Re: Split the IANA functions?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 






On Mon, Jan 6, 2014 at 2:12 PM, Brian E Carpenter <brian.e.carpenter@xxxxxxxxx> wrote:
On 07/01/2014 05:20, Phillip Hallam-Baker wrote:
> Following up on Jari's post, I think it would be a prudent political move
> to split the IANA functions so that assignment of IP addresses is separate
> from the protocol registry functions. The motivation behind this is to
> protect the IETF.

Actually the reason we included explosive bolts in the IETF-ICANN MoU was
to protect the IETF in this way. (By "explosive bolts" I mean the unilateral
6 months notice.) I'm not sure why would need to blow the bolts in adavance
of an emergency.

I am not suggesting changing the operation of the registry or taking it away from ICANN which is what I would see as 'blowing the bolts'.

I am suggesting painting a new sign for the protocol side of the functions.

The closest analogy I have is that in Vermont during hunting season it is very common to find a cow with 'COW' painted on the side in big white letters. The reason for this is that there is a particular type of 'hunter' who comes up from the city once a year with his mates, a large quantity of beer and an injudicious quantity of firearms and ammunition. They are liable shoot anything that moves. Labeling the livestock is the best way to mitigate the losses.
 
> Like the DNS, the allocation of IP address space and BGP parameters is a
> potential control point.

The MoU contains no exception to IETF control for BGP parameters.
And to be clear, the IETF retains control of "assignments of domain
names for technical uses", so DNS asignments and IP address assignments
are on exactly the same footing: IANA functions where the IETF has
agreed that "policy issues are outside the scope of this MOU." That
is not the case for BGP parameters. Since AS numbers are not in short
supply, and are allocated by IANA upon "RIR request to the IANA or IETF
Review" I can't see why we would want to change anything.

The vulnerability is to folk whose knowledge of the IETF and IANA is equivalent to the weekend hunter types. It is important to take the issue off the table.
 

--
Website: http://hallambaker.com/

[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Fedora Users]