Re: [sidr] Current document status && directionz

Christopher Morrow <morrowc.lists@gmail.com> Thu, 08 September 2016 18:50 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 3D25B12B011 for <sidr@ietfa.amsl.com>; Thu, 8 Sep 2016 11:50:40 -0700 (PDT)
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=unavailable 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 S02CmRSQizdg for <sidr@ietfa.amsl.com>; Thu, 8 Sep 2016 11:50:38 -0700 (PDT)
Received: from mail-qt0-x232.google.com (mail-qt0-x232.google.com [IPv6:2607:f8b0:400d:c0d::232]) (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 8E41E12B124 for <sidr@ietf.org>; Thu, 8 Sep 2016 11:40:52 -0700 (PDT)
Received: by mail-qt0-x232.google.com with SMTP id 93so28613298qtg.2 for <sidr@ietf.org>; Thu, 08 Sep 2016 11:40:52 -0700 (PDT)
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=8NM1Cblfi0064l/1EfXxND9zhK31EvyvhuDzT2qOhcI=; b=XFUqaHAz1X83ie6FiwXFhZMk7LI3rZXtN2Kbw91Nhb8aRi7RtPfjIx6Ig0F6rAalfi Ch8ZCMh2DDi7vuQvS3nGHhm2eIA+pZDzSaxIHYTYItpP36wIEOGNUs04ZEywfglsgfEW Ukig1sKlRwqH3YYpe/gH3qeXLl1hmvk88+uj8gveNp6bI8ecN4TQ1wSV72Au+on6Kn1k 0yoJj9PNmp6a77yCmX0ZY2eoB91Fhzo+if7FzCHko68bCiR6OkjroM532FH7NDe60QDC 3vslhjg2Uh1H79vnJd0HFrR53/G8w76NQ3gBQ+8YaRxKfJsw48zS34ajbn+IxmGuzGkB uSJQ==
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=8NM1Cblfi0064l/1EfXxND9zhK31EvyvhuDzT2qOhcI=; b=UuB1DjYFaw59QU45SykHU3LXSRUMK+JD7vClb7UCbcwV+8aEmXb3bLHzwtXfQDCaP8 54aSZKvhBp9Bq+L1IXomRgdEhpJFIqy6wksgpIyRhRJhH7SCy+rleNrLzGt4eZtpyHib B7y/oU0/JZX6B3qC17wGYfQ/+ojqMCO9tIL7kudEA6j1+oyAzVHRfWD8Ky+or9s1Vhft q+klS/jlHhgfdPXgDeStsw8VsbNRdE6zvpUde8T/0JFWug1pCw9j3jU6EC+k2lRWhpMT c2TYqN1ouWVvEly56RTGPBKjWBU9kk1tD8Qb4hyDQ6qRCewSxKclb/3dV24oYO+BJu1e ijHQ==
X-Gm-Message-State: AE9vXwOGLcY44pZ9XMUA1NbMPof2IxcfDWGy0iYcAAwVmRWSQk6tApaKcL8TrqqpQNbwZqIVv7+hoyZo8sc2iA==
X-Received: by 10.200.40.206 with SMTP id j14mr1348383qtj.123.1473360051683; Thu, 08 Sep 2016 11:40:51 -0700 (PDT)
MIME-Version: 1.0
Sender: christopher.morrow@gmail.com
Received: by 10.140.85.116 with HTTP; Thu, 8 Sep 2016 11:40:50 -0700 (PDT)
In-Reply-To: <etPan.57d1a436.41d16d8a.1a2d@virtualized.org>
References: <yj9ooa46aumt.wl%morrowc@ops-netman.net> <AAE3F119-98A3-4618-BBFB-76F921316BD1@gmail.com> <349cb6ac-f4fe-29e5-b01f-3223b14e47de@gmail.com> <m2shteszs3.wl-randy@psg.com> <0a66024b-5cae-1abb-dc53-b11c1e35cdeb@bbn.com> <20160906220000.F1005420823A@minas-ithil.hactrn.net> <CAL9jLaYLJ2_1Dj9BtpQBa+Ta+BrGdvNpHHfFgrRxQ6SVo-6RXw@mail.gmail.com> <20160907040720.769594208DBB@minas-ithil.hactrn.net> <CAL9jLabwQQzigJF1=36dY7uWVcHSBKBmRC8DLd4pv1F1i0PZJg@mail.gmail.com> <BBA42462-C8AF-4C78-973B-3C475A9970D6@ripe.net> <CAL9jLaZ5tPtg0D1gWvURv=CXRdzWud5C+FWv4WUHeW6v2BLzvw@mail.gmail.com> <m237lax2g7.wl-randy@psg.com> <3F99CEBE-90B9-46F9-92CE-3E773933A760@shrubbery.net> <CAL9jLaamc2o7C8Lw3ZMzCUD-=F74bkyTSRCH-fA3xq5dve6eLg@mail.gmail.com> <etPan.57d1a436.41d16d8a.1a2d@virtualized.org>
From: Christopher Morrow <morrowc.lists@gmail.com>
Date: Thu, 8 Sep 2016 14:40:50 -0400
X-Google-Sender-Auth: klma0oTm_0rIKmFV5MVlUokZ2kY
Message-ID: <CAL9jLaaib98OBxxtAD3izibOO24RvAfWC6G1=i7Nzdc4dRY7Xg@mail.gmail.com>
To: David Conrad <drc@virtualized.org>
Content-Type: multipart/alternative; boundary=001a1140422481ca00053c035e58
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidr/sZ0jWIYeinwDw1Cdn2nr1cWwCUM>
Cc: sidr wg list <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, 08 Sep 2016 18:50:40 -0000

On Thu, Sep 8, 2016 at 1:47 PM, David Conrad <drc@virtualized.org> wrote:

> Chris,
>
> sure... I think sriram may cover this in his document about the decision
> processes which lead to where we are today.
>
> I think, one way to look at the document and situation is this:
>   o community folks for each RIR asked for RPKI to be supported
>   o RIR folk put in some development $$/effort to do that
>   o no single-root came forward
>
> This is NOT accurate. ICANN, as the IANA Internet Numbering Functions
> Operator, did come forward and we were informed there was no interest from
> the RIRs for the IANA Internet Numbering Functions Operator to participate
> in testing a single root RPKI service.
>

ok, then that's distressing :( we can re-address the situation from the
rirs north through I bet?


>   o to make the RPKI work, specifically for xfers, or one way wrt
> transfers, is to fake the root at each RIR.
>   o rpki progress can still be made until single-root arrives, and then
> some re-signing and probably rough work would have to happen to move under
> the single-root.
> [...]
> apologies for not being up on the chain-of-command, but this doesn't seem
> like it's enough... we've been waiting, what are the blockers? why can't
> this action move forward? (yes, politics, let's move that to anyother list
> I  suppose)
>
> I suspect if the Internet Numbering Community would be interested in a
> single root operated by the IANA Internet Numbering Functions Operator, all
> they need do is _ask_.
>

excellent, thanks for the clarifications.
-chris


> Regards,
>
> -drc
>
> (ICANN CTO, but speaking only for myself. Really)
>
> P.S. In my previous note, I forgot to include the above disclaimer. I am
> not speaking for ICANN here.
>