Re: [eppext] New draft for keyrelay available

Maarten Bosteels <maarten.bosteels@dnsbelgium.be> Thu, 05 February 2015 14:58 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 C16D31A88DC for <eppext@ietfa.amsl.com>; Thu, 5 Feb 2015 06:58:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, 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 mxC_m8BJEiDT for <eppext@ietfa.amsl.com>; Thu, 5 Feb 2015 06:58:51 -0800 (PST)
Received: from emea01-am1-obe.outbound.protection.outlook.com (mail-am1on0789.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe00::789]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 723B91A8955 for <eppext@ietf.org>; Thu, 5 Feb 2015 06:57:37 -0800 (PST)
Received: from DB4PR06MB128.eurprd06.prod.outlook.com (10.242.155.27) by DB4PR06MB128.eurprd06.prod.outlook.com (10.242.155.27) with Microsoft SMTP Server (TLS) id 15.1.75.20; Thu, 5 Feb 2015 14:57:08 +0000
Received: from DB4PR06MB128.eurprd06.prod.outlook.com ([169.254.16.15]) by DB4PR06MB128.eurprd06.prod.outlook.com ([169.254.16.15]) with mapi id 15.01.0075.002; Thu, 5 Feb 2015 14:57:08 +0000
From: Maarten Bosteels <maarten.bosteels@dnsbelgium.be>
To: "Gould, James" <JGould@verisign.com>, "Hollenbeck, Scott" <shollenbeck@verisign.com>
Thread-Topic: [eppext] New draft for keyrelay available
Thread-Index: AdArSKQ+n3FmCyCWSq6l2+OWlzutM5ziBdxg40oDLgCAAB52gA==
Date: Thu, 5 Feb 2015 14:57:08 +0000
Message-ID: <46DE906F-03B9-4CBB-9CC9-885B15EDCA01@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> <AF040383-7DED-4DDA-A52A-F40978697DF9@dnsbelgium.be> <C80127C588F8F2409E2B535AF968B768B9285C2F@kambx2.SIDN.local> <831693C2CDA2E849A7D7A712B24E257F49F33387@BRN1WNEXMBX01.vcorp.ad.vrsn.com> <46F2F7EA-7FD4-4D47-B80D-CCC795277512@verisign.com> <831693C2CDA2E849A7D7A712B24E257F49F3353E@BRN1WNEXMBX01.vcorp.ad.vrsn.com> <ABCBA930-3045-438C-A526-B6B824390048@verisign.com> <831693C2CDA2E849A7D7A712B24E257F49F338CE@BRN1WNEXMBX01.vcorp.ad.vrsn.com> <C80127C588F8F2409E2B535AF968B768B928BC13@kambx2.SIDN.local> <831693C2CDA2E849A7D7A712B24E257F49F33CD7@BRN1WNEXMBX01.vcorp.ad.vrsn.com> <9DA4482A-EF0F-4D66-A941-9472F16403E3@verisign.com> <831693C2CDA2E849A7D7A712B24E257F49F33D6D@BRN1WNEXMBX01.vcorp.ad.vrsn.com> <831693C2CDA2E849A7D7A712B24E257F49F33F4C@BRN1WNEXMBX01.vcorp.ad.vrsn.com> <BF69A00E-EBD5-435A-8BF5-1C77A44E4545@verisign.com> <831693C2CDA2E849A7D7A712B24E257F49F34147@BRN1WNEXMBX01.vcorp.ad.vrsn.com> <AF85EB99-3250-4BBD-9106-59400D8AF911@antoin.nl> <831693C2CDA2E849A7D7A712B24E257F49F3AFB9@BRN1WNEXMBX01.vcorp.ad.vrsn.com> <ECD1F4F1-B5E7-4667-90CC-454204CCB065@verisign.com>
In-Reply-To: <ECD1F4F1-B5E7-4667-90CC-454204CCB065@verisign.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [77.67.63.234]
authentication-results: verisign.com; dkim=none (message not signed) header.d=none;
x-microsoft-antispam: BCL:0;PCL:0;RULEID:;SRVR:DB4PR06MB128;
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0;PCL:0;RULEID:;SRVR:DB4PR06MB128;
x-forefront-prvs: 0478C23FE0
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(24454002)(377454003)(19617315012)(2656002)(40100003)(18206015028)(33656002)(102836002)(122556002)(16601075003)(87936001)(16236675004)(83716003)(15975445007)(93886004)(66066001)(86362001)(2900100001)(82746002)(19580405001)(62966003)(77156002)(19580395003)(36756003)(46102003)(92566002)(2950100001)(74482002)(54356999)(50986999)(76176999)(17760045003)(99936001)(104396002); DIR:OUT; SFP:1102; SCL:1; SRVR:DB4PR06MB128; H:DB4PR06MB128.eurprd06.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en;
Content-Type: multipart/mixed; boundary="_004_46DE906F03B94CBB9CC9885B15EDCA01dnsbelgiumbe_"
MIME-Version: 1.0
X-OriginatorOrg: dnsbelgium.be
X-MS-Exchange-CrossTenant-originalarrivaltime: 05 Feb 2015 14:57:08.2706 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 695195de-c0cb-4478-9204-2a861e60e59c
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB4PR06MB128
Archived-At: <http://mailarchive.ietf.org/arch/msg/eppext/_kWa348xVoxXT1DGRXSaHA1Z7xQ>
Cc: Rik Ribbers <rik.ribbers@sidn.nl>, Miek Gieben <miek@miek.nl>, Maarten Bosteels <maarten.bosteels@dnsbelgium.be>, "eppext@ietf.org" <eppext@ietf.org>, Antoin Verschuren <antoin@antoin.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: Thu, 05 Feb 2015 14:58:55 -0000

I completely agree with James' argumentation and recommendation.

Best regards,
Maarten

From: <Gould>, James <JGould@verisign.com<mailto:JGould@verisign.com>>
Date: Thursday 5 February 2015 15:08
To: "Hollenbeck, Scott" <shollenbeck@verisign.com<mailto:shollenbeck@verisign.com>>
Cc: Antoin Verschuren <antoin@antoin.nl<mailto:antoin@antoin.nl>>, Rik Ribbers <rik.ribbers@sidn.nl<mailto:rik.ribbers@sidn.nl>>, Miek Gieben <miek@miek.nl<mailto:miek@miek.nl>>, Maarten Bosteels <maarten.bosteels@dnsbelgium.be<mailto:maarten.bosteels@dnsbelgium.be>>, "eppext@ietf.org<mailto:eppext@ietf.org>" <eppext@ietf.org<mailto:eppext@ietf.org>>
Subject: Re: [eppext] New draft for keyrelay available

Scott,

I believe that RFC 5730 is not limited to a certain class of objects that can be provisioned.  A create of a transient, immutable message object is a transform command and the use of a poll response supports a query command.  In this case the server is being used to support the passing of messages between two clients.  There is no idempotency issue between the clients and the server since the object is immutable, but there is an idempotency issue between the participating clients that could be addressed by including a unique relay identifier in the relay message that the consuming client can simply verify against previously applied relay identifiers ahead of applying the relay message.  There could be other use cases were clients need to communicate through the server using a transient object message pattern.

My recommendation to the authors of the Key Relay Extension is to make the draft an object mapping with a create transform command, a the poll response, and with a unique relay identifier to address the end-to-end idempotency concern.


—


JG


[cid:77031CC3-BE7A-4188-A95F-D23115A30A4D@vcorp.ad.vrsn.com]

James Gould
Distinguished Engineer
jgould@Verisign.com

703-948-3271
12061 Bluemont Way
Reston, VA 20190

VerisignInc.com<http://VerisignInc.com>

On Feb 5, 2015, at 8:16 AM, Hollenbeck, Scott <shollenbeck@verisign.com<mailto:shollenbeck@verisign.com>> wrote:

-----Original Message-----
From: Antoin Verschuren [mailto:antoin@antoin.nl]
Sent: Thursday, February 05, 2015 7:45 AM
To: Hollenbeck, Scott
Cc: Gould, James; Rik Ribbers; Miek Gieben; Maarten Bosteels;
eppext@ietf.org<mailto:eppext@ietf.org>
Subject: Re: [eppext] New draft for keyrelay available

Scott,

What do you considder a duplication?

The exact same message being sent or received more than once. This introduces a risk of inconsistency between client and server if there isn't a way to provide command idempotency, which is one of the reasons I prefer an approach that involves creating a transient object. Note that Section 2 of RFC 5730 includes this statement about EPP commands:

"EPP commands fall into three categories: session management commands, query commands, and object transform commands."

Which of these categories does the <relay> command fall into? The draft describes it as a "transient" command, and there's no mention of "transient" commands in 5730.

Scott