[mpls] Structure of draft-ietf-mpls-static-yang

tom petch <ietfc@btconnect.com> Tue, 13 November 2018 12:37 UTC

Return-Path: <ietfc@btconnect.com>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 62AF81276D0; Tue, 13 Nov 2018 04:37:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.196
X-Spam-Level: ***
X-Spam-Status: No, score=3.196 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RATWARE_MS_HASH=2.148, RATWARE_OUTLOOK_NONAME=2.95, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=btconnect.onmicrosoft.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 sHVICSVpy4n6; Tue, 13 Nov 2018 04:37:54 -0800 (PST)
Received: from EUR04-DB3-obe.outbound.protection.outlook.com (mail-eopbgr60126.outbound.protection.outlook.com [40.107.6.126]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D62D8126DBF; Tue, 13 Nov 2018 04:37:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btconnect.onmicrosoft.com; s=selector1-btconnect-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=efCetUx9EZVMGshQE/QVnw8O2qaCOTNZ3cazWz/yaMw=; b=WxoRL+iJ9nnMtk6iH1yfk0uf+syyYA0SD809bLZpYYYXYRgfUEYzcF7r+1tQoWS9O6qrRLuqZPA1PhKhuQKNOo5swsKkVBZ8Z0UZdnft9QAd7w5OGyL4aDy3LDbwMKbt5NckGmHgS7JGVITgzQWJmHD/9kwmhuHW+T0jIlEA180=
Received: from VI1PR07MB5022.eurprd07.prod.outlook.com (20.177.202.206) by VI1PR07MB4191.eurprd07.prod.outlook.com (20.176.6.28) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1339.11; Tue, 13 Nov 2018 12:37:50 +0000
Received: from VI1PR07MB5022.eurprd07.prod.outlook.com ([fe80::929:bd11:beb6:b887]) by VI1PR07MB5022.eurprd07.prod.outlook.com ([fe80::929:bd11:beb6:b887%3]) with mapi id 15.20.1339.021; Tue, 13 Nov 2018 12:37:50 +0000
From: tom petch <ietfc@btconnect.com>
To: "Tarek Saad (tsaad)" <tsaad@cisco.com>, mpls <mpls@ietf.org>
CC: "draft-ietf-mpls-base-yang@ietf.org" <draft-ietf-mpls-base-yang@ietf.org>
Thread-Topic: Structure of draft-ietf-mpls-static-yang
Thread-Index: AQHUe02wlCMgQUKxOkmdNrRJZT0IYw==
Date: Tue, 13 Nov 2018 12:37:50 +0000
Message-ID: <060801d47b4d$730cbd60$4001a8c0@gateway.2wire.net>
References: <151871655164.7468.17697751302068907872@ietfa.amsl.com> <03b001d3a714$5e08dce0$4001a8c0@gateway.2wire.net> <A7C87BD7-A6E5-474F-9D19-F3B9A6F83DA4@cisco.com> <001001d4767d$62fb1a40$4001a8c0@gateway.2wire.net> <00c901d478f6$25a75c00$4001a8c0@gateway.2wire.net>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-clientproxiedby: CWLP265CA0169.GBRP265.PROD.OUTLOOK.COM (2603:10a6:401:4d::13) To VI1PR07MB5022.eurprd07.prod.outlook.com (2603:10a6:803:9b::14)
authentication-results: spf=none (sender IP is ) smtp.mailfrom=ietfc@btconnect.com;
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: [86.128.101.213]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; VI1PR07MB4191; 6:oLBSqInbnGKGRQti+E43hpCL13eK1jYc+hdZseovor6k12CCpHXCf1rA6vaPoTkLidMurjyBTrJ5JkS+HUpICfBBBYrpym1baZAJag8bs43DMWvd4dJD4AQ5SZYfP331QTv+Kn0E+LVova6k42/OU6nzwoYEn/Qo56mDacolSwto66M66JVsARzwMwg2/OGZp4ui/2qpFxbox/Z/gO9M013krDeY0tMOeue9t46InrhW4ns/r3rcyWdSZQ8mogbvZJDbNbs0NgxaKawWTelhQpHX9pd88RB088bAOh85scGVKYN00G8X8KZHLKTG6zPEfTBDrpRSRYhSpATIf5mfpsMcgDSk2v3gblfN3ZRse3EOu0Qpz0641DgJ63WFlZbYQfCzCGVx9kavLq8sRri9QEuYajB4mHO9pi+xMgEo5AnMlEev1Eikkb7FmpYVdcPwxrWu6T4GmbisYgqX7BI3lA==; 5:gR1Je8fzqFttajNP6ls4LIj71AWQl6zgnu3C1ZrjwuSmsnrzIOCs2Lgl9RzhhrtGToVsKQ/5Z/RGAzt13Fii3hqnmRxkOBoopE/tanWFdgP0TnEjg0ZcU5ENgKv/HJm0CQ6DXOfN8UCy6HmsVyUPAb2d3J6g7Fv0XOXJKXbBB3I=; 7:udGayLbb3lS2Zahgvaj/hVYrn0SngJMMQP8M8oaU0sYwFT4N4ofDaS9g51U2OHxc4lKeqxHyKzKy+CbbnKM2IoApRhowC9FHy6ZAEBYxOyTLU1L146KtUsxI5+TEC0qhYj2gGnhhfItnw2+UMmAQtA==
x-ms-office365-filtering-correlation-id: ab4b32ef-5cc8-4d8b-06bc-08d64964d2e5
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390060)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600074)(711020)(2017052603328)(7193020); SRVR:VI1PR07MB4191;
x-ms-traffictypediagnostic: VI1PR07MB4191:
x-microsoft-antispam-prvs: <VI1PR07MB419163C87E4D3AEAB14AE5CBA0C20@VI1PR07MB4191.eurprd07.prod.outlook.com>
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040522)(2401047)(5005006)(8121501046)(93006095)(93001095)(10201501046)(3002001)(3231382)(944501410)(52105112)(6055026)(148016)(149066)(150057)(6041310)(20161123558120)(20161123564045)(20161123560045)(20161123562045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(201708071742011)(7699051)(76991095); SRVR:VI1PR07MB4191; BCL:0; PCL:0; RULEID:; SRVR:VI1PR07MB4191;
x-forefront-prvs: 085551F5A8
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(376002)(39860400002)(396003)(366004)(136003)(346002)(54094003)(199004)(189003)(102836004)(2906002)(476003)(446003)(99286004)(84392002)(6116002)(386003)(6506007)(76176011)(26005)(3846002)(5660300001)(33896004)(2900100001)(81156014)(81166006)(8676002)(53936002)(71200400001)(71190400001)(105586002)(8936002)(486006)(52116002)(186003)(106356001)(14454004)(6486002)(14496001)(1556002)(86362001)(256004)(305945005)(44736005)(68736007)(4326008)(9686003)(6512007)(316002)(478600001)(110136005)(86152003)(6436002)(97736004)(93886005)(25786009)(66066001)(7736002); DIR:OUT; SFP:1102; SCL:1; SRVR:VI1PR07MB4191; H:VI1PR07MB5022.eurprd07.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:0; MX:1;
received-spf: None (protection.outlook.com: btconnect.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: HtizDWR8aiPPTMzGW00UKI/tN2wBgmG0cNIX8Qzi4MZrpeOjN35+b6D5va2zhgmqSq9ieX7UeWMO2IKxmIZ+U50Ng5jbIjBw5hAypxqAllhwBol9xxq9WbkU46K7ExjyA3nwLjK6Ab/6v5cF1IR/Bvc0VAvVUzTZoh+/5Dq+hRq/4XMmRv1maTWII49c8YOM73PqJK5BGSW9D++vhJCvmjIlese9fAz9XU2tWtPdlDc66DET2hHGZJjCkFQoxwYujm2rCdk9Y2FvvCrGSsW0MKJoaBAjxSUUR9t5/hZnq29KZoGaPI1YYWvQ7WyFeqyENXhoxvbScB9ud3v6wIUZVEyMaMRex8J0vV7cq+nFPiM=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-ID: <BEB949C8D162D9468110576B3405935B@eurprd07.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-Network-Message-Id: ab4b32ef-5cc8-4d8b-06bc-08d64964d2e5
X-MS-Exchange-CrossTenant-originalarrivaltime: 13 Nov 2018 12:37:50.6410 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: cf8853ed-96e5-465b-9185-806bfe185e30
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR07MB4191
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/sr5Wc1TBlmPB9Lp7s7e_kaR6ggs>
Subject: [mpls] Structure of draft-ietf-mpls-static-yang
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mpls/>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Nov 2018 12:37:57 -0000

I wonder if the IETF has yet worked out how to model routing protocols.
I asked, what is MPLS?  Looking at various modules, I see

RIP
     augment /routing/control-plane-protocols/control-plane-protocol:
       +--rw rip
          +--rw interfaces

OSPF
     augment /routing/control-plane-protocols/control-plane-protocol:
       +--rw ospf
          +--rw areas
          |  +--rw area* [area-id]
          |     +--rw interfaces

the other IxxxGP
  module: ietf-ixxx
    augment /routing/ribs/rib/routes/route:
      +--ro route-type?   enumeration
    augment /interfaces/interface:
      +--rw clns-mtu?   uint16
    augment /routing/control-plane-protocols/:control-plane-protocol:
      +--rw ixxx
         +--rw enable?                   boolean {admin-control}?
         +--rw system-id?                system-id
         +--rw area-address*             area-address

BGP
     augment "/routing-policy/defined-sets"
    module ietf-bgp {
           +--rw bgp!
             +--rw global
                +--rw afi-safis
                   +--rw afi-safi* [afi-safi-name]
                      +--rw ipv4-unicast
                      +--rw ipv6-unicast
                      +--rw l3vpn-ipv4-unicast

PIM
module: ietf-pim-base
     augment /routing/control-plane-protocols:
       +--rw pim!
          +--rw address-family* [address-family]
          |  +--rw address-family        identityref
          |  +--rw <per address family configuration>
          +--rw interfaces
             +--rw interface* [name]
                +--rw name              if:interface-ref
                +--rw address-family* [address-family]

MPLS

module: ietf-mpls
  augment /rt:routing:
    +--rw mpls
  augment /routing/ribs/rib/routes/:route:
    +--ro local-label?   rt-types:mpls-label
  augment
/routing/ribs/rib/routes/route/next-hop/next-hop-options/simple-next-hop
:
 ....
  identity mpls { base address-family;

Different! which is right?  Perhaps none of them.  It is very early days
for routing YANG modules, no RFC, limited experience.  I am mindful that
it took several years after the publication of the initial system YANG
modules for the advent of NDMA - a radically different approach - so
perhaps in a few years we will be looking at the routing modules and say
it needs a different approach.  Sigh

Tom Petch