tech-invite   World Map     

IETF     RFCs     Groups     SIP     ABNFs    |    3GPP     Specs     Gloss.     Arch.     IMS     UICC    |    Misc.    |    search     info

RFC 1700


Assigned Numbers

Part 3 of 7, p. 70 to 99
Prev RFC Part       Next RFC Part


prevText      Top       Page 70 
            0  No Code

 10     Router Selection                        [RFC1256]

            0  No Code

 11     Time Exceeded                            [RFC792]

            0  Time to Live exceeded in Transit
            1  Fragment Reassembly Time Exceeded

 12     Parameter Problem                        [RFC792]

            0  Pointer indicates the error
            1  Missing a Required Option        [RFC1108]
            2  Bad Length

 13     Timestamp                                [RFC792]

            0  No Code

 14     Timestamp Reply                          [RFC792]

            0  No Code

 15     Information Request                      [RFC792]

            0  No Code

 16     Information Reply                        [RFC792]

            0  No Code

 17     Address Mask Request                     [RFC950]

            0  No Code

 18     Address Mask Reply                       [RFC950]

Top       Page 71 
            0  No Code

 19     Reserved (for Security)                    [Solo]

 20-29  Reserved (for Robustness Experiment)        [ZSu]

 30     Traceroute                              [RFC1393]

 31     Datagram Conversion Error               [RFC1475]

 32     Mobile Host Redirect              [David Johnson]

 33     IPv6 Where-Are-You                 [Bill Simpson]

 34     IPv6 I-Am-Here                     [Bill Simpson]

 35     Mobile Registration Request        [Bill Simpson]

 36     Mobile Registration Reply          [Bill Simpson]


[RFC792] Postel, J., "Internet Control Message Protocol", STD 5,
         RFC 792, USC/Information Sciences Institute, September 1981.

[RFC950] Mogul, J., and J. Postel, "Internet Standard Subnetting
         Procedure", STD 5, RFC 950, Stanford, USC/Information
         Sciences Institute, August 1985.

[RFC1108] Kent, S., "U.S. Department of Defense Security Options for
          the Internet Protocol", RFC 1108, November 1991.

[RFC1256] Deering, S., Editor, "ICMP Router Discovery Messages", RFC
          1256, Xerox PARC, September 1991.

[RFC1393] Malkin, G., "Traceroute Using an IP Option", RFC 1393,
          Xylogics, Inc., January 1993.

[RFC1475] Ullmann, R., "TP/IX: The Next Internet", RFC 1475, Process
          Software Corporation, June 1993.


[JBP] Jon Postel <>

[David Johnson]

Top       Page 72 
[Bill Simpson]  <> September, 1994.





Top       Page 73 

The Transmission Control Protocol (TCP) has provision for optional
header fields identified by an option kind field.  Options 0 and 1 are
exactly one octet which is their kind field.  All other options have
their one octet kind field, followed by a one octet length field,
followed by length-2 octets of option data.

Kind   Length   Meaning                           Reference
----   ------   -------------------------------   ---------
  0        -    End of Option List                 [RFC793]
  1        -    No-Operation                       [RFC793]
  2        4    Maximum Segment Lifetime           [RFC793]
  3        3    WSOPT - Window Scale              [RFC1323]
  4        2    SACK Permitted                    [RFC1072]
  5        N    SACK                              [RFC1072]
  6        6    Echo (obsoleted by option 8)      [RFC1072]
  7        6    Echo Reply (obsoleted by option 8)[RFC1072]
  8       10    TSOPT - Time Stamp Option         [RFC1323]
  9        2    Partial Order Connection Permitted[RFC1693]
 10        5    Partial Order Service Profile     [RFC1693]
 11             CC                                 [Braden]
 12             CC.NEW                             [Braden]
 13             CC.ECHO                            [Braden]
 14         3   TCP Alternate Checksum Request    [RFC1146]
 15         N   TCP Alternate Checksum Data       [RFC1146]
 16             Skeeter                           [Knowles]
 17             Bubba                             [Knowles]
 18         3   Trailer Checksum Option    [Subbu & Monroe]


Number  Description                     Reference
------- ------------------------------- ----------
   0    TCP Checksum                    [RFC-1146]
   1    8-bit Fletchers's algorithm     [RFC-1146]
   2    16-bit Fletchers's algorithm    [RFC-1146]
   3    Redundant Checksum Avoidance    [Kay]


[KAY] Kay, J. and Pasquale, J., "Measurement, Analysis, and
      Improvement of UDP/IP Throughput for the DECstation 5000,"
      Proceedings of the Winter 1993 Usenix Conference, January 1993
      (available for anonymous FTP in

Top       Page 74 <>

[RFC793] Postel, J., "Transmission Control Protocol - DARPA Internet
         Program Protocol Specification", STD 7, RFC 793, DARPA,
         September 1981.

[RFC1323] Jacobson, V., Braden, R., and D. Borman, "TCP Extensions for
          High Performance", RFC 1323, LBL, ISI, Cray Research, May

[RFC1072] Jacobson, V., and R. Braden, "TCP Extensions for Long-Delay
          Paths", RFC 1072, LBL, ISI, October 1988.

[RFC1693]  ?????

[RFC1146] Zweig, J., and C. Partridge, "TCP Alternate Checksum
          Options", RFC 1146, UIUC, BBN, March 1990.


[Braden]  Bob Braden <>

[Knowles] Stev Knowles <>

[Kay] J. Kay <>

[Subbu & Monroe] <mystery contact>



Top       Page 75 

The Telnet Protocol has a number of options that may be negotiated.
These options are listed here.  "Internet Official Protocol Standards"
(STD 1) provides more detailed information.

Options  Name                                              References
-------  -----------------------                           ----------
   0     Binary Transmission                             [RFC856,JBP]
   1     Echo                                            [RFC857,JBP]
   2     Reconnection                                  [NIC50005,JBP]
   3     Suppress Go Ahead                               [RFC858,JBP]
   4     Approx Message Size Negotiation               [ETHERNET,JBP]
   5     Status                                          [RFC859,JBP]
   6     Timing Mark                                     [RFC860,JBP]
   7     Remote Controlled Trans and Echo                [RFC726,JBP]
   8     Output Line Width                             [NIC50005,JBP]
   9     Output Page Size                              [NIC50005,JBP]
  10     Output Carriage-Return Disposition              [RFC652,JBP]
  11     Output Horizontal Tab Stops                     [RFC653,JBP]
  12     Output Horizontal Tab Disposition               [RFC654,JBP]
  13     Output Formfeed Disposition                     [RFC655,JBP]
  14     Output Vertical Tabstops                        [RFC656,JBP]
  15     Output Vertical Tab Disposition                 [RFC657,JBP]
  16     Output Linefeed Disposition                     [RFC657,JBP]
  17     Extended ASCII                                  [RFC698,JBP]
  18     Logout                                          [RFC727,MRC]
  19     Byte Macro                                      [RFC735,JBP]
  20     Data Entry Terminal                     [RFC1043,RFC732,JBP]
  22     SUPDUP                                   [RFC736,RFC734,MRC]
  22     SUPDUP Output                                   [RFC749,MRC]
  23     Send Location                                  [RFC779,EAK1]
  24     Terminal Type                                 [RFC1091,MS56]
  25     End of Record                                   [RFC885,JBP]
  26     TACACS User Identification                      [RFC927,BA4]
  27     Output Marking                                  [RFC933,SXS]
  28     Terminal Location Number                        [RFC946,RN6]
  29     Telnet 3270 Regime                             [RFC1041,JXR]
  30     X.3 PAD                                       [RFC1053,SL70]
  31     Negotiate About Window Size                  [RFC1073,DW183]
  32     Terminal Speed                                [RFC1079,CLH3]
  33     Remote Flow Control                           [RFC1372,CLH3]
  34     Linemode                                      [RFC1184,DB14]
  35     X Display Location                            [RFC1096,GM23]
  36     Environment Option                            [RFC1408,DB14]
  37     Authentication Option                         [RFC1409,DB14]
  38     Encryption Option                                     [DB14]
  39     New Environment Option                        [RFC1572,DB14]

Top       Page 76 
  40     TN3270E                                            [RFC1647]
 255     Extended-Options-List                           [RFC861,JBP]

Telnet Authentication Types

In [RFC1409], a list of authentication types is introduced.  Additions
to the list are registerd by the IANA and documented here.

Type       Description                  Reference
  0        NULL                         [RFC1409]
  1        KERBEROS_V4                  [RFC1409]
  2        KERBEROS_V5                  [RFC1409]
  3        SPX                          [RFC1409]
  4-5      Unassigned
  6        RSA                          [RFC1409]
  7-9      Unassigned
 10        LOKI                         [RFC1409]
 11        SSA                          [Schoch]


[ETHERNET] "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.

[NIC50005] DDN Protocol Handbook, "Telnet Reconnection Option",
           "Telnet Output Line Width Option", "Telnet Output Page Size
           Option", NIC 50005, December 1985.

[RFC652] Crocker, D., "Telnet Output Carriage-Return Disposition
         Option", RFC 652, UCLA-NMC, October 1974.

[RFC653] Crocker, D., "Telnet Output Horizontal Tabstops Option",
         RFC 653, UCLA-NMC, October 1974.

[RFC654] Crocker, D., "Telnet Output Horizontal Tab Disposition
         Option", RFC 654, UCLA-NMC, October 1974.

[RFC655] Crocker, D., "Telnet Output Formfeed Disposition Option",
         RFC 655, UCLA-NMC, October 1974.

Top       Page 77 
[RFC656] Crocker, D., "Telnet Output Vertical Tabstops Option",
         RFC 656, UCLA-NMC, October 1974.

[RFC657] Crocker, D., "Telnet Output Vertical Tab Disposition Option",
         RFC 657, UCLA-NMC, October 1974.

[RFC658] Crocker, D., "Telnet Output Linefeed Disposition", RFC 658,
         UCLA-NMC, October 1974.

[RFC698] Tovar, "Telnet Extended ASCII Option", RFC 698, Stanford
         University-AI, July 1975.

[RFC726] Postel, J. and D. Crocker, "Remote Controlled Transmission
         and Echoing Telnet Option", RFC 726, SRI-ARC, UC Irvine,
         March 1977.

[RFC727] Crispin, M., "Telnet Logout Option", RFC 727, Stanford
         University-AI, April 1977.

[RFC734] Crispin, M., "SUPDUP Protocol", RFC 734, Stanford,
         October 1977.

[RFC735] Crocker, D. and R. Gumpertz, "Revised Telnet Byte Marco
         Option", RFC 735, Rand, CMU, November 1977.

[RFC736] Crispin, M., "Telnet SUPDUP Option", Stanford University-AI,
         RFC 736, Stanford, October 1977.

[RFC749] Greenberg, B., "Telnet SUPDUP-OUTPUT Option", RFC 749,
         MIT-Multics, September 1978.

[RFC779] Killian, E., "Telnet Send-Location Option", RFC 779,
         LLL, April 1981.

[RFC856] Postel, J. and J. Reynolds, "Telnet Binary Transmission",
         STD 27, RFC 856, USC/Information Sciences Institute, May

[RFC857] Postel, J. and J. Reynolds, "Telnet Echo Option", STD 28, RFC
         857, USC/Information Sciences Institute, May 1983.

[RFC858] Postel, J. and J. Reynolds, "Telnet Suppress Go Ahead
         Option", STD 29, RFC 858, USC/Information Sciences Institute,
         May 1983.

[RFC859] Postel, J. and J. Reynolds, "Telnet Status Option", STD 30,
         RFC 859, USC/Information Sciences Institute, May 1983.

Top       Page 78 
[RFC860] Postel, J. and J. Reynolds, "Telnet Timing Mark Option",
         STD 31, RFC 860, USC/Information Sciences Institute, May

[RFC861] Postel, J. and J. Reynolds, "Telnet Extended Options - List
         Option", STD 32, RFC 861, USC/Information Sciences Institute,
         May 1983.

[RFC885] Postel, J., "Telnet End of Record Option", RFC 885,
         USC/Information Sciences Institute, December 1983.

[RFC927] Anderson, B., "TACACS User Identification Telnet Option",
         RFC 927, BBN, December 1984.

[RFC933] Silverman, S., "Output Marking Telnet Option", RFC 933,
         MITRE, January 1985.

[RFC946] Nedved, R., "Telnet Terminal Location Number Option",
         RFC 946, Carnegie-Mellon University, May 1985.

[RDC1041] Rekhter, J., "Telnet 3270 Regime Option", RFC 1041,
          IBM, January 1988.

[RFC1043] Yasuda, A., and T. Thompson, "TELNET Data Entry Terminal
          Option DODIIS Implementation", RFC 1043, DIA, February 1988.

[RFC1053] Levy, S., and T. Jacobson, "Telnet X.3 PAD Option",
          RFC 1053, Minnesota Supercomputer Center, April 1988.

[RFC1073] Waitzman, D., "Telnet Window Size Option", RFC 1073,
          BBN STC, October, 1988.

[RFC1079] Hedrick, C., "Telnet Terminal Speed Option", RFC 1079,
          Rutgers University, December 1988.

[RFC1091] VanBokkelen, J., "Telnet Terminal Type Option",
          RFC 1091, FTP Software, Inc., February 1989.

[RFC1096] Marcy, G., "Telnet X Display Location Option", RFC 1096,
          Carnegie Mellon University, March 1989.

[RFC1184] Borman, D., Editor, "Telnet Linemode Option",
          RFC 1184, Cray Research, Inc., October 1990.

[RFC1372] Hedrick, C., and D. Borman, "Telnet Remote Flow Control
         Option", RFC 1372, Rutgers University, Cray Research, Inc.,
         October 1992.

Top       Page 79 
[RFC1408] Borman, D., Editor, "Telnet Environment Option", RFC 1408,
          Cray Research, Inc., January 1993.

[RFC1409] Borman, D., Editor, "Telnet Authentication Option", RFC
          1409, Cray Research, Inc., January 1993.

[RFC1572] Alexander, S., Editor, "Telnet Environment Option", RFC1572,
          Lachman Technology, Inc., January 1994.

[RFC1647] Kelly, B., "TN3270 Enhancements", RFC1647, Auburn
          University, July 1994.


[BA4] Brian Anderson <baanders@CCQ.BBN.CO>


[DB14] Dave Borman <dab@CRAY.COM>

[DW183] David Waitzman <dwaitzman@BBN.COM>

[EAK4] Earl Kill <EAK@MORDOR.S1.GOV>

[GM23] Glenn Marcy  <Glenn.Marcy@A.CS.CMU.EDU>

[JBP] Jon Postel <>


[MS56] Marvin Solomon <solomon@CS.WISC.EDU>

[RN6] Rudy Nedved <Rudy.Nedved@CMU-CS-A.>

[Schoch]  Steven Schoch <>

[SL70] Stuart Levy <slevy@UC.MSC.UMN.EDU>

[SXS] Steve Silverman <Blankert@MITRE-GATEWAY.ORG>

[YXR] Yakov Rekhter  <Yakov@IBM.COM>



Top       Page 80 

The Internet Domain Naming System (DOMAIN) includes several
parameters.  These are documented in [RFC1034] and [RFC1035].  The
CLASS parameter is listed here.  The per CLASS parameters are defined
in separate RFCs as indicated.

Domain System Parameters:

Decimal   Name                                          References
--------  ----                                          ----------
       0  Reserved                                           [PM1]
       1  Internet (IN)                              [RFC1034,PM1]
       2  Unassigned                                         [PM1]
       3  Chaos (CH)                                         [PM1]
       4  Hessoid (HS)                                       [PM1]
 5-65534  Unassigned                                         [PM1]
   65535  Reserved                                           [PM1]

In the Internet (IN) class the following TYPEs and QTYPEs are defined:

TYPE            value and meaning

A               1 a host address                         [RFC1035]
NS              2 an authoritative name server           [RFC1035]
MD              3 a mail destination (Obsolete - use MX) [RFC1035]
MF              4 a mail forwarder (Obsolete - use MX)   [RFC1035]
CNAME           5 the canonical name for an alias        [RFC1035]
SOA             6 marks the start of a zone of authority [RFC1035]
MB              7 a mailbox domain name (EXPERIMENTAL)   [RFC1035]
MG              8 a mail group member (EXPERIMENTAL)     [RFC1035]
MR              9 a mail rename domain name (EXPERIMENTAL)[RFC1035]
NULL            10 a null RR (EXPERIMENTAL)              [RFC1035]
WKS             11 a well known service description      [RFC1035]
PTR             12 a domain name pointer                 [RFC1035]
HINFO           13 host information                      [RFC1035]
MINFO           14 mailbox or mail list information      [RFC1035]
MX              15 mail exchange                         [RFC1035]
TXT             16 text strings                          [RFC1035]

RP              17 for Responsible Person                [RFC1183]
AFSDB           18 for AFS Data Base location            [RFC1183]
X25             19 for X.25 PSDN address                 [RFC1183]
ISDN            20 for ISDN address                      [RFC1183]
RT              21 for Route Through                     [RFC1183]

NSAP            22 for NSAP address, NSAP style A record [RFC1348]
NSAP-PTR        23 for domain name pointer, NSAP style   [RFC1348]

Top       Page 81 
SIG             24 for security signature        [Donald Eastlake]
KEY             25 for security key              [Donald Eastlake]

PX              26 X.400 mail mapping information        [RFC1664]

GPOS            27 Geographical Position           [Craig Farrell]

AAAA            28 IP6 Address                     [Susan Thomson]

AXFR            252 transfer of an entire zone           [RFC1035]
MAILB           253 mailbox-related RRs (MB, MG or MR)   [RFC1035]
MAILA           254 mail agent RRs (Obsolete - see MX)   [RFC1035]
*               255 A request for all records            [RFC1035]


[RFC1034] Mockapetris, P., "Domain Names - Concepts and
          Facilities", STD 13, RFC 1034, USC/Information Sciences
          Institute, November 1987.

[RFC1035] Mockapetris, P., "Domain Names - Implementation and
          Specification", STD 13, RFC 1035, USC/Information Sciences
          Institute, November 1987.

[RFC1183] Everhart, C., Mamakos, L., Ullmann, R., and P. Mockapetris,
          Editors, "New DNS RR Definitions", RFC 1183, Transarc,
          University of Maryland, Prime Computer, USC/Information
          Sciences Institute, October 1990.

[RFC1348] Manning, B., "DNS NSAP RRs", RFC 1348, Rice University,
          July 1992.

[RFC1664] Allocchio, C., Bonito, A., Cole, B., Giordano, S., and R.
          Hagens, "Using the Internet DNS to Distribute RFC1327 Mail
          Address Mapping Tables", GARR-Italy, Cisco Systems Inc.,
          Centro Svizzero Calcolo Scientifico, Advanced Network &
          Services, August 1994.


[Susan Thomson] Susan Thomson <>

[PM1] Paul Mockapetris <>

[Donald Eastlake] Donald E. Eastlake, III <>

Top       Page 82 
[Craig Farrell]



Top       Page 83 

[RFC1505] specifies an initial list of keywords for the experimental
encoding header field (EHF-MAIL), and provides that additional
keywords may be registered with the IANA.

Keyword         Description                             Reference
_______         ___________                          ____________

EDIFACT         EDIFACT format                          [RFC1505]
EDI-X12         EDI X12 format                         [ANSI-X12]
EVFU            FORTRAN format                          [RFC1505]
FS              File System format                      [RFC1505]
Hex             Hex binary format                       [RFC1505]
LZJU90          LZJU90 format                           [RFC1505]
LZW             LZW format                              [RFC1505]
Message         Encapsulated Message                     [RFC822]
PEM, PEM-Clear  Privacy Enhanced Mail                   [RFC1421]
PGP             Pretty Good Privacy                     [RFC1505]
Postscript      Postscript format                    [POSTSCRIPT]
Shar            Shell Archive format                    [RFC1505]
Signature       Signature                               [RFC1505]
Tar             Tar format                              [RFC1505]
Text            Text                                   [IS-10646]
uuencode        uuencode format                         [RFC1505]
URL             external URL-reference                  [RFC1505]


[RFC822] specifies that Encryption Types for mail may be assigned.
There are currently no RFC 822 encryption types assigned.  Please use
instead the Mail Privacy procedures defined in [RFC1421, RFC1422,


[RFC1651] specifies that extension to SMTP can be identified with

Keywords        Description                              Reference

Top       Page 84 
------------    --------------------------------         ---------
SEND            Send as mail                              [RFC821]
SOML            Send as mail or terminal                  [RFC821]
SAML            Send as mail and terminal                 [RFC821]
EXPN            Expand the mailing list                   [RFC821]
HELP            Supply helpful information                [RFC821]
TURN            Turn the operation around                 [RFC821]
8BITMIME        Use 8-bit data                           [RFC1652]
SIZE            Message size declaration                 [RFC1653]
VERB            Verbose                              [Eric Allman]
ONEX            One message transaction only         [Eric Allman]


The Simple Mail Transfer Protocol [RFC821] specifies a set of
commands or services for mail transfer.  A general procedure for
extending the set of services is defined in [RFC1651].  The set of
service extensions is listed here.

Service Ext   EHLO Keyword Parameters Verb       Reference
-----------   ------------ ---------- ---------- ---------
Send             SEND         none       SEND     [RFC821]
Send or Mail     SOML         none       SOML     [RFC821]
Send and Mail    SAML         none       SAML     [RFC821]
Expand           EXPN         none       EXPN     [RFC821]
Help             HELP         none       HELP     [RFC821]
Turn             TURN         none       TURN     [RFC821]
8 Bit MIME       8BITMIME     none       none    [RFC1652]
Size             SIZE         number     none    [RFC1653]


In some places, an identification of other mail systems is used.

One of these is in "The COSINE and Internet X.500 Schema" (section
9.3.18) [RFC1274].  The mail system names listed here are used as the
legal values in that schema under the "otherMailbox" attribute
"mailboxType" type (which must be a PrintableString).

Another place is in "Mapping between X.400(1988) / ISO 10021 and RFC
822" (section 4.2.2) [RFC1327].  The names listed here are used as

Top       Page 85 
the legal values in that schema under the "std-or-address" attribute
"registered-dd-type" type (which must be a "key-string").

Note that key-string = <a-z, A-Z, 0-9, and "-" >.

Mail System Name        Description                     Reference
----------------        ------------------------------- ---------
mcimail                 MCI Mail


The Simple Mail Transfer Protocol [RFC821] and the Standard for the
Format of ARPA Internet Text Messages [RFC822] specify that a set of
"Received" lines will be prepended to the headers of electronic mail
messages as they are transported through the Internet.  These received
line may optionally include either or both a "via" phrase and/or a
"with" phrase.  The legal values for the phrases are listed here.  The
via phrase is intended to indicate the link or physical medium over
which the message was transferred.  The with phrase is intended to
indicate the protocol or logical process that was used to transfer the

VIA link types  Description                             Reference
--------------  ----------------------------            ---------
UUCP            Unix-to-Unix Copy Program                   [???]

WITH protocol types  Description                        Reference
-------------------  ----------------------------       ---------
SMTP                 Simple Mail Transfer Protocol       [RFC821]
ESMTP                SMTP with Service Extensions       [RFC1651]



[POSTSCRIPT] Adobe Systems Inc., "PostScript Langpuage Reference
Manual", 2nd Edition, 2nd Printing, January 1991.


Top       Page 86 
[RFC821] Postel, J., "Simple Mail Transfer Protocol", STD 10, RFC 821,
         USC/Information Sciences Institute, August 1982.

[RFC822] Crocker, D., "Standard for the Format of ARPA-Internet Text
         Messages", STD 11, RFC 822, UDEL, August 1982.

[RFC1274] Barker, P., and S. Kille, "The COSINE and Internet X.500
          Schema", RFC 1274, University College London, November 1991.

[RFC1327] Hardcastle-Kille, S., "Mapping between X.400(1988) / ISO
          10021 and RFC 822", RFC 1327, University College London,
          May 1992.

[RFC1421] Linn, J., "Privacy Enhancement for Internet Electronic
          Mail: Part I: Message Encipherment and Authentication
          Procedures", RFC 1421, IAB IRTF PSRG, IETF PEM WG,
          February 1993.

[RFC1422] Kent, S., "Privacy Enhancement for Internet
          Electronic Mail: Part II -- Certificate-Based Key
          Management", BBN, IAB IRTF PSRG, IETF PEM, February 1993.

[RFC1423] Balenson, D., "Privacy Enhancement for Internet Electronic
          Mail: Part III -- Algorithms, Modes, and Identifiers",
          RFC 1423, TIS, IAB IRTF PSRG, IETF PEM WG, February 1993.

[RFC1505] Costanzo, A., Robinson, D., and R. Ullmann, "Encoding Header
          Field for Internet Messages", RFC 1505, AKC Consulting,
          Computervision Corporation, August 1993.

[RFC1651] Klensin, J., Freed, N., Rose, M., Stefferud, E., and D.
          Crocker, "SMTP Service Extensions", RFC 1651, MCI, Innosoft,
          Dover Beach Consulting, Inc., Network Management Associates,
          Inc., Silicon Graphics, Inc., July 1994.

[RFC1652] Klensin, J., Freed, N., Rose, M., Stefferud, E., and D.
          Crocker, "SMTP Service Extension for 8bit-MIMEtransport",
          RFC 1652, MCI, Innosoft, Dover Beach Consulting, Inc.,
          Network Management Associates, Inc., Silicon Graphics, Inc.,
          July 1994.

[RFC1653] Klensin, J., Freed, N., and K. Moore, "SMTP Service
          Extension for Message Size Declaration", RFC 1653,
          MCI, Innosoft, University of Tennessee, July 1994.


Top       Page 87 
[Eric Allman]



Top       Page 88 

The Bootstrap Protocol (BOOTP) [RFC951] describes an IP/UDP
bootstrap protocol (BOOTP) which allows a diskless client machine to
discover its own IP address, the address of a server host, and the
name of a file to be loaded into memory and executed.  The Dynamic
Host Configuration Protocol (DHCP) [RFC1531] provides a framework for
automatic configuration of IP hosts.  The "DHCP Options and BOOTP
Vendor Information Extensions" [RFC1533] describes the additions to the
Bootstrap Protocol (BOOTP) which can also be used as options with the
Dynamic Host Configuration Protocol (DHCP).

BOOTP Vendor Extensions and DHCP Options are listed below:

   Tag     Name          Data Length    Meaning
   ---     ----          -----------    -------
    0      Pad               0          None
    1      Subnet Mask       4          Subnet Mask Value
    2      Time Offset       4          Time Offset in
                                        Seconds from UTC
    3      Gateways          N          N/4 Gateway addresses
    4      Time Server       N          N/4 Timeserver addresses
    5      Name Server       N          N/4 IEN-116 Server addresses
    6      Domain Server     N          N/4 DNS Server addresses
    7      Log Server        N          N/4 Logging Server addresses
    8      Quotes Server     N          N/4 Quotes Server addresses
    9      LPR Server        N          N/4 Printer Server addresses
   10      Impress Server    N          N/4 Impress Server addresses
   11      RLP Server        N          N/4 RLP Server addresses
   12      Hostname          N          Hostname string
   13      Boot File Size    2          Size of boot file in 512 byte
   14      Merit Dump File              Client to dump and name
                                        the file to dump it to
   15      Domain Name       N          The DNS domain name of the
   16      Swap Server       N          Swap Server addeess
   17      Root Path         N          Path name for root disk
   18      Extension File    N          Path name for more BOOTP info

   19      Forward On/Off    1          Enable/Disable IP Forwarding
   20      SrcRte On/Off     1          Enable/Disable Source Routing
   21      Policy Filter     N          Routing Policy Filters
   22      Max DG Assembly   2          Max Datagram Reassembly Size
   23      Default IP TTL    1          Default IP Time to Live
   24      MTU Timeout       4          Path MTU Aging Timeout
   25      MTU Plateau       N          Path MTU  Plateau Table

Top       Page 89 
   26      MTU Interface     2          Interface MTU Size
   27      MTU Subnet        1          All Subnets are Local
   28      Broadcast Address 4          Broadcast Address
   29      Mask Discovery    1          Perform Mask Discovery
   30      Mask Supplier     1          Provide Mask to Others
   31      Router Discovery  1          Perform Router Discovery
   32      Router Request    4          Router Solicitation Address
   33      Static Route      N          Static Routing Table
   34      Trailers          1          Trailer Encapsulation
   35      ARP Timeout       4          ARP Cache Timeout
   36      Ethernet          1          Ethernet Encapsulation
   37      Default TCP TTL   1          Default TCP Time to Live
   38      Keepalive Time    4          TCP Keepalive Interval
   39      Keepalive Data    1          TCP Keepalive Garbage
   40      NIS Domain        N          NIS Domain Name
   41      NIS Servers       N          NIS Server Addresses
   42      NTP Servers       N          NTP Server Addresses
   43      Vendor Specific   N          Vendor Specific Information
   44      NETBIOS Name Srv  N          NETBIOS Name Servers
   45      NETBIOS Dist Srv  N          NETBIOS Datagram Distribution
   46      NETBIOS Note Type 1          NETBIOS Note Type
   47      NETBIOS Scope     N          NETBIOS Scope
   48      X Window Font     N          X Window Font Server
   49      X Window Manmager N          X Window Display Manager
   50      Address Request   4          Requested IP Address
   51      Address Time      4          IP Address Lease Time
   52      Overload          1          Overloaf "sname" or "file"
   53      DHCP Msg Type     1          DHCP Message Type
   54      DHCP Server Id    4          DHCP Server Identification
   55      Parameter List    N          Parameter Request List
   56      DHCP Message      N          DHCP Error Message
   57      DHCP Max Msg Size 2          DHCP Maximum Message Size
   58      Renewal Time      4          DHCP Renewal (T1) Time
   59      Rebinding Time    4          DHCP Rebinding (T2) Time
   60      Class Id          N          Class Identifier
   61      Client Id         N          Client Identifier
   62      Netware/IP Domain N          Netware/IP Domain Name
   63      Netware/IP Option N          Netware/IP sub Options

   64-127  Unassigned
   128-154 Reserved

   255     End               0          None


Top       Page 90 
[RFC951]  Croft, B., and J. Gilmore, "BOOTSTRAP Protocol (BOOTP)",
          RFC-951, Stanford and SUN Microsytems, September 1985.

[RFC1531]  Droms, R., "Dynamic Host Configuration Protocol", Bucknell
           University, October 1993.

[RFC1533]  Alexander, S., and R. Droms, "DHCP Options and BOOTP Vendor
           Extensions", Lachman Technology, Inc., Bucknell University,
           October 1993.



Top       Page 91 

Several protocols deal with multiple address families.  The 16-bit
assignments are listed here.

Number    Description                                          Reference
------    ---------------------------------------------------- ---------
     0    Reserved
     1    IP (IP version 4)
     2    IP6 (IP version 6)
     3    NSAP
     4    HDLC (8-bit multidrop)
     5    BBN 1822
     6    802 (includes all 802 media plus Ethernet "canonical format")
     7    E.163
     8    E.164 (SMDS, Frame Relay, ATM)
     9    F.69 (Telex)
    10    X.121 (X.25, Frame Relay)
    11    IPX
    12    Appletalk
    13    Decnet IV
    14    Banyan Vines
 65535    Reserved



Top       Page 92 

In the FTP Operation Over Big Address Records (FOOBAR) Protocol
[RFC1639] there is a field, called "address family" or "af", to
identify the lower level protocol addresses in use.  This is an 8 bit
field.  The first 16 assignments (0-15) of the af value are exactly
the same as the IP Version number.  The assignment for values 16-255
are listed here.

Assigned FOOBAR Address Families

Decimal   Keyword    Address Family                     References
-------   -------    --------------                     ----------
    16    IPX        Novell IPX
17-254               Unassigned
   255               Reserved


[RFC1639] Piscitello, D., "FTP Operation Over Big Address Records
          (FOOBAR)", Core Competence, Inc., June 1994.



Top       Page 93 

In the representation of distinquished names (and possibly other
contexts) of the X.500 Directory system, several unique keywords may
be necessary.  For example, in the string representation of
distinguished names [RFC1485].

Keyword  Attribute (X.520 keys)
-------  ---------------------------------
 CN       CommonName
 L        LocalityName
 ST       StateOrProvinceName
 O        OrganizationName
 OU       OrganizationalUnitName
 C        CountryName


[RFC1485]  Hardcastle-Kille, S., "A String Representation of
           Distinguished Names (OSI-DS 23 (v5))", RFC1485, ISODE
           Consortium, July 1993.



Top       Page 94 

The RFC "A Format for E-Mailing Bibliographic Records" [RFC1357]
establishs a "publisher-ID" code.  The IANA registry of these codes is
listed here.

Code   Publisher                                               Reference
------ ------------------------------------------------------- ---------
DUMMY  for testing only                                         [RFC1357]
TEST   for testing only                                         [RFC1357]
ISI    Information Sciences Institute                               [JBP]
          of the University of Southern California
UMCS   University of Manchester Computer Science Department         [TXC]


[RFC1357] Cohen, D., Editor, "A Format for E-mailing Bibliographic
          Records", RFC 1357, USC/Information Sciences Institute,
          July 1992.


[JBP] Jon Postel <>

[TXC] Tim Clement <>



Top       Page 95 

The Open Shotrest Path First (OSPF) protocols has a provision for
authentication, and the type of authentication can me indicated by a
code number.  The following are the registered authentication codes.

Code    Authentication Method                             Reference
----    ---------------------                             ---------
   0    No Authentication                                 [RFC1583]
   1    Simple Password Authentication                    [RFC1583]
2-65535 Reserved


[RFC1583] Moy, J., "OSPF Version 2", RFC 1583, Proteon, Inc., March

[RFC1584] Moy, J., "Multicast Extensions to OSPF", RFC 1584, Proteon,
          Inc., March 1994.

[RFC1585] Moy, J., "MOSPF: Analysis and Experience", RFC 1585,
          Proteon, Inc., March 1994.

[RFC1586] deSouza, O., and M. Rodrigues, "Guidelines for Running OSPF
          Over Frame Relay Networks", RFC 1586, AT&T Bell
          Laboratories, March 1994.

[RFC1587] Coltun, R., and V. Fuller, "The OSPF NSSA Option", RFC 1587,
          RainbowBridge Communications, BARRNet, March 1994.



Top       Page 96 

[RFC1521] specifies that Content Types, Content Subtypes, Character
Sets, Access Types, and Conversion values for MIME mail will be
assigned and listed by the IANA.

Content Types and Subtypes

Type            Subtype         Description                 Reference
----            -------         -----------                 ---------
text            plain                                   [RFC1521,NSB]
                richtext                                [RFC1521,NSB]
                tab-separated-values                   [Paul Lindner]

multipart       mixed                                   [RFC1521,NSB]
                alternative                             [RFC1521,NSB]
                digest                                  [RFC1521,NSB]
                parallel                                [RFC1521,NSB]
                appledouble                [MacMime,Patrik Faltstrom]
                header-set                             [Dave Crocker]

message         rfc822                                  [RFC1521,NSB]
                partial                                 [RFC1521,NSB]
                external-body                           [RFC1521,NSB]
                news                        [RFC 1036, Henry Spencer]

application     octet-stream                            [RFC1521,NSB]
                postscript                              [RFC1521,NSB]
                oda                                     [RFC1521,NSB]
                atomicmail                           [atomicmail,NSB]
                andrew-inset                       [andrew-inset,NSB]
                slate                           [slate,terry crowley]
                wita              [Wang Info Transfer,Larry Campbell]
                dec-dx            [Digital Doc Trans, Larry Campbell]
                dca-rft        [IBM Doc Content Arch, Larry Campbell]
                activemessage                          [Ehud Shapiro]
                rtf                                    [Paul Lindner]
                applefile                  [MacMime,Patrik Faltstrom]
                mac-binhex40               [MacMime,Patrik Faltstrom]
                news-message-id              [RFC1036, Henry Spencer]
                news-transmission            [RFC1036, Henry Spencer]
                wordperfect5.1                         [Paul Lindner]
                pdf                                    [Paul Lindner]
                zip                                    [Paul Lindner]
                macwriteii                             [Paul Lindner]

Top       Page 97 
                msword                                 [Paul Lindner]
                remote-printing                         [RFC1486,MTR]

image           jpeg                                    [RFC1521,NSB]
                gif                                     [RFC1521,NSB]
                ief             Image Exchange Format       [RFC1314]
                tiff            Tag Image File Format           [MTR]

audio           basic                                   [RFC1521,NSB]

video           mpeg                                    [RFC1521,NSB]
                quicktime                              [Paul Lindner]

The "media-types" directory contains a subdirectory for each content
type and each of those directories contains a file for each content


   URL =

Character Sets

All of the character sets listed the section on Character Sets are
registered for use with MIME as MIME Character Sets.  The
correspondance between the few character sets listed in the MIME
specification [RFC1521] and the list in that section are:

Type           Description                                  Reference
----           -----------                                  ---------
US-ASCII       see ANSI_X3.4-1968 below                 [RFC1521,NSB]
ISO-8859-1     see ISO_8859-1:1987 below                [RFC1521,NSB]
ISO-8859-2     see ISO_8859-2:1987 below                [RFC1521,NSB]
ISO-8859-3     see ISO_8859-3:1988 below                [RFC1521,NSB]
ISO-8859-4     see ISO_8859-4:1988 below                [RFC1521,NSB]
ISO-8859-5     see ISO_8859-5:1988 below                [RFC1521,NSB]
ISO-8859-6     see ISO_8859-6:1987 below                [RFC1521,NSB]
ISO-8859-7     see ISO_8859-7:1987 below                [RFC1521,NSB]
ISO-8859-8     see ISO_8859-8:1988 below                [RFC1521,NSB]
ISO-8859-9     see ISO_8859-9:1989 below                [RFC1521,NSB]

Top       Page 98 
Access Types

Type           Description                                  Reference
----           -----------                                  ---------
FTP                                                     [RFC1521,NSB]
ANON-FTP                                                [RFC1521,NSB]
TFTP                                                    [RFC1521,NSB]
AFS                                                     [RFC1521,NSB]
LOCAL-FILE                                              [RFC1521,NSB]
MAIL-SERVER                                             [RFC1521,NSB]

Conversion Values

Conversion values or Content Transfer Encodings.

Type           Description                                  Reference
----           -----------                                  ---------
7BIT                                                    [RFC1521,NSB]
8BIT                                                    [RFC1521,NSB]
BASE64                                                  [RFC1521,NSB]
BINARY                                                  [RFC1521,NSB]
QUOTED-PRINTABLE                                        [RFC1521,NSB]


MIME to X.400 Table

    MIME content-type          X.400 Body Part             Reference
    -----------------          ------------------          ---------
      charset=us-ascii         ia5-text                     [RFC1494]
      charset=iso-8859-x       EBP - GeneralText            [RFC1494]
    text/richtext              no mapping defined           [RFC1494]
    application/oda            EBP - ODA                    [RFC1494]
    application/octet-stream   bilaterally-defined          [RFC1494]
    application/postscript     EBP - mime-postscript-body   [RFC1494]
    image/g3fax                g3-facsimile                 [RFC1494]
    image/jpeg                 EBP - mime-jpeg-body         [RFC1494]
    image/gif                  EBP - mime-gif-body          [RFC1494]
    audio/basic                no mapping defined           [RFC1494]
    video/mpeg                 no mapping defined           [RFC1494]

    Abbreviation: EBP - Extended Body Part

Top       Page 99 
X.400 to MIME Table

                             Basic Body Parts

    X.400 Basic Body Part      MIME content-type           Reference
    ---------------------      --------------------        ---------
    ia5-text                   text/plain;charset=us-ascii [RFC1494]
    voice                      No Mapping Defined          [RFC1494]
    g3-facsimile               image/g3fax                 [RFC1494]
    g4-class1                  no mapping defined          [RFC1494]
    teletex                    no mapping defined          [RFC1494]
    videotex                   no mapping defined          [RFC1494]
    encrypted                  no mapping defined          [RFC1494]
    bilaterally-defined        application/octet-stream    [RFC1494]
    nationally-defined         no mapping defined          [RFC1494]
    externally-defined         See Extended Body Parts     [RFC1494]

    X.400 Extended Body Part  MIME content-type            Reference
    ------------------------- --------------------         ---------
    GeneralText               text/plain;charset=iso-8859-x[RFC1494]
    ODA                       application/oda              [RFC1494]
    mime-postscript-body      application/postscript       [RFC1494]
    mime-jpeg-body            image/jpeg                   [RFC1494]
    mime-gif-body             image/gif                    [RFC1494]


[MacMime] Work in Progress.

[RFC1036] Horton, M., and R. Adams, "Standard for Interchange of
          USENET Messages", RFC 1036, AT&T Bell Laboratories,
          Center for Seismic Studies, December 1987.

[RFC1494] Alvestrand, H., and S. Thompson, "Equivalences between 1988
          X.400 and RFC-822 Message Bodies", RFC 1494, SINTEF DELAB,
          Soft*Switch, Inc., August 1993.

[RFC1521] Borenstien, N., and N. Freed, "MIME (Multipurpose Internet
          Mail Extensions) Part One: Mechanisms for Specifying and
          Describing the Format of Internet Message Bodies", RFC 1521,
          Bellcore, Innosoft, September 1993.


[Larry Campbell]

[Dave Crocker]  Dave Crocker <>

Next RFC Part