To:
"Hollenbeck, Scott" <shollenbeck@verisign.com>
Cc:
"'ietf-provreg@cafax.se'" <ietf-provreg@cafax.se>
From:
Dave Crocker <dcrocker@brandenburg.com>
Date:
Tue, 04 Sep 2001 10:11:55 -0700
In-Reply-To:
<3CD14E451751BD42BA48AAA50B07BAD6C5F9DD@vsvapostal3.prod.netsol.com>
Sender:
owner-ietf-provreg@cafax.se
Subject:
Re: BEEP Transport
Scott, At 09:37 AM 9/4/2001, Hollenbeck, Scott wrote: >BEEP does not have an explicit dependency on TCP, though this draft >describes TCP connectivity. It certainly relies on a reliable, connection-oriented transport that delivers data in the order sent. >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; What do you mean vendor-specific URI, and how is it relevant to discussion of our use of BEEP? d/ ---------- Dave Crocker <mailto:dcrocker@brandenburg.com> Brandenburg InternetWorking <http://www.brandenburg.com> tel +1.408.246.8253; fax +1.408.273.6464