Aii types for aggregation draft metz aii aggregate 00 txt
Download
1 / 7

AII Types for Aggregation draft-metz-aii-aggregate-00.txt - PowerPoint PPT Presentation


  • 84 Views
  • Uploaded on

AII Types for Aggregation draft-metz-aii-aggregate-00.txt. Chris Metz, [email protected] Luca Martini, [email protected] Florin Balus, [email protected] Jeff Sugimoto, [email protected] Paris IETF. Scenario. target PE set. source PE. Provisioning Model: Selective Inter-Domain VPWS

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about ' AII Types for Aggregation draft-metz-aii-aggregate-00.txt' - gina


An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
Aii types for aggregation draft metz aii aggregate 00 txt

AII Types for Aggregationdraft-metz-aii-aggregate-00.txt

Chris Metz, [email protected]

Luca Martini, [email protected]

Florin Balus, [email protected]

Jeff Sugimoto, [email protected]

Paris IETF


Scenario
Scenario

target PE

set

source PE

  • 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-PE4

C4

AS #2

AS #1

C1

U-PE5

U-PE1

S-PE2

S-PE3

U-PE6


Issues
Issues

Candidate Target AIIs

source PE

  • Scalability: distributing O(# of candidate target AIIs) will stress AII distribution (e.g. MP-BGP) machinery and PE memory

  • 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

1. AII Distribution

U-PE4

AS #2

AS #1

U-PE5

U-PE1

S-PE2

S-PE3

U-PE6

2. Target PE

/32 loopbacks


What s needed
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


Short prefix aii type
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

AC ID

Length

Prefix (32-bits)

AII Type = 01

Global ID


Long prefix aii type
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

Length

Prefix (256-bits)

AII Type = 02

Global ID


Final comments
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


ad