version -01 of draft-ietf-dnsext-dns-protocol-profile sent

[George Michaelson <ggm@apnic.net>]

I have just submitted a 01 revision of draft-ietf-dnsext-dns-protocol- 
profile, incorporating many of the comments from the namedroppers list.

Comments from Mark Andrews, Florien Weimer and Stephane Bortzmeyer  
weren't incorporated at this time, because
I couldn't see convergence on a clear, non-normative text change in  
the discussion. My instructions from Olafur are to
leave it to the WG to determine normative text, and only change when  
clear.

 A lot of non-normative changes such as spelling and syntactic fixes  
from Joe Abley and Wouter Wijngaards were incorporated wholesale,  
including getting rid of a specious reference to RFC1997 (BGP...) and  
updating several other RFC references. There are still many places in  
the document with text, lacking normative references entirely.

A couple of minor normative language changes from both Joe and Wouter  
were incorporated. I believe these did not alter the sense of the  
normative language, only its syntax.

A few new non-normative language references were introduced. For  
example the reference to NSID. Since this did not seem contentious,  
and is non-binding, I did it in the short term but if on reflection  
NSID is a problem area for people as couched, I can remove it again. I  
added slightly different references in for Authoritative Servers and  
Recursive Resolvers
since the RFC observes the transitive issue slightly differently in  
each case.

Some more deep, structural proposals from Wouter were not incorporated  
at this time. I believe I need to discuss these with
Olafur, since they imply a different approach to the document. I would  
say in the meantime that I think they made perfect sense in the main,  
and would simplify reading the document.

An ID issues tracker is obviously needed. I have sent some mail  
requesting assistance from one of the existing well known
ID tracker sites.

Paul Vixie's comments about XML are also valid, and I fully intend re- 
structuring the back-end XML into <include> form to
permit better editorial control of the text as it emerges, if the WG  
proceeds with this document.

Sam Weiler suggested that Olafur's instructions to the WG in respect  
of process might disagree with the statements in the -00
draft. I have not altered the document in that area, pending  
clarification of how people wish to proceed.

-George

----
12.  Changes since the -00 draft

Spelling, improved language and other editorial changes (which did not  
alter the substance of normative language) from the namedroppers list  
were incorporated wholesale. (jabley)

incorrect normative reference to 1997 removed. (jabley).

text from 3597 on Transparancy for unknown RRtypes included (jabley).

Better normative language for 4.1.1 (TCP Connection Management)  
adopted (jabley).

Better normative language for 4.2.2 (TCP) adopted (jabley).

Better normative language for 4.3 (UDP DNS Message Processing) adopted  
(jabley).

References for OPT processing clarified (jabley).

A section addressing [RFC 5001] in respect of NSID was added to the  
Server section and the Recursive Resolver section. (jabley)  
incorporated.

Editorial from ml adopted for key approach section (wijngaards)

incorrect normative reference to 1997 corrected to 2671 (wijngaards)

added normative reference to 4343 (wijngaards)

added normative reference to RRset TTL (wijngaards)

editoral text in respect of NOTIFY/UPDATE (wijngaards)

normative editorial text in respect of FORMERR TC bit (wijngaards)


--
to unsubscribe send a message to namedroppers-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/namedroppers/>