1 / 6

VCAT/LCAS and GMPLS

VCAT/LCAS and GMPLS. Greg Bernstein (Grotto) Diego Caviglia (Ericsson/Marconi) Richard Rabbat (Fujitsu) Huub van Helvoort (Huawei) Lyndon Ong (Ciena) Wataru Imajuku (NTT) Julien Meuric (France Telecom) IETF 66: Montréal. Table of Contents. Background reading

nishan
Download Presentation

VCAT/LCAS and GMPLS

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. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. VCAT/LCAS and GMPLS Greg Bernstein (Grotto) Diego Caviglia (Ericsson/Marconi) Richard Rabbat (Fujitsu) Huub van Helvoort (Huawei) Lyndon Ong (Ciena) Wataru Imajuku (NTT) Julien Meuric (France Telecom) IETF 66: Montréal

  2. Table of Contents • Background reading draft-bernstein-ccamp-gmpls-vcat-lcas-03.txt • Changes from -02 • Extending GMPLS to support diversely routed LSPs • Association object • Next steps

  3. Background reading • A number of vendors, carriers have initiated this work • The draft includes documentation of the function performed by VCAT and LCAS • The advances in data transport now allow good support for diversely routed SONET paths • LCAS also allows hitless resizing of the VCAT group (zero dropped traffic)

  4. Changes from -02 • Added one more author (Huub) • Dropped section about advertising VCAT and LCAS capability. • This change is due to the amount of information that would need to be advertised. • VCAT capability at the interface comprises a lot of information, which make advertising not very scalable. For example, a node could perform an adaptation using two interfaces lying on different line cards but that's not necessarily always the case. • This update to the draft expects the use of an outside entity in selecting the right destinations.

  5. Association object • Used to associate the diversely routed LSPs Association Type: 16 bits Value Type ----- ---- 3 VCAT group Association ID: 16-bit value, so we can have up to 2^16 associations, meaning up to 2^16 diversely routed VCAT groups and any number of co-routed LSPs. • May use the same PathErr message with "Traffic Control Error/ Service unsupported" indication

  6. Next Steps • Authors feel that the draft is stable and is now ready to be CCAMP WG draft

More Related