<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet type="text/xsl" href="milnet-parameters.xsl"?>
<?xml-model href="milnet-parameters.rng" schematypens="http://relaxng.org/ns/structure/1.0" ?>
<registry xmlns="http://www.iana.org/assignments" id="milnet-parameters">
  <title>Milnet Parameters - Registry closed</title>
  <updated>2001-08-23</updated>
  <registry id="milnet-parameters-1">
    <title>Milnet Link Numbers</title>
    <registration_rule>Registry closed</registration_rule>
    <note>The word "link" here refers to a field in the original MILNET Host/IMP
interface leader.  The link was originally defined as an 8-bit field.
Later specifications defined this field as the "message-id" with a
length of 12 bits.  The name link now refers to the high order 8 bits of
this 12-bit message-id field.  The Host/IMP interface is defined in BBN
Report 1822 <xref type="text">BBN, "Specifications for the Interconnection of a Host and
an IMP", Report 1822, Bolt Beranek and Newman, Cambridge,
Massachusetts, revised, December 1981.</xref>.

The low-order 4 bits of the message-id field are called the sub-link.
Unless explicitly specified otherwise for a particular protocol, there
is no sender to receiver significance to the sub-link.  The sender may
use the sub-link in any way he chooses (it is returned in the RFNM by
the destination IMP), the receiver should ignore the sub-link.</note>
    <record>
      <value>0-63</value>
      <description>BBNCC Monitoring</description>
      <xref type="person" data="Michael_Brescia"/>
    </record>
    <record>
      <value>64-149</value>
      <description>Unassigned</description>
      <xref type="person" data="Jon_Postel"/>
    </record>
    <record>
      <value>150</value>
      <description>Xerox NS IDP</description>
      <xref type="text">"The Ethernet, A Local Area Network: Data Link Layer and
Physical Layer Specification", AA-K759B-TK, Digital
Equipment Corporation, Maynard, MA.  Also as: "The Ethernet
- A Local Area Network", Version 1.0, Digital Equipment
Corporation, Intel Corporation, Xerox Corporation,
September 1980.  And: "The Ethernet, A Local Area Network:
Data Link Layer and Physical Layer Specifications",
Digital, Intel and Xerox, November 1982.  And: XEROX, "The
Ethernet, A Local Area Network: Data Link Layer and
Physical Layer Specification", X3T51/80-50, Xerox
Corporation, Stamford, CT., October 1980.</xref>
      <xref type="person" data="Fonda_Pallone"/>
    </record>
    <record>
      <value>151</value>
      <description>Unassigned</description>
      <xref type="person" data="Jon_Postel"/>
    </record>
    <record>
      <value>152</value>
      <description>PARC Universal Protocol</description>
      <xref type="text">Boggs, D., J. Shoch, E. Taft, and R. Metcalfe, "PUP: An
Internetwork Architecture", XEROX Palo Alto Research Center,
CSL-79-10, July 1979; also in IEEE Transactions on
Communication, Volume COM-28, Number 4, April 1980.</xref>
      <xref type="person" data="Fonda_Pallone"/>
    </record>
    <record>
      <value>153</value>
      <description>TIP Status Reporting</description>
      <xref type="person" data="Jim_Herman"/>
    </record>
    <record>
      <value>154</value>
      <description>TIP Accounting</description>
      <xref type="person" data="Jim_Herman"/>
    </record>
    <record>
      <value>155</value>
      <description>Internet Protocol [regular]</description>
      <xref type="rfc" data="rfc791"/>
      <xref type="person" data="Jon_Postel"/>
    </record>
    <record>
      <value>156-158</value>
      <description>Internet Protocol [experimental]</description>
      <xref type="rfc" data="rfc791"/>
      <xref type="person" data="Jon_Postel"/>
    </record>
    <record>
      <value>159</value>
      <description>Figleaf Link</description>
      <xref type="person" data="Joseph_Walters_Jr"/>
    </record>
    <record>
      <value>160</value>
      <description>Blacker Local Network Protocol</description>
      <xref type="person" data="Dennis_Morris"/>
    </record>
    <record>
      <value>161-194</value>
      <description>Unassigned</description>
      <xref type="person" data="Jon_Postel"/>
    </record>
    <record>
      <value>195</value>
      <description>ISO-IP</description>
      <xref type="rfc" data="rfc926"/>
      <xref type="person" data="Robert_Myhill"/>
    </record>
    <record>
      <value>196-247</value>
      <description>Experimental Protocols</description>
      <xref type="person" data="Jon_Postel"/>
    </record>
    <record>
      <value>248-255</value>
      <description>Network Maintenance</description>
      <xref type="person" data="Jim_Herman"/>
    </record>
  </registry>
  <registry id="milnet-parameters-2">
    <title>Milnet Logical Addresses</title>
    <registration_rule>Registry closed</registration_rule>
    <note>The MILNET facility for "logical addressing" is described in <xref type="rfc" data="rfc878"/>
and <xref type="rfc" data="rfc1005"/>.  A portion of the possible logical addresses are
reserved for standard uses.

There are 49,152 possible logical host addresses.  Of these, 256 are
reserved for assignment to well-known functions.  Assignments for
well-known functions are made by the IANA.  Assignments for other
logical host addresses are made by the NIC.</note>
    <record>
      <value>0</value>
      <description>Reserved</description>
      <xref type="person" data="Jon_Postel"/>
    </record>
    <record>
      <value>1</value>
      <description>The BBN Core Gateways</description>
      <xref type="person" data="Michael_Brescia"/>
    </record>
    <record>
      <value>2-254</value>
      <description>Unassigned</description>
      <xref type="person" data="Jon_Postel"/>
    </record>
    <record>
      <value>255</value>
      <description>Reserved</description>
      <xref type="person" data="Jon_Postel"/>
    </record>
  </registry>
  <registry id="milnet-parameters-3">
    <title>Milnet X.25 Address Mappings</title>
    <registration_rule>Registry closed</registration_rule>
    <note>All MILNET hosts are assigned addresses by the Defense Data Network
(DDN).  The address of a MILNET host may be obtained from the Network
Information Center (NIC), represented as an ASCII text string in what
is called "host table format".  This section describes the process by
which MILNET X.25 addresses may be derived from addresses in the NIC
host table format.

A NIC host table address consists of the ASCII text string
representations of four decimal numbers separated by periods,
corresponding to the four octeted of a thirty-two bit Internet
address.  The four decimal numbers are referred to in this section as
"n", "h' "l", and "i".  Thus, a host table address may be represented
as: "n.h.l.i".  Each of these four numbers will have either one, two,
or three decimal digits and will never have a value greater than 255.
For example, in the host table, address: "10.2.0.124", n=10, h=2, l=0,
and i=124.  To convert a host table address to a MILNET X.25 address:

1.  If h &lt; 64, the host table address corresponds to the X.25
physical address:


ZZZZ F IIIHHZZ (SS)

where:

     ZZZZ = 0000    as required

     F = 0          because the address is a physical address;

     III            is a three decimal digit respresentation of
                    "i", right-adjusted and padded with leading
                    zeros if required;

     HH             is a two decimal digit representation of "h",
                    right-adjusted and padded with leading zeros
                    if required;

     ZZ = 00        and

     (SS)           is optional


In the example given above, the host table address 10.2.0.124
corresponds to the X.25 physical address 000001240200.

2.  If h &gt; 64 or h = 64, the host table address corresponds to the
X.25 logical address


ZZZZ F RRRRRZZ (SS)

where:

     ZZZZ = 0000    as required

     F = 1          because the address is a logical address;

     RRRRR          is a five decimal digit representation of
                    the result "r" of the calculation

                             r = h * 256 + i

                    (Note that the decimal representation of
                    "r" will always require five digits);

     ZZ = 00        and

     (SS)           is optional

Thus, the host table address 10.83.0.207 corresponds to the X.25
logical address 000012145500.

In both cases, the "n" and "l" fields of the host table address are
not used.</note>
  </registry>
  <people>
    <person id="Dennis_Morris">
      <name>Dennis Morris</name>
      <uri>mailto:Morrisd&amp;imo-uvax.dca.mil</uri>
    </person>
    <person id="Fonda_Pallone">
      <name>Fonda Pallone</name>
    </person>
    <person id="Jim_Herman">
      <name>Jim Herman</name>
      <uri>mailto:Herman&amp;ccj.bbn.com</uri>
    </person>
    <person id="Jon_Postel">
      <name>Jon Postel</name>
      <uri>mailto:postel&amp;isi.edu</uri>
    </person>
    <person id="Joseph_Walters_Jr">
      <name>Joseph Walters, Jr.</name>
      <uri>mailto:JWalters&amp;BBN.COM</uri>
    </person>
    <person id="Michael_Brescia">
      <name>Michael Brescia</name>
      <uri>mailto:Brescia&amp;ccv.bbn.com</uri>
    </person>
    <person id="Robert_Myhill">
      <name>Robert Myhill</name>
      <uri>mailto:Myhill&amp;ccs.bbn.com</uri>
    </person>
  </people>
</registry>
