IETF Logo Mail Archive

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

Marc Groeneweg <Marc.Groeneweg@sidn.nl> Thu, 10 November 2016 08:01 UTC

Return-Path: <Marc.Groeneweg@sidn.nl>
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 63A05129451 for <regext@ietfa.amsl.com>; Thu, 10 Nov 2016 00:01:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.797
X-Spam-Level:
X-Spam-Status: No, score=-5.797 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-1.497, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=sidn.nl
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 SU2IwxKWnoAd for <regext@ietfa.amsl.com>; Thu, 10 Nov 2016 00:01:48 -0800 (PST)
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 3347012943C for <regext@ietf.org>; Thu, 10 Nov 2016 00:01:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; d=sidn.nl; 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:user-agent:x-ms-exchange-messagesentrepresentingtype:x-ms-exchange-transport-fromentityheader:x-originating-ip:content-type:mime-version; bh=0yW9nx17sol/W77GTYC0fL5Lh/bZEBgn4MozUi8HSeM=; b=HhZvY1qfDRqZ8qHs83uMeV7WZQyVnX/e5X3nuRcwvOLvggAFs5u9Idog+DETqWCKbSu+x0xvi2k+f5x1zV8sQdHXrrkFZG9DerV0GyQ/daIaa3NQHiQFIZFVyPBb1RD/7PuaNH0WXj90mEp/UPuPyTFXevNtIG8qcUa4h+TxHusm33BGtZDY5dl+w17bT+NaSHkTNg+KhZ6PaNr51lKbTh4GIpl1GZwfKxlycZpggs9XS1on4c6/QCH7mTqdTfVR/n5/A5I+aOilbiC4YdwKeqF8VJbx9qDDroa+eNybE3KBCaTbQ9P1jQt6kfOKu3QD03D4t96XnqEEWwJEVvYiFw==
Received: from ka-mbx02.SIDN.local ([192.168.2.178]) by arn2-kamx.sidn.nl with ESMTP id uAA81h1A016306-uAA81h1C016306 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=CAFAIL); Thu, 10 Nov 2016 09:01:43 +0100
Received: from ka-mbx01.SIDN.local (192.168.2.177) by ka-mbx02.SIDN.local (192.168.2.178) with Microsoft SMTP Server (TLS) id 15.0.1130.7; Thu, 10 Nov 2016 09:01:42 +0100
Received: from ka-mbx01.SIDN.local ([fe80::e051:e184:7a9f:b09d]) by ka-mbx01.SIDN.local ([fe80::e051:e184:7a9f:b09d%13]) with mapi id 15.00.1130.005; Thu, 10 Nov 2016 09:01:42 +0100
From: Marc Groeneweg <Marc.Groeneweg@sidn.nl>
To: Rik Ribbers <rik.ribbers@sidn.nl>, Antoin Verschuren <ietf@antoin.nl>
Thread-Topic: [regext] draft-ietf-eppext-keyrelay unreasonably stuck on IPR?
Thread-Index: AQHSOc8YkZkE5rYWeEKyIArlNp5Ma6DPa32AgADpUgCAAC3qAIAAFsYAgABVqICAANjuAIAAFaaA
Date: Thu, 10 Nov 2016 08:01:42 +0000
Message-ID: <1F8381BD-3E2F-4167-9511-9015F57A09BD@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>
In-Reply-To: <D4F44DCF-8789-4139-A006-2AA78CBEC082@sidn.nl>
Accept-Language: en-US
Content-Language: en-GB
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/f.1b.0.161010
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [192.168.7.24]
Content-Type: multipart/alternative; boundary="_000_1F8381BD3E2F416795119015F57A09BDsidnnl_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/jITXjPrTiz0QylIoXOXpBUPtTj0>
Cc: Job Snijders <job@instituut.net>, "alissa@cooperw.in" <alissa@cooperw.in>, "Livesay, Paul" <plivesay@verisign.com>, Scott Hollenbeck <shollenbeck@verisign.com>, "regext@ietf.org" <regext@ietf.org>, Stephen Farrell <stephen.farrell@cs.tcd.ie>
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 08:01:50 -0000

+1 I agree. It seems there is a rough consensus formed by the overwhelming silence within this WG regarding this keyrelay draft. Let’s move on!

From: regext <regext-bounces@ietf.org> on behalf of Rik Ribbers <rik.ribbers@sidn.nl>
Date: Thursday, 10 November 2016 at 08:44
To: Antoin Verschuren <ietf@antoin.nl>
Cc: Job Snijders <job@instituut.net>, "alissa@cooperw.in" <alissa@cooperw.in>, Scott Hollenbeck <shollenbeck@verisign.com>, "Livesay, Paul" <plivesay@verisign.com>, "regext@ietf.org" <regext@ietf.org>, Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: [regext] draft-ietf-eppext-keyrelay unreasonably stuck on IPR?

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<mailto: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.

Gr,
Rik

v2.23.0 | Report a Bug | By Email