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

Stewart Bryant <stbryant@cisco.com> Wed, 22 January 2014 10:09 UTC

Return-Path: <stbryant@cisco.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 0EF341A02D0 for <mpls@ietfa.amsl.com>; Wed, 22 Jan 2014 02:09:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.036
X-Spam-Level:
X-Spam-Status: No, score=-10.036 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] 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 iOkqm9Q_RxCu for <mpls@ietfa.amsl.com>; Wed, 22 Jan 2014 02:09:03 -0800 (PST)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) by ietfa.amsl.com (Postfix) with ESMTP id 02C0D1A02C2 for <mpls@ietf.org>; Wed, 22 Jan 2014 02:08:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=881; q=dns/txt; s=iport; t=1390385340; x=1391594940; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=DKh1cOu4uImSRT/VJVgHNSTXmN3ucltgnCh+zO8JDy4=; b=eoPblhno8uUB21E+KWJWdB6qyvSGyUYYbtZr8bT5HeQ/yz3hL5Awn+Ou SUJau3E+4SLNKoXnH8dWAT/+Ansenot+8YADtcF951WYJJS7NNa0v8irs FdyI3kXsd+S5/CCBwLMXk42EWO3uZgax19uVLgEmgr6O7wasIYbjzT2FM k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhoFAKCX31KQ/khN/2dsb2JhbABbgwu5ZIMFgREWdIIlAQEBBDhAARALGAkWBAsJAwIBAgFFBgEMAQcBAYgBwUgXjiRYB4Q4AQOYIpIYgW+BPoFo
X-IronPort-AV: E=Sophos;i="4.95,698,1384300800"; d="scan'208";a="3332408"
Received: from ams-core-4.cisco.com ([144.254.72.77]) by aer-iport-2.cisco.com with ESMTP; 22 Jan 2014 10:08:58 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id s0MA8wmZ004158 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 22 Jan 2014 10:08:58 GMT
Received: from [IPv6:::1] (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id s0MA8u22019306; Wed, 22 Jan 2014 10:08:56 GMT
Message-ID: <52DF98B8.3050208@cisco.com>
Date: Wed, 22 Jan 2014 10:08:56 +0000
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: "Eggert, Lars" <lars@netapp.com>, "curtis@ipv6.occnc.com" <curtis@ipv6.occnc.com>
References: <201401212014.s0LKEDXM065730@maildrop2.v6ds.occnc.com> <1811208D-230A-4EA7-B5AA-07E2C0460120@netapp.com>
In-Reply-To: <1811208D-230A-4EA7-B5AA-07E2C0460120@netapp.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: Joel Jaeggli <joelja@bogus.com>, "mpls@ietf.org" <mpls@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
Reply-To: stbryant@cisco.com
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: Wed, 22 Jan 2014 10:09:05 -0000

On 22/01/2014 07:51, Eggert, Lars wrote:
> This is not at all the argument I am making. My emails have not touched at all on the issue of zero checksums.
>
> My point is that UDP encapsulation changes the potential *reach* of congestion-uncontrolled traffic that was otherwise limited to L2 networks.
>
> Lars
How about if text is introduced recommending the use of an
OAM between tunnel endpoints that monitors packet loss.

The tunnel endpoints need to know if the tunnel is broken
anyway and on hitting a loss threshold they can  alarm,
redirect the traffic, or shutdown, depending on configuration,
topology and the needs of the operator.

You probably also need pro-active CV to make the whole
system work.

This many not necessarily be fast or elegant, but if there
is significant misdelivery or congestion loss, traffic will
eventually cease.

Stewart