[mpls] Second call: A question about draft-ietf-mpls-sfl-control

Adrian Farrel <adrian@olddog.co.uk> Mon, 04 March 2024 10:41 UTC

Return-Path: <adrian@olddog.co.uk>
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 E9D90C151061; Mon, 4 Mar 2024 02:41:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.106
X-Spam-Level:
X-Spam-Status: No, score=-7.106 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, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=olddog.co.uk
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id feWxT_YS_y0s; Mon, 4 Mar 2024 02:41:48 -0800 (PST)
Received: from mta5.iomartmail.com (mta5.iomartmail.com [62.128.193.155]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B22E2C14CEFF; Mon, 4 Mar 2024 02:41:32 -0800 (PST)
Received: from vs2.iomartmail.com (vs2.iomartmail.com [10.12.10.123]) by mta5.iomartmail.com (8.14.7/8.14.7) with ESMTP id 424AfUMD025381; Mon, 4 Mar 2024 10:41:30 GMT
Received: from vs2.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 4B12F4604B; Mon, 4 Mar 2024 10:41:30 +0000 (GMT)
Received: from vs2.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 3F4DF46048; Mon, 4 Mar 2024 10:41:30 +0000 (GMT)
Received: from asmtp3.iomartmail.com (unknown [10.12.10.224]) by vs2.iomartmail.com (Postfix) with ESMTPS; Mon, 4 Mar 2024 10:41:30 +0000 (GMT)
Received: from LAPTOPK7AS653V ([87.129.166.107]) (authenticated bits=0) by asmtp3.iomartmail.com (8.14.7/8.14.7) with ESMTP id 424AfTQn001307 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 4 Mar 2024 10:41:29 GMT
Reply-To: adrian@olddog.co.uk
From: Adrian Farrel <adrian@olddog.co.uk>
To: 'mpls' <mpls@ietf.org>
Cc: draft-ietf-mpls-sfl-control.all@ietf.org
References: <044701da68da$42740570$c75c1050$@olddog.co.uk>
In-Reply-To: <044701da68da$42740570$c75c1050$@olddog.co.uk>
Date: Mon, 04 Mar 2024 10:41:29 -0000
Organization: Old Dog Consulting
Message-ID: <005201da6e20$8456a290$8d03e7b0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AdpuIH1YAi90+eVrR5ygXuQzxUrRtg==
Content-Language: en-gb
X-Originating-IP: 87.129.166.107
X-Thinkmail-Auth: adrian@olddog.co.uk
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=olddog.co.uk; h=reply-to :from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-type:content-transfer-encoding; s= 20221128; bh=LJ+izblUKzDBUGFr9KgsUx4DD6ec7r/0tMeeZ07B70s=; b=xpa f/F4va7YoaqIniFjZaiklB1Cb48Uo46lMdLFPQJnnE6UMi5b0KkaFcApGFv7iw97 cdBG7LwGOClELBSMMfghmUDpxNhntGkC/L6kpJubJ8AuhlTmUiK2cj9bi7Xr8EHP aeRbENLycvXzQWA3PcuYEokZAR8Jm3+Gi57MbbbH5ahShBeOJbn0MkZ0Nm09/+qU IlyBxST6bo1iuUyYIxdYou/IxkrSw5yXHv6oH/y3wv02NL+jadIeefeunsSf50lS 0fITNYma6ewCdvIziY2PyQib1vyxKpgrmP2+BEdUgUjFpZ0ESCkk+AgLpXGHaJg/ xPgATPvipZl39fpK+CQ==
X-TM-AS-GCONF: 00
X-TM-AS-Product-Ver: IMSVA-9.1.0.2090-9.0.0.1002-28230.007
X-TM-AS-Result: No--2.254-10.0-31-10
X-imss-scan-details: No--2.254-10.0-31-10
X-TMASE-Version: IMSVA-9.1.0.2090-9.0.1002-28230.007
X-TMASE-Result: 10--2.254100-10.000000
X-TMASE-MatchedRID: OplBTMCIxtkDYP7H+M1ZMzjNGpWCIvfTfkuZtv/FS5r2apmI5+Nrzxeh 1vTlF/tNgvRaVUNx1oBXKoklfL1yzP+XuscWvkzgQQ5+hY6u+46GiafRvCBWaZ0C6WJNXTpiaxZ lX1gwMFsAjPE9XBt9MYyStEALHXb2sx4oz7locDXP01G0ZRd+f5GAt645FF0S7J/odmNkzarzWh IpvgX1cDsjLjEwO02ey27ymPMJR0RccQ8eam5EfTl/1fD/GopdWwo771mVvkkq9K81zhdBnwzKt 8/2P4LVIAcCikR3vq/pzXkzxHUr/x/kJZelZWEIG0Zug3DGEjdju6FsIiOIvx4GDwz09LiN
X-TMASE-SNAP-Result: 1.821001.0001-0-1-22:0,33:0,34:0-0
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/VddeWUQoY95R0ywM2vkMrijBhHs>
Subject: [mpls] Second call: A question about draft-ietf-mpls-sfl-control
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.39
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, 04 Mar 2024 10:41:53 -0000

Hi,

Resending this because I am hearing silence and that could mean:
- no one cares
- no one read the original email

A

-----Original Message-----
From: mpls <mpls-bounces@ietf.org> On Behalf Of Adrian Farrel
Sent: 26 February 2024 17:36
To: 'mpls' <mpls@ietf.org>
Cc: draft-ietf-mpls-sfl-control.all@ietf.org
Subject: [mpls] A question about draft-ietf-mpls-sfl-control

Hi WG,

While talking about draft-ietf-mpls-rfc6374-sfl and
draft-ietf-mpls-sfl-control with Stewart, and resulting from SEC ART review
of draft-ietf-mpls-sfl-control by Charlie Kaufman, we discovered that there
is a small hole in the control protocol arising in MP2P LSPs when one of the
senders crashes and restarts.

There are two possible approaches to solving this:
1. introduce a protocol fix
2. scope the utility of the control protocol draft to p2p and p2mp only

But, before going there, we are interested to know whether anyone cares
about this control protocol. Has anyone implemented it? Does anyone plan to
implement it?

Thanks for any answers.

Adrian

_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls