Re: [eppext] [tmch-tech] Type of encoding attribute in draft-lozano-tmch-smd-03
"Gould, James" <JGould@verisign.com> Wed, 05 March 2014 16:09 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 726C81A01EB for <eppext@ietfa.amsl.com>; Wed, 5 Mar 2014 08:09:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-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 0IP2PJEDjsdO for <eppext@ietfa.amsl.com>; Wed, 5 Mar 2014 08:09:10 -0800 (PST)
Received: from exprod6og120.obsmtp.com (exprod6og120.obsmtp.com [64.18.1.236]) by ietfa.amsl.com (Postfix) with ESMTP id 48CFE1A0502 for <eppext@ietf.org>; Wed, 5 Mar 2014 08:08:42 -0800 (PST)
Received: from osprey.verisign.com ([216.168.239.75]) (using TLSv1) by exprod6ob120.postini.com ([64.18.5.12]) with SMTP ID DSNKUxdMBgzrmKdFGwnzdZLYfIex0QQe2+AX@postini.com; Wed, 05 Mar 2014 08:09:01 PST
Received: from brn1wnexcas01.vcorp.ad.vrsn.com (brn1wnexcas01.vcorp.ad.vrsn.com [10.173.152.205]) by osprey.verisign.com (8.13.6/8.13.4) with ESMTP id s25G8bMk021734 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 5 Mar 2014 11:08:38 -0500
Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by brn1wnexcas01.vcorp.ad.vrsn.com ([::1]) with mapi id 14.03.0123.003; Wed, 5 Mar 2014 11:08:37 -0500
From: "Gould, James" <JGould@verisign.com>
To: Patrick Mevzek <Patrick.Mevzek@afnic.fr>, "tmch-tech@icann.org" <tmch-tech@icann.org>
Thread-Topic: [tmch-tech] Type of encoding attribute in draft-lozano-tmch-smd-03
Thread-Index: AQHPOIft8VG47mdNNkSdmXA1WXOBEJrSqToA
Date: Wed, 05 Mar 2014 16:08:37 +0000
Message-ID: <CF3CB1E1.58C3C%jgould@verisign.com>
In-Reply-To: <1394033312.26535.62.camel@citrine>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.3.6.130613
x-originating-ip: [10.173.152.4]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <3DEFF1C438792349A6889799624E722E@verisign.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/eppext/ZldNplSlkSo9Lgz0sMkP4S10YzU
Cc: "eppext@ietf.org" <eppext@ietf.org>
Subject: Re: [eppext] [tmch-tech] Type of encoding attribute in draft-lozano-tmch-smd-03
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: <http://www.ietf.org/mail-archive/web/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, 05 Mar 2014 16:09:12 -0000
Patrick, I support adding the type=³token² to the encoding attribute in draft-ietf-eppext-tmch-smd. I tested the change using the Verisign EPP SDK with no issue. To note, draft-lozano-tmch-smd has been moved to draft-ietf-eppext-tmch-smd and draft-tan-epp-launchphase has been moved to draft-ietf-eppext-launchphase, since they are being moved forward with the new eppext WG. I¹ve copied the eppext mailing list on this reply and my prior reply to your posting associated with draft-ietf-eppext-launchphase. -- JG James Gould Principal Software Engineer jgould@verisign.com 703-948-3271 (Office) 12061 Bluemont Way Reston, VA 20190 VerisignInc.com On 3/5/14, 10:28 AM, "Patrick Mevzek" <Patrick.Mevzek@afnic.fr> wrote: >Hello, > >One of my colleague remarks that this definition : > <complexType name="encodedSignedMarkType"> > <simpleContent> > <extension base="token"> > <attribute name="encoding" default="base64"/> > </extension> > </simpleContent> > </complexType> > >may lack a type for the encoding attribute. >Without this, some XML frameworks (such as SOAP::WSDL in Perl) can not >use this definition. >Just changing it to ><attribute name="encoding" type="token" default="base64"/> >solves the problem. > >-- >Patrick Mevzek >
- Re: [eppext] [tmch-tech] Type of encoding attribu… Gould, James
- Re: [eppext] [tmch-tech] Type of encoding attribu… Michael Holloway
- Re: [eppext] [tmch-tech] Type of encoding attribu… James Galvin
- Re: [eppext] [tmch-tech] Type of encoding attribu… Antoin Verschuren