[GROW] Fw: New Version Notification for draft-sriram-route-leak-detection-mitigation-00.txt
"Sriram, Kotikalapudi" <kotikalapudi.sriram@nist.gov> Tue, 28 October 2014 16:16 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 BF2C11A909D; Tue, 28 Oct 2014 09:16:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_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 nHPe9pDjy0qQ; Tue, 28 Oct 2014 09:16:31 -0700 (PDT)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1bon0788.outbound.protection.outlook.com [IPv6:2a01:111:f400:fc10::1:788]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 004D91A8AEB; Tue, 28 Oct 2014 09:12:34 -0700 (PDT)
Received: from DM2PR09MB0303.namprd09.prod.outlook.com (25.160.96.148) by DM2PR09MB0271.namprd09.prod.outlook.com (25.160.96.140) with Microsoft SMTP Server (TLS) id 15.1.6.9; Tue, 28 Oct 2014 16:12:12 +0000
Received: from DM2PR09MB0302.namprd09.prod.outlook.com (25.160.96.147) by DM2PR09MB0303.namprd09.prod.outlook.com (25.160.96.148) with Microsoft SMTP Server (TLS) id 15.1.6.9; Tue, 28 Oct 2014 16:12:10 +0000
Received: from DM2PR09MB0302.namprd09.prod.outlook.com ([25.160.96.147]) by DM2PR09MB0302.namprd09.prod.outlook.com ([25.160.96.147]) with mapi id 15.01.0006.000; Tue, 28 Oct 2014 16:12:10 +0000
From: "Sriram, Kotikalapudi" <kotikalapudi.sriram@nist.gov>
To: GROW WG <grow@ietf.org>, "idr@ietf.org" <idr@ietf.org>, "sidr@ietf.org" <sidr@ietf.org>
Thread-Topic: New Version Notification for draft-sriram-route-leak-detection-mitigation-00.txt
Thread-Index: AQHP8sjie+MIpcLEZEaCeJbYTPJ6Mg==
Date: Tue, 28 Oct 2014 16:12:10 +0000
Message-ID: <1414512729759.3402@nist.gov>
References: <20141027222842.23964.59825.idtracker@ietfa.amsl.com>, <1414511737146.42356@nist.gov>
In-Reply-To: <1414511737146.42356@nist.gov>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [129.6.222.126]
x-microsoft-antispam: BCL:0;PCL:0;RULEID:;SRVR:DM2PR09MB0303;UriScan:;
x-exchange-antispam-report-test: UriScan:;
x-forefront-prvs: 0378F1E47A
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(199003)(189002)(377454003)(377424004)(64706001)(85852003)(92566001)(97736003)(76482002)(2201001)(92726001)(15202345003)(31966008)(77096002)(107046002)(107886001)(87936001)(40100003)(86362001)(85306004)(15975445006)(230783001)(2501002)(117636001)(99286002)(95666004)(4396001)(101416001)(50986999)(120916001)(54356999)(105586002)(561944003)(106356001)(76176999)(106116001)(2656002)(80022003)(46102003)(20776003)(19580405001)(21056001)(122556002)(66066001)(36756003)(19580395003); DIR:OUT; SFP:1102; SCL:1; SRVR:DM2PR09MB0303; H:DM2PR09MB0302.namprd09.prod.outlook.com; FPR:; MLV:sfv; PTR:InfoNoRecords; A:1; MX:1; LANG:en;
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Microsoft-Antispam: BCL:0;PCL:0;RULEID:;SRVR:DM2PR09MB0271;
X-OriginatorOrg: nist.gov
Archived-At: http://mailarchive.ietf.org/arch/msg/grow/hO25abEf8fxm9VpXXLKJpFKsZMI
Subject: [GROW] Fw: New Version Notification for draft-sriram-route-leak-detection-mitigation-00.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: <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, 28 Oct 2014 16:16:42 -0000
Following up on my preceding email, this (notification below) is the second part (after the 1 to 2 split) that documents the “route leaks solution proposal”. This work was presented at the GROW meeting in Toronto, and it was suggested that the path of progress for this document (solution proposal) should be through IDR to SIDR. I will be happy to present this work in the IDR or the joint IDR-SIDR meeting in Honolulu. The earlier comments on this work at the GROW meeting in Toronto can be found here: http://www.ietf.org/proceedings/90/minutes/minutes-90-grow Further comments, suggestions are welcome. Sriram ________________________________________ From: internet-drafts@ietf.org <internet-drafts@ietf.org> Sent: Monday, October 27, 2014 7:01 PM To: Sriram, Kotikalapudi; Montgomery, Douglas; Subject: New Version Notification for draft-sriram-route-leak-detection-mitigation-00.txt A new version of I-D, draft-sriram-route-leak-detection-mitigation-00.txt has been successfully submitted by Kotikalapudi Sriram and posted to the IETF repository. Name: draft-sriram-route-leak-detection-mitigation Revision: 00 Title: Methods for Detection and Mitigation of BGP Route Leaks Document date: 2014-10-27 Group: Individual Submission Pages: 13 URL: http://www.ietf.org/internet-drafts/draft-sriram-route-leak-detection-mitigation-00.txt Status: https://datatracker.ietf.org/doc/draft-sriram-route-leak-detection-mitigation/ Htmlized: http://tools.ietf.org/html/draft-sriram-route-leak-detection-mitigation-00 Abstract: In [I-D.ietf-sriram-route-leak-problem-definition], the authors have provided a definition of the route leak problem, and also enumerated several types of route leaks. In this document, we first examine which of those route-leak types are detected and mitigated by the existing BGPSEC protocol [I-D.ietf-sidr-bgpsec-protocol-09]. Where the current BGPSEC protocol doesn't offer a solution, this document suggests an enhancement that would extend the route-leak detection and mitigation capability of BGPSEC. The solution can be implemented in BGP without necessarily tying it to BGPSEC. Incorporating the solution in BGPSEC is one way of implementing it in a secure way. We do not claim to have provided a solution for all possible types of route leaks, but the solution covers several, especially considering some significant route-leak attacks or occurrences that have been observed in recent years. The document also includes a stopgap method for detection and mitigation of route leaks for the phase when BGPSEC (path validation) is not yet deployed but only origin validation is deployed.
- [GROW] Fw: New Version Notification for draft-sri… Sriram, Kotikalapudi
- [GROW] Fw: New Version Notification for draft-sri… Sriram, Kotikalapudi