[RPSEC] BGP session security requirement draft, -01

"Michael H. Behringer" <mbehring@cisco.com> Tue, 15 May 2007 09:00 UTC

Return-path: <rpsec-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HnstK-0006aE-AT; Tue, 15 May 2007 05:00:22 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HnstI-0006a1-Qq for rpsec@ietf.org; Tue, 15 May 2007 05:00:20 -0400
Received: from ams-iport-1.cisco.com ([144.254.224.140]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HnstI-0003yj-8Q for rpsec@ietf.org; Tue, 15 May 2007 05:00:20 -0400
Received: from ams-dkim-1.cisco.com ([144.254.224.138]) by ams-iport-1.cisco.com with ESMTP; 15 May 2007 11:00:19 +0200
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150]) by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l4F90J2B014999 for <rpsec@ietf.org>; Tue, 15 May 2007 11:00:19 +0200
Received: from xbh-ams-331.emea.cisco.com (xbh-ams-331.cisco.com [144.254.231.71]) by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l4F90JDR029444 for <rpsec@ietf.org>; Tue, 15 May 2007 09:00:19 GMT
Received: from xfe-ams-331.emea.cisco.com ([144.254.231.72]) by xbh-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 15 May 2007 11:00:19 +0200
Received: from mbehring-wxp.cisco.com ([10.55.2.210]) by xfe-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 15 May 2007 11:00:18 +0200
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Tue, 15 May 2007 11:00:17 +0200
To: rpsec@ietf.org
From: "Michael H. Behringer" <mbehring@cisco.com>
Mime-Version: 1.0
Message-ID: <XFE-AMS-331HfqR77bi000005a2@xfe-ams-331.emea.cisco.com>
X-OriginalArrivalTime: 15 May 2007 09:00:19.0071 (UTC) FILETIME=[765028F0:01C796CF]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=4419; t=1179219619; x=1180083619; c=relaxed/simple; s=amsdkim1002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=mbehring@cisco.com; z=From:=20=22Michael=20H.=20Behringer=22=20<mbehring@cisco.com> |Subject:=20BGP=20session=20security=20requirement=20draft,=20-01 |Sender:=20; bh=Pu7ixHCqGbESaTvrr9R1dxBnS+4oX5yJpQ4lclI1pUI=; b=YrknrYUZNYV/egNpi/bct8vW4clrF3ZeXBUIC69d9oQ4r87bYJJGAslgIsGPrE2Z4poWv7Vg uztgLvEBvF3bTW32jNY26QkFr+sKU1XVlAk9piMsPe8Kbu+3cfluJlQi;
Authentication-Results: ams-dkim-1; header.From=mbehring@cisco.com; dkim=pass ( sig from cisco.com/amsdkim1002 verified; );
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 1a1bf7677bfe77d8af1ebe0e91045c5b
Subject: [RPSEC] BGP session security requirement draft, -01
X-BeenThere: rpsec@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Protocol Security Requirements <rpsec.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rpsec>, <mailto:rpsec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/rpsec>
List-Post: <mailto:rpsec@ietf.org>
List-Help: <mailto:rpsec-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rpsec>, <mailto:rpsec-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0407272420=="
Errors-To: rpsec-bounces@ietf.org

Incorporating all comments I received so far (thanks!) I published version -01 of the draft. 

http://www.ietf.org/internet-drafts/draft-behringer-bgp-session-sec-req-01.txt

Many comments I got suggested to add stories, examples, etc. So far my approach has been to be "minimalistic", and to really focus on the bare requirements, and leave out ornaments. Sandy commented that we need to move quickly on this draft, so keeping it "to the point" seems the right approach to me. 

Since this is a work item on the charter, I would like to request this document to become a WG draft, and to move it on from there. 

Any comments are appreciated. 

Thanks, 
Michael


>Date: Mon, 26 Feb 2007 19:13:41 +0100
>To: Russ White <riw@cisco.com>om>, rpsec@ietf.org
>From: "Michael H. Behringer" <mbehring@cisco.com>
>Subject: Re: [RPSEC] Charter and Meeting Agenda
>
>Russ, all, 
>
>At 15:37 06/01/2007, Russ White wrote:
>[...]
>>o P-2-P security requirements for BGP: This was to provide some cover
>>and thinking on the various TCP auth mechanisms to replace MD5 that are
>>currently being considered. We need, I believe, a volunteer to
>>author/edit this, and get it moving.
>[...]
>
>I had a go at that topic, please see below. This still needs quite some content and editing; for now, I would like to ask for feedback on the abstract / intro (to make sure the problem is described correctly), and the outline of the draft. Is this the way we want to go down here? Please let me know your opinion. 
>
>
>
>
>http://www.ietf.org/internet-drafts/draft-behringer-bgp-session-sec-req-00.txt
>
>
>Cheers, 
>Michael 
>_______________________________________________
>RPSEC mailing list
>RPSEC@ietf.orghttps://www1.ietf.org/mailman/listinfo/rpsec
_______________________________________________
RPSEC mailing list
RPSEC@ietf.org
https://www1.ietf.org/mailman/listinfo/rpsec