
From mnot@mnot.net  Mon Apr  2 12:34:25 2012
Return-Path: <mnot@mnot.net>
X-Original-To: w3c-policy@ietfa.amsl.com
Delivered-To: w3c-policy@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C94A21F86FA for <w3c-policy@ietfa.amsl.com>; Mon,  2 Apr 2012 12:34:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.599
X-Spam-Level: 
X-Spam-Status: No, score=-105.599 tagged_above=-999 required=5 tests=[AWL=-3.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id McGEiDWcJXa3 for <w3c-policy@ietfa.amsl.com>; Mon,  2 Apr 2012 12:34:24 -0700 (PDT)
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by ietfa.amsl.com (Postfix) with ESMTP id 1473721F86F6 for <w3c-policy@ietf.org>; Mon,  2 Apr 2012 12:34:20 -0700 (PDT)
Received: from [10.4.80.59] (unknown [74.205.24.231]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 7080450A5D for <w3c-policy@ietf.org>; Mon,  2 Apr 2012 15:34:14 -0400 (EDT)
From: Mark Nottingham <mnot@mnot.net>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Subject: For our next agenda
Date: Mon, 2 Apr 2012 15:34:13 -0400
References: <4F759780.1060501@gmx.de>
To: W3C/IETF <w3c-policy@ietf.org>
Message-Id: <E7CB3D17-4C60-4210-A7EA-32C2E69EB788@mnot.net>
Mime-Version: 1.0 (Apple Message framework v1257)
X-Mailer: Apple Mail (2.1257)
X-BeenThere: w3c-policy@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Administration of the W3C/IETF liaison <w3c-policy.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 02 Apr 2012 19:34:25 -0000

Begin forwarded message:

> 	http://trac.tools.ietf.org/wg/iri/trac/ticket/123
> 
> 	https://www.w3.org/html/wg/tracker/issues/189



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





From plh@w3.org  Tue Apr  3 12:42:03 2012
Return-Path: <plh@w3.org>
X-Original-To: w3c-policy@ietfa.amsl.com
Delivered-To: w3c-policy@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DAFF221F8548 for <w3c-policy@ietfa.amsl.com>; Tue,  3 Apr 2012 12:42:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wAokdd6sMFRs for <w3c-policy@ietfa.amsl.com>; Tue,  3 Apr 2012 12:42:03 -0700 (PDT)
Received: from jay.w3.org (ssh.w3.org [128.30.52.60]) by ietfa.amsl.com (Postfix) with ESMTP id 391F821F8541 for <w3c-policy@ietf.org>; Tue,  3 Apr 2012 12:42:03 -0700 (PDT)
Received: from 30-5-135.wireless.csail.mit.edu ([128.30.5.135]) by jay.w3.org with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.69) (envelope-from <plh@w3.org>) id 1SF9c9-0005Cd-TW; Tue, 03 Apr 2012 15:42:01 -0400
Subject: Re: For our next agenda
From: Philippe Le Hegaret <plh@w3.org>
To: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <E7CB3D17-4C60-4210-A7EA-32C2E69EB788@mnot.net>
References: <4F759780.1060501@gmx.de> <E7CB3D17-4C60-4210-A7EA-32C2E69EB788@mnot.net>
Content-Type: text/plain; charset="UTF-8"
Organization: World Wide Web Consortium
Date: Tue, 03 Apr 2012 15:41:56 -0400
Message-ID: <1333482116.12007.262.camel@chacal>
Mime-Version: 1.0
X-Mailer: Evolution 2.28.3 
Content-Transfer-Encoding: 7bit
Cc: "Michael\(tm\) Smith" <mike@w3.org>, W3C/IETF <w3c-policy@ietf.org>
X-BeenThere: w3c-policy@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Administration of the W3C/IETF liaison <w3c-policy.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 03 Apr 2012 19:42:04 -0000

On Mon, 2012-04-02 at 15:34 -0400, Mark Nottingham wrote:
> 
> Begin forwarded message:
> 
> > 	http://trac.tools.ietf.org/wg/iri/trac/ticket/123
> > 
> > 	https://www.w3.org/html/wg/tracker/issues/189

ok, I started loading the context on this one.

Note that the HTML Working Group has two change proposals around this
one:
 http://lists.w3.org/Archives/Public/public-html/2012Feb/0272.html
 http://www.w3.org/html/wg/wiki/User:Eoconnor/ISSUE-189

Both proposals received feedback from the Chairs:
 http://lists.w3.org/Archives/Public/public-html/2012Mar/0739.html

Philippe


From stpeter@stpeter.im  Thu Apr 12 14:22:41 2012
Return-Path: <stpeter@stpeter.im>
X-Original-To: w3c-policy@ietfa.amsl.com
Delivered-To: w3c-policy@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 64EEF21F86F6 for <w3c-policy@ietfa.amsl.com>; Thu, 12 Apr 2012 14:22:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.658
X-Spam-Level: 
X-Spam-Status: No, score=-102.658 tagged_above=-999 required=5 tests=[AWL=-0.059, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Uu0Rfkk2gxfW for <w3c-policy@ietfa.amsl.com>; Thu, 12 Apr 2012 14:22:40 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 3ED3F21F86F2 for <w3c-policy@ietf.org>; Thu, 12 Apr 2012 14:22:31 -0700 (PDT)
Received: from [64.101.72.157] (unknown [64.101.72.157]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id A99F240058; Thu, 12 Apr 2012 15:36:25 -0600 (MDT)
Message-ID: <4F874795.20703@stpeter.im>
Date: Thu, 12 Apr 2012 15:22:29 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:11.0) Gecko/20120327 Thunderbird/11.0.1
MIME-Version: 1.0
To: Philippe Le Hegaret <plh@w3.org>
Subject: Re: For our next agenda
References: <4F759780.1060501@gmx.de> <E7CB3D17-4C60-4210-A7EA-32C2E69EB788@mnot.net> <1333482116.12007.262.camel@chacal>
In-Reply-To: <1333482116.12007.262.camel@chacal>
X-Enigmail-Version: 1.4
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Chris Weber <chris@lookout.net>, Mark Nottingham <mnot@mnot.net>, "Michael\(tm\) Smith" <mike@w3.org>, W3C/IETF <w3c-policy@ietf.org>
X-BeenThere: w3c-policy@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Administration of the W3C/IETF liaison <w3c-policy.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Thu, 12 Apr 2012 21:22:41 -0000

On 4/3/12 1:41 PM, Philippe Le Hegaret wrote:
> On Mon, 2012-04-02 at 15:34 -0400, Mark Nottingham wrote:
>>
>> Begin forwarded message:
>>
>>> 	http://trac.tools.ietf.org/wg/iri/trac/ticket/123
>>>
>>> 	https://www.w3.org/html/wg/tracker/issues/189
> 
> ok, I started loading the context on this one.
> 
> Note that the HTML Working Group has two change proposals around this
> one:
>  http://lists.w3.org/Archives/Public/public-html/2012Feb/0272.html
>  http://www.w3.org/html/wg/wiki/User:Eoconnor/ISSUE-189
> 
> Both proposals received feedback from the Chairs:
>  http://lists.w3.org/Archives/Public/public-html/2012Mar/0739.html

This issue has also been aired in the IRI WG, see the thread starting at
<http://lists.w3.org/Archives/Public/public-iri/2012Apr/0008.html> (and
also discussed a bit in Paris, sorry, no audio recordings yet).

So yes, this is an issue for the next agenda, and perhaps sooner.

Peter

-- 
Peter Saint-Andre
https://stpeter.im/



From mnot@mnot.net  Tue Apr 24 22:50:35 2012
Return-Path: <mnot@mnot.net>
X-Original-To: w3c-policy@ietfa.amsl.com
Delivered-To: w3c-policy@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3CC8521F86F8 for <w3c-policy@ietfa.amsl.com>; Tue, 24 Apr 2012 22:50:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[AWL=-4.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id luAqLCmUrR5Q for <w3c-policy@ietfa.amsl.com>; Tue, 24 Apr 2012 22:50:32 -0700 (PDT)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) by ietfa.amsl.com (Postfix) with ESMTP id D082D21F8701 for <w3c-policy@ietf.org>; Tue, 24 Apr 2012 22:50:28 -0700 (PDT)
Received: from [10.4.229.38] (unknown [69.20.3.135]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id CC25822E1EB; Wed, 25 Apr 2012 01:50:21 -0400 (EDT)
Subject: Re: coordination call minutes for review
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=us-ascii
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <4F4D6275.3010303@stpeter.im>
Date: Wed, 25 Apr 2012 15:50:18 +1000
Content-Transfer-Encoding: 7bit
Message-Id: <18359165-F90F-445E-B312-2CDE3209A7B6@mnot.net>
References: <4F4D6275.3010303@stpeter.im>
To: Peter Saint-Andre <stpeter@stpeter.im>
X-Mailer: Apple Mail (2.1257)
Cc: W3C/IETF <w3c-policy@ietf.org>
X-BeenThere: w3c-policy@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Administration of the W3C/IETF liaison <w3c-policy.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Wed, 25 Apr 2012 05:50:35 -0000

Did these go out?

Cheers,

On 29/02/2012, at 10:25 AM, Peter Saint-Andre wrote:

> Please send your feedback in the next ~48 hours so we can make these
> public. Thanks!
> 
> ###
> 
> W3C/IETF Coordination Call
> February 28, 2012
> 
> Participants:
> 
> Gonzalo Camarillo (GC)
> Stephen Farrell (SF)
> John Klensin (JCK)
> Philippe Le Hegaret (PLH)
> Mark Nottingham (MNOT)
> Pete Resnick (PR)
> Peter Saint-Andre (PSA)
> Robert Sparks (RJS)
> Thomas Roessler (TLR)
> 
> Agenda:
> 
> 1. HTTP/2.0 / recharter of IETF HTTPBIS WG
> 2. Web authentication (see lively discussion triggered by #1)
> 3. Concerns about the "CA system"
> 4. IETF IRI WG / W3C i18n Core WG / URL processing spec
> 5. WebSocket extensions / HYBI WG recharter
> 6. Update on work in IETF WebSec WG and W3C WebAppSec WG
> 7. SIP provider identity - does it matter for WebRTC?
> 8. Crypto API chartering, Identity meetings in Paris
> 9. Paris IETF / IAB plenary
> 10. Next meeting
> 11. Any Other Business
> 
> Notes:
> 
> 1. HTTP Recharter
> 
> MNOT: SPDY came out ~1 year ago, gained significant momentum in late
> 2011. Mark reached out to implementer community. Lots of interest and
> positive feedback. Mark worked on strawman charter and socialized it
> with Mike Belshe / SPDY folks, IETF ADs, W3C TAG, etc. Implementation is
> accelerating. Concern that input is needed sooner rather than later. Has
> been put before the IESG. Idea is to solicit proposals for HTTP/2.0 in
> the next few months. Open process to ensure that we're not just taking
> on SPDY, other approaches are welcome.
> 
> PSA: Any coordination issues with W3C/IETF here?
> 
> MNOT: Should make sure that HTML and HTTP/2.0 are well-coordinated.
> 
> PLH: Are there specific people we need to get involved or specific
> issues related to HTML5 and HTTP/2.0?
> 
> MNOT: No specific concerns here, probably involve Yves.
> 
> TLR: Concur about involving Yves.
> 
> 2. Web Authentication
> 
> PSA: Lots of discussion over time, not clear that we have all the right
> people at the table yet.
> 
> SF: I think it's gotten better. Might be useful to develop some
> experimental approaches / new auth schemes.
> 
> TLR: Could you provide a summary of the discussion?
> 
> SF: During external review of the proposed recharter, I raised the issue
> of perhaps developing new / better HTTP authentication approaches. This
> gives people an opportunity to introduce proposals to work on that
> during the work on HTTP/2.0. If so, the work would happen in HTTPBIS;
> for non-adopted, interesting proposals, we might decide to form an
> initiative in the IETF Security Area to work on experimental proposals
> (so they are not critical path for HTTP/2.0.)
> 
> TLR: Are there any implementers strongly interested here?
> 
> SF: We won't know until we see concrete proposals.
> 
> 3. CA Concerns
> 
> PSA: Could TLR/PLH fill us in?
> 
> TLR: No obvious venue for a productive conversation. Some ideas for the
> W3C to form an initiative, also discussions at IETF (therightkey mailing
> list). One additional piece: notion among some in the W3C community that
> the DNS is more brittle than others think it is.
> 
> PR: What parts do people think are brittle?
> 
> TLR: Concerns not as well-defined as I'd like them to be.  But heads-up,
> that discussion is going on.
> 
> PR: My slightly snarky response to the CA problem is the existence of
> the DANE WG effort at the IETF. I personally feel like it could solve
> the problem.
> 
> SF: DANE can change/improve stuff, but might not fix it.
> 
> TLR: Personally I think we need to start thinking about / working on
> things like JavaScript APIs for some of this.
> 
> SF: One wrinkle is that there are more unreliable registrars than
> unreliable CAs.
> 
> JCK: If you look at it in terms of percentages, it's ugly all around.
> 
> TLR: DANE appears to perhaps limit the attack surface. Also, this is a
> much longer discussion.
> 
> TLR: Changing topics, the CA/Browser Forum is discussing whether to form
> a more open venue for work on this topic and is soliciting proposals:
> http://cabforum.org/index.html
> 
> SF: Is there concrete W3C planning here?
> 
> TLR: Not yet. Counter-question: is there concrete planning at the IETF?
> 
> SF: Not yet, other than therightkey@ietf.org discussion list, but the
> proposals there are not yet stable and need more work before they can be
> reviewed more widely. Perhaps a W3C community group?
> 
> TLR: Might be worth discussing the possibility of a workshop or, yes, a
> community group.
> 
> 4. IRI
> 
> PSA: i18n Core WG has agreed to review the IRI WG documents starting
> around the time of IETF83.
> 
> JCK: ICANN IDN work important in this context.  Note that, if ICANN
> declares that some sets of names are to be considered/ treated as
> "equal", anything based on comparisons of URIs or IRIs moves from "hard
> and not necessarily reliable" into "surreal".
> 
> ACTION: PSA to pull together IRI / IDN folks for discussion around IETF
> 83, additional discussion later.
> 
> Useful participants: folks on this call, Thomas Narten, Suzanne Woolf,
> Dave Thaler, Andrew Sullivan, Gervase Markham, Klensin, Faltstrom.
> Maybe Vint, maybe Steve Crocker.
> 
> TLR: Where do we stand on the HTML5 / IRI front?
> 
> PSA: See http://dvcs.w3.org/hg/url/raw-file/tip/Overview.html - based on
> conversation with Mike Smith the other day, it is a bit early to provide
> detailed feedback on that spec now.
> 
> 5. WebSocket Extensions
> 
> PSA: HYBI WG has been rechartered, we might want to make sure that we
> continue coordination between HYBI WG and WebApps WG.
> 
> PLH: Main blocker now is tests, but progress is ongoing there.
> 
> 6. WebSec / WebAppSec
> 
> PSA: New version of Strict Transport Security.
> 
> TLR: Discussion of clickjacking and Content Security Policy, trying to
> get CORS done, reasonable intensity of work. Reasonably confident that
> things are going well.
> 
> 7. SIP Provider Identity and WebRTC
> 
> TLR: There was discussion about having an IANA registry for SIP
> providers. Do we have a sense of the use case?
> 
> RJS: I don't think you need to worry about it. The proponents for the
> SPID idea itself are continuing to pursue the idea, and I'll point you
> to the messages where they have making their motivating arguments. I
> have not seen any desire to bring this up in the WebRTC.
> 
> JCK: Please loop me in on this.
> 
> 8. W3C Crypto API
> 
> TLR: WG is under review by Advisory Community, still working to find an
> additional co-chair. Expect approved charter in relatively near future.
> Other issue is relationship to OAuth, OpenID Connect, possibility for
> additional and broader work. Side meeting at IETF 83 in Paris.
> 
> SF: Scheduled on the Thursday lunch break (1130-1300) in room 252A, just
> before the OAuth WG session.
> 
> PSA: Stephen, do you see any coordination issues from the IETF side?
> 
> SF: Definitely interest in seeing crypto in the browsers. Existence of
> such an API could have an impact in the future on OAuth design etc.
> 
> TLR: Also note OpenID connect meeting Sunday, overlapping with training
> sessions
> 
> 9. IETF 83 / IAB Plenary
> 
> TLR: Do we have insights into the agenda for the IAB Plenary? I've heard
> it's related to web security.
> 
> SF: We don't have details yet.
> 
> PSA: Who will be there?
> 
> TLR: Me part of the time, Philippe, Dominique for RTCWeb, Harry Halpin
> is local, Wendy Seltzer for a few days, Yves might be there too. I also
> expect a number of TAG members to be there since they are meeting in
> Europe the next week. Might be good to have a separate discussion about
> that with Yves and Larry.
> 
> ACTION: Thomas to check in with Yves on TAG activities at IETF.
> 
> 10. Next Meeting
> 
> ~4-5 weeks after IETF 83? Week of April 23rd or 16th might work. To
> coordinate on the list.
> 
> 11. Any Other Business
> 
> PLH: Possibility of HTML meeting in May/June timeframe.
> 
> TLR: There's been some discussion about impact of application work such
> as WebRTC on lower layers of the network, best practices for network
> usage, etc. Is this a general topic that comes up on the IETF side of
> the discussion or should there be some coordination here? There is a
> community group at http://www.w3.org/community/networkfriendly/
> 
> PR: Move to hallway discussion in Paris.
> 
> END
> 
> ###
> 
> 
> 

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




From stpeter@stpeter.im  Wed Apr 25 08:14:19 2012
Return-Path: <stpeter@stpeter.im>
X-Original-To: w3c-policy@ietfa.amsl.com
Delivered-To: w3c-policy@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D04A521F8736 for <w3c-policy@ietfa.amsl.com>; Wed, 25 Apr 2012 08:14:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.529
X-Spam-Level: 
X-Spam-Status: No, score=-102.529 tagged_above=-999 required=5 tests=[AWL=0.070, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9BfadNQiN-XX for <w3c-policy@ietfa.amsl.com>; Wed, 25 Apr 2012 08:14:18 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 3A92221F861E for <w3c-policy@ietf.org>; Wed, 25 Apr 2012 08:14:16 -0700 (PDT)
Received: from [192.168.0.3] (unknown [216.17.175.160]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 7038F40058; Wed, 25 Apr 2012 09:28:51 -0600 (MDT)
Message-ID: <4F9814C4.9090607@stpeter.im>
Date: Wed, 25 Apr 2012 09:14:12 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:11.0) Gecko/20120327 Thunderbird/11.0.1
MIME-Version: 1.0
To: Mark Nottingham <mnot@mnot.net>
Subject: Re: coordination call minutes for review
References: <4F4D6275.3010303@stpeter.im> <18359165-F90F-445E-B312-2CDE3209A7B6@mnot.net>
In-Reply-To: <18359165-F90F-445E-B312-2CDE3209A7B6@mnot.net>
X-Enigmail-Version: 1.4
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: W3C/IETF <w3c-policy@ietf.org>
X-BeenThere: w3c-policy@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Administration of the W3C/IETF liaison <w3c-policy.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Wed, 25 Apr 2012 15:14:20 -0000

I recall sending them.

On 4/24/12 11:50 PM, Mark Nottingham wrote:
> Did these go out?
> 
> Cheers,
> 
> On 29/02/2012, at 10:25 AM, Peter Saint-Andre wrote:
> 
>> Please send your feedback in the next ~48 hours so we can make these
>> public. Thanks!
>>
>> ###
>>
>> W3C/IETF Coordination Call
>> February 28, 2012
>>
>> Participants:
>>
>> Gonzalo Camarillo (GC)
>> Stephen Farrell (SF)
>> John Klensin (JCK)
>> Philippe Le Hegaret (PLH)
>> Mark Nottingham (MNOT)
>> Pete Resnick (PR)
>> Peter Saint-Andre (PSA)
>> Robert Sparks (RJS)
>> Thomas Roessler (TLR)
>>
>> Agenda:
>>
>> 1. HTTP/2.0 / recharter of IETF HTTPBIS WG
>> 2. Web authentication (see lively discussion triggered by #1)
>> 3. Concerns about the "CA system"
>> 4. IETF IRI WG / W3C i18n Core WG / URL processing spec
>> 5. WebSocket extensions / HYBI WG recharter
>> 6. Update on work in IETF WebSec WG and W3C WebAppSec WG
>> 7. SIP provider identity - does it matter for WebRTC?
>> 8. Crypto API chartering, Identity meetings in Paris
>> 9. Paris IETF / IAB plenary
>> 10. Next meeting
>> 11. Any Other Business
>>
>> Notes:
>>
>> 1. HTTP Recharter
>>
>> MNOT: SPDY came out ~1 year ago, gained significant momentum in late
>> 2011. Mark reached out to implementer community. Lots of interest and
>> positive feedback. Mark worked on strawman charter and socialized it
>> with Mike Belshe / SPDY folks, IETF ADs, W3C TAG, etc. Implementation is
>> accelerating. Concern that input is needed sooner rather than later. Has
>> been put before the IESG. Idea is to solicit proposals for HTTP/2.0 in
>> the next few months. Open process to ensure that we're not just taking
>> on SPDY, other approaches are welcome.
>>
>> PSA: Any coordination issues with W3C/IETF here?
>>
>> MNOT: Should make sure that HTML and HTTP/2.0 are well-coordinated.
>>
>> PLH: Are there specific people we need to get involved or specific
>> issues related to HTML5 and HTTP/2.0?
>>
>> MNOT: No specific concerns here, probably involve Yves.
>>
>> TLR: Concur about involving Yves.
>>
>> 2. Web Authentication
>>
>> PSA: Lots of discussion over time, not clear that we have all the right
>> people at the table yet.
>>
>> SF: I think it's gotten better. Might be useful to develop some
>> experimental approaches / new auth schemes.
>>
>> TLR: Could you provide a summary of the discussion?
>>
>> SF: During external review of the proposed recharter, I raised the issue
>> of perhaps developing new / better HTTP authentication approaches. This
>> gives people an opportunity to introduce proposals to work on that
>> during the work on HTTP/2.0. If so, the work would happen in HTTPBIS;
>> for non-adopted, interesting proposals, we might decide to form an
>> initiative in the IETF Security Area to work on experimental proposals
>> (so they are not critical path for HTTP/2.0.)
>>
>> TLR: Are there any implementers strongly interested here?
>>
>> SF: We won't know until we see concrete proposals.
>>
>> 3. CA Concerns
>>
>> PSA: Could TLR/PLH fill us in?
>>
>> TLR: No obvious venue for a productive conversation. Some ideas for the
>> W3C to form an initiative, also discussions at IETF (therightkey mailing
>> list). One additional piece: notion among some in the W3C community that
>> the DNS is more brittle than others think it is.
>>
>> PR: What parts do people think are brittle?
>>
>> TLR: Concerns not as well-defined as I'd like them to be.  But heads-up,
>> that discussion is going on.
>>
>> PR: My slightly snarky response to the CA problem is the existence of
>> the DANE WG effort at the IETF. I personally feel like it could solve
>> the problem.
>>
>> SF: DANE can change/improve stuff, but might not fix it.
>>
>> TLR: Personally I think we need to start thinking about / working on
>> things like JavaScript APIs for some of this.
>>
>> SF: One wrinkle is that there are more unreliable registrars than
>> unreliable CAs.
>>
>> JCK: If you look at it in terms of percentages, it's ugly all around.
>>
>> TLR: DANE appears to perhaps limit the attack surface. Also, this is a
>> much longer discussion.
>>
>> TLR: Changing topics, the CA/Browser Forum is discussing whether to form
>> a more open venue for work on this topic and is soliciting proposals:
>> http://cabforum.org/index.html
>>
>> SF: Is there concrete W3C planning here?
>>
>> TLR: Not yet. Counter-question: is there concrete planning at the IETF?
>>
>> SF: Not yet, other than therightkey@ietf.org discussion list, but the
>> proposals there are not yet stable and need more work before they can be
>> reviewed more widely. Perhaps a W3C community group?
>>
>> TLR: Might be worth discussing the possibility of a workshop or, yes, a
>> community group.
>>
>> 4. IRI
>>
>> PSA: i18n Core WG has agreed to review the IRI WG documents starting
>> around the time of IETF83.
>>
>> JCK: ICANN IDN work important in this context.  Note that, if ICANN
>> declares that some sets of names are to be considered/ treated as
>> "equal", anything based on comparisons of URIs or IRIs moves from "hard
>> and not necessarily reliable" into "surreal".
>>
>> ACTION: PSA to pull together IRI / IDN folks for discussion around IETF
>> 83, additional discussion later.
>>
>> Useful participants: folks on this call, Thomas Narten, Suzanne Woolf,
>> Dave Thaler, Andrew Sullivan, Gervase Markham, Klensin, Faltstrom.
>> Maybe Vint, maybe Steve Crocker.
>>
>> TLR: Where do we stand on the HTML5 / IRI front?
>>
>> PSA: See http://dvcs.w3.org/hg/url/raw-file/tip/Overview.html - based on
>> conversation with Mike Smith the other day, it is a bit early to provide
>> detailed feedback on that spec now.
>>
>> 5. WebSocket Extensions
>>
>> PSA: HYBI WG has been rechartered, we might want to make sure that we
>> continue coordination between HYBI WG and WebApps WG.
>>
>> PLH: Main blocker now is tests, but progress is ongoing there.
>>
>> 6. WebSec / WebAppSec
>>
>> PSA: New version of Strict Transport Security.
>>
>> TLR: Discussion of clickjacking and Content Security Policy, trying to
>> get CORS done, reasonable intensity of work. Reasonably confident that
>> things are going well.
>>
>> 7. SIP Provider Identity and WebRTC
>>
>> TLR: There was discussion about having an IANA registry for SIP
>> providers. Do we have a sense of the use case?
>>
>> RJS: I don't think you need to worry about it. The proponents for the
>> SPID idea itself are continuing to pursue the idea, and I'll point you
>> to the messages where they have making their motivating arguments. I
>> have not seen any desire to bring this up in the WebRTC.
>>
>> JCK: Please loop me in on this.
>>
>> 8. W3C Crypto API
>>
>> TLR: WG is under review by Advisory Community, still working to find an
>> additional co-chair. Expect approved charter in relatively near future.
>> Other issue is relationship to OAuth, OpenID Connect, possibility for
>> additional and broader work. Side meeting at IETF 83 in Paris.
>>
>> SF: Scheduled on the Thursday lunch break (1130-1300) in room 252A, just
>> before the OAuth WG session.
>>
>> PSA: Stephen, do you see any coordination issues from the IETF side?
>>
>> SF: Definitely interest in seeing crypto in the browsers. Existence of
>> such an API could have an impact in the future on OAuth design etc.
>>
>> TLR: Also note OpenID connect meeting Sunday, overlapping with training
>> sessions
>>
>> 9. IETF 83 / IAB Plenary
>>
>> TLR: Do we have insights into the agenda for the IAB Plenary? I've heard
>> it's related to web security.
>>
>> SF: We don't have details yet.
>>
>> PSA: Who will be there?
>>
>> TLR: Me part of the time, Philippe, Dominique for RTCWeb, Harry Halpin
>> is local, Wendy Seltzer for a few days, Yves might be there too. I also
>> expect a number of TAG members to be there since they are meeting in
>> Europe the next week. Might be good to have a separate discussion about
>> that with Yves and Larry.
>>
>> ACTION: Thomas to check in with Yves on TAG activities at IETF.
>>
>> 10. Next Meeting
>>
>> ~4-5 weeks after IETF 83? Week of April 23rd or 16th might work. To
>> coordinate on the list.
>>
>> 11. Any Other Business
>>
>> PLH: Possibility of HTML meeting in May/June timeframe.
>>
>> TLR: There's been some discussion about impact of application work such
>> as WebRTC on lower layers of the network, best practices for network
>> usage, etc. Is this a general topic that comes up on the IETF side of
>> the discussion or should there be some coordination here? There is a
>> community group at http://www.w3.org/community/networkfriendly/
>>
>> PR: Move to hallway discussion in Paris.
>>
>> END
>>
>> ###
>>
>>
>>


