I know that 1394 has another focus but putting a CAT-5 network is somewhat easier than planning a flexible 1394 network (in Europe we don´t have phone nets like in the US).

The project will be taken to the 1394 TA board for approval in July. 8:34 Glyn Roberts discussed the closing report for the PC committee (IEEE802.15-03/189r2) 8:38 Karaoguz reported on 802.11g.

• 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. – Allow for Proprietary encapsulations via different subtype – 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.

I assume these have been handled already, since 1394 uses a 64-bit address space.

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

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.

Examples of devices which can be connected include computers, computer peripherals (similar to USB 2.0's 480 Mbps capability), PDA/HPCs, printers, set top boxes, information kiosks, image displays, virtual reality games, DVD players, and camcorders (similar to IEEE 1394's 400 Mbps capability).

It was noted that meshing also needs “hand over”. 11:42 Peter Johansson presented new MAC primitives for Synchronization support for 1394 or any time sync’ed protocol adaptation (document 03-0444-00-0030).

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.

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.

. > >As an MSC representative, I would have provided >such a follow-up on the addresses used within >MSC sponsored projects (754, 1394, etc.), as >a duty to my position. > >I prefer to see the evidence before jumping into >denial or conclusions, since (through out my career) >I have seen suboptimal decisions made when this >ordering is reversed. > > >> >If you feel strongly about this, >Yes, I feel strongly about conservation of OUI space.

. > >> > > >> >As an MSC representative, I would have provided > >> >such a follow-up on the addresses used within > >> >MSC sponsored projects (754, 1394, etc.), as > >> >a duty to my position. > >> > > >> >I prefer to see the evidence before jumping into > >> >denial or conclusions, since (through out my career) > >> >I have seen suboptimal decisions made when this > >> >ordering is reversed. > >> > > >> > >> >If you feel strongly about this, > >> >Yes, I feel strongly about conservation of OUI space. > >> >I naively thoutht that to be the premise of our charter. > >> >Times change, I suppose... > >> > > >> >Cheers, > >> >DVJ > >> > > >> > >> -----Original Message----- > >> > >> From: Geoff Thompson [ mailto:gthompso@nortel.com ] > >> > >> Sent: Wednesday, August 08, 2007 3:07 PM > >> > >> To: Floyd Backes > >> > >> Cc: dvj@alum.mit.edu; Geoff Thompson; a.n.weaver@IEEE.ORG; > >> > >> stds-rac@IEEE.ORG > >> > >> Subject: RE: Request for multiple OUI assignments > >> > >> > >> > >> > >> > >> At 11:48 AM 8/8/2007 , Floyd Backes wrote: > >> > >> >If you feel strongly about this, you could review the > >> latest version of > >> > >> >802.1 MAC Bridging, figure out how it can be made to work > >> using the same > >> > >> >MAC address on every port, get a PAR to update the > >> standard, and then > >> > >> >slug it out with Mick over the ensuing 2 years to produce a revised > >> > >> >standard.

. >> This identifier uniquely identifies a device, such as a >> current IEEE 1394 node or a future memory, refrigerator, >> video controller, power supply, etc. >> >> Note that the same identifier must not be used for more than >> one purpose.

. >> >>As an MSC representative, I would have provided >>such a follow-up on the addresses used within >>MSC sponsored projects (754, 1394, etc.), as >>a duty to my position. >> >>I prefer to see the evidence before jumping into >>denial or conclusions, since (through out my career) >>I have seen suboptimal decisions made when this >>ordering is reversed. >> >> >> >If you feel strongly about this, >>Yes, I feel strongly about conservation of OUI space.

The distinction between standards is getting fuzzy: 1394 over CAT-5, security over multiple transports, multiple transports over the same PHYs.

• 802.3ad Link Aggregation (Trunking) PAR • Executive Committee Report & Action Items • Venue of future 802 meetings • March Austin, Texas • July Montreal • November Kauai, Hawaii • Tutorials MONDAY • 6:30: Broadband Wireless (LMDS) - Roger Marks • 8:00: Switch Silicon Interface - Colin Mick TUESDAY • 6:30: Home PhoneWire Networks - Matt Taylor • 8:00: IEEE 1394 and its relevance to LANs - Michael Smith • Books to be distributed this week • 802.3 consolidated edition will be distributed in 802.3 ONLY to voters in the front of the book.

There is an additional standard, Wireless 1394, in development with expected completion in September 2001. 13.

. > >As an MSC representative, I would have provided >such a follow-up on the addresses used within >MSC sponsored projects (754, 1394, etc.), as >a duty to my position. > >I prefer to see the evidence before jumping into >denial or conclusions, since (through out my career) >I have seen suboptimal decisions made when this >ordering is reversed. > > >> >If you feel strongly about this, >Yes, I feel strongly about conservation of OUI space.

Its good for 802 and its good for 1394.

17 April 2007 AVB L3 Transport SG 7 Problem Statement (3) • Some things that AVB L3 TP is not: – Transparent bridging of 1394 over IP • Exploit existing IETF protocols (e.g.

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.

Examples of devices which can be connected include computers, computer peripherals (similar to USB 2.0's 480 Mbps capability), PDA/HPCs, printers, set top boxes, information kiosks, image displays, virtual reality games, DVD players, and camcorders (similar to IEEE 1394's 400 Mbps capability).

Its good for 802 and its good for 1394.

Examples of devices which can be connected include computers, computer peripherals (similar to USB 2.0's 480 Mbps capability), PDA/HPCs, printers, set top boxes, information kiosks, image displays, virtual reality games, DVD players, and camcorders (similar to IEEE 1394's 400 Mbps capability).