[aodvv2-discuss] Re: FW: Re: How to interface with the host routing table <from user space>?

  • From: "Ratliff, Stanley" <sratliff@xxxxxxxxxxx>
  • To: "aodvv2-discuss@xxxxxxxxxxxxx" <aodvv2-discuss@xxxxxxxxxxxxx>
  • Date: Mon, 31 Aug 2015 18:03:02 +0000



-----Original Message-----
From: aodvv2-discuss-bounce@xxxxxxxxxxxxx [mailto:aodvv2-discuss-
bounce@xxxxxxxxxxxxx] On Behalf Of Charlie Perkins
Sent: Monday, August 31, 2015 1:54 PM
To: aodvv2-discuss@xxxxxxxxxxxxx
Subject: [aodvv2-discuss] Re: FW: Re: How to interface with the host routing
table <from user space>?

Hello Stan,

I thought my point was responsive to your question. Some of the operations
affecting the route table happen because a link breaks and routes need to be
invalidated, or a packet cannot be forwarded. If a solution does not handle
link breakages, then that solution will impose less burden on the route table
interface.

Irrespective of a link break - *any* routing protocol *must* have a route
table. It either uses one of its own, or it interfaces with the support in the
host. I'm not nearly as concerned about the specifics of how that happens
(e.g., relinking objects, new libraries, etc), as I am with how to express that
interface in a standards document, so as to NOT draw the ire of fellow working
group participants.


I really don't think I was talking past you on this.

I interpret your words to mean that we should NOT respond on the mailing
list until ALL of the comments have some resolution.

That's not what I meant. I'm saying we should NOT respond to "most" of the
issues and merely remain silent on "some", especially when one of the "some"
has been raised by Thomas, and is pretty critical in nature.


If you would like to be more responsive sooner, we could instead post
follow-up on MOST of the comments with the further notice that our full
resolution to the route table interface question is not yet complete.

Yes, that is what needs to be done - at a bare minimum, we need some text in an
email response to the list saying "We are looking at the issue of the interface
to the host routing table, and will follow-up in a separate email".

Stan



No matter what, the route table interface question deserves its own email.

Regards,
Charlie P.


On 8/31/2015 10:39 AM, Ratliff, Stanley wrote:
Charlie,

I get the distinct impression that, as a co-worker of mine used to say,
"We're talking past each other". I don't know how we got off into link
breakage, or re-linking the object files with a socket wrapper, or recompiling
with a new clib.a... and at any rate, all of that discussion is at a much more
detailed-level than I was interested in. I'm just simply trying to string 3
points
together to give us some direction:

1. Clausen is raising (valid, IMO) concerns about how the AODVv2 draft
interfaces with the host routing table.
2. LOADng was (apparently) written in such a manner that interface with
host routing table wasn't an issue (or it dealt with it).
3. Therefore, why don't we use LOADng as a template to craft text
concerning the interface with the host routing table?

As for your statement that.. "But first, we have to get responses back to
the WG mailing list..." I'm unwilling to respond to the list without at least
attempting to address Thomas' route table issue. Since he (Thomas) has, by
far, complained the loudest about the AODVv2 team being "unresponsive"
and "unwilling to change", I think it's imperative that we at least
acknowledge
that we are looking at his concern. Anything less than that will put us back
into the same vicious loop we were in until very recently.

Regards,
Stan


-----Original Message-----
From: aodvv2-discuss-bounce@xxxxxxxxxxxxx [mailto:aodvv2-discuss-
bounce@xxxxxxxxxxxxx] On Behalf Of Charlie Perkins
Sent: Monday, August 31, 2015 1:25 PM
To: aodvv2-discuss@xxxxxxxxxxxxx
Subject: [aodvv2-discuss] Re: How to interface with the host routing
table <from user space>?

Hello Stan,

I'm not sure they handle link breakage. I'd have to go look again...
I'll try to do that "soon". But first, we have to get responses back
to the WG mailing list. I'm working on summarizing the discussion on
this list related to 'Resolving comments within file
"draft-ietf-manet-aodvv2-11 (p1-22).pdf"' I hope to send the result
to you all today.

Does anyone else want to post it to the [manet] list, as requested
previously?

Regards,
Charlie P.



On 8/31/2015 10:08 AM, Ratliff, Stanley wrote:
Charlie,

OK....

The point I was trying to make is that the LOADng spec was written
(or, at
least I figure it was written) in such a way that the interface to
the host routing table wasn't an issue. Stealing text would be a bad
thing (especially since the last time I looked, LOADng was
copyrighted), but we could take a look, see how LOADng as structured,
and consider structuring AODVv2 in a similar fashion, so as to address the
concerns.
Regards,
Stan


-----Original Message-----
From: aodvv2-discuss-bounce@xxxxxxxxxxxxx [mailto:aodvv2-discuss-
bounce@xxxxxxxxxxxxx] On Behalf Of Charlie Perkins
Sent: Monday, August 31, 2015 1:02 PM
To: aodvv2-discuss@xxxxxxxxxxxxx
Subject: [aodvv2-discuss] How to interface with the host routing
table <from user space>?

Hello folks,

I can think of at least four ways to do it without messing with the
kernel, in addition to the brute-force ways of re-linking the
object files using a socket wrapper library. Or, typically worse,
recompiling with a new clib.a. But all of them have more overhead.

Regards,
Charlie P.



On 8/25/2015 10:16 AM, Ratliff, Stanley wrote:
Charlie,

Well, as to all of the interface with the host routing table, I
wonder - how
did LOADng do it? Justin? Any guidance here as to how LOADng pulled
off Linux routing table interface?
Regards,
Stan


-----Original Message-----
From: aodvv2-discuss-bounce@xxxxxxxxxxxxx [mailto:aodvv2-discuss-
bounce@xxxxxxxxxxxxx] On Behalf Of Charlie Perkins
Sent: Tuesday, August 25, 2015 12:36 PM
To: aodvv2-discuss@xxxxxxxxxxxxx
Subject: [aodvv2-discuss] When shall we meet to get the new draft
out?

Hello folks,

I will prepare a response to Clausen's comments. Given past
history, it might be nice for someone else's name to be on the
"From:" line of that email to the list.

Shouldn't we be having a meeting and getting a new draft out very
soon?
Regards,
Charlie P.


_____________________________________________________
This electronic message and any files transmitted with it contains
information from iDirect, which may be privileged, proprietary
and/or confidential. It is intended solely for the use of the
individual or entity to whom they are addressed. If you are not
the original recipient or the person responsible for delivering
the email to the intended recipient, be advised that you have
received this email in error, and that any use, dissemination,
forwarding, printing, or copying of this email is strictly
prohibited. If you received this email in error, please delete it
and immediately notify the
sender.
_____________________________________________________
_____________________________________________________
This electronic message and any files transmitted with it contains
information from iDirect, which may be privileged, proprietary
and/or confidential. It is intended solely for the use of the
individual or entity to whom they are addressed. If you are not the
original recipient or the person responsible for delivering the
email to the intended recipient, be advised that you have received
this email in error, and that any use, dissemination, forwarding,
printing, or copying of this email is strictly prohibited. If you
received this email in error, please delete it and immediately notify the
sender.
_____________________________________________________


_____________________________________________________
This electronic message and any files transmitted with it contains
information from iDirect, which may be privileged, proprietary and/or
confidential. It is intended solely for the use of the individual or
entity to whom they are addressed. If you are not the original
recipient or the person responsible for delivering the email to the
intended recipient, be advised that you have received this email in
error, and that any use, dissemination, forwarding, printing, or
copying of this email is strictly prohibited. If you received this
email in error, please delete it and immediately notify the sender.
_____________________________________________________




_____________________________________________________
This electronic message and any files transmitted with it contains
information from iDirect, which may be privileged, proprietary
and/or confidential. It is intended solely for the use of the individual
or entity to whom they are addressed. If you are not the original
recipient or the person responsible for delivering the email to the
intended recipient, be advised that you have received this email
in error, and that any use, dissemination, forwarding, printing, or
copying of this email is strictly prohibited. If you received this email
in error, please delete it and immediately notify the sender.
_____________________________________________________

Other related posts:

  1. Home
  2. aodvv2-discuss
  3. Archive
  4. 08-2015