Re: [Sidrops] I-D Action: draft-ietf-sidrops-route-server-rpki-light-02.txt

Aris Lambrianidis <aristidis.lambrianidis@ams-ix.net> Tue, 25 July 2017 14:38 UTC

Return-Path: <aristidis.lambrianidis@ams-ix.net>
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 54879131CE1; Tue, 25 Jul 2017 07:38:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.001, 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 SXbrT7paXn7w; Tue, 25 Jul 2017 07:38:41 -0700 (PDT)
Received: from deliverix.ams-ix.net (deliverix.ams-ix.net [IPv6:2001:67c:1a8:a101::70]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 27CC0131CE2; Tue, 25 Jul 2017 07:38:40 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at ams-ix.net
Received: from [IPv6:2001:67c:1a8:102:10e2:b570:73cc:c076] (unknown [IPv6:2001:67c:1a8:102:10e2:b570:73cc:c076]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: aristidis) by deliverix.ams-ix.net (Postfix) with ESMTPSA id 4942540F9A; Tue, 25 Jul 2017 16:38:39 +0200 (CEST)
From: Aris Lambrianidis <aristidis.lambrianidis@ams-ix.net>
Message-Id: <F1D60787-5C00-46EF-BADE-8E68ECDEB506@ams-ix.net>
Content-Type: multipart/signed; boundary="Apple-Mail=_3EE466D9-3F60-41AD-8EF3-3F0DB6128F09"; protocol="application/pgp-signature"; micalg="pgp-sha256"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Date: Tue, 25 Jul 2017 16:38:38 +0200
In-Reply-To: <5971FE7B.6060607@foobar.org>
Cc: "sidrops@ietf.org" <sidrops@ietf.org>, draft-ietf-sidrops-route-server-rpki-light@ietf.org, Job Snijders <job@instituut.net>
To: Nick Hilliard <nick@foobar.org>
References: <149192729348.15702.14003842869826829117@ietfa.amsl.com> <8EB8DB53-793E-4269-8CF4-6BAB1D2B76B6@de-cix.net> <B3BC1C5C-27AE-4809-82B6-297D090CEF0C@ams-ix.net> <5971FE7B.6060607@foobar.org>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/m1vuSkllkvGmgA32kpPdijR5XiU>
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: Tue, 25 Jul 2017 14:38:51 -0000

Hi Nick,

We’re working on an updated draft to elaborate further
on the valid path hiding concerns you raised, as well
as describing a new transitive extended BGP community attribute,
(instead of reusing the one described in RFC8097),
based on Job Snijders’ offline comments.

--Aris


> On 21 Jul 2017, at 15:15, Nick Hilliard <nick@foobar.org> wrote:
> 
> 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
> 
> _______________________________________________
> Sidrops mailing list
> Sidrops@ietf.org
> https://www.ietf.org/mailman/listinfo/sidrops