[STDS-802-16] [NETMAN][LM] Results of vote, updated list of participants and ca ll for contributions
Hello,
1. Results of voting on Question #1.
------------ Question #1 was:
What will be the scope of Ad Hoc in terms of sections in IEEE P802.16e/D4?
------- Resolution recommended by Chair
Limit the scope to D.1.1, D.1.2 ["Backbone network HO procedures"] and D2
["Inter-base station message formats"].
This does not preclude from adding new messages.
------------ Only 3 votes were submitted:
./Dinesh - Y
Nikhil Goel - Y
Jung Je Son - Y
Nobody objected, so resolution accepted.
2. Call for contributions
------------------------------------------------------------------
Please submit your contributions regarding specific messages mentioned in
Addendum D.
Deadline for contributions 2-Mar-2005.
Please note that 802.16g Baseline Document defines Network Reference Model
[14.4.1, Fig. 1]
that includes communication [between two BSs] over Network Control and
Management System Abstraction.
That entity may simply forward a message from one BS to another, but may
also receive message[s] of one
type and issue message[s] of another type. So our definitions should be
suitable for situation when
one BS transmits to [receives from] certain node N in the network which is
not necessary a BS.
For your convenience, the following is list of messages:
D.2.2 I-am-host-of message
D.2.4. MSS-info-request message
D.2.4 MSS-info-response message
D.2.5 HO-pre-notification message
D.2.6 HO-pre-notification-response message
D.2.7 HO-confirm message
D.2.11 HO-withdraw message
D.2.8 Paging-group-action message
D.2.9 Paging-announce message
D.2.10 MSS Ping pong Notification message
D.2.12 BS-info-request message
D.2.13 BS-info-response message
D.2.14 MSS Security Context Transfer Request
D.2.15 MSS Security Context Transfer Response
D.2.17 MSS-Data-Forwarding Message
D.2.18 Stop-Data-Forwarding Message
You may suggest specific text for Baseline document or just to write what
you think we have to do with each message.
New messages may also be proposed.
3. Updated list of Ad Hoc Group members
------------------------------------------------
1. Vladimir Yanover - Chair - vladimir.yanover@alvarion.com
2. Lin Zhibin - linzhibin@huawei.com
3. Aeran Youn - aryoun@lge.com
4. Joey Chou - joey.chou@intel.com
5. David Maez - dmaez@navini.com
6. Dinesh - dnambisan@proxim.com
7. Jeff Mandin - jmandin@streetwaves-networks.com
8. Jin Lee - jins978@lge.com
9. Lei Wang - LWang@cygnuscom.com
10. Mary Chion - mchion@ztesandiego.com
11. Raja Banerjea - RBanerjea@proxim.com
12. Rajesh Bhalla - rabhalla@ztesandiego.com
13. Greg Schumacher - gregory.schumacher@nextel.com
14. Torsten Fahldieck - torsten.fahldieck@alcatel.de
15. Weidong Yang - weidong_yang@navini.com
16. Yongseok Jin - jayjay@lge.com
17. Yongwon Kwak - yongwon@lge.com
18. Beomjoon Kim - beom@lge.com
19. Ronny (Yong-Ho) Kim - ronnykim@lge.com
20. Kiseon Ryu - ksryu@lge.com
21. Jung Je Son - jungje.son@samsung.com
22. Nikhil Goel - nikhil.goel@nex-G.com
23. Zion Hadad - zionh@runcom.co.il
24. Itzik Kitroser - itzikk@runcom.co.il
25. Janice Wunsch - wunsch@lucent.com
26. Prakash Iyer - prakash.iyer@intel.com
27. Sanjay Bakshi - sanjay.bakshi@intel.com
28. Lalit Kotecha - lalit.kotecha@verizonwireless.com
29. John Chan - jchan@wilan.com
30. Wujianjun - wujianjun@huawei.com
31. Moo Ryong Jeong - jeong@docomolabs-usa.com
32. Migaldi Scott- W10265@motorola.com
33. Guo-Qiang Wang - guoqiang@nortel.com
This mail was sent via mail.alvarion.com
************************************************************************************
This footnote confirms that this email message has been scanned by
PineApp Mail-SeCure for the presence of malicious code, vandals & computer viruses.
************************************************************************************