Re: [eppext] moving documents along

Ulrich Wisser <ulrich@wisser.se> Fri, 30 January 2015 09:32 UTC

Return-Path: <ulrich@wisser.se>
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 E697B1A8A77 for <eppext@ietfa.amsl.com>; Fri, 30 Jan 2015 01:32:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.943
X-Spam-Level:
X-Spam-Status: No, score=0.943 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, MISSING_HEADERS=1.021, RCVD_IN_DNSWL_LOW=-0.7] autolearn=no
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 iKZrfuSPMppK for <eppext@ietfa.amsl.com>; Fri, 30 Jan 2015 01:32:34 -0800 (PST)
Received: from mail-la0-f46.google.com (mail-la0-f46.google.com [209.85.215.46]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 077821A8A6D for <eppext@ietf.org>; Fri, 30 Jan 2015 01:32:34 -0800 (PST)
Received: by mail-la0-f46.google.com with SMTP id s18so22746776lam.5 for <eppext@ietf.org>; Fri, 30 Jan 2015 01:32:32 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:cc:content-type; bh=VkK8p8w64tkNYD/IUp3RrmM+U0splOHWUT2tCrGTFCQ=; b=cHROaT1Cs7b6JwwS9z0kqsNXJs8gBtNT+wcCynkd/y7Bj+4r7yAYxnGf890h90Liab hm052uE20qgMuXORCzQUhEIKvL1/uBVlL1vbZxeh50Gvi9UBEoaBm3d3uCWZeVhqwJ/g gktjxAQsxNqNtpGvQZiuKaa+M7k3m3ETQC0aNQU3JV8jXriVtLic5Oo8nNU/eYlJwbEY 2S4DozyLuFvzSYkJ4+aimr1KxCCvVBamO7l0gZSvLVMwQUsOYczcqj6SkHq/YrmHFeVM ZwKnWm09MvAaL/sVU9ByGR/fjvScP2qtvDCRjHDBfhmE3ZC7p5xfaVBNY6ZlArvZLGGB xFXQ==
X-Gm-Message-State: ALoCoQld8jK2rR72ApYB4wTnZUCOUIT89JHJ3Y2m2TPCc7xYgXCY3ddaVNnYCGcSXSEiCppdI7n2
MIME-Version: 1.0
X-Received: by 10.112.243.12 with SMTP id wu12mr5459549lbc.91.1422610352094; Fri, 30 Jan 2015 01:32:32 -0800 (PST)
Received: by 10.25.29.134 with HTTP; Fri, 30 Jan 2015 01:32:32 -0800 (PST)
In-Reply-To: <54BFC82E.1070208@elistx.com>
References: <54BFC82E.1070208@elistx.com>
Date: Fri, 30 Jan 2015 10:32:32 +0100
Message-ID: <CAJ9-zoUwhRYN=S_RdPqxLirRxX7JLb3i+xjW7vWwpHMfr1OXGg@mail.gmail.com>
From: Ulrich Wisser <ulrich@wisser.se>
Cc: eppext <eppext@ietf.org>
Content-Type: multipart/alternative; boundary="001a1133ac52b0e8f5050ddb48cd"
Archived-At: <http://mailarchive.ietf.org/arch/msg/eppext/Xg8legxG8OJ22JJm1OBYcZVmZl0>
Subject: Re: [eppext] moving documents along
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: Fri, 30 Jan 2015 09:32:36 -0000

Hi  James!

Besides the old documents I would like to see us discuss if we want to
adopt new ones / recharter.

draft-ietf-eppext-idnmap-02 is not very controversial except that we need
to defines the table names. Otherwise it doesn't help much.

draft-ietf-eppext-launchphase-02 and draft-ietf-eppext-tmch-smd-00 seem
technically sound so no objections there.

/Ulrich


2015-01-21 16:39 GMT+01:00 James Galvin <galvin@elistx.com>:

> Speaking as Chair, I want to bring folks up to date on where I believe we
> are.  Please do speak up if you disagree or have any corrections.
>
> We have 5 documents in our working group.
>
>
> 1. draft-ietf-eppext-reg-10 Extension Registry for the Extensible
> Provisioning Protocol
>
> If you've been tracking the status updates from the RFC Editor on the list
> then you know this document is close to publication as an RFC. Scott
> Hollenbeck has been doing his part to move this along.  There is no action
> for the working group at this time.
>
>
> 2. draft-ietf-eppext-idnmap-02 Internationalized Domain Name Mapping
> Extension for the Extensible Provisioning Protocol (EPP)
>
> There has been very little discussion on the mailing list about this
> document.  Andrew Sullivan posted some extensive comments to which there
> has been limited response.
>
> It's tough to declare consensus with so little discussion.  It would be
> helpful if folks would review the document and comments and post at least a
> "no objection".
>
>
> 3. draft-ietf-eppext-keyrelay-01         Relay Extension for the
> Extensible Provisioning Protocol
>
> There has been lively discussion here and we appear to have a difference
> of opinion on a technical point.  We very much need to hear from other
> folks.  Please review the thread and let everyone know what you think.
>
>
> 4. draft-ietf-eppext-launchphase-02 Launch Phase Mapping for the
> Extensible Provisioning Protocol (EPP)
>
> I believe we're close to consensus on this document.  There's been some
> discussion but nothing too contentious as far as I can see.  I'm expecting
> Jim Gould to submit a revised document in the not too distant future and
> we'll review where we are at that time.
>
>
> 5. draft-ietf-eppext-tmch-smd-00 Mark and Signed Mark Objects Mapping
>
> This document has expired and is waiting for the author to resubmit. There
> was one change proposed on the mailing list last year that needs to be
> incorporated in the revision.
>
> At one time there was concern about the relationship between this document
> and the launchphase document but I don't believe that concern exists any
> more.
>
> I suppose it's fair to ask if the working group is still interested in
> publishing this document.  If so, I'll press Gustavo to submit a revised
> document and we can review where we are at that time.
>
>
> Comments and corrections are welcome!
>
> Jim
>
> _______________________________________________
> EppExt mailing list
> EppExt@ietf.org
> https://www.ietf.org/mailman/listinfo/eppext
>