RE: [EFM-Copper] Initialization of the PHY-Aggregation
Mathias,
You are correct, 61.2.2.7.3 specifies that the PMI_Aggregate_register in
the CPE is remotely writable. But no mechanism is shown in 61.3.
I'm submitting a comment to add text to 61.3.
--Barry
-----Original Message-----
From: mathias.riess@infineon.com [mailto:mathias.riess@infineon.com]
Sent: Thursday, August 28, 2003 8:25 AM
To: stds-802-3-efm-copper@ieee.org
Subject: [EFM-Copper] Initialization of the PHY-Aggregation
Hi all,
as already outlined during the copper conference call last Tue
(Aug.
26) I still see some ambiguities for the entire initialization of the
PHY
aggregation using G.994. I understood the entire initialization process
of
the PAF functionality in that way, that
1.it should be discovered which PMIs of a remote device might be
aggregated
(using the Npar(3) code points remote_discovery_register and the
commands
'Get', 'Set if clear' and 'Clear if same'). Respective code points are
defined within the EFM tree of G.994.
2. the current aggregation functionality will be programmed on both -O
and
-R side in the PMI_Aggregate_Registers.
I assume that these 2 actions need to be done during the G.994 sessions.
From my point of view Item 1 is already covered, but I still miss
respective
code points for item 2, for writing/reading the PMI_aggregate_register
in
the G.994 EFM tree.
One suggestion would be that a new code point 'PMI_aggregate' will be
added.
If this bit is set, the Npar(3) code point remote_discovery_register
will be
interpreted as PMI_aggregate_register and the PMI_aggregate_register of
the
-r device will be written as described in section 61.2.2.7.3 (page 339
line
49 - page 340 line 8).
If we can agree on this procedure, a respective description needs to be
added to section 61.3.12.
Any feedback is welcome, may be some of the assumptions I stated above
are
not correct.
Thanks
Mathias