From hubmib-bounces@ietf.org Tue Jan 10 20:56:38 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EwVE6-00041c-8k; Tue, 10 Jan 2006 20:56:38 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EwVE3-0003zN-Rf
	for hubmib@megatron.ietf.org; Tue, 10 Jan 2006 20:56:36 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA00741
	for <hubmib@ietf.org>; Tue, 10 Jan 2006 20:55:15 -0500 (EST)
Received: from nj300815-ier2.net.avaya.com ([198.152.12.103])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EwVKr-0000p2-E9
	for hubmib@ietf.org; Tue, 10 Jan 2006 21:03:38 -0500
Received: from tiere.net.avaya.com (tiere.net.avaya.com [198.152.12.100])
	by nj300815-ier2.net.avaya.com (Switch-3.1.7/Switch-3.1.7) with ESMTP
	id k0B1sFAa015831
	for <hubmib@ietf.org>; Tue, 10 Jan 2006 20:54:15 -0500
Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com
	[135.64.105.51])
	by tiere.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id
	k0B1rTcS027982
	for <hubmib@ietf.org>; Tue, 10 Jan 2006 20:53:29 -0500 (EST)
content-class: urn:content-classes:message
MIME-Version: 1.0
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
Date: Wed, 11 Jan 2006 03:56:26 +0200
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F09D86554@is0004avexu1.global.avaya.com>
Thread-Topic: Resolution to comments from David Perkins
Thread-Index: AcX03f2h619QtlE5T2CtfEVssU+WmwhWdKlgAAZxzxA=
From: "Romascanu, Dan \(Dan\)" <dromasca@avaya.com>
To: "Matt Squire" <MSquire@HatterasNetworks.com>,
	"Lior khermosh" <lior.khermosh@passave.com>
X-Scanner: InterScan AntiVirus for Sendmail
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 995b2e24d23b953c94bac5288c432399
Cc: Hub MIB <hubmib@ietf.org>
Subject: [Hubmib] RE: Resolution to comments from David Perkins
X-BeenThere: hubmib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Ethernet Interfaces an Hub MIB WG <hubmib.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/hubmib>,
	<mailto:hubmib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:hubmib@ietf.org>
List-Help: <mailto:hubmib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/hubmib>,
	<mailto:hubmib-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0012076874=="
Sender: hubmib-bounces@ietf.org
Errors-To: hubmib-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0012076874==
content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C61652.3B57D728"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C61652.3B57D728
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Thanks Matt, for addressing Dave's comments.=20
=20
Dave, can you please look at the responses submitted by Lior and Matt to
your comments and let us know if your principal concerns have been
answered? We would like to issue revised versions of the I-Ds, but it
would be useful to make sure that the issues that you raised found an
appropriate resolutions.=20
=20
Thanks and Regards,
=20
Dan
=20
=20
=20
=20


  _____ =20

	From: Matt Squire [mailto:MSquire@HatterasNetworks.com]=20
	Sent: Wednesday, January 11, 2006 3:43 AM
	To: Romascanu, Dan (Dan); Lior khermosh
	Cc: David T. Perkins; Hub MIB
	Subject: RE: Resolution to comments from David Perkins
=09
=09

	Hi David, Dan  -=20

	=20

	Below are my responses to the various comments. =20


------_=_NextPart_001_01C61652.3B57D728
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:v =3D=20
"urn:schemas-microsoft-com:vml" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word" xmlns:st1 =3D=20
"urn:schemas-microsoft-com:office:smarttags"><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2800.1528" name=3DGENERATOR><!--[if !mso]>
<STYLE>v\:* {
	BEHAVIOR: url(#default#VML)
}
o\:* {
	BEHAVIOR: url(#default#VML)
}
w\:* {
	BEHAVIOR: url(#default#VML)
}
.shape {
	BEHAVIOR: url(#default#VML)
}
</STYLE>
<![endif]--><o:SmartTagType name=3D"PersonName"=20
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"></o:SmartTagT=
ype><!--[if !mso]>
<STYLE>st1\:* {
	BEHAVIOR: url(#default#ieooui)
}
</STYLE>
<![endif]-->
<STYLE>@font-face {
	font-family: Tahoma;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; }
P.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
	COLOR: purple; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
	COLOR: purple; TEXT-DECORATION: underline
}
SPAN.EmailStyle17 {
	COLOR: navy; FONT-FAMILY: Arial; mso-style-type: personal-reply
}
DIV.Section1 {
	page: Section1
}
</STYLE>
</HEAD>
<BODY lang=3DEN-US vLink=3Dpurple link=3Dblue>
<DIV><SPAN class=3D686515101-11012006><FONT face=3DArial color=3D#0000ff =

size=3D2><STRONG><EM>Thanks Matt, for&nbsp;addressing Dave's comments.=20
</EM></STRONG></FONT></SPAN></DIV>
<DIV><SPAN class=3D686515101-11012006><STRONG><EM><FONT face=3DArial =
color=3D#0000ff=20
size=3D2></FONT></EM></STRONG></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D686515101-11012006><STRONG><EM><FONT face=3DArial =
color=3D#0000ff=20
size=3D2>Dave, can you please look at the responses submitted by Lior =
and Matt to=20
your comments and let us know if your principal concerns have been =
answered? We=20
would like to issue revised versions of the I-Ds, but it would be useful =
to make=20
sure that the issues that you raised found an appropriate resolutions.=20
</FONT></EM></STRONG></SPAN></DIV>
<DIV><SPAN class=3D686515101-11012006><STRONG><EM><FONT face=3DArial =
color=3D#0000ff=20
size=3D2></FONT></EM></STRONG></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D686515101-11012006><STRONG><EM><FONT face=3DArial =
color=3D#0000ff=20
size=3D2>Thanks and Regards,</FONT></EM></STRONG></SPAN></DIV>
<DIV><SPAN class=3D686515101-11012006><STRONG><EM><FONT face=3DArial =
color=3D#0000ff=20
size=3D2></FONT></EM></STRONG></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D686515101-11012006><STRONG><EM><FONT face=3DArial =
color=3D#0000ff=20
size=3D2>Dan</FONT></EM></STRONG></SPAN></DIV>
<DIV><SPAN class=3D686515101-11012006><STRONG><EM><FONT face=3DArial =
color=3D#0000ff=20
size=3D2></FONT></EM></STRONG></SPAN>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV><BR>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> Matt Squire=20
  [mailto:MSquire@HatterasNetworks.com] <BR><B>Sent:</B> Wednesday, =
January 11,=20
  2006 3:43 AM<BR><B>To:</B> Romascanu, Dan (Dan); Lior =
khermosh<BR><B>Cc:</B>=20
  David T. Perkins; Hub MIB<BR><B>Subject:</B> RE: Resolution to =
comments from=20
  David Perkins<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV class=3DSection1>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">Hi David, =
Dan &nbsp;&#8211;=20
  <o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">Below are =
my=20
  responses to the various comments.&nbsp;=20
</SPAN></FONT></P></DIV></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C61652.3B57D728--


--===============0012076874==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib

--===============0012076874==--




From hubmib-bounces@ietf.org Tue Jan 10 21:00:20 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EwVHg-0004tt-Dk; Tue, 10 Jan 2006 21:00:20 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EwVHe-0004to-Ds
	for hubmib@megatron.ietf.org; Tue, 10 Jan 2006 21:00:18 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA00919
	for <hubmib@ietf.org>; Tue, 10 Jan 2006 20:58:57 -0500 (EST)
Received: from nj300815-ier2.net.avaya.com ([198.152.12.103])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EwVOS-0000tx-Q0
	for hubmib@ietf.org; Tue, 10 Jan 2006 21:07:21 -0500
Received: from tiere.net.avaya.com (tiere.net.avaya.com [198.152.12.100])
	by nj300815-ier2.net.avaya.com (Switch-3.1.7/Switch-3.1.7) with ESMTP
	id k0B1w2eZ017182
	for <hubmib@ietf.org>; Tue, 10 Jan 2006 20:58:03 -0500
Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com
	[135.64.105.51])
	by tiere.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id
	k0B1vGcS028582
	for <hubmib@ietf.org>; Tue, 10 Jan 2006 20:57:17 -0500 (EST)
content-class: urn:content-classes:message
MIME-Version: 1.0
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
Subject: RE: [Hubmib] Working Group Last Call
Date: Wed, 11 Jan 2006 04:00:14 +0200
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F09D86555@is0004avexu1.global.avaya.com>
Thread-Topic: [Hubmib] Working Group Last Call
Thread-Index: AcXeZV+SDV0nkLSJQeWspSjCLFi9OAA6tzBpDcCP7zA=
From: "Romascanu, Dan \(Dan\)" <dromasca@avaya.com>
To: "Edward Beili" <EdwardB@actelis.com>, "C. M. Heard" <heard@pobox.com>,
	"Hub MIB" <hubmib@ietf.org>
X-Scanner: InterScan AntiVirus for Sendmail
X-Spam-Score: 0.6 (/)
X-Scan-Signature: 850245b51c39701e2700a112f3032caa
Cc: 
X-BeenThere: hubmib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Ethernet Interfaces an Hub MIB WG <hubmib.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/hubmib>,
	<mailto:hubmib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:hubmib@ietf.org>
List-Help: <mailto:hubmib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/hubmib>,
	<mailto:hubmib-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1849915283=="
Sender: hubmib-bounces@ietf.org
Errors-To: hubmib-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1849915283==
content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C61652.C2F65A9C"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C61652.C2F65A9C
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Edward,
=20
Please let me know if you will be submitting a revised rfc3636bis draft
soon.=20
=20
I would like to call for WG Last call with the EFMCu and rfc3636bis
I-Ds, but I want to make sure that you have done all needed updates
before.=20
=20
Thanks and Regards,
=20
Dan
=20
=20
=20
=20


  _____ =20

	From: hubmib-bounces@ietf.org [mailto:hubmib-bounces@ietf.org]
On Behalf Of Edward Beili
	Sent: Wednesday, November 02, 2005 4:49 AM
	To: C. M. Heard; Hub MIB
	Subject: RE: [Hubmib] Working Group Last Call
=09
=09

	Mike,
	Apart from rpMauMediaAvailable, which is similar to
ifMauMediaAvailable
	there's nothing else that looks like another candidate for the
IANA-MAU-MIB module.
=09
	While looking at ifMauMediaAvailable I realized that I forgot to
add two new values defined in the 802.3ah, clause 30.5.1.1.4:
	1. availableReduced - link normal, reduced bandwidth, applies
only to 2BASE-TL and 10PASS-TS
	2. ready - at least one PME available, applies only to 2BASE-TL
and 10PASS-TS
=09
	In addition a clarification should be added to 'pmdLinkFault'
that all PMA/PMDs in the aggregation group must detect a fault.
=09
	I will add these to the new revision of the 3636bis I-D.
=09
	Regards,
	-Edward
=09
=09
	-----Original Message-----
	From:   C. M. Heard [mailto:heard@pobox.com]
	Sent:   Mon 10/31/2005 11:52 PM
	To:     Hub MIB
	Cc:     Edward Beili
	Subject:        Re: [Hubmib] Working Group Last Call
	On Mon, 24 Oct 2005, Edward Beili wrote:
	> 1. Currently the values for the ifMauTypeListBits are defined
in the
	>    IANA-MAU-MIB, while the values for the
ifMauAutoNegCapabilityBits,
	>    ifMauAutoNegCapAdvertisedBits and
ifMauAutoNegCapReceivedBits objects
	>    are defined in MAU-MIB.
	>    While none of the newly added MAU types (10GBASE-CX4,
2BASE-TL,
	>    10PASS-TS, 100BASE-LX/BX, 1000BASE-LX/BX/PX) supports
	>    auto-negotiation, this may change in the future (e.g. I
don't see
	>    a reason not to support it on P2P (-LX/BX) optical links as
well as
	>    for some new types). I suggest to put TC for these objects
in the
	>    IANA-MAU-MIB as well.
=09
	On Sun, 30 Oct 2005, C. M. Heard wrote:
	> If there is a realistic possibility that future MAU types will
	> support auto-negotiation, then it is probably advantageous to
	> put the capability list under IANA maintenance so that it
(like
	> the MAU types) can be expanded quickly upon approval of a new
	> 802.3 standard.  The main counter-argument would be that doing
	> this would lengthen an already protracted process.  In making
a
	> decision it might be useful to solicit input from the 802.3 WG
	> regarding the likelihood of the introduction of new
	> auto-negotiation capabilities.
=09
	I just noticed that there is (at least) one more object in the
MAU-MIB
	that has MAU-type-specific values, and that is the enumerated
INTEGER
	object ifMauMediaAvailable.  Additional enumerated values for
this
	object may well be required for future MAU types, so there may
be
	reason to put its enumerations under IANA maintenance as well.
=09
	Edward, are there any more such objects lurking in the MAU-MIB?
=09
	Mike
=09
=09
=09


------_=_NextPart_001_01C61652.C2F65A9C
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>RE: [Hubmib] Working Group Last Call</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2800.1528" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D121155801-11012006><FONT face=3DArial color=3D#0000ff =

size=3D2><STRONG><EM>Edward,</EM></STRONG></FONT></SPAN></DIV>
<DIV><SPAN class=3D121155801-11012006><STRONG><EM><FONT face=3DArial =
color=3D#0000ff=20
size=3D2></FONT></EM></STRONG></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D121155801-11012006><STRONG><EM><FONT face=3DArial =
color=3D#0000ff=20
size=3D2>Please let me know if you will be submitting a revised =
rfc3636bis draft=20
soon. </FONT></EM></STRONG></SPAN></DIV>
<DIV><SPAN class=3D121155801-11012006><STRONG><EM><FONT face=3DArial =
color=3D#0000ff=20
size=3D2></FONT></EM></STRONG></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D121155801-11012006><STRONG><EM><FONT face=3DArial =
color=3D#0000ff=20
size=3D2>I would like to&nbsp;call for&nbsp;WG Last call with the EFMCu =
and=20
rfc3636bis I-Ds, but I want to make sure that you have done all needed =
updates=20
before. </FONT></EM></STRONG></SPAN></DIV>
<DIV><SPAN class=3D121155801-11012006><STRONG><EM><FONT face=3DArial =
color=3D#0000ff=20
size=3D2></FONT></EM></STRONG></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D121155801-11012006><STRONG><EM><FONT face=3DArial =
color=3D#0000ff=20
size=3D2>Thanks and Regards,</FONT></EM></STRONG></SPAN></DIV>
<DIV><SPAN class=3D121155801-11012006><STRONG><EM><FONT face=3DArial =
color=3D#0000ff=20
size=3D2></FONT></EM></STRONG></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D121155801-11012006><STRONG><EM><FONT face=3DArial =
color=3D#0000ff=20
size=3D2>Dan</FONT></EM></STRONG></SPAN></DIV>
<DIV><SPAN class=3D121155801-11012006></SPAN>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV><BR>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> hubmib-bounces@ietf.org=20
  [mailto:hubmib-bounces@ietf.org] <B>On Behalf Of </B>Edward=20
  Beili<BR><B>Sent:</B> Wednesday, November 02, 2005 4:49 =
AM<BR><B>To:</B> C. M.=20
  Heard; Hub MIB<BR><B>Subject:</B> RE: [Hubmib] Working Group Last=20
  Call<BR></FONT><BR></DIV>
  <DIV></DIV><!-- Converted from text/plain format -->
  <P><FONT size=3D2>Mike,<BR>Apart from rpMauMediaAvailable, which is =
similar to=20
  ifMauMediaAvailable<BR>there's nothing else that looks like another =
candidate=20
  for the IANA-MAU-MIB module.<BR><BR>While looking at =
ifMauMediaAvailable I=20
  realized that I forgot to add two new values defined in the 802.3ah, =
clause=20
  30.5.1.1.4:<BR>1. availableReduced - link normal, reduced bandwidth, =
applies=20
  only to 2BASE-TL and 10PASS-TS<BR>2. ready - at least one PME =
available,=20
  applies only to 2BASE-TL and 10PASS-TS<BR><BR>In addition a =
clarification=20
  should be added to 'pmdLinkFault' that all PMA/PMDs in the aggregation =
group=20
  must detect a fault.<BR><BR>I will add these to the new revision of =
the=20
  3636bis I-D.<BR><BR>Regards,<BR>-Edward<BR><BR><BR>-----Original=20
  Message-----<BR>From:&nbsp;&nbsp; C. M. Heard [<A=20
  =
href=3D"mailto:heard@pobox.com">mailto:heard@pobox.com</A>]<BR>Sent:&nbsp=
;&nbsp;=20
  Mon 10/31/2005 11:52 PM<BR>To:&nbsp;&nbsp;&nbsp;&nbsp; Hub=20
  MIB<BR>Cc:&nbsp;&nbsp;&nbsp;&nbsp; Edward=20
  Beili<BR>Subject:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Re: =
[Hubmib]=20
  Working Group Last Call<BR>On Mon, 24 Oct 2005, Edward Beili =
wrote:<BR>&gt; 1.=20
  Currently the values for the ifMauTypeListBits are defined in=20
  the<BR>&gt;&nbsp;&nbsp;&nbsp; IANA-MAU-MIB, while the values for the=20
  ifMauAutoNegCapabilityBits,<BR>&gt;&nbsp;&nbsp;&nbsp;=20
  ifMauAutoNegCapAdvertisedBits and ifMauAutoNegCapReceivedBits=20
  objects<BR>&gt;&nbsp;&nbsp;&nbsp; are defined in=20
  MAU-MIB.<BR>&gt;&nbsp;&nbsp;&nbsp; While none of the newly added MAU =
types=20
  (10GBASE-CX4, 2BASE-TL,<BR>&gt;&nbsp;&nbsp;&nbsp; 10PASS-TS, =
100BASE-LX/BX,=20
  1000BASE-LX/BX/PX) supports<BR>&gt;&nbsp;&nbsp;&nbsp; =
auto-negotiation, this=20
  may change in the future (e.g. I don't see<BR>&gt;&nbsp;&nbsp;&nbsp; a =
reason=20
  not to support it on P2P (-LX/BX) optical links as well=20
  as<BR>&gt;&nbsp;&nbsp;&nbsp; for some new types). I suggest to put TC =
for=20
  these objects in the<BR>&gt;&nbsp;&nbsp;&nbsp; IANA-MAU-MIB as =
well.<BR><BR>On=20
  Sun, 30 Oct 2005, C. M. Heard wrote:<BR>&gt; If there is a realistic=20
  possibility that future MAU types will<BR>&gt; support =
auto-negotiation, then=20
  it is probably advantageous to<BR>&gt; put the capability list under =
IANA=20
  maintenance so that it (like<BR>&gt; the MAU types) can be expanded =
quickly=20
  upon approval of a new<BR>&gt; 802.3 standard.&nbsp; The main =
counter-argument=20
  would be that doing<BR>&gt; this would lengthen an already protracted=20
  process.&nbsp; In making a<BR>&gt; decision it might be useful to =
solicit=20
  input from the 802.3 WG<BR>&gt; regarding the likelihood of the =
introduction=20
  of new<BR>&gt; auto-negotiation capabilities.<BR><BR>I just noticed =
that there=20
  is (at least) one more object in the MAU-MIB<BR>that has =
MAU-type-specific=20
  values, and that is the enumerated INTEGER<BR>object=20
  ifMauMediaAvailable.&nbsp; Additional enumerated values for =
this<BR>object may=20
  well be required for future MAU types, so there may be<BR>reason to =
put its=20
  enumerations under IANA maintenance as well.<BR><BR>Edward, are there =
any more=20
  such objects lurking in the=20
MAU-MIB?<BR><BR>Mike<BR><BR><BR></FONT></P></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C61652.C2F65A9C--


--===============1849915283==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib

--===============1849915283==--




From hubmib-bounces@ietf.org Tue Jan 10 22:26:29 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EwWd3-000516-Kp; Tue, 10 Jan 2006 22:26:29 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EwV25-0008PR-IQ
	for hubmib@megatron.ietf.org; Tue, 10 Jan 2006 20:44:14 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA29843
	for <hubmib@ietf.org>; Tue, 10 Jan 2006 20:42:50 -0500 (EST)
Received: from [72.15.200.20] (helo=mailserv.hatterasnetworks.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EwV8e-0000QV-28
	for hubmib@ietf.org; Tue, 10 Jan 2006 20:51:14 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 10 Jan 2006 20:43:15 -0500
Message-ID: <8052E2EA753D144EB906B7A7AA39971403F40294@mailserv.hatteras.com>
Thread-Topic: Resolution to comments from David Perkins
Thread-Index: AcX03f2h619QtlE5T2CtfEVssU+WmwhWdKlg
From: "Matt Squire" <MSquire@HatterasNetworks.com>
To: "Romascanu, Dan \(Dan\)" <dromasca@avaya.com>,
	"Lior khermosh" <lior.khermosh@passave.com>
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 5b5d984330980e5b896a3a77a3695f69
X-Mailman-Approved-At: Tue, 10 Jan 2006 22:26:26 -0500
Cc: Hub MIB <hubmib@ietf.org>
Subject: [Hubmib] RE: Resolution to comments from David Perkins
X-BeenThere: hubmib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Ethernet Interfaces an Hub MIB WG <hubmib.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/hubmib>,
	<mailto:hubmib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:hubmib@ietf.org>
List-Help: <mailto:hubmib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/hubmib>,
	<mailto:hubmib-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1689550718=="
Sender: hubmib-bounces@ietf.org
Errors-To: hubmib-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1689550718==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C61650.63D0AA58"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C61650.63D0AA58
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi David, Dan  -=20

=20

Below are my responses to the various comments.  Many of the editorial
problems (spelling error, etc.) won't be listed here as they don't
really require discussion.  I separated out what I consider the biggest
issues and talk about them first, then include responses to your
individual comments in the parts that follow. =20

=20

- Matt

=20

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

=20

=20

Bigger issues:

=20

a) "dot3" vs "efm".  There were multiple comments related to whether
various names in the MIB should be "efm..." or "dot3...".  Admittedly,
the reviewed version of the MIB had a mix of the two as it historically
went from "EFM OAM" to "EFM Common" to "OAM" to whatever.  To be clear,
the OAM functionality of 802.3 is applicable to any Ethernet interface,
not just those defined in 802.3ah, so it applies to 1000BASE-X,
10/100BASE-T, etc.  For that reason, I'd suggest we move everything to a
"dot3..." prefix rather than an "efm..." prefix, and to use "Ethernet
OAM" as a description rather than "EFM OAM" (which appears in a few
places). =20

=20

b) Improving description clauses.  You commented that all description
clauses for tables need to contain XYZ, similarly for rows.  I've
attempted to improve the description clauses based on your feedback.  =20

=20

c) Removing frame reception conditions in MIB descriptions.  You had
multiple comments related to certain sections of the MIB (the OAM peer
objects) where the descriptions included detailed information on what
the values of various frame fields had to be in order to process the
frame.  As an example, the MIB had:

         An OAMPDU is indicated by a valid frame with (1) destination

         MAC address equal to that of the reserved MAC address for Slow

         Protocols (See 43B of [802.3ah]), (2) a lengthOrType field

         equal to the reserved type for Slow Protocols, (3) and a Slow

         Protocols subtype equal to that of the subtype reserved for

         OAM. =20

You basically indicated that such details weren't needed in those
sections.  I'm more than fine with removing it.  It was added several
revisions ago when someone asked for more details about "when exactly
does this value get updated?"  At that point I added descriptions like
the above to spell out as much as possible what has to be received for
this field to be updated.  I'd personally love to remove it, as it's
just a bunch of extra words to me, but more than that I don't want to
add it back again later.=20

=20

d) You found a couple of problems with my RTF-RFC conversion process.
In what was Section 4.3, there was a mapping of SNMP to 802.3
attributes, and you rightfully pointed out there should be a section
header and introduction sentence or two.  At some point when going from
the word RTF file to the text RFC, those were deleted.  In the next rev,
there will be a Section 4.4 just for the SNMP/802.3 attribute mappings.


=20

e) You pointed out some inconsistencies (and potential improvements) on
explaining when entries are created/deleted from various tables.  My
suggestion going forward is to detail when entries are created in the
primary control table (dot3OamTable), indicating they are automatically
created for every Ethernet interface that supports OAM.  And then say
that other tables have entries automatically created for every entry in
that primary table.  The way things were written,=20

 - dot3OamPeerTable didn't always have an entry - it was written so that
you could add an entry once you learned the peer, then leave it in
there, but an entry wasn't required even if you were running OAM.  I
suggest changing that so that an entry is always required, and the
various objects have mechanisms to indicate whether their values validly
reflect an actual OAM peer, or whether there is no peer.  This reflects
several of your comments

 - dot3OamLoopbackTable didn't require an entry if the implementation
didn't support loopback (there was a condition "if loopback is
supported" in the description).  Likewise, the dot3EventConfigTable
didn't always require an entry (it's an optional function as well).
Given the optional nature of certain functions (loopback, events, etc),
I wasn't sure whether the tables should always have an entry (with some
kind of 'not supported' indicator), or whether the tables should only
have entries if the function is supported, or if there was some other
approach.  I'm open to suggestions. =20

=20

f) In the dot3OamAdminState, I had a description that included:=20

         Note that the value of this object is ignored when the

         interface is not operating in full-duplex mode. OAM is not

         supported on half-duplex links. =20

]] I'm not sure what "ignored" means here.

]] I don't believe that "ignored" is the right term.

]] Shouldn't whether the interface is in half or full-duplex

]] show up in the value of object dot3OamOperStatus?

]] I'm assuming that only interfaces that can operate

]] in full-duplex mode will be in this table. That

]] should of been said in the table DESCRIPTION clause.

This is a little trickier than I originally thought.  OAM was intended
for full-duplex links, and some of the functions don't operate on
half-duplex links.  So I was trying to say that OAM shouldn't run on
half-duplex links, so setting the admin state doesn't matter (hence the
ignored).  I'm open to finding better ways of saying that.  Looking back
at 802.3ah, I was unable to find the sections that indicate OAM doesn't
come up on half-duplex links.  So I believe what happens is that OAM
would come up but some things might not work (anybody have a different
interpretation)?  If that's the case (as I think now), then I will
probably have to rewrite that description to capture the proper
behavior.  I'm not sure that reflecting the duplex of the interface in
the dot3OamStatus is either good or necessary.  The OAM tables should
exist whether the interface is full/half/auto, so the potential to be in
full-duplex may be required, but you don't have to be in full-duplex
mode to have an entry in the OAM table (your duplex may be auto, TBD
later). =20

=20

g) In the loobpack object, right now there is a separate status and
action attribute, so that you can set the action to start/stop loopback,
then go read the status.  You suggested a combined status/action object.
First, I don't know what that means.  Can you point me to an example in
some other document?  Second, the current separation of action/status
was a result of discussions on either the list or at a meeting.  All of
the examples that I was able to find or were given to me for similar
function had one attribute to initiate the action and another to return
the result.  =20

=20

h) You suggested combining dot3OamErrSymPeriodWindowHi and
dot3OamErrSymPeriodWindowLo into one CounterBasedGauge64.  This was
discussed on the list previously and it was decided that was not
possible.  The discussion centered on CounterBasedGauge64s as being
read-only counters.  In this case, we need settable parameters as we're
trying to setup a threshold.  So I was told CounterBasedGauge64s were
not applicable in that scenario, and that we needed to have two separate
attributes with rules to combine them. =20

=20

i) On the dot3EventLogTable, you had questions about the maximum size
and handling:

]] On this table, can it have an infinite number of entries?

]] Most likely not. In other tables, there is some indication

]] that says the max number (not always available), but

]] always something that says to either stop adding entries,

]] or delete the oldest, or some other algorithm to replace

]] the least important with a new one.

I suggest saying the size of the table is implementation dependent, and
that older entries are automatically replaced with newer entries when
the table gets full.  Is that satisfactory? =20

=20

j)  In the event log table, you asked what were the running totals and
event totals. After reading 802.3ah, you indicated you know what they
mean, but a re-write of the description is in order.  Here's my proposed
DESCRIPTION:

       "Each Event Notification TLV contains a running total of the

       number of times an event has occurred, as well as the number of

       times an Event Notification for the event has been transmitted.

       For non-threshold crossing events, the number of events

       (dot3OamLogRunningTotal) and the number of resultant Event

       Notifications (dot3OamLogEventTotal) should be identical.=20

      =20

       For threshold crossing events, since multiple occurrences may

       be required to cross the threshold, these values are likely

       different.  This value represents the total number of times one

       or more of these occurrences have resulted in an Event

       Notification (for example, 51 when 3253 symbol errors have

       occurred since the last reset, which has resulted in 51 symbol

       error threshold crossing events since the last reset). =20

       "

k) You made suggestions on rearranging the hierarchy so that there is a
dot3OamNotifications off dot3OamMIB, and having the notifications
reference that.  I'm fine with changing the tree that way so
Notifications are moved up in the tree. =20

=20

l) In the reviewed versions, the compliance section has some
unconditionally optional groups, allowing for a mix and match set of
implementations.  You suggested defining a minimum and maximum
compliance group.  I don't have a suggestion here yet.  I need to think
about it more, but would be interested in hearing opinions from anyone
else. =20

=20

 =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D

=20

In the text below, I basically include the version of the draft with
your comments in it as was sent to the mailing list.  From that text, I
removed certain sections that didn't have any comments, or had only what
I considered uncontroversial editorial comments.  Where text was
removed, << Text deleted >> appears.  Your comments are still prefixed
with ]], while I put "MBS:" in front of my response. =20

=20

]] Reviewed 8-sept-2005, david t. perkins, dperkins@snmpinfo.com

]]

]] Global comments:

]]  Comments are inserted in-line and each comment line

]]  is preceded by "]]".

]]

]]1) A line of "-"s is used as a separator. This is problematic

]]   and if a separator is desired, the it should be something

]]   like -- **************************************************

]]   (If the number of "-"s in a line is X, and mod(X,4)=3D=3D1,

]]   then a MIB compiler will report a parse error.)

MBS:  No problem doing the change. =20

=20

]]

]]2) All the tables should have consistent info in the

]]   DESCRIPTION clauses for the table and row definitions.

]]   Minimally, the tables DESCRIPTION clause should describe

]]   the table, and specify what determines the number of

]]   entries in the table.

]]   Minimally, the DESCRIPTION clause for rows should indicate

]]   how rows are added and removed from tables. And if can

]]   be done via direct SNMP operations, then the identification

]]   of the RowStatus object.

]]   Note that there is additional information that must be

]]   contained in the DESCRIPTION clause as specified in

]]   "Guidelines ... of MIB Documents"

]]   <draft-ietf-ops-mib-review-guidelines-04.txt>

]]   [MIBguidelines]

=20

MBS: I've attempted to update the objects as appropriate.  They'll

need to be reviewed to ensure they meet the goals. =20

=20

]]

]]3) For enumerated values, each value be described in the

]]   DESCRIPTION text of the object or TC definition.

=20

MBS: I found a couple instances where not every enumerated value was

spelled out, and tried to correct that (you have specific comments to

these at the various instances of the omission). =20

=20

]]

]]5) The term "byte" should be replaced by term "octet".

=20

MBS: Changed. =20

=20

]]6) The abbreviations "i.e.", and "e.g." are confused.

]]   I suggest that you always write out "that is",

]]   and "for example".

=20

MBS: I replaced the few occurences of "e.g." with "for example".

Personally, I don't believe that it improves (or hurts) anything, but

I'm more than willing to do it.  The abbreviation "i.e." wasn't used

in the document (that I could find). =20

=20

]]7) A few typos were found by idnits script found at

]]   http://ietf.levkowetz.com/tools/idnits/

=20

MBS: I'll be sure to run the script on next revision before

submission. =20

=20

  Ethernet Interfaces and Hub MIB WG                             =20

  Internet Draft                                    Matt Squire

  Document: draft-ietf-hubmib-efm-mib-03.txt        Hatteras Networks

  Expires: September 2005                           March, 2005

 =20

 =20

              Ethernet in the First Mile (EFM) OAM MIB

=20

 << Text deleted >>

 =20

 =20

3.   Overview

 =20

  Ethernet networks have evolved over the past 30 years from simple

  LANs to a variety of other applications, including wide area

  networks.  To address some of these emerging markets, the IEEE

  802.3ah task force defined additional clauses for the IEEE 802.3

  standard [802.3-2002] to better address Ethernet deployments in the

  public access network. =20

]] To make it clear, I'd change the above to the following:

]]   To address some of these emerging markets, the IEEE

]]   802.3ah task force defined additional clauses in [802.3ah]

]]   for the IEEE 802.3 standard [802.3-2002] to better address

]]   Ethernet deployments in the public access network.

=20

MBS: Changed made. =20

 =20

]] Is 802.3ah work strictly for "public access networks"?

]] If not, then the phrase should be dropped or replaced.

=20

MBS: Access networks were the motivation for the task force, but the

results can be applied for any application.  So the phrase does

address why the work was initiated and completed, but does not fully

address applicability.  Instead of the suggestion, I added a sentence;

"Although Ethernet access deployments were the primary motivation for

the task force work, the results of the task force are not limited to

that application.  "

=20

=20

<< Text deleted >>

=20

 =20

4.1    Relation to other SNMP MIB Modules

 =20

  This objects defined in this document do not overlap with MIB-2

  [RFC1213], the interfaces MIB [RFC2863], or the Ethernet like

  interfaces MIB [RFC3635].  The objects defined here are defined for

  Ethernet like interfaces only and use the same ifIndex as the

  associated Ethernet interface.  Ethernet OAM can be implemented on

  any Ethernet like interface managed via these MIBs. =20

]] The "This" should be "The".=20

]] MIB-2 is obsolete, and I'm not sure what this section is

]] trying to say. I'm not sure that this functionality

]] can be applied on any "Ethernet-like" interfaces,

]] and not just on the interface types as specified

]] in [802.3ah]. =20

=20

MBS: The OAM functionality controlled by this MIB can be applied to

any Ethernet interface (for example, 10/100BASE-T).  This was an

explicit goal of the OAM sub taskforce.  This paragraph is attempting

to say that this MIB does not overlap with existing MIBs used to

manage Ethernet interfaces (several examples given via references).

However, it is noted that the indexing scheme is the same.  I can

certainly try to re-write it again to make that point better.  One

possible wording would be:

=20

  "The objects defined in this document manage OAM functionality=20

   introduced in [802.3ah]  These objects do not overlap with=20

   MIB-2 [RFC1213], the interfaces MIB [RFC2863], the Ethernet like=20

   interfaces MIB [RFC3635], or any other MIB currently used to=20

   manage various aspects of an Ethernet interface.  The objects=20

   defined here are defined for Ethernet like interfaces only and=20

   use the same ifIndex as the associated Ethernet interface. =20

   Ethernet OAM can be implemented on any Ethernet like interface."

=20

=20

 =20

4.2    Relation to other EFM MIB Modules

 =20

  The Ethernet OAM functionality and MIB Module is independent of the

  other functionality and MIB Modules derived from [802.3ah] for copper

  [802.3ah-copper] and EPON [802.3ah-epon]. =20

 =20

  Ethernet OAM may be implemented on point-to-multipoint EFM EPON

  interfaces.  However, because higher layer protocols that run over

  Ethernet interfaces are not designed for the partial connectivity

  provided by a point-to-multipoint interface, EPON provides a point

  to-point emulation layer (see [802.3ah] and [802.3ah-epon]) whereby

  the single EPON interface of 1-to-N connectivity is represented by N

  point-to-point interfaces.  Ethernet OAM, like any other protocol at

  the Ethernet layer or above (for example, bridging), utilizes the

  point-to-point emulation layer of EPON in that the EPON interface is

  viewed as N point-to-point Ethernet interfaces.  Thus OAM, and other

  protocols, do not need to be altered for the EPON environment. =20

 =20

  Ethernet OAM may be implemented on the 2BASE-TL and 10PASS-TS

  Ethernet-over-copper interfaces defined in EFM [802.3ah].  2BASE-TL

  and 10PASS-TS can be aggregated interfaces, meaning that they can use

  the ifStackTable of the Interfaces Group MIB [RFC2863] to manage a

  set of N (1 <=3D N <=3D 32) physical layers into a single Ethernet

  interface. =20

=20

=20

M. Squire            Expires - September 2005            [Page 5]=20




=20

                         EFM OAM MIB                March 2005

=20

=20

 =20

  The other Ethernet interfaces introduced in EFM [802.3ah] are simply

  new optical physical layers that are managed by minimal extensions to

  the MAU MIB [RFC3636] defining new types of Ethernet interfaces. =20

 =20

4.3    IANA Considerations

 =20

  The EFM OAM MIB requires the allocation of a single object identifier

  for its MODULE-IDENTITY under the MIB-2 tree.  IANA has not yet

  allocated this object identifier.

=20

]] This needs to be updated to follow the format as

]] specified in [MIBguidelines]

=20

MORE

=20

]] The list that follows seems out of place. At the minimum

]] there needs to be a section header and intro.

]]

=20

]] NOTE: I didn't check the list below for errors, such

]]       as omissions and spellings.

=20

MBS: The lack of header/intro is apparently an artifact of RTF->I-D

format conversion.  I'll fix it in the next revision.  The headers and

introduction exist in my RTF file. =20

=20

  [802.3ah] Clause 30, and managed objects defined in this document. =20

=20

 =20

  IEEE 802.3 Managed Object     Corresponding SNMP object

=20

]] In the below, it would be useful to also show the object class

]] (the oXXX) containing each attribute. For example, the MAU MIB

]] document (draft-ietf-hubmib-rfc3636bis-01.txt) does this.

=20

MBS: Easy enough to do (there's just oOAM). =20

=20

   .aOAMID                       IF-MIB ifIndex

 =20

5.   MIB Structure

 =20

  The common EFM MIB objects of this memo focus on the OAM capabilities

  introduced in IEEE 802.3ah.  The MIB objects are partitioned into six

]] Probably want [803.3ah] instead of just 802.3ah

MBS: Done

  different MIB groups.

 =20

  The dot3OamTable group manages the primary OAM objects of the

  Ethernet interface.  This group controls the state and status of OAM

  as well as the mode in which it operates. =20

 =20

  The dot3OamPeerTable maintains the current information on the status

  and configuration of the peer OAM entity on the Ethernet interface.=20

  Managed information includes the capabilities and function available

]] I think "capabilities" and "function" are the same, so

]] I would drop "and function".

MBS:  I'm not sure I agree with that.  Capabilities generally refers to
what the other guy can do, while functions refers to what it does.  Some
capabilities may be disabled or inoperable for many reasons.  So I'm
trying to say that the MIB covers both potential and actual
functionality. =20

=20

  on the peer OAM entity. =20

=20

=20

M. Squire            Expires - September 2005            [Page 7]=20




=20

                         EFM OAM MIB                March 2005

=20

=20

 =20

  The dot3OamLoopbackTable manages the loopback function introduced in

  EFM [802.3ah].  This table controls enabling and disabling loopback,

]] Is there a difference between "EFM [802.3af]" and "[802.3af]"?

]] If so, this needs to be reflected throughout the the

]] document. If not, then the "EFM" should be removed.

MBS: No difference,so I removed EFM.  The benefit of having it in

there is that many people know the project as EFM, even though this

function is not restricted to the physical layers of that project. =20

=20

  as well as indicating the loopback status of Ethernet OAM on this

  interface. =20

]] Above and through the document, the terms "Ethernet OAM",

]] and "EFM OAM" are used. Are these the same, or different?

]] If different, then this needs to be explained. If the

]] same, then one should be chosen and used consistently.

=20

MBS: There's no intended difference.  As the OAM functionality applies

to any Ethernet interface, I will go with Ethernet OAM rather than EFM

OAM. =20

=20

 << Text deleted >>

 =20

6.   MIB Definition

   =20

      =20

  EFM-COMMON-MIB DEFINITIONS ::=3D BEGIN=20

]] This module name doesn't follow the naming conventions

]] in the [MIBguidelines] document. However, I can't determine

]] if it should be DOT3-OAM-MIB, or "EFM-OAM-MIB".

MBS: It should be DOT3-OAM-MIB to me, so that's what I'll change it to.


=20

   IMPORTS=20

     MODULE-IDENTITY, mib-2, OBJECT-TYPE, Counter32, Unsigned32,=20

       Integer32, NOTIFICATION-TYPE

       FROM SNMPv2-SMI=20

     TEXTUAL-CONVENTION, MacAddress, TimeStamp

       FROM SNMPv2-TC=20

     CounterBasedGauge64

       FROM HCNUM-TC

     ifIndex =20

       FROM IF-MIB=20

     MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP

       FROM SNMPv2-CONF;=20

   =20

 =20

     efmOamMIB MODULE-IDENTITY=20

]] Not sure if should be efmOamMIB or dot3OamMIB

MBS: Changed to dot3OamMIB

=20

       LAST-UPDATED "200503220000Z"  -- March 22, 2005"

       ORGANIZATION=20

         "IETF Ethernet Interfaces and Hub MIB Working Group"

       CONTACT-INFO=20

         "WG Charter:=20

           http://www.ietf.org/html.charters/hubmib-charter.html=20

         Mailing lists:=20

=20

=20

M. Squire            Expires - September 2005            [Page 8]=20




=20

                         EFM OAM MIB                March 2005

=20

=20

           General Discussion: hubmib@ietf.org=20

           To Subscribe: hubmib-requests@ietf.org=20

           In Body: subscribe your_email_address=20

         Chair: Dan Romascanu, Avaya

           Tel:  +972-3-645-8414=20

           Email: dromasca at avaya dot com=20

         Editor: Matt Squire=20

           Hatteras Networks=20

           Tel:    +1-919-991-5460=20

           Fax:    +1-919-991-0743

           E-mail: msquire at hatterasnetworks dot com

         "

       DESCRIPTION

         "The MIB module for managing the new Ethernet OAM features

         introduced by the Ethernet in the First Mile task force (IEEE

         802.3ah).  The functionality presented here is based on IEEE

         802.3ah [802.3ah], released in October, 2004. =20

 =20

         In particular, this MIB focused on the changes to Clause 30 of

         the draft that are not specific to any physical layer.  These

         changes are primarily reflected in the new OAM features

         developed under this project, that can be applied to any

         Ethernet like interface. The OAM features are described in

         Clause 57 of [802.3ah].

]] First, is it clause 30 or 57.

]] Also, the above reads strangely. People that don't understand

]] exactly how IEEE documents are updated (which is very different

]] than how IETF documents are updated).

MBS:  Attempted re-wording below.  Hopefully this will make more sense

to you.    The functionality is described in one clause, but the

management attributes of that functionality are described in another. =20

      "

       In particular, this MIB focuses on the new OAM functions

       introduced in Clause 57 of [802.3ah].  The OAM functionality of

       Clasue 57 is controlled by new management attributes introduced

       in Clause 30 of [802.3ah].  The OAM functions are not specific

       to any particular Ethernet physical layer, and can be

       generically applied to any Ethernet interface of [802.3-2002]. =20

      "

=20

<< Text deleted >>=20

=20

     --

     -- Ethernet OAM Control group

     --

 =20

 =20

     dot3OamTable OBJECT-TYPE

       SYNTAX      SEQUENCE OF Dot3OamEntry

       MAX-ACCESS  not-accessible

       STATUS      current

       DESCRIPTION=20

         "Primary controls and status for the OAM capabilities of an

         Ethernet like interface.  There will be one row in this table

         for each Ethernet like interface in the system that supports

         the Ethernet OAM functions defined in [802.3ah]."  =20

       ::=3D { dot3OamMIB 1 }

]] I'm still unclear as to exactly which interfaces will be

]] in this table. For example, if a 10baseT interface card

]] is plugged into the device, will a new row show up?

]] Or is it only for the Cu and EPON interfaces?

]] And does some other configuration (outside of SNMP)

]] configuration have to be done?

]] I believe the answer is not, but want to determine

]] if aggregated interfaces can exist in the table?  =20

=20

MBS:  Any Ethernet interface that can appear in the Ethernet like MIB

table can appear here if OAM functionality is supported.  So the

answer to your questions are

=20

 - yes, if the interfaces support Ethernet OAM (which is optional)

 - no, it is not only for the Cu/EPON interfaces

 - no, no other configuration is required=20

=20

=20

=20

=20

     dot3OamEntry OBJECT-TYPE

       SYNTAX     Dot3OamEntry

       MAX-ACCESS not-accessible

=20

=20

M. Squire            Expires - September 2005            [Page 10]=20




=20

                         EFM OAM MIB                March 2005

=20

=20

       STATUS     current

       DESCRIPTION=20

         "An entry in the table, containing information on the Ethernet

         OAM function for a single Ethernet like interface."

       INDEX       { ifIndex }

       ::=3D { dot3OamTable 1 }

]] The SMI requires in the DESCRIPTION clause for a row,

]] a description of index objects that not defined in the

]] table.

MBS: Added a description that says when entries created/deleted and the
row status. =20

=20

     Dot3OamEntry ::=3D

       SEQUENCE {

         dot3OamAdminState                  INTEGER,

         dot3OamOperStatus                  INTEGER,

         dot3OamMode                        INTEGER,

         dot3OamMaxOamPduSize               Integer32,

         dot3OamConfigRevision              Unsigned32,=20

         dot3OamFunctionsSupported          BITS

       }

 =20

            =20

     dot3OamAdminState OBJECT-TYPE

       SYNTAX      INTEGER {

                     disabled(1),

                     enabled(2)

                   }

       MAX-ACCESS  read-write

       STATUS      current

       DESCRIPTION=20

         "This object is used to provision the default administrative

         OAM mode for this interface.  This object represents the

         desired state of OAM for this interface. =20

 =20

         The dot3OamAdminState always starts in the disabled(1) state

         until an explicity management action or configuration

]]                ^^^^^^spelling error

MBS: Fixed.

         information retained by the system causes a transition to the

         enabled(2) state.=20

 =20

         Note that the value of this object is ignored when the

         interface is not operating in full-duplex mode. OAM is not

         supported on half-duplex links.  "

       REFERENCE   "[802.3ah], 30.3.6.1.2"

       ::=3D { dot3OamEntry 1 }

]] I'm not sure what "ignored" means here.

]] I don't believe that "ignored" is the right term.

]] Shouldn't whether the interface is in half or full-duplex

]] show up in the value of object dot3OamOperStatus?

]] I'm assuming that only interfaces that can operate

]] in full-duplex mode will be in this table. That

]] should of been said in the table DESCRIPTION clause.

=20

MBS: This is a little tricky.  Certain functions in Ethernet OAM

assume full-duplex links.  So I tried to say that you should ignore

the provisioned enable/disable admin state if the link comes up

half-duplex, and just leave OAM disabled.  Certainly a link should

have the capacity to be full-duplex to appear in this table.  However,

if the interface hasn't negotiated duplex yet, we should still allow

it in the table so that OAM can be configured in case the link comes

up full-duplex. =20

=20

MBS: This behavior is certainly up for

interpretation.  We could allow OAm to operate on half-duplex links

though not every function will be available.  Open to suggestions. =20

 =20

     dot3OamOperStatus OBJECT-TYPE

       SYNTAX      INTEGER {

                     disabled(1),

                     linkfault(2),

                     passiveWait(3),

                     activeSendLocal(4),

                     sendLocalAndRemote(5),

                     sendLocalAndRemoteOk(6),

=20

=20

M. Squire            Expires - September 2005            [Page 11]=20




=20

                         EFM OAM MIB                March 2005

=20

=20

                     oamPeeringLocallyRejected(7),

                     oamPeeringRemotelyRejected(8),

                     operational(9)

                   }

]] What values indicate that ifAdmin status is set down

]] or testing?

]] What are the values when ifOperStatus is not up?

]] It seems like some of these could occur concurrently.

]] Is this possible?

=20

MBS:  if the physical layer is not up, OAM will be in linkfault state

(regardless of whether its down, testing, or anything else).  The

linkFault state is the starting state for any enabled OAM

implementation. There are OAM state machines in [802.3ah] that define

the 9 states above, and one and only one is possible at any time. =20

=20

=20

<< Text deleted >>

=20

=20

     dot3OamMaxOamPduSize OBJECT-TYPE

       SYNTAX      Integer32 (64..1522)

]] This should be Unsigned32.

]] Also, is 1522 really the max?

=20

MBS:  I'll change to Unsigned32 though its not clear to me why thats

better.  The maximum value, as defined in [802.3ah] is equal the

maximum untagged frame size (which is undergoing change in 802.3 as we

speak).  I'd like to put a variable in here that ties it to the

maxUntaggedFrameSize, but I don't know what that variable would be.

Numerically, it should currently be 1518, not 1522. =20

=20

       UNITS       "bytes"

       MAX-ACCESS  read-only

       STATUS      current=20

=20

=20

M. Squire            Expires - September 2005            [Page 13]=20




=20

                         EFM OAM MIB                March 2005

=20

=20

       DESCRIPTION=20

         "The largest OAMPDU that the OAM entity supports.  OAM

         entities exchange maximum OAMPDU sizes and negotiate to use

         the smaller of the two maximum OAMPDU sizes between the peers.

         This value is determined by the local implementation. =20

         "

       REFERENCE   "[802.3ah], 30.3.6.1.8"

       ::=3D { dot3OamEntry 4 }

            =20

 << Text deleted >>=20

 =20

     ------------------------------------------------------------------

     --

     -- Ethernet OAM Peer group

     --

 =20

 =20

=20

=20

M. Squire            Expires - September 2005            [Page 14]=20




=20

                         EFM OAM MIB                March 2005

=20

=20

     dot3OamPeerTable OBJECT-TYPE

       SYNTAX      SEQUENCE OF Dot3OamPeerEntry

       MAX-ACCESS  not-accessible

       STATUS      current

       DESCRIPTION=20

         "Information about the OAM peer for a particular Ethernet like

         interface. OAM entities communicate with a single OAM peer

         entity on full-duplex Ethernet links on which OAM is enabled

         and operating properly. =20

        =20

         In certain states, the OAM peer information is not available.

         Whether peer information is available is communicated via the

         dot3OamPeerStatus object.  When this object is inactive, all

         other information in the row is to be considered invalid.  "=20

       ::=3D { dot3OamMIB 2 }

]] Fix this table DESCRIPTION as per global comments

]] The issue of communicating that when the value of dot3OamPeerStatus

]] is 'inactive(2)' that the values of the other columns is

]] unknown, is difficult. Yes, it is said in the DESCRIPTION

]] clause for the row, but I suggest that you also put

]] that in the DESCRIPTION clause for each column. Also,

]] if possible, define a value for each column that is

]] returned when dot3OamPeerStatus is 'inactive(2)',

]] which CAN NOT be a valid value with dot3OamPeerStatus

]] has value 'active(1)'.

=20

MBS: I've attempted to incorporate this comment in the next revision,

and the invalid statement is repeated for every column.  Its not clear

how to devine unique invalid values for every column - for example a

bits field or an unsigned32 where all 2^32 values are allowed.  So I

wasn't able to implement that part of the comment for every column. =20

=20

     dot3OamPeerEntry OBJECT-TYPE

       SYNTAX      Dot3OamPeerEntry

       MAX-ACCESS  not-accessible

       STATUS      current

       DESCRIPTION=20

         "An entry in the table, containing information on the peer OAM

         entity for a single Ethernet like interface. =20

 =20

         Note that there is at most one OAM peer for each Ethernet like

         interface.  There is exactly one row in this table for each

         Ethernet like interface supporting OAM.  "

       INDEX       { ifIndex }

       ::=3D { dot3OamPeerTable 1 }

]] Fix. Note, I believe it would be clearer to say

]] (in the DESCRIPTION for the table) that a row

]] exists in this table for each row in the OAM control

]] table. =20

=20

MBS:  I'm not sure what you mean by the "OAM control table", but the

intent is that there is at most one row for every entry in the

dot3OamTable.  There may be zero rows in this table for an entry in

the dot3OamTable if the peer information has not been discovered

(yet).  I guess we could say there's always a row but that its

information is inactive(2) - is that your point?  That probably is

simpler.  =20

=20

 =20

     Dot3OamPeerEntry ::=3D

       SEQUENCE {

         dot3OamPeerStatus                   INTEGER,

         dot3OamPeerMacAddress               MacAddress,=20

         dot3OamPeerVendorOui                Dot3Oui,=20

         dot3OamPeerVendorInfo               Unsigned32,=20

         dot3OamPeerMode                     INTEGER,

         dot3OamPeerMaxOamPduSize            Integer32,

         dot3OamPeerConfigRevision           Unsigned32,

         dot3OamPeerFunctionsSupported       BITS

       }

 =20

     dot3OamPeerStatus OBJECT-TYPE

       SYNTAX      INTEGER {

                     active(1),

                     inactive(2)

                   }

       MAX-ACCESS  read-only

=20

=20

M. Squire            Expires - September 2005            [Page 15]=20




=20

                         EFM OAM MIB                March 2005

=20

=20

       STATUS      current

       DESCRIPTION=20

         "This object indicates whether the information in this row

         should be considered valid.  When active(1), the information

         is valid and represents the current peer of the OAM entity.

         When inactive(2), the information in this row is invalid. =20

 =20

         A value of inactive(2) is returned if the dot3OamOperStatus is

         disabled, passiveWait, or activeSendLocal.  For all other

         values of dot3OamOperStatus, a value of active(1) is returned.


         "

       ::=3D { dot3OamPeerEntry 1 }

]] The above doesn't seem possible. Please check.

]] It seems that only when dot3OamOperStatus has the

]] value of 'operational(9)' can this have value 'active(1)'

=20

MBS:  The intent is that you know about the peer entity before OAM

becomes fully operational(9).  As soon as you receive one frame from

the peer you know their basic info (there is a multi-frame exchange

required for initialization).  So I believe the statement is correct

as is. =20

=20

     dot3OamPeerMacAddress OBJECT-TYPE

       SYNTAX      MacAddress

       MAX-ACCESS  read-only

       STATUS      current

       DESCRIPTION=20

         "The MAC address of the peer OAM entity.  The MAC address is

         derived from the most recently received OAMPDU.  This value is

         initialized to all zeros (0x000000000000).  This value is

         invalid if the dot3OamPeerStatus is inactive. =20

]] This seems pretty convoluted. Why not say "The MAC address

]]   of the peer OAM entity.  The MAC address is

]]   derived from the most recently received valid OAMPDU.

]]   The value is all zeros (0x000000000000) when the peer's

]]   MAC address unknown, such as when the value of

]]   dot3OamPeerStatus is 'inactive(2)'."

]]

]]   By the way, it seems like a value could be obtained

]]   even when dot3OamPeerStatus is 'inactive(2)'.

]]   If so, is it useful?

=20

MBS;  I didn't see any use, hence the current indications that its
garbage if 'inactive'.  Related to your general comment of
simplification, I'll change the description to indicate zeros are
returned whenever the dot3OamPeerStatus is inactive(2). =20

=20

=20

         An OAMPDU is indicated by a valid frame with (1) destination

         MAC address equal to that of the reserved MAC address for Slow

         Protocols (See 43B of [802.3ah]), (2) a lengthOrType field

         equal to the reserved type for Slow Protocols, (3) and a Slow

         Protocols subtype equal to that of the subtype reserved for

         OAM.  "

]] Not sure this is needed in this definition.

=20

MBS;  I don't mind removing it - in fact I prefer to.  It was added

because I was asked to specfically define what causes this value to

change.  The event that causes an update to this value is the

reception of an OAMPDU, which is defined as above.  I'm thrilled to be

allowed to kill it. =20

=20

       REFERENCE   "[802.3ah], 30.3.6.1.5." =20

       ::=3D { dot3OamPeerEntry 2 }

       =20

 =20

     dot3OamPeerVendorOui OBJECT-TYPE

       SYNTAX      Dot3Oui

       MAX-ACCESS  read-only

       STATUS      current

       DESCRIPTION=20

         "The OUI of the OAM peer as reflected in the latest

         Information OAMPDU received with a Local Information TLV.  The

         OUI can be used to identify the vendor of the remote OAM

         entity.  This value is initialized to all zeros (0x000000).

         This value is considered invalid if the dot3OamPeerStatus is

         inactive.

]] Can this be written to be simpler (see above)

=20

MBS; Simplification will be attempted in next revision. =20

=20

=20

       REFERENCE   "[802.3ah], 30.3.6.1.16."

       ::=3D { dot3OamPeerEntry 3 }

       =20

 =20

     dot3OamPeerVendorInfo OBJECT-TYPE

       SYNTAX      Unsigned32

       MAX-ACCESS  read-only

       STATUS      current

       DESCRIPTION=20

         "The Vendor Info of the OAM peer as reflected in the latest

         Information OAMPDU received with a Local Information TLV.  The

         vendor information field is within the Local Information TLV,

         and can be used to determine additional information about the

         peer entity.  The format of the vendor information is

         unspecified within the 32-bit field.  This value is intialized

]]                                              spelling error^^^^^^^^^

MBS: fixed. =20

=20

         to all zeros (0x00000000).  This value is invalid if the

         dot3OamPeerStatus is inactive. =20

]] Can this be written to be simpler (see above)

]] Also, the 802.3af spec is confusing to me. From

]] it, the value seems like it should have

]] SYNTAX clause value of OCTET STRING(SIZE(4)).

]] But maybe an "Unsigned32" value is OK. If so,

]] the 0x00000000 is very strange. It should just be 0.

=20

MBS: I left this as Unsigned32 as its just a 32-bit field,

non-formatted field.  But I switched to 0 instead of 0x00000000.=20

 =20

       REFERENCE   "[802.3ah], 30.3.6.1.17." =20

       ::=3D { dot3OamPeerEntry 4 }

        =20

 << Text deleted >>=20

 =20

     ------------------------------------------------------------------

     --

=20

=20

M. Squire            Expires - September 2005            [Page 19]=20




=20

                         EFM OAM MIB                March 2005

=20

=20

     -- Ethernet OAM Loopback group

     --

 =20

 =20

     dot3OamLoopbackTable OBJECT-TYPE

       SYNTAX      SEQUENCE OF Dot3OamLoopbackEntry

       MAX-ACCESS  not-accessible

       STATUS      current

       DESCRIPTION=20

         "This table contains methods to control the loopback state of

         the local link as well as indicating the status of the

         loopback function. =20

 =20

         Loopback can be used to place the remote OAM entity in a state

         where every received frame (except OAMPDUs) are echoed back

         over the same interface on which they were received.   In this

         state, at the remote entity, 'normal' traffic is disabled as

         only the looped back frames are transmitted on the interface.

         Loopback is thus an intrusive operation that prohibits normal

         data flow and should be used accordingly.  "=20

       ::=3D { dot3OamMIB 3 }

]] See global comment about tables, and comment on table

]] dot3OamPeerTable.

MBS: done

=20

]] This table is used to put the remote end in loopback

]] and report the loopback status of the local and remote

]] ports

=20

]] I'm confused as to whether both local and remote ports

]] can be put in loopback. And if not, then what happens

]] if the peer has put the local port in loopback and

]] an attempt is made to put the peer's port (the remote

]] port) in loopback?

=20

MBS: Simultaneous loopback on both ends is not possible - the protocol

detects such an action and an election algorithm is used to determine

which port enters loopback state and which does not. =20

=20

     dot3OamLoopbackEntry OBJECT-TYPE

       SYNTAX      Dot3OamLoopbackEntry

       MAX-ACCESS  not-accessible

       STATUS      current

       DESCRIPTION=20

         "An entry in the table, containing information on the loopback

         status for a single Ethernet like interface.  There is an

         entry in this table for every Ethernet like interface on which

         supports OAM and loopback function within OAM (as indicated in

         dot3OamFunctionsSupported).  "

]] See previous comments on rows

MBS: Changed to indicated automatic creation and conditions. =20

=20

       INDEX       { ifIndex }

       ::=3D { dot3OamLoopbackTable 1 }

 =20

     Dot3OamLoopbackEntry ::=3D

       SEQUENCE {

         dot3OamLoopbackCommand            INTEGER,

         dot3OamLoopbackStatus             INTEGER,

         dot3OamLoopbackIgnoreRx           INTEGER

       }

 =20

     dot3OamLoopbackCommand OBJECT-TYPE

       SYNTAX      INTEGER {=20

                     noLoopback (1),

                     startRemoteLoopback (2),

                     stopRemoteLoopback (3)

                   }=20

       MAX-ACCESS  read-write

=20

=20

M. Squire            Expires - September 2005            [Page 20]=20




=20

                         EFM OAM MIB                March 2005

=20

=20

       STATUS      current=20

       DESCRIPTION=20

         "This attribute initiates or terminates remote loopback with

         an OAM peer.  Writing startRemoteLoopback(2) to this attribute

         cause the local OAM client to send a loopback OAMPDU to the

         OAM peer with the loopback enable flags set.  Writing

         stopRemoteLoopback(3) to this attribute will cause the local

         OAM client to send a loopback OAMPDU to the OAM peer with the

         loopback enable flags cleared.  Writing noLoopback to this

         attribute has no effect. =20

 =20

         Writes to this attribute are ignored unless the OAM status of

         this interface is 'operational' (dot3OamOperStatus). =20

                         =20

         The attribute always returns noLoopback on a read.  To

         determine the loopback status, use the attribute

         dot3OamLoopbackStatus.  "=20

       REFERENCE   "[802.3ah], 57.2.11"  =20

       ::=3D { dot3OamLoopbackEntry 1 }

]] This object and the next need to be combined into a

]] action/status object.

]] The combined object support all the enum values

]] for dot3OamLoopbackStatus (which would be read-only)

]] and startRemoteLoopback and stopRemoteLoopback

]] from this object. Writes of startRemoteLoopback

]] when remote is already loopbacked (or dot3OamOperStatus

]] is not operational) cause no operation.

]] Likewise, writes of stopRemoteLoopback when remote

]] is not loopbacked (or dot3OamOperStatus

]] is not operational) cause no operation.

]] Note: just don't know what happens when

]] current value is localLoopback. =20

=20

MBS: I can change it, but I'd like to be pointed to an example.  All

of the examples I've come across had two objects, one for the actions,

one for the status, which is where this model comes from.  During

discussion with the group, two objects were suggested as the desired

approach. =20

=20

<< Text deleted >>

 =20

 =20

     ------------------------------------------------------------------

=20

=20

M. Squire            Expires - September 2005            [Page 22]=20




=20

                         EFM OAM MIB                March 2005

=20

=20

     --

     -- Ethernet OAM Statistics group

     --

 =20

 =20

     dot3OamStatsTable OBJECT-TYPE

       SYNTAX      SEQUENCE OF Dot3OamStatsEntry

       MAX-ACCESS  not-accessible

       STATUS      current

       DESCRIPTION=20

         "Statistics for the OAM function on a particular Ethernet like

         interface."=20

       ::=3D { dot3OamMIB 4 }

]] See previous comments on tables.

MBS: Done

=20

]] Add a note in the commentary section as to why the counters

]] in this table are Counter32 instead of Counter64!

MBS: Done.  The size of the counters was selected to match the size of
the counters as defined in 802.3.

=20

=20

 << Text deleted >>

      =20

     dot3OamUnsupportedCodesTx OBJECT-TYPE

       SYNTAX      Counter32

       UNITS       "frames"

       MAX-ACCESS  read-only

       STATUS      current

       DESCRIPTION=20

         "A count of the number of OAMPDUs transmitted on this

         interface with an unsupported op-code. =20

]] This is very strange.

]] Why would you send an "unsupported code"?

]] How would you know that you sent an "unsupported code"?

=20

MBS: Granted it seems a little strange.  The variable is supported in

the 802.3ah standard, so I decided to expose it via the MIB.  Since

Ethernet OAM could be supported in the HW or in the SW, the thought

was someone might try to do things where the underlying layer doesn't

support that thing (for example, loopback), and you might want to know

about it. =20

=20

=20

 << Text deleted >.=20

    =20

     dot3OamFramesLostDueToOam OBJECT-TYPE

]] Strange descriptor. How about "dot3OamDroppedTxFrames"

=20

MBS: I'm trying to match the names in 802.3ah as closely as possible

to make the implmeentaiton easier.  In 802.3, its called

FramesLostDueToOam.  The reason its not "OamDroppedTxFrames" is

because that might sound like OAM frames are dropped, when really any

frame might be dropped because OAM took precedence. =20

=20

=20

=20

       SYNTAX      Counter32

       UNITS       "frames"

       MAX-ACCESS  read-only

       STATUS      current

       DESCRIPTION=20

         "A count of the number of frames that were dropped by the OAM

         multiplexer.  Since the OAM mulitplexer has multiple inputs

         and a single output, there may be cases where frames are

         dropped due to transmit resource contention.  This counter is

         incremented whenever a frame is dropped by the OAM layer.

         When this counter is incremented, no other counters in this

         MIB are incremented. =20

                      =20

         Discontinuities of this counter can occur at re-initialization

         of the management system, and at other times as indicated by

         the value of the ifCounterDiscontinuityTime.  "

       REFERENCE   "[802.3ah], 30.3.6.1.46." =20

       ::=3D { dot3OamStatsEntry 17 }

    =20

 =20

     ------------------------------------------------------------------

     --

     -- Ethernet OAM Event Configuration group

     --

 =20

 << Text deleted >>=20

 =20

     dot3OamErrSymPeriodWindowHi OBJECT-TYPE

]] This needs to be combined with the next object

]] and given syntax CounterBasedGauge64

=20

MBS: This was discussed on the list.  The discussion said that

CounterBasedGauge64 is read-only and since this is a writable value,

it wouldn't apply. =20

=20

<< Text deleted >>

            =20

     dot3OamErrFrameWindow OBJECT-TYPE

       SYNTAX      Unsigned32

       UNITS       "tenths of a second"

       MAX-ACCESS  read-write

       STATUS      current

       DESCRIPTION=20

         "The amount of time (in 100ms increments) over which the

]] why not just say "in tenth of a second intervals" instead

]] of "in 100ms intervals"

MBS: 100ms seems easier to say then "tenths of a second"

         threshold is defined.  The default value is 10 (1 second). =20

                        =20

        If dot3OamErrFrameThreshold frame errors occur within a window

        of dot3OamErrFrameWindow seconds (measured in tenths of

        seconds), an Event Notification OAMPDU should be generated with

        an Errored Frame Event TLV indicating the threshold has been

        crossed in this window.  "

       REFERENCE   "[802.3ah], 30.3.6.1.36" =20

       ::=3D { dot3OamEventConfigEntry 9 }

      =20

=20

=20

M. Squire            Expires - September 2005            [Page 37]=20




=20

                         EFM OAM MIB                March 2005

=20

=20

      =20

     dot3OamErrFrameThreshold OBJECT-TYPE

       SYNTAX      Unsigned32

]] What happens when the value is zero?

=20

MBS: This would result in an event notification being sent at the end

of every measuring period.  So if the window were 30sec, you'd get an

OAMPDU every 30s saying how many errored frame there were.  Some may

consider this useless,but others thought it a way to get regular

periodic updtes on these error counters (e.g. tell me what the values

are every 30s). =20

=20

=20

 << Text deleted >>

=20

 =20

     ------------------------------------------------------------------

     --=20

     -- Ethernet OAM Event Status group=20

     --=20

 =20

     dot3OamEventLogTable   OBJECT-TYPE=20

       SYNTAX       SEQUENCE OF Dot3OamEventLogEntry=20

       MAX-ACCESS   not-accessible=20

       STATUS       current=20

       DESCRIPTION=20

]] See comments on tables

=20

]] On this table, can it have an infinite number of entries?

]] Most likely not. In other tables, there is some indication

]] that says the max number (not always available), but

]] always something that says to either stop adding entries,

]] or delete the oldest, or some other algorithm to replace

]] the least important with a new one.

=20

MBS: Added words to say that size is implemetnation dependent, and

that older entries should be automtically deleted to make room for

newer entries. =20

=20

         "This table records a history of the events that have occurred

         at the Ethernet OAM level.  These events can include locally

         detected events, which may result in locally generated

         OAMPDUs, and remotely detected events, which are detected by

         the OAM peer entity and signaled to the local entity via

         Ethernet OAM.  Ethernet OAM events can be signaled by Event

         Notification OAMPDUs or by the flags field in any OAMPDU.  "

]] Need to indicate that there are threshold crossing events

]] and nonthreshold events. For each, indicate the columns that

]] have meaningful values. The descriptions about the MAX values

]] didn't make sense until I read the descriptions of the

]] notifications and saw what was going on.=20

=20

MBS: Added words to say which columsn only apply to threshold crossing

events. =20

=20

         ::=3D { dot3OamMIB 6 }=20

 =20

     dot3OamEventLogEntry OBJECT-TYPE=20

       SYNTAX      Dot3OamEventLogEntry=20

       MAX-ACCESS  not-accessible=20

       STATUS      current=20

       DESCRIPTION "An entry in the dot3OamEventLogTable."=20

]] See previous comments on rows.

MBS: Done.

=20

]] Can selected entries in this table be deleted by

]] management operations?

MBS: The thought was no,that the table reflects what happened (to the
extent that it can). =20

       INDEX       { ifIndex, dot3OamEventLogIndex }

       ::=3D { dot3OamEventLogTable 1 }=20

=20

 << Text deleted >>

 =20

 =20

     dot3OamEventLogType      OBJECT-TYPE

       SYNTAX      Unsigned32=20

       MAX-ACCESS  read-only

       STATUS      current=20

       DESCRIPTION=20

         "The type of event that generated this entry in the event log.

 =20

         When the OUI is the IEEE 802.3 OUI of 0x0180C2, the following

         event types are defined:

             erroredSymbolEvent(1),=20

             erroredFramePeriodEvent (2),=20

             erroredFrameEvent(3),

             erroredFrameSecondsEvent(4),=20

             linkFault(256),=20

             dyingGaspEvent(257),

             criticalLinkEvent(258)

         The first four are considered threshold crossing events as

         they are generated when a metric exceeds a given value within

         a specified window.  The other three are not threshold

         crossing events. =20

 =20

         When the OUI is not 0x0180C2, then some other organization has

         defined the event space.  If event subtyping is known to the

         implementation, it may be reflected here.  Otherwise, this

         value should return all Fs (0xFFFFFFFF). =20

         "

]] If this is an Unsigned32, then say this in numeric

]] terms and not in terminology used for octet strings.

=20

MBS: added decimal value in addition to all Fs. =20

       REFERENCE   "[802.3ah], 30.3.6.1.10 and 57.5.3."

       ::=3D { dot3OamEventLogEntry 4 }

=20

=20

<< Text deleted >>

=20

=20

]] I'm not sure that I understand the objects

]] dot3OamEventLogRunningTotal and

]] dot3OamEventLogEventTotal. It

]] seems like dot3OamEventLogRunningTotal is the

]] value of a counter that is being thresholded,

]] and dot3OamEventLogEventTotal is the count of

]] the event crossings.=20

]] These counts seem possibly expensive to do.

]] Ok - after reading 802.3af, I see what is going on.

]] The descriptions below are really difficult to

]] understand. They need a rewrite.

=20

MBS: Rewrite will be attempted. =20

=20

=20

<< Text deleted >>

=20

 =20

     ------------------------------------------------------------------

     --=20

     -- Ethernet OAM Notifications

     --=20

 =20

     dot3OamNotifs OBJECT IDENTIFIER ::=3D { dot3OamMIB 7 }

     dot3OamNotifsPrefix OBJECT IDENTIFIER ::=3D {dot3OamNotifs 0}

]] remove these, and update OID values for notifications

MBS: I will delete these and replace the dot3OamNotifsPrefix in the

object below with dot3OamNotifications that you added earlier in the

MIB. =20

=20

=20

 << Text deleted >>

 =20

 =20

     ------------------------------------------------------------------

     --

     -- Ethernet OAM Compliance group

     --

 =20

 =20

     dot3OamGroups OBJECT IDENTIFIER ::=3D { dot3OamConformance 1 }

     dot3OamCompliances OBJECT IDENTIFIER ::=3D { dot3OamConformance 2 }

 =20

     -- Compliance statements

 =20

     dot3OamCompliance MODULE-COMPLIANCE=20

       STATUS          current

       DESCRIPTION "The compliance statement for managed entities

=20

=20

M. Squire            Expires - September 2005            [Page 46]=20




=20

                         EFM OAM MIB                March 2005

=20

=20

                    supporting OAM on Ethernet like interfaces. =20

                    "

     MODULE   -- this module

       MANDATORY-GROUPS { dot3OamControlGroup,=20

                          dot3OamPeerGroup,=20

                          dot3OamStatsBaseGroup=20

                        }

 =20

       GROUP       dot3OamLoopbackGroup

       DESCRIPTION=20

         "This group is mandatory for all IEEE 802.3 OAM

         implementations that support loopback functionality. "

 =20

       GROUP       dot3OamErrSymbolPeriodEventGroup

       DESCRIPTION=20

         "This group is mandatory for all IEEE 802.3 OAM

         implementations that support event functionality. "

 =20

       GROUP       dot3OamErrFramePeriodEventGroup

       DESCRIPTION=20

         "This group is mandatory for all IEEE 802.3 OAM

         implementations that support event functionality. "

 =20

       GROUP       dot3OamErrFrameEventGroup

       DESCRIPTION=20

         "This group is mandatory for all IEEE 802.3 OAM

         implementations that support event functionality. "

 =20

       GROUP       dot3OamErrFrameSecsSummaryEventGroup

       DESCRIPTION=20

         "This group is mandatory for all IEEE 802.3 OAM

         implementations that support event functionality. "

 =20

       GROUP dot3OamFlagEventGroup

       DESCRIPTION

         "This group is optional for all IEEE 802.3 OAM

         implementations.  The ability to send critical events or=20

         dying gasp events is not required in any system."

 =20

       GROUP       dot3OamEventLogGroup

       DESCRIPTION=20

         "This group is optional for all IEEE 802.3 OAM

         implementations. "

]] There will not be any local events in the log table

]] unless some of the event groups are implemented.

MBS: Correct.  Is that a question or are you suggesting some action? =20

 =20

       GROUP       dot3OamNotificationGroup

       DESCRIPTION=20

         "This group is optional for all IEEE 802.3 OAM

=20

=20

M. Squire            Expires - September 2005            [Page 47]=20




=20

                         EFM OAM MIB                March 2005

=20

=20

         implementations. "

]] This group requires implementation of the log table,

]] since the objects in the notifications are objects

]] in the log table!

MBS: I'm not sure what to do here, will have to think about it. =20

=20

       ::=3D { dot3OamCompliances 1}

=20

The way this module compliance is written, there are

a couple of unconditionally optional items (like the

notifications and logging). Also, there can be mix and

match of optional items. This is bad for IETF standards

track progression. You might consider having two

module compliance specifications - a minimal and

maximal. Others, like Bert, and provide better

advice as to the best practices in IETF standards

track MIB modules.

=20

 =20

 =20

    dot3OamControlGroup OBJECT-GROUP

       OBJECTS     {   dot3OamAdminState,

                       dot3OamOperStatus,

                       dot3OamMode,

                       dot3OamMaxOamPduSize,

                       dot3OamConfigRevision,

                       dot3OamFunctionsSupported

                   }

       STATUS      current

       DESCRIPTION=20

         "A collection of objects providing the abilities,

         configuration, and status of an Ethernet OAM entity.  "

       ::=3D { dot3OamGroups 1 }

 =20

    dot3OamPeerGroup OBJECT-GROUP

       OBJECTS     {   dot3OamPeerStatus,

                       dot3OamPeerMacAddress,

                       dot3OamPeerVendorOui,

                       dot3OamPeerVendorInfo,

                       dot3OamPeerMode,

                       dot3OamPeerFunctionsSupported,

                       dot3OamPeerMaxOamPduSize,

                       dot3OamPeerConfigRevision

                   }

       STATUS      current

       DESCRIPTION=20

         "A collection of objects providing the abilities,

         configuration, and status of a peer Ethernet OAM entity.  "

       ::=3D { dot3OamGroups 2 }

 =20

    dot3OamStatsBaseGroup OBJECT-GROUP

       OBJECTS     {   dot3OamInformationTx,

                       dot3OamInformationRx,

                       dot3OamUniqueEventNotificationTx,

                       dot3OamUniqueEventNotificationRx,

                       dot3OamDuplicateEventNotificationTx,

                       dot3OamDuplicateEventNotificationRx,

                       dot3OamLoopbackControlTx,

                       dot3OamLoopbackControlRx,

                       dot3OamVariableRequestTx,

                       dot3OamVariableRequestRx,

                       dot3OamVariableResponseTx,

                       dot3OamVariableResponseRx,

                       dot3OamOrgSpecificTx,

=20

=20

M. Squire            Expires - September 2005            [Page 48]=20




=20

                         EFM OAM MIB                March 2005

=20

=20

                       dot3OamOrgSpecificRx,

                       dot3OamUnsupportedCodesTx,

                       dot3OamUnsupportedCodesRx,

                       dot3OamFramesLostDueToOam

                   }

       STATUS      current

       DESCRIPTION=20

         "A collection of objects providing the statistics for the

         number of various transmit and recieve events for OAM on an

         Ethernet like interface.  Note that all of these counters must

         be supported even if the related function (as described in

         dot3OamFunctionsSupported) is not supported.  "

       ::=3D { dot3OamGroups 3 }

]] The compliance is not specified in group definitions.

MBS: Its one of the mandatory groups - what else are you looking for.=20

 =20

    dot3OamLoopbackGroup OBJECT-GROUP

       OBJECTS     {   dot3OamLoopbackCommand,

                       dot3OamLoopbackStatus,

                       dot3OamLoopbackIgnoreRx

                   }

       STATUS      current

       DESCRIPTION=20

         "A collection of objects for controlling the OAM remote

         loopback function.  "

       ::=3D { dot3OamGroups 4 }

 =20

    dot3OamErrSymbolPeriodEventGroup OBJECT-GROUP

       OBJECTS     {   dot3OamErrSymPeriodWindowHi,

                       dot3OamErrSymPeriodWindowLo,

                       dot3OamErrSymPeriodThresholdHi,

                       dot3OamErrSymPeriodThresholdLo,

                       dot3OamErrSymPeriodEvNotifEnable

                   }

       STATUS      current

       DESCRIPTION=20

         "A collection of objects for configuring the thresholds for an

         Errored Symbol Period Event. =20

 =20

         Each [802.3ah] defined Event Notification TLV has its own

         conformance group because each event can be implemented

         independently of any other.  "

       ::=3D { dot3OamGroups 5 }

 =20

    dot3OamErrFramePeriodEventGroup OBJECT-GROUP

       OBJECTS     {   dot3OamErrFramePeriodWindow,

                       dot3OamErrFramePeriodThreshold,

                       dot3OamErrFramePeriodEvNotifEnable

                   }

       STATUS      current

       DESCRIPTION=20

=20

=20

M. Squire            Expires - September 2005            [Page 49]=20




=20

                         EFM OAM MIB                March 2005

=20

=20

         "A collection of objects for configuring the thresholds for an

         Errored Frame Period Event. =20

 =20

         Each [802.3ah] defined Event Notification TLV has its own

         conformance group because each event can be implemented

         independently of any other.  "

       ::=3D { dot3OamGroups 6 }

 =20

    dot3OamErrFrameEventGroup OBJECT-GROUP

       OBJECTS     {   dot3OamErrFrameWindow,

                       dot3OamErrFrameThreshold,

                       dot3OamErrFrameEvNotifEnable

                   }

       STATUS      current

       DESCRIPTION=20

         "A collection of objects for configuring the thresholds for an

         Errored Frame Event. =20

 =20

         Each [802.3ah] defined Event Notification TLV has its own

         conformance group because each event can be implemented

         independently of any other.  "

       ::=3D { dot3OamGroups 7 }

]] Put this info about 802.3af in the commentary section

MBS: Which section are you refering to exactly? =20

 =20

    dot3OamErrFrameSecsSummaryEventGroup OBJECT-GROUP

       OBJECTS     {   dot3OamErrFrameSecsSummaryWindow,

                       dot3OamErrFrameSecsSummaryThreshold,

                       dot3OamErrFrameSecsEvNotifEnable

                   }

       STATUS      current

       DESCRIPTION=20

         "A collection of objects for configuring the thresholds for an

         Errored Frame Seconds Summary Event. =20

 =20

         Each [802.3ah] defined Event Notification TLV has its own

         conformance group because each event can be implemented

         independently of any other.  "

       ::=3D { dot3OamGroups 8 }

 =20

    dot3OamFlagEventGroup OBJECT-GROUP

       OBJECTS     {   dot3OamDyingGaspEnable,

                       dot3OamCriticalEventEnable

                   }

       STATUS      current

       DESCRIPTION=20

         "A collection of objects for configuring the sending OAMPDUs

         with the critical event flag or dying gasp flag enabled.  "

       ::=3D { dot3OamGroups 9 }

 =20

    dot3OamEventLogGroup OBJECT-GROUP

=20

=20

M. Squire            Expires - September 2005            [Page 50]=20




=20

                         EFM OAM MIB                March 2005

=20

=20

      OBJECTS {  dot3OamEventLogTimestamp,=20

                 dot3OamEventLogOui,=20

                 dot3OamEventLogType,

                 dot3OamEventLogLocation,

                 dot3OamEventLogWindowHi,

                 dot3OamEventLogWindowLo,

                 dot3OamEventLogThresholdHi,

                 dot3OamEventLogThresholdLo,

                 dot3OamEventLogValue,

                 dot3OamEventLogRunningTotal,

                 dot3OamEventLogEventTotal

               }

      STATUS      current

      DESCRIPTION=20

         "A collection of objects for configuring the thresholds for an

         Errored Frame Seconds Summary Event and maintaining the event

         information.  "

       ::=3D { dot3OamGroups 10 }

 =20

    dot3OamNotificationGroup NOTIFICATION-GROUP

      NOTIFICATIONS {  =20

                  dot3OamThresholdEvent,

                  dot3OamNonThresholdEvent

                    }

      STATUS      current

      DESCRIPTION=20

        "A collection of notifications used by Ethernet OAM to signal

        to a management entity that local or remote events have occured

        on a specified Ethernet link."

      ::=3D { dot3OamGroups 11 }

 =20

 =20

     END

 =20

 =20

 =20

 =20

=20

=20

=20

  _____ =20

From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com]=20
Sent: Tuesday, November 29, 2005 7:11 AM
To: Matt Squire; Lior khermosh
Cc: David T. Perkins; Hub MIB
Subject: Resolution to comments from David Perkins

=20

Matt, Lior, a.k.a. Hub-MIB Editors

=20

When will you be able to address the comments submitted by David Perkins
in his review and propose resolutions? Please do it on the WG list, so
that the proposals for resolution is open for discussion.

=20

Thanks and Regards,

=20

Dan

=20

=20

=20

=20

=20


------_=_NextPart_001_01C61650.63D0AA58
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><o:SmartTagType
 namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" =
name=3D"PersonName"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Hi David, Dan &nbsp;&#8211; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Below are my responses to the =
various
comments.&nbsp; Many of the editorial problems (spelling error, etc.) =
won&#8217;t
be listed here as they don&#8217;t really require discussion. &nbsp;I =
separated
out what I consider the biggest issues and talk about them first, then =
include
responses to your individual comments in the parts that follow. =
&nbsp;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>- Matt<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Bigger =
issues:<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>a) &#8220;dot3&#8221; vs =
&#8220;efm&#8221;.&nbsp;
There were multiple comments related to whether various names in the MIB =
should
be &#8220;efm&#8230;&#8221; or &#8220;dot3&#8230;&#8221;.&nbsp; =
Admittedly, the
reviewed version of the MIB had a mix of the two as it historically went =
from &#8220;EFM
OAM&#8221; to &#8220;EFM Common&#8221; to &#8220;OAM&#8221; to whatever. =
&nbsp;To
be clear, the OAM functionality of 802.3 is applicable to any Ethernet
interface, not just those defined in 802.3ah, so it applies to =
1000BASE-X,
10/100BASE-T, etc. &nbsp;For that reason, I&#8217;d suggest we move =
everything
to a &#8220;dot3&#8230;&#8221; prefix rather than an =
&#8220;efm&#8230;&#8221;
prefix, and to use &#8220;Ethernet OAM&#8221; as a description rather =
than &#8220;EFM
OAM&#8221; (which appears in a few places). =
&nbsp;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>b) Improving description clauses. =
&nbsp;You
commented that all description clauses for tables need to contain XYZ,
similarly for rows.&nbsp; I&#8217;ve attempted to improve the =
description
clauses based on your feedback. =
&nbsp;&nbsp;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>c) Removing frame reception =
conditions in
MIB descriptions.&nbsp; You had multiple comments related to certain =
sections
of the MIB (the OAM peer objects) where the descriptions included =
detailed
information on what the values of various frame fields had to be in =
order to
process the frame.&nbsp; As an example, the MIB =
had:<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&nbsp;An OAMPDU is indicated by a valid frame with (1) =
destination<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
MAC address equal to that of the reserved MAC address for =
Slow<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Protocols (See 43B of [802.3ah]), (2) a lengthOrType =
field<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
equal to the reserved type for Slow Protocols, (3) and a =
Slow<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Protocols subtype equal to that of the subtype reserved =
for<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
OAM.&nbsp; <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>You basically indicated that such =
details
weren&#8217;t needed in those sections. &nbsp;I&#8217;m more than fine =
with
removing it.&nbsp; It was added several revisions ago when someone asked =
for
more details about &#8220;when exactly does this value get =
updated?&#8221;&nbsp;
At that point I added descriptions like the above to spell out as much =
as
possible what has to be received for this field to be updated. =
&nbsp;I&#8217;d
personally love to remove it, as it&#8217;s just a bunch of extra words =
to me,
but more than that I don&#8217;t want to add it back again later. =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>d) You found a couple of problems =
with my
RTF-RFC conversion process. &nbsp;In what was Section 4.3, there was a =
mapping
of SNMP to 802.3 attributes, and you rightfully pointed out there should =
be a
section header and introduction sentence or two. &nbsp;At some point =
when going
from the word RTF file to the text RFC, those were deleted. &nbsp;In the =
next
rev, there will be a Section 4.4 just for the SNMP/802.3 attribute =
mappings. &nbsp;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>e) You pointed out some =
inconsistencies
(and potential improvements) on explaining when entries are =
created/deleted
from various tables.&nbsp; My suggestion going forward is to detail when
entries are created in the primary control table (dot3OamTable), =
indicating
they are automatically created for every Ethernet interface that =
supports
OAM.&nbsp; And then say that other tables have entries automatically =
created
for every entry in that primary table. &nbsp;The way things were =
written, <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>&nbsp;- dot3OamPeerTable =
didn&#8217;t
always have an entry &#8211; it was written so that you could add an =
entry once
you learned the peer, then leave it in there, but an entry wasn&#8217;t
required even if you were running OAM.&nbsp; I suggest changing that so =
that an
entry is always required, and the various objects have mechanisms to =
indicate
whether their values validly reflect an actual OAM peer, or whether =
there is no
peer.&nbsp; This reflects several of your =
comments<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>&nbsp;- dot3OamLoopbackTable =
didn&#8217;t
require an entry if the implementation didn&#8217;t support loopback =
(there was
a condition &#8220;if loopback is supported&#8221; in the description). =
&nbsp;Likewise,
the dot3EventConfigTable didn&#8217;t always require an entry =
(it&#8217;s an
optional function as well).&nbsp; &nbsp;&nbsp;Given the optional nature =
of
certain functions (loopback, events, etc), I wasn&#8217;t sure whether =
the
tables should always have an entry (with some kind of &#8216;not =
supported&#8217;
indicator), or whether the tables should only have entries if the =
function is
supported, or if there was some other approach. &nbsp;I&#8217;m open to
suggestions.&nbsp; <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>f) In the dot3OamAdminState, I had =
a
description that included: <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Note that the value of this object is ignored when =
the<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
interface is not operating in full-duplex mode. OAM is =
not<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
supported on half-duplex links.&nbsp; <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] I'm =
not sure
what &quot;ignored&quot; means here.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] I =
don't
believe that &quot;ignored&quot; is the right =
term.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] =
Shouldn't
whether the interface is in half or =
full-duplex<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] show =
up in the
value of object dot3OamOperStatus?<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] I'm =
assuming
that only interfaces that can operate<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] in =
full-duplex
mode will be in this table. That<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] =
should of been
said in the table DESCRIPTION clause.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>This is a little trickier than I
originally thought. &nbsp;OAM was intended for full-duplex links, and =
some of the
functions don&#8217;t operate on half-duplex links. &nbsp;So I was =
trying to
say that OAM shouldn&#8217;t run on half-duplex links, so setting the =
admin
state doesn&#8217;t matter (hence the ignored). &nbsp;I&#8217;m open to =
finding
better ways of saying that.&nbsp; Looking back at 802.3ah, I was unable =
to find
the sections that indicate OAM doesn&#8217;t come up on half-duplex =
links. &nbsp;So
I believe what happens is that OAM would come up but some things might =
not work
(anybody have a different interpretation)? &nbsp;If that&#8217;s the =
case (as I
think now), then I will probably have to rewrite that description to =
capture
the proper behavior. &nbsp;I&#8217;m not sure that reflecting the duplex =
of the
interface in the dot3OamStatus is either good or necessary. &nbsp;The =
OAM
tables should exist whether the interface is full/half/auto, so the =
potential
to be in full-duplex may be required, but you don&#8217;t have to be in
full-duplex mode to have an entry in the OAM table (your duplex may be =
auto,
TBD later). &nbsp;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>g) In the loobpack object, right =
now there
is a separate status and action attribute, so that you can set the =
action to
start/stop loopback, then go read the status. &nbsp;You suggested a =
combined
status/action object.&nbsp; First, I don&#8217;t know what that means. =
&nbsp;Can
you point me to an example in some other document? &nbsp;Second, the =
current separation
of action/status was a result of discussions on either the list or at a
meeting. &nbsp;All of the examples that I was able to find or were given =
to me for
similar function had one attribute to initiate the action and another to =
return
the result.&nbsp; &nbsp;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>h) You suggested combining =
dot3OamErrSymPeriodWindowHi
and dot3OamErrSymPeriodWindowLo into one CounterBasedGauge64. &nbsp;This =
was
discussed on the list previously and it was decided that was not =
possible. &nbsp;The
discussion centered on CounterBasedGauge64s as being read-only counters. =
&nbsp;In
this case, we need settable parameters as we&#8217;re trying to setup a
threshold. &nbsp;So I was told CounterBasedGauge64s were not applicable =
in that
scenario, and that we needed to have two separate attributes with rules =
to
combine them. &nbsp;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>i) On the dot3EventLogTable, you =
had
questions about the maximum size and =
handling:<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] On =
this table,
can it have an infinite number of entries?<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] Most =
likely
not. In other tables, there is some =
indication<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] that =
says the
max number (not always available), but<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] =
always
something that says to either stop adding =
entries,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] or =
delete the
oldest, or some other algorithm to replace<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] the =
least
important with a new one.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>I suggest saying the size of the =
table is
implementation dependent, and that older entries are automatically =
replaced
with newer entries when the table gets full. &nbsp;Is that =
satisfactory?&nbsp; <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>j)&nbsp; In the event log table, =
you asked
what were the running totals and event totals. After reading 802.3ah, =
you
indicated you know what they mean, but a re-write of the description is =
in
order. &nbsp;Here&#8217;s my proposed =
DESCRIPTION:<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;
&nbsp;&nbsp;&quot;Each Event Notification TLV contains a running total =
of the<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
number of times an event has occurred, as well as the number =
of<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
times an Event Notification for the event has been =
transmitted.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;For
non-threshold crossing events, the number of =
events<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
(dot3OamLogRunningTotal) and the number of resultant =
Event<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Notifications (dot3OamLogEventTotal) should be identical. =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
For threshold crossing events, since multiple occurrences =
may<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
be required to cross the threshold, these values are =
likely<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
different.&nbsp; This value represents the total number of times =
one<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
or more of these occurrences have resulted in an =
Event<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Notification (for example, 51 when 3253 symbol errors =
have<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
occurred since the last reset, which has resulted in 51 =
symbol<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
error threshold crossing events since the last reset).&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&#8220;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>k) You made suggestions on =
rearranging the
hierarchy so that there is a dot3OamNotifications off dot3OamMIB, and =
having
the notifications reference that. &nbsp;I&#8217;m fine with changing the =
tree
that way so Notifications are moved up in the tree. =
&nbsp;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>l) In the reviewed versions, the
compliance section has some unconditionally optional groups, allowing =
for a mix
and match set of implementations.&nbsp; You suggested defining a minimum =
and
maximum compliance group.&nbsp; I don&#8217;t have a suggestion here =
yet.&nbsp;
I need to think about it more, but would be interested in hearing =
opinions from
anyone else.&nbsp; <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>&nbsp;=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<o:p=
></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>In the text below, I basically =
include the
version of the draft with your comments in it as was sent to the mailing =
list. &nbsp;From
that text, I removed certain sections that didn&#8217;t have any =
comments, or
had only what I considered uncontroversial editorial comments. =
&nbsp;Where text
was removed, &lt;&lt; Text deleted &gt;&gt; appears.&nbsp; Your comments =
are
still prefixed with ]], while I put &#8220;MBS:&#8221; in front of my =
response.
&nbsp;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] =
Reviewed
8-sept-2005, david t. perkins, =
dperkins@snmpinfo.com<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>]]<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] =
Global
comments:<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]]&nbsp; =
Comments
are inserted in-line and each comment line<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]]&nbsp; =
is
preceded by &quot;]]&quot;.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>]]<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]]1) A =
line of
&quot;-&quot;s is used as a separator. This is =
problematic<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>]]&nbsp;&nbsp;
and if a separator is desired, the it should be =
something<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>]]&nbsp;&nbsp;
like -- =
**************************************************<o:p></o:p></span></fon=
t></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>]]&nbsp;&nbsp;
(If the number of &quot;-&quot;s in a line is X, and =
mod(X,4)=3D=3D1,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>]]&nbsp;&nbsp;
then a MIB compiler will report a parse =
error.)<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>MBS:&nbsp; No
problem doing the change.&nbsp; <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>]]<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]]2) All =
the
tables should have consistent info in the<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>]]&nbsp;&nbsp;
DESCRIPTION clauses for the table and row =
definitions.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>]]&nbsp;&nbsp;
Minimally, the tables DESCRIPTION clause should =
describe<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>]]&nbsp;&nbsp;
the table, and specify what determines the number =
of<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>]]&nbsp;&nbsp;
entries in the table.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>]]&nbsp;&nbsp;
Minimally, the DESCRIPTION clause for rows should =
indicate<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>]]&nbsp;&nbsp;
how rows are added and removed from tables. And if =
can<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>]]&nbsp;&nbsp; be
done via direct SNMP operations, then the =
identification<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>]]&nbsp;&nbsp; of
the RowStatus object.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>]]&nbsp;&nbsp;
Note that there is additional information that must =
be<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>]]&nbsp;&nbsp;
contained in the DESCRIPTION clause as specified =
in<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>]]&nbsp;&nbsp;
&quot;Guidelines ... of MIB Documents&quot;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>]]&nbsp;&nbsp;
&lt;draft-ietf-ops-mib-review-guidelines-04.txt&gt;<o:p></o:p></span></fo=
nt></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>]]&nbsp;&nbsp;
[MIBguidelines]<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>MBS: =
I've
attempted to update the objects as appropriate.&nbsp; =
They'll<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>need to =
be
reviewed to ensure they meet the goals.&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>]]<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]]3) For
enumerated values, each value be described in =
the<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>]]&nbsp;&nbsp;
DESCRIPTION text of the object or TC =
definition.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>MBS: I =
found a
couple instances where not every enumerated value =
was<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>spelled =
out, and
tried to correct that (you have specific comments =
to<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>these at =
the
various instances of the omission).&nbsp; <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>]]<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]]5) The =
term
&quot;byte&quot; should be replaced by term =
&quot;octet&quot;.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>MBS:
Changed.&nbsp; <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]]6) The
abbreviations &quot;i.e.&quot;, and &quot;e.g.&quot; are =
confused.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>]]&nbsp;&nbsp; I
suggest that you always write out &quot;that =
is&quot;,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>]]&nbsp;&nbsp;
and &quot;for example&quot;.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>MBS: I =
replaced
the few occurences of &quot;e.g.&quot; with &quot;for =
example&quot;.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>Personally, I
don't believe that it improves (or hurts) anything, =
but<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>I'm more =
than
willing to do it.&nbsp; The abbreviation &quot;i.e.&quot; wasn't =
used<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>in the =
document
(that I could find).&nbsp; <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]]7) A =
few typos
were found by idnits script found at<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>]]&nbsp;&nbsp;
http://ietf.levkowetz.com/tools/idnits/<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>MBS: =
I'll be sure
to run the script on next revision before<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>submission.&nbsp;
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
Ethernet
Interfaces and Hub MIB
WG&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
Internet
Draft&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
<st1:PersonName w:st=3D"on">Matt =
Squire</st1:PersonName><o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
Document:
draft-ietf-hubmib-efm-mib-03.txt&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;
Hatteras Networks<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
Expires:
September
2005&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;
March, 2005<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;
Ethernet in the First Mile (EFM) OAM MIB<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&lt;&lt;
Text deleted &gt;&gt;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>3.&nbsp;&nbsp;
Overview<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
Ethernet
networks have evolved over the past 30 years from =
simple<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
LANs to a
variety of other applications, including wide =
area<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp;
networks.&nbsp; To address some of these emerging markets, the =
IEEE<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
802.3ah
task force defined additional clauses for the IEEE =
802.3<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
standard
[802.3-2002] to better address Ethernet deployments in =
the<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
public
access network.&nbsp; <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] To =
make it
clear, I'd change the above to the =
following:<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>]]&nbsp;&nbsp; To
address some of these emerging markets, the =
IEEE<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>]]&nbsp;&nbsp;
802.3ah task force defined additional clauses in =
[802.3ah]<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>]]&nbsp;&nbsp;
for the IEEE 802.3 standard [802.3-2002] to better =
address<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>]]&nbsp;&nbsp;
Ethernet deployments in the public access =
network.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>MBS: =
Changed
made.&nbsp; <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] Is =
802.3ah
work strictly for &quot;public access =
networks&quot;?<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] If =
not, then
the phrase should be dropped or replaced.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>MBS: =
Access
networks were the motivation for the task force, but =
the<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>results =
can be
applied for any application.&nbsp; So the phrase =
does<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>address =
why the
work was initiated and completed, but does not =
fully<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>address
applicability.&nbsp; Instead of the suggestion, I added a =
sentence;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&quot;Although
Ethernet access deployments were the primary motivation =
for<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>the task =
force
work, the results of the task force are not limited =
to<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>that
application.&nbsp; &quot;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&lt;&lt; =
Text
deleted &gt;&gt;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>4.1&nbsp;&nbsp;&nbsp;
Relation to other SNMP MIB Modules<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
This
objects defined in this document do not overlap with =
MIB-2<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
[RFC1213],
the interfaces MIB [RFC2863], or the Ethernet =
like<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
interfaces
MIB [RFC3635].&nbsp; The objects defined here are defined =
for<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
Ethernet
like interfaces only and use the same ifIndex as =
the<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
associated
Ethernet interface.&nbsp; Ethernet OAM can be implemented =
on<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
any
Ethernet like interface managed via these MIBs.&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] The
&quot;This&quot; should be &quot;The&quot;. =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] MIB-2 =
is
obsolete, and I'm not sure what this section =
is<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] =
trying to say.
I'm not sure that this functionality<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] can =
be applied
on any &quot;Ethernet-like&quot; =
interfaces,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] and =
not just
on the interface types as specified<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] in
[802.3ah].&nbsp; <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>MBS: The =
OAM
functionality controlled by this MIB can be applied =
to<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>any =
Ethernet
interface (for example, 10/100BASE-T).&nbsp; This was =
an<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>explicit =
goal of
the OAM sub taskforce.&nbsp; This paragraph is =
attempting<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>to say =
that this
MIB does not overlap with existing MIBs used =
to<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>manage =
Ethernet
interfaces (several examples given via =
references).<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>However, =
it is
noted that the indexing scheme is the same.&nbsp; I =
can<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>certainly try to
re-write it again to make that point better.&nbsp; =
One<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>possible =
wording
would be:<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
&quot;The
objects defined in this document manage OAM functionality =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;
introduced in [802.3ah]&nbsp; These objects do not overlap with =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;
MIB-2 [RFC1213], the interfaces MIB [RFC2863], the Ethernet like =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;
interfaces MIB [RFC3635], or any other MIB currently used to =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;
manage various aspects of an Ethernet interface.&nbsp; The objects =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;
defined here are defined for Ethernet like interfaces only and =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp; use
the same ifIndex as the associated Ethernet interface.&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;
Ethernet OAM can be implemented on any Ethernet like =
interface.&quot;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>4.2&nbsp;&nbsp;&nbsp;
Relation to other EFM MIB Modules<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
The Ethernet
OAM functionality and MIB Module is independent of =
the<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
other
functionality and MIB Modules derived from [802.3ah] for =
copper<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp;
[802.3ah-copper] and EPON [802.3ah-epon].&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
Ethernet
OAM may be implemented on point-to-multipoint EFM =
EPON<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
interfaces.&nbsp;
However, because higher layer protocols that run =
over<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
Ethernet
interfaces are not designed for the partial =
connectivity<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
provided
by a point-to-multipoint interface, EPON provides a =
point<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
to-point
emulation layer (see [802.3ah] and [802.3ah-epon]) =
whereby<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
the single
EPON interface of 1-to-N connectivity is represented by =
N<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp;
point-to-point interfaces.&nbsp; Ethernet OAM, like any other protocol =
at<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
the
Ethernet layer or above (for example, bridging), utilizes =
the<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp;
point-to-point emulation layer of EPON in that the EPON interface =
is<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
viewed as
N point-to-point Ethernet interfaces.&nbsp; Thus OAM, and =
other<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
protocols,
do not need to be altered for the EPON environment.&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
Ethernet
OAM may be implemented on the 2BASE-TL and =
10PASS-TS<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
Ethernet-over-copper
interfaces defined in EFM [802.3ah].&nbsp; =
2BASE-TL<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
and
10PASS-TS can be aggregated interfaces, meaning that they can =
use<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
the
ifStackTable of the Interfaces Group MIB [RFC2863] to manage =
a<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
set of N
(1 &lt;=3D N &lt;=3D 32) physical layers into a single =
Ethernet<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp;
interface.&nbsp; <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>M.
Squire&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Expires - September
2005&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
[Page 5]
<o:p></o:p></span></font></p>

<font size=3D2 color=3Dnavy face=3D"Courier New"><span =
style=3D'font-size:10.0pt;
font-family:"Courier New";color:navy'><br clear=3Dall =
style=3D'page-break-before:
always'>
</span></font>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;
EFM OAM
MIB&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;
March 2005<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
The other
Ethernet interfaces introduced in EFM [802.3ah] are =
simply<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
new
optical physical layers that are managed by minimal extensions =
to<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
the MAU
MIB [RFC3636] defining new types of Ethernet interfaces.&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>4.3&nbsp;&nbsp;&nbsp;
IANA Considerations<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
The EFM
OAM MIB requires the allocation of a single object =
identifier<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
for its
MODULE-IDENTITY under the MIB-2 tree.&nbsp; IANA has not =
yet<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
allocated
this object identifier.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] This =
needs to
be updated to follow the format as<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] =
specified in
[MIBguidelines]<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>MORE<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] The =
list that
follows seems out of place. At the minimum<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] there =
needs to
be a section header and intro.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>]]<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] NOTE: =
I didn't
check the list below for errors, such<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>]]&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
as omissions and spellings.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>MBS: The =
lack of
header/intro is apparently an artifact of =
RTF-&gt;I-D<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>format
conversion.&nbsp; I'll fix it in the next revision.&nbsp; The headers =
and<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>introduction
exist in my RTF file.&nbsp; <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
[802.3ah]
Clause 30, and managed objects defined in this document.&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
IEEE 802.3
Managed Object&nbsp;&nbsp;&nbsp;&nbsp; Corresponding SNMP =
object<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] In =
the below,
it would be useful to also show the object =
class<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] (the =
oXXX)
containing each attribute. For example, the MAU =
MIB<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] =
document
(draft-ietf-hubmib-rfc3636bis-01.txt) does =
this.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>MBS: =
Easy enough
to do (there's just oOAM).&nbsp; <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;
.aOAMID&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;IF-MIB =
ifIndex<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>5.&nbsp;&nbsp;
MIB Structure<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
The common
EFM MIB objects of this memo focus on the OAM =
capabilities<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
introduced
in IEEE 802.3ah.&nbsp; The MIB objects are partitioned into =
six<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] =
Probably want
[803.3ah] instead of just 802.3ah<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>MBS: =
Done<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
different
MIB groups.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
The
dot3OamTable group manages the primary OAM objects of =
the<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
Ethernet
interface.&nbsp; This group controls the state and status of =
OAM<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
as well as
the mode in which it operates.&nbsp; <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
The
dot3OamPeerTable maintains the current information on the =
status<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
and
configuration of the peer OAM entity on the Ethernet interface. =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
Managed
information includes the capabilities and function =
available<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] I =
think
&quot;capabilities&quot; and &quot;function&quot; are the same, =
so<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] I =
would drop
&quot;and function&quot;.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>MBS:&nbsp; I'm
not sure I agree with that.&nbsp; Capabilities generally refers to what =
the
other guy can do, while functions refers to what it does.&nbsp; Some
capabilities may be disabled or inoperable for many reasons.&nbsp; So =
I'm
trying to say that the MIB covers both potential and actual
functionality.&nbsp; <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
on the
peer OAM entity.&nbsp; <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span lang=3DFR
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>M.
Squire&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Expires - September
2005&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
[Page 7]
<o:p></o:p></span></font></p>

<font size=3D2 color=3Dnavy face=3D"Courier New"><span lang=3DFR =
style=3D'font-size:10.0pt;
font-family:"Courier New";color:navy'><br clear=3Dall =
style=3D'page-break-before:
always'>
</span></font>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span lang=3DFR
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span lang=3DFR
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;
</span></font><font size=3D2 color=3Dnavy face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>EFM OAM
MIB&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;
March 2005<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
The dot3OamLoopbackTable
manages the loopback function introduced in<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
EFM
[802.3ah].&nbsp; This table controls enabling and disabling =
loopback,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] Is =
there a
difference between &quot;EFM [802.3af]&quot; and =
&quot;[802.3af]&quot;?<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] If =
so, this
needs to be reflected throughout the the<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] =
document. If
not, then the &quot;EFM&quot; should be =
removed.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>MBS: No
difference,so I removed EFM.&nbsp; The benefit of having it =
in<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>there is =
that
many people know the project as EFM, even though =
this<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>function =
is not
restricted to the physical layers of that project.&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
as well as
indicating the loopback status of Ethernet OAM on =
this<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp;
interface.&nbsp; <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] Above =
and
through the document, the terms &quot;Ethernet =
OAM&quot;,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] and =
&quot;EFM
OAM&quot; are used. Are these the same, or =
different?<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] If =
different,
then this needs to be explained. If the<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] same, =
then one
should be chosen and used consistently.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>MBS: =
There's no
intended difference.&nbsp; As the OAM functionality =
applies<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>to any =
Ethernet
interface, I will go with Ethernet OAM rather than =
EFM<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>OAM.&nbsp; <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&lt;&lt;
Text deleted &gt;&gt;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>6.&nbsp;&nbsp;
MIB Definition<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp;
EFM-COMMON-MIB DEFINITIONS ::=3D BEGIN <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] This =
module
name doesn't follow the naming conventions<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] in =
the
[MIBguidelines] document. However, I can't =
determine<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] if it =
should
be DOT3-OAM-MIB, or =
&quot;EFM-OAM-MIB&quot;.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>MBS: It =
should be
DOT3-OAM-MIB to me, so that's what I'll change it to.&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;
IMPORTS <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;
MODULE-IDENTITY, mib-2, OBJECT-TYPE, Counter32, Unsigned32, =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Integer32, NOTIFICATION-TYPE<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
FROM SNMPv2-SMI <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;
TEXTUAL-CONVENTION, MacAddress, TimeStamp<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
FROM SNMPv2-TC <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;
CounterBasedGauge64<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
FROM HCNUM-TC<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;
ifIndex&nbsp; <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
FROM IF-MIB <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;
MODULE-COMPLIANCE, OBJECT-GROUP, =
NOTIFICATION-GROUP<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
FROM SNMPv2-CONF; <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;
efmOamMIB MODULE-IDENTITY <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] Not =
sure if
should be efmOamMIB or dot3OamMIB<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>MBS: =
Changed to
dot3OamMIB<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
LAST-UPDATED &quot;200503220000Z&quot;&nbsp; -- March 22, =
2005&quot;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
ORGANIZATION <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&quot;IETF Ethernet Interfaces and Hub MIB Working =
Group&quot;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
CONTACT-INFO <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&quot;WG Charter: <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;
http://www.ietf.org/html.charters/hubmib-charter.html =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Mailing lists: <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>M.
Squire&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Expires - September
2005&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
[Page 8]
<o:p></o:p></span></font></p>

<font size=3D2 color=3Dnavy face=3D"Courier New"><span =
style=3D'font-size:10.0pt;
font-family:"Courier New";color:navy'><br clear=3Dall =
style=3D'page-break-before:
always'>
</span></font>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;
EFM OAM
MIB&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;
March 2005<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;
General Discussion: hubmib@ietf.org <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;
To Subscribe: hubmib-requests@ietf.org <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;
In Body: subscribe your_email_address <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font><font size=3D2 color=3Dnavy face=3D"Courier New"><span =
lang=3DFR
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>Chair: =
Dan
Romascanu, Avaya<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span lang=3DFR
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;
Tel:&nbsp; +972-3-645-8414 <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span lang=3DFR
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;
</span></font><font size=3D2 color=3Dnavy face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>Email: =
dromasca
at avaya dot com <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Editor: <st1:PersonName w:st=3D"on">Matt Squire</st1:PersonName> =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;
Hatteras Networks <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;
Tel:&nbsp;&nbsp;&nbsp; +1-919-991-5460 <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;
Fax:&nbsp;&nbsp;&nbsp; +1-919-991-0743<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;
E-mail: msquire at hatterasnetworks dot com<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&quot;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
DESCRIPTION<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&quot;The MIB module for managing the new Ethernet OAM =
features<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
introduced by the Ethernet in the First Mile task force =
(IEEE<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
802.3ah).&nbsp; The functionality presented here is based on =
IEEE<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
802.3ah [802.3ah], released in October, 2004.&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
In particular, this MIB focused on the changes to Clause 30 =
of<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
the draft that are not specific to any physical layer.&nbsp; =
These<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
changes are primarily reflected in the new OAM =
features<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
developed under this project, that can be applied to =
any<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Ethernet like interface. The OAM features are described =
in<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Clause 57 of [802.3ah].<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] =
First, is it
clause 30 or 57.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] Also, =
the
above reads strangely. People that don't =
understand<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] =
exactly how
IEEE documents are updated (which is very =
different<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] than =
how IETF
documents are updated).<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>MBS:&nbsp;
Attempted re-wording below.&nbsp; Hopefully this will make more =
sense<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>to
you.&nbsp;&nbsp;&nbsp; The functionality is described in one clause, but =
the<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>management
attributes of that functionality are described in another.&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&quot;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
In particular, this MIB focuses on the new OAM =
functions<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
introduced in Clause 57 of [802.3ah].&nbsp; The OAM functionality =
of<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Clasue 57 is controlled by new management attributes =
introduced<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
in Clause 30 of [802.3ah].&nbsp; The OAM functions are not =
specific<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
to any particular Ethernet physical layer, and can =
be<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
generically applied to any Ethernet interface of [802.3-2002].&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&quot;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&lt;&lt; =
Text
deleted &gt;&gt; <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;
--<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;
-- Ethernet OAM Control group<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;
--<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;
dot3OamTable OBJECT-TYPE<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
SYNTAX&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; SEQUENCE OF =
Dot3OamEntry<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
MAX-ACCESS&nbsp; not-accessible<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
STATUS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
current<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
DESCRIPTION <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&quot;Primary controls and status for the OAM capabilities of =
an<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Ethernet like interface.&nbsp; There will be one row in this =
table<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
for each Ethernet like interface in the system that =
supports<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
the Ethernet OAM functions defined in [802.3ah].&quot;&nbsp;&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
::=3D { dot3OamMIB 1 }<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] I'm =
still
unclear as to exactly which interfaces will =
be<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] in =
this table.
For example, if a 10baseT interface card<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] is =
plugged
into the device, will a new row show up?<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] Or is =
it only
for the Cu and EPON interfaces?<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] And =
does some
other configuration (outside of SNMP)<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] =
configuration
have to be done?<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] I =
believe the
answer is not, but want to determine<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] if =
aggregated
interfaces can exist in the table?&nbsp;&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>MBS:&nbsp; Any
Ethernet interface that can appear in the Ethernet like =
MIB<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>table =
can appear
here if OAM functionality is supported.&nbsp; So =
the<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>answer =
to your
questions are<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp;- =
yes, if
the interfaces support Ethernet OAM (which is =
optional)<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp;- =
no, it is
not only for the Cu/EPON interfaces<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp;- =
no, no
other configuration is required <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;
dot3OamEntry OBJECT-TYPE<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
SYNTAX&nbsp;&nbsp;&nbsp;&nbsp; Dot3OamEntry<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
MAX-ACCESS not-accessible<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span lang=3DFR
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>M.
Squire&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Expires - September
2005&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
[Page
10] <o:p></o:p></span></font></p>

<font size=3D2 color=3Dnavy face=3D"Courier New"><span lang=3DFR =
style=3D'font-size:10.0pt;
font-family:"Courier New";color:navy'><br clear=3Dall =
style=3D'page-break-before:
always'>
</span></font>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span lang=3DFR
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span lang=3DFR
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;
</span></font><font size=3D2 color=3Dnavy face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>EFM OAM
MIB&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;
March 2005<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
STATUS&nbsp;&nbsp;&nbsp;&nbsp; current<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
DESCRIPTION <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&quot;An entry in the table, containing information on the =
Ethernet<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
OAM function for a single Ethernet like =
interface.&quot;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
INDEX&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; { ifIndex =
}<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
::=3D { dot3OamTable 1 }<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] The =
SMI
requires in the DESCRIPTION clause for a =
row,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] a =
description
of index objects that not defined in the<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] =
table.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>MBS: =
Added a
description that says when entries created/deleted and the row =
status.&nbsp; <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;
Dot3OamEntry ::=3D<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
SEQUENCE {<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;dot3OamAdminState&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;
INTEGER,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
dot3OamOperStatus&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
INTEGER,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
dot3OamMode&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;
INTEGER,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
dot3OamMaxOamPduSize&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Integer32,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
dot3OamConfigRevision&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;
Unsigned32, <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
dot3OamFunctionsSupported&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;
BITS<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
}<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;
dot3OamAdminState OBJECT-TYPE<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
SYNTAX&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; INTEGER =
{<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
disabled(1),<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
enabled(2)<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
}<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
MAX-ACCESS&nbsp; read-write<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
STATUS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
current<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
DESCRIPTION <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&quot;This object is used to provision the default =
administrative<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
OAM mode for this interface.&nbsp; This object represents =
the<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
desired state of OAM for this interface.&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
The dot3OamAdminState always starts in the disabled(1) =
state<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
until an explicity management action or =
configuration<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>]]&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
^^^^^^spelling error<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>MBS: =
Fixed.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
information retained by the system causes a transition to =
the<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
enabled(2) state. <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Note that the value of this object is ignored when =
the<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
interface is not operating in full-duplex mode. OAM is =
not<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
supported on half-duplex links.&nbsp; =
&quot;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
REFERENCE&nbsp;&nbsp; &quot;[802.3ah], =
30.3.6.1.2&quot;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
::=3D { dot3OamEntry 1 }<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] I'm =
not sure
what &quot;ignored&quot; means here.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] I =
don't
believe that &quot;ignored&quot; is the right =
term.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] =
Shouldn't
whether the interface is in half or =
full-duplex<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] show =
up in the
value of object dot3OamOperStatus?<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] I'm =
assuming
that only interfaces that can operate<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] in =
full-duplex
mode will be in this table. That<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] =
should of been
said in the table DESCRIPTION clause.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>MBS: =
This is a
little tricky.&nbsp; Certain functions in Ethernet =
OAM<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>assume
full-duplex links.&nbsp; So I tried to say that you should =
ignore<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>the =
provisioned
enable/disable admin state if the link comes =
up<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>half-duplex, and
just leave OAM disabled.&nbsp; Certainly a link =
should<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>have the =
capacity
to be full-duplex to appear in this table.&nbsp; =
However,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>if the =
interface
hasn't negotiated duplex yet, we should still =
allow<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>it in =
the table
so that OAM can be configured in case the link =
comes<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>up
full-duplex.&nbsp; <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>MBS: =
This
behavior is certainly up for<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>interpretation.&nbsp;
We could allow OAm to operate on half-duplex =
links<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>though =
not every
function will be available.&nbsp; Open to suggestions.&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;
dot3OamOperStatus OBJECT-TYPE<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
SYNTAX&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; INTEGER =
{<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
disabled(1),<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
linkfault(2),<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
passiveWait(3),<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;activeSendLocal(4),<o:p></o:p><=
/span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
sendLocalAndRemote(5),<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
sendLocalAndRemoteOk(6),<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>M.
Squire&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Expires - September
2005&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
[Page
11] <o:p></o:p></span></font></p>

<font size=3D2 color=3Dnavy face=3D"Courier New"><span =
style=3D'font-size:10.0pt;
font-family:"Courier New";color:navy'><br clear=3Dall =
style=3D'page-break-before:
always'>
</span></font>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;
EFM OAM
MIB&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;
March 2005<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;oamPeeringLocallyRejected(7),<o:=
p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
oamPeeringRemotelyRejected(8),<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
operational(9)<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
}<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] What =
values
indicate that ifAdmin status is set down<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] or =
testing?<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] What =
are the
values when ifOperStatus is not up?<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] It =
seems like
some of these could occur concurrently.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] Is =
this
possible?<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>MBS:&nbsp; if the
physical layer is not up, OAM will be in linkfault =
state<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>(regardless of
whether its down, testing, or anything else).&nbsp; =
The<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>linkFault state
is the starting state for any enabled OAM<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>implementation.
There are OAM state machines in [802.3ah] that =
define<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>the 9 =
states
above, and one and only one is possible at any time.&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&lt;&lt; =
Text
deleted &gt;&gt;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;
dot3OamMaxOamPduSize OBJECT-TYPE<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
SYNTAX&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Integer32 =
(64..1522)<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] This =
should be
Unsigned32.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] Also, =
is 1522
really the max?<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>MBS:&nbsp; I'll
change to Unsigned32 though its not clear to me why =
thats<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>better.&nbsp; The
maximum value, as defined in [802.3ah] is equal =
the<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>maximum =
untagged
frame size (which is undergoing change in 802.3 as =
we<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>speak).&nbsp; I'd
like to put a variable in here that ties it to =
the<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>maxUntaggedFrameSize,
but I don't know what that variable would =
be.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>Numerically, it
should currently be 1518, not 1522.&nbsp; <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
UNITS&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&quot;bytes&quot;<o:p></o:p></span></font><=
/p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
MAX-ACCESS&nbsp; read-only<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
STATUS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; current =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>M.
Squire&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Expires - September
2005&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
[Page
13] <o:p></o:p></span></font></p>

<font size=3D2 color=3Dnavy face=3D"Courier New"><span =
style=3D'font-size:10.0pt;
font-family:"Courier New";color:navy'><br clear=3Dall =
style=3D'page-break-before:
always'>
</span></font>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;
EFM OAM
MIB&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;
March 2005<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
DESCRIPTION <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&quot;The largest OAMPDU that the OAM entity supports.&nbsp; =
OAM<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
entities exchange maximum OAMPDU sizes and negotiate to =
use<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
the smaller of the two maximum OAMPDU sizes between the =
peers.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
This value is determined by the local implementation.&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&quot;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
REFERENCE&nbsp;&nbsp; &quot;[802.3ah], =
30.3.6.1.8&quot;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
::=3D { dot3OamEntry 4 }<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&lt;&lt;
Text deleted &gt;&gt; <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;
------------------------------------------------------------------<o:p></=
o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;
--<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;
-- Ethernet OAM Peer group<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;
--<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>M.
Squire&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Expires - September
2005&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
[Page
14] <o:p></o:p></span></font></p>

<font size=3D2 color=3Dnavy face=3D"Courier New"><span =
style=3D'font-size:10.0pt;
font-family:"Courier New";color:navy'><br clear=3Dall =
style=3D'page-break-before:
always'>
</span></font>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;
EFM OAM
MIB&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;
March 2005<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;
dot3OamPeerTable OBJECT-TYPE<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
SYNTAX&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; SEQUENCE OF =
Dot3OamPeerEntry<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
MAX-ACCESS&nbsp; not-accessible<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
STATUS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
current<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
DESCRIPTION <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&quot;Information about the OAM peer for a particular Ethernet =
like<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
interface. OAM entities communicate with a single OAM =
peer<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
entity on full-duplex Ethernet links on which OAM is =
enabled<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
and operating properly.&nbsp; <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
In certain states, the OAM peer information is not =
available.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Whether peer information is available is communicated via =
the<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
dot3OamPeerStatus object.&nbsp; When this object is inactive, =
all<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
other information in the row is to be considered invalid.&nbsp; &quot; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
::=3D { dot3OamMIB 2 }<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] Fix =
this table
DESCRIPTION as per global comments<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] The =
issue of
communicating that when the value of =
dot3OamPeerStatus<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] is
'inactive(2)' that the values of the other columns =
is<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] =
unknown, is
difficult. Yes, it is said in the =
DESCRIPTION<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] =
clause for the
row, but I suggest that you also put<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] that =
in the
DESCRIPTION clause for each column. Also,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] if =
possible,
define a value for each column that is<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] =
returned when
dot3OamPeerStatus is 'inactive(2)',<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] which =
CAN NOT
be a valid value with dot3OamPeerStatus<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] has =
value
'active(1)'.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>MBS: =
I've
attempted to incorporate this comment in the next =
revision,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>and the =
invalid
statement is repeated for every column.&nbsp; Its not =
clear<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>how to =
devine
unique invalid values for every column - for example =
a<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>bits =
field or an
unsigned32 where all 2^32 values are allowed.&nbsp; So =
I<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>wasn't =
able to
implement that part of the comment for every column.&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;
dot3OamPeerEntry OBJECT-TYPE<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
SYNTAX&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Dot3OamPeerEntry<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
MAX-ACCESS&nbsp; not-accessible<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
STATUS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
current<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
DESCRIPTION <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&quot;An entry in the table, containing information on the peer =
OAM<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
entity for a single Ethernet like interface.&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Note that there is at most one OAM peer for each Ethernet =
like<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
interface.&nbsp; There is exactly one row in this table for =
each<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Ethernet like interface supporting OAM.&nbsp; =
&quot;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;
&nbsp;&nbsp;&nbsp;INDEX&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; { ifIndex =
}<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
::=3D { dot3OamPeerTable 1 }<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] Fix. =
Note, I
believe it would be clearer to say<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] (in =
the
DESCRIPTION for the table) that a row<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] =
exists in this
table for each row in the OAM control<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] =
table.&nbsp; <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>MBS:&nbsp; I'm
not sure what you mean by the &quot;OAM control table&quot;, but =
the<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>intent =
is that
there is at most one row for every entry in =
the<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>dot3OamTable.&nbsp;
There may be zero rows in this table for an entry =
in<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>the =
dot3OamTable
if the peer information has not been =
discovered<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>(yet).&nbsp; I
guess we could say there's always a row but that =
its<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>information is
inactive(2) - is that your point?&nbsp; That probably =
is<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>simpler.&nbsp;&nbsp;
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;
Dot3OamPeerEntry ::=3D<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
SEQUENCE {<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
dot3OamPeerStatus&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
INTEGER,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
dot3OamPeerMacAddress&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
MacAddress, <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
dot3OamPeerVendorOui&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Dot3Oui, <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
dot3OamPeerVendorInfo&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Unsigned32, <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
dot3OamPeerMode&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
INTEGER,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
dot3OamPeerMaxOamPduSize&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;
Integer32,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
dot3OamPeerConfigRevision&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;
Unsigned32,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
dot3OamPeerFunctionsSupported&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
BITS<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
}<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;
dot3OamPeerStatus OBJECT-TYPE<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
SYNTAX&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; INTEGER =
{<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
active(1),<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;inactive(2)<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
}<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
MAX-ACCESS&nbsp; read-only<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span lang=3DFR
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>M.
Squire&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Expires - September
2005&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
[Page
15] <o:p></o:p></span></font></p>

<font size=3D2 color=3Dnavy face=3D"Courier New"><span lang=3DFR =
style=3D'font-size:10.0pt;
font-family:"Courier New";color:navy'><br clear=3Dall =
style=3D'page-break-before:
always'>
</span></font>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span lang=3DFR
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span lang=3DFR
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;
</span></font><font size=3D2 color=3Dnavy face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>EFM OAM
MIB&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;
March 2005<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
STATUS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
current<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
DESCRIPTION <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;
&nbsp;&nbsp;&nbsp;&nbsp;&quot;This object indicates whether the =
information in
this row<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
should be considered valid.&nbsp; When active(1), the =
information<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
is valid and represents the current peer of the OAM =
entity.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
When inactive(2), the information in this row is invalid.&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
A value of inactive(2) is returned if the dot3OamOperStatus =
is<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
disabled, passiveWait, or activeSendLocal.&nbsp; For all =
other<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
values of dot3OamOperStatus, a value of active(1) is returned.&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&quot;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
::=3D { dot3OamPeerEntry 1 }<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] The =
above
doesn't seem possible. Please check.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] It =
seems that
only when dot3OamOperStatus has the<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] value =
of
'operational(9)' can this have value =
'active(1)'<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>MBS:&nbsp; The
intent is that you know about the peer entity before =
OAM<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>becomes =
fully
operational(9).&nbsp; As soon as you receive one frame =
from<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>the peer =
you know
their basic info (there is a multi-frame =
exchange<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>required =
for
initialization).&nbsp; So I believe the statement is =
correct<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>as =
is.&nbsp; <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;
dot3OamPeerMacAddress OBJECT-TYPE<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
SYNTAX&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
MacAddress<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
MAX-ACCESS&nbsp; read-only<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
STATUS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
current<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
DESCRIPTION <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&quot;The MAC address of the peer OAM entity.&nbsp; The MAC address =
is<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
derived from the most recently received OAMPDU.&nbsp; This value =
is<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
initialized to all zeros (0x000000000000).&nbsp; This value =
is<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
invalid if the dot3OamPeerStatus is inactive.&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] This =
seems
pretty convoluted. Why not say &quot;The MAC =
address<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>]]&nbsp;&nbsp; of
the peer OAM entity. &nbsp;The MAC address =
is<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>]]&nbsp;&nbsp;
derived from the most recently received valid =
OAMPDU.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>]]&nbsp;&nbsp;
The value is all zeros (0x000000000000) when the =
peer's<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>]]&nbsp;&nbsp;
MAC address unknown, such as when the value =
of<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>]]&nbsp;&nbsp;
dot3OamPeerStatus is 'inactive(2)'.&quot;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>]]<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>]]&nbsp;&nbsp; By
the way, it seems like a value could be =
obtained<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>]]&nbsp;&nbsp;
even when dot3OamPeerStatus is =
'inactive(2)'.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>]]&nbsp;&nbsp; If
so, is it useful?<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>MBS;&nbsp; I
didn't see any use, hence the current indications that its garbage if
'inactive'.&nbsp; Related to your general comment of simplification, =
I'll
change the description to indicate zeros are returned whenever the
dot3OamPeerStatus is inactive(2).&nbsp; <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
An OAMPDU is indicated by a valid frame with (1) =
destination<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
MAC address equal to that of the reserved MAC address for =
Slow<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Protocols (See 43B of [802.3ah]), (2) a lengthOrType =
field<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
equal to the reserved type for Slow Protocols, (3) and a =
Slow<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Protocols subtype equal to that of the subtype reserved =
for<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
OAM.&nbsp; &quot;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] Not =
sure this
is needed in this definition.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>MBS;&nbsp; I
don't mind removing it - in fact I prefer to.&nbsp; It was =
added<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>because =
I was
asked to specfically define what causes this value =
to<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>change.&nbsp; The
event that causes an update to this value is =
the<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>reception of an
OAMPDU, which is defined as above.&nbsp; I'm thrilled to =
be<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>allowed =
to kill
it.&nbsp; <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
REFERENCE&nbsp;&nbsp; &quot;[802.3ah], 30.3.6.1.5.&quot;&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
::=3D { dot3OamPeerEntry 2 }<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;
dot3OamPeerVendorOui OBJECT-TYPE<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
SYNTAX&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Dot3Oui<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
MAX-ACCESS&nbsp; read-only<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
STATUS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
current<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
DESCRIPTION <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&quot;The OUI of the OAM peer as reflected in the =
latest<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Information OAMPDU received with a Local Information TLV.&nbsp; =
The<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
OUI can be used to identify the vendor of the remote =
OAM<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
entity.&nbsp; This value is initialized to all zeros =
(0x000000).<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
This value is considered invalid if the dot3OamPeerStatus =
is<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
inactive.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] Can =
this be
written to be simpler (see above)<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>MBS;
Simplification will be attempted in next revision.&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
REFERENCE&nbsp;&nbsp; &quot;[802.3ah], =
30.3.6.1.16.&quot;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
::=3D { dot3OamPeerEntry 3 }<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;
dot3OamPeerVendorInfo OBJECT-TYPE<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
SYNTAX&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Unsigned32<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
MAX-ACCESS&nbsp; read-only<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
STATUS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
current<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
DESCRIPTION <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&quot;The Vendor Info of the OAM peer as reflected in the =
latest<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Information OAMPDU received with a Local Information TLV.&nbsp; =
The<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
vendor information field is within the Local Information =
TLV,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
and can be used to determine additional information about =
the<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
peer entity.&nbsp; The format of the vendor information =
is<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
unspecified within the 32-bit field.&nbsp; This value is =
intialized<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>]]&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
spelling error^^^^^^^^^<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>MBS: =
fixed.&nbsp;
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
to all zeros (0x00000000).&nbsp; This value is invalid if =
the<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
dot3OamPeerStatus is inactive.&nbsp; <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] Can =
this be
written to be simpler (see above)<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] Also, =
the
802.3af spec is confusing to me. From<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] it, =
the value
seems like it should have<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] =
SYNTAX clause
value of OCTET STRING(SIZE(4)).<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] But =
maybe an
&quot;Unsigned32&quot; value is OK. If so,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] the =
0x00000000
is very strange. It should just be 0.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>MBS: I =
left this
as Unsigned32 as its just a 32-bit field,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>non-formatted
field.&nbsp; But I switched to 0 instead of 0x00000000. =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
REFERENCE&nbsp;&nbsp; &quot;[802.3ah], 30.3.6.1.17.&quot;&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
::=3D { dot3OamPeerEntry 4 }<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&lt;&lt;
Text deleted &gt;&gt; <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;
</span></font><font size=3D2 color=3Dnavy face=3D"Courier New"><span =
lang=3DFR
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>--------------------------------------------------------=
----------<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span lang=3DFR
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;
--<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span lang=3DFR
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span lang=3DFR
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span lang=3DFR
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>M.
Squire&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Expires - September
2005&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
[Page
19] <o:p></o:p></span></font></p>

<font size=3D2 color=3Dnavy face=3D"Courier New"><span lang=3DFR =
style=3D'font-size:10.0pt;
font-family:"Courier New";color:navy'><br clear=3Dall =
style=3D'page-break-before:
always'>
</span></font>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span lang=3DFR
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span lang=3DFR
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;
</span></font><font size=3D2 color=3Dnavy face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>EFM OAM
MIB&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;
March 2005<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;
-- Ethernet OAM Loopback group<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;
--<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;
dot3OamLoopbackTable OBJECT-TYPE<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
SYNTAX&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; SEQUENCE OF =
Dot3OamLoopbackEntry<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
MAX-ACCESS&nbsp; not-accessible<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
STATUS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
current<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
DESCRIPTION <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&quot;This table contains methods to control the loopback state =
of<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
the local link as well as indicating the status of =
the<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
loopback function.&nbsp; <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&nbsp;&nbsp;Loopback can be used to place the remote OAM entity in a =
state<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
where every received frame (except OAMPDUs) are echoed =
back<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
over the same interface on which they were received.&nbsp;&nbsp; In =
this<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
state, at the remote entity, 'normal' traffic is disabled =
as<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
only the looped back frames are transmitted on the =
interface.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Loopback is thus an intrusive operation that prohibits =
normal<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
data flow and should be used accordingly.&nbsp; &quot; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
::=3D { dot3OamMIB 3 }<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] See =
global
comment about tables, and comment on table<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]]
dot3OamPeerTable.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>MBS: =
done<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] This =
table is
used to put the remote end in loopback<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] and =
report the
loopback status of the local and remote<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] =
ports<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] I'm =
confused
as to whether both local and remote ports<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] can =
be put in
loopback. And if not, then what happens<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] if =
the peer
has put the local port in loopback and<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] an =
attempt is
made to put the peer's port (the remote<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] port) =
in
loopback?<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>MBS: =
Simultaneous
loopback on both ends is not possible - the =
protocol<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>detects =
such an
action and an election algorithm is used to =
determine<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>which =
port enters
loopback state and which does not.&nbsp; <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;
dot3OamLoopbackEntry OBJECT-TYPE<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
SYNTAX&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Dot3OamLoopbackEntry<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
MAX-ACCESS&nbsp; not-accessible<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
STATUS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
current<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
DESCRIPTION <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&quot;An entry in the table, containing information on the =
loopback<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
status for a single Ethernet like interface.&nbsp; There is =
an<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
entry in this table for every Ethernet like interface on =
which<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
supports OAM and loopback function within OAM (as indicated =
in<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
dot3OamFunctionsSupported).&nbsp; &quot;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] See =
previous
comments on rows<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>MBS: =
Changed to
indicated automatic creation and conditions.&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
INDEX&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; { ifIndex =
}<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
::=3D { dot3OamLoopbackTable 1 }<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;
Dot3OamLoopbackEntry ::=3D<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
SEQUENCE {<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
dot3OamLoopbackCommand&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;
INTEGER,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
dot3OamLoopbackStatus&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;
INTEGER,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
dot3OamLoopbackIgnoreRx&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;
INTEGER<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
}<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;
dot3OamLoopbackCommand OBJECT-TYPE<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
SYNTAX&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; INTEGER { =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
noLoopback (1),<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
startRemoteLoopback (2),<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
stopRemoteLoopback (3)<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
} <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
MAX-ACCESS&nbsp; read-write<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span lang=3DFR
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>M.
Squire&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Expires - September
2005&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
[Page
20] <o:p></o:p></span></font></p>

<font size=3D2 color=3Dnavy face=3D"Courier New"><span lang=3DFR =
style=3D'font-size:10.0pt;
font-family:"Courier New";color:navy'><br clear=3Dall =
style=3D'page-break-before:
always'>
</span></font>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span lang=3DFR
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span lang=3DFR
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;
</span></font><font size=3D2 color=3Dnavy face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>EFM OAM
MIB&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;
March 2005<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
STATUS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; current =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
DESCRIPTION <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&quot;This attribute initiates or terminates remote loopback =
with<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
an OAM peer.&nbsp; Writing startRemoteLoopback(2) to this =
attribute<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
cause the local OAM client to send a loopback OAMPDU to =
the<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
OAM peer with the loopback enable flags set.&nbsp; =
Writing<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
stopRemoteLoopback(3) to this attribute will cause the =
local<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
OAM client to send a loopback OAMPDU to the OAM peer with =
the<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
loopback enable flags cleared.&nbsp; Writing noLoopback to =
this<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
attribute has no effect.&nbsp; <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Writes to this attribute are ignored unless the OAM status =
of<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
this interface is 'operational' (dot3OamOperStatus).&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
The attribute always returns noLoopback on a read.&nbsp; =
To<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
determine the loopback status, use the =
attribute<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
dot3OamLoopbackStatus.&nbsp; &quot; <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
REFERENCE&nbsp;&nbsp; &quot;[802.3ah], 57.2.11&quot;&nbsp;&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
::=3D { dot3OamLoopbackEntry 1 }<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] This =
object
and the next need to be combined into a<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] =
action/status
object.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] The =
combined
object support all the enum values<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] for
dot3OamLoopbackStatus (which would be =
read-only)<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] and
startRemoteLoopback and stopRemoteLoopback<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] from =
this
object. Writes of startRemoteLoopback<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] when =
remote is
already loopbacked (or dot3OamOperStatus<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] is =
not
operational) cause no operation.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] =
Likewise,
writes of stopRemoteLoopback when remote<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] is =
not
loopbacked (or dot3OamOperStatus<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] is =
not
operational) cause no operation.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] Note: =
just
don't know what happens when<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] =
current value
is localLoopback.&nbsp; <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>MBS: I =
can change
it, but I'd like to be pointed to an example.&nbsp; =
All<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>of the =
examples
I've come across had two objects, one for the =
actions,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>one for =
the
status, which is where this model comes from.&nbsp; =
During<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>discussion with
the group, two objects were suggested as the =
desired<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>approach.&nbsp; <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&lt;&lt; =
Text
deleted &gt;&gt;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;
------------------------------------------------------------------<o:p></=
o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>M.
Squire&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Expires - September
2005&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
[Page
22] <o:p></o:p></span></font></p>

<font size=3D2 color=3Dnavy face=3D"Courier New"><span =
style=3D'font-size:10.0pt;
font-family:"Courier New";color:navy'><br clear=3Dall =
style=3D'page-break-before:
always'>
</span></font>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;
EFM OAM
MIB&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;
March 2005<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;
--<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;
-- Ethernet OAM Statistics group<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;
--<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;
dot3OamStatsTable OBJECT-TYPE<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
SYNTAX&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; SEQUENCE OF =
Dot3OamStatsEntry<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
MAX-ACCESS&nbsp; not-accessible<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
STATUS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
current<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
DESCRIPTION <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&quot;Statistics for the OAM function on a particular Ethernet =
like<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
interface.&quot; <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
::=3D { dot3OamMIB 4 }<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] See =
previous
comments on tables.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>MBS: =
Done<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] Add a =
note in
the commentary section as to why the =
counters<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] in =
this table
are Counter32 instead of Counter64!<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>MBS: =
Done.&nbsp;
The size of the counters was selected to match the size of the counters =
as
defined in 802.3.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&lt;&lt;
Text deleted &gt;&gt;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;
dot3OamUnsupportedCodesTx OBJECT-TYPE<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
SYNTAX&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Counter32<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
UNITS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&quot;frames&quot;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
MAX-ACCESS&nbsp; read-only<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
STATUS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
current<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
DESCRIPTION <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&quot;A count of the number of OAMPDUs transmitted on =
this<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
interface with an unsupported op-code.&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] This =
is very
strange.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] Why =
would you
send an &quot;unsupported code&quot;?<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] How =
would you know
that you sent an &quot;unsupported =
code&quot;?<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>MBS: =
Granted it
seems a little strange.&nbsp; The variable is supported =
in<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>the =
802.3ah
standard, so I decided to expose it via the MIB.&nbsp; =
Since<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>Ethernet =
OAM
could be supported in the HW or in the SW, the =
thought<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>was =
someone might
try to do things where the underlying layer =
doesn't<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>support =
that
thing (for example, loopback), and you might want to =
know<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>about =
it.&nbsp; <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&lt;&lt;
Text deleted &gt;. <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;
dot3OamFramesLostDueToOam OBJECT-TYPE<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] =
Strange
descriptor. How about =
&quot;dot3OamDroppedTxFrames&quot;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>MBS: I'm =
trying
to match the names in 802.3ah as closely as =
possible<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>to make =
the
implmeentaiton easier.&nbsp; In 802.3, its =
called<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>FramesLostDueToOam.&nbsp;
The reason its not &quot;OamDroppedTxFrames&quot; =
is<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>because =
that
might sound like OAM frames are dropped, when really =
any<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>frame =
might be
dropped because OAM took precedence.&nbsp; <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
SYNTAX&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Counter32<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
UNITS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&quot;frames&quot;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
MAX-ACCESS&nbsp; read-only<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
STATUS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
current<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
DESCRIPTION <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&quot;A
count of the number of frames that were dropped by the =
OAM<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
multiplexer.&nbsp; Since the OAM mulitplexer has multiple =
inputs<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
and a single output, there may be cases where frames =
are<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
dropped due to transmit resource contention.&nbsp; This counter =
is<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
incremented whenever a frame is dropped by the OAM =
layer.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
When this counter is incremented, no other counters in =
this<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
MIB are incremented.&nbsp; <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Discontinuities of this counter can occur at =
re-initialization<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
of the management system, and at other times as indicated =
by<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
the value of the ifCounterDiscontinuityTime.&nbsp; =
&quot;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
REFERENCE&nbsp;&nbsp; &quot;[802.3ah], 30.3.6.1.46.&quot;&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
::=3D { dot3OamStatsEntry 17 }<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;
------------------------------------------------------------------<o:p></=
o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;
--<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;
-- Ethernet OAM Event Configuration group<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;
--<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&lt;&lt;
Text deleted &gt;&gt; <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;
dot3OamErrSymPeriodWindowHi OBJECT-TYPE<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] This =
needs to
be combined with the next object<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] and =
given
syntax CounterBasedGauge64<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>MBS: =
This was
discussed on the list.&nbsp; The discussion said =
that<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>CounterBasedGauge64
is read-only and since this is a writable =
value,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>it =
wouldn't
apply.&nbsp; <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&lt;&lt; =
Text
deleted &gt;&gt;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;
dot3OamErrFrameWindow OBJECT-TYPE<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
SYNTAX&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Unsigned32<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
UNITS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &quot;tenths of a =
second&quot;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
MAX-ACCESS&nbsp; read-write<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
STATUS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
current<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
DESCRIPTION <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&quot;The amount of time (in 100ms increments) over which =
the<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] why =
not just
say &quot;in tenth of a second intervals&quot; =
instead<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] of =
&quot;in
100ms intervals&quot;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>MBS: =
100ms seems
easier to say then &quot;tenths of a =
second&quot;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
threshold is defined.&nbsp; The default value is 10 (1 second).&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
If dot3OamErrFrameThreshold frame errors occur within a =
window<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
of dot3OamErrFrameWindow seconds (measured in tenths =
of<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
seconds), an Event Notification OAMPDU should be generated =
with<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
an Errored Frame Event TLV indicating the threshold has =
been<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
crossed in this window.&nbsp; &quot;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
REFERENCE&nbsp;&nbsp; &quot;[802.3ah], 30.3.6.1.36&quot;&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
::=3D { dot3OamEventConfigEntry 9 }<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>M.
Squire&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Expires - September
2005&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
[Page
37] <o:p></o:p></span></font></p>

<font size=3D2 color=3Dnavy face=3D"Courier New"><span =
style=3D'font-size:10.0pt;
font-family:"Courier New";color:navy'><br clear=3Dall =
style=3D'page-break-before:
always'>
</span></font>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;
EFM OAM =
MIB&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;
March 2005<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;
dot3OamErrFrameThreshold OBJECT-TYPE<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
SYNTAX&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Unsigned32<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] What =
happens
when the value is zero?<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>MBS: =
This would
result in an event notification being sent at the =
end<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>of every
measuring period.&nbsp; So if the window were 30sec, you'd get =
an<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>OAMPDU =
every 30s
saying how many errored frame there were.&nbsp; Some =
may<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>consider =
this
useless,but others thought it a way to get =
regular<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>periodic =
updtes
on these error counters (e.g. tell me what the =
values<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>are =
every 30s). &nbsp;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&lt;&lt;
Text deleted &gt;&gt;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;
------------------------------------------------------------------<o:p></=
o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;
-- <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;
-- Ethernet OAM Event Status group <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;
-- <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;
dot3OamEventLogTable&nbsp;&nbsp; OBJECT-TYPE =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
SYNTAX&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; SEQUENCE OF =
Dot3OamEventLogEntry <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
MAX-ACCESS&nbsp;&nbsp; not-accessible <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
STATUS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; current =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
DESCRIPTION <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] See =
comments
on tables<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] On =
this table,
can it have an infinite number of entries?<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] Most =
likely
not. In other tables, there is some =
indication<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] that =
says the
max number (not always available), but<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] =
always
something that says to either stop adding =
entries,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] or =
delete the
oldest, or some other algorithm to replace<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] the =
least
important with a new one.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>MBS: =
Added words
to say that size is implemetnation dependent, =
and<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>that =
older
entries should be automtically deleted to make room =
for<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>newer
entries.&nbsp; <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&quot;This table records a history of the events that have =
occurred<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
at the Ethernet OAM level.&nbsp; These events can include =
locally<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
detected events, which may result in locally =
generated<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
OAMPDUs, and remotely detected events, which are detected =
by<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
the OAM peer entity and signaled to the local entity =
via<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Ethernet OAM.&nbsp; Ethernet OAM events can be signaled by =
Event<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Notification OAMPDUs or by the flags field in any OAMPDU.&nbsp; =
&quot;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] Need =
to
indicate that there are threshold crossing =
events<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] and
nonthreshold events. For each, indicate the columns =
that<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] have
meaningful values. The descriptions about the MAX =
values<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] =
didn't make
sense until I read the descriptions of the<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] =
notifications
and saw what was going on. <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>MBS: =
Added words
to say which columsn only apply to threshold =
crossing<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>events. =
&nbsp;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
::=3D { dot3OamMIB 6 } <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;
dot3OamEventLogEntry OBJECT-TYPE <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
SYNTAX&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Dot3OamEventLogEntry =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
MAX-ACCESS&nbsp; not-accessible <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
STATUS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; current =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
DESCRIPTION &quot;An entry in the dot3OamEventLogTable.&quot; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] See =
previous comments
on rows.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>MBS: =
Done.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] Can =
selected
entries in this table be deleted by<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] =
management
operations?<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>MBS: The =
thought
was no,that the table reflects what happened (to the extent that it =
can).&nbsp;
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
INDEX&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; { ifIndex, =
dot3OamEventLogIndex }<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;::=3D
{ dot3OamEventLogTable 1 } <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&lt;&lt;
Text deleted &gt;&gt;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;
dot3OamEventLogType&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
OBJECT-TYPE<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
SYNTAX&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Unsigned32 =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
MAX-ACCESS&nbsp; read-only<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
STATUS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; current =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
DESCRIPTION <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&quot;The type of event that generated this entry in the event =
log.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
When the OUI is the IEEE 802.3 OUI of 0x0180C2, the =
following<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
event types are defined:<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;
erroredSymbolEvent(1), <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;
erroredFramePeriodEvent (2), <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;
erroredFrameEvent(3),<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;
erroredFrameSecondsEvent(4), <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;
linkFault(256), <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;
dyingGaspEvent(257),<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;
criticalLinkEvent(258)<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
The first four are considered threshold crossing events =
as<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&nbsp;&nbsp;&nbsp;they are generated when a metric exceeds a given value =
within<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
a specified window.&nbsp; The other three are not =
threshold<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
crossing events.&nbsp; <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
When the OUI is not 0x0180C2, then some other organization =
has<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
defined the event space.&nbsp; If event subtyping is known to =
the<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
implementation, it may be reflected here.&nbsp; Otherwise, =
this<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
value should return all Fs (0xFFFFFFFF).&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&quot;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] If =
this is an
Unsigned32, then say this in numeric<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] terms =
and not
in terminology used for octet strings.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>MBS: =
added
decimal value in addition to all Fs.&nbsp; <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
REFERENCE&nbsp;&nbsp; &quot;[802.3ah], 30.3.6.1.10 and =
57.5.3.&quot;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
::=3D { dot3OamEventLogEntry 4 }<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&lt;&lt; =
Text
deleted &gt;&gt;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] I'm =
not sure
that I understand the objects<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]]
dot3OamEventLogRunningTotal and<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]]
dot3OamEventLogEventTotal. It<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] seems =
like
dot3OamEventLogRunningTotal is the<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] value =
of a
counter that is being thresholded,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] and
dot3OamEventLogEventTotal is the count of<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] the =
event
crossings. <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] These =
counts
seem possibly expensive to do.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] Ok - =
after
reading 802.3af, I see what is going on.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] The
descriptions below are really difficult to<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] =
understand.
They need a rewrite.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>MBS: =
Rewrite will
be attempted.&nbsp; <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&lt;&lt; =
Text
deleted &gt;&gt;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;
------------------------------------------------------------------<o:p></=
o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;
-- <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;
-- Ethernet OAM Notifications<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;
-- <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;
dot3OamNotifs OBJECT IDENTIFIER ::=3D { dot3OamMIB 7 =
}<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;
dot3OamNotifsPrefix OBJECT IDENTIFIER ::=3D {dot3OamNotifs =
0}<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] =
remove these,
and update OID values for notifications<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>MBS: I =
will
delete these and replace the dot3OamNotifsPrefix in =
the<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>object =
below with
dot3OamNotifications that you added earlier in =
the<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>MIB.&nbsp; <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&lt;&lt;
Text deleted &gt;&gt;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;
------------------------------------------------------------------<o:p></=
o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;
--<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;
-- Ethernet OAM Compliance group<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;
</span></font><font size=3D2 color=3Dnavy face=3D"Courier New"><span =
lang=3DFR
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>--<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span lang=3DFR
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span lang=3DFR
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span lang=3DFR
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;
dot3OamGroups OBJECT IDENTIFIER ::=3D { dot3OamConformance 1 =
}<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span lang=3DFR
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;
dot3OamCompliances OBJECT IDENTIFIER ::=3D { dot3OamConformance 2 =
}<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span lang=3DFR
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span lang=3DFR
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;
-- Compliance statements<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span lang=3DFR
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span lang=3DFR
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;
dot3OamCompliance MODULE-COMPLIANCE <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span lang=3DFR
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
STATUS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
current<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span lang=3DFR
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
DESCRIPTION &quot;The compliance statement for managed =
entities<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span lang=3DFR
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span lang=3DFR
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span lang=3DFR
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>M.
Squire&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Expires - September
2005&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
[Page
46] <o:p></o:p></span></font></p>

<font size=3D2 color=3Dnavy face=3D"Courier New"><span lang=3DFR =
style=3D'font-size:10.0pt;
font-family:"Courier New";color:navy'><br clear=3Dall =
style=3D'page-break-before:
always'>
</span></font>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span lang=3DFR
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span lang=3DFR
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;
EFM OAM
MIB&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;
March 2005<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span lang=3DFR
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span lang=3DFR
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span lang=3DFR
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font><font size=3D2 color=3Dnavy face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>supporting OAM on
Ethernet like interfaces.&nbsp; <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&quot;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;
MODULE&nbsp;&nbsp; -- this module<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
MANDATORY-GROUPS { dot3OamControlGroup, <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
dot3OamPeerGroup, <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
dot3OamStatsBaseGroup <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;
}<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
GROUP&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
dot3OamLoopbackGroup<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
DESCRIPTION <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&quot;This group is mandatory for all IEEE 802.3 =
OAM<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
implementations that support loopback functionality. =
&quot;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
GROUP&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
dot3OamErrSymbolPeriodEventGroup<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
DESCRIPTION <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&quot;This group is mandatory for all IEEE 802.3 =
OAM<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
implementations that support event functionality. =
&quot;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
GROUP&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
dot3OamErrFramePeriodEventGroup<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
DESCRIPTION <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&quot;This group is mandatory for all IEEE 802.3 =
OAM<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
implementations that support event functionality. =
&quot;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
GROUP&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
dot3OamErrFrameEventGroup<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
DESCRIPTION <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&quot;This group is mandatory for all IEEE 802.3 =
OAM<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
implementations that support event functionality. =
&quot;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
GROUP&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
dot3OamErrFrameSecsSummaryEventGroup<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
DESCRIPTION <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&quot;This group is mandatory for all IEEE 802.3 =
OAM<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;implementations
that support event functionality. &quot;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
GROUP dot3OamFlagEventGroup<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
DESCRIPTION<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&quot;This group is optional for all IEEE 802.3 =
OAM<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
implementations.&nbsp; The ability to send critical events or =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
dying gasp events is not required in any =
system.&quot;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
GROUP&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
dot3OamEventLogGroup<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
DESCRIPTION <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&quot;This group is optional for all IEEE 802.3 =
OAM<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
implementations. &quot;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] There =
will not
be any local events in the log table<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] =
unless some of
the event groups are implemented.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>MBS:
Correct.&nbsp; Is that a question or are you suggesting some =
action?&nbsp; <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
GROUP&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
dot3OamNotificationGroup<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
DESCRIPTION <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&quot;This group is optional for all IEEE 802.3 =
OAM<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span lang=3DFR
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>M.
Squire&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Expires - September
2005&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
[Page
47] <o:p></o:p></span></font></p>

<font size=3D2 color=3Dnavy face=3D"Courier New"><span lang=3DFR =
style=3D'font-size:10.0pt;
font-family:"Courier New";color:navy'><br clear=3Dall =
style=3D'page-break-before:
always'>
</span></font>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span lang=3DFR
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span lang=3DFR
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;
</span></font><font size=3D2 color=3Dnavy face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>EFM OAM
MIB&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;
March 2005<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
implementations. &quot;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] This =
group
requires implementation of the log table,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] since =
the
objects in the notifications are objects<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] in =
the log
table!<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>MBS: I'm =
not sure
what to do here, will have to think about it.&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
::=3D { dot3OamCompliances 1}<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>The way =
this
module compliance is written, there are<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>a couple =
of
unconditionally optional items (like the<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>notifications and
logging). Also, there can be mix and<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>match of =
optional
items. This is bad for IETF standards<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>track
progression. You might consider having two<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>module =
compliance
specifications - a minimal and<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>maximal. =
Others,
like Bert, and provide better<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>advice =
as to the
best practices in IETF standards<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>track =
MIB
modules.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;
dot3OamControlGroup OBJECT-GROUP<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
OBJECTS&nbsp;&nbsp;&nbsp;&nbsp; {&nbsp;&nbsp; =
dot3OamAdminState,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;
dot3OamOperStatus,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;
dot3OamMode,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;
dot3OamMaxOamPduSize,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;
dot3OamConfigRevision,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;
dot3OamFunctionsSupported<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
}<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
STATUS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
current<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
DESCRIPTION <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&quot;A collection of objects providing the =
abilities,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
configuration, and status of an Ethernet OAM entity.&nbsp; =
&quot;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
::=3D { dot3OamGroups 1 }<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;
dot3OamPeerGroup OBJECT-GROUP<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
OBJECTS&nbsp;&nbsp;&nbsp;&nbsp; {&nbsp;&nbsp; =
dot3OamPeerStatus,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;
dot3OamPeerMacAddress,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;
dot3OamPeerVendorOui,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;
dot3OamPeerVendorInfo,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;
dot3OamPeerMode,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;
dot3OamPeerFunctionsSupported,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;
dot3OamPeerMaxOamPduSize,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;
dot3OamPeerConfigRevision<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
}<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
STATUS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
current<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
DESCRIPTION <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&quot;A collection of objects providing the =
abilities,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
configuration, and status of a peer Ethernet OAM entity.&nbsp; =
&quot;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
::=3D { dot3OamGroups 2 }<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;
dot3OamStatsBaseGroup OBJECT-GROUP<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
OBJECTS&nbsp;&nbsp;&nbsp;&nbsp; {&nbsp;&nbsp; =
dot3OamInformationTx,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;
dot3OamInformationRx,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;
dot3OamUniqueEventNotificationTx,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;
dot3OamUniqueEventNotificationRx,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;
dot3OamDuplicateEventNotificationTx,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;
dot3OamDuplicateEventNotificationRx,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;
dot3OamLoopbackControlTx,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;
dot3OamLoopbackControlRx,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;
dot3OamVariableRequestTx,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;
dot3OamVariableRequestRx,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;
dot3OamVariableResponseTx,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;
dot3OamVariableResponseRx,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;
dot3OamOrgSpecificTx,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>M.
Squire&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Expires - September 2005&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[Page
48] <o:p></o:p></span></font></p>

<font size=3D2 color=3Dnavy face=3D"Courier New"><span =
style=3D'font-size:10.0pt;
font-family:"Courier New";color:navy'><br clear=3Dall =
style=3D'page-break-before:
always'>
</span></font>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;
EFM OAM
MIB&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;
March 2005<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;
dot3OamOrgSpecificRx,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;
dot3OamUnsupportedCodesTx,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;
dot3OamUnsupportedCodesRx,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;
dot3OamFramesLostDueToOam<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
}<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
STATUS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
current<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
DESCRIPTION <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&quot;A collection of objects providing the statistics for =
the<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
number of various transmit and recieve events for OAM on =
an<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Ethernet like interface.&nbsp; Note that all of these counters =
must<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
be supported even if the related function (as described =
in<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
dot3OamFunctionsSupported) is not supported.&nbsp; =
&quot;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
::=3D { dot3OamGroups 3 }<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] The =
compliance
is not specified in group definitions.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>MBS: Its =
one of
the mandatory groups - what else are you looking for. =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;
dot3OamLoopbackGroup OBJECT-GROUP<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
OBJECTS&nbsp;&nbsp;&nbsp;&nbsp; {&nbsp;&nbsp; =
dot3OamLoopbackCommand,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;
dot3OamLoopbackStatus,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&nbsp;dot3OamLoopbackIgnoreRx<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
}<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
STATUS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
current<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
DESCRIPTION <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&quot;A collection of objects for controlling the OAM =
remote<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
loopback function.&nbsp; &quot;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
::=3D { dot3OamGroups 4 }<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;
dot3OamErrSymbolPeriodEventGroup =
OBJECT-GROUP<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
OBJECTS&nbsp;&nbsp;&nbsp;&nbsp; {&nbsp;&nbsp; =
dot3OamErrSymPeriodWindowHi,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;
dot3OamErrSymPeriodWindowLo,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;
dot3OamErrSymPeriodThresholdHi,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;
dot3OamErrSymPeriodThresholdLo,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;
dot3OamErrSymPeriodEvNotifEnable<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
}<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
STATUS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
current<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
DESCRIPTION <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&quot;A collection of objects for configuring the thresholds for =
an<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Errored Symbol Period Event.&nbsp; <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Each [802.3ah] defined Event Notification TLV has its =
own<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
conformance group because each event can be =
implemented<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
independently of any other.&nbsp; &quot;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
::=3D { dot3OamGroups 5 }<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;
dot3OamErrFramePeriodEventGroup =
OBJECT-GROUP<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
OBJECTS&nbsp;&nbsp;&nbsp;&nbsp; {&nbsp;&nbsp; =
dot3OamErrFramePeriodWindow,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;
dot3OamErrFramePeriodThreshold,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;
dot3OamErrFramePeriodEvNotifEnable<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
}<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
STATUS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
current<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
DESCRIPTION <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>M.
Squire&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Expires
- September
2005&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
[Page
49] <o:p></o:p></span></font></p>

<font size=3D2 color=3Dnavy face=3D"Courier New"><span =
style=3D'font-size:10.0pt;
font-family:"Courier New";color:navy'><br clear=3Dall =
style=3D'page-break-before:
always'>
</span></font>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;
EFM OAM
MIB&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;
March 2005<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&quot;A collection of objects for configuring the thresholds for =
an<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Errored Frame Period Event.&nbsp; <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Each [802.3ah] defined Event Notification TLV has its =
own<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
conformance group because each event can be =
implemented<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
independently of any other.&nbsp; &quot;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
::=3D { dot3OamGroups 6 }<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;
dot3OamErrFrameEventGroup OBJECT-GROUP<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
OBJECTS&nbsp;&nbsp;&nbsp;&nbsp; {&nbsp;&nbsp; =
dot3OamErrFrameWindow,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;
dot3OamErrFrameThreshold,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;
dot3OamErrFrameEvNotifEnable<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
}<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
STATUS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
current<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
DESCRIPTION <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&quot;A collection of objects for configuring the thresholds for =
an<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Errored Frame Event.&nbsp; <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Each [802.3ah] defined Event Notification TLV has its =
own<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
conformance group because each event can be =
implemented<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
independently of any other.&nbsp; &quot;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
::=3D { dot3OamGroups 7 }<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>]] Put =
this info
about 802.3af in the commentary section<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>MBS: =
Which
section are you refering to exactly?&nbsp; <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;
dot3OamErrFrameSecsSummaryEventGroup =
OBJECT-GROUP<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
OBJECTS&nbsp;&nbsp;&nbsp;&nbsp; {&nbsp;&nbsp; =
dot3OamErrFrameSecsSummaryWindow,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&nbsp;dot3OamErrFrameSecsSummaryThreshold,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;
dot3OamErrFrameSecsEvNotifEnable<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
}<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
STATUS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
current<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
DESCRIPTION <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&quot;A collection of objects for configuring the thresholds for =
an<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Errored Frame Seconds Summary Event.&nbsp; <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Each [802.3ah] defined Event Notification TLV has its =
own<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
conformance group because each event can be =
implemented<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
independently of any other.&nbsp; &quot;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
::=3D { dot3OamGroups 8 }<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;
dot3OamFlagEventGroup OBJECT-GROUP<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
OBJECTS&nbsp;&nbsp;&nbsp;&nbsp; {&nbsp;&nbsp; =
dot3OamDyingGaspEnable,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;
dot3OamCriticalEventEnable<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
}<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
STATUS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
current<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
DESCRIPTION <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&quot;A collection of objects for configuring the sending =
OAMPDUs<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
with the critical event flag or dying gasp flag enabled.&nbsp; =
&quot;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
::=3D { dot3OamGroups 9 }<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;
dot3OamEventLogGroup OBJECT-GROUP<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>M.
Squire&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Expires - September
2005&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
[Page
50] <o:p></o:p></span></font></p>

<font size=3D2 color=3Dnavy face=3D"Courier New"><span =
style=3D'font-size:10.0pt;
font-family:"Courier New";color:navy'><br clear=3Dall =
style=3D'page-break-before:
always'>
</span></font>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;
EFM OAM
MIB&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;
March 2005<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
OBJECTS {&nbsp; dot3OamEventLogTimestamp, <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
dot3OamEventLogOui, <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
dot3OamEventLogType,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
dot3OamEventLogLocation,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
dot3OamEventLogWindowHi,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;dot3OamEventLogWindowLo,<o:p></o:p></span><=
/font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
dot3OamEventLogThresholdHi,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
dot3OamEventLogThresholdLo,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
dot3OamEventLogValue,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
dot3OamEventLogRunningTotal,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
dot3OamEventLogEventTotal<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;
}<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
STATUS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
current<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
DESCRIPTION <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&quot;A collection of objects for configuring the thresholds for =
an<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Errored Frame Seconds Summary Event and maintaining the =
event<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
information.&nbsp; &quot;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
::=3D { dot3OamGroups 10 }<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;
dot3OamNotificationGroup NOTIFICATION-GROUP<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
NOTIFICATIONS {&nbsp;&nbsp; <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
dot3OamThresholdEvent,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
dot3OamNonThresholdEvent<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
}<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
STATUS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
current<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
DESCRIPTION <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&quot;A collection of notifications used by Ethernet OAM to =
signal<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
to a management entity that local or remote events have =
occured<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
on a specified Ethernet link.&quot;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
::=3D { dot3OamGroups 11 }<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;
END<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<div style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in =
0in 4.0pt'>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>

<hr size=3D3 width=3D"100%" align=3Dcenter tabindex=3D-1>

</span></font></div>

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font =
size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'> =
Romascanu, Dan
(Dan) [mailto:dromasca@avaya.com] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Tuesday, November =
29, 2005
7:11 AM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> <st1:PersonName =
w:st=3D"on">Matt
 Squire</st1:PersonName>; Lior khermosh<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> David T. Perkins; Hub =
MIB<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> Resolution to =
comments
from David Perkins</span></font><o:p></o:p></p>

</div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<div>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Matt, Lior, a.k.a. Hub-MIB =
Editors</span></font><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>When will you be able to&nbsp;address the comments =
submitted
by David Perkins in his review and propose resolutions? Please do it on =
the WG
list, so that the proposals for resolution is open for =
discussion.</span></font><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Thanks and Regards,</span></font><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Dan</span></font><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

</div>

</div>

</div>

</body>

</html>

------_=_NextPart_001_01C61650.63D0AA58--


--===============1689550718==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib

--===============1689550718==--




From hubmib-bounces@ietf.org Wed Jan 11 02:28:56 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EwaPg-0002rQ-MB; Wed, 11 Jan 2006 02:28:56 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EwaPd-0002rE-7P
	for hubmib@megatron.ietf.org; Wed, 11 Jan 2006 02:28:54 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA20885
	for <hubmib@ietf.org>; Wed, 11 Jan 2006 02:27:27 -0500 (EST)
Received: from [62.90.13.193] (helo=il-mail.actelis.net)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EwaWL-0001SL-0R
	for hubmib@ietf.org; Wed, 11 Jan 2006 02:35:54 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.6556.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [Hubmib] Working Group Last Call
Date: Wed, 11 Jan 2006 09:27:44 +0200
Message-ID: <9C1CAB2B65E62D49A10E49DFCD68EF3E6030A6@il-mail.actelis.net>
Thread-topic: [Hubmib] Working Group Last Call
Thread-Index: AcXeZV+SDV0nkLSJQeWspSjCLFi9OAA6tzBpDcCP7zAAC0kYsA==
From: "Edward Beili" <EdwardB@actelis.com>
To: "Romascanu, Dan \(Dan\)" <dromasca@avaya.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 249cd1efd3d5e0d09114abe826a41235
Cc: "C. M. Heard" <heard@pobox.com>, Hub MIB <hubmib@ietf.org>
X-BeenThere: hubmib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Ethernet Interfaces an Hub MIB WG <hubmib.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/hubmib>,
	<mailto:hubmib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:hubmib@ietf.org>
List-Help: <mailto:hubmib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/hubmib>,
	<mailto:hubmib-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1003834678=="
Sender: hubmib-bounces@ietf.org
Errors-To: hubmib-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1003834678==
content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C61680.83656754"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C61680.83656754
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Dan,
I have a few things to add to the efm-cu-mib, which I'm planning to do =
next week. I'll change the rfc363bis at the same time.

I'll try to do everything by Monday, Jan 23.

Regards,
-Edward


-----Original Message-----
From:	hubmib-bounces@ietf.org on behalf of Romascanu, Dan (Dan)
Sent:	Wed 1/11/2006 4:00 AM
To:	Edward Beili; C. M. Heard; Hub MIB
Cc:=09
Subject:	RE: [Hubmib] Working Group Last Call

Edward,
=20
Please let me know if you will be submitting a revised rfc3636bis draft =
soon.=20
=20
I would like to call for WG Last call with the EFMCu and rfc3636bis =
I-Ds, but I want to make sure that you have done all needed updates =
before.=20
=20
Thanks and Regards,
=20
Dan
=20
=20
=20
=20


  _____ =20

From: hubmib-bounces@ietf.org [mailto:hubmib-bounces@ietf.org] On Behalf =
Of Edward Beili
Sent: Wednesday, November 02, 2005 4:49 AM
To: C. M. Heard; Hub MIB
Subject: RE: [Hubmib] Working Group Last Call



Mike,
Apart from rpMauMediaAvailable, which is similar to ifMauMediaAvailable
there's nothing else that looks like another candidate for the =
IANA-MAU-MIB module.

While looking at ifMauMediaAvailable I realized that I forgot to add two =
new values defined in the 802.3ah, clause 30.5.1.1.4:
1. availableReduced - link normal, reduced bandwidth, applies only to =
2BASE-TL and 10PASS-TS
2. ready - at least one PME available, applies only to 2BASE-TL and =
10PASS-TS

In addition a clarification should be added to 'pmdLinkFault' that all =
PMA/PMDs in the aggregation group must detect a fault.

I will add these to the new revision of the 3636bis I-D.

Regards,
-Edward


-----Original Message-----
From:   C. M. Heard [mailto:heard@pobox.com]
Sent:   Mon 10/31/2005 11:52 PM
To:     Hub MIB
Cc:     Edward Beili
Subject:        Re: [Hubmib] Working Group Last Call
On Mon, 24 Oct 2005, Edward Beili wrote:
> 1. Currently the values for the ifMauTypeListBits are defined in the
>    IANA-MAU-MIB, while the values for the ifMauAutoNegCapabilityBits,
>    ifMauAutoNegCapAdvertisedBits and ifMauAutoNegCapReceivedBits =
objects
>    are defined in MAU-MIB.
>    While none of the newly added MAU types (10GBASE-CX4, 2BASE-TL,
>    10PASS-TS, 100BASE-LX/BX, 1000BASE-LX/BX/PX) supports
>    auto-negotiation, this may change in the future (e.g. I don't see
>    a reason not to support it on P2P (-LX/BX) optical links as well as
>    for some new types). I suggest to put TC for these objects in the
>    IANA-MAU-MIB as well.

On Sun, 30 Oct 2005, C. M. Heard wrote:
> If there is a realistic possibility that future MAU types will
> support auto-negotiation, then it is probably advantageous to
> put the capability list under IANA maintenance so that it (like
> the MAU types) can be expanded quickly upon approval of a new
> 802.3 standard.  The main counter-argument would be that doing
> this would lengthen an already protracted process.  In making a
> decision it might be useful to solicit input from the 802.3 WG
> regarding the likelihood of the introduction of new
> auto-negotiation capabilities.

I just noticed that there is (at least) one more object in the MAU-MIB
that has MAU-type-specific values, and that is the enumerated INTEGER
object ifMauMediaAvailable.  Additional enumerated values for this
object may well be required for future MAU types, so there may be
reason to put its enumerations under IANA maintenance as well.

Edward, are there any more such objects lurking in the MAU-MIB?

Mike









------_=_NextPart_001_01C61680.83656754
Content-Type: text/html;
	charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3DWindows-1252">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.0.6556.0">
<TITLE>RE: [Hubmib] Working Group Last Call</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->

<P><FONT SIZE=3D2>Dan,<BR>
I have a few things to add to the efm-cu-mib, which I'm planning to do =
next week. I'll change the rfc363bis at the same time.<BR>
<BR>
I'll try to do everything by Monday, Jan 23.<BR>
<BR>
Regards,<BR>
-Edward<BR>
<BR>
<BR>
-----Original Message-----<BR>
From:&nbsp;&nbsp; hubmib-bounces@ietf.org on behalf of Romascanu, Dan =
(Dan)<BR>
Sent:&nbsp;&nbsp; Wed 1/11/2006 4:00 AM<BR>
To:&nbsp;&nbsp;&nbsp;&nbsp; Edward Beili; C. M. Heard; Hub MIB<BR>
Cc:&nbsp;&nbsp;&nbsp;&nbsp;<BR>
Subject:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; RE: [Hubmib] Working =
Group Last Call<BR>
<BR>
Edward,<BR>
<BR>
Please let me know if you will be submitting a revised rfc3636bis draft =
soon.<BR>
<BR>
I would like to call for WG Last call with the EFMCu and rfc3636bis =
I-Ds, but I want to make sure that you have done all needed updates =
before.<BR>
<BR>
Thanks and Regards,<BR>
<BR>
Dan<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
&nbsp; _____&nbsp;<BR>
<BR>
From: hubmib-bounces@ietf.org [<A =
HREF=3D"mailto:hubmib-bounces@ietf.org">mailto:hubmib-bounces@ietf.org</A=
>] On Behalf Of Edward Beili<BR>
Sent: Wednesday, November 02, 2005 4:49 AM<BR>
To: C. M. Heard; Hub MIB<BR>
Subject: RE: [Hubmib] Working Group Last Call<BR>
<BR>
<BR>
<BR>
Mike,<BR>
Apart from rpMauMediaAvailable, which is similar to =
ifMauMediaAvailable<BR>
there's nothing else that looks like another candidate for the =
IANA-MAU-MIB module.<BR>
<BR>
While looking at ifMauMediaAvailable I realized that I forgot to add two =
new values defined in the 802.3ah, clause 30.5.1.1.4:<BR>
1. availableReduced - link normal, reduced bandwidth, applies only to =
2BASE-TL and 10PASS-TS<BR>
2. ready - at least one PME available, applies only to 2BASE-TL and =
10PASS-TS<BR>
<BR>
In addition a clarification should be added to 'pmdLinkFault' that all =
PMA/PMDs in the aggregation group must detect a fault.<BR>
<BR>
I will add these to the new revision of the 3636bis I-D.<BR>
<BR>
Regards,<BR>
-Edward<BR>
<BR>
<BR>
-----Original Message-----<BR>
From:&nbsp;&nbsp; C. M. Heard [<A =
HREF=3D"mailto:heard@pobox.com">mailto:heard@pobox.com</A>]<BR>
Sent:&nbsp;&nbsp; Mon 10/31/2005 11:52 PM<BR>
To:&nbsp;&nbsp;&nbsp;&nbsp; Hub MIB<BR>
Cc:&nbsp;&nbsp;&nbsp;&nbsp; Edward Beili<BR>
Subject:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Re: [Hubmib] Working =
Group Last Call<BR>
On Mon, 24 Oct 2005, Edward Beili wrote:<BR>
&gt; 1. Currently the values for the ifMauTypeListBits are defined in =
the<BR>
&gt;&nbsp;&nbsp;&nbsp; IANA-MAU-MIB, while the values for the =
ifMauAutoNegCapabilityBits,<BR>
&gt;&nbsp;&nbsp;&nbsp; ifMauAutoNegCapAdvertisedBits and =
ifMauAutoNegCapReceivedBits objects<BR>
&gt;&nbsp;&nbsp;&nbsp; are defined in MAU-MIB.<BR>
&gt;&nbsp;&nbsp;&nbsp; While none of the newly added MAU types =
(10GBASE-CX4, 2BASE-TL,<BR>
&gt;&nbsp;&nbsp;&nbsp; 10PASS-TS, 100BASE-LX/BX, 1000BASE-LX/BX/PX) =
supports<BR>
&gt;&nbsp;&nbsp;&nbsp; auto-negotiation, this may change in the future =
(e.g. I don't see<BR>
&gt;&nbsp;&nbsp;&nbsp; a reason not to support it on P2P (-LX/BX) =
optical links as well as<BR>
&gt;&nbsp;&nbsp;&nbsp; for some new types). I suggest to put TC for =
these objects in the<BR>
&gt;&nbsp;&nbsp;&nbsp; IANA-MAU-MIB as well.<BR>
<BR>
On Sun, 30 Oct 2005, C. M. Heard wrote:<BR>
&gt; If there is a realistic possibility that future MAU types will<BR>
&gt; support auto-negotiation, then it is probably advantageous to<BR>
&gt; put the capability list under IANA maintenance so that it (like<BR>
&gt; the MAU types) can be expanded quickly upon approval of a new<BR>
&gt; 802.3 standard.&nbsp; The main counter-argument would be that =
doing<BR>
&gt; this would lengthen an already protracted process.&nbsp; In making =
a<BR>
&gt; decision it might be useful to solicit input from the 802.3 WG<BR>
&gt; regarding the likelihood of the introduction of new<BR>
&gt; auto-negotiation capabilities.<BR>
<BR>
I just noticed that there is (at least) one more object in the =
MAU-MIB<BR>
that has MAU-type-specific values, and that is the enumerated =
INTEGER<BR>
object ifMauMediaAvailable.&nbsp; Additional enumerated values for =
this<BR>
object may well be required for future MAU types, so there may be<BR>
reason to put its enumerations under IANA maintenance as well.<BR>
<BR>
Edward, are there any more such objects lurking in the MAU-MIB?<BR>
<BR>
Mike<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C61680.83656754--


--===============1003834678==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib

--===============1003834678==--




From hubmib-bounces@ietf.org Mon Jan 16 09:46:05 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EyVcS-0000ZR-RZ; Mon, 16 Jan 2006 09:46:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EyVcO-0000X2-GN
	for hubmib@megatron.ietf.org; Mon, 16 Jan 2006 09:46:00 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA17543
	for <hubmib@ietf.org>; Mon, 16 Jan 2006 09:44:37 -0500 (EST)
Received: from nj300815-ier2.net.avaya.com ([198.152.12.103])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EyVkJ-0004BW-Vq
	for hubmib@ietf.org; Mon, 16 Jan 2006 09:54:13 -0500
Received: from tiere.net.avaya.com (tiere.net.avaya.com [198.152.12.100])
	by nj300815-ier2.net.avaya.com (Switch-3.1.7/Switch-3.1.7) with ESMTP
	id k0GEhO4v010385
	for <hubmib@ietf.org>; Mon, 16 Jan 2006 09:43:24 -0500
Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com
	[135.64.105.51])
	by tiere.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id
	k0GEgwcS029541
	for <hubmib@ietf.org>; Mon, 16 Jan 2006 09:42:58 -0500 (EST)
content-class: urn:content-classes:message
MIME-Version: 1.0
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
Date: Mon, 16 Jan 2006 16:45:56 +0200
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F09AE3B71@is0004avexu1.global.avaya.com>
Thread-Topic: the file
Thread-Index: AcYaq46hvt6cvkWtRJihd6dxvoux/QAAAAX1
From: "Romascanu, Dan \(Dan\)" <dromasca@avaya.com>
To: "hubmib" <hubmib@ietf.org>
X-Scanner: InterScan AntiVirus for Sendmail
X-Spam-Score: 0.8 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Subject: [Hubmib] Out of Office AutoReply: the file
X-BeenThere: hubmib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Ethernet Interfaces an Hub MIB WG <hubmib.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/hubmib>,
	<mailto:hubmib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:hubmib@ietf.org>
List-Help: <mailto:hubmib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/hubmib>,
	<mailto:hubmib-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1202780819=="
Sender: hubmib-bounces@ietf.org
Errors-To: hubmib-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1202780819==
content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C61AAB.8EB506A4"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C61AAB.8EB506A4
Content-Type: text/plain;
	charset="windows-1255"
Content-Transfer-Encoding: quoted-printable

I am out-of-office, attending standards and company meetings until =
January 22, 2006, and I may read your e-mail only after this date. If =
you need to contact me urgently, please leave a message at my office =
voice mail.

Regards,

Dan


------_=_NextPart_001_01C61AAB.8EB506A4
Content-Type: text/html;
	charset="windows-1255"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dwindows-1255">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.0.6617.47">
<TITLE>Out of Office AutoReply: the file</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->

<P><FONT SIZE=3D2>I am out-of-office, attending standards and company =
meetings until January 22, 2006, and I may read your e-mail only after =
this date. If you need to contact me urgently, please leave a message at =
my office voice mail.<BR>
<BR>
Regards,<BR>
<BR>
Dan<BR>
</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C61AAB.8EB506A4--


--===============1202780819==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib

--===============1202780819==--




From hubmib-bounces@ietf.org Tue Jan 17 01:26:18 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EykIM-0006yx-DQ; Tue, 17 Jan 2006 01:26:18 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EykIK-0006yO-CZ
	for hubmib@megatron.ietf.org; Tue, 17 Jan 2006 01:26:16 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA19930
	for <hubmib@ietf.org>; Tue, 17 Jan 2006 01:24:51 -0500 (EST)
Received: from co300216-ier2.net.avaya.com ([198.152.13.103])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EykQO-0000KQ-Ra
	for hubmib@ietf.org; Tue, 17 Jan 2006 01:34:37 -0500
Received: from tierw.net.avaya.com (h198-152-13-100.avaya.com [198.152.13.100])
	by co300216-ier2.net.avaya.com (Switch-3.1.7/Switch-3.1.7) with ESMTP
	id k0H5O4dY007666
	for <hubmib@ietf.org>; Tue, 17 Jan 2006 00:24:04 -0500
Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com
	[135.64.105.51])
	by tierw.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id
	k0H6B2Pk016079
	for <hubmib@ietf.org>; Tue, 17 Jan 2006 01:11:03 -0500 (EST)
content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 17 Jan 2006 08:26:08 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F09E0EF8E@is0004avexu1.global.avaya.com>
Thread-Topic: meeting at the 65th IETF?
Thread-Index: AcYbLudaS8t+j476RSG5iHX5e+8fqQ==
From: "Romascanu, Dan \(Dan\)" <dromasca@avaya.com>
To: "Hub MIB" <hubmib@ietf.org>
X-Scanner: InterScan AntiVirus for Sendmail
X-Spam-Score: 0.5 (/)
X-Scan-Signature: a2c12dacc0736f14d6b540e805505a86
Subject: [Hubmib] meeting at the 65th IETF?
X-BeenThere: hubmib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Ethernet Interfaces an Hub MIB WG <hubmib.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/hubmib>,
	<mailto:hubmib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:hubmib@ietf.org>
List-Help: <mailto:hubmib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/hubmib>,
	<mailto:hubmib-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0440350426=="
Sender: hubmib-bounces@ietf.org
Errors-To: hubmib-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0440350426==
content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C61B2E.E7419E78"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C61B2E.E7419E78
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

=20

We are in the final rounds of editing before completing the current
charter. The EFM OAM MIB and EFM EPON MIB were reviewed by David
Perkins, the authors submitted proposals for comments resolution, and we
are still waiting for David's response. Unless we hear from David until
the end of this week, we should consider that he is happy with the
comments resolutions and we will proceed to what should be the I-Ds to
be submitted to the IESG for IETF Last Call. We are also looking forward
for the EFM Cu and MAU MIB revisions I-Ds to be posted and run the WGLC.


I do not believe that we need a meeting in Dallas. However, if you think
there is a need for a session of the hubmib WG at the 65th IETF meeting,
please post your agenda proposals to this mailing list so we can
determine whether there is sufficient need and support for a
face-to-face meeting. The cut-off date for session requests is February
13, so please make any such proposals before February 10, 2006.

Regards,

=20

Dan

=20

=20
=20
=20

------_=_NextPart_001_01C61B2E.E7419E78
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.2800.1528" name=3DGENERATOR></HEAD>
<BODY>
<DIV>
<P><FONT face=3DArial size=3D2></FONT>&nbsp;</P>
<P><FONT face=3DArial><FONT size=3D2><SPAN class=3D166511706-17012006>We =
are in the=20
final rounds of editing before completing the current charter. The EFM =
OAM MIB=20
and EFM EPON MIB were reviewed by David Perkins, the authors submitted =
proposals=20
for comments resolution, and we are still waiting for David's response. =
Unless=20
we hear from David until the end of this week, we should consider that =
he is=20
happy with the comments resolutions and we will proceed to what should =
be the=20
I-Ds to be submitted to the IESG for IETF Last Call. We are also looking =
forward=20
for the EFM Cu and MAU MIB revisions I-Ds to be posted and run the WGLC. =

</SPAN></FONT></FONT></P>
<P><FONT><FONT face=3DArial><FONT size=3D2><SPAN =
class=3D166511706-17012006>I do not=20
believe that we need a meeting in Dallas. However, i</SPAN>f you think =
there is=20
a need for a session of the&nbsp;<SPAN =
class=3D166511706-17012006>hubmib</SPAN> WG=20
at the 65th IETF meeting, please post your agenda proposals to this =
mailing list=20
so we can determine whether there is sufficient need and support for a=20
face-to-face meeting. The cut-off date for session requests is February =
13, so=20
please make any such proposals before February 10,=20
2006.</FONT></FONT></FONT></P>
<P><FONT face=3DArial size=3D2><SPAN=20
class=3D166511706-17012006>Regards,</SPAN></FONT></P>
<P><FONT face=3DArial size=3D2><SPAN=20
class=3D166511706-17012006></SPAN></FONT>&nbsp;</P>
<P><FONT face=3DArial size=3D2><SPAN =
class=3D166511706-17012006>Dan</SPAN></FONT></P>
<P><FONT face=3DArial size=3D2><SPAN=20
class=3D166511706-17012006></SPAN></FONT>&nbsp;</P></DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV></BODY></HTML>

------_=_NextPart_001_01C61B2E.E7419E78--


--===============0440350426==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib

--===============0440350426==--




From hubmib-bounces@ietf.org Fri Jan 20 06:21:16 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EzuKS-0003Ls-Sj; Fri, 20 Jan 2006 06:21:16 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EzuKR-0003Ky-I4
	for hubmib@megatron.ietf.org; Fri, 20 Jan 2006 06:21:16 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA01982
	for <hubmib@ietf.org>; Fri, 20 Jan 2006 06:19:47 -0500 (EST)
Received: from smtpout1.bayarea.net ([209.128.95.10])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EzuTA-00083v-2U
	for hubmib@ietf.org; Fri, 20 Jan 2006 06:30:16 -0500
Received: from shell4.bayarea.net (shell4.bayarea.net [209.128.82.1])
	by smtpout1.bayarea.net (8.12.10/8.12.10) with ESMTP id k0K7b5eO007728; 
	Thu, 19 Jan 2006 23:45:00 -0800
Received: from shell4.bayarea.net (localhost [127.0.0.1])
	by shell4.bayarea.net (8.12.11/8.12.11) with ESMTP id k0K716uL027930;
	Thu, 19 Jan 2006 23:01:06 -0800
Received: from localhost (dperkins@localhost)
	by shell4.bayarea.net (8.12.11/8.12.11/Submit) with ESMTP id
	k0K715tC027922; Thu, 19 Jan 2006 23:01:05 -0800
X-Authentication-Warning: shell4.bayarea.net: dperkins owned process doing -bs
Date: Thu, 19 Jan 2006 23:01:05 -0800 (PST)
From: "David T. Perkins" <dperkins@dsperkins.com>
X-Sender: dperkins@shell4.bayarea.net
To: lior.khermosh@passave.com
Message-ID: <Pine.LNX.4.10.10601192255590.24809-100000@shell4.bayarea.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ee80a2074afbfe28d15369f4e74e579d
Cc: dromasca@avaya.com, Hub MIB <hubmib@ietf.org>
Subject: [Hubmib] Response to EPON-MIB-04
X-BeenThere: hubmib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Ethernet Interfaces an Hub MIB WG <hubmib.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/hubmib>,
	<mailto:hubmib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:hubmib@ietf.org>
List-Help: <mailto:hubmib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/hubmib>,
	<mailto:hubmib-request@ietf.org?subject=subscribe>
Sender: hubmib-bounces@ietf.org
Errors-To: hubmib-bounces@ietf.org

HI,

Comments on draft-ietf-hubmib-efm-epon-mib-04.txt - dtp:19-jan-2006

The document is much improved. However, it is not yet ready for
submission to the IESG. The changes introduced many grammar and
some spelling errors (and a couple of formatting problems), which
can be easily fixed. Unfortunately, there are a couple of
fundamental issues that remain. These are:
 1) if an "SNMP MIB walk" was done on the
     a) IF table
     b) bridge table
     c) MAU table
     d) stack table (and inverted stack table)
     e) etherLike interfaces table
     d) and tables defined in the MIB module
   what would be the answers to the following questions for
   OLTs and for ONUs (for both, assume that each has a 1Gig Eth
   interface and an optical interface, and for the OLT, there
   are 3 ONUs connected to the optical interface):
     a) how many entries would be in the IF table
     b) what would the values be for each column in the
         IF table. That is, what are the values of the
         following objects: ifIndex, ifDescr, ifType,
          ifMtu, ifSpeed, ifPhysAddress, ifAdminStatus,
          ifOperStatus, ifLastChange, ifInOctets, ifInUcastPkts,
          ifInNUcastPkts, ifInDiscards, ifInErrors, 
          ifInUnknownProtos, ifOutOctets, ifOutUcastPkts,
          ifOutNUcastPkts, ifOutDiscards, ifOutErrors,
          ifOutQLen
     c) how the values of the above objects determined?
     d) what happens when the value of ifAdmin is set to
         'up(1)', 'down(2)', and 'testing(3)'?
     e) the table dot1dBasePortTable has the mapping of
        bridge ports to interfaces (and "circuit" on that
        interface). What would the values be for the
        objects dot1dBasePortIfIndex and dot1dBasePortCircuit
        when the OLT supported bridging? (By the way,
        document "Definitions of Managed Objects for Bridges"
        was recently updated and, thus, the refs should
        have RFC 4188 and not 1493.)
     f) how many entries would be in table ifMauTable,
        and would be the value of columns in the table.
     g) Are the stack and inverted stack tables used?
        If so, show the stacking relationships.
     h) How many entries are in the etherLike tables
        dot3StatsTable, dot3CollTable, dot3PauseTable,
        and dot3HCStatsTable and what would the values
        be of columns in the tables.
     i) How many entries would be in the tables defined
        in this document, which are:
        dot3MpcpGlobalTable, dot3MpcpParamTable,
        dot3MpcpStatTable, dot3OmpEmulationTable,
        dot3OmpEmulationStatTable, dot3EponFecTable,
        dot3ExtPkgGlobalControlTable,
        dot3ExtPkgControlTable, dot3ExtPkgQueueTable,
        dot3ExtPkgQueueSetsTable and
        dot3ExtPkgOptIfTable.
 2) Which tables in the MIB module allow rows to be created
    and or deleted, and if so, then how? (Note the the phrase
    "Rows at the table are created by direct SNMP management
    setting." is used in the DESCRIPTION for many tables.
    However, there was no information provided as to what
    this means. (I'm guessing that my original comments
    were not completely understood. What I was asking for
    was to include in the DESCRIPTION clause whether or
    not an SNMP SET could be done to columns in a table
    to create or delete a row, and if so, to provide the
    details (or indicate the object definition where the
    details were provided). For example, the TCP connection
    table does not support SNMP SETs to create rows in
    the table. Rows are created as TCP connections
    are created by processes running on the system.
    However, an SNMP SET can be done on object tcpConnState 
    with value 'deleteTCB(12)' to terminate a TCP
    connection (which results in the row being deleted
    from the table). There are plenty of examples of
    using a "RowStatus" object to create and delete
    rows in tables (see the SNMPv3 RFCs, such as RFC 3413).
    In the RMON MIB modules, there are examples of
    control tables and data tables. A row creation
    (or deletion) in a control table results in
    row creation (or row deletion) in data tables.
    Describing how instances are created and deleted,
    (by system operation or configuration, and/or
    via management operations) is a key piece of
    information for the DESCRIPTION clauses of
    tables and rows.

Until the above fundamental issues are resolved,
it doesn't make a lot of sense to spend much time
on other issues such as grouping and conformance.

Note that I did spot a bunch of easy to fix items
that I'm listing below:
 section 1 - the text for the abstract is Ok. I just don't
     get the term "registers" here.
 section 1.1 - It's great to have a list of abbreviations.
     a) However in documents that contain MIB modules, typically
     the modules are extracted, and thus all the explanatory
     is not available. To help, there is a little redundancy
     that is added to the document of putting KEY definitions
     and terms in the DESCRIPTION clause for the MIB module.
     b) I didn't check to see if all the abbreviations were
     actually used. If not, then I would remove them.
     c) I thought CPE was customer premises equipment
 section 1.2.3 - I was confused. Does "Gate messages"
     start a new subsection?
 section 3 (3.1-3.4) - This is still a little skimpy!
     Look at RFC 2863, sections 3.1.1-3.1.18 & 4. Also
     look at RFC 3635, section 3.2 and contained subsections.
 section 4 - tables 1 thru 3. The column head should be
     IEEE802.3ah attribute and not "object"
 In the MIB module, there are several ASN.1 comments that
     that are used to group the definitions. They start
     out with phrase "Editor's note:". I believe the
     grouping is useful, but I'd drop the "Editor's note:"
     phrase. Note the first one is slightly out of order.
     It should be moved to immediately before the
     definition of OID dot3EponMpcpObjects.
 Object dot3MpcpID - the DESCRIPTION needs to be translated
     from GDMO speak to something meaningful in SMIv2.
     (I commented on this before, and still don't see the
     usefulness of the object!)
 Do the objects dot3MpcpOperStatus and dot3MpcpAdminStatus
     ever have different values. If not, then you should
     have one object.
 I really don't follow whether or not you can create LLIDs
     via SNMP. It doesn't seem possible to me, just like
     you can't create TCP connections. Thus, I don't understand
     the object dot3LinkIndex. (And note: a table that
     allows row creation uses "read-create" (and not "read-write")
     for all writable objects in the table.)
 Entries in parallel tables - I asked you to describe the
     expected number of entries in tables. However, many of
     the tables in the MIB module are related, and the text
     was just copied. Instead, if there is a "base table"
     that determines the number of entries, and additional
     tables that have additional info, you should say
     something like "The rows in this table are match the
     rows in table X".
 Transient condition in table dot3MpcpParamTable - it appears
     that this table tries to capture the transient values
     during the time a OLT and ONU are setting up a relationship
     and determining an LLID. Is this a long enough running
     activity that it can be seen, and what LLID value is
     used durring negotiation (can't it change)?
 Object dot3OmpEmulationID - the DESCRIPTION needs to be translated
     from GDMO speak to something meaningful in SMIv2.
     (I commented on this before, and still don't see the
     usefulness of the object!)
 Enum names in DESCRIPTION for object dot3ExtPkgObjectPowerDown -
     The enum names start with lower-case letters and not
     upper-case.
 Queues - I really don't understand the queues. Could some
     intro text be added.
 Indexing - this is somewhat subjective. I don't believe that
     it is proper to define an object in one table (which is not
     an index in that table) and use it for an index in another
     table. This is done in the queue tables and object dot3LinkIndex.


NOTE: this review was not complete. I didn't try to compile the
MIB module or run the document through the nit checker. Also,
I didn't look at the compliances.

-- that's it

Regards,
/david t. perkins  



_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib



From hubmib-bounces@ietf.org Fri Jan 20 12:44:23 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F00JD-0000tb-JL; Fri, 20 Jan 2006 12:44:23 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1F00JC-0000t7-Fr
	for hubmib@megatron.ietf.org; Fri, 20 Jan 2006 12:44:23 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA04408
	for <hubmib@ietf.org>; Fri, 20 Jan 2006 12:42:54 -0500 (EST)
Received: from smtpout1.bayarea.net ([209.128.95.10])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F00Rx-0004tP-Tn
	for hubmib@ietf.org; Fri, 20 Jan 2006 12:53:27 -0500
Received: from shell4.bayarea.net (shell4.bayarea.net [209.128.82.1])
	by smtpout1.bayarea.net (8.12.10/8.12.10) with ESMTP id k0KHiIcU023471; 
	Fri, 20 Jan 2006 09:44:18 -0800
Received: from shell4.bayarea.net (localhost [127.0.0.1])
	by shell4.bayarea.net (8.12.11/8.12.11) with ESMTP id k0KHgeAQ018978;
	Fri, 20 Jan 2006 09:42:40 -0800
Received: from localhost (dperkins@localhost)
	by shell4.bayarea.net (8.12.11/8.12.11/Submit) with ESMTP id
	k0KHgeTG018974; Fri, 20 Jan 2006 09:42:40 -0800
X-Authentication-Warning: shell4.bayarea.net: dperkins owned process doing -bs
Date: Fri, 20 Jan 2006 09:42:39 -0800 (PST)
From: "David T. Perkins" <dperkins@dsperkins.com>
X-Sender: dperkins@shell4.bayarea.net
To: lior.khermosh@passave.com
Subject: Re: [Hubmib] Response to EPON-MIB-04
In-Reply-To: <Pine.LNX.4.10.10601192255590.24809-100000@shell4.bayarea.net>
Message-ID: <Pine.LNX.4.10.10601200941150.18476-100000@shell4.bayarea.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7bac9cb154eb5790ae3b2913587a40de
Cc: dromasca@avaya.com, Hub MIB <hubmib@ietf.org>
X-BeenThere: hubmib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Ethernet Interfaces an Hub MIB WG <hubmib.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/hubmib>,
	<mailto:hubmib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:hubmib@ietf.org>
List-Help: <mailto:hubmib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/hubmib>,
	<mailto:hubmib-request@ietf.org?subject=subscribe>
Sender: hubmib-bounces@ietf.org
Errors-To: hubmib-bounces@ietf.org

HI,

Just saw one more small item. The MIB module is named
"DOT3-EFM-EPON-MIB". I suggest that the name "DOT3-EPON-MIB"
be used instead.

Regards,
/david t. perkins



_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib



From hubmib-bounces@ietf.org Sun Jan 22 01:05:12 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F0YLg-0003Rj-MT; Sun, 22 Jan 2006 01:05:12 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1F06e8-00031F-9v
	for hubmib@megatron.ietf.org; Fri, 20 Jan 2006 19:30:24 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA15525
	for <hubmib@ietf.org>; Fri, 20 Jan 2006 19:28:55 -0500 (EST)
Received: from smtpout1.bayarea.net ([209.128.95.10])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F06mv-0005Bl-IF
	for hubmib@ietf.org; Fri, 20 Jan 2006 19:39:32 -0500
Received: from shell4.bayarea.net (shell4.bayarea.net [209.128.82.1])
	by smtpout1.bayarea.net (8.12.10/8.12.10) with ESMTP id k0L0UAcU028631; 
	Fri, 20 Jan 2006 16:30:10 -0800
Received: from shell4.bayarea.net (localhost [127.0.0.1])
	by shell4.bayarea.net (8.12.11/8.12.11) with ESMTP id k0L0SWGx032644;
	Fri, 20 Jan 2006 16:28:32 -0800
Received: from localhost (dperkins@localhost)
	by shell4.bayarea.net (8.12.11/8.12.11/Submit) with ESMTP id
	k0L0SQVh032621; Fri, 20 Jan 2006 16:28:26 -0800
X-Authentication-Warning: shell4.bayarea.net: dperkins owned process doing -bs
Date: Fri, 20 Jan 2006 16:28:26 -0800 (PST)
From: "David T. Perkins" <dperkins@dsperkins.com>
X-Sender: dperkins@shell4.bayarea.net
To: hubmib@ietf.org
Message-ID: <Pine.LNX.4.10.10601201623170.29711-100000@shell4.bayarea.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 44c13fcb5ac8234f1196c1913fbec387
X-Mailman-Approved-At: Sun, 22 Jan 2006 01:05:11 -0500
Cc: dromasca@avaya.com, MSquire@HatterasNetworks.com
Subject: [Hubmib] Response to comments on OAM doc
X-BeenThere: hubmib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Ethernet Interfaces an Hub MIB WG <hubmib.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/hubmib>,
	<mailto:hubmib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:hubmib@ietf.org>
List-Help: <mailto:hubmib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/hubmib>,
	<mailto:hubmib-request@ietf.org?subject=subscribe>
Sender: hubmib-bounces@ietf.org
Errors-To: hubmib-bounces@ietf.org

HI,

It looks like much progress, and maybe with the comments
below incorroprated, the document will be ready for
a new WG last call and IESG submission.

------------------------------------------------------------

Response to OAM comments (email from Matt Squire on 10-jan-2006) -
dtp:20-jan-2006 
-------------------------------------------------------------
Responses are prefixed by %%. For example:
%% This is an example
-------------------------------------------------------------
Hi David, Dan  - 

Below are my responses to the various comments.  Many of the editorial
problems (spelling error, etc.) won't be listed here as they don't
really require discussion.  I separated out what I consider the biggest
issues and talk about them first, then include responses to your
individual comments in the parts that follow.  

- Matt
========================

Bigger issues:

a) "dot3" vs "efm".  There were multiple comments related to whether
various names in the MIB should be "efm..." or "dot3...".  Admittedly,
the reviewed version of the MIB had a mix of the two as it historically
went from "EFM OAM" to "EFM Common" to "OAM" to whatever.  To be clear,
the OAM functionality of 802.3 is applicable to any Ethernet interface,
not just those defined in 802.3ah, so it applies to 1000BASE-X,
10/100BASE-T, etc.  For that reason, I'd suggest we move everything to a
"dot3..." prefix rather than an "efm..." prefix, and to use "Ethernet
OAM" as a description rather than "EFM OAM" (which appears in a few
places).  

%% Yes, I suggest the following:
%%  DOT3-OAM-MIB for the module name, and
%%  dot3OamMIB for the descriptor of the MODULE-IDENTITY definition
%% I believe that the prefix of the descriptors used throughout
%% the -03 document are "dot3Oam", so no change needed for them. 

b) Improving description clauses.  You commented that all description
clauses for tables need to contain XYZ, similarly for rows.  I've
attempted to improve the description clauses based on your feedback.   


c) Removing frame reception conditions in MIB descriptions.  You had
multiple comments related to certain sections of the MIB (the OAM peer
objects) where the descriptions included detailed information on what
the values of various frame fields had to be in order to process the
frame.  As an example, the MIB had:

         An OAMPDU is indicated by a valid frame with (1) destination

         MAC address equal to that of the reserved MAC address for Slow

         Protocols (See 43B of [802.3ah]), (2) a lengthOrType field

         equal to the reserved type for Slow Protocols, (3) and a Slow

         Protocols subtype equal to that of the subtype reserved for

         OAM.  

You basically indicated that such details weren't needed in those
sections.  I'm more than fine with removing it.  It was added several
revisions ago when someone asked for more details about "when exactly
does this value get updated?"  At that point I added descriptions like
the above to spell out as much as possible what has to be received for
this field to be updated.  I'd personally love to remove it, as it's
just a bunch of extra words to me, but more than that I don't want to
add it back again later. 

%% The question is whether the text is useful or distracting, or
%% even confusing.
%% I suggest that OAM PDU be defined in the explanatory text
%% (the text before the MIB module) with a reference to the
%% section in the appropriate IEEE document. And also duplicate
%% that definition an put it in the DESCRIPTION clause of
%% the MODULE-IDENTITY. Then, just say "OAM PDU" without
%% defining what is an OAM PDU.

d) You found a couple of problems with my RTF-RFC conversion process.
In what was Section 4.3, there was a mapping of SNMP to 802.3
attributes, and you rightfully pointed out there should be a section
header and introduction sentence or two.  At some point when going from
the word RTF file to the text RFC, those were deleted.  In the next rev,
there will be a Section 4.4 just for the SNMP/802.3 attribute mappings.

e) You pointed out some inconsistencies (and potential improvements) on
explaining when entries are created/deleted from various tables.  My
suggestion going forward is to detail when entries are created in the
primary control table (dot3OamTable), indicating they are automatically
created for every Ethernet interface that supports OAM.  And then say
that other tables have entries automatically created for every entry in
that primary table.  The way things were written, 

%% Here is a summary of my suggestion:
%% Table dot3OamTable - entries are in this table if OAM is
%%     supported on this dot3 interface. These entries
%%     are not added or deleted via SNMP operations, but
%%     and present if the OAM function is supported.
%%  (NOTE: on rereading the DESCRIPTION of object dot3OamConfigRevision,
%%         I was confused. Shouldn't the description simply be
%%           "The local value of the OAM configuration revision."
%%         I don't understand the reference to local_statisfied
%%         in 802.3ah 57.3.1.2. Also, can there be different
%%         versions on different interfaces? And given that
%%         the GMDO attribute is aOAMLocalRevision, why not
%%         call this dot3OamLocalConfigRevision?)
%% Table dot3OamPeerTable - presently, an entry is in this table
%%         for each entry in table dot3OamTable, and object
%%         dot3OamPeerStatus indicates if the values of other
%%         columns in the table are "valid". The point that I
%%         was making was to either a) remove object dot3OamPeerStatus
%%         and only put rows in the table that have "valid values",
%%         or b) define values that should be returned when
%%         the value of object dot3OamPeerStatus is 'inactive(2)'.
%% Table dot3OamLoopbackTable - an entry exists in this table
%%         for each entry in table dot3OamTable where object
%%         dot3OamFunctionsSupported has bit 'loopbackSupported(1)'
%%         with value 1. 
%%         NOTE: what happens if a loopback is started, and then
%%         the value of dot3OamOperStatus changes to some value
%%         from 'operational(9)', and then cycles back to 
%%         'operational(9)'. Is the loopback lost?
%% Table dot3OamStatsTable - an entry exists in this table
%%         for each entry in table dot3OamTable. The counts
%%         are not "reset" due to changes in dot3OamOperStatus.
%% Table dot3EventConfigTable -  an entry exists in this table
%%         for each entry in table dot3OamTable where object
%%         dot3OamFunctionsSupported has bit ??
%%         with value 1. The values are not affected by 
%%         changes in dot3OamOperStatus or dot3OamAdminStatus.
%% Table dot3OamEventLogTable - an entry exists in this table
%%         for each event that has occurred up to the max
%%         supported by the implementation. When the implementation
%%         max is present, the addition of a new event result in
%%         the deletion of one or more of the oldest events. The
%%         value of the index object dot3OamEvetLogIndex increase
%%         in value for each new entry, and when the max is reached
%%         then the value restarts at zero. 

 - dot3OamPeerTable didn't always have an entry - it was written so that
you could add an entry once you learned the peer, then leave it in
there, but an entry wasn't required even if you were running OAM.  I
suggest changing that so that an entry is always required, and the
various objects have mechanisms to indicate whether their values validly
reflect an actual OAM peer, or whether there is no peer.  This reflects
several of your comments.


 - dot3OamLoopbackTable didn't require an entry if the implementation
didn't support loopback (there was a condition "if loopback is
supported" in the description).  Likewise, the dot3EventConfigTable
didn't always require an entry (it's an optional function as well).
Given the optional nature of certain functions (loopback, events, etc),
I wasn't sure whether the tables should always have an entry (with some
kind of 'not supported' indicator), or whether the tables should only
have entries if the function is supported, or if there was some other
approach.  I'm open to suggestions.  


f) In the dot3OamAdminState, I had a description that included: 

         Note that the value of this object is ignored when the
         interface is not operating in full-duplex mode. OAM is not
         supported on half-duplex links.  

]] I'm not sure what "ignored" means here.
]] I don't believe that "ignored" is the right term.
]] Shouldn't whether the interface is in half or full-duplex
]] show up in the value of object dot3OamOperStatus?
]] I'm assuming that only interfaces that can operate
]] in full-duplex mode will be in this table. That
]] should of been said in the table DESCRIPTION clause.

This is a little trickier than I originally thought.  OAM was intended
for full-duplex links, and some of the functions don't operate on
half-duplex links.  So I was trying to say that OAM shouldn't run on
half-duplex links, so setting the admin state doesn't matter (hence the
ignored).  I'm open to finding better ways of saying that.  Looking back
at 802.3ah, I was unable to find the sections that indicate OAM doesn't
come up on half-duplex links.  So I believe what happens is that OAM
would come up but some things might not work (anybody have a different
interpretation)?  If that's the case (as I think now), then I will
probably have to rewrite that description to capture the proper
behavior.  I'm not sure that reflecting the duplex of the interface in
the dot3OamStatus is either good or necessary.  The OAM tables should
exist whether the interface is full/half/auto, so the potential to be in
full-duplex may be required, but you don't have to be in full-duplex
mode to have an entry in the OAM table (your duplex may be auto, TBD
later).  

%% (I'm going to ignore the potential "degraded operation" while
%% in half-duplex.)
%% I just don't like the sentence "Note that the value is
%% ignored..."
%% Let's back up. I believe that an implementation will choose
%% which dot3 interfaces that it will support the OAM function.
%% A management app will be able to read the instances in table
%% dot3OamTable to determine this. Some dot3 interfaces will
%% support negotiation, and if the peer negotiates half-duplex,
%% then the OAM function will not operate. Likewise, if there
%% is no peer attached or the peer's interface is down the
%% OAM function will not operate. Likewise, if the peer doesn't
%% support the OAM function (it may not have code, or it may
%% be administratively disabled), the OAM function will not
%% operate.
%% Thus, I'm suggesting that you remove the sentence, and
%% add a new value for dot3OperStatus, such as
%% 'nonOperInHalfDuplex()', which would be returned
%% if dot3OamAdminState is 'enabled(2)', and the link is
%% in half duplex mode.
%% Also, dot3OperStatus needs a value when ifAdminStatus
%% is 'down(2)' or 'testing(3)', and when ifOperStatus
%% has a value other than 'up(1)'.

g) In the loobpack object, right now there is a separate status and
action attribute, so that you can set the action to start/stop loopback,
then go read the status.  You suggested a combined status/action object.
First, I don't know what that means.  Can you point me to an example in
some other document?  Second, the current separation of action/status
was a result of discussions on either the list or at a meeting.  All of
the examples that I was able to find or were given to me for similar
function had one attribute to initiate the action and another to return
the result.   
%% Having one object or two is somewhat subjective. There are
%% plenty of examples of action/status objects. For example,
%% all RowStatus objects are action/status objects. Here are
%% the enum values from RFC 2579:
%%    -- the following two values are states:
%%    -- these values may be read or written
%%    active(1),
%%    notInService(2),
%%
%%    -- the following value is a state:
%%    -- this value may be read, but not written
%%    notReady(3),
%%
%%    -- the following three values are
%%    -- actions: these values may be written,
%%    --   but are never read
%%    createAndGo(4),
%%    createAndWait(5),
%%    destroy(6)

h) You suggested combining dot3OamErrSymPeriodWindowHi and
dot3OamErrSymPeriodWindowLo into one CounterBasedGauge64.  This was
discussed on the list previously and it was decided that was not
possible.  The discussion centered on CounterBasedGauge64s as being
read-only counters.  In this case, we need settable parameters as we're
trying to setup a threshold.  So I was told CounterBasedGauge64s were
not applicable in that scenario, and that we needed to have two separate
attributes with rules to combine them.  

%% I'm checking into options.
 

i) On the dot3EventLogTable, you had questions about the maximum size
and handling:

]] On this table, can it have an infinite number of entries?
]] Most likely not. In other tables, there is some indication
]] that says the max number (not always available), but
]] always something that says to either stop adding entries,
]] or delete the oldest, or some other algorithm to replace
]] the least important with a new one.

I suggest saying the size of the table is implementation dependent, and
that older entries are automatically replaced with newer entries when
the table gets full.  Is that satisfactory?  

%% See above.

j)  In the event log table, you asked what were the running totals and
event totals. After reading 802.3ah, you indicated you know what they
mean, but a re-write of the description is in order.  Here's my proposed
DESCRIPTION:

       "Each Event Notification TLV contains a running total of the
       number of times an event has occurred, as well as the number of
       times an Event Notification for the event has been transmitted.

       For non-threshold crossing events, the number of events
       (dot3OamLogRunningTotal) and the number of resultant Event
       Notifications (dot3OamLogEventTotal) should be identical. 

       For threshold crossing events, since multiple occurrences may
       be required to cross the threshold, these values are likely
       different.  This value represents the total number of times one
       or more of these occurrences have resulted in an Event
       Notification (for example, 51 when 3253 symbol errors have
       occurred since the last reset, which has resulted in 51 symbol
       error threshold crossing events since the last reset).  
       "

k) You made suggestions on rearranging the hierarchy so that there is a
dot3OamNotifications off dot3OamMIB, and having the notifications
reference that.  I'm fine with changing the tree that way so
Notifications are moved up in the tree.  

l) In the reviewed versions, the compliance section has some
unconditionally optional groups, allowing for a mix and match set of
implementations.  You suggested defining a minimum and maximum
compliance group.  I don't have a suggestion here yet.  I need to think
about it more, but would be interested in hearing opinions from anyone
else.  

 =================================

In the text below, I basically include the version of the draft with
your comments in it as was sent to the mailing list.  From that text, I
removed certain sections that didn't have any comments, or had only what
I considered uncontroversial editorial comments.  Where text was
removed, << Text deleted >> appears.  Your comments are still prefixed
with ]], while I put "MBS:" in front of my response.  

]] Reviewed 8-sept-2005, david t. perkins, dperkins@snmpinfo.com
]]
]] Global comments:

]]  Comments are inserted in-line and each comment line
]]  is preceded by "]]".
]]

]]1) A line of "-"s is used as a separator. This is problematic
]]   and if a separator is desired, the it should be something
]]   like -- **************************************************
]]   (If the number of "-"s in a line is X, and mod(X,4)==1,
]]   then a MIB compiler will report a parse error.)

MBS:  No problem doing the change.  

]]2) All the tables should have consistent info in the
]]   DESCRIPTION clauses for the table and row definitions.
]]   Minimally, the tables DESCRIPTION clause should describe
]]   the table, and specify what determines the number of
]]   entries in the table.
]]   Minimally, the DESCRIPTION clause for rows should indicate
]]   how rows are added and removed from tables. And if can
]]   be done via direct SNMP operations, then the identification
]]   of the RowStatus object.
]]   Note that there is additional information that must be
]]   contained in the DESCRIPTION clause as specified in
]]   "Guidelines ... of MIB Documents"
]]   <draft-ietf-ops-mib-review-guidelines-04.txt>
]]   [MIBguidelines]

%% The I-D is now RFC 4181
 

MBS: I've attempted to update the objects as appropriate.  They'll
need to be reviewed to ensure they meet the goals.  

]]3) For enumerated values, each value be described in the
]]   DESCRIPTION text of the object or TC definition.

MBS: I found a couple instances where not every enumerated value was
spelled out, and tried to correct that (you have specific comments to
these at the various instances of the omission).  


]]5) The term "byte" should be replaced by term "octet".

MBS: Changed.  

]]6) The abbreviations "i.e.", and "e.g." are confused.
]]   I suggest that you always write out "that is",
]]   and "for example".

MBS: I replaced the few occurences of "e.g." with "for example".
Personally, I don't believe that it improves (or hurts) anything, but
I'm more than willing to do it.  The abbreviation "i.e." wasn't used
in the document (that I could find).  


]]7) A few typos were found by idnits script found at
]]   http://ietf.levkowetz.com/tools/idnits/

MBS: I'll be sure to run the script on next revision before
submission.  


  Ethernet Interfaces and Hub MIB WG                              
  Internet Draft                                    Matt Squire

  Document: draft-ietf-hubmib-efm-mib-03.txt        Hatteras Networks
  Expires: September 2005                           March, 2005

              Ethernet in the First Mile (EFM) OAM MIB
 << Text deleted >>
%% I hope that you are changing this to the following:
%%   Definitions of Managed Objects for OAM Functions for
%%   Ethernet-Like Interfaces 
  

3.   Overview
  Ethernet networks have evolved over the past 30 years from simple
  LANs to a variety of other applications, including wide area
  networks.  To address some of these emerging markets, the IEEE
  802.3ah task force defined additional clauses for the IEEE 802.3
  standard [802.3-2002] to better address Ethernet deployments in the
  public access network.  

]] To make it clear, I'd change the above to the following:
]]   To address some of these emerging markets, the IEEE
]]   802.3ah task force defined additional clauses in [802.3ah]
]]   for the IEEE 802.3 standard [802.3-2002] to better address
]]   Ethernet deployments in the public access network.

MBS: Changed made.  

]] Is 802.3ah work strictly for "public access networks"?
]] If not, then the phrase should be dropped or replaced.
 

MBS: Access networks were the motivation for the task force, but the
results can be applied for any application.  So the phrase does
address why the work was initiated and completed, but does not fully
address applicability.  Instead of the suggestion, I added a sentence;
"Although Ethernet access deployments were the primary motivation for
the task force work, the results of the task force are not limited to
that application.  "

<< Text deleted >>
 
4.1    Relation to other SNMP MIB Modules
  This objects defined in this document do not overlap with MIB-2
  [RFC1213], the interfaces MIB [RFC2863], or the Ethernet like
  interfaces MIB [RFC3635].  The objects defined here are defined for
  Ethernet like interfaces only and use the same ifIndex as the
  associated Ethernet interface.  Ethernet OAM can be implemented on
  any Ethernet like interface managed via these MIBs.  

]] The "This" should be "The". 
]] MIB-2 is obsolete, and I'm not sure what this section is
]] trying to say. I'm not sure that this functionality
]] can be applied on any "Ethernet-like" interfaces,
]] and not just on the interface types as specified
]] in [802.3ah].  

MBS: The OAM functionality controlled by this MIB can be applied to
any Ethernet interface (for example, 10/100BASE-T).  This was an
explicit goal of the OAM sub taskforce.  This paragraph is attempting
to say that this MIB does not overlap with existing MIBs used to
manage Ethernet interfaces (several examples given via references).
However, it is noted that the indexing scheme is the same.  I can
certainly try to re-write it again to make that point better.  One
possible wording would be:

  "The objects defined in this document manage OAM functionality 
   introduced in [802.3ah]  These objects do not overlap with 
   MIB-2 [RFC1213], the interfaces MIB [RFC2863], the Ethernet like 
   interfaces MIB [RFC3635], or any other MIB currently used to 
   manage various aspects of an Ethernet interface.  The objects 
   defined here are defined for Ethernet like interfaces only and 
   use the same ifIndex as the associated Ethernet interface.  

   Ethernet OAM can be implemented on any Ethernet like interface."

%% Please drop the MIB-2 [RFC1213] reference, since it is obsoleted
%% or updated by other documents. 

 
4.2    Relation to other EFM MIB Modules

  The Ethernet OAM functionality and MIB Module is independent of the
  other functionality and MIB Modules derived from [802.3ah] for copper
  [802.3ah-copper] and EPON [802.3ah-epon].  

  Ethernet OAM may be implemented on point-to-multipoint EFM EPON
  interfaces.  However, because higher layer protocols that run over
  Ethernet interfaces are not designed for the partial connectivity
  provided by a point-to-multipoint interface, EPON provides a point
  to-point emulation layer (see [802.3ah] and [802.3ah-epon]) whereby
  the single EPON interface of 1-to-N connectivity is represented by N
  point-to-point interfaces.  Ethernet OAM, like any other protocol at
  the Ethernet layer or above (for example, bridging), utilizes the
  point-to-point emulation layer of EPON in that the EPON interface is
  viewed as N point-to-point Ethernet interfaces.  Thus OAM, and other
  protocols, do not need to be altered for the EPON environment.  

  Ethernet OAM may be implemented on the 2BASE-TL and 10PASS-TS
  Ethernet-over-copper interfaces defined in EFM [802.3ah].  2BASE-TL
  and 10PASS-TS can be aggregated interfaces, meaning that they can use
  the ifStackTable of the Interfaces Group MIB [RFC2863] to manage a
  set of N (1 <= N <= 32) physical layers into a single Ethernet
  interface.  

  The other Ethernet interfaces introduced in EFM [802.3ah] are simply
  new optical physical layers that are managed by minimal extensions to
  the MAU MIB [RFC3636] defining new types of Ethernet interfaces.  
  
%% I don't believe that "EFM interface types" need any special
%% mention. The key point is that the OAM function can function
%% on any etherLike interface and (if I understand you correctly) 
%% any aggregated interface that uses an aggregation of etherLike
%% interfaces.

4.3    IANA Considerations

  The EFM OAM MIB requires the allocation of a single object identifier
  for its MODULE-IDENTITY under the MIB-2 tree.  IANA has not yet
  allocated this object identifier.
 
]] This needs to be updated to follow the format as
]] specified in [MIBguidelines]

MORE
%% See, for example section 5 in RFC 4188

]] The list that follows seems out of place. At the minimum
]] there needs to be a section header and intro.
]]

 
]] NOTE: I didn't check the list below for errors, such
]]       as omissions and spellings.

MBS: The lack of header/intro is apparently an artifact of RTF->I-D
format conversion.  I'll fix it in the next revision.  The headers and
introduction exist in my RTF file.  

 
  [802.3ah] Clause 30, and managed objects defined in this document.  
  IEEE 802.3 Managed Object     Corresponding SNMP object

]] In the below, it would be useful to also show the object class
]] (the oXXX) containing each attribute. For example, the MAU MIB
]] document (draft-ietf-hubmib-rfc3636bis-01.txt) does this.

MBS: Easy enough to do (there's just oOAM).  
   .aOAMID                       IF-MIB ifIndex

5.   MIB Structure
  The common EFM MIB objects of this memo focus on the OAM capabilities
  introduced in IEEE 802.3ah.  The MIB objects are partitioned into six
]] Probably want [803.3ah] instead of just 802.3ah
MBS: Done
  different MIB groups.

  The dot3OamTable group manages the primary OAM objects of the
  Ethernet interface.  This group controls the state and status of OAM
  as well as the mode in which it operates.  

  The dot3OamPeerTable maintains the current information on the status
  and configuration of the peer OAM entity on the Ethernet interface. 

  Managed information includes the capabilities and function available

]] I think "capabilities" and "function" are the same, so
]] I would drop "and function".

MBS:  I'm not sure I agree with that.  Capabilities generally refers to
what the other guy can do, while functions refers to what it does.  Some
capabilities may be disabled or inoperable for many reasons.  So I'm
trying to say that the MIB covers both potential and actual
functionality.  

  on the peer OAM entity.  
 
  

  The dot3OamLoopbackTable manages the loopback function introduced in
  EFM [802.3ah].  This table controls enabling and disabling loopback,
]] Is there a difference between "EFM [802.3af]" and "[802.3af]"?
]] If so, this needs to be reflected throughout the the
]] document. If not, then the "EFM" should be removed.

MBS: No difference,so I removed EFM.  The benefit of having it in
there is that many people know the project as EFM, even though this
function is not restricted to the physical layers of that project.  


  as well as indicating the loopback status of Ethernet OAM on this
  interface.  

]] Above and through the document, the terms "Ethernet OAM",
]] and "EFM OAM" are used. Are these the same, or different?
]] If different, then this needs to be explained. If the
]] same, then one should be chosen and used consistently.

MBS: There's no intended difference.  As the OAM functionality applies
to any Ethernet interface, I will go with Ethernet OAM rather than EFM
OAM.  

 

 << Text deleted >>


6.   MIB Definition

  EFM-COMMON-MIB DEFINITIONS ::= BEGIN 

]] This module name doesn't follow the naming conventions
]] in the [MIBguidelines] document. However, I can't determine
]] if it should be DOT3-OAM-MIB, or "EFM-OAM-MIB".

MBS: It should be DOT3-OAM-MIB to me, so that's what I'll change it to.

  <<text deleted>>

     efmOamMIB MODULE-IDENTITY 

]] Not sure if should be efmOamMIB or dot3OamMIB

MBS: Changed to dot3OamMIB

 
   <<text deleted>>

       DESCRIPTION
         "The MIB module for managing the new Ethernet OAM features
         introduced by the Ethernet in the First Mile task force (IEEE
         802.3ah).  The functionality presented here is based on IEEE
         802.3ah [802.3ah], released in October, 2004.  


         In particular, this MIB focused on the changes to Clause 30 of
         the draft that are not specific to any physical layer.  These
         changes are primarily reflected in the new OAM features
         developed under this project, that can be applied to any
         Ethernet like interface. The OAM features are described in
         Clause 57 of [802.3ah].
]] First, is it clause 30 or 57.
]] Also, the above reads strangely. People that don't understand
]] exactly how IEEE documents are updated (which is very different
]] than how IETF documents are updated).

MBS:  Attempted re-wording below.  Hopefully this will make more sense
to you.    The functionality is described in one clause, but the
management attributes of that functionality are described in another.  

       "In particular, this MIB focuses on the new OAM functions
       introduced in Clause 57 of [802.3ah].  The OAM functionality of
       Clasue 57 is controlled by new management attributes introduced
       in Clause 30 of [802.3ah].  The OAM functions are not specific
       to any particular Ethernet physical layer, and can be
       generically applied to any Ethernet interface of [802.3-2002].  
      "
%% looks good
 
<< Text deleted >> 


     --
     -- Ethernet OAM Control group
     --

     dot3OamTable OBJECT-TYPE
       SYNTAX      SEQUENCE OF Dot3OamEntry
       MAX-ACCESS  not-accessible
       STATUS      current
       DESCRIPTION 
         "Primary controls and status for the OAM capabilities of an
         Ethernet like interface.  There will be one row in this table
         for each Ethernet like interface in the system that supports
         the Ethernet OAM functions defined in [802.3ah]."   
       ::= { dot3OamMIB 1 }

]] I'm still unclear as to exactly which interfaces will be
]] in this table. For example, if a 10baseT interface card
]] is plugged into the device, will a new row show up?
]] Or is it only for the Cu and EPON interfaces?
]] And does some other configuration (outside of SNMP)
]] configuration have to be done?
]] I believe the answer is not, but want to determine
]] if aggregated interfaces can exist in the table?   
 
MBS:  Any Ethernet interface that can appear in the Ethernet like MIB
table can appear here if OAM functionality is supported.  So the
answer to your questions are
 - yes, if the interfaces support Ethernet OAM (which is optional)
 - no, it is not only for the Cu/EPON interfaces
 - no, no other configuration is required 

%% Just to be sure, if an aggregation interface is created using
%% members that are etherLike, can the aggregation have OAM
%% applied, or is it only for the base links. For example,
%% I can create an aggregation interface from, say 4 1Gig Ethernet
%% interfaces. In this case is the aggregation interface
%% supported by OAM? 

     dot3OamEntry OBJECT-TYPE
       SYNTAX     Dot3OamEntry
       MAX-ACCESS not-accessible
       STATUS     current
       DESCRIPTION 
         "An entry in the table, containing information on the Ethernet
         OAM function for a single Ethernet like interface."
       INDEX       { ifIndex }
       ::= { dot3OamTable 1 }

]] The SMI requires in the DESCRIPTION clause for a row,
]] a description of index objects that not defined in the
]] table.

MBS: Added a description that says when entries created/deleted and the
row status.
%% Don't need a RowStatus column for this table. Just need to say
%% that entries are not created or deleted via SNMP operations.

     Dot3OamEntry ::=
       SEQUENCE {
         dot3OamAdminState                  INTEGER,
         dot3OamOperStatus                  INTEGER,
         dot3OamMode                        INTEGER,
         dot3OamMaxOamPduSize               Integer32,
         dot3OamConfigRevision              Unsigned32, 
         dot3OamFunctionsSupported          BITS
       }

     dot3OamAdminState OBJECT-TYPE
       SYNTAX      INTEGER {
                     disabled(1),
                     enabled(2)
                   }
       MAX-ACCESS  read-write
       STATUS      current
       DESCRIPTION 
         "This object is used to provision the default administrative
         OAM mode for this interface.  This object represents the
         desired state of OAM for this interface.  

  
         The dot3OamAdminState always starts in the disabled(1) state
         until an explicity management action or configuration

]]                ^^^^^^spelling error

MBS: Fixed.
         information retained by the system causes a transition to the
         enabled(2) state. 

         Note that the value of this object is ignored when the
         interface is not operating in full-duplex mode. OAM is not
         supported on half-duplex links.  "
       REFERENCE   "[802.3ah], 30.3.6.1.2"

       ::= { dot3OamEntry 1 }

]] I'm not sure what "ignored" means here.
]] I don't believe that "ignored" is the right term.
]] Shouldn't whether the interface is in half or full-duplex
]] show up in the value of object dot3OamOperStatus?
]] I'm assuming that only interfaces that can operate
]] in full-duplex mode will be in this table. That
]] should of been said in the table DESCRIPTION clause.

MBS: This is a little tricky.  Certain functions in Ethernet OAM
assume full-duplex links.  So I tried to say that you should ignore
the provisioned enable/disable admin state if the link comes up
half-duplex, and just leave OAM disabled.  Certainly a link should
have the capacity to be full-duplex to appear in this table.  However,
if the interface hasn't negotiated duplex yet, we should still allow
it in the table so that OAM can be configured in case the link comes
up full-duplex.  

 
MBS: This behavior is certainly up for
interpretation.  We could allow OAm to operate on half-duplex links
though not every function will be available.  Open to suggestions.  
%% see above

     dot3OamOperStatus OBJECT-TYPE
       SYNTAX      INTEGER {
                     disabled(1),
                     linkfault(2),
                     passiveWait(3),
                     activeSendLocal(4),
                     sendLocalAndRemote(5),
                     sendLocalAndRemoteOk(6),
                     oamPeeringLocallyRejected(7),
                     oamPeeringRemotelyRejected(8),
                     operational(9)
                   }

]] What values indicate that ifAdmin status is set down
]] or testing?
]] What are the values when ifOperStatus is not up?
]] It seems like some of these could occur concurrently.
]] Is this possible?
 
MBS:  if the physical layer is not up, OAM will be in linkfault state
(regardless of whether its down, testing, or anything else).  The
linkFault state is the starting state for any enabled OAM
implementation. There are OAM state machines in [802.3ah] that define
the 9 states above, and one and only one is possible at any time.  
%% See above. Please state this in the DESCRIPTION. However
%% oper and admin work in the IETF management model is DIFFERENT
%% from the ITU module. Don't know the IEEE model.
%% In IETF oper "follows" admin. That is, when admin is down,
%% then oper is down. In ITU, oper is independent from admin.
%% That is, when admin is down (ITU calls this locked), then
%% oper is suppose to tell you if the interface can still
%% work, and would normally be "up".

 
<< Text deleted >>

     dot3OamMaxOamPduSize OBJECT-TYPE
       SYNTAX      Integer32 (64..1522)
]] This should be Unsigned32.
]] Also, is 1522 really the max?


MBS:  I'll change to Unsigned32 though its not clear to me why thats
better.  The maximum value, as defined in [802.3ah] is equal the
maximum untagged frame size (which is undergoing change in 802.3 as we
speak).  I'd like to put a variable in here that ties it to the
maxUntaggedFrameSize, but I don't know what that variable would be.
Numerically, it should currently be 1518, not 1522.  

       UNITS       "bytes"
%% octets please
       MAX-ACCESS  read-only
       STATUS      current 
       DESCRIPTION 
         "The largest OAMPDU that the OAM entity supports.  OAM
         entities exchange maximum OAMPDU sizes and negotiate to use
         the smaller of the two maximum OAMPDU sizes between the peers.
         This value is determined by the local implementation.  
         "
       REFERENCE   "[802.3ah], 30.3.6.1.8"
       ::= { dot3OamEntry 4 }

 << Text deleted >> 

     ------------------------------------------------------------------
     --
     -- Ethernet OAM Peer group
     --

     dot3OamPeerTable OBJECT-TYPE
       SYNTAX      SEQUENCE OF Dot3OamPeerEntry
       MAX-ACCESS  not-accessible
       STATUS      current
       DESCRIPTION 
         "Information about the OAM peer for a particular Ethernet like
         interface. OAM entities communicate with a single OAM peer
         entity on full-duplex Ethernet links on which OAM is enabled
         and operating properly.  

         In certain states, the OAM peer information is not available.
         Whether peer information is available is communicated via the
         dot3OamPeerStatus object.  When this object is inactive, all
         other information in the row is to be considered invalid.  " 
       ::= { dot3OamMIB 2 }

]] Fix this table DESCRIPTION as per global comments
]] The issue of communicating that when the value of dot3OamPeerStatus
]] is 'inactive(2)' that the values of the other columns is
]] unknown, is difficult. Yes, it is said in the DESCRIPTION
]] clause for the row, but I suggest that you also put
]] that in the DESCRIPTION clause for each column. Also,
]] if possible, define a value for each column that is
]] returned when dot3OamPeerStatus is 'inactive(2)',
]] which CAN NOT be a valid value with dot3OamPeerStatus
]] has value 'active(1)'.

MBS: I've attempted to incorporate this comment in the next revision,
and the invalid statement is repeated for every column.  Its not clear
how to devine unique invalid values for every column - for example a
bits field or an unsigned32 where all 2^32 values are allowed.  So I
wasn't able to implement that part of the comment for every column.  
 

     dot3OamPeerEntry OBJECT-TYPE
       SYNTAX      Dot3OamPeerEntry
       MAX-ACCESS  not-accessible
       STATUS      current
       DESCRIPTION 
         "An entry in the table, containing information on the peer OAM
         entity for a single Ethernet like interface.  

         Note that there is at most one OAM peer for each Ethernet like
         interface.  There is exactly one row in this table for each
         Ethernet like interface supporting OAM.  "
       INDEX       { ifIndex }
       ::= { dot3OamPeerTable 1 }
]] Fix. Note, I believe it would be clearer to say
]] (in the DESCRIPTION for the table) that a row
]] exists in this table for each row in the OAM control
]] table.  

MBS:  I'm not sure what you mean by the "OAM control table", but the
intent is that there is at most one row for every entry in the
dot3OamTable.  There may be zero rows in this table for an entry in
the dot3OamTable if the peer information has not been discovered
(yet).  I guess we could say there's always a row but that its
information is inactive(2) - is that your point?  That probably is
simpler.
%% see above.
%% You either have a one-to-one relationship with rows in the
%% control table (dot3OamTable) (and you have object dot3OamPeerStatus),
%% or you have a subset of the rows (and you don't need object
%% dot3OamPeerStatus).

     Dot3OamPeerEntry ::=
       SEQUENCE {
         dot3OamPeerStatus                   INTEGER,
         dot3OamPeerMacAddress               MacAddress, 
         dot3OamPeerVendorOui                Dot3Oui, 
         dot3OamPeerVendorInfo               Unsigned32, 
         dot3OamPeerMode                     INTEGER,
         dot3OamPeerMaxOamPduSize            Integer32,
         dot3OamPeerConfigRevision           Unsigned32,
         dot3OamPeerFunctionsSupported       BITS
       }

     dot3OamPeerStatus OBJECT-TYPE
       SYNTAX      INTEGER {
                     active(1),
                     inactive(2)
                   }
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION 
         "This object indicates whether the information in this row
         should be considered valid.  When active(1), the information
         is valid and represents the current peer of the OAM entity.

         When inactive(2), the information in this row is invalid.  
         A value of inactive(2) is returned if the dot3OamOperStatus is
         disabled, passiveWait, or activeSendLocal.  For all other
         values of dot3OamOperStatus, a value of active(1) is returned.
         "
       ::= { dot3OamPeerEntry 1 }
]] The above doesn't seem possible. Please check.
]] It seems that only when dot3OamOperStatus has the
]] value of 'operational(9)' can this have value 'active(1)'

MBS:  The intent is that you know about the peer entity before OAM
becomes fully operational(9).  As soon as you receive one frame from
the peer you know their basic info (there is a multi-frame exchange
required for initialization).  So I believe the statement is correct
as is.  
%% Please add the above in the DESCRIPTION
 
     dot3OamPeerMacAddress OBJECT-TYPE
       SYNTAX      MacAddress
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION 
         "The MAC address of the peer OAM entity.  The MAC address is
         derived from the most recently received OAMPDU.  This value is
         initialized to all zeros (0x000000000000).  This value is
         invalid if the dot3OamPeerStatus is inactive.  
]] This seems pretty convoluted. Why not say "The MAC address
]]   of the peer OAM entity.  The MAC address is
]]   derived from the most recently received valid OAMPDU.
]]   The value is all zeros (0x000000000000) when the peer's
]]   MAC address unknown, such as when the value of
]]   dot3OamPeerStatus is 'inactive(2)'."
]]
]]   By the way, it seems like a value could be obtained
]]   even when dot3OamPeerStatus is 'inactive(2)'.
]]   If so, is it useful?

MBS;  I didn't see any use, hence the current indications that its
garbage if 'inactive'.  Related to your general comment of
simplification, I'll change the description to indicate zeros are
returned whenever the dot3OamPeerStatus is inactive(2).  
 

         An OAMPDU is indicated by a valid frame with (1) destination
         MAC address equal to that of the reserved MAC address for Slow
         Protocols (See 43B of [802.3ah]), (2) a lengthOrType field
         equal to the reserved type for Slow Protocols, (3) and a Slow
         Protocols subtype equal to that of the subtype reserved for
         OAM.  "

]] Not sure this is needed in this definition.

MBS;  I don't mind removing it - in fact I prefer to.  It was added
because I was asked to specfically define what causes this value to
change.  The event that causes an update to this value is the
reception of an OAMPDU, which is defined as above.  I'm thrilled to be
allowed to kill it.  

%% see above

       REFERENCE   "[802.3ah], 30.3.6.1.5."  
       ::= { dot3OamPeerEntry 2 }

     dot3OamPeerVendorOui OBJECT-TYPE
       SYNTAX      Dot3Oui
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION 
         "The OUI of the OAM peer as reflected in the latest
         Information OAMPDU received with a Local Information TLV.  The
         OUI can be used to identify the vendor of the remote OAM
         entity.  This value is initialized to all zeros (0x000000).
         This value is considered invalid if the dot3OamPeerStatus is
         inactive.
]] Can this be written to be simpler (see above)

MBS; Simplification will be attempted in next revision.  

       REFERENCE   "[802.3ah], 30.3.6.1.16."
       ::= { dot3OamPeerEntry 3 }

     dot3OamPeerVendorInfo OBJECT-TYPE
       SYNTAX      Unsigned32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION 
         "The Vendor Info of the OAM peer as reflected in the latest
         Information OAMPDU received with a Local Information TLV.  The
         vendor information field is within the Local Information TLV,
         and can be used to determine additional information about the

         unspecified within the 32-bit field.  This value is intialized
]]                                              spelling error^^^^^^^^^
MBS: fixed.  
         to all zeros (0x00000000).  This value is invalid if the
         dot3OamPeerStatus is inactive.  

]] Can this be written to be simpler (see above)
]] Also, the 802.3af spec is confusing to me. From
]] it, the value seems like it should have
]] SYNTAX clause value of OCTET STRING(SIZE(4)).
]] But maybe an "Unsigned32" value is OK. If so,
]] the 0x00000000 is very strange. It should just be 0.

MBS: I left this as Unsigned32 as its just a 32-bit field,
non-formatted field.  But I switched to 0 instead of 0x00000000. 

       REFERENCE   "[802.3ah], 30.3.6.1.17."  
       ::= { dot3OamPeerEntry 4 }

 << Text deleted >> 

     ------------------------------------------------------------------
     --
     -- Ethernet OAM Loopback group
     --

     dot3OamLoopbackTable OBJECT-TYPE
       SYNTAX      SEQUENCE OF Dot3OamLoopbackEntry
       MAX-ACCESS  not-accessible
       STATUS      current
       DESCRIPTION 
         "This table contains methods to control the loopback state of
         the local link as well as indicating the status of the
         loopback function.  
         Loopback can be used to place the remote OAM entity in a state
         where every received frame (except OAMPDUs) are echoed back
         over the same interface on which they were received.   In this
         state, at the remote entity, 'normal' traffic is disabled as
         only the looped back frames are transmitted on the interface.
         Loopback is thus an intrusive operation that prohibits normal
         data flow and should be used accordingly.  " 
       ::= { dot3OamMIB 3 }
]] See global comment about tables, and comment on table
]] dot3OamPeerTable.

MBS: done

]] This table is used to put the remote end in loopback
]] and report the loopback status of the local and remote
]] ports
]] I'm confused as to whether both local and remote ports
]] can be put in loopback. And if not, then what happens
]] if the peer has put the local port in loopback and
]] an attempt is made to put the peer's port (the remote
]] port) in loopback?

MBS: Simultaneous loopback on both ends is not possible - the protocol
detects such an action and an election algorithm is used to determine
which port enters loopback state and which does not.  

     dot3OamLoopbackEntry OBJECT-TYPE
       SYNTAX      Dot3OamLoopbackEntry
       MAX-ACCESS  not-accessible
       STATUS      current
       DESCRIPTION 
         "An entry in the table, containing information on the loopback
         status for a single Ethernet like interface.  There is an
         entry in this table for every Ethernet like interface on which
         supports OAM and loopback function within OAM (as indicated in
         dot3OamFunctionsSupported).  "
]] See previous comments on rows
MBS: Changed to indicated automatic creation and conditions.  
       INDEX       { ifIndex }
       ::= { dot3OamLoopbackTable 1 }

 <<text deleted>>

     dot3OamLoopbackCommand OBJECT-TYPE
       SYNTAX      INTEGER { 
                     noLoopback (1),
                     startRemoteLoopback (2),
                     stopRemoteLoopback (3)
                   } 
       MAX-ACCESS  read-write
       STATUS      current 
       DESCRIPTION 
         "This attribute initiates or terminates remote loopback with
         an OAM peer.  Writing startRemoteLoopback(2) to this attribute
         cause the local OAM client to send a loopback OAMPDU to the
         OAM peer with the loopback enable flags set.  Writing
         stopRemoteLoopback(3) to this attribute will cause the local
         OAM client to send a loopback OAMPDU to the OAM peer with the
         loopback enable flags cleared.  Writing noLoopback to this
         attribute has no effect.  

         Writes to this attribute are ignored unless the OAM status of
         this interface is 'operational' (dot3OamOperStatus).  
         The attribute always returns noLoopback on a read.  To
         determine the loopback status, use the attribute
         dot3OamLoopbackStatus.  " 
       REFERENCE   "[802.3ah], 57.2.11"   
       ::= { dot3OamLoopbackEntry 1 }
]] This object and the next need to be combined into a
]] action/status object.
]] The combined object support all the enum values
]] for dot3OamLoopbackStatus (which would be read-only)
]] and startRemoteLoopback and stopRemoteLoopback
]] from this object. Writes of startRemoteLoopback
]] when remote is already loopbacked (or dot3OamOperStatus
]] is not operational) cause no operation.
]] Likewise, writes of stopRemoteLoopback when remote
]] is not loopbacked (or dot3OamOperStatus
]] is not operational) cause no operation.
]] Note: just don't know what happens when
]] current value is localLoopback.  

MBS: I can change it, but I'd like to be pointed to an example.  All
of the examples I've come across had two objects, one for the actions,
one for the status, which is where this model comes from.  During
discussion with the group, two objects were suggested as the desired
approach.  

<< Text deleted >>

     ------------------------------------------------------------------
     --
     -- Ethernet OAM Statistics group
     --

     dot3OamStatsTable OBJECT-TYPE
       SYNTAX      SEQUENCE OF Dot3OamStatsEntry
       MAX-ACCESS  not-accessible
       STATUS      current
       DESCRIPTION 
         "Statistics for the OAM function on a particular Ethernet like
         interface." 
       ::= { dot3OamMIB 4 }
]] See previous comments on tables.
MBS: Done

]] Add a note in the commentary section as to why the counters
]] in this table are Counter32 instead of Counter64!

MBS: Done.  The size of the counters was selected to match the size of
the counters as defined in 802.3.

 << Text deleted >>

     dot3OamUnsupportedCodesTx OBJECT-TYPE
       SYNTAX      Counter32
       UNITS       "frames"
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION 
         "A count of the number of OAMPDUs transmitted on this
         interface with an unsupported op-code.  
]] This is very strange.
]] Why would you send an "unsupported code"?
]] How would you know that you sent an "unsupported code"?

MBS: Granted it seems a little strange.  The variable is supported in
the 802.3ah standard, so I decided to expose it via the MIB.  Since
Ethernet OAM could be supported in the HW or in the SW, the thought
was someone might try to do things where the underlying layer doesn't
support that thing (for example, loopback), and you might want to know
about it.  
%% Does the other end tell you that you have sent an unsupported
%% op-code?

 << Text deleted >> 

     dot3OamFramesLostDueToOam OBJECT-TYPE
]] Strange descriptor. How about "dot3OamDroppedTxFrames"

MBS: I'm trying to match the names in 802.3ah as closely as possible
to make the implmeentaiton easier.  In 802.3, its called
FramesLostDueToOam.  The reason its not "OamDroppedTxFrames" is
because that might sound like OAM frames are dropped, when really any
frame might be dropped because OAM took precedence.  
%% I'm not sure I could figure that out the above. Why not put it
%% in the DESCRIPTION 
       SYNTAX      Counter32
       UNITS       "frames"
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION 
         "A count of the number of frames that were dropped by the OAM
         multiplexer.  Since the OAM mulitplexer has multiple inputs
         and a single output, there may be cases where frames are
         dropped due to transmit resource contention.  This counter is
         incremented whenever a frame is dropped by the OAM layer.
         When this counter is incremented, no other counters in this
         MIB are incremented.  
                       
         Discontinuities of this counter can occur at re-initialization
         of the management system, and at other times as indicated by
         the value of the ifCounterDiscontinuityTime.  "
       REFERENCE   "[802.3ah], 30.3.6.1.46."  
       ::= { dot3OamStatsEntry 17 }

     ------------------------------------------------------------------
     --
     -- Ethernet OAM Event Configuration group
     --

 << Text deleted >> 
  

     dot3OamErrSymPeriodWindowHi OBJECT-TYPE
]] This needs to be combined with the next object
]] and given syntax CounterBasedGauge64

MBS: This was discussed on the list.  The discussion said that
CounterBasedGauge64 is read-only and since this is a writable value,
it wouldn't apply.  
%% Sorry, you are correct
 
<< Text deleted >>

     dot3OamErrFrameWindow OBJECT-TYPE
       SYNTAX      Unsigned32
       UNITS       "tenths of a second"
       MAX-ACCESS  read-write
       STATUS      current
       DESCRIPTION 
         "The amount of time (in 100ms increments) over which the
]] why not just say "in tenth of a second intervals" instead
]] of "in 100ms intervals"

MBS: 100ms seems easier to say then "tenths of a second"
         threshold is defined.  The default value is 10 (1 second).  
                         
        If dot3OamErrFrameThreshold frame errors occur within a window
        of dot3OamErrFrameWindow seconds (measured in tenths of
        seconds), an Event Notification OAMPDU should be generated with
        an Errored Frame Event TLV indicating the threshold has been
        crossed in this window.  "
       REFERENCE   "[802.3ah], 30.3.6.1.36"  
       ::= { dot3OamEventConfigEntry 9 }
       

     dot3OamErrFrameThreshold OBJECT-TYPE
       SYNTAX      Unsigned32
]] What happens when the value is zero?

MBS: This would result in an event notification being sent at the end
of every measuring period.  So if the window were 30sec, you'd get an
OAMPDU every 30s saying how many errored frame there were.  Some may
consider this useless,but others thought it a way to get regular
periodic updtes on these error counters (e.g. tell me what the values
are every 30s).  
%% so why not include that in the DESCRIPTION
 

 << Text deleted >>

     ------------------------------------------------------------------
     -- 
     -- Ethernet OAM Event Status group 
     -- 

     dot3OamEventLogTable   OBJECT-TYPE 
       SYNTAX       SEQUENCE OF Dot3OamEventLogEntry 
       MAX-ACCESS   not-accessible 
       STATUS       current 
       DESCRIPTION 
]] See comments on tables
]] On this table, can it have an infinite number of entries?
]] Most likely not. In other tables, there is some indication
]] that says the max number (not always available), but
]] always something that says to either stop adding entries,
]] or delete the oldest, or some other algorithm to replace
]] the least important with a new one.

 
MBS: Added words to say that size is implemetnation dependent, and
that older entries should be automtically deleted to make room for
newer entries.  
%% see above

         "This table records a history of the events that have occurred
         at the Ethernet OAM level.  These events can include locally
         detected events, which may result in locally generated
         OAMPDUs, and remotely detected events, which are detected by
         the OAM peer entity and signaled to the local entity via
         Ethernet OAM.  Ethernet OAM events can be signaled by Event
         Notification OAMPDUs or by the flags field in any OAMPDU.  "
]] Need to indicate that there are threshold crossing events
]] and nonthreshold events. For each, indicate the columns that
]] have meaningful values. The descriptions about the MAX values
]] didn't make sense until I read the descriptions of the
]] notifications and saw what was going on. 

MBS: Added words to say which columsn only apply to threshold crossing
events.  

         ::= { dot3OamMIB 6 } 
  

     dot3OamEventLogEntry OBJECT-TYPE 
       SYNTAX      Dot3OamEventLogEntry 
       MAX-ACCESS  not-accessible 
       STATUS      current 
       DESCRIPTION "An entry in the dot3OamEventLogTable." 
]] See previous comments on rows.
MBS: Done.

]] Can selected entries in this table be deleted by
]] management operations?

MBS: The thought was no,that the table reflects what happened (to the
extent that it can).  

       INDEX       { ifIndex, dot3OamEventLogIndex }
       ::= { dot3OamEventLogTable 1 } 

 << Text deleted >>
  

     dot3OamEventLogType      OBJECT-TYPE
       SYNTAX      Unsigned32 
       MAX-ACCESS  read-only
       STATUS      current 
       DESCRIPTION 
         "The type of event that generated this entry in the event log.

         When the OUI is the IEEE 802.3 OUI of 0x0180C2, the following
         event types are defined:
             erroredSymbolEvent(1), 
             erroredFramePeriodEvent (2), 
             erroredFrameEvent(3),
             erroredFrameSecondsEvent(4), 
             linkFault(256), 
             dyingGaspEvent(257),
             criticalLinkEvent(258)
         The first four are considered threshold crossing events as
         they are generated when a metric exceeds a given value within
         a specified window.  The other three are not threshold
         crossing events.  
  
         When the OUI is not 0x0180C2, then some other organization has
         defined the event space.  If event subtyping is known to the
         implementation, it may be reflected here.  Otherwise, this
         value should return all Fs (0xFFFFFFFF).  
         "

]] If this is an Unsigned32, then say this in numeric
]] terms and not in terminology used for octet strings.

MBS: added decimal value in addition to all Fs.  
       REFERENCE   "[802.3ah], 30.3.6.1.10 and 57.5.3."
       ::= { dot3OamEventLogEntry 4 }

<< Text deleted >>

]] I'm not sure that I understand the objects
]] dot3OamEventLogRunningTotal and
]] dot3OamEventLogEventTotal. It
]] seems like dot3OamEventLogRunningTotal is the
]] value of a counter that is being thresholded,
]] and dot3OamEventLogEventTotal is the count of
]] the event crossings. 

]] These counts seem possibly expensive to do.
]] Ok - after reading 802.3af, I see what is going on.
]] The descriptions below are really difficult to
]] understand. They need a rewrite.

 
MBS: Rewrite will be attempted.  

<< Text deleted >>

     ------------------------------------------------------------------
     -- 
     -- Ethernet OAM Notifications
     -- 

     dot3OamNotifs OBJECT IDENTIFIER ::= { dot3OamMIB 7 }
     dot3OamNotifsPrefix OBJECT IDENTIFIER ::= {dot3OamNotifs 0}
]] remove these, and update OID values for notifications
MBS: I will delete these and replace the dot3OamNotifsPrefix in the
object below with dot3OamNotifications that you added earlier in the
MIB.  

 << Text deleted >>

     ------------------------------------------------------------------
     --
     -- Ethernet OAM Compliance group
     --

     dot3OamGroups OBJECT IDENTIFIER ::= { dot3OamConformance 1 }
     dot3OamCompliances OBJECT IDENTIFIER ::= { dot3OamConformance 2 }

     -- Compliance statements

     dot3OamCompliance MODULE-COMPLIANCE 
       STATUS          current
       DESCRIPTION "The compliance statement for managed entities
                    supporting OAM on Ethernet like interfaces.  

                    "
     MODULE   -- this module
       MANDATORY-GROUPS { dot3OamControlGroup, 
                          dot3OamPeerGroup, 
                          dot3OamStatsBaseGroup 
                        }

       GROUP       dot3OamLoopbackGroup
       DESCRIPTION 
         "This group is mandatory for all IEEE 802.3 OAM
         implementations that support loopback functionality. "

       GROUP       dot3OamErrSymbolPeriodEventGroup
       DESCRIPTION 
         "This group is mandatory for all IEEE 802.3 OAM
         implementations that support event functionality. "

       GROUP       dot3OamErrFramePeriodEventGroup
       DESCRIPTION 
         "This group is mandatory for all IEEE 802.3 OAM
         implementations that support event functionality. "

       GROUP       dot3OamErrFrameEventGroup
       DESCRIPTION 
         "This group is mandatory for all IEEE 802.3 OAM
         implementations that support event functionality. "

       GROUP       dot3OamErrFrameSecsSummaryEventGroup
       DESCRIPTION 
         "This group is mandatory for all IEEE 802.3 OAM
         implementations that support event functionality. "


       GROUP dot3OamFlagEventGroup
       DESCRIPTION
         "This group is optional for all IEEE 802.3 OAM
         implementations.  The ability to send critical events or 
         dying gasp events is not required in any system."

  
       GROUP       dot3OamEventLogGroup
       DESCRIPTION 
         "This group is optional for all IEEE 802.3 OAM
         implementations. "
]] There will not be any local events in the log table
]] unless some of the event groups are implemented.
MBS: Correct.  Is that a question or are you suggesting some action?  

%% The descriptions specify dependencies.   


       GROUP       dot3OamNotificationGroup
       DESCRIPTION 
         "This group is optional for all IEEE 802.3 OAM
         implementations. "

]] This group requires implementation of the log table,
]] since the objects in the notifications are objects
]] in the log table!

MBS: I'm not sure what to do here, will have to think about it.  
 

       ::= { dot3OamCompliances 1}


]] The way this module compliance is written, there are
]] a couple of unconditionally optional items (like the
]] notifications and logging). Also, there can be mix and
]] match of optional items. This is bad for IETF standards
]] track progression. You might consider having two
]] module compliance specifications - a minimal and
]] maximal. Others, like Bert, and provide better
]] advice as to the best practices in IETF standards
]] track MIB modules.

<<text deleted>>

    dot3OamStatsBaseGroup OBJECT-GROUP
       OBJECTS     {   dot3OamInformationTx,
                       dot3OamInformationRx,
                       dot3OamUniqueEventNotificationTx,
                       dot3OamUniqueEventNotificationRx,
                       dot3OamDuplicateEventNotificationTx,
                       dot3OamDuplicateEventNotificationRx,
                       dot3OamLoopbackControlTx,
                       dot3OamLoopbackControlRx,
                       dot3OamVariableRequestTx,
                       dot3OamVariableRequestRx,
                       dot3OamVariableResponseTx,
                       dot3OamVariableResponseRx,
                       dot3OamOrgSpecificTx,
                       dot3OamOrgSpecificRx,
                       dot3OamUnsupportedCodesTx,
                       dot3OamUnsupportedCodesRx,
                       dot3OamFramesLostDueToOam
                   }
       STATUS      current
       DESCRIPTION 
         "A collection of objects providing the statistics for the
         number of various transmit and recieve events for OAM on an
         Ethernet like interface.  Note that all of these counters must
         be supported even if the related function (as described in
         dot3OamFunctionsSupported) is not supported.  "
       ::= { dot3OamGroups 3 }

]] The compliance is not specified in group definitions.
MBS: Its one of the mandatory groups - what else are you looking for. 
%% Oops, overlooked it, sorry.
  

<<text deleted>>

    dot3OamErrFrameEventGroup OBJECT-GROUP
       OBJECTS     {   dot3OamErrFrameWindow,
                       dot3OamErrFrameThreshold,
                       dot3OamErrFrameEvNotifEnable
                   }
       STATUS      current
       DESCRIPTION 
         "A collection of objects for configuring the thresholds for an
         Errored Frame Event.  

         Each [802.3ah] defined Event Notification TLV has its own
         conformance group because each event can be implemented
         independently of any other.  "
       ::= { dot3OamGroups 7 }

]] Put this info about 802.3af in the commentary section
MBS: Which section are you refering to exactly?  
%% Put it in the section before the MIB module, that describes
%% the organization of the objects in the MIB module.

<<text deleted>>

     END
 

Regards,
/david t. perkins


_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib



From hubmib-bounces@ietf.org Sun Jan 22 11:00:16 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F0hdY-0003qc-Ij; Sun, 22 Jan 2006 11:00:16 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1F0hdW-0003qS-Kf
	for hubmib@megatron.ietf.org; Sun, 22 Jan 2006 11:00:14 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA27995
	for <hubmib@ietf.org>; Sun, 22 Jan 2006 10:58:46 -0500 (EST)
Received: from nj300815-ier2.net.avaya.com ([198.152.12.103])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F0hmg-0003cp-D7
	for hubmib@ietf.org; Sun, 22 Jan 2006 11:09:43 -0500
Received: from tiere.net.avaya.com (tiere.net.avaya.com [198.152.12.100])
	by nj300815-ier2.net.avaya.com (Switch-3.1.7/Switch-3.1.7) with ESMTP
	id k0MFv9jo005558
	for <hubmib@ietf.org>; Sun, 22 Jan 2006 10:57:09 -0500
Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com
	[135.64.105.51])
	by tiere.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id
	k0MFv5QH007275
	for <hubmib@ietf.org>; Sun, 22 Jan 2006 10:57:05 -0500 (EST)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Hubmib] Response to EPON-MIB-04
Date: Sun, 22 Jan 2006 18:00:04 +0200
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F09E8C898@is0004avexu1.global.avaya.com>
Thread-Topic: [Hubmib] Response to EPON-MIB-04
Thread-Index: AcYd6SEWdZt/VRVpTdSxSnQrYnyMuABgi5WQ
From: "Romascanu, Dan \(Dan\)" <dromasca@avaya.com>
To: "David T. Perkins" <dperkins@dsperkins.com>, <lior.khermosh@passave.com>
X-Scanner: InterScan AntiVirus for Sendmail
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Content-Transfer-Encoding: quoted-printable
Cc: Hub MIB <hubmib@ietf.org>
X-BeenThere: hubmib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Ethernet Interfaces an Hub MIB WG <hubmib.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/hubmib>,
	<mailto:hubmib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:hubmib@ietf.org>
List-Help: <mailto:hubmib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/hubmib>,
	<mailto:hubmib-request@ietf.org?subject=subscribe>
Sender: hubmib-bounces@ietf.org
Errors-To: hubmib-bounces@ietf.org

What is exactly the rationale for this request, David?=20

The other MIB modules in the family are named EFM-COMMON-MIB and
EFM-CU-MIB. If we are to look for consistency, the names of the MIB
modules defined in this document should be EFM-EPON-MIB and
EFM-EPON-DEVICE-MIB.

Regards,

Dan


=20
=20

> -----Original Message-----
> From: David T. Perkins [mailto:dperkins@dsperkins.com]=20
> Sent: Friday, January 20, 2006 7:43 PM
> To: lior.khermosh@passave.com
> Cc: Romascanu, Dan (Dan); Hub MIB
> Subject: Re: [Hubmib] Response to EPON-MIB-04
>=20
> HI,
>=20
> Just saw one more small item. The MIB module is named=20
> "DOT3-EFM-EPON-MIB". I suggest that the name "DOT3-EPON-MIB"
> be used instead.
>=20
> Regards,
> /david t. perkins
>=20
>=20
>=20

_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib



From hubmib-bounces@ietf.org Sun Jan 22 13:36:08 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F0k4O-00005C-2p; Sun, 22 Jan 2006 13:36:08 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1F0k4M-000057-Rg
	for hubmib@megatron.ietf.org; Sun, 22 Jan 2006 13:36:06 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA07653
	for <hubmib@ietf.org>; Sun, 22 Jan 2006 13:34:37 -0500 (EST)
Received: from co300216-ier2.net.avaya.com ([198.152.13.103])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F0kDX-0007wZ-Qe
	for hubmib@ietf.org; Sun, 22 Jan 2006 13:45:37 -0500
Received: from tierw.net.avaya.com (h198-152-13-100.avaya.com [198.152.13.100])
	by co300216-ier2.net.avaya.com (Switch-3.1.7/Switch-3.1.7) with ESMTP
	id k0MHXbuh029961
	for <hubmib@ietf.org>; Sun, 22 Jan 2006 12:33:37 -0500
Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com
	[135.64.105.51])
	by tierw.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id
	k0MIKlYj019752
	for <hubmib@ietf.org>; Sun, 22 Jan 2006 13:20:48 -0500 (EST)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Sun, 22 Jan 2006 20:35:57 +0200
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F09E8C8D9@is0004avexu1.global.avaya.com>
Thread-Topic: Response to comments on OAM doc
Thread-Index: AcYeIdXnXE5uOqX2QpG2WLZY2l+JsgBX5nKQ
From: "Romascanu, Dan \(Dan\)" <dromasca@avaya.com>
To: "David T. Perkins" <dperkins@dsperkins.com>, <hubmib@ietf.org>
X-Scanner: InterScan AntiVirus for Sendmail
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793
Content-Transfer-Encoding: quoted-printable
Cc: MSquire@HatterasNetworks.com
Subject: [Hubmib] RE: Response to comments on OAM doc
X-BeenThere: hubmib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Ethernet Interfaces an Hub MIB WG <hubmib.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/hubmib>,
	<mailto:hubmib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:hubmib@ietf.org>
List-Help: <mailto:hubmib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/hubmib>,
	<mailto:hubmib-request@ietf.org?subject=subscribe>
Sender: hubmib-bounces@ietf.org
Errors-To: hubmib-bounces@ietf.org

(speaking as a contributor)=20

Grrrrr ... I did not want to enter into a naming discussion at this
stage, but it looks like we got into one anyway.=20

There is no overall convention for names of hubmib MIB modules to be
prefixed by DOT3. If there is a consistency to be reached, I would
rather aim all EFM MIB module names to be prefixed by EFM.=20

Thus, the module names I would recommend to be used in the four
documents are:

EFM-OAM-MIB=20
EFM-CU-MIB
EFM-EPON-MIB
EFM-EPON-DEVICE-MIB

The descriptors associated with the module identity and the other
descriptors of MIB objects within the MIB modules should be a lower case
version of the module name prefix without hyphenation of course, as
recommended in Annex C of RFC 4181.

Regards,

Dan


=20
=20

> -----Original Message-----
> From: David T. Perkins [mailto:dperkins@dsperkins.com]=20
>=20
> 6.   MIB Definition
>=20
>   EFM-COMMON-MIB DEFINITIONS ::=3D BEGIN=20
>=20
> ]] This module name doesn't follow the naming conventions
> ]] in the [MIBguidelines] document. However, I can't determine
> ]] if it should be DOT3-OAM-MIB, or "EFM-OAM-MIB".
>=20
> MBS: It should be DOT3-OAM-MIB to me, so that's what I'll=20
> change it to.
>=20
>   <<text deleted>>
>=20
>      efmOamMIB MODULE-IDENTITY=20
>=20
> ]] Not sure if should be efmOamMIB or dot3OamMIB
>=20
> MBS: Changed to dot3OamMIB
>=20
>=20

_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib



From hubmib-bounces@ietf.org Sun Jan 22 13:43:17 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F0kBJ-0002US-D2; Sun, 22 Jan 2006 13:43:17 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1F0kBH-0002Os-FO
	for hubmib@megatron.ietf.org; Sun, 22 Jan 2006 13:43:15 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA08192
	for <hubmib@ietf.org>; Sun, 22 Jan 2006 13:41:45 -0500 (EST)
Received: from smtpout1.bayarea.net ([209.128.95.10])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F0kKS-0008Ax-GC
	for hubmib@ietf.org; Sun, 22 Jan 2006 13:52:45 -0500
Received: from shell4.bayarea.net (shell4.bayarea.net [209.128.82.1])
	by smtpout1.bayarea.net (8.12.10/8.12.10) with ESMTP id k0MIh3cU012587; 
	Sun, 22 Jan 2006 10:43:03 -0800
Received: from shell4.bayarea.net (localhost [127.0.0.1])
	by shell4.bayarea.net (8.12.11/8.12.11) with ESMTP id k0MIeQQO019604;
	Sun, 22 Jan 2006 10:40:26 -0800
Received: from localhost (dperkins@localhost)
	by shell4.bayarea.net (8.12.11/8.12.11/Submit) with ESMTP id
	k0MIeQWt019590; Sun, 22 Jan 2006 10:40:26 -0800
X-Authentication-Warning: shell4.bayarea.net: dperkins owned process doing -bs
Date: Sun, 22 Jan 2006 10:40:25 -0800 (PST)
From: "David T. Perkins" <dperkins@dsperkins.com>
X-Sender: dperkins@shell4.bayarea.net
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
Subject: RE: [Hubmib] Response to EPON-MIB-04
In-Reply-To: <AAB4B3D3CF0F454F98272CBE187FDE2F09E8C898@is0004avexu1.global.avaya.com>
Message-ID: <Pine.LNX.4.10.10601221000220.3366-100000@shell4.bayarea.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 25620135586de10c627e3628c432b04a
Cc: lior.khermosh@passave.com, Hub MIB <hubmib@ietf.org>
X-BeenThere: hubmib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Ethernet Interfaces an Hub MIB WG <hubmib.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/hubmib>,
	<mailto:hubmib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:hubmib@ietf.org>
List-Help: <mailto:hubmib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/hubmib>,
	<mailto:hubmib-request@ietf.org?subject=subscribe>
Sender: hubmib-bounces@ietf.org
Errors-To: hubmib-bounces@ietf.org

HI,

First, I was pointing out an inconsistancy between the
module name and the descriptor for the the MODULE-IDENTITY.
In lior's lastest I-D, there are
   DOT3-EFM-EPON-MIB DEFINITIONS ::= BEGIN
    <<text deleted>>
   dot3EponMIB MODULE-IDENTITY

This is inconsistent. Thus, the module name should be
 DOT3-EPON-MIB
or the descriptor should be
 dot3EfmEponMIB

However, with regards to the naming scheme for the
collection of documents, I believe the that "EFM"
is not approapriate for the dot3 OAM MIB module
(since it applies to any dot3 technology),
and whether or not the EFM is part of the EPON or
CU MIB modules, this is something for the WG to decide.
However, it seems to me that EFM is a marketing term
and the dot3 is more appropriate. The 802.3ah
document calls the CU and EPON technology "Subscriber
access networks" in the document title, and then
and inside the document there are phrases like:
67.1 Overview
This clause provides information on building Ethernet subscriber
access networks, also referred to as "Ethernet in the First Mile",
or EFM networks. 

Given than "copper" when describing dot3 is ambiguous,
then an additional adjective is needed. But with EPON,
there is no ambiguity. Thus, I suggest the following
module names:
  DOT3-EPON-MIB (or DOT3-EFM-EPON-MIB)
  DOT3-EFM-CU-MIB
  DOT3-OAM-MIB 

Then have consistent descriptors for items defined in
the MIB modules. For the lastest OAM and EPON modules,
the prefixes are dot3Oam and dot3Epon (plus dot3Mpcp,
dot3OmpE, etc).
The CU module has prefixe emfCu.

On Sun, 22 Jan 2006, Romascanu, Dan (Dan) wrote:
> What is exactly the rationale for this request, David? 
> 
> The other MIB modules in the family are named EFM-COMMON-MIB and
> EFM-CU-MIB. If we are to look for consistency, the names of the MIB
> modules defined in this document should be EFM-EPON-MIB and
> EFM-EPON-DEVICE-MIB.
> 
> Regards,
> 
> Dan
> > -----Original Message-----
> > From: David T. Perkins [mailto:dperkins@dsperkins.com] 
> > Sent: Friday, January 20, 2006 7:43 PM
> > To: lior.khermosh@passave.com
> > Cc: Romascanu, Dan (Dan); Hub MIB
> > Subject: Re: [Hubmib] Response to EPON-MIB-04
> > 
> > HI,
> > 
> > Just saw one more small item. The MIB module is named 
> > "DOT3-EFM-EPON-MIB". I suggest that the name "DOT3-EPON-MIB"
> > be used instead.
> > 
> > Regards,
> > /david t. perkins

Regards,
/david t. perkins


_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib



From hubmib-bounces@ietf.org Sun Jan 22 13:47:45 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F0kFd-0003z9-Dt; Sun, 22 Jan 2006 13:47:45 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1F0kFc-0003z4-MS
	for hubmib@megatron.ietf.org; Sun, 22 Jan 2006 13:47:44 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA08556
	for <hubmib@ietf.org>; Sun, 22 Jan 2006 13:46:14 -0500 (EST)
Received: from nj300815-ier2.net.avaya.com ([198.152.12.103])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F0kOn-0008L3-E7
	for hubmib@ietf.org; Sun, 22 Jan 2006 13:57:14 -0500
Received: from tiere.net.avaya.com (tiere.net.avaya.com [198.152.12.100])
	by nj300815-ier2.net.avaya.com (Switch-3.1.7/Switch-3.1.7) with ESMTP
	id k0MIiY3u011488
	for <hubmib@ietf.org>; Sun, 22 Jan 2006 13:44:34 -0500
Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com
	[135.64.105.51])
	by tiere.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id
	k0MIiUQH002213
	for <hubmib@ietf.org>; Sun, 22 Jan 2006 13:44:31 -0500 (EST)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Hubmib] Response to comments on OAM doc
Date: Sun, 22 Jan 2006 20:47:29 +0200
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F09E8C8DA@is0004avexu1.global.avaya.com>
Thread-Topic: [Hubmib] Response to comments on OAM doc
Thread-Index: AcYfGjickonnycvcRiq8/9B3UMqcQwAaLscw
From: "Romascanu, Dan \(Dan\)" <dromasca@avaya.com>
To: "David T. Perkins" <dperkins@dsperkins.com>, <hubmib@ietf.org>
X-Scanner: InterScan AntiVirus for Sendmail
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Content-Transfer-Encoding: quoted-printable
Cc: MSquire@HatterasNetworks.com
X-BeenThere: hubmib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Ethernet Interfaces an Hub MIB WG <hubmib.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/hubmib>,
	<mailto:hubmib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:hubmib@ietf.org>
List-Help: <mailto:hubmib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/hubmib>,
	<mailto:hubmib-request@ietf.org?subject=subscribe>
Sender: hubmib-bounces@ietf.org
Errors-To: hubmib-bounces@ietf.org


>=20
>      dot3OamMaxOamPduSize OBJECT-TYPE
>        SYNTAX      Integer32 (64..1522)
> ]] This should be Unsigned32.
> ]] Also, is 1522 really the max?
>=20
>=20
> MBS:  I'll change to Unsigned32 though its not clear to me why thats
> better.  The maximum value, as defined in [802.3ah] is equal the
> maximum untagged frame size (which is undergoing change in 802.3 as we
> speak).  I'd like to put a variable in here that ties it to the
> maxUntaggedFrameSize, but I don't know what that variable would be.
> Numerically, it should currently be 1518, not 1522. =20
>=20

See RFC 4181, Section 4.6.1.1 for the reason of using Unsigned32.

Concerning the new max PDU size. It is true that IEEE 802.3as is working
at a frame extension that would take the max frame size to a new value,
around 2k I believe. We should be able to liaison with them and
determine if they already can tell us what is this value.=20

However, my question is whether EFM OAM is supposed to use the new max
size. It was designed by the time a non-tagged frame was (actually still
is by today) 1518. Is there any text that says what the max size of a
OAM PDU can be - 1518, or the max size of the day?

Thanks,

Dan


_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib



From hubmib-bounces@ietf.org Sun Jan 22 13:53:04 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F0kKm-00067O-LZ; Sun, 22 Jan 2006 13:53:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1F0kKl-00067E-8u
	for hubmib@megatron.ietf.org; Sun, 22 Jan 2006 13:53:03 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA08955
	for <hubmib@ietf.org>; Sun, 22 Jan 2006 13:51:33 -0500 (EST)
Received: from nj300815-ier2.net.avaya.com ([198.152.12.103])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F0kTx-0008WA-BI
	for hubmib@ietf.org; Sun, 22 Jan 2006 14:02:33 -0500
Received: from tiere.net.avaya.com (tiere.net.avaya.com [198.152.12.100])
	by nj300815-ier2.net.avaya.com (Switch-3.1.7/Switch-3.1.7) with ESMTP
	id k0MIo4Cm013576
	for <hubmib@ietf.org>; Sun, 22 Jan 2006 13:50:04 -0500
Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com
	[135.64.105.51])
	by tiere.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id
	k0MIo0QH002983
	for <hubmib@ietf.org>; Sun, 22 Jan 2006 13:50:00 -0500 (EST)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Hubmib] Response to EPON-MIB-04
Date: Sun, 22 Jan 2006 20:52:59 +0200
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F09E8C8DC@is0004avexu1.global.avaya.com>
Thread-Topic: [Hubmib] Response to EPON-MIB-04
Thread-Index: AcYfg6lrpkvwsQvRTgSBwHLS6PKGkwAAKQfw
From: "Romascanu, Dan \(Dan\)" <dromasca@avaya.com>
To: "David T. Perkins" <dperkins@dsperkins.com>
X-Scanner: InterScan AntiVirus for Sendmail
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1a1bf7677bfe77d8af1ebe0e91045c5b
Content-Transfer-Encoding: quoted-printable
Cc: lior.khermosh@passave.com, Hub MIB <hubmib@ietf.org>
X-BeenThere: hubmib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Ethernet Interfaces an Hub MIB WG <hubmib.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/hubmib>,
	<mailto:hubmib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:hubmib@ietf.org>
List-Help: <mailto:hubmib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/hubmib>,
	<mailto:hubmib-request@ietf.org?subject=subscribe>
Sender: hubmib-bounces@ietf.org
Errors-To: hubmib-bounces@ietf.org

David,

I have no strong feelings on this, but I still would argue that EFM is a
better prefix. Although true that EFM OAM may apply to any Ethernet
link, this is kind of a side effect, it still was designed as part of
the 802.3ah project. EFM is the name the whole planet knows this
technology, and it is recognized as such in the overview section of
clause 67 of the IEEE document quoted by you. Moreover, we did not
follow a strict dot3 prefixing policy in the past, starting now when the
last MIB modules are on the exit gate seems a little odd.

I agree with you on the need of consistency between the module name and
the identifiers of the module and object names.=20

Regards,

Dan




=20
=20

> -----Original Message-----
> From: David T. Perkins [mailto:dperkins@dsperkins.com]=20
> Sent: Sunday, January 22, 2006 8:40 PM
> To: Romascanu, Dan (Dan)
> Cc: lior.khermosh@passave.com; Hub MIB
> Subject: RE: [Hubmib] Response to EPON-MIB-04
>=20
> HI,
>=20
> First, I was pointing out an inconsistancy between the module=20
> name and the descriptor for the the MODULE-IDENTITY.
> In lior's lastest I-D, there are
>    DOT3-EFM-EPON-MIB DEFINITIONS ::=3D BEGIN
>     <<text deleted>>
>    dot3EponMIB MODULE-IDENTITY
>=20
> This is inconsistent. Thus, the module name should be =20
> DOT3-EPON-MIB or the descriptor should be  dot3EfmEponMIB
>=20
> However, with regards to the naming scheme for the collection=20
> of documents, I believe the that "EFM"
> is not approapriate for the dot3 OAM MIB module (since it=20
> applies to any dot3 technology), and whether or not the EFM=20
> is part of the EPON or CU MIB modules, this is something for=20
> the WG to decide.
> However, it seems to me that EFM is a marketing term and the=20
> dot3 is more appropriate. The 802.3ah document calls the CU=20
> and EPON technology "Subscriber access networks" in the=20
> document title, and then and inside the document there are=20
> phrases like:
> 67.1 Overview
> This clause provides information on building Ethernet=20
> subscriber access networks, also referred to as "Ethernet in=20
> the First Mile", or EFM networks.=20
>=20
> Given than "copper" when describing dot3 is ambiguous, then=20
> an additional adjective is needed. But with EPON, there is no=20
> ambiguity. Thus, I suggest the following module names:
>   DOT3-EPON-MIB (or DOT3-EFM-EPON-MIB)
>   DOT3-EFM-CU-MIB
>   DOT3-OAM-MIB=20
>=20
> Then have consistent descriptors for items defined in the MIB=20
> modules. For the lastest OAM and EPON modules, the prefixes=20
> are dot3Oam and dot3Epon (plus dot3Mpcp, dot3OmpE, etc).
> The CU module has prefixe emfCu.
>=20
> On Sun, 22 Jan 2006, Romascanu, Dan (Dan) wrote:
> > What is exactly the rationale for this request, David?=20
> >=20
> > The other MIB modules in the family are named EFM-COMMON-MIB and=20
> > EFM-CU-MIB. If we are to look for consistency, the names of the MIB=20
> > modules defined in this document should be EFM-EPON-MIB and=20
> > EFM-EPON-DEVICE-MIB.
> >=20
> > Regards,
> >=20
> > Dan
> > > -----Original Message-----
> > > From: David T. Perkins [mailto:dperkins@dsperkins.com]
> > > Sent: Friday, January 20, 2006 7:43 PM
> > > To: lior.khermosh@passave.com
> > > Cc: Romascanu, Dan (Dan); Hub MIB
> > > Subject: Re: [Hubmib] Response to EPON-MIB-04
> > >=20
> > > HI,
> > >=20
> > > Just saw one more small item. The MIB module is named=20
> > > "DOT3-EFM-EPON-MIB". I suggest that the name "DOT3-EPON-MIB"
> > > be used instead.
> > >=20
> > > Regards,
> > > /david t. perkins
>=20
> Regards,
> /david t. perkins
>=20
>=20

_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib



From hubmib-bounces@ietf.org Sun Jan 22 13:56:09 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F0kNl-0006Zz-LE; Sun, 22 Jan 2006 13:56:09 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1F0kNk-0006Zs-8j
	for hubmib@megatron.ietf.org; Sun, 22 Jan 2006 13:56:08 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09198
	for <hubmib@ietf.org>; Sun, 22 Jan 2006 13:54:38 -0500 (EST)
Received: from nj300815-ier2.net.avaya.com ([198.152.12.103])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F0kWv-00009X-8J
	for hubmib@ietf.org; Sun, 22 Jan 2006 14:05:38 -0500
Received: from tiere.net.avaya.com (tiere.net.avaya.com [198.152.12.100])
	by nj300815-ier2.net.avaya.com (Switch-3.1.7/Switch-3.1.7) with ESMTP
	id k0MIr4Ac014611
	for <hubmib@ietf.org>; Sun, 22 Jan 2006 13:53:04 -0500
Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com
	[135.64.105.51])
	by tiere.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id
	k0MIr0QH003415
	for <hubmib@ietf.org>; Sun, 22 Jan 2006 13:53:01 -0500 (EST)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Hubmib] Response to comments on OAM doc
Date: Sun, 22 Jan 2006 20:55:59 +0200
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F09E8C8DE@is0004avexu1.global.avaya.com>
Thread-Topic: [Hubmib] Response to comments on OAM doc
Thread-Index: AcYfGjickonnycvcRiq8/9B3UMqcQwAauhlA
From: "Romascanu, Dan \(Dan\)" <dromasca@avaya.com>
To: "David T. Perkins" <dperkins@dsperkins.com>, <hubmib@ietf.org>
X-Scanner: InterScan AntiVirus for Sendmail
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Content-Transfer-Encoding: quoted-printable
Cc: MSquire@HatterasNetworks.com
X-BeenThere: hubmib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Ethernet Interfaces an Hub MIB WG <hubmib.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/hubmib>,
	<mailto:hubmib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:hubmib@ietf.org>
List-Help: <mailto:hubmib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/hubmib>,
	<mailto:hubmib-request@ietf.org?subject=subscribe>
Sender: hubmib-bounces@ietf.org
Errors-To: hubmib-bounces@ietf.org


Thanks to David for reviewing the comments. It looks like we have
agreement on the majority of the items, and I would suggest that Matt
performs the necessary edits as soon as possible, so that we can submit
a revised version ready to go through a WGLC and then IESG submission.

Regards,

Dan

=20
=20

> -----Original Message-----
> From: hubmib-bounces@ietf.org=20
> [mailto:hubmib-bounces@ietf.org] On Behalf Of David T. Perkins
> Sent: Saturday, January 21, 2006 2:28 AM
> To: hubmib@ietf.org
> Cc: Romascanu, Dan (Dan); MSquire@HatterasNetworks.com
> Subject: [Hubmib] Response to comments on OAM doc
>=20
> HI,
>=20
> It looks like much progress, and maybe with the comments
> below incorroprated, the document will be ready for
> a new WG last call and IESG submission.
>=20


_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib



From hubmib-bounces@ietf.org Mon Jan 23 02:06:27 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F0vmU-0001nY-Uy; Mon, 23 Jan 2006 02:06:26 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1F0vmS-0001md-Tb
	for hubmib@megatron.ietf.org; Mon, 23 Jan 2006 02:06:25 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA23066
	for <hubmib@ietf.org>; Mon, 23 Jan 2006 02:04:54 -0500 (EST)
Received: from co300216-ier2.net.avaya.com ([198.152.13.103])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F0vvi-00039g-U8
	for hubmib@ietf.org; Mon, 23 Jan 2006 02:16:01 -0500
Received: from tierw.net.avaya.com (h198-152-13-100.avaya.com [198.152.13.100])
	by co300216-ier2.net.avaya.com (Switch-3.1.7/Switch-3.1.7) with ESMTP
	id k0N63oZv031250
	for <hubmib@ietf.org>; Mon, 23 Jan 2006 01:03:51 -0500
Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com
	[135.64.105.51])
	by tierw.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id
	k0N6p1Yj015342
	for <hubmib@ietf.org>; Mon, 23 Jan 2006 01:51:02 -0500 (EST)
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 23 Jan 2006 09:06:10 +0200
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F09E8C9A0@IS0004AVEXU1.global.avaya.com>
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
Thread-Topic: Response to EPON-MIB-04
Thread-Index: AcYds5ao9KFwth9MQMS8of6VLYNCDACNQ38A
From: "Romascanu, Dan \(Dan\)" <dromasca@avaya.com>
To: "David T. Perkins" <dperkins@dsperkins.com>, <lior.khermosh@passave.com>
X-Scanner: InterScan AntiVirus for Sendmail
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bacfc6c7290e34d410f9bc22b825ce96
Content-Transfer-Encoding: quoted-printable
Cc: Hub MIB <hubmib@ietf.org>
Subject: [Hubmib] RE: Response to EPON-MIB-04
X-BeenThere: hubmib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Ethernet Interfaces an Hub MIB WG <hubmib.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/hubmib>,
	<mailto:hubmib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:hubmib@ietf.org>
List-Help: <mailto:hubmib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/hubmib>,
	<mailto:hubmib-request@ietf.org?subject=subscribe>
Sender: hubmib-bounces@ietf.org
Errors-To: hubmib-bounces@ietf.org

David,

Thank you for the review and the latest comments.=20

Lior,

Can you please address David's questions?=20

I believe that David is asking for clarifications, maybe an example that
would clarify his question 1. This new text could expand Section 3
'Relationship of the EFM EPON MIB to other MIBs'. By the way, 'Relation
to other MIB Modules' would be a better name for this section.=20

With respect to David's question #2, the text 'Rows at the table are
created by direct SNMP management setting." seems wrong. David's
question is correct, if rows in these tables are created dynamically by
management operations on the specific table, you need to use "RowStatus"
objects for the specific table. If this was not the intention, the text
should be eliminated and you should mention in the DESCRIPTION clauses
in each table how each row shows up, maybe as result of operations
performed on other tables, or corresponding to existing ports on the
device, or something else.=20

I am also feeling very uncomfortable with holding discussions around a
non-submitted draft.  I would like to ask Lior to submit draft 04
immediately. If the issues cannot be clarified and a revised draft
submitted in the next couple of days, it can be as it was distributed on
the mailing list last December. =20

Regards,

Dan


=20
=20

> -----Original Message-----
> From: David T. Perkins [mailto:dperkins@dsperkins.com]=20
> Sent: Friday, January 20, 2006 9:01 AM
> To: lior.khermosh@passave.com
> Cc: Romascanu, Dan (Dan); Hub MIB
> Subject: Response to EPON-MIB-04
>=20
> HI,
>=20
> Comments on draft-ietf-hubmib-efm-epon-mib-04.txt - dtp:19-jan-2006
>=20
> The document is much improved. However, it is not yet ready=20
> for submission to the IESG. The changes introduced many=20
> grammar and some spelling errors (and a couple of formatting=20
> problems), which can be easily fixed. Unfortunately, there=20
> are a couple of fundamental issues that remain. These are:
>  1) if an "SNMP MIB walk" was done on the
>      a) IF table
>      b) bridge table
>      c) MAU table
>      d) stack table (and inverted stack table)
>      e) etherLike interfaces table
>      d) and tables defined in the MIB module
>    what would be the answers to the following questions for
>    OLTs and for ONUs (for both, assume that each has a 1Gig Eth
>    interface and an optical interface, and for the OLT, there
>    are 3 ONUs connected to the optical interface):
>      a) how many entries would be in the IF table
>      b) what would the values be for each column in the
>          IF table. That is, what are the values of the
>          following objects: ifIndex, ifDescr, ifType,
>           ifMtu, ifSpeed, ifPhysAddress, ifAdminStatus,
>           ifOperStatus, ifLastChange, ifInOctets, ifInUcastPkts,
>           ifInNUcastPkts, ifInDiscards, ifInErrors,=20
>           ifInUnknownProtos, ifOutOctets, ifOutUcastPkts,
>           ifOutNUcastPkts, ifOutDiscards, ifOutErrors,
>           ifOutQLen
>      c) how the values of the above objects determined?
>      d) what happens when the value of ifAdmin is set to
>          'up(1)', 'down(2)', and 'testing(3)'?
>      e) the table dot1dBasePortTable has the mapping of
>         bridge ports to interfaces (and "circuit" on that
>         interface). What would the values be for the
>         objects dot1dBasePortIfIndex and dot1dBasePortCircuit
>         when the OLT supported bridging? (By the way,
>         document "Definitions of Managed Objects for Bridges"
>         was recently updated and, thus, the refs should
>         have RFC 4188 and not 1493.)
>      f) how many entries would be in table ifMauTable,
>         and would be the value of columns in the table.
>      g) Are the stack and inverted stack tables used?
>         If so, show the stacking relationships.
>      h) How many entries are in the etherLike tables
>         dot3StatsTable, dot3CollTable, dot3PauseTable,
>         and dot3HCStatsTable and what would the values
>         be of columns in the tables.
>      i) How many entries would be in the tables defined
>         in this document, which are:
>         dot3MpcpGlobalTable, dot3MpcpParamTable,
>         dot3MpcpStatTable, dot3OmpEmulationTable,
>         dot3OmpEmulationStatTable, dot3EponFecTable,
>         dot3ExtPkgGlobalControlTable,
>         dot3ExtPkgControlTable, dot3ExtPkgQueueTable,
>         dot3ExtPkgQueueSetsTable and
>         dot3ExtPkgOptIfTable.
>  2) Which tables in the MIB module allow rows to be created
>     and or deleted, and if so, then how? (Note the the phrase
>     "Rows at the table are created by direct SNMP management
>     setting." is used in the DESCRIPTION for many tables.
>     However, there was no information provided as to what
>     this means. (I'm guessing that my original comments
>     were not completely understood. What I was asking for
>     was to include in the DESCRIPTION clause whether or
>     not an SNMP SET could be done to columns in a table
>     to create or delete a row, and if so, to provide the
>     details (or indicate the object definition where the
>     details were provided). For example, the TCP connection
>     table does not support SNMP SETs to create rows in
>     the table. Rows are created as TCP connections
>     are created by processes running on the system.
>     However, an SNMP SET can be done on object tcpConnState=20
>     with value 'deleteTCB(12)' to terminate a TCP
>     connection (which results in the row being deleted
>     from the table). There are plenty of examples of
>     using a "RowStatus" object to create and delete
>     rows in tables (see the SNMPv3 RFCs, such as RFC 3413).
>     In the RMON MIB modules, there are examples of
>     control tables and data tables. A row creation
>     (or deletion) in a control table results in
>     row creation (or row deletion) in data tables.
>     Describing how instances are created and deleted,
>     (by system operation or configuration, and/or
>     via management operations) is a key piece of
>     information for the DESCRIPTION clauses of
>     tables and rows.
>=20
> Until the above fundamental issues are resolved, it doesn't=20
> make a lot of sense to spend much time on other issues such=20
> as grouping and conformance.
>=20
> Note that I did spot a bunch of easy to fix items that I'm=20
> listing below:
>  section 1 - the text for the abstract is Ok. I just don't
>      get the term "registers" here.
>  section 1.1 - It's great to have a list of abbreviations.
>      a) However in documents that contain MIB modules, typically
>      the modules are extracted, and thus all the explanatory
>      is not available. To help, there is a little redundancy
>      that is added to the document of putting KEY definitions
>      and terms in the DESCRIPTION clause for the MIB module.
>      b) I didn't check to see if all the abbreviations were
>      actually used. If not, then I would remove them.
>      c) I thought CPE was customer premises equipment =20
> section 1.2.3 - I was confused. Does "Gate messages"
>      start a new subsection?
>  section 3 (3.1-3.4) - This is still a little skimpy!
>      Look at RFC 2863, sections 3.1.1-3.1.18 & 4. Also
>      look at RFC 3635, section 3.2 and contained subsections.
>  section 4 - tables 1 thru 3. The column head should be
>      IEEE802.3ah attribute and not "object"
>  In the MIB module, there are several ASN.1 comments that
>      that are used to group the definitions. They start
>      out with phrase "Editor's note:". I believe the
>      grouping is useful, but I'd drop the "Editor's note:"
>      phrase. Note the first one is slightly out of order.
>      It should be moved to immediately before the
>      definition of OID dot3EponMpcpObjects.
>  Object dot3MpcpID - the DESCRIPTION needs to be translated
>      from GDMO speak to something meaningful in SMIv2.
>      (I commented on this before, and still don't see the
>      usefulness of the object!)
>  Do the objects dot3MpcpOperStatus and dot3MpcpAdminStatus
>      ever have different values. If not, then you should
>      have one object.
>  I really don't follow whether or not you can create LLIDs
>      via SNMP. It doesn't seem possible to me, just like
>      you can't create TCP connections. Thus, I don't understand
>      the object dot3LinkIndex. (And note: a table that
>      allows row creation uses "read-create" (and not "read-write")
>      for all writable objects in the table.)  Entries in=20
> parallel tables - I asked you to describe the
>      expected number of entries in tables. However, many of
>      the tables in the MIB module are related, and the text
>      was just copied. Instead, if there is a "base table"
>      that determines the number of entries, and additional
>      tables that have additional info, you should say
>      something like "The rows in this table are match the
>      rows in table X".
>  Transient condition in table dot3MpcpParamTable - it appears
>      that this table tries to capture the transient values
>      during the time a OLT and ONU are setting up a relationship
>      and determining an LLID. Is this a long enough running
>      activity that it can be seen, and what LLID value is
>      used durring negotiation (can't it change)?
>  Object dot3OmpEmulationID - the DESCRIPTION needs to be translated
>      from GDMO speak to something meaningful in SMIv2.
>      (I commented on this before, and still don't see the
>      usefulness of the object!)
>  Enum names in DESCRIPTION for object dot3ExtPkgObjectPowerDown -
>      The enum names start with lower-case letters and not
>      upper-case.
>  Queues - I really don't understand the queues. Could some
>      intro text be added.
>  Indexing - this is somewhat subjective. I don't believe that
>      it is proper to define an object in one table (which is not
>      an index in that table) and use it for an index in another
>      table. This is done in the queue tables and object dot3LinkIndex.
>=20
>=20
> NOTE: this review was not complete. I didn't try to compile=20
> the MIB module or run the document through the nit checker.=20
> Also, I didn't look at the compliances.
>=20
> -- that's it
>=20
> Regards,
> /david t. perkins =20
>=20
>=20
>=20

_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib



From hubmib-bounces@ietf.org Mon Jan 23 09:30:37 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F12iL-0003xz-3O; Mon, 23 Jan 2006 09:30:37 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1F12iJ-0003wd-O3
	for hubmib@megatron.ietf.org; Mon, 23 Jan 2006 09:30:36 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA22781
	for <hubmib@ietf.org>; Mon, 23 Jan 2006 09:29:04 -0500 (EST)
Received: from mailserv.hatterasnetworks.com ([72.15.200.20])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F12p8-0007zF-EM
	for hubmib@ietf.org; Mon, 23 Jan 2006 09:37:38 -0500
content-class: urn:content-classes:message
Subject: RE: [Hubmib] Response to comments on OAM doc
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 23 Jan 2006 09:26:41 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
Message-ID: <8052E2EA753D144EB906B7A7AA39971403FC3B0B@mailserv.hatteras.com>
Thread-Topic: [Hubmib] Response to comments on OAM doc
Thread-Index: AcYfGjickonnycvcRiq8/9B3UMqcQwAaLscwAClMMaA=
From: "Matt Squire" <MSquire@HatterasNetworks.com>
To: "Romascanu, Dan \(Dan\)" <dromasca@avaya.com>,
	"David T. Perkins" <dperkins@dsperkins.com>, <hubmib@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
Content-Transfer-Encoding: quoted-printable
Cc: 
X-BeenThere: hubmib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Ethernet Interfaces an Hub MIB WG <hubmib.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/hubmib>,
	<mailto:hubmib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:hubmib@ietf.org>
List-Help: <mailto:hubmib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/hubmib>,
	<mailto:hubmib-request@ietf.org?subject=subscribe>
Sender: hubmib-bounces@ietf.org
Errors-To: hubmib-bounces@ietf.org



> >      dot3OamMaxOamPduSize OBJECT-TYPE
> >        SYNTAX      Integer32 (64..1522)
> > ]] This should be Unsigned32.
> > ]] Also, is 1522 really the max?
> >
> >
> > MBS:  I'll change to Unsigned32 though its not clear to me why thats
> > better.  The maximum value, as defined in [802.3ah] is equal the
> > maximum untagged frame size (which is undergoing change in 802.3 as
we
> > speak).  I'd like to put a variable in here that ties it to the
> > maxUntaggedFrameSize, but I don't know what that variable would be.
> > Numerically, it should currently be 1518, not 1522.
> >
>=20
> See RFC 4181, Section 4.6.1.1 for the reason of using Unsigned32.
>=20
> Concerning the new max PDU size. It is true that IEEE 802.3as is
working
> at a frame extension that would take the max frame size to a new
value,
> around 2k I believe. We should be able to liaison with them and
> determine if they already can tell us what is this value.
>=20
> However, my question is whether EFM OAM is supposed to use the new max
> size. It was designed by the time a non-tagged frame was (actually
still
> is by today) 1518. Is there any text that says what the max size of a
> OAM PDU can be - 1518, or the max size of the day?
>=20

The text in .3 says that the maximum size of an OAMPDU is the
maxUntaggedFrameSize (see Table 57-9).  As I think about it more, the
maximum size of an untagged frame is not changing, just the name.
According to the latest draft of 802.3as, Table 57-9 changes
maxUntaggedFrameSize to maxBasicFrameSize, which is still defined as
1518. =20

I don't think a liaison is necessary - the 802.3as draft is pretty
clear. =20

- Matt



_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib



From hubmib-bounces@ietf.org Mon Jan 23 09:33:22 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F12l0-0004U3-BH; Mon, 23 Jan 2006 09:33:22 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1F12ky-0004Sm-3X
	for hubmib@megatron.ietf.org; Mon, 23 Jan 2006 09:33:20 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA23271
	for <hubmib@ietf.org>; Mon, 23 Jan 2006 09:31:49 -0500 (EST)
Received: from mailserv.hatterasnetworks.com ([72.15.200.20])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F12uK-0008Ma-PI
	for hubmib@ietf.org; Mon, 23 Jan 2006 09:43:01 -0500
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 23 Jan 2006 09:32:07 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
Message-ID: <8052E2EA753D144EB906B7A7AA39971403FC3B10@mailserv.hatteras.com>
Thread-Topic: Response to comments on OAM doc
Thread-Index: AcYeIdXnXE5uOqX2QpG2WLZY2l+JsgBX5nKQACn2bAA=
From: "Matt Squire" <MSquire@HatterasNetworks.com>
To: "Romascanu, Dan \(Dan\)" <dromasca@avaya.com>,
	"David T. Perkins" <dperkins@dsperkins.com>, <hubmib@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 25620135586de10c627e3628c432b04a
Content-Transfer-Encoding: quoted-printable
Cc: 
Subject: [Hubmib] RE: Response to comments on OAM doc
X-BeenThere: hubmib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Ethernet Interfaces an Hub MIB WG <hubmib.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/hubmib>,
	<mailto:hubmib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:hubmib@ietf.org>
List-Help: <mailto:hubmib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/hubmib>,
	<mailto:hubmib-request@ietf.org?subject=subscribe>
Sender: hubmib-bounces@ietf.org
Errors-To: hubmib-bounces@ietf.org


I would personally prefer to have the OAM MIB name be DOT3 rather than
EFM, for two reasons:

1) The other non-PHY specific functions seem to be named this way. =20
2) I already made the change in a working draft:)

Not a strong feeling by any means, but it seems more appropriate. =20

- Matt


> -----Original Message-----
> From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com]
> Sent: Sunday, January 22, 2006 1:36 PM
> To: David T. Perkins; hubmib@ietf.org
> Cc: Matt Squire
> Subject: RE: Response to comments on OAM doc
>=20
> (speaking as a contributor)
>=20
> Grrrrr ... I did not want to enter into a naming discussion at this
> stage, but it looks like we got into one anyway.
>=20
> There is no overall convention for names of hubmib MIB modules to be
> prefixed by DOT3. If there is a consistency to be reached, I would
> rather aim all EFM MIB module names to be prefixed by EFM.
>=20
> Thus, the module names I would recommend to be used in the four
> documents are:
>=20
> EFM-OAM-MIB
> EFM-CU-MIB
> EFM-EPON-MIB
> EFM-EPON-DEVICE-MIB
>=20
> The descriptors associated with the module identity and the other
> descriptors of MIB objects within the MIB modules should be a lower
case
> version of the module name prefix without hyphenation of course, as
> recommended in Annex C of RFC 4181.
>=20
> Regards,
>=20
> Dan
>=20
>=20
>=20
>=20
>=20
> > -----Original Message-----
> > From: David T. Perkins [mailto:dperkins@dsperkins.com]
> >
> > 6.   MIB Definition
> >
> >   EFM-COMMON-MIB DEFINITIONS ::=3D BEGIN
> >
> > ]] This module name doesn't follow the naming conventions
> > ]] in the [MIBguidelines] document. However, I can't determine
> > ]] if it should be DOT3-OAM-MIB, or "EFM-OAM-MIB".
> >
> > MBS: It should be DOT3-OAM-MIB to me, so that's what I'll
> > change it to.
> >
> >   <<text deleted>>
> >
> >      efmOamMIB MODULE-IDENTITY
> >
> > ]] Not sure if should be efmOamMIB or dot3OamMIB
> >
> > MBS: Changed to dot3OamMIB
> >
> >


_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib



From hubmib-bounces@ietf.org Mon Jan 23 09:38:39 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F12q6-00058u-VB; Mon, 23 Jan 2006 09:38:38 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1F12q5-00058Z-0V
	for hubmib@megatron.ietf.org; Mon, 23 Jan 2006 09:38:37 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA23633
	for <hubmib@ietf.org>; Mon, 23 Jan 2006 09:37:06 -0500 (EST)
Received: from nj300815-ier2.net.avaya.com ([198.152.12.103])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F12zR-00005L-Ix
	for hubmib@ietf.org; Mon, 23 Jan 2006 09:48:17 -0500
Received: from tiere.net.avaya.com (tiere.net.avaya.com [198.152.12.100])
	by nj300815-ier2.net.avaya.com (Switch-3.1.7/Switch-3.1.7) with ESMTP
	id k0NEZUHf017704
	for <hubmib@ietf.org>; Mon, 23 Jan 2006 09:35:30 -0500
Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com
	[135.64.105.51])
	by tiere.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id
	k0NEZTQH013194
	for <hubmib@ietf.org>; Mon, 23 Jan 2006 09:35:30 -0500 (EST)
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
Date: Mon, 23 Jan 2006 16:38:28 +0200
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F09E8CE03@IS0004AVEXU1.global.avaya.com>
Thread-Topic: Response to comments on OAM doc
Thread-Index: AcYeIdXnXE5uOqX2QpG2WLZY2l+JsgBX5nKQACn2bAAAAEwusA==
From: "Romascanu, Dan \(Dan\)" <dromasca@avaya.com>
To: "Matt Squire" <MSquire@HatterasNetworks.com>,
	"David T. Perkins" <dperkins@dsperkins.com>, <hubmib@ietf.org>
X-Scanner: InterScan AntiVirus for Sendmail
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 14582b0692e7f70ce7111d04db3781c8
Content-Transfer-Encoding: quoted-printable
Cc: 
Subject: [Hubmib] RE: Response to comments on OAM doc
X-BeenThere: hubmib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Ethernet Interfaces an Hub MIB WG <hubmib.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/hubmib>,
	<mailto:hubmib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:hubmib@ietf.org>
List-Help: <mailto:hubmib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/hubmib>,
	<mailto:hubmib-request@ietf.org?subject=subscribe>
Sender: hubmib-bounces@ietf.org
Errors-To: hubmib-bounces@ietf.org

I have no stronger feelings either. Please go ahead as your non-strong
feelings dictate :-)

Regards,

Dan


=20
=20

> -----Original Message-----
> From: Matt Squire [mailto:MSquire@HatterasNetworks.com]=20
> Sent: Monday, January 23, 2006 4:32 PM
> To: Romascanu, Dan (Dan); David T. Perkins; hubmib@ietf.org
> Subject: RE: Response to comments on OAM doc
>=20
>=20
> I would personally prefer to have the OAM MIB name be DOT3=20
> rather than EFM, for two reasons:
>=20
> 1) The other non-PHY specific functions seem to be named this way. =20
> 2) I already made the change in a working draft:)
>=20
> Not a strong feeling by any means, but it seems more appropriate. =20
>=20
> - Matt
>=20
>=20
> > -----Original Message-----
> > From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com]
> > Sent: Sunday, January 22, 2006 1:36 PM
> > To: David T. Perkins; hubmib@ietf.org
> > Cc: Matt Squire
> > Subject: RE: Response to comments on OAM doc
> >=20
> > (speaking as a contributor)
> >=20
> > Grrrrr ... I did not want to enter into a naming discussion at this=20
> > stage, but it looks like we got into one anyway.
> >=20
> > There is no overall convention for names of hubmib MIB=20
> modules to be=20
> > prefixed by DOT3. If there is a consistency to be reached, I would=20
> > rather aim all EFM MIB module names to be prefixed by EFM.
> >=20
> > Thus, the module names I would recommend to be used in the four=20
> > documents are:
> >=20
> > EFM-OAM-MIB
> > EFM-CU-MIB
> > EFM-EPON-MIB
> > EFM-EPON-DEVICE-MIB
> >=20
> > The descriptors associated with the module identity and the other=20
> > descriptors of MIB objects within the MIB modules should be a lower
> case
> > version of the module name prefix without hyphenation of course, as=20
> > recommended in Annex C of RFC 4181.
> >=20
> > Regards,
> >=20
> > Dan
> >=20
> >=20
> >=20
> >=20
> >=20
> > > -----Original Message-----
> > > From: David T. Perkins [mailto:dperkins@dsperkins.com]
> > >
> > > 6.   MIB Definition
> > >
> > >   EFM-COMMON-MIB DEFINITIONS ::=3D BEGIN
> > >
> > > ]] This module name doesn't follow the naming conventions=20
> ]] in the=20
> > > [MIBguidelines] document. However, I can't determine ]]=20
> if it should=20
> > > be DOT3-OAM-MIB, or "EFM-OAM-MIB".
> > >
> > > MBS: It should be DOT3-OAM-MIB to me, so that's what I'll=20
> change it=20
> > > to.
> > >
> > >   <<text deleted>>
> > >
> > >      efmOamMIB MODULE-IDENTITY
> > >
> > > ]] Not sure if should be efmOamMIB or dot3OamMIB
> > >
> > > MBS: Changed to dot3OamMIB
> > >
> > >
>=20
>=20

_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib



