[Internal-cg] how collaboration works today between the OCs

Alissa Cooper alissa at cooperw.in
Tue Oct 13 16:11:40 UTC 2015


Is there an update on this? Do we have agreed text to insert into the document, or are we putting this to the side?

Thanks,
Alissa

> On Oct 8, 2015, at 11:38 AM, Lynn St.Amour <Lynn at LStAmour.org> wrote:
> 
> First, we'd like to thank all the ICG members for their very helpful comments. 
> 
> And, we are now pulling this back up to the top of the pile, noting that it has not yet been incorporated into Part 0.   The WG needs a bit more time to complete it.
> 
> Lynn
> 
> 
> On Oct 4, 2015, at 11:37 AM, Kavouss Arasteh <kavouss.arasteh at gmail.com> wrote:
> 
>> Patrik
>> I agree with you, I suggest the the broad lines os collaboration among various OCs to be summarized and  included in the final report together with the example that you did provide
>> BR
>> Kavouss
>> 
>> 
>> Sent from my iPhone
>> 
>>> On 4 Oct 2015, at 15:10, joseph alhadeff <joseph.alhadeff at oracle.com> wrote:
>>> 
>>> good example of needs-generated dynamic cooperative process...
>>> 
>>>> On 10/3/2015 7:00 AM, Patrik Fältström wrote:
>>>> The explicit examples that exists are very few. My favourite example involves the IP addresses.
>>>> 
>>>> IETF set the over all policy for IP addresses. Some blocks are to be used for routing on the Internet. IANA keep track of this over arching allocation. RIRs then sets the detailed policy for those subsets of the addresses. When RIRs later request addresses from IANA,  IN-ADDR.ARPA and IP6.ARPA zones (and whois) are updated accordingly, i.e. managed by IANA, although ARPA TLD is managed by IAB.
>>>> 
>>>> So, IETF set the over arching policy, RIRs set the detailed policy. IANA is coordinating and keeps track of all of this.
>>>> 
>>>>  Patrik
>>>> 
>>>>> On 3 Oct 2015, at 12:36, joseph alhadeff wrote:
>>>>> 
>>>>> Patrik:
>>>>> 
>>>>> I don't think there's a real issue with keeping the OC descriptions/historical function as long as we provide the needed examples of cooperation and consultation across different scenarios.  The mere statement that the concept of cooperation exists is not sufficient to make the needed point that collaboration and cooperation are context specific/as needed or provide the kind of assurance that will address the misplaced desire to develop or impose a specific mechanism for collaboration and cooperation.
>>>>> 
>>>>> Joe
>>>>> 
>>>>>> On 10/3/2015 2:57 AM, Patrik Fältström wrote:
>>>>>>> On 3 Oct 2015, at 1:42, Alissa Cooper wrote:
>>>>>>> 
>>>>>>> The fact that the bodies that establish registry policies can also choose which operator will run the registry is interesting, but it’s a bit of a subtle point and I think it may be complicated to explain without adding a lot of additional clarifying value.
>>>>>> Hmm...let me just ensure my point is made clear here.
>>>>>> 
>>>>>> As each registry is decided upon by the OC defining it, and not the OCs as a collective, collaboration is explicitly needed. They must explicitly reach out to the other OCs and collaborate with them.
>>>>>> 
>>>>>> That was my point.
>>>>>> 
>>>>>> Patrik
>>>>>> 
>>>>>> 
>>>>>> _______________________________________________
>>>>>> Internal-cg mailing list
>>>>>> 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
>>> 
>>> 
>>> _______________________________________________
>>> Internal-cg mailing list
>>> 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
> 
> 
> _______________________________________________
> Internal-cg mailing list
> Internal-cg at mm.ianacg.org
> http://mm.ianacg.org/mailman/listinfo/internal-cg_ianacg.org




More information about the Internal-cg mailing list