Re: [sidr] wg adoption call for draft-tbruijnzeels-sidr-validation-local-cache-02

Tim Bruijnzeels <tim@ripe.net> Wed, 16 December 2015 10:30 UTC

Return-Path: <tim@ripe.net>
X-Original-To: sidr@ietfa.amsl.com
Delivered-To: sidr@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 073671ACE44 for <sidr@ietfa.amsl.com>; Wed, 16 Dec 2015 02:30:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FxTlM6uPROSW for <sidr@ietfa.amsl.com>; Wed, 16 Dec 2015 02:30:55 -0800 (PST)
Received: from molamola.ripe.net (molamola.ripe.net [IPv6:2001:67c:2e8:11::c100:1371]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 86A531ACE42 for <sidr@ietf.org>; Wed, 16 Dec 2015 02:30:55 -0800 (PST)
Received: from titi.ripe.net ([193.0.23.11]) by molamola.ripe.net with esmtps (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.84) (envelope-from <tim@ripe.net>) id 1a99M7-0000Cc-LQ; Wed, 16 Dec 2015 11:30:49 +0100
Received: from sslvpn.ripe.net ([193.0.20.230] helo=vpn-1.ripe.net) by titi.ripe.net with esmtps (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from <tim@ripe.net>) id 1a99M7-00010p-GY; Wed, 16 Dec 2015 11:30:47 +0100
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
Content-Type: text/plain; charset="us-ascii"
From: Tim Bruijnzeels <tim@ripe.net>
In-Reply-To: <56709354.6080006@bbn.com>
Date: Wed, 16 Dec 2015 11:30:47 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <26C6CEB6-D858-4AC4-BC6E-3B3A8927CE03@ripe.net>
References: <C5F46C82-299D-4DBB-BF6D-7B24FE3C330D@tislabs.com> <56709354.6080006@bbn.com>
To: Stephen Kent <kent@bbn.com>
X-Mailer: Apple Mail (2.2104)
X-ACL-Warn: Delaying message
X-RIPE-Spam-Level: --
X-RIPE-Spam-Report: Spam Total Points: -2.9 points pts rule name description ---- ---------------------- ------------------------------------ -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP -0.0 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay domain -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000]
X-RIPE-Signature: 784d7acfe6559f2a0b602ec6519a0719f4299181a30b74cec0defa3768693ee5
Archived-At: <http://mailarchive.ietf.org/arch/msg/sidr/-9aZoMqU2GRYFHec9XsPBpZfwkU>
Cc: sidr@ietf.org
Subject: Re: [sidr] wg adoption call for draft-tbruijnzeels-sidr-validation-local-cache-02
X-BeenThere: sidr@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Secure Interdomain Routing <sidr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sidr>, <mailto:sidr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sidr/>
List-Post: <mailto:sidr@ietf.org>
List-Help: <mailto:sidr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sidr>, <mailto:sidr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Dec 2015 10:30:57 -0000

Hi Steve, group,

I agree that it would be useful to have a standards track document co-authored by the three major implementors.

But this document is intended as an informational track document to describe our implementation only, so that:
- it can be scrutinised
- we can refer to it to explain how our implementation works
- it can server as an example, not standard, on how this can work

It may very well be that parts of this exercise are useful to feed into another, standards track and implementation agnostic, document later. I believe that Rob already expressed interest in this - long term, but he can correct me of course :)

In short: I see your point, but I don't believe the efforts are mutually exclusive.

Tim


> On 15 Dec 2015, at 23:25, Stephen Kent <kent@bbn.com> wrote:
> 
> I think we ought to have a document that describes how an RP can manage a local
> cache, since we usually say that we expect RPs to do so. However, this document 
> seems to be a description of only one implementation's approach to local cache
> management. I'd be more comfortable with a document that is co-authored by
> the developers of the three major RP implementations.
> 
> Steve
>> As noted in the minutes, the authors of draft-tbruijnzeels-sidr-validation-local-cache-02 request that the working group adopt this work as a wg work item.
>> 
>> A working group adoption poll starts now and will end 14 days from now on 23 December.
>> 
>> Please respond on the list to say whether you support adoption of this work as a working group work item AND whether you will participate in the discussion.
>> 
>> Remember that working group consensus to adopt the work needs responses, not just absence of objection, so speak up.
>> 
>> --Sandy, speaking as one of the wg co-chairs
>> 
>> 
>> 
>> _______________________________________________
>> sidr mailing list
>> 
>> sidr@ietf.org
>> https://www.ietf.org/mailman/listinfo/sidr
> 
> _______________________________________________
> sidr mailing list
> sidr@ietf.org
> https://www.ietf.org/mailman/listinfo/sidr