
From wwwrun@rfc-editor.org  Tue Nov  6 13:53:45 2012
Return-Path: <wwwrun@rfc-editor.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 693FC21F8B65; Tue,  6 Nov 2012 13:53:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.3
X-Spam-Level: 
X-Spam-Status: No, score=-102.3 tagged_above=-999 required=5 tests=[AWL=0.300,  BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cSZoPNcrKQ5o; Tue,  6 Nov 2012 13:53:44 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id EF40521F8B61; Tue,  6 Nov 2012 13:53:43 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 04ED8B1E01F; Tue,  6 Nov 2012 13:47:13 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20121106214713.04ED8B1E01F@rfc-editor.org>
Date: Tue,  6 Nov 2012 13:47:13 -0800 (PST)
Cc: grow@ietf.org, rfc-editor@rfc-editor.org
Subject: [GROW] RFC 6774 on Distribution of Diverse BGP Paths
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, 06 Nov 2012 21:53:45 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 6774

        Title:      Distribution of Diverse BGP Paths 
        Author:     R. Raszuk, Ed.,
                    R. Fernando, K. Patel,
                    D. McPherson, K. Kumaki
        Status:     Informational
        Stream:     IETF
        Date:       November 2012
        Mailbox:    robert@raszuk.net, 
                    rex@cisco.com, 
                    keyupate@cisco.com,
                    dmcpherson@verisign.com, 
                    ke-kumaki@kddi.com
        Pages:      22
        Characters: 48316
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-grow-diverse-bgp-path-dist-08.txt

        URL:        http://www.rfc-editor.org/rfc/rfc6774.txt

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 that are not
considered best path between its speakers.  This behavior results in a 
number of disadvantages for new applications and services.

The main objective of this document is to observe that by simply
adding a new session between a route reflector and its client, the Nth best
path can be distributed.  This 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 a software upgrade of provider edge (PE)
routers acting as route reflector clients.  This document is not an Internet 
Standards Track specification; it is published for informational purposes.

This document is a product of the Global Routing Operations Working Group of the IETF.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC



From xuxiaohu@huawei.com  Thu Nov  8 13:52:55 2012
Return-Path: <xuxiaohu@huawei.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 871F121F89D0 for <grow@ietfa.amsl.com>; Thu,  8 Nov 2012 13:52:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.446
X-Spam-Level: 
X-Spam-Status: No, score=-2.446 tagged_above=-999 required=5 tests=[AWL=-0.650, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kwPb7+-H29i6 for <grow@ietfa.amsl.com>; Thu,  8 Nov 2012 13:52:54 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 26F6F21F89A1 for <grow@ietf.org>; Thu,  8 Nov 2012 13:52:53 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id AMO04875; Thu, 08 Nov 2012 21:52:52 +0000 (GMT)
Received: from LHREML404-HUB.china.huawei.com (10.201.5.218) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 8 Nov 2012 21:52:38 +0000
Received: from SZXEML402-HUB.china.huawei.com (10.82.67.32) by lhreml404-hub.china.huawei.com (10.201.5.218) with Microsoft SMTP Server (TLS) id 14.1.323.3; Fri, 9 Nov 2012 05:52:51 +0800
Received: from SZXEML525-MBX.china.huawei.com ([169.254.1.161]) by szxeml402-hub.china.huawei.com ([::1]) with mapi id 14.01.0323.003; Fri, 9 Nov 2012 05:52:48 +0800
From: Xuxiaohu <xuxiaohu@huawei.com>
To: "rbonica@juniper.net" <rbonica@juniper.net>
Thread-Topic: Wake up two sleeping VA drafts?//: Last Call comments on draft-ietf-l3vpn-virtual-hub 
Thread-Index: AQHNvfsEMb5fV5gac0WMrTIRrVsjCQ==
Date: Thu, 8 Nov 2012 21:52:47 +0000
Message-ID: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0757029A@szxeml525-mbx.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.47.141.106]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "grow@ietf.org" <grow@ietf.org>
Subject: [GROW] Wake up two sleeping VA drafts?//: Last Call comments on draft-ietf-l3vpn-virtual-hub
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, 08 Nov 2012 21:52:55 -0000

SGkgUm9uYWxkLA0KDQpJZiBJIHJlbWVtYmVyZWQgY29ycmVjdGx5LCB5b3UgaGF2ZSBzYWlkLCBk
dXJpbmcgdGhlIFdHIGxhc3QgY2FsbCBvZiB0aHJlZSBWQSBkcmFmdCwgdGhhdCB5b3UgbWF5IHJl
Y29uc2lkZXIgeW91ciBhdHRpdHVkZXMgdG93YXJkcyB0aGUgdHdvIG9mIHRocmVlIFZBIGRyYWZ0
cyAoZHJhZnQtaWV0Zi1ncm93LXZhIGFuZCBkcmFmdC1pZXRmLWdyb3ctdmEtYXV0bykgaW4gY2Fz
ZSB0aGVyZSB3ZXJlIGFueSBpbnRlcmVzdHMgZnJvbSBTUHMgb24gdGhlIEZJQiBhZ2dyZWdhdGlv
bi4NCg0KSSBvY2Nhc2lvbmFsbHkgbm90aWNlZCB0aGF0IGRyYWZ0LWlldGYtbDN2cG4tdmlydHVh
bC1odWIgaGFzIGp1c3QgZGVjcmliZWQgYSB1c2UgY2FzZSBvZiBGSUIgYWdncmVnYXRpb24gIGFu
ZCBhIHBvc3NpYmxlIEZJQiBhZ2dyZWdhdGlvbiBhcHByb2FjaCB3aGljaCBzZWVtcyBtdWNoIHNp
bWlsYXIgdG8gdGhlIFZBIGFwcHJvYWNoIChzZWUgdGhlIGZvbGxvd2luZyB0ZXh0IHF1b3RlZCBm
cm9tIHRoYXQgZHJhZnQpLiBZb3UgbWF5IGhhdmUgbm90aWNlZCB0aGF0IG1vc3Qgb2YgdGhlIGNv
LWF1dGhvcnMgb2YgdGhpcyBkcmFmdCBhcmUgZnJvbSBTUHMuDQoNCkluIGFkZGl0aW9uLCB0aGVy
ZSBhcmUgbWFueSBjb25jZXJucyB3aXRoIHRoZSBmb3J3YXJkaW5nIHRhYmxlIHNjYWxhYmlsaXR5
IGlzc3VlcyBpbiB0aGUgbXVsdGktdGVuYW50IGNsb3VkIGRhdGEgY2VudGVyIG5ldHdvcmsgZW52
aXJvbm1lbnRzIHRoYXQgaGF2ZSBiZWVuIGV4cHJlc3NlZCBpbiBzZXZlcmFsIE5WbzMgcmVsYXRl
ZCBkcmFmdHMuDQoNCkhlbmNlIEkgd29uZGVyIHdoZXRoZXIgeW91IGNvdWxkIHBsZWFzZSByZWNv
bnNpZGVyIHlvdXIgYXR0aXR1ZGVzIHRvd2FyZHMgdGhlIHR3byBvZiB0aHJlZSBWQSByZWxhdGVk
IGRyYWZ0cy4gTWFueSB0aGFua3MhDQoNCg0KKioqKioqKioqKioqKioqKioqKioqKioqKioNCjku
IEZ1cnRoZXIgcmVmaW5lbWVudHMNCiAgIEluIHNvbWUgY2FzZXMgYSBWUE4gY3VzdG9tZXIgbWF5
IG5vdCB3YW50IHRvIHJlbHkgc29sZWx5IG9uIGFuIChJUCkNCiAgIGRlZmF1bHQgcm91dGUgYmVp
bmcgYWR2ZXJ0aXNlZCBmcm9tIGEgVi1zcG9rZSB0byBhIENFLCBidXQgbWF5IHdhbnQNCiAgIENF
cyB0byByZWNlaXZlIGFsbCB0aGUgVlBOIHJvdXRlcyAoZS5nLiwgZm9yIHRoZSBwdXJwb3NlIG9m
IGZhc3Rlcg0KICAgZGV0ZWN0aW9uIG9mIFZQTiBjb25uZWN0aXZpdHkgZmFpbHVyZXMsIGFuZCBh
Y3RpdmF0aW5nIHNvbWUgYmFja3VwDQogICBjb25uZWN0aXZpdHkpLg0KICAgSW4gdGhpcyBjYXNl
IG9uZSBwb3NzaWJsZSBhcHByb2FjaCB3b3VsZCBiZSB0byBpbnN0YWxsIGluIHRoZSBWLQ0KICAg
c3Bva2UncyBkYXRhIHBsYW5lIG9ubHkgdGhlIGRlZmF1bHQgcm91dGUgKGZvbGxvd2luZyB0aGUg
VmlydHVhbCBIdWINCiAgIGFuZCBTcG9rZSBtb2RlbCwgYXMgZGVzY3JpYmVkIGFib3ZlKSwgYnV0
IGtlZXAgYWxsIHRoZSBWUE4tSVAgcm91dGVzDQogICBpbiB0aGUgVi1zcG9rZSdzIGNvbnRyb2wg
cGxhbmUgKGFuZCB0aHVzIGJlaW5nIGFibGUgdG8gYWR2ZXJ0aXNlDQogICB0aGVzZSByb3V0ZXMg
ZnJvbSB0aGUgVi1zcG9rZSB0byB0aGUgQ0VzKS4gIEdyYW50ZWQsIHRoaXMgd291bGQgbm90DQog
ICBjaGFuZ2UgY29udHJvbCBwbGFuZSByZXNvdXJjZSBjb25zdW1wdGlvbiwgYnV0IHdvdWxkIChz
aWduaWZpY2FudGx5KQ0KICAgcmVkdWNlIHJlc291cmNlIGNvbnN1bXB0aW9uIG9uIHRoZSBkYXRh
IHBsYW5lLg0KKioqKioqKioqKioqKioqKioqKioqKioqKioqKioNCg0KQmVzdCByZWdhcmRzLA0K
WGlhb2h1DQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQq3orz+yMs6
IGwzdnBuLWJvdW5jZXNAaWV0Zi5vcmcgW2wzdnBuLWJvdW5jZXNAaWV0Zi5vcmddILT6se0gWWFr
b3YgUmVraHRlciBbeWFrb3ZAanVuaXBlci5uZXRdDQq3osvNyrG85DogMjAxMsTqMTHUwjjI1SAy
MzoxNw0Ktb06IGVyb3NlbkBjaXNjby5jb20NCkNjOiBMM1ZQTg0K1vfM4jogUmU6IExhc3QgQ2Fs
bCBjb21tZW50cyBvbiBkcmFmdC1pZXRmLWwzdnBuLXZpcnR1YWwtaHViDQoNCkVyaWMsDQoNCj4g
SSBoYXZlIGEgbnVtYmVyIG9mIGNvbW1lbnRzIG9uIHRoZSB2aXJ0dWFsLWh1YiBkcmFmdC4gIFNv
bWUgYXJlIG1pbm9yIGFuZC9vcg0KPiBlZGl0b3JpYWwsIGJ1dCBhIG51bWJlciBhcmUgbW9yZSBz
dWJzdGFudGlhbC4gIEkgdGhpbmsgdGhlc2UgY29tbWVudHMgbmVlZA0KPiB0byBiZSBhZGRyZXNz
ZWQgYmVmb3JlIHRoZSBkcmFmdCBpcyBzdWJtaXR0ZWQgZm9yIHB1YmxpY2F0aW9uLg0KPg0KPiBJ
J3ZlIHBsYWNlZCBhIGxvdCBvZiBjb21tZW50cyBpbi1saW5lLCBidXQgbGV0IG1lIHN1bW1hcml6
ZSB3aGF0IEkgdGhpbmsgYXJlDQo+IHRoZSBtYWpvciBpc3N1ZXM6DQoNCkkgYW0gaW4gdGhlIHBy
b2Nlc3Mgb2YgYWRkcmVzc2luZyB5b3VyIGNvbW1lbnRzLiBJbiB0aGlzIGUtbWFpbCBJJ2QgbGlr
ZQ0KdG8gZm9jdXMgb24gb25lIHBhcnRpY3VsYXIgb25lOg0KDQo+IEVyaWM+IExldCdzIGNvbnNp
ZGVyIHRoZSBjYXNlIHdoZXJlIHRoZSBzb3VyY2UgaXMgYXQgYSBzaXRlIGF0dGFjaGVkIHRvDQo+
IEVyaWM+IFYtaHViMi4gIFYtaHViMSB3aWxsIHJlY2VpdmUgYW4gUy1QTVNJIEEtRCByb3V0ZSBt
YXRjaGluZyAoUyxHKSBmcm9tDQo+IEVyaWM+IFYtaHViMi4gIFYtaHViMSB0aGVuIG1vZGlmaWVz
IHRoaXMgQS1EIHJvdXRlIGFuZCBmb3J3YXJkcyBpdCB0bw0KPiBFcmljPiBWLXNwb2tlMS4gIFYt
aHViMSBjb3VsZCB1c2UgdGhpcyByb3V0ZSB0byBpZGVudGlmeSB0aGUgUC10dW5uZWwNCj4gRXJp
Yz4gb3JpZ2luYXRpbmcgYXQgVi1odWIyLCB0aGVyZWJ5IGluc3RydWN0aW5nIFYtc3Bva2UxIHRv
IGpvaW4gVi1odWIyJ3MNCj4gRXJpYz4gdHVubmVsIGRpcmVjdGx5LiAgVGhlbiBWLWh1YjEgd291
bGQgbm90IGJlIGluIHRoZSBkYXRhIHBhdGggZnJvbSBTIHRvDQo+IEVyaWM+IFIsIGJ1dCBpdCB3
b3VsZCBwYXJ0aWNpcGF0ZSBpbiB0aGUgY29udHJvbCBwbGFuZS4gIFdvdWxkbid0IHRoaXMgbWVl
dA0KPiBFcmljPiBhbGwgdGhlIHJlcXVpcmVtZW50cyBvZiB0aGUgVi1odWIvVi1zcG9rZSBhcmNo
aXRlY3R1cmUsIHdoaWxlIHByb2R1Y2luZw0KPiBFcmljPiBhIG1vcmUgb3B0aW1hbCBwYXRoIGZv
ciBtdWx0aWNhc3QgZGF0YSwgYW5kIGVsaW1pbmF0aW5nIHRoZSBuZWVkIHRvDQo+IEVyaWM+IGhh
dmUgdGhlIFYtaHVicyBzcGxpY2UgdG9nZXRoZXIgYW55IFAtdHVubmVscz8NCj4NCj4gRXJpYz4g
V2FzIGFueSBjb25zaWRlcmF0aW9uIGdpdmVuIHRvIHN1Y2ggYW4gYWx0ZXJuYXRpdmU/DQoNClBs
ZWFzZSBub3RlIHRoYXQgdGhlIHByb2NlZHVyZXMgc3BlY2lmaWVkIGluIHRoZSBkcmFmdCBhc3N1
bWUNCnRoZSBhYmlsaXR5IHRvIHBlcmZvcm0gc2VuZGVyLWJhc2VkIFJQRiwgYXMgc3BlY2lmaWVk
IGluIDkuMS4xDQpvZiByZmM2NTEzLiBHaXZlbiB0aGF0LCBpZiBvbmUgd291bGQgZm9sbG93IHdo
YXQgeW91IG91dGxpbmVkIGFib3ZlLA0KY291bGQgeW91IHBvaW50IG1lIHRvIHRoZSBzcGVjaWZp
YyB0ZXh0IGluIDkuMS4xIHRoYXQgd291bGQNCmVuYWJsZSBWLXNwb2tlMSB0byBkZXRlcm1pbmUg
dGhhdCBmcm9tIGl0cyBvd24gcGVyc3BlY3RpdmUgdGhlDQpVTUggZm9yIChDLVMsIEMtRykgaXMg
Vi1odWIxID8NCg0KRnVydGhlcm1vcmUsIHlvdXIgb3V0bGluZSBhYm92ZSB0YWxrcyBhYm91dCBT
LVBNU0kgQS1EIHJvdXRlLiBIb3cNCndvdWxkIGl0IHdvcmsgZm9yIEktUE1TSSBBLUQgcm91dGVz
ID8NCg0KWWFrb3Yu

From rbonica@juniper.net  Fri Nov  9 08:29:31 2012
Return-Path: <rbonica@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 BDC2B21F8646 for <grow@ietfa.amsl.com>; Fri,  9 Nov 2012 08:29:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.793
X-Spam-Level: 
X-Spam-Status: No, score=-100.793 tagged_above=-999 required=5 tests=[AWL=-2.129, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-4, UNRESOLVED_TEMPLATE=3.132, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0MNH1D+gIS1u for <grow@ietfa.amsl.com>; Fri,  9 Nov 2012 08:29:31 -0800 (PST)
Received: from exprod7og121.obsmtp.com (exprod7og121.obsmtp.com [64.18.2.20]) by ietfa.amsl.com (Postfix) with ESMTP id F17A721F84DC for <grow@ietf.org>; Fri,  9 Nov 2012 08:29:30 -0800 (PST)
Received: from P-EMHUB03-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob121.postini.com ([64.18.6.12]) with SMTP ID DSNKUJ0vaknf3LEWKLmXlLRxXc0cDjCYYXOK@postini.com; Fri, 09 Nov 2012 08:29:31 PST
Received: from P-CLDFE01-HQ.jnpr.net (172.24.192.59) by P-EMHUB03-HQ.jnpr.net (172.24.192.37) with Microsoft SMTP Server (TLS) id 8.3.213.0; Fri, 9 Nov 2012 08:27:52 -0800
Received: from o365mail.juniper.net (207.17.137.149) by o365mail.juniper.net (172.24.192.59) with Microsoft SMTP Server id 14.1.355.2; Fri, 9 Nov 2012 08:27:51 -0800
Received: from ch1outboundpool.messaging.microsoft.com (216.32.181.186) by o365mail.juniper.net (207.17.137.149) with Microsoft SMTP Server (TLS) id 14.1.355.2; Fri, 9 Nov 2012 08:30:09 -0800
Received: from mail148-ch1-R.bigfish.com (10.43.68.243) by CH1EHSOBE012.bigfish.com (10.43.70.62) with Microsoft SMTP Server id 14.1.225.23; Fri, 9 Nov 2012 16:27:37 +0000
Received: from mail148-ch1 (localhost [127.0.0.1])	by mail148-ch1-R.bigfish.com (Postfix) with ESMTP id 97E1C3401D3	for <grow@ietf.org.FOPE.CONNECTOR.OVERRIDE>; Fri,  9 Nov 2012 16:27:37 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.245.197; KIP:(null); UIP:(null); (null); H:CH1PRD0511HT003.namprd05.prod.outlook.com; R:internal; EFV:INT
X-SpamScore: -28
X-BigFish: PS-28(zz9371Ic89bh103dK542M1432I1a09Jzz1de0h1202h1d1ah1d2ahzz1033IL8275bh8275dhz2dh2a8h668h839h941hd25hf0ah1269h1288h12a5h12a9h12bdh12e1h137ah13b6h1441h1504h1537h153bh15d0l1155h)
Received: from mail148-ch1 (localhost.localdomain [127.0.0.1]) by mail148-ch1 (MessageSwitch) id 135247845648562_631; Fri,  9 Nov 2012 16:27:36 +0000 (UTC)
Received: from CH1EHSMHS043.bigfish.com (snatpool1.int.messaging.microsoft.com [10.43.68.254])	by mail148-ch1.bigfish.com (Postfix) with ESMTP id 0A50C30001D;	Fri,  9 Nov 2012 16:27:36 +0000 (UTC)
Received: from CH1PRD0511HT003.namprd05.prod.outlook.com (157.56.245.197) by CH1EHSMHS043.bigfish.com (10.43.69.252) with Microsoft SMTP Server (TLS) id 14.1.225.23; Fri, 9 Nov 2012 16:27:35 +0000
Received: from CH1PRD0511MB418.namprd05.prod.outlook.com ([169.254.1.202]) by CH1PRD0511HT003.namprd05.prod.outlook.com ([10.255.159.38]) with mapi id 14.16.0233.002; Fri, 9 Nov 2012 16:27:35 +0000
From: Ronald Bonica <rbonica@juniper.net>
To: Xuxiaohu <xuxiaohu@huawei.com>
Thread-Topic: Wake up two sleeping VA drafts?//: Last Call comments on draft-ietf-l3vpn-virtual-hub 
Thread-Index: AQHNvfsEMb5fV5gac0WMrTIRrVsjCZfhshUg
Date: Fri, 9 Nov 2012 16:27:34 +0000
Message-ID: <2CF4CB03E2AA464BA0982EC92A02CE250652EC@CH1PRD0511MB418.namprd05.prod.outlook.com>
References: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0757029A@szxeml525-mbx.china.huawei.com>
In-Reply-To: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0757029A@szxeml525-mbx.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [66.129.232.2]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
X-FOPE-CONNECTOR: Id%12219$Dn%HUAWEI.COM$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net
X-FOPE-CONNECTOR: Id%12219$Dn%IETF.ORG$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net
Cc: "grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] Wake up two sleeping VA drafts?//: Last Call comments on draft-ietf-l3vpn-virtual-hub
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, 09 Nov 2012 16:29:31 -0000

SG93IGRvIGZvbGtzIG9uIHRoZSBsaXN0IGZlZWw/DQoNCiAgICAgICAgICAgICAgICAgICAgICAg
ICBSb24NCg0KDQo+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+IEZyb206IFh1eGlhb2h1
IFttYWlsdG86eHV4aWFvaHVAaHVhd2VpLmNvbV0NCj4gU2VudDogVGh1cnNkYXksIE5vdmVtYmVy
IDA4LCAyMDEyIDQ6NTMgUE0NCj4gVG86IFJvbmFsZCBCb25pY2ENCj4gQ2M6IGdyb3dAaWV0Zi5v
cmcNCj4gU3ViamVjdDogV2FrZSB1cCB0d28gc2xlZXBpbmcgVkEgZHJhZnRzPy8vOiBMYXN0IENh
bGwgY29tbWVudHMgb24NCj4gZHJhZnQtaWV0Zi1sM3Zwbi12aXJ0dWFsLWh1Yg0KPiANCj4gSGkg
Um9uYWxkLA0KPiANCj4gSWYgSSByZW1lbWJlcmVkIGNvcnJlY3RseSwgeW91IGhhdmUgc2FpZCwg
ZHVyaW5nIHRoZSBXRyBsYXN0IGNhbGwgb2YNCj4gdGhyZWUgVkEgZHJhZnQsIHRoYXQgeW91IG1h
eSByZWNvbnNpZGVyIHlvdXIgYXR0aXR1ZGVzIHRvd2FyZHMgdGhlIHR3bw0KPiBvZiB0aHJlZSBW
QSBkcmFmdHMgKGRyYWZ0LWlldGYtZ3Jvdy12YSBhbmQgZHJhZnQtaWV0Zi1ncm93LXZhLWF1dG8p
IGluDQo+IGNhc2UgdGhlcmUgd2VyZSBhbnkgaW50ZXJlc3RzIGZyb20gU1BzIG9uIHRoZSBGSUIg
YWdncmVnYXRpb24uDQo+IA0KPiBJIG9jY2FzaW9uYWxseSBub3RpY2VkIHRoYXQgZHJhZnQtaWV0
Zi1sM3Zwbi12aXJ0dWFsLWh1YiBoYXMganVzdA0KPiBkZWNyaWJlZCBhIHVzZSBjYXNlIG9mIEZJ
QiBhZ2dyZWdhdGlvbiAgYW5kIGEgcG9zc2libGUgRklCIGFnZ3JlZ2F0aW9uDQo+IGFwcHJvYWNo
IHdoaWNoIHNlZW1zIG11Y2ggc2ltaWxhciB0byB0aGUgVkEgYXBwcm9hY2ggKHNlZSB0aGUgZm9s
bG93aW5nDQo+IHRleHQgcXVvdGVkIGZyb20gdGhhdCBkcmFmdCkuIFlvdSBtYXkgaGF2ZSBub3Rp
Y2VkIHRoYXQgbW9zdCBvZiB0aGUgY28tDQo+IGF1dGhvcnMgb2YgdGhpcyBkcmFmdCBhcmUgZnJv
bSBTUHMuDQo+IA0KPiBJbiBhZGRpdGlvbiwgdGhlcmUgYXJlIG1hbnkgY29uY2VybnMgd2l0aCB0
aGUgZm9yd2FyZGluZyB0YWJsZQ0KPiBzY2FsYWJpbGl0eSBpc3N1ZXMgaW4gdGhlIG11bHRpLXRl
bmFudCBjbG91ZCBkYXRhIGNlbnRlciBuZXR3b3JrDQo+IGVudmlyb25tZW50cyB0aGF0IGhhdmUg
YmVlbiBleHByZXNzZWQgaW4gc2V2ZXJhbCBOVm8zIHJlbGF0ZWQgZHJhZnRzLg0KPiANCj4gSGVu
Y2UgSSB3b25kZXIgd2hldGhlciB5b3UgY291bGQgcGxlYXNlIHJlY29uc2lkZXIgeW91ciBhdHRp
dHVkZXMNCj4gdG93YXJkcyB0aGUgdHdvIG9mIHRocmVlIFZBIHJlbGF0ZWQgZHJhZnRzLiBNYW55
IHRoYW5rcyENCj4gDQo+IA0KPiAqKioqKioqKioqKioqKioqKioqKioqKioqKg0KPiA5LiBGdXJ0
aGVyIHJlZmluZW1lbnRzDQo+ICAgIEluIHNvbWUgY2FzZXMgYSBWUE4gY3VzdG9tZXIgbWF5IG5v
dCB3YW50IHRvIHJlbHkgc29sZWx5IG9uIGFuIChJUCkNCj4gICAgZGVmYXVsdCByb3V0ZSBiZWlu
ZyBhZHZlcnRpc2VkIGZyb20gYSBWLXNwb2tlIHRvIGEgQ0UsIGJ1dCBtYXkgd2FudA0KPiAgICBD
RXMgdG8gcmVjZWl2ZSBhbGwgdGhlIFZQTiByb3V0ZXMgKGUuZy4sIGZvciB0aGUgcHVycG9zZSBv
ZiBmYXN0ZXINCj4gICAgZGV0ZWN0aW9uIG9mIFZQTiBjb25uZWN0aXZpdHkgZmFpbHVyZXMsIGFu
ZCBhY3RpdmF0aW5nIHNvbWUgYmFja3VwDQo+ICAgIGNvbm5lY3Rpdml0eSkuDQo+ICAgIEluIHRo
aXMgY2FzZSBvbmUgcG9zc2libGUgYXBwcm9hY2ggd291bGQgYmUgdG8gaW5zdGFsbCBpbiB0aGUg
Vi0NCj4gICAgc3Bva2UncyBkYXRhIHBsYW5lIG9ubHkgdGhlIGRlZmF1bHQgcm91dGUgKGZvbGxv
d2luZyB0aGUgVmlydHVhbCBIdWINCj4gICAgYW5kIFNwb2tlIG1vZGVsLCBhcyBkZXNjcmliZWQg
YWJvdmUpLCBidXQga2VlcCBhbGwgdGhlIFZQTi1JUCByb3V0ZXMNCj4gICAgaW4gdGhlIFYtc3Bv
a2UncyBjb250cm9sIHBsYW5lIChhbmQgdGh1cyBiZWluZyBhYmxlIHRvIGFkdmVydGlzZQ0KPiAg
ICB0aGVzZSByb3V0ZXMgZnJvbSB0aGUgVi1zcG9rZSB0byB0aGUgQ0VzKS4gIEdyYW50ZWQsIHRo
aXMgd291bGQgbm90DQo+ICAgIGNoYW5nZSBjb250cm9sIHBsYW5lIHJlc291cmNlIGNvbnN1bXB0
aW9uLCBidXQgd291bGQgKHNpZ25pZmljYW50bHkpDQo+ICAgIHJlZHVjZSByZXNvdXJjZSBjb25z
dW1wdGlvbiBvbiB0aGUgZGF0YSBwbGFuZS4NCj4gKioqKioqKioqKioqKioqKioqKioqKioqKioq
KioNCj4gDQo+IEJlc3QgcmVnYXJkcywNCj4gWGlhb2h1DQo+IF9fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX18NCj4gt6K8/sjLOiBsM3Zwbi1ib3VuY2VzQGlldGYub3JnIFts
M3Zwbi1ib3VuY2VzQGlldGYub3JnXSC0+rHtIFlha292DQo+IFJla2h0ZXIgW3lha292QGp1bmlw
ZXIubmV0XQ0KPiC3osvNyrG85DogMjAxMsTqMTHUwjjI1SAyMzoxNw0KPiC1vTogZXJvc2VuQGNp
c2NvLmNvbQ0KPiBDYzogTDNWUE4NCj4g1vfM4jogUmU6IExhc3QgQ2FsbCBjb21tZW50cyBvbiBk
cmFmdC1pZXRmLWwzdnBuLXZpcnR1YWwtaHViDQo+IA0KPiBFcmljLA0KPiANCj4gPiBJIGhhdmUg
YSBudW1iZXIgb2YgY29tbWVudHMgb24gdGhlIHZpcnR1YWwtaHViIGRyYWZ0LiAgU29tZSBhcmUg
bWlub3INCj4gPiBhbmQvb3IgZWRpdG9yaWFsLCBidXQgYSBudW1iZXIgYXJlIG1vcmUgc3Vic3Rh
bnRpYWwuICBJIHRoaW5rIHRoZXNlDQo+ID4gY29tbWVudHMgbmVlZCB0byBiZSBhZGRyZXNzZWQg
YmVmb3JlIHRoZSBkcmFmdCBpcyBzdWJtaXR0ZWQgZm9yDQo+IHB1YmxpY2F0aW9uLg0KPiA+DQo+
ID4gSSd2ZSBwbGFjZWQgYSBsb3Qgb2YgY29tbWVudHMgaW4tbGluZSwgYnV0IGxldCBtZSBzdW1t
YXJpemUgd2hhdCBJDQo+ID4gdGhpbmsgYXJlIHRoZSBtYWpvciBpc3N1ZXM6DQo+IA0KPiBJIGFt
IGluIHRoZSBwcm9jZXNzIG9mIGFkZHJlc3NpbmcgeW91ciBjb21tZW50cy4gSW4gdGhpcyBlLW1h
aWwgSSdkDQo+IGxpa2UgdG8gZm9jdXMgb24gb25lIHBhcnRpY3VsYXIgb25lOg0KPiANCj4gPiBF
cmljPiBMZXQncyBjb25zaWRlciB0aGUgY2FzZSB3aGVyZSB0aGUgc291cmNlIGlzIGF0IGEgc2l0
ZSBhdHRhY2hlZA0KPiA+IEVyaWM+IHRvIFYtaHViMi4gIFYtaHViMSB3aWxsIHJlY2VpdmUgYW4g
Uy1QTVNJIEEtRCByb3V0ZSBtYXRjaGluZw0KPiA+IEVyaWM+IChTLEcpIGZyb20gVi1odWIyLiAg
Vi1odWIxIHRoZW4gbW9kaWZpZXMgdGhpcyBBLUQgcm91dGUgYW5kDQo+ID4gRXJpYz4gZm9yd2Fy
ZHMgaXQgdG8gVi1zcG9rZTEuICBWLWh1YjEgY291bGQgdXNlIHRoaXMgcm91dGUgdG8NCj4gPiBF
cmljPiBpZGVudGlmeSB0aGUgUC10dW5uZWwgb3JpZ2luYXRpbmcgYXQgVi1odWIyLCB0aGVyZWJ5
DQo+IGluc3RydWN0aW5nDQo+ID4gRXJpYz4gVi1zcG9rZTEgdG8gam9pbiBWLWh1YjIncyB0dW5u
ZWwgZGlyZWN0bHkuICBUaGVuIFYtaHViMSB3b3VsZA0KPiA+IEVyaWM+IG5vdCBiZSBpbiB0aGUg
ZGF0YSBwYXRoIGZyb20gUyB0byBSLCBidXQgaXQgd291bGQgcGFydGljaXBhdGUNCj4gaW4NCj4g
PiBFcmljPiB0aGUgY29udHJvbCBwbGFuZS4gIFdvdWxkbid0IHRoaXMgbWVldCBhbGwgdGhlIHJl
cXVpcmVtZW50cyBvZg0KPiA+IEVyaWM+IHRoZSBWLWh1Yi9WLXNwb2tlIGFyY2hpdGVjdHVyZSwg
d2hpbGUgcHJvZHVjaW5nIGEgbW9yZSBvcHRpbWFsDQo+ID4gRXJpYz4gcGF0aCBmb3IgbXVsdGlj
YXN0IGRhdGEsIGFuZCBlbGltaW5hdGluZyB0aGUgbmVlZCB0byBoYXZlIHRoZQ0KPiBWLWh1YnMg
c3BsaWNlIHRvZ2V0aGVyIGFueSBQLXR1bm5lbHM/DQo+ID4NCj4gPiBFcmljPiBXYXMgYW55IGNv
bnNpZGVyYXRpb24gZ2l2ZW4gdG8gc3VjaCBhbiBhbHRlcm5hdGl2ZT8NCj4gDQo+IFBsZWFzZSBu
b3RlIHRoYXQgdGhlIHByb2NlZHVyZXMgc3BlY2lmaWVkIGluIHRoZSBkcmFmdCBhc3N1bWUgdGhl
DQo+IGFiaWxpdHkgdG8gcGVyZm9ybSBzZW5kZXItYmFzZWQgUlBGLCBhcyBzcGVjaWZpZWQgaW4g
OS4xLjEgb2YgcmZjNjUxMy4NCj4gR2l2ZW4gdGhhdCwgaWYgb25lIHdvdWxkIGZvbGxvdyB3aGF0
IHlvdSBvdXRsaW5lZCBhYm92ZSwgY291bGQgeW91DQo+IHBvaW50IG1lIHRvIHRoZSBzcGVjaWZp
YyB0ZXh0IGluIDkuMS4xIHRoYXQgd291bGQgZW5hYmxlIFYtc3Bva2UxIHRvDQo+IGRldGVybWlu
ZSB0aGF0IGZyb20gaXRzIG93biBwZXJzcGVjdGl2ZSB0aGUgVU1IIGZvciAoQy1TLCBDLUcpIGlz
IFYtDQo+IGh1YjEgPw0KPiANCj4gRnVydGhlcm1vcmUsIHlvdXIgb3V0bGluZSBhYm92ZSB0YWxr
cyBhYm91dCBTLVBNU0kgQS1EIHJvdXRlLiBIb3cgd291bGQNCj4gaXQgd29yayBmb3IgSS1QTVNJ
IEEtRCByb3V0ZXMgPw0KPiANCj4gWWFrb3YuDQo=


From shtsuchi@cisco.com  Fri Nov  9 21:25:55 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 677E021F8682 for <grow@ietfa.amsl.com>; Fri,  9 Nov 2012 21:25:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.998
X-Spam-Level: 
X-Spam-Status: No, score=-9.998 tagged_above=-999 required=5 tests=[AWL=0.001,  BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 010fZU0QEpJl for <grow@ietfa.amsl.com>; Fri,  9 Nov 2012 21:25:54 -0800 (PST)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) by ietfa.amsl.com (Postfix) with ESMTP id 7FA0721F866E for <grow@ietf.org>; Fri,  9 Nov 2012 21:25:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4804; q=dns/txt; s=iport; t=1352525154; x=1353734754; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=+hVhzWPR1oOOot0qzZtaQVCOpHqAperoQpc5nGaFMSc=; b=jG8575zRpyV0sIQPDHiI7MUXBZCoxWpzKcztJX59oyKgFfcGcd4hSPZa rYs9AG8eBq/B9FSPasdCsnnB/gyn7AbOXJ08Hu3Owm7WDPIbcfFTlclbp s7yEfN7YdBgefVGEXU3SENpDMJqt9Hkgph1+Lh+i8KTP0cXLLQt6NYdyo k=;
X-IronPort-AV: E=McAfee;i="5400,1158,6891"; a="140795960"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-2.cisco.com with ESMTP; 10 Nov 2012 05:25:54 +0000
Received: from [10.82.241.196] (rtp-vpn2-452.cisco.com [10.82.241.196]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id qAA5PpwO020511;  Sat, 10 Nov 2012 05:25:52 GMT
Message-ID: <509DE55E.7080309@cisco.com>
Date: Sat, 10 Nov 2012 00:25:50 -0500
From: Shishio Tsuchiya <shtsuchi@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: rbonica@juniper.net
References: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0757029A@szxeml525-mbx.china.huawei.com> <2CF4CB03E2AA464BA0982EC92A02CE250652EC@CH1PRD0511MB418.namprd05.prod.outlook.com>
In-Reply-To: <2CF4CB03E2AA464BA0982EC92A02CE250652EC@CH1PRD0511MB418.namprd05.prod.outlook.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Cc: grow@ietf.org
Subject: Re: [GROW] Wake up two sleeping VA drafts?//: Last Call comments on draft-ietf-l3vpn-virtual-hub
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, 10 Nov 2012 05:25:55 -0000

I like and support "draft-ietf-grow-va".
I think "draft-ietf-grow-va" would be one of useful design document/technic for FIB suppression.

Regards,
-Shishio


(2012/11/09 11:27), Ronald Bonica wrote:
> How do folks on the list feel?
>
>                           Ron
>
>
>> -----Original Message-----
>> From: Xuxiaohu [mailto:xuxiaohu@huawei.com]
>> Sent: Thursday, November 08, 2012 4:53 PM
>> To: Ronald Bonica
>> Cc: grow@ietf.org
>> Subject: Wake up two sleeping VA drafts?//: Last Call comments on
>> draft-ietf-l3vpn-virtual-hub
>>
>> Hi Ronald,
>>
>> If I remembered correctly, you have said, during the WG last call of
>> three VA draft, that you may reconsider your attitudes towards the two
>> of three VA drafts (draft-ietf-grow-va and draft-ietf-grow-va-auto) in
>> case there were any interests from SPs on the FIB aggregation.
>>
>> I occasionally noticed that draft-ietf-l3vpn-virtual-hub has just
>> decribed a use case of FIB aggregation  and a possible FIB aggregation
>> approach which seems much similar to the VA approach (see the following
>> text quoted from that draft). You may have noticed that most of the co-
>> authors of this draft are from SPs.
>>
>> In addition, there are many concerns with the forwarding table
>> scalability issues in the multi-tenant cloud data center network
>> environments that have been expressed in several NVo3 related drafts.
>>
>> Hence I wonder whether you could please reconsider your attitudes
>> towards the two of three VA related drafts. Many thanks!
>>
>>
>> **************************
>> 9. Further refinements
>>     In some cases a VPN customer may not want to rely solely on an (IP)
>>     default route being advertised from a V-spoke to a CE, but may want
>>     CEs to receive all the VPN routes (e.g., for the purpose of faster
>>     detection of VPN connectivity failures, and activating some backup
>>     connectivity).
>>     In this case one possible approach would be to install in the V-
>>     spoke's data plane only the default route (following the Virtual Hub
>>     and Spoke model, as described above), but keep all the VPN-IP routes
>>     in the V-spoke's control plane (and thus being able to advertise
>>     these routes from the V-spoke to the CEs).  Granted, this would not
>>     change control plane resource consumption, but would (significantly)
>>     reduce resource consumption on the data plane.
>> *****************************
>>
>> Best regards,
>> Xiaohu
>> ________________________________________
>> 发件人: l3vpn-bounces@ietf.org [l3vpn-bounces@ietf.org] 代表 Yakov
>> Rekhter [yakov@juniper.net]
>> 发送时间: 2012年11月8日 23:17
>> 到: erosen@cisco.com
>> Cc: L3VPN
>> 主题: Re: Last Call comments on draft-ietf-l3vpn-virtual-hub
>>
>> Eric,
>>
>>> I have a number of comments on the virtual-hub draft.  Some are minor
>>> and/or editorial, but a number are more substantial.  I think these
>>> comments need to be addressed before the draft is submitted for
>> publication.
>>>
>>> I've placed a lot of comments in-line, but let me summarize what I
>>> think are the major issues:
>>
>> I am in the process of addressing your comments. In this e-mail I'd
>> like to focus on one particular one:
>>
>>> Eric> Let's consider the case where the source is at a site attached
>>> Eric> to V-hub2.  V-hub1 will receive an S-PMSI A-D route matching
>>> Eric> (S,G) from V-hub2.  V-hub1 then modifies this A-D route and
>>> Eric> forwards it to V-spoke1.  V-hub1 could use this route to
>>> Eric> identify the P-tunnel originating at V-hub2, thereby
>> instructing
>>> Eric> V-spoke1 to join V-hub2's tunnel directly.  Then V-hub1 would
>>> Eric> not be in the data path from S to R, but it would participate
>> in
>>> Eric> the control plane.  Wouldn't this meet all the requirements of
>>> Eric> the V-hub/V-spoke architecture, while producing a more optimal
>>> Eric> path for multicast data, and eliminating the need to have the
>> V-hubs splice together any P-tunnels?
>>>
>>> Eric> Was any consideration given to such an alternative?
>>
>> Please note that the procedures specified in the draft assume the
>> ability to perform sender-based RPF, as specified in 9.1.1 of rfc6513.
>> Given that, if one would follow what you outlined above, could you
>> point me to the specific text in 9.1.1 that would enable V-spoke1 to
>> determine that from its own perspective the UMH for (C-S, C-G) is V-
>> hub1 ?
>>
>> Furthermore, your outline above talks about S-PMSI A-D route. How would
>> it work for I-PMSI A-D routes ?
>>
>> Yakov.
> _______________________________________________
> GROW mailing list
> GROW@ietf.org
> https://www.ietf.org/mailman/listinfo/grow
>



From christopher.morrow@gmail.com  Fri Nov  9 23:11:40 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 0FF0B21F85D4 for <grow@ietfa.amsl.com>; Fri,  9 Nov 2012 23:11:40 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QXQQ2XYdY0r4 for <grow@ietfa.amsl.com>; Fri,  9 Nov 2012 23:11:39 -0800 (PST)
Received: from mail-ee0-f44.google.com (mail-ee0-f44.google.com [74.125.83.44]) by ietfa.amsl.com (Postfix) with ESMTP id 5C68021F853F for <grow@ietf.org>; Fri,  9 Nov 2012 23:11:30 -0800 (PST)
Received: by mail-ee0-f44.google.com with SMTP id d4so2875485eek.31 for <grow@ietf.org>; Fri, 09 Nov 2012 23:11:30 -0800 (PST)
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=jsjPEMaE0aKV92bwXUzXoreuaaYC+CB3ae9E26vhNSY=; b=dTe5LbvBTWVHwK8u6pVxKSikKm7vnSbno6sjsu8FmFrMrhuAIbWcVXK/PQMFJ6jBWr hDmEzDUX4wX/f7YXT+veS/T1o9uCSJtvW8MxP0CjOYJWuvWc6z9Da4iQuV7ffxsA9D53 DyCyVvP5BWnP1EGFWG7FiJhELAqrV6Qo5gsLvr9f4FactqmxQdEB/pDtCV2aK/yT8JXF C7zrvWmEoi5N637t5ErWFgRTTYPbGmnYW1Ioq90l8Ku//2Ysi8Oo8TVRDM9bBnS/pwTW j17R1iJWztsWHotpMxv1V8nmob2fMeEKg4F0KTE3eLbDt74KVNdqSJMx0aEhbicEWW55 xOMg==
MIME-Version: 1.0
Received: by 10.14.199.134 with SMTP id x6mr44294498een.31.1352531490277; Fri, 09 Nov 2012 23:11:30 -0800 (PST)
Received: by 10.223.177.71 with HTTP; Fri, 9 Nov 2012 23:11:30 -0800 (PST)
Date: Sat, 10 Nov 2012 02:11:30 -0500
Message-ID: <CAL9jLaac30PC0rqiRmZbSP8-nwz2fwM3-_f3HHJijPWX9xS6AQ@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
Subject: [GROW] Meeting minutes/slides
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, 10 Nov 2012 07:11:40 -0000

all are now uploaded, apologies for the hectic meeting start AND not
having the slides available at the start.

I still owe mail about:
  1) Route Leaks - Fallout from SIDR/IDR discussions
  2) IRR Efficacy draft adoption

Please let me know if I missed something in that list (short list).

-chris
co-chair

From christopher.morrow@gmail.com  Wed Nov 14 14:18:28 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 DF7D921F882F for <grow@ietfa.amsl.com>; Wed, 14 Nov 2012 14:18:27 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TGMA0CMK+3Ob for <grow@ietfa.amsl.com>; Wed, 14 Nov 2012 14:18:27 -0800 (PST)
Received: from mail-ee0-f44.google.com (mail-ee0-f44.google.com [74.125.83.44]) by ietfa.amsl.com (Postfix) with ESMTP id B12FB21F880F for <grow@ietf.org>; Wed, 14 Nov 2012 14:18:20 -0800 (PST)
Received: by mail-ee0-f44.google.com with SMTP id b47so671010eek.31 for <grow@ietf.org>; Wed, 14 Nov 2012 14:18:20 -0800 (PST)
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=/D5RyoeCJPuD5b/dmsil4MF9Ztp8QIo5erm8WlgRVDs=; b=z7xxcu2kKzuFzK9M7Koe9kW2k8gYxEAv+ptRv6yb/uFF+zVpscacnuuykhLwnS3ExA VLrk1u3YSSJxLpQAEBDcDM0TczalGyLNLEA29gcCxhqN5YOIaBQOI8JOSIrPm5c1DnTq QpGpPeiN3rGaipLlq1BzTd0oPNS9zv8N8boZggCN9ukQhVRfCzY9C02XhqGQ3T5POYNf CzlcEqM8HKraEjYML+U7NRqZfW7BsYIupdOe3coSUQ3RQNNAFdE8FCV6mNYLGEzI6+n2 0fIgbpspcZTT/6hDGx042r2Dz3Bp1xse80m66P5V7MAI6Hpw2MV+g7rvUSLSpu7UWC9b GD5Q==
MIME-Version: 1.0
Received: by 10.14.179.69 with SMTP id g45mr91574965eem.42.1352931499922; Wed, 14 Nov 2012 14:18:19 -0800 (PST)
Received: by 10.223.177.71 with HTTP; Wed, 14 Nov 2012 14:18:19 -0800 (PST)
Date: Wed, 14 Nov 2012 17:18:19 -0500
Message-ID: <CAL9jLaagY5bBe_8eRST8noEp2-o00Zkm2Qc59Ys7pak++EPGNw@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>,  draft-foo-sidr-simple-leak-attack-bgpsec-no-help@tools.ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Subject: [GROW] RouteLeaks - problem or not?
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, 14 Nov 2012 22:18:28 -0000

GROW Folks,
The SIDR working group is working on security for origination and path
data related to BGP routes. There has been a note (a few) about SIDR's
effect(s) or not on 'route leaks'. There have even been a few notes on
'what is a route leak'. To date there is a draft which discusses route
leaks:
  <http://tools.ietf.org/html/draft-foo-sidr-simple-leak-attack-bgpsec-no-help-02>

where the authors have attempted to describe one (or many possible)
situations which are called 'route leaks'. They also attempt to
outline security issues which are follow-on effects of the situation
described.

SIDR attempted to look at route-leaks and came up a bit stymied, they
asked IDR for some assistance with the issue, IDR pushed back to GROW
to decide:
  1) What is a 'route leak' (perhaps the above draft identifies one
examplar to be used in that definition)
  2) Are 'route leaks' a problem that Operations folks care about
  3) Should IDR (or the IETF proper) address 'route leaks' with some
form(s) of fix action.

The end result of the above 3 steps is to push back into IDR one of
two action requests:
  1) "Yes, route leaks are a problem, please fix them."
     or
  2) "No, route leaks are not a problem, take no action."

If #1 above is the answer, and IDR decides that changes to the BGP
protocol are warranted (or are a possible solution to the problem)
then SIDR has agreed to do what they can to 'secure' the bits
added/changed/used in that endeavor.

Could we have some discussion on-list about this problem, and some
discussion about whether or not the draft referenced above fits the
definition we would like to use for 'route leak'? I would also like
the authors of the draft to decide where they would like to take their
draft:
   1) SIDR
   2) IDR
   3) GROW
   4) other

Thanks!
-Chris
(co-chair 1:2 of grow, and 1:3 in sidr)

From christopher.morrow@gmail.com  Wed Nov 14 14:35:58 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 A07A021F8814 for <grow@ietfa.amsl.com>; Wed, 14 Nov 2012 14:35:58 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FKMH91L0G5MZ for <grow@ietfa.amsl.com>; Wed, 14 Nov 2012 14:35:58 -0800 (PST)
Received: from mail-ee0-f44.google.com (mail-ee0-f44.google.com [74.125.83.44]) by ietfa.amsl.com (Postfix) with ESMTP id C8C5921F84F9 for <grow@ietf.org>; Wed, 14 Nov 2012 14:35:57 -0800 (PST)
Received: by mail-ee0-f44.google.com with SMTP id b47so679675eek.31 for <grow@ietf.org>; Wed, 14 Nov 2012 14:35:57 -0800 (PST)
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=0AAGdrQFd58d04l2AC8KsXD7q1aGfhloPCRUrNe6Rt4=; b=IWe+mmXqw4FLsGclV/m3zBFrKbCHyvDV9kkUCrDUN2Ru7mQaOTSUwcBb3etNxuK69c FqqqFkNTPGRT2Qvp3TsL87eHVi3/hWKtWdDZ2ljbqmLMxAqMLdX69aB3A5lW1kX+RtM1 FYERGYh3k2citRLf1UGFSr+JXrDuYaushx890YLqJAyP6p0Fr4ZAactYonQDJcI10kq9 eTkXaLelKMq+BU9bW9fJK8eMxF1ZCtHSKum27htCeScBAN0snDsC84yFgE2m0f6lva6C iO1Nlp27NZ7jZP9S2gQLSNDiIS1uCfaZOAfJ0AcPDOSamimV4Q2xLLxDUM24dxWwCe35 2KaQ==
MIME-Version: 1.0
Received: by 10.14.209.201 with SMTP id s49mr18492925eeo.7.1352932556995; Wed, 14 Nov 2012 14:35:56 -0800 (PST)
Received: by 10.223.177.71 with HTTP; Wed, 14 Nov 2012 14:35:56 -0800 (PST)
Date: Wed, 14 Nov 2012 17:35:56 -0500
Message-ID: <CAL9jLabt0S98HEygsQp=a98ARwiRxJ2x3F2=H5w-pDRbyqWE7A@mail.gmail.com>
From: Christopher Morrow <christopher.morrow@gmail.com>
To: grow-ads@tools.ietf.org, grow-chairs@tools.ietf.org,  "grow@ietf.org grow@ietf.org" <grow@ietf.org>,  draft-mcpherson-irr-routing-policy-considerations@tools.ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Subject: [GROW] WG Adoption call: draft-mcpherson-irr-routing-policy-considerations (END: 11/28/2012)
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, 14 Nov 2012 22:35:58 -0000

Grow Folks,
the authors of:  draft-mcpherson-irr-routing-policy-considerations
  <http://tools.ietf.org/html/draft-mcpherson-irr-routing-policy-considerations-01>

have asked if their work is appropriate for the GROW-wg, could we take
the next 14 days (ending Nov 28, 2012) to think/discuss this draft and
it's efficacy to work in the GROW arena? The abstract of the draft is:
  "The purpose of this document is to catalog past issues influencing
   the efficacy of Internet Routing Registries (IRR) for inter-domain
   routing policy specification and application in the global routing
   system over the past two decades.  Additionally, it provides a
   discussion regarding which of these issues are still problematic in
   practice, and which are simply artifacts that are no longer
   applicable but continue to stifle inter-provider policy-based
   filtering adoption and IRR utility to this day."

Thanks!
-Chris
(co-chair)

From christopher.morrow@gmail.com  Wed Nov 14 14:44:28 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 BB01321F887D for <grow@ietfa.amsl.com>; Wed, 14 Nov 2012 14:44:27 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iMIxC5BS8wgA for <grow@ietfa.amsl.com>; Wed, 14 Nov 2012 14:44:27 -0800 (PST)
Received: from mail-ea0-f172.google.com (mail-ea0-f172.google.com [209.85.215.172]) by ietfa.amsl.com (Postfix) with ESMTP id C46EA21F884D for <grow@ietf.org>; Wed, 14 Nov 2012 14:44:26 -0800 (PST)
Received: by mail-ea0-f172.google.com with SMTP id k13so463981eaa.31 for <grow@ietf.org>; Wed, 14 Nov 2012 14:44:26 -0800 (PST)
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; bh=3kkX/jJpWTmBbdGUB+HfoJWrcIMXBvCxXALTf+LxaAM=; b=nQh/1vjNeNJGy5/fbi0GHqF23/1QppZCSn2noj8lwjhkTiG56UtuVSj3t5Hd/9DXAh wdXWM204xYtbdx9Tu59T2IIKm/UH1kQd1+VEDaPfGIXebrpBMnQUdFA11oHbl7xorwfq Rg3xK6s9/I39dcjs+PeYZ6Zicqrtch7DBeAfCnXFA0kDR7jUKIY3BeNxrTxgZ2sqhbHm 7VIca+KuTGJCQxMoBR3B7NrlgUaNssbEK701YZj2BYzmzw6/y1OLzeQWwWzqnVDMDG1O Ga+kr1CkKRYZTYo9bDbdr1ZeOMVZMEtWGcmwsHzasGEZQIZw3tNReRmUa1XXb2CpNKuK uwJw==
MIME-Version: 1.0
Received: by 10.14.175.71 with SMTP id y47mr91660482eel.36.1352933065988; Wed, 14 Nov 2012 14:44:25 -0800 (PST)
Received: by 10.223.177.71 with HTTP; Wed, 14 Nov 2012 14:44:25 -0800 (PST)
In-Reply-To: <CAL9jLaagY5bBe_8eRST8noEp2-o00Zkm2Qc59Ys7pak++EPGNw@mail.gmail.com>
References: <CAL9jLaagY5bBe_8eRST8noEp2-o00Zkm2Qc59Ys7pak++EPGNw@mail.gmail.com>
Date: Wed, 14 Nov 2012 17:44:25 -0500
Message-ID: <CAL9jLaZT43OBwHqWs-xzy8qCm1UEyfN+hDKTgdrrvCc09xWNHw@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>,  draft-foo-sidr-simple-leak-attack-bgpsec-no-help@tools.ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [GROW] RouteLeaks - problem or not?
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, 14 Nov 2012 22:44:28 -0000

Apologies for the extra spam, there was a topic point I missed in this
mail, see below please.

On Wed, Nov 14, 2012 at 5:18 PM, Christopher Morrow
<christopher.morrow@gmail.com> wrote:
> GROW Folks,
> The SIDR working group is working on security for origination and path
> data related to BGP routes. There has been a note (a few) about SIDR's
> effect(s) or not on 'route leaks'. There have even been a few notes on
> 'what is a route leak'. To date there is a draft which discusses route
> leaks:
>   <http://tools.ietf.org/html/draft-foo-sidr-simple-leak-attack-bgpsec-no-help-02>
>
> where the authors have attempted to describe one (or many possible)
> situations which are called 'route leaks'. They also attempt to
> outline security issues which are follow-on effects of the situation
> described.
>

Additionally there were several drafts written by Brian Dickson aiming
to provide some definitions about route-leaks and some direction for a
solution, they are:
  <http://tools.ietf.org/html/draft-dickson-sidr-route-leak-def-03>
  <http://tools.ietf.org/html/draft-dickson-sidr-route-leak-solns-01>
  <http://tools.ietf.org/html/draft-dickson-sidr-route-leak-reqts-02>

These are probably best read in reverse numerical order:
   definition
   requirements
   solution

I believe the author aimed to talk about this in a GROW meeting, or on
the GROW list, I have not seen him pipe up as of yet to that end,
however.

-chris

> SIDR attempted to look at route-leaks and came up a bit stymied, they
> asked IDR for some assistance with the issue, IDR pushed back to GROW
> to decide:
>   1) What is a 'route leak' (perhaps the above draft identifies one
> examplar to be used in that definition)
>   2) Are 'route leaks' a problem that Operations folks care about
>   3) Should IDR (or the IETF proper) address 'route leaks' with some
> form(s) of fix action.
>
> The end result of the above 3 steps is to push back into IDR one of
> two action requests:
>   1) "Yes, route leaks are a problem, please fix them."
>      or
>   2) "No, route leaks are not a problem, take no action."
>
> If #1 above is the answer, and IDR decides that changes to the BGP
> protocol are warranted (or are a possible solution to the problem)
> then SIDR has agreed to do what they can to 'secure' the bits
> added/changed/used in that endeavor.
>
> Could we have some discussion on-list about this problem, and some
> discussion about whether or not the draft referenced above fits the
> definition we would like to use for 'route leak'? I would also like
> the authors of the draft to decide where they would like to take their
> draft:
>    1) SIDR
>    2) IDR
>    3) GROW
>    4) other
>
> Thanks!
> -Chris
> (co-chair 1:2 of grow, and 1:3 in sidr)

From jared@puck.nether.net  Wed Nov 14 15:14:26 2012
Return-Path: <jared@puck.nether.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 5F50721F8792 for <grow@ietfa.amsl.com>; Wed, 14 Nov 2012 15:14:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.599
X-Spam-Level: 
X-Spam-Status: No, score=-1.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_BACKHAIR_43=1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tbuRGlyv61Xo for <grow@ietfa.amsl.com>; Wed, 14 Nov 2012 15:14:15 -0800 (PST)
Received: from puck.nether.net (puck.nether.net [IPv6:2001:418:3f4::5]) by ietfa.amsl.com (Postfix) with ESMTP id 8F45C21F87B6 for <grow@ietf.org>; Wed, 14 Nov 2012 15:14:15 -0800 (PST)
Received: from [10.170.96.57] (adsl-99-29-148-75.dsl.sfldmi.sbcglobal.net [99.29.148.75]) (authenticated bits=0) by puck.nether.net (8.14.4/8.14.4) with ESMTP id qAENE6sl007318 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 14 Nov 2012 18:14:09 -0500
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Content-Type: text/plain; charset=windows-1252
From: Jared Mauch <jared@puck.nether.net>
In-Reply-To: <CAL9jLaagY5bBe_8eRST8noEp2-o00Zkm2Qc59Ys7pak++EPGNw@mail.gmail.com>
Date: Wed, 14 Nov 2012 18:14:06 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <FAB1C764-3D17-4912-B2AF-E03E95A6B5BA@puck.nether.net>
References: <CAL9jLaagY5bBe_8eRST8noEp2-o00Zkm2Qc59Ys7pak++EPGNw@mail.gmail.com>
To: Christopher Morrow <christopher.morrow@gmail.com>
X-Mailer: Apple Mail (2.1499)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (puck.nether.net [204.42.254.5]); Wed, 14 Nov 2012 18:14:09 -0500 (EST)
Cc: "grow@ietf.org grow@ietf.org" <grow@ietf.org>, draft-foo-sidr-simple-leak-attack-bgpsec-no-help@tools.ietf.org, grow-ads@tools.ietf.org, grow-chairs@tools.ietf.org
Subject: Re: [GROW] RouteLeaks - problem or not?
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, 14 Nov 2012 23:14:26 -0000

On Nov 14, 2012, at 5:18 PM, Christopher Morrow =
<christopher.morrow@gmail.com> wrote:

>  1) What is a 'route leak' (perhaps the above draft identifies one
> examplar to be used in that definition)
>  2) Are 'route leaks' a problem that Operations folks care about

Side comment:

I fixed two problems in the tool in the past day or two.  It appears =
that 3561<->209 integration is happening and another was related to =
Comcast which has been corrected.

I certainly support the premise presented int his draft and that this is =
a significant issue.  The IETF network was subject to a problem like =
this for Atlanta=85

130.129.0.0/16	 3549 2828 10026 4538 4538 4538 4538 3320 7922 7725 =
56554=20

Not sure if you can still view the ticket, but It was here:=20

trac.meeting.ietf.org/ticket/536#comment:1

- Jared=

From danny@tcb.net  Wed Nov 14 15:37:14 2012
Return-Path: <danny@tcb.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 DE47721F85EB for <grow@ietfa.amsl.com>; Wed, 14 Nov 2012 15:37:14 -0800 (PST)
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=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c57XyN9EC1yo for <grow@ietfa.amsl.com>; Wed, 14 Nov 2012 15:37:14 -0800 (PST)
Received: from mail.friendswithtools.org (unknown [IPv6:2600:3000:150f:701:5054:ff:fed1:24a9]) by ietfa.amsl.com (Postfix) with ESMTP id 83AD421F84EC for <grow@ietf.org>; Wed, 14 Nov 2012 15:37:12 -0800 (PST)
Received: from dspam (unknown [127.0.0.1]) by mail.friendswithtools.org (Postfix) with SMTP id DC43C2148 for <grow@ietf.org>; Wed, 14 Nov 2012 23:37:11 +0000 (UTC)
Received: from [10.196.208.46] (unknown [209.133.29.54]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mail.friendswithtools.org (Postfix) with ESMTPSA id 6B1492136; Wed, 14 Nov 2012 16:37:08 -0700 (MST)
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=us-ascii
From: Danny McPherson <danny@tcb.net>
In-Reply-To: <CAL9jLabt0S98HEygsQp=a98ARwiRxJ2x3F2=H5w-pDRbyqWE7A@mail.gmail.com>
Date: Wed, 14 Nov 2012 18:37:10 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <9C6661E5-D760-44C4-A4EA-ACFB531FA33C@tcb.net>
References: <CAL9jLabt0S98HEygsQp=a98ARwiRxJ2x3F2=H5w-pDRbyqWE7A@mail.gmail.com>
To: Christopher Morrow <christopher.morrow@gmail.com>
X-Mailer: Apple Mail (2.1283)
X-DSPAM-Result: Innocent
X-DSPAM-Processed: Wed Nov 14 16:37:11 2012
X-DSPAM-Confidence: 1.0000
X-DSPAM-Improbability: 1 in 98689409 chance of being spam
X-DSPAM-Probability: 0.0023
X-DSPAM-Signature: 50a42b27199631278919350
X-DSPAM-Factors: 27, 28+#+to, 0.40000, like+#+#+#+published, 0.40000, with+#+#+inform, 0.40000, what+the, 0.40000, not+#+#+start, 0.40000, it+#+#+improvements, 0.40000, whether+#+enabled, 0.40000, PM+#+#+#+Grow, 0.40000, considering+#+#+issues, 0.40000, what+#+#+are, 0.40000, discussion+#+#+of, 0.40000, Additionally+#+provides, 0.40000, global+routing, 0.40000, that+are, 0.40000, irr+#+policy, 0.40000, Subject*Adoption+#+draft-mcpherson-irr-routing-policy-considerations, 0.40000, to+#+the, 0.40000, in+#+#+#+system, 0.40000, still+#+in, 0.40000, a+#+#+which, 0.40000, IRR+#+#+this, 0.40000, days+#+#+28, 0.40000, Thanks!+#+#+chair, 0.40000, danny+#+Nov, 0.40000, it+#+inform, 0.40000, 5+#+#+Christopher, 0.40000, Url*01, 0.40000
Cc: "grow@ietf.org grow@ietf.org" <grow@ietf.org>, draft-mcpherson-irr-routing-policy-considerations@tools.ietf.org, grow-ads@tools.ietf.org, grow-chairs@tools.ietf.org
Subject: Re: [GROW] WG Adoption call: draft-mcpherson-irr-routing-policy-considerations (END: 11/28/2012)
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, 14 Nov 2012 23:37:15 -0000

Authors would definitely like to see this published, and GROW seems like =
a reasonable home.

Given that we need to fix the IRRs whether RPKI-enabled BGPSEC is fully =
deployed or not, we should start considering what the issues are with it =
to inform improvements or recommend replacements.

Comments welcome...

-danny


On Nov 14, 2012, at 5:35 PM, Christopher Morrow wrote:

> Grow Folks,
> the authors of:  draft-mcpherson-irr-routing-policy-considerations
>  =
<http://tools.ietf.org/html/draft-mcpherson-irr-routing-policy-considerati=
ons-01>
>=20
> have asked if their work is appropriate for the GROW-wg, could we take
> the next 14 days (ending Nov 28, 2012) to think/discuss this draft and
> it's efficacy to work in the GROW arena? The abstract of the draft is:
>  "The purpose of this document is to catalog past issues influencing
>   the efficacy of Internet Routing Registries (IRR) for inter-domain
>   routing policy specification and application in the global routing
>   system over the past two decades.  Additionally, it provides a
>   discussion regarding which of these issues are still problematic in
>   practice, and which are simply artifacts that are no longer
>   applicable but continue to stifle inter-provider policy-based
>   filtering adoption and IRR utility to this day."
>=20
> Thanks!
> -Chris
> (co-chair)
> _______________________________________________
> GROW mailing list
> GROW@ietf.org
> https://www.ietf.org/mailman/listinfo/grow
>=20



From dmcpherson@verisign.com  Wed Nov 14 15:34:19 2012
Return-Path: <dmcpherson@verisign.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 A425E21F85CD for <grow@ietfa.amsl.com>; Wed, 14 Nov 2012 15:34:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 54E6kWDSU8jX for <grow@ietfa.amsl.com>; Wed, 14 Nov 2012 15:34:19 -0800 (PST)
Received: from exprod6og112.obsmtp.com (exprod6og112.obsmtp.com [64.18.1.29]) by ietfa.amsl.com (Postfix) with ESMTP id 6677A21F8595 for <grow@ietf.org>; Wed, 14 Nov 2012 15:34:16 -0800 (PST)
Received: from osprey.verisign.com ([216.168.239.75]) (using TLSv1) by exprod6ob112.postini.com ([64.18.5.12]) with SMTP ID DSNKUKQqcYozn4fN8THXCnlY6tuh6y30Tp2D@postini.com; Wed, 14 Nov 2012 15:34:19 PST
Received: from BRN1WNEXCHM01.vcorp.ad.vrsn.com (brn1wnexchm01.vcorp.ad.vrsn.com [10.173.152.255]) by osprey.verisign.com (8.13.6/8.13.4) with ESMTP id qAENY4gI029045 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 14 Nov 2012 18:34:04 -0500
Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by BRN1WNEXCHM01.vcorp.ad.vrsn.com ([::1]) with mapi id 14.02.0318.004; Wed, 14 Nov 2012 18:34:04 -0500
From: "McPherson, Danny" <dmcpherson@verisign.com>
To: Jared Mauch <jared@puck.nether.net>, Christopher Morrow <christopher.morrow@gmail.com>
Thread-Topic: [GROW] RouteLeaks - problem or not?
Thread-Index: AQHNwrX7bkitRj8lhEC3YPT+N4KompfqSeIAgAAFlAA=
Date: Wed, 14 Nov 2012 23:34:03 +0000
Message-ID: <49E321F57E514F40989268678089C60C0F890C81@BRN1WNEXMBX01.vcorp.ad.vrsn.com>
References: <CAL9jLaagY5bBe_8eRST8noEp2-o00Zkm2Qc59Ys7pak++EPGNw@mail.gmail.com> <FAB1C764-3D17-4912-B2AF-E03E95A6B5BA@puck.nether.net>
In-Reply-To: <FAB1C764-3D17-4912-B2AF-E03E95A6B5BA@puck.nether.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.173.152.4]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <4D2B4A708694624D837EA783C620A2B4@verisign.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Wed, 14 Nov 2012 15:46:05 -0800
Cc: "grow@ietf.org grow@ietf.org" <grow@ietf.org>, "draft-foo-sidr-simple-leak-attack-bgpsec-no-help@tools.ietf.org" <draft-foo-sidr-simple-leak-attack-bgpsec-no-help@tools.ietf.org>, "<grow-ads@tools.ietf.org>" <grow-ads@tools.ietf.org>, "<grow-chairs@tools.ietf.org>" <grow-chairs@tools.ietf.org>
Subject: Re: [GROW] RouteLeaks - problem or not?
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, 14 Nov 2012 23:34:19 -0000

On Nov 14, 2012, at 6:14 PM, Jared Mauch wrote:
>=20
> I certainly support the premise presented int his draft and that this is =
a significant issue.=20

In addition to Jared, Shane, Eric and I, other folks said route leaks are a=
 problem as well on SIDR.  I'll provide full fragment for context below, an=
d they can chime in if they so choose...

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Begin forwarded message:

> From: Christopher Morrow <morrowc.lists@gmail.com>
> Subject: Re: [sidr] The need for SIDR - Google limited outage today due t=
o bogus route announcement
> Date: November 7, 2012 3:56:33 PM EST
> To: Danny McPherson <danny@tcb.net>
> Cc: "sidr@ietf.org list" <sidr@ietf.org>
>=20
> On Wed, Nov 7, 2012 at 2:06 PM, Danny McPherson <danny@tcb.net> wrote:
>>=20
>> On Nov 7, 2012, at 1:48 PM, Christopher Morrow wrote:
>>=20
>>> 1) show/agree that this is a problem (route leaks)
>>=20
>> Do you believe this is a problem?  When describing events such as this a=
s
>> of late, what did you call it?
>=20
> sure, but I'm not the grow-wg ... right? aim that question over ->
> <mailto: grow@ietf.org> there.

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

Begin forwarded message:

> From: Randy Bush <randy@psg.com>
> Subject: Re: [sidr] The need for SIDR - Google limited outage today due t=
o bogus route announcement
> Date: November 7, 2012 10:22:16 PM EST
> To: Christopher Morrow <morrowc.lists@gmail.com>
> Cc: sidr wg list <sidr@ietf.org>
>=20
> <pedantry>
>=20
>> "'Route leaks" are viewed as a routing security problem..."
>=20
> route leaks, as we anecdotally know them, are an operational problem.
> imiho, they are not particularly a security problem.  but that does not
> mean i think the ietf routing community should not be working on a
> solution, quite the opposite.
>=20
> randy


=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D


From nick@inex.ie  Wed Nov 14 15:53:08 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 6C69421F8660 for <grow@ietfa.amsl.com>; Wed, 14 Nov 2012 15:53:04 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jB1KxRm0uqi4 for <grow@ietfa.amsl.com>; Wed, 14 Nov 2012 15:53:03 -0800 (PST)
Received: from mail.acquirer.com (mail.acquirer.com [IPv6:2a03:8900:0:100::5]) by ietfa.amsl.com (Postfix) with ESMTP id 8625421F85EB for <grow@ietf.org>; Wed, 14 Nov 2012 15:53:02 -0800 (PST)
X-Envelope-To: grow@ietf.org
Received: from cupcake.foobar.org ([IPv6:2001:4d68:2002:100:3187:b074:bdb2:306a]) (authenticated bits=0) by mail.acquirer.com (8.14.4/8.14.4) with ESMTP id qAENpn1A098808 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Wed, 14 Nov 2012 23:51:54 GMT (envelope-from nick@inex.ie)
Message-ID: <50A42ED5.2060803@inex.ie>
Date: Wed, 14 Nov 2012 23:52:53 +0000
From: Nick Hilliard <nick@inex.ie>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: Christopher Morrow <christopher.morrow@gmail.com>
References: <CAL9jLaagY5bBe_8eRST8noEp2-o00Zkm2Qc59Ys7pak++EPGNw@mail.gmail.com>
In-Reply-To: <CAL9jLaagY5bBe_8eRST8noEp2-o00Zkm2Qc59Ys7pak++EPGNw@mail.gmail.com>
X-Enigmail-Version: 1.4.6
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@ietf.org>, draft-foo-sidr-simple-leak-attack-bgpsec-no-help@tools.ietf.org, grow-ads@tools.ietf.org, grow-chairs@tools.ietf.org
Subject: Re: [GROW] RouteLeaks - problem or not?
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, 14 Nov 2012 23:53:08 -0000

On 14/11/2012 22:18, Christopher Morrow wrote:
>   1) What is a 'route leak' (perhaps the above draft identifies one
> examplar to be used in that definition)

dunno really.  Some foo which involves prefixes being sent to places where
they oughtn't have been sent to.  This is possibly more of a legal /
wordsmithing problem than anything else.

>   2) Are 'route leaks' a problem that Operations folks care about

speaking with my IXP operator hat on, hell yeah.  INEX operates a route
server cluster which provides service to ~70% of our members.  If we were
to operate an unprotected system and had a prefix leak from a client, it
would destroy confidence in the system and people would depeer.
Connectivity would be directly harmed.  In my experience, it takes very
little for people to lose trust in a system like this.

We use strict prefix filtering based on IRRDB data with a vengeance, but
ended up also having to implement maxprefixes after someone attached the
INEX route server as-set macro to their own as set macro (mistake #1), then
announced all the prefixes they received back to INEX (mistake #2).  As it
happened, their prefixes were depreferred because of the asn path length,
but if they hadn't been depreferred, it could have taken down the entire
system.  Ouch.

Anyway, point being: yes: route leaks matter, yes: at least some operations
people care, and belt + braces is sensible.

>   3) Should IDR (or the IETF proper) address 'route leaks' with some
> form(s) of fix action.

mmmm, difficult one.

So the current thinking seems to be heading in the direction of RPKI which
has a lot of interesting technical characteristics, probably the most
interesting of which is the max prefix length.  One interesting
characteristic of RPKI is that in order for it to have any real function on
a live network, it will be necessary to completely drop rpki-invalid
prefixes.  Merely depreferring them is a bit useless.

Problem is, the current implementations of rpki only deal with origin
validation, and not as path validation.  Work on this has begun in terms of
a list of specifications (draft-ietf-sidr-bgpsec-reqs), but hasn't
progressed much beyond that as far as I can tell.  I wonder if some of the
sine-qua-nons in this document are mutually exclusive.

RPKI will only be fully functional from the point of view of preventing
leaks (whatever leaks are) when we have full as path validation.

Being honest, RPKI concerns me from two points of view.  From a technical
point of view, BGP is a fully distributed system which forms the basis of
global network reachability, yet RPKI seeks to impose a top-down control /
validation mechanism for it, albeit based on many potential roots.  I
cannot seem to stop being concerned that this is an architecturally bad
idea from a technical point of view, even though there are many safeguards,
including:

- recommendations for using local caches
- lazy validation
- recommendations for validation only at ASN boundaries
- recommendations in draft-ietf-sidr-origin-ops

... even still, there is a double architectural inversion going on here,
where a full-distributed, very low level protocol is being made to depend
on a top-down, much higher level protocol.

>From a non-technical point of view I also have serious concerns about RPKI
in terms of it being used as a hammer that politicians / bureaucrats / LEAs
/ judges / etc are (and that's "are" as in present tense) extremely
interested in as a potential future means of blocking content / services
which they happen not to like.  Although GROW is not the place for this
particular discussion, this aspect of RPKI concerns me to the extent that I
am disturbed about the wisdom of developing the technology in the first
place:  we're building an on/off button for prefixes throughout the
Internet.  We need to be careful what we wish for because one day, we might
get it.

Nick


From jared@puck.nether.net  Wed Nov 14 15:57:16 2012
Return-Path: <jared@puck.nether.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 38B3021F8660 for <grow@ietfa.amsl.com>; Wed, 14 Nov 2012 15:57:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[AWL=0.500,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LA6PP1b9l8eQ for <grow@ietfa.amsl.com>; Wed, 14 Nov 2012 15:57:15 -0800 (PST)
Received: from puck.nether.net (puck.nether.net [IPv6:2001:418:3f4::5]) by ietfa.amsl.com (Postfix) with ESMTP id BC85921F85DF for <grow@ietf.org>; Wed, 14 Nov 2012 15:57:15 -0800 (PST)
Received: from [10.170.96.57] (adsl-99-29-148-75.dsl.sfldmi.sbcglobal.net [99.29.148.75]) (authenticated bits=0) by puck.nether.net (8.14.4/8.14.4) with ESMTP id qAENv7qG012807 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 14 Nov 2012 18:57:09 -0500
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Content-Type: text/plain; charset=us-ascii
From: Jared Mauch <jared@puck.nether.net>
In-Reply-To: <50A42ED5.2060803@inex.ie>
Date: Wed, 14 Nov 2012 18:57:07 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <06206752-A09E-4F37-B1A9-25B8DB3CCFB9@puck.nether.net>
References: <CAL9jLaagY5bBe_8eRST8noEp2-o00Zkm2Qc59Ys7pak++EPGNw@mail.gmail.com> <50A42ED5.2060803@inex.ie>
To: Nick Hilliard <nick@inex.ie>
X-Mailer: Apple Mail (2.1499)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (puck.nether.net [204.42.254.5]); Wed, 14 Nov 2012 18:57:10 -0500 (EST)
Cc: grow-chairs@tools.ietf.org, "grow@ietf.org" <grow@ietf.org>, draft-foo-sidr-simple-leak-attack-bgpsec-no-help@tools.ietf.org, grow-ads@tools.ietf.org
Subject: Re: [GROW] RouteLeaks - problem or not?
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, 14 Nov 2012 23:57:16 -0000

On Nov 14, 2012, at 6:52 PM, Nick Hilliard <nick@inex.ie> wrote:

> On 14/11/2012 22:18, Christopher Morrow wrote:
>>  1) What is a 'route leak' (perhaps the above draft identifies one
>> examplar to be used in that definition)
>=20
> dunno really.  Some foo which involves prefixes being sent to places =
where
> they oughtn't have been sent to.  This is possibly more of a legal /
> wordsmithing problem than anything else.

I would say unexpected paths that appear as a result of poorly =
constructed routing policies or software defaults and lax filtering =
policies.

My "leak info" tool does fuzz detection and find a lot of these things =
all day long.

- Jared=

From christopher.morrow@gmail.com  Wed Nov 14 16:02:19 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 6561B21F85A5 for <grow@ietfa.amsl.com>; Wed, 14 Nov 2012 16:02:19 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pCb76i0gLfD5 for <grow@ietfa.amsl.com>; Wed, 14 Nov 2012 16:02:18 -0800 (PST)
Received: from mail-ea0-f172.google.com (mail-ea0-f172.google.com [209.85.215.172]) by ietfa.amsl.com (Postfix) with ESMTP id 9ECC421F853F for <grow@ietf.org>; Wed, 14 Nov 2012 16:02:18 -0800 (PST)
Received: by mail-ea0-f172.google.com with SMTP id k13so485163eaa.31 for <grow@ietf.org>; Wed, 14 Nov 2012 16:02:17 -0800 (PST)
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; bh=tAdTKjFa1Qob/Vg5EJWic+SBsTka2fKXYW8wfnnjUgg=; b=qCdrKINUkf9zQJrNcQbxyt7jiYb96XiOogB6pbY5aCJ4j9pys/3yWoASwU4/wBED4t zHgiWXVrhim7VoBViAzUK3Ex1hj6yI+yOLW8XOu/5jzlIBUMpJB30OvjR+t7vyS9RNoC JOWkrzk5RTwXKMupA2Rh4CdBvvozLUEPriwNZ9C2iJKuPYL0Ntzn/zy1TO0I14NM7oeg sEOhBeoTgf7Qxa8XwEwEvZ2uEZFdMrYsTRPH8bgBXVz7swU04Wna8NC+ZwDSjmuDdiHO 0cVqfjTa8jPZVUqfooflpF1+7PYDprFSeAAykpj9nM/R/EkLsRxT3MPwfFiIF1gnQEvl 9A4A==
MIME-Version: 1.0
Received: by 10.14.194.72 with SMTP id l48mr92898482een.9.1352937737839; Wed, 14 Nov 2012 16:02:17 -0800 (PST)
Received: by 10.223.177.71 with HTTP; Wed, 14 Nov 2012 16:02:17 -0800 (PST)
In-Reply-To: <50A42ED5.2060803@inex.ie>
References: <CAL9jLaagY5bBe_8eRST8noEp2-o00Zkm2Qc59Ys7pak++EPGNw@mail.gmail.com> <50A42ED5.2060803@inex.ie>
Date: Wed, 14 Nov 2012 19:02:17 -0500
Message-ID: <CAL9jLaY+aogBBj1K0SGiuAL04CjcadQyaz5C0iDj94KOAMz9eQ@mail.gmail.com>
From: Christopher Morrow <christopher.morrow@gmail.com>
To: Nick Hilliard <nick@inex.ie>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "grow@ietf.org" <grow@ietf.org>, draft-foo-sidr-simple-leak-attack-bgpsec-no-help@tools.ietf.org, grow-ads@tools.ietf.org, grow-chairs@tools.ietf.org
Subject: Re: [GROW] RouteLeaks - problem or not?
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, 15 Nov 2012 00:02:19 -0000

On Wed, Nov 14, 2012 at 6:52 PM, Nick Hilliard <nick@inex.ie> wrote:
> Problem is, the current implementations of rpki only deal with origin
> validation, and not as path validation.

one clarifying point, the RPKI doesn't actually say anything at all
about 'path' data. I merely says which origin-as(es) should be able to
announce a prefix.

From nick@inex.ie  Wed Nov 14 16:12:41 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 6687E21F8705 for <grow@ietfa.amsl.com>; Wed, 14 Nov 2012 16:12:41 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aSmb9edvfK5S for <grow@ietfa.amsl.com>; Wed, 14 Nov 2012 16:12:41 -0800 (PST)
Received: from mail.acquirer.com (mail.acquirer.com [IPv6:2a03:8900:0:100::5]) by ietfa.amsl.com (Postfix) with ESMTP id B123E21F86E9 for <grow@ietf.org>; Wed, 14 Nov 2012 16:12:39 -0800 (PST)
X-Envelope-To: grow@ietf.org
Received: from cupcake.foobar.org ([IPv6:2001:4d68:2002:100:3187:b074:bdb2:306a]) (authenticated bits=0) by mail.acquirer.com (8.14.4/8.14.4) with ESMTP id qAF0BQaX098965 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Thu, 15 Nov 2012 00:11:32 GMT (envelope-from nick@inex.ie)
Message-ID: <50A4336F.2020102@inex.ie>
Date: Thu, 15 Nov 2012 00:12:31 +0000
From: Nick Hilliard <nick@inex.ie>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: Christopher Morrow <christopher.morrow@gmail.com>
References: <CAL9jLaagY5bBe_8eRST8noEp2-o00Zkm2Qc59Ys7pak++EPGNw@mail.gmail.com> <50A42ED5.2060803@inex.ie> <CAL9jLaY+aogBBj1K0SGiuAL04CjcadQyaz5C0iDj94KOAMz9eQ@mail.gmail.com>
In-Reply-To: <CAL9jLaY+aogBBj1K0SGiuAL04CjcadQyaz5C0iDj94KOAMz9eQ@mail.gmail.com>
X-Enigmail-Version: 1.4.6
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@ietf.org>, draft-foo-sidr-simple-leak-attack-bgpsec-no-help@tools.ietf.org, grow-ads@tools.ietf.org, grow-chairs@tools.ietf.org
Subject: Re: [GROW] RouteLeaks - problem or not?
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, 15 Nov 2012 00:12:41 -0000

On 15/11/2012 00:02, Christopher Morrow wrote:
> one clarifying point, the RPKI doesn't actually say anything at all
> about 'path' data. I merely says which origin-as(es) should be able to
> announce a prefix.

i'm being slack about my usage of the term rpki here, and should have
referred to bgpsec instead.

Nick


From aservin@lacnic.net  Wed Nov 14 16:38:05 2012
Return-Path: <aservin@lacnic.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 01DBD21F8777 for <grow@ietfa.amsl.com>; Wed, 14 Nov 2012 16:38:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.602
X-Spam-Level: 
X-Spam-Status: No, score=-1.602 tagged_above=-999 required=5 tests=[AWL=0.998,  BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uP0FnWds4KHO for <grow@ietfa.amsl.com>; Wed, 14 Nov 2012 16:38:04 -0800 (PST)
Received: from mail.lacnic.net.uy (mail.lacnic.net.uy [IPv6:2001:13c7:7001:4000::3]) by ietfa.amsl.com (Postfix) with ESMTP id 6D0C521F86E4 for <grow@ietf.org>; Wed, 14 Nov 2012 16:38:04 -0800 (PST)
Received: from [IPv6:2800:af:ba30:fc38:e451:718e:d470:1cae] (unknown [IPv6:2800:af:ba30:fc38:e451:718e:d470:1cae]) by mail.lacnic.net.uy (Postfix) with ESMTP id BABF8308436 for <grow@ietf.org>; Wed, 14 Nov 2012 22:38:04 -0200 (UYST)
Message-ID: <50A4396A.1050109@lacnic.net>
Date: Wed, 14 Nov 2012 22:38:02 -0200
From: Arturo Servin <aservin@lacnic.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: grow@ietf.org
References: <CAL9jLaagY5bBe_8eRST8noEp2-o00Zkm2Qc59Ys7pak++EPGNw@mail.gmail.com> <50A42ED5.2060803@inex.ie>
In-Reply-To: <50A42ED5.2060803@inex.ie>
X-Enigmail-Version: 1.4.5
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-LACNIC.uy-MailScanner-Information: Please contact the ISP for more information
X-LACNIC.uy-MailScanner: Found to be clean
X-LACNIC.uy-MailScanner-SpamCheck: 
X-LACNIC.uy-MailScanner-From: aservin@lacnic.net
Subject: Re: [GROW] RouteLeaks - problem or not?
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, 15 Nov 2012 00:38:05 -0000

Nick,

	Perhaps this is not the place, but ...

	I am still finding these arguments about RPKI as a bunch of fud (please
do not take it personally). I think that are much easier, cheap and
practical methods (or hammers) that would accomplish the same goal. In
fact, any entity trying to use RPKI as a hammer I would say that it is
very badly advised (to said the least).

Regards,
as



<snip>
On 14/11/2012 21:52, Nick Hilliard wrote:
>>From a non-technical point of view I also have serious concerns about RPKI
> in terms of it being used as a hammer that politicians / bureaucrats / LEAs
> / judges / etc are (and that's "are" as in present tense) extremely
> interested in as a potential future means of blocking content / services
> which they happen not to like.  Although GROW is not the place for this
> particular discussion, this aspect of RPKI concerns me to the extent that I
> am disturbed about the wisdom of developing the technology in the first
> place:  we're building an on/off button for prefixes throughout the
> Internet.  We need to be careful what we wish for because one day, we might
> get it.

From nick@inex.ie  Wed Nov 14 16:47:02 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 6E15621F8792 for <grow@ietfa.amsl.com>; Wed, 14 Nov 2012 16:47:02 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zhRT6VFuvGik for <grow@ietfa.amsl.com>; Wed, 14 Nov 2012 16:47:02 -0800 (PST)
Received: from mail.acquirer.com (mail.acquirer.com [IPv6:2a03:8900:0:100::5]) by ietfa.amsl.com (Postfix) with ESMTP id A651021F85D1 for <grow@ietf.org>; Wed, 14 Nov 2012 16:47:01 -0800 (PST)
X-Envelope-To: <grow@ietf.org>
Received: from cupcake.foobar.org ([IPv6:2001:4d68:2002:100:3187:b074:bdb2:306a]) (authenticated bits=0) by mail.acquirer.com (8.14.4/8.14.4) with ESMTP id qAF0joH9099123 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <grow@ietf.org>; Thu, 15 Nov 2012 00:45:55 GMT (envelope-from nick@inex.ie)
Message-ID: <50A43B7E.2000909@inex.ie>
Date: Thu, 15 Nov 2012 00:46:54 +0000
From: Nick Hilliard <nick@inex.ie>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: grow@ietf.org
References: <CAL9jLaagY5bBe_8eRST8noEp2-o00Zkm2Qc59Ys7pak++EPGNw@mail.gmail.com> <50A42ED5.2060803@inex.ie> <50A4396A.1050109@lacnic.net>
In-Reply-To: <50A4396A.1050109@lacnic.net>
X-Enigmail-Version: 1.4.6
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
Subject: Re: [GROW] RouteLeaks - problem or not?
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, 15 Nov 2012 00:47:02 -0000

On 15/11/2012 00:38, Arturo Servin wrote:
> Nick,
> 
> 	Perhaps this is not the place, but ...

It probably isn't.  Let's discuss the technical issues.

Nick

> 	I am still finding these arguments about RPKI as a bunch of fud (please
> do not take it personally). I think that are much easier, cheap and
> practical methods (or hammers) that would accomplish the same goal. In
> fact, any entity trying to use RPKI as a hammer I would say that it is
> very badly advised (to said the least).
> 
> Regards,
> as
> 
> 
> 
> <snip>
> On 14/11/2012 21:52, Nick Hilliard wrote:
>> >From a non-technical point of view I also have serious concerns about RPKI
>> in terms of it being used as a hammer that politicians / bureaucrats / LEAs
>> / judges / etc are (and that's "are" as in present tense) extremely
>> interested in as a potential future means of blocking content / services
>> which they happen not to like.  Although GROW is not the place for this
>> particular discussion, this aspect of RPKI concerns me to the extent that I
>> am disturbed about the wisdom of developing the technology in the first
>> place:  we're building an on/off button for prefixes throughout the
>> Internet.  We need to be careful what we wish for because one day, we might
>> get it.
> _______________________________________________
> GROW mailing list
> GROW@ietf.org
> https://www.ietf.org/mailman/listinfo/grow
> 


-- 
Network Ability Ltd. | Chief Technical Officer | Tel: +353 1 6169698
3 Westland Square    | INEX - Internet Neutral | Fax: +353 1 6041981
Dublin 2, Ireland    | Exchange Association    | Email: nick@inex.ie

From aservin@lacnic.net  Wed Nov 14 17:08:21 2012
Return-Path: <aservin@lacnic.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 C105721E8030 for <grow@ietfa.amsl.com>; Wed, 14 Nov 2012 17:08:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.101
X-Spam-Level: 
X-Spam-Status: No, score=-2.101 tagged_above=-999 required=5 tests=[AWL=0.499,  BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Pb2iy9hEbi8s for <grow@ietfa.amsl.com>; Wed, 14 Nov 2012 17:08:20 -0800 (PST)
Received: from mail.lacnic.net.uy (mail.lacnic.net.uy [IPv6:2001:13c7:7001:4000::3]) by ietfa.amsl.com (Postfix) with ESMTP id B2CCC21E802E for <grow@ietf.org>; Wed, 14 Nov 2012 17:08:19 -0800 (PST)
Received: from [IPv6:2800:af:ba30:fc38:e451:718e:d470:1cae] (unknown [IPv6:2800:af:ba30:fc38:e451:718e:d470:1cae]) by mail.lacnic.net.uy (Postfix) with ESMTP id 39942308444 for <grow@ietf.org>; Wed, 14 Nov 2012 23:08:18 -0200 (UYST)
Message-ID: <50A44080.8020704@lacnic.net>
Date: Wed, 14 Nov 2012 23:08:16 -0200
From: Arturo Servin <aservin@lacnic.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: grow@ietf.org
References: <CAL9jLaagY5bBe_8eRST8noEp2-o00Zkm2Qc59Ys7pak++EPGNw@mail.gmail.com> <CAL9jLaZT43OBwHqWs-xzy8qCm1UEyfN+hDKTgdrrvCc09xWNHw@mail.gmail.com>
In-Reply-To: <CAL9jLaZT43OBwHqWs-xzy8qCm1UEyfN+hDKTgdrrvCc09xWNHw@mail.gmail.com>
X-Enigmail-Version: 1.4.5
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-LACNIC.uy-MailScanner-Information: Please contact the ISP for more information
X-LACNIC.uy-MailScanner: Found to be clean
X-LACNIC.uy-MailScanner-SpamCheck: 
X-LACNIC.uy-MailScanner-From: aservin@lacnic.net
Subject: Re: [GROW] RouteLeaks - problem or not?
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, 15 Nov 2012 01:08:21 -0000

Chris,

	I think that draft-foo-sidr-simple-leak-attack-bgpsec-no-help-02 shows
very well why rpki-origin-validation and bgpsec are vulerable to route
leaks. Also it has a good and simple example of a route leak. One
drawback that I see is that it does not explain the problem in general,
the document is focused on route leaks as result of
Man-in-the-middle-attack. Recent events relating leaks showed us that an
attack it is not necessary, just some fat fingers in the right place and
you are done.

	draft-dickson-sidr-route-leak-def-03 is more general, it tries to
explain route leaks as an event and not as an attack. However the level
of granularity and detail makes the document and the concept of leak
hard to understand (perhaps it is because English is not my first
language) and I found the simpler example in
draft-foo-sidr-simple-leak-attack-bgpsec-no-help-02 much easier to follow.

	The other two documents (draft-dickson-sidr-route-leak-solns-01 and
draft-dickson-sidr-route-leak-reqts-02) are about solutions and
requirements of a solution. I think for now are beyond us. First I would
prefer to define very well a route leak and then finding a solution.

	In my opinion some merging or re-writting of
draft-foo-sidr-simple-leak-attack-bgpsec-no-help-02 and
draft-dickson-sidr-route-leak-def-03 could result in a good explanation
of leaks and why they are a problem. However, what ever were the next
step, I would suggest to keep
draft-foo-sidr-simple-leak-attack-bgpsec-no-help-02 or some sort of it
because it may be useful in the future (or now) to describe the
limitations of rpki-origin-validation and bgpsec.
	
	And finally, I would prefer (now that sidr and idr have stepped out to)
to work on the definition of the route-leak problem here. After defined,
we could move it either to sidr or idr (although I think both have a
said on the possible solution).

my 20 cents,
as


On 14/11/2012 20:44, Christopher Morrow wrote:
> Apologies for the extra spam, there was a topic point I missed in this
> mail, see below please.
> 
> On Wed, Nov 14, 2012 at 5:18 PM, Christopher Morrow
> <christopher.morrow@gmail.com> wrote:
>> GROW Folks,
>> The SIDR working group is working on security for origination and path
>> data related to BGP routes. There has been a note (a few) about SIDR's
>> effect(s) or not on 'route leaks'. There have even been a few notes on
>> 'what is a route leak'. To date there is a draft which discusses route
>> leaks:
>>   <http://tools.ietf.org/html/draft-foo-sidr-simple-leak-attack-bgpsec-no-help-02>
>>
>> where the authors have attempted to describe one (or many possible)
>> situations which are called 'route leaks'. They also attempt to
>> outline security issues which are follow-on effects of the situation
>> described.
>>
> 
> Additionally there were several drafts written by Brian Dickson aiming
> to provide some definitions about route-leaks and some direction for a
> solution, they are:
>   <http://tools.ietf.org/html/draft-dickson-sidr-route-leak-def-03>
>   <http://tools.ietf.org/html/draft-dickson-sidr-route-leak-solns-01>
>   <http://tools.ietf.org/html/draft-dickson-sidr-route-leak-reqts-02>
> 
> These are probably best read in reverse numerical order:
>    definition
>    requirements
>    solution
> 
> I believe the author aimed to talk about this in a GROW meeting, or on
> the GROW list, I have not seen him pipe up as of yet to that end,
> however.
> 
> -chris
> 
>> SIDR attempted to look at route-leaks and came up a bit stymied, they
>> asked IDR for some assistance with the issue, IDR pushed back to GROW
>> to decide:
>>   1) What is a 'route leak' (perhaps the above draft identifies one
>> examplar to be used in that definition)
>>   2) Are 'route leaks' a problem that Operations folks care about
>>   3) Should IDR (or the IETF proper) address 'route leaks' with some
>> form(s) of fix action.
>>
>> The end result of the above 3 steps is to push back into IDR one of
>> two action requests:
>>   1) "Yes, route leaks are a problem, please fix them."
>>      or
>>   2) "No, route leaks are not a problem, take no action."
>>
>> If #1 above is the answer, and IDR decides that changes to the BGP
>> protocol are warranted (or are a possible solution to the problem)
>> then SIDR has agreed to do what they can to 'secure' the bits
>> added/changed/used in that endeavor.
>>
>> Could we have some discussion on-list about this problem, and some
>> discussion about whether or not the draft referenced above fits the
>> definition we would like to use for 'route leak'? I would also like
>> the authors of the draft to decide where they would like to take their
>> draft:
>>    1) SIDR
>>    2) IDR
>>    3) GROW
>>    4) other
>>
>> Thanks!
>> -Chris
>> (co-chair 1:2 of grow, and 1:3 in sidr)
> _______________________________________________
> GROW mailing list
> GROW@ietf.org
> https://www.ietf.org/mailman/listinfo/grow
> 

From shane@castlepoint.net  Wed Nov 14 20:33:37 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 BC89421F853A for <grow@ietfa.amsl.com>; Wed, 14 Nov 2012 20:33:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.25
X-Spam-Level: 
X-Spam-Status: No, score=-0.25 tagged_above=-999 required=5 tests=[AWL=0.187,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611,  RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sS7UM341sefL for <grow@ietfa.amsl.com>; Wed, 14 Nov 2012 20:33:37 -0800 (PST)
Received: from mail.friendswithtools.org (unknown [64.78.239.70]) by ietfa.amsl.com (Postfix) with ESMTP id 3584521F8522 for <grow@ietf.org>; Wed, 14 Nov 2012 20:33:37 -0800 (PST)
Received: from dspam (unknown [127.0.0.1]) by mail.friendswithtools.org (Postfix) with SMTP id 196242157 for <grow@ietf.org>; Thu, 15 Nov 2012 04:33:36 +0000 (UTC)
Received: from mbp.castlepoint.net (174-29-211-99.hlrn.qwest.net [174.29.211.99]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mail.friendswithtools.org (Postfix) with ESMTPSA id DA6942148; Wed, 14 Nov 2012 21:33:34 -0700 (MST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: Shane Amante <shane@castlepoint.net>
In-Reply-To: <CAL9jLaagY5bBe_8eRST8noEp2-o00Zkm2Qc59Ys7pak++EPGNw@mail.gmail.com>
Date: Wed, 14 Nov 2012 21:33:33 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <C8308656-31A2-4475-85FD-0DF07734A8B1@castlepoint.net>
References: <CAL9jLaagY5bBe_8eRST8noEp2-o00Zkm2Qc59Ys7pak++EPGNw@mail.gmail.com>
To: Christopher Morrow <christopher.morrow@gmail.com>
X-Mailer: Apple Mail (2.1499)
X-DSPAM-Result: Innocent
X-DSPAM-Processed: Wed Nov 14 21:33:36 2012
X-DSPAM-Confidence: 1.0000
X-DSPAM-Improbability: 1 in 98689409 chance of being spam
X-DSPAM-Probability: 0.0023
X-DSPAM-Signature: 50a470a0199636703811353
X-DSPAM-Factors: 27, remain+#+minded, 0.40000, would+#+#+use, 0.40000, answer+#+a, 0.40000, what+happens, 0.40000, to+#+#+#+or, 0.40000, and+IDR, 0.40000, 3+#+4, 0.40000, they+#+#+to, 0.40000, situations+#+#+#+'route, 0.40000, and+came, 0.40000, came+#+a, 0.40000, presently+#+would, 0.40000, a+#+#+#+action, 0.40000, is+narrowly, 0.40000, I'd+like, 0.40000, T+#+like, 0.40000, 1+#+#+#+answer, 0.40000, leaks'+#+also, 0.40000, repeatedly+#+#+Internet, 0.40000, also+#+#+#+of, 0.40000, up+#+#+stymied, 0.40000, possible+#+which, 0.40000, is+#+#+leak', 0.40000, concerns+I've, 0.40000, refine+one, 0.40000, route+#+are, 0.40000, route+#+are, 0.40000
Cc: "grow@ietf.org grow@ietf.org" <grow@ietf.org>, draft-foo-sidr-simple-leak-attack-bgpsec-no-help@tools.ietf.org, grow-ads@tools.ietf.org, grow-chairs@tools.ietf.org
Subject: Re: [GROW] RouteLeaks - problem or not?
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, 15 Nov 2012 04:33:37 -0000

Chris,

See below.

On Nov 14, 2012, at 3:18 PM, Christopher Morrow =
<christopher.morrow@gmail.com> wrote:
[--snip--]
> To date there is a draft which discusses route leaks:
>  =
<http://tools.ietf.org/html/draft-foo-sidr-simple-leak-attack-bgpsec-no-he=
lp-02>
>=20
> where the authors have attempted to describe one (or many possible)
> situations which are called 'route leaks'. They also attempt to
> outline security issues which are follow-on effects of the situation
> described.
>=20
> SIDR attempted to look at route-leaks and came up a bit stymied, they
> asked IDR for some assistance with the issue, IDR pushed back to GROW
> to decide:
>  1) What is a 'route leak' (perhaps the above draft identifies one
> examplar to be used in that definition)

See aforementioned draft.  It's the most _concise_ definition of the =
problem, as observed repeatedly in the Internet.


>  2) Are 'route leaks' a problem that Operations folks care about

Yes!


>  3) Should IDR (or the IETF proper) address 'route leaks' with some
> form(s) of fix action.

WRT "Should IDR" ... that's like Henry Ford asking what color "Model T" =
I'd like, right?  Look, no offense to the folks in IDR :-), but as with =
every other WG their present charter is narrowly defined to =
'enhancements to BGP'.  I would hope that _when_the_time_comes_ we =
remain open-minded about conducting a thorough evaluation of the =
solution space, before deciding to further refine one, or more, of those =
solutions to a standard, or set of standards.  So, presently, I would =
not be in favor of exclusively asking IDR to fix 'route leaks', given =
the concerns I've raised above.

FWIW, I'm not clear on what you're proposing with "the IETF proper" ... =
so I can't say "yes" to that option either.


> The end result of the above 3 steps is to push back into IDR one of
> two action requests:
>  1) "Yes, route leaks are a problem, please fix them."
>     or
>  2) "No, route leaks are not a problem, take no action."
>=20
> If #1 above is the answer, and IDR decides that changes to the BGP
> protocol are warranted (or are a possible solution to the problem)
> then SIDR has agreed to do what they can to 'secure' the bits
> added/changed/used in that endeavor.

Dare I ask what happens if IDR decides they do not have an answer?


> Could we have some discussion on-list about this problem, and some
> discussion about whether or not the draft referenced above fits the
> definition we would like to use for 'route leak'?

Um, yes, but then again I'm a co-author, so clearly you should take this =
answer with a healthy dose of salt.  :-)


> I would also like
> the authors of the draft to decide where they would like to take their
> draft:
>   1) SIDR
>   2) IDR
>   3) GROW
>   4) other

IMO, since you're asking GROW, the answer should hopefully present =
itself.  :-) =20

-shane=


From christopher.morrow@gmail.com  Wed Nov 14 21:27:39 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 D25BF21E8053 for <grow@ietfa.amsl.com>; Wed, 14 Nov 2012 21:27:39 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 21p5KYNsWwYI for <grow@ietfa.amsl.com>; Wed, 14 Nov 2012 21:27:39 -0800 (PST)
Received: from mail-ee0-f44.google.com (mail-ee0-f44.google.com [74.125.83.44]) by ietfa.amsl.com (Postfix) with ESMTP id 09DC321E8051 for <grow@ietf.org>; Wed, 14 Nov 2012 21:27:38 -0800 (PST)
Received: by mail-ee0-f44.google.com with SMTP id b47so809857eek.31 for <grow@ietf.org>; Wed, 14 Nov 2012 21:27:38 -0800 (PST)
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=+U3ePsqrCLSSQj39jDnIi1UHPB8+F4ktwQkxKWQCu+0=; b=mkftemW5WH+NLfBvdEwZnRkJx6J5wG50wkHfxIxz4NbW4O3Qdfz9b30MQlr3XXsGWa yCQJdlTaAvK/K5QMErLWZi19KkQqqHEmLNO+byIn+27aZGDrNk0nIksq8cnDKblgpDot mMiklHmj8YQAly2H1hdVCCmaA7fHBRdwRfRk4VIQU8J4dJYQASaJXfhPYhDfN8RTUODW ppTaHNBkXBCGes+KSx20HPuyDw1J2I4kz2MPa2esR4ixhBw88gy7q8A9duoDthy3bZJn JOmdeQPipBNROiOTfcpismGZr2I2GbLStiJMQqXO0064G7GxIqxGvsfvMAidrqsV+dYZ +IKw==
MIME-Version: 1.0
Received: by 10.14.175.71 with SMTP id y47mr95005532eel.36.1352957257985; Wed, 14 Nov 2012 21:27:37 -0800 (PST)
Received: by 10.223.177.71 with HTTP; Wed, 14 Nov 2012 21:27:37 -0800 (PST)
In-Reply-To: <C8308656-31A2-4475-85FD-0DF07734A8B1@castlepoint.net>
References: <CAL9jLaagY5bBe_8eRST8noEp2-o00Zkm2Qc59Ys7pak++EPGNw@mail.gmail.com> <C8308656-31A2-4475-85FD-0DF07734A8B1@castlepoint.net>
Date: Thu, 15 Nov 2012 00:27:37 -0500
Message-ID: <CAL9jLabgy7f5ZkaqfGGaHkRodLfpWP=8yNcTm-4xFTgjtFVsiA@mail.gmail.com>
From: Christopher Morrow <christopher.morrow@gmail.com>
To: Shane Amante <shane@castlepoint.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "grow@ietf.org grow@ietf.org" <grow@ietf.org>, draft-foo-sidr-simple-leak-attack-bgpsec-no-help@tools.ietf.org, grow-ads@tools.ietf.org, grow-chairs@tools.ietf.org
Subject: Re: [GROW] RouteLeaks - problem or not?
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, 15 Nov 2012 05:27:39 -0000

Shane,

See below.

On Wed, Nov 14, 2012 at 11:33 PM, Shane Amante <shane@castlepoint.net> wrot=
e:
> Chris,
>
> See below.
>
> On Nov 14, 2012, at 3:18 PM, Christopher Morrow <christopher.morrow@gmail=
.com> wrote:
> [--snip--]
>> To date there is a draft which discusses route leaks:
>>  <http://tools.ietf.org/html/draft-foo-sidr-simple-leak-attack-bgpsec-no=
-help-02>
>>
>> where the authors have attempted to describe one (or many possible)
>> situations which are called 'route leaks'. They also attempt to
>> outline security issues which are follow-on effects of the situation
>> described.
>>
>> SIDR attempted to look at route-leaks and came up a bit stymied, they
>> asked IDR for some assistance with the issue, IDR pushed back to GROW
>> to decide:
>>  1) What is a 'route leak' (perhaps the above draft identifies one
>> examplar to be used in that definition)
>
> See aforementioned draft.  It's the most _concise_ definition of the prob=
lem, as observed repeatedly in the Internet.
>
>
>>  2) Are 'route leaks' a problem that Operations folks care about
>
> Yes!
>
>
>>  3) Should IDR (or the IETF proper) address 'route leaks' with some
>> form(s) of fix action.
>
> WRT "Should IDR" ... that's like Henry Ford asking what color "Model T" I=
'd like, right?  Look, no offense to the folks in IDR :-), but as with ever=
y other WG their present charter is narrowly defined to 'enhancements to BG=
P'.  I would hope that _when_the_time_comes_ we remain open-minded about co=
nducting a thorough evaluation of the solution space, before deciding to fu=
rther refine one, or more, of those solutions to a standard, or set of stan=
dards.  So, presently, I would not be in favor of exclusively asking IDR to=
 fix 'route leaks', given the concerns I've raised above.
>

apologies, I was a bit rushed in my message (and I note my first
question was poorly chosen, as well) but I had meant to say that the
placement of a  solution doesn't have to be in bgp (so doesn't have to
involve IDR), if the WG here takes a look at sees other directions to
go.

> FWIW, I'm not clear on what you're proposing with "the IETF proper" ... s=
o I can't say "yes" to that option either.
>

'should the ietf care about this problem, and spend resources
attempting to provide solutions?'

is that better? I'm really asking whether or not there is a problem
and if we (ietf in general) can get a solution (or even the
requirements for a solution?) defined...

-chris

>
>> The end result of the above 3 steps is to push back into IDR one of
>> two action requests:
>>  1) "Yes, route leaks are a problem, please fix them."
>>     or
>>  2) "No, route leaks are not a problem, take no action."
>>
>> If #1 above is the answer, and IDR decides that changes to the BGP
>> protocol are warranted (or are a possible solution to the problem)
>> then SIDR has agreed to do what they can to 'secure' the bits
>> added/changed/used in that endeavor.
>
> Dare I ask what happens if IDR decides they do not have an answer?
>
>
>> Could we have some discussion on-list about this problem, and some
>> discussion about whether or not the draft referenced above fits the
>> definition we would like to use for 'route leak'?
>
> Um, yes, but then again I'm a co-author, so clearly you should take this =
answer with a healthy dose of salt.  :-)
>
>
>> I would also like
>> the authors of the draft to decide where they would like to take their
>> draft:
>>   1) SIDR
>>   2) IDR
>>   3) GROW
>>   4) other
>
> IMO, since you're asking GROW, the answer should hopefully present itself=
.  :-)
>
> -shane

From job@instituut.net  Wed Nov 14 23:07:18 2012
Return-Path: <job@instituut.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 5A57E21F87A0 for <grow@ietfa.amsl.com>; Wed, 14 Nov 2012 23:07:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2jj7iUN-Z05F for <grow@ietfa.amsl.com>; Wed, 14 Nov 2012 23:07:17 -0800 (PST)
Received: from mail-wi0-f172.google.com (mail-wi0-f172.google.com [209.85.212.172]) by ietfa.amsl.com (Postfix) with ESMTP id 46A5A21F87AD for <grow@ietf.org>; Wed, 14 Nov 2012 23:07:16 -0800 (PST)
Received: by mail-wi0-f172.google.com with SMTP id hj6so834902wib.13 for <grow@ietf.org>; Wed, 14 Nov 2012 23:07:15 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer :x-gm-message-state; bh=ZyEgB9g5oU1x/LA/xUTCGmeJoiFeFTqa+Haa7aI01qY=; b=lDaE/Ffg+wQJQQKgY9WZVY+2utn/pjXwmE7B3+eKXDLKjPUJwDBswNkxd1lhSJ+b5R VOOj6qBiUsAJFlYpl9FNSisdsf3yPjNgo+KgYATpZnfwozJyVwmJiNDO+PQlLlyzDhC4 yKyhyozythWO8mHLG2zcO9MYynWa1IJggIbiuGX3uq7j1acXNvjfOscQjC13fwN6ALyU L2Av+G02pfraWHVxWED5IsQdbTgmxf95iI721YkR9gT7n+9hhXLLuobiN4+6MBE4ARBd tchfqIa3SbVbAcqLD/8kHkiGvn5nndO80WULFyoTB9LmcZRW++EbZEFeoOtZyczNt88i h3jw==
Received: by 10.216.217.134 with SMTP id i6mr91878wep.22.1352963205383; Wed, 14 Nov 2012 23:06:45 -0800 (PST)
Received: from ?IPv6:2001:67c:208c:10:59e:489f:536c:cdb? ([2001:67c:208c:10:59e:489f:536c:cdb]) by mx.google.com with ESMTPS id az2sm26325273wib.7.2012.11.14.23.06.29 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 14 Nov 2012 23:06:30 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: Job Snijders <job@instituut.net>
In-Reply-To: <06206752-A09E-4F37-B1A9-25B8DB3CCFB9@puck.nether.net>
Date: Thu, 15 Nov 2012 08:06:27 +0100
Content-Transfer-Encoding: 7bit
Message-Id: <2996E883-FEC8-4EAB-AEC1-CCB32E057641@instituut.net>
References: <CAL9jLaagY5bBe_8eRST8noEp2-o00Zkm2Qc59Ys7pak++EPGNw@mail.gmail.com> <50A42ED5.2060803@inex.ie> <06206752-A09E-4F37-B1A9-25B8DB3CCFB9@puck.nether.net>
To: Jared Mauch <jared@puck.nether.net>
X-Mailer: Apple Mail (2.1499)
X-Gm-Message-State: ALoCoQnIpEwnjE/xrynR0Cp8iZshRqsoRU2ycjGldm5aI/Pqokq5LcUj8GRuHHLFL21iK0tdR1Hu
Cc: "grow@ietf.org" <grow@ietf.org>, grow-ads@tools.ietf.org, draft-foo-sidr-simple-leak-attack-bgpsec-no-help@tools.ietf.org, grow-chairs@tools.ietf.org
Subject: Re: [GROW] RouteLeaks - problem or not?
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, 15 Nov 2012 07:07:18 -0000

Hi,

On Nov 15, 2012, at 12:57 AM, Jared Mauch <jared@puck.nether.net> wrote:

> On Nov 14, 2012, at 6:52 PM, Nick Hilliard <nick@inex.ie> wrote:
> 
>> On 14/11/2012 22:18, Christopher Morrow wrote:
>>> 1) What is a 'route leak' (perhaps the above draft identifies one
>>> examplar to be used in that definition)
>> 
>> dunno really.  Some foo which involves prefixes being sent to places where
>> they oughtn't have been sent to.  This is possibly more of a legal /
>> wordsmithing problem than anything else.
> 
> I would say unexpected paths that appear as a result of poorly constructed
> routing policies or software defaults and lax filtering policies.

I'd define it as following: 

	Route Leak: When a misconfigured BGP speaker sends an NLRI Update to another
	Autonomous System and subsequently becomes a potential transit network for
	the given NLRI while this transit service is not aligned with the routing
	policy between the two networks, the NLRI Update is considered a route leak.

Kind regards,

Job

From xuxiaohu@huawei.com  Thu Nov 15 02:10:35 2012
Return-Path: <xuxiaohu@huawei.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 B82B421F8586 for <grow@ietfa.amsl.com>; Thu, 15 Nov 2012 02:10:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.377
X-Spam-Level: 
X-Spam-Status: No, score=-2.377 tagged_above=-999 required=5 tests=[AWL=-0.920, BAYES_00=-2.599, CN_BODY_35=0.339, J_CHICKENPOX_13=0.6, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aYNerLKSqqUu for <grow@ietfa.amsl.com>; Thu, 15 Nov 2012 02:10:35 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 0695721F8475 for <grow@ietf.org>; Thu, 15 Nov 2012 02:10:33 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id ALP12215; Thu, 15 Nov 2012 10:10:32 +0000 (GMT)
Received: from LHREML402-HUB.china.huawei.com (10.201.5.241) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 15 Nov 2012 10:10:17 +0000
Received: from SZXEML427-HUB.china.huawei.com (10.72.61.35) by lhreml402-hub.china.huawei.com (10.201.5.241) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 15 Nov 2012 10:10:30 +0000
Received: from SZXEML525-MBX.china.huawei.com ([169.254.1.161]) by szxeml427-hub.china.huawei.com ([10.72.61.35]) with mapi id 14.01.0323.003; Thu, 15 Nov 2012 18:10:13 +0800
From: Xuxiaohu <xuxiaohu@huawei.com>
To: Ronald Bonica <rbonica@juniper.net>
Thread-Topic: Wake up two sleeping VA drafts?//: Last Call comments on draft-ietf-l3vpn-virtual-hub 
Thread-Index: AQHNvfsEMb5fV5gac0WMrTIRrVsjCZfhshUggAkC5zA=
Date: Thu, 15 Nov 2012 10:10:13 +0000
Message-ID: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE075718D5@szxeml525-mbx.china.huawei.com>
References: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0757029A@szxeml525-mbx.china.huawei.com> <2CF4CB03E2AA464BA0982EC92A02CE250652EC@CH1PRD0511MB418.namprd05.prod.outlook.com>
In-Reply-To: <2CF4CB03E2AA464BA0982EC92A02CE250652EC@CH1PRD0511MB418.namprd05.prod.outlook.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.98.130]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] Wake up two sleeping VA drafts?//: Last Call comments on draft-ietf-l3vpn-virtual-hub
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, 15 Nov 2012 10:10:35 -0000

SGkgUm9uLA0KDQpEaWQgdGhlIFdHIGFkb3B0aW9uIGFuZCB0aGUgSUVTRyBzdWJtaXNzaW9uIG9m
IHRoZXNlIHRocmVlIGRyYWZ0cyBhbHJlYWR5IGRlbW9uc3RyYXRlIHRoZSBXRyByb3VnaCBjb25z
ZW5zdXM/DQoNCkJlc3QgcmVnYXJkcywNClhpYW9odQ0KDQo+IC0tLS0t08q8/tStvP4tLS0tLQ0K
PiC3orz+yMs6IFJvbmFsZCBCb25pY2EgW21haWx0bzpyYm9uaWNhQGp1bmlwZXIubmV0XQ0KPiC3
osvNyrG85DogMjAxMsTqMTHUwjEwyNUgMDoyOA0KPiDK1bz+yMs6IFh1eGlhb2h1DQo+ILOty806
IGdyb3dAaWV0Zi5vcmcNCj4g1vfM4jogUkU6IFdha2UgdXAgdHdvIHNsZWVwaW5nIFZBIGRyYWZ0
cz8vLzogTGFzdCBDYWxsIGNvbW1lbnRzIG9uDQo+IGRyYWZ0LWlldGYtbDN2cG4tdmlydHVhbC1o
dWINCj4gDQo+IEhvdyBkbyBmb2xrcyBvbiB0aGUgbGlzdCBmZWVsPw0KPiANCj4gICAgICAgICAg
ICAgICAgICAgICAgICAgIFJvbg0KPiANCj4gDQo+ID4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0t
LS0NCj4gPiBGcm9tOiBYdXhpYW9odSBbbWFpbHRvOnh1eGlhb2h1QGh1YXdlaS5jb21dDQo+ID4g
U2VudDogVGh1cnNkYXksIE5vdmVtYmVyIDA4LCAyMDEyIDQ6NTMgUE0NCj4gPiBUbzogUm9uYWxk
IEJvbmljYQ0KPiA+IENjOiBncm93QGlldGYub3JnDQo+ID4gU3ViamVjdDogV2FrZSB1cCB0d28g
c2xlZXBpbmcgVkEgZHJhZnRzPy8vOiBMYXN0IENhbGwgY29tbWVudHMgb24NCj4gPiBkcmFmdC1p
ZXRmLWwzdnBuLXZpcnR1YWwtaHViDQo+ID4NCj4gPiBIaSBSb25hbGQsDQo+ID4NCj4gPiBJZiBJ
IHJlbWVtYmVyZWQgY29ycmVjdGx5LCB5b3UgaGF2ZSBzYWlkLCBkdXJpbmcgdGhlIFdHIGxhc3Qg
Y2FsbCBvZg0KPiA+IHRocmVlIFZBIGRyYWZ0LCB0aGF0IHlvdSBtYXkgcmVjb25zaWRlciB5b3Vy
IGF0dGl0dWRlcyB0b3dhcmRzIHRoZSB0d28NCj4gPiBvZiB0aHJlZSBWQSBkcmFmdHMgKGRyYWZ0
LWlldGYtZ3Jvdy12YSBhbmQgZHJhZnQtaWV0Zi1ncm93LXZhLWF1dG8pIGluDQo+ID4gY2FzZSB0
aGVyZSB3ZXJlIGFueSBpbnRlcmVzdHMgZnJvbSBTUHMgb24gdGhlIEZJQiBhZ2dyZWdhdGlvbi4N
Cj4gPg0KPiA+IEkgb2NjYXNpb25hbGx5IG5vdGljZWQgdGhhdCBkcmFmdC1pZXRmLWwzdnBuLXZp
cnR1YWwtaHViIGhhcyBqdXN0DQo+ID4gZGVjcmliZWQgYSB1c2UgY2FzZSBvZiBGSUIgYWdncmVn
YXRpb24gIGFuZCBhIHBvc3NpYmxlIEZJQiBhZ2dyZWdhdGlvbg0KPiA+IGFwcHJvYWNoIHdoaWNo
IHNlZW1zIG11Y2ggc2ltaWxhciB0byB0aGUgVkEgYXBwcm9hY2ggKHNlZSB0aGUgZm9sbG93aW5n
DQo+ID4gdGV4dCBxdW90ZWQgZnJvbSB0aGF0IGRyYWZ0KS4gWW91IG1heSBoYXZlIG5vdGljZWQg
dGhhdCBtb3N0IG9mIHRoZSBjby0NCj4gPiBhdXRob3JzIG9mIHRoaXMgZHJhZnQgYXJlIGZyb20g
U1BzLg0KPiA+DQo+ID4gSW4gYWRkaXRpb24sIHRoZXJlIGFyZSBtYW55IGNvbmNlcm5zIHdpdGgg
dGhlIGZvcndhcmRpbmcgdGFibGUNCj4gPiBzY2FsYWJpbGl0eSBpc3N1ZXMgaW4gdGhlIG11bHRp
LXRlbmFudCBjbG91ZCBkYXRhIGNlbnRlciBuZXR3b3JrDQo+ID4gZW52aXJvbm1lbnRzIHRoYXQg
aGF2ZSBiZWVuIGV4cHJlc3NlZCBpbiBzZXZlcmFsIE5WbzMgcmVsYXRlZCBkcmFmdHMuDQo+ID4N
Cj4gPiBIZW5jZSBJIHdvbmRlciB3aGV0aGVyIHlvdSBjb3VsZCBwbGVhc2UgcmVjb25zaWRlciB5
b3VyIGF0dGl0dWRlcw0KPiA+IHRvd2FyZHMgdGhlIHR3byBvZiB0aHJlZSBWQSByZWxhdGVkIGRy
YWZ0cy4gTWFueSB0aGFua3MhDQo+ID4NCj4gPg0KPiA+ICoqKioqKioqKioqKioqKioqKioqKioq
KioqDQo+ID4gOS4gRnVydGhlciByZWZpbmVtZW50cw0KPiA+ICAgIEluIHNvbWUgY2FzZXMgYSBW
UE4gY3VzdG9tZXIgbWF5IG5vdCB3YW50IHRvIHJlbHkgc29sZWx5IG9uIGFuIChJUCkNCj4gPiAg
ICBkZWZhdWx0IHJvdXRlIGJlaW5nIGFkdmVydGlzZWQgZnJvbSBhIFYtc3Bva2UgdG8gYSBDRSwg
YnV0IG1heSB3YW50DQo+ID4gICAgQ0VzIHRvIHJlY2VpdmUgYWxsIHRoZSBWUE4gcm91dGVzIChl
LmcuLCBmb3IgdGhlIHB1cnBvc2Ugb2YgZmFzdGVyDQo+ID4gICAgZGV0ZWN0aW9uIG9mIFZQTiBj
b25uZWN0aXZpdHkgZmFpbHVyZXMsIGFuZCBhY3RpdmF0aW5nIHNvbWUgYmFja3VwDQo+ID4gICAg
Y29ubmVjdGl2aXR5KS4NCj4gPiAgICBJbiB0aGlzIGNhc2Ugb25lIHBvc3NpYmxlIGFwcHJvYWNo
IHdvdWxkIGJlIHRvIGluc3RhbGwgaW4gdGhlIFYtDQo+ID4gICAgc3Bva2UncyBkYXRhIHBsYW5l
IG9ubHkgdGhlIGRlZmF1bHQgcm91dGUgKGZvbGxvd2luZyB0aGUgVmlydHVhbCBIdWINCj4gPiAg
ICBhbmQgU3Bva2UgbW9kZWwsIGFzIGRlc2NyaWJlZCBhYm92ZSksIGJ1dCBrZWVwIGFsbCB0aGUg
VlBOLUlQIHJvdXRlcw0KPiA+ICAgIGluIHRoZSBWLXNwb2tlJ3MgY29udHJvbCBwbGFuZSAoYW5k
IHRodXMgYmVpbmcgYWJsZSB0byBhZHZlcnRpc2UNCj4gPiAgICB0aGVzZSByb3V0ZXMgZnJvbSB0
aGUgVi1zcG9rZSB0byB0aGUgQ0VzKS4gIEdyYW50ZWQsIHRoaXMgd291bGQgbm90DQo+ID4gICAg
Y2hhbmdlIGNvbnRyb2wgcGxhbmUgcmVzb3VyY2UgY29uc3VtcHRpb24sIGJ1dCB3b3VsZCAoc2ln
bmlmaWNhbnRseSkNCj4gPiAgICByZWR1Y2UgcmVzb3VyY2UgY29uc3VtcHRpb24gb24gdGhlIGRh
dGEgcGxhbmUuDQo+ID4gKioqKioqKioqKioqKioqKioqKioqKioqKioqKioNCj4gPg0KPiA+IEJl
c3QgcmVnYXJkcywNCj4gPiBYaWFvaHUNCj4gPiBfX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fDQo+ID4gt6K8/sjLOiBsM3Zwbi1ib3VuY2VzQGlldGYub3JnIFtsM3Zwbi1i
b3VuY2VzQGlldGYub3JnXSC0+rHtIFlha292DQo+ID4gUmVraHRlciBbeWFrb3ZAanVuaXBlci5u
ZXRdDQo+ID4gt6LLzcqxvOQ6IDIwMTLE6jEx1MI4yNUgMjM6MTcNCj4gPiC1vTogZXJvc2VuQGNp
c2NvLmNvbQ0KPiA+IENjOiBMM1ZQTg0KPiA+INb3zOI6IFJlOiBMYXN0IENhbGwgY29tbWVudHMg
b24gZHJhZnQtaWV0Zi1sM3Zwbi12aXJ0dWFsLWh1Yg0KPiA+DQo+ID4gRXJpYywNCj4gPg0KPiA+
ID4gSSBoYXZlIGEgbnVtYmVyIG9mIGNvbW1lbnRzIG9uIHRoZSB2aXJ0dWFsLWh1YiBkcmFmdC4g
IFNvbWUgYXJlIG1pbm9yDQo+ID4gPiBhbmQvb3IgZWRpdG9yaWFsLCBidXQgYSBudW1iZXIgYXJl
IG1vcmUgc3Vic3RhbnRpYWwuICBJIHRoaW5rIHRoZXNlDQo+ID4gPiBjb21tZW50cyBuZWVkIHRv
IGJlIGFkZHJlc3NlZCBiZWZvcmUgdGhlIGRyYWZ0IGlzIHN1Ym1pdHRlZCBmb3INCj4gPiBwdWJs
aWNhdGlvbi4NCj4gPiA+DQo+ID4gPiBJJ3ZlIHBsYWNlZCBhIGxvdCBvZiBjb21tZW50cyBpbi1s
aW5lLCBidXQgbGV0IG1lIHN1bW1hcml6ZSB3aGF0IEkNCj4gPiA+IHRoaW5rIGFyZSB0aGUgbWFq
b3IgaXNzdWVzOg0KPiA+DQo+ID4gSSBhbSBpbiB0aGUgcHJvY2VzcyBvZiBhZGRyZXNzaW5nIHlv
dXIgY29tbWVudHMuIEluIHRoaXMgZS1tYWlsIEknZA0KPiA+IGxpa2UgdG8gZm9jdXMgb24gb25l
IHBhcnRpY3VsYXIgb25lOg0KPiA+DQo+ID4gPiBFcmljPiBMZXQncyBjb25zaWRlciB0aGUgY2Fz
ZSB3aGVyZSB0aGUgc291cmNlIGlzIGF0IGEgc2l0ZSBhdHRhY2hlZA0KPiA+ID4gRXJpYz4gdG8g
Vi1odWIyLiAgVi1odWIxIHdpbGwgcmVjZWl2ZSBhbiBTLVBNU0kgQS1EIHJvdXRlIG1hdGNoaW5n
DQo+ID4gPiBFcmljPiAoUyxHKSBmcm9tIFYtaHViMi4gIFYtaHViMSB0aGVuIG1vZGlmaWVzIHRo
aXMgQS1EIHJvdXRlIGFuZA0KPiA+ID4gRXJpYz4gZm9yd2FyZHMgaXQgdG8gVi1zcG9rZTEuICBW
LWh1YjEgY291bGQgdXNlIHRoaXMgcm91dGUgdG8NCj4gPiA+IEVyaWM+IGlkZW50aWZ5IHRoZSBQ
LXR1bm5lbCBvcmlnaW5hdGluZyBhdCBWLWh1YjIsIHRoZXJlYnkNCj4gPiBpbnN0cnVjdGluZw0K
PiA+ID4gRXJpYz4gVi1zcG9rZTEgdG8gam9pbiBWLWh1YjIncyB0dW5uZWwgZGlyZWN0bHkuICBU
aGVuIFYtaHViMSB3b3VsZA0KPiA+ID4gRXJpYz4gbm90IGJlIGluIHRoZSBkYXRhIHBhdGggZnJv
bSBTIHRvIFIsIGJ1dCBpdCB3b3VsZCBwYXJ0aWNpcGF0ZQ0KPiA+IGluDQo+ID4gPiBFcmljPiB0
aGUgY29udHJvbCBwbGFuZS4gIFdvdWxkbid0IHRoaXMgbWVldCBhbGwgdGhlIHJlcXVpcmVtZW50
cyBvZg0KPiA+ID4gRXJpYz4gdGhlIFYtaHViL1Ytc3Bva2UgYXJjaGl0ZWN0dXJlLCB3aGlsZSBw
cm9kdWNpbmcgYSBtb3JlIG9wdGltYWwNCj4gPiA+IEVyaWM+IHBhdGggZm9yIG11bHRpY2FzdCBk
YXRhLCBhbmQgZWxpbWluYXRpbmcgdGhlIG5lZWQgdG8gaGF2ZSB0aGUNCj4gPiBWLWh1YnMgc3Bs
aWNlIHRvZ2V0aGVyIGFueSBQLXR1bm5lbHM/DQo+ID4gPg0KPiA+ID4gRXJpYz4gV2FzIGFueSBj
b25zaWRlcmF0aW9uIGdpdmVuIHRvIHN1Y2ggYW4gYWx0ZXJuYXRpdmU/DQo+ID4NCj4gPiBQbGVh
c2Ugbm90ZSB0aGF0IHRoZSBwcm9jZWR1cmVzIHNwZWNpZmllZCBpbiB0aGUgZHJhZnQgYXNzdW1l
IHRoZQ0KPiA+IGFiaWxpdHkgdG8gcGVyZm9ybSBzZW5kZXItYmFzZWQgUlBGLCBhcyBzcGVjaWZp
ZWQgaW4gOS4xLjEgb2YgcmZjNjUxMy4NCj4gPiBHaXZlbiB0aGF0LCBpZiBvbmUgd291bGQgZm9s
bG93IHdoYXQgeW91IG91dGxpbmVkIGFib3ZlLCBjb3VsZCB5b3UNCj4gPiBwb2ludCBtZSB0byB0
aGUgc3BlY2lmaWMgdGV4dCBpbiA5LjEuMSB0aGF0IHdvdWxkIGVuYWJsZSBWLXNwb2tlMSB0bw0K
PiA+IGRldGVybWluZSB0aGF0IGZyb20gaXRzIG93biBwZXJzcGVjdGl2ZSB0aGUgVU1IIGZvciAo
Qy1TLCBDLUcpIGlzIFYtDQo+ID4gaHViMSA/DQo+ID4NCj4gPiBGdXJ0aGVybW9yZSwgeW91ciBv
dXRsaW5lIGFib3ZlIHRhbGtzIGFib3V0IFMtUE1TSSBBLUQgcm91dGUuIEhvdyB3b3VsZA0KPiA+
IGl0IHdvcmsgZm9yIEktUE1TSSBBLUQgcm91dGVzID8NCj4gPg0KPiA+IFlha292Lg0K

From xuxiaohu@huawei.com  Thu Nov 15 02:14:29 2012
Return-Path: <xuxiaohu@huawei.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 EDE0421F85A9 for <grow@ietfa.amsl.com>; Thu, 15 Nov 2012 02:14:29 -0800 (PST)
X-Quarantine-ID: <WmXY61kpWVK3>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Improper folded header field made up entirely of whitespace (char 20 hex): References: ...C@CH1PRD0511MB418.namprd05.prod.outlook.com>\n 
X-Spam-Flag: NO
X-Spam-Score: -2.275
X-Spam-Level: 
X-Spam-Status: No, score=-2.275 tagged_above=-999 required=5 tests=[AWL=-0.818, BAYES_00=-2.599, CN_BODY_35=0.339, J_CHICKENPOX_13=0.6, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WmXY61kpWVK3 for <grow@ietfa.amsl.com>; Thu, 15 Nov 2012 02:14:29 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 563A421F858B for <grow@ietf.org>; Thu, 15 Nov 2012 02:14:28 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id AMV15439; Thu, 15 Nov 2012 10:14:27 +0000 (GMT)
Received: from LHREML404-HUB.china.huawei.com (10.201.5.218) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 15 Nov 2012 10:14:13 +0000
Received: from SZXEML410-HUB.china.huawei.com (10.82.67.137) by lhreml404-hub.china.huawei.com (10.201.5.218) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 15 Nov 2012 18:14:26 +0800
Received: from SZXEML525-MBX.china.huawei.com ([169.254.1.161]) by szxeml410-hub.china.huawei.com ([10.82.67.137]) with mapi id 14.01.0323.003; Thu, 15 Nov 2012 18:14:23 +0800
From: Xuxiaohu <xuxiaohu@huawei.com>
To: Ronald Bonica <rbonica@juniper.net>
Thread-Topic: Wake up two sleeping VA drafts?//: Last Call comments on draft-ietf-l3vpn-virtual-hub 
Thread-Index: AQHNvfsEMb5fV5gac0WMrTIRrVsjCZfhshUggAkC5zCAAAJnMA==
Date: Thu, 15 Nov 2012 10:14:23 +0000
Message-ID: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE075718E3@szxeml525-mbx.china.huawei.com>
References: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0757029A@szxeml525-mbx.china.huawei.com> <2CF4CB03E2AA464BA0982EC92A02CE250652EC@CH1PRD0511MB418.namprd05.prod.outlook.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.98.130]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] Wake up two sleeping VA drafts?//: Last Call comments on draft-ietf-l3vpn-virtual-hub
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, 15 Nov 2012 10:14:30 -0000

PiAtLS0tLdPKvP7Urbz+LS0tLS0NCj4gt6K8/sjLOiBYdXhpYW9odQ0KPiC3osvNyrG85DogMjAx
MsTqMTHUwjE1yNUgMTg6MTANCj4gytW8/sjLOiAnUm9uYWxkIEJvbmljYScNCj4gs63LzTogZ3Jv
d0BpZXRmLm9yZw0KPiDW98ziOiByZTogV2FrZSB1cCB0d28gc2xlZXBpbmcgVkEgZHJhZnRzPy8v
OiBMYXN0IENhbGwgY29tbWVudHMgb24NCj4gZHJhZnQtaWV0Zi1sM3Zwbi12aXJ0dWFsLWh1Yg0K
PiANCj4gSGkgUm9uLA0KPiANCj4gRGlkIHRoZSBXRyBhZG9wdGlvbiBhbmQgdGhlIElFU0cgc3Vi
bWlzc2lvbiBvZiB0aGVzZSB0aHJlZSBkcmFmdHMgYWxyZWFkeQ0KPiBkZW1vbnN0cmF0ZSB0aGUg
V0cgcm91Z2ggY29uc2Vuc3VzPw0KDQpTb3JyeSwgdGhlIGFib3ZlIHNob3VsZCBiZTogRGlkbid0
IHRoZSBXRyBhZG9wdGlvbiBhbmQgdGhlIElFU0cgc3VibWlzc2lvbiBvZiB0aGVzZSB0aHJlZSBk
cmFmdHMgYWxyZWFkeQ0KZGVtb25zdHJhdGUgdGhlIFdHIHJvdWdoIGNvbnNlbnN1cz8NCg0KPiBC
ZXN0IHJlZ2FyZHMsDQo+IFhpYW9odQ0KPiANCj4gPiAtLS0tLdPKvP7Urbz+LS0tLS0NCj4gPiC3
orz+yMs6IFJvbmFsZCBCb25pY2EgW21haWx0bzpyYm9uaWNhQGp1bmlwZXIubmV0XQ0KPiA+ILei
y83KsbzkOiAyMDEyxOoxMdTCMTDI1SAwOjI4DQo+ID4gytW8/sjLOiBYdXhpYW9odQ0KPiA+ILOt
y806IGdyb3dAaWV0Zi5vcmcNCj4gPiDW98ziOiBSRTogV2FrZSB1cCB0d28gc2xlZXBpbmcgVkEg
ZHJhZnRzPy8vOiBMYXN0IENhbGwgY29tbWVudHMgb24NCj4gPiBkcmFmdC1pZXRmLWwzdnBuLXZp
cnR1YWwtaHViDQo+ID4NCj4gPiBIb3cgZG8gZm9sa3Mgb24gdGhlIGxpc3QgZmVlbD8NCj4gPg0K
PiA+ICAgICAgICAgICAgICAgICAgICAgICAgICBSb24NCj4gPg0KPiA+DQo+ID4gPiAtLS0tLU9y
aWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiA+ID4gRnJvbTogWHV4aWFvaHUgW21haWx0bzp4dXhpYW9o
dUBodWF3ZWkuY29tXQ0KPiA+ID4gU2VudDogVGh1cnNkYXksIE5vdmVtYmVyIDA4LCAyMDEyIDQ6
NTMgUE0NCj4gPiA+IFRvOiBSb25hbGQgQm9uaWNhDQo+ID4gPiBDYzogZ3Jvd0BpZXRmLm9yZw0K
PiA+ID4gU3ViamVjdDogV2FrZSB1cCB0d28gc2xlZXBpbmcgVkEgZHJhZnRzPy8vOiBMYXN0IENh
bGwgY29tbWVudHMgb24NCj4gPiA+IGRyYWZ0LWlldGYtbDN2cG4tdmlydHVhbC1odWINCj4gPiA+
DQo+ID4gPiBIaSBSb25hbGQsDQo+ID4gPg0KPiA+ID4gSWYgSSByZW1lbWJlcmVkIGNvcnJlY3Rs
eSwgeW91IGhhdmUgc2FpZCwgZHVyaW5nIHRoZSBXRyBsYXN0IGNhbGwgb2YNCj4gPiA+IHRocmVl
IFZBIGRyYWZ0LCB0aGF0IHlvdSBtYXkgcmVjb25zaWRlciB5b3VyIGF0dGl0dWRlcyB0b3dhcmRz
IHRoZSB0d28NCj4gPiA+IG9mIHRocmVlIFZBIGRyYWZ0cyAoZHJhZnQtaWV0Zi1ncm93LXZhIGFu
ZCBkcmFmdC1pZXRmLWdyb3ctdmEtYXV0bykgaW4NCj4gPiA+IGNhc2UgdGhlcmUgd2VyZSBhbnkg
aW50ZXJlc3RzIGZyb20gU1BzIG9uIHRoZSBGSUIgYWdncmVnYXRpb24uDQo+ID4gPg0KPiA+ID4g
SSBvY2Nhc2lvbmFsbHkgbm90aWNlZCB0aGF0IGRyYWZ0LWlldGYtbDN2cG4tdmlydHVhbC1odWIg
aGFzIGp1c3QNCj4gPiA+IGRlY3JpYmVkIGEgdXNlIGNhc2Ugb2YgRklCIGFnZ3JlZ2F0aW9uICBh
bmQgYSBwb3NzaWJsZSBGSUIgYWdncmVnYXRpb24NCj4gPiA+IGFwcHJvYWNoIHdoaWNoIHNlZW1z
IG11Y2ggc2ltaWxhciB0byB0aGUgVkEgYXBwcm9hY2ggKHNlZSB0aGUgZm9sbG93aW5nDQo+ID4g
PiB0ZXh0IHF1b3RlZCBmcm9tIHRoYXQgZHJhZnQpLiBZb3UgbWF5IGhhdmUgbm90aWNlZCB0aGF0
IG1vc3Qgb2YgdGhlIGNvLQ0KPiA+ID4gYXV0aG9ycyBvZiB0aGlzIGRyYWZ0IGFyZSBmcm9tIFNQ
cy4NCj4gPiA+DQo+ID4gPiBJbiBhZGRpdGlvbiwgdGhlcmUgYXJlIG1hbnkgY29uY2VybnMgd2l0
aCB0aGUgZm9yd2FyZGluZyB0YWJsZQ0KPiA+ID4gc2NhbGFiaWxpdHkgaXNzdWVzIGluIHRoZSBt
dWx0aS10ZW5hbnQgY2xvdWQgZGF0YSBjZW50ZXIgbmV0d29yaw0KPiA+ID4gZW52aXJvbm1lbnRz
IHRoYXQgaGF2ZSBiZWVuIGV4cHJlc3NlZCBpbiBzZXZlcmFsIE5WbzMgcmVsYXRlZCBkcmFmdHMu
DQo+ID4gPg0KPiA+ID4gSGVuY2UgSSB3b25kZXIgd2hldGhlciB5b3UgY291bGQgcGxlYXNlIHJl
Y29uc2lkZXIgeW91ciBhdHRpdHVkZXMNCj4gPiA+IHRvd2FyZHMgdGhlIHR3byBvZiB0aHJlZSBW
QSByZWxhdGVkIGRyYWZ0cy4gTWFueSB0aGFua3MhDQo+ID4gPg0KPiA+ID4NCj4gPiA+ICoqKioq
KioqKioqKioqKioqKioqKioqKioqDQo+ID4gPiA5LiBGdXJ0aGVyIHJlZmluZW1lbnRzDQo+ID4g
PiAgICBJbiBzb21lIGNhc2VzIGEgVlBOIGN1c3RvbWVyIG1heSBub3Qgd2FudCB0byByZWx5IHNv
bGVseSBvbiBhbiAoSVApDQo+ID4gPiAgICBkZWZhdWx0IHJvdXRlIGJlaW5nIGFkdmVydGlzZWQg
ZnJvbSBhIFYtc3Bva2UgdG8gYSBDRSwgYnV0IG1heSB3YW50DQo+ID4gPiAgICBDRXMgdG8gcmVj
ZWl2ZSBhbGwgdGhlIFZQTiByb3V0ZXMgKGUuZy4sIGZvciB0aGUgcHVycG9zZSBvZiBmYXN0ZXIN
Cj4gPiA+ICAgIGRldGVjdGlvbiBvZiBWUE4gY29ubmVjdGl2aXR5IGZhaWx1cmVzLCBhbmQgYWN0
aXZhdGluZyBzb21lIGJhY2t1cA0KPiA+ID4gICAgY29ubmVjdGl2aXR5KS4NCj4gPiA+ICAgIElu
IHRoaXMgY2FzZSBvbmUgcG9zc2libGUgYXBwcm9hY2ggd291bGQgYmUgdG8gaW5zdGFsbCBpbiB0
aGUgVi0NCj4gPiA+ICAgIHNwb2tlJ3MgZGF0YSBwbGFuZSBvbmx5IHRoZSBkZWZhdWx0IHJvdXRl
IChmb2xsb3dpbmcgdGhlIFZpcnR1YWwgSHViDQo+ID4gPiAgICBhbmQgU3Bva2UgbW9kZWwsIGFz
IGRlc2NyaWJlZCBhYm92ZSksIGJ1dCBrZWVwIGFsbCB0aGUgVlBOLUlQIHJvdXRlcw0KPiA+ID4g
ICAgaW4gdGhlIFYtc3Bva2UncyBjb250cm9sIHBsYW5lIChhbmQgdGh1cyBiZWluZyBhYmxlIHRv
IGFkdmVydGlzZQ0KPiA+ID4gICAgdGhlc2Ugcm91dGVzIGZyb20gdGhlIFYtc3Bva2UgdG8gdGhl
IENFcykuICBHcmFudGVkLCB0aGlzIHdvdWxkIG5vdA0KPiA+ID4gICAgY2hhbmdlIGNvbnRyb2wg
cGxhbmUgcmVzb3VyY2UgY29uc3VtcHRpb24sIGJ1dCB3b3VsZCAoc2lnbmlmaWNhbnRseSkNCj4g
PiA+ICAgIHJlZHVjZSByZXNvdXJjZSBjb25zdW1wdGlvbiBvbiB0aGUgZGF0YSBwbGFuZS4NCj4g
PiA+ICoqKioqKioqKioqKioqKioqKioqKioqKioqKioqDQo+ID4gPg0KPiA+ID4gQmVzdCByZWdh
cmRzLA0KPiA+ID4gWGlhb2h1DQo+ID4gPiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fDQo+ID4gPiC3orz+yMs6IGwzdnBuLWJvdW5jZXNAaWV0Zi5vcmcgW2wzdnBuLWJv
dW5jZXNAaWV0Zi5vcmddILT6se0gWWFrb3YNCj4gPiA+IFJla2h0ZXIgW3lha292QGp1bmlwZXIu
bmV0XQ0KPiA+ID4gt6LLzcqxvOQ6IDIwMTLE6jEx1MI4yNUgMjM6MTcNCj4gPiA+ILW9OiBlcm9z
ZW5AY2lzY28uY29tDQo+ID4gPiBDYzogTDNWUE4NCj4gPiA+INb3zOI6IFJlOiBMYXN0IENhbGwg
Y29tbWVudHMgb24gZHJhZnQtaWV0Zi1sM3Zwbi12aXJ0dWFsLWh1Yg0KPiA+ID4NCj4gPiA+IEVy
aWMsDQo+ID4gPg0KPiA+ID4gPiBJIGhhdmUgYSBudW1iZXIgb2YgY29tbWVudHMgb24gdGhlIHZp
cnR1YWwtaHViIGRyYWZ0LiAgU29tZSBhcmUgbWlub3INCj4gPiA+ID4gYW5kL29yIGVkaXRvcmlh
bCwgYnV0IGEgbnVtYmVyIGFyZSBtb3JlIHN1YnN0YW50aWFsLiAgSSB0aGluayB0aGVzZQ0KPiA+
ID4gPiBjb21tZW50cyBuZWVkIHRvIGJlIGFkZHJlc3NlZCBiZWZvcmUgdGhlIGRyYWZ0IGlzIHN1
Ym1pdHRlZCBmb3INCj4gPiA+IHB1YmxpY2F0aW9uLg0KPiA+ID4gPg0KPiA+ID4gPiBJJ3ZlIHBs
YWNlZCBhIGxvdCBvZiBjb21tZW50cyBpbi1saW5lLCBidXQgbGV0IG1lIHN1bW1hcml6ZSB3aGF0
IEkNCj4gPiA+ID4gdGhpbmsgYXJlIHRoZSBtYWpvciBpc3N1ZXM6DQo+ID4gPg0KPiA+ID4gSSBh
bSBpbiB0aGUgcHJvY2VzcyBvZiBhZGRyZXNzaW5nIHlvdXIgY29tbWVudHMuIEluIHRoaXMgZS1t
YWlsIEknZA0KPiA+ID4gbGlrZSB0byBmb2N1cyBvbiBvbmUgcGFydGljdWxhciBvbmU6DQo+ID4g
Pg0KPiA+ID4gPiBFcmljPiBMZXQncyBjb25zaWRlciB0aGUgY2FzZSB3aGVyZSB0aGUgc291cmNl
IGlzIGF0IGEgc2l0ZSBhdHRhY2hlZA0KPiA+ID4gPiBFcmljPiB0byBWLWh1YjIuICBWLWh1YjEg
d2lsbCByZWNlaXZlIGFuIFMtUE1TSSBBLUQgcm91dGUgbWF0Y2hpbmcNCj4gPiA+ID4gRXJpYz4g
KFMsRykgZnJvbSBWLWh1YjIuICBWLWh1YjEgdGhlbiBtb2RpZmllcyB0aGlzIEEtRCByb3V0ZSBh
bmQNCj4gPiA+ID4gRXJpYz4gZm9yd2FyZHMgaXQgdG8gVi1zcG9rZTEuICBWLWh1YjEgY291bGQg
dXNlIHRoaXMgcm91dGUgdG8NCj4gPiA+ID4gRXJpYz4gaWRlbnRpZnkgdGhlIFAtdHVubmVsIG9y
aWdpbmF0aW5nIGF0IFYtaHViMiwgdGhlcmVieQ0KPiA+ID4gaW5zdHJ1Y3RpbmcNCj4gPiA+ID4g
RXJpYz4gVi1zcG9rZTEgdG8gam9pbiBWLWh1YjIncyB0dW5uZWwgZGlyZWN0bHkuICBUaGVuIFYt
aHViMSB3b3VsZA0KPiA+ID4gPiBFcmljPiBub3QgYmUgaW4gdGhlIGRhdGEgcGF0aCBmcm9tIFMg
dG8gUiwgYnV0IGl0IHdvdWxkIHBhcnRpY2lwYXRlDQo+ID4gPiBpbg0KPiA+ID4gPiBFcmljPiB0
aGUgY29udHJvbCBwbGFuZS4gIFdvdWxkbid0IHRoaXMgbWVldCBhbGwgdGhlIHJlcXVpcmVtZW50
cyBvZg0KPiA+ID4gPiBFcmljPiB0aGUgVi1odWIvVi1zcG9rZSBhcmNoaXRlY3R1cmUsIHdoaWxl
IHByb2R1Y2luZyBhIG1vcmUgb3B0aW1hbA0KPiA+ID4gPiBFcmljPiBwYXRoIGZvciBtdWx0aWNh
c3QgZGF0YSwgYW5kIGVsaW1pbmF0aW5nIHRoZSBuZWVkIHRvIGhhdmUgdGhlDQo+ID4gPiBWLWh1
YnMgc3BsaWNlIHRvZ2V0aGVyIGFueSBQLXR1bm5lbHM/DQo+ID4gPiA+DQo+ID4gPiA+IEVyaWM+
IFdhcyBhbnkgY29uc2lkZXJhdGlvbiBnaXZlbiB0byBzdWNoIGFuIGFsdGVybmF0aXZlPw0KPiA+
ID4NCj4gPiA+IFBsZWFzZSBub3RlIHRoYXQgdGhlIHByb2NlZHVyZXMgc3BlY2lmaWVkIGluIHRo
ZSBkcmFmdCBhc3N1bWUgdGhlDQo+ID4gPiBhYmlsaXR5IHRvIHBlcmZvcm0gc2VuZGVyLWJhc2Vk
IFJQRiwgYXMgc3BlY2lmaWVkIGluIDkuMS4xIG9mIHJmYzY1MTMuDQo+ID4gPiBHaXZlbiB0aGF0
LCBpZiBvbmUgd291bGQgZm9sbG93IHdoYXQgeW91IG91dGxpbmVkIGFib3ZlLCBjb3VsZCB5b3UN
Cj4gPiA+IHBvaW50IG1lIHRvIHRoZSBzcGVjaWZpYyB0ZXh0IGluIDkuMS4xIHRoYXQgd291bGQg
ZW5hYmxlIFYtc3Bva2UxIHRvDQo+ID4gPiBkZXRlcm1pbmUgdGhhdCBmcm9tIGl0cyBvd24gcGVy
c3BlY3RpdmUgdGhlIFVNSCBmb3IgKEMtUywgQy1HKSBpcyBWLQ0KPiA+ID4gaHViMSA/DQo+ID4g
Pg0KPiA+ID4gRnVydGhlcm1vcmUsIHlvdXIgb3V0bGluZSBhYm92ZSB0YWxrcyBhYm91dCBTLVBN
U0kgQS1EIHJvdXRlLiBIb3cgd291bGQNCj4gPiA+IGl0IHdvcmsgZm9yIEktUE1TSSBBLUQgcm91
dGVzID8NCj4gPiA+DQo+ID4gPiBZYWtvdi4NCg==

From warren@kumari.net  Thu Nov 15 07:21:49 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 52C9921F8897 for <grow@ietfa.amsl.com>; Thu, 15 Nov 2012 07:21:49 -0800 (PST)
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=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QmPYM836o-5L for <grow@ietfa.amsl.com>; Thu, 15 Nov 2012 07:21:47 -0800 (PST)
Received: from vimes.kumari.net (smtp1.kumari.net [204.194.22.1]) by ietfa.amsl.com (Postfix) with ESMTP id F0C6221F888E for <grow@ietf.org>; Thu, 15 Nov 2012 07:21:46 -0800 (PST)
Received: from [192.168.2.103] (unknown [209.133.29.2]) by vimes.kumari.net (Postfix) with ESMTPSA id 966D61B40639; Thu, 15 Nov 2012 10:21:45 -0500 (EST)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: Warren Kumari <warren@kumari.net>
In-Reply-To: <CAL9jLaagY5bBe_8eRST8noEp2-o00Zkm2Qc59Ys7pak++EPGNw@mail.gmail.com>
Date: Thu, 15 Nov 2012 10:21:41 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <13BC60DC-CBA6-414A-9F4B-A96C3F39D6FC@kumari.net>
References: <CAL9jLaagY5bBe_8eRST8noEp2-o00Zkm2Qc59Ys7pak++EPGNw@mail.gmail.com>
To: Christopher Morrow <christopher.morrow@gmail.com>
X-Mailer: Apple Mail (2.1499)
Cc: "grow@ietf.org grow@ietf.org" <grow@ietf.org>, Warren Kumari <warren@kumari.net>, draft-foo-sidr-simple-leak-attack-bgpsec-no-help@tools.ietf.org, grow-ads@tools.ietf.org, grow-chairs@tools.ietf.org
Subject: Re: [GROW] RouteLeaks - problem or not?
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, 15 Nov 2012 15:21:49 -0000

On Nov 14, 2012, at 5:18 PM, Christopher Morrow =
<christopher.morrow@gmail.com> wrote:

> GROW Folks,
Hi!

[SNIP]
>=20
> SIDR attempted to look at route-leaks and came up a bit stymied, they
> asked IDR for some assistance with the issue, IDR pushed back to GROW
> to decide:
>  1) What is a 'route leak' (perhaps the above draft identifies one
> examplar to be used in that definition)
>  2) Are 'route leaks' a problem that Operations folks care about

Yes=85=20


>  3) Should IDR (or the IETF proper) address 'route leaks' with some
> form(s) of fix action.

Yes=85=20

>=20
> The end result of the above 3 steps is to push back into IDR one of
> two action requests:
>  1) "Yes, route leaks are a problem, please fix them."
>     or
>  2) "No, route leaks are not a problem, take no action."
>=20
> If #1 above is the answer, and IDR decides that changes to the BGP
> protocol are warranted (or are a possible solution to the problem)
> then SIDR has agreed to do what they can to 'secure' the bits
> added/changed/used in that endeavor.

Personally I'm not convinced that the resolution to the "route leaks =
problem" needs to occur in BGP / needs to update BGP, so not sure if =
this gets 'fixed" in IDR, but I think that is does need to be worked on.


>=20
> Could we have some discussion on-list about this problem, and some
> discussion about whether or not the draft referenced above fits the
> definition we would like to use for 'route leak'? I would also like
> the authors of the draft to decide where they would like to take their
> draft:
>   1) SIDR
>   2) IDR
>   3) GROW
>   4) other
>=20
> Thanks!
> -Chris
> (co-chair 1:2 of grow, and 1:3 in sidr)
> _______________________________________________
> GROW mailing list
> GROW@ietf.org
> https://www.ietf.org/mailman/listinfo/grow
>=20

--
Credo quia absurdum est.




From shane@castlepoint.net  Thu Nov 15 20:11:04 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 8A0D021F84F8 for <grow@ietfa.amsl.com>; Thu, 15 Nov 2012 20:11:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.322
X-Spam-Level: 
X-Spam-Status: No, score=-0.322 tagged_above=-999 required=5 tests=[AWL=0.115,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611,  RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Hh+zZPc5k5My for <grow@ietfa.amsl.com>; Thu, 15 Nov 2012 20:11:04 -0800 (PST)
Received: from mail.friendswithtools.org (unknown [64.78.239.70]) by ietfa.amsl.com (Postfix) with ESMTP id E8AEE21F84F5 for <grow@ietf.org>; Thu, 15 Nov 2012 20:11:03 -0800 (PST)
Received: from dspam (unknown [127.0.0.1]) by mail.friendswithtools.org (Postfix) with SMTP id 2B0312169 for <grow@ietf.org>; Fri, 16 Nov 2012 04:11:03 +0000 (UTC)
Received: from mbp.castlepoint.net (174-29-211-99.hlrn.qwest.net [174.29.211.99]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mail.friendswithtools.org (Postfix) with ESMTPSA id 453EC2156; Thu, 15 Nov 2012 21:11:00 -0700 (MST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: Shane Amante <shane@castlepoint.net>
In-Reply-To: <CAL9jLabgy7f5ZkaqfGGaHkRodLfpWP=8yNcTm-4xFTgjtFVsiA@mail.gmail.com>
Date: Thu, 15 Nov 2012 21:10:59 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <58638A07-2914-4BCD-96FE-A850F2B16C1E@castlepoint.net>
References: <CAL9jLaagY5bBe_8eRST8noEp2-o00Zkm2Qc59Ys7pak++EPGNw@mail.gmail.com> <C8308656-31A2-4475-85FD-0DF07734A8B1@castlepoint.net> <CAL9jLabgy7f5ZkaqfGGaHkRodLfpWP=8yNcTm-4xFTgjtFVsiA@mail.gmail.com>
To: Christopher Morrow <christopher.morrow@gmail.com>
X-Mailer: Apple Mail (2.1499)
X-DSPAM-Result: Innocent
X-DSPAM-Processed: Thu Nov 15 21:11:03 2012
X-DSPAM-Confidence: 1.0000
X-DSPAM-Improbability: 1 in 98689409 chance of being spam
X-DSPAM-Probability: 0.0023
X-DSPAM-Signature: 50a5bcd7199631785921093
X-DSPAM-Factors: 27, poorly+chosen, 0.40000, remain+#+minded, 0.40000, remain+#+minded, 0.40000, would+#+#+use, 0.40000, answer+#+a, 0.40000, what+happens, 0.40000, directions+#+#+FWIW, 0.40000, to+#+#+#+or, 0.40000, takes+#+look, 0.40000, and+IDR, 0.40000, 3+#+4, 0.40000, they+#+#+to, 0.40000, situations+#+#+#+'route, 0.40000, and+came, 0.40000, came+#+a, 0.40000, presently+#+would, 0.40000, a+#+#+#+action, 0.40000, is+narrowly, 0.40000, apologies+#+#+#+bit, 0.40000, '+#+#+that, 0.40000, I'd+like, 0.40000, T+#+like, 0.40000, 1+#+#+#+answer, 0.40000, leaks'+#+also, 0.40000, repeatedly+#+#+Internet, 0.40000, also+#+#+#+of, 0.40000, rushed+#+#+message, 0.40000
Cc: "grow@ietf.org grow@ietf.org" <grow@ietf.org>, draft-foo-sidr-simple-leak-attack-bgpsec-no-help@tools.ietf.org, grow-ads@tools.ietf.org, grow-chairs@tools.ietf.org
Subject: Re: [GROW] RouteLeaks - problem or not?
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, 16 Nov 2012 04:11:04 -0000

Chris,

On Nov 14, 2012, at 10:27 PM, Christopher Morrow =
<christopher.morrow@gmail.com> wrote:
> Shane,
>=20
> See below.
>=20
> On Wed, Nov 14, 2012 at 11:33 PM, Shane Amante <shane@castlepoint.net> =
wrote:
>> Chris,
>>=20
>> See below.
>>=20
>> On Nov 14, 2012, at 3:18 PM, Christopher Morrow =
<christopher.morrow@gmail.com> wrote:
>> [--snip--]
>>> To date there is a draft which discusses route leaks:
>>> =
<http://tools.ietf.org/html/draft-foo-sidr-simple-leak-attack-bgpsec-no-he=
lp-02>
>>>=20
>>> where the authors have attempted to describe one (or many possible)
>>> situations which are called 'route leaks'. They also attempt to
>>> outline security issues which are follow-on effects of the situation
>>> described.
>>>=20
>>> SIDR attempted to look at route-leaks and came up a bit stymied, =
they
>>> asked IDR for some assistance with the issue, IDR pushed back to =
GROW
>>> to decide:
>>> 1) What is a 'route leak' (perhaps the above draft identifies one
>>> examplar to be used in that definition)
>>=20
>> See aforementioned draft.  It's the most _concise_ definition of the =
problem, as observed repeatedly in the Internet.
>>=20
>>=20
>>> 2) Are 'route leaks' a problem that Operations folks care about
>>=20
>> Yes!
>>=20
>>=20
>>> 3) Should IDR (or the IETF proper) address 'route leaks' with some
>>> form(s) of fix action.
>>=20
>> WRT "Should IDR" ... that's like Henry Ford asking what color "Model =
T" I'd like, right?  Look, no offense to the folks in IDR :-), but as =
with every other WG their present charter is narrowly defined to =
'enhancements to BGP'.  I would hope that _when_the_time_comes_ we =
remain open-minded about conducting a thorough evaluation of the =
solution space, before deciding to further refine one, or more, of those =
solutions to a standard, or set of standards.  So, presently, I would =
not be in favor of exclusively asking IDR to fix 'route leaks', given =
the concerns I've raised above.
>>=20
>=20
> apologies, I was a bit rushed in my message (and I note my first
> question was poorly chosen, as well) but I had meant to say that the
> placement of a  solution doesn't have to be in bgp (so doesn't have to
> involve IDR), if the WG here takes a look at sees other directions to
> go.
>=20
>> FWIW, I'm not clear on what you're proposing with "the IETF proper" =
... so I can't say "yes" to that option either.
>>=20
>=20
> 'should the ietf care about this problem, and spend resources
> attempting to provide solutions?'

Yes.


> is that better? I'm really asking whether or not there is a problem
> and if we (ietf in general) can get a solution (or even the
> requirements for a solution?) defined...

Yes, there is a (big) operational problem wrt route-leaks.

Yes, we (IETF in general) should work toward a solution.  As I stated =
previously, I hope we remain open-minded as to the solution space and do =
not pigeon-hole ourselves into thinking that one must exist inside BGP, =
either solely or at all.

-shane



> -chris
>=20
>>=20
>>> The end result of the above 3 steps is to push back into IDR one of
>>> two action requests:
>>> 1) "Yes, route leaks are a problem, please fix them."
>>>    or
>>> 2) "No, route leaks are not a problem, take no action."
>>>=20
>>> If #1 above is the answer, and IDR decides that changes to the BGP
>>> protocol are warranted (or are a possible solution to the problem)
>>> then SIDR has agreed to do what they can to 'secure' the bits
>>> added/changed/used in that endeavor.
>>=20
>> Dare I ask what happens if IDR decides they do not have an answer?
>>=20
>>=20
>>> Could we have some discussion on-list about this problem, and some
>>> discussion about whether or not the draft referenced above fits the
>>> definition we would like to use for 'route leak'?
>>=20
>> Um, yes, but then again I'm a co-author, so clearly you should take =
this answer with a healthy dose of salt.  :-)
>>=20
>>=20
>>> I would also like
>>> the authors of the draft to decide where they would like to take =
their
>>> draft:
>>>  1) SIDR
>>>  2) IDR
>>>  3) GROW
>>>  4) other
>>=20
>> IMO, since you're asking GROW, the answer should hopefully present =
itself.  :-)
>>=20
>> -shane
>=20



From christopher.morrow@gmail.com  Thu Nov 15 20:46:33 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 31D2421E8037 for <grow@ietfa.amsl.com>; Thu, 15 Nov 2012 20:46:33 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5KQ7wif2FRgT for <grow@ietfa.amsl.com>; Thu, 15 Nov 2012 20:46:32 -0800 (PST)
Received: from mail-ee0-f44.google.com (mail-ee0-f44.google.com [74.125.83.44]) by ietfa.amsl.com (Postfix) with ESMTP id 698C321E802E for <grow@ietf.org>; Thu, 15 Nov 2012 20:46:32 -0800 (PST)
Received: by mail-ee0-f44.google.com with SMTP id b47so1514065eek.31 for <grow@ietf.org>; Thu, 15 Nov 2012 20:46:31 -0800 (PST)
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; bh=nds0rI2nfcce/YjnzEl1+Zf0ODJYUvvYfTTONIRxkew=; b=F5xAL092WE7KR3tLHgjreSqrlzVxENmpfNLpN3sAn9jkuqzVPFKhADNFPT1BDUP8+s bvtNlOCbkQTHYEDtphnonVbfynp7UCE6HEgBkwvJFg76+D9D3Fdx+wDPjNGYk2p5/lKy 627DNPtXwS4fBLacUcCPUv6Gdhitf3tMv2fOhGkpratrbq8+Wb5P8jB+f5qQ4MrF8Z6a pgj15u1nQxM1ZiDNCFnMlgONhs2IcarJjSY/EqGGFTEXBwmIk1ZBngd9ASmS01hPmmCU OIVayiaXGoQt770x5XsvZK8UEeay98sTN5m1omIJke/eu8yEPYfBol3LEpnHlgl7HfZ1 fTcg==
MIME-Version: 1.0
Received: by 10.14.175.71 with SMTP id y47mr10161000eel.36.1353041191582; Thu, 15 Nov 2012 20:46:31 -0800 (PST)
Received: by 10.223.177.71 with HTTP; Thu, 15 Nov 2012 20:46:31 -0800 (PST)
In-Reply-To: <58638A07-2914-4BCD-96FE-A850F2B16C1E@castlepoint.net>
References: <CAL9jLaagY5bBe_8eRST8noEp2-o00Zkm2Qc59Ys7pak++EPGNw@mail.gmail.com> <C8308656-31A2-4475-85FD-0DF07734A8B1@castlepoint.net> <CAL9jLabgy7f5ZkaqfGGaHkRodLfpWP=8yNcTm-4xFTgjtFVsiA@mail.gmail.com> <58638A07-2914-4BCD-96FE-A850F2B16C1E@castlepoint.net>
Date: Thu, 15 Nov 2012 23:46:31 -0500
Message-ID: <CAL9jLaaRz=MOTdo=O4PZxKFn9FkL3_FGG-ugpa2FoB-Vbp5mUg@mail.gmail.com>
From: Christopher Morrow <christopher.morrow@gmail.com>
To: Shane Amante <shane@castlepoint.net>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "grow@ietf.org grow@ietf.org" <grow@ietf.org>, draft-foo-sidr-simple-leak-attack-bgpsec-no-help@tools.ietf.org, grow-ads@tools.ietf.org, grow-chairs@tools.ietf.org
Subject: Re: [GROW] RouteLeaks - problem or not?
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, 16 Nov 2012 04:46:33 -0000

On Thu, Nov 15, 2012 at 11:10 PM, Shane Amante <shane@castlepoint.net> wrote:

>> is that better? I'm really asking whether or not there is a problem
>> and if we (ietf in general) can get a solution (or even the
>> requirements for a solution?) defined...
>
> Yes, there is a (big) operational problem wrt route-leaks.

it'd be good to outline that as well in the document... often the
'mitm' problem is brought up, but honestly there are probably more
cases of:
  1) suboptimal routing (why am I routing through Chile to get to my
next-door-asn?)
  2) traffic loss (via too-small-pipes + congestion)
  3) link costs (lookie at the transit pipe being full instead of the
other one!)

that happen and are simpler to show than other issues.

>
> Yes, we (IETF in general) should work toward a solution.  As I stated previously, I hope we remain open-minded as to the solution space and do not pigeon-hole ourselves into thinking that one must exist inside BGP, either solely or at all.
>
> -shane
>
>
>
>> -chris
>>
>>>
>>>> The end result of the above 3 steps is to push back into IDR one of
>>>> two action requests:
>>>> 1) "Yes, route leaks are a problem, please fix them."
>>>>    or
>>>> 2) "No, route leaks are not a problem, take no action."
>>>>
>>>> If #1 above is the answer, and IDR decides that changes to the BGP
>>>> protocol are warranted (or are a possible solution to the problem)
>>>> then SIDR has agreed to do what they can to 'secure' the bits
>>>> added/changed/used in that endeavor.
>>>
>>> Dare I ask what happens if IDR decides they do not have an answer?
>>>
>>>
>>>> Could we have some discussion on-list about this problem, and some
>>>> discussion about whether or not the draft referenced above fits the
>>>> definition we would like to use for 'route leak'?
>>>
>>> Um, yes, but then again I'm a co-author, so clearly you should take this answer with a healthy dose of salt.  :-)
>>>
>>>
>>>> I would also like
>>>> the authors of the draft to decide where they would like to take their
>>>> draft:
>>>>  1) SIDR
>>>>  2) IDR
>>>>  3) GROW
>>>>  4) other
>>>
>>> IMO, since you're asking GROW, the answer should hopefully present itself.  :-)
>>>
>>> -shane
>>
>
>

From rbonica@juniper.net  Fri Nov 16 09:43:36 2012
Return-Path: <rbonica@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 1FD0921F850E for <grow@ietfa.amsl.com>; Fri, 16 Nov 2012 09:43:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.316
X-Spam-Level: 
X-Spam-Status: No, score=-100.316 tagged_above=-999 required=5 tests=[AWL=-1.991, BAYES_00=-2.599, CN_BODY_35=0.339, J_CHICKENPOX_13=0.6, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-4, UNRESOLVED_TEMPLATE=3.132, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CLdxZoJ4V07N for <grow@ietfa.amsl.com>; Fri, 16 Nov 2012 09:43:35 -0800 (PST)
Received: from exprod7og113.obsmtp.com (exprod7og113.obsmtp.com [64.18.2.179]) by ietfa.amsl.com (Postfix) with ESMTP id D7E3521F84E4 for <grow@ietf.org>; Fri, 16 Nov 2012 09:43:34 -0800 (PST)
Received: from P-EMHUB03-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob113.postini.com ([64.18.6.12]) with SMTP ID DSNKUKZ7RqCbd3FYzIMjgEWo4E/FdQ5A3e1K@postini.com; Fri, 16 Nov 2012 09:43:34 PST
Received: from P-CLDFE02-HQ.jnpr.net (172.24.192.60) by P-EMHUB03-HQ.jnpr.net (172.24.192.37) with Microsoft SMTP Server (TLS) id 8.3.213.0; Fri, 16 Nov 2012 09:41:29 -0800
Received: from o365mail.juniper.net (207.17.137.149) by o365mail.juniper.net (172.24.192.60) with Microsoft SMTP Server id 14.1.355.2; Fri, 16 Nov 2012 09:41:29 -0800
Received: from tx2outboundpool.messaging.microsoft.com (65.55.88.11) by o365mail.juniper.net (207.17.137.149) with Microsoft SMTP Server (TLS) id 14.1.355.2; Fri, 16 Nov 2012 09:43:17 -0800
Received: from mail9-tx2-R.bigfish.com (10.9.14.239) by TX2EHSOBE008.bigfish.com (10.9.40.28) with Microsoft SMTP Server id 14.1.225.23; Fri, 16 Nov 2012 17:41:02 +0000
Received: from mail9-tx2 (localhost [127.0.0.1])	by mail9-tx2-R.bigfish.com (Postfix) with ESMTP id 88FF93401B8	for <grow@ietf.org.FOPE.CONNECTOR.OVERRIDE>; Fri, 16 Nov 2012 17:41:02 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.245.197; KIP:(null); UIP:(null); (null); H:CH1PRD0511HT001.namprd05.prod.outlook.com; R:internal; EFV:INT
X-SpamScore: -28
X-BigFish: PS-28(zz9371Ic89bh103dK542M1432I1a09Jzz1de0h1202h1d1ah1d2ahzz1033IL8275bh8275dhz2dh2a8h668h839h941hd25hf0ah1269h1288h12a5h12a9h12bdh12e1h137ah13b6h1441h1504h1537h153bh162dh1631h15d0l1155h)
Received: from mail9-tx2 (localhost.localdomain [127.0.0.1]) by mail9-tx2 (MessageSwitch) id 1353087660758209_5048; Fri, 16 Nov 2012 17:41:00 +0000 (UTC)
Received: from TX2EHSMHS024.bigfish.com (unknown [10.9.14.235])	by mail9-tx2.bigfish.com (Postfix) with ESMTP id B50EFC004E; Fri, 16 Nov 2012 17:41:00 +0000 (UTC)
Received: from CH1PRD0511HT001.namprd05.prod.outlook.com (157.56.245.197) by TX2EHSMHS024.bigfish.com (10.9.99.124) with Microsoft SMTP Server (TLS) id 14.1.225.23; Fri, 16 Nov 2012 17:41:00 +0000
Received: from CH1PRD0511MB418.namprd05.prod.outlook.com ([169.254.1.251]) by CH1PRD0511HT001.namprd05.prod.outlook.com ([10.255.159.36]) with mapi id 14.16.0233.002; Fri, 16 Nov 2012 17:40:55 +0000
From: Ronald Bonica <rbonica@juniper.net>
To: Xuxiaohu <xuxiaohu@huawei.com>
Thread-Topic: Wake up two sleeping VA drafts?//: Last Call comments on draft-ietf-l3vpn-virtual-hub 
Thread-Index: AQHNvfsEMb5fV5gac0WMrTIRrVsjCZfhshUggAkC5zCAAAJnMIACDPaQ
Date: Fri, 16 Nov 2012 17:40:55 +0000
Message-ID: <2CF4CB03E2AA464BA0982EC92A02CE2506BD06@CH1PRD0511MB418.namprd05.prod.outlook.com>
References: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0757029A@szxeml525-mbx.china.huawei.com> <2CF4CB03E2AA464BA0982EC92A02CE250652EC@CH1PRD0511MB418.namprd05.prod.outlook.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE075718E3@szxeml525-mbx.china.huawei.com>
In-Reply-To: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE075718E3@szxeml525-mbx.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [66.129.232.2]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
X-FOPE-CONNECTOR: Id%12219$Dn%HUAWEI.COM$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net
X-FOPE-CONNECTOR: Id%12219$Dn%IETF.ORG$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net
Cc: "grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] Wake up two sleeping VA drafts?//: Last Call comments on draft-ietf-l3vpn-virtual-hub
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, 16 Nov 2012 17:43:36 -0000

WGlhb2h1LA0KDQpTaW5jZSB0aGVzZSBkcmFmdHMgaGF2ZSBiZWVuIGRvcm1hbnQgZm9yIHNvIGxv
bmcsIGFuZCBzaW5jZSB0aGVyZSB3YXMgc28gbGl0dGxlIGRpc2N1c3Npb24gb2YgdGhlbSB3aGVu
IHRoZXkgd2VyZSBhY3RpdmUsIHdlIHNob3VsZCBkZXRlcm1pbmUgd2hldGhlciB0aGVyZSBpcyBj
dXJyZW50bHkgYW55IGludGVyZXN0IGluIHRoZW0uDQoNCkkgaW52aXRlIHlvdSB0byByYWlzZSB0
aGF0IHF1ZXN0aW9uIG9uIHRoaXMgbWFpbGluZyBsaXN0Lg0KDQogICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgUm9uDQoNCg0KPiAtLS0tLU9yaWdpbmFsIE1lc3Nh
Z2UtLS0tLQ0KPiBGcm9tOiBYdXhpYW9odSBbbWFpbHRvOnh1eGlhb2h1QGh1YXdlaS5jb21dDQo+
IFNlbnQ6IFRodXJzZGF5LCBOb3ZlbWJlciAxNSwgMjAxMiA1OjE0IEFNDQo+IFRvOiBSb25hbGQg
Qm9uaWNhDQo+IENjOiBncm93QGlldGYub3JnDQo+IFN1YmplY3Q6IHJlOiBXYWtlIHVwIHR3byBz
bGVlcGluZyBWQSBkcmFmdHM/Ly86IExhc3QgQ2FsbCBjb21tZW50cyBvbg0KPiBkcmFmdC1pZXRm
LWwzdnBuLXZpcnR1YWwtaHViDQo+IA0KPiA+IC0tLS0t08q8/tStvP4tLS0tLQ0KPiA+ILeivP7I
yzogWHV4aWFvaHUNCj4gPiC3osvNyrG85DogMjAxMsTqMTHUwjE1yNUgMTg6MTANCj4gPiDK1bz+
yMs6ICdSb25hbGQgQm9uaWNhJw0KPiA+ILOty806IGdyb3dAaWV0Zi5vcmcNCj4gPiDW98ziOiBy
ZTogV2FrZSB1cCB0d28gc2xlZXBpbmcgVkEgZHJhZnRzPy8vOiBMYXN0IENhbGwgY29tbWVudHMg
b24NCj4gPiBkcmFmdC1pZXRmLWwzdnBuLXZpcnR1YWwtaHViDQo+ID4NCj4gPiBIaSBSb24sDQo+
ID4NCj4gPiBEaWQgdGhlIFdHIGFkb3B0aW9uIGFuZCB0aGUgSUVTRyBzdWJtaXNzaW9uIG9mIHRo
ZXNlIHRocmVlIGRyYWZ0cw0KPiA+IGFscmVhZHkgZGVtb25zdHJhdGUgdGhlIFdHIHJvdWdoIGNv
bnNlbnN1cz8NCj4gDQo+IFNvcnJ5LCB0aGUgYWJvdmUgc2hvdWxkIGJlOiBEaWRuJ3QgdGhlIFdH
IGFkb3B0aW9uIGFuZCB0aGUgSUVTRw0KPiBzdWJtaXNzaW9uIG9mIHRoZXNlIHRocmVlIGRyYWZ0
cyBhbHJlYWR5IGRlbW9uc3RyYXRlIHRoZSBXRyByb3VnaA0KPiBjb25zZW5zdXM/DQo+IA0KPiA+
IEJlc3QgcmVnYXJkcywNCj4gPiBYaWFvaHUNCj4gPg0KPiA+ID4gLS0tLS3Tyrz+1K28/i0tLS0t
DQo+ID4gPiC3orz+yMs6IFJvbmFsZCBCb25pY2EgW21haWx0bzpyYm9uaWNhQGp1bmlwZXIubmV0
XQ0KPiA+ID4gt6LLzcqxvOQ6IDIwMTLE6jEx1MIxMMjVIDA6MjgNCj4gPiA+IMrVvP7IyzogWHV4
aWFvaHUNCj4gPiA+ILOty806IGdyb3dAaWV0Zi5vcmcNCj4gPiA+INb3zOI6IFJFOiBXYWtlIHVw
IHR3byBzbGVlcGluZyBWQSBkcmFmdHM/Ly86IExhc3QgQ2FsbCBjb21tZW50cyBvbg0KPiA+ID4g
ZHJhZnQtaWV0Zi1sM3Zwbi12aXJ0dWFsLWh1Yg0KPiA+ID4NCj4gPiA+IEhvdyBkbyBmb2xrcyBv
biB0aGUgbGlzdCBmZWVsPw0KPiA+ID4NCj4gPiA+ICAgICAgICAgICAgICAgICAgICAgICAgICBS
b24NCj4gPiA+DQo+ID4gPg0KPiA+ID4gPiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiA+
ID4gPiBGcm9tOiBYdXhpYW9odSBbbWFpbHRvOnh1eGlhb2h1QGh1YXdlaS5jb21dDQo+ID4gPiA+
IFNlbnQ6IFRodXJzZGF5LCBOb3ZlbWJlciAwOCwgMjAxMiA0OjUzIFBNDQo+ID4gPiA+IFRvOiBS
b25hbGQgQm9uaWNhDQo+ID4gPiA+IENjOiBncm93QGlldGYub3JnDQo+ID4gPiA+IFN1YmplY3Q6
IFdha2UgdXAgdHdvIHNsZWVwaW5nIFZBIGRyYWZ0cz8vLzogTGFzdCBDYWxsIGNvbW1lbnRzIG9u
DQo+ID4gPiA+IGRyYWZ0LWlldGYtbDN2cG4tdmlydHVhbC1odWINCj4gPiA+ID4NCj4gPiA+ID4g
SGkgUm9uYWxkLA0KPiA+ID4gPg0KPiA+ID4gPiBJZiBJIHJlbWVtYmVyZWQgY29ycmVjdGx5LCB5
b3UgaGF2ZSBzYWlkLCBkdXJpbmcgdGhlIFdHIGxhc3QgY2FsbA0KPiA+ID4gPiBvZiB0aHJlZSBW
QSBkcmFmdCwgdGhhdCB5b3UgbWF5IHJlY29uc2lkZXIgeW91ciBhdHRpdHVkZXMgdG93YXJkcw0K
PiA+ID4gPiB0aGUgdHdvIG9mIHRocmVlIFZBIGRyYWZ0cyAoZHJhZnQtaWV0Zi1ncm93LXZhIGFu
ZA0KPiA+ID4gPiBkcmFmdC1pZXRmLWdyb3ctdmEtYXV0bykgaW4gY2FzZSB0aGVyZSB3ZXJlIGFu
eSBpbnRlcmVzdHMgZnJvbQ0KPiBTUHMgb24gdGhlIEZJQiBhZ2dyZWdhdGlvbi4NCj4gPiA+ID4N
Cj4gPiA+ID4gSSBvY2Nhc2lvbmFsbHkgbm90aWNlZCB0aGF0IGRyYWZ0LWlldGYtbDN2cG4tdmly
dHVhbC1odWIgaGFzIGp1c3QNCj4gPiA+ID4gZGVjcmliZWQgYSB1c2UgY2FzZSBvZiBGSUIgYWdn
cmVnYXRpb24gIGFuZCBhIHBvc3NpYmxlIEZJQg0KPiA+ID4gPiBhZ2dyZWdhdGlvbiBhcHByb2Fj
aCB3aGljaCBzZWVtcyBtdWNoIHNpbWlsYXIgdG8gdGhlIFZBIGFwcHJvYWNoDQo+ID4gPiA+IChz
ZWUgdGhlIGZvbGxvd2luZyB0ZXh0IHF1b3RlZCBmcm9tIHRoYXQgZHJhZnQpLiBZb3UgbWF5IGhh
dmUNCj4gPiA+ID4gbm90aWNlZCB0aGF0IG1vc3Qgb2YgdGhlIGNvLSBhdXRob3JzIG9mIHRoaXMg
ZHJhZnQgYXJlIGZyb20gU1BzLg0KPiA+ID4gPg0KPiA+ID4gPiBJbiBhZGRpdGlvbiwgdGhlcmUg
YXJlIG1hbnkgY29uY2VybnMgd2l0aCB0aGUgZm9yd2FyZGluZyB0YWJsZQ0KPiA+ID4gPiBzY2Fs
YWJpbGl0eSBpc3N1ZXMgaW4gdGhlIG11bHRpLXRlbmFudCBjbG91ZCBkYXRhIGNlbnRlciBuZXR3
b3JrDQo+ID4gPiA+IGVudmlyb25tZW50cyB0aGF0IGhhdmUgYmVlbiBleHByZXNzZWQgaW4gc2V2
ZXJhbCBOVm8zIHJlbGF0ZWQNCj4gZHJhZnRzLg0KPiA+ID4gPg0KPiA+ID4gPiBIZW5jZSBJIHdv
bmRlciB3aGV0aGVyIHlvdSBjb3VsZCBwbGVhc2UgcmVjb25zaWRlciB5b3VyIGF0dGl0dWRlcw0K
PiA+ID4gPiB0b3dhcmRzIHRoZSB0d28gb2YgdGhyZWUgVkEgcmVsYXRlZCBkcmFmdHMuIE1hbnkg
dGhhbmtzIQ0KPiA+ID4gPg0KPiA+ID4gPg0KPiA+ID4gPiAqKioqKioqKioqKioqKioqKioqKioq
KioqKg0KPiA+ID4gPiA5LiBGdXJ0aGVyIHJlZmluZW1lbnRzDQo+ID4gPiA+ICAgIEluIHNvbWUg
Y2FzZXMgYSBWUE4gY3VzdG9tZXIgbWF5IG5vdCB3YW50IHRvIHJlbHkgc29sZWx5IG9uIGFuDQo+
IChJUCkNCj4gPiA+ID4gICAgZGVmYXVsdCByb3V0ZSBiZWluZyBhZHZlcnRpc2VkIGZyb20gYSBW
LXNwb2tlIHRvIGEgQ0UsIGJ1dCBtYXkNCj4gd2FudA0KPiA+ID4gPiAgICBDRXMgdG8gcmVjZWl2
ZSBhbGwgdGhlIFZQTiByb3V0ZXMgKGUuZy4sIGZvciB0aGUgcHVycG9zZSBvZg0KPiBmYXN0ZXIN
Cj4gPiA+ID4gICAgZGV0ZWN0aW9uIG9mIFZQTiBjb25uZWN0aXZpdHkgZmFpbHVyZXMsIGFuZCBh
Y3RpdmF0aW5nIHNvbWUNCj4gYmFja3VwDQo+ID4gPiA+ICAgIGNvbm5lY3Rpdml0eSkuDQo+ID4g
PiA+ICAgIEluIHRoaXMgY2FzZSBvbmUgcG9zc2libGUgYXBwcm9hY2ggd291bGQgYmUgdG8gaW5z
dGFsbCBpbiB0aGUNCj4gVi0NCj4gPiA+ID4gICAgc3Bva2UncyBkYXRhIHBsYW5lIG9ubHkgdGhl
IGRlZmF1bHQgcm91dGUgKGZvbGxvd2luZyB0aGUNCj4gVmlydHVhbCBIdWINCj4gPiA+ID4gICAg
YW5kIFNwb2tlIG1vZGVsLCBhcyBkZXNjcmliZWQgYWJvdmUpLCBidXQga2VlcCBhbGwgdGhlIFZQ
Ti1JUA0KPiByb3V0ZXMNCj4gPiA+ID4gICAgaW4gdGhlIFYtc3Bva2UncyBjb250cm9sIHBsYW5l
IChhbmQgdGh1cyBiZWluZyBhYmxlIHRvDQo+IGFkdmVydGlzZQ0KPiA+ID4gPiAgICB0aGVzZSBy
b3V0ZXMgZnJvbSB0aGUgVi1zcG9rZSB0byB0aGUgQ0VzKS4gIEdyYW50ZWQsIHRoaXMNCj4gd291
bGQgbm90DQo+ID4gPiA+ICAgIGNoYW5nZSBjb250cm9sIHBsYW5lIHJlc291cmNlIGNvbnN1bXB0
aW9uLCBidXQgd291bGQNCj4gKHNpZ25pZmljYW50bHkpDQo+ID4gPiA+ICAgIHJlZHVjZSByZXNv
dXJjZSBjb25zdW1wdGlvbiBvbiB0aGUgZGF0YSBwbGFuZS4NCj4gPiA+ID4gKioqKioqKioqKioq
KioqKioqKioqKioqKioqKioNCj4gPiA+ID4NCj4gPiA+ID4gQmVzdCByZWdhcmRzLA0KPiA+ID4g
PiBYaWFvaHUNCj4gPiA+ID4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
Xw0KPiA+ID4gPiC3orz+yMs6IGwzdnBuLWJvdW5jZXNAaWV0Zi5vcmcgW2wzdnBuLWJvdW5jZXNA
aWV0Zi5vcmddILT6se0gWWFrb3YNCj4gPiA+ID4gUmVraHRlciBbeWFrb3ZAanVuaXBlci5uZXRd
DQo+ID4gPiA+ILeiy83KsbzkOiAyMDEyxOoxMdTCOMjVIDIzOjE3DQo+ID4gPiA+ILW9OiBlcm9z
ZW5AY2lzY28uY29tDQo+ID4gPiA+IENjOiBMM1ZQTg0KPiA+ID4gPiDW98ziOiBSZTogTGFzdCBD
YWxsIGNvbW1lbnRzIG9uIGRyYWZ0LWlldGYtbDN2cG4tdmlydHVhbC1odWINCj4gPiA+ID4NCj4g
PiA+ID4gRXJpYywNCj4gPiA+ID4NCj4gPiA+ID4gPiBJIGhhdmUgYSBudW1iZXIgb2YgY29tbWVu
dHMgb24gdGhlIHZpcnR1YWwtaHViIGRyYWZ0LiAgU29tZSBhcmUNCj4gPiA+ID4gPiBtaW5vciBh
bmQvb3IgZWRpdG9yaWFsLCBidXQgYSBudW1iZXIgYXJlIG1vcmUgc3Vic3RhbnRpYWwuICBJDQo+
ID4gPiA+ID4gdGhpbmsgdGhlc2UgY29tbWVudHMgbmVlZCB0byBiZSBhZGRyZXNzZWQgYmVmb3Jl
IHRoZSBkcmFmdCBpcw0KPiA+ID4gPiA+IHN1Ym1pdHRlZCBmb3INCj4gPiA+ID4gcHVibGljYXRp
b24uDQo+ID4gPiA+ID4NCj4gPiA+ID4gPiBJJ3ZlIHBsYWNlZCBhIGxvdCBvZiBjb21tZW50cyBp
bi1saW5lLCBidXQgbGV0IG1lIHN1bW1hcml6ZQ0KPiB3aGF0DQo+ID4gPiA+ID4gSSB0aGluayBh
cmUgdGhlIG1ham9yIGlzc3VlczoNCj4gPiA+ID4NCj4gPiA+ID4gSSBhbSBpbiB0aGUgcHJvY2Vz
cyBvZiBhZGRyZXNzaW5nIHlvdXIgY29tbWVudHMuIEluIHRoaXMgZS1tYWlsDQo+ID4gPiA+IEkn
ZCBsaWtlIHRvIGZvY3VzIG9uIG9uZSBwYXJ0aWN1bGFyIG9uZToNCj4gPiA+ID4NCj4gPiA+ID4g
PiBFcmljPiBMZXQncyBjb25zaWRlciB0aGUgY2FzZSB3aGVyZSB0aGUgc291cmNlIGlzIGF0IGEg
c2l0ZQ0KPiA+ID4gPiA+IEVyaWM+IGF0dGFjaGVkIHRvIFYtaHViMi4gIFYtaHViMSB3aWxsIHJl
Y2VpdmUgYW4gUy1QTVNJIEEtRA0KPiA+ID4gPiA+IEVyaWM+IHJvdXRlIG1hdGNoaW5nDQo+ID4g
PiA+ID4gRXJpYz4gKFMsRykgZnJvbSBWLWh1YjIuICBWLWh1YjEgdGhlbiBtb2RpZmllcyB0aGlz
IEEtRCByb3V0ZQ0KPiA+ID4gPiA+IEVyaWM+IGFuZCBmb3J3YXJkcyBpdCB0byBWLXNwb2tlMS4g
IFYtaHViMSBjb3VsZCB1c2UgdGhpcyByb3V0ZQ0KPiA+ID4gPiA+IEVyaWM+IHRvIGlkZW50aWZ5
IHRoZSBQLXR1bm5lbCBvcmlnaW5hdGluZyBhdCBWLWh1YjIsIHRoZXJlYnkNCj4gPiA+ID4gaW5z
dHJ1Y3RpbmcNCj4gPiA+ID4gPiBFcmljPiBWLXNwb2tlMSB0byBqb2luIFYtaHViMidzIHR1bm5l
bCBkaXJlY3RseS4gIFRoZW4gVi1odWIxDQo+ID4gPiA+ID4gRXJpYz4gd291bGQgbm90IGJlIGlu
IHRoZSBkYXRhIHBhdGggZnJvbSBTIHRvIFIsIGJ1dCBpdCB3b3VsZA0KPiA+ID4gPiA+IEVyaWM+
IHBhcnRpY2lwYXRlDQo+ID4gPiA+IGluDQo+ID4gPiA+ID4gRXJpYz4gdGhlIGNvbnRyb2wgcGxh
bmUuICBXb3VsZG4ndCB0aGlzIG1lZXQgYWxsIHRoZQ0KPiA+ID4gPiA+IEVyaWM+IHJlcXVpcmVt
ZW50cyBvZiB0aGUgVi1odWIvVi1zcG9rZSBhcmNoaXRlY3R1cmUsIHdoaWxlDQo+ID4gPiA+ID4g
RXJpYz4gcHJvZHVjaW5nIGEgbW9yZSBvcHRpbWFsIHBhdGggZm9yIG11bHRpY2FzdCBkYXRhLCBh
bmQNCj4gPiA+ID4gPiBFcmljPiBlbGltaW5hdGluZyB0aGUgbmVlZCB0byBoYXZlIHRoZQ0KPiA+
ID4gPiBWLWh1YnMgc3BsaWNlIHRvZ2V0aGVyIGFueSBQLXR1bm5lbHM/DQo+ID4gPiA+ID4NCj4g
PiA+ID4gPiBFcmljPiBXYXMgYW55IGNvbnNpZGVyYXRpb24gZ2l2ZW4gdG8gc3VjaCBhbiBhbHRl
cm5hdGl2ZT8NCj4gPiA+ID4NCj4gPiA+ID4gUGxlYXNlIG5vdGUgdGhhdCB0aGUgcHJvY2VkdXJl
cyBzcGVjaWZpZWQgaW4gdGhlIGRyYWZ0IGFzc3VtZSB0aGUNCj4gPiA+ID4gYWJpbGl0eSB0byBw
ZXJmb3JtIHNlbmRlci1iYXNlZCBSUEYsIGFzIHNwZWNpZmllZCBpbiA5LjEuMSBvZg0KPiByZmM2
NTEzLg0KPiA+ID4gPiBHaXZlbiB0aGF0LCBpZiBvbmUgd291bGQgZm9sbG93IHdoYXQgeW91IG91
dGxpbmVkIGFib3ZlLCBjb3VsZA0KPiB5b3UNCj4gPiA+ID4gcG9pbnQgbWUgdG8gdGhlIHNwZWNp
ZmljIHRleHQgaW4gOS4xLjEgdGhhdCB3b3VsZCBlbmFibGUgVi1zcG9rZTENCj4gPiA+ID4gdG8g
ZGV0ZXJtaW5lIHRoYXQgZnJvbSBpdHMgb3duIHBlcnNwZWN0aXZlIHRoZSBVTUggZm9yIChDLVMs
IEMtRykNCj4gPiA+ID4gaXMgVi0NCj4gPiA+ID4gaHViMSA/DQo+ID4gPiA+DQo+ID4gPiA+IEZ1
cnRoZXJtb3JlLCB5b3VyIG91dGxpbmUgYWJvdmUgdGFsa3MgYWJvdXQgUy1QTVNJIEEtRCByb3V0
ZS4gSG93DQo+ID4gPiA+IHdvdWxkIGl0IHdvcmsgZm9yIEktUE1TSSBBLUQgcm91dGVzID8NCj4g
PiA+ID4NCj4gPiA+ID4gWWFrb3YuDQo=


From warren@kumari.net  Fri Nov 16 18:18: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 BEB5B21F84CE for <grow@ietfa.amsl.com>; Fri, 16 Nov 2012 18:18:52 -0800 (PST)
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=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xC-oqxUyE2i2 for <grow@ietfa.amsl.com>; Fri, 16 Nov 2012 18:18:52 -0800 (PST)
Received: from vimes.kumari.net (smtp1.kumari.net [204.194.22.1]) by ietfa.amsl.com (Postfix) with ESMTP id 09DAB21F84D4 for <grow@ietf.org>; Fri, 16 Nov 2012 18:18:51 -0800 (PST)
Received: from [192.168.2.103] (unknown [209.133.29.2]) by vimes.kumari.net (Postfix) with ESMTPSA id 31F671B401B5; Fri, 16 Nov 2012 21:18:50 -0500 (EST)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: Warren Kumari <warren@kumari.net>
In-Reply-To: <CAL9jLaaRz=MOTdo=O4PZxKFn9FkL3_FGG-ugpa2FoB-Vbp5mUg@mail.gmail.com>
Date: Fri, 16 Nov 2012 21:18:45 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <AB3896C0-88F6-4353-9C3B-4B636721058D@kumari.net>
References: <CAL9jLaagY5bBe_8eRST8noEp2-o00Zkm2Qc59Ys7pak++EPGNw@mail.gmail.com> <C8308656-31A2-4475-85FD-0DF07734A8B1@castlepoint.net> <CAL9jLabgy7f5ZkaqfGGaHkRodLfpWP=8yNcTm-4xFTgjtFVsiA@mail.gmail.com> <58638A07-2914-4BCD-96FE-A850F2B16C1E@castlepoint.net> <CAL9jLaaRz=MOTdo=O4PZxKFn9FkL3_FGG-ugpa2FoB-Vbp5mUg@mail.gmail.com>
To: Christopher Morrow <christopher.morrow@gmail.com>
X-Mailer: Apple Mail (2.1499)
Cc: "grow@ietf.org grow@ietf.org" <grow@ietf.org>, draft-foo-sidr-simple-leak-attack-bgpsec-no-help@tools.ietf.org, grow-chairs@tools.ietf.org, Warren Kumari <warren@kumari.net>, grow-ads@tools.ietf.org
Subject: Re: [GROW] RouteLeaks - problem or not?
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, 17 Nov 2012 02:18:52 -0000

On Nov 15, 2012, at 11:46 PM, Christopher Morrow =
<christopher.morrow@gmail.com> wrote:

> On Thu, Nov 15, 2012 at 11:10 PM, Shane Amante <shane@castlepoint.net> =
wrote:
>=20
>>> is that better? I'm really asking whether or not there is a problem
>>> and if we (ietf in general) can get a solution (or even the
>>> requirements for a solution?) defined...
>>=20
>> Yes, there is a (big) operational problem wrt route-leaks.
>=20
> it'd be good to outline that as well in the document... often the
> 'mitm' problem is brought up, but honestly there are probably more
> cases of:
>  1) suboptimal routing (why am I routing through Chile to get to my
> next-door-asn?)
>  2) traffic loss (via too-small-pipes + congestion)
>  3) link costs (lookie at the transit pipe being full instead of the
> other one!)
>=20
> that happen and are simpler to show than other issues.

=85 and easier to talk about as well :-)

I think that you left out:
2.5) Hey, where the hell did my traffic go?! Bah, someone over there fat =
fingered and all my traffic follo .. and it's back...

W

>=20
>>=20
>> Yes, we (IETF in general) should work toward a solution.  As I stated =
previously, I hope we remain open-minded as to the solution space and do =
not pigeon-hole ourselves into thinking that one must exist inside BGP, =
either solely or at all.
>>=20
>> -shane
>>=20
>>=20
>>=20
>>> -chris
>>>=20
>>>>=20
>>>>> The end result of the above 3 steps is to push back into IDR one =
of
>>>>> two action requests:
>>>>> 1) "Yes, route leaks are a problem, please fix them."
>>>>>   or
>>>>> 2) "No, route leaks are not a problem, take no action."
>>>>>=20
>>>>> If #1 above is the answer, and IDR decides that changes to the BGP
>>>>> protocol are warranted (or are a possible solution to the problem)
>>>>> then SIDR has agreed to do what they can to 'secure' the bits
>>>>> added/changed/used in that endeavor.
>>>>=20
>>>> Dare I ask what happens if IDR decides they do not have an answer?
>>>>=20
>>>>=20
>>>>> Could we have some discussion on-list about this problem, and some
>>>>> discussion about whether or not the draft referenced above fits =
the
>>>>> definition we would like to use for 'route leak'?
>>>>=20
>>>> Um, yes, but then again I'm a co-author, so clearly you should take =
this answer with a healthy dose of salt.  :-)
>>>>=20
>>>>=20
>>>>> I would also like
>>>>> the authors of the draft to decide where they would like to take =
their
>>>>> draft:
>>>>> 1) SIDR
>>>>> 2) IDR
>>>>> 3) GROW
>>>>> 4) other
>>>>=20
>>>> IMO, since you're asking GROW, the answer should hopefully present =
itself.  :-)
>>>>=20
>>>> -shane
>>>=20
>>=20
>>=20
> _______________________________________________
> GROW mailing list
> GROW@ietf.org
> https://www.ietf.org/mailman/listinfo/grow
>=20

--
Do not meddle in the affairs of dragons, for you are crunchy and taste =
good with ketchup.=20




From mawatari@jpix.ad.jp  Fri Nov 16 20:47:40 2012
Return-Path: <mawatari@jpix.ad.jp>
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 DC98121F876A for <grow@ietfa.amsl.com>; Fri, 16 Nov 2012 20:47:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.09
X-Spam-Level: 
X-Spam-Status: No, score=-0.09 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cGxMSeWJ8ka9 for <grow@ietfa.amsl.com>; Fri, 16 Nov 2012 20:47:40 -0800 (PST)
Received: from mx20.jpix.ad.jp (mx20.jpix.ad.jp [210.171.225.78]) by ietfa.amsl.com (Postfix) with ESMTP id 046A121F84D5 for <grow@ietf.org>; Fri, 16 Nov 2012 20:47:31 -0800 (PST)
Received: from [192.168.1.102] (KD106169162223.au-net.ne.jp [106.169.162.223]) by mx20.jpix.ad.jp (Postfix) with ESMTP id 8AE3BFC040; Sat, 17 Nov 2012 13:47:28 +0900 (JST)
Date: Sat, 17 Nov 2012 13:47:29 +0900
From: MAWATARI Masataka <mawatari@jpix.ad.jp>
To: nick@inex.ie
In-Reply-To: <50A42ED5.2060803@inex.ie>
References: <CAL9jLaagY5bBe_8eRST8noEp2-o00Zkm2Qc59Ys7pak++EPGNw@mail.gmail.com> <50A42ED5.2060803@inex.ie>
Message-Id: <20121117134726.389D.8FE1F57E@jpix.ad.jp>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Becky! ver. 2.61.01 [ja]
Cc: grow-chairs@tools.ietf.org, grow@ietf.org, draft-foo-sidr-simple-leak-attack-bgpsec-no-help@tools.ietf.org, grow-ads@tools.ietf.org
Subject: Re: [GROW] RouteLeaks - problem or not?
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, 17 Nov 2012 04:47:41 -0000

Greetings,


* On Wed, 14 Nov 2012 23:52:53 +0000
* Nick Hilliard <nick@inex.ie> wrote:

> On 14/11/2012 22:18, Christopher Morrow wrote:
> >   1) What is a 'route leak' (perhaps the above draft identifies one
> > examplar to be used in that definition)
> 
> dunno really.  Some foo which involves prefixes being sent to places where
> they oughtn't have been sent to.  This is possibly more of a legal /
> wordsmithing problem than anything else.
> 
> >   2) Are 'route leaks' a problem that Operations folks care about
> 
> speaking with my IXP operator hat on, hell yeah.  INEX operates a route
> server cluster which provides service to ~70% of our members.  If we were
> to operate an unprotected system and had a prefix leak from a client, it
> would destroy confidence in the system and people would depeer.
> Connectivity would be directly harmed.  In my experience, it takes very
> little for people to lose trust in a system like this.
> 
> We use strict prefix filtering based on IRRDB data with a vengeance, but
> ended up also having to implement maxprefixes after someone attached the
> INEX route server as-set macro to their own as set macro (mistake #1), then
> announced all the prefixes they received back to INEX (mistake #2).  As it
> happened, their prefixes were depreferred because of the asn path length,
> but if they hadn't been depreferred, it could have taken down the entire
> system.  Ouch.
> 
> Anyway, point being: yes: route leaks matter, yes: at least some operations
> people care, and belt + braces is sensible.


I agree.
Max-prefix-limits feature is one of the operative tools for mitigating
route leaks.  However in case of operating the route servers in IXP,
threshold of limit also is a important consideration.
Sometimes new members advertise the full routes into route servers,
so IXP operators would like to prevent that.
Combination of route filter and max-prefix-limit is reasonable.


Kind Regards,
Masataka MAWATARI


> >   3) Should IDR (or the IETF proper) address 'route leaks' with some
> > form(s) of fix action.
> 
> mmmm, difficult one.
> 
> So the current thinking seems to be heading in the direction of RPKI which
> has a lot of interesting technical characteristics, probably the most
> interesting of which is the max prefix length.  One interesting
> characteristic of RPKI is that in order for it to have any real function on
> a live network, it will be necessary to completely drop rpki-invalid
> prefixes.  Merely depreferring them is a bit useless.
> 
> Problem is, the current implementations of rpki only deal with origin
> validation, and not as path validation.  Work on this has begun in terms of
> a list of specifications (draft-ietf-sidr-bgpsec-reqs), but hasn't
> progressed much beyond that as far as I can tell.  I wonder if some of the
> sine-qua-nons in this document are mutually exclusive.
> 
> RPKI will only be fully functional from the point of view of preventing
> leaks (whatever leaks are) when we have full as path validation.
> 
> Being honest, RPKI concerns me from two points of view.  From a technical
> point of view, BGP is a fully distributed system which forms the basis of
> global network reachability, yet RPKI seeks to impose a top-down control /
> validation mechanism for it, albeit based on many potential roots.  I
> cannot seem to stop being concerned that this is an architecturally bad
> idea from a technical point of view, even though there are many safeguards,
> including:
> 
> - recommendations for using local caches
> - lazy validation
> - recommendations for validation only at ASN boundaries
> - recommendations in draft-ietf-sidr-origin-ops
> 
> ... even still, there is a double architectural inversion going on here,
> where a full-distributed, very low level protocol is being made to depend
> on a top-down, much higher level protocol.
> 
> From a non-technical point of view I also have serious concerns about RPKI
> in terms of it being used as a hammer that politicians / bureaucrats / LEAs
> / judges / etc are (and that's "are" as in present tense) extremely
> interested in as a potential future means of blocking content / services
> which they happen not to like.  Although GROW is not the place for this
> particular discussion, this aspect of RPKI concerns me to the extent that I
> am disturbed about the wisdom of developing the technology in the first
> place:  we're building an on/off button for prefixes throughout the
> Internet.  We need to be careful what we wish for because one day, we might
> get it.
> 
> Nick


From ttauber@1-4-5.net  Sun Nov 18 17:32:29 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 CC1FC21F8545 for <grow@ietfa.amsl.com>; Sun, 18 Nov 2012 17:32:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.976
X-Spam-Level: 
X-Spam-Status: No, score=-102.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id s9sD+Gyv9j6j for <grow@ietfa.amsl.com>; Sun, 18 Nov 2012 17:32:25 -0800 (PST)
Received: from mail-oa0-f44.google.com (mail-oa0-f44.google.com [209.85.219.44]) by ietfa.amsl.com (Postfix) with ESMTP id E2F3721F850D for <grow@ietf.org>; Sun, 18 Nov 2012 17:32:22 -0800 (PST)
Received: by mail-oa0-f44.google.com with SMTP id n5so4713185oag.31 for <grow@ietf.org>; Sun, 18 Nov 2012 17:32:22 -0800 (PST)
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=XGTjr03Jpc9MAqFeGJXFZlphOq6LX30YchYlu/VX9jM=; b=Ji7NTTGgkG6gHKHTwKXRcmXSw9y/ZsqhlQMeLMKS+boz7yqPgs23Lh9YsceYi2u+zR UC8NbMApBP8CXRkwK726G/dR6A20HxHPq6c/QixIagLhPX3aoG5Z6gUfY3RzFpne9xYM O4Ab4iGDVFPzNComvIjeHOK6kJDlpu47VpHGk16n/UhDWHON9q5uwHmDp2WWJ/F5DYIw fev2O1OFGGcN4YXJ23ZUYiynSW+kI91Da5p/DUsLH0Ijk2gl17B2MlIYmBKBIT7CpaFy gwrptPYwgRE61aPosgC+bPQ13t3d4sqO7+SJ+7W37O8zhJG/foaGqVv24VnPZ9P+SPbn F7eg==
MIME-Version: 1.0
Received: by 10.182.21.142 with SMTP id v14mr9308003obe.46.1353288742073; Sun, 18 Nov 2012 17:32:22 -0800 (PST)
Received: by 10.76.153.99 with HTTP; Sun, 18 Nov 2012 17:32:22 -0800 (PST)
X-Originating-IP: [24.104.152.66]
In-Reply-To: <9C6661E5-D760-44C4-A4EA-ACFB531FA33C@tcb.net>
References: <CAL9jLabt0S98HEygsQp=a98ARwiRxJ2x3F2=H5w-pDRbyqWE7A@mail.gmail.com> <9C6661E5-D760-44C4-A4EA-ACFB531FA33C@tcb.net>
Date: Sun, 18 Nov 2012 20:32:22 -0500
Message-ID: <CAGQUKcfxsvPJbBLZvf13ozbHMYxSAhgK0B9XhH3CSPLSL47zVQ@mail.gmail.com>
From: Tony Tauber <ttauber@1-4-5.net>
To: Danny McPherson <danny@tcb.net>
Content-Type: multipart/alternative; boundary=14dae93b5820bff43704cecf160f
X-Gm-Message-State: ALoCoQnZy+nK7Ir6eXEOOyxb6HqjNfiJoMNgZjMi7w4HwRdBWzfkcPajof3WuNI/vmaj8NtMDX49
Cc: grow-chairs@tools.ietf.org, "grow@ietf.org grow@ietf.org" <grow@ietf.org>, draft-mcpherson-irr-routing-policy-considerations@tools.ietf.org, grow-ads@tools.ietf.org
Subject: Re: [GROW] WG Adoption call: draft-mcpherson-irr-routing-policy-considerations (END: 11/28/2012)
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, 19 Nov 2012 01:32:29 -0000

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

Yes, adopt.  But "s/efficacy/effectiveness/g"

:-)

Tony

On Wed, Nov 14, 2012 at 6:37 PM, Danny McPherson <danny@tcb.net> wrote:

>
> Authors would definitely like to see this published, and GROW seems like a
> reasonable home.
>
> Given that we need to fix the IRRs whether RPKI-enabled BGPSEC is fully
> deployed or not, we should start considering what the issues are with it to
> inform improvements or recommend replacements.
>
> Comments welcome...
>
> -danny
>
>
> On Nov 14, 2012, at 5:35 PM, Christopher Morrow wrote:
>
> > Grow Folks,
> > the authors of:  draft-mcpherson-irr-routing-policy-considerations
> >  <
> http://tools.ietf.org/html/draft-mcpherson-irr-routing-policy-considerations-01
> >
> >
> > have asked if their work is appropriate for the GROW-wg, could we take
> > the next 14 days (ending Nov 28, 2012) to think/discuss this draft and
> > it's efficacy to work in the GROW arena? The abstract of the draft is:
> >  "The purpose of this document is to catalog past issues influencing
> >   the efficacy of Internet Routing Registries (IRR) for inter-domain
> >   routing policy specification and application in the global routing
> >   system over the past two decades.  Additionally, it provides a
> >   discussion regarding which of these issues are still problematic in
> >   practice, and which are simply artifacts that are no longer
> >   applicable but continue to stifle inter-provider policy-based
> >   filtering adoption and IRR utility to this day."
> >
> > Thanks!
> > -Chris
> > (co-chair)
> > _______________________________________________
> > 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
>

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

Yes, adopt.=A0 But &quot;s/efficacy/effectiveness/g&quot; <br><br>:-)<br><b=
r>Tony<br><br><div class=3D"gmail_quote">On Wed, Nov 14, 2012 at 6:37 PM, D=
anny McPherson <span dir=3D"ltr">&lt;<a href=3D"mailto:danny@tcb.net" targe=
t=3D"_blank">danny@tcb.net</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"><br>
Authors would definitely like to see this published, and GROW seems like a =
reasonable home.<br>
<br>
Given that we need to fix the IRRs whether RPKI-enabled BGPSEC is fully dep=
loyed or not, we should start considering what the issues are with it to in=
form improvements or recommend replacements.<br>
<br>
Comments welcome...<br>
<span><font color=3D"#888888"><br>
-danny<br>
</font></span><div><div><br>
<br>
On Nov 14, 2012, at 5:35 PM, Christopher Morrow wrote:<br>
<br>
&gt; Grow Folks,<br>
&gt; the authors of: =A0draft-mcpherson-irr-routing-policy-considerations<b=
r>
&gt; =A0&lt;<a href=3D"http://tools.ietf.org/html/draft-mcpherson-irr-routi=
ng-policy-considerations-01" target=3D"_blank">http://tools.ietf.org/html/d=
raft-mcpherson-irr-routing-policy-considerations-01</a>&gt;<br>
&gt;<br>
&gt; have asked if their work is appropriate for the GROW-wg, could we take=
<br>
&gt; the next 14 days (ending Nov 28, 2012) to think/discuss this draft and=
<br>
&gt; it&#39;s efficacy to work in the GROW arena? The abstract of the draft=
 is:<br>
&gt; =A0&quot;The purpose of this document is to catalog past issues influe=
ncing<br>
&gt; =A0 the efficacy of Internet Routing Registries (IRR) for inter-domain=
<br>
&gt; =A0 routing policy specification and application in the global routing=
<br>
&gt; =A0 system over the past two decades. =A0Additionally, it provides a<b=
r>
&gt; =A0 discussion regarding which of these issues are still problematic i=
n<br>
&gt; =A0 practice, and which are simply artifacts that are no longer<br>
&gt; =A0 applicable but continue to stifle inter-provider policy-based<br>
&gt; =A0 filtering adoption and IRR utility to this day.&quot;<br>
&gt;<br>
&gt; Thanks!<br>
&gt; -Chris<br>
&gt; (co-chair)<br>
&gt; _______________________________________________<br>
&gt; GROW mailing list<br>
&gt; <a href=3D"mailto:GROW@ietf.org" target=3D"_blank">GROW@ietf.org</a><b=
r>
&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>
<br>
<br>
_______________________________________________<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/listinfo/grow</a><br>
</div></div></blockquote></div><br>

--14dae93b5820bff43704cecf160f--

From rjs@rob.sh  Mon Nov 19 07:57:39 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 13AAD21F8643 for <grow@ietfa.amsl.com>; Mon, 19 Nov 2012 07:57:39 -0800 (PST)
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=[AWL=-0.000, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qNG2aqRoWZ+I for <grow@ietfa.amsl.com>; Mon, 19 Nov 2012 07:57:36 -0800 (PST)
Received: from cappuccino.rob.sh (cappuccino.rob.sh [IPv6:2001:b98:201:101::10:cafe]) by ietfa.amsl.com (Postfix) with ESMTP id 8E78C21F8616 for <grow@ietf.org>; Mon, 19 Nov 2012 07:57:35 -0800 (PST)
Received: from [195.59.14.153] (helo=host-153.linxmeeting.cw.com) by cappuccino.rob.sh with esmtpa (Exim 4.72) (envelope-from <rjs@rob.sh>) id 1TaTgM-0006Kg-3O; Mon, 19 Nov 2012 15:54:46 +0000
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=us-ascii
From: Rob Shakir <rjs@rob.sh>
In-Reply-To: <58638A07-2914-4BCD-96FE-A850F2B16C1E@castlepoint.net>
Date: Mon, 19 Nov 2012 15:57:29 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <B714554D-4747-4742-8A76-7F1F42544245@rob.sh>
References: <CAL9jLaagY5bBe_8eRST8noEp2-o00Zkm2Qc59Ys7pak++EPGNw@mail.gmail.com> <C8308656-31A2-4475-85FD-0DF07734A8B1@castlepoint.net> <CAL9jLabgy7f5ZkaqfGGaHkRodLfpWP=8yNcTm-4xFTgjtFVsiA@mail.gmail.com> <58638A07-2914-4BCD-96FE-A850F2B16C1E@castlepoint.net>
To: Shane Amante <shane@castlepoint.net>, "grow@ietf.org grow@ietf.org" <grow@ietf.org>
X-Mailer: Apple Mail (2.1257)
Cc: grow-ads@tools.ietf.org, draft-foo-sidr-simple-leak-attack-bgpsec-no-help@tools.ietf.org, grow-chairs@tools.ietf.org
Subject: Re: [GROW] RouteLeaks - problem or not?
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, 19 Nov 2012 15:57:39 -0000

On 16 Nov 2012, at 04:10, Shane Amante wrote:

>> is that better? I'm really asking whether or not there is a problem
>> and if we (ietf in general) can get a solution (or even the
>> requirements for a solution?) defined...
>=20
> Yes, there is a (big) operational problem wrt route-leaks.
>=20
> Yes, we (IETF in general) should work toward a solution.  As I stated =
previously, I hope we remain open-minded as to the solution space and do =
not pigeon-hole ourselves into thinking that one must exist inside BGP, =
either solely or at all.

Hi GROW, All,

I would support the comments that Shane made here - essentially, this is =
an operational concern, and we should at least properly document what =
the problem is. If we can use this problem statement to work towards a =
solution, then this would be a good aim.

However, I would urge that we consider the operational complexity, =
manageability and overhead of any suggested solutions. A number of the =
mechanisms in the sidr space have significant cost of implementation, =
which I'm not sure is wholly being considered, and may present a =
challenge for deployment of these solutions.

Specifically regarding route leaks, I have some concerns around the ease =
of classification of relationships between networks (that I raised in =
idr when this was discussed) -- whilst it may be convenient to consider =
there to be clearly defined categories in this space, in the real world, =
I do not think that it is as clear cut.=20

My view is that GROW is the right place to begin this work within the =
ietf -- however, some consultation with the wider operational community =
(e.g., NANOG etc.) is likely to be advantageous to tap into the best =
sources of knowledge on this matter. A solution specified without =
considering those operators which are not represented in the ietf is =
likely to be limited in its deployment.

Cheers,
r.=

From SONALKERA@battelle.org  Mon Nov 19 08:50:49 2012
Return-Path: <SONALKERA@battelle.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 59D0E21F8559 for <grow@ietfa.amsl.com>; Mon, 19 Nov 2012 08:50:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.392
X-Spam-Level: 
X-Spam-Status: No, score=-1.392 tagged_above=-999 required=5 tests=[AWL=-1.207, BAYES_40=-0.185]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H-FD8UgXqmoY for <grow@ietfa.amsl.com>; Mon, 19 Nov 2012 08:50:47 -0800 (PST)
Received: from egw3.battelle.org (egw3.battelle.org [131.167.253.52]) by ietfa.amsl.com (Postfix) with ESMTP id 2028621F84EB for <grow@ietf.org>; Mon, 19 Nov 2012 08:50:42 -0800 (PST)
Received: from pps.filterd (lp-prfpnta3 [127.0.0.1]) by lp-prfpnta3.battelle.org (8.14.5/8.14.5) with SMTP id qAJGoaiC018434; Mon, 19 Nov 2012 11:50:40 -0500
Received: from lp-prfpnta4.battelle.org ([10.50.10.71]) by lp-prfpnta3.battelle.org with ESMTP id 18n7wxeq0p-1; Mon, 19 Nov 2012 11:50:40 -0500
Received: from pps.filterd (lp-prfpnta4 [127.0.0.1]) by lp-prfpnta4.battelle.org (8.14.5/8.14.5) with SMTP id qAJGlebi020334; Mon, 19 Nov 2012 11:50:28 -0500
Received: from ws-bco-cas2.milky-way.battelle.org (ws-bco-cas2.milky-way.battelle.org [131.167.8.115]) by lp-prfpnta4.battelle.org with ESMTP id 18p3yp0w8w-1; Mon, 19 Nov 2012 11:50:28 -0500
Received: from WS-BEST-MBX1.milky-way.battelle.org (131.167.188.7) by ws-bco-cas2.milky-way.battelle.org (131.167.8.115) with Microsoft SMTP Server (TLS) id 8.3.106.1; Mon, 19 Nov 2012 11:50:39 -0500
Received: from WS-BEST-MBX1.milky-way.battelle.org ([131.167.188.7]) by WS-BEST-MBX1.milky-way.battelle.org ([131.167.188.7]) with mapi; Mon, 19 Nov 2012 11:50:38 -0500
From: "Sonalker, Anuja" <SONALKERA@battelle.org>
To: Rob Shakir <rjs@rob.sh>, Shane Amante <shane@castlepoint.net>, "grow@ietf.org grow@ietf.org" <grow@ietf.org>
Date: Mon, 19 Nov 2012 11:50:29 -0500
Thread-Topic: [GROW] RouteLeaks - problem or not?
Thread-Index: Ac3Gbpyre8tgRBksTYC8BmeiqMkZ0wAAkaqw
Message-ID: <AEDBD9C3109C3649BF68A077B7A592FD0591CFE122@WS-BEST-MBX1.milky-way.battelle.org>
References: <CAL9jLaagY5bBe_8eRST8noEp2-o00Zkm2Qc59Ys7pak++EPGNw@mail.gmail.com> <C8308656-31A2-4475-85FD-0DF07734A8B1@castlepoint.net> <CAL9jLabgy7f5ZkaqfGGaHkRodLfpWP=8yNcTm-4xFTgjtFVsiA@mail.gmail.com> <58638A07-2914-4BCD-96FE-A850F2B16C1E@castlepoint.net> <B714554D-4747-4742-8A76-7F1F42544245@rob.sh>
In-Reply-To: <B714554D-4747-4742-8A76-7F1F42544245@rob.sh>
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-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.9.8185, 1.0.431, 0.0.0000 definitions=2012-11-19_06:2012-11-19, 2012-11-19, 1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=1 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1207200000 definitions=main-1211190148
Cc: "draft-foo-sidr-simple-leak-attack-bgpsec-no-help@tools.ietf.org" <draft-foo-sidr-simple-leak-attack-bgpsec-no-help@tools.ietf.org>, "grow-ads@tools.ietf.org" <grow-ads@tools.ietf.org>, "grow-chairs@tools.ietf.org" <grow-chairs@tools.ietf.org>
Subject: Re: [GROW] RouteLeaks - problem or not?
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, 19 Nov 2012 16:50:49 -0000

Hello GROW

Bit slow on the replying over here, sorry for the late chime.=20

Thoughts in line below....


> -----Original Message-----
> From: grow-bounces@ietf.org [mailto:grow-bounces@ietf.org] On Behalf Of
> Rob Shakir
> Sent: Monday, November 19, 2012 10:57 AM
> To: Shane Amante; grow@ietf.org grow@ietf.org
> Cc: grow-ads@tools.ietf.org; draft-foo-sidr-simple-leak-attack-bgpsec-
> no-help@tools.ietf.org; grow-chairs@tools.ietf.org
> Subject: Re: [GROW] RouteLeaks - problem or not?
>=20
>=20
> On 16 Nov 2012, at 04:10, Shane Amante wrote:
>=20
> >> is that better? I'm really asking whether or not there is a problem
> >> and if we (ietf in general) can get a solution (or even the
> >> requirements for a solution?) defined...
> >
> > Yes, there is a (big) operational problem wrt route-leaks.


Agree with everyone!!=20


> >
> > Yes, we (IETF in general) should work toward a solution.  As I stated
> previously, I hope we remain open-minded as to the solution space and
> do not pigeon-hole ourselves into thinking that one must exist inside
> BGP, either solely or at all.


Completely agree with this comment. imho part of our problem is that even t=
hough we know what route leaks are when we start defining them it gets comp=
licated very quickly. There are several aspects that have a qualitative/sub=
jective and to address those we may have to think outside of bgp. The opera=
tional perspective is the most important one and therefore GROW is the best=
 place for taking up this problem, imo.=20


>=20
> Hi GROW, All,
>=20
> I would support the comments that Shane made here - essentially, this
> is an operational concern, and we should at least properly document
> what the problem is. If we can use this problem statement to work
> towards a solution, then this would be a good aim.
>

This is a great start. There are probably a few more cases that fall into t=
he Route leaks bucket that we should consider. I would be happy to share th=
em with the authors and everyone on the mailing list.=20


> However, I would urge that we consider the operational complexity,
> manageability and overhead of any suggested solutions. A number of the
> mechanisms in the sidr space have significant cost of implementation,
> which I'm not sure is wholly being considered, and may present a
> challenge for deployment of these solutions.
>=20
> Specifically regarding route leaks, I have some concerns around the
> ease of classification of relationships between networks (that I raised
> in idr when this was discussed) -- whilst it may be convenient to
> consider there to be clearly defined categories in this space, in the
> real world, I do not think that it is as clear cut.
>=20

Similar to yours, but one concern I have is that there are several non-engi=
neering rules that also contribute to route leaks. Should we even open the =
can on them, or just keep it to engineering and operations while defining t=
he problem?


> My view is that GROW is the right place to begin this work within the
> ietf -- however, some consultation with the wider operational community
> (e.g., NANOG etc.) is likely to be advantageous to tap into the best
> sources of knowledge on this matter. A solution specified without
> considering those operators which are not represented in the ietf is
> likely to be limited in its deployment.


+1


--Anuja



From m.hallgren@free.fr  Mon Nov 19 13:06:37 2012
Return-Path: <m.hallgren@free.fr>
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 82EB921F8711 for <grow@ietfa.amsl.com>; Mon, 19 Nov 2012 13:06:37 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wK5pogP9DeSb for <grow@ietfa.amsl.com>; Mon, 19 Nov 2012 13:06:37 -0800 (PST)
Received: from smtp1-g21.free.fr (smtp1-g21.free.fr [IPv6:2a01:e0c:1:1599::10]) by ietfa.amsl.com (Postfix) with ESMTP id B5C5921F8767 for <grow@ietf.org>; Mon, 19 Nov 2012 13:06:35 -0800 (PST)
Received: from [IPv6:2a01:e35:2e49:1280:21f:3bff:fe1d:c945] (unknown [IPv6:2a01:e35:2e49:1280:21f:3bff:fe1d:c945]) by smtp1-g21.free.fr (Postfix) with ESMTP id E361E940147; Mon, 19 Nov 2012 22:06:22 +0100 (CET)
From: Michael Hallgren <m.hallgren@free.fr>
To: Rob Shakir <rjs@rob.sh>
In-Reply-To: <B714554D-4747-4742-8A76-7F1F42544245@rob.sh>
References: <CAL9jLaagY5bBe_8eRST8noEp2-o00Zkm2Qc59Ys7pak++EPGNw@mail.gmail.com> <C8308656-31A2-4475-85FD-0DF07734A8B1@castlepoint.net> <CAL9jLabgy7f5ZkaqfGGaHkRodLfpWP=8yNcTm-4xFTgjtFVsiA@mail.gmail.com> <58638A07-2914-4BCD-96FE-A850F2B16C1E@castlepoint.net> <B714554D-4747-4742-8A76-7F1F42544245@rob.sh>
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-saQeZPehWc1HE++5aIo7"
Date: Mon, 19 Nov 2012 22:06:20 +0100
Message-ID: <1353359181.3599.13.camel@home>
Mime-Version: 1.0
X-Mailer: Evolution 2.30.3 
Cc: "grow@ietf.org grow@ietf.org" <grow@ietf.org>, draft-foo-sidr-simple-leak-attack-bgpsec-no-help@tools.ietf.org, grow-ads@tools.ietf.org, grow-chairs@tools.ietf.org
Subject: Re: [GROW] RouteLeaks - problem or not?
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, 19 Nov 2012 21:06:37 -0000

--=-saQeZPehWc1HE++5aIo7
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Le lundi 19 novembre 2012 =C3=A0 15:57 +0000, Rob Shakir a =C3=A9crit :
> On 16 Nov 2012, at 04:10, Shane Amante wrote:
>=20
> >> is that better? I'm really asking whether or not there is a problem
> >> and if we (ietf in general) can get a solution (or even the
> >> requirements for a solution?) defined...
> >=20
> > Yes, there is a (big) operational problem wrt route-leaks.
> >=20
> > Yes, we (IETF in general) should work toward a solution.  As I stated p=
reviously, I hope we remain open-minded as to the solution space and do not=
 pigeon-hole ourselves into thinking that one must exist inside BGP, either=
 solely or at all.
>=20
> Hi GROW, All,
>=20
> I would support the comments that Shane made here - essentially, this is =
an operational concern, and we should at least properly document what the p=
roblem is. If we can use this problem statement to work towards a solution,=
 then this would be a good aim.
>=20
> However, I would urge that we consider the operational complexity, manage=
ability and overhead of any suggested solutions. A number of the mechanisms=
 in the sidr space have significant cost of implementation, which I'm not s=
ure is wholly being considered, and may present a challenge for deployment =
of these solutions.
>=20
> Specifically regarding route leaks, I have some concerns around the ease =
of classification of relationships between networks (that I raised in idr w=
hen this was discussed) -- whilst it may be convenient to consider there to=
 be clearly defined categories in this space, in the real world, I do not t=
hink that it is as clear cut.=20
>=20

Right, I think we all know by now that modeling commercial or social
desire or need is 'hard'. A good starting or way point would thus likely
be to carefully study the problem space, in order to keep our pieces to
develop as simple (and well defined) as ever possible.

For instance, as you hint, inter domain routing knobs are currently
quite often "used" to patch billing (or collection of sufficient or
cheap enough billing data) shortcomings, which IMHO is a bit
unfortunate.=20

> My view is that GROW is the right place to begin this work within the iet=
f -- however, some consultation with the wider operational community (e.g.,=
 NANOG etc.) is likely to be advantageous to tap into the best sources of k=
nowledge on this matter. A solution specified without considering those ope=
rators which are not represented in the ietf is likely to be limited in its=
 deployment.
>=20

Yep.

Cheers

mh

> Cheers,
> r.
> _______________________________________________
> GROW mailing list
> GROW@ietf.org
> https://www.ietf.org/mailman/listinfo/grow


--=-saQeZPehWc1HE++5aIo7
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEABECAAYFAlCqn0MACgkQZNZ/rrgsqadl6ACgidwruduoxUvKVGNwlJCRlJNX
dcMAoJT7ytqTLk2wTJjXQdGyDWqHrQbS
=+Rhe
-----END PGP SIGNATURE-----

--=-saQeZPehWc1HE++5aIo7--


From russw@riw.us  Tue Nov 20 06:35:20 2012
Return-Path: <russw@riw.us>
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 8762321F84CC for <grow@ietfa.amsl.com>; Tue, 20 Nov 2012 06:35:20 -0800 (PST)
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=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jMlEU06CLlPE for <grow@ietfa.amsl.com>; Tue, 20 Nov 2012 06:35:14 -0800 (PST)
Received: from da31.namelessnet.net (da31.namelessnet.net [74.124.205.66]) by ietfa.amsl.com (Postfix) with ESMTP id 68EF821F8203 for <grow@ietf.org>; Tue, 20 Nov 2012 06:35:14 -0800 (PST)
Received: from cpe-065-190-156-032.nc.res.rr.com ([65.190.156.32] helo=[192.168.100.51]) by da31.namelessnet.net with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.80) (envelope-from <russw@riw.us>) id 1Taouq-0005sf-ES for grow@ietf.org; Tue, 20 Nov 2012 06:35:08 -0800
Message-ID: <50AB950F.5080801@riw.us>
Date: Tue, 20 Nov 2012 09:34:55 -0500
From: Russ White <russw@riw.us>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: grow@ietf.org
References: <CAL9jLaagY5bBe_8eRST8noEp2-o00Zkm2Qc59Ys7pak++EPGNw@mail.gmail.com> <CAL9jLaZT43OBwHqWs-xzy8qCm1UEyfN+hDKTgdrrvCc09xWNHw@mail.gmail.com> <50A44080.8020704@lacnic.net>
In-Reply-To: <50A44080.8020704@lacnic.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Antivirus-Scanner: Seems clean.  You should still use an Antivirus Scanner
Subject: Re: [GROW] RouteLeaks - problem or not?
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, 20 Nov 2012 14:35:20 -0000

> 	I think that draft-foo-sidr-simple-leak-attack-bgpsec-no-help-02 shows
> very well why rpki-origin-validation and bgpsec are vulerable to route
> leaks. Also it has a good and simple example of a route leak. One
> drawback that I see is that it does not explain the problem in general,
> the document is focused on route leaks as result of
> Man-in-the-middle-attack. Recent events relating leaks showed us that an
> attack it is not necessary, just some fat fingers in the right place and
> you are done.

In reality, what we are calling a "man in the middle attack," has always
just been one instance of the more general "route leak" problem. The
only way to know if a route has been "leaked," is to know what the table
_should_ look like.

BGPSEC (and the original drafts, S-BGP, on which the BGPSEC
"requirements" are based) is focused on "this is what really happened,"
rather than, "this is what should be happening." The interesting point
of security (if we want to prevent problems rather than just provide
forensics) is, "this is what should be happening."

So, to answers Chris' questions:

>>>   1) "Yes, route leaks are a problem, please fix them."

Yes, route leaks are a problem, and there needs to be some way to guard
against them, which means, we're going to have to talk about intent.

>>> If #1 above is the answer, and IDR decides that changes to the BGP
>>> protocol are warranted (or are a possible solution to the problem)
>>> then SIDR has agreed to do what they can to 'secure' the bits
>>> added/changed/used in that endeavor.

This, OTOH, I disagree with. The most direct way to solve this problem
isn't to "add bits to BGP." It's to provide a general framework in which
intent can be exposed where necessary. Let's not pretend that this
"route leak" problem is the last and only problem to be solved, nor that
the solution to all possible future problem is to continue to "add bits."

>>>    1) SIDR

SIDR is the correct place to address this problem, though I know it
means reconsidering the entire suite of requirements and currently
proposed solutions. OTOH, that's a good thing, because it might make us
go back and look at real requirements, rather than trying to narrow the
requirements to the set that can be solved with an already proposed
solution.

:-)

Russ

-- 
<><
riwhite@verisign.com
russw@riw.us

From russw@riw.us  Wed Nov 21 04:42:56 2012
Return-Path: <russw@riw.us>
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 C2BD421F8691 for <grow@ietfa.amsl.com>; Wed, 21 Nov 2012 04:42:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.45
X-Spam-Level: 
X-Spam-Status: No, score=-0.45 tagged_above=-999 required=5 tests=[AWL=0.754,  BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hscxjpYoSSQ3 for <grow@ietfa.amsl.com>; Wed, 21 Nov 2012 04:42:56 -0800 (PST)
Received: from da31.namelessnet.net (da31.namelessnet.net [74.124.205.66]) by ietfa.amsl.com (Postfix) with ESMTP id 6304D21F8675 for <grow@ietf.org>; Wed, 21 Nov 2012 04:42:56 -0800 (PST)
Received: from cpe-071-074-016-043.ec.res.rr.com ([71.74.16.43] helo=[192.168.100.52]) by da31.namelessnet.net with esmtpa (Exim 4.80) (envelope-from <russw@riw.us>) id 1Tb9dk-00022D-Pe; Wed, 21 Nov 2012 04:42:53 -0800
References: <CAL9jLabt0S98HEygsQp=a98ARwiRxJ2x3F2=H5w-pDRbyqWE7A@mail.gmail.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: <CAL9jLabt0S98HEygsQp=a98ARwiRxJ2x3F2=H5w-pDRbyqWE7A@mail.gmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <D839E7E2-D3E8-42C2-A494-87F26EB7A39C@riw.us>
X-Mailer: iPad Mail (10A523)
From: Russ White <russw@riw.us>
Date: Wed, 21 Nov 2012 07:42:53 -0500
To: Christopher Morrow <christopher.morrow@gmail.com>
X-Antivirus-Scanner: Seems clean.  You should still use an Antivirus Scanner
Cc: "grow@ietf.org grow@ietf.org" <grow@ietf.org>, "draft-mcpherson-irr-routing-policy-considerations@tools.ietf.org" <draft-mcpherson-irr-routing-policy-considerations@tools.ietf.org>, "grow-ads@tools.ietf.org" <grow-ads@tools.ietf.org>, "grow-chairs@tools.ietf.org" <grow-chairs@tools.ietf.org>
Subject: Re: [GROW] WG Adoption call: draft-mcpherson-irr-routing-policy-considerations (END: 11/28/2012)
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, 21 Nov 2012 12:42:56 -0000

I think this is good work to adopt, and GROW is a good home for it.

Russ

 Sent from my iPad

On Nov 14, 2012, at 5:35 PM, Christopher Morrow <christopher.morrow@gmail.co=
m> wrote:

> Grow Folks,
> the authors of:  draft-mcpherson-irr-routing-policy-considerations
>  <http://tools.ietf.org/html/draft-mcpherson-irr-routing-policy-considerat=
ions-01>
>=20
> have asked if their work is appropriate for the GROW-wg, could we take
> the next 14 days (ending Nov 28, 2012) to think/discuss this draft and
> it's efficacy to work in the GROW arena? The abstract of the draft is:
>  "The purpose of this document is to catalog past issues influencing
>   the efficacy of Internet Routing Registries (IRR) for inter-domain
>   routing policy specification and application in the global routing
>   system over the past two decades.  Additionally, it provides a
>   discussion regarding which of these issues are still problematic in
>   practice, and which are simply artifacts that are no longer
>   applicable but continue to stifle inter-provider policy-based
>   filtering adoption and IRR utility to this day."
>=20
> Thanks!
> -Chris
> (co-chair)
> _______________________________________________
> GROW mailing list
> GROW@ietf.org
> https://www.ietf.org/mailman/listinfo/grow

From rob.shakir@bt.com  Wed Nov 21 06:59:54 2012
Return-Path: <rob.shakir@bt.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 C50ED21F84CA for <grow@ietfa.amsl.com>; Wed, 21 Nov 2012 06:59:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gaiKOnGdwqd1 for <grow@ietfa.amsl.com>; Wed, 21 Nov 2012 06:59:54 -0800 (PST)
Received: from smtpe1.intersmtp.com (smtp61.intersmtp.com [62.239.224.234]) by ietfa.amsl.com (Postfix) with ESMTP id A7CD521F843C for <grow@ietf.org>; Wed, 21 Nov 2012 06:59:53 -0800 (PST)
Received: from EVHUB70-UKRD.domain1.systemhost.net (10.36.3.153) by RDW083A005ED61.smtp-e1.hygiene.service (10.187.98.10) with Microsoft SMTP Server (TLS) id 8.3.279.1; Wed, 21 Nov 2012 14:59:52 +0000
Received: from EVMHT03-UKBR.domain1.systemhost.net (193.113.108.56) by EVHUB70-UKRD.domain1.systemhost.net (10.36.3.153) with Microsoft SMTP Server (TLS) id 14.2.318.4; Wed, 21 Nov 2012 14:59:52 +0000
Received: from EMV02-UKBR.domain1.systemhost.net ([169.254.2.82]) by EVMHT03-UKBR.domain1.systemhost.net ([193.113.108.56]) with mapi; Wed, 21 Nov 2012 14:59:51 +0000
From: <rob.shakir@bt.com>
To: <m.hallgren@free.fr>, <rjs@rob.sh>
Date: Wed, 21 Nov 2012 14:59:49 +0000
Thread-Topic: [GROW] RouteLeaks - problem or not?
Thread-Index: Ac3H+NvvWAS1ldRJR9a2ZobDKzpmaw==
Message-ID: <CCD29C6F.7ED23%rob.shakir@bt.com>
In-Reply-To: <1353359181.3599.13.camel@home>
Accept-Language: en-US, en-GB
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.3.120616
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: grow@ietf.org, grow-ads@tools.ietf.org, draft-foo-sidr-simple-leak-attack-bgpsec-no-help@tools.ietf.org, grow-chairs@tools.ietf.org
Subject: Re: [GROW] RouteLeaks - problem or not?
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, 21 Nov 2012 14:59:54 -0000

On 19/11/2012 21:06, "Michael Hallgren" <m.hallgren@free.fr> wrote:

>Right, I think we all know by now that modeling commercial or social
>desire or need is 'hard'. A good starting or way point would thus likely
>be to carefully study the problem space, in order to keep our pieces to
>develop as simple (and well defined) as ever possible.
>
>For instance, as you hint, inter domain routing knobs are currently
>quite often "used" to patch billing (or collection of sufficient or
>cheap enough billing data) shortcomings, which IMHO is a bit
>unfortunate.

Yes - exactly.  The other consideration here is around how willing certain
networks are to expose such "patches" being used.  The situation is
unfortunate, but at the risk of stating the obvious, if we do not consider
real world behaviour (as Russ commented), then a solution will not solve
real world problems.

r.


From wesley.george@twcable.com  Wed Nov 21 07:31:45 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 218AE21F8683 for <grow@ietfa.amsl.com>; Wed, 21 Nov 2012 07:31:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.406
X-Spam-Level: 
X-Spam-Status: No, score=-0.406 tagged_above=-999 required=5 tests=[AWL=0.057,  BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id x59a+y+GXRJL for <grow@ietfa.amsl.com>; Wed, 21 Nov 2012 07:31:44 -0800 (PST)
Received: from cdpipgw02.twcable.com (cdpipgw02.twcable.com [165.237.59.23]) by ietfa.amsl.com (Postfix) with ESMTP id 429C221F867D for <grow@ietf.org>; Wed, 21 Nov 2012 07:31:44 -0800 (PST)
X-SENDER-IP: 10.136.163.11
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.83,293,1352091600"; d="scan'208";a="455851055"
Received: from unknown (HELO PRVPEXHUB02.corp.twcable.com) ([10.136.163.11]) by cdpipgw02.twcable.com with ESMTP/TLS/RC4-MD5; 21 Nov 2012 10:31:26 -0500
Received: from PRVPEXVS15.corp.twcable.com ([10.136.163.79]) by PRVPEXHUB02.corp.twcable.com ([10.136.163.11]) with mapi; Wed, 21 Nov 2012 10:31:42 -0500
From: "George, Wes" <wesley.george@twcable.com>
To: Christopher Morrow <christopher.morrow@gmail.com>, "grow@ietf.org" <grow@ietf.org>
Date: Wed, 21 Nov 2012 10:31:48 -0500
Thread-Topic: [GROW] WG Adoption call: draft-mcpherson-irr-routing-policy-considerations (END: 11/28/2012)
Thread-Index: Ac3CuG5UCckNui7iQu+7OliPSsiyfgFRJJbg
Message-ID: <2671C6CDFBB59E47B64C10B3E0BD592303385FBC8B@PRVPEXVS15.corp.twcable.com>
References: <CAL9jLabt0S98HEygsQp=a98ARwiRxJ2x3F2=H5w-pDRbyqWE7A@mail.gmail.com>
In-Reply-To: <CAL9jLabt0S98HEygsQp=a98ARwiRxJ2x3F2=H5w-pDRbyqWE7A@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] WG Adoption call: draft-mcpherson-irr-routing-policy-considerations (END: 11/28/2012)
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, 21 Nov 2012 15:31:45 -0000

Yes, please. While I'm not certain it's complete in its current form, it's =
definitely a good platform for the discussion that *needs* to happen about =
it.

Thanks,

Wes

> -----Original Message-----
> From: grow-bounces@ietf.org [mailto:grow-bounces@ietf.org] On Behalf Of
> Christopher Morrow
> Sent: Wednesday, November 14, 2012 5:36 PM
> To: grow-ads@tools.ietf.org; grow-chairs@tools.ietf.org; grow@ietf.org
> grow@ietf.org; draft-mcpherson-irr-routing-policy-
> considerations@tools.ietf.org
> Subject: [GROW] WG Adoption call: draft-mcpherson-irr-routing-policy-
> considerations (END: 11/28/2012)
>
> Grow Folks,
> the authors of:  draft-mcpherson-irr-routing-policy-considerations
>   <http://tools.ietf.org/html/draft-mcpherson-irr-routing-policy-
> considerations-01>
>
> have asked if their work is appropriate for the GROW-wg, could we take
> the next 14 days (ending Nov 28, 2012) to think/discuss this draft and
> it's efficacy to work in the GROW arena? The abstract of the draft is:
>   "The purpose of this document is to catalog past issues influencing
>    the efficacy of Internet Routing Registries (IRR) for inter-domain
>    routing policy specification and application in the global routing
>    system over the past two decades.  Additionally, it provides a
>    discussion regarding which of these issues are still problematic in
>    practice, and which are simply artifacts that are no longer
>    applicable but continue to stifle inter-provider policy-based
>    filtering adoption and IRR utility to this day."
>
> Thanks!
> -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 rraszuk@gmail.com  Tue Nov 27 08:18:03 2012
Return-Path: <rraszuk@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 0083A21F8604 for <grow@ietfa.amsl.com>; Tue, 27 Nov 2012 08:18:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.977
X-Spam-Level: 
X-Spam-Status: No, score=-2.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KnH5bUHHy9PZ for <grow@ietfa.amsl.com>; Tue, 27 Nov 2012 08:18:02 -0800 (PST)
Received: from mail-ie0-f172.google.com (mail-ie0-f172.google.com [209.85.223.172]) by ietfa.amsl.com (Postfix) with ESMTP id 47D2721F8521 for <grow@ietf.org>; Tue, 27 Nov 2012 08:18:02 -0800 (PST)
Received: by mail-ie0-f172.google.com with SMTP id c13so12032352ieb.31 for <grow@ietf.org>; Tue, 27 Nov 2012 08:17:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:cc:content-type; bh=Ao6k/O/3JEAwPjD60xwN4x4eT3b1TXO0Tr5ffAFkWpU=; b=FicGrzEwCaF4RK6BSmckTKB6aRvSnIMWhSErXuEfdhdp53c5Pg7y9imoVd/4AdO8RS HgLPHeqF3peH9qhvQ9pV9el9vxcnWJ2aHx6JQHB9kdCw0zuyl0m9PmTOJNGA/zzGppZd DDdP0+mDe4SrIuUFu8//RwQ3u/dJdPmXqyAkvB8AKYSKaJuHfMu/m/VIKbZRdJZ6VVd8 QPvQWdFMBaV2cIc/GmROxbzsonfv+81vBy9Z+nNIoyW3UWUJAr0hHA6uv0APQ3mMTQ8L HE1dWcTSLe7FrxD0uM+278/Xeyj3AGbDZdLqGObhkxqC0LXm7yCuG54oPDc/k4iOSZiu 5geQ==
MIME-Version: 1.0
Received: by 10.50.91.169 with SMTP id cf9mr18570498igb.44.1354033069490; Tue, 27 Nov 2012 08:17:49 -0800 (PST)
Sender: rraszuk@gmail.com
Received: by 10.42.222.133 with HTTP; Tue, 27 Nov 2012 08:17:49 -0800 (PST)
Date: Tue, 27 Nov 2012 17:17:49 +0100
X-Google-Sender-Auth: _7I0GQKBcAlwuDGZeLp10p_WwSI
Message-ID: <CA+b+ERk0A1Kkex-f2goRv5Wa+GOXENMgXqA52myHzxO23bJfvA@mail.gmail.com>
From: Robert Raszuk <robert@raszuk.net>
To: grow@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Cc: mkarir@merit.edu, labovit@arbor.net
Subject: [GROW] MRT
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, 27 Nov 2012 16:18:03 -0000

Hello,

Does anyone (in particular cc-ed authors) recall what is the status,
planned update, planned progress to RFC of this document:

http://tools.ietf.org/id/draft-ietf-grow-mrt-04.txt

Thx,
R.

From jhaas@pfrc.org  Tue Nov 27 08:26:26 2012
Return-Path: <jhaas@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 33BE721F8233 for <grow@ietfa.amsl.com>; Tue, 27 Nov 2012 08:26:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.265
X-Spam-Level: 
X-Spam-Status: No, score=-102.265 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9jJz3sJeAufX for <grow@ietfa.amsl.com>; Tue, 27 Nov 2012 08:26:25 -0800 (PST)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id 9149921F85A5 for <grow@ietf.org>; Tue, 27 Nov 2012 08:26:25 -0800 (PST)
Received: from [192.168.1.85] (99-59-194-154.lightspeed.livnmi.sbcglobal.net [99.59.194.154]) by slice.pfrc.org (Postfix) with ESMTPSA id 1E40BC0E9; Tue, 27 Nov 2012 11:26:21 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: PFRC - jhaas <jhaas@pfrc.org>
In-Reply-To: <CA+b+ERk0A1Kkex-f2goRv5Wa+GOXENMgXqA52myHzxO23bJfvA@mail.gmail.com>
Date: Tue, 27 Nov 2012 11:26:20 -0500
Content-Transfer-Encoding: 7bit
Message-Id: <2AC2796A-FE5F-44CB-900D-0A199F616D79@pfrc.org>
References: <CA+b+ERk0A1Kkex-f2goRv5Wa+GOXENMgXqA52myHzxO23bJfvA@mail.gmail.com>
To: Robert Raszuk <robert@raszuk.net>
X-Mailer: Apple Mail (2.1499)
Cc: grow@ietf.org
Subject: Re: [GROW] MRT
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, 27 Nov 2012 16:26:26 -0000

http://tools.ietf.org/html/rfc6396

On Nov 27, 2012, at 11:17 AM, Robert Raszuk <robert@raszuk.net> wrote:

> Hello,
> 
> Does anyone (in particular cc-ed authors) recall what is the status,
> planned update, planned progress to RFC of this document:
> 
> http://tools.ietf.org/id/draft-ietf-grow-mrt-04.txt
> 
> Thx,
> R.
> _______________________________________________
> GROW mailing list
> GROW@ietf.org
> https://www.ietf.org/mailman/listinfo/grow


From ljb@merit.edu  Tue Nov 27 08:29:10 2012
Return-Path: <ljb@merit.edu>
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 82E3821F8469 for <grow@ietfa.amsl.com>; Tue, 27 Nov 2012 08:29:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cOy1udtRs4pz for <grow@ietfa.amsl.com>; Tue, 27 Nov 2012 08:28:55 -0800 (PST)
Received: from sfpop-ironport03.merit.edu (sfpop-ironport03.merit.edu [207.75.116.62]) by ietfa.amsl.com (Postfix) with ESMTP id 4959721F844D for <grow@ietf.org>; Tue, 27 Nov 2012 08:28:53 -0800 (PST)
X-Merit-ExtLoop1: 1
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ak8JAH7ptFDGbD6X/2dsb2JhbABFvxMEgQeBCYIeAQEFOEABEAsYCRMDDwkDAgECAUUGDQEHAQGICQywNodGiQiMOjyEBQOIXo0jgRyPKIMO
X-IronPort-AV: E=Sophos;i="4.83,328,1352091600"; d="scan'208";a="14753328"
Received: from ablate.merit.edu ([198.108.62.151]) by sfpop-ironport03.merit.edu with ESMTP; 27 Nov 2012 11:28:52 -0500
Message-ID: <50B4EA44.7090502@merit.edu>
Date: Tue, 27 Nov 2012 11:28:52 -0500
From: Larry Blunk <ljb@merit.edu>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Robert Raszuk <robert@raszuk.net>
References: <CA+b+ERk0A1Kkex-f2goRv5Wa+GOXENMgXqA52myHzxO23bJfvA@mail.gmail.com>
In-Reply-To: <CA+b+ERk0A1Kkex-f2goRv5Wa+GOXENMgXqA52myHzxO23bJfvA@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: mkarir@merit.edu, grow@ietf.org, labovit@arbor.net
Subject: Re: [GROW] MRT
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, 27 Nov 2012 16:29:12 -0000

On 11/27/2012 11:17 AM, Robert Raszuk wrote:
> Hello,
>
> Does anyone (in particular cc-ed authors) recall what is the status,
> planned update, planned progress to RFC of this document:
>
> http://tools.ietf.org/id/draft-ietf-grow-mrt-04.txt
>
> Thx,
> R.
>

  It's an RFC now --

http://tools.ietf.org/html/rfc6396

  Unfortunately, section 4.3.4 does not match the
current Quagga/libbgpdump implementations.  The RFC
says to omit the AFI/SAFI/NLRI fields in the MP_REACH_NLRI
attribute (since that info is already in the MRT
RIB Entry Header), but the current implementations
simply copy the attribute as-is in the RIB Entry
field.

  Regards,
   Larry Blunk



From rraszuk@gmail.com  Tue Nov 27 08:29:13 2012
Return-Path: <rraszuk@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 99D4B21F8449 for <grow@ietfa.amsl.com>; Tue, 27 Nov 2012 08:29:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.977
X-Spam-Level: 
X-Spam-Status: No, score=-2.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KioXnMJZDhbL for <grow@ietfa.amsl.com>; Tue, 27 Nov 2012 08:29:12 -0800 (PST)
Received: from mail-ie0-f172.google.com (mail-ie0-f172.google.com [209.85.223.172]) by ietfa.amsl.com (Postfix) with ESMTP id A979321F844D for <grow@ietf.org>; Tue, 27 Nov 2012 08:29:12 -0800 (PST)
Received: by mail-ie0-f172.google.com with SMTP id c13so12056451ieb.31 for <grow@ietf.org>; Tue, 27 Nov 2012 08:29:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=YKohT3++NG0abAGLb/ZRFYBqpGclwOBuRuyHivhBcfQ=; b=NpkVHqHmSfbsHxZQzHtlKMJOeGcZEfRZGZ228OnuTQeyYGKt7ZooGC/jBgpYIhbQri 9D93lXwwmqzoKzo5nnZu8g4a7g7C1gwDoJmG0sicURrMyLVLNMNAK8GbvU4Z6fxHNjcr P2560pRSzyanFC1isMErE3W+nt9HETeoWZX8GVd1GaPrCz0nXAYbTus17n0KfBm9kzPN jlmPH2rSYrlb0eTudeO4Q4t4Dls2AvygfjeLED+OKv2r5rK7Um2Di8K47ELIS1xCwhmT ak3Sf0ftdC4+egZ62W9D905SbvJ/60SBZcjb6vlmfG8wa7nc7NIvExK4snBV30YUS8c+ /rqA==
MIME-Version: 1.0
Received: by 10.42.68.203 with SMTP id y11mr14458961ici.26.1354033752049; Tue, 27 Nov 2012 08:29:12 -0800 (PST)
Sender: rraszuk@gmail.com
Received: by 10.42.222.133 with HTTP; Tue, 27 Nov 2012 08:29:11 -0800 (PST)
In-Reply-To: <2AC2796A-FE5F-44CB-900D-0A199F616D79@pfrc.org>
References: <CA+b+ERk0A1Kkex-f2goRv5Wa+GOXENMgXqA52myHzxO23bJfvA@mail.gmail.com> <2AC2796A-FE5F-44CB-900D-0A199F616D79@pfrc.org>
Date: Tue, 27 Nov 2012 17:29:11 +0100
X-Google-Sender-Auth: rn5NPuBkHkrMAyQ5QCDaO9-oKXs
Message-ID: <CA+b+ERk6D4d4p=o340EO0Xn7zagRz1SYQ0D5LZ6BB0KpvuqM=w@mail.gmail.com>
From: Robert Raszuk <robert@raszuk.net>
To: PFRC - jhaas <jhaas@pfrc.org>
Content-Type: text/plain; charset=ISO-8859-1
Cc: grow@ietf.org
Subject: Re: [GROW] MRT
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, 27 Nov 2012 16:29:13 -0000

Thx ! Just found that it went up to version -17 then became RFC.

Many thx,
R.

On Tue, Nov 27, 2012 at 5:26 PM, PFRC - jhaas <jhaas@pfrc.org> wrote:
> http://tools.ietf.org/html/rfc6396
>
> On Nov 27, 2012, at 11:17 AM, Robert Raszuk <robert@raszuk.net> wrote:
>
>> Hello,
>>
>> Does anyone (in particular cc-ed authors) recall what is the status,
>> planned update, planned progress to RFC of this document:
>>
>> http://tools.ietf.org/id/draft-ietf-grow-mrt-04.txt
>>
>> Thx,
>> R.
>> _______________________________________________
>> GROW mailing list
>> GROW@ietf.org
>> https://www.ietf.org/mailman/listinfo/grow
>

From rraszuk@gmail.com  Tue Nov 27 08:33:52 2012
Return-Path: <rraszuk@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 0571F21F84D3 for <grow@ietfa.amsl.com>; Tue, 27 Nov 2012 08:33:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.977
X-Spam-Level: 
X-Spam-Status: No, score=-2.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IwXDqHjw79rl for <grow@ietfa.amsl.com>; Tue, 27 Nov 2012 08:33:51 -0800 (PST)
Received: from mail-ia0-f172.google.com (mail-ia0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id 6776321F845E for <grow@ietf.org>; Tue, 27 Nov 2012 08:33:45 -0800 (PST)
Received: by mail-ia0-f172.google.com with SMTP id j26so9910591iaf.31 for <grow@ietf.org>; Tue, 27 Nov 2012 08:33:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=2b9jbLO+rO1uKiUh0XrWkor/IBTASEryS5v6B6bYJqE=; b=X0jbr/0/qYxIbZscgFD+PtV5yU9BzVj8lENNV4ju7ZquKiiTE83nRHDzvRH7WVUcvx EknC06dzp30ccWzqy/o8ab+ATFqPBAkW4QWfrMMDtoaMRhdfzOVCaxQl7z9Osnlu5c+a aQuUnJ8NGsazu14w1vyQ/Qm0rdDix8+O7wdd8BuiHZOtUVVMy0x4aIdTGr907E7uD7hN el4nkKvvI1FIxoqGZF0JRTIctaRYs8WVmm03RXdx3ie8aMQj2VXausPmdiYamJyHqRX/ YJVz6AscOTphPsvme2JUIEWNAM4dU1+IP6ebl2wYHnZnsW2OYAo4rSBR0ggL9uumzh4P w9sw==
MIME-Version: 1.0
Received: by 10.50.179.5 with SMTP id dc5mr16272839igc.15.1354034024686; Tue, 27 Nov 2012 08:33:44 -0800 (PST)
Sender: rraszuk@gmail.com
Received: by 10.42.222.133 with HTTP; Tue, 27 Nov 2012 08:33:44 -0800 (PST)
In-Reply-To: <50B4EA44.7090502@merit.edu>
References: <CA+b+ERk0A1Kkex-f2goRv5Wa+GOXENMgXqA52myHzxO23bJfvA@mail.gmail.com> <50B4EA44.7090502@merit.edu>
Date: Tue, 27 Nov 2012 17:33:44 +0100
X-Google-Sender-Auth: 1FJlRXzyP0W-ri2pNksPTNhED7I
Message-ID: <CA+b+ERm0DKs5Pzk5c0e2PJaQeMHvK1Y6Yqwvg0_G88ibjhoUTw@mail.gmail.com>
From: Robert Raszuk <robert@raszuk.net>
To: Larry Blunk <ljb@merit.edu>
Content-Type: text/plain; charset=ISO-8859-1
Cc: mkarir@merit.edu, grow@ietf.org
Subject: Re: [GROW] MRT
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, 27 Nov 2012 16:33:52 -0000

Thx Larry !

Any pointer to best MRT opensource tools repository for parsing the
messages and maybe even performing some analysis on them (in
particular related to BGP) ?

Rgs,
R.

On Tue, Nov 27, 2012 at 5:28 PM, Larry Blunk <ljb@merit.edu> wrote:
> On 11/27/2012 11:17 AM, Robert Raszuk wrote:
>>
>> Hello,
>>
>> Does anyone (in particular cc-ed authors) recall what is the status,
>> planned update, planned progress to RFC of this document:
>>
>> http://tools.ietf.org/id/draft-ietf-grow-mrt-04.txt
>>
>> Thx,
>> R.
>>
>
>  It's an RFC now --
>
> http://tools.ietf.org/html/rfc6396
>
>  Unfortunately, section 4.3.4 does not match the
> current Quagga/libbgpdump implementations.  The RFC
> says to omit the AFI/SAFI/NLRI fields in the MP_REACH_NLRI
> attribute (since that info is already in the MRT
> RIB Entry Header), but the current implementations
> simply copy the attribute as-is in the RIB Entry
> field.
>
>  Regards,
>   Larry Blunk
>
>

From mattia.rossi.mailinglists@gmail.com  Tue Nov 27 08:43:36 2012
Return-Path: <mattia.rossi.mailinglists@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 63A2F21F84E4 for <grow@ietfa.amsl.com>; Tue, 27 Nov 2012 08:43:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ixa230UqL+kH for <grow@ietfa.amsl.com>; Tue, 27 Nov 2012 08:43:35 -0800 (PST)
Received: from mail-lb0-f172.google.com (mail-lb0-f172.google.com [209.85.217.172]) by ietfa.amsl.com (Postfix) with ESMTP id 6A95421F84DF for <grow@ietf.org>; Tue, 27 Nov 2012 08:43:34 -0800 (PST)
Received: by mail-lb0-f172.google.com with SMTP id y2so10527875lbk.31 for <grow@ietf.org>; Tue, 27 Nov 2012 08:43:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=TxEb0ObNSHnDADs5sq6o7+k+mDioXsIcbL7PQISSaZk=; b=kW6wddiwJWonYhlZPCL5XwktT7c/l53mh2ztvXz2dB0FAeFLnf3hRmgVIWk9aqyY5H X8evBSSKb6PyjjPy91amy0/whKNnaDjfZidyxSo//sPjchmbkAepE4sGf/+y2l1HggSH OD2V88G4+IcMqrU5VyHeKP6T4jtCFThgB/EIfBjN0xGxz33YQ7A6RxqWPThfuz6lVEQ4 hA93muD1aVSKh1NSb3GM8SL1H+PT6fATPeuxysCYnv4VokKhg2jef1Pe1MVBDpp49Dxw yraYd2JwnB8TstQSG4C3Pne3id9XwUFWk3HLWBvMBcN3SjHrJhI6p6sntDF9FPhEpPgL KzVw==
Received: by 10.112.44.135 with SMTP id e7mr1854200lbm.55.1354034611409; Tue, 27 Nov 2012 08:43:31 -0800 (PST)
Received: from [192.168.0.121] (vpn.static.83-173-212-209.cybernet.ch. [83.173.212.209]) by mx.google.com with ESMTPS id bf3sm7275986lbb.16.2012.11.27.08.43.29 (version=SSLv3 cipher=OTHER); Tue, 27 Nov 2012 08:43:30 -0800 (PST)
Message-ID: <50B4EDB0.6040102@gmail.com>
Date: Tue, 27 Nov 2012 17:43:28 +0100
From: Mattia Rossi <mattia.rossi.mailinglists@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: grow@ietf.org
References: <CA+b+ERk0A1Kkex-f2goRv5Wa+GOXENMgXqA52myHzxO23bJfvA@mail.gmail.com> <50B4EA44.7090502@merit.edu> <CA+b+ERm0DKs5Pzk5c0e2PJaQeMHvK1Y6Yqwvg0_G88ibjhoUTw@mail.gmail.com>
In-Reply-To: <CA+b+ERm0DKs5Pzk5c0e2PJaQeMHvK1Y6Yqwvg0_G88ibjhoUTw@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [GROW] MRT
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, 27 Nov 2012 16:43:36 -0000

There are tools in here: http://caia.swin.edu.au/urp/bgp/tools.html 
which you might find useful, and work (or at least worked) with Quagga 
dump files. In particular the MDFMT and the Path Exploration Analyzer. 
The PEA might give you some ideas on how to use libbgpdump for analysis, 
while the MDFMT is based on pybgpdump 
(http://jon.oberheide.org/projects/pybgpdump/) which is very nice for a 
quick analysis of MRT dumps.

Hope you haven't already discarded them :-)

Mat


Am 27.11.2012 17:33, schrieb Robert Raszuk:
> Thx Larry !
>
> Any pointer to best MRT opensource tools repository for parsing the
> messages and maybe even performing some analysis on them (in
> particular related to BGP) ?
>
> Rgs,
> R.
>
> On Tue, Nov 27, 2012 at 5:28 PM, Larry Blunk <ljb@merit.edu> wrote:
>> On 11/27/2012 11:17 AM, Robert Raszuk wrote:
>>> Hello,
>>>
>>> Does anyone (in particular cc-ed authors) recall what is the status,
>>> planned update, planned progress to RFC of this document:
>>>
>>> http://tools.ietf.org/id/draft-ietf-grow-mrt-04.txt
>>>
>>> Thx,
>>> R.
>>>
>>   It's an RFC now --
>>
>> http://tools.ietf.org/html/rfc6396
>>
>>   Unfortunately, section 4.3.4 does not match the
>> current Quagga/libbgpdump implementations.  The RFC
>> says to omit the AFI/SAFI/NLRI fields in the MP_REACH_NLRI
>> attribute (since that info is already in the MRT
>> RIB Entry Header), but the current implementations
>> simply copy the attribute as-is in the RIB Entry
>> field.
>>
>>   Regards,
>>    Larry Blunk
>>
>>
> _______________________________________________
> GROW mailing list
> GROW@ietf.org
> https://www.ietf.org/mailman/listinfo/grow


From ljb@merit.edu  Tue Nov 27 08:45:04 2012
Return-Path: <ljb@merit.edu>
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 A030821F8506 for <grow@ietfa.amsl.com>; Tue, 27 Nov 2012 08:45:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I2q6W0TtpoUE for <grow@ietfa.amsl.com>; Tue, 27 Nov 2012 08:45:03 -0800 (PST)
Received: from sfpop-ironport02.merit.edu (sfpop-ironport02.merit.edu [207.75.116.68]) by ietfa.amsl.com (Postfix) with ESMTP id 7160721F84F9 for <grow@ietf.org>; Tue, 27 Nov 2012 08:45:03 -0800 (PST)
X-Merit-ExtLoop1: 1
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av4EAP/stFDGbD6X/2dsb2JhbABFwB6BCYIeAQEFOEABEAsYCRMDDwkDAgECAUUGDQEFAgEBiAkMsDaHRIkIjDqEQQOIXo0jgRyKG4UNgw5c
X-IronPort-AV: E=Sophos;i="4.83,328,1352091600"; d="scan'208";a="193587481"
Received: from ablate.merit.edu ([198.108.62.151]) by sfpop-ironport02.merit.edu with ESMTP; 27 Nov 2012 11:45:00 -0500
Message-ID: <50B4EE0C.4070803@merit.edu>
Date: Tue, 27 Nov 2012 11:45:00 -0500
From: Larry Blunk <ljb@merit.edu>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Robert Raszuk <robert@raszuk.net>
References: <CA+b+ERk0A1Kkex-f2goRv5Wa+GOXENMgXqA52myHzxO23bJfvA@mail.gmail.com> <50B4EA44.7090502@merit.edu> <CA+b+ERm0DKs5Pzk5c0e2PJaQeMHvK1Y6Yqwvg0_G88ibjhoUTw@mail.gmail.com>
In-Reply-To: <CA+b+ERm0DKs5Pzk5c0e2PJaQeMHvK1Y6Yqwvg0_G88ibjhoUTw@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: mkarir@merit.edu, grow@ietf.org
Subject: Re: [GROW] MRT
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, 27 Nov 2012 16:45:04 -0000

   libbgpdump is available at http://www.ris.ripe.net/source/ and
contains the bgpdump tool which will read and process the table dump
and update files in the Routeviews and RIPE RIS archives.

  -Larry


On 11/27/2012 11:33 AM, Robert Raszuk wrote:
> Thx Larry !
>
> Any pointer to best MRT opensource tools repository for parsing the
> messages and maybe even performing some analysis on them (in
> particular related to BGP) ?
>
> Rgs,
> R.
>
> On Tue, Nov 27, 2012 at 5:28 PM, Larry Blunk <ljb@merit.edu> wrote:
>> On 11/27/2012 11:17 AM, Robert Raszuk wrote:
>>>
>>> Hello,
>>>
>>> Does anyone (in particular cc-ed authors) recall what is the status,
>>> planned update, planned progress to RFC of this document:
>>>
>>> http://tools.ietf.org/id/draft-ietf-grow-mrt-04.txt
>>>
>>> Thx,
>>> R.
>>>
>>
>>   It's an RFC now --
>>
>> http://tools.ietf.org/html/rfc6396
>>
>>   Unfortunately, section 4.3.4 does not match the
>> current Quagga/libbgpdump implementations.  The RFC
>> says to omit the AFI/SAFI/NLRI fields in the MP_REACH_NLRI
>> attribute (since that info is already in the MRT
>> RIB Entry Header), but the current implementations
>> simply copy the attribute as-is in the RIB Entry
>> field.
>>
>>   Regards,
>>    Larry Blunk
>>
>>


From rraszuk@gmail.com  Tue Nov 27 08:52:13 2012
Return-Path: <rraszuk@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 2470921F8665 for <grow@ietfa.amsl.com>; Tue, 27 Nov 2012 08:52:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.977
X-Spam-Level: 
X-Spam-Status: No, score=-2.977 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8LpMyTtdJS-h for <grow@ietfa.amsl.com>; Tue, 27 Nov 2012 08:52:12 -0800 (PST)
Received: from mail-ie0-f172.google.com (mail-ie0-f172.google.com [209.85.223.172]) by ietfa.amsl.com (Postfix) with ESMTP id 6EEB721F8740 for <grow@ietf.org>; Tue, 27 Nov 2012 08:52:09 -0800 (PST)
Received: by mail-ie0-f172.google.com with SMTP id c13so12104252ieb.31 for <grow@ietf.org>; Tue, 27 Nov 2012 08:52:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=+P0ze5XQFgK5efguH7gMcZQCR+Y/lkCfjIuxSQdSW+0=; b=d42yFc3klicXkKNZphzHipSVJrUQY/DCZj32jp1cVGKqqBDW4RohtZ8hbtrngcfAs2 VVMiA0oJ28Id2VsKBDgG1OIXV/u7pj8vcXw16QyqYOqCymKY7NhWg4hgUgVspqPPhG74 BjR8KvKNw4z24JeTOMnRoB/NfptzZ/5EOOp2ne4k1t4Guf/Kk9UzzGRqHjud5rvA/qYI 0rDru6AdhgZ9VUBiqkm2LnudgHqRvgkxMwHooCUXdHt+3JKJ78WVUAtzQcAhsMf368R7 VbeqlBLxGn+Ha7ri/BfQX67SmJbwwgubppiEyy4Gt+vnMV0N54fxomb42bp9oV1g1fyt yFAQ==
MIME-Version: 1.0
Received: by 10.50.202.97 with SMTP id kh1mr19026256igc.15.1354035129322; Tue, 27 Nov 2012 08:52:09 -0800 (PST)
Sender: rraszuk@gmail.com
Received: by 10.42.222.133 with HTTP; Tue, 27 Nov 2012 08:52:09 -0800 (PST)
In-Reply-To: <50B4EE0C.4070803@merit.edu>
References: <CA+b+ERk0A1Kkex-f2goRv5Wa+GOXENMgXqA52myHzxO23bJfvA@mail.gmail.com> <50B4EA44.7090502@merit.edu> <CA+b+ERm0DKs5Pzk5c0e2PJaQeMHvK1Y6Yqwvg0_G88ibjhoUTw@mail.gmail.com> <50B4EE0C.4070803@merit.edu>
Date: Tue, 27 Nov 2012 17:52:09 +0100
X-Google-Sender-Auth: 9tBzGmjwVsujU06JKE8it3mUi_Y
Message-ID: <CA+b+ERnbdC9GdhyUOLSUtLm+MY032eWydaUqfJVVWNdJKNOiyw@mail.gmail.com>
From: Robert Raszuk <robert@raszuk.net>
To: Larry Blunk <ljb@merit.edu>
Content-Type: text/plain; charset=ISO-8859-1
Cc: mkarir@merit.edu, grow@ietf.org
Subject: Re: [GROW] MRT
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, 27 Nov 2012 16:52:13 -0000

Thx again both Larry and Mattia,

Actually I am more looking for parsing MRT BGP4MP_MESSAGE containing
bunch of raw UPDATE messages from peers rather then table dumps.

However libbgpdump seems like a good starting point ... if for nothing
else then for parsing common message headers.

Many thx,
R.


On Tue, Nov 27, 2012 at 5:45 PM, Larry Blunk <ljb@merit.edu> wrote:
>
>   libbgpdump is available at http://www.ris.ripe.net/source/ and
> contains the bgpdump tool which will read and process the table dump
> and update files in the Routeviews and RIPE RIS archives.
>
>  -Larry
>
>
>
> On 11/27/2012 11:33 AM, Robert Raszuk wrote:
>>
>> Thx Larry !
>>
>> Any pointer to best MRT opensource tools repository for parsing the
>> messages and maybe even performing some analysis on them (in
>> particular related to BGP) ?
>>
>> Rgs,
>> R.
>>
>> On Tue, Nov 27, 2012 at 5:28 PM, Larry Blunk <ljb@merit.edu> wrote:
>>>
>>> On 11/27/2012 11:17 AM, Robert Raszuk wrote:
>>>>
>>>>
>>>> Hello,
>>>>
>>>> Does anyone (in particular cc-ed authors) recall what is the status,
>>>> planned update, planned progress to RFC of this document:
>>>>
>>>> http://tools.ietf.org/id/draft-ietf-grow-mrt-04.txt
>>>>
>>>> Thx,
>>>> R.
>>>>
>>>
>>>   It's an RFC now --
>>>
>>> http://tools.ietf.org/html/rfc6396
>>>
>>>   Unfortunately, section 4.3.4 does not match the
>>> current Quagga/libbgpdump implementations.  The RFC
>>> says to omit the AFI/SAFI/NLRI fields in the MP_REACH_NLRI
>>> attribute (since that info is already in the MRT
>>> RIB Entry Header), but the current implementations
>>> simply copy the attribute as-is in the RIB Entry
>>> field.
>>>
>>>   Regards,
>>>    Larry Blunk
>>>
>>>
>

From ljb@merit.edu  Tue Nov 27 09:32:02 2012
Return-Path: <ljb@merit.edu>
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 74BF821F85D9 for <grow@ietfa.amsl.com>; Tue, 27 Nov 2012 09:32:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5UOdtRiO9Qoz for <grow@ietfa.amsl.com>; Tue, 27 Nov 2012 09:32:01 -0800 (PST)
Received: from sfpop-ironport07.merit.edu (sfpop-ironport07.merit.edu [207.75.116.66]) by ietfa.amsl.com (Postfix) with ESMTP id AEF9D21F84DD for <grow@ietf.org>; Tue, 27 Nov 2012 09:32:01 -0800 (PST)
X-Merit-ExtLoop1: 1
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av4EAJf3tFDGbD6X/2dsb2JhbABFwB6BCYIeAQEFOEABEAsYCRMDDwkDAgECAUUGDQEFAgEBiAkMsCyHQ4kIjDqEQQOIXo0jgRyKG4UNgw5c
X-IronPort-AV: E=Sophos;i="4.83,328,1352091600"; d="scan'208";a="187298094"
Received: from ablate.merit.edu ([198.108.62.151]) by sfpop-ironport07.merit.edu with ESMTP; 27 Nov 2012 12:32:00 -0500
Message-ID: <50B4F910.4020000@merit.edu>
Date: Tue, 27 Nov 2012 12:32:00 -0500
From: Larry Blunk <ljb@merit.edu>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Robert Raszuk <robert@raszuk.net>
References: <CA+b+ERk0A1Kkex-f2goRv5Wa+GOXENMgXqA52myHzxO23bJfvA@mail.gmail.com> <50B4EA44.7090502@merit.edu> <CA+b+ERm0DKs5Pzk5c0e2PJaQeMHvK1Y6Yqwvg0_G88ibjhoUTw@mail.gmail.com> <50B4EE0C.4070803@merit.edu> <CA+b+ERnbdC9GdhyUOLSUtLm+MY032eWydaUqfJVVWNdJKNOiyw@mail.gmail.com>
In-Reply-To: <CA+b+ERnbdC9GdhyUOLSUtLm+MY032eWydaUqfJVVWNdJKNOiyw@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: mkarir@merit.edu, grow@ietf.org
Subject: Re: [GROW] MRT
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, 27 Nov 2012 17:32:02 -0000

   libbgpdump supports both the BGP4MP_MESSAGE UPDATE message MRT type
  and the TABLE_DUMP/TABLE_DUMP_V2 table dump types.

  -Larry



On 11/27/2012 11:52 AM, Robert Raszuk wrote:
> Thx again both Larry and Mattia,
>
> Actually I am more looking for parsing MRT BGP4MP_MESSAGE containing
> bunch of raw UPDATE messages from peers rather then table dumps.
>
> However libbgpdump seems like a good starting point ... if for nothing
> else then for parsing common message headers.
>
> Many thx,
> R.
>
>
> On Tue, Nov 27, 2012 at 5:45 PM, Larry Blunk <ljb@merit.edu> wrote:
>>
>>    libbgpdump is available at http://www.ris.ripe.net/source/ and
>> contains the bgpdump tool which will read and process the table dump
>> and update files in the Routeviews and RIPE RIS archives.
>>
>>   -Larry
>>
>>
>>
>> On 11/27/2012 11:33 AM, Robert Raszuk wrote:
>>>
>>> Thx Larry !
>>>
>>> Any pointer to best MRT opensource tools repository for parsing the
>>> messages and maybe even performing some analysis on them (in
>>> particular related to BGP) ?
>>>
>>> Rgs,
>>> R.
>>>
>>> On Tue, Nov 27, 2012 at 5:28 PM, Larry Blunk <ljb@merit.edu> wrote:
>>>>
>>>> On 11/27/2012 11:17 AM, Robert Raszuk wrote:
>>>>>
>>>>>
>>>>> Hello,
>>>>>
>>>>> Does anyone (in particular cc-ed authors) recall what is the status,
>>>>> planned update, planned progress to RFC of this document:
>>>>>
>>>>> http://tools.ietf.org/id/draft-ietf-grow-mrt-04.txt
>>>>>
>>>>> Thx,
>>>>> R.
>>>>>
>>>>
>>>>    It's an RFC now --
>>>>
>>>> http://tools.ietf.org/html/rfc6396
>>>>
>>>>    Unfortunately, section 4.3.4 does not match the
>>>> current Quagga/libbgpdump implementations.  The RFC
>>>> says to omit the AFI/SAFI/NLRI fields in the MP_REACH_NLRI
>>>> attribute (since that info is already in the MRT
>>>> RIB Entry Header), but the current implementations
>>>> simply copy the attribute as-is in the RIB Entry
>>>> field.
>>>>
>>>>    Regards,
>>>>     Larry Blunk
>>>>
>>>>
>>


From christopher.morrow@gmail.com  Tue Nov 27 09:58:31 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 40DAA21F85E1 for <grow@ietfa.amsl.com>; Tue, 27 Nov 2012 09:58:31 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EJ8zZK8bHhmB for <grow@ietfa.amsl.com>; Tue, 27 Nov 2012 09:58:30 -0800 (PST)
Received: from mail-ee0-f44.google.com (mail-ee0-f44.google.com [74.125.83.44]) by ietfa.amsl.com (Postfix) with ESMTP id 6F8C821F8563 for <grow@ietf.org>; Tue, 27 Nov 2012 09:58:30 -0800 (PST)
Received: by mail-ee0-f44.google.com with SMTP id b47so7929165eek.31 for <grow@ietf.org>; Tue, 27 Nov 2012 09:58:29 -0800 (PST)
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; bh=efS/N+zt7E/ZaLZZgwePSmy9v0Dqex095bom0mEcdcE=; b=J9d95/TbmFuQyGZ5x4H/XrZPH/e+vWgla8aytupqwYGVRs3hDHt8VJwl6Uv9Ng2KcX ge4Qk/frv/y6WjBF7vEC2Mkz31k1eL+mHqzLNJBJ9BXJ99G2hGDF8ABTaL74gS3c2EYT aV50uCPFGvpVPYh9rvoWaitgTcVxKQ/Acj4ozc3R7+dRlEuUnSNtn7yc/EjQpMI7uyMq UuPpNhaRC0xwOt9UWOeAqgHJ/Dsgn8kG2UM1Tll6PT5RWjh7AqNuSDGl8ZI9TJIj6eFp rRz62wuWRDn14H4k54hz2gr9sY1auG4YChbBXaqWK4CsxSfi7svLJpR4m2Hnmo/wFGSq ZS5A==
MIME-Version: 1.0
Received: by 10.14.223.200 with SMTP id v48mr60618520eep.24.1354039109607; Tue, 27 Nov 2012 09:58:29 -0800 (PST)
Received: by 10.223.96.5 with HTTP; Tue, 27 Nov 2012 09:58:29 -0800 (PST)
In-Reply-To: <50B4EDB0.6040102@gmail.com>
References: <CA+b+ERk0A1Kkex-f2goRv5Wa+GOXENMgXqA52myHzxO23bJfvA@mail.gmail.com> <50B4EA44.7090502@merit.edu> <CA+b+ERm0DKs5Pzk5c0e2PJaQeMHvK1Y6Yqwvg0_G88ibjhoUTw@mail.gmail.com> <50B4EDB0.6040102@gmail.com>
Date: Tue, 27 Nov 2012 12:58:29 -0500
Message-ID: <CAL9jLaagOxmx6na-TTyuZB_ochQ5LOLOCr3RJz=CGFKvC_WRqQ@mail.gmail.com>
From: Christopher Morrow <christopher.morrow@gmail.com>
To: Mattia Rossi <mattia.rossi.mailinglists@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: grow@ietf.org
Subject: Re: [GROW] MRT
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, 27 Nov 2012 17:58:31 -0000

On Tue, Nov 27, 2012 at 11:43 AM, Mattia Rossi
<mattia.rossi.mailinglists@gmail.com> wrote:
> (http://jon.oberheide.org/projects/pybgpdump/) which is very nice for a
> quick analysis of MRT dumps.

sadly jon's tool is ... not very well updated :( or gives me lots and
LOTS of error messages on reading current routeviews/ris update
streams :(

(noting i know this from attempting to parse those update files around
the time of the moratel leak of google ip space ~2 wks ago).

From jared@puck.nether.net  Tue Nov 27 10:21:06 2012
Return-Path: <jared@puck.nether.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 E2C2E21F8671 for <grow@ietfa.amsl.com>; Tue, 27 Nov 2012 10:21:06 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8fuGiMvyL3Aq for <grow@ietfa.amsl.com>; Tue, 27 Nov 2012 10:21:06 -0800 (PST)
Received: from puck.nether.net (puck.nether.net [IPv6:2001:418:3f4::5]) by ietfa.amsl.com (Postfix) with ESMTP id 18F7721F861F for <grow@ietf.org>; Tue, 27 Nov 2012 10:21:06 -0800 (PST)
Received: from [10.0.0.137] (173-167-0-105-michigan.hfc.comcastbusiness.net [173.167.0.105]) (authenticated bits=0) by puck.nether.net (8.14.4/8.14.4) with ESMTP id qARIKwU0011007 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 27 Nov 2012 13:20:59 -0500
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=us-ascii
From: Jared Mauch <jared@puck.nether.net>
In-Reply-To: <CAL9jLaagOxmx6na-TTyuZB_ochQ5LOLOCr3RJz=CGFKvC_WRqQ@mail.gmail.com>
Date: Tue, 27 Nov 2012 13:20:58 -0500
Content-Transfer-Encoding: 7bit
Message-Id: <329D9664-957F-4682-85FC-E8028CC37EE1@puck.nether.net>
References: <CA+b+ERk0A1Kkex-f2goRv5Wa+GOXENMgXqA52myHzxO23bJfvA@mail.gmail.com> <50B4EA44.7090502@merit.edu> <CA+b+ERm0DKs5Pzk5c0e2PJaQeMHvK1Y6Yqwvg0_G88ibjhoUTw@mail.gmail.com> <50B4EDB0.6040102@gmail.com> <CAL9jLaagOxmx6na-TTyuZB_ochQ5LOLOCr3RJz=CGFKvC_WRqQ@mail.gmail.com>
To: Christopher Morrow <christopher.morrow@gmail.com>
X-Mailer: Apple Mail (2.1283)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (puck.nether.net [204.42.254.5]); Tue, 27 Nov 2012 13:20:59 -0500 (EST)
Cc: grow@ietf.org
Subject: Re: [GROW] MRT
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, 27 Nov 2012 18:21:07 -0000

On Nov 27, 2012, at 12:58 PM, Christopher Morrow wrote:

> On Tue, Nov 27, 2012 at 11:43 AM, Mattia Rossi
> <mattia.rossi.mailinglists@gmail.com> wrote:
>> (http://jon.oberheide.org/projects/pybgpdump/) which is very nice for a
>> quick analysis of MRT dumps.
> 
> sadly jon's tool is ... not very well updated :( or gives me lots and
> LOTS of error messages on reading current routeviews/ris update
> streams :(
> 
> (noting i know this from attempting to parse those update files around
> the time of the moratel leak of google ip space ~2 wks ago).'

The MRT file parser I sent you should work.

- Jared


From christopher.morrow@gmail.com  Tue Nov 27 10:41:23 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 B8D0A21F85C0 for <grow@ietfa.amsl.com>; Tue, 27 Nov 2012 10:41:23 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9wKo8Cw6LYQM for <grow@ietfa.amsl.com>; Tue, 27 Nov 2012 10:41:23 -0800 (PST)
Received: from mail-ee0-f44.google.com (mail-ee0-f44.google.com [74.125.83.44]) by ietfa.amsl.com (Postfix) with ESMTP id 994F521F8741 for <grow@ietf.org>; Tue, 27 Nov 2012 10:41:22 -0800 (PST)
Received: by mail-ee0-f44.google.com with SMTP id b47so7955100eek.31 for <grow@ietf.org>; Tue, 27 Nov 2012 10:41:16 -0800 (PST)
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; bh=finN/ALymmcAQOHXms2ntYLxpvI+afcPuUx4bjwmeo4=; b=weVzswm7ZHkLo47GC6XeU8dlnczPIsY2T2qJ3W8zzsVNrZX8IxYChVSzLTFcWb5W5W JrkgR8Bi9vlu5gtGYjkQfK3btdN9Sa1f/m2NaYObelOfW1nsr46pCNUhLbD/zwaivcg6 HqQlaX4O+y+GEqNKabgJFOcjAa8VAxWbHPK2GwNmOSOifpJ+jiwuuyDtzs+UtRuWkOV6 3uWFUz137Xy+RiKqH1GABmc0LEMeERa0czeH5AiyznvgpekRD/t7qLF7wvVKN1SVmWeM xotqHtOQnlOAZiLddde0uB9kqSIUwnISNFphc6Kl0sWhd6BuK4Zcj2ZJnO8WlIz/eBR1 GiCQ==
MIME-Version: 1.0
Received: by 10.14.198.67 with SMTP id u43mr60985382een.7.1354041676586; Tue, 27 Nov 2012 10:41:16 -0800 (PST)
Received: by 10.223.96.5 with HTTP; Tue, 27 Nov 2012 10:41:16 -0800 (PST)
In-Reply-To: <329D9664-957F-4682-85FC-E8028CC37EE1@puck.nether.net>
References: <CA+b+ERk0A1Kkex-f2goRv5Wa+GOXENMgXqA52myHzxO23bJfvA@mail.gmail.com> <50B4EA44.7090502@merit.edu> <CA+b+ERm0DKs5Pzk5c0e2PJaQeMHvK1Y6Yqwvg0_G88ibjhoUTw@mail.gmail.com> <50B4EDB0.6040102@gmail.com> <CAL9jLaagOxmx6na-TTyuZB_ochQ5LOLOCr3RJz=CGFKvC_WRqQ@mail.gmail.com> <329D9664-957F-4682-85FC-E8028CC37EE1@puck.nether.net>
Date: Tue, 27 Nov 2012 13:41:16 -0500
Message-ID: <CAL9jLaYj+WOWVH92j-XOLXzoSKyTLVuc43rR2NdaPw_pG7k8qQ@mail.gmail.com>
From: Christopher Morrow <christopher.morrow@gmail.com>
To: Jared Mauch <jared@puck.nether.net>
Content-Type: text/plain; charset=ISO-8859-1
Cc: grow@ietf.org
Subject: Re: [GROW] MRT
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, 27 Nov 2012 18:41:23 -0000

On Tue, Nov 27, 2012 at 1:20 PM, Jared Mauch <jared@puck.nether.net> wrote:
>
> On Nov 27, 2012, at 12:58 PM, Christopher Morrow wrote:
>
>> On Tue, Nov 27, 2012 at 11:43 AM, Mattia Rossi
>> <mattia.rossi.mailinglists@gmail.com> wrote:
>>> (http://jon.oberheide.org/projects/pybgpdump/) which is very nice for a
>>> quick analysis of MRT dumps.
>>
>> sadly jon's tool is ... not very well updated :( or gives me lots and
>> LOTS of error messages on reading current routeviews/ris update
>> streams :(
>>
>> (noting i know this from attempting to parse those update files around
>> the time of the moratel leak of google ip space ~2 wks ago).'
>
> The MRT file parser I sent you should work.

yes, no :( or it didn't work at the time, perhaps I was being
ham-fisted... in the end there was an internal tool that worked well
enough for my purposes.

From aservin@lacnic.net  Wed Nov 28 04:01:15 2012
Return-Path: <aservin@lacnic.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 9CC6B21F87F5 for <grow@ietfa.amsl.com>; Wed, 28 Nov 2012 04:01:15 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vEUYJpqwfrg2 for <grow@ietfa.amsl.com>; Wed, 28 Nov 2012 04:01:14 -0800 (PST)
Received: from mail.lacnic.net.uy (mail.lacnic.net.uy [IPv6:2001:13c7:7001:4000::3]) by ietfa.amsl.com (Postfix) with ESMTP id 8FEDD21F85A2 for <grow@ietf.org>; Wed, 28 Nov 2012 04:01:14 -0800 (PST)
Received: from 85-7-200.lacnic.net.uy (unknown [IPv6:2001:13c7:7001:5128:752a:46c8:4cb:e9b2]) by mail.lacnic.net.uy (Postfix) with ESMTP id 149AA308432; Wed, 28 Nov 2012 10:01:11 -0200 (UYST)
Message-ID: <50B5FD06.2060008@lacnic.net>
Date: Wed, 28 Nov 2012 10:01:10 -0200
From: Arturo Servin <aservin@lacnic.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Christopher Morrow <christopher.morrow@gmail.com>
References: <CA+b+ERk0A1Kkex-f2goRv5Wa+GOXENMgXqA52myHzxO23bJfvA@mail.gmail.com> <50B4EA44.7090502@merit.edu> <CA+b+ERm0DKs5Pzk5c0e2PJaQeMHvK1Y6Yqwvg0_G88ibjhoUTw@mail.gmail.com> <50B4EDB0.6040102@gmail.com> <CAL9jLaagOxmx6na-TTyuZB_ochQ5LOLOCr3RJz=CGFKvC_WRqQ@mail.gmail.com> <329D9664-957F-4682-85FC-E8028CC37EE1@puck.nether.net> <CAL9jLaYj+WOWVH92j-XOLXzoSKyTLVuc43rR2NdaPw_pG7k8qQ@mail.gmail.com>
In-Reply-To: <CAL9jLaYj+WOWVH92j-XOLXzoSKyTLVuc43rR2NdaPw_pG7k8qQ@mail.gmail.com>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-LACNIC.uy-MailScanner-Information: Please contact the ISP for more information
X-LACNIC.uy-MailScanner: Found to be clean
X-LACNIC.uy-MailScanner-SpamCheck: 
X-LACNIC.uy-MailScanner-From: aservin@lacnic.net
Cc: grow@ietf.org
Subject: Re: [GROW] MRT
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, 28 Nov 2012 12:01:15 -0000

Chris,

	The problem that I had is that it pybgpdum requires dpkt and it did not
support 4 byte ASN and you need a hack.

	Not sure if that is was problem as well. If it were, let me know and I
will try to remember what I did to make it work but I think this is the
place with the answer:

http://caia.swin.edu.au/urp/bgp/tools.html

regards,
as

On 27/11/2012 16:41, Christopher Morrow wrote:
> On Tue, Nov 27, 2012 at 1:20 PM, Jared Mauch <jared@puck.nether.net> wrote:
>>
>> On Nov 27, 2012, at 12:58 PM, Christopher Morrow wrote:
>>
>>> On Tue, Nov 27, 2012 at 11:43 AM, Mattia Rossi
>>> <mattia.rossi.mailinglists@gmail.com> wrote:
>>>> (http://jon.oberheide.org/projects/pybgpdump/) which is very nice for a
>>>> quick analysis of MRT dumps.
>>>
>>> sadly jon's tool is ... not very well updated :( or gives me lots and
>>> LOTS of error messages on reading current routeviews/ris update
>>> streams :(
>>>
>>> (noting i know this from attempting to parse those update files around
>>> the time of the moratel leak of google ip space ~2 wks ago).'
>>
>> The MRT file parser I sent you should work.
> 
> yes, no :( or it didn't work at the time, perhaps I was being
> ham-fisted... in the end there was an internal tool that worked well
> enough for my purposes.
> _______________________________________________
> GROW mailing list
> GROW@ietf.org
> https://www.ietf.org/mailman/listinfo/grow
> 

From backup2.torres@gmail.com  Wed Nov 28 04:39:54 2012
Return-Path: <backup2.torres@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 577B821F841F for <grow@ietfa.amsl.com>; Wed, 28 Nov 2012 04:39:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.377
X-Spam-Level: 
X-Spam-Status: No, score=-2.377 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, J_CHICKENPOX_32=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AgBAqB5k3mu8 for <grow@ietfa.amsl.com>; Wed, 28 Nov 2012 04:39:53 -0800 (PST)
Received: from mail-ia0-f172.google.com (mail-ia0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id E316521F841E for <grow@ietf.org>; Wed, 28 Nov 2012 04:39:52 -0800 (PST)
Received: by mail-ia0-f172.google.com with SMTP id j26so10696184iaf.31 for <grow@ietf.org>; Wed, 28 Nov 2012 04:39:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=H+3lTAf+0Yf5lXokliv9pUOYcepxdAurqA8pvtn9l0g=; b=XopQp3Ih4+JEn6YlOpaA5kd/Vu2hefP/UDC1xRW/oHuk4bPOB2KFHsrnEZqhL694LW kVB3y7yNwoGlhxJTEzzXGNAXsYhcxRLoFgpQIX6skQM3hbVqUppP5eKKimqHZ4XrUo7h AELXCQpdyvzHqRx3CIMFz1mJJXMPDK8xm9zn4wZ8G/sPwaTtNRHPilvyfosN7yHk5Kay HH7JphCVX+SBkZrrw0yo6+xXAY2Z/VG4YLHKGO0Q6orZcZcJUtuipOsgUTFmurvHUYxQ hYd3G+gsaCSd65GHHZHUnkWdezn2Raz4ihf2k1Nubv6mPxf7twBD6sZYsfzcjkfWkMv7 7ZKA==
MIME-Version: 1.0
Received: by 10.50.220.199 with SMTP id py7mr21315934igc.34.1354106392333; Wed, 28 Nov 2012 04:39:52 -0800 (PST)
Sender: backup2.torres@gmail.com
Received: by 10.50.87.133 with HTTP; Wed, 28 Nov 2012 04:39:52 -0800 (PST)
In-Reply-To: <50B4F910.4020000@merit.edu>
References: <CA+b+ERk0A1Kkex-f2goRv5Wa+GOXENMgXqA52myHzxO23bJfvA@mail.gmail.com> <50B4EA44.7090502@merit.edu> <CA+b+ERm0DKs5Pzk5c0e2PJaQeMHvK1Y6Yqwvg0_G88ibjhoUTw@mail.gmail.com> <50B4EE0C.4070803@merit.edu> <CA+b+ERnbdC9GdhyUOLSUtLm+MY032eWydaUqfJVVWNdJKNOiyw@mail.gmail.com> <50B4F910.4020000@merit.edu>
Date: Wed, 28 Nov 2012 10:39:52 -0200
X-Google-Sender-Auth: EUQk9z3sTUu0IK4o8jB8armiYeU
Message-ID: <CAPfnYRhCh57wj0U+nE1MPS2K7YkRMvbXZX20Z4atYFVZ-u2mLw@mail.gmail.com>
From: Pedro Torres <torres@pop-pr.rnp.br>
To: Larry Blunk <ljb@merit.edu>
Content-Type: text/plain; charset=ISO-8859-1
Cc: mkarir@merit.edu, grow@ietf.org
Subject: Re: [GROW] MRT
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, 28 Nov 2012 12:39:54 -0000

Hello,

Yes, libbgpdump is a really great tool. We are using it with success.
The lib is fast and simple.
Unfortunately the source code still use some defines that not follow
RFC-6396, example: BGPDUMP_TYPE_ZEBRA_BGP instead BGP4MP.

https://bitbucket.org/ripencc/bgpdump/wiki/Home
They say: "This format is described in the Internet Draft grow-mrt-13."

According to what they says the lib follow a draft. I don't think it's
a big problem because no big changes was done since MRT draft 13 until
RFC-6396 but could be a good idea to update the documentation and
nomenclatures. The same should be done with Quagga bgpd daemon.

--
Pedro

On Tue, Nov 27, 2012 at 3:32 PM, Larry Blunk <ljb@merit.edu> wrote:
>
>   libbgpdump supports both the BGP4MP_MESSAGE UPDATE message MRT type
>  and the TABLE_DUMP/TABLE_DUMP_V2 table dump types.
>
>  -Larry
>
>
>
>
> On 11/27/2012 11:52 AM, Robert Raszuk wrote:
>>
>> Thx again both Larry and Mattia,
>>
>> Actually I am more looking for parsing MRT BGP4MP_MESSAGE containing
>> bunch of raw UPDATE messages from peers rather then table dumps.
>>
>> However libbgpdump seems like a good starting point ... if for nothing
>> else then for parsing common message headers.
>>
>> Many thx,
>> R.
>>
>>
>> On Tue, Nov 27, 2012 at 5:45 PM, Larry Blunk <ljb@merit.edu> wrote:
>>>
>>>
>>>    libbgpdump is available at http://www.ris.ripe.net/source/ and
>>> contains the bgpdump tool which will read and process the table dump
>>> and update files in the Routeviews and RIPE RIS archives.
>>>
>>>   -Larry
>>>
>>>
>>>
>>> On 11/27/2012 11:33 AM, Robert Raszuk wrote:
>>>>
>>>>
>>>> Thx Larry !
>>>>
>>>> Any pointer to best MRT opensource tools repository for parsing the
>>>> messages and maybe even performing some analysis on them (in
>>>> particular related to BGP) ?
>>>>
>>>> Rgs,
>>>> R.
>>>>
>>>> On Tue, Nov 27, 2012 at 5:28 PM, Larry Blunk <ljb@merit.edu> wrote:
>>>>>
>>>>>
>>>>> On 11/27/2012 11:17 AM, Robert Raszuk wrote:
>>>>>>
>>>>>>
>>>>>>
>>>>>> Hello,
>>>>>>
>>>>>> Does anyone (in particular cc-ed authors) recall what is the status,
>>>>>> planned update, planned progress to RFC of this document:
>>>>>>
>>>>>> http://tools.ietf.org/id/draft-ietf-grow-mrt-04.txt
>>>>>>
>>>>>> Thx,
>>>>>> R.
>>>>>>
>>>>>
>>>>>    It's an RFC now --
>>>>>
>>>>> http://tools.ietf.org/html/rfc6396
>>>>>
>>>>>    Unfortunately, section 4.3.4 does not match the
>>>>> current Quagga/libbgpdump implementations.  The RFC
>>>>> says to omit the AFI/SAFI/NLRI fields in the MP_REACH_NLRI
>>>>> attribute (since that info is already in the MRT
>>>>> RIB Entry Header), but the current implementations
>>>>> simply copy the attribute as-is in the RIB Entry
>>>>> field.
>>>>>
>>>>>    Regards,
>>>>>     Larry Blunk
>>>>>
>>>>>
>>>
>
> _______________________________________________
> GROW mailing list
> GROW@ietf.org
> https://www.ietf.org/mailman/listinfo/grow

From paaguti@gmail.com  Wed Nov 28 09:47:03 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 A96A121F8847 for <grow@ietfa.amsl.com>; Wed, 28 Nov 2012 09:47:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.999
X-Spam-Level: 
X-Spam-Status: No, score=-2.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_32=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TYncSXaEjpym for <grow@ietfa.amsl.com>; Wed, 28 Nov 2012 09:47:02 -0800 (PST)
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id 8B4F121F8860 for <grow@ietf.org>; Wed, 28 Nov 2012 09:47:02 -0800 (PST)
Received: by mail-pb0-f44.google.com with SMTP id uo1so9641596pbc.31 for <grow@ietf.org>; Wed, 28 Nov 2012 09:47:02 -0800 (PST)
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; bh=S89q/wBJie+n3VoGpTZ84/Okr718LdzPLGsorG4l2R0=; b=d9bFPrW5KQAFk7lEpfKkkPHdyY+x8wbp4WkJ+c/79Kgsi0/LztiUZ4BAjinuEApguQ wX9nHBD+4NJSy3w4fg96Gs79NNqQQLJGhJWGOEb33KzhbB+X2W/uOHIMTxSocgxe7FLc eMK/TOGoukwzhFnoprStoMHJO6e/hHK6K6IStWMruOpzpCJFwzyJpfzkaAxBhlh1EIuz T69K/JwC9apc/y6YbUGG3yOGsrfu4VoHaKwm1t6Ls8+PKJrxW1RjmIydUF5zRTmD1zRS i8Ph4+sK1YWnXgNg5OYjSl3gmGCGNngSoFyGx/IcDeMVkeUDVWvC/gCLmonPQu8Yf3a8 q73A==
MIME-Version: 1.0
Received: by 10.66.84.131 with SMTP id z3mr54158277pay.34.1354124822319; Wed, 28 Nov 2012 09:47:02 -0800 (PST)
Received: by 10.67.5.68 with HTTP; Wed, 28 Nov 2012 09:47:02 -0800 (PST)
In-Reply-To: <CAPfnYRhCh57wj0U+nE1MPS2K7YkRMvbXZX20Z4atYFVZ-u2mLw@mail.gmail.com>
References: <CA+b+ERk0A1Kkex-f2goRv5Wa+GOXENMgXqA52myHzxO23bJfvA@mail.gmail.com> <50B4EA44.7090502@merit.edu> <CA+b+ERm0DKs5Pzk5c0e2PJaQeMHvK1Y6Yqwvg0_G88ibjhoUTw@mail.gmail.com> <50B4EE0C.4070803@merit.edu> <CA+b+ERnbdC9GdhyUOLSUtLm+MY032eWydaUqfJVVWNdJKNOiyw@mail.gmail.com> <50B4F910.4020000@merit.edu> <CAPfnYRhCh57wj0U+nE1MPS2K7YkRMvbXZX20Z4atYFVZ-u2mLw@mail.gmail.com>
Date: Wed, 28 Nov 2012 18:47:02 +0100
Message-ID: <CAO48Bk_Hd1R5dUd+u6k1mYzXwXcGe-iW+ZeJus5GFCMKeiuhfA@mail.gmail.com>
From: Pedro Andres Aranda Gutierrez <paaguti@gmail.com>
To: grow@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Cc: mkarir@merit.edu
Subject: Re: [GROW] MRT
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, 28 Nov 2012 17:47:03 -0000

I had to write my own MRT parser library for my PhD. After my defense
next January, I plan to release it. (one step at a time, I'm quite
busy right now preparing the defense ;-) ) It's written in Java. Re:
pybgpdump, I have to agree it's a very nice tool once you patch dpkt
:-) re libbgpdump, it compiles, it helped me kick-start my research,
but that's it.

My .02 cents,

/Pedro A. Aranda

On Wed, Nov 28, 2012 at 1:39 PM, Pedro Torres <torres@pop-pr.rnp.br> wrote:
> Hello,
>
> Yes, libbgpdump is a really great tool. We are using it with success.
> The lib is fast and simple.
> Unfortunately the source code still use some defines that not follow
> RFC-6396, example: BGPDUMP_TYPE_ZEBRA_BGP instead BGP4MP.
>
> https://bitbucket.org/ripencc/bgpdump/wiki/Home
> They say: "This format is described in the Internet Draft grow-mrt-13."
>
> According to what they says the lib follow a draft. I don't think it's
> a big problem because no big changes was done since MRT draft 13 until
> RFC-6396 but could be a good idea to update the documentation and
> nomenclatures. The same should be done with Quagga bgpd daemon.
>
> --
> Pedro
>
> On Tue, Nov 27, 2012 at 3:32 PM, Larry Blunk <ljb@merit.edu> wrote:
>>
>>   libbgpdump supports both the BGP4MP_MESSAGE UPDATE message MRT type
>>  and the TABLE_DUMP/TABLE_DUMP_V2 table dump types.
>>
>>  -Larry
>>
>>
>>
>>
>> On 11/27/2012 11:52 AM, Robert Raszuk wrote:
>>>
>>> Thx again both Larry and Mattia,
>>>
>>> Actually I am more looking for parsing MRT BGP4MP_MESSAGE containing
>>> bunch of raw UPDATE messages from peers rather then table dumps.
>>>
>>> However libbgpdump seems like a good starting point ... if for nothing
>>> else then for parsing common message headers.
>>>
>>> Many thx,
>>> R.
>>>
>>>
>>> On Tue, Nov 27, 2012 at 5:45 PM, Larry Blunk <ljb@merit.edu> wrote:
>>>>
>>>>
>>>>    libbgpdump is available at http://www.ris.ripe.net/source/ and
>>>> contains the bgpdump tool which will read and process the table dump
>>>> and update files in the Routeviews and RIPE RIS archives.
>>>>
>>>>   -Larry
>>>>
>>>>
>>>>
>>>> On 11/27/2012 11:33 AM, Robert Raszuk wrote:
>>>>>
>>>>>
>>>>> Thx Larry !
>>>>>
>>>>> Any pointer to best MRT opensource tools repository for parsing the
>>>>> messages and maybe even performing some analysis on them (in
>>>>> particular related to BGP) ?
>>>>>
>>>>> Rgs,
>>>>> R.
>>>>>
>>>>> On Tue, Nov 27, 2012 at 5:28 PM, Larry Blunk <ljb@merit.edu> wrote:
>>>>>>
>>>>>>
>>>>>> On 11/27/2012 11:17 AM, Robert Raszuk wrote:
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Hello,
>>>>>>>
>>>>>>> Does anyone (in particular cc-ed authors) recall what is the status,
>>>>>>> planned update, planned progress to RFC of this document:
>>>>>>>
>>>>>>> http://tools.ietf.org/id/draft-ietf-grow-mrt-04.txt
>>>>>>>
>>>>>>> Thx,
>>>>>>> R.
>>>>>>>
>>>>>>
>>>>>>    It's an RFC now --
>>>>>>
>>>>>> http://tools.ietf.org/html/rfc6396
>>>>>>
>>>>>>    Unfortunately, section 4.3.4 does not match the
>>>>>> current Quagga/libbgpdump implementations.  The RFC
>>>>>> says to omit the AFI/SAFI/NLRI fields in the MP_REACH_NLRI
>>>>>> attribute (since that info is already in the MRT
>>>>>> RIB Entry Header), but the current implementations
>>>>>> simply copy the attribute as-is in the RIB Entry
>>>>>> field.
>>>>>>
>>>>>>    Regards,
>>>>>>     Larry Blunk
>>>>>>
>>>>>>
>>>>
>>
>> _______________________________________________
>> 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 christopher.morrow@gmail.com  Wed Nov 28 10:41:40 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 E1A2121F8201 for <grow@ietfa.amsl.com>; Wed, 28 Nov 2012 10:41:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.999
X-Spam-Level: 
X-Spam-Status: No, score=-102.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_32=0.6, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id b8IS2qIgr9yQ for <grow@ietfa.amsl.com>; Wed, 28 Nov 2012 10:41:40 -0800 (PST)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id D885221F8588 for <grow@ietf.org>; Wed, 28 Nov 2012 10:41:39 -0800 (PST)
Received: by mail-vb0-f44.google.com with SMTP id fc26so6711448vbb.31 for <grow@ietf.org>; Wed, 28 Nov 2012 10:41:37 -0800 (PST)
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; bh=qWhsYGcS4TTTGQQWNH+nhAFFsfjX1rwcLbUPuL+400M=; b=Mpp/o/Rk73lZZ/2LDWGJLRVcZ3H5/huwqGxGlyi4iZnW/V+FQsZC9sjksxAW1UuU2V +kPq3Sh0UTy5BDDHUNrvKdQuSGZcF+tmHs2vvBQsrY+a64F0bBTzQuG8v4Cy/RwD+SzL wHcZoel5tQoxHtMC1NcNmF+DtHCCEzST5SM5dfvZIwD12zZZOW50Uy/O9ZGK8r6sklRy SEgqgqhivVYbYeu8fQX+XU8tkkSZUFVjOBgqEC6Cx2tb+y16OqAnEjguRhf/LmlbQ/Z2 QUbDw7FEl28lDSLRDx9uhMfr6DElBhWDockOuiaF0AEja5XbIfvOzEvydN/AUzmz4VXp 2ROw==
MIME-Version: 1.0
Received: by 10.52.73.10 with SMTP id h10mr22738697vdv.97.1354128097212; Wed, 28 Nov 2012 10:41:37 -0800 (PST)
Received: by 10.58.205.148 with HTTP; Wed, 28 Nov 2012 10:41:37 -0800 (PST)
In-Reply-To: <CAO48Bk_Hd1R5dUd+u6k1mYzXwXcGe-iW+ZeJus5GFCMKeiuhfA@mail.gmail.com>
References: <CA+b+ERk0A1Kkex-f2goRv5Wa+GOXENMgXqA52myHzxO23bJfvA@mail.gmail.com> <50B4EA44.7090502@merit.edu> <CA+b+ERm0DKs5Pzk5c0e2PJaQeMHvK1Y6Yqwvg0_G88ibjhoUTw@mail.gmail.com> <50B4EE0C.4070803@merit.edu> <CA+b+ERnbdC9GdhyUOLSUtLm+MY032eWydaUqfJVVWNdJKNOiyw@mail.gmail.com> <50B4F910.4020000@merit.edu> <CAPfnYRhCh57wj0U+nE1MPS2K7YkRMvbXZX20Z4atYFVZ-u2mLw@mail.gmail.com> <CAO48Bk_Hd1R5dUd+u6k1mYzXwXcGe-iW+ZeJus5GFCMKeiuhfA@mail.gmail.com>
Date: Wed, 28 Nov 2012 13:41:37 -0500
Message-ID: <CAL9jLaYD9fL5gdaAb5LX6zD4i7tGg5+z--+mP_HaNvik6UqPLg@mail.gmail.com>
From: Christopher Morrow <christopher.morrow@gmail.com>
To: Pedro Andres Aranda Gutierrez <paaguti@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: mkarir@merit.edu, grow@ietf.org
Subject: Re: [GROW] MRT
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, 28 Nov 2012 18:41:41 -0000

On Wed, Nov 28, 2012 at 12:47 PM, Pedro Andres Aranda Gutierrez
<paaguti@gmail.com> wrote:
> I had to write my own MRT parser library for my PhD. After my defense
> next January, I plan to release it. (one step at a time, I'm quite
> busy right now preparing the defense ;-) ) It's written in Java. Re:
> pybgpdump, I have to agree it's a very nice tool once you patch dpkt

how about we send the diff to dug and have him patch dpkt? :)

> :-) re libbgpdump, it compiles, it helped me kick-start my research,
> but that's it.
>
> My .02 cents,
>
> /Pedro A. Aranda
>
> On Wed, Nov 28, 2012 at 1:39 PM, Pedro Torres <torres@pop-pr.rnp.br> wrote:
>> Hello,
>>
>> Yes, libbgpdump is a really great tool. We are using it with success.
>> The lib is fast and simple.
>> Unfortunately the source code still use some defines that not follow
>> RFC-6396, example: BGPDUMP_TYPE_ZEBRA_BGP instead BGP4MP.
>>
>> https://bitbucket.org/ripencc/bgpdump/wiki/Home
>> They say: "This format is described in the Internet Draft grow-mrt-13."
>>
>> According to what they says the lib follow a draft. I don't think it's
>> a big problem because no big changes was done since MRT draft 13 until
>> RFC-6396 but could be a good idea to update the documentation and
>> nomenclatures. The same should be done with Quagga bgpd daemon.
>>
>> --
>> Pedro
>>
>> On Tue, Nov 27, 2012 at 3:32 PM, Larry Blunk <ljb@merit.edu> wrote:
>>>
>>>   libbgpdump supports both the BGP4MP_MESSAGE UPDATE message MRT type
>>>  and the TABLE_DUMP/TABLE_DUMP_V2 table dump types.
>>>
>>>  -Larry
>>>
>>>
>>>
>>>
>>> On 11/27/2012 11:52 AM, Robert Raszuk wrote:
>>>>
>>>> Thx again both Larry and Mattia,
>>>>
>>>> Actually I am more looking for parsing MRT BGP4MP_MESSAGE containing
>>>> bunch of raw UPDATE messages from peers rather then table dumps.
>>>>
>>>> However libbgpdump seems like a good starting point ... if for nothing
>>>> else then for parsing common message headers.
>>>>
>>>> Many thx,
>>>> R.
>>>>
>>>>
>>>> On Tue, Nov 27, 2012 at 5:45 PM, Larry Blunk <ljb@merit.edu> wrote:
>>>>>
>>>>>
>>>>>    libbgpdump is available at http://www.ris.ripe.net/source/ and
>>>>> contains the bgpdump tool which will read and process the table dump
>>>>> and update files in the Routeviews and RIPE RIS archives.
>>>>>
>>>>>   -Larry
>>>>>
>>>>>
>>>>>
>>>>> On 11/27/2012 11:33 AM, Robert Raszuk wrote:
>>>>>>
>>>>>>
>>>>>> Thx Larry !
>>>>>>
>>>>>> Any pointer to best MRT opensource tools repository for parsing the
>>>>>> messages and maybe even performing some analysis on them (in
>>>>>> particular related to BGP) ?
>>>>>>
>>>>>> Rgs,
>>>>>> R.
>>>>>>
>>>>>> On Tue, Nov 27, 2012 at 5:28 PM, Larry Blunk <ljb@merit.edu> wrote:
>>>>>>>
>>>>>>>
>>>>>>> On 11/27/2012 11:17 AM, Robert Raszuk wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Hello,
>>>>>>>>
>>>>>>>> Does anyone (in particular cc-ed authors) recall what is the status,
>>>>>>>> planned update, planned progress to RFC of this document:
>>>>>>>>
>>>>>>>> http://tools.ietf.org/id/draft-ietf-grow-mrt-04.txt
>>>>>>>>
>>>>>>>> Thx,
>>>>>>>> R.
>>>>>>>>
>>>>>>>
>>>>>>>    It's an RFC now --
>>>>>>>
>>>>>>> http://tools.ietf.org/html/rfc6396
>>>>>>>
>>>>>>>    Unfortunately, section 4.3.4 does not match the
>>>>>>> current Quagga/libbgpdump implementations.  The RFC
>>>>>>> says to omit the AFI/SAFI/NLRI fields in the MP_REACH_NLRI
>>>>>>> attribute (since that info is already in the MRT
>>>>>>> RIB Entry Header), but the current implementations
>>>>>>> simply copy the attribute as-is in the RIB Entry
>>>>>>> field.
>>>>>>>
>>>>>>>    Regards,
>>>>>>>     Larry Blunk
>>>>>>>
>>>>>>>
>>>>>
>>>
>>> _______________________________________________
>>> 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
> _______________________________________________
> GROW mailing list
> GROW@ietf.org
> https://www.ietf.org/mailman/listinfo/grow

From cjeker@diehard.n-r-g.com  Wed Nov 28 22:42:15 2012
Return-Path: <cjeker@diehard.n-r-g.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 D379221F8A11 for <grow@ietfa.amsl.com>; Wed, 28 Nov 2012 22:42:15 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 686odWra5lBh for <grow@ietfa.amsl.com>; Wed, 28 Nov 2012 22:42:14 -0800 (PST)
Received: from diehard.n-r-g.com (diehard.n-r-g.com [62.48.3.9]) by ietfa.amsl.com (Postfix) with ESMTP id 0FAFA21F8A0D for <grow@ietf.org>; Wed, 28 Nov 2012 22:42:04 -0800 (PST)
Received: (qmail 25686 invoked by uid 1001); 29 Nov 2012 06:42:00 -0000
Date: Thu, 29 Nov 2012 07:42:00 +0100
From: Claudio Jeker <cjeker@diehard.n-r-g.com>
To: grow@ietf.org
Message-ID: <20121129064200.GF11066@diehard.n-r-g.com>
References: <CA+b+ERk0A1Kkex-f2goRv5Wa+GOXENMgXqA52myHzxO23bJfvA@mail.gmail.com> <50B4EA44.7090502@merit.edu> <CA+b+ERm0DKs5Pzk5c0e2PJaQeMHvK1Y6Yqwvg0_G88ibjhoUTw@mail.gmail.com> <50B4EE0C.4070803@merit.edu> <CA+b+ERnbdC9GdhyUOLSUtLm+MY032eWydaUqfJVVWNdJKNOiyw@mail.gmail.com> <50B4F910.4020000@merit.edu> <CAPfnYRhCh57wj0U+nE1MPS2K7YkRMvbXZX20Z4atYFVZ-u2mLw@mail.gmail.com> <CAO48Bk_Hd1R5dUd+u6k1mYzXwXcGe-iW+ZeJus5GFCMKeiuhfA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAO48Bk_Hd1R5dUd+u6k1mYzXwXcGe-iW+ZeJus5GFCMKeiuhfA@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Subject: Re: [GROW] MRT
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, 29 Nov 2012 06:42:15 -0000

On Wed, Nov 28, 2012 at 06:47:02PM +0100, Pedro Andres Aranda Gutierrez wrote:
> I had to write my own MRT parser library for my PhD. After my defense
> next January, I plan to release it. (one step at a time, I'm quite
> busy right now preparing the defense ;-) ) It's written in Java. Re:
> pybgpdump, I have to agree it's a very nice tool once you patch dpkt
> :-) re libbgpdump, it compiles, it helped me kick-start my research,
> but that's it.
> 

OpenBGPD has a mrt parser in bgpctl. It is mainly for table dumps but
the basic framework for dumping bgp messages there. I have a diff that 
uses the tcpdump BGP protocol parser to dump those messages. If interested
just drop me a mail.

-- 
:wq Claudio

From mattia.rossi.mailinglists@gmail.com  Thu Nov 29 00:00:51 2012
Return-Path: <mattia.rossi.mailinglists@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 B82FC21F8860 for <grow@ietfa.amsl.com>; Thu, 29 Nov 2012 00:00:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.299
X-Spam-Level: 
X-Spam-Status: No, score=-3.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_32=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EVtGKk5HVqPW for <grow@ietfa.amsl.com>; Thu, 29 Nov 2012 00:00:50 -0800 (PST)
Received: from mail-bk0-f44.google.com (mail-bk0-f44.google.com [209.85.214.44]) by ietfa.amsl.com (Postfix) with ESMTP id 608CD21F8A47 for <grow@ietf.org>; Thu, 29 Nov 2012 00:00:50 -0800 (PST)
Received: by mail-bk0-f44.google.com with SMTP id w11so6798492bku.31 for <grow@ietf.org>; Thu, 29 Nov 2012 00:00:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=2sHvZ1+8JEhNSVTvfwtLW0RB4m1Pxn/eZO+RzDK49Dg=; b=sUzS3QeYAzFKHyBWubEYIVhx/j23bkF413lg6cryQ0BIbfZLcw8zDryr/9lEAj+2Gc g8hs+BUdloWzCcbsBvXngQOHzrrNbB89x2XVbBQIDzdPVRBoOep0n4yibde47YLsaAzx gI0dzoNBpQYM8i5KYV9oInZcnZv986lQBoP5X1KkDrj2jM9XB5osr03jYV1Du41G5K2n oIl3QRAhufm8UdMqMg59kNuTvDsZjRHcPJA7Pdk0CEGxPDFDn0nZ3+c9wFT/BKPd2XUt F4y5I8FjAx3Ac45Y/Ux2UalGB1LvXdiM0iXWLHEPnr0d3I3er+n1hWylf8q/8KmIVDK0 f98g==
Received: by 10.204.147.5 with SMTP id j5mr6389763bkv.49.1354176049255; Thu, 29 Nov 2012 00:00:49 -0800 (PST)
Received: from [192.168.0.121] (vpn.static.83-173-212-209.cybernet.ch. [83.173.212.209]) by mx.google.com with ESMTPS id v8sm235516bku.6.2012.11.29.00.00.47 (version=SSLv3 cipher=OTHER); Thu, 29 Nov 2012 00:00:48 -0800 (PST)
Message-ID: <50B7162D.5060406@gmail.com>
Date: Thu, 29 Nov 2012 09:00:45 +0100
From: Mattia Rossi <mattia.rossi.mailinglists@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: grow@ietf.org
References: <CA+b+ERk0A1Kkex-f2goRv5Wa+GOXENMgXqA52myHzxO23bJfvA@mail.gmail.com> <50B4EA44.7090502@merit.edu> <CA+b+ERm0DKs5Pzk5c0e2PJaQeMHvK1Y6Yqwvg0_G88ibjhoUTw@mail.gmail.com> <50B4EDB0.6040102@gmail.com> <CAL9jLaagOxmx6na-TTyuZB_ochQ5LOLOCr3RJz=CGFKvC_WRqQ@mail.gmail.com> <329D9664-957F-4682-85FC-E8028CC37EE1@puck.nether.net> <CAL9jLaYj+WOWVH92j-XOLXzoSKyTLVuc43rR2NdaPw_pG7k8qQ@mail.gmail.com> <50B5FD06.2060008@lacnic.net>
In-Reply-To: <50B5FD06.2060008@lacnic.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [GROW] MRT
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, 29 Nov 2012 08:00:51 -0000

Am 28.11.2012 13:01, schrieb Arturo Servin:
> Chris,
>
> 	The problem that I had is that it pybgpdum requires dpkt and it did not
> support 4 byte ASN and you need a hack.
>
> 	Not sure if that is was problem as well. If it were, let me know and I
> will try to remember what I did to make it work but I think this is the
> place with the answer:
>
> http://caia.swin.edu.au/urp/bgp/tools.html
>
Yes, the 4 Byte AS patch is part of the MDFMT. I would have hoped that 
by now somebody would have included it in dpkt, but it seems it didn't 
happen. The patch includes support for TABLE_DUMP_V2 as well, which is 
also not in dpkt by default.
Dpkt still has an issue with certain RIPE MRT dumps, as some of the 
BGP4MP messages in there contain more entries than a Python String can 
handle, and thus dpkt will crash. (Dpkt will try to read the whole 
BGP4MP message in one go into a Python String).

Cheers,

Mat

From mattia.rossi.mailinglists@gmail.com  Thu Nov 29 00:09:10 2012
Return-Path: <mattia.rossi.mailinglists@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 482AA21F89F7 for <grow@ietfa.amsl.com>; Thu, 29 Nov 2012 00:09:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.449
X-Spam-Level: 
X-Spam-Status: No, score=-3.449 tagged_above=-999 required=5 tests=[AWL=0.150,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d4UndhEjQ16G for <grow@ietfa.amsl.com>; Thu, 29 Nov 2012 00:09:09 -0800 (PST)
Received: from mail-bk0-f44.google.com (mail-bk0-f44.google.com [209.85.214.44]) by ietfa.amsl.com (Postfix) with ESMTP id 217BA21F89DE for <grow@ietf.org>; Thu, 29 Nov 2012 00:09:08 -0800 (PST)
Received: by mail-bk0-f44.google.com with SMTP id w11so6802624bku.31 for <grow@ietf.org>; Thu, 29 Nov 2012 00:09:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=a/mLaEKqaURMuOIMN3ZFhTatBSo662grDT9CtzVnZqA=; b=KMNIbp3LbpKP+PrcR9oewTNBVVdDTZQzdJ0m58byLmHxmQqVV1P2kINj27INTjKXJ6 tOOxIi7VPxkP+vWkCyk5w3BHUju6Ltr5IzIigGKKXy42+wvnnUxO7rEPuFOIh5B5pl2k rSk//Jgx/4JyfvfoJ+w8zA8wTEpOKD9M/iI2jX9xnV52QmCUEsg3YzAFsUxNu4F17AJu PqZoChIy6Lsb5ekha7QFWGYJdI6u7xMNvkcPFSiRX244h7oM0M+WwJkbpt0ec0VPSoN1 1Ak5KLSXHR0qFYAPWyyo3mpnE0rR+BSM5girlBrpFsuEu598N+b66g2JcGk3gg4TurCB heLQ==
Received: by 10.204.11.79 with SMTP id s15mr6582211bks.136.1354176548155; Thu, 29 Nov 2012 00:09:08 -0800 (PST)
Received: from [192.168.0.121] (vpn.static.83-173-212-209.cybernet.ch. [83.173.212.209]) by mx.google.com with ESMTPS id u3sm252588bkw.9.2012.11.29.00.09.06 (version=SSLv3 cipher=OTHER); Thu, 29 Nov 2012 00:09:07 -0800 (PST)
Message-ID: <50B71821.4010108@gmail.com>
Date: Thu, 29 Nov 2012 09:09:05 +0100
From: Mattia Rossi <mattia.rossi.mailinglists@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: grow@ietf.org
References: <CA+b+ERk0A1Kkex-f2goRv5Wa+GOXENMgXqA52myHzxO23bJfvA@mail.gmail.com> <50B4EA44.7090502@merit.edu> <CA+b+ERm0DKs5Pzk5c0e2PJaQeMHvK1Y6Yqwvg0_G88ibjhoUTw@mail.gmail.com> <50B4EE0C.4070803@merit.edu> <CA+b+ERnbdC9GdhyUOLSUtLm+MY032eWydaUqfJVVWNdJKNOiyw@mail.gmail.com> <50B4F910.4020000@merit.edu> <CAPfnYRhCh57wj0U+nE1MPS2K7YkRMvbXZX20Z4atYFVZ-u2mLw@mail.gmail.com> <CAO48Bk_Hd1R5dUd+u6k1mYzXwXcGe-iW+ZeJus5GFCMKeiuhfA@mail.gmail.com> <CAL9jLaYD9fL5gdaAb5LX6zD4i7tGg5+z--+mP_HaNvik6UqPLg@mail.gmail.com>
In-Reply-To: <CAL9jLaYD9fL5gdaAb5LX6zD4i7tGg5+z--+mP_HaNvik6UqPLg@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [GROW] MRT
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, 29 Nov 2012 08:09:10 -0000

Am 28.11.2012 19:41, schrieb Christopher Morrow:
> On Wed, Nov 28, 2012 at 12:47 PM, Pedro Andres Aranda Gutierrez
> <paaguti@gmail.com> wrote:
>> I had to write my own MRT parser library for my PhD. After my defense
>> next January, I plan to release it. (one step at a time, I'm quite
>> busy right now preparing the defense ;-) ) It's written in Java. Re:
>> pybgpdump, I have to agree it's a very nice tool once you patch dpkt
> how about we send the diff to dug and have him patch dpkt? :)

I've sent the patch to Jon a few years ago, he asked me to create the 
Unit tests as well, to sanity check it, I didn't find the time then. 
Before I could get back on that, I've been approached by someone in NZ 
about a year ago, who offered to do all the necessary cleanup and unit 
tests, contact Jon or Dug, and get the patch committed, but I wasn't 
able to follow up on that any more for personal reasons. Given that 
there's a great interest in that again, I'll try to find some time to 
see what's happening there.

Cheers,

Mat

From christopher.morrow@gmail.com  Thu Nov 29 06:55: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 5473C21F8A7D for <grow@ietfa.amsl.com>; Thu, 29 Nov 2012 06:55:39 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7QpnnE+00+4Q for <grow@ietfa.amsl.com>; Thu, 29 Nov 2012 06:55:38 -0800 (PST)
Received: from mail-ee0-f44.google.com (mail-ee0-f44.google.com [74.125.83.44]) by ietfa.amsl.com (Postfix) with ESMTP id 2C3CC21F8AF2 for <grow@ietf.org>; Thu, 29 Nov 2012 06:55:34 -0800 (PST)
Received: by mail-ee0-f44.google.com with SMTP id b47so9245541eek.31 for <grow@ietf.org>; Thu, 29 Nov 2012 06:55:33 -0800 (PST)
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; bh=qqwieNDahQb5xRm65uui5X0RXp1PTelecn/of7Jz2fk=; b=L14QG6UsYA/ENun23FjpnwFeiEduQDYTHuemumVfXQam8SYi9HgR3wJPnU49v1noyK 5J68mQIZX194I8nDQVGeDeH4Blm6u17BC7tCOatLC3attBkMQxzePg5/6QpXqgJh7mhk SG8FyRbg6Izrk8XOFCqi/wnnay1DsCGWxOkQ0Ru2smYZYEWW28UFLFkEVAqTrGYzGHom xOUwBf0AvDaibLKceDjtSb4JhHC6avTP6RMv9BiivGGoqa96wGevZkPwrot3AGs37wzl aCm9Nvr3p+GQTZIE0/1gnBjFNqXuKhLeo3rkvQHGtaRIW4gewrwpphwF7fOPP3GFE4qb 2zIQ==
MIME-Version: 1.0
Received: by 10.14.198.67 with SMTP id u43mr83077241een.7.1354200933406; Thu, 29 Nov 2012 06:55:33 -0800 (PST)
Received: by 10.223.96.5 with HTTP; Thu, 29 Nov 2012 06:55:33 -0800 (PST)
In-Reply-To: <50B71821.4010108@gmail.com>
References: <CA+b+ERk0A1Kkex-f2goRv5Wa+GOXENMgXqA52myHzxO23bJfvA@mail.gmail.com> <50B4EA44.7090502@merit.edu> <CA+b+ERm0DKs5Pzk5c0e2PJaQeMHvK1Y6Yqwvg0_G88ibjhoUTw@mail.gmail.com> <50B4EE0C.4070803@merit.edu> <CA+b+ERnbdC9GdhyUOLSUtLm+MY032eWydaUqfJVVWNdJKNOiyw@mail.gmail.com> <50B4F910.4020000@merit.edu> <CAPfnYRhCh57wj0U+nE1MPS2K7YkRMvbXZX20Z4atYFVZ-u2mLw@mail.gmail.com> <CAO48Bk_Hd1R5dUd+u6k1mYzXwXcGe-iW+ZeJus5GFCMKeiuhfA@mail.gmail.com> <CAL9jLaYD9fL5gdaAb5LX6zD4i7tGg5+z--+mP_HaNvik6UqPLg@mail.gmail.com> <50B71821.4010108@gmail.com>
Date: Thu, 29 Nov 2012 09:55:33 -0500
Message-ID: <CAL9jLaaTco_crLvvaoSU1yg55MKqB_Bu=UAdSpHAzXKk1qmKpw@mail.gmail.com>
From: Christopher Morrow <christopher.morrow@gmail.com>
To: Mattia Rossi <mattia.rossi.mailinglists@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: grow@ietf.org
Subject: Re: [GROW] MRT
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, 29 Nov 2012 14:55:53 -0000

On Thu, Nov 29, 2012 at 3:09 AM, Mattia Rossi
<mattia.rossi.mailinglists@gmail.com> wrote:
> Am 28.11.2012 19:41, schrieb Christopher Morrow:
>
>> On Wed, Nov 28, 2012 at 12:47 PM, Pedro Andres Aranda Gutierrez
>> <paaguti@gmail.com> wrote:
>>>
>>> I had to write my own MRT parser library for my PhD. After my defense
>>> next January, I plan to release it. (one step at a time, I'm quite
>>> busy right now preparing the defense ;-) ) It's written in Java. Re:
>>> pybgpdump, I have to agree it's a very nice tool once you patch dpkt
>>
>> how about we send the diff to dug and have him patch dpkt? :)
>
>
> I've sent the patch to Jon a few years ago, he asked me to create the Unit
> tests as well, to sanity check it, I didn't find the time then. Before I
> could get back on that, I've been approached by someone in NZ about a year
> ago, who offered to do all the necessary cleanup and unit tests, contact Jon
> or Dug, and get the patch committed, but I wasn't able to follow up on that
> any more for personal reasons. Given that there's a great interest in that
> again, I'll try to find some time to see what's happening there.

happy to attempt helping you with this... if you'd like.
(no guarantees to quality or time available, but I can take a shot as
well if that'd help)

-chris

From andrew.lange@alcatel-lucent.com  Tue Nov 20 14:37:34 2012
Return-Path: <andrew.lange@alcatel-lucent.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 2274C21F8815 for <grow@ietfa.amsl.com>; Tue, 20 Nov 2012 14:37:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.249
X-Spam-Level: 
X-Spam-Status: No, score=-6.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SGwRWnPsWS9l for <grow@ietfa.amsl.com>; Tue, 20 Nov 2012 14:37:33 -0800 (PST)
Received: from smail5.alcatel.fr (smail5.alcatel.fr [62.23.212.27]) by ietfa.amsl.com (Postfix) with ESMTP id 563F121F872D for <grow@ietf.org>; Tue, 20 Nov 2012 14:37:32 -0800 (PST)
Received: from FRMRSSXCHHUB02.dc-m.alcatel-lucent.com (FRMRSSXCHHUB02.dc-m.alcatel-lucent.com [135.120.45.62]) by smail5.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id qAKMbUfZ021817 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 20 Nov 2012 23:37:30 +0100
Received: from US70TWXCHHUB03.zam.alcatel-lucent.com (135.5.2.35) by FRMRSSXCHHUB02.dc-m.alcatel-lucent.com (135.120.45.62) with Microsoft SMTP Server (TLS) id 8.3.213.0; Tue, 20 Nov 2012 23:37:30 +0100
Received: from alange.lra.lucent.com (135.5.27.17) by US70TWXCHHUB03.zam.alcatel-lucent.com (135.5.2.35) with Microsoft SMTP Server (TLS) id 14.2.247.3; Tue, 20 Nov 2012 17:37:27 -0500
MIME-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset="us-ascii"
From: Andrew Lange <andrew.lange@alcatel-lucent.com>
In-Reply-To: <CAL9jLabt0S98HEygsQp=a98ARwiRxJ2x3F2=H5w-pDRbyqWE7A@mail.gmail.com>
Date: Tue, 20 Nov 2012 14:33:13 -0800
Content-Transfer-Encoding: quoted-printable
Message-ID: <02F2E288-0042-4637-9234-A946B7501EC6@alcatel-lucent.com>
References: <CAL9jLabt0S98HEygsQp=a98ARwiRxJ2x3F2=H5w-pDRbyqWE7A@mail.gmail.com>
To: Christopher Morrow <christopher.morrow@gmail.com>
X-Mailer: Apple Mail (2.1085)
X-Originating-IP: [135.5.27.17]
X-Scanned-By: MIMEDefang 2.69 on 155.132.188.13
X-Mailman-Approved-At: Thu, 29 Nov 2012 08:49:38 -0800
Cc: "grow@ietf.org grow@ietf.org" <grow@ietf.org>, draft-mcpherson-irr-routing-policy-considerations@tools.ietf.org, grow-ads@tools.ietf.org, grow-chairs@tools.ietf.org
Subject: Re: [GROW] WG Adoption call: draft-mcpherson-irr-routing-policy-considerations (END: 11/28/2012)
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, 20 Nov 2012 22:37:34 -0000

Strongly support.  IRR is a key issue for interdomain routing.  =
Understanding the history is key for getting things right in the future.

Andrew

On Nov 14, 2012, at 2:35 PM, Christopher Morrow wrote:

> Grow Folks,
> the authors of:  draft-mcpherson-irr-routing-policy-considerations
>  =
<http://tools.ietf.org/html/draft-mcpherson-irr-routing-policy-considerati=
ons-01>
>=20
> have asked if their work is appropriate for the GROW-wg, could we take
> the next 14 days (ending Nov 28, 2012) to think/discuss this draft and
> it's efficacy to work in the GROW arena? The abstract of the draft is:
>  "The purpose of this document is to catalog past issues influencing
>   the efficacy of Internet Routing Registries (IRR) for inter-domain
>   routing policy specification and application in the global routing
>   system over the past two decades.  Additionally, it provides a
>   discussion regarding which of these issues are still problematic in
>   practice, and which are simply artifacts that are no longer
>   applicable but continue to stifle inter-provider policy-based
>   filtering adoption and IRR utility to this day."
>=20
> Thanks!
> -Chris
> (co-chair)
> _______________________________________________
> GROW mailing list
> GROW@ietf.org
> https://www.ietf.org/mailman/listinfo/grow

