Folks,
Now that Robert and I have provided some entertainment, could someone answer
the technical question that initiated this thread?
Does the document recommend against using Next-C-SId and Replace-C-Sid in the
same domain for ease of operation or because they don’t work well together? If
the former, please provide the example described below.
Ron
Sent from my iPhone
On Oct 1, 2021, at 5:07 PM, Robert Raszuk <[email protected]> wrote:
[External Email. Be cautious of content]
Hi Ron,
* Can we say that they are a single behavior ?
No. And neither RFC8986 defines a single behavior or single flavor. Yet the
bounds are clearly set what is the SRv6 data plane.
For some strange reason I am observing here an attempt to squeeze different
data plane into the room which is not compliant to [RFC8402], [RFC8754] and
[RFC8986]. Do you think anyone will be so naive to accept it ?
Now I am going to rest assured and enjoy the rest of this show.
Best,
Robert
On Fri, Oct 1, 2021 at 10:58 PM Ron Bonica
<[email protected]<mailto:[email protected]>> wrote:
Robert,
I do remember that quote. And that is exactly why I ask the question!
If NEXT-C-SID and REPLACE-C-SID are incompatible within a domain:
* Can we say that they are a single behavior ?
* Can we justify both because each is optimized for a different kind of
network?
* Can we justify another behavior either because it is optimized for yet
another type of network or because it does relatively well in all network types?
However, if this is just an “ease of operation” thing, as stated in the draft,
the authors are obliged to answer my question.
Ron
P.S. Rest assured that I have read the draft. However, your concern is greatly
appreciated 😉
Juniper Business Use Only
From: Robert Raszuk <[email protected]<mailto:[email protected]>>
Sent: Friday, October 1, 2021 4:32 PM
To: Ron Bonica <[email protected]<mailto:[email protected]>>
Cc: SPRING WG <[email protected]<mailto:[email protected]>>
Subject: Re: [spring] CSID Question
[External Email. Be cautious of content]
Hi Ron,
Have you read this draft ?
Quote from it:
It is recommended for ease of operation that a single compressed
encoding flavor be used in a given SRv6 domain. However, in a multi-
domain deployment, different flavors can be used in different
domains.
On Fri, Oct 1, 2021 at 9:33 PM Ron Bonica
<[email protected]<mailto:[email protected]>>
wrote:
CSID Authors,
Assume that an SR path contains segments 1 through 8. Segments 1, 3, 5, and 7
are END SIDs that use Next-C-SID (i.e., uSID). Segments 2, 4, and 6 are END
SIDs that use Replace-C-SID. Segment 8 is and END.DX4 SID.
Please provide an example that shows us:
* What the SRH looks like as it arrives at the first segment endpoint
* What the IPv6 Destination Address looks like at each segment endpoint,
including information required to parse the Destination Address
Ron
Juniper Business Use Only
_______________________________________________
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!UL_LsTEWuybtewcIHX2FwrqtwS3G97ki3tzHT8pGyGcx2hPWYZfriSmeG75uwP7l$>
_______________________________________________
spring mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/spring
