Re: [Teas] IETF TE Topology YANG Model Design Meeting Notes - 2016-08-22

[Xufeng Liu <[e-mail]>]

Hi Xian,

Such a notification example can be:

When TE Node “node-10” is created, the server sends the following on-change notification:

<notification
      xmlns="urn:ietf:params:xml:ns:netconf:notification:1.0">
   <eventTime>2015-03-09T19:14:56Z</eventTime>
   <push-change-update xmlns=
       "urn:ietf:params:xml:ns:yang:ietf-yang-push:1.0">
     <subscription-id>89</subscription-id>
     <time-of-update>2015-03-09T19:14:56Z</time-of-update>
     <datastore-changes-xml>

       <networks xmlns="urn:ietf:params:xml:ns:yang:ietf-network">
         <network>
                  <network-id>topo-1</network-id>
                 <node urn:ietf:params:xml:ns:netconf:base:1.0:operation="create">
                    <node-id>node-10</node-id>
                  </node>
         </network>
       </networks>

     </datastore-changes-xml>
   </push-change-update>
</notification>

Regards,

- Xufeng

From: Zhangxian (Xian) [mailto:[e-mail]]
Sent: Thursday, August 25, 2016 3:03 AM
To: Xufeng Liu <[e-mail]>; Vishnu Pavan Beeram <[e-mail]>; Igor Bryskin <[e-mail]>; Oscar Gonzalez De Dios <[e-mail]>; Tarek Saad <[e-mail]>; Himanshu Shah <[e-mail]>; Lou Berger <[e-mail]>; BRUNGARD, DEBORAH A (ATTLABS) <[e-mail]>; Susan Hares <[e-mail]>; Zafar Ali (zali) <[e-mail]>; Khaddam, Mazen (CCI-Atlanta) <[e-mail]>; Tony Le <[e-mail]>; BELOTTI, SERGIO (SERGIO) <[e-mail]>; Beller, Dieter (Dieter) <[e-mail]>; Rajan Rao <[e-mail]>; [e-mail]; Belotti, Sergio (Nokia - IT) <[e-mail]>; Anurag Sharma <[e-mail]>
Cc: [e-mail]
Subject: Re: IETF TE Topology YANG Model Design Meeting Notes - 2016-08-22

Hi, Xufeng,

   With regard to the following point:
 - Clean up notifications
  We currently have notifications for te-node and te-link. These
  notifications are covered by draft-ietf-netconf-yang-push and
  draft-gonzalez-netconf-5277bis.
  We will remove these notifications from te-topology model.

The existing notification is really clear, in terms of event types. But I still cannot figure out how to use the model specified by draft-ietf-netconf-yang-push.  I wonder if you can give an example, say, how a creation of te-node can be modeled using the model provided in draft-ietf-netconf-yang-push?

Regards,
Xian

发件人: Xufeng Liu [mailto:[e-mail]]
发送时间: 2016年8月25日 3:16
收件人: Vishnu Pavan Beeram; Igor Bryskin; Oscar Gonzalez De Dios; Tarek Saad; Himanshu Shah; Lou Berger; BRUNGARD, DEBORAH A (ATTLABS); Susan Hares; Zafar Ali (zali); Khaddam, Mazen (CCI-Atlanta); Tony Le; BELOTTI, SERGIO (SERGIO); Beller, Dieter (Dieter); Rajan Rao; Zhangxian (Xian); [e-mail]<mailto:[e-mail]>; Belotti, Sergio (Nokia - IT); Anurag Sharma
抄送: [e-mail]<mailto:[e-mail]>
主题: IETF TE Topology YANG Model Design Meeting Notes - 2016-08-22

Participants:
Igor, Xufeng, Dieter, Oscar

- Connectivity matrix
  > TE path needs to be able to specify node/connectivity-matrix id, to facilitate path computation, and to support parallel connectivity-matrix entries in a node.
    This needs to be in both te-topology model and te model.
    Will bring the topic to TE model discussion meeting.
  > Agreed to add underlay TE path for each connectivity-matrix entry.

- Make LLCL entry as rich as connectivity entry, to have enough TE
  information for path computation.
 > Xufeng to prepare the model change proposal.

- Have a list of attributes to be used for technology specific augmentations.
  > Dieter to prepare the list for the meeting after Dieter is back
    from vacation.

- Schedule down time (in addition to up time)

      |  +--rw schedules
      |  |  +--rw schedule* [schedule-id]
      |  |     +--rw schedule-id            uint32
+      |  |     +--rw inclusive-exclusive?   enumeration
      |  |     +--rw start?                 yang:date-and-time
      |  |     +--rw schedule-duration?     string
      |  |     +--rw repeat-interval?       string

+        leaf inclusive-exclusive {
+          type enumeration {
+            enum inclusive {
+              description "The schedule element is inclusive.";
+            }
+            enum exclusive {
+              description "The schedule element is exclusive.";
+            }
+          }
+          description
+            "Whether the list item is inclusive or exclusive.";
+        }

- info-source: bgp-ls

    leaf information-source {
      type enumeration {
        enum "unknown" {
          description "The source is unknown.";
        }
        enum "locally-configured" {
          description "Configured entity.";
        }
        enum "ospfv2" {
          description "OSPFv2.";
        }
        enum "ospfv3" {
          description "OSPFv3.";
        }
        enum "isis" {
          description "ISIS.";
        }
+        enum "bgp-ls" {
+          description "BGP-LS.";
+          reference
+            "RFC7752: North-Bound Distribution of Link-State and
+             Traffic Engineering (TE) Information Using BGP";
+        }
        enum "system-processed" {
          description "System processed entity.";
        }
        enum "other" {
          description "Other source.";
        }
      }
      description
        "Indicates the source of the information.";
    }

- Clean up notifications
  We currently have notifications for te-node and te-link. These
  notifications are covered by draft-ietf-netconf-yang-push and
  draft-gonzalez-netconf-5277bis.
  We will remove these notifications from te-topology model.

- Need to complete counters/statistics. Each of us will think about
  what attributes are needed.
  > number of operational links/tunnels
  > number of recoverying links/tunnels
  > number of protection switches
  > number of protection reversions

Thanks,

- Xufeng

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