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

"Joel M. Halpern" <jmh@joelhalpern.com> Mon, 03 December 2012 15:57 UTC

Return-Path: <jmh@joelhalpern.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 2F91E21F86C3 for <mpls@ietfa.amsl.com>; Mon, 3 Dec 2012 07:57:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.515
X-Spam-Level:
X-Spam-Status: No, score=-102.515 tagged_above=-999 required=5 tests=[AWL=-0.250, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, 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 JlkH9UiX6FTy for <mpls@ietfa.amsl.com>; Mon, 3 Dec 2012 07:57:43 -0800 (PST)
Received: from morbo.mail.tigertech.net (morbo.mail.tigertech.net [67.131.251.54]) by ietfa.amsl.com (Postfix) with ESMTP id 9388421F86B5 for <mpls@ietf.org>; Mon, 3 Dec 2012 07:57:43 -0800 (PST)
Received: from mailc2.tigertech.net (mailc2.tigertech.net [208.80.4.156]) by morbo.tigertech.net (Postfix) with ESMTP id 8D092A6814 for <mpls@ietf.org>; Mon, 3 Dec 2012 07:57:41 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailc2.tigertech.net (Postfix) with ESMTP id 988EB1BDA437; Mon, 3 Dec 2012 07:57:40 -0800 (PST)
X-Virus-Scanned: Debian amavisd-new at c2.tigertech.net
Received: from [10.10.10.104] (pool-71-161-50-174.clppva.btas.verizon.net [71.161.50.174]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailc2.tigertech.net (Postfix) with ESMTPSA id BE9991BDA3EB; Mon, 3 Dec 2012 07:57:39 -0800 (PST)
Message-ID: <50BCCBE4.7010606@joelhalpern.com>
Date: Mon, 03 Dec 2012 10:57:24 -0500
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: stbryant@cisco.com
References: <4FDCDA0D.6010204@joelhalpern.com> <50B34B9D.3040102@cisco.com> <50B39D99.90209@joelhalpern.com> <50BCB775.2060909@cisco.com>
In-Reply-To: <50BCB775.2060909@cisco.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
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 15:57:44 -0000

That suffices.
Thank you,
Joel

PS: My personal guess is that on a link known correctly to be 
point-to-point FF-FF-FF-FF-FF-FF would work fine.  But that is a WG 
call, and the new text is sufficient.

On 12/3/2012 9:30 AM, Stewart Bryant wrote:
> 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
>> .
>>
>
>