Re: Last Call: draft-arkko-rfc2780-proto-update (IANA Allocation Guidelines for the Protocol Field) to BCP

Bernard Aboba <aboba@internaut.com> Wed, 07 November 2007 19:33 UTC

Return-path: <ietf-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ipqe7-0008R4-TX; Wed, 07 Nov 2007 14:33:03 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ipqe7-0008Qb-99 for ietf@ietf.org; Wed, 07 Nov 2007 14:33:03 -0500
Received: from mho-02-bos.mailhop.org ([63.208.196.179]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ipqe5-0006K4-1M for ietf@ietf.org; Wed, 07 Nov 2007 14:33:03 -0500
Received: from c-71-197-208-131.hsd1.or.comcast.net ([71.197.208.131] helo=internaut.com) by mho-02-bos.mailhop.org with esmtpa (Exim 4.68) (envelope-from <aboba@internaut.com>) id 1Ipqe4-0008Bm-3z for ietf@ietf.org; Wed, 07 Nov 2007 19:33:00 +0000
Received: by internaut.com (Postfix, from userid 1000) id E5FE582A6D; Wed, 7 Nov 2007 11:32:58 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by internaut.com (Postfix) with ESMTP id D8D2582A67 for <ietf@ietf.org>; Wed, 7 Nov 2007 11:32:58 -0800 (PST)
X-Mail-Handler: MailHop Outbound by DynDNS
X-Originating-IP: 71.197.208.131
X-Report-Abuse-To: abuse@dyndns.com (see http://www.mailhop.org/outbound/abuse.html for abuse reporting information)
X-MHO-User: U2FsdGVkX18ExR2UKUtsJDIxiLlqSEsw
Date: Wed, 07 Nov 2007 11:32:58 -0800
From: Bernard Aboba <aboba@internaut.com>
To: ietf@ietf.org
Message-ID: <Pine.LNX.4.64.0711071120410.27519@internaut.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Subject: Re: Last Call: draft-arkko-rfc2780-proto-update (IANA Allocation Guidelines for the Protocol Field) to BCP
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Errors-To: ietf-bounces@ietf.org

Jari Arkko said:

"> McBride never said so. He said you have to pay experts for the
> reviews.

Right, but that's not needed either. At least not if we are
talking about a registry that has policy Expert Review.
If an expert exists, he will be polled by IANA for an opinion.
If an expert is not assigned for the particular registry, IANA
will ask IESG to assign one."

Here is a different take on what happened: 

>From http://en.wikipedia.org/wiki/Common_Address_Redundancy_Protocol  :

"From OpenBSD.org:

As a final note of course, when we petitioned IANA, the IETF body 
regulating "official" internet protocol numbers, to give us numbers for 
CARP and pfsync our request was denied. Apparently we had failed to go 
through an official standards organization. Consequently we were forced 
to choose a protocol number which would not conflict with anything else 
of value, and decided to place CARP at IP protocol 112. We also placed 
pfsync at an open and unused number. We informed IANA of these decisions, 
but they declined to reply.

The reason for this is that no specification for CARP has ever been 
written. The closest thing to specifications is the implementation in 
OpenBSD.

Note that VRRP also uses IP protocol 112, having been assigned it by 
IANA."

See also:
http://archives.devshed.com/forums/networking-100/carp-1500297.html



_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf