Re: [eppext] [tmch-tech] Type of encoding attribute in draft-lozano-tmch-smd-03

James Galvin <galvin@elistx.com> Thu, 06 March 2014 10:18 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 [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6B91C1A01EF for <eppext@ietfa.amsl.com>; Thu, 6 Mar 2014 02:18:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level:
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, USER_IN_WHITELIST=-100] 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 h3nN9E7wCYXL for <eppext@ietfa.amsl.com>; Thu, 6 Mar 2014 02:18:23 -0800 (PST)
Received: from mail-we0-f179.google.com (mail-we0-f179.google.com [74.125.82.179]) by ietfa.amsl.com (Postfix) with ESMTP id 969941A020D for <eppext@ietf.org>; Thu, 6 Mar 2014 02:18:23 -0800 (PST)
Received: by mail-we0-f179.google.com with SMTP id x48so2727415wes.24 for <eppext@ietf.org>; Thu, 06 Mar 2014 02:18:19 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=IVBa/aKdJu3IY5ae2ti9UczusPplX488Jn4WLW1gCWs=; b=Xiptn4nVvpSD+ARNk1gEyg/Yp9lHnYjhG3mXd0F+fRXTNgie8JiiP3m9rATNgnSOBy scdRuKEaHi+EoM+yaFrGrfb5lcjEziq9BOzIwZK6Cz7HoeYH2ojQaLtuQsIVz4oMgcd1 YKwIsKVZdJHXVDXYttj54EQ/ja2/Gz9k+p+NXt/iO48yV+Tz0O9FSlD5nYEncDKdE3OD VjOsVf0GpRQjeMesv5eSml+HH2/yiOaR5c07puTDKEC9Mh+p7CNvywWn6Afp/KECdIqM X9r5PnpueloZn1QXgIb0q/Rp0nh5TevT2YlphJmlbLfd08UBlbz87yJ2ervCelXbIsFD k06A==
X-Gm-Message-State: ALoCoQnkJPYQvoUHIY2nRpdVv1rptgg13i2hxOBG3PkzGGQR2G5p0cP+G9FkOqX+AHJGkfT9dK+T
X-Received: by 10.194.234.106 with SMTP id ud10mr8974206wjc.0.1394101098893; Thu, 06 Mar 2014 02:18:18 -0800 (PST)
Received: from [31.133.166.63] (dhcp-a63f.meeting.ietf.org. [31.133.166.63]) by mx.google.com with ESMTPSA id q15sm14643635wjw.18.2014.03.06.02.18.17 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 06 Mar 2014 02:18:17 -0800 (PST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (1.0)
From: James Galvin <galvin@elistx.com>
X-Mailer: iPad Mail (11B651)
In-Reply-To: <53182E33.9020807@comlaude.com>
Date: Thu, 06 Mar 2014 10:18:17 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <8BF32284-6198-4036-8E90-19EB370E8726@elistx.com>
References: <CF3CB1E1.58C3C%jgould@verisign.com> <53182E33.9020807@comlaude.com>
To: Michael Holloway <michael.holloway@comlaude.com>
Archived-At: http://mailarchive.ietf.org/arch/msg/eppext/2nZyKx-4TKOgpHHs3Vvtdc2kxwo
Cc: "tmch-tech@icann.org" <tmch-tech@icann.org>, "eppext@ietf.org" <eppext@ietf.org>
Subject: Re: [eppext] [tmch-tech] Type of encoding attribute in draft-lozano-tmch-smd-03
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: <http://www.ietf.org/mail-archive/web/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, 06 Mar 2014 10:18:29 -0000

> On Mar 6, 2014, at 8:13 AM, Michael Holloway <michael.holloway@comlaude.com> wrote:
> 
>> On 03/05/2014 05:08 PM, Gould, James wrote:
>> To note, draft-lozano-tmch-smd has been moved to
>> draft-ietf-eppext-tmch-smd and draft-tan-epp-launchphase has been moved to
>> draft-ietf-eppext-launchphase, since they are being moved forward with the
>> new eppext WG.  I¹ve copied the eppext mailing list on this reply and my
>> prior reply to your posting associated with draft-ietf-eppext-launchphase.
> 
> Keeping both lists on as its probably relevant to both.
> 
> Is there a way to forward the old drafts to the new ones on ietf.org (eg draft-tan-epp-launchphase-13 -> draft-ietf-eppext-launchphase-00) or a note somewhere that this has happened. I think this changed has gone unnoticed by a number of registries & registrars so any updates might be missed (though I realise there is no change from launchphase-12 -> launchphase-00 other than names/references). I have yet to see registry documentation referencing the new drafts.

Speaking as cochair of EPPEXT, there may be a short cut but there are two things that the authors of the docs should do.  First if the docs are going to remain as working group docs, the editors should move to editing a version with the new name.  Second, since the "00" version of the docs are created in the working group, the editors should upload the current version as the "01".

Jim