FW: BCP 59, RFC 3349 on A Transient Prefix for Identifying Profil es under Development by the Working Groups of the Internet Engineering Ta sk Force

"Hollenbeck, Scott" <shollenbeck@verisign.com> Fri, 02 August 2002 00:01 UTC

Message-ID: <3CD14E451751BD42BA48AAA50B07BAD60336FCE8@vsvapostal3.prod.netsol.com>
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
To: "'ietf-provreg@cafax.se'" <ietf-provreg@cafax.se>
Subject: FW: BCP 59, RFC 3349 on A Transient Prefix for Identifying Profil es under Development by the Working Groups of the Internet Engineering Ta sk Force
Date: Thu, 01 Aug 2002 19:54:42 -0400
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Sender: owner-ietf-provreg@cafax.se
Precedence: bulk

Being BEEP-related, this might be of interest to folks looking at the BEEP
transport I-D.

-Scott-

-----Original Message-----
From: rfc-editor@rfc-editor.org [mailto:rfc-editor@rfc-editor.org] 
Sent: Thursday, August 01, 2002 5:44 PM
To: rfc-dist@rfc-editor.org
Cc: rfc-editor@rfc-editor.org
Subject: [rfc-dist] BCP 59, RFC 3349 on A Transient Prefix for
Identifying Profiles under Development by the Working Groups of the
Internet Engineering Task Force

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:    mrose@dbc.mtview.ca.us
        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.

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.

FW: BCP 59, RFC 3349 on A Transient Prefix for Id… Hollenbeck, Scott