Re: [sidr] Current document status && directionz

joel jaeggli <joelja@bogus.com> Sat, 03 September 2016 21:06 UTC

Return-Path: <joelja@bogus.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 8913012B0EC; Sat, 3 Sep 2016 14:06:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.508
X-Spam-Level:
X-Spam-Status: No, score=-6.508 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-1.508] autolearn=ham autolearn_force=no
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 gOEQimwiSvQb; Sat, 3 Sep 2016 14:06:28 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6121812B0AD; Sat, 3 Sep 2016 14:06:28 -0700 (PDT)
Received: from mb-2.local ([IPv6:2601:1c0:cb00:5d1a:5996:34aa:2529:58c3]) (authenticated bits=0) by nagasaki.bogus.com (8.15.2/8.15.2) with ESMTPSA id u83L6Qx1094948 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT); Sat, 3 Sep 2016 21:06:27 GMT (envelope-from joelja@bogus.com)
X-Authentication-Warning: nagasaki.bogus.com: Host [IPv6:2601:1c0:cb00:5d1a:5996:34aa:2529:58c3] claimed to be mb-2.local
To: Chris Morrow <morrowc@ops-netman.net>, sidr@ietf.org, sidr-chairs@ietf.org, sidr-ads@ietf.org
References: <yj9ooa46aumt.wl%morrowc@ops-netman.net>
From: joel jaeggli <joelja@bogus.com>
Message-ID: <453bf466-2b47-966f-4378-19a161d0c6a1@bogus.com>
Date: Sat, 3 Sep 2016 14:06:25 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:47.0) Gecko/20100101 Thunderbird/47.0
MIME-Version: 1.0
In-Reply-To: <yj9ooa46aumt.wl%morrowc@ops-netman.net>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="u7WoRkMrMXlHps8N59g1F6O7IcK9pDVXK"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidr/E60euJUbuJk5djob9wuyEWN5f7c>
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: Sat, 03 Sep 2016 21:06:29 -0000

On 9/2/16 1:56 PM, Chris Morrow 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

I think we good good feeback on the draft of a charter, I will start
work on taking this to the IESG, but as some point soon the time will
come to ask for community review of that proposal.

regards
joel

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