Beta Draft Confidential
About SVCs
Address Formats
ATM Services Configuration Guide for CBX 3500, CBX 500, GX 550, and B-STDX 9000 1/19/0516-7
Native E.164 Address Format
Native E.164 addresses are the standard Integrated Services Digital Network (ISDN)
numbers, including telephone numbers. Native E.164 addresses consist of 1-15 ASCII
digits. For example, standard 10-digit United States telephone numbers, such as
508-555-1234, are native E.164 addresses.
Unlike AESA address formats, native E.164 addresses are not broken down into AFI,
HO-DSP, ESI, and SEL portions. When a native E.164 address is translated to E.164
AESA format, the native E.164 address is stored in octets 2-9 of the 20-octet AESA
address, while the HO-DSP, ESI, and SEL portions are filled with zeros. Conversely,
when an E.164 AESA address is translated to the native E.164 address format, the
AFI, HO-DSP, ESI, and SEL portions, as well as any leading zeros in the 8-octet
AESA E.164 address, are stripped off to produce the native E.164 address.
Designing an Address Format Plan
The SVC address formats you select must support the equipment and services your
network needs to provide. Keep in mind that some CPEs may not support certain
address formats. To avoid address conflicts, apply for globally-recognized address
space in the ATM formats you need to use.
You use address formats to develop a network numbering plan. Using an AESA
address, you can design the IDP portion of an address to target a specific network;
then use the HO-DSP portion of the address to identify subnetworks within that
network, and use the ESI portion to identify a specific end system.
Regardless of the address format you choose, the network numbering plan should
satisfy the following goals:
• Intelligently assign network addresses
• Simplify network topology using a hierarchal organization
• Minimize the size of network routing tables
• Uniquely identify each endpoint
• Provide a high level of network scalability
To Next Page
Loading...
