IETF Logo Mail Archive

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

Patrick Mevzek <pm@dotandco.com> Mon, 15 June 2015 21:35 UTC

Return-Path: <patrick@shaktot.patoche.org>
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 191E71B2AC0 for <eppext@ietfa.amsl.com>; Mon, 15 Jun 2015 14:35:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.512
X-Spam-Level:
X-Spam-Status: No, score=-0.512 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, 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 4HyyLK9-_Bd2 for <eppext@ietfa.amsl.com>; Mon, 15 Jun 2015 14:35:55 -0700 (PDT)
Received: from shaktot.patoche.org (shaktot.patoche.org [212.85.152.86]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0AA761B2AC6 for <eppext@ietf.org>; Mon, 15 Jun 2015 14:35:54 -0700 (PDT)
Received: from shaktot.patoche.org (localhost.localdomain [127.0.0.1]) by shaktot.patoche.org (8.14.3/8.14.3/Debian-9.4) with ESMTP id t5FLZid3019036 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 15 Jun 2015 23:35:44 +0200
Received: (from patrick@localhost) by shaktot.patoche.org (8.14.3/8.14.3/Submit) id t5FLZi4D019035; Mon, 15 Jun 2015 23:35:44 +0200
Date: Mon, 15 Jun 2015 23:35:41 +0200
From: Patrick Mevzek <pm@dotandco.com>
To: "eppext@ietf.org" <eppext@ietf.org>
Message-ID: <20150615213541.GA13131@home.patoche.org>
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>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <831693C2CDA2E849A7D7A712B24E257F49FF55C6@BRN1WNEXMBX01.vcorp.ad.vrsn.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-Scanned-By: shaktot_dot_patoche_dot_org on 212.85.152.86
Archived-At: <http://mailarchive.ietf.org/arch/msg/eppext/ri3ecJGKaAux6REDJQD98FIo2Zc>
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: Mon, 15 Jun 2015 21:35:57 -0000

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.

-- 
Patrick Mevzek

v2.8.7 | Report a Bug | By Email