From sidr-bounces@ietf.org Mon Jun 16 13:45:20 2008 Return-Path: X-Original-To: sidr-archive@megatron.ietf.org Delivered-To: ietfarch-sidr-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 033F528C142; Mon, 16 Jun 2008 13:45:19 -0700 (PDT) X-Original-To: sidr@ietf.org Delivered-To: sidr@core3.amsl.com Received: by core3.amsl.com (Postfix, from userid 0) id C083428C154; Mon, 16 Jun 2008 13:45:01 -0700 (PDT) From: Internet-Drafts@ietf.org To: i-d-announce@ietf.org Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 Message-Id: <20080616204501.C083428C154@core3.amsl.com> Date: Mon, 16 Jun 2008 13:45:01 -0700 (PDT) Cc: sidr@ietf.org Subject: [Sidr] I-D Action:draft-ietf-sidr-res-certs-10.txt X-BeenThere: sidr@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Secure Interdomain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: sidr-bounces@ietf.org 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-10.txt Pages : 31 Date : 2008-06-16 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 issued certificate. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-sidr-res-certs-10.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ 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: Message/External-body; name="draft-ietf-sidr-res-certs-10.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2008-06-16133044.I-D@ietf.org> --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://www.ietf.org/mailman/listinfo/sidr --NextPart-- From sidr-bounces@ietf.org Mon Jun 16 14:25:19 2008 Return-Path: X-Original-To: sidr-archive@megatron.ietf.org Delivered-To: ietfarch-sidr-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 363513A6B46; Mon, 16 Jun 2008 14:25:19 -0700 (PDT) X-Original-To: sidr@core3.amsl.com Delivered-To: sidr@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0DC2D3A6B46 for ; Mon, 16 Jun 2008 14:25:19 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.298 X-Spam-Level: X-Spam-Status: No, score=-6.298 tagged_above=-999 required=5 tests=[AWL=0.301, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9pzrVrTZmIxw for ; Mon, 16 Jun 2008 14:25:18 -0700 (PDT) Received: from nutshell.tislabs.com (ns1.tislabs.com [192.94.214.100]) by core3.amsl.com (Postfix) with ESMTP id D8F303A67B1 for ; Mon, 16 Jun 2008 14:25:17 -0700 (PDT) Received: (from uucp@localhost) by nutshell.tislabs.com (8.12.9/8.12.9) id m5GLMcTN020144 for ; Mon, 16 Jun 2008 17:22:38 -0400 (EDT) Received: from nodnsquery(10.66.1.30) by nutshell.tislabs.com via csmap (V6.0) id srcAAAOna4vN; Mon, 16 Jun 08 17:22:38 -0400 Received: by pecan.tislabs.com (Postfix, from userid 2005) id 203FF3F477; Mon, 16 Jun 2008 17:25:22 -0400 (EDT) To: sidr@ietf.org Message-Id: <20080616212522.203FF3F477@pecan.tislabs.com> Date: Mon, 16 Jun 2008 17:25:22 -0400 (EDT) From: sandy@tislabs.com (Sandy Murphy) Cc: sandy@tislabs.com Subject: [Sidr] important dates to remember for IETF 72 X-BeenThere: sidr@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Secure Interdomain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sidr-bounces@ietf.org Errors-To: sidr-bounces@ietf.org Just a reminder to everyone of the important dates looming for IETF 72 in Dublin. June 30, Monday - Working Group Chair approval for initial document (Version -00) submissions appreciated by 17:00 PDT (24:00 UTC/GMT) July 7, Monday - Internet Draft Cut-off for initial document (-00) submission by 17:00 PDT (24:00 UTC/GMT) July 14, Monday - Internet Draft final submission cut-off by 17:00 PDT (24:00 UTC/GMT) July 16, Wednesday - Draft Working Group agendas due by 17:00 PDT (24:00 UTC/GMT) Note that this means that if you anticipate producing an initial internet draft (a -00 version), that you should be speaking to your friendly working group chairs real soon now, so that we can approve the submission. --Sandy P.S. And of course there is the deadline for early registration: Early-Bird: $635 USD, if paid in full prior to 17:00 PDT (24:00 UTC/GMT), Friday 18 July, 2008. And the uptick for late registration is: Late: $785 USD if paid after Early-Bird cutoff date and time. so not inconsequential. _______________________________________________ Sidr mailing list Sidr@ietf.org https://www.ietf.org/mailman/listinfo/sidr From sidr-bounces@ietf.org Wed Jun 18 05:30:04 2008 Return-Path: X-Original-To: sidr-archive@megatron.ietf.org Delivered-To: ietfarch-sidr-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7E8AE3A6ADA; Wed, 18 Jun 2008 05:30:04 -0700 (PDT) X-Original-To: sidr@ietf.org Delivered-To: sidr@core3.amsl.com Received: by core3.amsl.com (Postfix, from userid 0) id BD3F83A6A5D; Wed, 18 Jun 2008 05:30:01 -0700 (PDT) From: Internet-Drafts@ietf.org To: i-d-announce@ietf.org Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 Message-Id: <20080618123001.BD3F83A6A5D@core3.amsl.com> Date: Wed, 18 Jun 2008 05:30:01 -0700 (PDT) Cc: sidr@ietf.org Subject: [Sidr] I-D Action:draft-ietf-sidr-rescerts-provisioning-01.txt X-BeenThere: sidr@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Secure Interdomain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: sidr-bounces@ietf.org 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 Protocol for Provisioning Resource Certificates Author(s) : G. Huston, et al. Filename : draft-ietf-sidr-rescerts-provisioning-01.txt Pages : 28 Date : 2008-06-18 This document defines a framework for certificate management interactions between a resource issuer ("Internet Registry" or "IR") and a resource recipient ("Internet Service Provider" or "ISP") through the specification of a protocol for interaction between the two parties. The protocol supports the transmission of requests from the ISP, and corresponding responses from the IR encompassing the actions of certificate issuance, certificate revocation and certificate status information reports. This protocol is intended to be limited to the application of resource certificate management and is not intended to be used as part of a more general certificate management framework. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-sidr-rescerts-provisioning-01.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ 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: Message/External-body; name="draft-ietf-sidr-rescerts-provisioning-01.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2008-06-18051929.I-D@ietf.org> --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://www.ietf.org/mailman/listinfo/sidr --NextPart-- From sidr-bounces@ietf.org Fri Jun 20 09:45:16 2008 Return-Path: X-Original-To: sidr-archive@megatron.ietf.org Delivered-To: ietfarch-sidr-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A61BC3A68F1; Fri, 20 Jun 2008 09:45:15 -0700 (PDT) X-Original-To: sidr@ietf.org Delivered-To: sidr@core3.amsl.com Received: by core3.amsl.com (Postfix, from userid 0) id D7F7E3A685A; Fri, 20 Jun 2008 09:45:04 -0700 (PDT) From: Internet-Drafts@ietf.org To: i-d-announce@ietf.org Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 Message-Id: <20080620164504.D7F7E3A685A@core3.amsl.com> Date: Fri, 20 Jun 2008 09:45:04 -0700 (PDT) Cc: sidr@ietf.org Subject: [Sidr] I-D Action:draft-ietf-sidr-rescerts-provisioning-02.txt X-BeenThere: sidr@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Secure Interdomain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: sidr-bounces@ietf.org 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 Protocol for Provisioning Resource Certificates Author(s) : G. Huston, et al. Filename : draft-ietf-sidr-rescerts-provisioning-02.txt Pages : 29 Date : 2008-06-20 This document defines a framework for certificate management interactions between a resource issuer ("Internet Registry" or "IR") and a resource recipient ("Internet Service Provider" or "ISP") through the specification of a protocol for interaction between the two parties. The protocol supports the transmission of requests from the ISP, and corresponding responses from the IR encompassing the actions of certificate issuance, certificate revocation and certificate status information reports. This protocol is intended to be limited to the application of resource certificate management and is not intended to be used as part of a more general certificate management framework. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-sidr-rescerts-provisioning-02.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ 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: Message/External-body; name="draft-ietf-sidr-rescerts-provisioning-02.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2008-06-20093913.I-D@ietf.org> --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://www.ietf.org/mailman/listinfo/sidr --NextPart-- From sidr-bounces@ietf.org Wed Jun 25 08:33:11 2008 Return-Path: X-Original-To: sidr-archive@megatron.ietf.org Delivered-To: ietfarch-sidr-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 84FB03A6A0B; Wed, 25 Jun 2008 08:33:11 -0700 (PDT) X-Original-To: sidr@core3.amsl.com Delivered-To: sidr@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4888A3A6A55 for ; Wed, 25 Jun 2008 08:33:10 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mqnfc81PNNGc for ; Wed, 25 Jun 2008 08:33:09 -0700 (PDT) Received: from M4.sparta.com (M4.sparta.com [157.185.61.2]) by core3.amsl.com (Postfix) with ESMTP id 46E063A6A0B for ; Wed, 25 Jun 2008 08:33:09 -0700 (PDT) Received: from Beta5.sparta.com (beta5.sparta.com [157.185.63.21]) by M4.sparta.com (8.13.5/8.13.5) with ESMTP id m5PFXAAR013754 for ; Wed, 25 Jun 2008 10:33:10 -0500 Received: from nemo.columbia.ads.sparta.com (nemo.columbia.sparta.com [157.185.80.75]) by Beta5.sparta.com (8.12.11/8.13.1) with ESMTP id m5PFXAEx018759 for ; Wed, 25 Jun 2008 10:33:10 -0500 Received: from localhost ([157.185.81.122]) by nemo.columbia.ads.sparta.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.3959); Wed, 25 Jun 2008 11:33:09 -0400 Date: Wed, 25 Jun 2008 11:33:11 -0400 (Eastern Daylight Time) From: Sandra Murphy To: sidr@ietf.org Message-ID: X-X-Sender: sandy@nemo.columbia.sparta.com MIME-Version: 1.0 X-OriginalArrivalTime: 25 Jun 2008 15:33:09.0523 (UTC) FILETIME=[C585F630:01C8D6D8] X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (M4.sparta.com [157.185.61.2]); Wed, 25 Jun 2008 10:33:10 -0500 (CDT) Subject: [Sidr] reminder - deadline Mon Jun 30 for -00 approval X-BeenThere: sidr@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Secure Interdomain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: sidr-bounces@ietf.org Errors-To: sidr-bounces@ietf.org Recall that Monday is the deadline for wg chair approval of submission of an internet draft as a sidr wg draft (draft-ietf-sidr-...) at the -00 level. (I.e., anyone thinking of submitting draft-ietf-sidr-....-00.txt should be speaking to Geoff and me.) --Sandy P.S. More reminders: July 7, Monday - Internet Draft Cut-off for initial document (-00) submission by 17:00 PDT July 14, Monday - Internet Draft final submission cut-off by 17:00 PDT July 18, Friday - Early-Bird registration and payment cut-off at 17:00 PDT July 21, Monday - Registration cancellation cut-off at 17:00 PDT _______________________________________________ Sidr mailing list Sidr@ietf.org https://www.ietf.org/mailman/listinfo/sidr From sidr-bounces@ietf.org Wed Jun 25 17:57:52 2008 Return-Path: X-Original-To: sidr-archive@megatron.ietf.org Delivered-To: ietfarch-sidr-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4EF753A68C0; Wed, 25 Jun 2008 17:57:52 -0700 (PDT) X-Original-To: sidr@core3.amsl.com Delivered-To: sidr@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AF0643A68C0 for ; Wed, 25 Jun 2008 17:57:50 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.965 X-Spam-Level: X-Spam-Status: No, score=-1.965 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, J_CHICKENPOX_210=0.6] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YA3ehLNE3TrB for ; Wed, 25 Jun 2008 17:57:49 -0700 (PDT) Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by core3.amsl.com (Postfix) with ESMTP id 739F03A67E5 for ; Wed, 25 Jun 2008 17:57:49 -0700 (PDT) Received: by slice.pfrc.org (Postfix, from userid 1001) id 17E692441A1; Thu, 26 Jun 2008 00:57:52 +0000 (UTC) Date: Wed, 25 Jun 2008 20:57:52 -0400 From: Jeffrey Haas To: sidr@ietf.org Message-ID: <20080626005752.GA12981@slice> References: MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.15+20070412 (2007-04-11) Subject: Re: [Sidr] adoption of draft-huston-sidr-roa-validation-00.txt as a working group work item X-BeenThere: sidr@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Secure Interdomain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sidr-bounces@ietf.org Errors-To: sidr-bounces@ietf.org Chiming in a bit late after catching up on other IETF tasks: On Fri, Apr 04, 2008 at 09:46:29AM -0400, Sandra Murphy wrote: > This internet draft was presented at the sidr meeting in Philadelphia. > Please state whether you believe that this is appropriate to adopt as a > working group work item. Like Steve, I would support this work, either independently or incorporated in the core ROA work. My personal preference would be that some form of this work is incorporated into the core ROA drafts. A few comments on the draft while I'm in here: : [Note: If the origination of the prefix is an AS Set then ??. The : draft authors do not have a clear idea as to what to propose here!] I would suggest text proposing that the validation process is doomed. Given the typical aggregation strategy chosen by current BGP implementations, one is almost never guaranteed a trailing AS_PATH that includes AS_SEQs despite the fact that the protocol will happily permit such a thing when it makes sense. Any reasonable mechanism for dealing with validation of aggregates would likely require changes in BGP code. I'm happy to speculate on such changes, but in a different thread. Personally I think the gain is minimal and we should focus our efforts on the 99.99% of the routes that don't have this issue. : In this case the ROA that would be used for the validation function : is selected from the set such that the most specific valid ROA that : matches or covers the route object address prefix and where the route : object origin AS matches the ROA AS. If there is no such ROA in the : set, then the most specific valid ROA is selected. If there is no : such ROA in the set then the most specific ROA is selected. There is one other case potentially worth mentioning although the authors may consider this a case worth disregarding. In the instance where no valid certificates are available due to *expiration* rather than revocation, an implementation may choose to add this to the candidate list of validation criteria as "better than unvalidated". The match criteria suggested in this draft, after all, provides good inputs to the "security metric" that we've previously discussed here and in RPSEC. With regards to the linked approach, I'm in favor of this mechanism in the referral form. Such a referral can likely be highly compressed - perhaps of the simple form of "repository ip:repository version". Something more general than a repository ip - perhaps a handle - would likely be more important given the desired distributed and replicated nature of the repositories. In section 3, Applying Validation Outcomes to BGP Route Selection, there is some strong suggestion of using BGP local preference for reflecting the "security metric" within the AS. I think this is a fine idea for reflecting a "valid" or "semi valid" or "probably not valid" granularity but I think it is overly strong for the "valid but covering" case. If a prefix is valid, it shouldn't be less preferable simply because it is covered differently by different ROAs. This is especially true in a deployment where multiple validation roots are present for whatever reason. These local preference tweaks also need to be affected by local policy. Doing so would reflect the general idea of a "security metric" from the original RPSEC discussions. Reflecting the security metric in LOCAL_PREF is a nice touch since it means that validation need only happen at the eBGP edges. In section 3.1, Using ROA Validation Outcomes to reject BGP advertisements, you may wish to differentiate the case of the linked and non-linked approach with regards to validation. In the linked case, there is sufficient information present that you could indeed reject a route if you can: 1) Reach the repository 2) Have a current enough version of the relevant objects 3) Know it is invalid. Open issues: : o When should validation of an advertised prefix be performed by a : BGP speaker? Is it strictly necessary to perform validation at a : point prior to loading the object into the Adj-RIB-In structure, : or once the object has been loaded into Adj-RIB-IN, or at a later : time that is determined by a local configuration setting? Should : validation be performed each time a route object is updated by a : peer even when the origin AS has not altered? I think validation could be accomplished at any step of the for a given AS. Downstream ASes will also perform their own validation and may choose to depref a route you have deferred security preference selection on during the distribution process. Ideally, one would do this prior to installing the route in the adj-rib-in. Less ideally would be to install the route but make it ineligible pending near-line validation. Even less ideal would be to advertise the route internally with a security preference that says "validation pending, trust this less than validated routes". Given the lack of additional cryptographic signatures on the BGP route, I believe no additonal validation is required when the prefix/Origin remains the same as long as it is within the window of validity of the ROA. In particular, given such lack, this would constitute a valuable caching mechanism. To whit: : o Can ROA validation be performed on a per-AS basis rather than a : per-BGP speaker? What BGP mechanisms would be appropriate to : support such a mode of operation? Again, presuming no additional cryptographic changes to the BGP route, absolutely. Validation of a BGP route reduces to a simple function: (Security Preference, Valid Until) = ROA_Validation(Prefix, Origin AS) Note that some implementations may choose to add properties relating to the interface or AS from which the route is learned as inputs to the function. This calculation can be done locally or via some RPC mechanism. -- Jeff _______________________________________________ Sidr mailing list Sidr@ietf.org https://www.ietf.org/mailman/listinfo/sidr From sidr-bounces@ietf.org Wed Jun 25 19:34:48 2008 Return-Path: X-Original-To: sidr-archive@megatron.ietf.org Delivered-To: ietfarch-sidr-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 44A4A3A68C3; Wed, 25 Jun 2008 19:34:48 -0700 (PDT) X-Original-To: sidr@core3.amsl.com Delivered-To: sidr@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DDA963A687F for ; Wed, 25 Jun 2008 19:34:46 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.115 X-Spam-Level: X-Spam-Status: No, score=-2.115 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3LRdSLmCoLAs for ; Wed, 25 Jun 2008 19:34:46 -0700 (PDT) Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by core3.amsl.com (Postfix) with ESMTP id 205AB3A67AE for ; Wed, 25 Jun 2008 19:34:46 -0700 (PDT) Received: by slice.pfrc.org (Postfix, from userid 1001) id E214C24419E; Thu, 26 Jun 2008 02:34:48 +0000 (UTC) Date: Wed, 25 Jun 2008 22:34:48 -0400 From: Jeffrey Haas To: sidr@ietf.org Message-ID: <20080626023448.GB12981@slice> References: <20080529180516.26C9C3F4A2@pecan.tislabs.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20080529180516.26C9C3F4A2@pecan.tislabs.com> User-Agent: Mutt/1.5.15+20070412 (2007-04-11) Subject: Re: [Sidr] ROA Validation, Repository Structure, and Bogon drafts X-BeenThere: sidr@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Secure Interdomain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sidr-bounces@ietf.org Errors-To: sidr-bounces@ietf.org On Thu, May 29, 2008 at 02:05:16PM -0400, Sandy Murphy wrote: > It might be judged "apathy", though. The SIDR work is a hyperfocused implementation of esoteric security issues. Admittedly those issues have broad impact on the Internet but they are arcane enough that even those who want to follow have a bit of a time doing so. :-) > whether the working group should adopt each topic as part of our work. > > The messages you should respond to are: > > > http://www.ietf.org/mail-archive/web/sidr/current/msg00401.html > (for draft-huston-sidr-bogons-01.txt - a new version has been > announced since, so the correct link is > http://www.ietf.org/internet-drafts/draft-huston-sidr-bogons-01.txt) I support this work. I'd also suggest a continuation of the discussion of the potential security issues related to these that Danny brought up last IETF. > http://www.ietf.org/mail-archive/web/sidr/current/msg00402.html > for draft-huston-sidr-repos-struct-01.txt I support this draft. I would, in particular, like to see further discussion of shared caches (helps the bootstrapping issue) as well as version numbers on manifests and other resources for purposes of determining what needs to be fetched. -- Jeff _______________________________________________ Sidr mailing list Sidr@ietf.org https://www.ietf.org/mailman/listinfo/sidr From sidr-bounces@ietf.org Fri Jun 27 14:12:31 2008 Return-Path: X-Original-To: sidr-archive@megatron.ietf.org Delivered-To: ietfarch-sidr-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8D23D3A689D; Fri, 27 Jun 2008 14:12:31 -0700 (PDT) X-Original-To: sidr@core3.amsl.com Delivered-To: sidr@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 912F23A6A01 for ; Fri, 27 Jun 2008 14:12:30 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.117 X-Spam-Level: X-Spam-Status: No, score=-1.117 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, DNS_FROM_RFC_BOGUSMX=1.482] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZwcR6NBXb4Ca for ; Fri, 27 Jun 2008 14:12:29 -0700 (PDT) Received: from dog.tcb.net (dog.tcb.net [64.78.150.133]) by core3.amsl.com (Postfix) with ESMTP id CBD4C3A68DF for ; Fri, 27 Jun 2008 14:12:29 -0700 (PDT) Received: by dog.tcb.net (Postfix, from userid 0) id 9525B2684E9; Fri, 27 Jun 2008 15:12:35 -0600 (MDT) Received: from [192.168.1.102] (VDSL-151-118-146-11.DNVR.QWEST.NET [151.118.146.11]) (authenticated-user smtp) (TLSv1/SSLv3 AES128-SHA 128/128) by dog.tcb.net with SMTP; Fri, 27 Jun 2008 15:12:35 -0600 (MDT) (envelope-from danny@tcb.net) X-Avenger: version=0.7.8; receiver=dog.tcb.net; client-ip=151.118.146.11; client-port=61956; syn-fingerprint=65535:55:1:64:M1316,N,W3,N,N,T,S; data-bytes=0 Message-Id: <519F8E1F-8665-46C0-A143-81E946C1ECEF@tcb.net> From: Danny McPherson To: Sandra Murphy In-Reply-To: Mime-Version: 1.0 (Apple Message framework v924) Date: Fri, 27 Jun 2008 15:12:20 -0600 References: X-Mailer: Apple Mail (2.924) Cc: sidr@ietf.org Subject: Re: [Sidr] adoption of draft-huston-sidr-roa-validation-00.txt as a working group work item X-BeenThere: sidr@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Secure Interdomain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes" Sender: sidr-bounces@ietf.org Errors-To: sidr-bounces@ietf.org On Apr 4, 2008, at 7:46 AM, Sandra Murphy wrote: > This internet draft was presented at the sidr meeting in Philadelphia. > Please state whether you believe that this is appropriate to adopt > as a > working group work item. > > If your response is positive, please also indicate whether you would > actively participate in commenting on this draft. > > ROA Validation > > http://www.ietf.org/internet-drafts/draft-huston-sidr-roa-validation-00.txt I'm with Steve & Jeff here. I would support this work, either as part of the ROA validation (which I think I'd prefer), or as a separate document. -danny _______________________________________________ Sidr mailing list Sidr@ietf.org https://www.ietf.org/mailman/listinfo/sidr From sidr-bounces@ietf.org Fri Jun 27 14:14:37 2008 Return-Path: X-Original-To: sidr-archive@megatron.ietf.org Delivered-To: ietfarch-sidr-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B7D5D3A6A01; Fri, 27 Jun 2008 14:14:37 -0700 (PDT) X-Original-To: sidr@core3.amsl.com Delivered-To: sidr@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 90C753A6A01 for ; Fri, 27 Jun 2008 14:14:36 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.117 X-Spam-Level: X-Spam-Status: No, score=-1.117 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, DNS_FROM_RFC_BOGUSMX=1.482] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zJ5WK3t6kHKe for ; Fri, 27 Jun 2008 14:14:35 -0700 (PDT) Received: from dog.tcb.net (dog.tcb.net [64.78.150.133]) by core3.amsl.com (Postfix) with ESMTP id D32FA3A6813 for ; Fri, 27 Jun 2008 14:14:35 -0700 (PDT) Received: by dog.tcb.net (Postfix, from userid 0) id A23C52684EB; Fri, 27 Jun 2008 15:14:41 -0600 (MDT) Received: from [192.168.1.102] (VDSL-151-118-146-11.DNVR.QWEST.NET [151.118.146.11]) (authenticated-user smtp) (TLSv1/SSLv3 AES128-SHA 128/128) by dog.tcb.net with SMTP; Fri, 27 Jun 2008 15:14:41 -0600 (MDT) (envelope-from danny@tcb.net) X-Avenger: version=0.7.8; receiver=dog.tcb.net; client-ip=151.118.146.11; client-port=61960; syn-fingerprint=65535:55:1:64:M1316,N,W3,N,N,T,S; data-bytes=0 Message-Id: <2E5F62D9-0985-4879-B50F-A0E146C563DB@tcb.net> From: Danny McPherson To: sidr@ietf.org, Sandra Murphy In-Reply-To: <20080626023448.GB12981@slice> Mime-Version: 1.0 (Apple Message framework v924) Date: Fri, 27 Jun 2008 15:14:26 -0600 References: <20080529180516.26C9C3F4A2@pecan.tislabs.com> <20080626023448.GB12981@slice> X-Mailer: Apple Mail (2.924) Subject: Re: [Sidr] ROA Validation, Repository Structure, and Bogon drafts X-BeenThere: sidr@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Secure Interdomain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes" Sender: sidr-bounces@ietf.org Errors-To: sidr-bounces@ietf.org On Jun 25, 2008, at 8:34 PM, Jeffrey Haas wrote: > On Thu, May 29, 2008 at 02:05:16PM -0400, Sandy Murphy wrote: >> It might be judged "apathy", though. > > The SIDR work is a hyperfocused implementation of esoteric security > issues. Admittedly those issues have broad impact on the Internet but > they are arcane enough that even those who want to follow have a bit > of > a time doing so. :-) > >> whether the working group should adopt each topic as part of our >> work. >> >> The messages you should respond to are: >> >> >> http://www.ietf.org/mail-archive/web/sidr/current/msg00401.html >> (for draft-huston-sidr-bogons-01.txt - a new version has been >> announced since, so the correct link is >> http://www.ietf.org/internet-drafts/draft-huston-sidr-bogons-01.txt) > > I support this work. I'd also suggest a continuation of the > discussion > of the potential security issues related to these that Danny brought > up > last IETF. I agree as well, obviously :-) > > >> http://www.ietf.org/mail-archive/web/sidr/current/msg00402.html >> for draft-huston-sidr-repos-struct-01.txt > > I support this draft I support this work as well, and as with the others, will continue to review and provide feedback where appropriate. Thanks! -danny _______________________________________________ Sidr mailing list Sidr@ietf.org https://www.ietf.org/mailman/listinfo/sidr