IETF #82 DRINKS WG Meeting Taipei, Taiwan Fri, Nov 18 th

Note Well Any submission to the IETF intended by the Contributor for publication as all or part of an IETF Internet-Draft or RFC and any statement made within the context of an IETF activity is considered an "IETF Contribution". Such statements include oral statements in IETF sessions, as well as written and electronic communications made at any time or place, which are addressed to: – The IETF plenary session – The IESG, or any member thereof on behalf of the IESG – Any IETF mailing list, including the IETF list itself, any working group or design team list, or any other list functioning under IETF auspices – Any IETF working group or portion thereof – The IAB or any member thereof on behalf of the IAB – The RFC Editor or the Internet-Drafts function All IETF Contributions are subject to the rules of RFC 5378 and RFC 3979 (updated by RFC 4879).RFC 5378RFC 3979RFC 4879 Statements made outside of an IETF session, mailing list or other function, that are clearly not intended to be input to an IETF activity, group or function, are not IETF Contributions in the context of this notice. Please consult RFC 5378 and RFC 3979 for details.RFC 5378RFC 3979 A participant in any IETF activity is deemed to accept all IETF rules of process, as documented in Best Current Practices RFCs and IESG Statements. A participant in any IETF activity acknowledges that written, audio and video records of meetings may be made and may be available to the public. 1

Agenda 0. Welcome and Administrivia (5m) – Note well, Blue sheets, scribes – Agenda Bashing 1.WG status review (5m) 2.Discussions at the Interim and current action items (10m) 3.Protocol document ( 15m) 4.Transport document ( 15m) 5.Proposed next steps (5m) 6.Open Mic Time 2

!!Scribes, Jabber!! 3

#1: WG Status Review (Chairs) 4

Goal still remains the same… Develop and propose data structures and data exchange provisioning protocol between SIP-based multimedia administrative domains Specifically, – Identify use cases and requirements – Specify data model and protocol – Specify one transport; agreed upon mechanism is SOAP over HTTP There are no current plans to extend the charter (e.g., for distribution) or other transport mechanisms – This was clarified in Quebec and re-iterated at the interim – However, new work requests can be submitted to DISPATCH 5

Status of WG Drafts draft-ietf-drinks-usecases-requirements – Past WG, and past IESG review – Approved-announcement to be sent::Point Raised - writeup needed – Link: draft-ietf-drinks-spprov – In Progress – Major structural changes made; will be discussed today – Link: draft-ietf-drinks-sppp-over-soap – In Progress – Major structural changes made; will be discussed today – Link: 6

Since Quebec… The Design team continued weekly design team calls – Minutes continue to be shared on the WG mailing list We also held a WG (virtual) interim meeting on Aug 31 st – Minutes shared on the WG list A few I-D Updates! – One update to draft-ietf-drinks-usecases-requirements v06 updated on 8/12 – Three updates made to draft-ietf-drinks-spprov v10 on 9/9, v11 on 10/31, v12 on 11/15 – Three updates made to draft-ietf-drinks-spprov-over-soap v05 on 9/2, v06 on 10/31, v07 on 11/15 Responded to ITU Liaison ( 7