| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
|
Thanks, Duane – I had forgotten that 802.3bn modified it as well!
Now we just have to wait for everyone else to catch up on their emails. -george From: Duane Remein [mailto:Duane.Remein@xxxxxxxxxx]
Actually the latest version is in 802.3bn. 1.4.134 channel:
In 10BROAD36 and 10GPASS-XR, a band of frequencies dedicated to a certain service transmitted on the broadband medium. Otherwise, a defined path along which data in the form of an electrical or optical signal passes. (For 10BROAD36, see IEEE Std 802.3,
Clause 11, for 10GPASS-XR see Clause 100, Clause 101, and Clause 102.) Best Regards Duane From: George Zimmerman [mailto:george@xxxxxxxxxxxxxxxxxxxx]
Val & Christian & all – The intent of this has already been addressed. Christian seems to have fallen into the trap that we are amending only 802.3-2015.
Instead, we are amending 802.3-2015 as amended by the 9 other amendments that have gone before us. Yes, it’s been a busy year and hard to keep track. 802.3by already addressed this issue in large part, by changing the definition of channel in 1.4.134. The definition of channel we SHOULD be using is: 1.4.134 channel:
In 10BROAD36, a band of frequencies dedicated to a certain service transmitted on the broadband medium. Otherwise, a defined path along which data in the form of an electrical or optical signal passes. (For 10BROAD36, s other than the explicit reference to link section, which I think is unnecessary, because the definition is generic enough to refer to either link segment or link section, and the possibility that we might
consider power not an electrical “signal”, (in which case, a simple amendment to make it signal
or power should suffice), this comment seems to be OBE by 802.3by-2016. Please, let’s not create extra work for either ourselves or the whole rest of 802.3… -george From: Valerie Maguire [mailto:Valerie_Maguire@xxxxxxxxxx]
Happy New Year, Christian! Your comment definitely identifies a terminology concern. However, since the “power channel” that you are proposing to define is essentially the same as the “data channel”, I think that adding this term may
be confusing. As an alternate solution, how would the group feel about performing a maintenance request to change the current definition of “channel” to “frequency channel” as in:
1.4.xxx frequency channel: In 10BROAD36, a band of
frequencies dedicated to a certain service transmitted on the broadband medium. (See IEEE Std 802.3, Clause 11.) Note, that occurrences of the word “channel” in Clause 11 may also need to be replaced with “frequency channel”. And, revising the existing definition of channel as follows:
1.4.134 channel:
Within Clause 33 and its annexes, the electrical path on which the power is transferred, i.e. the link section. I suspect that it might be necessary to extend the definition of channel to other Clauses besides 33, but I just wanted to get the idea out there for consideration. All the best - Val Valerie Maguire, BSEE Global Sales Engineer 602-228-7943 mobile DISCLAIMER: Siemon makes every attempt to ensure that the content of materials presented or communicated to you is accurate. The content herein is for informational purpose only and Siemon assumes
no responsibility or obligation for actions resulting from this content unless otherwise agreed to in writing and signed by both parties. From: Christian BEIA [mailto:christian.beia@xxxxxx]
Hi all, I prepared a short baseline document in support of comment #26, which addresses my action item in the TDL. Please review and comment. Thanks Christian
|