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

Thomas King <thomas.king@de-cix.net> Tue, 11 April 2017 16:15 UTC

Return-Path: <thomas.king@de-cix.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 E7066129537; Tue, 11 Apr 2017 09:15:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.602
X-Spam-Level:
X-Spam-Status: No, score=-2.602 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-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 ylkDaAHwAJ4M; Tue, 11 Apr 2017 09:15:53 -0700 (PDT)
Received: from de-cix.net (relay4.de-cix.net [IPv6:2a02:c50:0:1e::4:1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9904112EAF2; Tue, 11 Apr 2017 09:15:52 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="5.37,186,1488841200"; d="scan'208";a="4844497"
Received: from smtp.de-cix.net ([192.168.65.10]) by mailgw012.de-cix.net with ESMTP; 11 Apr 2017 18:15:50 +0200
Received: from MS-EXCHANGE.for-the-inter.net (MS-EXCHANGE.for-the-inter.net [192.168.49.2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by smtp.de-cix.net (Postfix) with ESMTPS id B90C6B00B8; Tue, 11 Apr 2017 18:15:50 +0200 (CEST)
Received: from MS-EXCHANGE.for-the-inter.net (192.168.49.2) by MS-EXCHANGE.for-the-inter.net (192.168.49.2) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Tue, 11 Apr 2017 18:15:50 +0200
Received: from MS-EXCHANGE.for-the-inter.net ([fe80::9449:4d85:69bf:3d4c]) by MS-EXCHANGE.for-the-inter.net ([fe80::9449:4d85:69bf:3d4c%12]) with mapi id 15.00.1263.000; Tue, 11 Apr 2017 18:15:50 +0200
From: Thomas King <thomas.king@de-cix.net>
To: "internet-drafts@ietf.org" <internet-drafts@ietf.org>, "i-d-announce@ietf.org" <i-d-announce@ietf.org>
CC: "sidrops@ietf.org" <sidrops@ietf.org>
Thread-Topic: [Sidrops] I-D Action: draft-ietf-sidrops-route-server-rpki-light-02.txt
Thread-Index: AQHSst7Efgg6fIy+J0C9WVomdLJQwqHAWAaA
Date: Tue, 11 Apr 2017 16:15:49 +0000
Message-ID: <8EB8DB53-793E-4269-8CF4-6BAB1D2B76B6@de-cix.net>
References: <149192729348.15702.14003842869826829117@ietfa.amsl.com>
In-Reply-To: <149192729348.15702.14003842869826829117@ietfa.amsl.com>
Accept-Language: en-US, de-DE
Content-Language: en-GB
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [192.168.60.10]
Content-Type: text/plain; charset="utf-8"
Content-ID: <25F8F9B326F8C649B25C1B8722382123@for-the-inter.net>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/Wym9i0Z6pdJj7ISLIyDyfsUL4Uo>
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: <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, 11 Apr 2017 16:15:56 -0000

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" <sidrops-bounces@ietf.org on behalf of 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.
    
    Internet-Drafts are also available by anonymous FTP at:
    ftp://ftp.ietf.org/internet-drafts/
    
    _______________________________________________
    Sidrops mailing list
    Sidrops@ietf.org
    https://www.ietf.org/mailman/listinfo/sidrops