Debian Codegraph @

rfc8507.html

raw
1 <pre>Independent Submission S. Deering
2 Request for Comments: 8507 Retired
3 Category: Historic R. Hinden, Ed.
4 ISSN: 2070-1721 Check Point Software
5 December 2018
6
7
8 <span class="h1">Simple Internet Protocol (SIP) Specification</span>
9
10 Abstract
11
12 This document is published for the historical record. The Simple
13 Internet Protocol was the basis for one of the candidates for the
14 IETF's Next Generation (IPng) work that became IPv6.
15
16 The publication date of the original Internet-Draft was November 10,
17 1992. It is presented here substantially unchanged and is neither a
18 complete document nor intended to be implementable.
19
20 The paragraph that follows is the Abstract from the original draft.
21
22 This document specifies a new version of IP called SIP, the Simple
23 Internet Protocol. It also describes the changes needed to ICMP,
24 IGMP, and transport protocols such as TCP and UDP, in order to work
25 with SIP. A companion document [<a href="#ref-SIP-ADDR" title="&quot;Simple Internet Protocol (SIP) Addressing and Routing&quot;">SIP-ADDR</a>] describes the addressing
26 and routing aspects of SIP, including issues of auto-configuration,
27 host and subnet mobility, and multicast.
28
29 Status of This Memo
30
31 This document is not an Internet Standards Track specification; it is
32 published for the historical record.
33
34 This document defines a Historic Document for the Internet community.
35 This is a contribution to the RFC Series, independently of any other
36 RFC stream. The RFC Editor has chosen to publish this document at
37 its discretion and makes no statement about its value for
38 implementation or deployment. Documents approved for publication by
39 the RFC Editor are not candidates for any level of Internet Standard;
40 see <a href="./rfc7841#section-2">Section&nbsp;2 of RFC 7841</a>.
41
42 Information about the current status of this document, any errata,
43 and how to provide feedback on it may be obtained at
44 <a href="https://www.rfc-editor.org/info/rfc8507">https://www.rfc-editor.org/info/rfc8507</a>.
45
46
47
48
49
50
51
52 <span class="grey">Deering &amp; Hinden Historic [Page 1]</span></pre>
53 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
54 <span class="grey"><a href="./rfc8507">RFC 8507</a> Simple IP (SIP) December 2018</span>
55
56
57 Copyright Notice
58
59 Copyright (c) 2018 IETF Trust and the persons identified as the
60 document authors. All rights reserved.
61
62 This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
63 Provisions Relating to IETF Documents
64 (<a href="https://trustee.ietf.org/license-info">https://trustee.ietf.org/license-info</a>) in effect on the date of
65 publication of this document. Please review these documents
66 carefully, as they describe your rights and restrictions with respect
67 to this document.
68
69 Table of Contents
70
71 <a href="#section-1">1</a>. Preface .........................................................<a href="#page-3">3</a>
72 <a href="#section-2">2</a>. Introduction ....................................................<a href="#page-3">3</a>
73 <a href="#section-3">3</a>. Terminology .....................................................<a href="#page-4">4</a>
74 <a href="#section-4">4</a>. SIP Header Format ...............................................<a href="#page-5">5</a>
75 <a href="#section-5">5</a>. Addresses .......................................................<a href="#page-6">6</a>
76 <a href="#section-5.1">5.1</a>. Text Representation of Addresses ...........................<a href="#page-6">6</a>
77 <a href="#section-5.2">5.2</a>. Unicast Addresses ..........................................<a href="#page-6">6</a>
78 <a href="#section-5.3">5.3</a>. Multicast Addresses ........................................<a href="#page-8">8</a>
79 <a href="#section-5.4">5.4</a>. Special Addresses ..........................................<a href="#page-9">9</a>
80 <a href="#section-6">6</a>. Packet Size Issues .............................................<a href="#page-12">12</a>
81 <a href="#section-7">7</a>. Source Routing Header ..........................................<a href="#page-13">13</a>
82 <a href="#section-8">8</a>. Fragmentation Header ...........................................<a href="#page-14">14</a>
83 <a href="#section-9">9</a>. Changes to Other Protocols .....................................<a href="#page-16">16</a>
84 <a href="#section-9.1">9.1</a>. Changes to ICMP ...........................................<a href="#page-16">16</a>
85 <a href="#section-9.2">9.2</a>. Changes to IGMP ...........................................<a href="#page-20">20</a>
86 <a href="#section-9.3">9.3</a>. Changes to Transport Protocols ............................<a href="#page-21">21</a>
87 <a href="#section-9.4">9.4</a>. Changes to Link-Layer Protocols ...........................<a href="#page-22">22</a>
88 <a href="#section-10">10</a>. Security Considerations .......................................<a href="#page-22">22</a>
89 <a href="#section-11">11</a>. Acknowledgments ...............................................<a href="#page-23">23</a>
90 <a href="#section-12">12</a>. Informative References ........................................<a href="#page-23">23</a>
91 <a href="#appendix-A">Appendix A</a>. SIP Design Rationale ..................................<a href="#page-25">25</a>
92 <a href="#appendix-B">Appendix B</a>. Future Directions .....................................<a href="#page-25">25</a>
93 Authors' Addresses ................................................<a href="#page-26">26</a>
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108 <span class="grey">Deering &amp; Hinden Historic [Page 2]</span></pre>
109 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
110 <span class="grey"><a href="./rfc8507">RFC 8507</a> Simple IP (SIP) December 2018</span>
111
112
113 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Preface</span>
114
115 This document is published for the historical record.
116
117 Simple IP (SIP) was the basis for one of the candidates for the
118 IETF's Next Generation (IPng) work; see "The Recommendation for the
119 IP Next Generation Protocol" [<a href="./rfc1752" title="&quot;The Recommendation for the IP Next Generation Protocol&quot;">RFC1752</a>]. The original 1992
120 Internet-Draft describing SIP is published here as part of the record
121 of that work.
122
123 SIP evolved into SIP Plus [<a href="./rfc1710" title="&quot;Simple Internet Protocol Plus White Paper&quot;">RFC1710</a>], which was assessed as a
124 candidate for IPng [<a href="./rfc1752" title="&quot;The Recommendation for the IP Next Generation Protocol&quot;">RFC1752</a>] and led eventually to the development of
125 IPv6, first published as [<a href="./rfc1883" title="&quot;Internet Protocol, Version 6 (IPv6) Specification&quot;">RFC1883</a>]. The current specification for
126 IPv6 is [<a href="./rfc8200" title="&quot;Internet Protocol, Version 6 (IPv6) Specification&quot;">RFC8200</a>].
127
128 The original Internet-Draft describing the Simple Internet Protocol
129 was written by Steve Deering, and the Internet-Draft was posted on
130 November 10, 1992. The contents of this document are unchanged from
131 that Internet-Draft, except for clarifications in the Abstract, the
132 addition of this section, modifications to the authors' information,
133 the updating of references, removal of the IANA considerations, and
134 minor formatting changes.
135
136 It should be noted that the original draft was not complete and that
137 no attempt has been made to complete it. This document is not
138 intended to be implementable.
139
140 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Introduction</span>
141
142 SIP is a new version of IP. Its salient differences from IP
143 version 4 [<a href="./rfc791" title="&quot;Internet Protocol&quot;">RFC791</a>], subsequently referred to as "IPv4", are:
144
145 o expansion of addresses to 64 bits,
146
147 o simplification of the IP header by eliminating some
148 inessential fields, and
149
150 o relaxation of length restrictions on optional data, such as
151 source-routing information.
152
153 SIP retains the IP model of globally-unique addresses,
154 hierarchically-structured for efficient routing. Increasing the
155 address size from 32 to 64 bits allows more levels of hierarchy to be
156 encoded in the addresses, enough to enable efficient routing in an
157 internet with tens of thousands of addressable devices in every
158 office, every residence, and every vehicle in the world. Keeping the
159
160
161
162
163
164 <span class="grey">Deering &amp; Hinden Historic [Page 3]</span></pre>
165 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
166 <span class="grey"><a href="./rfc8507">RFC 8507</a> Simple IP (SIP) December 2018</span>
167
168
169 addresses fixed-length and relatively compact facilitates
170 high-performance router and host implementation, and keeps the
171 bandwidth overhead of the SIP headers almost as low as IPv4.
172
173 The elimination of inessential fields also contributes to
174 high-performance implementation, and to the likelihood of correct
175 implementation. A change in the way that optional data, such as
176 source-routing information, is encoded allows for more efficient
177 forwarding and less stringent limits on the length of such data.
178
179 Despite these changes, SIP remains very similar to IPv4. This
180 similarity makes it easy to understand SIP (for those who already
181 understand IPv4), makes it possible to reuse much of the code and
182 data structures from IPv4 in an implementation of SIP (including
183 almost all of ICMP and IGMP), and makes it straightforward to
184 translate between SIP packets and IPv4 packets for transition
185 purposes [<a href="#ref-IPAE" title="&quot;IP Address Encapsulation (IPAE): A Mechanism for Introducing a New IP&quot;">IPAE</a>].
186
187 The subsequent sections of this document specify SIP and its
188 associated protocols without much explanation of why the design
189 choices were made the way they were. <a href="#appendix-A">Appendix A</a> presents the
190 rationale for those aspects of SIP that differ from IPv4.
191
192 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Terminology</span>
193
194 system - a device that implements SIP.
195
196 router - a system that forwards SIP packets.
197
198 host - any system that is not a router.
199
200 link - a communication facility or medium over which systems
201 can communicate at the link layer, i.e., the layer
202 immediately below SIP.
203
204 interface - a system's attachment point to a link.
205
206 address - a SIP-layer identifier for an interface or a group of
207 interfaces.
208
209 subnet - in the SIP unicast addressing hierarchy, a
210 lowest-level (finest-grain) cluster of addresses,
211 sharing a common address prefix (i.e., high-order
212 address bits). Typically, all interfaces attached to
213 the same link have addresses in the same subnet;
214 however, in some cases, a single link may support more
215 than one subnet, or a single subnet may span more than
216 one link.
217
218
219
220 <span class="grey">Deering &amp; Hinden Historic [Page 4]</span></pre>
221 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
222 <span class="grey"><a href="./rfc8507">RFC 8507</a> Simple IP (SIP) December 2018</span>
223
224
225 link MTU - the maximum transmission unit, i.e., maximum packet
226 size in octets, that can be conveyed in one piece over
227 a link (where a packet is a SIP header plus payload).
228
229 path MTU - the minimum link MTU of all the links in a path
230 between a source system and a destination system.
231
232 packetization
233 layer - any protocol layer above SIP that is responsible for
234 packetizing data to fit within outgoing SIP packets.
235 Typically, transport-layer protocols, such as TCP, are
236 packetization protocols, but there may also be
237 higher-layer packetization protocols, such as
238 protocols implemented on top of UDP.
239
240 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. SIP Header Format</span>
241
242 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
243 |Version| Reserved |
244 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
245 | Payload Length | Payload Type | Hop Limit |
246 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
247 | |
248 + Source Address +
249 | |
250 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
251 | |
252 + Destination Address +
253 | |
254 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
255
256 Version 4-bit IP version number = decimal 6.
257 &lt;to be confirmed&gt;
258
259 Reserved 28-bit reserved field. Initialized to zero
260 for transmission; ignored on reception.
261
262 Payload Length 16-bit unsigned integer. Length of payload,
263 i.e., the rest of the packet following the
264 SIP header, in octets.
265
266 Payload Type 8-bit selector. Identifies the type of
267 payload, e.g., TCP.
268
269 Hop Limit 8-bit unsigned integer. Decremented by 1
270 by each system that forwards the packet.
271 The packet is discarded if Hop Limit is
272 decremented to zero.
273
274
275
276 <span class="grey">Deering &amp; Hinden Historic [Page 5]</span></pre>
277 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
278 <span class="grey"><a href="./rfc8507">RFC 8507</a> Simple IP (SIP) December 2018</span>
279
280
281 Source Address 64 bits. See "Addresses" section, following.
282
283 Destination Address 64 bits. See "Addresses" section, following.
284
285 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Addresses</span>
286
287 <span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a>. Text Representation of Addresses</span>
288
289 SIP addresses are 64 bits (8 octets) long. The text representation
290 of a SIP addresses is 16 hexadecimal digits, with a colon between the
291 4th and 5th digits, and optional colons between any subsequent pair
292 of digits. Leading zeros must not be dropped. Examples:
293
294 0123:4567:89AB:CDEF
295
296 0123:456789ABCDEF
297
298 0123:456789AB:CDE:F
299
300 Programs that read the text representation of SIP addresses must be
301 insensitive to the presence or absence of optional colons. Programs
302 that write the text representation of a SIP address should use the
303 first format above (i.e., colons after the 4th, 8th, and 12th
304 digits), in the absence of any knowledge of the structure or
305 preferred format of the address, such as knowledge of the format in
306 which it was originally read.
307
308 The presence of at least one colon in the text representation allows
309 SIP addresses to be easily distinguished from both domain names and
310 the text representation of IPv4 addresses.
311
312 <span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a>. Unicast Addresses</span>
313
314 A SIP unicast address is a globally-unique identifier for a single
315 interface, i.e., no two interfaces in a SIP internet may have the
316 same unicast address. A single interface may, however, have more
317 than one unicast address.
318
319 A system considers its own unicast address(es) to have the following
320 structure, where different addresses may have different values for n:
321
322 | n bits | 64-n bits |
323 +----------------------------------------------------+------------+
324 | subnet prefix |interface ID|
325 +----------------------------------------------------+------------+
326
327
328
329
330
331
332 <span class="grey">Deering &amp; Hinden Historic [Page 6]</span></pre>
333 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
334 <span class="grey"><a href="./rfc8507">RFC 8507</a> Simple IP (SIP) December 2018</span>
335
336
337 To know the length of the subnet prefix, the system is required to
338 associate with each of its addresses a 'subnet mask' of the following
339 form:
340
341 | n bits | 64-n bits |
342 +----------------------------------------------------+------------+
343 |1111111111111111111111111111111111111111111111111111|000000000000|
344 +----------------------------------------------------+------------+
345
346 A system may have a subnet mask of all-ones, which means that the
347 system belongs to a subnet containing exactly one system -- itself.
348
349 A system acquires its subnet mask(s) at the same time, and by the
350 same mechanism, as it acquires its address(es), for example, by
351 manual configuration or by a dynamic configuration protocol such as
352 BOOTP [<a href="./rfc951" title="&quot;Bootstrap Protocol&quot;">RFC951</a>].
353
354 Hosts are ignorant of any further structure in a unicast address.
355
356 Routers may acquire, through manual configuration or the operation of
357 routing protocols, additional masks that identify higher-level
358 clusters in a hierarchical addressing plan. For example, the routers
359 within a single site would typically have a 'site mask', such as the
360 following:
361
362 | m bits | 64-m bits |
363 +-----------------------------------------+-----------------------+
364 |11111111111111111111111111111111111111111|00000000000000000000000|
365 +-----------------------------------------+-----------------------+
366
367 by which they could deduce the following structure in the site's
368 addresses:
369
370 | m bits | p bits | 64-m-p bits|
371 +-----------------------------------------+----------+------------+
372 | site prefix |subnet ID|interface ID|
373 +-----------------------------------------+----------+------------+
374
375 All knowledge by SIP systems of the structure of unicast addresses is
376 based on possession of such masks -- there is no "wired-in" knowledge
377 of unicast address formats.
378
379 The SIP Addressing and Routing document [<a href="#ref-SIP-ADDR" title="&quot;Simple Internet Protocol (SIP) Addressing and Routing&quot;">SIP-ADDR</a>] proposes two
380 hierarchical addressing plans, one based on a hierarchy of SIP
381 service providers, and one based on a geographic hierarchy.
382
383
384
385
386
387
388 <span class="grey">Deering &amp; Hinden Historic [Page 7]</span></pre>
389 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
390 <span class="grey"><a href="./rfc8507">RFC 8507</a> Simple IP (SIP) December 2018</span>
391
392
393 <span class="h3"><a class="selflink" id="section-5.3" href="#section-5.3">5.3</a>. Multicast Addresses</span>
394
395 A SIP multicast address is an identifier for a group of interfaces.
396 An interface may belong to any number of multicast groups. Multicast
397 addresses have the following format:
398
399 |1| 7 | 4 | 4 | 48 bits |
400 +-+-------+----+----+---------------------------------------------+
401 |C|1111111|flgs|scop| group ID |
402 +-+-------+----+----+---------------------------------------------+
403
404 where:
405
406 C = IPv4 compatibility flag; see [<a href="#ref-IPAE" title="&quot;IP Address Encapsulation (IPAE): A Mechanism for Introducing a New IP&quot;">IPAE</a>].
407
408 1111111 in the rest of the first octet identifies the address as
409 being a multicast address.
410
411 +-+-+-+-+
412 flgs is a set of 4 flags: |0|0|0|T|
413 +-+-+-+-+
414
415 the high-order 3 flags are reserved, and must be initialized
416 to 0.
417
418 T = 0 indicates a permanently-assigned ("well-known") multicast
419 address, assigned by the global internet numbering
420 authority.
421
422 T = 1 indicates a non-permanently-assigned ("transient")
423 multicast address.
424
425 scop is a 4-bit multicast scope value:
426
427 0 reserved
428 1 intra-system scope
429 2 intra-link scope
430 3 (unassigned)
431 4 (unassigned)
432 5 intra-site scope
433 6 (unassigned)
434 7 (unassigned)
435 8 intra-metro scope
436 9 (unassigned)
437 A (unassigned)
438 B intra-country scope
439 C (unassigned)
440
441
442
443
444 <span class="grey">Deering &amp; Hinden Historic [Page 8]</span></pre>
445 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
446 <span class="grey"><a href="./rfc8507">RFC 8507</a> Simple IP (SIP) December 2018</span>
447
448
449 D (unassigned)
450 E global scope
451 F reserved
452
453 group ID identifies the multicast group, either permanent or
454 transient, within the given scope.
455
456 The "meaning" of a permanently-assigned multicast address is
457 independent of the scope value. For example, if the "NTP servers
458 group" is assigned a permanent multicast address with a group ID of
459 43 (hex), then:
460
461 7F01:000000000043 means all NTP servers on the same system as the
462 sender.
463
464 7F02:000000000043 means all NTP servers on the same link as the
465 sender.
466
467 7F05:000000000043 means all NTP servers at the same site as the
468 sender.
469
470 7F0E:000000000043 means all NTP servers in the internet.
471
472 Non-permanently-assigned multicast addresses are meaningful only
473 within a given scope. For example, a group identified by the
474 non-permanent, intra-site multicast address 7F15:000000000043 at one
475 site bears no relationship to a group using the same address at a
476 different site, nor to a non-permanent group using the same group ID
477 with different scope, nor to a permanent group with the same
478 group ID.
479
480 <span class="h3"><a class="selflink" id="section-5.4" href="#section-5.4">5.4</a>. Special Addresses</span>
481
482 There are a number of "special purpose" SIP addresses:
483
484 The Unspecified Address: 0000:0000:0000:0000
485
486 This address shall never be assigned to any system. It may be
487 used wherever an address appears, to indicate the absence of an
488 address. One example of its use is in the Source Address field
489 of a SIP packet sent by an initializing host, before it has
490 learned its own address.
491
492 The Loopback Address: 0000:0000:0000:0001
493
494 This address may be used by a system to send a SIP packet to
495 itself.
496
497
498
499
500 <span class="grey">Deering &amp; Hinden Historic [Page 9]</span></pre>
501 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
502 <span class="grey"><a href="./rfc8507">RFC 8507</a> Simple IP (SIP) December 2018</span>
503
504
505 Anyone Addresses: &lt;prefix&gt;&lt;zero&gt;
506
507 Addresses of this form may be used to send to the "nearest"
508 system (according the routing protocols' measure of distance)
509 that "knows" it has a unicast address prefix of &lt;prefix&gt;.
510
511 Since hosts know only their subnet prefix(es), and no
512 higher-level prefixes, a host with the following address:
513
514 +----------------------------------------------+----------------+
515 | subnet prefix = A |interface ID = B|
516 +----------------------------------------------+----------------+
517
518 shall recognize only the following Anyone address as identifying
519 itself:
520
521 +----------------------------------------------+----------------+
522 | subnet prefix = A |0000000000000000|
523 +----------------------------------------------+----------------+
524
525 An intra-site router that knows that one of its addresses has the
526 format:
527
528 +-------------------------------+--------------+----------------+
529 | site prefix = X |subnet ID = Y|interface ID = Z|
530 +-------------------------------+--------------+----------------+
531
532 shall accept packets sent to either of the following two Anyone
533 addresses as if they had been sent to the router's own address:
534
535 +-------------------------------+-------------------------------+
536 | site prefix = X |0000000000000000000000000000000|
537 +-------------------------------+-------------------------------+
538
539 +-------------------------------+--------------+----------------+
540 | site prefix = X |subnet ID = Y|0000000000000000|
541 +-------------------------------+--------------+----------------+
542
543 Anyone Addresses work as follows:
544
545 If any system belonging to subnet A sends a packet to
546 subnet A's Anyone address, the packet shall be looped-back
547 within the sending system itself, since it is the nearest
548 system to itself with the subnet A prefix. If a system outside
549 of subnet A sends a packet to subnet A's Anyone address, the
550 packet shall be accepted by the first router on subnet A that
551 the packet reaches.
552
553
554
555
556 <span class="grey">Deering &amp; Hinden Historic [Page 10]</span></pre>
557 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
558 <span class="grey"><a href="./rfc8507">RFC 8507</a> Simple IP (SIP) December 2018</span>
559
560
561 Similarly, a packet sent to site X's Anyone address from
562 outside of site X shall be accepted by the first encountered
563 router belonging to site X, i.e., one of site X's boundary
564 routers. If a higher-level prefix P identifies, say, a
565 particular service provider, then a packet sent to &lt;P&gt; &lt;zero&gt;
566 from outside of provider P's facilities shall be delivered to
567 the nearest entry router into P's facilities.
568
569 Anyone addresses are most commonly used in conjunction with the
570 SIP source routing header, to cause a packet to be routed via one
571 or more specified "transit domains", without the need to identify
572 individual routers in those domains.
573
574 The value zero is reserved at each level of every unicast address
575 hierarchy, to serve as an Anyone address for that level.
576
577 The Reserved Multicast Address: 7F0s:0000:0000:0000
578
579 This multicast address (with any scope value, s) is reserved, and
580 shall never be assigned to any multicast group.
581
582 The All Systems Addresses: 7F01:0000:0000:0001
583 7F02:0000:0000:0001
584
585 These multicast addresses identify the group of all SIP systems,
586 within scope 1 (intra-system) or 2 (intra-link).
587
588 The All Hosts Addresses: 7F01:0000:0000:0002
589 7F02:0000:0000:0002
590
591 These multicast addresses identify the group of all SIP hosts,
592 within scope 1 (intra-system) or 2 (intra-link).
593
594 The All Routers Addresses: 7F01:0000:0000:0003
595 7F02:0000:0000:0003
596
597 These multicast addresses identify the group of all SIP routers,
598 within scope 1 (intra-system) or 2 (intra-link).
599
600
601 A host is required to recognize the following addresses as
602 identifying itself: its own unicast addresses, the Anyone addresses
603 with the same subnet prefixes as its unicast addresses, the Loopback
604 address, the All Systems and All Hosts addresses, and any other
605 multicast addresses to which the host belongs.
606
607
608
609
610
611
612 <span class="grey">Deering &amp; Hinden Historic [Page 11]</span></pre>
613 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
614 <span class="grey"><a href="./rfc8507">RFC 8507</a> Simple IP (SIP) December 2018</span>
615
616
617 A router is required to recognize the following addresses as
618 identifying itself: its own unicast addresses, the Anyone addresses
619 with the same subnet or higher-level prefixes as its unicast
620 addresses, the Loopback address, the All Systems and All Routers
621 addresses, and any other multicast addresses to which the host
622 belongs.
623
624 <span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Packet Size Issues</span>
625
626 SIP requires that every link in the internet have an MTU of 576
627 octets or greater. On any link that cannot convey a 576-octet packet
628 in one piece, link-specific fragmentation and reassembly must be
629 provided at a layer below SIP.
630
631 (Note: this minimum link MTU is NOT the same as the one in IPv4.
632 In IPv4, the minimum link MTU is 68 octets [ [<a href="./rfc791" title="&quot;Internet Protocol&quot;">RFC791</a>], page 25 ];
633 576 octets is the minimum reassembly buffer size required in an
634 IPv4 system, which has nothing to do with link MTUs.)
635
636 From each link to which a system is directly attached, the system
637 must be able to accept packets as large as that link's MTU. Links
638 that have a configurable MTU, such as PPP links [<a href="./rfc1661" title="&quot;The Point-to-Point Protocol (PPP)&quot;">RFC1661</a>], should be
639 configured with an MTU of 600 octets or greater.
640
641 SIP systems are expected to implement Path MTU Discovery [<a href="./rfc1191" title="&quot;Path MTU discovery&quot;">RFC1191</a>],
642 in order to discover and take advantage of paths with MTU greater
643 than 576 octets. However, a minimal SIP implementation (e.g., in a
644 boot ROM) may simply restrict itself to sending packets no larger
645 than 576 octets, and omit implementation of Path MTU Discovery.
646
647 Path MTU Discovery requires support both in the SIP layer and in the
648 packetization layers. A system that supports Path MTU Discovery at
649 the SIP layer may serve packetization layers that are unable to adapt
650 to changes of the path MTU. Such packetization layers must limit
651 themselves to sending packets no longer than 576 octets, even when
652 sending to destinations that belong to the same subnet.
653
654 (Note: Unlike IPv4, it is unnecessary in SIP to set a "Don't
655 Fragment" flag in the packet header in order to perform Path MTU
656 Discovery; that is an implicit attribute of every SIP packet.
657 Also, those parts of the <a href="./rfc1191">RFC-1191</a> procedures that involve use of
658 a table of MTU "plateaus" do not apply to SIP, because the SIP
659 version of the "Datagram Too Big" message always identifies the
660 exact MTU to be used.)
661
662
663
664
665
666
667
668 <span class="grey">Deering &amp; Hinden Historic [Page 12]</span></pre>
669 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
670 <span class="grey"><a href="./rfc8507">RFC 8507</a> Simple IP (SIP) December 2018</span>
671
672
673 <span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Source Routing Header</span>
674
675 A Payload Type of &lt;TBD&gt; in the immediately preceding header indicates
676 the presence of this Source Routing header:
677
678 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
679 | Reserved |
680 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
681 | Num Addrs | Next Addr | Payload Type | Reserved |
682 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
683 | |
684 + Address[0] +
685 | |
686 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
687 | |
688 + Address[1] +
689 | |
690 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
691 . . .
692 . . .
693 . . .
694 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
695 | |
696 + Address[Num Addrs - 1] +
697 | |
698 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
699
700 Reserved Initialized to zero for transmission; ignored
701 on reception.
702
703 Num Addrs Number of addresses in the Source Routing
704 header.
705
706 Next Addr Index of next address to be processed;
707 initialized to 0 by the originating system.
708
709 Payload Type Identifies the type of payload following the
710 Source Routing header.
711
712
713
714
715
716
717
718
719
720
721
722
723
724 <span class="grey">Deering &amp; Hinden Historic [Page 13]</span></pre>
725 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
726 <span class="grey"><a href="./rfc8507">RFC 8507</a> Simple IP (SIP) December 2018</span>
727
728
729 A Source Routing header is not examined or processed until it reaches
730 the system identified in the Destination Address field of the SIP
731 header. In that system, dispatching on the Payload Type of the SIP
732 (or subsequent) header causes the Source Routing module to be
733 invoked, which performs the following algorithm:
734
735 o If Next Addr &lt; Num Addrs, swap the SIP Destination Address and
736 Address[Next Addr], increment Next Addr by one, and re-submit
737 the packet to the SIP module for forwarding to the next
738 destination.
739
740 o If Next Addr = Num Addrs, dispatch to the local protocol
741 module identified by the Payload Type field in the Source
742 Routing header.
743
744 o If Next Addr &gt; Num Addrs, send an ICMP Parameter Problem
745 message to the Source Address, pointing to the Num Addrs
746 field.
747
748 <span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Fragmentation Header</span>
749
750 A Payload Type of &lt;TBD&gt; in the immediately preceding header indicates
751 the presence of this Fragmentation header:
752
753 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
754 | Identification |
755 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
756 |0 0 M| Fragment Offset | Payload Type | Reserved |
757 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
758
759 Identification A value that changes on each packet sent with
760 the same Source Address, Destination Address,
761 and preceding Payload Type.
762
763 M flag 1 = more fragments; 0 = last fragment.
764
765 Fragment Offset The offset, in 8-octet chunks, of the
766 following payload, relative to the original,
767 unfragmented payload.
768
769 Payload Type Identifies the type of payload following the
770 Fragmentation header.
771
772 Reserved Initialized to zero for transmission; ignored
773 on reception.
774
775
776
777
778
779
780 <span class="grey">Deering &amp; Hinden Historic [Page 14]</span></pre>
781 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span>
782 <span class="grey"><a href="./rfc8507">RFC 8507</a> Simple IP (SIP) December 2018</span>
783
784
785 The Fragmentation header is NOT intended to support general,
786 SIP-layer fragmentation. In particular, SIP routers shall not
787 fragment a SIP packet that is too big for the MTU of its next hop,
788 except in the special cases described below; in the normal case, such
789 a packet results in an ICMP Packet Too Big message being sent back to
790 its source, for use by the source system's Path MTU Discovery
791 algorithm.
792
793 The special cases for which the Fragmentation header is intended are
794 the following:
795
796 o A SIP packet that is "tunneled", either by encapsulation
797 within another SIP packet or by insertion of a Source Routing
798 header en-route, may, after the addition of the extra header
799 fields, exceed the MTU of the tunnel's path; if the original
800 packet is 576 octets or less in length, the tunnel entry
801 system cannot respond to the source with a Packet Too Big
802 message, and therefore must insert a Fragmentation header and
803 fragment the packet to fit within the tunnel's MTU.
804
805 o An IPv4 fragment that is translated into a SIP packet, or an
806 unfragmented IPv4 packet that is translated into too long a
807 SIP packet to fit in the remaining path MTU, must include the
808 SIP Fragmentation header, so that it may be properly
809 reassembled at the destination SIP system.
810
811 Every SIP system must support SIP fragmentation and reassembly, since
812 any system may be configured to serve as a tunnel entry or exit
813 point, and any SIP system may be destination of IPv4 fragments. All
814 SIP systems must be capable of reassembling, from fragments, a SIP
815 packet of up to 1024 octets in length, including the SIP header; a
816 system may be capable of assembling packets longer than 1024 octets.
817
818 Routers do not examine or process Fragmentation headers of packets
819 that they forward; only at the destination system is the
820 Fragmentation header acted upon (i.e., reassembly performed), as a
821 result of dispatching on the Payload Type of the preceding header.
822
823 Fragmentation and reassembly employ the same algorithm as IPv4, with
824 the following exceptions:
825
826 o All headers up to and including the Fragmentation header are
827 repeated in each fragment; no headers or data following the
828 Fragmentation header are repeated in each fragment.
829
830 o the Identification field is increased to 32 bits, to decrease
831 the risk of wraparound of that field within the maximum packet
832 lifetime over very high-throughput paths.
833
834
835
836 <span class="grey">Deering &amp; Hinden Historic [Page 15]</span></pre>
837 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span>
838 <span class="grey"><a href="./rfc8507">RFC 8507</a> Simple IP (SIP) December 2018</span>
839
840
841 The similarity of the algorithm and the field layout to that of IPv4
842 enables existing IPv4 fragmentation and reassembly code and data
843 structures to be re-used with little modification.
844
845 <span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. Changes to Other Protocols</span>
846
847 Upgrading IPv4 to SIP entails changes to the associated control
848 protocols, ICMP and IGMP, as well as to the transport layer, above,
849 and possibly to the link-layer, below. This section identifies those
850 changes.
851
852 <span class="h3"><a class="selflink" id="section-9.1" href="#section-9.1">9.1</a>. Changes to ICMP</span>
853
854 SIP uses a subset of ICMP [[<a href="./rfc792" title="&quot;Internet Control Message Protocol&quot;">RFC792</a>], [<a href="./rfc950" title="&quot;Internet Standard Subnetting Procedure&quot;">RFC950</a>], [<a href="./rfc1122" title="&quot;Requirements for Internet Hosts - Communication Layers&quot;">RFC1122</a>], [<a href="./rfc1191" title="&quot;Path MTU discovery&quot;">RFC1191</a>],
855 [<a href="./rfc1256" title="&quot;ICMP Router Discovery Messages&quot;">RFC1256</a>]], with a few minor changes and some additions. The
856 presence of an ICMP header is indicated by a Payload Type of 1.
857
858 One change to all ICMP messages is that, when used with SIP, the ICMP
859 checksum includes a pseudo-header, like TCP and UDP, consisting of
860 the SIP Source Address, Destination Address, Payload Length, and
861 Payload Type (see <a href="#section-8.3">section 8.3</a>).
862
863 There are a set of ICMP messages called "error messages", each of
864 which, for IPv4, carries the IPv4 header plus 64 bits or more of data
865 from the packet that invoked the error message. When used with SIP,
866 ICMP error messages carry the first 256 octets of the invoking SIP
867 packet, or the entire invoking packet if it is shorter than
868 256 octets.
869
870 For most of the ICMP message types, the packets retain the same
871 format and semantics as with IPv4; however, some of the fields are
872 given new names to match SIP terminology.
873
874 The changes to specific message types are as follows:
875
876 Destination Unreachable
877
878 The following Codes have different names when used with SIP:
879
880 1 - destination address unreachable (IPv4 "host unreachable")
881 7 - destination address unknown (IPv4 "dest. host unknown")
882 2 - payload type unknown (IPv4 "protocol unreachable")
883 4 - packet too big (IPv4 "fragmentation needed and DF set")
884
885
886
887
888
889
890
891
892 <span class="grey">Deering &amp; Hinden Historic [Page 16]</span></pre>
893 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span>
894 <span class="grey"><a href="./rfc8507">RFC 8507</a> Simple IP (SIP) December 2018</span>
895
896
897 The following Codes retain the same names when used with SIP:
898
899 3 - port unreachable
900 5 - source route failed
901 8 - source host isolated
902 13 - communication administratively prohibited
903
904 The following Codes are not used with SIP:
905
906 0 - net unreachable
907 6 - destination network unknown
908 9 - comm. with dest. network administratively prohibited
909 10 - comm. with dest. host administratively prohibited
910 11 - network unreachable for type of service
911 12 - host unreachable for type of service
912
913 For "packet too big" messages (Code 4), the minimum legal value
914 in the Next-Hop MTU field [<a href="./rfc1191" title="&quot;Path MTU discovery&quot;">RFC1191</a>] is 576.
915
916
917 Time Exceeded
918
919 The name of Code 0 is changed to "hop limit exceeded in transit".
920
921
922 Parameter Problem
923
924 The Pointer field is extended to 16 bits and moved to the
925 low-order end of the second 32-bit word, as follows:
926
927 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
928 | Type | Code | Checksum |
929 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
930 | Reserved | Pointer |
931 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
932 | |
933 | first 256 octets of the invoking packet |
934 | |
935
936
937
938
939
940
941
942
943
944
945
946
947
948 <span class="grey">Deering &amp; Hinden Historic [Page 17]</span></pre>
949 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span>
950 <span class="grey"><a href="./rfc8507">RFC 8507</a> Simple IP (SIP) December 2018</span>
951
952
953 Redirect
954
955 Only Code 1 is used for SIP, meaning "redirect packets for the
956 destination address".
957
958 The Redirect header is modified for SIP, to accommodate the
959 64-bit address of the "preferred router" and to retain 64-bit
960 alignment, as follows:
961
962 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
963 | Type | Code | Checksum |
964 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
965 | Reserved |
966 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
967 | |
968 + Preferred Router +
969 | |
970 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
971 | |
972 | first 256 octets of the invoking packet |
973 | |
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
1001
1002
1003
1004 <span class="grey">Deering &amp; Hinden Historic [Page 18]</span></pre>
1005 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span>
1006 <span class="grey"><a href="./rfc8507">RFC 8507</a> Simple IP (SIP) December 2018</span>
1007
1008
1009 Router Advertisement
1010
1011 The format of the Router Advertisement message is changed to:
1012
1013 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1014 | Type | Code | Checksum |
1015 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1016 | Num Addrs |Addr Entry Size| Lifetime |
1017 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1018 | |
1019 + Router Address[0] +
1020 | |
1021 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1022 | Preference Level[0] |
1023 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1024 | Reserved[0] |
1025 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1026 | |
1027 + Router Address[1] +
1028 | |
1029 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1030 | Preference Level[1] |
1031 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1032 | Reserved[1] |
1033 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1034 | . |
1035 | . |
1036 | . |
1037
1038 The value in the Addr Entry Size field is 4, and all of the
1039 Reserved fields are initialized to zero by senders and ignored by
1040 receivers.
1041
1042
1043 Router Solicitation
1044
1045 No changes.
1046
1047
1048 Echo and Echo Reply
1049
1050 No changes.
1051
1052
1053
1054
1055
1056
1057
1058
1059
1060 <span class="grey">Deering &amp; Hinden Historic [Page 19]</span></pre>
1061 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span>
1062 <span class="grey"><a href="./rfc8507">RFC 8507</a> Simple IP (SIP) December 2018</span>
1063
1064
1065 The following ICMP message types are not used with SIP:
1066
1067 Source Quench
1068 Timestamp
1069 Timestamp Reply
1070 Information Request
1071 Information Reply
1072 Address Mask Request
1073 Address Mask Reply
1074
1075 <span class="h3"><a class="selflink" id="section-9.2" href="#section-9.2">9.2</a>. Changes to IGMP</span>
1076
1077 SIP uses the Internet Group Management Protocol, IGMP [<a href="./rfc1112" title="&quot;Host extensions for IP multicasting&quot;">RFC1112</a>]. The
1078 presence of an IGMP header is indicated by a Payload Type of 2.
1079
1080 When used with SIP, the IGMP checksum includes a pseudo-header, like
1081 TCP and UDP, consisting of the SIP Source Address, Destination
1082 Address, Payload Length, and Payload Type (see <a href="#section-8.3">section 8.3</a>).
1083
1084 The format of an IGMP Host Membership Query message becomes:
1085
1086 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1087 |Version| Type | Reserved | Checksum |
1088 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1089 | Reserved |
1090 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1091
1092 The format of an IGMP Host Membership Report message becomes:
1093
1094 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1095 |Version| Type | Reserved | Checksum |
1096 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1097 | Reserved |
1098 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1099 | |
1100 + Multicast Address +
1101 | |
1102 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1103
1104 For both message types, the Version number remains 1, and the
1105 Reserved fields are set to zero by senders and ignored by receivers.
1106
1107
1108
1109
1110
1111
1112
1113
1114
1115
1116 <span class="grey">Deering &amp; Hinden Historic [Page 20]</span></pre>
1117 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-21" ></span>
1118 <span class="grey"><a href="./rfc8507">RFC 8507</a> Simple IP (SIP) December 2018</span>
1119
1120
1121 <span class="h3"><a class="selflink" id="section-9.3" href="#section-9.3">9.3</a>. Changes to Transport Protocols</span>
1122
1123 The service interface to SIP has some differences from IPv4's service
1124 interface. Existing transport protocols that use IPv4 must be
1125 changed to operate over SIP's service interface. The differences
1126 from IPv4 are:
1127
1128 o Any addresses passed across the interface are 64 bits long,
1129 rather than 32 bits.
1130
1131 o The following IPv4 variables are not passed across the
1132 interface: Precedence, Type-of-Service, Identifier,
1133 Don't Fragment Flag
1134
1135 o SIP options have a different format than IPv4 options. (For
1136 SIP, "options" are all headers between, and not including, the
1137 SIP header and the transport header. The only IPv4 option
1138 currently specified for SIP is Loose Source Routing.
1139
1140 o ICMP error messages for SIP that are passed up to the
1141 transport layer carry the first 256 octets of the invoking SIP
1142 packet.
1143
1144 Transport protocols that use IPv4 addresses for their own purposes,
1145 such as identifying connection state or inclusion in a pseudo-header
1146 checksum, must be changed to use 64-bit SIP addresses for those
1147 purposes instead.
1148
1149 For SIP, the pseudo-header checksums of TCP, UDP, ICMP, and IGMP
1150 include the SIP Source Address, Destination Address, Payload Length,
1151 and Payload Type, with the following caveats:
1152
1153 o If the packet contains a Source Routing header, the
1154 destination address used in the pseudo-header checksum is that
1155 of the final destination.
1156
1157 o The Payload Length used in the pseudo-header checksum is the
1158 length of the transport-layer packet, including the transport
1159 header.
1160
1161 o The Payload Type used in the pseudo-header checksum is the
1162 Payload Type from the header immediately preceding the
1163 transport header.
1164
1165 o When added to the pseudo-header checksum, the Payload Type is
1166 treated as the left octet of a 16-bit word, with zeros in the
1167 the right octet, when viewed in IP standard octet order.
1168
1169
1170
1171
1172 <span class="grey">Deering &amp; Hinden Historic [Page 21]</span></pre>
1173 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-22" ></span>
1174 <span class="grey"><a href="./rfc8507">RFC 8507</a> Simple IP (SIP) December 2018</span>
1175
1176
1177 o If either of the two addresses used in the pseudo-header
1178 checksum has its high-order bit set to 1, only the low-order
1179 32-bits of that address shall be used in the sum. The
1180 high-order bit is used to indicate that the addressed system
1181 is an IPv4 system, and that the low-order 32-bits of the
1182 address contain that system's IPv4 address [<a href="#ref-IPAE" title="&quot;IP Address Encapsulation (IPAE): A Mechanism for Introducing a New IP&quot;">IPAE</a>].
1183
1184 The semantics of SIP service differ from IPv4 service in three ways
1185 that may affect some transport protocols:
1186
1187 (1) SIP does not enforce maximum packet lifetime. Any transport
1188 protocol that relies on IPv4 to limit packet lifetime must
1189 take this change into account, for example, by providing its
1190 own mechanisms for detecting and discarding obsolete packets.
1191
1192 (2) SIP does not checksum its own header fields. Any transport
1193 protocol that relies on IPv4 to assure the integrity of the
1194 source and destinations addresses, packet length, and
1195 transport protocol identifier must take this change into
1196 account. In particular, when used with SIP, the UDP checksum
1197 is mandatory, and ICMP and IGMP are changed to use a
1198 pseudo-header checksum.
1199
1200 (3) SIP does not (except in special cases) fragment packets that
1201 exceed the MTU of their delivery paths. Therefore, a
1202 transport protocol must not send packets longer than
1203 576 octets unless it implements Path MTU Discovery [<a href="./rfc1191" title="&quot;Path MTU discovery&quot;">RFC1191</a>]
1204 and is capable of adapting its transmitted packet size in
1205 response to changes of the path MTU.
1206
1207 <span class="h3"><a class="selflink" id="section-9.4" href="#section-9.4">9.4</a>. Changes to Link-Layer Protocols</span>
1208
1209 Link-layer media that have an MTU less than 576 must be enhanced
1210 with a link-specific fragmentation and reassembly mechanism, to
1211 support SIP.
1212
1213 For links on which ARP is used by IPv4, the identical ARP protocol is
1214 used for SIP. The low-order 32-bits of SIP addresses are used
1215 wherever IPv4 addresses would appear; since ARP is used only among
1216 systems on the same subnet, the high-order 32-bits of the SIP
1217 addresses may be inferred from the subnet prefix (assuming the subnet
1218 prefix is at least 32 bits long). [This is subject to change -- see
1219 <a href="#appendix-B">Appendix B</a>.]
1220
1221 <span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a>. Security Considerations</span>
1222
1223 &lt;to be done&gt;
1224
1225
1226
1227
1228 <span class="grey">Deering &amp; Hinden Historic [Page 22]</span></pre>
1229 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-23" ></span>
1230 <span class="grey"><a href="./rfc8507">RFC 8507</a> Simple IP (SIP) December 2018</span>
1231
1232
1233 <span class="h2"><a class="selflink" id="section-11" href="#section-11">11</a>. Acknowledgments</span>
1234
1235 The author acknowledges the many helpful suggestions and the words of
1236 encouragement from Dave Clark, Dave Crocker, Deborah Estrin, Bob
1237 Hinden, Christian Huitema, Van Jacobson, Jeff Mogul, Dave Nichols,
1238 Erik Nordmark, Dave Oran, Craig Partridge, Scott Shenker, Paul
1239 Tsuchiya, Lixia Zhang, the members of End-to-End Research Group and
1240 the IPAE Working Group, and the participants in the big-internet and
1241 sip mailing lists. He apologizes to those whose names he has not
1242 explicitly listed. [If you want to be on the list in the next draft,
1243 just let him know!]
1244
1245 Editor's note: Steve Deering was employed by the Xerox Palo Alto
1246 Research Center in Palo Alto, CA USA when this work was done.
1247
1248 <span class="h2"><a class="selflink" id="section-12" href="#section-12">12</a>. Informative References</span>
1249
1250 [<a id="ref-IPAE">IPAE</a>] Crocker, D. and R. Hinden, "IP Address Encapsulation
1251 (IPAE): A Mechanism for Introducing a New IP", Work in
1252 Progress, <a href="./draft-crocker-ip-encaps-01">draft-crocker-ip-encaps-01</a>, November 1992.
1253
1254 [<a id="ref-RFC791">RFC791</a>] Postel, J., "Internet Protocol", STD 5, <a href="./rfc791">RFC 791</a>,
1255 DOI 10.17487/RFC0791, September 1981,
1256 &lt;<a href="https://www.rfc-editor.org/info/rfc791">https://www.rfc-editor.org/info/rfc791</a>&gt;.
1257
1258 [<a id="ref-RFC792">RFC792</a>] Postel, J., "Internet Control Message Protocol", STD 5,
1259 <a href="./rfc792">RFC 792</a>, DOI 10.17487/RFC0792, September 1981,
1260 &lt;<a href="https://www.rfc-editor.org/info/rfc792">https://www.rfc-editor.org/info/rfc792</a>&gt;.
1261
1262 [<a id="ref-RFC950">RFC950</a>] Mogul, J. and J. Postel, "Internet Standard Subnetting
1263 Procedure", STD 5, <a href="./rfc950">RFC 950</a>, DOI 10.17487/RFC0950,
1264 August 1985, &lt;<a href="https://www.rfc-editor.org/info/rfc950">https://www.rfc-editor.org/info/rfc950</a>&gt;.
1265
1266 [<a id="ref-RFC951">RFC951</a>] Croft, W. and J. Gilmore, "Bootstrap Protocol", <a href="./rfc951">RFC 951</a>,
1267 DOI 10.17487/RFC0951, September 1985,
1268 &lt;<a href="https://www.rfc-editor.org/info/rfc951">https://www.rfc-editor.org/info/rfc951</a>&gt;.
1269
1270 [<a id="ref-RFC1112">RFC1112</a>] Deering, S., "Host extensions for IP multicasting", STD 5,
1271 <a href="./rfc1112">RFC 1112</a>, DOI 10.17487/RFC1112, August 1989,
1272 &lt;<a href="https://www.rfc-editor.org/info/rfc1112">https://www.rfc-editor.org/info/rfc1112</a>&gt;.
1273
1274 [<a id="ref-RFC1122">RFC1122</a>] Braden, R., Ed., "Requirements for Internet Hosts -
1275 Communication Layers", STD 3, <a href="./rfc1122">RFC 1122</a>,
1276 DOI 10.17487/RFC1122, October 1989,
1277 &lt;<a href="https://www.rfc-editor.org/info/rfc1122">https://www.rfc-editor.org/info/rfc1122</a>&gt;.
1278
1279
1280
1281
1282
1283
1284 <span class="grey">Deering &amp; Hinden Historic [Page 23]</span></pre>
1285 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-24" ></span>
1286 <span class="grey"><a href="./rfc8507">RFC 8507</a> Simple IP (SIP) December 2018</span>
1287
1288
1289 [<a id="ref-RFC1191">RFC1191</a>] Mogul, J. and S. Deering, "Path MTU discovery", <a href="./rfc1191">RFC 1191</a>,
1290 DOI 10.17487/RFC1191, November 1990,
1291 &lt;<a href="https://www.rfc-editor.org/info/rfc1191">https://www.rfc-editor.org/info/rfc1191</a>&gt;.
1292
1293 [<a id="ref-RFC1256">RFC1256</a>] Deering, S., Ed., "ICMP Router Discovery Messages",
1294 <a href="./rfc1256">RFC 1256</a>, DOI 10.17487/RFC1256, September 1991,
1295 &lt;<a href="https://www.rfc-editor.org/info/rfc1256">https://www.rfc-editor.org/info/rfc1256</a>&gt;.
1296
1297 [<a id="ref-RFC1661">RFC1661</a>] Simpson, W., Ed., "The Point-to-Point Protocol (PPP)",
1298 STD 51, <a href="./rfc1661">RFC 1661</a>, DOI 10.17487/RFC1661, July 1994,
1299 &lt;<a href="https://www.rfc-editor.org/info/rfc1661">https://www.rfc-editor.org/info/rfc1661</a>&gt;.
1300
1301 [<a id="ref-RFC1710">RFC1710</a>] Hinden, R., "Simple Internet Protocol Plus White Paper",
1302 <a href="./rfc1710">RFC 1710</a>, DOI 10.17487/RFC1710, October 1994,
1303 &lt;<a href="https://www.rfc-editor.org/info/rfc1710">https://www.rfc-editor.org/info/rfc1710</a>&gt;.
1304
1305 [<a id="ref-RFC1752">RFC1752</a>] Bradner, S. and A. Mankin, "The Recommendation for the IP
1306 Next Generation Protocol", <a href="./rfc1752">RFC 1752</a>, DOI 10.17487/RFC1752,
1307 January 1995, &lt;<a href="https://www.rfc-editor.org/info/rfc1752">https://www.rfc-editor.org/info/rfc1752</a>&gt;.
1308
1309 [<a id="ref-RFC1883">RFC1883</a>] Deering, S. and R. Hinden, "Internet Protocol, Version 6
1310 (IPv6) Specification", <a href="./rfc1883">RFC 1883</a>, DOI 10.17487/RFC1883,
1311 December 1995, &lt;<a href="https://www.rfc-editor.org/info/rfc1883">https://www.rfc-editor.org/info/rfc1883</a>&gt;.
1312
1313 [<a id="ref-RFC8200">RFC8200</a>] Deering, S. and R. Hinden, "Internet Protocol, Version 6
1314 (IPv6) Specification", STD 86, <a href="./rfc8200">RFC 8200</a>,
1315 DOI 10.17487/RFC8200, July 2017,
1316 &lt;<a href="https://www.rfc-editor.org/info/rfc8200">https://www.rfc-editor.org/info/rfc8200</a>&gt;.
1317
1318 [<a id="ref-SIP-ADDR">SIP-ADDR</a>] Deering, S., "Simple Internet Protocol (SIP) Addressing
1319 and Routing", Work in Progress, November 1992.
1320
1321
1322
1323
1324
1325
1326
1327
1328
1329
1330
1331
1332
1333
1334
1335
1336
1337
1338
1339
1340 <span class="grey">Deering &amp; Hinden Historic [Page 24]</span></pre>
1341 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-25" ></span>
1342 <span class="grey"><a href="./rfc8507">RFC 8507</a> Simple IP (SIP) December 2018</span>
1343
1344
1345 <span class="h2"><a class="selflink" id="appendix-A" href="#appendix-A">Appendix A</a>. SIP Design Rationale</span>
1346
1347 &lt;this section still to be done&gt;
1348
1349 Fields present in IPv4, but absent in SIP:
1350
1351 Header Length Not needed; SIP header length is fixed.
1352
1353 Precedence &amp;
1354 Type of Service Not used; transport-layer Port fields (or perhaps
1355 a to-be-defined value in the Reserved field of the
1356 SIP header) may be used for classifying packets at
1357 a granularity finer than host-to-host, as required
1358 for special handling.
1359
1360 Header Checksum Not used; transport pseudo-header checksum
1361 protects destinations from accepting corrupted
1362 packets.
1363
1364 Need to justify:
1365
1366 change of Total Length -&gt; Payload Length, excluding header
1367 change of Protocol -&gt; Payload Type
1368 change of Time to Live -&gt; Hop Limit
1369 movement of fragmentation fields out of fixed header
1370 bigger minimum MTU, and reliance on PMTU Discovery
1371
1372 <span class="h2"><a class="selflink" id="appendix-B" href="#appendix-B">Appendix B</a>. Future Directions</span>
1373
1374 SIP as specified above is a fully functional replacement for IPv4,
1375 with a number of improvements, particularly in the areas of
1376 scalability of routing and addressing, and performance. Some
1377 additional improvements are still under consideration:
1378
1379 o ARP may be modified to carry full 64-bit addresses, and to use
1380 link-layer multicast addresses, rather than broadcast
1381 addresses.
1382
1383 o The 28-bit Reserved field in the SIP header may be defined as
1384 a "Flow ID", or partitioned into a Type of Service field and a
1385 Flow ID field, for classifying packets deserving of special
1386 handling, e.g., non-default quality of service or real-time
1387 service. On the other hand, the transport-layer port fields
1388 may be adequate for performing any such classification. (One
1389 possibility would be simply to remove the port fields from TCP
1390 &amp; UDP and append them to the SIP header, as in XNS.)
1391
1392
1393
1394
1395
1396 <span class="grey">Deering &amp; Hinden Historic [Page 25]</span></pre>
1397 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-26" ></span>
1398 <span class="grey"><a href="./rfc8507">RFC 8507</a> Simple IP (SIP) December 2018</span>
1399
1400
1401 o A new ICMP "destination has moved" message may defined, for
1402 re-routing to mobile hosts or subnets, and to domains that
1403 have changed their address prefixes.
1404
1405 o An explicit Trace Route message or option may be defined; the
1406 current IPv4 traceroute scheme will work fine with SIP, but it
1407 does not work for multicast, for which it has become very
1408 apparent that management and debugging tools are needed.
1409
1410 o A new Host-to-Router protocol may be specified, encompassing
1411 the requirements of router discovery, black-hole detection,
1412 auto- configuration of subnet prefixes, "beaconing" for mobile
1413 hosts, and, possibly, address resolution. The OSI End System
1414 To Intermediate System Protocol may serve as a good model for
1415 such a protocol.
1416
1417 o The requirement that SIP addresses be strictly bound to
1418 interfaces may be relaxed, so that, for example, a system
1419 might have fewer addresses than interfaces. There is some
1420 experience with this approach in the current Internet, with
1421 the use of "unnumbered links" in routing protocols such as
1422 OSPF.
1423
1424 o Authentication and integrity-assurance mechanisms for all
1425 clients of SIP, including ICMP and IGMP, may be specified,
1426 possibly based on the Secure Data Network System (SNDS) SP-3
1427 or SP-4 protocol.
1428
1429 Authors' Addresses
1430
1431 Stephen E. Deering
1432 Retired
1433 Vancouver, British Columbia
1434 Canada
1435
1436
1437 Robert M. Hinden (editor)
1438 Check Point Software
1439 959 Skyway Road
1440 San Carlos, CA 94070
1441 USA
1442
1443 Email: [email protected]
1444
1445
1446
1447
1448
1449
1450
1451
1452 Deering &amp; Hinden Historic [Page 26]
1453 </pre>