1 / 6

RSVP -TE extensions for RRO editing draft-hartley-ccamp-rro-editing-00.txt

RSVP -TE extensions for RRO editing draft-hartley-ccamp-rro-editing-00.txt. Matt Hartley Zafar Ali (Presenter) Oscar Gonzalez de Dios Cyril Margaria Zhang Xian. Cisco Systems Cisco Systems Telefonica I+ D Coriant R&D GmbH Huawei.

rania
Télécharger la présentation

RSVP -TE extensions for RRO editing draft-hartley-ccamp-rro-editing-00.txt

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. RSVP-TE extensions for RRO editingdraft-hartley-ccamp-rro-editing-00.txt Matt Hartley • Zafar Ali (Presenter) Oscar Gonzalez de Dios Cyril Margaria Zhang Xian Cisco Systems Cisco Systems Telefonica I+D Coriant R&D GmbH Huawei Acknowledgment: Lou Berger and George Swallow 88th IETF, CCAMP WG, Vancouver, BC, Canada (November 2013)

  2. Requirements NNI • Policy in server network may require information in RRO be edited, summarized or removed. E.g., GMPLS UNI, inter-domain, etc. • Client nodes need to know how RRO contents has been manipulated. • RRO reduction to avoid packet fragmentation. UNI-C UNI-N NNI UNI-N UNI-C

  3. Requirements – Cont. • The requirement was identified in the following WG drafts: • SRLG Recording - draft-ietf-ccamp-rsvp-te-srlg-collect. • TE Metric Recording - draft-ietf-ccamp-te-metric-recording. • Working group feedback was to define a generic RRO-edit mechanism, which is extendable to all RRO sub-objects.

  4. RRO-edit RRO sub-object • Insert a new RRO-edit sub-object for each subobjectbeen edited. 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Type | Length | Edited type |E|P|S|R|reserve| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ • Edited type: The type of the sub-object being manipulated. • E : Edited bit – subobject(s) of edited typehas been edited in some way. • P : Partial bit – subobject(s) of edited type is known to have incomplete info. • S: Summary bit – subobject(s) of edited type has been summarized. • R: Removed bit – subobject(s) of edited typehas been removed.

  5. RRO edit example UNI-C UNI-N CN UNI-N UNI-C 10.0.0.3 10.0.0.4 10.0.0.2 10.0.0.5 RRO header RRO header RRO header RRO header Addr-sub:10.0.0.5 Addr-sub:10.0.0.4 Addr-sub:10.0.0.2 Addr-sub:10.0.0.3 SRLG-sub:1,2,3 SRLG-sub: 4,5 Edit-sub: type:IPv4, R=1 SRLG-sub: 5,6,7 Addr-sub:10.0.0.5 Edit:type:SRLG, S=1 Addr-sub:10.0.0.4 SRLG-sub:1,2,3 SRLG-sub: 9800 SRLG-sub: 4,5 Addr-sub:10.0.0.5 Addr-sub:10.0.0.5 SRLG-sub:1,2,3 SRLG-sub:1,2,3

  6. Next Steps • Work on a couple of working group documents depends on this draft. • Authors would like to request a quick call for WG adoption.

More Related