update of wcard submitted

[Edward Lewis <Ed.Lewis@neustar.biz>]

I managed to get around to an update of the wcard draft.  I made 
updates based on notes from Alex and Robert.  I didn't make all the 
updates, nor did I manage time to even reread the whole thing myself.

In a few days, or perhaps at the meeting, I'll send in any 
substantive questions based on the comments received.  In general, 
the comments were about wording and not concepts as were any 
reactions I had.  Mostly, I wanted to keep the draft "chatty" because 
this is supposed to be a clarificiation and not a "dry" specification 
(countering some recommendations from Robert).

I still don't consider the draft well-written, nor set in type.

I guess I do have one more headache - whether or not to discuss DS 
and NSEC types at the parent.  I kind of have one foot into that rat 
hole when speaking about the NS types.  I'm not sure if I should pull 
my foot out or dive in with the second foot.  If we're mentioning 
DNAME, why not DS and NSEC?  OTOH, if this document sticks with 1034 
topics, mayne all of DNAME is dropped.

I suppose it's debate over whether this is an strict update of 1034 
or is an update on the concept of (1034:) wildcards.

BTW - As far as comments form Phill Halem-Baker, this draft is only a 
clarification of the documented status quo.  This document's 
expansion into other forms of synthesis is not appropriate - if the 
desire is there, then a new draft is needed that will update other 
documents.  This document can't endorse the new efforts, it can hint 
at requirements for them.  If it comes across as prohibiting them 
(e.g., the*.example. does not pattern match), that's because the 
current specs also "prohibit" the expansion - but don't take this as 
a "rejection with prejudice."  (Meaning - not allowed now, but 
proposals are welcome.)

--
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Edward Lewis                                            +1-571-434-5468
NeuStar

"Now under neu management"

--
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/>