IETF Logo Mail Archive

Re: [eppext] rechartering

Rik Ribbers <rik.ribbers@sidn.nl> Wed, 29 July 2015 13:32 UTC

Return-Path: <rik.ribbers@sidn.nl>
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 B97331A0AF8 for <eppext@ietfa.amsl.com>; Wed, 29 Jul 2015 06:32:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.085
X-Spam-Level:
X-Spam-Status: No, score=0.085 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=no
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 X7qCHYcVSO71 for <eppext@ietfa.amsl.com>; Wed, 29 Jul 2015 06:32:40 -0700 (PDT)
Received: from arn2-kamx.sidn.nl (kamx.sidn.nl [IPv6:2a00:d78:0:147:94:198:152:69]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8A1C01A039F for <eppext@ietf.org>; Wed, 29 Jul 2015 06:32:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; d=sidn.nl; s=sidn-nl; c=relaxed/relaxed; h=from:to:subject:thread-topic:thread-index:date:message-id:references:in-reply-to:accept-language:content-language:x-ms-has-attach:x-ms-tnef-correlator:content-type:mime-version; bh=qe+7JxQig1Foyqgt4/M4MrrHKF9UErLbRYkejUqKmJA=; b=P77LYtWJMhLdVtUxPcL8m7xERtMVWHpuCIrhEzqTABV3Pye7POf9OKGnpprhh7wdT0OFSwdmL0v3ZAwwG6xYpR17bhIYR7Fn9n4VPOyeFz82miZpVUik8DuyMgrDsdpuLZc4E0zamcTYyV71btjtVTH/SymLTI23DmapNhf8yzw1wUl88PP0TyhmkNSm1DdybuVH7Rxkje7VU3MYupvxR3QsZI5IEtWabsPHUoDleEzqvNDGjqWoEgjvIoCZ0w0Fp6EyJyn3YgFQ5REjZCFzknxikn1szElrqNKus1IVPAlZeuQwMyPpd1B1/0eufOCatAwaNGEz4ZuQwqmpEzAXeg==
Received: from ka-mbx03.SIDN.local ([192.168.2.179]) by arn2-kamx.sidn.nl with ESMTP id t6TDWc7s020477-t6TDWc7u020477 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=CAFAIL); Wed, 29 Jul 2015 15:32:38 +0200
Received: from KAHUBCASN02.SIDN.local (192.168.2.76) by ka-mbx03.SIDN.local (192.168.2.179) with Microsoft SMTP Server (TLS) id 15.0.1076.9; Wed, 29 Jul 2015 15:32:39 +0200
Received: from KAMBX1.SIDN.local ([fe80::501d:affc:30a9:4edf]) by kahubcasn02 ([192.168.2.74]) with mapi id 14.03.0224.002; Wed, 29 Jul 2015 15:32:37 +0200
From: Rik Ribbers <rik.ribbers@sidn.nl>
To: Andrew Newton <andy@hxr.us>, "eppext@ietf.org" <eppext@ietf.org>
Thread-Topic: [eppext] rechartering
Thread-Index: AQHQyJkQdjJErQqm9UOi5gStcoR0rJ3yITpQgAAT7ICAAD+4DA==
Date: Wed, 29 Jul 2015 13:32:37 +0000
Message-ID: <8CDE735F-7330-4D1C-B5E5-0C502D0CA917@sidn.nl>
References: <CAAQiQRdBDKb8NF+d2COxTVCbx7MMtV4dsTRDSqBotq6XroHxBQ@mail.gmail.com> <C80127C588F8F2409E2B535AF968B768BA20AA85@kambx1.SIDN.local>, <CAAQiQRcdX_WHE-F7U=OW7qfANiX6fSuPB-9QmH+COPCra-V_0A@mail.gmail.com>
In-Reply-To: <CAAQiQRcdX_WHE-F7U=OW7qfANiX6fSuPB-9QmH+COPCra-V_0A@mail.gmail.com>
Accept-Language: nl-NL, en-US
Content-Language: nl-NL
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: multipart/alternative; boundary="_000_8CDE735F73304D1CB5E50C502D0CA917sidnnl_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/eppext/W_oBUXeCSSlmiizMpx8JBsvE7_o>
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 13:32:42 -0000

That makes sense. I forgot the openid draft.... And looking forward to the other extensions.

Thx for the update.

Gr
Rik

Verstuurd vanaf mijn iPhone

Op 29 jul. 2015 om 13:44 heeft Andrew Newton <andy@hxr.us<mailto:andy@hxr.us>> het volgende geschreven:

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<mailto: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<mailto:eppext-bounces@ietf.org>] On Behalf Of Andrew Newton
Sent: maandag 27 juli 2015 20:21
To: eppext@ietf.org<mailto: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

v2.23.0 | Report a Bug | By Email