IETF Logo Mail Archive

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

"Linlin Zhou" <zhoulinlin@cnnic.cn> Thu, 05 November 2015 14:53 UTC

Return-Path: <zhoulinlin@cnnic.cn>
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 4A9DB1B2E3D for <eppext@ietfa.amsl.com>; Thu, 5 Nov 2015 06:53:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.612
X-Spam-Level:
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 mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1PXoVPqnJz7U for <eppext@ietfa.amsl.com>; Thu, 5 Nov 2015 06:53:46 -0800 (PST)
Received: from cnnic.cn (smtp13.cnnic.cn [218.241.118.13]) by ietfa.amsl.com (Postfix) with ESMTP id 725461B2E3A for <eppext@ietf.org>; Thu, 5 Nov 2015 06:53:45 -0800 (PST)
Received: by ajax-webmail-ocmail02.zx.nicx.cn (Coremail) ; Thu, 5 Nov 2015 22:53:39 +0800 (GMT+08:00)
X-CM-HeaderCharset: UTF-8
X-Originating-IP: [218.241.102.150]
Date: Thu, 05 Nov 2015 22:53:39 +0800
From: Linlin Zhou <zhoulinlin@cnnic.cn>
To: "Gould, James" <JGould@verisign.com>
X-Priority: 3
X-Mailer: Coremail Webmail Server Version XT3.0.5b dev build 20150108(58896.7041) Copyright (c) 2002-2015 www.mailtech.cn cnnic
In-Reply-To: <1CE7A0FE-DAC8-4757-A131-340047FAB812@verisign.com>
References: <CAJ9-zoXEL_QMsGJ1ZkNr61VHqXRCFCR8o6_UHO7vZxRtV-ZL=w@mail.gmail.com> <2015110518242454766331@cnnic.cn> <C0004164-F535-4AB4-A9E6-A534BCAD266D@verisign.com> <17335b97.ad9.150d7de92ea.Coremail.zhoulinlin@cnnic.cn> <1CE7A0FE-DAC8-4757-A131-340047FAB812@verisign.com>
X-SendMailWithSms: false
Content-Transfer-Encoding: base64
Content-Type: text/plain; charset="UTF-8"
MIME-Version: 1.0
Message-ID: <17bec963.ae3.150d8238c7f.Coremail.zhoulinlin@cnnic.cn>
X-CM-TRANSID: AQAAf0DJ0DhzbTtWAFV0Bg--.1750W
X-CM-SenderInfo: p2kr3zplqox0w6fq0xffof0/1tbiAQAEBiVCNzp+JwAAsw
X-Coremail-Antispam: 1Ur529EdanIXcx71UUUUU7IcSsGvfJ3iIAIbVAYjsxI4VWxJw CS07vEb4IE77IF4wCS07vE1I0E4x80FVAKz4kxMIAIbVAFxVCaYxvI4VCIwcAKzIAtYxBI daVFxhVjvjDU=
Archived-At: <http://mailarchive.ietf.org/arch/msg/eppext/YKhPCRrKHewhTjWLmIa56I6SaOc>
Cc: Ulrich Wisser <ulrich@wisser.se>, "eppext@ietf.org" <EppExt@ietf.org>
Subject: Re: [eppext] Minutes for our meeting in Yokohama IETF94
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: Thu, 05 Nov 2015 14:53:48 -0000

Hi James,
> I really don’t understand the concern related to passing large image files via EPP.  There is no technical reason why EPP cannot include elements that happen to contain a large amount of data to satisfy a specific provisioning use case.   In this case the client is attempting to create a signed code based on the verification of the input, which can include information like scanned images.  
> 
> 
> Do you have any specific technical limitation with EPP that will not work for this? 
>  
> Do you know of a standards track HTTP interface for Chinese verification that can be used to help with what is defined in the nv draft?  
> 
> 
> Do you have any specific feedback on the elements that are passed with the nv draft other then the size of the image files?  
> 
I just express my cocern about the large file transfer on EPP, after all the package size will increase sharply. Or do you have any performance test data on transfer image files over EPP to dispel my worries. Many thanks.

Regards,
Linlin

v2.29.0 | Report a Bug | By Email | System Status