.fo off

.bf x0pr12

Received: (from CUNYVM.BITNET for <SHARON@NIC.DDN.MIL> via BSMTP)

Received: (from MAILER@CUNYVMV2 for MAILER@YUBGSS21 via NJE)

 (UCLA/Mail V1.410 M-MAILER-6191-50); Sun, 21 Jul 91 21:22:11 GMT

Received: from CUNYVM by CUNYVM.BITNET (Mailer R2.07) with BSMTP id 3268; Sun,

 21 Jul 91 15:18:20 EDT

Received: from NIC.DDN.MIL by CUNYVM.CUNY.EDU (IBM VM SMTP R1.2.2MX) with TCP;

 Sun, 21 Jul 91 15:18:19 EDT

Date: Sun, 21 Jul 91 12:18:17 PDT

From: HOSTMASTER@NIC.DDN.MIL

Subject: Re: Internet number application

Sender: SHARON@NIC.DDN.MIL

To: SYSTEM3%YUBGSS21.BITNET@CUNYVM.CUNY.EDU

cc: sharon@NIC.DDN.MIL, hostmaster@NIC.DDN.MIL

Reply-To: HOSTMASTER@NIC.DDN.MIL

In-Reply-To: Message from "Mirjana Tasic +38-11-419-895

 <SYSTEM3%YUBGSS21.BITNET@CUNYVM.CUNY.EDU>" of Tue, 16 Jul 91 04:19:42 PDT

Message-ID: <12703184811.23.SHARON@NIC.DDN.MIL>

 

Hi,

 

The new class and network number for UNINET-BG is:

 

Class B, #147.91.0.0

 

NIC Handle: OZ4

 

The NIC handle is an internal record searching tool.  If a new Technical

Point of Contact was registered with this application a new NIC handle

has been assigned.  If the Technical POC was already registered at the

NIC but their handle was not provided in the application, it has been

listed here for your reference and for use in all future correspondence

with the NIC.

 

It is suggested that host number zero in any network be reserved (not

used), and the host address of all ones (255 in class C networks) in any

network be used to indicate a broadcast datagram.

 

The association between addresses used in the particular network

hardware and the Internet addresses may be established and maintained by

any method you select.  Use of the address resolution procedure

described in RFC 826 is encouraged.

 

Thanks again for your cooperation!

Sharon McGregor

AN

-------

