Re: [eppext] [provreg] Publishing of the Change Poll EPP Extension IETF Draft

Ulrich Wisser <ulrich@wisser.se> Fri, 30 January 2015 09:08 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 CF8E81A8A72 for <eppext@ietfa.amsl.com>; Fri, 30 Jan 2015 01:08:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.723
X-Spam-Level:
X-Spam-Status: No, score=0.723 tagged_above=-999 required=5 tests=[BAYES_50=0.8, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] 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 vExtwlxXYHMN for <eppext@ietfa.amsl.com>; Fri, 30 Jan 2015 01:08:05 -0800 (PST)
Received: from mail-lb0-f180.google.com (mail-lb0-f180.google.com [209.85.217.180]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 451F51A8A71 for <eppext@ietf.org>; Fri, 30 Jan 2015 01:08:05 -0800 (PST)
Received: by mail-lb0-f180.google.com with SMTP id b6so35281795lbj.11 for <eppext@ietf.org>; Fri, 30 Jan 2015 01:08:03 -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:to:content-type; bh=00R+Oz1RQr5oyiHv22Pbjslj/VS5EOJ0fqnuFZnUVuI=; b=Ie+69OOmfoozBt72TxBBQmf63YMsWQId9UBoITMCCTWMI/h0tj8EwhK3OMzS9Gj0Ia VRHFAgdQqxMCRJjFHR4h4C6b+ODMkrI86QbIKLTK5jo9McdQgdZvTa2Zyebp4kpVn3TA NJs4/dEdL2qLwcwvLneuvSn/sboFS0/29S6H6qC4uVazKC9ahh2/HdN5jqVtm53V0Dmo WXzpEdQe/ABPDDmDC1qjIEx9wu+lSdpfDki6+l96b2kpAiUFp3SWmeapjGLMDZzrX17q gkBMqlrR7P/OMsZ3VF7ZIfaZTqmc3GMAYt6Ccs9JAhVLm63ZPSBqZzpwwbkkq9JxE9Og ehZg==
X-Gm-Message-State: ALoCoQmBQJyYoTDcz+y8aus+n3CAAg/dTnSrtfCSmo5H8lCpVuA7OuCv6Vg3Yo+5EpQVjs2YpCtz
MIME-Version: 1.0
X-Received: by 10.112.199.39 with SMTP id jh7mr5511441lbc.46.1422608883306; Fri, 30 Jan 2015 01:08:03 -0800 (PST)
Received: by 10.25.29.134 with HTTP; Fri, 30 Jan 2015 01:08:03 -0800 (PST)
In-Reply-To: <211D0420-18A3-43D7-9A3D-553B34C6DF43@verisign.com>
References: <211D0420-18A3-43D7-9A3D-553B34C6DF43@verisign.com>
Date: Fri, 30 Jan 2015 10:08:03 +0100
Message-ID: <CAJ9-zoVSoY=g+70ZfYFkYG7KEFM88x0BxVRH5jUxNYqMsMt+8A@mail.gmail.com>
From: Ulrich Wisser <ulrich@wisser.se>
To: "eppext@ietf.org" <eppext@ietf.org>
Content-Type: multipart/related; boundary=001a11c32cf0254e49050ddaf18c
Archived-At: <http://mailarchive.ietf.org/arch/msg/eppext/651A1mPhCu4tHyEei9fNuD89--w>
Subject: Re: [eppext] [provreg] Publishing of the Change Poll EPP Extension IETF Draft
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:08:08 -0000

Hi James and Trung!

You two did a nice job on the extension.

I  would prefer the transform command instead of the info response. That
would eliminate the need for before/after indicator.

I have some problems with the operators

- Why is autoRenew a special operation instead of operation renew with
op="auto"?
- What is the difference between delete and delete op="purge"?
- Why autoPurge / autoDelete?

Kind regards from Stockholm

Ulrich



2015-01-20 14:49 GMT+01:00 Gould, James <JGould@verisign.com>om>:

>  The first draft of the Change Poll EPP Extension (
> http://tools.ietf.org/html/draft-gould-change-poll-00 ) has been
> submitted to the IETF.  I co-authored this draft with Trung Tran from
> Neustar to provide a mechanism within EPP to notify clients of any
> server-side change, including but not limited to regular batch processes,
> customer support actions, Uniform Domain-Name Dispute-Resolution Policy
> (UDRP) or Uniform Rapid Suspension (URS) actions, court directed actions,
> and bulk updates based on customer requests.    Since the client is not
> directly involved or knowledgable of these operations, the extension is
> used along with an EPP object mapping to provide the resulting state of the
> post-operation object, and optionally a pre-operation object, with the
> operation meta-data of what, when, who, and why.  We would like this draft
> to be included in a re-charting of the EPPEXT Working Group.
>
>  Please review the draft and provide any feedback.
>
>  Thanks,
>
>  —
>
>
>  JG
>
>
>
>
>
> *James Gould *Distinguished Engineer
> jgould@Verisign.com
>
> 703-948-3271
> 12061 Bluemont Way
> Reston, VA 20190
>
> VerisignInc.com
>
> “This message (including any attachments) is intended only for the use of
> the individual or entity to which it is addressed, and may contain
> information that is non-public, proprietary, privileged, confidential and
> exempt from disclosure under applicable law or may be constituted as
> attorney work product. If you are not the intended recipient, you are
> hereby notified that any use, dissemination, distribution, or copying of
> this communication is strictly prohibited. If you have received this
> message in error, notify sender immediately and delete this message
> immediately.”
>
> _______________________________________________
> provreg mailing list
> provreg@ietf.org
> https://www.ietf.org/mailman/listinfo/provreg
>
>