Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

On 2014-1-10, at 22:32, Scott Brim <scott.brim@xxxxxxxxx> wrote:
> OK good point - so we invoke the end-to-end argument on MPLS's behalf.

look at it the other way. From the viewpoint of the rest of the net, you are an application using UDP. Such applications need to follow a set of principles we have IETF consensus on (RFC5405).

By encapsulating MPLS in UDP, you are changing the game. That traffic can now appear on any Internet path, and not just inside provisioned networks. Because of that, you need a mechanism to detect if you are causing congestion, and a mechanism to react to it.

And it *is* a requirement on the encapsulator, because from the perspective of the rest of the net, that is the application that generates the UDP traffic.

Lars

Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail


[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Fedora Users]