Subject: [Idr] One AFI for ATM-related addresses

From: "Busschbach, Peter B (Peter)" <[email-masked]>
Date: Fri, 17 Sep 2004 09:44:59 -0400

Draft-ck-bgp-atm-nlri-00.txt proposes to use MP-BGP to exchange ATM address information between independent ATM sub-networks. In particular, it proposes to use a single AFI/SAFI combination (AFI=TBD; SAFI=VPN) and to use an "ATM Reachability Type" field in the NLRI to distinguish between different types of ATM addresses: NSAP, E.164, etc.

After this draft was presented in San Diego, we received questions why there is a need for a new AFI considering that there are already existing AFIs for NSAP, E.164 and X.121.

We would like to solicit input from the mailing list on this issue.

In our opinion, the use of a new AFI/SAFI value for a combination of ATM addresses is justified. ATM is used as the unifying protocol for carrying Frame Relay, SMDS and other traffic. As a consequence, over time, ATM has incorporated multiple address families like X.121, SMDS-related addresses and vendor-proprietary addresses. In fact, PNNI messages use an "ATM AFI" to distinguish between these different address families, and Call Control functionality in ATM Switches generally uses a single address data base integrating different types of addresses.

For this reason, as far as MP-BGP is concerned, it makes more sense to treat all addresses exchanged between ATM Switches as a single family, rather than as a collection of separate families. Or, in other words, it makes more sense to use a single AFI/SAFI value than to use multiple.

As we are currently working on a new version of the draft, we would appreciate your input on whether we can move ahead with our proposal for a new AFI/SAFI for ATM addresses.

Thanks,

CK,
Chris Metz,
Peter Busschbach

_______________________________________________
Idr mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/idr