
From plh@w3.org  Mon Apr  6 07:49:54 2009
Return-Path: <plh@w3.org>
X-Original-To: w3c-policy@core3.amsl.com
Delivered-To: w3c-policy@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C0E5E3A6926 for <w3c-policy@core3.amsl.com>; Mon,  6 Apr 2009 07:49:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.449
X-Spam-Level: 
X-Spam-Status: No, score=-9.449 tagged_above=-999 required=5 tests=[AWL=-1.150, BAYES_00=-2.599, MANGLED_LOAN=2.3, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZDUgKH-oUkin for <w3c-policy@core3.amsl.com>; Mon,  6 Apr 2009 07:49:54 -0700 (PDT)
Received: from homer.w3.org (ssh.w3.org [128.30.52.60]) by core3.amsl.com (Postfix) with ESMTP id BE3CB3A6C7E for <w3c-policy@apps.ietf.org>; Mon,  6 Apr 2009 07:49:49 -0700 (PDT)
Received: from [127.0.0.1] (homer.w3.org [128.30.52.30]) by homer.w3.org (Postfix) with ESMTP id 64D664EEBA; Mon,  6 Apr 2009 10:50:54 -0400 (EDT)
Subject: Requesting IESG Approval for the Media Type application/xslt+xml, application/xquery+xml, and application/xquery
From: Philippe Le Hegaret <plh@w3.org>
To: iesg@ietf.org
Content-Type: text/plain; charset=UTF-8
Organization: World Wide Web Consortium
Date: Mon, 06 Apr 2009 10:50:52 -0400
Message-Id: <1239029452.14860.32.camel@localhost>
Mime-Version: 1.0
X-Mailer: Evolution 2.22.3.1 
Content-Transfer-Encoding: 8bit
Cc: Liam Quin <liam@w3.org>, w3c-policy@apps.ietf.org, Dan Connolly <connolly@w3.org>, Carine Bournez <carine@w3.org>
X-BeenThere: w3c-policy@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of w3c-ietf policy issues <w3c-policy.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/w3c-policy>, <mailto:w3c-policy-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/w3c-policy>
List-Post: <mailto:w3c-policy@ietf.org>
List-Help: <mailto:w3c-policy-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/w3c-policy>, <mailto:w3c-policy-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Apr 2009 14:49:54 -0000

Dear IESG participants,

This message is to request approval for the registration of three media
types:
1.
 application/xslt+xml
 Appendix B.1 of "XSL Transformations (XSLT) Version 2.0"
 http://www.w3.org/TR/2007/REC-xslt20-20070123/#media-type-registration

2.
 application/xquery+xml
 Appendix C.2 of "XML Syntax for XQuery 1.0 (XQueryX)"
 http://www.w3.org/TR/2007/REC-xqueryx-20070123/#xqueryx-mime-registration

3.
 application/xquery
 Appendix G.2 of "XQuery 1.0: An XML Query Language"
 http://www.w3.org/TR/2007/REC-xquery-20070123/#id-registration-of-mime-type

This message follows the procedure described in the Media Type
Specifications and Registration Procedures, section 5.2, "IESG
Approval" [1]. The proposed media types were sent for preliminary
community review on January 17, 2007:

 http://www.alvestrand.no/pipermail/ietf-types/2007-January/001791.html

No comments were received during the review period on ietf-types.
Comments from Larry Masinter [2] were received on
public-qt-comments@w3.org and were resolved.

We believe the media types are ready for IESG approval.

Thank you, 

Philippe

[1] http://www.ietf.org/rfc/rfc4288.txt
[2] http://lists.w3.org/Archives/Public/public-qt-comments/2007Jan/0242.html
-- 
Philippe Le Hégaret, W3C Interaction Domain Leader
World Wide Web Consortium (W3C)
http://www.w3.org/People/LeHegaret/


From mnot@mnot.net  Mon Apr  6 18:25:44 2009
Return-Path: <mnot@mnot.net>
X-Original-To: w3c-policy@core3.amsl.com
Delivered-To: w3c-policy@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C65F73A6883 for <w3c-policy@core3.amsl.com>; Mon,  6 Apr 2009 18:25:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.486
X-Spam-Level: 
X-Spam-Status: No, score=-5.486 tagged_above=-999 required=5 tests=[AWL=-1.887, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wAYQL-X-WWgg for <w3c-policy@core3.amsl.com>; Mon,  6 Apr 2009 18:25:36 -0700 (PDT)
Received: from fallback-in1.mxes.net (fallback-out1.mxes.net [216.86.168.190]) by core3.amsl.com (Postfix) with ESMTP id 393FB3A6D37 for <w3c-policy@ietf.org>; Mon,  6 Apr 2009 18:25:31 -0700 (PDT)
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by fallback-in1.mxes.net (Postfix) with ESMTP id 084EE164893 for <w3c-policy@ietf.org>; Mon,  6 Apr 2009 21:26:36 -0400 (EDT)
Received: from [192.168.1.1] (unknown [209.131.62.115]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id D3F06D059F for <w3c-policy@ietf.org>; Mon,  6 Apr 2009 21:26:24 -0400 (EDT)
Message-Id: <9E4B7415-85C2-461A-84CD-552602B4626C@mnot.net>
From: Mark Nottingham <mnot@mnot.net>
To: W3C/IETF <w3c-policy@ietf.org>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v930.3)
Subject: DRAFT minutes from 13 March
Date: Tue, 7 Apr 2009 11:26:21 +1000
X-Mailer: Apple Mail (2.930.3)
X-BeenThere: w3c-policy@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of w3c-ietf policy issues <w3c-policy.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/w3c-policy>, <mailto:w3c-policy-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/w3c-policy>
List-Post: <mailto:w3c-policy@ietf.org>
List-Help: <mailto:w3c-policy-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/w3c-policy>, <mailto:w3c-policy-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Apr 2009 01:25:44 -0000

[ re-send with minor corrections. Unless I hear otherwise, will  
publish on public list in three days ]

IETF/W3C Liaison Meeting
13 Mar 2009

Attendees

Present
        DanC, Matt, lisa, Johnk, Sam, mnot, plh
Regrets
	TimBL
Chair
        mnot

Scribe
        Matt

Contents

   * [3]Topics
       1. [4]Action items
       2. [5]Content Transformation
       3. [6]Wiki page review
       4. [7]Geopriv
       5. [8]IETF 74
       6. [9]IETF HTML5 bar BOF
       7. [10]VoiceXML use of POST
       8. [11]draft-abarth-origin
       9. [12]origin
      10. [13]mime sniff
      11. [14]Other business
   * [15]Summary of Action Items


Action items

mnot: Draft of wiki, everyone okay with it?

<DanC> <[16]http://esw.w3.org/topic/IetfW3cLiaison>

   [16] http://esw.w3.org/topic/IetfW3cLiaison%3E

DanC: I tweaked it a bit.

lisa: I havent' looked yet.

Content Transformation

francois: You want an introduction to the CT guidelines, I take it.
... CT Proxies were introduced by mobile carriers to allow mobile
users to access the Web at large.
... In theory it's a good idea, but in practice... there are many
legacy servers that return errors whent hey don't know the UA, so
the proxies instead replace the UA string with a well known one to
trick
... the server into thinking they know who they are.
... But in the mobile world, the UA string is essential due to
fragmentation. Mobile content creators adapt the resource based on
the capabilties of the device found in the UA string.
... These proxies ruined carefully crafted content...

<francois> x-mobile-ua, x-device-user-agent, x-original-user-agent

francois: Now CT proxies provide the original UA string in a
separate header field. There was no real consensus, so each one came
up with their own strings, using X-...
... Now with this guideline we're trying to define some practices
that will bring some order back to the world.
... This way CT proxies can still add value for legacy pages, but
allow mobile developers to be happy.
... Current draft says to send the original UA agent, but if you
receive a response that doesn't look right, then send the request
again with the fake UA.
... That doesn't satisfy everyone... they also want to use a single
HTTP header field.
... There's no immediate benefit to adding another new header... so,
can we keep the X- prefix and how can we migrate?
... The X- header field is already deployed. How do we migrate to
not having it?

mnot: rfc 3864 describes the header field registration policies.
... I don't remember specifically if we completely disallow X-, but
I think from the way you describe it you might have a rationale to
grandfather it in.
... It's in wide use?

francois: How wide?

<lisa> Have you seen [17]http://www.ietf.org/rfc/rfc4236.txt ?

   [17] http://www.ietf.org/rfc/rfc4236.txt

mnot: 2 or more implementations deployed...

<DanC> (a search for "x-" in [18]http://tools.ietf.org/html/rfc3864
fails)

   [18] http://tools.ietf.org/html/rfc3864

mnot: I don't see anything in the rfc that says you can't use X-...
you could make the in use argument. You could also register
something without the X- prefix.

<plh> John Klensin

JcK: Even if you register the X- there's a non-trivial risk that
someone is using the same string with different semantics.
... It's worse in X- because it's been custom for others to come
along later and reuse them with a different meaning.

plh: They did say they'd consider something other than X- right? But
if there's another UA string in the headers, how do they name it,
etc?

mnot: The UA header does allow more than one value, it's a list of
values. That should be the first place to look.

DanC: X- doesn't occur in 3864, is that by design?

mnot: I don't recall.

DanC: The X-.. once their introduced, how do we get rid of them?
x-www-form... it's everywhere. How do we get rid of them?

mnot: Don't use them unless it's a private thing.

JcK: This is a 25+ year old argument that we keep going around on.
Only use it if it's extremely private, not on the public network.
Never use one of these... names are cheap, register one if you must
and if it doesn't work it goes unused.

DanC: Why put energy into discouraging it at all? Is it just wasted
breath?

JcK: Long arguments about this...

<DanC> (fyi... [19]http://www.mnot.net/blog/2009/02/18/x- "Stop it
with the X- Already!" )

   [19] http://www.mnot.net/blog/2009/02/18/x-

JcK: The private uses do have meaning, the key to registering these
things is providing a minimal description.
... If it's private, and I don't want the public to know what it is,
perhaps there's a justification there...
... RFC ???? took a different position than 2822, and 56?? took a
slightly different take on that...

mnot: While RFC [media types] says X- shouldn't be registered.

<DanC> (provisional registries are one of the best ways to mitigate
these problems, IMO)

JcK: Many of the authors of these RFCs have the wounds of it...

mnot: Does this clarify enough to make progress or add confusion?

DanC: Least cost seems to be to keep using X-.

mnot: Use a proper name, but if it hurts adoption or vendors scream,
then you could get it grandfathered in.

francois: I expect that we'll get some negative feedback from the
IETF and the w3c as well. If we have a strong use case we could
register the X- if need be.

mnot: HTTPbis can't give a formal recommendation, but we could get
someone to review the document.

francois: We did for the first draft already, and will for the
second one I imagine.

Wiki page review

[20]http://esw.w3.org/topic/IetfW3cLiaison

mnot: Any comments?

Geopriv

<plh> Matt: I've been encouraging the geo chairs to come up with a
formal reply.

<DanC> wow... this liaison statement is *still* pending?

<plh> Matt: it's taking time and I apologize for the delay

<plh> ... Richard Barnes was in attendance for the geo f2f meeting

<plh> ... came up with a consensus

<plh> ... updated the draft

<plh> ... planning to re-open this can of worms for the next draft

<plh> Mark: when will we receive a response?

<plh> Matt: was supposed to come up by last Friday

<DanC> (I got myself an android/G1 phone a week or so ago... so this
privacy stuff is now a real-world concern of mine. Maybe I'll take
another look.)

<plh> ACTION: Matt to follow up on geopriv liaison statement
[recorded in
[22]http://www.w3.org/2009/03/13-ietf-minutes.html#action01]

<plh> Plh: since the co-chair of geopriv attended the f2f meeting,
it was assumed that consensus obtained was enough to move forward

<plh> Lisa: Richard is now chair of the geopriv wg

<plh> Mark: we could cover recent changes in the IETF at the end

IETF 74

mnot: IETF 74 is next week.

lisa: There's a bof on XMPP
... There's a mail BOF.
... BOF on multi-participants online interactions, MMOX

<DanC> I'll be there, FYI.
[23]http://www.tripit.com/trip/show/id/1329957 arrive SFO Sun
mid-day, depart SFO mid-day Thu Mar 26

   [23] http://www.tripit.com/trip/show/id/1329957

lisa: Second Life, virtual world companies, etc, having a debate
about interoperability and use cases and such. MMOX lots of
interest.

<Zakim> DanC, you wanted to ask date time of MMOX

mnot: Tuesday 3:20-5.

<JcK> The mail bof could have been called "find old stuff that has
been lying around for years, is widely deployed and used, clean it
up, and advance it to Internet Standard". There should be few, if
any, substantive issues -- docs that raise substantive issues will
be taken off the agenda"

lisa: OAUTH bof should be interesting to W3C I assume. Work moving
quite well on list after quiet period during holidays. Getting
consensus on charter, and have new chairs and [scribe failure]
... IPR bof, copy right issues that have come up recently.
... bar bof on HTML5.
... Bi-directional HTTP, COMET, etc.

mnot: That's during the app area meeting?

lisa: Yes.

<lisa> APPAREA :
[24]http://www.ietf.org/proceedings/09mar/agenda/apparea.txt

<JcK> DanC: OAUTH is at 1300 Monday, Apps Area at 0900

lisa: The 2nd Life folks are interested in this bidirectional stuff
and claim they've got a different use case.

mnot: Are W3C people aware of copyright problems?

lisa: There's a sun rise problem...

DanC: The IETF note-well thing didn't cover that?

mnot: Doesn't transfer copyright.
... There's an implication on standards that are published... the
idea behind the change, I could be wrong, was that other standards
organizations could re-use IETF text. Because of the sunrise
problems they can't do that.

<JcK> If I can get into the conversation, I can explain this stuff
... am very much in the middle

mnot: e.g. link draft, I have pre-November 10th contributions with
Note Well...
... Changes in IESG?

<JcK> But folks claiming to speak for/be involved in the W3C are
very active in the conversations.

<mnot> [26]http://www.ietf.org/IESGmems.html

<scribe> ACTION: plh to add mnot to Policy admins [recorded in
[27]http://www.w3.org/2009/03/13-ietf-minutes.html#action02]

mnot: Changes are not reflected on that link.

lisa: The IETF mailing list for it...
... JcK now on IAB.
... There are other changes too.

mnot: The most relavent are in apps and RAI.

IETF HTML5 bar BOF

rubys: Only 10 people signed up so far, but may be more popular than
that.

lisa: IETF people are likely to not sign up on the wiki page.

mnot: More likely to just drop in.

lisa: Sitting room for 25 or so, but probably bigger than that.

mnot: Can we get the wiki updated with location info?

rubys: Someone who has more details can send it to me or update it
themselves.

<scribe> ACTION: rubys to update the HTML5 bar BOF page with
details. [recorded in
[29]http://www.w3.org/2009/03/13-ietf-minutes.html#action03]

lisa: I don't know which room is assigned. Wednesday?

rubys: Yes.

<DanC> [30]http://esw.w3.org/topic/IETF_HTML5_Meeting_March_2009

   [30] http://esw.w3.org/topic/IETF_HTML5_Meeting_March_2009

mnot: I see a lot of high level goals and a lot of concrete things
to look at.

rubys: Lots of issues we could talk about, not sure quite how to
keep things moving.

mnot: How much time?

rubys: 8pm until whenever.

mnot: Dinner before?
... We could go until 10 if we have the time.
... Is Ian coming? he's on the list.

rubys: He's told me he's coming, but then says to others he may not.

mnot: Anything we can do to prepare for this to make it successful?

DanC: Should be good. Chris Wilson not certain?

rubys: I think that's old data. I believe he's planning on being at
this and Web open (?).

<DanC> (what 7:30pm start time? "8pm Wednesday, March 25th")

lisa: The 7:30 start time is rgiht at the end of the plenary, so
some IETF people may not have had dinner.
... Room was reserved for 7:30...

mnot: Might it be worth meeting ahead of time?

VoiceXML use of POST

lisa: The IETF spec punted on interoperability questions by pointing
to the w3c spec.
... The VoiceXML stuff talks about GET and POST, but... tried to get
folks in IETF to write down stuff like this.

DanC: Not clear to me that both parties must support chunk transfer
encoding.

lisa: Re-inforcing what the HTTP spec actually requires is often
useful.
... It's worth re-iterating what's in the HTTP spec.

[31]http://lists.w3.org/Archives/Public/www-voice/2009JanMar/0014.ht
ml

   [31] http://lists.w3.org/Archives/Public/www-voice/2009JanMar/0014.html

lisa: Are redirects appropriate? etc. we're trying to set standards
for what the IETF standards must met when they use HTTP as a
transport.
... I sent mail and haven't gotten an answer yet.

mnot: You're talking about a profile of HTTP...

lisa: If we could find the right people we could get this written
down and referenced once.

mnot: Identify extensibility points, and which points we could have
variance across, etc. If there's something we could put into BIS it
might be useful.

[32]http://lists.w3.org/Archives/Public/www-voice/2009JanMar/0014.ht
ml

   [32] http://lists.w3.org/Archives/Public/www-voice/2009JanMar/0014.html

<DanC> matt, if you see mail like lisa's, please *reply* to confirm
receipt.

Matt: The chairs will be sending a response once they figure out
what it should be. Looking for clarifications on the first two
paragraphs and asking for review on the last paragraph.

<DanC> I think senders can wait a couple days when they send a
comment on a W3C WD, but more than a week is kinda off-putting

draft-abarth-origin

origin

mime sniff

<DanC> mnot: the feedback from the HTTP WG was "Use Referer" and the
question remains whether that suffices

mnot: Are we going to review this in HTTP bis was DanC's question.

<DanC> "The above algorithm is a willful violation of the HTTP

<DanC> specification."

mnot: It looked like they were specifying a mime-sniffing algorithm
for browsers on top of HTTP, but that we weren't going to
incorporate this into HTTP.

DanC: It's not on top of HTTP, it's in violation...

mnot: I think we'll have sufficient wiggle room in HTTP bis that
they could do this...

DanC: There's still some chatting to do?

mnot: That's my impression.

DanC: This is a huge hot button issue.

mnot: If they want it published as an IETF standard they're going to
need more consensus.

rubys: I am pretty confident they want to publish it as a standard.

DanC: I don't think they're breaking things, just writing down
what's broken already.

lisa: The way we deal with contentious things like this is to form
working groups. We don't have any other mechanism for reaching consensus
when there's such a substantial difference of opinion.
... We now have several such topics that could be worthy of a second
HTTP WG if we don't extend the current one.

DanC: And if no one shows up?

lisa: In a WG we have a way to make sure people play nicely. It's
where there is a lack of a WG that there's less order.

mnot: Getting to the point where there's agreement that there should
be a standard that describes what this thing describes and getting
to a charter is going to be difficult.

lisa: If there was a way forward recommended too that would be
great. A charter can have two deliverables, documenting what's there
and how to move forward...

DanC: Hixie spent 10 years trying to get browsers to follow the
spec, but the browsers would end up losing market share...
... Users will think the browser is broken and not the server.

<JcK> At the same time, some of those practices, however
well-established, can cause rather serious problems including
security ones... and there, behavior sometimes does change.

<DanC> yes, JcK, I think there's a pretty good argument on the other
side... it'll be tricky to get people to consider both sides

<lisa> yeah, sorry it was so confusing too

mnot: I fear in 10-12 years you're going to have to publish a media
type, and a 3 page algorithim on how to sniff it...

<JcK> There are pretty good arguments on both sides. The problem is,
indeed, to get people to consider both, rather than repeating the
same position over and over again.

mnot: I think it needs to be handled very carefully.
... Web socket protocol is totally different in that it's not trying
to document anything that's there, just something totally new.

Other business

mnot: Next meeting, 14th of May. No particular time.
... I'll chair the next two meetings.
... I'll be in Australia.

JcK: I'll be in Nairobi.

Summary of Action Items

[NEW] ACTION: Matt to follow up on geopriv liaison statement
[recorded in
[33]http://www.w3.org/2009/03/13-ietf-minutes.html#action01]
[NEW] ACTION: plh to add mnot to Policy admins [recorded in
[34]http://www.w3.org/2009/03/13-ietf-minutes.html#action02]
[NEW] ACTION: rubys to update the HTML5 bar BOF page with details.
[recorded in
[35]http://www.w3.org/2009/03/13-ietf-minutes.html#action03]

[End of minutes]


From mnot@mnot.net  Tue Apr 14 01:18:35 2009
Return-Path: <mnot@mnot.net>
X-Original-To: w3c-policy@core3.amsl.com
Delivered-To: w3c-policy@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7D83A3A6AC7 for <w3c-policy@core3.amsl.com>; Tue, 14 Apr 2009 01:18:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.278
X-Spam-Level: 
X-Spam-Status: No, score=-4.278 tagged_above=-999 required=5 tests=[AWL=-3.639, BAYES_00=-2.599, RCVD_IN_BL_SPAMCOP_NET=1.96]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jcYB1mzoy90g for <w3c-policy@core3.amsl.com>; Tue, 14 Apr 2009 01:18:34 -0700 (PDT)
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by core3.amsl.com (Postfix) with ESMTP id A41873A6A7E for <w3c-policy@ietf.org>; Tue, 14 Apr 2009 01:18:34 -0700 (PDT)
Received: from [192.168.1.1] (unknown [209.131.62.115]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id CEC84D05AE for <w3c-policy@ietf.org>; Tue, 14 Apr 2009 04:19:44 -0400 (EDT)
Message-Id: <40A7FECF-DC18-4D92-841A-8C82247F96A9@mnot.net>
From: Mark Nottingham <mnot@mnot.net>
To: W3C/IETF <w3c-policy@ietf.org>
Content-Type: text/plain; charset=US-ASCII; format=flowed
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v930.3)
Subject: Next call: 5/14
Date: Tue, 14 Apr 2009 18:19:41 +1000
X-Mailer: Apple Mail (2.930.3)
X-BeenThere: w3c-policy@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of w3c-ietf policy issues <w3c-policy.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/w3c-policy>, <mailto:w3c-policy-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/w3c-policy>
List-Post: <mailto:w3c-policy@ietf.org>
List-Help: <mailto:w3c-policy-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/w3c-policy>, <mailto:w3c-policy-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Apr 2009 08:18:35 -0000

Our next call is scheduled for:
   8pm US/Eastern
   5pm US/Pacific
   10am (Friday) Australia/Eastern

Agenda items now being accepted...

Cheers,

--
Mark Nottingham     http://www.mnot.net/


From plh@w3.org  Tue Apr 14 11:28:42 2009
Return-Path: <plh@w3.org>
X-Original-To: w3c-policy@core3.amsl.com
Delivered-To: w3c-policy@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6D72F28C1F4 for <w3c-policy@core3.amsl.com>; Tue, 14 Apr 2009 11:28:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.532
X-Spam-Level: 
X-Spam-Status: No, score=-8.532 tagged_above=-999 required=5 tests=[AWL=-0.533, BAYES_50=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NJSvJdv-mkc8 for <w3c-policy@core3.amsl.com>; Tue, 14 Apr 2009 11:28:41 -0700 (PDT)
Received: from homer.w3.org (ssh.w3.org [128.30.52.60]) by core3.amsl.com (Postfix) with ESMTP id 8B64B28C1F5 for <w3c-policy@ietf.org>; Tue, 14 Apr 2009 11:28:41 -0700 (PDT)
Received: from [127.0.0.1] (homer.w3.org [128.30.52.30]) by homer.w3.org (Postfix) with ESMTP id E59EC4EF8A; Tue, 14 Apr 2009 14:29:52 -0400 (EDT)
Subject: Re: Next call: 5/14
From: Philippe Le Hegaret <plh@w3.org>
To: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <40A7FECF-DC18-4D92-841A-8C82247F96A9@mnot.net>
References: <40A7FECF-DC18-4D92-841A-8C82247F96A9@mnot.net>
Content-Type: text/plain
Organization: World Wide Web Consortium
Date: Tue, 14 Apr 2009 14:29:48 -0400
Message-Id: <1239733788.6619.16.camel@localhost>
Mime-Version: 1.0
X-Mailer: Evolution 2.24.5 
Content-Transfer-Encoding: 7bit
Cc: W3C/IETF <w3c-policy@ietf.org>
X-BeenThere: w3c-policy@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of w3c-ietf policy issues <w3c-policy.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/w3c-policy>, <mailto:w3c-policy-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/w3c-policy>
List-Post: <mailto:w3c-policy@ietf.org>
List-Help: <mailto:w3c-policy-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/w3c-policy>, <mailto:w3c-policy-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Apr 2009 18:28:42 -0000

On Tue, 2009-04-14 at 18:19 +1000, Mark Nottingham wrote:
> Our next call is scheduled for:
>    8pm US/Eastern
>    5pm US/Pacific
>    10am (Friday) Australia/Eastern
> 
> Agenda items now being accepted...

Can we have an agenda item on status of CORS and Web Sockets? Larry
Masinter is rightfully concerned that we don't have enough liaison
between W3C and IETF on those specifications (developed in the W3C
WebApps Group). My understanding that we have a cross mailing list
related to Web sockets. I also saw a message from you asking the IETF to
review CORS as well.

I asked repeatedly our Geolocation folks to provide an answer to the
IESG message but I still didn't see anything coming out. There has been
various extra communications that happened since then, including
involving Vint Cerf and TimBL. I'm wondering how much relevant it still
is to ask them to provide such answer. I could certainly explain why the
presence of Richard Barnes at the W3C meeting led the Group to believe
that they could move forward and publish without further communication
with the IETF. It wasn't Richard's fault, since he did not say he was
representing the IESG at that meeting, but simply of a matter of false
assumptions on the W3C Group side I think. On the technical aspects
enumerated in the message, geopriv and our group have been over them
several times already, even if they haven't been resolved to the
satisfaction of the geopriv folks, as far as I understand the situation.
I could certainly ask the chairs of our group to join us if necessary
(one of them is located in Oslo, so the call time would probably be too
late for him).

Philippe



From mnot@mnot.net  Fri Apr 17 17:49:19 2009
Return-Path: <mnot@mnot.net>
X-Original-To: w3c-policy@core3.amsl.com
Delivered-To: w3c-policy@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5E54A3A6A38 for <w3c-policy@core3.amsl.com>; Fri, 17 Apr 2009 17:49:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.302
X-Spam-Level: 
X-Spam-Status: No, score=-4.302 tagged_above=-999 required=5 tests=[AWL=-3.663, BAYES_00=-2.599, RCVD_IN_BL_SPAMCOP_NET=1.96]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MLoVdh82UARJ for <w3c-policy@core3.amsl.com>; Fri, 17 Apr 2009 17:49:18 -0700 (PDT)
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by core3.amsl.com (Postfix) with ESMTP id 88F163A6AAD for <w3c-policy@ietf.org>; Fri, 17 Apr 2009 17:49:18 -0700 (PDT)
Received: from [192.168.1.1] (unknown [209.131.62.115]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id CED3BD0A2D; Fri, 17 Apr 2009 20:50:28 -0400 (EDT)
Message-Id: <15BE8817-5384-4209-8E4C-B2D01F63FCBE@mnot.net>
From: Mark Nottingham <mnot@mnot.net>
To: Philippe Le Hegaret <plh@w3.org>
In-Reply-To: <1239733788.6619.16.camel@localhost>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v930.3)
Subject: Re: Next call: 5/14
Date: Sat, 18 Apr 2009 10:50:26 +1000
References: <40A7FECF-DC18-4D92-841A-8C82247F96A9@mnot.net> <1239733788.6619.16.camel@localhost>
X-Mailer: Apple Mail (2.930.3)
Cc: W3C/IETF <w3c-policy@ietf.org>
X-BeenThere: w3c-policy@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of w3c-ietf policy issues <w3c-policy.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/w3c-policy>, <mailto:w3c-policy-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/w3c-policy>
List-Post: <mailto:w3c-policy@ietf.org>
List-Help: <mailto:w3c-policy-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/w3c-policy>, <mailto:w3c-policy-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 18 Apr 2009 00:49:19 -0000

On 15/04/2009, at 4:29 AM, Philippe Le Hegaret wrote:

> On Tue, 2009-04-14 at 18:19 +1000, Mark Nottingham wrote:
>> Our next call is scheduled for:
>>   8pm US/Eastern
>>   5pm US/Pacific
>>   10am (Friday) Australia/Eastern
>>
>> Agenda items now being accepted...
>
> Can we have an agenda item on status of CORS and Web Sockets? Larry
> Masinter is rightfully concerned that we don't have enough liaison
> between W3C and IETF on those specifications (developed in the W3C
> WebApps Group). My understanding that we have a cross mailing list
> related to Web sockets. I also saw a message from you asking the  
> IETF to
> review CORS as well.

Ack. The mailing list is:
   https://www.ietf.org/mailman/listinfo/hybi
its scope is the general area that WebSockets, Comet/Long Poll, etc.  
come into.


> I asked repeatedly our Geolocation folks to provide an answer to the
> IESG message but I still didn't see anything coming out. There has  
> been
> various extra communications that happened since then, including
> involving Vint Cerf and TimBL. I'm wondering how much relevant it  
> still
> is to ask them to provide such answer. I could certainly explain why  
> the
> presence of Richard Barnes at the W3C meeting led the Group to believe
> that they could move forward and publish without further communication
> with the IETF. It wasn't Richard's fault, since he did not say he was
> representing the IESG at that meeting, but simply of a matter of false
> assumptions on the W3C Group side I think. On the technical aspects
> enumerated in the message, geopriv and our group have been over them
> several times already, even if they haven't been resolved to the
> satisfaction of the geopriv folks, as far as I understand the  
> situation.
> I could certainly ask the chairs of our group to join us if necessary
> (one of them is located in Oslo, so the call time would probably be  
> too
> late for him).

I'll follow up and see if we need anything else.


--
Mark Nottingham     http://www.mnot.net/


From mnot@mnot.net  Fri Apr 17 17:50:25 2009
Return-Path: <mnot@mnot.net>
X-Original-To: w3c-policy@core3.amsl.com
Delivered-To: w3c-policy@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 344933A6A5C for <w3c-policy@core3.amsl.com>; Fri, 17 Apr 2009 17:50:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.25
X-Spam-Level: 
X-Spam-Status: No, score=-4.25 tagged_above=-999 required=5 tests=[AWL=-3.611,  BAYES_00=-2.599, RCVD_IN_BL_SPAMCOP_NET=1.96]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DqrtPJl-CP-F for <w3c-policy@core3.amsl.com>; Fri, 17 Apr 2009 17:50:24 -0700 (PDT)
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by core3.amsl.com (Postfix) with ESMTP id 833593A6A38 for <w3c-policy@ietf.org>; Fri, 17 Apr 2009 17:50:24 -0700 (PDT)
Received: from [192.168.1.1] (unknown [209.131.62.115]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 7CAE2D059F for <w3c-policy@ietf.org>; Fri, 17 Apr 2009 20:51:37 -0400 (EDT)
Message-Id: <1CE73FD1-4D21-4E5B-819A-6A1974AAFA7A@mnot.net>
From: Mark Nottingham <mnot@mnot.net>
To: W3C/IETF <w3c-policy@ietf.org>
In-Reply-To: <40A7FECF-DC18-4D92-841A-8C82247F96A9@mnot.net>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v930.3)
Subject: Re: Next call: 5/14
Date: Sat, 18 Apr 2009 10:51:35 +1000
References: <40A7FECF-DC18-4D92-841A-8C82247F96A9@mnot.net>
X-Mailer: Apple Mail (2.930.3)
X-BeenThere: w3c-policy@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of w3c-ietf policy issues <w3c-policy.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/w3c-policy>, <mailto:w3c-policy-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/w3c-policy>
List-Post: <mailto:w3c-policy@ietf.org>
List-Help: <mailto:w3c-policy-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/w3c-policy>, <mailto:w3c-policy-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 18 Apr 2009 00:50:25 -0000

One item I'd like to cover is the status of W3C TAG findings; it's  
been asserted that they carry some weight, both inside and outside of  
the W3C, but it's not clear what that weight is (at least from my  
understanding). Some clarification of this from the W3C side would be  
helpful.

Cheers,


On 14/04/2009, at 6:19 PM, Mark Nottingham wrote:

> Our next call is scheduled for:
>  8pm US/Eastern
>  5pm US/Pacific
>  10am (Friday) Australia/Eastern
>
> Agenda items now being accepted...
>
> Cheers,
>
> --
> Mark Nottingham     http://www.mnot.net/
>


--
Mark Nottingham     http://www.mnot.net/


From mnot@mnot.net  Thu Apr 30 22:06:45 2009
Return-Path: <mnot@mnot.net>
X-Original-To: w3c-policy@core3.amsl.com
Delivered-To: w3c-policy@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CF3813A6C05 for <w3c-policy@core3.amsl.com>; Thu, 30 Apr 2009 22:06:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.797
X-Spam-Level: 
X-Spam-Status: No, score=-3.797 tagged_above=-999 required=5 tests=[AWL=-3.798, BAYES_50=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qbmppCezXDa6 for <w3c-policy@core3.amsl.com>; Thu, 30 Apr 2009 22:06:44 -0700 (PDT)
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by core3.amsl.com (Postfix) with ESMTP id 91A623A6E2F for <w3c-policy@ietf.org>; Thu, 30 Apr 2009 22:06:30 -0700 (PDT)
Received: from [192.168.1.6] (unknown [118.208.158.227]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id B571AD0B7E for <w3c-policy@ietf.org>; Fri,  1 May 2009 01:07:52 -0400 (EDT)
Message-Id: <904D28A2-3106-4889-9E0C-7CF1C3F4764F@mnot.net>
From: Mark Nottingham <mnot@mnot.net>
To: W3C/IETF <w3c-policy@ietf.org>
Content-Type: text/plain; charset=WINDOWS-1252; format=flowed; delsp=yes
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Apple Message framework v930.3)
Subject: First agenda for 5/14
Date: Fri, 1 May 2009 15:07:50 +1000
X-Mailer: Apple Mail (2.930.3)
X-BeenThere: w3c-policy@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of w3c-ietf policy issues <w3c-policy.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/w3c-policy>, <mailto:w3c-policy-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/w3c-policy>
List-Post: <mailto:w3c-policy@ietf.org>
List-Help: <mailto:w3c-policy-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/w3c-policy>, <mailto:w3c-policy-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 May 2009 05:06:45 -0000

0) select scribe

1) review action items
ACTION: mnot to propose times for 7/16 liaison call
DONE: Matt to follow up on geopriv liaison statement
DONE: plh to add mnot to Policy admins
DONE: rubys to update the HTML5 bar BOF page with details.

2) Status of TAG findings [ Mark ]

3) Status of CORS [ PLH ]

4) Status of WebSockets [ PLH ]



Call details:
Thursday, 14 May  8pm US/Eastern  5pm US/Pacific  10am (Friday) =20
Australia/Eastern
=
<http://www.timeanddate.com/worldclock/fixedtime.html?month=3D5&day=3D14&y=
ear=3D2009&hour=3D20&min=3D0&sec=3D0&p1=3D43=20
 >
Zakim Bridge +1.617.761.6200 <tel:+1.617.761.6200>, conference 4383 =20
(=93IETF=94) [ tentative ]
IRC: irc.w3.org, port 6665  #ietf

Expected:
   TimBL, Lisa, Mark, Philippe, DanC, John Klensin, Sam Ruby
Regrets:

--
Mark Nottingham     http://www.mnot.net/


From mnot@mnot.net  Thu Apr 30 22:37:40 2009
Return-Path: <mnot@mnot.net>
X-Original-To: w3c-policy@core3.amsl.com
Delivered-To: w3c-policy@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 160EF3A6938 for <w3c-policy@core3.amsl.com>; Thu, 30 Apr 2009 22:37:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.747
X-Spam-Level: 
X-Spam-Status: No, score=-4.747 tagged_above=-999 required=5 tests=[AWL=-2.148, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6RGlROpHnfqI for <w3c-policy@core3.amsl.com>; Thu, 30 Apr 2009 22:37:38 -0700 (PDT)
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by core3.amsl.com (Postfix) with ESMTP id 837C33A67B7 for <w3c-policy@ietf.org>; Thu, 30 Apr 2009 22:37:38 -0700 (PDT)
Received: from [192.168.1.6] (unknown [118.208.158.227]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 6F1B4D05B0 for <w3c-policy@ietf.org>; Fri,  1 May 2009 01:38:59 -0400 (EDT)
Message-Id: <77EF8A9A-CA6B-4B62-8FE8-35F5B04DE7AF@mnot.net>
From: Mark Nottingham <mnot@mnot.net>
To: W3C/IETF <w3c-policy@ietf.org>
In-Reply-To: <904D28A2-3106-4889-9E0C-7CF1C3F4764F@mnot.net>
Content-Type: text/plain; charset=WINDOWS-1252; format=flowed; delsp=yes
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Apple Message framework v930.3)
Subject: Updated agenda for 5/14
Date: Fri, 1 May 2009 15:38:56 +1000
References: <904D28A2-3106-4889-9E0C-7CF1C3F4764F@mnot.net>
X-Mailer: Apple Mail (2.930.3)
X-BeenThere: w3c-policy@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of w3c-ietf policy issues <w3c-policy.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/w3c-policy>, <mailto:w3c-policy-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/w3c-policy>
List-Post: <mailto:w3c-policy@ietf.org>
List-Help: <mailto:w3c-policy-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/w3c-policy>, <mailto:w3c-policy-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 May 2009 05:37:40 -0000

0) select scribe

1) review action items
ACTION: mnot to propose times for 7/16 liaison call
DONE: Matt to follow up on geopriv liaison statement
DONE: plh to add mnot to Policy admins
DONE: rubys to update the HTML5 bar BOF page with details.
DONE: MNot to advertise new SI-HTTP/HiBi list =
<https://www.ietf.org/mailman/listinfo/hybi=20
 >
ACTION:  Dan to reformat "Hypertext References" work as an Internet =20
Draft
ACTION: Lisa to review Content-Type sniffing I-D
DONE: MNot to send a pointer to prior discussion on Origin header
DONE: Jonas to send an email with pointers and/or description of CORS =20=

to Mark Nottingham
ACTION: Meadhbh Hamrick (Infinity) to explore involving NIST in a =20
workshop
ACTION: Sam to work on reconciling the multiple uses of the MIME types

2) Status of TAG findings [ Mark ]

3) Status of CORS [ PLH ]
   <http://www.w3.org/TR/access-control/>

4) Status of WebSockets [ PLH ]
   =
<https://datatracker.ietf.org/drafts/draft-hixie-thewebsocketprotocol/=20=

 >

5) Link relation registry work [ Mark ]
   =
<https://datatracker.ietf.org/drafts/draft-nottingham-http-link-header/=20=

 >

6) RFC4329 - JavaScript Media Types (HTML5 is giving counter advice; =20
does it need an update?)
   <http://www.ietf.org/rfc/rfc4329.txt>
   <http://www.w3.org/Bugs/Public/show_bug.cgi?id=3D6684>

7) URI/IRI coordination [ John, Dan ]

8) Web Security Workshop
    See discussion at =
<http://esw.w3.org/topic/IETF_HTML5_Meeting_March_2009=20
 >

9) Future meetings


Call details:
Thursday, 14 May  8pm US/Eastern  5pm US/Pacific  10am (Friday) =20
Australia/Eastern
=
<http://www.timeanddate.com/worldclock/fixedtime.html?month=3D5&day=3D14&y=
ear=3D2009&hour=3D20&min=3D0&sec=3D0&p1=3D43=20
 >
Zakim Bridge +1.617.761.6200 <tel:+1.617.761.6200>, conference 4383 =20
(=93IETF=94) [ tentative ]
IRC: irc.w3.org, port 6665  #ietf

Expected:
  TimBL, Lisa, Alexey, Mark, Philippe, DanC, John Klensin, Sam Ruby
Regrets:

--
Mark Nottingham     http://www.mnot.net/

