Ahmed,
That is a far cry from recommending anything.
* If you take a look at the first page of that slide deck, the DT was
tasked with enumeration and analysis of requirements. The word "recommend" does
not appear on that page.
* If you look at the third page of that slide deck, you will see that one
very important requirement (PS/BCP Compliance) was left for the relevant WGs to
determine.
* If you look under the chart, you will see a note that says "All
requirements are not equally important. The working group must decide which are
more significant." The WG needs to determine whether the requirements that
register a difference are significant.
Ron
Juniper Business Use Only
From: Ahmed Bashandy <[email protected]>
Sent: Wednesday, October 6, 2021 1:21 PM
To: Ron Bonica <[email protected]>; James Guichard
<[email protected]>; SPRING WG <[email protected]>
Cc: [email protected]
Subject: Re: [spring] WG Adoption call for
https://datatracker.ietf.org/doc/draft-filsfilscheng-spring-srv6-srh-compression/
[External Email. Be cautious of content]
If we take a look at the summary table in slide 17 in the DT presentation at
last IETF
https://datatracker.ietf.org/meeting/111/materials/slides-111-spring-srcomp-design-team-update-00<https://urldefense.com/v3/__https:/datatracker.ietf.org/meeting/111/materials/slides-111-spring-srcomp-design-team-update-00__;!!NEt6yMaO-gk!XRu-vlE4UU8DQXBtTSicMvItj5PBLG69P1RlwJSbtBR6lOLQtnSPeds1ommxXiJY$>
we can see that CSID is the only column with *all blocks dark green*.
Thanks
Ahmed
On 10/6/21 9:06 AM, Ron Bonica wrote:
Ahmed,
I don't recall the DT recommending the CSID. In fact, the word "recommend" does
not appear anywhere in the analysis document.
As a member of the DT, I don't recommend CSID.
Ron
Juniper Business Use Only
From: spring <[email protected]><mailto:[email protected]> On
Behalf Of Ahmed Bashandy
Sent: Tuesday, October 5, 2021 10:53 PM
To: James Guichard
<[email protected]><mailto:[email protected]>; SPRING
WG <[email protected]><mailto:[email protected]>
Cc: [email protected]<mailto:[email protected]>
Subject: Re: [spring] WG Adoption call for
https://datatracker.ietf.org/doc/draft-filsfilscheng-spring-srv6-srh-compression/<https://urldefense.com/v3/__https:/datatracker.ietf.org/doc/draft-filsfilscheng-spring-srv6-srh-compression/__;!!NEt6yMaO-gk!XRu-vlE4UU8DQXBtTSicMvItj5PBLG69P1RlwJSbtBR6lOLQtnSPeds1ovJ2hhnQ$>
[External Email. Be cautious of content]
I support the adoption of this document.
1. The network programming model (RFC8986) defines multiple behaviors, CSID
is just adding the next and replace flavors
2. The draft proposes a single SRv6 based data plane that defines next and
replace behaviors. IMO that is consistent with RFC8986
1. CSID has been recommended by the design team for SRv6 based compression
2. Interop was done. That is more evidence that CSID is a single data plane
solution
3. IMO CSID is ready to become the basis for the SRv6 compression solution
4. Being an SRv6 data plane-based solution, CSID is coherent with the one
data plane solution objective
5. CSID meets SRv6 compression requirements as single solution
Thanks
Ahmed
On 10/1/21 7:04 AM, James Guichard wrote:
Dear WG:
The chairs would like to express their appreciation for all the responses
received to our emails with reference to how the working group wishes to move
forward with respect to a solution for SRv6 compression.
The apparent inclination of the working group is to use
https://datatracker.ietf.org/doc/draft-filsfilscheng-spring-srv6-srh-compression/<https://urldefense.com/v3/__https:/datatracker.ietf.org/doc/draft-filsfilscheng-spring-srv6-srh-compression/__;!!NEt6yMaO-gk!UB-06E0vV1hJFKLsWYZym6F3d_lXgEa-0TT6vPXh5GKmmrA9UhFLCWIRgLQM66Td$>
as the basis for its compression standardization work. That is part of what
this email attempts to confirm.
Because of the above the chairs would like to issue a 2-week WG call for
adoption ending October 15th for
https://datatracker.ietf.org/doc/draft-filsfilscheng-spring-srv6-srh-compression/<https://urldefense.com/v3/__https:/datatracker.ietf.org/doc/draft-filsfilscheng-spring-srv6-srh-compression/__;!!NEt6yMaO-gk!UB-06E0vV1hJFKLsWYZym6F3d_lXgEa-0TT6vPXh5GKmmrA9UhFLCWIRgLQM66Td$>
but with some clear guidelines as follows. By expressing support for adoption
of this document you are fully aware of and are acknowledging that:
1. The SPRING working group is adopting a document that has multiple SRv6
Endpoint behaviors.
2. The document is a "living" document; it may change as it goes through
review and analysis by the SPRING working group.
3. All open discussion points raised on our mailing list MUST be addressed
BEFORE said document is allowed to progress from the working group to
publication. A list of these discussion points will be documented in the WG
document and maintained by the document editor in conjunction with the chairs.
4. If this document is adopted by the working group, the chairs specify as
part of the adoption call that the following text describing an open issue be
added to the document in the above-described open issues section:
* "Given that the working group has said that it wants to standardize
one data plane solution, and given that the document contains multiple SRv6
EndPoint behaviors that some WG members have stated are multiple data plane
solutions, the working group will address whether this is valid and coherent
with its one data plane solution objective.".
Please consider the above guidelines as you decide on whether to support or not
this WG adoption. Please express clearly your reasoning for support/non-support
as well as any open discussion points you would like addressed should the
document be adopted into the working group.
Thanks!
Jim, Bruno & Joel
_______________________________________________
spring mailing list
[email protected]<mailto:[email protected]>
https://www.ietf.org/mailman/listinfo/spring<https://urldefense.com/v3/__https:/www.ietf.org/mailman/listinfo/spring__;!!NEt6yMaO-gk!UB-06E0vV1hJFKLsWYZym6F3d_lXgEa-0TT6vPXh5GKmmrA9UhFLCWIRgDaeqmAm$>
_______________________________________________
spring mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/spring
