RE: ITU's H.350 and ENUM
- Date: Wed, 10 Sep 2003 15:51:26 +0200
Hi folks,
(BThere is really something very wierd going on. I took some time to dig into and found
(Bthe following info:
(B
(BViDeNet (Video Developing Network) is setting up the so-called
(B"H.323 Global Dialling Scheme (GDS)".
(B
(BThis is currently a wild mixture
(Bof a private numbering and dialing plan, containing of
(B1.an international access code '00', also called
(BTHE WORLD GATEKEEPER PREFIX (very bombastic)
(B2.the E.164 Country code (the real one)
(B3. An organisational prefix?? (OP) -choose what you like e.g:
(B(Many national research organizations follow the telephone
(Bnumber system in their country and use their area code and
(Borganizational telephone exchange prefix. For instance, SURFnet's OP is 302305.
(B4.an Endpoint Number (EN)
(B
(BThis is all set up by a Numerical Addressing Space Management Team
(BWorking Group (NASM) and implemented
(Bin a ViDeNet Root Level Architecture set up with Gatekeepers.
(B
(BAt least ENUM and DNS is mentioned in the scope of NASM
(B
(BNASM is responsible the management of ViDeNet numerical address space. This group designs the numerical address space and supporting routing schemes, including E.164int integration, hierarchical and flat structures, with particular emphasis on the root level and top tier architectures. Of particular importance is the alignment of existing h.323 addressing to E.164-like structures, in order to prepare the way for an eventual migration toward full DNS-based dialing, ENUM and related numerical address translation schemes.
(B
(BSofar ITU-T SG16:
(B
(BAt the same time SG13 is sending a liasion to SG2 AND SG16:
(B(TD122 (WP 1/2) Liasion on Videoconferencing Networks.
(Battached to SG13 Documents:
(BCOM 13 - D353 (WP 2/13) - A proposal for launching research on videoconferencing services network
(BCOM 13 - D356 (WP2/13) - Draft recommendation of a general description of videoconferencing services networks
(Bboth from China Telecom and Huawei Technologies.
(B
(BIn D356 a numbering plan is proposed (at least not containing an
(BWorld Gatekeeper Access code :-) and also not a choose as you like
(BOrganizational Prefix, but instead an domestic access code.
(B(Regulators, watch out and free up some domestic numbering space,
(Bto profide space for 100 Million H.323 Video terminals per country -
(Band the same for SIP). Hey, what about technology independance?
(BAt least this proposal could be compatible with E.164
(B
(BBoth ideas are quite new, because neither a prefix nor an acces code can
(Bbe part of an E.164 number.
(B
(BI attach below some excepts what I found sofar:
(B
(Bhave fun
(B
(BI consider this development at least very interesting in context with ENUM
(B
(BRichard Stastny
(BPS: and I thought the next SG2 meeting will be boring;-)
(B
(B------------------------------------------------------------
(BFrom D356
(B9. Numbering Schemes
(B9.1 Introduction
(BIt is necessary that number resource for videoconferencing services networks is created and assigned in a unified way in order to facilitate the deployment of videoconferencing services and the efficient management of user resource. The principles for number formation and assignment have borrowed the advantages from PSTN networks and ITU-T E.164 recommendation is adopted. For ISDN videoconferencing services networks, the numbering of MCUs and terminals directly uses their ISDN numbers. If the approach described in section 9.2 is used, a mapping or correspondence relationship between terminal numbers and ISDN numbers shall be established on SMC. For ISDN videoconferencing services networks, the approach described in section 9.2 is used.
(B9.2 Numbering of terminals
(BThe domestic number of a videoconferencing terminal can be formed in such a way that the first 3 to 5 digits to be used as access number followed by another 8 digits to yield a number with 11 to 13 digits. The last 8-digit sub number is composed of a 3-digit domestic area code and 5-digit intra-area terminal number. The formation rules are shown in the following diagram:
(B
(BCC DAC CN
(B|-- --International videoconferencing terminal number --------|
(B |-- Domestic terminal number--|
(BCC$B!a(JCountry code
(BDAC$B!a(JDomestic access code for videoconferencing
(BCN$B!a(JCustomer number, 8 digits long with a structure H1H2H3ABCDE where HlH2H3 is the domestic area code and ABCDE is the intra-area terminal number.
(BWhen the capacity for customer numbers is limited, more numbers can be created by introducing either longer domestic area codes or longer domestic access code.
(B
(B------------------------------------------------------------------------------------------------
(BFrom ViDeNet:
(B-------------------------------------------------------------------------
(BThe Global Dialing Scheme Explained
(B
(BThe Global Dialing Scheme (GDS) is a new numbering plan for the global video and voice over IP network test bed, developed by Terena.
(B
(BIt resembles the international telephone system numbering plan, with some exceptions. With the GDS, you can number each participating videoconferencing endpoint, MCU conference and gateway. GDS provides easy, uniform dialing throughout the world.
(B
(BEach basic number consists of four parts:
(B
(B1. The International Access Code (IAC) (also called the world gatekeeper prefix) This is defined as 00.
(B
(B2. A Country Code (CC)
(BThis follows the ITU international access code system. For instance, the country code for the Netherlands is 31. See the following PDF document for country codes:
(B
(Bhttp://www.itu.int/itudoc/itu-t/ob-lists/icc/e164_717.pdf
(B
(B3. An Organizational Prefix (OP)
(B
(BMany national research organizations follow the telephone number system in their country and use their area code and organizational telephone exchange prefix. For instance, SURFnet's OP is 302305.
(B
(BHowever, there are other possibilities. Some organizations use their administration number or make one up. National research organizations or videoconferencing service providers could instead supply you with an OP, as was the case with the old ViDeNet system.
(B
(BIn any case, your OP MUST be unique within a country. If you don't know your OP, please contact your videoconferencing service provider, your national gatekeeper, or the NASM working group (see below).
(B
(B4. An Endpoint Number (EN)
(B
(BYour EN can be any number and is decided by each organization. However, we recommend that it be no longer than seven digits. Each endpoint number MUST be unique within the organization. Both 305 and 1234567 are fine examples as long as they are unique.
(B
(BThe whole numeric number therefore looks like: <IAC><CC><OP><EN>
(B
(BExamples:
(B
(BThe Megaconference informal test MCU:
(B
(B00(IAC) 1(CC) 189(OP) 7201234(EN)
(B
(BTyped into your videoconferencing endpoint, the number would simply look like: 0011897201234
(B
(BThe GDS also defines an alphanumeric dial plan (not used during the Megaconference game). This part is equal to the alphanumeric dial plan of the old ViDeNet and should be in the form: <station ID>@<fully qualified domain name of the institution>
(B
(BAn example is: egon.verharen@localhost
(B
(BMore information on the GDS and the Numerical Addressing Space Management (NASM) working group overseeing its development can be found at: http://www.wvn.ac.uk/support/h323address.htm and http://www.vide.net/workgroups/nasm/index.shtml
(B
(BCourtesy of Egon Verharen
(B
(B------------------------------------------------------------------------------------------------------------------------------------------
(BH.323 Global Dialing Scheme (GDS)
(BThe Global Dialing Scheme has been adopted by a number of European Countries for H.323 interzone dialing - including Ireland, The Netherlands, Germany, Switzerland and the UK. More countries are currently being added to the system.
(BThe scheme defines 00 as an international dialing prefix and the the use of the well-known ITU-T country telephone codes. Zone prefixes and extension numbers are defined by the national managing agent - usually the National Research Network (NRN) in that country.
(B
(BE.g. To dial a conference hosted in the UK, dial 0044 01002 468 where:
(B
(B00 is the international dialing prefix
(B44 is the code for the UK
(B01002 is the zone in which the MCU hosting the test conference is registered
(B468 is the conference number
(BIt is also possible to dial existing ViDeNet numbers through systems connected to the dial plan. Dial the ViDeNet dial number as if you were connected directly to a ViDe zone. ViDe numbers usually begin with a single 0. All other numbers begin with 00.
(B
(BNote: Within your country system it may be necessary to dial an additional prefix or 'Exit Zone' prefix. This is similar to dialing 9 for an outside line from an internal telephone system. Contact your national gatekeeper manager for more information.
(B
(BThe Global Dialing Scheme uses a hierarchy of gatekeepers to route call setup information nationally and internationally. National gatekeepers have knowledge of all zones within a country, World gatekeepers have knowledge of all National gatekeepers.
(B
(BWhere a country does not have a National Gatekeeper and an institution within that country would like to join the system, it will be possible for another National Gatekeeper to act as a 'Virtual Gatekeeper' until that country has its own Gatekeeper in place. This means that the institution can have a number within its own country code from the beginning.
(B
(BIf you would like further information on connecting to the system please contact:
(B
(BEgon Verharen at Surfnet
(BVictor Reijs at HEAnet
(BSteve Williams Welsh Video Network
(B
(B --------------------------------------------------------------------------------------------------------
(BNumerical Addressing Space Management Team (NASM) Working Group
(BScope of Work: NASM is responsible the management of ViDeNet numerical address space. This group designs the numerical address space and supporting routing schemes, including E.164int integration, hierarchical and flat structures, with particular emphasis on the root level and top tier architectures. Of particular importance is the alignment of existing h.323 addressing to E.164-like structures, in order to prepare the way for an eventual migration toward full DNS-based dialing, ENUM and related numerical address translation schemes. This group is responsible for the allocation of ViDeNet address space to lower tier domains. In particular, the group identifies which organizations and research networks will be responsible for managing national gatekeepers. The group's operational responsibilities include the review of new ViDeNet membership requests, assignment of address space, and configuration of the top-level gatekeeper meshes. Members of this group will ha
(B ve root administrative access to the ViDeNet management system and all top-level gatekeepers and will ensure the integrity of data registered with ViDeNet. All address assignments made by this group are final. Architectural recommendations of this group require the support of the ViDeNet Zone Administrators.
(B
(BProject Leader: Tyler Miller Johnson
(B
(BTeam Members and Liaison Responsibilities:
(BEurope and Africa
(BSteve Williams, UKERNA (Wales)
(BVictor Reijs, HEAnet (Ireland)
(BBert Andree, SURFnet (Netherlands)
(BEgon Verharen, SURFNet (Netherlands)
(B
(BNorth and South America, Including Internet2
(BTyler Miller Johnson, University of North Carolina (US)
(BTim Poe, University of North Carolina (US)
(BMegan Crabb, Ohio State Univesity (US) Internet2 Commons - Special Liaison
(B
(BAustralia and Asia
(BStephen Kingham, AARnet (Australia)
(B
(BMembership Guidelines: Project team members are appointed by the Working Group Chair. All members of this group must be zone administrators or representatives from active ViDeNet zones. Membership terms are from January 1 to December 31 of any calendar year and terminate automatically, with the option to request renewal.
(B
(B-----------------------------------------------------------------------------------------------------------------------
(BViDeNet Root Level Architecture
(BViDeNet will adopt the hierarchical gatekeeper scheme developed by the European research and education community and described in detail at http://www.wvn.ac.uk/support/h323address.htm. This architecture will support existing and new ViDeNet users, the Internet2 Commons and international video and voice over IP deployments. The initial implementation of this hierarchy will be built around the RADVISION ECS Pro version 2 gatekeeper. A global root gatekeeper will have as children, gatekeepers associated with each country. The Numerical Address Space Management Team will manage the Global Tier, country tiers when appropriate agreements are reached with individual countries, and certain leaves as appropriate, such as the ViDeNet Public Zone and other public, shared or test resources. A RADVISION ENC tool will be used to administer the gatekeeper hierarchy. All information on the hierarchy will be stored in a database that will be accessible via secure client by mem
(B bers of the NASM team.
(B
(BIn the first iteration, a single global root will be implemented. This global root will have a live hot standby gatekeeper configured to automatically fail-over in the event of the unavailability of the primary gatekeeper. A US gatekeeper will be similarly configured to serve Internet2 and other US sites. The ViDeNet Public Zone will be configured as a leaf serving MCU resources globally and acting as test facility.
(B
(BSimultaneous to the creation of this simple, redundant hierarchy, a set of alternate gatekeepers will be implemented at both the global and country tiers. An alternate gatekeeper, with a live hot standby gatekeeper, will be implemented in Europe and Australia. These gatekeepers will be neighbored in a mesh with the global root gatekeeper in the US. This will enable country tier gatekeepers to have redundant parents in the event of a network layer problem associated with their primary parent. A similar architecture will be created on the country level in the US in support of the Internet2 Commons. It is expected that other countries will adopt a similar architecture. This mesh neighboring will also include Cisco MCM and other non-RADVISION gatekeepers as contributed by NASM team members as they can be effectively integrated into the mesh.
(B
(B
(B> -----Original Message-----
(B> From: Carsten Schiefner [
]
(B> Sent: Tuesday, September 09, 2003 12:59 PM
(B> Subject: ITU's H.350 and ENUM
(B>
(B>
(B> All,
(B>
(B> just having read an article on the final resolution on H.350, but
(B> currently not having the time to REALLY dig into the issue, I
(B> nonetheless wonder whether this would create another
(B> addressing scheme
(B> sort of in parallel to ENUM as H.350 is meant to be for video
(B> conferencing, but also for VoIP.
(B>
(B
http://www.itu.int/osg/spu/newslog/categories/internetNamesAndAddresses/2003/09/04.html#a174
(B
(BRegards,
(B
(B -C.
