Re: [IPv6] [spring] WG Adoption call for Segment Routing Header encapsulation for Alternate Marking Method
Ketan Talaulikar <ketant.ietf@gmail.com> Sat, 18 February 2023 04:16 UTC
Return-Path: <ketant.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 C6EB7C15DD44; Fri, 17 Feb 2023 20:16:15 -0800 (PST)
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, 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, 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 qL6J3adaO2WC; Fri, 17 Feb 2023 20:16:11 -0800 (PST)
Received: from mail-ed1-x535.google.com (mail-ed1-x535.google.com [IPv6:2a00:1450:4864:20::535]) (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 AA948C1595E5; Fri, 17 Feb 2023 20:16:11 -0800 (PST)
Received: by mail-ed1-x535.google.com with SMTP id cz7so8251716edb.12; Fri, 17 Feb 2023 20:16:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=/b9ii+ASr6buFD5tVfF2+TqKEq8Eo8cbhR6fEcXQt0I=; b=Ey4EoQlvujWb8BrRyqH5bs8tdIVBKazIRAKe6TYvf/P4fOhgOMrNU6xLz33d2njTIy YgA3rCp2fjZKKF1JeC1Q8bFLSjNkWRd+gCJD8AgbeBcrBsloJATMaqMzaLUWmc+WRsxF yBTqBrTp+XXIizcg6qFDJmd1UtqYGVlY8aswpVKMQRx7WmBpw1QVs8poT+nlmHmtPhop Zo9Rro73dX2mSuJ9SGWHR3hZ2VLQKCmqbQCNxoa7k8f+NdvhIxofsOx+7qNBR3jmYyTK 2Irmfq5MWtCqzQ+LaENCRP9+UtwtyD09K5LerCgoixWd0KqceCp0JnknWqeuSCR1gI9A yggg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; 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=/b9ii+ASr6buFD5tVfF2+TqKEq8Eo8cbhR6fEcXQt0I=; b=mjY55CQXhNO+VNLSGI1C9+Up+r3S3KYvpkLmntHQ3oZEuOdkCAOblKDqvmT8hBL6o/ mmRKiclcl11O14zNMPBpr+UmvULNdTlWZyk48AeGNbq0NmFhfcOOrTtJJD1nUZ3PSCkU wph9YifQy70XIOSO3zEzyfGppgzqb1A+PK9J7w2IAtgjw6V4HpgGwYfBegsvFnfiIbZU hHMOGvnTCuqeXetqz0Lx+P6w9+4j6svR6gFuKu3O7kYAoI0fUwXnUnOWh+O72R84hbFj fSVzutY+9CiJj//SS1G6eYKaZkKvX0QKOlr/omXRRjuphhxDtKw4p9BgAFxU2sC08aIg OrdA==
X-Gm-Message-State: AO0yUKW5cbQEm0Q4/tF/AJ5PyEc3hv3/MBKtrmvhxOhhLebzqtqh+2wh QmZjkhUGArq6JYi4ppGAFRD/O8U7+Q2V96LNQms=
X-Google-Smtp-Source: AK7set8LRWRAlDD0N6mO6S43ugKeFLY88WDNvgEV2V7hYEilrDdoiqhl2JTE5LstCvLnXoPg2LMmvn3Iw8lAsPSZMbg=
X-Received: by 2002:a17:906:a292:b0:8b1:28e5:a1bc with SMTP id i18-20020a170906a29200b008b128e5a1bcmr1303722ejz.5.1676693770072; Fri, 17 Feb 2023 20:16:10 -0800 (PST)
MIME-Version: 1.0
References: <c51e4a3f-5e6e-5386-4e6a-23709d52c1fe@joelhalpern.com> <CAH6gdPz72FkfCBVNf88cwww+dZmbFC+im+YdB0JtByNk3TZ6gA@mail.gmail.com> <83562aebefc14043993de7ae1d0e7a57@huawei.com> <CAH6gdPxEGkOS4BPcmhk199aibFP+bzRNCqY+pFHEr8oHELkP8A@mail.gmail.com> <CAOj+MMHXKzAw3iPFO5zLTY+qsn_JrwLocbGcaX07D91hxofOvQ@mail.gmail.com> <CA+RyBmVv2q1PUJ2TVYKP_d+-4CbVB3PLuWuEVYD69e+wP2=1ZQ@mail.gmail.com> <CAOj+MME1HPd_G-Ef7Y74EzhTpmid9xsuvse9wVFEYkg48E7-ag@mail.gmail.com>
In-Reply-To: <CAOj+MME1HPd_G-Ef7Y74EzhTpmid9xsuvse9wVFEYkg48E7-ag@mail.gmail.com>
From: Ketan Talaulikar <ketant.ietf@gmail.com>
Date: Sat, 18 Feb 2023 09:45:58 +0530
Message-ID: <CAH6gdPyeZhyEj7y=1XMycpLQy5D0tzwr61qDuKLf+DydMz6CtQ@mail.gmail.com>
To: Robert Raszuk <robert@raszuk.net>
Cc: Greg Mirsky <gregimirsky@gmail.com>, Giuseppe Fioccola <giuseppe.fioccola@huawei.com>, SPRING WG List <spring@ietf.org>, 6man <ipv6@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000008ff74d05f4f1b095"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/NA17miWaZxsthKTlmLEHnFr96YQ>
Subject: Re: [IPv6] [spring] WG Adoption call for Segment Routing Header encapsulation for Alternate Marking Method
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: Sat, 18 Feb 2023 04:16:16 -0000
Hi Robert/Authors, Thanks for sharing that perspective. It would be very helpful if the authors can share their perspective as well and update the draft (especially with challenges/issues that they have found with the RFC9343 approach). Thanks, Ketan On Sat, Feb 18, 2023 at 3:03 AM Robert Raszuk <robert@raszuk.net> wrote: > Hi Greg, > > It all depends on the hardware support. > > Some may support SRH parsing and processing, but may choose not to support > DOH or HbH v6 headers extensions parsing and processing. > > Some may be fine to process SRH in line card's CPU or in smart NICs while > may in the same time not choose to do the same parsing of extensions to DOH > or HbH headers. > > So you are all correct that the operator is enabled to control this per > node and per flow. But they may not always be able to assure that all IPv6 > headers are up to speed with all IETF extensions in running nodes. > > Bottom line is that if we just look at this IETF aspect the spec surely > looks redundant. But if we extend the view to practical field deployments > we may see the value. > > Cheers, > Robert > > > > On Fri, Feb 17, 2023 at 10:25 PM Greg Mirsky <gregimirsky@gmail.com> > wrote: > >> Hi Robert, >> I think that the solution defined in RFC 9343 can operationally achieve >> everything that is suggested in this draft. Consider an SRv6 domain. I >> imagine that the support of on-path telemetry, whether IOAM or Alternate >> Marking, is controlled per node over the management plane. Furthermore, it >> seems like such control is granular, i.e., per a flow (definition of a flow >> can be further discussed). If my assumptions are correct, an operator can >> enable the support of the Alternate Marking on-path telemetry collection >> using RFC 9343 solution on either all nodes within the SRv6 domain or on >> any sub-set, e.g., nodes that terminate route segments. Hence, I believe >> that RFC 9343 already defines what is required to use the Alternate Marking >> method in an SRv6 domain. Do you see that I've missed anything? >> >> Regards, >> Greg >> >> On Fri, Feb 17, 2023 at 8:20 AM Robert Raszuk <robert@raszuk.net> wrote: >> >>> Hey Ketan, >>> >>> > The encodings are exactly identical - zero difference (from a quick >>> read). Am I missing something? >>> >>> It looks like RFC9343 is defining extension to IPv6 Options Header while >>> the subject draft is defining an extension to SRH. >>> >>> So while data fields look indeed identical the intended placement of >>> this seems very different. >>> >>> In fact one could envision that there is indeed a class of applicability >>> for various measurements which is sufficient to be done only on SRH parsing >>> segment endpoints, hence I find this draft actually pretty useful. >>> >>> Cheers, >>> Robert. >>> >>> >>> On Fri, Feb 17, 2023 at 3:50 PM Ketan Talaulikar <ketant.ietf@gmail.com> >>> wrote: >>> >>>> Hi Giuseppe, >>>> >>>> To clarify, I was looking for some text that explains the need for this >>>> draft given RFC9343. The proposal first needs to provide a new/different >>>> functionality or one that is more efficient (just an example) that is not >>>> provided by RFC9343. >>>> >>>> The encodings are exactly identical - zero difference (from a quick >>>> read). Am I missing something? >>>> >>>> Deployment aspects come into play later. >>>> >>>> Given that it is the same author team, I am more curious to know if you >>>> have found any challenges with what's in RFC9343 for SRv6 deployments which >>>> require you to come up with these new encoding. >>>> >>>> Will await the document update. >>>> >>>> Thanks, >>>> Ketan >>>> >>>> PS: You would have seen similar questions being asked all the time ;-) >>>> >>>> >>>> On Fri, Feb 17, 2023 at 8:00 PM Giuseppe Fioccola < >>>> giuseppe.fioccola@huawei.com> wrote: >>>> >>>>> Hi Ketan, >>>>> >>>>> Thank you for your comments. >>>>> >>>>> I plan to revise the draft and add a new section on deployment >>>>> recommendations. >>>>> >>>>> Anyway, I think that the choice between DOH and SRH TLV may be a more >>>>> general decision that should be taken by SPRING and 6MAN. Indeed, the same >>>>> concern involves all the telemetry techniques, e.g. for IOAM the same two >>>>> mechanisms have been proposed: see draft-ietf-ippm-ioam-ipv6-options and >>>>> draft-ali-spring-ioam-srv6 >>>>> >>>>> >>>>> >>>>> Regards, >>>>> >>>>> >>>>> >>>>> Giuseppe >>>>> >>>>> >>>>> >>>>> *From:* spring <spring-bounces@ietf.org> *On Behalf Of *Ketan >>>>> Talaulikar >>>>> *Sent:* Friday, February 17, 2023 12:46 PM >>>>> *To:* Joel Halpern <jmh@joelhalpern.com> >>>>> *Cc:* SPRING WG List <spring@ietf.org>; 6man <ipv6@ietf.org> >>>>> *Subject:* Re: [spring] [IPv6] WG Adoption call for Segment Routing >>>>> Header encapsulation for Alternate Marking Method >>>>> >>>>> >>>>> >>>>> Hi Joel/All, >>>>> >>>>> >>>>> >>>>> I share some of the questions and concerns of the chairs and other WG >>>>> members. >>>>> >>>>> >>>>> >>>>> Perhaps we need to give more time to the authors to add clarifying >>>>> text to the draft (what has been said on the list). >>>>> >>>>> >>>>> >>>>> I suggest a dedicated section towards the start of the document that >>>>> *only* focuses on why this mechanism is needed in addition to RFC9343. It >>>>> would be interesting if there is any analysis from the >>>>> implementation/deployment of RFC9343 that has shown it to be not suitable >>>>> for SRv6 deployments. >>>>> >>>>> >>>>> >>>>> Thanks, >>>>> >>>>> Ketan >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> On Thu, Feb 2, 2023 at 6:14 AM Joel Halpern <jmh@joelhalpern.com> >>>>> wrote: >>>>> >>>>> This call is for the draft at: >>>>> https://datatracker.ietf.org/doc/draft-fz-spring-srv6-alt-mark >>>>> >>>>> This email starts the WG adoption call for the subject draft (as >>>>> requested by the authors, with apologies from the WG chairs for how >>>>> long >>>>> it has taken to kick this out.) This call will run through the end of >>>>> the day on Feb 16. Pleaes read the whole email as there are a few >>>>> points, and it is not that long. >>>>> >>>>> Please comment on whether you think this topic is something you think >>>>> the spring WG should work, whether you think this draft is a good >>>>> starting point for such work, any issues or concerns you have, and >>>>> whether you would be willing to help be contributing and / or >>>>> reviewing >>>>> the work if the WG does choose to work on it. >>>>> >>>>> 6man is copied for their information, as this is different from but >>>>> related to an extension header proposal in front of 6man. >>>>> >>>>> Authors and named contributors, please confirm to the list that all >>>>> known, relevant, IPR has been disclosed. If it has note, please >>>>> remedy >>>>> this gap. >>>>> >>>>> The spring chairs have noted one aspect of this draft that caught our >>>>> eye, and we would appreciate WG members who comment on the adoption to >>>>> consider, and if possible opine, on this. As we read this draft, as >>>>> distinct from the related 6man extension header work, this causes the >>>>> recorded altmarks to only be updated at routers identified in the SRH >>>>> segment list. (We presume this would include all identified points in >>>>> a >>>>> compressed container.) We could not tell from the document what the >>>>> value was for this as distinct from getting the measurements at all >>>>> routers. Do WG members understand and agree that it does have value? >>>>> >>>>> As a lesser point, we consider that one quote in the draft is >>>>> misleading >>>>> and will likely need to be reworded in the near future. The draft say >>>>> "SRH TLV can also be used to encode the AltMark Data Fields for SRv6 >>>>> and >>>>> to monitor every node along the SR path." It is unclear if these was >>>>> intended to mean all routers (most of which would not see this TLV) or >>>>> if it was intended to refer to only those routers identified in the >>>>> SRH, >>>>> in which case we presume it will be reworded. >>>>> >>>>> Thank you, >>>>> >>>>> Joel >>>>> >>>>> -------------------------------------------------------------------- >>>>> 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 >>>> -------------------------------------------------------------------- >>>> >>> _______________________________________________ >>> spring mailing list >>> spring@ietf.org >>> https://www.ietf.org/mailman/listinfo/spring >>> >>
- [IPv6] WG Adoption call for Segment Routing Heade… Joel Halpern
- Re: [IPv6] WG Adoption call for Segment Routing H… Haoyu Song
- Re: [IPv6] WG Adoption call for Segment Routing H… Cheng Li
- Re: [IPv6] WG Adoption call for Segment Routing H… Giuseppe Fioccola
- Re: [IPv6] WG Adoption call for Segment Routing H… Tianran Zhou
- Re: [IPv6] WG Adoption call for Segment Routing H… Greg Mirsky
- Re: [IPv6] WG Adoption call for Segment Routing H… Mauro Cociglio
- Re: [IPv6] WG Adoption call for Segment Routing H… Giuseppe Fioccola
- Re: [IPv6] WG Adoption call for Segment Routing H… Greg Mirsky
- Re: [IPv6] WG Adoption call for Segment Routing H… Chongfeng Xie
- Re: [IPv6] [spring] WG Adoption call for Segment … xiao.min2
- Re: [IPv6] WG Adoption call for Segment Routing H… Dongjie (Jimmy)
- Re: [IPv6] WG Adoption call for Segment Routing H… Giuseppe Fioccola
- Re: [IPv6] [spring] WG Adoption call for Segment … Giuseppe Fioccola
- Re: [IPv6] WG Adoption call for Segment Routing H… Greg Mirsky
- Re: [IPv6] [spring] WG Adoption call for Segment … Haoyu Song
- Re: [IPv6] WG Adoption call for Segment Routing H… Gyan Mishra
- Re: [IPv6] WG Adoption call for Segment Routing H… 庞冉(联通集团中国联通研究院-本 部)
- Re: [IPv6] WG Adoption call for Segment Routing H… Giuseppe Fioccola
- Re: [IPv6] WG Adoption call for Segment Routing H… Giuseppe Fioccola
- Re: [IPv6] WG Adoption call for Segment Routing H… Ackermann, Michael
- Re: [IPv6] [spring] WG Adoption call for Segment … xiao.min2
- Re: [IPv6] WG Adoption call for Segment Routing H… Huaimo Chen
- Re: [IPv6] [spring] WG Adoption call for Segment … Xuewei Wang
- Re: [IPv6] [spring] WG Adoption call for Segment … Aijun Wang
- Re: [IPv6] [spring] WG Adoption call for Segment … Giuseppe Fioccola
- Re: [IPv6] [spring] WG Adoption call for Segment … Greg Mirsky
- Re: [IPv6] WG Adoption call for Segment Routing H… Nilo Massimo
- Re: [IPv6] [spring] WG Adoption call for Segment … Tianran Zhou
- Re: [IPv6] WG Adoption call for Segment Routing H… Ketan Talaulikar
- Re: [IPv6] [spring] WG Adoption call for Segment … Giuseppe Fioccola
- Re: [IPv6] [spring] WG Adoption call for Segment … Ketan Talaulikar
- Re: [IPv6] [spring] WG Adoption call for Segment … Robert Raszuk
- Re: [IPv6] [spring] WG Adoption call for Segment … Giuseppe Fioccola
- Re: [IPv6] [spring] WG Adoption call for Segment … Greg Mirsky
- Re: [IPv6] [spring] WG Adoption call for Segment … Robert Raszuk
- Re: [IPv6] [spring] WG Adoption call for Segment … Greg Mirsky
- Re: [IPv6] [spring] WG Adoption call for Segment … Greg Mirsky
- Re: [IPv6] [spring] WG Adoption call for Segment … Tianran Zhou
- Re: [IPv6] [spring] WG Adoption call for Segment … Ketan Talaulikar
- Re: [IPv6] WG Adoption call for Segment Routing H… Dhruv Dhody
- Re: [IPv6] [spring] WG Adoption call for Segment … Giuseppe Fioccola
- Re: [IPv6] WG Adoption call for Segment Routing H… Pengshuping (Peng Shuping)
- Re: [IPv6] [spring] WG Adoption call for Segment … Joel Halpern
- Re: [IPv6] WG Adoption call for Segment Routing H… bruno.decraene
- Re: [IPv6] WG Adoption call for Segment Routing H… Giuseppe Fioccola