RFC 3349: A Transient Prefix for Identifying Profiles under Development by the Working Groups of the Internet Engineering Task Force
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC3349
- Published
- August 2002
- Authors
- M. Rose
- Status
- BEST CURRENT PRACTICE
- Stream
- IETF
- Area
- —
- Pages
- 6
- Also known as
- BCP59
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3195Reliable Delivery for syslogCurrent
November 2001
- RFC 3081Mapping the BEEP Core onto TCPCurrent
March 2001
- RFC 3080The Blocks Extensible Exchange Protocol CoreCurrent
March 2001
- RFC 3620The TUNNEL ProfileUpdated
October 2003
- RFC 3767Securely Available Credentials ProtocolUpdated
June 2004
- RFC 4767The Intrusion Detection Exchange Protocol (IDXP)Current
March 2007
- RFC 3529Using Extensible Markup Language-Remote Procedure Calling (XML-RPC) in Blocks Extensible Exchange Protocol (BEEP)Updated
April 2003
- RFC 3117On the Design of Application ProtocolsCurrent
November 2001
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?