Re: [spring] WG Adoption Call - draft-cheng-rtgwg-srv6-multihome-egress-protection (02/09/24 - 02/24/24)

Ketan Talaulikar <ketant.ietf@gmail.com> Wed, 21 February 2024 16:06 UTC

Return-Path: <ketant.ietf@gmail.com>
X-Original-To: spring@ietfa.amsl.com
Delivered-To: spring@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C598C14CEFC; Wed, 21 Feb 2024 08:06:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.105
X-Spam-Level:
X-Spam-Status: No, score=-2.105 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, 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 yE9slQDTZp3F; Wed, 21 Feb 2024 08:06:21 -0800 (PST)
Received: from mail-ej1-x636.google.com (mail-ej1-x636.google.com [IPv6:2a00:1450:4864:20::636]) (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 8C4FEC14F712; Wed, 21 Feb 2024 08:06:21 -0800 (PST)
Received: by mail-ej1-x636.google.com with SMTP id a640c23a62f3a-a2f22bfb4e6so854165966b.0; Wed, 21 Feb 2024 08:06:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1708531579; x=1709136379; 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=PDX7CBzVjr7LdnTlc2o4Dis8279QNvF9xkHES0cLz8I=; b=knEGvDmXjBGFFyWuOx/T9MrN2STWEHWDx7GPxExi6Jqrn6/c30eVou0k4gjNIzMUhN XRf3ox4AaQG/cbAaxsPzFLCV3xJ4wQOxbA8BC1g7HDuhtFfnrrlMbUknDkuEs/J3PTMm I/2vc+dnU0Sy5meDwakB1n7UbSku7MKkpe74ov4HEFrC/JFplcQ/KYoSZgS3Zqr4cMo3 lcJIoMv+5LkAc5h4sp1n7qCxwhMA9RxfWrQdvrt+52waR5Dm3BlK7KAt0LBfGo0XuHLO mTxZ4Y66NcFEktX6z8LX1i0yMuzR181SHNO10YTyO+SPCl/zi3tvRry90ucc6yGgcwk0 Jm2Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1708531579; x=1709136379; 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=PDX7CBzVjr7LdnTlc2o4Dis8279QNvF9xkHES0cLz8I=; b=wSH62nRSPfi6kzh2fNJLb8ovC+kb3gEZz/uoZcLS74Drq6KKqzE7F3kg+CaQq4ew5a nfEKqALm9wtydMlD1fRKxAFmnQq/rdtfXH4BOFgNcUmCg83SWOqhW2dnD4ok6ePifPjZ QKVm9z+YCVy2eGGQI4uo5mt3E6Cco/2R7qkmtpWiu+pjP274c9waH1n+Fhm0r6OWx78O bH2bdjCm3GvPuJnBq5N1ybHm8uoMfJ4CfK9mJcIiWGZrhE1P+F3boQ55TV3siDA2FzFg wksSukPG8/l33DUyAQ2fus0mWhfXIq8VTnkzeZ8ruBjVM0fie7u3hWdCyUijHieen6Pn fukQ==
X-Forwarded-Encrypted: i=1; AJvYcCXlWAxPe3ba2KBVz9RNz7kTDtO4MtkSUowpK0zkIeQyHSjwtvZ9/A6trd49Z1ZPPSAkPz4T9u5iWSXcyoeGZfIIlAAZi84Qd3jkAfRBRCI2x+uH0b+UYpm2dgesgvXNj3BvNd2u+DiXamkk1cyjZsY8O0rl/RN48F5l8WrUr60huAsStA09FomwOQkvxv2DXUxl8RQ=
X-Gm-Message-State: AOJu0Yx0yEKPIkArXMOowqkedza33eqh5ukMFkLL3WYMPWjgXR/boP3h h2MMaleJgNnz3947covGyH9ngrsX/MPrB0azmar0bUW5SZwpJXG/qxp44jqhaYSVSIigO+H9/+1 Cvx7VYNfgWhRE+SpatE00eMArBDbNMH/r
X-Google-Smtp-Source: AGHT+IGAaq5Xk0khoakKgJXDBtgTBYNM8Rqdcgj9Kc+UT3Uo3GnJwYCIGjepEysVVXyuHUdq0aS4AcZnDLvn8YIYUh0=
X-Received: by 2002:a17:906:718d:b0:a3e:7cd8:3db7 with SMTP id h13-20020a170906718d00b00a3e7cd83db7mr7228823ejk.68.1708531579351; Wed, 21 Feb 2024 08:06:19 -0800 (PST)
MIME-Version: 1.0
References: <CABY-gOMQ=LaECWJsJHsdKX7i+BUsiX=LF5b5ZPMVp=3qQjZ8Mg@mail.gmail.com>
In-Reply-To: <CABY-gOMQ=LaECWJsJHsdKX7i+BUsiX=LF5b5ZPMVp=3qQjZ8Mg@mail.gmail.com>
From: Ketan Talaulikar <ketant.ietf@gmail.com>
Date: Wed, 21 Feb 2024 21:36:06 +0530
Message-ID: <CAH6gdPyuWV=xvDerDCtXnD1T5CGymsm+b1i-idRGEs1w9aui=A@mail.gmail.com>
To: Yingzhen Qu <yingzhen.ietf@gmail.com>
Cc: RTGWG <rtgwg@ietf.org>, spring@ietf.org, rtgwg-chairs <rtgwg-chairs@ietf.org>, draft-cheng-rtgwg-srv6-multihome-egress-protection <draft-cheng-rtgwg-srv6-multihome-egress-protection@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000dffd310611e68194"
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/hVBXKnfbMyiRJrQ7BB42j3Yuw0Q>
Subject: Re: [spring] WG Adoption Call - draft-cheng-rtgwg-srv6-multihome-egress-protection (02/09/24 - 02/24/24)
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "Source Packet Routing in NetworkinG \(SPRING\)" <spring.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spring>, <mailto:spring-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spring/>
List-Post: <mailto:spring@ietf.org>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spring>, <mailto:spring-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Feb 2024 16:06:22 -0000

Hi Yingzhen/All,

I have some concerns regarding the adoption of this document.


   - Do we need these different solutions?

KT> No. There is one common author for both these drafts who is also from a
vendor. I hope that person is also able to evaluate implementation aspects
and pick one solution.
KT> Does the adoption of this solution make the other draft "dead"?

   - Technical merits and drawbacks of each solution

KT> The existing WG draft needs IGP protocol extensions and its
implementation is very complex (as stated in the document under adoption).

   - If there is any implementation of the proposals, please voice it.

KT> I think this is the key question and look forward to the answer.

Coming to this document, please find below my comments/concerns:

1) There is no pseudocode for the new VPN behavior with PSD that covers the
entire behavior - i.e., one that covers not just the "normal" case but the
failure scenarios as well (e.g., PE/CE link failure).
2) The draft requires a transit IPv6 node to perform SRH processing for the
SID that does not belong to it (this is some action that a P router needs
to do when reachability to the PE is lost) and hence does not know what
that SID behavior is. This is something very new for SRv6 and it can cause
problems. e.g., consider the case that the active segment points to a BSID
- what happens when a BSID is skipped.

Thanks,
Ketan

On Sat, Feb 10, 2024 at 1:00 AM Yingzhen Qu <yingzhen.ietf@gmail.com> wrote:

> Hi,
>
> This email begins a 2 week WG adoption poll for the following draft:draft-cheng-rtgwg-srv6-multihome-egress-protection-05 - SRv6 Egress Protection in Multi-homed scenario (ietf.org) <https://datatracker.ietf.org/doc/draft-cheng-rtgwg-srv6-multihome-egress-protection/>
>
> Please review the document and indicate your support or objections by Feb 24th, 2024.
>
> Please note that there is an existing WG document:draft-ietf-rtgwg-srv6-egress-protection-16 - SRv6 Path Egress Protection <https://datatracker.ietf.org/doc/draft-ietf-rtgwg-srv6-egress-protection/> Which proposes fast protections for the egress node and link of an SRv6 path through extending IGP and using Mirror SID. As you discuss adopting draft-cheng-rtgwg-srv6-multihome-egress-protection, please also consider:
>
>
>    - Do we need these different solutions?
>    - Technical merits and drawbacks of each solution
>    - If there is any implementation of the proposals, please voice it.
>
> Authors, please respond to the list indicating whether you are aware of any IPR that applies to the draft.
>
> Also copying SPRING WG.
>
> Thanks,
> Yingzhen (RTGWG Co-chair)
>
> _______________________________________________
> rtgwg mailing list
> rtgwg@ietf.org
> https://www.ietf.org/mailman/listinfo/rtgwg
>