Opened 5 years ago

Last modified 5 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 5 years ago by charliep@…

  • Owner changed from draft-ietf-manet-aodvv2@… to charliep@…

comment:2 Changed 5 years ago by charliep@…

On 9/8/2014 10:45 AM, Christopher Dearlove wrote:

This needs specifying .... And also because people who want to implement it know what capabilities they need. If they need queueing in the IP stack they need to be told they need queuing in the IP stack. And that makes it clear this needs to be more than a routing protocol if that capability is not available as standard, which I think you just agreed it's not. Knowledge in the ad hoc routing community isn't enough.

On 8 Sep 2014, at 18:20, Charles E. Perkins wrote:

On 9/7/2014 3:01 PM, Abdussalam Baryun wrote:

I think you may misunderstand MANET reactive routing. I don't see your reply answers the editor question of examples of AODVv2 needs from IP or ICMP. You mention that the protocol needs to see ICMP, what is the problem with that as RFC3561 already has similar issue and already accepted by WG.

On Tuesday, July 22, 2014, Dearlove, Christopher (UK) wrote:

Just for a start you also need to know that IP routes are requested, that packets are flowing, and to have the ability to queue packets.

On Tuesday, July 22, 2014, Dearlove, Christopher (UK) wrote something that Charlie interprets as follows:

AODVv2 needs the following:

  • information that IP routes are requested
  • information that packets are flowing
  • the ability to queue packets.

Tautologically, 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 available, the packet has to wait until the route is available. So, yes, queuing a packet is needed.

comment:3 Changed 5 years ago by charliep@…

  • Status changed from new to assigned

comment:4 Changed 5 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.

Note: See TracTickets for help on using tickets.