Protocol Action: A Transient Prefix for Identifying Profiles under Development by the Working Groups of the IETF to BCP
The IESG <iesg-secretary@ietf.org> Thu, 25 April 2002 21:48 UTC
Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA07336; Thu, 25 Apr 2002 17:48:21 -0400 (EDT)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id RAA22557 for ietf-123-outbound.10@ietf.org; Thu, 25 Apr 2002 17:45:02 -0400 (EDT)
Received: from ietf.org (odin.ietf.org [10.27.2.28]) by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id RAA22396 for <all-ietf@loki.ietf.org>; Thu, 25 Apr 2002 17:29:24 -0400 (EDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA06750; Thu, 25 Apr 2002 17:29:21 -0400 (EDT)
Message-Id: <200204252129.RAA06750@ietf.org>
To: IETF-Announce:;
Cc: RFC Editor <rfc-editor@isi.edu>
Cc: Internet Architecture Board <iab@isi.edu>
From: The IESG <iesg-secretary@ietf.org>
Subject: Protocol Action: A Transient Prefix for Identifying Profiles under Development by the Working Groups of the IETF to BCP
Date: Thu, 25 Apr 2002 17:29:21 -0400
Sender: scoya@cnri.reston.va.us
The IESG has approved the Internet-Draft 'A Transient Prefix for Identifying Profiles under Development by the Working Groups of the IETF' <draft-mrose-beep-transientid-02.txt> as a BCP. This has been reviewed in the IETF but is not the product of an IETF Working Group. The IESG contact persons are Ned Freed and Patrik Faltstrom Technical Summary Each profile in The Blocks Extensible Exchange Protocol is identified by a URI. If the BEEP profile appears on the standards-track [3], then the IANA is responsible for assigning the URI associated with the BEEP profile at the time of publication of the RFC. 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. Further, it is desirable that the transient identifier be associated with the working group. Working Group Summary The document is not the product of any working group in the IETF, but has been reviewed on the mailing lists which discuss the Beep protocol. Protocol Quality The document has been reviewed for the IESG by Patrik Faltstrom.