[GROW] Fw: New Version Notification for draft-ietf-grow-route-leak-problem-definition-04.txt

"Sriram, Kotikalapudi" <kotikalapudi.sriram@nist.gov> Thu, 11 February 2016 13:03 UTC

Return-Path: <kotikalapudi.sriram@nist.gov>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8F06F1B2C56 for <grow@ietfa.amsl.com>; Thu, 11 Feb 2016 05:03:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ExSZW-eMnrIY for <grow@ietfa.amsl.com>; Thu, 11 Feb 2016 05:03:27 -0800 (PST)
Received: from gcc01-CY1-obe.outbound.protection.outlook.com (mail-cy1gcc01on0116.outbound.protection.outlook.com [23.103.200.116]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B07801B2C3D for <grow@ietf.org>; Thu, 11 Feb 2016 05:03:25 -0800 (PST)
Received: from SN1PR09MB0799.namprd09.prod.outlook.com (10.162.101.145) by SN1PR09MB0800.namprd09.prod.outlook.com (10.162.101.146) with Microsoft SMTP Server (TLS) id 15.1.403.16; Thu, 11 Feb 2016 13:03:23 +0000
Received: from SN1PR09MB0799.namprd09.prod.outlook.com ([10.162.101.145]) by SN1PR09MB0799.namprd09.prod.outlook.com ([10.162.101.145]) with mapi id 15.01.0403.017; Thu, 11 Feb 2016 13:03:23 +0000
From: "Sriram, Kotikalapudi" <kotikalapudi.sriram@nist.gov>
To: "grow@ietf.org grow@ietf.org" <grow@ietf.org>
Thread-Topic: New Version Notification for draft-ietf-grow-route-leak-problem-definition-04.txt
Thread-Index: AQHRZMi11EiibiyTRky1bkpwUE4Ltp8mye/P
Date: Thu, 11 Feb 2016 13:03:23 +0000
Message-ID: <SN1PR09MB0799A198AF3F8B05AA67D1A584A80@SN1PR09MB0799.namprd09.prod.outlook.com>
References: <20160211123536.14424.12004.idtracker@ietfa.amsl.com>
In-Reply-To: <20160211123536.14424.12004.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: instituut.net; dkim=none (message not signed) header.d=none;instituut.net; dmarc=none action=none header.from=nist.gov;
x-originating-ip: [129.6.219.62]
x-microsoft-exchange-diagnostics: 1; SN1PR09MB0800; 5:eh9MQfYvYijqKWY/2dbex1W2TrWXppT56wv3DgzitvVc4zEo1KfzGV+7nhMG4P6pmE3FwlLReCc7huu4jkNFrZnDvTi0yXQjSh0p1xVMMxA8Kv9isrfKJer6rtshyNjNULkx6WhYU1FJJCjn+D0zhQ==; 24:0uiKUvblMVhjkEPTWNq+Tw+KNBjdVLPNSLt1eDy+clZDsEAAp26YJxKcwsAKmPPMfLhMsxMGQyftWohe6XKgrW1v8WpuZ/g0F64QLpRjirw=
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:SN1PR09MB0800;
x-ms-office365-filtering-correlation-id: 1d97fe3d-6266-462b-93c0-08d332e3b900
x-microsoft-antispam-prvs: <SN1PR09MB0800028B874DF0F8DBF6A14784A80@SN1PR09MB0800.namprd09.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(2401047)(8121501046)(5005006)(10201501046)(3002001); SRVR:SN1PR09MB0800; BCL:0; PCL:0; RULEID:; SRVR:SN1PR09MB0800;
x-forefront-prvs: 08497C3D99
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(377424004)(377454003)(7110500001)(87936001)(50986999)(3660700001)(189998001)(76176999)(3900700001)(86362001)(2906002)(106116001)(2900100001)(102836003)(586003)(5001960100002)(1220700001)(77096005)(33656002)(110136002)(92566002)(15975445007)(3846002)(10400500002)(1096002)(2420400007)(2950100001)(54356999)(5004730100002)(66066001)(6116002)(5008740100001)(230783001)(3280700002)(76576001)(5003600100002)(19580395003)(19580405001)(10710500007)(11100500001)(74316001)(4326007)(40100003)(122556002); DIR:OUT; SFP:1102; SCL:1; SRVR:SN1PR09MB0800; H:SN1PR09MB0799.namprd09.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en;
spamdiagnosticoutput: 1:23
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: nist.gov
X-MS-Exchange-CrossTenant-originalarrivaltime: 11 Feb 2016 13:03:23.0440 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 2ab5d82f-d8fa-4797-a93e-054655c61dec
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN1PR09MB0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/grow/wfeQ8X6ETHJgSGzPNg4F57NloIA>
Subject: [GROW] Fw: New Version Notification for draft-ietf-grow-route-leak-problem-definition-04.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.15
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: <https://mailarchive.ietf.org/arch/browse/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, 11 Feb 2016 13:03:32 -0000

This revision takes care of the comments received during the WGLC on the -03 version draft.
One major comment was from Job:

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

Job and I met in person in Yokohama and discussed his comment, 
and we agreed that it made sense to remove the section on what was
“Type 5: U-Shaped Turn with More Specific Prefix” in version -03 draft. 
I had posted on the GROW list earlier about my conversation with Job:

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

Andrei also had suggested the same thing in a private email to me. 
So I have revised the draft now to reflect this change.

Wes and David Farmer suggested using “Hairpin turn” instead of “U-shaped turn”.
That is done and I have also put in some words to explain the term.

Jeff and Rick Casarez suggested using “more specific” instead of “subprefix”.  -- Done.

I have also made a few other minor changes, and added a new reference [Kephart].

I think this takes care of addressing all received comments since the last WGLC:

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

Thanks once again to all who have reviewed and offered suggestions and comments.

Sriram

________________________________________
From: internet-drafts@ietf.org <internet-drafts@ietf.org>
Sent: Thursday, February 11, 2016 7:35 AM
To: Sriram, Kotikalapudi; Montgomery, Douglas; Eric Osterweil; Brian Dickson; Danny McPherson
Subject: New Version Notification for draft-ietf-grow-route-leak-problem-definition-04.txt

A new version of I-D, draft-ietf-grow-route-leak-problem-definition-04.txt
has been successfully submitted by Kotikalapudi Sriram and posted to the
IETF repository.

Name:           draft-ietf-grow-route-leak-problem-definition
Revision:       04
Title:          Problem Definition and Classification of BGP Route Leaks
Document date:  2016-02-11
Group:          grow
Pages:          11
URL:            https://www.ietf.org/internet-drafts/draft-ietf-grow-route-leak-problem-definition-04.txt
Status:         https://datatracker.ietf.org/doc/draft-ietf-grow-route-leak-problem-definition/
Htmlized:       https://tools.ietf.org/html/draft-ietf-grow-route-leak-problem-definition-04
Diff:           https://www.ietf.org/rfcdiff?url2=draft-ietf-grow-route-leak-problem-definition-04

Abstract:
   A systemic vulnerability of the Border Gateway Protocol routing
   system, known as 'route leaks', has received significant attention in
   recent years.  Frequent incidents that result in significant
   disruptions to Internet routing are labeled "route leaks", but to
   date we have lacked a common definition of the term.  In this
   document, we provide a working definition of route leaks, keeping in
   mind the real occurrences that have received significant attention.
   Further, we attempt to enumerate (though not exhaustively) different
   types of route leaks based on observed events on the Internet.  We
   aim to provide a taxonomy that covers several forms of route leaks
   that have been observed and are of concern to Internet user community
   as well as the network operator community.