Re: [STDS-802-3-EPOC] PHY Link ad hoc call tomorrow (Wednesday) 10am Pacific
Duane,
Before we get into the weeds of how to do it, perhaps we need to figure out
what we are trying to do (whether we are trying to provide PHY sync, or
synchronization for upper layers) and whether that puts us on a "collision
course" with the scope of 802.1AS, that is approved and in force. Unless
there is something broken with 802.1AS, I would think that we are kind of
providing an alternative to that solution. It is like providing an
alternative bridging standard within 802.3. That is something that 802.1
does.
Anyway, I would like to better understand what the problem with 802.1AS is
and how we can solve it, rather than trying to jump to the phase of working
on a solution to a problem that has not been yet demonstrated. Perhaps
instead of venturing on this task, we ought to simply indicate to 802.1AS
folks what is broken with their system that it might not work correctly on
our new PHY and cooperate with them on the currently open revision of
802.1AS to make it work right.
The development stage, register sizes, and the likes come then, after we've
better understood what the problem is and why what is currently available
does not work for us.
Regards
Marek
From: Duane Remein [mailto:Duane.Remein@xxxxxxxxxx]
Sent: Wednesday, July 31, 2013 12:47 AM
To: STDS-802-3-EPOC@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-3-EPOC] PHY Link ad hoc call tomorrow (Wednesday)
10am Pacific
Mark,
Could we have an ope discussion on the following topics?
Timestamp - this was part of Avis presentation that was approved by motion
but there were no details. I would like to propose that this is a 32 bit
counter clocked off the PHY Clock (204.8 MHz) or some multiple thereof. The
CNU would keep a local copy of this clock (reset on receipt of DS PHY Link
timestamp) with behavior very similar to the local clock in EPON. This would
be part of the PHY frame overhead along with the already approved PHY
Configuration (2b), PHY Target Address (48b) and FEC Pointer (here I recall
14b but haven't found it in any motioned material).
Another item from Avi's presentation would be Start and number of RB's for
initial Ranging window. As a starting point here I would propose a 32 bit
counter clocked off the PHY Clock (204.8 MHz) or some multiple thereof for
the start timer, call it PHY Discovery Start (essentially the same size as
the Timestamp). When the local PHY clock = PHY Discovery Start then the PHY
ranging window opens. A second register, call it PHY Discovery Duration (in
symbols or PHY clocks), would signify the end of the window.
Avi's presentation also included references to the Preamble sequence. I
would like to here more on what this is to include.
A detailed discussion on PHY Discovery would be good to have also, it should
include:
. What information must the CNU acquire prior to responding to the
PHY Discovery window? My guess: FDD/TDD flag, FFT Size, Cyclic Prefix size,
Window Size, Interleaver Depth (?), OFDMA Frame size, US PLC Center
Frequency, US PLC Cycle Time. Anything else absolutely required?
. What conditions on the CNU must be met on the CNU prior to
responding to the PHY Discovery window? My guess is only that the local PHY
clock and counter are synchronized.
. How does the CNU respond and with what information? My guess is it
only needs to transmit the preamble sequence the its MAC address.
After this if there is time (ha ha) we could start on the "fine tuning".
Best Regards,
Duane
FutureWei Technologies Inc.
duane.remein@xxxxxxxxxx
Director, Access R&D
919 418 4741
Raleigh, NC
From: Mark Laubach [mailto:laubach@xxxxxxxxxxxx]
Sent: Tuesday, July 30, 2013 7:02 PM
To: STDS-802-3-EPOC@xxxxxxxxxxxxxxxxx
Subject: [STDS-802-3-EPOC] PHY Link ad hoc call tomorrow (Wednesday) 10am
Pacific
Dear IEEE P802.3bn Task Force participants,
There will be a PHY Link ad hoc conference call starting at its new time of
10AM Pacific time tomorrow (Wednesday).
As of this time, I have received no presentations to socialize for
tomorrow's call.
We can use the time to review work plan and discussion.
Please be familiar with the IEEE Patent Policy:
https://development.standards.ieee.org/myproject/Public/mytools/mob/slideset
.pdf
Conference Call URL:
WebEx Meeting Number: 921 130 644
To start: https://broadcom.webex.com/broadcom/j.php?J=921130644
Meeting Password: This meeting does not require a password.
Yours truly,
Mark Laubach, Chair
IEEE P802.3bn Task Force
Broadband Communications Group
Broadcom Corporation
1351 Redwood Way
Petaluma, CA, 94954
broadcom.jpg
Tel: +1.707.792.9093
Cell: +1.650.996.2219
_____
<="" p="">
_____
________________________________________________________________________
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
