RFC4728 日本語訳
4728 The Dynamic Source Routing Protocol (DSR) for Mobile Ad HocNetworks for IPv4. D. Johnson, Y. Hu, D. Maltz. February 2007. (Format: TXT=265706 bytes) (Status: EXPERIMENTAL)
プログラムでの自動翻訳です。
英語原文
Network Working Group D. Johnson
Request for Comments: 4728 Rice University
Category: Experimental Y. Hu
UIUC
D. Maltz
Microsoft Research
February 2007
コメントを求めるワーキンググループD.ペニス要求をネットワークでつないでください: 4728年のライス大学カテゴリ: 実験的なY.のUIUC D.マルツマイクロソフト研究胡2007年2月
The Dynamic Source Routing Protocol (DSR)
for Mobile Ad Hoc Networks for IPv4
IPv4のためのモバイル臨時のネットワークのためのダイナミックなソースルーティング・プロトコル(DSR)
Status of This Memo
このメモの状態
This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested. Distribution of this memo is unlimited.
このメモはインターネットコミュニティのためにExperimentalプロトコルを定義します。 それはどんな種類のインターネット標準も指定しません。 議論と改善提案は要求されています。 このメモの分配は無制限です。
Copyright Notice
版権情報
Copyright (C) The IETF Trust (2007).
IETFが信じる著作権(C)(2007)。
Abstract
要約
The Dynamic Source Routing protocol (DSR) is a simple and efficient routing protocol designed specifically for use in multi-hop wireless ad hoc networks of mobile nodes. DSR allows the network to be completely self-organizing and self-configuring, without the need for any existing network infrastructure or administration. The protocol is composed of the two main mechanisms of "Route Discovery" and "Route Maintenance", which work together to allow nodes to discover and maintain routes to arbitrary destinations in the ad hoc network. All aspects of the protocol operate entirely on demand, allowing the routing packet overhead of DSR to scale automatically to only what is needed to react to changes in the routes currently in use. The protocol allows multiple routes to any destination and allows each sender to select and control the routes used in routing its packets, for example, for use in load balancing or for increased robustness. Other advantages of the DSR protocol include easily guaranteed loop- free routing, operation in networks containing unidirectional links, use of only "soft state" in routing, and very rapid recovery when routes in the network change. The DSR protocol is designed mainly for mobile ad hoc networks of up to about two hundred nodes and is designed to work well even with very high rates of mobility. This document specifies the operation of the DSR protocol for routing unicast IPv4 packets.
Dynamic Sourceルート設定プロトコル(DSR)は特にモバイルノードのマルチホップのワイヤレスの臨時のネットワークにおける使用のために設計された簡単で効率的なルーティング・プロトコルです。 ネットワークは、完全に自己組織化といずれの必要性が存在しないでDSRはネットワークインフラか管理を自己に構成することにさせます。 プロトコルはノードが臨時のネットワークで任意の目的地にルートを発見して、維持するのを許容するために一緒に働いている「ルート発見」と「ルートメインテナンス」の2つの主なメカニズムで構成されます。 プロトコルの全面は完全に要求に応じて作動します、DSRのルーティングパケットオーバーヘッドが自動的に現在使用中のルートの変化に反応するのに必要であるものだけに比例するのを許容して。 プロトコルは、例えばロードバランシングにおける使用か増強された丈夫さのためにパケットを発送する際にどんな目的地にも複数のルートを許容して、選ぶ各送付者とルートが使用したコントロールを許します。 ネットワークにおけるルートが変化するとき、DSRプロトコルの他の利点は容易に保証された輪の無料のルーティング、単方向のリンクを含むネットワークにおける操作、ルーティングにおける「軟性国家」だけの使用、および非常に急速な回復を含んでいます。 DSRプロトコルは、主に最大およそ200のノードのモバイル臨時のネットワークのために設計されていて、移動性の非常に高いレートがあってもうまくいくように設計されています。 このドキュメントはルーティングユニキャストIPv4パケットにDSRプロトコルの操作を指定します。
Johnson, et al. Experimental [Page 1] RFC 4728 The Dynamic Source Routing Protocol February 2007
ジョンソン、他 ダイナミックな実験的な[1ページ]RFC4728のソースルーティング・プロトコル2007年2月
Table of Contents
目次
1. Introduction ....................................................5
2. Assumptions .....................................................7
3. DSR Protocol Overview ...........................................9
3.1. Basic DSR Route Discovery .................................10
3.2. Basic DSR Route Maintenance ...............................12
3.3. Additional Route Discovery Features .......................14
3.3.1. Caching Overheard Routing Information ..............14
3.3.2. Replying to Route Requests Using Cached Routes .....15
3.3.3. Route Request Hop Limits ...........................16
3.4. Additional Route Maintenance Features .....................17
3.4.1. Packet Salvaging ...................................17
3.4.2. Queued Packets Destined over a Broken Link .........18
3.4.3. Automatic Route Shortening .........................19
3.4.4. Increased Spreading of Route Error Messages ........20
3.5. Optional DSR Flow State Extension .........................20
3.5.1. Flow Establishment .................................21
3.5.2. Receiving and Forwarding Establishment Packets .....22
3.5.3. Sending Packets along Established Flows ............22
3.5.4. Receiving and Forwarding Packets Sent along
Established Flows ..................................23
3.5.5. Processing Route Errors ............................24
3.5.6. Interaction with Automatic Route Shortening ........24
3.5.7. Loop Detection .....................................25
3.5.8. Acknowledgement Destination ........................25
3.5.9. Crash Recovery .....................................25
3.5.10. Rate Limiting .....................................25
3.5.11. Interaction with Packet Salvaging .................26
4. Conceptual Data Structures .....................................26
4.1. Route Cache ...............................................26
4.2. Send Buffer ...............................................30
4.3. Route Request Table .......................................30
4.4. Gratuitous Route Reply Table ..............................31
4.5. Network Interface Queue and Maintenance Buffer ............32
4.6. Blacklist .................................................33
5. Additional Conceptual Data Structures for Flow State
Extension ......................................................34
5.1. Flow Table ................................................34
5.2. Automatic Route Shortening Table ..........................35
5.3. Default Flow ID Table .....................................36
6. DSR Options Header Format ......................................36
6.1. Fixed Portion of DSR Options Header .......................37
6.2. Route Request Option ......................................40
6.3. Route Reply Option ........................................42
1. 序論…5 2. 仮定…7 3. DSRは概要について議定書の中で述べます…9 3.1. 基本的なDSRは発見を発送します…10 3.2. 基本的なDSRはメインテナンスを発送します…12 3.3. 追加ルート発見機能…14 3.3.1. キャッシュは経路情報を立ち聞きしました…14 3.3.2. 発送する返答は、使用がルートをキャッシュしたよう要求します…15 3.3.3. 要求ホップ限界を発送してください…16 3.4. 追加ルートメインテナンス機能…17 3.4.1. パケットサルベージ…17 3.4.2. 列に並ばせられたパケットはリンク切れの上で運命づけられました…18 3.4.3. 自動ルート短縮…19 3.4.4. ルートエラーメッセージを広まらせながら、増加します…20 3.5. 任意のDSR流れ州の拡張子…20 3.5.1. 流れ設立…21 3.5.2. 設立パケットを受けて、進めます…22 3.5.3. パケットを送ると、流れは確立されました…22 3.5.4. 送られたパケットを受けて、進めると、流れは確立されました…23 3.5.5. 処理ルート誤り…24 3.5.6. 自動ルート短縮との相互作用…24 3.5.7. 検出を輪にしてください…25 3.5.8. 承認の目的地…25 3.5.9. 回復を墜落させてください…25 3.5.10. 制限を評定してください…25 3.5.11. パケットサルベージとの相互作用…26 4. 概念的なデータ構造…26 4.1. キャッシュを発送してください…26 4.2. バッファを送ってください…30 4.3. 要求テーブルを発送してください…30 4.4. 無料のルート回答テーブル…31 4.5. インタフェース待ち行列とメインテナンスバッファをネットワークでつないでください…32 4.6. ブラックリストに載せます。33 5. 流れのための追加概念的なデータ構造は拡大を述べます…34 5.1. 流れテーブル…34 5.2. 自動ルート短縮テーブル…35 5.3. デフォルト流れIDテーブル…36 6. DSRオプションヘッダー形式…36 6.1. DSRオプションヘッダーの固定部分…37 6.2. 要求オプションを発送してください…40 6.3. 回答オプションを発送してください…42
Johnson, et al. Experimental [Page 2] RFC 4728 The Dynamic Source Routing Protocol February 2007
ジョンソン、他 ダイナミックな実験的な[2ページ]RFC4728のソースルーティング・プロトコル2007年2月
6.4. Route Error Option ........................................44
6.4.1. Node Unreachable Type-Specific Information .........46
6.4.2. Flow State Not Supported Type-Specific
Information ........................................46
6.4.3. Option Not Supported Type-Specific Information .....46
6.5. Acknowledgement Request Option ............................46
6.6. Acknowledgement Option ....................................47
6.7. DSR Source Route Option ...................................48
6.8. Pad1 Option ...............................................50
6.9. PadN Option ...............................................50
7. Additional Header Formats and Options for Flow State
Extension ......................................................51
7.1. DSR Flow State Header .....................................52
7.2. New Options and Extensions in DSR Options Header ..........52
7.2.1. Timeout Option .....................................52
7.2.2. Destination and Flow ID Option .....................53
7.3. New Error Types for Route Error Option ....................54
7.3.1. Unknown Flow Type-Specific Information .............54
7.3.2. Default Flow Unknown Type-Specific Information .....55
7.4. New Acknowledgement Request Option Extension ..............55
7.4.1. Previous Hop Address Extension .....................55
8. Detailed Operation .............................................56
8.1. General Packet Processing .................................56
8.1.1. Originating a Packet ...............................56
8.1.2. Adding a DSR Options Header to a Packet ............57
8.1.3. Adding a DSR Source Route Option to a Packet .......57
8.1.4. Processing a Received Packet .......................58
8.1.5. Processing a Received DSR Source Route Option ......60
8.1.6. Handling an Unknown DSR Option .....................63
8.2. Route Discovery Processing ................................64
8.2.1. Originating a Route Request ........................65
8.2.2. Processing a Received Route Request Option .........66
8.2.3. Generating a Route Reply Using the Route Cache .....68
8.2.4. Originating a Route Reply ..........................71
8.2.5. Preventing Route Reply Storms ......................72
8.2.6. Processing a Received Route Reply Option ...........74
8.3. Route Maintenance Processing ..............................74
8.3.1. Using Link-Layer Acknowledgements ..................75
8.3.2. Using Passive Acknowledgements .....................76
8.3.3. Using Network-Layer Acknowledgements ...............77
8.3.4. Originating a Route Error ..........................80
8.3.5. Processing a Received Route Error Option ...........81
8.3.6. Salvaging a Packet .................................82
8.4. Multiple Network Interface Support ........................84
8.5. IP Fragmentation and Reassembly ...........................84
8.6. Flow State Processing .....................................85
8.6.1. Originating a Packet ...............................85
8.6.2. Inserting a DSR Flow State Header ..................88
6.4. エラーオプションを発送してください…44 6.4.1. ノードの手の届かないタイプ特有の情報…46 6.4.2. 流れ州はタイプ特有の情報をサポートしませんでした…46 6.4.3. オプションはタイプ特有の情報をサポートしませんでした…46 6.5. 承認要求オプション…46 6.6. 承認オプション…47 6.7. DSR送信元経路オプション…48 6.8. Pad1オプション…50 6.9. PadNオプション…50 7. 流れのための追加ヘッダー形式とオプションは拡大を述べます…51 7.1. DSR流れ州のヘッダー…52 7.2. DSRオプションヘッダーでの新しいオプションと拡大…52 7.2.1. タイムアウトオプション…52 7.2.2. 目的地と流れIDオプション…53 7.3. ルートエラーオプションのための新しい誤りタイプ…54 7.3.1. 未知の流れタイプ特有の情報…54 7.3.2. デフォルトの流れの未知のタイプ特有の情報…55 7.4. 新しい承認要求オプション拡張子…55 7.4.1. 前のホップアドレス拡大…55 8. 詳細な操作…56 8.1. 一般パケット処理…56 8.1.1. パケットを溯源します…56 8.1.2. DSRオプションヘッダーをパケットに加えます…57 8.1.3. DSR送信元経路オプションをパケットに加えます…57 8.1.4. 容認されたパケットを処理します…58 8.1.5. 受け取られていているDSRソースを処理して、オプションを発送してください…60 8.1.6. 未知のDSRオプションを扱います…63 8.2. 発見処理を発送してください…64 8.2.1. ルート要求を溯源します…65 8.2.2. 容認されたルートを処理して、オプションを要求してください…66 8.2.3. ルートを生成して、経路キャッシュを使用して、返答してください…68 8.2.4. ルートを溯源して、返答してください…71 8.2.5. ルート回答を防ぐのはどなります…72 8.2.6. 容認されたルート回答オプションを処理します…74 8.3. メインテナンス処理を発送してください…74 8.3.1. リンクレイヤ承認を使用します…75 8.3.2. 受け身の承認を使用します…76 8.3.3. ネットワーク層承認を使用します…77 8.3.4. ルート誤りを溯源します…80 8.3.5. 容認されたルートエラーオプションを処理します…81 8.3.6. パケットを回収します…82 8.4. 複数のネットワーク・インターフェースサポート…84 8.5. IPの断片化とReassembly…84 8.6. 流れ州の処理…85 8.6.1. パケットを溯源します…85 8.6.2. DSR流動を挿入して、ヘッダーを述べてください…88
Johnson, et al. Experimental [Page 3] RFC 4728 The Dynamic Source Routing Protocol February 2007
ジョンソン、他 ダイナミックな実験的な[3ページ]RFC4728のソースルーティング・プロトコル2007年2月
8.6.3. Receiving a Packet .................................88
8.6.4. Forwarding a Packet Using Flow IDs .................93
8.6.5. Promiscuously Receiving a Packet ...................93
8.6.6. Operation Where the Layer below DSR
Decreases the IP TTL ...............................94
8.6.7. Salvage Interactions with DSR ......................94
9. Protocol Constants and Configuration Variables .................95
10. IANA Considerations ...........................................96
11. Security Considerations .......................................96
Appendix A. Link-MaxLife Cache Description ........................97
Appendix B. Location of DSR in the ISO Network Reference Model ....99
Appendix C. Implementation and Evaluation Status .................100
Acknowledgements .................................................101
Normative References .............................................102
Informative References ...........................................102
8.6.3. パケットを受けます…88 8.6.4. 流れIDを使用することでパケットを進めます…93 8.6.5. 乱雑に、パケットを受けます…93 8.6.6. 操作どこ層の以下のDSR減少IP TTL…94 8.6.7. DSRとの相互作用を救助してください…94 9. 定数と構成変数について議定書の中で述べてください…95 10. IANA問題…96 11. セキュリティ問題…96 付録A.リンク-MaxLifeは記述をキャッシュします…97 ISOネットワーク規範モデルのDSRの付録B.位置…99の付録C.実装と評価状態…100の承認…101 標準の参照…102 有益な参照…102
Johnson, et al. Experimental [Page 4] RFC 4728 The Dynamic Source Routing Protocol February 2007
ジョンソン、他 ダイナミックな実験的な[4ページ]RFC4728のソースルーティング・プロトコル2007年2月
1. Introduction
1. 序論
The Dynamic Source Routing protocol (DSR) [JOHNSON94, JOHNSON96a] is a simple and efficient routing protocol designed specifically for use in multi-hop wireless ad hoc networks of mobile nodes. Using DSR, the network is completely self-organizing and self-configuring, requiring no existing network infrastructure or administration. Network nodes cooperate to forward packets for each other to allow communication over multiple "hops" between nodes not directly within wireless transmission range of one another. As nodes in the network move about or join or leave the network, and as wireless transmission conditions such as sources of interference change, all routing is automatically determined and maintained by the DSR routing protocol. Since the number or sequence of intermediate hops needed to reach any destination may change at any time, the resulting network topology may be quite rich and rapidly changing.
Dynamic Sourceルート設定プロトコル(DSR)[JOHNSON94、JOHNSON96a]は特にモバイルノードのマルチホップのワイヤレスの臨時のネットワークにおける使用のために設計された簡単で効率的なルーティング・プロトコルです。 DSRを使用して、どんな既存のネットワークインフラも管理も必要としないで、ネットワークは、完全に自己組織化と自己構成です。 ネットワーク・ノードは協力して、互いが放送範囲のどんなお互いの直接中にもノードの間の複数の「ホップ」の上にコミュニケーションを許容しないように、パケットを進めます。 ネットワークにおけるノードがネットワークを動き回るか、加わるか、または出て、干渉の源などの放送状態が変化するとき、すべてのルーティングが、DSRルーティング・プロトコルによって自動的に決定して、維持されます。 どんな目的地にも達するのが必要である中間的ホップの数か系列がいつでも変化するかもしれないので、結果として起こるネットワーク形態は、かなり豊かで急速に変化しているかもしれません。
In designing DSR, we sought to create a routing protocol that had very low overhead yet was able to react very quickly to changes in the network. The DSR protocol provides highly reactive service in order to help ensure successful delivery of data packets in spite of node movement or other changes in network conditions.
DSRを設計する際に、私たちはネットワークで非常に低いオーバーヘッドを持っていましたが、非常に急速に変化に反応できたルーティング・プロトコルを作成しようとしました。 DSRプロトコルは、ネットワーク状態におけるノード運動か他の変化にもかかわらず、データ・パケットのうまくいっている配送を確実にするのを助けるために非常に反応しているサービスを提供します。
The DSR protocol is composed of two main mechanisms that work together to allow the discovery and maintenance of source routes in the ad hoc network:
DSRプロトコルは臨時のネットワークにおける、送信元経路の発見とメインテナンスを許容するために一緒に動作する2つの主なメカニズムで構成されます:
- Route Discovery is the mechanism by which a node S wishing to send
a packet to a destination node D obtains a source route to D.
Route Discovery is used only when S attempts to send a packet to D
and does not already know a route to D.
- ルートディスカバリーはSがパケットをDに送るのを試みて、既にルートをDに知らないときだけ、目的地ノードDにパケットを送りたがっているノードSがD.Routeディスカバリーに送信元経路を入手するメカニズムが使用されているということです。
- Route Maintenance is the mechanism by which node S is able to
detect, while using a source route to D, if the network topology
has changed such that it can no longer use its route to D because
a link along the route no longer works. When Route Maintenance
indicates a source route is broken, S can attempt to use any other
route it happens to know to D, or it can invoke Route Discovery
again to find a new route for subsequent packets to D. Route
Maintenance for this route is used only when S is actually sending
packets to D.
- Dに送信元経路を使用している間、ルートMaintenanceは検出するノードSがどれであるかでできるメカニズムです、ネットワーク形態がルートに沿ったリンクがもう働いていないのでもうDにルートを使用できないように変化したなら。 Route Maintenanceが、送信元経路が壊れているのを示すとき、Sが、それがたまたまDに知るいかなる他のルートも使用するのを試みることができますか、またはそれは、Sが実際にパケットをDに送るときだけ、このルートへのD.Route Maintenanceへのその後のパケットのための新しいルートが使用されているのがわかるために再びRouteディスカバリーを呼び出すことができます。
In DSR, Route Discovery and Route Maintenance each operate entirely "on demand". In particular, unlike other protocols, DSR requires no periodic packets of any kind at any layer within the network. For example, DSR does not use any periodic routing advertisement, link status sensing, or neighbor detection packets and does not rely on these functions from any underlying protocols in the network. This
DSRでは、RouteディスカバリーとRoute Maintenanceはそれぞれ「要求に応じて完全に」作動します。 他のプロトコルと異なって、特に、DSRはネットワークの中のどんな層でもどんな種類のどんな周期的なパケットも必要としません。 例えば、DSRはどんな周期的なルーティング広告、リンク状態の感じ、または隣人検出パケットも使用しないで、またネットワークにおけるどんな基本的なプロトコルからもこれらの機能を当てにしません。 これ
Johnson, et al. Experimental [Page 5] RFC 4728 The Dynamic Source Routing Protocol February 2007
ジョンソン、他 ダイナミックな実験的な[5ページ]RFC4728のソースルーティング・プロトコル2007年2月
entirely on-demand behavior and lack of periodic activity allows the number of overhead packets caused by DSR to scale all the way down to zero, when all nodes are approximately stationary with respect to each other and all routes needed for current communication have already been discovered. As nodes begin to move more or as communication patterns change, the routing packet overhead of DSR automatically scales to only what is needed to track the routes currently in use. Network topology changes not affecting routes currently in use are ignored and do not cause reaction from the protocol.
完全に、周期的な活動の要求次第の振舞いと不足はDSRがいっぱいなゼロまで比例させられる頭上のパケットの数を許容します、すべてのノードが互いに関してほとんど静止していて、既に現在のコミュニケーションに必要であるすべてのルートを発見してあるとき。 よりまたは、コミュニケーションパターンが変化するのに従ってノードが移行し始めるとき、DSRのルーティングパケットオーバーヘッドは自動的に現在使用中のルートを追跡するのに必要であるものだけに比例します。 現在使用中のルートに影響しないネットワークトポロジ変更が、無視されて、プロトコルからの反応を引き起こしません。
All state maintained by DSR is "soft state" [CLARK88], in that the loss of any state will not interfere with the correct operation of the protocol; all state is discovered as needed and can easily and quickly be rediscovered if needed after a failure without significant impact on the protocol. This use of only soft state allows the routing protocol to be very robust to problems such as dropped or delayed routing packets or node failures. In particular, a node in DSR that fails and reboots can easily rejoin the network immediately after rebooting; if the failed node was involved in forwarding packets for other nodes as an intermediate hop along one or more routes, it can also resume this forwarding quickly after rebooting, with no or minimal interruption to the routing protocol.
DSRによって維持されたすべての状態が「軟性国家」[CLARK88]です、どんな状態の損失もプロトコルの正しい操作を妨げないので。 失敗の後にプロトコルで重要な影響なしで必要であるなら、すべての状態を必要に応じて発見して、簡単にすぐに再発見できます。 軟性国家だけのこの使用は、ルーティング・プロトコルが下げられるか、または遅らせられるようなパケットかノード障害を発送することにおける問題に非常に強健であることを許容します。 特に、失敗して、リブートするDSRのノードはリブート直後容易にネットワークに再び加わることができます。 また、失敗したノードが他のノードのために中間的ホップとして1つ以上のルートに沿って推進パケットにかかわったなら、それはいいえか最小量の中断でルーティング・プロトコルにリブートした後に、すぐにこの推進を再開できます。
In response to a single Route Discovery (as well as through routing information from other packets overheard), a node may learn and cache multiple routes to any destination. This support for multiple routes allows the reaction to routing changes to be much more rapid, since a node with multiple routes to a destination can try another cached route if the one it has been using should fail. This caching of multiple routes also avoids the overhead of needing to perform a new Route Discovery each time a route in use breaks. The sender of a packet selects and controls the route used for its own packets, which, together with support for multiple routes, also allows features such as load balancing to be defined. In addition, all routes used are easily guaranteed to be loop-free, since the sender can avoid duplicate hops in the routes selected.
ただ一つのRouteディスカバリー(他のパケットからの情報が立ち聞きしたルーティングと同じくらいよく)に対応して、ノードは、どんな目的地にも複数のルートを学んで、キャッシュするかもしれません。 複数のルートのこのサポートはそれが使用している失敗するならはるかに急速である目的地への複数のルートがあるノードが別のキャッシュされたルートを試みることができて以来の変化を発送するのに反応を許します。 また、複数のルートのこのキャッシュは使用中のルートが壊れるたびに新しいRouteディスカバリーを実行するのが必要であることのオーバーヘッドを避けます。 パケットの送付者は、それ自身のパケットに使用されるルートを、選択して、制御します。(また、それは、複数のルートのサポートと共にロードバランシングなどの特徴が定義されるのを許容します)。 さらに、ルートが使用したすべてが輪なしであるために容易に保証されます、送付者がルートによるホップが選択した写しを避けることができるので。
The operation of both Route Discovery and Route Maintenance in DSR are designed to allow unidirectional links and asymmetric routes to be supported. In particular, as noted in Section 2, in wireless networks, it is possible that a link between two nodes may not work equally well in both directions, due to differing transmit power levels or sources of interference.
DSRでのRouteディスカバリーとRoute Maintenanceの両方の操作は、単方向のリンクと非対称のルートが支えられるのを許容するように設計されています。 2つのノードの間のリンクが等しく両方の方向にうまくいかないのは、セクション2に述べられるワイヤレス・ネットワークで、特に、干渉のパワーレベルか情報筋が異なるため伝わっているのが可能です。
It is possible to interface a DSR network with other networks, external to this DSR network. Such external networks may, for example, be the Internet or may be other ad hoc networks routed with
それは、他のネットワークにDSRネットワークを連結するのにおいて可能であって、このDSRネットワークに外部です。 そのような外部のネットワークは、例えば、インターネットであるかもしれないか掘られた他の臨時のネットワークであるかもしれません。
Johnson, et al. Experimental [Page 6] RFC 4728 The Dynamic Source Routing Protocol February 2007
ジョンソン、他 ダイナミックな実験的な[6ページ]RFC4728のソースルーティング・プロトコル2007年2月
a routing protocol other than DSR. Such external networks may also be other DSR networks that are treated as external networks in order to improve scalability. The complete handling of such external networks is beyond the scope of this document. However, this document specifies a minimal set of requirements and features necessary to allow nodes only implementing this specification to interoperate correctly with nodes implementing interfaces to such external networks.
DSR以外のルーティング・プロトコル。 また、そのような外部のネットワークはスケーラビリティを改良するために外部のネットワークとして扱われる他のDSRネットワークであるかもしれません。 そのような外部のネットワークの完全な取り扱いはこのドキュメントの範囲を超えています。 しかしながら、このドキュメントはノードがそのような外部のネットワークにインタフェースを実装していてこの仕様を履行するだけであるノードが正しく共同利用するのを許容する1人の極小集合の要件と必要特性を指定します。
This document specifies the operation of the DSR protocol for routing unicast IPv4 packets in multi-hop wireless ad hoc networks. Advanced, optional features, such as Quality of Service (QoS) support and efficient multicast routing, and operation of DSR with IPv6 [RFC2460], will be covered in other documents. The specification of DSR in this document provides a compatible base on which such features can be added, either independently or by integration with the DSR operation specified here. As described in Appendix C, the design of DSR has been extensively studied through detailed simulations and testbed implementation and demonstration; this document encourages additional implementation and experimentation with the protocol.
このドキュメントはマルチホップのワイヤレスの臨時のネットワークでルーティングユニキャストIPv4パケットにDSRプロトコルの操作を指定します。 Service(QoS)サポートと効率的なマルチキャストルーティングのQualityや、IPv6[RFC2460]とのDSRの操作などの高度で、任意の特徴は他のドキュメントでカバーされているでしょう。 DSRの仕様は本書では、独自か統合でそのような特徴を加えることができるコンパチブルベースをここで指定されるDSR操作に供給します。 Appendix Cで説明されるように、DSRのデザインは詳細なシミュレーション、テストベッド実装、およびデモンストレーションで手広く研究されました。 このドキュメントはプロトコルで追加実装と実験を奨励します。
The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119].
キーワード“MUST"、「必須NOT」が「必要です」、“SHALL"、「」、“SHOULD"、「「推薦され」て、「5月」の、そして、「任意」のNOTはRFC2119[RFC2119]で説明されるように本書では解釈されることであるべきですか?
2. Assumptions
2. 仮定
As described here, the DSR protocol is designed mainly for mobile ad hoc networks of up to about two hundred nodes and is designed to work well even with very high rates of mobility. Other protocol features and enhancements that may allow DSR to scale to larger networks are outside the scope of this document.
ここで説明されるように、DSRプロトコルは、主に最大およそ200のノードのモバイル臨時のネットワークのために設計されていて、移動性の非常に高いレートがあってもうまくいくように設計されています。 このドキュメントの範囲の外に他のプロトコル機能とDSRが、より大きいネットワークに比例できるかもしれない増進があります。
We assume in this document that all nodes wishing to communicate with other nodes within the ad hoc network are willing to participate fully in the protocols of the network. In particular, each node participating in the ad hoc network SHOULD also be willing to forward packets for other nodes in the network.
私たちは、臨時のネットワークの中で他のノードとコミュニケートしたがっているすべてのノードが、ネットワークのプロトコルに完全に参加しても構わないと思っていると本書では思います。 特に、臨時に参加する各ノードがSHOULDをネットワークでつなぎます、また、ネットワークにおける他のノードのためにパケットを進めることを望んでください。
The diameter of an ad hoc network is the minimum number of hops necessary for a packet to reach from any node located at one extreme edge of the ad hoc network to another node located at the opposite extreme. We assume that this diameter will often be small (e.g., perhaps 5 or 10 hops), but it may often be greater than 1.
臨時のネットワークの直径はパケットが臨時のネットワークの1つの極端な縁に位置するどんなノードから全く正反対で位置する別のノードまでも届くのに必要なホップの最小の数です。 私たちは、この直径がしばしば小さいと(例えば、恐らく5か10のホップ)思いますが、しばしばそれは1以上であるかもしれません。
Johnson, et al. Experimental [Page 7] RFC 4728 The Dynamic Source Routing Protocol February 2007
ジョンソン、他 ダイナミックな実験的な[7ページ]RFC4728のソースルーティング・プロトコル2007年2月
Packets may be lost or corrupted in transmission on the wireless network. We assume that a node receiving a corrupted packet can detect the error, such as through a standard link-layer checksum or Cyclic Redundancy Check (CRC), and discard the packet.
パケットは、ワイヤレス・ネットワークでトランスミッションで失われているか、または崩壊するかもしれません。 私たちは、崩壊したパケットを受けるノードがチェックサムかCyclic Redundancy Checkの標準の(CRC)リンクレイヤなどの誤りを検出して、パケットを捨てることができると思います。
Nodes within the ad hoc network MAY move at any time without notice and MAY even move continuously, but we assume that the speed with which nodes move is moderate with respect to the packet transmission latency and wireless transmission range of the particular underlying network hardware in use. In particular, DSR can support very rapid rates of arbitrary node mobility, but we assume that nodes do not continuously move so rapidly as to make the flooding of every individual data packet the only possible routing protocol.
臨時のネットワークの中のノードは、いつでも、予告なしで移行して、絶え間なく移行さえするかもしれませんが、私たちは、ノードが移行する速度が使用中の特定の基本的なネットワークハードウェアのパケット伝送潜在と放送範囲に関して適度であると思います。 特に、DSRは任意のノードの移動性の非常に急速なレートをサポートすることができますが、私たちは、ノードが絶え間なくあらゆる個々のデータ・パケットの氾濫を可能だけにするほど急速にルーティング・プロトコルを動かさないと思います。
A common feature of many network interfaces, including most current LAN hardware for broadcast media such as wireless, is the ability to operate the network interface in "promiscuous" receive mode. This mode causes the hardware to deliver every received packet to the network driver software without filtering based on link-layer destination address. Although we do not require this facility, some of our optimizations can take advantage of its availability. Use of promiscuous mode does increase the software overhead on the CPU, but we believe that wireless network speeds and capacity are more the inherent limiting factors to performance in current and future systems; we also believe that portions of the protocol are suitable for implementation directly within a programmable network interface unit to avoid this overhead on the CPU [JOHNSON96a]. Use of promiscuous mode may also increase the power consumption of the network interface hardware, depending on the design of the receiver hardware, and in such cases, DSR can easily be used without the optimizations that depend on promiscuous receive mode or can be programmed to only periodically switch the interface into promiscuous mode. Use of promiscuous receive mode is entirely optional.
含む中で最も現在ワイヤレスなどの電波媒体のためのLANハードウェア多くのネットワーク・インターフェースの共通点は「無差別」でネットワーク・インターフェースを操作する能力がモードを受けるということです。 このモードで、ハードウェアはリンクレイヤ送付先アドレスに基づくフィルタリングなしであらゆる容認されたパケットをネットワークドライバソフトウェアに提供します。 私たちはこの施設を必要としませんが、私たちの最適化のいくつかが有用性を利用できます。 無差別なモードの使用はCPUでソフトウェアオーバーヘッドを増強しますが、私たちは、ワイヤレス・ネットワーク速度と容量が固有の制限が現在の、そして、将来のシステムにおける性能に因数分解する以上であると信じています。 また、私たちは、プログラマブルネットワーク・インターフェースユニットの直接中の実装がCPU[JOHNSON96a]の上にこのオーバーヘッドを避けるのにおいてプロトコルの部分が適当であると信じています。 無差別なモードの使用は、また、受信機ハードウェアの設計によって、ネットワーク・インターフェースハードウェアの電力消費量を増強するかもしれなくて、容易に無差別による最適化なしで使用されて、モードを受けるか、または定期的に単に無差別なモードにインタフェースを切り換えるようにプログラムできるというそのような場合、DSRのことであるかもしれません。 無差別の使用は受信されます。モードは完全に任意です。
Wireless communication ability between any pair of nodes may at times not work equally well in both directions, due, for example, to transmit power levels or sources of interference around the two nodes [BANTZ94, LAUER95]. That is, wireless communications between each pair of nodes will in many cases be able to operate bidirectionally, but at times the wireless link between two nodes may be only unidirectional, allowing one node to successfully send packets to the other while no communication is possible in the reverse direction. Some Medium Access Control (MAC) protocols, however, such as MACA [KARN90], MACAW [BHARGHAVAN94], or IEEE 802.11 [IEEE80211], limit unicast data packet transmission to bidirectional links, due to the required bidirectional exchange of request to send (RTS) and clear to send (CTS) packets in these protocols and to the link-layer acknowledgement feature in IEEE 802.11. When used on top of MAC
どんな組のノードの間の無線通信能力は時には、2つのノード[BANTZ94、LAUER95]の周りで干渉の両方の方向、例えば、パワーレベルを伝える支払われるべきものまたは源で等しくうまくいかないかもしれません。 すなわち、それぞれの組のノードの間の無線通信は多くの場合双方向に作動できるでしょうが、時には2つのノードの間のワイヤレスのリンクは単方向であるにすぎないかもしれません、どんなコミュニケーションも可能でない間、1つのノードが首尾よくパケットをもう片方に送るのを反対の方向に許容して。 いくつかのMedium Access Control(MAC)プロトコル、しかしながら、MACAなどの[KARN90](MACAW[BHARGHAVAN94]、またはIEEE802.11[IEEE80211])はユニキャストデータ・パケット送信をこれらのプロトコルで(RTS)と送信可(CTS)パケットを送るという要求の必要なバイディレクショナル変換とIEEE802.11のリンクレイヤ承認機能への双方向のリンクに制限します。 MACの上で使用されるいつ
Johnson, et al. Experimental [Page 8] RFC 4728 The Dynamic Source Routing Protocol February 2007
ジョンソン、他 ダイナミックな実験的な[8ページ]RFC4728のソースルーティング・プロトコル2007年2月
protocols such as these, DSR can take advantage of additional optimizations, such as the ability to reverse a source route to obtain a route back to the origin of the original route.
これらなどのプロトコル、DSRは追加最適化を利用できます、元のルートの発生源にルートを入手して戻すために送信元経路を逆にする能力などのように。
The IP address used by a node using the DSR protocol MAY be assigned by any mechanism (e.g., static assignment or use of Dynamic Host Configuration Protocol (DHCP) for dynamic assignment [RFC2131]), although the method of such assignment is outside the scope of this specification.
どんなメカニズム(例えば、Dynamic Host Configuration Protocol(DHCP)のダイナミックな課題[RFC2131]の静的な課題か使用)によってもノードによってDSRプロトコルを使用することで使用されるIPアドレスは割り当てられるかもしれません、この仕様の範囲の外にそのような課題のメソッドがありますが。
A routing protocol such as DSR chooses a next-hop for each packet and provides the IP address of that next-hop. When the packet is transmitted, however, the lower-layer protocol often has a separate, MAC-layer address for the next-hop node. DSR uses the Address Resolution Protocol (ARP) [RFC826] to translate from next-hop IP addresses to next-hop MAC addresses. In addition, a node MAY add an entry to its ARP cache based on any received packet, when the IP address and MAC address of the transmitting node are available in the packet; for example, the IP address of the transmitting node is present in a Route Request option (in the Address list being accumulated) and any packets containing a source route. Adding entries to the ARP cache in this way avoids the overhead of ARP in most cases.
DSRなどのルーティング・プロトコルは、各パケットに次のホップを選んで、その次のホップのアドレスをIPに提供します。 しかしながら、パケットが伝えられるとき、下位層プロトコルには、次のホップノードのための別々のMAC-層のアドレスがしばしばあります。 DSRは、次のホップIPアドレスから次のホップMACアドレスまで翻訳するのに、Address Resolutionプロトコル(ARP)[RFC826]を使用します。 さらに、ノードはどんな容認されたパケットにも基づくARPキャッシュにエントリーを加えるかもしれません、伝えるノードのIPアドレスとMACアドレスがパケットで利用可能であるときに。 例えば、送信元経路を含んでいて、伝えるノードのIPアドレスはRoute Requestオプション(蓄積されるAddressリストの)とどんなパケットにも存在しています。 このようにARPキャッシュにエントリーを加えると、多くの場合、ARPのオーバーヘッドは避けられます。
3. DSR Protocol Overview
3. DSRプロトコル概要
This section provides an overview of the operation of the DSR protocol. The basic version of DSR uses explicit "source routing", in which each data packet sent carries in its header the complete, ordered list of nodes through which the packet will pass. This use of explicit source routing allows the sender to select and control the routes used for its own packets, supports the use of multiple routes to any destination (for example, for load balancing), and allows a simple guarantee that the routes used are loop-free. By including this source route in the header of each data packet, other nodes forwarding or overhearing any of these packets can also easily cache this routing information for future use. Section 3.1 describes this basic operation of Route Discovery, Section 3.2 describes basic Route Maintenance, and Sections 3.3 and 3.4 describe additional features of these two parts of DSR's operation. Section 3.5 then describes an optional, compatible extension to DSR, known as "flow state", that allows the routing of most packets without an explicit source route header in the packet, while the fundamental properties of DSR's operation are preserved.
このセクションはDSRプロトコルの操作の概観を提供します。 DSRの基本的なバージョンは明白な「ソースルーティング」を使用します。(パケットが送った各データはヘッダーでそれでパケットが通るノードの完全で、規則正しいリストを運びます)。 明白なソースルーティングのこの使用は、選ぶ送付者とルートがそれ自身のパケットに使用したコントロールを許して、どんな目的地(例えばロードバランシングのために)にも複数のルートの使用を支持して、使用されるルートが輪なしであるという簡単な保証を許容します。 また、それぞれのデータ・パケットのヘッダーのこの送信元経路を含んでいることによって、これらのパケットのいずれも進めるか、または立ち聞きする他のノードは容易に今後の使用のためのこのルーティング情報をキャッシュできます。 セクション3.1はRouteディスカバリーのこの基本的な操作について説明します、そして、セクション3.2は基本的なRoute Maintenanceについて説明します、そして、セクション3.3と3.4はDSRの操作のこれらの2つの部品の付加的な機能について説明します。 次に、セクション3.5はパケットで明白な送信元経路ヘッダーなしでほとんどのパケットのルーティングを許す「流れ状態」として知られているDSRに任意の、そして、コンパチブル拡大について説明します、DSRの操作の基本財産は保持されますが。
Johnson, et al. Experimental [Page 9] RFC 4728 The Dynamic Source Routing Protocol February 2007
ジョンソン、他 ダイナミックな実験的な[9ページ]RFC4728のソースルーティング・プロトコル2007年2月
3.1. Basic DSR Route Discovery
3.1. 基本的なDSRルート発見
When some source node originates a new packet addressed to some destination node, the source node places in the header of the packet a "source route" giving the sequence of hops that the packet is to follow on its way to the destination. Normally, the sender will obtain a suitable source route by searching its "Route Cache" of routes previously learned; if no route is found in its cache, it will initiate the Route Discovery protocol to dynamically find a new route to this destination node. In this case, we call the source node the "initiator" and the destination node the "target" of the Route Discovery.
何らかのソースノードが何らかの目的地ノードに記述された新しいパケットを溯源するとき、ソースノードは、パケットが目的地への途中に続くことになっているホップの系列を与えながら、「送信元経路」をパケットのヘッダーに置きます。 通常、送付者は以前に学習されたルートの「経路キャッシュ」を捜すことによって、適当な送信元経路を入手するでしょう。 ルートが全くキャッシュで見つけられないと、それは、ダイナミックにこの目的地ノードに新しいルートを見つけるためにRouteディスカバリープロトコルを開始するでしょう。 この場合、私たちは、「創始者」にソースノードを呼んで、目的地ノードをRouteディスカバリーの「目標」と呼びます。
For example, suppose a node A is attempting to discover a route to node E. The Route Discovery initiated by node A in this example would proceed as follows:
例えば、ノードAが、Routeディスカバリーがこの例のノードAで開始したノードE.へのルートが以下の通り続くと発見するのを試みていると仮定してください:
^ "A" ^ "A,B" ^ "A,B,C" ^ "A,B,C,D"
| id=2 | id=2 | id=2 | id=2
+-----+ +-----+ +-----+ +-----+ +-----+
| A |---->| B |---->| C |---->| D |---->| E |
+-----+ +-----+ +-----+ +-----+ +-----+
| | | |
v v v v
^^「A、B」^「A、B、C」^、「A、B、C、D」| イド=2| イド=2| イド=2| イド=2+-----+ +-----+ +-----+ +-----+ +-----+ | A|、-、-、--、>| B|、-、-、--、>| C|、-、-、--、>| D|、-、-、--、>| E| +-----+ +-----+ +-----+ +-----+ +-----+ | | | | v対vに
To initiate the Route Discovery, node A transmits a "Route Request" as a single local broadcast packet, which is received by (approximately) all nodes currently within wireless transmission range of A, including node B in this example. Each Route Request identifies the initiator and target of the Route Discovery, and also contains a unique request identification (2, in this example), determined by the initiator of the Request. Each Route Request also contains a record listing the address of each intermediate node through which this particular copy of the Route Request has been forwarded. This route record is initialized to an empty list by the initiator of the Route Discovery. In this example, the route record initially lists only node A.
Routeディスカバリーを開始するために、ノードAは単一のローカル放送パケットとしての「ルート要求」Aを伝えます、この例にノードBを含んでいて。パケットは現在、放送の中のすべてのノードが及ぶ(approximately)によって受け取られます。 各Route RequestはRouteディスカバリーの創始者と目標を特定して、また、Requestの創始者によって決定されたユニークな要求識別(この例の2)を含んでいます。 また、各Route RequestはRoute Requestのこの特定のコピーが進められたそれぞれの中間的ノードのアドレスを記載する記録を含んでいます。 このルート記録はRouteディスカバリーの創始者によって空のリストに初期化されます。 この例では、ルート記録は初めは、ノードAだけをリストアップします。
When another node receives this Route Request (such as node B in this example), if it is the target of the Route Discovery, it returns a "Route Reply" to the initiator of the Route Discovery, giving a copy of the accumulated route record from the Route Request; when the initiator receives this Route Reply, it caches this route in its Route Cache for use in sending subsequent packets to this destination.
別のノードがそれがRouteディスカバリーの目標であるならこのRoute Request(この例のノードBなどの)を受けるとき、「ルート回答」をRouteディスカバリーの創始者に返します、Route Requestから蓄積されたルート記録のコピーを与えて。 創始者がこのRoute Replyを受け取るとき、それは送付のその後のパケットにおける使用のためにRoute Cacheのこのルートをこの目的地にキャッシュします。
Johnson, et al. Experimental [Page 10] RFC 4728 The Dynamic Source Routing Protocol February 2007
ジョンソン、他 ダイナミックな実験的な[10ページ]RFC4728のソースルーティング・プロトコル2007年2月
Otherwise, if this node receiving the Route Request has recently seen another Route Request message from this initiator bearing this same request identification and target address, or if this node's own address is already listed in the route record in the Route Request, this node discards the Request. (A node considers a Request recently seen if it still has information about that Request in its Route Request Table, which is described in Section 4.3.) Otherwise, this node appends its own address to the route record in the Route Request and propagates it by transmitting it as a local broadcast packet (with the same request identification). In this example, node B broadcast the Route Request, which is received by node C; nodes C and D each also, in turn, broadcast the Request, resulting in receipt of a copy of the Request by node E.
さもなければ、Route Requestを受けるこのノードが最近この同じ要求識別とあて先アドレスを示すこの創始者から別のRoute Requestメッセージを見たか、またはこのノードの自己のアドレスがRoute Requestでのルート記録に既に記載されるなら、このノードはRequestを捨てます。 (ノードは、それがRoute Request TableにまだそのRequestの情報を持っているならRequestが最近見られると考えます。)Route Request Tableはセクション4.3で説明されます。 さもなければ、このノードは、Route Requestでのルート記録にそれ自身のアドレスを追加して、ローカル放送パケット(同じ要求識別がある)としてそれを伝えることによって、それを伝播します。 この例では、ノードBはRoute Requestを放送しました。(Route RequestはノードCによって受け取られます)。 また、ノードCとDはそれぞれ順番にRequestを放送します、Requestのコピーを受け取ってノードEでなって。
In returning the Route Reply to the initiator of the Route Discovery, such as in this example, node E replying back to node A, node E will typically examine its own Route Cache for a route back to A and, if one is found, will use it for the source route for delivery of the packet containing the Route Reply. Otherwise, E SHOULD perform its own Route Discovery for target node A, but to avoid possible infinite recursion of Route Discoveries, it MUST in this case piggyback this Route Reply on the packet containing its own Route Request for A. It is also possible to piggyback other small data packets, such as a TCP SYN packet [RFC793], on a Route Request using this same mechanism.
ノードAに応じて戻りながらこの例、ノードEなどのRouteディスカバリーの創始者にRoute Replyを返す際に、ノードEは、ルートがないかどうかそれ自身のRoute CacheをAに通常調べて戻して、1つが見つけられると、Route Replyを含むパケットの配送のための送信元経路にそれを使用するでしょう。 さもなければ、E SHOULDは目標ノードAのためにそれ自身のRouteディスカバリーを実行しますが、A.のためのそれ自身のRoute Requestを含んでいて、Route Discoveriesの可能な無限の再帰を避けるために、それはこの場合パケットの上でこのRoute Replyを背負わなければなりません。また、Itも他の小さいデータ・パケットを背負うのにおいて可能です、TCP SYNパケット[RFC793]のように、この同じメカニズムを使用するRoute Requestで。
Node E could instead simply reverse the sequence of hops in the route record that it is trying to send in the Route Reply and use this as the source route on the packet carrying the Route Reply itself. For MAC protocols, such as IEEE 802.11, that require a bidirectional frame exchange for unicast packets as part of the MAC protocol [IEEE80211], the discovered source route MUST be reversed in this way to return the Route Reply, since this route reversal tests the discovered route to ensure that it is bidirectional before the Route Discovery initiator begins using the route. This route reversal also avoids the overhead of a possible second Route Discovery.
ノードEは、Route Reply自身を運びながら、代わりにRoute Replyを送ろうとしているというルート記録で単にホップの系列を逆にして、パケットの上の送信元経路としてこれを使用するかもしれません。 MACプロトコル[IEEE80211]の一部としてユニキャストパケットへの双方向のフレーム交換を必要とするIEEE802.11などのMACプロトコルにおいて発見された送信元経路をRoute Replyを返すこのように逆にしなければなりません、このルート反転が確実にRouteディスカバリー創始者がルートを使用し始める前に双方向になるようにするために発見されたルートをテストするので。 また、このルート反転は第2の可能なRouteディスカバリーのオーバーヘッドを避けます。
When initiating a Route Discovery, the sending node saves a copy of the original packet (that triggered the discovery) in a local buffer called the "Send Buffer". The Send Buffer contains a copy of each packet that cannot be transmitted by this node because it does not yet have a source route to the packet's destination. Each packet in the Send Buffer is logically associated with the time that it was placed into the Send Buffer and is discarded after residing in the Send Buffer for some timeout period SendBufferTimeout; if necessary for preventing the Send Buffer from overflowing, a FIFO or other replacement strategy MAY also be used to evict packets even before they expire.
Routeディスカバリーを開始するとき、送付ノードは「よりもみ皮製で、発信してください」と呼ばれるローカルのバッファで謄本パケット(それは発見の引き金となった)を救います。 Send Bufferはまだパケットの目的地に送信元経路を持っていないのでこのノードで伝えることができないそれぞれのパケットのコピーを含んでいます。 Send BufferのそれぞれのパケットはそれがSend Bufferに置かれて、いつかのタイムアウト時間SendBufferTimeoutの間、Send Bufferに住んだ後に捨てられる時間に論理的に関連しています。 また、必要なら、Send Bufferがあふれるのを防ぐのにおいて、先入れ先出し法か他の置換促進戦略が、期限が切れる前にさえパケットを追い立てるのに使用されるかもしれません。
Johnson, et al. Experimental [Page 11] RFC 4728 The Dynamic Source Routing Protocol February 2007
ジョンソン、他 ダイナミックな実験的な[11ページ]RFC4728のソースルーティング・プロトコル2007年2月
While a packet remains in the Send Buffer, the node SHOULD occasionally initiate a new Route Discovery for the packet's destination address. However, the node MUST limit the rate at which such new Route Discoveries for the same address are initiated (as described in Section 4.3), since it is possible that the destination node is not currently reachable. In particular, due to the limited wireless transmission range and the movement of the nodes in the network, the network may at times become partitioned, meaning that there is currently no sequence of nodes through which a packet could be forwarded to reach the destination. Depending on the movement pattern and the density of nodes in the network, such network partitions may be rare or common.
パケットがSend Bufferに残っている間、ノードSHOULDはパケットの送付先アドレスのために時折新しいRouteディスカバリーを開始します。 しかしながら、ノードは同じアドレスのためのそのような新しいRoute Discoveriesが開始されるレートを制限しなければなりません(セクション4.3で説明されるように)、目的地ノードが現在届いていないのが、可能であるので。 限られた放送範囲とネットワークでのノードの運動のため、特に、ネットワークは時には仕切られるようになるかもしれません、現在、目的地に達するようにパケットを進めることができたノードの系列が全くない意味。 ネットワークにおける、動作パターンとノードの密度によって、そのようなネットワークパーティションは、まれであるか、または一般的であるかもしれません。
If a new Route Discovery was initiated for each packet sent by a node in such a partitioned network, a large number of unproductive Route Request packets would be propagated throughout the subset of the ad hoc network reachable from this node. In order to reduce the overhead from such Route Discoveries, a node SHOULD use an exponential back-off algorithm to limit the rate at which it initiates new Route Discoveries for the same target, doubling the timeout between each successive discovery initiated for the same target. If the node attempts to send additional data packets to this same destination node more frequently than this limit, the subsequent packets SHOULD be buffered in the Send Buffer until a Route Reply is received giving a route to this destination, but the node MUST NOT initiate a new Route Discovery until the minimum allowable interval between new Route Discoveries for this target has been reached. This limitation on the maximum rate of Route Discoveries for the same target is similar to the mechanism required by Internet nodes to limit the rate at which ARP Requests are sent for any single target IP address [RFC1122].
新しいRouteディスカバリーがそのような仕切られたネットワークにおけるノードによって送られた各パケットのために開始されるなら、多くの非生産的なRoute Requestパケットがこのノードから届いている臨時のネットワークの部分集合中で伝播されるでしょうに。 オーバーヘッドを下げるには、そのようなRoute Discoveries、SHOULDが指数の下に後部アルゴリズムを使用するノードから、それが同じ目標のために新しいRoute Discoveriesを開始するレートを制限してください、同じ目標のために開始されたそれぞれの連続した発見の間のタイムアウトを倍にして。 この限界、その後のパケットSHOULDより頻繁にこの同じ目的地ノードに追加データ・パケットを送るノード試みであるなら、Route Replyがこの目的地にルートを与えるのにおいて受け取られていますが、この目標のための新しいRoute Discoveriesの最小の許容間隔に達するまでノードが新しいRouteディスカバリーを開始してはいけないまで、Send Bufferでバッファリングされてください。 同じ目標のためのRoute Discoveriesの最高率におけるこの制限はインターネット接続装置がARP Requestsがどんなただ一つの目標IPアドレス[RFC1122]のためにも送られるレートを制限しなければならなかったメカニズムと同様です。
3.2. Basic DSR Route Maintenance
3.2. 基本的なDSRルート維持
When originating or forwarding a packet using a source route, each node transmitting the packet is responsible for confirming that data can flow over the link from that node to the next hop. For example, in the situation shown below, node A has originated a packet for node E using a source route through intermediate nodes B, C, and D:
送信元経路を使用することでパケットを溯源するか、または進めるとき、データがそのノードから次のホップへのリンクの上に流れることができると確認するのにパケットを伝えるそれぞれのノードは原因となります。 例えば、以下の状況で、ノードAはノードEのために中間的ノードB、C、およびDを通して送信元経路を使用することでパケットを溯源しました:
+-----+ +-----+ +-----+ +-----+ +-----+
| A |---->| B |---->| C |-->? | D | | E |
+-----+ +-----+ +-----+ +-----+ +-----+
+-----+ +-----+ +-----+ +-----+ +-----+ | A|、-、-、--、>| B|、-、-、--、>| C|-->? | D| | E| +-----+ +-----+ +-----+ +-----+ +-----+
In this case, node A is responsible for the link from A to B, node B is responsible for the link from B to C, node C is responsible for the link from C to D, and node D is responsible for the link from D to E.
この場合、ノードAはAからBへのリンクに原因となります、そして、ノードBはBからCへのリンクに原因となります、そして、ノードCはCからDへのリンクに原因となります、そして、ノードDはDからEへのリンクに原因となります。
Johnson, et al. Experimental [Page 12] RFC 4728 The Dynamic Source Routing Protocol February 2007
ジョンソン、他 ダイナミックな実験的な[12ページ]RFC4728のソースルーティング・プロトコル2007年2月
An acknowledgement can provide confirmation that a link is capable of carrying data, and in wireless networks, acknowledgements are often provided at no cost, either as an existing standard part of the MAC protocol in use (such as the link-layer acknowledgement frame defined by IEEE 802.11 [IEEE80211]), or by a "passive acknowledgement" [JUBIN87] (in which, for example, B confirms receipt at C by overhearing C transmit the packet when forwarding it on to D).
承認はリンクが運ぶことができる確認にデータを提供できます、そして、使用(IEEE802.11[IEEE80211]によって定義されたリンクレイヤ承認フレームなどの)でのMACプロトコルの既存の標準部品、または「受け身の承認」[JUBIN87](それをDに送るとき、Cがパケットを伝えると立ち聞きすることによって、例えば、BはそこでCで領収書を確認する)でワイヤレス・ネットワークに、承認を無料でしばしば提供します。
If a built-in acknowledgement mechanism is not available, the node transmitting the packet can explicitly request that a DSR-specific software acknowledgement be returned by the next node along the route; this software acknowledgement will normally be transmitted directly to the sending node, but if the link between these two nodes is unidirectional (Section 4.6), this software acknowledgement could travel over a different, multi-hop path.
内蔵の承認メカニズムが利用可能でないなら、パケットを伝えるノードは、DSR特有のソフトウェア承認がルートに沿った次のノードによって返されるよう明らかに要求できます。 このソフトウェア承認は通常直接送付ノードに伝えられるでしょうが、これらの2つのノードの間のリンクが単方向(セクション4.6)であるなら、このソフトウェア承認は異なったマルチホップ経路の上を移動するかもしれません。
After an acknowledgement has been received from some neighbor, a node MAY choose not to require acknowledgements from that neighbor for a brief period of time, unless the network interface connecting a node to that neighbor always receives an acknowledgement in response to unicast traffic.
隣人から承認を受けた後に、ノードは、簡潔な期間の間、その隣人から承認を必要としないのを選ぶかもしれません、その隣人にノードを接続するネットワーク・インターフェースがいつもユニキャスト交通に対応して承認を受けるというわけではないなら。
When a software acknowledgement is used, the acknowledgement request SHOULD be retransmitted up to a maximum number of times. A retransmission of the acknowledgement request can be sent as a separate packet, piggybacked on a retransmission of the original data packet, or piggybacked on any packet with the same next-hop destination that does not also contain a software acknowledgement.
ソフトウェア承認が使用されているとき、承認は、SHOULDが最大数の倍まで再送されるよう要求します。 承認要求の「再-トランスミッション」を別々のパケットとして送るか、オリジナルのデータ・パケットの「再-トランスミッション」で便乗するか、またはどんなパケットの上でもまた、ソフトウェア承認を含まないのと同じ次のホップの目的地で背負うことができます。
After the acknowledgement request has been retransmitted the maximum number of times, if no acknowledgement has been received, then the sender treats the link to this next-hop destination as currently "broken". It SHOULD remove this link from its Route Cache and SHOULD return a "Route Error" to each node that has sent a packet routed over that link since an acknowledgement was last received. For example, in the situation shown above, if C does not receive an acknowledgement from D after some number of requests, it would return a Route Error to A, as well as any other node that may have used the link from C to D since C last received an acknowledgement from D. Node A then removes this broken link from its cache; any retransmission of the original packet can be performed by upper layer protocols such as TCP, if necessary. For sending such a retransmission or other packets to this same destination E, if A has in its Route Cache another route to E (for example, from additional Route Replies from its earlier Route Discovery, or from having overheard sufficient routing information from other packets), it can
承認要求を再送した後に、回承認でないなら最大数を受け取って、次に、送付者は現在「壊される」ようにこの次のホップの目的地へのリンクを扱います。 それ、SHOULDはRoute Cacheからこのリンクを取り外して、SHOULDは最後に承認を受けて以来そのリンクの上に発送されたパケットを送った各ノードに「ルート誤り」を返します。 例えば、Cが何らかの数の要求の後にDから承認を受けないなら、上の状況で、Route ErrorをAに返すでしょう、次に、Cが最後にD.Nodeから承認を受けて以来CからDへのリンクを使用したかもしれないいかなる他のノードと同様に、Aはキャッシュからこのリンク切れを取り外します。 必要なら、TCPなどの上側の層のプロトコルはオリジナルのパケットのどんな「再-トランスミッション」も実行できます。 AがRoute Cacheに別のルートをE(例えば以前のRouteディスカバリーからの追加Route Repliesか、他のパケットから十分なルーティング情報を立ち聞きしたことから)まで持っているならそのような「再-トランスミッション」か他のパケットをこの同じ目的地Eに送るために、それはそうすることができます。
Johnson, et al. Experimental [Page 13] RFC 4728 The Dynamic Source Routing Protocol February 2007
ジョンソン、他 ダイナミックな実験的な[13ページ]RFC4728のソースルーティング・プロトコル2007年2月
send the packet using the new route immediately. Otherwise, it SHOULD perform a new Route Discovery for this target (subject to the back-off described in Section 3.1).
すぐに新しいルートを使用することでパケットを送ってください。 そうでなければ、それ、SHOULDはこの目標(下にセクション3.1で説明された後部を条件とした)のために新しいRouteディスカバリーを実行します。
3.3. Additional Route Discovery Features
3.3. 追加ルート発見機能
3.3.1. Caching Overheard Routing Information
3.3.1. キャッシュは経路情報を立ち聞きしました。
A node forwarding or otherwise overhearing any packet SHOULD add all usable routing information from that packet to its own Route Cache. The usefulness of routing information in a packet depends on the directionality characteristics of the physical medium (Section 2), as well as on the MAC protocol being used. Specifically, three distinct cases are possible:
どんなパケットSHOULDもそのパケットからそれ自身のRoute Cacheにすべての使用可能なルーティング情報を加えると進めるか、またはそうでなければ立ち聞きするノード。 パケットのルーティング情報の有用性は物理的な媒体(セクション2)の方向性の特性と、そして、使用されるMACプロトコルに依存します。 明確に、3つの異なったケースが可能です:
- Links in the network frequently are capable of operating only
unidirectionally (not bidirectionally), and the MAC protocol in
use in the network is capable of transmitting unicast packets over
unidirectional links.
- ネットワークにおけるリンクは頻繁に単方向(双方向でない)だけに作動できます、そして、ネットワークで使用でのMACプロトコルは単方向のリンクの上にユニキャストパケットを伝えることができます。
- Links in the network occasionally are capable of operating only
unidirectionally (not bidirectionally), but this unidirectional
restriction on any link is not persistent; almost all links are
physically bidirectional, and the MAC protocol in use in the
network is capable of transmitting unicast packets over
unidirectional links.
- ネットワークにおけるリンクは時折単方向(双方向でない)だけに作動できますが、どんなリンクにおけるこの単方向の制限はしつこくはありません。 ほとんどすべてのリンクが物理的に双方向です、そして、ネットワークで使用でのMACプロトコルは単方向のリンクの上にユニキャストパケットを伝えることができます。
- The MAC protocol in use in the network is not capable of
transmitting unicast packets over unidirectional links; only
bidirectional links can be used by the MAC protocol for
transmitting unicast packets. For example, the IEEE 802.11
Distributed Coordination Function (DCF) MAC protocol [IEEE80211]
is capable of transmitting a unicast packet only over a
bidirectional link, since the MAC protocol requires the return of
a link-level acknowledgement packet from the receiver and also
optionally requires the bidirectional exchange of an RTS and CTS
packet between the transmitter and receiver nodes.
- ネットワークで使用でのMACプロトコルは単方向のリンクの上にユニキャストパケットを伝えることができません。 MACプロトコルは、ユニキャストパケットを伝えるのに双方向のリンクしか使用できません。 例えば、IEEE802.11Distributed Coordination Function(DCF)MACプロトコル[IEEE80211]は双方向のリンクだけの上にユニキャストパケットを伝えることができます、MACプロトコルが受信機からリンク・レベル確認応答パケットの復帰を必要として、また、送信機と受信機ノードの間で任意にRTSとCTSパケットのバイディレクショナル変換を必要とするので。
In the first case above, for example, the source route used in a data packet, the accumulated route record in a Route Request, or the route being returned in a Route Reply SHOULD all be cached by any node in the "forward" direction. Any node SHOULD cache this information from any such packet received, whether the packet was addressed to this node, sent to a broadcast (or multicast) MAC address, or overheard while the node's network interface is in promiscuous mode. However, the "reverse" direction of the links identified in such packet headers SHOULD NOT be cached.
送信元経路は前者の場合上に、例えば、記録がRoute Requestでデータ・パケット、蓄積されたルートで使用されたか、またはRoute Reply SHOULDで返されるルートを使用されました。「前方」という指示のどんなノードによってもすべてキャッシュされます。 どんなノードSHOULDもパケットが放送(または、マルチキャスト)MACアドレスに送られたこのノードに記述されたか否かに関係なく、受け取るか、ノードのネットワーク・インターフェースが無差別なモードでありますが、または立ち聞きするどんなそのようなパケットからのこの情報もキャッシュします。 しかしながら、リンクの「逆」指示はそのようなパケットのヘッダーでSHOULD NOTを特定しました。キャッシュされます。
Johnson, et al. Experimental [Page 14] RFC 4728 The Dynamic Source Routing Protocol February 2007
ジョンソン、他 ダイナミックな実験的な[14ページ]RFC4728のソースルーティング・プロトコル2007年2月
For example, in the situation shown below, node A is using a source route to communicate with node E:
例えば、以下の状況で、ノードAはノードEとコミュニケートするのに送信元経路を使用しています:
+-----+ +-----+ +-----+ +-----+ +-----+
| A |---->| B |---->| C |---->| D |---->| E |
+-----+ +-----+ +-----+ +-----+ +-----+
+-----+ +-----+ +-----+ +-----+ +-----+ | A|、-、-、--、>| B|、-、-、--、>| C|、-、-、--、>| D|、-、-、--、>| E| +-----+ +-----+ +-----+ +-----+ +-----+
As node C forwards a data packet along the route from A to E, it SHOULD add to its cache the presence of the "forward" direction links that it learns from the headers of these packets, from itself to D and from D to E. Node C SHOULD NOT, in this case, cache the "reverse" direction of the links identified in these packet headers, from itself back to B and from B to A, since these links might be unidirectional.
ノードとして、Cはルートに沿ってAからEまでデータ・パケットを進めます、それ。SHOULDはそれがこれらのパケットのヘッダーから学ぶ「前進」の指示リンクの存在をキャッシュに加えます、それ自体からDまでDからE.Node C SHOULD NOTまで、この場合、リンクの「逆」の指示がこれらのパケットのヘッダーで特定したキャッシュ、それ自体からBまでBからAまで、これらのリンクが単方向であるかもしれないので。
In the second case above, in which links may occasionally operate unidirectionally, the links described above SHOULD be cached in both directions. Furthermore, in this case, if node X overhears (e.g., through promiscuous mode) a packet transmitted by node C that is using a source route from node A to E, node X SHOULD cache all of these links as well, also including the link from C to X over which it overheard the packet.
どのリンクが時折単方向、作動するかもしれないかのSHOULDの上で説明されたリンクの上の2番目の場合では、両方の方向にキャッシュされてください。 その上、ノードXがノードAからEまで送信元経路を使用しているノードCによって伝えられたパケットを立ち聞きするなら(例えば、無差別なモードで)、この場合ノードX SHOULDはまた、これらのリンクのすべてをキャッシュします、また、Cからそれがパケットを立ち聞きしたXへのリンクを含んでいて。
In the final case, in which the MAC protocol requires physical bidirectionality for unicast operation, links from a source route SHOULD be cached in both directions, except when the packet also contains a Route Reply, in which case only the links already traversed in this source route SHOULD be cached. However, the links not yet traversed in this route SHOULD NOT be cached.
最終的な場合では、またパケットがRoute Replyを含む時を除いて、ソースルートSHOULDからのリンクが両方の方向にキャッシュされて、リンクがこのソースルートSHOULDで既にどのケースだけを横断したかでキャッシュされてください。(MACプロトコルはそれでユニキャスト操作に、双方向性な身体検査を必要とします)。 しかしながら、リンクはこのルートでまだSHOULD NOTを横断していませんでした。キャッシュされます。
3.3.2. Replying to Route Requests Using Cached Routes
3.3.2. キャッシュされたルートを使用することでルート要求に答えます。
A node receiving a Route Request for which it is not the target searches its own Route Cache for a route to the target of the Request. If it is found, the node generally returns a Route Reply to the initiator itself rather than forward the Route Request. In the Route Reply, this node sets the route record to list the sequence of hops over which this copy of the Route Request was forwarded to it, concatenated with the source route to this target obtained from its own Route Cache.
それが目標でないRoute Requestを受けるノードはRequestの目標へのルートとしてそれ自身のRoute Cacheを捜します。 それが見つけられるなら、一般に、ノードはRoute Requestを進めるよりむしろRoute Replyを創始者自身に返します。 Route Replyでは、このノードはRoute Requestのこのコピーがそれに送られたホップの系列を記載するために記録的で、送信元経路でそれ自身のRoute Cacheから入手されたこの目標に連結されたルートを設定します。
However, before transmitting a Route Reply packet that was generated using information from its Route Cache in this way, a node MUST verify that the resulting route being returned in the Route Reply, after this concatenation, contains no duplicate nodes listed in the route record. For example, the figure below illustrates a case in which a Route Request for target E has been received by node F, and node F already has in its Route Cache a route from itself to E:
しかしながら、Route Cacheから情報を使用することで発生したRoute Replyパケットをこのように伝える前に、ノードは、この連結の後にRoute Replyで返される結果として起こるルートがルート記録にリストアップされなかった写しノードを全く含むことを確かめなければなりません。 例えば、以下の図は目標EのためのRoute RequestがノードFによって受け取られた場合を例証します、そして、ノードFはRoute Cacheにそれ自体からEまで既にルートを持ちます:
Johnson, et al. Experimental [Page 15] RFC 4728 The Dynamic Source Routing Protocol February 2007
ジョンソン、他 ダイナミックな実験的な[15ページ]RFC4728のソースルーティング・プロトコル2007年2月
+-----+ +-----+ +-----+ +-----+
| A |---->| B |- >| D |---->| E |
+-----+ +-----+ \ / +-----+ +-----+
\ /
\ +-----+ /
>| C |-
+-----+
| ^
v |
Route Request +-----+
Route: A - B - C - F | F | Cache: C - D - E
+-----+
+-----+ +-----+ +-----+ +-----+ | A|、-、-、--、>| B|- >| D|、-、-、--、>| E| +-----+ +-----+ \ / +-----+ +-----+ \ / \ +-----+ / >| C|- +-----+ | ^v| ルート要求+-----+ ルート: A--B--C--F| F| 以下をキャッシュしてください。 C--D--E+-----+
The concatenation of the accumulated route record from the Route Request and the cached route from F's Route Cache would include a duplicate node in passing from C to F and back to C.
Route Requestからの蓄積されたルート記録とFのRoute Cacheからのキャッシュされたルートの連結はCからFまでCに行き帰り通る際に写しノードを含んでいるでしょう。
Node F in this case could attempt to edit the route to eliminate the duplication, resulting in a route from A to B to C to D and on to E, but in this case, node F would not be on the route that it returned in its own Route Reply. DSR Route Discovery prohibits node F from returning such a Route Reply from its cache; this prohibition increases the probability that the resulting route is valid, since node F in this case should have received a Route Error if the route had previously stopped working. Furthermore, this prohibition means that a future Route Error traversing the route is very likely to pass through any node that sent the Route Reply for the route (including node F), which helps to ensure that stale data is removed from caches (such as at F) in a timely manner; otherwise, the next Route Discovery initiated by A might also be contaminated by a Route Reply from F containing the same stale route. If, due to this restriction on returning a Route Reply based on information from its Route Cache, node F does not return such a Route Reply, it propagates the Route Request normally.
この場合、ノードFは、複製を排除するためにルートを編集するのを試みるかもしれなくて、CへのAからBまでのルートをもたらして、それがそれ自身のところで返したルートの上にDと、そして、しかし、E、この場合ノードFに、Route Replyがないでしょう。 DSR RouteディスカバリーはキャッシュからそのようなRoute Replyを返すのからノードFを禁じます。 この禁止は結果として起こるルートが有効であるという確率を増加させます、ルートが以前に仕事を中止したならこの場合、ノードFがRoute Errorを受けたので。 その上、この禁止は、ルートを横断する将来のRoute Errorが聞き古したデータがキャッシュ(Fなどの)から直ちに取り除かれるのを保証するのを助けるルート(ノードFを含んでいる)にRoute Replyを送ったどんなノードも非常に通り抜けそうを意味します。 さもなければ、また、同じ聞き古したルートを含んでいて、Aによって開始された次のRouteディスカバリーはRoute ReplyによってFから汚染されるかもしれません。 ノードFがRoute Cacheから情報に基づくRoute Replyを返すときのこの制限のためそのようなRoute Replyを返さないなら、通常、それはRoute Requestを伝播します。
3.3.3. Route Request Hop Limits
3.3.3. ルート要求ホップ限界
Each Route Request message contains a "hop limit" that may be used to limit the number of intermediate nodes allowed to forward that copy of the Route Request. This hop limit is implemented using the Time- to-Live (TTL) field in the IP header of the packet carrying the Route Request. As the Request is forwarded, this limit is decremented, and the Request packet is discarded if the limit reaches zero before finding the target. This Route Request hop limit can be used to implement a variety of algorithms for controlling the spread of a Route Request during a Route Discovery attempt.
それぞれのRoute RequestメッセージはRoute Requestのそのコピーを進めることができた中間的ノードの数を制限するのに使用されるかもしれない「ホップ限界」を含んでいます。 このホップ限界がTimeを使用することで実行される、-生きてください、(TTL)はパケット携帯のIPヘッダーでRoute Requestをさばきます。 Requestを進めるのに従って、この限界は減少します、そして、目標を見つける前に限界がゼロに達するなら、Requestパケットは捨てられます。 Routeディスカバリー試みの間、Route Requestの普及を制御するためのさまざまなアルゴリズムを実行するのにこのRoute Requestホップ限界を使用できます。
Johnson, et al. Experimental [Page 16] RFC 4728 The Dynamic Source Routing Protocol February 2007
ジョンソン、他 ダイナミックな実験的な[16ページ]RFC4728のソースルーティング・プロトコル2007年2月
For example, a node MAY use this hop limit to implement a "non- propagating" Route Request as an initial phase of a Route Discovery. A node using this technique sends its first Route Request attempt for some target node using a hop limit of 1, such that any node receiving the initial transmission of the Route Request will not forward the Request to other nodes by re-broadcasting it. This form of Route Request is called a "non-propagating" Route Request; it provides an inexpensive method for determining if the target is currently a neighbor of the initiator or if a neighbor node has a route to the target cached (effectively using the neighbors' Route Caches as an extension of the initiator's own Route Cache). If no Route Reply is received after a short timeout, then the node sends a "propagating" Route Request for the target node (i.e., with hop limit as defined by the value of the DiscoveryHopLimit configuration variable).
例えば、ノードは、Routeディスカバリーの初期位相として「非伝播」Route Requestを実行するのにこのホップ限界を使用するかもしれません。 このテクニックを使用するノードは1のホップ限界を使用することで何らかの目標ノードのための最初のRoute Request試みを送ります、Route Requestの初期のトランスミッションを受けるどんなノードもそれを再放送することによって他のノードにRequestを送らないように。 Route Requestのこのフォームは「非伝播」Route Requestと呼ばれます。 それは現在、目標が創始者の隣接物であるかどうかかそれとも隣人ノードで目標へのルートをキャッシュするかどうか(事実上、創始者の自身のRoute Cacheの拡大として隣人のRoute Cachesを使用して)決定するための安価な方法を提供します。 短いタイムアウトの後にRoute Replyを全く受け取らないなら、ノードは目標ノード(すなわち、DiscoveryHopLimit構成変数の値によって定義されるホップ限界がある)のために「伝播」Route Requestを送ります。
As another example, a node MAY use this hop limit to implement an "expanding ring" search for the target [JOHNSON96a]. A node using this technique sends an initial non-propagating Route Request as described above; if no Route Reply is received for it, the node originates another Route Request with a hop limit of 2. For each Route Request originated, if no Route Reply is received for it, the node doubles the hop limit used on the previous attempt, to progressively explore for the target node without allowing the Route Request to propagate over the entire network. However, this expanding ring search approach could increase the average latency of Route Discovery, since multiple Discovery attempts and timeouts may be needed before discovering a route to the target node.
別の例として、ノードは、目標[JOHNSON96a]の「拡張リング」検索を実行するのにこのホップ限界を使用するかもしれません。 このテクニックを使用するノードは上で説明されるように初期の非伝播Route Requestを送ります。 それのためにRoute Replyを全く受け取らないなら、ノードは2のホップ限界で別のRoute Requestを溯源します。 それのためにRoute Replyを全く受け取らないなら溯源する各Route Requestに関しては、ノードは前の試みのときにRoute Requestが全体のネットワークの上で伝播するのを許容しない目標ノードのために次第に探検するのに使用されたホップ限界を倍にします。 しかしながら、この拡張リング検索アプローチはRouteディスカバリーの平均した潜在を高めるかもしれません、目標ノードにルートを発見する前に複数のディスカバリー試みとタイムアウトが必要であるかもしれないので。
3.4. Additional Route Maintenance Features
3.4. 追加ルート維持機能
3.4.1. Packet Salvaging
3.4.1. パケットサルベージ
When an intermediate node forwarding a packet detects through Route Maintenance that the next hop along the route for that packet is broken, if the node has another route to the packet's destination in its Route Cache, the node SHOULD "salvage" the packet rather than discard it. To salvage a packet, the node replaces the original source route on the packet with a route from its Route Cache. The node then forwards the packet to the next node indicated along this source route. For example, in the situation shown in the example of Section 3.2, if node C has another route cached to node E, it can salvage the packet by replacing the original route in the packet with this new route from its own Route Cache rather than discarding the packet.
ノードであるなら壊されて、パケットがそのパケットのためのルートに沿った次のホップがそうであるRoute Maintenanceを通して検出する中間的ノード推進がRoute Cacheにパケットの目的地に別のルートを持っているとき、ノードSHOULDはそれを捨てるよりむしろパケットを「救助します」。 パケットを回収するために、ノードはパケットの上の一次資料ルートをRoute Cacheからルートに置き換えます。 そして、ノードはこの送信元経路に沿って示された次のノードにパケットを送ります。 例えば、セクション3.2に関する例の状況で、ノードCでノードEに別のルートをキャッシュするなら、それは、パケットを捨てるよりパケットの元のルートをそれ自身のRoute Cacheからこの新しいルートにむしろ取り替えることによって、パケットを回収できます。
When salvaging a packet, a count is maintained in the packet of the number of times that it has been salvaged, to prevent a single packet from being salvaged endlessly. Otherwise, since the TTL is
パケットを回収するとき、カウントはそれが単一のパケットが際限なく回収されるのを防ぐために回収されたという回の数のパケットで維持されます。 別の方法で、TTLはそうです。
Johnson, et al. Experimental [Page 17] RFC 4728 The Dynamic Source Routing Protocol February 2007
ジョンソン、他 ダイナミックな実験的な[17ページ]RFC4728のソースルーティング・プロトコル2007年2月
decremented only once by each node, a single node could salvage a packet an unbounded number of times. Even if we chose to require the TTL to be decremented on each salvage attempt, packet salvaging is an expensive operation, so it is desirable to bound the maximum number of times a packet can be salvaged independently of the maximum number of hops a packet can traverse.
decremented only once by each node, a single node could salvage a packet an unbounded number of times. Even if we chose to require the TTL to be decremented on each salvage attempt, packet salvaging is an expensive operation, so it is desirable to bound the maximum number of times a packet can be salvaged independently of the maximum number of hops a packet can traverse.
As described in Section 3.2, an intermediate node, such as in this case, that detects through Route Maintenance that the next hop along the route for a packet that it is forwarding is broken, the node also SHOULD return a Route Error to the original sender of the packet, identifying the link over which the packet could not be forwarded. If the node sends this Route Error, it SHOULD originate the Route Error before salvaging the packet.
As described in Section 3.2, an intermediate node, such as in this case, that detects through Route Maintenance that the next hop along the route for a packet that it is forwarding is broken, the node also SHOULD return a Route Error to the original sender of the packet, identifying the link over which the packet could not be forwarded. If the node sends this Route Error, it SHOULD originate the Route Error before salvaging the packet.
3.4.2. Queued Packets Destined over a Broken Link
3.4.2. Queued Packets Destined over a Broken Link
When an intermediate node forwarding a packet detects through Route Maintenance that the next-hop link along the route for that packet is broken, in addition to handling that packet as defined for Route Maintenance, the node SHOULD also handle in a similar way any pending packets that it has queued that are destined over this new broken link. Specifically, the node SHOULD search its Network Interface Queue and Maintenance Buffer (Section 4.5) for packets for which the next-hop link is this new broken link. For each such packet currently queued at this node, the node SHOULD process that packet as follows:
When an intermediate node forwarding a packet detects through Route Maintenance that the next-hop link along the route for that packet is broken, in addition to handling that packet as defined for Route Maintenance, the node SHOULD also handle in a similar way any pending packets that it has queued that are destined over this new broken link. Specifically, the node SHOULD search its Network Interface Queue and Maintenance Buffer (Section 4.5) for packets for which the next-hop link is this new broken link. For each such packet currently queued at this node, the node SHOULD process that packet as follows:
- Remove the packet from the node's Network Interface Queue and
Maintenance Buffer.
- Remove the packet from the node's Network Interface Queue and Maintenance Buffer.
- Originate a Route Error for this packet to the original sender of
the packet, using the procedure described in Section 8.3.4, as if
the node had already reached the maximum number of retransmission
attempts for that packet for Route Maintenance. However, in
sending such Route Errors for queued packets in response to
detection of a single, new broken link, the node SHOULD send no
more than one Route Error to each original sender of any of these
packets.
- Originate a Route Error for this packet to the original sender of the packet, using the procedure described in Section 8.3.4, as if the node had already reached the maximum number of retransmission attempts for that packet for Route Maintenance. However, in sending such Route Errors for queued packets in response to detection of a single, new broken link, the node SHOULD send no more than one Route Error to each original sender of any of these packets.
- If the node has another route to the packet's IP Destination
Address in its Route Cache, the node SHOULD salvage the packet as
described in Section 8.3.6. Otherwise, the node SHOULD discard
the packet.
- If the node has another route to the packet's IP Destination Address in its Route Cache, the node SHOULD salvage the packet as described in Section 8.3.6. Otherwise, the node SHOULD discard the packet.
Johnson, et al. Experimental [Page 18] RFC 4728 The Dynamic Source Routing Protocol February 2007
Johnson, et al. Experimental [Page 18] RFC 4728 The Dynamic Source Routing Protocol February 2007
3.4.3. Automatic Route Shortening
3.4.3. Automatic Route Shortening
Source routes in use MAY be automatically shortened if one or more intermediate nodes in the route become no longer necessary. This mechanism of automatically shortening routes in use is somewhat similar to the use of passive acknowledgements [JUBIN87]. In particular, if a node is able to overhear a packet carrying a source route (e.g., by operating its network interface in promiscuous receive mode), then this node examines the unexpended portion of that source route. If this node is not the intended next-hop destination for the packet but is named in the later unexpended portion of the packet's source route, then it can infer that the intermediate nodes before itself in the source route are no longer needed in the route. For example, the figure below illustrates an example in which node D has overheard a data packet being transmitted from B to C, for later forwarding to D and to E:
Source routes in use MAY be automatically shortened if one or more intermediate nodes in the route become no longer necessary. This mechanism of automatically shortening routes in use is somewhat similar to the use of passive acknowledgements [JUBIN87]. In particular, if a node is able to overhear a packet carrying a source route (e.g., by operating its network interface in promiscuous receive mode), then this node examines the unexpended portion of that source route. If this node is not the intended next-hop destination for the packet but is named in the later unexpended portion of the packet's source route, then it can infer that the intermediate nodes before itself in the source route are no longer needed in the route. For example, the figure below illustrates an example in which node D has overheard a data packet being transmitted from B to C, for later forwarding to D and to E:
+-----+ +-----+ +-----+ +-----+ +-----+
| A |---->| B |---->| C | | D | | E |
+-----+ +-----+ +-----+ +-----+ +-----+
\ ^
\ /
---------------------
+-----+ +-----+ +-----+ +-----+ +-----+ | A |---->| B |---->| C | | D | | E | +-----+ +-----+ +-----+ +-----+ +-----+ \ ^ \ / ---------------------
In this case, this node (node D) SHOULD return a "gratuitous" Route Reply to the original sender of the packet (node A). The Route Reply gives the shorter route as the concatenation of the portion of the original source route up through the node that transmitted the overheard packet (node B), plus the suffix of the original source route beginning with the node returning the gratuitous Route Reply (node D). In this example, the route returned in the gratuitous Route Reply message sent from D to A gives the new route as the sequence of hops from A to B to D to E.
In this case, this node (node D) SHOULD return a "gratuitous" Route Reply to the original sender of the packet (node A). The Route Reply gives the shorter route as the concatenation of the portion of the original source route up through the node that transmitted the overheard packet (node B), plus the suffix of the original source route beginning with the node returning the gratuitous Route Reply (node D). In this example, the route returned in the gratuitous Route Reply message sent from D to A gives the new route as the sequence of hops from A to B to D to E.
When deciding whether to return a gratuitous Route Reply in this way, a node MAY factor in additional information beyond the fact that it was able to overhear the packet. For example, the node MAY decide to return the gratuitous Route Reply only when the overheard packet is received with a signal strength or signal-to-noise ratio above some specific threshold. In addition, each node maintains a Gratuitous Route Reply Table, as described in Section 4.4, to limit the rate at which it originates gratuitous Route Replies for the same returned route.
When deciding whether to return a gratuitous Route Reply in this way, a node MAY factor in additional information beyond the fact that it was able to overhear the packet. For example, the node MAY decide to return the gratuitous Route Reply only when the overheard packet is received with a signal strength or signal-to-noise ratio above some specific threshold. In addition, each node maintains a Gratuitous Route Reply Table, as described in Section 4.4, to limit the rate at which it originates gratuitous Route Replies for the same returned route.
Johnson, et al. Experimental [Page 19] RFC 4728 The Dynamic Source Routing Protocol February 2007
Johnson, et al. Experimental [Page 19] RFC 4728 The Dynamic Source Routing Protocol February 2007
3.4.4. Increased Spreading of Route Error Messages
3.4.4. Increased Spreading of Route Error Messages
When a source node receives a Route Error for a data packet that it originated, this source node propagates this Route Error to its neighbors by piggybacking it on its next Route Request. In this way, stale information in the caches of nodes around this source node will not generate Route Replies that contain the same invalid link for which this source node received the Route Error.
When a source node receives a Route Error for a data packet that it originated, this source node propagates this Route Error to its neighbors by piggybacking it on its next Route Request. In this way, stale information in the caches of nodes around this source node will not generate Route Replies that contain the same invalid link for which this source node received the Route Error.
For example, in the situation shown in the example of Section 3.2, node A learns from the Route Error message from C that the link from C to D is currently broken. It thus removes this link from its own Route Cache and initiates a new Route Discovery (if it has no other route to E in its Route Cache). On the Route Request packet initiating this Route Discovery, node A piggybacks a copy of this Route Error, ensuring that the Route Error spreads well to other nodes, and guaranteeing that any Route Reply that it receives (including those from other node's Route Caches) in response to this Route Request does not contain a route that assumes the existence of this broken link.
For example, in the situation shown in the example of Section 3.2, node A learns from the Route Error message from C that the link from C to D is currently broken. It thus removes this link from its own Route Cache and initiates a new Route Discovery (if it has no other route to E in its Route Cache). On the Route Request packet initiating this Route Discovery, node A piggybacks a copy of this Route Error, ensuring that the Route Error spreads well to other nodes, and guaranteeing that any Route Reply that it receives (including those from other node's Route Caches) in response to this Route Request does not contain a route that assumes the existence of this broken link.
3.5. Optional DSR Flow State Extension
3.5. Optional DSR Flow State Extension
This section describes an optional, compatible extension to the DSR protocol, known as "flow state", that allows the routing of most packets without an explicit source route header in the packet. The DSR flow state extension further reduces the overhead of the protocol yet still preserves the fundamental properties of DSR's operation. Once a sending node has discovered a source route such as through DSR's Route Discovery mechanism, the flow state mechanism allows the sending node to establish hop-by-hop forwarding state within the network, based on this source route, to enable each node along the route to forward the packet to the next hop based on the node's own local knowledge of the flow along which this packet is being routed. Flow state is dynamically initialized by the first packet using a source route and is then able to route subsequent packets along the same flow without use of a source route header in the packet. The state established at each hop along a flow is "soft state" and thus automatically expires when no longer needed and can be quickly recreated as necessary. Extending DSR's basic operation based on an explicit source route in the header of each packet routed, the flow state extension operates as a form of "implicit source routing" by preserving DSR's basic operation but removing the explicit source route from packets.
This section describes an optional, compatible extension to the DSR protocol, known as "flow state", that allows the routing of most packets without an explicit source route header in the packet. The DSR flow state extension further reduces the overhead of the protocol yet still preserves the fundamental properties of DSR's operation. Once a sending node has discovered a source route such as through DSR's Route Discovery mechanism, the flow state mechanism allows the sending node to establish hop-by-hop forwarding state within the network, based on this source route, to enable each node along the route to forward the packet to the next hop based on the node's own local knowledge of the flow along which this packet is being routed. Flow state is dynamically initialized by the first packet using a source route and is then able to route subsequent packets along the same flow without use of a source route header in the packet. The state established at each hop along a flow is "soft state" and thus automatically expires when no longer needed and can be quickly recreated as necessary. Extending DSR's basic operation based on an explicit source route in the header of each packet routed, the flow state extension operates as a form of "implicit source routing" by preserving DSR's basic operation but removing the explicit source route from packets.
Johnson, et al. Experimental [Page 20] RFC 4728 The Dynamic Source Routing Protocol February 2007
Johnson, et al. Experimental [Page 20] RFC 4728 The Dynamic Source Routing Protocol February 2007
3.5.1. Flow Establishment
3.5.1. Flow Establishment
A source node sending packets to some destination node MAY use the DSR flow state extension described here to establish a route to that destination as a flow. A "flow" is a route from the source to the destination represented by hop-by-hop forwarding state within the nodes along the route. Each flow is uniquely identified by a combination of the source node address, the destination node address, and a flow identifier (flow ID) chosen by the source node.
A source node sending packets to some destination node MAY use the DSR flow state extension described here to establish a route to that destination as a flow. A "flow" is a route from the source to the destination represented by hop-by-hop forwarding state within the nodes along the route. Each flow is uniquely identified by a combination of the source node address, the destination node address, and a flow identifier (flow ID) chosen by the source node.
Each flow ID is a 16-bit unsigned integer. Comparison between different flow IDs MUST be performed modulo 2**16. For example, using an implementation in the C programming language, a flow ID value (a) is greater than another flow ID value (b) if ((short)((a) - (b)) > 0), if a C language "short" data type is implemented as a 16-bit signed integer.
Each flow ID is a 16-bit unsigned integer. Comparison between different flow IDs MUST be performed modulo 2**16. For example, using an implementation in the C programming language, a flow ID value (a) is greater than another flow ID value (b) if ((short)((a) - (b)) > 0), if a C language "short" data type is implemented as a 16-bit signed integer.
A DSR Flow State header in a packet identifies the flow ID to be followed in forwarding that packet. From a given source to some destination, any number of different flows MAY exist and be in use, for example, following different sequences of hops to reach the destination. One of these flows MAY be considered the "default" flow from that source to that destination. If a node receives a packet with neither a DSR Options header specifying the route to be taken (with a Source Route option in the DSR Options header) nor a DSR Flow State header specifying the flow ID to be followed, it is forwarded along the default flow for the source and destination addresses specified in the packet's IP header.
A DSR Flow State header in a packet identifies the flow ID to be followed in forwarding that packet. From a given source to some destination, any number of different flows MAY exist and be in use, for example, following different sequences of hops to reach the destination. One of these flows MAY be considered the "default" flow from that source to that destination. If a node receives a packet with neither a DSR Options header specifying the route to be taken (with a Source Route option in the DSR Options header) nor a DSR Flow State header specifying the flow ID to be followed, it is forwarded along the default flow for the source and destination addresses specified in the packet's IP header.
In establishing a new flow, the source node generates a nonzero 16-bit flow ID greater than any unexpired flow IDs for this (source, destination) pair. If the source wishes for this flow to become the default flow, the low bit of the flow ID MUST be set (the flow ID is an odd number); otherwise, the low bit MUST NOT be set (the flow ID is an even number).
In establishing a new flow, the source node generates a nonzero 16-bit flow ID greater than any unexpired flow IDs for this (source, destination) pair. If the source wishes for this flow to become the default flow, the low bit of the flow ID MUST be set (the flow ID is an odd number); otherwise, the low bit MUST NOT be set (the flow ID is an even number).
The source node establishing the new flow then transmits a packet containing a DSR Options header with a Source Route option. To establish the flow, the source node also MUST include in the packet a DSR Flow State header, with the Flow ID field set to the chosen flow ID for the new flow, and MUST include a Timeout option in the DSR Options header, giving the lifetime after which state information about this flow is to expire. This packet will generally be a normal data packet being sent from this sender to the destination (for example, the first packet sent after discovering the new route) but is also treated as a "flow establishment" packet.
The source node establishing the new flow then transmits a packet containing a DSR Options header with a Source Route option. To establish the flow, the source node also MUST include in the packet a DSR Flow State header, with the Flow ID field set to the chosen flow ID for the new flow, and MUST include a Timeout option in the DSR Options header, giving the lifetime after which state information about this flow is to expire. This packet will generally be a normal data packet being sent from this sender to the destination (for example, the first packet sent after discovering the new route) but is also treated as a "flow establishment" packet.
Johnson, et al. Experimental [Page 21] RFC 4728 The Dynamic Source Routing Protocol February 2007
Johnson, et al. Experimental [Page 21] RFC 4728 The Dynamic Source Routing Protocol February 2007
The source node records this flow in its Flow Table for future use, setting the TTL in this Flow Table entry to the value used in the TTL field in the packet's IP header and setting the Lifetime in this entry to the lifetime specified in the Timeout option in the DSR Options header. The TTL field is used for Default Flow Forwarding, as described in Sections 3.5.3 and 3.5.4.
The source node records this flow in its Flow Table for future use, setting the TTL in this Flow Table entry to the value used in the TTL field in the packet's IP header and setting the Lifetime in this entry to the lifetime specified in the Timeout option in the DSR Options header. The TTL field is used for Default Flow Forwarding, as described in Sections 3.5.3 and 3.5.4.
Any further packets sent with this flow ID before the timeout that also contain a DSR Options header with a Source Route option MUST use this same source route in the Source Route option.
Any further packets sent with this flow ID before the timeout that also contain a DSR Options header with a Source Route option MUST use this same source route in the Source Route option.
3.5.2. Receiving and Forwarding Establishment Packets
3.5.2. Receiving and Forwarding Establishment Packets
Packets intended to establish a flow, as described in Section 3.5.1, contain a DSR Options header with a Source Route option and are forwarded along the indicated route. A node implementing the DSR flow state extension, when receiving and forwarding such a DSR packet, also keeps some state in its own Flow Table to enable it to forward future packets that are sent along this flow with only the flow ID specified. Specifically, if the packet also contains a DSR Flow State header, this packet SHOULD cause an entry to be established for this flow in the Flow Table of each node along the packet's route.
Packets intended to establish a flow, as described in Section 3.5.1, contain a DSR Options header with a Source Route option and are forwarded along the indicated route. A node implementing the DSR flow state extension, when receiving and forwarding such a DSR packet, also keeps some state in its own Flow Table to enable it to forward future packets that are sent along this flow with only the flow ID specified. Specifically, if the packet also contains a DSR Flow State header, this packet SHOULD cause an entry to be established for this flow in the Flow Table of each node along the packet's route.
The Hop Count field of the DSR Flow State header is also stored in the Flow Table, as is the lifetime specified in the Timeout option specified in the DSR Options header.
The Hop Count field of the DSR Flow State header is also stored in the Flow Table, as is the lifetime specified in the Timeout option specified in the DSR Options header.
If the Flow ID is odd and there is no flow in the Flow Table with Flow ID greater than the received Flow ID, set the default Flow ID for this (IP Source Address, IP Destination Address) pair to the received Flow ID, and the TTL of the packet is recorded.
If the Flow ID is odd and there is no flow in the Flow Table with Flow ID greater than the received Flow ID, set the default Flow ID for this (IP Source Address, IP Destination Address) pair to the received Flow ID, and the TTL of the packet is recorded.
The Flow ID option is removed before final delivery of the packet.
The Flow ID option is removed before final delivery of the packet.
3.5.3. Sending Packets along Established Flows
3.5.3. Sending Packets along Established Flows
When a flow is established as described in Section 3.5.1, a packet is sent that establishes state in each node along the route. This state is soft; that is, the protocol contains mechanisms for recovering from the loss of this state. However, the use of these mechanisms may result in reduced performance for packets sent along flows with forgotten state. As a result, it is desirable to differentiate behavior based on whether or not the sender is reasonably certain that the flow state exists on each node along the route. We define a flow's state to be "established end-to-end" if the Flow Tables of all nodes on the route contains forwarding information for that flow. While it is impossible to detect whether or not a flow's state has
When a flow is established as described in Section 3.5.1, a packet is sent that establishes state in each node along the route. This state is soft; that is, the protocol contains mechanisms for recovering from the loss of this state. However, the use of these mechanisms may result in reduced performance for packets sent along flows with forgotten state. As a result, it is desirable to differentiate behavior based on whether or not the sender is reasonably certain that the flow state exists on each node along the route. We define a flow's state to be "established end-to-end" if the Flow Tables of all nodes on the route contains forwarding information for that flow. While it is impossible to detect whether or not a flow's state has
Johnson, et al. Experimental [Page 22] RFC 4728 The Dynamic Source Routing Protocol February 2007
Johnson, et al. Experimental [Page 22] RFC 4728 The Dynamic Source Routing Protocol February 2007
been established end-to-end without sending packets, implementations may make reasonable assumptions about the retention of flow state and the probability that an establishment packet has been seen by all nodes on the route.
been established end-to-end without sending packets, implementations may make reasonable assumptions about the retention of flow state and the probability that an establishment packet has been seen by all nodes on the route.
A source wishing to send a packet along an established flow determines if the flow state has been established end-to-end. If it has not, a DSR Options header with Source Route option with this flow's route is added to the packet. The source SHOULD set the Flow ID field of the DSR Flow State header either to the flow ID previously associated with this flow's route or to zero. If it sets the Flow ID field to any other value, it MUST follow the processing steps in Section 3.5.1 for establishing a new flow ID. If it sets the Flow ID field to a nonzero value, it MUST include a Timeout option with a value not greater than the timeout remaining in the node's Flow Table, and if its TTL is not equal to that specified in the Flow Table, the flow MUST NOT be used as a default flow in the future.
A source wishing to send a packet along an established flow determines if the flow state has been established end-to-end. If it has not, a DSR Options header with Source Route option with this flow's route is added to the packet. The source SHOULD set the Flow ID field of the DSR Flow State header either to the flow ID previously associated with this flow's route or to zero. If it sets the Flow ID field to any other value, it MUST follow the processing steps in Section 3.5.1 for establishing a new flow ID. If it sets the Flow ID field to a nonzero value, it MUST include a Timeout option with a value not greater than the timeout remaining in the node's Flow Table, and if its TTL is not equal to that specified in the Flow Table, the flow MUST NOT be used as a default flow in the future.
Once flow state has been established end-to-end for non-default flows, a source adds a DSR Flow State header to each packet it wishes to send along that flow, setting the Flow ID field to the flow ID of that flow. A Source Route option SHOULD NOT be added to the packet, though if one is, then the steps for processing flows that have not been established end-to-end MUST be followed.
Once flow state has been established end-to-end for non-default flows, a source adds a DSR Flow State header to each packet it wishes to send along that flow, setting the Flow ID field to the flow ID of that flow. A Source Route option SHOULD NOT be added to the packet, though if one is, then the steps for processing flows that have not been established end-to-end MUST be followed.
Once flow state has been established end-to-end for default flows, sources sending packets with IP TTL equal to the TTL value in the local Flow Table entry for this flow then transmit the packet to the next hop. In this case, a DSR Flow State header SHOULD NOT be added to the packet and a DSR Options header likewise SHOULD NOT be added to the packet; though if one is, the steps for sending packets along non-default flows MUST be followed. If the IP TTL is not equal to the TTL value in the local Flow Table, then the steps for processing a non-default flow MUST be followed.
Once flow state has been established end-to-end for default flows, sources sending packets with IP TTL equal to the TTL value in the local Flow Table entry for this flow then transmit the packet to the next hop. In this case, a DSR Flow State header SHOULD NOT be added to the packet and a DSR Options header likewise SHOULD NOT be added to the packet; though if one is, the steps for sending packets along non-default flows MUST be followed. If the IP TTL is not equal to the TTL value in the local Flow Table, then the steps for processing a non-default flow MUST be followed.
3.5.4. Receiving and Forwarding Packets Sent along Established Flows
3.5.4. Receiving and Forwarding Packets Sent along Established Flows
The handling of packets containing a DSR Options header with both a nonzero Flow ID and a Source Route option is described in Section 3.5.2. The Flow ID is ignored when it is equal to zero. This section only describes handling of packets without a Source Route option.
The handling of packets containing a DSR Options header with both a nonzero Flow ID and a Source Route option is described in Section 3.5.2. The Flow ID is ignored when it is equal to zero. This section only describes handling of packets without a Source Route option.
If a node receives a packet with a Flow ID in the DSR Options header that indicates an unexpired flow in the node's Flow Table, it increments the Hop Count in the DSR Options header and forwards the packet to the next hop indicated in the Flow Table.
If a node receives a packet with a Flow ID in the DSR Options header that indicates an unexpired flow in the node's Flow Table, it increments the Hop Count in the DSR Options header and forwards the packet to the next hop indicated in the Flow Table.
Johnson, et al. Experimental [Page 23] RFC 4728 The Dynamic Source Routing Protocol February 2007
Johnson, et al. Experimental [Page 23] RFC 4728 The Dynamic Source Routing Protocol February 2007
If a node receives a packet with a Flow ID that indicates a flow not currently in the node's Flow Table, it returns a Route Error of type UNKNOWN_FLOW with Error Destination and IP Destination addresses copied from the IP Source of the packet triggering the error. This error packet SHOULD be MAC-destined to the node from which the packet was received; if it cannot confirm reachability of the previous node using Route Maintenance, it MUST send the error as described in Section 8.1.1. The node sending the error SHOULD attempt to salvage the packet triggering the Route Error. If it does salvage the packet, it MUST zero the Flow ID in the packet.
If a node receives a packet with a Flow ID that indicates a flow not currently in the node's Flow Table, it returns a Route Error of type UNKNOWN_FLOW with Error Destination and IP Destination addresses copied from the IP Source of the packet triggering the error. This error packet SHOULD be MAC-destined to the node from which the packet was received; if it cannot confirm reachability of the previous node using Route Maintenance, it MUST send the error as described in Section 8.1.1. The node sending the error SHOULD attempt to salvage the packet triggering the Route Error. If it does salvage the packet, it MUST zero the Flow ID in the packet.
If a node receives a packet with no DSR Options header and no DSR Flow State header, it checks the Default Flow Table. If there is a matching entry, it forwards to the next hop indicated in the Flow Table for the default flow. Otherwise, it returns a Route Error of type DEFAULT_FLOW_UNKNOWN with Error Destination and IP Destination addresses copied from the IP Source Address of the packet triggering the error. This error packet SHOULD be MAC-destined to the node from which it was received; if this node cannot confirm reachability of the previous node using Route Maintenance, it MUST send the error as described in Section 8.1.1. The node sending the error SHOULD attempt to salvage the packet triggering the Route Error. If it does salvage the packet, it MUST zero the Flow ID in the packet.
If a node receives a packet with no DSR Options header and no DSR Flow State header, it checks the Default Flow Table. If there is a matching entry, it forwards to the next hop indicated in the Flow Table for the default flow. Otherwise, it returns a Route Error of type DEFAULT_FLOW_UNKNOWN with Error Destination and IP Destination addresses copied from the IP Source Address of the packet triggering the error. This error packet SHOULD be MAC-destined to the node from which it was received; if this node cannot confirm reachability of the previous node using Route Maintenance, it MUST send the error as described in Section 8.1.1. The node sending the error SHOULD attempt to salvage the packet triggering the Route Error. If it does salvage the packet, it MUST zero the Flow ID in the packet.
3.5.5. Processing Route Errors
3.5.5. Processing Route Errors
When a node receives a Route Error of type UNKNOWN_FLOW, it marks the flow to indicate that it has not been established end-to-end. When a node receives a Route Error of type DEFAULT_FLOW_UNKNOWN, it marks the default flow to indicate that it has not been established end- to-end.
When a node receives a Route Error of type UNKNOWN_FLOW, it marks the flow to indicate that it has not been established end-to-end. When a node receives a Route Error of type DEFAULT_FLOW_UNKNOWN, it marks the default flow to indicate that it has not been established end- to-end.
3.5.6. Interaction with Automatic Route Shortening
3.5.6. Interaction with Automatic Route Shortening
Because a full source route is not carried in every packet, an alternative method for performing automatic route shortening is necessary for packets using the flow state extension. Instead, nodes promiscuously listen to packets, and if a node receives a packet with (IP Source, IP Destination, Flow ID) found in the Flow Table but the MAC-layer (next hop) destination address of the packet is not this node, the node determines whether the packet was sent by an upstream or downstream node by examining the Hop Count field in the DSR Flow State header. If the Hop Count field is less than the expected Hop Count at this node (that is, the expected Hop Count field in the Flow Table described in Section 5.1), the node assumes that the packet was sent by an upstream node and adds an entry for the packet to its Automatic Route Shortening Table, possibly evicting an earlier entry added to this table. When the packet is then sent to that node for
Because a full source route is not carried in every packet, an alternative method for performing automatic route shortening is necessary for packets using the flow state extension. Instead, nodes promiscuously listen to packets, and if a node receives a packet with (IP Source, IP Destination, Flow ID) found in the Flow Table but the MAC-layer (next hop) destination address of the packet is not this node, the node determines whether the packet was sent by an upstream or downstream node by examining the Hop Count field in the DSR Flow State header. If the Hop Count field is less than the expected Hop Count at this node (that is, the expected Hop Count field in the Flow Table described in Section 5.1), the node assumes that the packet was sent by an upstream node and adds an entry for the packet to its Automatic Route Shortening Table, possibly evicting an earlier entry added to this table. When the packet is then sent to that node for
Johnson, et al. Experimental [Page 24] RFC 4728 The Dynamic Source Routing Protocol February 2007
Johnson, et al. Experimental [Page 24] RFC 4728 The Dynamic Source Routing Protocol February 2007
forwarding, the node finds that it has previously received the packet by checking its Automatic Route Shortening Table and returns a gratuitous Route Reply to the source of the packet.
forwarding, the node finds that it has previously received the packet by checking its Automatic Route Shortening Table and returns a gratuitous Route Reply to the source of the packet.
3.5.7. Loop Detection
3.5.7. Loop Detection
If a node receives a packet for forwarding with TTL lower than expected and default flow forwarding is being used, it sends a Route Error of type DEFAULT_FLOW_UNKNOWN back to the IP source. It can attempt delivery of the packet by normal salvaging (subject to constraints described in Section 8.6.7).
If a node receives a packet for forwarding with TTL lower than expected and default flow forwarding is being used, it sends a Route Error of type DEFAULT_FLOW_UNKNOWN back to the IP source. It can attempt delivery of the packet by normal salvaging (subject to constraints described in Section 8.6.7).
3.5.8. Acknowledgement Destination
3.5.8. Acknowledgement Destination
In packets sent using Flow State, the previous hop is not necessarily known. In order to allow nodes that have lost flow state to determine the previous hop, the address of the previous hop can optionally be stored in the Acknowledgement Request. This extension SHOULD NOT be used when a Source Route option is present, MAY be used when flow state routing is used without a Source Route option, and SHOULD be used before Route Maintenance determines that the next-hop destination is unreachable.
In packets sent using Flow State, the previous hop is not necessarily known. In order to allow nodes that have lost flow state to determine the previous hop, the address of the previous hop can optionally be stored in the Acknowledgement Request. This extension SHOULD NOT be used when a Source Route option is present, MAY be used when flow state routing is used without a Source Route option, and SHOULD be used before Route Maintenance determines that the next-hop destination is unreachable.
3.5.9. Crash Recovery
3.5.9. Crash Recovery
Each node has a maximum Timeout value that it can possibly generate. This can be based on the largest number that can be set in a timeout option (2**16 - 1 seconds) or may be less than this, set in system software. When a node crashes, it does not establish new flows for a period equal to this maximum Timeout value, in order to avoid colliding with its old Flow IDs.
Each node has a maximum Timeout value that it can possibly generate. This can be based on the largest number that can be set in a timeout option (2**16 - 1 seconds) or may be less than this, set in system software. When a node crashes, it does not establish new flows for a period equal to this maximum Timeout value, in order to avoid colliding with its old Flow IDs.
3.5.10. Rate Limiting
3.5.10. Rate Limiting
Flow IDs can be assigned with a counter. More specifically, the "Current Flow ID" is kept. When a new default Flow ID needs to be assigned, if the Current Flow ID is odd, the Current Flow ID is assigned as the Flow ID and the Current Flow ID is incremented by one; if the Current Flow ID is even, one plus the Current Flow ID is assigned as the Flow ID and the Current Flow ID is incremented by two.
Flow IDs can be assigned with a counter. More specifically, the "Current Flow ID" is kept. When a new default Flow ID needs to be assigned, if the Current Flow ID is odd, the Current Flow ID is assigned as the Flow ID and the Current Flow ID is incremented by one; if the Current Flow ID is even, one plus the Current Flow ID is assigned as the Flow ID and the Current Flow ID is incremented by two.
If Flow IDs are assigned in this way, one algorithm for avoiding duplicate, unexpired Flow IDs is to rate limit new Flow IDs to an average rate of n assignments per second, where n is 2**15 divided by the maximum Timeout value. This can be averaged over any period not exceeding the maximum Timeout value.
If Flow IDs are assigned in this way, one algorithm for avoiding duplicate, unexpired Flow IDs is to rate limit new Flow IDs to an average rate of n assignments per second, where n is 2**15 divided by the maximum Timeout value. This can be averaged over any period not exceeding the maximum Timeout value.
Johnson, et al. Experimental [Page 25] RFC 4728 The Dynamic Source Routing Protocol February 2007
Johnson, et al. Experimental [Page 25] RFC 4728 The Dynamic Source Routing Protocol February 2007
3.5.11. Interaction with Packet Salvaging
3.5.11. Interaction with Packet Salvaging
Salvaging is modified to zero the Flow ID field in the packet. Also, anytime this document refers to the Salvage field in the Source Route option in a DSR Options header, packets without a Source Route option are considered to have the value zero in the Salvage field.
Salvaging is modified to zero the Flow ID field in the packet. Also, anytime this document refers to the Salvage field in the Source Route option in a DSR Options header, packets without a Source Route option are considered to have the value zero in the Salvage field.
4. Conceptual Data Structures
4. Conceptual Data Structures
This document describes the operation of the DSR protocol in terms of a number of conceptual data structures. This section describes each of these data structures and provides an overview of its use in the protocol. In an implementation of the protocol, these data structures MUST be implemented in a manner consistent with the external behavior described in this document, but the choice of implementation used is otherwise unconstrained. Additional conceptual data structures are required for the optional flow state extensions to DSR; these data structures are described in Section 5.
This document describes the operation of the DSR protocol in terms of a number of conceptual data structures. This section describes each of these data structures and provides an overview of its use in the protocol. In an implementation of the protocol, these data structures MUST be implemented in a manner consistent with the external behavior described in this document, but the choice of implementation used is otherwise unconstrained. Additional conceptual data structures are required for the optional flow state extensions to DSR; these data structures are described in Section 5.
4.1. Route Cache
4.1. Route Cache
Each node implementing DSR MUST maintain a Route Cache, containing routing information needed by the node. A node adds information to its Route Cache as it learns of new links between nodes in the ad hoc network; for example, a node may learn of new links when it receives a packet carrying a Route Request, Route Reply, or DSR source route. Likewise, a node removes information from its Route Cache as it learns that existing links in the ad hoc network have broken. For example, a node may learn of a broken link when it receives a packet carrying a Route Error or through the link-layer retransmission mechanism reporting a failure in forwarding a packet to its next-hop destination.
Each node implementing DSR MUST maintain a Route Cache, containing routing information needed by the node. A node adds information to its Route Cache as it learns of new links between nodes in the ad hoc network; for example, a node may learn of new links when it receives a packet carrying a Route Request, Route Reply, or DSR source route. Likewise, a node removes information from its Route Cache as it learns that existing links in the ad hoc network have broken. For example, a node may learn of a broken link when it receives a packet carrying a Route Error or through the link-layer retransmission mechanism reporting a failure in forwarding a packet to its next-hop destination.
Anytime a node adds new information to its Route Cache, the node SHOULD check each packet in its own Send Buffer (Section 4.2) to determine whether a route to that packet's IP Destination Address now exists in the node's Route Cache (including the information just added to the Cache). If so, the packet SHOULD then be sent using that route and removed from the Send Buffer.
Anytime a node adds new information to its Route Cache, the node SHOULD check each packet in its own Send Buffer (Section 4.2) to determine whether a route to that packet's IP Destination Address now exists in the node's Route Cache (including the information just added to the Cache). If so, the packet SHOULD then be sent using that route and removed from the Send Buffer.
It is possible to interface a DSR network with other networks, external to this DSR network. Such external networks may, for example, be the Internet or may be other ad hoc networks routed with a routing protocol other than DSR. Such external networks may also be other DSR networks that are treated as external networks in order to improve scalability. The complete handling of such external networks is beyond the scope of this document. However, this document specifies a minimal set of requirements and features
It is possible to interface a DSR network with other networks, external to this DSR network. Such external networks may, for example, be the Internet or may be other ad hoc networks routed with a routing protocol other than DSR. Such external networks may also be other DSR networks that are treated as external networks in order to improve scalability. The complete handling of such external networks is beyond the scope of this document. However, this document specifies a minimal set of requirements and features
Johnson, et al. Experimental [Page 26] RFC 4728 The Dynamic Source Routing Protocol February 2007
Johnson, et al. Experimental [Page 26] RFC 4728 The Dynamic Source Routing Protocol February 2007
necessary to allow nodes only implementing this specification to interoperate correctly with nodes implementing interfaces to such external networks. This minimal set of requirements and features involve the First Hop External (F) and Last Hop External (L) bits in a DSR Source Route option (Section 6.7) and a Route Reply option (Section 6.3) in a packet's DSR Options header (Section 6). These requirements also include the addition of an External flag bit tagging each link in the Route Cache, copied from the First Hop External (F) and Last Hop External (L) bits in the DSR Source Route option or Route Reply option from which this link was learned.
ノードがそのような外部のネットワークにインタフェースを実装していてこの仕様を履行するだけであるノードが正しく共同利用するのを許容するために、必要です。 この極小集合の要件と特徴はパケットのDSR Optionsヘッダー(セクション6)のDSR Source Routeオプション(セクション6.7)とRoute Replyオプション(セクション6.3)にFirst Hop External(F)とLast Hop External(L)ビットにかかわります。 また、これらの要件はFirst Hop External(F)とLast Hop External(L)ビットからDSR Source RouteオプションでコピーされたRoute Cacheかこのリンクが学習されたRoute Replyオプションで各リンクにタグ付けをするExternalフラグビットの追加を含んでいます。
The Route Cache SHOULD support storing more than one route to each destination. In searching the Route Cache for a route to some destination node, the Route Cache is searched by destination node address. The following properties describe this searching function on a Route Cache:
Route Cache SHOULDは、各目的地あたり保存が1つ以上のルートであるとサポートします。 何らかの目的地ノードへのルートとしてRoute Cacheを捜す際に、Route Cacheは送付先ノードアドレスによって捜されます。 以下の特性はRoute Cacheでこの探す機能について説明します:
- Each implementation of DSR at any node MAY choose any appropriate
strategy and algorithm for searching its Route Cache and selecting
a "best" route to the destination from among those found. For
example, a node MAY choose to select the shortest route to the
destination (the shortest sequence of hops), or it MAY use an
alternate metric to select the route from the Cache.
- どんなノードのDSRの各実装もRoute Cacheとそれらからの目的地への「最も良い」ルートを選択すると設立される探索のためのどんな適切な戦略とアルゴリズムも選ぶかもしれません。 例えば、ノードが、目的地(ホップの最も短い系列)に最も短いルートを選択するのを選ぶかもしれませんか、またはそれはCacheからルートを選択するためにはメートル法の補欠を使用するかもしれません。
- However, if there are multiple cached routes to a destination, the
selection of routes when searching the Route Cache SHOULD prefer
routes that do not have the External flag set on any link. This
preference will select routes that lead directly to the target
node over routes that attempt to reach the target via any external
networks connected to the DSR ad hoc network.
- しかしながら、複数のキャッシュされたルートがあれば、目的地、探すときのルートの品揃えより、Route Cache SHOULDはどんなリンクの上にもExternal旗を設定しないルートを好みます。 この好みはDSRの臨時のネットワークに接続されたどんな外部のネットワークを通しても目標に達するのを試みるルートの上で直接目標ノードにつながるルートを選択するでしょう。
- In addition, any route selected when searching the Route Cache
MUST NOT have the External bit set for any links other than
possibly the first link, the last link, or both; the External bit
MUST NOT be set for any intermediate hops in the route selected.
- さらに、Route Cacheを捜すとき選択されたどんなルートでも、ことによると最初のリンク、最後のリンク、または両方以外のどんなリンクにもExternalビットを設定してはいけません。 ルートによる中間的ホップが選択したいずれにもExternalビットを設定してはいけません。
An implementation of a Route Cache MAY provide a fixed capacity for the cache, or the cache size MAY be variable. The following properties describe the management of available space within a node's Route Cache:
Route Cacheの実装は固定容量にキャッシュに備えるかもしれませんか、またはキャッシュサイズが可変であるかもしれません。 以下の特性はノードのRoute Cacheの中で利用可能なスペースの管理について説明します:
- Each implementation of DSR at each node MAY choose any appropriate
policy for managing the entries in its Route Cache, such as when
limited cache capacity requires a choice of which entries to
retain in the Cache. For example, a node MAY chose a "least
recently used" (LRU) cache replacement policy, in which the entry
- 各ノードのDSRの各実装はRoute Cacheでエントリーを管理するためのどんな適切な方針も選ぶかもしれません、限られたキャッシュ容量が選択をCacheでどのエントリーを保有するかを必要とする時のように。 例えば、5月が「最も最近でない、中古」の(LRU)キャッシュ交換方針、コネを選んだノード、どれ、エントリー
Johnson, et al. Experimental [Page 27] RFC 4728 The Dynamic Source Routing Protocol February 2007
ジョンソン、他 ダイナミックな実験的な[27ページ]RFC4728のソースルーティング・プロトコル2007年2月
last used longest ago is discarded from the cache if a decision
needs to be made to allow space in the cache for some new entry
being added.
最終が最も長い間使用した、前、キャッシュから、決定が、加えられるいくらかの新しいエントリーへのキャッシュで紙面を割かされる必要があるなら、捨てられます。
- However, the Route Cache replacement policy SHOULD allow routes to
be categorized based upon "preference", where routes with a higher
preferences are less likely to be removed from the cache. For
example, a node could prefer routes for which it initiated a Route
Discovery over routes that it learned as the result of promiscuous
snooping on other packets. In particular, a node SHOULD prefer
routes that it is presently using over those that it is not.
- しかしながら、Route Cache交換方針SHOULDは、ルートが、より高い好みがあるルートがキャッシュから、より取り除かれそうにない「好み」に基づいた状態で分類されるのを許容します。 例えば、ノードは、他のパケットの上で詮索しながら、それがそれが無差別の結果として学んだルートの上でRouteディスカバリーを開始したルートを好むかもしれません。 特にそれが現在それらの上で使用しているルートですが、SHOULDが好むノード。
Any suitable data structure organization, consistent with this specification, MAY be used to implement the Route Cache in any node. For example, the following two types of organization are possible:
どんなこの仕様と一致した適当なデータ構造組織も、どんなノードでもRoute Cacheを実装するのに使用されるかもしれません。 例えば、以下の2つのタイプの組織は可能です:
- In DSR, the route returned in each Route Reply that is received by
the initiator of a Route Discovery (or that is learned from the
header of overhead packets, as described in Section 8.1.4)
represents a complete path (a sequence of links) leading to the
destination node. By caching each of these paths separately, a
"path cache" organization for the Route Cache can be formed. A
path cache is very simple to implement and easily guarantees that
all routes are loop-free, since each individual route from a Route
Reply or Route Request or used in a packet is loop-free. To
search for a route in a path cache data structure, the sending
node can simply search its Route Cache for any path (or prefix of
a path) that leads to the intended destination node.
- DSRでは、Routeディスカバリー(それはセクション8.1.4で説明されるように頭上のパケットのヘッダーから学習される)の創始者によって受け取られる各Route Replyで返されたルートは、目的地ノードに通じながら、完全な経路(リンクの系列)を表します。 別々にそれぞれのこれらの経路をキャッシュすることによって、Route Cacheのための「経路キャッシュ」組織を形成できます。 パケットで実装するのが非常に簡単であり、Route ReplyかRoute Requestからのそれぞれの独特のルート以来すべてのルートが輪なしであることを容易に保証するか、または使用される経路キャッシュは輪なしです。 経路キャッシュデータ構造でルートを捜し求めるために、送付ノードは単に意図している目的地ノードにつながるどんな経路(または、経路の接頭語)としてもRoute Cacheを捜すことができます。
This type of organization for the Route Cache in DSR has been
extensively studied through simulation [BROCH98, HU00,
JOHANSSON99, MALTZ99a] and through implementation of DSR in a
mobile outdoor testbed under significant workload [MALTZ99b,
MALTZ00, MALTZ01].
DSRのRoute Cacheのためのこのタイプの組織はシミュレーション[BROCH98、HU00、JOHANSSON99、MALTZ99a]を通して重要なワークロード[MALTZ99b、MALTZ00、MALTZ01]の下のモバイル野外のテストベッドのDSRの実装を通して手広く研究されました。
- Alternatively, a "link cache" organization could be used for the
Route Cache, in which each individual link (hop) in the routes
returned in Route Reply packets (or otherwise learned from the
header of overhead packets) is added to a unified graph data
structure of this node's current view of the network topology. To
search for a route in link cache, the sending node must use a more
complex graph search algorithm, such as the well-known Dijkstra's
shortest-path algorithm, to find the current best path through the
graph to the destination node. Such an algorithm is more
difficult to implement and may require significantly more CPU time
to execute.
- あるいはまた、Route Cacheに「リンクキャッシュ」組織を使用できました。そこでは、Route Replyパケット(または、別の方法で頭上のパケットのヘッダーから学習される)で返されたルートによるそれぞれの個々のリンク(ホップ)はこのノードのネットワーク形態の現在の視点の統一されたグラフデータ構造に追加されます。 リンクキャッシュでルートを捜し求めるなら、送付ノードは、グラフで現在の最も良い経路を目的地ノードに見つけるのによく知られるダイクストラの最短パスアルゴリズムなどの、より複雑なグラフ検索アルゴリズムを使用しなければなりません。 そのようなアルゴリズムは、実装するのが、より難しく、実行するかなり多くのCPU時間を必要とするかもしれません。
Johnson, et al. Experimental [Page 28] RFC 4728 The Dynamic Source Routing Protocol February 2007
ジョンソン、他 ダイナミックな実験的な[28ページ]RFC4728のソースルーティング・プロトコル2007年2月
However, a link cache organization is more powerful than a path
cache organization, in its ability to effectively utilize all of
the potential information that a node might learn about the state
of the network. In particular, links learned from different Route
Discoveries or from the header of any overheard packets can be
merged together to form new routes in the network, but this is not
possible in a path cache due to the separation of each individual
path in the cache.
しかしながら、リンクキャッシュ組織は経路キャッシュ組織より強力です、事実上、ノードがネットワークの事情に関して学ぶかもしれないという潜在的情報のすべてを利用する性能で。 特に、異なったRoute Discoveriesかどんな立ち聞きされたパケットのヘッダーからも学習されたリンクはネットワークで新しいルートを形成するために結合できますが、これはキャッシュにおける、それぞれの個々の経路の分離のために経路キャッシュでは可能ではありません。
This type of organization for the Route Cache in DSR, including
the effect of a range of implementation choices, has been studied
through detailed simulation [HU00].
詳細なシミュレーション[HU00]でさまざまな実装選択の効果を含むDSRのRoute Cacheのためのこのタイプの組織は研究されました。
The choice of data structure organization to use for the Route Cache in any DSR implementation is a local matter for each node and affects only performance; any reasonable choice of organization for the Route Cache does not affect either correctness or interoperability.
Route CacheにどんなDSR実装にも使用するデータ構造組織の選択は、各ノードのための地域にかかわる事柄であり、性能だけに影響します。 Route Cacheのための組織のどんな正当な選択も正当性か相互運用性のどちらかに影響しません。
Each entry in the Route Cache SHOULD have a timeout associated with it, to allow that entry to be deleted if not used within some time. The particular choice of algorithm and data structure used to implement the Route Cache SHOULD be considered in choosing the timeout for entries in the Route Cache. The configuration variable RouteCacheTimeout defined in Section 9 specifies the timeout to be applied to entries in the Route Cache, although it is also possible to instead use an adaptive policy in choosing timeout values rather than using a single timeout setting for all entries. For example, the Link-MaxLife cache design (below) uses an adaptive timeout algorithm and does not use the RouteCacheTimeout configuration variable.
Route Cache SHOULDの各エントリーには、そのエントリーがいつか中で削除されるか、または使用されるのを許容するために、それに関連しているタイムアウトがあります。 考えられて、アルゴリズムとデータ構造の特定の選択は以前はRoute Cacheのエントリーへのタイムアウトを選ぶ際にRoute Cache SHOULDをよく実装していました。 セクション9で定義された構成の可変RouteCacheTimeoutはRoute Cacheのエントリーに適用されるためにタイムアウトを指定します、また、代わりにすべてのエントリーにセットする単一のタイムアウトを使用するよりむしろタイムアウト値を選ぶ際に適応型の方針を使用するのも可能ですが。 例えば、Link-MaxLifeキャッシュデザイン(below)は適応型のタイムアウトアルゴリズムを使用して、RouteCacheTimeout構成変数は使用しません。
As guidance to implementers, Appendix A describes a type of link cache known as "Link-MaxLife" that has been shown to outperform other types of link caches and path caches studied in detailed simulation [HU00]. Link-MaxLife is an adaptive link cache in which each link in the cache has a timeout that is determined dynamically by the caching node according to its observed past behavior of the two nodes at the ends of the link. In addition, when selecting a route for a packet being sent to some destination, among cached routes of equal length (number of hops) to that destination, Link-MaxLife selects the route with the longest expected lifetime (highest minimum timeout of any link in the route). Use of the Link-MaxLife design for the Route Cache is recommended in implementations of DSR.
implementersへの指導として、Appendix Aは詳細なシミュレーション[HU00]で研究された他のタイプのリンクキャッシュと経路キャッシュより優れるように示された「リンク-MaxLife」として知られている一種のリンクキャッシュについて説明します。 リンク-MaxLifeは2つのノードの観測された過去の動きに従ってキャッシュにおける各リンクがリンクの端にキャッシュノードでダイナミックに断固としたタイムアウトを持っている適応型のリンクキャッシュです。 いくつかの目的地に送られるパケットのためにルートを選択するとき、さらに、その目的地への等しい長さ(ホップの数)のキャッシュされたルートの中では、Link-MaxLifeは最も長い予想された生涯(どんなリンクのルートで最も高い最小のタイムアウトも)があるルートを選択します。 Link-MaxLifeデザインのRoute Cacheの使用はDSRの実装でお勧めです。
Johnson, et al. Experimental [Page 29] RFC 4728 The Dynamic Source Routing Protocol February 2007
ジョンソン、他 ダイナミックな実験的な[29ページ]RFC4728のソースルーティング・プロトコル2007年2月
4.2. Send Buffer
4.2. バッファを送ってください。
The Send Buffer of a node implementing DSR is a queue of packets that cannot be sent by that node because it does not yet have a source route to each such packet's destination. Each packet in the Send Buffer is logically associated with the time that it was placed into the buffer and SHOULD be removed from the Send Buffer and silently discarded after a period of SendBufferTimeout after initially being placed in the buffer. If necessary, a FIFO strategy SHOULD be used to evict packets before they time out to prevent the buffer from overflowing.
DSRを実装するノードのSend Bufferはそれがまだそのような各パケットの目的地に送信元経路を持っていないのでそのノードで送ることができないパケットの待ち行列です。 Send Bufferのそれぞれのパケットは、初めは後にバッファに置かれながら、Send Bufferから取り外されて、SendBufferTimeoutの期間の後に静かに捨てられるそれがバッファの中に置かれた時間とSHOULDに論理的に関連しています。 必要なら先入れ先出し法戦略SHOULD、パケットを追い立てる前で中古のそれら、バッファがあふれるのを防ぐタイムアウト。
Subject to the rate limiting defined in Section 4.3, a Route Discovery SHOULD be initiated as often as allowed for the destination address of any packets residing in the Send Buffer.
制限がセクション4.3、RouteディスカバリーSHOULDで定義したレートを条件として、Send Bufferに住んでいるどんなパケットの送付先アドレスのためにも許容されているのと同じくらい頻繁に開始されてください。
4.3. Route Request Table
4.3. ルート要求テーブル
The Route Request Table of a node implementing DSR records information about Route Requests that have been recently originated or forwarded by this node. The table is indexed by IP address.
DSRを実装するノードのRoute Request Tableはこのノードによって最近、溯源されるか、または進められたRoute Requestsの情報を記録します。 テーブルはIPアドレスによって索引をつけられます。
The Route Request Table on a node records the following information about nodes to which this node has initiated a Route Request:
ノードの上のRoute Request TableはこのノードがRoute Requestを開始したノードの以下の情報を記録します:
- The Time-to-Live (TTL) field used in the IP header of the Route
Request for the last Route Discovery initiated by this node for
that target node. This value allows the node to implement a
variety of algorithms for controlling the spread of its Route
Request on each Route Discovery initiated for a target. As
examples, two possible algorithms for this use of the TTL field
are described in Section 3.3.3.
- その目標ノードのためのこのノードによって開始された最後のRouteディスカバリーにRoute RequestのIPヘッダーで使用される生きるTime(TTL)分野。 この値で、ノードは目標のために開始されたそれぞれのRouteディスカバリーの上でRoute Requestの普及を制御するためのさまざまなアルゴリズムを実装することができます。 例として、TTL分野のこの使用のための2つの可能なアルゴリズムがセクション3.3.3で説明されます。
- The time that this node last originated a Route Request for that
target node.
- このノードが持続する時間はその目標ノードのためにRoute Requestを溯源しました。
- The number of consecutive Route Discoveries initiated for this
target since receiving a valid Route Reply giving a route to that
target node.
- ルートをそれに与えながら有効なRoute Replyを受けて以来この目標のために開始された連続したRoute Discoveriesの数はノードを狙います。
- The remaining amount of time before which this node MAY next
attempt at a Route Discovery for that target node. When the node
initiates a new Route Discovery for this target node, this field
in the Route Request Table entry for that target node is
initialized to the timeout for that Route Discovery, after which
the node MAY initiate a new Discovery for that target. Until a
valid Route Reply is received for this target node address, a node
MUST implement a back-off algorithm in determining this timeout
- このノードが次にそうするかもしれない残っている量の時がその目標ノードのためにRouteでディスカバリーを試みます。 ノードがこの目標ノードのために新しいRouteディスカバリーを開始するとき、その目標ノードのためのRoute Request Tableエントリーにおけるこの分野はそのRouteディスカバリーのためにタイムアウトに初期化されます。(その時、ノードはその目標のために新しいディスカバリーを開始したかもしれません後)。 ノードはこのタイムアウトを決定する際に下に後部アルゴリズムをこの目標ノードアドレスのために有効なRoute Replyを受け取るまで実装しなければなりません。
Johnson, et al. Experimental [Page 30] RFC 4728 The Dynamic Source Routing Protocol February 2007
ジョンソン、他 ダイナミックな実験的な[30ページ]RFC4728のソースルーティング・プロトコル2007年2月
value for each successive Route Discovery initiated for this
target using the same Time-to-Live (TTL) value in the IP header of
the Route Request packet. The timeout between such consecutive
Route Discovery initiations SHOULD increase by doubling the
timeout value on each new initiation.
この目標のためにRoute RequestパケットのIPヘッダーで生きる同じTime(TTL)値を使用することで開始されたそれぞれの連続したRouteディスカバリーのための値。 SHOULDがそれぞれの新しい開始のときにタイムアウト値を倍にすることによって増強するそのような連続したRouteディスカバリー開始の間のタイムアウト。
In addition, the Route Request Table on a node also records the following information about initiator nodes from which this node has received a Route Request:
また、さらに、ノードの上のRoute Request TableはこのノードがRoute Requestを受けた創始者ノードの以下の情報を記録します:
- A FIFO cache of size RequestTableIds entries containing the
Identification value and target address from the most recent Route
Requests received by this node from that initiator node.
- 最新のRoute RequestsからのIdentification値とあて先アドレスを含むサイズRequestTableIdsエントリーの先入れ先出し法キャッシュはその創始者ノードからのこのノードのそばで受信されました。
Nodes SHOULD use an LRU policy to manage the entries in their Route Request Table.
ノードSHOULDは、それらのRoute Request Tableでエントリーを管理するのにLRU方針を使用します。
The number of Identification values to retain in each Route Request Table entry, RequestTableIds, MUST NOT be unlimited, since, in the worst case, when a node crashes and reboots, the first RequestTableIds Route Discoveries it initiates after rebooting could appear to be duplicates to the other nodes in the network. In addition, a node SHOULD base its initial Identification value, used for Route Discoveries after rebooting, on a battery backed-up clock or other persistent memory device, if available, in order to help avoid any possible such delay in successfully discovering new routes after rebooting; if no such source of initial Identification value is available, a node after rebooting SHOULD base its initial Identification value on a random number.
それぞれのRoute Request Tableエントリーで保有するIdentification値の数(RequestTableIds)は無制限であるはずがありません、ノードがダウンして、リブートするとき、それがリブートした後に開始する最初のRequestTableIds Route Discoveriesが、ネットワークにおける他のノードへの写しであるように最悪の場合には見えるかもしれないので。 追加、初期のIdentificationが評価するRoute Discoveriesに、支援しているバッテリー時計か他の永続的なメモリ素子の上でリブートした後に中古のノードSHOULDベースの中では、利用可能であるなら、どんな可能なそのようなものも避けるのを助けるためにリブートした後に首尾よく新しいルートを発見する際に延着してください。 初期のIdentification価値のどれかそのような源が利用可能でないなら、乱数で初期のIdentificationが評価するSHOULDベースをリブートした後のノードです。
4.4. Gratuitous Route Reply Table
4.4. 無料のルート回答テーブル
The Gratuitous Route Reply Table of a node implementing DSR records information about "gratuitous" Route Replies sent by this node as part of automatic route shortening. As described in Section 3.4.3, a node returns a gratuitous Route Reply when it overhears a packet transmitted by some node, for which the node overhearing the packet was not the intended next-hop node but was named later in the unexpended hops of the source route in that packet; the node overhearing the packet returns a gratuitous Route Reply to the original sender of the packet, listing the shorter route (not including the hops of the source route "skipped over" by this packet). A node uses its Gratuitous Route Reply Table to limit the rate at which it originates gratuitous Route Replies to the same original sender for the same node from which it overheard a packet to trigger the gratuitous Route Reply.
DSR記録が「無料」のRoute Repliesの情報であると実装するノードのGratuitous Route Reply Tableは自動ルート短縮の一部としてこのノードで発信しました。 何らかのノードによってパケットを立ち聞きするノードが意図している次のホップノードではありませんでしたが、後でそのパケットの送信元経路の未支出ホップで命名された伝えられたパケットを立ち聞きするとき、セクション3.4.3で説明されるように、ノードは無料のRoute Replyを返します。 パケットを立ち聞きするノードは無料のRoute Replyをパケットの元の送り主に返します、いっそう早く行けるルート(このパケットによって「飛び越えられた」送信元経路のホップを含んでいない)を記載して。 ノードは、それがそれが無料のRoute Replyの引き金となるようにパケットを立ち聞きしたのと同じノードのために同じ元の送り主に無料のRoute Repliesを溯源するレートを制限するのにGratuitous Route Reply Tableを使用します。
Johnson, et al. Experimental [Page 31] RFC 4728 The Dynamic Source Routing Protocol February 2007
ジョンソン、他 ダイナミックな実験的な[31ページ]RFC4728のソースルーティング・プロトコル2007年2月
Each entry in the Gratuitous Route Reply Table of a node contains the following fields:
ノードのGratuitous Route Reply Tableの各エントリーは以下の分野を含んでいます:
- The address of the node to which this node originated a gratuitous
Route Reply.
- このノードが無料のRoute Replyを溯源したノードのアドレス。
- The address of the node from which this node overheard the packet
triggering that gratuitous Route Reply.
- このノードが、パケットがその無料のRoute Replyの引き金となると立ち聞きしたノードのアドレス。
- The remaining time before which this entry in the Gratuitous Route
Reply Table expires and SHOULD be deleted by the node. When a
node creates a new entry in its Gratuitous Route Reply Table, the
timeout value for that entry SHOULD be initialized to the value
GratReplyHoldoff.
- 残りはGratuitous Route Reply Tableのこのエントリーが吐き出すものとSHOULDの前で調節されます。ノードで、削除されます。 ノードがGratuitous Route Reply Tableで新しいエントリーを作成するとき、タイムアウトはそのエントリーにSHOULDを評価します。値のGratReplyHoldoffに初期化されます。
When a node overhears a packet that would trigger a gratuitous Route Reply, if a corresponding entry already exists in the node's Gratuitous Route Reply Table, then the node SHOULD NOT send a gratuitous Route Reply for that packet. Otherwise (i.e., if no corresponding entry already exists), the node SHOULD create a new entry in its Gratuitous Route Reply Table to record that gratuitous Route Reply, with a timeout value of GratReplyHoldoff.
ノードが無料のRoute Replyの引き金となるパケットを立ち聞きするとき、対応するエントリーがノードのGratuitous Route Reply Tableに既に存在しているなら、ノードSHOULD NOTはそのパケットのために無料のRoute Replyを送ります。 さもなければ(すなわち、どんな対応するエントリーも既に存在していないなら)、ノードSHOULDはその無料のRoute Replyを記録するためにGratuitous Route Reply Tableで新しいエントリーを作成します、GratReplyHoldoffのタイムアウト値で。
4.5. Network Interface Queue and Maintenance Buffer
4.5. ネットワーク・インターフェース待ち行列とメインテナンスバッファ
Depending on factors such as the structure and organization of the operating system, protocol stack implementation, network interface device driver, and network interface hardware, a packet being transmitted could be queued in a variety of ways. For example, outgoing packets from the network protocol stack might be queued at the operating system or link layer, before transmission by the network interface. The network interface might also provide a retransmission mechanism for packets, such as occurs in IEEE 802.11 [IEEE80211]; the DSR protocol, as part of Route Maintenance, requires limited buffering of packets already transmitted for which the reachability of the next-hop destination has not yet been determined. The operation of DSR is defined here in terms of two conceptual data structures that, together, incorporate this queuing behavior.
オペレーティングシステム、プロトコル・スタック実装、ネットワークインタフェース機器、およびネットワーク・インターフェースハードウェアの構造や組織などの要素によって、さまざまな方法で伝えられるパケットは列に並ばせることができました。 例えば、ネットワークプロトコル・スタックからの出発しているパケットはオペレーティングシステムかリンクレイヤに列に並ばせられるかもしれません、ネットワーク・インターフェースのそばでのトランスミッションの前に。 また、ネットワーク・インターフェースはパケットのための「再-トランスミッション」メカニズムを提供するかもしれません。(それは、IEEE802.11[IEEE80211]に現れます)。 Route Maintenanceの一部として、DSRプロトコルは次のホップの目的地の可到達性がまだ決定していない既に伝えられたパケットの限られたバッファリングを必要とします。 DSRの操作はここで振舞いを列に並ばせながらこれを一緒に取り入れる2つの概念的なデータ構造で定義されます。
The Network Interface Queue of a node implementing DSR is an output queue of packets from the network protocol stack waiting to be transmitted by the network interface; for example, in the 4.4BSD Unix network protocol stack implementation, this queue for a network interface is represented as a "struct ifqueue" [WRIGHT95]. This queue is used to hold packets while the network interface is in the process of transmitting another packet.
DSRを実装するノードのNetwork Interface Queueはネットワーク・インターフェースによって伝えられるのを待つネットワークプロトコル・スタックからのパケットの出力キューです。 例えば、4.4BSD Unixネットワーク・プロトコルスタック実装では、ネットワーク・インターフェースのためのこの待ち行列は"struct ifqueue"[WRIGHT95]として表されます。 この待ち行列は、別のパケットを伝えることの途中にネットワーク・インターフェースがある間、パケットを保持するのに使用されます。
Johnson, et al. Experimental [Page 32] RFC 4728 The Dynamic Source Routing Protocol February 2007
ジョンソン、他 ダイナミックな実験的な[32ページ]RFC4728のソースルーティング・プロトコル2007年2月
The Maintenance Buffer of a node implementing DSR is a queue of packets sent by this node that are awaiting next-hop reachability confirmation as part of Route Maintenance. For each packet in the Maintenance Buffer, a node maintains a count of the number of retransmissions and the time of the last retransmission. Packets are added to the Maintenance buffer after the first transmission attempt is made. The Maintenance Buffer MAY be of limited size; when adding a new packet to the Maintenance Buffer, if the buffer size is insufficient to hold the new packet, the new packet SHOULD be silently discarded. If, after MaxMaintRexmt attempts to confirm next-hop reachability of some node, no confirmation is received, all packets in this node's Maintenance Buffer with this next-hop destination SHOULD be removed from the Maintenance Buffer. In this case, the node also SHOULD originate a Route Error for this packet to each original source of a packet removed in this way (Section 8.3) and SHOULD salvage each packet removed in this way (Section 8.3.6) if it has another route to that packet's IP Destination Address in its Route Cache. The definition of MaxMaintRexmt conceptually includes any retransmissions that might be attempted for a packet at the link layer or within the network interface hardware. The timeout value to use for each transmission attempt for an acknowledgement request depends on the type of acknowledgement mechanism used by Route Maintenance for that attempt, as described in Section 8.3.
DSRを実装するノードのMaintenance BufferはRoute Maintenanceの一部として次のホップ可到達性確認を待っているこのノードによって送られたパケットの待ち行列です。 Maintenance Bufferの各パケットに関しては、ノードは「再-トランスミッション」の数と最後の「再-トランスミッション」の現代のカウントを維持します。 最初のトランスミッション試みをした後にMaintenanceバッファにパケットを追加します。 Maintenance Bufferは限られたサイズのものであるかもしれません。 新しいパケットをMaintenance Bufferに加えるときには、バッファサイズが新しいパケット、新しいパケットSHOULDを持つためには不十分であるなら、静かに捨てられてください。 MaxMaintRexmtが、何らかのノードの次のホップの可到達性を確認するのを試みた後にどんな確認も受け取られていないなら、この次のホップの目的地SHOULDがMaintenance Bufferから取り外されているこのノードのMaintenance Bufferですべてのパケットです。 この場合ノード、また、Route CacheにそのパケットのIP Destination Addressに別のルートを持っているなら、SHOULDはこのパケットのためにこのように取り除かれたパケット(セクション8.3)と各パケットがこのように取り除いたSHOULD海難救助(セクション8.3.6)の各一次資料にRoute Errorを溯源します。 MaxMaintRexmtの定義は概念的にリンクレイヤにおける、または、ネットワーク・インターフェースハードウェアの中のパケットのために試みられるどんな「再-トランスミッション」も含んでいます。 承認要求のためのそれぞれのトランスミッション試みに使用するタイムアウト値をその試みにRoute Maintenanceによって使用された承認メカニズムのタイプに頼っています、セクション8.3で説明されるように。
4.6. Blacklist
4.6. ブラックリスト
When a node using the DSR protocol is connected through a network interface that requires physically bidirectional links for unicast transmission, the node MUST maintain a blacklist. The blacklist is a table, indexed by neighbor node address, that indicates that the link between this node and the specified neighbor node may not be bidirectional. A node places another node's address in this list when it believes that broadcast packets from that other node reach this node, but that unicast transmission between the two nodes is not possible. For example, if a node forwarding a Route Reply discovers that the next hop is unreachable, it places that next hop in the node's blacklist.
DSRプロトコルを使用するノードがユニキャスト送信のために物理的に双方向のリンクを必要とするネットワーク・インターフェースを通して接続されるとき、ノードはブラックリストを維持しなければなりません。 ブラックリストはこのノードと指定された隣人ノードとのリンクが双方向でないかもしれないことを示す隣人ノードアドレスによって索引をつけられたテーブルです。 その他のノードからの放送パケットがこのノードに達しますが、2つのノードの間のユニキャスト送信が可能でないことが信じているとき、ノードは別のノードのアドレスをこのリストに置きます。 Route Replyを進めるノードが例えば次のホップが手が届かなく、それがノードのブラックリストを次に跳ぶ場所であると発見するなら。
Once a node discovers that it can communicate bidirectionally with one of the nodes listed in the blacklist, it SHOULD remove that node from the blacklist. For example, if node A has node B listed in its blacklist, but after transmitting a Route Request, node A hears B forward the Route Request with a route record indicating that the broadcast from A to B was successful, then A SHOULD remove the entry for node B from its blacklist.
かつて、ノードは、それが双方向にブラックリストにリストアップされたノードの1つとコミュニケートできると発見して、それはSHOULDです。ブラックリストからそのノードを取り除いてください。 例えば、ノードAにはブラックリストにリストアップされたノードBがありますが、Route Requestを伝えた後にノードAが、ルート記録が、AからBまでの放送がうまくいったのを示していてBがRoute Requestを進めるのを聞くなら、A SHOULDはブラックリストからノードBのためのエントリーを取り除きます。
Johnson, et al. Experimental [Page 33] RFC 4728 The Dynamic Source Routing Protocol February 2007
ジョンソン、他 ダイナミックな実験的な[33ページ]RFC4728のソースルーティング・プロトコル2007年2月
A node MUST associate a state with each node listed in its blacklist, specifying whether the unidirectionality of the link to that node is "questionable" or "probable". Each time the unreachability is positively determined, the node SHOULD set the state to "probable". After the unreachability has not been positively determined for some amount of time, the state SHOULD revert to "questionable". A node MAY expire entries for nodes from its blacklist after a reasonable amount of time.
ノードはブラックリストにリストアップされている各ノードに状態を関連づけなければなりません、そのノードへのリンクのunidirectionalityが「疑わしい」か「ありえそうであるか」を指定して。 「非-可到達性」が明確に断固としている各回、ノードSHOULDは「ありえそうに」状態を設定します。 「非-可到達性」がいつかの時間明確に決定していなかった後に、州のSHOULDは「疑わしく」戻ります。 ノードは妥当な時間の後にブラックリストからノードのためのエントリーを吐き出すかもしれません。
5. Additional Conceptual Data Structures for Flow State Extension
5. 流れ州の拡大のための追加概念的なデータ構造
This section defines additional conceptual data structures used by the optional "flow state" extension to DSR. In an implementation of the protocol, these data structures MUST be implemented in a manner consistent with the external behavior described in this document, but the choice of implementation used is otherwise unconstrained.
このセクションはDSRへの任意の「流れ状態」拡大で使用される追加概念的なデータ構造を定義します。 プロトコルの実装では、本書では説明される外部の振舞いと一致した方法でこれらのデータ構造を実装しなければなりませんが、そうでなければ、使用される実装の選択は自由です。
5.1. Flow Table
5.1. フロー・テーブル
A node implementing the flow state extension MUST implement a Flow Table or other data structure consistent with the external behavior described in this section. A node not implementing the flow state extension SHOULD NOT implement a Flow Table.
流れ状態が拡大であると実装するノードはこのセクションで説明される外部の振舞いと一致したFlow Tableか他のデータ構造を実装しなければなりません。 SHOULD NOTが実装する流れ州の拡大にFlow Tableを実装しないノード。
The Flow Table records information about flows from which packets recently have been sent or forwarded by this node. The table is indexed by a triple (IP Source Address, IP Destination Address, Flow ID), where Flow ID is a 16-bit number assigned by the source as described in Section 3.5.1. Each entry in the Flow Table contains the following fields:
Flow Tableは最近このノードでパケットを送るか、または進めた流れの情報を記録します。 三重(IP Source Address、IP Destination Address、Flow ID)によってテーブルは索引をつけられます、Flow IDがセクション3.5.1で説明されるようにソースによって割り当てられた16ビットの数であるところで。 Flow Tableの各エントリーは以下の分野を含んでいます:
- The MAC address of the next-hop node along this flow.
- この流れに沿った次のホップノードのMACアドレス。
- An indication of the outgoing network interface on this node to be
used in transmitting packets along this flow.
- このこの流れに沿ってパケットを伝える際に使用されるべきノードにおける外向的なネットワーク・インターフェースのしるし。
- The MAC address of the previous-hop node along this flow.
- この流れに沿った前のホップノードのMACアドレス。
- An indication of the network interface on this node from which
packets from that previous-hop node are received.
- その前のホップノードからのパケットが受け取られているこのノードにおけるネットワーク・インターフェースのしるし。
- A timeout after which this entry in the Flow Table MUST be
deleted.
- Flow Tableのこのエントリーを削除しなければならないタイムアウト。
- The expected value of the Hop Count field in the DSR Flow State
header for packets received for forwarding along this field (for
use with packets containing a DSR Flow State header).
- この分野(パケットがDSR Flow州ヘッダーを含んでいる使用のための)に沿った推進のために受け取られたパケットのためのDSR Flow州ヘッダーのHop Count分野の期待値。
Johnson, et al. Experimental [Page 34] RFC 4728 The Dynamic Source Routing Protocol February 2007
ジョンソン、他 ダイナミックな実験的な[34ページ]RFC4728のソースルーティング・プロトコル2007年2月
- An indication of whether or not this flow can be used as a default
flow for packets originated by this node (the Flow ID of a default
flow MUST be odd).
- パケットにデフォルト流動としてこの流れを使用できるかどうかしるしはこのノードで起因しました(デフォルト流動のFlow IDは変であるに違いありません)。
- The entry SHOULD record the complete source route for the flow.
(Nodes not recording the complete source route cannot participate
in Automatic Route Shortening.)
- エントリーSHOULDは流れのために完全な送信元経路を記録します。 (完全な送信元経路を記録しないノードはAutomatic Route Shorteningに参加できません。)
- The entry MAY contain a field recording the time this entry was
last used.
- エントリーはこのエントリーが最後に使用された時を記録する分野を含むかもしれません。
The entry MUST be deleted when its timeout expires.
タイムアウトが期限が切れるとき、エントリーを削除しなければなりません。
5.2. Automatic Route Shortening Table
5.2. 自動ルート短縮テーブル
A node implementing the flow state extension SHOULD implement an Automatic Route Shortening Table or other data structure consistent with the external behavior described in this section. A node not implementing the flow state extension SHOULD NOT implement an Automatic Route Shortening Table.
SHOULDが実装する流れ州の拡大にAutomatic Route Shortening Tableを実装するノードかこのセクションで説明される外部の振舞いと一致した他のデータ構造。 SHOULD NOTが実装する流れ州の拡大にAutomatic Route Shortening Tableを実装しないノード。
The Automatic Route Shortening Table records information about received packets for which Automatic Route Shortening may be possible. The table is indexed by a triple (IP Source Address, IP Destination Address, Flow ID). Each entry in the Automatic Route Shortening Table contains a list of (packet identifier, Hop Count) pairs for that flow. The packet identifier in the list may be any unique identifier for the received packet; for example, for IPv4 packets, the combination of the following fields from the packet's IP header MAY be used as a unique identifier for the packet: Source Address, Destination Address, Identification, Protocol, Fragment Offset, and Total Length. The Hop Count in the list in the entry is copied from the Hop Count field in the DSR Flow State header of the received packet for which this table entry was created. Any packet identifier SHOULD appear at most once in an entry's list, and this list item SHOULD record the minimum Hop Count value received for that packet (if the wireless signal strength or signal-to-noise ratio at which a packet is received is available to the DSR implementation in a node, the node MAY, for example, remember instead in this list the minimum Hop Count value for which the received packet's signal strength or signal-to-noise ratio exceeded some threshold).
Automatic Route Shortening TableはAutomatic Route Shorteningが可能であるかもしれない容認されたパケットの情報を記録します。 三重(IP Source Address、IP Destination Address、Flow ID)によってテーブルは索引をつけられます。 Automatic Route Shortening Tableの各エントリーはその流れのための(パケット識別子、Hop Count)組のリストを含んでいます。 リストのパケット識別子は容認されたパケットのためのどんなユニークな識別子であるかもしれませんも。 例えば、IPv4パケットに関して、パケットのIPヘッダーからの以下の分野の組み合わせはパケットにユニークな識別子として使用されるかもしれません: ソースアドレス、送付先アドレス、識別、プロトコル、断片オフセット、および全長。 エントリーにおけるリストのHop Countはこのテーブル項目が作成された容認されたパケットのDSR Flow州ヘッダーのHop Count分野からコピーされます。 どんなパケット識別子SHOULDもエントリーのリストに高々一度現れます、そして、このリスト項目SHOULDはそのパケットのために最小のHop Count対価領収を記録します(ノードのDSR実装について、パケットが受け取られているワイヤレスの信号強度かSN比があるなら、例えば、ノードは代わりに、このリストで容認されたパケットの信号強度かSN比が何らかの敷居を超えていた最小のHop Count値を覚えているかもしれません)。
Space in the Automatic Route Shortening Table of a node MAY be dynamically managed by any local algorithm at the node. For example, in order to limit the amount of memory used to store the table, any existing entry MAY be deleted at any time, and the number of packets listed in each entry MAY be limited. However, when reclaiming space in the table, nodes SHOULD favor retaining information about more
ノードのAutomatic Route Shortening Tableのスペースはノードのどんなローカルのアルゴリズムでもダイナミックに管理されるかもしれません。 例えば、どんな既存のエントリーもいつでもテーブルを保存するのに使用されるメモリー容量を制限するために削除されるかもしれません、そして、各エントリーに記載されたパケットの数は制限されるかもしれません。 しかしながら、テーブルのスペースを取り戻すとき、ノードSHOULDは、情報をおよそさらに保有するのを支持します。
Johnson, et al. Experimental [Page 35] RFC 4728 The Dynamic Source Routing Protocol February 2007
ジョンソン、他 ダイナミックな実験的な[35ページ]RFC4728のソースルーティング・プロトコル2007年2月
flows in the table rather than about more packets listed in each entry in the table, as long as at least the listing of some small number of packets (e.g., 3) can be retained in each entry.
より多くのパケットに関してというよりむしろテーブルの流れはテーブルの各エントリーに記載しました、各エントリーで少なくとも何らかの少ない数のパケット(例えば、3)のリストを保有できる限り。
5.3. Default Flow ID Table
5.3. デフォルト流れIDテーブル
A node implementing the flow state extension MUST implement a Default Flow Table or other data structure consistent with the external behavior described in this section. A node not implementing the flow state extension SHOULD NOT implement a Default Flow Table.
A node implementing the flow state extension MUST implement a Default Flow Table or other data structure consistent with the external behavior described in this section. A node not implementing the flow state extension SHOULD NOT implement a Default Flow Table.
For each (IP Source Address, IP Destination Address) pair for which a node forwards packets, the node MUST record:
For each (IP Source Address, IP Destination Address) pair for which a node forwards packets, the node MUST record:
- The largest odd Flow ID value seen.
- The largest odd Flow ID value seen.
- The time at which all the corresponding flows that are forwarded
by this node expire.
- The time at which all the corresponding flows that are forwarded by this node expire.
- The current default Flow ID.
- The current default Flow ID.
- A flag indicating whether or not the current default Flow ID is
valid.
- A flag indicating whether or not the current default Flow ID is valid.
If a node deletes this record for an (IP Source Address, IP Destination Address) pair, it MUST also delete all Flow Table entries for that pair. Nodes MUST delete table entries if all of this (IP Source Address, IP Destination Address) pair's flows that are forwarded by this node expire.
If a node deletes this record for an (IP Source Address, IP Destination Address) pair, it MUST also delete all Flow Table entries for that pair. Nodes MUST delete table entries if all of this (IP Source Address, IP Destination Address) pair's flows that are forwarded by this node expire.
6. DSR Options Header Format
6. DSR Options Header Format
The Dynamic Source Routing protocol makes use of a special header carrying control information that can be included in any existing IP packet. This DSR Options header in a packet contains a small fixed- sized, 4-octet portion, followed by a sequence of zero or more DSR options carrying optional information. The end of the sequence of DSR options in the DSR Options header is implied by the total length of the DSR Options header.
The Dynamic Source Routing protocol makes use of a special header carrying control information that can be included in any existing IP packet. This DSR Options header in a packet contains a small fixed- sized, 4-octet portion, followed by a sequence of zero or more DSR options carrying optional information. The end of the sequence of DSR options in the DSR Options header is implied by the total length of the DSR Options header.
For IPv4, the DSR Options header MUST immediately follow the IP header in the packet. (If a Hop-by-Hop Options extension header, as defined in IPv6 [RFC2460], becomes defined for IPv4, the DSR Options header MUST immediately follow the Hop-by-Hop Options extension header, if one is present in the packet, and MUST otherwise immediately follow the IP header.)
For IPv4, the DSR Options header MUST immediately follow the IP header in the packet. (If a Hop-by-Hop Options extension header, as defined in IPv6 [RFC2460], becomes defined for IPv4, the DSR Options header MUST immediately follow the Hop-by-Hop Options extension header, if one is present in the packet, and MUST otherwise immediately follow the IP header.)
Johnson, et al. Experimental [Page 36] RFC 4728 The Dynamic Source Routing Protocol February 2007
Johnson, et al. Experimental [Page 36] RFC 4728 The Dynamic Source Routing Protocol February 2007
To add a DSR Options header to a packet, the DSR Options header is inserted following the packet's IP header, before any following header such as a traditional (e.g., TCP or UDP) transport layer header. Specifically, the Protocol field in the IP header is used to indicate that a DSR Options header follows the IP header, and the Next Header field in the DSR Options header is used to indicate the type of protocol header (such as a transport layer header) following the DSR Options header.
To add a DSR Options header to a packet, the DSR Options header is inserted following the packet's IP header, before any following header such as a traditional (e.g., TCP or UDP) transport layer header. Specifically, the Protocol field in the IP header is used to indicate that a DSR Options header follows the IP header, and the Next Header field in the DSR Options header is used to indicate the type of protocol header (such as a transport layer header) following the DSR Options header.
If any headers follow the DSR Options header in a packet, the total length of the DSR Options header (and thus the total, combined length of all DSR options present) MUST be a multiple of 4 octets. This requirement preserves the alignment of these following headers in the packet.
If any headers follow the DSR Options header in a packet, the total length of the DSR Options header (and thus the total, combined length of all DSR options present) MUST be a multiple of 4 octets. This requirement preserves the alignment of these following headers in the packet.
6.1. Fixed Portion of DSR Options Header
6.1. Fixed Portion of DSR Options Header
The fixed portion of the DSR Options header is used to carry information that must be present in any DSR Options header. This fixed portion of the DSR Options header has the following format:
The fixed portion of the DSR Options header is used to carry information that must be present in any DSR Options header. This fixed portion of the DSR Options header has the following format:
0 1 2 3
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Next Header |F| Reserved | Payload Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
. .
. Options .
. .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3 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 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Next Header |F| Reserved | Payload Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ . . . Options . . . +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Next Header
Next Header
8-bit selector. Identifies the type of header immediately
following the DSR Options header. Uses the same values as the
IPv4 Protocol field [RFC1700]. If no header follows, then Next
Header MUST have the value 59, "No Next Header" [RFC2460].
8-bit selector. Identifies the type of header immediately following the DSR Options header. Uses the same values as the IPv4 Protocol field [RFC1700]. If no header follows, then Next Header MUST have the value 59, "No Next Header" [RFC2460].
Flow State Header (F)
Flow State Header (F)
Flag bit. MUST be set to 0. This bit is set in a DSR Flow
State header (Section 7.1) and clear in a DSR Options header.
Flag bit. MUST be set to 0. This bit is set in a DSR Flow State header (Section 7.1) and clear in a DSR Options header.
Reserved
Reserved
MUST be sent as 0 and ignored on reception.
MUST be sent as 0 and ignored on reception.
Johnson, et al. Experimental [Page 37] RFC 4728 The Dynamic Source Routing Protocol February 2007
Johnson, et al. Experimental [Page 37] RFC 4728 The Dynamic Source Routing Protocol February 2007
Payload Length
Payload Length
The length of the DSR Options header, excluding the 4-octet
fixed portion. The value of the Payload Length field defines
the total length of all options carried in the DSR Options
header.
The length of the DSR Options header, excluding the 4-octet fixed portion. The value of the Payload Length field defines the total length of all options carried in the DSR Options header.
Options
Options
Variable-length field; the length of the Options field is
specified by the Payload Length field in this DSR Options
header. Contains one or more pieces of optional information
(DSR options), encoded in type-length-value (TLV) format (with
the exception of the Pad1 option described in Section 6.8).
Variable-length field; the length of the Options field is specified by the Payload Length field in this DSR Options header. Contains one or more pieces of optional information (DSR options), encoded in type-length-value (TLV) format (with the exception of the Pad1 option described in Section 6.8).
The placement of DSR options following the fixed portion of the DSR Options header MAY be padded for alignment. However, due to the typically limited available wireless bandwidth in ad hoc networks, this padding is not required, and receiving nodes MUST NOT expect options within a DSR Options header to be aligned.
The placement of DSR options following the fixed portion of the DSR Options header MAY be padded for alignment. However, due to the typically limited available wireless bandwidth in ad hoc networks, this padding is not required, and receiving nodes MUST NOT expect options within a DSR Options header to be aligned.
Each DSR option is assigned a unique Option Type code. The most significant 3 bits (that is, Option Type & 0xE0) allow a node not implementing processing for this Option Type value to behave in the manner closest to correct for that type:
Each DSR option is assigned a unique Option Type code. The most significant 3 bits (that is, Option Type & 0xE0) allow a node not implementing processing for this Option Type value to behave in the manner closest to correct for that type:
- The most significant bit in the Option Type value (that is, Option
Type & 0x80) represents whether or not a node receiving this
Option Type (when the node does not implement processing for this
Option Type) SHOULD respond to such a DSR option with a Route
Error of type OPTION_NOT_SUPPORTED, except that such a Route Error
SHOULD never be sent in response to a packet containing a Route
Request option.
- The most significant bit in the Option Type value (that is, Option Type & 0x80) represents whether or not a node receiving this Option Type (when the node does not implement processing for this Option Type) SHOULD respond to such a DSR option with a Route Error of type OPTION_NOT_SUPPORTED, except that such a Route Error SHOULD never be sent in response to a packet containing a Route Request option.
- The two following bits in the Option Type value (that is, Option
Type & 0x60) are a two-bit field indicating how such a node that
does not support this Option Type MUST process the packet:
- The two following bits in the Option Type value (that is, Option Type & 0x60) are a two-bit field indicating how such a node that does not support this Option Type MUST process the packet:
00 = Ignore Option
01 = Remove Option
10 = Mark Option
11 = Drop Packet
00 = Ignore Option 01 = Remove Option 10 = Mark Option 11 = Drop Packet
When these 2 bits are 00 (that is, Option Type & 0x60 == 0), a
node not implementing processing for that Option Type MUST use the
Opt Data Len field to skip over the option and continue
processing. When these 2 bits are 01 (that is, Option Type & 0x60
== 0x20), a node not implementing processing for that Option Type
When these 2 bits are 00 (that is, Option Type & 0x60 == 0), a node not implementing processing for that Option Type MUST use the Opt Data Len field to skip over the option and continue processing. When these 2 bits are 01 (that is, Option Type & 0x60 == 0x20), a node not implementing processing for that Option Type
Johnson, et al. Experimental [Page 38] RFC 4728 The Dynamic Source Routing Protocol February 2007
Johnson, et al. Experimental [Page 38] RFC 4728 The Dynamic Source Routing Protocol February 2007
MUST use the Opt Data Len field to remove the option from the
packet and continue processing as if the option had not been
included in the received packet. When these 2 bits are 10 (that
is, Option Type & 0x60 == 0x40), a node not implementing
processing for that Option Type MUST set the most significant bit
following the Opt Data Len field, MUST ignore the contents of the
option using the Opt Data Len field, and MUST continue processing
the packet. Finally, when these 2 bits are 11 (that is, Option
Type & 0x60 == 0x60), a node not implementing processing for that
Option Type MUST drop the packet.
MUST use the Opt Data Len field to remove the option from the packet and continue processing as if the option had not been included in the received packet. When these 2 bits are 10 (that is, Option Type & 0x60 == 0x40), a node not implementing processing for that Option Type MUST set the most significant bit following the Opt Data Len field, MUST ignore the contents of the option using the Opt Data Len field, and MUST continue processing the packet. Finally, when these 2 bits are 11 (that is, Option Type & 0x60 == 0x60), a node not implementing processing for that Option Type MUST drop the packet.
The following types of DSR options are defined in this document for use within a DSR Options header:
The following types of DSR options are defined in this document for use within a DSR Options header:
- Route Request option (Section 6.2)
- Route Request option (Section 6.2)
- Route Reply option (Section 6.3)
- Route Reply option (Section 6.3)
- Route Error option (Section 6.4)
- Route Error option (Section 6.4)
- Acknowledgement Request option (Section 6.5)
- Acknowledgement Request option (Section 6.5)
- Acknowledgement option (Section 6.6)
- Acknowledgement option (Section 6.6)
- DSR Source Route option (Section 6.7)
- DSR Source Route option (Section 6.7)
- Pad1 option (Section 6.8)
- Pad1 option (Section 6.8)
- PadN option (Section 6.9)
- PadN option (Section 6.9)
In addition, Section 7 specifies further DSR options for use with the optional DSR flow state extension.
In addition, Section 7 specifies further DSR options for use with the optional DSR flow state extension.
Johnson, et al. Experimental [Page 39] RFC 4728 The Dynamic Source Routing Protocol February 2007
Johnson, et al. Experimental [Page 39] RFC 4728 The Dynamic Source Routing Protocol February 2007
6.2. Route Request Option
6.2. Route Request Option
The Route Request option in a DSR Options header is encoded as follows:
The Route Request option in a DSR Options header is encoded as follows:
0 1 2 3
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Option Type | Opt Data Len | Identification |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Target Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Address[1] |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Address[2] |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Address[n] |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3 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 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Option Type | Opt Data Len | Identification | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Target Address | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Address[1] | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Address[2] | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Address[n] | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
IP fields:
IP fields:
Source Address
Source Address
MUST be set to the address of the node originating this packet.
Intermediate nodes that retransmit the packet to propagate the
Route Request MUST NOT change this field.
MUST be set to the address of the node originating this packet. Intermediate nodes that retransmit the packet to propagate the Route Request MUST NOT change this field.
Destination Address
Destination Address
MUST be set to the IP limited broadcast address
(255.255.255.255).
MUST be set to the IP limited broadcast address (255.255.255.255).
Hop Limit (TTL)
Hop Limit (TTL)
MAY be varied from 1 to 255, for example, to implement non-
propagating Route Requests and Route Request expanding-ring
searches (Section 3.3.3).
MAY be varied from 1 to 255, for example, to implement non- propagating Route Requests and Route Request expanding-ring searches (Section 3.3.3).
Route Request fields:
Route Request fields:
Option Type
Option Type
1. Nodes not understanding this option will ignore this
option.
1. Nodes not understanding this option will ignore this option.
Johnson, et al. Experimental [Page 40] RFC 4728 The Dynamic Source Routing Protocol February 2007
Johnson, et al. Experimental [Page 40] RFC 4728 The Dynamic Source Routing Protocol February 2007
Opt Data Len
Opt Data Len
8-bit unsigned integer. Length of the option, in octets,
excluding the Option Type and Opt Data Len fields. MUST be set
equal to (4 * n) + 6, where n is the number of addresses in the
Route Request Option.
8-bit unsigned integer. Length of the option, in octets, excluding the Option Type and Opt Data Len fields. MUST be set equal to (4 * n) + 6, where n is the number of addresses in the Route Request Option.
Identification
Identification
A unique value generated by the initiator (original sender) of
the Route Request. Nodes initiating a Route Request generate a
new Identification value for each Route Request, for example
based on a sequence number counter of all Route Requests
initiated by the node.
A unique value generated by the initiator (original sender) of the Route Request. Nodes initiating a Route Request generate a new Identification value for each Route Request, for example based on a sequence number counter of all Route Requests initiated by the node.
This value allows a receiving node to determine whether it has
recently seen a copy of this Route Request. If this
Identification value (for this IP Source address and Target
Address) is found by this receiving node in its Route Request
Table (in the cache of Identification values in the entry there
for this initiating node), this receiving node MUST discard the
Route Request. When a Route Request is propagated, this field
MUST be copied from the received copy of the Route Request
being propagated.
This value allows a receiving node to determine whether it has recently seen a copy of this Route Request. If this Identification value (for this IP Source address and Target Address) is found by this receiving node in its Route Request Table (in the cache of Identification values in the entry there for this initiating node), this receiving node MUST discard the Route Request. When a Route Request is propagated, this field MUST be copied from the received copy of the Route Request being propagated.
Target Address
Target Address
The address of the node that is the target of the Route
Request.
The address of the node that is the target of the Route Request.
Address[1..n]
Address[1..n]
Address[i] is the IPv4 address of the i-th node recorded in the
Route Request option. The address given in the Source Address
field in the IP header is the address of the initiator of the
Route Discovery and MUST NOT be listed in the Address[i]
fields; the address given in Address[1] is thus the IPv4
address of the first node on the path after the initiator. The
number of addresses present in this field is indicated by the
Opt Data Len field in the option (n = (Opt Data Len - 6) / 4).
Each node propagating the Route Request adds its own address to
this list, increasing the Opt Data Len value by 4 octets.
Address[i] is the IPv4 address of the i-th node recorded in the Route Request option. The address given in the Source Address field in the IP header is the address of the initiator of the Route Discovery and MUST NOT be listed in the Address[i] fields; the address given in Address[1] is thus the IPv4 address of the first node on the path after the initiator. The number of addresses present in this field is indicated by the Opt Data Len field in the option (n = (Opt Data Len - 6) / 4). Each node propagating the Route Request adds its own address to this list, increasing the Opt Data Len value by 4 octets.
The Route Request option MUST NOT appear more than once within a DSR Options header.
The Route Request option MUST NOT appear more than once within a DSR Options header.
Johnson, et al. Experimental [Page 41] RFC 4728 The Dynamic Source Routing Protocol February 2007
Johnson, et al. Experimental [Page 41] RFC 4728 The Dynamic Source Routing Protocol February 2007
6.3. Route Reply Option
6.3. Route Reply Option
The Route Reply option in a DSR Options header is encoded as follows:
The Route Reply option in a DSR Options header is encoded as follows:
0 1 2 3
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Option Type | Opt Data Len |L| Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Address[1] |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Address[2] |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Address[n] |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3 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 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Option Type | Opt Data Len |L| Reserved | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Address[1] | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Address[2] | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Address[n] | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
IP fields:
IP fields:
Source Address
Source Address
Set to the address of the node sending the Route Reply. In the
case of a node sending a reply from its Route Cache (Section
3.3.2) or sending a gratuitous Route Reply (Section 3.4.3),
this address can differ from the address that was the target of
the Route Discovery.
Set to the address of the node sending the Route Reply. In the case of a node sending a reply from its Route Cache (Section 3.3.2) or sending a gratuitous Route Reply (Section 3.4.3), this address can differ from the address that was the target of the Route Discovery.
Destination Address
Destination Address
MUST be set to the address of the source node of the route
being returned. Copied from the Source Address field of the
Route Request generating the Route Reply or, in the case of a
gratuitous Route Reply, copied from the Source Address field of
the data packet triggering the gratuitous Reply.
MUST be set to the address of the source node of the route being returned. Copied from the Source Address field of the Route Request generating the Route Reply or, in the case of a gratuitous Route Reply, copied from the Source Address field of the data packet triggering the gratuitous Reply.
Route Reply fields:
Route Reply fields:
Option Type
Option Type
2. Nodes not understanding this option will ignore this
option.
2. Nodes not understanding this option will ignore this option.
Johnson, et al. Experimental [Page 42] RFC 4728 The Dynamic Source Routing Protocol February 2007
Johnson, et al. Experimental [Page 42] RFC 4728 The Dynamic Source Routing Protocol February 2007
Opt Data Len
Opt Data Len
8-bit unsigned integer. Length of the option, in octets,
excluding the Option Type and Opt Data Len fields. MUST be set
equal to (4 * n) + 1, where n is the number of addresses in the
Route Reply Option.
8-bit unsigned integer. Length of the option, in octets, excluding the Option Type and Opt Data Len fields. MUST be set equal to (4 * n) + 1, where n is the number of addresses in the Route Reply Option.
Last Hop External (L)
Last Hop External (L)
Set to indicate that the last hop given by the Route Reply (the
link from Address[n-1] to Address[n]) is actually an arbitrary
path in a network external to the DSR network; the exact route
outside the DSR network is not represented in the Route Reply.
Nodes caching this hop in their Route Cache MUST flag the
cached hop with the External flag. Such hops MUST NOT be
returned in a cached Route Reply generated from this Route
Cache entry, and selection of routes from the Route Cache to
route a packet being sent SHOULD prefer routes that contain no
hops flagged as External.
Set to indicate that the last hop given by the Route Reply (the link from Address[n-1] to Address[n]) is actually an arbitrary path in a network external to the DSR network; the exact route outside the DSR network is not represented in the Route Reply. Nodes caching this hop in their Route Cache MUST flag the cached hop with the External flag. Such hops MUST NOT be returned in a cached Route Reply generated from this Route Cache entry, and selection of routes from the Route Cache to route a packet being sent SHOULD prefer routes that contain no hops flagged as External.
Reserved
Reserved
MUST be sent as 0 and ignored on reception.
MUST be sent as 0 and ignored on reception.
Address[1..n]
Address[1..n]
The source route being returned by the Route Reply. The route
indicates a sequence of hops, originating at the source node
specified in the Destination Address field of the IP header of
the packet carrying the Route Reply, through each of the
Address[i] nodes in the order listed in the Route Reply, ending
at the node indicated by Address[n]. The number of addresses
present in the Address[1..n] field is indicated by the Opt Data
Len field in the option (n = (Opt Data Len - 1) / 4).
The source route being returned by the Route Reply. The route indicates a sequence of hops, originating at the source node specified in the Destination Address field of the IP header of the packet carrying the Route Reply, through each of the Address[i] nodes in the order listed in the Route Reply, ending at the node indicated by Address[n]. The number of addresses present in the Address[1..n] field is indicated by the Opt Data Len field in the option (n = (Opt Data Len - 1) / 4).
A Route Reply option MAY appear one or more times within a DSR Options header.
A Route Reply option MAY appear one or more times within a DSR Options header.
Johnson, et al. Experimental [Page 43] RFC 4728 The Dynamic Source Routing Protocol February 2007
Johnson, et al. Experimental [Page 43] RFC 4728 The Dynamic Source Routing Protocol February 2007
6.4. Route Error Option
6.4. Route Error Option
The Route Error option in a DSR Options header is encoded as follows:
The Route Error option in a DSR Options header is encoded as follows:
0 1 2 3
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Option Type | Opt Data Len | Error Type |Reservd|Salvage|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Error Source Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Error Destination Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
. .
. Type-Specific Information .
. .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3 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 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Option Type | Opt Data Len | Error Type |Reservd|Salvage| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Error Source Address | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Error Destination Address | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ . . . Type-Specific Information . . . +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Option Type
Option Type
3. Nodes not understanding this option will ignore this
option.
3. Nodes not understanding this option will ignore this option.
Opt Data Len
Opt Data Len
8-bit unsigned integer. Length of the option, in octets,
excluding the Option Type and Opt Data Len fields.
8-bit unsigned integer. Length of the option, in octets, excluding the Option Type and Opt Data Len fields.
For the current definition of the Route Error option,
this field MUST be set to 10, plus the size of any
Type-Specific Information present in the Route Error. Further
extensions to the Route Error option format may also be
included after the Type-Specific Information portion of the
Route Error option specified above. The presence of such
extensions will be indicated by the Opt Data Len field.
When the Opt Data Len is greater than that required for
the fixed portion of the Route Error plus the necessary
Type-Specific Information as indicated by the Option Type
value in the option, the remaining octets are interpreted as
extensions. Currently, no such further extensions have been
defined.
For the current definition of the Route Error option, this field MUST be set to 10, plus the size of any Type-Specific Information present in the Route Error. Further extensions to the Route Error option format may also be included after the Type-Specific Information portion of the Route Error option specified above. The presence of such extensions will be indicated by the Opt Data Len field. When the Opt Data Len is greater than that required for the fixed portion of the Route Error plus the necessary Type-Specific Information as indicated by the Option Type value in the option, the remaining octets are interpreted as extensions. Currently, no such further extensions have been defined.
Error Type
Error Type
The type of error encountered. Currently, the following type
values are defined:
The type of error encountered. Currently, the following type values are defined:
Johnson, et al. Experimental [Page 44] RFC 4728 The Dynamic Source Routing Protocol February 2007
Johnson, et al. Experimental [Page 44] RFC 4728 The Dynamic Source Routing Protocol February 2007
1 = NODE_UNREACHABLE
2 = FLOW_STATE_NOT_SUPPORTED
3 = OPTION_NOT_SUPPORTED
1 = NODE_UNREACHABLE 2 = FLOW_STATE_NOT_SUPPORTED 3 = OPTION_NOT_SUPPORTED
Other values of the Error Type field are reserved for future
use.
Other values of the Error Type field are reserved for future use.
Reservd
Reservd
Reserved. MUST be sent as 0 and ignored on reception.
Reserved. MUST be sent as 0 and ignored on reception.
Salvage
Salvage
A 4-bit unsigned integer. Copied from the Salvage field in the
DSR Source Route option of the packet triggering the Route
Error.
A 4-bit unsigned integer. Copied from the Salvage field in the DSR Source Route option of the packet triggering the Route Error.
The "total salvage count" of the Route Error option is derived
from the value in the Salvage field of this Route Error option
and all preceding Route Error options in the packet as follows:
the total salvage count is the sum of, for each such Route
Error option, one plus the value in the Salvage field of that
Route Error option.
The "total salvage count" of the Route Error option is derived from the value in the Salvage field of this Route Error option and all preceding Route Error options in the packet as follows: the total salvage count is the sum of, for each such Route Error option, one plus the value in the Salvage field of that Route Error option.
Error Source Address
Error Source Address
The address of the node originating the Route Error (e.g., the
node that attempted to forward a packet and discovered the link
failure).
The address of the node originating the Route Error (e.g., the node that attempted to forward a packet and discovered the link failure).
Error Destination Address
Error Destination Address
The address of the node to which the Route Error must be
delivered. For example, when the Error Type field is set to
NODE_UNREACHABLE, this field will be set to the address of the
node that generated the routing information claiming that the
hop from the Error Source Address to Unreachable Node Address
(specified in the Type-Specific Information) was a valid hop.
The address of the node to which the Route Error must be delivered. For example, when the Error Type field is set to NODE_UNREACHABLE, this field will be set to the address of the node that generated the routing information claiming that the hop from the Error Source Address to Unreachable Node Address (specified in the Type-Specific Information) was a valid hop.
Type-Specific Information
Type-Specific Information
Information specific to the Error Type of this Route Error
message.
Information specific to the Error Type of this Route Error message.
A Route Error option MAY appear one or more times within a DSR Options header.
A Route Error option MAY appear one or more times within a DSR Options header.
Johnson, et al. Experimental [Page 45] RFC 4728 The Dynamic Source Routing Protocol February 2007
Johnson, et al. Experimental [Page 45] RFC 4728 The Dynamic Source Routing Protocol February 2007
6.4.1. Node Unreachable Type-Specific Information
6.4.1. Node Unreachable Type-Specific Information
When the Route Error is of type NODE_UNREACHABLE, the Type-Specific Information field is defined as follows:
When the Route Error is of type NODE_UNREACHABLE, the Type-Specific Information field is defined as follows:
0 1 2 3
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Unreachable Node Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3 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 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Unreachable Node Address | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Unreachable Node Address
Unreachable Node Address
The IP address of the node that was found to be unreachable
(the next-hop neighbor to which the node with address
Error Source Address was attempting to transmit the packet).
The IP address of the node that was found to be unreachable (the next-hop neighbor to which the node with address Error Source Address was attempting to transmit the packet).
6.4.2. Flow State Not Supported Type-Specific Information
6.4.2. Flow State Not Supported Type-Specific Information
When the Route Error is of type FLOW_STATE_NOT_SUPPORTED, the Type-Specific Information field is empty.
When the Route Error is of type FLOW_STATE_NOT_SUPPORTED, the Type-Specific Information field is empty.
6.4.3. Option Not Supported Type-Specific Information
6.4.3. Option Not Supported Type-Specific Information
When the Route Error is of type OPTION_NOT_SUPPORTED, the Type-Specific Information field is defined as follows:
When the Route Error is of type OPTION_NOT_SUPPORTED, the Type-Specific Information field is defined as follows:
0 1 2 3 4 5 6 7 +-+-+-+-+-+-+-+-+ |Unsupported Opt| +-+-+-+-+-+-+-+-+
0 1 2 3 4 5 6 7 +-+-+-+-+-+-+-+-+ |Unsupported Opt| +-+-+-+-+-+-+-+-+
Unsupported Opt
Unsupported Opt
The Option Type of option triggering the Route Error.
The Option Type of option triggering the Route Error.
6.5. Acknowledgement Request Option
6.5. Acknowledgement Request Option
The Acknowledgement Request option in a DSR Options header is encoded as follows:
The Acknowledgement Request option in a DSR Options header is encoded as follows:
0 1 2 3
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Option Type | Opt Data Len | Identification |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3 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 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Option Type | Opt Data Len | Identification | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Johnson, et al. Experimental [Page 46] RFC 4728 The Dynamic Source Routing Protocol February 2007
Johnson, et al. Experimental [Page 46] RFC 4728 The Dynamic Source Routing Protocol February 2007
Option Type
Option Type
160. Nodes not understanding this option will remove the
option and return a Route Error.
160. Nodes not understanding this option will remove the option and return a Route Error.
Opt Data Len
Opt Data Len
8-bit unsigned integer. Length of the option, in octets,
excluding the Option Type and Opt Data Len fields.
8-bit unsigned integer. Length of the option, in octets, excluding the Option Type and Opt Data Len fields.
Identification
Identification
The Identification field is set to a unique value and is copied
into the Identification field of the Acknowledgement option
when returned by the node receiving the packet over this hop.
The Identification field is set to a unique value and is copied into the Identification field of the Acknowledgement option when returned by the node receiving the packet over this hop.
An Acknowledgement Request option MUST NOT appear more than once within a DSR Options header.
An Acknowledgement Request option MUST NOT appear more than once within a DSR Options header.
6.6. Acknowledgement Option
6.6. Acknowledgement Option
The Acknowledgement option in a DSR Options header is encoded as follows:
The Acknowledgement option in a DSR Options header is encoded as follows:
0 1 2 3
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Option Type | Opt Data Len | Identification |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ACK Source Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ACK Destination Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3 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 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Option Type | Opt Data Len | Identification | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | ACK Source Address | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | ACK Destination Address | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Option Type
Option Type
32. Nodes not understanding this option will remove the
option.
32. Nodes not understanding this option will remove the option.
Opt Data Len
Opt Data Len
8-bit unsigned integer. Length of the option, in octets,
excluding the Option Type and Opt Data Len fields.
8-bit unsigned integer. Length of the option, in octets, excluding the Option Type and Opt Data Len fields.
Identification
Identification
Copied from the Identification field of the Acknowledgement
Request option of the packet being acknowledged.
Copied from the Identification field of the Acknowledgement Request option of the packet being acknowledged.
Johnson, et al. Experimental [Page 47] RFC 4728 The Dynamic Source Routing Protocol February 2007
Johnson, et al. Experimental [Page 47] RFC 4728 The Dynamic Source Routing Protocol February 2007
ACK Source Address
ACK Source Address
The address of the node originating the acknowledgement.
The address of the node originating the acknowledgement.
ACK Destination Address
ACK Destination Address
The address of the node to which the acknowledgement is to be
delivered.
The address of the node to which the acknowledgement is to be delivered.
An Acknowledgement option MAY appear one or more times within a DSR Options header.
An Acknowledgement option MAY appear one or more times within a DSR Options header.
6.7. DSR Source Route Option
6.7. DSR Source Route Option
The DSR Source Route option in a DSR Options header is encoded as follows:
The DSR Source Route option in a DSR Options header is encoded as follows:
0 1 2 3
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Option Type | Opt Data Len |F|L|Reservd|Salvage| Segs Left |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Address[1] |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Address[2] |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Address[n] |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3 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 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | オプションタイプ| Dataレンを選んでください。|F|L|Reservd|海難救助| Segsは残っています。| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | アドレス[1]| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | アドレス[2]| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | アドレス[n]| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Option Type
オプションタイプ
96. Nodes not understanding this option will drop the packet.
96. このオプションを理解していないノードがパケットを下げるでしょう。
Opt Data Len
Dataレンを選んでください。
8-bit unsigned integer. Length of the option, in octets,
excluding the Option Type and Opt Data Len fields. For the
format of the DSR Source Route option defined here, this field
MUST be set to the value (n * 4) + 2, where n is the number of
addresses present in the Address[i] fields.
8ビットの符号のない整数。 Option TypeとOpt Dataレン分野を除いた八重奏における、オプションの長さ。 ここで定義されたDSR Source Routeオプションの形式において、値(n*4)+2にこの分野を設定しなければなりません。そこでは、nがAddress[i]分野の現在のアドレスの数です。
First Hop External (F)
まず最初に、外部であることの形で、跳んでください。(F)
Set to indicate that the first hop indicated by the DSR Source
Route option is actually an arbitrary path in a network
external to the DSR network; the exact route outside the DSR
セットして、DSR Source Routeオプションで示された最初のホップが実際にDSRネットワークへの外部のネットワークで任意の経路であることを示してください。 DSRの外の正確なルート
Johnson, et al. Experimental [Page 48] RFC 4728 The Dynamic Source Routing Protocol February 2007
ジョンソン、他 ダイナミックな実験的な[48ページ]RFC4728のソースルーティング・プロトコル2007年2月
network is not represented in the DSR Source Route option.
Nodes caching this hop in their Route Cache MUST flag the
cached hop with the External flag. Such hops MUST NOT be
returned in a Route Reply generated from this Route Cache
entry, and selection of routes from the Route Cache to route a
packet being sent SHOULD prefer routes that contain no hops
flagged as External.
ネットワークはDSR Source Routeオプションで代表されません。 それらのRoute CacheでこのホップをキャッシュするノードはキャッシュされたホップにExternal旗で旗を揚げさせなければなりません。 送られたSHOULDがホップを全く含まないルートを好むということであることがExternalとして旗を揚げさせたパケットを発送するためにRoute CacheからこのRoute Cacheエントリーから生成されたRoute Reply、およびルートの品揃えでそのようなホップを返してはいけません。
Last Hop External (L)
最後に、外部であることの形で、跳んでください。(L)
Set to indicate that the last hop indicated by the DSR Source
Route option is actually an arbitrary path in a network
external to the DSR network; the exact route outside the DSR
network is not represented in the DSR Source Route option.
Nodes caching this hop in their Route Cache MUST flag the
cached hop with the External flag. Such hops MUST NOT be
returned in a Route Reply generated from this Route Cache
entry, and selection of routes from the Route Cache to route a
packet being sent SHOULD prefer routes that contain no hops
flagged as External.
セットして、DSR Source Routeオプションで示された最後のホップが実際にDSRネットワークへの外部のネットワークで任意の経路であることを示してください。 DSRネットワークの外における正確なルートはDSR Source Routeオプションで表されません。 それらのRoute CacheでこのホップをキャッシュするノードはキャッシュされたホップにExternal旗で旗を揚げさせなければなりません。 送られたSHOULDがホップを全く含まないルートを好むということであることがExternalとして旗を揚げさせたパケットを発送するためにRoute CacheからこのRoute Cacheエントリーから生成されたRoute Reply、およびルートの品揃えでそのようなホップを返してはいけません。
Reserved
予約されます。
MUST be sent as 0 and ignored on reception.
0として送られて、レセプションで無視しなければなりません。
Salvage
海難救助
A 4-bit unsigned integer. Count of number of times that this
packet has been salvaged as a part of DSR routing (Section
3.4.1).
4ビットの符号のない整数。 このパケットがDSRルーティング(セクション3.4.1)の一部として回収されたという回の数のカウント。
Segments Left (Segs Left)
セグメントは残っています。(あとSegs)
Number of route segments remaining, i.e., number of explicitly
listed intermediate nodes still to be visited before reaching
the final destination.
ルートセグメントの残り(すなわち、最終的な目的地に達する前にまだ訪問されるべき中間的明らかに記載されたノードの数)の数。
Address[1..n]
アドレス[1..n]
The sequence of addresses of the source route. In routing and
forwarding the packet, the source route is processed as
described in Sections 8.1.3 and 8.1.5. The number of addresses
present in the Address[1..n] field is indicated by the Opt Data
Len field in the option (n = (Opt Data Len - 2) / 4).
送信元経路のアドレスの系列。 ルーティングとパケットを進める際に、送信元経路はセクション8.1.3と8.1で.5に説明されるように処理されます。 Address[1..n]分野の現在のアドレスの数はオプションにおけるOpt Dataレン分野によって示されます(nは(Dataレンを選んでください--2)という/4と等しいです)。
When forwarding a packet along a DSR source route using a DSR Source Route option in the packet's DSR Options header, the Destination Address field in the packet's IP header is always set to the address
DSR送信元経路に沿ってパケットのDSR OptionsヘッダーでDSR Source Routeオプションを使用することでパケットを進めるとき、パケットのIPヘッダーのDestination Address分野はいつもアドレスに設定されます。
Johnson, et al. Experimental [Page 49] RFC 4728 The Dynamic Source Routing Protocol February 2007
ジョンソン、他 ダイナミックな実験的な[49ページ]RFC4728のソースルーティング・プロトコル2007年2月
of the packet's ultimate destination. A node receiving a packet containing a DSR Options header with a DSR Source Route option MUST examine the indicated source route to determine if it is the intended next-hop node for the packet and how to forward the packet, as defined in Sections 8.1.4 and 8.1.5.
パケットの最終仕向地について。 DSR Source RouteオプションでDSR Optionsヘッダーを含むパケットを受けるノードは、それがパケットとセクション8.1.4で定義されるようにどうパケットを進めるかためには意図している次のホップノードであり、8.1が.5であるかどうか決定するために示された送信元経路を調べなければなりません。
6.8. Pad1 Option
6.8. Pad1オプション
The Pad1 option in a DSR Options header is encoded as follows:
DSR OptionsヘッダーのPad1オプションは以下の通りコード化されます:
+-+-+-+-+-+-+-+-+ | Option Type | +-+-+-+-+-+-+-+-+
+-+-+-+-+-+-+-+-+ | オプションタイプ| +-+-+-+-+-+-+-+-+
Option Type
オプションタイプ
224. Nodes not understanding this option will drop the packet
and return a Route Error.
224. このオプションを理解していないノードが、パケットを下げて、Route Errorを返すでしょう。
A Pad1 option MAY be included in the Options field of a DSR Options header in order to align subsequent DSR options, but such alignment is not required and MUST NOT be expected by a node receiving a packet containing a DSR Options header.
Pad1オプションがその後のDSRオプションを並べるためにDSR OptionsヘッダーのOptions分野に含まれるかもしれませんが、そのような整列を、必要でなく、DSR Optionsヘッダーを含むパケットを受けるノードは予想してはいけません。
If any headers follow the DSR Options header in a packet, the total length of a DSR Options header, indicated by the Payload Length field in the DSR Options header MUST be a multiple of 4 octets. In this case, when building a DSR Options header in a packet, sufficient Pad1 or PadN options MUST be included in the Options field of the DSR Options header to make the total length a multiple of 4 octets.
どれかヘッダーが続くなら、パケットのDSR Optionsヘッダー(DSR Optionsヘッダーの全長)は、有効搭載量でDSR OptionsヘッダーのLength分野が4つの八重奏の倍数であるに違いないことを示しました。 この場合パケットにDSR Optionsヘッダーを造るとき、全長を4つの八重奏の倍数にするようにDSR OptionsヘッダーのOptions分野に十分なPad1かPadNオプションを含まなければなりません。
If more than one consecutive octet of padding is being inserted in the Options field of a DSR Options header, the PadN option described next, SHOULD be used, rather than multiple Pad1 options.
複数であるというよりむしろ使用されたPad1がオプションであったならDSR Optionsヘッダー、オプションが次に説明したPadN、SHOULDのOptions分野に挿入されながらそっと歩く1つ以上の連続した八重奏であるなら。
Note that the format of the Pad1 option is a special case; it does not have an Opt Data Len or Option Data field.
Pad1オプションの形式が特別なケースであることに注意してください。 それには、Opt DataレンかOption Data分野がありません。
6.9. PadN Option
6.9. PadNオプション
The PadN option in a DSR Options header is encoded as follows:
DSR OptionsヘッダーのPadNオプションは以下の通りコード化されます:
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- - - - - - - - - | Option Type | Opt Data Len | Option Data +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- - - - - - - - -
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- - - - - - - - - | オプションタイプ| Dataレンを選んでください。| データ+++++++++++++++++をゆだねてください、-、--、--、--、--、--、--、--、-
Johnson, et al. Experimental [Page 50] RFC 4728 The Dynamic Source Routing Protocol February 2007
ジョンソン、他 ダイナミックな実験的な[50ページ]RFC4728のソースルーティング・プロトコル2007年2月
Option Type
オプションタイプ
0. Nodes not understanding this option will ignore this
option.
0. このオプションを理解していないノードがこのオプションを無視するでしょう。
Opt Data Len
Dataレンを選んでください。
8-bit unsigned integer. Length of the option, in octets,
excluding the Option Type and Opt Data Len fields. The size of
the Option Data field.
8ビットの符号のない整数。 Option TypeとOpt Dataレン分野を除いた八重奏における、オプションの長さ。 Option Data分野のサイズ。
Option Data
オプションデータ
A number of zero-valued octets equal to the Opt Data Len.
多くの無評価された八重奏がOpt Dataとレンと等しいです。
A PadN option MAY be included in the Options field of a DSR Options header in order to align subsequent DSR options, but such alignment is not required and MUST NOT be expected by a node receiving a packet containing a DSR Options header.
PadNオプションがその後のDSRオプションを並べるためにDSR OptionsヘッダーのOptions分野に含まれるかもしれませんが、そのような整列を、必要でなく、DSR Optionsヘッダーを含むパケットを受けるノードは予想してはいけません。
If any headers follow the DSR Options header in a packet, the total length of a DSR Options header, indicated by the Payload Length field in the DSR Options header, MUST be a multiple of 4 octets. In this case, when building a DSR Options header in a packet, sufficient Pad1 or PadN options MUST be included in the Options field of the DSR Options header to make the total length a multiple of 4 octets.
どれかヘッダーがパケットでDSR Optionsヘッダーについて来るなら、DSR Optionsヘッダーの有効搭載量Length分野によって示されたDSR Optionsヘッダーの全長は4つの八重奏の倍数であるに違いありません。 この場合パケットにDSR Optionsヘッダーを造るとき、全長を4つの八重奏の倍数にするようにDSR OptionsヘッダーのOptions分野に十分なPad1かPadNオプションを含まなければなりません。
7. Additional Header Formats and Options for Flow State Extension
7. 流れ州の拡大のための追加ヘッダー形式とオプション
The optional DSR flow state extension requires a new header type, the DSR Flow State header.
任意のDSR流れ州の拡張子は新しいヘッダータイプ、DSR Flow州ヘッダーを必要とします。
In addition, the DSR flow state extension adds the following options for the DSR Options header defined in Section 6:
さらに、DSR流れ州の拡張子はセクション6で定義されたDSR Optionsヘッダーのために以下のオプションを加えます:
- Timeout option (Section 7.2.1)
- タイムアウトオプション(セクション7.2.1)
- Destination and Flow ID option (Section 7.2.2)
- 目的地とFlow IDオプション(セクション7.2.2)
Two new Error Type values are also defined for use in the Route Error option in a DSR Options header:
また、2つの新しいError Type値がDSR OptionsヘッダーのRoute Errorオプションにおける使用のために定義されます:
- UNKNOWN_FLOW
- 未知の_流動
- DEFAULT_FLOW_UNKNOWN
- デフォルト_流れ_未知
Finally, an extension to the Acknowledgement Request option in a DSR Options header is also defined:
また、最終的に、DSR OptionsヘッダーのAcknowledgement Requestオプションへの拡大は定義されます:
Johnson, et al. Experimental [Page 51] RFC 4728 The Dynamic Source Routing Protocol February 2007
ジョンソン、他 ダイナミックな実験的な[51ページ]RFC4728のソースルーティング・プロトコル2007年2月
- Previous Hop Address
- 前のホップアドレス
This section defines each of these new header, option, or extension formats.
このセクションはそれぞれのこれらの新しいヘッダー、オプション、または拡大書式を定義します。
7.1. DSR Flow State Header
7.1. DSR流れ州のヘッダー
The DSR Flow State header is a small 4-byte header optionally used to carry the flow ID and hop count for a packet being sent along a DSR flow. It is distinguished from the fixed DSR Options header (Section 6.1) in that the Flow State Header (F) bit is set in the DSR Flow State header and is clear in the fixed DSR Options header.
DSR Flow州ヘッダーはDSR流動に沿って送られるパケットのための流れIDとホップカウントを運ぶのに任意に使用される小さい4バイトのヘッダーです。 Flow州Header(F)ビットがDSR Flow州ヘッダーに設定されて、固定DSR Optionsヘッダーで明確であるので、それは固定DSR Optionsヘッダー(セクション6.1)と区別されます。
0 1 2 3
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Next Header |F| Hop Count | Flow Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3 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 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | 次のヘッダー|F| ホップカウント| 流れ識別子| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Next Header
次のヘッダー
8-bit selector. Identifies the type of header immediately
following the DSR Flow State header. Uses the same values as
the IPv4 Protocol field [RFC1700].
8ビットのセレクタ。 すぐにDSR Flow州ヘッダーに続いて、ヘッダーのタイプを特定します。 同じくらいがIPv4プロトコルとして評価する用途は[RFC1700]をさばきます。
Flow State Header (F)
流れ州のヘッダー(F)
Flag bit. MUST be set to 1. This bit is set in a DSR Flow
State header and clear in a DSR Options header (Section 6.1).
ビットに旗を揚げさせてください。 1に設定しなければなりません。 このビットはDSR Optionsヘッダー(セクション6.1)にDSR Flow州ヘッダーにはっきりと設定されます。
Hop Count
ホップカウント
7-bit unsigned integer. The number of hops through which this
packet has been forwarded.
7ビットの符号のない整数。 このパケットが進められたホップの数。
Flow Identification
流れ識別
The flow ID for this flow, as described in Section 3.5.1.
この流れのためのセクション3.5.1で説明されるような流れID。
7.2. New Options and Extensions in DSR Options Header
7.2. DSRオプションヘッダーでの新しいオプションと拡大
7.2.1. Timeout Option
7.2.1. タイムアウトオプション
The Timeout option is defined for use in a DSR Options header to indicate the amount of time before the expiration of the flow ID along which the packet is being sent.
DSR Optionsヘッダーにおける使用が流れの満了の前の時間にパケットが送られるIDを示すように、Timeoutオプションは定義されます。
Johnson, et al. Experimental [Page 52] RFC 4728 The Dynamic Source Routing Protocol February 2007
ジョンソン、他 ダイナミックな実験的な[52ページ]RFC4728のソースルーティング・プロトコル2007年2月
0 1 2 3
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Option Type | Opt Data Len | Timeout |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3 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 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | オプションタイプ| Dataレンを選んでください。| タイムアウト| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Option Type
オプションタイプ
128. Nodes not understanding this option will ignore the
option and return a Route Error.
128. このオプションを理解していないノードが、オプションを無視して、Route Errorを返すでしょう。
Opt Data Len
Dataレンを選んでください。
8-bit unsigned integer. Length of the option, in octets,
excluding the Option Type and Opt Data Len fields.
8ビットの符号のない整数。 Option TypeとOpt Dataレン分野を除いた八重奏における、オプションの長さ。
When no extensions are present, the Opt Data Len of a Timeout
option is 2. Further extensions to DSR may include additional
data in a Timeout option. The presence of such extensions is
indicated by an Opt Data Len greater than 2. Currently, no
such extensions have been defined.
どんな拡大も存在していないとき、TimeoutオプションのOpt Dataレンは2歳です。 DSRへのさらなる拡大はTimeoutオプションに追加データを含むかもしれません。 そのような拡大の存在はOpt Dataレンより多くの2によって示されます。 現在、どんなそのような拡大も定義されていません。
Timeout
タイムアウト
The number of seconds for which this flow remains valid.
この流れが有効なままで残っている秒数。
The Timeout option MUST NOT appear more than once within a DSR Options header.
TimeoutオプションはDSR Optionsヘッダーの中に一度より多く見えてはいけません。
7.2.2. Destination and Flow ID Option
7.2.2. 目的地と流れIDオプション
The Destination and Flow ID option is defined for use in a DSR Options header to send a packet to an intermediate host along one flow, for eventual forwarding to the final destination along a different flow. This option enables the aggregation of the state of multiple flows.
DSR Optionsヘッダーにおける使用が1回の流れに沿って中間的ホストにパケットを送るように、DestinationとFlow IDオプションは定義されます、異なった流れに沿った最終的な目的地への最後の推進のために。 このオプションは複数の流れの状態の集合を可能にします。
0 1 2 3
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Option Type | Opt Data Len | New Flow Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| New IP Destination Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3 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 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | オプションタイプ| Dataレンを選んでください。| 新しい流れ識別子| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | 新しいIP送付先アドレス| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Johnson, et al. Experimental [Page 53] RFC 4728 The Dynamic Source Routing Protocol February 2007
ジョンソン、他 ダイナミックな実験的な[53ページ]RFC4728のソースルーティング・プロトコル2007年2月
Option Type
オプションタイプ
129. Nodes not understanding this option will ignore the
option and return a Route Error.
129. このオプションを理解していないノードが、オプションを無視して、Route Errorを返すでしょう。
Opt Data Len
Dataレンを選んでください。
8-bit unsigned integer. Length of the option, in octets,
excluding the Option Type and Opt Data Len fields.
8ビットの符号のない整数。 Option TypeとOpt Dataレン分野を除いた八重奏における、オプションの長さ。
When no extensions are present, the Opt Data Len of a
Destination and Flow ID option is 6. Further extensions to DSR
may include additional data in a Destination and Flow ID
option. The presence of such extensions is indicated by an Opt
Data Len greater than 6. Currently, no such extensions have
been defined.
どんな拡大も存在していないとき、DestinationとFlow IDオプションのOpt Dataレンは6歳です。 DSRへのさらなる拡大はDestinationとFlow IDオプションに追加データを含むかもしれません。 そのような拡大の存在はOpt Dataレンより多くの6によって示されます。 現在、どんなそのような拡大も定義されていません。
New Flow Identifier
新しい流れ識別子
Indicates the next identifier to store in the Flow ID field of
the DSR Options header.
DSR OptionsヘッダーのFlow ID分野に保存する次の識別子を示します。
New IP Destination Address
新しいIP送付先アドレス
Indicates the next address to store in the Destination Address
field of the IP header.
IPヘッダーのDestination Address分野に保存する次のアドレスを示します。
The Destination and Flow ID option MAY appear one or more times within a DSR Options header.
DestinationとFlow IDオプションはDSR Optionsヘッダーの中に1回以上現れるかもしれません。
7.3. New Error Types for Route Error Option
7.3. ルートエラーオプションのための新しい誤りタイプ
7.3.1. Unknown Flow Type-Specific Information
7.3.1. 未知の流れタイプ特有の情報
A new Error Type value of 129 (UNKNOWN_FLOW) is defined for use in a Route Error option in a DSR Options header. The Type-Specific Information for errors of this type is encoded as follows:
129(UNKNOWN_FLOW)の新しいError Type値はDSR OptionsヘッダーのRoute Errorオプションにおける使用のために定義されます。 このタイプの誤りのためのType特有の情報は以下の通りコード化されます:
0 1 2 3
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Original IP Destination Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Flow ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3 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 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | オリジナルのIP送付先アドレス| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | 流れID| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Johnson, et al. Experimental [Page 54] RFC 4728 The Dynamic Source Routing Protocol February 2007
ジョンソン、他 ダイナミックな実験的な[54ページ]RFC4728のソースルーティング・プロトコル2007年2月
Original IP Destination Address
オリジナルのIP送付先アドレス
The IP Destination Address of the packet that caused the error.
誤りを引き起こしたパケットのIP Destination Address。
Flow ID
流れID
The Flow ID contained in the DSR Flow ID option that caused the
error.
Flow IDはDSR Flow IDオプションに誤りが引き起こされたそれを含みました。
7.3.2. Default Flow Unknown Type-Specific Information
7.3.2. デフォルトの流れの未知のタイプ特有の情報
A new Error Type value of 130 (DEFAULT_FLOW_UNKNOWN) is defined for use in a Route Error option in a DSR Options header. The Type-Specific Information for errors of this type is encoded as follows:
130(DEFAULT_FLOW_UNKNOWN)の新しいError Type値はDSR OptionsヘッダーのRoute Errorオプションにおける使用のために定義されます。 このタイプの誤りのためのType特有の情報は以下の通りコード化されます:
0 1 2 3
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Original IP Destination Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3 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 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | オリジナルのIP送付先アドレス| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Original IP Destination Address
オリジナルのIP送付先アドレス
The IP Destination Address of the packet that caused the error.
誤りを引き起こしたパケットのIP Destination Address。
7.4. New Acknowledgement Request Option Extension
7.4. 新しい承認要求オプション拡張子
7.4.1. Previous Hop Address Extension
7.4.1. 前のホップアドレス拡大
When the Opt Data Len field of an Acknowledgement Request option in a DSR Options header is greater than or equal to 6, the ACK Request Source Address field is present. The option is then formatted as follows:
DSR OptionsヘッダーのAcknowledgement RequestオプションのOpt Dataレン分野が6以上であるときに、ACK Request Source Address分野は存在しています。 次に、オプションは以下の通りフォーマットされます:
0 1 2 3
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Option Type | Opt Data Len | Packet Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ACK Request Source Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3 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 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | オプションタイプ| Dataレンを選んでください。| パケット識別子| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | ACKはソースアドレスを要求します。| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Option Type
オプションタイプ
160. Nodes not understanding this option will remove the
option and return a Route Error.
160. このオプションを理解していないノードが、オプションを取り除いて、Route Errorを返すでしょう。
Johnson, et al. Experimental [Page 55] RFC 4728 The Dynamic Source Routing Protocol February 2007
ジョンソン、他 ダイナミックな実験的な[55ページ]RFC4728のソースルーティング・プロトコル2007年2月
Opt Data Len
Dataレンを選んでください。
8-bit unsigned integer. Length of the option, in octets,
excluding the Option Type and Opt Data Len fields.
8ビットの符号のない整数。 Option TypeとOpt Dataレン分野を除いた八重奏における、オプションの長さ。
When no extensions are presents, the Opt Data Len of an
Acknowledgement Request option is 2. Further extensions to DSR
may include additional data in an Acknowledgement Request
option. The presence of such extensions is indicated by an Opt
Data Len greater than 2.
どんな拡大もプレゼントでないときに、Acknowledgement RequestオプションのOpt Dataレンは2歳です。 DSRへのさらなる拡大はAcknowledgement Requestオプションに追加データを含むかもしれません。 そのような拡大の存在はOpt Dataレンより多くの2によって示されます。
Currently, one such extension has been defined. If the Opt
Data Len is at least 6, then an ACK Request Source Address is
present.
現在、そのような拡大の1つは定義されました。 Opt Dataレンが少なくとも6歳であるなら、ACK Request Source Addressは存在しています。
Packet Identifier
パケット識別子
The Packet Identifier field is set to a unique number and is
copied into the Identification field of the DSR Acknowledgement
option when returned by the node receiving the packet over this
hop.
このホップの上にパケットを受けるノードで返すと、Packet Identifier分野をユニークな数に設定して、DSR AcknowledgementオプションのIdentification分野にコピーします。
ACK Request Source Address
ACKはソースアドレスを要求します。
The address of the node requesting the DSR Acknowledgement.
DSR Acknowledgementを要求するノードのアドレス。
8. Detailed Operation
8. 詳細な操作
8.1. General Packet Processing
8.1. 一般パケット処理
8.1.1. Originating a Packet
8.1.1. パケットを溯源します。
When originating any packet, a node using DSR routing MUST perform the following sequence of steps:
どんなパケットも溯源するとき、DSRルーティングを使用するノードは以下のステップの以下の系列を実行しなければなりません:
- Search the node's Route Cache for a route to the address given in
the IP Destination Address field in the packet's header.
- パケットのヘッダーのIP Destination Address分野で与えられたアドレスへのルートとしてノードのRoute Cacheを捜してください。
- If no such route is found in the Route Cache, then perform Route
Discovery for the Destination Address, as described in Section
8.2. Initiating a Route Discovery for this target node address
results in the node adding a Route Request option in a DSR Options
header in this existing packet, or saving this existing packet to
its Send Buffer and initiating the Route Discovery by sending a
separate packet containing such a Route Request option. If the
node chooses to initiate the Route Discovery by adding the Route
Request option to this existing packet, it will replace the IP
Destination Address field with the IP "limited broadcast" address
- 何かそのようなルートがRoute Cacheで見つけられないなら、Destination AddressのためにRouteディスカバリーを実行してください、セクション8.2で説明されるように。 この目標ノードアドレスのためにRouteディスカバリーを開始すると、この既存のパケットのDSR OptionsヘッダーでRoute Requestオプションを加えるか、この既存のパケットをSend Bufferに保存して、またはそのようなRoute Requestオプションを含む別々のパケットを送ることによってRouteディスカバリーを開始するノードはもたらされます。 ノードが、この既存のパケットにRoute Requestオプションを加えることによってRouteディスカバリーを開始するのを選ぶと、それはIP Destination Address分野をIP「限られた放送」アドレスに取り替えるでしょう。
Johnson, et al. Experimental [Page 56] RFC 4728 The Dynamic Source Routing Protocol February 2007
ジョンソン、他 ダイナミックな実験的な[56ページ]RFC4728のソースルーティング・プロトコル2007年2月
(255.255.255.255) [RFC1122], copying the original IP Destination
Address to the Target Address field of the new Route Request
option added to the packet, as described in Section 8.2.1.
(255.255 .255 .255) [RFC1122]、新しいRoute RequestオプションのTarget Address分野にオリジナルのIP Destination Addressをコピーするのはパケットに加えました、セクション8.2.1で説明されるように。
- If the packet now does not contain a Route Request option, then
this node must have a route to the Destination Address of the
packet; if the node has more than one route to this Destination
Address, the node selects one to use for this packet. If the
length of this route is greater than 1 hop, or if the node
determines to request a DSR network-layer acknowledgement from the
first-hop node in that route, then insert a DSR Options header
into the packet, as described in Section 8.1.2, and insert a DSR
Source Route option, as described in Section 8.1.3. The source
route in the packet is initialized from the selected route to the
Destination Address of the packet.
- パケットが現在Route Requestオプションを含まないなら、このノードはパケットのDestination Addressにルートを持たなければなりません。 ノードがこのDestination Addressに1つ以上のルートを持っているなら、ノードはこのパケットの使用への1つを選択します。 このルートの長さが1つ以上のホップである、またはノードが、そのルートによる最初に、ホップノードからDSRネットワーク層承認を要求することを決定するなら、セクション8.1.2で説明されるようにDSR Optionsヘッダーをパケットに挿入してください、そして、DSR Source Routeオプションを挿入してください、セクション8.1.3で説明されるように。 パケットの送信元経路は選択されたルートからパケットのDestination Addressまで初期化されます。
- Transmit the packet to the first-hop node address given in
selected source route, using Route Maintenance to determine the
reachability of the next hop, as described in Section 8.3.
- 選択された送信元経路で与えられた最初に、ホップノードアドレスにパケットを伝えてください、次のホップの可到達性を決定するのにRoute Maintenanceを使用して、セクション8.3で説明されるように。
8.1.2. Adding a DSR Options Header to a Packet
8.1.2. DSRオプションヘッダーをパケットに加えます。
A node originating a packet adds a DSR Options header to the packet, if necessary, to carry information needed by the routing protocol. A packet MUST NOT contain more than one DSR Options header. A DSR Options header is added to a packet by performing the following sequence of steps (these steps assume that the packet contains no other headers that MUST be located in the packet before the DSR Options header):
必要なら、パケットを溯源するノードは、ルーティング・プロトコルによって必要とされた情報を運ぶためにDSR Optionsヘッダーをパケットに加えます。 パケットは1個以上のDSR Optionsヘッダーを含んではいけません。 DSR Optionsヘッダーはステップの以下の系列を実行することによって、パケットに加えられます(これらのステップは、パケットがDSR Optionsヘッダーの前にパケットに位置させてはいけない他のヘッダーを全く含むと仮定します):
- Insert a DSR Options header after the IP header but before any
other header that may be present.
- ヘッダーにもかかわらず、いかなる他の出席するかもしれないヘッダーの前でもDSR OptionsヘッダーをIPの後に挿入してください。
- Set the Next Header field of the DSR Options header to the
Protocol number field of the packet's IP header.
- パケットのIPヘッダーのプロトコルナンバーフィールドにDSR OptionsヘッダーのNext Header分野を設定してください。
- Set the Protocol field of the packet's IP header to the protocol
number assigned for DSR (48).
- パケットのIPヘッダーのプロトコル分野をDSR(48)のために割り当てられたプロトコル番号に設定してください。
8.1.3. Adding a DSR Source Route Option to a Packet
8.1.3. DSR送信元経路オプションをパケットに加えます。
A node originating a packet adds a DSR Source Route option to the packet, if necessary, in order to carry the source route from this originating node to the final destination address of the packet. Specifically, the node adding the DSR Source Route option constructs the DSR Source Route option and modifies the IP packet according to the following sequence of steps:
必要なら、パケットを溯源するノードは、この起因するノードから最終的なパケットの送付先アドレスまで送信元経路を運ぶためにDSR Source Routeオプションをパケットに加えます。 明確に、以下のステップの以下の系列によると、DSR Source Routeオプションを加えるノードは、DSR Source Routeオプションを構成して、IPパケットを変更します:
Johnson, et al. Experimental [Page 57] RFC 4728 The Dynamic Source Routing Protocol February 2007
ジョンソン、他 ダイナミックな実験的な[57ページ]RFC4728のソースルーティング・プロトコル2007年2月
- The node creates a DSR Source Route option, as described in
Section 6.7, and appends it to the DSR Options header in the
packet. (A DSR Options header is added, as described in Section
8.1.2, if not already present.)
- ノードは、セクション6.7で説明されるようにDSR Source Routeオプションを作成して、パケットのDSR Optionsヘッダーにそれを追加します。 (DSR Optionsヘッダーはセクション8.1.2で説明される、または既に現在として加えられます。)
- The number of Address[i] fields to include in the DSR Source Route
option (n) is the number of intermediate nodes in the source route
for the packet (i.e., excluding the address of the originating
node and the final destination address of the packet). The
Segments Left field in the DSR Source Route option is initialized
equal to n.
- パケット(すなわち、起因するノードのアドレスとパケットの最終的な送付先アドレスを除いた)のための送信元経路でDSR Source Routeオプション(n)に含んでいるAddress[i]分野の数は中間的ノードの数です。 DSR Source RouteオプションにおけるSegments Left分野はnと等しい状態で初期化されます。
- The addresses within the source route for the packet are copied
into sequential Address[i] fields in the DSR Source Route option,
for i = 1, 2, ..., n.
- パケットのための送信元経路の中のアドレスはDSR Source Routeオプションにおける連続したAddress[i]分野にコピーされます、i=1、2のために…, n。
- The First Hop External (F) bit in the DSR Source Route option is
copied from the External bit flagging the first hop in the source
route for the packet, as indicated in the Route Cache.
- DSR Source RouteオプションにおけるFirst Hop External(F)ビットはパケットのために送信元経路で最初のホップに旗を揚げさせるExternalビットからコピーされます、Route Cacheにみられるように。
- The Last Hop External (L) bit in the DSR Source Route option is
copied from the External bit flagging the last hop in the source
route for the packet, as indicated in the Route Cache.
- DSR Source RouteオプションにおけるLast Hop External(L)ビットはパケットのために送信元経路で最後のホップに旗を揚げさせるExternalビットからコピーされます、Route Cacheにみられるように。
- The Salvage field in the DSR Source Route option is initialized to
0.
- DSR Source RouteオプションにおけるSalvage分野は0に初期化されます。
8.1.4. Processing a Received Packet
8.1.4. 容認されたパケットを処理します。
When a node receives any packet (whether for forwarding, overheard, or the final destination of the packet), if that packet contains a DSR Options header, then that node MUST process any options contained in that DSR Options header, in the order contained there. Specifically:
ノードがどんなパケットも受けるとき(立ち聞きされた推進かパケットの最終的な目的地にかかわらず)、そのパケットがDSR Optionsヘッダーを含んでいるなら、そのノードはそのDSR Optionsヘッダーに含まれたどんなオプションも処理しなければなりません、そこに含まれたオーダーで。 明確に:
- If the DSR Options header contains a Route Request option, the
node SHOULD extract the source route from the Route Request and
add this routing information to its Route Cache, subject to the
conditions identified in Section 3.3.1. The routing information
from the Route Request is the sequence of hop addresses
- DSR OptionsヘッダーがRoute Requestオプションを含んでいるなら、ノードSHOULDはセクション3.3.1で特定された状態を条件としてRoute Requestから送信元経路を抜粋して、このルーティング情報をRoute Cacheに加えます。 Route Requestからのルーティング情報はホップアドレスの系列です。
initiator, Address[1], Address[2], ..., Address[n]
創始者、Address[1]、Address[2]…, アドレス[n]
where initiator is the value of the Source Address field in the IP
header of the packet carrying the Route Request (the address of
the initiator of the Route Discovery), and each Address[i] is a
node through which this Route Request has passed, in turn, during
創始者がRoute Request(Routeディスカバリーの創始者のアドレス)を運ぶパケットのIPヘッダーのSource Address分野の値であり、各Address[i]がこのRoute Requestが順番に通ったノードであるところ
Johnson, et al. Experimental [Page 58] RFC 4728 The Dynamic Source Routing Protocol February 2007
ジョンソン、他 ダイナミックな実験的な[58ページ]RFC4728のソースルーティング・プロトコル2007年2月
this Route Discovery. The value n, here, is the number of
addresses recorded in the Route Request option, or
(Opt Data Len - 6) / 4.
このRouteディスカバリー。 値nは、ここのRoute Requestオプションに記録されたアドレスの数、または(Dataレンを選んでください--6)という/4です。
After possibly updating the node's Route Cache in response to the
routing information in the Route Request option, the node MUST
then process the Route Request option as described in Section
8.2.2.
そして、ことによるとRoute Requestオプションにおけるルーティング情報に対応してノードのRoute Cacheをアップデートした後に、ノードはセクション8.2.2で説明されるようにRoute Requestオプションを処理しなければなりません。
- If the DSR Options header contains a Route Reply option, the node
SHOULD extract the source route from the Route Reply and add this
routing information to its Route Cache, subject to the conditions
identified in Section 3.3.1. The source route from the Route
Reply is the sequence of hop addresses
- DSR OptionsヘッダーがRoute Replyオプションを含んでいるなら、ノードSHOULDはセクション3.3.1で特定された状態を条件としてRoute Replyから送信元経路を抜粋して、このルーティング情報をRoute Cacheに加えます。 Route Replyからの送信元経路はホップアドレスの系列です。
initiator, Address[1], Address[2], ..., Address[n]
創始者、Address[1]、Address[2]…, アドレス[n]
where initiator is the value of the Destination Address field in
the IP header of the packet carrying the Route Reply (the address
of the initiator of the Route Discovery), and each Address[i] is a
node through which the source route passes, in turn, on the route
to the target of the Route Discovery. Address[n] is the address
of the target. If the Last Hop External (L) bit is set in the
Route Reply, the node MUST flag the last hop from the Route Reply
(the link from Address[n-1] to Address[n]) in its Route Cache as
External. The value n here is the number of addresses in the
source route being returned in the Route Reply option, or
(Opt Data Len - 1) / 4.
創始者がRoute Reply(Routeディスカバリーの創始者のアドレス)を運ぶパケットのIPヘッダーのDestination Address分野の値であり、各Address[i]が送信元経路がルートで順番にRouteディスカバリーの目標に通るノードであるところ。 アドレス[n]は目標のアドレスです。 Last Hop External(L)ビットがRoute Replyに設定されるなら、ノードはRoute Replyから最後のホップに旗を揚げさせなければなりません。(Address[n-1]からExternalとしてのRoute CacheのAddress[n])へのリンク。 ここの値nはRoute Replyオプションで返される送信元経路、または(Dataレンを選んでください--1)という/4のアドレスの数です。
After possibly updating the node's Route Cache in response to the
routing information in the Route Reply option, then if the
packet's IP Destination Address matches one of this node's IP
addresses, the node MUST then process the Route Reply option as
described in Section 8.2.6.
そして、そして、ことによるとRoute Replyオプションにおけるルーティング情報に対応してノードのRoute Cacheをアップデートした後に、パケットのIP Destination AddressがこのノードのIPアドレスの1つに合っているなら、ノードはセクション8.2.6で説明されるようにRoute Replyオプションを処理しなければなりません。
- If the DSR Options header contains a Route Error option, the node
MUST process the Route Error option as described in Section 8.3.5.
- DSR OptionsヘッダーがRoute Errorオプションを含んでいるなら、ノードはセクション8.3.5で説明されるようにRoute Errorオプションを処理しなければなりません。
- If the DSR Options header contains an Acknowledgement Request
option, the node MUST process the Acknowledgement Request option
as described in Section 8.3.3.
- DSR OptionsヘッダーがAcknowledgement Requestオプションを含んでいるなら、ノードはセクション8.3.3で説明されるようにAcknowledgement Requestオプションを処理しなければなりません。
- If the DSR Options header contains an Acknowledgement option, then
subject to the conditions identified in Section 3.3.1, the node
SHOULD add to its Route Cache the single link from the node
identified by the ACK Source Address field to the node identified
by the ACK Destination Address field.
- DSR OptionsヘッダーがAcknowledgementオプションを含んでいるなら、セクション3.3.1で特定された状態を条件として、ノードSHOULDはACK Source Address分野によって特定されたノードからACK Destination Address分野によって特定されたノードまで単一のリンクをRoute Cacheに加えます。
Johnson, et al. Experimental [Page 59] RFC 4728 The Dynamic Source Routing Protocol February 2007
ジョンソン、他 ダイナミックな実験的な[59ページ]RFC4728のソースルーティング・プロトコル2007年2月
After possibly updating the node's Route Cache in response to the
routing information in the Acknowledgement option, the node MUST
then process the Acknowledgement option as described in Section
8.3.3.
そして、ことによるとAcknowledgementオプションにおけるルーティング情報に対応してノードのRoute Cacheをアップデートした後に、ノードはセクション8.3.3で説明されるようにAcknowledgementオプションを処理しなければなりません。
- If the DSR Options header contains a DSR Source Route option, the
node SHOULD extract the source route from the DSR Source Route
option and add this routing information to its Route Cache,
subject to the conditions identified in Section 3.3.1. If the
value of the Salvage field in the DSR Source Route option is zero,
then the routing information from the DSR Source Route is the
sequence of hop addresses
- DSR OptionsヘッダーがDSR Source Routeオプションを含んでいるなら、ノードSHOULDはセクション3.3.1で特定された状態を条件としてDSR Source Routeオプションから送信元経路を抜粋して、このルーティング情報をRoute Cacheに加えます。 DSR Source Routeオプションにおける、Salvage分野の値がゼロであるなら、DSR Source Routeからのルーティング情報はホップアドレスの系列です。
source, Address[1], Address[2], ..., Address[n], destination
ソース、Address[1]、Address[2]…, アドレス[n]、目的地
Otherwise (i.e., if Salvage is nonzero), the routing information
from the DSR Source Route is the sequence of hop addresses
さもなければ(すなわち、Salvageが非零であるなら)、DSR Source Routeからのルーティング情報はホップアドレスの系列です。
Address[1], Address[2], ..., Address[n], destination
[1]、アドレス[2]を扱ってください…, アドレス[n]、目的地
where source is the value of the Source Address field in the IP
header of the packet carrying the DSR Source Route option (the
original sender of the packet), each Address[i] is the value in
the Address[i] field in the DSR Source Route option, and
destination is the value of the Destination Address field in the
packet's IP header (the last-hop address of the source route).
The value n here is the number of addresses in source route in the
DSR Source Route option, or (Opt Data Len - 2) / 4.
ソースがDSR Source Routeオプション(パケットの元の送り主)を運ぶパケットのIPヘッダーのSource Address分野の値であるところでは、各Address[i]はDSR Source RouteオプションにおけるAddress[i]分野の値です、そして、目的地はパケットのIPヘッダー(送信元経路の最後のホップアドレス)のDestination Address分野の値です。 DSR Source Routeオプション、または(Dataレンを選んでください--2)という/4の送信元経路でここの値nはアドレスの数です。
After possibly updating the node's Route Cache in response to the
routing information in the DSR Source Route option, the node MUST
then process the DSR Source Route option as described in Section
8.1.5.
そして、ことによるとDSR Source Routeオプションにおけるルーティング情報に対応してノードのRoute Cacheをアップデートした後に、ノードはセクション8.1.5で説明されるようにDSR Source Routeオプションを処理しなければなりません。
- Any Pad1 or PadN options in the DSR Options header are ignored.
- DSR OptionsヘッダーのどんなPad1やPadNオプションも無視されます。
- Finally, if the Destination Address in the packet's IP header
matches one of this receiving node's own IP address(es), remove
the DSR Options header and all the included DSR options in the
header, and pass the rest of the packet to the network layer.
- この受信ノードの自身のIPに関するパケットのIPヘッダーマッチ1のDestination Addressが(es)を扱うなら、ヘッダーで最終的にDSR Optionsヘッダーとすべての含まれているDSRオプションを移してください、そして、パケットの残りをネットワーク層に通過してください。
8.1.5. Processing a Received DSR Source Route Option
8.1.5. 容認されたDSR送信元経路オプションを処理します。
When a node receives a packet containing a DSR Source Route option (whether for forwarding, overheard, or the final destination of the packet), that node SHOULD examine the packet to determine if the receipt of that packet indicates an opportunity for automatic route shortening, as described in Section 3.4.3. Specifically, if this
ノードがDSR Source Routeオプションを含むパケットを受けるとき(立ち聞きされた推進かパケットの最終的な目的地にかかわらず)、そのノードSHOULDはそのパケットの領収書が自動ルート短縮の機会を示すかどうか決定するためにパケットを調べます、セクション3.4.3で説明されるように。 明確にこれです。
Johnson, et al. Experimental [Page 60] RFC 4728 The Dynamic Source Routing Protocol February 2007
ジョンソン、他 ダイナミックな実験的な[60ページ]RFC4728のソースルーティング・プロトコル2007年2月
node is not the intended next-hop destination for the packet but is named in the later unexpended portion of the source route in the packet's DSR Source Route option, then this packet indicates an opportunity for automatic route shortening: the intermediate nodes after the node from which this node overheard the packet and before this node itself are no longer necessary in the source route. In this case, this node SHOULD perform the following sequence of steps as part of automatic route shortening:
ノードは、パケットのための意図している次のホップの目的地ではありませんが、送信元経路の後の未支出部分でパケットのDSR Source Routeオプションで命名されます、次に、このパケットは自動ルート短縮の機会を示します: ノードのこのノードがパケットを立ち聞きした後とこのノード自体の前の中間的ノードはもう送信元経路で必要ではありません。 この場合、このノードSHOULDは自動ルート短縮の一部としてステップの以下の系列を実行します:
- The node searches its Gratuitous Route Reply Table for an entry
describing a gratuitous Route Reply earlier sent by this node, for
which the original sender (of the packet triggering the gratuitous
Route Reply) and the transmitting node (from which this node
overheard that packet in order to trigger the gratuitous Route
Reply) both match the respective node addresses for this new
received packet. If such an entry is found in the node's
Gratuitous Route Reply Table, the node SHOULD NOT perform
automatic route shortening in response to this receipt of this
packet.
- ノードは前に元の送り主(パケットが無料のRoute Replyの引き金となるのについて)と伝えるノード(このノードが無料のRoute Replyの引き金となるようにそのパケットを立ち聞きした)がともにこの新しい容認されたパケットのためのそれぞれのノードアドレスに合っているこのノードによって送られた無料のRoute Replyについて説明するエントリーとしてGratuitous Route Reply Tableを捜します。 そのようなエントリーがノードのGratuitous Route Reply Tableで見つけられるなら、ノードSHOULD NOTはこのパケットのこの領収書に対応して自動ルート短縮を実行します。
- Otherwise, the node creates an entry for this overheard packet in
its Gratuitous Route Reply Table. The timeout value for this new
entry SHOULD be initialized to the value GratReplyHoldoff. After
this timeout has expired, the node SHOULD delete this entry from
its Gratuitous Route Reply Table.
- さもなければ、ノードはGratuitous Route Reply Tableでこの立ち聞きされたパケットのためのエントリーを作成します。 タイムアウトはこの新しいエントリーにSHOULDを評価します。値のGratReplyHoldoffに初期化されます。 このタイムアウトが期限が切れた後に、ノードSHOULDはGratuitous Route Reply Tableからこのエントリーを削除します。
- After creating the new Gratuitous Route Reply Table entry above,
the node originates a gratuitous Route Reply to the IP Source
Address of this overheard packet, as described in Section 3.4.3.
- 新しいGratuitous Route Reply Tableエントリーを作成した後に、上では、ノードがこの立ち聞きされたパケットのIP Source Addressに無料のRoute Replyを溯源します、セクション3.4.3で説明されるように。
If the MAC protocol in use in the network is not capable of
transmitting unicast packets over unidirectional links, as
discussed in Section 3.3.1, then in originating this Route Reply,
the node MUST use a source route for routing the Route Reply
packet that is obtained by reversing the sequence of hops over
which the packet triggering the gratuitous Route Reply was routed
in reaching and being overheard by this node. This reversing of
the route uses the gratuitous Route Reply to test this sequence of
hops for bidirectionality, preventing the gratuitous Route Reply
from being received by the initiator of the Route Discovery unless
each of the hops over which the gratuitous Route Reply is returned
is bidirectional.
ネットワークで使用でのMACプロトコルがセクション3.3.1で議論するように単方向のリンクの上にユニキャストパケットを伝えることができないなら、このRoute Replyを溯源する際に、ノードは、無料のRoute Replyの引き金となるパケットが達して、このノードで立ち聞きされる際に発送されたホップの系列を逆にすることによって得られるRoute Replyパケットを発送するのに送信元経路を使用しなければなりません。 ルートをこの逆にするのがホップのこの系列をテストする無料のRoute Replyを使用する、双方向性です、それぞれ無料のRoute Replyが返されるホップについてそうしない場合無料のRoute ReplyがRouteディスカバリーの創始者によって受け取られるのを防ぐのは双方向です。
- Discard the overheard packet, since the packet has been received
before its normal traversal of the packet's source route would
have caused it to reach this receiving node. Another copy of the
packet will normally arrive at this node as indicated in the
- 立ち聞きされたパケットを捨ててください、パケットの送信元経路に関する通常の縦断でこの受信ノードに達する前にパケットを受け取ったので。 にみられるように通常、パケットの別のコピーがこのノードに届く。
Johnson, et al. Experimental [Page 61] RFC 4728 The Dynamic Source Routing Protocol February 2007
ジョンソン、他 ダイナミックな実験的な[61ページ]RFC4728のソースルーティング・プロトコル2007年2月
packet's source route; discarding this initial copy of the packet,
which triggered the gratuitous Route Reply, will prevent the
duplication of this packet that would otherwise occur.
パケットの送信元経路。 無料のRoute Replyの引き金となったパケットのこの初期のコピーを捨てると、そうでなければ起こるこのパケットの複製は防がれるでしょう。
If the packet is not discarded as part of automatic route shortening above, then the node MUST process the Source Route option according to the following sequence of steps:
パケットが上で短くされる自動ルートの一部として捨てられないなら、以下のステップの以下の系列によると、ノードはSource Routeオプションを処理しなければなりません:
- If the value of the Segments Left field in the DSR Source Route
option equals 0, then remove the DSR Source Route option from the
DSR Options header.
- DSR Source Routeオプションにおける、Segments Left分野の値が0と等しいなら、DSR OptionsヘッダーからDSR Source Routeオプションを取り除いてください。
- Else, let n equal (Opt Data Len - 2) / 4. This is the number of
addresses in the DSR Source Route option.
- ほかに、nを(Dataレンを選んでください--2)という/4との等しさにしてください。 これはDSR Source Routeオプションで、アドレスの数です。
- If the value of the Segments Left field is greater than n, then
send an ICMP Parameter Problem, Code 0, message [RFC792] to the IP
Source Address, pointing to the Segments Left field, and discard
the packet. Do not process the DSR Source Route option further.
- Segments Left分野の値がn以上であるなら、ICMP Parameter Problem、Code0、Segments Left野原を示すIP Source Addressへのメッセージ[RFC792]を送ってください、そして、パケットを捨ててください。 さらにDSR Source Routeオプションを処理しないでください。
- Else, decrement the value of the Segments Left field by 1. Let i
equal n minus Segments Left. This is the index of the next
address to be visited in the Address vector.
- ほかに、Segments Left分野の値を1つ減少させてください。 Segments Leftを引いてiをnとの等しさにしてください。 これは次のAddressベクトルで訪問されるべきアドレスのインデックスです。
- If Address[i] or the IP Destination Address is a multicast
address, then discard the packet. Do not process the DSR Source
Route option further.
- Address[i]かIP Destination Addressがマルチキャストアドレスであるなら、パケットを捨ててください。 さらにDSR Source Routeオプションを処理しないでください。
- If this node has more than one network interface and if Address[i]
is the address of one this node's network interfaces, then this
indicates a change in the network interface to use in forwarding
the packet, as described in Section 8.4. In this case, decrement
the value of the Segments Left field by 1 to skip over this
address (that indicated the change of network interface) and go to
the first step above (checking the value of the Segments Left
field) to continue processing this Source Route option; in further
processing of this Source Route option, the indicated new network
interface MUST be used in forwarding the packet.
- このノードで1つ以上のネットワーク・インターフェースがあって、Address[i]がこのノードのネットワークが連結するもののアドレスであるなら、これはパケットを進める際に使用するネットワーク・インターフェースの変化を示します、セクション8.4で説明されるように。 この場合、Segments Left分野の値を1つ減少させて(それはネットワーク・インターフェースの変化を示しました)、このアドレスを飛ばしてください、このSource Routeオプションを処理し続けに上(Segments Left分野の値をチェックする)に第一歩に行ってください。 このSource Routeオプションのさらなる処理では、パケットを進める際に示された新しいネットワーク・インターフェースを使用しなければなりません。
- If the MTU of the link over which this node would transmit the
packet to forward it to the node Address[i] is less than the size
of the packet, the node MUST either discard the packet and send an
ICMP Packet Too Big message to the packet's Source Address
[RFC792] or fragment it as specified in Section 8.5.
- このノードがノードAddress[i]にそれを送るためにパケットを伝えるリンクのMTUがパケットのサイズ以下であるなら、ノードは、セクション8.5で指定されるようにパケットを捨てて、パケットのSource Address[RFC792]にICMP Packet Too Bigメッセージを送らなければならないか、またはそれを断片化しなければなりません。
- Forward the packet to the IP address specified in the Address[i]
field of the IP header, following normal IP forwarding procedures,
including checking and decrementing the Time-to-Live (TTL) field
- 前方に、IPアドレスへのパケットはIPヘッダーのAddress[i]分野で指定しました、手順を進めながら正常なIPに続いて、生きるTime(TTL)分野をチェックして、減少させるのを含んでいて
Johnson, et al. Experimental [Page 62] RFC 4728 The Dynamic Source Routing Protocol February 2007
ジョンソン、他 ダイナミックな実験的な[62ページ]RFC4728のソースルーティング・プロトコル2007年2月
in the packet's IP header [RFC791, RFC1122]. In this forwarding
of the packet, the next-hop node (identified by Address[i]) MUST
be treated as a direct neighbor node: the transmission to that
next node MUST be done in a single IP forwarding hop, without
Route Discovery and without searching the Route Cache.
パケットのIPヘッダー[RFC791、RFC1122]で。 ノードを次に飛び越してください。パケットのこの推進で(Address[i])によって特定されて、ダイレクト隣人ノードとして扱わなければなりません: Routeディスカバリーなしで単一のIP推進ホップと、Route Cacheを捜すことなしでその次のノードへのトランスミッションをしなければなりません。
- In forwarding the packet, perform Route Maintenance for the next
hop of the packet, by verifying that the next-hop node is
reachable, as described in Section 8.3.
- パケットを進める際に、パケットの次のホップのためにRoute Maintenanceを実行してください、次のホップノードが届いていることを確かめることによって、セクション8.3で説明されるように。
Multicast addresses MUST NOT appear in a DSR Source Route option or in the IP Destination Address field of a packet carrying a DSR Source Route option in a DSR Options header.
マルチキャストアドレスは、DSR OptionsヘッダーでDSR Source Routeオプションを運びながら、DSR Source RouteオプションかパケットのIP Destination Address分野に現れてはいけません。
8.1.6. Handling an Unknown DSR Option
8.1.6. 未知のDSRオプションを扱います。
Nodes implementing DSR MUST handle all options specified in this document, except those options pertaining to the optional flow state extension (Section 7). However, further extensions to DSR may include other option types that may not be understood by implementations conforming to this version of the DSR specification. In DSR, Option Type codes encode required behavior for nodes not implementing that type of option. These behaviors are included in the most significant 3 bits of the Option Type.
DSR MUSTを実装するノードが本書では指定されたすべてのオプションを扱います、任意の流れ州の拡大(セクション7)に関係するそれらのオプションを除いて。 しかしながら、DSRへのさらなる拡大はDSR仕様のこのバージョンに従う実装に解釈されないかもしれない別の選択肢タイプを含むかもしれません。 DSRでは、Option Typeコードはそのタイプのオプションを実装しないノードのための必要な振舞いをコード化します。 これらの振舞いはOption Typeの最も重要な3ビットに含まれています。
If the most significant bit of the Option Type is set (that is, Option Type & 0x80 is nonzero), and this packet does not contain a Route Request option, a node SHOULD return a Route Error to the IP Source Address, following the steps described in Section 8.3.4, except that the Error Type MUST be set to OPTION_NOT_SUPPORTED and the Unsupported Opt field MUST be set to the Option Type triggering the Route Error.
最も重要であるのが噛み付いた、Option Typeは用意ができています、そして、(すなわち、Option Typeと0×80は非零です)このパケットはRoute Requestオプションを含んでいません、IP Source AddressへのaノードSHOULDリターンa Route Error、セクション8.3.4で説明された方法に従って、Error TypeがOPTION_NOT_SUPPORTEDに用意ができなければならなくて、Route Errorの引き金となるOption TypeにUnsupported Opt分野を設定しなければならないのを除いて。
Whether or not a Route Error is sent in response to this DSR option, as described above, the node also MUST examine the next 2 most significant bits (that is, Option Type & 0x60):
上で説明されるようにこのDSRオプションに対応してRoute Errorを送るか否かに関係なく、ノードも次の2つの最上位ビット(すなわち、Option Typeと0×60)を調べなければなりません:
- When these 2 bits are 00 (that is, Option Type & 0x60 == 0), a
node not implementing processing for that Option Type MUST use the
Opt Data Len field to skip over the option and continue
processing.
- これらの2ビットが00(すなわち、Option Typeと0×60=0)であるときに、そのOption Typeのために処理を実装しないノードは、オプションを飛ばして、処理し続けるのにOpt Dataレン分野を使用しなければなりません。
- When these 2 bits are 01 (that is, Option Type & 0x60 == 0x20), a
node not implementing processing for that Option Type MUST use the
Opt Data Len field to remove the option from the packet and
continue processing as if the option had not been included in the
received packet.
- これらの2ビットが01(すなわち、Option Typeと0×60=0×20)であるときに、そのOption Typeのために処理を実装しないノードは、パケットからオプションを取り除いて、まるでオプションが容認されたパケットに含まれていないかのように処理し続けるのにOpt Dataレン分野を使用しなければなりません。
Johnson, et al. Experimental [Page 63] RFC 4728 The Dynamic Source Routing Protocol February 2007
ジョンソン、他 ダイナミックな実験的な[63ページ]RFC4728のソースルーティング・プロトコル2007年2月
- When these 2 bits are 10 (that is, Option Type & 0x60 == 0x40), a
node not implementing processing for that Option Type MUST set the
most significant bit following the Opt Data Len field. In
addition, the node MUST then ignore and skip over the contents of
the option using the Opt Data Len field and MUST continue
processing the packet.
- これらの2ビットが10(すなわち、Option Typeと0×60=0×40)であるときに、そのOption Typeのために処理を実装しないノードは、最も重要なビットがOpt Dataレン野原に続くように設定しなければなりません。 ノードは、次に、Opt Dataレン分野を使用して、オプションのコンテンツを無視して、飛ばさなければならなくて、さらに、パケットを処理し続けなければなりません。
- Finally, when these 2 bits are 11 (that is,
Option Type & 0x60 == 0x60), a node not implementing processing
for that Option Type MUST drop the packet.
- これらの2ビットが11(すなわち、Option Typeと0×60=0×60)であるときに、最終的に、そのOption Typeのために処理を実装しないノードはパケットを下げなければなりません。
8.2. Route Discovery Processing
8.2. ルート発見処理
Route Discovery is the mechanism by which a node S wishing to send a packet to a destination node D obtains a source route to D. Route Discovery SHOULD be used only when S attempts to send a packet to D and does not already know a route to D. The node initiating a Route Discovery is known as the "initiator" of the Route Discovery, and the destination node for which the Route Discovery is initiated is known as the "target" of the Route Discovery.
ルートディスカバリーは目的地ノードDにパケットを送りたがっているノードSが送信元経路をD.に入手するメカニズムです。RouteディスカバリーSHOULDは、Sが、パケットをDに送るのを試みる場合にだけ使用されて、D. Routeディスカバリーを開始するノードへのルートは「創始者」としてRouteディスカバリーを知られているのを既に知りません、そして、Routeディスカバリーが開始される目的地ノードはRouteディスカバリーの「目標」として知られています。
Route Discovery operates entirely on demand; a node initiates Route Discovery based on its own origination of new packets for some destination address to which it does not currently know a route. Route Discovery does not depend on any periodic or background exchange of routing information or neighbor node detection at any layer in the network protocol stack at any node.
ディスカバリーが完全に要求に応じて操作するルート。 ノードはそれが現在ルートを知らない何らかの送付先アドレスのためにそれ自身の新しいパケットの創作に基づくRouteディスカバリーを開始します。 ルートディスカバリーはどんなノードのネットワークプロトコル・スタックのどんな層でもルーティング情報か隣人ノード検出のどんな周期的であるかバックグラウンド交換にもよりません。
The Route Discovery procedure utilizes two types of messages, a Route Request (Section 6.2) and a Route Reply (Section 6.3), to actively search the ad hoc network for a route to the desired target destination. These DSR messages MAY be carried in any type of IP packet, through use of the DSR Options header as described in Section 6.
Routeディスカバリー手順は、活発に必要な目標の目的地へのルートとして臨時のネットワークを捜すのに、2つのタイプに関するメッセージ、Route Request(セクション6.2)、およびRoute Reply(セクション6.3)を利用します。 これらのDSRメッセージはどんなタイプのIPパケットでも伝えられるかもしれません、セクション6における説明されるとしてのDSR Optionsヘッダーの使用で。
Except as discussed in Section 8.3.5, a Route Discovery for a destination address SHOULD NOT be initiated unless the initiating node has a packet in its Send Buffer requiring delivery to that destination. A Route Discovery for a given target node MUST NOT be initiated unless permitted by the rate-limiting information contained in the Route Request Table. After each Route Discovery attempt, the interval between successive Route Discoveries for this target SHOULD be doubled, up to a maximum of MaxRequestPeriod, until a valid Route Reply is received for this target.
目的地がSHOULD NOTを扱うのでセクション8.3.5、Routeディスカバリーで議論するのを除いて、開始ノードがその目的地に配送を必要とするSend Bufferにパケットを持っていない場合、開始されてください。 Route Request Tableに含まれたレートを制限する情報によって受入れられない場合、与えられた目標ノードのためのRouteディスカバリーを開始してはいけません。 それぞれのRouteディスカバリー試み、これのための連続したRoute Discoveriesの間隔がSHOULDを狙った後に、倍にされてください、最大MaxRequestPeriodまで、この目標のために有効なRoute Replyを受け取るまで。
Johnson, et al. Experimental [Page 64] RFC 4728 The Dynamic Source Routing Protocol February 2007
ジョンソン、他 ダイナミックな実験的な[64ページ]RFC4728のソースルーティング・プロトコル2007年2月
8.2.1. Originating a Route Request
8.2.1. ルート要求を溯源します。
A node initiating a Route Discovery for some target creates and initializes a Route Request option in a DSR Options header in some IP packet. This MAY be a separate IP packet, used only to carry this Route Request option, or the node MAY include the Route Request option in some existing packet that it needs to send to the target node (e.g., the IP packet originated by this node that caused the node to attempt Route Discovery for the destination address of the packet). The Route Request option MUST be included in a DSR Options header in the packet. To initialize the Route Request option, the node performs the following sequence of steps:
何らかの目標のためにRouteディスカバリーを開始するノードは、あるIPパケットのDSR OptionsヘッダーでRoute Requestオプションを作成して、初期化します。 これは使用されるこのRoute Requestオプションを運ぶ別々のIPパケットであるかもしれませんかノードがそれが目標ノードに送る必要があるある既存のパケットにRoute Requestオプションを含むかもしれません(例えばIPパケットはノードがパケットの送付先アドレスのためにRouteディスカバリーを試みたこのノードで起因しました)。 パケットのDSR OptionsヘッダーにRoute Requestオプションを含まなければなりません。 Route Requestオプションを初期化するために、ノードは以下のステップの以下の系列を実行します:
- The Option Type in the option MUST be set to the value 2.
- オプションにおけるOption Typeは値2に用意ができなければなりません。
- The Opt Data Len field in the option MUST be set to the value 6.
The total size of the Route Request option, when initiated, is 8
octets; the Opt Data Len field excludes the size of the Option
Type and Opt Data Len fields themselves.
- オプションにおけるOpt Dataレン分野を値6に設定しなければなりません。 開始されると、Route Requestオプションの総サイズは8つの八重奏です。 Opt Dataレン分野はOption TypeとOpt Dataレン分野自体のサイズを除きます。
- The Identification field in the option MUST be set to a new value,
different from that used for other Route Requests recently
initiated by this node for this same target address. For example,
each node MAY maintain a single counter value for generating a new
Identification value for each Route Request it initiates.
- オプションにおけるIdentification分野を新しい値に設定しなければなりません、最近この同じあて先アドレスのためのこのノードによって開始された他のRoute Requestsに使用されるそれと、異なります。 例えば、各ノードは、各Route Requestのために新しいIdentificationが値であると生成するために単一のカウンタが値であることを支持するかもしれません。それは開始します。
- The Target Address field in the option MUST be set to the IP
address that is the target of this Route Discovery.
- このRouteディスカバリーの目標であるIPアドレスにオプションにおけるTarget Address分野を設定しなければなりません。
The Source Address in the IP header of this packet MUST be the node's own IP address. The Destination Address in the IP header of this packet MUST be the IP "limited broadcast" address (255.255.255.255).
このパケットのIPヘッダーのSource Addressはノードの自己のIPアドレスであるに違いありません。 このパケットのIPヘッダーのDestination AddressがIP「限られた放送」アドレスであるに違いない、(255.255 .255 .255)。
A node MUST maintain, in its Route Request Table, information about Route Requests that it initiates. When initiating a new Route Request, the node MUST use the information recorded in the Route Request Table entry for the target of that Route Request, and it MUST update that information in the table entry for use in the next Route Request initiated for this target. In particular:
ノードはRoute Request Tableでそれが開始するRoute Requestsの情報を保守しなければなりません。 新しいRoute Requestを開始するとき、ノードはそのRoute Requestの目標にRoute Request Tableエントリーに記録された情報を使用しなければなりません、そして、それはこの目標のために開始された次のRoute Requestにおける使用のためのテーブル項目でその情報をアップデートしなければなりません。 特に:
- The Route Request Table entry for a target node records the Time-
to-Live (TTL) field used in the IP header of the Route Request for
the last Route Discovery initiated by this node for that target
node. This value allows the node to implement a variety of
algorithms for controlling the spread of its Route Request on each
Route Discovery initiated for a target. As examples, two possible
algorithms for this use of the TTL field are described in Section
3.3.3.
- 目的のノードのためのRoute Request TableエントリーがTimeを記録する、-生きてください、その目標ノードのためのこのノードによって開始された最後のRouteディスカバリーにRoute RequestのIPヘッダーで使用される(TTL)分野。 この値で、ノードは目標のために開始されたそれぞれのRouteディスカバリーの上でRoute Requestの普及を制御するためのさまざまなアルゴリズムを実装することができます。 例として、TTL分野のこの使用のための2つの可能なアルゴリズムがセクション3.3.3で説明されます。
Johnson, et al. Experimental [Page 65] RFC 4728 The Dynamic Source Routing Protocol February 2007
ジョンソン、他 ダイナミックな実験的な[65ページ]RFC4728のソースルーティング・プロトコル2007年2月
- The Route Request Table entry for a target node records the number
of consecutive Route Requests initiated for this target since
receiving a valid Route Reply giving a route to that target node,
and the remaining amount of time before which this node MAY next
attempt at a Route Discovery for that target node.
- 目標ノードのためのRoute Request Tableエントリーはその目標ノードにルートを与えながら有効なRoute Replyを受けて以来この目標のために開始された連続したRoute Requestsの数を記録します、そして、このノードが次にそうするかもしれない残っている量の時がその目標ノードのためにRouteでディスカバリーを試みます。
A node MUST use these values to implement a back-off algorithm to
limit the rate at which this node initiates new Route Discoveries
for the same target address. In particular, until a valid Route
Reply is received for this target node address, the timeout
between consecutive Route Discovery initiations for this target
node with the same hop limit SHOULD increase by doubling the
timeout value on each new initiation.
ノードは、このノードが同じあて先アドレスのために新しいRoute Discoveriesを開始するレートを制限するために下に後部アルゴリズムを実装するのにこれらの値を使用しなければなりません。 特に、ノードアドレスをこれのために有効なRoute Replyを受け取るまで狙ってください、この目標ノードのためのSHOULDがそれぞれの新しい開始のときにタイムアウト値を倍にすることによって増強する同じホップ限界による連続したRouteディスカバリー開始の間のタイムアウト。
The behavior of a node processing a packet containing DSR Options header with both a DSR Source Route option and a Route Request option is unspecified. Packets SHOULD NOT contain both a DSR Source Route option and a Route Request option.
DSR Source RouteオプションとRoute Requestオプションの両方でDSR Optionsヘッダーを含むパケットを処理するノードの動きは不特定です。 パケットSHOULD NOTはDSR Source RouteオプションとRoute Requestオプションの両方を含んでいます。
Packets containing a Route Request option SHOULD NOT include an Acknowledgement Request option, SHOULD NOT expect link-layer acknowledgement or passive acknowledgement, and SHOULD NOT be retransmitted. The retransmission of packets containing a Route Request option is controlled solely by the logic described in this section.
リンクレイヤの承認か受け身の承認と、SHOULD NOTが再送されるとRoute RequestオプションSHOULD NOTを含むパケットがAcknowledgement Requestオプションを含んで、SHOULD NOTは、予想します。 Route Requestオプションを含むパケットの「再-トランスミッション」は唯一このセクションで説明された論理によって制御されます。
8.2.2. Processing a Received Route Request Option
8.2.2. 容認されたルート要求オプションを処理します。
When a node receives a packet containing a Route Request option, that node MUST process the option according to the following sequence of steps:
ノードがRoute Requestオプションを含むパケットを受けるとき、以下のステップの以下の系列によると、そのノードはオプションを処理しなければなりません:
- If the Target Address field in the Route Request matches this
node's own IP address, then the node SHOULD return a Route Reply
to the initiator of this Route Request (the Source Address in the
IP header of the packet), as described in Section 8.2.4. The
source route for this Reply is the sequence of hop addresses
- Route RequestのTarget Address分野がこのノードの自己のIPアドレスに合っているなら、ノードSHOULDはこのRoute Request(パケットのIPヘッダーのSource Address)の創始者にRoute Replyを返します、セクション8.2.4で説明されるように。 このReplyのための送信元経路はホップアドレスの系列です。
initiator, Address[1], Address[2], ..., Address[n], target
創始者、Address[1]、Address[2]…, アドレス[n]、目標
where initiator is the address of the initiator of this Route
Request, each Address[i] is an address from the Route Request, and
target is the target of the Route Request (the Target Address
field in the Route Request). The value n here is the number of
addresses recorded in the Route Request, or
(Opt Data Len - 6) / 4.
創始者がこのRoute Requestの創始者のアドレスであるところでは、各Address[i]がRoute Requestからのアドレスです、そして、目標がRoute Request(Route RequestのTarget Address分野)の目標です。 ここの値nは、Route Requestに記録されたアドレスの数、または(Dataレンを選んでください--6)という/4です。
Johnson, et al. Experimental [Page 66] RFC 4728 The Dynamic Source Routing Protocol February 2007
ジョンソン、他 ダイナミックな実験的な[66ページ]RFC4728のソースルーティング・プロトコル2007年2月
The node then MUST replace the Destination Address field in the
Route Request packet's IP header with the value in the Target
Address field in the Route Request option, and continue processing
the rest of the Route Request packet normally. The node MUST NOT
process the Route Request option further and MUST NOT retransmit
the Route Request to propagate it to other nodes as part of the
Route Discovery.
ノードは、Route RequestオプションにおけるTarget Address分野でRoute RequestパケットのIPヘッダーのDestination Address野原を値に取り替えて、次に、通常、Route Requestパケットの残りを処理し続けなければなりません。 ノードは、さらにRoute Requestオプションを処理してはいけなくて、Routeディスカバリーの一部として他のノードにそれを伝播するためにRoute Requestを再送してはいけません。
- Else, the node MUST examine the route recorded in the Route
Request option (the IP Source Address field and the sequence of
Address[i] fields) to determine if this node's own IP address
already appears in this list of addresses. If so, the node MUST
discard the entire packet carrying the Route Request option.
- ほかに、ノードはこのノードの自己のIPアドレスがこの住所録に既に現れるかどうか決定するためにRoute Requestオプション(IP Source Address分野とAddress[i]分野の系列)に記録されたルートを調べなければなりません。 そうだとすれば、Route Requestオプションを運んで、ノードは全体のパケットを捨てなければなりません。
- Else, if the Route Request was received through a network
interface that requires physically bidirectional links for unicast
transmission, the node MUST check if the Route Request was last
forwarded by a node on its blacklist (Section 4.6). If such an
entry is found in the blacklist, and the state of the
unidirectional link is "probable", then the Request MUST be
silently discarded.
- ほかに、ユニキャスト送信のために物理的に双方向のリンクを必要とするネットワーク・インターフェースを通してRoute Requestを受け取ったなら、ノードは、Route Requestが最後にブラックリスト(セクション4.6)のノードによって進められたかどうかチェックしなければなりません。 そのようなエントリーがブラックリストで見つけられて、単方向のリンクの状態が「ありえそうである」なら、静かにRequestを捨てなければなりません。
- Else, if the Route Request was received through a network
interface that requires physically bidirectional links for unicast
transmission, the node MUST check if the Route Request was last
forwarded by a node on its blacklist. If such an entry is found
in the blacklist, and the state of the unidirectional link is
"questionable", then the node MUST create and unicast a Route
Request packet to that previous node, setting the IP Time-To-Live
(TTL) to 1 to prevent the Request from being propagated. If the
node receives a Route Reply in response to the new Request, it
MUST remove the blacklist entry for that node, and SHOULD continue
processing. If the node does not receive a Route Reply within
some reasonable amount of time, the node MUST silently discard the
Route Request packet.
- ほかに、ユニキャスト送信のために物理的に双方向のリンクを必要とするネットワーク・インターフェースを通してRoute Requestを受け取ったなら、ノードは、Route Requestが最後にブラックリストのノードによって進められたかどうかチェックしなければなりません。 そのようなものであるなら、エントリーはブラックリストで見つけられます、そして、単方向のリンクの状態は「疑わしいです」、ノードが作成しなければならないその時、ユニキャストはその前のノードへのRoute Requestパケットをその時です、IP生きるTime(TTL)をRequestが伝播されるのを防ぐ1に設定して。 ノードが新しいRequestに対応してRoute Replyを受けるなら、そのノードのためのブラックリストエントリーを取り除かなければなりません、そして、SHOULDは処理し続けています。 ノードがいつかの妥当な時間以内にRoute Replyを受けないなら、ノードは静かにRoute Requestパケットを捨てなければなりません。
- Else, the node MUST search its Route Request Table for an entry
for the initiator of this Route Request (the IP Source Address
field). If such an entry is found in the table, the node MUST
search the cache of Identification values of recently received
Route Requests in that table entry, to determine if an entry is
present in the cache matching the Identification value and target
node address in this Route Request. If such an (Identification,
target address) entry is found in this cache in this entry in the
Route Request Table, then the node MUST discard the entire packet
carrying the Route Request option.
- ほかに、ノードはこのRoute Request(IP Source Address分野)の創始者のためにエントリーとしてRoute Request Tableを捜さなければなりません。 そのようなエントリーがテーブルで見つけられるなら、ノードは、エントリーがこのRoute RequestのIdentification値と目標ノードアドレスに合っているキャッシュで存在しているかどうか決定するためにそのテーブル項目における、最近容認されたRoute RequestsのIdentification値のキャッシュを捜さなければなりません。 そのような(識別、あて先アドレス)エントリーがRoute Request Tableのこのエントリーにおけるこのキャッシュで見つけられるなら、Route Requestオプションを運んで、ノードは全体のパケットを捨てなければなりません。
Johnson, et al. Experimental [Page 67] RFC 4728 The Dynamic Source Routing Protocol February 2007
ジョンソン、他 ダイナミックな実験的な[67ページ]RFC4728のソースルーティング・プロトコル2007年2月
- Else, this node SHOULD further process the Route Request according
to the following sequence of steps:
- ほかに、以下のステップの以下の系列によると、このノードSHOULDはRoute Requestをさらに処理します:
o Add an entry for this Route Request in its cache of
(Identification, target address) values of recently received
Route Requests.
o 最近の(識別、あて先アドレス)値のキャッシュにおけるこのRoute RequestのためのエントリーがRoute Requestsを受けたと言い足してください。
o Conceptually create a copy of this entire packet and perform
the following steps on the copy of the packet.
o 概念的にこの全体のパケットのコピーを作成してください、そして、パケットのコピーに以下のステップを実行してください。
o Append this node's own IP address to the list of Address[i]
values in the Route Request and increase the value of the Opt
Data Len field in the Route Request by 4 (the size of an IP
address). However, if the node has multiple network
interfaces, this step MUST be modified by the special
processing specified in Section 8.4.
o このノードの自己のIPアドレスをRoute RequestのAddress[i]値のリストに追加してください、そして、Route RequestのOpt Dataレン分野の値を4つ(IPアドレスのサイズ)増強してください。 しかしながら、ノードに複数のネットワーク・インターフェースがあるなら、セクション8.4で指定された特別な処理でこのステップを変更しなければなりません。
o This node SHOULD search its own Route Cache for a route (from
itself, as if it were the source of a packet) to the target of
this Route Request. If such a route is found in its Route
Cache, then this node SHOULD follow the procedure outlined in
Section 8.2.3 to return a "cached Route Reply" to the initiator
of this Route Request, if permitted by the restrictions
specified there.
o このノードSHOULDはこのRoute Requestの目標へのルート(まるでそれがそれ自体パケットの源であるかのように)としてそれ自身のRoute Cacheを捜します。 そのようなルートがRoute Cacheで見つけられるなら、このノードSHOULDは「キャッシュされたRoute Reply」をこのRoute Requestの創始者に返すためにセクション8.2.3に概説された手順に従います、そこで指定された制限で受入れられるなら。
o If the node does not return a cached Route Reply, then this
node SHOULD transmit this copy of the packet as a link-layer
broadcast, with a short jitter delay before the broadcast is
sent. The jitter period SHOULD be chosen as a random period,
uniformly distributed between 0 and BroadcastJitter.
o ノードがキャッシュされたRoute Replyを返さないなら、このノードSHOULDは放送を送る前の少しジター遅れがあるリンク層ブロードキャストとしてパケットのこのコピーを伝えます。 以上、SHOULD。ジター、無作為の期間として、一様に0とBroadcastJitterの間に分配されて、選ばれてください。
8.2.3. Generating a Route Reply Using the Route Cache
8.2.3. 経路キャッシュを使用することでルート回答を生成します。
As described in Section 3.3.2, it is possible for a node processing a received Route Request to avoid propagating the Route Request further toward the target of the Request, if this node has in its Route Cache a route from itself to this target. Such a Route Reply generated by a node from its own cached route to the target of a Route Request is called a "cached Route Reply", and this mechanism can greatly reduce the overall overhead of Route Discovery on the network by reducing the flood of Route Requests. The general processing of a received Route Request is described in Section 8.2.2; this section specifies the additional requirements that MUST be met before a cached Route Reply may be generated and returned and specifies the procedure for returning such a cached Route Reply.
セクション3.3.2で説明されるように、容認されたRoute Requestを処理するノードに、さらにRequestの目標に向かってRoute Requestを伝播するのを避けるのは可能です、このノードがRoute Cacheにそれ自体からこの目標までルートを持っているなら。 ノードによってそれ自身のキャッシュされたルートからRoute Requestの目標まで生成されたそのようなRoute Replyは「キャッシュされたRoute Reply」と呼ばれます、そして、このメカニズムはネットワークでRoute Requestsの洪水を減少させることによって、Routeディスカバリーの総合的なオーバーヘッドを大いに下げることができます。 容認されたRoute Requestの一般的な処理はセクション8.2.2で説明されます。 このセクションは、キャッシュされたRoute Replyを生成して、返すかもしれない前に満たさなければならない追加必要条件を指定して、そのようなキャッシュされたRoute Replyを返すための手順を指定します。
Johnson, et al. Experimental [Page 68] RFC 4728 The Dynamic Source Routing Protocol February 2007
Johnson, et al. Experimental [Page 68] RFC 4728 The Dynamic Source Routing Protocol February 2007
While processing a received Route Request, for a node to possibly return a cached Route Reply, it MUST have in its Route Cache a route from itself to the target of this Route Request. However, before generating a cached Route Reply for this Route Request, the node MUST verify that there are no duplicate addresses listed in the route accumulated in the Route Request together with the route from this node's Route Cache. Specifically, there MUST be no duplicates among the following addresses:
While processing a received Route Request, for a node to possibly return a cached Route Reply, it MUST have in its Route Cache a route from itself to the target of this Route Request. However, before generating a cached Route Reply for this Route Request, the node MUST verify that there are no duplicate addresses listed in the route accumulated in the Route Request together with the route from this node's Route Cache. Specifically, there MUST be no duplicates among the following addresses:
- The IP Source Address of the packet containing the Route Request,
- The IP Source Address of the packet containing the Route Request,
- The Address[i] fields in the Route Request, and
- The Address[i] fields in the Route Request, and
- The nodes listed in the route obtained from this node's Route
Cache, excluding the address of this node itself (this node itself
is the common point between the route accumulated in the Route
Request and the route obtained from the Route Cache).
- The nodes listed in the route obtained from this node's Route Cache, excluding the address of this node itself (this node itself is the common point between the route accumulated in the Route Request and the route obtained from the Route Cache).
If any duplicates exist among these addresses, then the node MUST NOT send a cached Route Reply using this route from the Route Cache (it is possible that this node has another route in its Route Cache for which the above restriction on duplicate addresses is met, allowing the node to send a cached Route Reply based on that cached route, instead). The node SHOULD continue to process the Route Request as described in Section 8.2.2 if it does not send a cached Route Reply.
If any duplicates exist among these addresses, then the node MUST NOT send a cached Route Reply using this route from the Route Cache (it is possible that this node has another route in its Route Cache for which the above restriction on duplicate addresses is met, allowing the node to send a cached Route Reply based on that cached route, instead). The node SHOULD continue to process the Route Request as described in Section 8.2.2 if it does not send a cached Route Reply.
If the Route Request and the route from the Route Cache meet the restriction above, then the node SHOULD construct and return a cached Route Reply as follows:
If the Route Request and the route from the Route Cache meet the restriction above, then the node SHOULD construct and return a cached Route Reply as follows:
- The source route for this Route Reply is the sequence of hop
addresses
- The source route for this Route Reply is the sequence of hop addresses
initiator, Address[1], Address[2], ..., Address[n], c-route
initiator, Address[1], Address[2], ..., Address[n], c-route
where initiator is the address of the initiator of this Route
Request, each Address[i] is an address from the Route Request, and
c-route is the sequence of hop addresses in the source route to
this target node, obtained from the node's Route Cache. In
appending this cached route to the source route for the reply, the
address of this node itself MUST be excluded, since it is already
listed as Address[n].
where initiator is the address of the initiator of this Route Request, each Address[i] is an address from the Route Request, and c-route is the sequence of hop addresses in the source route to this target node, obtained from the node's Route Cache. In appending this cached route to the source route for the reply, the address of this node itself MUST be excluded, since it is already listed as Address[n].
- Send a Route Reply to the initiator of the Route Request, using
the procedure defined in Section 8.2.4. The initiator of the
Route Request is indicated in the Source Address field in the
packet's IP header.
- Send a Route Reply to the initiator of the Route Request, using the procedure defined in Section 8.2.4. The initiator of the Route Request is indicated in the Source Address field in the packet's IP header.
Johnson, et al. Experimental [Page 69] RFC 4728 The Dynamic Source Routing Protocol February 2007
Johnson, et al. Experimental [Page 69] RFC 4728 The Dynamic Source Routing Protocol February 2007
Before sending the cached Route Reply, however, the node MAY delay the Reply in order to help prevent a possible Route Reply "storm", as described in Section 8.2.5.
Before sending the cached Route Reply, however, the node MAY delay the Reply in order to help prevent a possible Route Reply "storm", as described in Section 8.2.5.
If the node returns a cached Route Reply as described above, then the node MUST NOT propagate the Route Request further (i.e., the node MUST NOT rebroadcast the Route Request). In this case, instead, if the packet contains no other DSR options and contains no payload after the DSR Options header (e.g., the Route Request is not piggybacked on a TCP or UDP packet), then the node SHOULD simply discard the packet. Otherwise (if the packet contains other DSR options or contains any payload after the DSR Options header), the node SHOULD forward the packet along the cached route to the target of the Route Request. Specifically, if the node does so, it MUST use the following steps:
If the node returns a cached Route Reply as described above, then the node MUST NOT propagate the Route Request further (i.e., the node MUST NOT rebroadcast the Route Request). In this case, instead, if the packet contains no other DSR options and contains no payload after the DSR Options header (e.g., the Route Request is not piggybacked on a TCP or UDP packet), then the node SHOULD simply discard the packet. Otherwise (if the packet contains other DSR options or contains any payload after the DSR Options header), the node SHOULD forward the packet along the cached route to the target of the Route Request. Specifically, if the node does so, it MUST use the following steps:
- Copy the Target Address from the Route Request option in the DSR
Options header to the Destination Address field in the packet's IP
header.
- Copy the Target Address from the Route Request option in the DSR Options header to the Destination Address field in the packet's IP header.
- Remove the Route Request option from the DSR Options header in the
packet, and add a DSR Source Route option to the packet's DSR
Options header.
- Remove the Route Request option from the DSR Options header in the packet, and add a DSR Source Route option to the packet's DSR Options header.
- In the DSR Source Route option, set the Address[i] fields to
represent the source route found in this node's Route Cache to the
original target of the Route Discovery (the new IP Destination
Address of the packet). Specifically, the node copies the hop
addresses of the source route into sequential Address[i] fields in
the DSR Source Route option, for i = 1, 2, ..., n. Address[1],
here, is the address of this node itself (the first address in the
source route found from this node to the original target of the
Route Discovery). The value n, here, is the number of hop
addresses in this source route, excluding the destination of the
packet (which is instead already represented in the Destination
Address field in the packet's IP header).
- In the DSR Source Route option, set the Address[i] fields to represent the source route found in this node's Route Cache to the original target of the Route Discovery (the new IP Destination Address of the packet). Specifically, the node copies the hop addresses of the source route into sequential Address[i] fields in the DSR Source Route option, for i = 1, 2, ..., n. Address[1], here, is the address of this node itself (the first address in the source route found from this node to the original target of the Route Discovery). The value n, here, is the number of hop addresses in this source route, excluding the destination of the packet (which is instead already represented in the Destination Address field in the packet's IP header).
- Initialize the Segments Left field in the DSR Source Route option
to n as defined above.
- Initialize the Segments Left field in the DSR Source Route option to n as defined above.
- The First Hop External (F) bit in the DSR Source Route option MUST
be set to 0.
- The First Hop External (F) bit in the DSR Source Route option MUST be set to 0.
- The Last Hop External (L) bit in the DSR Source Route option is
copied from the External bit flagging the last hop in the source
route for the packet, as indicated in the Route Cache.
- The Last Hop External (L) bit in the DSR Source Route option is copied from the External bit flagging the last hop in the source route for the packet, as indicated in the Route Cache.
Johnson, et al. Experimental [Page 70] RFC 4728 The Dynamic Source Routing Protocol February 2007
Johnson, et al. Experimental [Page 70] RFC 4728 The Dynamic Source Routing Protocol February 2007
- The Salvage field in the DSR Source Route option MUST be
initialized to some nonzero value; the particular nonzero value
used SHOULD be MAX_SALVAGE_COUNT. By initializing this field to a
nonzero value, nodes forwarding or overhearing this packet will
not consider a link to exist between the IP Source Address of the
packet and the Address[1] address in the DSR Source Route option
(e.g., they will not attempt to add this to their Route Cache as a
link). By choosing MAX_SALVAGE_COUNT as the nonzero value to
which the node initializes this field, nodes furthermore will not
attempt to salvage this packet.
- The Salvage field in the DSR Source Route option MUST be initialized to some nonzero value; the particular nonzero value used SHOULD be MAX_SALVAGE_COUNT. By initializing this field to a nonzero value, nodes forwarding or overhearing this packet will not consider a link to exist between the IP Source Address of the packet and the Address[1] address in the DSR Source Route option (e.g., they will not attempt to add this to their Route Cache as a link). By choosing MAX_SALVAGE_COUNT as the nonzero value to which the node initializes this field, nodes furthermore will not attempt to salvage this packet.
- Transmit the packet to the next-hop node on the new source route
in the packet, using the forwarding procedure described in Section
8.1.5.
- Transmit the packet to the next-hop node on the new source route in the packet, using the forwarding procedure described in Section 8.1.5.
8.2.4. Originating a Route Reply
8.2.4. Originating a Route Reply
A node originates a Route Reply in order to reply to a received and processed Route Request, according to the procedures described in Sections 8.2.2 and 8.2.3. The Route Reply is returned in a Route Reply option (Section 6.3). The Route Reply option MAY be returned to the initiator of the Route Request in a separate IP packet, used only to carry this Route Reply option, or it MAY be included in any other IP packet being sent to this address.
A node originates a Route Reply in order to reply to a received and processed Route Request, according to the procedures described in Sections 8.2.2 and 8.2.3. The Route Reply is returned in a Route Reply option (Section 6.3). The Route Reply option MAY be returned to the initiator of the Route Request in a separate IP packet, used only to carry this Route Reply option, or it MAY be included in any other IP packet being sent to this address.
The Route Reply option MUST be included in a DSR Options header in the packet returned to the initiator. To initialize the Route Reply option, the node performs the following sequence of steps:
The Route Reply option MUST be included in a DSR Options header in the packet returned to the initiator. To initialize the Route Reply option, the node performs the following sequence of steps:
- The Option Type in the option MUST be set to the value 3.
- The Option Type in the option MUST be set to the value 3.
- The Opt Data Len field in the option MUST be set to the value
(n * 4) + 3, where n is the number of addresses in the source
route being returned (excluding the Route Discovery initiator
node's address).
- The Opt Data Len field in the option MUST be set to the value (n * 4) + 3, where n is the number of addresses in the source route being returned (excluding the Route Discovery initiator node's address).
- If this node is the target of the Route Request, the Last Hop
External (L) bit in the option MUST be initialized to 0.
- If this node is the target of the Route Request, the Last Hop External (L) bit in the option MUST be initialized to 0.
- The Reserved field in the option MUST be initialized to 0.
- The Reserved field in the option MUST be initialized to 0.
- The Route Request Identifier MUST be initialized to the Identifier
field of the Route Request to which this Route Reply is sent in
response.
- The Route Request Identifier MUST be initialized to the Identifier field of the Route Request to which this Route Reply is sent in response.
- The sequence of hop addresses in the source route are copied into
the Address[i] fields of the option. Address[1] MUST be set to
the first-hop address of the route after the initiator of the
- The sequence of hop addresses in the source route are copied into the Address[i] fields of the option. Address[1] MUST be set to the first-hop address of the route after the initiator of the
Johnson, et al. Experimental [Page 71] RFC 4728 The Dynamic Source Routing Protocol February 2007
Johnson, et al. Experimental [Page 71] RFC 4728 The Dynamic Source Routing Protocol February 2007
Route Discovery, Address[n] MUST be set to the last-hop address of
the source route (the address of the target node), and each other
Address[i] MUST be set to the next address in sequence in the
source route being returned.
Route Discovery, Address[n] MUST be set to the last-hop address of the source route (the address of the target node), and each other Address[i] MUST be set to the next address in sequence in the source route being returned.
The Destination Address field in the IP header of the packet carrying the Route Reply option MUST be set to the address of the initiator of the Route Discovery (i.e., for a Route Reply being returned in response to some Route Request, the IP Source Address of the Route Request).
The Destination Address field in the IP header of the packet carrying the Route Reply option MUST be set to the address of the initiator of the Route Discovery (i.e., for a Route Reply being returned in response to some Route Request, the IP Source Address of the Route Request).
After creating and initializing the Route Reply option and the IP packet containing it, send the Route Reply. In sending the Route Reply from this node (but not from nodes forwarding the Route Reply), this node SHOULD delay the Reply by a small jitter period chosen randomly between 0 and BroadcastJitter.
After creating and initializing the Route Reply option and the IP packet containing it, send the Route Reply. In sending the Route Reply from this node (but not from nodes forwarding the Route Reply), this node SHOULD delay the Reply by a small jitter period chosen randomly between 0 and BroadcastJitter.
When returning any Route Reply in the case in which the MAC protocol in use in the network is not capable of transmitting unicast packets over unidirectional links, the source route used for routing the Route Reply packet MUST be obtained by reversing the sequence of hops in the Route Request packet (the source route that is then returned in the Route Reply). This restriction on returning a Route Reply enables the Route Reply to test this sequence of hops for bidirectionality, preventing the Route Reply from being received by the initiator of the Route Discovery unless each of the hops over which the Route Reply is returned (and thus each of the hops in the source route being returned in the Reply) is bidirectional.
When returning any Route Reply in the case in which the MAC protocol in use in the network is not capable of transmitting unicast packets over unidirectional links, the source route used for routing the Route Reply packet MUST be obtained by reversing the sequence of hops in the Route Request packet (the source route that is then returned in the Route Reply). This restriction on returning a Route Reply enables the Route Reply to test this sequence of hops for bidirectionality, preventing the Route Reply from being received by the initiator of the Route Discovery unless each of the hops over which the Route Reply is returned (and thus each of the hops in the source route being returned in the Reply) is bidirectional.
If sending a Route Reply to the initiator of the Route Request requires performing a Route Discovery, the Route Reply option MUST be piggybacked on the packet that contains the Route Request. This piggybacking prevents a recursive dependency wherein the target of the new Route Request (which was itself the initiator of the original Route Request) must do another Route Request in order to return its Route Reply.
If sending a Route Reply to the initiator of the Route Request requires performing a Route Discovery, the Route Reply option MUST be piggybacked on the packet that contains the Route Request. This piggybacking prevents a recursive dependency wherein the target of the new Route Request (which was itself the initiator of the original Route Request) must do another Route Request in order to return its Route Reply.
If sending the Route Reply to the initiator of the Route Request does not require performing a Route Discovery, a node SHOULD send a unicast Route Reply in response to every Route Request it receives for which it is the target node.
If sending the Route Reply to the initiator of the Route Request does not require performing a Route Discovery, a node SHOULD send a unicast Route Reply in response to every Route Request it receives for which it is the target node.
8.2.5. Preventing Route Reply Storms
8.2.5. Preventing Route Reply Storms
The ability for nodes to reply to a Route Request based on information in their Route Caches, as described in Sections 3.3.2 and 8.2.3, could result in a possible Route Reply "storm" in some cases. In particular, if a node broadcasts a Route Request for a target node
The ability for nodes to reply to a Route Request based on information in their Route Caches, as described in Sections 3.3.2 and 8.2.3, could result in a possible Route Reply "storm" in some cases. In particular, if a node broadcasts a Route Request for a target node
Johnson, et al. Experimental [Page 72] RFC 4728 The Dynamic Source Routing Protocol February 2007
Johnson, et al. Experimental [Page 72] RFC 4728 The Dynamic Source Routing Protocol February 2007
for which the node's neighbors have a route in their Route Caches, each neighbor may attempt to send a Route Reply, thereby wasting bandwidth and possibly increasing the number of network collisions in the area.
for which the node's neighbors have a route in their Route Caches, each neighbor may attempt to send a Route Reply, thereby wasting bandwidth and possibly increasing the number of network collisions in the area.
For example, the figure below shows a situation in which nodes B, C, D, E, and F all receive A's Route Request for target G, and each has the indicated route cached for this target:
For example, the figure below shows a situation in which nodes B, C, D, E, and F all receive A's Route Request for target G, and each has the indicated route cached for this target:
+-----+ +-----+
| D |< >| C |
+-----+ \ / +-----+
Cache: C - B - G \ / Cache: B - G
\ +-----+ /
-| A |-
+-----+\ +-----+ +-----+
| | \--->| B | | G |
/ \ +-----+ +-----+
/ \ Cache: G
v v
+-----+ +-----+
| E | | F |
+-----+ +-----+
Cache: F - B - G Cache: B - G
+-----+ +-----+ | D |< >| C | +-----+ \ / +-----+ Cache: C - B - G \ / Cache: B - G \ +-----+ / -| A |- +-----+\ +-----+ +-----+ | | \--->| B | | G | / \ +-----+ +-----+ / \ Cache: G v v +-----+ +-----+ | E | | F | +-----+ +-----+ Cache: F - B - G Cache: B - G
Normally, each of these nodes would attempt to reply from its own Route Cache, and they would thus all send their Route Replies at about the same time, since they all received the broadcast Route Request at about the same time. Such simultaneous Route Replies from different nodes all receiving the Route Request may cause local congestion in the wireless network and may create packet collisions among some or all of these Replies if the MAC protocol in use does not provide sufficient collision avoidance for these packets. In addition, it will often be the case that the different replies will indicate routes of different lengths, as shown in this example.
Normally, each of these nodes would attempt to reply from its own Route Cache, and they would thus all send their Route Replies at about the same time, since they all received the broadcast Route Request at about the same time. Such simultaneous Route Replies from different nodes all receiving the Route Request may cause local congestion in the wireless network and may create packet collisions among some or all of these Replies if the MAC protocol in use does not provide sufficient collision avoidance for these packets. In addition, it will often be the case that the different replies will indicate routes of different lengths, as shown in this example.
In order to reduce these effects, if a node can put its network interface into promiscuous receive mode, it MAY delay sending its own Route Reply for a short period, while listening to see if the initiating node begins using a shorter route first. Specifically, this node MAY delay sending its own Route Reply for a random period
In order to reduce these effects, if a node can put its network interface into promiscuous receive mode, it MAY delay sending its own Route Reply for a short period, while listening to see if the initiating node begins using a shorter route first. Specifically, this node MAY delay sending its own Route Reply for a random period
d = H * (h - 1 + r)
d = H * (h - 1 + r)
where h is the length in number of network hops for the route to be returned in this node's Route Reply, r is a random floating point number between 0 and 1, and H is a small constant delay (at least twice the maximum wireless link propagation delay) to be introduced
where h is the length in number of network hops for the route to be returned in this node's Route Reply, r is a random floating point number between 0 and 1, and H is a small constant delay (at least twice the maximum wireless link propagation delay) to be introduced
Johnson, et al. Experimental [Page 73] RFC 4728 The Dynamic Source Routing Protocol February 2007
Johnson, et al. Experimental [Page 73] RFC 4728 The Dynamic Source Routing Protocol February 2007
per hop. This delay effectively randomizes the time at which each node sends its Route Reply, with all nodes sending Route Replies giving routes of length less than h sending their Replies before this node, and all nodes sending Route Replies giving routes of length greater than h send their Replies after this node.
per hop. This delay effectively randomizes the time at which each node sends its Route Reply, with all nodes sending Route Replies giving routes of length less than h sending their Replies before this node, and all nodes sending Route Replies giving routes of length greater than h send their Replies after this node.
Within the delay period, this node promiscuously receives all packets, looking for data packets from the initiator of this Route Discovery destined for the target of the Route Discovery. If such a data packet received by this node during the delay period uses a source route of length less than or equal to h, this node may infer that the initiator of the Route Discovery has already received a Route Reply giving an equally good or better route. In this case, this node SHOULD cancel its delay timer and SHOULD NOT send its Route Reply for this Route Discovery.
Within the delay period, this node promiscuously receives all packets, looking for data packets from the initiator of this Route Discovery destined for the target of the Route Discovery. If such a data packet received by this node during the delay period uses a source route of length less than or equal to h, this node may infer that the initiator of the Route Discovery has already received a Route Reply giving an equally good or better route. In this case, this node SHOULD cancel its delay timer and SHOULD NOT send its Route Reply for this Route Discovery.
8.2.6. Processing a Received Route Reply Option
8.2.6. Processing a Received Route Reply Option
Section 8.1.4 describes the general processing for a received packet, including the addition of routing information from options in the packet's DSR Options header to the receiving node's Route Cache.
Section 8.1.4 describes the general processing for a received packet, including the addition of routing information from options in the packet's DSR Options header to the receiving node's Route Cache.
If the received packet contains a Route Reply, no additional special processing of the Route Reply option is required beyond what is described there. As described in Section 4.1, anytime a node adds new information to its Route Cache (including the information added from this Route Reply option), the node SHOULD check each packet in its own Send Buffer (Section 4.2) to determine whether a route to that packet's IP Destination Address now exists in the node's Route Cache (including the information just added to the Cache). If so, the packet SHOULD then be sent using that route and removed from the Send Buffer. This general procedure handles all processing required for a received Route Reply option.
If the received packet contains a Route Reply, no additional special processing of the Route Reply option is required beyond what is described there. As described in Section 4.1, anytime a node adds new information to its Route Cache (including the information added from this Route Reply option), the node SHOULD check each packet in its own Send Buffer (Section 4.2) to determine whether a route to that packet's IP Destination Address now exists in the node's Route Cache (including the information just added to the Cache). If so, the packet SHOULD then be sent using that route and removed from the Send Buffer. This general procedure handles all processing required for a received Route Reply option.
When using a MAC protocol that requires bidirectional links for unicast transmission, a unidirectional link may be discovered by the propagation of the Route Request. When the Route Reply is sent over the reverse path, a forwarding node may discover that the next-hop is unreachable. In this case, it MUST add the next-hop address to its blacklist (Section 4.6).
When using a MAC protocol that requires bidirectional links for unicast transmission, a unidirectional link may be discovered by the propagation of the Route Request. When the Route Reply is sent over the reverse path, a forwarding node may discover that the next-hop is unreachable. In this case, it MUST add the next-hop address to its blacklist (Section 4.6).
8.3. Route Maintenance Processing
8.3. Route Maintenance Processing
Route Maintenance is the mechanism by which a source node S is able to detect, while using a source route to some destination node D, if the network topology has changed such that it can no longer use its route to D because a link along the route no longer works. When Route Maintenance indicates that a source route is broken, S can
Route Maintenance is the mechanism by which a source node S is able to detect, while using a source route to some destination node D, if the network topology has changed such that it can no longer use its route to D because a link along the route no longer works. When Route Maintenance indicates that a source route is broken, S can
Johnson, et al. Experimental [Page 74] RFC 4728 The Dynamic Source Routing Protocol February 2007
Johnson, et al. Experimental [Page 74] RFC 4728 The Dynamic Source Routing Protocol February 2007
attempt to use any other route it happens to know to D or can invoke Route Discovery again to find a new route for subsequent packets to D. Route Maintenance for this route is used only when S is actually sending packets to D.
attempt to use any other route it happens to know to D or can invoke Route Discovery again to find a new route for subsequent packets to D. Route Maintenance for this route is used only when S is actually sending packets to D.
Specifically, when forwarding a packet, a node MUST attempt to confirm the reachability of the next-hop node, unless such confirmation had been received in the last MaintHoldoffTime period. Individual implementations MAY choose to bypass such confirmation for some limited number of packets, as long as those packets all fall within MaintHoldoffTime since the last confirmation. If no confirmation is received after the retransmission of MaxMaintRexmt acknowledgement requests, after the initial transmission of the packet, and conceptually including all retransmissions provided by the MAC layer, the node determines that the link for this next-hop node of the source route is "broken". This confirmation from the next-hop node for Route Maintenance can be implemented using a link- layer acknowledgement (Section 8.3.1), a "passive acknowledgement" (Section 8.3.2), or a network-layer acknowledgement (Section 8.3.3); the particular strategy for retransmission timing depends on the type of acknowledgement mechanism used. When not using link-layer acknowledgements for Route Maintenance, nodes SHOULD use passive acknowledgements when possible but SHOULD try requesting a network- layer acknowledgement one or more times before deciding that the link has failed and originating a Route Error to the original sender of the packet, as described in Section 8.3.4.
Specifically, when forwarding a packet, a node MUST attempt to confirm the reachability of the next-hop node, unless such confirmation had been received in the last MaintHoldoffTime period. Individual implementations MAY choose to bypass such confirmation for some limited number of packets, as long as those packets all fall within MaintHoldoffTime since the last confirmation. If no confirmation is received after the retransmission of MaxMaintRexmt acknowledgement requests, after the initial transmission of the packet, and conceptually including all retransmissions provided by the MAC layer, the node determines that the link for this next-hop node of the source route is "broken". This confirmation from the next-hop node for Route Maintenance can be implemented using a link- layer acknowledgement (Section 8.3.1), a "passive acknowledgement" (Section 8.3.2), or a network-layer acknowledgement (Section 8.3.3); the particular strategy for retransmission timing depends on the type of acknowledgement mechanism used. When not using link-layer acknowledgements for Route Maintenance, nodes SHOULD use passive acknowledgements when possible but SHOULD try requesting a network- layer acknowledgement one or more times before deciding that the link has failed and originating a Route Error to the original sender of the packet, as described in Section 8.3.4.
In deciding whether or not to send a Route Error in response to attempting to forward a packet from some sender over a broken link, a node MUST limit the number of consecutive packets from a single sender that the node attempts to forward over this same broken link for which the node chooses not to return a Route Error. This requirement MAY be satisfied by returning a Route Error for each packet that the node attempts to forward over a broken link.
In deciding whether or not to send a Route Error in response to attempting to forward a packet from some sender over a broken link, a node MUST limit the number of consecutive packets from a single sender that the node attempts to forward over this same broken link for which the node chooses not to return a Route Error. This requirement MAY be satisfied by returning a Route Error for each packet that the node attempts to forward over a broken link.
8.3.1. Using Link-Layer Acknowledgements
8.3.1. Using Link-Layer Acknowledgements
If the MAC protocol in use provides feedback as to the successful delivery of a data packet (such as is provided for unicast packets by the link-layer acknowledgement frame defined by IEEE 802.11 [IEEE80211]), then the use of the DSR Acknowledgement Request and Acknowledgement options is not necessary. If such link-layer feedback is available, it SHOULD be used instead of any other acknowledgement mechanism for Route Maintenance, and the node SHOULD NOT use either passive acknowledgements or network-layer acknowledgements for Route Maintenance.
If the MAC protocol in use provides feedback as to the successful delivery of a data packet (such as is provided for unicast packets by the link-layer acknowledgement frame defined by IEEE 802.11 [IEEE80211]), then the use of the DSR Acknowledgement Request and Acknowledgement options is not necessary. If such link-layer feedback is available, it SHOULD be used instead of any other acknowledgement mechanism for Route Maintenance, and the node SHOULD NOT use either passive acknowledgements or network-layer acknowledgements for Route Maintenance.
Johnson, et al. Experimental [Page 75] RFC 4728 The Dynamic Source Routing Protocol February 2007
Johnson, et al. Experimental [Page 75] RFC 4728 The Dynamic Source Routing Protocol February 2007
When using link-layer acknowledgements for Route Maintenance, the retransmission timing and the timing at which retransmission attempts are scheduled are generally controlled by the particular link layer implementation in use in the network. For example, in IEEE 802.11, the link-layer acknowledgement is returned after a unicast packet as a part of the basic access method of the IEEE 802.11 Distributed Coordination Function (DCF) MAC protocol; the time at which the acknowledgement is expected to arrive and the time at which the next retransmission attempt (if necessary) will occur are controlled by the MAC protocol implementation.
When using link-layer acknowledgements for Route Maintenance, the retransmission timing and the timing at which retransmission attempts are scheduled are generally controlled by the particular link layer implementation in use in the network. For example, in IEEE 802.11, the link-layer acknowledgement is returned after a unicast packet as a part of the basic access method of the IEEE 802.11 Distributed Coordination Function (DCF) MAC protocol; the time at which the acknowledgement is expected to arrive and the time at which the next retransmission attempt (if necessary) will occur are controlled by the MAC protocol implementation.
When a node receives a link-layer acknowledgement for any packet in its Maintenance Buffer, that node SHOULD remove from its Maintenance Buffer that packet, as well as any other packets in its Maintenance Buffer with the same next-hop destination.
When a node receives a link-layer acknowledgement for any packet in its Maintenance Buffer, that node SHOULD remove from its Maintenance Buffer that packet, as well as any other packets in its Maintenance Buffer with the same next-hop destination.
8.3.2. Using Passive Acknowledgements
8.3.2. Using Passive Acknowledgements
When link-layer acknowledgements are not available, but passive acknowledgements [JUBIN87] are available, passive acknowledgements SHOULD be used for Route Maintenance when originating or forwarding a packet along any hop other than the last hop (the hop leading to the IP Destination Address node of the packet). In particular, passive acknowledgements SHOULD be used for Route Maintenance in such cases if the node can place its network interface into "promiscuous" receive mode, and if network links used for data packets generally operate bidirectionally.
When link-layer acknowledgements are not available, but passive acknowledgements [JUBIN87] are available, passive acknowledgements SHOULD be used for Route Maintenance when originating or forwarding a packet along any hop other than the last hop (the hop leading to the IP Destination Address node of the packet). In particular, passive acknowledgements SHOULD be used for Route Maintenance in such cases if the node can place its network interface into "promiscuous" receive mode, and if network links used for data packets generally operate bidirectionally.
A node MUST NOT attempt to use passive acknowledgements for Route Maintenance for a packet originated or forwarded over its last hop (the hop leading to the IP Destination Address node of the packet), since the receiving node will not be forwarding the packet and thus no passive acknowledgement will be available to be heard by this node. Beyond this restriction, a node MAY utilize a variety of strategies in using passive acknowledgements for Route Maintenance of a packet that it originates or forwards. For example, the following two strategies are possible:
A node MUST NOT attempt to use passive acknowledgements for Route Maintenance for a packet originated or forwarded over its last hop (the hop leading to the IP Destination Address node of the packet), since the receiving node will not be forwarding the packet and thus no passive acknowledgement will be available to be heard by this node. Beyond this restriction, a node MAY utilize a variety of strategies in using passive acknowledgements for Route Maintenance of a packet that it originates or forwards. For example, the following two strategies are possible:
- Each time a node receives a packet to be forwarded to a node other
than the final destination (the IP Destination Address of the
packet), that node sends the original transmission of that packet
without requesting a network-layer acknowledgement for it. If no
passive acknowledgement is received within PassiveAckTimeout after
this transmission, the node retransmits the packet, again without
requesting a network-layer acknowledgement for it; the same
PassiveAckTimeout timeout value is used for each such attempt. If
no acknowledgement has been received after a total of
TryPassiveAcks retransmissions of the packet, network-layer
- Each time a node receives a packet to be forwarded to a node other than the final destination (the IP Destination Address of the packet), that node sends the original transmission of that packet without requesting a network-layer acknowledgement for it. If no passive acknowledgement is received within PassiveAckTimeout after this transmission, the node retransmits the packet, again without requesting a network-layer acknowledgement for it; the same PassiveAckTimeout timeout value is used for each such attempt. If no acknowledgement has been received after a total of TryPassiveAcks retransmissions of the packet, network-layer
Johnson, et al. Experimental [Page 76] RFC 4728 The Dynamic Source Routing Protocol February 2007
Johnson, et al. Experimental [Page 76] RFC 4728 The Dynamic Source Routing Protocol February 2007
acknowledgements (as described in Section 8.3.3) are requested for
all remaining attempts for that packet.
acknowledgements (as described in Section 8.3.3) are requested for all remaining attempts for that packet.
- Each node maintains a table of possible next-hop destination
nodes, noting whether or not passive acknowledgements can
typically be expected from transmission to that node, and the
expected latency and jitter of a passive acknowledgement from that
node. Each time a node receives a packet to be forwarded to a
node other than the IP Destination Address, the node checks its
table of next-hop destination nodes to determine whether to use a
passive acknowledgement or a network-layer acknowledgement for
that transmission to that node. The timeout for this packet can
also be derived from this table. A node using this method SHOULD
prefer using passive acknowledgements to network-layer
acknowledgements.
- Each node maintains a table of possible next-hop destination nodes, noting whether or not passive acknowledgements can typically be expected from transmission to that node, and the expected latency and jitter of a passive acknowledgement from that node. Each time a node receives a packet to be forwarded to a node other than the IP Destination Address, the node checks its table of next-hop destination nodes to determine whether to use a passive acknowledgement or a network-layer acknowledgement for that transmission to that node. The timeout for this packet can also be derived from this table. A node using this method SHOULD prefer using passive acknowledgements to network-layer acknowledgements.
In using passive acknowledgements for a packet that it originates or forwards, a node considers the later receipt of a new packet (e.g., with promiscuous receive mode enabled on its network interface) an acknowledgement of this first packet if both of the following two tests succeed:
In using passive acknowledgements for a packet that it originates or forwards, a node considers the later receipt of a new packet (e.g., with promiscuous receive mode enabled on its network interface) an acknowledgement of this first packet if both of the following two tests succeed:
- The Source Address, Destination Address, Protocol, Identification,
and Fragment Offset fields in the IP header of the two packets
MUST match [RFC791].
- The Source Address, Destination Address, Protocol, Identification, and Fragment Offset fields in the IP header of the two packets MUST match [RFC791].
- If either packet contains a DSR Source Route header, both packets
MUST contain one, and the value in the Segments Left field in the
DSR Source Route header of the new packet MUST be less than that
in the first packet.
- If either packet contains a DSR Source Route header, both packets MUST contain one, and the value in the Segments Left field in the DSR Source Route header of the new packet MUST be less than that in the first packet.
When a node hears such a passive acknowledgement for any packet in its Maintenance Buffer, that node SHOULD remove from its Maintenance Buffer that packet, as well as any other packets in its Maintenance Buffer with the same next-hop destination.
When a node hears such a passive acknowledgement for any packet in its Maintenance Buffer, that node SHOULD remove from its Maintenance Buffer that packet, as well as any other packets in its Maintenance Buffer with the same next-hop destination.
8.3.3. Using Network-Layer Acknowledgements
8.3.3. Using Network-Layer Acknowledgements
When a node originates or forwards a packet and has no other mechanism of acknowledgement available to determine reachability of the next-hop node in the source route for Route Maintenance, that node SHOULD request a network-layer acknowledgement from that next- hop node. To do so, the node inserts an Acknowledgement Request option in the DSR Options header in the packet. The Identification field in that Acknowledgement Request option MUST be set to a value unique over all packets recently transmitted by this node to the same next-hop node.
When a node originates or forwards a packet and has no other mechanism of acknowledgement available to determine reachability of the next-hop node in the source route for Route Maintenance, that node SHOULD request a network-layer acknowledgement from that next- hop node. To do so, the node inserts an Acknowledgement Request option in the DSR Options header in the packet. The Identification field in that Acknowledgement Request option MUST be set to a value unique over all packets recently transmitted by this node to the same next-hop node.
Johnson, et al. Experimental [Page 77] RFC 4728 The Dynamic Source Routing Protocol February 2007
Johnson, et al. Experimental [Page 77] RFC 4728 The Dynamic Source Routing Protocol February 2007
When a node receives a packet containing an Acknowledgement Request option, that node performs the following tests on the packet:
When a node receives a packet containing an Acknowledgement Request option, that node performs the following tests on the packet:
- If the indicated next-hop node address for this packet does not
match any of this node's own IP addresses, then this node MUST NOT
process the Acknowledgement Request option. The indicated next-
hop node address is the next Address[i] field in the DSR Source
Route option in the DSR Options header in the packet, or the IP
Destination Address in the packet if the packet does not contain a
DSR Source Route option or the Segments Left there is zero.
- If the indicated next-hop node address for this packet does not match any of this node's own IP addresses, then this node MUST NOT process the Acknowledgement Request option. The indicated next- hop node address is the next Address[i] field in the DSR Source Route option in the DSR Options header in the packet, or the IP Destination Address in the packet if the packet does not contain a DSR Source Route option or the Segments Left there is zero.
- If the packet contains an Acknowledgement option, then this node
MUST NOT process the Acknowledgement Request option.
- If the packet contains an Acknowledgement option, then this node MUST NOT process the Acknowledgement Request option.
If neither of the tests above fails, then this node MUST process the Acknowledgement Request option by sending an Acknowledgement option to the previous-hop node; to do so, the node performs the following sequence of steps:
If neither of the tests above fails, then this node MUST process the Acknowledgement Request option by sending an Acknowledgement option to the previous-hop node; to do so, the node performs the following sequence of steps:
- Create a packet and set the IP Protocol field to the protocol
number assigned for DSR (48).
- Create a packet and set the IP Protocol field to the protocol number assigned for DSR (48).
- Set the IP Source Address field in this packet to the IP address
of this node, copied from the source route in the DSR Source Route
option in that packet (or from the IP Destination Address field of
the packet, if the packet does not contain a DSR Source Route
option).
- Set the IP Source Address field in this packet to the IP address of this node, copied from the source route in the DSR Source Route option in that packet (or from the IP Destination Address field of the packet, if the packet does not contain a DSR Source Route option).
- Set the IP Destination Address field in this packet to the IP
address of the previous-hop node, copied from the source route in
the DSR Source Route option in that packet (or from the IP Source
Address field of the packet, if the packet does not contain a DSR
Source Route option).
- Set the IP Destination Address field in this packet to the IP address of the previous-hop node, copied from the source route in the DSR Source Route option in that packet (or from the IP Source Address field of the packet, if the packet does not contain a DSR Source Route option).
- Add a DSR Options header to the packet. Set the Next Header field
in the DSR Options header to the value 59, "No Next Header"
[RFC2460].
- Add a DSR Options header to the packet. Set the Next Header field in the DSR Options header to the value 59, "No Next Header" [RFC2460].
- Add an Acknowledgement option to the DSR Options header in the
packet; set the Acknowledgement option's Option Type field to 6
and the Opt Data Len field to 10.
- Add an Acknowledgement option to the DSR Options header in the packet; set the Acknowledgement option's Option Type field to 6 and the Opt Data Len field to 10.
- Copy the Identification field from the received Acknowledgement
Request option into the Identification field in the
Acknowledgement option.
- Copy the Identification field from the received Acknowledgement Request option into the Identification field in the Acknowledgement option.
Johnson, et al. Experimental [Page 78] RFC 4728 The Dynamic Source Routing Protocol February 2007
Johnson, et al. Experimental [Page 78] RFC 4728 The Dynamic Source Routing Protocol February 2007
- Set the ACK Source Address field in the Acknowledgement option to
be the IP Source Address of this new packet (set above to be the
IP address of this node).
- Set the ACK Source Address field in the Acknowledgement option to be the IP Source Address of this new packet (set above to be the IP address of this node).
- Set the ACK Destination Address field in the Acknowledgement
option to be the IP Destination Address of this new packet (set
above to be the IP address of the previous-hop node).
- Set the ACK Destination Address field in the Acknowledgement option to be the IP Destination Address of this new packet (set above to be the IP address of the previous-hop node).
- Send the packet as described in Section 8.1.1.
- Send the packet as described in Section 8.1.1.
Packets containing an Acknowledgement option SHOULD NOT be placed in the Maintenance Buffer.
Packets containing an Acknowledgement option SHOULD NOT be placed in the Maintenance Buffer.
When a node receives a packet with both an Acknowledgement option and an Acknowledgement Request option, if that node is not the destination of the Acknowledgement option (the IP Destination Address of the packet), then the Acknowledgement Request option MUST be ignored. Otherwise (that node is the destination of the Acknowledgement option), that node MUST process the Acknowledgement Request option by returning an Acknowledgement option according to the following sequence of steps:
When a node receives a packet with both an Acknowledgement option and an Acknowledgement Request option, if that node is not the destination of the Acknowledgement option (the IP Destination Address of the packet), then the Acknowledgement Request option MUST be ignored. Otherwise (that node is the destination of the Acknowledgement option), that node MUST process the Acknowledgement Request option by returning an Acknowledgement option according to the following sequence of steps:
- Create a packet and set the IP Protocol field to the protocol
number assigned for DSR (48).
- Create a packet and set the IP Protocol field to the protocol number assigned for DSR (48).
- Set the IP Source Address field in this packet to the IP address
of this node, copied from the source route in the DSR Source Route
option in that packet (or from the IP Destination Address field of
the packet, if the packet does not contain a DSR Source Route
option).
- Set the IP Source Address field in this packet to the IP address of this node, copied from the source route in the DSR Source Route option in that packet (or from the IP Destination Address field of the packet, if the packet does not contain a DSR Source Route option).
- Set the IP Destination Address field in this packet to the IP
address of the node originating the Acknowledgement option.
- Set the IP Destination Address field in this packet to the IP address of the node originating the Acknowledgement option.
- Add a DSR Options header to the packet, and set the DSR Options
header's Next Header field to the value 59, "No Next Header"
[RFC2460].
- Add a DSR Options header to the packet, and set the DSR Options header's Next Header field to the value 59, "No Next Header" [RFC2460].
- Add an Acknowledgement option to the DSR Options header in this
packet; set the Acknowledgement option's Option Type field to 6
and the Opt Data Len field to 10.
- Add an Acknowledgement option to the DSR Options header in this packet; set the Acknowledgement option's Option Type field to 6 and the Opt Data Len field to 10.
- Copy the Identification field from the received Acknowledgement
Request option into the Identification field in the
Acknowledgement option.
- Copy the Identification field from the received Acknowledgement Request option into the Identification field in the Acknowledgement option.
Johnson, et al. Experimental [Page 79] RFC 4728 The Dynamic Source Routing Protocol February 2007
Johnson, et al. Experimental [Page 79] RFC 4728 The Dynamic Source Routing Protocol February 2007
- Set the ACK Source Address field in the option to the IP Source
Address of this new packet (set above to be the IP address of this
node).
- Set the ACK Source Address field in the option to the IP Source Address of this new packet (set above to be the IP address of this node).
- Set the ACK Destination Address field in the option to the IP
Destination Address of this new packet (set above to be the IP
address of the node originating the Acknowledgement option).
- Set the ACK Destination Address field in the option to the IP Destination Address of this new packet (set above to be the IP address of the node originating the Acknowledgement option).
- Send the packet directly to the destination. The IP Destination
Address MUST be treated as a direct neighbor node: the
transmission to that node MUST be done in a single IP forwarding
hop, without Route Discovery and without searching the Route
Cache. In addition, this packet MUST NOT contain a DSR
Acknowledgement Request, MUST NOT be retransmitted for Route
Maintenance, and MUST NOT expect a link-layer acknowledgement or
passive acknowledgement.
- Send the packet directly to the destination. The IP Destination Address MUST be treated as a direct neighbor node: the transmission to that node MUST be done in a single IP forwarding hop, without Route Discovery and without searching the Route Cache. In addition, this packet MUST NOT contain a DSR Acknowledgement Request, MUST NOT be retransmitted for Route Maintenance, and MUST NOT expect a link-layer acknowledgement or passive acknowledgement.
When using network-layer acknowledgements for Route Maintenance, a node SHOULD use an adaptive algorithm in determining the retransmission timeout for each transmission attempt of an acknowledgement request. For example, a node SHOULD maintain a separate round-trip time (RTT) estimate for each node to which it has recently attempted to transmit packets, and it SHOULD use this RTT estimate in setting the timeout for each retransmission attempt for Route Maintenance. The TCP RTT estimation algorithm has been shown to work well for this purpose in implementation and testbed experiments with DSR [MALTZ99b, MALTZ01].
When using network-layer acknowledgements for Route Maintenance, a node SHOULD use an adaptive algorithm in determining the retransmission timeout for each transmission attempt of an acknowledgement request. For example, a node SHOULD maintain a separate round-trip time (RTT) estimate for each node to which it has recently attempted to transmit packets, and it SHOULD use this RTT estimate in setting the timeout for each retransmission attempt for Route Maintenance. The TCP RTT estimation algorithm has been shown to work well for this purpose in implementation and testbed experiments with DSR [MALTZ99b, MALTZ01].
8.3.4. Originating a Route Error
8.3.4. Originating a Route Error
When a node is unable to verify reachability of a next-hop node after reaching a maximum number of retransmission attempts, it SHOULD send a Route Error to the IP Source Address of the packet. When sending a Route Error for a packet containing either a Route Error option or an Acknowledgement option, a node SHOULD add these existing options to its Route Error, subject to the limit described below.
When a node is unable to verify reachability of a next-hop node after reaching a maximum number of retransmission attempts, it SHOULD send a Route Error to the IP Source Address of the packet. When sending a Route Error for a packet containing either a Route Error option or an Acknowledgement option, a node SHOULD add these existing options to its Route Error, subject to the limit described below.
A node transmitting a Route Error MUST perform the following steps:
A node transmitting a Route Error MUST perform the following steps:
- Create an IP packet and set the IP Protocol field to the protocol
number assigned for DSR (48). Set the Source Address field in
this packet's IP header to the address of this node.
- Create an IP packet and set the IP Protocol field to the protocol number assigned for DSR (48). Set the Source Address field in this packet's IP header to the address of this node.
- If the Salvage field in the DSR Source Route option in the packet
triggering the Route Error is zero, then copy the Source Address
field of the packet triggering the Route Error into the
Destination Address field in the new packet's IP header;
- If the Salvage field in the DSR Source Route option in the packet triggering the Route Error is zero, then copy the Source Address field of the packet triggering the Route Error into the Destination Address field in the new packet's IP header;
Johnson, et al. Experimental [Page 80] RFC 4728 The Dynamic Source Routing Protocol February 2007
Johnson, et al. Experimental [Page 80] RFC 4728 The Dynamic Source Routing Protocol February 2007
otherwise, copy the Address[1] field from the DSR Source Route
option of the packet triggering the Route Error into the
Destination Address field in the new packet's IP header
otherwise, copy the Address[1] field from the DSR Source Route option of the packet triggering the Route Error into the Destination Address field in the new packet's IP header
- Insert a DSR Options header into the new packet.
- Insert a DSR Options header into the new packet.
- Add a Route Error Option to the new packet, setting the Error Type
to NODE_UNREACHABLE, the Salvage value to the Salvage value from
the DSR Source Route option of the packet triggering the Route
Error, and the Unreachable Node Address field to the address of
the next-hop node from the original source route. Set the Error
Source Address field to this node's IP address, and the Error
Destination field to the new packet's IP Destination Address.
- Add a Route Error Option to the new packet, setting the Error Type to NODE_UNREACHABLE, the Salvage value to the Salvage value from the DSR Source Route option of the packet triggering the Route Error, and the Unreachable Node Address field to the address of the next-hop node from the original source route. Set the Error Source Address field to this node's IP address, and the Error Destination field to the new packet's IP Destination Address.
- If the packet triggering the Route Error contains any Route Error
or Acknowledgement options, the node MAY append to its Route Error
each of these options, with the following constraints:
- If the packet triggering the Route Error contains any Route Error or Acknowledgement options, the node MAY append to its Route Error each of these options, with the following constraints:
o The node MUST NOT include any Route Error option from the
packet triggering the new Route Error, for which the total
Salvage count (Section 6.4) of that included Route Error would
be greater than MAX_SALVAGE_COUNT in the new packet.
o The node MUST NOT include any Route Error option from the packet triggering the new Route Error, for which the total Salvage count (Section 6.4) of that included Route Error would be greater than MAX_SALVAGE_COUNT in the new packet.
o If any Route Error option from the packet triggering the new
Route Error is not included in the packet, the node MUST NOT
include any following Route Error or Acknowledgement options
from the packet triggering the new Route Error.
o If any Route Error option from the packet triggering the new Route Error is not included in the packet, the node MUST NOT include any following Route Error or Acknowledgement options from the packet triggering the new Route Error.
o Any appended options from the packet triggering the Route Error
MUST follow the new Route Error in the packet.
o Any appended options from the packet triggering the Route Error MUST follow the new Route Error in the packet.
o In appending these options to the new Route Error, the order of
these options from the packet triggering the Route Error MUST
be preserved.
o In appending these options to the new Route Error, the order of these options from the packet triggering the Route Error MUST be preserved.
- Send the packet as described in Section 8.1.1.
- Send the packet as described in Section 8.1.1.
8.3.5. Processing a Received Route Error Option
8.3.5. Processing a Received Route Error Option
When a node receives a packet containing a Route Error option, that node MUST process the Route Error option according to the following sequence of steps:
When a node receives a packet containing a Route Error option, that node MUST process the Route Error option according to the following sequence of steps:
- The node MUST remove from its Route Cache the link from the node
identified by the Error Source Address field to the node
identified by the Unreachable Node Address field (if this link is
present in its Route Cache). If the node implements its Route
Cache as a link cache, as described in Section 4.1, only this
- The node MUST remove from its Route Cache the link from the node identified by the Error Source Address field to the node identified by the Unreachable Node Address field (if this link is present in its Route Cache). If the node implements its Route Cache as a link cache, as described in Section 4.1, only this
Johnson, et al. Experimental [Page 81] RFC 4728 The Dynamic Source Routing Protocol February 2007
Johnson, et al. Experimental [Page 81] RFC 4728 The Dynamic Source Routing Protocol February 2007
single link is removed; if the node implements its Route Cache as
a path cache, however, all routes (paths) that use this link are
either truncated before the link or removed completely.
single link is removed; if the node implements its Route Cache as a path cache, however, all routes (paths) that use this link are either truncated before the link or removed completely.
- If the option following the Route Error is an Acknowledgement or
Route Error option sent by this node (that is, with
Acknowledgement or Error Source Address equal to this node's
address), copy the DSR options following the current Route Error
into a new packet with IP Source Address equal to this node's own
IP address and IP Destination Address equal to the Acknowledgement
or Error Destination Address. Transmit this packet as described
in Section 8.1.1, with the Salvage count in the DSR Source Route
option set to the Salvage value of the Route Error.
- If the option following the Route Error is an Acknowledgement or Route Error option sent by this node (that is, with Acknowledgement or Error Source Address equal to this node's address), copy the DSR options following the current Route Error into a new packet with IP Source Address equal to this node's own IP address and IP Destination Address equal to the Acknowledgement or Error Destination Address. Transmit this packet as described in Section 8.1.1, with the Salvage count in the DSR Source Route option set to the Salvage value of the Route Error.
In addition, after processing the Route Error as described above, the node MAY initiate a new Route Discovery for any destination node for which it then has no route in its Route Cache as a result of processing this Route Error, if the node has indication that a route to that destination is needed. For example, if the node has an open TCP connection to some destination node, then if the processing of this Route Error removed the only route to that destination from this node's Route Cache, then this node MAY initiate a new Route Discovery for that destination node. Any node, however, MUST limit the rate at which it initiates new Route Discoveries for any single destination address, and any new Route Discovery initiated in this way as part of processing this Route Error MUST conform as a part of this limit.
In addition, after processing the Route Error as described above, the node MAY initiate a new Route Discovery for any destination node for which it then has no route in its Route Cache as a result of processing this Route Error, if the node has indication that a route to that destination is needed. For example, if the node has an open TCP connection to some destination node, then if the processing of this Route Error removed the only route to that destination from this node's Route Cache, then this node MAY initiate a new Route Discovery for that destination node. Any node, however, MUST limit the rate at which it initiates new Route Discoveries for any single destination address, and any new Route Discovery initiated in this way as part of processing this Route Error MUST conform as a part of this limit.
8.3.6. Salvaging a Packet
8.3.6. Salvaging a Packet
When an intermediate node forwarding a packet detects through Route Maintenance that the next-hop link along the route for that packet is broken (Section 8.3), if the node has another route to the packet's IP Destination Address in its Route Cache, the node SHOULD "salvage" the packet rather than discard it. To do so using the route found in its Route Cache, this node processes the packet as follows:
When an intermediate node forwarding a packet detects through Route Maintenance that the next-hop link along the route for that packet is broken (Section 8.3), if the node has another route to the packet's IP Destination Address in its Route Cache, the node SHOULD "salvage" the packet rather than discard it. To do so using the route found in its Route Cache, this node processes the packet as follows:
- If the MAC protocol in use in the network is not capable of
transmitting unicast packets over unidirectional links, as
discussed in Section 3.3.1, then if this packet contains a Route
Reply option, remove and discard the Route Reply option in the
packet; if the DSR Options header in the packet then contains no
DSR options or only a DSR Source Route Option, remove the DSR
Options header from the packet. If the resulting packet then
contains only an IP header (e.g., no transport layer header or
payload), the node SHOULD NOT salvage the packet and instead
SHOULD discard the entire packet.
- If the MAC protocol in use in the network is not capable of transmitting unicast packets over unidirectional links, as discussed in Section 3.3.1, then if this packet contains a Route Reply option, remove and discard the Route Reply option in the packet; if the DSR Options header in the packet then contains no DSR options or only a DSR Source Route Option, remove the DSR Options header from the packet. If the resulting packet then contains only an IP header (e.g., no transport layer header or payload), the node SHOULD NOT salvage the packet and instead SHOULD discard the entire packet.
Johnson, et al. Experimental [Page 82] RFC 4728 The Dynamic Source Routing Protocol February 2007
Johnson, et al. Experimental [Page 82] RFC 4728 The Dynamic Source Routing Protocol February 2007
- Modify the existing DSR Source Route option in the packet so that
the Address[i] fields represent the source route found in this
node's Route Cache to this packet's IP Destination Address.
Specifically, the node copies the hop addresses of the source
route into sequential Address[i] fields in the DSR Source Route
option, for i = 1, 2, ..., n. Address[1], here, is the address of
the salvaging node itself (the first address in the source route
found from this node to the IP Destination Address of the packet).
The value n, here, is the number of hop addresses in this source
route, excluding the destination of the packet (which is instead
already represented in the Destination Address field in the
packet's IP header).
- Modify the existing DSR Source Route option in the packet so that the Address[i] fields represent the source route found in this node's Route Cache to this packet's IP Destination Address. Specifically, the node copies the hop addresses of the source route into sequential Address[i] fields in the DSR Source Route option, for i = 1, 2, ..., n. Address[1], here, is the address of the salvaging node itself (the first address in the source route found from this node to the IP Destination Address of the packet). The value n, here, is the number of hop addresses in this source route, excluding the destination of the packet (which is instead already represented in the Destination Address field in the packet's IP header).
- Initialize the Segments Left field in the DSR Source Route option
to n as defined above.
- Initialize the Segments Left field in the DSR Source Route option to n as defined above.
- The First Hop External (F) bit in the DSR Source Route option MUST
be set to 0.
- The First Hop External (F) bit in the DSR Source Route option MUST be set to 0.
- The Last Hop External (L) bit in the DSR Source Route option is
copied from the External bit flagging the last hop in the source
route for the packet, as indicated in the Route Cache.
- The Last Hop External (L) bit in the DSR Source Route option is copied from the External bit flagging the last hop in the source route for the packet, as indicated in the Route Cache.
- The Salvage field in the DSR Source Route option is set to 1 plus
the value of the Salvage field in the DSR Source Route option of
the packet that caused the error.
- The Salvage field in the DSR Source Route option is set to 1 plus the value of the Salvage field in the DSR Source Route option of the packet that caused the error.
- Transmit the packet to the next-hop node on the new source route
in the packet, using the forwarding procedure described in Section
8.1.5.
- Transmit the packet to the next-hop node on the new source route in the packet, using the forwarding procedure described in Section 8.1.5.
As described in Section 8.3.4, the node in this case also SHOULD return a Route Error to the original sender of the packet. If the node chooses to salvage the packet, it SHOULD do so after originating the Route Error.
As described in Section 8.3.4, the node in this case also SHOULD return a Route Error to the original sender of the packet. If the node chooses to salvage the packet, it SHOULD do so after originating the Route Error.
When returning any Route Reply in the case in which the MAC protocol in use in the network is not capable of transmitting unicast packets over unidirectional links, the source route used for routing the Route Reply packet MUST be obtained by reversing the sequence of hops in the Route Request packet (the source route that is then returned in the Route Reply). This restriction on returning a Route Reply and on salvaging a packet that contains a Route Reply option enables the Route Reply to test this sequence of hops for bidirectionality, preventing the Route Reply from being received by the initiator of the Route Discovery unless each of the hops over which the Route Reply is returned (and thus each of the hops in the source route being returned in the Reply) is bidirectional.
When returning any Route Reply in the case in which the MAC protocol in use in the network is not capable of transmitting unicast packets over unidirectional links, the source route used for routing the Route Reply packet MUST be obtained by reversing the sequence of hops in the Route Request packet (the source route that is then returned in the Route Reply). This restriction on returning a Route Reply and on salvaging a packet that contains a Route Reply option enables the Route Reply to test this sequence of hops for bidirectionality, preventing the Route Reply from being received by the initiator of the Route Discovery unless each of the hops over which the Route Reply is returned (and thus each of the hops in the source route being returned in the Reply) is bidirectional.
Johnson, et al. Experimental [Page 83] RFC 4728 The Dynamic Source Routing Protocol February 2007
Johnson, et al. Experimental [Page 83] RFC 4728 The Dynamic Source Routing Protocol February 2007
8.4. Multiple Network Interface Support
8.4. Multiple Network Interface Support
A node using DSR MAY have multiple network interfaces that support DSR ad hoc network routing. This section describes special packet processing at such nodes.
A node using DSR MAY have multiple network interfaces that support DSR ad hoc network routing. This section describes special packet processing at such nodes.
A node with multiple network interfaces that support DSR ad hoc network routing MUST have some policy for determining which Route Request packets are forwarded using which network interfaces. For example, a node MAY choose to forward all Route Requests over all network interfaces.
A node with multiple network interfaces that support DSR ad hoc network routing MUST have some policy for determining which Route Request packets are forwarded using which network interfaces. For example, a node MAY choose to forward all Route Requests over all network interfaces.
When a node with multiple network interfaces that support DSR propagates a Route Request on a network interface other than the one on which it received the Route Request, it MUST in this special case modify the Address list in the Route Request as follows:
When a node with multiple network interfaces that support DSR propagates a Route Request on a network interface other than the one on which it received the Route Request, it MUST in this special case modify the Address list in the Route Request as follows:
- Append the node's IP address for the incoming network interface.
- Append the node's IP address for the incoming network interface.
- Append the node's IP address for the outgoing network interface.
- Append the node's IP address for the outgoing network interface.
When a node forwards a packet containing a source route, it MUST assume that the next-hop node is reachable on the incoming network interface, unless the next hop is the address of one of this node's network interfaces, in which case this node MUST skip over this address in the source route and process the packet in the same way as if it had just received it from that network interface, as described in Section 8.1.5.
When a node forwards a packet containing a source route, it MUST assume that the next-hop node is reachable on the incoming network interface, unless the next hop is the address of one of this node's network interfaces, in which case this node MUST skip over this address in the source route and process the packet in the same way as if it had just received it from that network interface, as described in Section 8.1.5.
If a node that previously had multiple network interfaces that support DSR receives a packet sent with a source route specifying a change to a network interface, as described above, that is no longer available, it MAY send a Route Error to the source of the packet without attempting to forward the packet on the incoming network interface, unless the network uses an autoconfiguration mechanism that may have allowed another node to acquire the now unused address of the unavailable network interface.
If a node that previously had multiple network interfaces that support DSR receives a packet sent with a source route specifying a change to a network interface, as described above, that is no longer available, it MAY send a Route Error to the source of the packet without attempting to forward the packet on the incoming network interface, unless the network uses an autoconfiguration mechanism that may have allowed another node to acquire the now unused address of the unavailable network interface.
8.5. IP Fragmentation and Reassembly
8.5. IP Fragmentation and Reassembly
When a node using DSR wishes to fragment a packet that contains a DSR header not containing a Route Request option, it MUST perform the following sequence of steps:
When a node using DSR wishes to fragment a packet that contains a DSR header not containing a Route Request option, it MUST perform the following sequence of steps:
- Remove the DSR Options header from the packet.
- Remove the DSR Options header from the packet.
Johnson, et al. Experimental [Page 84] RFC 4728 The Dynamic Source Routing Protocol February 2007
Johnson, et al. Experimental [Page 84] RFC 4728 The Dynamic Source Routing Protocol February 2007
- Fragment the packet using normal IP fragmentation processing
[RFC791]. However, when determining the size of each fragment to
create from the original packet, the fragment size MUST be reduced
by the size of the DSR Options header from the original packet.
- Fragment the packet using normal IP fragmentation processing [RFC791]. However, when determining the size of each fragment to create from the original packet, the fragment size MUST be reduced by the size of the DSR Options header from the original packet.
- IP-in-IP encapsulate each fragment [RFC2003]. The IP Destination
address of the outer (encapsulating) packet MUST be set equal to
the IP Destination address of the original packet.
- IP-in-IP encapsulate each fragment [RFC2003]. The IP Destination address of the outer (encapsulating) packet MUST be set equal to the IP Destination address of the original packet.
- Add the DSR Options header from the original packet to each
resulting encapsulating packet. If a Source Route header is
present in the DSR Options header, increment the Salvage field.
- Add the DSR Options header from the original packet to each resulting encapsulating packet. If a Source Route header is present in the DSR Options header, increment the Salvage field.
When a node using the DSR protocol receives an IP-in-IP encapsulated packet destined to itself, it SHOULD decapsulate the packet [RFC2003] and then process the inner packet according to standard IP reassembly processing [RFC791].
When a node using the DSR protocol receives an IP-in-IP encapsulated packet destined to itself, it SHOULD decapsulate the packet [RFC2003] and then process the inner packet according to standard IP reassembly processing [RFC791].
8.6. Flow State Processing
8.6. Flow State Processing
A node implementing the optional DSR flow state extension MUST follow these additional processing steps.
A node implementing the optional DSR flow state extension MUST follow these additional processing steps.
8.6.1. Originating a Packet
8.6.1. Originating a Packet
When originating any packet to be routed using flow state, a node using DSR flow state MUST do the following:
When originating any packet to be routed using flow state, a node using DSR flow state MUST do the following:
- If the route to be used for this packet has never had a DSR flow
state established along it (or the existing flow state has
expired):
- If the route to be used for this packet has never had a DSR flow state established along it (or the existing flow state has expired):
o Generate a 16-bit Flow ID larger than any unexpired Flow IDs
used by this node for this destination. Odd Flow IDs MUST be
chosen for "default" flows; even Flow IDs MUST be chosen for
non-default flows.
o Generate a 16-bit Flow ID larger than any unexpired Flow IDs used by this node for this destination. Odd Flow IDs MUST be chosen for "default" flows; even Flow IDs MUST be chosen for non-default flows.
o Add a DSR Options header, as described in Section 8.1.2.
o Add a DSR Options header, as described in Section 8.1.2.
o Add a DSR Flow State header, as described in Section 8.6.2.
o Add a DSR Flow State header, as described in Section 8.6.2.
o Initialize the Hop Count field in the DSR Flow State header to
0.
o Initialize the Hop Count field in the DSR Flow State header to 0.
o Set the Flow ID field in the DSR Flow State header to the Flow
ID generated in the first step.
o Set the Flow ID field in the DSR Flow State header to the Flow ID generated in the first step.
o Add a Timeout option to the DSR Options header.
o Add a Timeout option to the DSR Options header.
Johnson, et al. Experimental [Page 85] RFC 4728 The Dynamic Source Routing Protocol February 2007
Johnson, et al. Experimental [Page 85] RFC 4728 The Dynamic Source Routing Protocol February 2007
o Add a Source Route option after the Timeout option with the
route to be used, as described in Section 8.1.3.
o Add a Source Route option after the Timeout option with the route to be used, as described in Section 8.1.3.
o The source node SHOULD record this flow in its Flow Table.
o The source node SHOULD record this flow in its Flow Table.
o If this flow is recorded in the Flow Table, the TTL in this
Flow Table entry MUST be set to be the TTL of this flow
establishment packet.
o If this flow is recorded in the Flow Table, the TTL in this Flow Table entry MUST be set to be the TTL of this flow establishment packet.
o If this flow is recorded in the Flow Table, the timeout in this
Flow Table entry MUST be set to a value no less than the value
specified in the Timeout option.
o If this flow is recorded in the Flow Table, the timeout in this Flow Table entry MUST be set to a value no less than the value specified in the Timeout option.
- If the route to be used for this packet has had DSR flow state
established along it, but has not been established end-to-end:
- If the route to be used for this packet has had DSR flow state established along it, but has not been established end-to-end:
o Add a DSR Options header, as described in Section 8.1.2.
o Add a DSR Options header, as described in Section 8.1.2.
o Add a DSR Flow State header, as described in Section 8.6.2.
o Add a DSR Flow State header, as described in Section 8.6.2.
o Initialize the Hop Count field in the DSR Flow State header to
0.
o Initialize the Hop Count field in the DSR Flow State header to 0.
o The Flow ID field of the DSR Flow State header SHOULD be the
Flow ID previously used for this route. If it is not, the
steps for sending packets along never-before-established routes
above MUST be followed in place of these.
o The Flow ID field of the DSR Flow State header SHOULD be the Flow ID previously used for this route. If it is not, the steps for sending packets along never-before-established routes above MUST be followed in place of these.
o Add a Timeout option to the DSR Options header, setting the
Timeout to a value not greater than the timeout remaining for
this flow in the Flow Table.
o Add a Timeout option to the DSR Options header, setting the Timeout to a value not greater than the timeout remaining for this flow in the Flow Table.
o Add a Source Route option after the Timeout option with the
route to be used, as described in Section 8.1.3.
o Add a Source Route option after the Timeout option with the route to be used, as described in Section 8.1.3.
o If the IP TTL is not equal to the TTL specified in the Flow
Table, the source node MUST set a flag to indicate that this
flow cannot be used as default.
o If the IP TTL is not equal to the TTL specified in the Flow Table, the source node MUST set a flag to indicate that this flow cannot be used as default.
- If the route the node wishes to use for this packet has been
established as a flow end-to-end and is not the default flow:
- If the route the node wishes to use for this packet has been established as a flow end-to-end and is not the default flow:
o Add a DSR Flow State header, as described in Section 8.6.2.
o Add a DSR Flow State header, as described in Section 8.6.2.
o Initialize the Hop Count field in the DSR Flow State header to
0.
o Initialize the Hop Count field in the DSR Flow State header to 0.
Johnson, et al. Experimental [Page 86] RFC 4728 The Dynamic Source Routing Protocol February 2007
Johnson, et al. Experimental [Page 86] RFC 4728 The Dynamic Source Routing Protocol February 2007
o The Flow ID field of the DSR Flow State header SHOULD be set to
the Flow ID previously used for this route. If it is not, the
steps for sending packets along never-before-established routes
above MUST be followed in place of these.
o The Flow ID field of the DSR Flow State header SHOULD be set to the Flow ID previously used for this route. If it is not, the steps for sending packets along never-before-established routes above MUST be followed in place of these.
o If the next hop requires a network-layer acknowledgement for
Route Maintenance, add a DSR Options header, as described in
Section 8.1.2, and an Acknowledgement Request option, as
described in Section 8.3.3.
o If the next hop requires a network-layer acknowledgement for Route Maintenance, add a DSR Options header, as described in Section 8.1.2, and an Acknowledgement Request option, as described in Section 8.3.3.
o A DSR Options header SHOULD NOT be added to a packet, unless it
is added to carry an Acknowledgement Request option, in which
case:
o A DSR Options header SHOULD NOT be added to a packet, unless it is added to carry an Acknowledgement Request option, in which case:
+ A Source Route option in the DSR Options header SHOULD NOT
be added.
+ A Source Route option in the DSR Options header SHOULD NOT be added.
+ If a Source Route option in the DSR Options header is added,
the steps for sending packets along flows not yet
established end-to-end MUST be followed in place of these.
+ If a Source Route option in the DSR Options header is added, the steps for sending packets along flows not yet established end-to-end MUST be followed in place of these.
+ A Timeout option SHOULD NOT be added.
+ A Timeout option SHOULD NOT be added.
+ If a Timeout option is added, it MUST specify a timeout not
greater than the timeout remaining for this flow in the Flow
Table.
+ If a Timeout option is added, it MUST specify a timeout not greater than the timeout remaining for this flow in the Flow Table.
- If the route the node wishes to use for this packet has been
established as a flow end-to-end and is the current default flow:
- If the route the node wishes to use for this packet has been established as a flow end-to-end and is the current default flow:
o If the IP TTL is not equal to the TTL specified in the Flow
Table, the source node MUST follow the steps above for sending
a packet along a non-default flow that has been established
end-to-end in place of these steps.
o If the IP TTL is not equal to the TTL specified in the Flow Table, the source node MUST follow the steps above for sending a packet along a non-default flow that has been established end-to-end in place of these steps.
o If the next hop requires a network-layer acknowledgement for
Route Maintenance, the sending node MUST add a DSR Options
header and an Acknowledgement Request option, as described in
Section 8.3.3. The sending node MUST NOT add any additional
options to this header.
o If the next hop requires a network-layer acknowledgement for Route Maintenance, the sending node MUST add a DSR Options header and an Acknowledgement Request option, as described in Section 8.3.3. The sending node MUST NOT add any additional options to this header.
o A DSR Options header SHOULD NOT be added, except as specified
in the previous step. If one is added in a way inconsistent
with the previous step, the source node MUST follow the steps
above for sending a packet along a non-default flow that has
been established end-to-end in place of these steps.
o A DSR Options header SHOULD NOT be added, except as specified in the previous step. If one is added in a way inconsistent with the previous step, the source node MUST follow the steps above for sending a packet along a non-default flow that has been established end-to-end in place of these steps.
Johnson, et al. Experimental [Page 87] RFC 4728 The Dynamic Source Routing Protocol February 2007
Johnson, et al. Experimental [Page 87] RFC 4728 The Dynamic Source Routing Protocol February 2007
8.6.2. Inserting a DSR Flow State Header
8.6.2. Inserting a DSR Flow State Header
A node originating a packet adds a DSR Flow State header to the packet, if necessary, to carry information needed by the routing protocol. A packet MUST NOT contain more than one DSR Flow State header. A DSR Flow State header is added to a packet by performing the following sequence of steps:
A node originating a packet adds a DSR Flow State header to the packet, if necessary, to carry information needed by the routing protocol. A packet MUST NOT contain more than one DSR Flow State header. A DSR Flow State header is added to a packet by performing the following sequence of steps:
- Insert a DSR Flow State header after the IP header and any Hop-
by-Hop Options header that may already be in the packet, but
before any other header that may be present.
- Insert a DSR Flow State header after the IP header and any Hop- by-Hop Options header that may already be in the packet, but before any other header that may be present.
- Set the Next Header field of the DSR Flow State header to the Next
Header field of the previous header (either an IP header or a
Hop-by-Hop Options header).
- 前のヘッダー(IPヘッダーかホップによるHop Optionsヘッダーのどちらか)のNext Header分野にDSR Flow州ヘッダーのNext Header分野を設定してください。
- Set the Flow (F) bit in the DSR Flow State header to 1.
- 1へのDSR Flow州ヘッダーにFlow(F)ビットをはめ込んでください。
- Set the Protocol field of the IP header to the protocol number
assigned for DSR (48).
- DSR(48)のために割り当てられたプロトコル番号にIPヘッダーのプロトコル分野を設定してください。
8.6.3. Receiving a Packet
8.6.3. パケットを受けます。
This section describes processing only for packets that are sent to this processing node as the next-hop node; that is, when the MAC- layer destination address is the MAC address of this node. Otherwise, the process described in Sections 8.6.5 should be followed.
このセクションは、次のホップノードとしてこの処理ノードに送られるパケットのためだけに処理すると説明します。 すなわち、MAC層の送付先アドレスがこのノードのMACアドレスであるときに。 さもなければ、セクション8.6.5で説明されたプロセスは続かれるべきです。
The flow along which a packet is being sent is considered to be in the Flow Table if the triple (IP Source Address, IP Destination Address, Flow ID) has an unexpired entry in this node's Flow Table.
三重(IP Source Address、IP Destination Address、Flow ID)がこのノードのFlow Tableに満期になっていないエントリーを持っているなら、パケットが送られる流れがFlow Tableにあると考えられます。
When a node using DSR flow state receives a packet, it MUST follow the following steps for processing:
DSR流れ状態を使用するノードがパケットを受けるとき、処理のための以下の方法に従わなければなりません:
- If a DSR Flow State header is present, increment the Hop Count
field.
- DSR Flow州ヘッダーが出席しているなら、Hop Count分野を増加してください。
- In addition, if a DSR Flow State header is present, then if the
triple (IP Source Address, IP Destination Address, Flow ID) is in
this node's Automatic Route Shortening Table and the packet is
listed in the entry, then the node MAY send a gratuitous Route
Reply as described in Section 4.4, subject to the rate limiting
specified therein. This gratuitous Route Reply gives the route by
which the packet originally reached this node. Specifically, the
node sending the gratuitous Route Reply constructs the route to
return in the Route Reply as follows:
- さらに、DSR Flow州ヘッダーが出席しているなら、三重(IP Source Address、IP Destination Address、Flow ID)がこのノードのAutomatic Route Shortening Tableにあって、パケットがエントリーに記載されるなら、ノードはセクション4.4でそこに指定されたレート制限を条件として説明されるように無料のRoute Replyを送るかもしれません。 この無料のRoute Replyはパケットが元々このノードに達したルートを与えます。 明確に、無料のRoute Replyを送るノードは以下のRoute Replyで戻るためにルートを構成します:
Johnson, et al. Experimental [Page 88] RFC 4728 The Dynamic Source Routing Protocol February 2007
ジョンソン、他 ダイナミックな実験的な[88ページ]RFC4728のソースルーティング・プロトコル2007年2月
o Let k = (packet Hop Count) - (table Hop Count), where packet
Hop Count is the value of the Hop Count field in this received
packet, and table Hop Count is the Hop Count value stored for
this packet in the corresponding entry in this node's Automatic
Route Shortening Table.
o kを(パケットHop Count)との等しさにしてください--(テーブルHop Count)(パケットHop Countはこの容認されたパケット、およびテーブルHop CountのHop Count分野の値である)はこのノードのAutomatic Route Shortening Tableの対応するエントリーにおけるこのパケットのために保存されたHop Count値です。
o Copy the complete source route for this flow from the
corresponding entry in the node's Flow Table.
o ノードのFlow Tableの対応するエントリーからのこの流れのために完全な送信元経路をコピーしてください。
o Remove from this route the k hops immediately preceding this
node in the route, since these are the hops "skipped over" by
the packet as recorded in the Automatic Route Shortening Table
entry.
o ルートでこのルートからすぐにこのノードに先行するkホップを取り除いてください、これらがAutomatic Route Shortening Tableエントリーにおける記録されるとしてのパケットによって「飛び越えられた」ホップであるので。
- Process each of the DSR options within the DSR Options header in
order:
- DSR Optionsヘッダーの中に整然とした状態でそれぞれのDSRオプションを処理してください:
o On receiving a Pad1 or PadN option, skip over the option.
o Pad1かPadNオプションを受け取ったら、オプションを飛ばしてください。
o On receiving a Route Request for which this node is the
destination, remove the option and return a Route Reply as
specified in Section 8.2.2.
o このノードが目的地であるRoute Requestを受けたら、オプションを取り除いてください、そして、セクション8.2.2における指定されるとしてのRoute Replyを返してください。
o On receiving a broadcast Route Request that this node has not
previously seen for which this node is not the destination,
append this node's incoming interface address to the Route
Request, continue propagating the Route Request as specified in
Section 8.2.2, pass the payload, if any, to the network layer,
and stop processing.
o 目的地ではなく、このノードが以前にこのノードがどれであるかために見ていない放送Route Requestを受けたら、このノードの入って来るインターフェース・アドレスをRoute Requestに追加してください、そして、セクション8.2.2における指定されるとしてのRoute Requestを伝播し続けてください、そして、もしあればペイロードをネットワーク層に渡してください、そして、処理するのを止めてください。
o On receiving a Route Request that this node has previously seen
for which this node is not the destination, discard the packet
and stop processing.
o 目的地ではなく、このノードが以前にこのノードがどれであるかために見たRoute Requestを受けたら、パケットを捨ててください、そして、処理するのを止めてください。
o On receiving any Route Request, add appropriate links to the
Route Cache, as specified in Section 8.2.2.
o どんなRoute Requestも受けたら、セクション8.2.2で指定されるように適切なリンクをRoute Cacheに加えてください。
o On receiving a Route Reply for which this node is the
initiator, remove the Route Reply from the packet and process
it as specified in Section 8.2.6.
o このノードが創始者であるRoute Replyを受けたら、パケットからRoute Replyを取り外してください、そして、セクション8.2.6で指定されるようにそれを処理してください。
o On receiving any Route Reply, add appropriate links to the
Route Cache, as specified in Section 8.2.6.
o どんなRoute Replyも受けたら、セクション8.2.6で指定されるように適切なリンクをRoute Cacheに加えてください。
o On receiving any Route Error of type NODE_UNREACHABLE, remove
appropriate links to the Route Cache, as specified in Section
8.3.5.
o タイプNODE_UNREACHABLEのどんなRoute Errorも受けたら、セクション8.3.5で指定されるようにRoute Cacheへの適切なリンクを取り外してください。
Johnson, et al. Experimental [Page 89] RFC 4728 The Dynamic Source Routing Protocol February 2007
ジョンソン、他 ダイナミックな実験的な[89ページ]RFC4728のソースルーティング・プロトコル2007年2月
o On receiving a Route Error of type NODE_UNREACHABLE that this
node is the Error Destination Address of, remove the Route
Error from the packet and process it as specified in Section
8.3.5. It also MUST stop originating packets along any flows
using the link from Error Source Address to Unreachable Node,
and it MAY remove from its Flow Table any flows using the link
from Error Source Address to Unreachable Node.
o _このノードがUNREACHABLEですが、タイプNODEのRoute Errorを受ける、Error Destination Address、パケットからRoute Errorを取り外してください、そして、セクション8.3で.5に指定されるようにそれを処理してください。 また、Error Source AddressからUnreachable Nodeへのリンクを使用して、それは、どんな流れに沿ってもパケットを溯源するのを止めなければなりません、そして、Error Source AddressからUnreachable Nodeへのリンクを使用して、Flow Tableからどんな流れも取り除くかもしれません。
o On receiving a Route Error of type UNKNOWN_FLOW that this node
is not the Error Destination Address of, the node checks if the
Route Error corresponds to a flow in its Flow Table. If it
does not, the node silently discards the Route Error;
otherwise, it forwards the packet to the expected previous hop
of the corresponding flow. If Route Maintenance cannot confirm
the reachability of the previous hop, the node checks if the
network interface requires bidirectional links for operation.
If it does, the node silently discards the Route Error;
otherwise, it sends the Error as if it were originating it, as
described in Section 8.1.1.
o オンである、Error Destination Addressではなく、このノードがそうであるタイプUNKNOWN_FLOWのa Route Errorを受ける、ノードは、Route ErrorがFlow Tableの流れに対応するかどうかチェックします。 そうしないなら、ノードは静かにRoute Errorを捨てます。 さもなければ、それは対応する流れの前の期待しているホップにパケットを送ります。 Route Maintenanceが前のホップの可到達性を確認できないなら、ノードは、ネットワーク・インターフェースが操作のために双方向のリンクを必要とするかどうかチェックします。 そうするなら、ノードは静かにRoute Errorを捨てます。 さもなければ、それはまるでそれを溯源しているかのようにセクション8.1.1で説明されるようにErrorを送ります。
o On receiving a Route Error of type UNKNOWN_FLOW that this node
is the Error Destination Address of, remove the Route Error
from the packet and mark the flow specified by the triple
(Error Destination Address, Original IP Destination Address,
Flow ID) as not having been established end-to-end.
o _このノードがFLOWですが、タイプUNKNOWNのRoute Errorを受ける、Error Destination Address、パケットからRoute Errorを取り外してください、そして、設立されていないとして三重(誤りDestination Address、Original IP Destination Address、Flow ID)の終わりから終わりまでに指定された流れをマークしてください。
o On receiving a Route Error of type DEFAULT_FLOW_UNKNOWN that
this node is not the Error Destination Address of, the node
checks if the Route Error corresponds to a flow in its Default
Flow Table. If it does not, the node silently discards the
Route Error; otherwise, it forwards the packet to the expected
previous hop of the corresponding flow. If Route Maintenance
cannot confirm the reachability of the previous hop, the node
checks if the network interface requires bidirectional links
for operation. If it does, the node silently discards the
Route Error; otherwise, it sends the Error as if it were
originating it, as described in Section 8.1.1.
o オンである、Error Destination Addressではなく、このノードがそうであるタイプDEFAULT_FLOW_UNKNOWNのa Route Errorを受ける、ノードは、Route ErrorがDefault Flow Tableの流れに対応するかどうかチェックします。 そうしないなら、ノードは静かにRoute Errorを捨てます。 さもなければ、それは対応する流れの前の期待しているホップにパケットを送ります。 Route Maintenanceが前のホップの可到達性を確認できないなら、ノードは、ネットワーク・インターフェースが操作のために双方向のリンクを必要とするかどうかチェックします。 そうするなら、ノードは静かにRoute Errorを捨てます。 さもなければ、それはまるでそれを溯源しているかのようにセクション8.1.1で説明されるようにErrorを送ります。
o On receiving a Route Error of type DEFAULT_FLOW_UNKNOWN that
this node is the Error Destination Address of, remove the Route
Error from the packet and mark the default flow between the
Error Destination Address and the Original IP Destination
Address as not having been established end-to-end.
o _このノードがFLOW_UNKNOWNですが、タイプDEFAULTのRoute Errorを受ける、Error Destination Address、パケットからRoute Errorを取り外してください、そして、設立されていないとしてのError Destination AddressとOriginal IP Destination Addressの間のデフォルト流動が終わるために終わっているとマークしてください。
Johnson, et al. Experimental [Page 90] RFC 4728 The Dynamic Source Routing Protocol February 2007
ジョンソン、他 ダイナミックな実験的な[90ページ]RFC4728のソースルーティング・プロトコル2007年2月
o On receiving an Acknowledgement Request option, the receiving
node removes the Acknowledgement Request option and replies to
the previous hop with an Acknowledgement option. If the
previous hop cannot be determined, the Acknowledgement Request
option is discarded, and processing continues.
o Acknowledgement Requestオプションを受け取ると、受信ノードは、AcknowledgementオプションでAcknowledgement Requestオプションを移して、前のホップに答えます。 前のホップが決定できないなら、Acknowledgement Requestオプションは捨てられます、そして、処理は続きます。
o On receiving an Acknowledgement option, the receiving node
removes the Acknowledgement option and processes it.
o Acknowledgementオプションを受け取ると、受信ノードは、Acknowledgementオプションを取り除いて、それを処理します。
o On receiving any Acknowledgement option, add the appropriate
link to the Route Cache, as specified in Section 8.1.4.
o どんなAcknowledgementオプションも受け取ったら、セクション8.1.4で指定されるように適切なリンクをRoute Cacheに加えてください。
o On receiving any Source Route option, add appropriate links to
the Route Cache, as specified in Section 8.1.4.
o どんなSource Routeオプションも受け取ったら、セクション8.1.4で指定されるように適切なリンクをRoute Cacheに加えてください。
o On receiving a Source Route option, if no DSR Flow State header
is present, if the flow this packet is being sent along is in
the Flow Table, or if no Timeout option preceded the Source
Route option in this DSR Options header, process it as
specified in Section 8.1.4. Stop processing this packet unless
the last address in the Source Route option is an address of
this node.
o どんなDSR Flow州ヘッダーも出席していないならSource Routeオプションを受け取って、このパケットがずっと送られる流れがFlow Tableにあったか、またはどんなTimeoutオプションもこのDSR OptionsヘッダーでSource Routeオプションに先行しなかったなら、セクション8.1.4で指定されるようにそれを処理してください。 Source Routeオプションにおける最後のアドレスがこのノードのアドレスでないならこのパケットを処理するのを止めてください。
o On receiving a Source Route option in a packet with a DSR Flow
State header, if the Flow ID specified in the DSR Flow State
header is not in the Flow Table, add the flow to the Flow
Table, setting the Timeout value to a value not greater than
the Timeout field of the Timeout option in this header. If no
Timeout option preceded the Source Route option in this header,
the flow MUST NOT be added to the Flow Table.
o DSR Flow州ヘッダーで指定されたFlow IDがFlow TableにないならDSR Flow州ヘッダーと共にパケットにSource Routeオプションを受け取ったら、Flow Tableに流れを加えてください、このヘッダーでは、TimeoutオプションのTimeout分野ほど大きくない値にTimeout値を設定して。 どんなTimeoutオプションもこのヘッダーでSource Routeオプションに先行しなかったなら、Flow Tableに流れを加えてはいけません。
If the Flow ID is odd and larger than any unexpired, odd Flow
IDs for this (IP Source Address, IP Destination Address), it is
set to be default in the Default Flow ID Table.
これには、Flow IDがどんな満期になっていなくて、変なFlow IDよりも変であって、大きい、(IP Source Address、IP Destination Address)、それはDefault Flow ID Tableのデフォルトであるように設定されます。
Then process the Route option as specified in Section 8.1.4.
Stop processing this packet unless the last address in the
Source Route option is an address of this node.
そして、セクション8.1.4における指定されるとしてのRouteオプションを処理してください。 Source Routeオプションにおける最後のアドレスがこのノードのアドレスでないならこのパケットを処理するのを止めてください。
o On receiving a Timeout option, check if this packet contains a
DSR Flow State header. If this packet does not contain a DSR
Flow State header, discard the DSR option. Otherwise, record
the Timeout value in the option for future reference. The
value recorded SHOULD be discarded when the node has finished
processing this DSR Options header. If the flow that this
packet is being sent along is in the Flow Table, it MAY set the
flow to time out no more than Timeout seconds in the future.
o Timeoutオプションを受け取ったら、このパケットがDSR Flow州ヘッダーを含むかどうかチェックしてください。 このパケットがDSR Flow州ヘッダーを含まないなら、DSRオプションを捨ててください。 さもなければ、後日のためにTimeout値をオプションに記録してください。 ノードが、このDSR Optionsヘッダーを処理し終えたとき、捨てられて、値はSHOULDを記録しました。 このパケットがずっと送られる流れがFlow Tableにあるなら、それは将来、Timeout秒ほどタイムアウトに流れを設定しないかもしれません。
Johnson, et al. Experimental [Page 91] RFC 4728 The Dynamic Source Routing Protocol February 2007
ジョンソン、他 ダイナミックな実験的な[91ページ]RFC4728のソースルーティング・プロトコル2007年2月
o On receiving a Destination and Flow ID option, if the IP
Destination Address is not an address of this node, forward the
packet according to the Flow ID, as described in Section 8.6.4,
and stop processing this packet.
o IP Destination AddressがこのノードのアドレスでないならDestinationとFlow IDオプションを受け取ったら、Flow IDに応じて、セクション8.6.4で説明されるようにパケットを進めてください、そして、このパケットを処理するのを止めてください。
o On receiving a Destination and Flow ID option, if the IP
Destination Address is an address of this node, set the IP
Destination Address to the New IP Destination Address specified
in the option and set the Flow ID to the New Flow Identifier.
Then remove the Destination and Flow ID option from the packet
and continue processing.
o IP Destination AddressがこのノードのアドレスであるならDestinationとFlow IDオプションを受け取ったら、オプションで指定されたNew IP Destination AddressにIP Destination Addressを設定してください、そして、Flow IDをNew Flow Identifierに設定してください。 次に、パケットからDestinationとFlow IDオプションを取り外してください、そして、処理し続けてください。
- If the IP Destination Address is an address of this node, remove
the DSR Options header, if any, pass the packet up the network
stack, and stop processing.
- IP Destination Addressがこのノードのアドレスであるなら、DSR Optionsヘッダーを取り除いてください、もしあればネットワークスタックでパケットを通過してください、そして、処理するのを止めてください。
- If there is still a DSR Options header containing no options,
remove the DSR Options header.
- オプションを全く含まないDSR Optionsヘッダーがまだあれば、DSR Optionsヘッダーを取り除いてください。
- If there is still a DSR Flow State header, forward the packet
according to the Flow ID, as described in Section 8.6.4.
- DSR Flow州ヘッダーがまだあれば、Flow IDに応じて、パケットを進めてください、セクション8.6.4で説明されるように。
- If there is neither a DSR Options header nor a DSR Flow State
header, but there is an entry in the Default Flow Table for the
(IP Source Address, IP Destination Address) pair:
- DSR OptionsヘッダーもDSR Flow州ヘッダーもありませんが、エントリーが(IP Source Address、IP Destination Address)組Default Flow Tableにあれば:
o If the IP TTL is not equal to the TTL expected in the Flow
Table, insert a DSR Flow State header, setting the Hop Count
equal to the Hop Count of this node, and the Flow ID equal to
the default Flow ID found in the Default Flow Table, and
forward this packet according to the Flow ID, as described in
Section 8.6.4.
o IP TTLがFlow Tableで予想されたTTLと等しくないなら、DSR Flow州ヘッダーを挿入してください、このノードのHop Countと等しいHop Count、およびFlow IDによると、Flow IDがDefault Flow Tableに、前方にこのパケットを見つけたデフォルトと等しいFlow IDを設定して、セクション8.6.4で説明されるように。
o Otherwise, follow the steps for forwarding the packet using
Flow IDs described in Section 8.6.4, but taking the Flow ID to
be the default Flow ID found in the Default Flow Table.
o さもなければ、セクション8.6.4で説明されますが、Flow IDがDefault Flow Tableで見つけたデフォルトになるようにFlow IDを占領しながらFlow IDを使用することでパケットを進めるための方法に従ってください。
- If there is no DSR Options header and no DSR Flow State header and
no default flow can be found, the node returns a Route Error of
type DEFAULT_FLOW_UNKNOWN to the IP Source Address, specifying the
IP Destination Address as the Original IP Destination in the
type-specific field.
- DSR OptionsヘッダーがなくてDSR Flow州ヘッダーが全くなくて、デフォルト流動を全く見つけることができないなら、ノードはタイプDEFAULT_FLOW_UNKNOWNのRoute ErrorをIP Source Addressに返します、Original IP Destinationとしてタイプ特有の分野でIP Destination Addressを指定して。
Johnson, et al. Experimental [Page 92] RFC 4728 The Dynamic Source Routing Protocol February 2007
ジョンソン、他 ダイナミックな実験的な[92ページ]RFC4728のソースルーティング・プロトコル2007年2月
8.6.4. Forwarding a Packet Using Flow IDs
8.6.4. 流れIDを使用することでパケットを進めます。
To forward a packet using Flow IDs, a node MUST follow the following sequence of steps:
Flow IDを使用することでパケットを進めるために、ノードは以下のステップの以下の順序に従わなければなりません:
- If the triple (IP Source Address, IP Destination Address, Flow ID)
is not in the Flow Table, return a Route Error of type
UNKNOWN_FLOW.
- 三重(IP Source Address、IP Destination Address、Flow ID)がFlow Tableにないなら、タイプUNKNOWN_FLOWのRoute Errorを返してください。
- If a network-layer acknowledgement is required for Route
Maintenance for the next hop, the node MUST include an
Acknowledgement Request option as specified in Section 8.3.3. If
no DSR Options header is in the packet in which the
Acknowledgement Request option is to be added, it MUST be
included, as described in Section 8.1.2, except that it MUST be
added after the DSR Flow State header, if one is present.
- ネットワーク層承認が次のホップのためのRoute Maintenanceに必要であるなら、ノードはセクション8.3.3における指定されるとしてのAcknowledgement Requestオプションを含まなければなりません。 DSR Optionsヘッダーが全く加えられるAcknowledgement Requestオプションがことであるパケットにないなら、それを含まなければなりません、セクション8.1.2で説明されるように、DSR Flow州ヘッダーの後にそれを加えなければならないのを除いて、1つが存在しているなら。
- Attempt to transmit this packet to the next hop as specified in
the Flow Table, performing Route Maintenance to detect broken
routes.
- Flow Tableで指定されているとしてこのパケットを次のホップに伝えるのを試みてください、壊れているルートを検出するためにRoute Maintenanceを実行して。
8.6.5. Promiscuously Receiving a Packet
8.6.5. 乱雑に、パケットを受けます。
This section describes processing only for packets that have MAC destinations other than this processing node. Otherwise, the process described in Section 8.6.3 should be followed.
このセクションは、この処理ノード以外のMACの目的地を持っているパケットのためだけに処理すると説明します。 さもなければ、セクション8.6.3で説明されたプロセスは続かれるべきです。
When a node using DSR flow state promiscuously overhears a packet, it SHOULD follow the following steps for processing:
ノードであるときに、乱雑にDSR流れ状態を使用すると、パケットは立ち聞きされて、それは以下が処理のために踏むSHOULD尾行です:
- If the packet contains a DSR Flow State header, and if the triple
(IP Source Address, IP Destination Address, Flow ID) is in the
Flow Table and the Hop Count is less than the Hop Count in the
flow's entry, the node MAY retain the packet in the Automatic
Route Shortening Table. If it can be determined that this Flow ID
has been recently used, the node SHOULD retain the packet in the
Automatic Route Shortening Table.
- パケットがDSR Flow州ヘッダーを含んでいて、三重(IP Source Address、IP Destination Address、Flow ID)がFlow Tableにあって、Hop Countが流れのエントリーにおけるHop Count以下であるなら、ノードはAutomatic Route Shortening Tableでパケットを保有するかもしれません。 このFlow IDが最近使用されたことを決定できるなら、ノードSHOULDはAutomatic Route Shortening Tableでパケットを保有します。
- If the packet contains neither a DSR Flow State header nor a
Source Route option and a Default Flow ID can be found in the
Default Flow Table for the (IP Source Address, IP Destination
Address), and if the IP TTL is greater than the TTL in the Flow
Table for the default flow, the node MAY retain the packet in the
Automatic Route Shortening Table. If it can be determined that
this Flow ID has been used recently, the node SHOULD retain the
packet in the Automatic Route Shortening Table.
- パケットがどちらもDSR Flow州ヘッダーかSource RouteオプションとDefault Flow TableでIDを見つけることができるa Default Flowを含んでいる、(IP Source Address、IP Destination Address)、Flow Tableでは、IP TTLがTTLよりデフォルト流動が大きいなら、ノードはAutomatic Route Shortening Tableでパケットを保有するかもしれません。 このFlow IDが最近使用されたことを決定できるなら、ノードSHOULDはAutomatic Route Shortening Tableでパケットを保有します。
Johnson, et al. Experimental [Page 93] RFC 4728 The Dynamic Source Routing Protocol February 2007
ジョンソン、他 ダイナミックな実験的な[93ページ]RFC4728のソースルーティング・プロトコル2007年2月
8.6.6. Operation Where the Layer below DSR Decreases the IP TTL
Non-uniformly
8.6.6. DSRの下の層がIP TTLを非一様に減少させる操作
Some nodes may use an IP tunnel as a DSR hop. If different packets sent along this IP tunnel can take different routes, the reduction in IP TTL across this link may be different for different packets. This prevents the Automatic Route Shortening and Loop Detection functionality from working properly when used in conjunction with default routes.
いくつかのノードがDSRホップとしてIPトンネルを使用するかもしれません。 このIPトンネルに沿って送られた異なったパケットが異なったルートを取ることができるなら、異なったパケットにおいて、このリンクの向こう側のIP TTLでの減少は異なっているかもしれません。 これは、デフォルトルートに関連して使用されるとAutomatic Route ShorteningとLoop Detectionの機能性が適切に働くのを防ぎます。
Nodes forwarding packets without a Source Route option onto a link with unpredictable TTL changes MUST ensure that a DSR Flow State header is present, indicating the correct Hop Count and Flow ID.
Source Routeオプションなしで予測できないTTL変化とのリンクにパケットを送るノードは、DSR Flow州ヘッダーに出席しているのを確実にしなければなりません、正しいHop CountとFlow IDを示して。
8.6.7. Salvage Interactions with DSR
8.6.7. DSRとの海難救助相互作用
Nodes salvaging packets MUST remove the DSR Flow State header, if present.
存在しているなら、パケットを回収するノードはDSR Flow州ヘッダーを取り除かなければなりません。
Anytime this document refers to the Salvage field in the Source Route option, packets without a Source Route option are considered to have the value zero in the Salvage field.
いつでも、このドキュメントはSource RouteオプションにおけるSalvage野原を呼んで、Source RouteオプションのないパケットがSalvage分野に値ゼロを持っていると考えられます。
Johnson, et al. Experimental [Page 94] RFC 4728 The Dynamic Source Routing Protocol February 2007
ジョンソン、他 ダイナミックな実験的な[94ページ]RFC4728のソースルーティング・プロトコル2007年2月
9. Protocol Constants and Configuration Variables
9. プロトコル定数と構成変数
Any DSR implementation MUST support the following configuration variables and MUST support a mechanism enabling the value of these variables to be modified by system management. The specific variable names are used for demonstration purposes only, and an implementation is not required to use these names for the configuration variables, so long as the external behavior of the implementation is consistent with that described in this document.
どんなDSR実装も、以下の構成が変数であることをサポートしなければならなくて、これらの変数の値がシステム管理で変更されるのを可能にするメカニズムをサポートしなければなりません。 特定の変数名はデモンストレーションの目的だけに使用されます、そして、実装は構成変数にこれらの名前を使用するのに必要ではありません、実装の外部の振舞いが本書では説明されるそれと一致している限り。
For each configuration variable below, the default value is specified to simplify configuration. In particular, the default values given below are chosen for a DSR network running over 2 Mbps IEEE 802.11 network interfaces using the Distributed Coordination Function (DCF) MAC protocol with RTS and CTS [IEEE80211, BROCH98].
以下のそれぞれの構成変数として、デフォルト値は、構成を簡素化するために指定されます。 特に、以下に与えられたデフォルト値はRTSとCTS[IEEE80211、BROCH98]とのDistributed Coordination Function(DCF)MACプロトコルを使用することで2以上Mbps IEEE802.11ネットワーク・インターフェースを実行するDSRネットワークに選ばれています。
DiscoveryHopLimit 255 hops
DiscoveryHopLimit255ホップ
BroadcastJitter 10 milliseconds
BroadcastJitter10ミリセカンド
RouteCacheTimeout 300 seconds
300秒のRouteCacheTimeout
SendBufferTimeout 30 seconds
30秒のSendBufferTimeout
RequestTableSize 64 nodes
RequestTableIds 16 identifiers
MaxRequestRexmt 16 retransmissions
MaxRequestPeriod 10 seconds
RequestPeriod 500 milliseconds
NonpropRequestTimeout 30 milliseconds
500ミリセカンドのRequestTableSize64ノードRequestTableIds16識別子MaxRequestRexmt16retransmissions MaxRequestPeriod10秒RequestPeriod NonpropRequestTimeout30ミリセカンド
RexmtBufferSize 50 packets
RexmtBufferSize50パケット
MaintHoldoffTime 250 milliseconds
MaintHoldoffTime250ミリセカンド
MaxMaintRexmt 2 retransmissions
MaxMaintRexmt2「再-トランスミッション」
TryPassiveAcks 1 attempt
PassiveAckTimeout 100 milliseconds
TryPassiveAcks1はPassiveAckTimeoutを100ミリセカンドと同じくらい試みます。
GratReplyHoldoff 1 second
GratReplyHoldoff1 2番目
In addition, the following protocol constant MUST be supported by any implementation of the DSR protocol:
さらに、DSRプロトコルのどんな実装でも以下のプロトコル定数をサポートしなければなりません:
MAX_SALVAGE_COUNT 15 salvages
COUNT15が回収するマックス_SALVAGE_
Johnson, et al. Experimental [Page 95] RFC 4728 The Dynamic Source Routing Protocol February 2007
ジョンソン、他 ダイナミックな実験的な[95ページ]RFC4728のソースルーティング・プロトコル2007年2月
10. IANA Considerations
10. IANA問題
This document specifies the DSR Options header and DSR Flow State header, for which the IP protocol number 48 has been assigned. A single IP protocol number can be used for both header types, since they can be distinguished by the Flow State Header (F) bit in each header.
このドキュメントはDSR OptionsヘッダーとDSR Flow州ヘッダーを指定します。(ヘッダーに関してIPプロトコル番号48を割り当ててあります)。 両方のヘッダータイプにただ一つのIPプロトコル番号を使用できます、各ヘッダーでFlow州Header(F)ビットで彼らを区別できるので。
In addition, this document proposes use of the value "No Next Header" (originally defined for use in IPv6 [RFC2460]) within an IPv4 packet, to indicate that no further header follows a DSR Options header.
さらに、このドキュメントは、どんな一層のヘッダーもDSR Optionsヘッダーについて来ないのを示すためにIPv4パケットの中で値「いいえ、次のヘッダー」(元々、IPv6[RFC2460]における使用のために定義される)の使用を提案します。
Finally, this document introduces a number of DSR options for use in the DSR Options header, and additional new DSR options may be defined in the future. Each of these options requires a unique Option Type value, the most significant 3 bits (that is, Option Type & 0xE0) encoded as defined in Section 6.1. It is necessary only that each Option Type value be unique, not that they be unique in the remaining 5 bits of the value after these 3 most significant bits.
最終的に、このドキュメントはDSR Optionsヘッダーにおける使用のための多くのDSRオプションを紹介します、そして、追加新しいDSRオプションは将来、定義されるかもしれません。 それぞれのこれらのオプションはユニークなOption Type値、セクション6.1で定義されるようにコード化される中で最も重要な3ビット(すなわち、Option Type&0xE0)を必要とします。 それぞれのOption Type値がユニークであるだけであることが必要であり、彼らはこれらの3つの最上位ビットの後に価値の残っている5ビットでユニークであるというわけではありません。
Two registries (DSR Protocol Options and DSR Protocol Route Error Types) have been created and contain the initial registrations. Assignment of new values for DSR options will be by Expert Review [RFC2434], with the authors of this document serving as the Designated Experts.
2つの登録(DSRプロトコルOptionsとDSRプロトコルRoute Error Types)が、作成されて、初期の登録証明書を含んでいます。 Expert Review[RFC2434]でDSRオプションのための新しい値の課題があるでしょう、このドキュメントの作者がDesignated Expertsとして勤めていて。
11. Security Considerations
11. セキュリティ問題
This document does not specifically address security concerns. This document does assume that all nodes participating in the DSR protocol do so in good faith and without malicious intent to corrupt the routing ability of the network.
このドキュメントは、セキュリティが関心であると明確に扱いません。 このドキュメントは、DSRプロトコルに参加するすべてのノードが誠実とネットワークのルーティング能力を崩壊させる悪意がある意図なしでそうすると仮定します。
Depending on the threat model, a number of different mechanisms can be used to secure DSR. For example, in an environment where node compromise is unrealistic and where all the nodes participating in the DSR protocol share a common goal that motivates their participation in the protocol, the communications between the nodes can be encrypted at the physical channel or link layer to prevent attack by outsiders. Cryptographic approaches, such as that provided by Ariadne [HU02] or Secure Routing Protocol (SRP) [PAPADIMITRATOS02], can resist stronger attacks.
脅威モデルに頼っていて、DSRを固定するのに多くの異なったメカニズムを使用できます。 例えば、ノード感染が非現実的であり、DSRプロトコルに参加するすべてのノードがプロトコルへの彼らの参加を動機づける一般的な目標を共有する環境で、部外者による攻撃を防ぐために物理的なチャンネルかリンクレイヤにノードのコミュニケーションを暗号化できます。 アリアドネによって提供されたそれなどの暗号のアプローチ[HU02]かSecureルート設定プロトコル(SRP)[PAPADIMITRATOS02]が、より強い攻撃に抵抗できます。
Johnson, et al. Experimental [Page 96] RFC 4728 The Dynamic Source Routing Protocol February 2007
ジョンソン、他 ダイナミックな実験的な[96ページ]RFC4728のソースルーティング・プロトコル2007年2月
Appendix A. Link-MaxLife Cache Description
付録A.リンク-MaxLifeキャッシュ記述
As guidance to implementers of DSR, the description below outlines the operation of a possible implementation of a Route Cache for DSR that has been shown to outperform other caches studied in detailed simulations. Use of this design for the Route Cache is recommended in implementations of DSR.
DSRのimplementersへの指導、以下での記述がDSRのためにRoute Cacheの可能な実装の操作について概説するとき、それは、詳細なシミュレーションで研究された他のキャッシュより優れるように示されました。 このデザインのRoute Cacheの使用はDSRの実装でお勧めです。
This cache, called "Link-MaxLife" [HU00], is a link cache, in that each individual link (hop) in the routes returned in Route Reply packets (or otherwise learned from the header of overhead packets) is added to a unified graph data structure of this node's current view of the network topology, as described in Section 4.1. To search for a route in this cache to some destination node, the sending node uses a graph search algorithm, such as the well-known Dijkstra's shortest-path algorithm, to find the current best path through the graph to the destination node.
「リンク-MaxLife」[HU00]と呼ばれるこのキャッシュはリンクキャッシュです、Route Replyパケット(または、別の方法で頭上のパケットのヘッダーから学習される)で返されたルートによるそれぞれの個々のリンク(ホップ)がこのノードのネットワーク形態の現在の視点の統一されたグラフデータ構造に追加されるので、セクション4.1で説明されるように。 このキャッシュで何らかの目的地ノードにルートを捜し求めるなら、送付ノードは、グラフで現在の最も良い経路を目的地ノードに見つけるのによく知られるダイクストラの最短パスアルゴリズムなどのグラフ検索アルゴリズムを使用します。
The Link-MaxLife form of link cache is adaptive in that each link in the cache has a timeout that is determined dynamically by the caching node according to its observed past behavior of the two nodes at the ends of the link; in addition, when selecting a route for a packet being sent to some destination, among cached routes of equal length (number of hops) to that destination, Link-MaxLife selects the route with the longest expected lifetime (highest minimum timeout of any link in the route).
2つのノードの観測された過去の動きに従ってキャッシュにおける各リンクがリンクの端にキャッシュノードでダイナミックに断固としたタイムアウトを持っているので、リンクキャッシュのLink-MaxLifeフォームは適応型です。 いくつかの目的地に送られるパケットのためにルートを選択するとき、さらに、その目的地への等しい長さ(ホップの数)のキャッシュされたルートの中では、Link-MaxLifeは最も長い予想された生涯(どんなリンクのルートで最も高い最小のタイムアウトも)があるルートを選択します。
Specifically, in Link-MaxLife, a link's timeout in the Route Cache is chosen according to a "Stability Table" maintained by the caching node. Each entry in a node's Stability Table records the address of another node and a factor representing the perceived "stability" of this node. The stability of each other node in a node's Stability Table is initialized to InitStability. When a link from the Route Cache is used in routing a packet originated or salvaged by that node, the stability metric for each of the two endpoint nodes of that link is incremented by the amount of time since that link was last used, multiplied by StabilityIncrFactor (StabilityIncrFactor >= 1); when a link is observed to break and the link is thus removed from the Route Cache, the stability metric for each of the two endpoint nodes of that link is multiplied by StabilityDecrFactor (StabilityDecrFactor < 1).
明確に、キャッシュノードによって維持された「安定性テーブル」に従って、Link-MaxLifeでは、Route Cacheのリンクのタイムアウトは選ばれています。 ノードのStability Tableの各エントリーはこのノードの知覚された「安定性」を表す別のノードと要素のアドレスを記録します。 安定性、互いでは、ノードのStability TableのノードはInitStabilityに初期化されます。 Route Cacheからのリンクがパケットが溯源したルーティングで使用されるか、またはそのノードによって救助されるとき、それぞれのそのリンクの2つの終点ノードにおける、メートル法の安定性はそのリンクがStabilityIncrFactor(StabilityIncrFactor>=1)によって中古の、そして、掛けられた最終であった時から時間までに増加されます。 リンクが壊れると認められて、リンクがRoute Cacheからこのようにして取り外されるとき、StabilityDecrFactor(StabilityDecrFactor<1)はそれぞれのそのリンクの2つの終点ノードにおける、メートル法の安定性に掛けられます。
When a node adds a new link to its Route Cache, the node assigns a lifetime for that link in the Cache equal to the stability of the less "stable" of the two endpoint nodes for the link, except that a link is not allowed to be given a lifetime less than MinLifetime. When a link is used in a route chosen for a packet originated or salvaged by this node, the link's lifetime is set to be at least
ノードが新しいリンクをRoute Cacheに加えるとき、ノードはそれほどリンクのための2つの終点ノードの「安定でない」安定性と等しいCacheのそのリンクに生涯を割り当てます、リンクがMinLifetimeほど生涯を与えないことができないのを除いて。 リンクがこのノードによって溯源されるか、または回収されたパケットに選ばれたルートで使用されるとき、リンクの寿命は少なくともである決められます。
Johnson, et al. Experimental [Page 97] RFC 4728 The Dynamic Source Routing Protocol February 2007
ジョンソン、他 ダイナミックな実験的な[97ページ]RFC4728のソースルーティング・プロトコル2007年2月
UseExtends into the future; if the lifetime of that link in the Route Cache is already further into the future, the lifetime remains unchanged.
未来までのUseExtends。 さらに未来までRoute Cacheのそのリンクの寿命が既にあるなら、寿命は変わりがありません。
When a node using Link-MaxLife selects a route from its Route Cache for a packet being originated or salvaged by this node, it selects the shortest-length route that has the longest expected lifetime (highest minimum timeout of any link in the route), as opposed to simply selecting an arbitrary route of shortest length.
Link-MaxLifeを使用するノードがこのノードによって溯源されるか、または回収されるパケットのためにRoute Cacheからルートを選択するとき、最も長い予想された生涯(どんなリンクのルートで最も高い最小のタイムアウトも)を持っている最も短い長さのルートを選択します、単に最も短い長さの任意のルートを選択することと対照的に。
The following configuration variables are used in the description of Link-MaxLife above. The specific variable names are used for demonstration purposes only, and an implementation is not required to use these names for these configuration variables. For each configuration variable below, the default value is specified to simplify configuration. In particular, the default values given below are chosen for a DSR network where nodes move at relative velocities between 12 and 25 seconds per wireless transmission radius.
以下の構成変数はLink-MaxLifeの上の記述に使用されます。 特定の変数名はデモンストレーションの目的だけに使用されます、そして、実装は、これらの構成変数にこれらの名前を使用するのに必要ではありません。 以下のそれぞれの構成変数として、デフォルト値は、構成を簡素化するために指定されます。 ノードが相対的な速度で放送半径あたり12〜25秒移行するところで特に、以下に与えられたデフォルト値はDSRネットワークに選ばれています。
InitStability 25 seconds
StabilityIncrFactor 4
StabilityDecrFactor 0.5
InitStability25秒StabilityIncrFactor4StabilityDecrFactor0.5
MinLifetime 1 second
UseExtends 120 seconds
120秒のMinLifetime1第2UseExtends
Johnson, et al. Experimental [Page 98] RFC 4728 The Dynamic Source Routing Protocol February 2007
ジョンソン、他 ダイナミックな実験的な[98ページ]RFC4728のソースルーティング・プロトコル2007年2月
Appendix B. Location of DSR in the ISO Network Reference Model
ISOネットワーク規範モデルのDSRの付録B.位置
When designing DSR, we had to determine at what layer within the protocol hierarchy to implement ad hoc network routing. We considered two different options: routing at the link layer (ISO layer 2) and routing at the network layer (ISO layer 3). Originally, we opted to route at the link layer for several reasons:
DSRを設計するとき、私たちは、プロトコル階層の中のどんな層で臨時のネットワークルーティングを実装すると決心しなければならなかったか。 私たちは2つの異なったオプションを考えました: リンクで掘って、ネットワーク層(ISO層3)で(ISO層2)とルーティングを層にしてください。 元々、私たちはいくつかの理由でリンクレイヤのルートに選びました:
- Pragmatically, running the DSR protocol at the link layer
maximizes the number of mobile nodes that can participate in ad
hoc networks. For example, the protocol can route equally well
between IPv4 [RFC791], IPv6 [RFC2460], and IPX [TURNER90] nodes.
- DSRプロトコルをリンクレイヤに実行すると、実践的に、臨時のネットワークに参加できるモバイルノードの数は最大化します。 例えば、プロトコルは等しくIPv4[RFC791]、IPv6[RFC2460]、およびIPX[TURNER90]ノードの間に井戸を発送できます。
- Historically [JOHNSON94, JOHNSON96a], DSR grew from our
contemplation of a multi-hop propagating version of the Internet's
Address Resolution Protocol (ARP) [RFC826], as well as from the
routing mechanism used in IEEE 802 source routing bridges
[PERLMAN92]. These are layer 2 protocols.
- 歴史的[JOHNSON94、JOHNSON96a]に、DSRは私たちのインターネットのAddress Resolutionプロトコル(ARP)[RFC826]のマルチホップ伝播バージョンの熟考から成長しました、よくIEEE802ソースルーティングブリッジ[PERLMAN92]で使用されるルーティングメカニズムのように。 これらは層2のプロトコルです。
- Technically, we designed DSR to be simple enough that it could be
implemented directly in the firmware inside wireless network
interface cards [JOHNSON94, JOHNSON96a], well below the layer 3
software within a mobile node. We see great potential in this for
DSR running inside a cloud of mobile nodes around a fixed base
station, where DSR would act to transparently extend the coverage
range to these nodes. Mobile nodes that would otherwise be unable
to communicate with the base station due to factors such as
distance, fading, or local interference sources could then reach
the base station through their peers.
- 技術的に、私たちは、モバイルノードの中で直接ワイヤレスのネットワーク・インターフェース・カード[JOHNSON94、JOHNSON96a]の中のファームウェアでそれを実装することができて、層の下の井戸が3ソフトウェアである簡単になるようにDSRを設計しました。 私たちは、DSRのためのこれの素晴らしい潜在能力がモバイルノードの雲の中で固定基地局の周りに稼働しているのを見ます。そこでは、DSRが、透過的に適用範囲の範囲をこれらのノードに広げるために行動するでしょう。 そして、そうでなければ距離、色あせ、またはローカルの干渉ソースなどの要素のためベースステーションとコミュニケートできないモバイルノードは彼らの同輩を通して基地局に達するかもしれません。
Ultimately, however, we decided to specify and to implement [MALTZ99b] DSR as a layer 3 protocol, since this is the only layer at which we could realistically support nodes with multiple network interfaces of different types forming an ad hoc network.
しかしながら、結局、私たちは、指定して、層3が議定書を作るとき[MALTZ99b]DSRを実装すると決めました、これが私たちが現実的に異なったタイプの複数のネットワーク・インターフェースが臨時のネットワークを形成しているノードをサポートできた唯一の層であるので。
Johnson, et al. Experimental [Page 99] RFC 4728 The Dynamic Source Routing Protocol February 2007
ジョンソン、他 ダイナミックな実験的な[99ページ]RFC4728のソースルーティング・プロトコル2007年2月
Appendix C. Implementation and Evaluation Status
付録C.実装と評価状態
The initial design of the DSR protocol, including DSR's basic Route Discovery and Route Maintenance mechanisms, was first published in December 1994 [JOHNSON94]; significant additional design details and initial simulation results were published in early 1996 [JOHNSON96a].
DSRの基本的なRouteディスカバリーとRoute Maintenanceメカニズムを含むDSRプロトコルの初期のデザインは1994[JOHNSON94]年12月に最初に、発行されました。 重要な追加デザインの詳細と初期のシミュレーションの結果は1996年[JOHNSON96a]前半に発表されました。
The DSR protocol has been extensively studied since then through additional detailed simulations. In particular, we have implemented DSR in the ns-2 network simulator [NS-2, BROCH98] and performed extensive simulations of DSR using ns-2 (e.g., [BROCH98, MALTZ99a]). We have also conducted evaluations of the different caching strategies in this document [HU00].
DSRプロトコルはそれ以来、追加詳細なシミュレーションで手広く研究されています。 私たちは、ナノ秒-2(例えば、[BROCH98、MALTZ99a])を使用することで特に、ナノ秒-2ネットワークシミュレータ[NS-2、BROCH98]でDSRを実装して、DSRの大規模なシミュレーションを実行しました。 また、私たちは本書では[HU00]異なったキャッシュ戦略の評価を行いました。
We have also implemented the DSR protocol under the FreeBSD 2.2.7 operating system running on Intel x86 platforms. FreeBSD [FREEBSD] is based on a variety of free software, including 4.4 BSD Lite, from the University of California, Berkeley. For the environments in which we used it, this implementation is functionally equivalent to the version of the DSR protocol specified in this document.
また、私たちはインテルx86プラットホームで走る無料OSの一つ2.2.7オペレーティングシステムの下でDSRプロトコルを実装しました。無料OSの一つ[FREEBSD]はさまざまなフリーソフトウェアに基づいています、4.4BSD Liteを含んでいて、カリフォルニア大学バークレイ校から。 私たちがそれを使用した環境において、この実装は本書では指定されたDSRプロトコルのバージョンに機能上同等です。
During the 7 months from August 1998 to February 1999, we designed and implemented a full-scale physical testbed to enable the evaluation of ad hoc network performance in the field, in an actively mobile ad hoc network under realistic communication workloads. The last week of February and the first week of March of 1999 included demonstrations of this testbed to a number of our sponsors and partners, including Lucent Technologies, Bell Atlantic, and the Defense Advanced Research Projects Agency (DARPA). A complete description of the testbed is available [MALTZ99b, MALTZ00, MALTZ01].
1998年8月から1999年2月までの7カ月、私たちは、その分野での臨時のネットワーク性能の評価を可能にするために実物大の物理的なテストベッドを設計して、実装しました、現実的なコミュニケーションワークロードの下の活発にモバイルの臨時のネットワークで。 2月の最後の週と1999年3月の1週間目は私たちの多くのスポンサーとパートナーにこのテストベッドのデモンストレーションを含めました、ルーセントテクノロジーズ、ベル・アトランティック、および国防高等研究計画庁(DARPA)を含んでいて。 テストベッドの完全な記述は利用可能です[MALTZ99b、MALTZ00、MALTZ01]。
We have since ported this implementation of DSR to FreeBSD 3.3, and we have also added a preliminary version of Quality of Service (QoS) support for DSR. A demonstration of this modified version of DSR was presented in July 2000. These QoS features are not included in this document and will be added later in a separate document on top of the base protocol specified here.
私たちは以来DSRのこの実装を無料OSの一つ3.3に移植しています、そして、また、DSRのService(QoS)サポートのQualityの準備段階を加えました。 DSRのこの変更されたバージョンのデモンストレーションは2000年7月に提示されました。 これらのQoSの特徴は、ここで指定されたベースプロトコルの上で本書では含まれていなくて、後で別々のドキュメントで加えられるでしょう。
DSR has also been implemented under Linux by Alex Song at the University of Queensland, Australia [SONG01]. This implementation supports the Intel x86 PC platform and the Compaq iPAQ.
また、DSRはクィーンズランド大学、オーストラリア[SONG01]でリナックスの下でアレックスSongによって実装されました。 この実装はインテルx86PCプラットホームとコンパックiPAQをサポートします。
The Network and Telecommunications Research Group at Trinity College, Dublin, have implemented a version of DSR on Windows CE.
トリニティー・カレッジ、ダブリンのNetworkとTelecommunications Research GroupはWindowsCEでDSRのバージョンを実装しました。
Microsoft Research has implemented a version of DSR on Windows XP and has used it in testbeds of over 15 nodes. Several machines use this implementation as their primary means of accessing the Internet.
マイクロソフトResearchはWindows XPの上のDSRのバージョンを実装して、15以上のノードのテストベッドでそれを使用しました。 数台のマシンがそれらのインターネットにアクセスするプライマリ手段としてこの実装を使用します。
Johnson, et al. Experimental [Page 100] RFC 4728 The Dynamic Source Routing Protocol February 2007
ジョンソン、他 ダイナミックな実験的な[100ページ]RFC4728のソースルーティング・プロトコル2007年2月
Several other independent groups have also used DSR as a platform for their own research, or as a basis of comparison between ad hoc network routing protocols.
また、他のいくつかの独立しているグループがそれら自身の調査のためのプラットホームとして、または、臨時のネットワークルーティング・プロトコルでの比較の基準としてDSRを使用しました。
A preliminary version of the optional DSR flow state extension was implemented in FreeBSD 3.3. A demonstration of this modified version of DSR was presented in July 2000. The DSR flow state extension has also been extensively evaluated using simulation [HU01].
任意のDSR流れ州の拡張子の準備段階は無料OSの一つ3.3で実装されました。 DSRのこの変更されたバージョンのデモンストレーションは2000年7月に提示されました。 また、DSR流れ州の拡張子は、シミュレーション[HU01]を使用することで手広く評価されました。
Acknowledgements
承認
The protocol described in this document has been designed and developed within the Monarch Project, a long-term research project at Rice University (previously at Carnegie Mellon University) that is developing adaptive networking protocols and protocol interfaces to allow truly seamless wireless and mobile node networking [JOHNSON96b, MONARCH].
Monarch Projectの中で本書では説明されたプロトコルを、設計されていて、開発してあります、ライス大学の長期の研究計画。(以前、カーネギー・メロンでは、大学) それは、[JOHNSON96b、MONARCH]をネットワークでつなぎながら本当にシームレスのワイヤレスの、そして、モバイルのノードを許容するために適応型のネットワーク・プロトコルとプロトコルインタフェースを開発します。
The authors would like to acknowledge the substantial contributions of Josh Broch in helping to design, simulate, and implement the DSR protocol. We thank him for his contributions to earlier versions of this document.
作者はDSRプロトコルを設計して、シミュレートして、実装するのを助けることにおける、ジョッシュ・ブロッホの多大な貢献を承諾したがっています。 私たちはこのドキュメントの以前のバージョンへの彼の貢献について彼に感謝します。
We would also like to acknowledge the assistance of Robert V. Barron at Carnegie Mellon University. Bob ported our DSR implementation from FreeBSD 2.2.7 into FreeBSD 3.3.
また、カーネギーメロン大学でロバート・V.バロンの支援を承諾したいと思います。 ボブは私たちのDSR実装を無料OSの一つ2.2.7から無料OSの一つ3.3に移植しました。
Many valuable suggestions came from participants in the IETF process. We would particularly like to acknowledge Fred Baker, who provided extensive feedback on a previous version of this document, as well as the working group chairs, for their suggestions of previous versions of the document.
多くの貴重な提案がIETFプロセスの関係者から来ました。 彼らのドキュメントの旧バージョンの提案のために、特にフレッド・ベイカーを承認したいと思います。(ベイカーは、このドキュメントの旧バージョン、およびワーキンググループいすで大規模なフィードバックを提供しました)。
Johnson, et al. Experimental [Page 101] RFC 4728 The Dynamic Source Routing Protocol February 2007
ジョンソン、他 ダイナミックな実験的な[101ページ]RFC4728のソースルーティング・プロトコル2007年2月
Normative References
引用規格
[RFC791] Postel, J., "Internet Protocol", STD 5, RFC 791,
September 1981.
[RFC791] ポステル、J.、「インターネットプロトコル」、STD5、RFC791、1981年9月。
[RFC792] Postel, J., "Internet Control Message Protocol", STD
5, RFC 792, September 1981.
[RFC792] ポステル、J.、「インターネット・コントロール・メッセージ・プロトコル」、STD5、RFC792、1981年9月。
[RFC826] Plummer, David C., "Ethernet Address Resolution
Protocol: Or converting network protocol addresses to
48.bit Ethernet address for transmission on Ethernet
hardware", STD 37, RFC 826, November 1982.
[RFC826]プラマー、デヴィッドC.、「イーサネットは解決プロトコルを扱います」。 「または、ネットワーク・プロトコルを変換するのは、イーサネットハードウェアの上でイーサネットがトランスミッションのためのアドレスであると48.bitに扱う」STD37、RFC826、1982年11月。
[RFC1122] Braden, R., "Requirements for Internet Hosts -
Communication Layers", STD 3, RFC 1122, October 1989.
[RFC1122]ブレーデン、R.、「インターネットのためのホスト--コミュニケーションが層にされるという要件」、STD3、RFC1122、10月1989日
[RFC1700] Reynolds, J. and J. Postel, "Assigned Numbers", STD 2,
RFC 1700, October 1994. See also
http://www.iana.org/numbers.html.
[RFC1700] レイノルズとJ.とJ.ポステル、「規定番号」、STD2、RFC1700、1994年10月。 また、 http://www.iana.org/numbers.html を見てください。
[RFC2003] Perkins, C., "IP Encapsulation within IP", RFC 2003,
October 1996. RFC 2003, October 1996.
[RFC2003] パーキンス、C.、「IPの中のIPカプセル化」、RFC2003、1996年10月。 1996年10月のRFC2003。
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2119] ブラドナー、S.、「Indicate Requirement LevelsへのRFCsにおける使用のためのキーワード」、BCP14、RFC2119、1997年3月。
[RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing
an IANA Considerations Section in RFCs", BCP 26, RFC
2434, October 1998.
[RFC2434]Narten、T.とH.Alvestrand、「RFCsにIANA問題部に書くためのガイドライン」BCP26、RFC2434(1998年10月)。
Informative References
有益な参照
[BANTZ94] David F. Bantz and Frederic J. Bauchot. Wireless LAN
Design Alternatives. IEEE Network, 8(2):43-53,
March/April 1994.
[BANTZ94]デヴィッドF.BantzとフレディリックJ.Bauchot。 ワイヤレスのLANデザイン代替手段。 IEEEネットワーク、8(2): 43-53と、1994年3月/4月。
[BHARGHAVAN94] Vaduvur Bharghavan, Alan Demers, Scott Shenker, and
Lixia Zhang. MACAW: A Media Access Protocol for
Wireless LAN's. In Proceedings of the ACM SIGCOMM '94
Conference, pages 212-225. ACM, August 1994.
[BHARGHAVAN94]Vaduvur Bharghavan、アランDemers、スコットShenker、およびLixiaチャン。 コンゴウインコ: メディアアクセスはワイヤレスのLANのもののために議定書を作ります。 ACM SIGCOMM94年のコンファレンスのProceedings、212-225ページで。 1994年8月のACM。
[BROCH98] Josh Broch, David A. Maltz, David B. Johnson, Yih-Chun
Hu, and Jorjeta Jetcheva. A Performance Comparison of
Multi-Hop Wireless Ad Hoc Network Routing Protocols.
In Proceedings of the Fourth Annual ACM/IEEE
International Conference on Mobile Computing and
Networking, pages 85-97. ACM/IEEE, October 1998.
[BROCH98]ジョッシュ・ブロッホ、デヴィッド・A.マルツ、デヴィッド・B.ジョンソン、Yih-クーン・胡、およびJorjeta Jetcheva。 マルチホップのワイヤレスの臨時のネットワークルーティング・プロトコルのパフォーマンス比較。 モバイルComputingとNetworkingの上のFourth Annual ACM/IEEEの国際コンファレンス、85-97ページのProceedingsで。 1998年10月のACM/IEEE。
Johnson, et al. Experimental [Page 102] RFC 4728 The Dynamic Source Routing Protocol February 2007
ジョンソン、他 ダイナミックな実験的な[102ページ]RFC4728のソースルーティング・プロトコル2007年2月
[CLARK88] David D. Clark. The Design Philosophy of the DARPA
Internet Protocols. In Proceedings of the ACM SIGCOMM
'88 Conference, pages 106-114. ACM, August 1988.
[CLARK88]デヴィッド・D.クラーク。 DARPAインターネットプロトコルの設計理念。 ACM SIGCOMM88年のコンファレンスのProceedings、106-114ページで。 1988年8月のACM。
[FREEBSD] The FreeBSD Project. Project web page available at
http://www.freebsd.org/.
[FREEBSD] 無料OSの一つは突出しています。 http://www.freebsd.org/ で利用可能なウェブページを映し出してください。
[HU00] Yih-Chun Hu and David B. Johnson. Caching Strategies
in On-Demand Routing Protocols for Wireless Ad Hoc
Networks. In Proceedings of the Sixth Annual ACM
International Conference on Mobile Computing and
Networking. ACM, August 2000.
[HU00] Yih-クーン・胡とデヴィッド・B.ジョンソン。 ワイヤレスの臨時のネットワークのために要求次第のルーティング・プロトコルの戦略をキャッシュします。 モバイル・コンピューティングとネットワークの第6年に一度のACM国際会議の議事で。 2000年8月のACM。
[HU01] Yih-Chun Hu and David B. Johnson. Implicit Source
Routing in On-Demand Ad Hoc Network Routing. In
Proceedings of the Second Symposium on Mobile Ad Hoc
Networking and Computing (MobiHoc 2001), pages 1-10,
October 2001.
[HU01] Yih-クーン・胡とデヴィッド・B.ジョンソン。 要求次第の臨時のネットワークルート設定における暗黙のソースルート設定。 モバイルAd Hoc NetworkingとComputing(MobiHoc2001)の上のSecond SymposiumのProceedings、1-10ページ、2001年10月に。
[HU02] Yih-Chun Hu, Adrian Perrig, and David B. Johnson.
Ariadne: A Secure On-Demand Routing Protocol for Ad
Hoc Networks. In Proceedings of the Eighth Annual
International Conference on Mobile Computing and
Networking (MobiCom 2002), pages 12-23, September
2002.
[HU02]Yih-クーン・胡、エードリアンPerrig、およびデヴィッド・B.ジョンソン。 アリアドネ: 臨時のネットワークのための安全な要求次第のルーティング・プロトコル。 モバイルComputingとNetworking(MobiCom2002)の上のEighth Annualの国際コンファレンスのProceedings、12-23ページ、2002年9月に。
[IEEE80211] IEEE Computer Society LAN MAN Standards Committee.
Wireless LAN Medium Access Control (MAC) and Physical
Layer (PHY) Specifications, IEEE Std 802.11-1997. The
Institute of Electrical and Electronics Engineers, New
York, New York, 1997.
[IEEE80211]IEEEコンピュータ社会LAN男性規格委員会。 ワイヤレスのLAN媒体アクセス制御(MAC)と物理的な層(PHY)の仕様、IEEE Std802.11-1997。 米国電気電子技術者学会(ニューヨーク)(ニューヨーク)1997。
[JOHANSSON99] Per Johansson, Tony Larsson, Nicklas Hedman, Bartosz
Mielczarek, and Mikael Degermark. Scenario-based
Performance Analysis of Routing Protocols for Mobile
Ad-hoc Networks. In Proceedings of the Fifth Annual
ACM/IEEE International Conference on Mobile Computing
and Networking, pages 195-206. ACM/IEEE, August 1999.
1ヨハンソンあたりの[JOHANSSON99]、トニー・ラーソン、ニクラス・ヘドマン、バルトシュMielczarek、およびマイケル・デーゲルマルク。 モバイル臨時のネットワークのためのルーティング・プロトコルのシナリオベースの機能解析。 モバイルComputingとNetworkingの上の黙秘権のAnnual ACM/IEEEの国際コンファレンス、195-206ページのProceedingsで。 1999年8月のACM/IEEE。
[JOHNSON94] David B. Johnson. Routing in Ad Hoc Networks of
Mobile Hosts. In Proceedings of the IEEE Workshop on
Mobile Computing Systems and Applications, pages 158-
163. IEEE Computer Society, December 1994.
[JOHNSON94]デヴィッド・B.ジョンソン。 モバイルホストの臨時のネットワークでは、掘ります。 モバイルComputing SystemsとApplicationsの上のIEEE WorkshopのProceedings、158- 163ページで。 1994年12月のIEEEコンピュータ社会。
Johnson, et al. Experimental [Page 103] RFC 4728 The Dynamic Source Routing Protocol February 2007
ジョンソン、他 ダイナミックな実験的な[103ページ]RFC4728のソースルーティング・プロトコル2007年2月
[JOHNSON96a] David B. Johnson and David A. Maltz. Dynamic Source
Routing in Ad Hoc Wireless Networks. In Mobile
Computing, edited by Tomasz Imielinski and Hank Korth,
chapter 5, pages 153-181. Kluwer Academic Publishers,
1996.
[JOHNSON96a]デヴィッド・B.ジョンソンとデヴィッド・A.マルツ。 臨時のワイヤレス・ネットワークにおけるダイナミックなソースルート設定。 第5章、153-181ページのトマシュ・イメリンスキーとハンク・コースによって編集されたモバイルComputingで。 Kluwerのアカデミックな出版社、1996。
[JOHNSON96b] David B. Johnson and David A. Maltz. Protocols for
Adaptive Wireless and Mobile Networking. IEEE
Personal Communications, 3(1):34-42, February 1996.
[JOHNSON96b]デヴィッド・B.ジョンソンとデヴィッド・A.マルツ。 適応型のワイヤレスの、そして、モバイルのネットワークのためのプロトコル。 IEEEの個人的なコミュニケーション、3(1): 34-42と、1996年2月。
[JUBIN87] John Jubin and Janet D. Tornow. The DARPA Packet
Radio Network Protocols. Proceedings of the IEEE,
75(1):21-32, January 1987.
[JUBIN87]ジョンJubinとジャネットD.Tornow。 DARPAパケットラジオネットワーク・プロトコル。 IEEEの議事、75(1): 21-32と、1987年1月。
[KARN90] Phil Karn. MACA---A New Channel Access Method for
Packet Radio. In ARRL/CRRL Amateur Radio 9th Computer
Networking Conference, pages 134-140. American Radio
Relay League, September 1990.
[KARN90]フィルKarn。 MACA---パケットラジオのための新しいチャンネルアクセス法。 ARRL/CRRL Amateur Radio第9コンピュータNetworkingコンファレンス、134-140ページで。 1990年9月のアメリカの無線中継連盟。
[LAUER95] Gregory S. Lauer. Packet-Radio Routing. In Routing
in Communications Networks, edited by Martha E.
Steenstrup, chapter 11, pages 351-396. Prentice-Hall,
Englewood Cliffs, New Jersey, 1995.
[LAUER95]グレゴリー・S.ラウアー。 パケットラジオルート設定。 第11章、351-396ページのマーサ・E.ステーンストルプによって編集されたCommunications Networksのルート設定で。 新米のホール、イングルウッドがけ、ニュージャージー、1995。
[MALTZ99a] David A. Maltz, Josh Broch, Jorjeta Jetcheva, and
David B. Johnson. The Effects of On-Demand Behavior
in Routing Protocols for Multi-Hop Wireless Ad Hoc
Networks. IEEE Journal on Selected Areas of
Communications, 17(8):1439-1453, August 1999.
[MALTZ99a] デヴィッド・A.マルツ、ジョッシュ・ブロッホ、Jorjeta Jetcheva、およびデヴィッド・B.ジョンソン。 マルチホップのワイヤレスの臨時のネットワークのためのルーティング・プロトコルにおける、要求次第の振舞いの効果。 コミュニケーションの選択された領域に関するIEEEジャーナル、17(8): 1439-1453と、1999年8月。
[MALTZ99b] David A. Maltz, Josh Broch, and David B. Johnson.
Experiences Designing and Building a Multi-Hop
Wireless Ad Hoc Network Testbed. Technical Report
CMU-CS-99-116, School of Computer Science, Carnegie
Mellon University, Pittsburgh, Pennsylvania, March
1999.
[MALTZ99b] デヴィッド・A.マルツ、ジョッシュ・ブロッホ、およびデヴィッド・B.ジョンソン。 マルチホップのワイヤレスの臨時のネットワークテストベッドを設計して、建設するという経験。 技術報告書米カーネギーメロン大学Cs99-116、コンピュータサイエンスの学校、カーネギーメロン大学、1999年のピッツバーグ(ペンシルバニア)行進。
[MALTZ00] David A. Maltz, Josh Broch, and David B. Johnson.
Quantitative Lessons From a Full-Scale Multi-Hop
Wireless Ad Hoc Network Testbed. In Proceedings of
the IEEE Wireless Communications and Networking
Conference. IEEE, September 2000.
[MALTZ00] デヴィッド・A.マルツ、ジョッシュ・ブロッホ、およびデヴィッド・B.ジョンソン。 マルチホップの実物大のワイヤレス臨時のネットワークテストベッドからの量的なレッスン。 IEEE無線通信とネットワークコンファレンスの議事で。 2000年9月のIEEE。
[MALTZ01] David A. Maltz, Josh Broch, and David B. Johnson.
Lessons From a Full-Scale MultiHop Wireless Ad Hoc
Network Testbed. IEEE Personal Communications,
8(1):8-15, February 2001.
[MALTZ01] デヴィッド・A.マルツ、ジョッシュ・ブロッホ、およびデヴィッド・B.ジョンソン。 マルチホップの実物大のワイヤレス臨時のネットワークテストベッドからのレッスン。 IEEEの個人的なコミュニケーション、8(1): 8-15と、2001年2月。
Johnson, et al. Experimental [Page 104] RFC 4728 The Dynamic Source Routing Protocol February 2007
ジョンソン、他 ダイナミックな実験的な[104ページ]RFC4728のソースルーティング・プロトコル2007年2月
[MONARCH] Rice University Monarch Project. Monarch Project Home
Page. Available at http://www.monarch.cs.rice.edu/.
[君主]ライス大学君主プロジェクト。 君主プロジェクトホームページ。 http://www.monarch.cs.rice.edu/ では、利用可能です。
[NS-2] The Network Simulator -- ns-2. Project web page
available at http://www.isi.edu/nsnam/ns/.
[NS-2] Network Simulator--ナノ秒-2。 http://www.isi.edu/nsnam/ns/ で利用可能なウェブページを映し出してください。
[PAPADIMITRATOS02]
Panagiotis Papadimitratos and Zygmunt J. Haas. Secure
Routing for Mobile Ad Hoc Networks. In SCS
Communication Networks and Distributed Systems
Modeling and Simulation Conference (CNDS 2002),
January 2002.
[PAPADIMITRATOS02]パナギオティスPapadimitratosとジグムント・J.ハース。 モバイル臨時のネットワークのためにルート設定を保証してください。 Sc通信ネットワークと分散システムモデリングシミュレーションコンファレンス(CNDS2002)、2002年1月に。
[PERLMAN92] Radia Perlman. Interconnections: Bridges and
Routers. Addison-Wesley, Reading, Massachusetts,
1992.
[PERLMAN92]Radiaパールマン。 インタコネクト: ブリッジとルータ。 アディソン-ウエスリー、読書、マサチューセッツ、1992。
[RFC793] Postel, J., "Transmission Control Protocol", STD 7,
RFC 793, September 1981.
[RFC793] ポステル、J.、「通信制御プロトコル」、STD7、RFC793、1981年9月。
[RFC2131] Droms, R., "Dynamic Host Configuration Protocol", RFC
2131, March 1997.
[RFC2131] Droms、R.、「ダイナミックなホスト構成プロトコル」、RFC2131、1997年3月。
[RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version
6 (IPv6) Specification", RFC 2460, December 1998.
[RFC2460]デアリング、S.とR.Hinden、「インターネットプロトコル、バージョン6(IPv6)仕様」、RFC2460、12月1998日
[SONG01] Alex Song. picoNet II: A Wireless Ad Hoc Network for
Mobile Handheld Devices. Submitted for the degree of
Bachelor of Engineering (Honours) in the division of
Electrical Engineering, Department of Information
Technology and Electrical Engineering, University of
Queensland, Australia, October 2001. Available at
http://piconet.sourceforge.net/thesis/index.html.
[SONG01]アレックスSongピコネットII: モバイルハンドヘルドデバイスのためのワイヤレスの臨時のネットワーク。 Electrical Engineeringの分割、情報Technologyの部とElectrical Engineering、クィーンズランド大学、オーストラリアの工学士(名誉)の度合いのために、2001年10月に提出します。 http://piconet.sourceforge.net/thesis/index.html では、利用可能です。
[TURNER90] Paul Turner. NetWare Communications Processes.
NetWare Application Notes, Novell Research, pages 25-
91, September 1990.
[TURNER90]ポール・ターナー。 NetWareコミュニケーションプロセス。 NetWare Application Notes、ノベルResearch、25- 91ページ、1990年9月。
[WRIGHT95] Gary R. Wright and W. Richard Stevens. TCP/IP
Illustrated, Volume 2: The Implementation. Addison-
Wesley, Reading, Massachusetts, 1995.
[WRIGHT95]ゲーリー・R.ライトとW.リチャード・スティーブンス。 例証されたTCP/IP、第2巻: 実装。 アディソンウエスリー、読書、マサチューセッツ、1995。
Johnson, et al. Experimental [Page 105] RFC 4728 The Dynamic Source Routing Protocol February 2007
ジョンソン、他 ダイナミックな実験的な[105ページ]RFC4728のソースルーティング・プロトコル2007年2月
Authors' Addresses
作者のアドレス
David B. Johnson Rice University Computer Science Department, MS 132 6100 Main Street Houston, TX 77005-1892 USA
デヴィッドB.ペニスライス大学コンピュータ理学部、MS132 6100大通りのヒューストン、テキサス77005-1892米国
Phone: +1 713 348-3063 Fax: +1 713 348-5930 EMail: dbj@cs.rice.edu
以下に電話をしてください。 +1 713 348-3063Fax: +1 713 348-5930 メールしてください: dbj@cs.rice.edu
David A. Maltz Microsoft Research One Microsoft Way Redmond, WA 98052 USA
デヴィッドA.マルツマイクロソフトは1つのマイクロソフト方法でワシントン98052レッドモンド(米国)について研究します。
Phone: +1 425 706-7785 Fax: +1 425 936-7329 EMail: dmaltz@microsoft.com
以下に電話をしてください。 +1 425 706-7785Fax: +1 425 936-7329 メールしてください: dmaltz@microsoft.com
Yih-Chun Hu University of Illinois at Urbana-Champaign Coordinated Science Lab 1308 West Main St, MC 228 Urbana, IL 61801 USA
Urbana-ChampaignにおけるイリノイのYih-クーン胡大学は科学研究室1308の西主な通り、米国のM.C.228アーバナ、IL61801を調整しました。
Phone: +1 217 333-4220 EMail: yihchun@uiuc.edu
以下に電話をしてください。 +1 217 333-4220 メールしてください: yihchun@uiuc.edu
Johnson, et al. Experimental [Page 106] RFC 4728 The Dynamic Source Routing Protocol February 2007
ジョンソン、他 ダイナミックな実験的な[106ページ]RFC4728のソースルーティング・プロトコル2007年2月
Full Copyright Statement
完全な著作権宣言文
Copyright (C) The IETF Trust (2007).
IETFが信じる著作権(C)(2007)。
This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights.
このドキュメントはBCP78に含まれた権利、ライセンス、および制限を受けることがあります、そして、そこに詳しく説明されるのを除いて、作者は彼らのすべての権利を保有します。
This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
このドキュメントとここに含まれた情報はその人が代理をするか、または(もしあれば)後援される組織、インターネットの振興発展を目的とする組織、「そのままで」という基礎と貢献者の上で提供していて、IETFはそして、インターネット・エンジニアリング・タスク・フォースがすべての保証を放棄すると信じます、急行である、または暗示していて、他を含んでいて、情報の使用がここに侵害しないどんな保証も少しもまっすぐになるということであるかいずれが市場性か特定目的への適合性の黙示的な保証です。
Intellectual Property
知的所有権
The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79.
IETFはどんなIntellectual Property Rightsの正当性か範囲、実装に関係すると主張されるかもしれない他の権利、本書では説明された技術の使用またはそのような権利の下におけるどんなライセンスも利用可能であるかもしれない、または利用可能でないかもしれない範囲に関しても立場を全く取りません。 または、それはそれを表しません。どんなそのような権利も特定するどんな独立している取り組みも作りました。 BCP78とBCP79でRFCドキュメントの権利に関する手順に関する情報を見つけることができます。
Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr.
IPR公開のコピーが利用可能に作られるべきライセンスの保証、または一般的な免許を取得するのが作られた試みの結果をIETF事務局といずれにもしたか、または http://www.ietf.org/ipr のIETFのオンラインIPR倉庫からこの仕様のimplementersかユーザによるそのような所有権の使用のために許可を得ることができます。
The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org.
IETFはこの規格を実装するのに必要であるかもしれない技術をカバーするかもしれないどんな著作権もその注目していただくどんな利害関係者、特許、特許出願、または他の所有権も招待します。 ietf-ipr@ietf.org のIETFに情報を扱ってください。
Acknowledgement
承認
Funding for the RFC Editor function is currently provided by the Internet Society.
RFC Editor機能のための基金は現在、インターネット協会によって提供されます。
Johnson, et al. Experimental [Page 107]
ジョンソン、他 実験的[107ページ]
一覧
スポンサーリンク
