Last call on mandatory issues

From: Josh Cohen (joshco@microsoft.com)
Date: Mon, May 18 1998


Message-ID: <8B57882C41A0D1118F7100805F9F68B50340A3D2@red-msg-45.dns.microsoft.com>
From: Josh Cohen <joshco@microsoft.com>
To: ietf-http-ext@w3.org
Date: Mon, 18 May 1998 10:04:56 -0700
Subject: Last call on mandatory issues

After the 5/8 conference call, we would like
to suggest that the following issues are ready for
last call.

This is a last call announcement.

1) End-to-end notion in Mandatory and HTTP/1.1 (END_TO_END)
3) Extension parameters in extension declarations (DECL_PARAMETERS)
5) Interactions with Expect in HTTP/1.1, rev 03 ()

Please review and comment.

1) Concensus was that the current working in Mandatory is correct. A
solution to the discussion was proposed to a) take out the current wording
in Mandatory and leave it "as defined in HTTP" and b) do one of the
following in order of preference:

     -	Make a plea to Larry and Jim that the notion of end-to-end
	is clarified in HTTP/1.1 spec as currently stated in Mandatory
     - Make a note in the (now yet written) extension guide lines
	discussing the floating notion of end-to-end.

Action: Henrik to talk to Larry and Jim.
Status: Ready for last call on mailing list

3) Extension parameters in extension declarations (DECL_PARAMETERS)

People are happy with the name space solution together with headers and
did not want another way of passing extension parameters. All unknown
extension parameters are for the mandatory extension mechanism itself and
*not* for the extension.

Status: Ready for last call on mailing list

5) Problem with expect is that it can't be enforced. It is semantically
close to (and completely contained by) the C-Opt header field: A hop-by-hop
header field with an optional extension. Difference is that Expect is a
request-only header field whereas C-Opt is a general header field. Should
Expect be deprecated in favor of C-Opt?

Action: Henrik to talk to talk to Larry and Jim.
Status: Ready for last call on mailing list