IETF/W3C coordination ()

Thomas Roessler | 16 Oct 2011 17:14

strawman document: W3C/IETF mutual review mechanics

On behalf of Mark Nottingham and myself, here's a strawman of what guidance about mutual review mechanics
between W3C and IETF could look like.

This is intended to capture a mix of current practice and some immediate lessons from the collaboration
around hybi / websockets.  The document does not propose any process changes on either side.  Changes to
specifications that happen beyond Proposed Standard are explicitly out of scope for this document,
since we don't have recent experience.

Possible destinations for this document may include a wiki page, or an individual informational i-d.

Comments and input most welcome!

Regards,
--
Thomas Roessler, W3C  <tlr <at> w3.org>  ( <at> roessler)

Strawman
W3C/IETF mutual review expectations

Mark Nottingham <mnot <at> mnot.net> 
Thomas Roessler <tlr <at> w3.org>

2011-10-16

0. Introduction

Occasionally, W3C and IETF produce specifications in close
cooperation, sometimes marked by a significant formal dependency
beween the specifications. A recent example is the websockets protocol
and API specifications produced by the IETF hybi and W3C web

(Continue reading)

headers

Peter Saint-Andre | 17 Oct 2011 21:16

Re: strawman document: W3C/IETF mutual review mechanics

On 10/16/11 9:14 AM, Thomas Roessler wrote:
> On behalf of Mark Nottingham and myself, here's a strawman of what guidance about mutual review mechanics
between W3C and IETF could look like.
> 
> This is intended to capture a mix of current practice and some immediate lessons from the collaboration
around hybi / websockets.  The document does not propose any process changes on either side.  Changes to
specifications that happen beyond Proposed Standard are explicitly out of scope for this document,
since we don't have recent experience.
> 
> Possible destinations for this document may include a wiki page, or an individual informational i-d.
> 
> Comments and input most welcome!
> 
> Regards,
> --
> Thomas Roessler, W3C  <tlr <at> w3.org>  ( <at> roessler)
> 
> 
> 
> 
> 
> 
> Strawman
> W3C/IETF mutual review expectations
> 
> Mark Nottingham <mnot <at> mnot.net> 
> Thomas Roessler <tlr <at> w3.org>
> 
> 
> 2011-10-16

(Continue reading)

headers

Thomas Roessler | 20 Oct 2011 13:40

Re: strawman document: W3C/IETF mutual review mechanics

On 2011-10-17, at 21:16 +0200, Peter Saint-Andre wrote:

>> The liaison telephone conferences are attended by the assigned
>> liaisons from both sides. The IETF Application Area Directors and the
>> W3C Director have standing invitations to join the liaison meetings.
>> IAB members may join the meetings.
> 
> In practice, people other than the IETF Application Area Directors can
> attend these teleconferences. Recently, Area Directors for RAI and
> security have joined given wider cooperation of late between the W3C and
> IETF (web application security, RTC web, etc.).

Indeed.  Want to propose specific changes to the text?

>> Other individuals with specific expertise participate at the
>> invitation of the liaisons.
>> 
>> It is appropriate to copy the (archived) public-ietf-w3c <at> w3.org
>> mailing list on relevant communications between IETF and W3C
>> participants.  The archives of this list serve to document agreements
>> about review time lines, scopes, and issues.
>> 
>> The W3C/IETF liaison team is generally involved in chartering
>> negotiations that require mutual review.  The liaison team keeps an
>> online list of WGs to which the coordination expectations in this
>> document apply at  <at>  <at> .
> 
> That all looks good. Thanks for writing this strawman.

Thanks for the review.

(Continue reading)