draft-ietf-lamps-rfc7030est-clarify-06.txt   draft-ietf-lamps-rfc7030est-clarify-07.txt 
LAMPS Working Group M. Richardson LAMPS Working Group M. Richardson
Internet-Draft Sandelman Software Works Internet-Draft Sandelman Software Works
Updates: 7030 (if approved) T. Werner Updates: 7030 (if approved) T. Werner
Intended status: Standards Track Siemens Intended status: Standards Track Siemens
Expires: December 16, 2020 W. Pan Expires: December 18, 2020 W. Pan
Huawei Technologies Huawei Technologies
June 14, 2020 June 16, 2020
Clarification of Enrollment over Secure Transport (EST): transfer Clarification of Enrollment over Secure Transport (EST): transfer
encodings and ASN.1 encodings and ASN.1
draft-ietf-lamps-rfc7030est-clarify-06 draft-ietf-lamps-rfc7030est-clarify-07
Abstract Abstract
This document updates RFC7030: Enrollment over Secure Transport (EST) This document updates RFC7030: Enrollment over Secure Transport (EST)
to resolve some errata that was reported, and which has proven to to resolve some errata that was reported, and which has proven to
cause interoperability issues when RFC7030 was extended. cause interoperability issues when RFC7030 was extended.
This document deprecates the specification of "Content-Transfer- This document deprecates the specification of "Content-Transfer-
Encoding" headers for EST endpoints. This document fixes some Encoding" headers for EST endpoints. This document fixes some
syntactical errors in ASN.1 that was presented. syntactical errors in ASN.1 that was presented.
skipping to change at page 1, line 40 skipping to change at page 1, line 40
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on December 16, 2020. This Internet-Draft will expire on December 18, 2020.
Copyright Notice Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the Copyright (c) 2020 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
(https://trustee.ietf.org/license-info) in effect on the date of (https://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
skipping to change at page 4, line 18 skipping to change at page 4, line 18
CRLF, while the "base64" used in MIME [RFC2045] does. This CRLF, while the "base64" used in MIME [RFC2045] does. This
specification clarifies that despite [RFC2616], that white space specification clarifies that despite [RFC2616], that white space
including CR, LF, spaces (ASCII 32) and, tabs (ASCII 9) SHOULD be including CR, LF, spaces (ASCII 32) and, tabs (ASCII 9) SHOULD be
tolerated by receivers. Senders are not required to insert any kind tolerated by receivers. Senders are not required to insert any kind
of white space. of white space.
3.2. Changes sections 4 of RFC7030 3.2. Changes sections 4 of RFC7030
3.2.1. Section 4.1.3 3.2.1. Section 4.1.3
Replace: In the paragraph reading:
A successful response MUST be a certs-only CMC Simple PKI Response, A successful response MUST be a certs-only CMC Simple PKI Response,
as defined in [RFC5272], containing the certificates described in the as defined in [RFC5272], containing the certificates described in the
following paragraph. The HTTP content-type of following paragraph. The HTTP content-type of
"application/pkcs7-mime" is used. The Simple PKI Response is sent "application/pkcs7-mime" is used. The Simple PKI Response is sent
with a Content-Transfer-Encoding of "base64" [RFC2045]. with a Content-Transfer-Encoding of "base64" [RFC2045].
Replace:
The Simple PKI Response is sent
with a Content-Transfer-Encoding of "base64" [RFC2045].
with: with:
A successful response MUST be a certs-only CMC Simple PKI Response, The CMC Simple PKI Response is encoded in base64 [RFC4648].
as defined in [RFC5272], containing the certificates described in the
following paragraph. The HTTP content-type of
"application/pkcs7-mime" is used. The CMC Simple PKI Response is
encoded in base64 [RFC4648].
3.2.2. Section 4.3.1 3.2.2. Section 4.3.1
Replace: In the paragraph reading:
If the HTTP POST to /fullcmc is not a valid Full PKI Request, the If the HTTP POST to /fullcmc is not a valid Full PKI Request, the
server MUST reject the message. The HTTP content-type used is server MUST reject the message. The HTTP content-type used is
"application/pkcs7-mime" with an smime-type parameter "CMC-request", "application/pkcs7-mime" with an smime-type parameter "CMC-request",
as specified in [RFC5273]. The body of the message is the binary as specified in [RFC5273]. The body of the message is the binary
value of the encoding of the PKI Request with a value of the encoding of the PKI Request with a
Content-Transfer-Encoding of "base64" [RFC2045]. Content-Transfer-Encoding of "base64" [RFC2045].
Replace:
The body of the message is the binary
value of the encoding of the PKI Request with a
Content-Transfer-Encoding of "base64" [RFC2045].
with: with:
If the HTTP POST to /fullcmc is not a valid Full PKI Request, the The body of the message is encoded in base64 [RFC4648].
server MUST reject the message. The HTTP content-type used is
"application/pkcs7-mime" with an smime-type parameter "CMC-request",
as specified in [RFC5273]. The body of the message is encoded
in base64 [RFC4648].
3.2.3. Section 4.3.2 3.2.3. Section 4.3.2
Replace: Replace:
The body of the message is the binary value of the encoding of the The body of the message is the binary value of the encoding of the
PKI Response with a Content-Transfer-Encoding of "base64" [RFC2045]. PKI Response with a Content-Transfer-Encoding of "base64" [RFC2045].
with: with:
 End of changes. 10 change blocks. 
16 lines changed or deleted 19 lines changed or added

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