Re: [sidr] Current document status && directionz

"Roque Gagliano (rogaglia)" <rogaglia@cisco.com> Wed, 07 September 2016 20:10 UTC

Return-Path: <rogaglia@cisco.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 5303012B395; Wed, 7 Sep 2016 13:10:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.03
X-Spam-Level:
X-Spam-Status: No, score=-16.03 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.508, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 k3mzm48cLVYt; Wed, 7 Sep 2016 13:10:10 -0700 (PDT)
Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0BDEC12B1AB; Wed, 7 Sep 2016 13:10:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2714; q=dns/txt; s=iport; t=1473279010; x=1474488610; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=yzTreL6KQD/iUIP4xhs2T7G42ihAQ/6OeykW8fpotPk=; b=Bb6d1u72tm/lo2ENtdV2s4BbwdfksgV3t2Ac/T6nV4MCjYJQXKOD5iLn xS3fP8n1opDl4M3joZcycUyQ2jBq0UiykAD/b358KWZM02vPWkPuPr9NV 3fXWT8VUAHsynAe3ltSnnN35BPoDEQiSagnRTJH9EcMsVldoWS4AzykaO Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BRAQA8c9BX/4sNJK1dGQEBAQEBAQEBA?= =?us-ascii?q?QEBgy0BAQEBAR5XfAeNKKsRggMZC4V4AoFqOBQBAgEBAQEBAQFeJ4RiAQEEAQE?= =?us-ascii?q?BawsQAgEIGC4nCyUCBAEJBAUUB4gvDrwyAQEBAQEBAQEBAQEBAQEBAQEBAQEBF?= =?us-ascii?q?wWGL4ROhCoWhT8dBY5hingBhxOIKYFujW2MUIN6AR42hFBwg04rgQJ/AQEB?=
X-IronPort-AV: E=Sophos;i="5.30,297,1470700800"; d="scan'208";a="320782995"
Received: from alln-core-6.cisco.com ([173.36.13.139]) by alln-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 07 Sep 2016 20:10:09 +0000
Received: from XCH-RTP-012.cisco.com (xch-rtp-012.cisco.com [64.101.220.152]) by alln-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id u87KA8n6011171 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 7 Sep 2016 20:10:09 GMT
Received: from xch-rtp-011.cisco.com (64.101.220.151) by XCH-RTP-012.cisco.com (64.101.220.152) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Wed, 7 Sep 2016 16:10:07 -0400
Received: from xch-rtp-011.cisco.com ([64.101.220.151]) by XCH-RTP-011.cisco.com ([64.101.220.151]) with mapi id 15.00.1210.000; Wed, 7 Sep 2016 16:10:08 -0400
From: "Roque Gagliano (rogaglia)" <rogaglia@cisco.com>
To: Chris Morrow <morrowc@ops-netman.net>, joel jaeggli <joelja@bogus.com>
Thread-Topic: [sidr] Current document status && directionz
Thread-Index: AQHSCUPUwDSafJV2ikaIhhAEiDU42Q==
Date: Wed, 7 Sep 2016 20:10:08 +0000
Message-ID: <D3F63DEF.57FCA%rogaglia@cisco.com>
References: <yj9ooa46aumt.wl%morrowc@ops-netman.net> <453bf466-2b47-966f-4378-19a161d0c6a1@bogus.com> <yj9o60q9ui5k.wl%morrowc@ops-netman.net>
In-Reply-To: <yj9o60q9ui5k.wl%morrowc@ops-netman.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.6.7.160722
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.55.172.245]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <B0FA0ACEE13C7A4D9647C81509A9273A@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidr/fMNI742Z2EsiuRAE8UE4NQkJoFI>
Cc: "sidr-ads@ietf.org" <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, 07 Sep 2016 20:10:11 -0000

Hi Chris,

With regards to "draft-rir-rpki-allres-ta-app-statement², the question for
the WG acceptance should go back to the authors on their willingness to
take WG feedback.

If the aim is to work with the WG, I think the document describes a
current problem with inter-RIR address transfers and one (but maybe not
the one the WG would finally document) solution.

If the aim is for the RIRs to inform the rest of the world of a decision
they have taken, this should be an individual draft submission into the
Independent Submission Editor and not a SIDR WG item.

Regards,
Roque


On 06/09/16 18:06, "sidr on behalf of Chris Morrow" <sidr-bounces@ietf.org
on behalf of morrowc@ops-netman.net>; wrote:

>At Sat, 3 Sep 2016 14:06:25 -0700,
>joel jaeggli <joelja@bogus.com>; wrote:
>> 
>> [1 Re: Current document status && directionz <multipart/mixed (7bit)>]
>> [1.1  <text/plain; windows-1252 (quoted-printable)>]
>> 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.
>> 
>
>I also forgot to mention the all-res draft:
>  draft-rir-rpki-allres-ta-app-statement
>
>is waiting for some AD comments to complete (with chairs I mean) to set
>location/direction.
>
>_______________________________________________
>sidr mailing list
>sidr@ietf.org
>https://www.ietf.org/mailman/listinfo/sidr