Rolling back the clock a bit here...
On Thu, May 26, 2022 at 11:11 AM John C Klensin wrote:
> First, it appears that it is making a more fundamental change to
> EPP than just allowing for SMTPUTF8 (aka "non-ASCII" or "EAI")
> addresses local parts. The second paragraph of the Introduction
>
On Mon, Sep 12, 2022 at 03:54:32PM +0200, Antoin Verschuren wrote:
> Dear Working Group,
>
> The authors of the following working group document have indicated
> that it is believed to be ready for submission to the IESG for
> publication as a standards track document:
>
>
Hello Gavin,
On 9/14/22 13:35, Gavin Brown wrote:
Greetings all,
Many years ago CentralNic had a proprietary EPP extension for managing
the TTL values of domain names. ...
However I've had a bit of feedback about the draft since then, so I've
just published a new version and am now sharing
Hey Jim,
> On 14 Sep 2022, at 13:35, Gould, James wrote:
>
> Gavin,
>
> Thank you for publishing a new version of the draft. I have the following
> feedback:
>
> • Shouldn’t the track be Standards Track instead of Experimental since
> this seems very straight forward?
Since it's
Gavin,
Thank you for publishing a new version of the draft. I have the following
feedback:
1. Shouldn’t the track be Standards Track instead of Experimental since this
seems very straight forward?
2. Shouldn’t the A and TTL apply to the Host object instead of the
Domain Name
Greetings all,
Many years ago CentralNic had a proprietary EPP extension for managing the TTL
values of domain names.
After the Philadelphia IETF meeting, I was contacted by some WG members about
reviving this extension for possible adoption.
So I created a new I-D to describe the extension
