
From christopher.morrow@gmail.com  Fri Jun  1 10:36:42 2012
Return-Path: <christopher.morrow@gmail.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1AB1111E808A for <grow@ietfa.amsl.com>; Fri,  1 Jun 2012 10:36:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R3r6DQUPOtn4 for <grow@ietfa.amsl.com>; Fri,  1 Jun 2012 10:36:41 -0700 (PDT)
Received: from mail-gg0-f172.google.com (mail-gg0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id 67F6611E8074 for <grow@ietf.org>; Fri,  1 Jun 2012 10:36:41 -0700 (PDT)
Received: by ggnc4 with SMTP id c4so2211316ggn.31 for <grow@ietf.org>; Fri, 01 Jun 2012 10:36:41 -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:content-transfer-encoding; bh=BM8cCS2/vBGEUEJlMqHJI2dqQDiTHtYWRsv6r36/ln4=; b=F6IsAUZg/D+W9QRvvonHePwugScIsrP2LlbpnVEGnJrNsQu/yYZrm8eEinNqfvWwIW LRRZl8y8cbahLxIWOecQH5V6XLYdvWB6TEOp5O49YKCErJE2NNXvZhKUlKW0ADT3wg2z LElBJP/8qpUYfk9TTS9aAAiuqOmFIp1Z08RTK0ADk/UA9oVbc/Ut0rDbXSzEW58cyzIP j8oK4l+wi3TyL9XPxK7mFcQElni3r2sEIShwAweZgipb3AGoHcfgiksy5zZxFO2iC6UJ LwS7Ryw5Ep/SK/vSE4P8ltkIKIZpmVF6oVBcmhnSAVBIK3KRX+SH9NBTGQ6j/3IUomlT o6rQ==
MIME-Version: 1.0
Received: by 10.60.3.202 with SMTP id e10mr3507921oee.52.1338572200928; Fri, 01 Jun 2012 10:36:40 -0700 (PDT)
Received: by 10.182.166.71 with HTTP; Fri, 1 Jun 2012 10:36:40 -0700 (PDT)
In-Reply-To: <CAL9jLaZd_PUN3Y+Uj+n5roDfXoD_Raw1bn+QpcYQ++6452fppg@mail.gmail.com>
References: <CAL9jLaZd_PUN3Y+Uj+n5roDfXoD_Raw1bn+QpcYQ++6452fppg@mail.gmail.com>
Date: Fri, 1 Jun 2012 13:36:40 -0400
Message-ID: <CAL9jLaacDRLP1_u=sTuYD+DQO2YdK_sLhUwWOe53sA5AYO0Mfw@mail.gmail.com>
From: Christopher Morrow <christopher.morrow@gmail.com>
To: grow-chairs@tools.ietf.org, grow-ads@tools.ietf.org,  "grow@ietf.org grow@ietf.org" <grow@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [GROW] WGLC: draft-ietf-grow-simple-va
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Jun 2012 17:36:42 -0000

a belated (by 3 days-ish) note that this seems to have gotten some
more review/update/help and votes for passage on to the iesg for
publication (note the ietf-announce list note of same).

thanks!
-chris

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

From ietfc@btconnect.com  Fri Jun  1 11:17:07 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 2ED9521F897C for <grow@ietfa.amsl.com>; Fri,  1 Jun 2012 11:17:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.901
X-Spam-Level: 
X-Spam-Status: No, score=-4.901 tagged_above=-999 required=5 tests=[AWL=1.654,  BAYES_00=-2.599, DATE_IN_PAST_03_06=0.044, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6KwurmVeoMJt for <grow@ietfa.amsl.com>; Fri,  1 Jun 2012 11:17:06 -0700 (PDT)
Received: from tx2outboundpool.messaging.microsoft.com (tx2ehsobe004.messaging.microsoft.com [65.55.88.14]) by ietfa.amsl.com (Postfix) with ESMTP id 2426821F8979 for <grow@ietf.org>; Fri,  1 Jun 2012 11:17:05 -0700 (PDT)
Received: from mail47-tx2-R.bigfish.com (10.9.14.252) by TX2EHSOBE002.bigfish.com (10.9.40.22) with Microsoft SMTP Server id 14.1.225.23; Fri, 1 Jun 2012 18:16:34 +0000
Received: from mail47-tx2 (localhost [127.0.0.1])	by mail47-tx2-R.bigfish.com (Postfix) with ESMTP id D6FB92A0453; Fri,  1 Jun 2012 18:16:33 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.55.224.141; KIP:(null); UIP:(null); IPV:NLI; H:DB3PRD0702HT003.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -40
X-BigFish: PS-40(zz9371I936eK542M1432N98dK11f6Nzz1202hzz8275ch1033IL8275dhz2dh2a8h5a9h668h839hd24hf0ah304l)
Received: from mail47-tx2 (localhost.localdomain [127.0.0.1]) by mail47-tx2 (MessageSwitch) id 1338574592429596_7580; Fri,  1 Jun 2012 18:16:32 +0000 (UTC)
Received: from TX2EHSMHS034.bigfish.com (unknown [10.9.14.241])	by mail47-tx2.bigfish.com (Postfix) with ESMTP id 5D029A0288; Fri,  1 Jun 2012 18:16:32 +0000 (UTC)
Received: from DB3PRD0702HT003.eurprd07.prod.outlook.com (157.55.224.141) by TX2EHSMHS034.bigfish.com (10.9.99.134) with Microsoft SMTP Server (TLS) id 14.1.225.23; Fri, 1 Jun 2012 18:16:31 +0000
Received: from BY2PRD0610HT001.namprd06.prod.outlook.com (157.56.236.117) by pod51017.outlook.com (10.3.4.151) with Microsoft SMTP Server (TLS) id 14.15.74.2; Fri, 1 Jun 2012 18:16:42 +0000
Message-ID: <035701cd4022$47b4a820$4001a8c0@gateway.2wire.net>
From: t.petch <ietfc@btconnect.com>
To: <robert@raszuk.net>, SM <sm@resistor.net>
References: <20120529160722.12364.75583.idtracker@ietfa.amsl.com><6.2.5.6.2.20120531150923.098e3200@resistor.net> <4FC7F51F.3090309@raszuk.net>
Date: Fri, 1 Jun 2012 14:14:30 +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.236.117]
X-OriginatorOrg: btconnect.com
Cc: grow@ietf.org, draft-ietf-grow-simple-va.all@tools.ietf.org
Subject: Re: [GROW] Last Call: <draft-ietf-grow-simple-va-08.txt> (Simple Virtual Aggregation (S-VA)) to Informational RFC
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
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, 01 Jun 2012 18:17:07 -0000

----- Original Message -----
From: "Robert Raszuk" <robert@raszuk.net>
To: "SM" <sm@resistor.net>
Cc: <grow@ietf.org>; <draft-ietf-grow-simple-va.all@tools.ietf.org>
Sent: Thursday, May 31, 2012 11:47 PM
> Hi SM,
>
> Very good catch ... repurposing APNIC IPv4 address space was not
> intended. Simply the address space in the example was chosen
completely
> randomly.
>
> I will remove that text from the final version of the document.

Or try
5737 IPv4 Address Blocks Reserved for Documentation.
Tom Petch

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



From sm@resistor.net  Fri Jun  1 12:39:07 2012
Return-Path: <sm@resistor.net>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D566A11E813D for <grow@ietfa.amsl.com>; Fri,  1 Jun 2012 12:39:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.199
X-Spam-Level: 
X-Spam-Status: No, score=-102.199 tagged_above=-999 required=5 tests=[AWL=-0.200, BAYES_00=-2.599, J_CHICKENPOX_15=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UnI-lw0qtBbU for <grow@ietfa.amsl.com>; Fri,  1 Jun 2012 12:39:06 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 71B5511E808A for <grow@ietf.org>; Fri,  1 Jun 2012 12:39:06 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q51JctsA014704; Fri, 1 Jun 2012 12:39:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1338579544; i=@resistor.net; bh=pou+FCTuRghyV6Uu794WlsHtmBjiVPV5gWwJWvxbJ3g=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=SMIlgU3xhuNmRACHS8ZzNyTxpppc/CQrffs8N4tgvjVo9eTEgjIAznQpvichpSXv+ pc041/XPQ8qPp+kn50eXXMXa75y9PZpZsEOlO7v75CR5VBe2rxpkM2FZ+9fi+FCqOG ydETLeGJA8RrA8WZAZ5p53eVldN0PlH0zpDoWbek=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1338579544; i=@resistor.net; bh=pou+FCTuRghyV6Uu794WlsHtmBjiVPV5gWwJWvxbJ3g=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=QPDH5cpzk6CEwC3xzSy3M+lGbfUlJ5erY+VE6vt3spvxVl4V45+5yXo7W+7pKwglv g3/BawGUwUUyi65BLX3r3+kZdiSb7pup1H4fFDjIeJgBkxoYUIToNxo12DMNVlNPN7 6Zhtv9WNaBB/S00d1AszR9Dg2YgTeeLK61Y5pAaI=
Message-Id: <6.2.5.6.2.20120601123140.09d0e280@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 01 Jun 2012 12:35:33 -0700
To: "t.petch" <ietfc@btconnect.com>, robert@raszuk.net
From: SM <sm@resistor.net>
In-Reply-To: <035701cd4022$47b4a820$4001a8c0@gateway.2wire.net>
References: <20120529160722.12364.75583.idtracker@ietfa.amsl.com> <6.2.5.6.2.20120531150923.098e3200@resistor.net> <4FC7F51F.3090309@raszuk.net> <035701cd4022$47b4a820$4001a8c0@gateway.2wire.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Mailman-Approved-At: Fri, 01 Jun 2012 14:18:23 -0700
Cc: grow@ietf.org, draft-ietf-grow-simple-va.all@tools.ietf.org
Subject: Re: [GROW] Last Call: <draft-ietf-grow-simple-va-08.txt> (Simple Virtual Aggregation (S-VA)) to Informational RFC
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
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, 01 Jun 2012 19:39:08 -0000

Hi Tom,
At 06:14 01-06-2012, t.petch wrote:
>Or try
>5737 IPv4 Address Blocks Reserved for Documentation.
>Tom Petch

The problem is that there are only /24s in the reserved list.  An 
alternative is to use a /24 and a /25 for the examples.

Regards,
-sm 


From warren@kumari.net  Sat Jun  2 13:43:52 2012
Return-Path: <warren@kumari.net>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E01C621F859E; Sat,  2 Jun 2012 13:43:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.999
X-Spam-Level: 
X-Spam-Status: No, score=-105.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_15=0.6, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Up-XVey0F2fk; Sat,  2 Jun 2012 13:43:52 -0700 (PDT)
Received: from vimes.kumari.net (vimes.kumari.net [198.186.192.250]) by ietfa.amsl.com (Postfix) with ESMTP id 1CB6721F8599; Sat,  2 Jun 2012 13:43:51 -0700 (PDT)
Received: from [192.168.100.40] (unknown [207.34.158.233]) by vimes.kumari.net (Postfix) with ESMTPSA id C6FD41B40819; Sat,  2 Jun 2012 16:43:50 -0400 (EDT)
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=windows-1252
From: Warren Kumari <warren@kumari.net>
X-Priority: 3
In-Reply-To: <016b01cd37fc$9e125420$4001a8c0@gateway.2wire.net>
Date: Sat, 2 Jun 2012 16:43:42 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <F64DCE8D-8683-4437-945F-580887FB9A66@kumari.net>
References: <13205C286662DE4387D9AF3AC30EF456D76BA8836D@EMBX01-WF.jnpr.net> <016b01cd37fc$9e125420$4001a8c0@gateway.2wire.net>
To: t.petch <ietfc@btconnect.com>
X-Mailer: Apple Mail (2.1278)
Cc: grow@ietf.org, Warren Kumari <warren@kumari.net>, opsec@ietf.org
Subject: Re: [GROW] [OPSEC]  draft-ietf-grow-private-ip-sp-cores
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 02 Jun 2012 20:43:53 -0000

--=20
A. No
Q. Is it sensible to top-post?


On May 22, 2012, at 5:23 AM, t.petch wrote:

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

Ok, so I guess the obvious question here is -- *why* is this not in the =
Ed queue (and please don't say "Because WGLC / LC hasn't happened yet, =
dummy" :-)).

I spent a little time going back through the archives, but suspect I'm =
missing something / somethings (note: I have not read the meeting =
minutes yet)=85

There seems to be very little discussion regarding this / these, but the =
general impression I got was that the WG likes this draft and would like =
a: it to subsume -beringer- or b: to simply get published. It was =
unclear to me how many folk had read / supported the draft, but...

I suspect that I'm missing some context / some off list discussions=85=20=


Is this just a "someone needs to wave the WGLC wand" situation?

W

>=20
> It is a natural companion to RFC6598 and could have, should have, been
> in the queue at the same time.  This I-D was relevant when it was =
first
> written 2 years ago, and I see its relevance decreasing with time, as
> people stumble over the mistakes that this I-D could have prevented.  =
It
> has taken those 2 years to get this I-D IETF-ready, little has changed
> in the content in that time, and it is time we got it out of the door.
>=20
> Of course there is scope for improvement, there always is, but that is
> an argument for never publishing anything.  If the authors of the =
other
> I-Ds want to build on it, then of course they can produce a bis that
> covers more, but let's publish what we have got.
>=20
> Tom Petch
>=20
>>=20
>> For the purpose of discussing these three documents, I think that a
> little cross-posting is acceptable.
>>=20
>> --------------------------
>> Ron Bonica
>> vcard:       www.bonica.org/ron/ronbonica.vcf
>>=20
>>=20
>> _______________________________________________
>> GROW mailing list
>> GROW@ietf.org
>> https://www.ietf.org/mailman/listinfo/grow
>>=20
>=20
>=20
> _______________________________________________
> OPSEC mailing list
> OPSEC@ietf.org
> https://www.ietf.org/mailman/listinfo/opsec
>=20


From internet-drafts@ietf.org  Tue Jun  5 05:40:48 2012
Return-Path: <internet-drafts@ietf.org>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D81121F8663; Tue,  5 Jun 2012 05:40:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.55
X-Spam-Level: 
X-Spam-Status: No, score=-102.55 tagged_above=-999 required=5 tests=[AWL=0.049, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AR8fwZgRFNqV; Tue,  5 Jun 2012 05:40:47 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 84C8521F85D6; Tue,  5 Jun 2012 05:40:47 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.02
Message-ID: <20120605124047.1450.26889.idtracker@ietfa.amsl.com>
Date: Tue, 05 Jun 2012 05:40:47 -0700
Cc: grow@ietf.org
Subject: [GROW] I-D Action: draft-ietf-grow-simple-va-09.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, 05 Jun 2012 12:40:48 -0000

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

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

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

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

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


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

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

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

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


From robert@raszuk.net  Tue Jun  5 06:47:42 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 005A221F86A3 for <grow@ietfa.amsl.com>; Tue,  5 Jun 2012 06:47:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id B24V1nfJN+ts for <grow@ietfa.amsl.com>; Tue,  5 Jun 2012 06:47:41 -0700 (PDT)
Received: from mail1310.opentransfer.com (mail1310.opentransfer.com [76.162.254.103]) by ietfa.amsl.com (Postfix) with ESMTP id 2C50A21F8683 for <grow@ietf.org>; Tue,  5 Jun 2012 06:47:41 -0700 (PDT)
Received: (qmail 20423 invoked by uid 399); 5 Jun 2012 13:47:40 -0000
Received: from unknown (HELO ?45.0.254.46?) (pbs:robert@raszuk.net@45.0.254.46) by mail1310.opentransfer.com with ESMTPM; 5 Jun 2012 13:47:40 -0000
X-Originating-IP: 45.0.254.46
Message-ID: <4FCE0DFA.5000808@raszuk.net>
Date: Tue, 05 Jun 2012 06:47:38 -0700
From: Robert Raszuk <robert@raszuk.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: Bert Wijnen <bwijnen@ripe.net>
References: <4FCE0970.4070700@ripe.net>
In-Reply-To: <4FCE0970.4070700@ripe.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: grow@ietf.org, ops-ads@tools.ietf.org, ops-dir@ietf.org, draft-ietf-grow-simple-va@tools.ietf.org
Subject: Re: [GROW] OPS-DIR review of draft-ietf-grow-simple-va-06.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: robert@raszuk.net
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Jun 2012 13:47:42 -0000

Hello Bert,

> Hi, I was asked OPS-DIR review for draft-ietf-grow-simple-va-06.txt.

Great !

> At
> http://datatracker.ietf.org/doc/draft-ietf-grow-simple-va/?include_text=1
> I found revision 08, which is the one I reviewed yesterday.
>
> Then today I found draft-ietf-grow-simple-va-09.txt, so quickly skimmed
> through that as well. It fixed/removed the usage of example IP addresses
> that were not allowed according to RFC3330. Also, Acronyms have been
> expanded. So rev 9 is better than rev 8.

Yes I have just posted ver -09 to incorporate latest comments from few 
GROW reviewers.

> It seems to me that all the operational (deployment) aspects are described
> in this document. At least all the ones I could see.
>
> The document does not mention any "network management" specifics.
> I guess that means there are no simple-va specific management

True. The implementation we have tested in the field from one major 
router vendor was fully automated.

> I am somewhat wondering if RFC2119 language is needed.
> I find one case where MUST is used (top para on page 7).
> I wonder if you indeed want to use MUST, if the following "should"
> and "may" in that case better be SHOULD and MAY.
> But all in all, I would think that for informational all lowercase
> must/should/may would be fine. I am not hung up on it though.

I am happy to adjust the above accordingly (or remove ref to 2119) if 
you seem fit. Please advise on or off line and I will change it. Or we 
could always let RFC editor do those edits :)

Best regards and thank you very much for the review,
R.


> Bert Wijnen
> p.s. I am NOT on the grow mailing list.
>
>
>
>


From bwijnen@ripe.net  Tue Jun  5 06:28:22 2012
Return-Path: <bwijnen@ripe.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 06F4621F86AF; Tue,  5 Jun 2012 06:28:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S1KeQ5CMTRDM; Tue,  5 Jun 2012 06:28:21 -0700 (PDT)
Received: from postlady.ripe.net (postlady.ipv6.ripe.net [IPv6:2001:67c:2e8:11::c100:1341]) by ietfa.amsl.com (Postfix) with ESMTP id 3F03A21F8683; Tue,  5 Jun 2012 06:28:21 -0700 (PDT)
Received: from dodo.ripe.net ([193.0.23.4]) by postlady.ripe.net with esmtps (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from <bwijnen@ripe.net>) id 1Sbto1-0007yH-Gc; Tue, 05 Jun 2012 15:28:19 +0200
Received: from dog.ripe.net ([193.0.1.217] helo=BWMACBOOK.local) by dodo.ripe.net with esmtp (Exim 4.72) (envelope-from <bwijnen@ripe.net>) id 1Sbto0-000188-Tu; Tue, 05 Jun 2012 15:28:17 +0200
Message-ID: <4FCE0970.4070700@ripe.net>
Date: Tue, 05 Jun 2012 15:28:16 +0200
From: Bert Wijnen <bwijnen@ripe.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: draft-ietf-grow-simple-va@tools.ietf.org, ops-ads@tools.ietf.org,  grow@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Anti-Virus: Kaspersky Anti-Virus for Linux Mail Server 5.6.48/RELEASE, bases: 20120425 #7816066, check: 20120605 clean
X-RIPE-Spam-Level: --
X-RIPE-Spam-Report: Spam Total Points:   -2.9 points pts rule name              description ---- ---------------------- ------------------------------------ -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP -0.0 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay domain -1.9 BAYES_00               BODY: Bayes spam probability is 0 to 1% [score: 0.0000]
X-RIPE-Signature: 5ef2bffdfa2294c21c35da1b4f77885ef231e887825072955eb51b18c71804c4
X-Mailman-Approved-At: Tue, 05 Jun 2012 11:07:23 -0700
Cc: ops-dir@ietf.org
Subject: [GROW] OPS-DIR review of draft-ietf-grow-simple-va-06.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Jun 2012 13:28:22 -0000

Hi, I was asked OPS-DIR review for draft-ietf-grow-simple-va-06.txt.

At http://datatracker.ietf.org/doc/draft-ietf-grow-simple-va/?include_text=1
I found revision 08, which is the one I reviewed yesterday.

Then today I found draft-ietf-grow-simple-va-09.txt, so quickly skimmed
through that as well. It fixed/removed the usage of example IP addresses
that were not allowed according to RFC3330. Also, Acronyms have been
expanded. So rev 9 is better than rev 8.

It seems to me that all the operational (deployment) aspects are described
in this document. At least all the ones I could see.

The document does not mention any "network management" specifics.
I guess that means there are no simple-va specific management aspects.

I am somewhat wondering if RFC2119 language is needed.
I find one case where MUST is used (top para on page 7).
I wonder if you indeed want to use MUST, if the following "should"
and "may" in that case better be SHOULD and MAY.
But all in all, I would think that for informational all lowercase
must/should/may would be fine. I am not hung up on it though.

Bert Wijnen
p.s. I am NOT on the grow mailing list.



From christopher.morrow@gmail.com  Tue Jun  5 11:09:44 2012
Return-Path: <christopher.morrow@gmail.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 00A1F21F87C0; Tue,  5 Jun 2012 11:09:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O8GcYFx+IGnd; Tue,  5 Jun 2012 11:09:43 -0700 (PDT)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id 4CEB621F87B2; Tue,  5 Jun 2012 11:09:43 -0700 (PDT)
Received: by yhq56 with SMTP id 56so4648683yhq.31 for <multiple recipients>; Tue, 05 Jun 2012 11:09:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=trwMPAo/i+3S4YYKwRgdeVgyOKWIGzH1j1aNnpzyETs=; b=oazRPZXdtHlglvB66VyH+8nZBgnJPrjpNBJKLmK7bMbltqY76EvV//43pDwV1/dTGK CXh2g5N+jKmA7gdXl5ugT5S02qwdRVUawsMgc0pfyVJMIcnqZ/KeKgF6bTTwXZv2CCR4 H8k+4JkEo8Su5XVPRvuhGunPw6Au8CKZnEUPFn5FTHj0MhWIm/QiNA8DntT8hshkNjwC nujetaH7Zqlf9kiTGhwGZpnAY+xXjqTUvyv6ZQ+W338I2TeAXpG9w4GnIrdzYzvCQzlp aMgntkcyKRDX8zXVTSXSUx0iXKuRSEeSLVfi4gG1Qcp1zIV50mncGNModd94D91rHvVM dNEQ==
MIME-Version: 1.0
Received: by 10.60.24.7 with SMTP id q7mr17515722oef.50.1338919782596; Tue, 05 Jun 2012 11:09:42 -0700 (PDT)
Received: by 10.182.166.71 with HTTP; Tue, 5 Jun 2012 11:09:42 -0700 (PDT)
In-Reply-To: <F64DCE8D-8683-4437-945F-580887FB9A66@kumari.net>
References: <13205C286662DE4387D9AF3AC30EF456D76BA8836D@EMBX01-WF.jnpr.net> <016b01cd37fc$9e125420$4001a8c0@gateway.2wire.net> <F64DCE8D-8683-4437-945F-580887FB9A66@kumari.net>
Date: Tue, 5 Jun 2012 14:09:42 -0400
Message-ID: <CAL9jLab9GR_mbAZqQ8uOzY8OKuCS+dXfi3PQ1_kgpxGP_e2bJg@mail.gmail.com>
From: Christopher Morrow <christopher.morrow@gmail.com>
To: Warren Kumari <warren@kumari.net>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Cc: grow@ietf.org, opsec@ietf.org
Subject: Re: [GROW] [OPSEC] draft-ietf-grow-private-ip-sp-cores
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Jun 2012 18:09:44 -0000

On Sat, Jun 2, 2012 at 4:43 PM, Warren Kumari <warren@kumari.net> wrote:
>
> I suspect that I'm missing some context / some off list discussions=85
>
> Is this just a "someone needs to wave the WGLC wand" situation?

I believe my calendar failed me :( I think the WGLC finished with
people's issues covered.
let me go find the original thread and kick the can down the street.

From christopher.morrow@gmail.com  Tue Jun  5 11:12:36 2012
Return-Path: <christopher.morrow@gmail.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A595321F8735; Tue,  5 Jun 2012 11:12:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kJFRK4z+0chU; Tue,  5 Jun 2012 11:12:36 -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 12ADF21F8734; Tue,  5 Jun 2012 11:12:36 -0700 (PDT)
Received: by obbeh20 with SMTP id eh20so774862obb.31 for <multiple recipients>; Tue, 05 Jun 2012 11:12:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=xVrymNq7RojGToynS9fk5S78V3Uip29HElTnGukJCjc=; b=VqWtccci6cXfbEQTbfiiNkQcr3oepD3ZnX7AB0/E10ZQTUbrY0zRs+EUYeCGmwndLL LtDnERnQky1BYK+V45wSMyYNG2FEW99Yl+X+SJN8LzYxLq1YLiaq/dFTZRtYDdJ1HePV KubLqxVF0umvUKBEME9NeiTD+Eef560zbP6PNcig4s9wxZTkheXvgt7H12CjF+du1vBK MHXD25EfBwIxLKswDw2R4tf8fcyIXTkyZiE/J8FaOwsP3h56L1mSpGT2EiipUhUwWN06 m+uRN4HLo9xpHKd5eMDLRogESO1DM0YtBZrc2I3knjJDeXK84kyjYqUfm8q0rXIwP0t7 iFLQ==
MIME-Version: 1.0
Received: by 10.182.111.39 with SMTP id if7mr17439312obb.55.1338919955620; Tue, 05 Jun 2012 11:12:35 -0700 (PDT)
Received: by 10.182.166.71 with HTTP; Tue, 5 Jun 2012 11:12:35 -0700 (PDT)
In-Reply-To: <CAL9jLab9GR_mbAZqQ8uOzY8OKuCS+dXfi3PQ1_kgpxGP_e2bJg@mail.gmail.com>
References: <13205C286662DE4387D9AF3AC30EF456D76BA8836D@EMBX01-WF.jnpr.net> <016b01cd37fc$9e125420$4001a8c0@gateway.2wire.net> <F64DCE8D-8683-4437-945F-580887FB9A66@kumari.net> <CAL9jLab9GR_mbAZqQ8uOzY8OKuCS+dXfi3PQ1_kgpxGP_e2bJg@mail.gmail.com>
Date: Tue, 5 Jun 2012 14:12:35 -0400
Message-ID: <CAL9jLaYGZMbc9S+p2in6x08kDPNtpQRPmBtw+jxtV_GPQVV2ew@mail.gmail.com>
From: Christopher Morrow <christopher.morrow@gmail.com>
To: Warren Kumari <warren@kumari.net>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Cc: grow@ietf.org, opsec@ietf.org
Subject: Re: [GROW] [OPSEC] draft-ietf-grow-private-ip-sp-cores
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Jun 2012 18:12:36 -0000

On Tue, Jun 5, 2012 at 2:09 PM, Christopher Morrow
<christopher.morrow@gmail.com> wrote:
> On Sat, Jun 2, 2012 at 4:43 PM, Warren Kumari <warren@kumari.net> wrote:
>>
>> I suspect that I'm missing some context / some off list discussions=85
>>
>> Is this just a "someone needs to wave the WGLC wand" situation?
>
> I believe my calendar failed me :( I think the WGLC finished with
> people's issues covered.

oh, my calendar didn't fail me :( scheduling WGLC did.

> let me go find the original thread and kick the can down the street.

From christopher.morrow@gmail.com  Tue Jun  5 11:41:41 2012
Return-Path: <christopher.morrow@gmail.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 36A3621F86F9 for <grow@ietfa.amsl.com>; Tue,  5 Jun 2012 11:41:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Qv-57Zza2UHn for <grow@ietfa.amsl.com>; Tue,  5 Jun 2012 11:41:40 -0700 (PDT)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id 47A0B21F86BD for <grow@ietf.org>; Tue,  5 Jun 2012 11:41:40 -0700 (PDT)
Received: by yhq56 with SMTP id 56so4681757yhq.31 for <grow@ietf.org>; Tue, 05 Jun 2012 11:41:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=cvGTQJk1gW1Vg/JxI1SBSPOg2mZO9d4LIJEKFMlZWdU=; b=PrDG/TiZPfKGp03UqMkkrYatBp9p2VuFvmRScDBCjcJQr8IinefzEjO/9G4xsWyKpz KzwCTbyyIUVApzOrQxIbu1kMcFRZ0ug+27Js1GBzgHsIDsSurvFWG9p5qbD+JFR7esgM e8CO+NmuKZLgNpfCN9Ex63jLAJ8sPIlr9HHgQJWSGuCuXsUrx1oS11Zy45MPQDS/sOrI pfoLooL43W9Yfvpt3ASGL7K+DMRA7U85M74bY7Q5KDgZe8mW/8IoKdPmbJWmNpgR91SM t9ATposj4ScdiTWbiLfSPt3ml1L3hg2n4DK/6quoVuwuQyngjOdcKk88iNW0M5nF2am7 B2AQ==
MIME-Version: 1.0
Received: by 10.60.3.202 with SMTP id e10mr17702925oee.52.1338921699578; Tue, 05 Jun 2012 11:41:39 -0700 (PDT)
Received: by 10.182.166.71 with HTTP; Tue, 5 Jun 2012 11:41:39 -0700 (PDT)
Date: Tue, 5 Jun 2012 14:41:39 -0400
Message-ID: <CAL9jLabADdWCwDhBdaBJ4fVdk9a=OeJQYFQM4Z_+-P56cVWftw@mail.gmail.com>
From: Christopher Morrow <christopher.morrow@gmail.com>
To: grow-chairs@tools.ietf.org, "grow@ietf.org grow@ietf.org" <grow@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Subject: [GROW] WGLC: draft-ietf-grow-private-ip-sp-cores
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Jun 2012 18:41:41 -0000

Folks,
There's been work on the draft:
   <http://tools.ietf.org/html/draft-ietf-grow-private-ip-sp-cores>

I think the commenters' comments were addressed by the authors.
Can we move this to WGLC now and clear that 6/19/2012 (June 19, 2012).

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

Could there be some discussion on WGLC and  we'll see about  moving
this along to the IESG?

-chris

From internet-drafts@ietf.org  Wed Jun  6 08:04:59 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 E118A21F8622; Wed,  6 Jun 2012 08:04:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.407
X-Spam-Level: 
X-Spam-Status: No, score=-102.407 tagged_above=-999 required=5 tests=[AWL=-0.035, BAYES_00=-2.599, SARE_SUB_OBFU_Q1=0.227, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qSJwrxHMT2qw; Wed,  6 Jun 2012 08:04:59 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7351921F853D; Wed,  6 Jun 2012 08:04:59 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.02
Message-ID: <20120606150459.28821.4886.idtracker@ietfa.amsl.com>
Date: Wed, 06 Jun 2012 08:04:59 -0700
Cc: grow@ietf.org
Subject: [GROW] I-D Action: draft-ietf-grow-ops-reqs-for-bgp-error-handling-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: Wed, 06 Jun 2012 15:05:00 -0000

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

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

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

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


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-grow-ops-reqs-for-bgp-error-=
handling-04.txt

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

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-grow-ops-reqs-for-bgp-error-h=
andling-04.txt

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


From rjs@rob.sh  Wed Jun  6 08:34:34 2012
Return-Path: <rjs@rob.sh>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3957121F889B for <grow@ietfa.amsl.com>; Wed,  6 Jun 2012 08:34:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.372
X-Spam-Level: 
X-Spam-Status: No, score=-2.372 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SARE_SUB_OBFU_Q1=0.227]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1DUg5iOo44A7 for <grow@ietfa.amsl.com>; Wed,  6 Jun 2012 08:34:33 -0700 (PDT)
Received: from cappuccino.rob.sh (cappuccino.rob.sh [IPv6:2001:b98:201:101::10:cafe]) by ietfa.amsl.com (Postfix) with ESMTP id 75CF321F85F2 for <grow@ietf.org>; Wed,  6 Jun 2012 08:34:32 -0700 (PDT)
Received: from [109.144.222.193] (helo=[10.10.1.218]) by cappuccino.rob.sh with esmtpa (Exim 4.72) (envelope-from <rjs@rob.sh>) id 1ScIEV-0000AW-Nl; Wed, 06 Jun 2012 16:33:15 +0100
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=us-ascii
From: Rob Shakir <rjs@rob.sh>
In-Reply-To: <20120606150459.28821.4886.idtracker@ietfa.amsl.com>
Date: Wed, 6 Jun 2012 16:34:23 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <201DC116-9181-4DF5-A2DC-F91736912F85@rob.sh>
References: <20120606150459.28821.4886.idtracker@ietfa.amsl.com>
To: grow@ietf.org, grow-chairs@tools.ietf.org
X-Mailer: Apple Mail (2.1257)
Subject: Re: [GROW] I-D Action: draft-ietf-grow-ops-reqs-for-bgp-error-handling-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: Wed, 06 Jun 2012 15:34:34 -0000

Hi GROW,

Following the discussion and comments on and off the list over the last =
few weeks, I have made some modifications to some of the discussion =
within this draft.

Particularly, the changes are:

- As per Wes George's suggestion (and Sue Hares' request), added a =
statement that future updates to the BGP specification should define the =
category of error, and expected error handling class within which errors =
in each attribute fall.

- Updated the discussion of scaling considerations for both automated =
response to semantic errors, and the behaviour during repeated critical =
errors, as per the discussion on the GROW list. I think that this =
captures the conclusions that were reached, but comments are welcome.

- Some minor changes to wording and bringing drafts referenced in the =
informational references in line with the current drafts (mainly in =
light of a number of these drafts being adopted as IDR working group =
items).

Chris, Peter - I would like to request that this version of the draft is =
submitted for WGLC as I think this addresses all the outstanding =
comments both from the Paris meeting, and that I have received via on- =
and off-list mail.

Many thanks in advance for any comments and/or LC initiation!

Kind regards,
r.

On 6 Jun 2012, at 16:04, 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           : Operational Requirements for Enhanced Error =
Handling Behaviour in BGP-4
> 	Author(s)       : Rob Shakir
> 	Filename        : =
draft-ietf-grow-ops-reqs-for-bgp-error-handling-04.txt
> 	Pages           : 29
> 	Date            : 2012-06-06
>=20
>   BGP-4 is utilised as a key intra- and inter-Autonomous System =
routing
>   protocol in modern IP networks.  The failure modes as defined by the
>   original protocol standards are based on a number of assumptions
>   around the impact of session failure.  Numerous incidents both in =
the
>   global Internet routing table and within Service Provider networks
>   have been caused by strict handling of a single invalid UPDATE
>   message causing large-scale failures in one or more Autonomous
>   Systems.
>=20
>   This memo describes the current use of BGP-4 within Service Provider
>   networks, and outlines a set of requirements for further work to
>   enhance the mechanisms available to a BGP-4 implementation when
>   erroneous data is detected.  Whilst this document does not provide
>   specification of any standard, it is intended as an overview of a =
set
>   of enhancements to BGP-4 to improve the protocol's robustness to =
suit
>   its current deployment.
>=20
>=20
> A URL for this Internet-Draft is:
> =
http://www.ietf.org/internet-drafts/draft-ietf-grow-ops-reqs-for-bgp-error=
-handling-04.txt
>=20
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>=20
> This Internet-Draft can be retrieved at:
> =
ftp://ftp.ietf.org/internet-drafts/draft-ietf-grow-ops-reqs-for-bgp-error-=
handling-04.txt
>=20
> The IETF datatracker page for this Internet-Draft is:
> =
https://datatracker.ietf.org/doc/draft-ietf-grow-ops-reqs-for-bgp-error-ha=
ndling/
>=20
> _______________________________________________
> GROW mailing list
> GROW@ietf.org
> https://www.ietf.org/mailman/listinfo/grow


From ietfc@btconnect.com  Fri Jun  8 07:11:20 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 CD51021F8928 for <grow@ietfa.amsl.com>; Fri,  8 Jun 2012 07:11:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.63
X-Spam-Level: 
X-Spam-Status: No, score=-3.63 tagged_above=-999 required=5 tests=[AWL=-0.031,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BX+hOylIASlt for <grow@ietfa.amsl.com>; Fri,  8 Jun 2012 07:11:19 -0700 (PDT)
Received: from db3outboundpool.messaging.microsoft.com (db3ehsobe004.messaging.microsoft.com [213.199.154.142]) by ietfa.amsl.com (Postfix) with ESMTP id 00A0B21F8929 for <grow@ietf.org>; Fri,  8 Jun 2012 07:11:19 -0700 (PDT)
Received: from mail3-db3-R.bigfish.com (10.3.81.231) by DB3EHSOBE002.bigfish.com (10.3.84.22) with Microsoft SMTP Server id 14.1.225.23; Fri, 8 Jun 2012 14:10:27 +0000
Received: from mail3-db3 (localhost [127.0.0.1])	by mail3-db3-R.bigfish.com (Postfix) with ESMTP id 9034D3401E3; Fri,  8 Jun 2012 14:10:27 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.55.224.141; KIP:(null); UIP:(null); IPV:NLI; H:DB3PRD0702HT002.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -25
X-BigFish: PS-25(zzbb2dI9371I542M1432I1418Izz1202hzz1033IL8275bh8275dhz2dh2a8h5a9h668h839hd24hf0ah304l)
Received: from mail3-db3 (localhost.localdomain [127.0.0.1]) by mail3-db3 (MessageSwitch) id 1339164625700260_23991; Fri,  8 Jun 2012 14:10:25 +0000 (UTC)
Received: from DB3EHSMHS005.bigfish.com (unknown [10.3.81.249])	by mail3-db3.bigfish.com (Postfix) with ESMTP id A8C89A0047; Fri,  8 Jun 2012 14:10:25 +0000 (UTC)
Received: from DB3PRD0702HT002.eurprd07.prod.outlook.com (157.55.224.141) by DB3EHSMHS005.bigfish.com (10.3.87.105) with Microsoft SMTP Server (TLS) id 14.1.225.23; Fri, 8 Jun 2012 14:10:24 +0000
Received: from DBXPRD0610HT003.eurprd06.prod.outlook.com (157.56.252.181) by pod51017.outlook.com (10.3.4.146) with Microsoft SMTP Server (TLS) id 14.15.74.2; Fri, 8 Jun 2012 14:11:13 +0000
Message-ID: <01e301cd4580$208f3900$4001a8c0@gateway.2wire.net>
From: t.petch <ietfc@btconnect.com>
To: Christopher Morrow <christopher.morrow@gmail.com>, <grow-chairs@tools.ietf.org>, <grow@ietf.org>
References: <CAL9jLabADdWCwDhBdaBJ4fVdk9a=OeJQYFQM4Z_+-P56cVWftw@mail.gmail.com>
Date: Fri, 8 Jun 2012 15:06:16 +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.252.181]
X-OriginatorOrg: btconnect.com
Subject: Re: [GROW] WGLC: draft-ietf-grow-private-ip-sp-cores
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Jun 2012 14:11:21 -0000

I would like to see this published as an RFC.

The only discussion I see whether or not the title of 12.2 should have
an initial capital - I think that it should.

Tom Petch

----- Original Message -----
From: "Christopher Morrow" <christopher.morrow@gmail.com>
To: <grow-chairs@tools.ietf.org>; <grow@ietf.org>
Sent: Tuesday, June 05, 2012 7:41 PM
> Folks,
> There's been work on the draft:
>    <http://tools.ietf.org/html/draft-ietf-grow-private-ip-sp-cores>
>
> I think the commenters' comments were addressed by the authors.
> Can we move this to WGLC now and clear that 6/19/2012 (June 19, 2012).
>
> Abstract of the draft:
>   "The purpose of this document is to provide a discussion of the
>    potential problems of using private, RFC1918, or non-globally-
>    routable addressing within the core of an SP network.  The
discussion
>    focuses on link addresses and to a small extent loopback addresses.
>    While many of the issues are well recognised within the ISP
>    community, there appears to be no document that collectively
>    describes the issues."
>
> Could there be some discussion on WGLC and  we'll see about  moving
> this along to the IESG?
>
> -chris
> _______________________________________________
> GROW mailing list
> GROW@ietf.org
> https://www.ietf.org/mailman/listinfo/grow
>



From christopher.morrow@gmail.com  Fri Jun  8 10:08:37 2012
Return-Path: <christopher.morrow@gmail.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 64D1621F881D for <grow@ietfa.amsl.com>; Fri,  8 Jun 2012 10:08:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.299
X-Spam-Level: 
X-Spam-Status: No, score=-103.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_15=0.6, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id haKGa2FqYLI2 for <grow@ietfa.amsl.com>; Fri,  8 Jun 2012 10:08:36 -0700 (PDT)
Received: from mail-gg0-f172.google.com (mail-gg0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id 0234921F87F5 for <grow@ietf.org>; Fri,  8 Jun 2012 10:08:33 -0700 (PDT)
Received: by ggnc4 with SMTP id c4so1691528ggn.31 for <grow@ietf.org>; Fri, 08 Jun 2012 10:08:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=rbvn05k1U2O/5uHTw12qTRARAsxf7EuCAEXpUviYg70=; b=Qa76LVz2gKWIHvSMm3YovHrV4ADVrgj5gsoItCBfCIcy/EjDNxz7hDlLJseqZCKSVy 3joTifybWhp+Ds+dCm7zQi97eI0UIopUbWP5V6Ls6Adn6OrGAr4J5rOBQJD0V0XQy8MZ HNNigdCmes+WxPRcNe6f3BO7EnqaB6TGh+Xj2PASIbqM4z83jZVcJ8+t1valD6dylCSl P88bLclQ44lgvX6kpLaL/kmRUyio4vl4fxST6UQYxSKDi7QUdM+kTOwLXN1NvlAmv3Zm Xi7994kD25cbEoj/TBlINe2STMP4KqLGq2Gd4tKm2xaCrv0oQQm9YqzC6tIWlG1AiCtK 03TQ==
MIME-Version: 1.0
Received: by 10.60.20.70 with SMTP id l6mr7957811oee.38.1339175313451; Fri, 08 Jun 2012 10:08:33 -0700 (PDT)
Received: by 10.182.166.71 with HTTP; Fri, 8 Jun 2012 10:08:33 -0700 (PDT)
In-Reply-To: <01e301cd4580$208f3900$4001a8c0@gateway.2wire.net>
References: <CAL9jLabADdWCwDhBdaBJ4fVdk9a=OeJQYFQM4Z_+-P56cVWftw@mail.gmail.com> <01e301cd4580$208f3900$4001a8c0@gateway.2wire.net>
Date: Fri, 8 Jun 2012 13:08:33 -0400
Message-ID: <CAL9jLabZ0+q25DYR_bpP9fSks7+rauOWorP0oDe=2DB0rc-bQg@mail.gmail.com>
From: Christopher Morrow <christopher.morrow@gmail.com>
To: "t.petch" <ietfc@btconnect.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: grow@ietf.org, grow-chairs@tools.ietf.org
Subject: Re: [GROW] WGLC: draft-ietf-grow-private-ip-sp-cores
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Jun 2012 17:08:37 -0000

On Fri, Jun 8, 2012 at 10:06 AM, t.petch <ietfc@btconnect.com> wrote:
> I would like to see this published as an RFC.

thanks, I don't disagree.

> The only discussion I see whether or not the title of 12.2 should have
> an initial capital - I think that it should.

that seems like something that can get cleaned up by the editor if it
comes to it...

would be nice if more folk would chime in, however, in either the
positive or negative.

> Tom Petch
>
> ----- Original Message -----
> From: "Christopher Morrow" <christopher.morrow@gmail.com>
> To: <grow-chairs@tools.ietf.org>; <grow@ietf.org>
> Sent: Tuesday, June 05, 2012 7:41 PM
>> Folks,
>> There's been work on the draft:
>> =A0 =A0<http://tools.ietf.org/html/draft-ietf-grow-private-ip-sp-cores>
>>
>> I think the commenters' comments were addressed by the authors.
>> Can we move this to WGLC now and clear that 6/19/2012 (June 19, 2012).
>>
>> Abstract of the draft:
>> =A0 "The purpose of this document is to provide a discussion of the
>> =A0 =A0potential problems of using private, RFC1918, or non-globally-
>> =A0 =A0routable addressing within the core of an SP network. =A0The
> discussion
>> =A0 =A0focuses on link addresses and to a small extent loopback addresse=
s.
>> =A0 =A0While many of the issues are well recognised within the ISP
>> =A0 =A0community, there appears to be no document that collectively
>> =A0 =A0describes the issues."
>>
>> Could there be some discussion on WGLC and =A0we'll see about =A0moving
>> this along to the IESG?
>>
>> -chris
>> _______________________________________________
>> GROW mailing list
>> GROW@ietf.org
>> https://www.ietf.org/mailman/listinfo/grow
>>
>
>

From nick@inex.ie  Fri Jun  8 10:10:32 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 7A4FB21F8852 for <grow@ietfa.amsl.com>; Fri,  8 Jun 2012 10:10:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YRU9Wu0HOo4D for <grow@ietfa.amsl.com>; Fri,  8 Jun 2012 10:10:31 -0700 (PDT)
Received: from mail.acquirer.com (mail.acquirer.com [IPv6:2a03:8900:0:100::5]) by ietfa.amsl.com (Postfix) with ESMTP id 0AAEE21F884B for <grow@ietf.org>; Fri,  8 Jun 2012 10:10:29 -0700 (PDT)
X-Envelope-To: grow@ietf.org
Received: from cupcake.local ([IPv6:2001:1bb8:2004:100:5802:732e:320c:e81e]) (authenticated bits=0) by mail.acquirer.com (8.14.4/8.14.4) with ESMTP id q58HA58J023742 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Fri, 8 Jun 2012 18:10:05 +0100 (IST) (envelope-from nick@inex.ie)
Message-ID: <4FD231FE.2010503@inex.ie>
Date: Fri, 08 Jun 2012 18:10:22 +0100
From: Nick Hilliard <nick@inex.ie>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: Christopher Morrow <christopher.morrow@gmail.com>
References: <CAL9jLabADdWCwDhBdaBJ4fVdk9a=OeJQYFQM4Z_+-P56cVWftw@mail.gmail.com> <01e301cd4580$208f3900$4001a8c0@gateway.2wire.net> <CAL9jLabZ0+q25DYR_bpP9fSks7+rauOWorP0oDe=2DB0rc-bQg@mail.gmail.com>
In-Reply-To: <CAL9jLabZ0+q25DYR_bpP9fSks7+rauOWorP0oDe=2DB0rc-bQg@mail.gmail.com>
X-Enigmail-Version: 1.4.2
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-chairs@tools.ietf.org
Subject: Re: [GROW] WGLC: draft-ietf-grow-private-ip-sp-cores
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Jun 2012 17:10:32 -0000

On 08/06/2012 18:08, Christopher Morrow wrote:
> would be nice if more folk would chime in, however, in either the
> positive or negative.

+1

From warren@kumari.net  Fri Jun  8 11:34:26 2012
Return-Path: <warren@kumari.net>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8450B21F87F4 for <grow@ietfa.amsl.com>; Fri,  8 Jun 2012 11:34:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.075
X-Spam-Level: 
X-Spam-Status: No, score=-106.075 tagged_above=-999 required=5 tests=[AWL=-0.076, BAYES_00=-2.599, J_CHICKENPOX_15=0.6, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FhxvGvxJ20EO for <grow@ietfa.amsl.com>; Fri,  8 Jun 2012 11:34:26 -0700 (PDT)
Received: from vimes.kumari.net (vimes.kumari.net [198.186.192.250]) by ietfa.amsl.com (Postfix) with ESMTP id F0D6721F87F2 for <grow@ietf.org>; Fri,  8 Jun 2012 11:34:25 -0700 (PDT)
Received: from dhcp-172-19-118-235.cbf.corp.google.com (unknown [64.13.52.115]) by vimes.kumari.net (Postfix) with ESMTPSA id 817701B4062E; Fri,  8 Jun 2012 14:34:24 -0400 (EDT)
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=windows-1252
From: Warren Kumari <warren@kumari.net>
X-Priority: 3
In-Reply-To: <01e301cd4580$208f3900$4001a8c0@gateway.2wire.net>
Date: Fri, 8 Jun 2012 14:34:22 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <9A811639-8F60-4473-8B89-78065E8BA502@kumari.net>
References: <CAL9jLabADdWCwDhBdaBJ4fVdk9a=OeJQYFQM4Z_+-P56cVWftw@mail.gmail.com> <01e301cd4580$208f3900$4001a8c0@gateway.2wire.net>
To: t.petch <ietfc@btconnect.com>
X-Mailer: Apple Mail (2.1278)
Cc: grow@ietf.org, grow-chairs@tools.ietf.org
Subject: Re: [GROW] WGLC: draft-ietf-grow-private-ip-sp-cores
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Jun 2012 18:34:26 -0000

On Jun 8, 2012, at 10:06 AM, t.petch wrote:

> I would like to see this published as an RFC.
>=20

Yah, me too=85

W


> The only discussion I see whether or not the title of 12.2 should have
> an initial capital - I think that it should.
>=20
> Tom Petch
>=20
> ----- Original Message -----
> From: "Christopher Morrow" <christopher.morrow@gmail.com>
> To: <grow-chairs@tools.ietf.org>; <grow@ietf.org>
> Sent: Tuesday, June 05, 2012 7:41 PM
>> Folks,
>> There's been work on the draft:
>>   <http://tools.ietf.org/html/draft-ietf-grow-private-ip-sp-cores>
>>=20
>> I think the commenters' comments were addressed by the authors.
>> Can we move this to WGLC now and clear that 6/19/2012 (June 19, =
2012).
>>=20
>> Abstract of the draft:
>>  "The purpose of this document is to provide a discussion of the
>>   potential problems of using private, RFC1918, or non-globally-
>>   routable addressing within the core of an SP network.  The
> discussion
>>   focuses on link addresses and to a small extent loopback addresses.
>>   While many of the issues are well recognised within the ISP
>>   community, there appears to be no document that collectively
>>   describes the issues."
>>=20
>> Could there be some discussion on WGLC and  we'll see about  moving
>> this along to the IESG?
>>=20
>> -chris
>> _______________________________________________
>> GROW mailing list
>> GROW@ietf.org
>> https://www.ietf.org/mailman/listinfo/grow
>>=20
>=20
>=20
> _______________________________________________
> GROW mailing list
> GROW@ietf.org
> https://www.ietf.org/mailman/listinfo/grow
>=20

--=20
With Feudalism, it's your Count that votes.



From Donald.Smith@CenturyLink.com  Fri Jun  8 14:17:57 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 4AF4811E81A4 for <grow@ietfa.amsl.com>; Fri,  8 Jun 2012 14:17:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.149
X-Spam-Level: 
X-Spam-Status: No, score=-2.149 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, J_CHICKENPOX_15=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HoEuQyVRg58s for <grow@ietfa.amsl.com>; Fri,  8 Jun 2012 14:17:56 -0700 (PDT)
Received: from suomp64i.qwest.com (suomp64i.qwest.com [155.70.16.237]) by ietfa.amsl.com (Postfix) with ESMTP id 90D0F11E81A3 for <grow@ietf.org>; Fri,  8 Jun 2012 14:17:56 -0700 (PDT)
Received: from lxomavmpc030.qintra.com (lxomavmpc030.qintra.com [151.117.207.30]) by suomp64i.qwest.com (8.14.4/8.14.4) with ESMTP id q58LHqd2022372 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 8 Jun 2012 16:17:53 -0500 (CDT)
Received: from lxomavmpc030.qintra.com (unknown [127.0.0.1]) by IMSA (Postfix) with ESMTP id C24E01E006F; Fri,  8 Jun 2012 16:17:47 -0500 (CDT)
Received: from suomp60i.qintra.com (unknown [10.6.10.61]) by lxomavmpc030.qintra.com (Postfix) with ESMTP id A5E481E0049; Fri,  8 Jun 2012 16:17:47 -0500 (CDT)
Received: from suomp60i.qintra.com (localhost [127.0.0.1]) by suomp60i.qintra.com (8.14.4/8.14.4) with ESMTP id q58LHlW4003604; Fri, 8 Jun 2012 16:17:47 -0500 (CDT)
Received: from qtdenexhtm22.AD.QINTRA.COM (qtdenexhtm22.ad.qintra.com [151.119.91.231]) by suomp60i.qintra.com (8.14.4/8.14.4) with ESMTP id q58LHkCd003591 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=FAIL); Fri, 8 Jun 2012 16:17:46 -0500 (CDT)
Received: from qtdenexmbm24.AD.QINTRA.COM ([151.119.91.226]) by qtdenexhtm22.AD.QINTRA.COM ([151.119.91.231]) with mapi; Fri, 8 Jun 2012 15:17:46 -0600
From: "Smith, Donald" <Donald.Smith@CenturyLink.com>
To: "'t.petch'" <ietfc@btconnect.com>, "'Christopher Morrow'" <christopher.morrow@gmail.com>, "'grow-chairs@tools.ietf.org'" <grow-chairs@tools.ietf.org>, "'grow@ietf.org'" <grow@ietf.org>
Date: Fri, 8 Jun 2012 15:17:45 -0600
Thread-Topic: [GROW] WGLC: draft-ietf-grow-private-ip-sp-cores
Thread-Index: Ac1FgJ6vgtEZ35ZmSaqKaQwu8OLjdQACC/Wg
Message-ID: <B01905DA0C7CDC478F42870679DF0F101105C4C714@qtdenexmbm24.AD.QINTRA.COM>
References: <CAL9jLabADdWCwDhBdaBJ4fVdk9a=OeJQYFQM4Z_+-P56cVWftw@mail.gmail.com> <01e301cd4580$208f3900$4001a8c0@gateway.2wire.net>
In-Reply-To: <01e301cd4580$208f3900$4001a8c0@gateway.2wire.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: Re: [GROW] WGLC: draft-ietf-grow-private-ip-sp-cores
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Jun 2012 21:17:57 -0000

There is a mention of "squat" space that doesn't make any recommendations a=
s to use or not.

I can understand not expressing an opinion on the rfc1918/private space sho=
uldn't this state that squating is bad?
"This effect in itself is often not a problem.  However, if anti-
   spoofing controls are applied at network perimeters, then responses
   returned from hops with private IP addresses will be dropped."

Any rfc1918 filtering mechinisim will cause this issue not just bcp38 type =
anti-spoofing.
Firewalls, junipers and many platforms drop rfc1918 space but not as part o=
f bcp38 .
BTW BCP84 ala rfc3704 is an update/addition to bcp38 you should probably ad=
d them to this reference.


And for consistecy I recommend using an expression such as "any rfc1918 or =
bogon filtering..."

Under section 4 the author says urpf or ingress filtering.
"If the router's interface address is a
   private IP address, then this ICMP reply packet may be discarded due
   to uRPF or ingress filtering, thereby causing the PMTUD mechanism to
   fail."

Under
5. Unexpected interactions with some NAT implementations
The first section works. As stated it might confuse someone but honestly un=
less the 4th hop also matches the 2 hop it doesn't look like a routing loop=
 to me. It looks like rfc1918 reuse.


Type escape sequence to abort.
   Tracing the route to 198.51.100.100

     1 10.1.1.2 0 msec 0 msec 0 msec
     2 198.51.100.13 0 msec 4 msec 0 msec
     3 10.1.1.2 0 msec 4 msec 0 msec        <<<<
     4 198.51.100.5 4 msec 0 msec 4 msec
     5 198.51.100.1 0 msec 0 msec 0 msec

Section 6 references rfc2827 should probably include bcp84 and rfc3704.

Your first example of a security gap is really a no worse if you use privat=
e or public addresss but you call that out so I am ok with it.

NIT
This:
Some applications discover the outside address of
   their local CPE to determine if that address is reserver for special
   use.
Should be this:
Some applications discover the outside address of
   their local CPE to determine if that address is reserved for special
   use.


When packets collide the controllers cease transmission AND wait a random t=
ime before retransmission (mostly)!
Donald.Smith@CenturyLink.com


> -----Original Message-----
> From: grow-bounces@ietf.org [mailto:grow-bounces@ietf.org] On Behalf Of
> t.petch
> Sent: Friday, June 08, 2012 8:06 AM
> To: Christopher Morrow; grow-chairs@tools.ietf.org; grow@ietf.org
> Subject: Re: [GROW] WGLC: draft-ietf-grow-private-ip-sp-cores
>
> I would like to see this published as an RFC.
>
> The only discussion I see whether or not the title of 12.2 should have
> an initial capital - I think that it should.
>
> Tom Petch
>
> ----- Original Message -----
> From: "Christopher Morrow" <christopher.morrow@gmail.com>
> To: <grow-chairs@tools.ietf.org>; <grow@ietf.org>
> Sent: Tuesday, June 05, 2012 7:41 PM
> > Folks,
> > There's been work on the draft:
> >    <http://tools.ietf.org/html/draft-ietf-grow-private-ip-sp-cores>
> >
> > I think the commenters' comments were addressed by the authors.
> > Can we move this to WGLC now and clear that 6/19/2012 (June 19,
> 2012).
> >
> > Abstract of the draft:
> >   "The purpose of this document is to provide a discussion of the
> >    potential problems of using private, RFC1918, or non-globally-
> >    routable addressing within the core of an SP network.  The
> discussion
> >    focuses on link addresses and to a small extent loopback
> addresses.
> >    While many of the issues are well recognised within the ISP
> >    community, there appears to be no document that collectively
> >    describes the issues."
> >
> > Could there be some discussion on WGLC and  we'll see about  moving
> > this along to the IESG?
> >
> > -chris
> > _______________________________________________
> > 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

This communication is the property of CenturyLink and may contain confident=
ial or privileged information. Unauthorized use of this communication is st=
rictly
prohibited and may be unlawful.  If you have received this communication
in error, please immediately notify the sender by reply e-mail and destroy
all copies of the communication and any attachments.

From wesley.george@twcable.com  Mon Jun 11 07:36:40 2012
Return-Path: <wesley.george@twcable.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 6065C21F8657 for <grow@ietfa.amsl.com>; Mon, 11 Jun 2012 07:36:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.137
X-Spam-Level: 
X-Spam-Status: No, score=0.137 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, J_CHICKENPOX_15=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zxuuhfd8e-bD for <grow@ietfa.amsl.com>; Mon, 11 Jun 2012 07:36:39 -0700 (PDT)
Received: from cdpipgw02.twcable.com (cdpipgw02.twcable.com [165.237.59.23]) by ietfa.amsl.com (Postfix) with ESMTP id B9CDA21F864F for <grow@ietf.org>; Mon, 11 Jun 2012 07:36:39 -0700 (PDT)
X-SENDER-IP: 10.136.163.12
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.75,750,1330923600"; d="scan'208";a="376692768"
Received: from unknown (HELO PRVPEXHUB03.corp.twcable.com) ([10.136.163.12]) by cdpipgw02.twcable.com with ESMTP/TLS/RC4-MD5; 11 Jun 2012 10:36:04 -0400
Received: from PRVPEXVS03.corp.twcable.com ([10.136.163.26]) by PRVPEXHUB03.corp.twcable.com ([10.136.163.12]) with mapi; Mon, 11 Jun 2012 10:36:38 -0400
From: "George, Wes" <wesley.george@twcable.com>
To: "grow@ietf.org" <grow@ietf.org>, "grow-chairs@tools.ietf.org" <grow-chairs@tools.ietf.org>
Date: Mon, 11 Jun 2012 10:36:33 -0400
Thread-Topic: [GROW] WGLC: draft-ietf-grow-private-ip-sp-cores
Thread-Index: Ac1FpWqFOae6+yLqTDeISRzkFYLXVwCOddxg
Message-ID: <DCC302FAA9FE5F4BBA4DCAD4656937791743045351@PRVPEXVS03.corp.twcable.com>
References: <CAL9jLabADdWCwDhBdaBJ4fVdk9a=OeJQYFQM4Z_+-P56cVWftw@mail.gmail.com> <01e301cd4580$208f3900$4001a8c0@gateway.2wire.net> <9A811639-8F60-4473-8B89-78065E8BA502@kumari.net>
In-Reply-To: <9A811639-8F60-4473-8B89-78065E8BA502@kumari.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [GROW] WGLC: draft-ietf-grow-private-ip-sp-cores
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Jun 2012 14:36:40 -0000

I support publishing. I have brought up concerns around some overlap with a=
nother draft, however I believe that this document is far more complete tha=
n draft-behringer-lla-only, and can stand on its own.

Thanks,

Wes George


> -----Original Message-----
> From: grow-bounces@ietf.org [mailto:grow-bounces@ietf.org] On Behalf Of
> Warren Kumari
> Sent: Friday, June 08, 2012 2:34 PM
> To: t.petch
> Cc: grow@ietf.org; grow-chairs@tools.ietf.org
> Subject: Re: [GROW] WGLC: draft-ietf-grow-private-ip-sp-cores
>
>
> On Jun 8, 2012, at 10:06 AM, t.petch wrote:
>
> > I would like to see this published as an RFC.
> >
>
> Yah, me too...
>
> W
>
>
> > The only discussion I see whether or not the title of 12.2 should have
> > an initial capital - I think that it should.
> >
> > Tom Petch
> >
> > ----- Original Message -----
> > From: "Christopher Morrow" <christopher.morrow@gmail.com>
> > To: <grow-chairs@tools.ietf.org>; <grow@ietf.org>
> > Sent: Tuesday, June 05, 2012 7:41 PM
> >> Folks,
> >> There's been work on the draft:
> >>   <http://tools.ietf.org/html/draft-ietf-grow-private-ip-sp-cores>
> >>
> >> I think the commenters' comments were addressed by the authors.
> >> Can we move this to WGLC now and clear that 6/19/2012 (June 19,
> 2012).
> >>
> >> Abstract of the draft:
> >>  "The purpose of this document is to provide a discussion of the
> >>   potential problems of using private, RFC1918, or non-globally-
> >>   routable addressing within the core of an SP network.  The
> > discussion
> >>   focuses on link addresses and to a small extent loopback addresses.
> >>   While many of the issues are well recognised within the ISP
> >>   community, there appears to be no document that collectively
> >>   describes the issues."
> >>
> >> Could there be some discussion on WGLC and  we'll see about  moving
> >> this along to the IESG?
> >>
> >> -chris
> >> _______________________________________________
> >> 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
> >
>
> --
> With Feudalism, it's your Count that votes.
>
>
> _______________________________________________
> GROW mailing list
> GROW@ietf.org
> https://www.ietf.org/mailman/listinfo/grow

This E-mail and any of its attachments may contain Time Warner Cable propri=
etary information, which is privileged, confidential, or subject to copyrig=
ht belonging to Time Warner Cable. This E-mail is intended solely for the u=
se of the individual or entity to which it is addressed. If you are not the=
 intended recipient of this E-mail, you are hereby notified that any dissem=
ination, distribution, copying, or action taken in relation to the contents=
 of and attachments to this E-mail is strictly prohibited and may be unlawf=
ul. If you have received this E-mail in error, please notify the sender imm=
ediately and permanently delete the original and any copy of this E-mail an=
d any printout.

From pds@lugs.com  Mon Jun 11 07:54:54 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 5D8BE21F85CE for <grow@ietfa.amsl.com>; Mon, 11 Jun 2012 07:54:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.739
X-Spam-Level: 
X-Spam-Status: No, score=-100.739 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Z52IP-hQlf08 for <grow@ietfa.amsl.com>; Mon, 11 Jun 2012 07:54:52 -0700 (PDT)
Received: from murdock.lugs.com (murdock.lugs.com [192.80.15.4]) by ietfa.amsl.com (Postfix) with ESMTP id 39EA121F8573 for <grow@ietf.org>; Mon, 11 Jun 2012 07:54:52 -0700 (PDT)
Received: from r9m1fw1 (unknown [61.8.239.2]) by murdock.lugs.com (Postfix) with ESMTPSA id F3451D35B2 for <grow@ietf.org>; Mon, 11 Jun 2012 10:54:48 -0400 (EDT)
From: "Peter Schoenmaker" <pds@lugs.com>
To: <grow@ietf.org>
Date: Mon, 11 Jun 2012 22:54:46 +0800
Message-ID: <005c01cd47e2$267e8820$737b9860$@lugs.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_005D_01CD4825.34A300A0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac1H4crcZ3Q1XdDURpGiyMYCordLaQ==
Content-Language: en-us
Subject: [GROW] WGLC: draft-ietf-grow-diverse-bgp-path-dist-07
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, 11 Jun 2012 14:54:54 -0000

This is a multipart message in MIME format.

------=_NextPart_000_005D_01CD4825.34A300A0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit

Hi,

 

Based on discussion at the last Grow meeting in Paris, it was agreed that
draft-ietf-grow-diverse-bgp-path-dist-07 is ready for working group last
call.  It would be good to have some discussion on the draft before
submitting it to the IESG.

 

Abstract

 

   The BGP4 protocol specifies the selection and propagation of a single

   best path for each prefix.  As defined and widely deployed today BGP

   has no mechanisms to distribute alternate paths which are not

   considered best path between its speakers.  This behaviour results in

   number of disadvantages for new applications and services.

 

   This document presents an alternative mechanism for solving the

   problem based on the concept of parallel route reflector planes.

   Such planes can be built in parallel or they can co-exist on the

   current route reflection platforms.  Document also compares existing

   solutions and proposed ideas that enable distribution of more paths

   than just the best path.

 

   This proposal does not specify any changes to the BGP protocol

   definition.  It does not require upgrades to provider edge or core

   routers nor does it need network wide upgrades.

 

 

Thanks

 

Peter

 

 


------=_NextPart_000_005D_01CD4825.34A300A0
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;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";}
.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>Hi,<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Based on =
discussion at the last Grow meeting in Paris, it was agreed that =
draft-ietf-grow-diverse-bgp-path-dist-07 is ready for working group last =
call.&nbsp; It would be good to have some discussion on the draft before =
submitting it to the IESG.<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>Abstract<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>&nbsp;&nbsp; =
The BGP4 protocol specifies the selection and propagation of a =
single<o:p></o:p></p><p class=3DMsoNormal>&nbsp;&nbsp; best path for =
each prefix.&nbsp; As defined and widely deployed today =
BGP<o:p></o:p></p><p class=3DMsoNormal>&nbsp;&nbsp; has no mechanisms to =
distribute alternate paths which are not<o:p></o:p></p><p =
class=3DMsoNormal>&nbsp;&nbsp; considered best path between its =
speakers.&nbsp; This behaviour results in<o:p></o:p></p><p =
class=3DMsoNormal>&nbsp;&nbsp; number of disadvantages for new =
applications and services.<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>&nbsp;&nbsp; =
This document presents an alternative mechanism for solving =
the<o:p></o:p></p><p class=3DMsoNormal>&nbsp;&nbsp; problem based on the =
concept of parallel route reflector planes.<o:p></o:p></p><p =
class=3DMsoNormal>&nbsp;&nbsp; Such planes can be built in parallel or =
they can co-exist on the<o:p></o:p></p><p class=3DMsoNormal>&nbsp;&nbsp; =
current route reflection platforms.&nbsp; Document also compares =
existing<o:p></o:p></p><p class=3DMsoNormal>&nbsp;&nbsp; solutions and =
proposed ideas that enable distribution of more paths<o:p></o:p></p><p =
class=3DMsoNormal>&nbsp;&nbsp; than just the best path.<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>&nbsp;&nbsp; =
This proposal does not specify any changes to the BGP =
protocol<o:p></o:p></p><p class=3DMsoNormal>&nbsp;&nbsp; =
definition.&nbsp; It does not require upgrades to provider edge or =
core<o:p></o:p></p><p class=3DMsoNormal>&nbsp;&nbsp; routers nor does it =
need network wide upgrades.<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</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_005D_01CD4825.34A300A0--


From christopher.morrow@gmail.com  Mon Jun 11 13:19:46 2012
Return-Path: <christopher.morrow@gmail.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5A86C21F8501 for <grow@ietfa.amsl.com>; Mon, 11 Jun 2012 13:19:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.372
X-Spam-Level: 
X-Spam-Status: No, score=-103.372 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, SARE_SUB_OBFU_Q1=0.227, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BWGKRW7R3NJP for <grow@ietfa.amsl.com>; Mon, 11 Jun 2012 13:19:45 -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 8DCDC21F84FF for <grow@ietf.org>; Mon, 11 Jun 2012 13:19:45 -0700 (PDT)
Received: by obbeh20 with SMTP id eh20so10037825obb.31 for <grow@ietf.org>; Mon, 11 Jun 2012 13:19:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=01nn4+gpG1084FANwczpfUIbSbg2R4mFDPcdIZHvd8w=; b=cmhM2EIJLYYnYb465HjalWtaywUXJ/HiG5h5vpa1cZ6IqPQ9yBUs11ZRaAmJnpH/2g FMsJjQEv/Zjq/MgHm5PlhATpYASJXBPtuJg3yNzr6fbkalleEQaS+f4Ylm5uv3F/aRK6 ATbJKcMXSTwXHkBlmWrxrtp2cSPb8fKJWGZMRQFs3CSyTkmt1u+StklWNC+zsUcKOVzk 9z1+u2nkBVPm8U4+BnfnWuimQ8v+66bRT7yuauPMvGQ87AUQrU0GinpoWMsDhu9xtbBL xHm0LtGrqnYkZ2hepEiRrKlwQjC3XmmhECWfOvJnCoK92pHoCIOOoaYrfbaq/NeGuw9r Eelw==
MIME-Version: 1.0
Received: by 10.182.228.6 with SMTP id se6mr17508057obc.29.1339445985076; Mon, 11 Jun 2012 13:19:45 -0700 (PDT)
Received: by 10.182.166.71 with HTTP; Mon, 11 Jun 2012 13:19:45 -0700 (PDT)
In-Reply-To: <201DC116-9181-4DF5-A2DC-F91736912F85@rob.sh>
References: <20120606150459.28821.4886.idtracker@ietfa.amsl.com> <201DC116-9181-4DF5-A2DC-F91736912F85@rob.sh>
Date: Mon, 11 Jun 2012 16:19:45 -0400
Message-ID: <CAL9jLaaN+kY_Wq2Sqyd4XSxSMGbCCQEEpO8aVyZixtFwnTFZ9w@mail.gmail.com>
From: Christopher Morrow <christopher.morrow@gmail.com>
To: Rob Shakir <rjs@rob.sh>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: grow@ietf.org, grow-chairs@tools.ietf.org
Subject: Re: [GROW] I-D Action: draft-ietf-grow-ops-reqs-for-bgp-error-handling-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, 11 Jun 2012 20:19:46 -0000

On Wed, Jun 6, 2012 at 11:34 AM, Rob Shakir <rjs@rob.sh> wrote:
> Hi GROW,
>
> Following the discussion and comments on and off the list over the last f=
ew weeks, I have made some modifications to some of the discussion within t=
his draft.
>
> Particularly, the changes are:
>
> - As per Wes George's suggestion (and Sue Hares' request), added a statem=
ent that future updates to the BGP specification should define the category=
 of error, and expected error handling class within which errors in each at=
tribute fall.
>
> - Updated the discussion of scaling considerations for both automated res=
ponse to semantic errors, and the behaviour during repeated critical errors=
, as per the discussion on the GROW list. I think that this captures the co=
nclusions that were reached, but comments are welcome.
>
> - Some minor changes to wording and bringing drafts referenced in the inf=
ormational references in line with the current drafts (mainly in light of a=
 number of these drafts being adopted as IDR working group items).
>
> Chris, Peter - I would like to request that this version of the draft is =
submitted for WGLC as I think this addresses all the outstanding comments b=
oth from the Paris meeting, and that I have received via on- and off-list m=
ail.
>

sounds good to me... look for that in a moment.

> Many thanks in advance for any comments and/or LC initiation!
>
> Kind regards,
> r.
>
> On 6 Jun 2012, at 16:04, Internet-Drafts@ietf.org wrote:
>
>>
>> A New Internet-Draft is available from the on-line Internet-Drafts direc=
tories. This draft is a work item of the Global Routing Operations Working =
Group of the IETF.
>>
>> =A0 =A0 =A0 Title =A0 =A0 =A0 =A0 =A0 : Operational Requirements for Enh=
anced Error Handling Behaviour in BGP-4
>> =A0 =A0 =A0 Author(s) =A0 =A0 =A0 : Rob Shakir
>> =A0 =A0 =A0 Filename =A0 =A0 =A0 =A0: draft-ietf-grow-ops-reqs-for-bgp-e=
rror-handling-04.txt
>> =A0 =A0 =A0 Pages =A0 =A0 =A0 =A0 =A0 : 29
>> =A0 =A0 =A0 Date =A0 =A0 =A0 =A0 =A0 =A0: 2012-06-06
>>
>> =A0 BGP-4 is utilised as a key intra- and inter-Autonomous System routin=
g
>> =A0 protocol in modern IP networks. =A0The failure modes as defined by t=
he
>> =A0 original protocol standards are based on a number of assumptions
>> =A0 around the impact of session failure. =A0Numerous incidents both in =
the
>> =A0 global Internet routing table and within Service Provider networks
>> =A0 have been caused by strict handling of a single invalid UPDATE
>> =A0 message causing large-scale failures in one or more Autonomous
>> =A0 Systems.
>>
>> =A0 This memo describes the current use of BGP-4 within Service Provider
>> =A0 networks, and outlines a set of requirements for further work to
>> =A0 enhance the mechanisms available to a BGP-4 implementation when
>> =A0 erroneous data is detected. =A0Whilst this document does not provide
>> =A0 specification of any standard, it is intended as an overview of a se=
t
>> =A0 of enhancements to BGP-4 to improve the protocol's robustness to sui=
t
>> =A0 its current deployment.
>>
>>
>> A URL for this Internet-Draft is:
>> http://www.ietf.org/internet-drafts/draft-ietf-grow-ops-reqs-for-bgp-err=
or-handling-04.txt
>>
>> Internet-Drafts are also available by anonymous FTP at:
>> ftp://ftp.ietf.org/internet-drafts/
>>
>> This Internet-Draft can be retrieved at:
>> ftp://ftp.ietf.org/internet-drafts/draft-ietf-grow-ops-reqs-for-bgp-erro=
r-handling-04.txt
>>
>> The IETF datatracker page for this Internet-Draft is:
>> https://datatracker.ietf.org/doc/draft-ietf-grow-ops-reqs-for-bgp-error-=
handling/
>>
>> _______________________________________________
>> GROW mailing list
>> GROW@ietf.org
>> https://www.ietf.org/mailman/listinfo/grow
>

From christopher.morrow@gmail.com  Mon Jun 11 13:21:53 2012
Return-Path: <christopher.morrow@gmail.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 791FF21F85C3 for <grow@ietfa.amsl.com>; Mon, 11 Jun 2012 13:21:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.372
X-Spam-Level: 
X-Spam-Status: No, score=-103.372 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, SARE_SUB_OBFU_Q1=0.227, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L5Wm4ybpjDuG for <grow@ietfa.amsl.com>; Mon, 11 Jun 2012 13:21:53 -0700 (PDT)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id 95CD621F85AF for <grow@ietf.org>; Mon, 11 Jun 2012 13:21:51 -0700 (PDT)
Received: by yhq56 with SMTP id 56so3418830yhq.31 for <grow@ietf.org>; Mon, 11 Jun 2012 13:21:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=nN86dXuxca/34s7mr2oTM+VxO7mXUotU8/E9dIOCK6Q=; b=saJs+aTc7nCfz+x4I4QX/b8WZ4QZe9Nz5F6LBwkq2qwMZbk7dm5bcuZzLvfY/M6fVw NvqM8j31rZAJwrdfHOTLSiCIzDUFs7cwJ7eI/jcsZeojW7+Fq56Icojidi2u4CTMl53L 8NEtNuUpoKLl4DTO/j5awM47ERb8Vr7uamfzHRUCrnybE89M/fq79v5gA4MKcGpEDYQt BQZUpSQl1FZoJDkRTkVlnK+gZtYcEIooI62AkAUIibeGpzstLLTXkNUuu7Kk6FEkylLD W1BUPL+pBRN+psEOCIYoWVX7PPq5lKjRUtCBswe2v6GMAtJVFUKw32YiPjxtuZvlnpGF rp4w==
MIME-Version: 1.0
Received: by 10.60.24.7 with SMTP id q7mr17734852oef.50.1339446109067; Mon, 11 Jun 2012 13:21:49 -0700 (PDT)
Received: by 10.182.166.71 with HTTP; Mon, 11 Jun 2012 13:21:49 -0700 (PDT)
Date: Mon, 11 Jun 2012 16:21:49 -0400
Message-ID: <CAL9jLabOs02rOti4tezaZiHyiOD2f9vAhsoE9c-afFb4J1xYXQ@mail.gmail.com>
From: Christopher Morrow <christopher.morrow@gmail.com>
To: grow-chairs@tools.ietf.org, "grow@ietf.org grow@ietf.org" <grow@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Subject: [GROW] WGLC: draft-ietf-grow-ops-reqs-for-bgp-error-handling-04
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Jun 2012 20:21:53 -0000

Hello GROW-WG folk,
Please take this message as the start of a 2 week, ending 6/25/2012
(June 25, 2012) WGLC for the subject draft, link to current version:
  <http://www.ietf.org/internet-drafts/draft-ietf-grow-ops-reqs-for-bgp-error-handling-04.txt>

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

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

-Chris
co-chair

From shtsuchi@cisco.com  Mon Jun 11 19:18:59 2012
Return-Path: <shtsuchi@cisco.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D5E9F21F8513 for <grow@ietfa.amsl.com>; Mon, 11 Jun 2012 19:18:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.999
X-Spam-Level: 
X-Spam-Status: No, score=-9.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_15=0.6, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fbOweNlkSaee for <grow@ietfa.amsl.com>; Mon, 11 Jun 2012 19:18:59 -0700 (PDT)
Received: from bgl-iport-1.cisco.com (bgl-iport-1.cisco.com [72.163.197.25]) by ietfa.amsl.com (Postfix) with ESMTP id 9A5F721F8510 for <grow@ietf.org>; Mon, 11 Jun 2012 19:18:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=shtsuchi@cisco.com; l=1643; q=dns/txt; s=iport; t=1339467539; x=1340677139; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=zkHZm65LcyAaVY3+OyJppsz0swptHD1p3xMeroiGNo4=; b=IS9d9oqvX7G0ovyzq4XwwXFdovnCf33X/CEWavAgjY1Pr1rUX90q+WWb 26Pny3eEitLohfyb9rRVSxHsHpdCFD7UBzjvU6mjhhUiT4wW/Hnn3ajtg bH+ibCTwa09CtdbGxZ5vUke4IjqMxzf6y/6R6D12tpTGmS+VBkGg2CkVi M=;
X-IronPort-AV: E=Sophos;i="4.75,752,1330905600"; d="scan'208";a="14048128"
Received: from vla196-nat.cisco.com (HELO bgl-core-2.cisco.com) ([72.163.197.24]) by bgl-iport-1.cisco.com with ESMTP; 12 Jun 2012 02:18:54 +0000
Received: from [10.141.32.108] (dhcp-10-141-32-108.cisco.com [10.141.32.108]) by bgl-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id q5C2IrBb026182; Tue, 12 Jun 2012 07:48:53 +0530
Message-ID: <4FD6A70C.50103@cisco.com>
Date: Tue, 12 Jun 2012 11:18:52 +0900
From: Shishio Tsuchiya <shtsuchi@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: grow-chairs@tools.ietf.org, grow@ietf.org
References: <CAL9jLabADdWCwDhBdaBJ4fVdk9a=OeJQYFQM4Z_+-P56cVWftw@mail.gmail.com> <01e301cd4580$208f3900$4001a8c0@gateway.2wire.net>
In-Reply-To: <01e301cd4580$208f3900$4001a8c0@gateway.2wire.net>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
Subject: Re: [GROW] WGLC: draft-ietf-grow-private-ip-sp-cores
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Jun 2012 02:19:00 -0000

(2012/06/08 23:06), t.petch wrote:
> I would like to see this published as an RFC.

+1 I support publishing.

Regards,
-Shishio


> 
> The only discussion I see whether or not the title of 12.2 should have
> an initial capital - I think that it should.
> 
> Tom Petch
> 
> ----- Original Message -----
> From: "Christopher Morrow"<christopher.morrow@gmail.com>
> To:<grow-chairs@tools.ietf.org>;<grow@ietf.org>
> Sent: Tuesday, June 05, 2012 7:41 PM
>> Folks,
>> There's been work on the draft:
>>     <http://tools.ietf.org/html/draft-ietf-grow-private-ip-sp-cores>
>>
>> I think the commenters' comments were addressed by the authors.
>> Can we move this to WGLC now and clear that 6/19/2012 (June 19, 2012).
>>
>> Abstract of the draft:
>>    "The purpose of this document is to provide a discussion of the
>>     potential problems of using private, RFC1918, or non-globally-
>>     routable addressing within the core of an SP network.  The
> discussion
>>     focuses on link addresses and to a small extent loopback addresses.
>>     While many of the issues are well recognised within the ISP
>>     community, there appears to be no document that collectively
>>     describes the issues."
>>
>> Could there be some discussion on WGLC and  we'll see about  moving
>> this along to the IESG?
>>
>> -chris
>> _______________________________________________
>> 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 tkirkham@anthony-kirkham.com  Wed Jun 13 03:58:59 2012
Return-Path: <tkirkham@anthony-kirkham.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C83D521F852A for <grow@ietfa.amsl.com>; Wed, 13 Jun 2012 03:58:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_15=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gsO8SxTBO9QN for <grow@ietfa.amsl.com>; Wed, 13 Jun 2012 03:58:59 -0700 (PDT)
Received: from nschwmtas05p.mx.bigpond.com (nschwmtas05p.mx.bigpond.com [61.9.189.149]) by ietfa.amsl.com (Postfix) with ESMTP id B9F8121F8474 for <grow@ietf.org>; Wed, 13 Jun 2012 03:58:58 -0700 (PDT)
Received: from nschwcmgw05p ([61.9.190.165]) by nschwmtas05p.mx.bigpond.com with ESMTP id <20120613105856.UCQW2821.nschwmtas05p.mx.bigpond.com@nschwcmgw05p>;  Wed, 13 Jun 2012 10:58:56 +0000
Received: from Anthonys-MacBook-Pro.local ([123.211.150.122]) by nschwcmgw05p with BigPond Outbound id Mmyr1j0012ehmur01myt13; Wed, 13 Jun 2012 10:58:56 +0000
X-Authority-Analysis: v=2.0 cv=D4zF24tj c=1 sm=1 a=+yKKctPzAZhvBC3CJUMNgg==:17 a=_1pLAPWVdgkA:10 a=5guEdk2PV24A:10 a=Ib5BsLsVyy8A:10 a=bVeADsv9IVkA:10 a=kj9zAlcOel0A:10 a=xR3Tfk4wAAAA:8 a=J_N6KFswAAAA:8 a=48vgC7mUAAAA:8 a=pGLkceISAAAA:8 a=iSoXIPpArbcnMEQ-6CQA:9 a=CjuIK1q_8ugA:10 a=Pwbduc0PQ3sA:10 a=lZB815dzVvQA:10 a=MSl-tDqOz04A:10 a=tdsJYqgepGP4buZd:21 a=dYBJvqu5JNsmEfjc:21 a=+yKKctPzAZhvBC3CJUMNgg==:117
Message-ID: <4FD8726A.6040509@anthony-kirkham.com>
Date: Wed, 13 Jun 2012 20:58:50 +1000
From: Anthony Kirkham <tkirkham@anthony-kirkham.com>
Organization: Anthony-Kirkham.com
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: "Smith, Donald" <Donald.Smith@CenturyLink.com>
References: <CAL9jLabADdWCwDhBdaBJ4fVdk9a=OeJQYFQM4Z_+-P56cVWftw@mail.gmail.com> <01e301cd4580$208f3900$4001a8c0@gateway.2wire.net> <B01905DA0C7CDC478F42870679DF0F101105C4C714@qtdenexmbm24.AD.QINTRA.COM>
In-Reply-To: <B01905DA0C7CDC478F42870679DF0F101105C4C714@qtdenexmbm24.AD.QINTRA.COM>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "'grow@ietf.org'" <grow@ietf.org>, "'grow-chairs@tools.ietf.org'" <grow-chairs@tools.ietf.org>
Subject: Re: [GROW] WGLC: draft-ietf-grow-private-ip-sp-cores
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: tkirkham@anthony-kirkham.com
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jun 2012 10:58:59 -0000

Donald,

Thanks for the review, I plan to do another update in the next few days, 
I'm just waiting to see if any further feedback arrives.

A couple of specific comments:

re - squat space. The intent was not to make recommendations on the 
practice, just to document the effects.

re - 5. Unexpected interactions with some NAT implementations: What you 
say is exactly what I intended to illustrate. I will update the wording 
so its clear I'm not talking about a routing loop.

Regards
Tony K

On 9/06/12 7:17 AM, Smith, Donald wrote:
> There is a mention of "squat" space that doesn't make any recommendations as to use or not.
>
> I can understand not expressing an opinion on the rfc1918/private space shouldn't this state that squating is bad?
> "This effect in itself is often not a problem.  However, if anti-
>     spoofing controls are applied at network perimeters, then responses
>     returned from hops with private IP addresses will be dropped."
>
> Any rfc1918 filtering mechinisim will cause this issue not just bcp38 type anti-spoofing.
> Firewalls, junipers and many platforms drop rfc1918 space but not as part of bcp38 .
> BTW BCP84 ala rfc3704 is an update/addition to bcp38 you should probably add them to this reference.
>
>
> And for consistecy I recommend using an expression such as "any rfc1918 or bogon filtering..."
>
> Under section 4 the author says urpf or ingress filtering.
> "If the router's interface address is a
>     private IP address, then this ICMP reply packet may be discarded due
>     to uRPF or ingress filtering, thereby causing the PMTUD mechanism to
>     fail."
>
> Under
> 5. Unexpected interactions with some NAT implementations
> The first section works. As stated it might confuse someone but honestly unless the 4th hop also matches the 2 hop it doesn't look like a routing loop to me. It looks like rfc1918 reuse.
>
>
> Type escape sequence to abort.
>     Tracing the route to 198.51.100.100
>
>       1 10.1.1.2 0 msec 0 msec 0 msec
>       2 198.51.100.13 0 msec 4 msec 0 msec
>       3 10.1.1.2 0 msec 4 msec 0 msec<<<<
>       4 198.51.100.5 4 msec 0 msec 4 msec
>       5 198.51.100.1 0 msec 0 msec 0 msec
>
> Section 6 references rfc2827 should probably include bcp84 and rfc3704.
>
> Your first example of a security gap is really a no worse if you use private or public addresss but you call that out so I am ok with it.
>
> NIT
> This:
> Some applications discover the outside address of
>     their local CPE to determine if that address is reserver for special
>     use.
> Should be this:
> Some applications discover the outside address of
>     their local CPE to determine if that address is reserved for special
>     use.
>
>
> When packets collide the controllers cease transmission AND wait a random time before retransmission (mostly)!
> Donald.Smith@CenturyLink.com
>
>
>> -----Original Message-----
>> From: grow-bounces@ietf.org [mailto:grow-bounces@ietf.org] On Behalf Of
>> t.petch
>> Sent: Friday, June 08, 2012 8:06 AM
>> To: Christopher Morrow; grow-chairs@tools.ietf.org; grow@ietf.org
>> Subject: Re: [GROW] WGLC: draft-ietf-grow-private-ip-sp-cores
>>
>> I would like to see this published as an RFC.
>>
>> The only discussion I see whether or not the title of 12.2 should have
>> an initial capital - I think that it should.
>>
>> Tom Petch
>>
>> ----- Original Message -----
>> From: "Christopher Morrow"<christopher.morrow@gmail.com>
>> To:<grow-chairs@tools.ietf.org>;<grow@ietf.org>
>> Sent: Tuesday, June 05, 2012 7:41 PM
>>> Folks,
>>> There's been work on the draft:
>>>     <http://tools.ietf.org/html/draft-ietf-grow-private-ip-sp-cores>
>>>
>>> I think the commenters' comments were addressed by the authors.
>>> Can we move this to WGLC now and clear that 6/19/2012 (June 19,
>> 2012).
>>> Abstract of the draft:
>>>    "The purpose of this document is to provide a discussion of the
>>>     potential problems of using private, RFC1918, or non-globally-
>>>     routable addressing within the core of an SP network.  The
>> discussion
>>>     focuses on link addresses and to a small extent loopback
>> addresses.
>>>     While many of the issues are well recognised within the ISP
>>>     community, there appears to be no document that collectively
>>>     describes the issues."
>>>
>>> Could there be some discussion on WGLC and  we'll see about  moving
>>> this along to the IESG?
>>>
>>> -chris
>>> _______________________________________________
>>> 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
> This communication is the property of CenturyLink and may contain confidential or privileged information. Unauthorized use of this communication is strictly
> prohibited and may be unlawful.  If you have received this communication
> in error, please immediately notify the sender by reply e-mail and destroy
> all copies of the communication and any attachments.
> _______________________________________________
> GROW mailing list
> GROW@ietf.org
> https://www.ietf.org/mailman/listinfo/grow
>
>


-- 



From ttauber@1-4-5.net  Wed Jun 13 05:27:13 2012
Return-Path: <ttauber@1-4-5.net>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7738B21F8593 for <grow@ietfa.amsl.com>; Wed, 13 Jun 2012 05:27:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.71
X-Spam-Level: 
X-Spam-Status: No, score=-100.71 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, J_CHICKENPOX_15=0.6, RCVD_IN_DNSWL_LOW=-1, SARE_HTML_USL_OBFU=1.666, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CrDQK1wj84rz for <grow@ietfa.amsl.com>; Wed, 13 Jun 2012 05:27:12 -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 1A73121F8534 for <grow@ietf.org>; Wed, 13 Jun 2012 05:27:12 -0700 (PDT)
Received: by obbeh20 with SMTP id eh20so974160obb.31 for <grow@ietf.org>; Wed, 13 Jun 2012 05:27:11 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=CzJ1XRtwhljCzvmVKiz69idcXqAL5Aul1KN6ccWb3kQ=; b=Nc180K3GS4gQtgrktatI0buelAbUAZJ0+p38KGgoQGsvFEq/VP2Wi8NU+7StOlHjR7 HCYS+a9s3a8zEJoo40al8aW/SJbKW01OXKRxACF5HDQv5ZZ0z7BmlQtcgV6d02DCJB82 06zO3aLg4+OL9a6f8kgQikmblDXg//59PDYdP3IyPS9e92lMOfVnDzoi1AA18OeouThF XFj+Bv72iC54s0Ya3C46vsxyZC3uR1aGM6rOlmuVWbrz1eJJxMDT8/5hyhcM5BjAMVvF Lz31hfvmOv5xlxfH3ChRGIoLMJyoGn8SXT4ldrCfrkcFHbJvaieNCVDoJwVKbr2gH/n8 VRjg==
MIME-Version: 1.0
Received: by 10.182.47.66 with SMTP id b2mr24334098obn.2.1339590431478; Wed, 13 Jun 2012 05:27:11 -0700 (PDT)
Received: by 10.76.124.204 with HTTP; Wed, 13 Jun 2012 05:27:11 -0700 (PDT)
X-Originating-IP: [24.104.152.66]
In-Reply-To: <4FD8726A.6040509@anthony-kirkham.com>
References: <CAL9jLabADdWCwDhBdaBJ4fVdk9a=OeJQYFQM4Z_+-P56cVWftw@mail.gmail.com> <01e301cd4580$208f3900$4001a8c0@gateway.2wire.net> <B01905DA0C7CDC478F42870679DF0F101105C4C714@qtdenexmbm24.AD.QINTRA.COM> <4FD8726A.6040509@anthony-kirkham.com>
Date: Wed, 13 Jun 2012 08:27:11 -0400
Message-ID: <CAGQUKceQo3neZB7TTvCHK9hkM41ftNJaHx4dRXsVuYjhJa+5eQ@mail.gmail.com>
From: Tony Tauber <ttauber@1-4-5.net>
To: tkirkham@anthony-kirkham.com
Content-Type: multipart/alternative; boundary=14dae93998cdd013e504c259b38e
X-Gm-Message-State: ALoCoQmpLQVmVWZR6vkwN/E3TNQI+1sFTzMaWGkXU58cTnE+7A+8pjUqgl/z6ZZ3nf1YFOAb3S90
Cc: "grow@ietf.org" <grow@ietf.org>, "grow-chairs@tools.ietf.org" <grow-chairs@tools.ietf.org>
Subject: Re: [GROW] WGLC: draft-ietf-grow-private-ip-sp-cores
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jun 2012 12:27:13 -0000

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

Using squat/stolen space will mean ICMP messages from the SP core wouldn't
be able to reach the legitimate address holder's network but neither would
traffic of the customers of that SP.  I don't believe that the same is true
of "private" space; so there are actually _more_ problems with the "squat"
approach.

In general, big fan, support publication.

Thanks,

Tony T.

On Wed, Jun 13, 2012 at 6:58 AM, Anthony Kirkham <
tkirkham@anthony-kirkham.com> wrote:

> Donald,
>
> Thanks for the review, I plan to do another update in the next few days,
> I'm just waiting to see if any further feedback arrives.
>
> A couple of specific comments:
>
> re - squat space. The intent was not to make recommendations on the
> practice, just to document the effects.
>
> re - 5. Unexpected interactions with some NAT implementations: What you
> say is exactly what I intended to illustrate. I will update the wording so
> its clear I'm not talking about a routing loop.
>
> Regards
> Tony K
>
>
> On 9/06/12 7:17 AM, Smith, Donald wrote:
>
>> There is a mention of "squat" space that doesn't make any recommendations
>> as to use or not.
>>
>> I can understand not expressing an opinion on the rfc1918/private space
>> shouldn't this state that squating is bad?
>> "This effect in itself is often not a problem.  However, if anti-
>>    spoofing controls are applied at network perimeters, then responses
>>    returned from hops with private IP addresses will be dropped."
>>
>> Any rfc1918 filtering mechinisim will cause this issue not just bcp38
>> type anti-spoofing.
>> Firewalls, junipers and many platforms drop rfc1918 space but not as part
>> of bcp38 .
>> BTW BCP84 ala rfc3704 is an update/addition to bcp38 you should probably
>> add them to this reference.
>>
>>
>> And for consistecy I recommend using an expression such as "any rfc1918
>> or bogon filtering..."
>>
>> Under section 4 the author says urpf or ingress filtering.
>> "If the router's interface address is a
>>    private IP address, then this ICMP reply packet may be discarded due
>>    to uRPF or ingress filtering, thereby causing the PMTUD mechanism to
>>    fail."
>>
>> Under
>> 5. Unexpected interactions with some NAT implementations
>> The first section works. As stated it might confuse someone but honestly
>> unless the 4th hop also matches the 2 hop it doesn't look like a routing
>> loop to me. It looks like rfc1918 reuse.
>>
>>
>> Type escape sequence to abort.
>>    Tracing the route to 198.51.100.100
>>
>>      1 10.1.1.2 0 msec 0 msec 0 msec
>>      2 198.51.100.13 0 msec 4 msec 0 msec
>>      3 10.1.1.2 0 msec 4 msec 0 msec<<<<
>>      4 198.51.100.5 4 msec 0 msec 4 msec
>>      5 198.51.100.1 0 msec 0 msec 0 msec
>>
>> Section 6 references rfc2827 should probably include bcp84 and rfc3704.
>>
>> Your first example of a security gap is really a no worse if you use
>> private or public addresss but you call that out so I am ok with it.
>>
>> NIT
>> This:
>> Some applications discover the outside address of
>>    their local CPE to determine if that address is reserver for special
>>    use.
>> Should be this:
>> Some applications discover the outside address of
>>    their local CPE to determine if that address is reserved for special
>>    use.
>>
>>
>> When packets collide the controllers cease transmission AND wait a random
>> time before retransmission (mostly)!
>> Donald.Smith@CenturyLink.com
>>
>>
>>  -----Original Message-----
>>> From: grow-bounces@ietf.org [mailto:grow-bounces@ietf.org] On Behalf Of
>>> t.petch
>>> Sent: Friday, June 08, 2012 8:06 AM
>>> To: Christopher Morrow; grow-chairs@tools.ietf.org; grow@ietf.org
>>> Subject: Re: [GROW] WGLC: draft-ietf-grow-private-ip-sp-**cores
>>>
>>> I would like to see this published as an RFC.
>>>
>>> The only discussion I see whether or not the title of 12.2 should have
>>> an initial capital - I think that it should.
>>>
>>> Tom Petch
>>>
>>> ----- Original Message -----
>>> From: "Christopher Morrow"<christopher.morrow@**gmail.com<christopher.morrow@gmail.com>
>>> >
>>> To:<grow-chairs@tools.ietf.org**>;<grow@ietf.org>
>>> Sent: Tuesday, June 05, 2012 7:41 PM
>>>
>>>> Folks,
>>>> There's been work on the draft:
>>>>    <http://tools.ietf.org/html/**draft-ietf-grow-private-ip-sp-**cores<http://tools.ietf.org/html/draft-ietf-grow-private-ip-sp-cores>
>>>> >
>>>>
>>>> I think the commenters' comments were addressed by the authors.
>>>> Can we move this to WGLC now and clear that 6/19/2012 (June 19,
>>>>
>>> 2012).
>>>
>>>> Abstract of the draft:
>>>>   "The purpose of this document is to provide a discussion of the
>>>>    potential problems of using private, RFC1918, or non-globally-
>>>>    routable addressing within the core of an SP network.  The
>>>>
>>> discussion
>>>
>>>>    focuses on link addresses and to a small extent loopback
>>>>
>>> addresses.
>>>
>>>>    While many of the issues are well recognised within the ISP
>>>>    community, there appears to be no document that collectively
>>>>    describes the issues."
>>>>
>>>> Could there be some discussion on WGLC and  we'll see about  moving
>>>> this along to the IESG?
>>>>
>>>> -chris
>>>> ______________________________**_________________
>>>> GROW mailing list
>>>> GROW@ietf.org
>>>> https://www.ietf.org/mailman/**listinfo/grow<https://www.ietf.org/mailman/listinfo/grow>
>>>>
>>>>
>>> ______________________________**_________________
>>> GROW mailing list
>>> GROW@ietf.org
>>> https://www.ietf.org/mailman/**listinfo/grow<https://www.ietf.org/mailman/listinfo/grow>
>>>
>> This communication is the property of CenturyLink and may contain
>> confidential or privileged information. Unauthorized use of this
>> communication is strictly
>> prohibited and may be unlawful.  If you have received this communication
>> in error, please immediately notify the sender by reply e-mail and destroy
>> all copies of the communication and any attachments.
>> ______________________________**_________________
>> GROW mailing list
>> GROW@ietf.org
>> https://www.ietf.org/mailman/**listinfo/grow<https://www.ietf.org/mailman/listinfo/grow>
>>
>>
>>
>
> --
>
>
> ______________________________**_________________
> GROW mailing list
> GROW@ietf.org
> https://www.ietf.org/mailman/**listinfo/grow<https://www.ietf.org/mailman/listinfo/grow>
>

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

Using squat/stolen space will mean ICMP messages from the SP core wouldn&#3=
9;t be able to reach the legitimate address holder&#39;s network but neithe=
r would traffic of the customers of that SP.=A0 I don&#39;t believe that th=
e same is true of &quot;private&quot; space; so there are actually _more_ p=
roblems with the &quot;squat&quot; approach.<br>
<br>In general, big fan, support publication.<br><br>Thanks,<br><br>Tony T.=
<br><br><div class=3D"gmail_quote">On Wed, Jun 13, 2012 at 6:58 AM, Anthony=
 Kirkham <span dir=3D"ltr">&lt;<a href=3D"mailto:tkirkham@anthony-kirkham.c=
om" target=3D"_blank">tkirkham@anthony-kirkham.com</a>&gt;</span> wrote:<br=
>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Donald,<br>
<br>
Thanks for the review, I plan to do another update in the next few days, I&=
#39;m just waiting to see if any further feedback arrives.<br>
<br>
A couple of specific comments:<br>
<br>
re - squat space. The intent was not to make recommendations on the practic=
e, just to document the effects.<br>
<br>
re - 5. Unexpected interactions with some NAT implementations: What you say=
 is exactly what I intended to illustrate. I will update the wording so its=
 clear I&#39;m not talking about a routing loop.<br>
<br>
Regards<br>
Tony K<div><div class=3D"h5"><br>
<br>
On 9/06/12 7:17 AM, Smith, Donald wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
There is a mention of &quot;squat&quot; space that doesn&#39;t make any rec=
ommendations as to use or not.<br>
<br>
I can understand not expressing an opinion on the rfc1918/private space sho=
uldn&#39;t this state that squating is bad?<br>
&quot;This effect in itself is often not a problem. =A0However, if anti-<br=
>
 =A0 =A0spoofing controls are applied at network perimeters, then responses=
<br>
 =A0 =A0returned from hops with private IP addresses will be dropped.&quot;=
<br>
<br>
Any rfc1918 filtering mechinisim will cause this issue not just bcp38 type =
anti-spoofing.<br>
Firewalls, junipers and many platforms drop rfc1918 space but not as part o=
f bcp38 .<br>
BTW BCP84 ala rfc3704 is an update/addition to bcp38 you should probably ad=
d them to this reference.<br>
<br>
<br>
And for consistecy I recommend using an expression such as &quot;any rfc191=
8 or bogon filtering...&quot;<br>
<br>
Under section 4 the author says urpf or ingress filtering.<br>
&quot;If the router&#39;s interface address is a<br>
 =A0 =A0private IP address, then this ICMP reply packet may be discarded du=
e<br>
 =A0 =A0to uRPF or ingress filtering, thereby causing the PMTUD mechanism t=
o<br>
 =A0 =A0fail.&quot;<br>
<br>
Under<br>
5. Unexpected interactions with some NAT implementations<br>
The first section works. As stated it might confuse someone but honestly un=
less the 4th hop also matches the 2 hop it doesn&#39;t look like a routing =
loop to me. It looks like rfc1918 reuse.<br>
<br>
<br>
Type escape sequence to abort.<br>
 =A0 =A0Tracing the route to 198.51.100.100<br>
<br>
 =A0 =A0 =A01 10.1.1.2 0 msec 0 msec 0 msec<br>
 =A0 =A0 =A02 198.51.100.13 0 msec 4 msec 0 msec<br>
 =A0 =A0 =A0<a href=3D"tel:3%2010.1.1.2%200" value=3D"+13101120" target=3D"=
_blank">3 10.1.1.2 0</a> msec 4 msec 0 msec&lt;&lt;&lt;&lt;<br>
 =A0 =A0 =A0<a href=3D"tel:4%20198.51.100.5" value=3D"+14198511005" target=
=3D"_blank">4 198.51.100.5</a> 4 msec 0 msec 4 msec<br>
 =A0 =A0 =A0<a href=3D"tel:5%20198.51.100.1" value=3D"+15198511001" target=
=3D"_blank">5 198.51.100.1</a> 0 msec 0 msec 0 msec<br>
<br>
Section 6 references rfc2827 should probably include bcp84 and rfc3704.<br>
<br>
Your first example of a security gap is really a no worse if you use privat=
e or public addresss but you call that out so I am ok with it.<br>
<br>
NIT<br>
This:<br>
Some applications discover the outside address of<br>
 =A0 =A0their local CPE to determine if that address is reserver for specia=
l<br>
 =A0 =A0use.<br>
Should be this:<br>
Some applications discover the outside address of<br>
 =A0 =A0their local CPE to determine if that address is reserved for specia=
l<br>
 =A0 =A0use.<br>
<br>
<br>
When packets collide the controllers cease transmission AND wait a random t=
ime before retransmission (mostly)!<br>
Donald.Smith@CenturyLink.com<br>
<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
-----Original Message-----<br>
From: <a href=3D"mailto:grow-bounces@ietf.org" target=3D"_blank">grow-bounc=
es@ietf.org</a> [mailto:<a href=3D"mailto:grow-bounces@ietf.org" target=3D"=
_blank">grow-bounces@ietf.org</a>] On Behalf Of<br>
t.petch<br>
Sent: Friday, June 08, 2012 8:06 AM<br>
To: Christopher Morrow; <a href=3D"mailto:grow-chairs@tools.ietf.org" targe=
t=3D"_blank">grow-chairs@tools.ietf.org</a>; <a href=3D"mailto:grow@ietf.or=
g" target=3D"_blank">grow@ietf.org</a><br>
Subject: Re: [GROW] WGLC: draft-ietf-grow-private-ip-sp-<u></u>cores<br>
<br>
I would like to see this published as an RFC.<br>
<br>
The only discussion I see whether or not the title of 12.2 should have<br>
an initial capital - I think that it should.<br>
<br>
Tom Petch<br>
<br>
----- Original Message -----<br>
From: &quot;Christopher Morrow&quot;&lt;<a href=3D"mailto:christopher.morro=
w@gmail.com" target=3D"_blank">christopher.morrow@<u></u>gmail.com</a>&gt;<=
br>
To:&lt;<a href=3D"mailto:grow-chairs@tools.ietf.org" target=3D"_blank">grow=
-chairs@tools.ietf.org</a><u></u>&gt;;&lt;<a href=3D"mailto:grow@ietf.org" =
target=3D"_blank">grow@ietf.org</a>&gt;<br>
Sent: Tuesday, June 05, 2012 7:41 PM<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Folks,<br>
There&#39;s been work on the draft:<br>
 =A0 =A0&lt;<a href=3D"http://tools.ietf.org/html/draft-ietf-grow-private-i=
p-sp-cores" target=3D"_blank">http://tools.ietf.org/html/<u></u>draft-ietf-=
grow-private-ip-sp-<u></u>cores</a>&gt;<br>
<br>
I think the commenters&#39; comments were addressed by the authors.<br>
Can we move this to WGLC now and clear that 6/19/2012 (June 19,<br>
</blockquote>
2012).<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Abstract of the draft:<br>
 =A0 &quot;The purpose of this document is to provide a discussion of the<b=
r>
 =A0 =A0potential problems of using private, RFC1918, or non-globally-<br>
 =A0 =A0routable addressing within the core of an SP network. =A0The<br>
</blockquote>
discussion<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
 =A0 =A0focuses on link addresses and to a small extent loopback<br>
</blockquote>
addresses.<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
 =A0 =A0While many of the issues are well recognised within the ISP<br>
 =A0 =A0community, there appears to be no document that collectively<br>
 =A0 =A0describes the issues.&quot;<br>
<br>
Could there be some discussion on WGLC and =A0we&#39;ll see about =A0moving=
<br>
this along to the IESG?<br>
<br>
-chris<br>
______________________________<u></u>_________________<br>
GROW mailing list<br>
<a href=3D"mailto:GROW@ietf.org" target=3D"_blank">GROW@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/grow" target=3D"_blank">ht=
tps://www.ietf.org/mailman/<u></u>listinfo/grow</a><br>
<br>
</blockquote>
<br>
______________________________<u></u>_________________<br>
GROW mailing list<br>
<a href=3D"mailto:GROW@ietf.org" target=3D"_blank">GROW@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/grow" target=3D"_blank">ht=
tps://www.ietf.org/mailman/<u></u>listinfo/grow</a><br>
</blockquote>
This communication is the property of CenturyLink and may contain confident=
ial or privileged information. Unauthorized use of this communication is st=
rictly<br>
prohibited and may be unlawful. =A0If you have received this communication<=
br>
in error, please immediately notify the sender by reply e-mail and destroy<=
br>
all copies of the communication and any attachments.<br>
______________________________<u></u>_________________<br>
GROW mailing list<br>
<a href=3D"mailto:GROW@ietf.org" target=3D"_blank">GROW@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/grow" target=3D"_blank">ht=
tps://www.ietf.org/mailman/<u></u>listinfo/grow</a><br>
<br>
<br>
</blockquote>
<br>
<br></div></div>
-- <br><div class=3D"HOEnZb"><div class=3D"h5">
<br>
<br>
______________________________<u></u>_________________<br>
GROW mailing list<br>
<a href=3D"mailto:GROW@ietf.org" target=3D"_blank">GROW@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/grow" target=3D"_blank">ht=
tps://www.ietf.org/mailman/<u></u>listinfo/grow</a><br>
</div></div></blockquote></div><br>

--14dae93998cdd013e504c259b38e--

From Donald.Smith@CenturyLink.com  Wed Jun 13 06:56:36 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 BB7ED21F85AE for <grow@ietfa.amsl.com>; Wed, 13 Jun 2012 06:56:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_15=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id faXrnVhnI5zY for <grow@ietfa.amsl.com>; Wed, 13 Jun 2012 06:56:35 -0700 (PDT)
Received: from suomp64i.qwest.com (suomp64i.qwest.com [155.70.16.237]) by ietfa.amsl.com (Postfix) with ESMTP id A3AD021F858D for <grow@ietf.org>; Wed, 13 Jun 2012 06:56:35 -0700 (PDT)
Received: from lxdenvmpc030.qintra.com (lxdenvmpc030.qintra.com [10.1.51.30]) by suomp64i.qwest.com (8.14.4/8.14.4) with ESMTP id q5DDuV3J023490 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 13 Jun 2012 08:56:31 -0500 (CDT)
Received: from lxdenvmpc030.qintra.com (unknown [127.0.0.1]) by IMSA (Postfix) with ESMTP id 098441E0062; Wed, 13 Jun 2012 07:56:26 -0600 (MDT)
Received: from sudnp796.qintra.com (unknown [151.119.91.93]) by lxdenvmpc030.qintra.com (Postfix) with ESMTP id D4EB51E0035; Wed, 13 Jun 2012 07:56:25 -0600 (MDT)
Received: from sudnp796.qintra.com (localhost [127.0.0.1]) by sudnp796.qintra.com (8.14.4/8.14.4) with ESMTP id q5DDuPkv027792; Wed, 13 Jun 2012 07:56:25 -0600 (MDT)
Received: from qtdenexhtm20.AD.QINTRA.COM (qtdenexhtm20.ad.qintra.com [151.119.91.229]) by sudnp796.qintra.com (8.14.4/8.14.4) with ESMTP id q5DDuOjq027776 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=FAIL); Wed, 13 Jun 2012 07:56:25 -0600 (MDT)
Received: from qtdenexmbm24.AD.QINTRA.COM ([151.119.91.226]) by qtdenexhtm20.AD.QINTRA.COM ([151.119.91.229]) with mapi; Wed, 13 Jun 2012 07:56:24 -0600
From: "Smith, Donald" <Donald.Smith@CenturyLink.com>
To: "tkirkham@anthony-kirkham.com" <tkirkham@anthony-kirkham.com>
Content-Class: urn:content-classes:message
Date: Wed, 13 Jun 2012 07:56:41 -0600
Thread-Topic: [GROW] WGLC: draft-ietf-grow-private-ip-sp-cores
Thread-Index: Ac1JU4t9/JEs43RjTC+hyscZ7mpb2gAGDG0vAAAntvQ=
Message-ID: <1DD84719-A84B-4FFE-ABD6-39BDA7062E08@mimectl>
References: <CAL9jLabADdWCwDhBdaBJ4fVdk9a=OeJQYFQM4Z_+-P56cVWftw@mail.gmail.com> <01e301cd4580$208f3900$4001a8c0@gateway.2wire.net> <B01905DA0C7CDC478F42870679DF0F101105C4C714@qtdenexmbm24.AD.QINTRA.COM>, <4FD8726A.6040509@anthony-kirkham.com>
In-Reply-To: <4FD8726A.6040509@anthony-kirkham.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
x-mimectl: Produced By Microsoft Exchange V8.3.105.0
Content-Type: multipart/alternative; boundary="_000_1DD84719A84B4FFEABD639BDA7062E08mimectl_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "'grow@ietf.org'" <grow@ietf.org>, "'grow-chairs@tools.ietf.org'" <grow-chairs@tools.ietf.org>
Subject: Re: [GROW] WGLC: draft-ietf-grow-private-ip-sp-cores
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jun 2012 13:56:36 -0000

--_000_1DD84719A84B4FFEABD639BDA7062E08mimectl_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Your welcome. I understand not taking a stance on use of priv addresses in =
the core. I would rather either pull the mention of squat space or recommen=
d against it or explain why it is different then the use of private space. =
There are elements where that is much worse then the use of rfc1918 space.


(coffee !=3D sleep) & (!coffee =3D=3D sleep)
 Donald.Smith@qwest.com<mailto:Donald.Smith@qwest.com>
________________________________
From: Anthony Kirkham [tkirkham@anthony-kirkham.com]
Sent: Wednesday, June 13, 2012 4:58 AM
To: Smith, Donald
Cc: 't.petch'; 'Christopher Morrow'; 'grow-chairs@tools.ietf.org'; 'grow@ie=
tf.org'
Subject: Re: [GROW] WGLC: draft-ietf-grow-private-ip-sp-cores

Donald,

Thanks for the review, I plan to do another update in the next few days,
I'm just waiting to see if any further feedback arrives.

A couple of specific comments:

re - squat space. The intent was not to make recommendations on the
practice, just to document the effects.

re - 5. Unexpected interactions with some NAT implementations: What you
say is exactly what I intended to illustrate. I will update the wording
so its clear I'm not talking about a routing loop.

Regards
Tony K

On 9/06/12 7:17 AM, Smith, Donald wrote:
> There is a mention of "squat" space that doesn't make any recommendations=
 as to use or not.
>
> I can understand not expressing an opinion on the rfc1918/private space s=
houldn't this state that squating is bad?
> "This effect in itself is often not a problem.  However, if anti-
>     spoofing controls are applied at network perimeters, then responses
>     returned from hops with private IP addresses will be dropped."
>
> Any rfc1918 filtering mechinisim will cause this issue not just bcp38 typ=
e anti-spoofing.
> Firewalls, junipers and many platforms drop rfc1918 space but not as part=
 of bcp38 .
> BTW BCP84 ala rfc3704 is an update/addition to bcp38 you should probably =
add them to this reference.
>
>
> And for consistecy I recommend using an expression such as "any rfc1918 o=
r bogon filtering..."
>
> Under section 4 the author says urpf or ingress filtering.
> "If the router's interface address is a
>     private IP address, then this ICMP reply packet may be discarded due
>     to uRPF or ingress filtering, thereby causing the PMTUD mechanism to
>     fail."
>
> Under
> 5. Unexpected interactions with some NAT implementations
> The first section works. As stated it might confuse someone but honestly =
unless the 4th hop also matches the 2 hop it doesn't look like a routing lo=
op to me. It looks like rfc1918 reuse.
>
>
> Type escape sequence to abort.
>     Tracing the route to 198.51.100.100
>
>       1 10.1.1.2 0 msec 0 msec 0 msec
>       2 198.51.100.13 0 msec 4 msec 0 msec
>       3 10.1.1.2 0 msec 4 msec 0 msec<<<<
>       4 198.51.100.5 4 msec 0 msec 4 msec
>       5 198.51.100.1 0 msec 0 msec 0 msec
>
> Section 6 references rfc2827 should probably include bcp84 and rfc3704.
>
> Your first example of a security gap is really a no worse if you use priv=
ate or public addresss but you call that out so I am ok with it.
>
> NIT
> This:
> Some applications discover the outside address of
>     their local CPE to determine if that address is reserver for special
>     use.
> Should be this:
> Some applications discover the outside address of
>     their local CPE to determine if that address is reserved for special
>     use.
>
>
> When packets collide the controllers cease transmission AND wait a random=
 time before retransmission (mostly)!
> Donald.Smith@CenturyLink.com
>
>
>> -----Original Message-----
>> From: grow-bounces@ietf.org [mailto:grow-bounces@ietf.org] On Behalf Of
>> t.petch
>> Sent: Friday, June 08, 2012 8:06 AM
>> To: Christopher Morrow; grow-chairs@tools.ietf.org; grow@ietf.org
>> Subject: Re: [GROW] WGLC: draft-ietf-grow-private-ip-sp-cores
>>
>> I would like to see this published as an RFC.
>>
>> The only discussion I see whether or not the title of 12.2 should have
>> an initial capital - I think that it should.
>>
>> Tom Petch
>>
>> ----- Original Message -----
>> From: "Christopher Morrow"<christopher.morrow@gmail.com>
>> To:<grow-chairs@tools.ietf.org>;<grow@ietf.org>
>> Sent: Tuesday, June 05, 2012 7:41 PM
>>> Folks,
>>> There's been work on the draft:
>>>     <http://tools.ietf.org/html/draft-ietf-grow-private-ip-sp-cores>
>>>
>>> I think the commenters' comments were addressed by the authors.
>>> Can we move this to WGLC now and clear that 6/19/2012 (June 19,
>> 2012).
>>> Abstract of the draft:
>>>    "The purpose of this document is to provide a discussion of the
>>>     potential problems of using private, RFC1918, or non-globally-
>>>     routable addressing within the core of an SP network.  The
>> discussion
>>>     focuses on link addresses and to a small extent loopback
>> addresses.
>>>     While many of the issues are well recognised within the ISP
>>>     community, there appears to be no document that collectively
>>>     describes the issues."
>>>
>>> Could there be some discussion on WGLC and  we'll see about  moving
>>> this along to the IESG?
>>>
>>> -chris
>>> _______________________________________________
>>> 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
> This communication is the property of CenturyLink and may contain confide=
ntial or privileged information. Unauthorized use of this communication is =
strictly
> prohibited and may be unlawful.  If you have received this communication
> in error, please immediately notify the sender by reply e-mail and destro=
y
> all copies of the communication and any attachments.
> _______________________________________________
> GROW mailing list
> GROW@ietf.org
> https://www.ietf.org/mailman/listinfo/grow
>
>


--



________________________________
This communication is the property of CenturyLink and may contain confident=
ial or privileged information. Unauthorized use of this communication is st=
rictly
prohibited and may be unlawful. If you have received this communication
in error, please immediately notify the sender by reply e-mail and destroy
all copies of the communication and any attachments.

--_000_1DD84719A84B4FFEABD639BDA7062E08mimectl_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html dir=3D"ltr">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<style>.EmailQuote {
	BORDER-LEFT: #800000 2px solid; PADDING-LEFT: 4pt; MARGIN-LEFT: 1pt
}
</style><style title=3D"owaParaStyle"><!--P {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
--></style>
</head>
<body ocsi=3D"x">
<div dir=3D"ltr"><font color=3D"#000000" size=3D"2" face=3D"Tahoma">Your we=
lcome. I understand not taking a stance on use of&nbsp;priv<a target=3D"_bl=
ank"></a> addresses in the core. I would rather either pull the mention of =
squat space or recommend against it or explain
 why it is different then the use of private space. There are elements wher=
e that is much worse then the use of&nbsp;rfc1918<a target=3D"_blank"></a> =
space.</font></div>
<div dir=3D"ltr"><font size=3D"2" face=3D"tahoma"></font>&nbsp;</div>
<div dir=3D"ltr"><font size=3D"2" face=3D"tahoma"></font>&nbsp;</div>
<div>
<div><font size=3D"2">(coffee !=3D sleep) &amp; (!coffee =3D=3D sleep)<br>
&nbsp;<a href=3D"mailto:Donald.Smith@qwest.com" target=3D"_blank">Donald.Sm=
ith@qwest.com</a><a target=3D"_blank"></a></font></div>
</div>
<div style=3D"DIRECTION: ltr" id=3D"divRpF464120">
<hr tabindex=3D"-1">
<font color=3D"#000000" size=3D"2" face=3D"Tahoma"><b>From:</b> Anthony Kir=
kham [tkirkham@anthony-kirkham.com]<br>
<b>Sent:</b> Wednesday, June 13, 2012 4:58 AM<br>
<b>To:</b> Smith, Donald<br>
<b>Cc:</b> 't.petch'; 'Christopher Morrow'; 'grow-chairs@tools.ietf.org'; '=
grow@ietf.org'<br>
<b>Subject:</b> Re: [GROW] WGLC: draft-ietf-grow-private-ip-sp-cores<br>
</font><br>
</div>
<div></div>
<font size=3D"2">
<div class=3D"PlainText">Donald,<br>
<br>
Thanks for the review, I plan to do another update in the next few days, <b=
r>
I'm just waiting to see if any further feedback arrives.<br>
<br>
A couple of specific comments:<br>
<br>
re - squat space. The intent was not to make recommendations on the <br>
practice, just to document the effects.<br>
<br>
re - 5. Unexpected interactions with some NAT implementations: What you <br=
>
say is exactly what I intended to illustrate. I will update the wording <br=
>
so its clear I'm not talking about a routing loop.<br>
<br>
Regards<br>
Tony K<br>
<br>
On 9/06/12 7:17 AM, Smith, Donald wrote:<br>
&gt; There is a mention of &quot;squat&quot; space that doesn't make any re=
commendations as to use or not.<br>
&gt;<br>
&gt; I can understand not expressing an opinion on the rfc1918/private spac=
e shouldn't this state that squating is bad?<br>
&gt; &quot;This effect in itself is often not a problem.&nbsp; However, if =
anti-<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; spoofing controls are applied at network perim=
eters, then responses<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; returned from hops with private IP addresses w=
ill be dropped.&quot;<br>
&gt;<br>
&gt; Any rfc1918 filtering mechinisim will cause this issue not just bcp38 =
type anti-spoofing.<br>
&gt; Firewalls, junipers and many platforms drop rfc1918 space but not as p=
art of bcp38 .<br>
&gt; BTW BCP84 ala rfc3704 is an update/addition to bcp38 you should probab=
ly add them to this reference.<br>
&gt;<br>
&gt;<br>
&gt; And for consistecy I recommend using an expression such as &quot;any r=
fc1918 or bogon filtering...&quot;<br>
&gt;<br>
&gt; Under section 4 the author says urpf or ingress filtering.<br>
&gt; &quot;If the router's interface address is a<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; private IP address, then this ICMP reply packe=
t may be discarded due<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; to uRPF or ingress filtering, thereby causing =
the PMTUD mechanism to<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; fail.&quot;<br>
&gt;<br>
&gt; Under<br>
&gt; 5. Unexpected interactions with some NAT implementations<br>
&gt; The first section works. As stated it might confuse someone but honest=
ly unless the 4th hop also matches the 2 hop it doesn't look like a routing=
 loop to me. It looks like rfc1918 reuse.<br>
&gt;<br>
&gt;<br>
&gt; Type escape sequence to abort.<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; Tracing the route to 198.51.100.100<br>
&gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1 10.1.1.2 0 msec 0 msec 0 msec<br=
>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2 198.51.100.13 0 msec 4 msec 0 ms=
ec<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 3 10.1.1.2 0 msec 4 msec 0 msec&lt=
;&lt;&lt;&lt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 4 198.51.100.5 4 msec 0 msec 4 mse=
c<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 5 198.51.100.1 0 msec 0 msec 0 mse=
c<br>
&gt;<br>
&gt; Section 6 references rfc2827 should probably include bcp84 and rfc3704=
.<br>
&gt;<br>
&gt; Your first example of a security gap is really a no worse if you use p=
rivate or public addresss but you call that out so I am ok with it.<br>
&gt;<br>
&gt; NIT<br>
&gt; This:<br>
&gt; Some applications discover the outside address of<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; their local CPE to determine if that address i=
s reserver for special<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; use.<br>
&gt; Should be this:<br>
&gt; Some applications discover the outside address of<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; their local CPE to determine if that address i=
s reserved for special<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; use.<br>
&gt;<br>
&gt;<br>
&gt; When packets collide the controllers cease transmission AND wait a ran=
dom time before retransmission (mostly)!<br>
&gt; Donald.Smith@CenturyLink.com<br>
&gt;<br>
&gt;<br>
&gt;&gt; -----Original Message-----<br>
&gt;&gt; From: grow-bounces@ietf.org [<a href=3D"mailto:grow-bounces@ietf.o=
rg" target=3D"_blank">mailto:grow-bounces@ietf.org</a>] On Behalf Of<br>
&gt;&gt; t.petch<br>
&gt;&gt; Sent: Friday, June 08, 2012 8:06 AM<br>
&gt;&gt; To: Christopher Morrow; grow-chairs@tools.ietf.org; grow@ietf.org<=
br>
&gt;&gt; Subject: Re: [GROW] WGLC: draft-ietf-grow-private-ip-sp-cores<br>
&gt;&gt;<br>
&gt;&gt; I would like to see this published as an RFC.<br>
&gt;&gt;<br>
&gt;&gt; The only discussion I see whether or not the title of 12.2 should =
have<br>
&gt;&gt; an initial capital - I think that it should.<br>
&gt;&gt;<br>
&gt;&gt; Tom Petch<br>
&gt;&gt;<br>
&gt;&gt; ----- Original Message -----<br>
&gt;&gt; From: &quot;Christopher Morrow&quot;&lt;christopher.morrow@gmail.c=
om&gt;<br>
&gt;&gt; To:&lt;grow-chairs@tools.ietf.org&gt;;&lt;grow@ietf.org&gt;<br>
&gt;&gt; Sent: Tuesday, June 05, 2012 7:41 PM<br>
&gt;&gt;&gt; Folks,<br>
&gt;&gt;&gt; There's been work on the draft:<br>
&gt;&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; &lt;<a href=3D"http://tools.ietf.org/h=
tml/draft-ietf-grow-private-ip-sp-cores" target=3D"_blank">http://tools.iet=
f.org/html/draft-ietf-grow-private-ip-sp-cores</a>&gt;<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; I think the commenters' comments were addressed by the authors=
.<br>
&gt;&gt;&gt; Can we move this to WGLC now and clear that 6/19/2012 (June 19=
,<br>
&gt;&gt; 2012).<br>
&gt;&gt;&gt; Abstract of the draft:<br>
&gt;&gt;&gt;&nbsp;&nbsp;&nbsp; &quot;The purpose of this document is to pro=
vide a discussion of the<br>
&gt;&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; potential problems of using private, R=
FC1918, or non-globally-<br>
&gt;&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; routable addressing within the core of=
 an SP network.&nbsp; The<br>
&gt;&gt; discussion<br>
&gt;&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; focuses on link addresses and to a sma=
ll extent loopback<br>
&gt;&gt; addresses.<br>
&gt;&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; While many of the issues are well reco=
gnised within the ISP<br>
&gt;&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; community, there appears to be no docu=
ment that collectively<br>
&gt;&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; describes the issues.&quot;<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Could there be some discussion on WGLC and&nbsp; we'll see abo=
ut&nbsp; moving<br>
&gt;&gt;&gt; this along to the IESG?<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; -chris<br>
&gt;&gt;&gt; _______________________________________________<br>
&gt;&gt;&gt; GROW mailing list<br>
&gt;&gt;&gt; GROW@ietf.org<br>
&gt;&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/grow" target=
=3D"_blank">https://www.ietf.org/mailman/listinfo/grow</a><br>
&gt;&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; _______________________________________________<br>
&gt;&gt; GROW mailing list<br>
&gt;&gt; GROW@ietf.org<br>
&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/grow" target=3D"_=
blank">https://www.ietf.org/mailman/listinfo/grow</a><br>
&gt; This communication is the property of CenturyLink and may contain conf=
idential or privileged information. Unauthorized use of this communication =
is strictly<br>
&gt; prohibited and may be unlawful.&nbsp; If you have received this commun=
ication<br>
&gt; in error, please immediately notify the sender by reply e-mail and des=
troy<br>
&gt; all copies of the communication and any attachments.<br>
&gt; _______________________________________________<br>
&gt; GROW mailing list<br>
&gt; GROW@ietf.org<br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/grow" target=3D"_blan=
k">https://www.ietf.org/mailman/listinfo/grow</a><br>
&gt;<br>
&gt;<br>
<br>
<br>
-- <br>
<br>
<br>
</div>
</font><br>
<hr>
<font face=3D"Arial" color=3D"Gray" size=3D"1">This communication is the pr=
operty of CenturyLink and may contain confidential or privileged informatio=
n. Unauthorized use of this communication is strictly<br>
prohibited and may be unlawful. If you have received this communication<br>
in error, please immediately notify the sender by reply e-mail and destroy<=
br>
all copies of the communication and any attachments.<br>
</font>
</body>
</html>

--_000_1DD84719A84B4FFEABD639BDA7062E08mimectl_--

From tom@someaddress.net  Wed Jun 13 08:24:45 2012
Return-Path: <tom@someaddress.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 7211D21F850B for <grow@ietfa.amsl.com>; Wed, 13 Jun 2012 08:24:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.372
X-Spam-Level: 
X-Spam-Status: No, score=-2.372 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SARE_SUB_OBFU_Q1=0.227]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nOo3-St+GT08 for <grow@ietfa.amsl.com>; Wed, 13 Jun 2012 08:24:45 -0700 (PDT)
Received: from zinc.someaddress.net (zinc.someaddress.net [82.152.104.99]) by ietfa.amsl.com (Postfix) with ESMTP id E3A6021F8550 for <grow@ietf.org>; Wed, 13 Jun 2012 08:24:38 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by zinc.someaddress.net (Postfix) with ESMTPS id 55C403C001676; Wed, 13 Jun 2012 16:24:06 +0100 (BST)
Date: Wed, 13 Jun 2012 16:24:06 +0100 (BST)
From: Tom Hodgson <tom@someaddress.net>
X-X-Sender: tom@zinc
To: Christopher Morrow <christopher.morrow@gmail.com>
In-Reply-To: <CAL9jLabOs02rOti4tezaZiHyiOD2f9vAhsoE9c-afFb4J1xYXQ@mail.gmail.com>
Message-ID: <alpine.DEB.2.00.1206122333490.12509@zinc>
References: <CAL9jLabOs02rOti4tezaZiHyiOD2f9vAhsoE9c-afFb4J1xYXQ@mail.gmail.com>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
Cc: "grow@ietf.org grow@ietf.org" <grow@ietf.org>, grow-chairs@tools.ietf.org
Subject: Re: [GROW] WGLC: draft-ietf-grow-ops-reqs-for-bgp-error-handling-04
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jun 2012 15:24:45 -0000

On Mon, 11 Jun 2012, Christopher Morrow wrote:
> Hello GROW-WG folk,
> Please take this message as the start of a 2 week, ending 6/25/2012
> (June 25, 2012) WGLC for the subject draft, link to current version:
>  <http://www.ietf.org/internet-drafts/draft-ietf-grow-ops-reqs-for-bgp-error-handling-04.txt>
>

I have reviewed the latest diffs, and the draft in general and agree that 
this represents a useful documentation of the operator requirements and 
should proceed to the next stage.

-- 
Tom Hodgson
tom@someaddress.net

From Donald.Smith@CenturyLink.com  Wed Jun 13 09:18:35 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 DF5AD21F85C2 for <grow@ietfa.amsl.com>; Wed, 13 Jun 2012 09:18:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[AWL=0.001,  BAYES_00=-2.599, J_CHICKENPOX_15=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FcwWBHZjOUQJ for <grow@ietfa.amsl.com>; Wed, 13 Jun 2012 09:18:35 -0700 (PDT)
Received: from suomp64i.qwest.com (suomp64i.qwest.com [155.70.16.237]) by ietfa.amsl.com (Postfix) with ESMTP id 098E621F85CF for <grow@ietf.org>; Wed, 13 Jun 2012 09:18:34 -0700 (PDT)
Received: from lxomavmpc030.qintra.com (lxomavmpc030.qintra.com [151.117.207.30]) by suomp64i.qwest.com (8.14.4/8.14.4) with ESMTP id q5DGIWdK015943 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 13 Jun 2012 11:18:32 -0500 (CDT)
Received: from lxomavmpc030.qintra.com (unknown [127.0.0.1]) by IMSA (Postfix) with ESMTP id 55AE91E0077; Wed, 13 Jun 2012 11:18:27 -0500 (CDT)
Received: from suomp60i.qintra.com (unknown [10.6.10.61]) by lxomavmpc030.qintra.com (Postfix) with ESMTP id 38D0B1E006F; Wed, 13 Jun 2012 11:18:27 -0500 (CDT)
Received: from suomp60i.qintra.com (localhost [127.0.0.1]) by suomp60i.qintra.com (8.14.4/8.14.4) with ESMTP id q5DGIQUg023596; Wed, 13 Jun 2012 11:18:26 -0500 (CDT)
Received: from qtdenexhtm22.AD.QINTRA.COM (qtdenexhtm22.ad.qintra.com [151.119.91.231]) by suomp60i.qintra.com (8.14.4/8.14.4) with ESMTP id q5DGIQO9023581 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=FAIL); Wed, 13 Jun 2012 11:18:26 -0500 (CDT)
Received: from qtdenexmbm24.AD.QINTRA.COM ([151.119.91.226]) by qtdenexhtm22.AD.QINTRA.COM ([151.119.91.231]) with mapi; Wed, 13 Jun 2012 10:18:26 -0600
From: "Smith, Donald" <Donald.Smith@CenturyLink.com>
To: "'Tony Tauber'" <ttauber@1-4-5.net>, "'tkirkham@anthony-kirkham.com'" <tkirkham@anthony-kirkham.com>
Date: Wed, 13 Jun 2012 10:18:25 -0600
Thread-Topic: [GROW] WGLC: draft-ietf-grow-private-ip-sp-cores
Thread-Index: Ac1JX922sk0PLZmvRQmkrCdYQvnUMQAH8HIg
Message-ID: <B01905DA0C7CDC478F42870679DF0F101105E1DFEE@qtdenexmbm24.AD.QINTRA.COM>
References: <CAL9jLabADdWCwDhBdaBJ4fVdk9a=OeJQYFQM4Z_+-P56cVWftw@mail.gmail.com> <01e301cd4580$208f3900$4001a8c0@gateway.2wire.net> <B01905DA0C7CDC478F42870679DF0F101105C4C714@qtdenexmbm24.AD.QINTRA.COM> <4FD8726A.6040509@anthony-kirkham.com> <CAGQUKceQo3neZB7TTvCHK9hkM41ftNJaHx4dRXsVuYjhJa+5eQ@mail.gmail.com>
In-Reply-To: <CAGQUKceQo3neZB7TTvCHK9hkM41ftNJaHx4dRXsVuYjhJa+5eQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "'grow@ietf.org'" <grow@ietf.org>, "'grow-chairs@tools.ietf.org'" <grow-chairs@tools.ietf.org>
Subject: Re: [GROW] WGLC: draft-ietf-grow-private-ip-sp-cores
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jun 2012 16:18:36 -0000

Exactly! Sorry if I wasn't clear but squatting should be heavily discourage=
d as many things break that don't break with the use of private space. If y=
ou use squatted space you have to do prefix limiting possibly limiting the =
valid owner from announcing their route(s) to you (or play other better rou=
te metrics games).

When packets collide the controllers cease transmission AND wait a random t=
ime before retransmission (mostly)!
Donald.Smith@CenturyLink.com


> -----Original Message-----
> From: Tony Tauber [mailto:ttauber@1-4-5.net]
> Sent: Wednesday, June 13, 2012 6:27 AM
> To: tkirkham@anthony-kirkham.com
> Cc: Smith, Donald; grow@ietf.org; grow-chairs@tools.ietf.org
> Subject: Re: [GROW] WGLC: draft-ietf-grow-private-ip-sp-cores
>
> Using squat/stolen space will mean ICMP messages from the SP core
> wouldn't be able to reach the legitimate address holder's network but
> neither would traffic of the customers of that SP.  I don't believe
> that the same is true of "private" space; so there are actually _more_
> problems with the "squat" approach.
>
> In general, big fan, support publication.
>
> Thanks,
>
> Tony T.
>
>
> On Wed, Jun 13, 2012 at 6:58 AM, Anthony Kirkham <tkirkham@anthony-
> kirkham.com> wrote:
>
>
>       Donald,
>
>       Thanks for the review, I plan to do another update in the next
> few days, I'm just waiting to see if any further feedback arrives.
>
>       A couple of specific comments:
>
>       re - squat space. The intent was not to make recommendations on
> the practice, just to document the effects.
>
>       re - 5. Unexpected interactions with some NAT implementations:
> What you say is exactly what I intended to illustrate. I will update
> the wording so its clear I'm not talking about a routing loop.
>
>       Regards
>       Tony K
>
>
>       On 9/06/12 7:17 AM, Smith, Donald wrote:
>
>
>               There is a mention of "squat" space that doesn't make any
> recommendations as to use or not.
>
>               I can understand not expressing an opinion on the
> rfc1918/private space shouldn't this state that squating is bad?
>               "This effect in itself is often not a problem.  However, if
> anti-
>                  spoofing controls are applied at network perimeters,
> then responses
>                  returned from hops with private IP addresses will be
> dropped."
>
>               Any rfc1918 filtering mechinisim will cause this issue not
> just bcp38 type anti-spoofing.
>               Firewalls, junipers and many platforms drop rfc1918 space
> but not as part of bcp38 .
>               BTW BCP84 ala rfc3704 is an update/addition to bcp38 you
> should probably add them to this reference.
>
>
>               And for consistecy I recommend using an expression such as
> "any rfc1918 or bogon filtering..."
>
>               Under section 4 the author says urpf or ingress filtering.
>               "If the router's interface address is a
>                  private IP address, then this ICMP reply packet may be
> discarded due
>                  to uRPF or ingress filtering, thereby causing the PMTUD
> mechanism to
>                  fail."
>
>               Under
>               5. Unexpected interactions with some NAT implementations
>               The first section works. As stated it might confuse someone
> but honestly unless the 4th hop also matches the 2 hop it doesn't look
> like a routing loop to me. It looks like rfc1918 reuse.
>
>
>               Type escape sequence to abort.
>                  Tracing the route to 198.51.100.100
>
>                    1 10.1.1.2 0 msec 0 msec 0 msec
>                    2 198.51.100.13 0 msec 4 msec 0 msec
>                    3 10.1.1.2 0 <tel:3%2010.1.1.2%200>  msec 4 msec 0
> msec<<<<
>                    4 198.51.100.5 <tel:4%20198.51.100.5>  4 msec 0 msec 4
> msec
>                    5 198.51.100.1 <tel:5%20198.51.100.1>  0 msec 0 msec 0
> msec
>
>               Section 6 references rfc2827 should probably include bcp84
> and rfc3704.
>
>               Your first example of a security gap is really a no worse
> if you use private or public addresss but you call that out so I am ok
> with it.
>
>               NIT
>               This:
>               Some applications discover the outside address of
>                  their local CPE to determine if that address is reserver
> for special
>                  use.
>               Should be this:
>               Some applications discover the outside address of
>                  their local CPE to determine if that address is reserved
> for special
>                  use.
>
>
>               When packets collide the controllers cease transmission AND
> wait a random time before retransmission (mostly)!
>               Donald.Smith@CenturyLink.com
>
>
>
>
>                       -----Original Message-----
>                       From: grow-bounces@ietf.org [mailto:grow-
> bounces@ietf.org] On Behalf Of
>                       t.petch
>                       Sent: Friday, June 08, 2012 8:06 AM
>                       To: Christopher Morrow; grow-chairs@tools.ietf.org;
> grow@ietf.org
>                       Subject: Re: [GROW] WGLC: draft-ietf-grow-private-i=
p-
> sp-cores
>
>                       I would like to see this published as an RFC.
>
>                       The only discussion I see whether or not the title =
of
> 12.2 should have
>                       an initial capital - I think that it should.
>
>                       Tom Petch
>
>                       ----- Original Message -----
>                       From: "Christopher
> Morrow"<christopher.morrow@gmail.com
> <mailto:christopher.morrow@gmail.com> >
>                       To:<grow-chairs@tools.ietf.org>;<grow@ietf.org>
>                       Sent: Tuesday, June 05, 2012 7:41 PM
>
>
>                               Folks,
>                               There's been work on the draft:
>                                  <http://tools.ietf.org/html/draft-ietf-g=
row-
> private-ip-sp-cores <http://tools.ietf.org/html/draft-ietf-grow-
> private-ip-sp-cores> >
>
>                               I think the commenters' comments were addre=
ssed
> by the authors.
>                               Can we move this to WGLC now and clear that
> 6/19/2012 (June 19,
>
>
>                       2012).
>
>
>                               Abstract of the draft:
>                                 "The purpose of this document is to provi=
de a
> discussion of the
>                                  potential problems of using private,
> RFC1918, or non-globally-
>                                  routable addressing within the core of a=
n SP
> network.  The
>
>
>                       discussion
>
>
>                                  focuses on link addresses and to a small
> extent loopback
>
>
>                       addresses.
>
>
>                                  While many of the issues are well recogn=
ised
> within the ISP
>                                  community, there appears to be no docume=
nt
> that collectively
>                                  describes the issues."
>
>                               Could there be some discussion on WGLC and
> we'll see about  moving
>                               this along to the IESG?
>
>                               -chris
>                               ___________________________________________=
____
>                               GROW mailing list
>                               GROW@ietf.org
>                               https://www.ietf.org/mailman/listinfo/grow
> <https://www.ietf.org/mailman/listinfo/grow>
>
>
>
>
>                       _______________________________________________
>                       GROW mailing list
>                       GROW@ietf.org
>                       https://www.ietf.org/mailman/listinfo/grow
> <https://www.ietf.org/mailman/listinfo/grow>
>
>
>               This communication is the property of CenturyLink and may
> contain confidential or privileged information. Unauthorized use of
> this communication is strictly
>               prohibited and may be unlawful.  If you have received this
> communication
>               in error, please immediately notify the sender by reply e-
> mail and destroy
>               all copies of the communication and any attachments.
>               _______________________________________________
>               GROW mailing list
>               GROW@ietf.org
>               https://www.ietf.org/mailman/listinfo/grow
> <https://www.ietf.org/mailman/listinfo/grow>
>
>
>
>
>
>
>       --
>
>
>
>       _______________________________________________
>       GROW mailing list
>       GROW@ietf.org
>       https://www.ietf.org/mailman/listinfo/grow
> <https://www.ietf.org/mailman/listinfo/grow>
>
>


This communication is the property of CenturyLink and may contain confident=
ial or privileged information. Unauthorized use of this communication is st=
rictly
prohibited and may be unlawful.  If you have received this communication
in error, please immediately notify the sender by reply e-mail and destroy
all copies of the communication and any attachments.

From tkirkham@anthony-kirkham.com  Sat Jun 16 21:39:16 2012
Return-Path: <tkirkham@anthony-kirkham.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4D15211E808A for <grow@ietfa.amsl.com>; Sat, 16 Jun 2012 21:39:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_15=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tvyTOVi9yGOY for <grow@ietfa.amsl.com>; Sat, 16 Jun 2012 21:39:13 -0700 (PDT)
Received: from nskntmtas03p.mx.bigpond.com (nskntmtas03p.mx.bigpond.com [61.9.168.143]) by ietfa.amsl.com (Postfix) with ESMTP id 30B0211E8088 for <grow@ietf.org>; Sat, 16 Jun 2012 21:39:12 -0700 (PDT)
Received: from nskntcmgw06p ([61.9.169.166]) by nskntmtas03p.mx.bigpond.com with ESMTP id <20120617043911.YOJN10464.nskntmtas03p.mx.bigpond.com@nskntcmgw06p>;  Sun, 17 Jun 2012 04:39:11 +0000
Received: from Anthonys-MacBook-Pro.local ([124.185.157.18]) by nskntcmgw06p with BigPond Outbound id PGf61j00A0Q5xN401Gf7YH; Sun, 17 Jun 2012 04:39:11 +0000
X-Authority-Analysis: v=2.0 cv=MaHuSuDf c=1 sm=1 a=0VFf0P/YIxcxI/RgN+hXcA==:17 a=_1pLAPWVdgkA:10 a=5guEdk2PV24A:10 a=Ib5BsLsVyy8A:10 a=bVeADsv9IVkA:10 a=xR3Tfk4wAAAA:8 a=J_N6KFswAAAA:8 a=48vgC7mUAAAA:8 a=pGLkceISAAAA:8 a=W0TSPLbk8_8ecOe9HjYA:9 a=wPNLvfGTeEIA:10 a=XXhtLnmuZa8A:10 a=Pwbduc0PQ3sA:10 a=lZB815dzVvQA:10 a=MSl-tDqOz04A:10 a=DOA9UqtVIb8eiSIH:21 a=h2kJ-wAunyB7OuFJ:21 a=DRcdMcqMgZ9gEA3QyN8A:9 a=_W_S_7VecoQA:10 a=tXsnliwV7b4A:10 a=PKL3fjCvJOY_0fiD:21 a=sLg3YFiUJi1NeDKj:21 a=0VFf0P/YIxcxI/RgN+hXcA==:117
Message-ID: <4FDD5F69.3000009@anthony-kirkham.com>
Date: Sun, 17 Jun 2012 14:39:05 +1000
From: Anthony Kirkham <tkirkham@anthony-kirkham.com>
Organization: Anthony-Kirkham.com
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: Tony Tauber <ttauber@1-4-5.net>,  "Smith, Donald" <Donald.Smith@centurylink.com>
References: <CAL9jLabADdWCwDhBdaBJ4fVdk9a=OeJQYFQM4Z_+-P56cVWftw@mail.gmail.com> <01e301cd4580$208f3900$4001a8c0@gateway.2wire.net> <B01905DA0C7CDC478F42870679DF0F101105C4C714@qtdenexmbm24.AD.QINTRA.COM> <4FD8726A.6040509@anthony-kirkham.com> <CAGQUKceQo3neZB7TTvCHK9hkM41ftNJaHx4dRXsVuYjhJa+5eQ@mail.gmail.com>
In-Reply-To: <CAGQUKceQo3neZB7TTvCHK9hkM41ftNJaHx4dRXsVuYjhJa+5eQ@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------090301080804040007090404"
Cc: "grow@ietf.org" <grow@ietf.org>, "grow-chairs@tools.ietf.org" <grow-chairs@tools.ietf.org>
Subject: Re: [GROW] WGLC: draft-ietf-grow-private-ip-sp-cores
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: tkirkham@anthony-kirkham.com
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 17 Jun 2012 04:39:16 -0000

This is a multi-part message in MIME format.
--------------090301080804040007090404
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Tony and Donald,

What say If I change the wording on squat space from:

"The practice of ISPs using 'stolen' address space (also known as 
'squat' space) has many of the same issues (or effects) as that of using 
private IP address space within core networks.", plus some additional

  to:

"The practice of ISPs using 'stolen' address space (also known as 
'squat' space) has many of the same, plus some additional issues (or 
effects) as that of using private IP address space within core networks."

Regards
Tony K



On 13/06/12 10:27 PM, Tony Tauber wrote:
> Using squat/stolen space will mean ICMP messages from the SP core 
> wouldn't be able to reach the legitimate address holder's network but 
> neither would traffic of the customers of that SP.  I don't believe 
> that the same is true of "private" space; so there are actually _more_ 
> problems with the "squat" approach.
>
> In general, big fan, support publication.
>
> Thanks,
>
> Tony T.
>
> On Wed, Jun 13, 2012 at 6:58 AM, Anthony Kirkham 
> <tkirkham@anthony-kirkham.com <mailto:tkirkham@anthony-kirkham.com>> 
> wrote:
>
>     Donald,
>
>     Thanks for the review, I plan to do another update in the next few
>     days, I'm just waiting to see if any further feedback arrives.
>
>     A couple of specific comments:
>
>     re - squat space. The intent was not to make recommendations on
>     the practice, just to document the effects.
>
>     re - 5. Unexpected interactions with some NAT implementations:
>     What you say is exactly what I intended to illustrate. I will
>     update the wording so its clear I'm not talking about a routing loop.
>
>     Regards
>     Tony K
>
>
>     On 9/06/12 7:17 AM, Smith, Donald wrote:
>
>         There is a mention of "squat" space that doesn't make any
>         recommendations as to use or not.
>
>         I can understand not expressing an opinion on the
>         rfc1918/private space shouldn't this state that squating is bad?
>         "This effect in itself is often not a problem.  However, if anti-
>            spoofing controls are applied at network perimeters, then
>         responses
>            returned from hops with private IP addresses will be dropped."
>
>         Any rfc1918 filtering mechinisim will cause this issue not
>         just bcp38 type anti-spoofing.
>         Firewalls, junipers and many platforms drop rfc1918 space but
>         not as part of bcp38 .
>         BTW BCP84 ala rfc3704 is an update/addition to bcp38 you
>         should probably add them to this reference.
>
>
>         And for consistecy I recommend using an expression such as
>         "any rfc1918 or bogon filtering..."
>
>         Under section 4 the author says urpf or ingress filtering.
>         "If the router's interface address is a
>            private IP address, then this ICMP reply packet may be
>         discarded due
>            to uRPF or ingress filtering, thereby causing the PMTUD
>         mechanism to
>            fail."
>
>         Under
>         5. Unexpected interactions with some NAT implementations
>         The first section works. As stated it might confuse someone
>         but honestly unless the 4th hop also matches the 2 hop it
>         doesn't look like a routing loop to me. It looks like rfc1918
>         reuse.
>
>
>         Type escape sequence to abort.
>            Tracing the route to 198.51.100.100
>
>              1 10.1.1.2 0 msec 0 msec 0 msec
>              2 198.51.100.13 0 msec 4 msec 0 msec
>         3 10.1.1.2 0 <tel:3%2010.1.1.2%200> msec 4 msec 0 msec<<<<
>         4 198.51.100.5 <tel:4%20198.51.100.5> 4 msec 0 msec 4 msec
>         5 198.51.100.1 <tel:5%20198.51.100.1> 0 msec 0 msec 0 msec
>
>         Section 6 references rfc2827 should probably include bcp84 and
>         rfc3704.
>
>         Your first example of a security gap is really a no worse if
>         you use private or public addresss but you call that out so I
>         am ok with it.
>
>         NIT
>         This:
>         Some applications discover the outside address of
>            their local CPE to determine if that address is reserver
>         for special
>            use.
>         Should be this:
>         Some applications discover the outside address of
>            their local CPE to determine if that address is reserved
>         for special
>            use.
>
>
>         When packets collide the controllers cease transmission AND
>         wait a random time before retransmission (mostly)!
>         Donald.Smith@CenturyLink.com
>
>
>             -----Original Message-----
>             From: grow-bounces@ietf.org <mailto:grow-bounces@ietf.org>
>             [mailto:grow-bounces@ietf.org
>             <mailto:grow-bounces@ietf.org>] On Behalf Of
>             t.petch
>             Sent: Friday, June 08, 2012 8:06 AM
>             To: Christopher Morrow; grow-chairs@tools.ietf.org
>             <mailto:grow-chairs@tools.ietf.org>; grow@ietf.org
>             <mailto:grow@ietf.org>
>             Subject: Re: [GROW] WGLC: draft-ietf-grow-private-ip-sp-cores
>
>             I would like to see this published as an RFC.
>
>             The only discussion I see whether or not the title of 12.2
>             should have
>             an initial capital - I think that it should.
>
>             Tom Petch
>
>             ----- Original Message -----
>             From: "Christopher Morrow"<christopher.morrow@gmail.com
>             <mailto:christopher.morrow@gmail.com>>
>             To:<grow-chairs@tools.ietf.org
>             <mailto:grow-chairs@tools.ietf.org>>;<grow@ietf.org
>             <mailto:grow@ietf.org>>
>             Sent: Tuesday, June 05, 2012 7:41 PM
>
>                 Folks,
>                 There's been work on the draft:
>                 <http://tools.ietf.org/html/draft-ietf-grow-private-ip-sp-cores>
>
>                 I think the commenters' comments were addressed by the
>                 authors.
>                 Can we move this to WGLC now and clear that 6/19/2012
>                 (June 19,
>
>             2012).
>
>                 Abstract of the draft:
>                   "The purpose of this document is to provide a
>                 discussion of the
>                    potential problems of using private, RFC1918, or
>                 non-globally-
>                    routable addressing within the core of an SP
>                 network.  The
>
>             discussion
>
>                    focuses on link addresses and to a small extent
>                 loopback
>
>             addresses.
>
>                    While many of the issues are well recognised within
>                 the ISP
>                    community, there appears to be no document that
>                 collectively
>                    describes the issues."
>
>                 Could there be some discussion on WGLC and  we'll see
>                 about  moving
>                 this along to the IESG?
>
>                 -chris
>                 _______________________________________________
>                 GROW mailing list
>                 GROW@ietf.org <mailto:GROW@ietf.org>
>                 https://www.ietf.org/mailman/listinfo/grow
>
>
>             _______________________________________________
>             GROW mailing list
>             GROW@ietf.org <mailto:GROW@ietf.org>
>             https://www.ietf.org/mailman/listinfo/grow
>
>         This communication is the property of CenturyLink and may
>         contain confidential or privileged information. Unauthorized
>         use of this communication is strictly
>         prohibited and may be unlawful.  If you have received this
>         communication
>         in error, please immediately notify the sender by reply e-mail
>         and destroy
>         all copies of the communication and any attachments.
>         _______________________________________________
>         GROW mailing list
>         GROW@ietf.org <mailto:GROW@ietf.org>
>         https://www.ietf.org/mailman/listinfo/grow
>
>
>
>
>     -- 
>
>
>     _______________________________________________
>     GROW mailing list
>     GROW@ietf.org <mailto:GROW@ietf.org>
>     https://www.ietf.org/mailman/listinfo/grow
>
>


-- 



--------------090301080804040007090404
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Tony and Donald,<br>
    <br>
    What say If I change the wording on squat space from:<br>
    <br>
    "The practice of ISPs using &#8216;stolen&#8217; address space (also known as
    'squat' space) has many of the same issues (or effects) as that of
    using private IP address space within core networks.", plus some
    additional<br>
    <br>
    &nbsp;to:<br>
    <br>
    "The practice of ISPs using &#8216;stolen&#8217; address space (also known as
    'squat' space) has many of the same, plus some additional issues (or
    effects) as that of using private IP address space within core
    networks."<br>
    <br>
    Regards<br>
    Tony K<br>
    <br>
    <br>
    <br>
    On 13/06/12 10:27 PM, Tony Tauber wrote:
    <blockquote
cite="mid:CAGQUKceQo3neZB7TTvCHK9hkM41ftNJaHx4dRXsVuYjhJa+5eQ@mail.gmail.com"
      type="cite">Using squat/stolen space will mean ICMP messages from
      the SP core wouldn't be able to reach the legitimate address
      holder's network but neither would traffic of the customers of
      that SP.&nbsp; I don't believe that the same is true of "private"
      space; so there are actually _more_ problems with the "squat"
      approach.<br>
      <br>
      In general, big fan, support publication.<br>
      <br>
      Thanks,<br>
      <br>
      Tony T.<br>
      <br>
      <div class="gmail_quote">On Wed, Jun 13, 2012 at 6:58 AM, Anthony
        Kirkham <span dir="ltr">&lt;<a moz-do-not-send="true"
            href="mailto:tkirkham@anthony-kirkham.com" target="_blank">tkirkham@anthony-kirkham.com</a>&gt;</span>
        wrote:<br>
        <blockquote class="gmail_quote" style="margin:0 0 0
          .8ex;border-left:1px #ccc solid;padding-left:1ex">Donald,<br>
          <br>
          Thanks for the review, I plan to do another update in the next
          few days, I'm just waiting to see if any further feedback
          arrives.<br>
          <br>
          A couple of specific comments:<br>
          <br>
          re - squat space. The intent was not to make recommendations
          on the practice, just to document the effects.<br>
          <br>
          re - 5. Unexpected interactions with some NAT implementations:
          What you say is exactly what I intended to illustrate. I will
          update the wording so its clear I'm not talking about a
          routing loop.<br>
          <br>
          Regards<br>
          Tony K
          <div>
            <div class="h5"><br>
              <br>
              On 9/06/12 7:17 AM, Smith, Donald wrote:<br>
              <blockquote class="gmail_quote" style="margin:0 0 0
                .8ex;border-left:1px #ccc solid;padding-left:1ex">
                There is a mention of "squat" space that doesn't make
                any recommendations as to use or not.<br>
                <br>
                I can understand not expressing an opinion on the
                rfc1918/private space shouldn't this state that squating
                is bad?<br>
                "This effect in itself is often not a problem. &nbsp;However,
                if anti-<br>
                &nbsp; &nbsp;spoofing controls are applied at network perimeters,
                then responses<br>
                &nbsp; &nbsp;returned from hops with private IP addresses will be
                dropped."<br>
                <br>
                Any rfc1918 filtering mechinisim will cause this issue
                not just bcp38 type anti-spoofing.<br>
                Firewalls, junipers and many platforms drop rfc1918
                space but not as part of bcp38 .<br>
                BTW BCP84 ala rfc3704 is an update/addition to bcp38 you
                should probably add them to this reference.<br>
                <br>
                <br>
                And for consistecy I recommend using an expression such
                as "any rfc1918 or bogon filtering..."<br>
                <br>
                Under section 4 the author says urpf or ingress
                filtering.<br>
                "If the router's interface address is a<br>
                &nbsp; &nbsp;private IP address, then this ICMP reply packet may
                be discarded due<br>
                &nbsp; &nbsp;to uRPF or ingress filtering, thereby causing the
                PMTUD mechanism to<br>
                &nbsp; &nbsp;fail."<br>
                <br>
                Under<br>
                5. Unexpected interactions with some NAT implementations<br>
                The first section works. As stated it might confuse
                someone but honestly unless the 4th hop also matches the
                2 hop it doesn't look like a routing loop to me. It
                looks like rfc1918 reuse.<br>
                <br>
                <br>
                Type escape sequence to abort.<br>
                &nbsp; &nbsp;Tracing the route to 198.51.100.100<br>
                <br>
                &nbsp; &nbsp; &nbsp;1 10.1.1.2 0 msec 0 msec 0 msec<br>
                &nbsp; &nbsp; &nbsp;2 198.51.100.13 0 msec 4 msec 0 msec<br>
                &nbsp; &nbsp; &nbsp;<a moz-do-not-send="true"
                  href="tel:3%2010.1.1.2%200" value="+13101120"
                  target="_blank">3 10.1.1.2 0</a> msec 4 msec 0
                msec&lt;&lt;&lt;&lt;<br>
                &nbsp; &nbsp; &nbsp;<a moz-do-not-send="true"
                  href="tel:4%20198.51.100.5" value="+14198511005"
                  target="_blank">4 198.51.100.5</a> 4 msec 0 msec 4
                msec<br>
                &nbsp; &nbsp; &nbsp;<a moz-do-not-send="true"
                  href="tel:5%20198.51.100.1" value="+15198511001"
                  target="_blank">5 198.51.100.1</a> 0 msec 0 msec 0
                msec<br>
                <br>
                Section 6 references rfc2827 should probably include
                bcp84 and rfc3704.<br>
                <br>
                Your first example of a security gap is really a no
                worse if you use private or public addresss but you call
                that out so I am ok with it.<br>
                <br>
                NIT<br>
                This:<br>
                Some applications discover the outside address of<br>
                &nbsp; &nbsp;their local CPE to determine if that address is
                reserver for special<br>
                &nbsp; &nbsp;use.<br>
                Should be this:<br>
                Some applications discover the outside address of<br>
                &nbsp; &nbsp;their local CPE to determine if that address is
                reserved for special<br>
                &nbsp; &nbsp;use.<br>
                <br>
                <br>
                When packets collide the controllers cease transmission
                AND wait a random time before retransmission (mostly)!<br>
                <a class="moz-txt-link-abbreviated" href="mailto:Donald.Smith@CenturyLink.com">Donald.Smith@CenturyLink.com</a><br>
                <br>
                <br>
                <blockquote class="gmail_quote" style="margin:0 0 0
                  .8ex;border-left:1px #ccc solid;padding-left:1ex">
                  -----Original Message-----<br>
                  From: <a moz-do-not-send="true"
                    href="mailto:grow-bounces@ietf.org" target="_blank">grow-bounces@ietf.org</a>
                  [mailto:<a moz-do-not-send="true"
                    href="mailto:grow-bounces@ietf.org" target="_blank">grow-bounces@ietf.org</a>]
                  On Behalf Of<br>
                  t.petch<br>
                  Sent: Friday, June 08, 2012 8:06 AM<br>
                  To: Christopher Morrow; <a moz-do-not-send="true"
                    href="mailto:grow-chairs@tools.ietf.org"
                    target="_blank">grow-chairs@tools.ietf.org</a>; <a
                    moz-do-not-send="true" href="mailto:grow@ietf.org"
                    target="_blank">grow@ietf.org</a><br>
                  Subject: Re: [GROW] WGLC:
                  draft-ietf-grow-private-ip-sp-cores<br>
                  <br>
                  I would like to see this published as an RFC.<br>
                  <br>
                  The only discussion I see whether or not the title of
                  12.2 should have<br>
                  an initial capital - I think that it should.<br>
                  <br>
                  Tom Petch<br>
                  <br>
                  ----- Original Message -----<br>
                  From: "Christopher Morrow"&lt;<a
                    moz-do-not-send="true"
                    href="mailto:christopher.morrow@gmail.com"
                    target="_blank">christopher.morrow@gmail.com</a>&gt;<br>
                  To:&lt;<a moz-do-not-send="true"
                    href="mailto:grow-chairs@tools.ietf.org"
                    target="_blank">grow-chairs@tools.ietf.org</a>&gt;;&lt;<a
                    moz-do-not-send="true" href="mailto:grow@ietf.org"
                    target="_blank">grow@ietf.org</a>&gt;<br>
                  Sent: Tuesday, June 05, 2012 7:41 PM<br>
                  <blockquote class="gmail_quote" style="margin:0 0 0
                    .8ex;border-left:1px #ccc solid;padding-left:1ex">
                    Folks,<br>
                    There's been work on the draft:<br>
                    &nbsp; &nbsp;&lt;<a moz-do-not-send="true"
                      href="http://tools.ietf.org/html/draft-ietf-grow-private-ip-sp-cores"
                      target="_blank">http://tools.ietf.org/html/draft-ietf-grow-private-ip-sp-cores</a>&gt;<br>
                    <br>
                    I think the commenters' comments were addressed by
                    the authors.<br>
                    Can we move this to WGLC now and clear that
                    6/19/2012 (June 19,<br>
                  </blockquote>
                  2012).<br>
                  <blockquote class="gmail_quote" style="margin:0 0 0
                    .8ex;border-left:1px #ccc solid;padding-left:1ex">
                    Abstract of the draft:<br>
                    &nbsp; "The purpose of this document is to provide a
                    discussion of the<br>
                    &nbsp; &nbsp;potential problems of using private, RFC1918, or
                    non-globally-<br>
                    &nbsp; &nbsp;routable addressing within the core of an SP
                    network. &nbsp;The<br>
                  </blockquote>
                  discussion<br>
                  <blockquote class="gmail_quote" style="margin:0 0 0
                    .8ex;border-left:1px #ccc solid;padding-left:1ex"> &nbsp;
                    &nbsp;focuses on link addresses and to a small extent
                    loopback<br>
                  </blockquote>
                  addresses.<br>
                  <blockquote class="gmail_quote" style="margin:0 0 0
                    .8ex;border-left:1px #ccc solid;padding-left:1ex"> &nbsp;
                    &nbsp;While many of the issues are well recognised within
                    the ISP<br>
                    &nbsp; &nbsp;community, there appears to be no document that
                    collectively<br>
                    &nbsp; &nbsp;describes the issues."<br>
                    <br>
                    Could there be some discussion on WGLC and &nbsp;we'll
                    see about &nbsp;moving<br>
                    this along to the IESG?<br>
                    <br>
                    -chris<br>
                    _______________________________________________<br>
                    GROW mailing list<br>
                    <a moz-do-not-send="true"
                      href="mailto:GROW@ietf.org" target="_blank">GROW@ietf.org</a><br>
                    <a moz-do-not-send="true"
                      href="https://www.ietf.org/mailman/listinfo/grow"
                      target="_blank">https://www.ietf.org/mailman/listinfo/grow</a><br>
                    <br>
                  </blockquote>
                  <br>
                  _______________________________________________<br>
                  GROW mailing list<br>
                  <a moz-do-not-send="true" href="mailto:GROW@ietf.org"
                    target="_blank">GROW@ietf.org</a><br>
                  <a moz-do-not-send="true"
                    href="https://www.ietf.org/mailman/listinfo/grow"
                    target="_blank">https://www.ietf.org/mailman/listinfo/grow</a><br>
                </blockquote>
                This communication is the property of CenturyLink and
                may contain confidential or privileged information.
                Unauthorized use of this communication is strictly<br>
                prohibited and may be unlawful. &nbsp;If you have received
                this communication<br>
                in error, please immediately notify the sender by reply
                e-mail and destroy<br>
                all copies of the communication and any attachments.<br>
                _______________________________________________<br>
                GROW mailing list<br>
                <a moz-do-not-send="true" href="mailto:GROW@ietf.org"
                  target="_blank">GROW@ietf.org</a><br>
                <a moz-do-not-send="true"
                  href="https://www.ietf.org/mailman/listinfo/grow"
                  target="_blank">https://www.ietf.org/mailman/listinfo/grow</a><br>
                <br>
                <br>
              </blockquote>
              <br>
              <br>
            </div>
          </div>
          -- <br>
          <div class="HOEnZb">
            <div class="h5">
              <br>
              <br>
              _______________________________________________<br>
              GROW mailing list<br>
              <a moz-do-not-send="true" href="mailto:GROW@ietf.org"
                target="_blank">GROW@ietf.org</a><br>
              <a moz-do-not-send="true"
                href="https://www.ietf.org/mailman/listinfo/grow"
                target="_blank">https://www.ietf.org/mailman/listinfo/grow</a><br>
            </div>
          </div>
        </blockquote>
      </div>
      <br>
    </blockquote>
    <br>
    <br>
    <pre class="moz-signature" cols="72">-- 

</pre>
  </body>
</html>

--------------090301080804040007090404--

From internet-drafts@ietf.org  Sat Jun 16 22:53:48 2012
Return-Path: <internet-drafts@ietf.org>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EAFCA21F8621; Sat, 16 Jun 2012 22:53:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.388
X-Spam-Level: 
X-Spam-Status: No, score=-102.388 tagged_above=-999 required=5 tests=[AWL=0.211, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U3zqG2pm9RVu; Sat, 16 Jun 2012 22:53:47 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7755B21F861D; Sat, 16 Jun 2012 22:53:47 -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.20
Message-ID: <20120617055347.17930.41010.idtracker@ietfa.amsl.com>
Date: Sat, 16 Jun 2012 22:53:47 -0700
Cc: grow@ietf.org
Subject: [GROW] I-D Action: draft-ietf-grow-private-ip-sp-cores-05.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 17 Jun 2012 05:53:48 -0000

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

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

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


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

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

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


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


From tkirkham@anthony-kirkham.com  Sat Jun 16 22:59:36 2012
Return-Path: <tkirkham@anthony-kirkham.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 571F311E8095 for <grow@ietfa.amsl.com>; Sat, 16 Jun 2012 22:59:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.554
X-Spam-Level: 
X-Spam-Status: No, score=-1.554 tagged_above=-999 required=5 tests=[AWL=-0.445, BAYES_05=-1.11, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9t3p961n-w0s for <grow@ietfa.amsl.com>; Sat, 16 Jun 2012 22:59:34 -0700 (PDT)
Received: from nskntmtas03p.mx.bigpond.com (nskntmtas03p.mx.bigpond.com [61.9.168.143]) by ietfa.amsl.com (Postfix) with ESMTP id 1741011E8091 for <grow@ietf.org>; Sat, 16 Jun 2012 22:59:33 -0700 (PDT)
Received: from nskntcmgw05p ([61.9.169.165]) by nskntmtas03p.mx.bigpond.com with ESMTP id <20120617055933.CJCI10464.nskntmtas03p.mx.bigpond.com@nskntcmgw05p> for <grow@ietf.org>; Sun, 17 Jun 2012 05:59:33 +0000
Received: from Anthonys-MacBook-Pro.local ([124.185.157.18]) by nskntcmgw05p with BigPond Outbound id PHzX1j0070Q5xN401HzY4K; Sun, 17 Jun 2012 05:59:33 +0000
X-Authority-Analysis: v=2.0 cv=G9We4qY5 c=1 sm=1 a=0VFf0P/YIxcxI/RgN+hXcA==:17 a=_1pLAPWVdgkA:10 a=CJ6SaOCRzhsA:10 a=Ib5BsLsVyy8A:10 a=bVeADsv9IVkA:10 a=xR3Tfk4wAAAA:8 a=Z6zyjXXLuvutIYoKcsUA:9 a=wPNLvfGTeEIA:10 a=5qQHMCEJ-IWrrVaX:21 a=2ObOrOyYyw5-rNiG:21 a=KkvK9gHFwaSwYFugNAEA:9 a=_W_S_7VecoQA:10 a=0VFf0P/YIxcxI/RgN+hXcA==:117
Message-ID: <4FDD7242.5070204@anthony-kirkham.com>
Date: Sun, 17 Jun 2012 15:59:30 +1000
From: Anthony Kirkham <tkirkham@anthony-kirkham.com>
Organization: Anthony-Kirkham.com
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: "grow@ietf.org" <grow@ietf.org>
Content-Type: multipart/alternative; boundary="------------090009020502060008020606"
Subject: [GROW] Updates to draft-ietf-grow-private-ip-sp-cores
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: tkirkham@anthony-kirkham.com
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 17 Jun 2012 05:59:36 -0000

This is a multi-part message in MIME format.
--------------090009020502060008020606
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

All,

I have just posted a new version of draft-ietf-grow-private-ip-sp-cores. 
I have made the following minor changes to the document. Thank you to 
those people who provided review and feedback.


*Section 12.2 *

"informative References"  is now "Informative References"

*Section 1 - Introduction*

From:

"The practice of ISPs using 'stolen' address space (also known as 
'squat' space) has many of the same issues (or effects) as that of using 
private IP address space within core networks.", plus some additional

  to:

"The practice of ISPs using 'stolen' address space (also known as 
'squat' space) has many of the same, plus some additional issues (or 
effects) as that of using private IP address space within core networks."

*Section 3 - Effects on Traceroute*

From:

   " This effect in itself is often not a problem.  However, if anti-
    spoofing controls are applied at network perimeters, then responses
    returned from hops with private IP addresses will be dropped.  Anti-
    spoofing refers to a security control where traffic with an invalid
    source address is discarded.  Anti-spoofing is further described in
    [BCP38]/[RFC2827]. "

to:

This effect in itself is often not a problem.  However, if anti-
    spoofing controls are applied at network perimeters, then responses
    returned from hops with private IP addresses will be dropped.  Anti-
    spoofing refers to a security control where traffic with an invalid
    source address is discarded.  Anti-spoofing is further described in
    [BCP38]/[RFC2827]and[BCP84]/[RFC3704].  Additionally any RFC1918
    filtering mechanism, such as those employed in most firewalls and
    many other network devices can cause the same effect.

*Within Section 5:*

...

    R1#traceroute 198.51.100.100

    Type escape sequence to abort.
    Tracing the route to 198.51.100.100

      1 10.1.1.2 0 msec 0 msec 0 msec
      2 198.51.100.13 0 msec 4 msec 0 msec
      3 10.1.1.2 0 msec 4 msec 0 msec <<<<
      4 198.51.100.5 4 msec 0 msec 4 msec
      5 198.51.100.1 0 msec 0 msec 0 msec
    R1#

following para, from:

"This overlapping address space configuration is likely to cause
    confusion among operational staff, thereby making it more difficult
    to successfully debug networking problems."

to:

"This duplicate address space scenario has the potential to cause 
confusion among operational staff, thereby making it more difficult to 
successfully debug networking problems."

Note: I think the wording here needed to be a little clearer, but I'm 
not going to explicitly mention this is not a routing loop as I think 
the example itself is fairly clear.


Fixed NIT: "Reserver" changed to "reserved"

But have _not_ included the line "

When packets collide the controllers cease transmission AND wait a random time before retransmission (mostly)!

"


Regards
Tony K

-- 



--------------090009020502060008020606
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    All,<br>
    <br>
    I have just posted a new version of
    draft-ietf-grow-private-ip-sp-cores. I have made the following minor
    changes to the document. Thank you to those people who provided
    review and feedback.<br>
    <br>
    <br>
    <b>Section 12.2&nbsp;&nbsp; </b><br>
    <br>
    "informative References"&nbsp; is now "Informative References"<br>
    <br>
    <b>Section 1 - Introduction</b><br>
    <br>
    From:<br>
    <br>
    "The practice of ISPs using &#8216;stolen&#8217; address space (also known as
    'squat' space) has many of the same issues (or effects) as that of
    using private IP address space within core networks.", plus some
    additional<br>
    <br>
    &nbsp;to:<br>
    <br>
    "The practice of ISPs using &#8216;stolen&#8217; address space (also known as
    'squat' space) has many of the same, plus some additional issues (or
    effects) as that of using private IP address space within core
    networks."<br>
    <br>
    <b>Section 3 - Effects on Traceroute</b><br>
    <br>
    From:<br>
    <br>
    &nbsp; " This effect in itself is often not a problem.&nbsp; However, if anti-<br>
    &nbsp;&nbsp; spoofing controls are applied at network perimeters, then
    responses<br>
    &nbsp;&nbsp; returned from hops with private IP addresses will be dropped.&nbsp;
    Anti-<br>
    &nbsp;&nbsp; spoofing refers to a security control where traffic with an
    invalid<br>
    &nbsp;&nbsp; source address is discarded.&nbsp; Anti-spoofing is further described
    in<br>
    &nbsp;&nbsp; [BCP38]/[RFC2827]. "<br>
    <br>
    to:<br>
    <br>
    This effect in itself is often not a problem.&nbsp; However, if anti-<br>
    &nbsp;&nbsp; spoofing controls are applied at network perimeters, then
    responses<br>
    &nbsp;&nbsp; returned from hops with private IP addresses will be dropped.&nbsp;
    Anti-<br>
    &nbsp;&nbsp; spoofing refers to a security control where traffic with an
    invalid<br>
    &nbsp;&nbsp; source address is discarded.&nbsp; Anti-spoofing is further described
    in<br>
    &nbsp;&nbsp; [BCP38]/[RFC2827]and[BCP84]/[RFC3704].&nbsp; Additionally any RFC1918<br>
    &nbsp;&nbsp; filtering mechanism, such as those employed in most firewalls and<br>
    &nbsp;&nbsp; many other network devices can cause the same effect.<br>
    <br>
    <b>Within Section 5:</b><br>
    <br>
    ...<br>
    <br>
    &nbsp;&nbsp; R1#traceroute 198.51.100.100<br>
    <br>
    &nbsp;&nbsp; Type escape sequence to abort.<br>
    &nbsp;&nbsp; Tracing the route to 198.51.100.100<br>
    <br>
    &nbsp;&nbsp;&nbsp;&nbsp; 1 10.1.1.2 0 msec 0 msec 0 msec<br>
    &nbsp;&nbsp;&nbsp;&nbsp; 2 198.51.100.13 0 msec 4 msec 0 msec<br>
    &nbsp;&nbsp;&nbsp;&nbsp; 3 10.1.1.2 0 msec 4 msec 0 msec&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;&lt;&lt;&lt;<br>
    &nbsp;&nbsp;&nbsp;&nbsp; 4 198.51.100.5 4 msec 0 msec 4 msec<br>
    &nbsp;&nbsp;&nbsp;&nbsp; 5 198.51.100.1 0 msec 0 msec 0 msec<br>
    &nbsp;&nbsp; R1#<br>
    <br>
    following para, from:<br>
    <br>
    "This overlapping address space configuration is likely to cause<br>
    &nbsp;&nbsp; confusion among operational staff, thereby making it more
    difficult<br>
    &nbsp;&nbsp; to successfully debug networking problems."<br>
    <br>
    to:<br>
    <br>
    "This duplicate address space scenario has the potential to cause
    confusion among operational staff, thereby making it more difficult
    to successfully debug networking problems."<br>
    <br>
    Note: I think the wording here needed to be a little clearer, but
    I'm not going to explicitly mention this is not a routing loop as I
    think the example itself is fairly clear.<br>
    <br>
    <br>
    Fixed NIT: "Reserver" changed to "reserved"<br>
    <br>
    But have _not_ included the line "
    <pre wrap="">When packets collide the controllers cease transmission AND wait a random time before retransmission (mostly)!</pre>
    "<br>
    <br>
    <br>
    Regards<br>
    Tony K<br>
    <pre class="moz-signature" cols="72">-- 

</pre>
  </body>
</html>

--------------090009020502060008020606--

From Donald.Smith@CenturyLink.com  Sun Jun 17 12:21:23 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 49AF821F8608 for <grow@ietfa.amsl.com>; Sun, 17 Jun 2012 12:21:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.398
X-Spam-Level: 
X-Spam-Status: No, score=-2.398 tagged_above=-999 required=5 tests=[AWL=0.200,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cg3cHXrriXR3 for <grow@ietfa.amsl.com>; Sun, 17 Jun 2012 12:21:22 -0700 (PDT)
Received: from suomp64i.qwest.com (suomp64i.qwest.com [155.70.16.237]) by ietfa.amsl.com (Postfix) with ESMTP id 22F5521F85D0 for <grow@ietf.org>; Sun, 17 Jun 2012 12:21:21 -0700 (PDT)
Received: from lxdenvmpc030.qintra.com (lxdenvmpc030.qintra.com [10.1.51.30]) by suomp64i.qwest.com (8.14.4/8.14.4) with ESMTP id q5HJLK4U011172 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 17 Jun 2012 14:21:20 -0500 (CDT)
Received: from lxdenvmpc030.qintra.com (unknown [127.0.0.1]) by IMSA (Postfix) with ESMTP id 3AD331E004D; Sun, 17 Jun 2012 13:21:15 -0600 (MDT)
Received: from suomp61i.qintra.com (unknown [151.119.91.93]) by lxdenvmpc030.qintra.com (Postfix) with ESMTP id 182AF1E0035; Sun, 17 Jun 2012 13:21:15 -0600 (MDT)
Received: from suomp61i.qintra.com (localhost [127.0.0.1]) by suomp61i.qintra.com (8.14.4/8.14.4) with ESMTP id q5HJLEdm001972; Sun, 17 Jun 2012 14:21:14 -0500 (CDT)
Received: from qtdenexhtm22.AD.QINTRA.COM (qtdenexhtm22.ad.qintra.com [151.119.91.231]) by suomp61i.qintra.com (8.14.4/8.14.4) with ESMTP id q5HJLEZD001969 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=FAIL); Sun, 17 Jun 2012 14:21:14 -0500 (CDT)
Received: from qtdenexmbm24.AD.QINTRA.COM ([151.119.91.226]) by qtdenexhtm22.AD.QINTRA.COM ([151.119.91.231]) with mapi; Sun, 17 Jun 2012 13:21:14 -0600
From: "Smith, Donald" <Donald.Smith@CenturyLink.com>
To: "tkirkham@anthony-kirkham.com" <tkirkham@anthony-kirkham.com>, "grow@ietf.org" <grow@ietf.org>
Content-Class: urn:content-classes:message
Date: Sun, 17 Jun 2012 13:21:33 -0600
Thread-Topic: [GROW] Updates to draft-ietf-grow-private-ip-sp-cores
Thread-Index: Ac1MTmL9KkUFEq6VQUm9zKItgNhFmQAbo4IpAABdsag=
Message-ID: <20DA6B3E-8745-49A8-8E7D-92D607D9A813@mimectl>
References: <4FDD7242.5070204@anthony-kirkham.com>
In-Reply-To: <4FDD7242.5070204@anthony-kirkham.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
x-mimectl: Produced By Microsoft Exchange V8.3.105.0
Content-Type: multipart/alternative; boundary="_000_20DA6B3E874549A88E7D92D607D9A813mimectl_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: Re: [GROW] Updates to draft-ietf-grow-private-ip-sp-cores
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 17 Jun 2012 19:21:23 -0000

--_000_20DA6B3E874549A88E7D92D607D9A813mimectl_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

You don't need to include the Ethernet reference that is just a sig of mine=
. It wasn't intended as an actual comment on this rfc.
It is based on the fact that in the early days of Ethernet some routers ign=
ored the back off portion of the Ethernet standard.
It is a reminder that standards are only as good as the implementation whic=
h depends on engineer's understanding of the standard.


You addressed the rest of my concerns so far. Thank you.



(coffee !=3D sleep) & (!coffee =3D=3D sleep)
 Donald.Smith@qwest.com<mailto:Donald.Smith@qwest.com>
________________________________
From: grow-bounces@ietf.org [grow-bounces@ietf.org] On Behalf Of Anthony Ki=
rkham [tkirkham@anthony-kirkham.com]
Sent: Saturday, June 16, 2012 11:59 PM
To: grow@ietf.org
Subject: [GROW] Updates to draft-ietf-grow-private-ip-sp-cores

All,

I have just posted a new version of draft-ietf-grow-private-ip-sp-cores. I =
have made the following minor changes to the document. Thank you to those p=
eople who provided review and feedback.


Section 12.2

"informative References"  is now "Informative References"

Section 1 - Introduction

From:

"The practice of ISPs using =91stolen=92 address space (also known as 'squa=
t' space) has many of the same issues (or effects) as that of using private=
 IP address space within core networks.", plus some additional

 to:

"The practice of ISPs using =91stolen=92 address space (also known as 'squa=
t' space) has many of the same, plus some additional issues (or effects) as=
 that of using private IP address space within core networks."

Section 3 - Effects on Traceroute

From:

  " This effect in itself is often not a problem.  However, if anti-
   spoofing controls are applied at network perimeters, then responses
   returned from hops with private IP addresses will be dropped.  Anti-
   spoofing refers to a security control where traffic with an invalid
   source address is discarded.  Anti-spoofing is further described in
   [BCP38]/[RFC2827]. "

to:

This effect in itself is often not a problem.  However, if anti-
   spoofing controls are applied at network perimeters, then responses
   returned from hops with private IP addresses will be dropped.  Anti-
   spoofing refers to a security control where traffic with an invalid
   source address is discarded.  Anti-spoofing is further described in
   [BCP38]/[RFC2827]and[BCP84]/[RFC3704].  Additionally any RFC1918
   filtering mechanism, such as those employed in most firewalls and
   many other network devices can cause the same effect.

Within Section 5:

...

   R1#traceroute 198.51.100.100

   Type escape sequence to abort.
   Tracing the route to 198.51.100.100

     1 10.1.1.2 0 msec 0 msec 0 msec
     2 198.51.100.13 0 msec 4 msec 0 msec
     3 10.1.1.2 0 msec 4 msec 0 msec        <<<<
     4 198.51.100.5 4 msec 0 msec 4 msec
     5 198.51.100.1 0 msec 0 msec 0 msec
   R1#

following para, from:

"This overlapping address space configuration is likely to cause
   confusion among operational staff, thereby making it more difficult
   to successfully debug networking problems."

to:

"This duplicate address space scenario has the potential to cause confusion=
 among operational staff, thereby making it more difficult to successfully =
debug networking problems."

Note: I think the wording here needed to be a little clearer, but I'm not g=
oing to explicitly mention this is not a routing loop as I think the exampl=
e itself is fairly clear.


Fixed NIT: "Reserver" changed to "reserved"

But have _not_ included the line "

When packets collide the controllers cease transmission AND wait a random t=
ime before retransmission (mostly)!

"


Regards
Tony K

--



________________________________
This communication is the property of CenturyLink and may contain confident=
ial or privileged information. Unauthorized use of this communication is st=
rictly
prohibited and may be unlawful. If you have received this communication
in error, please immediately notify the sender by reply e-mail and destroy
all copies of the communication and any attachments.

--_000_20DA6B3E874549A88E7D92D607D9A813mimectl_
Content-Type: text/html; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<html dir=3D"ltr">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
<style title=3D"owaParaStyle"><!--P {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
--></style>
</head>
<body bgcolor=3D"#ffffff" text=3D"#000000" ocsi=3D"x">
<div dir=3D"ltr"><font color=3D"#000000" size=3D"2" face=3D"Tahoma">You don=
't need to include the&nbsp;Ethernet<a target=3D"_blank"></a><a target=3D"_=
blank"></a> reference that is just a sig of mine. It wasn't intended as an =
actual&nbsp;comment on this rfc<a target=3D"_blank"></a><a target=3D"_blank=
"></a><a target=3D"_blank"></a><a target=3D"_blank"></a>.</font></div>
<div dir=3D"ltr"><font size=3D"2" face=3D"tahoma">It is based on the fact t=
hat in the early days of&nbsp;Ethernet<a target=3D"_blank"></a>&nbsp;some r=
outers ignored the&nbsp;back off<a target=3D"_blank"></a> portion of the&nb=
sp;Ethernet<a target=3D"_blank"></a> standard.
</font></div>
<div dir=3D"ltr"><font size=3D"2" face=3D"tahoma">It is a reminder that sta=
ndards are only as good as the implementation which depends on engineer's u=
nderstanding of the standard.</font></div>
<div dir=3D"ltr"><font size=3D"2" face=3D"tahoma"></font>&nbsp;</div>
<div dir=3D"ltr">&nbsp;</div>
<div dir=3D"ltr"><font size=3D"2" face=3D"tahoma">You addressed the rest of=
 my concerns so far. Thank you.</font></div>
<div dir=3D"ltr"><font size=3D"2"></font>&nbsp;</div>
<div dir=3D"ltr"><font size=3D"2"></font>&nbsp;</div>
<div dir=3D"ltr"><font size=3D"2"></font>&nbsp;</div>
<div dir=3D"ltr"><font size=3D"2">(coffee !=3D sleep) &amp; (!coffee =3D=3D=
 sleep)<br>
&nbsp;<a href=3D"mailto:Donald.Smith@qwest.com" target=3D"_blank">Donald.Sm=
ith@qwest.com</a><a target=3D"_blank"></a><a target=3D"_blank"></a><a targe=
t=3D"_blank"></a><a target=3D"_blank"></a></font></div>
<div style=3D"DIRECTION: ltr" id=3D"divRpF167475">
<hr tabindex=3D"-1">
<font color=3D"#000000" size=3D"2" face=3D"Tahoma"><b>From:</b> grow-bounce=
s@ietf.org [grow-bounces@ietf.org] On Behalf Of Anthony Kirkham [tkirkham@a=
nthony-kirkham.com]<br>
<b>Sent:</b> Saturday, June 16, 2012 11:59 PM<br>
<b>To:</b> grow@ietf.org<br>
<b>Subject:</b> [GROW] Updates to draft-ietf-grow-private-ip-sp-cores<br>
</font><br>
</div>
<div></div>
<div>All,<br>
<br>
I have just posted a new version of draft-ietf-grow-private-ip-sp-cores. I =
have made the following minor changes to the document. Thank you to those p=
eople who provided review and feedback.<br>
<br>
<br>
<b>Section 12.2&nbsp;&nbsp; </b><br>
<br>
&quot;informative References&quot;&nbsp; is now &quot;Informative Reference=
s&quot;<br>
<br>
<b>Section 1 - Introduction</b><br>
<br>
From:<br>
<br>
&quot;The practice of ISPs using =91stolen=92 address space (also known as =
'squat' space) has many of the same issues (or effects) as that of using pr=
ivate IP address space within core networks.&quot;, plus some additional<br=
>
<br>
&nbsp;to:<br>
<br>
&quot;The practice of ISPs using =91stolen=92 address space (also known as =
'squat' space) has many of the same, plus some additional issues (or effect=
s) as that of using private IP address space within core networks.&quot;<br=
>
<br>
<b>Section 3 - Effects on Traceroute</b><br>
<br>
From:<br>
<br>
&nbsp; &quot; This effect in itself is often not a problem.&nbsp; However, =
if anti-<br>
&nbsp;&nbsp; spoofing controls are applied at network perimeters, then resp=
onses<br>
&nbsp;&nbsp; returned from hops with private IP addresses will be dropped.&=
nbsp; Anti-<br>
&nbsp;&nbsp; spoofing refers to a security control where traffic with an in=
valid<br>
&nbsp;&nbsp; source address is discarded.&nbsp; Anti-spoofing is further de=
scribed in<br>
&nbsp;&nbsp; [BCP38]/[RFC2827]. &quot;<br>
<br>
to:<br>
<br>
This effect in itself is often not a problem.&nbsp; However, if anti-<br>
&nbsp;&nbsp; spoofing controls are applied at network perimeters, then resp=
onses<br>
&nbsp;&nbsp; returned from hops with private IP addresses will be dropped.&=
nbsp; Anti-<br>
&nbsp;&nbsp; spoofing refers to a security control where traffic with an in=
valid<br>
&nbsp;&nbsp; source address is discarded.&nbsp; Anti-spoofing is further de=
scribed in<br>
&nbsp;&nbsp; [BCP38]/[RFC2827]and[BCP84]/[RFC3704].&nbsp; Additionally any =
RFC1918<br>
&nbsp;&nbsp; filtering mechanism, such as those employed in most firewalls =
and<br>
&nbsp;&nbsp; many other network devices can cause the same effect.<br>
<br>
<b>Within Section 5:</b><br>
<br>
...<br>
<br>
&nbsp;&nbsp; R1#traceroute 198.51.100.100<br>
<br>
&nbsp;&nbsp; Type escape sequence to abort.<br>
&nbsp;&nbsp; Tracing the route to 198.51.100.100<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp; 1 10.1.1.2 0 msec 0 msec 0 msec<br>
&nbsp;&nbsp;&nbsp;&nbsp; 2 198.51.100.13 0 msec 4 msec 0 msec<br>
&nbsp;&nbsp;&nbsp;&nbsp; 3 10.1.1.2 0 msec 4 msec 0 msec&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp; &lt;&lt;&lt;&lt;<br>
&nbsp;&nbsp;&nbsp;&nbsp; 4 198.51.100.5 4 msec 0 msec 4 msec<br>
&nbsp;&nbsp;&nbsp;&nbsp; 5 198.51.100.1 0 msec 0 msec 0 msec<br>
&nbsp;&nbsp; R1#<br>
<br>
following para, from:<br>
<br>
&quot;This overlapping address space configuration is likely to cause<br>
&nbsp;&nbsp; confusion among operational staff, thereby making it more diff=
icult<br>
&nbsp;&nbsp; to successfully debug networking problems.&quot;<br>
<br>
to:<br>
<br>
&quot;This duplicate address space scenario has the potential to cause conf=
usion among operational staff, thereby making it more difficult to successf=
ully debug networking problems.&quot;<br>
<br>
Note: I think the wording here needed to be a little clearer, but I'm not g=
oing to explicitly mention this is not a routing loop as I think the exampl=
e itself is fairly clear.<br>
<br>
<br>
Fixed NIT: &quot;Reserver&quot; changed to &quot;reserved&quot;<br>
<br>
But have _not_ included the line &quot;
<pre wrap=3D"">When packets collide the controllers cease transmission AND =
wait a random time before retransmission (mostly)!</pre>
&quot;<br>
<br>
<br>
Regards<br>
Tony K<br>
<pre class=3D"moz-signature" cols=3D"72">--=20

</pre>
</div>
<br>
<hr>
<font face=3D"Arial" color=3D"Gray" size=3D"1">This communication is the pr=
operty of CenturyLink and may contain confidential or privileged informatio=
n. Unauthorized use of this communication is strictly<br>
prohibited and may be unlawful. If you have received this communication<br>
in error, please immediately notify the sender by reply e-mail and destroy<=
br>
all copies of the communication and any attachments.<br>
</font>
</body>
</html>

--_000_20DA6B3E874549A88E7D92D607D9A813mimectl_--

From gaurab@lahai.com  Sun Jun 17 17:44:40 2012
Return-Path: <gaurab@lahai.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 33A3321F8573 for <grow@ietfa.amsl.com>; Sun, 17 Jun 2012 17:44:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.372
X-Spam-Level: 
X-Spam-Status: No, score=-2.372 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SARE_SUB_OBFU_Q1=0.227]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q-4WZgeJepFy for <grow@ietfa.amsl.com>; Sun, 17 Jun 2012 17:44:39 -0700 (PDT)
Received: from pao.lahai.com (pao.lahai.com [206.220.230.130]) by ietfa.amsl.com (Postfix) with ESMTP id 68B5A21F8570 for <grow@ietf.org>; Sun, 17 Jun 2012 17:44:39 -0700 (PDT)
Received: from Gaurabs-MacBook-Pro.local (cm190.epsilon121.maxonline.com.sg [222.164.121.190]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: gaurab) by pao.lahai.com (Postfix) with ESMTP id 35940B301C for <grow@ietf.org>; Mon, 18 Jun 2012 00:44:37 +0000 (UTC)
Message-ID: <4FDE79F8.3040407@lahai.com>
Date: Mon, 18 Jun 2012 01:44:40 +0100
From: Gaurab Raj Upadhaya <gaurab@lahai.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: grow@ietf.org
References: <CAL9jLabOs02rOti4tezaZiHyiOD2f9vAhsoE9c-afFb4J1xYXQ@mail.gmail.com> <alpine.DEB.2.00.1206122333490.12509@zinc>
In-Reply-To: <alpine.DEB.2.00.1206122333490.12509@zinc>
X-Enigmail-Version: 1.4.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [GROW] WGLC: draft-ietf-grow-ops-reqs-for-bgp-error-handling-04
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Jun 2012 00:44:40 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 6/13/12 4:24 PM, Tom Hodgson wrote:
> On Mon, 11 Jun 2012, Christopher Morrow wrote:
>> Hello GROW-WG folk, Please take this message as the start of a 2
>> week, ending 6/25/2012 (June 25, 2012) WGLC for the subject
>> draft, link to current version: 
>> <http://www.ietf.org/internet-drafts/draft-ietf-grow-ops-reqs-for-bgp-error-handling-04.txt>

The
>> 
latest draft -05 should proceed to the next level.

thanks
 -gaurab



- -- 

http://www.gaurab.org.np/


-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.16 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk/eefYACgkQSo7fU26F3X1F5ACeKwtHmfTcLZBDzjfd61s9QT+1
K3gAnioUbGf10Fi3OWHmeaIukontVAM1
=dWE0
-----END PGP SIGNATURE-----

From wesley.george@twcable.com  Tue Jun 19 08:08:08 2012
Return-Path: <wesley.george@twcable.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 90F3B21F852D for <grow@ietfa.amsl.com>; Tue, 19 Jun 2012 08:08:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.99
X-Spam-Level: 
X-Spam-Status: No, score=-0.99 tagged_above=-999 required=5 tests=[AWL=0.246,  BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368,  RCVD_IN_DNSWL_LOW=-1, SARE_SUB_OBFU_Q1=0.227]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Gth9-RaIEXqL for <grow@ietfa.amsl.com>; Tue, 19 Jun 2012 08:08:08 -0700 (PDT)
Received: from cdpipgw01.twcable.com (cdpipgw01.twcable.com [165.237.59.22]) by ietfa.amsl.com (Postfix) with ESMTP id 6D89521F8512 for <grow@ietf.org>; Tue, 19 Jun 2012 08:08:06 -0700 (PDT)
X-SENDER-IP: 10.136.163.12
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.75,798,1330923600"; d="scan'208";a="397970480"
Received: from unknown (HELO PRVPEXHUB03.corp.twcable.com) ([10.136.163.12]) by cdpipgw01.twcable.com with ESMTP/TLS/RC4-MD5; 19 Jun 2012 11:04:19 -0400
Received: from PRVPEXVS03.corp.twcable.com ([10.136.163.27]) by PRVPEXHUB03.corp.twcable.com ([10.136.163.12]) with mapi; Tue, 19 Jun 2012 11:05:00 -0400
From: "George, Wes" <wesley.george@twcable.com>
To: Christopher Morrow <christopher.morrow@gmail.com>, "grow-chairs@tools.ietf.org" <grow-chairs@tools.ietf.org>, "grow@ietf.org grow@ietf.org" <grow@ietf.org>
Date: Tue, 19 Jun 2012 11:05:00 -0400
Thread-Topic: [GROW] WGLC: draft-ietf-grow-ops-reqs-for-bgp-error-handling-04
Thread-Index: Ac1ID9lvOSGKMmokTm2g1oopDzKT9gGFjvVA
Message-ID: <DCC302FAA9FE5F4BBA4DCAD46569377917449AF235@PRVPEXVS03.corp.twcable.com>
References: <CAL9jLabOs02rOti4tezaZiHyiOD2f9vAhsoE9c-afFb4J1xYXQ@mail.gmail.com>
In-Reply-To: <CAL9jLabOs02rOti4tezaZiHyiOD2f9vAhsoE9c-afFb4J1xYXQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [GROW] WGLC: draft-ietf-grow-ops-reqs-for-bgp-error-handling-04
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Jun 2012 15:08:08 -0000

I've read this draft and I think it is useful and ready to proceed.
Two minor comments:

In section 4, it may be useful to specifically note the need for a flag, tr=
ap, or other notification method (to the user, rather than to the neighbor)=
 to identify when BGP is in the process of recovering RIB consistency, incl=
uding which routes are considered inconsistent (if this info is available).=
 While section 6 discusses the need for more information about the state of=
 BGP when it is recovering from these errors, I saw no reference to this sp=
ecific item. Since this is likely to be a transient state, it is also helpf=
ul to log this information to aid in root cause analysis of transient probl=
ems.

Also, there are a lot of uses of RFC2119 words in ways that could be interp=
reted as normative despite the lack of a reference to 2119. It may be usefu=
l to either go ahead and make them so (all caps, include RFC2119 boilerplat=
e) or to consider alternate words to avoid confusion. While this is an info=
rmational document and not a protocol specification, there are a lot of spe=
cific requirements of what we are expecting changes to the implementation t=
o do and not do such that normative words would likely be helpful both to i=
mplementers and to those who may follow this draft with one to make protoco=
l changes to address the requirements set forth.

Thanks,

Wes George




> -----Original Message-----
> From: grow-bounces@ietf.org [mailto:grow-bounces@ietf.org] On Behalf Of
> Christopher Morrow
> Sent: Monday, June 11, 2012 4:22 PM
> To: grow-chairs@tools.ietf.org; grow@ietf.org grow@ietf.org
> Subject: [GROW] WGLC: draft-ietf-grow-ops-reqs-for-bgp-error-handling-04
>
> Hello GROW-WG folk,
> Please take this message as the start of a 2 week, ending 6/25/2012
> (June 25, 2012) WGLC for the subject draft, link to current version:
>   <http://www.ietf.org/internet-drafts/draft-ietf-grow-ops-reqs-for-bgp-
> error-handling-04.txt>
>
> Abstract:
>  "BGP-4 is utilised as a key intra- and inter-Autonomous System routing
>    protocol in modern IP networks.  The failure modes as defined by the
>    original protocol standards are based on a number of assumptions
>    around the impact of session failure.  Numerous incidents both in the
>    global Internet routing table and within Service Provider networks
>    have been caused by strict handling of a single invalid UPDATE
>    message causing large-scale failures in one or more Autonomous
>    Systems.
>
>    This memo describes the current use of BGP-4 within Service Provider
>    networks, and outlines a set of requirements for further work to
>    enhance the mechanisms available to a BGP-4 implementation when
>    erroneous data is detected.  Whilst this document does not provide
>    specification of any standard, it is intended as an overview of a set
>    of enhancements to BGP-4 to improve the protocol's robustness to suit
>    its current deployment."
>
> -Chris
> co-chair
> _______________________________________________
> GROW mailing list
> GROW@ietf.org
> https://www.ietf.org/mailman/listinfo/grow

This E-mail and any of its attachments may contain Time Warner Cable propri=
etary information, which is privileged, confidential, or subject to copyrig=
ht belonging to Time Warner Cable. This E-mail is intended solely for the u=
se of the individual or entity to which it is addressed. If you are not the=
 intended recipient of this E-mail, you are hereby notified that any dissem=
ination, distribution, copying, or action taken in relation to the contents=
 of and attachments to this E-mail is strictly prohibited and may be unlawf=
ul. If you have received this E-mail in error, please notify the sender imm=
ediately and permanently delete the original and any copy of this E-mail an=
d any printout.

From jgs@juniper.net  Tue Jun 19 11:32:59 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 AEF1521F85FD for <grow@ietfa.amsl.com>; Tue, 19 Jun 2012 11:32:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.486
X-Spam-Level: 
X-Spam-Status: No, score=-6.486 tagged_above=-999 required=5 tests=[AWL=-0.114, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_SUB_OBFU_Q1=0.227]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iJmCw5zEzi6A for <grow@ietfa.amsl.com>; Tue, 19 Jun 2012 11:32:59 -0700 (PDT)
Received: from exprod7og120.obsmtp.com (exprod7og120.obsmtp.com [64.18.2.18]) by ietfa.amsl.com (Postfix) with ESMTP id F301521F85F7 for <grow@ietf.org>; Tue, 19 Jun 2012 11:32:56 -0700 (PDT)
Received: from P-EMHUB02-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob120.postini.com ([64.18.6.12]) with SMTP ID DSNKT+DF0jBly1q+Qpf0VnVYJJ5eW3x++6kk@postini.com; Tue, 19 Jun 2012 11:32:58 PDT
Received: from [172.16.13.202] (172.16.13.202) by P-EMHUB02-HQ.jnpr.net (172.24.192.33) with Microsoft SMTP Server id 8.3.213.0; Tue, 19 Jun 2012 11:28:44 -0700
MIME-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset="us-ascii"
From: "John G. Scudder" <jgs@juniper.net>
In-Reply-To: <CAL9jLabOs02rOti4tezaZiHyiOD2f9vAhsoE9c-afFb4J1xYXQ@mail.gmail.com>
Date: Tue, 19 Jun 2012 14:28:42 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <CCF250D4-A50B-4D29-86E6-3AC9D1C5083A@juniper.net>
References: <CAL9jLabOs02rOti4tezaZiHyiOD2f9vAhsoE9c-afFb4J1xYXQ@mail.gmail.com>
To: Christopher Morrow <christopher.morrow@gmail.com>, <draft-ietf-grow-ops-reqs-for-bgp-error-handling@tools.ietf.org>
X-Mailer: Apple Mail (2.1278)
Cc: "grow@ietf.org grow@ietf.org" <grow@ietf.org>, grow-chairs@tools.ietf.org
Subject: Re: [GROW] WGLC: draft-ietf-grow-ops-reqs-for-bgp-error-handling-04
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Jun 2012 18:32:59 -0000

It so happens that we are in the middle of an extended WG adoption =
debate for draft-uttaro-idr-bgp-persistence-01 over at IDR. The problem =
statement from that draft is kind of buried in S. 1.1:

   BGP Persistence targets the different use case of a catastrophic
   failure when the BGP control plane can remain down for a longer time
   (e.g. hours).

This relates to draft-ietf-grow-ops-reqs-for-bgp-error-handling insofar =
as draft-uttaro specifically proposes an extension to BGP error handling =
and (as far as I can tell) its problem statement is not addressed in =
reqs-for-bgp-error-handling.

While I don't think it would be reasonable to ask =
reqs-for-bgp-error-handling to address every imaginable error mode, the =
fact that this is a current active topic in IDR does suggest it might be =
worth speaking to this one.

--John

P.S.: It's possible I missed a relevant section in =
reqs-for-bgp-error-handling, in which case please do point it out.

On Jun 11, 2012, at 4:21 PM, Christopher Morrow wrote:

> Hello GROW-WG folk,
> Please take this message as the start of a 2 week, ending 6/25/2012
> (June 25, 2012) WGLC for the subject draft, link to current version:
>  =
<http://www.ietf.org/internet-drafts/draft-ietf-grow-ops-reqs-for-bgp-erro=
r-handling-04.txt>
>=20
> Abstract:
> "BGP-4 is utilised as a key intra- and inter-Autonomous System routing
>   protocol in modern IP networks.  The failure modes as defined by the
>   original protocol standards are based on a number of assumptions
>   around the impact of session failure.  Numerous incidents both in =
the
>   global Internet routing table and within Service Provider networks
>   have been caused by strict handling of a single invalid UPDATE
>   message causing large-scale failures in one or more Autonomous
>   Systems.
>=20
>   This memo describes the current use of BGP-4 within Service Provider
>   networks, and outlines a set of requirements for further work to
>   enhance the mechanisms available to a BGP-4 implementation when
>   erroneous data is detected.  Whilst this document does not provide
>   specification of any standard, it is intended as an overview of a =
set
>   of enhancements to BGP-4 to improve the protocol's robustness to =
suit
>   its current deployment."
>=20
> -Chris
> co-chair

From paaguti@gmail.com  Wed Jun 20 22:24:01 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 E2C0821F85C7 for <grow@ietfa.amsl.com>; Wed, 20 Jun 2012 22:24:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.372
X-Spam-Level: 
X-Spam-Status: No, score=-3.372 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, SARE_SUB_OBFU_Q1=0.227]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id y1t3KCjd85FU for <grow@ietfa.amsl.com>; Wed, 20 Jun 2012 22:24:01 -0700 (PDT)
Received: from mail-gh0-f172.google.com (mail-gh0-f172.google.com [209.85.160.172]) by ietfa.amsl.com (Postfix) with ESMTP id C625B21F85C6 for <grow@ietf.org>; Wed, 20 Jun 2012 22:23:59 -0700 (PDT)
Received: by ghbg16 with SMTP id g16so171270ghb.31 for <grow@ietf.org>; Wed, 20 Jun 2012 22:23:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=QJZdPerLyrDWWAOS2rDV18beQcTwDv2kIbdrt3y1wLg=; b=MlMivZGEzGHVTcc0PsonK52Huqiljg7uEHs/IIgomYLEkkxUmiN29RqgogYKtM5I7e qDAtn1pII2B6TwHYyFUO4aMfMem++AUOHbcXVNwBNxLQUzNal44+PkelXlVGG+U1v7gX fQZilUf5u4TtqA1MxvH8wdhbcKrDj212Je70EyyvZHvc/ZmBjDqqOGeRFmLmAxmXe5r/ d3qs/fnT9kCbjP7px2RmuspPRlJxj4xXrcBAZ7ywbsNPIsEogO/jKgsjPZxOGh68dgu0 zl6Objo0fL4zHvowN+wemrK1VZOFzhe8aa2U2A5fUnGBx0aydDJ+tDq2fzGZkiYy5OTP m6ew==
MIME-Version: 1.0
Received: by 10.236.77.134 with SMTP id d6mr31110717yhe.79.1340256239354; Wed, 20 Jun 2012 22:23:59 -0700 (PDT)
Received: by 10.236.46.103 with HTTP; Wed, 20 Jun 2012 22:23:59 -0700 (PDT)
In-Reply-To: <DCC302FAA9FE5F4BBA4DCAD46569377917449AF235@PRVPEXVS03.corp.twcable.com>
References: <CAL9jLabOs02rOti4tezaZiHyiOD2f9vAhsoE9c-afFb4J1xYXQ@mail.gmail.com> <DCC302FAA9FE5F4BBA4DCAD46569377917449AF235@PRVPEXVS03.corp.twcable.com>
Date: Thu, 21 Jun 2012 07:23:59 +0200
Message-ID: <CAO48Bk_O9ka4mf1SMcGh9kpbbNL5=+cfe3eGU5sOZoBaAVY9kw@mail.gmail.com>
From: Pedro Andres Aranda Gutierrez <paaguti@gmail.com>
To: "George, Wes" <wesley.george@twcable.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "grow@ietf.org grow@ietf.org" <grow@ietf.org>, "grow-chairs@tools.ietf.org" <grow-chairs@tools.ietf.org>
Subject: Re: [GROW] WGLC: draft-ietf-grow-ops-reqs-for-bgp-error-handling-04
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Jun 2012 05:24:02 -0000

I completely agree with the need to send as much root-cause info as
possible. I think that the user (i.e. admin of the router receiving
wrecked BGP-4 updates) has to be informed. But I also think it would
not do any harm to inform the neighbour causing the crash (=E0 la "you
killed me with this packet!!!"). This information has to be used to
inform (via trap, log, etc.) the admin of the router causing the
damage, so that he takes action ASAP.

My .2 cents,
/Pedro A. Aranda

On Tue, Jun 19, 2012 at 5:05 PM, George, Wes <wesley.george@twcable.com> wr=
ote:
> I've read this draft and I think it is useful and ready to proceed.
> Two minor comments:
>
> In section 4, it may be useful to specifically note the need for a flag, =
trap, or other notification method (to the user, rather than to the neighbo=
r) to identify when BGP is in the process of recovering RIB consistency, in=
cluding which routes are considered inconsistent (if this info is available=
). While section 6 discusses the need for more information about the state =
of BGP when it is recovering from these errors, I saw no reference to this =
specific item. Since this is likely to be a transient state, it is also hel=
pful to log this information to aid in root cause analysis of transient pro=
blems.
>
>
> Also, there are a lot of uses of RFC2119 words in ways that could be inte=
rpreted as normative despite the lack of a reference to 2119. It may be use=
ful to either go ahead and make them so (all caps, include RFC2119 boilerpl=
ate) or to consider alternate words to avoid confusion. While this is an in=
formational document and not a protocol specification, there are a lot of s=
pecific requirements of what we are expecting changes to the implementation=
 to do and not do such that normative words would likely be helpful both to=
 implementers and to those who may follow this draft with one to make proto=
col changes to address the requirements set forth.
>
> Thanks,
>
> Wes George
>
>
>
>
>> -----Original Message-----
>> From: grow-bounces@ietf.org [mailto:grow-bounces@ietf.org] On Behalf Of
>> Christopher Morrow
>> Sent: Monday, June 11, 2012 4:22 PM
>> To: grow-chairs@tools.ietf.org; grow@ietf.org grow@ietf.org
>> Subject: [GROW] WGLC: draft-ietf-grow-ops-reqs-for-bgp-error-handling-04
>>
>> Hello GROW-WG folk,
>> Please take this message as the start of a 2 week, ending 6/25/2012
>> (June 25, 2012) WGLC for the subject draft, link to current version:
>> =A0 <http://www.ietf.org/internet-drafts/draft-ietf-grow-ops-reqs-for-bg=
p-
>> error-handling-04.txt>
>>
>> Abstract:
>> =A0"BGP-4 is utilised as a key intra- and inter-Autonomous System routin=
g
>> =A0 =A0protocol in modern IP networks. =A0The failure modes as defined b=
y the
>> =A0 =A0original protocol standards are based on a number of assumptions
>> =A0 =A0around the impact of session failure. =A0Numerous incidents both =
in the
>> =A0 =A0global Internet routing table and within Service Provider network=
s
>> =A0 =A0have been caused by strict handling of a single invalid UPDATE
>> =A0 =A0message causing large-scale failures in one or more Autonomous
>> =A0 =A0Systems.
>>
>> =A0 =A0This memo describes the current use of BGP-4 within Service Provi=
der
>> =A0 =A0networks, and outlines a set of requirements for further work to
>> =A0 =A0enhance the mechanisms available to a BGP-4 implementation when
>> =A0 =A0erroneous data is detected. =A0Whilst this document does not prov=
ide
>> =A0 =A0specification of any standard, it is intended as an overview of a=
 set
>> =A0 =A0of enhancements to BGP-4 to improve the protocol's robustness to =
suit
>> =A0 =A0its current deployment."
>>
>> -Chris
>> co-chair
>> _______________________________________________
>> GROW mailing list
>> GROW@ietf.org
>> https://www.ietf.org/mailman/listinfo/grow
>
> This E-mail and any of its attachments may contain Time Warner Cable prop=
rietary information, which is privileged, confidential, or subject to copyr=
ight belonging to Time Warner Cable. This E-mail is intended solely for the=
 use of the individual or entity to which it is addressed. If you are not t=
he intended recipient of this E-mail, you are hereby notified that any diss=
emination, distribution, copying, or action taken in relation to the conten=
ts of and attachments to this E-mail is strictly prohibited and may be unla=
wful. If you have received this E-mail in error, please notify the sender i=
mmediately and permanently delete the original and any copy of this E-mail =
and any printout.
> _______________________________________________
> GROW mailing list
> GROW@ietf.org
> https://www.ietf.org/mailman/listinfo/grow

From jakob.heitz@ericsson.com  Wed Jun 20 22:48:50 2012
Return-Path: <jakob.heitz@ericsson.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 352E521F8600 for <grow@ietfa.amsl.com>; Wed, 20 Jun 2012 22:48:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.186
X-Spam-Level: 
X-Spam-Status: No, score=-6.186 tagged_above=-999 required=5 tests=[AWL=0.186,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_SUB_OBFU_Q1=0.227]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xzcmFDnCdWCm for <grow@ietfa.amsl.com>; Wed, 20 Jun 2012 22:48:49 -0700 (PDT)
Received: from imr3.ericy.com (imr3.ericy.com [198.24.6.13]) by ietfa.amsl.com (Postfix) with ESMTP id 9AB8321F85FC for <grow@ietf.org>; Wed, 20 Jun 2012 22:48:49 -0700 (PDT)
Received: from eusaamw0707.eamcs.ericsson.se ([147.117.20.32]) by imr3.ericy.com (8.13.8/8.13.8) with ESMTP id q5L5miQ3020289 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 21 Jun 2012 00:48:44 -0500
Received: from EUSAACMS0701.eamcs.ericsson.se ([169.254.1.64]) by eusaamw0707.eamcs.ericsson.se ([147.117.20.32]) with mapi; Thu, 21 Jun 2012 01:48:43 -0400
From: Jakob Heitz <jakob.heitz@ericsson.com>
To: Pedro Andres Aranda Gutierrez <paaguti@gmail.com>, "George, Wes" <wesley.george@twcable.com>
Date: Thu, 21 Jun 2012 01:48:42 -0400
Thread-Topic: [GROW] WGLC: draft-ietf-grow-ops-reqs-for-bgp-error-handling-04
Thread-Index: Ac1PbhUzk38sGVLCTOyYZbB/ONSvdAAA1YsQ
Message-ID: <7309FCBCAE981B43ABBE69B31C8D213921C2341341@EUSAACMS0701.eamcs.ericsson.se>
References: <CAL9jLabOs02rOti4tezaZiHyiOD2f9vAhsoE9c-afFb4J1xYXQ@mail.gmail.com> <DCC302FAA9FE5F4BBA4DCAD46569377917449AF235@PRVPEXVS03.corp.twcable.com> <CAO48Bk_O9ka4mf1SMcGh9kpbbNL5=+cfe3eGU5sOZoBaAVY9kw@mail.gmail.com>
In-Reply-To: <CAO48Bk_O9ka4mf1SMcGh9kpbbNL5=+cfe3eGU5sOZoBaAVY9kw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "grow@ietf.org grow@ietf.org" <grow@ietf.org>, "grow-chairs@tools.ietf.org" <grow-chairs@tools.ietf.org>
Subject: Re: [GROW] WGLC: draft-ietf-grow-ops-reqs-for-bgp-error-handling-04
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Jun 2012 05:48:50 -0000

http://tools.ietf.org/html/draft-ietf-idr-operational-message-00

On Wednesday, June 20, 2012 10:24 PM, Pedro Andres Aranda Gutierrez <> wrot=
e:

> I completely agree with the need to send as much root-cause info as
> possible. I think that the user (i.e. admin of the router receiving
> wrecked BGP-4 updates) has to be informed. But I also think it would
> not do any harm to inform the neighbour causing the crash (=E0 la "you
> killed me with this packet!!!"). This information has to be used to
> inform (via trap, log, etc.) the admin of the router causing the
> damage, so that he takes action ASAP.
>=20
> My .2 cents,
> /Pedro A. Aranda
>=20
> On Tue, Jun 19, 2012 at 5:05 PM, George, Wes
> <wesley.george@twcable.com> wrote:=20
>> I've read this draft and I think it is useful and ready to proceed.
>> Two minor comments:
>>=20
>> In section 4, it may be useful to specifically note the need for a
>> flag, trap, or other notification method (to the user, rather than
>> to the neighbor) to identify when BGP is in the process of
>> recovering RIB consistency, including which routes are considered
>> inconsistent (if this info is available). While section 6 discusses
>> the need for more information about the state of BGP when it is
>> recovering from these errors, I saw no reference to this specific
>> item. Since this is likely to be a transient state, it is also
>> helpful to log this information to aid in root cause analysis of
>> transient problems.        =20
--=20
Jakob Heitz.=

From paaguti@gmail.com  Wed Jun 20 23:22:49 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 CBCC421F85C6 for <grow@ietfa.amsl.com>; Wed, 20 Jun 2012 23:22:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.372
X-Spam-Level: 
X-Spam-Status: No, score=-3.372 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, SARE_SUB_OBFU_Q1=0.227]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LBhCcvD+dBrC for <grow@ietfa.amsl.com>; Wed, 20 Jun 2012 23:22:49 -0700 (PDT)
Received: from mail-gg0-f172.google.com (mail-gg0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id 2235021F859F for <grow@ietf.org>; Wed, 20 Jun 2012 23:22:48 -0700 (PDT)
Received: by ggnc4 with SMTP id c4so194105ggn.31 for <grow@ietf.org>; Wed, 20 Jun 2012 23:22:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=Hsu62B2DF+aOHtfMedqjSj3h40zqsaPGCH4XNlHbG4w=; b=ZZFLDex1kPxmNmKL2Ncu447ABLyfylu+ObcfrwvlF9aRbZZlns1ivyIUJl9C79yuVU 31jptaZlZt6Knf7Ixf5AcCtzzc+qT8NbcjoOU2mm928zCDKa0MUGRHtct2EH2bVHsxnB AkjFNzxwqgn4KMUzxtsgkSjsHmqNGyDpZrH6sWwLn9+eNrxEPrivjn1ruvndBH0jpvZ9 BTa2SUDw05Y8x2ZbPo/+Cm6BKL5Mxq3BfuCa9uB0LcjtvBWQEERjTrCjN/XTybLkdaDr wYB1NK6ba9Mi29d5naZhbPLzZ6fnQSIOXfqTIH9V1uivDF9wyt0CzrI50HRfQAYW1ao2 W+PQ==
MIME-Version: 1.0
Received: by 10.236.154.69 with SMTP id g45mr30676780yhk.47.1340259768544; Wed, 20 Jun 2012 23:22:48 -0700 (PDT)
Received: by 10.236.46.103 with HTTP; Wed, 20 Jun 2012 23:22:48 -0700 (PDT)
In-Reply-To: <7309FCBCAE981B43ABBE69B31C8D213921C2341341@EUSAACMS0701.eamcs.ericsson.se>
References: <CAL9jLabOs02rOti4tezaZiHyiOD2f9vAhsoE9c-afFb4J1xYXQ@mail.gmail.com> <DCC302FAA9FE5F4BBA4DCAD46569377917449AF235@PRVPEXVS03.corp.twcable.com> <CAO48Bk_O9ka4mf1SMcGh9kpbbNL5=+cfe3eGU5sOZoBaAVY9kw@mail.gmail.com> <7309FCBCAE981B43ABBE69B31C8D213921C2341341@EUSAACMS0701.eamcs.ericsson.se>
Date: Thu, 21 Jun 2012 08:22:48 +0200
Message-ID: <CAO48Bk9ZsubfcuLhf5EUx9bKF+XdmWO7U1Scf6gwGOgsEfFcXw@mail.gmail.com>
From: Pedro Andres Aranda Gutierrez <paaguti@gmail.com>
To: Jakob Heitz <jakob.heitz@ericsson.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "grow@ietf.org grow@ietf.org" <grow@ietf.org>, "grow-chairs@tools.ietf.org" <grow-chairs@tools.ietf.org>
Subject: Re: [GROW] WGLC: draft-ietf-grow-ops-reqs-for-bgp-error-handling-04
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Jun 2012 06:22:49 -0000

OK, then let's state that operational messages (DUMP with malformed
packet) shall be used to notify the neighbor. The ideal scenario for
me is:

1.- Someone sends me a stinking packet and resets my router: I'm able
to notify him back automatically and then, if he doesn't react I can
a) shut the session down and b) ask him why he didn't react.

2.- I'm sending stinking packets: I receive a trap after I sent the
first and I can shut the router/session down and rollback any changes
or investigate where that stinking packet came from, and why it was
rejected.

I think we have still not learnt from the 2009 incidents, where it
took more than 6 hours to bring the situation back to normal and
that's a pity.

/PA

On Thu, Jun 21, 2012 at 7:48 AM, Jakob Heitz <jakob.heitz@ericsson.com> wro=
te:
> http://tools.ietf.org/html/draft-ietf-idr-operational-message-00
>
> On Wednesday, June 20, 2012 10:24 PM, Pedro Andres Aranda Gutierrez <> wr=
ote:
>
>> I completely agree with the need to send as much root-cause info as
>> possible. I think that the user (i.e. admin of the router receiving
>> wrecked BGP-4 updates) has to be informed. But I also think it would
>> not do any harm to inform the neighbour causing the crash (=E0 la "you
>> killed me with this packet!!!"). This information has to be used to
>> inform (via trap, log, etc.) the admin of the router causing the
>> damage, so that he takes action ASAP.
>>
>> My .2 cents,
>> /Pedro A. Aranda
>>
>> On Tue, Jun 19, 2012 at 5:05 PM, George, Wes
>> <wesley.george@twcable.com> wrote:
>>> I've read this draft and I think it is useful and ready to proceed.
>>> Two minor comments:
>>>
>>> In section 4, it may be useful to specifically note the need for a
>>> flag, trap, or other notification method (to the user, rather than
>>> to the neighbor) to identify when BGP is in the process of
>>> recovering RIB consistency, including which routes are considered
>>> inconsistent (if this info is available). While section 6 discusses
>>> the need for more information about the state of BGP when it is
>>> recovering from these errors, I saw no reference to this specific
>>> item. Since this is likely to be a transient state, it is also
>>> helpful to log this information to aid in root cause analysis of
>>> transient problems.
> --
> Jakob Heitz.

From robert@raszuk.net  Wed Jun 20 23:45:51 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 244CD21F8622 for <grow@ietfa.amsl.com>; Wed, 20 Jun 2012 23:45:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.486
X-Spam-Level: 
X-Spam-Status: No, score=-2.486 tagged_above=-999 required=5 tests=[AWL=-0.113, BAYES_00=-2.599, SARE_SUB_OBFU_Q1=0.227]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cK7LoMAZURhr for <grow@ietfa.amsl.com>; Wed, 20 Jun 2012 23:45:50 -0700 (PDT)
Received: from mail1310.opentransfer.com (mail1310.opentransfer.com [76.162.254.103]) by ietfa.amsl.com (Postfix) with ESMTP id 5301F21F8620 for <grow@ietf.org>; Wed, 20 Jun 2012 23:45:49 -0700 (PDT)
Received: (qmail 22473 invoked by uid 399); 21 Jun 2012 06:45:48 -0000
Received: from unknown (HELO ?192.168.1.58?) (pbs:robert@raszuk.net@83.31.246.209) by mail1310.opentransfer.com with ESMTPM; 21 Jun 2012 06:45:48 -0000
X-Originating-IP: 83.31.246.209
Message-ID: <4FE2C31C.7020505@raszuk.net>
Date: Thu, 21 Jun 2012 08:45:48 +0200
From: Robert Raszuk <robert@raszuk.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: Pedro Andres Aranda Gutierrez <paaguti@gmail.com>
References: <CAL9jLabOs02rOti4tezaZiHyiOD2f9vAhsoE9c-afFb4J1xYXQ@mail.gmail.com> <DCC302FAA9FE5F4BBA4DCAD46569377917449AF235@PRVPEXVS03.corp.twcable.com> <CAO48Bk_O9ka4mf1SMcGh9kpbbNL5=+cfe3eGU5sOZoBaAVY9kw@mail.gmail.com> <7309FCBCAE981B43ABBE69B31C8D213921C2341341@EUSAACMS0701.eamcs.ericsson.se> <CAO48Bk9ZsubfcuLhf5EUx9bKF+XdmWO7U1Scf6gwGOgsEfFcXw@mail.gmail.com>
In-Reply-To: <CAO48Bk9ZsubfcuLhf5EUx9bKF+XdmWO7U1Scf6gwGOgsEfFcXw@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Cc: "grow@ietf.org grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] WGLC: draft-ietf-grow-ops-reqs-for-bgp-error-handling-04
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: robert@raszuk.net
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Jun 2012 06:45:51 -0000

Hi Pedro,

 > I think we have still not learnt from the 2009 incidents,

I think we actually did. The number of IETF documents are trying to 
address this both in IDR and GROW WGs.

It is just that it takes 2-3 years to come up with RFC and another 2-3 
years to implement such RFC these days .... Not to mention product 
marketing/management asking left and right about business case and 
frankly speaking operational quality improvements are not on top of 
their revenue generating list of enhancements ;(

Best,
R.


> OK, then let's state that operational messages (DUMP with malformed
> packet) shall be used to notify the neighbor. The ideal scenario for
> me is:
>
> 1.- Someone sends me a stinking packet and resets my router: I'm able
> to notify him back automatically and then, if he doesn't react I can
> a) shut the session down and b) ask him why he didn't react.
>
> 2.- I'm sending stinking packets: I receive a trap after I sent the
> first and I can shut the router/session down and rollback any changes
> or investigate where that stinking packet came from, and why it was
> rejected.
>
> I think we have still not learnt from the 2009 incidents, where it
> took more than 6 hours to bring the situation back to normal and
> that's a pity.
>
> /PA
>
> On Thu, Jun 21, 2012 at 7:48 AM, Jakob Heitz <jakob.heitz@ericsson.com> wrote:
>> http://tools.ietf.org/html/draft-ietf-idr-operational-message-00
>>
>> On Wednesday, June 20, 2012 10:24 PM, Pedro Andres Aranda Gutierrez <> wrote:
>>
>>> I completely agree with the need to send as much root-cause info as
>>> possible. I think that the user (i.e. admin of the router receiving
>>> wrecked BGP-4 updates) has to be informed. But I also think it would
>>> not do any harm to inform the neighbour causing the crash (à la "you
>>> killed me with this packet!!!"). This information has to be used to
>>> inform (via trap, log, etc.) the admin of the router causing the
>>> damage, so that he takes action ASAP.
>>>
>>> My .2 cents,
>>> /Pedro A. Aranda
>>>
>>> On Tue, Jun 19, 2012 at 5:05 PM, George, Wes
>>> <wesley.george@twcable.com> wrote:
>>>> I've read this draft and I think it is useful and ready to proceed.
>>>> Two minor comments:
>>>>
>>>> In section 4, it may be useful to specifically note the need for a
>>>> flag, trap, or other notification method (to the user, rather than
>>>> to the neighbor) to identify when BGP is in the process of
>>>> recovering RIB consistency, including which routes are considered
>>>> inconsistent (if this info is available). While section 6 discusses
>>>> the need for more information about the state of BGP when it is
>>>> recovering from these errors, I saw no reference to this specific
>>>> item. Since this is likely to be a transient state, it is also
>>>> helpful to log this information to aid in root cause analysis of
>>>> transient problems.
>> --
>> Jakob Heitz.
> _______________________________________________
> GROW mailing list
> GROW@ietf.org
> https://www.ietf.org/mailman/listinfo/grow
>
>



From ju1738@att.com  Fri Jun 22 07:57:42 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 4F3EC21F8659; Fri, 22 Jun 2012 07:57:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.713
X-Spam-Level: 
X-Spam-Status: No, score=-105.713 tagged_above=-999 required=5 tests=[AWL=-0.581, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, SARE_LWSHORTT=1.24, SARE_SUB_OBFU_Q1=0.227, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vfV-CPQNwdpp; Fri, 22 Jun 2012 07:57:36 -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 404F221F861A; Fri, 22 Jun 2012 07:57:35 -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-10) over TLS secured channel with ESMTP id ed784ef4.0.1435278.00-334.3971610.nbfkord-smmo06.seg.att.com (envelope-from <ju1738@att.com>);  Fri, 22 Jun 2012 14:57:35 +0000 (UTC)
X-MXL-Hash: 4fe487df62241740-2fce62ac18bc957c89826abe17b79858cf73f2cb
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 q5MEvY37024483; Fri, 22 Jun 2012 07:57:34 -0700
Received: from fflint04.pst.cso.att.com (fflint04.pst.cso.att.com [150.234.39.64]) by flpi408.enaf.ffdc.sbc.com (8.14.5/8.14.5) with ESMTP id q5MEvPo7024265 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 22 Jun 2012 07:57:32 -0700
Received: from MISOUT7MSGHUB9F.ITServices.sbc.com (misout7msghub9f.itservices.sbc.com [144.151.223.71]) by fflint04.pst.cso.att.com (RSA Interceptor); Fri, 22 Jun 2012 07:56:50 -0700
Received: from MISOUT7MSGUSR9I.ITServices.sbc.com ([144.151.223.56]) by MISOUT7MSGHUB9F.ITServices.sbc.com ([144.151.223.71]) with mapi id 14.02.0298.004; Fri, 22 Jun 2012 10:56:50 -0400
From: "UTTARO, JAMES" <ju1738@att.com>
To: Rob Shakir <rjs@rob.sh>
Thread-Topic: draft-ietf-grow-ops-reqs-for-bgp-error-handling-04
Thread-Index: Ac1Qh0AwzuLH5xBMSu2rz3aHemLX7w==
Date: Fri, 22 Jun 2012 14:56:49 +0000
Message-ID: <B17A6910EEDD1F45980687268941550FB1F5C0@MISOUT7MSGUSR9I.ITServices.sbc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.70.151.80]
Content-Type: multipart/alternative; boundary="_000_B17A6910EEDD1F45980687268941550FB1F5C0MISOUT7MSGUSR9IIT_"
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=1.0 c=1 a=dXkvp1zHZaMA:10 a=eKrM44SyMe0A:10 a=ofMgfj31e3]
X-AnalysisOut: [cA:10 a=w2_UvhHieS8A:10 a=BLceEmwcHowA:10 a=xwOvzTHDVLE4u4]
X-AnalysisOut: [nGvK72ag==:17 a=ZGluOzbleR_Xk4LxkFIA:9 a=CjuIK1q_8ugA:10 a]
X-AnalysisOut: [=3RyeW6pd_oEGcECB:21 a=poMvd1pBHBSRxmgq:21 a=yMhMjlubAAAA:]
X-AnalysisOut: [8 a=SSmOFEACAAAA:8 a=XXGzvcpgyve4yIA-16sA:9 a=gKO2Hq4RSVkA]
X-AnalysisOut: [:10 a=UiCQ7L4-1S4A:10 a=hTZeC7Yk6K0A:10]
X-Mailman-Approved-At: Fri, 22 Jun 2012 08:21:58 -0700
Cc: 'idr wg' <idr@ietf.org>, "'grow@ietf.org'" <grow@ietf.org>
Subject: [GROW] draft-ietf-grow-ops-reqs-for-bgp-error-handling-04
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jun 2012 14:57:42 -0000

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

Rob,

Following find my comments..

Thanks,
                Jim Uttaro

General Comment,

>From a philosophical perspective I agree with the goals of this draft but I=
 do not agree with an approach that maintains a session in the face of a fa=
ilure in the machinery. This is a bottom up approach which will always be a=
 day late and a dollar short as we continue to patch what it means to be a =
viable session.. I believe the proper approach to meet your reqs ( and mine=
 too!!! ) is a top down which does not change the BGP behavior but changes =
the response to that behavior.. The reality of today's BGP fields of use wh=
ich are many and varied is that the control and the forwarding paths are or=
thogonal, the state being carried is not always paths as we usually conside=
r them. Examples include RT-C, Flowspec which are used to create PWs and si=
mulate an IGP etc... I do not believe changing the behavior of BGP session =
viability machinery to accomplish maintaining valid forwarding in the face =
of a control plane failure is the correct approach

The draft addresses a very important error condition but ( Update Error )..=
 This should be expanded to other areas where the failure of a session does=
 not indicate that a subset or all of the routing state learned over said s=
ession is invalid.. I think the draft should address this directly.. Are th=
e changes here configurable? Can I turn this off if I do not want this beha=
vior for certain topologies, AFs?

Abstract

Can the scope be expanded? There are other failure modes, i.e Timer Expiry =
which today is not considered a failure mode. In reality what I have seen i=
s that timer expiry occurs due to the fact that BGP threads cannot be servi=
ced in a timely manner.  I think it would be best if we could put it all on=
 the table..

I do think that this draft should bound the solution space. At the minimum =
the solutions proposed should meet a minimum set of the operators criteria =
in terms of managing the network, convergence, persistence, churn, forwardi=
ng impact etc...

Section 1.1

The following paragraph is based on the premise that the session being "dow=
n" results in a large impact.. This is certainly true for today's implement=
ations which use the session ( Control Plane Construct ) to determine the v=
iability of the forwarding state learned over said session. There are cases=
 where this is the session and forwarding are parallel, but in many more ca=
ses control and forwarding planes are orthogonal.. I think we need to re-co=
nsider this assumption for many of the services BGP is being used for and b=
ase the response to error conditions on this reality..

" Both within Internet and multi-service routing architectures, a
   number of BGP sessions propagate a large proportion of the required
   routing information for network operation.  For Internet routing,
   these are typically BGP sessions which propagate the global routing
   table to an AS - failure of these sessions may have a large impact on
   network service, based on a single erroneous update.  In an multi-
   service environment, typical deployments utilise a small number of
   core-facing BGP sessions, typically towards route reflector devices.
   Failure of these sessions may also result in a large impact to
   network operation.  Clearly, the avoidance of conditions requiring
   these sessions to fail is of great utility to any network operator,
  and provides further motivation for the revision of the existing
   behaviour. "

Section 1.2

Bullet 1..


This is a very interesting point.. As you stated



"  Traditional network architectures would deploy an Interior Gateway

   Protocol (IGP) to carry infrastructure and customer prefixes, with an

   Exterior Gateway Protocol (EGP) such as BGP being utilised to

   propagate these prefixes to other Autonomous Systems. "



In this environment where BGP was predominantly used to advertised state be=
tween AS domains over dedicated peering points it would makes sense that a =
malformed update learned from a peer is a fairly good indication that the p=
eer which is originating the update is suspect.. As there are other NHs ava=
ilable it would be prudent to not use the suspect session/forwarding path w=
hich in these cases were in parallel.. Maybe "treat as withdraw" is appropr=
iate not sure, although the SP should be able to decide the course of actio=
n .



I would ask you to consider that there are two cases here.. The first is wh=
en a speaker learns an update from a peer where the NH for the paths in tha=
t update is the direct peer ( ASBR, PE ), and the second whereby the update=
 is from a peer where the NH for the paths in the update is not the peer ( =
RR ). In the former case is there still a case that the original premise ho=
lds..The offending egress router should be disconnected from the topology. =
I don't think this is black and white and operators may want the flexibilit=
y of determining the behavior..



Bullet 2



Totally agree.. This is the one of the major requirements driving the BG Pe=
rsistence Draft..



Bullet 3



Not sure exactly what the intent here is.. I am all for more robust NM and =
visibility...



Section 2



I think understand where you are coming from for the first set of errors.. =
Do we have a feel as to why there would be erroneous data? It would seem th=
at whichever speaker created/modified etc.. the attr is experiencing some f=
undamental issue with the BGP machinery as it is not validating the context=
??



"Since in this case, the message

   received from the remote peer is syntactically valid, it is

   considered that such an UPDATE is indicative of erroneous data within

   a path attribute."



Section 2.1, 2.1.1, 2.1.2



Hmmm. Too be honest this make me a bit nervous.. This introduces classes of=
 failure modes.. Downstream NM, Ops etc... will have to learn how to suppor=
t these nuanced messages and intended meanings.. There is one thing certain=
, when a BGP Session goes down in today's world it merits the immediate att=
n of operations to figure out what went wrong and to fix it.. Solutions lik=
e GR or BGP Persistence do not change the trigger for Operations response..



Section 3



The premise is to modify when a NOTIFICATION message is sent thus mitigatin=
g the possibility that the session becomes invalid or to use a "treat as wi=
thdraw" for those paths sharing this common attribute.. The issue in mind i=
s the notion of the session as the be all to end all.. We could as easily w=
ithout any change to BGP use BGP Persistence to maintain the paths except f=
or the ones that have the invalid attribute.. This is the simpler method, h=
as the benefit of not changing BGP, or educating the world on the nuances o=
f the changes etc...



I also do not fully understand "treat as withdraw" does this meant that the=
 peer who has received an update with P1-PN with malformed attr then initia=
te a withdrawal to all of its peers?  Or simply assume that the paths have =
been received as a message?  Some sample topologies as to how this works wo=
uld be a good addition to this section..



Section 4



I made some comments on a solution "Re: [Idr] I-D Action: draft-ietf-idr-er=
ror-handling-02.txt" which I think is intended to address some aspects of t=
his reqs doc. It seems that there is a possibility of forwarding loops that=
 can be created and the inability of BGP to recover without operator interv=
ention.



" There are therefore risks of traffic blackholing, due to

   missing routing information, or forwarding loops.  Whilst this is

   deemed an acceptable compromise in the short term, clearly, it is

   suboptimal.  Therefore, a requirement exists to provide mechanisms by

   which a BGP speaker is able to recover the consistency of the Adj-

   RIB-In for a particular neighbour."



I do not think that the above draft which does not recover addresses this r=
eq..





I am not in support of solutions which create a scenario where BGP cannot r=
ecover without human intervention.



"It is of particular note for both means of recovering RIB consistency

   described that these are effective only when considering transitive

   errors within an implementation - for instance, should an RFC

   interpretation error within an implementation be present, regardless

   of the number of times a specific UPDATE is generated, it is likely

   that this error condition will persist (as it may with the existing

   behaviour defined by [RFC4271])."



I think the difference is that the operator knows that a serious situation =
is occurring by virtue of the session failing and can take appropriate acti=
on to correct. Forwarding can be maintained using Persistence or GR.. So IM=
O I can know a serious issue exists using existing BGP Machinery and well k=
nown procedures and at the same time maintain my forwarding..



Section 5



Why wouldn't we simply let the session fail and then use BGP Persistence or=
 GR ;)



Section 6



Nothing is going to get people's attention like a failed BGP Session.. I ca=
n only speak for my org but this is what is actively monitored as the bases=
 for the health of BGP.. Diagnostic, log etc... messages are of high volume=
 and does not get folks attn.. IMO this is a major disadvantage to this app=
roach.. We do not know how convey that something bad has happened to the BG=
P Machinery..



Section 7



Although I understand the distinction between the different classes of Upda=
te Errors, I am not sure that I understand how that translates into how the=
 BGP Machinery is actually being impacted. The increased complexity of "und=
erstanding" the type of update error message, it's cause, possible remediat=
ion etc.. makes this approach really difficult to wrap ones arms around..








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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 12 (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;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Rob,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Following find my comments..<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Thanks,<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Jim Uttaro<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">General Comment,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">From a philosophical perspective I agree with the go=
als of this draft but I do not agree with an approach that maintains a sess=
ion in the face of a failure in the machinery. This is a bottom up approach=
 which will always be a day late and
 a dollar short as we continue to patch what it means to be a viable sessio=
n.. I believe the proper approach to meet your reqs ( and mine too!!! ) is =
a top down which does not change the BGP behavior but changes the response =
to that behavior.. The reality of
 today&#8217;s BGP fields of use which are many and varied is that the cont=
rol and the forwarding paths are orthogonal, the state being carried is not=
 always paths as we usually consider them. Examples include RT-C, Flowspec =
which are used to create PWs and simulate
 an IGP etc&#8230; I do not believe changing the behavior of BGP session vi=
ability machinery to accomplish maintaining valid forwarding in the face of=
 a control plane failure is the correct approach<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">The draft addresses a very important error condition=
 but ( Update Error ).. This should be expanded to other areas where the fa=
ilure of a session does not indicate that a subset or all of the routing st=
ate learned over said session is invalid..
 I think the draft should address this directly.. Are the changes here conf=
igurable? Can I turn this off if I do not want this behavior for certain to=
pologies, AFs?<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Abstract<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Can the scope be expanded? There are other failure m=
odes, i.e Timer Expiry which today is not considered a failure mode. In rea=
lity what I have seen is that timer expiry occurs due to the fact that BGP =
threads cannot be serviced in a timely
 manner. &nbsp;I think it would be best if we could put it all on the table=
.. <o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">I do think that this draft should bound the solution=
 space. At the minimum the solutions proposed should meet a minimum set of =
the operators criteria in terms of managing the network, convergence, persi=
stence, churn, forwarding impact etc&#8230;
 &nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 1.1<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">The following paragraph is based on the premise that=
 the session being &#8220;down&#8221; results in a large impact.. This is c=
ertainly true for today&#8217;s implementations which use the session ( Con=
trol Plane Construct ) to determine the viability of
 the forwarding state learned over said session. There are cases where this=
 is the session and forwarding are parallel, but in many more cases control=
 and forwarding planes are orthogonal.. I think we need to re-consider this=
 assumption for many of the services
 BGP is being used for and base the response to error conditions on this re=
ality..<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&#8220; Both within Internet and multi-service routing arc=
hitectures, a<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;&nbsp; number of BGP sessions propagate a large prop=
ortion of the required<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;&nbsp; routing information for network operation.&nb=
sp; For Internet routing,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;&nbsp; these are typically BGP sessions which propag=
ate the global routing<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;&nbsp; table to an AS - failure of these sessions ma=
y have a large impact on<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;&nbsp; network service, based on a single erroneous =
update.&nbsp; In an multi-<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;&nbsp; service environment, typical deployments util=
ise a small number of<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;&nbsp; core-facing BGP sessions, typically towards r=
oute reflector devices.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;&nbsp; Failure of these sessions may also result in =
a large impact to<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;&nbsp; network operation.&nbsp; Clearly, the avoidan=
ce of conditions requiring<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;&nbsp; these sessions to fail is of great utility to=
 any network operator,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;&nbsp;and provides further motivation for the revisi=
on of the existing<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;&nbsp; behaviour. &#8220;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 1.2<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Bullet 1.. <o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<pre>This is a very interesting point.. As you stated <o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>&#8220;&nbsp; Traditional network architectures would deploy an Interi=
or Gateway<o:p></o:p></pre>
<pre>&nbsp;&nbsp; Protocol (IGP) to carry infrastructure and customer prefi=
xes, with an<o:p></o:p></pre>
<pre>&nbsp;&nbsp; Exterior Gateway Protocol (EGP) such as BGP being utilise=
d to<o:p></o:p></pre>
<pre>&nbsp;&nbsp; propagate these prefixes to other Autonomous Systems. &#8=
220;<o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>In this environment where BGP was predominantly used to advertised sta=
te between AS domains over dedicated peering points it would makes sense th=
at a malformed update learned from a peer is a fairly good indication that =
the peer which is originating the update is suspect.. As there are other NH=
s available it would be prudent to not use the suspect session/forwarding p=
ath which in these cases were in parallel.. Maybe &#8220;treat as withdraw&=
#8221; is appropriate not sure, although the SP should be able to decide th=
e course of action .<o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>I would ask you to consider that there are two cases here.. The first =
is when a speaker learns an update from a peer where the NH for the paths i=
n that update is the direct peer ( ASBR, PE ), and the second whereby the u=
pdate is from a peer where the NH for the paths in the update is not the pe=
er ( RR ). In the former case is there still a case that the original premi=
se holds..The offending egress router should be disconnected from the topol=
ogy. I don&#8217;t think this is black and white and operators may want the=
 flexibility of determining the behavior..<o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>Bullet 2<o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>Totally agree.. This is the one of the major requirements driving the =
BG Persistence Draft..<o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>Bullet 3<o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>Not sure exactly what the intent here is.. I am all for more robust NM=
 and visibility&#8230;<o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>Section 2<o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>I think understand where you are coming from for the first set of erro=
rs.. Do we have a feel as to why there would be erroneous data? It would se=
em that whichever speaker created/modified etc.. the attr is experiencing s=
ome fundamental issue with the BGP machinery as it is not validating the co=
ntext??<o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>&#8220;Since in this case, the message<o:p></o:p></pre>
<pre>&nbsp;&nbsp; received from the remote peer is syntactically valid, it =
is<o:p></o:p></pre>
<pre>&nbsp;&nbsp; considered that such an UPDATE is indicative of erroneous=
 data within<o:p></o:p></pre>
<pre>&nbsp;&nbsp; a path attribute.&#8221;<o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>Section 2.1, 2.1.1, 2.1.2<o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>Hmmm. Too be honest this make me a bit nervous.. This introduces class=
es of failure modes.. Downstream NM, Ops etc&#8230; will have to learn how =
to support these nuanced messages and intended meanings.. There is one thin=
g certain, when a BGP Session goes down in today&#8217;s world it merits th=
e immediate attn of operations to figure out what went wrong and to fix it.=
. Solutions like GR or BGP Persistence do not change the trigger for Operat=
ions response..<o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>Section 3<o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>The premise is to modify when a NOTIFICATION message is sent thus miti=
gating the possibility that the session becomes invalid or to use a &#8220;=
treat as withdraw&#8221; for those paths sharing this common attribute.. Th=
e issue in mind is the notion of the session as the be all to end all.. We =
could as easily without any change to BGP use BGP Persistence to maintain t=
he paths except for the ones that have the invalid attribute.. This is the =
simpler method, has the benefit of not changing BGP, or educating the world=
 on the nuances of the changes etc&#8230; <o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>I also do not fully understand &#8220;treat as withdraw&#8221; does th=
is meant that the peer who has received an update with P1-PN with malformed=
 attr then initiate a withdrawal to all of its peers? &nbsp;Or simply assum=
e that the paths have been received as a message? &nbsp;Some sample topolog=
ies as to how this works would be a good addition to this section..<o:p></o=
:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>Section 4<o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>I made some comments on a solution &#8220;Re: [Idr] I-D Action: draft-=
ietf-idr-error-handling-02.txt&#8221; which I think is intended to address =
some aspects of this reqs doc. It seems that there is a possibility of forw=
arding loops that can be created and the inability of BGP to recover withou=
t operator intervention. <o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>&#8220; There are therefore risks of traffic blackholing, due to<o:p><=
/o:p></pre>
<pre>&nbsp;&nbsp; missing routing information, or forwarding loops.&nbsp; W=
hilst this is<o:p></o:p></pre>
<pre>&nbsp;&nbsp; deemed an acceptable compromise in the short term, clearl=
y, it is<o:p></o:p></pre>
<pre>&nbsp;&nbsp; suboptimal.&nbsp; Therefore, a requirement exists to prov=
ide mechanisms by<o:p></o:p></pre>
<pre>&nbsp;&nbsp; which a BGP speaker is able to recover the consistency of=
 the Adj-<o:p></o:p></pre>
<pre>&nbsp;&nbsp; RIB-In for a particular neighbour.&#8221;<o:p></o:p></pre=
>
<pre><o:p>&nbsp;</o:p></pre>
<pre>I do not think that the above draft which does not recover addresses t=
his req..<o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>I am not in support of solutions which create a scenario where BGP can=
not recover without human intervention.<o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>&#8220;It is of particular note for both means of recovering RIB consi=
stency<o:p></o:p></pre>
<pre>&nbsp;&nbsp; described that these are effective only when considering =
transitive<o:p></o:p></pre>
<pre>&nbsp;&nbsp; errors within an implementation - for instance, should an=
 RFC<o:p></o:p></pre>
<pre>&nbsp;&nbsp; interpretation error within an implementation be present,=
 regardless<o:p></o:p></pre>
<pre>&nbsp;&nbsp; of the number of times a specific UPDATE is generated, it=
 is likely<o:p></o:p></pre>
<pre>&nbsp;&nbsp; that this error condition will persist (as it may with th=
e existing<o:p></o:p></pre>
<pre>&nbsp;&nbsp; behaviour defined by [RFC4271]).&#8221;<o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>I think the difference is that the operator knows that a serious situa=
tion is occurring by virtue of the session failing and can take appropriate=
 action to correct. Forwarding can be maintained using Persistence or GR.. =
So IMO I can know a serious issue exists using existing BGP Machinery and w=
ell known procedures and at the same time maintain my forwarding..<o:p></o:=
p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>Section 5<o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>Why wouldn&#8217;t we simply let the session fail and then use BGP Per=
sistence or GR ;) &nbsp;<o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>Section 6<o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>Nothing is going to get people&#8217;s attention like a failed BGP Ses=
sion.. I can only speak for my org but this is what is actively monitored a=
s the bases for the health of BGP.. Diagnostic, log etc&#8230; messages are=
 of high volume and does not get folks attn.. IMO this is a major disadvant=
age to this approach.. We do not know how convey that something bad has hap=
pened to the BGP Machinery..<o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>Section 7<o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>Although I understand the distinction between the different classes of=
 Update Errors, I am not sure that I understand how that translates into ho=
w the BGP Machinery is actually being impacted. The increased complexity of=
 &#8220;understanding&#8221; the type of update error message, it&#8217;s c=
ause, possible remediation etc.. makes this approach really difficult to wr=
ap ones arms around..<o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_B17A6910EEDD1F45980687268941550FB1F5C0MISOUT7MSGUSR9IIT_--

From robert@raszuk.net  Fri Jun 22 08:57: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 31F0821F8601 for <grow@ietfa.amsl.com>; Fri, 22 Jun 2012 08:57:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.442
X-Spam-Level: 
X-Spam-Status: No, score=-2.442 tagged_above=-999 required=5 tests=[AWL=-0.070, BAYES_00=-2.599, SARE_SUB_OBFU_Q1=0.227]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MAKl8XDmmAg1 for <grow@ietfa.amsl.com>; Fri, 22 Jun 2012 08:57:04 -0700 (PDT)
Received: from mail1310.opentransfer.com (mail1310.opentransfer.com [76.162.254.103]) by ietfa.amsl.com (Postfix) with ESMTP id 1A2E821F859E for <grow@ietf.org>; Fri, 22 Jun 2012 08:57:04 -0700 (PDT)
Received: (qmail 22950 invoked by uid 399); 22 Jun 2012 15:57:02 -0000
Received: from unknown (HELO ?192.168.1.91?) (pbs:robert@raszuk.net@83.31.147.254) by mail1310.opentransfer.com with ESMTPM; 22 Jun 2012 15:57:02 -0000
X-Originating-IP: 83.31.147.254
Message-ID: <4FE495CD.7080604@raszuk.net>
Date: Fri, 22 Jun 2012 17:57:01 +0200
From: Robert Raszuk <robert@raszuk.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: "idr@ietf.org List" <idr@ietf.org>, "grow@ietf.org" <grow@ietf.org>
References: <B17A6910EEDD1F45980687268941550FB1F5C0@MISOUT7MSGUSR9I.ITServices.sbc.com>
In-Reply-To: <B17A6910EEDD1F45980687268941550FB1F5C0@MISOUT7MSGUSR9I.ITServices.sbc.com>
X-Forwarded-Message-Id: <B17A6910EEDD1F45980687268941550FB1F5C0@MISOUT7MSGUSR9I.ITServices.sbc.com>
Content-Type: multipart/mixed; boundary="------------020302020806020607080304"
Cc: "UTTARO, JAMES \(ATTLABS\)" <ju1738@att.com>
Subject: [GROW] Fwd:  draft-ietf-grow-ops-reqs-for-bgp-error-handling-04
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: robert@raszuk.net
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jun 2012 15:57:07 -0000

This is a multi-part message in MIME format.
--------------020302020806020607080304
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit

Jim,

> We could as easily without any change to BGP use BGP Persistence to
> maintain the paths except for the ones that have the invalid
> attribute.. This is the simpler method, has the benefit of not
> changing BGP, or educating the world on the nuances of the changes
> etc…
+
> Why wouldn’t we simply let the session fail and then use BGP Persistence
> or GR ;)

Please observe that when the session is down you are not receiving 
withdraws or new best paths for those "good" prefixes (maybe 99% of 
them) which did not have any errors in their respective update messages.

Equating it with persistence proposal is therefor highly incorrect.

> I also do not fully understand “treat as withdraw” does this meant that
> the peer who has received an update with P1-PN with malformed attr then
> initiate a withdrawal to all of its peers?  Or simply assume that the
> paths have been received as a message?  Some sample topologies as to how
> this works would be a good addition to this section..

The speaker reacting on an error which can be addressed by 
"treat-as-withdraw" invalidates locally those prefixes received in the 
update message, runs local best path and as result if no other path is 
found withdraws those prefixes from all peers it has previously sent 
them to.

> I am not in support of solutions which create a scenario where BGP
> cannot recover without human intervention.

I think no one is. But we are - I think - not there yet for the routers 
to automatically fix their bugs, but only automatically signalling them 
the requested action ;(.

 > Nothing is going to get people’s attention like a failed BGP
 > Session..

True statement. But the entire assumption behind treat-as-withdraw is 
that your ops scripts parse the syslog messages indicating the issue to 
NOC with the same red color and buzz as bgp session down. Of course you 
need to rework your ops scripts/alarms for that to happen.

Rgs,
R.

PS.

Note that if the main BGP session is down (like in the persistence case) 
BGP Operational Messages can not any longer be exchanged between peers 
as TCP connection could have been reset (if no multisession is used and 
if we are talking about single SAFI). That just makes the issue worse 
especially when you do not like to have humans intervention.



--------------020302020806020607080304
Content-Type: text/plain; charset=windows-1252;
 name="Attached Message Part"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
 filename="Attached Message Part"

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


--------------020302020806020607080304--

From enkechen@cisco.com  Fri Jun 22 10:58:49 2012
Return-Path: <enkechen@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 57C5B21F86CF; Fri, 22 Jun 2012 10:58:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.365
X-Spam-Level: 
X-Spam-Status: No, score=-10.365 tagged_above=-999 required=5 tests=[AWL=0.006, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, SARE_SUB_OBFU_Q1=0.227]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E8SSyliXgwhL; Fri, 22 Jun 2012 10:58:47 -0700 (PDT)
Received: from mtv-iport-1.cisco.com (mtv-iport-1.cisco.com [173.36.130.12]) by ietfa.amsl.com (Postfix) with ESMTP id 5E41821F86C9; Fri, 22 Jun 2012 10:58:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=enkechen@cisco.com; l=8075; q=dns/txt; s=iport; t=1340387927; x=1341597527; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to; bh=fmkzcRJgmtVEVP51hgY465sncHca9jTxZh/6z/nYmvI=; b=T+VHiPxzx5RUPik3/6kNOkARh2rPJ0L4fWCRq0MssYYOOd+BkO0raivR 2brlu9OPJzRyfRPK/FoaQN5ucU2stDGPFGfPtL9NTfjH/zbrc22lkP9n6 uiXJG+1sLe04gmVX6DdfVPtn2PErQI0IKg5m+ekN0kU0d2YVSfHKaEjZl 8=;
X-IronPort-AV: E=Sophos;i="4.77,459,1336348800"; d="scan'208,217";a="46791415"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by mtv-iport-1.cisco.com with ESMTP; 22 Jun 2012 17:58:47 +0000
Received: from sjc-vpn4-1382.cisco.com (sjc-vpn4-1382.cisco.com [10.21.85.101]) by mtv-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id q5MHwkbL019597; Fri, 22 Jun 2012 17:58:46 GMT
Message-ID: <4FE4B2AD.9050704@cisco.com>
Date: Fri, 22 Jun 2012 11:00:13 -0700
From: Enke Chen <enkechen@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: robert@raszuk.net
References: <B17A6910EEDD1F45980687268941550FB1F5C0@MISOUT7MSGUSR9I.ITServices.sbc.com> <4FE495CD.7080604@raszuk.net>
In-Reply-To: <4FE495CD.7080604@raszuk.net>
Content-Type: multipart/alternative; boundary="------------070506060203000902020309"
Cc: "idr@ietf.org List" <idr@ietf.org>, "grow@ietf.org" <grow@ietf.org>, "UTTARO, JAMES \(ATTLABS\)" <ju1738@att.com>
Subject: Re: [GROW] [Idr] Fwd: draft-ietf-grow-ops-reqs-for-bgp-error-handling-04
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jun 2012 17:58:49 -0000

This is a multi-part message in MIME format.
--------------070506060203000902020309
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hi, folks:

It might help the discussion to refresh ourselves about several large 
outages in the last few years that prompted the work on the error 
handling requirements and solutions:

    o issue with AS4_PATH that resulted in session resets multiple hops 
away (two separate incidents)
    o session reset triggered by a single route with a new attribute

I remember that Rob had a presentation at the NANOG on the topic.

-- Enke

On 6/22/12 8:57 AM, Robert Raszuk wrote:
> Jim,
>
>> We could as easily without any change to BGP use BGP Persistence to
>> maintain the paths except for the ones that have the invalid
>> attribute.. This is the simpler method, has the benefit of not
>> changing BGP, or educating the world on the nuances of the changes
>> etc...
> +
>> Why wouldn't we simply let the session fail and then use BGP Persistence
>> or GR ;)
>
> Please observe that when the session is down you are not receiving 
> withdraws or new best paths for those "good" prefixes (maybe 99% of 
> them) which did not have any errors in their respective update messages.
>
> Equating it with persistence proposal is therefor highly incorrect.
>
>> I also do not fully understand "treat as withdraw" does this meant that
>> the peer who has received an update with P1-PN with malformed attr then
>> initiate a withdrawal to all of its peers?  Or simply assume that the
>> paths have been received as a message?  Some sample topologies as to how
>> this works would be a good addition to this section..
>
> The speaker reacting on an error which can be addressed by 
> "treat-as-withdraw" invalidates locally those prefixes received in the 
> update message, runs local best path and as result if no other path is 
> found withdraws those prefixes from all peers it has previously sent 
> them to.
>
>> I am not in support of solutions which create a scenario where BGP
>> cannot recover without human intervention.
>
> I think no one is. But we are - I think - not there yet for the 
> routers to automatically fix their bugs, but only automatically 
> signalling them the requested action ;(.
>
> > Nothing is going to get people's attention like a failed BGP
> > Session..
>
> True statement. But the entire assumption behind treat-as-withdraw is 
> that your ops scripts parse the syslog messages indicating the issue 
> to NOC with the same red color and buzz as bgp session down. Of course 
> you need to rework your ops scripts/alarms for that to happen.
>
> Rgs,
> R.
>
> PS.
>
> Note that if the main BGP session is down (like in the persistence 
> case) BGP Operational Messages can not any longer be exchanged between 
> peers as TCP connection could have been reset (if no multisession is 
> used and if we are talking about single SAFI). That just makes the 
> issue worse especially when you do not like to have humans intervention.
>
>
>
>
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr


--------------070506060203000902020309
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    Hi, folks:<br>
    <br>
    It might help the discussion to refresh ourselves about several
    large outages in the last few years that prompted the work on the
    error handling requirements and solutions:<br>
    <br>
    &nbsp;&nbsp; o issue with AS4_PATH that resulted in session resets multiple
    hops away (two separate incidents)<br>
    &nbsp;&nbsp; o session reset triggered by a single route with a new attribute<br>
    <br>
    I remember that Rob had a presentation at the NANOG on the topic.<br>
    <br>
    -- Enke<br>
    <br>
    On 6/22/12 8:57 AM, Robert Raszuk wrote:
    <blockquote cite="mid:4FE495CD.7080604@raszuk.net" type="cite">Jim,
      <br>
      <br>
      <blockquote type="cite">We could as easily without any change to
        BGP use BGP Persistence to
        <br>
        maintain the paths except for the ones that have the invalid
        <br>
        attribute.. This is the simpler method, has the benefit of not
        <br>
        changing BGP, or educating the world on the nuances of the
        changes
        <br>
        etc&#8230;
        <br>
      </blockquote>
      +
      <br>
      <blockquote type="cite">Why wouldn&#8217;t we simply let the session
        fail and then use BGP Persistence
        <br>
        or GR ;)
        <br>
      </blockquote>
      <br>
      Please observe that when the session is down you are not receiving
      withdraws or new best paths for those "good" prefixes (maybe 99%
      of them) which did not have any errors in their respective update
      messages.
      <br>
      <br>
      Equating it with persistence proposal is therefor highly
      incorrect.
      <br>
      <br>
      <blockquote type="cite">I also do not fully understand &#8220;treat as
        withdraw&#8221; does this meant that
        <br>
        the peer who has received an update with P1-PN with malformed
        attr then
        <br>
        initiate a withdrawal to all of its peers?&nbsp; Or simply assume
        that the
        <br>
        paths have been received as a message?&nbsp; Some sample topologies
        as to how
        <br>
        this works would be a good addition to this section..
        <br>
      </blockquote>
      <br>
      The speaker reacting on an error which can be addressed by
      "treat-as-withdraw" invalidates locally those prefixes received in
      the update message, runs local best path and as result if no other
      path is found withdraws those prefixes from all peers it has
      previously sent them to.
      <br>
      <br>
      <blockquote type="cite">I am not in support of solutions which
        create a scenario where BGP
        <br>
        cannot recover without human intervention.
        <br>
      </blockquote>
      <br>
      I think no one is. But we are - I think - not there yet for the
      routers to automatically fix their bugs, but only automatically
      signalling them the requested action ;(.
      <br>
      <br>
      &gt; Nothing is going to get people&#8217;s attention like a failed BGP
      <br>
      &gt; Session..
      <br>
      <br>
      True statement. But the entire assumption behind treat-as-withdraw
      is that your ops scripts parse the syslog messages indicating the
      issue to NOC with the same red color and buzz as bgp session down.
      Of course you need to rework your ops scripts/alarms for that to
      happen.
      <br>
      <br>
      Rgs,
      <br>
      R.
      <br>
      <br>
      PS.
      <br>
      <br>
      Note that if the main BGP session is down (like in the persistence
      case) BGP Operational Messages can not any longer be exchanged
      between peers as TCP connection could have been reset (if no
      multisession is used and if we are talking about single SAFI).
      That just makes the issue worse especially when you do not like to
      have humans intervention.
      <br>
      <br>
      <br>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
Idr mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Idr@ietf.org">Idr@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/idr">https://www.ietf.org/mailman/listinfo/idr</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------070506060203000902020309--

From ju1738@att.com  Fri Jun 22 11:22:37 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 F349611E80AD; Fri, 22 Jun 2012 11:22:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.272
X-Spam-Level: 
X-Spam-Status: No, score=-106.272 tagged_above=-999 required=5 tests=[AWL=0.099, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, SARE_SUB_OBFU_Q1=0.227, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AcdokfpL03vj; Fri, 22 Jun 2012 11:22:34 -0700 (PDT)
Received: from nbfkord-smmo05.seg.att.com (nbfkord-smmo05.seg.att.com [209.65.160.92]) by ietfa.amsl.com (Postfix) with ESMTP id 37F6411E808C; Fri, 22 Jun 2012 11:22:34 -0700 (PDT)
Received: from unknown [144.160.20.145] (EHLO nbfkord-smmo05.seg.att.com) by nbfkord-smmo05.seg.att.com(mxl_mta-6.11.0-10) with ESMTP id ae7b4ef4.4dc14940.1038928.00-581.2893482.nbfkord-smmo05.seg.att.com (envelope-from <ju1738@att.com>);  Fri, 22 Jun 2012 18:22:34 +0000 (UTC)
X-MXL-Hash: 4fe4b7ea79e9af12-47e0413d48eefc472a51a820a15fdb092c0d2378
Received: from unknown [144.160.20.145] (EHLO mlpd192.enaf.sfdc.sbc.com) by nbfkord-smmo05.seg.att.com(mxl_mta-6.11.0-10) over TLS secured channel with ESMTP id 6e7b4ef4.0.1038911.00-468.2893422.nbfkord-smmo05.seg.att.com (envelope-from <ju1738@att.com>);  Fri, 22 Jun 2012 18:22:30 +0000 (UTC)
X-MXL-Hash: 4fe4b7e64943767e-c6f0041d8af840b2cfbab54ef5095598790e372b
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlpd192.enaf.sfdc.sbc.com (8.14.5/8.14.5) with ESMTP id q5MIMUtC012241; Fri, 22 Jun 2012 14:22:30 -0400
Received: from sflint02.pst.cso.att.com (sflint02.pst.cso.att.com [144.154.234.229]) by mlpd192.enaf.sfdc.sbc.com (8.14.5/8.14.5) with ESMTP id q5MIMMes012190 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 22 Jun 2012 14:22:25 -0400
Received: from MISOUT7MSGHUB9B.ITServices.sbc.com (misout7msghub9b.itservices.sbc.com [144.151.223.72]) by sflint02.pst.cso.att.com (RSA Interceptor); Fri, 22 Jun 2012 14:22:11 -0400
Received: from MISOUT7MSGUSR9I.ITServices.sbc.com ([144.151.223.56]) by MISOUT7MSGHUB9B.ITServices.sbc.com ([144.151.223.72]) with mapi id 14.02.0298.004; Fri, 22 Jun 2012 14:22:10 -0400
From: "UTTARO, JAMES" <ju1738@att.com>
To: "'Enke Chen'" <enkechen@cisco.com>, "robert@raszuk.net" <robert@raszuk.net>
Thread-Topic: [Idr] Fwd: [GROW] draft-ietf-grow-ops-reqs-for-bgp-error-handling-04
Thread-Index: Ac1Qh0AwzuLH5xBMSu2rz3aHemLX7wAGW8kZAADOS0A=
Date: Fri, 22 Jun 2012 18:22:10 +0000
Message-ID: <B17A6910EEDD1F45980687268941550FB1F97F@MISOUT7MSGUSR9I.ITServices.sbc.com>
References: <B17A6910EEDD1F45980687268941550FB1F5C0@MISOUT7MSGUSR9I.ITServices.sbc.com> <4FE495CD.7080604@raszuk.net> <4FE4B2AD.9050704@cisco.com>
In-Reply-To: <4FE4B2AD.9050704@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.70.151.80]
Content-Type: multipart/alternative; boundary="_000_B17A6910EEDD1F45980687268941550FB1F97FMISOUT7MSGUSR9IIT_"
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.20.145]
X-AnalysisOut: [v=1.0 c=1 a=dXkvp1zHZaMA:10 a=ofMgfj31e3cA:10 a=BLceEmwcHo]
X-AnalysisOut: [wA:10 a=ZRNLZ4dFUbCvG8UMqPvVAA==:17 a=AUd_NHdVAAAA:8 a=2cl]
X-AnalysisOut: [OPd4PAAAA:8 a=48vgC7mUAAAA:8 a=COAiZOjdOaZY4NTSpp4A:9 a=Cj]
X-AnalysisOut: [uIK1q_8ugA:10 a=JfD0Fch1gWkA:10 a=bDUki_mJ7DgA:10 a=lZB815]
X-AnalysisOut: [dzVvQA:10 a=yMhMjlubAAAA:8 a=SSmOFEACAAAA:8 a=_82lQTgo2F5v]
X-AnalysisOut: [O93CtvAA:9 a=gKO2Hq4RSVkA:10 a=UiCQ7L4-1S4A:10 a=hTZeC7Yk6]
X-AnalysisOut: [K0A:10]
X-Mailman-Approved-At: Fri, 22 Jun 2012 12:00:05 -0700
Cc: "idr@ietf.org List" <idr@ietf.org>, "grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] [Idr] Fwd: draft-ietf-grow-ops-reqs-for-bgp-error-handling-04
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jun 2012 18:22:37 -0000

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

+1..

Jim Uttaro

From: Enke Chen [mailto:enkechen@cisco.com]
Sent: Friday, June 22, 2012 2:00 PM
To: robert@raszuk.net
Cc: idr@ietf.org List; grow@ietf.org; UTTARO, JAMES; Enke Chen
Subject: Re: [Idr] Fwd: [GROW] draft-ietf-grow-ops-reqs-for-bgp-error-handl=
ing-04

Hi, folks:

It might help the discussion to refresh ourselves about several large outag=
es in the last few years that prompted the work on the error handling requi=
rements and solutions:

   o issue with AS4_PATH that resulted in session resets multiple hops away=
 (two separate incidents)
   o session reset triggered by a single route with a new attribute

I remember that Rob had a presentation at the NANOG on the topic.

-- Enke

On 6/22/12 8:57 AM, Robert Raszuk wrote:
Jim,


We could as easily without any change to BGP use BGP Persistence to
maintain the paths except for the ones that have the invalid
attribute.. This is the simpler method, has the benefit of not
changing BGP, or educating the world on the nuances of the changes
etc...
+

Why wouldn't we simply let the session fail and then use BGP Persistence
or GR ;)

Please observe that when the session is down you are not receiving withdraw=
s or new best paths for those "good" prefixes (maybe 99% of them) which did=
 not have any errors in their respective update messages.

Equating it with persistence proposal is therefor highly incorrect.


I also do not fully understand "treat as withdraw" does this meant that
the peer who has received an update with P1-PN with malformed attr then
initiate a withdrawal to all of its peers?  Or simply assume that the
paths have been received as a message?  Some sample topologies as to how
this works would be a good addition to this section..

The speaker reacting on an error which can be addressed by "treat-as-withdr=
aw" invalidates locally those prefixes received in the update message, runs=
 local best path and as result if no other path is found withdraws those pr=
efixes from all peers it has previously sent them to.


I am not in support of solutions which create a scenario where BGP
cannot recover without human intervention.

I think no one is. But we are - I think - not there yet for the routers to =
automatically fix their bugs, but only automatically signalling them the re=
quested action ;(.

> Nothing is going to get people's attention like a failed BGP
> Session..

True statement. But the entire assumption behind treat-as-withdraw is that =
your ops scripts parse the syslog messages indicating the issue to NOC with=
 the same red color and buzz as bgp session down. Of course you need to rew=
ork your ops scripts/alarms for that to happen.

Rgs,
R.

PS.

Note that if the main BGP session is down (like in the persistence case) BG=
P Operational Messages can not any longer be exchanged between peers as TCP=
 connection could have been reset (if no multisession is used and if we are=
 talking about single SAFI). That just makes the issue worse especially whe=
n you do not like to have humans intervention.






_______________________________________________

Idr mailing list

Idr@ietf.org<mailto:Idr@ietf.org>

https://www.ietf.org/mailman/listinfo/idr


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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 12 (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;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";
	color:black;}
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;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";
	color:black;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;
	color:black;}
span.EmailStyle19
	{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 bgcolor=3D"white" lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&#43;1..
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Jim Uttaro<o:p></o:p></sp=
an></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;;color:windowtext">From:</span></b><spa=
n style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif=
&quot;;color:windowtext"> Enke Chen [mailto:enkechen@cisco.com]
<br>
<b>Sent:</b> Friday, June 22, 2012 2:00 PM<br>
<b>To:</b> robert@raszuk.net<br>
<b>Cc:</b> idr@ietf.org List; grow@ietf.org; UTTARO, JAMES; Enke Chen<br>
<b>Subject:</b> Re: [Idr] Fwd: [GROW] draft-ietf-grow-ops-reqs-for-bgp-erro=
r-handling-04<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Hi, folks:<br>
<br>
It might help the discussion to refresh ourselves about several large outag=
es in the last few years that prompted the work on the error handling requi=
rements and solutions:<br>
<br>
&nbsp;&nbsp; o issue with AS4_PATH that resulted in session resets multiple=
 hops away (two separate incidents)<br>
&nbsp;&nbsp; o session reset triggered by a single route with a new attribu=
te<br>
<br>
I remember that Rob had a presentation at the NANOG on the topic.<br>
<br>
-- Enke<br>
<br>
On 6/22/12 8:57 AM, Robert Raszuk wrote: <o:p></o:p></p>
<p class=3D"MsoNormal">Jim, <br>
<br>
<br>
<o:p></o:p></p>
<p class=3D"MsoNormal">We could as easily without any change to BGP use BGP=
 Persistence to
<br>
maintain the paths except for the ones that have the invalid <br>
attribute.. This is the simpler method, has the benefit of not <br>
changing BGP, or educating the world on the nuances of the changes <br>
etc&#8230; <o:p></o:p></p>
<p class=3D"MsoNormal">&#43; <br>
<br>
<o:p></o:p></p>
<p class=3D"MsoNormal">Why wouldn&#8217;t we simply let the session fail an=
d then use BGP Persistence
<br>
or GR ;) <o:p></o:p></p>
<p class=3D"MsoNormal"><br>
Please observe that when the session is down you are not receiving withdraw=
s or new best paths for those &quot;good&quot; prefixes (maybe 99% of them)=
 which did not have any errors in their respective update messages.
<br>
<br>
Equating it with persistence proposal is therefor highly incorrect. <br>
<br>
<br>
<o:p></o:p></p>
<p class=3D"MsoNormal">I also do not fully understand &#8220;treat as withd=
raw&#8221; does this meant that
<br>
the peer who has received an update with P1-PN with malformed attr then <br=
>
initiate a withdrawal to all of its peers?&nbsp; Or simply assume that the =
<br>
paths have been received as a message?&nbsp; Some sample topologies as to h=
ow <br>
this works would be a good addition to this section.. <o:p></o:p></p>
<p class=3D"MsoNormal"><br>
The speaker reacting on an error which can be addressed by &quot;treat-as-w=
ithdraw&quot; invalidates locally those prefixes received in the update mes=
sage, runs local best path and as result if no other path is found withdraw=
s those prefixes from all peers it has previously
 sent them to. <br>
<br>
<br>
<o:p></o:p></p>
<p class=3D"MsoNormal">I am not in support of solutions which create a scen=
ario where BGP
<br>
cannot recover without human intervention. <o:p></o:p></p>
<p class=3D"MsoNormal"><br>
I think no one is. But we are - I think - not there yet for the routers to =
automatically fix their bugs, but only automatically signalling them the re=
quested action ;(.
<br>
<br>
&gt; Nothing is going to get people&#8217;s attention like a failed BGP <br=
>
&gt; Session.. <br>
<br>
True statement. But the entire assumption behind treat-as-withdraw is that =
your ops scripts parse the syslog messages indicating the issue to NOC with=
 the same red color and buzz as bgp session down. Of course you need to rew=
ork your ops scripts/alarms for
 that to happen. <br>
<br>
Rgs, <br>
R. <br>
<br>
PS. <br>
<br>
Note that if the main BGP session is down (like in the persistence case) BG=
P Operational Messages can not any longer be exchanged between peers as TCP=
 connection could have been reset (if no multisession is used and if we are=
 talking about single SAFI). That
 just makes the issue worse especially when you do not like to have humans =
intervention.
<br>
<br>
<br>
<br>
<br>
<br>
<o:p></o:p></p>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>Idr mailing list<o:p></o:p></pre>
<pre><a href=3D"mailto:Idr@ietf.org">Idr@ietf.org</a><o:p></o:p></pre>
<pre><a href=3D"https://www.ietf.org/mailman/listinfo/idr">https://www.ietf=
.org/mailman/listinfo/idr</a><o:p></o:p></pre>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_B17A6910EEDD1F45980687268941550FB1F97FMISOUT7MSGUSR9IIT_--

From rjs@rob.sh  Sat Jun 23 14:04:26 2012
Return-Path: <rjs@rob.sh>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B3E9521F8555 for <grow@ietfa.amsl.com>; Sat, 23 Jun 2012 14:04:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.372
X-Spam-Level: 
X-Spam-Status: No, score=-2.372 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SARE_SUB_OBFU_Q1=0.227]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pR6kKWRcoPaH for <grow@ietfa.amsl.com>; Sat, 23 Jun 2012 14:04:26 -0700 (PDT)
Received: from cappuccino.rob.sh (cappuccino.rob.sh [IPv6:2001:b98:201:101::10:cafe]) by ietfa.amsl.com (Postfix) with ESMTP id 2246521F854E for <grow@ietf.org>; Sat, 23 Jun 2012 14:04:25 -0700 (PDT)
Received: from [93.97.180.64] (helo=lait.config) by cappuccino.rob.sh with esmtpa (Exim 4.72) (envelope-from <rjs@rob.sh>) id 1SiXTu-0003DK-Px; Sat, 23 Jun 2012 22:02:58 +0100
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=us-ascii
From: Rob Shakir <rjs@rob.sh>
In-Reply-To: <DCC302FAA9FE5F4BBA4DCAD46569377917449AF235@PRVPEXVS03.corp.twcable.com>
Date: Sat, 23 Jun 2012 22:04:18 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <F8659490-D1B2-477D-ADCC-EC6FD7AD073A@rob.sh>
References: <CAL9jLabOs02rOti4tezaZiHyiOD2f9vAhsoE9c-afFb4J1xYXQ@mail.gmail.com> <DCC302FAA9FE5F4BBA4DCAD46569377917449AF235@PRVPEXVS03.corp.twcable.com>
To: "George, Wes" <wesley.george@twcable.com>
X-Mailer: Apple Mail (2.1257)
Cc: "grow@ietf.org grow@ietf.org" <grow@ietf.org>, "grow-chairs@tools.ietf.org" <grow-chairs@tools.ietf.org>
Subject: Re: [GROW] WGLC: draft-ietf-grow-ops-reqs-for-bgp-error-handling-04
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 23 Jun 2012 21:04:26 -0000

Hi Wes,

Thanks for the comments.

On 19 Jun 2012, at 16:05, George, Wes wrote:

> I've read this draft and I think it is useful and ready to proceed.
> Two minor comments:
>=20
> In section 4, it may be useful to specifically note the need for a =
flag, trap, or other notification method (to the user, rather than to =
the neighbor) to identify when BGP is in the process of recovering RIB =
consistency, including which routes are considered inconsistent (if this =
info is available). While section 6 discusses the need for more =
information about the state of BGP when it is recovering from these =
errors, I saw no reference to this specific item. Since this is likely =
to be a transient state, it is also helpful to log this information to =
aid in root cause analysis of transient problems.

This sounds like a good addition -- I'll add a statement regarding this =
into the -05 version of the draft.

> Also, there are a lot of uses of RFC2119 words in ways that could be =
interpreted as normative despite the lack of a reference to 2119. It may =
be useful to either go ahead and make them so (all caps, include RFC2119 =
boilerplate) or to consider alternate words to avoid confusion. While =
this is an informational document and not a protocol specification, =
there are a lot of specific requirements of what we are expecting =
changes to the implementation to do and not do such that normative words =
would likely be helpful both to implementers and to those who may follow =
this draft with one to make protocol changes to address the requirements =
set forth.

I'd be interested in further comments on this -- the intention of the =
document originally was to frame the problem space, as well as put =
forward requirements for solutions. If there is value in putting forward =
these requirements with 2119 wording, then I'll go ahead and do so.

Kind regards,
r.=

From rjs@rob.sh  Sat Jun 23 14:22:35 2012
Return-Path: <rjs@rob.sh>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2C13321F85BD for <grow@ietfa.amsl.com>; Sat, 23 Jun 2012 14:22:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.372
X-Spam-Level: 
X-Spam-Status: No, score=-2.372 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SARE_SUB_OBFU_Q1=0.227]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9LMS5vtud2nF for <grow@ietfa.amsl.com>; Sat, 23 Jun 2012 14:22:34 -0700 (PDT)
Received: from cappuccino.rob.sh (cappuccino.rob.sh [IPv6:2001:b98:201:101::10:cafe]) by ietfa.amsl.com (Postfix) with ESMTP id 8F92C21F847B for <grow@ietf.org>; Sat, 23 Jun 2012 14:22:34 -0700 (PDT)
Received: from [93.97.180.64] (helo=lait.config) by cappuccino.rob.sh with esmtpa (Exim 4.72) (envelope-from <rjs@rob.sh>) id 1SiXlW-0003Fj-5C; Sat, 23 Jun 2012 22:21:10 +0100
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=iso-8859-1
From: Rob Shakir <rjs@rob.sh>
In-Reply-To: <CAO48Bk9ZsubfcuLhf5EUx9bKF+XdmWO7U1Scf6gwGOgsEfFcXw@mail.gmail.com>
Date: Sat, 23 Jun 2012 22:22:31 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <879F731E-DAC2-47C4-B733-9230AB37EF5D@rob.sh>
References: <CAL9jLabOs02rOti4tezaZiHyiOD2f9vAhsoE9c-afFb4J1xYXQ@mail.gmail.com> <DCC302FAA9FE5F4BBA4DCAD46569377917449AF235@PRVPEXVS03.corp.twcable.com> <CAO48Bk_O9ka4mf1SMcGh9kpbbNL5=+cfe3eGU5sOZoBaAVY9kw@mail.gmail.com> <7309FCBCAE981B43ABBE69B31C8D213921C2341341@EUSAACMS0701.eamcs.ericsson.se> <CAO48Bk9ZsubfcuLhf5EUx9bKF+XdmWO7U1Scf6gwGOgsEfFcXw@mail.gmail.com>
To: Pedro Andres Aranda Gutierrez <paaguti@gmail.com>
X-Mailer: Apple Mail (2.1257)
Cc: "grow@ietf.org grow@ietf.org" <grow@ietf.org>, grow-chairs@tools.ietf.org
Subject: Re: [GROW] WGLC: draft-ietf-grow-ops-reqs-for-bgp-error-handling-04
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 23 Jun 2012 21:22:35 -0000

Hi Pedro,

On 21 Jun 2012, at 07:22, Pedro Andres Aranda Gutierrez wrote:

> OK, then let's state that operational messages (DUMP with malformed
> packet) shall be used to notify the neighbor. The ideal scenario for
> me is:
>=20
> 1.- Someone sends me a stinking packet and resets my router: I'm able
> to notify him back automatically and then, if he doesn't react I can
> a) shut the session down and b) ask him why he didn't react.
>=20
> 2.- I'm sending stinking packets: I receive a trap after I sent the
> first and I can shut the router/session down and rollback any changes
> or investigate where that stinking packet came from, and why it was
> rejected.
>=20
> I think we have still not learnt from the 2009 incidents, where it
> took more than 6 hours to bring the situation back to normal and
> that's a pity.

I think we have learnt from these incidents. During these incidents =
there were significant problems because sessions were torn down, and =
hence long-lived outages ensued. As is discussed at some length in the =
draft, this is not desirable for some operators, and in some operational =
deployments. The requirements outlined in this document are intended to =
provide means by which an implementation may balance the risk of =
inconsistency of routing information against preserving network =
operation. Primarily, therefore the requirements work out how to =
minimise the impact to overall network integrity during these cases, and =
then how to give operators much better visibility into what's happening.

It should be noted that where incidents that cause erroneous UPDATE =
messages occur today, a session MUST be torn down - and therefore a =
service outage is guaranteed for the subset of routing information =
carried by this session. Therefore your >6hr period is an outage, rather =
than a period of degraded service operation.

In both the cases that you have described, it seems like the assumption =
has been made that the advertising speaker is directly responsible for =
the erroneous nature of the UPDATE message. If we look at the AS4_PATH =
issue that we had in the DFZ a few years ago, the speaker that sent the =
UPDATE message was not responsible for the malformed contents of the =
attribute. In this case, there is little that the advertising speaker =
can actually do when one lets him know that he's sending "stinking =
packets".

If there are specific requirements that you don't feel are addressed in =
this document (particularly around the logging mechanisms), it would be =
great to hear about them. I've been working with a relatively large =
number of operators (many of whom do not not participate directly in the =
standards development process) and feel that this document is a good =
representation of these requirements.

Kind regards,
r.=

From rjs@rob.sh  Sat Jun 23 14:33:36 2012
Return-Path: <rjs@rob.sh>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AD31021F85E5; Sat, 23 Jun 2012 14:33:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.372
X-Spam-Level: 
X-Spam-Status: No, score=-2.372 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SARE_SUB_OBFU_Q1=0.227]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Va7vNm2xENnO; Sat, 23 Jun 2012 14:33:36 -0700 (PDT)
Received: from cappuccino.rob.sh (cappuccino.rob.sh [IPv6:2001:b98:201:101::10:cafe]) by ietfa.amsl.com (Postfix) with ESMTP id CB00321F85E3; Sat, 23 Jun 2012 14:33:35 -0700 (PDT)
Received: from [93.97.180.64] (helo=lait.config) by cappuccino.rob.sh with esmtpa (Exim 4.72) (envelope-from <rjs@rob.sh>) id 1SiXwA-0003KD-J9; Sat, 23 Jun 2012 22:32:10 +0100
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=iso-8859-1
From: Rob Shakir <rjs@rob.sh>
In-Reply-To: <4FE4B2AD.9050704@cisco.com>
Date: Sat, 23 Jun 2012 22:33:32 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <C48797E6-DEAB-43F8-ABEA-8FE71A712FBA@rob.sh>
References: <B17A6910EEDD1F45980687268941550FB1F5C0@MISOUT7MSGUSR9I.ITServices.sbc.com> <4FE495CD.7080604@raszuk.net> <4FE4B2AD.9050704@cisco.com>
To: Enke Chen <enkechen@cisco.com>
X-Mailer: Apple Mail (2.1257)
Cc: "idr@ietf.org List" <idr@ietf.org>, "grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] [Idr] Fwd: draft-ietf-grow-ops-reqs-for-bgp-error-handling-04
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 23 Jun 2012 21:33:36 -0000

On 22 Jun 2012, at 19:00, Enke Chen wrote:

> Hi, folks:
>=20
> It might help the discussion to refresh ourselves about several large =
outages in the last few years that prompted the work on the error =
handling requirements and solutions:
>=20
>    o issue with AS4_PATH that resulted in session resets multiple hops =
away (two separate incidents)
>    o session reset triggered by a single route with a new attribute
>=20
> I remember that Rob had a presentation at the NANOG on the topic.

Hi Enke,

Thanks for this message. This work is absolutely motivated by incidents =
in live networks (both those that have publicly been described and those =
in private network deployment that are not as public).

I have talked to this work a number of times across a number of operator =
forums:

- NANOG51 / LINX / UKNOF:
	=
http://www.nanog.org/meetings/nanog51/presentations/Tuesday/shakir-bgp-err=
or-handling_rob-shakir-FINAL2.pdf
	=
http://www.nanog.org/meetings/nanog51/presentations/Tuesday/bgp_err_hdling=
.wmv
- Netnod:
	=
http://rob.sh/files/RJS-Reinforcing_the_Kitchen_Sink-NETNOD-Autumn2011.pdf=


The motivation for this work is improving the robustness of real-world =
networks, where the current error handling behaviour does not match the =
situation and deployment in which the protocol is deployed.=20

As I have voiced in other posts to both the IDR and GROW mailing lists, =
these requirements put forward means to be able to balance the risk of =
things not being 100% correct in terms of protocol operation against the =
threat of complete outages for all routing information carried via a BGP =
session. If these risks are not acceptable to an operator, then the =
solutions implemented in answer to these requirements do not need to be =
enabled - however, at the moment, the protocol is completely constrained =
in terms of its behaviour -- sessions are torn down regardless of the =
impact of their failure.

Kind regards,
r.=

From rjs@rob.sh  Sat Jun 23 15:39:07 2012
Return-Path: <rjs@rob.sh>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0B08221F862F; Sat, 23 Jun 2012 15:39:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.372
X-Spam-Level: 
X-Spam-Status: No, score=-2.372 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SARE_SUB_OBFU_Q1=0.227]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZKuut4YW5ycK; Sat, 23 Jun 2012 15:39:06 -0700 (PDT)
Received: from cappuccino.rob.sh (cappuccino.rob.sh [IPv6:2001:b98:201:101::10:cafe]) by ietfa.amsl.com (Postfix) with ESMTP id 94AF721F8615; Sat, 23 Jun 2012 15:39:05 -0700 (PDT)
Received: from [93.97.180.64] (helo=lait.config) by cappuccino.rob.sh with esmtpa (Exim 4.72) (envelope-from <rjs@rob.sh>) id 1SiYxZ-0003Yh-HM; Sat, 23 Jun 2012 23:37:41 +0100
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=windows-1252
From: Rob Shakir <rjs@rob.sh>
In-Reply-To: <B17A6910EEDD1F45980687268941550FB1F5C0@MISOUT7MSGUSR9I.ITServices.sbc.com>
Date: Sat, 23 Jun 2012 23:39:03 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <52CBEC1F-49E6-4656-A617-CAB7304479F0@rob.sh>
References: <B17A6910EEDD1F45980687268941550FB1F5C0@MISOUT7MSGUSR9I.ITServices.sbc.com>
To: "UTTARO, JAMES" <ju1738@att.com>
X-Mailer: Apple Mail (2.1257)
Cc: 'idr wg' <idr@ietf.org>, "'grow@ietf.org'" <grow@ietf.org>
Subject: Re: [GROW] draft-ietf-grow-ops-reqs-for-bgp-error-handling-04
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 23 Jun 2012 22:39:07 -0000

Hi Jim,

Thanks very much for the detailed review of this document.

On 22 Jun 2012, at 15:56, UTTARO, JAMES wrote:

> Rob,
> =20
> Following find my comments..
> =20
> Thanks,
>                 Jim Uttaro
> =20
> General Comment,
> =20
> =46rom a philosophical perspective I agree with the goals of this =
draft but I do not agree with an approach that maintains a session in =
the face of a failure in the machinery. This is a bottom up approach =
which will always be a day late and a dollar short as we continue to =
patch what it means to be a viable session.. I believe the proper =
approach to meet your reqs ( and mine too!!! ) is a top down which does =
not change the BGP behavior but changes the response to that behavior.. =
The reality of today=92s BGP fields of use which are many and varied is =
that the control and the forwarding paths are orthogonal, the state =
being carried is not always paths as we usually consider them. Examples =
include RT-C, Flowspec which are used to create PWs and simulate an IGP =
etc=85 I do not believe changing the behavior of BGP session viability =
machinery to accomplish maintaining valid forwarding in the face of a =
control plane failure is the correct approach
> =20
> The draft addresses a very important error condition but ( Update =
Error ).. This should be expanded to other areas where the failure of a =
session does not indicate that a subset or all of the routing state =
learned over said session is invalid.. I think the draft should address =
this directly.. Are the changes here configurable? Can I turn this off =
if I do not want this behavior for certain topologies, AFs?

The scope for this draft was particularly to handle errors that occurred =
in the DFZ (and in some private networks) where UPDATE messages with =
malformed contents representing a subset of NLRI carried via a session =
(1 prefix in numerous cases) resulted in complete failure of these =
sessions. Particularly, errors where it was a malformed optional =
transitive attribute that was "tunnelled" across multiple speakers who =
did not parse it were particularly destructive in the DFZ. Jonathan =
Oddy, Andy Davidson and myself spent some effort analysing one of these =
incidents back in 2008/2009 -- =
http://mailman.nanog.org/pipermail/nanog/2009-January/006816.html.=20

One of the complexities in this problem space is that there are multiple =
underlying philosophies as to how such error behaviour should be =
handled:

1. Conservative -- any error in messages received from a neighbour are =
indicative that it is not a viable route to any prefix it advertises. =
Therefore where error conditions occur, disconnect and remove all routes =
from the neighbour from the RIB.

2. Balanced risk -- some errors are not indicative of an error on the =
remote speaker, or are localised to specific NLRI/prefixes that are =
propagated via this speaker. Therefore take a balanced approach of =
applying error handling mechanisms to those NLRI, but continue to trust =
the integrity of the speaker for the remainder of routing information.

Essentially, this draft's scope was to explain the requirements that =
exist to manage the risk of taking the latter view. At the moment, there =
is a risk to an operator presented by the first (a malformed UPDATE may =
break the BGP sessions that run between their PEs and RRs, or those that =
propagate their routes to the Internet DFZ, and cause a service outage), =
and there is no option to balance the impact of that risk against the =
impact of BGP being incorrect for a subset of prefixes propagated via =
those sessions.

I would expect all solutions implemented in response to these =
requirements to be optional. If the risk of incorrectness is =
unacceptable to you/an operator, then you should absolutely not enable =
any of these mechanisms. In a number of networks that I have operated, =
designed and architected, I am prepared to accept the risk of =
incorrectness, as I consider it acceptable when compared to the risk of =
complete service outages in terms of impact to my customers during such =
incidents. At the moment, without the work described through the =
requirements outlined in this draft I do not have the means to make that =
call...

>  Abstract
> =20
> Can the scope be expanded? There are other failure modes, i.e Timer =
Expiry which today is not considered a failure mode. In reality what I =
have seen is that timer expiry occurs due to the fact that BGP threads =
cannot be serviced in a timely manner.  I think it would be best if we =
could put it all on the table..
> =20
> I do think that this draft should bound the solution space. At the =
minimum the solutions proposed should meet a minimum set of the =
operators criteria in terms of managing the network, convergence, =
persistence, churn, forwarding impact etc=85 =20

I think there was clear consensus amongst operators with whom I have =
spoken to work on the problem space of erroneous UPDATEs - particularly =
in response to observed incidents. The very real risk of expanding the =
scope of this document even further to handle any error in the BGP =
protocol is that we spend another few years cataloguing such conditions, =
whilst doing nothing about the ones that we have identified.

>  Section 1.1
> =20
> The following paragraph is based on the premise that the session being =
=93down=94 results in a large impact.. This is certainly true for =
today=92s implementations which use the session ( Control Plane =
Construct ) to determine the viability of the forwarding state learned =
over said session. There are cases where this is the session and =
forwarding are parallel, but in many more cases control and forwarding =
planes are orthogonal.. I think we need to re-consider this assumption =
for many of the services BGP is being used for and base the response to =
error conditions on this reality..
> =20
> =93 Both within Internet and multi-service routing architectures, a
>    number of BGP sessions propagate a large proportion of the required
>    routing information for network operation.  For Internet routing,
>    these are typically BGP sessions which propagate the global routing
>    table to an AS - failure of these sessions may have a large impact =
on
>    network service, based on a single erroneous update.  In an multi-
>    service environment, typical deployments utilise a small number of
>    core-facing BGP sessions, typically towards route reflector =
devices.
>    Failure of these sessions may also result in a large impact to
>    network operation.  Clearly, the avoidance of conditions requiring
>    these sessions to fail is of great utility to any network operator,
>   and provides further motivation for the revision of the existing
>    behaviour. =93

I do not understand what the assertion that you are making here is. =
Please could you explain it to me? The errors that are being discussed =
relate to where a subset of NLRI are advertised within an erroneous =
UPDATE message, and the resulting impact of the current protocol =
behaviour on all other NLRI carried on that session. The cases of IP =
"transit" sessions, and RR-PE sessions are only examples of cases where =
there is a large amount of routing information carried over a single =
session - and hence it is of utility to avoid these sessions failing =
where they do not necessarily need to based on the impact to overall =
network service.

This point (to me anyway) seems entirely related to the control-plane -- =
it points out that an operator has cases where one really wants to keep =
the impact of errors down to the particular subset of routing =
information that is affected. This point is entirely in the protocol, =
rather than implying any behaviour about forwarding (i.e., no =
implication is made that the NLRI identified as carried in the erroneous =
UPDATE are installed in the FIB, but rather that all *other* NLRI =
continue to be installed in the RIB).

I'll work through the points that you have made in this mail -- but I'd =
like to respond with a specific point here comparing more targeted =
handling of errors in UPDATE messages with persistence-type approaches.=20=


- Persistence/hold-up is not acceptable to all operators in all =
deployments. Particularly, where no liveliness detection mechanism for =
the next-hop is available (i.e., where it is not possible or practical =
to determine the NH's reachability in the forwarding plane other than =
with with the routing protocol itself) then one would not want to accept =
the risk of running persistence.

- Therefore, an operator has two options for these deployments -- stick =
with the error handling behaviour that is available in BGP right now, =
which gives him no flexibility in terms of focusing responses to errors =
in a manner that is proportional to the actual error; or alternatively, =
accept some additional complexity and risk such that particular error =
handling is targeted to the NLRI that are contained in an UPDATE message =
that is found to be erroneous.

Given there are deployments where I cannot deploy persistence (e.g., =
towards an Internet network peer on an IXP where deployment of BFD/OAM =
mechanisms are very limited so BGP really tells me whether the other =
peer is "there" at all) yet in these cases I do not want to affect all =
NLRI when one erroneous UPDATE is received then it would seem that I =
need answers to the requirements in this draft.=20

Your e-mail seems to imply that you do not have cases where you will not =
be able to deploy persistence and that you are accepting of =
session-level error handling in these cases. Would this be a fair =
assessment?

Kind regards,
r.


From ju1738@att.com  Sat Jun 23 19:06:52 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 27E3621F8629; Sat, 23 Jun 2012 19:06:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.262
X-Spam-Level: 
X-Spam-Status: No, score=-106.262 tagged_above=-999 required=5 tests=[AWL=0.110, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_SUB_OBFU_Q1=0.227, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8tcJn1YHEh7m; Sat, 23 Jun 2012 19:06:48 -0700 (PDT)
Received: from nbfkord-smmo04.seg.att.com (nbfkord-smmo04.seg.att.com [209.65.160.86]) by ietfa.amsl.com (Postfix) with ESMTP id 6EAA521F8530; Sat, 23 Jun 2012 19:06:46 -0700 (PDT)
Received: from unknown [144.160.20.145] (EHLO mlpd192.enaf.sfdc.sbc.com) by nbfkord-smmo04.seg.att.com(mxl_mta-6.11.0-10) over TLS secured channel with ESMTP id 53676ef4.0.1804672.00-403.4967013.nbfkord-smmo04.seg.att.com (envelope-from <ju1738@att.com>);  Sun, 24 Jun 2012 02:06:46 +0000 (UTC)
X-MXL-Hash: 4fe67636001aba5c-89ad0036663afc8958bde267312f1609874262e4
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlpd192.enaf.sfdc.sbc.com (8.14.5/8.14.5) with ESMTP id q5O26jPR023681; Sat, 23 Jun 2012 22:06:45 -0400
Received: from sflint02.pst.cso.att.com (sflint02.pst.cso.att.com [144.154.234.229]) by mlpd192.enaf.sfdc.sbc.com (8.14.5/8.14.5) with ESMTP id q5O26ZQp023626 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 23 Jun 2012 22:06:40 -0400
Received: from MISOUT7MSGHUB9A.ITServices.sbc.com (misout7msghub9a.itservices.sbc.com [144.151.223.62]) by sflint02.pst.cso.att.com (RSA Interceptor); Sat, 23 Jun 2012 22:06:30 -0400
Received: from MISOUT7MSGUSR9I.ITServices.sbc.com ([144.151.223.56]) by MISOUT7MSGHUB9A.ITServices.sbc.com ([144.151.223.62]) with mapi id 14.02.0298.004; Sat, 23 Jun 2012 22:06:29 -0400
From: "UTTARO, JAMES" <ju1738@att.com>
To: "'Rob Shakir'" <rjs@rob.sh>
Thread-Topic: draft-ietf-grow-ops-reqs-for-bgp-error-handling-04
Thread-Index: Ac1Qh0AwzuLH5xBMSu2rz3aHemLX7wBK0QmAAAIbFGA=
Date: Sun, 24 Jun 2012 02:06:29 +0000
Message-ID: <B17A6910EEDD1F45980687268941550FB20F89@MISOUT7MSGUSR9I.ITServices.sbc.com>
References: <B17A6910EEDD1F45980687268941550FB1F5C0@MISOUT7MSGUSR9I.ITServices.sbc.com> <52CBEC1F-49E6-4656-A617-CAB7304479F0@rob.sh>
In-Reply-To: <52CBEC1F-49E6-4656-A617-CAB7304479F0@rob.sh>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.70.199.211]
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.20.145]
X-AnalysisOut: [v=1.0 c=1 a=Tyf1anlMpZ0A:10 a=81eWbNQ_HDgA:10 a=ofMgfj31e3]
X-AnalysisOut: [cA:10 a=BLceEmwcHowA:10 a=kj9zAlcOel0A:10 a=ZRNLZ4dFUbCvG8]
X-AnalysisOut: [UMqPvVAA==:17 a=48vgC7mUAAAA:8 a=Z_GzSN2XAAAA:8 a=WhWR3eUb]
X-AnalysisOut: [6aCqb_apkfMA:9 a=CjuIK1q_8ugA:10 a=RnEgMHWdb3IA:10 a=lZB81]
X-AnalysisOut: [5dzVvQA:10 a=YJInicgDRrRRWZgQ:21 a=J7eEVSSeIKoLk4Hk:21]
Cc: 'idr wg' <idr@ietf.org>, "'grow@ietf.org'" <grow@ietf.org>
Subject: Re: [GROW] draft-ietf-grow-ops-reqs-for-bgp-error-handling-04
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 24 Jun 2012 02:06:52 -0000

Rob,

	Comments In-Line...

Thanks,
	Jim Uttaro

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

Hi Jim,

Thanks very much for the detailed review of this document.

On 22 Jun 2012, at 15:56, UTTARO, JAMES wrote:

> Rob,
> =20
> Following find my comments..
> =20
> Thanks,
>                 Jim Uttaro
> =20
> General Comment,
> =20
> From a philosophical perspective I agree with the goals of this draft but=
 I do not agree with an approach that maintains a session in the face of a =
failure in the machinery. This is a bottom up approach which will always be=
 a day late and a dollar short as we continue to patch what it means to be =
a viable session.. I believe the proper approach to meet your reqs ( and mi=
ne too!!! ) is a top down which does not change the BGP behavior but change=
s the response to that behavior.. The reality of today's BGP fields of use =
which are many and varied is that the control and the forwarding paths are =
orthogonal, the state being carried is not always paths as we usually consi=
der them. Examples include RT-C, Flowspec which are used to create PWs and =
simulate an IGP etc... I do not believe changing the behavior of BGP sessio=
n viability machinery to accomplish maintaining valid forwarding in the fac=
e of a control plane failure is the correct approach
> =20
> The draft addresses a very important error condition but ( Update Error )=
.. This should be expanded to other areas where the failure of a session do=
es not indicate that a subset or all of the routing state learned over said=
 session is invalid.. I think the draft should address this directly.. Are =
the changes here configurable? Can I turn this off if I do not want this be=
havior for certain topologies, AFs?

The scope for this draft was particularly to handle errors that occurred in=
 the DFZ (and in some private networks) where UPDATE messages with malforme=
d contents representing a subset of NLRI carried via a session (1 prefix in=
 numerous cases) resulted in complete failure of these sessions. Particular=
ly, errors where it was a malformed optional transitive attribute that was =
"tunnelled" across multiple speakers who did not parse it were particularly=
 destructive in the DFZ. Jonathan Oddy, Andy Davidson and myself spent some=
 effort analysing one of these incidents back in 2008/2009 -- http://mailma=
n.nanog.org/pipermail/nanog/2009-January/006816.html.=20
[Jim U>] Got it..

One of the complexities in this problem space is that there are multiple un=
derlying philosophies as to how such error behaviour should be handled:

1. Conservative -- any error in messages received from a neighbour are indi=
cative that it is not a viable route to any prefix it advertises. Therefore=
 where error conditions occur, disconnect and remove all routes from the ne=
ighbour from the RIB.

[Jim U>] This is based on the current behavior of BGP.. If the NH is still =
viable you could allow the session to fall and persist the good state that =
has already been learned..

2. Balanced risk -- some errors are not indicative of an error on the remot=
e speaker, or are localised to specific NLRI/prefixes that are propagated v=
ia this speaker. Therefore take a balanced approach of applying error handl=
ing mechanisms to those NLRI, but continue to trust the integrity of the sp=
eaker for the remainder of routing information.

Essentially, this draft's scope was to explain the requirements that exist =
to manage the risk of taking the latter view. At the moment, there is a ris=
k to an operator presented by the first (a malformed UPDATE may break the B=
GP sessions that run between their PEs and RRs, or those that propagate the=
ir routes to the Internet DFZ, and cause a service outage), and there is no=
 option to balance the impact of that risk against the impact of BGP being =
incorrect for a subset of prefixes propagated via those sessions.
[Jim U>] Yes I have seen this..

I would expect all solutions implemented in response to these requirements =
to be optional. If the risk of incorrectness is unacceptable to you/an oper=
ator, then you should absolutely not enable any of these mechanisms. In a n=
umber of networks that I have operated, designed and architected, I am prep=
ared to accept the risk of incorrectness, as I consider it acceptable when =
compared to the risk of complete service outages in terms of impact to my c=
ustomers during such incidents. At the moment, without the work described t=
hrough the requirements outlined in this draft I do not have the means to m=
ake that call...
[Jim U>] I do not understand how it is possible to make this configurable o=
n a per session or AS basis..I would think all speakers participating in a =
routing context would have to adhere to the same rules for a consistent vie=
w across domains.. In my reading of the IDR draft it seems that it would be=
 a MUST.. Maybe I should not be considering that IDR draft as the actual re=
alization of the reqs..

>  Abstract
> =20
> Can the scope be expanded? There are other failure modes, i.e Timer Expir=
y which today is not considered a failure mode. In reality what I have seen=
 is that timer expiry occurs due to the fact that BGP threads cannot be ser=
viced in a timely manner.  I think it would be best if we could put it all =
on the table..
> =20
> I do think that this draft should bound the solution space. At the minimu=
m the solutions proposed should meet a minimum set of the operators criteri=
a in terms of managing the network, convergence, persistence, churn, forwar=
ding impact etc... =20

I think there was clear consensus amongst operators with whom I have spoken=
 to work on the problem space of erroneous UPDATEs - particularly in respon=
se to observed incidents. The very real risk of expanding the scope of this=
 document even further to handle any error in the BGP protocol is that we s=
pend another few years cataloguing such conditions, whilst doing nothing ab=
out the ones that we have identified.
[Jim U>] No doubt.. But  I have seen other errors that relate to overloadin=
g BGP, topological isolation etc... that have created huge outages in my ne=
twork.. So, My thinking is that we should try to consider all of the challe=
nges the protocol faces in terms of erroneous error conditions.=20

>  Section 1.1
> =20
> The following paragraph is based on the premise that the session being "d=
own" results in a large impact.. This is certainly true for today's impleme=
ntations which use the session ( Control Plane Construct ) to determine the=
 viability of the forwarding state learned over said session. There are cas=
es where this is the session and forwarding are parallel, but in many more =
cases control and forwarding planes are orthogonal.. I think we need to re-=
consider this assumption for many of the services BGP is being used for and=
 base the response to error conditions on this reality..
> =20
> " Both within Internet and multi-service routing architectures, a
>    number of BGP sessions propagate a large proportion of the required
>    routing information for network operation.  For Internet routing,
>    these are typically BGP sessions which propagate the global routing
>    table to an AS - failure of these sessions may have a large impact on
>    network service, based on a single erroneous update.  In an multi-
>    service environment, typical deployments utilise a small number of
>    core-facing BGP sessions, typically towards route reflector devices.
>    Failure of these sessions may also result in a large impact to
>    network operation.  Clearly, the avoidance of conditions requiring
>    these sessions to fail is of great utility to any network operator,
>   and provides further motivation for the revision of the existing
>    behaviour. "

I do not understand what the assertion that you are making here is. Please =
could you explain it to me? The errors that are being discussed relate to w=
here a subset of NLRI are advertised within an erroneous UPDATE message, an=
d the resulting impact of the current protocol behaviour on all other NLRI =
carried on that session. The cases of IP "transit" sessions, and RR-PE sess=
ions are only examples of cases where there is a large amount of routing in=
formation carried over a single session - and hence it is of utility to avo=
id these sessions failing where they do not necessarily need to based on th=
e impact to overall network service.
[Jim U>] The solution space here seems explicitly targeted to the internet =
IPV4 AF. Not sure if there is a dependency here on the control/forwarding p=
lanes being in parallel. I believe we need to consider all AFs that BGP is =
used for.. As the code that would be developed would be applicable to these=
 AF also ( I presume ). So as an example would be RT-C, is this solution ap=
plicable I don't know I am simply asking.. If we want to develop this and h=
ave it specific to the internet use case lets state that clearly. If not, t=
hen let's consider the other applications BGP supports..

This point (to me anyway) seems entirely related to the control-plane -- it=
 points out that an operator has cases where one really wants to keep the i=
mpact of errors down to the particular subset of routing information that i=
s affected. This point is entirely in the protocol, rather than implying an=
y behaviour about forwarding (i.e., no implication is made that the NLRI id=
entified as carried in the erroneous UPDATE are installed in the FIB, but r=
ather that all *other* NLRI continue to be installed in the RIB).
[Jim U>] See above.. My point is how can we ensure reliability across AFs..=
.There is no doubt that mal-formed updates are an issue I just do not know =
how they affect other AFs, in those case it may be more appropriate to tear=
 down and persist instead. Can we address these other use cases?

I'll work through the points that you have made in this mail -- but I'd lik=
e to respond with a specific point here comparing more targeted handling of=
 errors in UPDATE messages with persistence-type approaches.=20

- Persistence/hold-up is not acceptable to all operators in all deployments=
. Particularly, where no liveliness detection mechanism for the next-hop is=
 available (i.e., where it is not possible or practical to determine the NH=
's reachability in the forwarding plane other than with with the routing pr=
otocol itself) then one would not want to accept the risk of running persis=
tence.
[Jim U>] Agreed.. Persistence requires that the NH be viable.=20

- Therefore, an operator has two options for these deployments -- stick wit=
h the error handling behaviour that is available in BGP right now, which gi=
ves him no flexibility in terms of focusing responses to errors in a manner=
 that is proportional to the actual error; or alternatively, accept some ad=
ditional complexity and risk such that particular error handling is targete=
d to the NLRI that are contained in an UPDATE message that is found to be e=
rroneous.
[Jim U>] My concern here is that the entire support structure is based on s=
ession viability, the expectation here is that operators need to develop ne=
w approaches to understanding if there is a routing anomaly in their topolo=
gy and develop tools/procedures which are different.

Given there are deployments where I cannot deploy persistence (e.g., toward=
s an Internet network peer on an IXP where deployment of BFD/OAM mechanisms=
 are very limited so BGP really tells me whether the other peer is "there" =
at all) yet in these cases I do not want to affect all NLRI when one errone=
ous UPDATE is received then it would seem that I need answers to the requir=
ements in this draft.=20
[Jim U>] Agreed..=20

Your e-mail seems to imply that you do not have cases where you will not be=
 able to deploy persistence and that you are accepting of session-level err=
or handling in these cases. Would this be a fair assessment?
[Jim U>] My work primarily revolves around the following BGP use cases VPN =
( L2/L3 ), 3107, Multi-Cast, RT-C, Flowspec not Internet.. In these environ=
ments I would prefer that the session fail, persistence is activated, and w=
ell known procedures are used to correct the problem. I am in no way saying=
 that the use case described here for the internet application is not viabl=
e or the correct approach.. But the fact remains that the code base will be=
 used across all AFs and this solution requires different OpS/Troubleshooti=
ng knowledge and support. I would prefer consistency in the behavior..=20

Kind regards,
r.


From rjs@rob.sh  Sun Jun 24 02:09:55 2012
Return-Path: <rjs@rob.sh>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DD00E21F8633; Sun, 24 Jun 2012 02:09:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.072
X-Spam-Level: 
X-Spam-Status: No, score=-2.072 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, SARE_SUB_OBFU_Q1=0.227]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id j4pTdBvJouYB; Sun, 24 Jun 2012 02:09:49 -0700 (PDT)
Received: from cappuccino.rob.sh (cappuccino.rob.sh [IPv6:2001:b98:201:101::10:cafe]) by ietfa.amsl.com (Postfix) with ESMTP id E8D7621F862F; Sun, 24 Jun 2012 02:09:48 -0700 (PDT)
Received: from [93.97.180.64] (helo=lait.config) by cappuccino.rob.sh with esmtpa (Exim 4.72) (envelope-from <rjs@rob.sh>) id 1Siinw-0005pF-Gh; Sun, 24 Jun 2012 10:08:24 +0100
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=iso-8859-1
From: Rob Shakir <rjs@rob.sh>
In-Reply-To: <B17A6910EEDD1F45980687268941550FB20F89@MISOUT7MSGUSR9I.ITServices.sbc.com>
Date: Sun, 24 Jun 2012 10:09:46 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <FB4C2B5B-E935-4972-ACDD-151AF87DC26A@rob.sh>
References: <B17A6910EEDD1F45980687268941550FB1F5C0@MISOUT7MSGUSR9I.ITServices.sbc.com> <52CBEC1F-49E6-4656-A617-CAB7304479F0@rob.sh> <B17A6910EEDD1F45980687268941550FB20F89@MISOUT7MSGUSR9I.ITServices.sbc.com>
To: "UTTARO, JAMES" <ju1738@att.com>
X-Mailer: Apple Mail (2.1257)
Cc: 'idr wg' <idr@ietf.org>, "'grow@ietf.org'" <grow@ietf.org>
Subject: Re: [GROW] draft-ietf-grow-ops-reqs-for-bgp-error-handling-04
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 24 Jun 2012 09:09:55 -0000

Hi Jim,

Further comments in-line as [rjs].

On 24 Jun 2012, at 03:06, UTTARO, JAMES wrote:

> 1. Conservative -- any error in messages received from a neighbour are =
indicative that it is not a viable route to any prefix it advertises. =
Therefore where error conditions occur, disconnect and remove all routes =
from the neighbour from the RIB.
>=20
> [Jim U>] This is based on the current behavior of BGP.. If the NH is =
still viable you could allow the session to fall and persist the good =
state that has already been learned..

[rjs]: Absolutely, this is the current behaviour. The problem with =
taking a whole session down in this case is that you now take a risk of =
inconsistency for all NLRI across that session for the duration that you =
hold onto the learned NLRI. If one avoids being in the situation where =
the session is down (e.g., by applying treat-as-withdraw behaviour in =
cases where one can determine the NLRI) then all other NLRI on the =
session continue to be updated as they need to be. It is only the NLRI =
that were included in the erroneous UPDATE that may be affected for =
looping/black-holing.

> I would expect all solutions implemented in response to these =
requirements to be optional. If the risk of incorrectness is =
unacceptable to you/an operator, then you should absolutely not enable =
any of these mechanisms. In a number of networks that I have operated, =
designed and architected, I am prepared to accept the risk of =
incorrectness, as I consider it acceptable when compared to the risk of =
complete service outages in terms of impact to my customers during such =
incidents. At the moment, without the work described through the =
requirements outlined in this draft I do not have the means to make that =
call...
> [Jim U>] I do not understand how it is possible to make this =
configurable on a per session or AS basis..I would think all speakers =
participating in a routing context would have to adhere to the same =
rules for a consistent view across domains.. In my reading of the IDR =
draft it seems that it would be a MUST.. Maybe I should not be =
considering that IDR draft as the actual realization of the reqs..

[rjs]: The IDR draft is the solution for some of the requirements -- =
particularly those described in Section 3 of the GROW draft.

[rjs]: I do not see why this behaviour needs to be consistent across =
domains?

[rjs]: Essentially, if I receive an invalid UPDATE message, and apply =
treat-as-withdraw, if the advertising speaker did not know that this was =
erroneous then I end up with a different view of what is in the RIB than =
the advertising speaker does. If this was a prefix I had no other route =
to, then I may black-hole, if it was one where it was a more-specific of =
some larger prefix, then we end up with the potential for loops.

[rjs]: If I am prepared to accept the black-holing or loops for the NLRI =
in the erroneous UPDATE as a risk, in favour of keeping the remaining =
NLRI working (and being updated/withdrawn if they change), then this is =
a local decision and I do not need to imply any behaviour of the =
neighbouring domains.

>=20
>> Abstract
>>=20
>> Can the scope be expanded? There are other failure modes, i.e Timer =
Expiry which today is not considered a failure mode. In reality what I =
have seen is that timer expiry occurs due to the fact that BGP threads =
cannot be serviced in a timely manner.  I think it would be best if we =
could put it all on the table..
>>=20
>> I do think that this draft should bound the solution space. At the =
minimum the solutions proposed should meet a minimum set of the =
operators criteria in terms of managing the network, convergence, =
persistence, churn, forwarding impact etc... =20
>=20
> I think there was clear consensus amongst operators with whom I have =
spoken to work on the problem space of erroneous UPDATEs - particularly =
in response to observed incidents. The very real risk of expanding the =
scope of this document even further to handle any error in the BGP =
protocol is that we spend another few years cataloguing such conditions, =
whilst doing nothing about the ones that we have identified.
> [Jim U>] No doubt.. But  I have seen other errors that relate to =
overloading BGP, topological isolation etc... that have created huge =
outages in my network.. So, My thinking is that we should try to =
consider all of the challenges the protocol faces in terms of erroneous =
error conditions.=20

[rjs] Right, perhaps a better title for the draft would be "Operational =
Requirements for Enhanced Error Handling for UPDATE Messages in BGP-4" =
-- given that there were incidents that affected networks that =
particularly were focused on the errors in UPDATEs, it seemed logical =
that this was the place to start for this work.=20

>=20
>> Section 1.1
>>=20
>> The following paragraph is based on the premise that the session =
being "down" results in a large impact.. This is certainly true for =
today's implementations which use the session ( Control Plane Construct =
) to determine the viability of the forwarding state learned over said =
session. There are cases where this is the session and forwarding are =
parallel, but in many more cases control and forwarding planes are =
orthogonal.. I think we need to re-consider this assumption for many of =
the services BGP is being used for and base the response to error =
conditions on this reality..
>>=20
>> " Both within Internet and multi-service routing architectures, a
>>   number of BGP sessions propagate a large proportion of the required
>>   routing information for network operation.  For Internet routing,
>>   these are typically BGP sessions which propagate the global routing
>>   table to an AS - failure of these sessions may have a large impact =
on
>>   network service, based on a single erroneous update.  In an multi-
>>   service environment, typical deployments utilise a small number of
>>   core-facing BGP sessions, typically towards route reflector =
devices.
>>   Failure of these sessions may also result in a large impact to
>>   network operation.  Clearly, the avoidance of conditions requiring
>>   these sessions to fail is of great utility to any network operator,
>>  and provides further motivation for the revision of the existing
>>   behaviour. "
>=20
> I do not understand what the assertion that you are making here is. =
Please could you explain it to me? The errors that are being discussed =
relate to where a subset of NLRI are advertised within an erroneous =
UPDATE message, and the resulting impact of the current protocol =
behaviour on all other NLRI carried on that session. The cases of IP =
"transit" sessions, and RR-PE sessions are only examples of cases where =
there is a large amount of routing information carried over a single =
session - and hence it is of utility to avoid these sessions failing =
where they do not necessarily need to based on the impact to overall =
network service.
> [Jim U>] The solution space here seems explicitly targeted to the =
internet IPV4 AF. Not sure if there is a dependency here on the =
control/forwarding planes being in parallel. I believe we need to =
consider all AFs that BGP is used for.. As the code that would be =
developed would be applicable to these AF also ( I presume ). So as an =
example would be RT-C, is this solution applicable I don't know I am =
simply asking.. If we want to develop this and have it specific to the =
internet use case lets state that clearly. If not, then let's consider =
the other applications BGP supports..

[rjs] I'd say that it's not just applicable to IPv[46] in the Internet - =
but to numerous AFIs (there is a definite use-case for these solutions =
in L3VPN environments for instance). I am not saying that this is =
applicable or desirable to be turned on for all AFIs -- but it seems to =
me that this is a per-operator, per-deployment decision, not a per-AFI =
one. For instance, if we get an RTC UPDATE that is malformed, an =
operator may not want to tear down a session if it also carries other =
AFIs (e.g., VPNv[46] also) - in that case, the operator may want to =
treat this UPDATE as withdrawing the {as, route-target} NLRI (consider =
that we have no *standardised* multi-session mechanism yet, and there =
are potential scaling impacts of multiple sessions).

>=20
> This point (to me anyway) seems entirely related to the control-plane =
-- it points out that an operator has cases where one really wants to =
keep the impact of errors down to the particular subset of routing =
information that is affected. This point is entirely in the protocol, =
rather than implying any behaviour about forwarding (i.e., no =
implication is made that the NLRI identified as carried in the erroneous =
UPDATE are installed in the FIB, but rather that all *other* NLRI =
continue to be installed in the RIB).
> [Jim U>] See above.. My point is how can we ensure reliability across =
AFs...There is no doubt that mal-formed updates are an issue I just do =
not know how they affect other AFs, in those case it may be more =
appropriate to tear down and persist instead. Can we address these other =
use cases?

[rjs]: The consideration (that I see) that is missing from the draft =
w.r.t this point seems to be more "what would break if one utilises =
treat-as-withdraw and this is not {IPv[46],VPNv[46]} etc. Is this what =
you feel needs to be addressed?

[rjs]: I think the general though process of:
	1/ In some cases, we want avoid affecting all NLRI based on an =
error in a subset of the received NLRI.
	2/ In this case, we may need to recover from this inconsistency.
	3/ In some cases, we may want to give a session a chance to =
restart where we could not handle the error gracefully.
	4/ When errors occur on these sessions, there is great =
operational benefit of flagging them more explicitly.

[rjs]: is applicable across all AFIs almost. The distinction is really =
whether one considers that 1/ is a valid behaviour/risk for an AFI?=20

>=20
> I'll work through the points that you have made in this mail -- but =
I'd like to respond with a specific point here comparing more targeted =
handling of errors in UPDATE messages with persistence-type approaches.=20=

>=20
> - Persistence/hold-up is not acceptable to all operators in all =
deployments. Particularly, where no liveliness detection mechanism for =
the next-hop is available (i.e., where it is not possible or practical =
to determine the NH's reachability in the forwarding plane other than =
with with the routing protocol itself) then one would not want to accept =
the risk of running persistence.
> [Jim U>] Agreed.. Persistence requires that the NH be viable.=20
>=20
> - Therefore, an operator has two options for these deployments -- =
stick with the error handling behaviour that is available in BGP right =
now, which gives him no flexibility in terms of focusing responses to =
errors in a manner that is proportional to the actual error; or =
alternatively, accept some additional complexity and risk such that =
particular error handling is targeted to the NLRI that are contained in =
an UPDATE message that is found to be erroneous.
> [Jim U>] My concern here is that the entire support structure is based =
on session viability, the expectation here is that operators need to =
develop new approaches to understanding if there is a routing anomaly in =
their topology and develop tools/procedures which are different.

[rjs]: Yes, this is true. We introduce a more complex failure mode where =
a subset of prefixes are affected. *Any* new mechanism changing the =
tear-down and flush-the-RIB behaviour of BGP will need some different =
approaches to be developed. The intention of =A76 and =A77 of the draft =
is to highlight where things do become more complex and define =
requirements for ensuring that the right toolset exists around this =
behaviour.

[rjs]: Simplifying networks/removing complexity should always be a goal =
-- but we need to understand where simple behaviour does not provide the =
levers to limit the impact of errors occurring, and balance the =
complexity of introducing new mechanisms against the benefit to our =
network's operation.=20

[rjs]: I would like to think that the document highlights where =
complexity is being introduced -- and highlights the impact of turning =
some of these knobs on. If the complexity is not acceptable within a =
deployment, these mechanisms should not be deployed. However, where it =
is, we don't have the knobs to do anything today! If the document =
doesn't address this to your satisfaction, please let me know, and I'd =
be happy to make sure that the complexity is further highlighted.

> Given there are deployments where I cannot deploy persistence (e.g., =
towards an Internet network peer on an IXP where deployment of BFD/OAM =
mechanisms are very limited so BGP really tells me whether the other =
peer is "there" at all) yet in these cases I do not want to affect all =
NLRI when one erroneous UPDATE is received then it would seem that I =
need answers to the requirements in this draft.=20
> [Jim U>] Agreed..=20
>=20
> Your e-mail seems to imply that you do not have cases where you will =
not be able to deploy persistence and that you are accepting of =
session-level error handling in these cases. Would this be a fair =
assessment?
> [Jim U>] My work primarily revolves around the following BGP use cases =
VPN ( L2/L3 ), 3107, Multi-Cast, RT-C, Flowspec not Internet.. In these =
environments I would prefer that the session fail, persistence is =
activated, and well known procedures are used to correct the problem. I =
am in no way saying that the use case described here for the internet =
application is not viable or the correct approach.. But the fact remains =
that the code base will be used across all AFs and this solution =
requires different OpS/Troubleshooting knowledge and support. I would =
prefer consistency in the behavior..=20

[rjs]: I am involved in multiple network deployments across the company =
in which I work, both public and private. I understand that there are =
different requirements across different networks, and in different =
deployment cases.=20

[rjs]: The problem of any mechanism is that it *may* be available for =
places where it is not applicable. We could analyse persistence and say =
that for Internet deployments, it has the potential to be harmful -- a =
device that has failed will continue to look like a valid path when it =
might not be, where a network in the Internet DFZ is likely to have a =
number of alternate paths that could be used. In my view, in this draft, =
we're just taking the "lowest common denominator" approach - where we =
say, "how can we build mechanisms that could be applied across all =
AFIs?". I think in all the use cases you mentioned, there are =
deployments where these mechanisms are applicable. In all cases, one =
valid behaviour would be that we keep the subset of NLRI that were not =
affected from a neighbour, but do not use those that are not necessarily =
trustworthy because they were linked to an invalid message in the =
protocol. Of course, operationally, you may not want to do this, based =
on the risk of inconsistency and the impact of failure. The key point =
here is that my network deployment may differ to yours, and its up to =
both of us to decide for our networks, but we both need the tools to be =
able to make these choices. The problem with a consistent approach is =
that I don't see how we can have a consistent approach that isn't based =
on the lowest common denominator AFI - and even then, our logic may =
differ in terms of where we want to turn it on.

Kind regards,
r.


From shane@castlepoint.net  Mon Jun 25 14:15:33 2012
Return-Path: <shane@castlepoint.net>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2EFB021F8593 for <grow@ietfa.amsl.com>; Mon, 25 Jun 2012 14:15:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.336
X-Spam-Level: 
X-Spam-Status: No, score=-2.336 tagged_above=-999 required=5 tests=[AWL=0.036,  BAYES_00=-2.599, SARE_SUB_OBFU_Q1=0.227]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Lgyf56+uV0+A for <grow@ietfa.amsl.com>; Mon, 25 Jun 2012 14:15:31 -0700 (PDT)
Received: from dog.tcb.net (dog.tcb.net [64.78.150.133]) by ietfa.amsl.com (Postfix) with ESMTP id 91D2B21F8585 for <grow@ietf.org>; Mon, 25 Jun 2012 14:15:31 -0700 (PDT)
Received: by dog.tcb.net (Postfix, from userid 0) id 3879A268063; Mon, 25 Jun 2012 15:15:30 -0600 (MDT)
Received: from host2.tcb.net (64.78.235.218 [64.78.235.218]) (authenticated-user smtp) (TLSv1/SSLv3 AES128-SHA 128/128) by dog.tcb.net with SMTP; for grow@ietf.org; Mon, 25 Jun 2012 15:15:30 -0600 (MDT) (envelope-from shane@castlepoint.net)
X-Avenger: version=0.7.8; receiver=dog.tcb.net; client-ip=64.78.235.218; client-port=56904; data-bytes=0
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1278)
From: Shane Amante <shane@castlepoint.net>
In-Reply-To: <DCC302FAA9FE5F4BBA4DCAD46569377917449AF235@PRVPEXVS03.corp.twcable.com>
Date: Mon, 25 Jun 2012 15:15:29 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <D05A81B4-1317-4C13-A2D6-05F5B41096CA@castlepoint.net>
References: <CAL9jLabOs02rOti4tezaZiHyiOD2f9vAhsoE9c-afFb4J1xYXQ@mail.gmail.com> <DCC302FAA9FE5F4BBA4DCAD46569377917449AF235@PRVPEXVS03.corp.twcable.com>
To: "grow@ietf.org grow@ietf.org" <grow@ietf.org>
X-Mailer: Apple Mail (2.1278)
Subject: Re: [GROW] WGLC: draft-ietf-grow-ops-reqs-for-bgp-error-handling-04
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Jun 2012 21:15:33 -0000

I've read this draft and support it being published as an Informational =
RFC.

I do have some comments, which are not blocking, but that I do hope =
improve the clarity & readability of the draft.

1)  In Section 1.1, the following paragraph hints at the problems with =
current network architectures, but doesn't really come out and say what =
they are more directly.
---snip---
Traditional network architectures would deploy an Interior Gateway
Protocol (IGP) to carry infrastructure and customer prefixes, with an
Exterior Gateway Protocol (EGP) such as BGP being utilised to
propagate these prefixes to other Autonomous Systems.  [...]
---snip---
IMO, it would be better if the following section more directly said that =
scale, in terms of the sheer amount of routing information in BGP, has =
increased substantially, particularly in places like the core of a Route =
Reflection hierarchy with order _several_ million paths, and rising.  I =
wish I could point you at a link to a talk Danny & I gave to GROW and/or =
IDR at IETF 71 (?), but unfortunately I can't find a copy of the slides =
on the IETF's Web site.  You can see that it's in the GROW WG Agenda at =
IETF 71, but the slides link to a different presentation: =
<http://tools.ietf.org/wg/grow/agenda?item=3Dagenda71.html>

Anyway, IMO, this is (from my vantage point) the single factor that =
makes outages not only much more visible, but /also/ (just as =
importantly) take longer to recover from ... (at the end of the day, CPU =
is finite, there are no "easy" answers wrt using multi-core processors =
to speed-up convergence of single AFI's, DRAM speeds are not keeping =
pace, etc.)  This may be useful to mention here to "set the stage", as =
it were, since throughout the draft there's a continuous (and, good) =
dialogue of not making convergence times worse or CPU load increase as a =
result of incorporating better recovery capabilities.  IOW, another =
benefit you don't really mention anywhere, but probably should, is that =
/theoretically/ some of these mechanisms may help further promote =
scalability of BGP.  Obviously, we won't know that until we are =
evaluating solutions and researchers have time to study them, etc.

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

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

BTW, here's my list of optional, transitive attributes, with an "*" =
indicating those for which draft-ietf-idr-optional-transitive is =
applicable, in case you're wondering where I came up with my numbers =
above.  You don't need to include this in your draft.  I'm just =
providing it here in case someone wants to double-check my sources.
---snip---
7: Aggregator*
8: Community*
11: DPA - Destination Preference Attr
16: Extended Community*
17: AS4_PATH
18: AS4_Aggregator
22: PMSI-tunnel
23: Tunnel Encapsulation Attribute
25: IPv6 Address Specific Extended Community
128: Attribute Set
---snip---

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

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




Nits:
1)  =46rom <http://tools.ietf.org/html/rfc4271#section-3.1>:
---snip---
For the purpose of this protocol, a route is defined as a unit of
information that pairs a set of destinations with the attributes of a
path to those destinations.  The set of destinations are systems
whose IP addresses are contained in one IP address prefix that is
carried in the Network Layer Reachability Information (NLRI) field of
an UPDATE message, and the path is the information reported in the
path attributes field of the same UPDATE message.
---snip---
... thus, to be more correct, I think you should scrub the document to =
say "route" in places where you're saying "prefix".  Some examples =
include:

=
http://tools.ietf.org/html/draft-ietf-grow-ops-reqs-for-bgp-error-handling=
-04#section-1.2
---snip---
o  It is unacceptable within modern deployments of the BGP-4 protocol
   that a single erroneous UPDATE packet affects prefixes that it
   does not carry.  This requirement therefore requires some
---snip---
s/affects prefixes/affects routes/

---snip---
this reset of the BGP-4 session results in interruption to
forwarding packets (by means of withdrawing prefixes installed by
BGP-4 into a device's RIB, and subsequently FIB).  To this end,
---snip---
s/withdrawing prefixes/withdrawing routes/

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

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

4)  In Section 4, there do you really mean "transitive" here or do you =
instead mean "transient"?
---snip---
It is of particular note for both means of recovering RIB consistency
described that these are effective only when considering transitive
errors within an implementation - for instance, should an RFC ...
---snip---
... also, in the following, do you mean "dynamic" instead of =
"transitive" in the below?
---snip---
[...] It is not advisable that a transitive
filter and advertisement mechanism is triggered by all error handling
events due to the load this is likely to place on the neighbour
receiving such a request.  Where this BGP speaker is a relatively
---snip---

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

Thanks,

-shane




On Jun 19, 2012, at 9:05 AM, George, Wes wrote:
>> -----Original Message-----
>> From: grow-bounces@ietf.org [mailto:grow-bounces@ietf.org] On Behalf =
Of
>> Christopher Morrow
>> Sent: Monday, June 11, 2012 4:22 PM
>> To: grow-chairs@tools.ietf.org; grow@ietf.org grow@ietf.org
>> Subject: [GROW] WGLC: =
draft-ietf-grow-ops-reqs-for-bgp-error-handling-04
>>=20
>> Hello GROW-WG folk,
>> Please take this message as the start of a 2 week, ending 6/25/2012
>> (June 25, 2012) WGLC for the subject draft, link to current version:
>>  =
<http://www.ietf.org/internet-drafts/draft-ietf-grow-ops-reqs-for-bgp-
>> error-handling-04.txt>
>>=20
>> Abstract:
>> "BGP-4 is utilised as a key intra- and inter-Autonomous System =
routing
>>   protocol in modern IP networks.  The failure modes as defined by =
the
>>   original protocol standards are based on a number of assumptions
>>   around the impact of session failure.  Numerous incidents both in =
the
>>   global Internet routing table and within Service Provider networks
>>   have been caused by strict handling of a single invalid UPDATE
>>   message causing large-scale failures in one or more Autonomous
>>   Systems.
>>=20
>>   This memo describes the current use of BGP-4 within Service =
Provider
>>   networks, and outlines a set of requirements for further work to
>>   enhance the mechanisms available to a BGP-4 implementation when
>>   erroneous data is detected.  Whilst this document does not provide
>>   specification of any standard, it is intended as an overview of a =
set
>>   of enhancements to BGP-4 to improve the protocol's robustness to =
suit
>>   its current deployment."
>>=20
>> -Chris
>> co-chair
>> _______________________________________________
>> GROW mailing list
>> GROW@ietf.org
>> https://www.ietf.org/mailman/listinfo/grow
>=20
> This E-mail and any of its attachments may contain Time Warner Cable =
proprietary information, which is privileged, confidential, or subject =
to copyright belonging to Time Warner Cable. This E-mail is intended =
solely for the use of the individual or entity to which it is addressed. =
If you are not the intended recipient of this E-mail, you are hereby =
notified that any dissemination, distribution, copying, or action taken =
in relation to the contents of and attachments to this E-mail is =
strictly prohibited and may be unlawful. If you have received this =
E-mail in error, please notify the sender immediately and permanently =
delete the original and any copy of this E-mail and any printout.
> _______________________________________________
> GROW mailing list
> GROW@ietf.org
> https://www.ietf.org/mailman/listinfo/grow


From ju1738@att.com  Mon Jun 25 15:48:05 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 0846321F8554; Mon, 25 Jun 2012 15:48:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.931
X-Spam-Level: 
X-Spam-Status: No, score=-105.931 tagged_above=-999 required=5 tests=[AWL=-0.159, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_MED=-4, SARE_SUB_OBFU_Q1=0.227, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OXaoo3GbXan6; Mon, 25 Jun 2012 15:48:03 -0700 (PDT)
Received: from nbfkord-smmo05.seg.att.com (nbfkord-smmo05.seg.att.com [209.65.160.92]) by ietfa.amsl.com (Postfix) with ESMTP id C9E8321F8592; Mon, 25 Jun 2012 15:48:02 -0700 (PDT)
Received: from unknown [144.160.20.145] (EHLO mlpd192.enaf.sfdc.sbc.com) by nbfkord-smmo05.seg.att.com(mxl_mta-6.11.0-10) over TLS secured channel with ESMTP id 2aae8ef4.0.369400.00-397.1009023.nbfkord-smmo05.seg.att.com (envelope-from <ju1738@att.com>);  Mon, 25 Jun 2012 22:48:03 +0000 (UTC)
X-MXL-Hash: 4fe8eaa35910e810-babdfe16f318b4f2487e2e7b562ba50cb1ac0f9b
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlpd192.enaf.sfdc.sbc.com (8.14.5/8.14.5) with ESMTP id q5PMm2fg003563; Mon, 25 Jun 2012 18:48:02 -0400
Received: from sflint01.pst.cso.att.com (sflint01.pst.cso.att.com [144.154.234.228]) by mlpd192.enaf.sfdc.sbc.com (8.14.5/8.14.5) with ESMTP id q5PMlpYF003489 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 25 Jun 2012 18:47:52 -0400
Received: from MISOUT7MSGHUB9F.ITServices.sbc.com (misout7msghub9f.itservices.sbc.com [144.151.223.71]) by sflint01.pst.cso.att.com (RSA Interceptor); Mon, 25 Jun 2012 18:47:36 -0400
Received: from MISOUT7MSGUSR9I.ITServices.sbc.com ([144.151.223.56]) by MISOUT7MSGHUB9F.ITServices.sbc.com ([144.151.223.71]) with mapi id 14.02.0298.004; Mon, 25 Jun 2012 18:47:36 -0400
From: "UTTARO, JAMES" <ju1738@att.com>
To: "'Rob Shakir'" <rjs@rob.sh>
Thread-Topic: draft-ietf-grow-ops-reqs-for-bgp-error-handling-04
Thread-Index: Ac1Qh0AwzuLH5xBMSu2rz3aHemLX7wBK0QmAAAIbFGAAE+v4AABFsGbA
Date: Mon, 25 Jun 2012 22:47:35 +0000
Message-ID: <B17A6910EEDD1F45980687268941550FB2F6AA@MISOUT7MSGUSR9I.ITServices.sbc.com>
References: <B17A6910EEDD1F45980687268941550FB1F5C0@MISOUT7MSGUSR9I.ITServices.sbc.com> <52CBEC1F-49E6-4656-A617-CAB7304479F0@rob.sh> <B17A6910EEDD1F45980687268941550FB20F89@MISOUT7MSGUSR9I.ITServices.sbc.com> <FB4C2B5B-E935-4972-ACDD-151AF87DC26A@rob.sh>
In-Reply-To: <FB4C2B5B-E935-4972-ACDD-151AF87DC26A@rob.sh>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.70.228.209]
Content-Type: text/plain; charset="iso-8859-1"
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.20.145]
X-AnalysisOut: [v=1.0 c=1 a=rBRfEN-fR5wA:10 a=81eWbNQ_HDgA:10 a=ofMgfj31e3]
X-AnalysisOut: [cA:10 a=BLceEmwcHowA:10 a=8nJEP1OIZ-IA:10 a=ZRNLZ4dFUbCvG8]
X-AnalysisOut: [UMqPvVAA==:17 a=48vgC7mUAAAA:8 a=cXm1WQD8szEI92xSkW4A:9 a=]
X-AnalysisOut: [wPNLvfGTeEIA:10 a=lZB815dzVvQA:10 a=cTsA3ETV5bvCB0Qt:21 a=]
X-AnalysisOut: [S8P1yWJ-FUjRJRls:21]
Cc: 'idr wg' <idr@ietf.org>, "'grow@ietf.org'" <grow@ietf.org>
Subject: Re: [GROW] draft-ietf-grow-ops-reqs-for-bgp-error-handling-04
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Jun 2012 22:48:05 -0000

Rob,

	Comments In-Line..

Thanks,
	Jim Uttaro

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

Hi Jim,

Further comments in-line as [rjs].

On 24 Jun 2012, at 03:06, UTTARO, JAMES wrote:

> 1. Conservative -- any error in messages received from a neighbour are in=
dicative that it is not a viable route to any prefix it advertises. Therefo=
re where error conditions occur, disconnect and remove all routes from the =
neighbour from the RIB.
>=20
> [Jim U>] This is based on the current behavior of BGP.. If the NH is stil=
l viable you could allow the session to fall and persist the good state tha=
t has already been learned..

[rjs]: Absolutely, this is the current behaviour. The problem with taking a=
 whole session down in this case is that you now take a risk of inconsisten=
cy for all NLRI across that session for the duration that you hold onto the=
 learned NLRI. If one avoids being in the situation where the session is do=
wn (e.g., by applying treat-as-withdraw behaviour in cases where one can de=
termine the NLRI) then all other NLRI on the session continue to be updated=
 as they need to be. It is only the NLRI that were included in the erroneou=
s UPDATE that may be affected for looping/black-holing.


>>[Jim U>] The assumption being that the error was caused by an upstream sp=
eaker and is therefore not truly indicative of an issue over the session wh=
ere the error manifests itself. This seems to make sense in the IPV4 case. =
I am still a bit concerned as I do not understand how the following is addr=
essed.

- There is no way of knowing if the adjacent peer is the speaker that is ac=
tually responsible for the malformed attr or is coming from an upstream spe=
aker. I can think of no way of knowing this.. Can it be inferred from the n=
otion that an error is of the syntactic or semantic variety?
- There seems to be no threshold when the session is actually taking out of=
 service. It would seem that some number of these type of errors would indi=
cate a major issue is taking place and should be addressed by severing the =
speaker that is advertising paths with the malformed attr into the topology=
. A large number of these error will create a large number of withdrawn mes=
sages being generated from many peers. What are your thoughts on how this s=
hould be addressed?
>>

> I would expect all solutions implemented in response to these requirement=
s to be optional. If the risk of incorrectness is unacceptable to you/an op=
erator, then you should absolutely not enable any of these mechanisms. In a=
 number of networks that I have operated, designed and architected, I am pr=
epared to accept the risk of incorrectness, as I consider it acceptable whe=
n compared to the risk of complete service outages in terms of impact to my=
 customers during such incidents. At the moment, without the work described=
 through the requirements outlined in this draft I do not have the means to=
 make that call...
> [Jim U>] I do not understand how it is possible to make this configurable=
 on a per session or AS basis..I would think all speakers participating in =
a routing context would have to adhere to the same rules for a consistent v=
iew across domains.. In my reading of the IDR draft it seems that it would =
be a MUST.. Maybe I should not be considering that IDR draft as the actual =
realization of the reqs..

[rjs]: The IDR draft is the solution for some of the requirements -- partic=
ularly those described in Section 3 of the GROW draft.
>>[Jim U>] Got it..

[rjs]: I do not see why this behaviour needs to be consistent across domain=
s?
>>[Jim U>] Can you explain this

[rjs]: Essentially, if I receive an invalid UPDATE message, and apply treat=
-as-withdraw, if the advertising speaker did not know that this was erroneo=
us then I end up with a different view of what is in the RIB than the adver=
tising speaker does. If this was a prefix I had no other route to, then I m=
ay black-hole, if it was one where it was a more-specific of some larger pr=
efix, then we end up with the potential for loops.
>>[Jim U>] Yes.. I am not sure I like the notion of forwarding loops especi=
ally for large flows..=20

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

>=20
>> Abstract
>>=20
>> Can the scope be expanded? There are other failure modes, i.e Timer Expi=
ry which today is not considered a failure mode. In reality what I have see=
n is that timer expiry occurs due to the fact that BGP threads cannot be se=
rviced in a timely manner.  I think it would be best if we could put it all=
 on the table..
>>=20
>> I do think that this draft should bound the solution space. At the minim=
um the solutions proposed should meet a minimum set of the operators criter=
ia in terms of managing the network, convergence, persistence, churn, forwa=
rding impact etc... =20
>=20
> I think there was clear consensus amongst operators with whom I have spok=
en to work on the problem space of erroneous UPDATEs - particularly in resp=
onse to observed incidents. The very real risk of expanding the scope of th=
is document even further to handle any error in the BGP protocol is that we=
 spend another few years cataloguing such conditions, whilst doing nothing =
about the ones that we have identified.
> [Jim U>] No doubt.. But  I have seen other errors that relate to overload=
ing BGP, topological isolation etc... that have created huge outages in my =
network.. So, My thinking is that we should try to consider all of the chal=
lenges the protocol faces in terms of erroneous error conditions.=20

[rjs] Right, perhaps a better title for the draft would be "Operational Req=
uirements for Enhanced Error Handling for UPDATE Messages in BGP-4" -- give=
n that there were incidents that affected networks that particularly were f=
ocused on the errors in UPDATEs, it seemed logical that this was the place =
to start for this work.=20

>>[Jim U>] Agreed
>=20
>> Section 1.1
>>=20
>> The following paragraph is based on the premise that the session being "=
down" results in a large impact.. This is certainly true for today's implem=
entations which use the session ( Control Plane Construct ) to determine th=
e viability of the forwarding state learned over said session. There are ca=
ses where this is the session and forwarding are parallel, but in many more=
 cases control and forwarding planes are orthogonal.. I think we need to re=
-consider this assumption for many of the services BGP is being used for an=
d base the response to error conditions on this reality..
>>=20
>> " Both within Internet and multi-service routing architectures, a
>>   number of BGP sessions propagate a large proportion of the required
>>   routing information for network operation.  For Internet routing,
>>   these are typically BGP sessions which propagate the global routing
>>   table to an AS - failure of these sessions may have a large impact on
>>   network service, based on a single erroneous update.  In an multi-
>>   service environment, typical deployments utilise a small number of
>>   core-facing BGP sessions, typically towards route reflector devices.
>>   Failure of these sessions may also result in a large impact to
>>   network operation.  Clearly, the avoidance of conditions requiring
>>   these sessions to fail is of great utility to any network operator,
>>  and provides further motivation for the revision of the existing
>>   behaviour. "
>=20
> I do not understand what the assertion that you are making here is. Pleas=
e could you explain it to me? The errors that are being discussed relate to=
 where a subset of NLRI are advertised within an erroneous UPDATE message, =
and the resulting impact of the current protocol behaviour on all other NLR=
I carried on that session. The cases of IP "transit" sessions, and RR-PE se=
ssions are only examples of cases where there is a large amount of routing =
information carried over a single session - and hence it is of utility to a=
void these sessions failing where they do not necessarily need to based on =
the impact to overall network service.
> [Jim U>] The solution space here seems explicitly targeted to the interne=
t IPV4 AF. Not sure if there is a dependency here on the control/forwarding=
 planes being in parallel. I believe we need to consider all AFs that BGP i=
s used for.. As the code that would be developed would be applicable to the=
se AF also ( I presume ). So as an example would be RT-C, is this solution =
applicable I don't know I am simply asking.. If we want to develop this and=
 have it specific to the internet use case lets state that clearly. If not,=
 then let's consider the other applications BGP supports..

[rjs] I'd say that it's not just applicable to IPv[46] in the Internet - bu=
t to numerous AFIs (there is a definite use-case for these solutions in L3V=
PN environments for instance). I am not saying that this is applicable or d=
esirable to be turned on for all AFIs -- but it seems to me that this is a =
per-operator, per-deployment decision, not a per-AFI one. For instance, if =
we get an RTC UPDATE that is malformed, an operator may not want to tear do=
wn a session if it also carries other AFIs (e.g., VPNv[46] also) - in that =
case, the operator may want to treat this UPDATE as withdrawing the {as, ro=
ute-target} NLRI (consider that we have no *standardised* multi-session mec=
hanism yet, and there are potential scaling impacts of multiple sessions).

>>[Jim U>] Quite honestly AFs such as RT-C, Flowspec, etc... where the info=
 being propagated is more akin to "configuration" not path info should pers=
ist regardless of the session.. This goes to the heart of the discussion of=
 BGP is used for many fields of use that require persistence. It is not onl=
y paths that use BGP for dissemination.. I would prefer that this solution =
is limited to AFs that disseminate reachability/path info not configuration=
 info..
>>=20

>=20
> This point (to me anyway) seems entirely related to the control-plane -- =
it points out that an operator has cases where one really wants to keep the=
 impact of errors down to the particular subset of routing information that=
 is affected. This point is entirely in the protocol, rather than implying =
any behaviour about forwarding (i.e., no implication is made that the NLRI =
identified as carried in the erroneous UPDATE are installed in the FIB, but=
 rather that all *other* NLRI continue to be installed in the RIB).
> [Jim U>] See above.. My point is how can we ensure reliability across AFs=
...There is no doubt that mal-formed updates are an issue I just do not kno=
w how they affect other AFs, in those case it may be more appropriate to te=
ar down and persist instead. Can we address these other use cases?

[rjs]: The consideration (that I see) that is missing from the draft w.r.t =
this point seems to be more "what would break if one utilises treat-as-with=
draw and this is not {IPv[46],VPNv[46]} etc. Is this what you feel needs to=
 be addressed?

[rjs]: I think the general though process of:
	1/ In some cases, we want avoid affecting all NLRI based on an error in a =
subset of the received NLRI.
	2/ In this case, we may need to recover from this inconsistency.
	3/ In some cases, we may want to give a session a chance to restart where =
we could not handle the error gracefully.
	4/ When errors occur on these sessions, there is great operational benefit=
 of flagging them more explicitly.

[rjs]: is applicable across all AFIs almost. The distinction is really whet=
her one considers that 1/ is a valid behaviour/risk for an AFI?=20

>>[Jim U>] We need to look at AFs and decide what is the behavior required =
for the content being disseminated..=20
>=20
> I'll work through the points that you have made in this mail -- but I'd l=
ike to respond with a specific point here comparing more targeted handling =
of errors in UPDATE messages with persistence-type approaches.=20
>=20
> - Persistence/hold-up is not acceptable to all operators in all deploymen=
ts. Particularly, where no liveliness detection mechanism for the next-hop =
is available (i.e., where it is not possible or practical to determine the =
NH's reachability in the forwarding plane other than with with the routing =
protocol itself) then one would not want to accept the risk of running pers=
istence.
> [Jim U>] Agreed.. Persistence requires that the NH be viable.=20
>=20
> - Therefore, an operator has two options for these deployments -- stick w=
ith the error handling behaviour that is available in BGP right now, which =
gives him no flexibility in terms of focusing responses to errors in a mann=
er that is proportional to the actual error; or alternatively, accept some =
additional complexity and risk such that particular error handling is targe=
ted to the NLRI that are contained in an UPDATE message that is found to be=
 erroneous.
> [Jim U>] My concern here is that the entire support structure is based on=
 session viability, the expectation here is that operators need to develop =
new approaches to understanding if there is a routing anomaly in their topo=
logy and develop tools/procedures which are different.

[rjs]: Yes, this is true. We introduce a more complex failure mode where a =
subset of prefixes are affected. *Any* new mechanism changing the tear-down=
 and flush-the-RIB behaviour of BGP will need some different approaches to =
be developed. The intention of =A76 and =A77 of the draft is to highlight w=
here things do become more complex and define requirements for ensuring tha=
t the right toolset exists around this behaviour.

[rjs]: Simplifying networks/removing complexity should always be a goal -- =
but we need to understand where simple behaviour does not provide the lever=
s to limit the impact of errors occurring, and balance the complexity of in=
troducing new mechanisms against the benefit to our network's operation.=20

[rjs]: I would like to think that the document highlights where complexity =
is being introduced -- and highlights the impact of turning some of these k=
nobs on. If the complexity is not acceptable within a deployment, these mec=
hanisms should not be deployed. However, where it is, we don't have the kno=
bs to do anything today! If the document doesn't address this to your satis=
faction, please let me know, and I'd be happy to make sure that the complex=
ity is further highlighted.
> Given there are deployments where I cannot deploy persistence (e.g., towa=
rds an Internet network peer on an IXP where deployment of BFD/OAM mechanis=
ms are very limited so BGP really tells me whether the other peer is "there=
" at all) yet in these cases I do not want to affect all NLRI when one erro=
neous UPDATE is received then it would seem that I need answers to the requ=
irements in this draft.=20
> [Jim U>] Agreed..=20
>=20
> Your e-mail seems to imply that you do not have cases where you will not =
be able to deploy persistence and that you are accepting of session-level e=
rror handling in these cases. Would this be a fair assessment?
> [Jim U>] My work primarily revolves around the following BGP use cases VP=
N ( L2/L3 ), 3107, Multi-Cast, RT-C, Flowspec not Internet.. In these envir=
onments I would prefer that the session fail, persistence is activated, and=
 well known procedures are used to correct the problem. I am in no way sayi=
ng that the use case described here for the internet application is not via=
ble or the correct approach.. But the fact remains that the code base will =
be used across all AFs and this solution requires different OpS/Troubleshoo=
ting knowledge and support. I would prefer consistency in the behavior..=20

[rjs]: I am involved in multiple network deployments across the company in =
which I work, both public and private. I understand that there are differen=
t requirements across different networks, and in different deployment cases=
.=20

[rjs]: The problem of any mechanism is that it *may* be available for place=
s where it is not applicable. We could analyse persistence and say that for=
 Internet deployments, it has the potential to be harmful -- a device that =
has failed will continue to look like a valid path when it might not be, wh=
ere a network in the Internet DFZ is likely to have a number of alternate p=
aths that could be used. In my view, in this draft, we're just taking the "=
lowest common denominator" approach - where we say, "how can we build mecha=
nisms that could be applied across all AFIs?". I think in all the use cases=
 you mentioned, there are deployments where these mechanisms are applicable=
. In all cases, one valid behaviour would be that we keep the subset of NLR=
I that were not affected from a neighbour, but do not use those that are no=
t necessarily trustworthy because they were linked to an invalid message in=
 the protocol. Of course, operationally, you may not want to do this, based=
 on the risk of inconsistency and the impact of failure. The key point here=
 is that my network deployment may differ to yours, and its up to both of u=
s to decide for our networks, but we both need the tools to be able to make=
 these choices. The problem with a consistent approach is that I don't see =
how we can have a consistent approach that isn't based on the lowest common=
 denominator AFI - and even then, our logic may differ in terms of where we=
 want to turn it on.

Kind regards,
r.


From jhaas@slice.pfrc.org  Wed Jun 27 11:26:53 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 361F611E8132 for <grow@ietfa.amsl.com>; Wed, 27 Jun 2012 11:26:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.22
X-Spam-Level: 
X-Spam-Status: No, score=-102.22 tagged_above=-999 required=5 tests=[AWL=0.045, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9uLF5OVlq4i8 for <grow@ietfa.amsl.com>; Wed, 27 Jun 2012 11:26:52 -0700 (PDT)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id 63A4011E8131 for <grow@ietf.org>; Wed, 27 Jun 2012 11:26:52 -0700 (PDT)
Received: by slice.pfrc.org (Postfix, from userid 1001) id 2AF10D162; Wed, 27 Jun 2012 14:26:52 -0400 (EDT)
Date: Wed, 27 Jun 2012 14:26:52 -0400
From: Jeffrey Haas <jhaas@pfrc.org>
To: Christopher Morrow <christopher.morrow@gmail.com>
Message-ID: <20120627182652.GT18361@pfrc>
References: <CAL9jLabADdWCwDhBdaBJ4fVdk9a=OeJQYFQM4Z_+-P56cVWftw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAL9jLabADdWCwDhBdaBJ4fVdk9a=OeJQYFQM4Z_+-P56cVWftw@mail.gmail.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: "grow@ietf.org grow@ietf.org" <grow@ietf.org>, grow-chairs@tools.ietf.org
Subject: Re: [GROW] WGLC: draft-ietf-grow-private-ip-sp-cores
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Jun 2012 18:26:53 -0000

On Tue, Jun 05, 2012 at 02:41:39PM -0400, Christopher Morrow wrote:
> Folks,
> There's been work on the draft:
>    <http://tools.ietf.org/html/draft-ietf-grow-private-ip-sp-cores>
> 
> I think the commenters' comments were addressed by the authors.
> Can we move this to WGLC now and clear that 6/19/2012 (June 19, 2012).

While it's long past this date, I haven't seen a note saying that the WGLC
concluded successfully.  So, I'll add in my support for publication FWIW.

-- Jeff

From rjs@rob.sh  Thu Jun 28 01:48:53 2012
Return-Path: <rjs@rob.sh>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C1B3021F889F; Thu, 28 Jun 2012 01:48:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.772
X-Spam-Level: 
X-Spam-Status: No, score=-1.772 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_13=0.6, SARE_SUB_OBFU_Q1=0.227]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r3wEFj7Dz3GU; Thu, 28 Jun 2012 01:48:52 -0700 (PDT)
Received: from cappuccino.rob.sh (cappuccino.rob.sh [IPv6:2001:b98:201:101::10:cafe]) by ietfa.amsl.com (Postfix) with ESMTP id 8B69F21F88A5; Thu, 28 Jun 2012 01:48:52 -0700 (PDT)
Received: from [217.41.227.31] (helo=[10.96.3.206]) by cappuccino.rob.sh with esmtpa (Exim 4.72) (envelope-from <rjs@rob.sh>) id 1SkANq-0006NR-21; Thu, 28 Jun 2012 09:47:26 +0100
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=iso-8859-1
From: Rob Shakir <rjs@rob.sh>
In-Reply-To: <B17A6910EEDD1F45980687268941550FB2F6AA@MISOUT7MSGUSR9I.ITServices.sbc.com>
Date: Thu, 28 Jun 2012 09:48:49 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <3FE3D8FD-7658-4A42-8D9E-2133825A4061@rob.sh>
References: <B17A6910EEDD1F45980687268941550FB1F5C0@MISOUT7MSGUSR9I.ITServices.sbc.com> <52CBEC1F-49E6-4656-A617-CAB7304479F0@rob.sh> <B17A6910EEDD1F45980687268941550FB20F89@MISOUT7MSGUSR9I.ITServices.sbc.com> <FB4C2B5B-E935-4972-ACDD-151AF87DC26A@rob.sh> <B17A6910EEDD1F45980687268941550FB2F6AA@MISOUT7MSGUSR9I.ITServices.sbc.com>
To: "UTTARO, JAMES" <ju1738@att.com>
X-Mailer: Apple Mail (2.1257)
Cc: 'idr wg' <idr@ietf.org>, "'grow@ietf.org'" <grow@ietf.org>
Subject: Re: [GROW] draft-ietf-grow-ops-reqs-for-bgp-error-handling-04
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jun 2012 08:48:53 -0000

Hi Jim,

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

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

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

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

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

[rjs]: This is true, only where we have a mechanism such as the partial =
bit in the optional transitive attribute can we infer that the directly =
attached neighbour did not look at the session. What the semantic and =
critical errors that are called out in the draft relate to is the impact =
of the error on the resulting UPDATE message, rather than the direct =
neighbour being responsible for it.

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

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

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

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

I don't think that I can categorically state that the answer to the =
former is no, but I am not aware of the case. In my view, larger scale =
issues on the BGP speaker (e.g., things that affect memory integrity =
etc.) result in failures that produce output that is not well enough =
formed to fall within the "semantic" errors described in the draft. I =
would (of course) welcome implementor and tester's feed back on this =
point.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Thanks,
r.=

From tkirkham@anthony-kirkham.com  Fri Jun 29 18:11:35 2012
Return-Path: <tkirkham@anthony-kirkham.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7417C21F85D0 for <grow@ietfa.amsl.com>; Fri, 29 Jun 2012 18:11:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.076
X-Spam-Level: 
X-Spam-Status: No, score=-2.076 tagged_above=-999 required=5 tests=[AWL=0.523,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9KMjdSh9Eceb for <grow@ietfa.amsl.com>; Fri, 29 Jun 2012 18:11:35 -0700 (PDT)
Received: from nschwmtas01p.mx.bigpond.com (nschwmtas01p.mx.bigpond.com [61.9.189.137]) by ietfa.amsl.com (Postfix) with ESMTP id 9FEDC21F85CD for <grow@ietf.org>; Fri, 29 Jun 2012 18:11:34 -0700 (PDT)
Received: from nschwcmgw07p ([61.9.190.167]) by nschwmtas01p.mx.bigpond.com with ESMTP id <20120630011132.WBES24679.nschwmtas01p.mx.bigpond.com@nschwcmgw07p>;  Sat, 30 Jun 2012 01:11:32 +0000
Received: from Anthonys-MacBook-Pro.local ([124.185.157.18]) by nschwcmgw07p with BigPond Outbound id URBH1j0030Q5xN401RBVVQ; Sat, 30 Jun 2012 01:11:32 +0000
X-Authority-Analysis: v=2.0 cv=avcw+FlV c=1 sm=1 a=0VFf0P/YIxcxI/RgN+hXcA==:17 a=zjFFUUgunscA:10 a=5guEdk2PV24A:10 a=Ib5BsLsVyy8A:10 a=bVeADsv9IVkA:10 a=kj9zAlcOel0A:10 a=xR3Tfk4wAAAA:8 a=48vgC7mUAAAA:8 a=Sa8v3uAmxNAripQOvZ4A:9 a=CjuIK1q_8ugA:10 a=lZB815dzVvQA:10 a=0VFf0P/YIxcxI/RgN+hXcA==:117
Message-ID: <4FEE5234.9000502@anthony-kirkham.com>
Date: Sat, 30 Jun 2012 11:11:16 +1000
From: Anthony Kirkham <tkirkham@anthony-kirkham.com>
Organization: Anthony-Kirkham.com
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: Jeffrey Haas <jhaas@pfrc.org>
References: <CAL9jLabADdWCwDhBdaBJ4fVdk9a=OeJQYFQM4Z_+-P56cVWftw@mail.gmail.com> <20120627182652.GT18361@pfrc>
In-Reply-To: <20120627182652.GT18361@pfrc>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "grow@ietf.org grow@ietf.org" <grow@ietf.org>, grow-chairs@tools.ietf.org
Subject: Re: [GROW] WGLC: draft-ietf-grow-private-ip-sp-cores
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: tkirkham@anthony-kirkham.com
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 30 Jun 2012 01:11:35 -0000

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

Thank you for your support. I'm hoping this gets closed off soon.

Tony K

-- 

