To:
<ietf-provreg@cafax.se>, "'Liu, Hong'" <Hong.Liu@neustar.biz>, "Hollenbeck, Scott" <shollenbeck@verisign.com>
Cc:
<Amadeu@nominalia.com>, <andy@ccc.de>, <jcohen@shapirocohen.com>, <junsec@wide.ad.jp>, <karl@CaveBear.com>, <lyman@acm.org>, <lynn@icann.org>, <mouhamet@next.sn>, <vinton.g.cerf@WCOM.COM>, <apisan@servidor.unam.mx>, <yjpark@myepark.com>, "Ron Sherwood" <sherwood@islands.vi>, "Richard J. Sexton" <richard@vrx.net>, "Richard Henderson" <richardhenderson@ntlworld.com>, <ray@fassett.org>, <love@cptech.org>, <k@widgital.com>, "Judith Oppenheimer" <joppenheimer@icbtollfree.com>, "Joop Teernstra" <terastra@terabytz.co.nz>, "Joe Baptista" <baptista@dot-god.com>, "Joanna Lane" <jo-uk@rcn.com>, <jefsey@jefsey.com>, <hfeld@mediaaccess.org>, <hans.klein@pubpolicy.gatech.edu>, <eric@hi-tek.com>, "Ben Edelman" <edelman@law.harvard.edu>, "@quasar Internet Solutions, Inc." <shore@quasar.net>
From:
"Jim Fleming" <JimFleming@ameritech.net>
Date:
Wed, 9 Oct 2002 08:07:15 -0500
Sender:
owner-ietf-provreg@cafax.se
Subject:
Re: Definition of "External" Host
----- Original Message -----
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
To: "'Liu, Hong'" <Hong.Liu@neustar.biz>; <ietf-provreg@cafax.se>
Sent: Wednesday, October 09, 2002 6:29 AM
Subject: RE: Definition of "External" Host
> > The sentence you quoted seems OK if the terms "management
> > authority" and
> > "repository" are precisely defined. It is not a problem if
> > the repository is
> > the whole TLD and the management authority is the TLD
> > registry operator.
> > However, it is getting complicated when delegation of name
> > spaces occurs
> > under the same TLD in 3rd level and up.
> >
> > Maybe an example will help explain my point. Suppose we have
> > a TLD .tld with
> > two 3rd level delegations del1.tld and del2.tld. So there are
> > three disjoint
> > name spaces under .tld: del1.tld, del2.tld and anything else
> > under .tld.
> > These three name spaces have different registration policies.
> > They may also
> > share some common registration policies.
> >
> > If I understand correctly, .tld, .del1.tld, and .del2.tld are
> > considered as
> > three separate "repositories". If not, please ignore the rest of the
> > message.
>
> My contention is that they are all under the same ultimate management
> authority and part of the same repository because they are all part of the
> same TLD branch.
>
> Think of it this way: should I or should I not be publishing glue records
> for hosts registered under these domains? If the answer is "yes", they are
> not external hosts. If the answer is "no", they are external hosts.
>
Glue is the clue, but, it may not be that simple. You have to consider whether it is the
32-bit DNS or the 128-bit DNS. There are not many glue record services for the 32-bit DNS.
Also, if there are Mirrored Registries for the TLD in the 32-bit DNS, to prevent having
a single-point-of-corporate-failure, AND to allow transitions from a censored regime to
an open regime, then you might have a situation where one of the TLD Registries only has
a few SLD names, and the new TLD Registry could have all of those SLD names, plus all
of the new ones being added. Couple that with the 128-bit front-end Registry, with all of the
128-bit DNS AAAA Record Glue Control Services, and it is not so simple.
Glue is the clue...
128-bit DNS AAAA Record Flag Day Formats
2002:[IPv4]:[SDLL.OFFF.FFFF.TTTT]:[64-bit IPv8 or IPv16 Persistent Address]
[YMDD]:[IPv4]:[SDLL.OFFF.FFFF.TTTT]:[64-bit IPv8 or IPv16 Persistent Address]
1-bit to set the Reserved/Spare ("SNOOPY") bit in Fragment Offset [S]
1-bit to set the Don't Fragment (DF) bit [D]
2-bits to select 1 of 4 common TTL values (255, 128, 32, 8) [LL]
1-bit for Options Control [O]
7-bits to set the Identification Field(dst) [FFFFFFF]
4-bits to set the TOS(dst) Field [TTTT]
Default SDLL.OFFF.FFFF.TTTT = 0000.0000.0000.0000
FFF.FFFF.TTTT = GGG.SSSS.SSSS
http://www.ntia.doc.gov/ntiahome/domainname/130dftmail/unir.txt
IPv8
0QQQQGGGSSSSSSSS[32-bits][Port]
IPv16
0QQQQGGGSSSSSSSS[32-bits][Port]
1WWWWWWWSSSSSSSS[32-bits][Port]
Jim Fleming
2002:[IPv4]:000X:03DB:...IPv8 is closer than you think...IPv16 is even closer...
http://www.ietf.com
http://www.iana.org/assignments/ipv4-address-space
http://www.ntia.doc.gov/ntiahome/domainname/130dftmail/unir.txt
http://ipv8.dyndns.tv
http://ipv8.dyns.cx
http://ipv8.no-ip.com
http://ipv8.no-ip.biz
http://ipv8.no-ip.info
http://ipv8.myip.us
http://ipv8.dyn.ee
http://ipv8.community.net.au