[as112-ops] Update to draft for more AS112 delegations

[William F. Maton Sotomayor]

All,

 	Back on May 13, 2011, I posted a message regarding a new Internet 
Draft adding more delegations to AS112, mainly in keeping with keeping 
RFC 6304 in sync with the registry provided for in RFC 6303.  After some 
time, I'm ready to push out -03 of that draft.  One of the bigger changes 
I have made is to include proposed multicast documentation prefixes.  That 
and more will be found in the draft.

 	Those of you who followed the original message thread will also 
remember that the original draft was split into two, one as a directive to 
IANA and the other a more general treatise on care and feeding of AS112 
nodes.

 	Aside from making notes about lameness, etc., one thing that kept 
coming up in previous DNSOP wroking group meetings was a method for how, 
barring adopting something like Warren Kumari's idea, delegations to and 
removed from AS112 nodes should be carried out.  To date, there's no real 
established process except for spreading the word via this mailing list 
and the AS112 web site.  There's also Paul Vixie's idea plus some sample 
code he pointed to in one of the old threads.

 	For example, how does one request a delegation for AS112 nodes? 
Should there be a review?  Who does the reviewing?  Since RFC 6303's 
registry is a permanent one, should AS112 nodes strictly follow what's in 
that registry, or have an RFC create a separate registry that allows for 
temporary delegations of an experimental nature and results in a more 
flexible option?  Some things for AS112 operators to ponder while the 
draft I'm preparing makes some attempt at a proposal.

 	Once I have this draft ready, I'll post here for folks to bash on. 
Hopefully within the next week or so.

Thanks,

wfms