Clarification to second bullet in 4.2.2
4] Clarify bullet 2 in section 4.2.2
(Triggers shall NOT have unbounded state requirements) [Vivek]
In general each individual event shall be discrete in nature. Each
individual event shall be interpreted on it's own in entirety without
any dependence on any other past or future events.
Predictive events express likelihood of change in future. These events
shall have a bounded timeline associated with them during which they are
expected to cover. Predictive events can be retracted if the expected
event does not occur within the specified timeline.
Best Regards,
-Vivek
|-----Original Message-----
|From: owner-stds-802-21@listserv.ieee.org [mailto:owner-stds-802-
|21@listserv.ieee.org] On Behalf Of Gupta, Vivek G
|Sent: Thursday, September 02, 2004 6:01 AM
|To: STDS-802-21@listserv.ieee.org
|Subject: RE: Updated Requirements doc and Action Items
|
|802.21 Folks,
|
|The minutes of last telecon on Aug 25 from Xiaoyu Liu have been posted
|on the reflector. Below is a list of pending Action Items:
|
|1] Resolve definitions of application classes in section 3.2 on
|reflector [Yogesh]
|2] Resolve requirements for power management on reflector
|[Yogesh/Hong/Vivek]
|3] Submit text to distinguish definition of L2 and L2.5 between 802 and
|cellular technologies in glossary [Yogesh]
|4] Clarify bullet 2 in section 4.2.2 (Triggers shall NOT have unbounded
|state requirements) [Vivek]
|5] Update text for section 3.3 (QoS) based on discussions in last
|telecon (Aug 25) and send updated text [Peretz]
|6] An exhaustive list of references has been submitted by
|Eric/Yogesh/Peretz and some others. We should spend some time on how we
|want to organize this.
|
|
|Comments:
|All of Yogesh's comments have been resolved.
|Listed below are some long pending comments from Reijo and Eric and
some
|new text for section 6 from Reijo and Peretz. Eric has submitted some
|new comments for section 6 as well. All of the relevant documents here
|have been posted on the reflector.
|
|We expect today's telecon to be the last one before the Berlin meeting.
|An updated Requirements doc (rev 10) shall be posted shortly after
|today's teleconference.
|
|Best Regards
|-Vivek
|
||-----Original Message-----
||From: owner-stds-802-21@listserv.ieee.org
||[mailto:owner-stds-802-21@listserv.ieee.org] On Behalf Of Gupta, Vivek
|G
||Sent: Tuesday, August 17, 2004 6:22 AM
||To: ajayrajkumar@lucent.com; STDS-802-21@listserv.ieee.org
||Subject: Updated Requirements doc and Action Items
||
||Hello 802.21 folks,
||
||An updated version of Requirements draft (version 9) is about to be
||posted on the 802.21 web site under September 2004. This contains all
||agreed upon changes from last teleconference on 8/12. Also available
||there are the minutes of last teleconference from Xiaoyu Liu.
||
||
||The following two comments from the Unresolved_Comments list remain
||unresolved after the telecon on 8/12:
||
||1] Section 5.2 (Reijo)
||Comment 1 on chapter 5.2 on rev 7 requirement document:
||The following text:
||"The 802.21 standard shall facilitate handover scenarios related to
||WLAN-cellular inter-working as specified by Scenarios 4 and 5 in 3GPP
||standard."
||Should be either removed, or rewritten in the following way:
||"The 802.21 standard shall facilitate service continuity and seamless
||operation in the handover process between the IEEE 802 and Non-IEEE
||Cellular
||systems."
||This text would consider also other than WLAN systems (802.11?) from
|802
||and have the requirement in clear text what the scenarios from 3GPP
are
||aiming at. Then it is up to the proposals to come out with a solution
||how this could be achieved. As mentioned before there is very little
||information available about the details of the scenarios 4 and 5 from
||3GPP side, so it is not possible to evaluate the proposals on this
||requirement as it is written now in the requirement spec.
||
||2] Section 6 Reference Model (Eric)
|| It is not clear from the document where an input to any particular
||layer comes from and which direction (up or down) the output is
|directed
||at
||
||
||In addition there was new text submitted for section 6.2 by Reijo and
||Peretz.
||Please refer to following documents on 802.21 website under September
||2004.
||a]21-04-0087-08-0000-Draft_Technical_Requirements_seesta.doc and
||b] Draft_Technical_Requirements_section6_2_pfe.doc.
||
||Additional new comments were submitted by Yogesh on 8/11. Please refer
||to:
||Unresolved_Comments_9Aug04_Yogesh_Input.
||
||
||Below are the Action items along with dates when they were assigned:
||1] Resolve definitions of application classes in section 3.2 [Yogesh,
||8/9]
||2] Resolve definition of active and deep power management states in
||section 3.7 [Yogesh/Peretz 8/12]
||
||3] "The standard shall define generic mechanisms for providing layer 1
||(PHY), layer 2 (MAC), and layer 2.5 (Mobility Management) information
|to
||higher layer entity such as Mobile IP."
||Provide alternative text for above. [Cheng Hong/Eric 8/12] (Done)
||
||4] Submit list of normative references from IETF {[Eric 8/12]
||5] Submit list of references from IEEE [Yogesh 8/12]
||6] Submit list of references from 3GPP/3GPP2 [Yogesh/Peretz 8/12]
||7] Submit text to distinguish definition of L2 and L2.5 between 802
and
||cellular technologies in glossary [Yogesh 8/12]
||
||All the documents referenced above have been forwarded to the chair so
||that they can be posted on the 802.21 website under September 2004.
||
||Best Regards
||-Vivek