[sidr] as-migration nit in bgpsec-protocol-13
"George, Wes" <wesley.george@twcable.com> Fri, 16 October 2015 15:12 UTC
Return-Path: <wesley.george@twcable.com>
X-Original-To: sidr@ietfa.amsl.com
Delivered-To: sidr@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A44341B2BBB for <sidr@ietfa.amsl.com>; Fri, 16 Oct 2015 08:12:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.475
X-Spam-Level:
X-Spam-Status: No, score=-0.475 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EI9CDBZog0ZW for <sidr@ietfa.amsl.com>; Fri, 16 Oct 2015 08:12:27 -0700 (PDT)
Received: from cdpipgw01.twcable.com (cdpipgw01.twcable.com [165.237.59.22]) by ietfa.amsl.com (Postfix) with ESMTP id CB5641A90B5 for <sidr@ietf.org>; Fri, 16 Oct 2015 08:12:26 -0700 (PDT)
X-SENDER-IP: 10.64.163.150
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="5.17,689,1437451200"; d="scan'208";a="1001851274"
Received: from unknown (HELO exchpapp09.corp.twcable.com) ([10.64.163.150]) by cdpipgw01.twcable.com with ESMTP/TLS/AES256-SHA; 16 Oct 2015 11:07:05 -0400
Received: from EXCHPAPP06.corp.twcable.com (10.64.163.147) by exchpapp09.corp.twcable.com (10.64.163.150) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Fri, 16 Oct 2015 11:12:23 -0400
Received: from EXCHPAPP06.corp.twcable.com ([10.64.163.147]) by exchpapp06.corp.twcable.com ([10.64.163.147]) with mapi id 15.00.1104.000; Fri, 16 Oct 2015 11:12:23 -0400
From: "George, Wes" <wesley.george@twcable.com>
To: "sidr@ietf.org" <sidr@ietf.org>
Thread-Topic: as-migration nit in bgpsec-protocol-13
Thread-Index: AQHRCCUOs+UKDCxztUqIc1SAUM68tA==
Date: Fri, 16 Oct 2015 15:12:22 +0000
Message-ID: <D24688C9.6D372%wesley.george@twcable.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.5.7.151005
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.64.163.239]
x-tm-as-product-ver: SMEX-11.0.0.1191-8.000.1202-21882.004
x-tm-as-result: No--50.373000-8.000000-31
x-tm-as-user-approved-sender: No
x-tm-as-user-blocked-sender: No
Content-Type: text/plain; charset="utf-8"
Content-ID: <989FEC4E0915564B8F4FFE39BE8C4992@twcable.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/sidr/5sogBnL4s5so3ilqOAkEjVIbzyA>
Subject: [sidr] as-migration nit in bgpsec-protocol-13
X-BeenThere: sidr@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Secure Interdomain Routing <sidr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sidr>, <mailto:sidr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sidr/>
List-Post: <mailto:sidr@ietf.org>
List-Help: <mailto:sidr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sidr>, <mailto:sidr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Oct 2015 15:12:28 -0000
I just made another pass through sidr-as-migration and bgpsec-protocol-13 back to back to make sure that they are in sync, and I only found one sentence in the security considerations (7.4) that probably needs to be changed: Current: However, entities other than route servers could conceivably use this mechanism (set the pCount to zero) to attract traffic (by reducing the effective length of the AS-PATH) illegitimately. This risk is largely mitigated if every BGPsec speaker drops incoming update messages that set pCount to zero but come from a peer that is not a route server. Proposed: ... if every BGPsec speaker drops incoming update messages that set pCount to zero unless explicitly configured to accept them from a specific peer where pCount=0 messages are expected, such as a route server. Thanks, Wes On 7/6/15, 7:21 PM, "sidr on behalf of internet-drafts@ietf.org" <sidr-bounces@ietf.org on behalf of internet-drafts@ietf.org> wrote: > >A New Internet-Draft is available from the on-line Internet-Drafts >directories. > This draft is a work item of the Secure Inter-Domain Routing Working >Group of the IETF. > > Title : BGPsec Protocol Specification > Author : Matthew Lepinski >Filename : draft-ietf-sidr-bgpsec-protocol-13.txt >Pages : 39 >Date : 2015-07-06 > >Abstract: > This document describes BGPsec, an extension to the Border Gateway > Protocol (BGP) that provides security for the path of autonomous > systems through which a BGP update message passes. BGPsec is > implemented via a new optional non-transitive BGP path attribute that > carries a digital signature produced by each autonomous system that > propagates the update message. > > > >The IETF datatracker status page for this draft is: >https://datatracker.ietf.org/doc/draft-ietf-sidr-bgpsec-protocol/ > >There's also a htmlized version available at: >https://tools.ietf.org/html/draft-ietf-sidr-bgpsec-protocol-13 > >A diff from the previous version is available at: >https://www.ietf.org/rfcdiff?url2=draft-ietf-sidr-bgpsec-protocol-13 > > >Please note that it may take a couple of minutes from the time of >submission >until the htmlized version and diff are available at tools.ietf.org. > >Internet-Drafts are also available by anonymous FTP at: >ftp://ftp.ietf.org/internet-drafts/ > >_______________________________________________ >sidr mailing list >sidr@ietf.org >https://www.ietf.org/mailman/listinfo/sidr ________________________________ This E-mail and any of its attachments may contain Time Warner Cable proprietary information, which is privileged, confidential, or subject to copyright belonging to Time Warner Cable. This E-mail is intended solely for the use 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 dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout.
- [sidr] as-migration nit in bgpsec-protocol-13 George, Wes