Re: [regext] draft-ietf-eppext-keyrelay unreasonably stuck on IPR?
S Moonesamy <sm+ietf@elandsys.com> Tue, 08 November 2016 20:18 UTC
Return-Path: <sm@elandsys.com>
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 1670A129DEA; Tue, 8 Nov 2016 12:18:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.287
X-Spam-Level:
X-Spam-Status: No, score=-3.287 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RP_MATCHES_RCVD=-1.497, T_DKIM_INVALID=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=opendkim.org header.b=uOZJWibh; dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.com header.b=R31AC2d3
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 wtYP_BPhRI34; Tue, 8 Nov 2016 12:18:12 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8EF671295A7; Tue, 8 Nov 2016 12:18:12 -0800 (PST)
Received: from SUBMAN.elandsys.com ([197.227.86.223]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id uA8KHsx1014078 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 8 Nov 2016 12:18:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1478636289; x=1478722689; bh=r3TG5ngZ/uy203pQMj5B6Z2OzH0VfHAdFWkdlUG8yhw=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=uOZJWibh5PyPcX7yt8q7aA0h40jst46lEXANH3AmLMOjBh7auA+TEeCChbPvWbsYs CIYi+nakAQBxSnEnq6CGheqhJkNPLnoSZzchrgeJP26qgVjkm0KP8Glpg3Q8DiTTiy n+FEL23aQw4i6A94wBHNyTB09D6oOojNIegF1MbI=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1478636289; x=1478722689; i=@elandsys.com; bh=r3TG5ngZ/uy203pQMj5B6Z2OzH0VfHAdFWkdlUG8yhw=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=R31AC2d3d5mk4kwDbWt5cZL97NFrS55tsu5ukmmk8wROkzFDCzt9pLOdyME+L49rV Ba3QZIwKEuYG1WExckt8gEQtQVICpvIYqbt/2vcWmj4X+Z+/z9PREbzDNijfLX7VHP STxtWctoY+mYXSRXPxR9HngDFSeXp1HI8HRd/1jU=
Message-Id: <6.2.5.6.2.20161108115446.0bb33b90@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 08 Nov 2016 12:01:14 -0800
To: Rik Ribbers <rik.ribbers@sidn.nl>, Stephen Farrell <stephen.farrell@cs.tcd.ie>
From: S Moonesamy <sm+ietf@elandsys.com>
In-Reply-To: <F9093CE9-985F-4A45-A0BC-A60732FC4E72@sidn.nl>
References: <20161108144742.GH2473@Hanna.local> <6.2.5.6.2.20161108103525.0c84fd08@elandnews.com> <F9093CE9-985F-4A45-A0BC-A60732FC4E72@sidn.nl>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/wHlAx8OrF_r5DiSWhr8LuMk860g>
Cc: Job Snijders <job@instituut.net>, draft-ietf-eppext-keyrelay.all@ietf.org, shollenbeck@verisign.com, "Livesay, Paulplivesay"@verisign.com, regext@ietf.org
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: Tue, 08 Nov 2016 20:18:14 -0000
Hi Rik, Stephen, [ietf@ removed from Cc] At 11:53 08-11-2016, Rik Ribbers wrote: >Yes, this was addressed during the IESG review last december and >resulted in the latest version. The only thing blocking is the IPR-disclosure Thank you for confirming that. At 11:57 08-11-2016, Stephen Farrell wrote: >As to the meat of this, my discuss says "the DISCUSS is to ask >did I miss stuff and if not how can WG participants have >rationally considered an IPR declaration if the licensing >information will only arrive "later" after the document is >approved to become an RFC?" [snip] >I also chatted with Job about this a while back and indicated >that I'd be willing to clear (though not happy to clear) if the >response from the WG (via the chairs or AD) were something like >"the WG has consensus to live with the crap situation, seems >like it's not improving and we don't have anyone saying it out >be blocking." I don't think I ever did hear that back from anyone >though. Had I, I would have cleared the discuss. (And apologies >if I missed a statement to that effect.) Thanks. I gather that the above is clear enough for the Working Group to address the DISCUSS. Regards, S. Moonesamy
- [regext] draft-ietf-eppext-keyrelay unreasonably … Job Snijders
- Re: [regext] draft-ietf-eppext-keyrelay unreasona… S Moonesamy
- [regext] draft-ietf-eppext-keyrelay unreasonably … Marco Davids (IETF)
- Re: [regext] draft-ietf-eppext-keyrelay unreasona… Hollenbeck, Scott
- Re: [regext] draft-ietf-eppext-keyrelay unreasona… Rik Ribbers
- Re: [regext] draft-ietf-eppext-keyrelay unreasona… Stephen Farrell
- Re: [regext] draft-ietf-eppext-keyrelay unreasona… S Moonesamy
- Re: [regext] draft-ietf-eppext-keyrelay unreasona… Job Snijders
- Re: [regext] draft-ietf-eppext-keyrelay unreasona… Hollenbeck, Scott
- Re: [regext] draft-ietf-eppext-keyrelay unreasona… Hollenbeck, Scott
- Re: [regext] draft-ietf-eppext-keyrelay unreasona… Jelte Jansen
- Re: [regext] draft-ietf-eppext-keyrelay unreasona… Job Snijders
- Re: [regext] draft-ietf-eppext-keyrelay unreasona… Antoin Verschuren
- Re: [regext] draft-ietf-eppext-keyrelay unreasona… Rik Ribbers
- Re: [regext] draft-ietf-eppext-keyrelay unreasona… Marc Groeneweg
- Re: [regext] draft-ietf-eppext-keyrelay unreasona… Job Snijders
- Re: [regext] draft-ietf-eppext-keyrelay unreasona… Miek Gieben
- Re: [regext] draft-ietf-eppext-keyrelay unreasona… Rik Ribbers
- Re: [regext] draft-ietf-eppext-keyrelay unreasona… Alexey Melnikov
- Re: [regext] draft-ietf-eppext-keyrelay unreasona… Marc Groeneweg
- Re: [regext] draft-ietf-eppext-keyrelay unreasona… Marco Davids (IETF IMAP)
- Re: [regext] draft-ietf-eppext-keyrelay unreasona… bert hubert
- Re: [regext] draft-ietf-eppext-keyrelay unreasona… Jaap Akkerhuis
- Re: [regext] draft-ietf-eppext-keyrelay unreasona… Ulrich Wisser