1. Slide # 1 IETF-62 March 2005Conference Package Conference Package Status March 11 th, 2005 IETF 62, Minnesota draft-sipping-conference-package-09

2. Slide # 2 IETF-62 March 2005Conference Package -09 Status Last Called in December New suggested changes –Indexing of –Indexing of conference media containers

3. Slide # 3 IETF-62 March 2005Conference Package Indexing of In -09 –The key is comprised of mandatory ‘entity’ attribute and optional ‘call-id’ attribute Agreed on the listAgreed on the list –The key becomes a single attribute ‘entity’ of type “string”

4. Slide # 4 IETF-62 March 2005Conference Package Indexing of a Media Container In -09 – and are global conference containers – Rows are indexed by ‘id’ and contain (draft- ietf-mmusic-sdp-media-label-01.txt) as a sub-element Agreed during an informal ad-hoc meetingAgreed during an informal ad-hoc meeting – container will be removed from the schema because it is not useful and is a source for confusion –Rows of the container will be indexed by the ‘label’ attribute (which corresponds to the SDP label)

5. Slide # 5 IETF-62 March 2005Conference Package Indexing of of an endpoint In -09 – rows are indexed by ‘id’ of type “string” – rows contain as an optional sub-element Issue –Brian Rosen suggested having a global conference “label” as the index Editor’s ViewEditor’s View –In simple conferencing, the “label” concept does not exist because the media association across participants is expected to be done by media types, codecs, etc. –Therefore, it is an unnecessary burden for these conference servers to generate global “label” for compliancy only –In this case, “smart users” will be confused by non-compliant server behavior –‘id’ should remain the key

6. Slide # 6 IETF-62 March 2005Conference Package Indexing of In -09 – index is AoR of type “anyURI” –Can be “anonymous” as defined in "A Privacy Mechanism for the Session Initiation Protocol (SIP)", RFC 3323A Privacy Mechanism for the Session Initiation Protocol (SIP) –Assumed that the sub-element can be used as a “nickname” Issue: “Nickname” as index? –Brian Rosen suggested having a “nickname” as the index Editor’s ViewEditor’s View –The “nickname” concept requires broader cross-application requirements work before it can be standardized and used –AoR remains the key –Going forward, if needed XCON can define additional (to “anonymous”) URI conventions and use it in conjunction with for the “nickname” presentation

7. Slide # 7 IETF-62 March 2005Conference Package Next Steps Editor will resubmit -10 reflecting today’s decisions within 5 days Last call again? Submission to the IESG with other SIPPING conferencing drafts