From mailnull@www1.ietf.org Mon Jun 2 06:00:14 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA00228 for ; Mon, 2 Jun 2003 06:00:14 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h529xnT29907 for rpsec-archive@odin.ietf.org; Mon, 2 Jun 2003 05:59:49 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h529xnB29903 for ; Mon, 2 Jun 2003 05:59:49 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA00184 for ; Mon, 2 Jun 2003 05:59:43 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Mm4l-0001Ww-00 for rpsec-web-archive@ietf.org; Mon, 02 Jun 2003 05:57:59 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19Mm4k-0001Wt-00 for rpsec-web-archive@ietf.org; Mon, 02 Jun 2003 05:57:58 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h529xOB29870; Mon, 2 Jun 2003 05:59:24 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h529wvB29810 for ; Mon, 2 Jun 2003 05:58:57 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA00119; Mon, 2 Jun 2003 05:58:50 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Mm3u-0001VV-00; Mon, 02 Jun 2003 05:57:06 -0400 Received: from thurn.corp.titan.com ([159.62.51.20]) by ietf-mx with esmtp (Exim 4.12) id 19Mm3t-0001VR-00; Mon, 02 Jun 2003 05:57:05 -0400 Received: from vcmd-nt1.validity.com (val114-005.validity.titan.com [159.62.114.5]) by thurn.corp.titan.com (8.12.9/8.12.9) with ESMTP id h529wifo024520; Mon, 2 Jun 2003 02:58:44 -0700 Received: by VCMD-NT1 with Internet Mail Service (5.5.2655.55) id ; Mon, 2 Jun 2003 05:57:45 -0400 Message-ID: <561621C69F17D511A3A20050047340EC01AAF709@VCMD-NT1> From: "Ferrell, William" To: "'rpsec-request@ietf.org '" , "'rpsec@ietf.org '" Cc: "'rpsec@ietf.org'" , "'jhaas@nexthop.com'" , "'riw@cisco.com'" , "'piyush_bhatnagar@hotmail.com'" Date: Mon, 2 Jun 2003 05:57:44 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2655.55) Content-Type: text/plain Subject: [RPSEC] RE: RPSEC digest, Vol 1 #157 - 3 msgs Sender: rpsec-admin@ietf.org Errors-To: rpsec-admin@ietf.org X-BeenThere: rpsec@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Routing Protocol Security Requirements List-Post: List-Help: List-Subscribe: , Stephen 1. When I mention Barry Green , the name barely needs justification for his impact on the routing community. Are you familiar with Cisco press-ISP essentials ? 2. The intent of my comment was for the technical perspective only to add sound Technical value and discussion. Im a Routing-Security Engineer ,My apologies if my english is a bit sketchy , I cant spend a lot of time sparring with you on less valueable symantics and english compositon. 3. Would you like to lend any technical opinion to the documentation? it would be more usefull in this forum. -----Original Message----- From: rpsec-request@ietf.org To: rpsec@ietf.org Sent: 5/30/03 12:00 PM Subject: RPSEC digest, Vol 1 #157 - 3 msgs Send RPSEC mailing list submissions to rpsec@ietf.org To subscribe or unsubscribe via the World Wide Web, visit https://www1.ietf.org/mailman/listinfo/rpsec or, via email, send a message with subject or body 'help' to rpsec-request@ietf.org You can reach the person managing the list at rpsec-admin@ietf.org When replying, please edit your Subject line so it is more specific than "Re: Contents of RPSEC digest..." Today's Topics: 1. RE: Initial comments on draft-ietf-rpsec-routing-threats -01.txt (Stephen Kent) 2. Re: Comments on the Threats Draft.... (Piyush Bhatnagar) --__--__-- Message: 1 Date: Wed, 28 May 2003 11:07:17 -0400 To: "Ferrell, William" , "'rpsec@ietf.org'" From: Stephen Kent Subject: RE: [RPSEC] Initial comments on draft-ietf-rpsec-routing-threats -01.txt --============_-1157877368==_ma============ Content-Type: text/plain; charset="us-ascii" ; format="flowed" At 12:05 PM -0400 5/23/03, Ferrell, William wrote: > > > >Only a limited set of comments ,most are in reference to the editorials >or comments to the original text/author > >1. This definition model is becoming widely used and >well-known/well-understood in the industry. One of the major proponents >of this model is Barry Green of Cisco. His work goes without >explanation. I assume this phrase is supposed to be a compliment, but in normal English usage that's not clear. Irrespective of quality of the material in question, to better make your point you should cite some body of peer-reviewed, published work (vs. company-published documents, slide sets, etc.) by Barry. Steve --============_-1157877368==_ma============ Content-Type: text/html; charset="us-ascii" RE: [RPSEC] Initial comments on draft-ietf-rpsec-routi
At 12:05 PM -0400 5/23/03, Ferrell, William wrote:
 


Only a limited set of comments ,most are in reference to the editorials
or comments to the original text/author

1. This definition model is becoming widely used and
well-known/well-understood in the industry. One of the major proponents
of this model is Barry Green of Cisco. His work goes without
explanation.

I assume this phrase is supposed to be a compliment, but in normal English usage that's not clear. Irrespective of quality of the material in question, to better make your point you should cite some body of peer-reviewed, published work (vs. company-published documents, slide sets, etc.) by Barry.

Steve
--============_-1157877368==_ma============-- --__--__-- Message: 2 From: "Piyush Bhatnagar" To: "Jeffrey Haas" , "Russ White" Cc: Subject: Re: [RPSEC] Comments on the Threats Draft.... Date: Fri, 30 May 2003 04:04:27 -0400 I tend to agree with Jeff. We should try and add such a section or point to a place that does so. Through out the document we talk about threats to routing protocols by using multiple and at times overlaping classifications which lead to some confusion. I think it is also confusing to use different classifications interchangeably. I must agree that it is quite useful to describe the different classifications in this document but then after the description of various classifications, we should choose one classification to be used through the rest of the document for the sake of clarity. Also, these threats result in various threat consequences. In my opinion, it might be useful quite to create a matrix of threats and threat consequences depicting what threats can result in which threat consequences. This will be a very good way to summarize the document as well. Just my 2 cents. - Regards, Piyush ========================== Piyush Bhatnagar, CISSP piyush_bhatnagar@hotmail.com ========================== ----- Original Message ----- From: "Jeffrey Haas" To: "Russ White" Cc: Sent: Tuesday, May 27, 2003 12:40 PM Subject: Re: [RPSEC] Comments on the Threats Draft.... > On Wed, May 21, 2003 at 09:19:31AM -0400, Russ White wrote: > > by routing protocols, can make intelligent decisions when forwarding > > traffic from one port to another. > > We might not want to say "port" here. > > > This work describes such attack methods in terms of threats, including > > threat sources and capabilities, threat actions, and threat > > consequences. > > Given that the taxonomy beteween "security people" and "routing security > people" doesn't always seem to match, are we planning on doing > either a section on taxonomy or pointing to somewhere else that does so? > > -- > Jeff Haas > NextHop Technologies > _______________________________________________ > 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 End of RPSEC Digest _______________________________________________ RPSEC mailing list RPSEC@ietf.org https://www1.ietf.org/mailman/listinfo/rpsec From mailnull@www1.ietf.org Mon Jun 2 17:55:57 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA25836 for ; Mon, 2 Jun 2003 17:55:57 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h52LtX426924 for rpsec-archive@odin.ietf.org; Mon, 2 Jun 2003 17:55:33 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h52LtXB26921 for ; Mon, 2 Jun 2003 17:55:33 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA25806 for ; Mon, 2 Jun 2003 17:55:27 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19MxFO-0006rN-00 for rpsec-web-archive@ietf.org; Mon, 02 Jun 2003 17:53:42 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19MxFN-0006rJ-00 for rpsec-web-archive@ietf.org; Mon, 02 Jun 2003 17:53:41 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h52LsSB26787; Mon, 2 Jun 2003 17:54:28 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h52LqQB26653 for ; Mon, 2 Jun 2003 17:52:26 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA25673 for ; Mon, 2 Jun 2003 17:52:20 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19MxCN-0006qE-00 for rpsec@ietf.org; Mon, 02 Jun 2003 17:50:35 -0400 Received: from mesa.bbnplanet.com ([171.78.172.21]) by ietf-mx with esmtp (Exim 4.12) id 19MxCM-0006q5-00 for rpsec@ietf.org; Mon, 02 Jun 2003 17:50:34 -0400 Received: from localhost (ttauber@localhost) by mesa.bbnplanet.com (8.10.2+Sun/8.10.2) with ESMTP id h52LplX20576; Mon, 2 Jun 2003 17:51:47 -0400 (EDT) X-Authentication-Warning: mesa.bbnplanet.com: ttauber owned process doing -bs Date: Mon, 2 Jun 2003 17:51:47 -0400 (EDT) From: Tony Tauber X-X-Sender: ttauber@mesa.bbnplanet.com To: "Ferrell, William" cc: "'rpsec@ietf.org '" , "'jhaas@nexthop.com'" , "'riw@cisco.com'" , "'piyush_bhatnagar@hotmail.com'" In-Reply-To: <561621C69F17D511A3A20050047340EC01AAF709@VCMD-NT1> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: [RPSEC] List Etiquitte Sender: rpsec-admin@ietf.org Errors-To: rpsec-admin@ietf.org X-BeenThere: rpsec@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Routing Protocol Security Requirements List-Post: List-Help: List-Subscribe: , On Mon, 2 Jun 2003, Ferrell, William wrote: > Stephen > > 1. When I mention Barry Green , the name barely needs justification > for his impact on the routing community. Are you familiar with Cisco > press-ISP essentials ? I'm pretty sure Steve and Barry know each other as I had some hallway conversation with both of them at the last IETF meeting. > 2. The intent of my comment was for the technical perspective only > to add sound Technical value and discussion. Im a Routing-Security > Engineer ,My apologies if my english is a bit sketchy , I cant spend > a lot of time sparring with you on less valueable symantics and > english compositon. 3. Would you like to lend any technical opinion > to the documentation? it would be more usefull in this forum. [List-moderator hat on.] OK folks, let's keep it clean out there. To Steve's point, if your intent is to cite Barry's work as being valuable to the threat definition modeling, it'd help more to provide specific references (eg. URLs) so we could all see exactly which parts you had in mind that would help the effort. Beyond that, realize that some language mistakes rendered by non-native speakers or by typos can actually render the meaning of the words or intent of the author completely indeterminate. Trying to assume what people intend in these cases can lead to further misunderstanding. To William's point, let's keep the discussion as on-topic and as constructive as may be possible. We don't want to discourage the input of people with less English facility, certainly. Thanks, Tony > -----Original Message----- > At 12:05 PM -0400 5/23/03, Ferrell, William wrote: > > > >Only a limited set of comments ,most are in reference to the > >editorials or comments to the original text/author > > > >1. This definition model is becoming widely used and > >well-known/well-understood in the industry. One of the major > >proponents of this model is Barry Green of Cisco. His work goes > >without explanation. > > I assume this phrase is supposed to be a compliment, but in normal > English usage that's not clear. Irrespective of quality of the > material in question, to better make your point you should cite some > body of peer-reviewed, published work (vs. company-published > documents, slide sets, etc.) by Barry. > > Steve > > > > Given that the taxonomy beteween "security people" and "routing > > security people" doesn't always seem to match, are we planning on > > doing either a section on taxonomy or pointing to somewhere else > > that does so? > > > > -- > > Jeff Haas _______________________________________________ RPSEC mailing list RPSEC@ietf.org https://www1.ietf.org/mailman/listinfo/rpsec From mailnull@www1.ietf.org Mon Jun 2 21:52:23 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA03870 for ; Mon, 2 Jun 2003 21:52:23 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h531pwT12305 for rpsec-archive@odin.ietf.org; Mon, 2 Jun 2003 21:51:58 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h531pwB12302 for ; Mon, 2 Jun 2003 21:51:58 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA03829 for ; Mon, 2 Jun 2003 21:51:52 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19N0wA-0000ov-00 for rpsec-web-archive@ietf.org; Mon, 02 Jun 2003 21:50:07 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19N0wA-0000os-00 for rpsec-web-archive@ietf.org; Mon, 02 Jun 2003 21:50:06 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h531pFB12274; Mon, 2 Jun 2003 21:51:15 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h531oBB12238 for ; Mon, 2 Jun 2003 21:50:11 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA03790 for ; Mon, 2 Jun 2003 21:50:06 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19N0uS-0000o9-00 for rpsec@ietf.org; Mon, 02 Jun 2003 21:48:20 -0400 Received: from aragorn.bbn.com ([128.33.0.62]) by ietf-mx with esmtp (Exim 4.12) id 19N0uR-0000nq-00 for rpsec@ietf.org; Mon, 02 Jun 2003 21:48:20 -0400 Received: from [10.1.71.70] (SSH.BBN.COM [192.1.50.70]) by aragorn.bbn.com (8.12.7/8.12.7) with ESMTP id h531nLDJ000215; Mon, 2 Jun 2003 21:49:36 -0400 (EDT) Mime-Version: 1.0 X-Sender: kent@localhost Message-Id: In-Reply-To: <561621C69F17D511A3A20050047340EC01AAF709@VCMD-NT1> References: <561621C69F17D511A3A20050047340EC01AAF709@VCMD-NT1> Date: Mon, 2 Jun 2003 21:48:03 -0400 To: "Ferrell, William" , "'rpsec@ietf.org '" From: Stephen Kent Subject: [RPSEC] RE: RPSEC digest, Vol 1 #157 - 3 msgs Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Scanned-By: MIMEDefang 2.28 (www . roaringpenguin . com / mimedefang) Sender: rpsec-admin@ietf.org Errors-To: rpsec-admin@ietf.org X-BeenThere: rpsec@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Routing Protocol Security Requirements List-Post: List-Help: List-Subscribe: , At 5:57 AM -0400 6/2/03, Ferrell, William wrote: >Stephen > > >1. When I mention Barry Green , the name barely needs justification for his >impact on the routing community. Are you familiar with Cisco press-ISP >essentials ? I tend not to read vendor-sponsored publications of this sort. That's why I mentioned refereed publications as a suitable basis for citing someone's credentials and relevant work. >2. The intent of my comment was for the technical perspective only to add >sound Technical value and discussion. Im a Routing-Security Engineer ,My >apologies if my english is a bit sketchy , I cant spend a lot of time >sparring with you on less valueable symantics and english compositon. Words are the means by which we communicate ideas in document. We need to pay close attention to the choice of words, or we run the risk of confusing readers. >3. Would you like to lend any technical opinion to the documentation? it >would be more usefull in this forum. I have already sent an example of a threat model to assist in this work. I also have also authored several papers on securing BGP, peer-reviewed papers of the sort I note above. These provide potential inputs for the work of this WG. Steve _______________________________________________ RPSEC mailing list RPSEC@ietf.org https://www1.ietf.org/mailman/listinfo/rpsec From exim@www1.ietf.org Tue Jun 24 06:57:47 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA11069 for ; Tue, 24 Jun 2003 06:57:47 -0400 (EDT) Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5OAvLS21207 for rpsec-archive@odin.ietf.org; Tue, 24 Jun 2003 06:57:21 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19UlUH-0005Va-O8 for rpsec-web-archive@optimus.ietf.org; Tue, 24 Jun 2003 06:57:21 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA11043 for ; Tue, 24 Jun 2003 06:57:17 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19UlUD-00026B-00 for rpsec-web-archive@ietf.org; Tue, 24 Jun 2003 06:57:17 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19UlU7-00025x-00 for rpsec-web-archive@ietf.org; Tue, 24 Jun 2003 06:57:11 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19UlTx-0005Kt-DE; Tue, 24 Jun 2003 06:57:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19UlTT-0005KF-7N for rpsec@optimus.ietf.org; Tue, 24 Jun 2003 06:56:31 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA10854; Tue, 24 Jun 2003 06:56:26 -0400 (EDT) Message-Id: <200306241056.GAA10854@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; CC: idr@ietf.org, rpsec@ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Date: Tue, 24 Jun 2003 06:56:25 -0400 Subject: [RPSEC] I-D ACTION:draft-weis-sobgp-certificates-00.txt Sender: rpsec-admin@ietf.org Errors-To: rpsec-admin@ietf.org X-BeenThere: rpsec@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Routing Protocol Security Requirements List-Post: List-Help: List-Subscribe: , --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : Secure Origin BGP (soBGP) Certificates Author(s) : B. Weis Filename : draft-weis-sobgp-certificates-00.txt Pages : 38 Date : 2003-6-23 This document describes the format of digital certificates that are used by the Secure Origin BGP (soBGP) extensions to BGP, as well as acceptable use of those certificates. Included are certificates providing authentication, authorization, and policy distribution. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-weis-sobgp-certificates-00.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. 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-weis-sobgp-certificates-00.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-weis-sobgp-certificates-00.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: <2003-6-23142320.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-weis-sobgp-certificates-00.txt --OtherAccess Content-Type: Message/External-body; name="draft-weis-sobgp-certificates-00.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2003-6-23142320.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ RPSEC mailing list RPSEC@ietf.org https://www1.ietf.org/mailman/listinfo/rpsec