Re: [spring] We don't seem to be following our processes (Re: Network Programming - Penultimate Segment Popping)

[Robert Raszuk <[e-mail]>]

Hi Sander,

To your specific first question this is very popular deployment model ..
just look at SDWANs. So Internet is just a L3 transport for all routers in
your administrative domain or global WAN. Spot on. I do sincerely hope that
whatever the result be of this debate all features will be legal to run on
my boxes regardless how I choose to interconnect them.

As (Internet) transit boxes would never be destination addresses of the
outermost header what problem do you see running anything one likes on R1
or R2 or R3 and transporting it via open Internet or perhaps some third
party networks ?

Just pls limit the answer to technical points if at all possible.

And if your first point is MTU then assume I have this solved by code
running between my routers in the overlay even including making sure that
my probe is inline with the data - hence identical ECMP hashing.

Best,
R.


On Fri, Dec 6, 2019 at 4:13 PM Sander Steffann <[e-mail]> wrote:

> Hi Ole,
>
> > If I own and manage three routers, R1 -- R2 -- R3.
> > You are saying that if R1 sends a packet to R3, it is not allowed to
> off-load some functions to R2?
> > Going to be difficult to do stuff like service chaining then.
>
> This bit I don't mind that much, but what about:
>
> R1 -- R2 -- [open internet] -- R3
> or
> R1 -- [open internet] -- R2 -- R3
> or even
> R1 -- [open internet] -- R2 -- [open internet] -- R3
>
> And what if you're an ISP and R1 is your customer's device? It is in your
> routing domain but not in your administrative domain. What then?
>
>