Re: [STDS-802-3-EPOC] Timestamp presentation for PHY Link call
Duane,
Before we switch from PHY synchronization to synchronization services, I
would really love to get feedback to the questions I posted on the reflector
some time ago, if possible, i.e., what are we missing with 802.3bf and
802.1as in place that would prevent us from supporting synchronization
services over EPoC. We seem to be in a hurry to define whole solution for
delivery of synchronization services over EPoC, while I do not think we
fully explored the use of these two standards in combination to deliver sync
services.
Following the discussion at the last call, and you proposal, I can certainly
see how we can achieve PHY synchronization, though perhaps visual
explanation of the actual need for it would be certainly also very welcome.
As mentioned before, I want to understand the problem better to be able to
vote on this topic in an informed manner in York, should this topic comes up
for discussions and motions.
As for your proposal itself - I understand that the field sizes you propose
are merely minimum required sizes - we typically do not become overly
concerned with single bits, especially when future extensibility might be of
interest. Looking at the definitions of individual fields, it would be
helpful to actually show what units we measure each in.
Last but not least, one or two numeric examples would be helpful, to better
understand what each individual fields are expected to do. Without
additional drawings, it is a bit a stretch to figure out what is what,
despite the text you already included in the slides.
Thank you
Marek
PS. "worst cast" likely needs to be "worst case" ???
From: Duane Remein [mailto:Duane.Remein@xxxxxxxxxx]
Sent: Tuesday, August 06, 2013 3:30 PM
To: Marek Hajduczenia; STDS-802-3-EPOC@xxxxxxxxxxxxxxxxx
Cc: Duane Remein
Subject: RE: [STDS-802-3-EPOC] Timestamp presentation for PHY Link call
Marek,
You probably noticed that this bullet is followed by a question mark, as is
the bullet "Other". My guess is that a timestamp, as described, would be
useful in ToD synchronization and general network timing but you are
correct, I haven't explored it's application in this area.
Best Regards,
Duane
FutureWei Technologies Inc.
duane.remein@xxxxxxxxxx
Director, Access R&D
919 418 4741
Raleigh, NC
From: Marek Hajduczenia [mailto:marek.hajduczenia@xxxxxxxxx]
Sent: Tuesday, August 06, 2013 5:20 AM
To: Duane Remein; STDS-802-3-EPOC@xxxxxxxxxxxxxxxxx
Subject: RE: [STDS-802-3-EPOC] Timestamp presentation for PHY Link call
Duane,
Could you please clarify how your proposal is associated with "Network
Synchronization/ToD" ? It is mentioned up front, but otherwise - disregarded
afterwards .
Marek
From: Duane Remein [mailto:Duane.Remein@xxxxxxxxxx]
Sent: Tuesday, August 06, 2013 5:43 AM
To: STDS-802-3-EPOC@xxxxxxxxxxxxxxxxx
Subject: [STDS-802-3-EPOC] Timestamp presentation for PHY Link call
Mark,
Presentation for tomorrows call.
Best Regards,
Duane
FutureWei Technologies Inc.
duane.remein@xxxxxxxxxx
Director, Access R&D
919 418 4741
Raleigh, NC
_____
________________________________________________________________________
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