idnits 2.17.1 draft-mrose-beep-transientid-02.txt: Skipping this file; it looks like a tombstone file to me. -------------------------------------------------------------------------------- 1 A new Request for Comments is now available in online RFC libraries. 3 BCP 59 4 RFC 3349 6 Title: A Transient Prefix for Identifying Profiles under 7 Development by the Working Groups of the Internet 8 Engineering Task Force 9 Author(s): M. Rose 10 Status: Best Current Practice 11 Date: July 2002 12 Mailbox: mrose@dbc.mtview.ca.us 13 Pages: 6 14 Characters: 7916 15 SeeAlso: BCP 59 17 I-D Tag: draft-mrose-beep-transientid-02.txt 19 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3349.txt 21 As a part of their deliverables, working groups of the IETF may 22 develop BEEP profiles. During the development process, it is 23 desirable to assign a transient identifier to each profile. If the 24 profile is subsequently published as an RFC, then a permanent 25 identifier is subsequently assigned by the IANA. 27 This document specifies an Internet Best Current Practices for the 28 Internet Community, and requests discussion and suggestions for 29 improvements. Distribution of this memo is unlimited. 31 This announcement is sent to the IETF list and the RFC-DIST list. 32 Requests to be added to or deleted from the IETF distribution list 33 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 34 added to or deleted from the RFC-DIST distribution list should 35 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 37 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 38 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 39 help: ways_to_get_rfcs. For example: 41 To: rfc-info@RFC-EDITOR.ORG 42 Subject: getting rfcs 44 help: ways_to_get_rfcs 46 Requests for special distribution should be addressed to either the 47 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 48 specifically noted otherwise on the RFC itself, all RFCs are for 49 unlimited distribution.echo 50 Submissions for Requests for Comments should be sent to 51 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 52 Authors, for further information.