
From russw@riw.us  Tue Oct  2 14:20:51 2012
Return-Path: <russw@riw.us>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC95921F85ED for <grow@ietfa.amsl.com>; Tue,  2 Oct 2012 14:20:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.67
X-Spam-Level: 
X-Spam-Status: No, score=-1.67 tagged_above=-999 required=5 tests=[AWL=-0.930,  BAYES_20=-0.74]
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 Gax+StwLv8Mn for <grow@ietfa.amsl.com>; Tue,  2 Oct 2012 14:20:45 -0700 (PDT)
Received: from da31.namelessnet.net (da31.namelessnet.net [74.124.205.66]) by ietfa.amsl.com (Postfix) with ESMTP id 2256721F85EA for <grow@ietf.org>; Tue,  2 Oct 2012 14:20:42 -0700 (PDT)
Received: from cpe-065-190-156-032.nc.res.rr.com ([65.190.156.32] helo=[192.168.100.51]) by da31.namelessnet.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.77) (envelope-from <russw@riw.us>) id 1TJ9tR-0004CO-EO for grow@ietf.org; Tue, 02 Oct 2012 14:20:41 -0700
Message-ID: <506B5AA9.8000400@riw.us>
Date: Tue, 02 Oct 2012 17:20:41 -0400
From: Russ White <russw@riw.us>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120907 Thunderbird/15.0.1
MIME-Version: 1.0
To: grow@ietf.org
References: <CC5BE44F.2A792%pds@lugs.com> <CAP-guGXL6-AkPSnMJ7TY-dVafOMXKtFNQCUdKcrVGrbHoQNSXQ@mail.gmail.com> <CAL9jLaYGu3mOKEFGESEm8EmtH5bhijV1AhjYi44_4Kqv=2-2SQ@mail.gmail.com> <20120925201954.GG1854@pfrc>
In-Reply-To: <20120925201954.GG1854@pfrc>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Antivirus-Scanner: Seems clean.  You should still use an Antivirus Scanner
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: Tue, 02 Oct 2012 21:20:51 -0000

I haven't been keeping up on email very well, but...

> - Path information is lost.  While this doesn't impact loop prevention, this
>   information is operationally useful.  I'll offer the counter that this is
>   already done today through explicit policy, typically either because the
>   operator knows this is safe or because they simply don't care about the
>   consequences to forwarding.

I don't get how path information is lost in this draft. The AS Path is
not altered in any advertisement, so it's not like aggregation, where
you replace a series of AS' with a single AS, or anything like that.
Path information is no more lost than with simple filtering for various
other reasons.

> - In several cases, the more specific prefix may be information that is
>   *not* present from the originating AS - i.e. a subnet has "wandered away".
>   Such situations will become increasingly common as the Internet
>   deaggregates under pressure of address space exhaustion.  This is my
>   primary concern.

I don't get this one, either... Your concern is that the mechanism
explained will become less useful over time as aggregation becomes less
possible because of greater spreading of origination... I'm not certain
why we should read this... "We shouldn't document or use ideas that
aren't 100% effective, or won't be 100% effective in the future?"

Can you clarify what you're actually saying here?

>   - The draft does suggest you can look at the AS_PATH.  This is certainly
>     much safer if you ensure that the less and more specific routes share a
>     common origin AS.

No, not really... The decision point is whether or not the additional
path will impact forwarding at the neighboring AS, not whether or not
the route is the same in some way. I don't much care if the origin AS is
the same, so long as the traffic will pass to the same neighboring AS to
reach the destination.

Aggregation, in fact, is based on the principle that as you come closer
to the actual destination, routing information becomes more specific. If
we take this objection to heart, we should disallow aggregation of all
types in all routing systems.

>   - But even if they do share a common origin AS, if you have an internal AS
>     partition, things may be unhappy if the more specific provided you
>     forwarding coverage and it got suppressed.

AS partitions are already handled in the draft as written. If the two
routers with overlapping prefixes aren't reachable through iBGP (no
matter what their AS numbers might happen to me), then the mechanism
won't suppress the longer prefix.

> - Tying the fate of the routes together will likely yield some interesting
>   route flaps as covering prefixes come and go, especially as part of iBGP
>   churn.  

Churn due to route flaps is a problem outside of aggregation of routing
information --in fact, this proposal is likely to reduce churn, rather
than increase it, by suppressing longer prefixes, which tend to be less
stable.

>   - I'm vaguely concerned there may be scenarios where astable route
>     announcements happen during some convergence scenario, but I haven't
>     figured one out yet.  If such can happen, our friend policy would
>     probably be involved. :-)

I'm not convinced we should disallow solutions because of vague
feelings... Can you actually find a situation so we can analyze whether
or not it impacts operation?

> Note that some of these arguments appeared in a different form while
> discussing the ATOMIC_AGGREGATE feature in BGP during the RFC 4271
> standardization process.

Since this proposal doesn't use ATOMIC_AGGREGATE, none of these
objections apply...

:-)

Russ

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

From russw@riw.us  Tue Oct  2 14:23:07 2012
Return-Path: <russw@riw.us>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CDD6E21F8433 for <grow@ietfa.amsl.com>; Tue,  2 Oct 2012 14:23:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.134
X-Spam-Level: 
X-Spam-Status: No, score=-2.134 tagged_above=-999 required=5 tests=[AWL=0.465,  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 Rge76ocN2a+i for <grow@ietfa.amsl.com>; Tue,  2 Oct 2012 14:23:07 -0700 (PDT)
Received: from da31.namelessnet.net (da31.namelessnet.net [74.124.205.66]) by ietfa.amsl.com (Postfix) with ESMTP id 0895021F85F0 for <grow@ietf.org>; Tue,  2 Oct 2012 14:23:07 -0700 (PDT)
Received: from cpe-065-190-156-032.nc.res.rr.com ([65.190.156.32] helo=[192.168.100.51]) by da31.namelessnet.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.77) (envelope-from <russw@riw.us>) id 1TJ9vm-0004GU-Rq for grow@ietf.org; Tue, 02 Oct 2012 14:23:06 -0700
Message-ID: <506B5B3B.1020507@riw.us>
Date: Tue, 02 Oct 2012 17:23:07 -0400
From: Russ White <russw@riw.us>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120907 Thunderbird/15.0.1
MIME-Version: 1.0
To: grow@ietf.org
References: <CC5BE44F.2A792%pds@lugs.com> <CAP-guGXL6-AkPSnMJ7TY-dVafOMXKtFNQCUdKcrVGrbHoQNSXQ@mail.gmail.com> <CAL9jLaYGu3mOKEFGESEm8EmtH5bhijV1AhjYi44_4Kqv=2-2SQ@mail.gmail.com> <20120925201954.GG1854@pfrc> <5062BAE8.6010801@inex.ie>
In-Reply-To: <5062BAE8.6010801@inex.ie>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Antivirus-Scanner: Seems clean.  You should still use an Antivirus Scanner
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: Tue, 02 Oct 2012 21:23:07 -0000

>> - Path information is lost.  While this doesn't impact loop prevention, this
>>   information is operationally useful.
> 
> +1.  Reachability data optimisation is highly desirable and may one day be
> necessary, but this is one of the wrong places to do it.

Again, I'm a bit baffled. Can you explain how this draft actually
removes reachability optimization in the DFZ? It's carefully crafted NOT
to remove any reachability information that produces a shorter path.

I know the chairs have already (short sightedly, IMHO), decided not to
accept this draft as a WG item, but I'd really like to understand what
specific situation you can draw up where the proposed mechanism
increases the stretch in any path.

:-)

Russ


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

From wherrin@gmail.com  Tue Oct  2 14:46:29 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 8189D21F8605 for <grow@ietfa.amsl.com>; Tue,  2 Oct 2012 14:46:29 -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 wIHKIc+vvxO7 for <grow@ietfa.amsl.com>; Tue,  2 Oct 2012 14:46:28 -0700 (PDT)
Received: from mail-pa0-f44.google.com (mail-pa0-f44.google.com [209.85.220.44]) by ietfa.amsl.com (Postfix) with ESMTP id D516D21F846C for <grow@ietf.org>; Tue,  2 Oct 2012 14:46:27 -0700 (PDT)
Received: by padfb11 with SMTP id fb11so5754009pad.31 for <grow@ietf.org>; Tue, 02 Oct 2012 14:46:20 -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=pRi3UGIqf/haorUz2Mz9mH1xGimtb8c8qo9V3McBWUI=; b=S8BU1nLXFQjI2FCPrdkO41JqJ+OOfskqQjIHe8WmpB3jiTkkgYhf9wpq5XlNGjBeYk cdFqsfILgBrDyBILzuE7yOhHjx4yrjA5bnmjJrJ1PsjGQBiWB4d/IA2vRdaGUeaop6Nl +ezC4GZOvtVK/3XSqZrvVUgHaoOp4L7/W5wJQnncnstH5mUJiIoRKp5gaOeJ2/08dE1N zVTa4DP576eCbs/Aduq86P7ARY8dcciVNicXbmC71r5fLw8OkYvN/S5/J471ux3WG/MY 6YSc+NnVwoJFWfXCG6lkt6kYKWtYmIPKcx3jAkmh5+5WGYrs8gRwOkkxb9z4znyR3ov5 ARdw==
Received: by 10.66.72.132 with SMTP id d4mr100259pav.61.1349214380804; Tue, 02 Oct 2012 14:46:20 -0700 (PDT)
MIME-Version: 1.0
Sender: wherrin@gmail.com
Received: by 10.68.196.200 with HTTP; Tue, 2 Oct 2012 14:46:00 -0700 (PDT)
In-Reply-To: <506B5AA9.8000400@riw.us>
References: <CC5BE44F.2A792%pds@lugs.com> <CAP-guGXL6-AkPSnMJ7TY-dVafOMXKtFNQCUdKcrVGrbHoQNSXQ@mail.gmail.com> <CAL9jLaYGu3mOKEFGESEm8EmtH5bhijV1AhjYi44_4Kqv=2-2SQ@mail.gmail.com> <20120925201954.GG1854@pfrc> <506B5AA9.8000400@riw.us>
From: William Herrin <bill@herrin.us>
Date: Tue, 2 Oct 2012 17:46:00 -0400
X-Google-Sender-Auth: Zd9SPU2Vv67Fri6WnsBexvAOHx4
Message-ID: <CAP-guGXpfT46+mP_Q-uvrWmFbt_pOfEYw3HqtLRg98WweKK3bA@mail.gmail.com>
To: Russ White <russw@riw.us>
Content-Type: text/plain; charset=ISO-8859-1
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: Tue, 02 Oct 2012 21:46:29 -0000

On Tue, Oct 2, 2012 at 5:20 PM, Russ White <russw@riw.us> wrote:
>> - Path information is lost.  While this doesn't impact loop prevention, this
>>   information is operationally useful.  I'll offer the counter that this is
>>   already done today through explicit policy, typically either because the
>>   operator knows this is safe or because they simply don't care about the
>>   consequences to forwarding.
>
> I don't get how path information is lost in this draft. The AS Path is
> not altered in any advertisement, so it's not like aggregation, where
> you replace a series of AS' with a single AS, or anything like that.

Hi Russ,

10.1.0.0/16 AS path 12 5 4 2
10.1.1.0/24 AS path 12 1

The 12->1 path, 1 being a completely different origin AS than the
covering route's origin from 2, is lost when 10.1.1.0/24 is aggregated
into 10.1.0.0/16.


>> - In several cases, the more specific prefix may be information that is
>>   *not* present from the originating AS - i.e. a subnet has "wandered away".
>>   Such situations will become increasingly common as the Internet
>>   deaggregates under pressure of address space exhaustion.  This is my
>>   primary concern.
>
> I don't get this one, either...

The prior example exhibits this case as well.


>>   - But even if they do share a common origin AS, if you have an internal AS
>>     partition, things may be unhappy if the more specific provided you
>>     forwarding coverage and it got suppressed.
>
> AS partitions are already handled in the draft as written. If the two
> routers with overlapping prefixes aren't reachable through iBGP (no
> matter what their AS numbers might happen to me), then the mechanism
> won't suppress the longer prefix.

Suppose an Internet-connected network consists of site A and site B.
10.1.1.0/24 is advertised from and used by site A while 10.1.2.0/24 is
advertised from and used by site site B. Both sites advertise
10.1.0.0/16. Sites A and B are connected to each other, so if site A
receives a packet for 10.1.2.1, it will forward it to site B.

If site B should lose its internet connection, packets for 10.1.2.1
will follow the covering route via site A and still reach site B.
Regardless of aggregation.

Instead, lose the connection from site A to site B but keep both sites
connected to the Internet. The covering route continues to appear at
your router but if you send 10.1.2.1 to site A because you discarded
the more specific route, you have black-holed that packet. Even though
site B is connected to the Internet.


In normal operation, another nasty problem appears. Site A is in
London. Site B is in Honolulu. You're in Chicago. Your packet to
10.1.2.1 follows the closest aggregated route to London before it can
travel to Honolulu, adding thousands of miles and near a hundred
milliseconds to its trip.

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 jared@puck.nether.net  Tue Oct  2 15:44:12 2012
Return-Path: <jared@puck.nether.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 7567521F8618 for <grow@ietfa.amsl.com>; Tue,  2 Oct 2012 15:44:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.799
X-Spam-Level: 
X-Spam-Status: No, score=-1.799 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SARE_BAYES_7x5=0.8]
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 8Ha0GJRrLFmy for <grow@ietfa.amsl.com>; Tue,  2 Oct 2012 15:44:11 -0700 (PDT)
Received: from puck.nether.net (puck.nether.net [IPv6:2001:418:3f4::5]) by ietfa.amsl.com (Postfix) with ESMTP id B1A8721F8602 for <grow@ietf.org>; Tue,  2 Oct 2012 15:44:11 -0700 (PDT)
Received: from [10.0.1.2] (support01.sterling.verio.net [207.153.206.12]) (authenticated bits=0) by puck.nether.net (8.14.4/8.14.4) with ESMTP id q92Mi1v8012063 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 2 Oct 2012 18:44:02 -0400
Mime-Version: 1.0 (Mac OS X Mail 6.1 \(1498\))
Content-Type: text/plain; charset=us-ascii
From: Jared Mauch <jared@puck.nether.net>
In-Reply-To: <506B5B3B.1020507@riw.us>
Date: Tue, 2 Oct 2012 18:44:10 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <8121770B-66E1-47A9-90B5-563D0E106939@puck.nether.net>
References: <CC5BE44F.2A792%pds@lugs.com> <CAP-guGXL6-AkPSnMJ7TY-dVafOMXKtFNQCUdKcrVGrbHoQNSXQ@mail.gmail.com> <CAL9jLaYGu3mOKEFGESEm8EmtH5bhijV1AhjYi44_4Kqv=2-2SQ@mail.gmail.com> <20120925201954.GG1854@pfrc> <5062BAE8.6010801@inex.ie> <506B5B3B.1020507@riw.us>
To: Russ White <russw@riw.us>
X-Mailer: Apple Mail (2.1498)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (puck.nether.net [204.42.254.5]); Tue, 02 Oct 2012 18:44:02 -0400 (EDT)
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: Tue, 02 Oct 2012 22:44:12 -0000

On Oct 2, 2012, at 5:23 PM, Russ White <russw@riw.us> wrote:

>>>=20
>>> - Path information is lost.  While this doesn't impact loop =
prevention, this
>>>  information is operationally useful.
>>=20
>> +1.  Reachability data optimisation is highly desirable and may one =
day be
>> necessary, but this is one of the wrong places to do it.
>=20
> Again, I'm a bit baffled. Can you explain how this draft actually
> removes reachability optimization in the DFZ? It's carefully crafted =
NOT
> to remove any reachability information that produces a shorter path.
>=20
> I know the chairs have already (short sightedly, IMHO), decided not to
> accept this draft as a WG item, but I'd really like to understand what
> specific situation you can draw up where the proposed mechanism
> increases the stretch in any path.

Russ,

The problem as I see it is many of those that operate in the BGP/DFZ =
don't know what they are doing.

This makes solving these problems infinitely more complex compared to =
how they should be if everyone was sane.


58.64.162.0/24	 2497 701 6453 45474 174 17444=20

is a great example for me and easily observed (even if just as a =
transitory announcement).

I see this in my router, but the above leaked out...

*>i58.64.160.0/19     x.x.x.x                120      0 17444 17444 =
17444 17444 17444 17444 17444 i

Not only did the above route look disgusting for the as_path, but there =
should have been some better covering prefixes appear perhaps?

Anyways, you can't make people route sanely and the ISPs have a hard =
time rejecting the money people want to pay for the extra flexibility.

- Jared=

From aretana@cisco.com  Wed Oct  3 06:29:22 2012
Return-Path: <aretana@cisco.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 415A521F8533 for <grow@ietfa.amsl.com>; Wed,  3 Oct 2012 06:29:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 K-dSvCbbfF3g for <grow@ietfa.amsl.com>; Wed,  3 Oct 2012 06:29:21 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) by ietfa.amsl.com (Postfix) with ESMTP id 214CB21F8525 for <grow@ietf.org>; Wed,  3 Oct 2012 06:29:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3831; q=dns/txt; s=iport; t=1349270961; x=1350480561; h=from:to:cc:subject:date:message-id:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=1kKySZ34HEGyZEJq73ZrgDI40vuyJVuKOjjMApztCLQ=; b=eRHmmUWRZ8Y+jjj0hBlgTY5XYqc3JIK3U0azQJbQVi1cbISNKK9i4kUY rRRTyUIBE56TcVeOL3aH50csnR+KwqECpS4mdY+rRe48a59ySwrvauOXi m/mrejIz3xYfjsiExi+zU8j/INOinIFFeKgyWFVyLENJANRPRx9vcFsJH Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av4EACg9bFCtJV2d/2dsb2JhbABFvnOBCIIgAQEBBBIBCgpSEgEIDgoKViUCBAENBQgMDodjmBOff4sjhVpgA6QrgWmCbYIX
X-IronPort-AV: E=Sophos;i="4.80,528,1344211200"; d="scan'208";a="127869541"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rcdn-iport-6.cisco.com with ESMTP; 03 Oct 2012 13:29:20 +0000
Received: from xhc-aln-x09.cisco.com (xhc-aln-x09.cisco.com [173.36.12.83]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id q93DTKVT023059 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 3 Oct 2012 13:29:20 GMT
Received: from xmb-aln-x15.cisco.com ([169.254.9.154]) by xhc-aln-x09.cisco.com ([173.36.12.83]) with mapi id 14.02.0318.001; Wed, 3 Oct 2012 08:29:20 -0500
From: "Alvaro Retana (aretana)" <aretana@cisco.com>
To: William Herrin <bill@herrin.us>, Russ White <russw@riw.us>
Thread-Topic: [GROW] Call for GROW WG adoption of grow-overlapping-routes
Thread-Index: AQHNoOPGM9uziy/yHka1Y9ZqlazVtZem4KkAgADEgYA=
Date: Wed, 3 Oct 2012 13:29:19 +0000
Message-ID: <BBD66FD99311804F80324E8139B3C94EA39EC4@xmb-aln-x15.cisco.com>
In-Reply-To: <CAP-guGXpfT46+mP_Q-uvrWmFbt_pOfEYw3HqtLRg98WweKK3bA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.82.250.17]
x-tm-as-product-ver: SMEX-10.2.0.1135-7.000.1014-19234.001
x-tm-as-result: No--40.643100-8.000000-31
x-tm-as-user-approved-sender: No
x-tm-as-user-blocked-sender: No
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <49524BE9A86D254AAD1E6B4A26B55C91@cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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: Wed, 03 Oct 2012 13:29:22 -0000

[Also catching up=8A]

Bill:

I want to say up front that the proposal is not for this draft to be a
standards track document and to have everyone do it by default.  It
provides a tool that people may want to use, as reflected by some interest
at the WG meeting.  This is why we intended the draft to be Experimental
at this point.

On 10/2/12 5:46 PM, "William Herrin" <bill@herrin.us> wrote:

>On Tue, Oct 2, 2012 at 5:20 PM, Russ White <russw@riw.us> wrote:
>>> - Path information is lost.  While this doesn't impact loop
>>>prevention, this
>>>   information is operationally useful.  I'll offer the counter that
>>>this is
>>>   already done today through explicit policy, typically either because
>>>the
>>>   operator knows this is safe or because they simply don't care about
>>>the
>>>   Consequences to forwarding.
>>
>> I don't get how path information is lost in this draft. The AS Path is
>> not altered in any advertisement, so it's not like aggregation, where
>> you replace a series of AS' with a single AS, or anything like that.
>
>Hi Russ,
>
>10.1.0.0/16 AS path 12 5 4 2
>10.1.1.0/24 AS path 12 1
>
>The 12->1 path, 1 being a completely different origin AS than the
>covering route's origin from 2, is lost when 10.1.1.0/24 is aggregated
>into 10.1.0.0/16.

The path is not aggregated.  Instead, the /24 would be marked as BOUNDED;
the draft explains what that means:

=3D=3D=3D=3D=3D
3.3 Handling Marked Routes Within the AS

   Routes marked with the BOUNDED community MAY not be installed in the
   local RIB of routers within the AS.  This optional step will reduce
   local RIB and forwarding table usage and volatility within the AS.

3.4 Handling Marked Routes at the Outbound Edge

   Routes marked with the BOUNDED community SHOULD NOT be advertised to
   external peers.  If they are advertised, they SHOULD then be marked
   with the NO_EXPORT community.
=3D=3D=3D=3D=3D

The proposal is for the /24 to not be advertised further.  I can see how
this looks like loss of path information.

However, we also wrote the following:

=3D=3D=3D=3D=3D
3.1 Marking Overlapping Routes

   As each prefix is received by a BGP speaker from an external peer, it
   is evaluated in the light of other prefixes already received.  If two
   prefixes overlap in space (such as 192.0.2.0/24 and 192.0.2.128/25),
   the longer prefix SHOULD be BOUNDED.

   A BGP speaker MAY also choose to check the AS_PATH attribute length
   and contents before marking a prefix as BOUNDED.
=3D=3D=3D=3D=3D

The intent of the last paragraph was to have the local network decide
whether the AS_PATH should somehow match or not.

Given the comments, maybe we should change the 'MAY' above for 'SHOULD'
(??), and clarify what the checking would/could entail.



..
>>>   - But even if they do share a common origin AS, if you have an
>>>internal AS
>>>     partition, things may be unhappy if the more specific provided you
>>>     forwarding coverage and it got suppressed.
>>
>> AS partitions are already handled in the draft as written. If the two
>> routers with overlapping prefixes aren't reachable through iBGP (no
>> matter what their AS numbers might happen to me), then the mechanism
>> won't suppress the longer prefix.
>
>Suppose an Internet-connected network consists of site A and site B.
..

Yes, that is a problem.

I do want to note that the same problem exists today if the more specific
route is discarded due to a policy related to the length of the prefixes
accepted by a given SP -- or any other such policy that can be implemented
with a manual filter.  As with the manual filter (as I said above), our
proposal is optional, it is intended to facilitate the operation if you
want to use it..

Thanks!

Alvaro.


From aretana@cisco.com  Wed Oct  3 06:29:57 2012
Return-Path: <aretana@cisco.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6569C21F8510 for <grow@ietfa.amsl.com>; Wed,  3 Oct 2012 06:29:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 TmJ+ZzZ0UBeH for <grow@ietfa.amsl.com>; Wed,  3 Oct 2012 06:29:56 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) by ietfa.amsl.com (Postfix) with ESMTP id 8E29D21F8570 for <grow@ietf.org>; Wed,  3 Oct 2012 06:29:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2124; q=dns/txt; s=iport; t=1349270996; x=1350480596; h=from:to:cc:subject:date:message-id:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=12JbHysxAjwWS58/mKaRtGD+GD4QnamOFmUrdKuaHqQ=; b=Jocm9HC/QnP7bKptgDyUDOW3r1ZnedCQiT3lO7gl5QYC/006/SdGxJXB zhUaub/+gZx+5M8MGPWVfyyYLINCuHXoB2Z0wQk/h2KpR2grIjd2oWzUI 1NM0jezkWBLSAXu6fmmfJwIwTZdJy1c8/End6f5DpNIhBgH/+x3dUxyFH U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av4EAGU8bFCtJV2d/2dsb2JhbABFvnOBCIIgAQEBBBIBClwSAQgYClYlAgQBDQUIGodjmBiff4sjCoVQYAOkK4Fpgm2CFw
X-IronPort-AV: E=Sophos;i="4.80,528,1344211200"; d="scan'208";a="127649604"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rcdn-iport-1.cisco.com with ESMTP; 03 Oct 2012 13:29:51 +0000
Received: from xhc-rcd-x03.cisco.com (xhc-rcd-x03.cisco.com [173.37.183.77]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id q93DToFA023676 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 3 Oct 2012 13:29:51 GMT
Received: from xmb-aln-x15.cisco.com ([169.254.9.154]) by xhc-rcd-x03.cisco.com ([173.37.183.77]) with mapi id 14.02.0318.001; Wed, 3 Oct 2012 08:29:50 -0500
From: "Alvaro Retana (aretana)" <aretana@cisco.com>
To: Jared Mauch <jared@puck.nether.net>, Russ White <russw@riw.us>
Thread-Topic: [GROW] Call for GROW WG adoption of grow-overlapping-routes
Thread-Index: AQHNoOQdM9uziy/yHka1Y9ZqlazVtZem8OkAgAC0ZIA=
Date: Wed, 3 Oct 2012 13:29:50 +0000
Message-ID: <BBD66FD99311804F80324E8139B3C94EA39EF7@xmb-aln-x15.cisco.com>
In-Reply-To: <8121770B-66E1-47A9-90B5-563D0E106939@puck.nether.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.82.250.17]
x-tm-as-product-ver: SMEX-10.2.0.1135-7.000.1014-19234.001
x-tm-as-result: No--35.977600-8.000000-31
x-tm-as-user-approved-sender: No
x-tm-as-user-blocked-sender: No
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <80884F1019768C4BA001AC928106337A@cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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: Wed, 03 Oct 2012 13:29:57 -0000

Jared:

On 10/2/12 6:44 PM, "Jared Mauch" <jared@puck.nether.net> wrote:

>
>On Oct 2, 2012, at 5:23 PM, Russ White <russw@riw.us> wrote:
>
>>>>=20
>>>> - Path information is lost.  While this doesn't impact loop
>>>>prevention, this
>>>>  information is operationally useful.
>>>=20
>>> +1.  Reachability data optimisation is highly desirable and may one
>>>day be
>>> necessary, but this is one of the wrong places to do it.
>>=20
>> Again, I'm a bit baffled. Can you explain how this draft actually
>> removes reachability optimization in the DFZ? It's carefully crafted NOT
>> to remove any reachability information that produces a shorter path.
>>=20
>> I know the chairs have already (short sightedly, IMHO), decided not to
>> accept this draft as a WG item, but I'd really like to understand what
>> specific situation you can draw up where the proposed mechanism
>> increases the stretch in any path.
>
>Russ,
>
>The problem as I see it is many of those that operate in the BGP/DFZ
>don't know what they are doing.
>
>This makes solving these problems infinitely more complex compared to how
>they should be if everyone was sane.
>
>
>58.64.162.0/24	 2497 701 6453 45474 174 17444
>
>is a great example for me and easily observed (even if just as a
>transitory announcement).
>
>I see this in my router, but the above leaked out...
>
>*>i58.64.160.0/19     x.x.x.x                120      0 17444 17444 17444
>17444 17444 17444 17444 i
>
>Not only did the above route look disgusting for the as_path, but there
>should have been some better covering prefixes appear perhaps?
>
>Anyways, you can't make people route sanely and the ISPs have a hard time
>rejecting the money people want to pay for the extra flexibility.

I agree.  Which is why our proposal is optional; if you want to do it, you
can enable it=8Aas you can manually filter blocks of routes today or make
all the exceptions you want (or are paid for).

For the example above, we do need to better articulate the "rules" around
checking the AS_PATH before making a decision.

Thanks!

Alvaro.


From russw@riw.us  Wed Oct  3 07:20:17 2012
Return-Path: <russw@riw.us>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D0D321F85B6 for <grow@ietfa.amsl.com>; Wed,  3 Oct 2012 07:20:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.289
X-Spam-Level: 
X-Spam-Status: No, score=-2.289 tagged_above=-999 required=5 tests=[AWL=0.310,  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 tI9VBLajiXtX for <grow@ietfa.amsl.com>; Wed,  3 Oct 2012 07:20:16 -0700 (PDT)
Received: from da31.namelessnet.net (da31.namelessnet.net [74.124.205.66]) by ietfa.amsl.com (Postfix) with ESMTP id E3C7421F85AA for <grow@ietf.org>; Wed,  3 Oct 2012 07:20:16 -0700 (PDT)
Received: from cpe-065-190-156-032.nc.res.rr.com ([65.190.156.32] helo=[192.168.100.51]) by da31.namelessnet.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.77) (envelope-from <russw@riw.us>) id 1TJPo2-0003Y5-8D; Wed, 03 Oct 2012 07:20:10 -0700
Message-ID: <506C4996.7010909@riw.us>
Date: Wed, 03 Oct 2012 10:20:06 -0400
From: Russ White <russw@riw.us>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120907 Thunderbird/15.0.1
MIME-Version: 1.0
To: William Herrin <bill@herrin.us>
References: <CC5BE44F.2A792%pds@lugs.com> <CAP-guGXL6-AkPSnMJ7TY-dVafOMXKtFNQCUdKcrVGrbHoQNSXQ@mail.gmail.com> <CAL9jLaYGu3mOKEFGESEm8EmtH5bhijV1AhjYi44_4Kqv=2-2SQ@mail.gmail.com> <20120925201954.GG1854@pfrc> <506B5AA9.8000400@riw.us> <CAP-guGXpfT46+mP_Q-uvrWmFbt_pOfEYw3HqtLRg98WweKK3bA@mail.gmail.com>
In-Reply-To: <CAP-guGXpfT46+mP_Q-uvrWmFbt_pOfEYw3HqtLRg98WweKK3bA@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Antivirus-Scanner: Seems clean.  You should still use an Antivirus Scanner
Cc: grow@ietf.org
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: Wed, 03 Oct 2012 14:20:17 -0000

>> I don't get how path information is lost in this draft. The AS Path is
>> not altered in any advertisement, so it's not like aggregation, where
>> you replace a series of AS' with a single AS, or anything like that.
> 
> Hi Russ,
> 
> 10.1.0.0/16 AS path 12 5 4 2
> 10.1.1.0/24 AS path 12 1
> 
> The 12->1 path, 1 being a completely different origin AS than the
> covering route's origin from 2, is lost when 10.1.1.0/24 is aggregated
> into 10.1.0.0/16.

No more than if the longer prefix were filtered for any other reason
--such as if the provider is originating the shorter prefix, and decides
to filter the longer prefix for whatever local policy reason.  The only
way to see this as "losing AS Path information," is to see the filtering
of any possible route, including routes lost because they aren't the
best path, as "losing AS Path information."

>>>   - But even if they do share a common origin AS, if you have an internal AS
>>>     partition, things may be unhappy if the more specific provided you
>>>     forwarding coverage and it got suppressed.
>>
>> AS partitions are already handled in the draft as written. If the two
>> routers with overlapping prefixes aren't reachable through iBGP (no
>> matter what their AS numbers might happen to me), then the mechanism
>> won't suppress the longer prefix.
> 
> Suppose an Internet-connected network consists of site A and site B.
> 10.1.1.0/24 is advertised from and used by site A while 10.1.2.0/24 is
> advertised from and used by site site B. Both sites advertise
> 10.1.0.0/16. Sites A and B are connected to each other, so if site A
> receives a packet for 10.1.2.1, it will forward it to site B.
> 
> If site B should lose its internet connection, packets for 10.1.2.1
> will follow the covering route via site A and still reach site B.
> Regardless of aggregation.

This has always been true of any form of aggregation --this draft
doesn't introduce any new risk in this area. When you aggregate at any
level, ever, you always introduce the risk of suboptimal routes and/or
routing black holes. Does this mean all routes advertised into the DFZ
should be /24's, or host routes?

:-)

Russ


From russw@riw.us  Wed Oct  3 07:21:35 2012
Return-Path: <russw@riw.us>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BA25821F85A4 for <grow@ietfa.amsl.com>; Wed,  3 Oct 2012 07:21:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.367
X-Spam-Level: 
X-Spam-Status: No, score=-2.367 tagged_above=-999 required=5 tests=[AWL=0.232,  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 mu84Z7HWA8e6 for <grow@ietfa.amsl.com>; Wed,  3 Oct 2012 07:21:35 -0700 (PDT)
Received: from da31.namelessnet.net (da31.namelessnet.net [74.124.205.66]) by ietfa.amsl.com (Postfix) with ESMTP id 3E08721F8594 for <grow@ietf.org>; Wed,  3 Oct 2012 07:21:35 -0700 (PDT)
Received: from cpe-065-190-156-032.nc.res.rr.com ([65.190.156.32] helo=[192.168.100.51]) by da31.namelessnet.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.77) (envelope-from <russw@riw.us>) id 1TJPpO-0003Zr-Jj; Wed, 03 Oct 2012 07:21:34 -0700
Message-ID: <506C49EE.9060202@riw.us>
Date: Wed, 03 Oct 2012 10:21:34 -0400
From: Russ White <russw@riw.us>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120907 Thunderbird/15.0.1
MIME-Version: 1.0
To: Jared Mauch <jared@puck.nether.net>
References: <CC5BE44F.2A792%pds@lugs.com> <CAP-guGXL6-AkPSnMJ7TY-dVafOMXKtFNQCUdKcrVGrbHoQNSXQ@mail.gmail.com> <CAL9jLaYGu3mOKEFGESEm8EmtH5bhijV1AhjYi44_4Kqv=2-2SQ@mail.gmail.com> <20120925201954.GG1854@pfrc> <5062BAE8.6010801@inex.ie> <506B5B3B.1020507@riw.us> <8121770B-66E1-47A9-90B5-563D0E106939@puck.nether.net>
In-Reply-To: <8121770B-66E1-47A9-90B5-563D0E106939@puck.nether.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Antivirus-Scanner: Seems clean.  You should still use an Antivirus Scanner
Cc: grow@ietf.org
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: Wed, 03 Oct 2012 14:21:35 -0000

> The problem as I see it is many of those that operate in the BGP/DFZ don't know what they are doing.

???

Then they shouldn't be using this technique. Or perhaps even running
BGP. Protocols provide rope. It's choice whether you make good things or
bad things with the rope provided.

:-)

Russ

From ju1738@att.com  Wed Oct  3 07:26:30 2012
Return-Path: <ju1738@att.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4684D21F855B for <grow@ietfa.amsl.com>; Wed,  3 Oct 2012 07:26:30 -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=[AWL=0.001, 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 H8wmdcLMkVyY for <grow@ietfa.amsl.com>; Wed,  3 Oct 2012 07:26:29 -0700 (PDT)
Received: from nbfkord-smmo06.seg.att.com (nbfkord-smmo06.seg.att.com [209.65.160.94]) by ietfa.amsl.com (Postfix) with ESMTP id 4207D21F84D8 for <grow@ietf.org>; Wed,  3 Oct 2012 07:26:29 -0700 (PDT)
Received: from unknown [144.160.128.153] (EHLO flpi408.enaf.ffdc.sbc.com) by nbfkord-smmo06.seg.att.com(mxl_mta-6.11.0-12) over TLS secured channel with ESMTP id 41b4c605.0.1118004.00-379.3082247.nbfkord-smmo06.seg.att.com (envelope-from <ju1738@att.com>);  Wed, 03 Oct 2012 14:26:29 +0000 (UTC)
X-MXL-Hash: 506c4b15301425fe-3e837398dfaa72027c036e776c17ec4f41c249cc
Received: from enaf.ffdc.sbc.com (localhost.localdomain [127.0.0.1]) by flpi408.enaf.ffdc.sbc.com (8.14.5/8.14.5) with ESMTP id q93EQSAZ014192; Wed, 3 Oct 2012 07:26:28 -0700
Received: from fflint03.pst.cso.att.com (fflint03.pst.cso.att.com [150.234.39.63]) by flpi408.enaf.ffdc.sbc.com (8.14.5/8.14.5) with ESMTP id q93EQGRP013993 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 3 Oct 2012 07:26:22 -0700
Received: from MISOUT7MSGHUB9A.ITServices.sbc.com (misout7msghub9a.itservices.sbc.com [144.151.223.62]) by fflint03.pst.cso.att.com (RSA Interceptor); Wed, 3 Oct 2012 07:25:54 -0700
Received: from MISOUT7MSGUSR9I.ITServices.sbc.com ([144.151.223.56]) by MISOUT7MSGHUB9A.ITServices.sbc.com ([144.151.223.62]) with mapi id 14.02.0318.001; Wed, 3 Oct 2012 10:25:53 -0400
From: "UTTARO, JAMES" <ju1738@att.com>
To: "'Russ White'" <russw@riw.us>, Jared Mauch <jared@puck.nether.net>
Thread-Topic: [GROW] Call for GROW WG adoption of grow-overlapping-routes
Thread-Index: AQHNoXJoYb/wXBbLRkqXGbugxkqvxJenonLw
Date: Wed, 3 Oct 2012 14:25:53 +0000
Message-ID: <B17A6910EEDD1F45980687268941550FB99A0E@MISOUT7MSGUSR9I.ITServices.sbc.com>
References: <CC5BE44F.2A792%pds@lugs.com> <CAP-guGXL6-AkPSnMJ7TY-dVafOMXKtFNQCUdKcrVGrbHoQNSXQ@mail.gmail.com> <CAL9jLaYGu3mOKEFGESEm8EmtH5bhijV1AhjYi44_4Kqv=2-2SQ@mail.gmail.com> <20120925201954.GG1854@pfrc> <5062BAE8.6010801@inex.ie> <506B5B3B.1020507@riw.us> <8121770B-66E1-47A9-90B5-563D0E106939@puck.nether.net> <506C49EE.9060202@riw.us>
In-Reply-To: <506C49EE.9060202@riw.us>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.91.76.182]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-Spam: [F=0.2000000000; CM=0.500; S=0.200(2010122901)]
X-MAIL-FROM: <ju1738@att.com>
X-SOURCE-IP: [144.160.128.153]
X-AnalysisOut: [v=2.0 cv=TZchQ2sh c=1 sm=0 a=xwOvzTHDVLE4u4nGvK72ag==:17 a]
X-AnalysisOut: [=g8Qva45Ca7EA:10 a=ViMPHP9eR4sA:10 a=ofMgfj31e3cA:10 a=BLc]
X-AnalysisOut: [eEmwcHowA:10 a=kj9zAlcOel0A:10 a=zQP7CpKOAAAA:8 a=XIqpo32R]
X-AnalysisOut: [AAAA:8 a=ThYhczIr89kA:10 a=48vgC7mUAAAA:8 a=XyjiBvbOiW2qEx]
X-AnalysisOut: [zSGzcA:9 a=CjuIK1q_8ugA:10 a=lZB815dzVvQA:10]
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: Wed, 03 Oct 2012 14:26:30 -0000

Russ,

	Hmmm, I don't think this is a consistent message.. When I attempted to giv=
e people rope i.e BGP Persistence IETF chairs felt that this was too much r=
ope ?? IMO it takes very little rope to hang oneself so, let's be consisten=
t as a starting point...

Jim Uttaro

-----Original Message-----
From: grow-bounces@ietf.org [mailto:grow-bounces@ietf.org] On Behalf Of Rus=
s White
Sent: Wednesday, October 03, 2012 10:22 AM
To: Jared Mauch
Cc: grow@ietf.org
Subject: Re: [GROW] Call for GROW WG adoption of grow-overlapping-routes


> The problem as I see it is many of those that operate in the BGP/DFZ don'=
t know what they are doing.

???

Then they shouldn't be using this technique. Or perhaps even running
BGP. Protocols provide rope. It's choice whether you make good things or
bad things with the rope provided.

:-)

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

From russw@riw.us  Wed Oct  3 07:32:46 2012
Return-Path: <russw@riw.us>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BC0C921F859C for <grow@ietfa.amsl.com>; Wed,  3 Oct 2012 07:32:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.413
X-Spam-Level: 
X-Spam-Status: No, score=-2.413 tagged_above=-999 required=5 tests=[AWL=0.186,  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 HD50K0xiDByb for <grow@ietfa.amsl.com>; Wed,  3 Oct 2012 07:32:46 -0700 (PDT)
Received: from da31.namelessnet.net (da31.namelessnet.net [74.124.205.66]) by ietfa.amsl.com (Postfix) with ESMTP id 5681921F84F2 for <grow@ietf.org>; Wed,  3 Oct 2012 07:32:46 -0700 (PDT)
Received: from cpe-065-190-156-032.nc.res.rr.com ([65.190.156.32] helo=[192.168.100.51]) by da31.namelessnet.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.77) (envelope-from <russw@riw.us>) id 1TJQ0D-0003uk-BQ; Wed, 03 Oct 2012 07:32:45 -0700
Message-ID: <506C4C8D.6090304@riw.us>
Date: Wed, 03 Oct 2012 10:32:45 -0400
From: Russ White <russw@riw.us>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120907 Thunderbird/15.0.1
MIME-Version: 1.0
To: William Herrin <bill@herrin.us>
References: <CC5BE44F.2A792%pds@lugs.com> <CAP-guGXL6-AkPSnMJ7TY-dVafOMXKtFNQCUdKcrVGrbHoQNSXQ@mail.gmail.com> <CAL9jLaYGu3mOKEFGESEm8EmtH5bhijV1AhjYi44_4Kqv=2-2SQ@mail.gmail.com> <20120925201954.GG1854@pfrc> <506B5AA9.8000400@riw.us> <CAP-guGXpfT46+mP_Q-uvrWmFbt_pOfEYw3HqtLRg98WweKK3bA@mail.gmail.com> <506C4996.7010909@riw.us>
In-Reply-To: <506C4996.7010909@riw.us>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Antivirus-Scanner: Seems clean.  You should still use an Antivirus Scanner
Cc: grow@ietf.org
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: Wed, 03 Oct 2012 14:32:46 -0000

>> Suppose an Internet-connected network consists of site A and site B.
>> 10.1.1.0/24 is advertised from and used by site A while 10.1.2.0/24 is
>> advertised from and used by site site B. Both sites advertise
>> 10.1.0.0/16. Sites A and B are connected to each other, so if site A
>> receives a packet for 10.1.2.1, it will forward it to site B.
>>
>> If site B should lose its internet connection, packets for 10.1.2.1
>> will follow the covering route via site A and still reach site B.
>> Regardless of aggregation.
> 
> This has always been true of any form of aggregation --this draft
> doesn't introduce any new risk in this area. When you aggregate at any
> level, ever, you always introduce the risk of suboptimal routes and/or
> routing black holes. Does this mean all routes advertised into the DFZ
> should be /24's, or host routes?

BTW, I agree with Alvaro that the draft intends to leave open the option
of how to implement this within an individual provider's network, so the
provider could choose to check the entire AS Path before bounding a
particular route.

We had also removed (for simplicity) the "don't bound" community, but we
could easily add it back in if providers want the capability to have a
customer mark their routes to never be removed. Would that be useful?

:-)

Russ

From robert@raszuk.net  Wed Oct  3 07:34:07 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 754B721F8639 for <grow@ietfa.amsl.com>; Wed,  3 Oct 2012 07:34:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3pyFdaKYOgNR for <grow@ietfa.amsl.com>; Wed,  3 Oct 2012 07:34:07 -0700 (PDT)
Received: from mail1310.opentransfer.com (mail1310.opentransfer.com [76.162.254.103]) by ietfa.amsl.com (Postfix) with ESMTP id E6D6C21F84BF for <grow@ietf.org>; Wed,  3 Oct 2012 07:33:58 -0700 (PDT)
Received: (qmail 24185 invoked by uid 399); 3 Oct 2012 14:35:03 -0000
Received: from unknown (HELO ?192.168.1.91?) (pbs:robert@raszuk.net@83.31.237.219) by mail1310.opentransfer.com with ESMTPM; 3 Oct 2012 14:35:03 -0000
X-Originating-IP: 83.31.237.219
Message-ID: <506C4CD7.6060803@raszuk.net>
Date: Wed, 03 Oct 2012 16:33:59 +0200
From: Robert Raszuk <robert@raszuk.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120907 Thunderbird/15.0.1
MIME-Version: 1.0
To: "Alvaro Retana (aretana)" <aretana@cisco.com>
References: <BBD66FD99311804F80324E8139B3C94EA39EC4@xmb-aln-x15.cisco.com>
In-Reply-To: <BBD66FD99311804F80324E8139B3C94EA39EC4@xmb-aln-x15.cisco.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
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
Reply-To: robert@raszuk.net
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Oct 2012 14:34:07 -0000

Alvaro,

 >> >10.1.0.0/16 AS path 12 5 4 2
>> >10.1.1.0/24 AS path 12 1
>> >
>> >The 12->1 path, 1 being a completely different origin AS than the
>> >covering route's origin from 2, is lost when 10.1.1.0/24 is aggregated
>> >into 10.1.0.0/16.
 >
> The path is not aggregated.  Instead, the /24 would be marked as BOUNDED;
> the draft explains what that means:
>
> =====
> 3.3 Handling Marked Routes Within the AS
>
>     Routes marked with the BOUNDED community MAY not be installed in the
>     local RIB of routers within the AS.  This optional step will reduce
>     local RIB and forwarding table usage and volatility within the AS.

So if I learn /24 from different peer then /16 arrives on given ASBR or 
such /24 arrives via different ASBR (both cases would result /24 to have 
different next hop then /16) such /24 would not be marked as BOUNDED 
correct ?

If so I really fail why this filtering can not be done by inbound EBGP 
policy on such ASBR. Why do we need new draft and new communities ???

R.



From russw@riw.us  Wed Oct  3 08:52:44 2012
Return-Path: <russw@riw.us>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A1BF121F84F8 for <grow@ietfa.amsl.com>; Wed,  3 Oct 2012 08:52:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.444
X-Spam-Level: 
X-Spam-Status: No, score=-2.444 tagged_above=-999 required=5 tests=[AWL=0.155,  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 vSbw3r2J1luT for <grow@ietfa.amsl.com>; Wed,  3 Oct 2012 08:52:41 -0700 (PDT)
Received: from da31.namelessnet.net (da31.namelessnet.net [74.124.205.66]) by ietfa.amsl.com (Postfix) with ESMTP id A7CB121F84F6 for <grow@ietf.org>; Wed,  3 Oct 2012 08:52:40 -0700 (PDT)
Received: from cpe-065-190-156-032.nc.res.rr.com ([65.190.156.32] helo=[192.168.100.51]) by da31.namelessnet.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.77) (envelope-from <russw@riw.us>) id 1TJRFK-0006AT-Ul; Wed, 03 Oct 2012 08:52:27 -0700
Message-ID: <506C5F3B.9070906@riw.us>
Date: Wed, 03 Oct 2012 11:52:27 -0400
From: Russ White <russw@riw.us>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120907 Thunderbird/15.0.1
MIME-Version: 1.0
To: robert@raszuk.net
References: <BBD66FD99311804F80324E8139B3C94EA39EC4@xmb-aln-x15.cisco.com> <506C4CD7.6060803@raszuk.net>
In-Reply-To: <506C4CD7.6060803@raszuk.net>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
X-Antivirus-Scanner: Seems clean.  You should still use an Antivirus Scanner
Cc: "grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] 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: Wed, 03 Oct 2012 15:52:44 -0000

>> =====
>> 3.3 Handling Marked Routes Within the AS
>>
>>     Routes marked with the BOUNDED community MAY not be installed in the
>>     local RIB of routers within the AS.  This optional step will reduce
>>     local RIB and forwarding table usage and volatility within the AS.
> 
> So if I learn /24 from different peer then /16 arrives on given ASBR or
> such /24 arrives via different ASBR (both cases would result /24 to have
> different next hop then /16) such /24 would not be marked as BOUNDED
> correct ?
> 
> If so I really fail why this filtering can not be done by inbound EBGP
> policy on such ASBR. Why do we need new draft and new communities ???

MAY not, so it's a local option. This draft allows for two modes of
operation (at least), one where the two routes can arrive on two
different AS border routers, and one where they must arrive on the same
AS border router. The second case is just like filtering the longer
prefix at the inbound AS border router, the first keeps optimal exit
points out of the local AS, while removing information once it doesn't
matter to the flow of traffic.

:-)

Russ


From russw@riw.us  Wed Oct  3 09:10:48 2012
Return-Path: <russw@riw.us>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D4B2221F84C5 for <grow@ietfa.amsl.com>; Wed,  3 Oct 2012 09:10:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.466
X-Spam-Level: 
X-Spam-Status: No, score=-2.466 tagged_above=-999 required=5 tests=[AWL=0.133,  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 s-fTsuamJ7-A for <grow@ietfa.amsl.com>; Wed,  3 Oct 2012 09:10:48 -0700 (PDT)
Received: from da31.namelessnet.net (da31.namelessnet.net [74.124.205.66]) by ietfa.amsl.com (Postfix) with ESMTP id 15FFF21F846E for <grow@ietf.org>; Wed,  3 Oct 2012 09:10:46 -0700 (PDT)
Received: from cpe-065-190-156-032.nc.res.rr.com ([65.190.156.32] helo=[192.168.100.51]) by da31.namelessnet.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.77) (envelope-from <russw@riw.us>) id 1TJRWw-0006fN-AX; Wed, 03 Oct 2012 09:10:38 -0700
Message-ID: <506C637E.9060709@riw.us>
Date: Wed, 03 Oct 2012 12:10:38 -0400
From: Russ White <russw@riw.us>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120907 Thunderbird/15.0.1
MIME-Version: 1.0
To: Robert Raszuk <robert@raszuk.net>
References: <BBD66FD99311804F80324E8139B3C94EA39EC4@xmb-aln-x15.cisco.com> <506C4CD7.6060803@raszuk.net> <506C5F3B.9070906@riw.us> <CA+b+ERkfwQeZ4c1YTH3+QYfjGqtgMteVQkz=9C9cF9XrVL6o9w@mail.gmail.com>
In-Reply-To: <CA+b+ERkfwQeZ4c1YTH3+QYfjGqtgMteVQkz=9C9cF9XrVL6o9w@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Antivirus-Scanner: Seems clean.  You should still use an Antivirus Scanner
Cc: "grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] 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: Wed, 03 Oct 2012 16:10:48 -0000

> How do you know it does not matter if you are not comparing it best
> path with less specific ? How do you know that your competitor which
> your dual home customer is also connected to is not filtering and is
> injecting /24 attracting and charging for all the traffic ?

Because you could see this and mark your /24 not to be bounded (if we
put that back in). We were trying for the simplest solution to
increasing table sizes --I know there are economic reasons the table
sizes are growing, but we need at least some option to de-escalate the
madness at some point.

:-)

Russ

From nick@inex.ie  Wed Oct  3 09:28:45 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 5EAEC21F84F9 for <grow@ietfa.amsl.com>; Wed,  3 Oct 2012 09:28:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=-0.000, 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 STJbAUBbchFs for <grow@ietfa.amsl.com>; Wed,  3 Oct 2012 09:28:44 -0700 (PDT)
Received: from mail.acquirer.com (mail.acquirer.com [IPv6:2a03:8900:0:100::5]) by ietfa.amsl.com (Postfix) with ESMTP id 698C921F849C for <grow@ietf.org>; Wed,  3 Oct 2012 09:28:43 -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 q93GSI9O050971 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Wed, 3 Oct 2012 17:28:18 +0100 (IST) (envelope-from nick@inex.ie)
Message-ID: <506C67B9.4070301@inex.ie>
Date: Wed, 03 Oct 2012 17:28:41 +0100
From: Nick Hilliard <nick@inex.ie>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:15.0) Gecko/20120907 Thunderbird/15.0.1
MIME-Version: 1.0
To: Russ White <russw@riw.us>
References: <BBD66FD99311804F80324E8139B3C94EA39EC4@xmb-aln-x15.cisco.com> <506C4CD7.6060803@raszuk.net> <506C5F3B.9070906@riw.us> <CA+b+ERkfwQeZ4c1YTH3+QYfjGqtgMteVQkz=9C9cF9XrVL6o9w@mail.gmail.com> <506C637E.9060709@riw.us>
In-Reply-To: <506C637E.9060709@riw.us>
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" <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: Wed, 03 Oct 2012 16:28:45 -0000

On 03/10/2012 17:10, Russ White wrote:
> Because you could see this and mark your /24 not to be bounded (if we
> put that back in). We were trying for the simplest solution to
> increasing table sizes --I know there are economic reasons the table
> sizes are growing, but we need at least some option to de-escalate the
> madness at some point.

People have been saying for the last twentysomething years that the sky is
falling due to DMZ growth.  Geoff Huston gave a talk about this last year
in Vienna where he presented some data and analysis:

http://ripe63.ripe.net/archives/video/178
http://ripe63.ripe.net/presentations/61-2011-10-31-bgp2011.pdf

I'm not suggesting that the DFZ couldn't do with a bit of slimming, but the
bgp RIB is not the best place to do it because you're losing too much
information too early.

Nick


From wherrin@gmail.com  Wed Oct  3 10:41:26 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 75CF721F8647 for <grow@ietfa.amsl.com>; Wed,  3 Oct 2012 10:41:26 -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 uvmcukexEyUZ for <grow@ietfa.amsl.com>; Wed,  3 Oct 2012 10:41:25 -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 B4A8D21F8666 for <grow@ietf.org>; Wed,  3 Oct 2012 10:41:24 -0700 (PDT)
Received: by obqv19 with SMTP id v19so9098748obq.31 for <grow@ietf.org>; Wed, 03 Oct 2012 10:41:24 -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=HF2Bvvey/Y/OCVYgkyo7b2vcafZlhR6lFRGXBbua1uQ=; b=CGUhFQS0Lv1DyeDvVznyR9kAD+zsA32dQtxuHC309EBcgIyie2pwmNLgQ7l2ZX1UIG D8BDlfZqYEyXiwTY96h/whz/3pAM5KwX27k7TRVmZ81k6ZSjLvEJ6pcYi7WRQDiPQhai 81XJbBm+Uf+J2PLbx87VYBjtW7a+9K7+qHiQ1YLpaT7js9pOL0rrqqVL+eyeIKJP2YEt GPUR7KCMfDKmnQaIo63gkxzeLdfEpULm53XVOGQqtgStJVJ7CqI73arEYHJXXwthks3O V3ikFyfj3afcEN75NMJj7geTCpjywzsDKeQLJokam2QuA0pDWjN0jYbL5+fYa8mOecdP 8PzQ==
Received: by 10.182.45.42 with SMTP id j10mr2123796obm.60.1349286082994; Wed, 03 Oct 2012 10:41:22 -0700 (PDT)
MIME-Version: 1.0
Sender: wherrin@gmail.com
Received: by 10.182.81.164 with HTTP; Wed, 3 Oct 2012 10:41:02 -0700 (PDT)
In-Reply-To: <506C4996.7010909@riw.us>
References: <CC5BE44F.2A792%pds@lugs.com> <CAP-guGXL6-AkPSnMJ7TY-dVafOMXKtFNQCUdKcrVGrbHoQNSXQ@mail.gmail.com> <CAL9jLaYGu3mOKEFGESEm8EmtH5bhijV1AhjYi44_4Kqv=2-2SQ@mail.gmail.com> <20120925201954.GG1854@pfrc> <506B5AA9.8000400@riw.us> <CAP-guGXpfT46+mP_Q-uvrWmFbt_pOfEYw3HqtLRg98WweKK3bA@mail.gmail.com> <506C4996.7010909@riw.us>
From: William Herrin <bill@herrin.us>
Date: Wed, 3 Oct 2012 13:41:02 -0400
X-Google-Sender-Auth: VmiIDoBpo78b6iThMMrTX4J9wLw
Message-ID: <CAP-guGX6A8izxpRRLde_NNXy8fOA7JwTc4t3VhD_G=AiScp8eA@mail.gmail.com>
To: Russ White <russw@riw.us>
Content-Type: text/plain; charset=ISO-8859-1
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: Wed, 03 Oct 2012 17:41:26 -0000

On Wed, Oct 3, 2012 at 10:20 AM, Russ White <russw@riw.us> wrote:
>>> I don't get how path information is lost in this draft. The AS Path is
>>> not altered in any advertisement, so it's not like aggregation, where
>>> you replace a series of AS' with a single AS, or anything like that.
>>
>> 10.1.0.0/16 AS path 12 5 4 2
>> 10.1.1.0/24 AS path 12 1
>>
>> The 12->1 path, 1 being a completely different origin AS than the
>> covering route's origin from 2, is lost when 10.1.1.0/24 is aggregated
>> into 10.1.0.0/16.
>
> No more than if the longer prefix were filtered for any other reason
> --such as if the provider is originating the shorter prefix, and decides
> to filter the longer prefix for whatever local policy reason.  The only
> way to see this as "losing AS Path information," is to see the filtering
> of any possible route, including routes lost because they aren't the
> best path, as "losing AS Path information."

Hi Russ,

With the occasional exception of leaf ASes, the longer prefix *isn't*
filtered for any reason today. Precisely because it breaks the routing
system. Some folks tried some filtering for a while, filtering at /21
based on RIR minimum allocation sizes within particular /8's but it
didn't work out. Operationally, the current expectation is that any
prefix /24 or shorter will be propagated throughout the system.

The moment a major transit AS uses this technique, everybody doing
something like the above has to disaggregate into non-overlapping
routes in order to maintain operations. Those two advertisements
become at least nine. Unless you can identify a sufficient number of
origins who for one reason or another *wouldn't* choose to
disaggregate, the use of the technique in any transit AS would result
in an *increase* rather than decrease the routing table load.

If you restrict your solution set to non-transit ASes there are some
promising techniques based on aggregating for AS distance rather than
overlap. As a leaf, once a route is distant enough from you, if you
see it from all "upstream" neighbors you can usually aggregate it into
a /8 covering route with typically negligible harm to your routing
efficiency. But that only works if you are a leaf AS. If there's
someone who would otherwise receive the more specific route from you
then you've just broken the routing system. And of course offering the
aggregate route to a neighboring AS is a recipe for nastiness since
you can't really analyze its impact anywhere other than inside your
own AS.

However, since you're already at the leaf AS for this approach, it's
not clear such a technique wouldn't be better applied to the FIB
produced from the RIB rather than to the RIB directly. You have to
process the prefixes inbound anyway and holding them in a radix tree
that isn't accessed on a per-packet basis isn't computationally
expensive.


> This has always been true of any form of aggregation --this draft
> doesn't introduce any new risk in this area. When you aggregate at any
> level, ever, you always introduce the risk of suboptimal routes and/or
> routing black holes. Does this mean all routes advertised into the DFZ
> should be /24's, or host routes?

No. It means that the source AS is the only place technically capable
of making verifiably correct aggregation decisions impacting transit
ASes. Stated more generally, an AS is only capable of making
aggregation decisions which impact only that AS. The moment your
aggregation choice spreads to a neighbor AS you've broken the system.

As I mentioned in previous emails, this has been explored ad nauseam
over in RRG. It would be very productive to dig through those archives
and use the knowledge there to produce an RFC that documents the
myriad issues that a solution in this space would have to resolve.
Perhaps as a first step to further analyzing your approach.

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 russw@riw.us  Wed Oct  3 10:44:10 2012
Return-Path: <russw@riw.us>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 223A121F8647 for <grow@ietfa.amsl.com>; Wed,  3 Oct 2012 10:44:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.483
X-Spam-Level: 
X-Spam-Status: No, score=-2.483 tagged_above=-999 required=5 tests=[AWL=0.116,  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 acoIKH90CodX for <grow@ietfa.amsl.com>; Wed,  3 Oct 2012 10:44:08 -0700 (PDT)
Received: from da31.namelessnet.net (da31.namelessnet.net [74.124.205.66]) by ietfa.amsl.com (Postfix) with ESMTP id BE61E21F85A0 for <grow@ietf.org>; Wed,  3 Oct 2012 10:44:08 -0700 (PDT)
Received: from cpe-065-190-156-032.nc.res.rr.com ([65.190.156.32] helo=[192.168.100.51]) by da31.namelessnet.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.77) (envelope-from <russw@riw.us>) id 1TJSzP-0001FD-5k; Wed, 03 Oct 2012 10:44:07 -0700
Message-ID: <506C7967.90302@riw.us>
Date: Wed, 03 Oct 2012 13:44:07 -0400
From: Russ White <russw@riw.us>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120907 Thunderbird/15.0.1
MIME-Version: 1.0
To: Nick Hilliard <nick@inex.ie>
References: <BBD66FD99311804F80324E8139B3C94EA39EC4@xmb-aln-x15.cisco.com> <506C4CD7.6060803@raszuk.net> <506C5F3B.9070906@riw.us> <CA+b+ERkfwQeZ4c1YTH3+QYfjGqtgMteVQkz=9C9cF9XrVL6o9w@mail.gmail.com> <506C637E.9060709@riw.us> <506C67B9.4070301@inex.ie>
In-Reply-To: <506C67B9.4070301@inex.ie>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Antivirus-Scanner: Seems clean.  You should still use an Antivirus Scanner
Cc: "grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] 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: Wed, 03 Oct 2012 17:44:10 -0000

>> Because you could see this and mark your /24 not to be bounded (if we
>> put that back in). We were trying for the simplest solution to
>> increasing table sizes --I know there are economic reasons the table
>> sizes are growing, but we need at least some option to de-escalate the
>> madness at some point.
> 
> People have been saying for the last twentysomething years that the sky is
> falling due to DMZ growth.  Geoff Huston gave a talk about this last year
> in Vienna where he presented some data and analysis:
> 
> http://ripe63.ripe.net/archives/video/178
> http://ripe63.ripe.net/presentations/61-2011-10-31-bgp2011.pdf

I would suggest:

1. IPv6, over time, is going to present a different issue...
2. That the problem is an economic problem, not a technical one, and
hence we need a solution that pushes the tradeoffs between the cost of
advertising and the cost of not advertising into the front of our minds,
rather than making the advertisement of a new longer prefix route "free."

> I'm not suggesting that the DFZ couldn't do with a bit of slimming, but the
> bgp RIB is not the best place to do it because you're losing too much
> information too early.

This isn't at the BGP RIB, this is removing routes from the system when
they are no longer useful for modifying forwarding direction. It's no
different than removing routes that have lost in the best path decision
process, in terms of "lost information." We could, of course, back up
and argue that we shouldn't be removing routes that lose in the bestpath
process, because we're "losing AS Path information," if we want to argue
for complete information everywhere.

:-)

Russ


From wherrin@gmail.com  Wed Oct  3 10:45:53 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 1317D21F86C9 for <grow@ietfa.amsl.com>; Wed,  3 Oct 2012 10:45:53 -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 t1yfn5HcCVUM for <grow@ietfa.amsl.com>; Wed,  3 Oct 2012 10:45:52 -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 2A35621F8578 for <grow@ietf.org>; Wed,  3 Oct 2012 10:45:52 -0700 (PDT)
Received: by obqv19 with SMTP id v19so9104307obq.31 for <grow@ietf.org>; Wed, 03 Oct 2012 10:45:51 -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 :content-transfer-encoding; bh=UjpDsRBm9BN5ojBFgNAH816fYJjdm+rz6ZUbZqaM4Hk=; b=ZHgLTfR/CzvXCmkb+YDx0nQELA3WxaX2J6b+MKlWCod2iyYhWmOOeLsV4YSFbpFfPg 2rFPFTqQ71+jtCfk5CY9r0BbPOlEe2+6TQi6mMqAFbU1HrpkmBYN+J/8MNO63E4ukPLP 6T8jMYg7Lr9/OLzYtZsOZGqq6b7QgXIfoKUKca7fUQ+0XrRL1mcmn7dNA31XOGnauV06 8cXhlbN22r9knibmNBGyLd/vp5FyN8sM/67CLEomXY6zcdfkkcuy/G6QIwPNBnd72nmx 1mST+hPYGCmOo1I7dSE57uc8tJZZXZKRNm99MUWNzNCuUcLgf0o217X4ohYjWpewk35F zg1Q==
Received: by 10.182.40.6 with SMTP id t6mr2132590obk.100.1349286351704; Wed, 03 Oct 2012 10:45:51 -0700 (PDT)
MIME-Version: 1.0
Sender: wherrin@gmail.com
Received: by 10.182.81.164 with HTTP; Wed, 3 Oct 2012 10:45:31 -0700 (PDT)
In-Reply-To: <BBD66FD99311804F80324E8139B3C94EA39EF7@xmb-aln-x15.cisco.com>
References: <8121770B-66E1-47A9-90B5-563D0E106939@puck.nether.net> <BBD66FD99311804F80324E8139B3C94EA39EF7@xmb-aln-x15.cisco.com>
From: William Herrin <bill@herrin.us>
Date: Wed, 3 Oct 2012 13:45:31 -0400
X-Google-Sender-Auth: jblxlFNljrDdrzVwmHbwIXINo_E
Message-ID: <CAP-guGVCgsCLe3xyD3QYj6U+mRNVcP1hXoSHJLhKYPr7jmQ53A@mail.gmail.com>
To: "Alvaro Retana (aretana)" <aretana@cisco.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
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: Wed, 03 Oct 2012 17:45:53 -0000

On Wed, Oct 3, 2012 at 9:29 AM, Alvaro Retana (aretana)
<aretana@cisco.com> wrote:
> I agree.  Which is why our proposal is optional; if you want to do it, yo=
u
> can enable it=C5=A0as you can manually filter blocks of routes today or m=
ake
> all the exceptions you want (or are paid for).

Hi Alvaro,

That's not really an accurate characterization of the described
approach. When a particular AS chooses to aggregate a route, the
discarded route does not pass to neighbor to whom he'd otherwise pass
it on a general routing policy basis. Folks paying the AS for a full
view of the Internet do not receive a full view of the Internet.

Regards,
Bill Herrin


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

From russw@riw.us  Wed Oct  3 11:03:30 2012
Return-Path: <russw@riw.us>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AFCF421F845B for <grow@ietfa.amsl.com>; Wed,  3 Oct 2012 11:03:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.496
X-Spam-Level: 
X-Spam-Status: No, score=-2.496 tagged_above=-999 required=5 tests=[AWL=0.103,  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 vjztIyUFfmYV for <grow@ietfa.amsl.com>; Wed,  3 Oct 2012 11:03:29 -0700 (PDT)
Received: from da31.namelessnet.net (da31.namelessnet.net [74.124.205.66]) by ietfa.amsl.com (Postfix) with ESMTP id D0DF421F8203 for <grow@ietf.org>; Wed,  3 Oct 2012 11:03:29 -0700 (PDT)
Received: from cpe-065-190-156-032.nc.res.rr.com ([65.190.156.32] helo=[192.168.100.51]) by da31.namelessnet.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.77) (envelope-from <russw@riw.us>) id 1TJTHz-0001rr-5y; Wed, 03 Oct 2012 11:03:19 -0700
Message-ID: <506C7DE7.1010609@riw.us>
Date: Wed, 03 Oct 2012 14:03:19 -0400
From: Russ White <russw@riw.us>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120907 Thunderbird/15.0.1
MIME-Version: 1.0
To: William Herrin <bill@herrin.us>
References: <CC5BE44F.2A792%pds@lugs.com> <CAP-guGXL6-AkPSnMJ7TY-dVafOMXKtFNQCUdKcrVGrbHoQNSXQ@mail.gmail.com> <CAL9jLaYGu3mOKEFGESEm8EmtH5bhijV1AhjYi44_4Kqv=2-2SQ@mail.gmail.com> <20120925201954.GG1854@pfrc> <506B5AA9.8000400@riw.us> <CAP-guGXpfT46+mP_Q-uvrWmFbt_pOfEYw3HqtLRg98WweKK3bA@mail.gmail.com> <506C4996.7010909@riw.us> <CAP-guGX6A8izxpRRLde_NNXy8fOA7JwTc4t3VhD_G=AiScp8eA@mail.gmail.com>
In-Reply-To: <CAP-guGX6A8izxpRRLde_NNXy8fOA7JwTc4t3VhD_G=AiScp8eA@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Antivirus-Scanner: Seems clean.  You should still use an Antivirus Scanner
Cc: grow@ietf.org
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: Wed, 03 Oct 2012 18:03:30 -0000

>> No more than if the longer prefix were filtered for any other reason
>> --such as if the provider is originating the shorter prefix, and decides
>> to filter the longer prefix for whatever local policy reason.  The only
>> way to see this as "losing AS Path information," is to see the filtering
>> of any possible route, including routes lost because they aren't the
>> best path, as "losing AS Path information."
> 
> Hi Russ,
> 
> With the occasional exception of leaf ASes, the longer prefix *isn't*
> filtered for any reason today. Precisely because it breaks the routing
> system. Some folks tried some filtering for a while, filtering at /21
> based on RIR minimum allocation sizes within particular /8's but it
> didn't work out. Operationally, the current expectation is that any
> prefix /24 or shorter will be propagated throughout the system.

There's a vast difference between filtering out everything longer than a
/21 and suppressing a /24 when an overlapping route that takes the
traffic through the same path available. Completely different concepts.

In the case of suppressing longer prefixes, the result is something like
fisheye routing, or simple aggregation today. If an edge device only has
a default route, you don't expect the traffic to travel to the far end
of the network before it starts following a more sane path to the
destination. Instead, the traffic might follow a less than optimal route
until it reaches a point in the network where more specific routing
information is available.

This proposal does the same thing --I notice that I will be advertising
two overlapping routes that will draw traffic along the same path (to
me) to a peer. There's no reason to advertise both possible paths, it's
simply overlapping information that's not needed to draw traffic in the
right direction. So I don't advertise it.

>> This has always been true of any form of aggregation --this draft
>> doesn't introduce any new risk in this area. When you aggregate at any
>> level, ever, you always introduce the risk of suboptimal routes and/or
>> routing black holes. Does this mean all routes advertised into the DFZ
>> should be /24's, or host routes?
> 
> No. 

Yes.

Sorry, but it is always true that by removing information you always
lose optimality (you increase stretch). Whether that removal is done at
the edge or in the core, the result is always the same. There are two
ironclad rules of routing:

- Removing information decreases optimal routing.
- Removing information is necessary for the stability of the system.

You can play with different ways and places to remove information, but
you're always going to need to remove information. You can try to remove
information in the way that least impacts optimal routing, but you're
always going to introduce suboptimality in some way.

This proposal is about the minimal you can get to in terms of removing
information (no worse than best path does today), to keep modifications
to the path traffic actually flows to a minimum. I've looked at stuff
that does less than this, none of which has turned out to have any
meaningful impact, and stuff that does more than this, which has turned
out to be either complex for the gain, or increases stretch in
significant ways in normal operation (and not just broken corner cases).

> It means that the source AS is the only place technically capable
> of making verifiably correct aggregation decisions impacting transit
> ASes. 

Actually, the origin AS is the one place where you can't know how far
your route should propagate in order to effectively engineer traffic.
The only place you can know that the longer prefix is no longer useful
is at the point where two overlapping prefixes exist that will point
traffic in the same direction.

> As I mentioned in previous emails, this has been explored ad nauseam
> over in RRG. It would be very productive to dig through those archives
> and use the knowledge there to produce an RFC that documents the
> myriad issues that a solution in this space would have to resolve.
> Perhaps as a first step to further analyzing your approach.

I can feel your hands waving all the way over here... :-)

How about thinking up a specific situation where a problem exists that
will not or can not exist through normal aggregation, or through normal
route processing today, and posting it to the list? We can then sort out
whether its something that's actually broken (outside brokenness that
already exists in the routing system), if can be fixed, or if it's
impossible to fix.

:-)

Russ

From rraszuk@gmail.com  Wed Oct  3 11:27:18 2012
Return-Path: <rraszuk@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 84BED21F8551 for <grow@ietfa.amsl.com>; Wed,  3 Oct 2012 11:27:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.96
X-Spam-Level: 
X-Spam-Status: No, score=-2.96 tagged_above=-999 required=5 tests=[AWL=0.017,  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 lCLi09FG140G for <grow@ietfa.amsl.com>; Wed,  3 Oct 2012 11:27:18 -0700 (PDT)
Received: from mail-ie0-f172.google.com (mail-ie0-f172.google.com [209.85.223.172]) by ietfa.amsl.com (Postfix) with ESMTP id 1002E21F852E for <grow@ietf.org>; Wed,  3 Oct 2012 11:27:18 -0700 (PDT)
Received: by iec9 with SMTP id 9so20664193iec.31 for <grow@ietf.org>; Wed, 03 Oct 2012 11:27:17 -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:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=m/4PIKdfNJh63YovVFmxuAS9+YgeNAQ6jy794EXIPlc=; b=pN6dAL+d7jaWSkfD38HZypUwoMXptTRV1Jdfhz87ID1emS11vf4cP196lG88Dkeve4 XhZgNP1RjqTeAaByoQspYgEg7fHtjqXhuwcAvEs0xs/r53mQauLwBaLgmV7gdIXJn+fS cd0LcqbyRvMGss1qxyKB7NexylwoZvCcG7ky91sZ8+TwXX3089Ej5GUUOLSmqT3WAZCf 03GWsBkvUHZNInPwwkk0GC+2aKGjVfGd5lf6C0NH17wZw1U+PXv+qAom+PYkNE08OjAa yL3pzL6ToDyGp1yHW1sQabDOGRFC63O5HKyYJTIPleYZdgFUWoooYYWy9SNZhP9BdOAv rVGQ==
MIME-Version: 1.0
Received: by 10.42.109.194 with SMTP id m2mr2277518icp.48.1349288837606; Wed, 03 Oct 2012 11:27:17 -0700 (PDT)
Sender: rraszuk@gmail.com
Received: by 10.42.68.133 with HTTP; Wed, 3 Oct 2012 11:27:17 -0700 (PDT)
In-Reply-To: <506C7DE7.1010609@riw.us>
References: <CC5BE44F.2A792%pds@lugs.com> <CAP-guGXL6-AkPSnMJ7TY-dVafOMXKtFNQCUdKcrVGrbHoQNSXQ@mail.gmail.com> <CAL9jLaYGu3mOKEFGESEm8EmtH5bhijV1AhjYi44_4Kqv=2-2SQ@mail.gmail.com> <20120925201954.GG1854@pfrc> <506B5AA9.8000400@riw.us> <CAP-guGXpfT46+mP_Q-uvrWmFbt_pOfEYw3HqtLRg98WweKK3bA@mail.gmail.com> <506C4996.7010909@riw.us> <CAP-guGX6A8izxpRRLde_NNXy8fOA7JwTc4t3VhD_G=AiScp8eA@mail.gmail.com> <506C7DE7.1010609@riw.us>
Date: Wed, 3 Oct 2012 20:27:17 +0200
X-Google-Sender-Auth: f6e982EOuYkOFz6pAfyRLoitmfQ
Message-ID: <CA+b+ERkEQiUGuWyQJdtKZvF_8NH1ouqWYcH66_bQNiOnZWdEsQ@mail.gmail.com>
From: Robert Raszuk <robert@raszuk.net>
To: Russ White <russw@riw.us>
Content-Type: text/plain; charset=ISO-8859-1
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: Wed, 03 Oct 2012 18:27:18 -0000

Russ,

> Yes.
>
> Sorry, but it is always true that by removing information you always
> lose optimality (you increase stretch). Whether that removal is done at
> the edge or in the core, the result is always the same. There are two
> ironclad rules of routing:
>
> - Removing information decreases optimal routing.

No.

If you remove information which is redundant and when such removal
will not result in even a single bit of sub-optimal routing what you
wrote above is false "ironclad rule".

Also the critical piece is that the determination when and what should
be removed must be 100% automated. There is no way where manual
intervention would be required for any scheme to work right. And your
proposal does require manual NOC intervention as you have already
confirmed today.

The proposal from Pedro however is automated, adjust itself to
topology changes as well as removed only redundant information where
such removal does not impact a single bit routing optimality.

Rgs,
R.

From wherrin@gmail.com  Wed Oct  3 14:01:08 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 7C18C11E80A5 for <grow@ietfa.amsl.com>; Wed,  3 Oct 2012 14:01:08 -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=[AWL=-0.000, 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 Am8Ui7HU0s5U for <grow@ietfa.amsl.com>; Wed,  3 Oct 2012 14:01:07 -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 8526911E8091 for <grow@ietf.org>; Wed,  3 Oct 2012 14:01:07 -0700 (PDT)
Received: by obqv19 with SMTP id v19so9344222obq.31 for <grow@ietf.org>; Wed, 03 Oct 2012 14:01:07 -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=OZk6FyFKbRvsdjofH3VOLMwViq52wnjRyjoAD/PXRXs=; b=pSy27CpRtKbbVbS3OLkiMDVrmE7xXH0F2wAmb2jlW5PvyHfq3d4dsa6VrRkjJ5baUz W3sXZw8nNovZ2W577PrD2RpsSMJQL1ePJzz50K2enktAW16KKa6eagnq+SuD8CcX/lXW SZUIiKoLlr7pFe/ltxnhnAu0qJXeahPrJCZUfSRdAdxdL873cddeHFbWZZ4FLJ0KG2Zb c1WXiVHh9vQgXkzUClM8wX1r5vmHv7ZW4Kmw/OOK0grkVIOUeLkglAfx0IB2usLPOU7z Nbj+5EWHYQxMd1URm3Y8o2SppczdgSHlQ7njLXSXxdcM+YHCmiknNmSPETCsUTNh39qN lzpQ==
Received: by 10.182.40.6 with SMTP id t6mr2565911obk.100.1349298067040; Wed, 03 Oct 2012 14:01:07 -0700 (PDT)
MIME-Version: 1.0
Sender: wherrin@gmail.com
Received: by 10.182.81.164 with HTTP; Wed, 3 Oct 2012 14:00:46 -0700 (PDT)
In-Reply-To: <506C7DE7.1010609@riw.us>
References: <CC5BE44F.2A792%pds@lugs.com> <CAP-guGXL6-AkPSnMJ7TY-dVafOMXKtFNQCUdKcrVGrbHoQNSXQ@mail.gmail.com> <CAL9jLaYGu3mOKEFGESEm8EmtH5bhijV1AhjYi44_4Kqv=2-2SQ@mail.gmail.com> <20120925201954.GG1854@pfrc> <506B5AA9.8000400@riw.us> <CAP-guGXpfT46+mP_Q-uvrWmFbt_pOfEYw3HqtLRg98WweKK3bA@mail.gmail.com> <506C4996.7010909@riw.us> <CAP-guGX6A8izxpRRLde_NNXy8fOA7JwTc4t3VhD_G=AiScp8eA@mail.gmail.com> <506C7DE7.1010609@riw.us>
From: William Herrin <bill@herrin.us>
Date: Wed, 3 Oct 2012 17:00:46 -0400
X-Google-Sender-Auth: CAHE8PROv8xNNnhmGp5dHajQQqY
Message-ID: <CAP-guGUiGJ3jH1P4imrOyDaBp1+uqhOSTrYeyQJkPtiO_gRCuA@mail.gmail.com>
To: Russ White <russw@riw.us>
Content-Type: text/plain; charset=ISO-8859-1
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: Wed, 03 Oct 2012 21:01:08 -0000

On Wed, Oct 3, 2012 at 2:03 PM, Russ White <russw@riw.us> wrote:
>
>>> No more than if the longer prefix were filtered for any other reason
>>> --such as if the provider is originating the shorter prefix, and decides
>>> to filter the longer prefix for whatever local policy reason.  The only
>>> way to see this as "losing AS Path information," is to see the filtering
>>> of any possible route, including routes lost because they aren't the
>>> best path, as "losing AS Path information."
>>
>> With the occasional exception of leaf ASes, the longer prefix *isn't*
>> filtered for any reason today. Precisely because it breaks the routing
>> system. Some folks tried some filtering for a while, filtering at /21
>> based on RIR minimum allocation sizes within particular /8's but it
>> didn't work out. Operationally, the current expectation is that any
>> prefix /24 or shorter will be propagated throughout the system.
>
> There's a vast difference between filtering out everything longer than a
> /21 and suppressing a /24 when an overlapping route that takes the
> traffic through the same path available. Completely different concepts.

Hi Russ,

How do you know that the overlapping route takes traffic through the
same path? AS path != routing path and BGP is a distance-vector
protocol. Your router has no reliable knowledge of the routing path
more than 1 hop away.

Even if you could know the routing path was the same, consider:

ISP 88
10.1.0.0/16 via 2 3
10.1.1.0/24 via 2 3 (suppressed)

ISP 99
10.1.0.0/16 via 4 12 62 16 2 3
10.1.1.0/24 via 4 8 9 5 3 (not suppressed)

ISP 111 (customer of 88 & 99):
10.1.0.0/16 via 88 2 3
10.1.1.0/24 via 99 4 8 9 5 3

Best route was lost. But 111 can't safely suppress the /24 route
because he has no knowledge of whether the /24 is reachable via 88 1 2
3. To the best of 111's knowledge, AS3 might look like this right now:

2 - 3A
5 - 3B
No connection between 3A and 3B.

That's right, 111 doesn't know that AS3 is a contiguous network right
now. 111 doesn't even know that it's *intended* to be a contiguous
network ever. The most he knows about AS3 is that it's the same
organization from an administrative standpoint.

So, 111 is stuck using the badly suboptimal route because 88
suppressed a route that 111 needed to choose a reasonable next hop.

This is if you require exact path matching to suppress a route, which
your draft does not. Trivial scenarios following your draft lose
connectivity entirely.

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 jared@puck.nether.net  Wed Oct  3 14:21:34 2012
Return-Path: <jared@puck.nether.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 E5E0A21F8585 for <grow@ietfa.amsl.com>; Wed,  3 Oct 2012 14:21:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.199
X-Spam-Level: 
X-Spam-Status: No, score=-2.199 tagged_above=-999 required=5 tests=[AWL=0.400,  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 9x1mahWFh4Vd for <grow@ietfa.amsl.com>; Wed,  3 Oct 2012 14:21:34 -0700 (PDT)
Received: from puck.nether.net (puck.nether.net [IPv6:2001:418:3f4::5]) by ietfa.amsl.com (Postfix) with ESMTP id 813EC21F8574 for <grow@ietf.org>; Wed,  3 Oct 2012 14:21:27 -0700 (PDT)
Received: from [10.0.1.2] (support01.sterling.verio.net [207.153.206.12]) (authenticated bits=0) by puck.nether.net (8.14.4/8.14.4) with ESMTP id q93LLNHP003992 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 3 Oct 2012 17:21:24 -0400
Mime-Version: 1.0 (Mac OS X Mail 6.1 \(1498\))
Content-Type: text/plain; charset=iso-8859-1
From: Jared Mauch <jared@puck.nether.net>
In-Reply-To: <506C49EE.9060202@riw.us>
Date: Wed, 3 Oct 2012 17:21:23 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <FF0E84E6-19DD-4951-A9AD-3998B704129A@puck.nether.net>
References: <CC5BE44F.2A792%pds@lugs.com> <CAP-guGXL6-AkPSnMJ7TY-dVafOMXKtFNQCUdKcrVGrbHoQNSXQ@mail.gmail.com> <CAL9jLaYGu3mOKEFGESEm8EmtH5bhijV1AhjYi44_4Kqv=2-2SQ@mail.gmail.com> <20120925201954.GG1854@pfrc> <5062BAE8.6010801@inex.ie> <506B5B3B.1020507@riw.us> <8121770B-66E1-47A9-90B5-563D0E106939@puck.nether.net> <506C49EE.9060202@riw.us>
To: Russ White <russw@riw.us>
X-Mailer: Apple Mail (2.1498)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (puck.nether.net [204.42.254.5]); Wed, 03 Oct 2012 17:21:25 -0400 (EDT)
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: Wed, 03 Oct 2012 21:21:35 -0000

On Oct 3, 2012, at 10:21 AM, Russ White <russw@riw.us> wrote:

>>=20
>> The problem as I see it is many of those that operate in the BGP/DFZ =
don't know what they are doing.
>=20
> ???
>=20
> Then they shouldn't be using this technique. Or perhaps even running
> BGP. Protocols provide rope. It's choice whether you make good things =
or
> bad things with the rope provided.
>=20
> :-)

Sure.

But expecting them to do anything 'smart' has been a huge undertaking.  =
Some providers (e.g.: Bellsouth/ATT) have been trying for 2+ years to =
fix their unnecessary aggregate leaks with no success.=20

I'm not sure how to convince smaller folks to do the right thing if the =
big people can't sort it out. (even with the right hooks).

- Jared=

From russw@riw.us  Wed Oct  3 18:27:37 2012
Return-Path: <russw@riw.us>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7979211E8099 for <grow@ietfa.amsl.com>; Wed,  3 Oct 2012 18:27:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.506
X-Spam-Level: 
X-Spam-Status: No, score=-2.506 tagged_above=-999 required=5 tests=[AWL=0.093,  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 w8NQ9tjCdBiX for <grow@ietfa.amsl.com>; Wed,  3 Oct 2012 18:27:37 -0700 (PDT)
Received: from da31.namelessnet.net (da31.namelessnet.net [74.124.205.66]) by ietfa.amsl.com (Postfix) with ESMTP id 13B6811E8091 for <grow@ietf.org>; Wed,  3 Oct 2012 18:27:37 -0700 (PDT)
Received: from cpe-065-190-156-032.nc.res.rr.com ([65.190.156.32] helo=[192.168.100.51]) by da31.namelessnet.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.77) (envelope-from <russw@riw.us>) id 1TJaDp-0003QA-0Q; Wed, 03 Oct 2012 18:27:29 -0700
Message-ID: <506CE5FE.7020705@riw.us>
Date: Wed, 03 Oct 2012 21:27:26 -0400
From: Russ White <russw@riw.us>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120907 Thunderbird/15.0.1
MIME-Version: 1.0
To: Robert Raszuk <robert@raszuk.net>
References: <CC5BE44F.2A792%pds@lugs.com> <CAP-guGXL6-AkPSnMJ7TY-dVafOMXKtFNQCUdKcrVGrbHoQNSXQ@mail.gmail.com> <CAL9jLaYGu3mOKEFGESEm8EmtH5bhijV1AhjYi44_4Kqv=2-2SQ@mail.gmail.com> <20120925201954.GG1854@pfrc> <506B5AA9.8000400@riw.us> <CAP-guGXpfT46+mP_Q-uvrWmFbt_pOfEYw3HqtLRg98WweKK3bA@mail.gmail.com> <506C4996.7010909@riw.us> <CAP-guGX6A8izxpRRLde_NNXy8fOA7JwTc4t3VhD_G=AiScp8eA@mail.gmail.com> <506C7DE7.1010609@riw.us> <CA+b+ERkEQiUGuWyQJdtKZvF_8NH1ouqWYcH66_bQNiOnZWdEsQ@mail.gmail.com>
In-Reply-To: <CA+b+ERkEQiUGuWyQJdtKZvF_8NH1ouqWYcH66_bQNiOnZWdEsQ@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Antivirus-Scanner: Seems clean.  You should still use an Antivirus Scanner
Cc: grow@ietf.org
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, 04 Oct 2012 01:27:37 -0000

>> Sorry, but it is always true that by removing information you always
>> lose optimality (you increase stretch). Whether that removal is done at
>> the edge or in the core, the result is always the same. There are two
>> ironclad rules of routing:
>>
>> - Removing information decreases optimal routing.
> 
> No.

Yes. :-)

In fact, one of the points people are arguing here is, "in these
circumstances, the stretch increases."

1. Under normal operation, this proposal doesn't increase stretch (that
I know of).
2. Under broken conditions, any proposal may (probably will, in fact)
increase stretch.
3. In fact, normal aggregation increases stretch, so...

> Also the critical piece is that the determination when and what should
> be removed must be 100% automated. There is no way where manual
> intervention would be required for any scheme to work right. And your
> proposal does require manual NOC intervention as you have already
> confirmed today.

Robert --methinks you're putting words in my mouth. Beyond the basic
configuration, there's no "manual intervention." If you consider
configuring the option to be "manual intervention," then we have a fully
manual routing system already in place. :-)

> The proposal from Pedro however is automated, adjust itself to
> topology changes as well as removed only redundant information where
> such removal does not impact a single bit routing optimality.

This is a very simplified version of the proposal Pedro made --in fact,
this proposal actually predates Pedro's. I like Pedro's proposal, but I
consider the two different solutions parallel, rather than opposed.
There's no reason one AS couldn't implement one, and another the other
--it really isn't going to matter in the long run.

:-)

Russ

From russw@riw.us  Wed Oct  3 18:36:58 2012
Return-Path: <russw@riw.us>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 75DA111E809B for <grow@ietfa.amsl.com>; Wed,  3 Oct 2012 18:36:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.514
X-Spam-Level: 
X-Spam-Status: No, score=-2.514 tagged_above=-999 required=5 tests=[AWL=0.085,  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 yJoimQ2GIbDH for <grow@ietfa.amsl.com>; Wed,  3 Oct 2012 18:36:57 -0700 (PDT)
Received: from da31.namelessnet.net (da31.namelessnet.net [74.124.205.66]) by ietfa.amsl.com (Postfix) with ESMTP id B283C11E8091 for <grow@ietf.org>; Wed,  3 Oct 2012 18:36:57 -0700 (PDT)
Received: from cpe-065-190-156-032.nc.res.rr.com ([65.190.156.32] helo=[192.168.100.51]) by da31.namelessnet.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.77) (envelope-from <russw@riw.us>) id 1TJaMy-0003bS-Vx; Wed, 03 Oct 2012 18:36:57 -0700
Message-ID: <506CE83A.90401@riw.us>
Date: Wed, 03 Oct 2012 21:36:58 -0400
From: Russ White <russw@riw.us>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120907 Thunderbird/15.0.1
MIME-Version: 1.0
To: William Herrin <bill@herrin.us>
References: <CC5BE44F.2A792%pds@lugs.com> <CAP-guGXL6-AkPSnMJ7TY-dVafOMXKtFNQCUdKcrVGrbHoQNSXQ@mail.gmail.com> <CAL9jLaYGu3mOKEFGESEm8EmtH5bhijV1AhjYi44_4Kqv=2-2SQ@mail.gmail.com> <20120925201954.GG1854@pfrc> <506B5AA9.8000400@riw.us> <CAP-guGXpfT46+mP_Q-uvrWmFbt_pOfEYw3HqtLRg98WweKK3bA@mail.gmail.com> <506C4996.7010909@riw.us> <CAP-guGX6A8izxpRRLde_NNXy8fOA7JwTc4t3VhD_G=AiScp8eA@mail.gmail.com> <506C7DE7.1010609@riw.us> <CAP-guGUiGJ3jH1P4imrOyDaBp1+uqhOSTrYeyQJkPtiO_gRCuA@mail.gmail.com>
In-Reply-To: <CAP-guGUiGJ3jH1P4imrOyDaBp1+uqhOSTrYeyQJkPtiO_gRCuA@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Antivirus-Scanner: Seems clean.  You should still use an Antivirus Scanner
Cc: grow@ietf.org
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, 04 Oct 2012 01:36:58 -0000

> How do you know that the overlapping route takes traffic through the
> same path? AS path != routing path and BGP is a distance-vector
> protocol. Your router has no reliable knowledge of the routing path
> more than 1 hop away.

All that matters is that I draw the same traffic into my AS, where the
more specifics still exist, so I can optimally route the traffic out of
my AS --the same as I always have. You seem to be thinking that this
would be done at the edge in some way --that the originating AS would be
doing the suppression. That's not the way this is designed to work at all.

The suppression is supposed to take place at least one hop away from the
route origin, and only if I can be reasonably certain that my
suppression of the longer route isn't going to change traffic patterns
from my perspective.

> Even if you could know the routing path was the same, consider:
> 
> ISP 88
> 10.1.0.0/16 via 2 3
> 10.1.1.0/24 via 2 3 (suppressed)
> 
> ISP 99
> 10.1.0.0/16 via 4 12 62 16 2 3
> 10.1.1.0/24 via 4 8 9 5 3 (not suppressed)
> 
> ISP 111 (customer of 88 & 99):
> 10.1.0.0/16 via 88 2 3
> 10.1.1.0/24 via 99 4 8 9 5 3
> 
> Best route was lost. But 111 can't safely suppress the /24 route
> because he has no knowledge of whether the /24 is reachable via 88 1 2
> 3. To the best of 111's knowledge, AS3 might look like this right now:

So, I'm trying to guess how you have things connected, but it seems like
what you're saying is that the longer prefix is suppressed, leaving a
shorter prefix that loses to another peer's shorter prefix which doesn't
actually contain the longer prefix.

Further, the two AS' advertising the two shorter prefixes cannot be
connected to one another.

I actually don't see how this would work in normal routing, much less if
you suppress the shorter --you're saying you have a situation where one
AS has access to 10.1.0.0/16 and 10.1.1.0/24, and another has access to
10.1.0.0/16, but not 10.1.1.0/24. I'd like to see a network designed
where this is true without data plane filters implemented.

:-)

Russ

From russw@riw.us  Wed Oct  3 18:37:45 2012
Return-Path: <russw@riw.us>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E2C7E11E80BF for <grow@ietfa.amsl.com>; Wed,  3 Oct 2012 18:37:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.522
X-Spam-Level: 
X-Spam-Status: No, score=-2.522 tagged_above=-999 required=5 tests=[AWL=0.077,  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 507+cvPBiF5K for <grow@ietfa.amsl.com>; Wed,  3 Oct 2012 18:37:45 -0700 (PDT)
Received: from da31.namelessnet.net (da31.namelessnet.net [74.124.205.66]) by ietfa.amsl.com (Postfix) with ESMTP id 8DCEB11E8091 for <grow@ietf.org>; Wed,  3 Oct 2012 18:37:45 -0700 (PDT)
Received: from cpe-065-190-156-032.nc.res.rr.com ([65.190.156.32] helo=[192.168.100.51]) by da31.namelessnet.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.77) (envelope-from <russw@riw.us>) id 1TJaNl-0003cQ-6B; Wed, 03 Oct 2012 18:37:45 -0700
Message-ID: <506CE86A.1060301@riw.us>
Date: Wed, 03 Oct 2012 21:37:46 -0400
From: Russ White <russw@riw.us>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120907 Thunderbird/15.0.1
MIME-Version: 1.0
To: Jared Mauch <jared@puck.nether.net>
References: <CC5BE44F.2A792%pds@lugs.com> <CAP-guGXL6-AkPSnMJ7TY-dVafOMXKtFNQCUdKcrVGrbHoQNSXQ@mail.gmail.com> <CAL9jLaYGu3mOKEFGESEm8EmtH5bhijV1AhjYi44_4Kqv=2-2SQ@mail.gmail.com> <20120925201954.GG1854@pfrc> <5062BAE8.6010801@inex.ie> <506B5B3B.1020507@riw.us> <8121770B-66E1-47A9-90B5-563D0E106939@puck.nether.net> <506C49EE.9060202@riw.us> <FF0E84E6-19DD-4951-A9AD-3998B704129A@puck.nether.net>
In-Reply-To: <FF0E84E6-19DD-4951-A9AD-3998B704129A@puck.nether.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Antivirus-Scanner: Seems clean.  You should still use an Antivirus Scanner
Cc: grow@ietf.org
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, 04 Oct 2012 01:37:46 -0000

> I'm not sure how to convince smaller folks to do the right thing if the big people can't sort it out. (even with the right hooks).

You automate the process as much as possible, and let them sort out the
problems that result from their messed up shorter prefix routes.

:-)

Russ

From paaguti@gmail.com  Thu Oct  4 02:47:19 2012
Return-Path: <paaguti@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 3B87C21F86A5 for <grow@ietfa.amsl.com>; Thu,  4 Oct 2012 02:47:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UdsFpoJbq109 for <grow@ietfa.amsl.com>; Thu,  4 Oct 2012 02:47:18 -0700 (PDT)
Received: from mail-pa0-f44.google.com (mail-pa0-f44.google.com [209.85.220.44]) by ietfa.amsl.com (Postfix) with ESMTP id C251221F86A2 for <grow@ietf.org>; Thu,  4 Oct 2012 02:47:18 -0700 (PDT)
Received: by mail-pa0-f44.google.com with SMTP id fb11so354314pad.31 for <grow@ietf.org>; Thu, 04 Oct 2012 02:47:18 -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=8vFoeA98KapYFkpQS5uL27Mzlcy1WVfiejK1hf8WxqU=; b=RYaBHomp5lN4/6a2Rhh+L3l19E93m3Gt3u2gsSIqtH5DK0tsHoSkkz13OOFyCzdsUQ arXLPt8Oty7BS2Tsey3aopiaaXZM2ptNZMrsEv8iwcmHi2ZRsdfuTQoZFjlk95NwzcNQ YXxZV/c1zGK+2DI7wCNZ6Ff4EDS6IKQnykriNEVc7FsNP75LQld7tDzVljAQYCDHj/kw nxUnTn0v6+IsBCQ1EkpPFKGWnOU43XyUHpXyuXHEOAxF/YOvUXoXwgtax9PNBsNRX5nO SOxmPt0Z6KLrnXRM+FoOc3Afk2Pk+11FbD+quMzeCD7JaVhDAOk33YTnyK/ALgD3/ZrD QwOg==
MIME-Version: 1.0
Received: by 10.68.235.38 with SMTP id uj6mr20399552pbc.3.1349344038544; Thu, 04 Oct 2012 02:47:18 -0700 (PDT)
Received: by 10.66.228.4 with HTTP; Thu, 4 Oct 2012 02:47:18 -0700 (PDT)
In-Reply-To: <CA+b+ERkEQiUGuWyQJdtKZvF_8NH1ouqWYcH66_bQNiOnZWdEsQ@mail.gmail.com>
References: <CC5BE44F.2A792%pds@lugs.com> <CAP-guGXL6-AkPSnMJ7TY-dVafOMXKtFNQCUdKcrVGrbHoQNSXQ@mail.gmail.com> <CAL9jLaYGu3mOKEFGESEm8EmtH5bhijV1AhjYi44_4Kqv=2-2SQ@mail.gmail.com> <20120925201954.GG1854@pfrc> <506B5AA9.8000400@riw.us> <CAP-guGXpfT46+mP_Q-uvrWmFbt_pOfEYw3HqtLRg98WweKK3bA@mail.gmail.com> <506C4996.7010909@riw.us> <CAP-guGX6A8izxpRRLde_NNXy8fOA7JwTc4t3VhD_G=AiScp8eA@mail.gmail.com> <506C7DE7.1010609@riw.us> <CA+b+ERkEQiUGuWyQJdtKZvF_8NH1ouqWYcH66_bQNiOnZWdEsQ@mail.gmail.com>
Date: Thu, 4 Oct 2012 11:47:18 +0200
Message-ID: <CAO48Bk_1LsZEoYxRQSM=KXbnWDbTx9M_WBzg+dmzn=750ynvPg@mail.gmail.com>
From: Pedro Andres Aranda Gutierrez <paaguti@gmail.com>
To: Robert Raszuk <robert@raszuk.net>
Content-Type: text/plain; charset=ISO-8859-1
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: Thu, 04 Oct 2012 09:47:19 -0000

Just to add a bit more of entropy...

As part of my PhD, I'm working on a way to reduce the Internet's core
routing tables by looking at prefixes that can be aggregated. I'm
following this discussion, because of that and I suddenly see a
'Pedro' being mentioned... Is it me? :-)

Best regards,
/PA

On Wed, Oct 3, 2012 at 8:27 PM, Robert Raszuk <robert@raszuk.net> wrote:
> Russ,
>
>> Yes.
>>
>> Sorry, but it is always true that by removing information you always
>> lose optimality (you increase stretch). Whether that removal is done at
>> the edge or in the core, the result is always the same. There are two
>> ironclad rules of routing:
>>
>> - Removing information decreases optimal routing.
>
> No.
>
> If you remove information which is redundant and when such removal
> will not result in even a single bit of sub-optimal routing what you
> wrote above is false "ironclad rule".
>
> Also the critical piece is that the determination when and what should
> be removed must be 100% automated. There is no way where manual
> intervention would be required for any scheme to work right. And your
> proposal does require manual NOC intervention as you have already
> confirmed today.
>
> The proposal from Pedro however is automated, adjust itself to
> topology changes as well as removed only redundant information where
> such removal does not impact a single bit routing optimality.
>
> Rgs,
> R.
> _______________________________________________
> GROW mailing list
> GROW@ietf.org
> https://www.ietf.org/mailman/listinfo/grow

From rraszuk@gmail.com  Thu Oct  4 05:25:46 2012
Return-Path: <rraszuk@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 9425121F8685 for <grow@ietfa.amsl.com>; Thu,  4 Oct 2012 05:25:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.964
X-Spam-Level: 
X-Spam-Status: No, score=-2.964 tagged_above=-999 required=5 tests=[AWL=0.013,  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 k2dsL-PK1k91 for <grow@ietfa.amsl.com>; Thu,  4 Oct 2012 05:25:46 -0700 (PDT)
Received: from mail-ie0-f172.google.com (mail-ie0-f172.google.com [209.85.223.172]) by ietfa.amsl.com (Postfix) with ESMTP id 0BE7221F8680 for <grow@ietf.org>; Thu,  4 Oct 2012 05:25:45 -0700 (PDT)
Received: by mail-ie0-f172.google.com with SMTP id 9so991644iec.31 for <grow@ietf.org>; Thu, 04 Oct 2012 05:25:45 -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:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=9Aqzb6oKzkC0rATiO141Nr5646YzgnAvB219J3DTjvs=; b=Cfek35SaNGXLC1zEw1XELTzlnUtll4GWIFVMwxuHVeDofQIOcSHStNtkta5/C78rYw YGwrqLwDo4K0w4qDZTc0NIIedYEq/ygdNnt09WYk9hGxLw5gCYnmPG5E3HgvMpXgi8R8 7s6BEG4uMIrDoQ2m/QiWT7nJVv9xPT/P1qPLJbajMaUiPhLbWYi8XKm7Ilc6v8tpoVq1 qsJz+Z/f5KUEKOVz9ZyEeVUAwKsih6HnnT+Eexz3qSkJ3+S/43Elwac/lEl+qay5PnVk x03I3Uq5Vt4BEWbFT3OyT5NPVsz4I0ZQJxnvXRD1zeB4pKRYwCemsfO2h+Plx1aWjKFH wFeA==
MIME-Version: 1.0
Received: by 10.50.47.201 with SMTP id f9mr4937014ign.44.1349353545543; Thu, 04 Oct 2012 05:25:45 -0700 (PDT)
Sender: rraszuk@gmail.com
Received: by 10.42.68.133 with HTTP; Thu, 4 Oct 2012 05:25:45 -0700 (PDT)
In-Reply-To: <CAO48Bk_1LsZEoYxRQSM=KXbnWDbTx9M_WBzg+dmzn=750ynvPg@mail.gmail.com>
References: <CC5BE44F.2A792%pds@lugs.com> <CAP-guGXL6-AkPSnMJ7TY-dVafOMXKtFNQCUdKcrVGrbHoQNSXQ@mail.gmail.com> <CAL9jLaYGu3mOKEFGESEm8EmtH5bhijV1AhjYi44_4Kqv=2-2SQ@mail.gmail.com> <20120925201954.GG1854@pfrc> <506B5AA9.8000400@riw.us> <CAP-guGXpfT46+mP_Q-uvrWmFbt_pOfEYw3HqtLRg98WweKK3bA@mail.gmail.com> <506C4996.7010909@riw.us> <CAP-guGX6A8izxpRRLde_NNXy8fOA7JwTc4t3VhD_G=AiScp8eA@mail.gmail.com> <506C7DE7.1010609@riw.us> <CA+b+ERkEQiUGuWyQJdtKZvF_8NH1ouqWYcH66_bQNiOnZWdEsQ@mail.gmail.com> <CAO48Bk_1LsZEoYxRQSM=KXbnWDbTx9M_WBzg+dmzn=750ynvPg@mail.gmail.com>
Date: Thu, 4 Oct 2012 14:25:45 +0200
X-Google-Sender-Auth: 31EZHLYowgKtE7ne80TYAvn-aqU
Message-ID: <CA+b+ERkP=mgbV5Gb1-kP2DAir42_U=UA9KQX_m1nwC4SypKVSQ@mail.gmail.com>
From: Robert Raszuk <robert@raszuk.net>
To: Pedro Andres Aranda Gutierrez <paaguti@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
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: Thu, 04 Oct 2012 12:25:46 -0000

> 'Pedro' being mentioned... Is it me? :-)

Nope :)

http://tools.ietf.org/id/draft-marques-idr-aggregate-00.txt

Best,
R.


On Thu, Oct 4, 2012 at 11:47 AM, Pedro Andres Aranda Gutierrez
<paaguti@gmail.com> wrote:
> Just to add a bit more of entropy...
>
> As part of my PhD, I'm working on a way to reduce the Internet's core
> routing tables by looking at prefixes that can be aggregated. I'm
> following this discussion, because of that and I suddenly see a
> 'Pedro' being mentioned... Is it me? :-)
>
> Best regards,
> /PA
>
> On Wed, Oct 3, 2012 at 8:27 PM, Robert Raszuk <robert@raszuk.net> wrote:
>> Russ,
>>
>>> Yes.
>>>
>>> Sorry, but it is always true that by removing information you always
>>> lose optimality (you increase stretch). Whether that removal is done at
>>> the edge or in the core, the result is always the same. There are two
>>> ironclad rules of routing:
>>>
>>> - Removing information decreases optimal routing.
>>
>> No.
>>
>> If you remove information which is redundant and when such removal
>> will not result in even a single bit of sub-optimal routing what you
>> wrote above is false "ironclad rule".
>>
>> Also the critical piece is that the determination when and what should
>> be removed must be 100% automated. There is no way where manual
>> intervention would be required for any scheme to work right. And your
>> proposal does require manual NOC intervention as you have already
>> confirmed today.
>>
>> The proposal from Pedro however is automated, adjust itself to
>> topology changes as well as removed only redundant information where
>> such removal does not impact a single bit routing optimality.
>>
>> Rgs,
>> R.
>> _______________________________________________
>> GROW mailing list
>> GROW@ietf.org
>> https://www.ietf.org/mailman/listinfo/grow

From jhaas@slice.pfrc.org  Thu Oct  4 12:11:29 2012
Return-Path: <jhaas@slice.pfrc.org>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DE0E41F0C8E for <grow@ietfa.amsl.com>; Thu,  4 Oct 2012 12:11:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.335
X-Spam-Level: 
X-Spam-Status: No, score=-102.335 tagged_above=-999 required=5 tests=[AWL=-0.070, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, 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 lZQ2mSYiUo+3 for <grow@ietfa.amsl.com>; Thu,  4 Oct 2012 12:11:29 -0700 (PDT)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id 5FABB21F855E for <grow@ietf.org>; Thu,  4 Oct 2012 12:11:29 -0700 (PDT)
Received: by slice.pfrc.org (Postfix, from userid 1001) id EDAA8C3F0; Thu,  4 Oct 2012 15:11:28 -0400 (EDT)
Date: Thu, 4 Oct 2012 15:11:28 -0400
From: Jeffrey Haas <jhaas@pfrc.org>
To: "Alvaro Retana (aretana)" <aretana@cisco.com>
Message-ID: <20121004191128.GB6973@pfrc>
References: <CAP-guGXpfT46+mP_Q-uvrWmFbt_pOfEYw3HqtLRg98WweKK3bA@mail.gmail.com> <BBD66FD99311804F80324E8139B3C94EA39EC4@xmb-aln-x15.cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <BBD66FD99311804F80324E8139B3C94EA39EC4@xmb-aln-x15.cisco.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
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: Thu, 04 Oct 2012 19:11:30 -0000

On Wed, Oct 03, 2012 at 01:29:19PM +0000, Alvaro Retana (aretana) wrote:
> >10.1.0.0/16 AS path 12 5 4 2
> >10.1.1.0/24 AS path 12 1
> >
> >The 12->1 path, 1 being a completely different origin AS than the
> >covering route's origin from 2, is lost when 10.1.1.0/24 is aggregated
> >into 10.1.0.0/16.
> 
> The path is not aggregated.  Instead, the /24 would be marked as BOUNDED;
> the draft explains what that means:
> 
> =====
> 3.3 Handling Marked Routes Within the AS
> 
>    Routes marked with the BOUNDED community MAY not be installed in the
>    local RIB of routers within the AS.  This optional step will reduce
>    local RIB and forwarding table usage and volatility within the AS.
> 
> 3.4 Handling Marked Routes at the Outbound Edge
> 
>    Routes marked with the BOUNDED community SHOULD NOT be advertised to
>    external peers.  If they are advertised, they SHOULD then be marked
>    with the NO_EXPORT community.

I suspect my use of aggregated (implicit) conflicts with your use
(explicit/policy).  A recurring nightmare from working on RFC 4271 for me,
perhaps.

RFC 4271, sec 9.1.4:
:    If a BGP speaker receives overlapping routes, the Decision Process
:    MUST consider both routes based on the configured acceptance policy.
:    If both a less and a more specific route are accepted, then the
:    Decision Process MUST install, in Loc-RIB, either both the less and
:    the more specific routes or aggregate the two routes and install, in
:    Loc-RIB, the aggregated route, provided that both routes have the
:    same value of the NEXT_HOP attribute.
: 
:    If a BGP speaker chooses to aggregate, then it SHOULD either include
:    all ASes used to form the aggregate in an AS_SET, or add the
:    ATOMIC_AGGREGATE attribute to the route.  This attribute is now
:    primarily informational. [...]

No one that I'm aware of implements ATOMIC_AGGREGATE in this way.
As I pointed out many times during the standardization of 4271, your 3.4
above is effectively the same thing at a black-box perspective.  

Effectively, your bounded marking is largely what we should be doing for
ATOMIC_AGGREGATE.  The primary difference, and part of what I was alluding
to, is that if no path information is being lost, bounding is largely safe.
The partitioned AS case unfortunately is still not fully covered, but it's
better.

> I do want to note that the same problem exists today if the more specific
> route is discarded due to a policy related to the length of the prefixes
> accepted by a given SP -- or any other such policy that can be implemented
> with a manual filter.  As with the manual filter (as I said above), our
> proposal is optional, it is intended to facilitate the operation if you
> want to use it..

I believe I already agreed with this point.  The primary difference is
whether the operator is aware of whether it's safe to do this or not.  When
such a process is automated, that operator safety net is removed.  It's also
problematic in the sense that the party it may cause problems for is several
hops removed.  If you're a stubby enough AS, the loss of a more specific may
deny you reachability to the network.

-- Jeff

From jhaas@slice.pfrc.org  Thu Oct  4 12:28:33 2012
Return-Path: <jhaas@slice.pfrc.org>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 80B4421F84E7 for <grow@ietfa.amsl.com>; Thu,  4 Oct 2012 12:28:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.329
X-Spam-Level: 
X-Spam-Status: No, score=-102.329 tagged_above=-999 required=5 tests=[AWL=-0.064, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, 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 w9hUBUB9vrsb for <grow@ietfa.amsl.com>; Thu,  4 Oct 2012 12:28:33 -0700 (PDT)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id 14EA821F844A for <grow@ietf.org>; Thu,  4 Oct 2012 12:28:33 -0700 (PDT)
Received: by slice.pfrc.org (Postfix, from userid 1001) id B79DAC3F0; Thu,  4 Oct 2012 15:28:32 -0400 (EDT)
Date: Thu, 4 Oct 2012 15:28:32 -0400
From: Jeffrey Haas <jhaas@pfrc.org>
To: Russ White <russw@riw.us>
Message-ID: <20121004192832.GC6973@pfrc>
References: <CAP-guGXL6-AkPSnMJ7TY-dVafOMXKtFNQCUdKcrVGrbHoQNSXQ@mail.gmail.com> <CAL9jLaYGu3mOKEFGESEm8EmtH5bhijV1AhjYi44_4Kqv=2-2SQ@mail.gmail.com> <20120925201954.GG1854@pfrc> <506B5AA9.8000400@riw.us> <CAP-guGXpfT46+mP_Q-uvrWmFbt_pOfEYw3HqtLRg98WweKK3bA@mail.gmail.com> <506C4996.7010909@riw.us> <CAP-guGX6A8izxpRRLde_NNXy8fOA7JwTc4t3VhD_G=AiScp8eA@mail.gmail.com> <506C7DE7.1010609@riw.us> <CAP-guGUiGJ3jH1P4imrOyDaBp1+uqhOSTrYeyQJkPtiO_gRCuA@mail.gmail.com> <506CE83A.90401@riw.us>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <506CE83A.90401@riw.us>
User-Agent: Mutt/1.5.21 (2010-09-15)
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: Thu, 04 Oct 2012 19:28:33 -0000

On Wed, Oct 03, 2012 at 09:36:58PM -0400, Russ White wrote:
> All that matters is that I draw the same traffic into my AS, where the
> more specifics still exist, so I can optimally route the traffic out of
> my AS --the same as I always have. You seem to be thinking that this
> would be done at the edge in some way --that the originating AS would be
> doing the suppression. That's not the way this is designed to work at all.
> 
> The suppression is supposed to take place at least one hop away from the
> route origin, and only if I can be reasonably certain that my
> suppression of the longer route isn't going to change traffic patterns
> from my perspective.


AS 1 has 10.1.0.0/16
AS 2 has walked away with 10.1.1.0/24 

AS 1 doesn't providing routing for AS2's prefix.  
- This means that any traffic for AS 2 via AS 1 is dropped.
- This also means that AS 1 gets traffic for AS 2 in some cases, especially
  during events where AS 2's routes are dropped.  They were aware of this
  when they signed the contract to let AS 2 use that address space.

AS X receives the /16 and the /24 from upstream.  AS X bounds the /24 and
only advertises the /16.
AS Y receives only the /16 from upstream.

AS Z is dual-homed to AS X and Y.
AS Z receives the /16 from AS X and AS Y.

If AS Z chooses AS Y's /16, it has no reachability to AS 2.
If AS Y chooses AS X, everything works.

If AS X didn't implicitly aggregate the route, AS Z could use either AS X or Y.

Summary:
In cases where a subnet doesn't provide full reachability to contained more
specifics, suppressing the more specific may result in lost reachability
downstream.
a. This is less likely to be the case when the origin ASes are identical.
b. Even so, this doesn't preclude partitioned ASes.  Providers may leak the
   more specific for an internal network when internal topology isn't
   sufficiently diverse to cover certain types of outages.  See use cases for
   accepting one's own AS in an AS_PATH (junos 'loops', similar knobs in other
   implementations).
c. You'd be correct that even in cases like b, when you're "far enough
   away", implicit aggregation is probably safe again.  Such arguments have
   been used for route 'hop-limit' proposals.  The usual counter argument
   usually devolves down to Internet core-meshiness making hop-limits somewhat
   useless.

-- Jeff

From pds@lugs.com  Mon Oct  8 04:31:17 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 0301721F85C0 for <grow@ietfa.amsl.com>; Mon,  8 Oct 2012 04:31:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.998
X-Spam-Level: 
X-Spam-Status: No, score=-99.998 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VCrtzlEomiU7 for <grow@ietfa.amsl.com>; Mon,  8 Oct 2012 04:31:16 -0700 (PDT)
Received: from murdock.lugs.com (murdock.lugs.com [192.80.15.4]) by ietfa.amsl.com (Postfix) with ESMTP id 8A38521F8781 for <grow@ietf.org>; Mon,  8 Oct 2012 04:31:16 -0700 (PDT)
Received: from r9m1fw1 (unknown [123.231.16.167]) by murdock.lugs.com (Postfix) with ESMTPSA id F0CD5D342D for <grow@ietf.org>; Mon,  8 Oct 2012 07:31:14 -0400 (EDT)
From: "Peter Schoenmaker" <pds@lugs.com>
To: <grow@ietf.org>
Date: Mon, 8 Oct 2012 17:01:07 +0530
Message-ID: <000901cda548$6aeae620$40c0b260$@lugs.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_000A_01CDA576.84A4A8C0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac2lSAme7dlZlfflTry9MkFQ2s3xDA==
Content-Language: en-us
Subject: [GROW] Agenda items for Atlanta
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, 08 Oct 2012 11:31:17 -0000

This is a multipart message in MIME format.

------=_NextPart_000_000A_01CDA576.84A4A8C0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hello Grow,

 

We currently have a slot at IETF in Atlanta set for Friday.  Does anyone
have any agenda items?

 

Thanks

 

Peter

 

 


------=_NextPart_000_000A_01CDA576.84A4A8C0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

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


From pds@lugs.com  Fri Oct 12 00:26:31 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 0C52321F849A for <grow@ietfa.amsl.com>; Fri, 12 Oct 2012 00:26:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.998
X-Spam-Level: 
X-Spam-Status: No, score=-99.998 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id irBxQxQNXrLZ for <grow@ietfa.amsl.com>; Fri, 12 Oct 2012 00:26:29 -0700 (PDT)
Received: from murdock.lugs.com (murdock.lugs.com [192.80.15.4]) by ietfa.amsl.com (Postfix) with ESMTP id 6B24821F84A6 for <grow@ietf.org>; Fri, 12 Oct 2012 00:26:29 -0700 (PDT)
Received: from r9m1fw1 (hq.cariden.com [209.116.65.66]) by murdock.lugs.com (Postfix) with ESMTPSA id 5D2D7D3431 for <grow@ietf.org>; Fri, 12 Oct 2012 03:26:27 -0400 (EDT)
From: "Peter Schoenmaker" <pds@lugs.com>
To: <grow@ietf.org>
References: <000901cda548$6aeae620$40c0b260$@lugs.com>
In-Reply-To: <000901cda548$6aeae620$40c0b260$@lugs.com>
Date: Fri, 12 Oct 2012 12:56:22 +0530
Message-ID: <006d01cda84a$e368b9b0$aa3a2d10$@lugs.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_006E_01CDA878.FD2366B0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQJkx0j9+SdMAHCEi7FMLRsaLV/TxZaHBxDw
Content-Language: en-us
Subject: Re: [GROW] Agenda items for Atlanta
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, 12 Oct 2012 07:26:31 -0000

This is a multipart message in MIME format.

------=_NextPart_000_006E_01CDA878.FD2366B0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

This is another nudge to request any agenda items.

 

Thanks

 

Peter

 

 

 

From: grow-bounces@ietf.org [mailto:grow-bounces@ietf.org] On Behalf Of
Peter Schoenmaker
Sent: Monday, October 08, 2012 5:01 PM
To: grow@ietf.org
Subject: [GROW] Agenda items for Atlanta

 

Hello Grow,

 

We currently have a slot at IETF in Atlanta set for Friday.  Does anyone
have any agenda items?

 

Thanks

 

Peter

 

 


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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><META =
HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>This is another nudge to request any agenda =
items.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'>Thanks<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'>Peter<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
grow-bounces@ietf.org [mailto:grow-bounces@ietf.org] <b>On Behalf Of =
</b>Peter Schoenmaker<br><b>Sent:</b> Monday, October 08, 2012 5:01 =
PM<br><b>To:</b> grow@ietf.org<br><b>Subject:</b> [GROW] Agenda items =
for Atlanta<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Hello =
Grow,<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>We currently have a slot at IETF in Atlanta set for =
Friday.&nbsp; Does anyone have any agenda items?<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>Thanks<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>Peter<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div></body></html>
------=_NextPart_000_006E_01CDA878.FD2366B0--


From danny@tcb.net  Sun Oct 14 19:29:25 2012
Return-Path: <danny@tcb.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 101E321F84F8 for <grow@ietfa.amsl.com>; Sun, 14 Oct 2012 19:29:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.446
X-Spam-Level: 
X-Spam-Status: No, score=-102.446 tagged_above=-999 required=5 tests=[AWL=0.153, 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 E542gZ11AIKh for <grow@ietfa.amsl.com>; Sun, 14 Oct 2012 19:29:24 -0700 (PDT)
Received: from dog.tcb.net (dog.tcb.net [64.78.150.133]) by ietfa.amsl.com (Postfix) with ESMTP id 9AC0221F84EA for <grow@ietf.org>; Sun, 14 Oct 2012 19:29:24 -0700 (PDT)
Received: by dog.tcb.net (Postfix, from userid 0) id 57FB12680D7; Sun, 14 Oct 2012 20:29:24 -0600 (MDT)
Received: from dul1dmcphers-m2.home (pool-71-171-124-149.clppva.fios.verizon.net [71.171.124.149]) (authenticated-user smtp) (TLSv1/SSLv3 AES128-SHA 128/128) by dog.tcb.net with SMTP; Sun, 14 Oct 2012 20:29:24 -0600 (MDT) (envelope-from danny@tcb.net)
X-Avenger: version=0.7.8; receiver=dog.tcb.net; client-ip=71.171.124.149; client-port=64662; syn-fingerprint=65535:48:1:64:M1460,N,W1,N,N,T,S MacOS 10.4.8; data-bytes=0
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=us-ascii
From: Danny McPherson <danny@tcb.net>
In-Reply-To: <006d01cda84a$e368b9b0$aa3a2d10$@lugs.com>
Date: Sun, 14 Oct 2012 22:29:16 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <D6B09CC6-2E43-4590-8F44-A3147FABAA89@tcb.net>
References: <000901cda548$6aeae620$40c0b260$@lugs.com> <006d01cda84a$e368b9b0$aa3a2d10$@lugs.com>
To: Peter Schoenmaker <pds@lugs.com>
X-Mailer: Apple Mail (2.1283)
Cc: grow@ietf.org
Subject: Re: [GROW] Agenda items for Atlanta
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, 15 Oct 2012 02:29:25 -0000

We could say something about the IRR draft =
(draft-mcpherson-irr-routing-policy-considerations-) if there's =
sufficient interest.  There has been some discussion of it on the =
mailing list and GROW seems like a reasonable place to refine it and =
polish into something useful for publication.

Thoughts?


-danny


On Oct 12, 2012, at 3:26 AM, Peter Schoenmaker wrote:

> This is another nudge to request any agenda items.
> =20
> Thanks
> =20
> Peter
> =20
> =20
> =20
> From: grow-bounces@ietf.org [mailto:grow-bounces@ietf.org] On Behalf =
Of Peter Schoenmaker
> Sent: Monday, October 08, 2012 5:01 PM
> To: grow@ietf.org
> Subject: [GROW] Agenda items for Atlanta
> =20
> Hello Grow,
> =20
> We currently have a slot at IETF in Atlanta set for Friday.  Does =
anyone have any agenda items?
> =20
> Thanks
> =20
> Peter
> =20
> =20
> _______________________________________________
> GROW mailing list
> GROW@ietf.org
> https://www.ietf.org/mailman/listinfo/grow


From internet-drafts@ietf.org  Mon Oct 22 02:17:17 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 67E9421F889F; Mon, 22 Oct 2012 02:17:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.532
X-Spam-Level: 
X-Spam-Status: No, score=-102.532 tagged_above=-999 required=5 tests=[AWL=0.067, 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 adAORMpSD9sq; Mon, 22 Oct 2012 02:17:16 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C2F2E21F85F9; Mon, 22 Oct 2012 02:17:16 -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.34
Message-ID: <20121022091716.4413.60475.idtracker@ietfa.amsl.com>
Date: Mon, 22 Oct 2012 02:17:16 -0700
Cc: grow@ietf.org
Subject: [GROW] I-D Action: draft-ietf-grow-bgp-gshut-04.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Oct 2012 09:17:17 -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           : Graceful BGP session shutdown
	Author(s)       : Pierre Francois
                          Bruno Decraene
                          Cristel Pelsser
                          Keyur Patel
                          Clarence Filsfils
	Filename        : draft-ietf-grow-bgp-gshut-04.txt
	Pages           : 12
	Date            : 2012-10-22

Abstract:
   This draft describes operational procedures aimed at reducing the
   amount of traffic lost during planned maintenances of routers or
   links, involving the shutdown of BGP peering sessions.


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

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-grow-bgp-gshut-04

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


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


From internet-drafts@ietf.org  Mon Oct 22 14:00:47 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 54F4B1F0C61; Mon, 22 Oct 2012 14:00:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.586
X-Spam-Level: 
X-Spam-Status: No, score=-102.586 tagged_above=-999 required=5 tests=[AWL=0.013, 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 dBghmkV5oFLl; Mon, 22 Oct 2012 14:00:46 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EBD3E1F041C; Mon, 22 Oct 2012 14:00:46 -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.34
Message-ID: <20121022210046.6626.51587.idtracker@ietfa.amsl.com>
Date: Mon, 22 Oct 2012 14:00:46 -0700
Cc: grow@ietf.org
Subject: [GROW] I-D Action: draft-ietf-grow-bmp-07.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Oct 2012 21:00:47 -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           : BGP Monitoring Protocol
	Author(s)       : John Scudder
                          Rex Fernando
                          Stephen Stuart
	Filename        : draft-ietf-grow-bmp-07.txt
	Pages           : 22
	Date            : 2012-10-22

Abstract:
   This document defines a protocol, BMP, which can be used to monitor
   BGP sessions.  BMP is intended to provide a more convenient interface
   for obtaining route views for research purpose than the screen-
   scraping approach in common use today.  The design goals are to keep
   BMP simple, useful, easily implemented, and minimally service-
   affecting.  BMP is not suitable for use as a routing protocol.


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

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

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


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


From Donald.Smith@CenturyLink.com  Mon Oct 22 14:04:50 2012
Return-Path: <Donald.Smith@CenturyLink.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 841DC1F042B; Mon, 22 Oct 2012 14:04:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dyI6uPO-4AFm; Mon, 22 Oct 2012 14:04:49 -0700 (PDT)
Received: from sudnp799.qwest.com (sudnp799.qwest.com [155.70.32.99]) by ietfa.amsl.com (Postfix) with ESMTP id 7CDC91F041C; Mon, 22 Oct 2012 14:04:49 -0700 (PDT)
Received: from lxdenvmpc030.qintra.com (lxdenvmpc030.qintra.com [10.1.51.30]) by sudnp799.qwest.com (8.14.4/8.14.4) with ESMTP id q9ML4mUa029638 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 22 Oct 2012 15:04:48 -0600 (MDT)
Received: from lxdenvmpc030.qintra.com (unknown [127.0.0.1]) by IMSA (Postfix) with ESMTP id 39B071E006B; Mon, 22 Oct 2012 15:04:43 -0600 (MDT)
Received: from suomp60i.qintra.com (unknown [151.119.91.93]) by lxdenvmpc030.qintra.com (Postfix) with ESMTP id 06CFA1E0066; Mon, 22 Oct 2012 15:04:43 -0600 (MDT)
Received: from suomp60i.qintra.com (localhost [127.0.0.1]) by suomp60i.qintra.com (8.14.4/8.14.4) with ESMTP id q9ML4grM000291; Mon, 22 Oct 2012 16:04:42 -0500 (CDT)
Received: from vddcwhubex502.ctl.intranet (vddcwhubex502.qintra.com [151.119.128.29]) by suomp60i.qintra.com (8.14.4/8.14.4) with ESMTP id q9ML4fdx000244 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 22 Oct 2012 16:04:42 -0500 (CDT)
Received: from PDDCWMBXEX503.ctl.intranet ([fe80::9033:ef22:df02:32a9]) by vddcwhubex502.ctl.intranet ([2002:9777:801d::9777:801d]) with mapi id 14.02.0318.001; Mon, 22 Oct 2012 15:04:41 -0600
From: "Smith, Donald" <Donald.Smith@CenturyLink.com>
To: "'internet-drafts@ietf.org'" <internet-drafts@ietf.org>, "'i-d-announce@ietf.org'" <i-d-announce@ietf.org>
Thread-Topic: [GROW] I-D Action: draft-ietf-grow-bgp-gshut-04.txt
Thread-Index: AQHNsDYNiJVK4EBDakCtOZuBVste2ZfFz6aA
Date: Mon, 22 Oct 2012 21:04:41 +0000
Message-ID: <68EFACB32CF4464298EA2779B058889D0A23CFDF@PDDCWMBXEX503.ctl.intranet>
References: <20121022091716.4413.60475.idtracker@ietfa.amsl.com>
In-Reply-To: <20121022091716.4413.60475.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [151.119.128.8]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "'grow@ietf.org'" <grow@ietf.org>
Subject: Re: [GROW] I-D Action: draft-ietf-grow-bgp-gshut-04.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Oct 2012 21:04:50 -0000

Where are the "Changes to BGP Finite State Machine" listed?
BGP is supposed to be a Finite State Machine. Most early BGP rfcs called ou=
t the changes specifically.
At least up to rfc4724 (Graceful Restart).

This one CLEARLY changes the finite state machine but doesn't clearly state=
 what those changes are.
Many others have done the same thing it is nearly impossible to map out how=
 all those new rfcs have affected the state machine.




"Pampers use multiple layers of protection to prevent leakage. Rommel used =
defense in depth to defend European fortresses." (A.White) Donald.Smith@Cen=
turyLink.com


>-----Original Message-----
>From: grow-bounces@ietf.org [mailto:grow-bounces@ietf.org] On Behalf Of
>internet-drafts@ietf.org
>Sent: Monday, October 22, 2012 3:17 AM
>To: i-d-announce@ietf.org
>Cc: grow@ietf.org
>Subject: [GROW] I-D Action: draft-ietf-grow-bgp-gshut-04.txt
>
>
>A New Internet-Draft is available from the on-line Internet-Drafts
>directories.
> This draft is a work item of the Global Routing Operations Working
>Group of the IETF.
>
>	Title           : Graceful BGP session shutdown
>	Author(s)       : Pierre Francois
>                          Bruno Decraene
>                          Cristel Pelsser
>                          Keyur Patel
>                          Clarence Filsfils
>	Filename        : draft-ietf-grow-bgp-gshut-04.txt
>	Pages           : 12
>	Date            : 2012-10-22
>
>Abstract:
>   This draft describes operational procedures aimed at reducing the
>   amount of traffic lost during planned maintenances of routers or
>   links, involving the shutdown of BGP peering sessions.
>
>
>The IETF datatracker status page for this draft is:
>https://datatracker.ietf.org/doc/draft-ietf-grow-bgp-gshut
>
>There's also a htmlized version available at:
>http://tools.ietf.org/html/draft-ietf-grow-bgp-gshut-04
>
>A diff from the previous version is available at:
>http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-grow-bgp-gshut-04
>
>
>Internet-Drafts are also available by anonymous FTP at:
>ftp://ftp.ietf.org/internet-drafts/
>
>_______________________________________________
>GROW mailing list
>GROW@ietf.org
>https://www.ietf.org/mailman/listinfo/grow

From rraszuk@gmail.com  Mon Oct 22 14:23:26 2012
Return-Path: <rraszuk@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 66B5321F8907 for <grow@ietfa.amsl.com>; Mon, 22 Oct 2012 14:23:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.871
X-Spam-Level: 
X-Spam-Status: No, score=-2.871 tagged_above=-999 required=5 tests=[AWL=0.106,  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 oK94Xw6SYn4n for <grow@ietfa.amsl.com>; Mon, 22 Oct 2012 14:23:25 -0700 (PDT)
Received: from mail-ia0-f172.google.com (mail-ia0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id 5509921F8906 for <grow@ietf.org>; Mon, 22 Oct 2012 14:23:22 -0700 (PDT)
Received: by mail-ia0-f172.google.com with SMTP id o25so2878077iad.31 for <grow@ietf.org>; Mon, 22 Oct 2012 14:23:21 -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:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=kEKkCpeXUYEsNw1YqzYJIQRMau4UGlQ23mTF8aD7oKc=; b=hpCHekiYBJpKeY9GV+AtE4dJh4iGNFi7nHVbORJ1YEGz6xbXMv8rIW2HYh+Ulu8Tjo vtOBYlvnx9ohznj/c5BIbNBojISBmA/P147be4vkILnHDTt5RMfIPWIoJbKE8gZTcJRZ 1s+31C+588pwnW5man6slBUna5y8TT05am9EcA1v8SHcXHhMrrdGe8uNSdS9eCZ3VQ/y GclaR9hJwLt1aYno+1XYkbOEAFiRCkReY/OPod2pek48RKduxtPNUuMEU59l9RFlyKX9 1pGhOPlzBDAm7sutBwPaEgFlGYnT/kjy8KyAvjPsWGZ8ziLLDnmr2izNhSpD6LXH4tOr 3JVA==
MIME-Version: 1.0
Received: by 10.50.91.169 with SMTP id cf9mr17671702igb.44.1350941001701; Mon, 22 Oct 2012 14:23:21 -0700 (PDT)
Sender: rraszuk@gmail.com
Received: by 10.42.68.133 with HTTP; Mon, 22 Oct 2012 14:23:21 -0700 (PDT)
In-Reply-To: <20121022210046.6626.51587.idtracker@ietfa.amsl.com>
References: <20121022210046.6626.51587.idtracker@ietfa.amsl.com>
Date: Mon, 22 Oct 2012 23:23:21 +0200
X-Google-Sender-Auth: xsTCSM8qp_pTUhsKFQCG8GKJWIM
Message-ID: <CA+b+ERmVcCxcVi9bwYkQVoRMDQm9H-5WLYBROwdKX3xe5uR4wg@mail.gmail.com>
From: Robert Raszuk <robert@raszuk.net>
To: grow@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Cc: tli@cisco.com
Subject: Re: [GROW] I-D Action: draft-ietf-grow-bmp-07.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Oct 2012 21:23:26 -0000

Dear BMP authors,

The new version of the document seems still missing IMHO a very
important addition of additional BMP message allowing for "Raw inbound
BGP TCP stream" send in the BMP envelope to the station.

For the record I did proposed the small diff to add it to previous
version but apparently some authors are of the opinion that this
should go into separate BMP extension draft with which recommendation
I respectfully do disagree.

For the record of the list I am attaching the former diff which
accomplishes said _optional_ spec extension proposed on 21 Nov 2011.

Now this seems even more important as just replay of Adj_RIB_In would
miss all of those prefixes which were subject to drop due to BGP
Origin Validation on inbound. Of course I will leave to the GROW
members to decide on this optional spec extension and evaluate it's
applicability in their own BMP applications. In my view this is a
useful add-on yet as being optional not hurting any of the existing
shipping BMP implementations in any way.

Quote from email to the authors:

Finally I was able to find the proposed diff to draft ver -05 of BMP draft.

204a205,209
 >    o  TCP Stream Wrap (SW): This is an ongoing time shifted mirroring
 >       of all or selected received BGP TCP streams to the router. It
 >       could be very useful in verbatim/as-received BGP protocol
monitoring. The implementation of this capability is optional.
 >
 >
265a271
 >        *  Type = 5: TCP Stream Wrap (optional)
657c663,695
< 5.  Other Considerations
---
 > 5. TCP Stream Wrap
 >
 >    As router is receiving BGP data over TCP connection after
completing all TCP processing the payload is normally passed to BGP I/O.
At this time such payload may be locally mirrored, timestamped and
placed into temporary local storage.
 >
 >    At different time as well as possibly by different CPU such data
 >    may be wrapped in defined type 5 BMP header and replicated to BGP
receivers.
 >
 >    Reception of such copy of date stream will allow for number of
very important analysis to be done off-line by BMP station. Such
analysis may include:
 >
 >    * Monitoring of specific behaviour of given prefix or set of
 >      prefixes originated by any AS,
 >
 >    * Monitoring reception of BGP withdraws, their patterns as well as
 >      their
 >
 >    * Monitoring of update/withdraw frequencies
 >
 >    * Analysis on all received BGP messages before any BGP I/O and BGP
 >      inbound processing
 >
 >    * Removed the need to keep full BGP_RIB_In in cases where such
storage
 >      is not required from operational and functional perspective
 >
 >    * Easy ability to receive and interpret any protocol encoding errors
 >      (for example malformed updates or malformed BGP attributes)
 >
 >    * Provide ability to verify correct BGP MP_REACH and MP_UNREACH
 >      attribute ordering in BGP messages by sending peer
 >
 >    The implementation of this message time is optional.
 >
 >
 > 6.  Other Considerations
675c713
< 6.  Using BMP
---
 > 7.  Using BMP
694c732
< 7.  IANA Considerations
---
 > 8.  IANA Considerations
703a742
 >    o  Type 5: TCP Stream Wrap
705c744
<    Type values 5 through 128 MUST be assigned using the "Standards
---
 >    Type values 6 through 128 MUST be assigned using the "Standards

Best regards,
R.



On Mon, Oct 22, 2012 at 11:00 PM,  <internet-drafts@ietf.org> wrote:
>
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
>  This draft is a work item of the Global Routing Operations Working Group of the IETF.
>
>         Title           : BGP Monitoring Protocol
>         Author(s)       : John Scudder
>                           Rex Fernando
>                           Stephen Stuart
>         Filename        : draft-ietf-grow-bmp-07.txt
>         Pages           : 22
>         Date            : 2012-10-22
>
> Abstract:
>    This document defines a protocol, BMP, which can be used to monitor
>    BGP sessions.  BMP is intended to provide a more convenient interface
>    for obtaining route views for research purpose than the screen-
>    scraping approach in common use today.  The design goals are to keep
>    BMP simple, useful, easily implemented, and minimally service-
>    affecting.  BMP is not suitable for use as a routing protocol.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-grow-bmp
>
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-ietf-grow-bmp-07
>
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=draft-ietf-grow-bmp-07
>
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

From rraszuk@gmail.com  Mon Oct 22 14:29:55 2012
Return-Path: <rraszuk@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 9121B21F84C2 for <grow@ietfa.amsl.com>; Mon, 22 Oct 2012 14:29:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.88
X-Spam-Level: 
X-Spam-Status: No, score=-2.88 tagged_above=-999 required=5 tests=[AWL=0.098,  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 R1NJP2gapE4o for <grow@ietfa.amsl.com>; Mon, 22 Oct 2012 14:29:55 -0700 (PDT)
Received: from mail-ie0-f172.google.com (mail-ie0-f172.google.com [209.85.223.172]) by ietfa.amsl.com (Postfix) with ESMTP id E4F7C21F86D6 for <grow@ietf.org>; Mon, 22 Oct 2012 14:29:54 -0700 (PDT)
Received: by mail-ie0-f172.google.com with SMTP id 9so5136182iec.31 for <grow@ietf.org>; Mon, 22 Oct 2012 14:29:54 -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:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=fTXAy0Jr/Mf3pAPqn9Pzc4YHIyMiterr1ymZIz7sLPk=; b=WnZ4375G+w2GtHXANmCz56lY/15Nh1uP9AeevXzOnHRvbUtoPDagmkmfvAyAhpSekQ xqoZgscrTebkNTqsaHENqIP/jnxIj74OoQUSpumTVcKGNkmikA/L05K8Q3SBumwg2BQ+ ddzcb5rn58HSo6YL55J2Xg7m0W6iuRBkpPqh56DjZuawhn1QJ7fb+cYQZ647DnQHIicN wFEki8rbghtr3MjB+Ff4BEd83mlXm0ReDbQn/hSRnun2tI1CElphscdh/tnOqMT7oij2 x2VZANfEmqPGILG79XOVM+1vK6A9Q252Ao0eBFGz5UUkt6kjfnLb7ZSoILAK7Ui4Oey5 iLyQ==
MIME-Version: 1.0
Received: by 10.42.109.194 with SMTP id m2mr8850231icp.48.1350941394507; Mon, 22 Oct 2012 14:29:54 -0700 (PDT)
Sender: rraszuk@gmail.com
Received: by 10.42.68.133 with HTTP; Mon, 22 Oct 2012 14:29:54 -0700 (PDT)
In-Reply-To: <68EFACB32CF4464298EA2779B058889D0A23CFDF@PDDCWMBXEX503.ctl.intranet>
References: <20121022091716.4413.60475.idtracker@ietfa.amsl.com> <68EFACB32CF4464298EA2779B058889D0A23CFDF@PDDCWMBXEX503.ctl.intranet>
Date: Mon, 22 Oct 2012 23:29:54 +0200
X-Google-Sender-Auth: swfRQBtZ8xSFASa8x0dYwCNEhWg
Message-ID: <CA+b+ERnCLxHPU0V7feszdAM-GSsWWyTrBGPn-JHYwyxfv=Tdeg@mail.gmail.com>
From: Robert Raszuk <robert@raszuk.net>
To: "Smith, Donald" <Donald.Smith@centurylink.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] I-D Action: draft-ietf-grow-bgp-gshut-04.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Oct 2012 21:29:55 -0000

Hi Donald,

I do not think this proposal changes BGP state machine. It does not
affect connection state as such. It just de-preferes routes during
normal best path selection runs.

If it changes in any way it just delays the actual shutdown of the
connection which one may consider the operator's choice. Note that
what the draft is trying to automate and make easier operationally is
possible to do manually today with existing BGP state machine therefor
this seems like an argument that no changes to BGP state machine is
required.

Rgs,
R.

On Mon, Oct 22, 2012 at 11:04 PM, Smith, Donald
<Donald.Smith@centurylink.com> wrote:
> Where are the "Changes to BGP Finite State Machine" listed?
> BGP is supposed to be a Finite State Machine. Most early BGP rfcs called out the changes specifically.
> At least up to rfc4724 (Graceful Restart).
>
> This one CLEARLY changes the finite state machine but doesn't clearly state what those changes are.
> Many others have done the same thing it is nearly impossible to map out how all those new rfcs have affected the state machine.
>
>
>
>
> "Pampers use multiple layers of protection to prevent leakage. Rommel used defense in depth to defend European fortresses." (A.White) Donald.Smith@CenturyLink.com
>
>
>>-----Original Message-----
>>From: grow-bounces@ietf.org [mailto:grow-bounces@ietf.org] On Behalf Of
>>internet-drafts@ietf.org
>>Sent: Monday, October 22, 2012 3:17 AM
>>To: i-d-announce@ietf.org
>>Cc: grow@ietf.org
>>Subject: [GROW] I-D Action: draft-ietf-grow-bgp-gshut-04.txt
>>
>>
>>A New Internet-Draft is available from the on-line Internet-Drafts
>>directories.
>> This draft is a work item of the Global Routing Operations Working
>>Group of the IETF.
>>
>>       Title           : Graceful BGP session shutdown
>>       Author(s)       : Pierre Francois
>>                          Bruno Decraene
>>                          Cristel Pelsser
>>                          Keyur Patel
>>                          Clarence Filsfils
>>       Filename        : draft-ietf-grow-bgp-gshut-04.txt
>>       Pages           : 12
>>       Date            : 2012-10-22
>>
>>Abstract:
>>   This draft describes operational procedures aimed at reducing the
>>   amount of traffic lost during planned maintenances of routers or
>>   links, involving the shutdown of BGP peering sessions.
>>
>>
>>The IETF datatracker status page for this draft is:
>>https://datatracker.ietf.org/doc/draft-ietf-grow-bgp-gshut
>>
>>There's also a htmlized version available at:
>>http://tools.ietf.org/html/draft-ietf-grow-bgp-gshut-04
>>
>>A diff from the previous version is available at:
>>http://www.ietf.org/rfcdiff?url2=draft-ietf-grow-bgp-gshut-04
>>
>>
>>Internet-Drafts are also available by anonymous FTP at:
>>ftp://ftp.ietf.org/internet-drafts/
>>
>>_______________________________________________
>>GROW mailing list
>>GROW@ietf.org
>>https://www.ietf.org/mailman/listinfo/grow
> _______________________________________________
> GROW mailing list
> GROW@ietf.org
> https://www.ietf.org/mailman/listinfo/grow

From ietfc@btconnect.com  Tue Oct 23 03:16:10 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 94E4F21F8654 for <grow@ietfa.amsl.com>; Tue, 23 Oct 2012 03:16:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.384
X-Spam-Level: 
X-Spam-Status: No, score=-3.384 tagged_above=-999 required=5 tests=[AWL=0.215,  BAYES_00=-2.599, 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 3b4zqOdZ5BaY for <grow@ietfa.amsl.com>; Tue, 23 Oct 2012 03:16:08 -0700 (PDT)
Received: from db3outboundpool.messaging.microsoft.com (db3ehsobe001.messaging.microsoft.com [213.199.154.139]) by ietfa.amsl.com (Postfix) with ESMTP id 612AC21F8620 for <grow@ietf.org>; Tue, 23 Oct 2012 03:16:08 -0700 (PDT)
Received: from mail32-db3-R.bigfish.com (10.3.81.247) by DB3EHSOBE005.bigfish.com (10.3.84.25) with Microsoft SMTP Server id 14.1.225.23; Tue, 23 Oct 2012 10:16:07 +0000
Received: from mail32-db3 (localhost [127.0.0.1])	by mail32-db3-R.bigfish.com (Postfix) with ESMTP id 16C6C4A023E; Tue, 23 Oct 2012 10:16:07 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.249.213; KIP:(null); UIP:(null); IPV:NLI; H:AM2PRD0710HT005.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -26
X-BigFish: PS-26(zz98dI9371I936eI542M1432I1418Izz1202h1d1ah1d2ahzz8275ch1033IL17326ah8275bh8275dhz2dh2a8h5a9h668h839hd24hf0ah107ah1177h1179h1288h12a5h12a9h12bdh137ah139eh13b6h1441h1504h304l1155h)
Received: from mail32-db3 (localhost.localdomain [127.0.0.1]) by mail32-db3 (MessageSwitch) id 1350987365326223_32233; Tue, 23 Oct 2012 10:16:05 +0000 (UTC)
Received: from DB3EHSMHS018.bigfish.com (unknown [10.3.81.251])	by mail32-db3.bigfish.com (Postfix) with ESMTP id 4BB9FE0052; Tue, 23 Oct 2012 10:16:05 +0000 (UTC)
Received: from AM2PRD0710HT005.eurprd07.prod.outlook.com (157.56.249.213) by DB3EHSMHS018.bigfish.com (10.3.87.118) with Microsoft SMTP Server (TLS) id 14.1.225.23; Tue, 23 Oct 2012 10:16:03 +0000
Received: from SN2PRD0310HT004.namprd03.prod.outlook.com (157.56.234.5) by pod51017.outlook.com (10.255.165.40) with Microsoft SMTP Server (TLS) id 14.16.224.5; Tue, 23 Oct 2012 10:16:01 +0000
Message-ID: <042c01cdb107$5b3b1ae0$4001a8c0@gateway.2wire.net>
From: t.petch <ietfc@btconnect.com>
To: Robert Raszuk <robert@raszuk.net>, "Smith, Donald" <Donald.Smith@centurylink.com>
References: <20121022091716.4413.60475.idtracker@ietfa.amsl.com><68EFACB32CF4464298EA2779B058889D0A23CFDF@PDDCWMBXEX503.ctl.intranet> <CA+b+ERnCLxHPU0V7feszdAM-GSsWWyTrBGPn-JHYwyxfv=Tdeg@mail.gmail.com>
Date: Tue, 23 Oct 2012 11:15:31 +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.234.5]
X-OriginatorOrg: btconnect.com
Cc: grow@ietf.org
Subject: Re: [GROW] I-D Action: draft-ietf-grow-bgp-gshut-04.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Oct 2012 10:16:10 -0000

----- Original Message -----
From: "Robert Raszuk" <robert@raszuk.net>
To: "Smith, Donald" <Donald.Smith@centurylink.com>
Cc: <grow@ietf.org>
Sent: Monday, October 22, 2012 10:29 PM
> Hi Donald,
>
> I do not think this proposal changes BGP state machine. It does not
> affect connection state as such. It just de-preferes routes during
> normal best path selection runs.
>
> If it changes in any way it just delays the actual shutdown of the
> connection which one may consider the operator's choice. Note that
> what the draft is trying to automate and make easier operationally is
> possible to do manually today with existing BGP state machine therefor
> this seems like an argument that no changes to BGP state machine is
> required.

I am with Robert on this one.  The structure of the FSM, in terms of
states and events and state changes, is unaltered by this.

Arguably, this I-D changes the list of actions to be taken when Event 2
or Event 8 occurs in Established state but I think that such
enhancements have been with us for a while and that there is no reason
for them to be called out by this I-D in particular.

Tom Petch

> Rgs,
> R.
>
> On Mon, Oct 22, 2012 at 11:04 PM, Smith, Donald
> <Donald.Smith@centurylink.com> wrote:
> > Where are the "Changes to BGP Finite State Machine" listed?
> > BGP is supposed to be a Finite State Machine. Most early BGP rfcs
called out the changes specifically.
> > At least up to rfc4724 (Graceful Restart).
> >
> > This one CLEARLY changes the finite state machine but doesn't
clearly state what those changes are.
> > Many others have done the same thing it is nearly impossible to map
out how all those new rfcs have affected the state machine.
> >
> >
> >
> >
> > "Pampers use multiple layers of protection to prevent leakage.
Rommel used defense in depth to defend European fortresses." (A.White)
Donald.Smith@CenturyLink.com
> >
> >
> >>-----Original Message-----
> >>From: grow-bounces@ietf.org [mailto:grow-bounces@ietf.org] On Behalf
Of
> >>internet-drafts@ietf.org
> >>Sent: Monday, October 22, 2012 3:17 AM
> >>To: i-d-announce@ietf.org
> >>Cc: grow@ietf.org
> >>Subject: [GROW] I-D Action: draft-ietf-grow-bgp-gshut-04.txt
> >>
> >>
> >>A New Internet-Draft is available from the on-line Internet-Drafts
> >>directories.
> >> This draft is a work item of the Global Routing Operations Working
> >>Group of the IETF.
> >>
> >>       Title           : Graceful BGP session shutdown
> >>       Author(s)       : Pierre Francois
> >>                          Bruno Decraene
> >>                          Cristel Pelsser
> >>                          Keyur Patel
> >>                          Clarence Filsfils
> >>       Filename        : draft-ietf-grow-bgp-gshut-04.txt
> >>       Pages           : 12
> >>       Date            : 2012-10-22
> >>
> >>Abstract:
> >>   This draft describes operational procedures aimed at reducing the
> >>   amount of traffic lost during planned maintenances of routers or
> >>   links, involving the shutdown of BGP peering sessions.
> >>
> >>
> >>The IETF datatracker status page for this draft is:
> >>https://datatracker.ietf.org/doc/draft-ietf-grow-bgp-gshut
> >>
> >>There's also a htmlized version available at:
> >>http://tools.ietf.org/html/draft-ietf-grow-bgp-gshut-04
> >>
> >>A diff from the previous version is available at:
> >>http://www.ietf.org/rfcdiff?url2=draft-ietf-grow-bgp-gshut-04
> >>
> >>
> >>Internet-Drafts are also available by anonymous FTP at:
> >>ftp://ftp.ietf.org/internet-drafts/
> >>
> >>_______________________________________________
> >>GROW mailing list
> >>GROW@ietf.org
> >>https://www.ietf.org/mailman/listinfo/grow
> > _______________________________________________
> > GROW mailing list
> > GROW@ietf.org
> > https://www.ietf.org/mailman/listinfo/grow
> _______________________________________________
> GROW mailing list
> GROW@ietf.org
> https://www.ietf.org/mailman/listinfo/grow
>



From jgs@juniper.net  Tue Oct 23 10:38:11 2012
Return-Path: <jgs@juniper.net>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D9AA51F0C89 for <grow@ietfa.amsl.com>; Tue, 23 Oct 2012 10:38:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.753
X-Spam-Level: 
X-Spam-Status: No, score=-3.753 tagged_above=-999 required=5 tests=[AWL=-0.287, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, UNRESOLVED_TEMPLATE=3.132]
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 KXymqjp9W4OF for <grow@ietfa.amsl.com>; Tue, 23 Oct 2012 10:38:10 -0700 (PDT)
Received: from exprod7og115.obsmtp.com (exprod7og115.obsmtp.com [64.18.2.217]) by ietfa.amsl.com (Postfix) with ESMTP id 6158D1F0419 for <grow@ietf.org>; Tue, 23 Oct 2012 10:38:09 -0700 (PDT)
Received: from P-EMHUB01-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob115.postini.com ([64.18.6.12]) with SMTP ID DSNKUIbV/+sERGUuFInF57sfCzBJVKQRN2Mu@postini.com; Tue, 23 Oct 2012 10:38:09 PDT
Received: from P-CLDFE01-HQ.jnpr.net (172.24.192.59) by P-EMHUB01-HQ.jnpr.net (172.24.192.35) with Microsoft SMTP Server (TLS) id 8.3.213.0; Tue, 23 Oct 2012 10:36:42 -0700
Received: from o365mail.juniper.net (207.17.137.149) by o365mail.juniper.net (172.24.192.59) with Microsoft SMTP Server id 14.1.355.2; Tue, 23 Oct 2012 10:36:41 -0700
Received: from db3outboundpool.messaging.microsoft.com (213.199.154.141) by o365mail.juniper.net (207.17.137.149) with Microsoft SMTP Server (TLS) id 14.1.355.2; Tue, 23 Oct 2012 10:38:51 -0700
Received: from mail57-db3-R.bigfish.com (10.3.81.240) by DB3EHSOBE010.bigfish.com (10.3.84.30) with Microsoft SMTP Server id 14.1.225.23; Tue, 23 Oct 2012 17:36:38 +0000
Received: from mail57-db3 (localhost [127.0.0.1])	by mail57-db3-R.bigfish.com (Postfix) with ESMTP id B43A340211	for <grow@ietf.org.FOPE.CONNECTOR.OVERRIDE>; Tue, 23 Oct 2012 17:36:38 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.236.101; KIP:(null); UIP:(null); (null); H:BY2PRD0510HT005.namprd05.prod.outlook.com; R:internal; EFV:INT
X-SpamScore: -21
X-BigFish: PS-21(zz98dI9371I936eIc85fh1432Izz1202h1d1ah1d2ah1082kzz8275ch1033IL17326ah8275dhz2dh2a8h668h839hd25he5bhf0ah107ah1288h12a5h12bdh137ah139eh1441h1504h1155h)
Received: from mail57-db3 (localhost.localdomain [127.0.0.1]) by mail57-db3 (MessageSwitch) id 1351013795927169_1006; Tue, 23 Oct 2012 17:36:35 +0000 (UTC)
Received: from DB3EHSMHS015.bigfish.com (unknown [10.3.81.254])	by mail57-db3.bigfish.com (Postfix) with ESMTP id B25E2380291; Tue, 23 Oct 2012 17:36:35 +0000 (UTC)
Received: from BY2PRD0510HT005.namprd05.prod.outlook.com (157.56.236.101) by DB3EHSMHS015.bigfish.com (10.3.87.115) with Microsoft SMTP Server (TLS) id 14.1.225.23; Tue, 23 Oct 2012 17:36:32 +0000
Received: from sa-nc-common-37.static.jnpr.net (66.129.224.54) by pod51010.outlook.com (10.255.84.40) with Microsoft SMTP Server (TLS) id 14.16.224.5; Tue, 23 Oct 2012 17:36:20 +0000
Content-Type: multipart/alternative; boundary="Apple-Mail=_3FCB1942-5E47-468D-8DD2-ACB31D7B5072"
MIME-Version: 1.0 (Mac OS X Mail 6.1 \(1498\))
From: "John G. Scudder" <jgs@juniper.net>
In-Reply-To: <CA+b+ERmVcCxcVi9bwYkQVoRMDQm9H-5WLYBROwdKX3xe5uR4wg@mail.gmail.com>
Date: Tue, 23 Oct 2012 13:36:17 -0400
Message-ID: <AF17822D-15BA-4841-A9D5-2C25F903DFCD@juniper.net>
References: <20121022210046.6626.51587.idtracker@ietfa.amsl.com> <CA+b+ERmVcCxcVi9bwYkQVoRMDQm9H-5WLYBROwdKX3xe5uR4wg@mail.gmail.com>
To: Robert Raszuk <robert@raszuk.net>
X-Mailer: Apple Mail (2.1498)
X-Originating-IP: [66.129.224.54]
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
X-FOPE-CONNECTOR: Id%12219$Dn%CISCO.COM$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net
X-FOPE-CONNECTOR: Id%12219$Dn%IETF.ORG$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net
X-FOPE-CONNECTOR: Id%12219$Dn%RASZUK.NET$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net
Cc: tli@cisco.com, grow@ietf.org
Subject: Re: [GROW] I-D Action: draft-ietf-grow-bmp-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: Tue, 23 Oct 2012 17:38:12 -0000

--Apple-Mail=_3FCB1942-5E47-468D-8DD2-ACB31D7B5072
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="us-ascii"

Robert,

I was going to point that out in a summary of the latest changes, but =
you've beaten me to it.=20

My reasoning (I'll let the other authors speak for themselves if they =
wish) in not picking up this proposal was that I don't see any =
likelihood of it being implemented. Although the suggestion was that it =
be optional, my view is that if it won't be implemented, having it in =
the document detracts from the quality of the spec. "Perfection is =
reached not when there is nothing left to add, but when there is nothing =
left to take away."

That said, it's a WG doc, and as you say if the WG wants to direct the =
authors to spec that optional feature, OK. I was planning on presenting =
the changes in Atlanta, and that would be a good time to discuss the =
pros/cons. I'll plan to spend some time on it in my presentation.

Finally, as to your comment that "replay of Adj_RIB_In would miss all of =
those prefixes which were subject to drop due to BGP Origin Validation", =
I don't know why you think this. In our implementation, it isn't true.

--John

On Oct 22, 2012, at 5:23 PM, Robert Raszuk <robert@raszuk.net> wrote:

> Dear BMP authors,
>=20
> The new version of the document seems still missing IMHO a very
> important addition of additional BMP message allowing for "Raw inbound
> BGP TCP stream" send in the BMP envelope to the station.
>=20
> For the record I did proposed the small diff to add it to previous
> version but apparently some authors are of the opinion that this
> should go into separate BMP extension draft with which recommendation
> I respectfully do disagree.
>=20
> For the record of the list I am attaching the former diff which
> accomplishes said _optional_ spec extension proposed on 21 Nov 2011.
>=20
> Now this seems even more important as just replay of Adj_RIB_In would
> miss all of those prefixes which were subject to drop due to BGP
> Origin Validation on inbound. Of course I will leave to the GROW
> members to decide on this optional spec extension and evaluate it's
> applicability in their own BMP applications. In my view this is a
> useful add-on yet as being optional not hurting any of the existing
> shipping BMP implementations in any way.
>=20
> Quote from email to the authors:
>=20
> Finally I was able to find the proposed diff to draft ver -05 of BMP =
draft.
>=20
> 204a205,209
>>   o  TCP Stream Wrap (SW): This is an ongoing time shifted mirroring
>>      of all or selected received BGP TCP streams to the router. It
>>      could be very useful in verbatim/as-received BGP protocol
> monitoring. The implementation of this capability is optional.
>>=20
>>=20
> 265a271
>>       *  Type =3D 5: TCP Stream Wrap (optional)
> 657c663,695
> < 5.  Other Considerations
> ---
>> 5. TCP Stream Wrap
>>=20
>>   As router is receiving BGP data over TCP connection after
> completing all TCP processing the payload is normally passed to BGP =
I/O.
> At this time such payload may be locally mirrored, timestamped and
> placed into temporary local storage.
>>=20
>>   At different time as well as possibly by different CPU such data
>>   may be wrapped in defined type 5 BMP header and replicated to BGP
> receivers.
>>=20
>>   Reception of such copy of date stream will allow for number of
> very important analysis to be done off-line by BMP station. Such
> analysis may include:
>>=20
>>   * Monitoring of specific behaviour of given prefix or set of
>>     prefixes originated by any AS,
>>=20
>>   * Monitoring reception of BGP withdraws, their patterns as well as
>>     their
>>=20
>>   * Monitoring of update/withdraw frequencies
>>=20
>>   * Analysis on all received BGP messages before any BGP I/O and BGP
>>     inbound processing
>>=20
>>   * Removed the need to keep full BGP_RIB_In in cases where such
> storage
>>     is not required from operational and functional perspective
>>=20
>>   * Easy ability to receive and interpret any protocol encoding =
errors
>>     (for example malformed updates or malformed BGP attributes)
>>=20
>>   * Provide ability to verify correct BGP MP_REACH and MP_UNREACH
>>     attribute ordering in BGP messages by sending peer
>>=20
>>   The implementation of this message time is optional.
>>=20
>>=20
>> 6.  Other Considerations
> 675c713
> < 6.  Using BMP
> ---
>> 7.  Using BMP
> 694c732
> < 7.  IANA Considerations
> ---
>> 8.  IANA Considerations
> 703a742
>>   o  Type 5: TCP Stream Wrap
> 705c744
> <    Type values 5 through 128 MUST be assigned using the "Standards
> ---
>>   Type values 6 through 128 MUST be assigned using the "Standards
>=20
> Best regards,
> R.
>=20
>=20
>=20
> On Mon, Oct 22, 2012 at 11:00 PM,  <internet-drafts@ietf.org> wrote:
>>=20
>> A New Internet-Draft is available from the on-line Internet-Drafts =
directories.
>> This draft is a work item of the Global Routing Operations Working =
Group of the IETF.
>>=20
>>        Title           : BGP Monitoring Protocol
>>        Author(s)       : John Scudder
>>                          Rex Fernando
>>                          Stephen Stuart
>>        Filename        : draft-ietf-grow-bmp-07.txt
>>        Pages           : 22
>>        Date            : 2012-10-22
>>=20
>> Abstract:
>>   This document defines a protocol, BMP, which can be used to monitor
>>   BGP sessions.  BMP is intended to provide a more convenient =
interface
>>   for obtaining route views for research purpose than the screen-
>>   scraping approach in common use today.  The design goals are to =
keep
>>   BMP simple, useful, easily implemented, and minimally service-
>>   affecting.  BMP is not suitable for use as a routing protocol.
>>=20
>>=20
>> The IETF datatracker status page for this draft is:
>> https://datatracker.ietf.org/doc/draft-ietf-grow-bmp
>>=20
>> There's also a htmlized version available at:
>> http://tools.ietf.org/html/draft-ietf-grow-bmp-07
>>=20
>> A diff from the previous version is available at:
>> http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-grow-bmp-07
>>=20
>>=20
>> Internet-Drafts are also available by anonymous FTP at:
>> ftp://ftp.ietf.org/internet-drafts/
>>=20
>> _______________________________________________
>> I-D-Announce mailing list
>> I-D-Announce@ietf.org
>> https://www.ietf.org/mailman/listinfo/i-d-announce
>> Internet-Draft directories: http://www.ietf.org/shadow.html
>> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> _______________________________________________
> GROW mailing list
> GROW@ietf.org
> https://www.ietf.org/mailman/listinfo/grow
>=20


--Apple-Mail=_3FCB1942-5E47-468D-8DD2-ACB31D7B5072
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html; charset="us-ascii"

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
">Robert,<div><br></div><div>I was going to point that out in a summary =
of the latest changes, but you've beaten me to =
it.&nbsp;</div><div><br></div><div>My reasoning (I'll let the other =
authors speak for themselves if they wish) in not picking up this =
proposal was that I don't see any likelihood of it being implemented. =
Although the suggestion was that it be optional, my view is that if it =
won't be implemented, having it in the document detracts from the =
quality of the spec. "Perfection is reached not when there is nothing =
left to add, but when there is nothing left to take =
away."</div><div><br></div><div>That said, it's a WG doc, and as you say =
if the WG wants to direct the authors to spec that optional feature, OK. =
I was planning on presenting the changes in Atlanta, and that would be a =
good time to discuss the pros/cons. I'll plan to spend some time on it =
in my presentation.</div><div><br></div><div>Finally, as to your comment =
that "replay of Adj_RIB_In would&nbsp;miss all of those prefixes which =
were subject to drop due to BGP&nbsp;Origin Validation",&nbsp;I don't =
know why you think this. In our implementation, it isn't =
true.</div><div><br></div><div>--John</div><div><br></div><div><div><div>O=
n Oct 22, 2012, at 5:23 PM, Robert Raszuk &lt;<a =
href=3D"mailto:robert@raszuk.net">robert@raszuk.net</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite">Dear BMP authors,<br><br>The new version of the document =
seems still missing IMHO a very<br>important addition of additional BMP =
message allowing for "Raw inbound<br>BGP TCP stream" send in the BMP =
envelope to the station.<br><br>For the record I did proposed the small =
diff to add it to previous<br>version but apparently some authors are of =
the opinion that this<br>should go into separate BMP extension draft =
with which recommendation<br>I respectfully do disagree.<br><br>For the =
record of the list I am attaching the former diff which<br>accomplishes =
said _optional_ spec extension proposed on 21 Nov 2011.<br><br>Now this =
seems even more important as just replay of Adj_RIB_In would<br>miss all =
of those prefixes which were subject to drop due to BGP<br>Origin =
Validation on inbound.&nbsp;Of course I will leave to the =
GROW</blockquote><blockquote type=3D"cite">members to decide on this =
optional spec extension and evaluate it's<br>applicability in their own =
BMP applications. In my view this is a<br>useful add-on yet as being =
optional not hurting any of the existing<br>shipping BMP implementations =
in any way.<br><br>Quote from email to the authors:<br><br>Finally I was =
able to find the proposed diff to draft ver -05 of BMP =
draft.<br><br>204a205,209<br><blockquote type=3D"cite"> &nbsp;&nbsp;o =
&nbsp;TCP Stream Wrap (SW): This is an ongoing time shifted =
mirroring<br> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;of all or selected received =
BGP TCP streams to the router. It<br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;could be very useful in =
verbatim/as-received BGP protocol<br></blockquote>monitoring. The =
implementation of this capability is optional.<br><blockquote =
type=3D"cite"><br><br></blockquote>265a271<br><blockquote type=3D"cite"> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;* &nbsp;Type =3D 5: TCP Stream Wrap =
(optional)<br></blockquote>657c663,695<br>&lt; 5. &nbsp;Other =
Considerations<br>---<br><blockquote type=3D"cite">5. TCP Stream =
Wrap<br><br> &nbsp;&nbsp;As router is receiving BGP data over TCP =
connection after<br></blockquote>completing all TCP processing the =
payload is normally passed to BGP I/O.<br>At this time such payload may =
be locally mirrored, timestamped and<br>placed into temporary local =
storage.<br><blockquote type=3D"cite"><br> &nbsp;&nbsp;At different time =
as well as possibly by different CPU such data<br> &nbsp;&nbsp;may be =
wrapped in defined type 5 BMP header and replicated to =
BGP<br></blockquote>receivers.<br><blockquote type=3D"cite"><br> =
&nbsp;&nbsp;Reception of such copy of date stream will allow for number =
of<br></blockquote>very important analysis to be done off-line by BMP =
station. Such<br>analysis may include:<br><blockquote type=3D"cite"><br> =
&nbsp;&nbsp;* Monitoring of specific behaviour of given prefix or set =
of<br> &nbsp;&nbsp;&nbsp;&nbsp;prefixes originated by any AS,<br><br> =
&nbsp;&nbsp;* Monitoring reception of BGP withdraws, their patterns as =
well as<br> &nbsp;&nbsp;&nbsp;&nbsp;their<br><br> &nbsp;&nbsp;* =
Monitoring of update/withdraw frequencies<br><br> &nbsp;&nbsp;* Analysis =
on all received BGP messages before any BGP I/O and BGP<br> =
&nbsp;&nbsp;&nbsp;&nbsp;inbound processing<br><br> &nbsp;&nbsp;* Removed =
the need to keep full BGP_RIB_In in cases where =
such<br></blockquote>storage<br><blockquote type=3D"cite"> =
&nbsp;&nbsp;&nbsp;&nbsp;is not required from operational and functional =
perspective<br><br> &nbsp;&nbsp;* Easy ability to receive and interpret =
any protocol encoding errors<br> &nbsp;&nbsp;&nbsp;&nbsp;(for example =
malformed updates or malformed BGP attributes)<br><br> &nbsp;&nbsp;* =
Provide ability to verify correct BGP MP_REACH and MP_UNREACH<br> =
&nbsp;&nbsp;&nbsp;&nbsp;attribute ordering in BGP messages by sending =
peer<br><br> &nbsp;&nbsp;The implementation of this message time is =
optional.<br><br><br>6. &nbsp;Other =
Considerations<br></blockquote>675c713<br>&lt; 6. &nbsp;Using =
BMP<br>---<br><blockquote type=3D"cite">7. &nbsp;Using =
BMP<br></blockquote>694c732<br>&lt; 7. &nbsp;IANA =
Considerations<br>---<br><blockquote type=3D"cite">8. &nbsp;IANA =
Considerations<br></blockquote>703a742<br><blockquote type=3D"cite"> =
&nbsp;&nbsp;o &nbsp;Type 5: TCP Stream =
Wrap<br></blockquote>705c744<br>&lt; &nbsp;&nbsp;&nbsp;Type values 5 =
through 128 MUST be assigned using the "Standards<br>---<br><blockquote =
type=3D"cite"> &nbsp;&nbsp;Type values 6 through 128 MUST be assigned =
using the "Standards<br></blockquote><br>Best =
regards,<br>R.<br><br><br><br>On Mon, Oct 22, 2012 at 11:00 PM, =
&nbsp;&lt;<a =
href=3D"mailto:internet-drafts@ietf.org">internet-drafts@ietf.org</a>&gt; =
wrote:<br><blockquote type=3D"cite"><br>A New Internet-Draft is =
available from the on-line Internet-Drafts directories.<br> This draft =
is a work item of the Global Routing Operations Working Group of the =
IETF.<br><br> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Title =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: BGP =
Monitoring Protocol<br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Author(s) =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: John Scudder<br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;Rex Fernando<br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;Stephen Stuart<br> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Filename =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: =
draft-ietf-grow-bmp-07.txt<br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Pages =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: 22<br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Date =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: =
2012-10-22<br><br>Abstract:<br> &nbsp;&nbsp;This document defines a =
protocol, BMP, which can be used to monitor<br> &nbsp;&nbsp;BGP =
sessions. &nbsp;BMP is intended to provide a more convenient =
interface<br> &nbsp;&nbsp;for obtaining route views for research purpose =
than the screen-<br> &nbsp;&nbsp;scraping approach in common use today. =
&nbsp;The design goals are to keep<br> &nbsp;&nbsp;BMP simple, useful, =
easily implemented, and minimally service-<br> &nbsp;&nbsp;affecting. =
&nbsp;BMP is not suitable for use as a routing protocol.<br><br><br>The =
IETF datatracker status page for this draft is:<br><a =
href=3D"https://datatracker.ietf.org/doc/draft-ietf-grow-bmp">https://data=
tracker.ietf.org/doc/draft-ietf-grow-bmp</a><br><br>There's also a =
htmlized version available =
at:<br>http://tools.ietf.org/html/draft-ietf-grow-bmp-07<br><br>A diff =
from the previous version is available =
at:<br>http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-grow-bmp-07<br><br><b=
r>Internet-Drafts are also available by anonymous FTP =
at:<br>ftp://ftp.ietf.org/internet-drafts/<br><br>________________________=
_______________________<br>I-D-Announce mailing =
list<br>I-D-Announce@ietf.org<br>https://www.ietf.org/mailman/listinfo/i-d=
-announce<br>Internet-Draft directories: =
http://www.ietf.org/shadow.html<br>or =
ftp://ftp.ietf.org/ietf/1shadow-sites.txt<br></blockquote>________________=
_______________________________<br>GROW mailing list<br><a =
href=3D"mailto:GROW@ietf.org">GROW@ietf.org</a><br>https://www.ietf.org/ma=
ilman/listinfo/grow<br><br></blockquote></div><br></div></body></html>=

--Apple-Mail=_3FCB1942-5E47-468D-8DD2-ACB31D7B5072--

From jgs@juniper.net  Tue Oct 23 11:20:10 2012
Return-Path: <jgs@juniper.net>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8073A11E8108 for <grow@ietfa.amsl.com>; Tue, 23 Oct 2012 11:20:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.741
X-Spam-Level: 
X-Spam-Status: No, score=-3.741 tagged_above=-999 required=5 tests=[AWL=-0.274, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, UNRESOLVED_TEMPLATE=3.132]
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 3yaYVY3TgpMp for <grow@ietfa.amsl.com>; Tue, 23 Oct 2012 11:20:08 -0700 (PDT)
Received: from exprod7og109.obsmtp.com (exprod7og109.obsmtp.com [64.18.2.171]) by ietfa.amsl.com (Postfix) with ESMTP id 7B4CA11E8103 for <grow@ietf.org>; Tue, 23 Oct 2012 11:20:07 -0700 (PDT)
Received: from P-EMHUB02-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob109.postini.com ([64.18.6.12]) with SMTP ID DSNKUIbf1jzLI1WqICbRLJmA8siQ6lB0G3bF@postini.com; Tue, 23 Oct 2012 11:20:07 PDT
Received: from P-CLDFE02-HQ.jnpr.net (172.24.192.60) by P-EMHUB02-HQ.jnpr.net (172.24.192.36) with Microsoft SMTP Server (TLS) id 8.3.213.0; Tue, 23 Oct 2012 11:17:23 -0700
Received: from o365mail.juniper.net (207.17.137.224) by o365mail.juniper.net (172.24.192.60) with Microsoft SMTP Server id 14.1.355.2; Tue, 23 Oct 2012 11:17:23 -0700
Received: from am1outboundpool.messaging.microsoft.com (213.199.154.205) by o365mail.juniper.net (207.17.137.224) with Microsoft SMTP Server (TLS) id 14.1.355.2; Tue, 23 Oct 2012 11:23:01 -0700
Received: from mail67-am1-R.bigfish.com (10.3.201.228) by AM1EHSOBE008.bigfish.com (10.3.204.28) with Microsoft SMTP Server id 14.1.225.23; Tue, 23 Oct 2012 18:16:46 +0000
Received: from mail67-am1 (localhost [127.0.0.1])	by mail67-am1-R.bigfish.com (Postfix) with ESMTP id 0A425601B8	for <grow@ietf.org.FOPE.CONNECTOR.OVERRIDE>; Tue, 23 Oct 2012 18:16:46 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.236.101; KIP:(null); UIP:(null); (null); H:BY2PRD0510HT004.namprd05.prod.outlook.com; R:internal; EFV:INT
X-SpamScore: -17
X-BigFish: PS-17(zzzz1202h1d1ah1d2ah1082kzz1033IL17326ah8275dhz2dh2a8h668h839h944hd25he5bhf0ah107ah1220h1288h12a5h12a9h12bdh137ah139eh13b6h1441h1504h1537h1155h)
Received: from mail67-am1 (localhost.localdomain [127.0.0.1]) by mail67-am1 (MessageSwitch) id 1351016203651349_8119; Tue, 23 Oct 2012 18:16:43 +0000 (UTC)
Received: from AM1EHSMHS003.bigfish.com (unknown [10.3.201.232])	by mail67-am1.bigfish.com (Postfix) with ESMTP id 9D50120004B	for <grow@ietf.org>; Tue, 23 Oct 2012 18:16:43 +0000 (UTC)
Received: from BY2PRD0510HT004.namprd05.prod.outlook.com (157.56.236.101) by AM1EHSMHS003.bigfish.com (10.3.207.103) with Microsoft SMTP Server (TLS) id 14.1.225.23; Tue, 23 Oct 2012 18:16:42 +0000
Received: from sa-nc-common-37.static.jnpr.net (66.129.224.51) by pod51010.outlook.com (10.255.84.39) with Microsoft SMTP Server (TLS) id 14.16.224.5; Tue, 23 Oct 2012 18:16:31 +0000
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 6.1 \(1498\))
From: "John G. Scudder" <jgs@juniper.net>
In-Reply-To: <20121022210046.6626.51587.idtracker@ietfa.amsl.com>
Date: Tue, 23 Oct 2012 14:16:28 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <7E017E84-A17A-4D83-AC07-DF591B51DA9C@juniper.net>
References: <20121022210046.6626.51587.idtracker@ietfa.amsl.com>
To: <grow@ietf.org>
X-Mailer: Apple Mail (2.1498)
X-Originating-IP: [66.129.224.51]
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
X-FOPE-CONNECTOR: Id%12219$Dn%IETF.ORG$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net
Subject: Re: [GROW] I-D Action: draft-ietf-grow-bmp-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: Tue, 23 Oct 2012 18:20:10 -0000

You can get all the gory details from the diff =
(http://tools.ietf.org/rfcdiff?url2=3Ddraft-ietf-grow-bmp-07.txt) but =
here's my summary of the major differences between -03 and -04:

- Bumped length field to 32-bit (was 16-bit, which isn't enough if =
draft-ietf-idr-bgp-extended-messages-03 is in use).
- Session establishment must be rate-controlled.
- More information in Initiation message.
- Added several new stat types.
- Permit multiplexing pre- and post-policy Adj-RIBs-In.
- Allow monitoring station to be active party in establishing TCP =
connection.
- Introduced Termination message.
- Restructuring and terminology changes for clarity and readability.

I believe the changes take in all the suggestions from the WG, with the =
following exceptions:

- "Raw inbound BGP TCP stream", just discussed in another message.
- Instrumenting next hops. While a promising idea this would introduce =
significant complexity and I think falls under the "best is the enemy of =
good" heading. Perhaps BMPbis?
- Instrumentation of treat-as-withdraw. I think to do this right is =
harder than it sounds. I'll plan to cover this when I report at the WG =
meeting.

If you made a suggestion other than the exceptions listed above and =
don't see it reflected in the new draft, please let me know.

I'm hoping we will be able to WGLC this draft soonish, say by the =
Orlando meeting.

--John=


From rraszuk@gmail.com  Tue Oct 23 15:08:28 2012
Return-Path: <rraszuk@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 4CE431F0424 for <grow@ietfa.amsl.com>; Tue, 23 Oct 2012 15:08:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.879
X-Spam-Level: 
X-Spam-Status: No, score=-2.879 tagged_above=-999 required=5 tests=[AWL=0.098,  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 DA993SYzdThB for <grow@ietfa.amsl.com>; Tue, 23 Oct 2012 15:08:27 -0700 (PDT)
Received: from mail-ie0-f172.google.com (mail-ie0-f172.google.com [209.85.223.172]) by ietfa.amsl.com (Postfix) with ESMTP id C5D341F0C9A for <grow@ietf.org>; Tue, 23 Oct 2012 15:08:27 -0700 (PDT)
Received: by mail-ie0-f172.google.com with SMTP id 9so7086158iec.31 for <grow@ietf.org>; Tue, 23 Oct 2012 15:08:27 -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:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=Gl/pQ/jF80j/QjfBb2kIr19uDBTNFCsWa89LsSU0xQs=; b=QZRvOEuKd5ZFGFzmMEGwr6l65uV9o+Lf7J8pyCP/hBCQ6CXqCURixTd++2u/v8ZI+a 7zn3qw96+P3hImUG36FAJ/1FH83BhxEBMKdP+vQWUf9qZDAbb1qmZn1IQ1pB4sOtcEGD 6WxtNVj3VBj89nnqtM1z/GWYHArYUsLByB2+C4/8+kVaMhVu0mCjnatNfgix7kINU0O1 Ena0EvVAhsdv5He+IZAImWH/4lyH8i8J+CeeGtdXKlt2RLQh/4TJk2G0/9Y5wDs9svoz B6V6E/wTilcmlM55LnKzrxidIJMaS3tkNyY9v+YFZx2cQMxJKpGqcC+yUo4LyRwFLGD3 W8fQ==
MIME-Version: 1.0
Received: by 10.50.217.169 with SMTP id oz9mr642469igc.15.1351030107674; Tue, 23 Oct 2012 15:08:27 -0700 (PDT)
Sender: rraszuk@gmail.com
Received: by 10.42.68.133 with HTTP; Tue, 23 Oct 2012 15:08:27 -0700 (PDT)
In-Reply-To: <AF17822D-15BA-4841-A9D5-2C25F903DFCD@juniper.net>
References: <20121022210046.6626.51587.idtracker@ietfa.amsl.com> <CA+b+ERmVcCxcVi9bwYkQVoRMDQm9H-5WLYBROwdKX3xe5uR4wg@mail.gmail.com> <AF17822D-15BA-4841-A9D5-2C25F903DFCD@juniper.net>
Date: Wed, 24 Oct 2012 00:08:27 +0200
X-Google-Sender-Auth: 3nx0Gjz7Zrq4Kt-fj_Y7zUeuiY4
Message-ID: <CA+b+ERmk1HUst-x5OzONbKR916Z0Bk-AxumuKUtNW-gEowGtQA@mail.gmail.com>
From: Robert Raszuk <robert@raszuk.net>
To: "John G. Scudder" <jgs@juniper.net>
Content-Type: text/plain; charset=ISO-8859-1
Cc: tli@cisco.com, grow@ietf.org
Subject: Re: [GROW] I-D Action: draft-ietf-grow-bmp-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: Tue, 23 Oct 2012 22:08:28 -0000

Hi John,

Thank you for your perspective on this topic.

One thing to clarify ...

> Finally, as to your comment that "replay of Adj_RIB_In would miss all of
> those prefixes which were subject to drop due to BGP Origin Validation", I
> don't know why you think this. In our implementation, it isn't true.

Origin Validation is applied pre-inbound-policy - I think you agree with this.

Assume that during the origin validation prefix received from the peer
is found as INVALID and marked as such. Subsequent inbound policy is
configured by the operator to drop INVALID rather then just to
deprefer or not consider those in the best path.

I am afraid in the former policy configuration such prefix will never
go to Adj_RIB_In. In the latter case it will.

Are you saying that in your implementation you do not allow to drop
INVALID prefixes on EBGP inbound policy ?

Thx,
R.

From paaguti@gmail.com  Wed Oct 24 00:28:26 2012
Return-Path: <paaguti@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 2210E21F8472 for <grow@ietfa.amsl.com>; Wed, 24 Oct 2012 00:28:26 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UNvc-PTRQ1yJ for <grow@ietfa.amsl.com>; Wed, 24 Oct 2012 00:28:25 -0700 (PDT)
Received: from mail-da0-f44.google.com (mail-da0-f44.google.com [209.85.210.44]) by ietfa.amsl.com (Postfix) with ESMTP id 4AB9421F84A0 for <grow@ietf.org>; Wed, 24 Oct 2012 00:28:25 -0700 (PDT)
Received: by mail-da0-f44.google.com with SMTP id h15so126263dan.31 for <grow@ietf.org>; Wed, 24 Oct 2012 00:28:25 -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 :content-type; bh=2M5Uks/02n01HG0N6gVjalkGQyhxhmFYpgDztNkOFQo=; b=OzBuzkN+wHc/Q//60AHsai+bGnoaAtLudFcDfVLazoeyYN8XSRgIO2ATQ+cC47aOVy 8OcLtFOrwMRzV2YhVRkioIkycwS6xM0GS1su3MFOCz6YF67CYxCRe79quTDAy+bLuv9l PvpKfYAeO6wXZd1Lyv6AC/A4TgkxGfHrz8UZM2Q0A8I3y+wLBFUhKhOytsDFWFe2THiS 8Y4zBpMrKz0KB32XHlBIVKI6K94/stWsGxq8E4Gi0ilr94BE5UCw8gi9YLfLdHLo7JAB 7alsBq2lGsihA4WHl6JoQcX3Y6zU+9serqAYb0YRnysoJfbWddA8qkGgcucIaYiDlWPR W+2A==
MIME-Version: 1.0
Received: by 10.68.200.227 with SMTP id jv3mr47208873pbc.162.1351063705040; Wed, 24 Oct 2012 00:28:25 -0700 (PDT)
Received: by 10.66.228.4 with HTTP; Wed, 24 Oct 2012 00:28:24 -0700 (PDT)
In-Reply-To: <20121022210046.6626.51587.idtracker@ietfa.amsl.com>
References: <20121022210046.6626.51587.idtracker@ietfa.amsl.com>
Date: Wed, 24 Oct 2012 09:28:24 +0200
Message-ID: <CAO48Bk-17pp=kfnz9vk4BH5q_qxJhAAhTrD2d+GrhpyuUU3_Mw@mail.gmail.com>
From: Pedro Andres Aranda Gutierrez <paaguti@gmail.com>
To: grow@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [GROW] I-D Action: draft-ietf-grow-bmp-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, 24 Oct 2012 07:28:26 -0000

IMvHO, all this is quite conveniently covered by the MRT drafts. I get
snapshots of traffic as well as of routing tables without any
"screen-scraping approach"

Best,
/PA

On Mon, Oct 22, 2012 at 11:00 PM,  <internet-drafts@ietf.org> wrote:
>
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
>  This draft is a work item of the Global Routing Operations Working Group of the IETF.
>
>         Title           : BGP Monitoring Protocol
>         Author(s)       : John Scudder
>                           Rex Fernando
>                           Stephen Stuart
>         Filename        : draft-ietf-grow-bmp-07.txt
>         Pages           : 22
>         Date            : 2012-10-22
>
> Abstract:
>    This document defines a protocol, BMP, which can be used to monitor
>    BGP sessions.  BMP is intended to provide a more convenient interface
>    for obtaining route views for research purpose than the screen-
>    scraping approach in common use today.  The design goals are to keep
>    BMP simple, useful, easily implemented, and minimally service-
>    affecting.  BMP is not suitable for use as a routing protocol.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-grow-bmp
>
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-ietf-grow-bmp-07
>
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=draft-ietf-grow-bmp-07
>
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> _______________________________________________
> GROW mailing list
> GROW@ietf.org
> https://www.ietf.org/mailman/listinfo/grow

From pds@lugs.com  Wed Oct 24 02:13:31 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 BE40321F8B81 for <grow@ietfa.amsl.com>; Wed, 24 Oct 2012 02:13:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.949
X-Spam-Level: 
X-Spam-Status: No, score=-100.949 tagged_above=-999 required=5 tests=[AWL=-0.951, BAYES_50=0.001, HTML_MESSAGE=0.001, 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 pSO31yTYt9C7 for <grow@ietfa.amsl.com>; Wed, 24 Oct 2012 02:13:31 -0700 (PDT)
Received: from murdock.lugs.com (murdock.lugs.com [192.80.15.4]) by ietfa.amsl.com (Postfix) with ESMTP id 31D0721F8B75 for <grow@ietf.org>; Wed, 24 Oct 2012 02:13:26 -0700 (PDT)
Received: from r9m1fw1 (unknown [202.55.50.51]) by murdock.lugs.com (Postfix) with ESMTPSA id 6EAFBD3430 for <grow@ietf.org>; Wed, 24 Oct 2012 05:13:24 -0400 (EDT)
From: "Peter Schoenmaker" <pds@lugs.com>
To: <grow@ietf.org>
Date: Wed, 24 Oct 2012 17:13:20 +0800
Message-ID: <004701cdb1c7$d100a0e0$7301e2a0$@lugs.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0048_01CDB20A.DF276350"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac2xx2I0ildgFV34ScKO0dIrr6T3kA==
Content-Language: en-us
Subject: [GROW] Agenda for IETF 85
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, 24 Oct 2012 09:13:31 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0048_01CDB20A.DF276350
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hello,

 

I have posted the agenda for GROW.

 

GROW WG IETF 85 agenda  

Atlanta, GA

 

Administrivia                                      5 minutes

  o Blue sheets

  o Scribe/jabber

 

GROW Update                                  5 minutes

 

John Scudder                                     20 minutes

  o  draft-ietf-grow-bmp-07

 

Pierre Francois                  20 minutes

  o  draft-ietf-grow-bgp-gshut-04 update

 

Danny McPherson                                           15 minutes

  o  draft-mcpherson-irr-routing-policy-considerations-00

 

Peter

 

 


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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" =
xmlns:p=3D"urn:schemas-microsoft-com:office:powerpoint" =
xmlns:a=3D"urn:schemas-microsoft-com:office:access" =
xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" =
xmlns:s=3D"uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" =
xmlns:rs=3D"urn:schemas-microsoft-com:rowset" xmlns:z=3D"#RowsetSchema" =
xmlns:b=3D"urn:schemas-microsoft-com:office:publisher" =
xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadsheet" =
xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" =
xmlns:odc=3D"urn:schemas-microsoft-com:office:odc" =
xmlns:oa=3D"urn:schemas-microsoft-com:office:activation" =
xmlns:html=3D"http://www.w3.org/TR/REC-html40" =
xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/" =
xmlns:rtc=3D"http://microsoft.com/officenet/conferencing" =
xmlns:D=3D"DAV:" xmlns:Repl=3D"http://schemas.microsoft.com/repl/" =
xmlns:mt=3D"http://schemas.microsoft.com/sharepoint/soap/meetings/" =
xmlns:x2=3D"http://schemas.microsoft.com/office/excel/2003/xml" =
xmlns:ppda=3D"http://www.passport.com/NameSpace.xsd" =
xmlns:ois=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" =
xmlns:dir=3D"http://schemas.microsoft.com/sharepoint/soap/directory/" =
xmlns:ds=3D"http://www.w3.org/2000/09/xmldsig#" =
xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint/dsp" =
xmlns:udc=3D"http://schemas.microsoft.com/data/udc" =
xmlns:xsd=3D"http://www.w3.org/2001/XMLSchema" =
xmlns:sub=3D"http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/"=
 xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#" =
xmlns:sp=3D"http://schemas.microsoft.com/sharepoint/" =
xmlns:sps=3D"http://schemas.microsoft.com/sharepoint/soap/" =
xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-instance" =
xmlns:udcs=3D"http://schemas.microsoft.com/data/udc/soap" =
xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile" =
xmlns:udcp2p=3D"http://schemas.microsoft.com/data/udc/parttopart" =
xmlns:wf=3D"http://schemas.microsoft.com/sharepoint/soap/workflow/" =
xmlns:dsss=3D"http://schemas.microsoft.com/office/2006/digsig-setup" =
xmlns:dssi=3D"http://schemas.microsoft.com/office/2006/digsig" =
xmlns:mdssi=3D"http://schemas.openxmlformats.org/package/2006/digital-sig=
nature" =
xmlns:mver=3D"http://schemas.openxmlformats.org/markup-compatibility/2006=
" xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns:mrels=3D"http://schemas.openxmlformats.org/package/2006/relationshi=
ps" xmlns:spwp=3D"http://microsoft.com/sharepoint/webpartpages" =
xmlns:ex12t=3D"http://schemas.microsoft.com/exchange/services/2006/types"=
 =
xmlns:ex12m=3D"http://schemas.microsoft.com/exchange/services/2006/messag=
es" =
xmlns:pptsl=3D"http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/=
" =
xmlns:spsl=3D"http://microsoft.com/webservices/SharePointPortalServer/Pub=
lishedLinksService" xmlns:Z=3D"urn:schemas-microsoft-com:" =
xmlns:st=3D"&#1;" xmlns=3D"http://www.w3.org/TR/REC-html40"><head><META =
HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p =
class=3DMsoNormal>Hello,<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>I have =
posted the agenda for GROW.<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>GROW WG IETF =
85 agenda&nbsp; <o:p></o:p></p><p class=3DMsoNormal>Atlanta, =
GA<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>Administrivia&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 5 minutes<o:p></o:p></p><p =
class=3DMsoNormal>&nbsp; o Blue sheets<o:p></o:p></p><p =
class=3DMsoNormal>&nbsp; o Scribe/jabber<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>GROW =
Update&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 5 =
minutes<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>John =
Scudder&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp; 20 minutes<o:p></o:p></p><p class=3DMsoNormal>&nbsp; o&nbsp; =
draft-ietf-grow-bmp-07<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Pierre =
Francois =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp; 20 minutes<o:p></o:p></p><p =
class=3DMsoNormal>&nbsp; o&nbsp; draft-ietf-grow-bgp-gshut-04 =
update<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>Danny =
McPherson&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 15 minutes<o:p></o:p></p><p =
class=3DMsoNormal>&nbsp; o&nbsp; =
draft-mcpherson-irr-routing-policy-considerations-00<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>Peter<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_0048_01CDB20A.DF276350--


From wwwrun@rfc-editor.org  Wed Oct 24 15:52:02 2012
Return-Path: <wwwrun@rfc-editor.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 4C1DA11E808D; Wed, 24 Oct 2012 15:52:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.19
X-Spam-Level: 
X-Spam-Status: No, score=-102.19 tagged_above=-999 required=5 tests=[AWL=0.410, BAYES_00=-2.599, NO_RELAYS=-0.001, 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 odEGbwD52Ovw; Wed, 24 Oct 2012 15:52:00 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id 17DC71F0424; Wed, 24 Oct 2012 15:51:59 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 56ECF72E039; Wed, 24 Oct 2012 15:46:16 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20121024224616.56ECF72E039@rfc-editor.org>
Date: Wed, 24 Oct 2012 15:46:16 -0700 (PDT)
Cc: grow@ietf.org, rfc-editor@rfc-editor.org
Subject: [GROW] RFC 6769 on Simple Virtual Aggregation (S-VA)
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Oct 2012 22:52:02 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 6769

        Title:      Simple Virtual Aggregation (S-VA) 
        Author:     R. Raszuk, J. Heitz,
                    A. Lo, L. Zhang, X. Xu
        Status:     Informational
        Stream:     IETF
        Date:       October 2012
        Mailbox:    robert@raszuk.net, 
                    jakob.heitz@ericsson.com, 
                    altonlo@aristanetworks.com,
                    lixia@cs.ucla.edu, 
                    xuxh@huawei.com
        Pages:      8
        Characters: 16565
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-grow-simple-va-12.txt

        URL:        http://www.rfc-editor.org/rfc/rfc6769.txt

All BGP routers in the Default-Free Zone (DFZ) are required to carry
all routes in the Default-Free Routing Table (DFRT).  This document
describes a technique, Simple Virtual Aggregation (S-VA), that allows
some BGP routers not to install all of those routes into the 
Forwarding Information Base (FIB).

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

The VA prefixes that are announced within an AS are not announced to
any other AS.  The described functionality is of very low operational
complexity, as it proposes a confined BGP speaker solution without
any dependency on network-wide configuration or requirement for any
form of intra-domain tunneling.  This document is not an Internet Standards Track specification; it is published for informational 
purposes.

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


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC



From jgs@juniper.net  Thu Oct 25 12:12:26 2012
Return-Path: <jgs@juniper.net>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ED2EF21F86B1 for <grow@ietfa.amsl.com>; Thu, 25 Oct 2012 12:12:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.688
X-Spam-Level: 
X-Spam-Status: No, score=-3.688 tagged_above=-999 required=5 tests=[AWL=-0.221, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, UNRESOLVED_TEMPLATE=3.132]
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 GdH5QTymiyps for <grow@ietfa.amsl.com>; Thu, 25 Oct 2012 12:12:25 -0700 (PDT)
Received: from exprod7og108.obsmtp.com (exprod7og108.obsmtp.com [64.18.2.169]) by ietfa.amsl.com (Postfix) with ESMTP id 3E1A821F84EE for <grow@ietf.org>; Thu, 25 Oct 2012 12:12:25 -0700 (PDT)
Received: from P-EMHUB02-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob108.postini.com ([64.18.6.12]) with SMTP ID DSNKUImPGKdqHc8NaZlayvc+uJE2SvkGLLAr@postini.com; Thu, 25 Oct 2012 12:12:25 PDT
Received: from P-CLDFE01-HQ.jnpr.net (172.24.192.59) by P-EMHUB02-HQ.jnpr.net (172.24.192.36) with Microsoft SMTP Server (TLS) id 8.3.213.0; Thu, 25 Oct 2012 12:11:52 -0700
Received: from o365mail.juniper.net (207.17.137.224) by o365mail.juniper.net (172.24.192.59) with Microsoft SMTP Server id 14.1.355.2; Thu, 25 Oct 2012 12:11:52 -0700
Received: from db3outboundpool.messaging.microsoft.com (213.199.154.142) by o365mail.juniper.net (207.17.137.224) with Microsoft SMTP Server (TLS) id 14.1.355.2; Thu, 25 Oct 2012 12:18:03 -0700
Received: from mail51-db3-R.bigfish.com (10.3.81.235) by DB3EHSOBE005.bigfish.com (10.3.84.25) with Microsoft SMTP Server id 14.1.225.23; Thu, 25 Oct 2012 19:11:49 +0000
Received: from mail51-db3 (localhost [127.0.0.1])	by mail51-db3-R.bigfish.com (Postfix) with ESMTP id DFDC52E01A7	for <grow@ietf.org.FOPE.CONNECTOR.OVERRIDE>; Thu, 25 Oct 2012 19:11:48 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.240.101; KIP:(null); UIP:(null); (null); H:BL2PRD0510HT001.namprd05.prod.outlook.com; R:internal; EFV:INT
X-SpamScore: 0
X-BigFish: PS0(zz98dI9371I1432Izz1202h1d1ah1d2ah1082kzz8275chz2dh2a8h668h839hd25he5bhf0ah1288h12a5h12a9h12bdh137ah139eh13b6h1441h14ddh1504h1537h1155h)
Received: from mail51-db3 (localhost.localdomain [127.0.0.1]) by mail51-db3 (MessageSwitch) id 1351192306906249_15469; Thu, 25 Oct 2012 19:11:46 +0000 (UTC)
Received: from DB3EHSMHS011.bigfish.com (unknown [10.3.81.230])	by mail51-db3.bigfish.com (Postfix) with ESMTP id D0FE6180058; Thu, 25 Oct 2012 19:11:46 +0000 (UTC)
Received: from BL2PRD0510HT001.namprd05.prod.outlook.com (157.56.240.101) by DB3EHSMHS011.bigfish.com (10.3.87.111) with Microsoft SMTP Server (TLS) id 14.1.225.23; Thu, 25 Oct 2012 19:11:46 +0000
Received: from ntatavossian-sslvpn-nc.jnpr.net (66.129.224.53) by pod51010.outlook.com (10.255.100.36) with Microsoft SMTP Server (TLS) id 14.16.224.5; Thu, 25 Oct 2012 19:11:42 +0000
Content-Type: text/plain; charset="iso-8859-1"
MIME-Version: 1.0 (Mac OS X Mail 6.1 \(1498\))
From: "John G. Scudder" <jgs@juniper.net>
In-Reply-To: <CA+b+ERmk1HUst-x5OzONbKR916Z0Bk-AxumuKUtNW-gEowGtQA@mail.gmail.com>
Date: Thu, 25 Oct 2012 15:11:37 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <A203AD75-B9CD-4E1E-9DD5-CFF450BB6682@juniper.net>
References: <20121022210046.6626.51587.idtracker@ietfa.amsl.com> <CA+b+ERmVcCxcVi9bwYkQVoRMDQm9H-5WLYBROwdKX3xe5uR4wg@mail.gmail.com> <AF17822D-15BA-4841-A9D5-2C25F903DFCD@juniper.net> <CA+b+ERmk1HUst-x5OzONbKR916Z0Bk-AxumuKUtNW-gEowGtQA@mail.gmail.com>
To: Robert Raszuk <robert@raszuk.net>
X-Mailer: Apple Mail (2.1498)
X-Originating-IP: [66.129.224.53]
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
X-FOPE-CONNECTOR: Id%12219$Dn%CISCO.COM$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net
X-FOPE-CONNECTOR: Id%12219$Dn%IETF.ORG$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net
X-FOPE-CONNECTOR: Id%12219$Dn%RASZUK.NET$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net
Cc: tli@cisco.com, grow@ietf.org
Subject: Re: [GROW] I-D Action: draft-ietf-grow-bmp-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, 25 Oct 2012 19:12:26 -0000

On Oct 23, 2012, at 6:08 PM, Robert Raszuk <robert@raszuk.net> wrote:
> One thing to clarify ...
>=20
>> Finally, as to your comment that "replay of Adj_RIB_In would miss all =
of
>> those prefixes which were subject to drop due to BGP Origin =
Validation", I
>> don't know why you think this. In our implementation, it isn't true.
>=20
> Origin Validation is applied pre-inbound-policy - I think you agree =
with this.
>=20
> Assume that during the origin validation prefix received from the peer
> is found as INVALID and marked as such. Subsequent inbound policy is
> configured by the operator to drop INVALID rather then just to
> deprefer or not consider those in the best path.
>=20
> I am afraid in the former policy configuration such prefix will never
> go to Adj_RIB_In. In the latter case it will.
>=20
> Are you saying that in your implementation you do not allow to drop
> INVALID prefixes on EBGP inbound policy ?

No, you can filter them out just like any other route. I'm saying that =
in our implementation, by default we retain filtered routes in our =
Adj-RIB-In but don't allow them to be selected for inclusion in the =
Loc-RIB.

Also, if an implementation doesn't do this, it's a general issue and not =
specific to Origin Validation. The BMP draft does talk about this issue =
a little bit.

--John=

