[Tsvwg] Fwd: RFC 4727 on Experimental Values In IPv4, IPv6, ICMPv4, ICMPv6, UDP, and TCP Headers
Lars Eggert <lars.eggert@netlab.nec.de> Fri, 01 December 2006 06:51 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gq2F6-0000vi-Il; Fri, 01 Dec 2006 01:51:28 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gq2F4-0000ox-U8 for tsvwg@ietf.org; Fri, 01 Dec 2006 01:51:26 -0500
Received: from hiltonsmtp.worldspice.net ([216.37.94.58]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gq2F3-0002lb-H6 for tsvwg@ietf.org; Fri, 01 Dec 2006 01:51:26 -0500
Received: (qmail 18075 invoked by uid 0); 1 Dec 2006 06:48:52 -0000
Received: by simscan 1.2.0 ppid: 18056, pid: 18064, t: 2.5575s scanners: clamav: 0.88.4/m:40/d:1991 spam: 3.1.5
X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on hiltonsmtp.worldspice.net
X-Spam-Level:
X-Spam-Status: No, score=0.0 required=5.0 tests=BAYES_50 autolearn=disabled version=3.1.7
Received: from unknown (HELO lars.local) (nec-smtp@67.99.198.2) by hiltonsmtp.worldspice.net with ESMTPA; 1 Dec 2006 06:48:50 -0000
Received: from [127.0.0.1] (localhost [127.0.0.1]) by lars.local (Postfix) with ESMTP id 4B3FF29C201; Thu, 30 Nov 2006 22:51:06 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v752.2)
To: tsv-area@ietf.org, tsvwg <tsvwg@ietf.org>
Message-Id: <90E48311-1A5F-4922-BBA4-ADAB1BBF7800@netlab.nec.de>
Content-Type: multipart/signed; micalg="sha1"; boundary="Apple-Mail-53--182412457"; protocol="application/pkcs7-signature"
References: <200612010058.kB10wgfH015416@nit.isi.edu>
From: Lars Eggert <lars.eggert@netlab.nec.de>
Date: Thu, 30 Nov 2006 22:51:04 -0800
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: 1.8 (+)
X-Scan-Signature: 1449ead51a2ff026dcb23465f5379250
Cc:
Subject: [Tsvwg] Fwd: RFC 4727 on Experimental Values In IPv4, IPv6, ICMPv4, ICMPv6, UDP, and TCP Headers
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org
Note the experimental allocations for UDP and TCP, in case you are developing experimental extensions. Begin forwarded message: > A new Request for Comments is now available in online RFC libraries. > > > RFC 4727 > > Title: Experimental Values In IPv4, IPv6, > ICMPv4, ICMPv6, UDP, and TCP Headers > Author: B. Fenner > Status: Standards Track > Date: November 2006 > Mailbox: fenner@research.att.com > Pages: 11 > Characters: 19745 > Updates/Obsoletes/SeeAlso: None > > I-D Tag: draft-fenner-iana-exp-2780-05.txt > > URL: http://www.rfc-editor.org/rfc/rfc4727.txt > > When experimenting with or extending protocols, it is often necessary > to use some sort of protocol number or constant in order to actually > test or experiment with the new function, even when testing in a > closed environment. This document reserves some ranges of numbers > for experimentation purposes in specific protocols where the need to > support experimentation has been identified, and it describes the > numbers that have already been reserved by other documents. > [STANDARDS TRACK] > > This is now a Proposed Standard Protocol. > > STANDARDS TRACK: This document specifies an Internet standards track > protocol for the Internet community,and requests discussion and > suggestions for improvements.Please refer to the current edition of > the > Internet Official Protocol Standards (STD 1) for the standardization > state and status of this protocol. Distribution of this memo is > unlimited. > > This announcement is sent to the IETF list and the RFC-DIST list. > Requests to be added to or deleted from the IETF distribution list > should be sent to IETF-REQUEST@IETF.ORG. Requests to be > added to or deleted from the RFC-DIST distribution list should > be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. > > Details on obtaining RFCs via FTP or EMAIL may be obtained by sending > an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body > > help: ways_to_get_rfcs. For example: > > To: rfc-info@RFC-EDITOR.ORG > Subject: getting rfcs > > help: ways_to_get_rfcs > > Requests for special distribution should be addressed to either the > author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. > Unless > specifically noted otherwise on the RFC itself, all RFCs are for > unlimited distribution. > > Submissions for Requests for Comments should be sent to > RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions > to RFC > Authors, for further information. > > > The RFC Editor Team > USC/Information Sciences Institute > > ... > > > > _______________________________________________ > IETF-Announce mailing list > IETF-Announce@ietf.org > https://www1.ietf.org/mailman/listinfo/ietf-announce