IANA Action: Assignment of an IPV6 Hop-by-hop Option

IESG <iesg@ietf.org> Wed, 22 June 2005 19:23 UTC

Received: from localhost.localdomain ([] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DlApI-00079e-KF; Wed, 22 Jun 2005 15:23:56 -0400
Received: from odin.ietf.org ([] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dl6uO-0000Up-Au; Wed, 22 Jun 2005 11:12:56 -0400
Received: from ietf-mx.ietf.org (ietf-mx []) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA21836; Wed, 22 Jun 2005 11:12:53 -0400 (EDT)
Received: from [] (helo=newodin.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Dl7IX-0003Vn-HW; Wed, 22 Jun 2005 11:37:53 -0400
Received: from apache by newodin.ietf.org with local (Exim 4.43) id 1Dl6uL-0006ci-9i; Wed, 22 Jun 2005 11:12:53 -0400
Content-Type: text/plain
Mime-Version: 1.0
To: IETF Announcement list <ietf-announce@ietf.org>
From: IESG <iesg@ietf.org>
Message-Id: <E1Dl6uL-0006ci-9i@newodin.ietf.org>
Date: Wed, 22 Jun 2005 11:12:53 -0400
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 00e94c813bef7832af255170dca19e36
X-Mailman-Approved-At: Wed, 22 Jun 2005 15:23:54 -0400
Cc: iesg@ietf.org
Subject: IANA Action: Assignment of an IPV6 Hop-by-hop Option
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ietf-announce.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
Sender: ietf-announce-bounces@ietf.org
Errors-To: ietf-announce-bounces@ietf.org

The IESG received a request from the IANA on April 7, 2005
to review a request for a hop-by-hop option number assignment,
under the terms of RFC 2780. The request is appended, for

The IESG declines Dr. Roberts's request for a hop-by-hop option for
QOS purposes. The proposal includes significant changes to the
Internet architecture including a new TCP congestion control
algorithm, new requirements for IPsec security gateways and new
behavior for routers. Adopting the changes to the Internet
architecture contemplated by this proposal would require review and
consensus within the IETF; it would be inappropriate for another
standards organization to modify IETF protocols as contemplated by
this proposal. Within the NSIS working group, the IETF is already
actively working on solutions to QOS and to other problems identified
in this specification. We believe that these efforts will lead to a
preferable solution to the problems identified in this proposal.
Reviewing this proposal within the IETF as an alternative to the
ongoing work would be a multi-year endeavor. The IESG is pessimistic that
this effort would ever achieve consensus. So, the IESG
declines the assignment request and recommends against pursuing this
proposal within the IETF.

We encourage any interested parties to review the ongoing work within NSIS.

From: "iana" <iana@iana.org>
To: <iesg@ietf.org>
Date: Thu, 7 Apr 2005 11:06:42 -0700
Subject: FW: General Request for Assignments (Roberts)


The IANA has received the following request.
It is possible that what Larry is looking for is a registration in section
5b of the following registry:

Currently the registration rules for this registry are described in RFC
2780. Is this something we can request get "IESG Approval" via the telechats?

Please advise.

Thank you,

Michelle Cotton

-----Original Message-----
From: lroberts@packet.cc [mailto:lroberts@packet.cc]
Sent: Friday, March 25, 2005 9:12 AM
To: iana@iana.org; lroberts@packet.cc
Subject: General Request for Assignments

Contact Name :
Lawrence Roberts

Contact Email :

Type of Assignment :
hop-by-hop option number assignment

Registry :

Description :
A protocol for QoS signaling has been prliminarly approved by the TIA and
the ITU that does in-band QoS signaling including preemption (for 911 ,
military, etc.). It needs an option assigned of the form 011xxxxx. It must
be a hop-by-hop option to be seen by the routers durring encryption.

Additional Info :
The ITU version has been sent to IESG (Brian Carpenter, An early draft is at

IETF-Announce mailing list