|Thread Links||Date Links|
|Thread Prev||Thread Next||Thread Index||Date Prev||Date Next||Date Index|
I have copied your questions below
(and corrected some spelling and typographical items)
My answers are mixed in
(For those new to the conversation, these comments from Yair (Red) and my responses (Green) are all relative to my presentation from the March meeting, http://www.ieee802.org/3/bt/public/mar17/Thompson_01_0317.pdf )
Why it is not in the list above?
(GOT) Because we write our standards for the international market with an eye towards eventual adoption by ISI/IEC. That means we use international rather than national or regional standards for reference whenever possible. In this particular case the definition in the ISO/IEC standard is technically equivalent to the TIA definition so there is no need to cite both.
2. Does your plan is to change also the usage of "channel" and "permanent link" in clause 145.4.9 ?
(GOT) In a word, yes, but it is a little more complicated in my view. First, the problem with figure 145-38 is that it is a cabling standard diagram and only (costly) correct in that context. Thus we face two choices (a) to acknowledge it as a stolen cabling drawing (and somewhat incorrect in our context) or (b) to edit it into correctness. To do that we would have to do the following: (a) redepict (at least) the end connectors from a single box with one "c" into two boxes (i.e. a mated pair) then (b) move the endpoint demarcation lines to align to the mating interface of the mated pair and (c) change the term "channel" to "link section".
"permanent link" should be changed to "link segment" (not "link section")
(GOT) My changes should fix the technical errors introduced by doing that. We can still use the terms cross connect and interconnect without a problem (but I feel that they are unnecessary).
(GOT) It doesn't matter. The tradition in 802.3 (which is an equipment specification group, not a cabling group) has been to specify the media from MDI to MDI (or in the case of PoE from PI to PI) by overall performance of the link segment/section. How a cabling standard chooses to divide that up inside their standard and between cables and cabling hardware is outside our scope.
3. Why you prefer to use terms (link segment/Link section) from ISO/IEC and not from ANSI/TIA
(GOT) See answer #1 for slide 2 above.
4. What is your opinion regarding to modify the the definition above to
"Link section: The point-to-point medium connection between two and only two active Power Interfaces (PIs).
(GOT) I think your addition to my definition improves the definition. It may need more work or a clarifying note to cover the case during the contention process while the PSE PI to be used when the system goes active is being chosen.
Yair: I like the current one since it is more flexible. It allows me to support my current equipment while the above doesnt allow....which is my main problem unless you modify your fantasy definition to the one that I have suggested in the previous slide.
(GOT) The current one is not correct. That is because the "scope" of generic cabling does not include the "application specific connector" (i.e. the RJ-45 that is at each end of the "generic cabling").
1.4.248 link: The transmission path between any two interfaces of generic cabling. (From ISO/IEC 11801.)
As I said above, I like your modification. We will probably need to discuss this a little more in the meeting.
1. where from IEEE802.3AF/AT?
(GOT) Again, perhaps we should add the word "active" to the slide. Otherwise, this is a trick question. You know the answer much more intimately than I do.
Why it is more complex? This case is covered by IEEE802.3AF/AT and 802.3bt.. (Backoff time etc. It means that there is only one PSE active.
(GOT) I was under the impression that 802.3bt allows you to gang one active endspan PSE (Alt A) plus one active midspan PSE (Alt B) simultaneously to get additional power. In that case, if we say that there is one and only link section it has (at least) a funny shape.
1. You can't prevent such a case from happening, it can be by mistake and most likely will not work over 4-pairs due to serious unbalance issues (It will fail PSE_Vdiff, Icon-2P_unb, Overload etc.)
(GOT) This is not a question.
(GOT) Link segment and link section are exactly equivalent in the case of an endspan PSE.
We invented the term "link section" during the development of 802.3af to be able to have a term for the power path when it was not the same length as the data path (i.e. for the midspan case). We made the decision at the time that the term "link section" was defined to have it apply to either the endspan case or the midspan case. We COULD have decided at that time to only make the new term apply to the midspan case but that is not the decision we made at that time. That is not a decision that we can revisit at this point.
I hope this answers your questions. My guess is that to go any further on theses issues we need to discuss it during the meeting rather than by correspondence. I look forward to seeing you in New Orleans.