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.

Slides:



Advertisements
Similar presentations
A Proposal to Improve IETF Productivity Geoff Huston Marshall Rose draft-huston-ietf-pact-00 October 2002.
Advertisements

Summer Internship Program Outline
David J. Sammons, Dean UF International Center. Southern Association of Colleges and Schools: SACS is our regional accrediting authority. The last SACS.
Doc.: IEEE /1125r0 Submission September 2010 Marc Emmelmann, Fraunhofer FOKUSSlide 1 How does the (new) Fast Initial Link Set- Up PAR address.
Doc.: IEEE /481r3 Submission May 2004 Lily Yang, Steve Shellhammer, IntelSlide 1 Thoughts on AP Functional Descriptions L. Lily Yang Steve Shellhammer.
Doc.: IEEE /250r2 Submission March 2004 Lily Yang, IETF CAPWAP Design Team EditorSlide WLAN Architectural Considerations for IETF CAPWAP.
1 Capwap issues.PPT / DD-MM-YYYY / Initials CAPWAP Issues.
Lionel Morand DIME WG IETF 79 Diameter Design Guidelines Thursday, November 11, 2010 Lionel Morand.
Service Agency Accreditation Recognizing Quality Educational Service Agencies Mike Bugenski
Systems Engineering in a System of Systems Context
Parallel and Distributed IR
1 Common IEP Errors and Legal Requirements. 2 Today’s Agenda Parent Survey Results Procedural Compliance Self Assessment Results.
MIF API draft-ietf-mif-api-extension-05 Dapeng Liu.
Query Health Business Working Group Kick-Off September 8, 2011.
CAPWAP related draft-shao-opsawg-capwap-hybridmac-00 draft-chen-opsawg-capwap-extension-00 draft-zhang-opsawg-capwap-eap-00.
1 Goals and objectives (1 slide only) Project(s): MIB Ad hoc, involves EMS-NMS (MEF 7.1) Purpose of the contribution: Provide the rationale behind starting.
Instructore: Tasneem Darwish1 University of Palestine Faculty of Applied Engineering and Urban Planning Software Engineering Department Requirement engineering.
CIS 499 Senior Seminar Introduction to IT project management.
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, th IETF meeting.
EPotential ICT Capabilities Resource. The ePotential ICT Capabilities Resource (ePotential) is designed to: Assist teachers to develop their own ICT Professional.
Yang Shi (Richard), Yong Zhang IETF 74 th 26 March 2009, San Francisco CAPWAP WG MIB Drafts Report.
Ajh January 2007 CCSDS “Books” Adrian J. Hooke CMC Meeting, Colorado Springs 26 January 2007.
Project Kick-off Meeting Presented By: > > > > Office of the Chief Information Officer.
ARMD – Next Steps Next Steps. Why a WG There is a problem People want to work to solve the problem Scope of problem is defined Work items are defined.
1 IETF-61 – Washington DC Path Computation Element (PCE) BOF-2 Status - CCAMP Co-chairs: JP Vasseur/Adrian Farrel ADs: Alex Zinin/Bill Fenner.
Data Provenance Community Meeting November 6, 2014.
Doc.: IEEE /595r2 Submission May 2002 Lily Yang, Tyan-Shu JouSlide 1 Mesh Relevance in CAPWAP and AP Functional Descriptions L. Lily Yang (Intel.
SoberIT Software Business and Engineering Institute HELSINKI UNIVERSITY OF TECHNOLOGY © Tomi Männistö, Varvana Myllärniemi, 2008 T Software Architectures.
CAPWAP Arch-Draft Issues IETF 59, Seoul 4 March 2004.
62 nd IETF – CAPWAP Working Group1 CAPWAP Objectives Saravanan Govindan March 2005.
CAPWAP Working Group MIB documents IETF 65 David T. Perkins.
Draft-ietf-sidr-roa-format draft-ietf-sidr-arch Matt Lepinski BBN Technologies.
1 IPFIX WG 59th IETF Seoul March 3, 2004 Chairs: Nevil Brownlee, Dave Plonka Discussion:
Draft-melia-mipshop-mobility-services-ps-01.txt. From IETF #66 Discuss MIH PS (as expressed by the WG chair) Need a single PS at WG level (several drafts.
Doc.: IEEE /054r0 Submission January 2003 Dr. John R. Barr, MotorolaSlide 1 Project: IEEE Working Group for Wireless Personal Area Networks.
Outlines Overview Defining the Vision Through Business Requirements
NETLMM BOF IETF 64 James Kempf, DoCoMo Labs USA Phil Roberts, Motorola Labs November 7, 2005.
Doc.: IEEE /0860r0 Submission July 2010 Jon Rosdahl, CSRSlide 1 Comments for p New PAR – July 2010 Date: Authors:
CAPWAP Extension for n and Power/channel Reconfiguration draft-ietf-opsawg-capwap-extension-01 Yifan Chen Dapeng Liu – Presenting Hui Deng Lei Zhu.
Firewall Issues Research Group First meeting yesterday, GGF 14 Mailing list: Projects page:
GGF - © Birds of a Feather - Policy Architecture Working Group.
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 1 © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential.
World Class Standards 44TD21 The ETSI Standards Engineering Process STF308 DTR/MTS Steve Randall STF308 © ETSI All rights reserved MTS#44 March.
Interface extensions YANG & VLAN sub-interface YANG Status update
IEEE 802 OmniRAN EC SG July 2013 Conclusion
Project Integration Management
Mesh Relevance in CAPWAP and AP Functional Descriptions
CAPWAP Working Group IETF 66 Montreal
Dr. Olivier Thunus UNECE Task Force Vice-Chair
IETF Liaison Report November 2003 Dorothy Stanley – Agere Systems
Standards Development: An Overview
IETF Liaison Report March 2004 Dorothy Stanley – Agere Systems
IEEE IETF Liaison Report
Mesh Relevance in CAPWAP and AP Functional Descriptions
IETF Liaison Report May 2004 Dorothy Stanley – Agere Systems
IETF Liaison Report November 2004 Dorothy Stanley – Agere Systems
Mesh Relevance in CAPWAP and AP Functional Descriptions
Bing Liu, Sheng Jiang IETF July 2017
Multi-server Namespace in NFSv4.x Previous and Pending Updates
AP Functional Needs of CAPWAP
IEEE IETF Liaison Report
IEEE IETF Liaison Report
Thoughts on AP Functional Descriptions
Thoughts on AP Functional Descriptions
WLAN Architectural Considerations for IETF CAPWAP
IEEE 802 EC Privacy Recommendation SG November, 2014, Report to 802 EC
WLAN Architectural Considerations for IETF CAPWAP
ARC Closing Report Date: Authors: January 2016
The Need for an AP Functional Description
Presentation transcript:

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 draft is in AD evaluation phase Architecture Taxonomy draft has done: –its expert review rounds: IETF & IEEE Drawn favorable review on conclusions and alignment in perspective with IEEE –Due for (final) issue: rev-05 in a week/two. –That done – and into WGLC the WG has run its course per its current charter

Where do we go from here? A review of this exercise indicates –Architecture Taxonomy is well justified A phased approach to get agreement with IETF & IEEE A consensus in IETF community (WG) to the exercise and its deliverables –IEEE expert review has agreed positively on the trends indicated, analysis & conclusions “ there may be opportunities for future protocol standardization of the Centralized WLAN implementation ” The WG, at the conclusion of pending work –Shutdown and declare work complete Leave the work dangling –May consider extending the work to address the original problem Building upon the validations of the current Exercise. –Resurrect the work done in other forms To address the original intent of arriving at a CAPWAP Protocol Std.

WLAN WG Chair Comments Overall, the Architecture Taxonomy document provides a useful survey of existing vendor implementations, which –Highlights the inherent flexibility of the IEEE MAC definition to support a variety of implementation choices across both single and multiple network elements. –Shows an amount of regularity among vendor choices for partitioning of MAC functionality within the Centralized WLAN implementation alternatives. This suggests that there may be opportunities for future protocol standardization of the Centralized WLAN implementation alternatives. –Selects and describes a representative set of IEEE Functions, as a basis for comparison of the implementations. The selected set of functions used for the comparison is reasonable. Note that discussion is ongoing within IEEE regarding the potential need for additional description of Access Point functionality.