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

"Gould, James" <> Thu, 05 November 2015 15:14 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 382921B2EC2 for <>; Thu, 5 Nov 2015 07:14:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 6EF1w18bn0bE for <>; Thu, 5 Nov 2015 07:14:02 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 9DF571B2EC1 for <>; Thu, 5 Nov 2015 07:13:27 -0800 (PST)
Received: by oigi82 with SMTP id i82so5371501oig.0 for <>; Thu, 05 Nov 2015 07:13:27 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; 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:content-transfer-encoding :mime-version; bh=eO3y8sqFmY53/fi22caPhqK1UUiUMJ6cESzWqRR29d8=; b=JTunvMDxFJCs897fWfof07ZqubGKYN7i5ah1Gu/8Yp8lMnDg/mcIUR9D8QoQ2R8Nja Vm+dNYA8O2VygoM1OqrunlXZlh+oFHwQl1d5g70/BWzwLjrgTVMKAfAprBSMpDzcfjy2 PttHvhRnGkKrH+0nojGadqNA6EOWXmiB63E5Fw6RpVVXtCRjpJjKg4Cxfrc+DQkX01vQ UmmWRFnNd2m5LSPYNtykP6T+oc+KLZmdpCDq7tGdqib/E9p6S7Trfk+WiADWINZ46s1a TzFnzNIAioHFtgWfhsb5/fOEk8i5UndyOd+a6fGBJuY8O56UCySMyTRjlspBKRRHh4vR 1cvw==
X-Gm-Message-State: ALoCoQl8QlNBaVqgix3kN7TUKsNJm+GIfh4I4PfcxdbJUYLB5sWXm2kIIBS5Z2sRDWJ7DVXj/16n1QUiIHd2uURefsZIm5GLNw==
X-Received: by with SMTP id 11mr7866168qgy.94.1446736406893; Thu, 05 Nov 2015 07:13:26 -0800 (PST)
Received: from ( []) by with ESMTPS id a202sm790931qkb.1.2015. (version=TLSv1 cipher=RC4-SHA bits=128/128); Thu, 05 Nov 2015 07:13:26 -0800 (PST)
Received: from (brn1wnexcas01 []) by (8.13.8/8.13.8) with ESMTP id tA5FDPXG011493 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 5 Nov 2015 10:13:26 -0500
Received: from ([::1]) by ([::1]) with mapi id 14.03.0174.001; Thu, 5 Nov 2015 10:13:24 -0500
From: "Gould, James" <>
To: Linlin Zhou <>
Thread-Topic: [eppext] Minutes for our meeting in Yokohama IETF94
Thread-Index: AQHRF6m9eK/y8o0l60m7mZABbgQMIp6NON3PgAB7sYCAAA5mgIAABZmAgAAPc4D//7G0pw==
Date: Thu, 05 Nov 2015 15:13:24 +0000
Message-ID: <>
References: <> <> <> <> <>, <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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 15:14:08 -0000


I do not see a technical issue with the EPP protocol passing large packets.  There is no specific performance numbers to dispel the concern, but I believe any packet size limitations would be based on server policy and the performance testing done by the server.  Since EPP rides on top of TCP and includes packet framing based on a network header, there really is no technical limitation that I am aware of.

Do you have any feedback on the interface elements?



Sent from my iPhone

> On Nov 5, 2015, at 9:53 AM, Linlin Zhou <> wrote:
> 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
> _______________________________________________
> EppExt mailing list