Re: [sidr] Last Call: <draft-ietf-sidr-rfc6490-bis-04.txt> (Resource Public Key Infrastructure (RPKI) Trust Anchor Locator) to Proposed Standard

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Jul 29, 2015 at 08:52:22PM -0400, Richard Hansen wrote:

> I misread the MIME RFC; it requires line breaks every 76 characters, not
> every 75.  So I think 76 is a better choice.
> 
> My new proposal is to 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, a <CRLF> or <LF> line break MUST be inserted into
>           the Base64 encoded string every 76 or fewer characters.

If there are linebreaks, for best interoperability, each line should
contain a multiple of 4 base64 output characters, so that the
decoder can process each line without buffering "left-over" data
from the previous line.

Thus whether the width is 76 (from MIME) or 64 (from PEM), ...  it
should be a multiple of 4.

    http://tools.ietf.org/html/rfc4648#section-3.1

Of course if no line breaks are inserted, then the issue does not
arise.

-- 
	Viktor.




[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Fedora Users]