Re: [spring] WG Adoption call for https://datatracker.ietf.org/doc/draft-filsfilscheng-spring-srv6-srh-compression/

Greg Mirsky <gregimirsky@gmail.com> Thu, 07 October 2021 18:15 UTC

Return-Path: <gregimirsky@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 071A43A0D4F; Thu, 7 Oct 2021 11:15:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RBS2Tgv3GhzQ; Thu, 7 Oct 2021 11:15:33 -0700 (PDT)
Received: from mail-ed1-x52b.google.com (mail-ed1-x52b.google.com [IPv6:2a00:1450:4864:20::52b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 026123A0872; Thu, 7 Oct 2021 11:15:32 -0700 (PDT)
Received: by mail-ed1-x52b.google.com with SMTP id d9so2531208edh.5; Thu, 07 Oct 2021 11:15:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=JEixrYCqTKWeiR9DvYvqZ2G7yePKat3e0hhOv2wc34w=; b=FeL3dePPEY/nKbV8hOr5RwjyFqOC39Xql7K7v3lt1klN78UZgP1NSnJIaMm+VdyeD+ ubf34zoWNb5PtD8/JnoGNk3dQcUhF6YoUg9obP6y32BShnW5CPobQOfSCFoBAZV0g93Y 8Ir2yoMkFaXBvVUOoitT0uWftzDJO9l/kJnS3rD1fvQ6Gip0o4tYKoW976c41pOe21PE 88/t8xFrFWAt1qgGFMIPdcZMJrueMi2FUsMgoMtN6fiaYZEPvw/LonscNvtb99kUr8GR ahQ90ZsDcEFNNvl+9aFinwYXptSZ/XBtFH4zmz+s3qzn48BIRv75WJsce1Rvk32QXmLY 7JRQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=JEixrYCqTKWeiR9DvYvqZ2G7yePKat3e0hhOv2wc34w=; b=gH9ppWVJYDUoqBUcwcpydvmMJ5GxLqOh+6g8hwobVVO7fM9u6tSxhINMgpynNY14Zq Uce7TuJAita3E4IHptOGLPt7mjpgZURtTDfNoDr7G2auOGAHHvgwQ52qdIkgWkAq4G50 rYJwjHRp3/WiyWA3f1QAPI514+vPQPo7TGw/VvlDNKVah3DF7QQzLZt8rZZSTl2quMFV DgRK+qp/CYmlV4zVCkmgjQk1kQ3mQ3ACLvPKI8tVNv265Pp+zZTLjk93LE9ClHAggm+t /FXxp/sqQZjbYPiNXdViu0JggzV7DtIjN97wtTlLXWLZXW4kK3hvdXuCoDVQiPhQhlwH 6rhQ==
X-Gm-Message-State: AOAM530oJXPbic3sK93MlhBu5RLHuQIxTmk9Lp3ffqjaNnuPoIASVjBY TJWgw/qJBSRsYe1W8RAPE3OrNv7Rc4l4q62+Wry1vQFWOM8=
X-Google-Smtp-Source: ABdhPJzWifEfzsEmoRsKP/KruIpXxyXpHkT8FRu+I2dgOx1hVgbdYxluOxtC73AxMoN8OsyjQjqm1pxVRV6AJRwqzJ4=
X-Received: by 2002:a17:906:c302:: with SMTP id s2mr3479615ejz.499.1633630531172; Thu, 07 Oct 2021 11:15:31 -0700 (PDT)
MIME-Version: 1.0
References: <DM6PR13MB4204AEAF9D0F44DA0E4E0C4CD2AB9@DM6PR13MB4204.namprd13.prod.outlook.com> <DM8PR11MB5719868719840728F04A360EC9AE9@DM8PR11MB5719.namprd11.prod.outlook.com> <BL0PR05MB531610C8939F7E0C741E165AAEAF9@BL0PR05MB5316.namprd05.prod.outlook.com> <BN0PR11MB57263566709BA15200E44CBAC9AF9@BN0PR11MB5726.namprd11.prod.outlook.com> <BL0PR05MB53169700BE4620420B3F3BAEAEAF9@BL0PR05MB5316.namprd05.prod.outlook.com> <CAOj+MMGiPUq71C_hEeR74JT18jWYpmSHBihZKeRJZeeprL-Ldg@mail.gmail.com> <CA+RyBmXDe8Qsg9JBt0KPzNUDtCOTsF_+3SDEUoWgrssqSfK91Q@mail.gmail.com> <CO6PR11MB5650080ED84067C3943ACD66ACB09@CO6PR11MB5650.namprd11.prod.outlook.com> <CA+RyBmWWHfni+oqjo1-a0o0gtTnoUDuL7gRFSLwQYvfRGPdtwg@mail.gmail.com> <CO6PR11MB56507C80A718DB505DC97C73ACB19@CO6PR11MB5650.namprd11.prod.outlook.com>
In-Reply-To: <CO6PR11MB56507C80A718DB505DC97C73ACB19@CO6PR11MB5650.namprd11.prod.outlook.com>
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Thu, 07 Oct 2021 11:15:19 -0700
Message-ID: <CA+RyBmW_AvaMjpBSJMqoM8wG5OXo2q8j=yGa+qO75JGyC8uGbg@mail.gmail.com>
To: "Francois Clad (fclad)" <fclad@cisco.com>
Cc: Robert Raszuk <robert@raszuk.net>, Ron Bonica <rbonica=40juniper.net@dmarc.ietf.org>, James Guichard <james.n.guichard@futurewei.com>, SPRING WG <spring@ietf.org>, "spring-chairs@ietf.org" <spring-chairs@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000813e5605cdc73fac"
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/gAqgy0EceMz_QV_0wWU8IZYgI5Q>
Subject: Re: [spring] WG Adoption call for https://datatracker.ietf.org/doc/draft-filsfilscheng-spring-srv6-srh-compression/
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 07 Oct 2021 18:15:42 -0000

Hi Francois,
thank you for your detailed response and confirming that C-SIDs of
different flavors/behavior may be present in the same SRH and even the same
CSID container. I've noticed Ron's proposal as I was trying to formulate my
question. His proposal highlighted what I am trying to understand - the
relationship between NEXT-C-SID and REPLACE-C-SID. I concur with Ron. The
WG has adopted the compression analysis draft
<https://datatracker.ietf.org/doc/draft-ietf-spring-compression-analysis/>,
and the updates and an additional analysis Ron proposed will keep the
discussion and decision-making process on the firm technical foundation.

Regards,
Greg

On Thu, Oct 7, 2021 at 9:17 AM Francois Clad (fclad) <fclad@cisco.com>
wrote:

> Hi Greg,
>
>
>
> It is the role of the SR Source Node [Section 3.1 of RFC 8754] to form the
> segment list in the SRH. It learns about the available SIDs in the network
> with their associated behavior and flavors via control plane and/or
> management plane protocols, as described in Section 8 of RFC 8986, and
> selects the SIDs that are the most appropriate for the segment list.
>
>
>
> Each SR Segment Endpoint Node [Section 3.3 of RFC 8754] simply executes
> the pseudocode of a locally instantiated SID when it receives a packet
> matching that SID. The SR Segment Endpoint Node does not need to bother
> about the behavior/flavor of the subsequent SRv6 SIDs.
>
>
>
> This SRv6 logic applies to the C-SID flavors as well. The choice of
> flavors for the SIDs in the SID List is up to the SR Source Node.
>
>
>
> It is indeed possible to mix SIDs of different C-SID flavors in the same
> SRH, and even in a single C-SID container.
>
>
>
> Thanks,
>
> Francois
>
>
>
>
>
> *From: *Greg Mirsky <gregimirsky@gmail.com>
> *Date: *Wednesday, 6 October 2021 at 19:19
> *To: *Francois Clad (fclad) <fclad@cisco.com>
> *Cc: *Robert Raszuk <robert@raszuk.net>, Ron Bonica <rbonica=
> 40juniper.net@dmarc.ietf.org>, James Guichard <
> james.n.guichard@futurewei.com>, SPRING WG <spring@ietf.org>,
> spring-chairs@ietf.org <spring-chairs@ietf.org>
> *Subject: *Re: [spring] WG Adoption call for
> https://datatracker.ietf.org/doc/draft-filsfilscheng-spring-srv6-srh-compression/
>
> Hi Francois,
>
> thank you for the clarification. It is still not clear how a node selects
> which flavor of CSID to use on the next compressed CSID that may happen
> also be in the next CSID container. As I understand it, a CSID container
> must use the same flavor of compression but CSID containers with different
> compression flavors in the same SRH are allowed. Is that correct
> understanding?
>
>
>
> Regards,
>
> Greg
>
>
>
> On Wed, Oct 6, 2021 at 7:05 AM Francois Clad (fclad) <fclad@cisco.com>
> wrote:
>
> Hi Greg,
>
>
>
> A node that supports this draft in its entirety can instantiate SRv6 SIDs
> (e.g., End and End.X SIDs) with any of the three C-SID flavors.
>
>
>
> In particular, a node can instantiate multiple SRv6 SIDs bound to
> different C-SID flavors, possibly with different C-SID lengths. It can also
> instantiate SRv6 SIDs with behaviors and flavors defined in RFC 8986.
>
>
>
> As defined in Section 4.3 of RFC 8754 and again in Section 3 of RFC 8986,
> upon receiving an IPv6 packet with a destination address matching a FIB
> entry that represents one of these locally instantiated SIDs, the node
> processes the packet according to the behavior (and flavor(s)) (i.e.
> pseudocode) of that SID.
>
>
>
> RFC 8754 and 8986 have already standardized these mechanisms and the C-SID
> draft only leverages the same SRv6 dataplane to introduce new endpoint
> flavors for compression.
>
>
>
>
>
> Francois
>
>
>
> *From: *spring <spring-bounces@ietf.org> on behalf of Greg Mirsky <
> gregimirsky@gmail.com>
> *Date: *Tuesday, 5 October 2021 at 23:37
> *To: *Robert Raszuk <robert@raszuk.net>
> *Cc: *Ron Bonica <rbonica=40juniper.net@dmarc.ietf.org>, James Guichard <
> james.n.guichard@futurewei.com>, SPRING WG <spring@ietf.org>,
> spring-chairs@ietf.org <spring-chairs@ietf.org>
> *Subject: *Re: [spring] WG Adoption call for
> https://datatracker.ietf.org/doc/draft-filsfilscheng-spring-srv6-srh-compression/
>
> Hi Robert,
>
> as I understand it, you believe everything that is written in the draft. I
> hope you can help me find an answer to one simple question:
>
> Can a node that supports this draft in its entirety, i.e., supports all
> "flavors" defined in the document, process received SRv6 packet with the
> SRH encoded according to the specification?
>
> So far, the proponents of the draft referred to "planning" how flavors of
> SRv6 SID compressed. To the best of my understanding, that is is a clear
> demonstration of the incompatibility between flavors defined in the CSID
> draft. Regardless of what is written in it.
>
>
>
> Regards,
>
> Greg
>
>
>
> On Tue, Oct 5, 2021 at 1:24 PM Robert Raszuk <robert@raszuk.net> wrote:
>
> Ron & SPRING WG chairs,
>
>
>
> Through this discussion we first have seen a debate if we need one or more
> data planes to compress SIDs in SRv6. WG clearly stated we need one.
>
>
>
> Following that we have observed a first terminology shift to see if asking
> how many solutions should be supported will work any better. To that many
> WG members clearly stated that they support one solution.
>
>
>
> Well please notice that the draft in question in its introduction states:
>
>
>
> Abstract
>
>    This document defines a compressed SRv6 Segment List Encoding in the
>    Segment Routing Header (SRH).  *This solution* does not require any SRH
>    data plane change nor any SRv6 control plane change.  *This solution*
>    leverages the SRv6 Network Programming model.
>
>
>
> So based on my understanding of English the entire draft talks about a
> single solution.
>
>
>
> Then suddenly a new question popped up: how many behaviours are
> acceptable.
>
>
>
> I bet number of folks including myself said "one" keeping in mind previous
> discussions and the definition of "one" meaning based on the SRv6 data
> plane in compliance to [RFC8402], [RFC8754] and [RFC8986].
>
>
>
> Interestingly enough the draft in question defines not behaviours but
> flavors as new variants of the already defined behaviors in Standards Track
> RFCs. Namely it defines:
>
>
>
> 4.1.  NEXT-C-SID Flavor
>
> 4.2.  REPLACE-C-SID Flavor
>
>
>
> The newly defined behaviour End.XPS is optional.
>
> So if there is anything to ask here is to check if WG is ok with two
> flavors or not. I do not recall that question has ever been asked formally
> during the WG adoption call.
>
>
>
> With that let's note that optimal compressed SID size may be different
> network to network. One size does not fit all. Draft says:
>
> 6.1.  C-SID Length
>
>    The NEXT-C-SID flavor supports both 16- and 32-bit C-SID lengths.  A
> *   C-SID length of 16-bit is recommended.*
>
>    The REPLACE-C-SID flavor supports both 16- and 32-bit C-SID lengths.
> *   A C-SID length of 32-bit is recommended.*
>
>
>
> While I personally think 8-bit should be an option, if we choose a single
> flavor we will introduce suboptimality for no good reason. Hardware
> capable of supporting any flavor clearly can do LPM on locator. Also
> hardware capable of supporting one flavor can support few other flavors as
> this is pretty much just an offset game.
>
>
>
> Kind regards,
>
> Robert
>
>
>
>
>
>
>
> On Tue, Oct 5, 2021 at 9:43 PM Ron Bonica <rbonica=
> 40juniper.net@dmarc.ietf.org> wrote:
>
> Pablo,
>
>
>
> Ae you sure? Please look at the question as Joel asked it (
> https://mailarchive.ietf.org/arch/msg/spring/nS2gnQ_jxvpbmcxs_d3JAbUCT1I/
> ).
>
>
>
>
> Ron
>
> _______________________________________________
> spring mailing list
> spring@ietf.org
> https://www.ietf.org/mailman/listinfo/spring
>
>