July 2005 doc.: IEEE 802.11-05/0635r0 15 July 2005 Wireless WG argument to support proposed 802.1AM PAR & 5 criteria 2005-07-18 Notice: This document.

Slides:



Advertisements
Similar presentations
Doc.: IEEE /0675r0 Submission 15 July 2005 Roger DurandSlide 1 Wireless WG argument to support proposed 802.1AM PAR & 5 criteria Notice:
Advertisements

Coexistence Motions for LB84 Comment Resolution
LB84 General AdHoc Group Sept. Closing TGn Motions
[ Interim Meetings 2006] Date: Authors: July 2005
IEEE WG Status Report – July 2005
Motions Date: Authors: January 2006
Motion to approve letter to ISO/IEC JTC1
London TGu Motions Authors: January 2007 Date: Month Year
LB73 Noise and Location Categories
LB73 Noise and Location Categories
Waveform Generator Source Code
March 2014 Election Results
TGp Closing Report Date: Authors: July 2005 Month Year
TGp Closing Report Date: Authors: July 2007 Month Year
Attendance and Documentation for the March 2007 Plenary
[ Policies and Procedure Summary]
[ Policies and Procedure Summary]
Output from Wireless Architecture discussions
3GPP liaison report May 2006 May 2006 Date: Authors:
Motion to accept Draft p 2.0
November 2013 Opening Report
3GPP liaison report July 2006
[place presentation subject title text here]
Motions Date: Authors: January 2006
TGp Motions Date: Authors: November 2005 Month Year
TGu-changes-from-d0-02-to-d0-03
TGu Motions Date: Authors: September 2006 September 2006
IEEE P Wireless RANs Date:
TGp Closing Report Date: Authors: March 2006 Month Year
Reflector Tutorial Date: Authors: July 2006 Month Year
TGv Redline D0.07 Insert and Deletion
TGv Redline D0.06 Insert and Deletion
TGu Motions Date: Authors: May 2007 May 2007
ADS Study Group Mid-week Report
Joint Wireless Groups Architecture AdHoc
TGu-changes-from-d0-01-to-d0-02
Joint Wireless Groups Architecture AdHoc
LB73 Noise and Location Categories
Liaison Report From wng
TGu Motions Date: Authors: July 2006 July 2006
EC Summary of PAR Development
TGy draft 2.0 with changebars from draft 1.0
TGv Redline D0.10 Insert and Deletion
TGn PSMP Adhoc Group Dallas Opening report
IEEE WG Opening Report – July 2007
WAPI Position Paper Sept 2005 Sept 2005 IEEE WG
Redline of draft P802.11w D2.2 Date: Authors:
November Opening Report
TGu-changes-from-d0-02-to-d0-03
[ Policies and Procedure Summary]
March Opening Report Date: Authors: March 2011
May 2005 CAPWAP AHC Closing Report
TGu Motions Date: Authors: May 2006 May 2006
Beamforming and Link Adaptation Motions
IEEE P Wireless RANs Date:
[ Policies and Procedure Summary]
November 2012 Opening Report
Questions to the Contention-based Protocol (CBP) Study Group
January Opening Report
Motion to go to Letter Ballot
EC Motions – July 2005 Plenary
TGu-changes-from-d0-04-to-d0-05
for video transmission, Status
Motion for Study Group on TV White Space Coexistence
TGu-changes-from-d0-03-to-d0-04
TGu Motions Date: Authors: May 2006 May 2006
July 2005 doc.: IEEE /0635r0 15 July 2005 Wireless WG argument to support proposed 802.1AM PAR & 5 criteria Notice: This document.
PSMP Adhoc Oct TGn Adhoc
WAPI Position Paper Sept 2005 Sept 2005 IEEE WG
TGp Motions Date: Authors: January 2006 Month Year
Presentation transcript:

July 2005 doc.: IEEE 802.11-05/0635r0 15 July 2005 Wireless WG argument to support proposed 802.1AM PAR & 5 criteria 2005-07-18 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>. Roger Durand Andrew Myles, Cisco

July 2005 doc.: IEEE 802.11-05/0635r0 15 July 2005 A variety of technical and practical issues suggest the 802.1AM proposal is both needed and past due Practical issues How can a dual or multi modal product do anything, across different access methods if they do not use even use common terms, semantics or values? Can real co-existence or multi-system interoperability ever succeed if different systems continue to ignore just each other? Multiple dedicated interfaces are less desirable then a common interface. Just as proprietary systems are less desirable then a standard. Technical issues Reconfigurable product is coming to market that can connect using different and diverse access methods and standards A common dictionary is essential, and desirable, for effective RF management Should any algorithm or code require multiple languages to make common decisions or just one? Make changes to existing standards and limit future interoperability Roger Durand Andrew Myles, Cisco

Simple and functional manager Complex and functional manager July 2005 doc.: IEEE 802.11-05/0635r0 15 July 2005 This depicts a 20th century central manager method. A common interface in the long run will NOT be less capable, it will be more capable “Common” in this example for 4 systems =1/4 code, 1/4 bugs, 1/4 work, 1/4 delays, 1/4 failures, +enabling, consistency, simplicity and real co-existence, +facilitating multi systems interoperability 802.1AM proposal Simple and functional manager Common management Interfaces that can recognize the neighbours .1AM .1AM .1AM .1AM 802.1AM agent 802.1AM agent 802.1AM agent 802.1AM agent 802.11 802.15 802.16 802.20 Alternate approach Multiple Interface specific agents that are being developed today are doomed to be inferior when measured across the multiple systems 802.11 agent 802.15 agent 802.16 agent 802.20 agent Multiple dedicated interfaces that each only serve themselves .11 .15 .16 .20 Complex and functional manager Roger Durand Andrew Myles, Cisco

July 2005 doc.: IEEE 802.11-05/0635r0 15 July 2005 802 should encourage the wireless WG’s to ensure wireless networks are manageable It is important to ensure wireless networks are manageable as appropriate and possible using both central and distributed methods Various 802.11 TG’s are beginning to learn how to make 802.11 manageable… But all these efforts are focused only and exclusively on 802.11 with blinders on. No effort for commonality beyond 802.11 or at the 802 level! Other wireless groups are undertaking similar but distinctly different activities with little regard for enabling cross 802 issues Getting 802.1 to work on the many complex problems of the wireless working groups is in everyone’s best interest 802.3 Ethernet greatly benefited from this relationship in the past. The wireless groups are now in a position to benefit from this relationship. The wireless ad hoc in Cairns voted positively (23/1/15) that “…a common language is needed for wireless for communicating operational characteristics and status of dissimilar wireless systems” As 802.11 and the other wireless WG’s “learn to walk” there is clearly interest in making wireless management as easy as possible going forward 802 ExCom should continue to encourage the 802 wireless groups to work towards defining useful dedicated interfaces based on a common language whenever possible At present 802.1 is the group charged with management and Architecture across all 802. Until this charge changes, 802.1am is in the best interest of 802.11 and should be supported Next steps Roger Durand Andrew Myles, Cisco

July 2005 doc.: IEEE 802.11-05/0635r0 15 July 2005 Proposed straw poll at morning session of the wireless ad hoc on 18 July 2005 Straw poll “The wireless ad hoc recommends to the wireless WG’s that the 802.11 WG support the proposed 802.1AM PAR” Proposer: Roger Durand Result Yes: No: Abstain: Motion – wireless ad hoc Roger Durand Andrew Myles, Cisco

July 2005 doc.: IEEE 802.11-05/0635r0 15 July 2005 Proposed motion at the plenary session of the 802.11 WG on 18 July 2005 Motion That the 802.11 working group support the proposed 802.1AM PAR Proposer: Roger Durand Seconder: Result Yes: No: Abstain: Motions – 802.11 Roger Durand Andrew Myles, Cisco