Re: [eppext] Minutes for our meeting in Yokohama IETF94

"Linlin Zhou" <> Thu, 05 November 2015 13:38 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 46DE61B2C2D for <>; Thu, 5 Nov 2015 05:38:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.612
X-Spam-Status: No, score=-2.612 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 51YPVXNP4Izd for <>; Thu, 5 Nov 2015 05:38:27 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id 518121B2C25 for <>; Thu, 5 Nov 2015 05:38:25 -0800 (PST)
Received: by (Coremail) ; Thu, 5 Nov 2015 21:38:19 +0800 (GMT+08:00)
X-CM-HeaderCharset: UTF-8
X-Originating-IP: []
Date: Thu, 05 Nov 2015 21:38:19 +0800
From: Linlin Zhou <>
To: "Gould, James" <>
X-Priority: 3
X-Mailer: Coremail Webmail Server Version XT3.0.5b dev build 20150108(58896.7041) Copyright (c) 2002-2015 cnnic
In-Reply-To: <>
References: <> <> <>
X-SendMailWithSms: false
Content-Transfer-Encoding: base64
Content-Type: text/plain; charset="UTF-8"
MIME-Version: 1.0
Message-ID: <>
X-CM-TRANSID: AQAAf0BpcDjLWztW_cRyBg--.1818W
X-CM-SenderInfo: p2kr3zplqox0w6fq0xffof0/1tbiAQAEBiVCNzp9qAABs9
X-Coremail-Antispam: 1Ur529EdanIXcx71UUUUU7IcSsGvfJ3iIAIbVAYjsxI4VWxJw CS07vEb4IE77IF4wCS07vE1I0E4x80FVAKz4kxMIAIbVAFxVCaYxvI4VCIwcAKzIAtYxBI daVFxhVjvjDU=
Archived-At: <>
Cc: Ulrich Wisser <>, "" <>
Subject: Re: [eppext] Minutes for our meeting in Yokohama IETF94
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: EPPEXT <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 05 Nov 2015 13:38:29 -0000

Dear James,
> > 
> > On Nov 5, 2015, at 5:24 AM, Linlin Zhou <> wrote:
> > 
> > 
> > Dear Ulrich,
> > Thanks for the hardwork for taking meeting minutes. However, I feel that two points may be missed.
> > 1. We have hum for adopting informational drafts in WG charter, but to the particular two drafts of verification signedcode and nv document, the WG seems having no clear cosensus on adopting them. Although it showed up in the milestone slide.
> The hum’s where associated with the informational drafts, which does not include the verificationcode draft since it is defined as standards track.  There was no expressed issue with the WG adopting the verificationcode draft.  It was agreed that informational track drafts can be brought into the WG.  

Sorry, my mistake. Verificationcode draft is standards track. So we have not reached consensus on the nv draft adoption.
> > 
> > 
> > 2. I recalled my memory that several people have comments on nv draft and it seems not be fully supported. Minutes does not include these records.
> > 
> > 
> There was not clear consensus on the nv draft since it was defined as informational and there was the question of applicability for the WG.  The verificationcode draft defines a standard framework for applying local verification policies where the nv draft defines a concrete use case for China.  Based on the number of registrars and registries that will need to address the verification regulations in China and potentially in other countries, I believe that it’s important for the WG to address the standards track verificationcode draft as well as the concrete use case for China with the nv draft.  

I feel that verificationcode draft is more like a general method which could be used for real name verification or anything else verification. But the local verification policies in China is really somthing complex that the nv draft may not be the best choice. Many Chinese registrars and registries already implemented some other interface based on HTTP. If WG indeed wants some standards to address this scenario over EPP, I am skepticle on whether EPP is appropriate to transfer large image files as I said in the Jabber room.