Re: [Seamoby] IP Paging ]Framework discussion
"James Kempf" <kempf@docomolabs-usa.com> Thu, 03 January 2002 18:58 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 NAA08235 for <seamoby-archive@odin.ietf.org>; Thu, 3 Jan 2002 13:58:58 -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 NAA13719; Thu, 3 Jan 2002 13:47:23 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA13690 for <seamoby@optimus.ietf.org>; Thu, 3 Jan 2002 13:47:21 -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 NAA08018 for <seamoby@ietf.org>; Thu, 3 Jan 2002 13:47:18 -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 g03IknS02927; Thu, 3 Jan 2002 10:46:49 -0800 (PST)
Message-ID: <010e01c19486$c7bcc410$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> <007701c1947e$2ecb7380$7e6015ac@T23KEMPF> <3C34A514.2F9E3576@alcatel.com>
Subject: Re: [Seamoby] IP Paging ]Framework discussion
Date: Thu, 03 Jan 2002 10:45:14 -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
Hi Behcet, > I had suggested a civilized phone call to resolve or at least talk about > the issues. Reading your mail I conclude you do not wish to talk over these > things, but rather resort to written communication. > I have no personal accusations on any body. I am a professional, I am not > here to deal with persons. There are technical issues, and if I have > technical points to make, I believe I am entitled to my opinion as someone > who has been working on IP Paging issues for sometime probably longer than > many in the WG. This is good to know. If you have technical issues, please by all means post them. > It is the belief of our team that the renker draft is technically not the > right one as a base document. It is our belief that the base document should > have been dressed bottom up by getting consensus on the technical issues > starting with the architecture. As I mentioned to you in previous email, the WG already has agreed to the functional architecture, it is described in RFC 3154. There is still a need for a network architecture, draft-renker has a proposal that the WG will use as a start. If you have specific technical issues with the network architecture in draft-renker, then please post them to the list, and Marco and the WG can begin to address them. > Therefore it really does not matter if this > or that draft coauthor agrees to work on a wrong document. What matters is > the technical issues because we are talking about a protocol, not a > nontechnical issue. Great! > We may continue to work on our two protocol and one API drafts and if we > somehow come up with enhanced versions we wll share with IETF by submitting > them as I-Ds. Therefore we are unable to participate in the process you > prescribed in your email and this means of course the new draft makers > should not count on our drafts. You are certainly free to submit your documents to the IESG as informational documents. I am sorry to hear that you don't want to participate in the WG design on paging, we will certainly miss your expertise. > As a final remark, if one of 5 candidate proposals is eliminated by giving > no opinion even though some aspects of this one draft are used as arguments > for eliminating some other drafts, this execution of the agreed upon > assessment process has unfortunately been buggy. > Well, my semantic analyzer comes up indeterminate on this statement, so I guess I will have to refrain from comment. jak _______________________________________________ Seamoby mailing list Seamoby@ietf.org https://www1.ietf.org/mailman/listinfo/seamoby
- [Seamoby] IP Paging ]Framework discussion Behcet Sarikaya
- Re: [Seamoby] IP Paging ]Framework discussion James Kempf
- Re: [Seamoby] IP Paging ]Framework discussion Behcet Sarikaya
- Re: [Seamoby] IP Paging ]Framework discussion James Kempf
- Re: [Seamoby] IP Paging ]Framework discussion Behcet Sarikaya
- Re: [Seamoby] IP Paging ]Framework discussion James Kempf
- Re: [Seamoby] IP Paging ]Framework discussion Behcet Sarikaya
- Re: [Seamoby] IP Paging ]Framework discussion James Kempf
- Re: [Seamoby] IP Paging ]Framework discussion Behcet Sarikaya
- Re: [Seamoby] IP Paging ]Framework discussion David Frascone
- Re: [Seamoby] IP Paging ]Framework discussion James Kempf
- Re: [Seamoby] IP Paging ]Framework discussion James Kempf
- [Seamoby] IP Paging ]Framework discussion Behcet Sarikaya
- Re: [Seamoby] IP Paging ]Framework discussion Behcet Sarikaya
- Re: [Seamoby] IP Paging ]Framework discussion Behcet Sarikaya
- Re: [Seamoby] IP Paging ]Framework discussion James Kempf
- Re: [Seamoby] IP Paging ]Framework discussion Marcus Brunner
- Re: [Seamoby] IP Paging ]Framework discussion Scott Bradner
- Re: [Seamoby] IP Paging ]Framework discussion Scott Bradner