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

RE: I/F locations

All the interfaces defined are optional; therefore, demarcation points could
exist even where an instantiation of the interface is not specified, or
there may be no demarcation points.  Like you said, it is an implementation
question.  If someone implements a device with a demarcation point that
happens to be located at one of the optional interfaces (XGMII, XAUI, XSBI)
and markets their device as being compliant with the standard at that
interface, then that interface must comply with what is in the standard.

If you assume that a demarcation point for a WWDM optics at the PMA service
interface is going to be XSBI, then within the draft of the standard, there
is nothing that defines how to use XSBI for an 10GBASE-LX4 design.  That
doesn't mean you cannot build it.  It just means that it is outside the
scope of the standard.


-----Original Message-----
From: Speers, Ted [mailto:Ted.Speers@xxxxxxxxx]
Sent: Friday, December 01, 2000 3:36 PM
To: stds-802-3-hssg@xxxxxxxx
Subject: I/F locations

	I realize this is an implementation question, but is there a likely
demarcation point between the transceiver module and the MAC.  It's hard to
sort out a lot of these discussions (LSS, XAUI/SUPI, etc.) without have this
in proper context.

	Possible points of demarcation would seem to be either the XAUI or
the XSBI interfaces.  I've seen presentations suggesting both.

	It seems that a break at the XSBI would offer the most in terms of
end-user flexibility and economies of scale for both the users and the
vendors ... with one exception, 10GBASE-X4 would be left out in the cold
because, as far as I can tell, there is no way to implement the standard
across an XSBI. 

	Ted Speers
	Strategic Marketing