IEEE 1394, SONET, T-1, etc.

Isochronous bridging to IEEE 1394, IEEE 802.11, and IEEE 802.15.3. [1] The actual objectives list is somewhat longer.

. · An individual urged WiMedia Alliance/802.15.3/3a to work with 1394 to be sure that .15.3/3a will be the wireless transport for wireless 1394. 802.15 Tutorial: · Glyn Roberts reviewed tutorial information which will be posted to the 802.15 web site.

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

From : Jon Rosdahl < jrosdahl@xxxxxxxx > Date : Wed, 14 Nov 2012 05:58:21 -0700 --- This message came from the IEEE 802.11 Task Group M Technical Reflector --- I have uploaded the GEN AdHoc comment file: https://mentor.ieee.org/802.11/dcn/12/11-12-1394-00-000m-gen-adhoc-preballot-comment-collection-resolutions.xlsx   I propose to bring on Thursday AM1 the following Motion: Approve comment resolutions to comments on the Motion Gen-A tab in doc 11-12-1394r0 https://mentor.ieee.org/802.11/dcn/12/11-12-1394-00-000m-gen-adhoc-preballot-comment-collection-resolutions.xlsx There may be other motions after today's Timeslot, but this one covers the comments resolved last Sept.

Layer 2 Transport Protocol for Time Sensitive Applications in Bridged Local Area Networks IEEE P1722/D0.8 Layer 2 Transport Protocol for Time Sensitive Applications in Bridged Local Area Networks 2008-05-18 Copyright © 2007-2008 IEEE.

117 May 2005 RESG Interim Meeting, Austin, TX HigherHigher Level StreamingLevel Streaming Standards:Standards: Part 1 - IEC 61883Part 1 - IEC 61883 Michael Johas Teener mikejt@broadcom.com 217 May 2005 RESG Interim Meeting, Austin, TX IEC 61 IEC 61883883 Standards Standards • IEC 61883 - Digital Interface for Consumer Audio/video Equipment – Part 1: General – Part 2: SD-DVCR data transmission – Part 3: HD-DVCR data transmission (unused) – Part 4: MPEG-2-TS data transmission • 1394 TA adding MPEG-4 and MP3 – Part 5: SDL-DVCR data transmission (unused) – Part 6: Audio and Music data transmission – Part 7: Transmission of Rec.

I’ve uploaded the received comments to mentor:  https://mentor.ieee.org/802.11/dcn/23/11-23-1394-00-00bf-lb276-comments-and-approved-resolutions.xlsx A few action items: PoCs: Please review the comments that I have tentatively assigned to your area, and let me know if you any changes are needed.

That is, IEEE Std 1394 would be identified by:  iso (1) iso-identified-organization (3) ieee (111) standards-association-numberedseries-standards (2) std-1394 (1394)"   Management of the arcs under that is up to the standards developing group (e.g. the Working Group) responsible for that numbered standard.

If it is 32 bits, I think this provides the service needed by 1394 (to convey a quadlet every 125 usec), though I am rather hazy on the details of 1394.

ExampleExample – Purchasing a valid BluRay disk grants you legal access to view it on a valid BluRay player 2 – Content protection is used to insure you or someone else can’t illegally copy and distribute it Content Protection Overview Many, many different types of content protection Media (DVDs Files BluRay CDs etc)– Media (DVDs, Files, BluRay, CDs, etc) – Link (HDMI, MOST, IP, WiFi, etc) Media Examplesp – Content Scrambing System (CSS) - DVD – Advanced Access Content System (AACS) - BluRay Link Examples – Digital Transmission Content Protection (DTCP) • Originally developed with 1394 in mind already plays well with 1722 as a resultOriginally developed with 1394 in mind, already plays well with 1722 as a result – High-Bandwidth Digital Content Protection (HDCP) • Originally developed for HDMI/DVI links.

All data blocks in an RTP packet SHALL be associated with a single isochronous interval on the 1394 bus.

If it is 32 bits, I think this provides the service needed by 1394 (to convey a quadlet every 125 usec), though I am rather hazy on the details of 1394.

This makes them unsuitable for adoption in a layered networking application.makes them unsuitable for adoption in a layered networking application. • For IEEE 1394 bus based networks, a working implementation exists today that meets most of the needs for real-time audio and video streams and that is embodied in the IEC 61883 series standards. • Unfortunately for IEEE 802, the IEC 61883 series of standards uses mechanisms, formats, specific low level services and functions provided by IEEE 1394 that are not provided by IEEE 802. • For the reasons stated above, a new standard is needed to provide a common set of protocol encapsulations and mechanisms by starting with IEC 61883 protocol encapsulations and mechanisms, and modifying them to accommodate alternate lower layer protocols suitable for IEEE 802 networks.

That is, IEEE Std 1394 would be identified by:  iso (1) iso-identified-organization (3) ieee (111) standards-association-numberedseries-standards (2) std-1394 (1394)"   Management of the arcs under that is up to the standards developing group (e.g. the Working Group) responsible for that numbered standard.

This makes them unsuitable for adoption in a layered networking application.makes them unsuitable for adoption in a layered networking application. • For IEEE 1394 bus based networks, a working implementation exists today that meets most of the needs for real-time audio and video streams and that is embodied in the IEC 61883 series standards. • Unfortunately for IEEE 802, the IEC 61883 series of standards uses mechanisms, formats, specific low level services and functions provided by IEEE 1394 that are not provided by IEEE 802. • For the reasons stated above, a new standard is needed to provide a common set of protocol encapsulations and mechanisms by starting with IEC 61883 protocol encapsulations and mechanisms, and modifying them to accommodate alternate lower layer protocols suitable for IEEE 802 networks.

I’ve uploaded the received comments to mentor:  https://mentor.ieee.org/802.11/dcn/23/11-23-1394-00-00bf-lb276-comments-and-approved-resolutions.xlsx A few action items: PoCs: Please review the comments that I have tentatively assigned to your area, and let me know if you any changes are needed.

If I get the 1394 information incorrect, I assume the 1394 folks will correct me. >> My question therefore is are there actually two issues here - >> IEEE P1394c required a Selector Field but also want to use the >> Auto-Negotiation Next Page Message code #5 >> hence the need for clarification.

Microsoft PowerPoint - dvjTimeSync2005Jul08.ppt IEEE 802.3 RE Study Group San Francisco 1July 2005 Clock synchronizationClock synchronization (a Residential Ethernet SG presentation)(a Residential Ethernet SG presentation) David V JamesDavid V James JGGJGG Alexei Alexei BeliaevBeliaev GibsonGibson George George ClasemanClaseman MicrelMicrel IEEE 802.3 RE Study Group San Francisco 2July 2005 Categories of workCategories of work – Service discovery (out of scope) • Identify/control “talkers” and their available “plugs” – Subscription (802.1 centric) • Establish conversation between talker and listener(s) • Reject unless: linkBandwidth < linkCapacity – Clock synchronization • Synchronous reception, forwarding, and presentation – Pacing • Talkers must not be well behaved • Bridges should “sustain” such behaviors – Formats • Frame formats and content (stream IDs, time stamps) • Time aware service interfaces IEEE 802.3 RE Study Group San Francisco 3July 2005 House reference clockHouse reference clock 802.11e Ethernet 802.11e 1394 1394 Room #1 Room #2 Ethernet IEEE 802.3 RE Study Group San Francisco 4July 2005 OverviewOverview • What?

This makes them unsuitable for adoption in a layered networking application.makes them unsuitable for adoption in a layered networking application. • For IEEE 1394 bus based networks, a working implementation exists today that meets most of the needs for real-time audio and video streams and that is embodied in the IEC 61883 series standards. • Unfortunately for IEEE 802, the IEC 61883 series of standards uses mechanisms, formats, specific low level services and functions provided by IEEE 1394 that are not provided by IEEE 802. • For the reasons stated above, a new standard is needed to provide a common set of protocol encapsulations and mechanisms by starting with IEC 61883 protocol encapsulations and mechanisms, and modifying them to accommodate alternate lower layer protocols suitable for IEEE 802 networks.

For example, 1394 uses 125us cycles.

After all, that's what test&review >> companies are paid to do. >> >> To avoid this problem, 1394 reclocks synchronous data when >> it passes through bridges.

For example, 1394 uses 125us cycles.

After all, that's what test&review > companies are paid to do. > > To avoid this problem, 1394 reclocks synchronous data when > it passes through bridges.

March, 2007 AVB 61883 transport SG 3 IEEE 1394 Cycle start • Cycle start packet is sent out by 1394 Cycle Master device every 8 kHz delayed by a maximum of one Asynchronous packet. • All Isochronous Packets immediately follow the cycle start packet for a given 8 kHz cycle.