May 2005 doc.: IEEE 802.1105-0623-00-0000
Joint Wireless Groups Architecture AdHoc
Date: 2005-07-01
Name
Tom Siep
Company Address
CSR 2425 N. Central
Expressway, Suite
1000, Richardson,
TX 75080
Phone
+1 214 558
4358 email tom.siep@csr.com
Notice: This document has been prepared to assist IEEE 802.11. It is offered as a basis for discussion and is not binding on the contributing individual(s) or organization(s). The material in this document is subject to change in form and content after further study. The contributor(s) reserve(s) the right to add, amend or withdraw material contained herein.
Release: The contributor grants a free, irrevocable license to the IEEE to incorporate material contained in this contribution, and any modifications thereof, in the creation of an IEEE
Standards publication; to copyright in the IEEE’s name any IEEE Standards publication even though it may include portions of this contribution; and at the IEEE’s sole discretion to permit others to reproduce in whole or in part the resulting IEEE Standards publication. The contributor also acknowledges and accepts that this contribution may be made public by IEEE 802.11.
Patent Policy and Procedures: The contributor is familiar with the IEEE 802 Patent Policy and Procedures < http:// ieee802.org/guides/bylaws/sb-bylaws.pdf
>, including the statement
"IEEE standards may include the known use of patent(s), including patent applications, provided the IEEE receives assurance from the patent holder or applicant with respect to patents essential for compliance with both mandatory and optional portions of the standard." Early disclosure to the Working Group of patent information that might be relevant to the standard is essential to reduce the possibility for delays in the development process and increase the likelihood that the draft publication will be approved for publication. Please notify the Chair
< stuart.kerry@philips.com
> as early as possible, in written or electronic form, if patented technology (or technology under patent application) might be incorporated into a draft standard being developed within the IEEE 802.11 Working Group. If you have questions, contact the IEEE Patent Committee Administrator at < patcom@ieee.org
>.
Submission Slide 1 Tom Siep, Cambridge Silicon Radio

Month Year doc.: IEEE 802.1105-0623-00-0000
• Notes and slides from Ad Hoc meeting on
Architecture for 802 wireless standards held
17May05.
• Background slides are from 802.1
Architecture forum.
• Notes are on slide 9
• Output of meeting on slide 10
• NOTE : previous versions of slide 9 incorrectly had the number of “yes” votes as 13 instead of 3. Typo highlighted in RED
Submission Slide 2 Tom Siep, Cambridge Silicon Radio Plc

May 2005 doc.: IEEE 802.1105-0623-00-0000
• PURPOSE: Brief ad hoc attendees and prepare for
Plenary meeting of 802.1 Architecture
• Consolidate 802.wireless community’s architecture issues
– Quality of Service
– Security
– Management
– Other?
• Determine if we, as the wireless 802 community, want to:
– Present a common set of issues
– Request formation of a TAG to address architecture issues
Submission Slide 3 Tom Siep, Cambridge Silicon Radio

May 2005
Last Name
Shusaku
Haixiang
Godfrey
Shinkichi
Lach
Hiertz
Lothar
O'Hara
Odman
Lusheng
Miller
Worstell
Falk
Buttar
Takashi
Keigo
McInnis
Njedjon
Callaway
Liu
Submission
Attendees (1 of 2) doc.: IEEE 802.1105-0623-00-0000
First Name
Shimada
He
Tim
Ikeda
Hong-Yon
Guido R.
Skibov
Bob
Xiaoyu
Knut
Ji
Bob
Harry
Lars
Alistair
Aramaki
Aso
Mike
Eric
Ed
Email Address kodman@pulselink.net
lji@research.att.com
rrm@att.com
hworstell@att.com
lars.p.falk@-------.com
alistair.buttar@jp.panasonic.com
aramaki.takashi@jp.panasonic.com
aso.keigo@jp.panasonic.com
michael.d.mcinnis@boeing.com
eric.njedjon@francetelecom.com
ed.callaway@motorola.com
shusaku@ieee.org
haixiang@nortel.com
tim.godfrey@conerant.com
ikeda.shinkichi@jp.panasonic.com
hong-yon.lach@motorola.com
hiertz@ieee.org
lsr@comnets.--------.de
bob.ohara@cisco.com
xiaoyu.liu@samsung.com
Slide 4
WG
15
11
11
21
21
11
11
11
11
21
11
21
15
16
15
15
11
11
11
21
Tom Siep, Cambridge Silicon Radio

May 2005
Last Name
Bahr
Zweis
Yongwon
Jin
Jeom
Song
Kim
Tan
Williams
Barber
Rajkumar
Kim
Henderson
Engwer
Zuniga
Chouiward
Decuir
Astrin
Kiernan
Hunter
Submission
Attendees (2 of 2) doc.: IEEE 802.1105-0623-00-0000
First Name Email Address WG
Michael
Phillip
Ajay
Ronny (Yong-Ho)
G. Scott
Darwin
Juan Carlos
Gerald
Joe
Art
Michael
Johnny
Kwak
Lee
Soon Ik
Myungsun
Chang-Joo
Teik-Kheong
Brian
David michael.g.williams@nokia.com
pbarber@broadbandmobiletech.com
ajayrajkumar@lucent.com
ronnykim@lge.com
shenderson@rim.com
dengwer@nortel.com
j.c.zuniga@ieee.org
gerald.chouiward@crc.ca
joe@mcci.com
artastrin@aol.com
bahr@siemens.com
justjohnny@apple.com
yongwon@ige.com
jins978@ige.com
sijeon@etri.re.kr
mssong@etri.re.kr
cjkim@etri.re.kr
tktan@ieee.org
brian.kiernan@-----digital.com
hunter@timefactor.com
Slide 5
16
21
Tom Siep, Cambridge Silicon Radio
11
11
21
21
22
22
22
22
11
11
11
22
15
11
21
16
21
21

May 2005 doc.: IEEE 802.1105-0623-00-0000
• Improve alignment between WG projects and existing 802 architecture by:
– Identifying current problems, omissions, conflicts, ramifications, and their potential resolution
– Identifying potential refinements or changes to the architecture
– Providing a regular forum in which such discussion can take place, in a lower pressure environment than is possible during the core
Plenary cycle.
Submission Slide 6 Tom Siep, Cambridge Silicon Radio

May 2005 doc.: IEEE 802.1105-0623-00-0000
• Due diligence issues – need to fix 802 procedures
– TJ to propose to SEC that the rules for forwarding to SB &
RevCom be strengthened
– WGs should review projects against PAR/5C requirements during the development cycle
• Each WG:
– Prioritize issues
– Characterize the problem
– Propose approach to resolve, or identify as intractable
– Identify other groups (802 or external) that may be affected
Submission Slide 7 Tom Siep, Cambridge Silicon Radio

May 2005 doc.: IEEE 802.1105-0623-00-0000
• Security
– This standard specifies unique per-device identifiers (DevID) and the management and cryptographic binding of a device to its identifiers, the relationship between an initially installed identity and subsequent locally significant identities, and interfaces and methods for use of DevIDs with existing and new provisioning and authentication protocols.
– See
11-05-xxxx-00-0000-Summary_of_PAR-5C_of_P802-1AL.ppt
• Management of RF
– This standard specifies protocols, procedures, and managed objects to support Radio Frequency (RF) management across IEEE 802 wireless Media Access Control (MAC) layers.
– See
11-05-xxxx-00-0000-Summary_of_PAR-5C_of_P802-1AM.ppt
Submission Slide 8 Tom Siep, Cambridge Silicon Radio

May 2005 doc.: IEEE 802.1105-0623-00-0000
• ~60 people present (40 signed attendance sheet)
• Discussion turned initially to the 802.1AM PAR
– There was concern that 802.1 may not have the expertise to do the RF management task
– Question: Is management of an RF system fundamentally different than a wired system? Yes.
– Straw poll: “Do you favor approval of the 802.1AM PAR?” yes 3 ; no 20; reserve judgment 13
• Discussion then turned to what wireless groups need in common
– Straw poll: “Is a common language needed for wireless for communicating operational characteristics and status of dissimilar wireless systems?” yes 23; no 1; reserve judgement15
Submission Slide 9 Tom Siep, Cambridge Silicon Radio

May 2005 doc.: IEEE 802.1105-0623-00-0000
Output from Wireless Architecture Ad Hoc
Discussions in Cairns
• Establish a joint wireless systems study group to address common 802 wireless issues consisting of representatives of the various wireless groups
– Focus on cooperation between wireless groups
– Might lead to formation of a TAG or WG or TGs within a WG or a standing committee
– Support coexistence or handoff efforts, not duplicating
– Investigate a common language for communicating operational characteristics and status of dissimilar wireless systems
• Action: representatives from all wireless groups to present the above request for approval
Submission Slide 10 Tom Siep, Cambridge Silicon Radio

May 2005 doc.: IEEE 802.1105-0623-00-0000
Presented at Monterey
Submission Slide 11 Tom Siep, Cambridge Silicon Radio

May 2005 doc.: IEEE 802.1105-0623-00-0000
• Management
– LLC – acts as a block to passing additional
(e.g., QoS) parameters
– QoS
– (Signal) Power/channel management
• Bridging compatibility
– handling of multicasts, no clause 6 section for .1D
Submission Slide 12 Tom Siep, Cambridge Silicon Radio

May 2005 doc.: IEEE 802.1105-0623-00-0000
LLC – acts as a block to passing additional
(e.g., QoS) parameters
• All 3 MAC need LLC support to requests to create/modify/terminate streams based on
QoS parameters
• Data needs to be able to be associated with a stream at the MAC SAP
• QoS changes need to be communicated to the higher layers
• Need to be able to inquire QoS characteristics of remote nodes
Submission Slide 13 Tom Siep, Cambridge Silicon Radio

May 2005 doc.: IEEE 802.1105-0623-00-0000
• Block asynchronous data
– Need block size to plan and allocate resources
Submission Slide 14 Tom Siep, Cambridge Silicon Radio

May 2005 doc.: IEEE 802.1105-0623-00-0000
(Signal) Power/channel management
• Need a way to pass (up and down) information that is important to wireless, for example
– Transmit power
– Regulatory domain
– Signal quality
– Coexistence information
– Other
• Must be extensible
Submission Slide 15 Tom Siep, Cambridge Silicon Radio

May 2005 doc.: IEEE 802.1105-0623-00-0000
Bridging compatibility – handling of multicasts, no clause 6 section for .1D
• Compatibility with .1D
– 15.1a – Bridging is handled in BNEP, which maps to Ethernet.
– 15.3 – Annex A (normative) specifies compatibility
– 15.4 – Annex A (normative) specifies compatibility
• Multicasts
– 15.1a – does not do multicast
– 15.3 – Had multicast, being revised in current work
– 15.4 – Had broadcast, being revised to include multicast in current work
Submission Slide 16 Tom Siep, Cambridge Silicon Radio

May 2005 doc.: IEEE 802.1105-0623-00-0000
• LLC – acts as a block
 802.1 and 802.2
• QoS
 802.1 and 802.2
• (Signal) Power/channel management
 802.1 and 802.2
• Bridging compatibility – internal problem being worked
Submission Slide 17 Tom Siep, Cambridge Silicon Radio

May 2005 doc.: IEEE 802.1105-0623-00-0000
• Form plans to solve issues
• Determine feasibility of plans
• Study proposal to use IETF model for
QoS – will it work for .15 TGs?
• Characterize management function needs
• Can’t do bridging 64 to 48 bit addresses
– are we OK with this?
Submission Slide 18 Tom Siep, Cambridge Silicon Radio