IETF Logo Mail Archive

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

"Sriram, Kotikalapudi (Fed)" <kotikalapudi.sriram@nist.gov> Fri, 29 April 2016 16:50 UTC

Return-Path: <kotikalapudi.sriram@nist.gov>
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 2DC7F12D1A2; Fri, 29 Apr 2016 09:50:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.792
X-Spam-Level:
X-Spam-Status: No, score=-1.792 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=nistgov.onmicrosoft.com
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 3DK4lxKR027j; Fri, 29 Apr 2016 09:50:27 -0700 (PDT)
Received: from gcc01-CY1-obe.outbound.protection.outlook.com (mail-cy1gcc01on0095.outbound.protection.outlook.com [23.103.200.95]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3EE6612D192; Fri, 29 Apr 2016 09:50:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nistgov.onmicrosoft.com; s=selector1-nist-gov; h=From:To:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=Ol5ej950bvO84NiTiypoXM5DTQkmkngrrbc5OAh/01U=; b=0ZcE0jt802l/ZDsH34ZM/YtUB2jYbU+UcwAlrOCj0kP3M8AVNNvvRCGc7m5qnYHQ82EPXWqZZkGa/KSEMoBMZ8nXe3spy/pxM9Qn63QSZiniNI+mKcpSshq6EykgzgecabMvY+xJVvukfZomxbAUTF6NaZseeP6lZUrJf2OOouI=
Received: from BL2PR09MB1123.namprd09.prod.outlook.com (10.167.102.151) by BL2PR09MB1121.namprd09.prod.outlook.com (10.167.102.149) with Microsoft SMTP Server (TLS) id 15.1.477.8; Fri, 29 Apr 2016 16:50:25 +0000
Received: from BL2PR09MB1123.namprd09.prod.outlook.com ([10.167.102.151]) by BL2PR09MB1123.namprd09.prod.outlook.com ([10.167.102.151]) with mapi id 15.01.0477.014; Fri, 29 Apr 2016 16:50:25 +0000
From: "Sriram, Kotikalapudi (Fed)" <kotikalapudi.sriram@nist.gov>
To: "grow@ietf.org" <grow@ietf.org>, Mach Chen <mach.chen@huawei.com>, Pete Resnick <presnick@qti.qualcomm.com>
Thread-Topic: New Version Notification for draft-ietf-grow-route-leak-problem-definition-05.txt
Thread-Index: AQHRojXFlow0LFZ0iEmwEx+pVkDRV5+hJ3bw
Date: Fri, 29 Apr 2016 16:50:24 +0000
Message-ID: <BL2PR09MB1123848F2CD4C3667038445084660@BL2PR09MB1123.namprd09.prod.outlook.com>
References: <20160429163957.4785.73760.idtracker@ietfa.amsl.com>
In-Reply-To: <20160429163957.4785.73760.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=nist.gov;
x-originating-ip: [129.6.108.229]
x-ms-office365-filtering-correlation-id: d64c4d9d-6a3f-4385-e437-08d3704e5ca6
x-microsoft-exchange-diagnostics: 1; BL2PR09MB1121; 5:jSk0ybNem95B3LixEXIkeZ5VqWVeQ80AY7sr1gToZKPiB3i3nbUBKmnlJOnVgQaGKg85V77DGDfl7xElEGNgyJXb94zbEshiH0m/M2a8wGE3SPlau4U4DtNI8p74RHtFH0Xn1Y7GbHX8+/GzIIf8jw==; 24:bQKlh4Atm6QsMH9h0+4PgNG8GiE6Mbt8nG0uWDmm0nYdc5iNBVsqtYQYF3z9zpqGhkWptmabZ0gAzXN2nT2XNiR6CDtPhQPsRQsjHDmkyKI=; 7:r/9NpmfXGx0TA3OqneMVn0RY9uTisvTlQlnWSK7DtzqfNYR9rQu8S8zS5knQsfvoR8kUTWmPZOX56sPjbSQCUzb8WZyNxNXFAyAWzQPY6yN2unsqqWD3IkslAW14RArhwqXcTMh6OmPiyM3haeTEbyf7rcZNXCRNQzLXVKZf4mirKxH6CZkYM0nkahr/B87H
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BL2PR09MB1121;
x-microsoft-antispam-prvs: <BL2PR09MB11211A60F01033E6C045D2B584660@BL2PR09MB1121.namprd09.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(9101521072)(601004)(2401047)(8121501046)(5005006)(3002001)(10201501046)(6055026); SRVR:BL2PR09MB1121; BCL:0; PCL:0; RULEID:; SRVR:BL2PR09MB1121;
x-forefront-prvs: 0927AA37C7
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(13464003)(377454003)(377424004)(33656002)(81166005)(1220700001)(87936001)(19580405001)(86362001)(19580395003)(50986999)(1096002)(54356999)(76176999)(4326007)(66066001)(5003600100002)(5002640100001)(230783001)(189998001)(122556002)(15650500001)(2906002)(3660700001)(3846002)(5008740100001)(106116001)(586003)(2950100001)(15975445007)(6116002)(102836003)(2900100001)(92566002)(77096005)(5001770100001)(11100500001)(10400500002)(5004730100002)(3280700002)(2501003)(76576001)(9686002)(74316001); DIR:OUT; SFP:1102; SCL:1; SRVR:BL2PR09MB1121; H:BL2PR09MB1123.namprd09.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en;
spamdiagnosticoutput: 1:23
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: nist.gov
X-MS-Exchange-CrossTenant-originalarrivaltime: 29 Apr 2016 16:50:24.9198 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 2ab5d82f-d8fa-4797-a93e-054655c61dec
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BL2PR09MB1121
Archived-At: <http://mailarchive.ietf.org/arch/msg/grow/E7nPJNrej5EnIlAQLBYuYBZnU24>
Cc: "grow-chairs@ietf.org" <grow-chairs@ietf.org>
Subject: [GROW] FW: New Version Notification for draft-ietf-grow-route-leak-problem-definition-05.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.17
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: Fri, 29 Apr 2016 16:50:29 -0000

This new version incorporates changes suggested by Pete Resnick (Gen-ART LC reviewer) and by Mach Chen (Routing Directorate reviewer). Thanks to Pete and Mach for their reviews and comments.

Sriram

-----Original Message-----
From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org] 
Sent: Friday, April 29, 2016 12:40 PM
To: Sriram, Kotikalapudi (Fed) <kotikalapudi.sriram@nist.gov>; Montgomery, Douglas (Fed) <dougm@nist.gov>; Eric Osterweil <eosterweil@verisign.com>; Brian Dickson <brian.peter.dickson@gmail.com>; Danny McPherson <dmcpherson@verisign.com>
Subject: New Version Notification for draft-ietf-grow-route-leak-problem-definition-05.txt


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

Name:		draft-ietf-grow-route-leak-problem-definition
Revision:	05
Title:		Problem Definition and Classification of BGP Route Leaks
Document date:	2016-04-29
Group:		grow
Pages:		11
URL:            https://www.ietf.org/internet-drafts/draft-ietf-grow-route-leak-problem-definition-05.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-05
Diff:           https://www.ietf.org/rfcdiff?url2=draft-ietf-grow-route-leak-problem-definition-05

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 a common definition of the term has been lacking.  This document
   provides a working definition of route leaks, keeping in mind the
   real occurrences that have received significant attention.  Further,
   this document attempts to enumerate (though not exhaustively)
   different types of route leaks based on observed events on the
   Internet.  The aim is 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.

                                                                                  


Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat

v2.23.0 | Report a Bug | By Email