Re: [spring] Per segment service instructions

[Tarek Saad <[e-mail]>]

Hi all,

A possible way to avoid domain wide scope of PSSI, would be to encode a per node ID within the PSSI (per node namespace of Service IDs).
This allows the node parsing the DOH to identify PSSI(s) that needs to be invoked locally and to resolve the Service ID within its node scope. The per node ID can be a SRV6+ short SID that is instantiated locally on the node.

So, a PSSI = Short-SID.SE1

DOH can contain:
Short-SID1.SE1
Short-SID2.SE2
Etc.

Regards,
Tarek



From: spring <[e-mail]> on behalf of "Bernier, Daniel" <[e-mail]>
Date: Saturday, September 14, 2019 at 1:03 AM
To: Ron Bonica <rbonica=[e-mail]>, Robert Raszuk <[e-mail]>
Cc: SPRING WG <[e-mail]>, 6man <[e-mail]>
Subject: Re: [spring] Per segment service instructions

Hi Ron,

If PSSI provide non-routing services such as SE1 from Robert’s example which offers DPI, FW and Packet Replication then, I need a domain-wide PSSI defining DPI + FW + Sampling but if somewhere else in my network I just need FW, then I need another domain-wide PSSI for only FW.
In that model, I will end up with and endless list of permutations which must be agreed upon to ensure interop (i.e. vendor A cannot use a PSSI X for FW while vendor B think’s its DPI).
Thx
Dan B



On 2019-09-13, 2:10 PM, "ipv6 on behalf of Ron Bonica" <[e-mail]<mailto:[e-mail]> on behalf of rbonica=[e-mail]<mailto:rbonica=[e-mail]>> wrote:

Robert,

In your email, you ask how I would solve a TE problem with a Per Segment Service Instruction (PSSI). In SRv6+:


-          The CRH and the SIDs that it contains are used to solve TE problems

-          The PSSI is used too provide non-routing services (e.g., firewalling, sampling, DPI)

This leaves the following questions to be answered:


-          How would I solve the TE problem that you describe in your email?

-          Given another example, explain how PSSI works?

Which question would you like me to tackle first?

                                                                    Ron


From: Robert Raszuk <[e-mail]>
Sent: Friday, September 13, 2019 8:45 AM
To: Ron Bonica <[e-mail]>
Cc: SPRING WG <[e-mail]>; 6man <[e-mail]>
Subject: Per segment service instructions

Dear Ron,

I have read yet one more draft from the SRv6+ package defining another Destination Option type - this time Per Segment Service Instruction(s) described in draft-bonica-6man-seg-end-opt

I have one technical question regarding it.

Imagine I have following topology - drawing only what is relevant to the question:

PE1 - - P1 - - SE1 - - P2 - -  SE2 - - P3 - - PE2

When packet enters the network PE1 is instructed to program my flow A to execute following following functions on Segment End 1 (SE1) and Segment End 2 (SE2):

SE1 - When packet is routed out of SE1 consider only interfaces of bw 10G and up

SE2 - When packet is routed out of SE2 make sure that path to segment end node is no more then 2 hops away.

>From reading the draft I think the answer is that you mandated the segment end functions in SRv6+ to have domain-wide significance such that the function itself contains not only the instruction but also as it is of domain-wide significance the location of the instruction to execute it on.

So far so good ... Flow-A get's CRH and PSSI encoding the above requirement.

When packet enters SE1 Destination Options preceding RH is read and PSSIs are attempted to get executed ! Both instructions are tried but only one is known so only one get's executed on SE1. Same story on SE2.

Not sure if eveyone would be ok with such model to read and attempt to execute instructions which are not for a given end segment but let's assume some may accept it.

But now how unfortunate it may sound PE1 is receving the flow-B and for flow B the requirements are opposite:

SE1 - When packet is routed out of SE1 make sure that path to segment end node is no more then 2 hops away.

SE2 - When packet is routed out of SE2 consider only interfaces of bw 10G and up.

Well what do you - simple - you allocate another two domain wide functions and encode it in the packet at PSSI DOH on PE1.

But if my description matches the plan you now end up with per flow !!! state in the network which is the price to pay for splitting SIDs with its functions into completely different headers.

I don't know about others but I think we went in the past via multiple attempts to put any per flow state into the large network and it all failed when faced scale.

Also SR specifically in its architecture RFC8402 says that segment routing is "maintaining per-flow state only at the ingress node(s) to the SR domain."

Kind regards,
Robert.



Juniper Business Use Only