Re: [Teas] Associating a TE Tunnel/Policy with an NRP

Vishnu Pavan Beeram <vishnupavan@gmail.com> Fri, 10 November 2023 09:30 UTC

Return-Path: <vishnupavan@gmail.com>
X-Original-To: teas@ietfa.amsl.com
Delivered-To: teas@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 26387C16F3ED for <teas@ietfa.amsl.com>; Fri, 10 Nov 2023 01:30:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.107
X-Spam-Level:
X-Spam-Status: No, score=-2.107 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, 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] 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 r3x7ZQx2ou7x for <teas@ietfa.amsl.com>; Fri, 10 Nov 2023 01:30:50 -0800 (PST)
Received: from mail-ed1-x532.google.com (mail-ed1-x532.google.com [IPv6:2a00:1450:4864:20::532]) (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 A0FC9C16F3E3 for <teas@ietf.org>; Fri, 10 Nov 2023 01:30:50 -0800 (PST)
Received: by mail-ed1-x532.google.com with SMTP id 4fb4d7f45d1cf-5441305cbd1so2972007a12.2 for <teas@ietf.org>; Fri, 10 Nov 2023 01:30:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1699608649; x=1700213449; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=OSiE5bfgIWbOPdNzrIVzv79P6rNqxxYx7gRIkYj63ys=; b=iNFKGhGMlaPF9GVL/a4CKoIt8KHjGH41xoTV6btgjjXd3SLNxdDaS/EazJuXW1IOgb OE9mL4gZeNyTAo66sFyLzuy9/t09zmL9A9TOR/HUgccNbK74+SfDCetGugCTlePmHpDG Vx1hpwCiDoQhGwKRwS/RFnQufONwzmnEzwlgGaRYfhSoPDiZctWm023KIj/b/vmJscfc j41ylMPG7Eo7xHlE8EKylps978Pmx/QNKJMp1YvcFC0QODstUQUTolNxlKpSSwUaXNXs H999gEjC8FmnkYnJGIKXnrjF6dMtmE1VMk+418btpNM4lTddm7SPJAwaAOEzGgELyuwi 9lkQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1699608649; x=1700213449; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=OSiE5bfgIWbOPdNzrIVzv79P6rNqxxYx7gRIkYj63ys=; b=jFMZ9B7ZsTYKWFVsGvwuAhYzj+zF8gy6x0vZHKSC0pKf3sWxo8EUqQALMXLKFvUMyd /IjwkUUF4TdnjwlaE0pqAy2p9u1tBixX0kPOubmL8KAUBti8miR7Vrbz7BqUniUoTjvR J8UwYUoPgqBM7rj3AaujQ5nPLgLWJXPKbFXb3yRliU+S2FT86Kc5xYrA5oVCl/B7CXRO rOg3EjA+AvPN/5CbkdvtonUkYiVA4oW0kqG21kM1+24bY/EVAgItLyghwThh7ilf8/Fl NRx6yBONVUgZ3l9ALiNcE2tDUPSBonWzmstoCddMdApZF3I/S6KVJH8bY2ByXi2NKB5R tLvw==
X-Gm-Message-State: AOJu0YyX0dKSf07UBTk56K1j2Ff1lMWGg/JRAIpQbHFJLouSB3ZTl3Dk BT+YYDczzhguEjaTuCrnv9F88TRfpwi5yX2hB40pjTGAECBK2H8cjYA=
X-Google-Smtp-Source: AGHT+IGaoR+kOolG/6iosLEqov4sgCYDt+PnkN16LEwQx4AzCcj/dPkGKDmweOzVqJ3LVPgms2y44ZuksSLPiefLuwM=
X-Received: by 2002:a50:8e16:0:b0:543:cc90:cb8b with SMTP id 22-20020a508e16000000b00543cc90cb8bmr6932043edw.2.1699608648802; Fri, 10 Nov 2023 01:30:48 -0800 (PST)
MIME-Version: 1.0
References: <CA+YzgTuDfBQEoKAF3HhS7ZutPQSz95iX8ZWwVOXWi=xYAeLUeg@mail.gmail.com> <03ca01d9f214$a0fec860$e2fc5920$@olddog.co.uk>
In-Reply-To: <03ca01d9f214$a0fec860$e2fc5920$@olddog.co.uk>
From: Vishnu Pavan Beeram <vishnupavan@gmail.com>
Date: Fri, 10 Nov 2023 15:00:35 +0530
Message-ID: <CA+YzgTstS06LvEj6LjAq6qRjCwq3Jc1qUnPkCxYbb6G7PZ5SEA@mail.gmail.com>
To: adrian@olddog.co.uk
Cc: TEAS WG <teas@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000c4e5cf0609c8f966"
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/bAWE6Fy3qN0vDeeX9FJNviD5Aps>
Subject: Re: [Teas] Associating a TE Tunnel/Policy with an NRP
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <teas.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/teas>, <mailto:teas-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teas/>
List-Post: <mailto:teas@ietf.org>
List-Help: <mailto:teas-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/teas>, <mailto:teas-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Nov 2023 09:30:53 -0000

Just realized that this thread was left hanging..

For all NRP specific protocol extension documents, the request from the
TEAS WG chairs is the the following (nothing more, nothing less):

   - Add a “Scalability Considerations” section.
   - Keep the TEAS WG updated about the progress of the document
   (especially during WG adoption and WGLC)


With regards to draft-dong-idr-sr-policy-nrp for which this thread was
initiated, it is on the agenda in today's WG session. The expectation is
that this would trigger a discussion on the utility of the protocol
extension defined in this draft.

Regards,
-Pavan

On Thu, Sep 28, 2023 at 7:34 PM Adrian Farrel <adrian@olddog.co.uk> wrote:

> Hi Pavan,
>
>
>
> Thanks for starting this thread. It’s a fine thing to talk about.
>
>
>
> I don’t think the TEAS working group would be in a position to stop other
> working groups picking up and working on protocol extensions that they
> think are necessary. But it might be good to have an overview perspective
> of how NRPs might be constructed in different protocol environments so that
> those working groups can go ahead and make the protocol changes with
> confidence.
>
>
>
> It’s probable that TEAS was a bit premature adopting draft-ietf-teas-ns-ip-mpls
> while other working groups were holding back waiting for the slicing
> framework to stabilise and be approved for publication. But we don’t need
> to go there. What is important now is to recognise that it is open for
> people to work out how they want to develop solutions to support NRPs. TEAS
> can certainly coordinate that work, but I don’t think it can constrain it
> because slicing is a broad concept and there are plenty of protocols and
> service architectures that can deliver “slices.”
>
>
>
> What do you propose (maybe you could put your hat back on?) as a way that
> we could act to coordinate this work?
>
>
>
> Cheers,
>
> Adrian
>
>
>
> *From:* Teas <teas-bounces@ietf.org> *On Behalf Of *Vishnu Pavan Beeram
> *Sent:* 28 September 2023 14:11
> *To:* TEAS WG <teas@ietf.org>
> *Subject:* [Teas] Associating a TE Tunnel/Policy with an NRP
>
>
>
> There are a couple of control-plane protocol extension documents that have
> been proposed outside TEAS WG for associating a TE Tunnel/Policy with an
> NRP.
>
>    - draft-dong-idr-sr-policy-nrp proposes extensions to BGP for
>    associating an SR policy with an NRP
>    - draft-dong-pce-pcep-nrp proposes extensions to PCEP for associating
>    a TE LSP with an NRP
>
> The motivation behind this association is to ensure that the TE paths are
> computed, placed and maintained within the topology associated with the
> specified NRP (discussed briefly in draft-ietf-teas-ns-ip-mpls).
>
>
>
> We have had some discussion/debate in the past in TEAS on whether or not
> there should be any NRP specific control-plane protocol extensions defined
> at all. Most of that debate has been focused around extensions to
> link-state protocols. AFAIR, we (in TEAS) haven't discussed the specific
> type of protocol extension discussed in the aforementioned drafts.
>
>
>
> I'm starting this thread to get some feedback from the WG on this specific
> type of protocol extension.
>
>
>
> Regards,
>
> - Pavan (as a WG contributor)
>