Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!decwrl!ucbvax!UUNET.UU.NET!asp
From: asp@UUNET.UU.NET (Andrew Partan)
Newsgroups: comp.protocols.tcp-ip.domains
Subject: Re: no inverse mappings
Message-ID: <9008291458.AA07940@uunet.uu.net>
Date: 29 Aug 90 14:58:09 GMT
References: <9008282330.AA05607@bel.isi.edu>
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: inet
Organization: The Internet
Lines: 14

> See RFC-1174 for new policy on "connected status".

I have seen this - but the NIC is still using their old policies.  Does
any one known when the NIC is going to change their policies to fall in
line with RFC 1174?

I have networks that do not have connected status (connected status no
longer being required) that are being routed on the NSFNET.  I also
have networks that are not being routed on the NSFNET.  In both cases,
the NIC will not register their IN-ADDR.ARPA domains nor change their
name servers to hosts not on networks with connected status.

Thanks,
	--asp@uunet.uu.net (Andrew Partan)