Re: BEEP Transport

Michael Mealling <michael@neonym.net> Wed, 05 September 2001 06:32 UTC

Return-Path: <owner-ietf-provreg@cafax.se>
Received: from nic.cafax.se (localhost [127.0.0.1]) by nic.cafax.se (8.12.0.Gamma0/8.12.0.Gamma0) with ESMTP id f856Wh0l000499 for <ietf-provreg-outgoing@nic.cafax.se>; Wed, 5 Sep 2001 08:32:43 +0200 (MEST)
Received: by nic.cafax.se (8.12.0.Gamma0/8.12.0.Beta17) id f856WglX000498 for ietf-provreg-outgoing; Wed, 5 Sep 2001 08:32:42 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-ietf-provreg@cafax.se using -f
Received: from naptop.autonomica.se (flaptop.liman.sunet.se [193.10.90.102]) by nic.cafax.se (8.12.0.Gamma0/8.12.0.Gamma0) with ESMTP id f856Wd0l000493 for <ietf-provreg@cafax.se>; Wed, 5 Sep 2001 08:32:39 +0200 (MEST)
Received: by naptop.autonomica.se (8.12.0.Beta1/8.12.0.Beta1) id f856WlKw001051 for ietf-provreg@cafax.se; Wed, 5 Sep 2001 08:32:47 +0200 (MEST)
Received: from bailey.dscga.com (bailey.dscga.com [198.78.9.11]) by nic.cafax.se (8.12.0.Gamma0/8.12.0.Gamma0) with ESMTP id f84KNl0l026586 for <ietf-provreg@cafax.se>; Tue, 4 Sep 2001 22:23:48 +0200 (MEST)
Received: (from michael@localhost) by bailey.dscga.com (8.9.1/) id QAA01370; Tue, 4 Sep 2001 16:18:32 -0400 (EDT)
Date: Tue, 04 Sep 2001 16:18:32 -0400
From: Michael Mealling <michael@neonym.net>
To: "Marshall T. Rose" <mrose+mtr.netnews@dbc.mtview.ca.us>
Cc: "Hollenbeck, Scott" <shollenbeck@verisign.com>, ietf-provreg@cafax.se, Marshall Rose <mrose@dbc.mtview.ca.us>
Subject: Re: BEEP Transport
Message-ID: <20010904161832.L14430@bailey.dscga.com>
Reply-To: Michael Mealling <michael@neonym.net>
References: <3CD14E451751BD42BA48AAA50B07BAD6C5F9DD@vsvapostal3.prod.netsol.com> <02e101c13566$9c000d70$8d53cf3f@FATORA>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
User-Agent: Mutt/1.1.2i
In-Reply-To: <02e101c13566$9c000d70$8d53cf3f@FATORA>; from mrose+mtr.netnews@dbc.mtview.ca.us on Tue, Sep 04, 2001 at 10:25:35AM -0700
Sender: owner-ietf-provreg@cafax.se
Precedence: bulk

On Tue, Sep 04, 2001 at 10:25:35AM -0700, Marshall T. Rose wrote:
> > I believe it completely inappropriate for a WG draft to define a profile
> > using vendor-specific URIs.  I'm not aware of any IETF document that
> > describes IETF-standard BEEP profile definition procedures; does such a
> > document exist?  Perhaps one is needed if not, but in the mean time I
> think
> > it would be better to expand on the xml.resource.org precedent used by
> other
> > profiles described in IETF WG documents (such as those defined for TLS and
> > SASL).
> 
> hi. i don't think it will be difficult to set-up a work-in-progress prefix
> for beep profiles that are under development. i'll start moving on that.
> 
> a few working group have been using the xml.resource.org thing as a
> place-holder and no one on the iesg has objected, so i think you're safe in
> provreg to use that until the work-in-progress thing is set-up...

I've have two drafts that are relevent to this:

draft-mealling-iana-urn-01.txt
"An IETF URN Sub-namespace for Registered Protocol Parameters"

and

"The IETF XML Registry"
draft-mealling-iana-xmlns-registry-02.txt

If you want I can add a section that deals with creating temporary URIs
since it will be an issue with the URN namespace anyway...

-MM

-- 
--------------------------------------------------------------------------------
Michael Mealling	|      Vote Libertarian!       | urn:pin:1
michael@neonym.net      |                              | http://www.neonym.net