Technology and engineering · 2002
RFC 3349: A Transient Prefix for Identifying Profiles under Development by the Working Groups of the Internet Engineering Task Force
by M. Rose
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.
Anyone can see what's on the shelves. Open a book with a free account, and stay in touch with its book club.
- First published
- 2002
- Status
- Best Current Practice
- Pages
- 6
- Also known as
- BCP 59
- Copyright
- ✓ Free to read · Copied in full, as published
Where it comes from
RFC Editor · IETF Datatracker · IETF Trust Legal Provisions
Copied in full and unchanged from the RFC Editor, with the RFC's own notices. © IETF Trust and the persons identified as the document authors. The IETF Trust allows copying and distributing an RFC in full and without modification, so Micwyn shows it exactly as published and makes no study guide, audio or other version of it.
Discuss a passage
Select any passage in the reader and press Discuss to talk about it in public.