Re: [sidr] Current document status && directionz
"Carlos M. Martinez" <carlosm3011@gmail.com> Mon, 05 September 2016 18:33 UTC
Return-Path: <carlosm3011@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 CC93012B451; Mon, 5 Sep 2016 11:33:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.75
X-Spam-Level:
X-Spam-Status: No, score=-1.75 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 EUue8dMdrxYg; Mon, 5 Sep 2016 11:33:02 -0700 (PDT)
Received: from mail-ua0-x22d.google.com (mail-ua0-x22d.google.com [IPv6:2607:f8b0:400c:c08::22d]) (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 2A9DB12B0B3; Mon, 5 Sep 2016 11:33:02 -0700 (PDT)
Received: by mail-ua0-x22d.google.com with SMTP id u68so12493165uau.1; Mon, 05 Sep 2016 11:33:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=jB8hJrUaagYTkjNsm81pT3/nnPXf3On+iIppb/D3yBI=; b=0VQROg3xTmMGh+Gj3SxY+o+sXF5/oZLxjW3+vDEuvcfVovk+ga5Ilb1an+hgREO+EX VtMTYqSEOH+2oIjxH6OgEFSuUQxnjZCeXNEHf0hqG6aDVd5JygoXnvi4LeRImArZPbFk jOR2d4AflFc8q6Q7Ex2dH2MiGgvYo47ov/WFARCjhUXuGY3GR0eI/JM1YviynBkxQtXF X+9olkLs/JKpnYMrdjqwW63/U/UlxW9jqWVBNTlia7Q+uuDWay/I5lRYJwaGWunl7t0L 8wp2ZqDHkwZdGePX8DjE/AsOLHwU2hsK+lISN3h0bac6U2FZzd8MVJCHvIIQEiTAz63C rCpg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=jB8hJrUaagYTkjNsm81pT3/nnPXf3On+iIppb/D3yBI=; b=fGA2lTewSotHdn/q83DYNuSGcLmS0XRiJXSD4h+gVvLn+RGoz3d+NGusA9EykdrsZT AKzJl5NUX4PBV7ZwJSehkNe9bCVcT1XCODqnY0u4QHGo+sLkUcWQIduqmz5ifUpbuWzG SGdkpK1rSc3zCFo99SVYHofuRgevGVa93oZXe5ThS/U/bK+/f5Yh5krjrRImNmn/STKc Jo6AQhlechDtaZYRVVi0vPZ0FQOB0UteQ2iPUkU1ZcOR/QyUJexHhbFyTTlIbm1iqIEd LmffG/HlFaCmh1ERwi4WmtejnFmJ+GU5NtanZhnpijfFtk+VvV3UV82bv3PjaGSO5En9 NThA==
X-Gm-Message-State: AE9vXwPL16OB9OIiNDKmmU0Hv6D1qM8H1UVMm5uHZy7C8GYPblydMp4cpf8lJOC7VMTrhQ==
X-Received: by 10.159.33.6 with SMTP id 6mr15534986uab.27.1473100381061; Mon, 05 Sep 2016 11:33:01 -0700 (PDT)
Received: from [200.7.87.24] ([2001:13c7:7001:7000:4d2c:b463:1c3:50df]) by smtp.gmail.com with ESMTPSA id 61sm4454202uai.24.2016.09.05.11.32.59 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 05 Sep 2016 11:33:00 -0700 (PDT)
From: "Carlos M. Martinez" <carlosm3011@gmail.com>
To: Chris Morrow <morrowc@ops-netman.net>
Date: Mon, 05 Sep 2016 15:32:56 -0300
Message-ID: <AAE3F119-98A3-4618-BBFB-76F921316BD1@gmail.com>
In-Reply-To: <yj9ooa46aumt.wl%morrowc@ops-netman.net>
References: <yj9ooa46aumt.wl%morrowc@ops-netman.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
X-Mailer: MailMate (1.9.5r5260)
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidr/XxKsVnX6GdFD8v25XnKmMQY98Go>
Cc: sidr-ads@ietf.org, sidr-chairs@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: Mon, 05 Sep 2016 18:33:04 -0000
Hi Chris, I know we already discussed this over private email, but perhaps you can comment on the list on the future of the requested WG adoption call for the ‘all resources’ applicability statement draft. thanks! -Carlos On 2 Sep 2016, at 17:56, 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 > > 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] Current document status && directionz Chris Morrow
- Re: [sidr] Current document status && directionz joel jaeggli
- Re: [sidr] Current document status && directionz Carlos M. Martinez
- Re: [sidr] Current document status && directionz Carlos M. Martinez
- Re: [sidr] Current document status && directionz Randy Bush
- Re: [sidr] Current document status && directionz Chris Morrow
- Re: [sidr] Current document status && directionz Chris Morrow
- Re: [sidr] Current document status && directionz Stephen Kent
- Re: [sidr] Current document status && directionz Roque Gagliano (rogaglia)
- Re: [sidr] Current document status && directionz Rob Austein
- Re: [sidr] Current document status && directionz Christopher Morrow
- Re: [sidr] Current document status && directionz Rob Austein
- Re: [sidr] Current document status && directionz Randy Bush
- Re: [sidr] Current document status && directionz Christopher Morrow
- Re: [sidr] Current document status && directionz Andrew de la Haye
- Re: [sidr] Current document status && directionz Christopher Morrow
- Re: [sidr] Current document status && directionz Rob Austein
- Re: [sidr] Current document status && directionz Roque Gagliano (rogaglia)
- Re: [sidr] Current document status && directionz Roque Gagliano (rogaglia)
- Re: [sidr] Current document status && directionz Randy Bush
- Re: [sidr] Current document status && directionz Heasley
- Re: [sidr] Current document status && directionz Christopher Morrow
- Re: [sidr] Current document status && directionz David Conrad
- Re: [sidr] Current document status && directionz David Conrad
- Re: [sidr] Current document status && directionz Christopher Morrow
- Re: [sidr] Current document status && directionz Christopher Morrow
- Re: [sidr] Current document status && directionz Randy Bush
- Re: [sidr] Current document status && directionz Randy Bush
- Re: [sidr] Current document status && directionz Sandra Murphy
- Re: [sidr] Current document status && directionz Christopher Morrow
- Re: [sidr] Current document status && directionz Randy Bush
- Re: [sidr] Current document status && directionz Christopher Morrow
- Re: [sidr] Current document status && directionz Randy Bush
- Re: [sidr] Current document status && directionz Tim Bruijnzeels
- Re: [sidr] Current document status && directionz Christopher Morrow
- Re: [sidr] Current document status && directionz Randy Bush
- Re: [sidr] Current document status && directionz Christopher Morrow
- Re: [sidr] Current document status && directionz Declan Ma
- Re: [sidr] Current document status && directionz Christopher Morrow
- Re: [sidr] Current document status && directionz Randy Bush