Comments on PAR and 5C Date: Authors: March 2010

Slides:



Advertisements
Similar presentations
Doc.: IEEE /0204r2 Submission March 2010 David Halasz, AclaraSlide 1 Comments on Sub 1 GHz license-exempt operation Date: Authors:
Advertisements

Emergency Services EC SG Report to 802 EC Geoff Thompson/Interdigital Study Group Chair (as appointed by 802 chair) 802 Executive Committee Friday Session.
Submissions November 2007 Stephen McCann, NSNSlide 1 IEEE 802 Emergency Services (ES) Call for Interest (CFI) Date: Stephen McCann
Doc.: IEEE /0022r0 Submission July 2005 Steve Shellhammer, Qualcomm Inc.Slide 1 Discussion on Contention-based Protocol (CBP) Study Group Notice:
Brian Rosen Chair, Long Term Definition WG.  i1 = document older strategies for VoIP into  i2 = standard way to support VoIP on current E9-1-1.
Omniran TG 1 Cooperation for OmniRAN P802.1CF Max Riegel, NSN (Chair OmniRAN TG)
Jacob Boston Josh Pfeifer. Definition of HyperText Transfer Protocol How HTTP works How Websites work GoDaddy.com OSI Model Networking.
 The Open Systems Interconnection model (OSI model) is a product of the Open Systems Interconnection effort at the International Organization for Standardization.
IEEE Emergency Services DCN: Title: call flow for Layer 2 support for unauthenticated requests Date.
Doc.: IEEE /176 Submission July 2000 Slide 1Several Authors Perspective on the QoS Problem Keith Amann, Spectralink Peter Ecclesine, Cisco David.
IEEE “Green Book” This set of slides is a collection of presentations, motions and other material that has come before the Working Group.
Doc.: IEEE /296r0 Submission May 2003 Stephen R Whitesell, Chair TIA TR-41Slide 1 TIA TR-41 VoIP Activities Stephen R Whitesell Chair TIA TR-41.
IEEE Emergency Services Working Group Report to: Emergency Services Workshop #7 Geoff Thompson/GraCaSI (supported by Interdigital) Working Group.
Network Reliability and Interoperability Council VII NRIC Council Meeting Focus Group 1B Network Architectures for Emergency Communications in 2010 September.
Doc.: IEEE /0xxxr0 Submission March, 2007 Gabor/SriniSlide 1 Joint TGu : Location Configuration for Emergency Services Notice: This document.
Doc.: IEEE /0778r1 Submission July 2009 Bruce Kraemer (Marvell), Jon Rosdahl (CSR)Slide 1 Feedback on New WG PARs from WG11 for July Plenary Date:
IEEE 802Emergency Services Exec. Committee Study Group Report to IETF ECRIT Geoff Thompson/GraCaSI (supported by Interdigital) Study Group/WG Chair IETF.
Submission doc.: IEEE /0564r0 Slide 1 Operating Classes Date: Authors: Peter Ecclesine (Cisco Systems)
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: Emergency Services Date Submitted: March 18, 2008 Presented at.
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.
Presentation Material ● PAR ● 5 Criteria ● ✔ Problem tutorial ● ✔ Why VoIP doesn't work today ● ✔ What is needed to fix it ● ✔ Working with ECRIT should.
Presentation Material ● PAR ● 5 Criteria ● ✔ Problem tutorial ● ✔ Problem statement (2-6) ● ✔ Why VoIP doesn't work today (7-8) ● ✔ What ECRIT has done.
Chapter 3: Network Protocols and Communications
Chapter 3: Network Protocols and Communications
IEEE MEDIA INDEPENDENT HANDOVER DCN:
November 99 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Proposal for WPAN High Rate Study Group]
Device Security in Cognitive Radio
MISY 3312: Introduction to Telecommunications Summer 2012 VoIP
IP Telephony (VoIP).
IEEE 802 OmniRAN EC SG July 2013 Conclusion
Scope Date: Authors: July 2005 July 2005
IEEE MEDIA INDEPENDENT HANDOVER
How does IT enable our business?
Review of March 2013 Proposed Pars
TASK 4 Guideline.
Brief Introduction to IEEE P802.1CF
IEEE MEDIA INDEPENDENT HANDOVER DCN: REVP
Review of Important Networking Concepts
Brief Introduction to OmniRAN P802.1CF
IEEE MEDIA INDEPENDENT HANDOVER DCN:
TGv redline between Draft 1.0 and 1.01
Proposal for a Generic Emergency Call Support
WG11 response to Proposed 802 PAR - March Orlando Plenary
WG11 response to Proposed 802 PAR - March Orlando Plenary
IEEE 802 Scope of OmniRAN Abstract
IEEE TGaf Los Angeles Opening Report
Feedback on New WG PARs from WG11 for July Plenary
doc.: IEEE <doc#>
ARC-agenda-report-minutes-july-2011
Response to Comments on P802.22b PAR and 5C
Comments on Sub 1 GHz license-exempt operation
IEEE TGaf Los Angeles Closing Report
Liaison Report Date: Author: Mar 2007 Month Year
Video Transport Streaming SG Orlando Opening Report
Proposed work items and timeline for the LC SG
TG1 and System Design Document
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE Comments on aq PAR and 5C
IEEE Comments on aq PAR and 5C
IEEE Emergency Services
Jul 12, /12/10 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: Response to PAR and 5C Comments.
WG11 response to Proposed 802 PAR - March Orlando Plenary
Scope Date: Authors: July 2005 July 2005
The Need for an AP Functional Description
Media Independent Coexistence
Comments to IEEE /68 Date: Authors: September 2009
ARC-agenda-report-minutes-july-2011
Liaison Report Date: Authors: January 2011
July 2004 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Merger Proposal #2 Affirmation of Commitment.
Presentation transcript:

Comments on 802.23 PAR and 5C Date: 2010-03-11 Authors: March 2010 doc.: IEEE 802.11-10/0281r0 March 2010 Comments on 802.23 PAR and 5C Date: 2010-03-11 Authors: Peter Ecclesine, Cisco Systems Peter Ecclesine, Cisco Systems

Abstract Comments on 802.23 PAR and 5C March 2010 March 2010 doc.: IEEE 802.11-10/0281r0 March 2010 Abstract Comments on 802.23 PAR and 5C Peter Ecclesine, Cisco Systems Peter Ecclesine, Cisco Systems

March 2010 PAR request form Peter Ecclesine, Cisco Systems

1.2 Type of Document Situation: Standard March 2010 1.2 Type of Document Situation: Standard Complication: Noone can name the IP communications tools all the authorities are using for citizen-to-authority emergency services communications. Question: What should be done: compile a taxonomy and architecture of emergency services data packet communications? Answer: PAR should be for a Reference Guide, not a Standard. Peter Ecclesine, Cisco Systems

March 2010 5.2 Scope Situation: This standard defines a mechanism that supports compliance within IEEE 802 to applicable civil authority requirements for citizen-to-authority emergency services packet data communications. Specifically, it supports the need for consistent data that is required for citizen-to-authority emergency services packet data encoded session initiation requests. A new MAC or PHY is outside the scope of this effort. Complication: There is no evidence of the current lack of support for "civil authority requirements". Question: What should be done: Provide references of particular requirements not being met. Answer: Research exact requirements and include them (or references to) in the PAR. Peter Ecclesine, Cisco Systems

March 2010 5.2 Scope (2) Situation: This standard defines a mechanism that supports compliance within IEEE 802 to applicable civil authority requirements for citizen-to-authority emergency services packet data communications. Specifically, it supports the need for consistent data that is required for citizen-to-authority emergency services packet data encoded session initiation requests. A new MAC or PHY is outside the scope of this effort. Complication: We have kept IEEE 802 standards independent of telecommunications regulations of 185 countries. Those regulations change continually. Question: What should be done: Should the IEEE 802 Architecture be changed to include mechanisms that support compliance with civil authority requirements? Answer: Research exact requirements and include them (or references to) in a Reference Guide. Peter Ecclesine, Cisco Systems

March 2010 5.2 Scope (3) Situation: This standard defines a mechanism that supports compliance within IEEE 802 to applicable civil authority requirements for citizen-to-authority emergency services packet data communications. Specifically, it supports the need for consistent data that is required for citizen-to-authority emergency services packet data encoded session initiation requests. A new MAC or PHY is outside the scope of this effort. Complication: We have kept IEEE 802 standards independent of telecommunications regulations of 185 countries. Those regulations change continually. Question: What should be done: Is there consistent data that is required for citizen-to-authority emergency services packet data requirements? Answer: Research exact requirements and include them (or references to) in a Reference Guide. Peter Ecclesine, Cisco Systems

March 2010 5.4 Purpose Situation: The purpose of this standard is to support compliance to civil authority requirements complementary to IETF ECRIT specifications for citizen to authority emergency services functionality. This standard intends to encompass voice, data and multi-media requests across IEEE 802 using a new Layer 2 entity and associated behaviors and provide a uniform Structure of Management Information (SMI) for transferring required data for emergency services requests. Complication: There is no evidence of what civil authority requirements are. Question: What should be done: Provide references of particular requirements not being met. Answer: Research exact requirements and include them in the PAR, or change PAR to be for Reference Guide. Peter Ecclesine, Cisco Systems

March 2010 5.5 Need for the project Situation: VoIP emergency calls are currently less effective than those provided by traditional wireline and cellular networks. Emergency calls across IEEE 802 technologies need to support regulatory requirements to assure successful completion (and all associated requirements) of these calls to the correct Public Service Access Point (PSAP), and to do so utilizing the existing set of IEEE 802 PHYs and MACs. Complication: Today, VoIP Service Providers are meeting the regulatory requirements. There is no evidence of what regulatory requirements are not being met. Question: What should be done: Provide references of particular requirements not being met. Answer: Research exact regulatory requirements and include them in the PAR, or change PAR to be for Reference Guide. Peter Ecclesine, Cisco Systems

8.1 Additional Explanatory Notes March 2010 8.1 Additional Explanatory Notes Situation: There are increasingly uniform regulatory requirements that are being imposed on telephone systems across the world on the handling of calls to Emergency Services (911 calls in the US, for example). These requirements have been extended to cellular telephony and are being further extended to cover all cases of packet based telephony services. Voice over Internet Protocol (VoIP) is the most common of these. VoIP calls can easily originate on an 802 network. There is a need for such calls to be handled uniformly at the interface between the 802 Layer 2 network and the Internet. IETF-ECRIT is the group tasked with developing the Internet standards to meet these requirements for the upper layers of the protocol stack. This 802 effort will work with ECRIT to develop a complete solution. Complication: Packet based telephony services are operated at the application layer. 802 does not develop packet based telephony service standards. Question: What is the involvement of 802 with packet based telephony service? Answer: Research exact requirements of 802 for packet based telephony service and include them in the PAR , or change PAR to be for Reference Guide. Peter Ecclesine, Cisco Systems

Separating Regulation from Standards March 2010 Separating Regulation from Standards Situation: We have kept IEEE 802 standards independent of regulations Complication: Regulations continually change in 185 countries Question: How closely coupled should IEEE 802 Architecture be with packet data emergency services communications? Answer: A Reference Guide is the way IEEE-SA collects information about alternative ways for good practice. The IEEE 802 Architecture can be informed by such a Reference Guide. Peter Ecclesine, Cisco Systems

References IEEE-SA PAR Training Materials March 2010 References IEEE-SA PAR Training Materials http://standards.ieee.org/resources/development/initiate/newpar.ppt 802 Overview & Architecture This document serves as the foundation for the family of IEEE 802 Standards published by IEEE for Local Area Networks (LANs) and Metropolitan Area Networks (MANs). It contains descriptions of the networks considered as well as a reference model for protocol standards. Compliance with the family of IEEE 802 Standards is defined, and a standard for the identification of public, private and standard protocols is included. http://standards.ieee.org/getieee802/download/802-2001.pdf Peter Ecclesine, Cisco Systems