IETF 75 DRINKS Agenda (Stockholm, Sweden) - FINAL ================================================= Data for Reachability of Inter/tra-NetworK SIP (drinks) Date: MONDAY, July 27, 2009 Time: 1520-1720 Afternoon Session II, Location: Congresshall A Chair(s): Richard Shockey Alexander Mayrhofer WG Secretary: Debbie Guyton RAI Director(s): Cullen Jennings Robert Sparks RAI Area Advisor: Cullen Jennings fluffy@cisco.com Session Agenda ============== Welcome & Agenda Bashing (5m) A. Document status of the DRINKS WG (Deborah Guyton, 5m) B. Status of the Usecases Requirements Document. (20m) : DRINKS Use cases and Protocol Requirements Author(s) : S. Channabasappa Filename : draft-ietf-drinks-usecases-requirements-00.txt Pages : 22 Date : 2009-05-27 This document captures the use cases and associated requirements for interfaces to provision session establishment data into SIP Service Provider components that aid with session routing. Specifically, the current version of this document focuses on the provisioning of one such element, termed the registry. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-drinks-usecases-requirements-00.txt C. New Business. (40m) Title : Session Peering Provisioning Protocol Author(s) : J. Mule, et al. Filename : draft-mule-drinks-proto-01.txt Pages : 43 Date : 2009-07-13 This document defines a protocol for provisioning session establishment data into Session Data Registries or SIP Service Provider data stores. The provisioned data may then be used by various network elements for session peering. This document focuses on the Session Peering Provisioning Protocol used by clients to provision registries. The document provides a set of guiding principles for the design of this protocol like extensibility and independent transport definitions, a basic data model that meets some of the requirements discussed in DRINKS and an early XML Schema Document. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-mule-drinks-proto-01.txt D. Open discussion of the issues surrounding selection of SOAP vs RESTful as the baseline DRINKS transport protocol. (20m) E. Architectural issues surrounding transport layer decisions such as error code handling etc. (15m) F. Discussion about WG Milestones (15m) Open Discussion / Other Business (if time permits)