Re: [Seamoby] Paging Protocol Decision Description
Rajeev Koodli <rajeev@iprg.nokia.com> Thu, 17 January 2002 23:45 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 SAA15704 for <seamoby-archive@odin.ietf.org>; Thu, 17 Jan 2002 18:45:19 -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 SAA29764; Thu, 17 Jan 2002 18:34:55 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA29733 for <seamoby@optimus.ietf.org>; Thu, 17 Jan 2002 18:34:53 -0500 (EST)
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA15579 for <seamoby@ietf.org>; Thu, 17 Jan 2002 18:34:48 -0500 (EST)
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69]) by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id PAA23775; Thu, 17 Jan 2002 15:34:19 -0800 (PST)
Received: (from root@localhost) by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id g0HNYIr14035; Thu, 17 Jan 2002 15:34:18 -0800
X-mProtect: Thu, 17 Jan 2002 15:34:18 -0800 Nokia Silicon Valley Messaging Protection
Received: from rajeev.iprg.nokia.com (205.226.2.90, claiming to be "iprg.nokia.com") by darkstar.iprg.nokia.com smtpd6eyoXO; Thu, 17 Jan 2002 15:34:17 PST
Message-ID: <3C475F7A.9E88C7D4@iprg.nokia.com>
Date: Thu, 17 Jan 2002 15:34:18 -0800
From: Rajeev Koodli <rajeev@iprg.nokia.com>
Organization: Nokia Research Center
X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: "Chitrapu, Prabhakar R" <Prabhakar.Chitrapu@interdigital.com>
CC: seamoby@ietf.org
Subject: Re: [Seamoby] Paging Protocol Decision Description
References: <A1170612471BD21185B90008C7FA0A0D02703CC0@idcpa4.pa.interdigital.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
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
Hello Prabhakar, "Chitrapu, Prabhakar R" wrote: > Hi All: > > I would like to make a clarification on the scoring scheme and the > interpretation of the scores (in particular, high vs low values). > Unfortunately, I do not have those emails that were talking about the > interpretation of the scores, so that I am replying to this somewhat > randomly picked one on this topic. > > I think that there is an inaccuracy in thinking that a higher aggregate > score is 'better' (in the present context). Recall that a score of 1 was > given if a requirement was not met and a score of 4 was given if the > requirement was met, so that indeed the higher score is 'better'. However, > score 2 indicated 'under-specification', whereas score 3 indicated > 'over-specification'. Here, I am not sure if I can say that > 'over-specification' is 'better' than 'under-specification' or vice versa. > Therefore, I think that it is incorrect to interpret a higher aggregate > score as necessarily denoting a 'better' protocol. > It does appear from the text (from James) below that "over-specification" (which implies a higher score) was considered better, at least in one of the important areas. For what it is worth.. Regards, -Rajeev > mobility protocols. Draft-renker was judged by the assessment team to > be overspecific in these areas, in the sense that it contained two > modes, > explicit mode and implicit mode, depending on whether Mobile IP was > supported > or not. However, considering the relatively immature state of the paging > protocol design, the decision team felt that providing the working group > with choices, where the benefits and drawbacks of each choice could be > clearly weighed, was preferable to providing a fixed decision, so > draft-renker was judged to be better in this regard. > > Please note that my comment is related only to score interpretation and not > to the much bigger topic of the assessment process and its results. > However, I do sincerely hope that this discussion will soon be settled > amicably among all of us! > > Best regards > Prabhakar. > -------------------- > Prabhakar Chitrapu > InterDigital Communications Corp. > > > _______________________________________________ > 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
- Re: [Seamoby] Paging Protocol Decision Description Behcet Sarikaya
- RE: [Seamoby] Paging Protocol Decision Description Pat R. Calhoun
- Re: [Seamoby] Paging Protocol Decision Description Cedric Westphal
- RE: [Seamoby] Paging Protocol Decision Description Pat R. Calhoun
- RE: [Seamoby] Paging Protocol Decision Description Pat R. Calhoun
- RE: [Seamoby] Paging Protocol Decision Description Hesham Soliman (ERA)
- [Seamoby] Paging Protocol Decision Description James Kempf
- Re: [Seamoby] Paging Protocol Decision Description Behcet Sarikaya
- Re: [Seamoby] Paging Protocol Decision Description James Kempf
- Re: [Seamoby] Paging Protocol Decision Description Behcet Sarikaya
- Re: [Seamoby] Paging Protocol Decision Description James Kempf
- RE: [Seamoby] Paging Protocol Decision Description Pat R. Calhoun
- Re: [Seamoby] Paging Protocol Decision Description James Kempf
- Re: [Seamoby] Paging Protocol Decision Description James Kempf
- Re: [Seamoby] Paging Protocol Decision Description Cedric Westphal
- Re: [Seamoby] Paging Protocol Decision Description James Kempf
- Re: [Seamoby] Paging Protocol Decision Description James Kempf
- Re: [Seamoby] Paging Protocol Decision Description Behcet Sarikaya
- Re: [Seamoby] Paging Protocol Decision Description Cedric Westphal
- Re: [Seamoby] Paging Protocol Decision Description Vijay Devarapalli
- Re: [Seamoby] Paging Protocol Decision Description James Kempf
- RE: [Seamoby] Paging Protocol Decision Description Nakhjiri Madjid-MNAKHJI1
- Re: [Seamoby] Paging Protocol Decision Description Rajeev Koodli
- RE: [Seamoby] Paging Protocol Decision Description Nakhjiri Madjid-MNAKHJI1
- Re: [Seamoby] Paging Protocol Decision Description Muhammad Jaseemuddin
- Re: [Seamoby] Paging Protocol Decision Description Behcet Sarikaya
- Re: [Seamoby] Paging Protocol Decision Description Behcet Sarikaya
- Re: [Seamoby] Paging Protocol Decision Description James Kempf
- Re: [Seamoby] Paging Protocol Decision Description Vijay Devarapalli
- RE: [Seamoby] Paging Protocol Decision Description Chitrapu, Prabhakar R
- RE: [Seamoby] Paging Protocol Decision Description Nakhjiri Madjid-MNAKHJI1
- RE: [Seamoby] Paging Protocol Decision Description Pat R. Calhoun
- Re: [Seamoby] Paging Protocol Decision Description Rajeev Koodli
- Re: [Seamoby] Paging Protocol Decision Description Behcet Sarikaya
- RE: [Seamoby] Paging Protocol Decision Description Hesham Soliman (ERA)
- RE: [Seamoby] Paging Protocol Decision Description Nakhjiri Madjid-MNAKHJI1