Presentation is loading. Please wait.

Presentation is loading. Please wait.

Mesh Relevance in CAPWAP and AP Functional Descriptions

Published byWiktor Kujawa Modified over 5 years ago

Similar presentations

Presentation on theme: "Mesh Relevance in CAPWAP and AP Functional Descriptions"— Presentation transcript:

1 Mesh Relevance in CAPWAP and AP Functional Descriptions
May 2004 doc.: IEEE /595r3 May 2004 Mesh Relevance in CAPWAP and AP Functional Descriptions L. Lily Yang (Intel Corp.) Tyan-Shu Jou (Janusys Networks) Lily Yang, Tyan-Shu Jou Lily Yang, Tyan-Shu Jou

2 Overview Intro to IETF CAPWAP
May 2004 Overview Intro to IETF CAPWAP The role of mesh in CAPWAP Need help from mesh vendors The need for “AP Functional Descriptions” Why? Benefits (to mesh group and others) Need a new SG References Lily Yang, Tyan-Shu Jou

3 IETF CAPWAP Problem Statement
May 2004 IETF CAPWAP Problem Statement Network administration burden: Management Monitoring Control Effective RF dynamic provisioning: needs coordination among APs Maintaining Consistent Configuration Security: Access to the network (e.g., physical security of APs) Rogue AP detection Lily Yang, Tyan-Shu Jou

4 CAPWAP Architecture Taxonomy
May 2004 CAPWAP Architecture Taxonomy Autonomous Architecture * Self-contained controller 802.11 WLAN Architectures Centralized Architecture * Centralized controller Distributed Architecture * Distributed control across multiple nodes Categorized by Control Plane Characteristics Lily Yang, Tyan-Shu Jou

5 From Autonomous to Centralized
May 2004 From Autonomous to Centralized AP Functionality Autonomous PHY MAC Control & Config WTP Local MAC PHY MAC Control & Config WTP AC Split MAC PHY Real Time MAC Non RT MAC Control & Config WTP AC Remote MAC PHY Real Time MAC Non RT MAC Control & Config AC WTP Lily Yang, Tyan-Shu Jou

6 What about Mesh? Data plane: de-centralized, multi-hop
May 2004 What about Mesh? Data plane: de-centralized, multi-hop Control plane: can be either [2] Centralized (similar to Local MAC), or Distributed (via peer-to-peer mesh interface), or Hybrid CAPWAP may offer a solution for control and management in mesh networks IF IETF chooses to move on to protocol development in the near future STA 5 STA 1 STA2 STA 3 STA 4 AP #2 AP #1 AP #3 AC Portal External Network Lily Yang, Tyan-Shu Jou

7 Help needed from mesh vendors
May 2004 Help needed from mesh vendors CAPWAP mailing list: Current taxonomy document: Need help from mesh vendors on distributed control Timeline: next 2-3 weeks for another revision Possibly WG last call by end of June Encourage everyone to participate Lily Yang, Tyan-Shu Jou

8 “AP Functional Descriptions”: What? [5]
May 2004 “AP Functional Descriptions”: What? [5] To describe the AP architecture and functionality standardized by the current standard and its amendments, or implied by them. The purpose is to provide a better informative description of an AP, to provide: the basis for interoperability by design (rather than by test), technical innovation, and alignment with the work of other groups. Lily Yang, Tyan-Shu Jou

9 Trends (Why?) [5] A trend in 802.11 WG:
May 2004 Trends (Why?) [5] A trend in WG: from “link view” to “wireless network view” i.e. from 11e, 11n ==> 11r, 11s, WNM, WIEN Natural evolution for WLAN architectures From one-box AP with BSS-centric view (“Autonomous Architecture”) To better coordinated inter-BSS services: “Distributed Architecture”: distributed coordination by peer nodes (example: mesh) “Centralized Architecture”: centralized controller for the network Original AP definitions: interaction with the DS is vague No interoperability within ESS Need to provide better descriptions of ESS and interoperability within the ESS Lily Yang, Tyan-Shu Jou

10 What Groups can Benefit from This?[5]
May 2004 doc.: IEEE /595r3 May 2004 What Groups can Benefit from This?[5] To provide a formal description of the AP for use by other groups. 802.1X also needed and needs a clean description of the functions and behaviors of an AP. CAPWAP: The AP functional descriptions can be used by the IETF CAPWAP group. TGs (ESS Mesh) will extend the functions of an AP to provide for operation in a mesh of APs. This again requires a clear description of the baseline functions of an AP as a starting point. will be specifying inter-802 mobility (e.g to , and to 802.3), and also 802 to cellular mobility. These efforts also require a core functional description of an AP. Lily Yang, Tyan-Shu Jou Lily Yang, Tyan-Shu Jou

11 May 2004 Need to form a new SG [5] To work on better “AP Functional Descriptions” Some open questions for SG to investigate What do we have today in the Standards (as starting points)? What is missing, lacking, or confusing? How to approach the functional decomposition (methodology, granularity)? How to describe the interface or interaction? How to better separate data plane and control plane? What kind of documents will be produced in the end? What impact does it have on other groups? Current discussions in ESS Mesh touch some of these questions, but mostly around mesh and for mesh. => A new SG is needed to address the general issues. Lily Yang, Tyan-Shu Jou

12 One Possible Starting Point based on IAPP Diagram [4]
May 2004 doc.: IEEE /595r3 May 2004 One Possible Starting Point based on IAPP Diagram [4] APME IAPP Distribution Services Portal Integration DS MAC WM MAC MLME DS PHY WM PHY PLME Mesh Relevance: First need to figure out the baseline AP functions, and then figure out where/what ESS mesh functions are … Lily Yang, Tyan-Shu Jou Lily Yang, Tyan-Shu Jou

13 ESS Mesh Group can also help AP Functional Descriptions
May 2004 ESS Mesh Group can also help AP Functional Descriptions A lot of the questions about AP, DS, DSS, ESS are being asked here by ESS mesh group Indication of the need to re-examine the current descriptions Better understanding can result from the discussion here Can potentially feedback to the new SG/TG Lily Yang, Tyan-Shu Jou

14 May 2004 Summary Encourage mesh vendors here to participate in IETF CAPWAP and contribute to the discussion of Distributed Architecture Encourage ESS Mesh Group to stay informed of the CFI on AP Functional Descriptions in WNG and contribute to the effort Lily Yang, Tyan-Shu Jou

15 May 2004 References For additional information, please refer to these more detailed submissions: [1] wng-ap-functional-needs-capwap.ppt [2] wng-wlan-mesh-in-capwap-architecture.ppt [3] wng-thoughts-on-ap-functional-descriptions.ppt [4] wng-need-ap-functional-descriptions.ppt [5] wng-ap-functional-descriptions-update.ppt Lily Yang, Tyan-Shu Jou

Download ppt "Mesh Relevance in CAPWAP and AP Functional Descriptions"

Similar presentations

Doc.: IEEE 802.11-04/481r3 Submission May 2004 Lily Yang, Steve Shellhammer, IntelSlide 1 Thoughts on AP Functional Descriptions L. Lily Yang Steve Shellhammer.

Doc.: IEEE /481r3 Submission May 2004 Lily Yang, Steve Shellhammer, IntelSlide 1 Thoughts on AP Functional Descriptions L. Lily Yang Steve Shellhammer.
Doc.: IEEE 802.11-04/604r0 Submission May 2004 Darwin Engwer, Nortel Networks; Lily Yang, Intel Corp.Slide 1 AP Functional Descriptions Update Darwin Engwer,

Doc.: IEEE /604r0 Submission May 2004 Darwin Engwer, Nortel Networks; Lily Yang, Intel Corp.Slide 1 AP Functional Descriptions Update Darwin Engwer,
CAPWAP Architecture draft-mani-ietf-capwap-arch-00 Mahalingam Mani Avaya Bob O’Hara Airespace Lily Yang Intel.

CAPWAP Architecture draft-mani-ietf-capwap-arch-00 Mahalingam Mani Avaya Bob O’Hara Airespace Lily Yang Intel.
Doc.: IEEE 802.11-04/250r2 Submission March 2004 Lily Yang, IETF CAPWAP Design Team EditorSlide 1 802.11 WLAN Architectural Considerations for IETF CAPWAP.

Doc.: IEEE /250r2 Submission March 2004 Lily Yang, IETF CAPWAP Design Team EditorSlide WLAN Architectural Considerations for IETF CAPWAP.
Doc.: IEEE 802.11-04/0981r1 TGs Reference Architecture Considerations September 6, 2004 Tricci So & W. Steven Conner.Slide 1 TGs ESS Mesh System Reference.

Doc.: IEEE /0981r1 TGs Reference Architecture Considerations September 6, 2004 Tricci So & W. Steven Conner.Slide 1 TGs ESS Mesh System Reference.
Submission November 2003 Dorothy Stanley (Agere Systems) IETF Liaison Report November 2003 Dorothy Stanley – Agere Systems IEEE 802.11 Liaison To/From.

Submission November 2003 Dorothy Stanley (Agere Systems) IETF Liaison Report November 2003 Dorothy Stanley – Agere Systems IEEE Liaison To/From.
Status of CAPWAP Architecture Draft Lily Yang Intel Corp. March 3, 2004 59 th IETF meeting.

Status of CAPWAP Architecture Draft Lily Yang Intel Corp. March 3, th IETF meeting.
Doc.: 11-04-0500-00-0mes Submission 7 May 2004 Tricci SoSlide 1 Need Clarification on The Definition of ESS Mesh Prepared by Tricci So.

Doc.: mes Submission 7 May 2004 Tricci SoSlide 1 Need Clarification on The Definition of ESS Mesh Prepared by Tricci So.
Doc.: IEEE 802.11-04/595r2 Submission May 2002 Lily Yang, Tyan-Shu JouSlide 1 Mesh Relevance in CAPWAP and AP Functional Descriptions L. Lily Yang (Intel.

Doc.: IEEE /595r2 Submission May 2002 Lily Yang, Tyan-Shu JouSlide 1 Mesh Relevance in CAPWAP and AP Functional Descriptions L. Lily Yang (Intel.
Status Update of CAPWAP Architecture Taxonomy Lily Yang (Editor) Intel Corp. August 4, 2004 60 th IETF meeting.

Status Update of CAPWAP Architecture Taxonomy Lily Yang (Editor) Intel Corp. August 4, th IETF meeting.
Doc.: IEEE 11-04/0319r0 Submission March 2004 W. Steven Conner, Intel Corporation Slide 1 Architectural Considerations and Requirements for 802.11 ESS.

Doc.: IEEE 11-04/0319r0 Submission March 2004 W. Steven Conner, Intel Corporation Slide 1 Architectural Considerations and Requirements for ESS.
CAPWAP Arch-Draft Issues IETF 59, Seoul 4 March 2004.

CAPWAP Arch-Draft Issues IETF 59, Seoul 4 March 2004.
62 nd IETF – CAPWAP Working Group1 CAPWAP Objectives Saravanan Govindan March 2005.

62 nd IETF – CAPWAP Working Group1 CAPWAP Objectives Saravanan Govindan March 2005.
CAPWAP Working Group MIB documents IETF 65 David T. Perkins.

CAPWAP Working Group MIB documents IETF 65 David T. Perkins.
Doc.: IEEE 802.11-05/0371r0 Submission May 2005 S. McCann & E. Hepworth, Siemens Roke ManorSlide 1 IEEE 802 Architecture Issues Notice: This document has.

Doc.: IEEE /0371r0 Submission May 2005 S. McCann & E. Hepworth, Siemens Roke ManorSlide 1 IEEE 802 Architecture Issues Notice: This document has.
Doc.: IEEE 802.11-04/0690r0 Submission Andrew Myers, BT Slide 1 July 2004 3GPP SA3 Interworking Security Issues II Andrew Myers British Telecommunications.

Doc.: IEEE /0690r0 Submission Andrew Myers, BT Slide 1 July GPP SA3 Interworking Security Issues II Andrew Myers British Telecommunications.
Doc.: IEEE 802.11-09/1143r0 Submission November 2009 Kazuyuki Sakoda, Sony CorporationSlide 1 Potential confusion in D3.04 Date: 2009-11-11 Authors:

Doc.: IEEE /1143r0 Submission November 2009 Kazuyuki Sakoda, Sony CorporationSlide 1 Potential confusion in D3.04 Date: Authors:
Re-cap & Next Steps Mahalingam Mani. The WG Now and from Now The main deliverables have progressed close to completion for this charter Problem statement.

Re-cap & Next Steps Mahalingam Mani. The WG Now and from Now The main deliverables have progressed close to completion for this charter Problem statement.
IETF CAPWAP Protocol Objectives China Mobile,Huawei Technology, Intel Corporation,ZTE,RITT Nov. 8,2004.

IETF CAPWAP Protocol Objectives China Mobile,Huawei Technology, Intel Corporation,ZTE,RITT Nov. 8,2004.
Subject Name: WIRELESS COMMUNICATION Subject Code: 10EC81 Prepared By: Shima Ramesh, Shivlila Department: Electronics and Communication Engineering Date:

Subject Name: WIRELESS COMMUNICATION Subject Code: 10EC81 Prepared By: Shima Ramesh, Shivlila Department: Electronics and Communication Engineering Date:

Similar presentations

Ads by Google