RE: [Seamoby] Reminder: Last Call for CT Reqirements Ends Wed.

Nakhjiri Madjid-MNAKHJI1 <Madjid.Nakhjiri@motorola.com> Tue, 24 September 2002 16:19 UTC

Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA04313 for <seamoby-archive@lists.ietf.org>; Tue, 24 Sep 2002 12:19:04 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8OGJsv12166; Tue, 24 Sep 2002 12:19:54 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8OGItv12126 for <seamoby@optimus.ietf.org>; Tue, 24 Sep 2002 12:18:55 -0400
Received: from motgate3.mot.com (motgate3.mot.com [144.189.100.103]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA04259 for <seamoby@ietf.org>; Tue, 24 Sep 2002 12:17:00 -0400 (EDT)
Received: [from pobox.mot.com (pobox.mot.com [129.188.137.100]) by motgate3.mot.com (motgate3 2.1) with ESMTP id JAA00354 for <seamoby@ietf.org>; Tue, 24 Sep 2002 09:16:42 -0700 (MST)]
Received: [from il27exb01.cig.mot.com (il27exb01.cig.mot.com [136.182.15.100]) by pobox.mot.com (MOT-pobox 2.0) with ESMTP id JAA10964 for <seamoby@ietf.org>; Tue, 24 Sep 2002 09:18:50 -0700 (MST)]
Received: by il27exb01.cig.mot.com with Internet Mail Service (5.5.2654.52) id <R80728CY>; Tue, 24 Sep 2002 11:18:50 -0500
Message-ID: <35DBB8B7AC89D4118E98009027B1009B08AD58AB@IL27EXM10.cig.mot.com>
From: Nakhjiri Madjid-MNAKHJI1 <Madjid.Nakhjiri@motorola.com>
To: 'James Kempf' <kempf@docomolabs-usa.com>, seamoby@ietf.org
Subject: RE: [Seamoby] Reminder: Last Call for CT Reqirements Ends Wed.
Date: Tue, 24 Sep 2002 11:18:47 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2654.52)
Content-Type: text/plain; charset="iso-8859-1"
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-BeenThere: seamoby@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>, <mailto:seamoby-request@ietf.org?subject=unsubscribe>
List-Id: Context Transfer, Handoff Candidate Discovery, and Dormant Mode Host Alerting <seamoby.ietf.org>
List-Post: <mailto:seamoby@ietf.org>
List-Help: <mailto:seamoby-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>, <mailto:seamoby-request@ietf.org?subject=subscribe>

Reading from 2119

   SHOULD   This word, or the adjective "RECOMMENDED", mean that there
   may exist valid reasons in particular circumstances to ignore a
   particular item, but the full implications must be understood and
   carefully weighed before choosing a different course

   MAY   This word, or the adjective "OPTIONAL", mean that an item is
   truly optional.  One vendor may choose to include the item because a
   particular marketplace requires it or because the vendor feels that
   it enhances the product while another vendor may omit the same item.
   ......
   

It means you need to fully understand the implication of not supporting
a SHOULD item, before you exclude it. On the other hand if it is something
that may be useful in some cases, a may is more appropriate. 

Looking at 4.6, I would say one-to-many context transfer is not
an item that its "not use" needs to be investigated, but its "use" 
needs careful considerations. 
Example:
If you are dealing with dynamic context that is affected by flow of data
at a specific AR (header compression, or measurement based QoS context)
sending the context through a whole bunch of ARs that may not even see
the data causes serious synchronization issues for such context.

Based on this counter-example:
I say this requirement should be changed to "may" unless it is stated that
SHOULD only applies to the context whose value is not affected by data flow.

Madjid

-----Original Message-----
From: James Kempf [mailto:kempf@docomolabs-usa.com]
Sent: Monday, September 23, 2002 11:24 AM
To: seamoby@ietf.org
Subject: [Seamoby] Reminder: Last Call for CT Reqirements Ends Wed.


A reminder: last call for the CT requirements document
(draft-ietf-seamoby-ct-reqs-04.txt) concludes on Wed. Sept 25. So far, we have
not received any comments. If you have any comments, please send them to the
list by that date.

            jak

_______________________________________________
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