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

From: Xufeng Liu <[email-masked]>
Date: Thu, 9 Jun 2016 15:24:30 +0000

Participants:
Igor, Xufeng, Pavan, Dieter, Sergio, Anurag, Rajan, Pawel K

- Information sources
  > Continued last week's discussion on information source, and agreed
    on the following change: ( "<" indicates new)

      |  +--ro information-source?         enumeration
      |  +--ro information-source-state
      |  |  +--ro credibility-preference?   uint16
      |  |  +--ro topology
      |  |  |  +--ro provider-id-ref?      leafref
      |  |  |  +--ro client-id-ref?        leafref
      |  |  |  +--ro te-topology-id-ref?   leafref
      |  |  |  +--ro network-id-ref?       leafref
      |  |  +--ro routing-instance?         string
<       |  +--ro information-source-entry* [information-source]
---
>       |  +--ro alt-information-sources* [information-source]

- Connectivity Matrix
  > Continued last week's discussion on label restrictions.
  > Model options: (option 2 is preferred as for now)
Option 1:
+--rw inclusive-label*[label-start]
    +--rw label-start
    +--rw label-end?
    +--rw range-bitmap?

+--rw exclusive-label*[label-start]
    +--rw label-start
    +--rw label-end?
    +--rw range-bitmap?

Option 2:
+--rw inclusive-label*[label-start, inclusive-exclusive]
    +--rw inclusive-exclusive
    +--rw label-start
    +--rw label-end?
    +--rw range-bitmap?

Option 3:
+--rw inclusive-label*[label-start, label-end]
    +--rw label-start
    +--rw label-end
    +--rw inclusive-exclusive?
    +--rw range-bitmap?

  > Some features specified in RFC7579 are for WSON and will be left
    for technology specific augmentations.

- Based on mailing list feedbacks, label restrictions will also be
  applied to TTP LLCL. The same model grouping will be used.

- Discussed optmization options (cost, delay)
  > Agreed to add the option to the topology entity. The option is not
    added to other entities such as link and node because of the lack of
    use case support.
  > The values can be: cost, delay

- SR topology and SR TE topology
  > Discussed the hierachy and relations between SR topology, SR
    TE topology and the base TE topology:
l3-topo:
/nw:networks/nw:network/nw:network-types/l3-unicast-igp-topology

l3-te:
/nw:networks/nw:network/nw:network-types/l3-unicast-igp-topology/l3-te

sr:
/nw:networks/nw:network/nw:network-types/l3-unicast-igp-topology/sr
add info source

sr-te: (multiple inheritance)
/nw:networks/nw:network/nw:network-types/l3-unicast-igp-topology/l3-te
/nw:networks/nw:network/nw:network-types/l3-unicast-igp-topology/sr

 > Will schedule a separate meeting for further detailed discussions.
  > Will work with SPRING WG.

- TE topology and SFC topology
  > Will schedule a separate meeting to discuss the relations between
    TE topology and SFC topology.
  > Will work with I2RS WG.

Thanks,

- Xufeng

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