rfc6712.txt   rfc6712_altered.txt 
Internet Engineering Task Force (IETF) T. Kause Internet Engineering Task Force (IETF) T. Kause
Request for Comments: 6712 SSH Request for Comments: 6712 SSH
Updates: 4210 M. Peylo Updates: 4210 M. Peylo
Category: Standards Track NSN Category: Standards Track NSN
ISSN: 2070-1721 September 2012 ISSN: 2070-1721 September 2012
Internet X.509 Public Key Infrastructure -- HTTP Transfer Internet X.509 Public Key Infrastructure -- HTTP Transfer for the
for the Certificate Management Protocol (CMP) Certificate Management Protocol (CMP)
Abstract Abstract
This document describes how to layer the Certificate Management This document describes how to layer the Certificate Management
Protocol (CMP) over HTTP. It is the "CMPtrans" document referenced Protocol (CMP) over HTTP. It is the "CMPtrans" document referenced
in RFC 4210; therefore, this document updates the reference given in RFC 4210; therefore, this document updates the reference given
therein. therein.
Status of This Memo Status of This Memo
This is an Internet Standards Track document. This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has (IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 5741. Internet Standards is available in Section 2 of RFC 7841.
Information about the current status of this document, any errata, Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc6712. http://www.rfc-editor.org/info/rfc6712.
Copyright Notice Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Revised BSD License text as described in Section 4.e of the
the Trust Legal Provisions and are provided without warranty as Trust Legal Provisions and are provided without warranty as described
described in the Simplified BSD License. in the Revised BSD License.
This document may contain material from IETF Documents or IETF This document may contain material from IETF Documents or IETF
Contributions published or made publicly available before November Contributions published or made publicly available before November
10, 2008. The person(s) controlling the copyright in some of this 10, 2008. The person(s) controlling the copyright in some of this
material may not have granted the IETF Trust the right to allow material may not have granted the IETF Trust the right to allow
modifications of such material outside the IETF Standards Process. modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other it for publication as an RFC or to translate it into languages other
than English. than English.
Table of Contents Table of Contents
1. Introduction ....................................................2 1. Introduction
2. Conventions Used in This Document ...............................3 2. Conventions Used in This Document
3. HTTP-Based Protocol .............................................3 3. HTTP-Based Protocol
3.1. HTTP Versions ..............................................4 3.1. HTTP Versions
3.2. Persistent Connections .....................................4 3.2. Persistent Connections
3.3. General Form ...............................................4 3.3. General Form
3.4. Media Type .................................................4 3.4. Media Type
3.5. Communication Workflow .....................................5 3.5. Communication Workflow
3.6. HTTP Request-URI ...........................................5 3.6. HTTP Request-URI
3.7. Pushing of Announcements ...................................5 3.7. Pushing of Announcements
3.8. HTTP Considerations ........................................6 3.8. HTTP Considerations
4. Implementation Considerations ...................................7 4. Implementation Considerations
5. Security Considerations .........................................7 5. Security Considerations
6. IANA Considerations .............................................8 6. IANA Considerations
7. Acknowledgments .................................................8 7. Acknowledgments
8. References ......................................................9 8. References
8.1. Normative References .......................................9 8.1. Normative References
8.2. Informative References .....................................9 8.2. Informative References
Authors' Addresses
1. Introduction 1. Introduction
The Certificate Management Protocol (CMP) [RFC4210] requires a well- The Certificate Management Protocol (CMP) [RFC4210] requires a well-
defined transfer mechanism to enable End Entities (EEs), Registration defined transfer mechanism to enable End Entities (EEs), Registration
Authorities (RAs), and Certification Authorities (CAs) to pass Authorities (RAs), and Certification Authorities (CAs) to pass
PKIMessage sequences between them. PKIMessage sequences between them.
The first version of the CMP specification [RFC2510] included a brief The first version of the CMP specification [RFC2510] included a brief
description of a simple transfer protocol layer on top of TCP. Its description of a simple transfer protocol layer on top of TCP. Its
skipping to change at page 9, line 25 skipping to change at line 399
8.1. Normative References 8.1. Normative References
[ITU.X690.1994] [ITU.X690.1994]
International Telecommunications Union, "Information International Telecommunications Union, "Information
Technology - ASN.1 encoding rules: Specification of Basic Technology - ASN.1 encoding rules: Specification of Basic
Encoding Rules (BER), Canonical Encoding Rules (CER) and Encoding Rules (BER), Canonical Encoding Rules (CER) and
Distinguished Encoding Rules (DER)", ITU-T Recommendation Distinguished Encoding Rules (DER)", ITU-T Recommendation
X.690, 1994. X.690, 1994.
[RFC1945] Berners-Lee, T., Fielding, R., and H. Frystyk, "Hypertext [RFC1945] Berners-Lee, T., Fielding, R., and H. Frystyk, "Hypertext
Transfer Protocol -- HTTP/1.0", RFC 1945, May 1996. Transfer Protocol -- HTTP/1.0", RFC 1945,
DOI 10.17487/RFC1945, May 1996,
<https://www.rfc-editor.org/info/rfc1945>.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>.
[RFC2510] Adams, C. and S. Farrell, "Internet X.509 Public Key [RFC2510] Adams, C. and S. Farrell, "Internet X.509 Public Key
Infrastructure Certificate Management Protocols", RFC Infrastructure Certificate Management Protocols",
2510, March 1999. RFC 2510, DOI 10.17487/RFC2510, March 1999,
<https://www.rfc-editor.org/info/rfc2510>.
[RFC2616] Fielding, R., Gettys, J., Mogul, J., Frystyk, H., [RFC2616] Fielding, R., Gettys, J., Mogul, J., Frystyk, H.,
Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext
Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999. Transfer Protocol -- HTTP/1.1", RFC 2616,
DOI 10.17487/RFC2616, June 1999,
<https://www.rfc-editor.org/info/rfc2616>.
[RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
Resource Identifier (URI): Generic Syntax", STD 66, RFC Resource Identifier (URI): Generic Syntax", STD 66,
3986, January 2005. RFC 3986, DOI 10.17487/RFC3986, January 2005,
<https://www.rfc-editor.org/info/rfc3986>.
[RFC4210] Adams, C., Farrell, S., Kause, T., and T. Mononen, [RFC4210] Adams, C., Farrell, S., Kause, T., and T. Mononen,
"Internet X.509 Public Key Infrastructure Certificate "Internet X.509 Public Key Infrastructure Certificate
Management Protocol (CMP)", RFC 4210, September 2005. Management Protocol (CMP)", RFC 4210,
DOI 10.17487/RFC4210, September 2005,
<https://www.rfc-editor.org/info/rfc4210>.
8.2. Informative References 8.2. Informative References
[RFC2818] Rescorla, E., "HTTP Over TLS", RFC 2818, May 2000. [RFC2818] Rescorla, E., "HTTP Over TLS", RFC 2818,
DOI 10.17487/RFC2818, May 2000,
<https://www.rfc-editor.org/info/rfc2818>.
[RFC4301] Kent, S. and K. Seo, "Security Architecture for the [RFC4301] Kent, S. and K. Seo, "Security Architecture for the
Internet Protocol", RFC 4301, December 2005. Internet Protocol", RFC 4301, DOI 10.17487/RFC4301,
December 2005, <https://www.rfc-editor.org/info/rfc4301>.
[RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security [RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security
(TLS) Protocol Version 1.2", RFC 5246, August 2008. (TLS) Protocol Version 1.2", RFC 5246,
DOI 10.17487/RFC5246, August 2008,
<https://www.rfc-editor.org/info/rfc5246>.
Authors' Addresses Authors' Addresses
Tomi Kause Tomi Kause
SSH Communications Security SSH Communications Security
Takomotie 8 Takomotie 8
Helsinki 00380 Helsinki 00380
Finland Finland
Email: toka@ssh.com
EMail: toka@ssh.com
Martin Peylo Martin Peylo
Nokia Siemens Networks Nokia Siemens Networks
Linnoitustie 6 Linnoitustie 6
Espoo 02600 Espoo 02600
Finland Finland
Email: martin.peylo@nsn.com
EMail: martin.peylo@nsn.com
 End of changes. 17 change blocks. 
39 lines changed or deleted 54 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/