Re: [spring] I-D Action: draft-ietf-spring-srv6-network-programming-10.txt

[Robert Raszuk <[e-mail]>]

Ron,

How about we go the other way and really admit that some hardware just can
not PSP at line rate ?

But for that there is very simple solution - you advertise PSP depth of
zero in IGP extensions and you are done.

Both ISIS and OSPFv3 extensions support this already today.

And as it has been said and illustrated it does not stretch RFC8200 at all.
PSP is performed by node listed in DA of the arriving packet. Such node can
do whatever it want with the outer header of the packet. Some folks try to
punch holes in 8200 to cover their issues - is that in good spirit of IETF
?

Your idea of taking piece of the consistent spec away is very broken as it
now makes other documents inconsistent and blocks hardware where such
function is supported today at line rate.

Let the operator choose if he wants PSP or not and move on ...

Best,
R.








On Thu, Feb 27, 2020 at 7:39 PM Ron Bonica <rbonica=
[e-mail]> wrote:

> Pablo,
>
>
>
> The question at hand is whether PSP is so crucial to SRv6 that it is worth
> stretching the limits of RFC 8200 compliance. The emails that you site
> below say that it is for the following reasons:
>
>
>
>    1. Because PSP is already deployed
>    2. Because PSP unburdens the ultimate segment router from the task of
>    processing and removing the SRH
>    3. Because PSP enables incremental deployment
>
>
>
> The first argument can be dismissed out of hand. Just because something
> has been deployed doesn’t mean that it adds value or even that it causes no
> harm.
>
>
>
> The second argument is dubious. Given that the ultimate segment endpoint
> has to remove the outer IPv6 header and forward the packet, the additional
> cost of checking the Segments Left field and removing the SRH is minimal.
>
>
>
> The third argument was best articulated Dan Voyer in
> https://mailarchive.ietf.org/arch/msg/spring/ErcErN39RIlzkL5SKNVAeEWpnAI/
> and deserves some consideration. In his deployment scenario, the ultimate
> segment endpoint:
>
>
>
>    - Can process a SID, received as an IPv6 DA, on the fast path
>    - Cannot process an SRH, even if Segments Left equal 0, on the fast
>    path.
>
>
>
> In this scenario, PSP keeps packets off of that device’s slow path.
>
>
>
> While I have sympathy for Dan’s dilemma, I wonder whether it is a good
> idea to stretch the IPv6 standard to accommodate IPv6-challenged devices.
>
>
>
> Maybe a compromise is possible? Would it be possible to move discussion of
> the PSP out of the Network programming draft and into a separate draft that
> a) describes the use-case in which it is required and b) discourages its
> use in all other cases.
>
>
>
>
>               Ron
>
>
>
> Juniper Business Use Only
>
> *From:* spring <[e-mail]> *On Behalf Of *Pablo Camarillo
> (pcamaril)
> *Sent:* Tuesday, February 25, 2020 10:17 AM
> *To:* Gyan Mishra <[e-mail]>
> *Cc:* SPRING WG <[e-mail]>
> *Subject:* Re: [spring] I-D Action:
> draft-ietf-spring-srv6-network-programming-10.txt
>
>
>
> Gyan,
>
>
>
> As I (and other WG members) have explained in the past, PSP is not trying
> to provide any feature parity with MPLS.
>
>
>
> It enables new use-cases that have been provided by other members in the
> list. [1], [2] and [5].
>
> From operational perspective it is not complex as explained in [3].
>
> There is substantial benefit. Four operators have deployed PSP, which
> proves the benefit.
>
> And additionally operators have expressed their value in [4] and [5].
>
>
>
> [1].-
> https://mailarchive.ietf.org/arch/msg/spring/wTLJQkzC6xwSNPbhB84VH0mLXx0
>
> [2].-
> https://mailarchive.ietf.org/arch/msg/spring/V0ZpjVLSVZxHaBwecXFxqJjlg_c
>
> [3].-
> https://mailarchive.ietf.org/arch/msg/spring/ssobwemrPz0uEZjvRCZP1e4l_l0
>
> [4].-
> https://mailarchive.ietf.org/arch/msg/spring/KXCBHT8Tpy17S5BsJXLBS35yZbk
>
> [5].-
> https://mailarchive.ietf.org/arch/msg/spring/ErcErN39RIlzkL5SKNVAeEWpnAI
>
>
>
> I don't see the point of starting a new thread from zero that discusses
> the same thing.
>
>
>
> Cheers,
>
> Pablo.
>
>
>
> *From: *Gyan Mishra <[e-mail]>
> *Date: *Tuesday, 25 February 2020 at 00:35
> *To: *"Pablo Camarillo (pcamaril)" <[e-mail]>
> *Cc: *Ron Bonica <[e-mail]>, SPRING WG <[e-mail]>
> *Subject: *Re: [spring] I-D Action:
> draft-ietf-spring-srv6-network-programming-10.txt
>
>
>
>
>
> PSP has historical context from PHP ( Penultimate Hop POP) in the MPLS
> world.
>
>
>
> 20+ years ago when MPLS we originally developed the concept of PHP
> implicit null reserved label value 0 was done to offload the burden of the
> egress PE FEC destination to pop the entire label stack before forwarding
> the native IP packet to the CE.
>
>
>
> Hardware these days for the last 15 years or so are so advanced that the
> idea that you are saving processing on the egress PE has not existed for a
> long time.
>
>
>
> Even  back then in both SP and enterprise space there were issues that
> arise related to PHB QOS egress queuing,  that occurs on the PHP node that
> had the MPLS shim popped, it cannot schedule on the topmost label via exp
> provider markings done on the ingress PE upon label imposition.
>
>
>
> A workaround to this issue was to set explicit null label value 0 and use
> pipe or uniform mode to tunnel the customer payload to the egress PE FEC
> destination called UHP ultimate hop node with topmost label intact.
>
>
>
> The concept of implicit null PHP concept did not bode well in the MPLS
> world so I don’t see why that feature parity would be added to a next gen
> protocol that would be the future MPLS replacement.
>
>
>
> I agree with taking some of the good features and knobs from MPLS, but why
> take the ones like implicit null with is really an archaic feature.
>
>
>
> My 2 cents
>
>
>
> Gyan
>
>
>
> On Mon, Feb 24, 2020 at 5:38 PM Pablo Camarillo (pcamaril) <pcamaril=
> [e-mail]> wrote:
>
> Ron,
>
>
>
> This is the 5th time that we have this discussion in the past five months.
>
>
>
> I consider those three questions as closed based on the previous
> discussion.
>
> https://mailarchive.ietf.org/arch/msg/spring/yRkDJlXd71k0VUqagM3D77vYcFI/
> <https://urldefense.com/v3/__https:/mailarchive.ietf.org/arch/msg/spring/yRkDJlXd71k0VUqagM3D77vYcFI/__;!!NEt6yMaO-gk!TEtwPySm6G-5vGGZ1n_7cdy_CuLlKozmPjpyK5rOohk2yw1JV1unB51aYs9oOW3B$>
>
>
>
> Cheers,
>
> Pablo.
>
>
>
> *From: *Ron Bonica <rbonica=[e-mail]>
> *Date: *Monday, 24 February 2020 at 16:27
> *To: *Andrew Alston <[e-mail]>, Mark Smith <
> [e-mail]>, Sander Steffann <[e-mail]>
> *Cc: *SPRING WG <[e-mail]>, "Pablo Camarillo (pcamaril)" <
> [e-mail]>
> *Subject: *RE: [spring] I-D Action:
> draft-ietf-spring-srv6-network-programming-10.txt
>
>
>
> Folks,
>
>
>
> We may need to ask the following questions:
>
>
>
> 1)      Does PSP violate letter of RFC 8200?
>
> 2)      Does PSP violate the spirit of RFC 8200?
>
> 3)      Is PSP a good idea?
>
>
>
> The 6man WG, and not SPRING, should answer the first two questions. So I
> will avoid them an explore the third.
>
>
>
> At first glance, PSP adds no value. Once Segments Left has been
> decremented to 0, the Routing header becomes a NOOP. So why bother to
> remove it? I see the following arguments:
>
>
>
> 1)      To save bandwidth between the penultimate and ultimate segment
> endpoints.
>
> 2)      To unburden the ultimate segment endpoint from the task of
> processing the SRH
>
> 3)      To unburden the ultimate segment endpoint from the task of
> removing the SRH
>
>
>
> The first argument is weak. Routing headers should not be so large that
> the bandwidth they consume is an issue.
>
>
>
> The second argument is also weak. Once the ultimate segment endpoint has
> examined the Segments Left field, it can ignore the SRH. The ultimate
> segment endpoint must be SRv6-aware, because it must process the SID in the
> IPv6 destination address field. Given that the ultimate segment endpoint is
> SRv6 aware, it should be able to process the SRH on the fast path.
>
>
>
> The third argument is even weaker. The ultimate segment endpoint:
>
> -          Has to remove the IPv6 tunnel header, anyway
>
> -          Being closer to the edge, may be less heavily loaded than the
> penultimate segment endpoint.
>
>
>
> Can anyone articulate a better justification for PSP? If not, why test the
> limits of RFC 8200 over it?
>
>
>
>
>                                          Ron
>
>
>
>
>
>
>
>
>
> Juniper Business Use Only
>
> *From:* spring <[e-mail]> *On Behalf Of *Andrew Alston
> *Sent:* Monday, February 24, 2020 5:06 AM
> *To:* Mark Smith <[e-mail]>; Sander Steffann <
> [e-mail]>
> *Cc:* SPRING WG <[e-mail]>; Pablo Camarillo (pcamaril) <pcamaril=
> [e-mail]>
> *Subject:* Re: [spring] I-D Action:
> draft-ietf-spring-srv6-network-programming-10.txt
>
>
>
> I agree with the sentiments expressed below
>
>
>
> Andrew
>
>
>
>
>
> *From:* spring <[e-mail]> *On Behalf Of *Mark Smith
> *Sent:* Monday, 24 February 2020 00:50
> *To:* Sander Steffann <[e-mail]>
> *Cc:* SPRING WG <[e-mail]>; Pablo Camarillo (pcamaril) <
> pcamaril=[e-mail]>
> *Subject:* Re: [spring] I-D Action:
> draft-ietf-spring-srv6-network-programming-10.txt
>
>
>
>
>
> On Mon, 24 Feb 2020, 07:47 Sander Steffann, <[e-mail]> wrote:
>
> Hi,
>
> > We have published a new update to
> draft-ietf-spring-srv6-network-programming. This revision simplifies the
> counters as per [1], clarifies the upper layer header processing as per [2]
> and removes the reference to the OAM draft [3].
>
> I still oppose the segment popping flavours in section 4.16 without
> updating RFC8200.
>
>
>
> I would expect that defying Internet Standard 86/RFC8200 means this ID
> needs to have Experimental rather than Standards Track status.
>
>
>
>
>
>
>
>
> Cheers,
> Sander
>
> _______________________________________________
> spring mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/spring
> <https://urldefense.com/v3/__https:/www.ietf.org/mailman/listinfo/spring__;!!NEt6yMaO-gk!Tfl9m_at6pZSp38lOtxE5WZLnsW_ojrgXUvQ_Rx-tN4MY7qa-MtwIQWgGCTduGJT$>
>
> _______________________________________________
> spring mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/spring
> <https://urldefense.com/v3/__https:/www.ietf.org/mailman/listinfo/spring__;!!NEt6yMaO-gk!TEtwPySm6G-5vGGZ1n_7cdy_CuLlKozmPjpyK5rOohk2yw1JV1unB51aYkKy0jPv$>
>
> --
>
> Gyan  Mishra
>
> Network Engineering & Technology
>
> Verizon
>
> Silver Spring, MD 20904
>
> Phone: [phone]
>
> Email: [e-mail]
>
>
>
>
> _______________________________________________
> spring mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/spring
>