Browse Prior Art Database

A Transient Prefix for Identifying Profiles under Development by the Working Groups of the Internet Engineering Task Force (RFC3349)

IP.com Disclosure Number: IPCOM000009260D
Original Publication Date: 2002-Jul-01
Included in the Prior Art Database: 2005-May-19
Document File: 7 page(s) / 8K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

M. Rose: AUTHOR

Abstract

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 text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 36% of the total text.

Network Working Group                                            M. Rose
Request for Comments: 3349                  Dover Beach Consulting, Inc.
BCP: 59                                                        July 2002
Category: Best Current Practice


  A Transient Prefix for Identifying Profiles under Development by the
         Working Groups of the Internet Engineering Task Force

Status of this Memo

   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.

Copyright Notice

   Copyright (C) The Internet Society (2002).  All Rights Reserved.

Abstract

   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.

Rose                     Best Current Practice                  [Page 1]
RFC 3349            Transient IDs for BEEP Profiles            July 2002


Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  Practice . . . . . . . . . . . . . . . . . . . . . . . . . . .  3
   3.  Security Considerations  . . . . . . . . . . . . . . . . . . .  4
       References . . . . . . . . . . . . . . . . . . . . . . . . . .  4
   A.  Acknowledgements . . . . . . . . . . . . . . . . . . . . . . .  5
   B.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . .  5
       Author's Address . . . . . . . . . . . . . . . . . . . . . . .  5
       Full Copyright Statement . . . . . . . . . . . . . . . . . . .  6

Rose                     Best Current Practice                  [Page 2]
RFC 3349            Transient IDs for BEEP Profiles            July 2002


1. Introduction

   Each BEEP profile [1] is identified by a URI [2].  The BEEP
   specification uses URIs to identify a BEEP profile both:

   o  statically, when a profile is formally defined (RFC 3080's Section
      5.1); and,

   o  dynamically, during channel management (RFC 3080's Section 2.3.1).

   If the BEEP profile appears on the standards-track [3], then the IANA
   is responsible for assigning the URI associated with the BEEP
   profile.  Otherwise, the entity specifying the BEEP profile is free
   to assign a URI under its administration to the profile.

   If a working group of the IETF is developing a BEEP profile, then,
   during the development process, it is desirable to use a transient
   identifier for the profile.  Furthe...