Re: [Seamoby] IP Paging ]Framework discussion

"James Kempf" <kempf@docomolabs-usa.com> Thu, 03 January 2002 17:57 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA07070 for <seamoby-archive@odin.ietf.org>; Thu, 3 Jan 2002 12:57:02 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA11288; Thu, 3 Jan 2002 12:45:54 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA11228 for <seamoby@optimus.ietf.org>; Thu, 3 Jan 2002 12:45:51 -0500 (EST)
Received: from docomolabs-usa.com (fridge.docomo-usa.com [216.98.102.228]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA06762 for <seamoby@ietf.org>; Thu, 3 Jan 2002 12:45:48 -0500 (EST)
Received: from T23KEMPF (dhcp126.docomo-usa.com [172.21.96.126]) by docomolabs-usa.com (8.11.3/8.11.3) with SMTP id g03HjHS00653; Thu, 3 Jan 2002 09:45:17 -0800 (PST)
Message-ID: <007701c1947e$2ecb7380$7e6015ac@T23KEMPF>
From: James Kempf <kempf@docomolabs-usa.com>
To: Behcet Sarikaya <behcet.sarikaya@alcatel.com>
Cc: seamoby@ietf.org
References: <3C335823.5030009@alcatel.com> <016f01c193c7$0ae59e80$7e6015ac@T23KEMPF> <3C337390.4000109@alcatel.com> <01fe01c193d5$04e33200$7e6015ac@T23KEMPF> <3C348C0F.C0360646@alcatel.com>
Subject: Re: [Seamoby] IP Paging ]Framework discussion
Date: Thu, 03 Jan 2002 09:43:41 -0800
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Content-Transfer-Encoding: 7bit
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Context Transfer, Handoff Candidate Discovery, and Dormant Mode Host Alerting <seamoby.ietf.org>
X-BeenThere: seamoby@ietf.org
Content-Transfer-Encoding: 7bit

Behcet,

>   You still have not posted the slides neither the minutes. How many
times
> should I ask this?

I will post the minutes today, the slides are on Pat's machine and he
has some kind of crisis at work that requires his full attention. When
Pat gets done, he will post the slides, though we currently do
not have a site because diameter.org went down due to @Home's
demise. Perhaps Alcatel would like to volunteer a publically accessable
place
until we find another home?

>   My point is very simple. Here is someone who was brought on board to
> cochair a WG in order to help in the protocol assessment of paging
> proposals. This person has very many opinions. He makes sure to give a
reply
> to any message posted on the mailing list.
>   However this same person somehow forgets to make any opinion on one
the
> paging proposals jeopardizing the assessment process.
>   He seems to admit this and asks some way out on the one hand and he
> insists on the false conclusion of the assessment on the other hand.
>   The above is too good to believe. What do you think?
>

Behcet, I haven't a clue about what you are talking about here. These
sound to me like some kind of accusation against me, though I cannot
be sure. If that is the case, then I suggest that you come right out
and make the accusation and I will deal with it.

>   The fact is that the assesment process is wrong. All IETF WGs
receive
> several protocol proposals, Seamoby is not the only WG. However the
process
> used by Seamoby is unique to Seamoby.
>   Jim, I am ready to discuss this issue over the phone. My phone
number is
> below. Feel free to call me or give your phone number I am going to
call
> you.
>
>

The  very same assessment process was used by the AAA group. You can
send email to Bernard Abboba if you care to confirm this. However, the
outcome was different. In that case, one of the protocol
proposals exhibited considerably more implementation and
design maturity than the others and met the requirements more
completely, and so the results of
the assessment team were definitive: that proposal was
selected.

At the request of Yoshi and Jari, I have written up a
description of the decision process we used, it is
currently under review by Pat and Allision for
inclusion into the assessment draft. The WG
will get to comment when the draft
goes through WG last call again. The difference
with the AAA group is that the assessment process
in Seamoby resulted in an indeterminate result.
The assessment team did not recommend one
of the protocol proposals as the basis for harmonization, they
recommended only that either harmonization begin
or the authors go through another round of design
work.

The working group co-chairs decided against the
latter, and decided to select one protocol
proposal as the basis for harmonization, subject
to WG concensus, of course. This was done,
the text to be included in the document
will explain the decision process. There
was a presentation at the WG meeting,
comments and concerns of the protocol
authors were duely noted.
If what you are complaining about is
that the WG chairs basically made
a judgement call about which protocol
proposal should be selected, then
I'm sorry to say that this is certainly
within the duties of IETF WG chairs,
provided the chairs abide by
WG concensus. I believe
we have concensus on how to proceed,
since you seem to be the only person
who continues to complain.

Behcet, as I have continued to say, your
team had positive contributions and I
would appreciate if you would bring
them to the list instead of making veiled
and unveiled accusations about the decision
process. The other protocol proposal
authors seem to be willing to work together
with Marco and the WG, even though they are probably
no more happy than you are that their
proposals were not selected as the
basis for harmonization.

            jak





_______________________________________________
Seamoby mailing list
Seamoby@ietf.org
https://www1.ietf.org/mailman/listinfo/seamoby