Re: [provreg] [eppext] Inconsistency in number of status values in draft-tan-epp-launchphase-12 ?
Wil Tan <wil@cloudregistry.net> Fri, 07 March 2014 08:44 UTC
Return-Path: <wil@cloudregistry.net>
X-Original-To: provreg@ietfa.amsl.com
Delivered-To: provreg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 41E3B1A0103 for <provreg@ietfa.amsl.com>; Fri, 7 Mar 2014 00:44:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Level:
X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-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 qHHvDULuigVW for <provreg@ietfa.amsl.com>; Fri, 7 Mar 2014 00:44:08 -0800 (PST)
Received: from mail-we0-f181.google.com (mail-we0-f181.google.com [74.125.82.181]) by ietfa.amsl.com (Postfix) with ESMTP id 958251A010F for <provreg@ietf.org>; Fri, 7 Mar 2014 00:44:06 -0800 (PST)
Received: by mail-we0-f181.google.com with SMTP id q58so4501248wes.26 for <provreg@ietf.org>; Fri, 07 Mar 2014 00:44:02 -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:cc:content-type; bh=yIqjDnxx6DGWuwftjBP/rVG5QCQxlIKoFuam3B0w8OE=; b=Sv69Ez06RJneFCYtyEmtOnguT9vBIgqbPrpF/D0MCOaJs4GJPOixmob/AgFKqPYz8y 80QIpaIGqDkfjgYOsvbWCZVMDgppvzPZXXjSIYy9IRinxY7m3W7fWQTDhpPk24XrvZzO cBzpGIJUyGxFsjorI1WTTQLkM/HV6Bh9NgRTxj+S5CMDWEB/PzJ/2tW+w8Mc4hxA1jEk J5YzNnsl0LOy6S1GE3VuqGDa12gaAVDlhCjWX8Y4TMDZJxmPaBgL/fhPt2yQ19sM5rXd CgB9ttTdOGeJ57BRHVP4v9I5D2xZlZZlKbY0zBpzeoG2CisUg9QoWCij1ymMHxrEGYER bKIw==
X-Gm-Message-State: ALoCoQlDwvLXGzIUgztrUF31s0e1jKykbP5EdYXW68pNJB3VNY9of5m4G8490EBsSG80cyTrU6BE
MIME-Version: 1.0
X-Received: by 10.194.2.168 with SMTP id 8mr17145888wjv.8.1394181841927; Fri, 07 Mar 2014 00:44:01 -0800 (PST)
Received: by 10.216.95.66 with HTTP; Fri, 7 Mar 2014 00:44:01 -0800 (PST)
Received: by 10.216.95.66 with HTTP; Fri, 7 Mar 2014 00:44:01 -0800 (PST)
In-Reply-To: <53175035.3010102@centralnic.com>
References: <CF3CAD62.58C04%jgould@verisign.com> <53175035.3010102@centralnic.com>
Date: Fri, 07 Mar 2014 19:44:01 +1100
Message-ID: <CACnMJCOCv8fQPXbSv3wks_pB3X=ZOCooLLuAHx6ra1ktjMTX0A@mail.gmail.com>
From: Wil Tan <wil@cloudregistry.net>
To: Gavin Brown <gavin.brown@centralnic.com>
Content-Type: multipart/alternative; boundary="047d7b3a893a70d8a004f400418d"
Archived-At: http://mailarchive.ietf.org/arch/msg/provreg/u4mxMkPQwwtcQhCctwCP5832vjE
Cc: eppext@ietf.org, "provreg@ietf.org" <provreg@ietf.org>
Subject: Re: [provreg] [eppext] Inconsistency in number of status values in draft-tan-epp-launchphase-12 ?
X-BeenThere: provreg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: EPP discussion list <provreg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/provreg>, <mailto:provreg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/provreg/>
List-Post: <mailto:provreg@ietf.org>
List-Help: <mailto:provreg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/provreg>, <mailto:provreg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Mar 2014 08:44:12 -0000
On 06/03/2014 3:26 am, "Gavin Brown" <gavin.brown@centralnic.com> wrote: > > +1. Our implementation only supports a single status. Are there any > implementations which require this design? +1 we should keep it simple. already the spec supports quite a few use cases, so unless this is a blocker for a common scenario we should not allow multiple status values. .wil > > I'll add this point to my slides for discussion tomorrow. > > G. > > On 05/03/2014 15:36, Gould, James wrote: > > Patrick, > > > > Good catch. My recommendation is for the text to be tightened up to > > support only a single status, since the status really reflects the status > > or state within the state diagram of Figure 1. Adding support for > > multiple statuses in the XML schema would make it more difficult for the > > client to determine the state of the application. Thoughts? > > > > -- > Gavin Brown > Chief Technology Officer > CentralNic Group plc (LSE:CNIC) > Innovative, Reliable and Flexible Registry Services > for ccTLD, gTLD and private domain name registries > https://www.centralnic.com/ > > CentralNic Group plc is a company registered in England and Wales with > company > number 8576358. Registered Offices: 35-39 Moorgate, London, EC2R 6AR. > > > _______________________________________________ > provreg mailing list > provreg@ietf.org > https://www.ietf.org/mailman/listinfo/provreg >
- [provreg] Inconsistency in number of status value… Patrick Mevzek
- Re: [provreg] Inconsistency in number of status v… Gould, James
- Re: [provreg] [eppext] Inconsistency in number of… Gavin Brown
- Re: [provreg] [eppext] Inconsistency in number of… Mike O
- Re: [provreg] [eppext] Inconsistency in number of… Wil Tan