From rpsec-bounces@ietf.org Fri Oct 13 22:22:05 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GYZ7V-0004VO-CG; Fri, 13 Oct 2006 22:19:25 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GYZ7S-0004Uu-Gv; Fri, 13 Oct 2006 22:19:22 -0400 Received: from nit.isi.edu ([128.9.160.116]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GYZ7R-0008NA-5c; Fri, 13 Oct 2006 22:19:22 -0400 Received: from nit.isi.edu (loopback [127.0.0.1]) by nit.isi.edu (8.12.11.20060308/8.12.11) with ESMTP id k9E2JIHU018691; Fri, 13 Oct 2006 19:19:18 -0700 Received: (from apache@localhost) by nit.isi.edu (8.12.11.20060308/8.12.11/Submit) id k9E2JIXG018690; Fri, 13 Oct 2006 19:19:18 -0700 Date: Fri, 13 Oct 2006 19:19:18 -0700 Message-Id: <200610140219.k9E2JIXG018690@nit.isi.edu> To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org From: rfc-editor@rfc-editor.org X-Spam-Score: -14.8 (--------------) X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17 Cc: rpsec@ietf.org, rfc-editor@rfc-editor.org Subject: [RPSEC] RFC 4593 on Generic Threats to Routing Protocols X-BeenThere: rpsec@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Routing Protocol Security Requirements List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: rpsec-bounces@ietf.org A new Request for Comments is now available in online RFC libraries. RFC 4593 Title: Generic Threats to Routing Protocols Author: A. Barbir, S. Murphy, Y. Yang Status: Informational Date: October 2006 Mailbox: abbieb@nortel.com, sandy@sparta.com, yiya@cisco.com Pages: 22 Characters: 48292 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-rpsec-routing-threats-07.txt URL: http://www.rfc-editor.org/rfc/rfc4593.txt Routing protocols are subject to attacks that can harm individual users or network operations as a whole. This document provides a description and a summary of generic threats that affect routing protocols in general. This work describes threats, including threat sources and capabilities, threat actions, and threat consequences, as well as a breakdown of routing functions that might be attacked separately. This memo provides information for the Internet community. This document is a product of the Routing Protocol Security Requirements 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 list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... _______________________________________________ RPSEC mailing list RPSEC@ietf.org https://www1.ietf.org/mailman/listinfo/rpsec From rpsec-bounces@ietf.org Fri Oct 27 17:06:32 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GdYs6-0002Kt-7v; Fri, 27 Oct 2006 17:04:10 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GdYs4-0002Ko-Vj for rpsec@ietf.org; Fri, 27 Oct 2006 17:04:08 -0400 Received: from [2001:6b0:1:1300:20e:7fff:fef0:f8bb] (helo=mx3.kth.se) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GdYs3-0002TY-MQ for rpsec@ietf.org; Fri, 27 Oct 2006 17:04:08 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by mx3.kth.se (Postfix) with ESMTP id 4AE011405AD for ; Fri, 27 Oct 2006 23:03:50 +0200 (CEST) Received: from mx3.kth.se ([127.0.0.1]) by localhost (mx3.kth.se [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 18764-01-64 for ; Fri, 27 Oct 2006 23:03:49 +0200 (CEST) Received: from webmail.sys.kth.se (mensageiro.sys.kth.se [130.237.48.58]) by mx3.kth.se (Postfix) with ESMTP id 722D214057F for ; Fri, 27 Oct 2006 23:03:49 +0200 (CEST) Received: from 83.233.40.156 (SquirrelMail authenticated user hanis) by webmail.sys.kth.se with HTTP; Fri, 27 Oct 2006 23:03:49 +0200 (CEST) Message-ID: <3290.83.233.40.156.1161983029.squirrel@webmail.sys.kth.se> Date: Fri, 27 Oct 2006 23:03:49 +0200 (CEST) From: "Hani Salah" To: rpsec@ietf.org User-Agent: SquirrelMail/1.4.5 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 X-Priority: 3 (Normal) Importance: Normal X-Virus-Scanned: by amavisd-new at kth.se Content-Transfer-Encoding: quoted-printable X-Spam-Score: -2.8 (--) X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2 Subject: [RPSEC] Questions regarding soBGP X-BeenThere: rpsec@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Routing Protocol Security Requirements List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: rpsec-bounces@ietf.org Hi, Can anybody please show me how soBGP deal with (peer entity authentication) and (route withdrawal authorization)? Thanks a lot. Best Regards, Hani Salah _______________________________________________ RPSEC mailing list RPSEC@ietf.org https://www1.ietf.org/mailman/listinfo/rpsec From rpsec-bounces@ietf.org Mon Oct 30 09:03:58 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GeXhb-0001lo-Ju; Mon, 30 Oct 2006 09:01:23 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GeXhZ-0001Zq-V3 for rpsec@ietf.org; Mon, 30 Oct 2006 09:01:22 -0500 Received: from rtp-iport-2.cisco.com ([64.102.122.149]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GeXhS-0002LA-Le for rpsec@ietf.org; Mon, 30 Oct 2006 09:01:21 -0500 Received: from rtp-dkim-2.cisco.com ([64.102.121.159]) by rtp-iport-2.cisco.com with ESMTP; 30 Oct 2006 09:01:14 -0500 Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13]) by rtp-dkim-2.cisco.com (8.12.11.20060308/8.12.11) with ESMTP id k9UE1Euv005883 for ; Mon, 30 Oct 2006 09:01:14 -0500 Received: from [127.0.0.1] (rtp-ruwhite-vpn13.cisco.com [10.82.175.126]) by rtp-core-2.cisco.com (8.12.10/8.12.6) with SMTP id k9UE1DDM007676 for ; Mon, 30 Oct 2006 09:01:14 -0500 (EST) Message-ID: <454605A9.7020904@cisco.com> Date: Mon, 30 Oct 2006 09:01:13 -0500 From: Russ White User-Agent: Thunderbird 1.5.0.7 (Windows/20060909) MIME-Version: 1.0 To: rpsec@ietf.org X-Enigmail-Version: 0.94.1.0 Content-Type: multipart/mixed; boundary="------------000405060302030801040305" DKIM-Signature: a=rsa-sha1; q=dns; l=2691; t=1162216874; x=1163080874; c=relaxed/simple; s=rtpdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=riw@cisco.com; z=From:Russ=20White=20 |Subject:Charter=20Update.... |To:rpsec@ietf.org; X=v=3Dcisco.com=3B=20h=3DEGk6GeaXQx1rTd/qlx/9ZjPaXWY=3D; b=zMz/syieEeLGvBJRkGtlDV9YM3+Eg1XCvgjGtCEu1E15gVk2oOy4cqmUtA3cjyaYgwM7FEOc c9qhxXCs+4vyYilqqzuDW68ftFDIHG4cIDClQWvGlv5IenPrc7UY97kB; Authentication-Results: rtp-dkim-2.cisco.com; header.From=riw@cisco.com; dkim=pass ( 42 extraneous bytes; sig from cisco.com verified; ); X-Spam-Score: 0.0 (/) X-Scan-Signature: 31247fb3be228bb596db9127becad0bc Subject: [RPSEC] Charter Update.... X-BeenThere: rpsec@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Routing Protocol Security Requirements List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: rpsec-bounces@ietf.org This is a multi-part message in MIME format. --------------000405060302030801040305 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 We tried this once last year, and didn't seem to make any real progress, so.... Try again. :-) I'd like to propose we update the charter with current work, and what we should be working on in the next 6 months to a year. Any additions, changes, or suggestions are welcome. :-) Russ - -- riw@cisco.com CCIE <>< Grace Alone -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFRgWpER27sUhU9OQRArLmAJ4p8Hr/muXSITAaHip45HgVoj/aRQCeOV/0 QKi3489GZ4nR/69YpwjJg/Q= =AthA -----END PGP SIGNATURE----- --------------000405060302030801040305 Content-Type: text/plain; name="charter-11-06.txt" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="charter-11-06.txt" The lack of a common set of security requirements and methods for routing protocols has resulted in a wide variety of security mechanisms for individual routing protocols. Ongoing work on requirements for the next generation routing system and future work on the actual mechanisms for it will require well documented routing security requirements. The products of this working group will be used by routing protocol designers to ensure adequate coverage of security in the future, including well known and possible threats. The scope of work is limited to router-to-router protocols for unicast and multicast systems, and does NOT include host-to-router protocol such as IGMP, ICMP, ARP, or ND. It is also a non-goal at this point to produce new or change the current security mechanisms in the existing routing protocols. The RPSEC working group is charged with the following tasks: - Document threat models for routing systems - Document security requirements for routing systems - Document security analysis and requirements for specific routing protocols (e.g., OSPF, BGP) - Provide a common area for discussion between security and routing experts on the topic of securing the routing system Goals and Milestones: March 07 Submit BGP Attack-Tree analysis for publication as Informational RFC. March 07 Submit OSPF vulnerability analysis for publication as Informational RFC. March 07 Submit BGP security requirements for publication as Informational RFC. March 07 Initial draft of requirements for point-to-point security of BGP peering sessions. December 07 Evaluate progress, recharter with new goals or shutdown. --------------000405060302030801040305 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ RPSEC mailing list RPSEC@ietf.org https://www1.ietf.org/mailman/listinfo/rpsec --------------000405060302030801040305--