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

[Patrik Fältström]

FWIW: .ARPA itself is a separate zone, and not in the root zone. It is delegated just like any TLD. It is managed by the root server operators though, and delegated to the same set of name servers that runs the root zone.

   Patrik

 is a On 19 Oct 2015, at 10:11, Narelle Clark 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/docs2000/iab-statement-on-infrastructure-domain-and-subdomains-may-2000/
>
> RFC 3172 <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 --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 203 bytes
Desc: OpenPGP digital signature
URL: <http://mm.ianacg.org/pipermail/internal-cg_ianacg.org/attachments/20151019/de9bbd43/attachment.asc>