-JP-Knapp.doc 2001-04-03 22:11 24K FCC_part15_feb28_01.pdf 2001-03-15 07:01 273K FCC_letter-rev4.doc 2001-03-22 11:56 22K FCC_letter-rev3.doc 2001-03-20 18:37 22K Bluetooth-BOF-at-50th-IETF-PAN-Talk.ppt 2001-03-20 18:40 349K 11-01-201-PG-Publicity-Group-Report-r1.ppt 2001-03-16 14:03 46K 11-01-181r0-E-QoS-for-1394.ppt 2001-03-15 07:00 278K 11-01-152r0-G-An-approach-to-the-problem-of-optimizing-channel-parameters.ppt 2001-03-21 16:51 156K 10958-r2R-Amend-the-IEEE-Five-Criteria.pdf 2001-03-15 07:02 9.6K 1081r28R-Liaison-Between-IEEE802.11-and-RADARs-in-Radiolocation-and-Radionavigation.pdf 2001-03-15 07:02 18K 1080r28R-Liaison-Statement-on-Sharing-Studies.pdf 2001-03-15 07:02 12K 022001_BT_North_America-Siep-r1.PDF 2001-02-21 12:17 1.8M

-JP-Knapp.doc 2001-04-03 22:11 24K 11-01-201-PG-Publicity-Group-Report-r1.ppt 2001-03-16 14:03 46K meeting.pdf 2000-12-12 00:49 98K 11-01-152r0-G-An-approach-to-the-problem-of-optimizing-channel-parameters.ppt 2001-03-21 16:51 156K FCC_part15_feb28_01.pdf 2001-03-15 07:01 273K 11-01-181r0-E-QoS-for-1394.ppt 2001-03-15 07:00 278K Bluetooth-BOF-at-50th-IETF-PAN-Talk.ppt 2001-03-20 18:40 349K Siep_Changes_to_Bluetooth_r1.PDF 2001-02-20 19:15 826K 022001_BT_North_America-Siep-r1.PDF 2001-02-21 12:17 1.8M Siep-WPANs-r1.ppt 2001-03-30 16:39 1.9M

Index of /groups/802/15/pub/802.15 Archives/802.15 Archive pre-802WWW/2001/Mar01/Misc Index of /groups/802/15/pub/802.15 Archives/802.15 Archive pre-802WWW/2001/Mar01/Misc Name Last modified Size Description Parent Directory - 022001_BT_North_America-Siep-r1.PDF 2001-02-21 12:17 1.8M 1080r28R-Liaison-Statement-on-Sharing-Studies.pdf 2001-03-15 07:02 12K 1081r28R-Liaison-Between-IEEE802.11-and-RADARs-in-Radiolocation-and-Radionavigation.pdf 2001-03-15 07:02 18K 10958-r2R-Amend-the-IEEE-Five-Criteria.pdf 2001-03-15 07:02 9.6K 11-01-152r0-G-An-approach-to-the-problem-of-optimizing-channel-parameters.ppt 2001-03-21 16:51 156K 11-01-181r0-E-QoS-for-1394.ppt 2001-03-15 07:00 278K 11-01-201-PG-Publicity-Group-Report-r1.ppt 2001-03-16 14:03 46K Bluetooth-BOF-at-50th-IETF-PAN-Talk.ppt 2001-03-20 18:40 349K FCC_letter-rev3.doc 2001-03-20 18:37 22K FCC_letter-rev4.doc 2001-03-22 11:56 22K FCC_part15_feb28_01.pdf 2001-03-15 07:01 273K RR-01-011-draft2-Letter-to-Mr.

Bob Grow (Intel) – introduction to Study Group List of Isochronous Requirements for RE: (* could be done in 802.3, ** partially in 802.3) Fully supports 802.1 *Low cost (zero additional perceived cost per unit to consumer) MAX 500uSec DELAY THROUGH EACH HOP (illustrated by Gibson) Performance requirements are based on 7 hops maximum (3.5 milliseconds) *Provide master clock with which all stations’ clocks maintain bounded phase delay (illustrated by Pioneer, lip-sync and digital speaker scenarios) *Phase delay (between master and station clock) short term jitter maximum is within a few microseconds *Phase delay (between master and station clock) long term jitter (drift) asymptotically approaches zero *Isochronous traffic only supported over 100Mbps or greater full-duplex *At least 75% of link bandwidth may be reserved for isochronous traffic *At least 10% of link bandwidth is reserved for best-effort traffic *Assumed cycle size is 8kHz (very widely used) **Network provides a mechanism to request/assign resources for isochronous transmission (e.g. bandwidth, channel) and the default rule(s) for managing the resources *Isochronous packets are never dropped nor delayed due to ANY other network traffic *Granularity (not minimum) of bandwidth allocation is on the order of single bytes per cycle By default, resource allocation is first-come-first-serve **Network will automatically reclaim previously allocated but currently unused resources **Isochronous traffic is not disrupted when a station/session is added/removed to/from the network Allows bridging to isoch 802.11e Allows bridging to isoch 1394

Shorted conductors, pairs or loop- back plug (4) Define a capability detection function that works with a powered and an unpowered device (5) Select the voltage, minimum and maximum current and wattage to be supplied (6) Add appropriate management objects for power capability and status (7) Support current standard, 4- pair, horizontal cabling infrastructure for installed Cat 3 and Cat 5 cabling (8) Preserve the signal transmission and isolation characteristics of existing equipment and cabling (9) Maintain normal functionality of Link Integrity Test function in legacy and new devices (10) Consider mid- span power insertion, powering over the signal pairs, and interaction with other RJ- 45 interfaces: Token Ring, ATM, FDDI TP- PMD, 1000BASE- T, ISDN, networking test equipment, PBX, IEEE 1394, devices listed in ISO/IEC 11801 : 1995 Annex G

IEEE 1394 Cat-5?

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

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.

For example, see IEEE Std 1394-1995.

For example, >see IEEE Std 1394-1995.

Will the RAC make the request that IEEE Standard 1394 be modified to use EUI-48?

This would be similar to the case of IEEE 1394 vendor dependent command where the Company_id of the RAC is utilized.

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

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

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).

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

1/ FireWire does not like to go further than 4.5m 2/ FireWire does not scale well - fixed amount of bandwidth is shared amongst all devices on the network. 3/ FireWire is not Ethernet Items 1 and 2 have been addressed by enhancements to the IEEE-1394 specification (FireWore over CAT5 and bridging).

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.

[STDS-802-11-TGM] update to Gen AdHoc Spreadsheet posted -- 11-12/1394r5 Thread Links Date Links Thread Prev Thread Next Thread Index Date Prev Date Next Date Index [STDS-802-11-TGM] update to Gen AdHoc Spreadsheet posted -- 11-12/1394r5 To : STDS-802-11-TGM@xxxxxxxxxxxxxxxxx Subject : [STDS-802-11-TGM] update to Gen AdHoc Spreadsheet posted -- 11-12/1394r5 From : Jon Rosdahl < jrosdahl@xxxxxxxx > Date : Tue, 15 Jan 2013 10:46:03 -0700 --- This message came from the IEEE 802.11 Task Group M Technical Reflector --- After reviewing the file, there were some minor errors that have been corrected here: https://mentor.ieee.org/802.11/dcn/12/11-12-1394-05-000m-gen-adhoc-preballot-comment-collection-resolutions.xlsx   note that Eldad's 5 Comments all now show up on Tab GEN 1431 correctly.

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.

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.   

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.  

High-precision multi-bit linear audio 25 to 196 bit PCM MIDI conformant SMPTE time code conformant Sample count Ancillary data 32bit floating point 24 bit * 4 pack 32bit generic 61883-7 (BO.1294) Transport Stream DirecTV DSS MPEG-2 transport stream. 130byte TS packet length 61883-8 (BT.601) Video Compressed and uncompressed video: 176x120 to 1920x1080, 15 to 60fps IIDC (1394 Digital Camera) Video Uncompressed video 160x120 to 1600x1200 RGB/YUV/B&W, 1.875 to 240fps MMA ?

I have updated the GEN Comment Spreadsheet: https://mentor.ieee.org/802.11/dcn/12/11-12-1394-01-000m-gen-adhoc-preballot-comment-collection-resolutions.xlsx   The Tab for Vinko's set of comments is now labeled GEN-1297 Dorothy will have a motion prepared for this morning that accepts the resolution for GEN Motion A (Comments from Sept), and GEN-1297 (Vinko's Comments).  

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.