RFC781 Specification of the Internet Protocol (IP) timestamp option

0781 Specification of the Internet Protocol (IP) timestamp option. Z.Su. May 1981. (Format: TXT=4002 bytes) (Status: UNKNOWN)

日本語訳
RFC一覧

参照

RFC 781                                                            Zaw-Sing Su
                                                                           SRI
                                                                      May 1981


A SPECIFICATION OF THE INTERNET PROTOCOL (IP) TIMESTAMP OPTION





I. INTRODUCTION

     Packet switching is store-and-forward by nature.  Network delay is a
therefore a critical performance measure for packet-switching communications.
A catenet is a system of packet-switched communication networks interconnected
via gateways [Cerf 78].  The catenet "link" delays are thus variable.  Their
measurement, the measurement of delays across member networks of a catenet,
becomes important for catenet investigations.

     An effective way to measure catenet delays is by means of packet header
timestamping.  Header timestamping allows monitoring of catenet delays for
user traffic, such as the case of Ft. Bragg users accessing ISID across the
catenet.  Packet header timestamping is also compatible with the use of test
packets for catenet delay measurement.  Another advantage of header
timestamping is that since it is an IP option, the gateway imposes little
difference in the treatment of such a packet.  In this note, a specification
of the timestamp option format for IP is presented.

     Measurement of one-way delay, either end-to-end or across an individual
network, requires that device clocks be synchronized, using such facilities as
WWVB clocks [Mills 81].  This specification assumes this capability in the
gateways and involved network hosts.
    

II.  FORMAT SPECIFICATION

     As an IP option, the contents of the first two octets are dictated by the
IP header format to be option type and option length in octets [Postel 80].
The next two octets are used to control this option.


     0               7               15              23              31
     +---------------+---------------+---------------+---------------+
     |     type      |    length     |    offset     |overflw| flags |
     +---------------+---------------+---------------+---------------+
     |                          internet ID                          |
     +---------------+---------------+---------------+---------------+
     |                          time stamp                           |
     +---------------+---------------+---------------+---------------+
				     .
				     .
				     .




     option type = 68 decimal (i.e., option class = 2 and option number = 4);

     option length = the number of octets with a maximum of 40 (limited by
		 IHL = 15);

     offset =    the number of octets from the beginning of this option to the
		 end of timestamps (i.e., the beginning of space for next
		 timestamp).  It is set to one, an odd number, when no more
		 space remains in the header for timestamps;

     overflow =  the number of IP modules that cannot register timestamps due
		 to lack of space;

     flag = 0 -- time stamps only
	    1 -- each timestamp is preceded with internet ID of the
		 registering entity
	    3 -- the internet ID fields are prespecified.  An IP module only
		 registers its timestamp if it matches its own ID with the
		 next specified internet ID;

     internet ID = ID for the timestamping device;

     timestamp = a right-justified, 32-bit timestamp in milliseconds modulo
		 24 hours from midnight UT.

     The timestamp option is not copied upon fragmentation.  It is carried in
the first fragment.


REFERENCES

[Cerf 78]   Cerf, V., "The Catenet Model for Internetworking," Defense
	    Advanced Research Projects Agency, Information Processing
	    Techniques Office, IEN 48, July 1978.

[Mills 81]  Mills, D.L., "DCNET Internet Clock Service," RFC 778, COMSAT
	    Laboratories, April 1981.

[Postel 80] Postel, J. (ed.), "DoD Standard Transport Internet Protocol,"
	    Defense Advanced Reseach Projects Agency, Information Processing

一覧

 RFC 1〜100  RFC 1401〜1500  RFC 2801〜2900  RFC 4201〜4300 
 RFC 101〜200  RFC 1501〜1600  RFC 2901〜3000  RFC 4301〜4400 
 RFC 201〜300  RFC 1601〜1700  RFC 3001〜3100  RFC 4401〜4500 
 RFC 301〜400  RFC 1701〜1800  RFC 3101〜3200  RFC 4501〜4600 
 RFC 401〜500  RFC 1801〜1900  RFC 3201〜3300  RFC 4601〜4700 
 RFC 501〜600  RFC 1901〜2000  RFC 3301〜3400  RFC 4701〜4800 
 RFC 601〜700  RFC 2001〜2100  RFC 3401〜3500  RFC 4801〜4900 
 RFC 701〜800  RFC 2101〜2200  RFC 3501〜3600  RFC 4901〜5000 
 RFC 801〜900  RFC 2201〜2300  RFC 3601〜3700  RFC 5001〜5100 
 RFC 901〜1000  RFC 2301〜2400  RFC 3701〜3800  RFC 5101〜5200 
 RFC 1001〜1100  RFC 2401〜2500  RFC 3801〜3900  RFC 5201〜5300 
 RFC 1101〜1200  RFC 2501〜2600  RFC 3901〜4000  RFC 5301〜5400 
 RFC 1201〜1300  RFC 2601〜2700  RFC 4001〜4100  RFC 5401〜5500 
 RFC 1301〜1400  RFC 2701〜2800  RFC 4101〜4200 

スポンサーリンク

携帯サイトでのmailtoの使い方

ホームページ製作・web系アプリ系の製作案件募集中です。

上に戻る