On Thu, Aug 27, 2015 at 6:39 AM, Petr Spacek <pspa...@redhat.com> wrote:
> Dear DNSOP Chairs, > > I'm requesting a call for adoption of draft-spacek-dnsop-update-clarif. > > We did not have time allocated for discussing this in Prague but the draft > is > so short and easy (to quote Mark's words: "blatantly obvious") that I do > not > feel that postponing this till Yokohama is necessary. > > Thank you. > Petr Spacek > > > A new version of I-D, draft-spacek-dnsop-update-clarif-01.txt > has been successfully submitted by Petr Spacek and posted to the > IETF repository. > > Name: draft-spacek-dnsop-update-clarif > Revision: 01 > Title: Clarifications to the Dynamic Updates in the Domain Name > System (DNS > UPDATE) specification > Document date: 2015-08-27 > Group: Individual Submission > Pages: 5 > URL: > > https://www.ietf.org/internet-drafts/draft-spacek-dnsop-update-clarif-01.txt > Status: > https://datatracker.ietf.org/doc/draft-spacek-dnsop-update-clarif/ > Htmlized: > https://tools.ietf.org/html/draft-spacek-dnsop-update-clarif-01 > Diff: > https://www.ietf.org/rfcdiff?url2=draft-spacek-dnsop-update-clarif-01 > > Abstract: > This document clarifies interaction among Dynamic Updates in the > Domain Name System (DNS UPDATE), Classless IN-ADDR.ARPA delegation, > and Secure Domain Name System (DNS) Dynamic Update in the presence of > CNAME/DNAME redirections. > > Minor grammar suggestion - add "the" at three places: -----Change A Requestor MUST resolve (canonicalize) the original owner name (e.g. the one derived from an IPv4 address) to a canonical owner name before constructing the Update Message. The requestor MUST follow whole chain of redirections until the terminal node of the chain is reached and use canonical name found at the terminal node. Implementations MUST detect infinite loops. Canonical owner name MUST be used instead of the original owner name in the resulting Update Message: ----to: A Requestor MUST resolve (canonicalize) the original owner name (e.g. the one derived from an IPv4 address) to a canonical owner name before constructing the Update Message. The requestor MUST follow the whole chain of redirections until the terminal node of the chain is reached and use the canonical name found at the terminal node. Implementations MUST detect infinite loops. The canonical owner name MUST be used instead of the original owner name in the resulting Update Message: -- Bob Harold
_______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
