Re: [Seamoby] Moving forward with paging
Behcet Sarikaya <behcet.sarikaya@alcatel.com> Thu, 07 February 2002 21:20 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 QAA10177 for <seamoby-archive@odin.ietf.org>; Thu, 7 Feb 2002 16:20:53 -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 PAA16699; Thu, 7 Feb 2002 15:56:43 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA16672 for <seamoby@ns.ietf.org>; Thu, 7 Feb 2002 15:56:41 -0500 (EST)
Received: from netmail2.alcatel.com (netmail2.alcatel.com [128.251.168.51]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09622 for <seamoby@ietf.org>; Thu, 7 Feb 2002 15:56:39 -0500 (EST)
Received: from auds952.usa.alcatel.com (auds952.usa.alcatel.com [143.209.238.7]) by netmail2.alcatel.com (8.9.1/8.9.1) with ESMTP id OAA24043 for <seamoby@ietf.org>; Thu, 7 Feb 2002 14:56:12 -0600 (CST)
Received: from alcatel.com (localhost [127.0.0.1]) by auds952.usa.alcatel.com (8.10.2/8.10.2) with ESMTP id g17KuBg02051 for <seamoby@ietf.org>; Thu, 7 Feb 2002 14:56:11 -0600 (CST)
Message-ID: <3C62E9D9.4080109@alcatel.com>
Date: Thu, 07 Feb 2002 14:55:53 -0600
From: Behcet Sarikaya <behcet.sarikaya@alcatel.com>
Organization: Alcatel USA
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:0.9.4) Gecko/20011019 Netscape6/6.2
X-Accept-Language: en-us
MIME-Version: 1.0
To: seamoby@ietf.org
Subject: Re: [Seamoby] Moving forward with paging
References: <DC6C13921CCAFB49BCB8461164A3F4E38D2569@EXCHSRV.stormventures.com>
Content-Type: multipart/alternative; boundary="------------030909010704040606040000"
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
Dear All, My comments follow. If these changes are incorporated, I am OK with this draft going for the last call. Comments on the assessment draft: On page 2: Of these, [6] and [7] were from the same team and were treated as one contribution for purposes of assessment. Action: Drop this sentence, since 6 and 7 define different protocols and they were evaluated separately in 3.3 and 3.4. Page 4 draft-renker-paging-ipv6-01.txt Unacceptable Requirements Match: 4.4, 4.6, 4.19, 4.20, 4.21 Action: add 4.7 to the list. Page 5 Requirement 4.7: Independence of Mobility Protocol The independence of mobility protocol is valid for "explicit" case only. The design specifies two separate protocols, one for Mobile IP and one without Mobile IP. Even implicit mode requires HA, i.e. Mobile IP, see the figure on page 22 of draft-renker-paging-ipv6-01.txt. Action: replace the text above with this: The design basically specifies one protocol for Mobile IP home agent based paging. Page 13 Draft-sarikaya was ruled out because it is based on a protocol that is currently under evaluation in another working group, setting up an unacceptable dependency between the Seamoby paging protocol design and the other working group's process. Action: add the following to this. Moreover draft-sarikaya is not the only draft that has some dependency on HMIPv6. Draft-koodli also has included the mapping of their protocol to HMIPv6. Page 13 While the assessment of draft-guri was positive, draft-guri is explicitly concerned with utilizing Layer 2 support for paging, and was therefore not sufficiently broad enough as a base for IP paging. Action: Replace by: The assessment of draft-guri was positive. Page 13 and 14. Last 4 paragraphs starting with: Of these, both draft-renker and draft-ohba provided adequate support for the first two, independence of mobility protocol and support for existing mobility protocols. Until 5.0 Acknowledgements Action: Drop completely. The reasons are the following: 1. Some comments on the "advantages:" of draft-renker may be taken to mean that: IETF is soliciting the draft authors to have a long reference list of the published literature including conference/journal papers, otherwise you will be judged out not knowing the field The fact is that the text and the related references of draft-renker fail to identify clearly which is Layer 2 related (there is a very rich literature on the paging in cellular networks which is called Layer 2 paging) and which is Layer 3 related and some key references on Layer 3 paging are missing. Action. Add the following text. As the response to the survey sent out to the mailing list indicated, nobody is doing product in this area in the near future, so we have some time to get this right. The Working Group wants a design that will last, like Internet routing has, and fit properly into the Internet architecture, since paging will be a key component of the future all-IP wireless networks. This is naturally going to require some time. Page 15 The acknowledgements. This is the first time I see the authors acknowledging themselves. It is unheard of. Action. Drop section 5.0. Pat R. Calhoun wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Thanks for the feedback. However, what would be much more useful is > to provide comments on the assessment draft. If you believe that the > technical assessment of a particular draft is incorrect, please make > that statement. Perhaps the new text could justify the selection of > another draft as the starting point. > > PatC > Regards, -- Behcet
- [Seamoby] Moving forward with paging Pat R. Calhoun
- RE: [Seamoby] Moving forward with paging john.loughney
- Re: [Seamoby] Moving forward with paging Behcet Sarikaya
- RE: [Seamoby] Moving forward with paging Pat R. Calhoun
- Re: [Seamoby] Moving forward with paging Marco Liebsch
- Re: [Seamoby] Moving forward with paging Behcet Sarikaya
- Re: [Seamoby] Moving forward with paging Marco Liebsch
- RE: [Seamoby] Moving forward with paging Pat R. Calhoun
- Re: [Seamoby] Moving forward with paging Behcet Sarikaya
- RE: [Seamoby] Moving forward with paging Pat R. Calhoun
- Re: [Seamoby] Moving forward with paging Marco Liebsch
- Re: [Seamoby] Moving forward with paging Behcet Sarikaya
- Re: [Seamoby] Moving forward with paging Behcet Sarikaya
- Re: [Seamoby] Moving forward with paging James Kempf
- Re: [Seamoby] Moving forward with paging Behcet Sarikaya
- Re: [Seamoby] Moving forward with paging James Kempf
- Re: [Seamoby] Moving forward with paging Behcet Sarikaya
- RE: [Seamoby] Moving forward with paging Pat R. Calhoun
- Re: [Seamoby] Moving forward with paging James Kempf
- Re: [Seamoby] Moving forward with paging James Kempf
- Re: [Seamoby] Moving forward with paging Behcet Sarikaya
- Re: [Seamoby] Moving forward with paging James Kempf
- Re: [Seamoby] Moving forward with paging Yoshihiro Ohba
- Re: [Seamoby] Moving forward with paging Marco Liebsch
- Re: [Seamoby] Moving forward with paging Behcet Sarikaya
- RE: [Seamoby] Moving forward with paging Pat R. Calhoun
- Re: [Seamoby] Moving forward with paging Marco Liebsch
- Re: [Seamoby] Moving forward with paging Yoshihiro Ohba
- Re: [Seamoby] Moving forward with paging James Kempf
- Re: [Seamoby] Moving forward with paging James Kempf
- Re: [Seamoby] Moving forward with paging Behcet Sarikaya
- Re: [Seamoby] Moving forward with paging Behcet Sarikaya
- RE: [Seamoby] Moving forward with paging Pat R. Calhoun
- Re: [Seamoby] Moving forward with paging James Kempf
- Re: [Seamoby] Moving forward with paging Marco Liebsch
- Re: [Seamoby] Moving forward with paging Behcet Sarikaya
- Re: [Seamoby] Moving forward with paging -resendiā¦ Behcet Sarikaya
- RE: [Seamoby] Moving forward with paging Pat R. Calhoun
- Re: [Seamoby] Moving forward with paging Behcet Sarikaya
- Re: [Seamoby] Moving forward with paging Behcet Sarikaya
- RE: [Seamoby] Moving forward with paging rene.purnadi