Re: [sidr] Current document status && directionz

Christopher Morrow <morrowc.lists@gmail.com> Wed, 30 November 2016 18:33 UTC

Return-Path: <christopher.morrow@gmail.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 B9B02129626; Wed, 30 Nov 2016 10:33:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.099
X-Spam-Level:
X-Spam-Status: No, score=-0.099 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 vTJIbE_zNcOb; Wed, 30 Nov 2016 10:33:30 -0800 (PST)
Received: from mail-qk0-x242.google.com (mail-qk0-x242.google.com [IPv6:2607:f8b0:400d:c09::242]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2FAE21295C7; Wed, 30 Nov 2016 10:33:27 -0800 (PST)
Received: by mail-qk0-x242.google.com with SMTP id n204so23012964qke.2; Wed, 30 Nov 2016 10:33:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=vLHLs9Pp8z7IcPQYb8qjIpNn81zCDx4EKpKllpQRbuw=; b=IQNEdvc2MGXqVVaHpuSoulqNCjjQJ9loPYNtwFDe9hy0iBx5akGZgHs7YqgIOQ2cxu a55k5eW/ajep6GxqgzhxHOmv3BAP4cLmw5dtbylHfPbra+a57y6vnIvFMrl5P1KIAU/b nbnSmz2WGcThHN5zdPg7gODhft0gwxwOCM2ZTTDNsp3IPuTbN8WKNtCydTTQkQmdoH9v ZIiuNEP5HRcMvhyE2GWGGAN7WnPQ8IqilY8ISvREt7tO7bsI3E6iEMvkLEbJpU1KRhr/ HJFQjp7DGTuI4X/rM3Ua/+4WWPax4GuzXLb2JpMSiS+NlbRwCYa/9nSDmTNngBBM+DBZ YOGQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=vLHLs9Pp8z7IcPQYb8qjIpNn81zCDx4EKpKllpQRbuw=; b=PZT6PxuTCUcMtGwyuJaVJtYlvsEjUyZZbdzxfjsUC9qAEiBANUqkp1hvE8BbM0Yl9w NCcTQ5m+m7tA4huDQMOr1II8kZuLHLeHwNvnrPHXJCBQK1SE3PHGovW27EC9x76dpb66 OtRcTWRrsI4/6tQdSYJN45JkiRTHZpi/PzqRRhYFhwnw4M8P8saYlk/YlJX+yMhDQDNB 2opVIrS0A9PwRpc71Z2KZM8W2/+Sez6/hV0B5DF3sOxM2I0DXeAYYV78S+POTA2Z7i8I lFYj4EOqDaZWPjoZqiD+n4SHFnkeShoF5jDa5/l9GAqbYjmfeUBlGJKRYhu0TeIBDVjW NSOg==
X-Gm-Message-State: AKaTC01+d+JAIQv8qq6AgCi5Z1Ncz+zp88b3CfhtT3G2o6zJ6bEB9Y2x3FITtijQuxODoBj2VJQyuDuawkN26g==
X-Received: by 10.55.78.147 with SMTP id c141mr33787687qkb.4.1480530806285; Wed, 30 Nov 2016 10:33:26 -0800 (PST)
MIME-Version: 1.0
Sender: christopher.morrow@gmail.com
Received: by 10.140.27.179 with HTTP; Wed, 30 Nov 2016 10:33:25 -0800 (PST)
In-Reply-To: <CAL9jLab3Sv6K5tmbERvFg8AzDdvPJ8Qtv_v++kn_vJd_bgbUmA@mail.gmail.com>
References: <yj9ooa46aumt.wl%morrowc@ops-netman.net> <CAL9jLab3Sv6K5tmbERvFg8AzDdvPJ8Qtv_v++kn_vJd_bgbUmA@mail.gmail.com>
From: Christopher Morrow <morrowc.lists@gmail.com>
Date: Wed, 30 Nov 2016 13:33:25 -0500
X-Google-Sender-Auth: qHOdAlKuy7ziqHLQTFsigeo0nc8
Message-ID: <CAL9jLaafREby=4D9EkYwuwvNkmzRSAuXUhGoY1mru0Lb3nJ+SQ@mail.gmail.com>
To: Chris Morrow <morrowc@ops-netman.net>
Content-Type: multipart/alternative; boundary=001a114a97c6c9b225054288f06b
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidr/vYCCs5A7fPifGp-ST1TWWnRyt3k>
Cc: sidr-ads@ietf.org, "sidr-chairs@ietf.org" <sidr-chairs@ietf.org>, "sidr@ietf.org" <sidr@ietf.org>
Subject: Re: [sidr] Current document status && directionz
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: Wed, 30 Nov 2016 18:33:34 -0000

And again, restarting... post meeting and post travel refocusing :)

On Wed, Oct 26, 2016 at 11:35 AM, Christopher Morrow <
morrowc.lists@gmail.com>; wrote:

> Restarting this thread, with some updates :)
>
> Preparing for Seoul in a few weeks time, with the intent that we do not
> meet face-to-face in Chicago, have all current 'protocol' related docs to
> the IESG/done and meet instead in sidr-ops if there are agenda items at
> that time :)
>
> Currently we have the following in IESG/pub-request status (13 documents):
> draft-ietf-sidr-adverse-actions
> draft-ietf-sidr-as-migration
> draft-ietf-sidr-bgpsec-algs
> draft-ietf-sidr-bgpsec-ops
> draft-ietf-sidr-bgpsec-overview
> draft-ietf-sidr-bgpsec-pki-profiles
> draft-ietf-sidr-bgpsec-protocol
>
    draft-ietf-sidr-delta-protocol (10/26 sent forward)


> draft-ietf-sidr-origin-validation-signaling
> draft-ietf-sidr-publication
> draft-ietf-sidr-rpki-oob-setup
> draft-ietf-sidr-rpki-rtr-rfc6810-bis
>


I had thought I sent validation-reconsidered forward for processing, I'm
doing that today:

> draft-ietf-sidr-rpki-validation-reconsidered
>

 Currently still active documents (6 documents):

>

> draft-ietf-sidr-bgpsec-rollover
> draft-ietf-sidr-lta-use-cases
> draft-ietf-sidr-route-server-rpki-light
> draft-ietf-sidr-rpki-tree-validation
> draft-ietf-sidr-rtr-keying
> draft-ietf-sidr-slurm
>
> (this reflects the changes since the last email, included below)
>
> I believe we're still planning to move (and have agreement from authors):
>  draft-ietf-sidr-bgpsec-rollover
>  draft-ietf-sidr-lta-use-cases
>  draft-ietf-sidr-route-server-rpki-light
>  draft-ietf-sidr-rtr-keying
>

draft-ietf-sidr-rpki-tree-validation


> which leaves to be dealt with by Chicago 2 documents:
> draft-ietf-sidr-slurm
>
> I think this is good, I believe (and of course I should be corrected if
> wrong)
>   slurm - more work inbound and discussion planned in Seoul
>   tree-validation - I thought moved to sidr-ops, but don't have docs to
> back that up.
>
>
I still think this is good, I will be sending a request to the OPS-AD folk
today to move:
 draft-ietf-sidr-bgpsec-rollover
 draft-ietf-sidr-lta-use-cases
 draft-ietf-sidr-route-server-rpki-light
 draft-ietf-sidr-rtr-keying
 draft-ietf-sidr-rpki-tree-validation

to sidr-ops... If there are corrections/additions please send them along :)

-chris


> -chris
>
> On Fri, Sep 2, 2016 at 4:56 PM, Chris Morrow <morrowc@ops-netman.net>;
> wrote:
>
>>
>> Howdy SIDR peeps,
>> (+bonus ops ad)
>>
>> Following on the Berlin meeting we were trying to accomplish two
>> things:
>>
>>   1) get all documents related to sidr protocols into wglc and then
>>   publication
>>
>>   2) get all documents which are more operationally focused moved
>>   along to an ops group (sidr-ops or something akin to that)
>>
>> With that in mind there are 8 documents in the publication queue:
>>   draft-ietf-sidr-as-migration
>>   draft-ietf-sidr-bgpsec-algs
>>   draft-ietf-sidr-bgpsec-ops
>>   draft-ietf-sidr-bgpsec-overview
>>   draft-ietf-sidr-bgpsec-pki-profiles
>>   draft-ietf-sidr-bgpsec-protocol
>>   draft-ietf-sidr-origin-validation-signaling
>>   draft-ietf-sidr-rpki-rtr-rfc6810-bis
>>
>> and 11 still in progress. Of the 11 left Sandy and I think they
>> roughly break down like:
>>
>> Documents which should move to the ops group:
>>   draft-ietf-sidr-bgpsec-rollover
>>   draft-ietf-sidr-lta-use-cases
>>   draft-ietf-sidr-route-server-rpki-light - authors notified/queried
>> about this
>>   draft-ietf-sidr-rtr-keying
>>
>> documents which should finish out in sidr:
>>   draft-ietf-sidr-delta-protocol
>>   draft-ietf-sidr-publication
>>   draft-ietf-sidr-rpki-oob-setup - pub request in flight
>>   draft-ietf-sidr-rpki-tree-validation
>>   draft-ietf-sidr-rpki-validation-reconsidered
>>   draft-ietf-sidr-slurm - authors recently updated
>>   draft-ietf-sidr-adverse-actions - wglc imminent
>>
>> I think if there's no meaningful discussion on change for these
>> between now and 9/16/2016 (Sept 16th) we will assume this list is
>> correct. For documents in the 'move' list, if progress to publication
>> happens 'good!'. For all documents in the 'stays' list:
>>   1) we aim to have wglc by Seoul
>>   2) publication requests started on as many as possible
>>
>> We plan to meet in Seoul, but not in Chicago (Mar 2017) where we
>> expect the ops group to exist and meet. We can progress documents in
>> SIDR after Seoul, but the WG should close out shortly after the new
>> year. (or that's the goal).
>>
>> Thoughts?
>> -chris
>>
>> _______________________________________________
>> sidr mailing list
>> sidr@ietf.org
>> https://www.ietf.org/mailman/listinfo/sidr
>>
>
>