Re: [spring] WG Adoption call - draft-srcompdt-spring-compression-requirement - draft-srcompdt-spring-compression-analysis

Dhruv Dhody <dhruv.ietf@gmail.com> Thu, 23 September 2021 05:47 UTC

Return-Path: <dhruv.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 17FC33A1641 for <spring@ietfa.amsl.com>; Wed, 22 Sep 2021 22:47:58 -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 VfO_J_TaEOPZ for <spring@ietfa.amsl.com>; Wed, 22 Sep 2021 22:47:52 -0700 (PDT)
Received: from mail-il1-x132.google.com (mail-il1-x132.google.com [IPv6:2607:f8b0:4864:20::132]) (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 4E47F3A2172 for <spring@ietf.org>; Wed, 22 Sep 2021 22:47:52 -0700 (PDT)
Received: by mail-il1-x132.google.com with SMTP id q14so5433616ils.5 for <spring@ietf.org>; Wed, 22 Sep 2021 22:47:52 -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=3KY+aElALZoYnc0HQ0YHb9dq9cUGvWxvE7ZLOYI4anE=; b=a970OMs9mj3uHAfobXwvtVzwBiclgLaztGQxYlTzAyvlqrcEmzIA99IEN145czNFjp HYkkT7C1amEDiPyw1XmFVs8tJ/T55V0MV7dTUAowGO2yJaJ5Yr/57eIz2juHQk1+VPT1 BdqW9rnwCkiamOZZTJ1fxsByxTOiQKPwS4WJDig2+OKU8wdMSg0nXeWY7hG1bbBbce+e g5T6w1p16Yth+fNEthvIiaEU4aTJXfNUtVVfpelFvQcdSs9y2Y3x3CJUGZUrlyjRngdi SIozmkoy2hhv6+UvWmmLy15xdhK1Dqjipb3wmkC/RCSZzlNDWscv16GX3I+3yvymh/OF LHmg==
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=3KY+aElALZoYnc0HQ0YHb9dq9cUGvWxvE7ZLOYI4anE=; b=1TON/PhFGF4TKVmJHQod7D01flnXb5TOakP7zQD5gFgu+1kro+U5/5i0bIuyGyMT7y vCkCqio8LaSZJRUxsQZRHsb4Mten7EtOu6bdl3ovEQRMmlwidIvO51sOPikAKIHIx0I6 udlZQFd9zUCpchKJ25qwH2yc9I5tepyiJGD5hITBccv3B53EFcmx319oyawUnXLoH4vU z/iD7vJGnju3XwxtYLJYFiu8Xc5SDkzyqVbJ7H6g8VZnwE5bSajtS1q7DITZIrYCJhcJ RaI1GRmdVyVKdd1mIeqoL4soxunOIup2biQNFVveeyzLrhdBxXHFfwxEg6vynOrn9jlP ZC0Q==
X-Gm-Message-State: AOAM531+P8n0JfIbXM39WdtUfSp5u45CSQwGIEO9FrydV5eQOtM0lOON lQS9rJ8lz5oPcHR0iAPJzmwYpomrLEIV3xh2w2Y=
X-Google-Smtp-Source: ABdhPJw+qAjH2IWpogc66BDgPq4cMMhO7GvnNMNN4kXw8m4fSmS1/tiQqfTElSsyBZ6imjTgKfp1qGxWQUiXlIAiax8=
X-Received: by 2002:a05:6e02:1d06:: with SMTP id i6mr2091060ila.299.1632376070419; Wed, 22 Sep 2021 22:47:50 -0700 (PDT)
MIME-Version: 1.0
References: <15436_1631020356_61376544_15436_364_1_53C29892C857584299CBF5D05346208A4CE99E43@OPEXCAUBM43.corporate.adroot.infra.ftgroup> <CAB75xn7RFyBm7Z_Lhc7=fm8yFH+_Ha_E2YYVLUUa-evxaz=zgQ@mail.gmail.com> <BYAPR05MB5318BD1C7D44801FE2A022DCAEA29@BYAPR05MB5318.namprd05.prod.outlook.com>
In-Reply-To: <BYAPR05MB5318BD1C7D44801FE2A022DCAEA29@BYAPR05MB5318.namprd05.prod.outlook.com>
From: Dhruv Dhody <dhruv.ietf@gmail.com>
Date: Thu, 23 Sep 2021 11:17:13 +0530
Message-ID: <CAB75xn69SE70=bHcVjbJb8zg8rzi2QxwcDf1vtRVL0oX-bArWg@mail.gmail.com>
To: Ron Bonica <rbonica@juniper.net>
Cc: "bruno.decraene@orange.com" <bruno.decraene@orange.com>, "spring@ietf.org" <spring@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000d1396405cca32b06"
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/g7sxkW8FcSGH_wetByZh4BzrYBU>
Subject: Re: [spring] WG Adoption call - draft-srcompdt-spring-compression-requirement - draft-srcompdt-spring-compression-analysis
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, 23 Sep 2021 05:47:59 -0000

Thanks Ron! It does!

On Thu, Sep 23, 2021 at 2:25 AM Ron Bonica <rbonica@juniper.net> wrote:

> Dhruv,
>
>
>
> Thanks for you review and support.
>
>
>
> Does the change below (inline) address your first comment?
>
>
>
>                                                    Ron
>
>
>
>
>
> Juniper Business Use Only
>
> *From:* spring <spring-bounces@ietf.org> *On Behalf Of *Dhruv Dhody
> *Sent:* Monday, September 20, 2021 12:56 PM
> *To:* bruno.decraene@orange.com
> *Cc:* spring@ietf.org
> *Subject:* Re: [spring] WG Adoption call -
> draft-srcompdt-spring-compression-requirement -
> draft-srcompdt-spring-compression-analysis
>
>
>
> *[External Email. Be cautious of content]*
>
>
>
> Hi,
>
>
>
> I support the adoption of both documents.
>
>
>
> Thanks for all the effort put in by everyone involved. Few minor comments
> -
>
>
>
> *draft-srcompdt-spring-compression-requirement-07*
>
>
>
> In section 1
>
> It is a goal of the design team to identify solutions to…
> It is also a goal of the design team to consider proposals…
> The design team will produce a separate document…
>
> Should we still need to mention the design team in the introduction? If
> some history needs to be maintained, let's put that in the appendix!
>
> [RB]
>
> OLD>
>
> The SPRING working group defined SRv6, with [RFC8402] describing how the
> Segment Routing (SR) architecture is instantiated on two data-planes: SR
> over MPLS (SR-MPLS) and SR over IPv6 (SRv6).  SRv6 uses a routing header
> called the SR Header (SRH) [RFC8754] and defines SRv6
>
> SID behaviors and a registry for identifying them in [RFC8986].  SRv6 is a
> proposed standard and is deployed today.
>
> The SPRING working group has observed that some use cases, such as strict
> path TE, may require long SRv6 SID lists.  There are several proposed
> methods to reduce the resulting SRv6 encapsulation size by compressing the
> SID list.
>
> The SPRING working group formed a design team to define requirements for,
> and analyze proposals to, compress SRv6 SID lists.
>
> It is a goal of the design team to identify solutions to SRv6 SID list
> compression that are based on the SRv6 standards.  As such, this document
> provides requirements for SRv6 SID list compression solutions that utilize
> the existing SRv6 data plane and control plane.
>
> It is also a goal of the design team to consider proposals that are not
> based on the SRv6 data plane and control plane.  As such, this document
> includes requirements to evaluate whether a compression proposal provides
> all the functionality of SRv6 (section "SRv6 Functionality") in addition to
> satisfying compression specific requirements.
>
> For each requirement, a description, rationale and metrics are described.
>
> The design team will produce a separate document to analyze the proposals.
>
> This document is a draft; additional requirements are under review,
> additional requirements will be added, and current requirements may
> change.  Appendix A contains a subset of requirements without unanimous
> consensus.  Additional requirements without unanimous consensus are not in
> the appendix.
>
> <OLD
>
> NEW>
>
> The Segment Routing (SR) architecture [RFC 8402] can be instantiated on
> two data-planes: SR over MPLS (SR-MPLS) and SR over IPv6 (SRv6).  SRv6 uses
> a routing header called the SR Header (SRH) [RFC8754] and defines SRv6 SID
> behaviors and a registry for identifying them in [RFC8986].  SRv6 is a
> proposed standard and is deployed today.
>
> Some use cases, such as strict path TE, may require long SRv6 SID lists.
> There are several proposed methods to reduce the resulting SRv6
> encapsulation size by compressing the SID list.
>
> This document defines requirements for a SID list compression mechanism.
> For each requirement, a description, rationale and metrics are provided.
>
> A companion document [draft-srcompdt-spring-compression-analysis]
> evaluates several compression mechanisms according to compliance with the
> requirements described by this document.
>
> <NEW
>
> [RB]
>
>
>
>