RE: [mpls] For your review - Issues/errors/clarifications in RFC3 036
neil.2.harrison@bt.com Fri, 08 October 2004 11:04 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 HAA14173; Fri, 8 Oct 2004 07:04:00 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CFshU-0003xs-Lt; Fri, 08 Oct 2004 07:14:16 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CFsWN-0004bY-7H; Fri, 08 Oct 2004 07:02:47 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CFsQX-0003JJ-5a for mpls@megatron.ietf.org; Fri, 08 Oct 2004 06:56:45 -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 GAA13448 for <mpls@ietf.org>; Fri, 8 Oct 2004 06:56:42 -0400 (EDT)
From: neil.2.harrison@bt.com
Received: from smtp5.smtp.bt.com ([217.32.164.139]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CFsaP-0003mi-QQ for mpls@ietf.org; Fri, 08 Oct 2004 07:06:59 -0400
Received: from i2km98-ukbr.domain1.systemhost.net ([193.113.197.85]) by smtp5.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.80); Fri, 8 Oct 2004 11:57:04 +0100
Received: from i2km07-ukbr.domain1.systemhost.net ([193.113.197.26]) by i2km98-ukbr.domain1.systemhost.net with Microsoft SMTPSVC(5.0.2195.6713); Fri, 8 Oct 2004 11:57:04 +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:57:03 +0100
Message-ID: <0536FC9B908BEC4597EE721BE6A353890A9F12EC@i2km07-ukbr.domain1.systemhost.net>
Thread-Topic: [mpls] For your review - Issues/errors/clarifications in RFC3 036
Thread-Index: AcStIqkMBM574I/VRLmNB8nuQnLI3wAAXyzw
To: loa@pi.se
X-OriginalArrivalTime: 08 Oct 2004 10:57:04.0027 (UTC) FILETIME=[8B92DEB0:01C4AD25]
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 67c1ea29f88502ef6a32ccec927970f0
Content-Transfer-Encoding: quoted-printable
Cc: mpls@ietf.org, ewgray@GraIyMage.com
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: 2086112c730e13d5955355df27e3074b
Content-Transfer-Encoding: quoted-printable
Thanks Loa, I think there are 2 separate issues here: - whether the LDP signalling protocol has the right exception handling; - how *any* control-plane protocols should behave in the face of data-plane defects.....and in general it is not a good idea to take actions in the control-plane unless the nature of the defect is understood 1st in the data-plane. That is why I asked the question about issuing a withdraw on getting unexpected labelled pkts. Thanks.....regards, Neil > -----Original Message----- > From: Loa Andersson [mailto:loa@pi.se] > Sent: 08 October 2004 11:33 > To: Harrison,N,Neil,IKR2 R > Cc: ewgray@GraIyMage.com; Nick.Weeds@dataconnection.com; mpls@ietf.org > Subject: Re: [mpls] For your review - > Issues/errors/clarifications in RFC3 036 > > > Neil, > > guess that tht is a fair question, it should be looked into, > but I guess that it is out of scope for an update of the LDP > spec. (I didn't say "implemenation specific :) ). For > communication between LDP peers it is my take that we can > trust TCP, after all that was one of the reasons chosing TCP. > > Now, if the protocol exchange information in a correct > manner, but one implementation creates a label mapping > that is errornous, this is not something we can address > in the protocol specification, is it? > > /Loa > > neil.2.harrison@bt.com wrote: > > > Loa, > > > > I was meaning in general, ie labelled pkts. Just want to check > > nothing is being overlooked here. > > > > regards, Neil > > > > > >>-----Original Message----- > >>From: Loa Andersson [mailto:loa@pi.se] > >>Sent: 08 October 2004 11:19 > >>To: Harrison,N,Neil,IKR2 R > >>Cc: ewgray@GraIyMage.com; Nick.Weeds@dataconnection.com; > mpls@ietf.org > >>Subject: Re: [mpls] For your review - > >>Issues/errors/clarifications in RFC3 036 > >> > >> > >>Neil, > >> > >>are you talking about packets exchange over the TCP > >>connection between two LDP peers, or (labeled) packets in genral? > >> > >>/Loa > >> > >>neil.2.harrison@bt.com wrote: > >> > >>>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 > >>> > >>> > >> > >>-- > >>Loa Andersson > >> > >>Principal Networking Architect > >>Acreo AB phone: +46 8 632 77 14 > >>Isafjordsgatan 22 mobile: +46 739 81 21 64 > >>Kista, Sweden email: loa.andersson@acreo.se > >> loa@pi.se > >> > > > > > > > > -- > Loa Andersson > > Principal Networking Architect > Acreo AB phone: +46 8 632 77 14 > Isafjordsgatan 22 mobile: +46 739 81 21 64 > Kista, Sweden email: loa.andersson@acreo.se > loa@pi.se > _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls
- RE: [mpls] For your review - Issues/errors/clarif… Nick Weeds
- RE: [mpls] For your review - Issues/errors/clarif… Naidu, Venkata
- RE: [mpls] For your review - Issues/errors/clarif… Kishore Tiruveedhula
- RE: [mpls] For your review - Issues/errors/clarif… Ina Minei
- RE: [mpls] For your review - Issues/errors/clarif… Nick Weeds
- Re: [mpls] For your review - Issues/errors/clarif… Eric Gray
- Re: [mpls] For your review - Issues/errors/clarif… Eric Gray
- Re: [mpls] For your review - Issues/errors/clarif… Rama Ramakrishnan
- Re: [mpls] For your review - Issues/errors/clarif… Ina Minei
- RE: [mpls] For your review - Issues/errors/clarif… Ina Minei
- Re: [mpls] For your review - Issues/errors/clarif… Eric Gray
- RE: [mpls] For your review - Issues/errors/clarif… neil.2.harrison
- Re: [mpls] For your review - Issues/errors/clarif… Loa Andersson
- RE: [mpls] For your review - Issues/errors/clarif… neil.2.harrison
- Re: [mpls] For your review - Issues/errors/clarif… Loa Andersson
- RE: [mpls] For your review - Issues/errors/clarif… neil.2.harrison
- Re: [mpls] For your review - Issues/errors/clarif… Rama Ramakrishnan
- Re: [mpls] For your review - Issues/errors/clarif… Eric Gray
- Re: [mpls] For your review - Issues/errors/clarif… Eric Gray