The draft draft-ietf-sidr-rfc6490-bis-04 was approved by the IESG, provided the comments received during IETF Last Call were addressed.
The IETF Last Call comments were noted to the sidr list in http://www.ietf.org/mail-archive/web/sidr/current/msg07208.html. As wg co-chair, I am satisfied that wg has consensus is to adopt “Option #2” [ (allow but do not mandate line breaks)] as mentioned in the message that brought up the problem [http://www.ietf.org/mail-archive/web/sidr/current/msg07164.html]. The draft authors are requested to submit a revised version of the draft including this response. That would get the draft to publication. In the initial message, the following text was suggested. The draft authors may use this as they wish. 2. Permit but don't require newlines. For example, change Section 2.1 item #3 from: 3) a subjectPublicKeyInfo [RFC5280] in DER format [X.509], encoded in Base64 (see Section 4 of [RFC4648]. to: 3) a subjectPublicKeyInfo [RFC5280] in DER format [X.509], encoded in Base64 (see Section 4 of [RFC4648]). To avoid long lines, <CRLF> or <LF> line breaks MAY be inserted into the Base64 encoded string. —Sandy, speaking as co-chair
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ sidr mailing list sidr@ietf.org https://www.ietf.org/mailman/listinfo/sidr
