Re: [Sidrops] I-D Action: draft-ietf-sidrops-route-server-rpki-light-02.txt
Nick Hilliard <nick@foobar.org> Fri, 21 July 2017 13:15 UTC
Return-Path: <nick@foobar.org>
X-Original-To: sidrops@ietfa.amsl.com
Delivered-To: sidrops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 35DF0131D1C; Fri, 21 Jul 2017 06:15:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 SdVaDNv2HBWD; Fri, 21 Jul 2017 06:15:47 -0700 (PDT)
Received: from mail.netability.ie (mail.netability.ie [IPv6:2a03:8900:0:100::5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1339F131471; Fri, 21 Jul 2017 06:15:46 -0700 (PDT)
X-Envelope-To: draft-ietf-sidrops-route-server-rpki-light@ietf.org
Received: from cupcake.local (089-101-195156.ntlworld.ie [89.101.195.156] (may be forged)) (authenticated bits=0) by mail.netability.ie (8.15.2/8.15.2) with ESMTPSA id v6LDFd3f048084 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 21 Jul 2017 14:15:39 +0100 (IST) (envelope-from nick@foobar.org)
X-Authentication-Warning: cheesecake.ibn.ie: Host 089-101-195156.ntlworld.ie [89.101.195.156] (may be forged) claimed to be cupcake.local
Message-ID: <5971FE7B.6060607@foobar.org>
Date: Fri, 21 Jul 2017 14:15:39 +0100
From: Nick Hilliard <nick@foobar.org>
User-Agent: Postbox 5.0.16 (Macintosh/20170718)
MIME-Version: 1.0
To: Aris Lambrianidis <aristidis.lambrianidis@ams-ix.net>
CC: "sidrops@ietf.org" <sidrops@ietf.org>, draft-ietf-sidrops-route-server-rpki-light@ietf.org
References: <149192729348.15702.14003842869826829117@ietfa.amsl.com> <8EB8DB53-793E-4269-8CF4-6BAB1D2B76B6@de-cix.net> <B3BC1C5C-27AE-4809-82B6-297D090CEF0C@ams-ix.net>
In-Reply-To: <B3BC1C5C-27AE-4809-82B6-297D090CEF0C@ams-ix.net>
X-Enigmail-Version: 1.2.3
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/Z9-R23VJq6J4gT4eAf0KNcTmEtw>
Subject: Re: [Sidrops] I-D Action: draft-ietf-sidrops-route-server-rpki-light-02.txt
X-BeenThere: sidrops@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: A list for the SIDR Operations WG <sidrops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sidrops>, <mailto:sidrops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sidrops/>
List-Post: <mailto:sidrops@ietf.org>
List-Help: <mailto:sidrops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sidrops>, <mailto:sidrops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Jul 2017 13:15:49 -0000
Aris, the concerns I brought up about this draft on jan 13 / jan 14 have not been addressed in -01 or -02. The concerns were basically: this is not how to solve the problem of making things easier for route server clients + the reasons why. Nick Aris Lambrianidis wrote: > Hello all, > > As a quick note, Daniel and I are in Prague, at IETF99. Daniel will be > here until Tuesday afternoon and I’ll be here > for the entire week, should you have any concerns, comments, or > questions. We’re looking into moving things forward > (read: go for WG Last Call), so we’d appreciate any feedback, in person > or by email. > > --Aris > > >> On 11 Apr 2017, at 18:15, Thomas King <thomas.king@de-cix.net >> <mailto:thomas.king@de-cix.net>> wrote: >> >> Hi all, >> >> we have worked on the feedback we received through many channels (e.g. >> this mailing list): >> - Clarification of the “Security Considerations” section. Please let >> us know if you think a security issue is not tackled. >> - The feedback told us that different modes of operation for how >> “invalid” and “not found” routes should be handled needs to be >> addressed. For this, section “BGP Prefix Origin Validation State >> Utilized at Route-Servers” was added. >> - House-Keeping (e.g. update references, fix typos) >> >> Best regards, >> Thomas >> >> >> On 11/04/2017, 18:14, "Sidrops on behalf of internet-drafts@ietf.org >> <mailto:internet-drafts@ietf.org>" <sidrops-bounces@ietf.org >> <mailto:sidrops-bounces@ietf.org> on behalf of >> internet-drafts@ietf.org <mailto:internet-drafts@ietf.org>> wrote: >> >> >> A New Internet-Draft is available from the on-line Internet-Drafts >> directories. >> This draft is a work item of the SIDR Operations of the IETF. >> >> Title : Signaling Prefix Origin Validation >> Results from a Route Server to Peers >> Authors : Thomas King >> Daniel Kopp >> Aristidis Lambrianidis >> Arnaud Fenioux >> Filename : draft-ietf-sidrops-route-server-rpki-light-02.txt >> Pages : 7 >> Date : 2017-04-11 >> >> Abstract: >> This document defines the usage of the BGP Prefix Origin Validation >> State Extended Community [RFC8097] to signal prefix origin >> validation >> results from a route server to its peers. Upon reception of prefix >> origin validation results peers can use this information in their >> local routing decision process. >> >> >> >> The IETF datatracker status page for this draft is: >> https://datatracker.ietf.org/doc/draft-ietf-sidrops-route-server-rpki-light/ >> >> There are also htmlized versions available at: >> https://tools.ietf.org/html/draft-ietf-sidrops-route-server-rpki-light-02 >> https://datatracker.ietf.org/doc/html/draft-ietf-sidrops-route-server-rpki-light-02 >> >> A diff from the previous version is available at: >> https://www.ietf.org/rfcdiff?url2=draft-ietf-sidrops-route-server-rpki-light-02 >> >> >> Please note that it may take a couple of minutes from the time of >> submission >> until the htmlized version and diff are available at tools.ietf.org >> <http://tools.ietf.org>. >> >> Internet-Drafts are also available by anonymous FTP at: >> ftp://ftp.ietf.org/internet-drafts/ >> >> _______________________________________________ >> Sidrops mailing list >> Sidrops@ietf.org <mailto:Sidrops@ietf.org> >> https://www.ietf.org/mailman/listinfo/sidrops >> >> >> _______________________________________________ >> Sidrops mailing list >> Sidrops@ietf.org <mailto:Sidrops@ietf.org> >> https://www.ietf.org/mailman/listinfo/sidrops > > _______________________________________________ > Sidrops mailing list > Sidrops@ietf.org > https://www.ietf.org/mailman/listinfo/sidrops
- Re: [Sidrops] I-D Action: draft-ietf-sidrops-rout… Thomas King
- [Sidrops] I-D Action: draft-ietf-sidrops-route-se… internet-drafts
- Re: [Sidrops] I-D Action: draft-ietf-sidrops-rout… Aris Lambrianidis
- Re: [Sidrops] I-D Action: draft-ietf-sidrops-rout… Nick Hilliard
- Re: [Sidrops] I-D Action: draft-ietf-sidrops-rout… Aris Lambrianidis
- Re: [Sidrops] I-D Action: draft-ietf-sidrops-rout… Job Snijders
- Re: [Sidrops] I-D Action: draft-ietf-sidrops-rout… Jakob Heitz (jheitz)
- Re: [Sidrops] I-D Action: draft-ietf-sidrops-rout… Job Snijders
- Re: [Sidrops] I-D Action: draft-ietf-sidrops-rout… Job Snijders
- Re: [Sidrops] I-D Action: draft-ietf-sidrops-rout… Aris Lambrianidis
- Re: [Sidrops] I-D Action: draft-ietf-sidrops-rout… Job Snijders
- Re: [Sidrops] I-D Action: draft-ietf-sidrops-rout… Randy Bush