70 likes | 172 Views
Conference Package Status. draft-sipping-conference-package-09. March 11 th, 2005 IETF 62, Minnesota. -09 Status. Last Called in December New suggested changes Indexing of <user> Indexing of <endpoint> Indexing of <media> Indexing of conference media containers. Indexing of <endpoint>.
E N D
Conference PackageStatus draft-sipping-conference-package-09 March 11th, 2005 IETF 62, Minnesota Conference Package
-09 Status • Last Called in December • New suggested changes • Indexing of <user> • Indexing of <endpoint> • Indexing of <media> • Indexing of conference media containers Conference Package
Indexing of <endpoint> • In -09 • The key is comprised of mandatory ‘entity’ attribute and optional ‘call-id’ attribute • Agreed on the list • The keybecomes a single attribute ‘entity’ of type “string” Conference Package
Indexing of a Media Container • In -09 • <available-media> and <active-media> are global conference containers • Rows are indexed by ‘id’ and contain <label> (draft-ietf-mmusic-sdp-media-label-01.txt) as a sub-element • Agreed during an informal ad-hoc meeting • <active-media> container will be removed from the schema because it is not useful and is a source for confusion • Rows of the <available-media> container will be indexed by the ‘label’ attribute (which corresponds to the SDP label) Conference Package
Indexing of <media> of an endpoint • In -09 • <media> rows are indexed by ‘id’ of type “string” • <media> rows contain <label> as an optional sub-element • Issue • Brian Rosen suggested having a global conference “label” as the <media> index • Editor’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 <media> key Conference Package
Indexing of <user> • In -09 • <user> index is AoR of type “anyURI” • Can be “anonymous” as defined in "A Privacy Mechanism for the Session Initiation Protocol (SIP)", RFC 3323 • Assumed that the sub-element <display-text> can be used as a “nickname” • Issue: “Nickname” as <user> index? • Brian Rosen suggested having a “nickname” as the index • Editor’s View • The “nickname” concept requires broader cross-application requirements work before it can be standardized and used • AoR remains the <user> key • Going forward, if needed XCON can define additional (to “anonymous”) URI conventions and use it in conjunction with <display-text> for the “nickname” presentation Conference 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 Conference Package