Re: [mpls] I-D Action: draft-andersson-mpls-open-dt-questions-00.txt

Sergey Fomin <ietf@sergey.dev> Mon, 17 May 2021 17:00 UTC

Return-Path: <ietf@sergey.dev>
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 5EBAD3A3FF6 for <mpls@ietfa.amsl.com>; Mon, 17 May 2021 10:00:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.093
X-Spam-Level:
X-Spam-Status: No, score=-2.093 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=sergey.dev
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 DIVUCtM2o_4B for <mpls@ietfa.amsl.com>; Mon, 17 May 2021 10:00:14 -0700 (PDT)
Received: from forward103j.mail.yandex.net (forward103j.mail.yandex.net [5.45.198.246]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 936AE3A3FF3 for <mpls@ietf.org>; Mon, 17 May 2021 10:00:14 -0700 (PDT)
Received: from myt5-8d25db0e1b73.qloud-c.yandex.net (myt5-8d25db0e1b73.qloud-c.yandex.net [IPv6:2a02:6b8:c12:12b:0:640:8d25:db0e]) by forward103j.mail.yandex.net (Yandex) with ESMTP id 9FBFC6741A8F; Mon, 17 May 2021 20:00:11 +0300 (MSK)
Received: from myt4-1dda227af9a8.qloud-c.yandex.net (myt4-1dda227af9a8.qloud-c.yandex.net [2a02:6b8:c00:3c83:0:640:1dda:227a]) by myt5-8d25db0e1b73.qloud-c.yandex.net (mxback/Yandex) with ESMTP id O1f9O26gEg-0BKeA9he; Mon, 17 May 2021 20:00:11 +0300
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sergey.dev; s=mail; t=1621270811; bh=aY4uc/TUUKujsH6YnPBWR14MmkBMmWls+l31c1iPn0I=; h=Subject:Date:References:To:From:Message-ID:In-Reply-To; b=Yi6jw/anyGd2nABf1VjrznUrqF+9rdWFEqZTD5Gc9U2fASEml59LMg70rO/N9hvqq jj8+EPhj/xoSmJH7ISNWVNR1cJW9Zf5fBVAWec0QXd1R+bIlOZJNtI3RV9Dw7fK3yG 3Syb7jUBJve/+bNnuPfnoYQfPV+3lWxTLyEiOc2Q=
Authentication-Results: myt5-8d25db0e1b73.qloud-c.yandex.net; dkim=pass header.i=@sergey.dev
Received: by myt4-1dda227af9a8.qloud-c.yandex.net (smtp/Yandex) with ESMTPSA id IojwVaVH6F-08LKsTv3; Mon, 17 May 2021 20:00:10 +0300 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client certificate not present)
From: Sergey Fomin <ietf@sergey.dev>
To: 'Jeff Tantsura' <jefftant.ietf@gmail.com>, 'mpls' <mpls@ietf.org>, 'loa Andersson' <loa@pi.nu>, 'Stewart Bryant' <stewart.bryant@gmail.com>
References: <161968317610.20664.11107844270215068679@ietfa.amsl.com> <EDE7FDFB-4063-443D-BB72-C13238D22235@gmail.com> <0be3c175-1145-4c9d-a889-fa85d5732ec2@Spark>
In-Reply-To: <0be3c175-1145-4c9d-a889-fa85d5732ec2@Spark>
Date: Mon, 17 May 2021 10:00:06 -0700
Message-ID: <00db01d74b3e$18767170$49635450$@sergey.dev>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_00DC_01D74B03.6C192010"
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQGvQUfijzxX4zVhvp6ppEZJ9RUgGAFQ9rM4AiyLOVerHAzSgA==
Content-Language: en-us
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/z7zMhqOmVTlIJ5K3NJ3HVEsWL88>
Subject: Re: [mpls] I-D Action: draft-andersson-mpls-open-dt-questions-00.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: Mon, 17 May 2021 17:00:20 -0000

Hi Jeff,

 

> ERLD(Entropy Readable Label Depth)-MSD  is defined in draft-ietf-isis-mpls-elc and should be used to advertise readable label stack depth.

Not in a general case though.

As you may remember, there were quite a few discussions around the definition of RLD/ERLD for rfc8662 & drafts isis/ospf-mpls-elc, and the (rough) consensus settled on a strict, application specific definition & usage of ERLD, not a generic RLD.

 

--

Sergey

From: mpls <mpls-bounces@ietf.org> On Behalf Of Jeff Tantsura
Sent: Thursday, May 13, 2021 8:31 PM
To: mpls <mpls@ietf.org>; loa Andersson <loa@pi.nu>; Stewart Bryant <stewart.bryant@gmail.com>
Subject: Re: [mpls] I-D Action: draft-andersson-mpls-open-dt-questions-00.txt

 

Loa,

RFC8491/RFC8476/RFC8814 provide IGP/BGP-LS framework to signal HW capabilities wrt abilities to push/read label stacks.

Please use common terminology - read instead of scan.
ERLD(Entropy Readable Label Depth)-MSD  is defined in draft-ietf-isis-mpls-elc and should be used to advertise readable label stack depth.
 

 

Cheers, 

Jeff

On Apr 29, 2021, 3:26 AM -0700, Stewart Bryant <stewart.bryant@gmail.com <mailto:stewart.bryant@gmail.com> >, wrote:





2.1.3. Does flooding om maximum scanning depth of an LSR scale?

A remedy for the issues in Section 2.1.1 has been suggested, the
maaximum scanning depth for each LSR in the network should be flooded
to all othr LSRs and used as a constraint when setting up LSPs.

Would that scale satisfactorily.

Hi Loa

That is a duplicate of 2.1.2 and I think we can answer that as yes.

It is one additional capability field (no more than a byte) to flood and I find it hard to imagine that it would not scale.

Best regards

- Stewart








On 29 Apr 2021, at 08:59, internet-drafts@ietf.org <mailto:internet-drafts@ietf.org>  wrote:


A New Internet-Draft is available from the on-line Internet-Drafts directories.


Title : MPLS Open Design Team Questions
Author : Loa Andersson
Filename : draft-andersson-mpls-open-dt-questions-00.txt
Pages : 4
Date : 2021-04-29

Abstract:
This document is a living document, meaning that during the life
timme of the MPLS Open Design Team we will put additonal questions/
issues into the document. When we find an answer amd a way to
document the issu it will be removed from this document.

Ideally when the Design Team is closed this document will be empty,
or maybe we just add a pointer to where the answer to quesstion is
documented. Thus this document will never go on to become an RFCc.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-andersson-mpls-open-dt-questions/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-andersson-mpls-open-dt-questions-00
https://datatracker.ietf.org/doc/html/draft-andersson-mpls-open-dt-questions-00


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 <mailto: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 <mailto:mpls@ietf.org> 
https://www.ietf.org/mailman/listinfo/mpls