Re: [eppext] rechartering

Andrew Newton <andy@hxr.us> Wed, 29 July 2015 11:44 UTC

Return-Path: <andy@hxr.us>
X-Original-To: eppext@ietfa.amsl.com
Delivered-To: eppext@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EB1091A87C7 for <eppext@ietfa.amsl.com>; Wed, 29 Jul 2015 04:44:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level:
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
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 Ktu3nlg88yCC for <eppext@ietfa.amsl.com>; Wed, 29 Jul 2015 04:44:35 -0700 (PDT)
Received: from mail-wi0-f169.google.com (mail-wi0-f169.google.com [209.85.212.169]) (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 F11DE1A87C5 for <eppext@ietf.org>; Wed, 29 Jul 2015 04:44:34 -0700 (PDT)
Received: by wibxm9 with SMTP id xm9so197217895wib.0 for <eppext@ietf.org>; Wed, 29 Jul 2015 04:44:33 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=FTEa0k9yFbayQsjVkkD580m0zovykLQ+Q2sm3dhc45Q=; b=T1tGicUjUI/N2OHm2vf0dYVUfYom30FX71I83r8+AeeZu3wg/n2ZQaahyIY2K5duLL i3hUyKjorxsJEj1NdHXOqOYjJMfaJU9CO3/4wZzUJ5olCnyTAn1IyoUPtwbQgJxjFoMl BVzpMKgGWrxcoffy/8Q2MJDEHRCTRNzd1EDLSjuqSdCzYTwCNmmQ5HELjRP2IX1FbE0A LnhewQRLNvr+e+D7BNzx6cGPX8/kEHA6wxbtksfxUmKTnWUI0HhrZoETzzKAumAZq4gv rP/uTiEH0LSymLGHmh71rGICjT7lDy/e3jZkdsZD4M7td7srlbV5dbVevYNOTMrFwldQ 4L/A==
X-Gm-Message-State: ALoCoQlmFBjQo4HWrX1Ud6KvxWx5L6tGblWpXvx2I6MRvbzO2MjrdlFGXeXCNuCAGyGgnoPMdkl/
MIME-Version: 1.0
X-Received: by 10.180.96.1 with SMTP id do1mr15692350wib.37.1438170273654; Wed, 29 Jul 2015 04:44:33 -0700 (PDT)
Received: by 10.194.249.99 with HTTP; Wed, 29 Jul 2015 04:44:33 -0700 (PDT)
X-Originating-IP: [96.241.188.13]
In-Reply-To: <C80127C588F8F2409E2B535AF968B768BA20AA85@kambx1.SIDN.local>
References: <CAAQiQRdBDKb8NF+d2COxTVCbx7MMtV4dsTRDSqBotq6XroHxBQ@mail.gmail.com> <C80127C588F8F2409E2B535AF968B768BA20AA85@kambx1.SIDN.local>
Date: Wed, 29 Jul 2015 07:44:33 -0400
Message-ID: <CAAQiQRcdX_WHE-F7U=OW7qfANiX6fSuPB-9QmH+COPCra-V_0A@mail.gmail.com>
From: Andrew Newton <andy@hxr.us>
To: Rik Ribbers <rik.ribbers@sidn.nl>
Content-Type: multipart/alternative; boundary="f46d04447fc549c18a051c021cca"
Archived-At: <http://mailarchive.ietf.org/arch/msg/eppext/RpwETIYLl3f_-6eDG7XurMVlg7o>
Cc: "eppext@ietf.org" <eppext@ietf.org>
Subject: Re: [eppext] rechartering
X-BeenThere: eppext@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: EPPEXT <eppext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/eppext>, <mailto:eppext-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/eppext/>
List-Post: <mailto:eppext@ietf.org>
List-Help: <mailto:eppext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eppext>, <mailto:eppext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jul 2015 11:44:37 -0000

Hi Rik,

Scott has an interesting RDAP extension proposal
in draft-hollenbeck-weirds-rdap-openid.

Additionally we need an Informational RFC on guidelines for extending RDAP,
similar to the one for EPP. And there are several extensions being talked
about.

-andy

On Wed, Jul 29, 2015 at 4:44 AM, Rik Ribbers <rik.ribbers@sidn.nl> wrote:

>  Hello Andrew and others,
>
>
>
> I am not completely convinced it is a good idea, but I do not have any
> objection to combine the work as the interested people are mostly the same.
>
>
>
> The overlap between EPP an RDAP is mainly the data that is send using a
> different protocol (and a different purpose). Another thing is that I am
> not aware of any work that is being done for RDAP other than the EPP status
> mapping draft from James Gould.
>
>
>
> But I can imagine there will we work on extensions for RDAP in the future
> as more parties are going to implement it.
>
>
>
> Gr,
>
> Rik
>
>
>
>
>
> *From:* EppExt [mailto:eppext-bounces@ietf.org] *On Behalf Of *Andrew
> Newton
> *Sent:* maandag 27 juli 2015 20:21
> *To:* eppext@ietf.org
> *Subject:* [eppext] rechartering
>
>
>
> All,
>
>
>
> I'd like to offer another idea for the rechartering of this working group.
> Instead of focusing exclusively on EPP extensions, would it be better if we
> rechartered to focus on protocol issues of Internet registries... more
> specifically EPP and RDAP.
>
>
>
> Given that the constituencies for both have considerable overlap, and
> there is already at least one draft covering the mapping between EPP and
> RDAP and that there will likely be future drafts where the inputs of EPP
> and the outputs of RDAP are correlated, this seems like an easier way
> forward.
>
>
>
> I spoke privately with Scott, Barry, and Pete (the AD behind the
> chartering of both EPPEXT and WEIRDS) just to see if I wasn't barking madd,
> and they each thought it makes sense.
>
>
>
> What are your thoughts and comments about such an approach?
>
>
>
> -andy
>