Re: [mpls] Formal poll to abandon draft-ietf-mpls-sfl-control

Stewart Bryant <stewart.bryant@gmail.com> Wed, 13 March 2024 18:58 UTC

Return-Path: <stewart.bryant@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 BA6D1C14F693; Wed, 13 Mar 2024 11:58:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Level:
X-Spam-Status: No, score=-2.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, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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=gmail.com
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 84io6c2XSQd2; Wed, 13 Mar 2024 11:58:55 -0700 (PDT)
Received: from mail-wr1-x434.google.com (mail-wr1-x434.google.com [IPv6:2a00:1450:4864:20::434]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F103DC15154F; Wed, 13 Mar 2024 11:58:54 -0700 (PDT)
Received: by mail-wr1-x434.google.com with SMTP id ffacd0b85a97d-33e9ba0eadcso84980f8f.2; Wed, 13 Mar 2024 11:58:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1710356332; x=1710961132; darn=ietf.org; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=r6VLaZ6vHgLzDwkiIfbsr1Srl7Jg0IfC43jMdtSgXeU=; b=Z2JDUF9tzEVnKdo0EmCmr8B4OljxPAyvVLuTeyqYACz6b+6SSbtknI/Fa3eAaGZp09 1QuCMG3ppCj89jFRWcBTTRxW198egBnt8Z/V9FftvbLez11ue+GlA8AT42pNTFPE2WXP QqsDkPsstNDQRFIOTyFBIWwTei88z6XLLh2IQLIvTNqNUsVGKB+zflnw1Z0dJ+WqdESb eIOVYigE1szWF6RZhKRWsHUYXRM6MwKcxQk4fgSWgSdz3RVx0jwgPaes2wyZSFP2zsEo rA9AnA1k5A6Wb3uX5dK38THb3vQDmOcbiWunjwnZdh5Rb6C4e45wM5ePw1SouF9tg25d /j+Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1710356332; x=1710961132; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=r6VLaZ6vHgLzDwkiIfbsr1Srl7Jg0IfC43jMdtSgXeU=; b=kyM95o2OyLi99mnVIJbMnUv68vh+448YBwOjU8LUNc8q3bCIP0hJyO85/4nYjOXW7d 14oFmJbaK1GBluVgnvfRbvuvxlGump6hkRTz+kL73QhtgI/ATVdc7DJhq+cjiR7PlKYu GI9CyIDDG+S6U4f/ipbWLIEqEMaLhNJYRXGaecfLqapO3KpfqgsTvQIt0Hz+ISB9hkel QtcjtGaYKzoJJdg5vMfittXKp+eBAXXuxUJpAEl+zbc0DGgigt9JzjciJsxXFM9mrNyx K2W5Bw11Ip+p5KHRV6GWF1LfqS4pioye40mhTRuYUmagRPKE7GIKE5S7kSHbugllPQ1k Q30w==
X-Forwarded-Encrypted: i=1; AJvYcCWinrHjnyPJuqEYU249oMM9sX7NJactuRBt+TTK8eAxfLe3vk4NKccGDcSnz6X+qHFdynpI7xJsTpF+LfSNycXHKv6cR5gk4gqchxWu2ZwQ9IX7kiMMd4nRnM//DOlPBVQ9hU1SHMDx
X-Gm-Message-State: AOJu0YwYe/ypIUi0/SYi3rNYDI13ZexTXixpeuE0BeXqA5/qJoJBIaim M3GHPrCDZgJMwf2/A7xfhQPtNdX1jLLq+U91QQL1a1f60rea9kbz
X-Google-Smtp-Source: AGHT+IFMMIvDhFjQMzHomXH1oyHaBOVtKWGyKsB6GCk+dcZrTs/7bT9k2VmEZuZT4UI7ToMtjkPx5g==
X-Received: by 2002:adf:f644:0:b0:33e:774f:e3ca with SMTP id x4-20020adff644000000b0033e774fe3camr2872457wrp.64.1710356332323; Wed, 13 Mar 2024 11:58:52 -0700 (PDT)
Received: from smtpclient.apple ([185.69.145.29]) by smtp.gmail.com with ESMTPSA id z2-20020a5d6402000000b0033dedd63382sm12247244wru.101.2024.03.13.11.58.51 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 13 Mar 2024 11:58:51 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.100.2.1.4\))
From: Stewart Bryant <stewart.bryant@gmail.com>
X-Priority: 3 (Normal)
In-Reply-To: <14065d473d44f04a4efaecebb090c277.squirrel@pi.nu>
Date: Wed, 13 Mar 2024 18:58:40 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <DE2A0929-3FB5-4164-B3D0-FD43715DD5BB@gmail.com>
References: <071d01da749b$af812400$0e836c00$@olddog.co.uk> <14065d473d44f04a4efaecebb090c277.squirrel@pi.nu>
To: loa Andersson <loa@pi.nu>, Adrian Farrel <adrian@olddog.co.uk>, draft-ietf-mpls-sfl-control.all@ietf.org, mpls <mpls@ietf.org>
X-Mailer: Apple Mail (2.3774.100.2.1.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/V4X0JcqneO9LsbXlL4XyzpobmrA>
Subject: Re: [mpls] Formal poll to abandon 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: Wed, 13 Mar 2024 18:58:58 -0000

I will be sad as well, but no one has expressed any interest in the control plane work only in unblocking the other SFL drafts.

Interestingly the last time this was on the MPLS agenda people asked for control planes for LDP and RSVP-TE, but no one offered to so any work on this.

In the intervening years SDN has become more prevalent and I suggest that anyone wanting to deploy a facility that this simple control plane would address would probably use SDN to manage the SFLs.

If there is someone that wants to put this in a network and there is at least one other person interested in working through how it works in detail then I would be prepared to take this to completion, but in the absence of both such commitments I think it should go back to the WG and presumably eventually expire.

- Stewart


> On 13 Mar 2024, at 04:20, loa@pi.nu wrote:
> 
> Adrian,
> 
> You have correctly interpreted my feelings, I think it is sad that we
> drop the document.
> 
> Since there seems to be no support for continuing the work, I have to accept
> that the document is dropped.
> 
> /Loa
> 
>> All,
>> 
>> As you will have seen, there has been some discussion on the list about
>> the
>> work still needed to complete draft-ietf-mpls-sfl-control and a bug in the
>> spec that Stewart has discovered.
>> 
>> I asked on the list (2024-02-26) whether anyone is still interested in
>> this
>> work
>> (https://mailarchive.ietf.org/arch/msg/mpls/eW8SpBzEAZRlsiTPhPbSd3DnrPQ/)
>> I repeated the question (2024-03-04)
>> Stewart rephrased my questions (2024-03-04) to ask if anyone has
>> implemented
>> or deployed, or has plans to implement or deploy
>> (https://mailarchive.ietf.org/arch/msg/mpls/i4IC05iAheiYlKGIFq-8iu7nhjg/)
>> 
>> The only response has been from Loa, suggesting that if someone is willing
>> to do the work then he would support them, and that (my interpretation) he
>> would be sad to see the document dropped.
>> 
>> So, this email is a formal call for consensus.
>> 
>> The chairs propose to pull the document back from the AD and drop it from
>> the working group. This would allow anyone to pick the document up again
>> in
>> the future, but it would need to go back through the working group
>> adoption
>> process.
>> 
>> Please speak up if you are opposed to this action. In particular, please
>> state why you are opposed (e.g., you know something about
>> implementation/deployment) and how you propose that the document should
>> move
>> forward (i.e., who would do what work).
>> 
>> In the absence of voices opposed to this approach, the chairs will take
>> the
>> action.
>> 
>> This call ends on Tuesday 19th March 2024 at 17.00 UTC (i.e., after the
>> MPLS
>> session at IETF-119).
>> 
>> Thanks,
>> Adrian (on behalf of the MPLS WG chairs)
>> 
>> _______________________________________________
>> mpls mailing list
>> mpls@ietf.org
>> https://www.ietf.org/mailman/listinfo/mpls
>> 
> 
> 
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls