IETF Logo Mail Archive

Re: [sidr] New Version Notification for draft-kklf-sidr-route-server-rpki-light-00.txt

Thomas King <thomas.king@de-cix.net> Tue, 26 April 2016 12:34 UTC

Return-Path: <thomas.king@de-cix.net>
X-Original-To: sidr@ietfa.amsl.com
Delivered-To: sidr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 23C1712D18D for <sidr@ietfa.amsl.com>; Tue, 26 Apr 2016 05:34:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level:
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.996, SPF_HELO_PASS=-0.001, SPF_PASS=-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 LFgphKodJwvk for <sidr@ietfa.amsl.com>; Tue, 26 Apr 2016 05:34:04 -0700 (PDT)
Received: from de-cix.net (relay3.de-cix.net [IPv6:2a02:c50:0:1e::3:1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3249012D193 for <sidr@ietf.org>; Tue, 26 Apr 2016 05:34:02 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="5.24,536,1454972400"; d="scan'208";a="2823628"
Received: from smtp.de-cix.net ([192.168.65.10]) by mailgw011.de-cix.net with ESMTP; 26 Apr 2016 14:34:00 +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 5F396B009D; Tue, 26 Apr 2016 14:34:00 +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.1156.6; Tue, 26 Apr 2016 14:34:00 +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.1156.000; Tue, 26 Apr 2016 14:34:00 +0200
From: Thomas King <thomas.king@de-cix.net>
To: "sidr@ietf.org" <sidr@ietf.org>
Thread-Topic: [sidr] New Version Notification for draft-kklf-sidr-route-server-rpki-light-00.txt
Thread-Index: AQHRn52SzdB4iNpq/Ee01GU1Y2aqTp+b/c8AgAAyxYA=
Date: Tue, 26 Apr 2016 12:33:59 +0000
Message-ID: <EFD49909-B5BB-4CBC-996B-7C78E2BA1803@de-cix.net>
References: <5B8B8060-A9ED-427D-85BD-50723DA4CBB9@de-cix.net> <alpine.WNT.2.00.1604261239360.4044@mw-PC>
In-Reply-To: <alpine.WNT.2.00.1604261239360.4044@mw-PC>
Accept-Language: en-US, de-DE
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [192.168.140.65]
Content-Type: text/plain; charset="utf-8"
Content-ID: <7AA02E664806CB44AE5902FBA19F723C@for-the-inter.net>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/sidr/HygMsU1b_SGGu_UiGaPZJe5pQrY>
Cc: "John G. Scudder" <jgs@juniper.net>, "Sriram, Kotikalapudi (Fed)" <kotikalapudi.sriram@nist.gov>, Matthias Waehlisch <m.waehlisch@fu-berlin.de>
Subject: Re: [sidr] New Version Notification for draft-kklf-sidr-route-server-rpki-light-00.txt
X-BeenThere: sidr@ietf.org
X-Mailman-Version: 2.1.17
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: Tue, 26 Apr 2016 12:34:06 -0000

I would like to come back to a solution that was discussed already: If the route-server is not able to perform the origin prefix validation the BGP community is not added to the BGP update. The BGP community is only added if the origin prefix validation could be executed.

This solution allows a clear signalling. This would also be compatible with the current ietf-sidr-origin-validation-signaling document and could be easily stated in draft-kklf-sidr-route-server-rpki-light.

Best regards,
Thomas




On 26/04/2016, 13:32, "Matthias Waehlisch" <m.waehlisch@fu-berlin.de> wrote:

>There was a quite similar discussion in 2013, for the thread see
>
>https://mailarchive.ietf.org/arch/msg/sidr/zvSP_-iiEfu_acYInK5lOMnys5U
>
>As far as I remember w/o a final conclusion (or the conclusion was 
>leave it as is).
>
>
>Cheers
>  matthias
>
>On Tue, 26 Apr 2016, Thomas King wrote:
>
>> Hi all,
>> 
>> Following up on the discussion we had during the last IETF meeting I would like to discuss with you how we proceed with the “Did not perform validation” value. I think this value is very important and should be added to ietf-sidr-origin-validation-signaling.
>> 
>> Best regards,
>> Thomas
>> _______________________________________________
>> sidr mailing list
>> sidr@ietf.org
>> https://www.ietf.org/mailman/listinfo/sidr
>> 
>
>
>-- 
>Dr. Matthias Waehlisch
>.  Freie Universitaet Berlin, Inst. fuer Informatik, AG CST
>.  Takustr. 9, D-14195 Berlin, Germany
>.. mailto:m.waehlisch@fu-berlin.de .. http://www.inf.fu-berlin.de/~waehl
>:. Also: http://inet.haw-hamburg.de .. http://www.link-lab.net

v2.23.0 | Report a Bug | By Email