Re: [regext] WGLC: draft-ietf-regext-org-02

Patrick Mevzek <pm@dotandco.com> Mon, 28 May 2018 20:48 UTC

Return-Path: <pm@dotandco.com>
X-Original-To: regext@ietfa.amsl.com
Delivered-To: regext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8ABBD12D88A for <regext@ietfa.amsl.com>; Mon, 28 May 2018 13:48:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=dotandco.com header.b=nl3ax1My; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=XKd/pOPL
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 3LfFzHYVX-1A for <regext@ietfa.amsl.com>; Mon, 28 May 2018 13:48:27 -0700 (PDT)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 08FD812D88B for <regext@ietf.org>; Mon, 28 May 2018 13:48:27 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id AE1BC21C73 for <regext@ietf.org>; Mon, 28 May 2018 16:48:25 -0400 (EDT)
Received: from web3 ([10.202.2.213]) by compute3.internal (MEProxy); Mon, 28 May 2018 16:48:25 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dotandco.com; h= content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm3; bh=UIXFmLKH+OEMjnDppaDwJDbfE9Q3y 5FM80srJeeHNxs=; b=nl3ax1MyjHvCvwaLjtgOgRHtXn2MeMMozeHrYQ4mwpBGY sYwmaUAYtVtwt4iQpQpXyC1nbdi1GnJ6/QJ4kTAWh4Mp7wH86n0kxhRAXYZd8nW5 MAeY9qT/xxsxWYkEKsF2q5TaI7aEt8wewumj8D8A/XIeLUqUIgpABJFKuDXaGxE1 WH819O/NEd68Iv6tn/gTI/4QMhvzLjuwTky2Saqn7I9HsyMY9fbIlK6DRUqtViHg etMksb/FNcrcNMKRaFAH4IeZykTGarvRW0fNMSkEYukv9brSe8cyuOrB61vbvxz/ bQjzFC0+4HZLCUiNnbtzOiMg3slGtgUxHZUukVzVQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=UIXFmL KH+OEMjnDppaDwJDbfE9Q3y5FM80srJeeHNxs=; b=XKd/pOPL5vii6kx4BHB5PO h52dGwllhQvI2lJOj10lE7JSFRZss0zqZN7Xk0zQA3laI/r1T1iZy8L5/Weuxcbw mVX4T/dda4M3ChdWuY4rNwOOyR08ocHBBW8zdxyP45SJ6eTayCqZO9xIfyTD+gwl 1KfA+DLrUm3b9E5MWpl2Whzy0GrmIK2ru5s8rxFOGsrCZVm2fq2Xd31ZSOZd23pE 5u7xzEwnq2e2TqIYgWUkUmvQzufU7QBKmeai64ZM/Y3tSqDX1HXbzf9PTwYLdF75 O+DworUcNYsyvGJ1T5qC9YLgmdNH4ivZZT9AGwxkz3Uwj4nvCmgmUut6cZN6TqUg ==
X-ME-Proxy: <xmx:GWsMW48pe1jtp7UbR5beMS0WFuc4tCS-nijqEKc6ce2Gwd3RjGY2Zw>
X-ME-Proxy: <xmx:GWsMW9dVAET_RF8ugIpffrJkX103jbjp1-607pTEDrg5sPPbuS-h5g>
X-ME-Proxy: <xmx:GWsMW9mAmZ2jAbAStWr2uJqYZTxfzWVCuJy8Awm5k97SrytmMwAsRQ>
X-ME-Proxy: <xmx:GWsMWxEtj82GGZlVgFBzD0683KapxueFwTXwopZRx_GvLekluM3kgw>
X-ME-Proxy: <xmx:GWsMWxfZiflHli4TmIJ6TXPNKYpTktKDXChKWZ_KAlotLU8ukB0yWg>
X-ME-Proxy: <xmx:GWsMW-J6eEnjpS8uQoJ0gUncg2xBkLlf4kfjr3zJUPHf3r9nZrA4zw>
X-ME-Sender: <xms:GWsMW2LUTjh5x0QtUdXKsm6CzKzgWbOe5VVEG8u2uQw3Hp3mWTNmKqEPPEE>
Received: by mailuser.nyi.internal (Postfix, from userid 99) id 74A699E165; Mon, 28 May 2018 16:48:25 -0400 (EDT)
Message-Id: <1527540505.157331.1388343424.0B8EF8F3@webmail.messagingengine.com>
From: Patrick Mevzek <pm@dotandco.com>
To: regext@ietf.org
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"
X-Mailer: MessagingEngine.com Webmail Interface - ajax-397f98d6
References: <80ED56C6-75F7-4DED-927B-E0AB528A71EE@elistx.com> <656C123C-9ECF-434D-948D-4E704ED3E75C@elistx.com> <1526872740.790268.1378875200.662ECDF2@webmail.messagingengine.com> <A9E94F6D-1C51-47C4-B74D-22D40841317C@dnsbelgium.be> <B0F071B4-DF2D-4E46-9002-C7FFAA5DAC25@dnsbelgium.be> <1527140656.2870129.1382989368.51CB4B29@webmail.messagingengine.com> <E200CA5E-FB32-4767-B837-35560EA0EF06@dnsbelgium.be> <DA1F19C3-209A-40B7-A872-21582D25A5A1@verisign.com> <1D86FAEA-9A4D-4BD8-B280-067FFAEB3D54@antoin.nl> <1527448997.1643063.1387308680.73816387@webmail.messagingengine.com> <0ADC1E6A-87BF-4C27-B982-EB43FAEB4916@antoin.nl> <1527540044.154247.1388335520.68ECC648@webmail.messagingengine.com>
In-Reply-To: <1527540044.154247.1388335520.68ECC648@webmail.messagingengine.com>
Date: Mon, 28 May 2018 22:48:25 +0200
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/5xGTeQGQN53mSHeqkBtmOuDfVXI>
Subject: Re: [regext] WGLC: draft-ietf-regext-org-02
X-BeenThere: regext@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Registration Protocols Extensions <regext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/regext>, <mailto:regext-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/regext/>
List-Post: <mailto:regext@ietf.org>
List-Help: <mailto:regext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/regext>, <mailto:regext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 28 May 2018 20:48:29 -0000

Antoin,

On Mon, May 28, 2018, at 22:40, Patrick Mevzek wrote:
> 
> 
> On Mon, May 28, 2018, at 21:29, Antoin Verschuren wrote:
> > Op 27 mei 2018, om 21:23 heeft Patrick Mevzek <pm@dotandco.com> het 
> > volgende geschreven:
> > 
> > > This is covered I think in ICANN world by section 1.4.2 of the whois specification:
> > > 
> > > "Additional data elements can be added at the end of the text format outlined below.”
> > 
> > Ah yes, let’s take the solution of "we can put everything in one non-
> > parseble TXT record like DNS can do too if we fail proper design and 
> > really want to” ;-)
> > Sorry for the sarcasm Patrick, but that one was a too open goal ;-)
> 
> I am not sure to see where in the text it says that formatted content is 
> forbidden, can you pinpoint it to me?
> 
> Also, I fail to see how any EPP extension would have any impact here
> (in the sense that: you can change what is displayed in whois 
> irrespective to what happens on the EPP channel).

In your quote you missed the other part which is basically: all domain names are not under ICANN policies.

So for all other TLDs currently can you let me know which protocol limitations currently forbid registry to add formatted content in their whois or, let us say just decide to implement RDAP to start with? Do you really think there are almost none because of protocol limitations, especially in the EPP channel, or maybe for other reasons?

-- 
  Patrick Mevzek