From beepwg-admin@lists.beepcore.org  Mon Sep 10 11:45:01 2001
Received: from qawoor.dbc.mtview.ca.us (ppp-63-207-83-131.ded.pacbell.net [63.207.83.131])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA19040
	for <beep-archive@odin.ietf.org>; Mon, 10 Sep 2001 11:45:00 -0400 (EDT)
Received: from qawoor.dbc.mtview.ca.us (localhost [127.0.0.1])
	by qawoor.dbc.mtview.ca.us (8.11.3/8.11.5) with ESMTP id f8AFh7i21214;
	Mon, 10 Sep 2001 08:44:27 -0700 (PDT)
Received: from miz-mishtal.dbc.mtview.ca.us (miz-mishtal.dbc.mtview.ca.us [63.207.83.130])
	by qawoor.dbc.mtview.ca.us (8.11.3/8.11.5) with ESMTP id f8AFg6i21201
	for <beepwg@lists.beepcore.org>; Mon, 10 Sep 2001 08:42:06 -0700 (PDT)
Received: from FATORA (dhcp141 [63.207.83.141] (may be forged))
	by miz-mishtal.dbc.mtview.ca.us (8.11.0+3.3W/8.11.0) with SMTP id f8AFfoc07204;
	Mon, 10 Sep 2001 08:41:50 -0700 (PDT)
Message-ID: <129f01c13a0f$48a0e930$8d53cf3f@FATORA>
From: "Marshall T. Rose" <mrose+mtr.netnews@dbc.mtview.ca.us>
To: <beepwg@lists.beepcore.org>
Cc: "Marshall Rose" <mrose@dbc.mtview.ca.us>
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_NextPart_000_129C_01C139D4.9BC95EC0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Subject: [BEEPwg] BCP under consideration
Sender: beepwg-admin@lists.beepcore.org
Errors-To: beepwg-admin@lists.beepcore.org
X-BeenThere: beepwg@lists.beepcore.org
X-Mailman-Version: 2.0.6
Precedence: bulk
List-Help: <mailto:beepwg-request@lists.beepcore.org?subject=help>
List-Post: <mailto:beepwg@lists.beepcore.org>
List-Subscribe: <http://lists.beepcore.org/mailman/listinfo/beepwg>,
	<mailto:beepwg-request@lists.beepcore.org?subject=subscribe>
List-Id: Mailing list for the IETF's BEEP working group <beepwg.lists.beepcore.org>
List-Unsubscribe: <http://lists.beepcore.org/mailman/listinfo/beepwg>,
	<mailto:beepwg-request@lists.beepcore.org?subject=unsubscribe>
List-Archive: <http://lists.beepcore.org/pipermail/beepwg/>
Date: Mon, 10 Sep 2001 08:43:05 -0700

This is a multi-part message in MIME format.

------=_NextPart_000_129C_01C139D4.9BC95EC0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

the ADs for the Applications Area of the IETF have asked me to draw your
attention to the following internet-draft. they are considering using it as
the basis for a BCP for working groups developing BEEP profiles. your
comments are welcome.

the HTML version is at:
http://www.beepcore.org/beepcore/docs/beep-transientid.jsp

/mtr


------=_NextPart_000_129C_01C139D4.9BC95EC0
Content-Type: message/rfc822;
	name="I-D ACTION_draft-mrose-beep-transientid-00.txt.eml"
Content-Disposition: attachment;
	filename="I-D ACTION_draft-mrose-beep-transientid-00.txt.eml"

Delivery-Date: Mon, 10 Sep 2001 05:27:04 -0700
Received: from loki.ietf.org (loki.ietf.org [132.151.1.177])
	by miz-mishtal.dbc.mtview.ca.us (8.11.0+3.3W/8.11.0) with ESMTP id f8ACQqc06778
	for <mrose+internet.ietf.announce@DBC.MTVIEW.CA.US>; Mon, 10 Sep 2001 05:26:52 -0700 (PDT)
Received: (from adm@localhost)
	by loki.ietf.org (8.9.1b+Sun/8.9.1) id HAA28363
	for ietf-123-outbound.10@ietf.org; Mon, 10 Sep 2001 07:05:01 -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 GAA28243
	for <all-ietf@loki.ietf.org>; Mon, 10 Sep 2001 06:54:05 -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 GAA08421
	for <all-ietf@ietf.org>; Mon, 10 Sep 2001 06:54:04 -0400 (EDT)
Message-Id: <200109101054.GAA08421@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-mrose-beep-transientid-00.txt
Date: Mon, 10 Sep 2001 06:54:04 -0400
Sender: nsyracus@cnri.reston.va.us

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.


	Title		: A Transient Prefix for Identifying Profiles under 
                          Development by the Working Groups of the IETF
	Author(s)	: M. Rose
	Filename	: draft-mrose-beep-transientid-00.txt
	Pages		: 5
	Date		: 07-Sep-01
	
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.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-mrose-beep-transientid-00.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-mrose-beep-transientid-00.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-mrose-beep-transientid-00.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<20010907120426.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-mrose-beep-transientid-00.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-mrose-beep-transientid-00.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<20010907120426.I-D@ietf.org>

--OtherAccess--

--NextPart--



------=_NextPart_000_129C_01C139D4.9BC95EC0--

_______________________________________________
BEEPwg mailing list
BEEPwg@lists.beepcore.org
http://lists.beepcore.org/mailman/listinfo/beepwg


From beepwg-admin@lists.beepcore.org  Mon Sep 10 14:15:17 2001
Received: from qawoor.dbc.mtview.ca.us (ppp-63-207-83-131.ded.pacbell.net [63.207.83.131])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA25520
	for <beep-archive@odin.ietf.org>; Mon, 10 Sep 2001 14:15:16 -0400 (EDT)
Received: from qawoor.dbc.mtview.ca.us (localhost [127.0.0.1])
	by qawoor.dbc.mtview.ca.us (8.11.3/8.11.5) with ESMTP id f8AIE2i21865;
	Mon, 10 Sep 2001 11:15:22 -0700 (PDT)
Received: from dfw-smtpout4.email.verio.net (dfw-smtpout4.email.verio.net [129.250.36.44])
	by qawoor.dbc.mtview.ca.us (8.11.3/8.11.5) with ESMTP id f8AIDFi21853
	for <beepwg@lists.beepcore.org>; Mon, 10 Sep 2001 11:13:15 -0700 (PDT)
Received: from [129.250.38.63] (helo=dfw-mmp3.email.verio.net)
	by dfw-smtpout4.email.verio.net with esmtp
	id 15gVZa-0006RS-00
	for beepwg@lists.beepcore.org; Mon, 10 Sep 2001 18:14:18 +0000
Received: from [64.160.54.52] (helo=dan3480)
	by dfw-mmp3.email.verio.net with asmtp (110190536)
	id 15gVZZ-000554-00
	for beepwg@lists.beepcore.org; Mon, 10 Sep 2001 18:14:18 +0000
From: "Dan Kohn" <dan@dankohn.com>
To: <beepwg@lists.beepcore.org>
Subject: RE: [BEEPwg] BCP under consideration
Message-ID: <006601c13a24$678eccd0$6401a8c0@skymoonventures.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2627
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2526.0000
In-Reply-To: <129f01c13a0f$48a0e930$8d53cf3f@FATORA>
Sender: beepwg-admin@lists.beepcore.org
Errors-To: beepwg-admin@lists.beepcore.org
X-BeenThere: beepwg@lists.beepcore.org
X-Mailman-Version: 2.0.6
Precedence: bulk
List-Help: <mailto:beepwg-request@lists.beepcore.org?subject=help>
List-Post: <mailto:beepwg@lists.beepcore.org>
List-Subscribe: <http://lists.beepcore.org/mailman/listinfo/beepwg>,
	<mailto:beepwg-request@lists.beepcore.org?subject=subscribe>
List-Id: Mailing list for the IETF's BEEP working group <beepwg.lists.beepcore.org>
List-Unsubscribe: <http://lists.beepcore.org/mailman/listinfo/beepwg>,
	<mailto:beepwg-request@lists.beepcore.org?subject=unsubscribe>
List-Archive: <http://lists.beepcore.org/pipermail/beepwg/>
Date: Mon, 10 Sep 2001 11:14:16 -0700
Content-Transfer-Encoding: 7bit

This looks fine, but for one small comment on capitalization.  I believe
the W3C has a policy that although their URLs for documents may be mixed
case <http://www.w3.org/TR/SVG/intro.html#Namespace>, their namespace
URLs are always lowercase <http://www.w3.org/2000/svg>.  Since there's
no cost, it would seem worthwhile to maintain this notation.

So, in the document, <http://iana.org/beep/transient/provreg/EPP> would
become <http://iana.org/beep/transient/provreg/epp>.

Finally, it would be nice to have some comment on non working group BEEP
profiles, even if to say that they're on their own.

		- dan
--
Dan Kohn <mailto:dan@dankohn.com>
<http://www.dankohn.com/>  <tel:+1-650-327-2600>

-----Original Message-----
From: beepwg-admin@lists.beepcore.org
[mailto:beepwg-admin@lists.beepcore.org] On Behalf Of Marshall T. Rose
Sent: Monday, September 10, 2001 08:43
To: beepwg@lists.beepcore.org
Cc: Marshall Rose
Subject: [BEEPwg] BCP under consideration


the ADs for the Applications Area of the IETF have asked me to draw your
attention to the following internet-draft. they are considering using it
as
the basis for a BCP for working groups developing BEEP profiles. your
comments are welcome.

the HTML version is at:
http://www.beepcore.org/beepcore/docs/beep-transientid.jsp

/mtr


_______________________________________________
BEEPwg mailing list
BEEPwg@lists.beepcore.org
http://lists.beepcore.org/mailman/listinfo/beepwg


From beepwg-admin@lists.beepcore.org  Mon Sep 10 14:43:08 2001
Received: from qawoor.dbc.mtview.ca.us (ppp-63-207-83-131.ded.pacbell.net [63.207.83.131])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA26698
	for <beep-archive@odin.ietf.org>; Mon, 10 Sep 2001 14:43:08 -0400 (EDT)
Received: from qawoor.dbc.mtview.ca.us (localhost [127.0.0.1])
	by qawoor.dbc.mtview.ca.us (8.11.3/8.11.5) with ESMTP id f8AIg1i22025;
	Mon, 10 Sep 2001 11:43:21 -0700 (PDT)
Received: from monsoon.us.ny.firstrain.com ([208.198.42.246])
	by qawoor.dbc.mtview.ca.us (8.11.3/8.11.5) with ESMTP id f8AIf5i22006
	for <beepwg@lists.beepcore.org>; Mon, 10 Sep 2001 11:41:05 -0700 (PDT)
content-class: urn:content-classes:message
Subject: RE: [BEEPwg] BCP under consideration
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Message-ID: <C1C4A3C0FEE62A45A35BE7890264FF2715ECE7@monsoon.us.ny.firstrain.com>
X-MimeOLE: Produced By Microsoft Exchange V6.0.4712.0
Thread-Topic: [BEEPwg] BCP under consideration
Thread-Index: AcE6KMjyIn+0Nxf7Rpm06g1DjH2Pcg==
From: "Bob Wyman" <bobwyman@firstrain.com>
To: <beepwg@lists.beepcore.org>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by qawoor.dbc.mtview.ca.us id f8AIf5i22006
Sender: beepwg-admin@lists.beepcore.org
Errors-To: beepwg-admin@lists.beepcore.org
X-BeenThere: beepwg@lists.beepcore.org
X-Mailman-Version: 2.0.6
Precedence: bulk
List-Help: <mailto:beepwg-request@lists.beepcore.org?subject=help>
List-Post: <mailto:beepwg@lists.beepcore.org>
List-Subscribe: <http://lists.beepcore.org/mailman/listinfo/beepwg>,
	<mailto:beepwg-request@lists.beepcore.org?subject=subscribe>
List-Id: Mailing list for the IETF's BEEP working group <beepwg.lists.beepcore.org>
List-Unsubscribe: <http://lists.beepcore.org/mailman/listinfo/beepwg>,
	<mailto:beepwg-request@lists.beepcore.org?subject=unsubscribe>
List-Archive: <http://lists.beepcore.org/pipermail/beepwg/>
Date: Mon, 10 Sep 2001 14:45:38 -0400
Content-Transfer-Encoding: 8bit

Given a transient identifer of the form
"http://iana.org/beep/transient/XXXX/YYYY," where
    "http://iana.org/beep/transient" is defined by the
internet-draft/RFC, 
    "/xxxx" is defined by by the IETF Secretariat and 
    "/yyyy" is defined by the working group chair, 
it would seem reasonable to permit sub-groups of sub-efforts within the
working group to elaborate the identifier further to the right. Thus one
might indicate alternative variants or versions by adding another level
of hierarchy. 
	The following would then be permitted:
	http://iana.org/beep/transient/sacred/pdm
	http://iana.org/beep/transient/sacred/pdm/v1.4
	http://iana.org/beep/transient/sacred/pdm/janesproposal

	Since the specification in the internet draft says that "yyyy"
is merely a unique string, it would appear that the variants above would
all be permitted. However, I think it would make sense to explicitly
state that elaboration to the right can be arbitrarily long and would
indicate variants of the "yyyy" part.

		bob wyman
_______________________________________________
BEEPwg mailing list
BEEPwg@lists.beepcore.org
http://lists.beepcore.org/mailman/listinfo/beepwg


From beepwg-admin@lists.beepcore.org  Mon Sep 10 19:11:34 2001
Received: from qawoor.dbc.mtview.ca.us (ppp-63-207-83-131.ded.pacbell.net [63.207.83.131])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA05076
	for <beep-archive@odin.ietf.org>; Mon, 10 Sep 2001 19:11:32 -0400 (EDT)
Received: from qawoor.dbc.mtview.ca.us (localhost [127.0.0.1])
	by qawoor.dbc.mtview.ca.us (8.11.3/8.11.5) with ESMTP id f8AN9HO00392;
	Mon, 10 Sep 2001 16:10:37 -0700 (PDT)
Received: from miz-mishtal.dbc.mtview.ca.us (miz-mishtal.dbc.mtview.ca.us [63.207.83.130])
	by qawoor.dbc.mtview.ca.us (8.11.3/8.11.5) with ESMTP id f8AN8VO00380
	for <beepwg@lists.beepcore.org>; Mon, 10 Sep 2001 16:08:31 -0700 (PDT)
Received: from FATORA (dhcp141 [63.207.83.141] (may be forged))
	by miz-mishtal.dbc.mtview.ca.us (8.11.0+3.3W/8.11.0) with SMTP id f8AN8Ac08614;
	Mon, 10 Sep 2001 16:08:10 -0700 (PDT)
Message-ID: <177a01c13a4d$a3e2b100$8d53cf3f@FATORA>
From: "Marshall T. Rose" <mrose+mtr.netnews@dbc.mtview.ca.us>
To: "Dan Kohn" <dan@dankohn.com>, <beepwg@lists.beepcore.org>
Cc: "Marshall Rose" <mrose@dbc.mtview.ca.us>
References: <006601c13a24$678eccd0$6401a8c0@skymoonventures.com>
Subject: Re: [BEEPwg] BCP under consideration
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Sender: beepwg-admin@lists.beepcore.org
Errors-To: beepwg-admin@lists.beepcore.org
X-BeenThere: beepwg@lists.beepcore.org
X-Mailman-Version: 2.0.6
Precedence: bulk
List-Help: <mailto:beepwg-request@lists.beepcore.org?subject=help>
List-Post: <mailto:beepwg@lists.beepcore.org>
List-Subscribe: <http://lists.beepcore.org/mailman/listinfo/beepwg>,
	<mailto:beepwg-request@lists.beepcore.org?subject=subscribe>
List-Id: Mailing list for the IETF's BEEP working group <beepwg.lists.beepcore.org>
List-Unsubscribe: <http://lists.beepcore.org/mailman/listinfo/beepwg>,
	<mailto:beepwg-request@lists.beepcore.org?subject=unsubscribe>
List-Archive: <http://lists.beepcore.org/pipermail/beepwg/>
Date: Mon, 10 Sep 2001 16:09:27 -0700
Content-Transfer-Encoding: 7bit

> So, in the document, <http://iana.org/beep/transient/provreg/EPP> would
> become <http://iana.org/beep/transient/provreg/epp>.

how about adding this paragraph:

   Note that although the IETF hasn't established a practice with
   respect to the use of capitalization in URLs employed for namespace
   purposes, the W3C has a lowercase-only policy.  Working group chairs
   are encouraged to consider this when making assignments.


> Finally, it would be nice to have some comment on non working group BEEP
> profiles, even if to say that they're on their own.

how about adding this paragraph:

   Note that this practice does not apply to activities outside of working
   groups -- anyone able to assign a URL is capable of defining a URI
   for the purposes of identifying the BEEP profiles that they develop.


/mtr


_______________________________________________
BEEPwg mailing list
BEEPwg@lists.beepcore.org
http://lists.beepcore.org/mailman/listinfo/beepwg


From beepwg-admin@lists.beepcore.org  Mon Sep 10 19:18:14 2001
Received: from qawoor.dbc.mtview.ca.us (ppp-63-207-83-131.ded.pacbell.net [63.207.83.131])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA05267
	for <beep-archive@odin.ietf.org>; Mon, 10 Sep 2001 19:18:14 -0400 (EDT)
Received: from qawoor.dbc.mtview.ca.us (localhost [127.0.0.1])
	by qawoor.dbc.mtview.ca.us (8.11.3/8.11.5) with ESMTP id f8ANH1O00449;
	Mon, 10 Sep 2001 16:18:21 -0700 (PDT)
Received: from miz-mishtal.dbc.mtview.ca.us (miz-mishtal.dbc.mtview.ca.us [63.207.83.130])
	by qawoor.dbc.mtview.ca.us (8.11.3/8.11.5) with ESMTP id f8AN9HO00394
	for <beepwg@lists.beepcore.org>; Mon, 10 Sep 2001 16:09:17 -0700 (PDT)
Received: from FATORA (dhcp141 [63.207.83.141] (may be forged))
	by miz-mishtal.dbc.mtview.ca.us (8.11.0+3.3W/8.11.0) with SMTP id f8AN91c08619;
	Mon, 10 Sep 2001 16:09:01 -0700 (PDT)
Message-ID: <178001c13a4d$c20c18b0$8d53cf3f@FATORA>
From: "Marshall T. Rose" <mrose+mtr.netnews@dbc.mtview.ca.us>
To: "Bob Wyman" <bobwyman@firstrain.com>, <beepwg@lists.beepcore.org>
Cc: "Marshall Rose" <mrose@dbc.mtview.ca.us>
References: <C1C4A3C0FEE62A45A35BE7890264FF2715ECE7@monsoon.us.ny.firstrain.com>
Subject: Re: [BEEPwg] BCP under consideration
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Sender: beepwg-admin@lists.beepcore.org
Errors-To: beepwg-admin@lists.beepcore.org
X-BeenThere: beepwg@lists.beepcore.org
X-Mailman-Version: 2.0.6
Precedence: bulk
List-Help: <mailto:beepwg-request@lists.beepcore.org?subject=help>
List-Post: <mailto:beepwg@lists.beepcore.org>
List-Subscribe: <http://lists.beepcore.org/mailman/listinfo/beepwg>,
	<mailto:beepwg-request@lists.beepcore.org?subject=subscribe>
List-Id: Mailing list for the IETF's BEEP working group <beepwg.lists.beepcore.org>
List-Unsubscribe: <http://lists.beepcore.org/mailman/listinfo/beepwg>,
	<mailto:beepwg-request@lists.beepcore.org?subject=unsubscribe>
List-Archive: <http://lists.beepcore.org/pipermail/beepwg/>
Date: Mon, 10 Sep 2001 16:10:18 -0700
Content-Transfer-Encoding: 7bit

> Since the specification in the internet draft says that "yyyy"
> is merely a unique string, it would appear that the variants above would
> all be permitted. However, I think it would make sense to explicitly
> state that elaboration to the right can be arbitrarily long and would
> indicate variants of the "yyyy" part.

how about this change:

   Although the resulting URI must conform to the URI syntax, the "YYY"
   portion is otherwise arbitrary.  For example, it may contain a sub-
   hierarchy (e.g., "epp/1.0").

   For example,

       http://iana.org/beep/transient/provreg/epp/1.0
       http://iana.org/beep/transient/sacred/pdm

   might be assigned by the chairs of the "provreg" and "sacred" working
   groups, respectively.

/mtr


_______________________________________________
BEEPwg mailing list
BEEPwg@lists.beepcore.org
http://lists.beepcore.org/mailman/listinfo/beepwg


From beepwg-admin@lists.beepcore.org  Mon Sep 10 19:23:09 2001
Received: from qawoor.dbc.mtview.ca.us (ppp-63-207-83-131.ded.pacbell.net [63.207.83.131])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA05425
	for <beep-archive@odin.ietf.org>; Mon, 10 Sep 2001 19:23:09 -0400 (EDT)
Received: from qawoor.dbc.mtview.ca.us (localhost [127.0.0.1])
	by qawoor.dbc.mtview.ca.us (8.11.3/8.11.5) with ESMTP id f8ANM2O00495;
	Mon, 10 Sep 2001 16:23:22 -0700 (PDT)
Received: from monsoon.us.ny.firstrain.com ([208.198.42.246])
	by qawoor.dbc.mtview.ca.us (8.11.3/8.11.5) with ESMTP id f8ANI8O00458
	for <beepwg@lists.beepcore.org>; Mon, 10 Sep 2001 16:18:08 -0700 (PDT)
Subject: RE: [BEEPwg] BCP under consideration
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Message-ID: <C1C4A3C0FEE62A45A35BE7890264FF272B80B9@monsoon.us.ny.firstrain.com>
content-class: urn:content-classes:message
X-MimeOLE: Produced By Microsoft Exchange V6.0.4712.0
Thread-Topic: [BEEPwg] BCP under consideration
Thread-Index: AcE6TkYcXi9Nuvz5TvCfaYC1tSUQQQAAQPsA
From: "Bob Wyman" <bobwyman@firstrain.com>
To: "Marshall T. Rose" <mrose+mtr.netnews@dbc.mtview.ca.us>,
        <beepwg@lists.beepcore.org>
Cc: "Marshall Rose" <mrose@dbc.mtview.ca.us>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by qawoor.dbc.mtview.ca.us id f8ANI8O00458
Sender: beepwg-admin@lists.beepcore.org
Errors-To: beepwg-admin@lists.beepcore.org
X-BeenThere: beepwg@lists.beepcore.org
X-Mailman-Version: 2.0.6
Precedence: bulk
List-Help: <mailto:beepwg-request@lists.beepcore.org?subject=help>
List-Post: <mailto:beepwg@lists.beepcore.org>
List-Subscribe: <http://lists.beepcore.org/mailman/listinfo/beepwg>,
	<mailto:beepwg-request@lists.beepcore.org?subject=subscribe>
List-Id: Mailing list for the IETF's BEEP working group <beepwg.lists.beepcore.org>
List-Unsubscribe: <http://lists.beepcore.org/mailman/listinfo/beepwg>,
	<mailto:beepwg-request@lists.beepcore.org?subject=unsubscribe>
List-Archive: <http://lists.beepcore.org/pipermail/beepwg/>
Date: Mon, 10 Sep 2001 19:22:43 -0400
Content-Transfer-Encoding: 8bit

I would be happy with the proposed change.

		bob wyman

-----Original Message-----
From: Marshall T. Rose [mailto:mrose+mtr.netnews@dbc.mtview.ca.us]
Sent: Monday, September 10, 2001 7:10 PM
To: Bob Wyman; beepwg@lists.beepcore.org
Cc: Marshall Rose
Subject: Re: [BEEPwg] BCP under consideration


> Since the specification in the internet draft says that "yyyy"
> is merely a unique string, it would appear that the variants above
would
> all be permitted. However, I think it would make sense to explicitly
> state that elaboration to the right can be arbitrarily long and would
> indicate variants of the "yyyy" part.

how about this change:

   Although the resulting URI must conform to the URI syntax, the "YYY"
   portion is otherwise arbitrary.  For example, it may contain a sub-
   hierarchy (e.g., "epp/1.0").

   For example,

       http://iana.org/beep/transient/provreg/epp/1.0
       http://iana.org/beep/transient/sacred/pdm

   might be assigned by the chairs of the "provreg" and "sacred" working
   groups, respectively.

/mtr


_______________________________________________
BEEPwg mailing list
BEEPwg@lists.beepcore.org
http://lists.beepcore.org/mailman/listinfo/beepwg


From beepwg-admin@lists.beepcore.org  Wed Sep 12 11:08:55 2001
Received: from qawoor.dbc.mtview.ca.us (ppp-63-207-83-131.ded.pacbell.net [63.207.83.131])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA24130
	for <beep-archive@odin.ietf.org>; Wed, 12 Sep 2001 11:08:49 -0400 (EDT)
Received: from qawoor.dbc.mtview.ca.us (localhost [127.0.0.1])
	by qawoor.dbc.mtview.ca.us (8.11.3/8.11.5) with ESMTP id f8CF65O22140;
	Wed, 12 Sep 2001 08:06:05 -0700 (PDT)
Received: from miz-mishtal.dbc.mtview.ca.us (miz-mishtal.dbc.mtview.ca.us [63.207.83.130])
	by qawoor.dbc.mtview.ca.us (8.11.3/8.11.5) with ESMTP id f8CF5pO22128
	for <beepwg@lists.beepcore.org>; Wed, 12 Sep 2001 08:05:51 -0700 (PDT)
Received: from FATORA (dhcp141 [63.207.83.141] (may be forged))
	by miz-mishtal.dbc.mtview.ca.us (8.11.0+3.3W/8.11.0) with SMTP id f8CF5Zc15645;
	Wed, 12 Sep 2001 08:05:35 -0700 (PDT)
Message-ID: <1f2f01c13b9c$92f91960$8d53cf3f@FATORA>
From: "Marshall T. Rose" <mrose+mtr.netnews@dbc.mtview.ca.us>
To: <beepwg@lists.beepcore.org>
Cc: "Marshall Rose" <mrose@dbc.mtview.ca.us>
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_NextPart_000_1F2C_01C13B61.E647DBA0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Subject: [BEEPwg] new version of proposed BCP
Sender: beepwg-admin@lists.beepcore.org
Errors-To: beepwg-admin@lists.beepcore.org
X-BeenThere: beepwg@lists.beepcore.org
X-Mailman-Version: 2.0.6
Precedence: bulk
List-Help: <mailto:beepwg-request@lists.beepcore.org?subject=help>
List-Post: <mailto:beepwg@lists.beepcore.org>
List-Subscribe: <http://lists.beepcore.org/mailman/listinfo/beepwg>,
	<mailto:beepwg-request@lists.beepcore.org?subject=subscribe>
List-Id: Mailing list for the IETF's BEEP working group <beepwg.lists.beepcore.org>
List-Unsubscribe: <http://lists.beepcore.org/mailman/listinfo/beepwg>,
	<mailto:beepwg-request@lists.beepcore.org?subject=unsubscribe>
List-Archive: <http://lists.beepcore.org/pipermail/beepwg/>
Date: Wed, 12 Sep 2001 08:07:00 -0700

This is a multi-part message in MIME format.

------=_NextPart_000_1F2C_01C13B61.E647DBA0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

-01 accomodates comments from dan and bob.

the HTML version is at:
http://www.beepcore.org/beepcore/docs/beep-transientid.jsp


------=_NextPart_000_1F2C_01C13B61.E647DBA0
Content-Type: message/rfc822;
	name="I-D ACTION_draft-mrose-beep-transientid-01.txt.eml"
Content-Disposition: attachment;
	filename="I-D ACTION_draft-mrose-beep-transientid-01.txt.eml"

Delivery-Date: Wed, 12 Sep 2001 05:47:00 -0700
Received: from loki.ietf.org (loki.ietf.org [132.151.1.177])
	by miz-mishtal.dbc.mtview.ca.us (8.11.0+3.3W/8.11.0) with ESMTP id f8CCkvc15361
	for <mrose+internet.ietf.announce@DBC.MTVIEW.CA.US>; Wed, 12 Sep 2001 05:46:57 -0700 (PDT)
Received: (from adm@localhost)
	by loki.ietf.org (8.9.1b+Sun/8.9.1) id HAA05386
	for ietf-123-outbound.10@ietf.org; Wed, 12 Sep 2001 07:15:01 -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 HAA05335
	for <all-ietf@loki.ietf.org>; Wed, 12 Sep 2001 07:12:07 -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 HAA17200
	for <all-ietf@ietf.org>; Wed, 12 Sep 2001 07:11:39 -0400 (EDT)
Message-Id: <200109121111.HAA17200@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-mrose-beep-transientid-01.txt
Date: Wed, 12 Sep 2001 07:11:39 -0400
Sender: nsyracus@cnri.reston.va.us

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.


	Title		: A Transient Prefix for Identifying Profiles under 
                          Development by the Working Groups of the IETF
	Author(s)	: M. Rose
	Filename	: draft-mrose-beep-transientid-01.txt
	Pages		: 6
	Date		: 11-Sep-01
	
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.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-mrose-beep-transientid-01.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-mrose-beep-transientid-01.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-mrose-beep-transientid-01.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<20010911131714.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-mrose-beep-transientid-01.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-mrose-beep-transientid-01.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<20010911131714.I-D@ietf.org>

--OtherAccess--

--NextPart--



------=_NextPart_000_1F2C_01C13B61.E647DBA0--

_______________________________________________
BEEPwg mailing list
BEEPwg@lists.beepcore.org
http://lists.beepcore.org/mailman/listinfo/beepwg


From beepwg-admin@lists.beepcore.org  Fri Sep 21 15:57:33 2001
Received: from qawoor.dbc.mtview.ca.us (ppp-63-207-83-131.ded.pacbell.net [63.207.83.131])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA05634
	for <beep-archive@odin.ietf.org>; Fri, 21 Sep 2001 15:57:28 -0400 (EDT)
Received: from qawoor.dbc.mtview.ca.us (localhost [127.0.0.1])
	by qawoor.dbc.mtview.ca.us (8.11.3/8.11.5) with ESMTP id f8LJrDQ22493;
	Fri, 21 Sep 2001 12:53:13 -0700 (PDT)
Received: from xomi.pair.com (xomi.pair.com [209.68.2.14])
	by qawoor.dbc.mtview.ca.us (8.11.3/8.11.5) with SMTP id f8LJqvQ22461
	for <beepwg@lists.beepcore.org>; Fri, 21 Sep 2001 12:52:57 -0700 (PDT)
Received: (qmail 34148 invoked by uid 3039); 21 Sep 2001 19:55:04 -0000
Received: from localhost (sendmail-bs@127.0.0.1)
  by localhost with SMTP; 21 Sep 2001 19:55:04 -0000
From: Gabe Wachob <gwachob@wachob.com>
X-Sender:  <gwachob@xomi.pair.com>
To: <beepwg@lists.beepcore.org>
Message-ID: <Pine.BSF.4.30.0109211240450.27848-100000@xomi.pair.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [BEEPwg] Question about SOAP/BEEP
Sender: beepwg-admin@lists.beepcore.org
Errors-To: beepwg-admin@lists.beepcore.org
X-BeenThere: beepwg@lists.beepcore.org
X-Mailman-Version: 2.0.6
Precedence: bulk
List-Help: <mailto:beepwg-request@lists.beepcore.org?subject=help>
List-Post: <mailto:beepwg@lists.beepcore.org>
List-Subscribe: <http://lists.beepcore.org/mailman/listinfo/beepwg>,
	<mailto:beepwg-request@lists.beepcore.org?subject=subscribe>
List-Id: Mailing list for the IETF's BEEP working group <beepwg.lists.beepcore.org>
List-Unsubscribe: <http://lists.beepcore.org/mailman/listinfo/beepwg>,
	<mailto:beepwg-request@lists.beepcore.org?subject=unsubscribe>
List-Archive: <http://lists.beepcore.org/pipermail/beepwg/>
Date: Fri, 21 Sep 2001 12:55:04 -0700 (PDT)

Eamon & Marshall-
	Sorry for getting you comments so late in the review process - I
didn't have bandwidth nor a direct interest in SOAP/BEEP when it was
originally published, but now I'm finding myself extremely interested in
this binding as it will be key to a client of my consulting company.

	In short, I don't see any real problems yet with the draft, and
nothing I say here I think would require any new edits. I just want to
clarify one thing:

What is the use of the "resource" attribute provided in the bootmsg
message? How is this related to the HTTP SOAPAction header, or HTTP URLs
one would see in the SOAP/HTTP binding?

Thanks

	-Gabe

_______________________________________________
BEEPwg mailing list
BEEPwg@lists.beepcore.org
http://lists.beepcore.org/mailman/listinfo/beepwg


From beepwg-admin@lists.beepcore.org  Sun Sep 23 00:29:03 2001
Received: from qawoor.dbc.mtview.ca.us (ppp-63-207-83-131.ded.pacbell.net [63.207.83.131])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA08956
	for <beep-archive@lists.ietf.org>; Sun, 23 Sep 2001 00:28:58 -0400 (EDT)
Received: from qawoor.dbc.mtview.ca.us (localhost [127.0.0.1])
	by qawoor.dbc.mtview.ca.us (8.11.3/8.11.5) with ESMTP id f8N4Q4Q03862;
	Sat, 22 Sep 2001 21:26:05 -0700 (PDT)
Received: from smtp2.san.rr.com (smtp2.san.rr.com [24.25.195.39])
	by qawoor.dbc.mtview.ca.us (8.11.3/8.11.5) with ESMTP id f8N4PFQ03845
	for <beepwg@lists.beepcore.org>; Sat, 22 Sep 2001 21:25:15 -0700 (PDT)
Received: from san.rr.com (66-75-151-160.san.rr.com [66.75.151.160])
	by smtp2.san.rr.com (8.11.4/8.11.4) with ESMTP id f8N4RZw18001
	for <beepwg@lists.beepcore.org>; Sat, 22 Sep 2001 21:27:35 -0700 (PDT)
Message-ID: <3BAD64B8.7ABA9BE6@san.rr.com>
From: Darren New <dnew@san.rr.com>
Organization: Boxes!
X-Mailer: Mozilla 4.77 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: beepwg@lists.beepcore.org
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: [BEEPwg] Tuning reset and buffered data
Sender: beepwg-admin@lists.beepcore.org
Errors-To: beepwg-admin@lists.beepcore.org
X-BeenThere: beepwg@lists.beepcore.org
X-Mailman-Version: 2.0.6
Precedence: bulk
List-Help: <mailto:beepwg-request@lists.beepcore.org?subject=help>
List-Post: <mailto:beepwg@lists.beepcore.org>
List-Subscribe: <http://lists.beepcore.org/mailman/listinfo/beepwg>,
	<mailto:beepwg-request@lists.beepcore.org?subject=subscribe>
List-Id: Mailing list for the IETF's BEEP working group <beepwg.lists.beepcore.org>
List-Unsubscribe: <http://lists.beepcore.org/mailman/listinfo/beepwg>,
	<mailto:beepwg-request@lists.beepcore.org?subject=unsubscribe>
List-Archive: <http://lists.beepcore.org/pipermail/beepwg/>
Date: Sat, 22 Sep 2001 21:27:36 -0700
Content-Transfer-Encoding: 7bit

If a BEEP library takes in buffers of data read from the socket, it
needs to either make sure it processes frames as they arrive while
awaiting a tuning reset, or it needs to be able to return unconsumed
data.

Think about TUNNEL. 

Outside        firewall           Inside
  ......... ..... .... ... ... .. ...
                   <------ ok -------
   <------ ok ------
   <------------new greeting-------->

If the beep library on "outside" gets both the OK from the firewall and
the start of the new greeting from "inside" in the same buffer, it needs
to deal with this. TLS is OK, because the machine sending "proceed"
waits to get data from the remote machine. TUNNEL is different, becaue
Inside can send the greeting before the OK has made it all the way to
Outside, and it may even wind up in the same IP datagram.

The solution is to either have "Outside" only read precisely to the end
of the frame when it knows a tuning profile is running, or to be able to
return the unused portions of any buffers that the socket handling
threads may have already read, so they can be passed on to the greeting
parser.

Just something I thought of.
-- 
Darren New 
San Diego, CA, USA (PST). Cryptokeys on demand.
                   Who is this Dr. Ibid anyway, 
                  and how does he know so much?
_______________________________________________
BEEPwg mailing list
BEEPwg@lists.beepcore.org
http://lists.beepcore.org/mailman/listinfo/beepwg


From beepwg-admin@lists.beepcore.org  Sun Sep 23 01:24:32 2001
Received: from qawoor.dbc.mtview.ca.us (ppp-63-207-83-131.ded.pacbell.net [63.207.83.131])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA10088
	for <beep-archive@lists.ietf.org>; Sun, 23 Sep 2001 01:24:32 -0400 (EDT)
Received: from qawoor.dbc.mtview.ca.us (localhost [127.0.0.1])
	by qawoor.dbc.mtview.ca.us (8.11.3/8.11.5) with ESMTP id f8N5M3Q04304;
	Sat, 22 Sep 2001 22:22:03 -0700 (PDT)
Received: from miz-mishtal.dbc.mtview.ca.us (miz-mishtal.dbc.mtview.ca.us [63.207.83.130])
	by qawoor.dbc.mtview.ca.us (8.11.3/8.11.5) with ESMTP id f8N5LZQ04292
	for <beepwg@lists.beepcore.org>; Sat, 22 Sep 2001 22:21:35 -0700 (PDT)
Received: from FATORA (dhcp141 [63.207.83.141] (may be forged))
	by miz-mishtal.dbc.mtview.ca.us (8.11.0+3.3W/8.11.0) with SMTP id f8N5LHc11757;
	Sat, 22 Sep 2001 22:21:18 -0700 (PDT)
Message-ID: <173e01c143ef$e6412bc0$8d53cf3f@FATORA>
From: "Marshall T. Rose" <mrose+mtr.netnews@dbc.mtview.ca.us>
To: "Gabe Wachob" <gwachob@wachob.com>, <beepwg@lists.beepcore.org>
Cc: "Marshall Rose" <mrose@dbc.mtview.ca.us>
References: <Pine.BSF.4.30.0109211240450.27848-100000@xomi.pair.com>
Subject: Re: [BEEPwg] Question about SOAP/BEEP
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Sender: beepwg-admin@lists.beepcore.org
Errors-To: beepwg-admin@lists.beepcore.org
X-BeenThere: beepwg@lists.beepcore.org
X-Mailman-Version: 2.0.6
Precedence: bulk
List-Help: <mailto:beepwg-request@lists.beepcore.org?subject=help>
List-Post: <mailto:beepwg@lists.beepcore.org>
List-Subscribe: <http://lists.beepcore.org/mailman/listinfo/beepwg>,
	<mailto:beepwg-request@lists.beepcore.org?subject=subscribe>
List-Id: Mailing list for the IETF's BEEP working group <beepwg.lists.beepcore.org>
List-Unsubscribe: <http://lists.beepcore.org/mailman/listinfo/beepwg>,
	<mailto:beepwg-request@lists.beepcore.org?subject=unsubscribe>
List-Archive: <http://lists.beepcore.org/pipermail/beepwg/>
Date: Sat, 22 Sep 2001 22:23:37 -0700
Content-Transfer-Encoding: 7bit

> What is the use of the "resource" attribute provided in the bootmsg
> message? How is this related to the HTTP SOAPAction header, or HTTP URLs
> one would see in the SOAP/HTTP binding?


hi. eamon may have a different answer, but here's what i think:

i don't think there necessarily has to be an algorithmic relationship.
here's why:

1. depending on who you talk to, SOAPAction is either a hint for the
processor or the firewall or ...

2. the use of an HTTP URL doesn't necessarily provide all the information
you need.

i view the soap.beep url scheme as more or less opaque: establish a beep
session to the hostpart, pass the rest as the resource attribute, and it
gets you to the soap processor you want to talk to...

/mtr




_______________________________________________
BEEPwg mailing list
BEEPwg@lists.beepcore.org
http://lists.beepcore.org/mailman/listinfo/beepwg


