From nobody Thu Apr 29 03:26:08 2021 Return-Path: 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 74EB73A391D for ; Thu, 29 Apr 2021 03:26:07 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.098 X-Spam-Level: X-Spam-Status: No, score=-2.098 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, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, 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 GyHNUwa8WjcN for ; Thu, 29 Apr 2021 03:26:04 -0700 (PDT) Received: from mail-wr1-x42e.google.com (mail-wr1-x42e.google.com [IPv6:2a00:1450:4864:20::42e]) (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 8E0913A391A for ; Thu, 29 Apr 2021 03:26:04 -0700 (PDT) Received: by mail-wr1-x42e.google.com with SMTP id n2so13161675wrm.0 for ; Thu, 29 Apr 2021 03:26:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=Dr72h2OMiHoEZUwYUJOCq4UOhd59Mpb+YYK6BdTEnk8=; b=T9qtAYv8UUqsiXQ+IbjjxX5ya9K7z+YKHFBVTGQm0+J8oSCgPOB9A39FXNaA1GZDQO HqvfgvmRIiHx2rHV4zx+CcThOadt+ggNHcSO//kUycV20VzYHxuY1yuIRVT6xFQuLpKb 6DtaO/qrgnAJBQzsWddu75txu5PoTzz7HR4ThWOMXcgUXg9pMblMu2wFAGlVh8fdOGHk Z7bvSQol4g3dzHoh5+YEyhDDwobfnuElUlMFmRtAKsOjywIMRE7+Xa0kzgsCzAwR01ng eKRSdxNCKUxL2pVbe4xm0Mlk3qyZ02polmxigry3eNfVBfBbaJs46j0MxtauKSkj2Klz lwaA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=Dr72h2OMiHoEZUwYUJOCq4UOhd59Mpb+YYK6BdTEnk8=; b=ZH0G/tBvYLlL2X90RT6ZcJG1Fwr7SfIDT+WehNoPhnxV1ZQROFv1x4qN6hzysrXsyS jhNgoYWycxyL9Cyja4wZaK4lLzrTQ24a50mv5JnOmjO81ALnaOqqIiqyiuhk1LQmEvVE jcLV9yc/7pSnwOaTJoE61qSPuw4jrTrtRMw0EliMADMy682N3tzkeL+TV1nYThLKK9xt HCNgswiBvklNDbI40hCXBbK4CFWtmTqO8RSkiOnvhbW8V9xLd8NzALD74dwcwStwtaK3 Nt32iTC3iTtAU9yypw6IDDe9QY3kx7yd7b1pVFRMrryVc4dQzj4DCJfMR8YMN18frPDK vNuA== X-Gm-Message-State: AOAM532nDwoSCKahQnfFEVOwSbAGY/bw5B95C58ygQ91Rnw7ju2Tla4O V5HftwJ9KWpjUKewYS5u5l0ucwUv6e+m8g== X-Google-Smtp-Source: ABdhPJwbJDRU+KwMuNCM7BAtgIEdBla5WxZrmVS4ZqqVv9vUoQLI9bNxBKaVDY+/OX0jvtDMPza2sg== X-Received: by 2002:adf:f8c8:: with SMTP id f8mr28347227wrq.267.1619691961587; Thu, 29 Apr 2021 03:26:01 -0700 (PDT) Received: from broadband.bt.com ([2a00:23c5:3395:c901:78e6:3f82:75f2:207d]) by smtp.gmail.com with ESMTPSA id i11sm4149174wrp.56.2021.04.29.03.26.00 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 29 Apr 2021 03:26:01 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.6\)) From: Stewart Bryant In-Reply-To: <161968317610.20664.11107844270215068679@ietfa.amsl.com> Date: Thu, 29 Apr 2021 11:25:54 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: References: <161968317610.20664.11107844270215068679@ietfa.amsl.com> To: mpls , loa Andersson X-Mailer: Apple Mail (2.3608.120.23.2.6) Archived-At: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Apr 2021 10:26:08 -0000 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=20 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 wrote: >=20 >=20 > A New Internet-Draft is available from the on-line Internet-Drafts = directories. >=20 >=20 > Title : MPLS Open Design Team Questions > Author : Loa Andersson > Filename : draft-andersson-mpls-open-dt-questions-00.txt > Pages : 4 > Date : 2021-04-29 >=20 > 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. >=20 > 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. >=20 >=20 > The IETF datatracker status page for this draft is: > = https://datatracker.ietf.org/doc/draft-andersson-mpls-open-dt-questions/ >=20 > 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-questio= ns-00 >=20 >=20 > 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. >=20 > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ >=20 >=20 > _______________________________________________ > 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