Re: ason-routing-reqts: issue 1 addressing

[Jonathan Sadler <jonathan.sadler@tellabs.com>]

Hi Kireeti -

Let me try and correct what may be a misperception...

Kireeti Kompella wrote:

> On Tue, 16 Mar 2004, Ong, Lyndon wrote:
> > 3) the client system may use a non-IP address for compatibility
> > reasons, for example, a client with an existing management plane
> > address that the carrier wants to access without having to
> > add a new address and translation mechanism.

<snip>

> For point 3, I view Recommendation 7713.1 which (in my faint
> recollection) has only PNNI addressing, and in particular does not
> have IP addressing, as suggesting that it is NOT a requirement that
> a given solution cater to all possible address types.  So, while this
> might a nice-to-have, it certainly doesn't seem to be an ASON
> requirement.  If you think otherwise, please let me know --
> Recommendation number & section.

G.7713.1 does not include any special procedures to handle IPv4 and IPv6
addressing because special procedures are unnecessary.   The NSAP addresses
used in G.7713.1 are meta-addresses that incorporate a number of addresses
formats, including IPv4 and IPv6.  This is accomplished through the Address
Format Identifier (AFI) octet that exists at the begining of the NSAP
address format.  AFIs have been defined by ISO/IEC for IPv4 and IPv6 --
therefore the procedures for handling IPv4 and IPv6 addresses in G.7713.1
already exist.

For more information on NSAPs, including all the AFIs allocated, please see
ISO/IEC 8348:1996 and ISO/IEC 8348:1996 Amd.1, available free of charge at:

http://www.iso.org/iso/en/ittf/PubliclyAvailableStandards/s027728_ISO_IEC_8348_1996(E).zip


http://www.iso.org/iso/en/ittf/PubliclyAvailableStandards/c030507_ISO_IEC_8348_1996_Amd_1_1998(E).zip

It should be noted that this standards based approach is different than the
_experimental_ approach taken in RFC 1888.  Since NSAP addresses are
variable length, and allow for lengths longer than any of the address spaces
incorporated, there is no loss of information when using an NSAP version of
an IPv4 or IPv6 address.  Contrast this to RFC 1888, where new addresses are
defined in the IPv6 for each NSAP addressed endpoint, and a mapping function
must be used to do a translation.  This is necessary as IPv6 addresses are
too short to accommodate every NSAP.

Consequently, special procedures (ie. new objects) were necessary in
G.7713.2 and G.7713.3 to fully accommodate NSAP addresses.

Jonathan Sadler



-----------------------------------------
============================================================
The information contained in this message may be privileged 
and confidential and protected from disclosure.  If the 
reader of this message is not the intended recipient, or an 
employee or agent responsible for delivering this message to 
the intended recipient, you are hereby notified that any 
reproduction, dissemination or distribution of this 
communication is strictly prohibited. If you have received 
this communication in error, please notify us immediately by 
replying to the message and deleting it from your computer.

Thank you.
Tellabs
============================================================