RE: IP Address Management Team in Korea Network Information Center

["JFC (Jefsey) Morfin" <jefsey@jefsey.com>]

Dear Jim,
again I am afraid you are questioning the wrong roots. As pointed out in a 
private mail, the packet swicthed namespace has been created in 1977 by 
Tymnet as part of its value added carrier FCC license. The namespace has 
been propagated under the ITU rules through the Tymnet/US IRC agreements 
under approval of the FCC  to the foreign international operators, through 
them to the foreign domestic operators and through them to private 
networks. If you read the 47 USC 230 (f)(1) you read that the legal US 
definition of the term "internet" corresponds to that (all the 
interoperable packet swicth systems of the world) and not to the ISOC/Vint 
Cerf definition of "interconection of technologies: packet, circuit switch, 
tv, radio, etc..). The only legitimacy the US Communications Code has to 
define the Internet the way it does roots in the Tymnet 1977 license. That 
legitimacy went accross the progressivel replacement of the Tymnet 
technology by OSI architcture and now by IP. This is all interoperable 
packet switch.

In 1984, the namespace registered the ARPA subnamespace under the quoted 
above agreements and licenses. The resulting countrainsts for the ARPA 
subnamespace, also resulting from similar interconnects with "other 
systems" (RFC 921) are descibed in RFC 920 and 921. They correspond to the 
ARPA intranet becoming an extranet and buildinbg up accordingly a naming 
and numbering policy. I note that the public interconnect was not 
publicized for the simple reason it out-boud traffic was charged, so it was 
merely froeign in-bound charged by foreign operators and supported by ... 
me (and from the support I provided there was not much use and often 
trhough alternative paths only permited by a common namespace).

Under that policy and agreements, the foreign extranet users communities 
(ccTLDs) were designated in using ISO 3166 2 letters codes to avoid 
confusion. These communities are pure naming authorities (cf. RFC 920 they 
are registries of which the NIC (IANA) is only a registrar - hence 
establishing the legitimacy of the ccTLDs over ICANN if the ccTLDs managers 
wanted to read, and the reason why the ICANN community declares RFC 920/1 
"outdated", but makes them the basis of their own legitimacy - cf. ICP-3). 
The only Numbering authorities are those dealing with lines and addresses, 
ie the operators. and private (intranets) network (like ARPA). As indicated 
above they were created five years before and used 3 letter codes or more 
for private systems (TRW, ESA [European Space Agency], BULL, CODAN 
[Philips], BOFA, etc), (except in the UK for some historical reasons 
internal to Tymnet where UK prevaled over GBR which is the real name).

In the case of Korea, IN-ADDR.KR is historicaly meaningless, but 
IN-ADDR.KOR belongs to the Korean State. As IN-ADDR.FRA to the French 
people, and IN-ADDR-USA to the US people (plus IN-ADDR.WUI, IN-ADDR.RCA, 
IN-ADDR.FTC, IN-ADDR.ITT, IN-ADDR.FTC).

Again the question to you as "the" specialist of the matter is: "from this 
where do we go? What have we to tell our govs and public to have them 
enacted? How can we use them?".

Now, my root supports the ISO 3166 codes to protect them. And I can 
certainly make resolve any 0.0.IN-ADDR.FRA is there is a need.

jfc















The international public scheme used the ISO 3166




At 06:11 20/08/02, =?ks_c_5601-1987?B?wda/67/P?= wrote:

>I already know your meaning.
>But I don't know why do you ask this question through this mailing list ?
>
>However, in our case, we have not permitted registration of second level
>domains such as in-addr.kr etc.
>And even there is no in-addr.co.kr in our database.
>
>Yong Wan Ju
>
>=============================================================
>IP Address Management Team in Korea Network Information Center
>Manager Yong Wan Ju / Tel : +82-2-2186-4536 Mail : ywju@nic.or.kr
>=============================================================
>
>-----Original Message-----
>From: owner-nir-discuss@lists.apnic.net [mailto:owner-nir-discuss@lists.
>apnic.net]On Behalf Of Jim Fleming
>Sent: Tuesday, August 20, 2002 1:02 PM
>To: hostmaster; nir-discuss@apnic.net
>Cc: Richard J. Sexton; ellen@rony.com; j.oppenheimer@att.net;
>james.love@cptech.org; jefsey@jefsey.com; Joanna Lane; Joe Baptista;
>Joop Teernstra; karl@cavebear.com; Richard Henderson
>Subject: Re: IP Address Management Team in Korea Network Information
>Center
>
>
>----- Original Message -----
>From: "hostmaster" <hostmaster@nic.or.kr>
>Subject: RE: IP Address Management Team in Korea Network Information Center
>
>
> > Is there IN-ADDR.KR ?
> >
>
>http://packetderm.cotse.com/cgi-bin/lookuptools
>Dig any on in-addr.info
>
>-------------------------------------------
>
>
>;; res options: init recurs defnam dnsrch
>;; got answer:
>;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 4
>;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 2, ADDITIONAL: 2
>;; QUERY SECTION:
>;;      in-addr.info, type = ANY, class = IN
>
>;; ANSWER SECTION:
>in-addr.info.           23h55m21s IN NS  ns1.dotsterinc.com.
>in-addr.info.           23h55m21s IN NS  ns2.dotsterinc.com.
>
>;; AUTHORITY SECTION:
>in-addr.info.           23h55m21s IN NS  ns1.dotsterinc.com.
>in-addr.info.           23h55m21s IN NS  ns2.dotsterinc.com.
>
>;; ADDITIONAL SECTION:
>ns1.dotsterinc.com.     1d20h16m34s IN A  64.85.73.18
>ns2.dotsterinc.com.     1d20h16m34s IN A  64.85.73.15
>
>;; Total query time: 1 msec
>;; WHEN: Mon Aug 19 23:56:19 2002
>;; MSG SIZE  sent: 30  rcvd: 140
>
>Dig any on in-addr.museum
>
>-------------------------------------------
>
>
>;; res options: init recurs defnam dnsrch
>;; got answer:
>;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 4
>;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 5, ADDITIONAL: 5
>;; QUERY SECTION:
>;;      in-addr.museum, type = ANY, class = IN
>
>;; ANSWER SECTION:
>in-addr.museum.         23h57m49s IN A  195.7.77.20
>
>;; AUTHORITY SECTION:
>museum.                 1d23h57m49s IN NS  DNS1.GETTY.EDU.
>museum.                 1d23h57m49s IN NS  NIC.ICOM.ORG.
>museum.                 1d23h57m49s IN NS  NS-EXT.VIX.COM.
>museum.                 1d23h57m49s IN NS  NS.ICANN.ORG.
>museum.                 1d23h57m49s IN NS  NIC.museum.
>
>;; ADDITIONAL SECTION:
>DNS1.GETTY.EDU.         1d23h57m49s IN A  153.10.96.5
>NIC.ICOM.ORG.           1d17h20m11s IN A  195.7.65.253
>NS-EXT.VIX.COM.         20m29s IN A     204.152.184.64
>NS.ICANN.ORG.           1d16h7m44s IN A  192.0.34.126
>NIC.museum.             1d23h57m49s IN A  130.242.24.5
>
>;; Total query time: 1 msec
>;; WHEN: Mon Aug 19 23:56:52 2002
>;; MSG SIZE  sent: 32  rcvd: 251
>Dig any on in-addr.biz
>
>-------------------------------------------
>
>
>;; res options: init recurs defnam dnsrch
>;; got answer:
>;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 4
>;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 2, ADDITIONAL: 2
>;; QUERY SECTION:
>;;      in-addr.biz, type = ANY, class = IN
>
>;; ANSWER SECTION:
>in-addr.biz.            1h55m34s IN NS  DNS.FASTDNSSERVERS.COM.
>in-addr.biz.            1h55m34s IN NS  DNS2.FASTDNSSERVERS.COM.
>
>;; AUTHORITY SECTION:
>in-addr.biz.            1h55m34s IN NS  DNS.FASTDNSSERVERS.COM.
>in-addr.biz.            1h55m34s IN NS  DNS2.FASTDNSSERVERS.COM.
>
>;; ADDITIONAL SECTION:
>DNS.FASTDNSSERVERS.COM.  3h21m36s IN A  209.81.157.1
>DNS2.FASTDNSSERVERS.COM.  3h21m36s IN A  209.81.157.2
>
>;; Total query time: 1 msec
>;; WHEN: Mon Aug 19 23:57:45 2002
>;; MSG SIZE  sent: 29  rcvd: 144
>Dig any on in-addr.tv
>
>-------------------------------------------
>
>
>;; res options: init recurs defnam dnsrch
>;; got answer:
>;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 4
>;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 5, ADDITIONAL: 6
>;; QUERY SECTION:
>;;      in-addr.tv, type = ANY, class = IN
>
>;; ANSWER SECTION:
>in-addr.tv.             2m26s IN MX     10 nomail.www.tv.
>
>;; AUTHORITY SECTION:
>tv.                     10h20m5s IN NS  NS1.NIC.tv.
>tv.                     10h20m5s IN NS  NS2.NIC.tv.
>tv.                     10h20m5s IN NS  NS4.NIC.tv.
>tv.                     10h20m5s IN NS  NS6.NIC.tv.
>tv.                     10h20m5s IN NS  NS7.NIC.tv.
>
>;; ADDITIONAL SECTION:
>nomail.www.tv.          55S IN A        127.0.0.1
>NS1.NIC.tv.             10h20m5s IN A   216.136.192.136
>NS2.NIC.tv.             10h20m5s IN A   208.184.1.167
>NS4.NIC.tv.             10h20m5s IN A   208.185.237.100
>NS6.NIC.tv.             10h20m5s IN A   64.56.165.153
>NS7.NIC.tv.             10h20m5s IN A   64.69.172.153
>
>;; Total query time: 1 msec
>;; WHEN: Mon Aug 19 23:58:45 2002
>;; MSG SIZE  sent: 28  rcvd: 245
>
>
>2002 0:201 .COMhttp://www.thepricedomain.com/index.php?domainlist=com2002 
>1:158 .CLUB 2002 2:143 .FAMILYhttp://www.New.Net2002 3:219
>.INFOhttp://www.Name-Space.comhttp://www.thepricedomain.com/index.php?domainlist=info2002 
>4:58 .LLC2002 5:194
>.INChttp://www.New.Net2002 6:171 .TVhttp://www.TV2002 7:195 .CHURCH
>Jim Fleming2002:[IPv4]:000X:03DB:...IPv8 is closer than you
>think...http://www.ican.org/what's_new!!!.htmhttp://www.iana.org/assignments/ipv4-address-spacehttp://www.ntia.doc.gov/ntiahome/doma
>inname/130dftmail/unir.txt
>
>
>
>
>
>---
>Incoming mail is certified Virus Free.
>Checked by AVG anti-virus system (http://www.grisoft.com).
>Version: 6.0.381 / Virus Database: 214 - Release Date: 02/08/02