1. 1 Universal MultiMedia Addressing Platform Activity Group Update 20 May 2004 UMMAP

2. UMMAP 2 UMMAP Charter To promote the development of a platform using existing standards for addressing any multimedia end point from any multimedia end point, regardless of the service provider or protocol in use by the systems, and to build consensus for the platform among vendors, service providers, and users.

3. UMMAP 3 UMMAP Charter Caveat: Making a call from one multimedia device to another multimedia device may involve issues other than addressing, such as protocol incompatibilities or codec choices. Other obstacles to inter-protocol communications exist but are currently outside the scope of this working group. The UMMAP Activity Group will work with other bodies to accelerate resolution of related issues.

4. UMMAP 4 Background  Started in June 2003 as the Dialing Plan Working Group chartered by the H.323 Forum.  Moved to the IMTC as UMMAP in October 2003 after the group realized that the scope was beyond that of the H.323 Forum.

5. UMMAP 5 Background  Decision was made to separate ‘ideal world’ from ‘running code’  GDS was proposed and accepted as the 1 st ‘running code’ implementation GDS was developed by TERENA, and adopted by ViDe.net GDS was developed by TERENA, and adopted by ViDe.net Administration is done by the ViDe Numerical Addressing Space Management Team, with representation from UMMAP Administration is done by the ViDe Numerical Addressing Space Management Team, with representation from UMMAP

6. UMMAP 6 Background  First thinking was around developing an actual dialing plan Survey of existing dialing plans Survey of existing dialing plans E.164 (ITU & MOREnet)E.164 (ITU & MOREnet) GDS (ViDE)GDS (ViDE) IHETSIHETS ProprietaryProprietary Discussion then centered around related issues Discussion then centered around related issues

7. UMMAP 7 Background  What is in scope for UMMAP? Transport Transport IPv4IPv6PSTNISDN Protocol (which would require transcoding) Protocol (which would require transcoding) SIPH.323H.320Analog & Digital Voice Directory/Database Directory/Database ENUM/DNSH.350/LDAPLERG SIMPLE/XMPP Addressing Addressing E.164GDSSIP URITEL URIH.323 URL Routing Routing IPTRIPSS7

8. UMMAP 8 Background  What is not in scope for UMMAP? Encoding standards (i.e. G.711, G.729, etc.) Encoding standards (i.e. G.711, G.729, etc.)

9. UMMAP 9 Activities  Ongoing discussion is via the IMTCUMMAP mailing list  UMMAP has a web presence on the IMTC under Activity Groups, and includes topical resources as well as information on the next meeting

10. UMMAP 10 Activities  Conference calls are held every two weeks to discuss activities.  Subject Matter Experts are invited to join the call for 20-30 minutes periodically to brief the group on a particular topic.  Updates and discussion is held on the deployment of GDS as the ‘running code’ solution

11. UMMAP 11 Activities  New member recruitment is ongoing, with individual members contacting people who have an interest and inviting them to join;  A formal marketing plan for UMMAP will be developed in 2Q04 to build momentum for the AG efforts and to create a supplier/user base sufficient to begin consideration of an Interop event

12. UMMAP 12 2004 Goals Q1 2004   Goal: Deepen group understanding of and document existing protocols that the group believes are part of the ideal solution.   Accomplished: UMMAP Recommendation A.1 is currently being circulated for comment

13. UMMAP 13 2004 Goals Q1 2004   Goal: Prepare communications plan (most appropriate and effective vehicles to promote the UMMAP outputs).  Accomplished: Outreach to other groups/orgs working on similar or related issues Outreach to other groups/orgs working on similar or related issues IMTC should created liaison to SIP ForumIMTC should created liaison to SIP Forum

14. UMMAP 14 2004 Goals Q2 2004   Goal: Prepare document that articulates UMMAP group’s vision for potential transparent multimedia addressing solution.   Accomplished:

15. UMMAP 15 2004 Goals Q2 2004  Goal: Marketing plan developed and executed  Accomplished:

16. UMMAP 16 2004 Goals Q3 2004   Goal: Produce document that describes the gaps in existing protocols that prevent achievement of vision.   Accomplished:

17. UMMAP 17 Progress to Date  Recommendation A.1  Ongoing outreach to related groups/orgs

18. UMMAP 18 ITMC BoD Items 1. Approval to create board-level liaisons with related groups (i.e. SIP Forum)  Decision and approval process 2. Approval to formally issue UMMAP Recommendations  Decision and approval process  A.1 is out for comment

19. UMMAP 19 IMTC BoD Item 1  A board-level liaison with other industry groups would allow for board-directed and controlled collaboration.  A high-level liaison would be more effective in promoting inter-AG efforts than more informal, peer-level efforts

20. UMMAP 20 IMTC BoD Item 2  UMMAP Recommendations A.1 is the 1 st Addressing recommendation A.1 is the 1 st Addressing recommendation Issue and promote as recommendations, rather than standards (i.e. FR Forum FRF.x) Issue and promote as recommendations, rather than standards (i.e. FR Forum FRF.x) Interop events can be centered around compliance with recommendations (which include compliance specifications) Interop events can be centered around compliance with recommendations (which include compliance specifications) Do BoD need to be involved with issuance, or once UMMAP finalizes a recommendation, it can be published and promoted? Do BoD need to be involved with issuance, or once UMMAP finalizes a recommendation, it can be published and promoted?

21. UMMAP 21 Questions?  AG Chair – David Olson dolson@more.net dolson@more.net dolson@more.net  AG Secretary/Editor – Christine Perey cperey@perey.com cperey@perey.com cperey@perey.com  GDS Liaison – Tyler Johnson trjohns1@email.unc.edu trjohns1@email.unc.edu trjohns1@email.unc.edu  http://www.imtc.org/activity_groups/UMMAP.asp

22. 22 Universal MultiMedia Addressing Platform Activity Group Update 20 May 2004 UMMAP