Please add me to the list also. Thanks, Jody Kolker 319-294-3933 (office) 319-329-9805 (mobile) This email message and any attachments hereto is intended for use only by the addressee(s) named herein and may contain confidential information. If you have received this email in error, please immediately notify the sender and permanently delete the original and any copy of this message and its attachments.
From: regext <regext-boun...@ietf.org> On Behalf Of Tim Wicinski Sent: Monday, October 28, 2019 10:08 AM To: Hollenbeck, Scott <shollenbeck=40verisign....@dmarc.ietf.org> Cc: regext@ietf.org; alex.mayrhofer.i...@gmail.com Subject: Re: [regext] Side meeting about "Domain Suggestion APIs" - any interest? Notice: This email is from an external sender. Put me on the list Alexander. Tim On Mon, Oct 28, 2019 at 7:18 AM Hollenbeck, Scott <shollenbeck=40verisign....@dmarc.ietf.org<mailto:40verisign....@dmarc.ietf.org>> wrote: I'm interested. This is also something that could be a good topic for next May's Registration Operations Workshop, especially if someone has a candidate API (or APIs) to discuss. Scott > -----Original Message----- > From: regext <regext-boun...@ietf.org<mailto:regext-boun...@ietf.org>> On > Behalf Of Alexander Mayrhofer > Sent: Monday, October 28, 2019 3:45 AM > To: Registration Protocols Extensions > <regext@ietf.org<mailto:regext@ietf.org>> > Subject: [EXTERNAL] [regext] Side meeting about "Domain Suggestion APIs" - > any interest? > > Hello everyone, > > we've recently done some work on a tool that suggests domain names to > registrants if their desired name is already taken. The primary focus is now > using it on our website, but a subsequent step would be providing an API for > registrars so that they can integrate it into their websites as well. I'm > looking > at something REST/JSON based for now. > > Since this is a pretty generic function, i was wondering whether there's any > interest in holding a side meeting at IETF 106 about the standardization side > of that topic? Or shall we do a slot in regext itself? it's not perfectly in- > charter, but it's obviously closely related. > > feedback appreciated! > > best, > Alex > > _______________________________________________ > regext mailing list > regext@ietf.org<mailto:regext@ietf.org> > https://www.ietf.org/mailman/listinfo/regext _______________________________________________ regext mailing list regext@ietf.org<mailto:regext@ietf.org> https://www.ietf.org/mailman/listinfo/regext
_______________________________________________ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext
