Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!LANL.GOV!cpw%sneezy
From: cpw%sneezy@LANL.GOV (C. Philip Wood)
Newsgroups: comp.protocols.tcp-ip
Subject: Re:  RFC 1063 question
Message-ID: <8908021449.AA08925@sneezy.lanl.gov>
Date: 2 Aug 89 14:49:16 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 38

The absense of the 'copy on fragmentation' flag indicates that there is
no need to copy on fragmentation.  See my IP option wall chart below:
(Please send flaming corrections to cpw@lanl.gov)

Two types of options fixed and variable:

TYPE	        MNE LEN  First Octet    Second Octet    Function
	
		 	 C CL   NUM     OLEN

   F		EOL   1  0 00 00000   	N/A		End of Option List.
   F		NOP   1  0 00 00001   	N/A		No OPeration 

  V/F      SECURITY  11  1 00 00010     00001011	SECURITY.
   V	       LSRR var  1 00 00011 			Loose Source and RR
   V	         TS var  0 10 00100                     Time Stamp.
   V      XSECURITY var  1 00 00101                     eXtended SECURITY.
                    xxx  x xx 00110                     not defined
   V	         RR var  0 00 00111                     Record Route.
  V/F         SATID   4  1 00 01000     00000100**      SATnet stream ID.
   V	       SSRR var  1 00 01001                     Strict Source and RR
                    xxx  x xx 01010                     not defined
  V/F	       PMTU   4	 1 00 01011   	00000100        Probe MTU
  V/F	       RMTU   4  1 00 01100     00000100        Reply MTU

TYPE	(F = Fixed), (V = Variable), (V/F = Fixed but with length octet).
MNE 	mneumonic
LEN	length of option
C   	copied flag (copy on fragmentation, if set to 1)
CL  	option class 
	0 = control
	1 = reserved for future use
	2 = debugging and measurement
	3 = reserved for future use
NUM 	option number
OLEN	value of option length field for variable length options

** RFC 791 indicates 00000010 which must be a typo.