IETF Logo Mail Archive

Re: [regext] draft-ietf-eppext-keyrelay unreasonably stuck on IPR?

Alexey Melnikov <aamelnikov@fastmail.fm> Thu, 10 November 2016 10:42 UTC

Return-Path: <aamelnikov@fastmail.fm>
X-Original-To: regext@ietfa.amsl.com
Delivered-To: regext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 88981129650 for <regext@ietfa.amsl.com>; Thu, 10 Nov 2016 02:42:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.719
X-Spam-Level:
X-Spam-Status: No, score=-2.719 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=fastmail.fm header.b=Vp0EOsXi; dkim=pass (1024-bit key) header.d=messagingengine.com header.b=ts95lWCP
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 LhmW2vKq1AKE for <regext@ietfa.amsl.com>; Thu, 10 Nov 2016 02:42:38 -0800 (PST)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4BE0412958A for <regext@ietf.org>; Thu, 10 Nov 2016 02:42:38 -0800 (PST)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id A3E0E20663 for <regext@ietf.org>; Thu, 10 Nov 2016 05:42:37 -0500 (EST)
Received: from web5 ([10.202.2.215]) by compute1.internal (MEProxy); Thu, 10 Nov 2016 05:42:37 -0500
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=fastmail.fm; h= content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=mesmtp; bh=ZedROjarqpErILkCU/3aXRfGD6 Y=; b=Vp0EOsXizt5GKXxigWOWuDtDPLyLJ1nbxj/3fGqo3FjN1Ou5FT72D7H8CN tUNCFOxrI31iAsRUYktY7ekOIs5o9gODWYhR1RqspdArS+NBE3qeRs2Bn1UcjplC ljYC03pQR6n7mmfbUaKgG0pMDllguYQDU402zvcT1ONooa2aU=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=smtpout; bh=Ze dROjarqpErILkCU/3aXRfGD6Y=; b=ts95lWCPx4WJmBMv6toU4I3I1cRj0vPgDI 5UVUut77CoV8heQ1kPVWPUnlI2P0NtvawA1PzDblJicpBo9yYVUphlnNSvys9Vxr +s0Pcg4qsHBGXA+8Y5k9OXRExDh9ojEdP+Sa+y86ZnmPyuPezoKTH+hD+h9/0zOy NQR9iWwVk=
X-ME-Sender: <xms:HU8kWF-j6IQlYHPNFFuUB3n9wIqoJa0hb-OHO39ZTJ0c_zZqfhN0tQ>
Received: by mailuser.nyi.internal (Postfix, from userid 99) id 7092F5A67B; Thu, 10 Nov 2016 05:42:37 -0500 (EST)
Message-Id: <1478774557.2543370.783360089.2B9C66F5@webmail.messagingengine.com>
From: Alexey Melnikov <aamelnikov@fastmail.fm>
To: regext@ietf.org
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: multipart/alternative; boundary="_----------=_147877455725433700"; charset="utf-8"
X-Mailer: MessagingEngine.com Webmail Interface - ajax-d68eb56e
Date: Thu, 10 Nov 2016 10:42:37 +0000
In-Reply-To: <D4F44DCF-8789-4139-A006-2AA78CBEC082@sidn.nl>
References: <20161108144742.GH2473@Hanna.local> <831693C2CDA2E849A7D7A712B24E257F4A4BC33E@BRN1WNEXMBX01.vcorp.ad.vrsn.com> <20161109093524.GC89276@Vurt.local> <831693C2CDA2E849A7D7A712B24E257F4A4BCC19@BRN1WNEXMBX01.vcorp.ad.vrsn.com> <20161109134114.GK2473@Hanna.local> <C851A2CF-B946-4E3E-8799-585851CDEB77@antoin.nl> <D4F44DCF-8789-4139-A006-2AA78CBEC082@sidn.nl>
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/-iOeyV9xHFbc2qkRUG0aYERlPrM>
Subject: Re: [regext] draft-ietf-eppext-keyrelay unreasonably stuck on IPR?
X-BeenThere: regext@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Registration Protocols Extensions <regext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/regext>, <mailto:regext-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/regext/>
List-Post: <mailto:regext@ietf.org>
List-Help: <mailto:regext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/regext>, <mailto:regext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Nov 2016 10:42:39 -0000

Hi,

On Thu, Nov 10, 2016, at 07:44 AM, Rik Ribbers wrote:
> First of all thanks Antoin for your excellent reply.  lots of +1
> in there.
>
>> On 9 Nov 2016, at 19:47, Antoin Verschuren <ietf@antoin.nl> wrote:
>>
>> Jim has asked for this before, with little to no response to call
>> consensus to have this draft proceed, so I would like to ask you
>> again to state your opinion on this mailinglist so Jim can summarize
>> them in a response to the IESG.
> We all know what is going to happen now… we have been waiting for a
> response for almost a year now and nothing happens in the WG. So the
> document is not only stalled on a IPR-disclosure without licensing
> details but also on a WG that is not willing to discuss this.
>
> So I propose an option 3: Describe the situation to the IESG and from
> this
> (https://mailarchive.ietf.org/arch/msg/regext/wHlAx8OrF_r5DiSWhr8LuMk860g_)
> mail conversation Stephen will (unhappy with the crappy situation)
> clears his DISCUSS. At least this gets the document of the plate from
> the WG and takes the discussion to the IESG where the document and the
> IPR disclosure can be discussed in a broader context then just
> keyrelay and the REGEXT WG.

The main problem with this option is that IESG still needs feedback from
the WG about what outcome the WG prefers. IESG is unlikely to make a
decision to "just publish" on its own.

Alexey (not speaking for the whole IESG, but just my gut feeling).

v2.23.0 | Report a Bug | By Email