From msec-admin@securemulticast.org Thu May 9 09:34:10 2002 Received: from pairlist.net (pairlist.net [216.92.1.92]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA20668 for ; Thu, 9 May 2002 09:34:10 -0400 (EDT) Received: from pairlist.net (localhost.pair.com [127.0.0.1]) by pairlist.net (Postfix) with ESMTP id AFC9353766; Thu, 9 May 2002 09:30:10 -0400 (EDT) Delivered-To: msec@pairlist.net Received: from klesh.pair.com (klesh.pair.com [209.68.2.45]) by pairlist.net (Postfix) with SMTP id 3C15E53557 for ; Wed, 8 May 2002 15:49:37 -0400 (EDT) Received: (qmail 3388 invoked by uid 3269); 8 May 2002 19:53:06 -0000 Delivered-To: ietfsmug-securemulticast:org-msec@securemulticast.org Received: (qmail 3383 invoked from network); 8 May 2002 19:53:05 -0000 Received: from web8004.in.yahoo.com (HELO web8004.mail.in.yahoo.com) (203.199.70.64) by klesh.pair.com with SMTP; 8 May 2002 19:53:05 -0000 Message-ID: <20020508195232.4832.qmail@web8004.mail.in.yahoo.com> Received: from [202.141.25.117] by web8004.mail.in.yahoo.com via HTTP; Wed, 08 May 2002 20:52:32 BST From: =?iso-8859-1?q?iccc2002?= To: iccc_2002@yahoo.co.in MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Subject: [MSEC] ICCC 2002 - Call For Papers Sender: msec-admin@securemulticast.org Errors-To: msec-admin@securemulticast.org X-BeenThere: msec@securemulticast.org X-Mailman-Version: 2.0 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: IETF Multicast Security (MSEC) WG list List-Unsubscribe: , List-Archive: Date: Wed, 8 May 2002 20:52:32 +0100 (BST) Content-Transfer-Encoding: 8bit Please accept our apologies should you receive multiple copies of the mail. Also, we hope that you find the information in the mail useful to you. Our apologies if you feel that we are spamming. ******************************************************************* * * * ICCC 2002 * * * * INTERNATIONAL CONFERENCE ON COMPUTER COMMUNICATION * * * * http://iccc2002.ernet.in/ * * August 11-14, 2002 * * Regent Hotel, Bandra, Mumbai, India * * * * Organized by * * The International Council for Computer Communicaion * * * ******************************************************************* Call for Papers =============== "Redefining Internet in the context of Pervasive Computing" Ubiquitous access to pervasive mobile, static and embedded computing resources, will have profound implications for individuals and societies. ICCC 2002 will address technologies, applications, and changes in personal and social life under the theme "Redefining Internet in the context of Pervasive Computing". Original papers are solicited on the topics mentioned below 1. Topics --------- Access Networks for Data Communication Active and Programmable Networks Algorithms for Routing Multicasting and Addressing Audio Indexing BISDN and ATM Broadband Internet Applications Collaborative Workspaces E-Commerce Technologies Electronic Commerce Systems Electronic Publishing Home Networking and Appliances Intelligent Search Engines Internet Growth, Reliability and Management Issues Internet Security Technologies Internet Telephony Intrusion Detection Systems IP over Wireless Mobility Architectures Multimedia Technologies and Networking   Multi-Protocol Label Switching Network Management and Intelligent Networking Nomadic Computing Otical Internet: IP on WDM, Optical Signaling On-line Communities Protocol Engineering QoS in IP networks Security, Authentication and (Traffic engineering, DiffServ, Accounting Systems Media Streaming) Virtual Organizations Virtual Private Networks Web Based Education          Web Farming and Web Caching            Web Traffic Management and Control Wireless Networks; 3G mobile/wireless LAN Integration Wireless ATM 2. Information for Authors -------------------------- Papers should be submitted in PostScript(.ps), Portable Document Format(.pdf) or Microsoft Word Document(.doc) format through the conference website at http://iccc2002.ernet.in/. In case of any problems registering and uploading the paper at the conference website, the paper may be sent via email to iccc2002@iitm.ernet.in Papers should include: Title, name(s) and affiliations(s) of authors, an abstract of no more than 200 words, a set of relevant keywords, text of 2000-6000 words plus figures resulting in a manuscript of no more than 25 double-spaced A4-size pages, and completely cited references including page numbers.     All papers will be refereed and those accepted for presentation at the conference will be included in the Conference Proceedings, to be published by ICCC Press. 3. Important Dates ------------------ 31st May 2002 Last Date for receipt of submitted papers 30th June 2002 Notification of acceptance/rejection 15th July 2002 Last Date for receiving final camera-ready verison of accepted papers 4. Further Details ------------------ Further details are available at the conference website http://iccc2002.ernet.in. or you can directly email your queries to: Prof. S V Raghavan, Network Systems Laboratory, Department of Computer Science and Engineering Indian Institute of Technology Madras, Chennai 600036 INDIA. Tel (Voice) : +91 44 257 8337 (Office) 8355 (Laboratory) 8331 (Messages) Tel (Fax)  : +91 44 257 8352 Email : iccc2002@iitm.ernet.in 5. Program Format -----------------   ICCC 2002 will be organized in sessions addressing key topics. There will be a set of keynote addresses, invited talks, tutorials and state of the art reports, given by internationally renowned researchers and industry leaders.    6. Pre-Conference Tutorial --------------------------   In line with the International Conference convention, pre-conference tutorials (half day / Full day) will be organized in state-of-the-art topics. Proposals are invited giving the topic, extent of coverage, intended audience, and benefits. Please send your proposals to Mr S. Ramakrishnan at ramki@doe.ernet.in with a copy to the Principal Programme Chair at iccc2002@iitm.ernet.in.   7. Technology Showcase Presentations ------------------------------------   ICCC 2002 will additionally invite non-commercial, presentations by manufacturers and vendors on their latest communications technologies. These presentations will provide an excellent opportunity for leading technology developers to describe their latest developments to the conference audience. For further information, please contact the Conference Secretariat.   8. About the location - Mumbai ------------------------------   Mumbai, formerly known as Bombay, is the capital of Maharashtra state and the business capital of India.  It is the fastest moving, and most industrialized city in India. The main languages spoken in the city are Hindi (official language of India) and Marathi (official language of Maharashtra state). Visitors can manage their business/travel with English, which is also widely understood and spoken. Mumbai is well connected and is served by most international and domestic airlines.   August is the last of the three monsoon months. The highest daily temperature at that time would normally be 29 degrees Celsius that is 84 degrees Fahrenheit.   Regular tours from the city provide easy access to the ancient cave paintings and sculptures of Ajanta and Ellora. Mumbai also has shopping malls for good bargains in rich Indian garments.      9. Venue --------   Regent Hotel, Bandra West, Mumbai 400 050, India, a new hotel on theArabian Sea along the beach with all five star facilities and about 25-30 minutes drive from Mumbai airport. ________________________________________________________________________ For live cricket scores download Yahoo! Score Tracker at: http://in.sports.yahoo.com/cricket/tracker.html _______________________________________________ msec mailing list msec@securemulticast.org http://www.pairlist.net/mailman/listinfo/msec From msec-admin@securemulticast.org Fri May 10 10:12:16 2002 Received: from pairlist.net (pairlist.net [216.92.1.92]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA24104 for ; Fri, 10 May 2002 10:12:15 -0400 (EDT) Received: from pairlist.net (localhost.pair.com [127.0.0.1]) by pairlist.net (Postfix) with ESMTP id 881B0536BD; Fri, 10 May 2002 09:37:52 -0400 (EDT) Delivered-To: msec@pairlist.net Received: from klesh.pair.com (klesh.pair.com [209.68.2.45]) by pairlist.net (Postfix) with SMTP id 931375374D for ; Fri, 10 May 2002 09:32:09 -0400 (EDT) Received: (qmail 10170 invoked by uid 3269); 10 May 2002 13:35:42 -0000 Delivered-To: ietfsmug-securemulticast:org-msec@securemulticast.org Received: (qmail 10164 invoked from network); 10 May 2002 13:35:41 -0000 Received: from rumba.cefriel.it (131.175.53.6) by klesh.pair.com with SMTP; 10 May 2002 13:35:41 -0000 Received: by rumba.cefriel.it with Internet Mail Service (5.5.2653.19) id ; Fri, 10 May 2002 15:37:57 +0200 Message-ID: <7B6D8AAF768F194EB3090A0325C8520205655D@rumba.cefriel.it> From: Luca Venturi To: "'msec@securemulticast.org'" Cc: Davide Cerri MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) MIME-Version: 1.0 Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=SHA1; boundary="----=_NextPart_000_0000_01C1F838.47400700" X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Subject: [MSEC] three questions on GDOI... Sender: msec-admin@securemulticast.org Errors-To: msec-admin@securemulticast.org X-BeenThere: msec@securemulticast.org X-Mailman-Version: 2.0 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: IETF Multicast Security (MSEC) WG list List-Unsubscribe: , List-Archive: Date: Fri, 10 May 2002 15:37:48 +0200 This is a multi-part message in MIME format. ------=_NextPart_000_0000_01C1F838.47400700 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Hi everybody, I am a student who is trying to simulate gdoi on 'ns' for my graduation thesis work. Howevere there are some points about gdoi I can't figure out from the draft, and I hope someone from the mailing list can help me: 1) What must happen when a group member notices that it has lost one ore more 'PUSH' messages, e.g. it doesn't know the actual TEK and it notices that thatit is no more able to decrypt the incoming data traffic and/or that it has not the actual KEK to decrypt the TEK? Does it have tu re-run the entire 'PULL' Protocol, or is eventually a single notify message from the member to the GCKS enough? 2) What must happen when a group member decides to leave the group? How does it have to notify its decision to the GCKS? 3) Finally, can you suggest a network topology scenario that might be meaningful for my simulation? Thank you so much in advance for your help Luca Venturi ------=_NextPart_000_0000_01C1F838.47400700 Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Disposition: attachment; filename="smime.p7s" Content-Transfer-Encoding: base64 MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIJBjCCApUw ggH+oAMCAQICAwdOqDANBgkqhkiG9w0BAQQFADCBkjELMAkGA1UEBhMCWkExFTATBgNVBAgTDFdl c3Rlcm4gQ2FwZTESMBAGA1UEBxMJQ2FwZSBUb3duMQ8wDQYDVQQKEwZUaGF3dGUxHTAbBgNVBAsT FENlcnRpZmljYXRlIFNlcnZpY2VzMSgwJgYDVQQDEx9QZXJzb25hbCBGcmVlbWFpbCBSU0EgMjAw MC44LjMwMB4XDTAyMDQyNDA4MjkxMFoXDTAzMDQyNDA4MjkxMFowWzEQMA4GA1UEBBMHVmVudHVy aTENMAsGA1UEKhMETHVjYTEVMBMGA1UEAxMMTHVjYSBWZW50dXJpMSEwHwYJKoZIhvcNAQkBFhJ2 ZW50dXJpQGNlZnJpZWwuaXQwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBAOgHZQCZdsGNot5Q YmndQCvzq6nDbZ+xmmg/6TKEX6jenb+63EF8tByDzQiIkc8Y/WLT3bI9zCpRy1UYU2Zg4sZGXP7B z227my7ALv/VGupqAVuNyCDhjBVLJyRnciyNTTIs7Oyn6e9E+F8Z3ruUZBaGl5rZpVsYDQk19qV/ Ve81AgMBAAGjLzAtMB0GA1UdEQQWMBSBEnZlbnR1cmlAY2VmcmllbC5pdDAMBgNVHRMBAf8EAjAA MA0GCSqGSIb3DQEBBAUAA4GBAAY0MATZYldnFSlYb68pavbpY7awj6gnv8e2jAw/uogsoZFJkkDo aTsImz+f6HIt1meCGLlzM3HDLdKMuWOnKjs0aBldYsdUThi+LJC5KkgepHi92/WpX6IQToSKuX3P Q20Y/tM5qfA3sTw1xTRpanbJumiA82fDhYjrjuwvPQ0dMIIDLTCCApagAwIBAgIBADANBgkqhkiG 9w0BAQQFADCB0TELMAkGA1UEBhMCWkExFTATBgNVBAgTDFdlc3Rlcm4gQ2FwZTESMBAGA1UEBxMJ Q2FwZSBUb3duMRowGAYDVQQKExFUaGF3dGUgQ29uc3VsdGluZzEoMCYGA1UECxMfQ2VydGlmaWNh dGlvbiBTZXJ2aWNlcyBEaXZpc2lvbjEkMCIGA1UEAxMbVGhhd3RlIFBlcnNvbmFsIEZyZWVtYWls IENBMSswKQYJKoZIhvcNAQkBFhxwZXJzb25hbC1mcmVlbWFpbEB0aGF3dGUuY29tMB4XDTk2MDEw MTAwMDAwMFoXDTIwMTIzMTIzNTk1OVowgdExCzAJBgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJu IENhcGUxEjAQBgNVBAcTCUNhcGUgVG93bjEaMBgGA1UEChMRVGhhd3RlIENvbnN1bHRpbmcxKDAm BgNVBAsTH0NlcnRpZmljYXRpb24gU2VydmljZXMgRGl2aXNpb24xJDAiBgNVBAMTG1RoYXd0ZSBQ ZXJzb25hbCBGcmVlbWFpbCBDQTErMCkGCSqGSIb3DQEJARYccGVyc29uYWwtZnJlZW1haWxAdGhh d3RlLmNvbTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEA1GnX1LCUZFtx6UfYDFG26nKRsIRe fS0Nj3sS34UldSh0OkIsYyeflXtL734Zhx2G6qPduc6WZBrCFG5ErHzmj+hND3EfQDimAKOHePb5 lIZererAXnbr2RSjXW56fAylS1V/Bhkpf56aJtVquzgkCGqYx7Hao5iR/Xnb5VrEHLkCAwEAAaMT MBEwDwYDVR0TAQH/BAUwAwEB/zANBgkqhkiG9w0BAQQFAAOBgQDH7JJ+Tvj1lqVnYiqk8E0RYNBv jWBYYawmu1I1XAjPMPuoSpaKH2JCI4wXD/S6ZJwXrEcp352YXtJsYHFcoqzceePnbgBHH7UNKOgC neSa/RP0ptl8sfjcXyMmCZGAc9AUG95DqYMl8uacLxXK/qarigd1iwzdUYRr5PjRzneigTCCAzgw ggKhoAMCAQICEGZFcrfMdPXPY3ZFhNAukQEwDQYJKoZIhvcNAQEEBQAwgdExCzAJBgNVBAYTAlpB MRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUgVG93bjEaMBgGA1UEChMRVGhh d3RlIENvbnN1bHRpbmcxKDAmBgNVBAsTH0NlcnRpZmljYXRpb24gU2VydmljZXMgRGl2aXNpb24x JDAiBgNVBAMTG1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBDQTErMCkGCSqGSIb3DQEJARYccGVy c29uYWwtZnJlZW1haWxAdGhhd3RlLmNvbTAeFw0wMDA4MzAwMDAwMDBaFw0wNDA4MjcyMzU5NTla MIGSMQswCQYDVQQGEwJaQTEVMBMGA1UECBMMV2VzdGVybiBDYXBlMRIwEAYDVQQHEwlDYXBlIFRv d24xDzANBgNVBAoTBlRoYXd0ZTEdMBsGA1UECxMUQ2VydGlmaWNhdGUgU2VydmljZXMxKDAmBgNV BAMTH1BlcnNvbmFsIEZyZWVtYWlsIFJTQSAyMDAwLjguMzAwgZ8wDQYJKoZIhvcNAQEBBQADgY0A MIGJAoGBAN4zMqZjxwklRT7SbngnZ4HF2ogZgpcO40QpimM1Km1wPPrcrvfudG8wvDOQf/k0caCj bZjxw0+iZdsN+kvx1t1hpfmFzVWaNRqdknWoJ67Ycvm6AvbXsJHeHOmr4BgDqHxDQlBRh4M88Dm0 m1SKE4f/s5udSWYALQmJ7JRr6aFpAgMBAAGjTjBMMCkGA1UdEQQiMCCkHjAcMRowGAYDVQQDExFQ cml2YXRlTGFiZWwxLTI5NzASBgNVHRMBAf8ECDAGAQH/AgEAMAsGA1UdDwQEAwIBBjANBgkqhkiG 9w0BAQQFAAOBgQAxsUtHXfkBceX1U2xdedY9mMAmE2KBIqcS+CKV6BtJtyd7BDm6/ObyJOuR+r3s DSo491BVqGz3Da1MG7wD9LXrokefbKIMWI0xQgkRbLAaadErErJAXWr5edDqLiXdiuT82w0fnQLz WtvKPPZE6iZph39Ins6ln+eE2MliYq0FxjGCAqowggKmAgEBMIGaMIGSMQswCQYDVQQGEwJaQTEV MBMGA1UECBMMV2VzdGVybiBDYXBlMRIwEAYDVQQHEwlDYXBlIFRvd24xDzANBgNVBAoTBlRoYXd0 ZTEdMBsGA1UECxMUQ2VydGlmaWNhdGUgU2VydmljZXMxKDAmBgNVBAMTH1BlcnNvbmFsIEZyZWVt YWlsIFJTQSAyMDAwLjguMzACAwdOqDAJBgUrDgMCGgUAoIIBZTAYBgkqhkiG9w0BCQMxCwYJKoZI hvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wMjA1MTAxMzM1MTNaMCMGCSqGSIb3DQEJBDEWBBTEIKTR +viofaikWmupTUP+hVc0dTBYBgkqhkiG9w0BCQ8xSzBJMAoGCCqGSIb3DQMHMA4GCCqGSIb3DQMC AgIAgDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDAHBgUrDgMCGjAKBggqhkiG9w0CBTCBqwYJKwYB BAGCNxAEMYGdMIGaMIGSMQswCQYDVQQGEwJaQTEVMBMGA1UECBMMV2VzdGVybiBDYXBlMRIwEAYD VQQHEwlDYXBlIFRvd24xDzANBgNVBAoTBlRoYXd0ZTEdMBsGA1UECxMUQ2VydGlmaWNhdGUgU2Vy dmljZXMxKDAmBgNVBAMTH1BlcnNvbmFsIEZyZWVtYWlsIFJTQSAyMDAwLjguMzACAwdOqDANBgkq hkiG9w0BAQEFAASBgMkr8y6WMULwWE1Z1w8iRnnQBPLK/UGL9GYJKrzuyIq9SWXqfWfnqHJi2+Ns MBjPw3h424AK5+vyBm1QC6FkRfa2B9bzikqedJTAq8XaErEyShK7y9RRFvgqLcPzKgz295GUYD/4 fUDuH52DPpiEzfg5teiCre21ii/XO6OZV7qzAAAAAAAA ------=_NextPart_000_0000_01C1F838.47400700-- _______________________________________________ msec mailing list msec@securemulticast.org http://www.pairlist.net/mailman/listinfo/msec From msec-admin@securemulticast.org Tue May 14 22:35:29 2002 Received: from pairlist.net (pairlist.net [216.92.1.92]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA18852 for ; Tue, 14 May 2002 22:35:29 -0400 (EDT) Received: from pairlist.net (localhost.pair.com [127.0.0.1]) by pairlist.net (Postfix) with ESMTP id 0F91453709; Tue, 14 May 2002 21:56:07 -0400 (EDT) Delivered-To: msec@pairlist.net Received: from klesh.pair.com (klesh.pair.com [209.68.2.45]) by pairlist.net (Postfix) with SMTP id 08D7B53583 for ; Tue, 14 May 2002 21:55:05 -0400 (EDT) Received: (qmail 79597 invoked by uid 3269); 15 May 2002 01:58:48 -0000 Delivered-To: ietfsmug-securemulticast:org-msec@securemulticast.org Received: (qmail 79594 invoked from network); 15 May 2002 01:58:48 -0000 Received: from softdnserror (HELO sj-msg-core-3.cisco.com) (171.70.157.152) by klesh.pair.com with SMTP; 15 May 2002 01:58:48 -0000 Received: from nisser.cisco.com (nisser.cisco.com [171.71.176.85]) by sj-msg-core-3.cisco.com (8.12.2/8.12.2) with ESMTP id g4F1w7uF012671; Tue, 14 May 2002 18:58:07 -0700 (PDT) Received: from cisco.com ([10.34.255.58] (may be forged)) by nisser.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with SMTP id SAA07446; Tue, 14 May 2002 18:58:09 -0700 (PDT) Message-ID: <3CE1C0AB.5732E5B0@cisco.com> From: Brian Weis X-Mailer: Mozilla 4.61 [en] (X11; U; Linux 2.2.12-20 i686) X-Accept-Language: en MIME-Version: 1.0 To: Luca Venturi Cc: "'msec@securemulticast.org'" , Davide Cerri Subject: Re: [MSEC] three questions on GDOI... References: <7B6D8AAF768F194EB3090A0325C8520205655D@rumba.cefriel.it> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: msec-admin@securemulticast.org Errors-To: msec-admin@securemulticast.org X-BeenThere: msec@securemulticast.org X-Mailman-Version: 2.0 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: IETF Multicast Security (MSEC) WG list List-Unsubscribe: , List-Archive: Date: Tue, 14 May 2002 18:58:03 -0700 Content-Transfer-Encoding: 7bit Hi Luca, Luca Venturi wrote: > > Hi everybody, > > I am a student who is trying to simulate gdoi on 'ns' for my graduation > thesis work. Howevere there are some points about gdoi I can't figure > out from the draft, and I hope someone from the mailing list can help > me: > > 1) What must happen when a group member notices that it has lost one ore > more 'PUSH' messages, e.g. it doesn't know the actual TEK and it notices > that thatit is no more able to decrypt the incoming data traffic and/or > that it has not the actual KEK to decrypt the TEK? Does it have tu > re-run the entire 'PULL' Protocol, or is eventually a single notify > message from the member to the GCKS enough? If the group member receives PUSH messages for the group and finds that he does not have the current keys, then he must do a PULL protocol in order to get the most recent keys. > 2) What must happen when a group member decides to leave the group? How > does it have to notify its decision to the GCKS? We haven't provided a mechanism for a group member to announce his leaving. The only time a GCKS would care is if he's keeping an LKH tree, since only then does he keep state for each group member. In that case a new notify message type might be useful to the GCKS so he can prune his key tree. However, the GCKS can't depend on a group member telling him that he's leaving -- the client might crash or just shut down without notifying the GCKS. The GCKS needs a more reliable mechanism for knowing when group members have left the group. > 3) Finally, can you suggest a network topology scenario that might be > meaningful for my simulation? The following draft describes a couple of topologies: http://www.securemulticast.org/draft-irtf-smug-taxonomy-01.txt You might find other helpful information on www.securemulticast.org as well. Good luck, Brian > Thank you so much in advance for your help > > Luca Venturi -- Brian Weis Strategic Cryptographic Development, ITD, Cisco Systems Telephone: +1 408 526 4796 Email: bew@cisco.com _______________________________________________ msec mailing list msec@securemulticast.org http://www.pairlist.net/mailman/listinfo/msec From msec-admin@securemulticast.org Wed May 29 19:27:35 2002 Received: from pairlist.net (pairlist.net [216.92.1.92]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA07313 for ; Wed, 29 May 2002 19:27:35 -0400 (EDT) Received: from pairlist.net (localhost.pair.com [127.0.0.1]) by pairlist.net (Postfix) with ESMTP id 255DA536D6; Wed, 29 May 2002 19:20:12 -0400 (EDT) Delivered-To: msec@pairlist.net Received: from klesh.pair.com (klesh.pair.com [209.68.2.45]) by pairlist.net (Postfix) with SMTP id 8351A53572 for ; Wed, 29 May 2002 19:19:47 -0400 (EDT) Received: (qmail 11663 invoked by uid 3269); 29 May 2002 23:24:06 -0000 Delivered-To: ietfsmug-securemulticast:org-msec@securemulticast.org Received: (qmail 11657 invoked from network); 29 May 2002 23:24:06 -0000 Received: from sj-msg-core-2.cisco.com (171.69.24.11) by klesh.pair.com with SMTP; 29 May 2002 23:24:06 -0000 Received: from nisser.cisco.com (nisser.cisco.com [171.71.176.85]) by sj-msg-core-2.cisco.com (8.12.2/8.12.2) with ESMTP id g4TNNUPI016210 for ; Wed, 29 May 2002 16:23:30 -0700 (PDT) Received: from cisco.com (dhcp-128-107-212-140.cisco.com [128.107.212.140]) by nisser.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id QAA04433 for ; Wed, 29 May 2002 16:23:28 -0700 (PDT) Message-ID: <3CF562F1.66B34950@cisco.com> From: Brian Weis X-Mailer: Mozilla 4.61 [en] (X11; U; Linux 2.2.12-20 i686) X-Accept-Language: en MIME-Version: 1.0 To: msec@securemulticast.org Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: [MSEC] GDOI reference implementation available Sender: msec-admin@securemulticast.org Errors-To: msec-admin@securemulticast.org X-BeenThere: msec@securemulticast.org X-Mailman-Version: 2.0 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: IETF Multicast Security (MSEC) WG list List-Unsubscribe: , List-Archive: Date: Wed, 29 May 2002 16:23:29 -0700 Content-Transfer-Encoding: 7bit An open source reference implementation of GDOI is now available at http://www.vovida.org. Look for "GDOI" under "Protocols" in the leftmost frame. Enjoy, Brian -- Brian Weis Strategic Cryptographic Development, ITD, Cisco Systems Telephone: +1 408 526 4796 Email: bew@cisco.com _______________________________________________ msec mailing list msec@securemulticast.org http://www.pairlist.net/mailman/listinfo/msec