IETF Logo Mail Archive

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

Stewart Bryant <stbryant@cisco.com> Mon, 13 January 2014 09:35 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 A9CB91AE055 for <mpls@ietfa.amsl.com>; Mon, 13 Jan 2014 01:35:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.039
X-Spam-Level:
X-Spam-Status: No, score=-10.039 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.538, 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 8Thpw841awJR for <mpls@ietfa.amsl.com>; Mon, 13 Jan 2014 01:35:15 -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 7CF6B1ADF91 for <mpls@ietf.org>; Mon, 13 Jan 2014 01:35:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=756; q=dns/txt; s=iport; t=1389605705; x=1390815305; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=fCC+6B4dRml0YwA9B/bNhBw8CSmazGABsodQJ+wJJgY=; b=W7c1+IUDPA8LT3KP8JOqF7vaOfN0Z2moigqD6i88CRXyyxfcewNgrPFS 284fdxDtlrd8N4XU51cQY5snL2yw+kn6T+xeCEH8JmzfqJ6Cx7+KOzlgx fQQdOjkDVrCePlvbyIuASUknKLMT7Lg37G6pGSi9RjDO0hcNeo62zFECx E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AiEFABCy01KQ/khR/2dsb2JhbABagwu3boMIgQ4WdIIlAQEBBDhAARALGAkWBAsJAwIBAgFFBgEMAQcBAYgAxFYXjwcHhDcBA5gXkhWBb4E+
X-IronPort-AV: E=Sophos;i="4.95,651,1384300800"; d="scan'208";a="2881651"
Received: from ams-core-1.cisco.com ([144.254.72.81]) by aer-iport-2.cisco.com with ESMTP; 13 Jan 2014 09:35:03 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id s0D9Z2Kq024003 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 13 Jan 2014 09:35:03 GMT
Received: from [IPv6:::1] (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id s0D9Z1h3023919; Mon, 13 Jan 2014 09:35:01 GMT
Message-ID: <52D3B345.4050002@cisco.com>
Date: Mon, 13 Jan 2014 09:35:01 +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: mark.tinka@seacom.mu, Gregory Mirsky <gregory.mirsky@ericsson.com>
References: <20140102151419.4692.48031.idtracker@ietfa.amsl.com> <201401121444.31194.mark.tinka@seacom.mu> <7347100B5761DC41A166AC17F22DF1121B744E67@eusaamb103.ericsson.se> <201401130713.13126.mark.tinka@seacom.mu>
In-Reply-To: <201401130713.13126.mark.tinka@seacom.mu>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: "mpls@ietf.org" <mpls@ietf.org>, "Eggert, Lars" <lars@netapp.com>
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: Mon, 13 Jan 2014 09:35:16 -0000

On 13/01/2014 05:13, Mark Tinka wrote:
> On Monday, January 13, 2014 03:30:04 AM Gregory Mirsky
> wrote:
>
>> Hi Mark,
>> if by "provisioning" you mean "mapped to", "assigned",
>> then what about IP addresses? Ain't they pre-provisioned
>> as well? Or these are native properties of NEs?
> The path that two successive IP packets take to get from
> point A to B, in an MPLS-free network, can be arbitrary.
It can be arbitrary, but the router designers try rather hard
to make sure that flows follow the same path. This is because
the transport protocols in the hosts complain if the routers
introduce misordering.  Remove that constraint and the
forwarders become a lot simpler and we can do all sorts
of anti-PM in the network.

Stewart

v2.23.0 | Report a Bug | By Email