IETF Logo Mail Archive

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

"Hollenbeck, Scott" <shollenbeck@verisign.com> Thu, 05 November 2015 17:38 UTC

Return-Path: <shollenbeck@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 F2BF01B31A8 for <eppext@ietfa.amsl.com>; Thu, 5 Nov 2015 09:38:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
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 mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id j82sualiTo2f for <eppext@ietfa.amsl.com>; Thu, 5 Nov 2015 09:38:43 -0800 (PST)
Received: from mail-qg0-f99.google.com (mail-qg0-f99.google.com [209.85.192.99]) (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 D116C1B31AA for <EppExt@ietf.org>; Thu, 5 Nov 2015 09:38:36 -0800 (PST)
Received: by qgeb1 with SMTP id b1so1659945qge.0 for <EppExt@ietf.org>; Thu, 05 Nov 2015 09:38:35 -0800 (PST)
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:content-transfer-encoding :mime-version; bh=na6plXMwUivvN4Je0NH/8S33LYb4OnamEblMzFMugl0=; b=kQsmd62mMGAthFgWadMdzLW71G0C1y/HQWNjyXfQpa10kiR1+LSBgWZYe1ESQYs5Jq c8zwuDZH5I7aotLlNnpuR1lgB98TVCSsWnWQ9ZwENWesdr4vb6e5CxLNnQuiOiWvKjg2 DxH4MgMLrAnWxcNO+BTJkEVVRmnaa5DkNusLF5OmNeCkFemAqzCJzeb6ZK50AQSs6a4N RRmeefGwUikxA5Dkq6Eip6xr7aOHPCVE6xNOJmAO2gbCXXZnHQSeq116uAgHZv5KP54p 8KDE1gKsoBdt1e2w2U67NuXxHhGntcH8bkXXRTNcB06ARxLP1hUyQMfB/HgUskFO2vZe DxKA==
X-Gm-Message-State: ALoCoQnjFQTH47WFVIyam5+OEakmRxFaipgifQ23PmkLvAB1zKJBK46mcjtaiigSqeiujYvkC2Geaff1FC2mkoIZIRxqGqzpxw==
X-Received: by 10.140.25.166 with SMTP id 35mr8933891qgt.96.1446745115501; Thu, 05 Nov 2015 09:38:35 -0800 (PST)
Received: from brn1lxmailout01.verisign.com (brn1lxmailout01.verisign.com. [72.13.63.41]) by smtp-relay.gmail.com with ESMTPS id a202sm862164qkb.1.2015.11.05.09.38.35 (version=TLSv1 cipher=RC4-SHA bits=128/128); Thu, 05 Nov 2015 09:38:35 -0800 (PST)
X-Relaying-Domain: verisign.com
Received: from brn1wnexcas02.vcorp.ad.vrsn.com (brn1wnexcas02 [10.173.152.206]) by brn1lxmailout01.verisign.com (8.13.8/8.13.8) with ESMTP id tA5HcYOE014695 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 5 Nov 2015 12:38:35 -0500
Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by brn1wnexcas02.vcorp.ad.vrsn.com ([::1]) with mapi id 14.03.0174.001; Thu, 5 Nov 2015 12:38:34 -0500
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
To: Linlin Zhou <zhoulinlin@cnnic.cn>, "Gould, James" <JGould@verisign.com>
Thread-Topic: [eppext] Minutes for our meeting in Yokohama IETF94
Thread-Index: AQHRF6m98fxenGRVsUiFwVQJCJX+Vp6NONwUgAB7soCAAA5mgIAABZoAgAAPcoD//9jF4A==
Date: Thu, 05 Nov 2015 17:38:33 +0000
Message-ID: <831693C2CDA2E849A7D7A712B24E257F4A0DB3D9@BRN1WNEXMBX01.vcorp.ad.vrsn.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> <17bec963.ae3.150d8238c7f.Coremail.zhoulinlin@cnnic.cn>
In-Reply-To: <17bec963.ae3.150d8238c7f.Coremail.zhoulinlin@cnnic.cn>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.173.152.4]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/eppext/PqJ4dwWMBJ2VQLN_--hBu31FCew>
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 17:38:45 -0000

> -----Original Message-----
> From: EppExt [mailto:eppext-bounces@ietf.org] On Behalf Of Linlin Zhou
> Sent: Thursday, November 05, 2015 9:54 AM
> To: Gould, James
> Cc: Ulrich Wisser; eppext@ietf.org
> Subject: Re: [eppext] Minutes for our meeting in Yokohama IETF94
> 

[snip]

> > 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.

A correct implementation of EPP should not have any issues with encoded image files. If anything, it's a more efficient transport than a web service API (I believe I heard that mentioned as an alternative method) because there is no HTTP layer above TCP. One less software layer *should* be more efficient.

If TCP and your XML library can do it, EPP can do it.

Scott

v2.23.0 | Report a Bug | By Email