<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Alan,<br>
<br>
all I'm trying to do is talk things over. You take that as arguing. <br>
<br>
I have understood what you have stated. I'm just trying to tell you, it
isn't as obvious always as you might think it is. Sure, for you it is
easy, as you've even written the RFCs. Not everyone has the background
knowledge you do, which means they'll ask questions about things. That
is all I have done here. I did also tell you, I've not had a chance to
read the draft yet. Things may still clear up for me. So, give me that
chance to read things and get the understanding you have.<br>
<br>
There surely is no need to get into a huff about things, is there?<br>
<br>
//anders<br>
<br>
<br>
Alan DeKok wrote:
<blockquote cite="mid:494E4993.1000809@deployingradius.com" type="cite">
<pre wrap="">Anders Holm wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Ah, the missing piece emerges. This is probably what I was missing.
</pre>
</blockquote>
<pre wrap=""><!---->
My frustration is that I explained how it works. Rather than
believing that explanation, you started arguing about the rationale
behind the explanation.
That wasn't necessary.
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> Are you being deliberately obtuse? Or just deliberately difficult?
</pre>
</blockquote>
<pre wrap="">Neither. I'm deliberately trying to understand how it all works. The
draft you linked above may or may not do so.
</pre>
</blockquote>
<pre wrap=""><!---->
It was explained. Status-Server packets get Access-Accept responses.
Access-Request counters don't get incremented for Status-Server packets.
You can believe the explanations, or you can argue about them.
</pre>
<blockquote type="cite">
<pre wrap="">Ah. 3 simple rules that weren't spelled out anywhere in the
documentation you mean?
</pre>
</blockquote>
<pre wrap=""><!---->
I had explained them in my earlier email. The one you argued with.
</pre>
<blockquote type="cite">
<pre wrap="">No, nothing is asking for access. Something is asking for status. This
is why I spelled out the 3 Status counters I did.
</pre>
</blockquote>
<pre wrap=""><!---->
<sigh> There are no 3 status counters. This has been explained.
</pre>
<blockquote type="cite">
<pre wrap="">Starting with a Status-Request, not an Access-Request.
</pre>
</blockquote>
<pre wrap=""><!---->
There is no Status-Request packet. Why are you inventing it?
</pre>
<blockquote type="cite">
<pre wrap="">I my mind, the result of that is
either a Status-Accept or Status-Reject.
</pre>
</blockquote>
<pre wrap=""><!---->
There is no Status-Accept packet or Status-Reject packet. Why are you
inventing them?
</pre>
<blockquote type="cite">
<pre wrap="">Now, I still haven't had a
chance to read that draft, I'm just saying how I'm thinking about it.
</pre>
</blockquote>
<pre wrap=""><!---->
Your thinking is wrong.
When I say "Status-Server" packet... I mean "Status-Server". Not
"Status-Request". When I say "Access-Accept" packet, I mean
"Access-Accept", not "Status-Accept".
This is really the fundamental part of the miscommunication. I mean
what I say. I write what I mean. Yet when I do that, you interpret it
as meaning something else.
Why?
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> This is a fascinating discusion in how a simple example can be twisted
into something unrecognizable.
</pre>
</blockquote>
<pre wrap="">I find it a fascinating example of how misunderstandings can go way out
of order instead of trying to be rectified.
</pre>
</blockquote>
<pre wrap=""><!---->
Just... stop.
I've given the same explanation multiple times. I've tried to rectify
your misunderstandings.
You have (even in this message) refused to understand that the
response to a Status-Server is an Access-Accept. Not a Status-Accept.
Not a Status-Reject. Even when I gave the "3 simple rules", one of
which is:
c) The response to Status-Server is Access-Accept
You *still* talk about the response to a Status-Request being a
Status-Accept.
Uh... WTF? Did you not understand the line (c) above? And you
accusing *me* of "not trying to rectify a misunderstanding" ?
Believe me, I'm trying. Multiple times. Yet you are *consistently*
ignoring my answers, and talking about "Status-Request", and
"Status-Accept".
If you're not going to read my response, I don't understand why you're
asking questions.
</pre>
<blockquote type="cite">
<pre wrap="">I'm about to read it. So, what you're saying there is someone else than
the author I should ask if I don't understand it? See how easy things
get misunderstood?
</pre>
</blockquote>
<pre wrap=""><!---->
I'm saying that I obviously lack the skills to explain it to you.
Witness your responses to my message: I say "Status-Server", you read
"Status-Request". I say "Access-Accept", you read "Status-Accept".
I don't know how to fix that problem on my end.
If this sounds mean... please explain to me how it's nice to read:
c) The response to Status-Server is Access-Accept
and then to respond with:
Starting with a Status-Request... the result of that is
either a Status-Accept or Status-Reject.
?
Alan DeKok.
-
List info/subscribe/unsubscribe? See <a class="moz-txt-link-freetext" href="http://www.freeradius.org/list/users.html">http://www.freeradius.org/list/users.html</a>
</pre>
</blockquote>
<br>
</body>
</html>