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

Joe Touch <touch@isi.edu> Thu, 30 January 2014 20:30 UTC

Return-Path: <touch@isi.edu>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E13F21A0467; Thu, 30 Jan 2014 12:30:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.735
X-Spam-Level:
X-Spam-Status: No, score=-4.735 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EQQlbbMCkwTs; Thu, 30 Jan 2014 12:30:26 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id 5C89D1A046D; Thu, 30 Jan 2014 12:30:26 -0800 (PST)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id s0UKTLZH022449 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 30 Jan 2014 12:29:21 -0800 (PST)
Message-ID: <52EAB621.5010403@isi.edu>
Date: Thu, 30 Jan 2014 12:29:21 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Scott Brim <scott.brim@gmail.com>
References: <201401240320.s0O3KsR9013700@maildrop2.v6ds.occnc.com> <52E2BBC0.2030203@isi.edu> <52E68C12.2050308@cisco.com> <98034F7E-47CF-4ABE-A199-A9DB4DACBC2E@isi.edu> <52E6AA0B.1050600@bogus.com> <52E6AB15.2080907@isi.edu> <52E6B128.8060306@joelhalpern.com> <47d85636e70c4d6f86f199a274bcdcb0@CO2PR05MB636.namprd05.prod.outlook.com> <52EAA7F7.1010502@isi.edu> <CAPv4CP9JURzh44XtX5Q418ZBfcBAVctyGK6hEVjj8tp-97bs4g@mail.gmail.com>
In-Reply-To: <CAPv4CP9JURzh44XtX5Q418ZBfcBAVctyGK6hEVjj8tp-97bs4g@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: "mpls@ietf.org" <mpls@ietf.org>, IETF discussion list <ietf@ietf.org>, "EXT - joelja@bogus.com" <joelja@bogus.com>, Ross Callon <rcallon@juniper.net>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls/>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Jan 2014 20:30:28 -0000

On 1/30/2014 12:20 PM, Scott Brim wrote:
> There are two topics that should be separate: checksums and congestion
> control.

Agreed.

> On Thu, Jan 30, 2014 at 2:28 PM, Joe Touch <touch@isi.edu
> <mailto:touch@isi.edu>> wrote:
>
>     I think we agree that if the router needs faster, then the router
>     gets faster.
>
> That's in response to Ross, about checksums.

Also about the complaint that routers run to fast to run any sort of 
congestion algorithm, including circuit breakers (which is clearly false).

>     Where we disagree is whether the "bull in the china shop" gets to
>     ignore the rules of the road to get what it wants.
>
> congestion

Yes, in the sense that incorrect checksums should be checked at the 
egress only anyway, and thus ignoring them would only impact the network 
after the egress.

No, in the sense that anything that peeks inside a UDP header has the 
right to want to check whether that data is uncorrupted - that includes 
things like NATs.

>     I.e., I won't disagree on what router vendors want or what they're
>     willing to support (though I will disagree on what hardware can do,
>     based on experience).
>
> checksums

Both, as per above.

>     I will disagree that routers get to run roughshod over the rest of
>     us to do it.
>
>     Simple solution -- don't use UDP.
>
> congestion.

Both. If you want the benefits of UDP, pay the penalty. If you don't 
want the penalty, don't use UDP.

I don't buy the claims that there's a need here to eat cake and have it too.

> Joe, do I understand correctly that you've conceded about checksums and
> now you want to talk about congestion again?

I'm talking about the overall argument, which has circled back to "we 
need to do what vendors are willing to do", rather than "vendors need to 
play nice in the Internet that they're making money off of".

Joe