Re: [mpls] Comment on draft-ietf-mpls-tp-ethernet-addressing

Stewart Bryant <stbryant@cisco.com> Mon, 03 December 2012 14:30 UTC

Return-Path: <stbryant@cisco.com>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 826D921F86F3 for <mpls@ietfa.amsl.com>; Mon, 3 Dec 2012 06:30:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level:
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SfFmiMcOlgoF for <mpls@ietfa.amsl.com>; Mon, 3 Dec 2012 06:30:19 -0800 (PST)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by ietfa.amsl.com (Postfix) with ESMTP id 6051221F86CF for <mpls@ietf.org>; Mon, 3 Dec 2012 06:30:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2808; q=dns/txt; s=iport; t=1354545020; x=1355754620; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=isTVSzCZQKJf8cEqAAE7wblQUL3x0J/t/2APrAynAhM=; b=FkohCmWuG1nCDbbfbooW2EORP4YDbLXLKIT7hetWoZgO/ixoYBSzffgl GytWKm8kLkX72sXKtMpfAinF1FK6Vk9gYcPkfxY6TcVsCr/eCNTaThVfQ wsWnq02wZfbJ6j+QnVtHzQib85f/7KXxhlrAmSs9hm+y7eDCCrZz/yRa8 k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAAu3vFCQ/khN/2dsb2JhbABEwAAWc4IeAQEBBDhAARALGAkWDwkDAgECAUUGDQEHAQGIDAy+H4xAhEEDlgGFa4pcgnKBYwU
X-IronPort-AV: E=McAfee;i="5400,1158,6914"; a="147708948"
Received: from ams-core-4.cisco.com ([144.254.72.77]) by ams-iport-1.cisco.com with ESMTP; 03 Dec 2012 14:30:18 +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 qB3EUH5Y011627 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 3 Dec 2012 14:30:18 GMT
Received: from [127.0.0.1] (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id qB3EUD59016622; Mon, 3 Dec 2012 14:30:15 GMT
Message-ID: <50BCB775.2060909@cisco.com>
Date: Mon, 03 Dec 2012 14:30:13 +0000
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: "Joel M. Halpern" <jmh@joelhalpern.com>
References: <4FDCDA0D.6010204@joelhalpern.com> <50B34B9D.3040102@cisco.com> <50B39D99.90209@joelhalpern.com>
In-Reply-To: <50B39D99.90209@joelhalpern.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: "mpls@ietf.org" <mpls@ietf.org>
Subject: Re: [mpls] Comment on draft-ietf-mpls-tp-ethernet-addressing
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.12
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, 03 Dec 2012 14:30:20 -0000

Joel

I have changed the text to:

Another approach which may be considered is to use the Ethernet 
broadcast address FF-FF-FF-FF-FF-FF as the destination MAC address in 
frames carrying MPLS-TP packets over a link that is known to be 
point-to-point. This may, however, lead to excessive frame distribution 
and processing at the Ethernet layer. Broadcast traffic may also be 
treated specially by some devices and this may not be desirable for 
MPLS-TP data frames.

In view of the above considerations, the approach which SHOULD be used, 
is therefore to configure both nodes to use the method descibed in this 
document which uses, as a destination MAC address, an Ethernet multicast 
address reserved for MPLS-TP for use over point-to-point links. The 
address allocated for this purpose by the Internet Assigned Numbers 
Authority (IANA) is 01-00-5E-90-00-00. An MPLS-TP implementation MUST 
process Ethernet frames received over a point-to-point link with this 
destination MAC address by default.

Which I think should address your concern

- Stewart



On 26/11/2012 16:49, Joel M. Halpern wrote:
> Stewart,
>     Your description is what I would have expected.
>  However, sectio 2 of this document recommends that implementations 
> use this multicast address on pt-to-pt MLS-TP links.  There is no 
> discussion of negotiation, discovery, or even configuration.  The text 
> as written seems to simply assume that using this multicast address 
> will work. Your description clearly says that it won't work.
>
> Yours,
> Joel
>
> On 11/26/2012 5:59 AM, Stewart Bryant wrote:
>> On 16/06/2012 20:10, Joel M. Halpern wrote:
>>> In reviewing this document (sorry I am a day late for the WG LC end),
>>> a question occurred to me regarding the material in section 2.
>>>
>>> Is there reason to believe that existing implementations will process
>>> received frames on pt-to-pt Ethernet links where the destination
>>> address is 01-00-5E-90-00-00?  If so, should that reason be mentioned
>>> (or am I just missing the obvious here?)  If not, is this a safe
>>> recommendation?
>>>
>>> Otherwise, this is clear and useful.
>>> Thank you,
>>> Joel
>>
>> Hi Joel, I only just noticed that I did not reply on this.
>>
>> An MPLS-TP LSR  will reject all ethernet packets received on addresses
>> that it is not configured to receive packets on. This is how Ethernet
>> interfaces work. Thus an existing implementation will ignore packets
>> sent with a MAC address of 01-00-5E-90-00-00, since the address is not
>> meaningful to it and thus will not have been configured for reception.
>>
>> Regards
>>
>> Stewart
> .
>


-- 
For corporate legal information go to:

http://www.cisco.com/web/about/doing_business/legal/cri/index.html