deletion of a
domain by creating subordinate hosts, and I was not okay by allowing one
registrar to change the delegation for another domain (through a rename outside
the existing domain boundary).
Best,
James Mitchell
On Jul 11, 2023, at 12:07 PM, Hollenbeck, Scott
wrote:
Folks, we could
Date: Tuesday, July 25, 2023 at 3:05 PM
To: James Mitchell
Cc: "Hollenbeck, Scott" ,
"regext@ietf.org"
Subject: Re: [regext] [Ext] [DNSOP] Best Practices for Managing Existing
Delegations When Deleting a Domain or Host
> Host rename always seemed a dang
-3271
12061 Bluemont Way
Reston, VA 20190
Verisign.com
[verisigninc.com]<https://urldefense.com/v3/__http://verisigninc.com/__;!!PtGJab4!4EOVPv3pQzi9j_6Q5q8H2h7_lqdAfhHjwPNrJpkx65NazWCl5z6OPf0HSnw6BpgwfvozE4uro8hg1NPx_JjmuRSxMtk$>
From: regext on behalf of James Mitchell
Date: Tuesday, J
name space is specified as "" [RFC
9224].
Kind regards,
James Mitchell
IANA
___
regext mailing list
regext@ietf.org
https://www.ietf.org/mailman/listinfo/regext
Hi Marc,
I’ll share a version of the bootstrap file in a few weeks, once the host is
globally reachable.
Thanks,
James
From: Marc Blanchet
Date: Tuesday, February 20, 2024 at 6:40 AM
To: James Mitchell
Cc: "regext@ietf.org"
Subject: [Ext] Re: [regext] Adding the DNS root to the
Hi all,
What is the purpose of the context URI in the links structure? From 9083:
The "value" JSON value is the context URI as described by [RFC8288]. The
"value", "rel", and "href" JSON values MUST be specified.
My understanding is that the context URI is the request URI that generated the
JSO
ed in your thoughts to whether the matching logic needs updating,
and whether guidance or changes to the bootstrap file can reduce lookups for
“non-existent entries” to the root, e.g. publishing an empty RDAP URL for
delegated TLDs.
James
From: regext on behalf of James Mitchell
Date: Tuesday, F
that with our server. Otherwise I’ll
likely hold onto on the RFC 7483 requirements for links.
James
From: regext on behalf of "Andrew Newton (andy)"
Date: Wednesday, February 28, 2024 at 4:03 AM
To: James Mitchell
Cc: "regext@ietf.org"
Subject: [Ext] Re: [regext] RDAP
stently
returned in LDH name format to allow clients to process these IDNs according to
their capabilities.
Thanks,
James
From: regext on behalf of Jasdip Singh
Date: Monday, March 4, 2024 at 8:41 AM
To: "Hollenbeck, Scott" , James Mitchell
, "a...@hxr.us"
Cc: "re
From: "Andrew Newton (andy)"
Date: Monday, March 4, 2024 at 12:23 PM
To: James Mitchell
Cc: "regext@ietf.org"
Subject: Re: [Ext] Re: [regext] RDAP and link context
On Fri, Mar 1, 2024 at 6:57 PM James Mitchell
mailto:james.mitch...@iana.org>> wrote:
The new gTL
My understanding is the EPP ROID is an identifier that is composed of a suffix
that identifies the registry/repository to which an object belongs. That
repository identifier should be registered in the IANA registry of EPP
Repository Identifiers at https://www.iana.org/assignments/epp-repository
11 matches
Mail list logo
