Re: [Idr] WG Adoption for draft-zhu-idr-bgp-ls-path-mtu (11/1/2020 to 11/16/2020)

Jeff Tantsura <jefftant.ietf@gmail.com> Thu, 12 November 2020 17:52 UTC

Return-Path: <jefftant.ietf@gmail.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F0A543A145A for <idr@ietfa.amsl.com>; Thu, 12 Nov 2020 09:52:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 CI4er6Rwxi4j for <idr@ietfa.amsl.com>; Thu, 12 Nov 2020 09:52:42 -0800 (PST)
Received: from mail-pf1-x42a.google.com (mail-pf1-x42a.google.com [IPv6:2607:f8b0:4864:20::42a]) (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 D23FA3A1455 for <idr@ietf.org>; Thu, 12 Nov 2020 09:52:42 -0800 (PST)
Received: by mail-pf1-x42a.google.com with SMTP id g7so5255061pfc.2 for <idr@ietf.org>; Thu, 12 Nov 2020 09:52:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:message-id:in-reply-to:references:subject:mime-version; bh=3Rw5CmdYWoJ0MI/lAC3nvXhqA5vVlaDdwtmaWWkunH8=; b=A1W4srDGq6T996B2HO35G3uUnnc8RXFxXgoSNRbsDR2Hpb0m6kxUG2XD1zwFlMZYdV kceK7A6VilMOPTk5FaQV7vChVaTeeHGJV4myopSRt/gde8+4rvtjD7VaBy4SHTa00hqT 2+mMkZbq7PSJXV4E6TB6kSzSBQW8O/vTYOxdF/2vdfKvlJ8iuiaf36eA6iuYb9gFH1Fc u3mZ3iZZo7C4mcSvOJkqbvn7nih0e8uDdt5uIBikuEnF6G4y2QQAvxBotu/5FjauTJi3 GeMNuBi7cEAja2mHCq/3LUet9Yej9QqJoMp9C1Z1qtUZIXe21dKY7MNY667KTGLkJNdj u7lg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:message-id:in-reply-to:references :subject:mime-version; bh=3Rw5CmdYWoJ0MI/lAC3nvXhqA5vVlaDdwtmaWWkunH8=; b=LN2sqpermf3NxxWJHaV0LPtSjFV0cJOQg6ydbvb1VUcYzmf2zcEoCEjNTG1shXbX0D cpSFt30tVLVBrfvswOe9R1HBAsLXaoz3KfLJh+BaC7rX98oerGTLHS9njt4xv5gv49PN d8tQRTT37g5nILHHrPKJq0UGSg3zwXz/Tz3o+oGlrc4FWmYPfHx0SiK296oWDXL5ix4f qC1wN478ofu+QY0+gc5rsaNeLYElrSG2oj6QT4obiRr3Z7T2TPdZdsanhG2j2u9dQnbE L5GpaaM6Rak76egZFS+ffmCvBkmAPJXPyEtcuCEGCWbL4CdwDzSUVIqzo99SPIBCWzjy UoYQ==
X-Gm-Message-State: AOAM532fgrMOqltWnosK2oVCx5sFiSqMMF8QVqBFup/Wv3nzFkLs8SNS iGwmkLmNSwb1N1c2bu5MV74OJXa+THo=
X-Google-Smtp-Source: ABdhPJxVwbbeIwV/833YSX017CCulIIVtN8H6rJ+jBqLSzjGKuqlYjXEKEG6/Lk2SvWFWZNkamgDeg==
X-Received: by 2002:a17:90a:e604:: with SMTP id j4mr341862pjy.19.1605203562354; Thu, 12 Nov 2020 09:52:42 -0800 (PST)
Received: from [192.168.1.7] (c-73-63-232-212.hsd1.ca.comcast.net. [73.63.232.212]) by smtp.gmail.com with ESMTPSA id t32sm6818321pgl.0.2020.11.12.09.52.40 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 12 Nov 2020 09:52:41 -0800 (PST)
Date: Thu, 12 Nov 2020 09:52:34 -0800
From: Jeff Tantsura <jefftant.ietf@gmail.com>
To: Susan Hares <shares@ndzh.com>, "Stephane Litkowski (slitkows)" <slitkows=40cisco.com@dmarc.ietf.org>, "=?utf-8?Q?idr=40ietf.org?=" <idr@ietf.org>, "Acee Lindem (acee)" <acee=40cisco.com@dmarc.ietf.org>
Message-ID: <9346741d-6eda-4fbc-917f-2ac3662aac0b@Spark>
In-Reply-To: <1F8F1206-0583-4262-8837-934C10F2B034@cisco.com>
References: <050501d6b0d5$877d5970$96780c50$@ndzh.com> <SJ0PR11MB5136C14AD3AED30EF5EC128BC2EF0@SJ0PR11MB5136.namprd11.prod.outlook.com> <033001d6b678$08d20280$1a760780$@ndzh.com> <CO1PR11MB512125F36BEF9AC8FEAE0598C2EA0@CO1PR11MB5121.namprd11.prod.outlook.com> <006801d6b6de$0f89c390$2e9d4ab0$@ndzh.com> <1F8F1206-0583-4262-8837-934C10F2B034@cisco.com>
X-Readdle-Message-ID: 9346741d-6eda-4fbc-917f-2ac3662aac0b@Spark
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="5fad7668_1f16e9e8_5a0e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/VUhoq8TJXEnjrO64vVr10OiMeSM>
Subject: Re: [Idr] WG Adoption for draft-zhu-idr-bgp-ls-path-mtu (11/1/2020 to 11/16/2020)
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Nov 2020 17:52:45 -0000

+1 to everything Acee said

Cheers,
Jeff
On Nov 10, 2020, 1:01 PM -0800, Acee Lindem (acee) <acee=40cisco.com@dmarc.ietf.org>rg>, wrote:
> Speaking as an IDR WG member:
>
> The name of the draft is wrong – the extension is for a Link MTU and not a path MTU.
>
> Speaking as LSR Chair:
>
> We could this in LSR as there is currently no MTU advertisement in the LSAs for OSPFv2 and OSPFv3. Implementations already make use of this information as it is used in the OSPF DBD packets and for LSA packing. Of course, we’d require a more accurate draft name and title.
>
> Thanks,
> Acee
>
> From: Idr <idr-bounces@ietf.org> on behalf of Susan Hares <shares@ndzh.com>
> Date: Monday, November 9, 2020 at 4:20 PM
> To: "'Stephane Litkowski (slitkows)'" <slitkows=40cisco.com@dmarc.ietf.org>rg>, IDR List <idr@ietf.org>
> Subject: Re: [Idr] WG Adoption for draft-zhu-idr-bgp-ls-path-mtu (11/1/2020 to 11/16/2020)
>
> Stephane:
>
> My second message to this thread asked a few questions about the technology.
>
> This information can be more than IGP information.   If SR segments statically defined (static or direct interfaces) tunnels and pass the endpoints via BGP tunnel-encaps draft with SR Policy tunnel type, this can just be BGP.
>
> I’ll keep this WG adoption call going until we can be sure if:  1) it something LSR wants to standardize, and 2) whether there is a BGP only case.   It is clear to me that standardizing MTU for a SR segments with stacked tunnel segments passed by BGP was useful.
>
> The authors should be the ones to propose this in LSR.
>
> Cheers,  Sue
>
> From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of Stephane Litkowski (slitkows)
> Sent: Monday, November 9, 2020 4:28 AM
> To: Susan Hares; idr@ietf.org
> Subject: Re: [Idr] WG Adoption for draft-zhu-idr-bgp-ls-path-mtu (11/1/2020 to 11/16/2020)
>
> Hi Sue,
>
> > The purpose behind this mechanism is to reduce administrative work rather than to reduce the review on drafts.
>
> That’s exactly my point. If we don’t do OSPF extension now and in the same draft, we leave a gap that will require a new draft for a very very small extension. Just adds process overhead for nothing…
>
>
> Stephane
>
>
> From: Susan Hares <shares@ndzh.com>
> Sent: lundi 9 novembre 2020 10:10
> To: Stephane Litkowski (slitkows) <slitkows@cisco.com>om>; idr@ietf.org
> Subject: RE: [Idr] WG Adoption for draft-zhu-idr-bgp-ls-path-mtu (11/1/2020 to 11/16/2020)
>
> Stephane:
>
> I want to pick up on your email from two points:
>
> 1)  Why not do everything in LSR?
> <WG-chair hat>
> If the feature comes with interest in doing all 3 (ISIS, OSPF, and BGP-LS data gathering), then the authors may select to do everything in LSR rather than have 2 or 3 drafts to maintain.
>
> This is optional and the mechanism may not fit every draft.   The drafts may also start out adopted and vetted in LSR and IDR.    The purpose behind this mechanism is to reduce administrative work rather than to reduce the review on drafts.
>
> </wg-chair hat off>
>
>
> 2) TRILL implementations of IS-IS has some MTU subTLV -
>
> If you are interested in whether this has been implemented in TRILL, you might want to check with Donald Eastlake.   My vague and foggy recollection is that had some implementations or came from pre-TRILL implementations.
>
>
> Cheers, Susan Hares
>
>
>
> From: Stephane Litkowski (slitkows) [mailto:slitkows@cisco.com]
> Sent: Wednesday, November 4, 2020 3:03 AM
> To: Susan Hares; idr@ietf.org
> Subject: RE: [Idr] WG Adoption for draft-zhu-idr-bgp-ls-path-mtu (11/1/2020 to 11/16/2020)
>
> Hi,
>
> “a) Are there ways to pass IGP link MTUs in
> the IGPs?  If so, is this needed in BGP-LS”
>
> This is a valid point, most of the time BGP-LS is feeded by IGP LSDBs (of course there are other ways too). While I see that IS-IS has some MTU subTLV coming from TRILL RFC7176 (possibly never been implemented), I don’t see anything for OSPF (I’m not an OSPF expert, so I may have missed it).
> Shouldn’t this be checked and validated with LSR WG before adopting ?
>
>
> Stephane
>
>
> From: Idr <idr-bounces@ietf.org> On Behalf Of Susan Hares
> Sent: lundi 2 novembre 2020 06:04
> To: idr@ietf.org
> Subject: [Idr] WG Adoption for draft-zhu-idr-bgp-ls-path-mtu (11/1/2020 to 11/16/2020)
>
> This begins a 2 week WG adoption call for
> draft-zhu-idr-bgp-ls-path-mtu-04.txt (11/1 – 11/16/2020).
>
> The authors should send in an IPR statement for this draft
> by 11/5 so the WG can include the IPR status in their decision.
>
> You can access the draft at:
> https://datatracker.ietf.org/doc/draft-zhu-idr-bgp-ls-path-mtu/
>
> Since this draft is reference by an existing IDR draft
> I’ve included a bit of background below to help you place
> this draft into the larger context of the SR additions to BGP-LS
> and the draft-ietf-idr-tunnel-encaps-19.txt.
>
> This draft does continue BGP-LS additions.  if you
> are opposed to any BGP-LS additions rather than
> this specific addition, please make that clear in your
> comment in this discussion.
>
> The authors requested a WG adoption at IETF 108.
> The IDR co-chairs thank the authors for their patience.
> This draft has been delayed by process of having a
> new document shepherd (Sue Hares) come up to speed
> on draft-ietf-idr-tunnel-encapsulation.
>
> Cheers, Sue
>
> Background
> ===========
> Segment Routing technology creates SR tunnels that are
> directly overlaid on MPLS or SRv6.  While existing MPLS technology
> (LDP and RSV-TE) provides mechanisms to negotiate path MTU
> based on individual link MTU limits, the Segment Routing (SR)
> on BGP-LS Link Attribute does not pass information on
> MTU size per link.
>
> draft-ietf-idr-sr-policy-path-mtu-02.txt sends PATH MTU
> information in the tunnel-encapsulation attribute for the tunnel type
> SR-Policy that handles segment routing (SR) paths.
> However, it lacks the information to create a reasonable
> Path size since the BGP-LS Link Attribute does distribute
> this information.
>
> The draft proposes adding a new sub-TLV for MTU size
> to the BGP-LS Link Attribute TLV, and
> draft-ietf-idr-sr-policy-path-mtu-02.txt mentions this
> draft as one possible way to distribute the per link
> MTU.
>
> Questions for the authors might be:
> a) Are there ways to pass IGP link MTUs in
> the IGPs?  If so, is this needed in BGP-LS
>
> b) What other mechanisms pass link MTU?
>
>
>
>
>
>
>
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr