IETF Logo Mail Archive

Re: [ietf-provreg] Presentation on EPP present and future

Andrew Sullivan <ajs@shinkuro.com> Thu, 24 June 2010 15:57 UTC

Return-Path: <owner-ietf-provreg@cafax.se>
X-Original-To: ietfarch-provreg-archive@core3.amsl.com
Delivered-To: ietfarch-provreg-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id ECADF3A67CF for <ietfarch-provreg-archive@core3.amsl.com>; Thu, 24 Jun 2010 08:57:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.038
X-Spam-Level: *
X-Spam-Status: No, score=1.038 tagged_above=-999 required=5 tests=[AWL=0.687, BAYES_50=0.001, HELO_EQ_SE=0.35]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Uaa3f5z4-tuZ for <ietfarch-provreg-archive@core3.amsl.com>; Thu, 24 Jun 2010 08:57:40 -0700 (PDT)
Received: from nic.cafax.se (nic.cafax.se [192.71.228.17]) by core3.amsl.com (Postfix) with ESMTP id E18BB3A6403 for <provreg-archive@ietf.org>; Thu, 24 Jun 2010 08:57:39 -0700 (PDT)
Received: from nic.cafax.se (localhost [127.0.0.1]) by nic.cafax.se (8.13.7/8.12.11) with ESMTP id o5OFjDRJ026815 for <ietf-provreg-outgoing@nic.cafax.se>; Thu, 24 Jun 2010 17:45:13 +0200 (MEST)
Received: (from majordom@localhost) by nic.cafax.se (8.13.7/8.12.11/Submit) id o5OFjDge008007 for ietf-provreg-outgoing; Thu, 24 Jun 2010 17:45:13 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-ietf-provreg@cafax.se using -f
Received: from mail.yitter.info (mail.yitter.info [208.86.224.201]) by nic.cafax.se (8.13.7/8.12.11) with ESMTP id o5OFjC6O005735 for <ietf-provreg@cafax.se>; Thu, 24 Jun 2010 17:45:13 +0200 (MEST)
Received: from crankycanuck.ca (69-196-144-230.dsl.teksavvy.com [69.196.144.230]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.yitter.info (Postfix) with ESMTPSA id 9C5FF1ECB408 for <ietf-provreg@cafax.se>; Thu, 24 Jun 2010 15:45:11 +0000 (UTC)
Date: Thu, 24 Jun 2010 11:45:09 -0400
From: Andrew Sullivan <ajs@shinkuro.com>
To: 'EPP Provreg' <ietf-provreg@cafax.se>
Subject: Re: [ietf-provreg] Presentation on EPP present and future
Message-ID: <20100624154509.GP1239@shinkuro.com>
Mail-Followup-To: Andrew Sullivan <ajs@shinkuro.com>, 'EPP Provreg' <ietf-provreg@cafax.se>
References: <20100623190057.GM23071@home.patoche.org> <00bb01cb132a$b79e4c30$26dae490$@afilias.info> <AB7E314C-630B-42D1-B21C-B85663273D04@cisco.com> <4C230989.4020707@publisher.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <4C230989.4020707@publisher.de>
User-Agent: Mutt/1.5.18 (2008-05-17)
Sender: owner-ietf-provreg@cafax.se
Precedence: bulk

On Thu, Jun 24, 2010 at 09:30:17AM +0200, Ulrich Wisser wrote:
> The nice thing about all the extensions in the wild is, that we are now  
> seeing real world business needs for EPP. We could try to filter out a  
> common set of extensions needs and create one or more new standard  
> extensions.

One way to tackle this would be for someone to put together
draft-epp-common-profile that would outline the extensions (including
-- or not -- the base domain, host, contact extensions) that support
the widest interoperation.  That is not actually a change to the
protocol as such, though it is of course an overall change to the
operating protocol as deployed.

I think it would be very helpful to have a draft that one could
discuss, however.  But since I work for neither a registry nor a
(real) registrar, I'm not offering to write it.

A

-- 
Andrew Sullivan
ajs@shinkuro.com
Shinkuro, Inc.
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
List run by majordomo software.  For (Un-)subscription and similar details
send "help" to ietf-provreg-request@cafax.se

v2.23.0 | Report a Bug | By Email