Re: [spring] Conclusion from WG poll on dataplane solution for compressing segment routing over IPv6

zhen han <> Sun, 12 September 2021 00:53 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id A60683A1A7D for <>; Sat, 11 Sep 2021 17:53:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.837
X-Spam-Status: No, score=-1.837 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_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id tW9TgIO4J2DN for <>; Sat, 11 Sep 2021 17:53:22 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:4864:20::b44]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 4C3033A1A74 for <>; Sat, 11 Sep 2021 17:53:22 -0700 (PDT)
Received: by with SMTP id a93so12377732ybi.1 for <>; Sat, 11 Sep 2021 17:53:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20210112; h=mime-version:from:date:message-id:subject:to; bh=IyM0RFXjjngjEb58noq9BlsayygJpHnNNw9uqIiQqhw=; b=eQsy3wEUGyIDXJhxm98AFdwHr4kLIA86jGyLtwP86rh6WYYHD0A4Z4RdwGcvJOyLvP REHemns2HGCdJ2FZ3dyCBngYOOpmXfpySk95+s5ru56Yg3ufktucWHFQg1YGRG3JttnJ omuMjnymjo+/g+vrCH1t2ZlY1adak4GWFyX8aatfJOmTp0X5L9gv74C589wJGlylE3NW WpqDrUsYgLb1P4MKRo94nGPvgwt8Z+FRmuPUye8beO4ObOHwpWOGDaPtstOqUUodDsqY KUjpML8GHpBnoRIJ9vlDbgn9lQFtFNBez43/3BgsO2UurPHPFIPXMRl2zT9LCIJwaA67 48RA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20210112; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=IyM0RFXjjngjEb58noq9BlsayygJpHnNNw9uqIiQqhw=; b=bOPECqBERZUkwk/LCfx8ouLV8owWYDvwRa/pMctAqJ4E0KoTP4C9SQrnp67h2MQ5bl rgtobiFwNW81fcOr7v77EDdJ5+p9vZ94rEbpR/QQRf01ENFbyxaaUTkB/V5qyX33AJA3 3RzHG/x2c9QF7wD2mSLzBBeuL9PsQypFoAgYmFTx44VMUC1Gj8XZMeXwHwZo7HL1cMRz KyBgNOkH0objDlaI7U2MJu/ipwWDVzF36zVQQ3rEdDNec9NaWsX7MDPAkOW18UxXfdwt Dj69RIR5zYp3+PDQVW2GEFs36KF2lN033TwiuHOj+tNgU/l5UzCnPM+3d0xnrI/zFy13 GK0Q==
X-Gm-Message-State: AOAM5326II2QsULR14R/w/m9LVHzse1ibey8UMJnW8d6gv/6JDeBVy9j /4zRhDjZI++rBFpxs+Dfmzie2QRt8CaVFFSDh6Vj9cGkdJs=
X-Google-Smtp-Source: ABdhPJxrCP3GvEQVHCpHCtXeRZ/9Nu4f90WNRhBrvCdlTP5zY6kvOPB6rpxix1XnlO9+nTrURw5cAIfcR8bgoIYsfK4=
X-Received: by 2002:a25:4786:: with SMTP id u128mr6495744yba.539.1631407999932; Sat, 11 Sep 2021 17:53:19 -0700 (PDT)
MIME-Version: 1.0
From: zhen han <>
Date: Sun, 12 Sep 2021 08:53:08 +0800
Message-ID: <>
To: 程伟强 <>, "Joel M. Halpern" <>, "" <>
Content-Type: multipart/alternative; boundary="00000000000051dd8205cbc1c666"
Archived-At: <>
Subject: Re: [spring] Conclusion from WG poll on dataplane solution for compressing segment routing over IPv6
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Source Packet Routing in NetworkinG \(SPRING\)" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Sun, 12 Sep 2021 00:53:28 -0000

Hi Chairs,

I fully agree with the CSID authors opinions below.

It is definitely not a easy topic as it take such a long time to get a
consensus version.
Thank the authors for their hard working!
I agree that 2 flavors are not equal to 2 dataplane,different flavors are
all based on the same SRv6 dataplane(one dateplane).
The current version could be called as one solution.

Considering the huge progress we have achieved,it seems 100% ready to step
forward ASAP.

Best Regards,
Zhen HAN (Fiberhome)

*发件人:* Weiqiang Cheng <>
*发送时间:* 2021-09-08 11:25
*收件人:* 'Joel M. Halpern' <>;
*主题:* Re: [spring] Conclusion from WG poll on dataplane solution for
compressing segment routing over IPv6
Dear Chairs,

Many thanks for your hard working.

We are happy to see that the CSID draft has significant interest to be
adopted as a WG document.

Regarding the dataplane, the authors believe that the CSID draft contains
only one dataplane solution with two different flavors[1]: NEXT-CSID-FLAVOR
and REPLACE-CSID-FLAVOR, rather than two dataplane solutions.

Both the flavors are defined based on the SRv6 data plane(one data plane),
and the SIDs with these two flavors can be encoded in a single SRH just like
we can encode PSP Flavor SIDs and USD flavor SIDs together in a SRH.

The inter-op test of CSIDs had been done almost one year ago[2], and
everything was OK.

Furthermore, the mechanism defined in the draft has been stable and mature.

With the consensus, the authors hope WG can consider to adopt the CSID

Best regards,
on behalf of CSID authors


发件人: spring [] 代表 Joel M. Halpern
发送时间: 2021年9月7日 01:27
主题: [spring] Conclusion from WG poll on dataplane solution for compressing
segment routing over IPv6

Our thanks to the working group members for speaking up clearly.  There
is a rough (quite clear) consensus for standardizing one dataplane
solution to compressing segment routing over IPv6.

As chairs, there are some related observations we need to make.
There appears to be significant interest in using the framework in the
CSID draft for addressing the above.

However, before we issue a call for adoption on that, the chairs would
like to understand how the working group wants to solve a technical
problem.  The CSID draft contains two dataplane solutions.  The above
rough consensus is for one dataplane solution.  Does the working group
want to choose one?  Do the authors want to suggest that one of the two
is the one we should standardize, and get working group agreement?
Should we adopt the document, with a note indicating the problem, and
solve the problem afterwards?  (That itself does not solve the problem,
it merely kicks it down the road.) Do folks see another means to avoid
putting the WG in conflict with itself?

As a loosely related side node, the chairs will also observe that we do
not see an obstacle to informational or experimental publication of
other solutions, as long as there is sufficient energy in the working
group to deal with those.  Also, only documents for which there is at
least one implementation will be progressed this way.

Thank you,
Bruno, Jim, and Joel

spring mailing list

spring mailing list