Re: [mpls] MPLS label and LSE data models

Greg Mirsky <gregimirsky@gmail.com> Tue, 06 June 2017 00:43 UTC

Return-Path: <gregimirsky@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 815EF12EB57; Mon, 5 Jun 2017 17:43:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.999
X-Spam-Level:
X-Spam-Status: No, score=-0.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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLACK=1.7] autolearn=no 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 4w5YuYkIBjef; Mon, 5 Jun 2017 17:43:40 -0700 (PDT)
Received: from mail-oi0-x230.google.com (mail-oi0-x230.google.com [IPv6:2607:f8b0:4003:c06::230]) (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 C916D12EB58; Mon, 5 Jun 2017 17:43:40 -0700 (PDT)
Received: by mail-oi0-x230.google.com with SMTP id o65so146960214oif.1; Mon, 05 Jun 2017 17:43:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=6UsQ/B0nxm6VwpE0RMVEHnHV1VQXphzl/G8tiAk+vYE=; b=NDoib/d4GZMO6Ld+RaBCHgz5r1DKORpPeyGqQbP6i8rvRGVb7loZySVw6pwIA+MVrs 0btjwnm4/XFSXv4lQqFwf6ez0ulkSXwO9D9/WImpX7fd2j++PrLcHWKSN0BLabpQGfOs bdLzJOby7XZMRu7s/eabddZNZKEbgTHtJj1Lb0DN4yOB7tLqvAGqLzwEr8PH3GnMvThu 89mpL/DFbImgqVrWG1XKZePqBHmix/D3zRvW/Oof3viDP4N+8djweDMuU9WBDvWhq+VF VxiyrhllQtxppUQC09Etzsum0Tk8g3KHa6BE1LtKmDIHwl7QfLj25IiGwuXazUCsP1by nA9g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=6UsQ/B0nxm6VwpE0RMVEHnHV1VQXphzl/G8tiAk+vYE=; b=ENSIH2h1JAa3zBKi/VvJjHbnG0MVzYiG12Uo1vdki5esqwZgYDmMNdldlxDiK+LjYi SAwLwKgmi1N8LPT3uK6iLBDyRYFiaAanURpiXu2uDGFfzOsh67g/pWu3lDxsH+TVEbo2 kVZP9niP60raMqcr0ivP2iIZuaeZmvis55IBVtfSXKP5k9nm7gnbYfTX2zIUexvHfru3 5wCixo65WDMOGtPLF49QjtBnGGVPNJkCx2UAga67Mwn0s2c2zFGYNLRfRV2s/veOq4oK 9dWeraRFQ/RsEOUQyJSaxEwgWyixG9APGOrU9Uvwntf/f54y+4YPyPho+0qcTptTV/yr KMnw==
X-Gm-Message-State: AODbwcDrS+mUEb231R2TJ0RPqqW2s0YI14s5lNa43UX3WfbqvK1iA0FM RldfBZ6i3ZmQYs6gWrWzaQp8NRi/lw==
X-Received: by 10.202.83.213 with SMTP id h204mr12559987oib.59.1496709820146; Mon, 05 Jun 2017 17:43:40 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.157.52.225 with HTTP; Mon, 5 Jun 2017 17:43:39 -0700 (PDT)
In-Reply-To: <D55B6659.B21B8%acee@cisco.com>
References: <CA+RyBmVH=KCi3T8u2dB_WaKBOLheYwT4q0d+tpYdT-Z2iTZ+og@mail.gmail.com> <D55B6659.B21B8%acee@cisco.com>
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Mon, 05 Jun 2017 17:43:39 -0700
Message-ID: <CA+RyBmVyHKGhxitGgQ6RRMmHKwvs=b_GkKMq80rE=Ys8WetGaQ@mail.gmail.com>
To: "Acee Lindem (acee)" <acee@cisco.com>
Cc: "draft-ietf-rtgwg-routing-types@ietf.org" <draft-ietf-rtgwg-routing-types@ietf.org>, "draft-ietf-mpls-static-yang@ietf.org" <draft-ietf-mpls-static-yang@ietf.org>, "rtgwg@ietf.org" <rtgwg@ietf.org>, "mpls@ietf.org" <mpls@ietf.org>
Content-Type: multipart/alternative; boundary="001a113d66b2296c4005513fe9ca"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/ShIC3gYAXgOy-sf8VEmTjBZc7vs>
Subject: Re: [mpls] MPLS label and LSE data models
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.22
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, 06 Jun 2017 00:43:42 -0000

Hi Acee,
I think rather of the contrary, Static MPLS LSP must include TC and TTL.
And Bottom-of-the-stack flag as well (I don't see it in grouping
mpls-label-stack
of the ietf-routing-types).

Regards,
Greg

On Mon, Jun 5, 2017 at 4:55 PM, Acee Lindem (acee) <acee@cisco.com> wrote:

> Greg, et al,
>
> From: Greg Mirsky <gregimirsky@gmail.com>
> Date: Monday, June 5, 2017 at 6:28 PM
> To: "draft-ietf-rtgwg-routing-types@ietf.org" <draft-ietf-rtgwg-routing-
> types@ietf.org>, "draft-ietf-mpls-static-yang@ietf.org" <
> draft-ietf-mpls-static-yang@ietf.org>
> Cc: Routing WG <rtgwg@ietf.org>, "mpls@ietf.org" <mpls@ietf.org>
> Subject: MPLS label and LSE data models
> Resent-From: <alias-bounces@ietf.org>
> Resent-To: Yingzhen Qu <yingzhen.qu@huawei.com>, <xufeng_liu@jabil.com>,
> Acee Lindem <acee@cisco.com>, Christian Hopps <chopps@chopps.org>, <
> lberger@labn.net>
> Resent-Date: Monday, June 5, 2017 at 6:28 PM
>
> Dear Authors, et.al,
> I've got a question, or several of them, about data models of MPLS label
> and MPLS label stack element (LSE). I ahve not followed the discussions and
> apologize if these already were considered, discussed.
> In the Routing Types document I've found that only MPLS label being
> modeled but not the MPLS LSE. As result, models that use
> rt-types:mpls-label, e.g. YANG DAta Model for MPLS Static LSPs, defines
> outgoing labels not as array of LSEs but as array (leaf-list) of MPLS
> labels. In the latter document I don't see how TTL and Traffic Class (TC)
> are presented for each of labels in the array. Hence my questions:
>
>    - should there be data model of MPLS LSE in rt-types (it does have TTL
>    and TC but separately);
>
>
>    - should data model of Static MPLS LSP use MPLS LSE model rather than
>    model of only 20 bit-long label.
>
> Where else so you see  a requirement for a label stack with entries that
> don’t contain TC and TTL? This seems specific to static provisioning of
> static LSPs rather than a general requirement for ietf-routing-types.
>
> Thanks,
> Acee
>
>
> Appreciate you comments.
>
> Regards,
> Greg
>
>