1 / 5

GMPLS Asymmetric Bandwidth Bidirectional LSPs draft-berger-ccamp-asymm-bw-bidir-lsps-00.txt

GMPLS Asymmetric Bandwidth Bidirectional LSPs draft-berger-ccamp-asymm-bw-bidir-lsps-00.txt. Lou Berger <lberger@labn.net> Attila Takacs <attila.takacs@ericsson.com> Diego Caviglia <diego.caviglia@ericsson.com> Don Fedyk <dwfedyk@nortel.com> Julien Meuric <julien.meuric@orange-ftgroup.com>.

amelia-hurley
Télécharger la présentation

GMPLS Asymmetric Bandwidth Bidirectional LSPs draft-berger-ccamp-asymm-bw-bidir-lsps-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. GMPLS Asymmetric Bandwidth Bidirectional LSPsdraft-berger-ccamp-asymm-bw-bidir-lsps-00.txt Lou Berger <lberger@labn.net> Attila Takacs <attila.takacs@ericsson.com> Diego Caviglia <diego.caviglia@ericsson.com> Don Fedyk <dwfedyk@nortel.com> Julien Meuric <julien.meuric@orange-ftgroup.com> CCAMP - 70th IETF

  2. Draft Objective • Describe the preferred way to provide asymmetric bandwidth bidirectional LSPs • Build on GMPLS bidirectional LSPs • Enable different traffic parameters for each traffic direction CCAMP - 70th IETF

  3. Revision Deltas Last Meeting: Next Steps • Answer major questions: • Technical direction: • Per technology solutions (Ethernet today) • Generalized solution • Process direction: • If required functionality  Standard • If not  Experimental • General draft update CCAMP - 70th IETF

  4. Moved to appendix Draft Solution • Draft covers two approaches: • Both versions use a single bidirectional LSP • Technology specific • Uses ADSPEC to carry traffic parameters for upstream data • Requires MEF Ethernet Traffic Parameters • Generic • Defines new upstream traffic parameter related object classes to match old downstream objects  Propose that WG only follow generic approach CCAMP - 70th IETF

  5. Next Steps • Feedback from WG • General review & update • Last call CCAMP - 70th IETF

More Related