From mailman-bounces@ietf.org Fri Oct 1 09:10:08 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA26675 for ; Fri, 1 Oct 2004 09:10:08 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CDNJI-0006qy-LP for rpsec-web-archive@ietf.org; Fri, 01 Oct 2004 09:18:56 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CDK2z-0001fo-Af for rpsec-web-archive@ietf.org; Fri, 01 Oct 2004 05:49:53 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: ietf.org mailing list memberships reminder From: mailman-owner@ietf.org To: rpsec-web-archive@ietf.org X-No-Archive: yes Message-ID: Date: Fri, 01 Oct 2004 05:19:23 -0400 Precedence: bulk X-BeenThere: mailman@lists.ietf.org X-Mailman-Version: 2.1.5 List-Id: Mailman site list X-List-Administrivia: yes Sender: mailman-bounces@ietf.org Errors-To: mailman-bounces@ietf.org X-Spam-Score: 0.3 (/) X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5 Content-Transfer-Encoding: 7bit This is a reminder, sent out once a month, about your ietf.org mailing list memberships. It includes your subscription info and how to use it to change it or unsubscribe from a list. You can visit the URLs to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on. In addition to the URL interfaces, you can also use email to make such changes. For more info, send a message to the '-request' address of the list (for example, mailman-request@ietf.org) containing just the word 'help' in the message body, and an email message will be sent to you with instructions. ********************************************************************** NOTE WELL: Any submission to the IETF intended by the Contributor for publication as all or part of an IETF Internet-Draft or RFC and any statement made within the context of an IETF activity is considered an "IETF Contribution". Such statements include oral statements in IETF sessions, as well as written and electronic communications made at any time or place, which are addressed to: o the IETF plenary session, o any IETF working group or portion thereof, o the IESG, or any member thereof on behalf of the IESG, o the IAB or any member thereof on behalf of the IAB, o any IETF mailing list, including the IETF list itself, any working group or design team list, or any other list functioning under IETF auspices, o the RFC Editor or the Internet-Drafts function All IETF Contributions are subject to the rules of RFC 3667 and RFC 3668. Statements made outside of an IETF session, mailing list or other function, that are clearly not intended to be input to an IETF activity, group or function, are not IETF Contributions in the context of this notice. Please consult RFC 3667 for details. ******************************************************************************* If you have questions, problems, comments, etc, send them to mailman-owner@ietf.org. Thanks! Passwords for rpsec-web-archive@ietf.org: List Password // URL ---- -------- rpsec@ietf.org lLFY https://www1.ietf.org/mailman/options/rpsec/rpsec-web-archive%40ietf.org From rpsec-bounces@ietf.org Mon Oct 18 03:02:07 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA20374 for ; Mon, 18 Oct 2004 03:02:07 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CJRiv-0001Lx-Kp for rpsec-web-archive@ietf.org; Mon, 18 Oct 2004 03:14:29 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CJRVZ-0001YQ-Ez; Mon, 18 Oct 2004 03:00:41 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CJRTa-0001L9-LE for rpsec@megatron.ietf.org; Mon, 18 Oct 2004 02:58:38 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA20159 for ; Mon, 18 Oct 2004 02:58:37 -0400 (EDT) Received: from mail-sin.microsoft.com ([207.46.50.72]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CJRfW-0001Hi-0j for rpsec@ietf.org; Mon, 18 Oct 2004 03:10:59 -0400 Received: from APS-MSG-01.southpacific.corp.microsoft.com ([157.60.218.45]) by mail-sin.microsoft.com with Microsoft SMTPSVC(6.0.3790.0); Mon, 18 Oct 2004 15:57:52 +0900 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Mon, 18 Oct 2004 14:57:50 +0800 Message-ID: Thread-Topic: IPSEC and RIPng thread-index: AcS03pK/ANLkv6Z4R/ypr5PcLjUUmQAAM90w From: "Vikas Jain" To: X-OriginalArrivalTime: 18 Oct 2004 06:57:52.0848 (UTC) FILETIME=[C9BC3D00:01C4B4DF] X-Spam-Score: 0.1 (/) X-Scan-Signature: 67c1ea29f88502ef6a32ccec927970f0 Subject: [RPSEC] IPSEC and RIPng 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: , Content-Type: multipart/mixed; boundary="===============0641661027==" Sender: rpsec-bounces@ietf.org Errors-To: rpsec-bounces@ietf.org X-Spam-Score: 0.5 (/) X-Scan-Signature: 932cba6e0228cc603da43d861a7e09d8 This is a multi-part message in MIME format. --===============0641661027== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C4B4DF.C9E139E5" This is a multi-part message in MIME format. ------_=_NextPart_001_01C4B4DF.C9E139E5 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi, =20 Has there been any work on how RIPng can be secured by IPSEC (i.e. using IPSEC for authenticating RIPng messages)? RFC 2080 mentions that RIPng uses AH and ESP to authenticate messages. Is there any commercial implementation that implements IPSEC with RIPng? =20 Please direct me to the right mailing list if this is not the correct mailing list. =20 Thanks, Vikas ------_=_NextPart_001_01C4B4DF.C9E139E5 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi,

 

Has there been any work on how RIPng can be secured = by IPSEC (i.e. using IPSEC for authenticating RIPng messages)? RFC 2080 mentions = that RIPng uses AH and ESP to authenticate messages. Is there any commercial implementation that implements IPSEC with RIPng?

 

Please direct me to the right mailing list if this is = not the correct mailing list.

 

Thanks,

Vikas

------_=_NextPart_001_01C4B4DF.C9E139E5-- --===============0641661027== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ RPSEC mailing list RPSEC@ietf.org https://www1.ietf.org/mailman/listinfo/rpsec --===============0641661027==-- From rpsec-bounces@ietf.org Mon Oct 18 04:10:46 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA25943 for ; Mon, 18 Oct 2004 04:10:46 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CJSnL-0002mc-SQ for rpsec-web-archive@ietf.org; Mon, 18 Oct 2004 04:23:09 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CJSa0-00087j-83; Mon, 18 Oct 2004 04:09:20 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CJSUo-0007bU-Hp for rpsec@megatron.ietf.org; Mon, 18 Oct 2004 04:03:59 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA25529 for ; Mon, 18 Oct 2004 04:03:57 -0400 (EDT) From: Mukesh.K.Gupta@nokia.com Received: from mgw-x1.nokia.com ([131.228.20.21]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CJSgl-0002fv-HK for rpsec@ietf.org; Mon, 18 Oct 2004 04:16:19 -0400 Received: from esdks003.ntc.nokia.com (esdks003.ntc.nokia.com [172.21.138.158]) by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i9I83th28125; Mon, 18 Oct 2004 11:03:55 +0300 (EET DST) X-Scanned: Mon, 18 Oct 2004 11:03:16 +0300 Nokia Message Protector V1.3.31 2004060815 - RELEASE Received: (from root@localhost) by esdks003.ntc.nokia.com (8.12.9/8.12.9) id i9I83GTv003023; Mon, 18 Oct 2004 11:03:16 +0300 Received: from mgw-int2.ntc.nokia.com (172.21.143.97) by esdks003.ntc.nokia.com 006cuTp7; Mon, 18 Oct 2004 11:03:15 EEST Received: from daebh001.NOE.Nokia.com (daebh001.americas.nokia.com [10.241.35.121]) by mgw-int2.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i9I839S09226; Mon, 18 Oct 2004 11:03:09 +0300 (EET DST) Received: from daebe009.NOE.Nokia.com ([10.241.35.109]) by daebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); Mon, 18 Oct 2004 03:03:08 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: [RPSEC] IPSEC and RIPng Date: Mon, 18 Oct 2004 03:03:08 -0500 Message-ID: <8D260779A766FB4A9C1739A476F84FA4026AB58E@daebe009.americas.nokia.com> Thread-Topic: IPSEC and RIPng Thread-Index: AcS03pK/ANLkv6Z4R/ypr5PcLjUUmQAAM90wAAFJxSAAAK31kAAAZ4DA To: , X-OriginalArrivalTime: 18 Oct 2004 08:03:08.0706 (UTC) FILETIME=[E7C4C020:01C4B4E8] X-Spam-Score: 0.3 (/) X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17 Content-Transfer-Encoding: quoted-printable 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: , Sender: rpsec-bounces@ietf.org Errors-To: rpsec-bounces@ietf.org X-Spam-Score: 0.3 (/) X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b Content-Transfer-Encoding: quoted-printable Vikas, If you haven't already, please look at=20 draft draft-ietf-ospf-ospfv3-auth-04.txt that talks about how to secure OSPFv3 using IPsec. Securing RIPng using IPsec would be quite similar. I do not know of any work in progress about about RIPng and IPsec. I have to admit that I haven't implemented RIPng security using IPsec though. I have implemented the above mentioned draft for providing security to OSPFv3. Regards Mukesh -----Original Message----- From: rpsec-bounces@ietf.org [mailto:rpsec-bounces@ietf.org]On Behalf Of = ext Vikas Jain Sent: Sunday, October 17, 2004 11:58 PM To: rpsec@ietf.org Subject: [RPSEC] IPSEC and RIPng Hi, Has there been any work on how RIPng can be secured by IPSEC (i.e. using = IPSEC for authenticating RIPng messages)? RFC 2080 mentions that RIPng = uses AH and ESP to authenticate messages. Is there any commercial = implementation that implements IPSEC with RIPng? Please direct me to the right mailing list if this is not the correct = mailing list. Thanks, Vikas>=20 _______________________________________________ RPSEC mailing list RPSEC@ietf.org https://www1.ietf.org/mailman/listinfo/rpsec From rpsec-bounces@ietf.org Mon Oct 18 04:25:13 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA26880 for ; Mon, 18 Oct 2004 04:25:13 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CJT1M-00033q-Rs for rpsec-web-archive@ietf.org; Mon, 18 Oct 2004 04:37:37 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CJSo0-0001DJ-7U; Mon, 18 Oct 2004 04:23:48 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CJSjP-0000mZ-7k for rpsec@megatron.ietf.org; Mon, 18 Oct 2004 04:19:03 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA26526 for ; Mon, 18 Oct 2004 04:19:01 -0400 (EDT) From: Mukesh.K.Gupta@nokia.com Received: from mgw-x4.nokia.com ([131.228.20.27]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CJSvL-0002vV-BX for rpsec@ietf.org; Mon, 18 Oct 2004 04:31:24 -0400 Received: from esdks002.ntc.nokia.com (esdks002.ntc.nokia.com [172.21.138.121]) by mgw-x4.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i9I8IvW09727; Mon, 18 Oct 2004 11:18:58 +0300 (EET DST) X-Scanned: Mon, 18 Oct 2004 11:18:48 +0300 Nokia Message Protector V1.3.31 2004060815 - RELEASE Received: (from root@localhost) by esdks002.ntc.nokia.com (8.12.9/8.12.9) id i9I8Im6w020764; Mon, 18 Oct 2004 11:18:48 +0300 Received: from mgw-int1.ntc.nokia.com (172.21.143.96) by esdks002.ntc.nokia.com 00ES3EEV; Mon, 18 Oct 2004 11:17:03 EEST Received: from daebh002.NOE.Nokia.com (daebh002.americas.nokia.com [10.241.35.122]) by mgw-int1.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i9I7pZa03320; Mon, 18 Oct 2004 10:51:35 +0300 (EET DST) Received: from daebe009.NOE.Nokia.com ([10.241.35.109]) by daebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); Mon, 18 Oct 2004 02:51:34 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: [RPSEC] IPSEC and RIPng Date: Mon, 18 Oct 2004 02:51:34 -0500 Message-ID: <8D260779A766FB4A9C1739A476F84FA4026AB58D@daebe009.americas.nokia.com> Thread-Topic: IPSEC and RIPng Thread-Index: AcS03pK/ANLkv6Z4R/ypr5PcLjUUmQAAM90wAAFJxSAAAK31kA== To: , X-OriginalArrivalTime: 18 Oct 2004 07:51:34.0684 (UTC) FILETIME=[4A1965C0:01C4B4E7] X-Spam-Score: 0.3 (/) X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17 Content-Transfer-Encoding: quoted-printable 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: , Sender: rpsec-bounces@ietf.org Errors-To: rpsec-bounces@ietf.org X-Spam-Score: 0.3 (/) X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b Content-Transfer-Encoding: quoted-printable Vikas, If you haven't already, please look at=20 draft draft-ietf-ospf-ospfv3-auth-04.txt that talks about how to secure OSPFv3 using IPsec. Securing RIPng using IPsec would be quite similar. I do not know of any work in progress about about RIPng and IPsec. I have to admit that I haven't implemented RIPng security using IPsec though. I have implemented the above mentioned draft for providing security to OSPFv3. Regards Mukesh -----Original Message----- From: rpsec-bounces@ietf.org [mailto:rpsec-bounces@ietf.org]On Behalf Of = ext Vikas Jain Sent: Sunday, October 17, 2004 11:58 PM To: rpsec@ietf.org Subject: [RPSEC] IPSEC and RIPng Hi, Has there been any work on how RIPng can be secured by IPSEC (i.e. using = IPSEC for authenticating RIPng messages)? RFC 2080 mentions that RIPng = uses AH and ESP to authenticate messages. Is there any commercial = implementation that implements IPSEC with RIPng? Please direct me to the right mailing list if this is not the correct = mailing list. Thanks, Vikas>=20 _______________________________________________ RPSEC mailing list RPSEC@ietf.org https://www1.ietf.org/mailman/listinfo/rpsec From rpsec-bounces@ietf.org Tue Oct 26 13:32:30 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA26924 for ; Tue, 26 Oct 2004 13:32:30 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CMVP7-0000Ks-Tc for rpsec-web-archive@ietf.org; Tue, 26 Oct 2004 13:46:43 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CMUuj-000586-8J; Tue, 26 Oct 2004 13:15:17 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CMUp4-0003DY-3z for rpsec@megatron.ietf.org; Tue, 26 Oct 2004 13:09:26 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA24227 for ; Tue, 26 Oct 2004 13:09:23 -0400 (EDT) Received: from m106.maoz.com ([205.167.76.9]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CMV2f-0007ym-3R for rpsec@ietf.org; Tue, 26 Oct 2004 13:23:32 -0400 Received: from m106.maoz.com (localhost.localdomain [127.0.0.1]) by m106.maoz.com (8.12.11/8.12.11) with ESMTP id i9QH8lXA012486 for ; Tue, 26 Oct 2004 10:08:47 -0700 Received: from localhost (ttauber@localhost) by m106.maoz.com (8.12.11/8.12.11/Submit) with ESMTP id i9QH8lb4012483 for ; Tue, 26 Oct 2004 10:08:47 -0700 X-Authentication-Warning: m106.maoz.com: ttauber owned process doing -bs Date: Tue, 26 Oct 2004 10:08:47 -0700 (PDT) From: Tony Tauber To: rpsec@ietf.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Score: 0.0 (/) X-Scan-Signature: 6d62ab47271805379d7172ee693a45db Subject: [RPSEC] Agenda items for IETF 61? 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: , Sender: rpsec-bounces@ietf.org Errors-To: rpsec-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 7bac9cb154eb5790ae3b2913587a40de Please send them in in the next few days (if not sooner). Thanks, Tony _______________________________________________ RPSEC mailing list RPSEC@ietf.org https://www1.ietf.org/mailman/listinfo/rpsec From rpsec-bounces@ietf.org Thu Oct 28 14:45:02 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA13031 for ; Thu, 28 Oct 2004 14:45:02 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNFUp-0003O4-DW for rpsec-web-archive@ietf.org; Thu, 28 Oct 2004 14:59:39 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNCmP-0005WP-LV; Thu, 28 Oct 2004 12:05:37 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNBrp-0007l0-AZ; Thu, 28 Oct 2004 11:07:09 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA22565; Thu, 28 Oct 2004 11:07:08 -0400 (EDT) Message-Id: <200410281507.LAA22565@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Date: Thu, 28 Oct 2004 11:07:08 -0400 Cc: rpsec@ietf.org Subject: [RPSEC] I-D ACTION:draft-ietf-rpsec-routing-threats-07.txt 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: , Sender: rpsec-bounces@ietf.org Errors-To: rpsec-bounces@ietf.org X-Spam-Score: 0.4 (/) X-Scan-Signature: e1b0e72ff1bbd457ceef31828f216a86 --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Routing Protocol Security Requirements Working Group of the IETF. Title : Generic Threats to Routing Protocols Author(s) : A. Barbir, et al. Filename : draft-ietf-rpsec-routing-threats-07.txt Pages : 25 Date : 2004-10-27 Routing protocols are subject to attacks that can harm individual users or the network operations as a whole. This document provides a description and a summary of generic threats that affects routing protocols in general. The work describes threats, including threat sources and capabilities, threat actions, and threat consequences as well as a breakdown of routing functions that might be separately attacked. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-rpsec-routing-threats-07.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-rpsec-routing-threats-07.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-rpsec-routing-threats-07.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2004-10-28110250.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-rpsec-routing-threats-07.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-rpsec-routing-threats-07.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2004-10-28110250.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ RPSEC mailing list RPSEC@ietf.org https://www1.ietf.org/mailman/listinfo/rpsec --NextPart--