Thread Links Date Links
Thread Prev Thread Next Thread Index Date Prev Date Next Date Index

Re: [802.3_10SPE] comment r02-14



Hi All,

I spoke in favor of specifying MDI connector on the thread that Amrik started.
I listed why having an MDI is a good idea and serves one of the major intended purpose of any 802 standard -- multi-vendor interoperability.

In my mind - referencing a connector WITHOUT normative text, i.e.  connector xxx *may* be used, is marketing.   And by any determination such statement does not specify MDI -- Medium Dependent Interface, THE exposed interface for a particular specified medium and serves as electrical/optical, functional, mechanical, etc, whatever required to assure (multi-vendor) interoperability.  At best, it would serve (technically) additional info that *may be* helpful -- an informative text.

So
A) I would speak against having any connector referenced as MDI and do not have associated "SHALL" normative text. 
B) I may or may not speak against referencing (a set) of connectors that may meet the intended electrical/functional spec but do not claim to be MDI.  I need to see the text first.
C) I will not speak against referencing (a set) of connectors that may meet the intended electrical/functional spec in an informative annex (and by definition no claim of MDI).

I encourage all who agrees with these positions to make your opinion known.

best regards,

Yong Kim, affiliation: NIO


On Sat, Aug 10, 2019 at 1:58 PM Dieter Schicketanz <dieter_schicketanz@xxxxxxxxxxx> wrote:

I am sending this on behalf of Rainer Schmidt, his mail bounces and Matthias Fritsche is still on vacation.

Dieter

 

Dear Task Force Members,

 

since at least I  saw the message from Peter it was clear that I have to contribute to this conversation.

 

First of all I want to thank everyone in the loop for the thoughts, the ideas and all the initiatives to push this standard forward and to find consensus also in critical questions.

 

I guess that it is what the standardization work makes so interesting.

 

To solve the comments especially regarding MDI specification yes or nor or perhaps… the agenda Peter suggested is helpful.

 

  • Restore IEC 63171-1 as suggested in r02-14.

 

I think that is very near to the approach Lennart describes in his email. For my understanding it is important to understand that we speak about a very fragmented market for SPE applications - Lennart mentioned already.

With IEEE802.3cg we give one major advantage to all our customers (including future customers): universal TCP/IP communication over all levels of the network. That is the major success factor for all of the different applications.

But don’t forget where this applications come from and which installation practice is connected to them over many years. That means e.g. for process automation with the thick 18 or 16AWG cables they want to use termination blocks not just plugable cennectors..

And for the industrial space the same. They need well known connector dimensions like M8 and M12…

 

  • Revert the MDI connector text back to D3.0, adding back in IEC 63171-1 and IEC 63171-6 as “MAY” without any mapping to E1/E2/E3.

 

From my point of view that’s the best option combining the request from Lennart to give guidance for connectivity (even it’s not just one) as well as delivers maximal compatibility to cabling standards driven forward in TIA and in ISO/IEC as well - Val mentioned so often.

I personally believe in this solution helping us to address the different SPE applications needing such guidelines. I think automotive or intelligent lighting have their own roadmap regarding connectors…

 

  • Reject the comment and make no change.

 

That’s a possible option I don’t like it too much because we will let pass the opportunity to give guidance and to lead the upcoming SPE market(s) to high compatibility in connectivity.

I will try to attend the Milwaukee meeting. If I can’t for what reason ever I wish you all a successful meeting and good progress.

 

Rainer

 


To unsubscribe from the STDS-802-3-10SPE list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-3-10SPE&A=1


To unsubscribe from the STDS-802-3-10SPE list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-3-10SPE&A=1