
From roland.dobbins@gmail.com  Wed Aug  1 05:14:16 2012
Return-Path: <roland.dobbins@gmail.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D6CAE21F8AA8 for <grow@ietfa.amsl.com>; Wed,  1 Aug 2012 05:14:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EHmkL1BVlTbr for <grow@ietfa.amsl.com>; Wed,  1 Aug 2012 05:14:15 -0700 (PDT)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by ietfa.amsl.com (Postfix) with ESMTP id A77F121F8ABF for <grow@ietf.org>; Wed,  1 Aug 2012 05:14:15 -0700 (PDT)
Received: by yenq13 with SMTP id q13so7783509yen.31 for <grow@ietf.org>; Wed, 01 Aug 2012 05:14:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to:x-mailer; bh=ocEj7dGKL9wCb0zjAav8+yCP8TNnBejf3G4Tgzx161k=; b=DRaFnaFqWwGBq414ZOnvX5Eb2jpTn3NCn5AEZT7S5PAbJtnV5KEvXAOsMYL8g8Kex9 VrQEtcF+Viq5dUdGqIcgmqpElvFOqcrYijss2PN+UsmA2PMhXYwJD0Pr9zNztfTl4fWM 0oWgqOtxeKAwSmvlQS00ktYV6SQLuXf0DilEBKrKO2TRU1ICd1xpy7a7IrH8oOIn5Kl7 MmZ9+Oxx/aScmmp9RD82Q3MH4Bte3VRmbBycQUUExPWDLJmM6f5qcirrfi40ph0JNoul ZnCD/OmR9yZelyJAi+EilDywEnDuknmm+bcO6eqd0rxnYJ4OvLAOttHrDLAMlo5KqLhw 9N2g==
Received: by 10.66.84.130 with SMTP id z2mr39496560pay.77.1343823254887; Wed, 01 Aug 2012 05:14:14 -0700 (PDT)
Received: from [10.50.145.26] (61-91-65-157.static.asianet.co.th. [61.91.65.157]) by mx.google.com with ESMTPS id qr2sm2497536pbc.44.2012.08.01.05.14.11 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 01 Aug 2012 05:14:14 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1278)
From: Roland Dobbins <roland.dobbins@gmail.com>
In-Reply-To: <20120731223357.13543.68607.idtracker@ietfa.amsl.com>
Date: Wed, 1 Aug 2012 19:14:07 +0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <90D4C64D-0685-4F2D-BEC6-0C5DCB0231AF@gmail.com>
References: <20120731223357.13543.68607.idtracker@ietfa.amsl.com>
To: "grow@ietf.org grow@ietf.org" <grow@ietf.org>
X-Mailer: Apple Mail (2.1278)
Subject: Re: [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: Wed, 01 Aug 2012 12:14:17 -0000

On Aug 1, 2012, at 5:33 AM, Internet-Drafts@ietf.org wrote:

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

Should probably read something like this:

  The main objective of this document is to observe that by simply
  adding new sessions between a route reflector and its clients, =
multiple=20
  paths for a given prefix can in fact be distributed via BGP4.  This =
document=20
  also compares existing solutions and proposed ideas that enable =
distribution=20
  of more paths than solely the best path.=

From iesg-secretary@ietf.org  Wed Aug  8 14:30: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 0E70B11E812C; Wed,  8 Aug 2012 14:30:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.558
X-Spam-Level: 
X-Spam-Status: No, score=-102.558 tagged_above=-999 required=5 tests=[AWL=0.041, 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 FTjPcUMst4yB; Wed,  8 Aug 2012 14:30:52 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9842911E8131; Wed,  8 Aug 2012 14:30:51 -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.33
Message-ID: <20120808213051.1127.15823.idtracker@ietfa.amsl.com>
Date: Wed, 08 Aug 2012 14:30:51 -0700
Cc: grow mailing list <grow@ietf.org>, grow chair <grow-chairs@tools.ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>
Subject: [GROW] Document Action: 'Issues with Private IP Addressing in the Internet'	to Informational RFC (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: Wed, 08 Aug 2012 21:30:53 -0000

The IESG has approved the following document:
- 'Issues with Private IP Addressing in the Internet'
  (draft-ietf-grow-private-ip-sp-cores-07.txt) as Informational RFC

This document is the product of the Global Routing Operations Working
Group.

The IESG contact persons are Ronald Bonica and Benoit Claise.

A URL of this Internet Draft is:
http://datatracker.ietf.org/doc/draft-ietf-grow-private-ip-sp-cores/




Technical Summary

   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 recognized within the ISP
   community, there appears to be no document that collectively
   describes the issues.

Working Group Summary

This document had extensive review through the wg process. I believe there was good discussion about merits, improvements and polishing for this document, I believe the WG consensus long ago that this document is ready for publication.


Document Quality

This document aims to outline the pitfalls with certain implementation choices in building/operating a network which is to be part of the larger public Internet. It is a good, solid document.


Personnel

The document shepherd is myself (Chris Morrow), the responsible Area Director is:
  Ron Bonica


RFC Editor Note

Please removed the unused references to   'RFC1393' and RFC 792

From ietfc@btconnect.com  Thu Aug  9 01:27:32 2012
Return-Path: <ietfc@btconnect.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C82BD21F86E4 for <grow@ietfa.amsl.com>; Thu,  9 Aug 2012 01:27:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.038
X-Spam-Level: 
X-Spam-Status: No, score=-3.038 tagged_above=-999 required=5 tests=[AWL=-0.731, BAYES_00=-2.599, MISSING_HEADERS=1.292, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mMj3eq7QvOxv for <grow@ietfa.amsl.com>; Thu,  9 Aug 2012 01:27:32 -0700 (PDT)
Received: from co1outboundpool.messaging.microsoft.com (co1ehsobe005.messaging.microsoft.com [216.32.180.188]) by ietfa.amsl.com (Postfix) with ESMTP id 3B03E21F86E3 for <grow@ietf.org>; Thu,  9 Aug 2012 01:27:32 -0700 (PDT)
Received: from mail81-co1-R.bigfish.com (10.243.78.225) by CO1EHSOBE015.bigfish.com (10.243.66.78) with Microsoft SMTP Server id 14.1.225.23; Thu, 9 Aug 2012 08:27:31 +0000
Received: from mail81-co1 (localhost [127.0.0.1])	by mail81-co1-R.bigfish.com (Postfix) with ESMTP id 817311C02C8	for <grow@ietf.org>; Thu,  9 Aug 2012 08:27:31 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.55.224.141; KIP:(null); UIP:(null); IPV:NLI; H:DB3PRD0702HT004.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -23
X-BigFish: PS-23(zz9371I542M1432Izz1202hzz1033IL8275dhz2dh2a8h5a9h668h839hd24hf0ah107ah304l)
Received: from mail81-co1 (localhost.localdomain [127.0.0.1]) by mail81-co1 (MessageSwitch) id 134450084982168_17676; Thu,  9 Aug 2012 08:27:29 +0000 (UTC)
Received: from CO1EHSMHS028.bigfish.com (unknown [10.243.78.243])	by mail81-co1.bigfish.com (Postfix) with ESMTP id 12903200057	for <grow@ietf.org>; Thu,  9 Aug 2012 08:27:29 +0000 (UTC)
Received: from DB3PRD0702HT004.eurprd07.prod.outlook.com (157.55.224.141) by CO1EHSMHS028.bigfish.com (10.243.66.38) with Microsoft SMTP Server (TLS) id 14.1.225.23; Thu, 9 Aug 2012 08:27:28 +0000
Received: from AMSPRD0510HT002.eurprd05.prod.outlook.com (157.56.248.53) by pod51017.outlook.com (10.3.4.154) with Microsoft SMTP Server (TLS) id 14.15.108.4; Thu, 9 Aug 2012 08:27:19 +0000
Message-ID: <00fd01cd7608$2aae62e0$4001a8c0@gateway.2wire.net>
From: t.petch <ietfc@btconnect.com>
CC: grow mailing list <grow@ietf.org>
References: <20120808213051.1127.15823.idtracker@ietfa.amsl.com>
Date: Thu, 9 Aug 2012 09:22:25 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [157.56.248.53]
X-OriginatorOrg: btconnect.com
Subject: Re: [GROW] Document Action: 'Issues with Private IP Addressing in theInternet'	to Informational RFC(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: Thu, 09 Aug 2012 08:27:32 -0000

Yippee!

Well done everyone (including a little bit of myself)

Tom Petch


----- Original Message -----
From: "The IESG" <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
Cc: "grow mailing list" <grow@ietf.org>; "grow chair"
<grow-chairs@tools.ietf.org>; "RFC Editor" <rfc-editor@rfc-editor.org>
Sent: Wednesday, August 08, 2012 10:30 PM
> The IESG has approved the following document:
> - 'Issues with Private IP Addressing in the Internet'
>   (draft-ietf-grow-private-ip-sp-cores-07.txt) as Informational RFC
>
> This document is the product of the Global Routing Operations Working
> Group.
>
> The IESG contact persons are Ronald Bonica and Benoit Claise.
>
> A URL of this Internet Draft is:
> http://datatracker.ietf.org/doc/draft-ietf-grow-private-ip-sp-cores/
>
> Technical Summary
>
>    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 recognized within the ISP
>    community, there appears to be no document that collectively
>    describes the issues.
>
> Working Group Summary
>
> This document had extensive review through the wg process. I believe
there was good discussion about merits, improvements and polishing for
this document, I believe the WG consensus long ago that this document is
ready for publication.
>
>
> Document Quality
>
> This document aims to outline the pitfalls with certain implementation
choices in building/operating a network which is to be part of the
larger public Internet. It is a good, solid document.
>
>
> Personnel
>
> The document shepherd is myself (Chris Morrow), the responsible Area
Director is:
>   Ron Bonica
>
>
> RFC Editor Note
>
> Please removed the unused references to   'RFC1393' and RFC 792
> _______________________________________________
> GROW mailing list
> GROW@ietf.org
> https://www.ietf.org/mailman/listinfo/grow
>



From internet-drafts@ietf.org  Thu Aug 16 12:28:22 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 031C921F85FF; Thu, 16 Aug 2012 12:28:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.437
X-Spam-Level: 
X-Spam-Status: No, score=-102.437 tagged_above=-999 required=5 tests=[AWL=0.162, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IVi3savcRORE; Thu, 16 Aug 2012 12:28:21 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D8E621F859F; Thu, 16 Aug 2012 12:28:21 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.33
Message-ID: <20120816192821.7123.24348.idtracker@ietfa.amsl.com>
Date: Thu, 16 Aug 2012 12:28:21 -0700
Cc: grow@ietf.org
Subject: [GROW] I-D Action: draft-ietf-grow-simple-va-12.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, 16 Aug 2012 19:28:22 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.
 This draft is a work item of the Global Routing Operations Working 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-12.txt
	Pages           : 9
	Date            : 2012-08-16

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.  Described functionality is of very low operational
   complexity by proposing a confined BGP speaker solution without any
   dependency on network wide configuration or requirement for 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-12

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


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


From iesg-secretary@ietf.org  Tue Aug 21 08:31:01 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 0E2EF21F876E; Tue, 21 Aug 2012 08:31:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.53
X-Spam-Level: 
X-Spam-Status: No, score=-102.53 tagged_above=-999 required=5 tests=[AWL=0.069, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9otRw3X4T3Rp; Tue, 21 Aug 2012 08:31:00 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3B8AC21F8776; Tue, 21 Aug 2012 08:31:00 -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.33
Message-ID: <20120821153100.10327.98458.idtracker@ietfa.amsl.com>
Date: Tue, 21 Aug 2012 08:31:00 -0700
Cc: grow mailing list <grow@ietf.org>, grow chair <grow-chairs@tools.ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>
Subject: [GROW] Document Action: 'Simple Virtual Aggregation (S-VA)' to Informational	RFC (draft-ietf-grow-simple-va-12.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, 21 Aug 2012 15:31:01 -0000

The IESG has approved the following document:
- 'Simple Virtual Aggregation (S-VA)'
  (draft-ietf-grow-simple-va-12.txt) as Informational RFC

This document is the product of the Global Routing Operations Working
Group.

The IESG contact persons are Ronald Bonica and Benoit Claise.

A URL of this Internet Draft is:
http://datatracker.ietf.org/doc/draft-ietf-grow-simple-va/




Technical Summary

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

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

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

Working Group Summary

   This document was last called in 2011, went dormant for many months, 
   and last called again in May 2012. Last call   comments were positive, 
   but resulted in a new draft version.

Document Quality

  The author states that his employer has deployed the draft. 

Personnel

  Chris Morrow is shepherd. Ron Bonica is AD.

From iesg-secretary@ietf.org  Wed Aug 22 08:09:27 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 CD0E521F84D4; Wed, 22 Aug 2012 08:09:27 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lp-bdJrro+wy; Wed, 22 Aug 2012 08:09:27 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1611421F8672; Wed, 22 Aug 2012 08:09:27 -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.33
Message-ID: <20120822150927.12394.96217.idtracker@ietfa.amsl.com>
Date: Wed, 22 Aug 2012 08:09:27 -0700
Cc: grow mailing list <grow@ietf.org>, grow chair <grow-chairs@tools.ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>
Subject: [GROW] Document Action: 'Distribution of diverse BGP paths.' to	Informational RFC (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: Wed, 22 Aug 2012 15:09:28 -0000

The IESG has approved the following document:
- 'Distribution of diverse BGP paths.'
  (draft-ietf-grow-diverse-bgp-path-dist-08.txt) as Informational RFC

This document is the product of the Global Routing Operations Working
Group.

The IESG contact persons are Ronald Bonica and Benoit Claise.

A URL of this Internet Draft is:
http://datatracker.ietf.org/doc/draft-ietf-grow-diverse-bgp-path-dist/




Technical Summary

   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.

Working Group Summary

The draft was well supported in the working group, with active conversation
on the mailing list.  Numerous people contributed and commented on the draft
as part of the process. 

Document Quality

The document has had contribution from both vendors, researchers and 
operators.  The proposal does not require any changed to the BGP protocol,
but does require an implementation of the functionality specified.

Personnel

Document Shepherd -- Peter Schoenmaker <pds@lugs.com>
Area Directory -- Ron Bonica <rbonica@juniper.net>

From pds@lugs.com  Wed Aug 22 22:45:00 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 D52D921F8458 for <grow@ietfa.amsl.com>; Wed, 22 Aug 2012 22:45:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.44
X-Spam-Level: 
X-Spam-Status: No, score=-99.44 tagged_above=-999 required=5 tests=[AWL=-0.652, BAYES_40=-0.185, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lIAiGxkcAgXA for <grow@ietfa.amsl.com>; Wed, 22 Aug 2012 22:45:00 -0700 (PDT)
Received: from murdock.lugs.com (murdock.lugs.com [192.80.15.4]) by ietfa.amsl.com (Postfix) with ESMTP id 7154E21F8450 for <grow@ietf.org>; Wed, 22 Aug 2012 22:45:00 -0700 (PDT)
Received: from [172.31.255.126] (unknown [202.55.50.51]) by murdock.lugs.com (Postfix) with ESMTPSA id 80974D35BE for <grow@ietf.org>; Thu, 23 Aug 2012 01:44:58 -0400 (EDT)
User-Agent: Microsoft-MacOutlook/14.2.3.120616
Date: Thu, 23 Aug 2012 13:44:47 +0800
From: Peter Schoenmaker <pds@lugs.com>
To: "grow@ietf.org" <grow@ietf.org>
Message-ID: <CC5BE44F.2A792%pds@lugs.com>
Thread-Topic: Call for GROW WG adoption of grow-overlapping-routes
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3428574298_34778569"
Subject: [GROW] Call for GROW WG adoption of 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: Thu, 23 Aug 2012 05:45:00 -0000

> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--B_3428574298_34778569
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit

Hello,

At IETF in vancouver we had a presentation from Russ White for a new working
group item draft-white-grow-overlapping-routes-00.  I would like to gauge
the working group interest in adopting this draft as a working group item.
Can people please voice their approval or disapproval.

Thanks

Peter





--B_3428574298_34778569
Content-type: text/html;
	charset="US-ASCII"
Content-transfer-encoding: quoted-printable

<html><head></head><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: s=
pace; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size:=
 14px; font-family: Calibri, sans-serif; "><div>Hello,</div><div><br></div><=
div>At IETF in vancouver we had a presentation from Russ White for a new wor=
king group item draft-white-grow-overlapping-routes-00. &nbsp;I would like t=
o gauge the working group interest in adopting this draft as a working group=
 item. &nbsp;Can people please voice their approval or disapproval.</div><di=
v><br></div><div>Thanks</div><div><br></div><div>Peter</div><div><br></div><=
div><br></div></body></html>

--B_3428574298_34778569--



From nick@inex.ie  Mon Aug 27 07:12:18 2012
Return-Path: <nick@inex.ie>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3CA4921F86B8 for <grow@ietfa.amsl.com>; Mon, 27 Aug 2012 07:12:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.411
X-Spam-Level: 
X-Spam-Status: No, score=-2.411 tagged_above=-999 required=5 tests=[AWL=0.189,  BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yxTzF6Ujmcsj for <grow@ietfa.amsl.com>; Mon, 27 Aug 2012 07:12:17 -0700 (PDT)
Received: from mail.acquirer.com (mail.acquirer.com [IPv6:2a03:8900:0:100::5]) by ietfa.amsl.com (Postfix) with ESMTP id 9B56421F8665 for <grow@ietf.org>; Mon, 27 Aug 2012 07:12:09 -0700 (PDT)
X-Envelope-To: <grow@ietf.org>
Received: from crumpet.internal.acquirer.com ([IPv6:2001:1bb8:2004:100:4d7c:d1ec:9a32:d6b4]) (authenticated bits=0) by mail.acquirer.com (8.14.4/8.14.4) with ESMTP id q7REAXHj079011 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <grow@ietf.org>; Mon, 27 Aug 2012 15:10:34 +0100 (IST) (envelope-from nick@inex.ie)
Message-ID: <503B8037.9010505@inex.ie>
Date: Mon, 27 Aug 2012 15:12:07 +0100
From: Nick Hilliard <nick@inex.ie>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: grow@ietf.org
References: <CC5BE44F.2A792%pds@lugs.com>
In-Reply-To: <CC5BE44F.2A792%pds@lugs.com>
X-Enigmail-Version: 1.4.4
X-Company-Info-1: Internet Neutral Exchange Association Limited. Registered in Ireland No. 253804
X-Company-Info-2: Registered Offices: 1-2, Marino Mart, Fairview, Dublin 3
X-Company-Info-3: Internet Neutral Exchange Association Limited is limited by guarantee
X-Company-Info-4: Offices: 4027 Kingswood Road, Citywest, Dublin 24.
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [GROW] Call for GROW WG adoption of 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: Mon, 27 Aug 2012 14:12:18 -0000

On 23/08/2012 06:44, Peter Schoenmaker wrote:
> At IETF in vancouver we had a presentation from Russ White for a new
> working group item draft-white-grow-overlapping-routes-00.  I would like to
> gauge the working group interest in adopting this draft as a working group
> item.  Can people please voice their approval or disapproval.

I'm concerned by a lot of statements in this draft, particularly:
	
> Overall, then, it is desirable to remove overlapping routes from the
> global routing table where possible.

People inject prefixes into the DFZ for specific reasons.  If they are
pruned by some upstream providers but not others, then the traffic
engineering model is broken because you can no longer depend on
more-specifics having visibility around the dfz.  Or am I reading this
incorrectly?

Nick


From robert@raszuk.net  Mon Aug 27 09:07:01 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 0B8BD21F860F for <grow@ietfa.amsl.com>; Mon, 27 Aug 2012 09:07:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.516
X-Spam-Level: 
X-Spam-Status: No, score=-2.516 tagged_above=-999 required=5 tests=[AWL=0.083,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Eg5JGnH8559l for <grow@ietfa.amsl.com>; Mon, 27 Aug 2012 09:07:00 -0700 (PDT)
Received: from mail1310.opentransfer.com (mail1310.opentransfer.com [76.162.254.103]) by ietfa.amsl.com (Postfix) with ESMTP id EF1C321F853B for <grow@ietf.org>; Mon, 27 Aug 2012 09:06:59 -0700 (PDT)
Received: (qmail 18802 invoked by uid 399); 27 Aug 2012 16:08:00 -0000
Received: from unknown (HELO ?192.168.1.58?) (pbs:robert@raszuk.net@83.13.163.62) by mail1310.opentransfer.com with ESMTPM; 27 Aug 2012 16:08:00 -0000
X-Originating-IP: 83.13.163.62
Message-ID: <503B9B23.9070107@raszuk.net>
Date: Mon, 27 Aug 2012 18:06:59 +0200
From: Robert Raszuk <robert@raszuk.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: Nick Hilliard <nick@inex.ie>
References: <CC5BE44F.2A792%pds@lugs.com> <503B8037.9010505@inex.ie>
In-Reply-To: <503B8037.9010505@inex.ie>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: grow@ietf.org
Subject: Re: [GROW] Call for GROW WG adoption of grow-overlapping-routes
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, 27 Aug 2012 16:07:01 -0000

Hi Nick,

 >> Overall, then, it is desirable to remove overlapping routes from the
>> global routing table where possible.
>
> People inject prefixes into the DFZ for specific reasons.  If they are
> pruned by some upstream providers but not others, then the traffic
> engineering model is broken because you can no longer depend on
> more-specifics having visibility around the dfz.  Or am I reading this
> incorrectly?

You are very correct. In fact there is documented prior attempt to only 
remove more specifics where they do not matter any longer for routing. 
The key is to adjust the removal/suppression location to the dynamic 
topology of the inter-network.

http://www.watersprings.org/pub/id/draft-marques-idr-aggregate-00.txt

Otherwise I think we can do more harm then good.

Best,
R.


From iesg-secretary@ietf.org  Thu Aug 30 09:25:36 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 E7BF521F857D; Thu, 30 Aug 2012 09:25:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.874
X-Spam-Level: 
X-Spam-Status: No, score=-101.874 tagged_above=-999 required=5 tests=[AWL=0.498, BAYES_00=-2.599, SARE_SUB_OBFU_Q1=0.227, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oXRClI20aVTS; Thu, 30 Aug 2012 09:25:35 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5CDB821F84F1; Thu, 30 Aug 2012 09:25:35 -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.34
Message-ID: <20120830162535.30621.97129.idtracker@ietfa.amsl.com>
Date: Thu, 30 Aug 2012 09:25:35 -0700
Cc: grow@ietf.org
Subject: [GROW] Last Call: <draft-ietf-grow-ops-reqs-for-bgp-error-handling-05.txt>	(Operational Requirements for Enhanced Error Handling Behaviour	in BGP-4) 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, 30 Aug 2012 16:25:36 -0000

The IESG has received a request from the Global Routing Operations WG
(grow) to consider the following document:
- 'Operational Requirements for Enhanced Error Handling Behaviour in
   BGP-4'
  <draft-ietf-grow-ops-reqs-for-bgp-error-handling-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-09-13. 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


   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 file can be obtained via
http://datatracker.ietf.org/doc/draft-ietf-grow-ops-reqs-for-bgp-error-handling/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-ietf-grow-ops-reqs-for-bgp-error-handling/ballot/


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



From jnc@mercury.lcs.mit.edu  Mon Aug 27 07:43:09 2012
Return-Path: <jnc@mercury.lcs.mit.edu>
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 0CDD921F8464 for <grow@ietfa.amsl.com>; Mon, 27 Aug 2012 07:43:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.62
X-Spam-Level: 
X-Spam-Status: No, score=-5.62 tagged_above=-999 required=5 tests=[AWL=-0.510,  BAYES_05=-1.11, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xijHI+tCspar for <grow@ietfa.amsl.com>; Mon, 27 Aug 2012 07:43:08 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id 9014C21F845D for <grow@ietf.org>; Mon, 27 Aug 2012 07:43:08 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 8C54018C0B0; Mon, 27 Aug 2012 10:43:07 -0400 (EDT)
To: grow@ietf.org
Message-Id: <20120827144307.8C54018C0B0@mercury.lcs.mit.edu>
Date: Mon, 27 Aug 2012 10:43:07 -0400 (EDT)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
X-Mailman-Approved-At: Thu, 30 Aug 2012 12:25:25 -0700
Cc: jnc@mercury.lcs.mit.edu
Subject: Re: [GROW] Call for GROW WG adoption of 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: Mon, 27 Aug 2012 14:43:09 -0000

    > From: Nick Hilliard <nick@inex.ie>

    >> Overall, then, it is desirable to remove overlapping routes from the
    >> global routing table where possible.

    > People inject prefixes into the DFZ for specific reasons. If they are
    > pruned by some upstream providers but not others, then the traffic
    > engineering model is broken because you can no longer depend on
    > more-specifics having visibility around the dfz.

Doing traffic engineering by injecting more-specifics into the global
destination-vector routing is a top pick on my list of 'optimal illustration
for hammer-nail syndrome'. So if we break that approach, that's not a bug,
that's a feature.

Of course, doing traffic engineering 'right' would involve getting rid of
this archaic, creaky destination-vector routing architecture, and that is
going to be a huge project.

But in the meantime, there are approaches that are create slightly less
overhead for everyone in the entire system: e.g. using the identity/location
binding layer - there are several choices available at the moment. They're
just as ugly (architecturally), but at least fewer entities have to bear the
overhead costs (which are less in toto, too).

	Noel

From warren@kumari.net  Thu Aug 30 14:01:15 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 4E98921F8599 for <grow@ietfa.amsl.com>; Thu, 30 Aug 2012 14:01:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JdLhF4E30L8G for <grow@ietfa.amsl.com>; Thu, 30 Aug 2012 14:01:14 -0700 (PDT)
Received: from vimes.kumari.net (vimes.kumari.net [198.186.192.250]) by ietfa.amsl.com (Postfix) with ESMTP id B753421F8552 for <grow@ietf.org>; Thu, 30 Aug 2012 14:01:14 -0700 (PDT)
Received: from [192.168.1.87] (host86-179-59-20.range86-179.btcentralplus.com [86.179.59.20]) by vimes.kumari.net (Postfix) with ESMTPSA id 70EF81B40386; Thu, 30 Aug 2012 17:01:13 -0400 (EDT)
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=windows-1252
From: Warren Kumari <warren@kumari.net>
In-Reply-To: <20120827144307.8C54018C0B0@mercury.lcs.mit.edu>
Date: Thu, 30 Aug 2012 17:01:12 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <3B22B4C3-76BC-42CA-A5A5-8079E8611385@kumari.net>
References: <20120827144307.8C54018C0B0@mercury.lcs.mit.edu>
To: jnc@mercury.lcs.mit.edu (Noel Chiappa)
X-Mailer: Apple Mail (2.1278)
Cc: grow@ietf.org, Warren Kumari <warren@kumari.net>
Subject: Re: [GROW] Call for GROW WG adoption of 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: Thu, 30 Aug 2012 21:01:15 -0000

On Aug 27, 2012, at 10:43 AM, Noel Chiappa wrote:

>> From: Nick Hilliard <nick@inex.ie>
>=20
>>> Overall, then, it is desirable to remove overlapping routes from the
>>> global routing table where possible.
>=20
>> People inject prefixes into the DFZ for specific reasons. If they are
>> pruned by some upstream providers but not others, then the traffic
>> engineering model is broken because you can no longer depend on
>> more-specifics having visibility around the dfz.
>=20
> Doing traffic engineering by injecting more-specifics into the global
> destination-vector routing is a top pick on my list of 'optimal =
illustration
> for hammer-nail syndrome'. So if we break that approach, that's not a =
bug,
> that's a feature.

Sez you -- but there are a large number of folk that are currently doing =
this, and doing this for a reason, and will no doubt be very surprised =
when it suddenly stops working=85

Removing their ability to use this "feature" because it violates your =
(and to honest, my) views of elegance seems, um, impolite at best.

>=20
> Of course, doing traffic engineering 'right' would involve getting rid =
of
> this archaic, creaky destination-vector routing architecture, and that =
is
> going to be a huge project.
>=20

Yup.

> But in the meantime, there are approaches that are create slightly =
less
> overhead for everyone in the entire system: e.g. using the =
identity/location
> binding layer - there are several choices available at the moment.

Deployed ones? That I can actually use, now?

> They're
> just as ugly (architecturally), but at least fewer entities have to =
bear the
> overhead costs (which are less in toto, too).



W

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

--
What our ancestors would really be thinking, if they were alive today, =
is: "Why is it so dark in here?"

    -- (Terry Pratchett, Pyramids)



From jnc@mercury.lcs.mit.edu  Thu Aug 30 18:32:31 2012
Return-Path: <jnc@mercury.lcs.mit.edu>
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 6A9A121F8516 for <grow@ietfa.amsl.com>; Thu, 30 Aug 2012 18:32:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.357
X-Spam-Level: 
X-Spam-Status: No, score=-6.357 tagged_above=-999 required=5 tests=[AWL=0.242,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qB-Xv90CoOoH for <grow@ietfa.amsl.com>; Thu, 30 Aug 2012 18:32:31 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id DDB6D21F8512 for <grow@ietf.org>; Thu, 30 Aug 2012 18:32:30 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id F168D18C0E1; Thu, 30 Aug 2012 21:32:29 -0400 (EDT)
To: grow@ietf.org
Message-Id: <20120831013229.F168D18C0E1@mercury.lcs.mit.edu>
Date: Thu, 30 Aug 2012 21:32:29 -0400 (EDT)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: jnc@mercury.lcs.mit.edu
Subject: Re: [GROW] Call for GROW WG adoption of 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: Fri, 31 Aug 2012 01:32:31 -0000

    > From: Robert Raszuk <robert@raszuk.net>

    > even those proposed just push the issue to a mapping plane 

I did say that doing TE in a mapping would not be as good as an upgraded,
modern routing architecture (one suited to a global-scale information network
- but let's not get me started on that rant) that had TE capabilities built
into it... _but_ using the mapping plane is still much better than using
more-specifics.

Just like doing multi-homing by injecting routes into the global
destination-vector routing is just about the worst way to support MH, same
thing for TE. Every router in the entire default-free core has to dedicate a
routing table slot to each more-specific - and not just that, it's not just
table entries, there's also routing system overhead to maintain it (CPU, etc,
etc).

If you do it in a mapping plane the only people who have to pay the overhead
are the people _who actually talk to that destination_ - not everyone in the
whole world. Does this not sound like a fairer way to support this?

	Noel

From wherrin@gmail.com  Thu Aug 30 19:00:01 2012
Return-Path: <wherrin@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 C550321F851E for <grow@ietfa.amsl.com>; Thu, 30 Aug 2012 19:00:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.977
X-Spam-Level: 
X-Spam-Status: No, score=-2.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MIcPtiyJC8Mr for <grow@ietfa.amsl.com>; Thu, 30 Aug 2012 19:00:01 -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 EA2DA21F84F1 for <grow@ietf.org>; Thu, 30 Aug 2012 19:00:00 -0700 (PDT)
Received: by obbwc20 with SMTP id wc20so5157633obb.31 for <grow@ietf.org>; Thu, 30 Aug 2012 19:00:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type; bh=6JT18kgmx8dVIGnJnw2UtSF+5WqkasQAQpw/SxyNPvI=; b=CprMUEDD3nTGEdbMLSR8Nu0ruDgVrL0ndhsVS+YLaUuXmOTTPl+jg+xRwAC8LNQZ99 bUsBOrjLwBXhYCgvlR64uLq/+cbsWrhpcEa1cxMFAvvgeW9lryI8FKm19dNywT4mNSBh bK8yQKiR2fyfJyxY3frE5CO8sCT+e8rDoXHMu2ODPy6qaRkZWYnb4V05LRgzLz2KxKgu s4MSYHmPEt9riul+TXyn3OELoS//EKdQjK5lKcgEDd0oLexLWabCH7Uhen3UNRg1ERbs 0N/RNEnHOVd2DNgg5AZgLIBzbVN8lng8Ezue4I9O+rBbLQ57R/aZRBFODkrkUMDczs5U 49qQ==
Received: by 10.60.7.104 with SMTP id i8mr6369982oea.31.1346378400537; Thu, 30 Aug 2012 19:00:00 -0700 (PDT)
MIME-Version: 1.0
Sender: wherrin@gmail.com
Received: by 10.182.4.33 with HTTP; Thu, 30 Aug 2012 18:59:40 -0700 (PDT)
In-Reply-To: <CC5BE44F.2A792%pds@lugs.com>
References: <CC5BE44F.2A792%pds@lugs.com>
From: William Herrin <bill@herrin.us>
Date: Thu, 30 Aug 2012 21:59:40 -0400
X-Google-Sender-Auth: xxxhLazCa3RfqudvdrXJtDSxOWg
Message-ID: <CAP-guGXL6-AkPSnMJ7TY-dVafOMXKtFNQCUdKcrVGrbHoQNSXQ@mail.gmail.com>
To: Peter Schoenmaker <pds@lugs.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] Call for GROW WG adoption of 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: Fri, 31 Aug 2012 02:00:01 -0000

On Thu, Aug 23, 2012 at 1:44 AM, Peter Schoenmaker <pds@lugs.com> wrote:
> At IETF in vancouver we had a presentation from Russ White for a new working
> group item draft-white-grow-overlapping-routes-00.  I would like to gauge
> the working group interest in adopting this draft as a working group item.
> Can people please voice their approval or disapproval.

Hi Peter,

What am I missing? The last few times this was discussed here or on
RRG, RIB aggregation fell apart on the details. For example, what
happens when:

AS1 announces 10.1.0.0/16 from network A via ISP 1 and 2
AS1 announces 10.1.33.0/24 from network B via ISP 3 and 4

If the answer is: AS1 disaggregates 10.1.0.0/16 in order to avoid
overlapping 10.2.33.0/24 because at least a couple folks implementing
overlapping-routes broke network B then what is there to discuss?

Regards,
Bill Herrin

-- 
William D. Herrin ................ herrin@dirtside.com  bill@herrin.us
3005 Crane Dr. ...................... Web: <http://bill.herrin.us/>
Falls Church, VA 22042-3004

From christopher.morrow@gmail.com  Thu Aug 30 19:03:39 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 17AE011E80E4 for <grow@ietfa.amsl.com>; Thu, 30 Aug 2012 19:03:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.157
X-Spam-Level: 
X-Spam-Status: No, score=-103.157 tagged_above=-999 required=5 tests=[AWL=0.442, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R0PKGM7qCRlr for <grow@ietfa.amsl.com>; Thu, 30 Aug 2012 19:03:38 -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 C2F4E21F84CE for <grow@ietf.org>; Thu, 30 Aug 2012 19:03:25 -0700 (PDT)
Received: by vcbfo14 with SMTP id fo14so3125676vcb.31 for <grow@ietf.org>; Thu, 30 Aug 2012 19:03:23 -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=cdYOAQhv7rJ731YLPHqR3upuA8aW0WBwRrkW3GKqOTA=; b=JYyiM0Hip1D4XItNhD2HNPysf5kclsWsp5kpBlzntzDcJwA792YOl4E0YKa2QoxOKu bTZkb4h3hgkhnsnquV8zkycNEfkauVZAEyP3+MvqpCqBxeMWc/xpw8RjhM9IsGEIfHGz NHjj+MslkDuC3pJdnP14nbyhLeAP9a389+uS6I7MSTyb+7OxsXT/f+unwyKlQlUIAGS4 Io1d1ypzOPPOLotTBv7M8CvfOMBh+7qA5+GDtMm3w1lLVKrLaYBDBBaa9ItiQE+UU/Nz SKwGRhlk++olnPhMkZiXmBgm3j7LL2gFgdkvAoWqOigZSN+/x+DK5OmIfhM3FzVcKwNf wt8w==
MIME-Version: 1.0
Received: by 10.220.220.203 with SMTP id hz11mr4788804vcb.50.1346378603582; Thu, 30 Aug 2012 19:03:23 -0700 (PDT)
Received: by 10.58.216.42 with HTTP; Thu, 30 Aug 2012 19:03:23 -0700 (PDT)
In-Reply-To: <CAP-guGXL6-AkPSnMJ7TY-dVafOMXKtFNQCUdKcrVGrbHoQNSXQ@mail.gmail.com>
References: <CC5BE44F.2A792%pds@lugs.com> <CAP-guGXL6-AkPSnMJ7TY-dVafOMXKtFNQCUdKcrVGrbHoQNSXQ@mail.gmail.com>
Date: Thu, 30 Aug 2012 22:03:23 -0400
Message-ID: <CAL9jLaYGu3mOKEFGESEm8EmtH5bhijV1AhjYi44_4Kqv=2-2SQ@mail.gmail.com>
From: Christopher Morrow <christopher.morrow@gmail.com>
To: William Herrin <bill@herrin.us>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] Call for GROW WG adoption of 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: Fri, 31 Aug 2012 02:03:39 -0000

On Thu, Aug 30, 2012 at 9:59 PM, William Herrin <bill@herrin.us> wrote:
> On Thu, Aug 23, 2012 at 1:44 AM, Peter Schoenmaker <pds@lugs.com> wrote:
>> At IETF in vancouver we had a presentation from Russ White for a new working
>> group item draft-white-grow-overlapping-routes-00.  I would like to gauge
>> the working group interest in adopting this draft as a working group item.
>> Can people please voice their approval or disapproval.
>
> Hi Peter,
>
> What am I missing? The last few times this was discussed here or on

you're probably not missing anything in particular, except that you
didn't state whether or not the doc (or the ideas that the doc
contains/explains) should show up as a working-group work item.

> RRG, RIB aggregation fell apart on the details. For example, what
> happens when:
>
> AS1 announces 10.1.0.0/16 from network A via ISP 1 and 2
> AS1 announces 10.1.33.0/24 from network B via ISP 3 and 4
>
> If the answer is: AS1 disaggregates 10.1.0.0/16 in order to avoid
> overlapping 10.2.33.0/24 because at least a couple folks implementing
> overlapping-routes broke network B then what is there to discuss?
>
> Regards,
> Bill Herrin
>
> --
> William D. Herrin ................ herrin@dirtside.com  bill@herrin.us
> 3005 Crane Dr. ...................... Web: <http://bill.herrin.us/>
> Falls Church, VA 22042-3004
> _______________________________________________
> GROW mailing list
> GROW@ietf.org
> https://www.ietf.org/mailman/listinfo/grow

From wherrin@gmail.com  Thu Aug 30 19:44:43 2012
Return-Path: <wherrin@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 95CBE11E80E5 for <grow@ietfa.amsl.com>; Thu, 30 Aug 2012 19:44:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.977
X-Spam-Level: 
X-Spam-Status: No, score=-2.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1zIZxk+TXyku for <grow@ietfa.amsl.com>; Thu, 30 Aug 2012 19:44:42 -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 8E03B11E80E4 for <grow@ietf.org>; Thu, 30 Aug 2012 19:44:42 -0700 (PDT)
Received: by obbwc20 with SMTP id wc20so5208824obb.31 for <grow@ietf.org>; Thu, 30 Aug 2012 19:44:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type; bh=SQaXE0ZiNfcPynr0+lcmhHkAVv0e7mQSzyjYPI98CLE=; b=IHaMkpWiQB+9A39Lb6vN33KQYVoUU4krz/FVphbb2gGgdbOASFcr7L9b4OIZ6AcUPG FAX6+UuloCHC5KXGh06rg1pBwG6YHzEmQ75gS7+20fO/mUAeJIAjyaUo1x8BDi7rVC5f w4TL1hoB0rbfTvEL22pFM8ufrTmdHfN4/ERR82l7Zlls7EZD/nyufX0RSXztiySrQgSB /Tjgg1llLYx95ZbkCJl8uu3yTIb/bzcXjGWCxjnpZVfufCtm5GbHgpeCQ/lO0T5muBQt 2EsizGKKc8HmPs00x6bfXouhfo+X08iNUkxcwasRfDHoNoant4dRPl8jfiDL5sGgf1aO KyWA==
Received: by 10.60.170.47 with SMTP id aj15mr6500994oec.29.1346381082166; Thu, 30 Aug 2012 19:44:42 -0700 (PDT)
MIME-Version: 1.0
Sender: wherrin@gmail.com
Received: by 10.182.4.33 with HTTP; Thu, 30 Aug 2012 19:44:20 -0700 (PDT)
In-Reply-To: <CAL9jLaYGu3mOKEFGESEm8EmtH5bhijV1AhjYi44_4Kqv=2-2SQ@mail.gmail.com>
References: <CC5BE44F.2A792%pds@lugs.com> <CAP-guGXL6-AkPSnMJ7TY-dVafOMXKtFNQCUdKcrVGrbHoQNSXQ@mail.gmail.com> <CAL9jLaYGu3mOKEFGESEm8EmtH5bhijV1AhjYi44_4Kqv=2-2SQ@mail.gmail.com>
From: William Herrin <bill@herrin.us>
Date: Thu, 30 Aug 2012 22:44:20 -0400
X-Google-Sender-Auth: DVw_vsu1tWQm5NZssXHNvblMpcI
Message-ID: <CAP-guGWxhr4m7gc-7581Wo0PjHdOMx-HmNDcXxZAtYPBYUtssA@mail.gmail.com>
To: Christopher Morrow <christopher.morrow@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] Call for GROW WG adoption of 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: Fri, 31 Aug 2012 02:44:43 -0000

On Thu, Aug 30, 2012 at 10:03 PM, Christopher Morrow
<christopher.morrow@gmail.com> wrote:
> On Thu, Aug 30, 2012 at 9:59 PM, William Herrin <bill@herrin.us> wrote:
>> On Thu, Aug 23, 2012 at 1:44 AM, Peter Schoenmaker <pds@lugs.com> wrote:
>>> At IETF in vancouver we had a presentation from Russ White for a new working
>>> group item draft-white-grow-overlapping-routes-00.  I would like to gauge
>>> the working group interest in adopting this draft as a working group item.
>>
>> What am I missing? The last few times this was discussed here or on
>
> you're probably not missing anything in particular, except that you
> didn't state whether or not the doc (or the ideas that the doc
> contains/explains) should show up as a working-group work item.

Hi Christopher,

Well, unless one of the authors wants to step up and say, "Bill, we
anticipated the problem you posed and this is how we cleverly got
around everything like it," I'd have to say thumbs down on adopting it
for discussion and work. Recommend the authors pore through the RRG
archives for a history lesson in all the myriad approaches to RIB
aggregation that are known to not work. If aggregating overlaps isn't
the most popular non-working approach it's surely the second most
popular.

That, by the way, would make a great draft: a canonical list of the
approaches considered for RIB aggregation and the key faults
identified with each. So that the next guy doesn't have to pore
through the RRG archives and, when somebody does find a novel idea, he
can explicitly point out that, "This is why it doesn't suffer the
fault identified in RFC X section 8."

Regards,
Bill Herrin


-- 
William D. Herrin ................ herrin@dirtside.com  bill@herrin.us
3005 Crane Dr. ...................... Web: <http://bill.herrin.us/>
Falls Church, VA 22042-3004

From nick@inex.ie  Fri Aug 31 02:11:00 2012
Return-Path: <nick@inex.ie>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8C20121F859E for <grow@ietfa.amsl.com>; Fri, 31 Aug 2012 02:11:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.442
X-Spam-Level: 
X-Spam-Status: No, score=-2.442 tagged_above=-999 required=5 tests=[AWL=0.158,  BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id w5oTxbY59jlx for <grow@ietfa.amsl.com>; Fri, 31 Aug 2012 02:11:00 -0700 (PDT)
Received: from mail.acquirer.com (mail.acquirer.com [IPv6:2a03:8900:0:100::5]) by ietfa.amsl.com (Postfix) with ESMTP id C97C521F8532 for <grow@ietf.org>; Fri, 31 Aug 2012 02:10:58 -0700 (PDT)
X-Envelope-To: grow@ietf.org
Received: from crumpet.local ([IPv6:2001:1bb8:2004:100:8133:4651:f18f:1ee0]) (authenticated bits=0) by mail.acquirer.com (8.14.4/8.14.4) with ESMTP id q7V99Hdv036408 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Fri, 31 Aug 2012 10:09:18 +0100 (IST) (envelope-from nick@inex.ie)
Message-ID: <50407F9F.6010901@inex.ie>
Date: Fri, 31 Aug 2012 10:10:55 +0100
From: Nick Hilliard <nick@inex.ie>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:15.0) Gecko/20120824 Thunderbird/15.0
MIME-Version: 1.0
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
References: <20120831013229.F168D18C0E1@mercury.lcs.mit.edu>
In-Reply-To: <20120831013229.F168D18C0E1@mercury.lcs.mit.edu>
X-Enigmail-Version: 1.4.4
X-Company-Info-1: Internet Neutral Exchange Association Limited. Registered in Ireland No. 253804
X-Company-Info-2: Registered Offices: 1-2, Marino Mart, Fairview, Dublin 3
X-Company-Info-3: Internet Neutral Exchange Association Limited is limited by guarantee
X-Company-Info-4: Offices: 4027 Kingswood Road, Citywest, Dublin 24.
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: grow@ietf.org
Subject: Re: [GROW] Call for GROW WG adoption of 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: Fri, 31 Aug 2012 09:11:00 -0000

On 31/08/2012 02:32, Noel Chiappa wrote:
> Just like doing multi-homing by injecting routes into the global
> destination-vector routing is just about the worst way to support MH,

reminds me of that saying: "... democracy is the worst form of government
except all the others that have been tried."

No-one's going to argue that multihoming by multiple prefix announcement
isn't a pile of poo.  It's just that all that all the alternatives are even
worse.  At least multihoming by multiple prefix announcement is simple and
has well-understood problems and failure modes.  All the alternatives are
significantly more complicated in a variety of different ways, and all open
up many more and many more complicated failure modes.

Re: the draft, I don't think it should be adopted by the WG unless the
authors can provide analysis showing that it doesn't fail in the two modes
which were mentioned on the list in the last couple of days.

Nick

From chris.hall@highwayman.com  Fri Aug 31 01:02:42 2012
Return-Path: <chris.hall@highwayman.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 88B7A21F8448; Fri, 31 Aug 2012 01:02:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.394
X-Spam-Level: 
X-Spam-Status: No, score=-98.394 tagged_above=-999 required=5 tests=[AWL=1.918, BAYES_00=-2.599, HELO_MISMATCH_UK=1.749, HOST_MISMATCH_NET=0.311, SARE_SUB_OBFU_Q1=0.227, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jBmhqQLRVYHR; Fri, 31 Aug 2012 01:02:37 -0700 (PDT)
Received: from smtp.demon.co.uk (mdfmta009.mxout.tch.inty.net [91.221.169.50]) by ietfa.amsl.com (Postfix) with ESMTP id D548F21F851E; Fri, 31 Aug 2012 01:02:36 -0700 (PDT)
Received: from mdfmta009.tch.inty.net (unknown [127.0.0.1]) by mdfmta009.tch.inty.net (Postfix) with ESMTP id 73DC4128074; Fri, 31 Aug 2012 09:02:35 +0100 (BST)
Received: from mdfmta009.tch.inty.net (unknown [127.0.0.1])	by mdfmta009.tch.inty.net (Postfix) with ESMTP id 2FBAF128071; Fri, 31 Aug 2012 09:02:35 +0100 (BST)
Received: from hestia.halldom.com (unknown [80.177.246.130])	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))	(No client certificate requested)	by mdfmta009.tch.inty.net (Postfix) with ESMTP; Fri, 31 Aug 2012 09:02:34 +0100 (BST)
Received: from hyperion.halldom.com ([80.177.246.170] helo=HYPERION)	by hestia.halldom.com with esmtpsa (TLSv1:AES128-SHA:128)	(Exim 4.76)	(envelope-from <chris.hall@highwayman.com>)	id 1T7MBV-0003i5-J9; Fri, 31 Aug 2012 08:02:33 +0000
From: "Chris Hall" <chris.hall@highwayman.com>
To: "'idr wg'" <idr@ietf.org>,	<grow@ietf.org>
Date: Fri, 31 Aug 2012 09:02:28 +0100
Organization: Highwayman
Message-ID: <066901cd874e$fa0605f0$ee1211d0$@highwayman.com>
MIME-Version: 1.0
Content-Type: text/plain;	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
thread-index: Ac2HTvN2YkXA8qTARvuH2ZZnes8lhw==
Content-Language: en-gb
X-MDF-HostID: 22
X-Mailman-Approved-At: Fri, 31 Aug 2012 07:03:22 -0700
Subject: Re: [GROW] [Idr] draft-ietf-grow-ops-reqs-for-bgp-error-handling-05
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, 31 Aug 2012 08:02:42 -0000

In trying to classify Errors with BGP-4 UPDATE Messages I think it
would be useful to distinguish between the form of an error and the
severity of that error and how BGP should respond.

It seems to me that there are four severities/responses:

  1) "Critical Error" -> drop/restart session or AFI/SAFI

     So the overall response then depends on how gracefully the
     session drop and/or restart can be handled.

  2) "Serious Error" -> do something with NLRI, short of
     dropping the session.

     The "treat-as-withdraw" mechanism is mentioned.

     The requirements obviously do not wish to specify mechanisms.

     But I think that the requirements should address what outcome
     is expected if errors in an individual UPDATE message are to
     be limited to that message.  I think what that means is:

       * it must be possible to identify all NLRI that the message
         could be carrying.

       * whatever is done with those NLRI must reflect the fact
         that the recipient has an incomplete, possibly empty,
         set of attributes for those NLRI.

  3) "Ignorable Error" -> process the UPDATE message as if the
     ignored attributes

     Some errors in some trivial attributes may be ignorable.
     The requirements could cover the criteria for being deemed
     trivial.

     Some errors in Optional Transitive may be dealt with by
     ignoring the attribute altogether.  The requirements
     mention this, but do not specify criteria for being
     ignorable.

  4) "Recoverable Error" -> process the UPDATE message which has
     had errors "patched up".

     The draft-ieft-idr-error-handling, for example, suggests
     that invalid Attribute Flags may simply be overwritten
     by the expected value.

I would then divide the forms of error into (1) "framing" and (2)
"content" (or "semantic").

A BGP UPDATE message has three levels of framing:

  * Level 1 -- the 16 octet "Marker" + Message Length
                                     + Withdrawn Routes Length
                                     + Total Path Attributes Length

    If the Message Length is broken, it is extremely likely that the
    "Marker" on the next message will be invalid.

  * Level 2(a) -- the Withdrawn Routes

    Each prefix must have a valid prefix length, and the last
    must run exactly to the end of this part of the message.

  * Level 2(b) -- the Attributes

    Each attribute must be correctly framed, and at the end of the
    attributes the last one must run to exactly the end of the
    attribute part of the message.

  * Level 2(c) -- the Network Layer Reachability Information.

    Same as 2(a).

  * Level 3 -- various Attributes

    Some attributes have internal framing.

So far, so obvious.  To judge if an individual attribute is properly
framed, we need to consider the red-tape:

  * the Flags octet has a limited set of valid values, depending
    on the Type.

  * the Type may be more or less anything, but repeats are not
    valid.
 
  * the Length is constrained for some Types

There is some redundancy here, more for known types than unknown ones,
which helps.  The Total Path Attributes Length is, effectively, a
checksum for all the Lengths of all the Attributes.  It would be
possible to specify that a set of attributes should be deemed
correctly framed solely on the basis of passing that test.  However,
my feeling is that all the available redundancy (such as it is) should
be used to minimise the possibility of accepting a broken attributes
-- *particularly* where an error is going to be treated as Ignorable.

Once attributes are correctly framed, then one can consider their
content.  Wherever the line between framing and content is drawn, I
think it helps to be clear about the distinction between them --
"framing" errors affect the attribute and the attributes around it,
"content" errors affect only the attribute.

The framing of an Optional Transitive is a special case.  If the
parser recognises an Optional Transitive, but its Length is not valid,
what should the receiver do ?  If the sender did not understand the
Attribute, then the broken Length is a "content" issue.  If the sender
did understand it, then the broken Length is a "framing" issue.  (It
is a serious disappointment to me that the Partial bit does not help
here.  But even if it did, what if the sender made a mess of
setting/clearing it !?)

In section 2.1.2 the draft specifies a number of "Semantic BGP
Errors", which includes many things which I would class as "framing"
errors.

This is all pretty low level stuff.  I can hear an argument that the
requirements document is not the place for this level of detail.
However, without a more precise understanding of how broken attributes
may be parsed, requirements for how to deal with them are hard to
specify and to interpret.

If NLRI were explicitly separate from the attributes, then if a set of
attributes fails a strict "framing" check, then "treat-as-withdraw"
(or equivalent) could be applied, reliably.  This seems to me to be as
safe as possible, short of dropping the session (which has its own
safety issues).

With NLRI mixed up in the attributes, either one plays safe and treats
all attribute errors as Critical, or a much more detailed analysis of
attribute parsing is required.  What is the cost of missing some NLRI
which were sent, but were obscured by some other broken attribute ?
What is the risk ?  What degree of broken-ness of an attribute can be
deemed not to invalidate the parsing of the attributes before and/or
after it ?  Is that different for different attributes ?

In order to contemplate classifying some attribute errors as
"Ignorable" or "Recoverable", a more detailed analysis of attribute
parsing is also required.  An ATOMIC_AGGREGATE attribute is arguably
trivial and Ignorable.  But is an ATOMIC_AGGREGATE attribute with a
length of 421 (say) likely to be a momentary lapse of concentration at
the sender end, or more likely to be a symptom of a badly broken set
of attributes ? 

Chris


From jnc@mercury.lcs.mit.edu  Fri Aug 31 09:02:45 2012
Return-Path: <jnc@mercury.lcs.mit.edu>
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 4895221F8484 for <grow@ietfa.amsl.com>; Fri, 31 Aug 2012 09:02:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.364
X-Spam-Level: 
X-Spam-Status: No, score=-6.364 tagged_above=-999 required=5 tests=[AWL=0.235,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iHwxBqZxq3FQ for <grow@ietfa.amsl.com>; Fri, 31 Aug 2012 09:02:40 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id 029F621F866E for <grow@ietf.org>; Fri, 31 Aug 2012 09:02:39 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id CD85918C0E6; Fri, 31 Aug 2012 12:02:38 -0400 (EDT)
To: grow@ietf.org
Message-Id: <20120831160238.CD85918C0E6@mercury.lcs.mit.edu>
Date: Fri, 31 Aug 2012 12:02:38 -0400 (EDT)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: jnc@mercury.lcs.mit.edu
Subject: Re: [GROW] Call for GROW WG adoption of 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: Fri, 31 Aug 2012 16:02:45 -0000

{Apologies to the list for the slight derail I started, but it's an
interesting topic, and also one of my hot buttons... :-}

On the actual subject of the document, I too agree it would be good to have a
document which looks in detail at aggregation in destination-vector routing
architectures; there are indeed some interesting 'issues' when you try and
automatically start aggregating more-specifics.


    > From: Warren Kumari <warren@kumari.net>

    >> Doing traffic engineering by injecting more-specifics into the global
    >> destination-vector routing is a top pick on my list of 'optimal
    >> illustration for hammer-nail syndrome'

    > there are a large number of folk that are currently doing this ..
    > Removing their ability to use this "feature" because it violates ..
    > views of elegance seems, um, impolite at best.

First, 'elegance' isn't abstract - doing things the ugly way has real costs
and disadvantages, and it's those I really care about: 'elegant' is
effectively just a short-hand for all the upsides.

Second, I never advocated taking that mechanism way _unless there was
something else available_; of course we're running an operational system that
a large part of the world's population has come to rely on. But 'we do it
this way because we've always done it this way' is no way to run a railroad.


    > From: Nick Hilliard <nick@inex.ie>

    > No-one's going to argue that multihoming by multiple prefix
    > announcement isn't a pile of poo. It's just that all that all the
    > alternatives are even worse.

How is using a {location->identity} binding layer worse? (And please read
the next bit before you answer...)

    > All the alternatives are significantly more complicated in a variety of
    > different ways, and all open up many more and many more complicated
    > failure modes.

So, because the newer Unix/Linux file systems are "more complicated in a
variety of different ways", with "more and many more complicated failure
modes" we should go back to the v6 one?

Of course not. The new systems have lots of good properties (including better
scaling); and although they are indeed considerably more complex (with
attendant increase in number of failure modes), they also have stuff added to
try and make them even more robust - one of their features - (albeit at a
cost of even more complexity).

And don't forget that your 'simple' alternative has costs and failure modes
of its own - all those extra routes in the DFZ create problems when tables
overflow, mean longer convergance times after major topology changes, etc,
etc, etc.

Look, simple systems are wonderful. I love (and prefer) simple systems.
However, they often have issues (e.g. don't scale well), and you have to use
something more complex. Deal.

	Noel

From nick@inex.ie  Fri Aug 31 10:31:19 2012
Return-Path: <nick@inex.ie>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D8B4E21F861A for <grow@ietfa.amsl.com>; Fri, 31 Aug 2012 10:31:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level: 
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[AWL=0.150,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id axql22Q4dBat for <grow@ietfa.amsl.com>; Fri, 31 Aug 2012 10:31:19 -0700 (PDT)
Received: from mail.acquirer.com (mail.acquirer.com [IPv6:2a03:8900:0:100::5]) by ietfa.amsl.com (Postfix) with ESMTP id 2B2F721F8618 for <grow@ietf.org>; Fri, 31 Aug 2012 10:31:18 -0700 (PDT)
X-Envelope-To: grow@ietf.org
Received: from crumpet.local (inet-gw.acquirer.com [87.198.142.10]) (authenticated bits=0) by mail.acquirer.com (8.14.4/8.14.4) with ESMTP id q7VHTYBe042126 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Fri, 31 Aug 2012 18:29:34 +0100 (IST) (envelope-from nick@inex.ie)
Message-ID: <5040F4E0.8010805@inex.ie>
Date: Fri, 31 Aug 2012 18:31:12 +0100
From: Nick Hilliard <nick@inex.ie>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:15.0) Gecko/20120824 Thunderbird/15.0
MIME-Version: 1.0
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
References: <20120831160238.CD85918C0E6@mercury.lcs.mit.edu>
In-Reply-To: <20120831160238.CD85918C0E6@mercury.lcs.mit.edu>
X-Enigmail-Version: 1.4.4
X-Company-Info-1: Internet Neutral Exchange Association Limited. Registered in Ireland No. 253804
X-Company-Info-2: Registered Offices: 1-2, Marino Mart, Fairview, Dublin 3
X-Company-Info-3: Internet Neutral Exchange Association Limited is limited by guarantee
X-Company-Info-4: Offices: 4027 Kingswood Road, Citywest, Dublin 24.
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: grow@ietf.org
Subject: Re: [GROW] Call for GROW WG adoption of 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: Fri, 31 Aug 2012 17:31:20 -0000

On 31/08/2012 17:02, Noel Chiappa wrote:
> On the actual subject of the document, I too agree it would be good to have a
> document which looks in detail at aggregation in destination-vector routing
> architectures; there are indeed some interesting 'issues' when you try and
> automatically start aggregating more-specifics.

at the RIB layer, yes.  At the rib->fib conversion layer, you can do a lot
more as you're going to end up with an N:M mapping between prefixes (N) and
next-hops (M), so it's relatively easy to delete more specifics if it
happens that they have the same NH as the covering prefix.  Obviously you
can't do this at the RIB layer as easily because you can't afford to lose
the information there.

So the idea is good; it's just being applied to the wrong layer.

Nick

From rjs@rob.sh  Fri Aug 31 11:02:47 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 5834A21F846B; Fri, 31 Aug 2012 11:02:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.414
X-Spam-Level: 
X-Spam-Status: No, score=-1.414 tagged_above=-999 required=5 tests=[AWL=0.958,  BAYES_00=-2.599, SARE_SUB_OBFU_Q1=0.227]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Tddgg1zyH5-T; Fri, 31 Aug 2012 11:02:46 -0700 (PDT)
Received: from cappuccino.rob.sh (cappuccino.rob.sh [192.207.141.16]) by ietfa.amsl.com (Postfix) with ESMTP id 8019621F8469; Fri, 31 Aug 2012 11:02:46 -0700 (PDT)
Received: from [109.144.255.62] (helo=[10.10.2.82]) by cappuccino.rob.sh with esmtpa (Exim 4.72) (envelope-from <rjs@rob.sh>) id 1T7VTL-0000u0-BQ; Fri, 31 Aug 2012 18:57:35 +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: <066901cd874e$fa0605f0$ee1211d0$@highwayman.com>
Date: Fri, 31 Aug 2012 18:59:35 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <CB85647B-4BC9-483C-BBA3-73B6DAA8B1F4@rob.sh>
References: <066901cd874e$fa0605f0$ee1211d0$@highwayman.com>
To: Chris Hall <chris.hall@highwayman.com>
X-Mailer: Apple Mail (2.1257)
Cc: 'idr wg' <idr@ietf.org>, grow@ietf.org
Subject: Re: [GROW] [Idr] draft-ietf-grow-ops-reqs-for-bgp-error-handling-05
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, 31 Aug 2012 18:02:47 -0000

Hi Chris,

Thanks for this detailed analysis. It is akin to something that Alton Lo =
and I worked through whilst defining the critical and semantic error =
types (and suggested inclusions).

If you'll forgive me for responding to some particular points, I feel =
this might aid the discussion and positioning. I have added comments =
in-line marked [rjs].

On 31 Aug 2012, at 09:02, Chris Hall wrote:

> This is all pretty low level stuff.  I can hear an argument that the
> requirements document is not the place for this level of detail.
> However, without a more precise understanding of how broken attributes
> may be parsed, requirements for how to deal with them are hard to
> specify and to interpret.

[rjs]: What this draft intends to do is provide expectations, =
requirements and context for error handling in BGP-4, based on current =
deployments (and operator's experience). It also puts forwards =
requirements for how each type of error is reacted to in a broad sense. =
Essentially, where it came from is defining why amending the error =
handling behaviour is required, and providing a framework against which =
we can hang the different developments that are being discussed in IDR, =
such that they meet the operational challenges that come from amending =
this behaviour and form a complete set of solutions to meet the problem =
space.

[rjs]: I think the error handling solutions draft =
(draft-ietf-idr-error-handling) should take the work that we have done =
within IDR and GROW in this draft and build the next level of detail, =
which I think that you've made a great start to. I would like to try and =
keep the requirements draft such that it can be referred to by both =
existing attributes, and future ones.


> With NLRI mixed up in the attributes, either one plays safe and treats
> all attribute errors as Critical, or a much more detailed analysis of
> attribute parsing is required.  What is the cost of missing some NLRI
> which were sent, but were obscured by some other broken attribute ?
> What is the risk ?  What degree of broken-ness of an attribute can be
> deemed not to invalidate the parsing of the attributes before and/or
> after it ?  Is that different for different attributes ?
>=20

[rjs]: Please note that the requirements draft does not present =
distinctions such as recoverable and ignorable. We went around this loop =
previously. I think that in some cases, some specific errors may be =
handled by 'patching' or 'ignoring' specific errors. But generically, =
these are exceptions - the requirements try and define broader =
categories, if a particular attribute needs something else (e.g., =
AS4_PATH may have information it can recover from other attributes) then =
this can be handled in error handling solution considerations of these =
attributes or as it is defined going forward.

[rjs]: It came to my attention whilst reviewing this the existing =
"ignore" wording in the draft is potentially erroneous based on rfc4271:

   All errors detected while processing the UPDATE message MUST be
   indicated by sending the NOTIFICATION message with the Error Code
   UPDATE Message Error.  The error subcode elaborates on the specific
   nature of the error.

[rjs]: Section 3's requirements discuss a need to avoid sending =
NOTIFICATION, and consider the proposed solution that exists. The only =
recommendation made is that treat-as-withdraw looks to be a safe =
behaviour for ensuring that one is not trusting UPDATEs that had some =
erroneous information in them.=20

[rjs]: The requirement the document makes is explicitly that not all =
errors are defined as critical (if they were, the requirement specified =
by section 3 would not be met, and we would stick with the behaviour we =
have right now). The reason for a distinction between critical and =
semantic is that there are certain errors that mean that cannot be =
localised to certain NLRI.
=20
[rjs]: I hope you do not see these comments as dismissive of what you =
have put together - I think that this is where operational and =
implementation views diverge. My view is that I need to understand what =
the impact to a service, the device and the network is during these =
error conditions (and balance the risk of incorrectness against the =
correctness of the protocol). =46rom an implementation perspective, =
clearly, one needs to understand exactly which circumstances one can =
extract the NLRI, and the particulars of how this is achieved. I would =
encourage discussion that falls into the latter category such that we =
define the solutions draft to have the relevant guidance where required. =
Comments on the former should absolutely live in the requirements draft

[rjs]: I would of course encourage further feedback on this subject from =
the WG.

Kind regards,
r.



From john@jlc.net  Fri Aug 31 07:54:30 2012
Return-Path: <john@jlc.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 CC36421F8668; Fri, 31 Aug 2012 07:54:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.392
X-Spam-Level: 
X-Spam-Status: No, score=-105.392 tagged_above=-999 required=5 tests=[AWL=0.380, BAYES_00=-2.599, J_CHICKENPOX_66=0.6, RCVD_IN_DNSWL_MED=-4, SARE_SUB_OBFU_Q1=0.227, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AfTe1R8tGzFG; Fri, 31 Aug 2012 07:54:29 -0700 (PDT)
Received: from mailhost.jlc.net (mailhost.jlc.net [199.201.159.4]) by ietfa.amsl.com (Postfix) with ESMTP id ED5AE21F863C; Fri, 31 Aug 2012 07:54:28 -0700 (PDT)
Received: by mailhost.jlc.net (Postfix, from userid 104) id 6B6DE33C24; Fri, 31 Aug 2012 10:54:28 -0400 (EDT)
Date: Fri, 31 Aug 2012 10:54:28 -0400
From: John Leslie <john@jlc.net>
To: Chris Hall <chris.hall@highwayman.com>
Message-ID: <20120831145428.GX72831@verdi>
References: <066901cd874e$fa0605f0$ee1211d0$@highwayman.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <066901cd874e$fa0605f0$ee1211d0$@highwayman.com>
User-Agent: Mutt/1.4.1i
X-Mailman-Approved-At: Fri, 31 Aug 2012 12:09:50 -0700
Cc: 'idr wg' <idr@ietf.org>, grow@ietf.org
Subject: Re: [GROW] [Idr] draft-ietf-grow-ops-reqs-for-bgp-error-handling-05
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, 31 Aug 2012 14:54:30 -0000

Chris Hall <chris.hall@highwayman.com> wrote:
> 
> In trying to classify Errors with BGP-4 UPDATE Messages I think it
> would be useful to distinguish between the form of an error and the
> severity of that error and how BGP should respond.

   I welcome such a discussion!

> It seems to me that there are four severities/responses:
> 
>   1) "Critical Error" -> drop/restart session or AFI/SAFI
> 
>      So the overall response then depends on how gracefully the
>      session drop and/or restart can be handled.

   BGP was designed for a naive case where all your peers were either
dependable or broken. Moving beyond that has proven difficult. :^(

   But we should recognize the "fully broken" case, which amounts to
"drop the session and be in no hurry to try that peer again".

   Arguably, this should even require human intervention before trying
another session, but I have no horse in that race...

   It is indeed interesting to consider that one AFI/SAFI may be
"fully broken" while others seem dependable: perhaps we should consider
dropping only the part of a session concerning that AFI/SAFI...

>   2) "Serious Error" -> do something with NLRI, short of
>      dropping the session.

   This is a bit vague...

>      The "treat-as-withdraw" mechanism is mentioned.

   This is appropriate when we have reason to believe the peer is
dependable, but is passing us NLRI routing information we're not
willing to trust.  IMHO, "not willing to trust" is in the eye of the
beholder...

   The default should be: we won't send such blocks to that peer
because we don't trust what they'd do with it. However, we might
indeed want to send it to that peer if we have no other route to
that destinatin. Thus, it seems it should actually be a disincentive
(possibly a binary disincentive, but presumably usually closer to
a nasty localpref).

   In brief, I'm not sure "treat-as-withdraw" is the right name...

>      The requirements obviously do not wish to specify mechanisms.
> 
>      But I think that the requirements should address what outcome
>      is expected if errors in an individual UPDATE message are to
>      be limited to that message.  I think what that means is:
> 
>        * it must be possible to identify all NLRI that the message
>          could be carrying.

   I read this to mean that all length+prefix must be readable
(but not necessarily considered valid), whether or not the path
attributes make sense.

   There is an inevitable grey area when the "total path attribute
length" looks dubious but not downright illegal. IMHO, we cannot
usefully standardize "dubious" here -- if we try, we'll find that
implementations differ anyway.

   So this statement sounds fine to me...

>        * whatever is done with those NLRI must reflect the fact
>          that the recipient has an incomplete, possibly empty,
>          set of attributes for those NLRI.

   I take this to mean there's something about the attributes we
don't choose to trust: thus our picture of the "usable" attributes
differs from that of our peer. (Indeed, we may choose to trust
none of them.)

>   3) "Ignorable Error" -> process the UPDATE message as if the
>      ignored attributes

   Some words seem to have gotten lost in tranport...

>      Some errors in some trivial attributes may be ignorable.
>      The requirements could cover the criteria for being deemed
>      trivial.

   "trivial" may be an unfortunate word...

>      Some errors in Optional Transitive may be dealt with by
>      ignoring the attribute altogether.  The requirements
>      mention this, but do not specify criteria for being
>      ignorable.

   "Optional Transitive" is well-defined. Perhaps some advertised
capabilities are less well-defined...

>   4) "Recoverable Error" -> process the UPDATE message which has
>      had errors "patched up".

   This sounds dangerous.

   The path attributes are expected to reflect how our peer came
upon this route. It used to be the case that regardless of the
attributes, we could be sure the peer would _use_ this route; but
we've been chipping away at that assurance.

   I'm very uncomfortable about "patching up" UPDATE information
and passing it to other peers without being fully clear about
whether there's a sufficiently long path that actually _uses_
the route.

>      The draft-ieft-idr-error-handling, for example, suggests
>      that invalid Attribute Flags may simply be overwritten
>      by the expected value.

   I confess to being less than comfortable with idr-error-handling.
So I'll let others discuss how wise this is...

> I would then divide the forms of error into (1) "framing" and (2)
> "content" (or "semantic").
> 
> A BGP UPDATE message has three levels of framing:
> 
>   * Level 1 -- the 16 octet "Marker" + Message Length
>                                      + Withdrawn Routes Length
>                                      + Total Path Attributes Length
> 
>     If the Message Length is broken, it is extremely likely that the
>     "Marker" on the next message will be invalid.

   This sort of error clearly qualifies as "broken peer".

>   * Level 2(a) -- the Withdrawn Routes
> 
>     Each prefix must have a valid prefix length, and the last
>     must run exactly to the end of this part of the message.

   This would appear to qualify as "broken peer"

>   * Level 2(b) -- the Attributes
> 
>     Each attribute must be correctly framed, and at the end of the
>     attributes the last one must run to exactly the end of the
>     attribute part of the message.

   To the extent that type-length-value triplets should match total
path attribute length, this failure would indicate "broken peer".

>   * Level 2(c) -- the Network Layer Reachability Information.
> 
>     Same as 2(a).
> 
>   * Level 3 -- various Attributes
> 
>     Some attributes have internal framing.

   Indeed!

> So far, so obvious.  To judge if an individual attribute is properly
> framed, we need to consider the red-tape:
> 
>   * the Flags octet has a limited set of valid values, depending
>     on the Type.

   True, but probably not all BGP speakers check all of these...

>   * the Type may be more or less anything, but repeats are not
>     valid.

   Again, not all BGP speakers necessarily check this...

>   * the Length is constrained for some Types

   I suspect such checks are rather spotty...

> There is some redundancy here, more for known types than unknown ones,
> which helps.  The Total Path Attributes Length is, effectively, a
> checksum for all the Lengths of all the Attributes.  It would be
> possible to specify that a set of attributes should be deemed
> correctly framed solely on the basis of passing that test.

   This feels like the wrong question. Failing that test does indicate
a broken peer, but passing it doesn't prove the attributes safe to
send to a peer.

> However, my feeling is that all the available redundancy (such as
> it is) should be used to minimise the possibility of accepting a
> broken attributes
> -- *particularly* where an error is going to be treated as Ignorable.

   Yes, I am uncomfortable here.

   It's probably a good practice to check such minutiae (even for
attributes you know you don't care about), but it's foolish to hope
we can get such checking to be uniform.

   And it's not clear what actual harm would come from inconsistent
checking of such minutiae...

> Once attributes are correctly framed, then one can consider their
> content.  Wherever the line between framing and content is drawn, I
> think it helps to be clear about the distinction between them --
> "framing" errors affect the attribute and the attributes around it,
> "content" errors affect only the attribute.

   I like that distinction (though my primary concern is distinguishing
a broken peer from a careless peer).

> The framing of an Optional Transitive is a special case.  If the
> parser recognises an Optional Transitive, but its Length is not valid,
> what should the receiver do ?

   It depends on what the meaning of "not valid" is...

> If the sender did not understand the
> Attribute, then the broken Length is a "content" issue.  If the sender
> did understand it, then the broken Length is a "framing" issue.  (It
> is a serious disappointment to me that the Partial bit does not help
> here.  But even if it did, what if the sender made a mess of
> setting/clearing it !?)

   As I've said for years, "Error-correction is the most error-prone
operation in computing." :^(

> In section 2.1.2 the draft specifies a number of "Semantic BGP
> Errors", which includes many things which I would class as "framing"
> errors.

   Indeed, I prefer to think in terms of "framing".

> This is all pretty low level stuff.  I can hear an argument that the
> requirements document is not the place for this level of detail.
> However, without a more precise understanding of how broken attributes
> may be parsed, requirements for how to deal with them are hard to
> specify and to interpret.

   Especially if we try to "correct" errors!

> If NLRI were explicitly separate from the attributes, then if a set of
> attributes fails a strict "framing" check, then "treat-as-withdraw"
> (or equivalent) could be applied, reliably.  This seems to me to be as
> safe as possible, short of dropping the session (which has its own
> safety issues).
> 
> With NLRI mixed up in the attributes, either one plays safe and treats
> all attribute errors as Critical, or a much more detailed analysis of
> attribute parsing is required.  What is the cost of missing some NLRI
> which were sent, but were obscured by some other broken attribute ?
> What is the risk ?  What degree of broken-ness of an attribute can be
> deemed not to invalidate the parsing of the attributes before and/or
> after it ?  Is that different for different attributes ?

   This deserves discussion...

> In order to contemplate classifying some attribute errors as
> "Ignorable" or "Recoverable", a more detailed analysis of attribute
> parsing is also required.  An ATOMIC_AGGREGATE attribute is arguably
> trivial and Ignorable.  But is an ATOMIC_AGGREGATE attribute with a
> length of 421 (say) likely to be a momentary lapse of concentration at
> the sender end, or more likely to be a symptom of a badly broken set
> of attributes ? 

   That's something I'd guess most peers can't be bothered to check.

--
John Leslie <john@jlc.net>

From chris.hall@highwayman.com  Fri Aug 31 09:38:39 2012
Return-Path: <chris.hall@highwayman.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 77C8021F85A1; Fri, 31 Aug 2012 09:38:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.477
X-Spam-Level: 
X-Spam-Status: No, score=-98.477 tagged_above=-999 required=5 tests=[AWL=1.235, BAYES_00=-2.599, HELO_MISMATCH_UK=1.749, HOST_MISMATCH_NET=0.311, J_CHICKENPOX_66=0.6, SARE_SUB_OBFU_Q1=0.227, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LL+3NBEAhlBV; Fri, 31 Aug 2012 09:38:38 -0700 (PDT)
Received: from smtp.demon.co.uk (mdfmta010.mxout.tbr.inty.net [91.221.168.51]) by ietfa.amsl.com (Postfix) with ESMTP id 4173321F858A; Fri, 31 Aug 2012 09:38:37 -0700 (PDT)
Received: from mdfmta010.tbr.inty.net (unknown [127.0.0.1]) by mdfmta010.tbr.inty.net (Postfix) with ESMTP id B0AE76F8125; Fri, 31 Aug 2012 17:38:36 +0100 (BST)
Received: from mdfmta010.tbr.inty.net (unknown [127.0.0.1])	by mdfmta010.tbr.inty.net (Postfix) with ESMTP id 68A8E6F80DC; Fri, 31 Aug 2012 17:38:36 +0100 (BST)
Received: from hestia.halldom.com (unknown [80.177.246.130])	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))	(No client certificate requested)	by mdfmta010.tbr.inty.net (Postfix) with ESMTP; Fri, 31 Aug 2012 17:38:36 +0100 (BST)
Received: from hyperion.halldom.com ([80.177.246.170] helo=HYPERION)	by hestia.halldom.com with esmtpsa (TLSv1:AES128-SHA:128)	(Exim 4.76)	(envelope-from <chris.hall@highwayman.com>)	id 1T7UEt-0003iU-HX; Fri, 31 Aug 2012 16:38:35 +0000
From: "Chris Hall" <chris.hall@highwayman.com>
To: "'idr wg'" <idr@ietf.org>,	<grow@ietf.org>
References: <066901cd874e$fa0605f0$ee1211d0$@highwayman.com> <20120831145428.GX72831@verdi>
In-Reply-To: <20120831145428.GX72831@verdi>
Date: Fri, 31 Aug 2012 17:38:30 +0100
Organization: Highwayman
Message-ID: <06f601cd8797$10c1f310$3245d930$@highwayman.com>
MIME-Version: 1.0
Content-Type: text/plain;	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
thread-index: AQJn9OxjujSjCTsYygfO8NLLdB3mFwIfNcyPli4x2+A=
Content-Language: en-gb
X-MDF-HostID: 3
X-Mailman-Approved-At: Fri, 31 Aug 2012 12:09:50 -0700
Cc: 'John Leslie' <john@jlc.net>
Subject: Re: [GROW] [Idr] draft-ietf-grow-ops-reqs-for-bgp-error-handling-05
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, 31 Aug 2012 16:38:39 -0000

John Leslie wrote (on Fri 31-Aug-2012 at 15:54 +0100):
> Chris Hall <chris.hall@highwayman.com> wrote:
...
> > It seems to me that there are four severities/responses:
> >
> >   1) "Critical Error" -> drop/restart session or AFI/SAFI
> >
> >      So the overall response then depends on how gracefully the
> >      session drop and/or restart can be handled.

> BGP was designed for a naive case where all your peers were
> either dependable or broken. Moving beyond that has proven
> difficult. :^(

Certainly I have found it tricky when trying to do some of the things
in draft-ietf-idr-error-handling in Quagga !

>  But we should recognize the "fully broken" case, which amounts to
> "drop the session and be in no hurry to try that peer again".

One of my concerns with improving error handling is that however
inconvenient dropping an entire session may be, and how disruptive
repeatedly dropping and restarting sessions is, at least it draws
attention to a problem.  If the error handling becomes too smooth, on
the other hand may hide problems.

>    Arguably, this should even require human intervention before
> trying another session, but I have no horse in that race...
> 
>    It is indeed interesting to consider that one AFI/SAFI may be
> "fully broken" while others seem dependable: perhaps we should
> consider dropping only the part of a session concerning that
> AFI/SAFI...

So, I guess by "Critical" what one really means is some error which is
so severe that all NLRI (possibly only for a subset of AFI/SAFI)
learned during the session are suspect.  Suspect because the current
UPDATE message refers to some NLRI (possibly in a subset of AFI/SAFI
for the session) are affected by the broken UPDATE, but it's not
possible to be sure which ones.

> >   2) "Serious Error" -> do something with NLRI, short of
> >      dropping the session.

>    This is a bit vague...

So, I think the distinction between Critical and Serious is that for a
Serious error it is possible to identify the NLRI which the broken
UPDATE refers to, but not possible to identify enough of the
Attributes to be sure of the new state of those NLRI.  So, whatever
the problem is, it is limited to these NLRI, and all other NLRI may be
assumed to be unchanged.

What degree of proof is required to be sure (or sure enough) of being
able to identify the NLRI is the crux of the matter when it comes to
discussing how the parsing of attributes should proceed in the face of
errors.
 
> >      The "treat-as-withdraw" mechanism is mentioned.

> This is appropriate when we have reason to believe the peer is
> dependable, but is passing us NLRI routing information we're not
> willing to trust.  IMHO, "not willing to trust" is in the eye of
> the beholder...

It would clearly be possible to treat all errors as prima facie
evidence that the peer has left the reservation and is unlikely to
return to their senses any time soon, so that the only sensible
response is to forget all their routes.

So, yes, I think you are correctly observing that there are a number
of possible responses to each of the different severities of error.
The distinction is that with a Serious error the response *can* be
limited to the NLRI in the UPDATE, but for a Critical error it cannot.

...
> >      But I think that the requirements should address what outcome
> >      is expected if errors in an individual UPDATE message are to
> >      be limited to that message.  I think what that means is:
> >
> >        * it must be possible to identify all NLRI that the message
> >          could be carrying.

>    I read this to mean that all length+prefix must be readable
> (but not necessarily considered valid), whether or not the path
> attributes make sense.

I think that this requirement is best met by separating NLRI from
Attributes.  Then, if all the NLRI have valid lengths, and those add
up to the total length of the NLRI section(s), then you have
identified the NLRI.  For me, anything short of that should be deemed
a Critical error.

...
> >        * whatever is done with those NLRI must reflect the fact
> >          that the recipient has an incomplete, possibly empty,
> >          set of attributes for those NLRI.

>    I take this to mean there's something about the attributes we
> don't choose to trust: thus our picture of the "usable" attributes
> differs from that of our peer. (Indeed, we may choose to trust
> none of them.)

Yes.

> >   3) "Ignorable Error" -> process the UPDATE message as if the
> >      ignored attributes

>    Some words seem to have gotten lost in tranport...

:-(  ...as if the ignored attributes were not there.

...
> >      Some errors in Optional Transitive may be dealt with by
> >      ignoring the attribute altogether.  The requirements
> >      mention this, but do not specify criteria for being
> >      ignorable.

> "Optional Transitive" is well-defined. Perhaps some advertised
> capabilities are less well-defined...

What I was trying to get at is this: clearly a BGP implementation
which does not understand a given Optional Transitive attribute is
able to use the route(s) without it.  Perhaps this means that if an
implementation which does understand the attribute, but finds that it
is not valid in some way, could simply pretend not to understand it ?
Or, does some greater responsibility come with greater knowledge ?

> >   4) "Recoverable Error" -> process the UPDATE message which has
> >      had errors "patched up".

>    This sounds dangerous.

Amen to that.

...
> > So far, so obvious.  To judge if an individual attribute is
> > properly framed, we need to consider the red-tape:
> >
> >   * the Flags octet has a limited set of valid values, depending
> >     on the Type.

>    True, but probably not all BGP speakers check all of these...

> >   * the Type may be more or less anything, but repeats are not
> >     valid.

>    Again, not all BGP speakers necessarily check this...

> >   * the Length is constrained for some Types

>    I suspect such checks are rather spotty...

Hmmm.  I can only speak for the Quagga stuff I am working on, which
works through the attributes it knows about with a fine tooth comb.

...
>    It's probably a good practice to check such minutiae (even for
> attributes you know you don't care about), but it's foolish to hope
> we can get such checking to be uniform.
> 
>    And it's not clear what actual harm would come from inconsistent
> checking of such minutiae...

As I see it the problem is this: in order to be able to treat errors
in an UPDATE as Serious, but not Critical, it is essential that the
receiver be able to at least identify the NLRI with some (high?) level
of confidence.  While NLRI are mixed up with the Attributes (a bona
fide, first class, copper bottomed KLUDGE, IMNSHO) achieving that
requires some careful analysis of how Attributes are parsed when they
are broken.

Grinding out the detail is sort of an argument for separating NLRI
from Attributes.  The same detail is relevant to efforts to loosen
checks on Attributes, as suggested in draft-ietf-idr-error-handling.

The actual harm which could come from inadequate parsing of
Attributes, is that some NLRI in a broken UPDATE message could be
missed -- that is, some errors in an UPDATE could be treated as
Serious, where they should be treated as Critical.  It's possible that
the risk of such an outcome is acceptable... but I don't think the
requirements cover it.

...
> > In order to contemplate classifying some attribute errors as
> > "Ignorable" or "Recoverable", a more detailed analysis of
> > attribute parsing is also required.  An ATOMIC_AGGREGATE
> > attribute is arguably trivial and Ignorable.  But is an
> > ATOMIC_AGGREGATE attribute with length of 421 (say) likely 
> > to be a momentary lapse of concentration at the sender end,
> > or more likely to be a symptom of a badly broken set
> > of attributes ?

> That's something I'd guess most peers can't be bothered to check.

Goodness.  I do hope that's not the case :-(

Chris

