Request for IETF Input: Reuse of Protocol Number 33

Allison Mankin <mankin@psg.com> Thu, 19 May 2005 21:24 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DYsVI-0002HG-BI; Thu, 19 May 2005 17:24:28 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DYsTP-000260-Gy; Thu, 19 May 2005 17:22:31 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA02601; Thu, 19 May 2005 17:22:28 -0400 (EDT)
Received: from [132.151.6.50] (helo=newodin.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DYske-0002qo-5H; Thu, 19 May 2005 17:40:20 -0400
Received: from apache by newodin.ietf.org with local (Exim 4.43) id 1DYsTN-0002t5-6I; Thu, 19 May 2005 17:22:29 -0400
Content-Type: text/plain;
Mime-Version: 1.0
To: IETF Announcement list <ietf-announce@ietf.org>
From: Allison Mankin <mankin@psg.com>
Message-Id: <E1DYsTN-0002t5-6I@newodin.ietf.org>
Date: Thu, 19 May 2005 17:22:29 -0400
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
X-Mailman-Approved-At: Thu, 19 May 2005 17:24:25 -0400
Cc: dccp@ietf.org, iana@iana.org
Subject: Request for IETF Input: Reuse of Protocol Number 33
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

Protocols which can be encapsulated in IP datagrams must be assigned a
Protocol Number as defined in RFC2780. This number is used in an 8
bit field the IP header ("Protocol" in IPv4, "Next Header" in IPv6) to
identify the encapsulated protocol. Due to the limited range of
available values, it is desirable to recycle numbers, although not
sought in general by the IESG. Current assignments may be found at
http://www.iana.org/assignments/protocol-numbers.

The Datagram Congestion Control Protocol (recently approved)
has requested from IANA that it be permitted to reuse the
Protocol Number 33, currently assigned to the Sequential Exchange
Protocol (SEP). It is believed that this protocol has not been used
for many years. The protocol author, Jon Crowcroft, confirms this
view.

This note initiates a two week last call (to end 3 June 2005) to
solicit any indication that SEP is in active use. If there is no
indication by the date above, the IESG will let IANA know that
Protocol Number 33 may be assigned to DCCP, and that the
use of 33 for SEP will be considered OBSOLETE.

Public comments may be sent to ietf@ietf.org. Private comments may
be sent to the Responsible Area Director, Allison Mankin,
<mankin-at-psg.com>.

_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce