950 results found. results are sorted by relevance
  101-125
https://grouper.ieee.org/groups/802/15/pub/2002/Mar02/Misc/BRAN22d084%205GSG%20requirements,%20rev3a.doc
Connectivity is provided between IEEE 1394 buses using a H/2 network, and MTs and an NT using the same or another WL network and an optional Ethernet sub-network. interface a point of demarcation between two blocks through which information flows from one block to the other. key management the generation, storage, distribution archiving, deletion, revocation, registration, and de-registration of cryptographic keys. latency the perceived delay between an action and the corresponding reaction.
https://grouper.ieee.org/groups/802/15/pub/2002/May02/Misc/BRAN22d084%205GSG%20requirements,%20rev3a.doc
Connectivity is provided between IEEE 1394 buses using a H/2 network, and MTs and an NT using the same or another WL network and an optional Ethernet sub-network. interface a point of demarcation between two blocks through which information flows from one block to the other. key management the generation, storage, distribution archiving, deletion, revocation, registration, and de-registration of cryptographic keys. latency the perceived delay between an action and the corresponding reaction.
https://grouper.ieee.org/rac/private/email/doc00103.doc
Currently, the IEEE oversees ten registration authorities: Organizationally Unique Identifier (OUI) Individual Address Blocks (IAB) EtherType Field TEDS Extension Identifiers Standard Group MAC Addresses Logical Link Control (LLC) Addresses 1451.4 Manufacturer ID 1451.4 Universal Registration Number (URN) 1451.4 Templates 1451.4 TDL items The following standards and draft standards make use of each registration authority: Organizationally Unique Identifier/Company id/Individual Address Block IEEE Standard 802 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 Std 802.6 (ISO/IEC 8802-6) IEEE Standard 802.11 (ISO/IEC 8802-11) IEEE Standard 802.15 IEEE Standard 802.16 IEEE Standard 802.17 IEEE Standard 802.20 FDDI (ISO 9314-2) IEEE Std 1212-1991 Control and Status Register (CSR) IEEE Std 896.2-1991 Futurebus+Physical Layers and Profiles IEEE Std 1596-1995 Scalable Coherent Interface IEEE Std 1394-1995 Serial Bus ANSI X3. 131 1994 SCSI Manufacturer id IEEE Std 802.3, Clause 16 EtherType Field IEEE Std 802.3 Extension Transducer Electronic Data Sheet (TEDS) Identification Number IEEE Std 1451.2 Standard Group MAC Address IEEE Standard 802.1D IEEE Standard 802.1Q IEEE Standard 802.3 IEEE Standard 802.5 ISO 9542 ISO/IEC 10589 ISO/IEC 10030 ISO/IEC 9542 ISO/IEC 9314-2 and 9314-6 Logical Link Control (LLC) Addresses IEEE Standard 802 IEEE Standard 802.1D IEEE Standard 802.1Q IEEE Standard 802.2 ANSI/ASHRAE 135-1995 ARPANET/IP IEC 62056 IEC 955 ISO 9506 ISO/IEC 8208 ISO/IEC TR 9577 1451.4 Manufacturer ID IEEE Std 1451.4-2004 1451.4 Universal Registration Number (URN) IEEE Std 1451.4-2004 1451.4 Template IEEE Std 1451.4-2004 1451.4 TDL Item IEEE Std 1451.4-2004 Website status : the URL for the IEEE Registration Authority is http://standards.ieee.org/regauth/index.html .
https://grouper.ieee.org/rac/private/email/msg00308.html
The relevant standards include CSMA/CD (IEEE Std 802.3, ISO 8802-3), Token Bus (IEEE Std 802.4, ISO 8802-4), Token Ring (IEEE Std 802.5, ISO/IEC 8802-5), IEEE Std 802.6 (ISO/IEC DIS 8802-6), FDDI (ISO 9314-2) and WLAN (IEEE 802.11, ISO/IEC 8802-11) . b) The "company_id" defined in IEEE Std 1212-1991, IEEE Standard Control and Status Register (CSR) Architecture, is referenced by IEEE Std 896.2-1991, IEEE Standard for Futurebus+(TM) Physical Layer Specification and Profiles, and IEEE Std 1596-1992, IEEE Standard for Scalable Coherent Interface, as well as IEEE Std 1394-1995, IEEE Standard for a High Performance Serial Bus.
https://grouper.ieee.org/groups/802/3/power_study/public/jan00/agenda_0100.pdf
Shorted conductors, pairs or loop- back plug (4) Define a capability detection function that works with a powered and an unpowered device January 20 - 21, 2000 DTE Power via MDI Study Group DTE Power Objectives (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 January 20 - 21, 2000 DTE Power via MDI Study Group Presentation Guidelines • Requests for presentation time should be scheduled with the chair one week prior to the meeting • Presentations should be supplied via e-mail as a PDF file • Avoid fussy backgrounds or other decorative graphics • No animations, video clips, etc. • Goal: to keep the PDF small enough to fit on a single floppy disk January 20 - 21, 2000 DTE Power via MDI Study Group Short-Term Schedule • January Interim, Dallas – NESCOM approve PAR – Continue with real work • March Plenary, Albuquerque – First official meeting of the Task Force • May Interim, Ottawa – Last new proposal accepted January 20 - 21, 2000 DTE Power via MDI Study Group Presentations • “Thermal Impedance of SMT LAN Magnetics”, Henry Hinrichs, Pulse, Inc. • "BER vs.
https://grouper.ieee.org/rac/private/email/msg00973.html
Its good for 802 and its >> good for 1394.
https://grouper.ieee.org/rac/private/email/msg01317.html
The IEEE/RAC has (in my experience) attempted to avoid identifying specific instances of "things", such as I/O drivers on IEEE Std 1394.
https://grouper.ieee.org/rac/private/email/msg00285.html
The relevant standards include CSMA/CD (IEEE Std 802.3, ISO 8802-3), Token Bus (IEEE Std 802.4, ISO 8802-4), Token Ring (IEEE Std 802.5, ISO/IEC 8802-5), IEEE Std 802.6 (ISO/IEC DIS 8802-6), FDDI (ISO 9314-2) and WLAN (IEEE 802.11, ISO/IEC 8802-11) . b) The "company_id" defined in IEEE Std 1212-1991, IEEE Standard Control and Status Register (CSR) Architecture, is referenced by IEEE Std 896.2-1991, IEEE Standard for Futurebus+(TM) Physical Layer Specification and Profiles, and IEEE Std 1596-1992, IEEE Standard for Scalable Coherent Interface, as well as IEEE Std 1394-1995, IEEE Standard for a High Performance Serial Bus.
https://grouper.ieee.org/groups/802/3/re_study/email/msg00168.html
RE requires the following: (* could be done in 802.3, ** partially in 802.3) 1) Of course, fully supports 802.1 2) *Low cost (zero additional perceived cost per unit to consumer) 3) MAX 500uSec DELAY THROUGH EACH HOP (illustrated by Gibson) 4) Performance requirements are based on 7 hops maximum (3.5 milliseconds) 5) *Provide master clock with which all stations’ clocks maintain bounded phase delay (illustrated by Pioneer, lip-sync and digital speaker scenarios) 6) *Phase delay (between master and station clock) short term jitter maximum is within a few microseconds 7) *Phase delay (between master and station clock) long term jitter (drift) asymptotically approaches zero 8) *Isochronous traffic only supported over 100Mbps or greater full-duplex 9) *At least 75% of link bandwidth may be reserved for isochronous traffic 10) *At least 10% of link bandwidth is reserved for best-effort traffic 11) *Assumed cycle size is 8kHz (very widely used) 12) **Network provides a mechanism to request/assign resources for isochronous transmission (e.g. bandwidth, channel) and the default rule(s) for managing the resources 13) *Isochronous packets are never dropped nor delayed due to ANY other network traffic 14) *Granularity (not minimum) of bandwidth allocation is on the order of single bytes per cycle 15) By default, resource allocation is first-come-first-serve 16) **Network will automatically reclaim previously allocated but currently unused resources 17) **Isochronous traffic is not disrupted when a station/session is added/removed to/from the network 18) Allows bridging to isoch 802.11e 19) Allows bridging to isoch 1394 An end-to-end throttling mechanism, like what has been discussed in CM, would not satisfy the RE requirements.
https://grouper.ieee.org/groups/pp-dialog/drafting-committee/20060710/Ops%20Manual%202006-07-07-v11-redline.pdf
Microsoft Word - Ops Manual 2006-07-07-v11-redline.doc July 7, 2006 1 5.3.8 Compliance with laws 1 All Standards meetings shall be conducted in compliance with all applicable laws.
https://grouper.ieee.org/groups/802/3/10G_study/email/msg01564.html
Ed also pointed out that 1394 has some ways of dealing with this.
https://grouper.ieee.org/groups/802/15/pub/2005/15-05-0353-03-003c-draft-tg3c-system-requirements.doc
Draft TG3c System Requirements March, 1994 DOC: IEEE P802.11-94/xxx July, 2005 IEEE P802.15-05-0353-03-003c IEEE P802.15 Wireless Personal Area Networks Project IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs) Title Draft TG3c System Requirements Date Submitted [15 July, 2005] Source [Alireza Seyedi] [Philips] [345 Scarborough Rd, Briarcliff Manor, NY, 10510, USA] Voice: [+1-914-945-6318] Fax: [+1-914-945-6580] E-mail: [alireza.seyedi@philips.com] Re: [] Abstract [Draft of TG3c System Requirements.
https://grouper.ieee.org/rac/private/email/msg00358.html
. >> >> The distinction between standards is getting fuzzy: 1394 over CAT-5, >> security over multiple transports, multiple transports over the >> same PHYs.
https://grouper.ieee.org/rac/private/email/msg01256.html
Similarly, one might wish to communicate specific EUI-48 values within 1394 correspond to S***'s CD player software interface.  
https://grouper.ieee.org/groups/802/3/ca/email/msg00082.html
Cell: +1 (819) 609-1394 E-Mail:  francois.menard@xxxxxxxxxxx       Follow-Ups : Re: [802.3_NGEPON] ONU ASIC and wavelength plans From: Francois Menard Re: [802.3_NGEPON] ONU ASIC and wavelength plans From: Marek Hajduczenia References : Re: [802.3_NGEPON] ONU ASIC and wavelength plans From: Shawn Esser Re: [802.3_NGEPON] ONU ASIC and wavelength plans From: Marek Hajduczenia Re: [802.3_NGEPON] ONU ASIC and wavelength plans From: Barry Colella Re: [802.3_NGEPON] ONU ASIC and wavelength plans From: Marek Hajduczenia Re: [802.3_NGEPON] ONU ASIC and wavelength plans From: Barry Colella Re: [802.3_NGEPON] ONU ASIC and wavelength plans From: Francois Menard Re: [802.3_NGEPON] ONU ASIC and wavelength plans From: Glen Kramer Re: [802.3_NGEPON] ONU ASIC and wavelength plans From: Harstead, Ed (Nokia - US) Prev by Date: Re: [802.3_NGEPON] ONU ASIC and wavelength plans Next by Date: Re: [802.3_NGEPON] ONU ASIC and wavelength plans Previous by thread: Re: [802.3_NGEPON] ONU ASIC and wavelength plans Next by thread: Re: [802.3_NGEPON] ONU ASIC and wavelength plans Index(es): Date Thread
https://grouper.ieee.org/groups/802/3/af/public/aug02/agenda_0802.pdf
Shorted conductors, pairs or loop- back plug (4) Define a capability detection function that works with a powered and an unpowered device August 19 - 21, 2002 DTE Power via MDI TF DTE Power Objectives (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
https://grouper.ieee.org/groups/msc/upamd/email/msg00025.html
Like the 1394 standards for wireless, this would provide another example of the importance and usefulness of having and following standards that any consumer or engineering manager could point to - which ultimately helps us all.  
https://grouper.ieee.org/rac/private/email/msg00271.html
The relevant standards include CSMA/CD (IEEE Std 802.3, ISO 8802-3), Token Bus (IEEE Std 802.4, ISO 8802-4), Token Ring (IEEE Std 802.5, ISO/IEC 8802-5), IEEE Std 802.6 (ISO/IEC DIS 8802-6), FDDI (ISO 9314-2) and WLAN (IEEE 802.11, ISO/IEC 8802-11) . b) The "company_id" defined in IEEE Std 1212-1991, IEEE Standard Control and Status Register (CSR) Architecture, is referenced by IEEE Std 896.2-1991, IEEE Standard for Futurebus+(TM) Physical Layer Specification and Profiles, and IEEE Std 1596-1992, IEEE Standard for Scalable Coherent Interface, as well as IEEE Std 1394-1995, IEEE Standard for a High Performance Serial Bus.
https://grouper.ieee.org/rac/private/email/doc00029.doc
Currently, the IEEE oversees four Registration Authorities: · Manufacturer ID · The Organizationally Unique Identifier/Company_id a) Individual Address Blocks · The EtherType Field · TEDS Extension Identifiers A list to standards that make use of each Registration Authority below: Organizationally Unique Identifier/Company id · 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 Std 802.6 (ISO/IEC DIS 8802-6) · FDDI (ISO 9314-2) · IEEE Std 1212-1991 Control and Status Register (CSR) · IEEE Std 896.2-1991 Futurebus+Physical Layers and Profiles · IEEE Std 1596-1995 Scalable Coherent Interface · IEEE Std 1394-1995 Serial Bus · ANSI X3. 131 1994 SCSI Manufacture id · IEEE Std 802.3 Clause 16 EtherType Field · IEEE Std 802.3 Extension Transducer Electronic Data Sheet (TEDS) Identification Number · IEEE Std 1451.2 Status Website status: the URL for the IEEE Registration Authority is http://standards.ieee.org/regauth/index.html.
https://grouper.ieee.org/groups/802/3/re_study/email/msg00288.html
While I like talker and listener, these may be too 1394 centric, so perhaps others can chime in?
https://grouper.ieee.org/groups/802/3/ca/email/msg00086.html
Cell: +1 (819) 609-1394 E-Mail:  francois.menard@xxxxxxxxxxx       Follow-Ups : Re: [802.3_NGEPON] ONU ASIC and wavelength plans From: Francois Menard References : Re: [802.3_NGEPON] ONU ASIC and wavelength plans From: Shawn Esser Re: [802.3_NGEPON] ONU ASIC and wavelength plans From: Marek Hajduczenia Re: [802.3_NGEPON] ONU ASIC and wavelength plans From: Barry Colella Re: [802.3_NGEPON] ONU ASIC and wavelength plans From: Marek Hajduczenia Re: [802.3_NGEPON] ONU ASIC and wavelength plans From: Barry Colella Re: [802.3_NGEPON] ONU ASIC and wavelength plans From: Francois Menard Re: [802.3_NGEPON] ONU ASIC and wavelength plans From: Glen Kramer Re: [802.3_NGEPON] ONU ASIC and wavelength plans From: Harstead, Ed (Nokia - US) Re: [802.3_NGEPON] ONU ASIC and wavelength plans From: Francois Menard Prev by Date: Re: [802.3_NGEPON] ONU ASIC and wavelength plans Next by Date: Re: [802.3_NGEPON] ONU ASIC and wavelength plans Previous by thread: Re: [802.3_NGEPON] ONU ASIC and wavelength plans Next by thread: Re: [802.3_NGEPON] ONU ASIC and wavelength plans Index(es): Date Thread
https://grouper.ieee.org/rac/private/email/msg00442.html
The relevant standards include CSMA/CD (IEEE Std 802.3, ISO 8802-3), Token Bus (IEEE Std 802.4, ISO 8802-4), Token Ring (IEEE Std 802.5, ISO/IEC 8802-5), IEEE Std 802.6 (ISO/IEC DIS 8802-6), FDDI (ISO 9314-2) and WLAN (IEEE 802.11, ISO/IEC 8802-11) . b) The "company_id" defined in IEEE Std 1212-1991, IEEE Standard Control and Status Register (CSR) Architecture, is referenced by IEEE Std 896.2-1991, IEEE Standard for Futurebus+(TM) Physical Layer Specification and Profiles, and IEEE Std 1596-1992, IEEE Standard for Scalable Coherent Interface, as well as IEEE Std 1394-1995, IEEE Standard for a High Performance Serial Bus.
https://grouper.ieee.org/groups/802/15/pub/2003/15-03-0516-00-0030-draft-editorial-and-enhancements.doc
An 802.15.4/802.15.3 bridge, e.g. the security control pad, could forward the message between the two networks. 2. 1394 frame convergence sublayer (FCSL) and/or USB FCSL.
https://grouper.ieee.org/groups/pp-dialog/drafting-committee/20060710/Ops%20Manual%202006-07-07-v11-clean.pdf
In contrast, the re-use of an IEEE Standard 802.3 physical layer 39 device for IEEE Standard 1394 would require a new Letter of Assurance because its re-use is a 40 new fundamental application. 41 42 [Note to Drafting Committee: Seeking better examples; suggestions welcome] 43 44
https://grouper.ieee.org/groups/802/15/pub/2002/May02/02167r0P802-15_TG3-Minutes-St.-Louis-to-Sydney.doc
Gilb mentioned that the at the 1394 conference, it was mentioned that TGe dropped delayed ACK and was going to burst ACK.