[Collisions] "controlled interruption" - 127/8 versus RFC1918 space

James Galvin galvin at elistx.com
Fri Jan 10 21:04:41 UTC 2014

On Fri, Jan 10, 2014 at 12:50 PM, Joe Abley <jabley at hopcount.ca> wrote:

> On 2014-01-10, at 11:30, David Conrad <drc at virtualized.org> wrote:

> >> e.g. for registry operators who have already passed pre-delegation
> testing and are perhaps already running some new gTLD registries in
> production.
> >
> > I'm not positive (or authoritative in any way) but I don't believe folks
> who are already running in production will be forced to do anything they
> don't want to.  As I said, I believe for them, the idea is to allow them to
> move more quickly to normal operation.
> So what happens to a registry that is currently publishing new gTLD zones
> for delegated strings, but is also expected to accommodate approved but
> as-yet-undelegated strings?
> >>> Could you be explicit in the headaches you see?
> >> It seems like a lot of work for lawyers and developers,
> >
> > Not being a lawyer, I'll not comment on that bit. What development do
> you see being necessary?
> It's the changes to the registry state machine that worry me.
> We seem to be talking about changing the registry state machine such that
> there's an extra stage involved whereby DNS records other than those
> required for a simple delegation will be published for some period of time
> before they are replaced by the expected delegation. I suspect that in at
> least some cases this is going to require code changes, helpdesk/NOC
> changes, monitoring and measurement changes, documentation changes,
> re-education for sales staff, etc. None of this is impossible, but it seems
> to me it has a distinctly non-zero cost.


What changes to the "registry state machine" do you imagine?  The way I'm
seeing this I don't see any changes to the registry state machine.

If this is implemented as a "trial delegation", as I understand the
proposal by Jeff, then I imagine something like the following.  After an
nTLD has passed PDT but before the nTLD goes to production, that is the
opportunity to deploy this "trial delegation".  It requires only setting up
specific zones for the TLD in the DNS.

We need procedures/rules for when this starts, when it ends, evaluating
what happens, what actions to take under circumstances we can predict (as
well as those we can't predict), etc.  I presume that JAS will expand on
all this, including considering whatever advice comes from this discussion.

However, none of this involves the registry.

Did you have something else in mind?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.dns-oarc.net/pipermail/collisions/attachments/20140110/00e29942/attachment.htm>

More information about the Collisions mailing list