. • Bridging to non-802 nets – 1394/USB/MoCA Specifications must be met to use Trademark 720 July 2005 ResE Study Group Thank you!

Most noteable are IEEE 754 Floating Point and IEEE 1394, and other microprocessor standards.

RBR includes features appropriate for the low-latency backplane environment: destination-based flow control, low-power short-haul PHY, backplane-to-backplane links, transport of IEEE-1394 isochronous data, and support of IEEE-1596 memory-update operations.

RBR includes features appropriate for the low-latency backplane environment: destination-based flow control, low-power short-haul PHY, backplane-to-backplane links, transport of IEEE-1394 isochronous data, and support of IEEE-1596 memory-update operations."

. > > Examples: > > IEEE Std 802(R)-2002 or IEEE 802(R)-2002 > > IEEE 802(R) Working Group > > IEEE Std 802.11b(TM)-1999 > > IEEE 1394(TM) > > IEEE P1232(TM) > >If you have any questions, CONTACT Claudio Stanziola - IEEE Standards > >Activities - telephone +1 732 562 3804; " MailTo:c.stanziola@ieee.org" ;.

From IEEE Std 1394 Serial Bus experiences, as well as the telecom industry as a whole, the value of synchronous transfers is greatly increased if time-of-day clocks can also be synchronized.

This is one place where the SG received conflicting information, so the more restrictive number was used ... since existence proofs (IEEE 1588 and IEEE 1394) shows that this kind of synchronization can easily be done with very low complexity.

. > Examples: > IEEE Std 802(R)-2002 or IEEE 802(R)-2002 > IEEE 802(R) Working Group > IEEE Std 802.11b(TM)-1999 > IEEE 1394(TM) > IEEE P1232(TM) >If you have any questions, CONTACT Claudio Stanziola - IEEE Standards >Activities - telephone +1 732 562 3804; " MailTo:c.stanziola@ieee.org" ;.

RBR includes features appropriate for the low-latency backplane environment: destination-based flow control, low-power short-haul PHY, backplane-to-backplane links, transport of IEEE-1394 isochronous data, and support of IEEE-1596 memory-update operations.

Zhang gave a presentation titled ‘Wireless 1394 from microwave to millimeter-wave in MMAC’ (04/351r0).

The relevant standards include: CSMA/CD (IEEE 802.3, ISO 8802-3) Token Bus (IEEE 802.4, ISO 8802-4) Token Ring (IEEE 802.5, ISO/IEC 8802-5) IEEE 802.6 (ISO/IEC DIS 8802-6) FDDI (ISO 9314-2) WLAN (IEEE 802.11, ISO/IEC 8802-11) B) The 'company_id' relevant standards include: defined in IEEE Std 1212-1991 Control and Status Register (CSR) Architecture referenced by IEEE Std 896.2-1991 Futurebus+Physical Layers and Profiles IEEE Std 1596-1992 Scalable Coherent Interface IEEE Std 1394-1995 Serial Bus document.

For instance, a 1394 FCSL cannot correctly process a frame from an 802.2 FCSL.

GND Pair 2 Thomas Müller 4 IEEE RTPGETwisted Quad Fundamentals Typical insertion loss 1 dB/m @ 1 GHz Low crosstalk Bidirektional communication up to 3 GBit/s over 10 m LVDS possible Sdd21 [Pair 1] f [MHz] In se rt io n lo ss [ dB /m ] 0.1 1 10 100 1000 0.001 0.01 0.1 1 10 NEXT [Pair 1 to Pair 2] f [MHz] S dd 21 ( ne ar -e nd ) [d B ] 0.1 1 10 100 1000 -100 -90 -80 -70 -60 -50 -40 -30 -20 -10 0 Orange: Cat 6a Black: Cat 5 Thomas Müller 5 IEEE RTPGE Open interface (connectors are available from different vendors) Interface as described in automotive IEEE 1394 Copper Automotive Standard (Supplement to IDB-1394) Project TS2008001 Designed to meet automotive requirements Electrical (e.g.

IEEE 802.3 Residential Ethernet email archive IEEE 802.3 Residential Ethernet email archive Date Index (Page 14 of 15) Thread Index Search Tool First Page Prev Page Next Page Last Page Re: [RE] CE applications (was: RE: [RE] Focus of discussions) From : Alexei Beliaev Date: Thu, 2 Sep 2004 13:04:31 -0400 (EDT) Re: [RE] CE applications (was: RE: [RE] Focus of discussions) From : Gross, Kevin Date: Thu, 2 Sep 2004 11:28:43 -0400 (EDT) Re: [RE] Resume (was: Network topology requirements (was: [RE] CE app lications )) From : Gross, Kevin Date: Thu, 2 Sep 2004 10:44:15 -0400 (EDT) Re: [RE] Network topology requirements (was: [RE] CE applications ) From : Richard Brand Date: Thu, 2 Sep 2004 02:19:43 -0400 (EDT) Re: [RE] CE applications (was: RE: [RE] Focus of discussions) From : David V James Date: Wed, 1 Sep 2004 19:18:52 -0400 (EDT) Re: [RE] CE applications (was: RE: [RE] Focus of discussions) From : David V James Date: Wed, 1 Sep 2004 19:06:12 -0400 (EDT) Re: [RE] CE applications (was: RE: [RE] Focus of discussions) From : Henry Sariowan Date: Wed, 1 Sep 2004 18:29:57 -0400 (EDT) Re: [RE] CE applications (was: RE: [RE] Focus of discussions) From : Wadekar, Manoj K Date: Wed, 1 Sep 2004 18:12:07 -0400 (EDT) Re: [RE] Network topology requirements (was: [RE] CE applications ) From : Gross, Kevin Date: Wed, 1 Sep 2004 17:58:23 -0400 (EDT) Re: [RE] Overprovisioning (was Re: [RE] CE applications) From : Gross, Kevin Date: Wed, 1 Sep 2004 16:55:02 -0400 (EDT) Re: [RE] Requirement: Bridging to 1394 From : Gross, Kevin Date: Wed, 1 Sep 2004 16:52:39 -0400 (EDT) [RE] Requirement: Bridging to 1394 From : Michael D.

Zhang gave a presentation titled ‘Wireless 1394 from microwave to millimeter-wave in MMAC’ (04/351r0).

For instance, a 1394 FCSL cannot correctly process a frame from an 802.2 FCSL.

(see 802.1AS assumptions from AVB document)). • 61883 format over AVBTP will support presentation time using AVBTP timestamp field instead of current 61883 SYT field – 1394/61883 to 1722/61883 gateways will have to take care of all SYT to AVBTP timestamp conversions, synchronization, cross timestamps, etc. – Editor’s note: Need to work out SYT field for SPH = 1 packets as timestamps are on a per source packet basis (MPEG packet) instead of in the CIP header. • AVBTP 61883 presentation time shall be relative to the 802.1AS clock • Adapt 1394 AV/C Function Control Protocol (FCP) for use in 61883 over AVBTP. • Proprietary encapsulations allowed via reserved subtype (7F16) • Allow for other future expansions via different subtypes.

(see 802.1AS assumptions from AVB document)). • 61883 format over AVBTP will support presentation time using AVBTP timestamp field instead of current 61883 SYT field – 1394/61883 to 1722/61883 gateways will have to take care of all SYT to AVBTP timestamp conversions, synchronization, cross timestamps, etc. – Editor’s note: Need to work out SYT field for SPH = 1 packets as timestamps are on a per source packet basis (MPEG packet) instead of in the CIP header. • AVBTP 61883 presentation time shall be relative to the 802.1AS clock • Adapt 1394 AV/C Function Control Protocol (FCP) for use in 61883 over AVBTP. • Proprietary encapsulations allowed via reserved subtype (7F16) • Allow for other future expansions via different subtypes.

(see 802.1AS assumptions from AVB document)). • 61883 format over AVBTP will support presentation time using AVBTP timestamp field instead of current 61883 SYT field – 1394/61883 to 1722/61883 gateways will have to take care of all SYT to AVBTP timestamp conversions, synchronization, cross timestamps, etc. – Editor’s note: Need to work out SYT field for SPH = 1 packets as timestamps are on a per source packet basis (MPEG packet) instead of in the CIP header. • AVBTP 61883 presentation time shall be relative to the 802.1AS clock • Adapt 1394 AV/C Function Control Protocol (FCP) for use in 61883 over AVBTP. • Proprietary encapsulations allowed via reserved subtype (7F16) • Allow for other future expansions via different subtypes.

802.17 Terms And Definitions 802.17 Terms And Definitions TA Document Not AcceptedIEEE802.17-11Jul2001 IF ="Approved" "" "/ SUBJECT \* MERGEFORMAT :5" \* MERGEFORMAT / SUBJECT \* MERGEFORMAT :5 , July 11, 2000 TA Document Not AcceptedIEEE802.17-11Jul2001 IF ="Approved" "" "/ SUBJECT \* MERGEFORMAT :5" \* MERGEFORMAT / SUBJECT \* MERGEFORMAT :5 , July 11, 2000 802.17 Terms And Definitions 1.

(802.1d, RFC-1394, IP, USB, PCI?)

(802.1d, RFC-1394, IP, USB, PCI?)

(802.1d, RFC-1394, IP, USB, PCI?)

(802.1d, RFC-1394, IP, USB, PCI?)

. • Technologies such as IEEE 1394, Bluetooth and USB exist today but each has their own encapsulation, protocols, timing control, etc. such that building interworking functions is difficult.