To:
"Hollenbeck, Scott" <shollenbeck@verisign.com>
Cc:
ietf-provreg@cafax.se
From:
Dave Crocker <dcrocker@brandenburg.com>
Date:
Tue, 20 Mar 2001 07:35:09 -0600
In-Reply-To:
<DF737E620579D411A8E400D0B77E671D750814@regdom-ex01.prod.netsol.com>
Sender:
owner-ietf-provreg@cafax.se
Subject:
RE: security in draft-ietf-provreg-epp-0.txt
At 07:13 AM 3/20/2001, Hollenbeck, Scott wrote:
>Requiring BEEP contradicts other requirements for transport independence.
I suspect there is some confusion between:
a technical characteristic -- ability to map the application
protocol to run over multiple transports, versus
an operational profile -- specification of a complete set of
features to be used for basic interoperability, including transport and
security mechanisms.
The former is good for extensibility. The latter is essential for initial use.
d/
----------
Dave Crocker <mailto:dcrocker@brandenburg.com>
Brandenburg InternetWorking <http://www.brandenburg.com>
tel: +1.408.246.8253; fax: +1.408.273.6464