IETF CAPWAP Protocol Objectives China Mobile,Huawei Technology, Intel Corporation,ZTE,RITT Nov. 8,2004.

Slides:

Advertisements

Similar presentations

Richard The Management Model of the Centralized Network Architecture IETF 75th meeting, Stockholm draft-richard-opsawg-cna-mib-00.

Advertisements

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

Doc.: IEEE /604r0 Submission May 2004 Darwin Engwer, Nortel Networks; Lily Yang, Intel Corp.Slide 1 AP Functional Descriptions Update Darwin Engwer,

CH1 CWNA Certification Questions. Network Architecture Model What are the layers of the Network Architecture Model? – Core – Distribution – Access.

CAPWAP Architecture draft-mani-ietf-capwap-arch-00 Mahalingam Mani Avaya Bob O’Hara Airespace Lily Yang Intel.

Doc.: IEEE /250r2 Submission March 2004 Lily Yang, IETF CAPWAP Design Team EditorSlide WLAN Architectural Considerations for IETF CAPWAP.

1 © 2005 Cisco Systems, Inc. All rights reserved. CONFIDENTIAL AND PROPRIETARY INFORMATION Cisco Wireless Strategy Extending and Securing the Network Bill.

How are we going to get there? Perry Correll Xirrus, Principal Technologist How will White Spaces impact the consumer market?

Chapter 1 Read (again) chapter 1.

67th IETF San Diego IETF BMWG WLAN Switch Benchmarking Jerry Perser, Tom Alexander, Muninder Singh Sambi,

Mr C Johnston ICT Teacher BTEC IT Unit 09 - Lesson 03 Standards and Technologies.

COGNITIVE RADIO FOR NEXT-GENERATION WIRELESS NETWORKS: AN APPROACH TO OPPORTUNISTIC CHANNEL SELECTION IN IEEE BASED WIRELESS MESH Dusit Niyato,

IT in Business Enterprise and Personal Communications Networks Lecture – 07.

1 Remote Management of Wireless Gateway Student Name: Dinesh D N (BITS ID: 2004HZ12158) MphasiS Technologies Ltd, Bangalore March 2006.

OmniRAN SoA and Gap Analysis Date: [ ] Authors: NameAffiliationPhone Antonio de la Juan Carlos

Networked Information Systems 1 Advantages of and classified by their size & architecture or design.

CAPWAP related draft-shao-opsawg-capwap-hybridmac-00 draft-chen-opsawg-capwap-extension-00 draft-zhang-opsawg-capwap-eap-00.

Chapter 1 1.  Introduction to Networking  Fundamental Network Characteristics  Type and Sizes of Networks  Network Performance issues and Concepts.

IT 351 Mobile &Wireless Computing Semester 2, Dr. Hala Mokhtar Room 79- 2nd floor.

KARTIK DABBIRU Roll # EE

An Integrated QoS, Security and Mobility Framework for Delivering Ubiquitous Services Across All IP-based Networks Haitham Cruickshank University of Surrey.

Standard for a Convergent Digital Home Network for Heterogeneous Technologies Zhimeng Du 12/5/2013.

Yang Shi, Chris Elliott, Yong Zhang IETF 73 rd 18 Nov 2008, Minneapolis CAPWAP WG MIB Drafts Report.

IT 351 Mobile &Wireless Computing Semester 1, Dr. Hala Mokhtar Room th floor.

Doc.: IEEE /137r2 Submission June 2000 Tim Godfrey, IntersilSlide 1 TGe Requirements Version r2 8 June 2000.

Status of CAPWAP Architecture Draft Lily Yang Intel Corp. March 3, th IETF meeting.

Yang Shi (Richard), Yong Zhang IETF 74 th 26 March 2009, San Francisco CAPWAP WG MIB Drafts Report.

Wireless Networking Nandakumar.P. Web Resource

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, th IETF meeting.

CAPWAP Taxonomy Recommendations Pat R. Calhoun, Cisco Systems Bob O’Hara, Cisco Systems Inderpreet Singh, Chantry Networks.

Performance Management of WLANs Simulation of WLAN Manager (WM) Fairness issues related to multi-rate WLAN environment Policy based Service differentiation.

Introduction to Grids By: Fetahi Z. Wuhib [CSD2004-Team19]

Framework & Requirements for an Access Node Control Mechanism in Broadband Multi-Service Networks draft-ietf-ancp-framework-02.txt Presenter: Dong Sun.

62 nd IETF – CAPWAP Working Group1 CAPWAP Objectives Saravanan Govindan March 2005.

Networks, Topology, & Architecture Mrs. Wilson Dreamweaver for College & Business.

Introduction Chapter 1. Business Applications of Networks A network with two clients and one server. Client-Server Model.

TOPIC 1.3 INTRODUCTION TO NETWORKING. Router – A netwok interconnection device & associated software that links two networks. The networks being linked.

61 st IETF – CAPWAP Working Group1 CAPWAP Objectives Saravanan Govindan Panasonic 8 November, 2004.

CAPWAP Working Group MIB documents IETF 65 David T. Perkins.

November 2001 Lars Falk, TeliaSlide 1 doc.: IEEE /617r1 Submission Status of 3G Interworking Lars Falk, Telia.

Networking Components

1 3/13/ :25 Chapter 5Protocol Architecture1 Rivier College CS575: Advanced LANs Chapter 5: Protocol Architecture.

Wired and Wireless network management 1. outline 2 Wireless applications Wireless LAN Wireless LAN transmission medium WLAN modes WLAN design consideration.

Submission May 2016 H. H. LEESlide 1 IEEE Framework and Its Applicability to IMT-2020 Date: Authors:

IEEE Wireless LAN Standard

MUHAMAD SHAZNI BIN MOHAMMAD SHAH. Gateway Using different protocols for interfacing network by network nodes Contain device such as protocol translator,

4G Wireless Technology Prepared by K.Sai Kumar Yadav 07K81A0584.

Lect-12-1: IP over ATMComputer Networks : An Introduction to Computer Networks Handout #16: IP over ATM Homepage

Doc.: IEEE /1060r1 Submission September 2013 S. Rayment, Ericsson & S. McCann, BlackBerrySlide 1 3GPP Liaison Report Date: Authors:

David T. Perkings Shi Yang IETF 70 th 2 Dec 2007, Vancouver CAPWAP WG MIB.

Computer Network Course objective: To understand Network architecture

Shi Yang David T. Perkins IETF 70th 3 Dec 2007, Vancouver

Mobile &Wireless Computing

Mesh Relevance in CAPWAP and AP Functional Descriptions

Vision For IEEE Wireless Network Management

IEEE MEDIA INDEPENDENT HANDOVER

WLAN Mesh in CAPWAP Architecture

CAPWAP Architectural Requirements on

Vision For IEEE Wireless Network Management

Mesh Relevance in CAPWAP and AP Functional Descriptions

WLAN Mesh in CAPWAP Architecture

Mesh Relevance in CAPWAP and AP Functional Descriptions

AP Functional Needs of CAPWAP

3GPP WLAN Interworking Security Issues

Thoughts on AP Functional Descriptions

WLAN Architectural Considerations for IETF CAPWAP

WLAN Architectural Considerations for IETF CAPWAP

AP-AC communications and Functional Architecture

Presentation transcript:

IETF CAPWAP Protocol Objectives China Mobile,Huawei Technology, Intel Corporation,ZTE,RITT Nov. 8,2004

draft-zhou-capwap-objectives-00.txt Co-authors: –Wenhui Zhou (China Mobile) –Zhonghui Yao (Huawei Technologies) –Lily Yang (Intel Corp.) –Meimei Dang (Research Institute of Telecommunication Technologies) –Dong Wang (ZTE) zhou-capwap-objectives-00.txt

Outline Architectural requirements User (client) access requirements Service requirements Centralized control requirements Management requirements Security requirements QoS requirements

Architectural requirements Both local MAC and split MAC based products, (i.e., ACs or WTPs) must be able to co-exist and inter- operate in one WLAN access network. –But first we need to define exactly what is a Local (or Split) MAC AC (or WTP). ACs and WTPs should be able to connect by a variety of interconnect technologies (e.g., Ethernet, bus backplanes, ATM (cell) fabrics, etc.). CAPWAP-supported WTPs should be able to co-exist with non-CAPWAP WTPs in one WLAN access network.

User (client) access requirements There shouldn't be any impact on the client (both hardware and software platform) due to the use of CAPWAP protocol. Clients should not be required to be aware of the existence of CAPWAP protocol.

Service requirements Voice over WLAN. So CAPWAP should support IEEE e and provide fast-handoff capability to avoid voice interruption. Restrict direct inter-WTP layer 2 communication. WLAN network resource sharing: It is required that two or more WLAN service providers can share a hotspot WLAN network. This means that a physical WLAN network can be virtualized into several logical WLAN networks.

Centralized control requirements AC may perform access control functions based on radio resource and/or network resource. AC should support handover and load balancing between different WTPS.

Management requirements It is possible that WTPs can be managed directly or through AC where AC acts as a management agent.

Security requirements It is required to support WPA and/or IEEE i for wireless air interface security. It is required to provide mechanism supporting secure information exchange between AC and WTP

QoS requirements QoS policy should be supported between WTPs and AC via CAPWAP protocol.

Thank You

Questions ？Questions ？ Comments ？Comments ？ Suggestions ？Suggestions ？