RE: New I-D:draft-kaplan-enum-source-uri-00.txt
Hadriel Kaplan <[email protected]>
| Newsgroups | gmane.ietf.enum |
|---|---|
| Message-ID | <[email protected]> |
Hmm. Yeah, that was from an earlier (not-published) version of the draft which talked about how one could possibly extend this thing in the future without breaking backwards compatibility, and used that zero byte as a backwards compatible delimiter. But I forgot to fix that back when we removed that (ugly) idea. We'll remove that going forward. Thanks! -hadriel > -----Original Message----- > From: [email protected] [mailto:[email protected]] > Sent: Wednesday, December 12, 2007 5:27 PM > To: [email protected] > Subject: Re: [Enum] New I-D:draft-kaplan-enum-source-uri-00.txt > > How about a technical question? > > I see in section 9: "The URI field is null-terminated, ASCII > representation of the URI." Why is there a zero byte to mark the end > of the URI field? Its length is already encoded in the OPTION-LENGTH > field of the RDATA name/value pair. IIRC (and I may not), DNS > generally uses length-data format for variable length data, not an > end-marker format. > > Dale > > _______________________________________________ > enum mailing list > [email protected] > https://www1.ietf.org/mailman/listinfo/enum