
From christopher.morrow@gmail.com  Sun Jul  1 18:24:13 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 8DD3111E8136 for <grow@ietfa.amsl.com>; Sun,  1 Jul 2012 18:24:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.486
X-Spam-Level: 
X-Spam-Status: No, score=-103.486 tagged_above=-999 required=5 tests=[AWL=0.114, 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 U5vwE0lC8Iw3 for <grow@ietfa.amsl.com>; Sun,  1 Jul 2012 18:24:13 -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 0330E11E811F for <grow@ietf.org>; Sun,  1 Jul 2012 18:24:12 -0700 (PDT)
Received: by obbwc20 with SMTP id wc20so8554086obb.31 for <grow@ietf.org>; Sun, 01 Jul 2012 18:24:16 -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; bh=z+WHQg/UiYQQoGmQo5YQUQB4wO5ic9EYbqWJKl5iYxo=; b=xyrq5r3NUZBzM2+OaLnG+kfkCxnz2y110sB2BCkHT76l5lYxa6kYmWH8LJ7sPW3bgv Z0XsPXrJ5Sy4KEEyrcFw3bnJH+FQ8Ir42u7k0f9pUAYA9HvPXiwfS2+ndTFMT1F8kWHm /+EB2u+RzHofhiZXxRKfbLSW5WJFpYjC9z9zuHw8dnHGGWh0AuhdJx0sxjXdWEQUWjLi leRjpJmpvJ8lA4xSs2BdGf8YX7/QJZ4fTC4TICytCweWak9W2LH/f3+B/zyuSsVMFQ/V x5H37YAtMewX3CRwawhddM+CSvBfeDxS9LdslyqQVdBrIFyuLs7NfDJALIbkBvya5vGI dAvw==
MIME-Version: 1.0
Received: by 10.60.9.134 with SMTP id z6mr11322275oea.46.1341192256348; Sun, 01 Jul 2012 18:24:16 -0700 (PDT)
Received: by 10.182.191.98 with HTTP; Sun, 1 Jul 2012 18:24:15 -0700 (PDT)
In-Reply-To: <4FEE5234.9000502@anthony-kirkham.com>
References: <CAL9jLabADdWCwDhBdaBJ4fVdk9a=OeJQYFQM4Z_+-P56cVWftw@mail.gmail.com> <20120627182652.GT18361@pfrc> <4FEE5234.9000502@anthony-kirkham.com>
Date: Sun, 1 Jul 2012 21:24:15 -0400
Message-ID: <CAL9jLaYC7dEHX-CCdZhNDqfbGJX6etbtzC2S=5D9UsEzr6FndA@mail.gmail.com>
From: Christopher Morrow <christopher.morrow@gmail.com>
To: tkirkham@anthony-kirkham.com
Content-Type: text/plain; charset=ISO-8859-1
Cc: "grow@ietf.org grow@ietf.org" <grow@ietf.org>, grow-chairs@tools.ietf.org
Subject: Re: [GROW] WGLC: 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: Mon, 02 Jul 2012 01:24:13 -0000

I'll be sending along the pub request monday.

On Fri, Jun 29, 2012 at 9:11 PM, Anthony Kirkham
<tkirkham@anthony-kirkham.com> wrote:
> On 28/06/12 4:26 AM, Jeffrey Haas wrote:
>>
>> On Tue, Jun 05, 2012 at 02:41:39PM -0400, Christopher Morrow wrote:
>>>
>>> Folks,
>>> There's been work on the draft:
>>>     <http://tools.ietf.org/html/draft-ietf-grow-private-ip-sp-cores>
>>>
>>> I think the commenters' comments were addressed by the authors.
>>> Can we move this to WGLC now and clear that 6/19/2012 (June 19, 2012).
>>
>> While it's long past this date, I haven't seen a note saying that the WGLC
>> concluded successfully.  So, I'll add in my support for publication FWIW.
>>
>> -- Jeff
>> _______________________________________________
>> GROW mailing list
>> GROW@ietf.org
>> https://www.ietf.org/mailman/listinfo/grow
>>
>>
> Jeff,
>
> Thank you for your support. I'm hoping this gets closed off soon.
>
> Tony K
>
> --
>

From tkirkham@anthony-kirkham.com  Mon Jul  2 17:02:11 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 395D611E80DB for <grow@ietfa.amsl.com>; Mon,  2 Jul 2012 17:02:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.691
X-Spam-Level: 
X-Spam-Status: No, score=-0.691 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908]
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 LRQU7sBMKtrl for <grow@ietfa.amsl.com>; Mon,  2 Jul 2012 17:02:10 -0700 (PDT)
Received: from nskntmtas05p.mx.bigpond.com (nskntmtas05p.mx.bigpond.com [61.9.168.149]) by ietfa.amsl.com (Postfix) with ESMTP id 8417511E80BF for <grow@ietf.org>; Mon,  2 Jul 2012 17:02:10 -0700 (PDT)
Received: from nskntotgx04p.mx.bigpond.com ([1.147.9.104]) by nskntmtas05p.mx.bigpond.com with ESMTP id <20120703000215.HSEJ24726.nskntmtas05p.mx.bigpond.com@nskntotgx04p.mx.bigpond.com>; Tue, 3 Jul 2012 00:02:15 +0000
Received: from Anthonys-MacBook-Pro.local ([1.147.9.104]) by nskntotgx04p.mx.bigpond.com with ESMTP id <20120703000214.EZPO21008.nskntotgx04p.mx.bigpond.com@Anthonys-MacBook-Pro.local>; Tue, 3 Jul 2012 00:02:14 +0000
Message-ID: <4FF23681.5040508@anthony-kirkham.com>
Date: Tue, 03 Jul 2012 10:02:09 +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:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: Christopher Morrow <christopher.morrow@gmail.com>
References: <CAL9jLabADdWCwDhBdaBJ4fVdk9a=OeJQYFQM4Z_+-P56cVWftw@mail.gmail.com> <20120627182652.GT18361@pfrc> <4FEE5234.9000502@anthony-kirkham.com> <CAL9jLaYC7dEHX-CCdZhNDqfbGJX6etbtzC2S=5D9UsEzr6FndA@mail.gmail.com>
In-Reply-To: <CAL9jLaYC7dEHX-CCdZhNDqfbGJX6etbtzC2S=5D9UsEzr6FndA@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Authentication-Info: Submitted using SMTP AUTH PLAIN at nskntotgx04p.mx.bigpond.com from [1.147.9.104] using ID anthony.kirkham at Tue, 3 Jul 2012 00:02:13 +0000
Cc: "grow@ietf.org grow@ietf.org" <grow@ietf.org>, grow-chairs@tools.ietf.org
Subject: Re: [GROW] WGLC: 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: Tue, 03 Jul 2012 00:02:11 -0000

Thanks heaps, is there anything I need to do I do from here?

Tony K

On 2/07/12 11:24 AM, Christopher Morrow wrote:
> I'll be sending along the pub request monday.
>
> On Fri, Jun 29, 2012 at 9:11 PM, Anthony Kirkham
> <tkirkham@anthony-kirkham.com> wrote:
>> On 28/06/12 4:26 AM, Jeffrey Haas wrote:
>>> On Tue, Jun 05, 2012 at 02:41:39PM -0400, Christopher Morrow wrote:
>>>> Folks,
>>>> There's been work on the draft:
>>>>      <http://tools.ietf.org/html/draft-ietf-grow-private-ip-sp-cores>
>>>>
>>>> I think the commenters' comments were addressed by the authors.
>>>> Can we move this to WGLC now and clear that 6/19/2012 (June 19, 2012).
>>> While it's long past this date, I haven't seen a note saying that the WGLC
>>> concluded successfully.  So, I'll add in my support for publication FWIW.
>>>
>>> -- Jeff
>>> _______________________________________________
>>> GROW mailing list
>>> GROW@ietf.org
>>> https://www.ietf.org/mailman/listinfo/grow
>>>
>>>
>> Jeff,
>>
>> Thank you for your support. I'm hoping this gets closed off soon.
>>
>> Tony K
>>
>> --
>>
>


-- 


From iesg-secretary@ietf.org  Tue Jul  3 14:34:05 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 2031F11E819D; Tue,  3 Jul 2012 14:34:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.48
X-Spam-Level: 
X-Spam-Status: No, score=-102.48 tagged_above=-999 required=5 tests=[AWL=0.119, 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 obvuxown2fwu; Tue,  3 Jul 2012 14:34:04 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CD45211E809C; Tue,  3 Jul 2012 14:34:03 -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.30
Message-ID: <20120703213403.2504.5668.idtracker@ietfa.amsl.com>
Date: Tue, 03 Jul 2012 14:34:03 -0700
Cc: grow@ietf.org
Subject: [GROW] Last Call: <draft-ietf-grow-private-ip-sp-cores-05.txt> (Issues with	Private IP Addressing in the Internet) 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, 03 Jul 2012 21:34:05 -0000

The IESG has received a request from the Global Routing Operations WG
(grow) to consider the following document:
- 'Issues with Private IP Addressing in the Internet'
  <draft-ietf-grow-private-ip-sp-cores-05.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-07-17. 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 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.




The file can be obtained via
http://datatracker.ietf.org/doc/draft-ietf-grow-private-ip-sp-cores/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-ietf-grow-private-ip-sp-cores/ballot/


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



From internet-drafts@ietf.org  Thu Jul  5 08:20:11 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 B43DB11E80BA; Thu,  5 Jul 2012 08:20:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.52
X-Spam-Level: 
X-Spam-Status: No, score=-102.52 tagged_above=-999 required=5 tests=[AWL=0.079, 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 Uk1LRUYddfHa; Thu,  5 Jul 2012 08:20:11 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1374B21F8782; Thu,  5 Jul 2012 08:20:11 -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.30
Message-ID: <20120705152011.2941.27855.idtracker@ietfa.amsl.com>
Date: Thu, 05 Jul 2012 08:20:11 -0700
Cc: grow@ietf.org
Subject: [GROW] I-D Action: draft-ietf-grow-simple-va-10.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, 05 Jul 2012 15:20:12 -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 Group o=
f 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-10.txt
	Pages           : 8
	Date            : 2012-07-05

Abstract:
   All BGP routers in the Default Free Zone (DFZ) are required to carry
   all the routes in the Default Free Routing Table (DFRT).  A technique
   is described that allows some BGP routers not to install all of those
   routes into the Forwarding Information Base (FIB).

   Some routers in an Autonomous System (AS) announce an aggregate (the
   VA prefix) in addition to the routes they already announce.  This
   enables other routers not to install the routes covered by the VA
   prefix into the FIB as long as those routes have the same next-hop as
   the VA prefix.

   The VA prefixes that are announced within an AS are not announced to
   any other AS.


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

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-grow-simple-va-10

A diff from previous version is available at:
http://tools.ietf.org/rfcdiff?url2=3Ddraft-ietf-grow-simple-va-10


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


From iesg-secretary@ietf.org  Thu Jul  5 10:42:53 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 850AC21F86FE; Thu,  5 Jul 2012 10:42:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.476
X-Spam-Level: 
X-Spam-Status: No, score=-102.476 tagged_above=-999 required=5 tests=[AWL=0.123, 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 8846Tt16z8Ds; Thu,  5 Jul 2012 10:42:53 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 053BB21F84C8; Thu,  5 Jul 2012 10:42:53 -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.30
Message-ID: <20120705174253.26525.88756.idtracker@ietfa.amsl.com>
Date: Thu, 05 Jul 2012 10:42:53 -0700
Cc: grow@ietf.org
Subject: [GROW] Last Call: <draft-ietf-grow-diverse-bgp-path-dist-07.txt>	(Distribution of diverse BGP paths.) 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: Thu, 05 Jul 2012 17:42:53 -0000

The IESG has received a request from the Global Routing Operations WG
(grow) to consider the following document:
- 'Distribution of diverse BGP paths.'
  <draft-ietf-grow-diverse-bgp-path-dist-07.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-07-19. 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 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.




The file can be obtained via
http://datatracker.ietf.org/doc/draft-ietf-grow-diverse-bgp-path-dist/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-ietf-grow-diverse-bgp-path-dist/ballot/


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



From ju1738@att.com  Sun Jul  8 06:36:21 2012
Return-Path: <ju1738@att.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 9A4B621F8663; Sun,  8 Jul 2012 06:36:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.729
X-Spam-Level: 
X-Spam-Status: No, score=-104.729 tagged_above=-999 required=5 tests=[AWL=-1.371, BAYES_40=-0.185, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_MED=-4, 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 LfROB0bekAGd; Sun,  8 Jul 2012 06:36:20 -0700 (PDT)
Received: from nbfkord-smmo03.seg.att.com (nbfkord-smmo03.seg.att.com [209.65.160.84]) by ietfa.amsl.com (Postfix) with ESMTP id B9CDF21F864A; Sun,  8 Jul 2012 06:36:19 -0700 (PDT)
Received: from unknown [144.160.112.28] (EHLO tlpi048.enaf.dadc.sbc.com) by nbfkord-smmo03.seg.att.com(mxl_mta-6.11.0-10) over TLS secured channel with ESMTP id 9ec89ff4.0.22645.00-458.57236.nbfkord-smmo03.seg.att.com (envelope-from <ju1738@att.com>);  Sun, 08 Jul 2012 13:36:42 +0000 (UTC)
X-MXL-Hash: 4ff98cea79bd13e5-9c4588bd0fa20d634e0cd54f71bb05f6b6bb3993
Received: from enaf.dadc.sbc.com (localhost.localdomain [127.0.0.1]) by tlpi048.enaf.dadc.sbc.com (8.14.5/8.14.5) with ESMTP id q68DaeYf026599; Sun, 8 Jul 2012 08:36:41 -0500
Received: from dalint01.pst.cso.att.com (dalint01.pst.cso.att.com [135.31.133.159]) by tlpi048.enaf.dadc.sbc.com (8.14.5/8.14.5) with ESMTP id q68DaaBR026564; Sun, 8 Jul 2012 08:36:37 -0500
Received: from MISOUT7MSGHUB9B.ITServices.sbc.com (misout7msghub9b.itservices.sbc.com [144.151.223.72]) by dalint01.pst.cso.att.com (RSA Interceptor); Sun, 8 Jul 2012 08:36:13 -0500
Received: from MISOUT7MSGUSR9I.ITServices.sbc.com ([144.151.223.56]) by MISOUT7MSGHUB9B.ITServices.sbc.com ([144.151.223.72]) with mapi id 14.02.0298.004; Sun, 8 Jul 2012 09:35:51 -0400
From: "UTTARO, JAMES" <ju1738@att.com>
To: "'Rob Shakir'" <rjs@rob.sh>
Thread-Topic: draft-ietf-grow-ops-reqs-for-bgp-error-handling-04
Thread-Index: Ac1Qh0AwzuLH5xBMSu2rz3aHemLX7wBK0QmAAAIbFGAAE+v4AABFsGbAAIK+tYAAGy5tQA==
Date: Sun, 8 Jul 2012 13:35:51 +0000
Message-ID: <B17A6910EEDD1F45980687268941550FB3287D@MISOUT7MSGUSR9I.ITServices.sbc.com>
References: <B17A6910EEDD1F45980687268941550FB1F5C0@MISOUT7MSGUSR9I.ITServices.sbc.com> <52CBEC1F-49E6-4656-A617-CAB7304479F0@rob.sh> <B17A6910EEDD1F45980687268941550FB20F89@MISOUT7MSGUSR9I.ITServices.sbc.com> <FB4C2B5B-E935-4972-ACDD-151AF87DC26A@rob.sh> <B17A6910EEDD1F45980687268941550FB2F6AA@MISOUT7MSGUSR9I.ITServices.sbc.com> <3FE3D8FD-7658-4A42-8D9E-2133825A4061@rob.sh>
In-Reply-To: <3FE3D8FD-7658-4A42-8D9E-2133825A4061@rob.sh>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.70.57.167]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-Spam: [F=0.2000000000; CM=0.500; S=0.200(2010122901)]
X-MAIL-FROM: <ju1738@att.com>
X-SOURCE-IP: [144.160.112.28]
X-AnalysisOut: [v=1.0 c=1 a=AwR8yoXkD5AA:10 a=81eWbNQ_HDgA:10 a=ofMgfj31e3]
X-AnalysisOut: [cA:10 a=BLceEmwcHowA:10 a=kj9zAlcOel0A:10 a=srMsL6ituuWTYe]
X-AnalysisOut: [ky9Bs9mA==:17 a=48vgC7mUAAAA:8 a=8ZcXN_yANpVvQNl1C-EA:9 a=]
X-AnalysisOut: [CjuIK1q_8ugA:10 a=lZB815dzVvQA:10 a=nY9Zm9b37MAMMyBa:21 a=]
X-AnalysisOut: [9Dej72qHM68fRHrk:21]
Cc: 'idr wg' <idr@ietf.org>, "'grow@ietf.org'" <grow@ietf.org>
Subject: Re: [GROW] draft-ietf-grow-ops-reqs-for-bgp-error-handling-04
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: Sun, 08 Jul 2012 13:36:21 -0000

Rob,

	Sorry, I meant to respond to you sooner.. In re good/bad paths...

Thanks,
	Jim Uttaro

">>> [Jim U>] I guess what I meant was the other paths that are considered =
good would be treated differently.. So in an environment where only paths w=
ith the mal-formed attr are affected by this error condition as opposed to =
an environment where all paths are affected ( withdrawn ) would create a in=
consistent view of the "good" paths across AS domains.. So not so much the =
"bad" paths but the "good" paths and how they may be treated differently..

[rjs]: I'm not sure I fully understand here:
	- Today: UPDATE is received from element A and found to be erroneous - ses=
sion is reset, downstream do not see any paths where A was the best-path in=
 the RIB.=20
	- With this draft: UPDATE is received from element A, found to be erroneou=
s, downstream still see all other paths where A is the best-path in the RIB=
.

[rjs]: I'm not sure that this is so much inconsistency of what the "good" p=
aths look like - both the receiving and downstream elements still consider =
A's paths as valid, other than the ones that were included in the erroneous=
 UPDATE. In both cases, the NLRI contained in the erroneous UPDATE is also =
not propagated downstream (session reset, or treat-as-withdraw stops the fu=
rther propagation).
"

I do not know if my concern actually matters.. My thought was that if AS1 a=
dvertises P(1)...P(n) to AS2 and AS3 and AS2 has deployed error handling an=
d AS3 has not, then in a mal-formed scenario AS3 would withdraw all paths a=
nd AS2 would only send a withdrawal for the bad paths.. There is no way of =
AS4 knowing that the "good" paths from AS2 are actually suspect..Not sure i=
f it matters and if AS4 could ever actually know without AS2 sending the "g=
ood" paths and informing downstream peers..

-----Original Message-----
From: Rob Shakir [mailto:rjs@rob.sh]=20
Sent: Thursday, June 28, 2012 4:49 AM
To: UTTARO, JAMES
Cc: 'grow@ietf.org'; 'idr wg'
Subject: Re: draft-ietf-grow-ops-reqs-for-bgp-error-handling-04

Hi Jim,

Apologies for the delay in replying to this message. Further discussion in-=
line marked [rjs].

On 25 Jun 2012, at 23:47, UTTARO, JAMES wrote:

> [rjs]: Absolutely, this is the current behaviour. The problem with taking=
 a whole session down in this case is that you now take a risk of inconsist=
ency for all NLRI across that session for the duration that you hold onto t=
he learned NLRI. If one avoids being in the situation where the session is =
down (e.g., by applying treat-as-withdraw behaviour in cases where one can =
determine the NLRI) then all other NLRI on the session continue to be updat=
ed as they need to be. It is only the NLRI that were included in the errone=
ous UPDATE that may be affected for looping/black-holing.
>=20
>=20
>>> [Jim U>] The assumption being that the error was caused by an upstream =
speaker and is therefore not truly indicative of an issue over the session =
where the error manifests itself. This seems to make sense in the IPV4 case=
. I am still a bit concerned as I do not understand how the following is ad=
dressed.
>=20

[rjs]: Actually, I think treat-as-withdraw applied more generally than opti=
onal-transitive only does not necessarily imply that the error was not the =
direct fault of the upstream speaker. However:

> - There is no way of knowing if the adjacent peer is the speaker that is =
actually responsible for the malformed attr or is coming from an upstream s=
peaker. I can think of no way of knowing this.. Can it be inferred from the=
 notion that an error is of the syntactic or semantic variety?

[rjs]: This is true, only where we have a mechanism such as the partial bit=
 in the optional transitive attribute can we infer that the directly attach=
ed neighbour did not look at the session. What the semantic and critical er=
rors that are called out in the draft relate to is the impact of the error =
on the resulting UPDATE message, rather than the direct neighbour being res=
ponsible for it.
[Jim U>] >>> Yup. I was hoping that it may  be possible to infer..=20

> - There seems to be no threshold when the session is actually taking out =
of service. It would seem that some number of these type of errors would in=
dicate a major issue is taking place and should be addressed by severing th=
e speaker that is advertising paths with the malformed attr into the topolo=
gy. A large number of these error will create a large number of withdrawn m=
essages being generated from many peers. What are your thoughts on how this=
 should be addressed?

[rjs]: This was something that has been discussed on the list previously. T=
here are two key questions in this space:

- Do you expect errors that are indicative of a whole box failure, that are=
 not related to a large change on the device (e.g., code upgrade) that affe=
ct all prefixes in a manner that the UPDATE message is formed well enough t=
o extract the NLRI?

- Is the state of reaching all prefixes withdrawn (with UPDATEs withdrawing=
 all NLRI being sent to all neighbours) an acceptable state? I think there =
is (of course) a scaling impact of such UPDATES being transmitted and parse=
d to all downstream neighbours, but the impact of such an event is really d=
ependent on assuming that large proportions of the UPDATEs generated become=
 erroneous.

I don't think that I can categorically state that the answer to the former =
is no, but I am not aware of the case. In my view, larger scale issues on t=
he BGP speaker (e.g., things that affect memory integrity etc.) result in f=
ailures that produce output that is not well enough formed to fall within t=
he "semantic" errors described in the draft. I would (of course) welcome im=
plementor and tester's feed back on this point.
[Jim U>] >>> Not sure either.. But that being said it would be good to seve=
r a speaker if the number of errors in some time t exceed a threshold..

>> I would expect all solutions implemented in response to these requiremen=
ts to be optional. If the risk of incorrectness is unacceptable to you/an o=
perator, then you should absolutely not enable any of these mechanisms. In =
a number of networks that I have operated, designed and architected, I am p=
repared to accept the risk of incorrectness, as I consider it acceptable wh=
en compared to the risk of complete service outages in terms of impact to m=
y customers during such incidents. At the moment, without the work describe=
d through the requirements outlined in this draft I do not have the means t=
o make that call...
>> [Jim U>] I do not understand how it is possible to make this configurabl=
e on a per session or AS basis..I would think all speakers participating in=
 a routing context would have to adhere to the same rules for a consistent =
view across domains.. In my reading of the IDR draft it seems that it would=
 be a MUST.. Maybe I should not be considering that IDR draft as the actual=
 realization of the reqs..
>=20
> [rjs]: The IDR draft is the solution for some of the requirements -- part=
icularly those described in Section 3 of the GROW draft.
>>> [Jim U>] Got it..
>=20
> [rjs]: I do not see why this behaviour needs to be consistent across doma=
ins?
>>> [Jim U>] Can you explain this

[rjs]: See later point about "good"/"bad" paths.=20

>=20
> [rjs]: Essentially, if I receive an invalid UPDATE message, and apply tre=
at-as-withdraw, if the advertising speaker did not know that this was erron=
eous then I end up with a different view of what is in the RIB than the adv=
ertising speaker does. If this was a prefix I had no other route to, then I=
 may black-hole, if it was one where it was a more-specific of some larger =
prefix, then we end up with the potential for loops.
>>> [Jim U>] Yes.. I am not sure I like the notion of forwarding loops espe=
cially for large flows..=20

[rjs]: The potential for loops exists in some specific scenarios I think --=
 especially those where there is a covering aggregate advertised to a speak=
er, and a more specific that advertised within that aggregate. If this is t=
he case, then in some cases, rather than forwarding back to the device adve=
rtising the more specific (i.e., the one that was withdrawn). I think the b=
elow example shows something like this - if 10.0.0.0/24 is advertised from =
C to B, then A forwards packets destined to 10.0.0.0/24, during the time th=
at this prefix is withdrawn, then this will loop. Now, I think that this is=
 a feature of this topology anyway, since where B-C is down, then there wil=
l be loops for 10/8 in B-D.

                         <-- 10.0.0.0/8 --
[ A ] --0.0.0.0/0--> [ B ] ---0.0.0.0/0---> [ D ]
                      |
                  10.0.0.0/24
                      |
                    [ C ]

[rjs]: There is then a discussion as to whether one would actually expect s=
uch topologies to occur in practical terms. Really, I'd rather expect that =
there are blackholes (e.g., I only had one path to A, and it got withdrawn,=
 if anyone forwards me packets destined for A, then I drop them) or (more l=
ikely in an Internet DFZ perspective) I converge to an alternate path I had=
 to that NLRI.

[rjs]: The reason that this is highlighted in the text is that introducing =
behaviour into the protocol such that loops may occur is obviously a compro=
mise to protocol correctness, that may be a compromise to overall network f=
orwarding integrity. It's important that this risk is understood, and balan=
ced against the wider impact of session tear down.=20

>=20
> [rjs]: If I am prepared to accept the black-holing or loops for the NLRI =
in the erroneous UPDATE as a risk, in favour of keeping the remaining NLRI =
working (and being updated/withdrawn if they change), then this is a local =
decision and I do not need to imply any behaviour of the neighbouring domai=
ns.
>>> [Jim U>] I guess what I meant was the other paths that are considered g=
ood would be treated differently.. So in an environment where only paths wi=
th the mal-formed attr are affected by this error condition as opposed to a=
n environment where all paths are affected ( withdrawn ) would create a inc=
onsistent view of the "good" paths across AS domains.. So not so much the "=
bad" paths but the "good" paths and how they may be treated differently..

[rjs]: I'm not sure I fully understand here:
	- Today: UPDATE is received from element A and found to be erroneous - ses=
sion is reset, downstream do not see any paths where A was the best-path in=
 the RIB.=20
	- With this draft: UPDATE is received from element A, found to be erroneou=
s, downstream still see all other paths where A is the best-path in the RIB=
.

[rjs]: I'm not sure that this is so much inconsistency of what the "good" p=
aths look like - both the receiving and downstream elements still consider =
A's paths as valid, other than the ones that were included in the erroneous=
 UPDATE. In both cases, the NLRI contained in the erroneous UPDATE is also =
not propagated downstream (session reset, or treat-as-withdraw stops the fu=
rther propagation).

> [rjs] I'd say that it's not just applicable to Ivy[46] in the Internet - =
but to numerous AFIs (there is a definite use-case for these solutions in L=
3VPN environments for instance). I am not saying that this is applicable or=
 desirable to be turned on for all AFIs -- but it seems to me that this is =
a per-operator, per-deployment decision, not a per-AFI one. For instance, i=
f we get an RTC UPDATE that is malformed, an operator may not want to tear =
down a session if it also carries other AFIs (e.g., Van[46] also) - in that=
 case, the operator may want to treat this UPDATE as withdrawing the {as, r=
oute-target} NLRI (consider that we have no *standardized* multi-session me=
chanism yet, and there are potential scaling impacts of multiple sessions).
>=20
>>> [Jim U>] Quite honestly AFs such as RT-C, Flowspec, etc... where the in=
fo being propagated is more akin to "configuration" not path info should pe=
rsist regardless of the session.. This goes to the heart of the discussion =
of BGP is used for many fields of use that require persistence. It is not o=
nly paths that use BGP for dissemination.. I would prefer that this solutio=
n is limited to AFs that disseminate reachability/path info not configurati=
on info..

[rjs]: The persistence discussion is a further optimization over this work =
I feel, it addresses (as you correctly said before) more failure cases. In =
the case that one UPDATE containing modifications to this configuration inf=
ormation is invalid, is it worth making the rest of it "stale" (and not abl=
e to be updated)? I think that in the case, you also want to keep as much o=
f the RIB/config info up-to-date as possible, therefore targeting the error=
 handling mechanism to the contained NLRI still seems advantageous.

[rjs]: Now, the question may be whether treat-as-withdraw is suitable in th=
ese cases -- is it better to remove the flow specification, or RT from thos=
e installed, or keep it and know that it might be stale? I'd be interested =
to hear your thoughts here.

[rjs]: On the point of addressing this per-AF, perhaps the text to add to t=
he draft is that behaviour such as treat-as-withdraw must (MUST?) be config=
urable on a per-AFI basis? The problem with stating something like this, is=
 what does one do when there is no multi-session, and it is disabled for on=
e AFI, yet enabled for another?=20

Thanks,
r.

From robert@raszuk.net  Mon Jul  9 06:02:35 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 887BF21F8600 for <grow@ietfa.amsl.com>; Mon,  9 Jul 2012 06:02:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.456
X-Spam-Level: 
X-Spam-Status: No, score=-2.456 tagged_above=-999 required=5 tests=[AWL=-0.084, 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 4IHm8lE3+Hmw for <grow@ietfa.amsl.com>; Mon,  9 Jul 2012 06:02:35 -0700 (PDT)
Received: from mail1310.opentransfer.com (mail1310.opentransfer.com [76.162.254.103]) by ietfa.amsl.com (Postfix) with ESMTP id AA84B21F8669 for <grow@ietf.org>; Mon,  9 Jul 2012 06:02:34 -0700 (PDT)
Received: (qmail 4463 invoked by uid 399); 9 Jul 2012 13:02:59 -0000
Received: from unknown (HELO ?192.168.1.91?) (pbs:robert@raszuk.net@83.31.219.81) by mail1310.opentransfer.com with ESMTPM; 9 Jul 2012 13:02:59 -0000
X-Originating-IP: 83.31.219.81
Message-ID: <4FFAD681.70607@raszuk.net>
Date: Mon, 09 Jul 2012 15:02:57 +0200
From: Robert Raszuk <robert@raszuk.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: riwhite@verisign.com, "Retana, Alvaro" <alvaro.retana@hp.com>,  Susan Hares <skh@ndzh.com>
References: <CAL9jLabOs02rOti4tezaZiHyiOD2f9vAhsoE9c-afFb4J1xYXQ@mail.gmail.com> <DCC302FAA9FE5F4BBA4DCAD46569377917449AF235@PRVPEXVS03.corp.twcable.com> <F8659490-D1B2-477D-ADCC-EC6FD7AD073A@rob.sh>
In-Reply-To: <F8659490-D1B2-477D-ADCC-EC6FD7AD073A@rob.sh>
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-ops-reqs-for-bgp-error-handling-04
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, 09 Jul 2012 13:02:35 -0000

Hi Russ,

Regarding your topology:

                     (   )
            /-------( AS2 )--------\
     (   ) /         (   )          \ (   )       (   )
    ( AS1 )                          ( AS4 )-----( AS5 )
     (   ) \         (   )          / (   )       (   )
            \-------( AS3 )--------/
                     (   )

    o  AS1 is advertising 192.0.2.128/25 to both AS2 and AS3.

    o  AS2 is advertising both 192.0.2.128/25 and 192.0.2.0/24 into AS4.

    o  AS3 is advertising 192.0.2.128/25 into AS4


I am afraid you are too optimistic :)

The most common scenario I see is that AS2 only advertises to AS4 the 
aggregate so 192.0.2.0/24. That means that your 192.0.2.128/25 would 
never get "BOUNDED" status hence the other path via AS3 will continue 
worldwide via AS4.

Contrary as you very well know the alternative proposal 
http://tools.ietf.org/id/draft-marques-idr-aggregate-00.txt seems to 
address the above case as well as all cases you are trying to cover. 
Could you comment and compare both solutions especially as a (co-)author 
of both ;).

Best,
R.


From robert@raszuk.net  Tue Jul 10 01:50: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 590D211E80A0 for <grow@ietfa.amsl.com>; Tue, 10 Jul 2012 01:50:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.457
X-Spam-Level: 
X-Spam-Status: No, score=-2.457 tagged_above=-999 required=5 tests=[AWL=-0.085, 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 DFOzPv8I6xH7 for <grow@ietfa.amsl.com>; Tue, 10 Jul 2012 01:49:59 -0700 (PDT)
Received: from mail1310.opentransfer.com (mail1310.opentransfer.com [76.162.254.103]) by ietfa.amsl.com (Postfix) with ESMTP id 84E7A11E808E for <grow@ietf.org>; Tue, 10 Jul 2012 01:49:59 -0700 (PDT)
Received: (qmail 2639 invoked by uid 399); 10 Jul 2012 08:50:25 -0000
Received: from unknown (HELO ?192.168.1.58?) (pbs:m42@mojaklasa.info@83.31.246.125) by mail1310.opentransfer.com with ESMTPM; 10 Jul 2012 08:50:25 -0000
X-Originating-IP: 83.31.246.125
Message-ID: <4FFBECCE.6050000@raszuk.net>
Date: Tue, 10 Jul 2012 10:50:22 +0200
From: Robert Raszuk <robert@raszuk.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: "White, Russell" <riwhite@verisign.com>
References: <CAL9jLabOs02rOti4tezaZiHyiOD2f9vAhsoE9c-afFb4J1xYXQ@mail.gmail.com> <DCC302FAA9FE5F4BBA4DCAD46569377917449AF235@PRVPEXVS03.corp.twcable.com> <F8659490-D1B2-477D-ADCC-EC6FD7AD073A@rob.sh>, <4FFAD681.70607@raszuk.net> <3F74C1962631E14292BBF1B1B5F7021E043516@BRN1WNEXMBX01.vcorp.ad.vrsn.com>
In-Reply-To: <3F74C1962631E14292BBF1B1B5F7021E043516@BRN1WNEXMBX01.vcorp.ad.vrsn.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "grow@ietf.org" <grow@ietf.org>, Susan Hares <skh@ndzh.com>
Subject: Re: [GROW] WGLC: draft-ietf-grow-ops-reqs-for-bgp-error-handling-04
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, 10 Jul 2012 08:50:00 -0000

Hey Russ,

> o  AS1 is advertising 192.0.2.128/25 to both AS2 and AS3.
> o  AS2 is advertising both 192.0.2.128/25 and 192.0.2.0/24 into AS4.
> o  AS3 is advertising 192.0.2.128/25 into AS4
>
> I am afraid you are too optimistic :) ==
>
> Actually, this is really simple to fix in one of two ways.
>
> First, AS4 could see the overlap on the outbound side, note the
> origin AS is the same, and set the longer prefix to NO_EXPORT.

I don't think this is as simple as this ... Remember that when the less 
specific (/24) goes away the AS4 must readvertise the more specifics not 
to break routing. So therefor I do not think that any simple policy 
would work. The choice/decision what to advertise and what not must be 
done at best path run.

> Alternatively, the BGP implementation in AS4 could be modified so
> that when running bestpath if a losing route has a specific
> community, it is transferred to the winning route. This would allow
> the winning route to gain the BOUNDED community in processing.

Actually I am not that clear I understand this business reg communities 
marking. How about we consider even much simpler and ASBR local solution:

"If we are advertising on EBGP (so setting next hop self) and there are 
less specific covering more specific routes the more specific can be 
suppressed from advertisement."

Of course the implementation must back walk when the less specific goes 
away, but this is anyway required in all of the above.


> == The most common scenario I see is that AS2 only advertises to AS4
> the aggregate so 192.0.2.0/24. That means that your 192.0.2.128/25
> would never get "BOUNDED" status hence the other path via AS3 will
> continue worldwide via AS4. ==
>
> I rarely see this --because most of the time, folks want to "cover"
> the longer match with a shorter one, in case the longer prefix fails
> for some reason. With a covering route, both ISPs will be used for
> inbound traffic, and not just the one with the remaining longer
> prefix. This has been the recommended configuration for years,
> AFAIK.

If this is PI address given to a customer I actually do not know any ISP 
who would advertise his smaller blocks in addition to his aggregate 
those blocks are taken from. Only for backdoor/multihoming the smaller 
blocks get advertised via some other ISPs, but never directly connected.


> == Contrary as you very well know the alternative proposal
> http://tools.ietf.org/id/draft-marques-idr-aggregate-00.txt seems to
> address the above case as well as all cases you are trying to cover.
> Could you comment and compare both solutions especially as a
> (co-)author of both ;). ==
>
> I prefer the simpler solution presented in the draft we just
> published. Draft-marquis and the virtual aggregation drafts both add

Just to be very clear .. VA (any of the VA drafts) does not talk about 
the same problem. For one it does not stop BGP from advertising anything 
and second it is intra-domain solution.

> a lot of complexity to operations, while the BOUNDED community is
> very simple, and can (mostly) be implemented today with no changes to
> BGP, no changes to current traffic engineering, and no increased
> stretch within the SP network. Complexity can always be added, but a
> simple system on which future modifications can be made to cover
> corner cases seems like a better idea to me... :-)

Simple but not simpler ....


Best,
R.


From robert@raszuk.net  Tue Jul 10 07:59:45 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 C17EF11E80EC for <grow@ietfa.amsl.com>; Tue, 10 Jul 2012 07:59:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.455
X-Spam-Level: 
X-Spam-Status: No, score=-2.455 tagged_above=-999 required=5 tests=[AWL=-0.083, 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 oGRNcBTv1c4Q for <grow@ietfa.amsl.com>; Tue, 10 Jul 2012 07:59:44 -0700 (PDT)
Received: from mail1310.opentransfer.com (mail1310.opentransfer.com [76.162.254.103]) by ietfa.amsl.com (Postfix) with ESMTP id 9992411E808D for <grow@ietf.org>; Tue, 10 Jul 2012 07:59:43 -0700 (PDT)
Received: (qmail 6711 invoked by uid 399); 10 Jul 2012 15:00:10 -0000
Received: from unknown (HELO ?192.168.1.91?) (pbs:robert@raszuk.net@83.31.195.79) by mail1310.opentransfer.com with ESMTPM; 10 Jul 2012 15:00:10 -0000
X-Originating-IP: 83.31.195.79
Message-ID: <4FFC4378.7090505@raszuk.net>
Date: Tue, 10 Jul 2012 17:00:08 +0200
From: Robert Raszuk <robert@raszuk.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: "White, Russell" <riwhite@verisign.com>
References: <CAL9jLabOs02rOti4tezaZiHyiOD2f9vAhsoE9c-afFb4J1xYXQ@mail.gmail.com> <DCC302FAA9FE5F4BBA4DCAD46569377917449AF235@PRVPEXVS03.corp.twcable.com> <F8659490-D1B2-477D-ADCC-EC6FD7AD073A@rob.sh>, <4FFAD681.70607@raszuk.net> <3F74C1962631E14292BBF1B1B5F7021E043516@BRN1WNEXMBX01.vcorp.ad.vrsn.com>, <4FFBECCE.6050000@raszuk.net> <3F74C1962631E14292BBF1B1B5F7021E043924@BRN1WNEXMBX01.vcorp.ad.vrsn.com>
In-Reply-To: <3F74C1962631E14292BBF1B1B5F7021E043924@BRN1WNEXMBX01.vcorp.ad.vrsn.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "grow@ietf.org" <grow@ietf.org>, Susan Hares <skh@ndzh.com>
Subject: Re: [GROW] WGLC: draft-ietf-grow-ops-reqs-for-bgp-error-handling-04
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, 10 Jul 2012 14:59:45 -0000

>> I don't think this is as simple as this ... Remember that when the
>> less specific (/24) goes away the AS4 must readvertise the more
>> specifics not to break routing. So therefor I do not think that any
>> simple policy would work. The choice/decision what to advertise and
>> what not must be done at best path run.
>
> Sure --but won't best path be run when the best path towards a
> specific destination falls out of the table?

Best path today does not compare /16 and /24. In Pedro's proposal it does.

>> Actually I am not that clear I understand this business reg
>> communities marking. How about we consider even much simpler and
>> ASBR local solution:
>
> A local ASBR only solution won't work for various reasons, so let's
> not. :-)

I think it works. The example is comparing all best path eligible
attributes of less and more specific during best path and if the less
specific would win suppress the more specific.

I am only not sure if we really need to compare all. For example I am
not sure that like in your proposal it really matters if the more
specific was received over the same session as less specific (provided
that actually happens that often as you say :-)

> So what you are saying is that if a provider owns 10.1.0.0/16, and
> gives out 10.1.1.0/24 to a customer to advertise through some other
> provider the customer is connected to, the provider would never
> advertise 10.1.1.0/24 as well as 10.1.0.0/16? Why not? Since the
> longest match always wins, what you're saying is that the provider
> that handed out the address space would end up routing through the
> competing provider (the customer's other provider) to reach the
> customer, because there is a longer match being advertised by the
> customer through the competing provider.
>
> That doesn't make any sense to me.

That has been for years common recommendation of any RIR ... That's the 
value of PA addresses. Multihomers were told to get PI which indeed does 
not make the BGP table smaller.

Examples:

"Announcement of initial allocation as a single entity"
http://meetings.ripe.net/ripe-53/presentations/rou-ps-rou.pdf

"Advertisement of more specific prefixes should not be used unless
absolutely necessary and, where sensible, a covering aggregate
should also be advertised.  Further, LIRs should use BGP methods
such as NO_EXPORT [RFC-1997] and NOPEER [RFC-3765] or provider-specific
communities, as described in [RIPE-399] to limit the propagation of
more specific prefixes in the routing table."
SRC: ripe-532.txt


>> Just to be very clear .. VA (any of the VA drafts) does not talk
>> about the same problem. For one it does not stop BGP from
>> advertising anything and second it is intra-domain solution.
>
> Right --the VA drafts increase stretch and don't reduce the total
> table size for anyone.

It never intended to. It reduces the local RIB/FIB size. I am not even 
sure why you are comparing apple to oranges here :)

Best,
R.

From rjs@rob.sh  Tue Jul 10 09:26:40 2012
Return-Path: <rjs@rob.sh>
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 EAF3011E80ED for <grow@ietfa.amsl.com>; Tue, 10 Jul 2012 09:26:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.4
X-Spam-Level: 
X-Spam-Status: No, score=-0.4 tagged_above=-999 required=5 tests=[AWL=-1.972,  BAYES_00=-2.599, FB_INCREASE_VOL=3.629, SARE_MILLIONSOF=0.315,  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 mbfUtctKgt7U for <grow@ietfa.amsl.com>; Tue, 10 Jul 2012 09:26:39 -0700 (PDT)
Received: from cappuccino.rob.sh (cappuccino.rob.sh [IPv6:2001:b98:201:101::10:cafe]) by ietfa.amsl.com (Postfix) with ESMTP id 5C2D911E809A for <grow@ietf.org>; Tue, 10 Jul 2012 09:26:38 -0700 (PDT)
Received: from [109.144.227.140] (helo=[10.10.3.89]) by cappuccino.rob.sh with esmtpa (Exim 4.72) (envelope-from <rjs@rob.sh>) id 1SodFl-0006ft-Hz; Tue, 10 Jul 2012 17:25:33 +0100
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=us-ascii
From: Rob Shakir <rjs@rob.sh>
In-Reply-To: <D05A81B4-1317-4C13-A2D6-05F5B41096CA@castlepoint.net>
Date: Tue, 10 Jul 2012 17:27:03 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <09B801B2-B2AD-407F-B542-B02AEB997077@rob.sh>
References: <CAL9jLabOs02rOti4tezaZiHyiOD2f9vAhsoE9c-afFb4J1xYXQ@mail.gmail.com> <DCC302FAA9FE5F4BBA4DCAD46569377917449AF235@PRVPEXVS03.corp.twcable.com> <D05A81B4-1317-4C13-A2D6-05F5B41096CA@castlepoint.net>
To: Shane Amante <shane@castlepoint.net>
X-Mailer: Apple Mail (2.1257)
Cc: "grow@ietf.org grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] WGLC: draft-ietf-grow-ops-reqs-for-bgp-error-handling-04
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, 10 Jul 2012 16:26:41 -0000

Hi Shane,

Thanks very much for the detailed review of this document, and apologies =
it has taken a short while for me to reply.

I've responded to your comments in-line as [rjs].

On 25 Jun 2012, at 22:15, Shane Amante wrote:

> I've read this draft and support it being published as an =
Informational RFC.
>=20
> I do have some comments, which are not blocking, but that I do hope =
improve the clarity & readability of the draft.
>=20
> 1)  In Section 1.1, the following paragraph hints at the problems with =
current network architectures, but doesn't really come out and say what =
they are more directly.
> ---snip---
> Traditional network architectures would deploy an Interior Gateway
> Protocol (IGP) to carry infrastructure and customer prefixes, with an
> Exterior Gateway Protocol (EGP) such as BGP being utilised to
> propagate these prefixes to other Autonomous Systems.  [...]
> ---snip---
> IMO, it would be better if the following section more directly said =
that scale, in terms of the sheer amount of routing information in BGP, =
has increased substantially, particularly in places like the core of a =
Route Reflection hierarchy with order _several_ million paths, and =
rising.  I wish I could point you at a link to a talk Danny & I gave to =
GROW and/or IDR at IETF 71 (?), but unfortunately I can't find a copy of =
the slides on the IETF's Web site.  You can see that it's in the GROW WG =
Agenda at IETF 71, but the slides link to a different presentation: =
<http://tools.ietf.org/wg/grow/agenda?item=3Dagenda71.html>
>=20
> Anyway, IMO, this is (from my vantage point) the single factor that =
makes outages not only much more visible, but /also/ (just as =
importantly) take longer to recover from ... (at the end of the day, CPU =
is finite, there are no "easy" answers wrt using multi-core processors =
to speed-up convergence of single AFI's, DRAM speeds are not keeping =
pace, etc.)  This may be useful to mention here to "set the stage", as =
it were, since throughout the draft there's a continuous (and, good) =
dialogue of not making convergence times worse or CPU load increase as a =
result of incorporating better recovery capabilities.  IOW, another =
benefit you don't really mention anywhere, but probably should, is that =
/theoretically/ some of these mechanisms may help further promote =
scalability of BGP.  Obviously, we won't know that until we are =
evaluating solutions and researchers have time to study them, etc.

[rjs]: I tried to add something to cover this that fits in with Section =
1.1:

                        <t>
                            The combination of the increased number of =
deployments of BGP-4 as an intra-AS routing protocol, its use for the =
propagation of additional types of routing and service information, and =
the growth of IP services has resulted in a substantial increase in the =
volume of information carried within BGP-4. In numerous networks, RIB =
sizes of the order of millions of entries exist, with particular =
high-scale points existing at BGP speakers performing aggregation or =
functionality designed improve utilisation of network resources (e.g., =
route reflector hierarchies). Whilst clearly an increase in the amount =
routing information carried in BGP results in greater impact to services =
during failures, it is also critical to their recovery time. The =
increased time to compute new paths following a failures and =
subsequently re-learn them following recoveries results in greater =
impact of failures within the protocol, and hence adds further weight to =
the requirement to avoid failures affecting all routing, or service, =
information carried via a particular adjacency. Whilst an argument could =
be made the convergence time of BGP-4 can be reduced through additional =
computational resource being deployed, it is notable that significant =
challenges continue to exist for operators of scaling BGP-4, and hence =
mechanisms which improve the scalability of the protocol are of =
particular note.
                        </t>

[rjs]: Do you think this captures the point that was missing? I tried to =
avoid making any point that asserts that the requirements defined are =
going to make BGP scale better, but rather just call out that =
operationally, throwing resources at the problem isn't something that's =
always possible, so anything that reduces the amount of "work" BGP needs =
to do is interesting.

>=20
> Related to the above, there is also the following paragraph:
> ---snip---
> Along with this change in role, the nature of the IP routing
> information that is carried has changed.  BGP has become a ubiquitous
> means by which service information can be propagated between devices.
> ---snip---
> ... it may be better to say that the original scope of BGP wrt *just* =
exchanging reachability information has expanded to include functions =
that *were* typically in the domain of 'traditional' provisioning =
activities, and leave it at that.  (You are obviously familiar with =
things like BGP A-D + VPLS-LDP vs. VPLS-BGP vs. RFC 4364 ... where the =
former divorces service discovery [provisioning] from signaling/network =
reachability, whereas the latter two tightly couple service discovery & =
network reachability).

[rjs]: I'm not quite clear on whether this gets the point across =
completely - do we think that it is just that things have become in the =
realm of provisioning activities, or rather is it that there are more =
and more functions that are overloading onto BGP. I agree that this =
sentence doesn't necessarily capture that - but do you think that it's =
the generic information transfer protocol between PEs, as well as =
replacing provisioning mechanisms?

>=20
> 2)  In Section 3, wrt the discussion on =
draft-ietf-idr-optional-transitive, it may be much more compelling to =
state that practically this solution has (currently) only been defined =
to be applicable to 3 out of the 29 total BGP path attributes that have =
been assigned by IANA, at this time.  And, even if you *could* to go =
farther, then only 10 out of the total 29 BGP path attributes are =
optional transitive.  So, the short story is: a lot more work in the =
area of session preservation
> of iBGP sessions remains to be done, in particular wrt the other types =
of mandatory, discretionary, etc. attributes ... (assuming that such a =
thing is even technically possible with BGPv4, as we know it).

[rjs]: Agreed, it is definitely worth highlighting this. I amended the =
paragraph mentioned to cover this:

                    <t>
                        At the time of writing, error handling =
mechanisms related to optional, transitive attributes - such as <xref =
target=3D'I-D.ietf-idr-optional-transitive' /> are restricted to =
handling only a subset of attribute errors - whereas the operational =
requirement is to expand this coverage to the widest set of errors =
possible (i.e., all semantic errors within UPDATE messages). =
Additionally, where approaches applicable to a greater number of =
attributes are proposed (e.g., <xref =
target=3D'I-D.chen-ebgp-error-handing'>), these are limited to =
deployment in eBGP applications only, where requirements also exist in =
intra-domain cases. As such, it is envisaged that if extended to cover =
these expanded cases, these mechanisms provide a means to avoid the =
transmission of a NOTIFICATION message to a remote BGP speaker, based on =
a single erroneous message, where at all possible, and hence meet this =
requirement. Critical errors, including those whereby the NLRI cannot be =
extracted from the UPDATE message, represent cases whereby the receiving =
system cannot handle the error gracefully based on this mechanism.
                    </t>


>=20
> [ snipped ]
>=20
> 4)  In Section 4, I can't really discern a strong (?) preference for =
one of the associated recommendations to recovering RIB consistency.  I =
*think* what you should say, more clearly, is there is a strong =
preference toward narrow, targeted refresh mechanisms covering specific =
routes over those broader solutions (recovering an entire Adj-RIB-In), =
to reduce the
> impact on CPU, DRAM, etc.  Perhaps you could add a sentence at the end =
of the 4th paragraph, where you discuss draft-zeng-one-time-prefix-orf, =
along the lines of what I just mentioned above?  The good news is you =
state this very clearly, but much later, in Section 7.  Perhaps you can =
pull this sentence from Section 7 up to Section 4, as well?
> ---snip---
> [...] It is recommended that where available, any automatic (or
> manual) triggered recovery mechanism behaviour utilises such targeted
> means in preference to any whole RIB refresh mechanism (such as
> ROUTE-REFRESH).
> ---snip---=20

[rjs]: Agreed, yes. I think that there is a strong preference for the =
targeted mechanism in terms of scale. I rephrased the Section 3 text to =
be stronger, and left in the Section 7 text:

	<t>
		Whilst re-advertisement of the whole BGP RIB provides a =
means by which withdrawn NLRI can be re-advertised, there are some =
scaling implications that must be considered. In the case that a =
ROUTE-REFRESH is generated, all NLRI must be re-packed into UPDATE =
messages and advertised by one speaker on the BGP session, whilst the =
other must receive all UPDATE messages, and validate the RIB's =
consistency. In order to avoid the control-plane load, it is therefore a =
requirement to utilise targeted mechanisms where possible, rather than =
incurring the additional load on both the advertising and receiving =
speaker of building and processing UPDATEs for the entire contents of =
the RIB.
	</t>


> 5)  Section 5 seems targeted solely at recreating the data structures =
at one side of a BGP session, (specifically a receiver of a BGP =
session).  However, who's to say the corruption is not actually in the =
Adj-RIB-Out of the BGP transmitter?  Thus, transmitting you an =
Adj-RIB-Out all over again, even "gracefully", is unlikely to do much =
good.  Perhaps it would be good to consider whether the "Receiving =
Speaker", in Graceful Restart terminology, should consider 'gracefully' =
purging and recreating his Adj-RIB-Out data structures, as well, before =
re-xmit'ing them to the "Restarting Speaker"?

[rjs]: Absolutely, this definitely wasn't handled in the draft -- thanks =
for pointing it out. I added the following text - do you think this is =
sufficient?

                    <t>
                        In some cases, the erroneous condition may be =
due to corruption of the Adj-RIB-Out on the advertising BGP speaker - =
rather than caused by the receiving speaker's state. In these cases, =
where existing structures are replayed whilst performing graceful =
restart functionality, the error condition is not necessarily resolved. =
Therefore, it is recommended that during a session restart event, as =
described within this section, the advertising speaker purge and rebuild =
RIB structures, in order to resolve any corruption within these =
structures.
                    </t>=20

>=20
>=20
>=20
>=20
> Nits:
> 1)  =46rom <http://tools.ietf.org/html/rfc4271#section-3.1>:
> ---snip---
> For the purpose of this protocol, a route is defined as a unit of
> information that pairs a set of destinations with the attributes of a
> path to those destinations.  The set of destinations are systems
> whose IP addresses are contained in one IP address prefix that is
> carried in the Network Layer Reachability Information (NLRI) field of
> an UPDATE message, and the path is the information reported in the
> path attributes field of the same UPDATE message.
> ---snip---
> ... thus, to be more correct, I think you should scrub the document to =
say "route" in places where you're saying "prefix".  Some examples =
include:
>=20
> =
http://tools.ietf.org/html/draft-ietf-grow-ops-reqs-for-bgp-error-handling=
-04#section-1.2
> ---snip---
> o  It is unacceptable within modern deployments of the BGP-4 protocol
>   that a single erroneous UPDATE packet affects prefixes that it
>   does not carry.  This requirement therefore requires some
> ---snip---
> s/affects prefixes/affects routes/
>=20
> ---snip---
> this reset of the BGP-4 session results in interruption to
> forwarding packets (by means of withdrawing prefixes installed by
> BGP-4 into a device's RIB, and subsequently FIB).  To this end,
> ---snip---
> s/withdrawing prefixes/withdrawing routes/

[rjs]: Thanks, I've done this to reflect this definition.

>=20
> 2)  In Section 2, this may be just wording, but I'm unclear on what =
you mean in the below where you say: "... handle the error in a manner =
focused on the NLRI contained within the message".  Are you trying to =
say something like "constrain the logging and/or ignoring of malformed =
UPDATE messages specific to the narrowest subset of routes for which =
malformed path attributes have been received?"  I'm not suggesting my =
wording is necessarily better, in this case, but perhaps you could look =
at being a bit more precise below?
> ---snip---
> Where an UPDATE message is considered invalid by a BGP speaker due to
> an error within a path attribute that is not the NLRI (where the
> definition of NLRI includes reachability information encoded in the
> MP_REACH_NLRI and MP_UNREACH_NLRI attributes as specified in
> [RFC4760]) it is a requirement of any enhanced error handling
> mechanism to handle the error in a manner focused on the NLRI
> contained within the message. =20
> ---snip---

[rjs]: Yes - the intention is to define this based on the narrowest set =
possible, the reason that I used this wording is that (in my view) this =
is defined by the NLRI actually in the message (if there were differing =
path attributes for NLRI, then we expect that this is packed into a =
second UPDATE message). Perhaps a hybrid of our wording would clarify =
this (unless you think the assertion above is erroneous?).

>=20
> 3)  Section 2:
> ---snip---
> contained within the message.  Since in this case, the message
> received from the remote peer is syntactically valid, it is
> considered that such an UPDATE is indicative of erroneous data within
> a path attribute.  [...]
> ---snip---
> s/path attribute/path attributes/

[rjs]: Is the point here "one or more path attributes"? I'm not sure I =
quite understand the nit? :-)

>=20
> 4)  In Section 4, there do you really mean "transitive" here or do you =
instead mean "transient"?
> ---snip---
> It is of particular note for both means of recovering RIB consistency
> described that these are effective only when considering transitive
> errors within an implementation - for instance, should an RFC ...
> ---snip---

[rjs]: Transient, thanks.

> ... also, in the following, do you mean "dynamic" instead of =
"transitive" in the below?
> ---snip---
> [...] It is not advisable that a transitive
> filter and advertisement mechanism is triggered by all error handling
> events due to the load this is likely to place on the neighbour
> receiving such a request.  Where this BGP speaker is a relatively
> ---snip---

[rjs]: Dynamic is definitely what is meant here.

>=20
> 5)  In Section 7.1, I think you probably want to s/NLRI/route/ in =
several places, e.g.:
> ---snip---
> ... upstream speaker to perform a best-path selection, and =
re-advertise a
> new set of __NLRI__ before the downstream system is able to converge =
to a
> new path.
> ---snip---

[rjs]: Thanks, nit corrected.

Many thanks again for your comments - if you could cast your eyes over =
the above corrections, and let me know if you feel they're sufficient, =
that'd be fantastic.

In response to all the comments received during this review period, I'll =
push an -05 of the draft.

Kind regards,
r.


From robert@raszuk.net  Tue Jul 10 15:03:05 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 1208211E80CA for <grow@ietfa.amsl.com>; Tue, 10 Jul 2012 15:03:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.374
X-Spam-Level: 
X-Spam-Status: No, score=-1.374 tagged_above=-999 required=5 tests=[AWL=-1.075, BAYES_00=-2.599, MANGLED_PAIN=2.3]
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 OI1v9wV7WFSv for <grow@ietfa.amsl.com>; Tue, 10 Jul 2012 15:03:04 -0700 (PDT)
Received: from mail1310.opentransfer.com (mail1310.opentransfer.com [76.162.254.103]) by ietfa.amsl.com (Postfix) with ESMTP id 3BDDD21F8491 for <grow@ietf.org>; Tue, 10 Jul 2012 15:03:04 -0700 (PDT)
Received: (qmail 18978 invoked by uid 399); 10 Jul 2012 22:03:31 -0000
Received: from unknown (HELO ?192.168.1.58?) (pbs:robert@raszuk.net@83.9.118.178) by mail1310.opentransfer.com with ESMTPM; 10 Jul 2012 22:03:31 -0000
X-Originating-IP: 83.9.118.178
Message-ID: <4FFCA6B2.3060404@raszuk.net>
Date: Wed, 11 Jul 2012 00:03:30 +0200
From: Robert Raszuk <robert@raszuk.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: "White, Russell" <riwhite@verisign.com>
References: <CAL9jLabOs02rOti4tezaZiHyiOD2f9vAhsoE9c-afFb4J1xYXQ@mail.gmail.com> <DCC302FAA9FE5F4BBA4DCAD46569377917449AF235@PRVPEXVS03.corp.twcable.com> <F8659490-D1B2-477D-ADCC-EC6FD7AD073A@rob.sh>, <4FFAD681.70607@raszuk.net> <3F74C1962631E14292BBF1B1B5F7021E043516@BRN1WNEXMBX01.vcorp.ad.vrsn.com>, <4FFBECCE.6050000@raszuk.net> <3F74C1962631E14292BBF1B1B5F7021E043924@BRN1WNEXMBX01.vcorp.ad.vrsn.com>, <4FFC4378.7090505@raszuk.net> <3F74C1962631E14292BBF1B1B5F7021E043E94@BRN1WNEXMBX01.vcorp.ad.vrsn.com>
In-Reply-To: <3F74C1962631E14292BBF1B1B5F7021E043E94@BRN1WNEXMBX01.vcorp.ad.vrsn.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "grow@ietf.org" <grow@ietf.org>, Susan Hares <skh@ndzh.com>
Subject: Re: [GROW] draft-white-grow-overlapping-routes-00
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, 10 Jul 2012 22:03:05 -0000

/* subject fixed */

Hi Russ,

> We could compare the less specific with the more specific, as you
> say. But it's important that the comparison be done on the inbound
> side, not the outbound side, if you want the option of reducing
> internal table size.

Ok here I completely disagree. Let me try to explain why ...

The tools to solve RIB and FIB scaling do not require to prevent BGP 
from limiting it's table size.

The tools which may help with Internet BGP table grow are much more 
efficient outbound from any AS not inbound. The reason is that there are 
many inbound points which may receive overlapping prefixes.

> I don't think we say it has to come in on the same session, or even
> from the same entry point --only that the overlapping routes have to
> exist in the same table at some point for comparison. You could
> always do this at the outbound ASBR, but that's not the most
> efficient place to do it. The most efficient place is the inbound
> ASBR, I think.

As above I think we clearly disagree on that point ;)

> You said PI space first,

Sorry yes I meant PA in the first place as well.

> not PA... With PA, if a provider is stupid
> enough to give the inbound traffic to one of their customers to a
> competing provider, then go ahead.

It will not ! Because wise provider do not suppress anything on inbound 
within his network he carries his more specific prefixes just fine. It 
is just outbound to his upstream he advertises his single PA space. 4

> I can't imagine doing that as a
> provider. If I'm providing the PA space, I want to be the primary
> entry point into the customer's network.

And you still are .. of course provided that customer will not convince 
some other ISP with sufficient $$$ to advertise part of your PA space.

That's why RIRs were recognizing this as an important enough issue that 
such multimedia customer were getting Provider Independent address. Of 
course if we finally converge on how to do multihoming with PA addresses 
it would be much better.

> Why bother with "prefer local routes to my customers over routes from
> peers," if I'm going to give out a set of longer prefixes that
> customer can advertise through another provider, drawing traffic from
> within my own network across a transit link into a peer to reach that
> same customer?
>
> But note:
>
>> "Advertisement of more specific prefixes should not be used unless
>> absolutely necessary and, where sensible, a covering aggregate
>> should also be advertised.
>
> A covering aggregate should also be advertised. In other words, if
> you're advertising the longer prefix, you _should_ advertise a
> shorter covering route --specifically what we're counting on in this
> draft. So it looks like the draft is already in line with what best
> common practice is. :-)

You looked at the exception not the rule :)

r.



From robert@raszuk.net  Tue Jul 10 16:12:40 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 D30B311E80BF for <grow@ietfa.amsl.com>; Tue, 10 Jul 2012 16:12:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.405
X-Spam-Level: 
X-Spam-Status: No, score=-2.405 tagged_above=-999 required=5 tests=[AWL=0.194,  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 VfAEoBUDJBVc for <grow@ietfa.amsl.com>; Tue, 10 Jul 2012 16:12:40 -0700 (PDT)
Received: from mail1310.opentransfer.com (mail1310.opentransfer.com [76.162.254.103]) by ietfa.amsl.com (Postfix) with ESMTP id D001B11E809F for <grow@ietf.org>; Tue, 10 Jul 2012 16:12:39 -0700 (PDT)
Received: (qmail 7949 invoked by uid 399); 10 Jul 2012 23:13:08 -0000
Received: from unknown (HELO ?192.168.1.58?) (pbs:robert@raszuk.net@83.9.118.178) by mail1310.opentransfer.com with ESMTPM; 10 Jul 2012 23:13:08 -0000
X-Originating-IP: 83.9.118.178
Message-ID: <4FFCB702.8000202@raszuk.net>
Date: Wed, 11 Jul 2012 01:13:06 +0200
From: Robert Raszuk <robert@raszuk.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: "White, Russell" <riwhite@verisign.com>
References: <CAL9jLabOs02rOti4tezaZiHyiOD2f9vAhsoE9c-afFb4J1xYXQ@mail.gmail.com> <DCC302FAA9FE5F4BBA4DCAD46569377917449AF235@PRVPEXVS03.corp.twcable.com> <F8659490-D1B2-477D-ADCC-EC6FD7AD073A@rob.sh>, <4FFAD681.70607@raszuk.net> <3F74C1962631E14292BBF1B1B5F7021E043516@BRN1WNEXMBX01.vcorp.ad.vrsn.com>, <4FFBECCE.6050000@raszuk.net> <3F74C1962631E14292BBF1B1B5F7021E043924@BRN1WNEXMBX01.vcorp.ad.vrsn.com>, <4FFC4378.7090505@raszuk.net> <3F74C1962631E14292BBF1B1B5F7021E043E94@BRN1WNEXMBX01.vcorp.ad.vrsn.com>, <4FFCA6B2.3060404@raszuk.net> <3F74C1962631E14292BBF1B1B5F7021E043F33@BRN1WNEXMBX01.vcorp.ad.vrsn.com>
In-Reply-To: <3F74C1962631E14292BBF1B1B5F7021E043F33@BRN1WNEXMBX01.vcorp.ad.vrsn.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "grow@ietf.org" <grow@ietf.org>, Susan Hares <skh@ndzh.com>
Subject: Re: [GROW] draft-white-grow-overlapping-routes-00
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, 10 Jul 2012 23:12:41 -0000

Hi Russ,

> 1. A provider who is giving a customer PA space in parts, but that PA
> space is not being advertised anyplace other than to that provider.
> In this case, pulling traffic overlapping routes doesn't matter,
> because the provider who allows the use of PA space is going to take
> them out by not advertising the longer prefixes from their own space.
> In this case, the draft we've proposed would work, as well.

This is done today without the need for your draft. That's common 
practice :)

> 2. A provider who is giving a customer PA space and allowing the
> customer to advertise that same PA space through another provider. In
> this case, if the provider is not advertising the PA space at the
> same length as the customer is to an alternate provider, the
> alternate provider will consume all the inbound traffic to the
> customer. This is dumb on the part of the provider giving out the PA
> space.

What is the provider supposed to do ? Give ticket to his customer ? Get 
rid of his customer ?

See the PA owner can not do much not to break the business relation with 
his customer. However his (and another providers) upstreams can suppress 
the more specifics.

This is where the aim should be. Moreover the more specific should be 
suppressed only where it brings no more value.

> 3. A customer who has PI space and is advertising different bits in
> different places. Again, best practice would say to advertise a
> shorter covering route as well, to guard against failures. If the end
> AS is advertising longer and shorter prefixes that overlap, the draft
> we've proposed works --even if they're advertising them in different
> places, what we've proposed will take the longer prefix out once it
> no longer draws traffic along a different path than the shorter
> prefix.

I don't think we can do much with PI addresses.

> So, I'm a bit confused as to what case you think isn't covered... I
> thought you were saying it was normal operation for a provider to
> give out PA space, allow the customer to break that space up, and

I don not understand what do you mean by "allow" If I peer with you and 
you give me /24 out of your /16 then I pay Alvaro $$$ then he will be 
happy to advertise this /24. What can you do about that ? Be mad at both 
of us ?

> then only advertise the shorter block covering the space given to the
> customer. I don't care how you jiggle local pref if you do this,
> longer prefix wins, and the alternate provider consumes the traffic
> --even from your AS.

Nope. Not from your AS as as I said in the last email you will carry 
within your AS my /24 and prefer customer routes rather then peer routes 
(assuming Alvaro is even peering with you)

;-)
R.

From riwhite@verisign.com  Mon Jul  9 16:57:04 2012
Return-Path: <riwhite@verisign.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 AA23F21F8601 for <grow@ietfa.amsl.com>; Mon,  9 Jul 2012 16:57:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.372
X-Spam-Level: 
X-Spam-Status: No, score=-6.372 tagged_above=-999 required=5 tests=[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 8ePtq3lu4MBI for <grow@ietfa.amsl.com>; Mon,  9 Jul 2012 16:57:04 -0700 (PDT)
Received: from exprod6og102.obsmtp.com (exprod6og102.obsmtp.com [64.18.1.183]) by ietfa.amsl.com (Postfix) with ESMTP id B2FA121F8600 for <grow@ietf.org>; Mon,  9 Jul 2012 16:56:57 -0700 (PDT)
Received: from peregrine.verisign.com ([216.168.239.74]) (using TLSv1) by exprod6ob102.postini.com ([64.18.5.12]) with SMTP ID DSNKT/tv41mFxAo+ymZ3aPdXvbhA2AAX3nmC@postini.com; Mon, 09 Jul 2012 16:57:29 PDT
Received: from BRN1WNEXCHM01.vcorp.ad.vrsn.com (brn1wnexchm01.vcorp.ad.vrsn.com [10.173.152.255]) by peregrine.verisign.com (8.13.6/8.13.4) with ESMTP id q69NvKJp014268 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 9 Jul 2012 19:57:20 -0400
Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by BRN1WNEXCHM01.vcorp.ad.vrsn.com ([::1]) with mapi id 14.02.0247.003; Mon, 9 Jul 2012 19:57:19 -0400
From: "White, Russell" <riwhite@verisign.com>
To: "robert@raszuk.net" <robert@raszuk.net>, "Retana, Alvaro" <alvaro.retana@hp.com>, Susan Hares <skh@ndzh.com>
Thread-Topic: [GROW] WGLC: draft-ietf-grow-ops-reqs-for-bgp-error-handling-04
Thread-Index: AQHNXdMrB3AkwzWng0OCcKtRz3IQIpchoCFz
Date: Mon, 9 Jul 2012 23:57:19 +0000
Message-ID: <3F74C1962631E14292BBF1B1B5F7021E043516@BRN1WNEXMBX01.vcorp.ad.vrsn.com>
References: <CAL9jLabOs02rOti4tezaZiHyiOD2f9vAhsoE9c-afFb4J1xYXQ@mail.gmail.com> <DCC302FAA9FE5F4BBA4DCAD46569377917449AF235@PRVPEXVS03.corp.twcable.com> <F8659490-D1B2-477D-ADCC-EC6FD7AD073A@rob.sh>, <4FFAD681.70607@raszuk.net>
In-Reply-To: <4FFAD681.70607@raszuk.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.173.152.4]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Wed, 11 Jul 2012 08:43:07 -0700
Cc: "grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] WGLC: draft-ietf-grow-ops-reqs-for-bgp-error-handling-04
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, 09 Jul 2012 23:58:00 -0000

=3D=3D=0A=
                     (   )=0A=
            /-------( AS2 )--------\=0A=
     (   ) /         (   )          \ (   )       (   )=0A=
    ( AS1 )                          ( AS4 )-----( AS5 )=0A=
     (   ) \         (   )          / (   )       (   )=0A=
            \-------( AS3 )--------/=0A=
                     (   )=0A=
=0A=
    o  AS1 is advertising 192.0.2.128/25 to both AS2 and AS3.=0A=
=0A=
    o  AS2 is advertising both 192.0.2.128/25 and 192.0.2.0/24 into AS4.=0A=
=0A=
    o  AS3 is advertising 192.0.2.128/25 into AS4=0A=
=0A=
I am afraid you are too optimistic :)=0A=
=3D=3D=0A=
=0A=
Actually, this is really simple to fix in one of two ways.=0A=
=0A=
First, AS4 could see the overlap on the outbound side, note the origin AS i=
s the same, and set the longer prefix to NO_EXPORT.=0A=
=0A=
Alternatively, the BGP implementation in AS4 could be modified so that when=
 running bestpath if a losing route has a specific community, it is transfe=
rred to the winning route. This would allow the winning route to gain the B=
OUNDED community in processing.=0A=
=0A=
=3D=3D=0A=
The most common scenario I see is that AS2 only advertises to AS4 the=0A=
aggregate so 192.0.2.0/24. That means that your 192.0.2.128/25 would=0A=
never get "BOUNDED" status hence the other path via AS3 will continue=0A=
worldwide via AS4.=0A=
=3D=3D=0A=
=0A=
I rarely see this --because most of the time, folks want to "cover" the lon=
ger match with a shorter one, in case the longer prefix fails for some reas=
on. With a covering route, both ISPs will be used for inbound traffic, and =
not just the one with the remaining longer prefix. This has been the recomm=
ended configuration for years, AFAIK.=0A=
=0A=
=3D=3D=0A=
Contrary as you very well know the alternative proposal=0A=
http://tools.ietf.org/id/draft-marques-idr-aggregate-00.txt seems to=0A=
address the above case as well as all cases you are trying to cover.=0A=
Could you comment and compare both solutions especially as a (co-)author=0A=
of both ;).=0A=
=3D=3D=0A=
=0A=
I prefer the simpler solution presented in the draft we just published. Dra=
ft-marquis and the virtual aggregation drafts both add a lot of complexity =
to operations, while the BOUNDED community is very simple, and can (mostly)=
 be implemented today with no changes to BGP, no changes to current traffic=
 engineering, and no increased stretch within the SP network. Complexity ca=
n always be added, but a simple system on which future modifications can be=
 made to cover corner cases seems like a better idea to me... :-)=0A=
=0A=
:-)=0A=
=0A=
Russ=0A=
=0A=

From riwhite@verisign.com  Tue Jul 10 07:24:02 2012
Return-Path: <riwhite@verisign.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 D9E3D21F868A for <grow@ietfa.amsl.com>; Tue, 10 Jul 2012 07:24:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.429
X-Spam-Level: 
X-Spam-Status: No, score=-6.429 tagged_above=-999 required=5 tests=[AWL=-0.057, 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 mZ29NjCpEJYh for <grow@ietfa.amsl.com>; Tue, 10 Jul 2012 07:24:02 -0700 (PDT)
Received: from exprod6og112.obsmtp.com (exprod6og112.obsmtp.com [64.18.1.29]) by ietfa.amsl.com (Postfix) with ESMTP id D7FF221F8688 for <grow@ietf.org>; Tue, 10 Jul 2012 07:23:59 -0700 (PDT)
Received: from osprey.verisign.com ([216.168.239.75]) (using TLSv1) by exprod6ob112.postini.com ([64.18.5.12]) with SMTP ID DSNKT/w7G9QBVvaRKKRobVLAODSpDGUXLu/a@postini.com; Tue, 10 Jul 2012 07:24:30 PDT
Received: from brn1wnexcas01.vcorp.ad.vrsn.com (brn1wnexcas01.vcorp.ad.vrsn.com [10.173.152.205]) by osprey.verisign.com (8.13.6/8.13.4) with ESMTP id q6AEONqf023070 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 10 Jul 2012 10:24:23 -0400
Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by brn1wnexcas01.vcorp.ad.vrsn.com ([::1]) with mapi id 14.02.0247.003; Tue, 10 Jul 2012 10:24:23 -0400
From: "White, Russell" <riwhite@verisign.com>
To: "robert@raszuk.net" <robert@raszuk.net>
Thread-Topic: [GROW] WGLC: draft-ietf-grow-ops-reqs-for-bgp-error-handling-04
Thread-Index: AQHNXdMrB3AkwzWng0OCcKtRz3IQIpchoCFzgADZWwCAABeyIw==
Date: Tue, 10 Jul 2012 14:24:23 +0000
Message-ID: <3F74C1962631E14292BBF1B1B5F7021E043924@BRN1WNEXMBX01.vcorp.ad.vrsn.com>
References: <CAL9jLabOs02rOti4tezaZiHyiOD2f9vAhsoE9c-afFb4J1xYXQ@mail.gmail.com> <DCC302FAA9FE5F4BBA4DCAD46569377917449AF235@PRVPEXVS03.corp.twcable.com> <F8659490-D1B2-477D-ADCC-EC6FD7AD073A@rob.sh>, <4FFAD681.70607@raszuk.net> <3F74C1962631E14292BBF1B1B5F7021E043516@BRN1WNEXMBX01.vcorp.ad.vrsn.com>, <4FFBECCE.6050000@raszuk.net>
In-Reply-To: <4FFBECCE.6050000@raszuk.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.173.152.4]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Wed, 11 Jul 2012 08:43:08 -0700
Cc: "grow@ietf.org" <grow@ietf.org>, Susan Hares <skh@ndzh.com>
Subject: Re: [GROW] WGLC: draft-ietf-grow-ops-reqs-for-bgp-error-handling-04
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, 10 Jul 2012 14:24:03 -0000

=0A=
=0A=
>> o  AS1 is advertising 192.0.2.128/25 to both AS2 and AS3.=0A=
>> o  AS2 is advertising both 192.0.2.128/25 and 192.0.2.0/24 into AS4.=0A=
>> o  AS3 is advertising 192.0.2.128/25 into AS4=0A=
>>=0A=
>> I am afraid you are too optimistic :) =0A=
>>=0A=
>> Actually, this is really simple to fix in one of two ways.=0A=
>>=0A=
>> First, AS4 could see the overlap on the outbound side, note the=0A=
>> origin AS is the same, and set the longer prefix to NO_EXPORT.=0A=
> =0A=
> I don't think this is as simple as this ... Remember that when the less=
=0A=
> specific (/24) goes away the AS4 must readvertise the more specifics not=
=0A=
> to break routing. So therefor I do not think that any simple policy=0A=
> would work. The choice/decision what to advertise and what not must be=0A=
> done at best path run.=0A=
=0A=
Sure --but won't best path be run when the best path towards a specific des=
tination falls out of the table?=0A=
=0A=
>> Alternatively, the BGP implementation in AS4 could be modified so=0A=
>> that when running bestpath if a losing route has a specific=0A=
>> community, it is transferred to the winning route. This would allow=0A=
>> the winning route to gain the BOUNDED community in processing.=0A=
> =0A=
> Actually I am not that clear I understand this business reg communities=
=0A=
> marking. How about we consider even much simpler and ASBR local solution:=
=0A=
=0A=
A local ASBR only solution won't work for various reasons, so let's not. :-=
)=0A=
=0A=
> If this is PI address given to a customer I actually do not know any ISP=
=0A=
> who would advertise his smaller blocks in addition to his aggregate=0A=
> those blocks are taken from. Only for backdoor/multihoming the smaller=0A=
> blocks get advertised via some other ISPs, but never directly connected.=
=0A=
=0A=
So what you are saying is that if a provider owns 10.1.0.0/16, and gives ou=
t 10.1.1.0/24 to a customer to advertise through some other provider the cu=
stomer is connected to, the provider would never advertise 10.1.1.0/24 as w=
ell as 10.1.0.0/16? Why not? Since the longest match always wins, what you'=
re saying is that the provider that handed out the address space would end =
up routing through the competing provider (the customer's other provider) t=
o reach the customer, because there is a longer match being advertised by t=
he customer through the competing provider.=0A=
=0A=
That doesn't make any sense to me.=0A=
=0A=
> Just to be very clear .. VA (any of the VA drafts) does not talk about=0A=
> the same problem. For one it does not stop BGP from advertising anything=
=0A=
> and second it is intra-domain solution.=0A=
=0A=
Right --the VA drafts increase stretch and don't reduce the total table siz=
e for anyone. In return, you must inject a good bit of complexity, and cons=
ider the various problems involved with routing traffic on a smaller number=
 of links through your network. =0A=
=0A=
I prefer the simpler solution. And yes, it is simpler, even if it doesn't s=
olve (outright) every possible problem in the space.=0A=
=0A=
:-)=0A=
=0A=
Russ=0A=
=0A=

From riwhite@verisign.com  Tue Jul 10 14:44:15 2012
Return-Path: <riwhite@verisign.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 CDAC311E80E6 for <grow@ietfa.amsl.com>; Tue, 10 Jul 2012 14:44:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.41
X-Spam-Level: 
X-Spam-Status: No, score=-6.41 tagged_above=-999 required=5 tests=[AWL=-0.038,  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 KUKzLNnE6YdD for <grow@ietfa.amsl.com>; Tue, 10 Jul 2012 14:44:15 -0700 (PDT)
Received: from exprod6og117.obsmtp.com (exprod6og117.obsmtp.com [64.18.1.39]) by ietfa.amsl.com (Postfix) with ESMTP id 6497C11E80C4 for <grow@ietf.org>; Tue, 10 Jul 2012 14:44:12 -0700 (PDT)
Received: from osprey.verisign.com ([216.168.239.75]) (using TLSv1) by exprod6ob117.postini.com ([64.18.5.12]) with SMTP ID DSNKT/yiSOE43b5lnW7nNffqj0vP/b659FWx@postini.com; Tue, 10 Jul 2012 14:44:43 PDT
Received: from brn1wnexcas01.vcorp.ad.vrsn.com (brn1wnexcas01.vcorp.ad.vrsn.com [10.173.152.205]) by osprey.verisign.com (8.13.6/8.13.4) with ESMTP id q6ALiagO012057 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 10 Jul 2012 17:44:36 -0400
Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by brn1wnexcas01.vcorp.ad.vrsn.com ([::1]) with mapi id 14.02.0247.003; Tue, 10 Jul 2012 17:44:35 -0400
From: "White, Russell" <riwhite@verisign.com>
To: "robert@raszuk.net" <robert@raszuk.net>
Thread-Topic: [GROW] WGLC: draft-ietf-grow-ops-reqs-for-bgp-error-handling-04
Thread-Index: AQHNXdMrB3AkwzWng0OCcKtRz3IQIpchoCFzgADZWwCAABeyI4AAT54AgAAsP5M=
Date: Tue, 10 Jul 2012 21:44:35 +0000
Message-ID: <3F74C1962631E14292BBF1B1B5F7021E043E94@BRN1WNEXMBX01.vcorp.ad.vrsn.com>
References: <CAL9jLabOs02rOti4tezaZiHyiOD2f9vAhsoE9c-afFb4J1xYXQ@mail.gmail.com> <DCC302FAA9FE5F4BBA4DCAD46569377917449AF235@PRVPEXVS03.corp.twcable.com> <F8659490-D1B2-477D-ADCC-EC6FD7AD073A@rob.sh>, <4FFAD681.70607@raszuk.net> <3F74C1962631E14292BBF1B1B5F7021E043516@BRN1WNEXMBX01.vcorp.ad.vrsn.com>, <4FFBECCE.6050000@raszuk.net> <3F74C1962631E14292BBF1B1B5F7021E043924@BRN1WNEXMBX01.vcorp.ad.vrsn.com>, <4FFC4378.7090505@raszuk.net>
In-Reply-To: <4FFC4378.7090505@raszuk.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.173.152.4]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Wed, 11 Jul 2012 08:43:08 -0700
Cc: "grow@ietf.org" <grow@ietf.org>, Susan Hares <skh@ndzh.com>
Subject: Re: [GROW] WGLC: draft-ietf-grow-ops-reqs-for-bgp-error-handling-04
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, 10 Jul 2012 21:44:16 -0000

=0A=
>>> I don't think this is as simple as this ... Remember that when the=0A=
>>> less specific (/24) goes away the AS4 must readvertise the more=0A=
>>> specifics not to break routing. So therefor I do not think that any=0A=
>>> simple policy would work. The choice/decision what to advertise and=0A=
>>> what not must be done at best path run.=0A=
>>=0A=
>> Sure --but won't best path be run when the best path towards a=0A=
>> specific destination falls out of the table?=0A=
> =0A=
> Best path today does not compare /16 and /24. In Pedro's proposal it does=
.=0A=
=0A=
We could compare the less specific with the more specific, as you say. But =
it's important that the comparison be done on the inbound side, not the out=
bound side, if you want the option of reducing internal table size.=0A=
=0A=
> I think it works. The example is comparing all best path eligible=0A=
> attributes of less and more specific during best path and if the less=0A=
> specific would win suppress the more specific.=0A=
> =0A=
> I am only not sure if we really need to compare all. For example I am=0A=
> not sure that like in your proposal it really matters if the more=0A=
> specific was received over the same session as less specific (provided=0A=
> that actually happens that often as you say :-)=0A=
=0A=
I don't think we say it has to come in on the same session, or even from th=
e same entry point --only that the overlapping routes have to exist in the =
same table at some point for comparison. You could always do this at the ou=
tbound ASBR, but that's not the most efficient place to do it. The most eff=
icient place is the inbound ASBR, I think.=0A=
=0A=
> That has been for years common recommendation of any RIR ... That's the=
=0A=
> value of PA addresses. Multihomers were told to get PI which indeed does=
=0A=
> not make the BGP table smaller.=0A=
=0A=
You said PI space first, not PA... With PA, if a provider is stupid enough =
to give the inbound traffic to one of their customers to a competing provid=
er, then go ahead. I can't imagine doing that as a provider. If I'm providi=
ng the PA space, I want to be the primary entry point into the customer's n=
etwork.=0A=
=0A=
Why bother with "prefer local routes to my customers over routes from peers=
," if I'm going to give out a set of longer prefixes that customer can adve=
rtise through another provider, drawing traffic from within my own network =
across a transit link into a peer to reach that same customer? =0A=
=0A=
But note:=0A=
=0A=
> "Advertisement of more specific prefixes should not be used unless=0A=
> absolutely necessary and, where sensible, a covering aggregate=0A=
> should also be advertised.=0A=
=0A=
A covering aggregate should also be advertised. In other words, if you're a=
dvertising the longer prefix, you _should_ advertise a shorter covering rou=
te --specifically what we're counting on in this draft. So it looks like th=
e draft is already in line with what best common practice is. :-)=0A=
=0A=
> It never intended to. It reduces the local RIB/FIB size. I am not even=0A=
> sure why you are comparing apple to oranges here :)=0A=
=0A=
I didn't bring it up. :-)=0A=
=0A=
:-)=0A=
=0A=
Russ=0A=

From riwhite@verisign.com  Tue Jul 10 15:54:11 2012
Return-Path: <riwhite@verisign.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 0910611E80E6 for <grow@ietfa.amsl.com>; Tue, 10 Jul 2012 15:54:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.514
X-Spam-Level: 
X-Spam-Status: No, score=-6.514 tagged_above=-999 required=5 tests=[AWL=0.085,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 lu5gWNuatMAx for <grow@ietfa.amsl.com>; Tue, 10 Jul 2012 15:54:10 -0700 (PDT)
Received: from exprod6og101.obsmtp.com (exprod6og101.obsmtp.com [64.18.1.181]) by ietfa.amsl.com (Postfix) with ESMTP id 226D611E809F for <grow@ietf.org>; Tue, 10 Jul 2012 15:54:08 -0700 (PDT)
Received: from peregrine.verisign.com ([216.168.239.74]) (using TLSv1) by exprod6ob101.postini.com ([64.18.5.12]) with SMTP ID DSNKT/yyrB1u9c0n2PDcm9Ocw3/5y13iUS1+@postini.com; Tue, 10 Jul 2012 15:54:39 PDT
Received: from brn1wnexcas01.vcorp.ad.vrsn.com (brn1wnexcas01.vcorp.ad.vrsn.com [10.173.152.205]) by peregrine.verisign.com (8.13.6/8.13.4) with ESMTP id q6AMsZpd017893 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 10 Jul 2012 18:54:35 -0400
Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by brn1wnexcas01.vcorp.ad.vrsn.com ([::1]) with mapi id 14.02.0247.003; Tue, 10 Jul 2012 18:54:35 -0400
From: "White, Russell" <riwhite@verisign.com>
To: "robert@raszuk.net" <robert@raszuk.net>
Thread-Topic: [GROW] draft-white-grow-overlapping-routes-00
Thread-Index: AQHNXufZIhLiWShsFEaoV8oecTo8K5cjHohz
Date: Tue, 10 Jul 2012 22:54:34 +0000
Message-ID: <3F74C1962631E14292BBF1B1B5F7021E043F33@BRN1WNEXMBX01.vcorp.ad.vrsn.com>
References: <CAL9jLabOs02rOti4tezaZiHyiOD2f9vAhsoE9c-afFb4J1xYXQ@mail.gmail.com> <DCC302FAA9FE5F4BBA4DCAD46569377917449AF235@PRVPEXVS03.corp.twcable.com> <F8659490-D1B2-477D-ADCC-EC6FD7AD073A@rob.sh>, <4FFAD681.70607@raszuk.net> <3F74C1962631E14292BBF1B1B5F7021E043516@BRN1WNEXMBX01.vcorp.ad.vrsn.com>, <4FFBECCE.6050000@raszuk.net> <3F74C1962631E14292BBF1B1B5F7021E043924@BRN1WNEXMBX01.vcorp.ad.vrsn.com>, <4FFC4378.7090505@raszuk.net> <3F74C1962631E14292BBF1B1B5F7021E043E94@BRN1WNEXMBX01.vcorp.ad.vrsn.com>, <4FFCA6B2.3060404@raszuk.net>
In-Reply-To: <4FFCA6B2.3060404@raszuk.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.173.152.4]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Wed, 11 Jul 2012 08:43:08 -0700
Cc: "grow@ietf.org" <grow@ietf.org>, Susan Hares <skh@ndzh.com>
Subject: Re: [GROW] draft-white-grow-overlapping-routes-00
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, 10 Jul 2012 22:54:11 -0000

=0A=
>> not PA... With PA, if a provider is stupid=0A=
>> enough to give the inbound traffic to one of their customers to a=0A=
>> competing provider, then go ahead.=0A=
> =0A=
> It will not ! Because wise provider do not suppress anything on inbound=
=0A=
> within his network he carries his more specific prefixes just fine. It=0A=
> is just outbound to his upstream he advertises his single PA space. 4=0A=
> =0A=
>> I can't imagine doing that as a=0A=
>> provider. If I'm providing the PA space, I want to be the primary=0A=
>> entry point into the customer's network.=0A=
> =0A=
> And you still are .. of course provided that customer will not convince=
=0A=
> some other ISP with sufficient $$$ to advertise part of your PA space.=0A=
=0A=
Okay, there are three cases I can see:=0A=
=0A=
1. A provider who is giving a customer PA space in parts, but that PA space=
 is not being advertised anyplace other than to that provider. In this case=
, pulling traffic overlapping routes doesn't matter, because the provider w=
ho allows the use of PA space is going to take them out by not advertising =
the longer prefixes from their own space. In this case, the draft we've pro=
posed would work, as well.=0A=
=0A=
2. A provider who is giving a customer PA space and allowing the customer t=
o advertise that same PA space through another provider. In this case, if t=
he provider is not advertising the PA space at the same length as the custo=
mer is to an alternate provider, the alternate provider will consume all th=
e inbound traffic to the customer. This is dumb on the part of the provider=
 giving out the PA space.=0A=
=0A=
3. A customer who has PI space and is advertising different bits in differe=
nt places. Again, best practice would say to advertise a shorter covering r=
oute as well, to guard against failures. If the end AS is advertising longe=
r and shorter prefixes that overlap, the draft we've proposed works --even =
if they're advertising them in different places, what we've proposed will t=
ake the longer prefix out once it no longer draws traffic along a different=
 path than the shorter prefix.=0A=
=0A=
So, I'm a bit confused as to what case you think isn't covered... I thought=
 you were saying it was normal operation for a provider to give out PA spac=
e, allow the customer to break that space up, and then only advertise the s=
horter block covering the space given to the customer. I don't care how you=
 jiggle local pref if you do this, longer prefix wins, and the alternate pr=
ovider consumes the traffic --even from your AS.=0A=
=0A=
:-)=0A=
=0A=
Russ=

From riwhite@verisign.com  Tue Jul 10 17:06:41 2012
Return-Path: <riwhite@verisign.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 380C011E814A for <grow@ietfa.amsl.com>; Tue, 10 Jul 2012 17:06:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.531
X-Spam-Level: 
X-Spam-Status: No, score=-6.531 tagged_above=-999 required=5 tests=[AWL=0.068,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 4lxi3Mymlbfd for <grow@ietfa.amsl.com>; Tue, 10 Jul 2012 17:06:40 -0700 (PDT)
Received: from exprod6og104.obsmtp.com (exprod6og104.obsmtp.com [64.18.1.187]) by ietfa.amsl.com (Postfix) with ESMTP id A353A11E8087 for <grow@ietf.org>; Tue, 10 Jul 2012 17:06:37 -0700 (PDT)
Received: from peregrine.verisign.com ([216.168.239.74]) (using TLSv1) by exprod6ob104.postini.com ([64.18.5.12]) with SMTP ID DSNKT/zDqg3k1cA721w1hJH0GGRyQFfrTQxI@postini.com; Tue, 10 Jul 2012 17:07:09 PDT
Received: from BRN1WNEXCHM01.vcorp.ad.vrsn.com (brn1wnexchm01.vcorp.ad.vrsn.com [10.173.152.255]) by peregrine.verisign.com (8.13.6/8.13.4) with ESMTP id q6B073Ei021155 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 10 Jul 2012 20:07:03 -0400
Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by BRN1WNEXCHM01.vcorp.ad.vrsn.com ([::1]) with mapi id 14.02.0247.003; Tue, 10 Jul 2012 20:07:02 -0400
From: "White, Russell" <riwhite@verisign.com>
To: "robert@raszuk.net" <robert@raszuk.net>
Thread-Topic: [GROW] draft-white-grow-overlapping-routes-00
Thread-Index: AQHNXufZIhLiWShsFEaoV8oecTo8K5cjHohzgABJ1gD//8sS8w==
Date: Wed, 11 Jul 2012 00:07:01 +0000
Message-ID: <3F74C1962631E14292BBF1B1B5F7021E043FCA@BRN1WNEXMBX01.vcorp.ad.vrsn.com>
References: <CAL9jLabOs02rOti4tezaZiHyiOD2f9vAhsoE9c-afFb4J1xYXQ@mail.gmail.com> <DCC302FAA9FE5F4BBA4DCAD46569377917449AF235@PRVPEXVS03.corp.twcable.com> <F8659490-D1B2-477D-ADCC-EC6FD7AD073A@rob.sh>, <4FFAD681.70607@raszuk.net> <3F74C1962631E14292BBF1B1B5F7021E043516@BRN1WNEXMBX01.vcorp.ad.vrsn.com>, <4FFBECCE.6050000@raszuk.net> <3F74C1962631E14292BBF1B1B5F7021E043924@BRN1WNEXMBX01.vcorp.ad.vrsn.com>, <4FFC4378.7090505@raszuk.net> <3F74C1962631E14292BBF1B1B5F7021E043E94@BRN1WNEXMBX01.vcorp.ad.vrsn.com>, <4FFCA6B2.3060404@raszuk.net> <3F74C1962631E14292BBF1B1B5F7021E043F33@BRN1WNEXMBX01.vcorp.ad.vrsn.com>, <4FFCB702.8000202@raszuk.net>
In-Reply-To: <4FFCB702.8000202@raszuk.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.173.152.4]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Wed, 11 Jul 2012 08:43:08 -0700
Cc: "grow@ietf.org" <grow@ietf.org>, Susan Hares <skh@ndzh.com>
Subject: Re: [GROW] draft-white-grow-overlapping-routes-00
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, 11 Jul 2012 00:06:41 -0000

=0A=
>> 2. A provider who is giving a customer PA space and allowing the=0A=
>> customer to advertise that same PA space through another provider. In=0A=
>> this case, if the provider is not advertising the PA space at the=0A=
>> same length as the customer is to an alternate provider, the=0A=
>> alternate provider will consume all the inbound traffic to the=0A=
>> customer. This is dumb on the part of the provider giving out the PA=0A=
>> space.=0A=
> =0A=
> What is the provider supposed to do ? Give ticket to his customer ? Get=
=0A=
> rid of his customer ?=0A=
=0A=
Advertise the same length route as the other provider is... That's what I w=
ould do.=0A=
=0A=
However, if we're blocking the longer prefix route when it no longer impact=
s traffic flow, then the alternate provider will block the longer prefix wh=
en he receives the shorter from the owner of the PA space.=0A=
=0A=
Again, this is all about blocking longer prefixes when they are no longer u=
seful in the routing system as a whole. What we've proposed says that seein=
g two overlapping routes is the best indication of this condition, and atte=
mpts to strike a balance between traffic engineering and reducing table siz=
e.=0A=
=0A=
> I don't think we can do much with PI addresses.=0A=
=0A=
You can remove unneeded longer prefix traffic engineering routes with PI sp=
ace just like you can PA space.=0A=
=0A=
:-)=0A=
=0A=
Russ=

From shane@castlepoint.net  Wed Jul 11 09:51:10 2012
Return-Path: <shane@castlepoint.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 3FA4311E8106 for <grow@ietfa.amsl.com>; Wed, 11 Jul 2012 09:51:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.572
X-Spam-Level: *
X-Spam-Status: No, score=1.572 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FB_INCREASE_VOL=3.629, SARE_MILLIONSOF=0.315, 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 BZjWJ78GKHlc for <grow@ietfa.amsl.com>; Wed, 11 Jul 2012 09:51:08 -0700 (PDT)
Received: from dog.tcb.net (dog.tcb.net [64.78.150.133]) by ietfa.amsl.com (Postfix) with ESMTP id 94CAF11E810B for <grow@ietf.org>; Wed, 11 Jul 2012 09:51:08 -0700 (PDT)
Received: by dog.tcb.net (Postfix, from userid 0) id 562A7368199; Wed, 11 Jul 2012 10:51:39 -0600 (MDT)
Received: from [10.1.68.94] (machine77.Level3.com [209.244.4.106]) (authenticated-user smtp) (TLSv1/SSLv3 AES128-SHA 128/128) by dog.tcb.net with SMTP; Wed, 11 Jul 2012 10:51:39 -0600 (MDT) (envelope-from shane@castlepoint.net)
X-Avenger: version=0.7.8; receiver=dog.tcb.net; client-ip=209.244.4.106; client-port=40541; syn-fingerprint=65535:54:1:64:M1460,N,W1,N,N,T,S MacOS 10.4.8; data-bytes=0
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=us-ascii
From: Shane Amante <shane@castlepoint.net>
In-Reply-To: <09B801B2-B2AD-407F-B542-B02AEB997077@rob.sh>
Date: Wed, 11 Jul 2012 10:50:26 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <F634202B-3380-4620-93FE-4291A08F04CA@castlepoint.net>
References: <CAL9jLabOs02rOti4tezaZiHyiOD2f9vAhsoE9c-afFb4J1xYXQ@mail.gmail.com> <DCC302FAA9FE5F4BBA4DCAD46569377917449AF235@PRVPEXVS03.corp.twcable.com> <D05A81B4-1317-4C13-A2D6-05F5B41096CA@castlepoint.net> <09B801B2-B2AD-407F-B542-B02AEB997077@rob.sh>
To: Rob Shakir <rjs@rob.sh>
X-Mailer: Apple Mail (2.1278)
Cc: "grow@ietf.org grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] WGLC: draft-ietf-grow-ops-reqs-for-bgp-error-handling-04
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, 11 Jul 2012 16:51:10 -0000

Hi Rob,

On Jul 10, 2012, at 10:27 AM, Rob Shakir wrote:
> Hi Shane,
>=20
> Thanks very much for the detailed review of this document, and =
apologies it has taken a short while for me to reply.

No problem, on both counts.  See below.


> On 25 Jun 2012, at 22:15, Shane Amante wrote:
>=20
>> I've read this draft and support it being published as an =
Informational RFC.
>>=20
>> I do have some comments, which are not blocking, but that I do hope =
improve the clarity & readability of the draft.
>>=20
>> 1)  In Section 1.1, the following paragraph hints at the problems =
with current network architectures, but doesn't really come out and say =
what they are more directly.
>> ---snip---
>> Traditional network architectures would deploy an Interior Gateway
>> Protocol (IGP) to carry infrastructure and customer prefixes, with an
>> Exterior Gateway Protocol (EGP) such as BGP being utilised to
>> propagate these prefixes to other Autonomous Systems.  [...]
>> ---snip---
>> IMO, it would be better if the following section more directly said =
that scale, in terms of the sheer amount of routing information in BGP, =
has increased substantially, particularly in places like the core of a =
Route Reflection hierarchy with order _several_ million paths, and =
rising.  I wish I could point you at a link to a talk Danny & I gave to =
GROW and/or IDR at IETF 71 (?), but unfortunately I can't find a copy of =
the slides on the IETF's Web site.  You can see that it's in the GROW WG =
Agenda at IETF 71, but the slides link to a different presentation: =
<http://tools.ietf.org/wg/grow/agenda?item=3Dagenda71.html>
>>=20
>> Anyway, IMO, this is (from my vantage point) the single factor that =
makes outages not only much more visible, but /also/ (just as =
importantly) take longer to recover from ... (at the end of the day, CPU =
is finite, there are no "easy" answers wrt using multi-core processors =
to speed-up convergence of single AFI's, DRAM speeds are not keeping =
pace, etc.)  This may be useful to mention here to "set the stage", as =
it were, since throughout the draft there's a continuous (and, good) =
dialogue of not making convergence times worse or CPU load increase as a =
result of incorporating better recovery capabilities.  IOW, another =
benefit you don't really mention anywhere, but probably should, is that =
/theoretically/ some of these mechanisms may help further promote =
scalability of BGP.  Obviously, we won't know that until we are =
evaluating solutions and researchers have time to study them, etc.
>=20
> [rjs]: I tried to add something to cover this that fits in with =
Section 1.1:
>=20
>                        <t>
>                            The combination of the increased number of =
deployments of BGP-4 as an intra-AS routing protocol, its use for the =
propagation of additional types of routing and service information, and =
the growth of IP services has resulted in a substantial increase in the =
volume of information carried within BGP-4. In numerous networks, RIB =
sizes of the order of millions of entries exist, with particular =
high-scale points existing at BGP speakers performing aggregation or =
functionality designed improve utilisation of network resources (e.g., =
route reflector hierarchies). Whilst clearly an increase in the amount =
routing information carried in BGP results in greater impact to services =
during failures, it is also critical to their recovery time. The =
increased time to compute new paths following a failures and =
subsequently re-learn them following recoveries results in greater =
impact of failures within the protocol, and hence adds further weight to =
the requirement to avoid failures affecting all routing, or service, =
information carried via a particular adjacency. Whilst an argument could =
be made the convergence time of BGP-4 can be reduced through additional =
computational resource being deployed, it is notable that significant =
challenges continue to exist for operators of scaling BGP-4, and hence =
mechanisms which improve the scalability of the protocol are of =
particular note.
>                        </t>


The above looks good, but I've made some minor modifications.  See =
below.
---snip---
The combination of the increased number of deployments of BGP-4 as an =
intra-AS routing protocol, its use for the propagation of additional =
types of routing and service information, and the growth of IP services =
has resulted in a substantial increase in the volume of information =
carried within BGP-4. In numerous networks, RIB sizes of the order of =
millions of entries exist within individual BGP speakers, with =
particularly high-scale points exhibited at BGP speakers performing =
aggregation or functionality designed improve utilisation of network =
resources (e.g., route reflector hierarchies). Whilst clearly an =
increase in the amount routing information carried in BGP results in =
greater impact to services during failures, which is only amplified by a =
corresponding increase in recovery times. Following a failure, there is =
a substantial recovery time to learn, compute and distribute new paths, =
which results in a greater observed impact to services affected, and =
hence adds further weight to the requirement to avoid failures =
altogether or, at least, mitigate their impact to the narrowest scope =
possible, (e.g.: a specific NLRI). Whilst an argument could be made that =
convergence time of BGP-4 could potentially be reduced through =
deployment of additional computational resource, it is notable that =
solution is not necessarily straightforward from an implementation or =
deployment point-of-view, (e.g.: scaling computation resources within a =
single address-family is difficult).  Thus, significant challenges =
continue to exist for operators when scaling BGP-4 deployments, and =
hence mechanisms which improve the scalability of BGP-4 are very =
important.
---snip---


> [rjs]: Do you think this captures the point that was missing? I tried =
to avoid making any point that asserts that the requirements defined are =
going to make BGP scale better, but rather just call out that =
operationally, throwing resources at the problem isn't something that's =
always possible, so anything that reduces the amount of "work" BGP needs =
to do is interesting.

I definitely agree.


>> Related to the above, there is also the following paragraph:
>> ---snip---
>> Along with this change in role, the nature of the IP routing
>> information that is carried has changed.  BGP has become a ubiquitous
>> means by which service information can be propagated between devices.
>> ---snip---
>> ... it may be better to say that the original scope of BGP wrt *just* =
exchanging reachability information has expanded to include functions =
that *were* typically in the domain of 'traditional' provisioning =
activities, and leave it at that.  (You are obviously familiar with =
things like BGP A-D + VPLS-LDP vs. VPLS-BGP vs. RFC 4364 ... where the =
former divorces service discovery [provisioning] from signaling/network =
reachability, whereas the latter two tightly couple service discovery & =
network reachability).
>=20
> [rjs]: I'm not quite clear on whether this gets the point across =
completely - do we think that it is just that things have become in the =
realm of provisioning activities, or rather is it that there are more =
and more functions that are overloading onto BGP. I agree that this =
sentence doesn't necessarily capture that - but do you think that it's =
the generic information transfer protocol between PEs, as well as =
replacing provisioning mechanisms?

I believe that you are correct, and better off, in stating "more and =
more functions that are overloaded (sic) onto BGP".  Although, I'm not =
sure that "overloaded" is an appropriate adjective. =20

The point I was trying to get at is as follows.  I think there's a =
continuum of information exchanged within BGP from real-time information =
(reachability) to less dynamic (perhaps, even static) information, with =
_examples_ of the latter being auto-discovery/provisioning use cases.  =
While traditional applications, such as vanilla Internet service for =
which BGP was originally designed, only fall into the "real-time =
information" category ... there are a lot of new(er) applications that =
do not fit "neatly" in a single category and, in fact, span the range of =
real-time to less dynamic categories depending on which facet of a =
particular protocol you look at, (examples being: IPVPN, MVPN, VPLS-BGP, =
etc.).  Regardless, I don't think it's prudent to make value judgements =
(particularly at this point in time when these protocols are already =
widely deployed and successful) as to the "correctness" of these =
functions/services being in BGP, since that's bound to be very =
subjective.  Rather, we need to recognize the world for what it is =
today, which is why I think use of the word "overloaded" may be =
inappropriate.  Furthermore, I think that talking about this in such a =
context is only recognizing a symptom (the more complex the system, the =
higher the probability is to introduce errors), when in reality we =
should be trying to focus in on the root problem: since we've put so =
many eggs in one basket, we need unnoticeable (or, faster) recovery from =
errors that affect real-time, reachability information.



>> 2)  In Section 3, wrt the discussion on =
draft-ietf-idr-optional-transitive, it may be much more compelling to =
state that practically this solution has (currently) only been defined =
to be applicable to 3 out of the 29 total BGP path attributes that have =
been assigned by IANA, at this time.  And, even if you *could* to go =
farther, then only 10 out of the total 29 BGP path attributes are =
optional transitive.  So, the short story is: a lot more work in the =
area of session preservation
>> of iBGP sessions remains to be done, in particular wrt the other =
types of mandatory, discretionary, etc. attributes ... (assuming that =
such a thing is even technically possible with BGPv4, as we know it).
>=20
> [rjs]: Agreed, it is definitely worth highlighting this. I amended the =
paragraph mentioned to cover this:
>=20
>                    <t>
>                        At the time of writing, error handling =
mechanisms related to optional, transitive attributes - such as <xref =
target=3D'I-D.ietf-idr-optional-transitive' /> are restricted to =
handling only a subset of attribute errors - whereas the operational =
requirement is to expand this coverage to the widest set of errors =
possible (i.e., all semantic errors within UPDATE messages). =
Additionally, where approaches applicable to a greater number of =
attributes are proposed (e.g., <xref =
target=3D'I-D.chen-ebgp-error-handing'>), these are limited to =
deployment in eBGP applications only, where requirements also exist in =
intra-domain cases. As such, it is envisaged that if extended to cover =
these expanded cases, these mechanisms provide a means to avoid the =
transmission of a NOTIFICATION message to a remote BGP speaker, based on =
a single erroneous message, where at all possible, and hence meet this =
requirement. Critical errors, including those whereby the NLRI cannot be =
extracted from the UPDATE message, represent cases whereby the receiving =
system cannot handle the error gracefully based on this mechanism.
>                    </t>

OK.


>> [ snipped ]
>>=20
>> 4)  In Section 4, I can't really discern a strong (?) preference for =
one of the associated recommendations to recovering RIB consistency.  I =
*think* what you should say, more clearly, is there is a strong =
preference toward narrow, targeted refresh mechanisms covering specific =
routes over those broader solutions (recovering an entire Adj-RIB-In), =
to reduce the
>> impact on CPU, DRAM, etc.  Perhaps you could add a sentence at the =
end of the 4th paragraph, where you discuss =
draft-zeng-one-time-prefix-orf, along the lines of what I just mentioned =
above?  The good news is you state this very clearly, but much later, in =
Section 7.  Perhaps you can pull this sentence from Section 7 up to =
Section 4, as well?
>> ---snip---
>> [...] It is recommended that where available, any automatic (or
>> manual) triggered recovery mechanism behaviour utilises such targeted
>> means in preference to any whole RIB refresh mechanism (such as
>> ROUTE-REFRESH).
>> ---snip---=20
>=20
> [rjs]: Agreed, yes. I think that there is a strong preference for the =
targeted mechanism in terms of scale. I rephrased the Section 3 text to =
be stronger, and left in the Section 7 text:
>=20
> 	<t>
> 		Whilst re-advertisement of the whole BGP RIB provides a =
means by which withdrawn NLRI can be re-advertised, there are some =
scaling implications that must be considered. In the case that a =
ROUTE-REFRESH is generated, all NLRI must be re-packed into UPDATE =
messages and advertised by one speaker on the BGP session, whilst the =
other must receive all UPDATE messages, and validate the RIB's =
consistency. In order to avoid the control-plane load, it is therefore a =
requirement to utilise targeted mechanisms where possible, rather than =
incurring the additional load on both the advertising and receiving =
speaker of building and processing UPDATEs for the entire contents of =
the RIB.
> 	</t>

OK.


>> 5)  Section 5 seems targeted solely at recreating the data structures =
at one side of a BGP session, (specifically a receiver of a BGP =
session).  However, who's to say the corruption is not actually in the =
Adj-RIB-Out of the BGP transmitter?  Thus, transmitting you an =
Adj-RIB-Out all over again, even "gracefully", is unlikely to do much =
good.  Perhaps it would be good to consider whether the "Receiving =
Speaker", in Graceful Restart terminology, should consider 'gracefully' =
purging and recreating his Adj-RIB-Out data structures, as well, before =
re-xmit'ing them to the "Restarting Speaker"?
>=20
> [rjs]: Absolutely, this definitely wasn't handled in the draft -- =
thanks for pointing it out. I added the following text - do you think =
this is sufficient?
>=20
>                    <t>
>                        In some cases, the erroneous condition may be =
due to corruption of the Adj-RIB-Out on the advertising BGP speaker - =
rather than caused by the receiving speaker's state. In these cases, =
where existing structures are replayed whilst performing graceful =
restart functionality, the error condition is not necessarily resolved. =
Therefore, it is recommended that during a session restart event, as =
described within this section, the advertising speaker purge and rebuild =
RIB structures, in order to resolve any corruption within these =
structures.
>                    </t>

OK.


>> Nits:
>> 1)  =46rom <http://tools.ietf.org/html/rfc4271#section-3.1>:
>> ---snip---
>> For the purpose of this protocol, a route is defined as a unit of
>> information that pairs a set of destinations with the attributes of a
>> path to those destinations.  The set of destinations are systems
>> whose IP addresses are contained in one IP address prefix that is
>> carried in the Network Layer Reachability Information (NLRI) field of
>> an UPDATE message, and the path is the information reported in the
>> path attributes field of the same UPDATE message.
>> ---snip---
>> ... thus, to be more correct, I think you should scrub the document =
to say "route" in places where you're saying "prefix".  Some examples =
include:
>>=20
>> =
http://tools.ietf.org/html/draft-ietf-grow-ops-reqs-for-bgp-error-handling=
-04#section-1.2
>> ---snip---
>> o  It is unacceptable within modern deployments of the BGP-4 protocol
>>  that a single erroneous UPDATE packet affects prefixes that it
>>  does not carry.  This requirement therefore requires some
>> ---snip---
>> s/affects prefixes/affects routes/
>>=20
>> ---snip---
>> this reset of the BGP-4 session results in interruption to
>> forwarding packets (by means of withdrawing prefixes installed by
>> BGP-4 into a device's RIB, and subsequently FIB).  To this end,
>> ---snip---
>> s/withdrawing prefixes/withdrawing routes/
>=20
> [rjs]: Thanks, I've done this to reflect this definition.
>=20
>>=20
>> 2)  In Section 2, this may be just wording, but I'm unclear on what =
you mean in the below where you say: "... handle the error in a manner =
focused on the NLRI contained within the message".  Are you trying to =
say something like "constrain the logging and/or ignoring of malformed =
UPDATE messages specific to the narrowest subset of routes for which =
malformed path attributes have been received?"  I'm not suggesting my =
wording is necessarily better, in this case, but perhaps you could look =
at being a bit more precise below?
>> ---snip---
>> Where an UPDATE message is considered invalid by a BGP speaker due to
>> an error within a path attribute that is not the NLRI (where the
>> definition of NLRI includes reachability information encoded in the
>> MP_REACH_NLRI and MP_UNREACH_NLRI attributes as specified in
>> [RFC4760]) it is a requirement of any enhanced error handling
>> mechanism to handle the error in a manner focused on the NLRI
>> contained within the message. =20
>> ---snip---
>=20
> [rjs]: Yes - the intention is to define this based on the narrowest =
set possible, the reason that I used this wording is that (in my view) =
this is defined by the NLRI actually in the message (if there were =
differing path attributes for NLRI, then we expect that this is packed =
into a second UPDATE message). Perhaps a hybrid of our wording would =
clarify this (unless you think the assertion above is erroneous?).

I see your point now.  How about the following hybrid text?
---snip---
... it is a requirement of any enhanced error handling mechanism to =
constrain the error handling so that it is narrowly focused on the NLRI =
contained within the bad UPDATE message.
---snip---
=20

>> 3)  Section 2:
>> ---snip---
>> contained within the message.  Since in this case, the message
>> received from the remote peer is syntactically valid, it is
>> considered that such an UPDATE is indicative of erroneous data within
>> a path attribute.  [...]
>> ---snip---
>> s/path attribute/path attributes/
>=20
> [rjs]: Is the point here "one or more path attributes"? I'm not sure I =
quite understand the nit? :-)

Yes, sorry: "one or more path attributes".  (My point was you can't =
predict, here anyway, that it will only a single path attribute that is =
a problem.  Ideally, a more robust error-handling solution would not =
make such assumptions :-).


>> 4)  In Section 4, there do you really mean "transitive" here or do =
you instead mean "transient"?
>> ---snip---
>> It is of particular note for both means of recovering RIB consistency
>> described that these are effective only when considering transitive
>> errors within an implementation - for instance, should an RFC ...
>> ---snip---
>=20
> [rjs]: Transient, thanks.
>=20
>> ... also, in the following, do you mean "dynamic" instead of =
"transitive" in the below?
>> ---snip---
>> [...] It is not advisable that a transitive
>> filter and advertisement mechanism is triggered by all error handling
>> events due to the load this is likely to place on the neighbour
>> receiving such a request.  Where this BGP speaker is a relatively
>> ---snip---
>=20
> [rjs]: Dynamic is definitely what is meant here.
>=20
>>=20
>> 5)  In Section 7.1, I think you probably want to s/NLRI/route/ in =
several places, e.g.:
>> ---snip---
>> ... upstream speaker to perform a best-path selection, and =
re-advertise a
>> new set of __NLRI__ before the downstream system is able to converge =
to a
>> new path.
>> ---snip---
>=20
> [rjs]: Thanks, nit corrected.
>=20
> Many thanks again for your comments - if you could cast your eyes over =
the above corrections, and let me know if you feel they're sufficient, =
that'd be fantastic.

And, thank you Rob for your excellent work on this.

-shane=

From pds@lugs.com  Mon Jul 16 00:45:16 2012
Return-Path: <pds@lugs.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 EFF2021F850D for <grow@ietfa.amsl.com>; Mon, 16 Jul 2012 00:45:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.998
X-Spam-Level: 
X-Spam-Status: No, score=-99.998 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HTML_MESSAGE=0.001, 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 cQx9mUcNbX7g for <grow@ietfa.amsl.com>; Mon, 16 Jul 2012 00:45:15 -0700 (PDT)
Received: from murdock.lugs.com (murdock.lugs.com [192.80.15.4]) by ietfa.amsl.com (Postfix) with ESMTP id 8FF3C21F8604 for <grow@ietf.org>; Mon, 16 Jul 2012 00:45:06 -0700 (PDT)
Received: from r9m1fw1 (unknown [202.55.50.51]) by murdock.lugs.com (Postfix) with ESMTPSA id 1B6E9D342B for <grow@ietf.org>; Mon, 16 Jul 2012 03:45:46 -0400 (EDT)
From: "Peter Schoenmaker" <pds@lugs.com>
To: <grow@ietf.org>
Date: Mon, 16 Jul 2012 15:45:43 +0800
Message-ID: <000001cd6327$02757960$07606c20$@lugs.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0001_01CD636A.10992E90"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac1jJtrak/oC6NQHQTquq9ExqLCWLA==
Content-Language: en-us
Subject: [GROW] Agenda items for Vancouver IETF
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, 16 Jul 2012 07:45:16 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0001_01CD636A.10992E90
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hello,

 

I would like to request Agenda items for grow in Vancouver.  We currently
have 80 minutes on Tuesday morning.

 

Thanks

 

Peter

 

 


------=_NextPart_000_0001_01CD636A.10992E90
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><META =
HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p =
class=3DMsoNormal>Hello,<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>I would like =
to request Agenda items for grow in Vancouver.&nbsp; We currently have =
80 minutes on Tuesday morning.<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>Thanks<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>Peter<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_0001_01CD636A.10992E90--


From rjs@rob.sh  Wed Jul 18 10:53:56 2012
Return-Path: <rjs@rob.sh>
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 2BC0121F877A for <grow@ietfa.amsl.com>; Wed, 18 Jul 2012 10:53:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.586
X-Spam-Level: 
X-Spam-Status: No, score=0.586 tagged_above=-999 required=5 tests=[AWL=-0.986,  BAYES_00=-2.599, FB_INCREASE_VOL=3.629, SARE_MILLIONSOF=0.315,  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 lX5MPzFXNAMX for <grow@ietfa.amsl.com>; Wed, 18 Jul 2012 10:53:55 -0700 (PDT)
Received: from cappuccino.rob.sh (cappuccino.rob.sh [IPv6:2001:b98:201:101::10:cafe]) by ietfa.amsl.com (Postfix) with ESMTP id 2669B21F8739 for <grow@ietf.org>; Wed, 18 Jul 2012 10:53:55 -0700 (PDT)
Received: from [109.144.239.209] (helo=[10.96.3.93]) by cappuccino.rob.sh with esmtpa (Exim 4.72) (envelope-from <rjs@rob.sh>) id 1SrYQu-00054J-Qx; Wed, 18 Jul 2012 18:53:08 +0100
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=us-ascii
From: Rob Shakir <rjs@rob.sh>
In-Reply-To: <F634202B-3380-4620-93FE-4291A08F04CA@castlepoint.net>
Date: Wed, 18 Jul 2012 18:54:43 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <F4585D5C-5763-4759-AEA6-0E2B106CBC95@rob.sh>
References: <CAL9jLabOs02rOti4tezaZiHyiOD2f9vAhsoE9c-afFb4J1xYXQ@mail.gmail.com> <DCC302FAA9FE5F4BBA4DCAD46569377917449AF235@PRVPEXVS03.corp.twcable.com> <D05A81B4-1317-4C13-A2D6-05F5B41096CA@castlepoint.net> <09B801B2-B2AD-407F-B542-B02AEB997077@rob.sh> <F634202B-3380-4620-93FE-4291A08F04CA@castlepoint.net>
To: Shane Amante <shane@castlepoint.net>
X-Mailer: Apple Mail (2.1257)
Cc: "grow@ietf.org grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] WGLC: draft-ietf-grow-ops-reqs-for-bgp-error-handling-04
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, 18 Jul 2012 17:53:56 -0000

Hi Shane,

Thanks for the comments again, and apologies (again!) for the delay in =
responding.

Please find my responses in-line as [rjs].

On 11 Jul 2012, at 17:50, Shane Amante wrote:

>>> [...snip...]
>>=20
>> [rjs]: I tried to add something to cover this that fits in with =
Section 1.1:
>>=20
>>                       <t>
>>                           The combination of the increased number of =
deployments of BGP-4 as an intra-AS routing protocol, its use for the =
propagation of additional types of routing and service information, and =
the growth of IP services has resulted in a substantial increase in the =
volume of information carried within BGP-4. In numerous networks, RIB =
sizes of the order of millions of entries exist, with particular =
high-scale points existing at BGP speakers performing aggregation or =
functionality designed improve utilisation of network resources (e.g., =
route reflector hierarchies). Whilst clearly an increase in the amount =
routing information carried in BGP results in greater impact to services =
during failures, it is also critical to their recovery time. The =
increased time to compute new paths following a failures and =
subsequently re-learn them following recoveries results in greater =
impact of failures within the protocol, and hence adds further weight to =
the requirement to avoid failures affecting all routing, or service, =
information carried via a particular adjacency. Whilst an argument could =
be made the convergence time of BGP-4 can be reduced through additional =
computational resource being deployed, it is notable that significant =
challenges continue to exist for operators of scaling BGP-4, and hence =
mechanisms which improve the scalability of the protocol are of =
particular note.
>>                       </t>
>=20
>=20
> The above looks good, but I've made some minor modifications.  See =
below.
> ---snip---
> The combination of the increased number of deployments of BGP-4 as an =
intra-AS routing protocol, its use for the propagation of additional =
types of routing and service information, and the growth of IP services =
has resulted in a substantial increase in the volume of information =
carried within BGP-4. In numerous networks, RIB sizes of the order of =
millions of entries exist within individual BGP speakers, with =
particularly high-scale points exhibited at BGP speakers performing =
aggregation or functionality designed improve utilisation of network =
resources (e.g., route reflector hierarchies). Whilst clearly an =
increase in the amount routing information carried in BGP results in =
greater impact to services during failures, which is only amplified by a =
corresponding increase in recovery times. Following a failure, there is =
a substantial recovery time to learn, compute and distribute new paths, =
which results in a greater observed impact to services affected, and =
hence adds further weight to the requirement to avoid failures =
altogether or, at least, mitigate their impact to the narrowest scope =
possible, (e.g.: a specific NLRI). Whilst an argument could be made that =
convergence time of BGP-4 could potentially be reduced through =
deployment of additional computational resource, it is notable that =
solution is not necessarily straightforward from an implementation or =
deployment point-of-view, (e.g.: scaling computation resources within a =
single address-family is difficult).  Thus, significant challenges =
continue to exist for operators when scaling BGP-4 deployments, and =
hence mechanisms which improve the scalability of BGP-4 are very =
important.
> ---snip---

[rjs]: Thanks, other than some minor editorial changes I adopted this =
paragraph -- it seems like a good hybrid.


>>> [...snip...]
>>=20
>> [rjs]: I'm not quite clear on whether this gets the point across =
completely - do we think that it is just that things have become in the =
realm of provisioning activities, or rather is it that there are more =
and more functions that are overloading onto BGP. I agree that this =
sentence doesn't necessarily capture that - but do you think that it's =
the generic information transfer protocol between PEs, as well as =
replacing provisioning mechanisms?
>=20
> I believe that you are correct, and better off, in stating "more and =
more functions that are overloaded (sic) onto BGP".  Although, I'm not =
sure that "overloaded" is an appropriate adjective. =20

[rjs]: I guess there may be negative connotations of 'overloaded', I =
guess what I really mean is maybe "layered" onto BGP -- poor wording =
perhaps.

> The point I was trying to get at is as follows.  I think there's a =
continuum of information exchanged within BGP from real-time information =
(reachability) to less dynamic (perhaps, even static) information, with =
_examples_ of the latter being auto-discovery/provisioning use cases.  =
While traditional applications, such as vanilla Internet service for =
which BGP was originally designed, only fall into the "real-time =
information" category ... there are a lot of new(er) applications that =
do not fit "neatly" in a single category and, in fact, span the range of =
real-time to less dynamic categories depending on which facet of a =
particular protocol you look at, (examples being: IPVPN, MVPN, VPLS-BGP, =
etc.).  Regardless, I don't think it's prudent to make value judgements =
(particularly at this point in time when these protocols are already =
widely deployed and successful) as to the "correctness" of these =
functions/services being in BGP, since that's bound to be very =
subjective.  Rather, we need to recognize the world for what it is =
today, which is why I think use of the word "overloaded" may be =
inappropriate.  Furthermore, I think that talking about this in such a =
context is only recognizing a symptom (the more complex the system, the =
higher the probability is to introduce errors), when in reality we =
should be trying to focus in on the root problem: since we've put so =
many eggs in one basket, we need unnoticeable (or, faster) recovery from =
errors that affect real-time, reachability information.

[rjs]: Completely agree with this. I think my poor choice of wording =
perhaps portrayed my view as negative -- rather, the key point for me is =
that the robustness and error handling that we are discussing here is =
designed with the vanilla Internet service as the baseline - and as we =
extend the protocol to different deployment cases (no judgement about =
the value of which is made), then some of the initial assumptions =
perhaps don't hold true. I think this is in agreement with yourself, =
insofar that I think we would both assert that for the real-time =
information, potentially the behaviour required in a number of areas of =
the protocol is not the same as the behaviour required for relatively =
static information.

>>=20
>> [rjs]: Yes - the intention is to define this based on the narrowest =
set possible, the reason that I used this wording is that (in my view) =
this is defined by the NLRI actually in the message (if there were =
differing path attributes for NLRI, then we expect that this is packed =
into a second UPDATE message). Perhaps a hybrid of our wording would =
clarify this (unless you think the assertion above is erroneous?).
>=20
> I see your point now.  How about the following hybrid text?
> ---snip---
> ... it is a requirement of any enhanced error handling mechanism to =
constrain the error handling so that it is narrowly focused on the NLRI =
contained within the bad UPDATE message.
> ---snip---

[rjs]: Sure, this sounds good.

>>> 3)  Section 2:
>>> ---snip---
>>> contained within the message.  Since in this case, the message
>>> received from the remote peer is syntactically valid, it is
>>> considered that such an UPDATE is indicative of erroneous data =
within
>>> a path attribute.  [...]
>>> ---snip---
>>> s/path attribute/path attributes/
>>=20
>> [rjs]: Is the point here "one or more path attributes"? I'm not sure =
I quite understand the nit? :-)
>=20
> Yes, sorry: "one or more path attributes".  (My point was you can't =
predict, here anyway, that it will only a single path attribute that is =
a problem.  Ideally, a more robust error-handling solution would not =
make such assumptions :-).

[rjs]: ACK, updated this to 'one or more' :-)

>> Many thanks again for your comments - if you could cast your eyes =
over the above corrections, and let me know if you feel they're =
sufficient, that'd be fantastic.
>=20
> And, thank you Rob for your excellent work on this.

[rjs]: No worries - I'll take a read through and submit an -05 of the =
draft that merges the edits we've discussed in this thread.

Thanks again for the comments,
r.


From petrlapu@microsoft.com  Thu Jul 19 14:00:35 2012
Return-Path: <petrlapu@microsoft.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 70E0E11E8099 for <grow@ietfa.amsl.com>; Thu, 19 Jul 2012 14:00:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 FPMy0FdaO-Jc for <grow@ietfa.amsl.com>; Thu, 19 Jul 2012 14:00:34 -0700 (PDT)
Received: from tx2outboundpool.messaging.microsoft.com (tx2ehsobe005.messaging.microsoft.com [65.55.88.15]) by ietfa.amsl.com (Postfix) with ESMTP id B056711E8086 for <grow@ietf.org>; Thu, 19 Jul 2012 14:00:34 -0700 (PDT)
Received: from mail242-tx2-R.bigfish.com (10.9.14.248) by TX2EHSOBE006.bigfish.com (10.9.40.26) with Microsoft SMTP Server id 14.1.225.23; Thu, 19 Jul 2012 21:01:28 +0000
Received: from mail242-tx2 (localhost [127.0.0.1])	by mail242-tx2-R.bigfish.com (Postfix) with ESMTP id 27E4A4001F5; Thu, 19 Jul 2012 21:01:26 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:131.107.125.8; KIP:(null); UIP:(null); IPV:NLI; H:TK5EX14HUBC101.redmond.corp.microsoft.com; RD:none; EFVD:NLI
X-SpamScore: -21
X-BigFish: VS-21(zz9371Ic85fhzz1202hzz1033IL8275bh8275dhz2fh2a8h668h839hd25hf0ah107ah)
Received-SPF: pass (mail242-tx2: domain of microsoft.com designates 131.107.125.8 as permitted sender) client-ip=131.107.125.8; envelope-from=petrlapu@microsoft.com; helo=TK5EX14HUBC101.redmond.corp.microsoft.com ; icrosoft.com ; 
Received: from mail242-tx2 (localhost.localdomain [127.0.0.1]) by mail242-tx2 (MessageSwitch) id 1342731683479874_27238; Thu, 19 Jul 2012 21:01:23 +0000 (UTC)
Received: from TX2EHSMHS021.bigfish.com (unknown [10.9.14.236])	by mail242-tx2.bigfish.com (Postfix) with ESMTP id 5C92F3A0047; Thu, 19 Jul 2012 21:01:23 +0000 (UTC)
Received: from TK5EX14HUBC101.redmond.corp.microsoft.com (131.107.125.8) by TX2EHSMHS021.bigfish.com (10.9.99.121) with Microsoft SMTP Server (TLS) id 14.1.225.23; Thu, 19 Jul 2012 21:01:23 +0000
Received: from TK5EX14MBXC298.redmond.corp.microsoft.com ([169.254.1.126]) by TK5EX14HUBC101.redmond.corp.microsoft.com ([157.54.7.153]) with mapi id 14.02.0309.003; Thu, 19 Jul 2012 21:01:21 +0000
From: Petr Lapukhov <petrlapu@microsoft.com>
To: Peter Schoenmaker <pds@lugs.com>, "grow@ietf.org" <grow@ietf.org>
Thread-Topic: [GROW] Agenda items for Vancouver IETF
Thread-Index: Ac1jJtrak/oC6NQHQTquq9ExqLCWLACyofBg
Date: Thu, 19 Jul 2012 21:01:20 +0000
Message-ID: <F1688F301726A74C86D199FA0CAE08E51ADE5A5F@TK5EX14MBXC298.redmond.corp.microsoft.com>
References: <000001cd6327$02757960$07606c20$@lugs.com>
In-Reply-To: <000001cd6327$02757960$07606c20$@lugs.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.75]
Content-Type: multipart/alternative; boundary="_000_F1688F301726A74C86D199FA0CAE08E51ADE5A5FTK5EX14MBXC298r_"
MIME-Version: 1.0
X-OriginatorOrg: microsoft.com
Cc: "Jon Mitchell \(GNS\)" <Jon.Mitchell@microsoft.com>, "Ariff Premji \(ariff@aristanetworks.com\) \(ariff@aristanetworks.com\)" <ariff@aristanetworks.com>
Subject: Re: [GROW] Agenda items for Vancouver IETF
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, 19 Jul 2012 21:00:35 -0000

--_000_F1688F301726A74C86D199FA0CAE08E51ADE5A5FTK5EX14MBXC298r_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Peter,

We would like present our operational experience using BGP for routing in l=
arge scale data center, documented here

http://tools.ietf.org/html/draft-lapukhov-bgp-routing-large-dc-01

Thank you,

Petr

From: grow-bounces@ietf.org [mailto:grow-bounces@ietf.org] On Behalf Of Pet=
er Schoenmaker
Sent: Monday, July 16, 2012 12:46 AM
To: grow@ietf.org
Subject: [GROW] Agenda items for Vancouver IETF

Hello,

I would like to request Agenda items for grow in Vancouver.  We currently h=
ave 80 minutes on Tuesday morning.

Thanks

Peter



--_000_F1688F301726A74C86D199FA0CAE08E51ADE5A5FTK5EX14MBXC298r_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Hi Peter,<o:p></o:p></=
span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">We would like present =
our operational experience using BGP for routing in large scale data center=
, documented here<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><a href=3D"http://tool=
s.ietf.org/html/draft-lapukhov-bgp-routing-large-dc-01">http://tools.ietf.o=
rg/html/draft-lapukhov-bgp-routing-large-dc-01</a><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Thank you,<o:p></o:p><=
/span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Petr<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> grow-bou=
nces@ietf.org [mailto:grow-bounces@ietf.org]
<b>On Behalf Of </b>Peter Schoenmaker<br>
<b>Sent:</b> Monday, July 16, 2012 12:46 AM<br>
<b>To:</b> grow@ietf.org<br>
<b>Subject:</b> [GROW] Agenda items for Vancouver IETF<o:p></o:p></span></p=
>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Hello,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">I would like to request Agenda items for grow in Van=
couver.&nbsp; We currently have 80 minutes on Tuesday morning.<o:p></o:p></=
p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Thanks<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Peter<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_F1688F301726A74C86D199FA0CAE08E51ADE5A5FTK5EX14MBXC298r_--

From pds@lugs.com  Thu Jul 19 23:06:04 2012
Return-Path: <pds@lugs.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 9D71221F8668 for <grow@ietfa.amsl.com>; Thu, 19 Jul 2012 23:06:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.091
X-Spam-Level: 
X-Spam-Status: No, score=-100.091 tagged_above=-999 required=5 tests=[AWL=0.093, BAYES_40=-0.185, 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 rifIqde7zTRh for <grow@ietfa.amsl.com>; Thu, 19 Jul 2012 23:06:04 -0700 (PDT)
Received: from murdock.lugs.com (murdock.lugs.com [192.80.15.4]) by ietfa.amsl.com (Postfix) with ESMTP id F074C21F8552 for <grow@ietf.org>; Thu, 19 Jul 2012 23:06:03 -0700 (PDT)
Received: from r9m1fw1 (unknown [202.55.50.51]) by murdock.lugs.com (Postfix) with ESMTPSA id 5C1E9D359B for <grow@ietf.org>; Fri, 20 Jul 2012 02:06:57 -0400 (EDT)
From: "Peter Schoenmaker" <pds@lugs.com>
To: <grow@ietf.org>
Date: Fri, 20 Jul 2012 14:06:50 +0800
Message-ID: <004b01cd663d$dbc177a0$934466e0$@lugs.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Content-Language: en-us
Thread-Index: Ac1mPbesq7CkPniURaWrMZY2mGePxQ==
Subject: [GROW] Agenda posted for ietf 84
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, 20 Jul 2012 06:06:04 -0000

Hi,

I have posted the agenda for IETF 84.  We do have extra time if anyone else
would like to request time.


GROW WG IETF 84 agenda  

Administrivia			5 minutes
  o Blue sheets
  o Scribe/jabber

GROW Update			5 minutes

Russ White			15 minutes
  o  draft-white-filtering-te-routes

Petr Lapukhov 			15 minutes
  o  draft-lapukhov-bgp-routing-large-dc-01


thanks

peter



From mbehring@cisco.com  Tue Jul 17 05:48:12 2012
Return-Path: <mbehring@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 71EF821F85A2; Tue, 17 Jul 2012 05:48:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.999
X-Spam-Level: 
X-Spam-Status: No, score=-9.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_13=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 ccKm3qvhCwIk; Tue, 17 Jul 2012 05:48:11 -0700 (PDT)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) by ietfa.amsl.com (Postfix) with ESMTP id E5D9921F857A; Tue, 17 Jul 2012 05:48:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=8624; q=dns/txt; s=iport; t=1342529338; x=1343738938; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=8asSaACKdXk2ZXsQQUewRLWDGfj6T1WsZZ27cMJZTEA=; b=Ag5VWgW/wYza7pyjVH3Uy6nRA4WKhUkxzhPKu22W6N/HlWidA2TScZHB 3nneSoc7NXCvcR2T9eES4CytW5YCJSF28yUPAx07nNbQwPLlQAJQ7puUU QBEHN3zfi7NhldEX0Pea6FSlTqpnAoXxNM/DFP0bWAO8UYCulz+FPn7ZU I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAFAPBeBVCtJXHB/2dsb2JhbABFuU+BB4IgAQEBBAEBAQ8BJzQEBwwEAgEIEQQBAQsUCQcnCxQJCAEBBAENBQgBCwcHh2sLnFqgMotAFAaFTWADlk+NEIFmgl+BVgk
X-IronPort-AV: E=Sophos;i="4.77,603,1336348800"; d="scan'208";a="99613793"
Received: from rcdn-core2-6.cisco.com ([173.37.113.193]) by rcdn-iport-9.cisco.com with ESMTP; 17 Jul 2012 12:48:37 +0000
Received: from xhc-rcd-x01.cisco.com (xhc-rcd-x01.cisco.com [173.37.183.75]) by rcdn-core2-6.cisco.com (8.14.5/8.14.5) with ESMTP id q6HCmbwH025133 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 17 Jul 2012 12:48:37 GMT
Received: from xmb-rcd-x14.cisco.com ([169.254.4.60]) by xhc-rcd-x01.cisco.com ([173.37.183.75]) with mapi id 14.02.0298.004; Tue, 17 Jul 2012 07:48:37 -0500
From: "Michael Behringer (mbehring)" <mbehring@cisco.com>
To: "George, Wes" <wesley.george@twcable.com>, "grow@ietf.org" <grow@ietf.org>, "v6ops@ietf.org" <v6ops@ietf.org>
Thread-Topic: draft-behringer-lla-only and draft-ietf-grow-private-ip-sp-cores
Thread-Index: Ac0M1PTc8z4ZGA26S5W5umLx5IqzdwB6fdhwFVYuJJA=
Date: Tue, 17 Jul 2012 12:48:36 +0000
Message-ID: <3AA7118E69D7CD4BA3ECD5716BAF28DF02C124@xmb-rcd-x14.cisco.com>
References: <20120328112128.19122.59432.idtracker@ietfa.amsl.com> <DCC302FAA9FE5F4BBA4DCAD465693779173D6E9C51@PRVPEXVS03.corp.twcable.com>
In-Reply-To: <DCC302FAA9FE5F4BBA4DCAD465693779173D6E9C51@PRVPEXVS03.corp.twcable.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.55.194.18]
x-tm-as-product-ver: SMEX-10.2.0.1135-7.000.1014-19046.000
x-tm-as-result: No--45.061600-8.000000-31
x-tm-as-user-approved-sender: No
x-tm-as-user-blocked-sender: No
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Sat, 21 Jul 2012 13:53:16 -0700
Cc: "draft-behringer-lla-only@tools.ietf.org" <draft-behringer-lla-only@tools.ietf.org>
Subject: Re: [GROW] draft-behringer-lla-only and 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, 17 Jul 2012 12:48:12 -0000

Wes,=20

Thanks for your great input and sorry for the delay. In the meantime we hav=
e updated our draft to include many of your (and others') comments. (http:/=
/tools.ietf.org/html/draft-behringer-lla-only-01). Most importantly, we mad=
e it now an informational draft.=20

We believe it is best to keep the drafts separate. There are important diff=
erences between private addresses and link local: One is routed, one is not=
; one needs to be configured, one not. We added however a xref to draft-iet=
f-grow-private-ip-sp-cores, because as you rightly comment, they are relate=
d.

We still think there is value in draft-behringer-lla-only. Bottom line, we =
want to provide a document presenting the issues and advantages that allows=
 operators to make an educated decision whether link local is the right app=
roach for them.=20

We'll ask for slots in Vancouver at v6ops and opsec to discuss the new vers=
ion.=20

Eric and Michael

> -----Original Message-----
> From: George, Wes [mailto:wesley.george@twcable.com]
> Sent: 31 March 2012 01:15
> To: grow@ietf.org; v6ops@ietf.org
> Cc: draft-behringer-lla-only@tools.ietf.org; Anthony Kirkham
> Subject: draft-behringer-lla-only and draft-ietf-grow-private-ip-sp-cores
> =09
> Cross-posting to both lists again because I was unable to attend the v6op=
s
> session where draft-behringer was discussed, draft-ietf-grow-private-ip-s=
p-
> cores is likely nearing WGLC, and I believe that the issue I raised needs=
 to be
> addressed before either proceeds. I defer to the chairs of both groups to
> determine how to manage this across the two groups.
>=20
> After reviewing both draft-grow-private-ip-sp-cores (Kirkham) and draft-
> behringer-lla-only again, I am even more convinced that they either need =
to
> be merged, or that draft-behringer needs to be abandoned altogether as a
> bad idea. Draft-grow-private-ip-sp-cores is quite a lot more complete in =
its
> discussion of the considerations around private IP usage, but focuses on
> IPv4, meaning that it *is* incomplete for lack of discussion of IPv6, whi=
ch is
> a reality in most SP cores today. Nearly all of the same considerations a=
pply
> for IPv4 and IPv6 in this case, so there are probably a limited number of
> changes that would be necessary to cover IPv6 in the Kirkham document.
> I think that we need to come to some consensus on the recommended
> behavior on both cases. If the recommendation is different for one versus
> the other, we need to have a unified and clear articulation as to why thi=
s is
> the case. It may be that the consensus is to not recommend a behavior at =
all,
> and simply expand the format of Kirkham's document to cover any IPv6-
> specific items, since it discusses pros and cons evenly (as an informatio=
nal
> doc) rather than recommending anything as a BCP. My vote is to do this, a=
s I
> am unconvinced that use of LLA represents BCP today, nor should it. I
> outline some reasons below, but that's probably not as critical if others
> agree that this is the proper method to proceed with these documents.
>=20
>=20
>=20
> If draft-behringer is left as a separate document, here are some specific
> comments:
> The advantages proposed in draft-behringer are IMO not enough to justify
> recommending use of LLA.
> - Smaller routing tables can be achieved through other methods such as
> setting the interfaces into passive mode in the IGP (so that they are not
> redistributed into the IGP) and/or not redistributing connected routes.
> Further, as SPs make great use of interface bundling (LAG), the number of
> interfaces with IP addresses is dramatically reduced, making the need to
> pull the point to point interfaces out of the routing table significantly=
 lower.
> - Reduced attack surface - draft-ietf-grow-private-ip-sp-cores sections 1=
0
> and 11 discuss this in great detail, and come to the conclusion that it i=
s of
> limited benefit, and that alternatives exist to protect the infrastructur=
e.
> - lower configuration complexity - while this is true, it is replaced by
> additional complexity in troubleshooting. In the case of traces and pings
> locally on the box, it adds the additional step of requiring the operator=
 to
> use extended ping and trace commands to specify the exit interface in ord=
er
> to make the ping work (vs simply issuing "ping [ip address]"), and makes =
it
> nearly impossible to derive the address of the remote interface without
> determining the remote side router through some other means and logging
> into the router to look. (vs practice today of using an IP in the same su=
bnet,
> usually 1 digit up or down that can be guessed to save time).
> - less address space: The other draft mentions this as well, in the conte=
xt of
> IPv4 where it might make a difference, but this simply is not much of a
> concern with IPv6. An entire network could be numbered many times over
> out of one /64.
> -simpler DNS : Most ISPs operating at the scale where this makes any
> difference at all have tools to build the DNS forward and reverse entries=
 for
> their infrastructure automatically based on the router name and interface
> name extracted from their inventory tools. It's a few bits of scripting, =
so it's
> not like having less interfaces in DNS results in any net reduction in wo=
rk or
> increase in the possibility of mistakes.
>=20
> - Draft-ietf-grow-private-ip-sp-cores rightly notes that the proposed
> solution to broken pings/traces/PMTUD from draft-behringer (RFC 5837) has
> little or no implementation. This makes it a hard sell as any sort of
> recommended solution unless the benefits are much more significant than
> what is currently discussed in draft-behringer. This has to be a large en=
ough
> benefit to justify pushing hard on router vendors to implement the featur=
e
> and SPs to certify and deploy the code, and frankly there are many more
> important features to consider.
>=20
> Thanks,
>=20
> Wes George
>=20
>=20
> > -----Original Message-----
> > From: grow-bounces@ietf.org [mailto:grow-bounces@ietf.org] On Behalf
> > Of internet-drafts@ietf.org
> > Sent: Wednesday, March 28, 2012 7:21 AM
> > To: i-d-announce@ietf.org
> > Cc: grow@ietf.org
> > Subject: [GROW] I-D Action: draft-ietf-grow-private-ip-sp-cores-00.txt
> >
> >
> > 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 Intern=
et
> >       Author(s)       : Anthony Kirkham
> >       Filename        : draft-ietf-grow-private-ip-sp-cores-00.txt
> >       Pages           : 15
> >       Date            : 2012-03-28
> >
> >    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 discussio=
n
> >    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-core
> > s-00.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
> > -00.txt
> >
> > _______________________________________________
> > GROW mailing list
> > GROW@ietf.org
> > https://www.ietf.org/mailman/listinfo/grow
>=20
> This E-mail and any of its attachments may contain Time Warner Cable
> proprietary information, which is privileged, confidential, or subject to
> copyright belonging to Time Warner Cable. This E-mail is intended solely =
for
> the use of the individual or entity to which it is addressed. If you are =
not the
> intended recipient of this E-mail, you are hereby notified that any
> dissemination, distribution, copying, or action taken in relation to the
> contents of and attachments to this E-mail is strictly prohibited and may=
 be
> unlawful. If you have received this E-mail in error, please notify the se=
nder
> immediately and permanently delete the original and any copy of this E-
> mail and any printout.

From warren@kumari.net  Sun Jul 22 18:28:34 2012
Return-Path: <warren@kumari.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 82C8D21F8608; Sun, 22 Jul 2012 18:28:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.038
X-Spam-Level: 
X-Spam-Status: No, score=-106.038 tagged_above=-999 required=5 tests=[AWL=-0.039, BAYES_00=-2.599, J_CHICKENPOX_13=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 ffHS8NIGo7Ut; Sun, 22 Jul 2012 18:28:33 -0700 (PDT)
Received: from vimes.kumari.net (vimes.kumari.net [198.186.192.250]) by ietfa.amsl.com (Postfix) with ESMTP id 6840521F85E7; Sun, 22 Jul 2012 18:28:33 -0700 (PDT)
Received: from [5.5.8.21] (vpn.snozzages.com [204.194.22.7]) by vimes.kumari.net (Postfix) with ESMTPSA id 3AED41B405FA; Sun, 22 Jul 2012 21:28:32 -0400 (EDT)
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=us-ascii
From: Warren Kumari <warren@kumari.net>
In-Reply-To: <3AA7118E69D7CD4BA3ECD5716BAF28DF02C124@xmb-rcd-x14.cisco.com>
Date: Sun, 22 Jul 2012 21:28:37 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <20346E31-B14E-42FC-8AE9-F5CA97CEC38C@kumari.net>
References: <20120328112128.19122.59432.idtracker@ietfa.amsl.com> <DCC302FAA9FE5F4BBA4DCAD465693779173D6E9C51@PRVPEXVS03.corp.twcable.com> <3AA7118E69D7CD4BA3ECD5716BAF28DF02C124@xmb-rcd-x14.cisco.com>
To: Michael Behringer (mbehring) <mbehring@cisco.com>
X-Mailer: Apple Mail (2.1278)
Cc: "grow@ietf.org" <grow@ietf.org>, Warren Kumari <warren@kumari.net>, "v6ops@ietf.org" <v6ops@ietf.org>, "draft-behringer-lla-only@tools.ietf.org" <draft-behringer-lla-only@tools.ietf.org>
Subject: Re: [GROW] draft-behringer-lla-only and 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: Mon, 23 Jul 2012 01:28:34 -0000

On Jul 17, 2012, at 8:48 AM, Michael Behringer (mbehring) wrote:

> Wes,=20
>=20
> Thanks for your great input and sorry for the delay. In the meantime =
we have updated our draft to include many of your (and others') =
comments. (http://tools.ietf.org/html/draft-behringer-lla-only-01). Most =
importantly, we made it now an informational draft.=20
>=20
> We believe it is best to keep the drafts separate.

Excellent (actually, I believe that draft-ietf-grow-private-ip-sp-cores =
lies with the IESG at the moment, and so it kinda has to stay =
separate)...

> There are important differences between private addresses and link =
local: One is routed, one is not; one needs to be configured, one not. =
We added however a xref to draft-ietf-grow-private-ip-sp-cores, because =
as you rightly comment, they are related.
>=20

Cool.

> We still think there is value in draft-behringer-lla-only. Bottom =
line, we want to provide a document presenting the issues and advantages =
that allows operators to make an educated decision whether link local is =
the right approach for them.=20
>=20
> We'll ask for slots in Vancouver at v6ops and opsec to discuss the new =
version.=20
>=20

Excellent, and just to close the loop (so v6ops / grow folk know), you =
did ask, and we've created a slot on the OpSec agenda  (15min, =
Wednesday, Aug 1, 13:00 - 15:00, Georgia B) for this...

W
=20

> Eric and Michael
>=20
>> -----Original Message-----
>> From: George, Wes [mailto:wesley.george@twcable.com]
>> Sent: 31 March 2012 01:15
>> To: grow@ietf.org; v6ops@ietf.org
>> Cc: draft-behringer-lla-only@tools.ietf.org; Anthony Kirkham
>> Subject: draft-behringer-lla-only and =
draft-ietf-grow-private-ip-sp-cores
>> =09
>> Cross-posting to both lists again because I was unable to attend the =
v6ops
>> session where draft-behringer was discussed, =
draft-ietf-grow-private-ip-sp-
>> cores is likely nearing WGLC, and I believe that the issue I raised =
needs to be
>> addressed before either proceeds. I defer to the chairs of both =
groups to
>> determine how to manage this across the two groups.
>>=20
>> After reviewing both draft-grow-private-ip-sp-cores (Kirkham) and =
draft-
>> behringer-lla-only again, I am even more convinced that they either =
need to
>> be merged, or that draft-behringer needs to be abandoned altogether =
as a
>> bad idea. Draft-grow-private-ip-sp-cores is quite a lot more complete =
in its
>> discussion of the considerations around private IP usage, but focuses =
on
>> IPv4, meaning that it *is* incomplete for lack of discussion of IPv6, =
which is
>> a reality in most SP cores today. Nearly all of the same =
considerations apply
>> for IPv4 and IPv6 in this case, so there are probably a limited =
number of
>> changes that would be necessary to cover IPv6 in the Kirkham =
document.
>> I think that we need to come to some consensus on the recommended
>> behavior on both cases. If the recommendation is different for one =
versus
>> the other, we need to have a unified and clear articulation as to why =
this is
>> the case. It may be that the consensus is to not recommend a behavior =
at all,
>> and simply expand the format of Kirkham's document to cover any IPv6-
>> specific items, since it discusses pros and cons evenly (as an =
informational
>> doc) rather than recommending anything as a BCP. My vote is to do =
this, as I
>> am unconvinced that use of LLA represents BCP today, nor should it. I
>> outline some reasons below, but that's probably not as critical if =
others
>> agree that this is the proper method to proceed with these documents.
>>=20
>>=20
>>=20
>> If draft-behringer is left as a separate document, here are some =
specific
>> comments:
>> The advantages proposed in draft-behringer are IMO not enough to =
justify
>> recommending use of LLA.
>> - Smaller routing tables can be achieved through other methods such =
as
>> setting the interfaces into passive mode in the IGP (so that they are =
not
>> redistributed into the IGP) and/or not redistributing connected =
routes.
>> Further, as SPs make great use of interface bundling (LAG), the =
number of
>> interfaces with IP addresses is dramatically reduced, making the need =
to
>> pull the point to point interfaces out of the routing table =
significantly lower.
>> - Reduced attack surface - draft-ietf-grow-private-ip-sp-cores =
sections 10
>> and 11 discuss this in great detail, and come to the conclusion that =
it is of
>> limited benefit, and that alternatives exist to protect the =
infrastructure.
>> - lower configuration complexity - while this is true, it is replaced =
by
>> additional complexity in troubleshooting. In the case of traces and =
pings
>> locally on the box, it adds the additional step of requiring the =
operator to
>> use extended ping and trace commands to specify the exit interface in =
order
>> to make the ping work (vs simply issuing "ping [ip address]"), and =
makes it
>> nearly impossible to derive the address of the remote interface =
without
>> determining the remote side router through some other means and =
logging
>> into the router to look. (vs practice today of using an IP in the =
same subnet,
>> usually 1 digit up or down that can be guessed to save time).
>> - less address space: The other draft mentions this as well, in the =
context of
>> IPv4 where it might make a difference, but this simply is not much of =
a
>> concern with IPv6. An entire network could be numbered many times =
over
>> out of one /64.
>> -simpler DNS : Most ISPs operating at the scale where this makes any
>> difference at all have tools to build the DNS forward and reverse =
entries for
>> their infrastructure automatically based on the router name and =
interface
>> name extracted from their inventory tools. It's a few bits of =
scripting, so it's
>> not like having less interfaces in DNS results in any net reduction =
in work or
>> increase in the possibility of mistakes.
>>=20
>> - Draft-ietf-grow-private-ip-sp-cores rightly notes that the proposed
>> solution to broken pings/traces/PMTUD from draft-behringer (RFC 5837) =
has
>> little or no implementation. This makes it a hard sell as any sort of
>> recommended solution unless the benefits are much more significant =
than
>> what is currently discussed in draft-behringer. This has to be a =
large enough
>> benefit to justify pushing hard on router vendors to implement the =
feature
>> and SPs to certify and deploy the code, and frankly there are many =
more
>> important features to consider.
>>=20
>> Thanks,
>>=20
>> Wes George
>>=20
>>=20
>>> -----Original Message-----
>>> From: grow-bounces@ietf.org [mailto:grow-bounces@ietf.org] On Behalf
>>> Of internet-drafts@ietf.org
>>> Sent: Wednesday, March 28, 2012 7:21 AM
>>> To: i-d-announce@ietf.org
>>> Cc: grow@ietf.org
>>> Subject: [GROW] I-D Action: =
draft-ietf-grow-private-ip-sp-cores-00.txt
>>>=20
>>>=20
>>> 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.
>>>=20
>>>      Title           : Issues with Private IP Addressing in the =
Internet
>>>      Author(s)       : Anthony Kirkham
>>>      Filename        : draft-ietf-grow-private-ip-sp-cores-00.txt
>>>      Pages           : 15
>>>      Date            : 2012-03-28
>>>=20
>>>   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.
>>>=20
>>>=20
>>> A URL for this Internet-Draft is:
>>> =
http://www.ietf.org/internet-drafts/draft-ietf-grow-private-ip-sp-core
>>> s-00.txt
>>>=20
>>> Internet-Drafts are also available by anonymous FTP at:
>>> ftp://ftp.ietf.org/internet-drafts/
>>>=20
>>> This Internet-Draft can be retrieved at:
>>> =
ftp://ftp.ietf.org/internet-drafts/draft-ietf-grow-private-ip-sp-cores
>>> -00.txt
>>>=20
>>> _______________________________________________
>>> GROW mailing list
>>> GROW@ietf.org
>>> https://www.ietf.org/mailman/listinfo/grow
>>=20
>> This E-mail and any of its attachments may contain Time Warner Cable
>> proprietary information, which is privileged, confidential, or =
subject to
>> copyright belonging to Time Warner Cable. This E-mail is intended =
solely for
>> the use of the individual or entity to which it is addressed. If you =
are not the
>> intended recipient of this E-mail, you are hereby notified that any
>> dissemination, distribution, copying, or action taken in relation to =
the
>> contents of and attachments to this E-mail is strictly prohibited and =
may be
>> unlawful. If you have received this E-mail in error, please notify =
the sender
>> immediately and permanently delete the original and any copy of this =
E-
>> mail and any printout.
> _______________________________________________
> GROW mailing list
> GROW@ietf.org
> https://www.ietf.org/mailman/listinfo/grow
>=20

--
"Build a man a fire, and he'll be warm for a day. Set a man on fire, and =
he'll be warm for the rest of his life." -- Terry Pratchett



From christopher.morrow@gmail.com  Sun Jul 22 19:17:17 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 75CC621F863D for <grow@ietfa.amsl.com>; Sun, 22 Jul 2012 19:17:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.724
X-Spam-Level: 
X-Spam-Status: No, score=-100.724 tagged_above=-999 required=5 tests=[AWL=-2.785, BAYES_05=-1.11, FB_INCREASE_VOL=3.629, RCVD_IN_DNSWL_LOW=-1, SARE_MILLIONSOF=0.315, 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 ResSjGb4s+lo for <grow@ietfa.amsl.com>; Sun, 22 Jul 2012 19:17:16 -0700 (PDT)
Received: from mail-vc0-f172.google.com (mail-vc0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 6D9D821F8616 for <grow@ietf.org>; Sun, 22 Jul 2012 19:17:16 -0700 (PDT)
Received: by vcbfo14 with SMTP id fo14so4635778vcb.31 for <grow@ietf.org>; Sun, 22 Jul 2012 19:17:16 -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=1ep+NuASCvVbtWIkVJ3AKbhQNeXVVNt3cKVG5bJ2hv4=; b=0/2efomPzjzYmX5u2FOCeL3yusVjH6Spb0q5vGwuJ2Bj4pNvQ8un0GXdgKlHwerB67 lQOb6yvfCLbcJQ6GuAG3gpB8psybFMN3bA0lfnCpRB1sZhP0s9JMerkeJkriYUSFonk4 B2m6nF4hLYyR+DavcwZvque6T+DhvNohZaGGKMo/gQ4RzntB5yG/YJLWp98g2cEY3G5b UWe3aJREqRcev1cyYsubb3d1fePDm/dIThCJV/eYyWQIwi46u6q+VC8y75aOAMVSm+aw CClLVLzhg62n4JNxgolbgfLW5cnsnPk4IryhukM4KiKsJFbX+dIy7tDLIGXioSbuyVhQ v9hg==
MIME-Version: 1.0
Received: by 10.220.248.82 with SMTP id mf18mr10898880vcb.20.1343009835891; Sun, 22 Jul 2012 19:17:15 -0700 (PDT)
Received: by 10.58.117.34 with HTTP; Sun, 22 Jul 2012 19:17:15 -0700 (PDT)
In-Reply-To: <F4585D5C-5763-4759-AEA6-0E2B106CBC95@rob.sh>
References: <CAL9jLabOs02rOti4tezaZiHyiOD2f9vAhsoE9c-afFb4J1xYXQ@mail.gmail.com> <DCC302FAA9FE5F4BBA4DCAD46569377917449AF235@PRVPEXVS03.corp.twcable.com> <D05A81B4-1317-4C13-A2D6-05F5B41096CA@castlepoint.net> <09B801B2-B2AD-407F-B542-B02AEB997077@rob.sh> <F634202B-3380-4620-93FE-4291A08F04CA@castlepoint.net> <F4585D5C-5763-4759-AEA6-0E2B106CBC95@rob.sh>
Date: Sun, 22 Jul 2012 22:17:15 -0400
Message-ID: <CAL9jLaYK6jCKVkWEK3JAyiD8hxZbL_QjT0XvSZe=UfCYycLWgw@mail.gmail.com>
From: Christopher Morrow <christopher.morrow@gmail.com>
To: Rob Shakir <rjs@rob.sh>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "grow@ietf.org grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] WGLC: draft-ietf-grow-ops-reqs-for-bgp-error-handling-04
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, 23 Jul 2012 02:17:17 -0000

Rob,
Did you want to spin a new version of the draft and get final comments
from Shane? then move this along to IESG-land?

Or are there still comments/issues to deal with from other folk? (the
russ/robert discussion seemed to peter out as well)

-chris

On Wed, Jul 18, 2012 at 1:54 PM, Rob Shakir <rjs@rob.sh> wrote:
> Hi Shane,
>
> Thanks for the comments again, and apologies (again!) for the delay in re=
sponding.
>
> Please find my responses in-line as [rjs].
>
> On 11 Jul 2012, at 17:50, Shane Amante wrote:
>
>>>> [...snip...]
>>>
>>> [rjs]: I tried to add something to cover this that fits in with Section=
 1.1:
>>>
>>>                       <t>
>>>                           The combination of the increased number of de=
ployments of BGP-4 as an intra-AS routing protocol, its use for the propaga=
tion of additional types of routing and service information, and the growth=
 of IP services has resulted in a substantial increase in the volume of inf=
ormation carried within BGP-4. In numerous networks, RIB sizes of the order=
 of millions of entries exist, with particular high-scale points existing a=
t BGP speakers performing aggregation or functionality designed improve uti=
lisation of network resources (e.g., route reflector hierarchies). Whilst c=
learly an increase in the amount routing information carried in BGP results=
 in greater impact to services during failures, it is also critical to thei=
r recovery time. The increased time to compute new paths following a failur=
es and subsequently re-learn them following recoveries results in greater i=
mpact of failures within the protocol, and hence adds further weight to the=
 requirement to
>  avoid failures affecting all routing, or service, information carried vi=
a a particular adjacency. Whilst an argument could be made the convergence =
time of BGP-4 can be reduced through additional computational resource bein=
g deployed, it is notable that significant challenges continue to exist for=
 operators of scaling BGP-4, and hence mechanisms which improve the scalabi=
lity of the protocol are of particular note.
>>>                       </t>
>>
>>
>> The above looks good, but I've made some minor modifications.  See below=
.
>> ---snip---
>> The combination of the increased number of deployments of BGP-4 as an in=
tra-AS routing protocol, its use for the propagation of additional types of=
 routing and service information, and the growth of IP services has resulte=
d in a substantial increase in the volume of information carried within BGP=
-4. In numerous networks, RIB sizes of the order of millions of entries exi=
st within individual BGP speakers, with particularly high-scale points exhi=
bited at BGP speakers performing aggregation or functionality designed impr=
ove utilisation of network resources (e.g., route reflector hierarchies). W=
hilst clearly an increase in the amount routing information carried in BGP =
results in greater impact to services during failures, which is only amplif=
ied by a corresponding increase in recovery times. Following a failure, the=
re is a substantial recovery time to learn, compute and distribute new path=
s, which results in a greater observed impact to services affected, and hen=
ce adds further
>  weight to the requirement to avoid failures altogether or, at least, mit=
igate their impact to the narrowest scope possible, (e.g.: a specific NLRI)=
. Whilst an argument could be made that convergence time of BGP-4 could pot=
entially be reduced through deployment of additional computational resource=
, it is notable that solution is not necessarily straightforward from an im=
plementation or deployment point-of-view, (e.g.: scaling computation resour=
ces within a single address-family is difficult).  Thus, significant challe=
nges continue to exist for operators when scaling BGP-4 deployments, and he=
nce mechanisms which improve the scalability of BGP-4 are very important.
>> ---snip---
>
> [rjs]: Thanks, other than some minor editorial changes I adopted this par=
agraph -- it seems like a good hybrid.
>
>
>>>> [...snip...]
>>>
>>> [rjs]: I'm not quite clear on whether this gets the point across comple=
tely - do we think that it is just that things have become in the realm of =
provisioning activities, or rather is it that there are more and more funct=
ions that are overloading onto BGP. I agree that this sentence doesn't nece=
ssarily capture that - but do you think that it's the generic information t=
ransfer protocol between PEs, as well as replacing provisioning mechanisms?
>>
>> I believe that you are correct, and better off, in stating "more and mor=
e functions that are overloaded (sic) onto BGP".  Although, I'm not sure th=
at "overloaded" is an appropriate adjective.
>
> [rjs]: I guess there may be negative connotations of 'overloaded', I gues=
s what I really mean is maybe "layered" onto BGP -- poor wording perhaps.
>
>> The point I was trying to get at is as follows.  I think there's a conti=
nuum of information exchanged within BGP from real-time information (reacha=
bility) to less dynamic (perhaps, even static) information, with _examples_=
 of the latter being auto-discovery/provisioning use cases.  While traditio=
nal applications, such as vanilla Internet service for which BGP was origin=
ally designed, only fall into the "real-time information" category ... ther=
e are a lot of new(er) applications that do not fit "neatly" in a single ca=
tegory and, in fact, span the range of real-time to less dynamic categories=
 depending on which facet of a particular protocol you look at, (examples b=
eing: IPVPN, MVPN, VPLS-BGP, etc.).  Regardless, I don't think it's prudent=
 to make value judgements (particularly at this point in time when these pr=
otocols are already widely deployed and successful) as to the "correctness"=
 of these functions/services being in BGP, since that's bound to be very su=
bjective.  Rathe
>  r, we need to recognize the world for what it is today, which is why I t=
hink use of the word "overloaded" may be inappropriate.  Furthermore, I thi=
nk that talking about this in such a context is only recognizing a symptom =
(the more complex the system, the higher the probability is to introduce er=
rors), when in reality we should be trying to focus in on the root problem:=
 since we've put so many eggs in one basket, we need unnoticeable (or, fast=
er) recovery from errors that affect real-time, reachability information.
>
> [rjs]: Completely agree with this. I think my poor choice of wording perh=
aps portrayed my view as negative -- rather, the key point for me is that t=
he robustness and error handling that we are discussing here is designed wi=
th the vanilla Internet service as the baseline - and as we extend the prot=
ocol to different deployment cases (no judgement about the value of which i=
s made), then some of the initial assumptions perhaps don't hold true. I th=
ink this is in agreement with yourself, insofar that I think we would both =
assert that for the real-time information, potentially the behaviour requir=
ed in a number of areas of the protocol is not the same as the behaviour re=
quired for relatively static information.
>
>>>
>>> [rjs]: Yes - the intention is to define this based on the narrowest set=
 possible, the reason that I used this wording is that (in my view) this is=
 defined by the NLRI actually in the message (if there were differing path =
attributes for NLRI, then we expect that this is packed into a second UPDAT=
E message). Perhaps a hybrid of our wording would clarify this (unless you =
think the assertion above is erroneous?).
>>
>> I see your point now.  How about the following hybrid text?
>> ---snip---
>> ... it is a requirement of any enhanced error handling mechanism to cons=
train the error handling so that it is narrowly focused on the NLRI contain=
ed within the bad UPDATE message.
>> ---snip---
>
> [rjs]: Sure, this sounds good.
>
>>>> 3)  Section 2:
>>>> ---snip---
>>>> contained within the message.  Since in this case, the message
>>>> received from the remote peer is syntactically valid, it is
>>>> considered that such an UPDATE is indicative of erroneous data within
>>>> a path attribute.  [...]
>>>> ---snip---
>>>> s/path attribute/path attributes/
>>>
>>> [rjs]: Is the point here "one or more path attributes"? I'm not sure I =
quite understand the nit? :-)
>>
>> Yes, sorry: "one or more path attributes".  (My point was you can't pred=
ict, here anyway, that it will only a single path attribute that is a probl=
em.  Ideally, a more robust error-handling solution would not make such ass=
umptions :-).
>
> [rjs]: ACK, updated this to 'one or more' :-)
>
>>> Many thanks again for your comments - if you could cast your eyes over =
the above corrections, and let me know if you feel they're sufficient, that=
'd be fantastic.
>>
>> And, thank you Rob for your excellent work on this.
>
> [rjs]: No worries - I'll take a read through and submit an -05 of the dra=
ft that merges the edits we've discussed in this thread.
>
> Thanks again for the comments,
> r.
>
> _______________________________________________
> GROW mailing list
> GROW@ietf.org
> https://www.ietf.org/mailman/listinfo/grow

From rob.shakir@bt.com  Mon Jul 23 08:11:01 2012
Return-Path: <rob.shakir@bt.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 0F55C11E8091 for <grow@ietfa.amsl.com>; Mon, 23 Jul 2012 08:11:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.572
X-Spam-Level: 
X-Spam-Status: No, score=0.572 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FB_INCREASE_VOL=3.629, RCVD_IN_DNSWL_LOW=-1, SARE_MILLIONSOF=0.315, 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 LQC0ACorQnsF for <grow@ietfa.amsl.com>; Mon, 23 Jul 2012 08:10:59 -0700 (PDT)
Received: from smtpe1.intersmtp.com (smtp61.intersmtp.com [62.239.224.234]) by ietfa.amsl.com (Postfix) with ESMTP id 45EA211E808E for <grow@ietf.org>; Mon, 23 Jul 2012 08:10:59 -0700 (PDT)
Received: from EVMHT63-UKRD.domain1.systemhost.net (10.36.3.100) by RDW083A005ED61.smtp-e1.hygiene.service (10.187.98.10) with Microsoft SMTP Server (TLS) id 8.3.264.0; Mon, 23 Jul 2012 16:10:57 +0100
Received: from EVMHT01-UKBR.domain1.systemhost.net (193.113.108.42) by EVMHT63-UKRD.domain1.systemhost.net (10.36.3.100) with Microsoft SMTP Server (TLS) id 8.3.264.0; Mon, 23 Jul 2012 16:10:56 +0100
Received: from EMV02-UKBR.domain1.systemhost.net ([169.254.1.214]) by EVMHT01-UKBR.domain1.systemhost.net ([193.113.108.42]) with mapi; Mon, 23 Jul 2012 16:10:56 +0100
From: <rob.shakir@bt.com>
To: <christopher.morrow@gmail.com>, <rjs@rob.sh>
Date: Mon, 23 Jul 2012 16:08:53 +0100
Thread-Topic: [GROW] WGLC: draft-ietf-grow-ops-reqs-for-bgp-error-handling-04
Thread-Index: Ac1o5VwpHlLn6EJjTYesX4tQ7ZeKhQ==
Message-ID: <CC332685.44846%rob.shakir@bt.com>
In-Reply-To: <CAL9jLaYK6jCKVkWEK3JAyiD8hxZbL_QjT0XvSZe=UfCYycLWgw@mail.gmail.com>
Accept-Language: en-US, en-GB
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.1.120420
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: grow@ietf.org
Subject: Re: [GROW] WGLC: draft-ietf-grow-ops-reqs-for-bgp-error-handling-04
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, 23 Jul 2012 15:11:01 -0000

Hi Chris,

Sure - I will push an -05 version with the changes that were highlighted
this week (including integrating the changes that Shane and I discussed in
this thread). It would be great to progress this draft to the IESG
following this.

I don't believe that there are other comments to deal with. The discussion
between Russ and Robert did not relate to this draft (but was rather a
discussion of draft-white-grow-overlapping-routes-00 with the wrong
subject line).

Many thanks,
r.

On 23/07/2012 03:17, "Christopher Morrow" <christopher.morrow@gmail.com>
wrote:

>Rob,
>Did you want to spin a new version of the draft and get final comments
>from Shane? then move this along to IESG-land?
>
>Or are there still comments/issues to deal with from other folk? (the
>russ/robert discussion seemed to peter out as well)
>
>-chris
>
>On Wed, Jul 18, 2012 at 1:54 PM, Rob Shakir <rjs@rob.sh> wrote:
>> Hi Shane,
>>
>> Thanks for the comments again, and apologies (again!) for the delay in
>>responding.
>>
>> Please find my responses in-line as [rjs].
>>
>> On 11 Jul 2012, at 17:50, Shane Amante wrote:
>>
>>>>> [...snip...]
>>>>
>>>> [rjs]: I tried to add something to cover this that fits in with
>>>>Section 1.1:
>>>>
>>>>                       <t>
>>>>                           The combination of the increased number of
>>>>deployments of BGP-4 as an intra-AS routing protocol, its use for the
>>>>propagation of additional types of routing and service information,
>>>>and the growth of IP services has resulted in a substantial increase
>>>>in the volume of information carried within BGP-4. In numerous
>>>>networks, RIB sizes of the order of millions of entries exist, with
>>>>particular high-scale points existing at BGP speakers performing
>>>>aggregation or functionality designed improve utilisation of network
>>>>resources (e.g., route reflector hierarchies). Whilst clearly an
>>>>increase in the amount routing information carried in BGP results in
>>>>greater impact to services during failures, it is also critical to
>>>>their recovery time. The increased time to compute new paths following
>>>>a failures and subsequently re-learn them following recoveries results
>>>>in greater impact of failures within the protocol, and hence adds
>>>>further weight to the requirement to
>>  avoid failures affecting all routing, or service, information carried
>>via a particular adjacency. Whilst an argument could be made the
>>convergence time of BGP-4 can be reduced through additional
>>computational resource being deployed, it is notable that significant
>>challenges continue to exist for operators of scaling BGP-4, and hence
>>mechanisms which improve the scalability of the protocol are of
>>particular note.
>>>>                       </t>
>>>
>>>
>>> The above looks good, but I've made some minor modifications.  See
>>>below.
>>> ---snip---
>>> The combination of the increased number of deployments of BGP-4 as an
>>>intra-AS routing protocol, its use for the propagation of additional
>>>types of routing and service information, and the growth of IP services
>>>has resulted in a substantial increase in the volume of information
>>>carried within BGP-4. In numerous networks, RIB sizes of the order of
>>>millions of entries exist within individual BGP speakers, with
>>>particularly high-scale points exhibited at BGP speakers performing
>>>aggregation or functionality designed improve utilisation of network
>>>resources (e.g., route reflector hierarchies). Whilst clearly an
>>>increase in the amount routing information carried in BGP results in
>>>greater impact to services during failures, which is only amplified by
>>>a corresponding increase in recovery times. Following a failure, there
>>>is a substantial recovery time to learn, compute and distribute new
>>>paths, which results in a greater observed impact to services affected,
>>>and hence adds further
>>  weight to the requirement to avoid failures altogether or, at least,
>>mitigate their impact to the narrowest scope possible, (e.g.: a specific
>>NLRI). Whilst an argument could be made that convergence time of BGP-4
>>could potentially be reduced through deployment of additional
>>computational resource, it is notable that solution is not necessarily
>>straightforward from an implementation or deployment point-of-view,
>>(e.g.: scaling computation resources within a single address-family is
>>difficult).  Thus, significant challenges continue to exist for
>>operators when scaling BGP-4 deployments, and hence mechanisms which
>>improve the scalability of BGP-4 are very important.
>>> ---snip---
>>
>> [rjs]: Thanks, other than some minor editorial changes I adopted this
>>paragraph -- it seems like a good hybrid.
>>
>>
>>>>> [...snip...]
>>>>
>>>> [rjs]: I'm not quite clear on whether this gets the point across
>>>>completely - do we think that it is just that things have become in
>>>>the realm of provisioning activities, or rather is it that there are
>>>>more and more functions that are overloading onto BGP. I agree that
>>>>this sentence doesn't necessarily capture that - but do you think that
>>>>it's the generic information transfer protocol between PEs, as well as
>>>>replacing provisioning mechanisms?
>>>
>>> I believe that you are correct, and better off, in stating "more and
>>>more functions that are overloaded (sic) onto BGP".  Although, I'm not
>>>sure that "overloaded" is an appropriate adjective.
>>
>> [rjs]: I guess there may be negative connotations of 'overloaded', I
>>guess what I really mean is maybe "layered" onto BGP -- poor wording
>>perhaps.
>>
>>> The point I was trying to get at is as follows.  I think there's a
>>>continuum of information exchanged within BGP from real-time
>>>information (reachability) to less dynamic (perhaps, even static)
>>>information, with _examples_ of the latter being
>>>auto-discovery/provisioning use cases.  While traditional applications,
>>>such as vanilla Internet service for which BGP was originally designed,
>>>only fall into the "real-time information" category ... there are a lot
>>>of new(er) applications that do not fit "neatly" in a single category
>>>and, in fact, span the range of real-time to less dynamic categories
>>>depending on which facet of a particular protocol you look at,
>>>(examples being: IPVPN, MVPN, VPLS-BGP, etc.).  Regardless, I don't
>>>think it's prudent to make value judgements (particularly at this point
>>>in time when these protocols are already widely deployed and
>>>successful) as to the "correctness" of these functions/services being
>>>in BGP, since that's bound to be very subjective.  Rath
> e
>>  r, we need to recognize the world for what it is today, which is why I
>>think use of the word "overloaded" may be inappropriate.  Furthermore, I
>>think that talking about this in such a context is only recognizing a
>>symptom (the more complex the system, the higher the probability is to
>>introduce errors), when in reality we should be trying to focus in on
>>the root problem: since we've put so many eggs in one basket, we need
>>unnoticeable (or, faster) recovery from errors that affect real-time,
>>reachability information.
>>
>> [rjs]: Completely agree with this. I think my poor choice of wording
>>perhaps portrayed my view as negative -- rather, the key point for me is
>>that the robustness and error handling that we are discussing here is
>>designed with the vanilla Internet service as the baseline - and as we
>>extend the protocol to different deployment cases (no judgement about
>>the value of which is made), then some of the initial assumptions
>>perhaps don't hold true. I think this is in agreement with yourself,
>>insofar that I think we would both assert that for the real-time
>>information, potentially the behaviour required in a number of areas of
>>the protocol is not the same as the behaviour required for relatively
>>static information.
>>
>>>>
>>>> [rjs]: Yes - the intention is to define this based on the narrowest
>>>>set possible, the reason that I used this wording is that (in my view)
>>>>this is defined by the NLRI actually in the message (if there were
>>>>differing path attributes for NLRI, then we expect that this is packed
>>>>into a second UPDATE message). Perhaps a hybrid of our wording would
>>>>clarify this (unless you think the assertion above is erroneous?).
>>>
>>> I see your point now.  How about the following hybrid text?
>>> ---snip---
>>> ... it is a requirement of any enhanced error handling mechanism to
>>>constrain the error handling so that it is narrowly focused on the NLRI
>>>contained within the bad UPDATE message.
>>> ---snip---
>>
>> [rjs]: Sure, this sounds good.
>>
>>>>> 3)  Section 2:
>>>>> ---snip---
>>>>> contained within the message.  Since in this case, the message
>>>>> received from the remote peer is syntactically valid, it is
>>>>> considered that such an UPDATE is indicative of erroneous data within
>>>>> a path attribute.  [...]
>>>>> ---snip---
>>>>> s/path attribute/path attributes/
>>>>
>>>> [rjs]: Is the point here "one or more path attributes"? I'm not sure
>>>>I quite understand the nit? :-)
>>>
>>> Yes, sorry: "one or more path attributes".  (My point was you can't
>>>predict, here anyway, that it will only a single path attribute that is
>>>a problem.  Ideally, a more robust error-handling solution would not
>>>make such assumptions :-).
>>
>> [rjs]: ACK, updated this to 'one or more' :-)
>>
>>>> Many thanks again for your comments - if you could cast your eyes
>>>>over the above corrections, and let me know if you feel they're
>>>>sufficient, that'd be fantastic.
>>>
>>> And, thank you Rob for your excellent work on this.
>>
>> [rjs]: No worries - I'll take a read through and submit an -05 of the
>>draft that merges the edits we've discussed in this thread.
>>
>> Thanks again for the comments,
>> r.
>>
>> _______________________________________________
>> 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


From christopher.morrow@gmail.com  Mon Jul 23 11:15:48 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 23F7E11E80CE for <grow@ietfa.amsl.com>; Mon, 23 Jul 2012 11:15:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.056
X-Spam-Level: 
X-Spam-Status: No, score=-101.056 tagged_above=-999 required=5 tests=[AWL=-1.628, BAYES_00=-2.599, FB_INCREASE_VOL=3.629, RCVD_IN_DNSWL_LOW=-1, SARE_MILLIONSOF=0.315, 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 n7NVpt00NNJf for <grow@ietfa.amsl.com>; Mon, 23 Jul 2012 11:15:46 -0700 (PDT)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id A355211E80B5 for <grow@ietf.org>; Mon, 23 Jul 2012 11:15:46 -0700 (PDT)
Received: by vbbez10 with SMTP id ez10so5438932vbb.31 for <grow@ietf.org>; Mon, 23 Jul 2012 11:15:46 -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; bh=GI921mPMCWqPDW23QEPeOyxndtdr3/WRyTT+zRSGCbs=; b=BmhtDo5I1azb/73SEaqj/23aYR+oxO/bOhe542xbEmlQjKl3jDVCzIMfcLlKqY4p2z 1TQJPILbuRY7i3+TMh4ZPpeM0zkfc5WWux2fTnpm5kW4WcMK6F1EKLYZWBPCDQLYBfy8 GxB0DqtLr6jlNMXfSq0JncXzD8+ZD6RSBkipsmnnkwj3HHxR05I+Ec7BV47OGeEY4oFA u1IocBavZbBBDzY37aNmG9LwSB2DTVByreDARYDhRJReLA/sAVbWOB9PZI5PvfwwQcYW ZcHElzw3TAPrDJ3qx20aL+gXNBAz/BXYGXG9/vE5L3Ke9EECycDqyZsmzB6QHFaFKr8i hHDw==
MIME-Version: 1.0
Received: by 10.220.115.81 with SMTP id h17mr13192552vcq.66.1343067345964; Mon, 23 Jul 2012 11:15:45 -0700 (PDT)
Received: by 10.58.117.34 with HTTP; Mon, 23 Jul 2012 11:15:45 -0700 (PDT)
In-Reply-To: <CC332685.44846%rob.shakir@bt.com>
References: <CAL9jLaYK6jCKVkWEK3JAyiD8hxZbL_QjT0XvSZe=UfCYycLWgw@mail.gmail.com> <CC332685.44846%rob.shakir@bt.com>
Date: Mon, 23 Jul 2012 14:15:45 -0400
Message-ID: <CAL9jLab89Wz=-89Q0xZ7KdDQFqTS1Y-Tm7q-3RQRus3fv6_v5g@mail.gmail.com>
From: Christopher Morrow <christopher.morrow@gmail.com>
To: rob.shakir@bt.com
Content-Type: text/plain; charset=ISO-8859-1
Cc: grow@ietf.org
Subject: Re: [GROW] WGLC: draft-ietf-grow-ops-reqs-for-bgp-error-handling-04
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, 23 Jul 2012 18:15:48 -0000

On Mon, Jul 23, 2012 at 11:08 AM,  <rob.shakir@bt.com> wrote:
> Hi Chris,
>
> Sure - I will push an -05 version with the changes that were highlighted
> this week (including integrating the changes that Shane and I discussed in
> this thread). It would be great to progress this draft to the IESG
> following this.

sounds good to me, I think submissions may be blocked for a bit while
ietf-meeting-start happens... but once the new version goes in I'll
send (please ping me to remind me when it submits) iesg publication
requests out.

> I don't believe that there are other comments to deal with. The discussion
> between Russ and Robert did not relate to this draft (but was rather a
> discussion of draft-white-grow-overlapping-routes-00 with the wrong
> subject line).

ah, that was my feeling as well... go thread overlap!

-chris

>
> Many thanks,
> r.
>
> On 23/07/2012 03:17, "Christopher Morrow" <christopher.morrow@gmail.com>
> wrote:
>
>>Rob,
>>Did you want to spin a new version of the draft and get final comments
>>from Shane? then move this along to IESG-land?
>>
>>Or are there still comments/issues to deal with from other folk? (the
>>russ/robert discussion seemed to peter out as well)
>>
>>-chris
>>
>>On Wed, Jul 18, 2012 at 1:54 PM, Rob Shakir <rjs@rob.sh> wrote:
>>> Hi Shane,
>>>
>>> Thanks for the comments again, and apologies (again!) for the delay in
>>>responding.
>>>
>>> Please find my responses in-line as [rjs].
>>>
>>> On 11 Jul 2012, at 17:50, Shane Amante wrote:
>>>
>>>>>> [...snip...]
>>>>>
>>>>> [rjs]: I tried to add something to cover this that fits in with
>>>>>Section 1.1:
>>>>>
>>>>>                       <t>
>>>>>                           The combination of the increased number of
>>>>>deployments of BGP-4 as an intra-AS routing protocol, its use for the
>>>>>propagation of additional types of routing and service information,
>>>>>and the growth of IP services has resulted in a substantial increase
>>>>>in the volume of information carried within BGP-4. In numerous
>>>>>networks, RIB sizes of the order of millions of entries exist, with
>>>>>particular high-scale points existing at BGP speakers performing
>>>>>aggregation or functionality designed improve utilisation of network
>>>>>resources (e.g., route reflector hierarchies). Whilst clearly an
>>>>>increase in the amount routing information carried in BGP results in
>>>>>greater impact to services during failures, it is also critical to
>>>>>their recovery time. The increased time to compute new paths following
>>>>>a failures and subsequently re-learn them following recoveries results
>>>>>in greater impact of failures within the protocol, and hence adds
>>>>>further weight to the requirement to
>>>  avoid failures affecting all routing, or service, information carried
>>>via a particular adjacency. Whilst an argument could be made the
>>>convergence time of BGP-4 can be reduced through additional
>>>computational resource being deployed, it is notable that significant
>>>challenges continue to exist for operators of scaling BGP-4, and hence
>>>mechanisms which improve the scalability of the protocol are of
>>>particular note.
>>>>>                       </t>
>>>>
>>>>
>>>> The above looks good, but I've made some minor modifications.  See
>>>>below.
>>>> ---snip---
>>>> The combination of the increased number of deployments of BGP-4 as an
>>>>intra-AS routing protocol, its use for the propagation of additional
>>>>types of routing and service information, and the growth of IP services
>>>>has resulted in a substantial increase in the volume of information
>>>>carried within BGP-4. In numerous networks, RIB sizes of the order of
>>>>millions of entries exist within individual BGP speakers, with
>>>>particularly high-scale points exhibited at BGP speakers performing
>>>>aggregation or functionality designed improve utilisation of network
>>>>resources (e.g., route reflector hierarchies). Whilst clearly an
>>>>increase in the amount routing information carried in BGP results in
>>>>greater impact to services during failures, which is only amplified by
>>>>a corresponding increase in recovery times. Following a failure, there
>>>>is a substantial recovery time to learn, compute and distribute new
>>>>paths, which results in a greater observed impact to services affected,
>>>>and hence adds further
>>>  weight to the requirement to avoid failures altogether or, at least,
>>>mitigate their impact to the narrowest scope possible, (e.g.: a specific
>>>NLRI). Whilst an argument could be made that convergence time of BGP-4
>>>could potentially be reduced through deployment of additional
>>>computational resource, it is notable that solution is not necessarily
>>>straightforward from an implementation or deployment point-of-view,
>>>(e.g.: scaling computation resources within a single address-family is
>>>difficult).  Thus, significant challenges continue to exist for
>>>operators when scaling BGP-4 deployments, and hence mechanisms which
>>>improve the scalability of BGP-4 are very important.
>>>> ---snip---
>>>
>>> [rjs]: Thanks, other than some minor editorial changes I adopted this
>>>paragraph -- it seems like a good hybrid.
>>>
>>>
>>>>>> [...snip...]
>>>>>
>>>>> [rjs]: I'm not quite clear on whether this gets the point across
>>>>>completely - do we think that it is just that things have become in
>>>>>the realm of provisioning activities, or rather is it that there are
>>>>>more and more functions that are overloading onto BGP. I agree that
>>>>>this sentence doesn't necessarily capture that - but do you think that
>>>>>it's the generic information transfer protocol between PEs, as well as
>>>>>replacing provisioning mechanisms?
>>>>
>>>> I believe that you are correct, and better off, in stating "more and
>>>>more functions that are overloaded (sic) onto BGP".  Although, I'm not
>>>>sure that "overloaded" is an appropriate adjective.
>>>
>>> [rjs]: I guess there may be negative connotations of 'overloaded', I
>>>guess what I really mean is maybe "layered" onto BGP -- poor wording
>>>perhaps.
>>>
>>>> The point I was trying to get at is as follows.  I think there's a
>>>>continuum of information exchanged within BGP from real-time
>>>>information (reachability) to less dynamic (perhaps, even static)
>>>>information, with _examples_ of the latter being
>>>>auto-discovery/provisioning use cases.  While traditional applications,
>>>>such as vanilla Internet service for which BGP was originally designed,
>>>>only fall into the "real-time information" category ... there are a lot
>>>>of new(er) applications that do not fit "neatly" in a single category
>>>>and, in fact, span the range of real-time to less dynamic categories
>>>>depending on which facet of a particular protocol you look at,
>>>>(examples being: IPVPN, MVPN, VPLS-BGP, etc.).  Regardless, I don't
>>>>think it's prudent to make value judgements (particularly at this point
>>>>in time when these protocols are already widely deployed and
>>>>successful) as to the "correctness" of these functions/services being
>>>>in BGP, since that's bound to be very subjective.  Rath
>> e
>>>  r, we need to recognize the world for what it is today, which is why I
>>>think use of the word "overloaded" may be inappropriate.  Furthermore, I
>>>think that talking about this in such a context is only recognizing a
>>>symptom (the more complex the system, the higher the probability is to
>>>introduce errors), when in reality we should be trying to focus in on
>>>the root problem: since we've put so many eggs in one basket, we need
>>>unnoticeable (or, faster) recovery from errors that affect real-time,
>>>reachability information.
>>>
>>> [rjs]: Completely agree with this. I think my poor choice of wording
>>>perhaps portrayed my view as negative -- rather, the key point for me is
>>>that the robustness and error handling that we are discussing here is
>>>designed with the vanilla Internet service as the baseline - and as we
>>>extend the protocol to different deployment cases (no judgement about
>>>the value of which is made), then some of the initial assumptions
>>>perhaps don't hold true. I think this is in agreement with yourself,
>>>insofar that I think we would both assert that for the real-time
>>>information, potentially the behaviour required in a number of areas of
>>>the protocol is not the same as the behaviour required for relatively
>>>static information.
>>>
>>>>>
>>>>> [rjs]: Yes - the intention is to define this based on the narrowest
>>>>>set possible, the reason that I used this wording is that (in my view)
>>>>>this is defined by the NLRI actually in the message (if there were
>>>>>differing path attributes for NLRI, then we expect that this is packed
>>>>>into a second UPDATE message). Perhaps a hybrid of our wording would
>>>>>clarify this (unless you think the assertion above is erroneous?).
>>>>
>>>> I see your point now.  How about the following hybrid text?
>>>> ---snip---
>>>> ... it is a requirement of any enhanced error handling mechanism to
>>>>constrain the error handling so that it is narrowly focused on the NLRI
>>>>contained within the bad UPDATE message.
>>>> ---snip---
>>>
>>> [rjs]: Sure, this sounds good.
>>>
>>>>>> 3)  Section 2:
>>>>>> ---snip---
>>>>>> contained within the message.  Since in this case, the message
>>>>>> received from the remote peer is syntactically valid, it is
>>>>>> considered that such an UPDATE is indicative of erroneous data within
>>>>>> a path attribute.  [...]
>>>>>> ---snip---
>>>>>> s/path attribute/path attributes/
>>>>>
>>>>> [rjs]: Is the point here "one or more path attributes"? I'm not sure
>>>>>I quite understand the nit? :-)
>>>>
>>>> Yes, sorry: "one or more path attributes".  (My point was you can't
>>>>predict, here anyway, that it will only a single path attribute that is
>>>>a problem.  Ideally, a more robust error-handling solution would not
>>>>make such assumptions :-).
>>>
>>> [rjs]: ACK, updated this to 'one or more' :-)
>>>
>>>>> Many thanks again for your comments - if you could cast your eyes
>>>>>over the above corrections, and let me know if you feel they're
>>>>>sufficient, that'd be fantastic.
>>>>
>>>> And, thank you Rob for your excellent work on this.
>>>
>>> [rjs]: No worries - I'll take a read through and submit an -05 of the
>>>draft that merges the edits we've discussed in this thread.
>>>
>>> Thanks again for the comments,
>>> r.
>>>
>>> _______________________________________________
>>> 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
>

From Internet-Drafts@ietf.org  Mon Jul 30 10:32:19 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 C3F4411E8176; Mon, 30 Jul 2012 10:32:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.572
X-Spam-Level: 
X-Spam-Status: No, score=-102.572 tagged_above=-999 required=5 tests=[AWL=0.027, 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 rzt06QF1aSEq; Mon, 30 Jul 2012 10:32:19 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 350A411E8172; Mon, 30 Jul 2012 10:32:19 -0700 (PDT)
MIME-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.32
Message-ID: <20120730173219.25944.66973.idtracker@ietfa.amsl.com>
Date: Mon, 30 Jul 2012 10:32:19 -0700
Cc: grow@ietf.org
Subject: [GROW] I-D ACTION:draft-ietf-grow-private-ip-sp-cores-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, 30 Jul 2012 17:32:19 -0000

--NextPart

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)     : A. Kirkham
    Filename      : draft-ietf-grow-private-ip-sp-cores
    Pages         : 15 
    Date          : July 30, 2012 
    
   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-06.txt

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

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-grow-private-ip-sp-cores"; site="ftp.ietf.org";
	access-type="anon-ftp"; directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2012-07-30103219.I-D@ietf.org>


--NextPart--

From internet-drafts@ietf.org  Mon Jul 30 11:17:52 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 3D41921F85AC; Mon, 30 Jul 2012 11:17:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.486
X-Spam-Level: 
X-Spam-Status: No, score=-102.486 tagged_above=-999 required=5 tests=[AWL=-0.114, 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 4XvsEBXAclU4; Mon, 30 Jul 2012 11:17:51 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B57621F855B; Mon, 30 Jul 2012 11:17:51 -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.32
Message-ID: <20120730181751.8976.97374.idtracker@ietfa.amsl.com>
Date: Mon, 30 Jul 2012 11:17:51 -0700
Cc: grow@ietf.org
Subject: [GROW] I-D Action: draft-ietf-grow-ops-reqs-for-bgp-error-handling-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: Mon, 30 Jul 2012 18:17:52 -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 Group o=
f the IETF.

	Title           : Operational Requirements for Enhanced Error Handling Beh=
aviour in BGP-4
	Author(s)       : Rob Shakir
	Filename        : draft-ietf-grow-ops-reqs-for-bgp-error-handling-05.txt
	Pages           : 30
	Date            : 2012-07-30

Abstract:
   BGP-4 is utilised as a key intra- and inter-Autonomous System routing
   protocol in modern IP networks.  The failure modes as defined by the
   original protocol standards are based on a number of assumptions
   around the impact of session failure.  Numerous incidents both in the
   global Internet routing table and within Service Provider networks
   have been caused by strict handling of a single invalid UPDATE
   message causing large-scale failures in one or more Autonomous
   Systems.

   This memo describes the current use of BGP-4 within Service Provider
   networks, and outlines a set of requirements for further work to
   enhance the mechanisms available to a BGP-4 implementation when
   erroneous data is detected.  Whilst this document does not provide
   specification of any standard, it is intended as an overview of a set
   of enhancements to BGP-4 to improve the protocol's robustness to suit
   its current deployment.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-grow-ops-reqs-for-bgp-error-han=
dling

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-grow-ops-reqs-for-bgp-error-handling-=
05

A diff from previous version is available at:
http://tools.ietf.org/rfcdiff?url2=3Ddraft-ietf-grow-ops-reqs-for-bgp-error=
-handling-05


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


From internet-drafts@ietf.org  Mon Jul 30 14:38:24 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 02ED211E8166; Mon, 30 Jul 2012 14:38:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.56
X-Spam-Level: 
X-Spam-Status: No, score=-102.56 tagged_above=-999 required=5 tests=[AWL=0.039, 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 l+mwCfiKTUIw; Mon, 30 Jul 2012 14:38:23 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8292311E812C; Mon, 30 Jul 2012 14:38:23 -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.32
Message-ID: <20120730213823.24169.88284.idtracker@ietfa.amsl.com>
Date: Mon, 30 Jul 2012 14:38:23 -0700
Cc: grow@ietf.org
Subject: [GROW] I-D Action: draft-ietf-grow-private-ip-sp-cores-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, 30 Jul 2012 21:38:24 -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 Group o=
f the IETF.

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

Abstract:
   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.


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

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-grow-private-ip-sp-cores-07

A diff from previous version is available at:
http://tools.ietf.org/rfcdiff?url2=3Ddraft-ietf-grow-private-ip-sp-cores-07


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


From christopher.morrow@gmail.com  Tue Jul 31 09:13:10 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 EE96C21F86B8 for <grow@ietfa.amsl.com>; Tue, 31 Jul 2012 09:13:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.025
X-Spam-Level: 
X-Spam-Status: No, score=-103.025 tagged_above=-999 required=5 tests=[AWL=0.574, 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 byZwSmQwhZEw for <grow@ietfa.amsl.com>; Tue, 31 Jul 2012 09:13:09 -0700 (PDT)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id D4F2821F86BE for <grow@ietf.org>; Tue, 31 Jul 2012 09:13:08 -0700 (PDT)
Received: by vbbez10 with SMTP id ez10so6427628vbb.31 for <grow@ietf.org>; Tue, 31 Jul 2012 09:13:08 -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=OYyzFnOuGl3ZE7WQsuq79mArU36kSX1drsJx4fQ0v/w=; b=gtY6oIqg0fD/F/b435OblhhahdtBXfYe7zZd26ex8ZLkFfTVAjWNjLFiyqfLex6ArG IlQh4VyUACkaV2CxoQv+ZFjyABVezS55l+wIUJnil0EQwsdmUaMXcMG7j5F4LkjXk63f 41dSY/xxn2xucJYp0DOc0U2sAtvBAT0uRRbTUA641kr0fPZV0AewT2+DMg8E9HTThK4w Dt9xebClbLw1W9aW4cTTUMJ7ggFe9FxiRvyu+1KpNwcmWgz7cmnFgt1quR1V7Z67Vwba 9pbjQXzBsxqRmNpKxhh0dDlVArZ265M4mO8Q1kf0fY+tohFoUzpJVJUuR/y0EGUCIEsR g+YA==
MIME-Version: 1.0
Received: by 10.52.73.42 with SMTP id i10mr12706123vdv.116.1343751188363; Tue, 31 Jul 2012 09:13:08 -0700 (PDT)
Received: by 10.58.117.34 with HTTP; Tue, 31 Jul 2012 09:13:08 -0700 (PDT)
Date: Tue, 31 Jul 2012 12:13:08 -0400
Message-ID: <CAL9jLaY2FtacjJ3_+g=dnfZ=aZtAVvgRj=32+jxvGB3HK1cY7Q@mail.gmail.com>
From: Christopher Morrow <christopher.morrow@gmail.com>
To: grow-chairs@tools.ietf.org, "grow@ietf.org grow@ietf.org" <grow@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Subject: [GROW] Call for Adoption: draft-white-grow-overlapping-routes
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, 31 Jul 2012 16:13:10 -0000

As per the meeting moments ago, could we discuss adopting this draft:
  <http://tools.ietf.org/html/draft-white-grow-overlapping-routes-00>

as a GROW working group item? Let's call the call on my birthday:
08/14/2012 or August 14, 2012.

thanks!
-chris
(co-chair)

From ttauber@1-4-5.net  Tue Jul 31 10:31:16 2012
Return-Path: <ttauber@1-4-5.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 33E8221F874A for <grow@ietfa.amsl.com>; Tue, 31 Jul 2012 10:31:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.843
X-Spam-Level: 
X-Spam-Status: No, score=-101.843 tagged_above=-999 required=5 tests=[AWL=1.133, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, 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 bW0M0AOeM-9h for <grow@ietfa.amsl.com>; Tue, 31 Jul 2012 10:31:15 -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 6B66821F8746 for <grow@ietf.org>; Tue, 31 Jul 2012 10:31:15 -0700 (PDT)
Received: by obbwc20 with SMTP id wc20so12441888obb.31 for <grow@ietf.org>; Tue, 31 Jul 2012 10:31:15 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=Qo9A8hrgvtD9/O+07aYHbFtGIFG4Og5IiiXwZn0F/po=; b=Sbg4uUjE4A9OOy9vq0oZ1y6HoVqeN7K3qOmQ7DbtvxBew8I69VKqKTEtEf0+oUGyQv oLf/+9WAReGPGhfLa47cCjM11kI2bgxD3ogZM4Su+hgjWrwAFuuQSnIFUoXUNkCy5Hw4 s6LE2KloLER8q28R4Rz56LFqxNMwbBSwuVIJB6oQTEDWUe3zP5/ops5qwkPrUDoeHXg4 RBXSdFmzHHwm04Lgz8Modj5jx/EXM/geXrID5LCt/ddO+ulLnCooT+n3CZ8jTut5MJN6 b+al61U7iyFnq+BEZvEdbMcgrK1t67ImjwsDsc4m4sIiKhYH6rgYbOYgmVGtYovVOun6 DlUQ==
MIME-Version: 1.0
Received: by 10.182.49.7 with SMTP id q7mr24587921obn.68.1343755874932; Tue, 31 Jul 2012 10:31:14 -0700 (PDT)
Received: by 10.76.10.6 with HTTP; Tue, 31 Jul 2012 10:31:14 -0700 (PDT)
X-Originating-IP: [24.104.152.66]
In-Reply-To: <CAL9jLaY2FtacjJ3_+g=dnfZ=aZtAVvgRj=32+jxvGB3HK1cY7Q@mail.gmail.com>
References: <CAL9jLaY2FtacjJ3_+g=dnfZ=aZtAVvgRj=32+jxvGB3HK1cY7Q@mail.gmail.com>
Date: Tue, 31 Jul 2012 13:31:14 -0400
Message-ID: <CAGQUKccY6ASakCXOm4WcDaAfEpuFwwdGv6Ee1Yrb_ZzO86H9Rw@mail.gmail.com>
From: Tony Tauber <ttauber@1-4-5.net>
To: Christopher Morrow <christopher.morrow@gmail.com>
Content-Type: multipart/alternative; boundary=f46d044786fd97190e04c6238b70
X-Gm-Message-State: ALoCoQne6kGJ9R4wUcfeOEEQpx/5tQC6fwcJZerWPzEoeTGK9zfLXbStq+GZPuUJX8+743DIcveJ
Cc: "grow@ietf.org grow@ietf.org" <grow@ietf.org>, grow-chairs@tools.ietf.org
Subject: Re: [GROW] Call for Adoption: draft-white-grow-overlapping-routes
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, 31 Jul 2012 17:31:16 -0000

--f46d044786fd97190e04c6238b70
Content-Type: text/plain; charset=ISO-8859-1

Quick question.  To my understanding "overlapping routes" seem to be what
most people call more-specific routes (aka. "more-specifics").

In my experience things which are described as overlapping mean that some
part of one thing is _partially_ covered by some part of some other thing.
I don't see how what's commonly known as a "covering" route in the draft
and in current usage is _partially_ covering what's underneath.

Am I missing something?  If so, why introduce some new terminology?

Tony

On Tue, Jul 31, 2012 at 12:13 PM, Christopher Morrow <
christopher.morrow@gmail.com> wrote:

> As per the meeting moments ago, could we discuss adopting this draft:
>   <http://tools.ietf.org/html/draft-white-grow-overlapping-routes-00>
>
> as a GROW working group item? Let's call the call on my birthday:
> 08/14/2012 or August 14, 2012.
>
> thanks!
> -chris
> (co-chair)
> _______________________________________________
> GROW mailing list
> GROW@ietf.org
> https://www.ietf.org/mailman/listinfo/grow
>

--f46d044786fd97190e04c6238b70
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Quick question.=A0 To my understanding &quot;overlapping routes&quot; seem =
to be what most people call more-specific routes (aka. &quot;more-specifics=
&quot;).<br><br>In my experience things which are described as overlapping =
mean that some part of one thing is _partially_ covered by some part of som=
e other thing.<br>
I don&#39;t see how what&#39;s commonly known as a &quot;covering&quot; rou=
te in the draft and in current usage is _partially_ covering what&#39;s und=
erneath.<br><br>Am I missing something?=A0 If so, why introduce some new te=
rminology?<br>
<br>Tony<br><br><div class=3D"gmail_quote">On Tue, Jul 31, 2012 at 12:13 PM=
, Christopher Morrow <span dir=3D"ltr">&lt;<a href=3D"mailto:christopher.mo=
rrow@gmail.com" target=3D"_blank">christopher.morrow@gmail.com</a>&gt;</spa=
n> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">As per the meeting moments ago, could we dis=
cuss adopting this draft:<br>
=A0 &lt;<a href=3D"http://tools.ietf.org/html/draft-white-grow-overlapping-=
routes-00" target=3D"_blank">http://tools.ietf.org/html/draft-white-grow-ov=
erlapping-routes-00</a>&gt;<br>
<br>
as a GROW working group item? Let&#39;s call the call on my birthday:<br>
08/14/2012 or August 14, 2012.<br>
<br>
thanks!<br>
-chris<br>
(co-chair)<br>
_______________________________________________<br>
GROW mailing list<br>
<a href=3D"mailto:GROW@ietf.org">GROW@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/grow" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/grow</a><br>
</blockquote></div><br>

--f46d044786fd97190e04c6238b70--

From internet-drafts@ietf.org  Tue Jul 31 15:33:58 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 97D0911E8126; Tue, 31 Jul 2012 15:33:58 -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=[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 fS+7sp7h7iwr; Tue, 31 Jul 2012 15:33:58 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E0ABA11E8121; Tue, 31 Jul 2012 15:33:57 -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.33
Message-ID: <20120731223357.13543.68607.idtracker@ietfa.amsl.com>
Date: Tue, 31 Jul 2012 15:33:57 -0700
Cc: grow@ietf.org
Subject: [GROW] I-D Action: draft-ietf-grow-diverse-bgp-path-dist-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, 31 Jul 2012 22:33:58 -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 Group o=
f 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-08.txt
	Pages           : 23
	Date            : 2012-07-31

Abstract:
   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.

   The main objective of this document is to observe that by simply
   adding new session between route reflector and it's client Nth best
   path can be distributed.  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 software upgrade of provider edge
   routers acting as route reflector clients.


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

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-grow-diverse-bgp-path-dist-08

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-grow-diverse-bgp-path-dist-08


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


From internet-drafts@ietf.org  Tue Jul 31 15:59:19 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 AC28111E8161; Tue, 31 Jul 2012 15:59:19 -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 foRRmLwPtiE9; Tue, 31 Jul 2012 15:59:19 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0363411E8153; Tue, 31 Jul 2012 15:59:19 -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.33
Message-ID: <20120731225919.4286.75229.idtracker@ietfa.amsl.com>
Date: Tue, 31 Jul 2012 15:59:19 -0700
Cc: grow@ietf.org
Subject: [GROW] I-D Action: draft-ietf-grow-simple-va-11.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, 31 Jul 2012 22:59:19 -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 Group o=
f 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-11.txt
	Pages           : 9
	Date            : 2012-07-31

Abstract:
   All BGP routers in the Default Free Zone (DFZ) are required to carry
   all the routes in the Default Free Routing Table (DFRT).  A technique
   is described that allows some BGP routers not to install all of those
   routes into the Forwarding Information Base (FIB).

   Some routers in an Autonomous System (AS) announce an aggregate (the
   VA prefix) in addition to the routes they already announce.  This
   enables other routers not to install the routes covered by the VA
   prefix into the FIB as long as those routes have the same next-hop as
   the VA prefix.

   The VA prefixes that are announced within an AS are not announced to
   any other AS.  In contrast to VA, S-VA reduces operational complexity
   by proposing local to given BGP speaker solution without any
   dependency on network wide configuration or requires presence of any
   form of intra-domain tunneling.


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

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-grow-simple-va-11

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-grow-simple-va-11


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

