BEEP Transport

["Hollenbeck, Scott" <shollenbeck@verisign.com>]

I've just taken a cursory glance at beep-00, and I have a few
questions/comments:

BEEP does not have an explicit dependency on TCP, though this draft
describes TCP connectivity.  Would it be possible to clarify either a
specific requirement for TCP transport (expanding on the reference to
RFC3081), or note that protocols other than TCP are possible and that this
is just one possible way of moving data around?

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).

Rather than using Content-Type: text/xml, the base EPP spec defines an
application/epp+xml media type.  I'd like to recommend use of this media
type instead of text/xml.

The XML Schema references are outdated.  The current references should point
here:

http://www.w3.org/TR/xmlschema-1/, and
http://www.w3.org/TR/xmlschema-2/

<Scott/>