[Internal-cg] Text on .arpa for combined proposal

[Alissa Cooper]

Hi Narelle,

I’m unclear on why we would put this in part 0. These points are already reflected in paragraphs 2018, 2033, and 3047 of the proposal.

Alissa

> On Oct 19, 2015, at 10:11 AM, Narelle Clark <narelle.clark at accan.org.au> wrote:
> 
> 
> 
> 
> 
> Proposed Text:
> 
>  The additional domains under .arpa, such as “in-addr.arpa” and “ip6.arpa”, do not occur in the root zone.  The provision of these services are solely under the purview of the IAB as the authority of the .ARPA registry and therefore not included in the transition as existing systems will continue to apply.
> 
> Include references:
> https://www.iab.org/documents/correspondence-reports-documents/docs200 <https://www.iab.org/documents/correspondence-reports-documents/docs200>0/iab-statement-on-infrastructure-domain-and-subdomains-may-2000/
> 
>   RFC 3172 <https://tools.ietf.org/html/rfc3172 <https://tools.ietf.org/html/rfc3172>> defines the Management Guidelines & Operational Requirements for .ARPA.
> 
> -----8 <---------8 <-------------
> 
>  I had suggested this go into the section 'Workability' because it should go with the piece on the RZM.
> 
>  I now think that both of those paragraphs should go in under the heading 'Completeness and Clarity' at the end. These are parts that are not addressed in the combined proposal and everyone is happy that they aren't.
> 
> Both seem more relevant there.
> 
> 
> Narelle 
> _______________________________________________
> Internal-cg mailing list
> Internal-cg at mm.ianacg.org
> http://mm.ianacg.org/mailman/listinfo/internal-cg_ianacg.org

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.ianacg.org/pipermail/internal-cg_ianacg.org/attachments/20151019/3036276b/attachment.html>