Re: [Sidrops] I-D Action: draft-ietf-sidrops-rtr-keying-00.txt

"Brian Weis (bew)" <bew@cisco.com> Tue, 25 September 2018 17:58 UTC

Return-Path: <bew@cisco.com>
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 8E96A12785F; Tue, 25 Sep 2018 10:58:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.5
X-Spam-Level:
X-Spam-Status: No, score=-14.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 2Iaz9GhOH1hM; Tue, 25 Sep 2018 10:58:02 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 222081277CC; Tue, 25 Sep 2018 10:58:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=11928; q=dns/txt; s=iport; t=1537898281; x=1539107881; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=43JZ68tf944grgkSWV+DFokX3jgFskvGCCJePKWi/6U=; b=Pnrj95Dpz0CRDu1ktdWFm3Guoe+2lXbMQfCZ2iQKCc6TV3X/2wYLAJSx BbyIIcz4U9TbQvyJadyOcQ2VsHc6/uZSjzBXog6l9WDOKkfQAiwxhQyku pWyMkoW+1ceBfiBkIo0Wd2CKZDQ69UufrNd9R5Yh/p4PDssBneAY0XEHP c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AJAABgdqpb/4gNJK1YAxoBAQEBAQIBAQEBBwIBAQEBgVGCDmV/KAqDaogVjC2BaIkCiDWFPBSBZgsYAQqEA0YCF4NPITQYAQMBAQIBAQJtHAyFOQIBAwEBIUsLEAIBCD8DAgICHwYLFBECBA4FGYMIAYEdTAMVD6QWgS6EMwc9gkQNglGKeheCAIESJwwTgkyCVkUBAQIBAYEqARIBNgodCYI6MYImAo1qE45WLAkChkGDB4NGgxkXgUVKhAeJFot6bYd7AhEUgSUNEDhkcXAVGiEqAYJBCYsNhT5vi1aBH4EeAQE
X-IronPort-AV: E=Sophos;i="5.54,303,1534809600"; d="scan'208,217";a="457272411"
Received: from alln-core-3.cisco.com ([173.36.13.136]) by rcdn-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 25 Sep 2018 17:58:00 +0000
Received: from XCH-RTP-001.cisco.com (xch-rtp-001.cisco.com [64.101.220.141]) by alln-core-3.cisco.com (8.15.2/8.15.2) with ESMTPS id w8PHw0ma025231 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 25 Sep 2018 17:58:01 GMT
Received: from xch-rtp-001.cisco.com (64.101.220.141) by XCH-RTP-001.cisco.com (64.101.220.141) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Tue, 25 Sep 2018 13:57:59 -0400
Received: from xch-rtp-001.cisco.com ([64.101.220.141]) by XCH-RTP-001.cisco.com ([64.101.220.141]) with mapi id 15.00.1395.000; Tue, 25 Sep 2018 13:57:59 -0400
From: "Brian Weis (bew)" <bew@cisco.com>
To: Christopher Morrow <christopher.morrow@gmail.com>
CC: "sidrops@ietf.org" <sidrops@ietf.org>, "sidrops-chairs@ietf.org" <sidrops-chairs@ietf.org>
Thread-Topic: [Sidrops] I-D Action: draft-ietf-sidrops-rtr-keying-00.txt
Thread-Index: AQHUVJA4yRhUkSWGO0+BYn+Nc+6cnqUAu3AAgADRFIA=
Date: Tue, 25 Sep 2018 17:57:59 +0000
Message-ID: <63A21AC4-4377-4CA9-BA8E-09B2F3351700@cisco.com>
References: <153785311881.31266.9050138500778961489@ietfa.amsl.com> <CAL9jLaak0hnk4BSNHkpKFR42K_6=qmq3t87a7kBduJ1-OvvPMA@mail.gmail.com>
In-Reply-To: <CAL9jLaak0hnk4BSNHkpKFR42K_6=qmq3t87a7kBduJ1-OvvPMA@mail.gmail.com>
Accept-Language: en-US
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: [10.19.191.168]
Content-Type: multipart/alternative; boundary="_000_63A21AC443774CA9BA8E09B2F3351700ciscocom_"
MIME-Version: 1.0
X-Outbound-SMTP-Client: 64.101.220.141, xch-rtp-001.cisco.com
X-Outbound-Node: alln-core-3.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/josaj8jojwiY7Y0eIWuJKVz-ksU>
Subject: Re: [Sidrops] I-D Action: draft-ietf-sidrops-rtr-keying-00.txt
X-BeenThere: sidrops@ietf.org
X-Mailman-Version: 2.1.29
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 Sep 2018 17:58:05 -0000

It’s mature. How about WGLC and be done with it? Don’t forget that <https://tools.ietf.org/html/draft-ietf-sidrops-bgpsec-rollover-04> has been approved for publication but is waiting on rtr-keying to publish….

Thanks,
Brian

On Sep 24, 2018, at 10:29 PM, Christopher Morrow <christopher.morrow@gmail.com<mailto:christopher.morrow@gmail.com>> wrote:

howdy sidrops folks, this is the last draft standing from the former SIDR WG, it looked more like a SIDROPS draft so we shifted it over and ... in it's former life it was:
   https://datatracker.ietf.org/doc/draft-ietf-sidr-rtr-keying/ (version 16)

I believe the authors simply requested a name change and submitted that...
Should we WGLC this or discuss it some on-list or? :)

-chris

On Tue, Sep 25, 2018 at 1:25 AM <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 WG of the IETF.

        Title           : Router Keying for BGPsec
        Authors         : Randy Bush
                          Sean Turner
                          Keyur Patel
        Filename        : draft-ietf-sidrops-rtr-keying-00.txt
        Pages           : 18
        Date            : 2018-09-21

Abstract:
   BGPsec-speaking routers are provisioned with private keys in order to
   sign BGPsec announcements.  The corresponding public keys are
   published in the global Resource Public Key Infrastructure, enabling
   verification of BGPsec messages.  This document describes two methods
   of generating the public-private key-pairs: router-driven and
   operator-driven.



The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-sidrops-rtr-keying/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-sidrops-rtr-keying-00
https://datatracker.ietf.org/doc/html/draft-ietf-sidrops-rtr-keying-00


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

--
Brian Weis
Security, CSG, Cisco Systems
Telephone: +1 408 526 4796
Email: bew@cisco.com<mailto:bew@cisco.com>