[mpls] Question about 0x8848 Ethertype
"Shahram Davari" <davari@broadcom.com> Thu, 22 October 2009 17:37 UTC
Return-Path: <davari@broadcom.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9C8633A6990 for <mpls@core3.amsl.com>; Thu, 22 Oct 2009 10:37:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=-0.001, BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L+BkNDhm2Ijz for <mpls@core3.amsl.com>; Thu, 22 Oct 2009 10:37:05 -0700 (PDT)
Received: from MMS3.broadcom.com (mms3.broadcom.com [216.31.210.19]) by core3.amsl.com (Postfix) with ESMTP id C137F3A6994 for <mpls@ietf.org>; Thu, 22 Oct 2009 10:37:05 -0700 (PDT)
Received: from [10.16.192.232] by MMS3.broadcom.com with ESMTP (Broadcom SMTP Relay (Email Firewall v6.3.2)); Thu, 22 Oct 2009 10:37:04 -0700
X-Server-Uuid: B55A25B1-5D7D-41F8-BC53-C57E7AD3C201
Received: from SJEXCHCCR02.corp.ad.broadcom.com ([10.16.192.130]) by SJEXCHHUB02.corp.ad.broadcom.com ([10.16.192.232]) with mapi; Thu, 22 Oct 2009 10:37:04 -0700
From: Shahram Davari <davari@broadcom.com>
To: "mpls@ietf.org" <mpls@ietf.org>
Date: Thu, 22 Oct 2009 10:37:03 -0700
Thread-Topic: Question about 0x8848 Ethertype
Thread-Index: AcpTPkQqPOLzLzS1RKq/F/isNc+5ZQ==
Message-ID: <2C2F1EBA8050E74EA81502D5740B4BD6815768387B@SJEXCHCCR02.corp.ad.broadcom.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
MIME-Version: 1.0
X-WSS-ID: 66FE47B50UC23549803-01-01
Content-Type: multipart/alternative; boundary="_000_2C2F1EBA8050E74EA81502D5740B4BD6815768387BSJEXCHCCR02co_"
Subject: [mpls] Question about 0x8848 Ethertype
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Thu, 22 Oct 2009 17:37:06 -0000
Hi, RFC 5332 says: "Ethertype 0x8848, formerly known as the "MPLS multicast codepoint", is to be used only when an MPLS packet whose top label is upstream- assigned is carried in a multicast Ethernet frame." It also says: "It is expected that the LSR will follow the procedures of [RFC5331], pushing on two labels, with the topmost label being a "context label" that is the same for all MPLS packets being transmitted by the LSR onto the Ethernet, but with the second label being different for different LSPs" And RFC 5331 defines context label as: "A "context label" is one that identifies a label table in which the label immediately below the context label should be looked up. A context label carried as an outermost label over a particular multi-access subnet/tunnel MUST be unique within the scope of that subnet/tunnel." Considering the above statements we can conclude that: "Multicast MPLS packets with upstream assigned labels encapsulated in Multicast Ethernet frames in a Multi-access media (LAN) require to use 0x8848 as Ethertype and require to use a context label that is unique over that media to identify the label space for the Multicast MPLS packet" The question is since a context label is unique in a LAN and can be immediately identified as an upstream label, then why do we need 0x8847 Ethertype? Looks like we could just use the context label. Am I missing something? Regards, Shahram
- [mpls] Question about 0x8848 Ethertype Shahram Davari
- Re: [mpls] Question about 0x8848 Ethertype Nitin Bahadur
- Re: [mpls] Question about 0x8848 Ethertype Shahram Davari
- Re: [mpls] Question about 0x8848 Ethertype Nitin Bahadur
- Re: [mpls] Question about 0x8848 Ethertype Shahram Davari
- Re: [mpls] Question about 0x8848 Ethertype Nitin Bahadur
- Re: [mpls] Question about 0x8848 Ethertype Shahram Davari
- Re: [mpls] Question about 0x8848 Ethertype Eric Rosen
- Re: [mpls] Question about 0x8848 Ethertype Shahram Davari
- Re: [mpls] Question about 0x8848 Ethertype Shahram Davari
- Re: [mpls] Question about 0x8848 Ethertype Eric Rosen
- Re: [mpls] Question about 0x8848 Ethertype Mitchell Erblich