| 1 |
<pre>Network Working Group D. Estrin |
| 2 |
Request for Comments: 1940 USC |
| 3 |
Category: Informational T. Li |
| 4 |
Y. Rekhter |
| 5 |
cisco Systems |
| 6 |
K. Varadhan |
| 7 |
D. Zappala |
| 8 |
USC |
| 9 |
May 1996 |
| 10 |
|
| 11 |
|
| 12 |
<span class="h1">Source Demand Routing:</span> |
| 13 |
<span class="h1">Packet Format and Forwarding Specification (Version 1).</span> |
| 14 |
|
| 15 |
Status of this Memo |
| 16 |
|
| 17 |
This memo provides information for the Internet community. This memo |
| 18 |
does not specify an Internet standard of any kind. Distribution of |
| 19 |
this memo is unlimited. |
| 20 |
|
| 21 |
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Overview</span> |
| 22 |
|
| 23 |
The purpose of SDRP is to support source-initiated selection of |
| 24 |
routes to complement the route selection provided by existing routing |
| 25 |
protocols for both inter-domain and intra-domain routes. This |
| 26 |
document refers to such source-initiated routes as "SDRP routes". |
| 27 |
This document describes the packet format and forwarding procedure |
| 28 |
for SDRP. It also describes procedures for ascertaining feasibility |
| 29 |
of SDRP routes. Other components not described here are routing |
| 30 |
information distribution and route computation. This portion of the |
| 31 |
protocol may initially be used with manually configured routes. The |
| 32 |
same packet format and processing will be usable with dynamic route |
| 33 |
information distribution and computation methods under development. |
| 34 |
|
| 35 |
The packet forwarding protocol specified here makes minimal |
| 36 |
assumptions about the distribution and acquisition of routing |
| 37 |
information needed to construct the SDRP routes. These minimal |
| 38 |
assumptions are believed to be sufficient for the existing Internet. |
| 39 |
Future components of the SDRP protocol will extend capabilities in |
| 40 |
this area and others in a largely backward-compatible manner. |
| 41 |
|
| 42 |
This version of the packet forwarding protocol sends all packets with |
| 43 |
the complete SDRP route in the SDRP header. Future versions will |
| 44 |
address route setup and other enhancements and optimizations. |
| 45 |
|
| 46 |
|
| 47 |
|
| 48 |
|
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
<span class="grey">Estrin, et al Informational [Page 1]</span></pre> |
| 53 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span> |
| 54 |
<span class="grey"><a href="./rfc1940">RFC 1940</a> SDRv1 May 1996</span> |
| 55 |
|
| 56 |
|
| 57 |
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Model of operations</span> |
| 58 |
|
| 59 |
An Internet can be viewed as a collection of routing domains |
| 60 |
interconnected by means of common subnetworks, and Border Routers |
| 61 |
(BRs) attached to these subnetworks. A routing domain itself may be |
| 62 |
composed of further subnetworks, routers interconnecting these |
| 63 |
subnetworks, and hosts. This document assumes that there is some |
| 64 |
type of routing present within the routing domain, but it does not |
| 65 |
assume that this intra-domain routing is coordinated or even |
| 66 |
consistent. |
| 67 |
|
| 68 |
For the purposes of this discussion, a BR belongs to only one domain. |
| 69 |
A pair of BRs, each belonging to a different domain, but attached to |
| 70 |
a common subnetwork, form an inter-domain connection. By definition, |
| 71 |
packets that traverse multiple domains must traverse BRs of these |
| 72 |
domains. Note that a single physical router may act as multiple BRs |
| 73 |
for the purposes of this model. |
| 74 |
|
| 75 |
A pair of domains is said to be adjacent if there is at least one |
| 76 |
pair of BRs, one in each domain, that form an inter-domain |
| 77 |
connection. |
| 78 |
|
| 79 |
Each domain has a globally unique identifier, called a Domain |
| 80 |
Identifier (DI). All the BRs within a domain need to know the DI |
| 81 |
assigned to the domain. Management of the DI space is outside the |
| 82 |
scope of this document. This document assumes that Autonomous System |
| 83 |
(AS) numbers are used as DIs. A domain path (or simply path) refers |
| 84 |
to a list of DIs such as might be taken from a BGP AS path [<a href="#ref-1" title="and Y. Rekhter">1</a>, <a href="#ref-2" title=""Application of the Border Gateway Protocol in the Internet"">2</a>, <a href="#ref-3" title=""A Border Gateway Protocol 4 (BGP-4)"">3</a>] |
| 85 |
or an IDRP RD path [<a href="#ref-4" title=""IDRP for IP"">4</a>]. We refer to a route as the combination of a |
| 86 |
network address and domain paths. The network addresses are |
| 87 |
represented by NLRI (Network Layer Reachability Information) as |
| 88 |
described in [<a href="#ref-3" title=""A Border Gateway Protocol 4 (BGP-4)"">3</a>]. |
| 89 |
|
| 90 |
This document assumes that the routing domains are congruent to the |
| 91 |
autonomous systems. Thus, within the content of this document, the |
| 92 |
terms autonomous system and routing domain can be used |
| 93 |
interchangeably. |
| 94 |
|
| 95 |
An application residing at a source host inside a domain, |
| 96 |
communicates with a destination host at another domain. An |
| 97 |
intermediate router in the path from the source host to the |
| 98 |
destination host may decide to forward the packet using SDRP. It can |
| 99 |
do this by encapsulating the entire IP packet from the source host in |
| 100 |
an SDRP packet. The router that does this encapsulation is called |
| 101 |
the "encapsulating router." |
| 102 |
|
| 103 |
|
| 104 |
|
| 105 |
|
| 106 |
|
| 107 |
|
| 108 |
<span class="grey">Estrin, et al Informational [Page 2]</span></pre> |
| 109 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span> |
| 110 |
<span class="grey"><a href="./rfc1940">RFC 1940</a> SDRv1 May 1996</span> |
| 111 |
|
| 112 |
|
| 113 |
2.1 SDRP routes |
| 114 |
|
| 115 |
A component in an SDRP route is either a DI (AS number) or an IP |
| 116 |
address. Thus, an SDRP route is defined as a sequence of domains |
| 117 |
and routers, syntactically expressed as a sequence of DIs and IP |
| 118 |
addresses. Thus an SDRP route is a collection of source routed |
| 119 |
hops. |
| 120 |
|
| 121 |
Each component of the SDRP route is called a "hop." The packet |
| 122 |
traverses each component of the SDRP route exactly once. When a |
| 123 |
router corresponding to one of the components of the SDRP route |
| 124 |
receives the packet from a router corresponding to the previous |
| 125 |
component of the SDRP route, the router will process the packet |
| 126 |
according to the SDRP forwarding rules in this packet. The next |
| 127 |
component of the SDRP route that this router will forward the |
| 128 |
packet to, is called the "next hop," with respect to this router |
| 129 |
and component of the SDRP route. |
| 130 |
|
| 131 |
An SDRP hop can either be a "strict" source routed hop, or a |
| 132 |
"loose" source routed hop. A strict source route hop is one in |
| 133 |
which, if the next hop specified is a DI, refers to an immediately |
| 134 |
adjacent domain, and the packet will be forwarded directly to a |
| 135 |
route within the domain; if the next hop specified is an IP |
| 136 |
address, refers to an immediately adjacent router on a common |
| 137 |
subnetwork. Any other kind of a source route hop is a loose |
| 138 |
source route hop. |
| 139 |
|
| 140 |
A route is a "strict source route" if the current hop being |
| 141 |
executed is processed as a strict source route hop. Likewise, a |
| 142 |
route is a "loose source route" if the current hop being executed |
| 143 |
is processed as a loose source route hop. |
| 144 |
|
| 145 |
It is assumed that each BR participates in the intra-domain |
| 146 |
routing protocol(s) (IGPs) of the domain to which the BR belongs. |
| 147 |
Thus, a BR may forward a packet to any other BR in its own domain |
| 148 |
using intra-domain routing procedures. Forwarding a packet |
| 149 |
between two BRs that form an inter-domain connection requires |
| 150 |
neither intra-domain nor the inter-domain routing procedures (an |
| 151 |
inter-domain connection is a common Layer 2 subnetwork). |
| 152 |
|
| 153 |
It is also assumed that all routers participate in the intra- |
| 154 |
domain routing protocol(s) (IGPs) of the domain to which they |
| 155 |
belong. |
| 156 |
|
| 157 |
While SDRP does not require that all domains have a common network |
| 158 |
layer protocol, all the BRs in the domains along a given SDRP |
| 159 |
route are required to support a common network layer. This |
| 160 |
document specifies SDRP operations when that common network layer |
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
<span class="grey">Estrin, et al Informational [Page 3]</span></pre> |
| 165 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span> |
| 166 |
<span class="grey"><a href="./rfc1940">RFC 1940</a> SDRv1 May 1996</span> |
| 167 |
|
| 168 |
|
| 169 |
protocol is IP ([<a href="#ref-5" title=""Internet Protocol - DARPA Internet Program Protocol Specification"">5</a>]). |
| 170 |
|
| 171 |
While this document requires all the BRs to support IP, the |
| 172 |
document does not preclude a BR from additionally supporting other |
| 173 |
network layer protocols as well (e.g., CLNP, IPX, AppleTalk). If |
| 174 |
a BR supports multiple network layers, then for the purposes of |
| 175 |
this model, the BR must maintain multiple Forwarding Information |
| 176 |
Bases (FIBs), one per network layer. |
| 177 |
|
| 178 |
2.2 SDRP encapsulation |
| 179 |
|
| 180 |
Forwarding an IP packet along an SDRP route is accomplished by |
| 181 |
encapsulating the entire packet in an SDRP packet. An SDRP packet |
| 182 |
consists of the SDRP header followed by the SDRP data. The SDRP |
| 183 |
header carries the SDRP route constructed by the domain that |
| 184 |
originated the SDRP packet. The SDRP data carries the original |
| 185 |
packet that the source domain decided to forward via SDRP. |
| 186 |
|
| 187 |
An SDRP packet is carried across domains as the data portion of an |
| 188 |
IP packet with protocol number 42. |
| 189 |
|
| 190 |
This document refers to the IP header of a packet that carries an |
| 191 |
SDRP packet as the delivery IP header (or just the delivery |
| 192 |
header). This document refers to the packet carried as SDRP data |
| 193 |
s the payload packet, and the IP header of the payload packet is |
| 194 |
the payload header. |
| 195 |
|
| 196 |
Thus, an SDRP Packet can be represented as follows: |
| 197 |
|
| 198 |
+-------------------+--------------+------------------- |
| 199 |
| Delivery header | SDRP header | SDRP data |
| 200 |
| (IP header) | | (Payload packet) |
| 201 |
+-------------------+--------------+-------------------- |
| 202 |
|
| 203 |
Each SDRP route may have an MTU associated with it. An MTU of an |
| 204 |
SDRP route is defined as the maximum length of the payload packet |
| 205 |
that can be carried without fragmentation of an SDRP packet. This |
| 206 |
means that the SDRP MTU as seen by the transport layer and |
| 207 |
applications above the transport layer is the actual link MTU less |
| 208 |
the length of the Delivery and SDRP headers. Procedures for MTU |
| 209 |
discovery are specified in <a href="#section-9">Section 9</a>. |
| 210 |
|
| 211 |
2.3 D-FIB |
| 212 |
|
| 213 |
It is assumed that a BR participates in either BGP or IDRP. A BR |
| 214 |
participating in SDRP augments its FIBs with a D-FIB that contains |
| 215 |
routes to domains. A route to a domain is a triplet <DI, Next- |
| 216 |
Hop, NLRI>, where DI depicts a destination domain, Next-Hop |
| 217 |
|
| 218 |
|
| 219 |
|
| 220 |
<span class="grey">Estrin, et al Informational [Page 4]</span></pre> |
| 221 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span> |
| 222 |
<span class="grey"><a href="./rfc1940">RFC 1940</a> SDRv1 May 1996</span> |
| 223 |
|
| 224 |
|
| 225 |
depicts the IP address of the next-hop BR, and NLRI depicts the |
| 226 |
set of reachable destinations within the destination domain. D- |
| 227 |
FIBs are constructed based on the information obtained from either |
| 228 |
BGP, IDRP, or configuration information. |
| 229 |
|
| 230 |
An SDRP packet is forwarded across multiple domains by utilizing |
| 231 |
the forwarding databases (both FIBs and D-FIBs) maintained by the |
| 232 |
BRs. |
| 233 |
|
| 234 |
The operational status of SDRP routes is monitored via passive |
| 235 |
(Error Reporting) and active (Route Probing) mechanisms. The Error |
| 236 |
Reporting mechanism provides the originator of the SDRP route with |
| 237 |
a failure notification. The Probing mechanism provides the |
| 238 |
originator of the SDRP route with confirmation of a route's |
| 239 |
feasibility. |
| 240 |
|
| 241 |
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. SDRP Packet format</span> |
| 242 |
|
| 243 |
The total length of an SDRP packet (header plus data) can be |
| 244 |
determined from the information carried in the delivery IP header. |
| 245 |
The length of the payload packet can be determined from the total |
| 246 |
length of an SDRP packet and the length of its SDRP Header. |
| 247 |
|
| 248 |
The following describes the format of an SDRP packet. |
| 249 |
|
| 250 |
0 1 2 3 |
| 251 |
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 |
| 252 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 253 |
| Ver |D|S|P| | Hop Count |SourceProtoType| Payload Type | |
| 254 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 255 |
| Source Route Identifier | |
| 256 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 257 |
| Target Router | |
| 258 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 259 |
| Prefix | |
| 260 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 261 |
| PrefixLength | Notification |SrcRouteLength | NextHopPtr | |
| 262 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 263 |
| Source Route ... |
| 264 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 265 |
| Payload .... |
| 266 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 267 |
|
| 268 |
Version and Flags (1 octet) |
| 269 |
|
| 270 |
The SDRP version number and control flags are coded in the first |
| 271 |
octet. Bit 0 is the most significant bit, bit 7 is the least |
| 272 |
significant bit. |
| 273 |
|
| 274 |
|
| 275 |
|
| 276 |
<span class="grey">Estrin, et al Informational [Page 5]</span></pre> |
| 277 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span> |
| 278 |
<span class="grey"><a href="./rfc1940">RFC 1940</a> SDRv1 May 1996</span> |
| 279 |
|
| 280 |
|
| 281 |
Version (bits 0 through 2) |
| 282 |
|
| 283 |
The first three bits contain the Version field indicating |
| 284 |
the version number of the protocol. The value of this field |
| 285 |
is set to 1. |
| 286 |
|
| 287 |
Flags (bits 3 through 7) |
| 288 |
|
| 289 |
Data packet/Control packet (bit 3) |
| 290 |
|
| 291 |
If the bit is set to 1, then the packet carries data. |
| 292 |
|
| 293 |
Otherwise, the packet carries control information. |
| 294 |
|
| 295 |
Loose/Strict Source Route (bit 4) |
| 296 |
|
| 297 |
The Loose/Strict Source Route indicator is used when |
| 298 |
making a forwarding decision (see <a href="#section-5.2">Section 5.2</a>). If this |
| 299 |
bit is set to 1, it indicates that the next hop is a |
| 300 |
Strict Source Route Hop. If this bit is set to 0, it |
| 301 |
indicates that the next hop is a Loose Source Route. |
| 302 |
|
| 303 |
Probe Indicator (bit 5) |
| 304 |
|
| 305 |
The Probe Indicator is used by the originator of the |
| 306 |
route to request verification of the route's feasibility |
| 307 |
(see Sections <a href="#section-4">4</a> and <a href="#section-7.1">7.1</a>). If this bit is set to 1, it |
| 308 |
indicates that the originator is probing the route. This |
| 309 |
bit should always be set to 0 for control packets. |
| 310 |
|
| 311 |
Hop Count (1 octet) |
| 312 |
|
| 313 |
The Hop Count field carries the maximum number of routers an |
| 314 |
SDRP data packet may traverse. It is decremented by 1 as an |
| 315 |
SDRP data packet traverses a router which forwards the packet |
| 316 |
using SDRP forwarding. Once the Hop Count field reaches the |
| 317 |
value of 0, the router should discard the data packet and |
| 318 |
generate a control packet (see <a href="#section-5.2.6">Section 5.2.6</a>). A router that |
| 319 |
receives a packet with a Hop Count value of 0 should discard |
| 320 |
the data packet, and generate a control packet (see <a href="#section-5.2.6">Section</a> |
| 321 |
<a href="#section-5.2.6">5.2.6</a>). |
| 322 |
|
| 323 |
Source Route Protocol Type (1 octet) |
| 324 |
|
| 325 |
The Source Route Protocol Type fields indicates the type of |
| 326 |
information that appears in the source route. The value 1 in |
| 327 |
this field indicates that the contents of the source route are |
| 328 |
as described in this document and indicates an Explicit Source |
| 329 |
|
| 330 |
|
| 331 |
|
| 332 |
<span class="grey">Estrin, et al Informational [Page 6]</span></pre> |
| 333 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span> |
| 334 |
<span class="grey"><a href="./rfc1940">RFC 1940</a> SDRv1 May 1996</span> |
| 335 |
|
| 336 |
|
| 337 |
Route. The value 2 in this field indicates a Route Setup. The |
| 338 |
syntax of the source route for this value is identical to a |
| 339 |
value of 1, but also has additional semantics which are defined |
| 340 |
in other documents. |
| 341 |
|
| 342 |
Payload Protocol Type (1 octet) |
| 343 |
|
| 344 |
The Payload Protocol Type field indicates the protocol type of |
| 345 |
the payload. If the payload is an IP datagram, then this field |
| 346 |
should contain the value 1. |
| 347 |
|
| 348 |
Note that this Payload Protocol Type is not the same as the IP |
| 349 |
protocol type[5,7]. |
| 350 |
|
| 351 |
Source Route Identifier (4 octets) |
| 352 |
|
| 353 |
The BR that originates the SDRP packet should insert a 32 bit |
| 354 |
value in this field which will serve as an identifier for the |
| 355 |
source route. This value needs to be unique only in the |
| 356 |
context of the originating BR. |
| 357 |
|
| 358 |
Target Router (4 octets) |
| 359 |
|
| 360 |
This field is meaningful only in control packets. |
| 361 |
|
| 362 |
The Target Router field contains one of the IP addresses of the |
| 363 |
router that originated the SDRP packet that triggered the |
| 364 |
control packet to be returned. |
| 365 |
|
| 366 |
Prefix (4 octets) |
| 367 |
|
| 368 |
The Prefix field contains an IP address prefix. Only the |
| 369 |
number of bits specified in the Prefix Length are significant. |
| 370 |
The Prefix field is used to prevent routing loops when using |
| 371 |
BGP or IDRP to route to the next AS in a loose source route |
| 372 |
(see <a href="#section-4">Section 4</a>). |
| 373 |
|
| 374 |
Prefix Length (1 octet) |
| 375 |
|
| 376 |
The Prefix Length field indicates the length in bits of the IP |
| 377 |
address prefix. A length of zero indicates a prefix that |
| 378 |
matches all IP addresses. |
| 379 |
|
| 380 |
Notification Code (1 octet) |
| 381 |
|
| 382 |
This field is only meaningful in control packets. In |
| 383 |
data packets, this field is transmitted as zero, and |
| 384 |
should be ignored on receipt. |
| 385 |
|
| 386 |
|
| 387 |
|
| 388 |
<span class="grey">Estrin, et al Informational [Page 7]</span></pre> |
| 389 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span> |
| 390 |
<span class="grey"><a href="./rfc1940">RFC 1940</a> SDRv1 May 1996</span> |
| 391 |
|
| 392 |
|
| 393 |
This document defines the following values for the |
| 394 |
Notification Code: |
| 395 |
|
| 396 |
1 - No Route Available |
| 397 |
|
| 398 |
2 - Strict Source Route Failed |
| 399 |
|
| 400 |
3 - Transit Policy Violation |
| 401 |
|
| 402 |
4 - Hop Count Exceeded |
| 403 |
|
| 404 |
5 - Probe Completed |
| 405 |
|
| 406 |
6 - Unimplemented SDRP version |
| 407 |
|
| 408 |
7 - Unimplemented Source Route Protocol Type |
| 409 |
|
| 410 |
8 - Setup Request Rejected |
| 411 |
|
| 412 |
Source Route Length (1 octet) |
| 413 |
|
| 414 |
The Source Route Length field indicates the length in 32 bit |
| 415 |
words of the domain level source route carried in the SDRP |
| 416 |
Header. |
| 417 |
|
| 418 |
Next Hop Pointer (1 octet) |
| 419 |
|
| 420 |
The Next Hop Pointer field indicates the offset of the high- |
| 421 |
order byte of the next hop along the route that the packet has |
| 422 |
to be forwarded. This offset is relative to the start of the |
| 423 |
Source Route field; so if the value of the Next Hop Pointer |
| 424 |
field equals the value of the Source Route Length field, then |
| 425 |
the entire source route has been completely traversed. All |
| 426 |
other source routes are said to be incompletely traversed. |
| 427 |
|
| 428 |
Source Route (variable) |
| 429 |
|
| 430 |
The components of the source route are syntactically IP |
| 431 |
addresses. |
| 432 |
|
| 433 |
An IP address from network 128.0.0.0 is used to encode a next |
| 434 |
hop that is a domain. The least significant two octets contain |
| 435 |
the DI, which is an Internet Autonomous System number. |
| 436 |
|
| 437 |
|
| 438 |
|
| 439 |
|
| 440 |
|
| 441 |
|
| 442 |
|
| 443 |
|
| 444 |
<span class="grey">Estrin, et al Informational [Page 8]</span></pre> |
| 445 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span> |
| 446 |
<span class="grey"><a href="./rfc1940">RFC 1940</a> SDRv1 May 1996</span> |
| 447 |
|
| 448 |
|
| 449 |
0 1 2 3 |
| 450 |
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 |
| 451 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 452 |
| 128 . 0 | D. I. | |
| 453 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 454 |
|
| 455 |
|
| 456 |
An IP address from the network 127.0.0.0 is used to encode |
| 457 |
characteristics of the source route. The least significant |
| 458 |
three octets are used as a Source Route Change field. |
| 459 |
|
| 460 |
0 1 2 3 |
| 461 |
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 |
| 462 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 463 |
| 127 | Source Route Change | |
| 464 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 465 |
|
| 466 |
Source Route Change (3 octets) |
| 467 |
|
| 468 |
Loose/Strict Source Route Change (bit 1) |
| 469 |
|
| 470 |
The Loose/Strict Source Route Change bit reflects a new |
| 471 |
value of the Loose/Strict Source Route bit in the SDRP |
| 472 |
header. The value of the Loose/Strict Source Route |
| 473 |
Change bit is copied into the Loose/Strict Source Route |
| 474 |
bit in the SDRP header when a Source Route Change field |
| 475 |
is encountered in processing an SDRP packet. |
| 476 |
|
| 477 |
The rest of the Source Route Change field is transmitted as |
| 478 |
zero, and should be ignored on receipt. |
| 479 |
|
| 480 |
Payload (variable) |
| 481 |
|
| 482 |
The Payload field carries the datagram originated by the end- |
| 483 |
system within the domain that constructed the SDRP packet. The |
| 484 |
Payload field forms the data portion of the SDRP packet. In a |
| 485 |
control packet this field may be empty or may carry the payload |
| 486 |
header of the packet that triggered the control message (see |
| 487 |
5.2.5). Note that there is no padding between the Source Route |
| 488 |
and the Payload, and that the Payload may start at any |
| 489 |
arbitrary octet boundary. |
| 490 |
|
| 491 |
|
| 492 |
|
| 493 |
|
| 494 |
|
| 495 |
|
| 496 |
|
| 497 |
|
| 498 |
|
| 499 |
|
| 500 |
<span class="grey">Estrin, et al Informational [Page 9]</span></pre> |
| 501 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span> |
| 502 |
<span class="grey"><a href="./rfc1940">RFC 1940</a> SDRv1 May 1996</span> |
| 503 |
|
| 504 |
|
| 505 |
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Originating SDRP Data packets</span> |
| 506 |
|
| 507 |
This document assumes that a router that originates SDRP packets is |
| 508 |
preconfigured with a set of SDRP routes. Procedures for constructing |
| 509 |
these routes are outside the scope of this document. SDRP packet |
| 510 |
forwarding may be deployed initially without additional routing |
| 511 |
protocol support. |
| 512 |
|
| 513 |
An application on a source host generates packets that must be |
| 514 |
delivered to a given destination. The packet traverses the Internet |
| 515 |
by following normal hop-by-hop routing information. An intermediate |
| 516 |
router in the path between the source host and the destination host |
| 517 |
may decide to forward some of these packets via SDRP. |
| 518 |
|
| 519 |
When this router receives an IP datagram, the router uses the |
| 520 |
information in the datagram and the local criteria to determine |
| 521 |
whether the datagram should be forwarded along a particular SDRP |
| 522 |
route. Associated with each set of criteria is a set of one or more |
| 523 |
SDRP routes that should be used to route matching packets. The exact |
| 524 |
nature of the criteria is a local matter. The only restrictions this |
| 525 |
document places on the applicability of SDRP routes is that an IP |
| 526 |
datagram that contains a strict source route should not be forwarded |
| 527 |
along an SDRP route, that SDRP encapsulation should never be applied |
| 528 |
to an SDRP packet, and that if SDRP is used with inter-domain routes, |
| 529 |
the destination domain must also run SDRP. |
| 530 |
|
| 531 |
If the router decides to forward a datagram along a particular SDRP |
| 532 |
route, the router constructs the SDRP packet by placing the original |
| 533 |
datagram into the Payload field of the SDRP packet and constructing |
| 534 |
the SDRP header based on the selected SDRP route. The Next Hop |
| 535 |
pointer is set to 0 (the first entry in the Source Route field of the |
| 536 |
SDRP packet). The value of the Time To Live field in the payload |
| 537 |
header should be copied into the Hop Count field of the SDRP header. |
| 538 |
|
| 539 |
Even if we assume that interior routing is loop free, it is possible, |
| 540 |
either due to the state of inter-domain routing or due to other SDRP |
| 541 |
routers, that a domain level source route that does not terminate |
| 542 |
with the intended destination domain may lead a packet into a routing |
| 543 |
loop. Originating SDRP routers that wish to insure that this does |
| 544 |
not occur should include a final domain level hop of the |
| 545 |
destination's domain, i.e. specify the SDRP route as <DI1, DI2, DI3> |
| 546 |
instead of <DI1, DI2>, if the destination host is in domain DI3. The |
| 547 |
means for determining the DI of the destination domain is outside of |
| 548 |
the scope of this document. |
| 549 |
|
| 550 |
Similarly, when using SDRP for interior routing, it is possible that |
| 551 |
the source route does not coincide with IGP routing. In this case, |
| 552 |
one means of preventing a loop is to specify the last hop router's IP |
| 553 |
|
| 554 |
|
| 555 |
|
| 556 |
<span class="grey">Estrin, et al Informational [Page 10]</span></pre> |
| 557 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span> |
| 558 |
<span class="grey"><a href="./rfc1940">RFC 1940</a> SDRv1 May 1996</span> |
| 559 |
|
| 560 |
|
| 561 |
address as the last address within the source route. The |
| 562 |
encapsulating router can do this by specifying the source route to |
| 563 |
reach destination host IP3 as <IP1, IP2, IP3> instead of <IP1, IP2>. |
| 564 |
|
| 565 |
The source address field in the delivery header should contain an IP |
| 566 |
address of the router. The value of the Don't Fragment flag of the |
| 567 |
delivery header is copied from the Don't Fragment flag of the payload |
| 568 |
header. The value of the Type Of Service field in the delivery |
| 569 |
header is copied from the Type Of Service field in the payload |
| 570 |
header. If the payload header contains an IP security option, that |
| 571 |
option is replicated as an option in the delivery header. All other |
| 572 |
IP options in the payload header must be ignored. |
| 573 |
|
| 574 |
If the SDRP route that is used is learned from IDRP, then the TOS |
| 575 |
corresponding to this route is copied into the TOS field in the |
| 576 |
delivery header. |
| 577 |
|
| 578 |
The resulting SDRP packet is then forwarded as described in <a href="#section-5.2.2">Section</a> |
| 579 |
<a href="#section-5.2.2">5.2.2</a>. |
| 580 |
|
| 581 |
If the encapsulating router decides to forward a datagram along a |
| 582 |
particular SDRP route that has an MTU smaller than the length of the |
| 583 |
datagram, then if the payload header has the Don't Fragment flag set |
| 584 |
to 1, the router should generate an ICMP Destination Unreachable |
| 585 |
message with a code meaning "fragmentation needed and DF set" in |
| 586 |
accordance with [<a href="#ref-6" title=""Path MTU Discovery"">6</a>]. The ICMP message must be sent to the original |
| 587 |
source host. The router should then discard the original datagram. |
| 588 |
|
| 589 |
If a router has learned an MTU for a particular SDRP route, either |
| 590 |
via ICMP messages or via configuration information, and it determines |
| 591 |
that an SDRP packet must be fragmented before transmission, then it |
| 592 |
first calculates the the effective MTU seen by the payload packet. |
| 593 |
If the effective MTU is greater than or equal to 512 bytes, the |
| 594 |
router SHOULD first fragment the payload packet using normal IP |
| 595 |
fragmentation. SDRP packets are then constructed for each fragment, |
| 596 |
as describe above. Otherwise, the router should first form the SDRP |
| 597 |
packet, and then fragment it. |
| 598 |
|
| 599 |
A router may use locally originated SDRP packets to verify the |
| 600 |
feasibility of its SDRP routes. To do this the router sets the value |
| 601 |
of the Probe Indicator field in the SDRP packet to 1. Receipt of an |
| 602 |
SDRP control packet by the originating router with the "Probe |
| 603 |
Completed" Notification Code (see <a href="#section-7.1">Section 7.1</a>) indicates feasibility |
| 604 |
of the SDRP route. Persistent lack of SDRP control packets with the |
| 605 |
"Probe Completed" Notification Code should be used as an indication |
| 606 |
that the associated SDRP route is not feasible. |
| 607 |
|
| 608 |
|
| 609 |
|
| 610 |
|
| 611 |
|
| 612 |
<span class="grey">Estrin, et al Informational [Page 11]</span></pre> |
| 613 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span> |
| 614 |
<span class="grey"><a href="./rfc1940">RFC 1940</a> SDRv1 May 1996</span> |
| 615 |
|
| 616 |
|
| 617 |
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Processing SDRP packets</span> |
| 618 |
|
| 619 |
We say that a router receives an SDRP packet if the destination |
| 620 |
address field in the delivery header of the packet arriving at the |
| 621 |
router contains one of the IP addresses of the router. |
| 622 |
|
| 623 |
When a router receives an SDRP packet, the router extracts the Source |
| 624 |
Route Protocol field from the SDRP header. |
| 625 |
|
| 626 |
<span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a> Supporting Transit Policies</span> |
| 627 |
|
| 628 |
A router may be able to verify that a packet that it is given to |
| 629 |
forward does not violate any of the transit policies that may exist, |
| 630 |
of the domain to which the router belongs. Specific verification |
| 631 |
mechanisms are a matter that is local to the router and are outside |
| 632 |
the scope of this document. |
| 633 |
|
| 634 |
The restriction on the verification mechanisms is that they may take |
| 635 |
into account only the contents of the SDRP header, the payload |
| 636 |
header, and transport protocol header of the payload packet. |
| 637 |
|
| 638 |
With SDRP a domain may enforce its transit policies by applying |
| 639 |
filters based on the information present in the IP Header. For |
| 640 |
example a router may initially carefully filter all SDRP traffic from |
| 641 |
all possible sources. A filter that allows certain SDRP traffic from |
| 642 |
selected sources to pass through the router could then be installed |
| 643 |
dynamically to pass similar types of traffic. Thus, by caching |
| 644 |
appropriate filtering information, a transit domain can efficiently |
| 645 |
support transit policies. Other mechanisms for supporting transit |
| 646 |
policy and implementation techniques are not precluded by this |
| 647 |
document. |
| 648 |
|
| 649 |
If the router detects that the SDRP packet violates a domain's |
| 650 |
transit policy it sends back an SDRP control packet to the |
| 651 |
encapsulating router and discards the violating packet. |
| 652 |
|
| 653 |
SDRP control packets are not subject to transit policies. |
| 654 |
|
| 655 |
If a router does not discard an SDRP packet due to a transit policy |
| 656 |
violation, then the router attempts to forward it as specified in |
| 657 |
<a href="#section-5.2">Section 5.2</a>. |
| 658 |
|
| 659 |
<span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a> Forwarding SDRP packets</span> |
| 660 |
|
| 661 |
Procedures for forwarding of an SDRP packet depend on |
| 662 |
|
| 663 |
a) whether the router has the routing information needed to |
| 664 |
forward the packet; |
| 665 |
|
| 666 |
|
| 667 |
|
| 668 |
<span class="grey">Estrin, et al Informational [Page 12]</span></pre> |
| 669 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span> |
| 670 |
<span class="grey"><a href="./rfc1940">RFC 1940</a> SDRv1 May 1996</span> |
| 671 |
|
| 672 |
|
| 673 |
b) whether the SDRP route has been completely traversed; |
| 674 |
c) whether the SDRP route is strict or loose, and |
| 675 |
d) whether the packet is a data or control packet. |
| 676 |
|
| 677 |
When forwarding an SDRP packet (either data or control) a router |
| 678 |
should not modify the following fields in the delivery header: |
| 679 |
|
| 680 |
a) Source Address |
| 681 |
b) Don't Fragment flag |
| 682 |
|
| 683 |
If the Source Route Protocol Type of a packet indicates a Route Setup |
| 684 |
and the router does not or cannot support setup, the router MAY send |
| 685 |
the encapsulating router a control packet with a Notification Code of |
| 686 |
Setup Request Rejected. It MAY then modify the data packet so that |
| 687 |
the Source Route Protocol Type is Explicit Source Route and the Probe |
| 688 |
Indicator bit is 0, then forwards the packet as described below. The |
| 689 |
router MAY send notification of a failed setup request only |
| 690 |
periodically. Alternately, a router MAY silently drop the Route |
| 691 |
Setup packet. |
| 692 |
|
| 693 |
<span class="h4"><a class="selflink" id="section-5.2.1" href="#section-5.2.1">5.2.1</a> Forwarding algorithm pseudo-code</span> |
| 694 |
|
| 695 |
The following pseudo-code gives an overview of the SDRP forwarding |
| 696 |
algorithm. Please consult the text below for more details. |
| 697 |
|
| 698 |
Let LOCAL_DI be the DI of the domain of the local system, let |
| 699 |
NEXT_HOP be the next hop in the source route if the source route has |
| 700 |
not been completely traversed, let NEXT_DI be the DI portion of |
| 701 |
NEXT_HOP if NEXT_HOP is from network 128.0.0.0, and let NEXT_ROUTER |
| 702 |
be the IP address of the next router if the packet is to be forwarded |
| 703 |
using SDRP. We say that NEXT_DI is adjacent if the local domain is |
| 704 |
adjacent to the domain that has NEXT_DI as its DI, and we say that |
| 705 |
NEXT_ROUTER is adjacent if it represents an IP address of a router |
| 706 |
that shares a link with the current router. Normal IP forwarding |
| 707 |
refers to forwarding that can be accomplished using FIBs constructed |
| 708 |
via BGP, IDRP or one or more IGPs. |
| 709 |
|
| 710 |
The pseudo code requires sending control messages in a number of |
| 711 |
places. All such control messages must be sent to the encapsulating |
| 712 |
router, which is indicated in the source address of the delivery |
| 713 |
header. Note too that all intermediate SDRP routers that process an |
| 714 |
SDRP packet must ensure that the source address of the delivery |
| 715 |
header is left untouched, since this source address is the address of |
| 716 |
the encapsulating router to which any control messages must be sent. |
| 717 |
|
| 718 |
|
| 719 |
|
| 720 |
|
| 721 |
|
| 722 |
|
| 723 |
|
| 724 |
<span class="grey">Estrin, et al Informational [Page 13]</span></pre> |
| 725 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span> |
| 726 |
<span class="grey"><a href="./rfc1940">RFC 1940</a> SDRv1 May 1996</span> |
| 727 |
|
| 728 |
|
| 729 |
if the packet is a control packet begin |
| 730 |
if the Target Router equals an address assigned to the |
| 731 |
local router begin |
| 732 |
remove the delivery header |
| 733 |
process information carried in the control packet |
| 734 |
return |
| 735 |
end if |
| 736 |
if the packet can be forwarded using normal IP forwarding begin |
| 737 |
set Next Hop Pointer to Source Route Length |
| 738 |
forward the packet using normal IP forwarding |
| 739 |
return |
| 740 |
end if |
| 741 |
end if |
| 742 |
|
| 743 |
if the version field is not 1 begin |
| 744 |
if the packet is a data packet begin |
| 745 |
generate a control packet with "Unimplemented SDRP version" |
| 746 |
end if |
| 747 |
discard the packet |
| 748 |
return |
| 749 |
end if |
| 750 |
|
| 751 |
if the source route protocol type is not 1 begin |
| 752 |
if the packet is a data packet begin |
| 753 |
generate a control packet with "Unimplemented source route |
| 754 |
protocol type" |
| 755 |
end if |
| 756 |
discard the packet |
| 757 |
return |
| 758 |
end if |
| 759 |
|
| 760 |
|
| 761 |
|
| 762 |
if the Hop Count field is greater than 0 begin |
| 763 |
decrement the Hop Count field |
| 764 |
end if |
| 765 |
if the Hop Count field is 0 begin |
| 766 |
if the packet is a data packet begin |
| 767 |
generate a control packet with "Hop Count Exceeded" |
| 768 |
end if |
| 769 |
discard the packet |
| 770 |
return |
| 771 |
end if |
| 772 |
|
| 773 |
|
| 774 |
if the packet is a data packet begin |
| 775 |
if the packet violates transit policy begin |
| 776 |
generate a control packet with "Transit Policy Violation" |
| 777 |
|
| 778 |
|
| 779 |
|
| 780 |
<span class="grey">Estrin, et al Informational [Page 14]</span></pre> |
| 781 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span> |
| 782 |
<span class="grey"><a href="./rfc1940">RFC 1940</a> SDRv1 May 1996</span> |
| 783 |
|
| 784 |
|
| 785 |
discard the data packet |
| 786 |
return |
| 787 |
end if |
| 788 |
end if |
| 789 |
|
| 790 |
set mode to NONE |
| 791 |
set advanced to FALSE |
| 792 |
if Next Hop Ptr does not equal Source Route Length begin |
| 793 |
set NEXT_HOP to the next hop in the source route |
| 794 |
while mode equals NONE begin |
| 795 |
if NEXT_HOP is from network 127.0.0.0 begin |
| 796 |
set the Loose/Strict Source Route bit equal to |
| 797 |
the Loose/Strict Source Route Change bit |
| 798 |
else if NEXT_HOP is from network 128.0.0.0 begin |
| 799 |
set NEXT_DI to the least significant two octets of NEXT_HOP |
| 800 |
if NEXT_DI is not equal to LOCAL_DI begin |
| 801 |
set mode to DOMAIN |
| 802 |
end if |
| 803 |
else if NEXT_HOP does not equal an address assigned to the |
| 804 |
local router begin |
| 805 |
set mode to LOCAL |
| 806 |
end if |
| 807 |
if mode equals NONE begin |
| 808 |
set advanced to TRUE |
| 809 |
increment the Next Hop Pointer field |
| 810 |
if Next Hop Pointer equals Source Route Length begin |
| 811 |
set mode to COMPLETE |
| 812 |
else |
| 813 |
set NEXT_HOP to the next hop in the source route |
| 814 |
end if |
| 815 |
end if |
| 816 |
end while |
| 817 |
end if |
| 818 |
|
| 819 |
|
| 820 |
if mode equals DOMAIN begin |
| 821 |
set route to NONE |
| 822 |
if the source route is loose begin |
| 823 |
if not advanced begin |
| 824 |
find the route, if any, based on Prefix and Prefix Length |
| 825 |
if the route is an aggregate formed at the local router begin |
| 826 |
set route to NONE |
| 827 |
end if |
| 828 |
end if |
| 829 |
if route equals NONE begin |
| 830 |
select a BGP or IDRP route, if any, with a path that includes |
| 831 |
NEXT_DI and is not an aggregate formed at the local router |
| 832 |
if route equals NONE begin |
| 833 |
|
| 834 |
|
| 835 |
|
| 836 |
<span class="grey">Estrin, et al Informational [Page 15]</span></pre> |
| 837 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span> |
| 838 |
<span class="grey"><a href="./rfc1940">RFC 1940</a> SDRv1 May 1996</span> |
| 839 |
|
| 840 |
|
| 841 |
if the packet is a data packet begin |
| 842 |
generate a control packet with "No Route Available" |
| 843 |
end if |
| 844 |
discard the packet |
| 845 |
return |
| 846 |
end if |
| 847 |
copy the NLRI from the route to the Prefix and Prefix Length |
| 848 |
end if |
| 849 |
if the route is an IDRP route begin |
| 850 |
set appropriate TOS in delivery header |
| 851 |
end if |
| 852 |
set NEXT_ROUTER from the route |
| 853 |
else |
| 854 |
set NEXT_ROUTER from the routing information for NEXT_DI |
| 855 |
using the D-FIB |
| 856 |
if route equals NONE begin |
| 857 |
if the packet is a data packet begin |
| 858 |
generate a control packet with "No Route Available" |
| 859 |
end if |
| 860 |
discard the packet |
| 861 |
return |
| 862 |
end if |
| 863 |
if NEXT_DI is not adjacent begin |
| 864 |
if the packet is a data packet begin |
| 865 |
generate a control packet with "Strict Source Route Failed" |
| 866 |
end if |
| 867 |
discard the packet |
| 868 |
return |
| 869 |
end if |
| 870 |
end if |
| 871 |
end if |
| 872 |
end if |
| 873 |
|
| 874 |
|
| 875 |
if mode equals LOCAL begin |
| 876 |
set NEXT_ROUTER equal to NEXT_HOP |
| 877 |
if the source route is strict and NEXT_ROUTER is not |
| 878 |
adjacent begin |
| 879 |
if the packet is a data packet begin |
| 880 |
generate a control packet with "Strict Source Route Failed" |
| 881 |
end if |
| 882 |
discard the packet |
| 883 |
return |
| 884 |
end if |
| 885 |
end if |
| 886 |
|
| 887 |
if mode equals LOCAL or mode equals DOMAIN begin |
| 888 |
set the destination address of the delivery header equal |
| 889 |
|
| 890 |
|
| 891 |
|
| 892 |
<span class="grey">Estrin, et al Informational [Page 16]</span></pre> |
| 893 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span> |
| 894 |
<span class="grey"><a href="./rfc1940">RFC 1940</a> SDRv1 May 1996</span> |
| 895 |
|
| 896 |
|
| 897 |
to NEXT_ROUTER |
| 898 |
checksum the delivery header |
| 899 |
route packet to NEXT_ROUTER using normal IP forwarding |
| 900 |
return |
| 901 |
end if |
| 902 |
|
| 903 |
if the packet is a control packet begin |
| 904 |
discard the packet |
| 905 |
end if |
| 906 |
remove the delivery header and the SDRP Header |
| 907 |
if there is no normal IP route to the payload destination begin |
| 908 |
generate a control packet with "No Route Available" |
| 909 |
discard the data packet |
| 910 |
return |
| 911 |
end if |
| 912 |
forward the payload using normal IP forwarding |
| 913 |
if the probe bit is set begin |
| 914 |
generate a control packet with "Probe Completed" |
| 915 |
end if |
| 916 |
|
| 917 |
<span class="h4"><a class="selflink" id="section-5.2.2" href="#section-5.2.2">5.2.2</a> Handling an SDRP control packet.</span> |
| 918 |
|
| 919 |
An SDRP control packet is indicated by 0 in the Data packet/Control |
| 920 |
packet bit in the Flags field in the SDRP Header. |
| 921 |
|
| 922 |
If the Target Router field of the received SDRP packet contains an IP |
| 923 |
address that is assigned to the router that received this SDRP |
| 924 |
packet, then the router should use the information carried in the |
| 925 |
Notification Code field, the Source Route Identifier field and the |
| 926 |
information carried in the Payload field to update the status of its |
| 927 |
SDRP routes. Details of such procedures are described in <a href="#section-7">Section 7</a>. |
| 928 |
|
| 929 |
Otherwise, the router checks whether it can forward the packet to the |
| 930 |
router specified in the Target Router field by using the routing |
| 931 |
information present in its local FIB. If forwarding is possible then |
| 932 |
the local system sets the destination address of the delivery header |
| 933 |
to the address specified in the Target Router field, and hands the |
| 934 |
packet off for normal IP forwarding. If normal IP forwarding is |
| 935 |
impossible then the packet may be forwarded in the same manner as an |
| 936 |
SDRP data packet (described below) but with the following exceptions. |
| 937 |
|
| 938 |
- Control packets are not subject to transit policies. |
| 939 |
- In no case should a control packet be generated in response to |
| 940 |
an error caused by a control packet. |
| 941 |
- If the source route is completely traversed and the packet still |
| 942 |
cannot be forwarded via normal IP routing, the packet should be |
| 943 |
silently dropped. |
| 944 |
|
| 945 |
|
| 946 |
|
| 947 |
|
| 948 |
<span class="grey">Estrin, et al Informational [Page 17]</span></pre> |
| 949 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span> |
| 950 |
<span class="grey"><a href="./rfc1940">RFC 1940</a> SDRv1 May 1996</span> |
| 951 |
|
| 952 |
|
| 953 |
<span class="h4"><a class="selflink" id="section-5.2.3" href="#section-5.2.3">5.2.3</a> Handling an SDRP data packet.</span> |
| 954 |
|
| 955 |
An SDRP data packet is indicated by a one in the Data packet/Control |
| 956 |
packet bit in the Flags field in the SDRP Header. |
| 957 |
|
| 958 |
An SDRP data packet is forwarded by sending the packet along the |
| 959 |
source route in the SDRP Header. When the source route is completely |
| 960 |
traversed and the packet has reached the destination domain, the |
| 961 |
payload may be removed from the data packet and forwarded normally. |
| 962 |
Further details are described below. |
| 963 |
|
| 964 |
<span class="h4"><a class="selflink" id="section-5.2.4" href="#section-5.2.4">5.2.4</a> Checking the SDRP version number</span> |
| 965 |
|
| 966 |
An SDRP packet that has a version number other than 1 should be |
| 967 |
discarded. If the SDRP packet was a data packet, then a control |
| 968 |
packet with the Notification Code "Unimplemented SDRP version" should |
| 969 |
be generated as specified in <a href="#section-6">section 6</a>. |
| 970 |
|
| 971 |
<span class="h4"><a class="selflink" id="section-5.2.5" href="#section-5.2.5">5.2.5</a> Checking the Source Route Protocol Type</span> |
| 972 |
|
| 973 |
This document describes Source Route Protocol Type 1. An SDRP router |
| 974 |
may support multiple Source Route Protocol Types; however an SDRP |
| 975 |
router is NOT required to support all defined Source Route Types. |
| 976 |
Any packet that has a Source Route Protocol Type which is not |
| 977 |
supported should be discarded. If the SDRP packet was a data packet, |
| 978 |
then a control packet with the Notification Code "Unimplemented |
| 979 |
Source Route Protocol Type" should be generated as specified in |
| 980 |
<a href="#section-6">section 6</a>. |
| 981 |
|
| 982 |
<span class="h4"><a class="selflink" id="section-5.2.6" href="#section-5.2.6">5.2.6</a> Decrementing and checking Hop Count</span> |
| 983 |
|
| 984 |
If an SDRP packet is to be forwarded and the Hop Count field is non- |
| 985 |
zero, the Hop Count field should be decremented. If the resulting |
| 986 |
value is zero and the packet was a data packet, then a control packet |
| 987 |
with the Notification Code "Hop Count Exceeded" should be generated |
| 988 |
and sent to the encapsulating router as specified in <a href="#section-6">section 6</a>, and |
| 989 |
the packet should be discarded. If the resulting value is zero and |
| 990 |
the packet was a control packet, the packet should be discarded. The |
| 991 |
payload of the control packet should carry the payload header |
| 992 |
followed by 64 bits of the payload data of the data packet. |
| 993 |
|
| 994 |
<span class="h4"><a class="selflink" id="section-5.2.7" href="#section-5.2.7">5.2.7</a> Upholding transit policies</span> |
| 995 |
|
| 996 |
It is not a goal of SDRP to create a security routing system. |
| 997 |
Therefore, we need to qualify our use of the term "upholding transit |
| 998 |
policy". It is assumed that transit policies have the nature of a |
| 999 |
"gentleperson's agreement", and are upheld by all the participants. |
| 1000 |
In other words, it is assumed that there will be no malicious |
| 1001 |
|
| 1002 |
|
| 1003 |
|
| 1004 |
<span class="grey">Estrin, et al Informational [Page 18]</span></pre> |
| 1005 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span> |
| 1006 |
<span class="grey"><a href="./rfc1940">RFC 1940</a> SDRv1 May 1996</span> |
| 1007 |
|
| 1008 |
|
| 1009 |
attempts to violate transit policies and that parties will rely on |
| 1010 |
auditing and post facto detection of violations. When a security |
| 1011 |
architecture is developed for IP or other network protocols then it |
| 1012 |
may be applied to increase the assurance of transit policy |
| 1013 |
enforcement. These issues are beyond the scope of this document. |
| 1014 |
|
| 1015 |
A router may examine any data packet to verify if it complies with |
| 1016 |
local transit policies, as described in <a href="#section-5.1">section 5.1</a>. If the |
| 1017 |
verification fails, the router generates a control packet. If the |
| 1018 |
verification referred to only the contents of the SDRP header, then |
| 1019 |
the payload field of the control packet should be empty. If the |
| 1020 |
verification referred to both the contents of the SDRP header and the |
| 1021 |
payload header, then the payload field of the control packet should |
| 1022 |
carry the payload header. If the verification referred to the |
| 1023 |
transport protocol header, then the payload field of the control |
| 1024 |
packet should carry the payload header and the transport header. |
| 1025 |
|
| 1026 |
The Notification Code field of the SDRP header in the control packet |
| 1027 |
is set to Transit Policy Violation. The procedures for constructing |
| 1028 |
the rest of the SDRP Header of the control packet are specified in |
| 1029 |
<a href="#section-6">Section 6</a>. |
| 1030 |
|
| 1031 |
<span class="h4"><a class="selflink" id="section-5.2.8" href="#section-5.2.8">5.2.8</a> Partially traversed source routes</span> |
| 1032 |
|
| 1033 |
If a router receives an SDRP packet with a partially traversed source |
| 1034 |
route, it extracts the next hop of the source route from the Source |
| 1035 |
Route field. The router locates the high-order byte of the |
| 1036 |
appropriate hop by using the Next Hop Pointer field as a 32 bit word |
| 1037 |
offset relative to the start of the Source Route field. The next hop |
| 1038 |
is always four octets long. The following procedure is used to |
| 1039 |
interpret the next hop. |
| 1040 |
|
| 1041 |
Syntactically, each element in the source route appears as an IP |
| 1042 |
address. There are three encodings for the next hop: |
| 1043 |
|
| 1044 |
a) The next hop is an address in network 127.0.0.0. In this case, |
| 1045 |
the Loose/Strict Source Route field is set equal to the Loose/Strict |
| 1046 |
Source Route Change bit. Then the Next Hop Pointer is incremented, |
| 1047 |
the next hop is read from the Source Route field, and these three |
| 1048 |
cases are examined again. |
| 1049 |
|
| 1050 |
b) The next hop is an address in network 128.0.0.0. In this case, |
| 1051 |
the DI of the next domain is extracted from the least significant two |
| 1052 |
octets of the next hop. If the extracted DI is the same as the DI of |
| 1053 |
the local domain, then the Next Hop Pointer is incremented, the next |
| 1054 |
hop is read from the Source Route field, and these three cases are |
| 1055 |
examined again. Otherwise, if the extracted DI is different from the |
| 1056 |
DI of the local domain, the next hop is the extracted DI, and the |
| 1057 |
|
| 1058 |
|
| 1059 |
|
| 1060 |
<span class="grey">Estrin, et al Informational [Page 19]</span></pre> |
| 1061 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span> |
| 1062 |
<span class="grey"><a href="./rfc1940">RFC 1940</a> SDRv1 May 1996</span> |
| 1063 |
|
| 1064 |
|
| 1065 |
forwarding process may proceed. |
| 1066 |
|
| 1067 |
c) The next hop is any other IP address. If the next hop is equal to |
| 1068 |
any IP address assigned to the local router, the Next Hop Pointer is |
| 1069 |
incremented, the next hop is read from the Source Route field, and |
| 1070 |
these three cases examined again. Otherwise, the next hop is the IP |
| 1071 |
address of the next router in the source route and the forwarding |
| 1072 |
process may proceed. |
| 1073 |
|
| 1074 |
The above procedure for interpreting the next hop in the source route |
| 1075 |
finishes when the next hop is either a router other than the local |
| 1076 |
router or an encoded DI that is not the local DI or a completed |
| 1077 |
source route. |
| 1078 |
|
| 1079 |
If upon termination of this procedure the source route is completely |
| 1080 |
traversed, see <a href="#section-5.2.9">section 5.2.9</a>. |
| 1081 |
|
| 1082 |
<span class="h5"><a class="selflink" id="section-5.2.8.1" href="#section-5.2.8.1">5.2.8.1</a> Finding a route to the next hop</span> |
| 1083 |
|
| 1084 |
If the next hop is not a DI, then the destination address in the |
| 1085 |
delivery header is replaced by the next hop address and the resulting |
| 1086 |
packet can then be forwarded using normal IP forwarding. Otherwise, |
| 1087 |
a DI was extracted from the next hop in the source route, and the |
| 1088 |
following procedure is used to find a route to the next domain. |
| 1089 |
|
| 1090 |
Given the DI of the next domain, the router next consults its D-FIB. |
| 1091 |
If no entry exists in the D-FIB for the next domain, then the packet |
| 1092 |
should be discarded. If the packet was a data packet, a control |
| 1093 |
message with Notification Code "No Route Available" should be |
| 1094 |
generated as specified in <a href="#section-6">Section 6</a>. No other actions are necessary. |
| 1095 |
|
| 1096 |
If there is a D-FIB entry, the router next examines the SDRP header |
| 1097 |
to determine if the packet specified a strict source route. If so, |
| 1098 |
and the next domain is not adjacent to the local domain, then a |
| 1099 |
control packet with the Notification Code "Strict Source Route |
| 1100 |
Failed" should be generated, as specified in <a href="#section-6">section 6</a>, and the |
| 1101 |
original packet should be discarded. No other actions are necessary. |
| 1102 |
|
| 1103 |
If source route is loose, then BGP or IDRP information must be used |
| 1104 |
to insure that there is no loop in reaching the next hop. If the |
| 1105 |
Next Hop Pointer was incremented when determining the next hop, then |
| 1106 |
the router must select a BGP or IDRP route with a path that includes |
| 1107 |
the extracted DI, and the NLRI for this route is copied into the |
| 1108 |
Prefix Length and Prefix fields. |
| 1109 |
|
| 1110 |
Otherwise, the Next Hop Pointer was not incremented, and the router |
| 1111 |
should use the information carried in the Prefix and Prefix Length as |
| 1112 |
an index into its BGP or IDRP routing table. If it finds a matching |
| 1113 |
|
| 1114 |
|
| 1115 |
|
| 1116 |
<span class="grey">Estrin, et al Informational [Page 20]</span></pre> |
| 1117 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-21" ></span> |
| 1118 |
<span class="grey"><a href="./rfc1940">RFC 1940</a> SDRv1 May 1996</span> |
| 1119 |
|
| 1120 |
|
| 1121 |
route then it must select the corresponding D-FIB entry. If the |
| 1122 |
route was formed locally by aggregation, then the router must consult |
| 1123 |
its D-FIB and select any route with a path that includes the |
| 1124 |
extracted DI. The NLRI for this route should be copied into the |
| 1125 |
Prefix Length and Prefix fields. |
| 1126 |
|
| 1127 |
In either case, the D-FIB entry includes the IP address of the next |
| 1128 |
SDRP-speaking router to which the SDRP packet should be routed. The |
| 1129 |
destination address in the delivery header is replaced by this |
| 1130 |
address. The resulting packet can then be forwarded using normal IP |
| 1131 |
forwarding. |
| 1132 |
|
| 1133 |
<span class="h5"><a class="selflink" id="section-5.2.8.2" href="#section-5.2.8.2">5.2.8.2</a> Last Hop Optimization</span> |
| 1134 |
|
| 1135 |
A small optimization can be performed if there is only a single DI or |
| 1136 |
IP address in the source route that has not been traversed. |
| 1137 |
|
| 1138 |
In this case, if the next hop in the SDRP route is a DI, that DI is |
| 1139 |
adjacent to the router processing this packet, the route has a route |
| 1140 |
to the destination address in the payload header in its FIB, and this |
| 1141 |
FIB route passes through the adjacent domain, then the source route |
| 1142 |
may be considered completely traversed and processing may proceed as |
| 1143 |
in <a href="#section-5.2.9">section 5.2.9</a>. |
| 1144 |
|
| 1145 |
If the next hop in the SDRP route is an IP address, that IP address |
| 1146 |
is adjacent to the router processing this packet, the router has a |
| 1147 |
route to the destination address in the payload header in its FIB, |
| 1148 |
and this FIB route passes through the adjacent IP address, then the |
| 1149 |
source route may be considered completely traversed and processing |
| 1150 |
may proceed as in <a href="#section-5.2.9">section 5.2.9</a>. |
| 1151 |
|
| 1152 |
Since the last hop optimization may only be done if the last hop is |
| 1153 |
directly adjacent, and reachable, it is irrelevant whether the SDRP |
| 1154 |
route specifies that this is a strict source route or a loose source |
| 1155 |
route hop. |
| 1156 |
|
| 1157 |
<span class="h4"><a class="selflink" id="section-5.2.9" href="#section-5.2.9">5.2.9</a> Completely Traversed source routes</span> |
| 1158 |
|
| 1159 |
If the SDRP packet received by a router with a completely-traversed |
| 1160 |
source route is a control packet and if the Target Router field |
| 1161 |
carries an IP address assigned to the router, then the packet should |
| 1162 |
be processed as specified in <a href="#section-7">Section 7</a>. Otherwise, if the SDRP |
| 1163 |
packet is a control packet, and the packet cannot be forwarded via |
| 1164 |
either SDRP or normal IP forwarding, the packet should be silently |
| 1165 |
dropped. |
| 1166 |
|
| 1167 |
The Hop Count field has already been decremented when processing the |
| 1168 |
SDRP header. The Hop Count field should now be copied from the SDRP |
| 1169 |
|
| 1170 |
|
| 1171 |
|
| 1172 |
<span class="grey">Estrin, et al Informational [Page 21]</span></pre> |
| 1173 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-22" ></span> |
| 1174 |
<span class="grey"><a href="./rfc1940">RFC 1940</a> SDRv1 May 1996</span> |
| 1175 |
|
| 1176 |
|
| 1177 |
header into the IP TTL field in the payload header. The resulting |
| 1178 |
payload packet is then forwarded using normal IP forwarding. If |
| 1179 |
there is no FIB entry for the destination, then the packet should be |
| 1180 |
discarded and a control message with Notification Code "No Route |
| 1181 |
Available" should be generated as specified in <a href="#section-6">Section 6</a>. If the |
| 1182 |
packet can be forwarded and if the Probe Indication bit is set to one |
| 1183 |
in the SDRP header, then a control message with Notification Code |
| 1184 |
"Probe Completed" should be generated as specified in <a href="#section-6">section 6</a>. If a |
| 1185 |
control packet is generated, then it must be sent to the |
| 1186 |
encapsulating router. The payload of the control packet should carry |
| 1187 |
the first 64 bits of the SDRP header and the payload header. |
| 1188 |
|
| 1189 |
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Originating SDRP control packets</span> |
| 1190 |
|
| 1191 |
A router sends a control packet in response to either error |
| 1192 |
conditions, or to successful completion of a probe request (indicated |
| 1193 |
via Probe Indication in the Flags field). |
| 1194 |
|
| 1195 |
The Data Packet/Control Packet field is set to indicate Control |
| 1196 |
Packet. The following fields are copied from the SDRP header of the |
| 1197 |
Data packet that caused the generation of the Control packet: |
| 1198 |
|
| 1199 |
- Loose/Strict Source Route |
| 1200 |
- Source Route Protocol Type |
| 1201 |
- Source Route Identifier |
| 1202 |
- Source Route Length field |
| 1203 |
- Payload Protocol Type |
| 1204 |
|
| 1205 |
A Control packet should not carry a Probe Indication field. |
| 1206 |
|
| 1207 |
A router should never originate a Control packet as the result of an |
| 1208 |
error caused by a control packet. |
| 1209 |
|
| 1210 |
The Target Router is copied from the source IP address of the |
| 1211 |
delivery header of the SDRP Data packet. This causes the control |
| 1212 |
packet to be returned to the encapsulating router. |
| 1213 |
|
| 1214 |
The router generating a control packet checks its FIB for a route to |
| 1215 |
the destination depicted by the Target Router field. If such a route |
| 1216 |
is present, then the value of the Destination Address field in the |
| 1217 |
delivery header is set to the Target Router, the Source Address field |
| 1218 |
in the delivery header is set to the IP address of one of the |
| 1219 |
interfaces attached to the local system, and the packet is forwarded |
| 1220 |
via normal IP forwarding. |
| 1221 |
|
| 1222 |
If the FIB does not have a route to the destination depicted by the |
| 1223 |
Target Router field, the local system constructs the Source Route |
| 1224 |
field of the Control packet by reversing the SDRP route carried in |
| 1225 |
|
| 1226 |
|
| 1227 |
|
| 1228 |
<span class="grey">Estrin, et al Informational [Page 22]</span></pre> |
| 1229 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-23" ></span> |
| 1230 |
<span class="grey"><a href="./rfc1940">RFC 1940</a> SDRv1 May 1996</span> |
| 1231 |
|
| 1232 |
|
| 1233 |
the Source Route field of the Data packet, sets the value of the Next |
| 1234 |
Hop Pointer to the value of the Source Route Length field minus the |
| 1235 |
value of the Next Hop Pointer field of the SDRP data packet that |
| 1236 |
caused generation of the Control Packet. All Loose/Strict Source |
| 1237 |
Route change bits in the new source route should be set to 0 (loose |
| 1238 |
source route). |
| 1239 |
|
| 1240 |
The contents of the Payload field depends on the reason for |
| 1241 |
generating a control packet. |
| 1242 |
|
| 1243 |
The resulting packet is then handled via SDRP Forwarding procedures |
| 1244 |
described in <a href="#section-5.2">Section 5.2</a>. |
| 1245 |
|
| 1246 |
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Processing control information</span> |
| 1247 |
|
| 1248 |
A router participating in SDRP may receive control information in two |
| 1249 |
forms, SDRP control packets from other routers and ICMP messages from |
| 1250 |
routers that do not participate in SDRP, but are involved in |
| 1251 |
forwarding SDRP packets. |
| 1252 |
|
| 1253 |
<span class="h3"><a class="selflink" id="section-7.1" href="#section-7.1">7.1</a> Processing SDRP control packets</span> |
| 1254 |
|
| 1255 |
Most control packets carry information about some SDRP routes used by |
| 1256 |
the router. To correlate information carried in the SDRP control |
| 1257 |
packet with the SDRP routes used by the router, the router uses |
| 1258 |
information carried in the SDRP header of the control packet, and |
| 1259 |
optionally in the SDRP payload of the control packet (if present). |
| 1260 |
|
| 1261 |
In general, receipt of any SDRP control packet that carries one of |
| 1262 |
the following Notification codes |
| 1263 |
|
| 1264 |
- No Route Available |
| 1265 |
|
| 1266 |
- Strict Source Route Failed |
| 1267 |
|
| 1268 |
- Unimplemented SDRP Version |
| 1269 |
|
| 1270 |
- Unimplemented Source Route Probe Type |
| 1271 |
|
| 1272 |
indicates that the corresponding SDRP route is presently not |
| 1273 |
feasible, and thus should not be used for packet forwarding. The |
| 1274 |
router must mark the affected routes as not feasible, and may use |
| 1275 |
alternate routes if available. |
| 1276 |
|
| 1277 |
The router may at some later point attempt to use an SDRP route that |
| 1278 |
was marked as infeasible. The criteria used for retrying routes is |
| 1279 |
outside the scope of this document and a subject of further study. |
| 1280 |
It need not be standardizes and can be a matter of local control. |
| 1281 |
|
| 1282 |
|
| 1283 |
|
| 1284 |
<span class="grey">Estrin, et al Informational [Page 23]</span></pre> |
| 1285 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-24" ></span> |
| 1286 |
<span class="grey"><a href="./rfc1940">RFC 1940</a> SDRv1 May 1996</span> |
| 1287 |
|
| 1288 |
|
| 1289 |
Receipt of an SDRP control packet that carries "Probe Completed" |
| 1290 |
Notification code indicates that the corresponding SDRP route is |
| 1291 |
feasible. |
| 1292 |
|
| 1293 |
Receipt of an SDRP control packet that carries the "Transit Policy |
| 1294 |
Violation" Notification Code shall be interpreted as follows: |
| 1295 |
|
| 1296 |
- If the control packet carries no payload data then the |
| 1297 |
corresponding SDRP route violates transit policy regardless of |
| 1298 |
the content of the payload packet carried along that route. |
| 1299 |
- If the control packet carries only the payload header, then |
| 1300 |
the corresponding SDRP route violates transit policy due to |
| 1301 |
the content of the payload header. |
| 1302 |
- If the control packet carries the payload header and the |
| 1303 |
transport header, then the corresponding SDRP route violates |
| 1304 |
transit policy for the particular combination of payload and |
| 1305 |
transport header contents. |
| 1306 |
|
| 1307 |
If a router receives an SDRP control packet that carries "Hop Count |
| 1308 |
Exceeded" Notification Code, the router should use the information in |
| 1309 |
the payload of the Control packet to construct an ICMP Time Exceeded |
| 1310 |
Message with code "time to live exceeded in transit" and send the |
| 1311 |
message to the host indicated by the source address in the Payload |
| 1312 |
Header. |
| 1313 |
|
| 1314 |
<span class="h3"><a class="selflink" id="section-7.2" href="#section-7.2">7.2</a> Processing ICMP messages</span> |
| 1315 |
|
| 1316 |
To correlate information carried in the ICMP messages with the SDRP |
| 1317 |
routes used by the router, the router uses the portion of the SDRP |
| 1318 |
datagram returned by ICMP. This must contain the Source Route |
| 1319 |
Identifier of the SDRP route used by the router. |
| 1320 |
|
| 1321 |
ICMP Destination Unreachable messages with a code meaning |
| 1322 |
"fragmentation needed and DF set" should be used for SDRP MTU |
| 1323 |
discovery as described in <a href="#section-9">Section 9</a>. |
| 1324 |
|
| 1325 |
All other ICMP Unreachable messages indicate that the associated |
| 1326 |
route is not feasible. |
| 1327 |
|
| 1328 |
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Constructing D-FIBs.</span> |
| 1329 |
|
| 1330 |
A BR constructs its D-FIB as a result of participating in either BGP |
| 1331 |
or IDRP. A BR must advertise a route to destinations within its |
| 1332 |
domain to all of its external peers (BRs in adjacent domains), via |
| 1333 |
BGP or IDRP. In BGP and IDRP, a BR must advertise a route to |
| 1334 |
destinations within its domain to all of its external peers (BRs in |
| 1335 |
adjacent domains). |
| 1336 |
|
| 1337 |
|
| 1338 |
|
| 1339 |
|
| 1340 |
<span class="grey">Estrin, et al Informational [Page 24]</span></pre> |
| 1341 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-25" ></span> |
| 1342 |
<span class="grey"><a href="./rfc1940">RFC 1940</a> SDRv1 May 1996</span> |
| 1343 |
|
| 1344 |
|
| 1345 |
If a BR receives a route to an adjacent domain from a BR in that |
| 1346 |
domain and selects that route as part of its BGP or IDRP Decision |
| 1347 |
Process, then it must propagate this route (via BGP or IDRP) to all |
| 1348 |
other BRs within its domain. A BR may also propagate such a route if |
| 1349 |
it depicts an autonomous system other than the adjacent domain. |
| 1350 |
|
| 1351 |
Since AS numbers are encoded as network numbers in network 128.0.0.0, |
| 1352 |
it is possible to also advertise a route to a domain in BGP or IDRP. |
| 1353 |
|
| 1354 |
<span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. SDRP MTU Discovery</span> |
| 1355 |
|
| 1356 |
To participate in Path MTU Discovery ([<a href="#ref-6" title=""Path MTU Discovery"">6</a>]) a router may maintain |
| 1357 |
information about the maximum length of the payload packet that can |
| 1358 |
be carried without fragmentation along a particular SDRP route. |
| 1359 |
|
| 1360 |
SDRP provides two complimentary techniques to support MTU Discovery. |
| 1361 |
|
| 1362 |
The first one is passive and is based on the receipt of the ICMP |
| 1363 |
Destination Unreachable messages (as described in <a href="#section-7.2">Section 7.2</a>). By |
| 1364 |
combining information provided in the ICMP message with local |
| 1365 |
information about the SDRP route the local system can determine the |
| 1366 |
length of a payload packet that would require fragmentation. |
| 1367 |
|
| 1368 |
The second one is active and employs the Probe Indicator bit. If an |
| 1369 |
SDRP data packet that carries the Probe Indicator bit in the SDRP |
| 1370 |
header and Don't Fragment flag in the delivery header triggers the |
| 1371 |
last router on the SDRP route to return an SDRP Control packet (with |
| 1372 |
the Notification Code "Probe Completed"), then the information |
| 1373 |
carried in the payload header of the control packet can be used to |
| 1374 |
determine the length of the payload packet that went through the SDRP |
| 1375 |
route without fragmentation. |
| 1376 |
|
| 1377 |
<span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a>. Acknowledgments</span> |
| 1378 |
|
| 1379 |
The authors would like to thank Scott Bradner (Harvard University), |
| 1380 |
Noel Chiappa (Consultant), Joel Halpern (Newbridge Networks), |
| 1381 |
Christian Huitema (INRIA), and Curtis Villamizar (ANS) for their |
| 1382 |
comments on various aspects of this document. |
| 1383 |
|
| 1384 |
Security Considerations |
| 1385 |
|
| 1386 |
Security issues are not discussed in this memo. |
| 1387 |
|
| 1388 |
|
| 1389 |
|
| 1390 |
|
| 1391 |
|
| 1392 |
|
| 1393 |
|
| 1394 |
|
| 1395 |
|
| 1396 |
<span class="grey">Estrin, et al Informational [Page 25]</span></pre> |
| 1397 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-26" ></span> |
| 1398 |
<span class="grey"><a href="./rfc1940">RFC 1940</a> SDRv1 May 1996</span> |
| 1399 |
|
| 1400 |
|
| 1401 |
Authors' Addresses |
| 1402 |
|
| 1403 |
Deborah Estrin |
| 1404 |
USC/Information Sciences Institute |
| 1405 |
4676 Admiralty Way |
| 1406 |
Marina Del Rey, Ca 90292-6695. |
| 1407 |
|
| 1408 |
Phone: +1 310 822 1511 x 253 |
| 1409 |
EMail: [email protected] |
| 1410 |
|
| 1411 |
|
| 1412 |
Tony Li |
| 1413 |
cisco Systems, Inc. |
| 1414 |
1525 O'Brien Drive |
| 1415 |
Menlo Park, CA 94025 |
| 1416 |
|
| 1417 |
Phone: +1 415 526 8186 |
| 1418 |
EMail: [email protected] |
| 1419 |
|
| 1420 |
|
| 1421 |
Yakov Rekhter |
| 1422 |
Cisco systems |
| 1423 |
170 West Tasman Drive |
| 1424 |
San Jose, CA, USA |
| 1425 |
|
| 1426 |
Phone: +1 914 528 0090 |
| 1427 |
Fax: +1 408 526-4952 |
| 1428 |
EMail: [email protected] |
| 1429 |
|
| 1430 |
|
| 1431 |
Kannan Varadhan |
| 1432 |
USC/Information Sciences Institute |
| 1433 |
4676 Admiralty Way |
| 1434 |
Marina Del Rey, Ca 90292-6695. |
| 1435 |
|
| 1436 |
Phone: +1 310 822 1511 x 402 |
| 1437 |
EMail: [email protected] |
| 1438 |
|
| 1439 |
|
| 1440 |
Daniel Zappala |
| 1441 |
USC/Information Sciences Institute |
| 1442 |
4676 Admiralty Way |
| 1443 |
Marina Del Rey, Ca 90292-6695. |
| 1444 |
|
| 1445 |
Phone: +1 310 822 1511 x 352 |
| 1446 |
EMail: [email protected] |
| 1447 |
|
| 1448 |
|
| 1449 |
|
| 1450 |
|
| 1451 |
|
| 1452 |
<span class="grey">Estrin, et al Informational [Page 26]</span></pre> |
| 1453 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-27" ></span> |
| 1454 |
<span class="grey"><a href="./rfc1940">RFC 1940</a> SDRv1 May 1996</span> |
| 1455 |
|
| 1456 |
|
| 1457 |
References |
| 1458 |
|
| 1459 |
[<a id="ref-1">1</a>] Lougheed, K., and Y. Rekhter, "A Border Gateway Protocol 3 |
| 1460 |
(BGP-3), <a href="./rfc1267">RFC 1267</a>, October 1991. |
| 1461 |
|
| 1462 |
[<a id="ref-2">2</a>] Rekhter, Y., and P. Gross, "Application of the Border Gateway |
| 1463 |
Protocol in the Internet", <a href="./rfc1268">RFC 1268</a>, October 1991. |
| 1464 |
|
| 1465 |
[<a id="ref-3">3</a>] Rekhter, Y., and T. Li, "A Border Gateway Protocol 4 (BGP-4)", |
| 1466 |
<a href="./rfc1654">RFC 1654</a>, July 1994. |
| 1467 |
|
| 1468 |
[<a id="ref-4">4</a>] Hares, S., "IDRP for IP", IDR Working Group, 1994. |
| 1469 |
Work in Progress. |
| 1470 |
|
| 1471 |
[<a id="ref-5">5</a>] Postel, J., "Internet Protocol - DARPA Internet Program |
| 1472 |
Protocol Specification", STD 5, <a href="./rfc791">RFC 791</a>, September 1981. |
| 1473 |
|
| 1474 |
[<a id="ref-6">6</a>] Mogul, J., and S. Deering, "Path MTU Discovery", <a href="./rfc1191">RFC 1191</a>, |
| 1475 |
November 1990. |
| 1476 |
|
| 1477 |
[<a id="ref-7">7</a>] Reynolds, J., and J. Postel, "ASSIGNED NUMBERS", STD 2, |
| 1478 |
<a href="./rfc1700">RFC 1700</a>, October 1994. |
| 1479 |
|
| 1480 |
|
| 1481 |
|
| 1482 |
|
| 1483 |
|
| 1484 |
|
| 1485 |
|
| 1486 |
|
| 1487 |
|
| 1488 |
|
| 1489 |
|
| 1490 |
|
| 1491 |
|
| 1492 |
|
| 1493 |
|
| 1494 |
|
| 1495 |
|
| 1496 |
|
| 1497 |
|
| 1498 |
|
| 1499 |
|
| 1500 |
|
| 1501 |
|
| 1502 |
|
| 1503 |
|
| 1504 |
|
| 1505 |
|
| 1506 |
|
| 1507 |
|
| 1508 |
Estrin, et al Informational [Page 27] |
| 1509 |
</pre> |