Re: [eppext] Recharter Milestones discussion

"Gould, James" <JGould@verisign.com> Wed, 09 December 2015 15:41 UTC

Return-Path: <JGould@verisign.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 1FE191B2D8D for <eppext@ietfa.amsl.com>; Wed, 9 Dec 2015 07:41:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=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 obYlKbozSZ8V for <eppext@ietfa.amsl.com>; Wed, 9 Dec 2015 07:41:27 -0800 (PST)
Received: from mail-oi0-x263.google.com (mail-oi0-x263.google.com [IPv6:2607:f8b0:4003:c06::263]) (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 945241B2D85 for <eppext@ietf.org>; Wed, 9 Dec 2015 07:41:27 -0800 (PST)
Received: by oibl204 with SMTP id l204so3693238oib.3 for <eppext@ietf.org>; Wed, 09 Dec 2015 07:41:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=verisign-com.20150623.gappssmtp.com; s=20150623; h=from:to:cc:subject:thread-topic:thread-index:date:message-id :references:in-reply-to:accept-language:content-language :content-type:mime-version; bh=+rR8lkMbIC5AM7a18Dkj2b9aXqCAtYDecq9J1yYf1oE=; b=FGELFf4KWKmgBLZCYJGNiH/Ym/+F0WAvyfaIRrdcV4lZaPnTSuw7PkC1LnZXx27Zc9 ZVDubVQj2Wv+vWiwvJ3V7fXdIsj6OvUo624IJHc9R7FWiykfFd3GbYoji58usuM0cqBC lhyPM8gTuv4bkSFhELM/t2TJQbRaCspfa128y0j5mK34TBeRrfiuiH/NmFt8i3O8vScD y3qglarwOpbAyzR/I8uZgDCdwOAETUxRQ6nDouGfbTZvlwC8mHjn282DoUVTCiPO4xPA UJJ7HK7p8zmTCq8DZ84I8/awXiajpBHnGRFS4OVBmrx/MKmoJhnE61W2GKpKuHVAD5I9 4Wqw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:subject:thread-topic:thread-index :date:message-id:references:in-reply-to:accept-language :content-language:content-type:mime-version; bh=+rR8lkMbIC5AM7a18Dkj2b9aXqCAtYDecq9J1yYf1oE=; b=Fr5MhHP+qAqLfwF1VZhh588EyPrQcLR6YMFFmI3Us26oemozA9mo0gCzU+B/Z/6yVz ItNwnhAEN+1bCPD2y9ej/nRP2sTK2fqFGD9b4uJwhh512KWwrvK79SXzk3KOfoVs5FAZ 12o7TEoH98+suGfGeR4luWSvd5jGhXM/arr3aTr9jKSlXTHgqUqB/o2zBNFt+Ijvn2bO VxFbvM1hXLjMU0yRbbSxsUkFM/PVNmZgDdoFtOszPdQIMJooei5QW7Sy+I88aMJmFdrC b2A30IlUBj1JItDS60M/e34TIQ4JaPutlKk0YchA+NOi6Ii8ZMV6UBzzzw81QglX0NKg q6+w==
X-Gm-Message-State: ALoCoQl9Lic90ktfWZKpTy/8tESEkWbe9NDISHOh6V1FRvDvh6Lcs0A+JLatvSDfSpKYRoa5RnOcEVLnvFOgiirR58UWx/NOHMhYWfW1Pe//cNZPmxNKhmk=
X-Received: by 10.140.158.211 with SMTP id e202mr13920136qhe.81.1449675686398; Wed, 09 Dec 2015 07:41:26 -0800 (PST)
Received: from brn1lxmailout02.verisign.com (brn1lxmailout02.verisign.com. [72.13.63.42]) by smtp-relay.gmail.com with ESMTPS id y145sm1183037qka.12.2015.12.09.07.41.26 (version=TLS1 cipher=AES128-SHA bits=128/128); Wed, 09 Dec 2015 07:41:26 -0800 (PST)
X-Relaying-Domain: verisign.com
Received: from BRN1WNEXCHM01.vcorp.ad.vrsn.com (brn1wnexchm01 [10.173.152.255]) by brn1lxmailout02.verisign.com (8.13.8/8.13.8) with ESMTP id tB9FfO30014284 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 9 Dec 2015 10:41:25 -0500
Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by BRN1WNEXCHM01.vcorp.ad.vrsn.com ([::1]) with mapi id 14.03.0174.001; Wed, 9 Dec 2015 10:41:22 -0500
From: "Gould, James" <JGould@verisign.com>
To: Declan Ma <madi@zdns.cn>
Thread-Topic: [eppext] Recharter Milestones discussion
Thread-Index: AQHRLoRHCbKgve9FKUykWj9dwYlRfp6/N66AgAJkbICAAAfIAIABdsEAgAAMQIA=
Date: Wed, 9 Dec 2015 15:41:21 +0000
Message-ID: <B2962FC0-4D4C-43D9-868A-05FB44F5BEA1@verisign.com>
References: <F8238C95-4212-419A-BDE3-913E5CA6F99F@antoin.nl> <054701d130a0$73a37d90$5aea78b0$@cn> <D10C1316-9C6A-4477-B7E3-6AC894B07329@zdns.cn> <D459E0AD-006E-4C64-AC18-F33F6CB0C12D@verisign.com> <DD620164-DD96-46DD-83B1-3F0368F06DA0@zdns.cn>
In-Reply-To: <DD620164-DD96-46DD-83B1-3F0368F06DA0@zdns.cn>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [10.173.152.4]
Content-Type: multipart/related; boundary="_004_B2962FC04D4C43D9868A05FB44F5BEA1verisigncom_"; type="multipart/alternative"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/eppext/jKGGX1B6ND2PvthQUw1wo_uWqGY>
Cc: Linlin Zhou <zhoulinlin@cnnic.cn>, eppext <eppext@ietf.org>, Antoin Verschuren <ietf@antoin.nl>
Subject: Re: [eppext] Recharter Milestones discussion
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, 09 Dec 2015 15:41:31 -0000

Di,

I’m not aware of any technical limitations with EPP that would makes it unsuitable for passing the verification materials.  We previously discussed the applicability of EPP for this on the list.  Below are the relevant posts:


  1.  My reply to Linlin Zhou - http://www.ietf.org/mail-archive/web/eppext/current/msg00805.html
  2.  Scott Hollenbeck’s reply to Linlin Zhou - http://www.ietf.org/mail-archive/web/eppext/current/msg00809.html

Do you have any technical concerns with the use of EPP for this?

Thanks,


—


JG


[cid:77031CC3-BE7A-4188-A95F-D23115A30A4D@vcorp.ad.vrsn.com]

James Gould
Distinguished Engineer
jgould@Verisign.com

703-948-3271
12061 Bluemont Way
Reston, VA 20190

VerisignInc.com<http://VerisignInc.com>

On Dec 9, 2015, at 9:57 AM, Declan Ma <madi@zdns.cn<mailto:madi@zdns.cn>> wrote:


在 2015年12月9日,00:36,Gould, James <JGould@verisign.com<mailto:JGould@verisign.com>> 写道:

The proposal is to move draft-gould-eppext-verificationcode as a standards track WG document to define the locality verification framework, and to include draft-xie-eppext-nv-mapping as a concrete informational draft applicable to China.  This way the framework can be discussed along with a concrete implementation of the framework.

I think the framework offered by your draft is brilliant and is shedding lights on the R&D work in my team. I support it adopted as WG item.

Besides, many registry operators in China, enlightened by your draft, are working on their implementations of verification mechanisms.


Do you have feedback on the contents of draft-xie-eppext-nv-mapping?


I also appreciate the innovation of nv draft.

Granted, my concern is that using EPP to transport verification materials, pictures for instance, changes the light-weight EPP operation practice.

Di,


Thanks,

—

JG


<BF09FAA4-32D8-46E0-BED0-CD72F43BD6E0[81].png>

James Gould
Distinguished Engineer
jgould@Verisign.com<mailto:jgould@Verisign.com>

703-948-3271
12061 Bluemont Way
Reston, VA 20190

VerisignInc.com

On Dec 8, 2015, at 11:08 AM, Declan Ma <madi@zdns.cn> wrote:



在 2015年12月7日,11:36,Linlin Zhou <zhoulinlin@cnnic.cn> 写道:

Dear chair,
Thanks for your work to propose the discussion.

I agree that the WG needs a milestone and schedule, since we do not have so
much time to work on these existing documents in parallel. In my opinion,
the logical working process of a draft is that first calling for WG
adoption, approved by WG (discussed and supported on the mailing list or at
the f2f meeting), included in the milestone, etc.. I believe that all the
document should follow the clear working path. If a document has opposed
comments, whether or not we should discuss the technical stuff first and
pend the document included in the charter. The nv draft as a single
informational document, which is related to some Chinese local policies, I
still do not see a clarified consensus on it. Shall we discuss if the
document is qualified to be a WG document?


Linlin,

I quite agree with you, speaking as a technical guy from Chinese DNS industry.

Since the nv draft bears relevances to the local policies in China and is intended to be Informational, thorough discussions are indispensable to see whether it is qualified to be a WG item.

It’s unwise to jump into the decision of putting nv draft in milestone and to-do list.


Di Ma

ZDNS

http://en.zdns.cn


_______________________________________________
EppExt mailing list
EppExt@ietf.org
https://www.ietf.org/mailman/listinfo/eppext

_______________________________________________
EppExt mailing list
EppExt@ietf.org
https://www.ietf.org/mailman/listinfo/eppext