From rpsec-admin@ietf.org Sat Jun 1 04:08:29 2002 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA05031 for ; Sat, 1 Jun 2002 04:08:29 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA09415; Sat, 1 Jun 2002 04:07:33 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA09381 for ; Sat, 1 Jun 2002 04:07:32 -0400 (EDT) Received: from hermes.toad.net (hermes.toad.net [162.33.130.251]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA04968 for ; Sat, 1 Jun 2002 04:07:06 -0400 (EDT) Received: from gwu.edu (dboney-01.dslbr.toad.net [162.33.159.86]) by hermes.toad.net (8.11.6/8.11.6) with ESMTP id g5187TP21547; Sat, 1 Jun 2002 04:07:29 -0400 Message-ID: <3CF880BF.3060105@gwu.edu> Date: Sat, 01 Jun 2002 04:07:27 -0400 From: "David G. Boney" Organization: The George Washington University User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4.1) Gecko/20020508 Netscape6/6.2.3 X-Accept-Language: en-us MIME-Version: 1.0 To: rpsec@ietf.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [RPSEC] One way to view the security requirements for routing Sender: rpsec-admin@ietf.org Errors-To: rpsec-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: Routing Protocol Security Requirements X-BeenThere: rpsec@ietf.org Content-Transfer-Encoding: 7bit Below are some ideas on how to view the problem. First, someone had requested some security background information for people more knowledgeable about routing than security. Below is a link to a paper on general security models. A second link is to a paper on risk management. Also, there are a couple of links to the Common Criteria. I provided the link to the risk assessment paper to give a high level overview of how security is approached ( risk management is the current alter at which the security profession worships, there have been previous alters, I expect in the future there will new alters as risk management has a fatal flaw in that there is not enough loss data to computer the loss probability). I point out the Common Criteria because it provides a framework for specify security requirements. I am not recommending the use of the Common Criteria, I get a headache trying to read it, but part two is very useful for having a concise reference to the security functions that have been previously defined. There is a draft protection profile for switches and routers but I find it completely lacking as it does not seem to address vulnerabilities of routing or switching functionality. Underlying Technical Models for Information Technology Security http://csrc.nist.gov/publications/nistpubs/800-33/sp800-33.pdf Risk Management Guide for Information Technology Systems http://csrc.nist.gov/publications/nistpubs/800-30/sp800-30.pdf Common Criteria http://www.commoncriteria.org/docs/PDF/CCPART1V21.PDF http://www.commoncriteria.org/docs/PDF/CCPART2V21.PDF http://www.commoncriteria.org/docs/PDF/CCPART3V21.PDF Protection Profile for Switches and Routers http://www.commoncriteria.org/ccc/protection_profiles/ppdetail.jsp?id=PP-024 -------------- A model for specifying routing and switching vulnerabilities A model for discussing routing and switching vulnerabilities is proposed. This model is based on the identifying the effects of attacks on different routing and switching functions. Think of this as a three dimensional model. On one axis are the different routing functions. Here is a partial example, I am sure there are more elaborate taxonomies: topology discovery, topology advertising, forwarding, queuing, scheduling, resource allocation. On the second axis are the methods of attacks. One taxonomy that can be used to identify attacks is to refer to the security functions identified in part 2 of the Common Criteria and ask the question of what is the threat if I do not have this security function or how could I be attacked if I did not provide this security function. This also identifies a list of countermeasures, the security functions, for use in later analysis. The third axis is the impact of the attack. How is routing or switching effected by the attack? Examples might be: misroutes, network partition, changes in QOS. The goal is identify the end effects of the attacks as the vulnerability. The problem with most security models is that they are too low level and do not tell you what is important. To say that the vulnerability is that data in transmission can be manipulated does not really help you. To say how it effected your routing functions such as altering the routing table which lead to a misroute is far more useful. Once you have identified your vulnerabilities, you can address the countermeasures you need to reduce the risk of the vulnerabilities. Having identified your threats, vulnerabilities, and countermeasures should provide a useful framework for writing the security requirements. To develop a generic set of security requirements, analyze all the routing and switching protocols and identify the common patterns that emerge. Ok, that last statement sound like a school assignment but a good portion of the work is in the literature. One shortcoming with the above approach is that the security functions listed in the Common Criteria may not identify some of the issues associated with the fault tolerant point of view that is developing in security. But these functions can be easily added when identified. -- Sincerely, David G. Boney Graduate Research Assistant Department of Electrical and Computer Engineering The George Washington University Phillips Hall, Suite 607 801 22nd Street, N.W. Washington, DC 20052 http://student.seas.gwu.edu/~dboney mailto:dboney@gwu.edu Department Phone (202) 994-6083 Department Fax (202) 994-0227 "I don't get up until noon, I only work a couple of hours a day, and I spend the rest of my time reading. I guess my calling in life is to be a professor." _______________________________________________ RPSEC mailing list RPSEC@ietf.org https://www1.ietf.org/mailman/listinfo/rpsec From mailman-owner@ietf.org Sat Jun 1 07:00:38 2002 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA18792 for ; Sat, 1 Jun 2002 07:00:38 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA09427 for ; Sat, 1 Jun 2002 07:01:04 -0400 (EDT) Date: Sat, 1 Jun 2002 07:01:04 -0400 (EDT) Message-Id: <200206011101.HAA09427@optimus.ietf.org> From: mailman-owner@ietf.org Subject: ietf.org mailing list memberships reminder To: rpsec-web-archive@ietf.org X-No-Archive: yes Precedence: bulk X-Mailman-Version: 1.0 Precedence: bulk List-Id: Session Initiation Protocol 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, rpsec-request@ietf.org) containing just the word 'help' in the message body, and an email message will be sent to you with instructions. 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@ietf.org From rpsec-admin@ietf.org Sun Jun 2 20:04:52 2002 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA20782 for ; Sun, 2 Jun 2002 20:04:52 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA26078; Sun, 2 Jun 2002 20:03:52 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA26046 for ; Sun, 2 Jun 2002 20:03:50 -0400 (EDT) Received: from cisco.com (uzura.cisco.com [64.102.17.77]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA20774 for ; Sun, 2 Jun 2002 20:03:22 -0400 (EDT) Received: from ruwhite-u10.cisco.com (ruwhite-u10.cisco.com [64.102.48.251]) by cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) with ESMTP id UAA25849; Sun, 2 Jun 2002 20:03:13 -0400 (EDT) Date: Sun, 2 Jun 2002 20:03:13 -0400 (EDT) From: Russ White Reply-To: Russ White To: Marwaha Shivanajay cc: rpsec@ietf.org Subject: RE: [RPSEC] MPLS Security In-Reply-To: <6330DC96389A924A804F52FA3848930E5B3E6B@MBXSRV26.stu.nus.edu.sg> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: rpsec-admin@ietf.org Errors-To: rpsec-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: Routing Protocol Security Requirements X-BeenThere: rpsec@ietf.org I think both would be, from a routing and requirements perspective (not from an actual mechanism or traffic perspective). :-) Russ On Fri, 31 May 2002, Marwaha Shivanajay wrote: > We may also inlcude ad hoc network routing security. > > Regards, > Shivanajay > -~-~-~-~-~-~-~-~-~-~-~-~ > Research Scholar, > Dept. of Electrical and Comp. Eng. > National University of Singapore > Singapore. > -~-~-~-~-~-~-~-~-~-~-~-~ > > -----Original Message----- > From: David G. Boney [mailto:dboney@gwu.edu] > Sent: Friday, May 31, 2002 5:57 AM > To: rpsec@ietf.org > Subject: [RPSEC] MPLS Security > > > Hi, > > Would MPLS security be within the bounds of this group? > -- > > Sincerely, > David G. Boney > > Graduate Research Assistant > Department of Electrical and Computer Engineering > The George Washington University > Phillips Hall, Suite 607 > 801 22nd Street, N.W. > Washington, DC 20052 > > http://student.seas.gwu.edu/~dboney > mailto:dboney@gwu.edu > Department Phone (202) 994-6083 > Department Fax (202) 994-0227 > > "I don't get up until noon, I only work a couple of hours > a day, and I spend the rest of my time reading. > I guess my calling in life is to be a professor." > > > > > > _______________________________________________ > RPSEC mailing list > RPSEC@ietf.org > https://www1.ietf.org/mailman/listinfo/rpsec > > _______________________________________________ > RPSEC mailing list > RPSEC@ietf.org > https://www1.ietf.org/mailman/listinfo/rpsec > __________________________________ riw@cisco.com CCIE <>< Grace Alone _______________________________________________ RPSEC mailing list RPSEC@ietf.org https://www1.ietf.org/mailman/listinfo/rpsec From rpsec-admin@ietf.org Sat Jun 8 22:31:14 2002 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA15474 for ; Sat, 8 Jun 2002 22:31:14 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA23287; Sat, 8 Jun 2002 22:30:07 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA23194 for ; Sat, 8 Jun 2002 22:29:55 -0400 (EDT) Received: from rs1.arin.net (rs1.arin.net [192.149.252.21]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA15378 for ; Sat, 8 Jun 2002 22:28:52 -0400 (EDT) Received: from ops.arin.net (ops.arin.net [192.149.252.141]) by rs1.arin.net (8.9.3/8.9.3) with ESMTP id WAA08506; Sat, 8 Jun 2002 22:29:04 -0400 (EDT) Received: from donvaiont (localhost [127.0.0.1]) by ops.arin.net (8.9.0/8.9.0) with SMTP id WAA07790; Sat, 8 Jun 2002 22:29:03 -0400 (EDT) From: "Don Wilder" To: "Russ White" , Subject: RE: [RPSEC] Current Drafts.... (fwd) Date: Sat, 8 Jun 2002 22:28:35 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 In-Reply-To: Importance: Normal Content-Transfer-Encoding: 7bit Sender: rpsec-admin@ietf.org Errors-To: rpsec-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: Routing Protocol Security Requirements X-BeenThere: rpsec@ietf.org Content-Transfer-Encoding: 7bit Russ, Not sure how much I can help the effort, But count me in if you still need helpers. Don Wilder > -----Original Message----- > From: rpsec-admin@ietf.org [mailto:rpsec-admin@ietf.org]On Behalf Of > Russ White > Sent: Friday, May 17, 2002 7:36 AM > To: rpsec@ietf.org > Subject: [RPSEC] Current Drafts.... (fwd) > > > > > __________________________________ > riw@cisco.com CCIE <>< Grace Alone > > > ---------- Forwarded message ---------- > Date: Fri, 17 May 2002 00:06:04 -0400 > From: Harikrishna G. > To: "'riw@cisco.com'" > Subject: [RPSEC] Current Drafts.... > > > Russ, > I'm intereseted in working on it. > > -Hari > -----Original Message----- > From: Naidu, Venkata [mailto:Venkata.Naidu@marconi.com] > Sent: Thursday, May 16, 2002 9:00 PM > To: 'Russ White' > Cc: 'rpsec@ietf.org' > Subject: RE: [RPSEC] Current Drafts.... > > > Russ, > > Add me to the team. > > -- > Venkata. > > -> Y'all: > -> > -> Is anyone working on a requirements draft, or requirements > -> drafts? Should we form a small team to go out and do this? Just > -> trying to figure out if work has started, and how to proceed. > -> > -> :-) > -> > -> Russ > > _______________________________________________ > RPSEC mailing list > RPSEC@ietf.org > https://www1.ietf.org/mailman/listinfo/rpsec > > > _______________________________________________ > RPSEC mailing list > RPSEC@ietf.org > https://www1.ietf.org/mailman/listinfo/rpsec _______________________________________________ RPSEC mailing list RPSEC@ietf.org https://www1.ietf.org/mailman/listinfo/rpsec From rpsec-admin@ietf.org Wed Jun 19 05:23:55 2002 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA11557 for ; Wed, 19 Jun 2002 05:23:55 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA11886; Wed, 19 Jun 2002 05:21:54 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA11847 for ; Wed, 19 Jun 2002 05:21:52 -0400 (EDT) Received: from ims21.stu.nus.edu.sg (ims21.stu.nus.edu.sg [137.132.14.26]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA11516; Wed, 19 Jun 2002 05:21:10 -0400 (EDT) Received: from mbxsrv26.stu.nus.edu.sg ([137.132.14.236]) by ims21.stu.nus.edu.sg with Microsoft SMTPSVC(5.0.2195.4905); Wed, 19 Jun 2002 17:21:48 +0800 X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 19 Jun 2002 17:21:48 +0800 Message-ID: <6330DC96389A924A804F52FA3848930E703C74@MBXSRV26.stu.nus.edu.sg> Thread-Topic: Mobile agents in manets Thread-Index: AcHn4WP1039pLr99T7Oca3sXx9bkPQvjm30A From: "Marwaha Shivanajay" To: Cc: X-OriginalArrivalTime: 19 Jun 2002 09:21:48.0289 (UTC) FILETIME=[BCE8F710:01C21772] Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id FAA11850 Subject: [RPSEC] Mobile agents in manets Sender: rpsec-admin@ietf.org Errors-To: rpsec-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: Routing Protocol Security Requirements X-BeenThere: rpsec@ietf.org Content-Transfer-Encoding: 8bit Dear All, Can somebody point me to suggestions, scope & papers on applications & use of mobile agents in MANETs. Is someone working on the use of mobile agents in MANETs. Thanks, Shivanajay Marwaha ********************************* M. Eng. Research Scholar ECE Dept., National University of Singapore. www.nus.edu.sg ********************************* _______________________________________________ RPSEC mailing list RPSEC@ietf.org https://www1.ietf.org/mailman/listinfo/rpsec From rpsec-admin@ietf.org Wed Jun 19 07:30:38 2002 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA13966 for ; Wed, 19 Jun 2002 07:30:38 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA19055; Wed, 19 Jun 2002 07:30:16 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA14665 for ; Wed, 19 Jun 2002 06:14:51 -0400 (EDT) Received: from p-voyageur.rd.francetelecom.fr (p-voyageur.rd.francetelecom.fr [139.100.0.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA12177; Wed, 19 Jun 2002 06:14:10 -0400 (EDT) Received: by p-voyageur.rd.francetelecom.fr with Internet Mail Service (5.5.2655.55) id ; Wed, 19 Jun 2002 12:08:07 +0200 Message-ID: <0489A7888F080B4BA73B53F7E145F29A03C07F@LANMHS20.rd.francetelecom.fr> From: MEDDOUR Djamal Eddine thesard FTRD/DAC/LAN To: "'Marwaha Shivanajay'" , manet@ietf.org Cc: rpsec@ietf.org Date: Wed, 19 Jun 2002 11:36:13 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2655.55) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C21774.C07C36E0" Subject: [RPSEC] RE: [manet] Mobile agents in manets Sender: rpsec-admin@ietf.org Errors-To: rpsec-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: Routing Protocol Security Requirements X-BeenThere: rpsec@ietf.org This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C21774.C07C36E0 Content-Type: text/plain hi you can see MAGNET (Mobile Agent For AdHoc Networking) www.inagaki.nuie.nagoya-u.ac.jp/~kawaguti/research/ regards -----Message d'origine----- De : Marwaha Shivanajay [mailto:engp1609@nus.edu.sg] Envoye : mercredi 19 juin 2002 11:22 A : manet@ietf.org Cc : rpsec@ietf.org Objet : [manet] Mobile agents in manets Dear All, Can somebody point me to suggestions, scope & papers on applications & use of mobile agents in MANETs. Is someone working on the use of mobile agents in MANETs. Thanks, Shivanajay Marwaha ********************************* M. Eng. Research Scholar ECE Dept., National University of Singapore. www.nus.edu.sg ********************************* _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet ------_=_NextPart_001_01C21774.C07C36E0 Content-Type: text/html Content-Transfer-Encoding: quoted-printable RE: [manet] Mobile agents in manets

hi

you can see MAGNET (Mobile Agent For AdHoc = Networking)

www.inagaki.nuie.nagoya-u.ac.jp/~kawaguti/research/ =

regards

-----Message d'origine-----
De : Marwaha Shivanajay [mailto:engp1609@nus.edu.sg]
Envoye : mercredi 19 juin 2002 11:22
A : manet@ietf.org
Cc : rpsec@ietf.org
Objet : [manet] Mobile agents in manets


Dear All,
Can somebody point me to suggestions, scope & = papers on applications &
use of mobile agents in MANETs.
Is someone working on the use of mobile agents in = MANETs.

Thanks,
Shivanajay Marwaha
*********************************
M. Eng. Research Scholar
ECE Dept.,
National University of Singapore.
www.nus.edu.sg
*********************************




_______________________________________________
manet mailing list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet

------_=_NextPart_001_01C21774.C07C36E0-- _______________________________________________ RPSEC mailing list RPSEC@ietf.org https://www1.ietf.org/mailman/listinfo/rpsec