IEEE P criteria responses

Slides:



Advertisements
Similar presentations
Doc.: IEEE /661r1 Submission November 2002 Ziv Belsky, WavionSlide 1 Proposal for the 5 criteria for the HT SG.
Advertisements

Doc.: IEEE /661r0 Submission November 2002 Ziv Belsky, WavionSlide 1 Proposal for the 5 criteria for the HT SG.
ECMP for 802.1Qxx Proposal for PAR and 5 Criteria Version 2 16 people from ECMP ad-hoc committee.
CSD for P802.1AS-REV WG Wednesday, 05 November 2014.
IEEE 802.1ABrev Extension for Auto Attach Nigel Bragg Dan Romascanu Paul Unbehagen.
21-08-xxxx IEEE MEDIA INDEPENDENT HANDOVER DCN: mrpm Title: Comments on PAR/5C of MRPM SG Date Submitted: September 7, 2008.
Network Management Overview IACT 918 July 2004 Gene Awyzio SITACS University of Wollongong.
IEEE Qbv DRAFT 5C’s for Time Aware Shaper enhancement to 802.1Q
1 IS112 – Chapter 1 Notes Computer Organization and Programming Professor Catherine Dwyer Fall 2005.
Health Informatics Series
Network Management Management Tools –Desirable features Management Architectures Simple Network Management Protocol.
Remote Monitoring and Desktop Management Week-7. SNMP designed for management of a limited range of devices and a limited range of functions Monitoring.
Doc.: IEEE /252 Submission November M. Hoeben - No Wires Needed Load Balancing PAR Criteria Maarten Hoeben.
CHAPTER 5 Infrastructure Components PART I. 2 ESGD5125 SEM II 2009/2010 Dr. Samy Abu Naser 2 Learning Objectives: To discuss: The need for SQA procedures.
Introduction to Software Quality Assurance (SQA)
Doc.: IEEE /0981r1 TGs Reference Architecture Considerations September 6, 2004 Tricci So & W. Steven Conner.Slide 1 TGs ESS Mesh System Reference.
2 Systems Architecture, Fifth Edition Chapter Goals Describe the activities of information systems professionals Describe the technical knowledge of computer.
SCSC 311 Information Systems: hardware and software.
© 2006 Cisco Systems, Inc. All rights reserved.Cisco Public 1 Version 4.0 Gathering Network Requirements Designing and Supporting Computer Networks – Chapter.
Proposal for device identification PAR. Scope Unique per-device identifiers (DevID) Method or methods for authenticating that device is bound to that.
Product Documentation Chapter 5. Required Medical Device Documentation  Business proposal  Product specification  Design specification  Software.
IEEE SCC41 PARs Dr. Rashid A. Saeed. 2 SCC41 Standards Project Acceptance Criteria 1. Broad market application  Each SCC41 (P1900 series) standard shall.
PAR and CSD for P802.1Qxx WG January PAR (1) 1.1 Project Number: P802.1Qxx 1.2 Type of Document: Standard 1.3 Life Cycle: Full Use 2.1 Title:
Standardization of Mobile Wireless Small Cell Backhaul (SCB) Document Number: IEEE r Date Submitted: Source: Junhyeong.
1 IEEE TGu Interworking with External Network Stefano M. Faccin Nokia IEEE Liaison to 3GPP2.
Doc.: IEEE /0498r0 Submission April 2008 Eldad Perahia, Intel CorporationSlide 1 Modifications to the 60GHz PAR & 5 C’s Proposal Date:
Page 1 IEEE Ethernet Working Group - CSD Version 2.3 Items required by the IEEE 802 CSD are shown in Black text, supplementary items required by.
CSD for P802.1Qcj WG January Project process requirements Managed objects – Describe the plan for developing a definition of managed objects.
Privecsg Privacy Recommendation PAR Proposal Date: [ ] Authors: NameAffiliationPhone Juan Carlos ZúñigaInterDigital
1 Recommendations Now that 40 GbE has been adopted as part of the 802.3ba Task Force, there is a need to consider inter-switch links applications at 40.
1 6/3/2003 IEEE Link Security Study Group, June 2003, Ottawa, Canada Secure Frame Format PAR: 5 Criteria.
Doc.: IEEE /0981r0 TGs Reference Architecture Considerations August 30, 2004 Tricci So.Slide 1 TGs ESS Mesh System Reference Architecture Considerations.
Privecsg Privacy Recommendation PAR Proposal Date: [ ] Authors: NameAffiliationPhone Juan Carlos ZúñigaInterDigital
Management Considerations Sharon Chisholm
Doc.: IEEE xxxx-00-0psc Submission Slide1 PicoCast Forum Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission.
Privecsg Privacy Recommendation PAR Proposal Date: [ ] Authors: NameAffiliationPhone Juan Carlos ZúñigaInterDigital
Slide 1 2/22/2016 Policy-Based Management With SNMP SNMPCONF Working Group - Interim Meeting May 2000 Jon Saperia.
1 IEEE interim, Orlando, Florida, March, 2008new-nfinn-fast-chains-rings-par5c-0308-v1 Fast Recovery for Chains and Rings Proposal for PAR and 5.
Mastering SNMP Notes 25/12/2010. Simple Network Management Protocol (SNMP) is an application-layer protocol that provides a message format for communication.
Doc.: IEEE sru Submission 11 November 2013 M Ariyoshi, S Kitazawa (ATR)Slide 1 Project: IEEE P Working Group for Wireless Personal.
Doc.: IEEE /0860r0 Submission July 2010 Jon Rosdahl, CSRSlide 1 Comments for p New PAR – July 2010 Date: Authors:
Doc.: IEEE ulp Submission Slide 1 May 2012 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission.
Privecsg Privacy Recommendation PAR Proposal Date: [ ] Authors: NameAffiliationPhone Juan Carlos ZúñigaInterDigital
IEEE Std Proposed Revision Purpose, Scope & 5 Criteria.
Contents of this presentation ● PAR material (Title, Scope, Purpose) ● Material as developed at previous meetings ● Provision for new/revised material.
Contents of this presentation ● PAR material (Title, Scope, Purpose) ● Material as developed at previous meetings ● Provision for new/revised material.
Chapter 1 Computer Technology: Your Need to Know
Chapter 19: Network Management
Below 6GHz 11vht PAR&5C's proposal
<month year> doc.: IEEE < e> November 2011
Comments on HT PAR & 5 Criteria
doc.: IEEE <doc#>
Submission Title: [Proposal on PAR and 5C draft for BAN]
<month year> Denver, March 2006
Privacy Recommendation PAR Proposal
Submission Title: [Proposal on PAR and 5C draft for BAN]
doc.: IEEE <doc#1>
Below 6GHz 11vht PAR&5C's proposal
900 MHz ISM Band Date: Authors: January 2010 Month Year
<month year> Denver, March 2006
comments on Pending 802 PARs – July 2011
Comments for p New PAR – July 2010
Below 6GHz 11vht PAR&5C's proposal
IEEE Comments on aq PAR and 5C
IEEE Comments on aq PAR and 5C
Chapter 4 Network Management Standards and Models
Submission Title: BAN closing report for San Diego, CA
Howard Frazier – Broadcom Corporation Seoul, Korea 15-September-2008
Chapter 4 Network Management Standards and Models
Interest for HDR extension to a
Presentation transcript:

IEEE P802.3.1 5 criteria responses Howard Frazier – Broadcom Corporation Seoul, Korea 15-September-2008

Broad Market Potential a) Broad sets of applicability b) Multiple vendors and numerous users c) Balanced costs (LAN versus attached stations) Network management is an essential tool in the operation of all networks of greater than trivial size, and in most if not all application areas. Network management is applicable to all Ethernet operating speeds and media. There are hundreds of Ethernet vendors, including component, system and software suppliers, who produce SNMP-based network management functions and who depend on the availability of standards for SMIv2 MIB modules. There are countless end users who depend on the availability of these standards. GDMO MIB module specifications have traditionally been produced by the IEEE 802.3 working group to ensure that IEEE Std 802.3TM is technically correct and complete. Managed objects are defined with the explicit goal of balancing the cost between the LAN and the attached stations.

Compatibility IEEE 802 defines a family of standards. All standards shall be in conformance with the IEEE 802.1 Architecture, Management, and Interworking documents as follows: 802. Overview and Architecture, 802.1D, 802.1Q, and parts of 802.1f. If any variances in conformance emerge, they shall be thoroughly disclosed and reviewed with 802. Each standard in the IEEE 802 family of standards shall include a definition of managed objects that are compatible with systems management standards. Compatibility with IEEE Standard 802.3 Conformance with the IEEE Std 802.3 Managed object definitions compatible with SNMP The managed object definitions in IEEE Std 802.3 have always been specified in conformance with the referenced standards, and proposed project will build upon the existing work and continue this practice, with no foreseen exceptions. An explicit objective of the proposed project is to document the MIB modules in a manner that is compatible with systems management standards. Compatibility and conformance with IEEE Std 802.3 will be maintained by way of ongoing amendment and revision projects for IEEE Std 802.3.1TM. An explicit objective of the proposed project is to provide managed object definitions conforming to SMIv2, which is compatible with SNMP.

Distinct Identity Substantially different from other IEEE 802 standards One unique solution per problem (not two solutions to a problem) Easy for the document reader to select the relevant specification Substantially different from other 802.3 specifications/solutions Currently, GDMO MIB modules for Ethernet are specified in Annex 30A and 30B of IEEE Std 802.3. These specifications will be moved to IEEE Std 802.3.1 in the course of the proposed project. There is no other IEEE 802 standard for Ethernet interface MIB modules. The SMIv2 MIB modules for Ethernet-like interfaces were formerly produced and published by the IETF, which has stated its desire to discontinue this like of work. The SMIv2 MIB modules produced and published by the IETF will be incorporated into IEEE Std 802.3.1 in the course of the proposed project. The GDMO and SMIv2 MIB modules will be published in a new standard, to be designated IEEE Std 802.3.1, making it easy for the document reader to select the relevant specification. The standard will be published in both the traditional format, as well as a machine-readable (ASCII) format, making it easier for network management software developers to use the specifications. Once the initial project for IEEE Std 802.3.1 has been completed, the GDMO specifications in IEEE Std 802.3 will be deprecated. Future amendments and revisions to IEEE Std 802.3.1 will be performed as necessary to track amendments and revisions to IEEE Std 802.3.

Technical Feasibility Demonstrated system feasibility Proven technology, reasonable testing Confidence in reliability MIB compilers have existed for both SMIv2 and GDMO modules for many years. SNMP management agents have been implemented in a very diverse range of products. Nearly every type of product that provides an Ethernet interface is supported by an SNMP agent. Layer management entities and network management systems based on SNMP and SMIv2 have been in operation for many years. There is an enormous amount of field experience with implementations of the SMIv2 MIB modules for Ethernet-like interfaces. Not only have they been proven reliable, the very existence of these implementations improves the overall reliability of Ethernet networks by supporting network and device level monitoring and fault isolation.

Economic Feasibility Known cost factors, reliable data Reasonable cost for performance Consideration of installation costs The cost factors associated with the implementation of Ethernet-like MIBs conforming to SMIv2 are well known. The proposed project will not introduce any new cost factors. Over a billion units shipped (and counting) suggests that SMIv2 conformant MIB modules entail a reasonable cost for the supplied performance. It is well understood that some very cost-sensitive applications do not implement SMIv2 conformant MIB modules or the SNMP protocol. The use of standards-based MIB modules and network management protocols lowers the installation and operating costs of large networks, by obviating the need for customized agents tailored to a specific protocol or MIB structure.