Microsoft PowerPoint - AVBTP_Editors_working_slides_v0_03_2007_03_0 Misc. 61883, 1394 and AVB info for tutorial, discussion, brainstorming, etc. for AVBTP working group.

If Peter's concerns are properly paraphrased in the previous paragraph, then I note that: 1) Peter is an authority on 1212 & 1394. 2) Peter has valid points of concern.

The DTV/audio "clusters" will likely be connected together with 1394, but the bridges between 1394 and 802.3+ will have queues as well, so that doesn't reduce the need for queue management.

The DTV/audio "clusters" will likely be connected together with 1394, but the bridges between 1394 and 802.3+ will have queues as well, so that doesn't reduce the need for queue management.

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.

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.

But first, this group needs to ask, among other potential use cases, should "1394 carriage over IP" be included as the legitimate use case for Residential Ethernet?

I'm more familiar with IEEE Std 1394, which distributes&synchronizes timers so that the microphone data can be presented to the amplifier without dropping/inserting samples.

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.

From : Jon Rosdahl < jrosdahl@xxxxxxxx > Date : Tue, 15 Jan 2013 01:02:41 -0700 --- This message came from the IEEE 802.11 Working Group Reflector --- Hello, I have uploaded the GEN AdHoc file that shows all the comments in the Gen AdHoc: https://mentor.ieee.org/802.11/dcn/12/11-12-1394-04-000m-gen-adhoc-preballot-comment-collection-resolutions.xlsx   There are several comments that are still open, as we try to complete prep for closing comments this week, we could use your help.

. > - 802.15 representative to 802 Architecture committee > - 802 EC Attendance software point of contact, July 2006-present > - Sponsor ballot participant in a variety of groups (802.1, 802.16, > 802.11, 802.15, 802.20, 287, 1394, 260.3) > > James Gilb > ---------- This email is sent from the 802 Executive Committee email reflector.

For example, see IEEE Std 1394-1995.

Johas Teener - Mike@Teener.com PGP ID 0x3179D202 23 Acacia Way, Santa Cruz, CA 95062-1313 +1-831-247-9666, fax +1-831-480-5845 ------------------- www.teener.com ------------------------ Prev by Date: Re: [RE] Network topology requirements (was: [RE] CE applications ) Next by Date: Re: [RE] Requirement: Bridging to 1394 Prev by thread: Re: [RE] Overprovisioning (was Re: [RE] CE applications) Next by thread: Re: [RE] Technical Feasibility & Current Work Index(es): Date Thread

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.

Something simpler than this would probably suit our needs and am working with some others on a proposal, but since 1394 has been discussed I figured I'd put out the references.

From : Jon Rosdahl < jrosdahl@xxxxxxxx > Date : Fri, 16 Nov 2012 02:05:36 -0700 --- This message came from the IEEE 802.11 Task Group M Technical Reflector --- Hello TG REVmc, I have updated the GEN Adhoc Comments: https://mentor.ieee.org/802.11/dcn/12/11-12-1394-02-000m-gen-adhoc-preballot-comment-collection-resolutions.xlsx   note that as motions are passed, comments are moved to the Editor for incorporation into the Draft.  

Johas Teener - Mike@Teener.com PGP ID 0x3179D202 23 Acacia Way, Santa Cruz, CA 95062-1313 +1-831-247-9666, fax +1-831-480-5845 ------------------- www.teener.com ------------------------ References : Re: [RE] Overprovisioning (was Re: [RE] CE applications) From: Gross, Kevin Prev by Date: [RE] Requirement: Bridging to 1394 Next by Date: Re: [RE] Overprovisioning (was Re: [RE] CE applications) Prev by thread: Re: [RE] Overprovisioning (was Re: [RE] CE applications) Next by thread: Re: [RE] Overprovisioning (was Re: [RE] CE applications) Index(es): Date Thread

From : Jon Rosdahl < jrosdahl@xxxxxxxx > Date : Thu, 17 Jan 2013 19:30:53 -0700 --- This message came from the IEEE 802.11 Task Group M Technical Reflector --- https://mentor.ieee.org/802.11/dcn/12/11-12-1394-09-000m-gen-adhoc-preballot-comment-collection-resolutions.xlsx   That is the last update planned for the week.

Johas Teener" < Mike@xxxxxxxxxx > Subject : The 1394c bits in message code #5 From : "David V James" < dvj@xxxxxxxxxxxx > Date : Mon, 9 Aug 2004 21:33:37 -0700 Cc : "IEEE RAC" < stds-rac@xxxxxxxx >, < les@xxxxxxxxxxxxxxxxxxxxxx >, < colinws@xxxxxxxxx >, < kbrown@xxxxxxxxxxxx >, < mike@xxxxxxxxxx >, < whurwitz@xxxxxxxxxxxx >, < don.harwood@xxxxxxxxxx >, < pascal.lagrange@xxxxxxxxxxxx >, "David Law" < David_Law@xxxxxxxxxxxx > Importance : Normal In-Reply-To : Sender : owner-stds-rac@xxxxxxxxxxxxxxxxx Michael, As per my action item in: http://grouper.ieee.org/groups/1394/c/20040726/minutes20040726.pdf Specifically: 45 Dave James Review OUI mapping in section 14.11.2.6 (Still open) 4/27/2004 I have provided FrameMaker and pdf files (attached).

There are 10 CIDs that are ready now for a motion   https://mentor.ieee.org/802.11/dcn/12/11-12-1394-07-000m-gen-adhoc-preballot-comment-collection-resolutions.xlsx   28 CIDs have an owner -- 27 still open for help.   

Replaced by 1394-2008 Revision PAR active a.

. > 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" ;.

Inouye, The IEEE RAC has assigned an Individual Address to the Bluetooth SIG for use as a Bluetooth-specific extension to the 1394 Trade Association's "AV/C Digital Interface Command set General Specification."

I need to request a 1394 Global Unique ID (GUID) for this port. 

https://mentor.ieee.org/802.11/dcn/12/11-12-1394-06-000m-gen-adhoc-preballot-comment-collection-resolutions.xlsx   Please let me know if you can take one or more comments.