Re: [Idr] draft-uttaro-idr-bgp-persistence-00
"UTTARO, JAMES" <ju1738@att.com> Mon, 24 October 2011 15:13 UTC
Return-Path: <ju1738@att.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 47F5A21F8E4B for <idr@ietfa.amsl.com>; Mon, 24 Oct 2011 08:13:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level:
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5LOkb-hZCN4a for <idr@ietfa.amsl.com>; Mon, 24 Oct 2011 08:13:11 -0700 (PDT)
Received: from mail120.messagelabs.com (mail120.messagelabs.com [216.82.250.83]) by ietfa.amsl.com (Postfix) with ESMTP id 799B921F8E46 for <idr@ietf.org>; Mon, 24 Oct 2011 08:13:11 -0700 (PDT)
X-Env-Sender: ju1738@att.com
X-Msg-Ref: server-11.tower-120.messagelabs.com!1319469189!45392161!1
X-Originating-IP: [144.160.20.145]
X-StarScan-Version: 6.3.6; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 18686 invoked from network); 24 Oct 2011 15:13:09 -0000
Received: from sbcsmtp6.sbc.com (HELO mlpd192.enaf.sfdc.sbc.com) (144.160.20.145) by server-11.tower-120.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 24 Oct 2011 15:13:09 -0000
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlpd192.enaf.sfdc.sbc.com (8.14.4/8.14.4) with ESMTP id p9OFDZvb005851; Mon, 24 Oct 2011 11:13:36 -0400
Received: from MISOUT7MSGHUB9A.ITServices.sbc.com (misout7msghub9a.itservices.sbc.com [144.151.223.62]) by mlpd192.enaf.sfdc.sbc.com (8.14.4/8.14.4) with ESMTP id p9OFDTKX005655 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 24 Oct 2011 11:13:29 -0400
Received: from MISOUT7MSGUSR9I.ITServices.sbc.com ([169.254.1.231]) by MISOUT7MSGHUB9A.ITServices.sbc.com ([144.151.223.62]) with mapi id 14.01.0339.001; Mon, 24 Oct 2011 11:13:01 -0400
From: "UTTARO, JAMES" <ju1738@att.com>
To: "'robert@raszuk.net'" <robert@raszuk.net>, "idr@ietf.org List" <idr@ietf.org>
Thread-Topic: [Idr] draft-uttaro-idr-bgp-persistence-00
Thread-Index: AQHMkEAnLP0iAkRlVkChUYWtkZqOMZWLmyFg
Date: Mon, 24 Oct 2011 15:13:00 +0000
Message-ID: <B17A6910EEDD1F45980687268941550FA1FBAD@MISOUT7MSGUSR9I.ITServices.sbc.com>
References: <4EA1F0FB.3090100@raszuk.net>
In-Reply-To: <4EA1F0FB.3090100@raszuk.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.91.76.182]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [Idr] draft-uttaro-idr-bgp-persistence-00
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/idr>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Oct 2011 15:13:12 -0000
Robert, Comments In-Line Thanks, Jim Uttaro -----Original Message----- From: idr-bounces@ietf.org [mailto:idr-bounces@ietf.org] On Behalf Of Robert Raszuk Sent: Friday, October 21, 2011 6:24 PM To: idr@ietf.org List Subject: [Idr] draft-uttaro-idr-bgp-persistence-00 Hi, I have read the draft and have one question and one observation. Question: What is the point of defining DO_NOT_PERSIST community ? In other words why not having PERSIST community set would not mean the same as having path marked with DO_NOT_PERSIST. Observation: I found the below statement in section 4.2: o Forwarding must ensure that the Next Hop to a "stale" route is viable. Of course I agree. But since we stating obvious in the forwarding section I think it would be good to explicitly also state this in the best path selection that next hop to STALE best path must be valid. However sessions especially those between loopbacks do not go down for no reason. Most likely there is network problem which may have caused those sessions to go down. It is therefor likely that LDP session went also down between any of the LSRs in the data path and that in spite of having the paths in BGP and next hops in IGP the LSP required for both quoted L2/L3VPN applications is broken. That may particularly happen when network chooses to use independent control mode for label allocation. [Jim U>] Why do you believe that? BGP can and does fail independently of the underlying LDP session.. I do believe that viability of a data path between two endpoints should be taken into account when validating paths to NHs but that effort is clearly a much bigger effort.. This draft would take advantage of this mechanism but I am not looking to define that in this draft.. I would suggest to at least add the recommendation statement to the document that during best path selection especially for stale paths a validity of required forwarding paradigm to next hop of stale paths should be verified. [Jim U>] Why would this not be something that needs to be done as a general rule for paths.. I mean the underlying LSP could fail independently of BGP.. If this needs to be done in should be done as a general rule... For example using techniques as described in: draft-ietf-idr-bgp-bestpath-selection-criteria Best regards, R. _______________________________________________ Idr mailing list Idr@ietf.org https://www.ietf.org/mailman/listinfo/idr
- [Idr] draft-uttaro-idr-bgp-persistence-00 Robert Raszuk
- [Idr] draft-uttaro-idr-bgp-persistence-00 Robert Raszuk
- Re: [Idr] draft-uttaro-idr-bgp-persistence-00 UTTARO, JAMES
- Re: [Idr] draft-uttaro-idr-bgp-persistence-00 Robert Raszuk
- Re: [Idr] draft-uttaro-idr-bgp-persistence-00 UTTARO, JAMES
- Re: [Idr] draft-uttaro-idr-bgp-persistence-00 Robert Raszuk
- Re: [Idr] draft-uttaro-idr-bgp-persistence-00 Enke Chen
- Re: [Idr] draft-uttaro-idr-bgp-persistence-00 UTTARO, JAMES
- Re: [Idr] draft-uttaro-idr-bgp-persistence-00 UTTARO, JAMES
- Re: [Idr] draft-uttaro-idr-bgp-persistence-00 Robert Raszuk
- Re: [Idr] draft-uttaro-idr-bgp-persistence-00 Enke Chen
- Re: [Idr] draft-uttaro-idr-bgp-persistence-00 UTTARO, JAMES
- Re: [Idr] draft-uttaro-idr-bgp-persistence-00 Robert Raszuk
- Re: [Idr] draft-uttaro-idr-bgp-persistence-00 UTTARO, JAMES
- Re: [Idr] draft-uttaro-idr-bgp-persistence-00 bruno.decraene
- Re: [Idr] draft-uttaro-idr-bgp-persistence-00 bruno.decraene
- Re: [Idr] draft-uttaro-idr-bgp-persistence-00 Robert Raszuk
- Re: [Idr] draft-uttaro-idr-bgp-persistence-00 bruno.decraene
- Re: [Idr] draft-uttaro-idr-bgp-persistence-00 Robert Raszuk
- Re: [Idr] draft-uttaro-idr-bgp-persistence-00 bruno.decraene
- Re: [Idr] draft-uttaro-idr-bgp-persistence-00 bruno.decraene
- Re: [Idr] draft-uttaro-idr-bgp-persistence-00 Robert Raszuk
- Re: [Idr] draft-uttaro-idr-bgp-persistence-00 bruno.decraene
- Re: [Idr] draft-uttaro-idr-bgp-persistence-00 bruno.decraene
- Re: [Idr] draft-uttaro-idr-bgp-persistence-00 bruno.decraene
- Re: [Idr] draft-uttaro-idr-bgp-persistence-00 Robert Raszuk
- Re: [Idr] draft-uttaro-idr-bgp-persistence-00 Robert Raszuk
- Re: [Idr] draft-uttaro-idr-bgp-persistence-00 bruno.decraene
- Re: [Idr] draft-uttaro-idr-bgp-persistence-00 Robert Raszuk
- Re: [Idr] draft-uttaro-idr-bgp-persistence-00 UTTARO, JAMES
- Re: [Idr] draft-uttaro-idr-bgp-persistence-00: Se… Jakob Heitz
- Re: [Idr] draft-uttaro-idr-bgp-persistence-00: Se… UTTARO, JAMES
- Re: [Idr] draft-uttaro-idr-bgp-persistence-00: Se… Jakob Heitz
- Re: [Idr] draft-uttaro-idr-bgp-persistence-00: Se… Robert Raszuk
- Re: [Idr] draft-uttaro-idr-bgp-persistence-00: Se… Eric Rosen
- Re: [Idr] draft-uttaro-idr-bgp-persistence-00: Se… Jakob Heitz
- Re: [Idr] draft-uttaro-idr-bgp-persistence-00: Se… Robert Raszuk
- Re: [Idr] draft-uttaro-idr-bgp-persistence-00: Se… Robert Raszuk
- Re: [Idr] draft-uttaro-idr-bgp-persistence-00: Se… bruno.decraene
- Re: [Idr] draft-uttaro-idr-bgp-persistence-00: Se… bruno.decraene
- Re: [Idr] draft-uttaro-idr-bgp-persistence-00 bruno.decraene
- Re: [Idr] draft-uttaro-idr-bgp-persistence-00: Se… Robert Raszuk
- Re: [Idr] draft-uttaro-idr-bgp-persistence-00:Sec… bruno.decraene
- Re: [Idr] draft-uttaro-idr-bgp-persistence-00: Se… Eric Rosen
- Re: [Idr] draft-uttaro-idr-bgp-persistence-00 UTTARO, JAMES
- Re: [Idr] draft-uttaro-idr-bgp-persistence-00 Robert Raszuk
- Re: [Idr] draft-uttaro-idr-bgp-persistence-00 bruno.decraene
- Re: [Idr] draft-uttaro-idr-bgp-persistence-00 bruno.decraene
- Re: [Idr] draft-uttaro-idr-bgp-persistence-00 UTTARO, JAMES
- Re: [Idr] draft-uttaro-idr-bgp-persistence-00 Robert Raszuk
- Re: [Idr] draft-uttaro-idr-bgp-persistence-00 UTTARO, JAMES
- Re: [Idr] draft-uttaro-idr-bgp-persistence-00 Robert Raszuk
- Re: [Idr] draft-uttaro-idr-bgp-persistence-00 Russ White
- Re: [Idr] draft-uttaro-idr-bgp-persistence-00 UTTARO, JAMES
- Re: [Idr] draft-uttaro-idr-bgp-persistence-00 Robert Raszuk
- Re: [Idr] draft-uttaro-idr-bgp-persistence-00 bruno.decraene
- Re: [Idr] draft-uttaro-idr-bgp-persistence-00 Robert Raszuk
- Re: [Idr] draft-uttaro-idr-bgp-persistence-00 bruno.decraene