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

Wesley Eddy <wes@mti-systems.com> Tue, 14 January 2014 16:22 UTC

Return-Path: <wes@mti-systems.com>
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 1AE6B1AE10D for <mpls@ietfa.amsl.com>; Tue, 14 Jan 2014 08:22:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=unavailable
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 ky-ojuJbJhpn for <mpls@ietfa.amsl.com>; Tue, 14 Jan 2014 08:22:32 -0800 (PST)
Received: from atl4mhob10.myregisteredsite.com (atl4mhob10.myregisteredsite.com [209.17.115.48]) by ietfa.amsl.com (Postfix) with ESMTP id CC9301AE16F for <mpls@ietf.org>; Tue, 14 Jan 2014 08:22:23 -0800 (PST)
Received: from mailpod.hostingplatform.com ([10.30.71.204]) by atl4mhob10.myregisteredsite.com (8.14.4/8.14.4) with ESMTP id s0EGMA0m002458 for <mpls@ietf.org>; Tue, 14 Jan 2014 11:22:10 -0500
Received: (qmail 17092 invoked by uid 0); 14 Jan 2014 16:22:10 -0000
X-TCPREMOTEIP: 107.48.137.115
X-Authenticated-UID: wes@mti-systems.com
Received: from unknown (HELO ?192.168.43.65?) (wes@mti-systems.com@107.48.137.115) by 0 with ESMTPA; 14 Jan 2014 16:22:10 -0000
Message-ID: <52D5642A.7090103@mti-systems.com>
Date: Tue, 14 Jan 2014 11:22:02 -0500
From: Wesley Eddy <wes@mti-systems.com>
Organization: MTI Systems
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: "Eggert, Lars" <lars@netapp.com>, Scott Brim <scott.brim@gmail.com>
References: <20140102151419.4692.48031.idtracker@ietfa.amsl.com> <43B89809-F517-4BE2-BE1B-748A4B78FC7F@netapp.com> <52D01383.2080509@joelhalpern.com> <8DCFAFEE-2B06-4334-A5D7-7698D8D3081A@netapp.com> <CAPv4CP-iwoHEiV=xtNAd7qT4r8OYvfE1ZjnKE=wWY5VVcQ3x8w@mail.gmail.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0824427A@NKGEML512-MBS.china.huawei.com> <A1F82D9D-F9D0-46C1-B666-0C13DB79A845@netapp.com> <52D40B91.8040101@joelhalpern.com> <CAPv4CP9R-6Dv9O_H8Ox_-uLWMSzqpx7Gn97TF8jceFkVKPLWTw@mail.gmail.com> <52D518D9.7010703@cisco.com> <CAPv4CP-eNJuOKv4vWxGkiUPUTMkYyqY4cbTmj8M4sn+jXzmCkw@mail.gmail.com> <CAPv4CP-DnNdSoVEFTg9N53xP=yOd6pNe97WxmXJeGHBPKC2h6w@mail.gmail.com> <52D547B2.1060302@cisco.com> <DB6CF60F-FFBA-47DA-9FD6-7288CCB260A6@netapp.com> <52D5568F.2070600@joelhalpern.com> <3D9BA53E-F0F7-4B8B-8433-4DFE6852AF87@netapp.com> <CAPv4CP_3DmjZQN=LQmV53-8HsZDHukpdu0Lyuh9KwOgXQ-v=EQ@mail.gmail.com> <C54B4791-A023-4512-84C6-50869BBE9B66@netapp.com>
In-Reply-To: <C54B4791-A023-4512-84C6-50869BBE9B66@netapp.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: "mpls@ietf.org" <mpls@ietf.org>, IETF discussion list <ietf@ietf.org>
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: Tue, 14 Jan 2014 16:22:34 -0000

On 1/14/2014 11:06 AM, Eggert, Lars wrote:
> Hi,
> 
> On 2014-1-14, at 16:39, Scott Brim <scott.brim@gmail.com> wrote:
>> Lars, I know we're repeating arguments from the last decade. The
>> choice is between (1) specifying congestion control around the
>> substrate UDP that can be turned off if it causes problems, or (2)
>> specifying nothing at this time and adding it later if operators want
>> it.
>>
>> I guess if this can be written as a SHOULD, up to the implementor's
>> discretion, then okay.
> 
> I don't think we can leave this up to implementors discretion. We've had IETF consensus that Internet communication requires congestion control at least since RFC2914. A circuit breaker mechanisms seems straightforward to implement.
> 
> As is, I object to this document going forward. The minor benefits of getting some better load balancing for MPLS are far outweighed by the risks.
> 
> (I'm also going to shut up now, and let others speak. I think I've said my bit.)
> 


I'm in basic agreement.

Assuming we might all agree that there are conceivable scenarios where
a circuit breaker mechanism would be useful, is the real issue that
we don't all agree that it could be implemented in a way that's not
burdensome and doesn't degrade performance unnecessarily?

Or is there still fundamental disagreement about whether the scenarios
where the circuit breaker is useful are even valid?

-- 
Wes Eddy
MTI Systems