Simple light weight encoders that > compress 9 or > 10 to one have been suggested to allow this content to then > be sent to a > remote device over 1394 or other networks.

Simple light weight encoders that compress 9 or 10 to one have been suggested to allow this content to then be sent to a remote device over 1394 or other networks.

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.

Simple light weight encoders that compress 9 or 10 to one have been suggested to allow this content to then be sent to a remote device over 1394 or other networks.

Cell: +1 (819) 609-1394 E-Mail:  francois.menard@xxxxxxxxxxx       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 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

Cell: +1 (819) 609-1394 E-Mail:  francois.menard@xxxxxxxxxxx       Follow-Ups : Re: [802.3_NGEPON] ONU ASIC and wavelength plans From: Liudekun Re: [802.3_NGEPON] ONU ASIC and wavelength plans From: Harstead, Ed (Nokia - US) 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 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

Cell: +1 (819) 609-1394 E-Mail:  francois.menard@xxxxxxxxxxx       Follow-Ups : 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

I could imagine one that is used to tag all IEC 61883-type packets (the normal tagging and formatting system for consumer-electronics type streams in 1394). -- --------------------------------------------------------------- Michael D.

Flatman IEEE 802.3 Chair/Liaison Mr Grow/Mr Flatman IEEE 802.11Chair Mr Kerry, IEEE 802.15 Mr Heile IEEE 1394 Mr P.

2001, 1394 Trade Association.

We are also looking at a 1394 traffic model (low quality video model).

Message Formats M1M0 M3M2 M5M4 M7M6 M9M8 TM10 MP=1Ack2 NPAck D1D0 D3D2 D5D4 D7D6 D9D8 D11D10 D13D12 D15D14 Message Next Page 0, 7FF: Reserved 1~6: Null, One UP, Two UP, One UP + RF code, OUI, PHY ID 7: 100Base-T2 8: 1000BASE-T with Two AbilityP 9~2047: Future Use S1S0 S3S2 A0S4 A2A1 A4A3 A6A5 RFA7 NPAck D1D0 D3D2 D5D4 D7D6 D9D8 D11D10 D13D12 D15D14 Base Page 0, 1F: Reserved 1: 802.3 2: 802.9 3: 802.5 4: IEEE 1394 10 100X10F T4100XF aPP RES If IEEE 802.3 Clause 28 U1U0 U3U2 U5U4 U7U6 U9U8 TU10 MP=0Ack2 NPAck D1D0 D3D2 D5D4 D7D6 D9D8 D11D10 D13D12 D15D14 Unformatted Next Page1, 1000BaseTU0, U1, Master-Slave Config U2: M Port or Single Port U3: Full Duplex U4: 1000BASE-T Half Duplex Reserved=0 T2 mutually exclusive with 1000BASE-T (single Msg Pg) Valuable Coding space is taken up by legacy and not used.

Reconciliation sub layer Layer Model MAC and Higher layers Page 5 Clause 28 background Established for copper technologies and can Negotiate Multiple speeds Clause 28 state machines verified over years and have been made robust 7 years of AN Interoperability testing shows that most issues are associated with Software/Drivers that control the AN process (Device Management) The protocol and state machine itself is robust Most problems show up when system does not properly use the information provided by the AN protocol[2] Initial interoperability tests focused on accuracy of AN State Machines but later new tests were added to focus on Device Management to address system level issues (Reference: [2] UNH- IOL Clause 28 AN management system test suite Page 6 Advantages of using Clause 28 Auto-Negotiation function located below the PMD layer (Fig 28-2) [4] Perfect position of sub layer within PHY Ability to negotiate multiple speeds Ability to work with different signaling NRZ and non NRZ signaling (MLS) Does not depend on PCS encoding Self Clocking Interoperability issues have been identified and most issues are associated with Device Management The state machine has been field proven over multiple PHY generations Page 7 Clause 28 Base Page Clause 28 Base Page definition S0 S1 S2 S3 S4 A0 A1 A2 A3 A4 A5 A6 A7 RF Ack NP Next Page Acknowledge Remote Fault Page 8 Proposed 802.3ap Base Page Clause 28 Base Page definition S0 S1 S2 S3 S4 A0 A1 A2 A3 A4 A5 A6 A7 RF Ack NP IEEE Std 1394 00100 Reserved for future Auto-Negotiation development11111 IEEE 802.3ap Backplane Ethernet10100 IEEE Std 802.5 11000 IEEE Std 802.9 ISLAN-16T01000 IEEE Std 802.310000 Reserved for future Auto-Negotiation development00000 Selector descriptionS 0 S 1 S 2 S 3 S 4 Proposed selector field for 802.3ap TBDA7 Reserved for Future TechnologyA4 TBDA6 Pause OperationA5 Reserved for Future TechnologyA3 802.3ap 10Gb/s 4-LaneA2 802.3ap 10Gb/s 1-LaneA1 802.3ap 1Gb/s 1-LaneA0 Technology field bit assignmentsBit Proposed 802.3 Base page bit assignments Next Page Acknowledge Remote Fault Page 9 Next Page Assignment Continue to have Next Page for future proofing and to negotiate additional parameters if any Next Page encodings same as Clause 28.2.3.4 Page 10 Functional reference diagram Use Clause 28 functional reference diagram Technology dependent PMAs for 802.3ap Page 11 Transmit & Receive state machines Use Clause 28.3 State diagrams and transmit/receive/arbitration state machine definitions for exchanging base and next pages [4] The state diagram timers to use clause 28.3.2 definitions Some of the timer variables could be redefined for faster link convergence Goal: maximum 3 sec for link convergence NLP Receive link integrity state diagram is not needed and all reference in state machines will be removed for 802.3ap Page 12 Management Data Interface Use Clause 45 MDIO interface and Register space [4] Clause 22 Management frame format Clause 45.4 Electrical interface definition Clause 45.2.1 PMA/PMD register set definition Use Clause 45 interface (ST=00) to access Clause 45 registers Access Clause 22 registers if present in a legacy device through Clause 45 management interface (Register 2.5.0 & STcode =01) Other options considered: Using Clause 22 mechanism to access Clause 45 register set (Leverage mechanism defined by 802.3ah EFM [5]) Since there is no need to access control bits relevant to 10/100/1000 twisted pair operation it is proposed to use clause 45 interface to access clause 45 register space Page 13 Management Registers Use Clause 45.2.1 PMA/PMD register set [4][5] Define additional bits and registers for 802.3ap Lot of space available for future proofing Define 1.0.5:2 speed selector bits for 1G speeds: 0x00=10Gb/s; 0x01 taken by EFM; 0x02=1Gb/s Add 1Gb/s speed ability bit to Register 1.4.3 to indicate 1G speed (Table 45-5) Bit 1.5.0 to indicate clause 22 registers implemented and accessed through clause 45 interface Bit 1.5.1 indicates PMA/PMD device present in package Define 1.7.4:3 (two bits) to indicate different 802.3ap PMA/PMD types Add additional bits to the 10G PMA/PMD extended abilities register (Register 1.11) to indicate 802.3ap PMD types (Bits:1.11:3:2); Bit 1.11.0 taken by 10GBASE-CX4 and 1.11.1 possibly by 10GBASE-T Continue to use Registers 1.9 and 1.10 for Transmit/Receive functions Define 1.110 to 1.1xx new registers for 802.3ap specific functions Page 14 Summary Locate Auto-Neg function to be below PMD as shown in layer model (Figure 28-2) [4] New base page and selector fields for 802.3ap Backplane Ethernet Use Proposed SERDES compatible FLP [1] Use Clause 28 state machines for exchanging pages [4] Provide an informative annex for operation with legacy devices not supporting 802.3ap Auto-Negotiation Page 15 References [1] SERDES compatible FLP AN proposal for 802.3ap, July 04 Plenary http://ieee802.org/3/ap/public/jul04/szczepanek_02_0704.pdf [2] UNH-IOL Clause 28 Auto-Negotiation Management System Test Suite, UNH IOL Ethernet Interoperability Testing presentation http://ftp.iol.unh.edu/fec/anegSystem.pdf http://www.nbl.org.tw/nbl_old/nbl-iol-workshop/07_Ethernet_Overview.pdf [3] Earlier Auto-Neg presentations to Backplane Ethernet SG/TF http://www.ieee802.org/3/bladesg/public/mar04/chang_01_0304.pdf http://www.ieee802.org/3/ap/public/may04/ganga_01_0504.pdf [4] IEEE Std 802.3-2002, IEEE Std 802.3ae-2002 [5] IEEE Std 802.3ak-2004, P802.3ah approved draft D3.3 (to be published as IEEE Std 802.3ah-2004 )

All options on the table Hybrid E/O Module 1550 nm E/O Module Single Mode Fiber 1-30+ Residences 100 Base FX GBE Idealized Port cost At Market Port Cost Easily Upgraded to 10 GE or WDM for higher rates Ethernet in the Last Mile - 14 Active MDUActive MDU MDU oriented media Hybrid E/O Module 1550 nm E/O Module Single Mode Fiber 1-30+ Apartments Also suitable for urban hybrid deployment (business & residential users) 100 Base FX GBE Similar to curb criteria Ethernet in the Last Mile - 15 Digital Access GatewayDigital Access Gateway (CPE)(CPE) 100 Base FX Potentially hybrid media Hybrid E/O Module IEEE 1394 100 BaseT CATV POTS Remote Power over Copper Loop Services platform

In contrast, the re-use of an IEEE Standard 802.3 physical layer 23 device for IEEE Standard 1394 would require a new Letter of Assurance because its re-use is a 24 new fundamental application.

(ADSL2+, 1394, …) • Any other outreach (companies, countries) of importance to inform or engage?

Your may also want to read IEEE 1394, which (some of us feel) should be useful for background and is also highly desirable to support in a reasonably transparent-to-traffic fashion.

Several years ago we had a similar experience with the IEEE 1394 and USB specifications.

. 802.3af, 802.3at TIA-862 building automation and security devices Remote cameras IP telephone Multimedia devices supported by IEEE Std 1394-2008.

. > > > > >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. > > > > DVJ > > > > > > David V.

In contrast, the re-use of an IEEE Standard 802.3 physical layer device for IEEE Standard 1394 would require a new Letter of Assurance because its re-use is a new fundamental application.

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

. > > >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. > > DVJ > > > David V.

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

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.