
From robert@raszuk.net  Tue May  1 00:01:50 2012
Return-Path: <robert@raszuk.net>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DF09621F87CD for <grow@ietfa.amsl.com>; Tue,  1 May 2012 00:01:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 S-sVOkz39oCk for <grow@ietfa.amsl.com>; Tue,  1 May 2012 00:01:50 -0700 (PDT)
Received: from mail1310.opentransfer.com (mail1310.opentransfer.com [76.162.254.103]) by ietfa.amsl.com (Postfix) with ESMTP id 0202A21F87CC for <grow@ietf.org>; Tue,  1 May 2012 00:01:49 -0700 (PDT)
Received: (qmail 20383 invoked by uid 399); 1 May 2012 07:01:44 -0000
Received: from unknown (HELO ?192.168.1.57?) (pbs:robert@raszuk.net@83.28.249.78) by mail1310.opentransfer.com with ESMTPM; 1 May 2012 07:01:44 -0000
X-Originating-IP: 83.28.249.78
Message-ID: <4F9F8A55.2050203@raszuk.net>
Date: Tue, 01 May 2012 09:01:41 +0200
From: Robert Raszuk <robert@raszuk.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120420 Thunderbird/12.0
MIME-Version: 1.0
To: Jakob Heitz <jakob.heitz@ericsson.com>
References: <13205C286662DE4387D9AF3AC30EF456D76AB92C3B@EMBX01-WF.jnpr.net> <4F9BCB90.9090000@raszuk.net> <4F9C80BA.9040003@raszuk.net> <13205C286662DE4387D9AF3AC30EF456D76AD2906F@EMBX01-WF.jnpr.net> <4F9DA2A9.7070301@raszuk.net> <13205C286662DE4387D9AF3AC30EF456D76AD29113@EMBX01-WF.jnpr.net> <4F9E27CC.8070507@raszuk.net> <13205C286662DE4387D9AF3AC30EF456D76AD297C7@EMBX01-WF.jnpr.net> <7309FCBCAE981B43ABBE69B31C8D213921BE145B07@EUSAACMS0701.eamcs.ericsson.se> <4F9EEF87.1050504@raszuk.net> <7309FCBCAE981B43ABBE69B31C8D213921BE145CC4@EUSAACMS0701.eamcs.ericsson.se>
In-Reply-To: <7309FCBCAE981B43ABBE69B31C8D213921BE145CC4@EUSAACMS0701.eamcs.ericsson.se>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "grow@ietf.org" <grow@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>
Subject: Re: [GROW] draft-ietf-grow-simple-va
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: robert@raszuk.net
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 May 2012 07:01:51 -0000

> On Monday, April 30, 2012 1:01 PM, Robert Raszuk<mailto:robert@raszuk.net>  wrote:
>
>> Disconnect ! Simple-va does not remove routes from RIB. It suppresses
>> overlapping less specific one.
>
> quote from the draft
> ...suppress certain routes from being installed in RIB and FIB tables.
>
> If they are "suppressed from being installed in RIB"
> then they can't be used to resolve nexthops or to be redistributed.

"certain" is the key there. The default route case is a special case as 
explained in the other email.

For any other suppressed route the resolution result will be the same if 
you are resolving via less specific which by definition will not be 
suppressed.

>> However redistribution of BGP to other protocols is
>> usually not that good of an idea
>
> Redistribution of some selected BGP routes does occur.
> Not just into IGP and LDP, but also into applications.

Sure. That's why you have ability to exclude some routes from 
suppression. In fact you can apply the exact very same policy which does 
redistribution to the function which does the suppression.

Best,
R.

From shtsuchi@cisco.com  Wed May  2 09:47:04 2012
Return-Path: <shtsuchi@cisco.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8290011E8091 for <grow@ietfa.amsl.com>; Wed,  2 May 2012 09:47:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.699
X-Spam-Level: 
X-Spam-Status: No, score=-9.699 tagged_above=-999 required=5 tests=[AWL=0.300,  BAYES_00=-2.599, J_CHICKENPOX_73=0.6, RCVD_IN_DNSWL_HI=-8]
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 yKnmtsQWjCvo for <grow@ietfa.amsl.com>; Wed,  2 May 2012 09:46:52 -0700 (PDT)
Received: from bgl-iport-1.cisco.com (bgl-iport-1.cisco.com [72.163.197.25]) by ietfa.amsl.com (Postfix) with ESMTP id C36F711E8088 for <grow@ietf.org>; Wed,  2 May 2012 09:46:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=shtsuchi@cisco.com; l=4122; q=dns/txt; s=iport; t=1335977212; x=1337186812; h=message-id:date:from:mime-version:to:subject:references: in-reply-to:content-transfer-encoding; bh=vCtq6WhIuOS0C7ULNZm+fARfpRWm83QrFidr7BXNqc4=; b=dKUYmLTDPMpSSd81KMn3AjtvTU8Y7MPyPUsRYY8we511Cp1LrRLAPiKk +l1JXKudo1nsKEGWpU1z6y1xMdnb26cpQoOVm6wNr2NIO+OehCF8rWHFz cPJOcfeIalwP0LzJ9PhzOFkq/OGyZIOZWgv43KVXL9AsR4tmSj/1IxNSA 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhYFAKpkoU9Io8UY/2dsb2JhbABEgx6CT643ggkBAQECAgEBAQ8BDgEnJQoNBAsRBAEBAQEDBRYKAwIJAwIBAgEVKAgHDAYCAQEFCw6HawuOAYx4jREBkweBLIlLDoRogRsEiGKNHIV2hUyDF4FpgneBRgc
X-IronPort-AV: E=Sophos;i="4.75,518,1330905600"; d="scan'208";a="11334690"
Received: from vla196-nat.cisco.com (HELO bgl-core-2.cisco.com) ([72.163.197.24]) by bgl-iport-1.cisco.com with ESMTP; 02 May 2012 16:46:50 +0000
Received: from [10.71.44.85] (tky-shtsuchi-8914.cisco.com [10.71.44.85]) by bgl-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id q42Gkmeu007162; Wed, 2 May 2012 16:46:49 GMT
Message-ID: <4FA164F6.6010409@cisco.com>
Date: Thu, 03 May 2012 01:46:46 +0900
From: Shishio Tsuchiya <shtsuchi@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: rbonica@juniper.net, grow@ietf.org
References: <13205C286662DE4387D9AF3AC30EF456D76AB92C3B@EMBX01-WF.jnpr.net>
In-Reply-To: <13205C286662DE4387D9AF3AC30EF456D76AB92C3B@EMBX01-WF.jnpr.net>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
Subject: Re: [GROW] draft-ietf-grow-simple-va
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 May 2012 16:47:04 -0000

Ron and Grow WG
I posted to janog/apops to get comments of this draft.
I'm not sure why operator does not express his thought to this draft,
but I believe this draft is very important for operators especially in APAC/JAPAN.

I'm always participant to Japanese operators community meeting,
and often there were the topic of internet route growth and capacity of the router on the meeting.
I would like to share with wg the information with my summary.
Dec.2006 IRS11
Kamikawa-san,Energear Communication
http://irs.ietf.to/past/docs_20061211/CEF-kawakami-20061211.pdf (Japanese)
He explained the trouble case which the internet route exceeded than default TCAM size.

Sep.2009 IRS21
Ohkubo-san,Sakura Internet
http://irs.ietf.to/wiki.cgi?action=ATTACH&page=IRS21&file=20090914%2Dirs21%2Dpost%2Epdf (Japanese)
He explained growth of the internet route and utilization of each prefix in his network.
According to his research,there is bias of traffic load,280K prefix was not used with in 290K(full route).

July.2011 JANOG28
Mashiko-san and Yoshimura-san,NTT Communications
http://www.janog.gr.jp/meeting/janog28/doc/janog28-isp-after.pdf (Japanese)
NTT Communications,OCN is the biggest ISP of Japan.
They explained utilization of FIB memory on edge and core routers,and operation of reality.
If the memory would be closed to the limitation,then they replace the router or summarize/filter of the route.
If the filtering was careless,black hole(ping-pong) would occur.

Of course memory lookup speed will improve and the router's capacity is also growing.
But both of IPv4/IPv6 internet route is growing.

I think "draft-ietf-grow-simple-va" can help these operator's issue with minimum cost.

Regards,
-Shishio


(2012/04/26 8:32), Ronald Bonica wrote:
> Folks,
> 
> One week ago, I polled the WG in an attempt to gage interest in draft-ietf-grow-simple. The following responses were posted:
> 
> - http://www.ietf.org/mail-archive/web/grow/current/msg02228.html
> - http://www.ietf.org/mail-archive/web/grow/current/msg02229.html
> 
> While these two messages are not sufficient evidence of wide community interest in this draft, they do suggest that there may be interest out there. So, I will ask the chairs to conduct another WG last call on this draft. In the last call announcement, please ask folks who want the draft to be published to speak up. Silence will be interpreted as disinterest.
> 
> Until the WG last call is complete, I will transition the draft to the AD-WATCHING state.
> 
> Ron
> 
>  > -----Original Message-----
>  > From: Ronald Bonica
>  > Sent: Wednesday, April 18, 2012 3:19 PM
>  > To: grow@ietf.org
>  > Subject: draft-ietf-grow-simple-va
>  >
>  > Folks,
>  >
>  > The WG has recently submitted draft-ietf-grow-simple-va-04 for
>  > publication. As part of my AD review, I looked for discussion of this
>  > draft on the mailing list. Excluding messages from internet-
>  > drafts@ietf.org and the chairs, the following are the only messages
>  > that I see:
>  >
>  > - (Mar-17-2011) http://www.ietf.org/mail-
>  > archive/web/grow/current/msg01851.html
>  > - (Sep-20-2010) http://www.ietf.org/mail-
>  > archive/web/grow/current/msg01748.html
>  > - (Aug-23-2010) http://www.ietf.org/mail-
>  > archive/web/grow/current/msg01726.html
>  > - (Mar-01-2010) http://www.ietf.org/mail-
>  > archive/web/grow/current/msg01618.html
>  >
>  > Given that there has been no discussion of this draft for the last
>  > year, and that there was almost no discussion of this draft before
>  > that, I need to gage the degree to which the WG is still interested in
>  > it.
>  >
>  > Can anyone speak to the level of WG interest in this draft? As this is
>  > an operational WG, I am especially interested in hearing from
>  > operators. However, all views are welcomed.
>  >
>  > --------------------------
>  > Ron Bonica
>  > vcard: www.bonica.org/ron/ronbonica.vcf
>  >
> 
> _______________________________________________
> GROW mailing list
> GROW@ietf.org
> https://www.ietf.org/mailman/listinfo/grow
> 



From internet-drafts@ietf.org  Thu May  3 07:19:20 2012
Return-Path: <internet-drafts@ietf.org>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F85221F85C2; Thu,  3 May 2012 07:19:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.457
X-Spam-Level: 
X-Spam-Status: No, score=-102.457 tagged_above=-999 required=5 tests=[AWL=0.142, BAYES_00=-2.599, 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 5rMNjV1LIIXs; Thu,  3 May 2012 07:19:20 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 22C6D21F8592; Thu,  3 May 2012 07:19:20 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.02
Message-ID: <20120503141920.16694.71483.idtracker@ietfa.amsl.com>
Date: Thu, 03 May 2012 07:19:20 -0700
Cc: grow@ietf.org
Subject: [GROW] I-D Action: draft-ietf-grow-diverse-bgp-path-dist-07.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 May 2012 14:19:20 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies. This draft is a work item of the Global Routing Operations Working Gro=
up of the IETF.

	Title           : Distribution of diverse BGP paths.
	Author(s)       : Robert Raszuk
                          Rex Fernando
                          Keyur Patel
                          Danny McPherson
                          Kenji Kumaki
	Filename        : draft-ietf-grow-diverse-bgp-path-dist-07.txt
	Pages           : 23
	Date            : 2012-05-03

   The BGP4 protocol specifies the selection and propagation of a single
   best path for each prefix.  As defined and widely deployed today BGP
   has no mechanisms to distribute alternate paths which are not
   considered best path between its speakers.  This behaviour results in
   number of disadvantages for new applications and services.

   This document presents an alternative mechanism for solving the
   problem based on the concept of parallel route reflector planes.
   Such planes can be built in parallel or they can co-exist on the
   current route reflection platforms.  Document also compares existing
   solutions and proposed ideas that enable distribution of more paths
   than just the best path.

   This proposal does not specify any changes to the BGP protocol
   definition.  It does not require upgrades to provider edge or core
   routers nor does it need network wide upgrades.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-grow-diverse-bgp-path-dist-0=
7.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-grow-diverse-bgp-path-dist-07=
.txt

The IETF datatracker page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-grow-diverse-bgp-path-dist/


From internet-drafts@ietf.org  Thu May  3 07:23:27 2012
Return-Path: <internet-drafts@ietf.org>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C8AAE21F85CC; Thu,  3 May 2012 07:23:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.469
X-Spam-Level: 
X-Spam-Status: No, score=-102.469 tagged_above=-999 required=5 tests=[AWL=0.130, BAYES_00=-2.599, 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 HDqJqoeTpvX4; Thu,  3 May 2012 07:23:27 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5CFA021F860F; Thu,  3 May 2012 07:23:27 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.02
Message-ID: <20120503142327.17842.97230.idtracker@ietfa.amsl.com>
Date: Thu, 03 May 2012 07:23:27 -0700
Cc: grow@ietf.org
Subject: [GROW] I-D Action: draft-ietf-grow-simple-va-05.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 May 2012 14:23:28 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies. This draft is a work item of the Global Routing Operations Working Gro=
up of the IETF.

	Title           : Simple Virtual Aggregation (S-VA)
	Author(s)       : Robert Raszuk
                          Alton Lo
                          Lixia Zhang
                          Xiaohu Xu
	Filename        : draft-ietf-grow-simple-va-05.txt
	Pages           : 10
	Date            : 2012-05-03

   The continued growth in the Default Free Routing Table (DFRT)
   stresses the global routing system in a number of ways.  One of the
   most costly stresses is FIB size: ISPs often must upgrade router
   hardware simply because the FIB has run out of space, and router
   vendors must design routers that have adequate FIB.

   FIB suppression is an approach to relieving stress on the FIB by NOT
   loading selected RIB entries into the FIB.  Simple Virtual
   Aggregation (S-VA) is a simple form of Virtual Aggregation (VA) that
   allows any and all edge routers to shrink their RIB and FIB
   requirements substantially and therefore increase their useful
   lifetime.

   S-VA does not increase FIB requirements for core routers.  S-VA is
   extremely easy to configure considerably more so than the various
   tricks done today to extend the life of edge routers.  S-VA can be
   deployed autonomously by an ISP (cooperation between ISPs is not
   required), and can co-exist with legacy routers in the ISP.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-grow-simple-va-05.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-grow-simple-va-05.txt

The IETF datatracker page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-grow-simple-va/


From ietfc@btconnect.com  Fri May  4 01:35:38 2012
Return-Path: <ietfc@btconnect.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2A84C21F870A for <grow@ietfa.amsl.com>; Fri,  4 May 2012 01:35:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 sqBiaW1Sk0Rr for <grow@ietfa.amsl.com>; Fri,  4 May 2012 01:35:37 -0700 (PDT)
Received: from va3outboundpool.messaging.microsoft.com (va3ehsobe001.messaging.microsoft.com [216.32.180.11]) by ietfa.amsl.com (Postfix) with ESMTP id EB72F21F8709 for <grow@ietf.org>; Fri,  4 May 2012 01:35:36 -0700 (PDT)
Received: from mail58-va3-R.bigfish.com (10.7.14.244) by VA3EHSOBE004.bigfish.com (10.7.40.24) with Microsoft SMTP Server id 14.1.225.23; Fri, 4 May 2012 08:35:25 +0000
Received: from mail58-va3 (localhost [127.0.0.1])	by mail58-va3-R.bigfish.com (Postfix) with ESMTP id 3E1B03E0099; Fri,  4 May 2012 08:35:25 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.55.224.141; KIP:(null); UIP:(null); IPV:NLI; H:DB3PRD0702HT008.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -35
X-BigFish: PS-35(zzbb2dI9371I936eK542M1432N98dKzz1202hzz1033IL8275bh8275dhz2dh2a8h5a9h668h839hd24h304l)
Received: from mail58-va3 (localhost.localdomain [127.0.0.1]) by mail58-va3 (MessageSwitch) id 1336120523273820_29377; Fri,  4 May 2012 08:35:23 +0000 (UTC)
Received: from VA3EHSMHS025.bigfish.com (unknown [10.7.14.249])	by mail58-va3.bigfish.com (Postfix) with ESMTP id 3121CC01DC; Fri,  4 May 2012 08:35:23 +0000 (UTC)
Received: from DB3PRD0702HT008.eurprd07.prod.outlook.com (157.55.224.141) by VA3EHSMHS025.bigfish.com (10.7.99.35) with Microsoft SMTP Server (TLS) id 14.1.225.23; Fri, 4 May 2012 08:35:22 +0000
Received: from SN2PRD0710HT005.namprd07.prod.outlook.com (157.56.234.149) by pod51017.outlook.com (10.3.4.173) with Microsoft SMTP Server (TLS) id 14.15.74.2; Fri, 4 May 2012 08:35:23 +0000
Message-ID: <009c01cd29c8$306a8e20$4001a8c0@gateway.2wire.net>
From: t.petch <ietfc@btconnect.com>
To: <tkirkham@anthony-kirkham.com>
References: <20120410064953.27574.88075.idtracker@ietfa.amsl.com><4F8F9F9A.8010609@anthony-kirkham.com> <4F9480AE.9030504@inex.ie> <4F9755A3.3090004@anthony-kirkham.com>
Date: Fri, 4 May 2012 09:33:12 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [157.56.234.149]
X-OriginatorOrg: btconnect.com
Cc: grow@ietf.org, grow-chairs@tools.ietf.org
Subject: Re: [GROW] I-D Action: draft-ietf-grow-private-ip-sp-cores-01.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 May 2012 08:35:38 -0000

---- Original Message -----
From: "Anthony Kirkham" <tkirkham@anthony-kirkham.com>
To: "Nick Hilliard" <nick@inex.ie>
Cc: <grow@ietf.org>
Sent: Wednesday, April 25, 2012 3:38 AM

> Thanks Nick, I have incorporated all that feedback. I re-read it and
> fixed a few other instances of poor capitalisation. If there are any
> other nits, please let me know.
>
> The only other issue I can see is an erroneous index which gets created
> by the XML conversion tool. If anyone has any thoughts on how to change
> or remove it, I'd appreciate the advice.

Tony

The index is generated because you have an  <iref ... /> XML element in your
source.  Perhaps <xref... or <eref... was meant (see
http://xml.resource.org/authoring/draft-mrose-writing-rfcs.html
for more information).

That is the easy part.

Getting the I-D to progress, now that is a real challenge, as the recent posts
of Ron Bonica to the GROW list may suggest.

The next step, assuming you see no scope for improvement (and I would leave the
<iref... for the time being), is to ask the Chairs to initiate a Last Call.
There is an e-mail address for the chairs of a WG, which persists as and when
the individuals appointed to the office change, and I have added that to this
reply.

Tom Petch

>
> Tony K
>
>
>
> On 23/04/12 8:05 AM, Nick Hilliard wrote:
> > On 19/04/2012 06:16, Anthony Kirkham wrote:
> >> All,
> >>
> >> I'm very keen to know if we can progress this draft to WGLC? Comments
please?
> > I like the draft and would like to see it moved to WGLC.  No major
> > comments, but a couple of nits:
> >
> > -  weil-shared-transition-space-request is now rfc6598
> > - the last paragraph in section 5 is sloppily worded.
> > - section 11, reword "to using private addressing, Such" to be "to using
> > private addressing; such"
> > - there are a couple of other incorrect capitalisations and instances of
> > incorrectly used punctuation marks.
> >
> > Nick
> >
> >> Tony K
> >>
> >>
> >> On 10/04/12 4:49 PM, internet-drafts@ietf.org wrote:
> >>> A New Internet-Draft is available from the on-line Internet-Drafts
> >>> directories. This draft is a work item of the Global Routing Operations
> >>> Working Group of the IETF.
> >>>
> >>>      Title           : Issues with Private IP Addressing in the Internet
> >>>      Author(s)       : Anthony Kirkham
> >>>      Filename        : draft-ietf-grow-private-ip-sp-cores-01.txt
> >>>      Pages           : 15
> >>>      Date            : 2012-04-09
> >>>
> >>>      The purpose of this document is to provide a discussion of the
> >>>      potential problems of using private, RFC1918, or non-globally-
> >>>      routable addressing within the core of an SP network.  The discussion
> >>>      focuses on link addresses and to a small extent loopback addresses.
> >>>      While many of the issues are well recognised within the ISP
> >>>      community, there appears to be no document that collectively
> >>>      describes the issues.
> >>>
> >>>
> >>> A URL for this Internet-Draft is:
> >>>
http://www.ietf.org/internet-drafts/draft-ietf-grow-private-ip-sp-cores-01.txt
> >>>
> >>>



From christopher.morrow@gmail.com  Fri May  4 08:31:49 2012
Return-Path: <christopher.morrow@gmail.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ADCE321F85D7 for <grow@ietfa.amsl.com>; Fri,  4 May 2012 08:31:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.267
X-Spam-Level: 
X-Spam-Status: No, score=-103.267 tagged_above=-999 required=5 tests=[AWL=-0.268, BAYES_00=-2.599, J_CHICKENPOX_15=0.6, RCVD_IN_DNSWL_LOW=-1, 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 Ukg34cp29Bvz for <grow@ietfa.amsl.com>; Fri,  4 May 2012 08:31:48 -0700 (PDT)
Received: from mail-ob0-f172.google.com (mail-ob0-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id A5F4E21F85D4 for <grow@ietf.org>; Fri,  4 May 2012 08:31:48 -0700 (PDT)
Received: by obbeh20 with SMTP id eh20so4911937obb.31 for <grow@ietf.org>; Fri, 04 May 2012 08:31:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=rmfp/Js+VaSEKRgiXFExY6asBXFnXk+owMy/2vuWkRE=; b=b5jsNlCZ/DUC69hurTVs6ZIZyGuJrUnBruizSfGAAipiTcmFxyBl0tRo0PDD4WqP7E UfDQ9GRFeZdLSXQRWUsr55DJW9OKI1BXQ7jLw9MZbkUJpYfRUOhh9zg4P2UnqmuFlGME FPeToKQjxP8inKBUG77h3kguvrElFqGD9oER6fxBTaiLRXYLAeJRU6mnDNON8DXJ1NBp 2hMeSLgc+Iu2FNb0UVeiPLYI5etWOANQiwbwqz8qjFsyq2pFDb6AQXgIsOZc+nSRyKzN Zd5LaWAO1vFOTSq7MT327wkLJ41zqfGHHiwNUUFkufJrBSpoF21dCMf0xDOkSh5QNoSF 0IdQ==
MIME-Version: 1.0
Received: by 10.182.167.40 with SMTP id zl8mr6927423obb.39.1336145508186; Fri, 04 May 2012 08:31:48 -0700 (PDT)
Received: by 10.182.155.39 with HTTP; Fri, 4 May 2012 08:31:47 -0700 (PDT)
In-Reply-To: <009c01cd29c8$306a8e20$4001a8c0@gateway.2wire.net>
References: <20120410064953.27574.88075.idtracker@ietfa.amsl.com> <4F8F9F9A.8010609@anthony-kirkham.com> <4F9480AE.9030504@inex.ie> <4F9755A3.3090004@anthony-kirkham.com> <009c01cd29c8$306a8e20$4001a8c0@gateway.2wire.net>
Date: Fri, 4 May 2012 11:31:47 -0400
Message-ID: <CAL9jLaZ+=4+pcM-1m-KYKOHmW5B_PR0mdGiJQ_wi0hg02i+-qA@mail.gmail.com>
From: Christopher Morrow <christopher.morrow@gmail.com>
To: "t.petch" <ietfc@btconnect.com>, Nick Hilliard <nick@foobar.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: grow@ietf.org, grow-chairs@tools.ietf.org
Subject: Re: [GROW] I-D Action: draft-ietf-grow-private-ip-sp-cores-01.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 May 2012 15:31:49 -0000

On Fri, May 4, 2012 at 3:33 AM, t.petch <ietfc@btconnect.com> wrote:
> ---- Original Message -----
> From: "Anthony Kirkham" <tkirkham@anthony-kirkham.com>
> To: "Nick Hilliard" <nick@inex.ie>
> Cc: <grow@ietf.org>
> Sent: Wednesday, April 25, 2012 3:38 AM
>
>> Thanks Nick, I have incorporated all that feedback. I re-read it and
>> fixed a few other instances of poor capitalisation. If there are any
>> other nits, please let me know.
>>
>> The only other issue I can see is an erroneous index which gets created
>> by the XML conversion tool. If anyone has any thoughts on how to change
>> or remove it, I'd appreciate the advice.
>
> Tony
>
> The index is generated because you have an =A0<iref ... /> XML element in=
 your
> source. =A0Perhaps <xref... or <eref... was meant (see
> http://xml.resource.org/authoring/draft-mrose-writing-rfcs.html
> for more information).
>
> That is the easy part.
>
> Getting the I-D to progress, now that is a real challenge, as the recent =
posts
> of Ron Bonica to the GROW list may suggest.
>
> The next step, assuming you see no scope for improvement (and I would lea=
ve the
> <iref... for the time being), is to ask the Chairs to initiate a Last Cal=
l.
> There is an e-mail address for the chairs of a WG, which persists as and =
when
> the individuals appointed to the office change, and I have added that to =
this
> reply.

my impression (as a co-chair) was that we were awaiting all local
comments to be completed by Tony (which seems has been done? Nick?)
then we were prepared to WGLC the doc and see where it went from here.

thanks tom!

-chris

> Tom Petch
>
>>
>> Tony K
>>
>>
>>
>> On 23/04/12 8:05 AM, Nick Hilliard wrote:
>> > On 19/04/2012 06:16, Anthony Kirkham wrote:
>> >> All,
>> >>
>> >> I'm very keen to know if we can progress this draft to WGLC? Comments
> please?
>> > I like the draft and would like to see it moved to WGLC. =A0No major
>> > comments, but a couple of nits:
>> >
>> > - =A0weil-shared-transition-space-request is now rfc6598
>> > - the last paragraph in section 5 is sloppily worded.
>> > - section 11, reword "to using private addressing, Such" to be "to usi=
ng
>> > private addressing; such"
>> > - there are a couple of other incorrect capitalisations and instances =
of
>> > incorrectly used punctuation marks.
>> >
>> > Nick
>> >
>> >> Tony K
>> >>
>> >>
>> >> On 10/04/12 4:49 PM, internet-drafts@ietf.org wrote:
>> >>> A New Internet-Draft is available from the on-line Internet-Drafts
>> >>> directories. This draft is a work item of the Global Routing Operati=
ons
>> >>> Working Group of the IETF.
>> >>>
>> >>> =A0 =A0 =A0Title =A0 =A0 =A0 =A0 =A0 : Issues with Private IP Addres=
sing in the Internet
>> >>> =A0 =A0 =A0Author(s) =A0 =A0 =A0 : Anthony Kirkham
>> >>> =A0 =A0 =A0Filename =A0 =A0 =A0 =A0: draft-ietf-grow-private-ip-sp-c=
ores-01.txt
>> >>> =A0 =A0 =A0Pages =A0 =A0 =A0 =A0 =A0 : 15
>> >>> =A0 =A0 =A0Date =A0 =A0 =A0 =A0 =A0 =A0: 2012-04-09
>> >>>
>> >>> =A0 =A0 =A0The purpose of this document is to provide a discussion o=
f the
>> >>> =A0 =A0 =A0potential problems of using private, RFC1918, or non-glob=
ally-
>> >>> =A0 =A0 =A0routable addressing within the core of an SP network. =A0=
The discussion
>> >>> =A0 =A0 =A0focuses on link addresses and to a small extent loopback =
addresses.
>> >>> =A0 =A0 =A0While many of the issues are well recognised within the I=
SP
>> >>> =A0 =A0 =A0community, there appears to be no document that collectiv=
ely
>> >>> =A0 =A0 =A0describes the issues.
>> >>>
>> >>>
>> >>> A URL for this Internet-Draft is:
>> >>>
> http://www.ietf.org/internet-drafts/draft-ietf-grow-private-ip-sp-cores-0=
1.txt
>> >>>
>> >>>
>
>
> _______________________________________________
> GROW mailing list
> GROW@ietf.org
> https://www.ietf.org/mailman/listinfo/grow

From internet-drafts@ietf.org  Mon May  7 04:07:48 2012
Return-Path: <internet-drafts@ietf.org>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C2F821F85BE; Mon,  7 May 2012 04:07:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.466
X-Spam-Level: 
X-Spam-Status: No, score=-102.466 tagged_above=-999 required=5 tests=[AWL=0.133, BAYES_00=-2.599, 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 abKQ3xfzCsag; Mon,  7 May 2012 04:07:43 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0603F21F85B8; Mon,  7 May 2012 04:07:43 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.02
Message-ID: <20120507110743.22713.95954.idtracker@ietfa.amsl.com>
Date: Mon, 07 May 2012 04:07:43 -0700
Cc: grow@ietf.org
Subject: [GROW] I-D Action: draft-ietf-grow-private-ip-sp-cores-03.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 May 2012 11:07:49 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies. This draft is a work item of the Global Routing Operations Working Gro=
up of the IETF.

	Title           : Issues with Private IP Addressing in the Internet
	Author(s)       : Anthony Kirkham
	Filename        : draft-ietf-grow-private-ip-sp-cores-03.txt
	Pages           : 15
	Date            : 2012-05-07

   The purpose of this document is to provide a discussion of the
   potential problems of using private, RFC1918, or non-globally-
   routable addressing within the core of an SP network.  The discussion
   focuses on link addresses and to a small extent loopback addresses.
   While many of the issues are well recognised within the ISP
   community, there appears to be no document that collectively
   describes the issues.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-grow-private-ip-sp-cores-03.=
txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-grow-private-ip-sp-cores-03.t=
xt

The IETF datatracker page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-grow-private-ip-sp-cores/


From jhaas@slice.pfrc.org  Mon May  7 10:58:01 2012
Return-Path: <jhaas@slice.pfrc.org>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2E4AB21F866B for <grow@ietfa.amsl.com>; Mon,  7 May 2012 10:58:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.848
X-Spam-Level: 
X-Spam-Status: No, score=-101.848 tagged_above=-999 required=5 tests=[AWL=0.190, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, SARE_SUB_OBFU_Q1=0.227, 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 CKcBlzt+i+cE for <grow@ietfa.amsl.com>; Mon,  7 May 2012 10:58:00 -0700 (PDT)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id 31B5921F865F for <grow@ietf.org>; Mon,  7 May 2012 10:57:58 -0700 (PDT)
Received: by slice.pfrc.org (Postfix, from userid 1001) id 6C426D0EF; Mon,  7 May 2012 13:57:57 -0400 (EDT)
Date: Mon, 7 May 2012 13:57:57 -0400
From: Jeffrey Haas <jhaas@pfrc.org>
To: Rob Shakir <rjs@rob.sh>
Message-ID: <20120507175757.GB16863@pfrc>
References: <FB4645AC-2540-4152-A1F1-67DC7116D953@rob.sh>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <FB4645AC-2540-4152-A1F1-67DC7116D953@rob.sh>
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: grow@ietf.org
Subject: Re: [GROW] Repeated Errors in BGP - draft-ietf-grow-ops-reqs-for-bgp-error-handling
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 May 2012 17:58:02 -0000

On Fri, Apr 13, 2012 at 07:27:36PM +0100, Rob Shakir wrote:
> I'd like to ask the WG their collective opinion on a couple of matters in this draft, which come from some discussions at IETF83 (in particular with John Scudder and Adam Simpson) about how the requirements are currently written regarding repeated errors.

In reviewing this thread, there's another possible tool we could leverage.
The consensus seems to be trending toward "if the session is bad enough,
take it down.  Potentially hold it down if it continues to be bad."

An alternative before you get to such a stage is to perform BGP graceful
shutdown procedures on the session's routes.  This permits the routes to be
routes of last resort until the issue is dealt with.


-- Jeff

From jakob.heitz@ericsson.com  Tue May  8 18:08:26 2012
Return-Path: <jakob.heitz@ericsson.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BE7A121F8449 for <grow@ietfa.amsl.com>; Tue,  8 May 2012 18:08:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.267
X-Spam-Level: 
X-Spam-Status: No, score=-6.267 tagged_above=-999 required=5 tests=[AWL=0.105,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_SUB_OBFU_Q1=0.227]
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 jmIrusAWuXph for <grow@ietfa.amsl.com>; Tue,  8 May 2012 18:08:26 -0700 (PDT)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.9]) by ietfa.amsl.com (Postfix) with ESMTP id 4256521F8448 for <grow@ietf.org>; Tue,  8 May 2012 18:08:23 -0700 (PDT)
Received: from eusaamw0706.eamcs.ericsson.se ([147.117.20.31]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id q4918Fkg019108; Tue, 8 May 2012 20:08:22 -0500
Received: from EUSAACMS0701.eamcs.ericsson.se ([169.254.1.6]) by eusaamw0706.eamcs.ericsson.se ([147.117.20.31]) with mapi; Tue, 8 May 2012 21:08:16 -0400
From: Jakob Heitz <jakob.heitz@ericsson.com>
To: Jeffrey Haas <jhaas@pfrc.org>, Rob Shakir <rjs@rob.sh>
Date: Tue, 8 May 2012 21:08:11 -0400
Thread-Topic: [GROW] Repeated Errors in BGP - draft-ietf-grow-ops-reqs-for-bgp-error-handling
Thread-Index: Ac0sevtVwqdHRabyQ5qKCLHyToZZswBBBQZQ
Message-ID: <7309FCBCAE981B43ABBE69B31C8D213921BE3142CD@EUSAACMS0701.eamcs.ericsson.se>
References: <FB4645AC-2540-4152-A1F1-67DC7116D953@rob.sh> <20120507175757.GB16863@pfrc>
In-Reply-To: <20120507175757.GB16863@pfrc>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] Repeated Errors in BGP - draft-ietf-grow-ops-reqs-for-bgp-error-handling
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 May 2012 01:08:27 -0000

On Monday, May 07, 2012 10:58 AM, Jeffrey Haas <> wrote:

> On Fri, Apr 13, 2012 at 07:27:36PM +0100, Rob Shakir wrote:
>> I'd like to ask the WG their collective opinion on a couple of
>> matters in this draft, which come from some discussions at IETF83
>> (in particular with John Scudder and Adam Simpson) about how the
>> requirements are currently written regarding repeated errors.  =20
>=20
> In reviewing this thread, there's another possible tool we could
> leverage. The consensus seems to be trending toward "if the session
> is bad enough, take it down.  Potentially hold it down if it
> continues to be bad."=20
>=20
> An alternative before you get to such a stage is to perform BGP
> graceful shutdown procedures on the session's routes.  This permits
> the routes to be routes of last resort until the issue is dealt with.

That raises the possibility that the routes are actually used.
That may cause loops.

--=20
Jakob Heitz.=

From bruno.decraene@orange.com  Wed May  9 00:36:56 2012
Return-Path: <bruno.decraene@orange.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D58121F849A for <grow@ietfa.amsl.com>; Wed,  9 May 2012 00:36:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.566
X-Spam-Level: 
X-Spam-Status: No, score=0.566 tagged_above=-999 required=5 tests=[AWL=0.337,  BAYES_50=0.001, SARE_SUB_OBFU_Q1=0.227, UNPARSEABLE_RELAY=0.001]
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 eHzvJusRFGUY for <grow@ietfa.amsl.com>; Wed,  9 May 2012 00:36:55 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias91.francetelecom.com [193.251.215.91]) by ietfa.amsl.com (Postfix) with ESMTP id 7457721F848F for <grow@ietf.org>; Wed,  9 May 2012 00:36:55 -0700 (PDT)
Received: from omfedm08.si.francetelecom.fr (unknown [xx.xx.xx.4]) by omfedm13.si.francetelecom.fr (ESMTP service) with ESMTP id 3B23A3241D9; Wed,  9 May 2012 09:36:54 +0200 (CEST)
Received: from Exchangemail-eme1.itn.ftgroup (unknown [10.114.1.183]) by omfedm08.si.francetelecom.fr (ESMTP service) with ESMTP id DCF14238055; Wed,  9 May 2012 09:36:53 +0200 (CEST)
Received: from PEXCVZYM11.corporate.adroot.infra.ftgroup ([fe80::a441:e6a9:6143:6f0f]) by PEXCVZYH02.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.02.0247.003; Wed, 9 May 2012 09:36:53 +0200
From: <bruno.decraene@orange.com>
To: Jakob Heitz <jakob.heitz@ericsson.com>
Thread-Topic: [GROW] Repeated Errors in BGP - draft-ietf-grow-ops-reqs-for-bgp-error-handling
Thread-Index: AQHNLHr7pnBj1Hn2qk+EFNE5KcmtL5bAheqAgACMrAA=
Date: Wed, 9 May 2012 07:36:53 +0000
Message-ID: <14189_1336549014_4FAA1E96_14189_965_1_53C29892C857584299CBF5D05346208A0776EC@PEXCVZYM11.corporate.adroot.infra.ftgroup>
References: <FB4645AC-2540-4152-A1F1-67DC7116D953@rob.sh> <20120507175757.GB16863@pfrc> <7309FCBCAE981B43ABBE69B31C8D213921BE3142CD@EUSAACMS0701.eamcs.ericsson.se>
In-Reply-To: <7309FCBCAE981B43ABBE69B31C8D213921BE3142CD@EUSAACMS0701.eamcs.ericsson.se>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.197.38.5]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2012.5.2.131529
Cc: "grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] Repeated Errors in BGP - draft-ietf-grow-ops-reqs-for-bgp-error-handling
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 May 2012 07:36:56 -0000

From: grow Jakob Heitz Sent: Wednesday, May 09, 2012 3:08 AM
>On Monday, May 07, 2012 10:58 AM, Jeffrey Haas <> wrote:
>
>> On Fri, Apr 13, 2012 at 07:27:36PM +0100, Rob Shakir wrote:
>>> I'd like to ask the WG their collective opinion on a couple of
>>> matters in this draft, which come from some discussions at IETF83
>>> (in particular with John Scudder and Adam Simpson) about how the
>>> requirements are currently written regarding repeated errors.
>>
>> In reviewing this thread, there's another possible tool we could
>> leverage. The consensus seems to be trending toward "if the session
>> is bad enough, take it down.  Potentially hold it down if it
>> continues to be bad."
>>
>> An alternative before you get to such a stage is to perform BGP
>> graceful shutdown procedures on the session's routes.  This permits
>> the routes to be routes of last resort until the issue is dealt with.
>
>That raises the possibility that the routes are actually used.
>That may cause loops.

Would you mind sharing an example of such loops following an eBGP session f=
ailure?
That would help me. (Hopefully some others).

Thanks,
Bruno


___________________________________________________________________________=
______________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu=
 ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el=
ectroniques etant susceptibles d'alteration,
France Telecom - Orange decline toute responsabilite si ce message a ete al=
tere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged inf=
ormation that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and dele=
te this message and its attachments.
As emails may be altered, France Telecom - Orange is not liable for message=
s that have been modified, changed or falsified.
Thank you.


From jakob.heitz@ericsson.com  Wed May  9 01:10:13 2012
Return-Path: <jakob.heitz@ericsson.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 02F6F21F85B4 for <grow@ietfa.amsl.com>; Wed,  9 May 2012 01:10:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.272
X-Spam-Level: 
X-Spam-Status: No, score=-6.272 tagged_above=-999 required=5 tests=[AWL=0.100,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_SUB_OBFU_Q1=0.227]
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 ehDW3g3IgAHy for <grow@ietfa.amsl.com>; Wed,  9 May 2012 01:10:07 -0700 (PDT)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.9]) by ietfa.amsl.com (Postfix) with ESMTP id B8EA521F85AC for <grow@ietf.org>; Wed,  9 May 2012 01:10:04 -0700 (PDT)
Received: from eusaamw0707.eamcs.ericsson.se ([147.117.20.32]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id q498A2c3032325; Wed, 9 May 2012 03:10:04 -0500
Received: from EUSAACMS0701.eamcs.ericsson.se ([169.254.1.6]) by eusaamw0707.eamcs.ericsson.se ([147.117.20.32]) with mapi; Wed, 9 May 2012 04:09:57 -0400
From: Jakob Heitz <jakob.heitz@ericsson.com>
To: "bruno.decraene@orange.com" <bruno.decraene@orange.com>
Date: Wed, 9 May 2012 04:09:53 -0400
Thread-Topic: [GROW] Repeated Errors in BGP - draft-ietf-grow-ops-reqs-for-bgp-error-handling
Thread-Index: AQHNLHr7pnBj1Hn2qk+EFNE5KcmtL5bAheqAgACMrACAAAMZcA==
Message-ID: <7309FCBCAE981B43ABBE69B31C8D213921BE314335@EUSAACMS0701.eamcs.ericsson.se>
References: <FB4645AC-2540-4152-A1F1-67DC7116D953@rob.sh> <20120507175757.GB16863@pfrc> <7309FCBCAE981B43ABBE69B31C8D213921BE3142CD@EUSAACMS0701.eamcs.ericsson.se> <14189_1336549014_4FAA1E96_14189_965_1_53C29892C857584299CBF5D05346208A0776EC@PEXCVZYM11.corporate.adroot.infra.ftgroup>
In-Reply-To: <14189_1336549014_4FAA1E96_14189_965_1_53C29892C857584299CBF5D05346208A0776EC@PEXCVZYM11.corporate.adroot.infra.ftgroup>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] Repeated Errors in BGP - draft-ietf-grow-ops-reqs-for-bgp-error-handling
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 May 2012 08:10:13 -0000

A has a route learnt from C.
A configures a long AS path prepend, but because of a bug activated by
a too long AS path, it sends no AS path. B receives it,
but does not withdraw the route. It announces the route to C.
C had a better route before, but due to policy did not
announce it to B. C starts sending traffic to B.
B send to A. A sends to C. loop.

Here is the way:
If you can isolate an error to a set of routes withdraw them.
If not, drop the session and withdraw all routes from it.
RFD takes care of flapping sessions.

On Wednesday, May 09, 2012 12:37 AM, bruno.decraene@orange.com <mailto:brun=
o.decraene@orange.com> wrote:

> From: grow Jakob Heitz Sent: Wednesday, May 09, 2012 3:08 AM
>> On Monday, May 07, 2012 10:58 AM, Jeffrey Haas <> wrote:
>>=20
>>> On Fri, Apr 13, 2012 at 07:27:36PM +0100, Rob Shakir wrote:
>>>> I'd like to ask the WG their collective opinion on a couple of
>>>> matters in this draft, which come from some discussions at IETF83
>>>> (in particular with John Scudder and Adam Simpson) about how the
>>>> requirements are currently written regarding repeated errors.
>>>=20
>>> In reviewing this thread, there's another possible tool we could
>>> leverage. The consensus seems to be trending toward "if the session
>>> is bad enough, take it down.  Potentially hold it down if it
>>> continues to be bad."=20
>>>=20
>>> An alternative before you get to such a stage is to perform BGP
>>> graceful shutdown procedures on the session's routes.  This permits
>>> the routes to be routes of last resort until the issue is dealt
>>> with.=20
>>=20
>> That raises the possibility that the routes are actually used.
>> That may cause loops.
>=20
> Would you mind sharing an example of such loops following an eBGP
> session failure?=20
> That would help me. (Hopefully some others).
>=20
> Thanks,
> Bruno
>=20
>=20
> _________________________________________________________________________=
________________________________________________
>=20
> Ce message et ses pieces jointes peuvent contenir des informations
> confidentielles ou privilegiees et ne doivent donc=20
> pas etre diffuses, exploites ou copies sans autorisation. Si vous
> avez recu ce message par erreur, veuillez le signaler=20
> a l'expediteur et le detruire ainsi que les pieces jointes. Les
> messages electroniques etant susceptibles d'alteration, France
> Telecom - Orange decline toute responsabilite si ce message a ete
> altere, deforme ou falsifie. Merci. =20
>=20
> This message and its attachments may contain confidential or
> privileged information that may be protected by law;=20
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender
> and delete this message and its attachments.=20
> As emails may be altered, France Telecom - Orange is not liable for
> messages that have been modified, changed or falsified. Thank you.



--=20
Jakob Heitz.=

From bruno.decraene@orange.com  Wed May  9 03:11:37 2012
Return-Path: <bruno.decraene@orange.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DFCE321F85C0 for <grow@ietfa.amsl.com>; Wed,  9 May 2012 03:11:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.846
X-Spam-Level: 
X-Spam-Status: No, score=-0.846 tagged_above=-999 required=5 tests=[AWL=1.525,  BAYES_00=-2.599, SARE_SUB_OBFU_Q1=0.227, UNPARSEABLE_RELAY=0.001]
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 8RX-DI9zmLYm for <grow@ietfa.amsl.com>; Wed,  9 May 2012 03:11:37 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias91.francetelecom.com [193.251.215.91]) by ietfa.amsl.com (Postfix) with ESMTP id E50F121F8559 for <grow@ietf.org>; Wed,  9 May 2012 03:11:36 -0700 (PDT)
Received: from omfedm07.si.francetelecom.fr (unknown [xx.xx.xx.3]) by omfedm10.si.francetelecom.fr (ESMTP service) with ESMTP id 39178264362; Wed,  9 May 2012 12:11:36 +0200 (CEST)
Received: from Exchangemail-eme1.itn.ftgroup (unknown [10.114.1.183]) by omfedm07.si.francetelecom.fr (ESMTP service) with ESMTP id 1D6A04C015; Wed,  9 May 2012 12:11:36 +0200 (CEST)
Received: from PEXCVZYM11.corporate.adroot.infra.ftgroup ([fe80::a441:e6a9:6143:6f0f]) by PEXCVZYH02.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.02.0247.003; Wed, 9 May 2012 12:11:35 +0200
From: <bruno.decraene@orange.com>
To: Jakob Heitz <jakob.heitz@ericsson.com>
Thread-Topic: [GROW] Repeated Errors in BGP - draft-ietf-grow-ops-reqs-for-bgp-error-handling
Thread-Index: AQHNLHr7pnBj1Hn2qk+EFNE5KcmtL5bAheqAgACMrACAAAMZcIAAI7Fw
Date: Wed, 9 May 2012 10:11:34 +0000
Message-ID: <22325_1336558296_4FAA42D8_22325_5385_1_53C29892C857584299CBF5D05346208A07806F@PEXCVZYM11.corporate.adroot.infra.ftgroup>
References: <FB4645AC-2540-4152-A1F1-67DC7116D953@rob.sh> <20120507175757.GB16863@pfrc> <7309FCBCAE981B43ABBE69B31C8D213921BE3142CD@EUSAACMS0701.eamcs.ericsson.se> <14189_1336549014_4FAA1E96_14189_965_1_53C29892C857584299CBF5D05346208A0776EC@PEXCVZYM11.corporate.adroot.infra.ftgroup> <7309FCBCAE981B43ABBE69B31C8D213921BE314335@EUSAACMS0701.eamcs.ericsson.se>
In-Reply-To: <7309FCBCAE981B43ABBE69B31C8D213921BE314335@EUSAACMS0701.eamcs.ericsson.se>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.197.38.5]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2012.5.9.91218
Cc: "grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] Repeated Errors in BGP - draft-ietf-grow-ops-reqs-for-bgp-error-handling
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 May 2012 10:11:38 -0000

Jakob,

Thanks for your example.

For sure, if a router (partially) erase the AS PATH, we can have loops. So =
far, I don't see how this is related to BGP error handling, not to mention =
to Jeff proposition.

In more details, is B configured to enforce first AS?=20
 - if so, it should detect the error and react. As per draft-ietf-idr-error=
-handling I guess it should treat as withdraw. I don't see the issue. Or ar=
e you considering a case of two different bugs in two consecutive routers (=
A & B)?
 - if not, well, the loop is the current BGP behavior. Not specific to BGP =
error handling as no router see an error.


Or eventually, we have a different reading of Jeff proposal. I understood t=
hat the proposition is to use as last resort the routes received _before_ t=
he BGP error (i.e. valid routes received through a valid BGP UPDATE but whi=
ch would be implicitly withdrawn with the BGP notification). Not route from=
 the invalid BGP UPDATE.

Regards,
Bruno

>From: Jakob Heitz [mailto:jakob.heitz@ericsson.com] Sent: Wednesday, May 0=
9, 2012 10:10 AM
>
>A has a route learnt from C.
>A configures a long AS path prepend, but because of a bug activated by
>a too long AS path, it sends no AS path. B receives it,
>but does not withdraw the route. It announces the route to C.
>C had a better route before, but due to policy did not
>announce it to B. C starts sending traffic to B.
>B send to A. A sends to C. loop.
>
>Here is the way:
>If you can isolate an error to a set of routes withdraw them.
>If not, drop the session and withdraw all routes from it.
>RFD takes care of flapping sessions.
>
>On Wednesday, May 09, 2012 12:37 AM, bruno.decraene@orange.com
><mailto:bruno.decraene@orange.com> wrote:
>
>> From: grow Jakob Heitz Sent: Wednesday, May 09, 2012 3:08 AM
>>> On Monday, May 07, 2012 10:58 AM, Jeffrey Haas <> wrote:
>>>
>>>> On Fri, Apr 13, 2012 at 07:27:36PM +0100, Rob Shakir wrote:
>>>>> I'd like to ask the WG their collective opinion on a couple of
>>>>> matters in this draft, which come from some discussions at IETF83
>>>>> (in particular with John Scudder and Adam Simpson) about how the
>>>>> requirements are currently written regarding repeated errors.
>>>>
>>>> In reviewing this thread, there's another possible tool we could
>>>> leverage. The consensus seems to be trending toward "if the session
>>>> is bad enough, take it down.  Potentially hold it down if it
>>>> continues to be bad."
>>>>
>>>> An alternative before you get to such a stage is to perform BGP
>>>> graceful shutdown procedures on the session's routes.  This permits
>>>> the routes to be routes of last resort until the issue is dealt
>>>> with.
>>>
>>> That raises the possibility that the routes are actually used.
>>> That may cause loops.
>>
>> Would you mind sharing an example of such loops following an eBGP
>> session failure?
>> That would help me. (Hopefully some others).
>>
>> Thanks,
>> Bruno
>>
>>
>>
>__________________________________________________________________________=
_____
>__________________________________________
>>
>> Ce message et ses pieces jointes peuvent contenir des informations
>> confidentielles ou privilegiees et ne doivent donc
>> pas etre diffuses, exploites ou copies sans autorisation. Si vous
>> avez recu ce message par erreur, veuillez le signaler
>> a l'expediteur et le detruire ainsi que les pieces jointes. Les
>> messages electroniques etant susceptibles d'alteration, France
>> Telecom - Orange decline toute responsabilite si ce message a ete
>> altere, deforme ou falsifie. Merci.
>>
>> This message and its attachments may contain confidential or
>> privileged information that may be protected by law;
>> they should not be distributed, used or copied without authorisation.
>> If you have received this email in error, please notify the sender
>> and delete this message and its attachments.
>> As emails may be altered, France Telecom - Orange is not liable for
>> messages that have been modified, changed or falsified. Thank you.
>
>
>
>--
>Jakob Heitz.

___________________________________________________________________________=
______________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu=
 ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el=
ectroniques etant susceptibles d'alteration,
France Telecom - Orange decline toute responsabilite si ce message a ete al=
tere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged inf=
ormation that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and dele=
te this message and its attachments.
As emails may be altered, France Telecom - Orange is not liable for message=
s that have been modified, changed or falsified.
Thank you.


From jakob.heitz@ericsson.com  Wed May  9 03:42:21 2012
Return-Path: <jakob.heitz@ericsson.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 29EF821F847A for <grow@ietfa.amsl.com>; Wed,  9 May 2012 03:42:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.277
X-Spam-Level: 
X-Spam-Status: No, score=-6.277 tagged_above=-999 required=5 tests=[AWL=0.095,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_SUB_OBFU_Q1=0.227]
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 rq5+vA-ptisk for <grow@ietfa.amsl.com>; Wed,  9 May 2012 03:42:20 -0700 (PDT)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.9]) by ietfa.amsl.com (Postfix) with ESMTP id 6633421F8466 for <grow@ietf.org>; Wed,  9 May 2012 03:42:20 -0700 (PDT)
Received: from eusaamw0706.eamcs.ericsson.se ([147.117.20.31]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id q49AgIwY002883; Wed, 9 May 2012 05:42:19 -0500
Received: from EUSAACMS0701.eamcs.ericsson.se ([169.254.1.6]) by eusaamw0706.eamcs.ericsson.se ([147.117.20.31]) with mapi; Wed, 9 May 2012 06:42:12 -0400
From: Jakob Heitz <jakob.heitz@ericsson.com>
To: "bruno.decraene@orange.com" <bruno.decraene@orange.com>
Date: Wed, 9 May 2012 06:42:07 -0400
Thread-Topic: [GROW] Repeated Errors in BGP - draft-ietf-grow-ops-reqs-for-bgp-error-handling
Thread-Index: AQHNLHr7pnBj1Hn2qk+EFNE5KcmtL5bAheqAgACMrACAAAMZcIAAI7FwgAAJ2/A=
Message-ID: <7309FCBCAE981B43ABBE69B31C8D213921BE314343@EUSAACMS0701.eamcs.ericsson.se>
References: <FB4645AC-2540-4152-A1F1-67DC7116D953@rob.sh> <20120507175757.GB16863@pfrc> <7309FCBCAE981B43ABBE69B31C8D213921BE3142CD@EUSAACMS0701.eamcs.ericsson.se> <14189_1336549014_4FAA1E96_14189_965_1_53C29892C857584299CBF5D05346208A0776EC@PEXCVZYM11.corporate.adroot.infra.ftgroup> <7309FCBCAE981B43ABBE69B31C8D213921BE314335@EUSAACMS0701.eamcs.ericsson.se> <22325_1336558296_4FAA42D8_22325_5385_1_53C29892C857584299CBF5D05346208A07806F@PEXCVZYM11.corporate.adroot.infra.ftgroup>
In-Reply-To: <22325_1336558296_4FAA42D8_22325_5385_1_53C29892C857584299CBF5D05346208A07806F@PEXCVZYM11.corporate.adroot.infra.ftgroup>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] Repeated Errors in BGP - draft-ietf-grow-ops-reqs-for-bgp-error-handling
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 May 2012 10:42:21 -0000

The loop occurs because of an error in the update message:
The AS path was missing. The receiving router "handled"
the error and propagated it.

I just gave you an example of how slippery the error
handling slope can be.

Please don't lose perspective.

Error handling should be simple.

I don't want to trust anything from a buggy router.
However, it has been shown that dropping everything from
a router because of a small bug is too severe.

Therefore, I'm prepared to accept the additional rule:
If an error can be isolated to a set of prefixes,
withdraw only the prefixes, and send an operational message.

Nothing more.

On Wednesday, May 09, 2012 3:12 AM, bruno.decraene@orange.com <mailto:bruno=
.decraene@orange.com> wrote:

> Jakob,
>=20
> Thanks for your example.
>=20
> For sure, if a router (partially) erase the AS PATH, we can have
> loops. So far, I don't see how this is related to BGP error handling,
> not to mention to Jeff proposition. =20
>=20
> In more details, is B configured to enforce first AS?
>  - if so, it should detect the error and react. As per
> draft-ietf-idr-error-handling I guess it should treat as withdraw. I
> don't see the issue. Or are you considering a case of two different
> bugs in two consecutive routers (A & B)?  =20
>  - if not, well, the loop is the current BGP behavior. Not specific
> to BGP error handling as no router see an error.=20
>=20
>=20
> Or eventually, we have a different reading of Jeff proposal. I
> understood that the proposition is to use as last resort the routes
> received _before_ the BGP error (i.e. valid routes received through a
> valid BGP UPDATE but which would be implicitly withdrawn with the BGP
> notification). Not route from the invalid BGP UPDATE.   =20
>=20
> Regards,
> Bruno
>=20
>> From: Jakob Heitz [mailto:jakob.heitz@ericsson.com] Sent: Wednesday,
>> May 09, 2012 10:10 AM=20
>>=20
>> A has a route learnt from C.
>> A configures a long AS path prepend, but because of a bug activated
>> by=20
>> a too long AS path, it sends no AS path. B receives it,
>> but does not withdraw the route. It announces the route to C.
>> C had a better route before, but due to policy did not
>> announce it to B. C starts sending traffic to B.
>> B send to A. A sends to C. loop.
>>=20
>> Here is the way:
>> If you can isolate an error to a set of routes withdraw them.
>> If not, drop the session and withdraw all routes from it.
>> RFD takes care of flapping sessions.
>>=20
>> On Wednesday, May 09, 2012 12:37 AM, bruno.decraene@orange.com
>> <mailto:bruno.decraene@orange.com> wrote:
>>=20
>>> From: grow Jakob Heitz Sent: Wednesday, May 09, 2012 3:08 AM
>>>> On Monday, May 07, 2012 10:58 AM, Jeffrey Haas <> wrote:
>>>>=20
>>>>> On Fri, Apr 13, 2012 at 07:27:36PM +0100, Rob Shakir wrote:
>>>>>> I'd like to ask the WG their collective opinion on a couple of
>>>>>> matters in this draft, which come from some discussions at IETF83
>>>>>> (in particular with John Scudder and Adam Simpson) about how the
>>>>>> requirements are currently written regarding repeated errors.
>>>>>=20
>>>>> In reviewing this thread, there's another possible tool we could
>>>>> leverage. The consensus seems to be trending toward "if the
>>>>> session is bad enough, take it down.  Potentially hold it down if
>>>>> it continues to be bad."=20
>>>>>=20
>>>>> An alternative before you get to such a stage is to perform BGP
>>>>> graceful shutdown procedures on the session's routes.  This
>>>>> permits the routes to be routes of last resort until the issue is
>>>>> dealt with.
>>>>=20
>>>> That raises the possibility that the routes are actually used.
>>>> That may cause loops.
>>>=20
>>> Would you mind sharing an example of such loops following an eBGP
>>> session failure? That would help me. (Hopefully some others).
>>>=20
>>> Thanks,
>>> Bruno
>>>=20
>>>=20
>>>=20
>> ________________________________________________________________________=
_______
>> __________________________________________
>>>=20
>>> Ce message et ses pieces jointes peuvent contenir des informations
>>> confidentielles ou privilegiees et ne doivent donc
>>> pas etre diffuses, exploites ou copies sans autorisation. Si vous
>>> avez recu ce message par erreur, veuillez le signaler
>>> a l'expediteur et le detruire ainsi que les pieces jointes. Les
>>> messages electroniques etant susceptibles d'alteration, France
>>> Telecom - Orange decline toute responsabilite si ce message a ete
>>> altere, deforme ou falsifie. Merci.
>>>=20
>>> This message and its attachments may contain confidential or
>>> privileged information that may be protected by law;
>>> they should not be distributed, used or copied without
>>> authorisation. If you have received this email in error, please
>>> notify the sender and delete this message and its attachments.
>>> As emails may be altered, France Telecom - Orange is not liable for
>>> messages that have been modified, changed or falsified. Thank you.
>>=20
>>=20
>>=20
>> --
>> Jakob Heitz.=

From bruno.decraene@orange.com  Wed May  9 05:31:58 2012
Return-Path: <bruno.decraene@orange.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C934121F8551 for <grow@ietfa.amsl.com>; Wed,  9 May 2012 05:31:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.228
X-Spam-Level: 
X-Spam-Status: No, score=-1.228 tagged_above=-999 required=5 tests=[AWL=1.143,  BAYES_00=-2.599, SARE_SUB_OBFU_Q1=0.227, UNPARSEABLE_RELAY=0.001]
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 ObCppk8BqY2b for <grow@ietfa.amsl.com>; Wed,  9 May 2012 05:31:58 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias91.francetelecom.com [193.251.215.91]) by ietfa.amsl.com (Postfix) with ESMTP id 9B57421F8533 for <grow@ietf.org>; Wed,  9 May 2012 05:31:57 -0700 (PDT)
Received: from omfedm07.si.francetelecom.fr (unknown [xx.xx.xx.3]) by omfedm14.si.francetelecom.fr (ESMTP service) with ESMTP id A46BB22C47D; Wed,  9 May 2012 14:31:56 +0200 (CEST)
Received: from Exchangemail-eme1.itn.ftgroup (unknown [10.114.1.186]) by omfedm07.si.francetelecom.fr (ESMTP service) with ESMTP id 88E324C069; Wed,  9 May 2012 14:31:56 +0200 (CEST)
Received: from PEXCVZYM11.corporate.adroot.infra.ftgroup ([fe80::a441:e6a9:6143:6f0f]) by PEXCVZYH01.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.02.0247.003; Wed, 9 May 2012 14:31:56 +0200
From: <bruno.decraene@orange.com>
To: Jakob Heitz <jakob.heitz@ericsson.com>
Thread-Topic: [GROW] Repeated Errors in BGP - draft-ietf-grow-ops-reqs-for-bgp-error-handling
Thread-Index: AQHNLHr7pnBj1Hn2qk+EFNE5KcmtL5bAheqAgACMrACAAAMZcIAAI7FwgAAJ2/CAABepwA==
Date: Wed, 9 May 2012 12:31:55 +0000
Message-ID: <1962_1336566716_4FAA63BC_1962_1497_1_53C29892C857584299CBF5D05346208A07810F@PEXCVZYM11.corporate.adroot.infra.ftgroup>
References: <FB4645AC-2540-4152-A1F1-67DC7116D953@rob.sh> <20120507175757.GB16863@pfrc> <7309FCBCAE981B43ABBE69B31C8D213921BE3142CD@EUSAACMS0701.eamcs.ericsson.se> <14189_1336549014_4FAA1E96_14189_965_1_53C29892C857584299CBF5D05346208A0776EC@PEXCVZYM11.corporate.adroot.infra.ftgroup> <7309FCBCAE981B43ABBE69B31C8D213921BE314335@EUSAACMS0701.eamcs.ericsson.se> <22325_1336558296_4FAA42D8_22325_5385_1_53C29892C857584299CBF5D05346208A07806F@PEXCVZYM11.corporate.adroot.infra.ftgroup> <7309FCBCAE981B43ABBE69B31C8D213921BE314343@EUSAACMS0701.eamcs.ericsson.se>
In-Reply-To: <7309FCBCAE981B43ABBE69B31C8D213921BE314343@EUSAACMS0701.eamcs.ericsson.se>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.197.38.5]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2012.5.2.131529
Cc: "grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] Repeated Errors in BGP - draft-ietf-grow-ops-reqs-for-bgp-error-handling
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 May 2012 12:31:58 -0000

>From: Jakob Heitz [mailto:jakob.heitz@ericsson.com] Sent: Wednesday, May 0=
9, 2012 12:42 PM
>
>The loop occurs because of an error in the update message:
>The AS path was missing.=20

Well your original text was not that specific. I understood that the AS PAT=
H attribute was present but its length was 0. So no error in the UPDATE rec=
eived.

>The receiving router "handled"
>the error and propagated it.
>
>I just gave you an example of how slippery the error
>handling slope can be.
>
>Please don't lose perspective.
>
>Error handling should be simple.
>
>I don't want to trust anything from a buggy router.

I've heard that argument a few times in the discussion draft-ietf-idr-error=
-handling vs RFC 4271 (current error handling). IMHO it is not a valid one:

A) Note that what you want is not even the current RFC 4271 behavior which =
do accept and do try to correct some error from a buggy router. Including f=
or well know attributes:

e.g. RFC 4271 =A75.1.5 LOCAL_PREF
"A BGP speaker MUST NOT include this attribute in UPDATE messages it
   sends to external peers, except in the case of BGP Confederations
   [RFC3065].  If it is contained in an UPDATE message that is received
   from an external peer, then this attribute MUST be ignored by the
   receiving speaker, except in the case of BGP Confederations
   [RFC3065]."

And idem in RFC 1771:
"  A BGP speaker shall not include this attribute in UPDATE messages
   that it sends to BGP speakers located in a neighboring autonomous
   system. If it is contained in an UPDATE message that is received from
   a BGP speaker which is not located in the same autonomous system as
   the receiving speaker, then this attribute shall be ignored by the
   receiving speaker."


B) See also RFC 1122:
      1.2.2  Robustness Principle

         At every layer of the protocols, there is a general rule whose
         application can lead to enormous benefits in robustness and
         interoperability [IP:1]:

                "Be liberal in what you accept, and
                 conservative in what you send"


>However, it has been shown that dropping everything from
>a router because of a small bug is too severe.
>
>Therefore, I'm prepared to accept the additional rule:
>If an error can be isolated to a set of prefixes,
>withdraw only the prefixes

That would be fine for me. So I don't think we are in real significant disa=
greement.=20

> and send an operational message.

Do you mean that the support of operational message on your BGP peers would=
 be MUST/prerequisite for draft-ietf-idr-error-handling? If so I would disa=
gree. I want to limit the impact of errors regardless of the capabilities o=
f my peers (regardless if my peer is in a different AS or not)

>Nothing more.

That would be ok for me, at least as a first step until we get operational =
experience on the new error handling.

But to come back to the original point, IMHO Jeff proposal seems valid and =
you have not succeeded in proving otherwise.

Thanks,
Regards,
Bruno

>On Wednesday, May 09, 2012 3:12 AM, bruno.decraene@orange.com
><mailto:bruno.decraene@orange.com> wrote:
>
>> Jakob,
>>
>> Thanks for your example.
>>
>> For sure, if a router (partially) erase the AS PATH, we can have
>> loops. So far, I don't see how this is related to BGP error handling,
>> not to mention to Jeff proposition.
>>
>> In more details, is B configured to enforce first AS?
>>  - if so, it should detect the error and react. As per
>> draft-ietf-idr-error-handling I guess it should treat as withdraw. I
>> don't see the issue. Or are you considering a case of two different
>> bugs in two consecutive routers (A & B)?
>>  - if not, well, the loop is the current BGP behavior. Not specific
>> to BGP error handling as no router see an error.
>>
>>
>> Or eventually, we have a different reading of Jeff proposal. I
>> understood that the proposition is to use as last resort the routes
>> received _before_ the BGP error (i.e. valid routes received through a
>> valid BGP UPDATE but which would be implicitly withdrawn with the BGP
>> notification). Not route from the invalid BGP UPDATE.
>>
>> Regards,
>> Bruno
>>
>>> From: Jakob Heitz [mailto:jakob.heitz@ericsson.com] Sent: Wednesday,
>>> May 09, 2012 10:10 AM
>>>
>>> A has a route learnt from C.
>>> A configures a long AS path prepend, but because of a bug activated
>>> by
>>> a too long AS path, it sends no AS path. B receives it,
>>> but does not withdraw the route. It announces the route to C.
>>> C had a better route before, but due to policy did not
>>> announce it to B. C starts sending traffic to B.
>>> B send to A. A sends to C. loop.
>>>
>>> Here is the way:
>>> If you can isolate an error to a set of routes withdraw them.
>>> If not, drop the session and withdraw all routes from it.
>>> RFD takes care of flapping sessions.
>>>
>>> On Wednesday, May 09, 2012 12:37 AM, bruno.decraene@orange.com
>>> <mailto:bruno.decraene@orange.com> wrote:
>>>
>>>> From: grow Jakob Heitz Sent: Wednesday, May 09, 2012 3:08 AM
>>>>> On Monday, May 07, 2012 10:58 AM, Jeffrey Haas <> wrote:
>>>>>
>>>>>> On Fri, Apr 13, 2012 at 07:27:36PM +0100, Rob Shakir wrote:
>>>>>>> I'd like to ask the WG their collective opinion on a couple of
>>>>>>> matters in this draft, which come from some discussions at IETF83
>>>>>>> (in particular with John Scudder and Adam Simpson) about how the
>>>>>>> requirements are currently written regarding repeated errors.
>>>>>>
>>>>>> In reviewing this thread, there's another possible tool we could
>>>>>> leverage. The consensus seems to be trending toward "if the
>>>>>> session is bad enough, take it down.  Potentially hold it down if
>>>>>> it continues to be bad."
>>>>>>
>>>>>> An alternative before you get to such a stage is to perform BGP
>>>>>> graceful shutdown procedures on the session's routes.  This
>>>>>> permits the routes to be routes of last resort until the issue is
>>>>>> dealt with.
>>>>>
>>>>> That raises the possibility that the routes are actually used.
>>>>> That may cause loops.
>>>>
>>>> Would you mind sharing an example of such loops following an eBGP
>>>> session failure? That would help me. (Hopefully some others).
>>>>
>>>> Thanks,
>>>> Bruno
>>>>
>>>>
>>>>
>>>
>__________________________________________________________________________=
_____
>>> __________________________________________
>>>>
>>>> Ce message et ses pieces jointes peuvent contenir des informations
>>>> confidentielles ou privilegiees et ne doivent donc
>>>> pas etre diffuses, exploites ou copies sans autorisation. Si vous
>>>> avez recu ce message par erreur, veuillez le signaler
>>>> a l'expediteur et le detruire ainsi que les pieces jointes. Les
>>>> messages electroniques etant susceptibles d'alteration, France
>>>> Telecom - Orange decline toute responsabilite si ce message a ete
>>>> altere, deforme ou falsifie. Merci.
>>>>
>>>> This message and its attachments may contain confidential or
>>>> privileged information that may be protected by law;
>>>> they should not be distributed, used or copied without
>>>> authorisation. If you have received this email in error, please
>>>> notify the sender and delete this message and its attachments.
>>>> As emails may be altered, France Telecom - Orange is not liable for
>>>> messages that have been modified, changed or falsified. Thank you.
>>>
>>>
>>>
>>> --
>>> Jakob Heitz.

___________________________________________________________________________=
______________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu=
 ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el=
ectroniques etant susceptibles d'alteration,
France Telecom - Orange decline toute responsabilite si ce message a ete al=
tere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged inf=
ormation that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and dele=
te this message and its attachments.
As emails may be altered, France Telecom - Orange is not liable for message=
s that have been modified, changed or falsified.
Thank you.


From jhaas@slice.pfrc.org  Wed May  9 07:57:19 2012
Return-Path: <jhaas@slice.pfrc.org>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4A0B821F845C for <grow@ietfa.amsl.com>; Wed,  9 May 2012 07:57:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.881
X-Spam-Level: 
X-Spam-Status: No, score=-101.881 tagged_above=-999 required=5 tests=[AWL=0.157, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, SARE_SUB_OBFU_Q1=0.227, 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 14cFeI+-r2dV for <grow@ietfa.amsl.com>; Wed,  9 May 2012 07:57:18 -0700 (PDT)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id 83B5E21F844A for <grow@ietf.org>; Wed,  9 May 2012 07:57:17 -0700 (PDT)
Received: by slice.pfrc.org (Postfix, from userid 1001) id 24E66D02B; Wed,  9 May 2012 10:57:17 -0400 (EDT)
Date: Wed, 9 May 2012 10:57:17 -0400
From: Jeffrey Haas <jhaas@pfrc.org>
To: Jakob Heitz <jakob.heitz@ericsson.com>
Message-ID: <20120509145717.GN16863@pfrc>
References: <FB4645AC-2540-4152-A1F1-67DC7116D953@rob.sh> <20120507175757.GB16863@pfrc> <7309FCBCAE981B43ABBE69B31C8D213921BE3142CD@EUSAACMS0701.eamcs.ericsson.se>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <7309FCBCAE981B43ABBE69B31C8D213921BE3142CD@EUSAACMS0701.eamcs.ericsson.se>
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: "grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] Repeated Errors in BGP - draft-ietf-grow-ops-reqs-for-bgp-error-handling
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 May 2012 14:57:19 -0000

On Tue, May 08, 2012 at 09:08:11PM -0400, Jakob Heitz wrote:
> On Monday, May 07, 2012 10:58 AM, Jeffrey Haas <> wrote:
> > An alternative before you get to such a stage is to perform BGP
> > graceful shutdown procedures on the session's routes.  This permits
> > the routes to be routes of last resort until the issue is dealt with.
> 
> That raises the possibility that the routes are actually used.
> That may cause loops.

I'm not talking about the routes we'd be doing "treat as withdraw", I'm
talking about all of the otherwise "good" routes on the session.

-- Jeff

From jakob.heitz@ericsson.com  Wed May  9 08:03:55 2012
Return-Path: <jakob.heitz@ericsson.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AF17911E809C for <grow@ietfa.amsl.com>; Wed,  9 May 2012 08:03:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.282
X-Spam-Level: 
X-Spam-Status: No, score=-6.282 tagged_above=-999 required=5 tests=[AWL=0.090,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_SUB_OBFU_Q1=0.227]
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 w8rVSHoWcSp4 for <grow@ietfa.amsl.com>; Wed,  9 May 2012 08:03:55 -0700 (PDT)
Received: from imr3.ericy.com (imr3.ericy.com [198.24.6.13]) by ietfa.amsl.com (Postfix) with ESMTP id 0F5C011E8091 for <grow@ietf.org>; Wed,  9 May 2012 08:03:55 -0700 (PDT)
Received: from eusaamw0706.eamcs.ericsson.se ([147.117.20.31]) by imr3.ericy.com (8.13.8/8.13.8) with ESMTP id q49F3rev001092 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 9 May 2012 10:03:54 -0500
Received: from EUSAACMS0701.eamcs.ericsson.se ([169.254.1.6]) by eusaamw0706.eamcs.ericsson.se ([147.117.20.31]) with mapi; Wed, 9 May 2012 11:03:53 -0400
From: Jakob Heitz <jakob.heitz@ericsson.com>
To: Jeffrey Haas <jhaas@pfrc.org>
Date: Wed, 9 May 2012 11:03:50 -0400
Thread-Topic: [GROW] Repeated Errors in BGP - draft-ietf-grow-ops-reqs-for-bgp-error-handling
Thread-Index: Ac0t9BS2GbmQyqY0Qi+OPvUQstQ17AAADaPg
Message-ID: <7309FCBCAE981B43ABBE69B31C8D213921BE3144F0@EUSAACMS0701.eamcs.ericsson.se>
References: <FB4645AC-2540-4152-A1F1-67DC7116D953@rob.sh> <20120507175757.GB16863@pfrc> <7309FCBCAE981B43ABBE69B31C8D213921BE3142CD@EUSAACMS0701.eamcs.ericsson.se> <20120509145717.GN16863@pfrc>
In-Reply-To: <20120509145717.GN16863@pfrc>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] Repeated Errors in BGP - draft-ietf-grow-ops-reqs-for-bgp-error-handling
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 May 2012 15:03:56 -0000

On Wednesday, May 09, 2012 7:57 AM, Jeffrey Haas <mailto:jhaas@pfrc.org> wr=
ote:

> On Tue, May 08, 2012 at 09:08:11PM -0400, Jakob Heitz wrote:
>> On Monday, May 07, 2012 10:58 AM, Jeffrey Haas <> wrote:
>>> An alternative before you get to such a stage is to perform BGP
>>> graceful shutdown procedures on the session's routes.  This permits
>>> the routes to be routes of last resort until the issue is dealt
>>> with.=20
>>=20
>> That raises the possibility that the routes are actually used.
>> That may cause loops.
>=20
> I'm not talking about the routes we'd be doing "treat as withdraw",
> I'm=20
> talking about all of the otherwise "good" routes on the session.
>=20
> -- Jeff

Sorry, I misunderstood.

You mean for the case when a router does "treat as withdraw" for
routes in an errored update message, but does not bring down
the session, to deprefer the rest of the routes from that peer.

Right?

--=20
Jakob Heitz.=

From jhaas@slice.pfrc.org  Wed May  9 11:21:09 2012
Return-Path: <jhaas@slice.pfrc.org>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CF92411E80AB for <grow@ietfa.amsl.com>; Wed,  9 May 2012 11:21:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.891
X-Spam-Level: 
X-Spam-Status: No, score=-101.891 tagged_above=-999 required=5 tests=[AWL=0.147, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, SARE_SUB_OBFU_Q1=0.227, 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 I6tX4mUP6aYH for <grow@ietfa.amsl.com>; Wed,  9 May 2012 11:21:07 -0700 (PDT)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id 079DE11E80C4 for <grow@ietf.org>; Wed,  9 May 2012 11:21:06 -0700 (PDT)
Received: by slice.pfrc.org (Postfix, from userid 1001) id 22779D02B; Wed,  9 May 2012 14:21:03 -0400 (EDT)
Date: Wed, 9 May 2012 14:21:03 -0400
From: Jeffrey Haas <jhaas@pfrc.org>
To: Jakob Heitz <jakob.heitz@ericsson.com>
Message-ID: <20120509182103.GO16863@pfrc>
References: <FB4645AC-2540-4152-A1F1-67DC7116D953@rob.sh> <20120507175757.GB16863@pfrc> <7309FCBCAE981B43ABBE69B31C8D213921BE3142CD@EUSAACMS0701.eamcs.ericsson.se> <20120509145717.GN16863@pfrc> <7309FCBCAE981B43ABBE69B31C8D213921BE3144F0@EUSAACMS0701.eamcs.ericsson.se>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <7309FCBCAE981B43ABBE69B31C8D213921BE3144F0@EUSAACMS0701.eamcs.ericsson.se>
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: "grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] Repeated Errors in BGP - draft-ietf-grow-ops-reqs-for-bgp-error-handling
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 May 2012 18:21:09 -0000

On Wed, May 09, 2012 at 11:03:50AM -0400, Jakob Heitz wrote:
> You mean for the case when a router does "treat as withdraw" for
> routes in an errored update message, but does not bring down
> the session, to deprefer the rest of the routes from that peer.
> 
> Right?

Correct.

The topic this thread was covering was "what do we do when we receive a very
large number of faulty updates".  If a session gets a few bad updates, it's
reasonable to expect that a few "bad routes" got into the Internet's table.
If we get a very large number, it may be safer to assume that something is
very broken upstream.

When we've decided the upstream is broken enough, for some threshold of
broken, two reasonable actions are:
- Bring down the peering session.  
- Exercise "graceful shutdown" on that session to permit its routes to be 
  used as a path of last resort.  In this case, we perhaps do not take the
  session down.

The faulty routes are always handled according to the error-handling draft
semantics.

-- Jeff

From tony.li@tony.li  Wed May  9 11:31:42 2012
Return-Path: <tony.li@tony.li>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3DAB111E80C2 for <grow@ietfa.amsl.com>; Wed,  9 May 2012 11:31:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.372
X-Spam-Level: 
X-Spam-Status: No, score=-102.372 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SARE_SUB_OBFU_Q1=0.227, 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 hRBS9z24+6mw for <grow@ietfa.amsl.com>; Wed,  9 May 2012 11:31:41 -0700 (PDT)
Received: from qmta01.westchester.pa.mail.comcast.net (qmta02.westchester.pa.mail.comcast.net [76.96.62.24]) by ietfa.amsl.com (Postfix) with ESMTP id B232D11E8081 for <grow@ietf.org>; Wed,  9 May 2012 11:31:41 -0700 (PDT)
Received: from omta23.westchester.pa.mail.comcast.net ([76.96.62.74]) by qmta01.westchester.pa.mail.comcast.net with comcast id 7uAv1j0041c6gX851uXiSX; Wed, 09 May 2012 18:31:42 +0000
Received: from dhcp-64-101-233-216.cisco.com ([64.101.233.216]) by omta23.westchester.pa.mail.comcast.net with comcast id 7uXP1j0054go1nk3juXVHt; Wed, 09 May 2012 18:31:38 +0000
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=us-ascii
From: Tony Li <tony.li@tony.li>
In-Reply-To: <20120509182103.GO16863@pfrc>
Date: Wed, 9 May 2012 13:31:21 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <B3935C8B-8DF7-4A97-8C71-3564D4FEA05B@tony.li>
References: <FB4645AC-2540-4152-A1F1-67DC7116D953@rob.sh> <20120507175757.GB16863@pfrc> <7309FCBCAE981B43ABBE69B31C8D213921BE3142CD@EUSAACMS0701.eamcs.ericsson.se> <20120509145717.GN16863@pfrc> <7309FCBCAE981B43ABBE69B31C8D213921BE3144F0@EUSAACMS0701.eamcs.ericsson.se> <20120509182103.GO16863@pfrc>
To: Jeffrey Haas <jhaas@pfrc.org>
X-Mailer: Apple Mail (2.1257)
Cc: "grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] Repeated Errors in BGP - draft-ietf-grow-ops-reqs-for-bgp-error-handling
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 May 2012 18:31:42 -0000

On May 9, 2012, at 1:21 PM, Jeffrey Haas wrote:

> - Exercise "graceful shutdown" on that session to permit its routes to =
be=20
>  used as a path of last resort.  In this case, we perhaps do not take =
the
>  session down.
>=20
> The faulty routes are always handled according to the error-handling =
draft
> semantics.


Jeff,

One clarification: by "graceful shutdown" are you implying the use of =
"graceful restart"?

Tony


From jhaas@slice.pfrc.org  Wed May  9 11:45:47 2012
Return-Path: <jhaas@slice.pfrc.org>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 03C8C21F8567 for <grow@ietfa.amsl.com>; Wed,  9 May 2012 11:45:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.899
X-Spam-Level: 
X-Spam-Status: No, score=-101.899 tagged_above=-999 required=5 tests=[AWL=0.139, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, SARE_SUB_OBFU_Q1=0.227, 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 QVrS+IWAhppr for <grow@ietfa.amsl.com>; Wed,  9 May 2012 11:45:46 -0700 (PDT)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id E69DC21F8566 for <grow@ietf.org>; Wed,  9 May 2012 11:45:37 -0700 (PDT)
Received: by slice.pfrc.org (Postfix, from userid 1001) id 9CF7DCFD9; Wed,  9 May 2012 14:45:36 -0400 (EDT)
Date: Wed, 9 May 2012 14:45:36 -0400
From: Jeffrey Haas <jhaas@pfrc.org>
To: Tony Li <tony.li@tony.li>
Message-ID: <20120509184536.GP16863@pfrc>
References: <FB4645AC-2540-4152-A1F1-67DC7116D953@rob.sh> <20120507175757.GB16863@pfrc> <7309FCBCAE981B43ABBE69B31C8D213921BE3142CD@EUSAACMS0701.eamcs.ericsson.se> <20120509145717.GN16863@pfrc> <7309FCBCAE981B43ABBE69B31C8D213921BE3144F0@EUSAACMS0701.eamcs.ericsson.se> <20120509182103.GO16863@pfrc> <B3935C8B-8DF7-4A97-8C71-3564D4FEA05B@tony.li>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <B3935C8B-8DF7-4A97-8C71-3564D4FEA05B@tony.li>
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: "grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] Repeated Errors in BGP - draft-ietf-grow-ops-reqs-for-bgp-error-handling
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 May 2012 18:45:47 -0000

Tony,

On Wed, May 09, 2012 at 01:31:21PM -0500, Tony Li wrote:
> One clarification: by "graceful shutdown" are you implying the use of "graceful restart"?

http://tools.ietf.org/html/draft-ietf-grow-bgp-gshut-03

> Tony

From tony.li@tony.li  Wed May  9 12:12:21 2012
Return-Path: <tony.li@tony.li>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A182111E8081 for <grow@ietfa.amsl.com>; Wed,  9 May 2012 12:12:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.372
X-Spam-Level: 
X-Spam-Status: No, score=-102.372 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SARE_SUB_OBFU_Q1=0.227, 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 juMTUZ7mBJ8Z for <grow@ietfa.amsl.com>; Wed,  9 May 2012 12:12:21 -0700 (PDT)
Received: from qmta08.emeryville.ca.mail.comcast.net (qmta08.emeryville.ca.mail.comcast.net [76.96.30.80]) by ietfa.amsl.com (Postfix) with ESMTP id 378A211E80CA for <grow@ietf.org>; Wed,  9 May 2012 12:12:20 -0700 (PDT)
Received: from omta03.emeryville.ca.mail.comcast.net ([76.96.30.27]) by qmta08.emeryville.ca.mail.comcast.net with comcast id 7v5i1j0080b6N64A8vCL8i; Wed, 09 May 2012 19:12:20 +0000
Received: from dhcp-64-101-233-216.cisco.com ([64.101.233.216]) by omta03.emeryville.ca.mail.comcast.net with comcast id 7vC61j00n4go1nk8PvC9vh; Wed, 09 May 2012 19:12:18 +0000
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=us-ascii
From: Tony Li <tony.li@tony.li>
In-Reply-To: <20120509184536.GP16863@pfrc>
Date: Wed, 9 May 2012 14:12:05 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <BD4ED6BA-0C3F-4E22-908E-94D95C45FCAE@tony.li>
References: <FB4645AC-2540-4152-A1F1-67DC7116D953@rob.sh> <20120507175757.GB16863@pfrc> <7309FCBCAE981B43ABBE69B31C8D213921BE3142CD@EUSAACMS0701.eamcs.ericsson.se> <20120509145717.GN16863@pfrc> <7309FCBCAE981B43ABBE69B31C8D213921BE3144F0@EUSAACMS0701.eamcs.ericsson.se> <20120509182103.GO16863@pfrc> <B3935C8B-8DF7-4A97-8C71-3564D4FEA05B@tony.li> <20120509184536.GP16863@pfrc>
To: Jeffrey Haas <jhaas@pfrc.org>
X-Mailer: Apple Mail (2.1257)
Cc: "grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] Repeated Errors in BGP - draft-ietf-grow-ops-reqs-for-bgp-error-handling
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 May 2012 19:12:21 -0000

On May 9, 2012, at 1:45 PM, Jeffrey Haas wrote:

> Tony,
>=20
> On Wed, May 09, 2012 at 01:31:21PM -0500, Tony Li wrote:
>> One clarification: by "graceful shutdown" are you implying the use of =
"graceful restart"?
>=20
> http://tools.ietf.org/html/draft-ietf-grow-bgp-gshut-03


Thank you.  This seems to indicate that after a g-shut event, the =
neighbor would continue to advertise the prefixes to its peers (albeit =
tagged with the community).  Wouldn't this cause non-updated routers to =
blackhole traffic?  What happens when only half of you IBGP peers are =
updated?

If the peering doesn't come back for an extended period, couldn't this =
cause traffic to transit and then be blackholed, assuming there are no =
alternate paths?

This is violating BGP's fundamental principle: "Advertise what you're =
using, use what you advertise."  It seems like black holes are =
inevitable.

Tony



From jhaas@slice.pfrc.org  Wed May  9 13:29:03 2012
Return-Path: <jhaas@slice.pfrc.org>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C982311E80C8 for <grow@ietfa.amsl.com>; Wed,  9 May 2012 13:29:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.907
X-Spam-Level: 
X-Spam-Status: No, score=-101.907 tagged_above=-999 required=5 tests=[AWL=0.131, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, SARE_SUB_OBFU_Q1=0.227, 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 eve4u0ZWa7Vf for <grow@ietfa.amsl.com>; Wed,  9 May 2012 13:29:03 -0700 (PDT)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id 6CC9211E80CA for <grow@ietf.org>; Wed,  9 May 2012 13:29:03 -0700 (PDT)
Received: by slice.pfrc.org (Postfix, from userid 1001) id 207F3CFD9; Wed,  9 May 2012 16:29:03 -0400 (EDT)
Date: Wed, 9 May 2012 16:29:03 -0400
From: Jeffrey Haas <jhaas@pfrc.org>
To: Tony Li <tony.li@tony.li>
Message-ID: <20120509202903.GQ16863@pfrc>
References: <FB4645AC-2540-4152-A1F1-67DC7116D953@rob.sh> <20120507175757.GB16863@pfrc> <7309FCBCAE981B43ABBE69B31C8D213921BE3142CD@EUSAACMS0701.eamcs.ericsson.se> <20120509145717.GN16863@pfrc> <7309FCBCAE981B43ABBE69B31C8D213921BE3144F0@EUSAACMS0701.eamcs.ericsson.se> <20120509182103.GO16863@pfrc> <B3935C8B-8DF7-4A97-8C71-3564D4FEA05B@tony.li> <20120509184536.GP16863@pfrc> <BD4ED6BA-0C3F-4E22-908E-94D95C45FCAE@tony.li>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <BD4ED6BA-0C3F-4E22-908E-94D95C45FCAE@tony.li>
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: "grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] Repeated Errors in BGP - draft-ietf-grow-ops-reqs-for-bgp-error-handling
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 May 2012 20:29:03 -0000

Tony,

On Wed, May 09, 2012 at 02:12:05PM -0500, Tony Li wrote:
> 
> On May 9, 2012, at 1:45 PM, Jeffrey Haas wrote:
> 
> > Tony,
> > 
> > On Wed, May 09, 2012 at 01:31:21PM -0500, Tony Li wrote:
> >> One clarification: by "graceful shutdown" are you implying the use of "graceful restart"?
> > 
> > http://tools.ietf.org/html/draft-ietf-grow-bgp-gshut-03
> 
> 
> Thank you.  This seems to indicate that after a g-shut event, the neighbor would continue to advertise the prefixes to its peers (albeit tagged with the community).  Wouldn't this cause non-updated routers to blackhole traffic?  What happens when only half of you IBGP peers are updated?
> 
> If the peering doesn't come back for an extended period, couldn't this cause traffic to transit and then be blackholed, assuming there are no alternate paths?
> 
> This is violating BGP's fundamental principle: "Advertise what you're using, use what you advertise."  It seems like black holes are inevitable.

Please see the other clarification I posted.  Graceful shutdown is applied
to the routes from the peer that is sending bad updates that are accepted
and valid.  Routes that contain errors are processed with the stated "treat
as withdraw" behavior.

In other words, the goal is to remove the bad neighbor's valid routes from
the forwarding path as much as possible since that neighbor is presumed to
possibly crazy.

-- Jeff

From tony.li@tony.li  Wed May  9 13:33:07 2012
Return-Path: <tony.li@tony.li>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E59F111E80C8 for <grow@ietfa.amsl.com>; Wed,  9 May 2012 13:33:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.372
X-Spam-Level: 
X-Spam-Status: No, score=-102.372 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SARE_SUB_OBFU_Q1=0.227, 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 zvxRjmXM1QmI for <grow@ietfa.amsl.com>; Wed,  9 May 2012 13:33:07 -0700 (PDT)
Received: from qmta04.emeryville.ca.mail.comcast.net (qmta04.emeryville.ca.mail.comcast.net [76.96.30.40]) by ietfa.amsl.com (Postfix) with ESMTP id 7498511E80BB for <grow@ietf.org>; Wed,  9 May 2012 13:33:07 -0700 (PDT)
Received: from omta02.emeryville.ca.mail.comcast.net ([76.96.30.19]) by qmta04.emeryville.ca.mail.comcast.net with comcast id 7wPz1j0030QkzPwA4wZ7sc; Wed, 09 May 2012 20:33:07 +0000
Received: from dhcp-64-101-233-216.cisco.com ([64.101.233.216]) by omta02.emeryville.ca.mail.comcast.net with comcast id 7wYt1j00H4go1nk8NwYvmA; Wed, 09 May 2012 20:33:05 +0000
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=us-ascii
From: Tony Li <tony.li@tony.li>
In-Reply-To: <20120509202903.GQ16863@pfrc>
Date: Wed, 9 May 2012 15:32:52 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <FC814643-BB29-4C1B-A3E0-40840F786BFA@tony.li>
References: <FB4645AC-2540-4152-A1F1-67DC7116D953@rob.sh> <20120507175757.GB16863@pfrc> <7309FCBCAE981B43ABBE69B31C8D213921BE3142CD@EUSAACMS0701.eamcs.ericsson.se> <20120509145717.GN16863@pfrc> <7309FCBCAE981B43ABBE69B31C8D213921BE3144F0@EUSAACMS0701.eamcs.ericsson.se> <20120509182103.GO16863@pfrc> <B3935C8B-8DF7-4A97-8C71-3564D4FEA05B@tony.li> <20120509184536.GP16863@pfrc> <BD4ED6BA-0C3F-4E22-908E-94D95C45FCAE@tony.li> <20120509202903.GQ16863@pfrc>
To: Jeffrey Haas <jhaas@pfrc.org>
X-Mailer: Apple Mail (2.1257)
Cc: "grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] Repeated Errors in BGP - draft-ietf-grow-ops-reqs-for-bgp-error-handling
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 May 2012 20:33:08 -0000

On May 9, 2012, at 3:29 PM, Jeffrey Haas wrote:

>> Thank you.  This seems to indicate that after a g-shut event, the =
neighbor would continue to advertise the prefixes to its peers (albeit =
tagged with the community).  Wouldn't this cause non-updated routers to =
blackhole traffic?  What happens when only half of you IBGP peers are =
updated?
>>=20
>> If the peering doesn't come back for an extended period, couldn't =
this cause traffic to transit and then be blackholed, assuming there are =
no alternate paths?
>>=20
>> This is violating BGP's fundamental principle: "Advertise what you're =
using, use what you advertise."  It seems like black holes are =
inevitable.
>=20
> Please see the other clarification I posted.  Graceful shutdown is =
applied
> to the routes from the peer that is sending bad updates that are =
accepted
> and valid.  Routes that contain errors are processed with the stated =
"treat
> as withdraw" behavior.
>=20
> In other words, the goal is to remove the bad neighbor's valid routes =
from
> the forwarding path as much as possible since that neighbor is =
presumed to
> possibly crazy.


Jeff,

Understood.  I have no issues with withdrawn routes.  The issue is with =
g-shut routes that continue to sink traffic.

Tony


From jhaas@slice.pfrc.org  Wed May  9 13:51:07 2012
Return-Path: <jhaas@slice.pfrc.org>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D60A411E80CA for <grow@ietfa.amsl.com>; Wed,  9 May 2012 13:51:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.914
X-Spam-Level: 
X-Spam-Status: No, score=-101.914 tagged_above=-999 required=5 tests=[AWL=0.124, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, SARE_SUB_OBFU_Q1=0.227, 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 9fWN+ky1BiFQ for <grow@ietfa.amsl.com>; Wed,  9 May 2012 13:51:04 -0700 (PDT)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id 450B011E8080 for <grow@ietf.org>; Wed,  9 May 2012 13:51:03 -0700 (PDT)
Received: by slice.pfrc.org (Postfix, from userid 1001) id 09615CFD9; Wed,  9 May 2012 16:51:03 -0400 (EDT)
Date: Wed, 9 May 2012 16:51:03 -0400
From: Jeffrey Haas <jhaas@pfrc.org>
To: Tony Li <tony.li@tony.li>
Message-ID: <20120509205102.GR16863@pfrc>
References: <20120507175757.GB16863@pfrc> <7309FCBCAE981B43ABBE69B31C8D213921BE3142CD@EUSAACMS0701.eamcs.ericsson.se> <20120509145717.GN16863@pfrc> <7309FCBCAE981B43ABBE69B31C8D213921BE3144F0@EUSAACMS0701.eamcs.ericsson.se> <20120509182103.GO16863@pfrc> <B3935C8B-8DF7-4A97-8C71-3564D4FEA05B@tony.li> <20120509184536.GP16863@pfrc> <BD4ED6BA-0C3F-4E22-908E-94D95C45FCAE@tony.li> <20120509202903.GQ16863@pfrc> <FC814643-BB29-4C1B-A3E0-40840F786BFA@tony.li>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <FC814643-BB29-4C1B-A3E0-40840F786BFA@tony.li>
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: "grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] Repeated Errors in BGP - draft-ietf-grow-ops-reqs-for-bgp-error-handling
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 May 2012 20:51:07 -0000

On Wed, May 09, 2012 at 03:32:52PM -0500, Tony Li wrote:
> Understood.  I have no issues with withdrawn routes.  The issue is with g-shut routes that continue to sink traffic.

Perhaps I'm unclear on your reservations.

If we don't go through something like graceful shutdown and leave the
peering session up, we're potentially going to pull significantly more
traffic toward the "bad" peering session than if we didn't do such a thing.

-- Jeff

From robert@raszuk.net  Wed May  9 14:00:25 2012
Return-Path: <robert@raszuk.net>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A986721F8476 for <grow@ietfa.amsl.com>; Wed,  9 May 2012 14:00:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.367
X-Spam-Level: 
X-Spam-Status: No, score=-2.367 tagged_above=-999 required=5 tests=[AWL=0.005,  BAYES_00=-2.599, SARE_SUB_OBFU_Q1=0.227]
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 EdjANo+2Q3W0 for <grow@ietfa.amsl.com>; Wed,  9 May 2012 14:00:25 -0700 (PDT)
Received: from mail1310.opentransfer.com (mail1310.opentransfer.com [76.162.254.103]) by ietfa.amsl.com (Postfix) with ESMTP id EEE8321F8472 for <grow@ietf.org>; Wed,  9 May 2012 14:00:24 -0700 (PDT)
Received: (qmail 900 invoked by uid 399); 9 May 2012 21:00:24 -0000
Received: from unknown (HELO ?192.168.1.58?) (pbs:robert@raszuk.net@83.31.245.24) by mail1310.opentransfer.com with ESMTPM; 9 May 2012 21:00:24 -0000
X-Originating-IP: 83.31.245.24
Message-ID: <4FAADAE8.8090007@raszuk.net>
Date: Wed, 09 May 2012 23:00:24 +0200
From: Robert Raszuk <robert@raszuk.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: Jeffrey Haas <jhaas@pfrc.org>
References: <20120507175757.GB16863@pfrc> <7309FCBCAE981B43ABBE69B31C8D213921BE3142CD@EUSAACMS0701.eamcs.ericsson.se> <20120509145717.GN16863@pfrc> <7309FCBCAE981B43ABBE69B31C8D213921BE3144F0@EUSAACMS0701.eamcs.ericsson.se> <20120509182103.GO16863@pfrc> <B3935C8B-8DF7-4A97-8C71-3564D4FEA05B@tony.li> <20120509184536.GP16863@pfrc> <BD4ED6BA-0C3F-4E22-908E-94D95C45FCAE@tony.li> <20120509202903.GQ16863@pfrc> <FC814643-BB29-4C1B-A3E0-40840F786BFA@tony.li> <20120509205102.GR16863@pfrc>
In-Reply-To: <20120509205102.GR16863@pfrc>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] Repeated Errors in BGP - draft-ietf-grow-ops-reqs-for-bgp-error-handling
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: robert@raszuk.net
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 May 2012 21:00:25 -0000

Jeff,

I do not understand why we are not going to re-advertise "good" routes 
with lowest local preference which would not result in holes of some 
boxes understanding g-shut community and some not.

In fact I spoke to Bruno in the past on that and I was hoping we all 
converged that g-shut community would be used only on the EBGP side to 
indicate to the peer that it should in turn lower local pref on his 
side. Apparently g-shut draft still calls for this new community to be 
used both on iBGP and eBGP side.

Regards,
R.

> On Wed, May 09, 2012 at 03:32:52PM -0500, Tony Li wrote:
>> Understood.  I have no issues with withdrawn routes.  The issue is with g-shut routes that continue to sink traffic.
>
> Perhaps I'm unclear on your reservations.
>
> If we don't go through something like graceful shutdown and leave the
> peering session up, we're potentially going to pull significantly more
> traffic toward the "bad" peering session than if we didn't do such a thing.
>
> -- Jeff
> _______________________________________________
> GROW mailing list
> GROW@ietf.org
> https://www.ietf.org/mailman/listinfo/grow
>
>


From jakob.heitz@ericsson.com  Wed May  9 18:49:31 2012
Return-Path: <jakob.heitz@ericsson.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 71FAB9E8002 for <grow@ietfa.amsl.com>; Wed,  9 May 2012 18:49:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.286
X-Spam-Level: 
X-Spam-Status: No, score=-6.286 tagged_above=-999 required=5 tests=[AWL=0.086,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_SUB_OBFU_Q1=0.227]
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 lYJNNfC1ZYiy for <grow@ietfa.amsl.com>; Wed,  9 May 2012 18:49:31 -0700 (PDT)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.9]) by ietfa.amsl.com (Postfix) with ESMTP id F0D239E8001 for <grow@ietf.org>; Wed,  9 May 2012 18:49:30 -0700 (PDT)
Received: from eusaamw0707.eamcs.ericsson.se ([147.117.20.32]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id q4A1nS7E023414; Wed, 9 May 2012 20:49:30 -0500
Received: from EUSAACMS0701.eamcs.ericsson.se ([169.254.1.6]) by eusaamw0707.eamcs.ericsson.se ([147.117.20.32]) with mapi; Wed, 9 May 2012 21:49:23 -0400
From: Jakob Heitz <jakob.heitz@ericsson.com>
To: Jeffrey Haas <jhaas@pfrc.org>, Tony Li <tony.li@tony.li>
Date: Wed, 9 May 2012 21:49:18 -0400
Thread-Topic: [GROW] Repeated Errors in BGP - draft-ietf-grow-ops-reqs-for-bgp-error-handling
Thread-Index: Ac0uJX2Ca7LCNihbQPibBbanBzb6YQAKY1Yg
Message-ID: <7309FCBCAE981B43ABBE69B31C8D213921BE314A2D@EUSAACMS0701.eamcs.ericsson.se>
References: <20120507175757.GB16863@pfrc> <7309FCBCAE981B43ABBE69B31C8D213921BE3142CD@EUSAACMS0701.eamcs.ericsson.se> <20120509145717.GN16863@pfrc> <7309FCBCAE981B43ABBE69B31C8D213921BE3144F0@EUSAACMS0701.eamcs.ericsson.se> <20120509182103.GO16863@pfrc> <B3935C8B-8DF7-4A97-8C71-3564D4FEA05B@tony.li> <20120509184536.GP16863@pfrc> <BD4ED6BA-0C3F-4E22-908E-94D95C45FCAE@tony.li> <20120509202903.GQ16863@pfrc> <FC814643-BB29-4C1B-A3E0-40840F786BFA@tony.li> <20120509205102.GR16863@pfrc>
In-Reply-To: <20120509205102.GR16863@pfrc>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] Repeated Errors in BGP - draft-ietf-grow-ops-reqs-for-bgp-error-handling
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 May 2012 01:49:31 -0000

On Wednesday, May 09, 2012 1:51 PM, Jeffrey Haas <mailto:jhaas@pfrc.org> wr=
ote:

> On Wed, May 09, 2012 at 03:32:52PM -0500, Tony Li wrote:
>> Understood.  I have no issues with withdrawn routes.  The issue is
>> with g-shut routes that continue to sink traffic.=20
>=20
> Perhaps I'm unclear on your reservations.
>=20
> If we don't go through something like graceful shutdown and leave the
> peering session up, we're potentially going to pull significantly more
> traffic toward the "bad" peering session than if we didn't do such a
> thing.=20
>=20
> -- Jeff

This is for ebgp only, not ibgp. right?

--=20
Jakob Heitz.=

From bruno.decraene@orange.com  Thu May 10 01:57:15 2012
Return-Path: <bruno.decraene@orange.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 491E021F85C2 for <grow@ietfa.amsl.com>; Thu, 10 May 2012 01:57:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.456
X-Spam-Level: 
X-Spam-Status: No, score=-1.456 tagged_above=-999 required=5 tests=[AWL=0.915,  BAYES_00=-2.599, SARE_SUB_OBFU_Q1=0.227, UNPARSEABLE_RELAY=0.001]
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 VXEGCljHa1Ay for <grow@ietfa.amsl.com>; Thu, 10 May 2012 01:57:12 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias91.francetelecom.com [193.251.215.91]) by ietfa.amsl.com (Postfix) with ESMTP id 088A221F85A7 for <grow@ietf.org>; Thu, 10 May 2012 01:57:10 -0700 (PDT)
Received: from omfedm07.si.francetelecom.fr (unknown [xx.xx.xx.3]) by omfedm12.si.francetelecom.fr (ESMTP service) with ESMTP id BAE7118C3C2; Thu, 10 May 2012 10:57:09 +0200 (CEST)
Received: from Exchangemail-eme1.itn.ftgroup (unknown [10.114.1.186]) by omfedm07.si.francetelecom.fr (ESMTP service) with ESMTP id 9CBEE4C069; Thu, 10 May 2012 10:57:09 +0200 (CEST)
Received: from PEXCVZYM11.corporate.adroot.infra.ftgroup ([fe80::a441:e6a9:6143:6f0f]) by PEXCVZYH01.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.02.0247.003; Thu, 10 May 2012 10:57:09 +0200
From: <bruno.decraene@orange.com>
To: "robert@raszuk.net" <robert@raszuk.net>, Tony Li <tony.li@tony.li>
Thread-Topic: [GROW] Repeated Errors in BGP - draft-ietf-grow-ops-reqs-for-bgp-error-handling
Thread-Index: AQHNLibFFt2XXtyjG06cDE9wiWy8eJbCtLTA
Date: Thu, 10 May 2012 08:57:08 +0000
Message-ID: <13030_1336640229_4FAB82E5_13030_9246_1_53C29892C857584299CBF5D05346208A078727@PEXCVZYM11.corporate.adroot.infra.ftgroup>
References: <20120507175757.GB16863@pfrc> <7309FCBCAE981B43ABBE69B31C8D213921BE3142CD@EUSAACMS0701.eamcs.ericsson.se> <20120509145717.GN16863@pfrc> <7309FCBCAE981B43ABBE69B31C8D213921BE3144F0@EUSAACMS0701.eamcs.ericsson.se> <20120509182103.GO16863@pfrc>	<B3935C8B-8DF7-4A97-8C71-3564D4FEA05B@tony.li> <20120509184536.GP16863@pfrc>	<BD4ED6BA-0C3F-4E22-908E-94D95C45FCAE@tony.li> <20120509202903.GQ16863@pfrc>	<FC814643-BB29-4C1B-A3E0-40840F786BFA@tony.li> <20120509205102.GR16863@pfrc> <4FAADAE8.8090007@raszuk.net>
In-Reply-To: <4FAADAE8.8090007@raszuk.net>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.197.38.5]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2012.5.10.73320
Cc: "grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] Repeated Errors in BGP -	draft-ietf-grow-ops-reqs-for-bgp-error-handling
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 May 2012 08:57:15 -0000

Robert, Tony,

Please find below some clarification regarding gshut (draft-ietf-grow-bgp-g=
shut):
- the g-shut community in itself has no effect on BGP path selection
- when the eBGP session is being g-shut,=20
	- on the iBGP side, routes (from the eBGP session beeing gshut) are readve=
rtised with a low LOCAL_PREF (e.g. 0).
	- on the eBGP side, routes (from the eBGP session beeing gshut) are readve=
rtised with the ghsut community. Then (if the neighbor AS is willing to use=
 g-shut), on the AS boundary (eBGP), routes having the g-shut community are=
 set to a lower LOCAL_PREF.


So in both involved ASes, route are de-preferenced because of the lower LOC=
AL_PREF. (not by iBGP routers interpreting the g-shut community).

Regards,
Bruno





>From: Robert Raszuk >Sent: Wednesday, May 09, 2012 11:00 PM
>
>Jeff,
>
>I do not understand why we are not going to re-advertise "good" routes
>with lowest local preference which would not result in holes of some
>boxes understanding g-shut community and some not.
>
>In fact I spoke to Bruno in the past on that and I was hoping we all
>converged that g-shut community would be used only on the EBGP side to
>indicate to the peer that it should in turn lower local pref on his
>side. Apparently g-shut draft still calls for this new community to be
>used both on iBGP and eBGP side.
>
>Regards,
>R.
>
>> On Wed, May 09, 2012 at 03:32:52PM -0500, Tony Li wrote:
>>> Understood.  I have no issues with withdrawn routes.  The issue is with=
 g-
>shut routes that continue to sink traffic.
>>
>> Perhaps I'm unclear on your reservations.
>>
>> If we don't go through something like graceful shutdown and leave the
>> peering session up, we're potentially going to pull significantly more
>> traffic toward the "bad" peering session than if we didn't do such a thi=
ng.
>>
>> -- Jeff
>> _______________________________________________
>> GROW mailing list
>> GROW@ietf.org
>> https://www.ietf.org/mailman/listinfo/grow
>>
>>
>
>_______________________________________________
>GROW mailing list
>GROW@ietf.org
>https://www.ietf.org/mailman/listinfo/grow

___________________________________________________________________________=
______________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu=
 ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el=
ectroniques etant susceptibles d'alteration,
France Telecom - Orange decline toute responsabilite si ce message a ete al=
tere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged inf=
ormation that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and dele=
te this message and its attachments.
As emails may be altered, France Telecom - Orange is not liable for message=
s that have been modified, changed or falsified.
Thank you.


From bruno.decraene@orange.com  Thu May 10 01:57:21 2012
Return-Path: <bruno.decraene@orange.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3F2B321F84CF for <grow@ietfa.amsl.com>; Thu, 10 May 2012 01:57:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.609
X-Spam-Level: 
X-Spam-Status: No, score=-1.609 tagged_above=-999 required=5 tests=[AWL=0.762,  BAYES_00=-2.599, SARE_SUB_OBFU_Q1=0.227, UNPARSEABLE_RELAY=0.001]
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 Q99iDCjVR8hL for <grow@ietfa.amsl.com>; Thu, 10 May 2012 01:57:20 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias91.francetelecom.com [193.251.215.91]) by ietfa.amsl.com (Postfix) with ESMTP id 6718821F8517 for <grow@ietf.org>; Thu, 10 May 2012 01:57:20 -0700 (PDT)
Received: from omfedm06.si.francetelecom.fr (unknown [xx.xx.xx.2]) by omfedm11.si.francetelecom.fr (ESMTP service) with ESMTP id BA09D3B42F9; Thu, 10 May 2012 10:57:19 +0200 (CEST)
Received: from Exchangemail-eme1.itn.ftgroup (unknown [10.114.1.186]) by omfedm06.si.francetelecom.fr (ESMTP service) with ESMTP id 9D16C27C06F; Thu, 10 May 2012 10:57:19 +0200 (CEST)
Received: from PEXCVZYM11.corporate.adroot.infra.ftgroup ([fe80::a441:e6a9:6143:6f0f]) by PEXCVZYH01.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.02.0247.003; Thu, 10 May 2012 10:57:19 +0200
From: <bruno.decraene@orange.com>
To: "robert@raszuk.net" <robert@raszuk.net>
Thread-Topic: [GROW] Repeated Errors in BGP - draft-ietf-grow-ops-reqs-for-bgp-error-handling
Thread-Index: AQHNLibFFt2XXtyjG06cDE9wiWy8eJbCtzlA
Date: Thu, 10 May 2012 08:57:18 +0000
Message-ID: <28077_1336640239_4FAB82EF_28077_1008_1_53C29892C857584299CBF5D05346208A07872E@PEXCVZYM11.corporate.adroot.infra.ftgroup>
References: <20120507175757.GB16863@pfrc> <7309FCBCAE981B43ABBE69B31C8D213921BE3142CD@EUSAACMS0701.eamcs.ericsson.se> <20120509145717.GN16863@pfrc> <7309FCBCAE981B43ABBE69B31C8D213921BE3144F0@EUSAACMS0701.eamcs.ericsson.se> <20120509182103.GO16863@pfrc>	<B3935C8B-8DF7-4A97-8C71-3564D4FEA05B@tony.li> <20120509184536.GP16863@pfrc>	<BD4ED6BA-0C3F-4E22-908E-94D95C45FCAE@tony.li> <20120509202903.GQ16863@pfrc>	<FC814643-BB29-4C1B-A3E0-40840F786BFA@tony.li> <20120509205102.GR16863@pfrc> <4FAADAE8.8090007@raszuk.net>
In-Reply-To: <4FAADAE8.8090007@raszuk.net>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.197.38.5]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2012.5.2.131529
Cc: "grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] Repeated Errors in BGP -	draft-ietf-grow-ops-reqs-for-bgp-error-handling
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 May 2012 08:57:21 -0000

Robert,


>From: Robert Raszuk Sent: Wednesday, May 09, 2012 11:00 PM
>
>Jeff,
>
>I do not understand why we are not going to re-advertise "good" routes
>with lowest local preference which would not result in holes of some
>boxes understanding g-shut community and some not.

What you propose (using LOCAL_PREF) is what the g-shut draft also propose.

>In fact I spoke to Bruno in the past on that and I was hoping we all
>converged that g-shut community would be used only on the EBGP side to
>indicate to the peer that it should in turn lower local pref on his
>side.

The g-shut community has always been used to signal the ghsut only on the e=
BGP side. On the iBGP side, LOCAL_PREF has always been used.

> Apparently g-shut draft still calls for this new community to be
>used both on iBGP and eBGP side.

On the iBGP side, LOCAL_PREF is used to lower the preference of the g-shut =
draft.
In _addition_ to this, the g-shut community is attached for _informational_=
 purpose. Because some AS internal BGP policy may have a need to know that =
the route is being g-shut. And it's cleaner to use a community to provide t=
he root cause rather than try to guess from the low LOCAL_PREF the root cau=
se.

Regards,
Bruno


>
>Regards,
>R.
>
>> On Wed, May 09, 2012 at 03:32:52PM -0500, Tony Li wrote:
>>> Understood.  I have no issues with withdrawn routes.  The issue is with=
 g-
>shut routes that continue to sink traffic.
>>
>> Perhaps I'm unclear on your reservations.
>>
>> If we don't go through something like graceful shutdown and leave the
>> peering session up, we're potentially going to pull significantly more
>> traffic toward the "bad" peering session than if we didn't do such a thi=
ng.
>>
>> -- Jeff
>> _______________________________________________
>> GROW mailing list
>> GROW@ietf.org
>> https://www.ietf.org/mailman/listinfo/grow
>>
>>
>
>_______________________________________________
>GROW mailing list
>GROW@ietf.org
>https://www.ietf.org/mailman/listinfo/grow

___________________________________________________________________________=
______________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu=
 ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el=
ectroniques etant susceptibles d'alteration,
France Telecom - Orange decline toute responsabilite si ce message a ete al=
tere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged inf=
ormation that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and dele=
te this message and its attachments.
As emails may be altered, France Telecom - Orange is not liable for message=
s that have been modified, changed or falsified.
Thank you.


From bruno.decraene@orange.com  Thu May 10 02:17:52 2012
Return-Path: <bruno.decraene@orange.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 622D721F85FF for <grow@ietfa.amsl.com>; Thu, 10 May 2012 02:17:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.718
X-Spam-Level: 
X-Spam-Status: No, score=-1.718 tagged_above=-999 required=5 tests=[AWL=0.653,  BAYES_00=-2.599, SARE_SUB_OBFU_Q1=0.227, UNPARSEABLE_RELAY=0.001]
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 2IFsjMgzHfMC for <grow@ietfa.amsl.com>; Thu, 10 May 2012 02:17:51 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias91.francetelecom.com [193.251.215.91]) by ietfa.amsl.com (Postfix) with ESMTP id 8FA2021F8522 for <grow@ietf.org>; Thu, 10 May 2012 02:17:51 -0700 (PDT)
Received: from omfedm06.si.francetelecom.fr (unknown [xx.xx.xx.2]) by omfedm11.si.francetelecom.fr (ESMTP service) with ESMTP id CC1A73B4418; Thu, 10 May 2012 11:17:50 +0200 (CEST)
Received: from Exchangemail-eme1.itn.ftgroup (unknown [10.114.1.186]) by omfedm06.si.francetelecom.fr (ESMTP service) with ESMTP id A619727C067; Thu, 10 May 2012 11:17:50 +0200 (CEST)
Received: from PEXCVZYM11.corporate.adroot.infra.ftgroup ([fe80::a441:e6a9:6143:6f0f]) by PEXCVZYH01.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.02.0247.003; Thu, 10 May 2012 11:17:50 +0200
From: <bruno.decraene@orange.com>
To: Tony Li <tony.li@tony.li>, Jeffrey Haas <jhaas@pfrc.org>
Thread-Topic: [GROW] Repeated Errors in BGP - draft-ietf-grow-ops-reqs-for-bgp-error-handling
Thread-Index: AQHNLiL0Ft2XXtyjG06cDE9wiWy8eJbCucNg
Date: Thu, 10 May 2012 09:17:50 +0000
Message-ID: <28077_1336641470_4FAB87BE_28077_1364_1_53C29892C857584299CBF5D05346208A078764@PEXCVZYM11.corporate.adroot.infra.ftgroup>
References: <FB4645AC-2540-4152-A1F1-67DC7116D953@rob.sh> <20120507175757.GB16863@pfrc> <7309FCBCAE981B43ABBE69B31C8D213921BE3142CD@EUSAACMS0701.eamcs.ericsson.se> <20120509145717.GN16863@pfrc> <7309FCBCAE981B43ABBE69B31C8D213921BE3144F0@EUSAACMS0701.eamcs.ericsson.se> <20120509182103.GO16863@pfrc>	<B3935C8B-8DF7-4A97-8C71-3564D4FEA05B@tony.li> <20120509184536.GP16863@pfrc>	<BD4ED6BA-0C3F-4E22-908E-94D95C45FCAE@tony.li> <20120509202903.GQ16863@pfrc> <FC814643-BB29-4C1B-A3E0-40840F786BFA@tony.li>
In-Reply-To: <FC814643-BB29-4C1B-A3E0-40840F786BFA@tony.li>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.197.38.5]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2012.5.2.131529
Cc: "grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] Repeated Errors in BGP -	draft-ietf-grow-ops-reqs-for-bgp-error-handling
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 May 2012 09:17:52 -0000

Jeff, Tony,


>From: Tony Li >Sent: Wednesday, May 09, 2012 10:33 PM
>
>On May 9, 2012, at 3:29 PM, Jeffrey Haas wrote:
>
>>> Thank you.  This seems to indicate that after a g-shut event, the neigh=
bor
>would continue to advertise the prefixes to its peers (albeit tagged with =
the
>community).  Wouldn't this cause non-updated routers to blackhole traffic?
>What happens when only half of you IBGP peers are updated?
>>>
>>> If the peering doesn't come back for an extended period, couldn't this =
cause
>traffic to transit and then be blackholed, assuming there are no alternate
>paths?
>>>
>>> This is violating BGP's fundamental principle: "Advertise what you're u=
sing,
>use what you advertise."  It seems like black holes are inevitable.
>>
>> Please see the other clarification I posted.  Graceful shutdown is appli=
ed
>> to the routes from the peer that is sending bad updates that are accepted
>> and valid.  Routes that contain errors are processed with the stated "tr=
eat
>> as withdraw" behavior.
>>
>> In other words, the goal is to remove the bad neighbor's valid routes fr=
om
>> the forwarding path as much as possible since that neighbor is presumed =
to
>> possibly crazy.
>
>
>Jeff,
>
>Understood.  I have no issues with withdrawn routes.  The issue is with g-=
shut
>routes that continue to sink traffic.

In iBGP, as per my previous clarification, I don't see an issue within the =
AS de-preferencing the routes received from the "bad" eBGP peer:
- if there is a backup path, it will be used. Fine.
- otherwise, it may be better to still use the routes learnt from a valid U=
PDATE.

In eBGP, however, IMO Tony has a point for upstream ASes (next ASes from th=
e BGP propagation point of view). There is no guaranty that they will under=
stand the g-shut community. Hence they will not de-preference the route and=
 may still use the suspicious routes even if they have an alternate path.=
=20
Then it's a question of how much we trust those routes. If we believe they =
are reasonable, we could still advertise them to upstream AS (this is only =
for the case where is no a valid backup path as those path have a low local=
_pref). Otherwise, we could add the NO_EXPORT community to avoid propagatin=
g that path to others ASes.

Regards,
Bruno

>Tony
>
>_______________________________________________
>GROW mailing list
>GROW@ietf.org
>https://www.ietf.org/mailman/listinfo/grow

___________________________________________________________________________=
______________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu=
 ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el=
ectroniques etant susceptibles d'alteration,
France Telecom - Orange decline toute responsabilite si ce message a ete al=
tere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged inf=
ormation that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and dele=
te this message and its attachments.
As emails may be altered, France Telecom - Orange is not liable for message=
s that have been modified, changed or falsified.
Thank you.


From robert@raszuk.net  Thu May 10 02:25:19 2012
Return-Path: <robert@raszuk.net>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A251B21F861D for <grow@ietfa.amsl.com>; Thu, 10 May 2012 02:25:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.368
X-Spam-Level: 
X-Spam-Status: No, score=-2.368 tagged_above=-999 required=5 tests=[AWL=0.004,  BAYES_00=-2.599, SARE_SUB_OBFU_Q1=0.227]
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 p+DGNt2Dg+yf for <grow@ietfa.amsl.com>; Thu, 10 May 2012 02:25:19 -0700 (PDT)
Received: from mail1310.opentransfer.com (mail1310.opentransfer.com [76.162.254.103]) by ietfa.amsl.com (Postfix) with ESMTP id C8FA421F861A for <grow@ietf.org>; Thu, 10 May 2012 02:25:18 -0700 (PDT)
Received: (qmail 29440 invoked by uid 399); 10 May 2012 09:25:18 -0000
Received: from unknown (HELO ?192.168.1.58?) (pbs:robert@raszuk.net@83.31.240.97) by mail1310.opentransfer.com with ESMTPM; 10 May 2012 09:25:18 -0000
X-Originating-IP: 83.31.240.97
Message-ID: <4FAB897D.8040000@raszuk.net>
Date: Thu, 10 May 2012 11:25:17 +0200
From: Robert Raszuk <robert@raszuk.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: bruno.decraene@orange.com
References: <20120507175757.GB16863@pfrc> <7309FCBCAE981B43ABBE69B31C8D213921BE3142CD@EUSAACMS0701.eamcs.ericsson.se> <20120509145717.GN16863@pfrc> <7309FCBCAE981B43ABBE69B31C8D213921BE3144F0@EUSAACMS0701.eamcs.ericsson.se> <20120509182103.GO16863@pfrc>	<B3935C8B-8DF7-4A97-8C71-3564D4FEA05B@tony.li> <20120509184536.GP16863@pfrc>	<BD4ED6BA-0C3F-4E22-908E-94D95C45FCAE@tony.li> <20120509202903.GQ16863@pfrc>	<FC814643-BB29-4C1B-A3E0-40840F786BFA@tony.li> <20120509205102.GR16863@pfrc> <4FAADAE8.8090007@raszuk.net> <28077_1336640239_4FAB82EF_28077_1008_1_53C29892C857584299CBF5D05346208A07872E@PEXCVZYM11.corporate.adroot.infra.ftgroup>
In-Reply-To: <28077_1336640239_4FAB82EF_28077_1008_1_53C29892C857584299CBF5D05346208A07872E@PEXCVZYM11.corporate.adroot.infra.ftgroup>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] Repeated Errors in BGP - draft-ietf-grow-ops-reqs-for-bgp-error-handling
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: robert@raszuk.net
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 May 2012 09:25:19 -0000

Hello Bruno,

Excellent - this is exactly what we discussed in the past. But when I 
read the draft before sending email yesterday unfortunately it does not 
say so that clearly at all - regarding the IBGP case ;(

         iBGP         eBGP
PE1 ---- P ---- PE2 ====== PE3

The scenario I had in mind was we are receiving errored UPDATE msg from 
PE3 to PE2, PE2 treats as withdraw the parsable NLRIs then for the reast 
the thread so far indicated to inject g-shut community.

While injecting G_SHUT would not hurt and would allow for example PE1 to 
propagate it downstream in the same time error handling draft should 
IMHO me explicit to say we are advertising from PE2 towards it's AS with 
lowest LOCAL_PREF and G_SHUT.

Example:

4.2.1.1.  Pre-configuration

    On each ASBR supporting the g-shut procedure, an outbound BGP route
    policy is applied on all iBGP sessions of the ASBR, that:
    o    matches the g-shut community
    o    sets the local-pref of the paths tagged with the g-shut
         community to a low value

Here in out case we do not match on g-shut as g-shut is not received 
from EBGP.

Also perhaps it would be great to just copy and paste the quote from the 
previous email directly to a deployment section of the draft.

Best regards,
R.


> Robert,
>
>
>> From: Robert Raszuk Sent: Wednesday, May 09, 2012 11:00 PM
>>
>> Jeff,
>>
>> I do not understand why we are not going to re-advertise "good" routes
>> with lowest local preference which would not result in holes of some
>> boxes understanding g-shut community and some not.
>
> What you propose (using LOCAL_PREF) is what the g-shut draft also propose.
>
>> In fact I spoke to Bruno in the past on that and I was hoping we all
>> converged that g-shut community would be used only on the EBGP side to
>> indicate to the peer that it should in turn lower local pref on his
>> side.
>
> The g-shut community has always been used to signal the ghsut only on the eBGP side. On the iBGP side, LOCAL_PREF has always been used.
>
>> Apparently g-shut draft still calls for this new community to be
>> used both on iBGP and eBGP side.
>
> On the iBGP side, LOCAL_PREF is used to lower the preference of the g-shut draft.
> In _addition_ to this, the g-shut community is attached for _informational_ purpose. Because some AS internal BGP policy may have a need to know that the route is being g-shut. And it's cleaner to use a community to provide the root cause rather than try to guess from the low LOCAL_PREF the root cause.
>
> Regards,
> Bruno
>
>
>>
>> Regards,
>> R.
>>
>>> On Wed, May 09, 2012 at 03:32:52PM -0500, Tony Li wrote:
>>>> Understood.  I have no issues with withdrawn routes.  The issue is with g-
>> shut routes that continue to sink traffic.
>>>
>>> Perhaps I'm unclear on your reservations.
>>>
>>> If we don't go through something like graceful shutdown and leave the
>>> peering session up, we're potentially going to pull significantly more
>>> traffic toward the "bad" peering session than if we didn't do such a thing.
>>>
>>> -- Jeff
>>> _______________________________________________
>>> GROW mailing list
>>> GROW@ietf.org
>>> https://www.ietf.org/mailman/listinfo/grow
>>>
>>>
>>
>> _______________________________________________
>> GROW mailing list
>> GROW@ietf.org
>> https://www.ietf.org/mailman/listinfo/grow
>
> _________________________________________________________________________________________________________________________
>
> Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
> France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
>
> This message and its attachments may contain confidential or privileged information that may be protected by law;
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and delete this message and its attachments.
> As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified.
> Thank you.
>
>
>


From bruno.decraene@orange.com  Thu May 10 03:03:48 2012
Return-Path: <bruno.decraene@orange.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6023C21F854C for <grow@ietfa.amsl.com>; Thu, 10 May 2012 03:03:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.913
X-Spam-Level: 
X-Spam-Status: No, score=-1.913 tagged_above=-999 required=5 tests=[AWL=0.685,  BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001]
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 WpNjeq40CrbO for <grow@ietfa.amsl.com>; Thu, 10 May 2012 03:03:47 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias91.francetelecom.com [193.251.215.91]) by ietfa.amsl.com (Postfix) with ESMTP id 4C0BA21F8540 for <grow@ietf.org>; Thu, 10 May 2012 03:03:46 -0700 (PDT)
Received: from omfedm05.si.francetelecom.fr (unknown [xx.xx.xx.1]) by omfedm14.si.francetelecom.fr (ESMTP service) with ESMTP id 1581622C632; Thu, 10 May 2012 12:03:45 +0200 (CEST)
Received: from Exchangemail-eme1.itn.ftgroup (unknown [10.114.1.186]) by omfedm05.si.francetelecom.fr (ESMTP service) with ESMTP id ECE2F35C060; Thu, 10 May 2012 12:03:44 +0200 (CEST)
Received: from PEXCVZYM11.corporate.adroot.infra.ftgroup ([fe80::a441:e6a9:6143:6f0f]) by PEXCVZYH01.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.02.0247.003; Thu, 10 May 2012 12:03:44 +0200
From: <bruno.decraene@orange.com>
To: "robert@raszuk.net" <robert@raszuk.net>
Thread-Topic: draft-ietf-grow-bgp-gshut
Thread-Index: AQHNLpQuKEj+BoTPikOz3JMguGF/6Q==
Date: Thu, 10 May 2012 10:03:43 +0000
Message-ID: <11733_1336644225_4FAB9280_11733_14189_1_53C29892C857584299CBF5D05346208A0787CD@PEXCVZYM11.corporate.adroot.infra.ftgroup>
References: <20120507175757.GB16863@pfrc> <7309FCBCAE981B43ABBE69B31C8D213921BE3142CD@EUSAACMS0701.eamcs.ericsson.se> <20120509145717.GN16863@pfrc> <7309FCBCAE981B43ABBE69B31C8D213921BE3144F0@EUSAACMS0701.eamcs.ericsson.se> <20120509182103.GO16863@pfrc>	<B3935C8B-8DF7-4A97-8C71-3564D4FEA05B@tony.li> <20120509184536.GP16863@pfrc>	<BD4ED6BA-0C3F-4E22-908E-94D95C45FCAE@tony.li> <20120509202903.GQ16863@pfrc>	<FC814643-BB29-4C1B-A3E0-40840F786BFA@tony.li> <20120509205102.GR16863@pfrc> <4FAADAE8.8090007@raszuk.net> <28077_1336640239_4FAB82EF_28077_1008_1_53C29892C857584299CBF5D05346208A07872E@PEXCVZYM11.corporate.adroot.infra.ftgroup> <4FAB897D.8040000@raszuk.net>
In-Reply-To: <4FAB897D.8040000@raszuk.net>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.197.38.5]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2012.5.10.73320
Cc: "grow@ietf.org" <grow@ietf.org>
Subject: [GROW] draft-ietf-grow-bgp-gshut
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 May 2012 10:03:48 -0000

Robert,

[Changing the title of the thread to better reflect the subject]

>From: Robert Raszuk [mailto:robert@raszuk.net] >Sent: Thursday, May 10, 20=
12 11:25 AM
>
>Hello Bruno,
>
>Excellent - this is exactly what we discussed in the past. But when I
>read the draft before sending email yesterday unfortunately it does not
>say so that clearly at all - regarding the IBGP case ;(

If the draft is not clear enough, we always welcome comments. Do you have s=
pecific comments that we should add in the draft?=20

The following section of the draft recaps the actions to be performed.=20

"4.2.1.3. BGP implementation support for G-Shut


[...]

   Upon a session shutdown specified as graceful by the operator, a BGP
   implementation supporting a g-shut feature SHOULD:

   1.   Update all the paths propagated over the corresponding eBGP
        session, tagging the GSHUT community to them.  Any subsequent
        update sent to the session being gracefully shut down would be
        tagged with the GSHUT community.
   2.   Lower the local preference value of the paths received over the
        eBGP session being shut down, upon their propagation over iBGP
        sessions.  Optionally, also tag these paths with an AS specific
        g-shut community.  Note that alternatively, the local preference
        of the paths received over the eBGP session can be lowered on
        the g-shut initiator itself, instead of only when propagating
        over its iBGP sessions."

At least to me, seems clear that the community is used on the eBGP side and=
 LOCAL_PREF is used on the iBGP side. Eventually we could to the following =
change:
- :s/local preference/LOCAL_PREF
- May be start the sentence of 1. and 2. with: "on the eBGP side", "on the =
iBGP side"

Others comments welcomed.

>         iBGP         eBGP
>PE1 ---- P ---- PE2 =3D=3D=3D=3D=3D=3D PE3
>
>The scenario I had in mind was we are receiving errored UPDATE msg from
>PE3 to PE2, PE2 treats as withdraw the parsable NLRIs then for the reast
>the thread so far indicated to inject g-shut community.
>
>While injecting G_SHUT would not hurt and would allow for example PE1 to
>propagate it downstream in the same time error handling draft should
>IMHO me explicit to say we are advertising from PE2 towards it's AS with
>lowest LOCAL_PREF and G_SHUT.
>
>Example:
>
>4.2.1.1.  Pre-configuration
>
>    On each ASBR supporting the g-shut procedure, an outbound BGP route
>    policy is applied on all iBGP sessions of the ASBR, that:
>    o    matches the g-shut community
>    o    sets the local-pref of the paths tagged with the g-shut
>         community to a low value
>
>Here in out case we do not match on g-shut as g-shut is not received
>from EBGP.
>
>Also perhaps it would be great to just copy and paste the quote from the
>previous email directly to a deployment section of the draft.

Sorry the given the amount of emails, could you please be a little more spe=
cific? (e.g. which quote).

Thanks for the useful comments.
Best regards,
Bruno

>Best regards,
>R.
>
>
>> Robert,
>>
>>
>>> From: Robert Raszuk Sent: Wednesday, May 09, 2012 11:00 PM
>>>
>>> Jeff,
>>>
>>> I do not understand why we are not going to re-advertise "good" routes
>>> with lowest local preference which would not result in holes of some
>>> boxes understanding g-shut community and some not.
>>
>> What you propose (using LOCAL_PREF) is what the g-shut draft also propos=
e.
>>
>>> In fact I spoke to Bruno in the past on that and I was hoping we all
>>> converged that g-shut community would be used only on the EBGP side to
>>> indicate to the peer that it should in turn lower local pref on his
>>> side.
>>
>> The g-shut community has always been used to signal the ghsut only on the
>eBGP side. On the iBGP side, LOCAL_PREF has always been used.
>>
>>> Apparently g-shut draft still calls for this new community to be
>>> used both on iBGP and eBGP side.
>>
>> On the iBGP side, LOCAL_PREF is used to lower the preference of the g-sh=
ut
>draft.
>> In _addition_ to this, the g-shut community is attached for _information=
al_
>purpose. Because some AS internal BGP policy may have a need to know that =
the
>route is being g-shut. And it's cleaner to use a community to provide the =
root
>cause rather than try to guess from the low LOCAL_PREF the root cause.
>>
>> Regards,
>> Bruno
>>
>>
>>>
>>> Regards,
>>> R.
>>>
>>>> On Wed, May 09, 2012 at 03:32:52PM -0500, Tony Li wrote:
>>>>> Understood.  I have no issues with withdrawn routes.  The issue is wi=
th g-
>>> shut routes that continue to sink traffic.
>>>>
>>>> Perhaps I'm unclear on your reservations.
>>>>
>>>> If we don't go through something like graceful shutdown and leave the
>>>> peering session up, we're potentially going to pull significantly more
>>>> traffic toward the "bad" peering session than if we didn't do such a t=
hing.
>>>>
>>>> -- Jeff
>>>> _______________________________________________
>>>> GROW mailing list
>>>> GROW@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/grow
>>>>
>>>>
>>>
>>> _______________________________________________
>>> GROW mailing list
>>> GROW@ietf.org
>>> https://www.ietf.org/mailman/listinfo/grow
>>
>>
>__________________________________________________________________________=
_____
>__________________________________________
>>
>> Ce message et ses pieces jointes peuvent contenir des informations
>confidentielles ou privilegiees et ne doivent donc
>> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez r=
ecu
>ce message par erreur, veuillez le signaler
>> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages
>electroniques etant susceptibles d'alteration,
>> France Telecom - Orange decline toute responsabilite si ce message a ete
>altere, deforme ou falsifie. Merci.
>>
>> This message and its attachments may contain confidential or privileged
>information that may be protected by law;
>> they should not be distributed, used or copied without authorisation.
>> If you have received this email in error, please notify the sender and d=
elete
>this message and its attachments.
>> As emails may be altered, France Telecom - Orange is not liable for mess=
ages
>that have been modified, changed or falsified.
>> Thank you.
>>
>>
>>


___________________________________________________________________________=
______________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu=
 ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el=
ectroniques etant susceptibles d'alteration,
France Telecom - Orange decline toute responsabilite si ce message a ete al=
tere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged inf=
ormation that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and dele=
te this message and its attachments.
As emails may be altered, France Telecom - Orange is not liable for message=
s that have been modified, changed or falsified.
Thank you.


From robert@raszuk.net  Thu May 10 05:16:39 2012
Return-Path: <robert@raszuk.net>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B4F9821F865B for <grow@ietfa.amsl.com>; Thu, 10 May 2012 05:16:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.481
X-Spam-Level: 
X-Spam-Status: No, score=-2.481 tagged_above=-999 required=5 tests=[AWL=0.118,  BAYES_00=-2.599]
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 YHLn3tfNTe6S for <grow@ietfa.amsl.com>; Thu, 10 May 2012 05:16:38 -0700 (PDT)
Received: from mail1310.opentransfer.com (mail1310.opentransfer.com [76.162.254.103]) by ietfa.amsl.com (Postfix) with ESMTP id 23DE021F8659 for <grow@ietf.org>; Thu, 10 May 2012 05:16:37 -0700 (PDT)
Received: (qmail 16493 invoked by uid 399); 10 May 2012 12:16:37 -0000
Received: from unknown (HELO ?192.168.1.91?) (pbs:robert@raszuk.net@83.31.230.182) by mail1310.opentransfer.com with ESMTPM; 10 May 2012 12:16:37 -0000
X-Originating-IP: 83.31.230.182
Message-ID: <4FABB1A4.9050402@raszuk.net>
Date: Thu, 10 May 2012 14:16:36 +0200
From: Robert Raszuk <robert@raszuk.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: bruno.decraene@orange.com
References: <20120507175757.GB16863@pfrc> <7309FCBCAE981B43ABBE69B31C8D213921BE3142CD@EUSAACMS0701.eamcs.ericsson.se> <20120509145717.GN16863@pfrc> <7309FCBCAE981B43ABBE69B31C8D213921BE3144F0@EUSAACMS0701.eamcs.ericsson.se> <20120509182103.GO16863@pfrc>	<B3935C8B-8DF7-4A97-8C71-3564D4FEA05B@tony.li> <20120509184536.GP16863@pfrc>	<BD4ED6BA-0C3F-4E22-908E-94D95C45FCAE@tony.li> <20120509202903.GQ16863@pfrc>	<FC814643-BB29-4C1B-A3E0-40840F786BFA@tony.li> <20120509205102.GR16863@pfrc> <4FAADAE8.8090007@raszuk.net> <28077_1336640239_4FAB82EF_28077_1008_1_53C29892C857584299CBF5D05346208A07872E@PEXCVZYM11.corporate.adroot.infra.ftgroup> <4FAB897D.8040000@raszuk.net> <11733_1336644225_4FAB9280_11733_14189_1_53C29892C857584299CBF5D05346208A0787CD@PEXCVZYM11.corporate.adroot.infra.ftgroup>
In-Reply-To: <11733_1336644225_4FAB9280_11733_14189_1_53C29892C857584299CBF5D05346208A0787CD@PEXCVZYM11.corporate.adroot.infra.ftgroup>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] draft-ietf-grow-bgp-gshut
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: robert@raszuk.net
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 May 2012 12:16:39 -0000

Bruno,

 > 2.   Lower the local preference value of the paths received over the
 >      eBGP session being shut down, upon their propagation over iBGP
 >      sessions.

Looking at the definition of upon:

"upon" - immediately or very soon after
http://dictionary.reference.com/browse/upon

What is the point of lowering local pref "after" their propagation over 
ibgp session ? To repropagate again ? Shouldn't it s/upon/before/ ?

r.



> Robert,
>
> [Changing the title of the thread to better reflect the subject]
>
>> From: Robert Raszuk [mailto:robert@raszuk.net]>Sent: Thursday, May 10, 2012 11:25 AM
>>
>> Hello Bruno,
>>
>> Excellent - this is exactly what we discussed in the past. But when I
>> read the draft before sending email yesterday unfortunately it does not
>> say so that clearly at all - regarding the IBGP case ;(
>
> If the draft is not clear enough, we always welcome comments. Do you have specific comments that we should add in the draft?
>
> The following section of the draft recaps the actions to be performed.
>
> "4.2.1.3. BGP implementation support for G-Shut
>
>
> [...]
>
>     Upon a session shutdown specified as graceful by the operator, a BGP
>     implementation supporting a g-shut feature SHOULD:
>
>     1.   Update all the paths propagated over the corresponding eBGP
>          session, tagging the GSHUT community to them.  Any subsequent
>          update sent to the session being gracefully shut down would be
>          tagged with the GSHUT community.
>     2.   Lower the local preference value of the paths received over the
>          eBGP session being shut down, upon their propagation over iBGP
>          sessions.  Optionally, also tag these paths with an AS specific
>          g-shut community.  Note that alternatively, the local preference
>          of the paths received over the eBGP session can be lowered on
>          the g-shut initiator itself, instead of only when propagating
>          over its iBGP sessions."
>
> At least to me, seems clear that the community is used on the eBGP side and LOCAL_PREF is used on the iBGP side. Eventually we could to the following change:
> - :s/local preference/LOCAL_PREF
> - May be start the sentence of 1. and 2. with: "on the eBGP side", "on the iBGP side"
>
> Others comments welcomed.
>
>>          iBGP         eBGP
>> PE1 ---- P ---- PE2 ====== PE3
>>
>> The scenario I had in mind was we are receiving errored UPDATE msg from
>> PE3 to PE2, PE2 treats as withdraw the parsable NLRIs then for the reast
>> the thread so far indicated to inject g-shut community.
>>
>> While injecting G_SHUT would not hurt and would allow for example PE1 to
>> propagate it downstream in the same time error handling draft should
>> IMHO me explicit to say we are advertising from PE2 towards it's AS with
>> lowest LOCAL_PREF and G_SHUT.
>>
>> Example:
>>
>> 4.2.1.1.  Pre-configuration
>>
>>     On each ASBR supporting the g-shut procedure, an outbound BGP route
>>     policy is applied on all iBGP sessions of the ASBR, that:
>>     o    matches the g-shut community
>>     o    sets the local-pref of the paths tagged with the g-shut
>>          community to a low value
>>
>> Here in out case we do not match on g-shut as g-shut is not received
>>from EBGP.
>>
>> Also perhaps it would be great to just copy and paste the quote from the
>> previous email directly to a deployment section of the draft.
>
> Sorry the given the amount of emails, could you please be a little more specific? (e.g. which quote).
>
> Thanks for the useful comments.
> Best regards,
> Bruno
>
>> Best regards,
>> R.
>>
>>
>>> Robert,
>>>
>>>
>>>> From: Robert Raszuk Sent: Wednesday, May 09, 2012 11:00 PM
>>>>
>>>> Jeff,
>>>>
>>>> I do not understand why we are not going to re-advertise "good" routes
>>>> with lowest local preference which would not result in holes of some
>>>> boxes understanding g-shut community and some not.
>>>
>>> What you propose (using LOCAL_PREF) is what the g-shut draft also propose.
>>>
>>>> In fact I spoke to Bruno in the past on that and I was hoping we all
>>>> converged that g-shut community would be used only on the EBGP side to
>>>> indicate to the peer that it should in turn lower local pref on his
>>>> side.
>>>
>>> The g-shut community has always been used to signal the ghsut only on the
>> eBGP side. On the iBGP side, LOCAL_PREF has always been used.
>>>
>>>> Apparently g-shut draft still calls for this new community to be
>>>> used both on iBGP and eBGP side.
>>>
>>> On the iBGP side, LOCAL_PREF is used to lower the preference of the g-shut
>> draft.
>>> In _addition_ to this, the g-shut community is attached for _informational_
>> purpose. Because some AS internal BGP policy may have a need to know that the
>> route is being g-shut. And it's cleaner to use a community to provide the root
>> cause rather than try to guess from the low LOCAL_PREF the root cause.
>>>
>>> Regards,
>>> Bruno
>>>
>>>
>>>>
>>>> Regards,
>>>> R.
>>>>
>>>>> On Wed, May 09, 2012 at 03:32:52PM -0500, Tony Li wrote:
>>>>>> Understood.  I have no issues with withdrawn routes.  The issue is with g-
>>>> shut routes that continue to sink traffic.
>>>>>
>>>>> Perhaps I'm unclear on your reservations.
>>>>>
>>>>> If we don't go through something like graceful shutdown and leave the
>>>>> peering session up, we're potentially going to pull significantly more
>>>>> traffic toward the "bad" peering session than if we didn't do such a thing.
>>>>>
>>>>> -- Jeff
>>>>> _______________________________________________
>>>>> GROW mailing list
>>>>> GROW@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/grow
>>>>>
>>>>>
>>>>
>>>> _______________________________________________
>>>> GROW mailing list
>>>> GROW@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/grow
>>>
>>>
>> _______________________________________________________________________________
>> __________________________________________
>>>
>>> Ce message et ses pieces jointes peuvent contenir des informations
>> confidentielles ou privilegiees et ne doivent donc
>>> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu
>> ce message par erreur, veuillez le signaler
>>> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages
>> electroniques etant susceptibles d'alteration,
>>> France Telecom - Orange decline toute responsabilite si ce message a ete
>> altere, deforme ou falsifie. Merci.
>>>
>>> This message and its attachments may contain confidential or privileged
>> information that may be protected by law;
>>> they should not be distributed, used or copied without authorisation.
>>> If you have received this email in error, please notify the sender and delete
>> this message and its attachments.
>>> As emails may be altered, France Telecom - Orange is not liable for messages
>> that have been modified, changed or falsified.
>>> Thank you.
>>>
>>>
>>>
>
>
> _________________________________________________________________________________________________________________________
>
> Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
> France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
>
> This message and its attachments may contain confidential or privileged information that may be protected by law;
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and delete this message and its attachments.
> As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified.
> Thank you.
>
>
>


From bruno.decraene@orange.com  Thu May 10 06:06:00 2012
Return-Path: <bruno.decraene@orange.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8346F21F866A for <grow@ietfa.amsl.com>; Thu, 10 May 2012 06:06:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.989
X-Spam-Level: 
X-Spam-Status: No, score=-1.989 tagged_above=-999 required=5 tests=[AWL=0.609,  BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001]
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 3Mz4jf5hWUFw for <grow@ietfa.amsl.com>; Thu, 10 May 2012 06:05:59 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias92.francetelecom.com [193.251.215.92]) by ietfa.amsl.com (Postfix) with ESMTP id A185521F8667 for <grow@ietf.org>; Thu, 10 May 2012 06:05:58 -0700 (PDT)
Received: from omfedm07.si.francetelecom.fr (unknown [xx.xx.xx.3]) by omfedm13.si.francetelecom.fr (ESMTP service) with ESMTP id 0C406324654; Thu, 10 May 2012 15:05:58 +0200 (CEST)
Received: from Exchangemail-eme1.itn.ftgroup (unknown [10.114.1.186]) by omfedm07.si.francetelecom.fr (ESMTP service) with ESMTP id D31034C077; Thu, 10 May 2012 15:05:57 +0200 (CEST)
Received: from PEXCVZYM11.corporate.adroot.infra.ftgroup ([fe80::a441:e6a9:6143:6f0f]) by PEXCVZYH01.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.02.0247.003; Thu, 10 May 2012 15:05:57 +0200
From: <bruno.decraene@orange.com>
To: "robert@raszuk.net" <robert@raszuk.net>
Thread-Topic: draft-ietf-grow-bgp-gshut
Thread-Index: AQHNLqa+KEj+BoTPikOz3JMguGF/6ZbC+Geg
Date: Thu, 10 May 2012 13:05:57 +0000
Message-ID: <30550_1336655157_4FABBD35_30550_3926_3_53C29892C857584299CBF5D05346208A0788AC@PEXCVZYM11.corporate.adroot.infra.ftgroup>
References: <20120507175757.GB16863@pfrc> <7309FCBCAE981B43ABBE69B31C8D213921BE3142CD@EUSAACMS0701.eamcs.ericsson.se> <20120509145717.GN16863@pfrc> <7309FCBCAE981B43ABBE69B31C8D213921BE3144F0@EUSAACMS0701.eamcs.ericsson.se> <20120509182103.GO16863@pfrc>	<B3935C8B-8DF7-4A97-8C71-3564D4FEA05B@tony.li> <20120509184536.GP16863@pfrc>	<BD4ED6BA-0C3F-4E22-908E-94D95C45FCAE@tony.li> <20120509202903.GQ16863@pfrc>	<FC814643-BB29-4C1B-A3E0-40840F786BFA@tony.li> <20120509205102.GR16863@pfrc> <4FAADAE8.8090007@raszuk.net> <28077_1336640239_4FAB82EF_28077_1008_1_53C29892C857584299CBF5D05346208A07872E@PEXCVZYM11.corporate.adroot.infra.ftgroup> <4FAB897D.8040000@raszuk.net> <11733_1336644225_4FAB9280_11733_14189_1_53C29892C857584299CBF5D05346208A0787CD@PEXCVZYM11.corporate.adroot.infra.ftgroup> <4FABB1A4.9050402@raszuk.net>
In-Reply-To: <4FABB1A4.9050402@raszuk.net>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.197.38.1]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2012.5.10.111522
Cc: "grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] draft-ietf-grow-bgp-gshut
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 May 2012 13:06:00 -0000

Robert,

>From: Robert Raszuk [mailto:robert@raszuk.net] Sent: Thursday, May 10, 201=
2 2:17 PM
>
>Bruno,
>
> > 2.   Lower the local preference value of the paths received over the
> >      eBGP session being shut down, upon their propagation over iBGP
> >      sessions.
>
>Looking at the definition of upon:
>
>"upon" - immediately or very soon after
>http://dictionary.reference.com/browse/upon
>
>What is the point of lowering local pref "after" their propagation over
>ibgp session ? To repropagate again ? Shouldn't it s/upon/before/ ?

Actually, IMO timing does matter.=20

And as per your own dictionary, definition of upon also cover
5) on the occasion of
6) on (in any of various senses, used as an equivalent of on)

Both seems applicable to me, but I'm clearly not going to argue. If I were =
the editor, I would pick any proposition from a native English speaker. But=
 I'm not.

Alternatively, what about:

2.   On the iBGP side, (re-) advertises the path received over the eBGP ses=
sion being shutdown with a low LOCAL_PREF.

Bruno

>r.
>
>
>
>> Robert,
>>
>> [Changing the title of the thread to better reflect the subject]
>>
>>> From: Robert Raszuk [mailto:robert@raszuk.net]>Sent: Thursday, May 10, =
2012
>11:25 AM
>>>
>>> Hello Bruno,
>>>
>>> Excellent - this is exactly what we discussed in the past. But when I
>>> read the draft before sending email yesterday unfortunately it does not
>>> say so that clearly at all - regarding the IBGP case ;(
>>
>> If the draft is not clear enough, we always welcome comments. Do you have
>specific comments that we should add in the draft?
>>
>> The following section of the draft recaps the actions to be performed.
>>
>> "4.2.1.3. BGP implementation support for G-Shut
>>
>>
>> [...]
>>
>>     Upon a session shutdown specified as graceful by the operator, a BGP
>>     implementation supporting a g-shut feature SHOULD:
>>
>>     1.   Update all the paths propagated over the corresponding eBGP
>>          session, tagging the GSHUT community to them.  Any subsequent
>>          update sent to the session being gracefully shut down would be
>>          tagged with the GSHUT community.
>>     2.   Lower the local preference value of the paths received over the
>>          eBGP session being shut down, upon their propagation over iBGP
>>          sessions.  Optionally, also tag these paths with an AS specific
>>          g-shut community.  Note that alternatively, the local preference
>>          of the paths received over the eBGP session can be lowered on
>>          the g-shut initiator itself, instead of only when propagating
>>          over its iBGP sessions."
>>
>> At least to me, seems clear that the community is used on the eBGP side =
and
>LOCAL_PREF is used on the iBGP side. Eventually we could to the following
>change:
>> - :s/local preference/LOCAL_PREF
>> - May be start the sentence of 1. and 2. with: "on the eBGP side", "on t=
he
>iBGP side"
>>
>> Others comments welcomed.
>>
>>>          iBGP         eBGP
>>> PE1 ---- P ---- PE2 =3D=3D=3D=3D=3D=3D PE3
>>>
>>> The scenario I had in mind was we are receiving errored UPDATE msg from
>>> PE3 to PE2, PE2 treats as withdraw the parsable NLRIs then for the reast
>>> the thread so far indicated to inject g-shut community.
>>>
>>> While injecting G_SHUT would not hurt and would allow for example PE1 to
>>> propagate it downstream in the same time error handling draft should
>>> IMHO me explicit to say we are advertising from PE2 towards it's AS with
>>> lowest LOCAL_PREF and G_SHUT.
>>>
>>> Example:
>>>
>>> 4.2.1.1.  Pre-configuration
>>>
>>>     On each ASBR supporting the g-shut procedure, an outbound BGP route
>>>     policy is applied on all iBGP sessions of the ASBR, that:
>>>     o    matches the g-shut community
>>>     o    sets the local-pref of the paths tagged with the g-shut
>>>          community to a low value
>>>
>>> Here in out case we do not match on g-shut as g-shut is not received
>>>from EBGP.
>>>
>>> Also perhaps it would be great to just copy and paste the quote from the
>>> previous email directly to a deployment section of the draft.
>>
>> Sorry the given the amount of emails, could you please be a little more
>specific? (e.g. which quote).
>>
>> Thanks for the useful comments.
>> Best regards,
>> Bruno
>>
>>> Best regards,
>>> R.
>>>
>>>
>>>> Robert,
>>>>
>>>>
>>>>> From: Robert Raszuk Sent: Wednesday, May 09, 2012 11:00 PM
>>>>>
>>>>> Jeff,
>>>>>
>>>>> I do not understand why we are not going to re-advertise "good" routes
>>>>> with lowest local preference which would not result in holes of some
>>>>> boxes understanding g-shut community and some not.
>>>>
>>>> What you propose (using LOCAL_PREF) is what the g-shut draft also prop=
ose.
>>>>
>>>>> In fact I spoke to Bruno in the past on that and I was hoping we all
>>>>> converged that g-shut community would be used only on the EBGP side to
>>>>> indicate to the peer that it should in turn lower local pref on his
>>>>> side.
>>>>
>>>> The g-shut community has always been used to signal the ghsut only on =
the
>>> eBGP side. On the iBGP side, LOCAL_PREF has always been used.
>>>>
>>>>> Apparently g-shut draft still calls for this new community to be
>>>>> used both on iBGP and eBGP side.
>>>>
>>>> On the iBGP side, LOCAL_PREF is used to lower the preference of the g-=
shut
>>> draft.
>>>> In _addition_ to this, the g-shut community is attached for _informati=
onal_
>>> purpose. Because some AS internal BGP policy may have a need to know th=
at
>the
>>> route is being g-shut. And it's cleaner to use a community to provide t=
he
>root
>>> cause rather than try to guess from the low LOCAL_PREF the root cause.
>>>>
>>>> Regards,
>>>> Bruno
>>>>
>>>>
>>>>>
>>>>> Regards,
>>>>> R.
>>>>>
>>>>>> On Wed, May 09, 2012 at 03:32:52PM -0500, Tony Li wrote:
>>>>>>> Understood.  I have no issues with withdrawn routes.  The issue is =
with
>g-
>>>>> shut routes that continue to sink traffic.
>>>>>>
>>>>>> Perhaps I'm unclear on your reservations.
>>>>>>
>>>>>> If we don't go through something like graceful shutdown and leave the
>>>>>> peering session up, we're potentially going to pull significantly mo=
re
>>>>>> traffic toward the "bad" peering session than if we didn't do such a
>thing.
>>>>>>
>>>>>> -- Jeff
>>>>>> _______________________________________________
>>>>>> GROW mailing list
>>>>>> GROW@ietf.org
>>>>>> https://www.ietf.org/mailman/listinfo/grow
>>>>>>
>>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> GROW mailing list
>>>>> GROW@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/grow
>>>>
>>>>
>>>
>__________________________________________________________________________=
_____
>>> __________________________________________
>>>>
>>>> Ce message et ses pieces jointes peuvent contenir des informations
>>> confidentielles ou privilegiees et ne doivent donc
>>>> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez=
 recu
>>> ce message par erreur, veuillez le signaler
>>>> a l'expediteur et le detruire ainsi que les pieces jointes. Les messag=
es
>>> electroniques etant susceptibles d'alteration,
>>>> France Telecom - Orange decline toute responsabilite si ce message a e=
te
>>> altere, deforme ou falsifie. Merci.
>>>>
>>>> This message and its attachments may contain confidential or privileged
>>> information that may be protected by law;
>>>> they should not be distributed, used or copied without authorisation.
>>>> If you have received this email in error, please notify the sender and
>delete
>>> this message and its attachments.
>>>> As emails may be altered, France Telecom - Orange is not liable for
>messages
>>> that have been modified, changed or falsified.
>>>> Thank you.
>>>>
>>>>
>>>>
>>
>>
>>
>__________________________________________________________________________=
_____
>__________________________________________
>>
>> Ce message et ses pieces jointes peuvent contenir des informations
>confidentielles ou privilegiees et ne doivent donc
>> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez r=
ecu
>ce message par erreur, veuillez le signaler
>> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages
>electroniques etant susceptibles d'alteration,
>> France Telecom - Orange decline toute responsabilite si ce message a ete
>altere, deforme ou falsifie. Merci.
>>
>> This message and its attachments may contain confidential or privileged
>information that may be protected by law;
>> they should not be distributed, used or copied without authorisation.
>> If you have received this email in error, please notify the sender and d=
elete
>this message and its attachments.
>> As emails may be altered, France Telecom - Orange is not liable for mess=
ages
>that have been modified, changed or falsified.
>> Thank you.
>>
>>
>>


___________________________________________________________________________=
______________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu=
 ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el=
ectroniques etant susceptibles d'alteration,
France Telecom - Orange decline toute responsabilite si ce message a ete al=
tere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged inf=
ormation that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and dele=
te this message and its attachments.
As emails may be altered, France Telecom - Orange is not liable for message=
s that have been modified, changed or falsified.
Thank you.


From robert@raszuk.net  Thu May 10 06:23:00 2012
Return-Path: <robert@raszuk.net>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7894D21F864E for <grow@ietfa.amsl.com>; Thu, 10 May 2012 06:23:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.487
X-Spam-Level: 
X-Spam-Status: No, score=-2.487 tagged_above=-999 required=5 tests=[AWL=0.112,  BAYES_00=-2.599]
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 vpLlLCFzkaRi for <grow@ietfa.amsl.com>; Thu, 10 May 2012 06:23:00 -0700 (PDT)
Received: from mail1310.opentransfer.com (mail1310.opentransfer.com [76.162.254.103]) by ietfa.amsl.com (Postfix) with ESMTP id B394521F863F for <grow@ietf.org>; Thu, 10 May 2012 06:22:59 -0700 (PDT)
Received: (qmail 6091 invoked by uid 399); 10 May 2012 13:22:59 -0000
Received: from unknown (HELO ?192.168.1.91?) (pbs:robert@raszuk.net@83.31.230.182) by mail1310.opentransfer.com with ESMTPM; 10 May 2012 13:22:59 -0000
X-Originating-IP: 83.31.230.182
Message-ID: <4FABC12C.4050201@raszuk.net>
Date: Thu, 10 May 2012 15:22:52 +0200
From: Robert Raszuk <robert@raszuk.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: bruno.decraene@orange.com, Jakob Heitz <jakob.heitz@ericsson.com>,  Jeffrey Haas <jhaas@pfrc.org>
References: <20120507175757.GB16863@pfrc> <7309FCBCAE981B43ABBE69B31C8D213921BE3142CD@EUSAACMS0701.eamcs.ericsson.se> <20120509145717.GN16863@pfrc> <7309FCBCAE981B43ABBE69B31C8D213921BE3144F0@EUSAACMS0701.eamcs.ericsson.se> <20120509182103.GO16863@pfrc>	<B3935C8B-8DF7-4A97-8C71-3564D4FEA05B@tony.li> <20120509184536.GP16863@pfrc>	<BD4ED6BA-0C3F-4E22-908E-94D95C45FCAE@tony.li> <20120509202903.GQ16863@pfrc>	<FC814643-BB29-4C1B-A3E0-40840F786BFA@tony.li> <20120509205102.GR16863@pfrc> <4FAADAE8.8090007@raszuk.net> <28077_1336640239_4FAB82EF_28077_1008_1_53C29892C857584299CBF5D05346208A07872E@PEXCVZYM11.corporate.adroot.infra.ftgroup> <4FAB897D.8040000@raszuk.net> <11733_1336644225_4FAB9280_11733_14189_1_53C29892C857584299CBF5D05346208A0787CD@PEXCVZYM11.corporate.adroot.infra.ftgroup> <4FABB1A4.9050402@raszuk.net> <30550_1336655157_4FABBD35_30550_3926_3_53C29892C857584299CBF5D05346208A0788AC@PEXCVZYM11.corporate.adroot.infra.ftgroup>
In-Reply-To: <30550_1336655157_4FABBD35_30550_3926_3_53C29892C857584299CBF5D05346208A0788AC@PEXCVZYM11.corporate.adroot.infra.ftgroup>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] draft-ietf-grow-bgp-gshut
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: robert@raszuk.net
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 May 2012 13:23:00 -0000

Bruno,

 > 2.   On the iBGP side, (re-) advertises the path received over
 > the eBGP session being shutdown with a low LOCAL_PREF.

Sounds good.

Btw what is "low" ? Is 0 low ? Is 5 low ? Should we at least recommend 
some value if you are assuming automation in g-shut to local pref 
translation ?

Jakob, Jeff,

 > This is for ebgp only, not ibgp. right?

I was assuming this is mostly for ibgp.

If this is also for ebgp are you suggesting that we will receive from 
the peer a single error in UPDATE message for SAFI X/X and then it will 
trigger full re-advertisement of all of our routes for all of our SAFIs 
over such session to this peer with g-shut ?


The way I read what Jeff proposed is this:

1. We are receiving N errors and just treat-as-withdraw or drop errored 
optional attributes when applicable

2. When N becomes more then X send g-shut to eBGP peer and lower local 
pref towards iBGP then re-advertise

3. After time T shut EBGP session.

Questions: What is value of X and T above ?

Thx,
R.







From bruno.decraene@orange.com  Thu May 10 07:09:27 2012
Return-Path: <bruno.decraene@orange.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D05B21F864D for <grow@ietfa.amsl.com>; Thu, 10 May 2012 07:09:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.05
X-Spam-Level: 
X-Spam-Status: No, score=-2.05 tagged_above=-999 required=5 tests=[AWL=0.548,  BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001]
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 C2Vuipwzke62 for <grow@ietfa.amsl.com>; Thu, 10 May 2012 07:09:26 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias91.francetelecom.com [193.251.215.91]) by ietfa.amsl.com (Postfix) with ESMTP id 6940021F8657 for <grow@ietf.org>; Thu, 10 May 2012 07:09:26 -0700 (PDT)
Received: from omfedm07.si.francetelecom.fr (unknown [xx.xx.xx.3]) by omfedm11.si.francetelecom.fr (ESMTP service) with ESMTP id 809473B44C9; Thu, 10 May 2012 16:09:25 +0200 (CEST)
Received: from Exchangemail-eme1.itn.ftgroup (unknown [10.114.1.186]) by omfedm07.si.francetelecom.fr (ESMTP service) with ESMTP id 5E0764C06B; Thu, 10 May 2012 16:09:22 +0200 (CEST)
Received: from PEXCVZYM11.corporate.adroot.infra.ftgroup ([fe80::a441:e6a9:6143:6f0f]) by PEXCVZYH01.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.02.0247.003; Thu, 10 May 2012 16:09:22 +0200
From: <bruno.decraene@orange.com>
To: "robert@raszuk.net" <robert@raszuk.net>
Thread-Topic: draft-ietf-grow-bgp-gshut
Thread-Index: AQHNLrAAKEj+BoTPikOz3JMguGF/6ZbDClmg
Date: Thu, 10 May 2012 14:09:22 +0000
Message-ID: <30552_1336658962_4FABCC12_30552_15241_1_53C29892C857584299CBF5D05346208A07893A@PEXCVZYM11.corporate.adroot.infra.ftgroup>
References: <20120507175757.GB16863@pfrc> <7309FCBCAE981B43ABBE69B31C8D213921BE3142CD@EUSAACMS0701.eamcs.ericsson.se> <20120509145717.GN16863@pfrc> <7309FCBCAE981B43ABBE69B31C8D213921BE3144F0@EUSAACMS0701.eamcs.ericsson.se> <20120509182103.GO16863@pfrc>	<B3935C8B-8DF7-4A97-8C71-3564D4FEA05B@tony.li> <20120509184536.GP16863@pfrc>	<BD4ED6BA-0C3F-4E22-908E-94D95C45FCAE@tony.li> <20120509202903.GQ16863@pfrc>	<FC814643-BB29-4C1B-A3E0-40840F786BFA@tony.li> <20120509205102.GR16863@pfrc> <4FAADAE8.8090007@raszuk.net> <28077_1336640239_4FAB82EF_28077_1008_1_53C29892C857584299CBF5D05346208A07872E@PEXCVZYM11.corporate.adroot.infra.ftgroup> <4FAB897D.8040000@raszuk.net> <11733_1336644225_4FAB9280_11733_14189_1_53C29892C857584299CBF5D05346208A0787CD@PEXCVZYM11.corporate.adroot.infra.ftgroup> <4FABB1A4.9050402@raszuk.net> <30550_1336655157_4FABBD35_30550_3926_3_53C29892C857584299CBF5D05346208A0788AC@PEXCVZYM11.corporate.adroot.infra.ftgroup> <4FABC12C.4050201@raszuk.net>
In-Reply-To: <4FABC12C.4050201@raszuk.net>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.197.38.1]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2012.5.10.131221
Cc: "grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] draft-ietf-grow-bgp-gshut
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 May 2012 14:09:27 -0000

Robert,

>From: Robert Raszuk [mailto:robert@raszuk.net] >Sent: Thursday, May 10, 20=
12 3:23 PM
>
>Bruno,
>
> > 2.   On the iBGP side, (re-) advertises the path received over
> > the eBGP session being shutdown with a low LOCAL_PREF.
>
>Sounds good.

Great.


>Btw what is "low" ?=20

Low enough such as a backup path will be preferred. We can add this in the =
draft.

> Is 0 low ? Is 5 low ? Should we at least recommend
>some value if you are assuming automation in g-shut to local pref
>translation ?

Local pref value are choosen independantly by each AS. There is no way we c=
an pick a value -except 0 may be- which will work all the time. Even 0 may =
not be perfect:
- 0 could already be used by others path we should never be choosen even du=
ring a ghsut.
- In an Internet network, to optimize the convergence steps and the transie=
nt behavior we should/may pick the lower value assigned to the kind of rela=
tionship being gshut (e.g. peer). Indeed, if we gshut an eBGP session with =
a peering policy, BGP may transiently pick any path including a path from a=
 transit provider. This would lead to a transient withdraw to peers due to =
policy restriction (transit path are not advertised to peer). This is subop=
timal. OTOH an ISP may not want to spend time/money to optimize this...

In short: local_pref value are a local policy.

We can clearly discuss this in the draft, but OTOH a least one person had c=
ommented that the draft was too long and could fit in 1-2 pages.

Bruno

>Jakob, Jeff,
>
> > This is for ebgp only, not ibgp. right?
>
>I was assuming this is mostly for ibgp.
>
>If this is also for ebgp are you suggesting that we will receive from
>the peer a single error in UPDATE message for SAFI X/X and then it will
>trigger full re-advertisement of all of our routes for all of our SAFIs
>over such session to this peer with g-shut ?
>
>
>The way I read what Jeff proposed is this:
>
>1. We are receiving N errors and just treat-as-withdraw or drop errored
>optional attributes when applicable
>
>2. When N becomes more then X send g-shut to eBGP peer and lower local
>pref towards iBGP then re-advertise
>
>3. After time T shut EBGP session.
>
>Questions: What is value of X and T above ?
>
>Thx,
>R.
>
>
>
>
>


___________________________________________________________________________=
______________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu=
 ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el=
ectroniques etant susceptibles d'alteration,
France Telecom - Orange decline toute responsabilite si ce message a ete al=
tere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged inf=
ormation that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and dele=
te this message and its attachments.
As emails may be altered, France Telecom - Orange is not liable for message=
s that have been modified, changed or falsified.
Thank you.


From internet-drafts@ietf.org  Sat May 12 03:42:21 2012
Return-Path: <internet-drafts@ietf.org>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E305F21F8546; Sat, 12 May 2012 03:42:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.442
X-Spam-Level: 
X-Spam-Status: No, score=-102.442 tagged_above=-999 required=5 tests=[AWL=0.157, BAYES_00=-2.599, 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 rW3i2bULeo49; Sat, 12 May 2012 03:42:21 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7ECE021F8510; Sat, 12 May 2012 03:42:21 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.02
Message-ID: <20120512104221.4661.63724.idtracker@ietfa.amsl.com>
Date: Sat, 12 May 2012 03:42:21 -0700
Cc: grow@ietf.org
Subject: [GROW] I-D Action: draft-ietf-grow-private-ip-sp-cores-04.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 12 May 2012 10:42:22 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies. This draft is a work item of the Global Routing Operations Working Gro=
up of the IETF.

	Title           : Issues with Private IP Addressing in the Internet
	Author(s)       : Anthony Kirkham
	Filename        : draft-ietf-grow-private-ip-sp-cores-04.txt
	Pages           : 14
	Date            : 2012-05-12

   The purpose of this document is to provide a discussion of the
   potential problems of using private, RFC1918, or non-globally-
   routable addressing within the core of an SP network.  The discussion
   focuses on link addresses and to a small extent loopback addresses.
   While many of the issues are well recognised within the ISP
   community, there appears to be no document that collectively
   describes the issues.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-grow-private-ip-sp-cores-04.=
txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-grow-private-ip-sp-cores-04.t=
xt

The IETF datatracker page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-grow-private-ip-sp-cores/


From christopher.morrow@gmail.com  Mon May 14 09:51:14 2012
Return-Path: <christopher.morrow@gmail.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6ED9A11E807F for <grow@ietfa.amsl.com>; Mon, 14 May 2012 09:51:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.533
X-Spam-Level: 
X-Spam-Status: No, score=-103.533 tagged_above=-999 required=5 tests=[AWL=0.066, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, 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 zk5KAyGC+d1V for <grow@ietfa.amsl.com>; Mon, 14 May 2012 09:51:14 -0700 (PDT)
Received: from mail-qc0-f172.google.com (mail-qc0-f172.google.com [209.85.216.172]) by ietfa.amsl.com (Postfix) with ESMTP id CB03811E8074 for <grow@ietf.org>; Mon, 14 May 2012 09:51:13 -0700 (PDT)
Received: by qcsq13 with SMTP id q13so4257867qcs.31 for <grow@ietf.org>; Mon, 14 May 2012 09:51:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=TRmvfIYkLgyZCBgD4kik6M1GAK/KYWQkl4nnA5ZkRfI=; b=BMOEdD9OxbzLVQaJddqQSullwMjakpjc65QH/M/LNL5vp6RsMafYbFDowyZ4Sslp2O 6xeygc0jtAPqkReOnr7/xFBR0nGbgh1V80bnRUZYoZ/q85jv3jSGDVcHiN+aqLVDJLUE wyFsq21MqCBbuDtcn99JIN6nD6HEWmNKIZ26D0yV9fuRItD+CENG1EodP0CRqYE5DPCI KjuPmu+WqV5nmLU+kiogKmLM4+jqAZakAG1FrGFkiBXlcqQ/e52K8YLGHFmw8p3+Zfwd xl9sqg0A8zmu9vRvz/0PvWX70T7VgvprvTs3oepdnIS9W9tOG4n1YnOiX6+eMveCk7P2 /FvA==
MIME-Version: 1.0
Received: by 10.60.7.200 with SMTP id l8mr1769342oea.52.1337014271957; Mon, 14 May 2012 09:51:11 -0700 (PDT)
Received: by 10.182.166.71 with HTTP; Mon, 14 May 2012 09:51:11 -0700 (PDT)
Date: Mon, 14 May 2012 12:51:11 -0400
Message-ID: <CAL9jLaZd_PUN3Y+Uj+n5roDfXoD_Raw1bn+QpcYQ++6452fppg@mail.gmail.com>
From: Christopher Morrow <christopher.morrow@gmail.com>
To: grow-chairs@tools.ietf.org, grow-ads@tools.ietf.org,  "grow@ietf.org grow@ietf.org" <grow@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Subject: [GROW] WGLC: draft-ietf-grow-simple-va
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 May 2012 16:51:14 -0000

Helo wg folk,
Since we (I really I think) messed up the last WGLC for this document,
can we get another attempt at this now?
  <http://www.ietf.org/internet-drafts/draft-ietf-grow-simple-va-05.txt>

Abstract:
     The continued growth in the Default Free Routing Table (DFRT)
   stresses the global routing system in a number of ways.  One of the
   most costly stresses is FIB size: ISPs often must upgrade router
   hardware simply because the FIB has run out of space, and router
   vendors must design routers that have adequate FIB.

   FIB suppression is an approach to relieving stress on the FIB by NOT
   loading selected RIB entries into the FIB.  Simple Virtual
   Aggregation (S-VA) is a simple form of Virtual Aggregation (VA) that
   allows any and all edge routers to shrink their RIB and FIB
   requirements substantially and therefore increase their useful
   lifetime.

   S-VA does not increase FIB requirements for core routers.  S-VA is
   extremely easy to configure considerably more so than the various
   tricks done today to extend the life of edge routers.  S-VA can be
   deployed autonomously by an ISP (cooperation between ISPs is not
   required), and can co-exist with legacy routers in the ISP.

If we could finish this 5/28/2012 || 28/5/2012 that would be good.

-Chris

From robert@raszuk.net  Mon May 14 09:55:19 2012
Return-Path: <robert@raszuk.net>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 93DEC11E8088 for <grow@ietfa.amsl.com>; Mon, 14 May 2012 09:55:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.504
X-Spam-Level: 
X-Spam-Status: No, score=-2.504 tagged_above=-999 required=5 tests=[AWL=0.095,  BAYES_00=-2.599]
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 88QoYB15VQWr for <grow@ietfa.amsl.com>; Mon, 14 May 2012 09:55:19 -0700 (PDT)
Received: from mail1310.opentransfer.com (mail1310.opentransfer.com [76.162.254.103]) by ietfa.amsl.com (Postfix) with ESMTP id C8F5011E8087 for <grow@ietf.org>; Mon, 14 May 2012 09:55:18 -0700 (PDT)
Received: (qmail 11250 invoked by uid 399); 14 May 2012 16:55:18 -0000
Received: from unknown (HELO ?192.168.1.91?) (pbs:m42@mojaklasa.info@83.31.228.222) by mail1310.opentransfer.com with ESMTPM; 14 May 2012 16:55:18 -0000
X-Originating-IP: 83.31.228.222
Message-ID: <4FB138F6.5060503@raszuk.net>
Date: Mon, 14 May 2012 18:55:18 +0200
From: Robert Raszuk <robert@raszuk.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: Christopher Morrow <christopher.morrow@gmail.com>
References: <CAL9jLaZd_PUN3Y+Uj+n5roDfXoD_Raw1bn+QpcYQ++6452fppg@mail.gmail.com>
In-Reply-To: <CAL9jLaZd_PUN3Y+Uj+n5roDfXoD_Raw1bn+QpcYQ++6452fppg@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "grow@ietf.org grow@ietf.org" <grow@ietf.org>, grow-ads@tools.ietf.org, grow-chairs@tools.ietf.org
Subject: Re: [GROW] WGLC: draft-ietf-grow-simple-va
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: robert@raszuk.net
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 May 2012 16:55:19 -0000

Support.

Thx,
R.

> Helo wg folk,
> Since we (I really I think) messed up the last WGLC for this document,
> can we get another attempt at this now?
>    <http://www.ietf.org/internet-drafts/draft-ietf-grow-simple-va-05.txt>
>
> Abstract:
>       The continued growth in the Default Free Routing Table (DFRT)
>     stresses the global routing system in a number of ways.  One of the
>     most costly stresses is FIB size: ISPs often must upgrade router
>     hardware simply because the FIB has run out of space, and router
>     vendors must design routers that have adequate FIB.
>
>     FIB suppression is an approach to relieving stress on the FIB by NOT
>     loading selected RIB entries into the FIB.  Simple Virtual
>     Aggregation (S-VA) is a simple form of Virtual Aggregation (VA) that
>     allows any and all edge routers to shrink their RIB and FIB
>     requirements substantially and therefore increase their useful
>     lifetime.
>
>     S-VA does not increase FIB requirements for core routers.  S-VA is
>     extremely easy to configure considerably more so than the various
>     tricks done today to extend the life of edge routers.  S-VA can be
>     deployed autonomously by an ISP (cooperation between ISPs is not
>     required), and can co-exist with legacy routers in the ISP.
>
> If we could finish this 5/28/2012 || 28/5/2012 that would be good.
>
> -Chris
> _______________________________________________
> GROW mailing list
> GROW@ietf.org
> https://www.ietf.org/mailman/listinfo/grow
>
>


From nick@inex.ie  Mon May 14 10:15:12 2012
Return-Path: <nick@inex.ie>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 822D811E8088 for <grow@ietfa.amsl.com>; Mon, 14 May 2012 10:15:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.524
X-Spam-Level: 
X-Spam-Status: No, score=-2.524 tagged_above=-999 required=5 tests=[AWL=0.075,  BAYES_00=-2.599]
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 OcgB1FilLAyY for <grow@ietfa.amsl.com>; Mon, 14 May 2012 10:15:12 -0700 (PDT)
Received: from mail.acquirer.com (mail.acquirer.com [IPv6:2a03:8900:0:100::5]) by ietfa.amsl.com (Postfix) with ESMTP id C8AC511E8087 for <grow@ietf.org>; Mon, 14 May 2012 10:15:11 -0700 (PDT)
X-Envelope-To: <grow@ietf.org>
Received: from cupcake.local (inet-gw.acquirer.com [87.198.142.10]) (authenticated bits=0) by mail.acquirer.com (8.14.4/8.14.4) with ESMTP id q4EHEYS3031589 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <grow@ietf.org>; Mon, 14 May 2012 18:14:34 +0100 (IST) (envelope-from nick@inex.ie)
Message-ID: <4FB13D9D.3040500@inex.ie>
Date: Mon, 14 May 2012 18:15:09 +0100
From: Nick Hilliard <nick@inex.ie>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: grow@ietf.org
References: <CAL9jLaZd_PUN3Y+Uj+n5roDfXoD_Raw1bn+QpcYQ++6452fppg@mail.gmail.com>
In-Reply-To: <CAL9jLaZd_PUN3Y+Uj+n5roDfXoD_Raw1bn+QpcYQ++6452fppg@mail.gmail.com>
X-Enigmail-Version: 1.4.1
X-Company-Info-1: Internet Neutral Exchange Association Limited. Registered in Ireland No. 253804
X-Company-Info-2: Registered Offices: 1-2, Marino Mart, Fairview, Dublin 3
X-Company-Info-3: Internet Neutral Exchange Association Limited is limited by guarantee
X-Company-Info-4: Offices: 4027 Kingswood Road, Citywest, Dublin 24.
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [GROW] WGLC: draft-ietf-grow-simple-va
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 May 2012 17:15:12 -0000

nits:

- please run: s/it's/its/s on the document.

- "In some protocol's implementations for example BGP loc-RIB can be
further...".  Change to "For example, in some protocol implementations BGP
loc-RIB can be further..."

- "Let's illustrate...".  Too informal.  "We illustrate..."

- "Another deploymet consideration" => "Another deployment consideration"

- "Therefor under the above intra" => "Therefore under the above intra"

Most of the document looks fine.  However, there is one content omission,
namely that there is no analysis of what happens when a compressed RIB
undergoes a topology change which modifies a bunch of next-hops.  If this
happens, the fib compression can explode with an upper bound of the
uncompressed size.

This may cause Interesting and Unexpected side effects - e.g. routers
falling over due to topology changes and so forth.  From an operational
point of view, I think this is probably important enough to warrant a
mention in the draft.

Nick

From nick@inex.ie  Mon May 14 10:16:48 2012
Return-Path: <nick@inex.ie>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7DF5E11E808E for <grow@ietfa.amsl.com>; Mon, 14 May 2012 10:16:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.539
X-Spam-Level: 
X-Spam-Status: No, score=-2.539 tagged_above=-999 required=5 tests=[AWL=0.060,  BAYES_00=-2.599]
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 hYT3HMrqox5w for <grow@ietfa.amsl.com>; Mon, 14 May 2012 10:16:48 -0700 (PDT)
Received: from mail.acquirer.com (mail.acquirer.com [IPv6:2a03:8900:0:100::5]) by ietfa.amsl.com (Postfix) with ESMTP id DD7F411E808A for <grow@ietf.org>; Mon, 14 May 2012 10:16:47 -0700 (PDT)
X-Envelope-To: <grow@ietf.org>
Received: from cupcake.local (inet-gw.acquirer.com [87.198.142.10]) (authenticated bits=0) by mail.acquirer.com (8.14.4/8.14.4) with ESMTP id q4EHGBpT031606 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <grow@ietf.org>; Mon, 14 May 2012 18:16:12 +0100 (IST) (envelope-from nick@inex.ie)
Message-ID: <4FB13DFE.3020605@inex.ie>
Date: Mon, 14 May 2012 18:16:46 +0100
From: Nick Hilliard <nick@inex.ie>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: grow@ietf.org
References: <CAL9jLaZd_PUN3Y+Uj+n5roDfXoD_Raw1bn+QpcYQ++6452fppg@mail.gmail.com> <4FB13D9D.3040500@inex.ie>
In-Reply-To: <4FB13D9D.3040500@inex.ie>
X-Enigmail-Version: 1.4.1
X-Company-Info-1: Internet Neutral Exchange Association Limited. Registered in Ireland No. 253804
X-Company-Info-2: Registered Offices: 1-2, Marino Mart, Fairview, Dublin 3
X-Company-Info-3: Internet Neutral Exchange Association Limited is limited by guarantee
X-Company-Info-4: Offices: 4027 Kingswood Road, Citywest, Dublin 24.
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [GROW] WGLC: draft-ietf-grow-simple-va
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 May 2012 17:16:48 -0000

On 14/05/2012 18:15, Nick Hilliard wrote:
> nits:

another nit:

"different from the one assinged to VA-prefix" => "different from the one
assigned to VA-prefix".

There are possibly more spelling mistakes which I haven't caught.  Could I
suggest xml -> html -> cut-n-paste -> Microsoft word -> spell check?

Nick

From robert@raszuk.net  Mon May 14 10:46:06 2012
Return-Path: <robert@raszuk.net>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 031AF21F88F7 for <grow@ietfa.amsl.com>; Mon, 14 May 2012 10:46:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.508
X-Spam-Level: 
X-Spam-Status: No, score=-2.508 tagged_above=-999 required=5 tests=[AWL=0.091,  BAYES_00=-2.599]
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 YAQhhHYwGaxe for <grow@ietfa.amsl.com>; Mon, 14 May 2012 10:46:05 -0700 (PDT)
Received: from mail1310.opentransfer.com (mail1310.opentransfer.com [76.162.254.103]) by ietfa.amsl.com (Postfix) with ESMTP id 014CD21F8925 for <grow@ietf.org>; Mon, 14 May 2012 10:46:04 -0700 (PDT)
Received: (qmail 8001 invoked by uid 399); 14 May 2012 17:46:04 -0000
Received: from unknown (HELO ?192.168.1.91?) (pbs:robert@raszuk.net@83.31.228.222) by mail1310.opentransfer.com with ESMTPM; 14 May 2012 17:46:04 -0000
X-Originating-IP: 83.31.228.222
Message-ID: <4FB144D4.9060308@raszuk.net>
Date: Mon, 14 May 2012 19:45:56 +0200
From: Robert Raszuk <robert@raszuk.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: Nick Hilliard <nick@inex.ie>
References: <CAL9jLaZd_PUN3Y+Uj+n5roDfXoD_Raw1bn+QpcYQ++6452fppg@mail.gmail.com> <4FB13D9D.3040500@inex.ie>
In-Reply-To: <4FB13D9D.3040500@inex.ie>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: grow@ietf.org
Subject: Re: [GROW] WGLC: draft-ietf-grow-simple-va
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: robert@raszuk.net
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 May 2012 17:46:06 -0000

Hello Nick,

Many thx for reading the document and your comments. Please see below:

> nits:
>
> - please run: s/it's/its/s on the document.

Fixed.

> - "In some protocol's implementations for example BGP loc-RIB can be
> further...".  Change to "For example, in some protocol implementations BGP
> loc-RIB can be further..."

Fixed.

> - "Let's illustrate...".  Too informal.  "We illustrate..."

Fixed.

> - "Another deploymet consideration" =>  "Another deployment consideration"

Fixed.

> - "Therefor under the above intra" =>  "Therefore under the above intra"

Fixed.

> "different from the one assinged to VA-prefix" => "different from the one
> assigned to VA-prefix".

Fixed.

> There are possibly more spelling mistakes which I haven't caught.  Could I
> suggest xml -> html -> cut-n-paste -> Microsoft word -> spell check?

Done.

> Most of the document looks fine.  However, there is one content omission,
> namely that there is no analysis of what happens when a compressed RIB
> undergoes a topology change which modifies a bunch of next-hops.  If this
> happens, the fib compression can explode with an upper bound of the
> uncompressed size.

The point is that we are not compressing RIB nor FIB here. The entire 
mechanism really operates at the BGP level and suppresses overlapping 
prefixes before they end up in RIB.

That's very different and much simpler then any algorithm which would 
compress RIB or FIB. IGP topology changes have absolutely no bearing on 
the BGP suppression.

BGP will continue to rerun it's best path and while attempting to 
install the new set of best paths to RIB either suppress them or walk 
back and install those previously suppressed depending on the next hop 
value of given prefix which has changed due to topology change.

 > This may cause Interesting and Unexpected side effects - e.g. routers
 > falling over due to topology changes and so forth.  From an
 > operational point of view, I think this is probably important enough
 > to warrant a mention in the draft.

The implementation we have tested it with did efficient walk back in the 
above case as compared with normal unsuppressed case.

Btw the same walk back is used when BGP path becomes best which prefix 
length is between less specific and suppressed more specific.

Those requirements are necessary to remove burden from operator to match 
the topology to the knob. The assumption is that it should work in nay 
topology. However if one would deploy it in the edged of the POP most of 
the below would never apply as POP to core ABRs would be always less 
specific for all prefixes coming from other POPs. (Just a deployment 
option).

Many thx for your review. Please let me know if there are any other 
points for clarification or fix.

Best regards,
R.

PS. I have placed version -06 with above fixes into temporary location: 
http://goo.gl/yq7fF

From shtsuchi@cisco.com  Mon May 14 18:44:36 2012
Return-Path: <shtsuchi@cisco.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8C81121F8920 for <grow@ietfa.amsl.com>; Mon, 14 May 2012 18:44:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 7FMyC4DRmQuk for <grow@ietfa.amsl.com>; Mon, 14 May 2012 18:44:36 -0700 (PDT)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) by ietfa.amsl.com (Postfix) with ESMTP id 0A9F621F890B for <grow@ietf.org>; Mon, 14 May 2012 18:44:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=shtsuchi@cisco.com; l=1624; q=dns/txt; s=iport; t=1337046276; x=1338255876; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=+nQN9ZnQAWZuNrhMreMkgmRM8jNLe7GpR1i0GuiLQII=; b=RTs2Zv726vIQzG7ke7aktEJlYd4kZnEcc9R5KTWVJZZRzsqRNORgVt6W bXtdLl/IyF36BU9BW2tTBaqkM3B/1OgRgGDKkTR8LTbm8IAhYzo0D86z8 PuLY8AAbQ/3lFzRwaqQTLi0aPMpK5StIIFk4nW4aacvKjPQgnKqFrOxRw Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AoYFAEG0sU+tJV2c/2dsb2JhbABEgx6CXa19gQeCFQEBAQQBAQEPAQ4BTAoBEAsYAQMFFgoDAgkDAgECARUwBg0BBQIBAQUQCYdsC5sRjREBkneBLYllglqCC4EbBIhijRuFdYhigWmCeA
X-IronPort-AV: E=Sophos;i="4.75,590,1330905600"; d="scan'208";a="83210141"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-5.cisco.com with ESMTP; 15 May 2012 01:44:35 +0000
Received: from xhc-aln-x08.cisco.com (xhc-aln-x08.cisco.com [173.36.12.82]) by rcdn-core-5.cisco.com (8.14.3/8.14.3) with ESMTP id q4F1iZF7032461;  Tue, 15 May 2012 01:44:35 GMT
Received: from [10.141.32.141] (173.36.12.73) by xhc-aln-x08.cisco.com (173.36.12.82) with Microsoft SMTP Server (TLS) id 14.2.298.4; Mon, 14 May 2012 20:44:34 -0500
Message-ID: <4FB1B4FD.1070202@cisco.com>
Date: Tue, 15 May 2012 10:44:29 +0900
From: Shishio Tsuchiya <shtsuchi@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: <christopher.morrow@gmail.com>
References: <CAL9jLaZd_PUN3Y+Uj+n5roDfXoD_Raw1bn+QpcYQ++6452fppg@mail.gmail.com>
In-Reply-To: <CAL9jLaZd_PUN3Y+Uj+n5roDfXoD_Raw1bn+QpcYQ++6452fppg@mail.gmail.com>
Content-Type: text/plain; charset="ISO-2022-JP"
Content-Transfer-Encoding: 7bit
X-Originating-IP: [173.36.12.73]
X-TM-AS-Product-Ver: SMEX-10.2.0.1135-6.800.1017-18904.007
X-TM-AS-Result: No--12.060500-8.000000-31
X-TM-AS-User-Approved-Sender: No
X-TM-AS-User-Blocked-Sender: No
Cc: grow@ietf.org, grow-ads@tools.ietf.org, grow-chairs@tools.ietf.org
Subject: Re: [GROW] WGLC: draft-ietf-grow-simple-va
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 May 2012 01:44:36 -0000

Support.

Regards,
-Shishio

(2012/05/15 1:51), Christopher Morrow wrote:
> Helo wg folk,
> Since we (I really I think) messed up the last WGLC for this document,
> can we get another attempt at this now?
>    <http://www.ietf.org/internet-drafts/draft-ietf-grow-simple-va-05.txt>
> 
> Abstract:
>       The continued growth in the Default Free Routing Table (DFRT)
>     stresses the global routing system in a number of ways.  One of the
>     most costly stresses is FIB size: ISPs often must upgrade router
>     hardware simply because the FIB has run out of space, and router
>     vendors must design routers that have adequate FIB.
> 
>     FIB suppression is an approach to relieving stress on the FIB by NOT
>     loading selected RIB entries into the FIB.  Simple Virtual
>     Aggregation (S-VA) is a simple form of Virtual Aggregation (VA) that
>     allows any and all edge routers to shrink their RIB and FIB
>     requirements substantially and therefore increase their useful
>     lifetime.
> 
>     S-VA does not increase FIB requirements for core routers.  S-VA is
>     extremely easy to configure considerably more so than the various
>     tricks done today to extend the life of edge routers.  S-VA can be
>     deployed autonomously by an ISP (cooperation between ISPs is not
>     required), and can co-exist with legacy routers in the ISP.
> 
> If we could finish this 5/28/2012 || 28/5/2012 that would be good.
> 
> -Chris
> _______________________________________________
> GROW mailing list
> GROW@ietf.org
> https://www.ietf.org/mailman/listinfo/grow
> 



From xuxiaohu@huawei.com  Mon May 14 18:48:27 2012
Return-Path: <xuxiaohu@huawei.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 73EF19E8004 for <grow@ietfa.amsl.com>; Mon, 14 May 2012 18:48:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.339
X-Spam-Level: *
X-Spam-Status: No, score=1.339 tagged_above=-999 required=5 tests=[AWL=-0.604,  BAYES_00=-2.599, CN_BODY_35=0.339, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45]
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 ED3rLNApAn9q for <grow@ietfa.amsl.com>; Mon, 14 May 2012 18:48:27 -0700 (PDT)
Received: from dfwrgout.huawei.com (dfwrgout.huawei.com [206.16.17.72]) by ietfa.amsl.com (Postfix) with ESMTP id E809A21F893F for <grow@ietf.org>; Mon, 14 May 2012 18:48:26 -0700 (PDT)
Received: from 172.18.9.243 (EHLO dfweml202-edg.china.huawei.com) ([172.18.9.243]) by dfwrg01-dlp.huawei.com (MOS 4.2.3-GA FastPath) with ESMTP id AGE61724; Mon, 14 May 2012 21:48:26 -0400 (EDT)
Received: from DFWEML405-HUB.china.huawei.com (10.193.5.102) by dfweml202-edg.china.huawei.com (172.18.9.108) with Microsoft SMTP Server (TLS) id 14.1.323.3; Mon, 14 May 2012 18:46:23 -0700
Received: from SZXEML439-HUB.china.huawei.com (10.72.61.74) by dfweml405-hub.china.huawei.com (10.193.5.102) with Microsoft SMTP Server (TLS) id 14.1.323.3; Mon, 14 May 2012 18:46:21 -0700
Received: from SZXEML525-MBS.china.huawei.com ([169.254.8.32]) by szxeml439-hub.china.huawei.com ([10.72.61.74]) with mapi id 14.01.0323.003; Tue, 15 May 2012 09:46:15 +0800
From: Xuxiaohu <xuxiaohu@huawei.com>
To: "robert@raszuk.net" <robert@raszuk.net>, Christopher Morrow <christopher.morrow@gmail.com>
Thread-Topic: [GROW] WGLC: draft-ietf-grow-simple-va
Thread-Index: AQHNMfHLDPXiWFem60GRICIJxDtLPJbI+q4AgAEasbA=
Date: Tue, 15 May 2012 01:46:14 +0000
Message-ID: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE02F30A35@szxeml525-mbs.china.huawei.com>
References: <CAL9jLaZd_PUN3Y+Uj+n5roDfXoD_Raw1bn+QpcYQ++6452fppg@mail.gmail.com> <4FB138F6.5060503@raszuk.net>
In-Reply-To: <4FB138F6.5060503@raszuk.net>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.108.4.99]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "grow@ietf.org grow@ietf.org" <grow@ietf.org>, "grow-ads@tools.ietf.org" <grow-ads@tools.ietf.org>, "grow-chairs@tools.ietf.org" <grow-chairs@tools.ietf.org>
Subject: Re: [GROW] WGLC: draft-ietf-grow-simple-va
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 May 2012 01:48:27 -0000

KzENCg0KQlIsDQpYaWFvaHUNCg0KPiAtLS0tLdPKvP7Urbz+LS0tLS0NCj4gt6K8/sjLOiBncm93
LWJvdW5jZXNAaWV0Zi5vcmcgW21haWx0bzpncm93LWJvdW5jZXNAaWV0Zi5vcmddILT6se0gUm9i
ZXJ0DQo+IFJhc3p1aw0KPiC3osvNyrG85DogMjAxMsTqNdTCMTXI1SAwOjU1DQo+IMrVvP7Iyzog
Q2hyaXN0b3BoZXIgTW9ycm93DQo+ILOty806IGdyb3dAaWV0Zi5vcmcgZ3Jvd0BpZXRmLm9yZzsg
Z3Jvdy1hZHNAdG9vbHMuaWV0Zi5vcmc7DQo+IGdyb3ctY2hhaXJzQHRvb2xzLmlldGYub3JnDQo+
INb3zOI6IFJlOiBbR1JPV10gV0dMQzogZHJhZnQtaWV0Zi1ncm93LXNpbXBsZS12YQ0KPiANCj4g
U3VwcG9ydC4NCj4gDQo+IFRoeCwNCj4gUi4NCj4gDQo+ID4gSGVsbyB3ZyBmb2xrLA0KPiA+IFNp
bmNlIHdlIChJIHJlYWxseSBJIHRoaW5rKSBtZXNzZWQgdXAgdGhlIGxhc3QgV0dMQyBmb3IgdGhp
cyBkb2N1bWVudCwNCj4gPiBjYW4gd2UgZ2V0IGFub3RoZXIgYXR0ZW1wdCBhdCB0aGlzIG5vdz8N
Cj4gPiAgICA8aHR0cDovL3d3dy5pZXRmLm9yZy9pbnRlcm5ldC1kcmFmdHMvZHJhZnQtaWV0Zi1n
cm93LXNpbXBsZS12YS0wNS50eHQ+DQo+ID4NCj4gPiBBYnN0cmFjdDoNCj4gPiAgICAgICBUaGUg
Y29udGludWVkIGdyb3d0aCBpbiB0aGUgRGVmYXVsdCBGcmVlIFJvdXRpbmcgVGFibGUgKERGUlQp
DQo+ID4gICAgIHN0cmVzc2VzIHRoZSBnbG9iYWwgcm91dGluZyBzeXN0ZW0gaW4gYSBudW1iZXIg
b2Ygd2F5cy4gIE9uZSBvZiB0aGUNCj4gPiAgICAgbW9zdCBjb3N0bHkgc3RyZXNzZXMgaXMgRklC
IHNpemU6IElTUHMgb2Z0ZW4gbXVzdCB1cGdyYWRlIHJvdXRlcg0KPiA+ICAgICBoYXJkd2FyZSBz
aW1wbHkgYmVjYXVzZSB0aGUgRklCIGhhcyBydW4gb3V0IG9mIHNwYWNlLCBhbmQgcm91dGVyDQo+
ID4gICAgIHZlbmRvcnMgbXVzdCBkZXNpZ24gcm91dGVycyB0aGF0IGhhdmUgYWRlcXVhdGUgRklC
Lg0KPiA+DQo+ID4gICAgIEZJQiBzdXBwcmVzc2lvbiBpcyBhbiBhcHByb2FjaCB0byByZWxpZXZp
bmcgc3RyZXNzIG9uIHRoZSBGSUIgYnkgTk9UDQo+ID4gICAgIGxvYWRpbmcgc2VsZWN0ZWQgUklC
IGVudHJpZXMgaW50byB0aGUgRklCLiAgU2ltcGxlIFZpcnR1YWwNCj4gPiAgICAgQWdncmVnYXRp
b24gKFMtVkEpIGlzIGEgc2ltcGxlIGZvcm0gb2YgVmlydHVhbCBBZ2dyZWdhdGlvbiAoVkEpIHRo
YXQNCj4gPiAgICAgYWxsb3dzIGFueSBhbmQgYWxsIGVkZ2Ugcm91dGVycyB0byBzaHJpbmsgdGhl
aXIgUklCIGFuZCBGSUINCj4gPiAgICAgcmVxdWlyZW1lbnRzIHN1YnN0YW50aWFsbHkgYW5kIHRo
ZXJlZm9yZSBpbmNyZWFzZSB0aGVpciB1c2VmdWwNCj4gPiAgICAgbGlmZXRpbWUuDQo+ID4NCj4g
PiAgICAgUy1WQSBkb2VzIG5vdCBpbmNyZWFzZSBGSUIgcmVxdWlyZW1lbnRzIGZvciBjb3JlIHJv
dXRlcnMuICBTLVZBIGlzDQo+ID4gICAgIGV4dHJlbWVseSBlYXN5IHRvIGNvbmZpZ3VyZSBjb25z
aWRlcmFibHkgbW9yZSBzbyB0aGFuIHRoZSB2YXJpb3VzDQo+ID4gICAgIHRyaWNrcyBkb25lIHRv
ZGF5IHRvIGV4dGVuZCB0aGUgbGlmZSBvZiBlZGdlIHJvdXRlcnMuICBTLVZBIGNhbiBiZQ0KPiA+
ICAgICBkZXBsb3llZCBhdXRvbm9tb3VzbHkgYnkgYW4gSVNQIChjb29wZXJhdGlvbiBiZXR3ZWVu
IElTUHMgaXMgbm90DQo+ID4gICAgIHJlcXVpcmVkKSwgYW5kIGNhbiBjby1leGlzdCB3aXRoIGxl
Z2FjeSByb3V0ZXJzIGluIHRoZSBJU1AuDQo+ID4NCj4gPiBJZiB3ZSBjb3VsZCBmaW5pc2ggdGhp
cyA1LzI4LzIwMTIgfHwgMjgvNS8yMDEyIHRoYXQgd291bGQgYmUgZ29vZC4NCj4gPg0KPiA+IC1D
aHJpcw0KPiA+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
DQo+ID4gR1JPVyBtYWlsaW5nIGxpc3QNCj4gPiBHUk9XQGlldGYub3JnDQo+ID4gaHR0cHM6Ly93
d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9ncm93DQo+ID4NCj4gPg0KPiANCj4gX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj4gR1JPVyBtYWlsaW5n
IGxpc3QNCj4gR1JPV0BpZXRmLm9yZw0KPiBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xp
c3RpbmZvL2dyb3cNCg==

From nick@inex.ie  Wed May 16 03:38:41 2012
Return-Path: <nick@inex.ie>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 062FF21F85BB for <grow@ietfa.amsl.com>; Wed, 16 May 2012 03:38:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.556
X-Spam-Level: 
X-Spam-Status: No, score=-2.556 tagged_above=-999 required=5 tests=[AWL=0.043,  BAYES_00=-2.599]
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 tWTAr0iYwGSG for <grow@ietfa.amsl.com>; Wed, 16 May 2012 03:38:40 -0700 (PDT)
Received: from mail.acquirer.com (mail.acquirer.com [IPv6:2a03:8900:0:100::5]) by ietfa.amsl.com (Postfix) with ESMTP id 4A61121F85C0 for <grow@ietf.org>; Wed, 16 May 2012 03:38:39 -0700 (PDT)
X-Envelope-To: grow@ietf.org
Received: from cupcake.local (inet-gw.acquirer.com [87.198.142.10]) (authenticated bits=0) by mail.acquirer.com (8.14.4/8.14.4) with ESMTP id q4GAbvpJ062235 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Wed, 16 May 2012 11:37:58 +0100 (IST) (envelope-from nick@inex.ie)
Message-ID: <4FB383A9.1050904@inex.ie>
Date: Wed, 16 May 2012 11:38:33 +0100
From: Nick Hilliard <nick@inex.ie>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: robert@raszuk.net
References: <CAL9jLaZd_PUN3Y+Uj+n5roDfXoD_Raw1bn+QpcYQ++6452fppg@mail.gmail.com> <4FB13D9D.3040500@inex.ie> <4FB144D4.9060308@raszuk.net>
In-Reply-To: <4FB144D4.9060308@raszuk.net>
X-Enigmail-Version: 1.4.1
X-Company-Info-1: Internet Neutral Exchange Association Limited. Registered in Ireland No. 253804
X-Company-Info-2: Registered Offices: 1-2, Marino Mart, Fairview, Dublin 3
X-Company-Info-3: Internet Neutral Exchange Association Limited is limited by guarantee
X-Company-Info-4: Offices: 4027 Kingswood Road, Citywest, Dublin 24.
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: grow@ietf.org
Subject: Re: [GROW] WGLC: draft-ietf-grow-simple-va
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 May 2012 10:38:41 -0000

I meant to say that I approve of the doc for wglc.

Nick

From russw@riw.us  Thu May 17 05:21:18 2012
Return-Path: <russw@riw.us>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D1A2A21F8657 for <grow@ietfa.amsl.com>; Thu, 17 May 2012 05:21:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.696
X-Spam-Level: 
X-Spam-Status: No, score=-1.696 tagged_above=-999 required=5 tests=[AWL=0.304,  BAYES_00=-2.599, J_CHICKENPOX_13=0.6]
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 2h6Lyam8vNk2 for <grow@ietfa.amsl.com>; Thu, 17 May 2012 05:21:18 -0700 (PDT)
Received: from da31.namelessnet.net (da31.namelessnet.net [74.124.205.66]) by ietfa.amsl.com (Postfix) with ESMTP id 4DE4D21F8576 for <grow@ietf.org>; Thu, 17 May 2012 05:21:18 -0700 (PDT)
Received: from cpe-065-190-156-032.nc.res.rr.com ([65.190.156.32] helo=[192.168.100.69]) by da31.namelessnet.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.77) (envelope-from <russw@riw.us>) id 1SUzhl-0003L2-8w for grow@ietf.org; Thu, 17 May 2012 05:21:17 -0700
Message-ID: <4FB4ED36.2050700@riw.us>
Date: Thu, 17 May 2012 08:21:10 -0400
From: Russ White <russw@riw.us>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: "grow@ietf.org" <grow@ietf.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-Antivirus-Scanner: Seems clean.  You should still use an Antivirus Scanner
Subject: [GROW] Comments on draft-ietf-grow-va-06
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 May 2012 12:21:18 -0000

Y'all:

I finally got around to rereading this draft, so I could make some
intelligent comments on it. But before I begin, let me make a comment on
the process here...

There are three drafts I know of in this space. Two of them have
expired, but I've recently received emails about reviving them. None of
these drafts require changes to BGP's operation on the wire, however. It
seems, to me, that there's no reason for GROW to actually prefer one
solution over another. In fact, it seems like there's no reason not to
publish all the "non-overlapping" ideas, and let vendors and operators
choose which one they prefer to implement & deploy.

I'll leave this point open for discussion, and move to my comments on
this draft in particular.

==
The first thing to note is this draft specifically attacks FIB table
size without modifying the routing table size. Since I'm not convinced
that FIB size, as opposed to the on-the-wire table size, is a problem
that needs to be addressed, I'm not certain about the overall utility of
the mechanism outlined here.

Is there any reason to suspect that forwarding table size is "the"
problem in hand?

==
The core idea behind
FIB suppression is to run BGP as normal, and in particular to not
shrink the RIB, but rather to not load certain RIB entries into the
FIB.  This approach minimizes changes to routers, and in particular
is simpler than more general routing architectures that try to shrink
both RIB and FIB.

Is this really a good idea? I will now have two different control plane
tables, one ostensibly built from the other, which do not match. While
this might not be a problem for the router, it would be a wee bit of a
problem at 2am when I'm trying to troubleshoot some network traffic flow
problem, or a routing problem. Ping and traceroute are no longer
reliable indicators of forwarding table state through the network --not
a good thing, IMHO.

==
On the increase in stretch...

While I realize aggregation always causes increases in stretch, it seems
like this draft would increase stretch precisely where other drafts are
trying to reduce it by increasing the amount of information BGP sends. I
suppose different situations might call for different design parameters,
but I don't see how this draft would allow for shorter paths through
multiple BGP advertisements in parallel with reduced state (both
deployed at the same time).

Maybe the authors would care to add a section discussing how these
things would work together.

==
In other words, even if an ingress
router is not an APR for a given sub-prefix, it MAY install that sub-
prefix into its FIB.  Packets in this case are tunneled directly from
the ingress to the BGP NEXT_HOP.  These extra routes are called
"Popular Prefixes", and are typically installed for policy reasons

I'm not certain how these "popular prefixes" will actually work in
practice. Wouldn't it be a requirement that every router in AS have the
same list? It might be worth addressing this situation in some way
within the draft.

==
How would this interact with traffic engineering? Since this uses MPLS
tunnels to get traffic around to aggregation points, wouldn't this at
least overlap with other uses of MPLS in the same network? Again, it
seems like it might be worth making some comments on this in the draft.

==

I find this draft introduces a lot of complexity for the amount of gain
it provides. While the end result in theory might be a really high level
of aggregation within the provider's network, the reality of increased
stretch would probably mean most networks end up only gaining some lower
amount of savings in real forwarding table size reductions --and I'm not
certain the savings are where providers really need them.

I suppose this might be a good fit for some L3VPN deployments, but there
a provider might find the increased stretch causes his network to be
much slower at the savings of a small number of control plane entries,
and and the cost of increased TE complexity.

So, overall, I'm not certain of the value for complexity tradeoff here.

Russ



-- 
<><
riwhite@verisign.com
russw@riw.us


From roland.dobbins@gmail.com  Thu May 17 06:21:19 2012
Return-Path: <roland.dobbins@gmail.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0910421F869F for <grow@ietfa.amsl.com>; Thu, 17 May 2012 06:21:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 9KPcpzlK03NG for <grow@ietfa.amsl.com>; Thu, 17 May 2012 06:21:18 -0700 (PDT)
Received: from mail-qc0-f172.google.com (mail-qc0-f172.google.com [209.85.216.172]) by ietfa.amsl.com (Postfix) with ESMTP id 66F1521F8686 for <grow@ietf.org>; Thu, 17 May 2012 06:21:17 -0700 (PDT)
Received: by qcsq13 with SMTP id q13so1451790qcs.31 for <grow@ietf.org>; Thu, 17 May 2012 06:21:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to:x-mailer; bh=jZAFlTP+i2dUA4ayQP1/hUzqaaF6FAq5Iy5j8BPlfQg=; b=pAgqUCl3P1eImW6Ga2PhhKNnWy9SzxNEmJd0ZETornkJMAq5S5+9MPhpjAAkvXNhGj Y8flzxm/4H0cJZOKm7rp4PnaOUvF0oqOkMxyWx8zLeT/n8WBMSRsp+QGN846D2m+eFAz G7Qgi9SDJP34i2OW8sgxoe86uz1zp/602jwm5XT2Ert4edyHiAsqbn2JpurmwagTDWnJ DopMW7nv7kaOJ216RKR/6EGKp/N8M8Q/1ii7P9+bNVhp2dnPGaLdfssTkT+BTMcQvWFv EvLeX5PcmHh37IgheXPquYBQtOPYhq+2Gvrhk+QRFetG8/G17bWtEA4gwJbGXYAe4Fe8 galA==
Received: by 10.229.201.233 with SMTP id fb41mr3329953qcb.94.1337260876754; Thu, 17 May 2012 06:21:16 -0700 (PDT)
Received: from bdonovan-home.ellacoya.com (202-176-81-112.static.asianet.co.th. [202.176.81.112]) by mx.google.com with ESMTPS id gw2sm14757772qab.10.2012.05.17.06.21.14 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 17 May 2012 06:21:16 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1257)
From: Roland Dobbins <roland.dobbins@gmail.com>
In-Reply-To: <4FB4ED36.2050700@riw.us>
Date: Thu, 17 May 2012 20:21:10 +0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <5759E5E1-A054-45D5-8A07-EF2E17817419@gmail.com>
References: <4FB4ED36.2050700@riw.us>
To: "grow@ietf.org grow@ietf.org" <grow@ietf.org>
X-Mailer: Apple Mail (2.1257)
Subject: Re: [GROW] Comments on draft-ietf-grow-va-06
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 May 2012 13:21:19 -0000

On May 17, 2012, at 7:21 PM, Russ White wrote:

> Is there any reason to suspect that forwarding table size is "the" =
problem in hand?

The are concurrent and inter-related problems, IMHO - the idea behind =
any proposed solution(s) should be that solving for one will also solve =
for the other, to the extent(s) applicable and possible.=

From nick@inex.ie  Thu May 17 06:35:08 2012
Return-Path: <nick@inex.ie>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1E18121F8674 for <grow@ietfa.amsl.com>; Thu, 17 May 2012 06:35:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.562
X-Spam-Level: 
X-Spam-Status: No, score=-2.562 tagged_above=-999 required=5 tests=[AWL=0.037,  BAYES_00=-2.599]
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 vwjpC0sZVUCD for <grow@ietfa.amsl.com>; Thu, 17 May 2012 06:35:07 -0700 (PDT)
Received: from mail.acquirer.com (mail.acquirer.com [IPv6:2a03:8900:0:100::5]) by ietfa.amsl.com (Postfix) with ESMTP id 586DA21F85AE for <grow@ietf.org>; Thu, 17 May 2012 06:35:06 -0700 (PDT)
X-Envelope-To: grow@ietf.org
Received: from cupcake.local (inet-gw.acquirer.com [87.198.142.10]) (authenticated bits=0) by mail.acquirer.com (8.14.4/8.14.4) with ESMTP id q4HDYO9U081396 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Thu, 17 May 2012 14:34:24 +0100 (IST) (envelope-from nick@inex.ie)
Message-ID: <4FB4FE85.1010406@inex.ie>
Date: Thu, 17 May 2012 14:35:01 +0100
From: Nick Hilliard <nick@inex.ie>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: Russ White <russw@riw.us>
References: <4FB4ED36.2050700@riw.us>
In-Reply-To: <4FB4ED36.2050700@riw.us>
X-Enigmail-Version: 1.4.1
X-Company-Info-1: Internet Neutral Exchange Association Limited. Registered in Ireland No. 253804
X-Company-Info-2: Registered Offices: 1-2, Marino Mart, Fairview, Dublin 3
X-Company-Info-3: Internet Neutral Exchange Association Limited is limited by guarantee
X-Company-Info-4: Offices: 4027 Kingswood Road, Citywest, Dublin 24.
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] Comments on draft-ietf-grow-va-06
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 May 2012 13:35:08 -0000

On 17/05/2012 13:21, Russ White wrote:
> The first thing to note is this draft specifically attacks FIB table
> size without modifying the routing table size. Since I'm not convinced
> that FIB size, as opposed to the on-the-wire table size, is a problem
> that needs to be addressed, I'm not certain about the overall utility of
> the mechanism outlined here.
> 
> Is there any reason to suspect that forwarding table size is "the"
> problem in hand?

As an operator who needs to juggle between upgrade costs and actually
running a network, I'd tend to be of the opinion that it sucks to retire a
router from dfz operation because of fib size constraints.

There are hacks to deal with on-the-wire size.  They are probably uglier
that virtual aggregation, and certainly messier to maintain.

Nick

From russw@riw.us  Thu May 17 06:59:34 2012
Return-Path: <russw@riw.us>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5E39321F869A for <grow@ietfa.amsl.com>; Thu, 17 May 2012 06:59:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[AWL=0.502,  BAYES_00=-2.599]
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 wwMIQQ2OUgsc for <grow@ietfa.amsl.com>; Thu, 17 May 2012 06:59:33 -0700 (PDT)
Received: from da31.namelessnet.net (da31.namelessnet.net [74.124.205.66]) by ietfa.amsl.com (Postfix) with ESMTP id C9DB221F865C for <grow@ietf.org>; Thu, 17 May 2012 06:59:33 -0700 (PDT)
Received: from cpe-065-190-156-032.nc.res.rr.com ([65.190.156.32] helo=[192.168.100.69]) by da31.namelessnet.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.77) (envelope-from <russw@riw.us>) id 1SV1Ep-0000Gp-VY; Thu, 17 May 2012 06:59:32 -0700
Message-ID: <4FB5043C.9030209@riw.us>
Date: Thu, 17 May 2012 09:59:24 -0400
From: Russ White <russw@riw.us>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: Nick Hilliard <nick@inex.ie>
References: <4FB4ED36.2050700@riw.us> <4FB4FE85.1010406@inex.ie>
In-Reply-To: <4FB4FE85.1010406@inex.ie>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Antivirus-Scanner: Seems clean.  You should still use an Antivirus Scanner
Cc: "grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] Comments on draft-ietf-grow-va-06
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 May 2012 13:59:34 -0000

> There are hacks to deal with on-the-wire size.  They are probably
> uglier that virtual aggregation, and certainly messier to maintain.

Are you familiar with IRS, or any of its variants? Do you think the
operational aspects of this draft, in terms of MTTR, are okay?

Russ



-- 
<>< Scripture Alone, Grace Alone, Faith Alone
http://thinkinginchrist.com/

From nick@inex.ie  Thu May 17 07:49:08 2012
Return-Path: <nick@inex.ie>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8BCB921F85F0 for <grow@ietfa.amsl.com>; Thu, 17 May 2012 07:49:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.566
X-Spam-Level: 
X-Spam-Status: No, score=-2.566 tagged_above=-999 required=5 tests=[AWL=0.033,  BAYES_00=-2.599]
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 yDpFT87pgErt for <grow@ietfa.amsl.com>; Thu, 17 May 2012 07:49:08 -0700 (PDT)
Received: from mail.acquirer.com (mail.acquirer.com [IPv6:2a03:8900:0:100::5]) by ietfa.amsl.com (Postfix) with ESMTP id C343721F852E for <grow@ietf.org>; Thu, 17 May 2012 07:49:07 -0700 (PDT)
X-Envelope-To: grow@ietf.org
Received: from cupcake.local (inet-gw.acquirer.com [87.198.142.10]) (authenticated bits=0) by mail.acquirer.com (8.14.4/8.14.4) with ESMTP id q4HEmPu0082587 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Thu, 17 May 2012 15:48:25 +0100 (IST) (envelope-from nick@inex.ie)
Message-ID: <4FB50FDE.7080804@inex.ie>
Date: Thu, 17 May 2012 15:49:02 +0100
From: Nick Hilliard <nick@inex.ie>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: Russ White <russw@riw.us>
References: <4FB4ED36.2050700@riw.us> <4FB4FE85.1010406@inex.ie> <4FB5043C.9030209@riw.us>
In-Reply-To: <4FB5043C.9030209@riw.us>
X-Enigmail-Version: 1.4.1
X-Company-Info-1: Internet Neutral Exchange Association Limited. Registered in Ireland No. 253804
X-Company-Info-2: Registered Offices: 1-2, Marino Mart, Fairview, Dublin 3
X-Company-Info-3: Internet Neutral Exchange Association Limited is limited by guarantee
X-Company-Info-4: Offices: 4027 Kingswood Road, Citywest, Dublin 24.
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] Comments on draft-ietf-grow-va-06
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 May 2012 14:49:08 -0000

On 17/05/2012 14:59, Russ White wrote:
> Are you familiar with IRS, or any of its variants? 

Nope - can you provide a reference?  My google-fu is failing.

> Do you think the
> operational aspects of this draft, in terms of MTTR, are okay?

I can't answer this question until I see the protocol in operation.  Given
suitable visibility into what's happening with the collapsed routing
structure, I don't really see a problem.  Like most other things, what's
important is how much visibility the operator gets into what's going on, so
that problems can be debugged.

Nick


From rbonica@juniper.net  Thu May 17 09:11:47 2012
Return-Path: <rbonica@juniper.net>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 75B3B21F866D; Thu, 17 May 2012 09:11:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.548
X-Spam-Level: 
X-Spam-Status: No, score=-106.548 tagged_above=-999 required=5 tests=[AWL=0.051, 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 coXxzb2qndnH; Thu, 17 May 2012 09:11:46 -0700 (PDT)
Received: from exprod7og126.obsmtp.com (exprod7og126.obsmtp.com [64.18.2.206]) by ietfa.amsl.com (Postfix) with ESMTP id 57F3B21F865B; Thu, 17 May 2012 09:11:46 -0700 (PDT)
Received: from P-EMHUB03-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob126.postini.com ([64.18.6.12]) with SMTP ID DSNKT7UjQVh98DnwTfNI4+CsbJ0D4NqxJGn7@postini.com; Thu, 17 May 2012 09:11:46 PDT
Received: from P-CLDFE02-HQ.jnpr.net (172.24.192.60) by P-EMHUB03-HQ.jnpr.net (172.24.192.37) with Microsoft SMTP Server (TLS) id 8.3.213.0; Thu, 17 May 2012 09:11:31 -0700
Received: from p-emfe02-wf.jnpr.net (172.28.145.25) by p-cldfe02-hq.jnpr.net (172.24.192.60) with Microsoft SMTP Server (TLS) id 14.1.355.2; Thu, 17 May 2012 09:11:31 -0700
Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe02-wf.jnpr.net ([fe80::c126:c633:d2dc:8090%11]) with mapi; Thu, 17 May 2012 12:11:30 -0400
From: Ronald Bonica <rbonica@juniper.net>
To: "grow@ietf.org" <grow@ietf.org>, "opsec@ietf.org" <opsec@ietf.org>
Date: Thu, 17 May 2012 12:11:29 -0400
Thread-Topic: draft-ietf-grow-private-ip-sp-cores
Thread-Index: Ac00R7enS8J+NXJ5TBeH1QUCwxMMRg==
Message-ID: <13205C286662DE4387D9AF3AC30EF456D76BA8836D@EMBX01-WF.jnpr.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [GROW] draft-ietf-grow-private-ip-sp-cores
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 May 2012 16:11:47 -0000

Folks,

Thanks for introducing this document!=20

I would like to bring the authors' attention to the following documents tha=
t are working in OPSEC:

- draft-behringer-lla-only
- draft-baker-opsec-passive-ip-address

To some extent, draft-grow and draft-behringer are debating with one anothe=
r. While draft-baker is not directly involved in the debate, it is not unin=
volved, either. It is a shame that the three documents are being considered=
 in different WGs.=20

For the purpose of discussing these three documents, I think that a little =
cross-posting is acceptable.

--------------------------
Ron Bonica
vcard:       www.bonica.org/ron/ronbonica.vcf



From nick@inex.ie  Fri May 18 04:05:09 2012
Return-Path: <nick@inex.ie>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BBFA221F8599; Fri, 18 May 2012 04:05:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.569
X-Spam-Level: 
X-Spam-Status: No, score=-2.569 tagged_above=-999 required=5 tests=[AWL=0.030,  BAYES_00=-2.599]
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 gSl9UbtQagI2; Fri, 18 May 2012 04:05:09 -0700 (PDT)
Received: from mail.acquirer.com (mail.acquirer.com [IPv6:2a03:8900:0:100::5]) by ietfa.amsl.com (Postfix) with ESMTP id 0903321F8597; Fri, 18 May 2012 04:05:08 -0700 (PDT)
X-Envelope-To: opsec@ietf.org
Received: from cupcake.local (inet-gw.acquirer.com [87.198.142.10]) (authenticated bits=0) by mail.acquirer.com (8.14.4/8.14.4) with ESMTP id q4IB4RDS094464 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Fri, 18 May 2012 12:04:27 +0100 (IST) (envelope-from nick@inex.ie)
Message-ID: <4FB62CE1.3050805@inex.ie>
Date: Fri, 18 May 2012 12:05:05 +0100
From: Nick Hilliard <nick@inex.ie>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: Ronald Bonica <rbonica@juniper.net>
References: <13205C286662DE4387D9AF3AC30EF456D76BA8836D@EMBX01-WF.jnpr.net>
In-Reply-To: <13205C286662DE4387D9AF3AC30EF456D76BA8836D@EMBX01-WF.jnpr.net>
X-Enigmail-Version: 1.4.1
X-Company-Info-1: Internet Neutral Exchange Association Limited. Registered in Ireland No. 253804
X-Company-Info-2: Registered Offices: 1-2, Marino Mart, Fairview, Dublin 3
X-Company-Info-3: Internet Neutral Exchange Association Limited is limited by guarantee
X-Company-Info-4: Offices: 4027 Kingswood Road, Citywest, Dublin 24.
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "grow@ietf.org" <grow@ietf.org>, "opsec@ietf.org" <opsec@ietf.org>
Subject: Re: [GROW] draft-ietf-grow-private-ip-sp-cores
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 May 2012 11:05:09 -0000

On 17/05/2012 17:11, Ronald Bonica wrote:
> Thanks for introducing this document! 
> 
> I would like to bring the authors' attention to the following documents
> that are working in OPSEC:
> 
> - draft-behringer-lla-only
> - draft-baker-opsec-passive-ip-address
> 
> To some extent, draft-grow and draft-behringer are debating with one
> another. While draft-baker is not directly involved in the debate, it is
> not uninvolved, either. It is a shame that the three documents are being
> considered in different WGs.

yes, certainly draft-behringer and draft-grow are discussing a
substantially similar issue - namely using non-routable interface addresses
in the core.  tbh, it's not really possible to manage a network without
traceroute and remote interface ping.

Wes George posted a more complete response here:

http://www.ietf.org/mail-archive/web/grow/current/msg02191.html

I agree fully with his analysis on all points.

Nick

From tkirkham@anthony-kirkham.com  Sun May 20 03:39:14 2012
Return-Path: <tkirkham@anthony-kirkham.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B88B21F8570; Sun, 20 May 2012 03:39:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 BBrmHfo5XXZD; Sun, 20 May 2012 03:39:13 -0700 (PDT)
Received: from nskntmtas03p.mx.bigpond.com (nskntmtas03p.mx.bigpond.com [61.9.168.143]) by ietfa.amsl.com (Postfix) with ESMTP id EF10221F856C; Sun, 20 May 2012 03:39:12 -0700 (PDT)
Received: from nskntotgx04p.mx.bigpond.com ([123.211.150.122]) by nskntmtas03p.mx.bigpond.com with ESMTP id <20120520103910.DKSV10464.nskntmtas03p.mx.bigpond.com@nskntotgx04p.mx.bigpond.com>; Sun, 20 May 2012 10:39:10 +0000
Received: from Anthonys-MacBook-Pro.local ([123.211.150.122]) by nskntotgx04p.mx.bigpond.com with ESMTP id <20120520103910.JAXH9520.nskntotgx04p.mx.bigpond.com@Anthonys-MacBook-Pro.local>; Sun, 20 May 2012 10:39:10 +0000
Message-ID: <4FB8C99D.4030202@anthony-kirkham.com>
Date: Sun, 20 May 2012 20:38:21 +1000
From: Anthony Kirkham <tkirkham@anthony-kirkham.com>
Organization: Anthony-Kirkham.com
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: Ronald Bonica <rbonica@juniper.net>
References: <13205C286662DE4387D9AF3AC30EF456D76BA8836D@EMBX01-WF.jnpr.net>
In-Reply-To: <13205C286662DE4387D9AF3AC30EF456D76BA8836D@EMBX01-WF.jnpr.net>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Authentication-Info: Submitted using SMTP AUTH PLAIN at nskntotgx04p.mx.bigpond.com from [123.211.150.122] using ID anthony.kirkham at Sun, 20 May 2012 10:39:10 +0000
X-SIH-MSG-ID: ohg6EtD/TFOplWx72WziQVUtlUy7/yU1v8pWRYIhuRsaT1jBuMDAQs+jbaJDw56FkWBcS0vMLmMgc63kV4zYuNiwMb5RW7Lj
Cc: "grow@ietf.org" <grow@ietf.org>, "opsec@ietf.org" <opsec@ietf.org>
Subject: Re: [GROW] draft-ietf-grow-private-ip-sp-cores
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: tkirkham@anthony-kirkham.com
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 20 May 2012 10:39:14 -0000

If we come back to the original intent of this draft. The private-ip 
draft was fundamentally intended to provide some useful information on a 
topic, which had not previously been documented. And in my experience, 
there was a lot of confusion in relation to the subject across many 
ISPs. It was certainly not designed to make recommendations as to best 
practice (even though I have my own views on that). I have worded the 
document to avoid any suggestion of good or bad practice, just 
documenting the effects.

I would not like to see it delayed by getting caught up in these 
discussions. It should certainly not prevent any of these other 
discussions going forward.

That's my 0.02c, and again thanks for all the feedback and discussion.
Tony K


On 18/05/12 2:11 AM, Ronald Bonica wrote:
> Folks,
>
> Thanks for introducing this document!
>
> I would like to bring the authors' attention to the following documents that are working in OPSEC:
>
> - draft-behringer-lla-only
> - draft-baker-opsec-passive-ip-address
>
> To some extent, draft-grow and draft-behringer are debating with one another. While draft-baker is not directly involved in the debate, it is not uninvolved, either. It is a shame that the three documents are being considered in different WGs.
>
> For the purpose of discussing these three documents, I think that a little cross-posting is acceptable.
>
> --------------------------
> Ron Bonica
> vcard:       www.bonica.org/ron/ronbonica.vcf
>
>
> _______________________________________________
> GROW mailing list
> GROW@ietf.org
> https://www.ietf.org/mailman/listinfo/grow
>
>


-- 



From ietfc@btconnect.com  Tue May 22 02:26:59 2012
Return-Path: <ietfc@btconnect.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9D2F021F854F; Tue, 22 May 2012 02:26:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.74
X-Spam-Level: 
X-Spam-Status: No, score=-1.74 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, RCVD_IN_DNSWL_LOW=-1]
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 I4gaDAmVZfkv; Tue, 22 May 2012 02:26:59 -0700 (PDT)
Received: from va3outboundpool.messaging.microsoft.com (va3ehsobe002.messaging.microsoft.com [216.32.180.12]) by ietfa.amsl.com (Postfix) with ESMTP id CE51321F854D; Tue, 22 May 2012 02:26:58 -0700 (PDT)
Received: from mail218-va3-R.bigfish.com (10.7.14.249) by VA3EHSOBE010.bigfish.com (10.7.40.12) with Microsoft SMTP Server id 14.1.225.22; Tue, 22 May 2012 09:26:44 +0000
Received: from mail218-va3 (localhost [127.0.0.1])	by mail218-va3-R.bigfish.com (Postfix) with ESMTP id 21882100089; Tue, 22 May 2012 09:26:44 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.55.224.141; KIP:(null); UIP:(null); IPV:NLI; H:DB3PRD0702HT011.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -30
X-BigFish: PS-30(zz9371I148cI542M1432N1418Izz1202hzz8275ch1033IL8275dhz2dh2a8h5a9h668h839hd24hf0ah304l)
Received: from mail218-va3 (localhost.localdomain [127.0.0.1]) by mail218-va3 (MessageSwitch) id 133767880124023_13974; Tue, 22 May 2012 09:26:41 +0000 (UTC)
Received: from VA3EHSMHS005.bigfish.com (unknown [10.7.14.241])	by mail218-va3.bigfish.com (Postfix) with ESMTP id 03E2B140045; Tue, 22 May 2012 09:26:41 +0000 (UTC)
Received: from DB3PRD0702HT011.eurprd07.prod.outlook.com (157.55.224.141) by VA3EHSMHS005.bigfish.com (10.7.99.15) with Microsoft SMTP Server (TLS) id 14.1.225.23; Tue, 22 May 2012 09:26:40 +0000
Received: from BL2PRD0410HT002.namprd04.prod.outlook.com (157.56.240.85) by pod51017.outlook.com (10.3.48.170) with Microsoft SMTP Server (TLS) id 14.15.74.2; Tue, 22 May 2012 09:26:44 +0000
Message-ID: <016b01cd37fc$9e125420$4001a8c0@gateway.2wire.net>
From: t.petch <ietfc@btconnect.com>
To: Ronald Bonica <rbonica@juniper.net>, <grow@ietf.org>, <opsec@ietf.org>
References: <13205C286662DE4387D9AF3AC30EF456D76BA8836D@EMBX01-WF.jnpr.net>
Date: Tue, 22 May 2012 10:23:46 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [157.56.240.85]
X-FOPE-CRA-Verdict: 157.55.224.141$juniper.net%12218%2%btconnect.com%True%True%0$
X-OriginatorOrg: btconnect.com
Subject: Re: [GROW] draft-ietf-grow-private-ip-sp-cores
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 May 2012 09:26:59 -0000

----- Original Message -----
From: "Ronald Bonica" <rbonica@juniper.net>
To: <grow@ietf.org>; <opsec@ietf.org>
Sent: Thursday, May 17, 2012 5:11 PM
> Folks,
>
> Thanks for introducing this document!
>
> I would like to bring the authors' attention to the following
documents that are working in OPSEC:
>
> - draft-behringer-lla-only
> - draft-baker-opsec-passive-ip-address
>
> To some extent, draft-grow and draft-behringer are debating with one
another. While draft-baker is not directly involved in the debate, it is
not uninvolved, either. It is a shame that the three documents are being
considered in different WGs.

I think it a bigger shame that draft-ietf-grow-private-ip-sp-cores is
not in the RFC Editor queue awaiting publication!

It is a natural companion to RFC6598 and could have, should have, been
in the queue at the same time.  This I-D was relevant when it was first
written 2 years ago, and I see its relevance decreasing with time, as
people stumble over the mistakes that this I-D could have prevented.  It
has taken those 2 years to get this I-D IETF-ready, little has changed
in the content in that time, and it is time we got it out of the door.

Of course there is scope for improvement, there always is, but that is
an argument for never publishing anything.  If the authors of the other
I-Ds want to build on it, then of course they can produce a bis that
covers more, but let's publish what we have got.

Tom Petch

>
> For the purpose of discussing these three documents, I think that a
little cross-posting is acceptable.
>
> --------------------------
> Ron Bonica
> vcard:       www.bonica.org/ron/ronbonica.vcf
>
>
> _______________________________________________
> GROW mailing list
> GROW@ietf.org
> https://www.ietf.org/mailman/listinfo/grow
>



From robert@raszuk.net  Tue May 22 05:00:15 2012
Return-Path: <robert@raszuk.net>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CEA6821F8539 for <grow@ietfa.amsl.com>; Tue, 22 May 2012 05:00:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 QfFupnxU+6fK for <grow@ietfa.amsl.com>; Tue, 22 May 2012 05:00:15 -0700 (PDT)
Received: from mail1310.opentransfer.com (mail1310.opentransfer.com [76.162.254.103]) by ietfa.amsl.com (Postfix) with ESMTP id D59CF21F842C for <grow@ietf.org>; Tue, 22 May 2012 05:00:14 -0700 (PDT)
Received: (qmail 14599 invoked by uid 399); 22 May 2012 12:00:14 -0000
Received: from unknown (HELO ?192.168.1.91?) (pbs:m42@mojaklasa.info@83.31.233.32) by mail1310.opentransfer.com with ESMTPM; 22 May 2012 12:00:14 -0000
X-Originating-IP: 83.31.233.32
Message-ID: <4FBB7FC7.2050307@raszuk.net>
Date: Tue, 22 May 2012 14:00:07 +0200
From: Robert Raszuk <robert@raszuk.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: "t.petch" <ietfc@btconnect.com>
References: <13205C286662DE4387D9AF3AC30EF456D76BA8836D@EMBX01-WF.jnpr.net> <016b01cd37fc$9e125420$4001a8c0@gateway.2wire.net>
In-Reply-To: <016b01cd37fc$9e125420$4001a8c0@gateway.2wire.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: grow@ietf.org, opsec@ietf.org
Subject: Re: [GROW] draft-ietf-grow-private-ip-sp-cores
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: robert@raszuk.net
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 May 2012 12:00:15 -0000

Extremely well said Tom !

Rgs,
R.

> ----- Original Message -----
> From: "Ronald Bonica"<rbonica@juniper.net>
> To:<grow@ietf.org>;<opsec@ietf.org>
> Sent: Thursday, May 17, 2012 5:11 PM
>> Folks,
>>
>> Thanks for introducing this document!
>>
>> I would like to bring the authors' attention to the following
> documents that are working in OPSEC:
>>
>> - draft-behringer-lla-only
>> - draft-baker-opsec-passive-ip-address
>>
>> To some extent, draft-grow and draft-behringer are debating with one
> another. While draft-baker is not directly involved in the debate, it is
> not uninvolved, either. It is a shame that the three documents are being
> considered in different WGs.
>
> I think it a bigger shame that draft-ietf-grow-private-ip-sp-cores is
> not in the RFC Editor queue awaiting publication!
>
> It is a natural companion to RFC6598 and could have, should have, been
> in the queue at the same time.  This I-D was relevant when it was first
> written 2 years ago, and I see its relevance decreasing with time, as
> people stumble over the mistakes that this I-D could have prevented.  It
> has taken those 2 years to get this I-D IETF-ready, little has changed
> in the content in that time, and it is time we got it out of the door.
>
> Of course there is scope for improvement, there always is, but that is
> an argument for never publishing anything.  If the authors of the other
> I-Ds want to build on it, then of course they can produce a bis that
> covers more, but let's publish what we have got.
>
> Tom Petch
>
>>
>> For the purpose of discussing these three documents, I think that a
> little cross-posting is acceptable.
>>
>> --------------------------
>> Ron Bonica
>> vcard:       www.bonica.org/ron/ronbonica.vcf


From rbonica@juniper.net  Tue May 22 14:10:51 2012
Return-Path: <rbonica@juniper.net>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6564B21F8589; Tue, 22 May 2012 14:10:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.299
X-Spam-Level: 
X-Spam-Status: No, score=-106.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_15=0.6, 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 rqYi4JeSCi08; Tue, 22 May 2012 14:10:46 -0700 (PDT)
Received: from exprod7og110.obsmtp.com (exprod7og110.obsmtp.com [64.18.2.173]) by ietfa.amsl.com (Postfix) with ESMTP id 4681121F8603; Tue, 22 May 2012 14:10:44 -0700 (PDT)
Received: from P-EMHUB03-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob110.postini.com ([64.18.6.12]) with SMTP ID DSNKT7wA0/pdvdhUftJGAMoim5jk+RCK23ld@postini.com; Tue, 22 May 2012 14:10:45 PDT
Received: from p-emfe02-wf.jnpr.net (172.28.145.25) by P-EMHUB03-HQ.jnpr.net (172.24.192.37) with Microsoft SMTP Server (TLS) id 8.3.213.0; Tue, 22 May 2012 14:07:21 -0700
Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe02-wf.jnpr.net ([fe80::c126:c633:d2dc:8090%11]) with mapi; Tue, 22 May 2012 17:07:10 -0400
From: Ronald Bonica <rbonica@juniper.net>
To: t.petch <ietfc@btconnect.com>, "grow@ietf.org" <grow@ietf.org>, "opsec@ietf.org" <opsec@ietf.org>
Date: Tue, 22 May 2012 17:07:08 -0400
Thread-Topic: [GROW] draft-ietf-grow-private-ip-sp-cores
Thread-Index: Ac03/QuUMzo/ZokMR2GmjIr9l5EgQQAYLJlA
Message-ID: <13205C286662DE4387D9AF3AC30EF456D76C03EEBF@EMBX01-WF.jnpr.net>
References: <13205C286662DE4387D9AF3AC30EF456D76BA8836D@EMBX01-WF.jnpr.net> <016b01cd37fc$9e125420$4001a8c0@gateway.2wire.net>
In-Reply-To: <016b01cd37fc$9e125420$4001a8c0@gateway.2wire.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [GROW] draft-ietf-grow-private-ip-sp-cores
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 May 2012 21:10:51 -0000

Tom,

AFAIKS, the WGLC that Chris suggested in the email below can proceed:

- http://www.ietf.org/mail-archive/web/grow/current/msg02263.html

The updates that Chris requested seem to be addressed in the two versions t=
hat have been posted since then. Chris, do you agree?

                                               Ron

> -----Original Message-----
> From: t.petch [mailto:ietfc@btconnect.com]
> Sent: Tuesday, May 22, 2012 5:24 AM
> To: Ronald Bonica; grow@ietf.org; opsec@ietf.org
> Subject: Re: [GROW] draft-ietf-grow-private-ip-sp-cores
>=20
> ----- Original Message -----
> From: "Ronald Bonica" <rbonica@juniper.net>
> To: <grow@ietf.org>; <opsec@ietf.org>
> Sent: Thursday, May 17, 2012 5:11 PM
> > Folks,
> >
> > Thanks for introducing this document!
> >
> > I would like to bring the authors' attention to the following
> documents that are working in OPSEC:
> >
> > - draft-behringer-lla-only
> > - draft-baker-opsec-passive-ip-address
> >
> > To some extent, draft-grow and draft-behringer are debating with one
> another. While draft-baker is not directly involved in the debate, it
> is not uninvolved, either. It is a shame that the three documents are
> being considered in different WGs.
>=20
> I think it a bigger shame that draft-ietf-grow-private-ip-sp-cores is
> not in the RFC Editor queue awaiting publication!
>=20
> It is a natural companion to RFC6598 and could have, should have, been
> in the queue at the same time.  This I-D was relevant when it was first
> written 2 years ago, and I see its relevance decreasing with time, as
> people stumble over the mistakes that this I-D could have prevented.
> It has taken those 2 years to get this I-D IETF-ready, little has
> changed in the content in that time, and it is time we got it out of
> the door.
>=20
> Of course there is scope for improvement, there always is, but that is
> an argument for never publishing anything.  If the authors of the other
> I-Ds want to build on it, then of course they can produce a bis that
> covers more, but let's publish what we have got.
>=20
> Tom Petch
>=20
> >
> > For the purpose of discussing these three documents, I think that a
> little cross-posting is acceptable.
> >
> > --------------------------
> > Ron Bonica
> > vcard:       www.bonica.org/ron/ronbonica.vcf
> >
> >
> > _______________________________________________
> > GROW mailing list
> > GROW@ietf.org
> > https://www.ietf.org/mailman/listinfo/grow
> >
>=20


From internet-drafts@ietf.org  Mon May 28 07:40:23 2012
Return-Path: <internet-drafts@ietf.org>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3ED8C21F8617; Mon, 28 May 2012 07:40:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, 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 2QQT1NkATaz3; Mon, 28 May 2012 07:40:22 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C177521F8543; Mon, 28 May 2012 07:40:22 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.02
Message-ID: <20120528144022.22998.91827.idtracker@ietfa.amsl.com>
Date: Mon, 28 May 2012 07:40:22 -0700
Cc: grow@ietf.org
Subject: [GROW] I-D Action: draft-ietf-grow-simple-va-06.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 28 May 2012 14:40:23 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies. This draft is a work item of the Global Routing Operations Working Gro=
up of the IETF.

	Title           : Simple Virtual Aggregation (S-VA)
	Author(s)       : Robert Raszuk
                          Alton Lo
                          Lixia Zhang
                          Xiaohu Xu
	Filename        : draft-ietf-grow-simple-va-06.txt
	Pages           : 10
	Date            : 2012-05-28

   The continued growth in the Default Free Routing Table (DFRT)
   stresses the global routing system in a number of ways.  One of the
   most costly stresses is FIB size: ISPs often must upgrade router
   hardware simply because the FIB has run out of space, and router
   vendors must design routers that have adequate FIB.

   FIB suppression is an approach to relieving stress on the FIB by NOT
   loading selected RIB entries into the FIB.  Simple Virtual
   Aggregation (S-VA) is a simple form of Virtual Aggregation (VA) that
   allows any and all edge routers to shrink their RIB and FIB
   requirements substantially and therefore increase their useful
   lifetime.

   S-VA does not increase FIB requirements for core routers.  S-VA is
   extremely easy to configure considerably more so than the various
   tricks done today to extend the life of edge routers.  S-VA can be
   deployed autonomously by an ISP (cooperation between ISPs is not
   required), and can co-exist with legacy routers in the ISP.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-grow-simple-va-06.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-grow-simple-va-06.txt

The IETF datatracker page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-grow-simple-va/


From internet-drafts@ietf.org  Mon May 28 15:28:34 2012
Return-Path: <internet-drafts@ietf.org>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EFC1221F86F4; Mon, 28 May 2012 15:28:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.229
X-Spam-Level: 
X-Spam-Status: No, score=-102.229 tagged_above=-999 required=5 tests=[AWL=0.370, BAYES_00=-2.599, 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 YI1xEq87nTW8; Mon, 28 May 2012 15:28:33 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7E03D21F86EB; Mon, 28 May 2012 15:28:33 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.02
Message-ID: <20120528222833.20085.21338.idtracker@ietfa.amsl.com>
Date: Mon, 28 May 2012 15:28:33 -0700
Cc: grow@ietf.org
Subject: [GROW] I-D Action: draft-ietf-grow-simple-va-07.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 28 May 2012 22:28:34 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies. This draft is a work item of the Global Routing Operations Working Gro=
up of the IETF.

	Title           : Simple Virtual Aggregation (S-VA)
	Author(s)       : Robert Raszuk
                          Jakob Heitz
                          Alton Lo
                          Lixia Zhang
                          Xiaohu Xu
	Filename        : draft-ietf-grow-simple-va-07.txt
	Pages           : 11
	Date            : 2012-05-28

   The continued growth in the Default Free Routing Table (DFRT)
   stresses the global routing system in a number of ways.  One of the
   most costly stresses is FIB size: ISPs often must upgrade router
   hardware simply because the FIB has run out of space, and router
   vendors must design routers that have adequate FIB.

   FIB suppression is an approach to relieving stress on the FIB by NOT
   loading selected RIB entries into the FIB.  Simple Virtual
   Aggregation (S-VA) is a simple form of Virtual Aggregation (VA) that
   allows any and all edge routers to shrink their RIB and FIB
   requirements substantially and therefore increase their useful
   lifetime.

   S-VA does not increase FIB requirements for core routers.  S-VA is
   extremely easy to configure considerably more so than the various
   tricks done today to extend the life of edge routers.  S-VA can be
   deployed autonomously by an ISP (cooperation between ISPs is not
   required), and can co-exist with legacy routers in the ISP.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-grow-simple-va-07.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-grow-simple-va-07.txt

The IETF datatracker page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-grow-simple-va/


From internet-drafts@ietf.org  Tue May 29 05:38:16 2012
Return-Path: <internet-drafts@ietf.org>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6090121F87EE; Tue, 29 May 2012 05:38:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, 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 J5R9XDj-v9Pq; Tue, 29 May 2012 05:38:15 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F00D021F87E2; Tue, 29 May 2012 05:38:15 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.02
Message-ID: <20120529123815.28895.32743.idtracker@ietfa.amsl.com>
Date: Tue, 29 May 2012 05:38:15 -0700
Cc: grow@ietf.org
Subject: [GROW] I-D Action: draft-ietf-grow-simple-va-08.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 May 2012 12:38:16 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies. This draft is a work item of the Global Routing Operations Working Gro=
up of the IETF.

	Title           : Simple Virtual Aggregation (S-VA)
	Author(s)       : Robert Raszuk
                          Jakob Heitz
                          Alton Lo
                          Lixia Zhang
                          Xiaohu Xu
	Filename        : draft-ietf-grow-simple-va-08.txt
	Pages           : 11
	Date            : 2012-05-29

   The continued growth in the Default Free Routing Table (DFRT)
   stresses the global routing system in a number of ways.  One of the
   most costly stresses is FIB size: ISPs often must upgrade router
   hardware simply because the FIB has run out of space, and router
   vendors must design routers that have adequate FIB.

   FIB suppression is an approach to relieving stress on the FIB by NOT
   loading selected RIB entries into the FIB.  Simple Virtual
   Aggregation (S-VA) is a simple form of Virtual Aggregation (VA) that
   allows any and all edge routers to shrink their RIB and FIB
   requirements substantially and therefore increase their useful
   lifetime.

   S-VA does not increase FIB requirements for core routers.  S-VA is
   extremely easy to configure considerably more so than the various
   tricks done today to extend the life of edge routers.  S-VA can be
   deployed autonomously by an ISP (cooperation between ISPs is not
   required), and can co-exist with legacy routers in the ISP.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-grow-simple-va-08.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-grow-simple-va-08.txt

The IETF datatracker page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-grow-simple-va/


From iesg-secretary@ietf.org  Tue May 29 09:07:22 2012
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E1A6411E8073; Tue, 29 May 2012 09:07:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, 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 arJG1FpKXLu1; Tue, 29 May 2012 09:07:22 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5EEEC21F8724; Tue, 29 May 2012 09:07:22 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 4.02
Message-ID: <20120529160722.12364.75583.idtracker@ietfa.amsl.com>
Date: Tue, 29 May 2012 09:07:22 -0700
Cc: grow@ietf.org
Subject: [GROW] Last Call: <draft-ietf-grow-simple-va-08.txt> (Simple Virtual	Aggregation (S-VA)) to Informational RFC
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: ietf@ietf.org
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 May 2012 16:07:23 -0000

The IESG has received a request from the Global Routing Operations WG
(grow) to consider the following document:
- 'Simple Virtual Aggregation (S-VA)'
  <draft-ietf-grow-simple-va-08.txt> as Informational RFC

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2012-06-12. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract


   The continued growth in the Default Free Routing Table (DFRT)
   stresses the global routing system in a number of ways.  One of the
   most costly stresses is FIB size: ISPs often must upgrade router
   hardware simply because the FIB has run out of space, and router
   vendors must design routers that have adequate FIB.

   FIB suppression is an approach to relieving stress on the FIB by NOT
   loading selected RIB entries into the FIB.  Simple Virtual
   Aggregation (S-VA) is a simple form of Virtual Aggregation (VA) that
   allows any and all edge routers to shrink their RIB and FIB
   requirements substantially and therefore increase their useful
   lifetime.

   S-VA does not increase FIB requirements for core routers.  S-VA is
   extremely easy to configure considerably more so than the various
   tricks done today to extend the life of edge routers.  S-VA can be
   deployed autonomously by an ISP (cooperation between ISPs is not
   required), and can co-exist with legacy routers in the ISP.




The file can be obtained via
http://datatracker.ietf.org/doc/draft-ietf-grow-simple-va/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-ietf-grow-simple-va/ballot/


No IPR declarations have been submitted directly on this I-D.



From robert@raszuk.net  Thu May 31 15:48:00 2012
Return-Path: <robert@raszuk.net>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 563EC21F8647 for <grow@ietfa.amsl.com>; Thu, 31 May 2012 15:48:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 mXu6xU+ogtm4 for <grow@ietfa.amsl.com>; Thu, 31 May 2012 15:47:59 -0700 (PDT)
Received: from mail1310.opentransfer.com (mail1310.opentransfer.com [76.162.254.103]) by ietfa.amsl.com (Postfix) with ESMTP id 8A6B021F863D for <grow@ietf.org>; Thu, 31 May 2012 15:47:59 -0700 (PDT)
Received: (qmail 13627 invoked by uid 399); 31 May 2012 22:47:58 -0000
Received: from unknown (HELO ?192.168.1.58?) (pbs:robert@raszuk.net@83.9.126.152) by mail1310.opentransfer.com with ESMTPM; 31 May 2012 22:47:58 -0000
X-Originating-IP: 83.9.126.152
Message-ID: <4FC7F51F.3090309@raszuk.net>
Date: Fri, 01 Jun 2012 00:47:59 +0200
From: Robert Raszuk <robert@raszuk.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: SM <sm@resistor.net>
References: <20120529160722.12364.75583.idtracker@ietfa.amsl.com> <6.2.5.6.2.20120531150923.098e3200@resistor.net>
In-Reply-To: <6.2.5.6.2.20120531150923.098e3200@resistor.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: grow@ietf.org, draft-ietf-grow-simple-va.all@tools.ietf.org
Subject: Re: [GROW] Last Call: <draft-ietf-grow-simple-va-08.txt> (Simple Virtual Aggregation (S-VA)) to Informational RFC
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: robert@raszuk.net
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 May 2012 22:48:00 -0000

Hi SM,

Very good catch ... repurposing APNIC IPv4 address space was not 
intended. Simply the address space in the example was chosen completely 
randomly.

I will remove that text from the final version of the document.

Thank you very much for your review,
R.

> At 09:07 29-05-2012, The IESG wrote:
>
>> The IESG has received a request from the Global Routing Operations WG
>> (grow) to consider the following document:
>> - 'Simple Virtual Aggregation (S-VA)'
>> <draft-ietf-grow-simple-va-08.txt> as Informational RFC
>>
>> The IESG plans to make a decision in the next few weeks, and solicits
>
> As a nit:
>
> "Generally, any more specific route which carries the same next hop as
> the VA-prefix 0/0 is eligible for suppression. However, provided
> that there was at least one less specific prefix (e.g., 1.0.0.0/8)
> and the next-hop of such prefix was different from that of the VA
> 0/0, those more specific prefixes (e.g., 1.1.1.0/24) which are
> otherwise subject to suppression would not be eligible for
> suppression anymore."
>
>  From APNIC:
>
> inetnum: 1.1.1.0 - 1.1.1.255
> netname: Debogon-prefix
> descr: APNIC Debogon Project
> descr: APNIC Pty Ltd
>
> Is there a reason why the Global Routing Operations WG is repurposing
> APNIC IPv4 address space in this draft?
>
> Regards,
> -sm
>
>


From sm@resistor.net  Thu May 31 15:28:21 2012
Return-Path: <sm@resistor.net>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4B3F621F85DF for <grow@ietfa.amsl.com>; Thu, 31 May 2012 15:28:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.481
X-Spam-Level: 
X-Spam-Status: No, score=-102.481 tagged_above=-999 required=5 tests=[AWL=0.118, BAYES_00=-2.599, 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 Qo+HRHcG6HHd for <grow@ietfa.amsl.com>; Thu, 31 May 2012 15:28:18 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 3642A21F85B9 for <grow@ietf.org>; Thu, 31 May 2012 15:28:18 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q4VMSAMs005967; Thu, 31 May 2012 15:28:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1338503295; i=@resistor.net; bh=a/iM63AW5hJ2dzo+US4JaHxX9PssVuWMLRWvTLAgW/Y=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=yzhfA7j1PDX+IK1eevcbOMiL5MrZi5znvGJ1tDi7SVdaN/+YfVLE0lcDWAdlTXN00 xtGqXY340dozCNeP6PmwtGsjQWKssWV1AY3bZSvlNktS/ffd/pX45ojCRHLa8U5D8p DN7dXtZygmNwnVcHS1qyaMteTwEad4qjPfhDYMpU=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1338503295; i=@resistor.net; bh=a/iM63AW5hJ2dzo+US4JaHxX9PssVuWMLRWvTLAgW/Y=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=ZApG9L1u9oOe48Dx9uYSPKXFSxlaLeO9mVZWPV9yTm2iOkyWdbvZx8TZKI3tXb1rN +lcbSKQbaRmEtOcWQrhoLnTdVkQDFN1vzZiYzpoEvS3H/wXTeRckflvB+BJN39x5jX x/74ziRr6XS380ImX41yo40IYUgCZE09KkP0fX4U=
Message-Id: <6.2.5.6.2.20120531150923.098e3200@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 31 May 2012 15:25:10 -0700
To: draft-ietf-grow-simple-va.all@tools.ietf.org
From: SM <sm@resistor.net>
In-Reply-To: <20120529160722.12364.75583.idtracker@ietfa.amsl.com>
References: <20120529160722.12364.75583.idtracker@ietfa.amsl.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Mailman-Approved-At: Thu, 31 May 2012 18:34:39 -0700
Cc: grow@ietf.org
Subject: Re: [GROW] Last Call: <draft-ietf-grow-simple-va-08.txt> (Simple Virtual Aggregation (S-VA)) to Informational RFC
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 May 2012 22:28:21 -0000

At 09:07 29-05-2012, The IESG wrote:

>The IESG has received a request from the Global Routing Operations WG
>(grow) to consider the following document:
>- 'Simple Virtual Aggregation (S-VA)'
>   <draft-ietf-grow-simple-va-08.txt> as Informational RFC
>
>The IESG plans to make a decision in the next few weeks, and solicits

As a nit:

   "Generally, any more specific route which carries the same next hop as
    the VA-prefix 0/0 is eligible for suppression.  However, provided
    that there was at least one less specific prefix (e.g., 1.0.0.0/8)
    and the next-hop of such prefix was different from that of the VA
    0/0, those more specific prefixes (e.g., 1.1.1.0/24) which are
    otherwise subject to suppression would not be eligible for
    suppression anymore."

 From APNIC:

   inetnum:        1.1.1.0 - 1.1.1.255
   netname:        Debogon-prefix
   descr:          APNIC Debogon Project
   descr:          APNIC Pty Ltd

Is there a reason why the Global Routing Operations WG is repurposing 
APNIC IPv4 address space in this draft?

Regards,
-sm 

