RFC 5066 Comment on PME initialization and aggregation
"Baud, Yann" <[email protected]> Thu, 18 Nov 2010 12:05:09 +0100
| Newsgroups | gmane.ietf.hubmib |
|---|---|
| Message-ID | <14D81EC6B257AC4AA681E4969BCC58BE01B8F05D@szexchange.schmid-telecom.com> |
This is a multi-part message in MIME format.
--===============0858503049==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
boundary="----_=_NextPart_001_01CB8710.779F471B"
This is a multi-part message in MIME format.
------_=_NextPart_001_01CB8710.779F471B
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
I wish to comment on the penultimate paragraph of RFC 5066 section
3.1.3:
=20
*Quoted*
Note that the PCS port does not have to be operationally 'down' for
the connection to succeed. In fact, a dynamic PME addition (and
removal) MAY be implemented with an available PME being initialized
first (by setting its ifAdminStatus to 'up') and then added to an
operationally 'up' PCS port, by modifying a respective ifStackTable
(and respective ifInvStackTable) entry.
=20
In fact, PME addition to a PCS is impossible once the PME has been
initialized, because
the discovery and aggregation phases, which are done using ITU-T G.994.1
(G.Hs), must occur before PME training and
activation in the PME initialization process. Once the PME is
initialized, it is impossible=20
to configure the aggregation on the peer pme (IEEE 802.3 2008 61.4.7).
=20
I would much welcome a clarification on this paragraph.
=20
Best Regards,
Yann
------_=_NextPart_001_01CB8710.779F471B
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.5730.13" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D666162610-18112010><FONT face=3DArial>I wish to =
comment on the=20
penultimate paragraph of RFC 5066 section 3.1.3:</FONT></SPAN></DIV>
<DIV><SPAN class=3D666162610-18112010><FONT =
face=3DArial></FONT></SPAN> </DIV>
<DIV><SPAN class=3D666162610-18112010><FONT=20
face=3DArial>*Quoted*</FONT></SPAN></DIV>
<DIV><SPAN class=3D666162610-18112010><FONT =
face=3DArial> Note=20
that the PCS port does not have to be operationally 'down'=20
for</FONT></SPAN></DIV>
<DIV><SPAN class=3D666162610-18112010><FONT =
face=3DArial> the=20
connection to succeed. In fact, a dynamic PME addition=20
(and<BR> removal) MAY be implemented with an available =
PME=20
being initialized<BR> first (by setting its =
ifAdminStatus to=20
'up') and then added to an<BR> operationally 'up' PCS =
port, by=20
modifying a respective ifStackTable<BR> (and =
respective=20
ifInvStackTable) entry.</FONT></SPAN></DIV>
<DIV><FONT face=3DArial><SPAN class=3D666162610-18112010><FONT=20
face=3DArial></FONT></SPAN></FONT> </DIV>
<DIV><SPAN class=3D666162610-18112010><FONT face=3DArial>In fact, PME =
addition to a=20
PCS is impossible once the PME has been initialized, =
because</FONT></SPAN></DIV>
<DIV><SPAN class=3D666162610-18112010><FONT face=3DArial>the discovery =
and=20
aggregation phases, which are done using ITU-T G.994.1 =
(G.Hs), must=20
occur before PME training and</FONT></SPAN></DIV>
<DIV><FONT face=3DArial><SPAN class=3D666162610-18112010>activation in =
the PME=20
initialization process. </SPAN><SPAN =
class=3D666162610-18112010>Once the PME=20
is initialized, it is impossible </SPAN></FONT></DIV>
<DIV><SPAN class=3D666162610-18112010><FONT face=3DArial>to configure =
the=20
aggregation on the peer pme (IEEE 802.3 2008 =
61.4.7).</FONT></SPAN></DIV>
<DIV><SPAN class=3D666162610-18112010><FONT =
face=3DArial></FONT></SPAN> </DIV>
<DIV><SPAN class=3D666162610-18112010><FONT face=3DArial>I would much =
welcome a=20
clarification on this paragraph.</FONT></SPAN></DIV>
<DIV><SPAN class=3D666162610-18112010><FONT =
face=3DArial></FONT></SPAN> </DIV>
<DIV><SPAN class=3D666162610-18112010><FONT face=3DArial>Best=20
Regards,</FONT></SPAN><SPAN class=3D666162610-18112010></DIV>
<DIV><SPAN class=3D666162610-18112010></SPAN><FONT face=3DArial>Y<SPAN=20
class=3D666162610-18112010>ann</SPAN></FONT></DIV></SPAN></BODY></HTML>
------_=_NextPart_001_01CB8710.779F471B--
--===============0858503049==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
Hubmib mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/hubmib
--===============0858503049==--