IETF Logo Mail Archive

Re: [eppext] [provreg] auto subscription to the new regext@ietf.org

"Gould, James" <JGould@verisign.com> Thu, 04 February 2016 13:12 UTC

Return-Path: <JGould@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 DE7CF1B2EC9 for <eppext@ietfa.amsl.com>; Thu, 4 Feb 2016 05:12:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001] 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 UrtbsZNbulzQ for <eppext@ietfa.amsl.com>; Thu, 4 Feb 2016 05:12:11 -0800 (PST)
Received: from mail-qg0-x262.google.com (mail-qg0-x262.google.com [IPv6:2607:f8b0:400d:c04::262]) (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 BFAE91B2EC7 for <eppext@ietf.org>; Thu, 4 Feb 2016 05:12:10 -0800 (PST)
Received: by mail-qg0-x262.google.com with SMTP id o11so4549622qge.3 for <eppext@ietf.org>; Thu, 04 Feb 2016 05:12:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=verisign-com.20150623.gappssmtp.com; s=20150623; h=from:to:cc:subject:thread-topic:thread-index:date:message-id :references:in-reply-to:accept-language:content-language :content-type:mime-version; bh=ERo/DEzFovmSkJ/GBKekXOCZ8fVp4wsAZH1+nbNfes8=; b=V2FsZ0W+AN+F4UwmSxVX8Cgw3cpl8Qhul3iePy3A52cfRNLRwRPZ7zh0word7ZYuVi DO2F1obx4t0iF+xjrpq8lhsrpT7GmYPuHC6KqjkGf9xeVhZLx1D/NHk+zMGY+mRbBsDo 9GchQYhQO9Pv+Exyl3xKi/4lYZ0mvJN5tbF3tGY1TDNUs9TRBWY6StOfn1Twj2SyYAn0 a/t4AYAwatrG0Qe0Ym/dPzpvnvtgj+LPHVa7F8K8lE+fH6J9L36I57AF29MufmAg0Xre uPfGE66qm3XSKqsviWfN46nfo8/puyrj+wK490Qvq2cm6Ee10BeJweaTz3ZkSvi4077Z G1ew==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:subject:thread-topic:thread-index :date:message-id:references:in-reply-to:accept-language :content-language:content-type:mime-version; bh=ERo/DEzFovmSkJ/GBKekXOCZ8fVp4wsAZH1+nbNfes8=; b=WAlNem7VWhDDDPwlK9I21eUQtAezdiv4ESUBT/qRUujLKnmq2ycHGFITUzVduXDQOO 9gnaVO3EofM49I8SvQYhQFxCo4IVK35Y2rCnDUob0DDGeew68OETVpeCIrgQFU0OSVAC vWMbRY2Nwd98fZowztJDWu1kGKUTKxHpwnN/ArmcvvaCE5abtx3hFSA+9eVhGW1zz0Qy 6bjvWeeDV4EodcydvSCqDDE/Ykj94cPPc7+I3pIhfWNuJA3x+EtuRmGzvwdddlZFb411 1yvBsPmHmVGbT5htqy2CUUQKBv3Y1GLuVaKUlzuO4FKp2oCu8OJMFrizmZUziQlFAA/y SG1w==
X-Gm-Message-State: AG10YOT3Asg92AcvBY0iGI382CXRRIWmB6Ks6fkZ6kfpFKaQFSw4sjBzJycM8tNWgPsll1O4TJW9PCPqBnAHcSvBDQ8HVqSr
X-Received: by 10.140.108.229 with SMTP id j92mr8692716qgf.17.1454591529855; Thu, 04 Feb 2016 05:12:09 -0800 (PST)
Received: from brn1lxmailout02.verisign.com (brn1lxmailout02.verisign.com. [72.13.63.42]) by smtp-relay.gmail.com with ESMTPS id w125sm1519609qka.5.2016.02.04.05.12.09 (version=TLS1 cipher=AES128-SHA bits=128/128); Thu, 04 Feb 2016 05:12:09 -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 u14DC95M012691 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 4 Feb 2016 08:12:09 -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 08:12:03 -0500
From: "Gould, James" <JGould@verisign.com>
To: "Hollenbeck, Scott" <shollenbeck@verisign.com>
Thread-Topic: [eppext] [provreg] auto subscription to the new regext@ietf.org
Thread-Index: AQHRX0WsnJlJHIhO/UGCRCMKENGAVJ8cMI4A
Date: Thu, 04 Feb 2016 13:12:03 +0000
Message-ID: <F3CE07AA-733C-4AB1-B02D-6E4CA6B92A59@verisign.com>
References: <25DCAE42-78EF-40F0-BC87-34A53752B824@elistx.com> <58BB2DBF-DCBE-4194-884E-11715AE52585@sidn.nl> <7BCFE6E4-B9DF-448F-A91A-584521D8F479@antoin.nl> <831693C2CDA2E849A7D7A712B24E257F4A152532@BRN1WNEXMBX01.vcorp.ad.vrsn.com>
In-Reply-To: <831693C2CDA2E849A7D7A712B24E257F4A152532@BRN1WNEXMBX01.vcorp.ad.vrsn.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [10.173.152.4]
Content-Type: multipart/related; boundary="_004_F3CE07AA733C4AB1B02D6E4CA6B92A59verisigncom_"; type="multipart/alternative"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/eppext/3ca352qGTaj1W5-7ZqfcUGGd6-c>
Cc: Rik Ribbers <rik.ribbers@sidn.nl>, Antoin Verschuren <ietf@antoin.nl>, EPP Extensions WG <eppext@ietf.org>, "provreg@ietf.org" <provreg@ietf.org>
Subject: Re: [eppext] [provreg] auto subscription to the new regext@ietf.org
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 13:12:14 -0000

+1

—


JG


[cid:77031CC3-BE7A-4188-A95F-D23115A30A4D@vcorp.ad.vrsn.com]

James Gould
Distinguished Engineer
jgould@Verisign.com

703-948-3271
12061 Bluemont Way
Reston, VA 20190

VerisignInc.com<http://VerisignInc.com>

On Feb 4, 2016, at 7:14 AM, Hollenbeck, Scott <shollenbeck@verisign.com<mailto:shollenbeck@verisign.com>> wrote:

-----Original Message-----
From: provreg [mailto:provreg-bounces@ietf.org] On Behalf Of Antoin
Verschuren
Sent: Thursday, February 04, 2016 5:16 AM
To: Rik Ribbers
Cc: EPP Extensions WG; provreg@ietf.org<mailto:provreg@ietf.org>
Subject: Re: [provreg] [eppext] auto subscription to the new
regext@ietf.org<mailto:regext@ietf.org>

Rik,

We're discussing this.
Formally the provreg WG was closed, but since the mailinglist was still
used before EPPEXT was formed by lack of another channel to discuss
EPP, I guess we should have migrated the provreg mailinglist when
forming EPPEXT.
I'm CC'ing the provreg mailinglist to see if there are any objections,
otherwise we will aks the secretariat to migrate provreg as well as the
WG suggested.
Any objections from the provreg mailinglist subscribers if we alias the
provreg mailinglist to the new to be formed REGEXT mailinglist to
discuss EPP?

No objections from me.

Scott

_______________________________________________
EppExt mailing list
EppExt@ietf.org<mailto:EppExt@ietf.org>
https://www.ietf.org/mailman/listinfo/eppext

v2.23.0 | Report a Bug | By Email