[Sidrops] New Version Notification for draft-ietf-sidrops-bgpsec-rollover-01.txt
"Brian Weis (bew)" <bew@cisco.com> Mon, 14 August 2017 21:05 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 EA9FC132429 for <sidrops@ietfa.amsl.com>; Mon, 14 Aug 2017 14:05:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.521
X-Spam-Level:
X-Spam-Status: No, score=-14.521 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-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 4BORgjEemu52 for <sidrops@ietfa.amsl.com>; Mon, 14 Aug 2017 14:05:25 -0700 (PDT)
Received: from alln-iport-7.cisco.com (alln-iport-7.cisco.com [173.37.142.94]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C47DB132422 for <sidrops@ietf.org>; Mon, 14 Aug 2017 14:05:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2528; q=dns/txt; s=iport; t=1502744725; x=1503954325; h=from:to:subject:date:message-id:references:content-id: content-transfer-encoding:mime-version; bh=b2gnoN3YmfxZnaMUVb+VoD2c0EkLU+Hzxfxwv/XF2pc=; b=i2mETudhnbaoQ4CPTU3DmyJKrF+ZuJH/AIWOfsbl1piaOs5k/vuRBBsJ sTyajar1YjsZQi7i/oVa28jNk1PKigNdsgMkjULTlNeN4wo5GTNKrr6l+ d7+TF5rfdlA+2YKoLNVKR82k6IxBh+N7ksDBPk8YNVA0Umu7R2pTdz32m 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0DMAAA1EJJZ/4gNJK1aAxoBAQEBAgEBAQEIAQEBAYNaZIEUB44KkBGBbpYYDoIELoUZhHs/GAECAQEBAQEBAWsdC4UZAQQBOj0HCwIBPhAyJQIEE4onCBCvJotsAQEBAQEBAQEBAQEBAQEBAQEBAQEegyiCAoMvK4J8gyaBGgESAUAmgnyCMQWRC48mAodRg1OJFoIPWYUEimmJZIwwAR84fwt3FR88AYcHdgGHYoEjgQ8BAQE
X-IronPort-AV: E=Sophos;i="5.41,374,1498521600"; d="scan'208";a="471556564"
Received: from alln-core-3.cisco.com ([173.36.13.136]) by alln-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 14 Aug 2017 21:05:24 +0000
Received: from XCH-RTP-003.cisco.com (xch-rtp-003.cisco.com [64.101.220.143]) by alln-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id v7EL5OSL029426 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for <sidrops@ietf.org>; Mon, 14 Aug 2017 21:05:24 GMT
Received: from xch-rtp-001.cisco.com (64.101.220.141) by XCH-RTP-003.cisco.com (64.101.220.143) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Mon, 14 Aug 2017 17:05:23 -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.1210.000; Mon, 14 Aug 2017 17:05:23 -0400
From: "Brian Weis (bew)" <bew@cisco.com>
To: "sidrops@ietf.org" <sidrops@ietf.org>
Thread-Topic: New Version Notification for draft-ietf-sidrops-bgpsec-rollover-01.txt
Thread-Index: AQHTFTztw+OIpRuS2kK1eAgSOntpBg==
Date: Mon, 14 Aug 2017 21:05:23 +0000
Message-ID: <605BE4D9-0A76-40D4-BA4B-AA4FFEA5B2B8@cisco.com>
References: <150274294941.10434.10745925044193104854.idtracker@ietfa.amsl.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.32.173.184]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <8742A446F0344342B7A1637901B0C267@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/6TQi_KIbKYbqL1uQ2lR-2_hnvoQ>
Subject: [Sidrops] New Version Notification for draft-ietf-sidrops-bgpsec-rollover-01.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: Mon, 14 Aug 2017 21:05:28 -0000
This version of the BGPsec rollover I-D addresses many helpful comments provided by Sriram. The majority of the wording changes are adjustments to the terminology and addition of clarification text. Major changes include a re-written Abstract, re-written Security Considerations, and referencing draft-sriram-replay-protection-design-discussion-08 as a source of other replay protection methods for BGPsec. I believe this addresses all of the WGLC comments on the document. Thanks, Brian > A new version of I-D, draft-ietf-sidrops-bgpsec-rollover-01.txt > has been successfully submitted by Brian Weis and posted to the > IETF repository. > > Name: draft-ietf-sidrops-bgpsec-rollover > Revision: 01 > Title: BGPsec Router Certificate Rollover > Document date: 2017-08-14 > Group: sidrops > Pages: 10 > URL: https://www.ietf.org/internet-drafts/draft-ietf-sidrops-bgpsec-rollover-01.txt > Status: https://datatracker.ietf.org/doc/draft-ietf-sidrops-bgpsec-rollover/ > Htmlized: https://tools.ietf.org/html/draft-ietf-sidrops-bgpsec-rollover-01 > Htmlized: https://datatracker.ietf.org/doc/html/draft-ietf-sidrops-bgpsec-rollover-01 > Diff: https://www.ietf.org/rfcdiff?url2=draft-ietf-sidrops-bgpsec-rollover-01 > > Abstract: > Certificate Authorities (CAs) managing CA certificates and End-Entity > (EE) certificates within the Resource Public Key Infrastructure > (RPKI) will also manage BGPsec router certificates. But the rollover > of CA and EE certificates BGPsec router certificates have additional > considerations for Normal and emergency rollover processes. The > rollover must be carefully managed in order to synchronize > distribution of router public keys and BGPsec routers creating BGPsec > Update messages verified with those router public keys. This > document provides general recommendations for the rollover process, > as well as describing reasons why the rollover of BGPsec router > certificates might be necessary. When this rollover process is > followed the rollover should be accomplished without routing > information being lost. > > > > > 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. > > The IETF Secretariat > -- Brian Weis Security, CSG, Cisco Systems Telephone: +1 408 526 4796 Email: bew@cisco.com
- [Sidrops] New Version Notification for draft-ietf… Brian Weis (bew)