Re: [spring] [IPv6] Subject: Mandating SRH when using C-SIDs (draft-ietf-spring-srv6-srh-compression)

Tom Herbert <tom@herbertland.com> Fri, 05 April 2024 14:31 UTC

Return-Path: <tom@herbertland.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 BE754C1D6FB2 for <spring@ietfa.amsl.com>; Fri, 5 Apr 2024 07:31:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.095
X-Spam-Level:
X-Spam-Status: No, score=-2.095 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, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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=herbertland.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 LFFjaWDVjg7Z for <spring@ietfa.amsl.com>; Fri, 5 Apr 2024 07:31:19 -0700 (PDT)
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 7C2FAC1F5891 for <spring@ietf.org>; Fri, 5 Apr 2024 07:31:05 -0700 (PDT)
Received: by mail-ed1-x532.google.com with SMTP id 4fb4d7f45d1cf-56e0acaf69aso2851326a12.1 for <spring@ietf.org>; Fri, 05 Apr 2024 07:31:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=herbertland.com; s=google; t=1712327464; x=1712932264; 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=4Dt1V9GLGE0dEnbFCV9+Ed45FShcW1dy24V6HCS9T1w=; b=DDRVZITYKHe4fkGrdwoVL/rkQYt52f6o5Q/E8pXU1Tr3VdqArZzANP+suJf+xJBQCZ Ej+Bk81wYV05AuRKwZkTSyse4zk+0YmzxnHFnw7rn93FmOkLpYkmrgQFiohWZAPrzEq5 2L7jmK+haHR3YdyEzUqT8URHPH3uG0hFjfDb5BMRx3ZIIB9Vk4HyxqGDXzWQPPPytq/r vz2Dq3GPLO2rlVzjtQbpKt0gGIUssCXkzUx7i3CEiMLrytOWIIwdp3osmmWKuBV1Uvy+ kgHtGzprcF8IkRfMl5X1pOFoqyIkDwe0IHJOqacs0+qrqn0gWmI6b1JdVdn4akVwiniz H5+w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1712327464; x=1712932264; 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=4Dt1V9GLGE0dEnbFCV9+Ed45FShcW1dy24V6HCS9T1w=; b=IqlKo06VpthOfPgqNP4i2knbjStNpKxk9s80dNZKpDyQ9olXLLatGemSsUixKmMncw qftSCXhHsdsCnl5IbENUV8U+ceQDpcARn9SA/pSejOfwmG4oca4e18x2CU2H0c6o3nSF g4bEbGp41jIN4ynjxzmRnkWWRrHVPIL0IIVqMbNmxo4qAVzczhOBqhZQj8jw1A7Wr8f9 DHG9QoJEQEV0ZcsBJtQRVV1mWFQj1oG+vR/Sh6h3mHHXB12lsBA1A6/oQYh1i/nyqfQN yZuR5yQM4Qg47OWWWnlHH0w8uKuAqFj+NSCFNrYmsbMLpV9RWlCprQh/ulh+TuaSMDNE CJqg==
X-Gm-Message-State: AOJu0YzFp2dq7yLoR68iVtwjecpOs04bqoX9llhVB/egDG/+bNfczoYB mQ8SfKe+aLmLNMBWQWcxZ+0bGRj1iLSp2+Gu4lNFB6+J6d3kltWME3sewYlal4AlslMp0cjwoD9 K8VUvA9Jvzd6Im6J5WZwYFoS8tGgGeop8Sk1/
X-Google-Smtp-Source: AGHT+IFYc+3N5IWXhnYmjo5SYBJVhPbDfhI6HWXurwsjtzdSrQjI24pNp+y8P/1BsXSBOH9hjEfPVEx+tlHYdmh2JD0=
X-Received: by 2002:a50:9b56:0:b0:56b:fd17:3522 with SMTP id a22-20020a509b56000000b0056bfd173522mr1205258edj.14.1712327463642; Fri, 05 Apr 2024 07:31:03 -0700 (PDT)
MIME-Version: 1.0
References: <CAMMESszUUdDw-xnDtZKqz75g6SXZ+7mXtZujBKwN+hxypC-Kuw@mail.gmail.com> <5dfe16dffc0b4717ba9d16e6ecb90d20@huawei.com>
In-Reply-To: <5dfe16dffc0b4717ba9d16e6ecb90d20@huawei.com>
From: Tom Herbert <tom@herbertland.com>
Date: Fri, 05 Apr 2024 10:30:49 -0400
Message-ID: <CALx6S36-8hX1i9WoZiThQogQMOfZx_nM42hGd=cm6zs4LLHJqw@mail.gmail.com>
To: Antoine FRESSANCOURT <antoine.fressancourt=40huawei.com@dmarc.ietf.org>
Cc: SPRING WG List <spring@ietf.org>, 6man <ipv6@ietf.org>, spring-chairs@ietf.org
Content-Type: multipart/alternative; boundary="00000000000035c67a06155a4edf"
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/w7wOJOJFdrW6F9ypiX6v2wq8bVM>
Subject: Re: [spring] [IPv6] Subject: Mandating SRH when using C-SIDs (draft-ietf-spring-srv6-srh-compression)
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: Fri, 05 Apr 2024 14:31:23 -0000

On Fri, Apr 5, 2024, 8:53 AM Antoine FRESSANCOURT <antoine.fressancourt=
40huawei.com@dmarc.ietf.org> wrote:

> Hello,
>
> After reading RFC 8754 and RFC 8986 together with the draft (version 14),
> it seems to me that the cases when the SRH will be omitted are quite
> limited, and will happen among nodes sharing the same locator block. We can
> assume that, in such cases, nodes exchanging packets carrying a C-SID
> without SRH will be managed by a single entity and that this entity can
> check whether some middlebox infer with packet relaying.


Antoine,

If it's such a limited use case then I have to ask if it's worth the effort
to make this a robust protocol? All we really need is a deterministic way
to distinguish SR packets from non-SR packets, which could be accomplished
by a minimum sized eight byte SRH. In other words, it seems like this
discussion is only about saving eight bytes on the wire for a narrow use
case.

Tom


>
> Then we could modify the text to mention that, if such an inference is
> detected, the packet should use a SRH. In my view, being clear about
> potential issue related with omitting the SRH and giving an alternative is
> enough, and gives some freedom to people willing to use C-SID without SRH
> in their context.
>
> Best regards,
>
> Antoine Fressancourt
>
> -----Original Message-----
> From: spring <spring-bounces@ietf.org> On Behalf Of Alvaro Retana
> Sent: jeudi 28 mars 2024 13:06
> To: SPRING WG List <spring@ietf.org>
> Cc: 6man <ipv6@ietf.org>; spring-chairs@ietf.org
> Subject: [spring] Subject: Mandating SRH when using C-SIDs
> (draft-ietf-spring-srv6-srh-compression)
>
> Focusing on the C-SID draft, some have suggested requiring the presence of
> the SRH whenever C-SIDs are used. Please discuss whether that is the
> desired behavior (or not) -- please be specific when debating the benefits
> or consequences of either behavior.
>
> Please keep the related (but independent) discussion of requiring the SRH
> whenever SRv6 is used separate. This larger topic may impact several
> documents and is better handled in a different thread (with 6man and spring
> included).
>
> Thanks!
>
> Alvaro
> -- for spring-chairs
>
> _______________________________________________
> spring mailing list
> spring@ietf.org
> https://www.ietf.org/mailman/listinfo/spring
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>