IETF Logo Mail Archive

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

Scott Brim <scott.brim@gmail.com> Tue, 14 January 2014 13:12 UTC

Return-Path: <scott.brim@gmail.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 276F01AE0D2; Tue, 14 Jan 2014 05:12:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] 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 Z5HCmf6PJhQP; Tue, 14 Jan 2014 05:11:57 -0800 (PST)
Received: from mail-oa0-x232.google.com (mail-oa0-x232.google.com [IPv6:2607:f8b0:4003:c02::232]) by ietfa.amsl.com (Postfix) with ESMTP id C66EE1AE0D1; Tue, 14 Jan 2014 05:11:49 -0800 (PST)
Received: by mail-oa0-f50.google.com with SMTP id l6so9507208oag.23 for <multiple recipients>; Tue, 14 Jan 2014 05:11:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=26v0ajTFWiDpEIK5le1Spsm0vQYR1AbrRr6GeKfRa5c=; b=s8ch4Xo2M9/nrfir6BxgTMfsoNU2h3pYpHOIewwaJcNua0kJBVRyfoB+3g/zMjEjya pbJKE35LN1KY9Am/h0WZj8KTDBUh33Xoe4+7VcktZ6QQiGWTZMaVsvDOz49Dj89T4xrR ockbJU15HOjG4h5WTo8XlcMknRWtxh4OfbBTPhmwxDBDmu21Ex/QyZhUfszIuMLlww54 j5xc9N63VS8luliGcHzTNnmvLXeeq0su9aWF963KMVpopw+4AdYcmID8HCgwKoM1/s7y NCrj5C/BKlSLCIB4U5Xd/RhhqH4X65SPQ5lE7pGKgQi36KC5c7VrOsxKlWKJ1Egpn7qD STkA==
MIME-Version: 1.0
X-Received: by 10.60.174.167 with SMTP id bt7mr1019432oec.54.1389705098259; Tue, 14 Jan 2014 05:11:38 -0800 (PST)
Received: by 10.182.48.9 with HTTP; Tue, 14 Jan 2014 05:11:38 -0800 (PST)
Received: by 10.182.48.9 with HTTP; Tue, 14 Jan 2014 05:11:38 -0800 (PST)
In-Reply-To: <52D518D9.7010703@cisco.com>
References: <20140102151419.4692.48031.idtracker@ietfa.amsl.com> <5933BB7D-2D2D-4145-A0B2-E92C8DA25844@netapp.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE08242A8E@NKGEML512-MBS.china.huawei.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>
Date: Tue, 14 Jan 2014 08:11:38 -0500
Message-ID: <CAPv4CP-eNJuOKv4vWxGkiUPUTMkYyqY4cbTmj8M4sn+jXzmCkw@mail.gmail.com>
From: Scott Brim <scott.brim@gmail.com>
To: Stewart Bryant <stbryant@cisco.com>
Content-Type: multipart/alternative; boundary="047d7bd6c03eb9759f04efedee24"
Cc: "mpls@ietf.org" <mpls@ietf.org>, "Eggert, Lars" <lars@netapp.com>, 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 13:12:02 -0000

On Jan 14, 2014 6:00 AM, "Stewart Bryant" <stbryant@cisco.com> wrote:
>
> On 13/01/2014 19:09, Scott Brim wrote:
>>
>> On Mon, Jan 13, 2014 at 10:51 AM, Joel M. Halpern <jmh@joelhalpern.com>
wrote:
>> I'm concerned about TCP-over-X.25 scenarios.
>
> ... and how many b/s of that exist in the universe!

Stewart: none that I know of, of course, but it was in production at a
significant time in Internet history and was one of our first experiences
with multiple layers each trying to provide transport control and thereby
destroying goodput. I'll never forget it. When I think of two layers each
trying to do congestion management,  with no way to coordinate with each
other, that's the first example that comes to mind.

Scott

v2.23.0 | Report a Bug | By Email