Re: [Seamoby] Re: IP Paging Protocol
"James Kempf" <kempf@docomolabs-usa.com> Wed, 16 January 2002 17:28 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 MAA14961 for <seamoby-archive@odin.ietf.org>; Wed, 16 Jan 2002 12:28:35 -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 MAA10416; Wed, 16 Jan 2002 12:07:33 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA10385 for <seamoby@optimus.ietf.org>; Wed, 16 Jan 2002 12:07:31 -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 MAA14240 for <seamoby@ietf.org>; Wed, 16 Jan 2002 12:07:27 -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 g0GH6wS08355; Wed, 16 Jan 2002 09:06:58 -0800 (PST)
Message-ID: <000d01c19eaf$fbe04950$7e6015ac@T23KEMPF>
From: James Kempf <kempf@docomolabs-usa.com>
To: Behcet Sarikaya <behcet.sarikaya@alcatel.com>, seamoby@ietf.org
References: <748E8123D183394982E32A511DB3E73610B0B9@daebe005.NOE.Nokia.com> <3C433991.2090906@alcatel.com> <01fe01c19d3d$32563180$7e6015ac@T23KEMPF> <3C437674.F7603259@iprg.nokia.com> <003801c19de9$551e6280$7e6015ac@T23KEMPF> <3C44CABD.4949D8D2@alcatel.com>
Subject: Re: [Seamoby] Re: IP Paging Protocol
Date: Wed, 16 Jan 2002 09:05:22 -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
So, what is the difference between:
a) Forming an open design team and anyone in the working group
having the right to participate with Marco as the editor of the
document,
and:
b) The situation we are in now?
Why should the design team be restricted to authors of the
existing protocols?
jak
----- Original Message -----
From: "Behcet Sarikaya" <behcet.sarikaya@alcatel.com>
To: <seamoby@ietf.org>
Sent: Tuesday, January 15, 2002 4:35 PM
Subject: Re: [Seamoby] Re: IP Paging Protocol
> I think that WG chairs should not expect WG members to react more than
> what we observed so far. I reacted and pointed to one important
problem
> during the meeting and continued to argue on the mailing list. The
other
> WG members also have spoken out.
> WG members are kind people, we do not shout and leave the meeting
room
> slamming the door.
> WG members prefer to kindly indicate the peaceful solution which is
two
> fold, never again make such assessment irregularities and
> >We believe that the process of creating an IP paging protocol can be
> >> substantially improved, and that the establishment in Seamoby of a
> >> design team comprising the authors of the current proposal and few
> >> other relevant parties is the only realistic solution (as it has
> >> already happened in other IETF WGs).
>
> Regards,
>
> James Kempf wrote:
>
> >
> >
> >
> > If there was an outcry on the list from others, I would be more
> > inclined to view the complaints seriously. In the past,
> > the Seamoby list has not been short of people who
> > were ready to jump out at the first sign of a technical
> > controversy and express their opinions. I have not
> > seen a single one of those people, either in SLC
> > or on the list, stand up publically and say that they did
> > not agree with the decision.
> >
> > I've already agreed that the the decision process
> > by which the selection was made was not
> > transparent. I have some text that I have
> > written which I hope will render more
> > transparency to the process, but I have
> > not yet been able to get a time to
> > talk with Pat and Allision about it.
> > If you can just be patient, I will
> > post the text as soon as we have
> > had a chance to review it. Let's see if there
> > are any complaints from neutral
> > sources about the decision after
> > I've posted that text.
> >
> > jak
> >
> > _______________________________________________
> > --
>
> Behcet
>
>
> _______________________________________________
> Seamoby mailing list
> Seamoby@ietf.org
> https://www1.ietf.org/mailman/listinfo/seamoby
>
_______________________________________________
Seamoby mailing list
Seamoby@ietf.org
https://www1.ietf.org/mailman/listinfo/seamoby
- [Seamoby] Re: IP Paging Protocol Behcet Sarikaya
- Re: [Seamoby] Re: IP Paging Protocol James Kempf
- Re: [Seamoby] Re: IP Paging Protocol Vijay Devarapalli
- Re: [Seamoby] Re: IP Paging Protocol James Kempf
- Re: [Seamoby] Re: IP Paging Protocoly Yoshihiro Ohba
- Re: [Seamoby] Re: IP Paging Protocoly James Kempf
- Re: [Seamoby] Re: IP Paging Protocol Behcet Sarikaya
- Re: [Seamoby] Re: IP Paging Protocol James Kempf
- Re: [Seamoby] Re: IP Paging Protocol Behcet Sarikaya
- Re: [Seamoby] Re: IP Paging Protocol James Kempf
- Re: [Seamoby] Re: IP Paging Protocol Behcet Sarikaya
- Re: [Seamoby] Re: IP Paging Protocol James Kempf