From sidr-bounces@ietf.org Mon Feb 05 23:23:36 2007 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HEHqg-00074Z-N3; Mon, 05 Feb 2007 23:22:30 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HEHqe-00074T-Md for sidr@ietf.org; Mon, 05 Feb 2007 23:22:28 -0500 Received: from nutshell.tislabs.com ([192.94.214.100]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HEHqd-00007B-CG for sidr@ietf.org; Mon, 05 Feb 2007 23:22:28 -0500 Received: (from uucp@localhost) by nutshell.tislabs.com (8.12.9/8.12.9) id l164KmuX017379 for ; Mon, 5 Feb 2007 23:20:48 -0500 (EST) Received: from pecan.tislabs.com(10.66.1.30) by nutshell.tislabs.com via csmap (V6.0) id srcAAAMpaWWH; Mon, 5 Feb 07 23:20:04 -0500 Received: by pecan.tislabs.com (Postfix, from userid 2005) id C3C0D3F48E; Mon, 5 Feb 2007 13:21:19 -0500 (EST) To: sidr@ietf.org Message-Id: <20070205182119.C3C0D3F48E@pecan.tislabs.com> Date: Mon, 5 Feb 2007 13:21:19 -0500 (EST) From: sandy@tislabs.com (Sandy Murphy) X-Spam-Score: 0.2 (/) X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15 Cc: sandy@tislabs.com Subject: [Sidr] upcoming dates for the IETF 68 in Prague X-BeenThere: sidr@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Secure Interdomain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: sidr-bounces@ietf.org Note especially in the following message that if you wish to submit a working group draft (draft-ietf-sidr-...), you need to give the wg chairs advance notice (BEFORE Feb 19!) of the filename so the chairs can give approval to the secretariat. If you want to submit as a personal submission (draft-ietf-me-...), you have until Feb 26. It would be a good idea to bring ideas to the wg chairs, even if they will be a personal submission, so the wg chairs can put them on the agenda. --Sandy >From ietf-announce-bounces@ietf.org Fri Feb 2 00:25:15 2007 To: ietf-announce@ietf.org Cc: From: ietf-secretariat@ietf.org Date: Fri, 02 Feb 2007 00:00:01 -0500 Subject: Internet-Drafts Submission Cutoff Dates for the 68th IETF Meeting in Prague, Czech Republic There are two (2) Internet-Draft cutoff dates for the 68th IETF Meeting in Prague, Czech Republic: February 26th: Cutoff Date for Initial (i.e., version -00) Internet-Draft Submissions All initial Internet-Drafts (version -00) must be submitted by Monday, February 26th at 9:00 AM ET. As always, all initial submissions with a filename beginning with "draft-ietf" must be approved by the appropriate WG Chair before they can be processed or announced. The Secretariat would appreciate receiving WG Chair approval by Monday, February 19th at 9:00 AM ET. March 5th: Cutoff Date for Revised (i.e., version -01 and higher) Internet-Draft Submissions All revised Internet-Drafts (version -01 and higher) must be submitted by Monday, March 5th at 9:00 AM ET. Initial and revised Internet-Drafts received after their respective cutoff dates will not be made available in the Internet-Drafts directory or announced until on or after Monday, March 19th at 9:00 AM ET, when Internet-Draft posting resumes. Please do not wait until the last minute to submit. Thank you for your understanding and cooperation. If you have any questions or concerns, then please send a message to internet-drafts@ietf.org. The IETF Secretariat FYI: The Internet-Draft cutoff dates as well as other significant dates for the 68th IETF Meeting can be found at http://www.ietf.org/meetings/cutoff_dates_68.html. _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce _______________________________________________ Sidr mailing list Sidr@ietf.org https://www1.ietf.org/mailman/listinfo/sidr From sidr-bounces@ietf.org Tue Feb 06 18:33:32 2007 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HEZnz-0004eZ-Ky; Tue, 06 Feb 2007 18:32:55 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HEZny-0004eT-SJ for sidr@ietf.org; Tue, 06 Feb 2007 18:32:54 -0500 Received: from sentry.gw.tislabs.com ([192.94.214.100] helo=nutshell.tislabs.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HEZnq-0005q0-Hz for sidr@ietf.org; Tue, 06 Feb 2007 18:32:54 -0500 Received: (from uucp@localhost) by nutshell.tislabs.com (8.12.9/8.12.9) id l16NUoXG028640 for ; Tue, 6 Feb 2007 18:30:50 -0500 (EST) Received: from pecan.tislabs.com(10.66.1.30) by nutshell.tislabs.com via csmap (V6.0) id srcAAAoiaaX3; Tue, 6 Feb 07 18:30:07 -0500 Received: by pecan.tislabs.com (Postfix, from userid 2005) id E24933F4D0; Tue, 6 Feb 2007 18:03:23 -0500 (EST) To: sandy@tislabs.com, sidr@ietf.org Subject: Re: [Sidr] upcoming dates for the IETF 68 in Prague In-Reply-To: <20070205182119.C3C0D3F48E@pecan.tislabs.com> Message-Id: <20070206230323.E24933F4D0@pecan.tislabs.com> Date: Tue, 6 Feb 2007 18:03:23 -0500 (EST) From: sandy@tislabs.com (Sandy Murphy) X-Spam-Score: 0.0 (/) X-Scan-Signature: 6d62ab47271805379d7172ee693a45db Cc: X-BeenThere: sidr@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Secure Interdomain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: sidr-bounces@ietf.org >If you want to submit as a personal submission (draft-ietf-me-...), Nit: error in example: personal submissions are titled draft-me-... --Sandy _______________________________________________ Sidr mailing list Sidr@ietf.org https://www1.ietf.org/mailman/listinfo/sidr From sidr-bounces@ietf.org Tue Feb 13 15:50:58 2007 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HH4bj-0008OS-7S; Tue, 13 Feb 2007 15:50:35 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HH4bE-00080O-Qp; Tue, 13 Feb 2007 15:50:04 -0500 Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HH4bD-0007J2-PU; Tue, 13 Feb 2007 15:50:04 -0500 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id 5061526EFB; Tue, 13 Feb 2007 20:50:03 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1HH4bC-0002xq-V1; Tue, 13 Feb 2007 15:50:02 -0500 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: Date: Tue, 13 Feb 2007 15:50:02 -0500 X-Spam-Score: -2.5 (--) X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b Cc: sidr@ietf.org Subject: [Sidr] I-D ACTION:draft-ietf-sidr-res-certs-03.txt X-BeenThere: sidr@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Secure Interdomain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: sidr-bounces@ietf.org --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Secure Inter-Domain Routing Working Group of the IETF. Title : A Profile for X.509 PKIX Resource Certificates Author(s) : G. Huston, et al. Filename : draft-ietf-sidr-res-certs-03.txt Pages : 29 Date : 2007-2-13 This document defines a standard profile for X.509 certificates for the purposes of supporting validation of assertions of "right-to-use" of an Internet Number Resource (IP Addresses and Autonomous System Numbers). This profile is used to convey the issuer's authorization of the subject to be regarded as the current holder of a "right-of- use" of the IP addresses and AS numbers that are described in the associated Resource Certificate. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-sidr-res-certs-03.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-sidr-res-certs-03.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-sidr-res-certs-03.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: <2007-2-13141041.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-sidr-res-certs-03.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-sidr-res-certs-03.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2007-2-13141041.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Sidr mailing list Sidr@ietf.org https://www1.ietf.org/mailman/listinfo/sidr --NextPart-- From sidr-bounces@ietf.org Wed Feb 21 10:51:16 2007 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HJtk9-00083t-Qc; Wed, 21 Feb 2007 10:50:57 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HJtjN-0006Lu-95; Wed, 21 Feb 2007 10:50:09 -0500 Received: from ns0.neustar.com ([156.154.16.158]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HJtjI-0004gk-U1; Wed, 21 Feb 2007 10:50:09 -0500 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns0.neustar.com (Postfix) with ESMTP id 98BE6329E9; Wed, 21 Feb 2007 15:50:02 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1HJtjG-0008Tk-FS; Wed, 21 Feb 2007 10:50:02 -0500 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: Date: Wed, 21 Feb 2007 10:50:02 -0500 X-Spam-Score: -2.5 (--) X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b Cc: sidr@ietf.org Subject: [Sidr] I-D ACTION:draft-ietf-sidr-res-certs-04.txt X-BeenThere: sidr@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Secure Interdomain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: sidr-bounces@ietf.org --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Secure Inter-Domain Routing Working Group of the IETF. Title : A Profile for X.509 PKIX Resource Certificates Author(s) : G. Huston, et al. Filename : draft-ietf-sidr-res-certs-04.txt Pages : 30 Date : 2007-2-21 This document defines a standard profile for X.509 certificates for the purposes of supporting validation of assertions of "right-to-use" of an Internet Number Resource (IP Addresses and Autonomous System Numbers). This profile is used to convey the issuer's authorization of the subject to be regarded as the current holder of a "right-of- use" of the IP addresses and AS numbers that are described in the associated Resource Certificate. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-sidr-res-certs-04.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-sidr-res-certs-04.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-sidr-res-certs-04.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: <2007-2-21090416.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-sidr-res-certs-04.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-sidr-res-certs-04.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2007-2-21090416.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Sidr mailing list Sidr@ietf.org https://www1.ietf.org/mailman/listinfo/sidr --NextPart-- From sidr-bounces@ietf.org Thu Feb 22 18:11:28 2007 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HKN4z-0004eR-SA; Thu, 22 Feb 2007 18:10:25 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HKN4y-0004eK-7O for sidr@ietf.org; Thu, 22 Feb 2007 18:10:24 -0500 Received: from sentry.gw.tislabs.com ([192.94.214.100] helo=nutshell.tislabs.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HKN4x-0004hO-03 for sidr@ietf.org; Thu, 22 Feb 2007 18:10:24 -0500 Received: (from uucp@localhost) by nutshell.tislabs.com (8.12.9/8.12.9) id l1MN8d1r018297 for ; Thu, 22 Feb 2007 18:08:39 -0500 (EST) Received: from pecan.tislabs.com(10.66.1.30) by nutshell.tislabs.com via csmap (V6.0) id srcAAAifaOUJ; Thu, 22 Feb 07 18:08:35 -0500 Received: by pecan.tislabs.com (Postfix, from userid 2005) id 1C11B3F439; Thu, 22 Feb 2007 18:08:01 -0500 (EST) To: sidr@ietf.org Message-Id: <20070222230801.1C11B3F439@pecan.tislabs.com> Date: Thu, 22 Feb 2007 18:08:01 -0500 (EST) From: sandy@tislabs.com (Sandy Murphy) X-Spam-Score: 0.0 (/) X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2 Cc: sandy@tislabs.com Subject: [Sidr] deadline reminders X-BeenThere: sidr@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Secure Interdomain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: sidr-bounces@ietf.org There are two meeting dealines approaching: for draft submission: February 26, Monday - Internet Draft Cut-off for initial document (-00) submission by 09:00 ET (14:00 UTC/GMT) March 5, Monday - Internet Draft final submission cut-off by 09:00 ET (14:00 UTC/GMT) for registration: March 9, Friday - Early-Bird registration and payment cut-off at 12:00 noon ET (17:00 UTC/GMT) March 12, Monday - Registration cancellation cut-off at 17:00 ET (21:00 UTC/GMT) March 17, Saturday - Final Pre-Registration and Pre-Payment cut-off at 17:00 ET (21:00 UTC/GMT) --Sandy _______________________________________________ Sidr mailing list Sidr@ietf.org https://www1.ietf.org/mailman/listinfo/sidr From sidr-bounces@ietf.org Thu Feb 22 18:16:23 2007 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HKNAg-0008Cl-Po; Thu, 22 Feb 2007 18:16:18 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HKNAf-0008C3-Rn for sidr@ietf.org; Thu, 22 Feb 2007 18:16:17 -0500 Received: from ns1.tislabs.com ([192.94.214.100] helo=nutshell.tislabs.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HKNAe-0005SB-Kl for sidr@ietf.org; Thu, 22 Feb 2007 18:16:17 -0500 Received: (from uucp@localhost) by nutshell.tislabs.com (8.12.9/8.12.9) id l1MNEZe4018796 for ; Thu, 22 Feb 2007 18:14:35 -0500 (EST) Received: from pecan.tislabs.com(10.66.1.30) by nutshell.tislabs.com via csmap (V6.0) id srcAAA9ea4SK; Thu, 22 Feb 07 18:14:31 -0500 Received: by pecan.tislabs.com (Postfix, from userid 2005) id 6BB533F439; Thu, 22 Feb 2007 18:13:57 -0500 (EST) To: sidr@ietf.org Message-Id: <20070222231357.6BB533F439@pecan.tislabs.com> Date: Thu, 22 Feb 2007 18:13:57 -0500 (EST) From: sandy@tislabs.com (Sandy Murphy) X-Spam-Score: 0.0 (/) X-Scan-Signature: 7aefe408d50e9c7c47615841cb314bed Cc: sandy@tislabs.com Subject: [Sidr] agenda requests X-BeenThere: sidr@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Secure Interdomain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: sidr-bounces@ietf.org It's about time to ask for topics for the agenda. The deadline for the wg chairs to submit an agenda is March 7 for drafts and March 12 for revisions. So if you wish to speak, it would be great to send a request in to both wg chairs (for fault tolerance) soon. --Sandy _______________________________________________ Sidr mailing list Sidr@ietf.org https://www1.ietf.org/mailman/listinfo/sidr From sidr-bounces@ietf.org Thu Feb 22 18:42:32 2007 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HKNZk-000522-H5; Thu, 22 Feb 2007 18:42:12 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HKNZj-00051w-Gn for sidr@ietf.org; Thu, 22 Feb 2007 18:42:11 -0500 Received: from ns1.tislabs.com ([192.94.214.100] helo=nutshell.tislabs.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HKNZi-0000kE-8k for sidr@ietf.org; Thu, 22 Feb 2007 18:42:11 -0500 Received: (from uucp@localhost) by nutshell.tislabs.com (8.12.9/8.12.9) id l1MNeKp5020697 for ; Thu, 22 Feb 2007 18:40:20 -0500 (EST) Received: from pecan.tislabs.com(10.66.1.30) by nutshell.tislabs.com via csmap (V6.0) id srcAAAGYaWoO; Thu, 22 Feb 07 18:39:21 -0500 Received: by pecan.tislabs.com (Postfix, from userid 2005) id CD9B83F474; Thu, 22 Feb 2007 18:38:46 -0500 (EST) To: sidr@ietf.org Message-Id: <20070222233846.CD9B83F474@pecan.tislabs.com> Date: Thu, 22 Feb 2007 18:38:46 -0500 (EST) From: sandy@tislabs.com (Sandy Murphy) X-Spam-Score: 0.0 (/) X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906 Cc: sandy@tislabs.com Subject: [Sidr] exact match for ROA vs more specifics X-BeenThere: sidr@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Secure Interdomain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: sidr-bounces@ietf.org If you look at the minutes of the November meeting: http://www3.ietf.org/proceedings/06nov/minutes/sidr.html you will see that there was a discussion in the later part of the meeting about the ROA. The discussion started out to be whether the resource certificate prefix should exactly match the prefix in the ROA. It segued to a discussion of whether the ROA "allows more specifics or not" (ed: in route advertisements). There were speakers on either side (exact match vs more specifics) and no consensus was reached. This was to be taken to the list. Those who were speaking at the mike are hearby urged to speak more about the topic on the list. An example to highlight the issue: if you hold a delegation of a /18, and you anticipate the possibility of advertising longer prefixes, can you create the ROA for the /18 and it will authorize any advertisement of a longer prefix, or must you create a new ROA for each longer prefix you decide to advertise? --Sandy _______________________________________________ Sidr mailing list Sidr@ietf.org https://www1.ietf.org/mailman/listinfo/sidr From sidr-bounces@ietf.org Fri Feb 23 10:27:21 2007 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HKcJX-0001W6-Gc; Fri, 23 Feb 2007 10:26:27 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HKcIq-0000yw-8j for sidr@ietf.org; Fri, 23 Feb 2007 10:25:44 -0500 Received: from rwcrmhc13.comcast.net ([204.127.192.83]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HKcG9-0005wk-4e for sidr@ietf.org; Fri, 23 Feb 2007 10:22:58 -0500 Received: from [192.122.181.97] (dhcp-192-122-181-97.merit.edu[192.122.181.97]) by comcast.net (rwcrmhc13) with ESMTP id <20070223152256m13005ol6le>; Fri, 23 Feb 2007 15:22:56 +0000 Message-ID: <45DF06D7.4030808@merit.edu> Date: Fri, 23 Feb 2007 10:23:03 -0500 From: Larry Blunk User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: Sandy Murphy Subject: Re: [Sidr] exact match for ROA vs more specifics References: <20070222233846.CD9B83F474@pecan.tislabs.com> In-Reply-To: <20070222233846.CD9B83F474@pecan.tislabs.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17 Cc: sidr@ietf.org X-BeenThere: sidr@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Secure Interdomain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: sidr-bounces@ietf.org Would it be possible to make more specifics an option in the ROA? It might also be nice to be able specify a maximum prefix length. -Larry Sandy Murphy wrote: > If you look at the minutes of the November meeting: > > http://www3.ietf.org/proceedings/06nov/minutes/sidr.html > > you will see that there was a discussion in the later part of the meeting > about the ROA. The discussion started out to be whether the resource > certificate prefix should exactly match the prefix in the ROA. It segued > to a discussion of whether the ROA "allows more specifics or not" (ed: in > route advertisements). > > There were speakers on either side (exact match vs more specifics) and > no consensus was reached. This was to be taken to the list. > > Those who were speaking at the mike are hearby urged to speak more > about the topic on the list. > > An example to highlight the issue: if you hold a delegation of a /18, > and you anticipate the possibility of advertising longer prefixes, > can you create the ROA for the /18 and it will authorize any advertisement > of a longer prefix, or must you create a new ROA for each longer prefix you > decide to advertise? > > --Sandy > > _______________________________________________ > _______________________________________________ Sidr mailing list Sidr@ietf.org https://www1.ietf.org/mailman/listinfo/sidr From sidr-bounces@ietf.org Fri Feb 23 15:30:54 2007 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HKh41-0001ft-SM; Fri, 23 Feb 2007 15:30:45 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HKh40-0001f5-LB for sidr@ietf.org; Fri, 23 Feb 2007 15:30:44 -0500 Received: from mx11.bbn.com ([128.33.0.80]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HKh3y-0003sG-Fy for sidr@ietf.org; Fri, 23 Feb 2007 15:30:44 -0500 Received: from dhcp89-089-106.bbn.com ([128.89.89.106]) by mx11.bbn.com with esmtp (Exim 4.60) (envelope-from ) id 1HKh3v-0003G5-68; Fri, 23 Feb 2007 15:30:40 -0500 Mime-Version: 1.0 Message-Id: Date: Fri, 23 Feb 2007 15:30:38 -0500 To: sandy@tislabs.com From: Stephen Kent Subject: Re: [Sidr] exact match for ROA vs more specifics Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Spam-Score: 0.0 (/) X-Scan-Signature: 7aefe408d50e9c7c47615841cb314bed Cc: sidr@ietf.org X-BeenThere: sidr@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Secure Interdomain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: sidr-bounces@ietf.org I'm in favor of an exact match requirement when talking about ROAs and route advertisements. This helps ensure that matching the ROA against a prefix is intentional, not an accident. An address space holder can always generate additional ROAs with exactly the right prefixes to match the intent of the authorization. Steve _______________________________________________ Sidr mailing list Sidr@ietf.org https://www1.ietf.org/mailman/listinfo/sidr From sidr-bounces@ietf.org Sat Feb 24 19:07:30 2007 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HL6u7-00043K-U8; Sat, 24 Feb 2007 19:06:15 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HL6u6-00040U-Mp for sidr@ietf.org; Sat, 24 Feb 2007 19:06:14 -0500 Received: from geoff.telstra.net ([203.50.0.18]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HL6u5-0004ne-0r for sidr@ietf.org; Sat, 24 Feb 2007 19:06:14 -0500 Received: from vaioz1.apnic.net (dhcp19.potaroo.net [203.10.60.19]) by geoff.telstra.net (8.13.6/8.13.6) with ESMTP id l1P05TKL006351; Sun, 25 Feb 2007 11:05:30 +1100 (EST) (envelope-from gih@apnic.net) Message-Id: <7.0.0.16.2.20070225110207.04275578@apnic.net> X-Mailer: QUALCOMM Windows Eudora Version 7.0.0.16 Date: Sun, 25 Feb 2007 11:05:33 +1100 To: Stephen Kent , sandy@tislabs.com From: Geoff Huston Subject: Re: [Sidr] exact match for ROA vs more specifics In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Spam-Score: 0.1 (/) X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a Cc: sidr@ietf.org X-BeenThere: sidr@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Secure Interdomain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: sidr-bounces@ietf.org I'm against this exact match requirement - I think its a case of semantic overload in mixing basic authorities (permission to originate) with routing policy (explicit nomination of what prefixes to route). However if we have a "don't care" bit in the ROA to allow a prefix controller to allow the AS to originate the route any way they want then I'd be happy. Geoff At 07:30 AM 24/02/2007, Stephen Kent wrote: >I'm in favor of an exact match requirement when talking about ROAs >and route advertisements. This helps ensure that matching the ROA >against a prefix is intentional, not an accident. An address space >holder can always generate additional ROAs with exactly the right >prefixes to match the intent of the authorization. > >Steve > >_______________________________________________ >Sidr mailing list >Sidr@ietf.org >https://www1.ietf.org/mailman/listinfo/sidr _______________________________________________ Sidr mailing list Sidr@ietf.org https://www1.ietf.org/mailman/listinfo/sidr From sidr-bounces@ietf.org Mon Feb 26 17:18:37 2007 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HLmr8-0003Z3-My; Mon, 26 Feb 2007 15:53:59 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HLmnp-0004GR-K5; Mon, 26 Feb 2007 15:50:33 -0500 Received: from ns4.neustar.com ([156.154.24.139]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1HLmno-0007dO-VI; Mon, 26 Feb 2007 15:50:33 -0500 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns4.neustar.com (Postfix) with ESMTP id CAFC52ACD2; Mon, 26 Feb 2007 20:50:02 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1HLmnK-0004yo-IZ; Mon, 26 Feb 2007 15:50:02 -0500 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: Date: Mon, 26 Feb 2007 15:50:02 -0500 X-Spam-Score: -2.5 (--) X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b Cc: sidr@ietf.org Subject: [Sidr] I-D ACTION:draft-ietf-sidr-res-certs-05.txt X-BeenThere: sidr@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Secure Interdomain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: sidr-bounces@ietf.org --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Secure Inter-Domain Routing Working Group of the IETF. Title : A Profile for X.509 PKIX Resource Certificates Author(s) : G. Huston, et al. Filename : draft-ietf-sidr-res-certs-05.txt Pages : 30 Date : 2007-2-26 This document defines a standard profile for X.509 certificates for the purposes of supporting validation of assertions of "right-to-use" of an Internet Number Resource (IP Addresses and Autonomous System Numbers). This profile is used to convey the issuer's authorization of the subject to be regarded as the current holder of a "right-of- use" of the IP addresses and AS numbers that are described in the associated Resource Certificate. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-sidr-res-certs-05.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-sidr-res-certs-05.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-sidr-res-certs-05.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: <2007-2-26112508.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-sidr-res-certs-05.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-sidr-res-certs-05.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2007-2-26112508.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Sidr mailing list Sidr@ietf.org https://www1.ietf.org/mailman/listinfo/sidr --NextPart-- From sidr-bounces@ietf.org Tue Feb 27 15:52:08 2007 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HM9ID-0002PJ-P4; Tue, 27 Feb 2007 15:51:25 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HM9HO-00012h-UF; Tue, 27 Feb 2007 15:50:34 -0500 Received: from ns3.neustar.com ([156.154.24.138]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1HM9HM-0000SS-IG; Tue, 27 Feb 2007 15:50:34 -0500 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns3.neustar.com (Postfix) with ESMTP id 7C34617658; Tue, 27 Feb 2007 20:50:02 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1HM9Gs-0001dH-7j; Tue, 27 Feb 2007 15:50:02 -0500 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: Date: Tue, 27 Feb 2007 15:50:02 -0500 X-Spam-Score: -2.5 (--) X-Scan-Signature: f66b12316365a3fe519e75911daf28a8 Cc: sidr@ietf.org Subject: [Sidr] I-D ACTION:draft-ietf-sidr-cp-01.txt X-BeenThere: sidr@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Secure Interdomain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: sidr-bounces@ietf.org --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Secure Inter-Domain Routing Working Group of the IETF. Title : Certificate Policy (CP) for the Internet IP Address and AS Number (PKI) Author(s) : K. Seo, et al. Filename : draft-ietf-sidr-cp-01.txt Pages : 47 Date : 2007-2-27 This document describes the certificate policy for a PKI used to support improved routing security. Each organization that allocates IP addresses or Autonomous System (AS) numbers to an organization will, in parallel, issue a certificate reflecting this allocation. These certificates will enable verification that the holder of the associated private key has been allocated the resources indicated in the certificate, and is the current, unique holder of these resources. The PKI in which the certificates issued under this policy are employed, in conjunction with ancillary digitally signed data structures, will provide critical inputs for routing security mechanisms, e.g., generation of route filters by ISPs. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-sidr-cp-01.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-sidr-cp-01.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-sidr-cp-01.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: <2007-2-27102916.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-sidr-cp-01.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-sidr-cp-01.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2007-2-27102916.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Sidr mailing list Sidr@ietf.org https://www1.ietf.org/mailman/listinfo/sidr --NextPart-- From sidr-bounces@ietf.org Tue Feb 27 15:52:13 2007 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HM9IN-0002dd-4v; Tue, 27 Feb 2007 15:51:35 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HM9HP-000136-1Z; Tue, 27 Feb 2007 15:50:35 -0500 Received: from ns3.neustar.com ([156.154.24.138]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1HM9HM-0000ST-K9; Tue, 27 Feb 2007 15:50:34 -0500 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns3.neustar.com (Postfix) with ESMTP id 89F6B17660; Tue, 27 Feb 2007 20:50:02 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1HM9Gs-0001dM-8R; Tue, 27 Feb 2007 15:50:02 -0500 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: Date: Tue, 27 Feb 2007 15:50:02 -0500 X-Spam-Score: -2.5 (--) X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b Cc: sidr@ietf.org Subject: [Sidr] I-D ACTION:draft-ietf-sidr-cps-isp-00.txt X-BeenThere: sidr@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Secure Interdomain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: sidr-bounces@ietf.org --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Secure Inter-Domain Routing Working Group of the IETF. Title : Template for an Internet Service Provider's Certification Practice Statement (CPS) for the Internet IP address and AS Number PKI Author(s) : D. Kong, et al. Filename : draft-ietf-sidr-cps-isp-00.txt Pages : 48 Date : 2006-2-27 This document contains a template to be used for creating a Certification Practice Statement (CPS) for a Local Internet Registry (LIR) or Internet Service Provider (ISP) that is part of the Internet IP Address and Autonomous System (AS) Number Public Key Infrastructure (PKI). A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-sidr-cps-isp-00.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-sidr-cps-isp-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-ietf-sidr-cps-isp-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: <2007-2-27103721.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-sidr-cps-isp-00.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-sidr-cps-isp-00.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2007-2-27103721.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Sidr mailing list Sidr@ietf.org https://www1.ietf.org/mailman/listinfo/sidr --NextPart-- From sidr-bounces@ietf.org Wed Feb 28 12:46:39 2007 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HMSsB-0002sh-1W; Wed, 28 Feb 2007 12:45:51 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HMSs9-0002qs-W0 for sidr@ietf.org; Wed, 28 Feb 2007 12:45:49 -0500 Received: from sj-iport-2-in.cisco.com ([171.71.176.71] helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HMSs7-0006Ul-GT for sidr@ietf.org; Wed, 28 Feb 2007 12:45:49 -0500 Received: from rtp-dkim-1.cisco.com ([64.102.121.158]) by sj-iport-2.cisco.com with ESMTP; 28 Feb 2007 09:45:46 -0800 X-IronPort-AV: i="4.14,231,1170662400"; d="scan'208"; a="363377338:sNHT43617484" Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13]) by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l1SHjkg7011739; Wed, 28 Feb 2007 12:45:46 -0500 Received: from [216.230.34.101] (rtp-vpn3-546.cisco.com [10.82.218.37]) by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l1SHjZOA015711; Wed, 28 Feb 2007 12:45:37 -0500 (EST) Message-ID: <45E5BFBF.7060707@cisco.com> Date: Wed, 28 Feb 2007 12:45:35 -0500 From: Russ White User-Agent: Thunderbird 1.5.0.9 (Macintosh/20061207) MIME-Version: 1.0 To: Geoff Huston Subject: Re: [Sidr] exact match for ROA vs more specifics References: <7.0.0.16.2.20070225110207.04275578@apnic.net> In-Reply-To: <7.0.0.16.2.20070225110207.04275578@apnic.net> X-Enigmail-Version: 0.94.1.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=708; t=1172684746; x=1173548746; c=relaxed/simple; s=rtpdkim1001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=riw@cisco.com; z=From:=20Russ=20White=20 |Subject:=20Re=3A=20[Sidr]=20exact=20match=20for=20ROA=20vs=20more=20spec ifics |Sender:=20 |To:=20Geoff=20Huston=20; bh=2PTRhkHWMo1tpmsCKxx6kUYhTJUVAX99R8a8n/Sj+VE=; b=bMCOdvvNWoa0nn9tz9QUsOWm2M7UO3/2Hvv0ciMILfhPj1iwSlRSb5t7ZpPL+dL8TwPHxRkP lvd2g1zN9xHUUHgG6iciKIGjkh3OiKS3dqd+izKeGjc3YN91vedkhq6c; Authentication-Results: rtp-dkim-1; header.From=riw@cisco.com; dkim=pass (si g from cisco.com/rtpdkim1001 verified; ); X-Spam-Score: 0.0 (/) X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a Cc: sidr@ietf.org, sandy@tislabs.com X-BeenThere: sidr@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Secure Interdomain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: sidr-bounces@ietf.org -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Geoff Huston wrote: > I'm against this exact match requirement - I think its a case of > semantic overload in mixing basic authorities (permission to originate) > with routing policy (explicit nomination of what prefixes to route). Agreed.... I could see someone wanting to say: "nothing longer than /x will be advertised in this space," but I don't see any reason to make this an exact match only. :-) Russ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFF5b+/ER27sUhU9OQRAkI2AKC4VTiz0fhnYhSb4hXg0a4jJMpEZQCeLikc W1WH9UiIMgr6JG9g6wxUsUM= =Og24 -----END PGP SIGNATURE----- _______________________________________________ Sidr mailing list Sidr@ietf.org https://www1.ietf.org/mailman/listinfo/sidr From sidr-bounces@ietf.org Wed Feb 28 13:11:55 2007 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HMTHE-00079u-JJ; Wed, 28 Feb 2007 13:11:44 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HMTHD-00079k-JG for sidr@ietf.org; Wed, 28 Feb 2007 13:11:43 -0500 Received: from [69.37.59.173] (helo=workhorse.brookfield.occnc.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HMTHC-0000zI-7R for sidr@ietf.org; Wed, 28 Feb 2007 13:11:43 -0500 Received: from workhorse.brookfield.occnc.com (localhost [127.0.0.1]) by workhorse.brookfield.occnc.com (8.13.6/8.13.4) with ESMTP id l1SI6twF081144; Wed, 28 Feb 2007 13:06:55 -0500 (EST) (envelope-from curtis@occnc.com) X-DKIM: Sendmail DKIM Filter v0.5.2 workhorse.brookfield.occnc.com l1SI6twF081144 DKIM-Signature: a=rsa-sha1; c=relaxed/simple; d=occnc.com; s=workhorse; t=1172686015; bh=Uv2bsJWdq4Q1kLIkzk2HFJIBEII=; h=To:cc:Reply-To: From:Subject:In-reply-to:Date; b=l7PVYscUZeLbe/XmwZGE36KBDdL8jdtaqG BosYM1lG1isjNi64UDlvMiRN3wy1bUf7nENvy6cH+RhzxH3n/0cQ== Message-Id: <200702281806.l1SI6twF081144@workhorse.brookfield.occnc.com> To: Russ White From: Curtis Villamizar Subject: Re: [Sidr] exact match for ROA vs more specifics In-reply-to: Your message of "Wed, 28 Feb 2007 12:45:35 EST." <45E5BFBF.7060707@cisco.com> Date: Wed, 28 Feb 2007 13:06:55 -0500 X-Spam-Score: 0.1 (/) X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1 Cc: sandy@tislabs.com, sidr@ietf.org X-BeenThere: sidr@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: curtis@occnc.com List-Id: Secure Interdomain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: sidr-bounces@ietf.org In message <45E5BFBF.7060707@cisco.com> Russ White writes: > > Geoff Huston wrote: > > I'm against this exact match requirement - I think its a case of > > semantic overload in mixing basic authorities (permission to originate) > > with routing policy (explicit nomination of what prefixes to route). > > Agreed.... > > I could see someone wanting to say: "nothing longer than /x will be > advertised in this space," but I don't see any reason to make this an > exact match only. > > :-) > > Russ Seems like an argument for the following expressiveness: prefix/len1[-len2] Geoff would have to use prefix/len1-24 (or 28?, or ??) for most prefixes, assuming that most prefixes would want some limit. If not, using prefix/len1-32 notation could be used to do what Jeff wants. Or some tool could display this as prefix/len1* to indicate any more specific being allowed. In this notation prefix/len would imply exact match. Obviously there is no need to store information in ascii string format. We want this expressiveness and maybe for display a common notation would be helpful but not manditory. It might be used in an implimentation's XML representation or it might not be (an alternative would be explicit prefix and len tags). Curtis _______________________________________________ Sidr mailing list Sidr@ietf.org https://www1.ietf.org/mailman/listinfo/sidr From sidr-bounces@ietf.org Wed Feb 28 13:30:46 2007 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HMTYT-0006w2-Qw; Wed, 28 Feb 2007 13:29:33 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HMTYR-0006vf-Mo for sidr@ietf.org; Wed, 28 Feb 2007 13:29:31 -0500 Received: from fiji.merit.edu ([198.108.1.12]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HMTYO-0003Ds-EU for sidr@ietf.org; Wed, 28 Feb 2007 13:29:31 -0500 Received: from localhost (localhost [127.0.0.1]) by fiji.merit.edu (Postfix) with ESMTP id 1BB2A17D1; Wed, 28 Feb 2007 13:29:21 -0500 (EST) X-Virus-Scanned: amavisd-new at merit.edu Received: from fiji.merit.edu ([127.0.0.1]) by localhost (fiji.merit.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eBIQKonuUZpX; Wed, 28 Feb 2007 13:29:20 -0500 (EST) Received: from [198.108.62.151] (ablate.merit.edu [198.108.62.151]) by fiji.merit.edu (Postfix) with ESMTP id B80F7B02; Wed, 28 Feb 2007 13:29:20 -0500 (EST) Message-ID: <45E5CA07.6050203@merit.edu> Date: Wed, 28 Feb 2007 13:29:27 -0500 From: "Larry J. Blunk" User-Agent: Thunderbird 1.5.0.9 (X11/20061206) MIME-Version: 1.0 To: curtis@occnc.com Subject: Re: [Sidr] exact match for ROA vs more specifics References: <200702281806.l1SI6twF081144@workhorse.brookfield.occnc.com> In-Reply-To: <200702281806.l1SI6twF081144@workhorse.brookfield.occnc.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: fb6060cb60c0cea16e3f7219e40a0a81 Cc: sidr@ietf.org, sandy@tislabs.com X-BeenThere: sidr@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Secure Interdomain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: sidr-bounces@ietf.org Curtis Villamizar wrote: > In message <45E5BFBF.7060707@cisco.com> > Russ White writes: > >> >> Geoff Huston wrote: >> >>> I'm against this exact match requirement - I think its a case of >>> semantic overload in mixing basic authorities (permission to originate) >>> with routing policy (explicit nomination of what prefixes to route). >>> >> >> Agreed.... >> >> I could see someone wanting to say: "nothing longer than /x will be >> advertised in this space," but I don't see any reason to make this an >> exact match only. >> >> :-) >> >> Russ >> > > > Seems like an argument for the following expressiveness: > > prefix/len1[-len2] > > Geoff would have to use prefix/len1-24 (or 28?, or ??) for most > prefixes, assuming that most prefixes would want some limit. If not, > using prefix/len1-32 notation could be used to do what Jeff wants. Or > some tool could display this as prefix/len1* to indicate any more > specific being allowed. In this notation prefix/len would imply exact > match. > > Obviously there is no need to store information in ascii string > format. We want this expressiveness and maybe for display a common > notation would be helpful but not manditory. It might be used in an > implimentation's XML representation or it might not be (an alternative > would be explicit prefix and len tags). > > Curtis > > Curtis, sounds like an application for the RPSL range operators -- An address prefix range is an address prefix followed by an optional range operator. The range operators are: ^- is the exclusive more specifics operator; it stands for the more specifics of the address prefix excluding the address prefix itself. For example, 128.9.0.0/16^- contains all the more specifics of 128.9.0.0/16 excluding 128.9.0.0/16. ^+ is the inclusive more specifics operator; it stands for the more specifics of the address prefix including the address prefix itself. For example, 5.0.0.0/8^+ contains all the more specifics of 5.0.0.0/8 including 5.0.0.0/8. ^n where n is an integer, stands for all the length n specifics of the address prefix. For example, 30.0.0.0/8^16 contains all the more specifics of 30.0.0.0/8 which are of length 16 such as 30.9.0.0/16. ^n-m where n and m are integers, stands for all the length n to length m specifics of the address prefix. For example, 30.0.0.0/8^24-32 contains all the more specifics of 30.0.0.0/8 which are of length 24 to 32 such as 30.9.9.96/28. -Larry _______________________________________________ Sidr mailing list Sidr@ietf.org https://www1.ietf.org/mailman/listinfo/sidr From sidr-bounces@ietf.org Wed Feb 28 14:04:54 2007 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HMU6F-0000XD-K3; Wed, 28 Feb 2007 14:04:27 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HMU6E-0000X3-CF for sidr@ietf.org; Wed, 28 Feb 2007 14:04:26 -0500 Received: from [69.37.59.173] (helo=workhorse.brookfield.occnc.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HMU6D-0000gc-22 for sidr@ietf.org; Wed, 28 Feb 2007 14:04:26 -0500 Received: from workhorse.brookfield.occnc.com (localhost [127.0.0.1]) by workhorse.brookfield.occnc.com (8.13.6/8.13.4) with ESMTP id l1SIxU21081676; Wed, 28 Feb 2007 13:59:30 -0500 (EST) (envelope-from curtis@occnc.com) X-DKIM: Sendmail DKIM Filter v0.5.2 workhorse.brookfield.occnc.com l1SIxU21081676 DKIM-Signature: a=rsa-sha1; c=relaxed/simple; d=occnc.com; s=workhorse; t=1172689171; bh=O2EvqCklxH/ymV86G+lnESW0/ks=; h=To:cc:Reply-To: From:Subject:In-reply-to:Date; b=onPzyCfId2sWNk6fu+bvFvGzoyq2eJ3qfY F1kgkxVlO7EV8lNEsvF3lXpKQh4NoV5jI/vK3H5KTm7rspmC7XHg== Message-Id: <200702281859.l1SIxU21081676@workhorse.brookfield.occnc.com> To: "Larry J. Blunk" From: Curtis Villamizar Subject: Re: [Sidr] exact match for ROA vs more specifics In-reply-to: Your message of "Wed, 28 Feb 2007 13:29:27 EST." <45E5CA07.6050203@merit.edu> Date: Wed, 28 Feb 2007 13:59:30 -0500 X-Spam-Score: 0.1 (/) X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014 Cc: sandy@tislabs.com, sidr@ietf.org X-BeenThere: sidr@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: curtis@occnc.com List-Id: Secure Interdomain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: sidr-bounces@ietf.org In message <45E5CA07.6050203@merit.edu> "Larry J. Blunk" writes: Curtis, sounds like an application for the RPSL range operators -- Agreed. Curtis _______________________________________________ Sidr mailing list Sidr@ietf.org https://www1.ietf.org/mailman/listinfo/sidr From sidr-bounces@ietf.org Wed Feb 28 18:51:19 2007 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HMYYl-00017F-9n; Wed, 28 Feb 2007 18:50:11 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HMYYd-00014V-Ii; Wed, 28 Feb 2007 18:50:03 -0500 Received: from ns0.neustar.com ([156.154.16.158]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HMYYd-0002iI-4V; Wed, 28 Feb 2007 18:50:03 -0500 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns0.neustar.com (Postfix) with ESMTP id CAA4632938; Wed, 28 Feb 2007 23:50:02 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1HMYYc-000444-Kh; Wed, 28 Feb 2007 18:50:02 -0500 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: Date: Wed, 28 Feb 2007 18:50:02 -0500 X-Spam-Score: -2.5 (--) X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b Cc: sidr@ietf.org Subject: [Sidr] I-D ACTION:draft-ietf-sidr-roa-format-00.txt X-BeenThere: sidr@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Secure Interdomain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: sidr-bounces@ietf.org --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Secure Inter-Domain Routing Working Group of the IETF. Title : A Profile for Route Origin Authorizations (ROA) Author(s) : S. Kent, D. Kong Filename : draft-ietf-sidr-roa-format-00.txt Pages : 10 Date : 2007-2-28 This document defines a standard profile for Route Origin Authorizations (ROAs). A ROA is a digitally signed object that provides a means of verifying that an IP address block holder has authorized an Autonomous System (AS) to originate routes to that address block. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-sidr-roa-format-00.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-sidr-roa-format-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-ietf-sidr-roa-format-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: <2007-2-28154144.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-sidr-roa-format-00.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-sidr-roa-format-00.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2007-2-28154144.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Sidr mailing list Sidr@ietf.org https://www1.ietf.org/mailman/listinfo/sidr --NextPart-- From sidr-bounces@ietf.org Wed Feb 28 18:51:25 2007 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HMYZx-0002Th-RW; Wed, 28 Feb 2007 18:51:25 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HMYZ9-0001I4-Q5; Wed, 28 Feb 2007 18:50:35 -0500 Received: from ns3.neustar.com ([156.154.24.138]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1HMYZ6-00088q-Vb; Wed, 28 Feb 2007 18:50:35 -0500 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns3.neustar.com (Postfix) with ESMTP id E161917641; Wed, 28 Feb 2007 23:50:02 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1HMYYc-000447-LR; Wed, 28 Feb 2007 18:50:02 -0500 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: Date: Wed, 28 Feb 2007 18:50:02 -0500 X-Spam-Score: -2.5 (--) X-Scan-Signature: 386e0819b1192672467565a524848168 Cc: sidr@ietf.org Subject: [Sidr] I-D ACTION:draft-ietf-sidr-arch-00.txt X-BeenThere: sidr@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Secure Interdomain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: sidr-bounces@ietf.org --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Secure Inter-Domain Routing Working Group of the IETF. Title : An Infrastructure to Support Secure Internet Routing Author(s) : R. Barnes, S. Kent Filename : draft-ietf-sidr-arch-00.txt Pages : 16 Date : 2007-2-28 This document describes an architecture for an infrastructure to support secure Internet routing. The foundation of this architecture is a public key infrastructure (PKI) that represents the allocation hierarchy of IP address space and Autonomous System Numbers; certificates from this PKI are used to verify signed objects that authorize autonomous systems to originate routes for specified IP address prefixes. The data objects that comprise the PKI, as well as other signed objects necessary for secure routing, are stored and disseminated through a distributed repository system. This document also describes at a high level how this architecture can be used to add security features to common operations such as IP address space allocation and route filter construction. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-sidr-arch-00.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-sidr-arch-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-ietf-sidr-arch-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: <2007-2-28155045.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-sidr-arch-00.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-sidr-arch-00.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2007-2-28155045.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Sidr mailing list Sidr@ietf.org https://www1.ietf.org/mailman/listinfo/sidr --NextPart--