[Teas] Updates in draft-ietf-teas-yang-te-topo-19

Xufeng Liu <xufeng.liu.ietf@gmail.com> Thu, 07 March 2019 14:10 UTC

Return-Path: <xufeng.liu.ietf@gmail.com>
X-Original-To: teas@ietfa.amsl.com
Delivered-To: teas@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B3DD0127873 for <teas@ietfa.amsl.com>; Thu, 7 Mar 2019 06:10:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rZuT8CNEJQBg for <teas@ietfa.amsl.com>; Thu, 7 Mar 2019 06:10:50 -0800 (PST)
Received: from mail-it1-x135.google.com (mail-it1-x135.google.com [IPv6:2607:f8b0:4864:20::135]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 489CC124184 for <teas@ietf.org>; Thu, 7 Mar 2019 06:10:50 -0800 (PST)
Received: by mail-it1-x135.google.com with SMTP id v2so15396411ith.3 for <teas@ietf.org>; Thu, 07 Mar 2019 06:10:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=3jx8LOmVO7/CMHXpWxnCnqYWLG5PTlVqOZ3IbP82ePs=; b=vPs2CY9EXOI0sqFMgzLOeGDeNqvZmlBm/SAIllms+NUB/CUUBjuJyqI+POzs5Qasm7 hW0h8gYBkWxZaxc/fTvnb71lMz6Khd2fl3uoCbQxFiLcRxKp7JaalF5jZAZv52Q5gHct HuGBXQ/myqaHmF3PIaevCElxC6/Eoy/6xh2FbBsq01a11+4GvWXQYLCGiXIG0rWX33Gr BJFKuYBkyL5K0+830Z2YOwTtY2ous6UkGr84+OezhSSFWQ21CflH030qFfpjh/SRXDqd yHVJXWK2IUjXfJNx+ybp0e6Kawdg3w3djjUt6rTk2cWOETM1KtgjLg0gbWtFULtWZEDj HIqg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=3jx8LOmVO7/CMHXpWxnCnqYWLG5PTlVqOZ3IbP82ePs=; b=fPlxEQLkpjFiELXg1u99Vd0gcLCSLiViJeWfISCJqoxFq6mHIuHTQJLZ6MYKzXFM8+ cO+YKarp+liWI3j8VbWKfnUZiXi2IrGai4za5kuW6KT9gd2+jcawQhmFk4B0Q1XYHisj nCV69HNEM11DyiVc2rjRFTVY2rUxrV9i3rY0jKc1UwCyl1A3Ezvd7MpIbrYx84cy7iD8 Fz9d/BBZvFBs6uFcSiJE9eh25SDA9J81fofyMJwTsrQQvkBAP9oY9nmmds1r6+T0NLHI 6JaUHDKw6Jd4lfZXF/qB/Cb0U2Y5/ZjIUdlYT712gU0UjTxEuRfzrSOybnz+6HAR3I6T QrEw==
X-Gm-Message-State: APjAAAU6AJuEB60zUk61A42ClmfjROG4UhTkZkvy6Y/NrqtXzHW1Ak6e ytoK+2K8ESgQvDvrBZtjXUTQ7cHKthcB8oBsKGoEloSXVqQ=
X-Google-Smtp-Source: APXvYqxXBoY4AGS16YMalv/zskeWPszOWZLF3IUxQeQ0jJrkk2CG8ECUUBu5W4jdBRvjVWL0slIbTRB1zcoSSzkM3rI=
X-Received: by 2002:a02:781:: with SMTP id f123mr7574030jaf.133.1551967849408; Thu, 07 Mar 2019 06:10:49 -0800 (PST)
MIME-Version: 1.0
From: Xufeng Liu <xufeng.liu.ietf@gmail.com>
Date: Thu, 7 Mar 2019 09:10:38 -0500
Message-ID: <CAEz6PPRqHeG-vsUuBM172Cxbf5T6azXhwMkSWokf=_eiZw6JXg@mail.gmail.com>
To: TEAS WG <teas@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000005deec6058381acd9"
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/sQ2wMTXYXwniUujt29fysqHwwpI>
Subject: [Teas] Updates in draft-ietf-teas-yang-te-topo-19
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <teas.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/teas>, <mailto:teas-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teas/>
List-Post: <mailto:teas@ietf.org>
List-Help: <mailto:teas-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/teas>, <mailto:teas-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Mar 2019 14:10:53 -0000

As discussed in previous IETF meeting sessions, the YANG module ietf-te-types
has been moved from draft-ietf-teas-yang-te to draft-ietf-teas-yang-te-types.
Such a change allows us to move draft-ietf-teas-yang-te-topo forward
without waiting for draft-ietf-teas-yang-te, even though
draft-ietf-teas-yang-te-topo depends on the module ietf-te-types. We have
just updated draft-ietf-teas-yang-te-topo with
https://tools.ietf.org/html/draft-ietf-teas-yang-te-topo-19 to use the
module ietf-te-types in draft-ietf-teas-yang-te-types instead of
draft-ietf-teas-yang-te. The changes are:

- Used te-types:te-topology-identifier
  The grouping te-topology-identifier is now defined in ietf-te-types.
ietf-te-topology now uses this grouping for consistency.

- Used te-types:link-protection-type
  The identify link-protection-type has been defined in ietf-te-types.
ietf-te-topology now uses this new identity instead of defining its own
enumeration.

- Used te-types:objective-function-type
  The identify te-optimization-criterion in ietf-te-types has been renamed
to objective-function-type. ietf-te-topology now uses this new identity.

In addition, authors have received some implementation feedback regarding
the information-source in the model. There were use-cases where the
TE-topology is learned via different instances of the same source protocol
(different instances of the same IGP). We have introduced the following
changes in the model:

- Fixed information-source, by adding an additional leaf to indicate the
instance of the information source.

The differences introduced in the YANG model file are:
--- ietf-te-topology@2018-06-15.yang    2018-06-16 22:11:58.304834200 -0400
+++ ietf-te-topology@2019-02-07.yang    2019-02-08 12:16:04.591228810 -0500
@@ -17,8 +17,8 @@
   import ietf-te-types {
     prefix "te-types";
     reference
-      "I-D.ietf-teas-yang-te: A YANG Data Model for Traffic
-       Engineering Tunnels and Interfaces";
+      "I-D.ietf-teas-yang-te-types: Traffic Engineering Common YANG
+       Types";
   }

   import ietf-network {
@@ -61,7 +61,7 @@
     "TE topology model for representing and manipulating technology
      agnostic TE Topologies.

-     Copyright (c) 2018 IETF Trust and the persons identified as
+     Copyright (c) 2019 IETF Trust and the persons identified as
      authors of the code.  All rights reserved.

      Redistribution and use in source and binary forms, with or
@@ -74,7 +74,7 @@
      This version of this YANG module is part of RFC XXXX; see the
      RFC itself for full legal notices.";

-  revision "2018-06-15" {
+  revision "2019-02-07" {
     description "Initial revision";
     reference "RFC XXXX: YANG Data Model for TE Topologies";
   // RFC Ed.: replace XXXX with actual RFC number and remove
@@ -243,7 +243,14 @@
       type te-info-source;
       config false;
       description
-        "Indicates the source of the information.";
+        "Indicates the type of the information source.";
+    }
+    leaf information-source-instance {
+      type string;
+      config false;
+      description
+        "The name indicating the instance of the information
+         source.";
     }
     container information-source-state {
       config false;
@@ -270,7 +277,14 @@
       type te-info-source;
       config false;
       description
-        "Indicates the source of the information.";
+        "Indicates the type of the information source.";
+    }
+    leaf information-source-instance {
+      type string;
+      config false;
+      description
+        "The name indicating the instance of the information
+         source.";
     }
     container information-source-state {
       config false;
@@ -785,25 +799,8 @@
     uses te-types:label-set-info;

     leaf link-protection-type {
-      type enumeration {
-        enum "unprotected" {
-          description "Unprotected.";
-        }
-        enum "extra-traffic" {
-          description "Extra traffic.";
-        }
-        enum "shared" {
-          description "Shared.";
-        }
-        enum "1-for-1" {
-          description "One for one protection.";
-        }
-        enum "1-plus-1" {
-          description "One plus one protection.";
-        }
-        enum "enhanced" {
-          description "Enhanced protection.";
-        }
+      type identityref {
+        base te-types:link-protection-type;
       }
       description
         "Link Protection Type desired for this link.";
@@ -952,7 +949,7 @@
     }
     uses information-source-per-link-attributes;
     list information-source-entry {
-      key "information-source";
+      key "information-source information-source-instance";
       config false;
       description
         "A list of information sources learned, including the one
@@ -1338,7 +1335,7 @@
     }
     uses information-source-per-node-attributes;
     list information-source-entry {
-      key "information-source";
+      key "information-source information-source-instance";
       config false;
       description
         "A list of information sources learned, including the one
@@ -1604,26 +1601,12 @@
   grouping te-topology-augment {
     description
       "Augmentation for TE topology.";
-    leaf provider-id {
-      type te-types:te-global-id;
-      description
-        "An identifier to uniquely identify a provider.";
-    }
-    leaf client-id {
-      type te-types:te-global-id;
-      description
-        "An identifier to uniquely identify a client.";
-    }
-    leaf te-topology-id {
-      type te-types:te-topology-id;
-      description
-        "It is presumed that a datastore will contain many
-         topologies. To distinguish between topologies it is
-         vital to have UNIQUE topology identifiers.";
-    }
+    uses te-types:te-topology-identifier;

     container te {
-      must "../provider-id and ../client-id and ../te-topology-id";
+      must "../te-topology-identifier/provider-id"
+        + " and ../te-topology-identifier/client-id"
+        + " and ../te-topology-identifier/topology-id";
       presence "TE support.";
       description
         "Indicates TE support.";
@@ -1655,7 +1638,7 @@
     }
     leaf optimization-criterion {
       type identityref {
-        base te-types:te-optimization-criterion;
+        base te-types:objective-function-type;
       }
       description
         "Optimization criterion applied to this topology.";

Thanks,
- Xufeng