We've frittered away a week or more talking about this issue. That doesn't mean
to say nothing else is getting done, but it's not just a day or two - it's
"some indeterminate amount of time, which has been preceded by an enormous
amount of time, endlessly grinding away on an issue that is miniscule in and
amongst the plethora of issues for the team to deal with." If you have to
"craft" a brand-new registry, that (in and of itself) marks yet another point
of contention in an endless sea of contention surrounding this document.
My patience is at an end. There's a resolution to this problem right in front
of us. I refuse to twist, twirl, and kvetch any more over it. My call for
consensus stands.
Stick a fork in me, 'cause I'm done.
Stan
-----Original Message-----
From: aodvv2-discuss-bounce@xxxxxxxxxxxxx [mailto:aodvv2-discuss-
bounce@xxxxxxxxxxxxx] On Behalf Of Charlie Perkins
Sent: Thursday, April 14, 2016 1:57 PM
To: aodvv2-discuss@xxxxxxxxxxxxx
Subject: [aodvv2-discuss] Re: Metric type registry
Hello Stan,
When I say a day or two, that's what I mean. It's the weekend anyway and
this won't affect the production of another draft. You don't have to have
much patience to let me at least get this answer.
What was the genesis of the 32-bit idea anyway?
Regards,
Charlie P.
On 4/14/2016 10:53 AM, Ratliff, Stanley wrote:
Charlie,day or two" is 'no'. We resolve this here and now, and move on. There are
My patience has reached it's "sell-by" date. So my answer for "give me a
bigger fish to fry.
metrics.
Stsan
-----Original Message-----
From: aodvv2-discuss-bounce@xxxxxxxxxxxxx [mailto:aodvv2-discuss-
bounce@xxxxxxxxxxxxx] On Behalf Of Charlie Perkins
Sent: Thursday, April 14, 2016 1:52 PM
To: aodvv2-discuss@xxxxxxxxxxxxx
Subject: [aodvv2-discuss] Re: Metric type registry
Hello Stan,
I hope you will give me a day or two to sort this out.
Believe me, I want this done even more than you do.
Regards,
Charlie P.
On 4/14/2016 10:50 AM, Ratliff, Stanley wrote:
Charlie,AODVv2? Will AODVv2 now *require* this brand-new,
And how long is this supposed to take? Will it impact getting to
WGLC on
protocol-independent registry?
This looks suspiciously like a rat-hole to me. Remember what I saidBuenos Aires? "It's April. I don't want to be doing this in May. And
in
if it gets to June, it won't be our decision."
We're losing focus here. I know you hate the notion of a 32-bitrepresents hop count. However, I now call for consensus amongst the
metric that
editing team - I believe the implementation of a 32-bit metric for
AODVv2 is the best way to go. I want to hear opinions from my co-editors.
Regards,answer.
Stan
-----Original Message-----
From: aodvv2-discuss-bounce@xxxxxxxxxxxxx [mailto:aodvv2-discuss-
bounce@xxxxxxxxxxxxx] On Behalf Of Charlie Perkins
Sent: Thursday, April 14, 2016 1:45 PM
To: aodvv2-discuss@xxxxxxxxxxxxx
Subject: [aodvv2-discuss] Metric type registry
Hello folks,
The situation is not yet clear. I am asking various people and
getting some unexpected answers. I will craft a registry for
protocol-independent Metric Types. I did not find one for OLSR or
OLSRv2, but if there is one please let me know. One way or another
we will have an answer within a day or two, perhaps awaiting a
better
I'll be honest. I am more than surprised about this. Routing uses
sender.Where are they? It's amazing._____________________________________________________
More later.
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
_____________________________________________________
_____________________________________________________
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.
_____________________________________________________
