W3C home > Mailing lists > Public > public-html@w3.org > January 2009

Re: Origin IETF draft

From: Adam Barth <w3c@adambarth.com>
Date: Mon, 19 Jan 2009 12:49:14 -0800
Message-ID: <7789133a0901191249s1b0a6b27vf912315f13ae9d16@mail.gmail.com>
To: Larry Masinter <masinter@adobe.com>
Cc: Arthur Barstow <art.barstow@nokia.com>, Anne van Kesteren <annevk@opera.com>, Sam Ruby <rubys@us.ibm.com>, "public-html@w3.org" <public-html@w3.org>

On Mon, Jan 19, 2009 at 9:58 AM, Larry Masinter <masinter@adobe.com> wrote:
> I'm willing to help with the "move to IETF" tasks and shepherding the documents through. (I'm not volunteering to edit the drafts but rather to assist those who have the action items.)

Thanks Larry.  I'm new to IETF process and would appreciate advice and help.  :)

> Personally, I prefer to use the RFC 2629 XML format for producing documents (see http://xml.resource.org/).

I am using this format to author the documents.  Is it customary to
also make that available to people reviewing the draft?

> Delegating things to the IETF means removing them from the HTML specification, not leaving them in pending their acceptance (or "blessing") by the IETF.

I believe there is another thread in this mailing list about this topic.

> If the "Origin" header requires additional guidance on when it should or shouldn't be used, then that also belongs in the IETF review.

At some point the spec will have to distinguish situations in which an
HTTP request is made on behalf of an origin (e.g., as a result of a
XMLHttpRequest) and situations in which an HTTP request is not made on
behalf of an origin (e.g., when the user types in the location bar).
This is difficult to spec precisely without a complete model of how
user agents work.  My current thinking is to leave this as an input
parameter to the spec and let clients of the spec (e.g., CORS and
HTML5) provide this information.  In that sense, the HTML spec will
likely provide "guidance" about sending the header.

> "Writing an internet draft" is merely a first step in getting IETF approval

Indeed.

Adam
Received on Monday, 19 January 2009 20:51:31 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:16:28 GMT