Re: [mpls] I have questions

David Charlap <David.Charlap@marconi.com> Mon, 13 December 2004 15:41 UTC

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA20554; Mon, 13 Dec 2004 10:41:03 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CdsRi-00010j-G5; Mon, 13 Dec 2004 10:49:11 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CdsCY-0004dv-Dc; Mon, 13 Dec 2004 10:33:30 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Cds3H-0001ie-ES for mpls@megatron.ietf.org; Mon, 13 Dec 2004 10:23:55 -0500
Received: from mailgate.pit.comms.marconi.com (mailgate.pit.comms.marconi.com [169.144.68.6]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18568 for <mpls@lists.ietf.org>; Mon, 13 Dec 2004 10:23:53 -0500 (EST)
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12]) by mailgate.pit.comms.marconi.com (8.12.10+Sun/8.12.10) with ESMTP id iBDFNNcT005608 for <mpls@lists.ietf.org>; Mon, 13 Dec 2004 10:23:23 -0500 (EST)
Received: from [169.144.136.107] (dcharlap-pc.dc.fore.com [169.144.136.107]) by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id KAA06420 for <mpls@lists.ietf.org>; Mon, 13 Dec 2004 10:23:23 -0500 (EST)
Message-ID: <41BDB3EA.3000102@marconi.com>
Date: Mon, 13 Dec 2004 10:23:22 -0500
From: David Charlap <David.Charlap@marconi.com>
Organization: Marconi, Vienna VA
User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: IETF MPLS List <mpls@ietf.org>
Subject: Re: [mpls] I have questions
References: <BAY17-F8A48581DA27251B18776ABBAB0@phx.gbl>
In-Reply-To: <BAY17-F8A48581DA27251B18776ABBAB0@phx.gbl>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@lists.ietf.org?subject=subscribe>
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Content-Transfer-Encoding: 7bit

Lee Garth wrote:
> 
>    What if an LSR node receives a packet with a label, and the LFIB in 
> the LSR doesn't have a matching entry for the label? Eg. there is no 
> entry in LFIB whose incoming label is the same as the label from the 
> receiving packet.

If you receive a packet with an unknown label, you should drop the packet.

To do anything else would result in undefined behavior.

Some people have entertained the idea of popping the label in this
situation.  This is bad, because a transit switch does not know the
nature of the packet under the label.  It might not be an IP packet. The
transit switch may not have routing information to the destination
(assuming it is IP.)  If there are inner labels, the transit switch may
not be able to handle them either.  (For example, VPN-identifying labels
are usually unknown to all but the PE routers.)

-- David


_______________________________________________
mpls mailing list
mpls@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/mpls