Re: [Idr] draft-uttaro-idr-bgp-persistence-00
"UTTARO, JAMES" <ju1738@att.com> Tue, 01 November 2011 19:26 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 9AB481F0C5C for <idr@ietfa.amsl.com>; Tue, 1 Nov 2011 12:26:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.749
X-Spam-Level:
X-Spam-Status: No, score=-105.749 tagged_above=-999 required=5 tests=[AWL=0.350, BAYES_00=-2.599, GB_ABOUTYOU=0.5, 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 i5zN2danc-xY for <idr@ietfa.amsl.com>; Tue, 1 Nov 2011 12:26:16 -0700 (PDT)
Received: from mail120.messagelabs.com (mail120.messagelabs.com [216.82.250.83]) by ietfa.amsl.com (Postfix) with ESMTP id 1556D1F0C58 for <idr@ietf.org>; Tue, 1 Nov 2011 12:26:16 -0700 (PDT)
X-Env-Sender: ju1738@att.com
X-Msg-Ref: server-7.tower-120.messagelabs.com!1320175489!46955532!1
X-Originating-IP: [144.160.20.145]
X-StarScan-Version: 6.3.6; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 26799 invoked from network); 1 Nov 2011 19:24:50 -0000
Received: from sbcsmtp6.sbc.com (HELO mlpd192.enaf.sfdc.sbc.com) (144.160.20.145) by server-7.tower-120.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 1 Nov 2011 19:24:50 -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 pA1JPG3D017707; Tue, 1 Nov 2011 15:25:17 -0400
Received: from MISOUT7MSGHUB9E.ITServices.sbc.com (misout7msghub9e.itservices.sbc.com [144.151.223.61]) by mlpd192.enaf.sfdc.sbc.com (8.14.4/8.14.4) with ESMTP id pA1JPAOX017547 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 1 Nov 2011 15:25:10 -0400
Received: from MISOUT7MSGUSR9I.ITServices.sbc.com ([169.254.1.231]) by MISOUT7MSGHUB9E.ITServices.sbc.com ([144.151.223.61]) with mapi id 14.01.0339.001; Tue, 1 Nov 2011 15:24:42 -0400
From: "UTTARO, JAMES" <ju1738@att.com>
To: "'robert@raszuk.net'" <robert@raszuk.net>
Thread-Topic: [Idr] draft-uttaro-idr-bgp-persistence-00
Thread-Index: AQHMkEAnLP0iAkRlVkChUYWtkZqOMZWKuQoAgAQhplCAAIdcwoABIPrwgAESmgCABpCw8IAAhjgA///InCA=
Date: Tue, 01 Nov 2011 19:24:41 +0000
Message-ID: <B17A6910EEDD1F45980687268941550FA220C7@MISOUT7MSGUSR9I.ITServices.sbc.com>
References: <4EA1F0FB.3090100@raszuk.net> <4EA487E4.2040201@raszuk.net> <B17A6910EEDD1F45980687268941550FA20750@MISOUT7MSGUSR9I.ITServices.sbc.com> <4EA84254.9000400@raszuk.net> <4EA8A91C.4090305@cisco.com> <B17A6910EEDD1F45980687268941550FA20BB8@MISOUT7MSGUSR9I.ITServices.sbc.com> <4EAA496C.9070605@cisco.com> <B17A6910EEDD1F45980687268941550FA21F96@MISOUT7MSGUSR9I.ITServices.sbc.com> <4EB03BE0.8090504@raszuk.net>
In-Reply-To: <4EB03BE0.8090504@raszuk.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.70.84.170]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "idr@ietf.org List" <idr@ietf.org>
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: Tue, 01 Nov 2011 19:26:16 -0000
Comments In-Line.. Thanks Jim Uttaro -----Original Message----- From: Robert Raszuk [mailto:robert@raszuk.net] Sent: Tuesday, November 01, 2011 2:35 PM To: UTTARO, JAMES Cc: 'Enke Chen'; idr@ietf.org List Subject: Re: [Idr] draft-uttaro-idr-bgp-persistence-00 Jim, > [Jim U>] One ex would be customers who create multiple VPNs over > different SPs.. A customer may want to take advantage of the > knowledge that a control plane failure has occurred and migrate the > traffic to the backup. This could be done at a path granularity by > use of the DO_NOT_PERSIST CV. . We as SPs want to provide our > customers with the tools needed to manage their VPNs and not > prescribe a one size fits all solution. I would recommend not to generalize "We as SPs" requirements as above. [Jim U>] s/'We as SPs'/'As an SP'/ Some SPs may prefer to build their control plane in a robust and multi vendor way for any application they offer to customers in order to prevent from any control plane failures to impact the services. [Jim U>] That may or may not protect you as people architect/design/write code. Other SPs may actually focus on delivering the actual services even during a transient control plane failures they may encounter. I do not think that DO_NOT_PERSIST community is the best way to indicate that peering network is multihomed and that it would prefer the normal BGP withdraw as opposed to receiving STALE routes from their service provider during said service provider encountering a control plane failure. [Jim U>] DO_NOT_PERSIST does not indicate that a network is multi-homed simply allows for a speaker to be informed as to the viability of a control plane. It does allow a peer/speaker/customer to make a decision as to whether or not they want to continue using that network or to migrate away from it in a graceful fashion It is clearly a very new requirement and justification for this proposal to develop a tool in order to communicate to your customers about your network's control plane failures even though data plane and services could continue to be active. With this in mind what is the mechanism build into this tool for your customers to indicate interest is receiving such information ? [Jim U>] ? I do not understand the question.. Best regards, R.
- [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