Re: Last Call: 'The Base16, Base32, and Base64 Data Encodings' to Proposed Standard

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

 




--On Tuesday, 11 April, 2006 11:26 +1000 Mark Andrews
<Mark_Andrews@xxxxxxx> wrote:

>> On 4/10/06 4:31 PM, "Mark Andrews" <Mark_Andrews@xxxxxxx>
>> wrote:
>> 
>> >> Did the base32 extended hex version get used in the SASL
>> >> work? Can we upda
>> te
>> >> the reference or if it is not needed not just remove it.
>> > 
>> > base32 extended hex is being / will be used for NSEC3 as it
>> > preserves the sort order.
>> 
>> Great - perhaps we could add a reference to that. 
> 
> 	Work in progress. draft-ietf-dnsext-nsec3-04.txt needs to
> 	be update to say base32 extended hex and reference this
> 	draft.

But such a reference from the Base16, Base32,... draft is not
normative.  To simply give (clearly non-normative) examples,
with each encoding, of where it is used or expected to be used
seems to me to helpful to the reader and to cost almost nothing.

    john





_______________________________________________

Ietf@xxxxxxxx
https://www1.ietf.org/mailman/listinfo/ietf

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