Re: [spring] SRv6 compression

"Voyer, Daniel" <> Fri, 30 July 2021 21:06 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 4F4E93A10B5 for <>; Fri, 30 Jul 2021 14:06:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.087
X-Spam-Status: No, score=-2.087 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_REMOTE_IMAGE=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 IIaLloy7Npf2 for <>; Fri, 30 Jul 2021 14:06:21 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 4FC6D3A10C1 for <>; Fri, 30 Jul 2021 14:06:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;;; q=dns/txt; s=ESAcorp; t=1627679180; x=1659215180; h=from:to:cc:date:message-id:references:in-reply-to: mime-version:subject; bh=hR6iHx6bdFgHfg3A+Ue9D2N2yJ/SnMvhCPxKjE1ECIY=; b=V9isV/CH/dlPPsuRLh3F2j8PSH5evwf9zlJYPhykOmHu0hXjBN/M3pOj Vn8rhhSGPI2YVlhBQMITCjzXI90KaNH2OWlUuznejb1eAmHJ/vgcLRhKA fPHdzzp2LdZqmZi93zBipHcs9KkgpCJ5Bc5csDJWdOfTt9ht+TgZzj8hK 6nBBLBOYaxTviEdmJ0nWVceyLrdeWfgJzQqdDPU5lr/jf+iPvXI0GQ4x5 mjGGNmKJRzY0+HgA3PFAHST0Bf2yNNJ2/Tha0at0JECv7KfUHh8Zm9z9k ePilJh2ApZYA6DXRm+ChsEVyq3bBZeILz5LHYYj0b0M9OmE4g6C59zf0a w==;
IronPort-SDR: o6fubnDisp4STmAZv4Dr9axMDvZeA2Exk5jG9Wk0kvc/p+yTa8H7EzmQnkWiwp2UcGqzkIQ8rW B9XEpQvqyJXw==
Received: from (HELO ([]) by with ESMTP; 30 Jul 2021 17:06:18 -0400
Received: from (2002:8eb6:120e::8eb6:120e) by (2002:8eb6:120e::8eb6:120e) with Microsoft SMTP Server (TLS) id 15.0.1497.18; Fri, 30 Jul 2021 17:06:18 -0400
Received: from ([fe80::8d9b:1c8a:173a:e6d1]) by ([fe80::8d9b:1c8a:173a:e6d1%22]) with mapi id 15.00.1497.018; Fri, 30 Jul 2021 17:06:18 -0400
From: "Voyer, Daniel" <>
To: Eduard Metz <>, Gyan Mishra <>
CC: "Rabadan, Jorge (Nokia - US/Mountain View)" <>, "Aissaoui, Mustapha (Nokia - CA/Ottawa)" <>, "" <>, "Henderickx, Wim (Nokia - BE/Antwerp)" <>
Thread-Topic: [EXT]Re: [spring] SRv6 compression
Thread-Index: AQHXgwHU0Hp+yv4aEUubL5bWtM/A56tbp+sAgABfiQA=
Date: Fri, 30 Jul 2021 21:06:18 +0000
Message-ID: <>
References: <> <> <> <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/16.51.21071101
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_861DFD9744DD439FA36704E0653E4847bellca_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <>
Subject: Re: [spring] SRv6 compression
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: Fri, 30 Jul 2021 21:06:26 -0000

I agree as well – DT spent a year to come up with an analysis and now have a conclusion. In my view, we are ready to move with a single standard solution. This will unlock the vendors community to adopt an SRv6 compression standard and allow operators to move forward.

At the end of the analysis document, CSID seems to be the clear winner.


From: spring <> on behalf of Eduard Metz <>
Date: Friday, July 30, 2021 at 7:24 AM
To: Gyan Mishra <>
Cc: "Rabadan, Jorge (Nokia - US/Mountain View)" <>om>, "Aissaoui, Mustapha (Nokia - CA/Ottawa)" <>om>, "" <>rg>, Wim Henderickx <>
Subject: [EXT]Re: [spring] SRv6 compression

The DT has done a great job in the analysis.

Moving forward with a single, standards track solution is preferred/required for interoperable SRv6 implementations.


On Tue, Jul 27, 2021 at 6:09 PM Gyan Mishra <<>> wrote:

For all operators around the world looking at deployment of SRv6 compression and being in a  holding pattern waiting for SRv6 compression to be standardized by the IETF.

Given the ubiquitous importance of SRV6 compression and MSD issues with long strict SR-TE explicit route object,  it is critical for interoperability for all steering use cases that exist today: enterprise, internet, private, access network - 5G wireless xHaul, mobile core, wireline, MBB, FBB.

We as a WG need a single standardized solution for SRv6 compression for interoperability to work and all vendors marching to the same sheet of music.

I agree that the NVO3 - GENEVE is a solid precedence path forward to take and for Spring WG to come to consensus and standardize on one solution and progress the other solutions as informational if implementations already exist.

Kind Regards

Verizon Inc

On Tue, Jul 27, 2021 at 10:12 AM Aissaoui, Mustapha (Nokia - CA/Ottawa) <<>> wrote:
Same here. We want a single standard method of SID compression to allow the WG to focus on finalizing it and get vendors hardware implementations updated.


From: spring <<>> On Behalf Of Rabadan, Jorge (Nokia - US/Mountain View)
Sent: Tuesday, July 27, 2021 4:54 AM
To: Henderickx, Wim (Nokia - BE/Antwerp) <<>>;<>
Subject: Re: [spring] SRv6 compression

I agree with Wim’s statement that the precedent in NVO3 *could* apply here too: pick one solution as Standard’s track RFC, and once it is done, the others might be documented as Informational RFCs if they have implementations.

That would help the industry to move forward.


From: spring <<>> on behalf of Henderickx, Wim (Nokia - BE/Antwerp) <<>>
Date: Tuesday, July 27, 2021 at 9:11 AM
To:<> <<>>
Subject: [spring] SRv6 compression
Given the design team accomplished the work on providing requirements and analysis to compress an SRv6 SID list, I would recommend we pick 1 solution similar to what was done in NVO3 (when we discussed GENEVE, GUE, GPE, etc) given this has to be implemented in HW..

I hope we can conclude on this asap and move forward on this topic

spring mailing list<>


Gyan Mishra

Network Solutions Architect


M 301 502-1347

spring mailing list<>