Re: [sidr] Current document status && directionz

"Carlos M. Martinez" <carlosm3011@gmail.com> Mon, 05 September 2016 22:54 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 5B78412B464; Mon, 5 Sep 2016 15:54:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.45
X-Spam-Level:
X-Spam-Status: No, score=-2.45 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_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 P1JBz0o7A4Gp; Mon, 5 Sep 2016 15:54:29 -0700 (PDT)
Received: from mail-vk0-x22a.google.com (mail-vk0-x22a.google.com [IPv6:2607:f8b0:400c:c05::22a]) (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 3C5AC12B444; Mon, 5 Sep 2016 15:54:29 -0700 (PDT)
Received: by mail-vk0-x22a.google.com with SMTP id w124so86335852vkd.3; Mon, 05 Sep 2016 15:54:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=PgvfelrdTVz8BcLcH+MDxzyVM1Cy4t/M6gb1fDdH31M=; b=ZRNnWzK6PJRwv3DDrZ5Qq17Tugr249s3n4sL0e93ax+wTfJgtZ7ZAfGeRGRRN6pUqm SABMBn5RSaxoCBTlui9obyXP/CWPYVqR9Xged5PR9bQPjgGK3CL+vnQALmqq9CUPI2dm wIFNZMlr1oSF6JMrfP9UOSgTZSg1HlYVq8UoLLGc/jC659b8fgJoHM9XVasJAcqoeJXB rSG0gvYX5VUU1xTxtoMrvLT4EmU20i0SSKNXMmZLJGr6snS97YT8ssW0/PP0YVo0Tga3 B3O8qxsyn4vMECa671YOcu3U8r0w/nGoMkclstjtto9xW2IF4ZQcARAY/tfEwVsNvOlt fecQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=PgvfelrdTVz8BcLcH+MDxzyVM1Cy4t/M6gb1fDdH31M=; b=bCXyO829/nbBYf64wHcZ43FXOZka92HZz1Gp8BUQpUByQI8aIU55jamOSLYAKKs8Ua AkLTFLoHSMm4GQvhHyZSxRyI3T6dTQrI5TWyWGH98YK2CCPGxr40tM0/hNioMk4UuvsV FW4QgzDSs7D2x3QNJqMl/iEW35glSybyFple6cXKMzn3oNh2uZUvJiGo9EsZ9FyrGvHi ceYVY47zGwlVeSZOoLk0G5QbLpO9zIQ0bJlLiQn0qsL+kmm8++iSJM2wmQrSLCoLRQbq 8OB77Vt3MTSe6LFOPWVtEvjDT/iDFcKq3VzL1+yz6XCknP1Q7+sU2DHTp6xmzQk4soF3 T35g==
X-Gm-Message-State: AE9vXwORx1e00k/tQyFRixfQ3B4XqSgPNNxHrx3iYKD+VpwREj41ZlQI/i0tzY3Lyshdsw==
X-Received: by 10.31.210.66 with SMTP id j63mr10148882vkg.113.1473116068045; Mon, 05 Sep 2016 15:54:28 -0700 (PDT)
Received: from ?IPv6:2800:af:a73a:1e4a:2da5:a8c4:25ca:9e7d? ([2800:af:a73a:1e4a:2da5:a8c4:25ca:9e7d]) by smtp.googlemail.com with ESMTPSA id 90sm4724192uam.22.2016.09.05.15.54.26 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 05 Sep 2016 15:54:27 -0700 (PDT)
To: Chris Morrow <morrowc@ops-netman.net>
References: <yj9ooa46aumt.wl%morrowc@ops-netman.net> <AAE3F119-98A3-4618-BBFB-76F921316BD1@gmail.com>
From: "Carlos M. Martinez" <carlosm3011@gmail.com>
Message-ID: <349cb6ac-f4fe-29e5-b01f-3223b14e47de@gmail.com>
Date: Mon, 5 Sep 2016 19:54:53 -0300
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <AAE3F119-98A3-4618-BBFB-76F921316BD1@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidr/BIOA2cW3-frvrWRabc-LzAcC_jM>
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 22:54:31 -0000

Here is the pointer to the document:

https://tools.ietf.org/html/draft-rir-rpki-allres-ta-app-statement-01

Apologies for my earlier laziness.

On 9/5/2016 3:32 PM, Carlos M. Martinez wrote:
> 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