RE: security requirements (was: Updating RFC 2617 (HTTP Digest) to use UTF-8)

It's what those words mean.

To say what you mean, then a protocol spec says that when a client sends
X, it MUST respond with Y -- it does not say that X and Y are
mandatory-to-implement.


-----Original Message-----
From: ietf-http-wg-request@w3.org [mailto:ietf-http-wg-request@w3.org]
On Behalf Of Robert Sayre
Sent: Saturday, November 04, 2006 4:22 PM
To: Paul Leach
Cc: Henrik Nordstrom; HTTP Working Group
Subject: Re: security requirements (was: Updating RFC 2617 (HTTP Digest)
to use UTF-8)


On 11/4/06, Paul Leach <paulle@windows.microsoft.com> wrote:
>
> That's because making a protocol feature mandatory-to-implement does
NOT
> make it mandatory to configure.

That's not a meaningful distinction on the Internet.

-- 

Robert Sayre