Re: [sidr] Current document status && directionz

Christopher Morrow <morrowc.lists@gmail.com> Thu, 01 December 2016 12:23 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 B0A47129647; Thu, 1 Dec 2016 04:23:21 -0800 (PST)
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 BCohWiOdsf7b; Thu, 1 Dec 2016 04:23:19 -0800 (PST)
Received: from mail-qt0-x243.google.com (mail-qt0-x243.google.com [IPv6:2607:f8b0:400d:c0d::243]) (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 ECD1212949B; Thu, 1 Dec 2016 04:23:18 -0800 (PST)
Received: by mail-qt0-x243.google.com with SMTP id m48so23283109qta.2; Thu, 01 Dec 2016 04:23:18 -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=zDz9kPzKdM9+uXsBeDzPkRp6PPjbi4zdZ9r5+JaR6n4=; b=kXn81mG1OD+kT5B6/lSzund9wDeH581sss++QuaJFO8Om5KzKKgmgYWYLMp4+BTUqP iDIt0XMOS8iE4WiYYy+BkeK0kKRmiF04HfJsb8n/XwqXn68AccS1mA5hIUfuviJQfRUb V2PA7GJ4w2+CsV+djLFQVTbbjdmrxVLBnkn+joitSlhFd2mFUd8ZbM4mLgIDV9AFfnDU JAGVejH2taRrQIc9whHOopFte8Y3SmZhqHrAnvR388rlkR2+GZA4p+rsz3fO/SnqkQxU +UVMEs+i8Jr0Pgif8tqrNqe78sbKy1jdpji1vigPF/KK2IRpr7WktdPeZtlU6L2Is6do Ravg==
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=zDz9kPzKdM9+uXsBeDzPkRp6PPjbi4zdZ9r5+JaR6n4=; b=Cluv2rwNjU5gioOi9b9dLT55WQoi36BjZFzBwb/z2OAZJadx3N9qzuwaewKSjisTL4 Lfb+6jL86g6BnpkOiv7KC7reDX5eHfRyD/1uPDOrnV7R79bHnQmV/7/N9fWbmJyCpS2y sORakGjw5ES95kGk7wtaMPPnNx2Dp7EqeIsHH+BFe/lHOl5aGcygPdWjpbHawY8MKnmZ oORmQE0GKHOUSf9xbX2jSTzE1QdsN7PAQGLXKzsgptZiDLMgJge9AOh/CSETVJtqmVAP Yclx4RKl9cr1du8EwMFZWP+o+Jes6asLzOPUta/LxRVBTS148Pwt8awevHH68FWnuzCN 5qtQ==
X-Gm-Message-State: AKaTC001ffOXzUZFWj/O9kIlkf+xD1/leQd6klnYAHCEoFb2s71HAWU5soaeNqVLGSKqFzH3RCJvlBakl3OSNw==
X-Received: by 10.200.34.56 with SMTP id o53mr37235706qto.272.1480594998133; Thu, 01 Dec 2016 04:23:18 -0800 (PST)
MIME-Version: 1.0
Sender: christopher.morrow@gmail.com
Received: by 10.140.27.179 with HTTP; Thu, 1 Dec 2016 04:23:17 -0800 (PST)
In-Reply-To: <55A37339-61E6-4D44-A00C-8718A05584A1@zdns.cn>
References: <yj9ooa46aumt.wl%morrowc@ops-netman.net> <CAL9jLab3Sv6K5tmbERvFg8AzDdvPJ8Qtv_v++kn_vJd_bgbUmA@mail.gmail.com> <CAL9jLaafREby=4D9EkYwuwvNkmzRSAuXUhGoY1mru0Lb3nJ+SQ@mail.gmail.com> <55A37339-61E6-4D44-A00C-8718A05584A1@zdns.cn>
From: Christopher Morrow <morrowc.lists@gmail.com>
Date: Thu, 1 Dec 2016 07:23:17 -0500
X-Google-Sender-Auth: nluiUCBlsTXHWSV2d9JxXe9qeX4
Message-ID: <CAL9jLaabXQsX96yC8GkdDvAcpf+V3cbUz1KB3J8RONA1ZRf4AQ@mail.gmail.com>
To: Declan Ma <madi@zdns.cn>
Content-Type: multipart/alternative; boundary=001a11406abaeba611054297e202
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidr/1xAcOl3xIMN6EA3Q82jhKZ1bPvE>
Cc: Chris Morrow <morrowc@ops-netman.net>, 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: Thu, 01 Dec 2016 12:23:21 -0000

On Thu, Dec 1, 2016 at 1:51 AM, Declan Ma <madi@zdns.cn>; wrote:

> Chris,
>
> I would like to take this thread to request for comments on how to move on
> SLURM.
>
> During the Seoul meeting, Tim suggested moving it to SIDROPS since SIDR is
> being closed.
>
> Yet I had the impression that the AD hopes keeping the list/structure
> going until current work items are done.
>
> Considering the only issue facing SLURM is the file format that Tim and
> Rudiger mentioned in the MIC, IMHO, if this WG won’t plan to move SLURM to
> SIDROPS, WGLC is desirable to bring about inputs and comments to conclude
> this work.
>
>
if we're just haggling on format... then let's try to finish here?
How about we give it until ~monday for comments here, then start WGLC if no
comments/movement?


>
> Di
>
>
> > 在 2016年12月1日,02:33,Christopher Morrow <morrowc.lists@gmail.com>; 写道:
> >
> > 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
> >
> >
> > _______________________________________________
> > sidr mailing list
> > sidr@ietf.org
> > https://www.ietf.org/mailman/listinfo/sidr
>
>