[rfc-dist] BCP 82, RFC 3692 on Assigning Experimental and Testing Numbers Considered Useful

rfc-editor@rfc-editor.org rfc-editor@rfc-editor.org
Fri, 30 Jan 2004 16:49:57 -0800


--NextPart


A new Request for Comments is now available in online RFC libraries.


        BCP 82
        RFC 3692

        Title:      Assigning Experimental and Testing Numbers
                    Considered Useful
        Author(s):  T. Narten
        Status:     Best Current Practice
        Date:       January 2004
        Mailbox:    narten@us.ibm.com
        Pages:      7
        Characters: 15054
        Updates:    2434

        I-D Tag:    draft-narten-iana-experimental-allocations-05.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3692.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.  For example, to test a new DHCP option, one needs
an option number to identify the new function.  This document
recommends that when writing IANA Considerations sections, authors
should consider assigning a small range of numbers for
experimentation purposes that implementers can use when testing
protocol extensions or other new features.  This document reserves
some ranges of numbers for experimentation purposes in specific
protocols where the need to support experimentation has been
identified.

This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for
improvements.  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.echo 
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.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type:  Message/External-body;
        access-type="mail-server";
        server="RFC-INFO@RFC-EDITOR.ORG"

Content-Type: text/plain
Content-ID: <040130164849.RFC@RFC-EDITOR.ORG>

RETRIEVE: rfc
DOC-ID: rfc3692

--OtherAccess
Content-Type:   Message/External-body;
        name="rfc3692.txt";
        site="ftp.isi.edu";
        access-type="anon-ftp";
        directory="in-notes"

Content-Type: text/plain
Content-ID: <040130164849.RFC@RFC-EDITOR.ORG>

--OtherAccess--
--NextPart--