Re: [sidr] wg adoption call for draft-ymbk-bgpsec-rtr-rekeying-00.txt

"George, Wes" <wesley.george@twcable.com> Sat, 24 March 2012 20:37 UTC

Return-Path: <wesley.george@twcable.com>
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 C025021F8484 for <sidr@ietfa.amsl.com>; Sat, 24 Mar 2012 13:37:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.07
X-Spam-Level:
X-Spam-Status: No, score=-1.07 tagged_above=-999 required=5 tests=[AWL=0.393, BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eKiQzYotWKE5 for <sidr@ietfa.amsl.com>; Sat, 24 Mar 2012 13:37:23 -0700 (PDT)
Received: from cdpipgw01.twcable.com (cdpipgw01.twcable.com [165.237.59.22]) by ietfa.amsl.com (Postfix) with ESMTP id 0CAD721F8483 for <sidr@ietf.org>; Sat, 24 Mar 2012 13:37:22 -0700 (PDT)
X-SENDER-IP: 10.136.163.12
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.73,643,1325480400"; d="scan'208";a="358511199"
Received: from unknown (HELO PRVPEXHUB03.corp.twcable.com) ([10.136.163.12]) by cdpipgw01.twcable.com with ESMTP/TLS/RC4-MD5; 24 Mar 2012 16:36:31 -0400
Received: from PRVPEXVS03.corp.twcable.com ([10.136.163.27]) by PRVPEXHUB03.corp.twcable.com ([10.136.163.12]) with mapi; Sat, 24 Mar 2012 16:37:22 -0400
From: "George, Wes" <wesley.george@twcable.com>
To: Christopher Morrow <morrowc.lists@gmail.com>, Matt Lepinski <mlepinski@bbn.com>
Date: Sat, 24 Mar 2012 16:37:20 -0400
Thread-Topic: [sidr] wg adoption call for draft-ymbk-bgpsec-rtr-rekeying-00.txt
Thread-Index: Ac0Jx7wu/FgwIfZiR42oq99zZ07L8AANSpfw
Message-ID: <DCC302FAA9FE5F4BBA4DCAD465693779173D27628C@PRVPEXVS03.corp.twcable.com>
References: <24B20D14B2CD29478C8D5D6E9CBB29F60F6C0E99@Hermes.columbia.ads.sparta.com> <24B20D14B2CD29478C8D5D6E9CBB29F60F6C0EFE@Hermes.columbia.ads.sparta.com> <4F5E58EF.2000908@ieca.com> <CAL9jLabKPd1XyGrhgQSbHRtp-StRax2JRGLM_yi5fJGi7aJHHA@mail.gmail.com> <DCC302FAA9FE5F4BBA4DCAD465693779173D276228@PRVPEXVS03.corp.twcable.com> <CAL9jLaaEEJaqW5ArsPnW3L8bDR5vzYof+SGYSNGT-cx+R3Uh2A@mail.gmail.com> <4F6DD3E3.4090501@bbn.com> <CAL9jLaaTfJz=3m5UJ6VjLcn1Djp-HG_PEWnYdcAX_ZTyfbHreA@mail.gmail.com> <CAL9jLabV_1no-pgFFWcmnKqqSMaSKxaUG+uipSMTmmOXMdpndA@mail.gmail.com>
In-Reply-To: <CAL9jLabV_1no-pgFFWcmnKqqSMaSKxaUG+uipSMTmmOXMdpndA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "sidr@ietf.org" <sidr@ietf.org>
Subject: Re: [sidr] wg adoption call for draft-ymbk-bgpsec-rtr-rekeying-00.txt
X-BeenThere: sidr@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Sat, 24 Mar 2012 20:37:23 -0000

> -----Original Message-----
> From: sidr-bounces@ietf.org [mailto:sidr-bounces@ietf.org] On Behalf Of
> Christopher Morrow
> Sent: Saturday, March 24, 2012 10:09 AM
> To: Matt Lepinski
> Cc: sidr@ietf.org
> Subject: Re: [sidr] wg adoption call for draft-ymbk-bgpsec-rtr-rekeying-00.txt
>
> oh, except that the -rollover doc says:
> "The BGPSEC key roll-over process should be very tighten to the key
>    provisioning mechanisms that would be in place.  The key provisioning
>    mechanisms for BGPSEC are not yet documented.  We will assume that
>    such an automatic provisioning mechanism will be in place (a possible
>    provisioning mechanism when the private key lives only inside the BGP
>    speaker is the Enrollment over Secure Transport (EST).  This protocol
>    will allow BGPSEC code to include automatic re-keying scripts with
>    minimum development cost."
>
> in the second sentence it's asking for this doc... (the first sentence
> seems to have some missing words though)
>
> > thanks!
> > -chris
> >


[WEG] the cited text can be changed, especially now that the referenced documentation exists. :-)
My point was not that all of the information isn't important, but rather that this occupies similar space and I don't know that it needs to be separated, other than as a separate section in one document. This WG generates a lot of documents that are logically separated by subject matter, but by necessity very intertwined, which sometimes makes it hard for those not intimately involved in writing/reviewing the drafts to keep track of what information is discussed where, and requires a fair amount of cross-referencing to truly understand the implementation. I'm thinking that if there are obvious places to consolidate, we should do so.

Wes

This E-mail and any of its attachments may contain Time Warner Cable proprietary information, which is privileged, confidential, or subject to copyright belonging to Time Warner Cable. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout.