Re: [802.3_EPOC] TDD and PHY sub-Task Force creation, ad hoc committee timeframe extensions
Hi Geoff,
Thanks for the heads up. Collectively we'll discuss how to best address these concerns while moving forward.
Mark
From: Geoff Thompson [mailto:thompson@xxxxxxxx]
Sent: Tuesday, December 04, 2012 4:00 PM
To: Mark Laubach
Cc: STDS-802-3-EPOC@xxxxxxxxxxxxxxxxx; Geoff Thompson; David Law; Tony Jeffree; Michael Johas Teener; Steve Carlson
Subject: Re: [802.3_EPOC] TDD and PHY sub-Task Force creation, ad hoc committee timeframe extensions
Mark-
Just an early heads up.
I consider the TDD approach to be out of scope for the currently approved project.
A TDD approach involves changes to the MAC
(The TF may be able to bury it or gloss it over by putting the TDD functionality somewhere else where it doesn't philosophically belong, but the change in approach is a change to the media access control algorithm.)
Therefore, if this approach is to be pursued, you need to start making provision for changing the project paperwork.
In particular, I am concerned with the compatibility issues that such an approach would bring forth with respect to time-sensitive/time-stamped services. That is, I have a suspicion that TDD might break some assumptions that are made for timed services in 802.1 and their dependence on 802.3bf.
I do believe that all of this is fixable but I don't think it is fixable within the current scope. It certainly is better to take these issues into consideration earlier in the project than to run into a brick wall during Working Group or Sponsor ballot.
Best regards,
Geoff Thompson
On 412//12 7:16 AM, Mark Laubach wrote:
Dear IEEE P802.3bn Task Force members,
At the recent P802.3bn meeting at the November 802 Plenary in San Antonio, the TF agreed on the creation of two sub-Task Force subgroups. By way of this email, I am chartering the TDD sub-Task Force and the PHY sub-Task Force as detailed below. For housekeeping on three of our existing ad hoc committees, I am extending their originally stated timeframes until the March 2013 plenary. I'll be overviewing meeting agenda impact with respect to parallel tracks in another email.
IEEE P802.3bn sub-group actions in this email:
Creating: Sub-Task Force name: TDD
Sub-Task Force chair: Steve Shellhammer
Charter
Continue work as started in law_01a_1112.pdf<http://www.ieee802.org/3/bn/public/nov12/law_01a_1112.pdf>
Contribute recommendations to Task Force for approval:
Minimal augmentation to MPCP "logic" to support TDD operation mode for EPoC PHY
Communicate "operational needs" to PHY sub-Task Force and Task Force
E.g. delay and delay variation tolerances, CLT downstream transmitter control, etc.
Maintain approved MPCP clause amendments
NOTES:
Task Force editor staff will coordinate draft work output
At interim and plenary meetings, when this sub-Task Force meets on a parallel track, the remainder of the Task Force continues to meet as the PHY sub-Task Force.
Otherwise follows same procedures as an ad hoc committee
Creating: Sub-Task Force name: PHY
Sub-Task Force chair: Mark Laubach
Charter
Continue main PHY specification development effort
Contribute recommendations to Task Force for approval
Maintain approved PHY clause amendments
NOTES:
Task Force editor staff will coordinate draft work output
At interim and plenary meetings, when the TDD sub-Task Force meets on a parallel track, the remainder of the Task Force continues to meet as this sub-Task Force.
Otherwise follows same procedures as an ad hoc committee
Extending: the following ad hoc committee timeframes are extended until March 2013 IEEE 802 Plenary meeting:
RF Spectrum
Evaluation Criteria and Requirements
PHY Link
These actions will be restated and recorded in opening minutes of the next meeting.
Yours truly,
Mark Laubach, Chair
IEEE P802.3bn EPoC PHY Task Force
Broadband Communications Group
Broadcom Corporation
1351 Redwood Way
Petaluma, CA, 94954
[Description: broadcom.jpg]
Tel: +1.707.792.9093
Cell: +1.650.996.2219
________________________________
________________________________________________________________________
To unsubscribe from the STDS-802-3-EPOC list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-3-EPOC&A=1