[STDS-802-3-EPOC] Fwd: [STDS-802-3-EPOC] Revised TDD contribution
FYI - more input from George Hart of Rogers.
-- john
---------- Forwarded message ----------
From: George Hart <George.Hart@xxxxxxxxxxxxxx>
Date: Fri, Jan 25, 2013 at 2:30 PM
Subject: RE: [STDS-802-3-EPOC] Revised TDD contribution
To: John Ulm <julm@xxxxxxxxxxxx>
Hi John,****
** **
I would agree that instantaneous is not the intent either. A diurnal
variation might be the most frequent update required, although I could
imagine it would not even be that often. ****
** **
Thanks for seeking clarification on this.****
** **
Best regards,****
** **
George****
** **
(Please forward this response to the group.)****
** **
** **
*From:* John Ulm [mailto:julm@xxxxxxxxxxxx]
*Sent:* Friday, January 25, 2013 1:35 PM
*To:* STDS-802-3-EPOC@xxxxxxxxxxxxxxxxx
*Subject:* Re: [STDS-802-3-EPOC] Revised TDD contribution****
** **
Hi George,****
** **
A quick additional comment: our discussion in the TDD group was that it
could be re-configure infrequently (e.g. based on time of day), but the
intent is NOT to dynamically change the upstream/downstream mix based on
instantaneous loading. The TDD group would obviously like feedback from
operators thinking of using TDD to make sure this is acceptable.****
****
** **
-- john****
** **
On Fri, Jan 25, 2013 at 12:44 PM, Garavaglia, Andrea <
andreag@xxxxxxxxxxxxxxxx> wrote:****
Hi George,****
Thanks for your feedback, very valid point – we discussed this point
yesterday during the TDD session. ****
****
The group shared the understanding that the solution presented does not
actually require to reset the CNU for such scope: the TDD parameters are
communicated (e.g. beaconed periodically) via the PHY link and it should be
possible therefore to reconfigure the TDD cycle and resource partitioning
between upstream and downstream while the system is operating (as well as
to configure CNU that newly attach to the system). We may need to discuss,
also based on the decision and capability made for the PHY link work, how
fast can such configuration occur and whether some guard intervals would
need to be considered when reconfiguring – I CC Steve here (chairing TDD),
so we can consider it while proceeding with the work. I think we can
further discuss that during the upcoming phone calls.****
****
Thanks,****
Andrea****
****
*From:* Matthew Schmitt [mailto:m.schmitt@xxxxxxxxxxxxx]
*Sent:* Friday, January 25, 2013 10:39
*To:* George Hart @ Rogers; Garavaglia, Andrea;
STDS-802-3-EPOC@xxxxxxxxxxxxxxxxx
*Cc:* Jorge_Salinger@xxxxxxxxxxxxxxxxx
*Subject:* Re: [STDS-802-3-EPOC] Revised TDD contribution****
****
Sharing on behalf of George Hart per his request (since he is unable to
override some offending privacy text in his corporate email system).
Please read below.****
****
Thanks.****
****
Matt****
****
*From: *George Hart <George.Hart@xxxxxxxxxxxxxx>
*Date: *Friday, January 25, 2013 10:32 AM
*To: *"Garavaglia, Andrea" <andreag@xxxxxxxxxxxxxxxx>
*Cc: *Matthew Schmitt <m.schmitt@xxxxxxxxxxxxx>, Jorge Salinger <
Jorge_Salinger@xxxxxxxxxxxxxxxxx>
*Subject: *RE: [STDS-802-3-EPOC] Revised TDD contribution****
****
Andrea,****
****
Thank you for this contribution for TDD mode. ****
****
One of the benefits we hope to exploit from TDD mode is a flexibility in
how capacity is allocated between upstream and downstream. It would appear
from this proposal that such allocation is relatively static, as a CNU
power up is required to change it. It would be preferable that a method is
supported in the EPOC standard for changing the relative time duration for
Downstream vs Upstream transmission without requiring all the CNUs affected
by the change needing a power reset.****
****
Thank you for considering the implications on your proposal for this use
case.****
****
Best regards,****
****
George****
****
P.S. My automatic email privacy notification addendum contravenes the IEEE
email reflector policy so I request that you or Matt forward my note to the
EPOC group without that offending text.****
****
*From:* Garavaglia, Andrea
[mailto:andreag@xxxxxxxxxxxxxxxx<andreag@xxxxxxxxxxxxxxxx>]
*Sent:* Friday, January 25, 2013 11:38 AM
*To:* STDS-802-3-EPOC@xxxxxxxxxxxxxxxxx
*Subject:* [STDS-802-3-EPOC] Revised TDD contribution****
****
Hi all,****
Please find attached the updated contribution Steve just mentioned, Mark is
posting it on the web as well.****
****
Changes compared to previous revision are:****
- Slides 8-11 -> Empty boxes are now labeled Control Multiplexer***
*
- Slide 15 diagram is revised -> typo on localGrantList corrected
and bottom part simplified (no need to check for discovery flag in the CLT)*
***
- Slide 2: clarification added in red****
****
A draft of the changes on the specification according to the proposal will
also be posted by Mark.****
****
Thanks,****
Andrea
________________________________________________________________________
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