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

"James Galvin" <galvin@elistx.com> Wed, 03 February 2016 22:37 UTC

Return-Path: <galvin@elistx.com>
X-Original-To: eppext@ietfa.amsl.com
Delivered-To: eppext@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id 10AE21B35F6 for <eppext@ietfa.amsl.com>; Wed, 3 Feb 2016 14:37:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, USER_IN_WHITELIST=-100] autolearn=unavailable
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id i8KSbfyGXVpC for <eppext@ietfa.amsl.com>; Wed, 3 Feb 2016 14:37:02 -0800 (PST)
Received: from mail-qg0-x233.google.com (mail-qg0-x233.google.com [IPv6:2607:f8b0:400d:c04::233]) (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 96FB01B2D1C for <eppext@ietf.org>; Wed, 3 Feb 2016 14:36:38 -0800 (PST)
Received: by mail-qg0-x233.google.com with SMTP id o11so27754744qge.2 for <eppext@ietf.org>; Wed, 03 Feb 2016 14:36:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=elistx-com.20150623.gappssmtp.com; s=20150623; h=from:to:subject:date:message-id:mime-version:content-type :content-transfer-encoding; bh=T8KqgWAGwD9XOsdFEadwtwHGv68AIE4HQ+es8N8kSPE=; b=Ni4P/FSiNm6T8u+RhIe+gA+rkIFfjhFtJec9Qt9jQpC6uiJ4Aa/yemkOc9n/69b5gv JqzdF9ccFAMJcNaCo7qKSDPtbjTR7jbNKM6JNk9YXPPRjV30Zszgw1aTezSaCuTHf3Us TiAPSMHrlEs3wUosHo2XG4h0fXucT/qmWfxGSs+onGU2mReJTh875ItCMZIPtekzIB3O UGp+4ZJhrUP7mXlz6kLwNfBGhO7v9lo3GMMCNT9cbGeiUh6cXbvoQqcZUTV5Yxs71IDA e1ua2H4xIeesOo/nMDtqLPkJUCOWXjonE20eYvOGD1mioqmsarwqpt43wscWdsKTv1Vz WCeQ==
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:date:message-id:mime-version :content-type:content-transfer-encoding; bh=T8KqgWAGwD9XOsdFEadwtwHGv68AIE4HQ+es8N8kSPE=; b=FZ+LyTFUUnoIWiLLrh5NqG3g34obNht6jzYvVQsNByWpXS9L6VdsUDsvk6y0oFKqV7 Guzh4mr2TWr4Fv8wxwRX2rQzTacRKuXcXRg5E1zN0062f6VXfl3cNk61/p+F+OaqTSbY D/+0cd2/FU8RmuV7wPHCyfJUxMXG7kybvJdGLcKQ8eAWmepnN95N3OeKRD6oh60EFZZW a3cjQNWgp74EPsbI4SzOpeqlCTxeipl2qJHkt6usminE0MjUeJf6mcvV6t+0pJLevzxn VjMDLWbk4psEkMCZjXIMEk+RcXt+heWVxfN9V6mS6Go7+1vdxJaysr1XqqYrcMUsFauM zJ/Q==
X-Gm-Message-State: AG10YOS0ekmrafAZ40RWriZBxVxKbdnBcRhaFsWZFflg9D6kjLy94nDi9tiY0q5WWDvMsw==
X-Received: by with SMTP id l66mr5091368qgd.90.1454538997856; Wed, 03 Feb 2016 14:36:37 -0800 (PST)
Received: from [] (c-73-133-108-218.hsd1.md.comcast.net. []) by smtp.googlemail.com with ESMTPSA id l19sm3480637qki.42.2016. (version=TLS1 cipher=AES128-SHA bits=128/128); Wed, 03 Feb 2016 14:36:37 -0800 (PST)
From: James Galvin <galvin@elistx.com>
To: WEIRDS WG <weirds@ietf.org>, EPP Extensions WG <eppext@ietf.org>
Date: Wed, 03 Feb 2016 17:36:36 -0500
Message-ID: <25DCAE42-78EF-40F0-BC87-34A53752B824@elistx.com>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="=_MailMate_A9C2F99B-DBE4-460C-98F6-DFFCDE394290_="
Content-Transfer-Encoding: 8bit
X-Mailer: MailMate (1.9.3r5187)
Archived-At: <http://mailarchive.ietf.org/arch/msg/eppext/olZoZ9CQh_tJKn074j-cUyWsDss>
Subject: [eppext] 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: Wed, 03 Feb 2016 22:37:09 -0000

Many of you are probably aware of the proposed new working group for the 
IETF: Registration Protocols Extensions (regext).  Certainly the EPPEXT 
working group is aware because the charter was developed there.  I have 
attached the charter that has been submitted to the IESG for review for 
your convenience.

This message is to alert everyone that the IETF Secretariat has been 
asked to create the new “regext” mailing list and to automatically 
subscribe all current subscribers of both the “weirds” and 
“eppext” to it.

If you do not wish to be a part of this work going forward please just 
unsubscribe when you get the welcome message.

The next step will be for the IESG to review the proposed charter and 
make a decision as to whether or not to proceed using its usual process.

If the charter is approved and the working group is to be created then 
both the “weirds” and the “eppext” mailing lists will be aliased 
to point to the “regext” mailing list.  The old mailing lists will 
be removed but their respective archives will remain.


Jim and Antoin
proposed co-chairs of the regext working group