1 AII Types for Aggregation draft-metz-aii-aggregate-00.txt Chris Metz, Luca Martini, Florin Balus, Jeff Sugimoto, Paris IETF

2 Scenario Provisioning Model: Selective Inter-Domain VPWS –provider triggers circuit (i.e. PW) signaling based on customer demand –PWE3 signaling must carry fully-qualified end-point identifier (i.e. TAI) U-PE 1 AS #1 S-PE 2 S-PE 3 AS #2 U-PE 4 U-PE 5 U-PE 6 source PE target PE set C1C1 C4C4

3 Issues 1.Scalability: distributing O(# of candidate target AIIs) will stress AII distribution (e.g. MP-BGP) machinery and PE memory 2.Security: source U-PE1 is prohibited from learning IP addresses of candidate target PE set. Implication: can’t route PWE3 setups based on target U-PE IP address U-PE 1 AS #1 S-PE 2 S-PE 3 AS #2 U-PE 4 U-PE 5 U-PE 6 source PE Candidate Target AIIs 1. AII Distribution 2. Target PE /32 loopbacks

4 What’s Needed Define new AII Type: –enables many discrete AIIs to be summarized into a single or few AII aggregates (note: PW routing based on AII aggregates is needed) –option for global uniqueness –AII numbering flexibility – based on IPv4, IPv6, NSAP or other circuit addressing scheme –conformant with PWE3 FEC129 signaling semantics

5 Short Prefix AII Type Defined in Section 2.1 of draft Multiple levels of aggregation possible (see draft for examples) Affinity with IPv4 –e.g. auto-generate discrete AII values from PE /32 loopback Optional Attachment Circuit ID (AC ID) included to further refine identification of a particular attachment circuit AII Type = 01 Length Global ID Prefix (32-bits) AC ID

6 Long Prefix AII Type Defined in Section 2.2 of draft Hold longer prefixes (e.g. IPv6, NSAP or even IPv4) –e.g. useful if provider’s existing circuit-provisioning NMS uses NSAP addressing AC ID not defined because there are enough bits in prefix field AII Type = 02 Length Global ID Prefix (256-bits)

7 Final Comments Selective VPWS provisioning model warrants AII aggregation for scalability MS-PW is a signaling *AND* routing problem –when explicit paths not used or target U-PE address is not reachable, then PW routing must be based on something else Next Steps: –Refinements: Use Route Distinguisher as Global ID? Both types needed? –Sync up with MS-PW signaling and routing efforts