Re: [sidr] Current document status && directionz

Christopher Morrow <morrowc.lists@gmail.com> Wed, 26 October 2016 15:35 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 809A6129625; Wed, 26 Oct 2016 08:35:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 niWXwz2Ee7SS; Wed, 26 Oct 2016 08:35:26 -0700 (PDT)
Received: from mail-qk0-x234.google.com (mail-qk0-x234.google.com [IPv6:2607:f8b0:400d:c09::234]) (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 2A8961294C7; Wed, 26 Oct 2016 08:35:26 -0700 (PDT)
Received: by mail-qk0-x234.google.com with SMTP id v138so8950676qka.5; Wed, 26 Oct 2016 08:35:26 -0700 (PDT)
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=Hq7ACGXa6XUWfsu3Quj5W4Sy4auX8bKHxEqCiotQO3Y=; b=z/YAICCkPpYBrpvY20eh9YalqecuuoRzRVKS1JCBTrofUSaaaPWMRZcJ+KPCp73HdW ZoWOld8gEG/e71fc8NX9TN2wBcKyDBiNE9RvAjY1LtDGZsnB/rsMKj5IuzP5GqpjNLRR 9QtfZkySc8xl7av444OdoPZ/muhbyqlzfXBYHOdvTh+fK44rRfPBosSqp0UbmDerC3p7 b4at/LEBAs0/luNVHMQBz1J2swbVXZ3uFQ3sV7ppNvsvkYew004o+QgBeFJYOb87A+rj o9U3wJaj2kcU5BLgjNSvm4v6XqS52vZvZlksaqF2N1J2SzYDUC4pywwWu5HoOOuyyvr9 RVlg==
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=Hq7ACGXa6XUWfsu3Quj5W4Sy4auX8bKHxEqCiotQO3Y=; b=Uk1I2iVBlUyRFKeHjoaT2053j9hRD1aYCnEMP04OypJvsw5J6B6tJAYNQ84MvsMZzO GDmOHSbiQHco5E9tmzVHxfMksTmLbcpX3kfV0QRIM+cvBWLoTd7ZV1NF/AqY5s2OyAb0 ZcTk9cr9eBhp9/+vuORfgo6R3OihzNDpZf9wfUX8YZzDbcIXsAZZZDmx5kKRIBcNUEP7 DRhz0z+IFDT7Ura3H9JdfKcRMot+RQY5n0hfXTiSROpxo0DdbMJXu+IIARwRNoiQ9Vg2 30UcnNIu7QkzMAVDzIqwD1JQF1ae2SjXZVcP8zjFSNQOrnVGT1XfcAbAWcyTE72jCJ0D SOmQ==
X-Gm-Message-State: ABUngvcp3Siq/VAqYlfyRJ6tjQ6PpltVI6crS4HYAxccaAJ1YA/zJ2KF4qP5GkwbLTvOP0e1CXwfXrVIzV1vZA==
X-Received: by 10.55.129.6 with SMTP id c6mr2576734qkd.4.1477496125199; Wed, 26 Oct 2016 08:35:25 -0700 (PDT)
MIME-Version: 1.0
Sender: christopher.morrow@gmail.com
Received: by 10.140.105.244 with HTTP; Wed, 26 Oct 2016 08:35:24 -0700 (PDT)
In-Reply-To: <yj9ooa46aumt.wl%morrowc@ops-netman.net>
References: <yj9ooa46aumt.wl%morrowc@ops-netman.net>
From: Christopher Morrow <morrowc.lists@gmail.com>
Date: Wed, 26 Oct 2016 11:35:24 -0400
X-Google-Sender-Auth: C823bDtoUVsI91ywKmHUKA66HtY
Message-ID: <CAL9jLab3Sv6K5tmbERvFg8AzDdvPJ8Qtv_v++kn_vJd_bgbUmA@mail.gmail.com>
To: Chris Morrow <morrowc@ops-netman.net>
Content-Type: multipart/alternative; boundary=94eb2c05cd80b32442053fc65f24
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidr/lKQVPHWjYe0UGIisH1Mz3IRcITk>
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, 26 Oct 2016 15:35:30 -0000

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-origin-validation-signaling
draft-ietf-sidr-publication
draft-ietf-sidr-rpki-oob-setup
draft-ietf-sidr-rpki-rtr-rfc6810-bis
draft-ietf-sidr-delta-protocol (10/26 sent forward)
draft-ietf-sidr-rpki-validation-reconsidered (10/26 sent forward)


Currently still active documents (8 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-rpki-validation-reconsidered
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

which leaves to be dealt with by Chicago 2 documents:
draft-ietf-sidr-rpki-tree-validation
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.

-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
>