Re: [eppext] New draft for keyrelay available
Maarten Bosteels <maarten.bosteels@dnsbelgium.be> Mon, 19 January 2015 11:31 UTC
Return-Path: <maarten.bosteels@dnsbelgium.be>
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 2D42E1B2A2D
for <eppext@ietfa.amsl.com>; Mon, 19 Jan 2015 03:31:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001]
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 X-cPQvPXTwbm for <eppext@ietfa.amsl.com>;
Mon, 19 Jan 2015 03:31:26 -0800 (PST)
Received: from emea01-am1-obe.outbound.protection.outlook.com
(mail-am1on0700.outbound.protection.outlook.com
[IPv6:2a01:111:f400:fe00::700])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits))
(No client certificate requested)
by ietfa.amsl.com (Postfix) with ESMTPS id 80D0E1AD4A1
for <eppext@ietf.org>; Mon, 19 Jan 2015 03:31:25 -0800 (PST)
Received: from DB4PR06MB128.eurprd06.prod.outlook.com (10.242.155.27) by
DB4PR06MB126.eurprd06.prod.outlook.com (10.242.155.21) with Microsoft SMTP
Server (TLS) id 15.1.59.20; Mon, 19 Jan 2015 11:26:16 +0000
Received: from DB4PR06MB128.eurprd06.prod.outlook.com ([169.254.16.245]) by
DB4PR06MB128.eurprd06.prod.outlook.com ([169.254.16.245]) with mapi id
15.01.0059.007; Mon, 19 Jan 2015 11:26:16 +0000
From: Maarten Bosteels <maarten.bosteels@dnsbelgium.be>
To: Miek Gieben <miek@miek.nl>, "Gould, James" <JGould@verisign.com>,
"eppext@ietf.org" <eppext@ietf.org>
Thread-Topic: [eppext] New draft for keyrelay available
Thread-Index: AdArSKQ+n3FmCyCWSq6l2+OWlzutMwA+eoEAALUP4qAAEcW9gAEbw5wAAAWKvYA=
Date: Mon, 19 Jan 2015 11:26:16 +0000
Message-ID: <AF040383-7DED-4DDA-A52A-F40978697DF9@dnsbelgium.be>
References: <C80127C588F8F2409E2B535AF968B768B927CDA8@kambx2.SIDN.local>
<0ED7237B-F4E8-45D7-971F-1625350DB0FC@verisign.com>
<C80127C588F8F2409E2B535AF968B768B9280B52@kambx2.SIDN.local>
<472EF001-1A03-4C50-A7DB-3D6B766B3BA8@verisign.com>
<20150119094734.GA27180@miek.nl>
In-Reply-To: <20150119094734.GA27180@miek.nl>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [77.67.63.234]
authentication-results: spf=none (sender IP is )
smtp.mailfrom=maarten.bosteels@dnsbelgium.be;
x-dmarcaction-test: None
x-microsoft-antispam: BCL:0;PCL:0;RULEID:(3005004);SRVR:DB4PR06MB126;
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0;PCL:0;RULEID:;SRVR:DB4PR06MB126;
x-forefront-prvs: 046164D5C4
x-forefront-antispam-report: SFV:NSPM;
SFS:(10019020)(6009001)(189002)(479174004)(24454002)(51704005)(53754006)(199003)(87936001)(102836002)(15975445007)(2950100001)(2900100001)(83716003)(40100003)(68736005)(2501002)(2656002)(19580405001)(46102003)(97736003)(64706001)(62966003)(74482002)(122556002)(77156002)(66066001)(36756003)(101416001)(33656002)(86362001)(93886004)(105586002)(54356999)(76176999)(50986999)(82746002)(19580395003)(92566002)(106356001)(104396002);
DIR:OUT; SFP:1102; SCL:1; SRVR:DB4PR06MB126;
H:DB4PR06MB128.eurprd06.prod.outlook.com; FPR:; SPF:None; MLV:sfv;
PTR:InfoNoRecords; MX:1; A:1; LANG:en;
received-spf: None (protection.outlook.com: dnsbelgium.be does not designate
permitted sender hosts)
Content-Type: text/plain; charset="utf-8"
Content-ID: <DFCF1F304D1BFA45A27C974B81D35369@eurprd06.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: dnsbelgium.be
X-MS-Exchange-CrossTenant-originalarrivaltime: 19 Jan 2015 11:26:16.2766 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 695195de-c0cb-4478-9204-2a861e60e59c
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB4PR06MB126
Archived-At: <http://mailarchive.ietf.org/arch/msg/eppext/Olaqfe92O4V2RiTwQaamSWPkEHY>
Cc: Rik Ribbers <rik.ribbers@sidn.nl>
Subject: Re: [eppext] New draft for keyrelay available
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: <http://www.ietf.org/mail-archive/web/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: Mon, 19 Jan 2015 11:31:29 -0000
Hi all, I agree with James that creating a Key Relay Object Mapping instead of mixing of a protocol extension for the command and an object mapping for the poll response seems simpler. And I am all for simpler ;-) At DNS Belgium we have in the past created extra verbs using a protocol extension, but in most cases it proved afterwards to be more appropriate to use an plain command/response extension or a new Object Mapping. Like Miek, I also assume not many people care about this issue. I think for the following reasons: A) Both options will work: it's a very technical choice with little impact on the actual users B) I assume not many registries (and RAR's) are considering implementing key relay in the near future. But I'd love to be proved wrong here ! Miek or Rik, is the key-relay functionality implemented by SIDN actively used by many registrars ? On both sides of the transfer/relay ? Regards Maarten On 19/01/15 09:47, "Miek Gieben" <miek@miek.nl> wrote: >[ Quoting <JGould@verisign.com> in "Re: [eppext] New draft for >keyrelay..." ] >>All, >> >>I agree with Rik that more from the WG must weigh in on this. I believe >>Rik >>and I understood fully each others perspective, but we simply don’t >>agree. >>Please take some time to review the two different approaches and reply >>to the >>list with your opinion. > >I didn't see any replies, so I'm assuming not that many people care about >this >issue. > >As one of the draft authors I think we should leave the draft in its >current >state. > >/Miek > >-- >Miek Gieben > >_______________________________________________ >EppExt mailing list >EppExt@ietf.org >https://www.ietf.org/mailman/listinfo/eppext
- [eppext] New draft for keyrelay available Rik Ribbers
- Re: [eppext] New draft for keyrelay available Gould, James
- Re: [eppext] New draft for keyrelay available Rik Ribbers
- Re: [eppext] New draft for keyrelay available Gould, James
- Re: [eppext] New draft for keyrelay available Miek Gieben
- Re: [eppext] New draft for keyrelay available Maarten Bosteels
- Re: [eppext] New draft for keyrelay available Rik Ribbers
- Re: [eppext] New draft for keyrelay available Ulrich Wisser
- Re: [eppext] New draft for keyrelay available Rik Ribbers
- Re: [eppext] New draft for keyrelay available Hollenbeck, Scott
- Re: [eppext] New draft for keyrelay available Gould, James
- Re: [eppext] New draft for keyrelay available Hollenbeck, Scott
- Re: [eppext] New draft for keyrelay available Gould, James
- Re: [eppext] New draft for keyrelay available Hollenbeck, Scott
- Re: [eppext] New draft for keyrelay available Rik Ribbers
- Re: [eppext] New draft for keyrelay available Gould, James
- Re: [eppext] New draft for keyrelay available Hollenbeck, Scott
- Re: [eppext] New draft for keyrelay available Hollenbeck, Scott
- Re: [eppext] New draft for keyrelay available Gould, James
- Re: [eppext] New draft for keyrelay available Rik Ribbers
- Re: [eppext] New draft for keyrelay available Hollenbeck, Scott
- Re: [eppext] New draft for keyrelay available Rik Ribbers
- Re: [eppext] New draft for keyrelay available Gould, James
- Re: [eppext] New draft for keyrelay available Hollenbeck, Scott
- Re: [eppext] New draft for keyrelay available Gould, James
- Re: [eppext] New draft for keyrelay available Santosh Kalsangrah
- Re: [eppext] New draft for keyrelay available Hollenbeck, Scott
- [eppext] FW: New draft for keyrelay available Rik Ribbers
- Re: [eppext] New draft for keyrelay available Hollenbeck, Scott
- Re: [eppext] New draft for keyrelay available Gould, James
- Re: [eppext] New draft for keyrelay available Antoin Verschuren
- Re: [eppext] New draft for keyrelay available Antoin Verschuren
- Re: [eppext] New draft for keyrelay available Maarten Bosteels
- Re: [eppext] New draft for keyrelay available Gould, James
- Re: [eppext] New draft for keyrelay available Hollenbeck, Scott
- Re: [eppext] New draft for keyrelay available Antoin Verschuren
- Re: [eppext] New draft for keyrelay available Gould, James