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

Stewart Bryant <stbryant@cisco.com> Fri, 24 January 2014 18:04 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 732261A0040; Fri, 24 Jan 2014 10:04:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.035
X-Spam-Level:
X-Spam-Status: No, score=-10.035 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, 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 3r0WeC_ELcZh; Fri, 24 Jan 2014 10:04:57 -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 691091A003B; Fri, 24 Jan 2014 10:04:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5743; q=dns/txt; s=iport; t=1390586695; x=1391796295; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to; bh=38Pz967vdvkDhMGfnp2j9WEtHzW/xJWBdxFgrAvQajI=; b=FkWN2GAhM1dmD6cX5qS9xQiCIy1OO2kbZBPALYkb/r+W5y2wGaGh157G h+hBiHB4DuGPKoyK5xqpyQJZT+LJIRY8IZxclF0kI42AFUBnLqJJc2+1/ z4J60+JjWLXjcESemShIr9oYGBtMBS5iRvLCrnFsI8Fd86e59G8Unnzxb s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AiAFAAmr4lKQ/khM/2dsb2JhbABaDoI6RDi9C4ENFnSCJQEBAQQtSwEQCxgJFgQLCQMCAQIBRQYBDAEHAQGIAQ3INxMEjioRAVAHhDgEmCeSHoFvfz+BcQ
X-IronPort-AV: E=Sophos;i="4.95,714,1384300800"; d="scan'208,217";a="3473128"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by aer-iport-2.cisco.com with ESMTP; 24 Jan 2014 18:04:54 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id s0OI4r35000313 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 24 Jan 2014 18:04:53 GMT
Received: from [IPv6:::1] (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id s0OI4one006108; Fri, 24 Jan 2014 18:04:51 GMT
Message-ID: <52E2AB42.8060206@cisco.com>
Date: Fri, 24 Jan 2014 18:04:50 +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: John E Drake <jdrake@juniper.net>, Edward Crabbe <edc@google.com>, Joe Touch <touch@isi.edu>
References: <20140122172930.3D31A18C13B@mercury.lcs.mit.edu> <64A7AA55-795A-40FA-8008-5FCE3B8E2C44@netapp.com> <52E18661.4060000@isi.edu> <CACKN6JFzaGkiCzJgcd0BEHeWi5x0ReemJOv4ASuXAnz36RA-fg@mail.gmail.com> <e807421cc9fb4d98a46dce129aa39c82@BLUPR05MB562.namprd05.prod.outlook.com>
In-Reply-To: <e807421cc9fb4d98a46dce129aa39c82@BLUPR05MB562.namprd05.prod.outlook.com>
Content-Type: multipart/alternative; boundary="------------060005050208040809040604"
Cc: "mpls@ietf.org" <mpls@ietf.org>, "Eggert, Lars" <lars@netapp.com>, Noel Chiappa <jnc@mercury.lcs.mit.edu>, 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
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: Fri, 24 Jan 2014 18:04:59 -0000

On 24/01/2014 15:01, John E Drake wrote:
>
> Ed,
>
> I completely agree with your email, below.  As an aside, the L2 
> packets that Lars is worried about are transported over a pseudo-wire 
> using MPLS, so the logical place to place congestion awareness is in 
> the pseudo-wire endpoints.  I remember that this was in the PWE3's 
> charter some time ago.
>
> Yours Irrespectively,
>
> John
>
The charter says:

Whilst a service provider may traffic engineer their network
in such a way that PW traffic will not cause significant
congestion, a PW deployed by an end-user may cause
congestion of the underlying PSN. Suitable congestion
avoidance mechanisms are therefore needed to protect the
Internet from the unconstrained deployment of PWs. Congestion
avoidance may be more difficult with P2MP pseudowires than
P2P pseudowires. The WG will consider both cases.

https://datatracker.ietf.org/doc/draft-stein-pwe3-congcons/
has expired, but if you are interested in working on the subject
I am sure the authors would be delighted to talk to you.

Stewart