Opened 7 years ago
Last modified 6 years ago
#46 assigned defect
What is needed from IP and ICMP (submitted for Chris Dearlove)
Reported by: | charliep@… | Owned by: | charliep@… |
---|---|---|---|
Priority: | minor | Milestone: | |
Component: | aodvv2 | Version: | |
Severity: | Active WG Document | Keywords: | IP/ICMP interaction |
Cc: |
Description
The protocol needs many things from IP, such as failed routing notification, and interacts with it in ways such as queuing packets. It also interacts (sends and receives) with ICMP, and I'm not sure what else. This needs to be put together, so the reader can see what is needed to be able to implement this.
Change History (4)
comment:1 Changed 7 years ago by charliep@…
- Owner changed from draft-ietf-manet-aodvv2@… to charliep@…
comment:2 Changed 6 years ago by charliep@…
comment:3 Changed 6 years ago by charliep@…
- Status changed from new to assigned
comment:4 Changed 6 years ago by charliep@…
The following text is proposed to resolve this issue:
Appendix G. Features of IP needed by AODVv2
AODVv2 needs the following:
o information that IP routes are requested
o information that packets are flowing
o the ability to queue packets.
A reactive protocol reacts when a route is needed. One might say that a route is requested when an application tries to send a packet. The fundamental concept of reactive routing is to avoid creating routes that are not needed, and the way that has been used to know whether a route is needed is when an application tries to send a packet.
If an application tries to send a packet, and the route is not available, the packet has to wait until the route is available.
If this text is sufficient to explain what is needed from IP and ICMP and from commodity OSs, then the issue should be closed.
On 9/8/2014 10:45 AM, Christopher Dearlove wrote: