will fold them in, thanks. /bill
On Sun, Feb 05, 2012 at 11:34:06AM -0500, Warren Kumari wrote: > Nits and notes: > > Abstract: > O: The DNS is considered a crucial part of that technical infrastrcuture. > P: The DNS is considered a crucial part of that technical infrastructure. > C: s/infrastrcuture/infrastructure/ -- typo. > > Background: > O: ...servers to enable robust dand resilientb & > P: ...servers to enable robust and resilientb & > C: s/dand/and/ -- typo. > > 1.4: > O: ...temporary simulatneous loss of manyb & > P: ...temporary simultaneous loss of manyb & > C: s/simulatneous/simultaneous/ -- typo. > > 3.2.1: > O: ...for TSIG and DNSSEC syncronizationb & > P: ...for TSIG and DNSSEC synchronizationb & > C: s/syncronization/synchronization/ -- typo. > > 3.2.6: > O: Servers must log in UTC to facilitate log comparison. > C: Seems a little strong -- If I want to log in fortnights since lunar > eclipse, that's my business -- as long as I'm willing to convert the log to > UTC before handing it to be analyzed. > > 3.2.8: > O: "The server should be protected from attacks based on source routing. The > server must not soley rely on address- or name-based authentication." > C: Seems like it should have more text. Not entirely sure what is being said > here. > also: s/soley/solely/ -- typo. > > 3.3.6: > O: ...based on the currnet update cycleb & > P: ...based on the current update cycleb & > C: s/currnet/current/ -- typo. > > 3.3.10: > O: These monitoring processes could be automated. > P: These monitoring processes should be automated. > > 4.2: > C: See "draft-mcpherson-unique-origin-as-00" (expired). Neither supporting > nor opposing the draft, just mentioning it. > > 5.1: > O: ... a scheduled maintaince windowb & > P: ... a scheduled maintenance windowb & > C: s/maintaince/maintenance/ --typo. > > > W > > > > > > On Feb 1, 2012, at 7:11 AM, [email protected] wrote: > > > > > The Root Server System Advisory Committee of ICANN has been working on a > > revision to RFC 2870. > > It is currently posted as: > > > > ------------ > > A New Internet-Draft is available from the on-line Internet-Drafts > > directories. > > > > Title : Root Name Server Operational Requirements > > Author(s) : Root Server System Advisory Committee > > Filename : draft-rssac-dnsop-rfc2870bis-03.txt > > Pages : 9 > > Date : 2012-01-31 > > > > As the Internet has become critical to the world's social and economic > > infrastructure, attention has focused on the correct, safe, reliable, and > > secure operation of the Internet infrastructure itself. The DNS is > > considered > > a crucial part of that technical infrastrcuture. The root domain and its > > authoritative name servers are a part of that technical infrastructure. > > > > The primary focus of this document is to provide guidelines for secure, > > stable, > > and resilient authoritative name service for the root zone. Additionally > > it will > > look into some specifics for the operation of the name servers. Other > > operators > > of authoritative name servers such as those for generic top-level domains > > (gTLDs), > > country code top-level domains (ccTLDs) and other zones may also find it > > useful. > > > > A URL for this Internet-Draft is: > > http://www.ietf.org/internet-drafts/draft-rssac-dnsop-rfc2870bis-03.txt > > ------------ > > > > Your comments would be appreciated. > > > > /bill > > _______________________________________________ > > DNSOP mailing list > > [email protected] > > https://www.ietf.org/mailman/listinfo/dnsop > > > > -- > Don't be impressed with unintelligible stuff said condescendingly. > -- Radia Perlman. > > > > > _______________________________________________ DNSOP mailing list [email protected] https://www.ietf.org/mailman/listinfo/dnsop
