Re: [eppext] draft-ietf-eppext-keyrelay seems stuck

Rik Ribbers <> Thu, 04 February 2016 15:44 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 90E4C1B31D1 for <>; Thu, 4 Feb 2016 07:44:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: 0.094
X-Spam-Status: No, score=0.094 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, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id uldmaJatGoM5 for <>; Thu, 4 Feb 2016 07:44:17 -0800 (PST)
Received: from ( [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 (Postfix) with ESMTPS id 477111B31B7 for <>; Thu, 4 Feb 2016 07:44:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt;; s=sidn-nl; c=relaxed/relaxed; h=from:to:cc:subject:thread-topic:thread-index:date:message-id:references:in-reply-to:accept-language:content-language:x-ms-has-attach:x-ms-tnef-correlator:x-mailer:x-ms-exchange-messagesentrepresentingtype:x-ms-exchange-transport-fromentityheader:x-originating-ip:content-type:mime-version; bh=yjjd6NwRUz69codZksvKCXuSENImVNtKfgX7vBYJ4qo=; b=B9x2ClrLpLOWLGutfE+xGPFT/GoqIYBaaWLHjBpRm5CdWv2zQQ8TcDli+A1KoaRXYbpSiqXB+YMUIdaUvzO08raWuf1F1G/NzsJ+mnjsk6cZBS7tQDKyuypfSSZ7KUkhmIbMK0n6lqlwnPw4C4vCmxGQ6EuPVyB5k9V2+kDmTxoVYfYsL7rmebDvgz3gB9TJhnHsQ/x2rrltIgcvBKPRU7RKfeeFW8HDwpH8E9Aj5rwMqGQ/mITRGky5C/UNGVjjXM7tFEklO8HEteRyy8aNXRIViDy/+tP3FL7LEh3EIfoZml6dlS8IxP5GGGMudEOg7P90OzVMYCd048kGDPvR2w==
Received: from ka-mbx01.SIDN.local ([]) by with ESMTP id u14FiF1M000766-u14FiF1O000766 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=CAFAIL); Thu, 4 Feb 2016 16:44:15 +0100
Received: from ka-mbx02.SIDN.local ( by ka-mbx01.SIDN.local ( with Microsoft SMTP Server (TLS) id 15.0.1130.7; Thu, 4 Feb 2016 16:44:18 +0100
Received: from ka-mbx02.SIDN.local ([fe80::9855:369a:1ca4:6549]) by ka-mbx02.SIDN.local ([fe80::9855:369a:1ca4:6549%13]) with mapi id 15.00.1130.005; Thu, 4 Feb 2016 16:44:18 +0100
From: Rik Ribbers <>
To: Paul Hoffman <>, Scott Hollenbeck <>
Thread-Topic: [eppext] draft-ietf-eppext-keyrelay seems stuck
Thread-Index: AQHRX14dumTQ4s2FJEa9Vp2md1vQfp8b9k2A
Date: Thu, 04 Feb 2016 15:44:18 +0000
Message-ID: <>
References: <>
In-Reply-To: <>
Accept-Language: nl-NL, en-US
Content-Language: en-US
x-mailer: Apple Mail (2.3112)
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_23799EAB5C924C02AC4B85DA879EBBB5sidnnl_"
MIME-Version: 1.0
Archived-At: <>
Cc: "" <>
Subject: Re: [eppext] draft-ietf-eppext-keyrelay seems stuck
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: EPPEXT <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 04 Feb 2016 15:44:19 -0000

Hello Paul,

Quoting from the IESG evaluation record:

The IPR declaration says that license terms will be available
"later." As things stand, I don't understand how the WG can have
made an informed decision in that case. I looked at the archive
and saw essentially no discussion, other than the announcement.

The document is currently waiting for an update of the IPR disclosure with the license terms, before it can move along. Depending on the updated text (that needs to be provided by Verisign) the next steps need to be determined.

Scott has indicated that the legal department of Verisign will update the IPR disclosure a.s.a.p.

@Scott: Any progress to report?

Hope this clarifies things.


On 04 Feb 2016, at 16:07, Paul Hoffman <<>> wrote:

Greetings. According to <>, this draft has been stuck with a significant DISCUSS for well over a month. How can the WG help get