Re: [mpls] I-D Action: draft-ietf-mpls-static-yang-08.txt
Tarek Saad <tsaad.net@gmail.com> Fri, 08 March 2019 18:14 UTC
Return-Path: <tsaad.net@gmail.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 762AC131386 for <mpls@ietfa.amsl.com>; Fri, 8 Mar 2019 10:14:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, 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 q_kZzKvcIzN0 for <mpls@ietfa.amsl.com>; Fri, 8 Mar 2019 10:14:24 -0800 (PST)
Received: from mail-it1-x130.google.com (mail-it1-x130.google.com [IPv6:2607:f8b0:4864:20::130]) (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 CFE03131375 for <mpls@ietf.org>; Fri, 8 Mar 2019 10:14:23 -0800 (PST)
Received: by mail-it1-x130.google.com with SMTP id z124so22669314itc.2 for <mpls@ietf.org>; Fri, 08 Mar 2019 10:14:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:thread-topic:thread-index:date:message-id :references:in-reply-to:accept-language:content-language :content-transfer-encoding:mime-version; bh=nirG/3LskGUN6EcQTZkfwRUTqrrr/voJWsNAzQNHWKk=; b=oYPJdV+F/e6gKEdlWu8aEHYzczKPKUsK+9FyGZBCJGGq2y1AsmY6/iyth4COe2g3jk N4tRnPM1KB+16TDCkf+/gDHIO3hhAi5dSfccpliv4j3hHMJf4Jq4gjwyQOEh7y3uBYN/ ppIcqJqRCKM9M/vcSieX3EntN6Gpf0/VwqdDjHWxiL6DnXyvrge26DtbEecbC6vpYNcT qo8yVWiNZFxP7EbvIxSgnCulp29G6fejLYYLpB2U/NEg7Jk+SN3K1DzcALRkhsS8EcOB vDnUFv7Y8Nmi3JaCSScH9wrjmr33izDOwy++D/AgC1WdUPicptwpUALPSi1sNAYPnM7u gDqg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:thread-topic:thread-index :date:message-id:references:in-reply-to:accept-language :content-language:content-transfer-encoding:mime-version; bh=nirG/3LskGUN6EcQTZkfwRUTqrrr/voJWsNAzQNHWKk=; b=iwJR+uPBeq7PHkEZIywKDjl5Dt0RtISCZnOawkfuJTahyRUeS1IanRFLn5HIWGpI5c lOyJxgUcU4Psff+fWIeibgr4wmYpfHUiC7YNBxCsQkJKmoFD2GAZPuC7wz7U/1AzCEz2 RY5Gt+TLSlRA05RMluloVmUTugFdp+6M+gDvvH/fusD+8C3LQ/sdcaRab47INDwjSH14 h73++SKZl/ihVp3l1Igw6MTPqkwUD10tBcuxyi6H9apMbK7uNOwaC9vBy8O9lJ99e94J c5V8e4rodOLoTnZxrVEryj+mQPO1Gx+bB1On2JxgECIDC83at1Ej4YCJvgbENt8M31Xu iieQ==
X-Gm-Message-State: APjAAAU4kLBhGSCx4RbUztJBbpgmkWj/L7piMKyHHmQKEu18IWdtJawZ Dg9ZOeAglUuUQ99T+ssdx5U=
X-Google-Smtp-Source: APXvYqz98GZrN6XnKv4AByLZ6S8vl2msFRtC9cp66THbe6KdL9V8CjBzY6FjagQyKGbwLf0u6eKGLA==
X-Received: by 2002:a24:4161:: with SMTP id x94mr8675155ita.69.1552068863142; Fri, 08 Mar 2019 10:14:23 -0800 (PST)
Received: from BN8PR06MB6289.namprd06.prod.outlook.com ([52.96.29.13]) by smtp.gmail.com with ESMTPSA id w19sm4195929ita.33.2019.03.08.10.14.22 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 08 Mar 2019 10:14:22 -0800 (PST)
From: Tarek Saad <tsaad.net@gmail.com>
To: tom petch <ietfc@btconnect.com>
CC: "mpls@ietf.org" <mpls@ietf.org>
Thread-Topic: [mpls] I-D Action: draft-ietf-mpls-static-yang-08.txt
Thread-Index: ATU5OTU3dRXcZeBagFJxXtYijmNCZjAwMTkxd0pWZXMwMDQzMbh77TeT
X-MS-Exchange-MessageSentRepresentingType: 1
Date: Fri, 08 Mar 2019 18:14:21 +0000
Message-ID: <BN8PR06MB62890074D29EA4440AC6F170FC4D0@BN8PR06MB6289.namprd06.prod.outlook.com>
References: <155155736768.27158.1653954565392604255@ietfa.amsl.com> <016901d4d379$a1e91e60$4001a8c0@gateway.2wire.net> <CAHVfGYrtzs_Q+7Q1v2yeTmhjKRMarVZOD_1kynOJVxHFcpmZVw@mail.gmail.com> <068601d4d4e3$c5dc4980$4001a8c0@gateway.2wire.net>
In-Reply-To: <068601d4d4e3$c5dc4980$4001a8c0@gateway.2wire.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-Exchange-Organization-SCL: -1
X-MS-TNEF-Correlator:
X-MS-Exchange-Organization-RecordReviewCfmType: 0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/cE29hKapOzByBDVAKKEFNiyV9oE>
Subject: Re: [mpls] I-D Action: draft-ietf-mpls-static-yang-08.txt
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: Fri, 08 Mar 2019 18:14:27 -0000
Hi Tom, Thanks. We'll unify to "Mbps" and keep this consistent in units and description. Regards, Tarek On 3/7/19, 7:48 AM, "tom petch" <ietfc@btconnect.com> wrote: Tarek One point I keep noticing but do not think I have raised before is units mbps; description "Bandwidth in Mbps, I have known systems fail because one party was using mbps, another Mbps, so seeing a mix of the two, as here, raises a flag for me. I note that draft-ietf-teas-yang-te-types has units "Mbps"; which I prefer - if they really mean Mbps and not mbps; I have my doubts! - but then draft-ietf-l2sm-l2vpn-service-model-10 has units "mbps"; default "10"; description "LACP speed. By default, the lacp speed is 10Mbps."; Perhaps in the context of MPLS there is no ambiguity but it would be nice to have consistency at least within an I-D. Tom Petch ----- Original Message ----- From: "Tarek Saad" <tsaad.net@gmail.com> Sent: Wednesday, March 06, 2019 2:53 PM > Hi Tom, > > As usual, thanks for your review on this one and for your patience. More > Inline.. > > On Tue, Mar 5, 2019 at 12:36 PM tom petch <ietfc@btconnect.com> wrote: > > > A long and winding road! > > > > module ietf-mpls-static { > > ..... > > import ietf-routing-types { > > prefix "rt-types"; > > reference "RFC8294: Common YANG Data Types"; > > > > I see, in the RFC Index, > > > > 8294 Common YANG Data Types for the Routing Area. > > i.e. a different title > > > > [TS]: yes, unfortunately a deja vu (fixed in another module). We'll take > care of this in the new version. > > > > > module ietf-mpls-static-extended { > > .... > > import ietf-routing { prefix "rt"; > > reference "RFC6991: Common YANG Data Types"; > > I suggest > > reference "RFC8349: A YANG Data Model for Routing Management"; > > > > [TS]: yes, will take of this. > > reference "RFC XXXX: Extended YANG Data Model for MPLS Static LSPs"; > > um - I see this I-D as titled > > A YANG Data Model for MPLS Static LSPs > > > > [TS]: OK for this one too. > > Regards, > Tarek > > > > > > Tom Petch > > > > > > ----- Original Message ----- > > From: <internet-drafts@ietf.org> > > To: <i-d-announce@ietf.org> > > Cc: <mpls@ietf.org> > > Sent: Saturday, March 02, 2019 8:09 PM > > > > > A New Internet-Draft is available from the on-line Internet-Drafts > > directories. > > > This draft is a work item of the Multiprotocol Label Switching WG of > > the IETF. > > > > > > Title : A YANG Data Model for MPLS Static LSPs > > > Authors : Tarek Saad > > > Rakesh Gandhi > > > Xufeng Liu > > > Vishnu Pavan Beeram > > > Igor Bryskin > > > Filename : draft-ietf-mpls-static-yang-08.txt > > > Pages : 18 > > > Date : 2019-03-02 > > > > > > Abstract: > > > This document contains the specification for the MPLS Static Label > > > Switched Paths (LSPs) YANG model. The model allows for the > > > provisioning of static LSP(s) on Label Edge Router(s) LER(s) and > > > Label Switched Router(s) LSR(s) devices along a LSP path without > > the > > > dependency on any signaling protocol. The MPLS Static LSP model > > > augments the MPLS base YANG model with specific data to configure > > and > > > manage MPLS Static LSP(s). > > > > > > > > > The IETF datatracker status page for this draft is: > > > https://datatracker.ietf.org/doc/draft-ietf-mpls-static-yang/ > > > > > > There are also htmlized versions available at: > > > https://tools.ietf.org/html/draft-ietf-mpls-static-yang-08 > > > https://datatracker.ietf.org/doc/html/draft-ietf-mpls-static-yang-08 > > > > > > A diff from the previous version is available at: > > > https://www.ietf.org/rfcdiff?url2=draft-ietf-mpls-static-yang-08 > > > > > > > > > Please note that it may take a couple of minutes from the time of > > submission > > > until the htmlized version and diff are available at tools.ietf.org. > > > > > > Internet-Drafts are also available by anonymous FTP at: > > > ftp://ftp.ietf.org/internet-drafts/ > > > > > > _______________________________________________ > > > I-D-Announce mailing list > > > I-D-Announce@ietf.org > > > https://www.ietf.org/mailman/listinfo/i-d-announce > > > Internet-Draft directories: http://www.ietf.org/shadow.html > > > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt > > > > _______________________________________________ > > mpls mailing list > > mpls@ietf.org > > https://www.ietf.org/mailman/listinfo/mpls > > >
- [mpls] I-D Action: draft-ietf-mpls-static-yang-08… internet-drafts
- Re: [mpls] I-D Action: draft-ietf-mpls-static-yan… tom petch
- Re: [mpls] I-D Action: draft-ietf-mpls-static-yan… Tarek Saad
- Re: [mpls] I-D Action: draft-ietf-mpls-static-yan… tom petch
- Re: [mpls] I-D Action: draft-ietf-mpls-static-yan… Tarek Saad
- Re: [mpls] I-D Action: draft-ietf-mpls-static-yan… Tarek Saad
- Re: [mpls] I-D Action: draft-ietf-mpls-static-yan… tom petch
- Re: [mpls] I-D Action: draft-ietf-mpls-static-yan… Tarek Saad