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

Madjid has proposed changing requirement 4.6 from a SHOULD to a MAY. If there
are no comments or further discussion, I'd like to propose to Gary to make the
change and reissue the CT requirements draft immediately, and that we close Last
Call today as planned so that we can start the IESG working on them.

            jak

----- Original Message -----
From: "Nakhjiri Madjid-MNAKHJI1" <Madjid.Nakhjiri@motorola.com>
To: "'James Kempf'" <kempf@docomolabs-usa.com>; <seamoby@ietf.org>
Sent: Tuesday, September 24, 2002 9:18 AM
Subject: RE: [Seamoby] Reminder: Last Call for CT Reqirements Ends Wed.

> 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