Skip to content

Home

Jump to bottom Edit New page
ietf-mpls-yang edited this page Jan 7, 2015 · 9 revisions

MPLS-TE YANG Model.

Welcome to the IETF MPLS-TE YANG model wiki.

Meeting Information:

  • Meeting A - Every other Thursday, starting 12/10 Meeting Number: 302215356 Webex: URL

  • Meeting B - Every other Wednesday, starting 12/04 Meeting Number: 201725919 Webex: URL

Past Meetings:

Meeting 3 - Wednesday 12/18 @ 7:00pm EST

Minutes:

  1. Based on feedback from last TEAS WG interim meeting, need to migrate generic work to TEAS:

    • by generic it's meant dataplane agnostic (MPLS/GMPLS) not necessarily control plane agnostic
    • possibility of remarking xx-mpls-te.yang to -te-xx.yang

  2. Xia: have implementation where SDN is used to compute a TE path (for IP-TE). BGP is used for doing Traffic-Engineering. MED? path-attributes? to base the path Susan: BGP has flow classification... refer to draft-ietf-idr-te-pm-bgp-01

AI: Pavan to investigate

  1. AI: Tarek to look at what from RSVP-TE should move to RSVP yang model

  2. tentative module list: ietf-xx-te-types.yang ietf-xx-te-base.yang (DP independent) ietf-mpls-te-base.yang (DP packet MPLS specific) (e.g.) ietf-gmpls-otn-te.yang, flex-grid, ethernet ... (outside scope) Zafar: will work on technology-specific GMPLS, e.g. OTN ietf-te-rsvp.yang ietf-rsvp

  3. Pavan: Should TE links be configured under a routing instance?

    • links can be configured for multiple routing protocols
    • Consider the case when running the same TE link under multiple routing instance ** If TE link configuration is under the routing instance, the TE link attributes may have to be replicated under each routing instance ** Alternatively, TE link attributes can be configured once (decoupled from routing instance) and have the TE link refernced under each routing instance
  • layered topologies
  • to review the base netmod-routing-cfg instances -- Susan: investigate drawbacks of putting the links/interface list under the routing instance. Susan: PBR for TE.

Meeting 2 - Wednesday 12/10 @ 7:00pm EST

Meeting Summary

  • team progressed with TE link data model

    1. In addition to the reference models (non-final), the following models were created and checked-in:
    • ietf-mpls-te.yang
    • ietf-mpls-te-types.yang
    • ietf-mpls-te-rsvp.yang

  • Work-in-progress for TE link model was discussed

    • Base MPLS-TE link data reperesentation to be added in ietf-mpls-te.yang
    • RSVP-TE specific link data extensions to be added in ietf-mpls-te-rsvp.yang
    • Common grouping to go in iet-mpls-te-types.yang. Other models can import and reuse.

  • Team to review the checked-in of the models above and make modifications as needed.

    • to discuss changes/additions in next meeting

  • Discussed possibility of having the top of the MPLS-TE tree off a routing instance

  • Tools

  • Next steps/AIs:

    • Team: to review/add/update link data node in the model Pavan will share comments.

  • To use if-feature for vendor specific supported features

  • RSVP Yang model

    • The point of defining RSVP groupings and an RSVP (non-TE) YANG model was discussed a. Need to be able to enable RSVP on interface for non-TE (e.g. IPv4 flows) b. May require defining module in ietf-rsvp.yang. Module ietf-mpls-te-rsvp.yang can import

  • AIs: to send email to alias and ask for WG-chair's thoughts on expanding scope to include ietf-rsvp.yang module

Meetings:

Meeting 1 - Thursday 12/4 @ 7:00pm EST

Meeting Summary

A group of us (from above) met on Thursday 12/4 for the first time to discuss MPLS TE YANG model. Below are minutes/notes. Next meeting is scheduled for next Wednesday 12/10.

  • Next steps/AIs:
    • Team: to check-in all existing YANG models to GitHub: https://github.com/ietf-mpls-yang/te
    • Team: phase 1 to tackle links and link attributes for phase 1
      • team to communicate proposed attributes over email.
      • in-progress model for TE links will be discussed next week
    • Team: to use email to send proposals
    • Tarek: to send an email with minutes to the WG group
      • include invitations for next meetings
    • Tarek: to schedule weekly meeting for next wednesday onwards

Recording of meeting @ https://cisco.webex.com/ciscosales/lsr.php?RCID=7a824854ae304230ab579f6977974239

Meeting minutes/Notes:

  • Meeting organization/time (do we need to meet more often?)

    • Meet weekly,
    • OK to keep Thursday 7:00pm EST
    • Poll for next weekly meeting Wednesday 7:00pm EST
    • Consideration for holidays

  • Scope of our work:

    • MPLS TE YANG model: TE base yang types TE base yang model RSVP-TE extensions to TE base yang model
    • MPLS Tunnels/links: Config, operational/state, notification, rpcs
    • Topology (proposal to handle in another effort in TEAS)

  • Do we need an alias to communicate/send queries?

    • use mpls WG alias as long as manageable (not noisy)
    • may create another alias to use too

  • Agree on tools/process:

    • repository in GitHub: https://github.com/ietf-mpls-yang/te
      • check-in all yang models to date:
        • tagged iet-mpls-te-(1/2/3).yang
      • create ietf-mpls-te.yang
        • to include sanitized/agreed data model to be presented at IETF
      • create common draft draft-common-mpls-te-yang-model
    • review/commit process?
      • Need to converge

  • Divide the work into phases

    • ph1: TE Links: link attributes (local TE links)

      • Admin Groups, Extended Admin Groups (config)
      • SRLGs (config)
      • local/remote identifiers (config)
      • reservable bandwidth (config)
        • RSVP per interface properties
        • etc.
      • CAC (state) -- LSPs admitted on the link

    • ph2: TE Tunnels:

    • ph3: TE LSPs

    • ph4: TE Globals/templates properties

  • Revisit MPLS Yang module(s) hierarchy. Proposal:

+ ietf-mpls-base-types.yang
       |
       + -- ietf-mpls-ldp-types.yang (imports mpls-base-types)
       + -- ietf-mpls-te-types.yang  (imports mpls-base-types)
       + -- ietf-mpls-te-pce-types.yang  (imports mpls-base-types)
       + -- etc.
+ ietf-mpls-base.yang
     + -- ietf-mpls-te-base.yang (augments ietf-mpls-base.yang)
              + -- ietf-mpls-te-rsvp.yang (augments ietf-mpls-te-base.yang)
              + -- ietf-gmpls-te.yang (augments ietf-mpls-te-base.yang ? augments ietf-mpls-te-rsvp.yang, both ?)
                    - encoding types (PSC, LSC, FSC, etc.)?
                    - OTN/Optical
+ ietf-mpls-oam
    - the MPLS OAM YANG model (to augment MPLS-TE model whenever needed)
  • Where does MPLS data plane YANG state sit?
    • In respective MPLS Yang models — identified with data plane distinguisher (?)
    • data/control plane state and data plane state may not be in sync always (e.g. in transient post FRR)

How to pull

You can download the yang code in a tar ball or zip bundle:

$ cd your_repo_root/repo_name
$ git fetch origin
$ git checkout gh-pages
Add a custom footer
Add a custom sidebar
Clone this wiki locally