[Int-area] Assigning experimental code points for IP and related protocols

Bill Fenner <fenner@gmail.com> Tue, 02 August 2005 06:10 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DzpzB-00044P-3W; Tue, 02 Aug 2005 02:10:45 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dzpz7-00043D-OC for int-area@megatron.ietf.org; Tue, 02 Aug 2005 02:10:41 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA11103 for <int-area@ietf.org>; Tue, 2 Aug 2005 02:10:40 -0400 (EDT)
Received: from rproxy.gmail.com ([64.233.170.205]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1DzqVU-0004cq-3u for int-area@ietf.org; Tue, 02 Aug 2005 02:44:09 -0400
Received: by rproxy.gmail.com with SMTP id r35so1456449rna for <int-area@ietf.org>; Mon, 01 Aug 2005 23:10:36 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=W0eD8AdPjv5VtJHdsUcFUoodA7ozYVovcVj1pOXtJakPHL0oZ+n7cjFf7FXs0YT222DWctnMaLkJJV/gQUMCIkl1MBP6uDy7XPx1/wGZ77ccojEKhpTGAu4QICFsTu8iKjod+JqWL3hBQnJUe5fogBG2eUyZS85XzOn9ljMGoYQ=
Received: by 10.38.24.1 with SMTP id 1mr43026rnx; Mon, 01 Aug 2005 23:10:36 -0700 (PDT)
Received: by 10.38.10.40 with HTTP; Mon, 1 Aug 2005 23:10:36 -0700 (PDT)
Message-ID: <ed6d469d05080123101575fd39@mail.gmail.com>
Date: Tue, 02 Aug 2005 08:10:36 +0200
From: Bill Fenner <fenner@gmail.com>
To: int-area@ietf.org
Mime-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Content-Transfer-Encoding: quoted-printable
Cc:
Subject: [Int-area] Assigning experimental code points for IP and related protocols
X-BeenThere: int-area@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Bill Fenner <fenner@gmail.com>
List-Id: IETF Internet Area Mailing List <int-area.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/int-area>
List-Post: <mailto:int-area@lists.ietf.org>
List-Help: <mailto:int-area-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@lists.ietf.org?subject=subscribe>
Sender: int-area-bounces@lists.ietf.org
Errors-To: int-area-bounces@lists.ietf.org

This is the draft that I mentioned during the INT area meeting
yesterday.  It's a result of applying

3692 Assigning Experimental and Testing Numbers Considered Useful. T.
     Narten. January 2004. (Format: TXT=15054 bytes) (Updates RFC2434)
     (Also BCP0082) (Status: BEST CURRENT PRACTICE)

to

2780 IANA Allocation Guidelines For Values In the Internet Protocol
     and Related Headers. S. Bradner, V. Paxson. March 2000. (Format:
     TXT=18954 bytes) (Also BCP0037) (Status: BEST CURRENT PRACTICE)

        Title           : Experimental Values In IPv4, IPv6, ICMPv4,
ICMPv6, UDP and TCP Headers
        Author(s)       : B. Fenner
        Filename        : draft-fenner-iana-exp-2780-00.txt
        Pages           : 8
        Date            : 2005-7-12
        
   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 describes the
   numbers that have already been reserved by other documents.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-fenner-iana-exp-2780-00.txt

I'd love to get feedback on whether the proposed assignments are too
few, too many, or "just right".

Thanks,
  Bill

_______________________________________________
Int-area mailing list
Int-area@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/int-area