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

"Hollenbeck, Scott" <shollenbeck@verisign.com> Thu, 04 February 2016 15:36 UTC

Return-Path: <shollenbeck@verisign.com>
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 C73BE1B3198 for <eppext@ietfa.amsl.com>; Thu, 4 Feb 2016 07:36:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1] 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 UntUts8gaazO for <eppext@ietfa.amsl.com>; Thu, 4 Feb 2016 07:36:46 -0800 (PST)
Received: from mail-oi0-x261.google.com (mail-oi0-x261.google.com [IPv6:2607:f8b0:4003:c06::261]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 18BEA1B318E for <eppext@ietf.org>; Thu, 4 Feb 2016 07:36:46 -0800 (PST)
Received: by mail-oi0-x261.google.com with SMTP id x141so1586385oia.1 for <eppext@ietf.org>; Thu, 04 Feb 2016 07:36:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=verisign-com.20150623.gappssmtp.com; s=20150623; h=from:to:subject:thread-topic:thread-index:date:message-id :references:in-reply-to:accept-language:content-language :content-type:content-transfer-encoding:mime-version; bh=Di8GAyMF1yk6vAu+5zD8zP26esrZECb0yVdCPjXdcpY=; b=0XT31tXwKS3SbAR2sFGACtmn5yM24TODXV+v457FamxM/4S+Mp+4YUHKBOSYzjmHYI oAaSxHo5CzMYE94LkcfycB4dSYk6D1kx+6WEKuUm5eNdlXSyF/S1fxwq3ILcTfxTKITF vkmMqNVjPCQybMlkxWKv74A4yuLn7U7cd12bECLXo/YSyY3HP+Rdr+6R16SpRHNRZ5LC eZ9KJTaFUolRvW4NzarNK4nhoEEWXbRcz+o/zsU42it1SQ6XMZ7A/QgU6BjTKv0aPXxX PkL8DK3cJiK1Eyv25GRzlU9P5KlEmW5WibmnyVwuSoKPg63fzGVTi2VYWvpKbw7/q4LT yUxw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:subject:thread-topic:thread-index:date :message-id:references:in-reply-to:accept-language:content-language :content-type:content-transfer-encoding:mime-version; bh=Di8GAyMF1yk6vAu+5zD8zP26esrZECb0yVdCPjXdcpY=; b=O7KYJZcY20HV6IPcYQ+tq7TE1yWxxxl9lwDxO2Eu8TpRvjT1R/its0qBYh8NBAWTtN GOVCfkTDOfUtvptby4nwSQKS0V8lUJXWlLAQnhZ8+w19ApmqTsdl6lY8qhRruFQ/vw/a I3Uol//G+lgaNJXVi/V5YOpAJf9M33PqATa4w7/PiCMdELyodLl4zSfewenW/YXUIHBb rjEnDzL/cKsi1dCn8tnrwjtbQPMKVPT9ib8EmyuopTdeLqlGVDxJ2tGpWi7blnPilqdO RWI7V+NETk6y+v0+0+u852o7jqv91g8GkNu+isG5xh2saFf/JDTSLiIBtGN9F2N29RVX 3Z5A==
X-Gm-Message-State: AG10YOTokYj2QgFdtCOsMZpWYDA17pIE3h+QToPsbXsVGkK+/jO/PyPtP8Gw0TDCEfwL+joFA7XY97IUWyJWrI3XUvhz5dcZ
X-Received: by 10.140.255.8 with SMTP id a8mr10508636qhd.20.1454600205402; Thu, 04 Feb 2016 07:36:45 -0800 (PST)
Received: from brn1lxmailout02.verisign.com (brn1lxmailout02.verisign.com. [72.13.63.42]) by smtp-relay.gmail.com with ESMTPS id d123sm1633670qka.12.2016.02.04.07.36.45 (version=TLS1 cipher=AES128-SHA bits=128/128); Thu, 04 Feb 2016 07:36:45 -0800 (PST)
X-Relaying-Domain: verisign.com
Received: from brn1wnexcas02.vcorp.ad.vrsn.com (brn1wnexcas02 [10.173.152.206]) by brn1lxmailout02.verisign.com (8.13.8/8.13.8) with ESMTP id u14FaiLc019254 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 4 Feb 2016 10:36:45 -0500
Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by brn1wnexcas02.vcorp.ad.vrsn.com ([::1]) with mapi id 14.03.0174.001; Thu, 4 Feb 2016 10:36:44 -0500
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
To: Paul Hoffman <paul.hoffman@vpnc.org>, "eppext@ietf.org" <eppext@ietf.org>
Thread-Topic: [eppext] draft-ietf-eppext-keyrelay seems stuck
Thread-Index: AQHRX14ZLnQ1KrU0L0ObDJeXM0PjTp8cBFzg
Date: Thu, 4 Feb 2016 15:36:44 +0000
Message-ID: <831693C2CDA2E849A7D7A712B24E257F4A152A7D@BRN1WNEXMBX01.vcorp.ad.vrsn.com>
References: <D1F909D5-F358-487F-9CD9-DB1E85579FEB@vpnc.org>
In-Reply-To: <D1F909D5-F358-487F-9CD9-DB1E85579FEB@vpnc.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.173.152.4]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/eppext/C1zJNCszttJp4B5fQsLIsW6LM5w>
Subject: Re: [eppext] draft-ietf-eppext-keyrelay seems stuck
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: <https://mailarchive.ietf.org/arch/browse/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, 04 Feb 2016 15:36:47 -0000

> -----Original Message-----
> From: EppExt [mailto:eppext-bounces@ietf.org] On Behalf Of Paul Hoffman
> Sent: Thursday, February 04, 2016 10:07 AM
> To: eppext@ietf.org
> Subject: [eppext] draft-ietf-eppext-keyrelay seems stuck
> 
> Greetings. According to
> <https://datatracker.ietf.org/doc/draft-ietf-eppext-keyrelay/>;, this
> draft has been stuck with a significant DISCUSS for well over a month.
> How can the WG help get this WG document moving again?

The WG is waiting for an updated IPR declaration from Verisign. I'm still trying to make that happen and unfortunately I don't yet know when it will be done. I will report back when I know for sure.

Scott