IETF Logo Mail Archive

Re: [eppext] [IANA #826994] Registration request for EPP extension

"Hollenbeck, Scott" <shollenbeck@verisign.com> Tue, 16 June 2015 11:00 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 810A51B301D for <eppext@ietfa.amsl.com>; Tue, 16 Jun 2015 04:00:20 -0700 (PDT)
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 DkHzo-zRWAW1 for <eppext@ietfa.amsl.com>; Tue, 16 Jun 2015 04:00:18 -0700 (PDT)
Received: from mail-oi0-f98.google.com (mail-oi0-f98.google.com [209.85.218.98]) (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 128151B3017 for <eppext@ietf.org>; Tue, 16 Jun 2015 04:00:18 -0700 (PDT)
Received: by oiav1 with SMTP id v1so648208oia.3 for <eppext@ietf.org>; Tue, 16 Jun 2015 04:00:17 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:subject:thread-topic:thread-index:date :message-id:references:in-reply-to:accept-language:content-language :content-type:content-transfer-encoding:mime-version; bh=WziY84UnK12KBj9fXcOvHcB2MOrcfMGNX3Lb96nbF8s=; b=He+wKVVtEJU1XNDt9ZfFmr8Ox7EsAqI3/E9VUDy/7IsH6Nbka7qMFWBEANZUezzjvS jCnqi7chmsrzAE2ZKNuqgxlaonNPfvtVL4wJ9KcFdpVBT1c5YzeWkYoMOT0rMwf5755W qMf0/A6pwYvhhYmSZ7ohp7kimG2iDl6YzAi3lBIYrWXBdMYdv1KBhoXDsOvUTT8kyaHx gPZ6tqx96lD8b7NnxjQ5TR7zxNwtUkmVzYx7FcJlRU1HhnNlfxxj8CFiwXXTZa5yu3Tz NaRBrGtHDtMFWvl4mJ7iGrY5Vy8fITOrcuYKg5r0Bt2TMGr2JgEP7VHcBThzn6KIyZOw cTJQ==
X-Gm-Message-State: ALoCoQm3GwCDa26H7cPKwnh3/PL3NZ/lJcZHv2VwpS21NvpjXBMhgFsjuWCVI59EBQcsEqKWAbiLH1i9t5/rf8M672EEHVN2tw==
X-Received: by 10.55.17.26 with SMTP id b26mr23328061qkh.93.1434452417415; Tue, 16 Jun 2015 04:00:17 -0700 (PDT)
Received: from brn1lxmailout01.verisign.com (brn1lxmailout01.verisign.com. [72.13.63.41]) by mx.google.com with ESMTPS id e4sm170345qcm.3.2015.06.16.04.00.16 (version=TLSv1 cipher=RC4-SHA bits=128/128); Tue, 16 Jun 2015 04:00:17 -0700 (PDT)
X-Relaying-Domain: verisign.com
Received: from brn1wnexcas01.vcorp.ad.vrsn.com (brn1wnexcas01 [10.173.152.205]) by brn1lxmailout01.verisign.com (8.13.8/8.13.8) with ESMTP id t5GB0ER3005950 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 16 Jun 2015 07:00:16 -0400
Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by brn1wnexcas01.vcorp.ad.vrsn.com ([::1]) with mapi id 14.03.0174.001; Tue, 16 Jun 2015 07:00:13 -0400
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
To: Mario Loffredo <mario.loffredo@iit.cnr.it>, "eppext@ietf.org" <eppext@ietf.org>
Thread-Topic: [eppext] [IANA #826994] Registration request for EPP extension
Thread-Index: AQHQnp56UkBWD8V2G0OxBbm+q9BBGZ2cACswgBIpK36AAOtjAP//9KTQ
Date: Tue, 16 Jun 2015 11:00:13 +0000
Message-ID: <831693C2CDA2E849A7D7A712B24E257F49FF69B2@BRN1WNEXMBX01.vcorp.ad.vrsn.com>
References: <RT-Ticket-826994@icann.org> <D195D022.ACE3%ulrich.wisser@iis.se> <rt-4.2.9-12728-1433405664-1101.826994-9-0@icann.org> <831693C2CDA2E849A7D7A712B24E257F49FECCC4@BRN1WNEXMBX01.vcorp.ad.vrsn.com> <831693C2CDA2E849A7D7A712B24E257F49FF55C6@BRN1WNEXMBX01.vcorp.ad.vrsn.com> <20150615213541.GA13131@home.patoche.org> <557FD27C.4010601@iit.cnr.it>
In-Reply-To: <557FD27C.4010601@iit.cnr.it>
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/N9fYlQqnkjxBEII6xNjiOtg_6GM>
Subject: Re: [eppext] [IANA #826994] Registration request for EPP extension
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: Tue, 16 Jun 2015 11:00:20 -0000

> -----Original Message-----
> From: EppExt [mailto:eppext-bounces@ietf.org] On Behalf Of Mario
> Loffredo
> Sent: Tuesday, June 16, 2015 3:39 AM
> To: eppext@ietf.org
> Subject: Re: [eppext] [IANA #826994] Registration request for EPP
> extension
> 
> Il 15/06/2015 23:35, Patrick Mevzek ha scritto:
> > Hollenbeck, Scott <shollenbeck@verisign.com> 2015-06-15 13:47
> >> An indirect comment: the need for VAT and national identifier
> information seems to be a common need for registries that operate in
> the EU. Does it make sense to develop a standard extension for them?
> > I personnally think so, including other contact data too.
> >
> > Based on the (mostly ccTLDs) EPP extensions I have seen working with
> > this kind of data, I was planning to write after the Stockholm EPP
> > workshop an extension to handle that,
> > and then starting the hard part on seeing how it could get
> implemented
> > by registries…
> >
> > I have not started that work yet, and if anyone has ideas and/or want
> > to help write the I-D, he/she is welcome.
> >
> We (as .it) would like to give our contribution to this discussion.
> I think we should collect all the extensions related to this topic
> (maybe in a set of mails with the apporpriate subject and, after, in a
> pre-draft document) before writing the first  draft.
> This could be useful to have an exhaustive survey and to catch
> similarities among proprietary extensions.

I'm glad to see some discussion - it's the first step in getting something done! One thought on Mario's suggestion: it would also be a good idea for anyone who has a related extension to *register* it.

Scott

v2.8.7 | Report a Bug | By Email