Conference Package Status

1
Conference PackageStatus
draft-sipping-conference-package-09

• March 11th, 2005
• IETF 62, Minnesota

2
-09 Status

• Last Called in December
• New suggested changes
• Indexing of ltusergt
• Indexing of ltendpointgt
• Indexing of ltmediagt
• Indexing of conference media containers

3
Indexing of ltendpointgt

• In -09
• The key is comprised of mandatory entity
  attribute and optional call-id attribute
• Agreed on the list
• The key becomes a single attribute entity of
  type string

4
Indexing of a Media Container

• In -09
• ltavailable-mediagt and ltactive-mediagt are global
  conference containers
• Rows are indexed by id and contain ltlabelgt
  (draft-ietf-mmusic-sdp-media-label-01.txt) as a
  sub-element
• Agreed during an informal ad-hoc meeting
• ltactive-mediagt container will be removed from the
  schema because it is not useful and is a source
  for confusion
• Rows of the ltavailable-mediagt container will be
  indexed by the label attribute (which
  corresponds to the SDP label)

5
Indexing of ltmediagt of an endpoint

• In -09
• ltmediagt rows are indexed by id of type string
• ltmediagt rows contain ltlabelgt as an optional
  sub-element
• Issue
• Brian Rosen suggested having a global conference
  label as the ltmediagt index
• Editors 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 ltmediagt key

6
Indexing of ltusergt

• In -09
• ltusergt 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 ltdisplay-textgt can
  be used as a nickname
• Issue Nickname as ltusergt index?
• Brian Rosen suggested having a nickname as the
  index
• Editors View
• The nickname concept requires broader
  cross-application requirements work before it can
  be standardized and used
• AoR remains the ltusergt key
• Going forward, if needed XCON can define
  additional (to anonymous) URI conventions and
  use it in conjunction with ltdisplay-textgt for the
  nickname presentation

7
Next Steps

• Editor will resubmit -10 reflecting todays
  decisions within 5 days
• Last call again?
• Submission to the IESG with other SIPPING
  conferencing drafts