Hi WG,
I guess it is still 7th in some part of the earth and hoping I am not
too late :)
I find it weird that the SRv6 Yang
[https://tools.ietf.org/html/draft-raza-spring-srv6-yang-05] does not
use/augment ietf-segment-routing or ietf-segment-routing-common. A
sync up between these modules will b
Hi minhong:
Question 1: draft-hu-rtgwg-srv6-egress-protection-08 compliance
draft-ietf-spring-srv6-network-programming，It use H.Encaps Encapsulating the
Repair List。
Question 2: Only if SL == 0 or No SRH, It will execut the mirror behavior。If
the End Sid is the last sid,It will mirror behavior。O
Team organization and operation is up to the team.
In the abstract, having an archive would be good, but if you feel it
will interfere with the work, then so be it.
We can ask the ADs for support if you want an archived email list.
Yours,
Joel
PS: Sorry about the typo on your name.
On 7/7/202
Thanks Rishabh!
+1 to the above comments and looking forward to the updated draft.
Cheers,
Jeff
On Jul 7, 2020, 7:35 AM -0700, Alexander Vainshtein
, wrote:
> Dhruv, Bruno and all,
> Regarding the statement " What is missing in the spring I-D is some very high
> level discussion in terms of arch
Hi Joel,
On 07-07-2020 18:24, Joel Halpern wrote:
> The Design team will be
> Co-Chaired by:
> Cheng Weiqiang of China Mobile and
> Sanders Steffann of SJM Steffann Consultancy
Minor typo in my first name (Sander) but no harm done :)
> The other members of the team are:
> Ron Bonica
Hi Parag,
Yes, it can be the last SID. When SL=0 you ignore the SRH and process the next
header in the header chain. Upper-layer header processing is defined in 4.1.1.
If you would like to remove the SRH with the End behavior you can use PSP, USP
or USD flavors to do so.
Regards,
Pablo.
From:
Having gotten various volunteers, and considered what the WG needs, the
SPRING chairs have selected the design team for clarifying the SR over
IPv6 compression situation.
The Design team will be
Co-Chaired by:
Cheng Weiqiang of China Mobile and
Sanders Steffann of SJM Steffann Consultan
Sorry folks. This is the wrong version. I will resend in a moment.
The important error is that it has the wrong affiliation for Cheng
Weiqiang, for which I sincerely apologize.
Yours,
Joel
On 7/7/2020 12:20 PM, Joel Halpern wrote:
Having gotten various volunteers, and considered what the WG
Having gotten various volunteers, and considered what the WG needs, the
SPRING chairs have selected the design team for clarifying the SR over
IPv6 compression situation.
The Design team will be
Co-Chaired by:
Cheng Weiqiang of China Telecom and
Sanders Steffann of SJM Steffann Consulta
>> Reading the I-D and based on the discussion on this thread I believe
>> more description is required. As Joel pointed out, clarity on what is
>> legal/illegal (or out of scope for now) is needed.
>I leave this for the authors to reply.
We are working onthe next revision of the draft that will
Dhruv, Bruno and all,
Regarding the statement " What is missing in the spring I-D is some very high
level discussion in terms of architecture on how replication segment and SR
P2MP policy come together" - I cannot agree more.
My 2c,
Sasha
Office: +972-39266302
Cell: +972-549266302
Email:
Hi Bruno,
Yes, thanks! I was just making sure that we have an agreement that PIM
is the right place to define SR P2MP Policy.
What is missing in the spring I-D is some very high level discussion
in terms of architecture on how replication segment and SR P2MP policy
come together. The current I-D
Hi Dhruv,
> -Original Message-
> From: spring [mailto:spring-boun...@ietf.org] On Behalf Of Dhruv Dhody
> Subject: Re: [spring] Understanding the replication draft
>
> Hi WG,
>
> Reading the I-D and based on the discussion on this thread I believe
> more description is required. As Joel
13 matches
Mail list logo
