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

[Alissa Cooper]

How about if we add a footnote to paragraph 62 (where there is already text about in-addr.arpa and ip6.arpa) as follows:

See https://tools.ietf.org/html/rfc3172 <https://tools.ietf.org/html/rfc3172> and https://www.iab.org/documents/correspondence-reports-documents/docs2000/iab-statement-on-infrastructure-domain-and-subdomains-may-2000/ <https://www.iab.org/documents/correspondence-reports-documents/docs2000/iab-statement-on-infrastructure-domain-and-subdomains-may-2000/> for more information about .ARPA. 
   

> On Oct 21, 2015, at 9:55 AM, Paul Wilson <pwilson at apnic.net> wrote:
> 
> I’m also not fussed about this; was merely following up with Narelle to action some suggestions that we both made in that teleconf meeting.
> 
> From my previous search, I couldn’t see these specific references included anywhere in the transition plan - so again it seemed worthwhile to add them somewhere.
> 
> Paul.
> 
> 
> On 21 Oct 2015, at 13:34, Narelle Clark wrote:
> 
>> The paragraphs you refer to cover a lot of detail. The part we were suggesting runs to the scope of the overall proposal generation, and therefore has a good home in part 0.
>> 
>> I’m not fussed either way. Particularly given there are other tlds or matters that could be similarly described.
>> 
>> 
>> Narelle
>> 
>> 
>> From: Alissa Cooper [mailto:alissa at cooperw.in]
>> Sent: Tuesday, 20 October 2015 12:53 AM
>> To: Narelle Clark
>> Cc: internal-cg at ianacg.org
>> Subject: Re: [Internal-cg] Text on .arpa for combined proposal
>> 
>> 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<mailto: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/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<mailto:Internal-cg at mm.ianacg.org>
>> http://mm.ianacg.org/mailman/listinfo/internal-cg_ianacg.org
>> 
>> _______________________________________________
>> Internal-cg mailing list
>> Internal-cg at mm.ianacg.org
>> http://mm.ianacg.org/mailman/listinfo/internal-cg_ianacg.org
> 
> ________________________________________________________________________
> Paul Wilson, Director-General, APNIC                        dg at apnic.net
> http://www.apnic.net                                            @apnicdg

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.ianacg.org/pipermail/internal-cg_ianacg.org/attachments/20151021/9f9d0aa8/attachment.html>