Re: [Idr] WG LC on draft-ietf-idr-sr-policy-safi-00 and draft-ietf-idr-bgp-sr-segtypes-ext-02 (2/15/2024 to 2/29/2024)

Ketan Talaulikar <ketant.ietf@gmail.com> Thu, 22 February 2024 02:12 UTC

Return-Path: <ketant.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 3B023C15198C for <idr@ietfa.amsl.com>; Wed, 21 Feb 2024 18:12:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.104
X-Spam-Level:
X-Spam-Status: No, score=-2.104 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_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=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 aTXb5npyvfiC for <idr@ietfa.amsl.com>; Wed, 21 Feb 2024 18:12:40 -0800 (PST)
Received: from mail-ej1-x632.google.com (mail-ej1-x632.google.com [IPv6:2a00:1450:4864:20::632]) (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 3F819C14F6E1 for <idr@ietf.org>; Wed, 21 Feb 2024 18:12:40 -0800 (PST)
Received: by mail-ej1-x632.google.com with SMTP id a640c23a62f3a-a3f48422fb6so182643066b.3 for <idr@ietf.org>; Wed, 21 Feb 2024 18:12:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1708567958; x=1709172758; 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=Dw7Nn08ZnNZqwQLfPOrRQEamMc1UaXVNHXZcYT5FX/s=; b=dCqRsH+iys8SUs0R4maGxVgZ+HUG5dyFD9pyHoJteCJzK/hkV9RYj8lFQac8MgJXvh 4t0mYMYMaJv8VWLhoTOZ3NBNgFQBO7Gfte2fazti+CE0ZDnuCyCUCAENqouxRBzOR8hi LrggSotwpr8sRXdTCRii+U+NNON0Qe8XsA7bITgza0yg1gRcSS/en1erK+y1dsCG/s6C BH1Tn5Hw8E9JYxY+m0araj7JfSKSvSL1gdmSK30AfXMGrCrirM7Zc5b/rCvp1tH8lsEJ ftpKbUMSP9y3lkGI5Jy9GIVECs3wiVEjVZpPznwYqw+n4YZIGpuokt3RPum6wzyIyPhg NSNg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1708567958; x=1709172758; 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=Dw7Nn08ZnNZqwQLfPOrRQEamMc1UaXVNHXZcYT5FX/s=; b=QcKcrS4MxM+NmpKTYvs0lTwZ30SpxoBSbML84Hc/y5vN+F7yygFDKkaul2EecCON+I GSIyjwMiJa+I75uQ7AfSSKBI1RqrOL42DTsCKdEd3Q4w0tIDgyC5X6ZbCOizJ4EX7JT/ 8T5hQ4kf2+oJkr6Xw4Hi84yFWPeZ5E77DWwDwy2fnzO7yp5iKpHrIwzgVE1vUfdPwYas cwm2IEpT9mnO28APco/6pPMRZI/y20BxkICpT6V0A9zRhohg8eM83TpsUKyNsnYOIBO7 55B/L9DBWTyarEmvUYremD/2DflgIUNqhxylarIIes3SoZMRmJiEYgD548ICmHdZjEJe gNhQ==
X-Gm-Message-State: AOJu0Yy9hdNedJt1vG/IPpT4uaJitPWGlXCVsG4v4Uw8O9/OXfeDCG9l j43zI3Xwu9s8GkSxTFKADYk1R/Za62yCXnYABH0iNTyi11yg6iPJZytnqyeh7FjwnJI3ogSrmq3 5H0aj0J2UY9/u9PbdU8Xm34hwJ0Kb0eJW
X-Google-Smtp-Source: AGHT+IF/uVDDk86jwUphp+2ft7gEVlz2gxzrrc836Hto9miiSxG4VK6s6nWnFUgnNQpKqvgUX06OZkFMIW5LCuVbDOs=
X-Received: by 2002:a17:906:f206:b0:a3e:39f7:52b4 with SMTP id gt6-20020a170906f20600b00a3e39f752b4mr8709278ejb.49.1708567958103; Wed, 21 Feb 2024 18:12:38 -0800 (PST)
MIME-Version: 1.0
References: <DM6PR08MB48572F86EA48D3FDB532EA21B34D2@DM6PR08MB4857.namprd08.prod.outlook.com>
In-Reply-To: <DM6PR08MB48572F86EA48D3FDB532EA21B34D2@DM6PR08MB4857.namprd08.prod.outlook.com>
From: Ketan Talaulikar <ketant.ietf@gmail.com>
Date: Thu, 22 Feb 2024 07:42:26 +0530
Message-ID: <CAH6gdPz3a9U_cDvXciAkiVhXbnWDStYZzrdak3swh2h8=9fLmQ@mail.gmail.com>
To: Susan Hares <shares@ndzh.com>
Cc: "idr@ietf. org" <idr@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000037ac8b0611eefaba"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/T2VaUQTIP0KqO5X3WGM6ThnlUQ8>
Subject: Re: [Idr] WG LC on draft-ietf-idr-sr-policy-safi-00 and draft-ietf-idr-bgp-sr-segtypes-ext-02 (2/15/2024 to 2/29/2024)
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.39
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, 22 Feb 2024 02:12:44 -0000

Hi Sue,

I am not aware of any undisclosed IPR related to this document.

Thanks,
Ketan


On Fri, 16 Feb, 2024, 3:43 am Susan Hares, <shares@ndzh.com> wrote:

> Greetings IDR:
>
>
>
> This begins a 2-week WG LC on the following two drafts created from the
> text in
>
> draft-ietf-idr-segment-routing-te-policy-18 – that the IDR WG approved for
> publication:
>
>
>
>    - draft-ietf-idr-sr-policy-safi-00  (proposed standard)
>
> https://datatracker.ietf.org/doc/draft-ietf-idr-sr-policy-safi/
>
>    - draft-ietf-idr-bgp-sr-segtypes-ext-02 (experimental)
>
> https://datatracker.ietf.org/doc/draft-ietf-idr-bgp-sr-segtypes-ext/
>
>
>
> The Authors (per IETF policy) are asked to respond to this message with a
>
> message indicating whether they know of any undisclosed IPR as the
> documents stand now.
>
> Please note there are 3 IPR declarations on these drafts.
>
>
>
> History:
>
> ======
>
> After reviewing draft-ietf-idr-segment-routing-te-policy-18, Andrew Alston
> (IDR RTG AD)
>
> asked that draft-ietf-idr-segment-routing-te-policy be split into two
> parts because
>
> some segment types (C-L) did not have two implementations.
>
> Therefore, draft-ietf-idr-bgp-srsegtypes-ext-02 contains the text for
>
> Segment types C-L.   This split has been discussed at IETF meetings.
>
>
>
> Since Andrew Alston had personally implemented this draft,
>
> he also asked for additional reviews on procedures.
>
>
>
> During this review, the procedures regarding the link to RFC9012 were
> improved.
>
>
>
> Issues in call:
>
> ============
>
> During the WG should note that the procedures specified in
>
> draft-ietf-idr-sr-policy-safi-00 do the following:
>
>
>
>    1. Only apply to the SR Policy Tunnel (15) + SR Policy SAFI
>    2. Do not require any of the TLVs defined in RFC9012 for other tunnel
>    types
>    3. May ignore TLVs defined in RFC9012 for other tunnel types
>    4. Do not use the validation process in RFC9012, and depend on the
>    SRPM to validate content.
>    5. Makes changes to Color Extended Community [RFC9012] to add to
>    2-bits [C, O]
>
> To support “color-only” (CO)  functions of section 8.8 of [RFC9256]
>
>
>
> C0 – type 0 (00) – Specific end-point match (Match endpoint that is BGP
> NH)
>
>          type 1 (01) - Specific or null end-point match (BGP NH or null
> (default gw))
>
>          type 2 (10) – Specific, null, or any end-point match (BGP NH,
> Null, or any endpoint)
>
>          type 3 (11) – Reserved
>
>
>
> The SR Policy Tunnel functions in this draft use BGP as a transport
> mechanism for the
>
> Information contained in the SR Policy.
>
>
>
> Please note that these procedures split the context validation away from
> the
>
> BGP module into the SRPM module.   This split is similar to the BGP-LS
> split
>
> syntax validation from context validation.
>
>
>
> There are multiple implementations of this technology as detailed at:
>
>
> https://wiki.ietf.org/group/idr/BGP-Implementation-report/draft-ietf-idr-segment-routing-te-policy-implement
>
>
>
> The WG members are asked to confirm their agreement to the changes made in
> this document.
>
>
>
> If there are questions, please ask them on this mail thread.  Please note
> any errors in the call are mine (and not the authors).
>
>
>
> Cheerily, Sue
>
>
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr
>