[CRISP-TEAM] draft proposal issue: reverse DNS

[Izumi Okutani]

I find this draft make it very clear the points we wanted to emphasize.
Thanks Andrei for the work on precise wordings.

Michael, apologies for streams of last minutes requests -
*if* it's still possible to accomodate, please highlight this and add to 
the draft.

If it cannot be accomodated, I'll still mention it in the call, so no 
worries.


Izumi

(2014/12/17 4:52), Andrei Robachevsky wrote:
> Izumi, thank you for this excellent summary.
>
> Some proposed changes below.
>
> Izumi Okutani wrote on 16/12/14 15:48:
>> Many thanks Andrei for a very comprehensive summary of the current
>> situation.
>>
>> It's helpful to clarify:
>>
>>   -  NTIA is not involved in delegation of *.IN-ADDR.ARPA and *.IP6.ARPA
>>
>>   -  IETF, as the delegated entity of TLD ".ARPA" defines delegations of
>>      *.IN-ADDR.ARPA and *.IP6.ARPA
>>
>>   -  IETF defines to delegate *.IN-ADDR.ARPA and *.IP6.ARPA according to
>>      address management heirachical structure
>>      i.e. -->IANA-->RIRs
>>
>> Does anyone feel we *shouldn't* include it in the draft proposal,
>> suggested by Alan below?
>>
>> If not, let's prepare to include it. If we document this, I feel we want
>> to be clear that this does not involve NTIA, as Andrei's suggested
>> approach about overlaps.
>>
>> I'd like to call for volunteers to work on this wording.
>>
>> Alan and/or Andrei, would you be willing to help in drafting this part?
>> Anyone else would be welcome to volunteer ofcourse.
>
> OLD:
>
> The global Internet community also depends upon the IANA operator for
> administration of the special-purpose �IN-ADDR.ARPA� and �IPv6.ARPA� DNS
> zones which is associated with IPv4 and IPv6 number resources
> respectively. It is the understanding of the Regional Internet Registry
> community that the IANA operator administers these zones per request of
> the Internet Architecture Board (�IAB�)3 as �agreed technical work
> items� per the IETF- ICANN IANA MOU.
>
> NEW:
>
> The global Internet community also depends upon the IANA operator for
> administration of the special-purpose �IN-ADDR.ARPA� and �IP6.ARPA� DNS
> zones which is associated with IPv4 and IPv6 number resources
> respectively. These zones are delegated to IANA by the IAB and
> "[s]ub-delegations within this hierarchy are undertaken in accordance
> with the IANA's address allocation practices" (RFC3172). The IANA
> operator administers these zones as �agreed technical work items� per
> the IETF- ICANN IANA MOU. It is important to note that this work is
> outside the scope of the NTIA contract.
>
> OLD:
>
> The Internet numbering community proposes that a new contract be
> established between the IANA functions operator and the five Regional
> Internet Registries (RIRs). The contract, essentially an IANA Service
> Level Agreement, would obligate the IANA functions operator to carry out
> those IANA functions relating to the global Internet number pools
> according to policies developed by the regional communities via the
> global Policy Development Process (gPDP).
>
> NEW:
>
> The Internet numbering community proposes that a new contract be
> established between the IANA functions operator and the five Regional
> Internet Registries (RIRs). The contract, essentially an IANA Service
> Level Agreement, would obligate the IANA functions operator to carry out
> those IANA functions relating to the global Internet number pools
> according to policies developed by the regional communities via the
> global Policy Development Process (gPDP) as well as the management of
> the delegations within IN-ADDR.ARPA and IP6.ARPA domains.
>
>
> Regards,
>
> Andrei
>