50 likes | 180 Views
Basic Network Media Services with SIP. IETF 59 - Seoul, ROK Eric W m . Burger. What Does User Look Like?. Discussion on uri@w3.org List Uncomfortable With Concept That a User at a Device Will Never Leak Out to Broad Domain
E N D
Basic Network Media Services with SIP IETF 59 - Seoul, ROK Eric Wm. Burger draft-burger-sipping-netann-08
What Does User Look Like? • Discussion on uri@w3.org List • Uncomfortable With Concept That a User at a Device Will Never Leak Out to Broad Domain • E.g., annc@ms.example.net will never collide with annc@example.net or annc@ann_charles_phone.example.net draft-burger-sipping-netann-08
Suggestions from URI List • Prefix or Postfix Something “Special” • special-annc, special-dialog, … • Mumble-Master is Already De Facto Standard • Postmaster, newsmaster, webmaster • SIP Thing, Use SIP: • sip-annc, sip-dialog • sipanncmaster, sipdialogmaster • Thoughts? draft-burger-sipping-netann-08
Changes in –08Prompted By IESG Review • Much More Security Consideration, e.g., When to Use sips: • sips: Mandatory to Implement; S/MIME Strongly Suggested to Implement; https Mandatory to Implement for VoiceXML Service • Locale Algorithm for Closest Match Provided draft-burger-sipping-netann-08
Changes to Appear in –09 • Locale to follow RFC3066/BCP47 • Examples Quote play= attribute; Not Necessary draft-burger-sipping-netann-08