1. IETF-62 draft-johnston-enum-conf-service-00 1 IANA Registration for ENUMservices ‘conf-web’ and ‘conf-uri’ Alan Johnston

2. IETF-62 draft-johnston-enum-conf-service-00 2 ‘conf-web’ ENUM Service Discovery mechanism for web conferences Indicates that the resource identified by the associated URI scheme is capable of being a source of information about the conference. Can be http or https URI

3. IETF-62 draft-johnston-enum-conf-service-00 3 Issues with ‘conf-web’ Value added over ‘web’ RFC 4002? –‘web’ might just be a personal web page, pre-call ID, etc. –web conference URI is a source of direct information, content, and control of the conference. Multiple records –Is it OK to have both a ‘web’ and ‘conf-web’ URIs Should it be ‘web-conf’?

4. IETF-62 draft-johnston-enum-conf-service-00 4 ‘conf-uri’ ENUM Service Discovery mechanism for IP conferences Indicate that the resource identified by the conference URI is a "focus" as defined in the Centralized Conferencing framework. Can be sip, sips, h323 URI –Could add tel and xmpp as well

5. IETF-62 draft-johnston-enum-conf-service-00 5 Issues with ‘conf-uri’ Value added over ‘sip’ and ‘h323’? –Provides “isfocus” indication without calling or querying with OPTIONS –h323 (and tel) have no “isfocus” capability How many telephone numbers are true Conference URIs (i.e. dedicated to a single conference – no passcode or PIN needed)? –One solution is to make more general than a Conference URI to say a Conference Access URI which would allow IVRs. Multiple records –Is it OK to have both a ‘sip’ and ‘conf-uri’ URIs

6. IETF-62 draft-johnston-enum-conf-service-00 6 Next Steps?

7. IETF-62 draft-johnston-enum-conf-service-00 7 Contact Alan Johnston alan.johnston@mci.com