> SIDs need to be arranged together at the header end for interoperability to
> be achieved.
>
>
>
> Thanks,
>
> Changwang
>
>
>
>
>
> *From:* Andrew Alston - IETF [mailto:andrew-i...@liquid.tech]
> *Sent:* Friday, August 04, 2023 10:28 AM
> *To
:n...@foobar.org>>
Date: Wednesday, August 9, 2023 at 5:43 AM
To: Zafar Ali (zali) mailto:z...@cisco.com>>
Cc: Joel Halpern mailto:j...@joelhalpern.com>>, SPRING WG
List mailto:spring@ietf.org>>
Subject: Re: [spring] Issue 1 regarding draft-ietf-spring-srv6-srh-compression
Za
; flavor or the replace flavor or both. Emails from Changwang Lin and Darren
> Dukes on this tread provides further explanation. I hope that clarifies
> your query.
>
>
>
> Thanks
>
>
>
> Regards … Zafar
>
>
>
> *From: *Nick Hilliard
> *Date: *Wednesda
Hello WG,
I believe that the issue 1, 2, 3 and 4 have been resolved.
Thanks,
Gurminder
--
Thanks,
Gurminder
___
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring
to compress SID list using the next
> flavor or the replace flavor or both. Emails from Changwang Lin and Darren
> Dukes on this tread provides further explanation. I hope that clarifies
> your query.
>
>
>
> Thanks
>
>
>
> Regards … Zafar
>
>
>
> *From:
I agree this issue #1 can be closed.
All SIDs both next SID uSID and replace SID GSID can Co-exist in the same
SRH as single data plane solution.
Thank you
Gyan
On Mon, Jul 31, 2023 at 5:08 PM Joel Halpern wrote:
> As per the discussions on list and at IETF 117, the SPRING WG chairs
> (mysel
Hi Joel and WG,
The resolution is satisfactory to close issue #1.
Brgds
Amit D
Rakuten
From: Joel Halpern
Date: Tuesday, 1 August 2023 at 2:38 AM
To: SPRING WG List
Subject: [spring] Issue 1 regarding draft-ietf-spring-srv6-srh-compression
As per the discussions on list and at IETF 117, the SP
Hi, yes I agree to close this issue.
Dan
From: spring on behalf of Joel Halpern
Date: Monday, July 31, 2023 at 5:08 PM
To: SPRING WG List
Subject: [EXT][spring] Issue 1 regarding draft-ietf-spring-srv6-srh-compression
As per the discussions on list and at IETF 117, the SPRING WG chairs (mys
Hi Joel and team,
We agree that issue#1 can be closed.
Different SID types coexist in the same SRH: implemented and aligned with
the Broadcom Jericho line implementation.
Best Regards,
Shay
On Tue, Aug 22, 2023 at 11:26 AM Satoru Matsushima <
satoru.matsush...@gmail.com> wrote:
> This issue was
This issue was resolved and I agree to close issue#1.
Best regards,
--satoru
On Tue, Aug 1, 2023 at 6:08 AM Joel Halpern wrote:
> As per the discussions on list and at IETF 117, the SPRING WG chairs
> (myself and Alvaro specifically) are attempting to determine if we can
> close the open issue
Dear WG,
in my eyes this resolves the issue good enough.
Best regards, Martin
Von: spring im Auftrag von Joel Halpern
Datum: Montag, 31. Juli 2023 um 23:10
An: SPRING WG List
Betreff: [spring] Issue 1 regarding draft-ietf-spring-srv6-srh-compression
As per the discussions on list and at IET
We think the issue is resolved.
Jiang Liu Professor
Beijing University of Posts and Telecommunications
School of Information and Communication Engineering
State Key Laboratory of networking and switching technology,
No.10 Xitucheng Road, Haidian District, Beijing, China
Tel: +86-13810517330
Hi WG,
I consider the issue 1 closable.
I think the multiple SRv6 Endpoint behaviors belong to a single data plane
solution just like I have seen in RFC8986.
Thanks,
Jingrong
本邮件及其附件可能含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！
Th
ust 9, 2023 at 5:43 AM
To: Zafar Ali (zali) mailto:z...@cisco.com>>
Cc: Joel Halpern mailto:j...@joelhalpern.com>>, SPRING WG
List mailto:spring@ietf.org>>
Subject: Re: [spring] Issue 1 regarding draft-ietf-spring-srv6-srh-compression
Zafar,
can you confirm that if Router A in one
t;
> Regards … Zafar
>
>
>
> *From: *Nick Hilliard
> *Date: *Wednesday, August 9, 2023 at 5:43 AM
> *To: *Zafar Ali (zali)
> *Cc: *Joel Halpern , SPRING WG List
> *Subject: *Re: [spring] Issue 1 regarding
> draft-ietf-spring-srv6-srh-compression
>
> Zafa
clarifies your
query.
Thanks
Regards … Zafar
From: Nick Hilliard
Date: Wednesday, August 9, 2023 at 5:43 AM
To: Zafar Ali (zali)
Cc: Joel Halpern , SPRING WG List
Subject: Re: [spring] Issue 1 regarding draft-ietf-spring-srv6-srh-compression
Zafar,
can you confirm that if Router A in one
Hi Darren,
I agree that in the current form, the authors asserted that proposed C-SID
mechanisms are parts of the single data plane. But, as I've noted earlier,
that the resolution should come as a conclusion, not an assertion. I hope
that the authors will share text that would illustrate in detail
Hello Joel and WG chairs. I’m in agreement with the authors/editors assertion
that we have a single data plane and we can close this issue.
The document defines two new flavors of SID and applies them to existing
behaviors. The resultant behaviors are implemented only on the device deploying
th
Many thanks for Joel for handling the work. After reading all the resolutions,
I agree to close them all. Thanks to Authors for their excellent work！ PS. in
order to avoid sending a lots of emails, I share my POV in this email to close
issue 1,3,4 and 5.
Zhibo
From: spring [mailto:spring-boun..
Zafar,
can you confirm that if Router A in one domain uses next-c-sid and
Router B in another domain uses replace-c-sid, that they will be able to
interoperate? I'm not picking this up from the draft, and this would be
the overriding operational consideration in terms of what a single data
p
Dear WG chairs and the WG,
I agree that this resolves the issue 1; it is a single data plane solution
compliant with the specifications in [RFC8402], [RFC8754] and [RFC8986], aka
SRv6 data plane.
Thanks
Regards … Zafar
From: spring on behalf of Joel Halpern
Date: Monday, July 31, 2023 at 5
So folks don't get confused, later today I will be issueing calls to
confirm the editor's conclusions on issues #3, #4, and #5. Those will
run for 2 weeks. The call for issue #1 continues, and the call for
issue #2 will be issued next week.
Yours,
Joel
__
Hi Joel,
I agree with the editors’ resolution for issue 1. "All SIDs of the SRv6
dataplane can co-exist in the same SRH. This make SRv6 a single, consistent
dataplane solution". It is indeed so.
I think we can close it.
Best regards,
Yuanxiang
From: spring On Behalf Of Joel Halpern
Sent:
racteristics of different networking scenarios.
Thanks,
Changwang
From: Andrew Alston - IETF [mailto:andrew-i...@liquid.tech]
Sent: Friday, August 04, 2023 8:22 PM
To: linchangwang (RD); Joel Halpern; SPRING WG List
Subject: Re: [spring] Issue 1 regarding draft-ietf-spring-srv6-srh-compression
Now,
Let
Hi Joel,
The authors’ resolution of issue 1 looks good to me, and I’d consider issue 1
as closed.
This document is currently in a stable and good shape to move forward. Thanks
for all the good work of the editors, authors and WG chairs.
Best regards,
Jie
From: spring On Behalf Of Joel Halper
, 4 August 2023 at 08:24
To: Andrew Alston - IETF , Joel Halpern
, SPRING WG List
Subject: RE: [spring] Issue 1 regarding draft-ietf-spring-srv6-srh-compression
Hi Andrew,WG,
Let me add my understanding of interoperability.
If all devices support NEXT-C-SID, the encapsulation is as follows
Hi Joel, WG,
I wanted to share my perspective on the issue at hand. I am in agreement that
the issue has been satisfactorily resolved. The document
"draft-ietf-spring-srv6-srh-compression" clearly defines that all SIDs,
including Next-C-SID and Replace-C-SID, can co-exist in the same SRH. This
In my opinion the suggested approach is the most reasonable approach
at this point, and therefore the issue can be closed.
Cheers,
Tal.
On Tue, Aug 1, 2023 at 12:08 AM Joel Halpern wrote:
>
> As per the discussions on list and at IETF 117, the SPRING WG chairs (myself
> and Alvaro specifically)
Joel Halpern mailto:j...@joelhalpern.com>>, SPRING WG
List mailto:spring@ietf.org>>
Subject: Re: [spring] Issue 1 regarding draft-ietf-spring-srv6-srh-compression
Hi Joel, WG,
I agree that the issue has been resolved.
According to the SRv6 dataplane definition in the document
&qu
I think we can close issue 1.
I agree the editors said that "All SIDs of the SRv6 dataplane can co-exist in
the same SRH. This make SRv6 a single, consistent dataplane solution". There
were some interop tests in the document.
Regards,
Aihua Liu
Original
From: JoelHalpern
I think we can close the issue 1, and I think it can be closed long time ago in
the WG adoption not now.
Like the authors and contributors said, “All SIDs of the SRv6 dataplane
(defined in this document and in other documents) can co-exist in the same SRH.
This make SRv6 a single, consistent da
achieved.
Thanks,
Changwang
From: Andrew Alston - IETF [mailto:andrew-i...@liquid.tech]
Sent: Friday, August 04, 2023 10:28 AM
To: linchangwang (RD); Joel Halpern; SPRING WG List
Subject: Re: [spring] Issue 1 regarding draft-ietf-spring-srv6-srh-compression
Hi Joel, WG
Speaking strictly as a
consider this issue closed �C and I really fail to see how these can be
considered one solution.
Andrew
Internal All Employees
From: spring on behalf of linchangwang
Date: Tuesday, 1 August 2023 at 03:46
To: Joel Halpern , SPRING WG List
Subject: Re: [spring] Issue 1 regarding draft-ietf
Hi Joel, WG,
I agree that the issue has been resolved.
According to the SRv6 dataplane definition in the document
"draft-ietf-spring-srv6-srh-compression,"all SIDs can co-exist in the same SRH,
including Next-C-SID and Replace-C-SID.
This allows for SRv6 to be a single and consistent datapla
Hi, Joel, Authors, et al.,
I have a clarification question and appreciate your help answering it.
According to RFC 8986:
SRv6 Endpoint behavior: A packet processing behavior executed at an SRv6
Segment Endpoint Node.
As I understand it, two compression techniques, NEXT-C-SID and
REPLACE-C-SID, ar
35 matches
Mail list logo
