[comp.protocols.tcp-ip] Name of NIC

brescia@CCV.BBN.COM (Mike Brescia) (07/18/87)

     NIC.SRI.COM is not and was never the official name of any host.

SRI-NIC.ARPA is equally hard to remember.  I suggest that NIC be a name at the
top level of the domain tree, and be the obvious place.  The reason is that
the Net.Info.Ctr is a top level resource, not actually some branch of SRI.COM.
Suppose SRI changes its corporate name?  Suppose ARPA removes its support of
the internet, and the ARPA domain goes away?  The (THE) NIC service should
still be available by name.

Mike.

PERRY@VAX.DARPA.MIL (Dennis G. Perry) (07/18/87)

Mike, I agree with you.  The NIC should be availabe by name, regardless
of where it is located.

dennis
-------

M.JSOL@DEEP-THOUGHT.MIT.EDU (Jon Solomon) (07/18/87)

It's a neat idea, but the main problem with that is that there is already
another NIC (I'm speaking of nic.nyser.net).

--jsol

p.s. also there is a BITNIC in the BITNET namespace.

LYNCH@A.ISI.EDU (Dan Lynch) (07/19/87)

Jon,  I think that Mike and Dennis were thinking of the name
of the entity to be NIC (or .NIC to be syntatically incorrect).
Dan
-------

ROODE@BIONET-20.ARPA (David Roode) (07/20/87)

WaWhat about creating a domain under the top level NET domain,
NIC.NET  in there could be the name DDN.NIC.NET for
the DDN NIC......  NYSER.NIC.NET for their NIC....
This also works for the NOC.... ARPANET.NOC.NET  MILNET.NOC.NET
etc.  The NIC/NOC for the NSFNET is called NNSC for some reason,
so NSFNET.NNSC.NET is also possible.
-------

schoff@NIC.NYSER.NET (Martin Lee Schoffstall) (07/20/87)

Actually there is a "nic.isi.edu" also.

Reading between the lines is sri-nic.arpa suppose to become:

	nic.ddn.net

Or some such thing?

Marty

schoff@NIC.NYSER.NET (Martin Lee Schoffstall) (07/20/87)

Actually the NOC for the NSFNet is called devvax.tn.cornell.edu.

marty

STJOHNS@SRI-NIC.ARPA (07/20/87)

Guys,  to  forestall  further  discussions  on  this.   The  name
"SRI-NIC.ARPA" is the official name for the NIC now and  this  is
due  mostly  to  historical concerns.  At some time in the future
(i.e.  when I can spare the time to argue the case at  the  PMO),
the  NIC will change to something like NIC.DDN.MIL.  (No, I don't
want naming suggestions just yet thanks!)

Mhing

leiner@riacs.EDU (07/20/87)

Mike,

That was the reason for having ORG or NET as a top level domain.

Barry
----------

PERRY@VAX.DARPA.MIL (Dennis G. Perry) (07/21/87)

Mike, who you gonna argue with?  It seems to me that you should just
write the memo to the Col and say here we what we are going to do and
when and why.  No one else cares about what the NIC is called.

I will help you with the Col if you want it.

dennis
-------

ron@TOPAZ.RUTGERS.EDU (Ron Natalie) (07/22/87)

Watch out or they'll make the name of the hosts NET.INFO.CTR as you suggested.

M.JSOL@DEEP-THOUGHT.MIT.EDU (Jon Solomon) (07/24/87)

Oh, so there would be MILNET.NIC and ARPANET.NIC and NYSERNET.NIC 
and BITNET.NIC? Good idea!

--jsol

steve@BRL.ARPA (Stephen Wolff) (07/26/87)

Indeed.  One would hope that the name of the address of "the NIC" would
contain no clue concerning which of the multiple, partially-redundant,
National Research Internet databases (the InterNic) would answer any query.