A Transient Prefix for Identifying Profiles under Development by the Working Groups of the Internet Engineering Task Force
The information below is for an old version of the document that is already published as an RFC.
This is an older version of an Internet-Draft that was ultimately published as RFC 3349.
|Dr. Marshall T. Rose
|2013-03-02 (Latest revision 2002-03-01)
|Internet Engineering Task Force (IETF)
|Intended RFC status
|Best Current Practice
|Became RFC 3349 (Best Current Practice)
|Send notices to
A new Request for Comments is now available in online RFC libraries. BCP 59 RFC 3349 Title: A Transient Prefix for Identifying Profiles under Development by the Working Groups of the Internet Engineering Task Force Author(s): M. Rose Status: Best Current Practice Date: July 2002 Mailbox: firstname.lastname@example.org Pages: 6 Characters: 7916 SeeAlso: BCP 59 I-D Tag: draft-mrose-beep-transientid-02.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3349.txt As a part of their deliverables, working groups of the IETF may develop BEEP profiles. During the development process, it is desirable to assign a transient identifier to each profile. If the profile is subsequently published as an RFC, then a permanent identifier is subsequently assigned by the IANA. 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.