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

[STDS-802-11-TGM] Updated REVmd MAC ad hoc comment resolution spreadshee Thread Links Date Links Thread Prev Thread Next Thread Index Date Prev Date Next Date Index [STDS-802-11-TGM] Updated REVmd MAC ad hoc comment resolution spreadsheet To : STDS-802-11-TGM@xxxxxxxxxxxxxxxxx Subject : [STDS-802-11-TGM] Updated REVmd MAC ad hoc comment resolution spreadsheet From : Mark Hamilton < mark.hamilton2152@xxxxxxxxx > Date : Thu, 10 May 2018 01:46:23 -0600 --- This message came from the IEEE 802.11 Task Group M Technical Reflector --- All,   I have posted an updated spreadsheet of REVmd MAC ad hoc comment resolutions, here: https://mentor.ieee.org/802.11/dcn/17/11-17-0927-18-000m-revmd-mac-comments.xls   This includes CIDs ready for motion on the “Motion MAC-O” tab: 1397, 1394, 1369, 1354, 1189, 1021.  

August 3, 2007 IEEE P1722 AVBTP Working Group Contribution 4 Proposal Summary •Provide a fragmentation/reassembly service based on an integral number of quadlets •Add one additional quadlet to AVBTP header for all stream data frames •Standardize use of packet length field to use in Bartky Networks www.bartky.net •Standardize use of packet length field to use in conjunction with fragmentation and reassembly algorithms (e.g. used as sanity check for reassembly) –Use 1394 isochronous packet byte length field from previous proposals August 3, 2007 IEEE P1722 AVBTP Working Group Contribution 5 Proposal Summary • Add the following new fields: – Fragment Length (quadlet count) – Fragment Control (First and Last bits) – Stream Sequence (quadlet count) • Reuse the 1394 based packet length field, but standardize for all stream types. • Mandate “smart fragmentation”for cases such as 61883 Bartky Networks www.bartky.net • Mandate “smart fragmentation”for cases such as 61883 where packets are to be fragmented on source packet boundaries – Fragmentation rules passed to on a per stream basis • Per stream needed anyway to handle sequence number control • Allow for delivery of received pipelined fragments and/or incomplete reassembled packets at AVBTP to upper layer.

IEEE 802.3 RE Study Group Atlanta 26March 2005 fractions offset Conversion example: 1394Conversion example: 1394 fractionsseconds cycle (NTP RFC-1305, SNTP RFC-2030) sec b = (a*125)>>7 a b cycles d = (c*3)>>6 c d Notes: Two 32-bit additions for b: b= ((a<<7) - (a<<2) + a) >> 7; One 16-bit addition for d: d = ((c<<2) + c) >> 6; (IEEE 1394 CYCLE_TIME) IEEE 802.3 RE Study Group Atlanta 27March 2005 Conversion example: EPONConversion example: EPON fractionsseconds (NTP RFC-1305, SNTP RFC-2030) b = (a*193125)>>24 a b Notes: Thus, eight 36-bit additions compute a very precise b value: b= ((a<<17)+(a<<16)-(a<<12)+(a<<9)+(a<<6)+(a<<5)+(a<<2)+a) >>24; (nanoTick = 16ns) nanoTicks IEEE 802.3 RE Study Group Atlanta 28March 2005 PassbyPassby PLLs PLLs (proposal 1)(proposal 1) slave PLL clock master clock master clock master clock gate gate gate gate IEEE 802.3 RE Study Group Atlanta 29March 2005 Passthrough PLLs Passthrough PLLs (option 2)(option 2) slave PLL clock master clock master clock master clock gate gate gate gate IEEE 802.3 RE Study Group Atlanta 30March 2005 Synchronized timeSynchronized time--ofof--day clocksday clocks Why?

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.

For example, see IEEE Std 1394-1995.

For example, >see IEEE Std 1394-1995.

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

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

When it 24 did this it listed the existing PHY speeds, thinking new PHYs would be 25 added as they came available. 802.3ch-2020 already failed to add itself. 26 Making this general change will fix the problem that clause 149 27 (2.5G/5G/10GBASE-T1) are not included, as well as smooth the path for 28 IEEE P802.3cy, without impacting existing networks, or closing 29 possibilities for 100BASE-T1L and any possible future 1000BASE-T1L. 30 Additionally, contributions in the Greater than 10 Mb/s long-reach SPE 31 study group have shown that long-reach 1 Gb/s is challenging, leaving 32 greater than 1 Gb/s unlikely - hence 1 Gb/s is a good threshold to pass 33 autonegotiation off to the shorter-reach HSM. 34 35 IMPACT ON EXISTING NETWORKS: None. 36 37 38 +----------------------------------------------------------------------+ 39 |Please attach supporting material, if any | 40 |Submit to:- David Law, Chair IEEE 802.3 | 41 |and copy:- Adam Healey, Vice-Chair IEEE 802.3 | 42 | | 43 |At:- E-Mail: stds-802-3-maint-req@ieee.org | 44 | | 45 | +------- For official 802.3 use -----------+ | 46 | | REV REQ NUMBER: 1394 | | 47 | | DATE RECEIVED: 18 February, 2022 | | 48 | | EDITORIAL/TECHNICAL | | 49 | | ACCEPTED/DENIED | | 50 | | BALLOT REQ'D YES/NO | | 51 | | COMMENTS: | | 52 +-------------+------------------------------------------+-------------+ 53 | For information about this Revision Request see - | 54 |http://www.ieee802.org/3/maint/requests/revision_history.html#REQ1394 | 55 +----------------------------------------------------------------------+ 56

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.  

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

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

However, 1394 acquired global channels and this had some problems.

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.

Replaced by 1394-2008 Revision PAR active a.

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.