Re: [IPv6] Subject: Mandating SRH when using C-SIDs (draft-ietf-spring-srv6-srh-compression)
Francois Clad <fclad.ietf@gmail.com> Thu, 04 April 2024 13:39 UTC
Return-Path: <fclad.ietf@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DFC3BC14CF18; Thu, 4 Apr 2024 06:39:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.094
X-Spam-Level:
X-Spam-Status: No, score=-1.094 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, FREEMAIL_REPLY=1, 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, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no 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 60YvbaSUS8Bq; Thu, 4 Apr 2024 06:39:09 -0700 (PDT)
Received: from mail-ed1-x529.google.com (mail-ed1-x529.google.com [IPv6:2a00:1450:4864:20::529]) (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 EAF10C151539; Thu, 4 Apr 2024 06:39:08 -0700 (PDT)
Received: by mail-ed1-x529.google.com with SMTP id 4fb4d7f45d1cf-56c404da0ebso1546949a12.0; Thu, 04 Apr 2024 06:39:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1712237947; x=1712842747; 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=J0lEaAZITZxibCAu0mvdr43yyOdDixr3OuUXLHR0Drg=; b=KqndgGu4nexSKUGm2YfnJVAD6OSOJvcDZjOLa444V7G2ccg+CnodbpmwdBrwma+Du+ OLUeTC9AOTtvbFTgBJBXCAuZrNfBqi1xz2J1deOzepe1QRHt3iKMvXnW5Bj/1vSRHQt0 JO8Ei0pOMo9m4o0mVGuebBY23FcM3GAm82LlRtMvT3MV+lTBiAxueDI5KW49kcdfz9li 1lUSTyqHaAHZtfTOaR5uBrJBtKh9Px0Croqhos/6t9GT0Erjb+KNss7uO9K5rkN6rSLo NUX3pCA/lsfIxKspraxidZ9KLFzbrkFGDp0nd+2arwniBO/5F4wlaRZFTkJp4e+G4BfS mZFw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1712237947; x=1712842747; 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=J0lEaAZITZxibCAu0mvdr43yyOdDixr3OuUXLHR0Drg=; b=hmAPsfR0Pz6C/lPtkuypUQMyr02nwtw4Bf6+fTPT2o7991aQujwubXRudNNatWJXuR kEN9wfZF7wbjJPEEVAUs1YqjkDECEOLJwgur8W/aRRwyLyujRykz6NfLzidtNZMpJ/ZS t4HNdlAYZmrXTEjqYAsgetu8jlKo30iVI0fxfga9lKjy1+BWMoFpQe4lw7Jqlxbsu6kK h9SdIvvZiKMQwnNop77VBInz/Mx5LkUiB/IkBHdEuPbq+l5dN+ommNtebWDFDz/piLdP dyp6c3PVXIxdrxOZz8PiPtp7rPwB/CgeAv1zRQpfjZ8LluoBqC2qEC4EjXsq0Wxc0F7h pPGQ==
X-Forwarded-Encrypted: i=1; AJvYcCW65YtqSd1I8ypurKbLArtWTkXqjZ80Y4if5tJcnE0KsWuwTjxAyak/qtmgW2CrNGKoKFX6z4F6qtj9zzVJQZBc7c/QgFuuoMlYW3DvlfBn5fj1k3vCmpSQ44XedrCrU6v8d28DxkE=
X-Gm-Message-State: AOJu0YxKz1Yrja9wpJfLC/gYQXMDIVbtZ5gCedhB/f+Wq4IK43V/Xaap SgSUj+BJWh76aRWv4x4HjQJdXVtuBZTDtIY4qPypZygHQ1MHlXv1wUdTrDRkj3PPDB4Q+uz29bv TTW9LMk+HhuDNzEksCAQUnyq8Jg==
X-Google-Smtp-Source: AGHT+IHgT2uICztr5y8q9Hjh5PSD/qNfx+cYHE0b73dpt3CNePbG7AlfM0sdWpTPePX8VsjtVBvtAIaIsuTQe5lSfzo=
X-Received: by 2002:a17:907:7d93:b0:a47:16d1:113f with SMTP id oz19-20020a1709077d9300b00a4716d1113fmr2352514ejc.47.1712237947196; Thu, 04 Apr 2024 06:39:07 -0700 (PDT)
Received: from 1064022179695 named unknown by gmailapi.google.com with HTTPREST; Thu, 4 Apr 2024 13:39:06 +0000
Received: from 1064022179695 named unknown by gmailapi.google.com with HTTPREST; Thu, 4 Apr 2024 13:39:03 +0000
MIME-Version: 1.0 (Mimestream 1.2.6)
References: <CAMMESszUUdDw-xnDtZKqz75g6SXZ+7mXtZujBKwN+hxypC-Kuw@mail.gmail.com> <CAMMESswF_NnpK7_xk9OXmmocU8P7pne0gmPjCkapXEQVfQA2zQ@mail.gmail.com> <CAHT6gR--Qw7W0ZqyfdEupTpLAjeJ5OLTTjzM6NvQ87zdizgb8Q@mail.gmail.com> <CAO42Z2xHNgzhmgC6mPrauSQZ6Q4mcgD_FOp_uWqRpz=pFwa7_w@mail.gmail.com>
In-Reply-To: <CAO42Z2xHNgzhmgC6mPrauSQZ6Q4mcgD_FOp_uWqRpz=pFwa7_w@mail.gmail.com>
From: Francois Clad <fclad.ietf@gmail.com>
Date: Thu, 04 Apr 2024 13:39:06 +0000
Message-ID: <CAHT6gR-q9B60fcvT7nTfErS8M+hUm+x8zoez0KkYiPtTthaYYg@mail.gmail.com>
To: Mark Smith <markzzzsmith@gmail.com>
Cc: Alvaro Retana <aretana.ietf@gmail.com>, 6man <ipv6@ietf.org>, spring-chairs@ietf.org, SPRING WG List <spring@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000009d1bee0615457617"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/ymh6VdnywWZA2_7PV3eLCXJUQv8>
Subject: Re: [IPv6] Subject: Mandating SRH when using C-SIDs (draft-ietf-spring-srv6-srh-compression)
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Apr 2024 13:39:13 -0000
Hi Mark, Tcpdump/wireshark decodes the IPv6 header just fine. I do not see any issue here. Cheers, Francois On 4 Apr 2024 at 14:09:43, Mark Smith <markzzzsmith@gmail.com> wrote: > > > On Thu, 4 Apr 2024, 22:50 Francois Clad, <fclad.ietf@gmail.com> wrote: > >> Hi Alvaro, all, >> >> RFC 8754 allows the SR source node to omit the SRH when it contains >> redundant information with what is already carried in the base IPv6 header. >> Mandating its presence for C-SID does not resolve any problem because it >> will not provide any extra information to the nodes along the packet path. >> > > How are troubleshooting tools like 'tcpdump' going to know how to > automatically decode these packets as SRv6 packets if there is no SRH? > > > >> Specifically for the case of middleboxes attempting to verify the >> upper-layer checksum, >> >> - An SRv6-unaware middlebox will not be able to verify the >> upper-layer checksum of SRv6 packets in flight, regardless of whether an >> SRH is present or not. >> - An SRv6 and C-SID aware middlebox will be able to find the ultimate >> DA and verify the upper-layer checksum in flight, regardless of whether an >> SRH is present or not. >> >> >> Furthermore, transit nodes (e.g., middleboxes) should not attempt to >> identify SRv6 traffic based on the presence of the SRH, because they will >> miss a significant portion of it: all the best-effort or Flex-Algo traffic >> steered with a single segment may not include an SRH, even without C-SID. >> Instead, RFC 8402, 8754, and 8986 define identification rules based on the >> SRv6 SID block. >> >> Thanks, >> Francois >> >> >> On 2 Apr 2024 at 19:44:51, Alvaro Retana <aretana.ietf@gmail.com> wrote: >> >>> [Moving this conversation up on your mailbox. :-) ] >>> >>> [Thanks, Robert and Tom for your input!] >>> >>> >>> We want to hear from more of you, including the authors. Even if you >>> already expressed your opinion in a different thread, please chime in here. >>> >>> We will collect feedback until the end of this week. >>> >>> Thanks! >>> >>> Alvaro. >>> >>> On March 28, 2024 at 8:06:18 AM, Alvaro Retana (aretana.ietf@gmail.com) >>> wrote: >>> >>> >>> 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 >>> >>> -------------------------------------------------------------------- >>> IETF IPv6 working group mailing list >>> ipv6@ietf.org >>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 >>> -------------------------------------------------------------------- >>> >> -------------------------------------------------------------------- >> IETF IPv6 working group mailing list >> ipv6@ietf.org >> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 >> -------------------------------------------------------------------- >> >
- Re: [IPv6] Subject: Mandating SRH when using C-SI… Robert Raszuk
- Re: [IPv6] Subject: Mandating SRH when using C-SI… Tom Herbert
- [IPv6] Subject: Mandating SRH when using C-SIDs (… Alvaro Retana
- Re: [IPv6] Subject: Mandating SRH when using C-SI… Robert Raszuk
- Re: [IPv6] Subject: Mandating SRH when using C-SI… Tom Herbert
- Re: [IPv6] Subject: Mandating SRH when using C-SI… Robert Raszuk
- [IPv6] Requiring Tunneling - subject change Joel Halpern
- Re: [IPv6] Requiring Tunneling - subject change Martin Vigoureux (Nokia)
- Re: [IPv6] Requiring Tunneling - subject change Bob Hinden
- Re: [IPv6] Subject: Mandating SRH when using C-SI… Tom Herbert
- Re: [IPv6] Requiring Tunneling - subject change Robert Raszuk
- Re: [IPv6] Subject: Mandating SRH when using C-SI… Alvaro Retana
- Re: [IPv6] Subject: Mandating SRH when using C-SI… Francois Clad
- Re: [IPv6] Subject: Mandating SRH when using C-SI… Mark Smith
- Re: [IPv6] Subject: Mandating SRH when using C-SI… Francois Clad
- Re: [IPv6] Subject: Mandating SRH when using C-SI… Tom Herbert
- Re: [IPv6] Subject: Mandating SRH when using C-SI… Francois Clad
- Re: [IPv6] Subject: Mandating SRH when using C-SI… Tom Herbert
- Re: [IPv6] Subject: Mandating SRH when using C-SI… Robert Raszuk
- Re: [IPv6] Subject: Mandating SRH when using C-SI… Tom Herbert
- Re: [IPv6] Subject: Mandating SRH when using C-SI… Ole Troan
- Re: [IPv6] Subject: Mandating SRH when using C-SI… Michael Richardson
- Re: [IPv6] Subject: Mandating SRH when using C-SI… Tom Herbert
- Re: [IPv6] Subject: Mandating SRH when using C-SI… Tom Herbert
- Re: [IPv6] Subject: Mandating SRH when using C-SI… Cheng Li
- Re: [IPv6] Subject: Mandating SRH when using C-SI… Ole Trøan
- Re: [IPv6] Subject: Mandating SRH when using C-SI… Robert Raszuk
- Re: [IPv6] Subject: Mandating SRH when using C-SI… Tom Herbert
- Re: [IPv6] Subject: Mandating SRH when using C-SI… Robert Raszuk
- Re: [IPv6] Subject: Mandating SRH when using C-SI… Adrian Farrel
- Re: [IPv6] Subject: Mandating SRH when using C-SI… Tom Herbert
- Re: [IPv6] Subject: Mandating SRH when using C-SI… Michael Richardson
- Re: [IPv6] Subject: Mandating SRH when using C-SI… Suresh Krishnan
- Re: [IPv6] Subject: Mandating SRH when using C-SI… Francois Clad
- Re: [IPv6] Subject: Mandating SRH when using C-SI… Robert Raszuk
- Re: [IPv6] Subject: Mandating SRH when using C-SI… Tom Herbert
- Re: [IPv6] [spring] Subject: Mandating SRH when u… Suresh Krishnan
- Re: [IPv6] [spring] Subject: Mandating SRH when u… Michael Richardson
- Re: [IPv6] Subject: Mandating SRH when using C-SI… Robert Raszuk
- Re: [IPv6] Subject: Mandating SRH when using C-SI… Tom Herbert
- Re: [IPv6] [spring] Subject: Mandating SRH when u… Bob Hinden
- Re: [IPv6] Subject: Mandating SRH when using C-SI… Tal Mizrahi
- Re: [IPv6] [spring] Subject: Mandating SRH when u… Antoine FRESSANCOURT
- Re: [IPv6] [spring] Subject: Mandating SRH when u… Tom Herbert
- Re: [IPv6] [spring] Subject: Mandating SRH when u… Robert Raszuk
- Re: [IPv6] Subject: Mandating SRH when using C-SI… Ketan Talaulikar
- Re: [IPv6] [spring] Subject: Mandating SRH when u… Mark Smith