Subject: [Teas] IETF TE Topology YANG Model Design Meeting Notes - 2016-12-14

From: Xufeng Liu <[email-masked]>
Date: Tue, 20 Dec 2016 22:46:18 +0000

Attendees:
Igor, Xufeng, Sergio, Pavan

- Continued discussion on the naming for MDLG.
  > use NSRLG.
  > Indicates the easy to understand concept completely opposite to SRLG.
  > Configuring abstract TE link has the NSRLG requirements.
    When configuring an abstract TE topology, how a client can
    articulate that given n TE links should be mutually SRLG disjoint,
    with their respective underlay TE paths unknown and to be dynamically
    or semi-dynamically computed?
  > When a TE link is configured with NSRLG, the intent is to have
    this link to be independent (not to share fate, risk) with other TE
    links within the same group. This independence is expected to be
    ensured by the provider with TE tunnel supporting the link taking
    path in the underlay topology diverse from the paths taking by the
    TE tunnels supporting other TE links within the same NSRLG.

- Proposed modeling changes:

augment /nw:networks/nw:network/nt:link:
   +--rw te!
      +--rw config
      |  +--rw te-link-attributes
      |     +--rw access-type?                      te-types:te-link-access-type
      |     +--rw external-domain
      |     |  +--rw remote-te-node-id?      te-types:te-node-id
      |     |  +--rw remote-te-link-tp-id?   te-types:te-tp-id
      |     |  +--rw plug-id?                uint32
      |     +--rw is-abstract?                      empty
      |     +--rw name?                             string
      |     +--rw underlay! {te-topology-hierarchy}?
      |     +--rw admin-status?                     te-types:te-admin-status
      |     +--rw link-index?                       uint64
      |     +--rw administrative-group?             te-types:admin-groups
      |     +--rw interface-switching-capability* [switching-capability]
      |     +--rw link-protection-type?             enumeration
      |     +--rw max-link-bandwidth?               te-bandwidth
      |     +--rw max-resv-link-bandwidth?          te-bandwidth
      |     +--rw unreserved-bandwidth* [priority]
      |     |  +--rw priority     uint8
      |     |  +--rw bandwidth?   te-bandwidth
      |     +--rw te-default-metric?                uint32
      |     +--rw te-delay-metric?                  uint32
      |     +--rw te-srlgs
      |        +--rw value*   te-types:srlg
+      |     +--rw te-nsrlg {nsrlg}?
+      |        +--rw id*   uint32

augment /nw:networks/nw:network:
   +--rw provider-id?      te-types:te-global-id
   +--rw client-id?        te-types:te-global-id
   +--rw te-topology-id?   te-types:te-topology-id
   +--rw te!
      +--rw config
      |  +--rw preference?               uint8
      |  +--rw optimization-criterion?   identityref
+      |  +--rw nsrlg* [id] {mdlg}?
+      |     +--rw id              uint32
+      |     +--rw disjointness?   enumeration {none, node, link, srlg}

- Based on implementation feedbacks, we will do the following fixes:
  > Add topology-id to
               +--rw external-domain
               |  +--rw remote-te-node-id?      te-types:te-node-id
               |  +--rw remote-te-link-tp-id?   te-types:te-tp-id

  > Add missing supporting tunnel-ttp on to tunnel-ttp

  > Make underlay tunnel-id rw
  > In underlay, add a flag to request to be shared or dedicated.

- Discussed and agreed to add default attributes for connectivity matrix:

augment /nw:networks/nw:network/nw:node:
   +--rw te-node-id?   te-types:te-node-id
   +--rw te!
      +--rw config
      |  +--rw te-node-template*     leafref {template}?
      |  +--rw te-node-attributes
      |     +--rw admin-status?          te-types:te-admin-status
+     |     +--rw connectivity-matrices
+              +--rw number-of-entries       // requested number of entries
+        |     +--rw default-attrs           // defaults
+        |     +--rw connectivity-matrix* [id]

- Logistics
  > We will cancel our weekly meetings for the next two weeks.
  > We will resume our weekly meetings from Jan 4, 2017

Thanks,
- Xufeng

Note: Please drop me an email if you need an invite for joining the weekly call.