[sidr] A chair consensus statement on route leaks and forward plan

"Murphy, Sandra" <Sandra.Murphy@sparta.com> Mon, 15 July 2013 09:49 UTC

Return-Path: <Sandra.Murphy@sparta.com>
X-Original-To: sidr@ietfa.amsl.com
Delivered-To: sidr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8C44521F9FCA for <sidr@ietfa.amsl.com>; Mon, 15 Jul 2013 02:49:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, 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 Kl6fz4RoEMEl for <sidr@ietfa.amsl.com>; Mon, 15 Jul 2013 02:49:24 -0700 (PDT)
Received: from M4.sparta.com (M4.sparta.com [157.185.61.2]) by ietfa.amsl.com (Postfix) with ESMTP id 610FA21F9306 for <sidr@ietf.org>; Mon, 15 Jul 2013 02:49:24 -0700 (PDT)
Received: from Beta5.sparta.com ([10.62.8.21]) by M4.sparta.com (8.14.4/8.14.4) with ESMTP id r6F9nOlU031386 for <sidr@ietf.org>; Mon, 15 Jul 2013 04:49:24 -0500
Received: from CVA-HUB002.centreville.ads.sparta.com ([10.62.108.29]) by Beta5.sparta.com (8.13.8/8.13.8) with ESMTP id r6F9nN4I002351 for <sidr@ietf.org>; Mon, 15 Jul 2013 04:49:23 -0500
Received: from CVA-MB002.centreville.ads.sparta.com ([fe80::6046:a82a:c500:c9ad]) by CVA-HUB002.centreville.ads.sparta.com ([fe80::9817:c0c5:e172:9d1c%11]) with mapi id 14.02.0342.003; Mon, 15 Jul 2013 05:49:10 -0400
From: "Murphy, Sandra" <Sandra.Murphy@sparta.com>
To: "sidr@ietf.org" <sidr@ietf.org>
Thread-Topic: A chair consensus statement on route leaks and forward plan
Thread-Index: AQHOgT+0bqdsk6ZYZUuNblHf1J0BaA==
Date: Mon, 15 Jul 2013 09:49:09 +0000
Message-ID: <24B20D14B2CD29478C8D5D6E9CBB29F6749AFC79@CVA-MB002.centreville.ads.sparta.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.62.8.118]
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [sidr] A chair consensus statement on route leaks and forward plan
X-BeenThere: sidr@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Secure Interdomain Routing <sidr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sidr>, <mailto:sidr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sidr>
List-Post: <mailto:sidr@ietf.org>
List-Help: <mailto:sidr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sidr>, <mailto:sidr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Jul 2013 09:49:32 -0000

A chair consensus statement on route leaks and forward plan

Route leaks have been mentioned and discussed at length in the working group and in working group meetings many times.

One view is that route leaks are a critical concern to many operators and so should be included in the work of this working group.

The opposing view is that route leaks are not in scope of the wg charter.  Route leaks are presently ill-defined and even the common understanding seems to rely on arrangements between neighbors that are presently unpublished, and are not carried in the BGP protocol.

There were discussions and individual draft proposals for mechanisms that could extend the BGP protocol to communicate and enforce route leak constraints.

The rough consensus of the working group was that route leaks are an important problem but not presently within the scope of possible work in this working group.  The plan to address the problem has three steps – first, that definition and requirements would be considered in other working groups, then mechanisms for protection possibly including extensions to bgp could be developed, and then security protections for those mechanisms could be developed.  At present, definition and requirements is in the scope of the GROW working group, and any identified extensions to bgp that result would be in the scope of the IDR working group. 

At this point in time, the GROW working group has adopted one work item to define route leaks and has a draft under consideration.  It is not possible to state definitively that this work will progress or what the results or next steps will be.

--Sandy, speaking for the co-chairs