Submission Title: [ e Naming Proposal] Date Submitted: [5 Nov 2015]

Slides:



Advertisements
Similar presentations
<November 2003> doc.: IEEE /486r0 <November 2003>
Advertisements

<month year> doc.: IEEE /271r0 September, 2000
Project: IEEE Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Proposals for adding a version number and for the treatment.
Submission Title: [Add name of submission]
May 2000 doc.: IEEE /109r0 May 2000 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: WPAN Requirements.
June 2006 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Proposed Scenarios for Usage Model Document.
Submission Title: [MC EventsList] Date Submitted: [11Jul00]
doc.: IEEE <doc#>
doc.: IEEE <doc#>
<month year> doc.: IEEE <030158r0> March 2004
Submission Title: [Wireless Display Throughput Requirements]
NOV 01 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Application Specific Information Element] Date.
March 2008 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Toumaz response to TG6 Call for Applications]
doc.: IEEE <doc#1>
doc.: IEEE <doc#>
<month year> doc.: IEEE <xyz> January 2001
doc.: IEEE <doc#>
< Sept > Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [IG LPWA Draft Call for Contributions]
Submission Title: [Common rate resolution]
<month year> doc.: IEEE <030158r0> November 2003
August, 2008 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Enhancing reliability of data transmission.
Submission Title: [Resolutions for CID 85, 86, and 87]
September g Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Recognition of Hiroshi.
November 2007 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [TG4c Project Plan] Date Submitted: [15.
<month year> doc.: IEEE <030158r0> September 2003
<month year> November, 2004
July 2018 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Extensions to IEEE in support of.
doc.: IEEE <doc#>
March 2017 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Timeline of TG4s] Date Submitted: [16 March.
doc.: IEEE /XXXr0 Sep 19, 2007 June 2009
Submission Title: [Frame and packet structure in ]
November 2006 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Simplified geometry for the usage model.
October 2011 doc.: IEEE ptc August 2012
<month year>20 Jan 2006
Submission Title: [ e Closing Report for May 2015 Vancouver Session]
<month year> doc.: IEEE <030158r0> January 2004
doc.: IEEE <doc#>
doc.: IEEE <doc#>
April 19 July 2010 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: WNG Closing Report for San Diego.
<month year> <doc.: IEEE doc> March 2015
May 2016 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Timeline of TG4s] Date Submitted: [19 May 2016]
Submission Title: [Proposed project timeline]
doc.: IEEE <doc#1>
May 2015 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: Text for General Description of PAC Date Submitted:
<month year> doc.: IEEE <030158r0> November 2003
Submission Title: [ e Schedule Update]
March 2017 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Timeline of TG4s] Date Submitted: [16 March.
Submission Title: [Proposed project timeline]
<month year> doc.: IEEE <030158r0> <March 2003>
January 2008 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [TG3c Project Plan] Date Submitted: [17.
Submission Title: [ e BRC Motions for the April 2016 teleconference]
Submission Title: [ e Closing Report for July 2015 Waikoloa Session]
September 2008 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Suggested TG3c PAR Changes] Date Submitted:
Mar 2008 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Resolution for Comment 70 ] Date Submitted:
Mar 2008 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Resolution for Comment 70 ] Date Submitted:
November 2007 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [TG4c Project Plan] Date Submitted: [15.
Nov Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Report on IEEE PAC Draft Status]
<month year> <doc.: IEEE doc> September 2015
August, 2008 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Improve the latency between GTS request.
Doc.: IEEE Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Summary.
Submission Title: [Common rate resolution]
September 2015 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Timeline of TG4s] Date Submitted: [17.
Submission Title: [Common rate resolution]
July 2003 doc.: IEEE <03/242> July 2003
Jul 12, /12/10 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: Dependable Interest Group Closing.
Submission Title: TG9ma Agenda for September Meeting
August 2019 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: MLME-SOUNDING and MLME-CALIBRATE comment.
August 2019 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: MLME-SOUNDING and MLME-CALIBRATE comment.
Jan 2008 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: TeraHertz Closing Report Date Submitted: January.
12/15/2019 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [AWGN Simulation Results] Date Submitted:
Presentation transcript:

Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [802.15.3e Naming Proposal] Date Submitted: [5 Nov 2015] Source: [Andrew Estrada] Company [Sony] Address [San Diego, CA, USA] Voice:[+1.858.942.5483], E-Mail:[Andrew.Estrada@am.sony.com] Re: [802.15.3e Naming Proposal] Abstract: [Naming proposal for the 802.15.3e amendment] Purpose: [] Notice: This document has been prepared to assist the IEEE P802.15. It is offered as a basis for discussion and is not binding on the contributing individual(s) or organization(s). The material in this document is subject to change in form and content after further study. The contributor(s) reserve(s) the right to add, amend or withdraw material contained herein. Release: The contributor acknowledges and accepts that this contribution becomes the property of IEEE and may be made publicly available by P802.15.

Naming the new network? 802.15.3 network is called a Piconet: Can be one or many devices Can have child Piconets Can be scanned and discovered 802.15.3e network: let’s call it P2Pnet Can it have 1 device? Yes Can it be scanned? Yes Other possible names?

Editing strategy? Existing text: make clear it applies only to Piconet. New text: make clear only applies to P2Pnet If new text utilizes existing features, DO NOT repeat the text, simply reference existing text

The trouble with P2P P2P, or Point to point, is a widely recognized term in network and communications terminology. Readers may interpret P2P or P2P structure with a meaning different from our intended meaning in the spec.

3 Types of Edits Type 1: Only applies to Piconet Type 2: Only applies to P2Pnet Type 3: Applies to both or either -> reference

Amending each type of text Type 1: Piconet: Leave as is. No change Type 2: P2Pnet: Insert new text, clearly specify P2Pnet

What if text applies to both/either? Type 3: New Text, clearly specify “Piconet or P2Pnet” or “Piconet and P2Pnet”. Type 3: Existing text, insert phrase “or P2Pnet” or “and P2Pnet”

What about PNPP? Is PNPP really required? PNPP = Piconet and P2P. It is not a new network, topology, protocol, or other item. It is merely shorthand for two independent networks. Not necessary to replace every mention of Piconet with PNPP.

What about HRCP? HRCP refers to the use case enabled by the .3e spec. What is the proper usage of HRCP in the draft? Can P2Pnet and HRCP be used interchangeably? Use only P2Pnet to differentiate from Piconet. Use HRCP when referring to the use case

What about HRCP? HRCP could be used to describe the device. Ex: The P2Pnet includes only HRCP devices. HRCP can distinguish from DEV and PNC How about HRCP DEV (HDEV) and HRCP Connection (HCON)? HRCP Link (HLINK)?

Straw Poll To describe the new topology, do you prefer P2Pnet or HRCPxxx -> HRCPxxx Do you prefer HRCPnet (Hnet) (1), or HRCP Link (HRCPlink) (14), or HRCP Connection (HCON) (2), or HRCP Communication (HCOM) (0), or CP Link (CPlink) (10), or CPnet (4), or HRCP Wireless Cable (1)

2nd Straw Poll Do you prefer HRCP Link (11) or CP Link (10)? Straw poll is almost tied. To be discussed and reviewed further.