IETF Logo Mail Archive

RE: [mpls] For your review - Issues/errors/clarifications in RFC3 036

neil.2.harrison@bt.com Fri, 08 October 2004 10:07 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 GAA09398; Fri, 8 Oct 2004 06:07:11 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CFroT-0002v5-P7; Fri, 08 Oct 2004 06:17:26 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CFrcN-0001bg-VD; Fri, 08 Oct 2004 06:04:55 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CFrcC-0001UJ-F7 for mpls@megatron.ietf.org; Fri, 08 Oct 2004 06:04:44 -0400
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 GAA09230 for <mpls@ietf.org>; Fri, 8 Oct 2004 06:04:42 -0400 (EDT)
From: neil.2.harrison@bt.com
Received: from smtp3.smtp.bt.com ([217.32.164.138]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CFrm5-0002rx-6D for mpls@ietf.org; Fri, 08 Oct 2004 06:14:58 -0400
Received: from i2km95-ukbr.domain1.systemhost.net ([193.113.197.29]) by smtp3.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.80); Fri, 8 Oct 2004 11:05:10 +0100
Received: from i2km07-ukbr.domain1.systemhost.net ([193.113.197.26]) by i2km95-ukbr.domain1.systemhost.net with Microsoft SMTPSVC(5.0.2195.6713); Fri, 8 Oct 2004 11:05:09 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.0.6556.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [mpls] For your review - Issues/errors/clarifications in RFC3 036
Date: Fri, 08 Oct 2004 11:05:09 +0100
Message-ID: <0536FC9B908BEC4597EE721BE6A353890A9F12E8@i2km07-ukbr.domain1.systemhost.net>
Thread-Topic: [mpls] For your review - Issues/errors/clarifications in RFC3 036
Thread-Index: AcSsx14s9gp7B99oTx+fssHyzqJ8kAAVVl1Q
To: ewgray@GraIyMage.com, Nick.Weeds@dataconnection.com
X-OriginalArrivalTime: 08 Oct 2004 10:05:09.0642 (UTC) FILETIME=[4B416EA0:01C4AD1E]
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199
Content-Transfer-Encoding: quoted-printable
Cc: mpls@ietf.org
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.3 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Content-Transfer-Encoding: quoted-printable

Eric,
<Snipped>
 
> Not if the downstream router sends a label withdraw as an appropriate
> recovery response to getting a packet with a label that is invalid.

Is there not a possibility that packets might end up at the wrong
destination for other (defect) reasons?  And in such a case sending a
label withdraw seems the wrong action...comments?

regards, Neil


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

v2.23.0 | Report a Bug | By Email