
From dromasca@avaya.com  Mon Mar  2 05:19:28 2009
Return-Path: <dromasca@avaya.com>
X-Original-To: opsawg@core3.amsl.com
Delivered-To: opsawg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7492728C204 for <opsawg@core3.amsl.com>; Mon,  2 Mar 2009 05:19:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.768
X-Spam-Level: 
X-Spam-Status: No, score=-1.768 tagged_above=-999 required=5 tests=[AWL=-0.654, BAYES_00=-2.599, HTML_FONT_FACE_BAD=0.884, HTML_MESSAGE=0.001, J_CHICKENPOX_12=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rxROBDCAB57J for <opsawg@core3.amsl.com>; Mon,  2 Mar 2009 05:19:27 -0800 (PST)
Received: from nj300815-nj-outbound.net.avaya.com (nj300815-nj-outbound.net.avaya.com [198.152.12.100]) by core3.amsl.com (Postfix) with ESMTP id DF5A928C1F9 for <opsawg@ietf.org>; Mon,  2 Mar 2009 05:19:02 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.38,289,1233550800";  d="scan'208,217";a="153897168"
Received: from unknown (HELO nj300815-nj-erheast.avaya.com) ([198.152.6.5]) by nj300815-nj-outbound.net.avaya.com with ESMTP; 02 Mar 2009 08:19:24 -0500
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14]) by nj300815-nj-erheast-out.avaya.com with ESMTP; 02 Mar 2009 08:19:24 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C99B39.7D682A66"
Date: Mon, 2 Mar 2009 14:19:15 +0100
Message-ID: <EDC652A26FB23C4EB6384A4584434A0401454160@307622ANEX5.global.avaya.com>
In-Reply-To: <013a01c99b34$14984d20$3682990a@h3c.huawei3com.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [OPSAWG]  I would like to extend ENTITY-MIB (rfc4133)...
Thread-Index: AcmbNC7J4Rokl089RruCZHLUwKWGywABHEXA
References: <013301c997d4$434f4820$3682990a@h3c.huawei3com.com> <EDC652A26FB23C4EB6384A4584434A0401453B85@307622ANEX5.global.avaya.com> <013a01c99b34$14984d20$3682990a@h3c.huawei3com.com>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Shimin Ban" <banshimin@h3c.com>
Cc: opsawg@ietf.org
Subject: Re: [OPSAWG] I would like to extend ENTITY-MIB (rfc4133)...
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Mar 2009 13:19:28 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01C99B39.7D682A66
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

So, the discussion has been reduced to the need of representing in an
Entity MIB extension the location and other information that allows for
a device panel representation in a management application.=20
=20
My personal opinion as a contributor is that this information is not
important for standard management. Graphical representations are not
essential or of high priority in the management of devices, and this is
why they were not considered until now for standard management but left
as vendors-specific extensions. Also, I am not sure that the MIB of the
devices is the best vehicle for transferring such information which is
static in nature. =20
=20
This is my opinion - other opinions are certainly welcome, and folks
interested in such work are welcome to write an individual submission
Internet-Draft.=20
=20
Regards,
=20
Dan
=20


________________________________

	From: Shimin Ban [mailto:banshimin@h3c.com]=20
	Sent: Monday, March 02, 2009 2:41 PM
	To: Romascanu, Dan (Dan)
	Cc: opsawg@ietf.org
	Subject: Re: [OPSAWG] I would like to extend ENTITY-MIB
(rfc4133)[DR] ee ...
=09
=09
	Hello Dan,
	Thank you very much. Please see in-line, too.
	=20
	Cheers
	Shimin Ban

		----- Original Message -----=20
		From: Romascanu, Dan (Dan) <mailto:dromasca@avaya.com> =20
		To: Shimin Ban <mailto:banshimin@h3c.com>  ;
opsawg@ietf.org=20
		Sent: Thursday, February 26, 2009 9:40 PM
		Subject: RE: [OPSAWG] I would like to extend ENTITY-MIB
(rfc4133)...

		Hi Shimin Ban,
		=20
		Please see in-line.=20
		=20
		Regards,
		=20
		Dan
		=20
	=09
	=09

________________________________

			From: opsawg-bounces@ietf.org
[mailto:opsawg-bounces@ietf.org] On Behalf Of Shimin Ban
			Sent: Thursday, February 26, 2009 7:37 AM
			To: opsawg@ietf.org
			Subject: [OPSAWG] I would like to extend
ENTITY-MIB (rfc4133)...
		=09
		=09
			Hello,
			I would like to extend RFC4133. I'ld like to add
the following information to entity MIB:
			=20
			(1) The absolute position of the entity in its
parent
			According to the absolute position and the
information provided by entity MIB, the NMS can display the panel of
devices easily regardless of vendor.
			The customer could monitor the status of the
entity easily through the panel. But the entity MIB does not provide the
entity status information.
			[DR] You probably need to provide more
information about what you mean by 'absolute position'. Is this about
order (like first card, second card, etc.) or even more - like exact
coordinates on a panel drawing?=20
			=20
			Depending on your answers other folks writing
similar applications could comment if representing such information in
the MIB of the device is important enough to be included in an extension
of the Entity MIB.=20
			=20
			[Ban] Yes. The 'absolute position' is the
entity's exact coordinates in its parent picture.
			You know, to monitor the entities of the device
easily most of NMS provides device panel management. How to draw the
panel? We have to know the 'absolute position' of every displayed
entity. For example, we can store the information into a XML file (see
the follwing).  But it's not a good method. To manage a device, we have
to know its 'absolute position' information, or else it couldn't be
managed.=20
			So I think, why not store the information into
the managed devices? Entity-MIB has provided the relative position, but
it's not enough. We can add 'entity picture name', 'entity width',
'entity height', 'entity angle', 'entity X position', 'entity Y
position', 'isVisible' ... information to Entity-MIB.=20
			With the above information and pictures
downloaded from vendor's website, we could draw the panel of devices
easily regardless of vendor.
			Let me know if you have some good idea about
drawing the device panel. Thank you in advance.
			=20
			=20
			For example, S2104 is a simple switch. It only
has 4 ports. The XML file could be:
			                <Entity name=3D"PANE_S2104"
w=3D"835" h=3D"116", imgname=3D"s2104.gif">
			                    <ElementList size=3D"1">
			                        <Element
name=3D"FRAME_S2104" type=3D"Frame" angle=3D"0" visible=3D"false" =
x=3D"0" y=3D"0"
w=3D"835" h=3D"116" />
			                    </ElementList>
			                </Entity>
		=09
			                <Entity name=3D"FRAME_S2104"
w=3D"835" h=3D"116">
			                    <ElementList size=3D"1">
			                        <Element
name=3D"MODULE1_S2104" type=3D"MODULE1" angle=3D"0" visible=3D"false" =
x=3D"0"
y=3D"0" w=3D"835" h=3D"116" />
			                    </ElementList>
			                </Entity>
			=20
			                <Entity name=3D"MODULE1_S2104"
w=3D"835" h=3D"116">
			                    <ElementList size=3D"1">
			                        <Element
name=3D"MODULE2_S2104" type=3D"MODULE2" angle=3D"0" visible=3D"false" =
x=3D"0"
y=3D"0" w=3D"835" h=3D"116" />
			                    </ElementList>
			                </Entity>
			=20
			                <Entity name=3D"MODULE2_S2104"
w=3D"835" h=3D"116">
			                    <ElementList size=3D"5">
			                        <Element name=3D"PORT"
type=3D"10or100M" angle=3D"180" visible=3D"true" x=3D"168" y=3D"64" =
w=3D"20" h=3D"20"
/>
			                        <Element name=3D"PORT"
type=3D"10or100M" angle=3D"180" visible=3D"true" x=3D"240" y=3D"64" =
w=3D"20" h=3D"20"
/>
			                        <Element name=3D"PORT"
type=3D"10or100M" angle=3D"180" visible=3D"true" x=3D"312" y=3D"64" =
w=3D"20" h=3D"20"
/>
			                        <Element name=3D"PORT"
type=3D"10or100M" angle=3D"180" visible=3D"true" x=3D"384" y=3D"64" =
w=3D"20" h=3D"20"
/>
			                    </ElementList>
			                </Entity>
			=20
			=20
			=20
			(2) The status of the entity
			[DR] Is the information in the Entity State MIB
(RFC 4268) not sufficient?=20
			[Ban] Yes, it's enough. I didn't know the mib.
			=20
			(3) The other important information of CPU,
Sensor, disk, powersupply etc.
			[DR] Is the information in the Entity Sensor MIB
(RFC 3433)  not sufficient?=20
			[Ban] Yes, it's enough. I didn't know the mib.
			=20
			Can the ENTITY-MIB be extended? What needs to
happen?=20
			[DR] The OPSAWG can be a home for working on
such extensions if there is interest here. Let us see what other people
think.=20
			=20
			Thank you very much.
			=20
			Cheers
			Shimin Ban
			=20
			=20
			=20


------_=_NextPart_001_01C99B39.7D682A66
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.2900.3492" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><SPAN class=3D965051313-02032009><FONT face=3DArial color=3D#0000ff =

size=3D2><STRONG><EM>So, the discussion has been reduced to the need of=20
representing in an Entity MIB extension the location and other =
information that=20
allows for a device panel representation in a management application.=20
</EM></STRONG></FONT></SPAN></DIV>
<DIV><SPAN class=3D965051313-02032009><STRONG><EM><FONT face=3DArial =
color=3D#0000ff=20
size=3D2></FONT></EM></STRONG></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D965051313-02032009><STRONG><EM><FONT face=3DArial =
color=3D#0000ff=20
size=3D2>My personal opinion as a contributor is that this information =
is not=20
important for standard management. Graphical representations are not =
essential=20
or of high priority in the management of devices, and this is why they =
were not=20
considered until now for standard management but left as =
vendors-specific=20
extensions. Also, I am not sure that the MIB of the devices is the best =
vehicle=20
for transferring such information which is static in nature.&nbsp;=20
</FONT></EM></STRONG></SPAN></DIV>
<DIV><SPAN class=3D965051313-02032009><STRONG><EM><FONT face=3DArial =
color=3D#0000ff=20
size=3D2></FONT></EM></STRONG></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D965051313-02032009><STRONG><EM><FONT face=3DArial =
color=3D#0000ff=20
size=3D2>This is my opinion - other opinions are certainly welcome, and =
folks=20
interested in such work are welcome to write an individual submission=20
Internet-Draft. </FONT></EM></STRONG></SPAN></DIV>
<DIV><SPAN class=3D965051313-02032009><STRONG><EM><FONT face=3DArial =
color=3D#0000ff=20
size=3D2></FONT></EM></STRONG></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D965051313-02032009><STRONG><EM><FONT face=3DArial =
color=3D#0000ff=20
size=3D2>Regards,</FONT></EM></STRONG></SPAN></DIV>
<DIV><SPAN class=3D965051313-02032009></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D965051313-02032009><STRONG><EM><FONT face=3DArial =
color=3D#0000ff=20
size=3D2>Dan</FONT></EM></STRONG></SPAN></DIV>
<DIV><SPAN class=3D965051313-02032009><STRONG><EM><FONT face=3DArial =
color=3D#0000ff=20
size=3D2></FONT></EM></STRONG></SPAN>&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><FONT size=3D2><B>From:</B> Shimin Ban=20
  [mailto:banshimin@h3c.com] <BR><B>Sent:</B> Monday, March 02, 2009 =
2:41=20
  PM<BR><B>To:</B> Romascanu, Dan (Dan)<BR><B>Cc:</B>=20
  opsawg@ietf.org<BR><B>Subject:</B> Re: [OPSAWG] I would like to extend =

  ENTITY-MIB (rfc4133)<SPAN class=3D965051313-02032009><STRONG><EM><FONT =

  face=3DArial=20
  =
color=3D#0000ff>[DR]&nbsp;ee&nbsp;</FONT></EM></STRONG></SPAN>...<BR></FO=
NT></FONT><BR></DIV>
  <DIV></DIV>
  <DIV><FONT face=3D&#23435;&#20307; size=3D2>Hello Dan,</FONT></DIV>
  <DIV><FONT face=3D&#23435;&#20307; size=3D2>Thank you very much. =
Please see in-line,=20
  too.</FONT></DIV>
  <DIV><FONT face=3D&#23435;&#20307; size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3D&#23435;&#20307; size=3D2>Cheers</FONT></DIV>
  <DIV><FONT face=3D&#23435;&#20307; size=3D2>Shimin Ban</FONT></DIV>
  <BLOCKQUOTE dir=3Dltr=20
  style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
    <DIV style=3D"FONT: 9pt &#23435;&#20307;">----- Original Message =
----- </DIV>
    <DIV=20
    style=3D"BACKGROUND: #e4e4e4; FONT: 9pt &#23435;&#20307;; =
font-color: black"><B>From:</B> <A=20
    title=3Ddromasca@avaya.com =
href=3D"mailto:dromasca@avaya.com">Romascanu, Dan=20
    (Dan)</A> </DIV>
    <DIV style=3D"FONT: 9pt &#23435;&#20307;"><B>To:</B> <A =
title=3Dbanshimin@h3c.com=20
    href=3D"mailto:banshimin@h3c.com">Shimin Ban</A> ; <A =
title=3Dopsawg@ietf.org=20
    href=3D"mailto:opsawg@ietf.org">opsawg@ietf.org</A> </DIV>
    <DIV style=3D"FONT: 9pt &#23435;&#20307;"><B>Sent:</B> Thursday, =
February 26, 2009 9:40=20
    PM</DIV>
    <DIV style=3D"FONT: 9pt &#23435;&#20307;"><B>Subject:</B> RE: =
[OPSAWG] I would like to=20
    extend ENTITY-MIB (rfc4133)...</DIV>
    <DIV><BR></DIV>
    <DIV><SPAN class=3D719183313-26022009><FONT face=3DArial =
color=3D#0000ff=20
    size=3D2><STRONG><EM>Hi Shimin =
Ban,</EM></STRONG></FONT></SPAN></DIV>
    <DIV><SPAN class=3D719183313-26022009><STRONG><EM><FONT face=3DArial =

    color=3D#0000ff size=3D2></FONT></EM></STRONG></SPAN>&nbsp;</DIV>
    <DIV><SPAN class=3D719183313-26022009><STRONG><EM><FONT face=3DArial =

    color=3D#0000ff size=3D2>Please see in-line. =
</FONT></EM></STRONG></SPAN></DIV>
    <DIV><SPAN class=3D719183313-26022009><STRONG><EM><FONT face=3DArial =

    color=3D#0000ff size=3D2></FONT></EM></STRONG></SPAN>&nbsp;</DIV>
    <DIV><SPAN class=3D719183313-26022009><STRONG><EM><FONT face=3DArial =

    color=3D#0000ff size=3D2>Regards,</FONT></EM></STRONG></SPAN></DIV>
    <DIV><SPAN class=3D719183313-26022009><STRONG><EM><FONT face=3DArial =

    color=3D#0000ff size=3D2></FONT></EM></STRONG></SPAN>&nbsp;</DIV>
    <DIV><SPAN class=3D719183313-26022009><STRONG><EM><FONT face=3DArial =

    color=3D#0000ff size=3D2>Dan</FONT></EM></STRONG></SPAN></DIV>
    <DIV><SPAN class=3D719183313-26022009><STRONG><EM><FONT face=3DArial =

    color=3D#0000ff=20
    size=3D2></FONT></EM></STRONG></SPAN>&nbsp;</DIV><STRONG><EM><FONT =
face=3DArial=20
    color=3D#0000ff size=3D2></FONT></EM></STRONG><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> <A=20
      =
href=3D"mailto:opsawg-bounces@ietf.org">opsawg-bounces@ietf.org</A>=20
      [mailto:opsawg-bounces@ietf.org] <B>On Behalf Of </B>Shimin=20
      Ban<BR><B>Sent:</B> Thursday, February 26, 2009 7:37 =
AM<BR><B>To:</B> <A=20
      =
href=3D"mailto:opsawg@ietf.org">opsawg@ietf.org</A><BR><B>Subject:</B>=20
      [OPSAWG] I would like to extend ENTITY-MIB=20
      (rfc4133)...<BR></FONT><BR></DIV>
      <DIV></DIV>
      <DIV><FONT size=3D2>Hello,</FONT></DIV>
      <DIV><FONT size=3D2>I would&nbsp;like to extend RFC4133. I'ld like =
to add=20
      the following information to entity MIB:</FONT></DIV>
      <DIV><FONT size=3D2></FONT>&nbsp;</DIV>
      <DIV><FONT size=3D2>(1) The absolute position of the entity in its =

      parent</FONT></DIV>
      <DIV><FONT size=3D2>According to the absolute position and the =
information=20
      provided by entity MIB, the NMS can display the panel of devices =
easily=20
      regardless of vendor.</FONT></DIV>
      <DIV><FONT size=3D2>The customer could monitor the status of the =
entity=20
      easily through the panel. But the entity MIB does not provide the =
entity=20
      status information.<BR><SPAN =
class=3D719183313-26022009><STRONG><EM><FONT=20
      face=3DArial color=3D#0000ff>[DR]&nbsp;You probably need to =
provide more=20
      information about what you mean by 'absolute position'. Is this =
about=20
      order (like first card, second card, etc.) or even more - like =
exact=20
      coordinates on a panel drawing? =
</FONT></EM></STRONG></SPAN></FONT></DIV>
      <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
      =
class=3D719183313-26022009><STRONG><EM></EM></STRONG></SPAN></FONT>&nbsp;=
</DIV>
      <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
      class=3D719183313-26022009><STRONG><EM>Depending on your answers =
other=20
      folks&nbsp;writing similar applications&nbsp;could comment if =
representing=20
      such information in the MIB of the device is important enough to =
be=20
      included in an extension of the Entity MIB.=20
      </EM></STRONG></SPAN></FONT></DIV>
      <DIV><FONT face=3DArial color=3D#008000 size=3D2><SPAN=20
      class=3D719183313-26022009><STRONG><EM><SPAN=20
      =
class=3D719183313-26022009><STRONG><EM></EM></STRONG></SPAN></EM></STRONG=
></SPAN></FONT>&nbsp;</DIV>
      <DIV><FONT face=3DArial color=3D#008000 size=3D2><SPAN=20
      class=3D719183313-26022009><STRONG><EM><SPAN=20
      class=3D719183313-26022009><STRONG><EM>[Ban] Yes. The 'absolute =
position' is=20
      the entity's exact coordinates in its parent=20
      picture.</EM></STRONG></SPAN></EM></STRONG></SPAN></FONT></DIV>
      <DIV><FONT face=3DArial color=3D#008000 size=3D2><SPAN=20
      class=3D719183313-26022009><STRONG><EM><SPAN=20
      class=3D719183313-26022009><STRONG><EM>You know, to monitor the =
entities of=20
      the device easily most of NMS provides device panel management.=20
      </EM></STRONG></SPAN></EM></STRONG></SPAN></FONT><FONT =
face=3DArial=20
      color=3D#008000 size=3D2><SPAN =
class=3D719183313-26022009><STRONG><EM><SPAN=20
      class=3D719183313-26022009><STRONG><EM>How to draw the panel? We =
have to=20
      know the 'absolute position' of every displayed entity. For =
example, we=20
      can store the information into a XML file (see the =
follwing).&nbsp; But=20
      it's not a good method. To manage a device, we have to know its =
'absolute=20
      position' information, or else it couldn't be managed.=20
      </EM></STRONG></SPAN></EM></STRONG></SPAN></FONT></DIV>
      <DIV><FONT face=3DArial color=3D#008000 size=3D2><SPAN=20
      class=3D719183313-26022009><STRONG><EM><SPAN=20
      class=3D719183313-26022009><STRONG><EM>So I think, why not store =
the=20
      information into the managed devices? Entity-MIB has provided the =
relative=20
      position, but it's not enough. We can add 'entity picture name', =
'entity=20
      width', 'entity height', 'entity angle', 'entity X position', =
'entity Y=20
      position', 'isVisible' ... information to Entity-MIB.=20
      </EM></STRONG></SPAN></EM></STRONG></SPAN></FONT></DIV>
      <DIV><FONT face=3DArial color=3D#008000 size=3D2><SPAN=20
      class=3D719183313-26022009><SPAN =
class=3D719183313-26022009><STRONG><EM>With=20
      the above information and pictures downloaded from&nbsp;vendor's=20
      website,&nbsp;we could draw the panel of devices easily regardless =
of=20
      vendor.</EM></STRONG></SPAN></SPAN></FONT></DIV>
      <DIV><FONT face=3DArial color=3D#008000 size=3D2><SPAN=20
      class=3D719183313-26022009><SPAN =
class=3D719183313-26022009><STRONG><EM>Let me=20
      know if you have some good idea about drawing the device panel. =
Thank you=20
      in advance.</EM></STRONG></SPAN></SPAN></FONT></DIV>
      <DIV><FONT face=3DArial color=3D#008000 size=3D2><SPAN=20
      class=3D719183313-26022009><STRONG><EM><SPAN=20
      =
class=3D719183313-26022009></SPAN></EM></STRONG></SPAN></FONT><FONT=20
      face=3DArial color=3D#008000 size=3D2><SPAN=20
      class=3D719183313-26022009><STRONG><EM><SPAN=20
      =
class=3D719183313-26022009></SPAN></EM></STRONG></SPAN></FONT><FONT=20
      face=3DArial color=3D#0000ff size=3D2><SPAN=20
      =
class=3D719183313-26022009><STRONG><EM></EM></STRONG></SPAN></FONT>&nbsp;=
</DIV>
      <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
      class=3D719183313-26022009></SPAN></FONT><FONT face=3DArial =
color=3D#0000ff=20
      size=3D2><SPAN=20
      =
class=3D719183313-26022009><STRONG><EM></EM></STRONG></SPAN></FONT>&nbsp;=
</DIV>
      <DIV><FONT face=3DArial color=3D#008000 size=3D2><SPAN=20
      class=3D719183313-26022009>For example, S2104 is a simple switch. =
It only=20
      has 4 ports. The XML file could be:</SPAN></FONT></DIV>
      <DIV><FONT face=3DArial color=3D#008000 size=3D2><SPAN=20
      =
class=3D719183313-26022009>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &lt;Entity name=3D"PANE_S2104" w=3D"835" h=3D"116",=20
      =
imgname=3D"s2104.gif"&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &lt;ElementList=20
      =
size=3D"1"&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;=20
      &lt;Element name=3D"FRAME_S2104" type=3D"Frame" angle=3D"0" =
visible=3D"false"=20
      <STRONG>x=3D"0" y=3D"0"</STRONG> w=3D"835" h=3D"116"=20
      =
/&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
&lt;/ElementList&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &lt;/Entity&gt;</SPAN></FONT></DIV>
      <DIV><FONT face=3DArial size=3D2><SPAN =
class=3D719183313-26022009><FONT=20
      face=3D&#23435;&#20307;></FONT><BR><FONT=20
      =
color=3D#008000>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &lt;Entity name=3D"FRAME_S2104" w=3D"835"=20
      =
h=3D"116"&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &lt;ElementList=20
      =
size=3D"1"&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;=20
      &lt;Element name=3D"MODULE1_S2104" type=3D"MODULE1" angle=3D"0" =
visible=3D"false"=20
      <STRONG>x=3D"0" y=3D"0"</STRONG> w=3D"835" h=3D"116"=20
      =
/&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
&lt;/ElementList&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &lt;/Entity&gt;</FONT></DIV>
      <DIV><FONT color=3D#008000></FONT>&nbsp;</DIV>
      <DIV><FONT=20
      =
color=3D#008000>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &lt;Entity name=3D"MODULE1_S2104" w=3D"835"=20
      =
h=3D"116"&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &lt;ElementList=20
      =
size=3D"1"&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;=20
      &lt;Element name=3D"MODULE2_S2104" type=3D"MODULE2" angle=3D"0" =
visible=3D"false"=20
      <STRONG>x=3D"0" y=3D"0"</STRONG> w=3D"835" h=3D"116"=20
      =
/&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
&lt;/ElementList&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &lt;/Entity&gt;</FONT></DIV>
      <DIV><FONT color=3D#008000></FONT>&nbsp;</DIV>
      <DIV><FONT=20
      =
color=3D#008000>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &lt;Entity name=3D"MODULE2_S2104" w=3D"835"=20
      =
h=3D"116"&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &lt;ElementList=20
      =
size=3D"5"&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;=20
      &lt;Element name=3D"PORT" type=3D"10or100M" angle=3D"180" =
visible=3D"true"=20
      <STRONG>x=3D"168" y=3D"64"</STRONG> w=3D"20" h=3D"20"=20
      =
/&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;=20
      &lt;Element name=3D"PORT" type=3D"10or100M" angle=3D"180" =
visible=3D"true"<STRONG>=20
      x=3D"240" y=3D"64"</STRONG> w=3D"20" h=3D"20"=20
      =
/&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;=20
      &lt;Element name=3D"PORT" type=3D"10or100M" angle=3D"180" =
visible=3D"true"=20
      <STRONG>x=3D"312" y=3D"64"</STRONG> w=3D"20" h=3D"20"=20
      =
/&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;=20
      &lt;Element name=3D"PORT" type=3D"10or100M" angle=3D"180" =
visible=3D"true"=20
      <STRONG>x=3D"384" y=3D"64"</STRONG> w=3D"20" h=3D"20"=20
      =
/&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
&lt;/ElementList&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &lt;/Entity&gt;</FONT></SPAN></FONT></DIV>
      <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
      =
class=3D719183313-26022009><STRONG><EM></EM></STRONG></SPAN></FONT>&nbsp;=
</DIV>
      <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
      =
class=3D719183313-26022009><STRONG><EM></EM></STRONG></SPAN></FONT>&nbsp;=
</DIV>
      <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
      =
class=3D719183313-26022009><STRONG><EM></EM></STRONG></SPAN></FONT>&nbsp;=
</DIV>
      <DIV><FONT size=3D2>(2) The status of the entity<BR><SPAN=20
      class=3D719183313-26022009><STRONG><EM><FONT face=3DArial=20
      color=3D#0000ff>[DR]&nbsp;Is the information in the Entity State =
MIB (RFC=20
      4268) not sufficient? </FONT></EM></STRONG></SPAN></FONT></DIV>
      <DIV><FONT face=3DArial color=3D#008000 size=3D2><SPAN=20
      class=3D719183313-26022009><STRONG><EM>[Ban] Yes, it's enough. I =
didn't know=20
      the mib.</EM></STRONG></SPAN></FONT></DIV>
      <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
      =
class=3D719183313-26022009><STRONG><EM></EM></STRONG></SPAN></FONT>&nbsp;=
</DIV>
      <DIV><FONT size=3D2>(3) The other important information of CPU, =
Sensor,=20
      disk, powersupply etc.<BR><SPAN =
class=3D719183313-26022009><STRONG><EM><FONT=20
      face=3DArial color=3D#0000ff>[DR]&nbsp;Is the information in the =
Entity Sensor=20
      MIB (RFC&nbsp;3433) &nbsp;not sufficient?=20
      </FONT></EM></STRONG></SPAN></FONT></DIV>
      <DIV><FONT face=3DArial color=3D#008000 size=3D2><SPAN=20
      class=3D719183313-26022009><STRONG><EM>[Ban] Yes, it's enough. I =
didn't know=20
      the mib.</EM></STRONG></SPAN></FONT></DIV>
      <DIV><FONT face=3DArial color=3D#008000 size=3D2><SPAN=20
      =
class=3D719183313-26022009><STRONG><EM></EM></STRONG></SPAN></FONT>&nbsp;=
</DIV>
      <DIV><FONT size=3D2>Can the ENTITY-MIB be extended? What needs to =
happen?=20
      <BR><SPAN class=3D719183313-26022009><STRONG><EM><FONT =
face=3DArial=20
      color=3D#0000ff>[DR]&nbsp;The OPSAWG can be a home for working on =
such=20
      extensions if there is interest here. Let us see what other people =
think.=20
      </FONT></EM></STRONG></SPAN></FONT></DIV>
      <DIV><FONT size=3D2><SPAN=20
class=3D719183313-26022009></SPAN></FONT>&nbsp;</DIV>
      <DIV><FONT size=3D2>Thank you very much.</FONT></DIV>
      <DIV><FONT size=3D2></FONT>&nbsp;</DIV>
      <DIV><FONT size=3D2>Cheers</FONT></DIV>
      <DIV><FONT size=3D2>Shimin Ban</FONT></DIV>
      <DIV><FONT size=3D2></FONT>&nbsp;</DIV>
      <DIV><FONT size=3D2></FONT>&nbsp;</DIV>
      <DIV><FONT=20
size=3D2></FONT>&nbsp;</DIV></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BODY=
></HTML>

------_=_NextPart_001_01C99B39.7D682A66--

From root@core3.amsl.com  Mon Mar  2 18:00:01 2009
Return-Path: <root@core3.amsl.com>
X-Original-To: opsawg@ietf.org
Delivered-To: opsawg@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id E36AD3A694D; Mon,  2 Mar 2009 18:00:01 -0800 (PST)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20090303020001.E36AD3A694D@core3.amsl.com>
Date: Mon,  2 Mar 2009 18:00:01 -0800 (PST)
Cc: opsawg@ietf.org
Subject: [OPSAWG] I-D Action:draft-ietf-opsawg-survey-management-00.txt
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Mar 2009 02:00:02 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Operations and Management Area Working Group Working Group of the IETF.


	Title           : Survey of IETF Network Management Standards
	Author(s)       : D. Harrington
	Filename        : draft-ietf-opsawg-survey-management-00.txt
	Pages           : 21
	Date            : 2009-03-02

This document provides a survey of existing IETF standards-track
network management protocols and data models.  The purpose of this
document is to help protocol designers, implementers, and users to
select appropriate standard management protocols and data models to
address relevant management needs.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-opsawg-survey-management-00.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-opsawg-survey-management-00.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2009-03-02175300.I-D@ietf.org>


--NextPart--

From cfinss@dial.pipex.com  Tue Mar  3 10:30:42 2009
Return-Path: <cfinss@dial.pipex.com>
X-Original-To: opsawg@core3.amsl.com
Delivered-To: opsawg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 196273A6B29 for <opsawg@core3.amsl.com>; Tue,  3 Mar 2009 10:30:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.795
X-Spam-Level: 
X-Spam-Status: No, score=-0.795 tagged_above=-999 required=5 tests=[AWL=-0.439, BAYES_00=-2.599, J_CHICKENPOX_35=0.6, RCVD_IN_NJABL_PROXY=1.643]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m-kWX3DL5WnC for <opsawg@core3.amsl.com>; Tue,  3 Mar 2009 10:30:39 -0800 (PST)
Received: from mk-outboundfilter-2.mail.uk.tiscali.com (mk-outboundfilter-2.mail.uk.tiscali.com [212.74.114.38]) by core3.amsl.com (Postfix) with ESMTP id A9C443A6987 for <opsawg@ietf.org>; Tue,  3 Mar 2009 10:30:37 -0800 (PST)
X-Trace: 190969422/mk-outboundfilter-2.mail.uk.tiscali.com/PIPEX/$PIPEX-ACCEPTED/pipex-customers/62.188.17.133/None/cfinss@dial.pipex.com
X-SBRS: None
X-RemoteIP: 62.188.17.133
X-IP-MAIL-FROM: cfinss@dial.pipex.com
X-MUA: Microsoft Outlook Express 6.00.2800.1106Produced By Microsoft MimeOLE V6.00.2800.1106
X-IP-BHB: Once
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: As4EALsFrUk+vBGF/2dsb2JhbACDIkKKBLsYj0IHgkABgT4Ghmg
X-IronPort-AV: E=Sophos;i="4.38,296,1233532800"; d="scan'208";a="190969422"
X-IP-Direction: IN
Received: from 1cust133.tnt1.lnd3.gbr.da.uu.net (HELO allison) ([62.188.17.133]) by smtp.pipex.tiscali.co.uk with SMTP; 03 Mar 2009 18:30:55 +0000
Message-ID: <001f01c99c25$99418220$0601a8c0@allison>
From: "tom.petch" <cfinss@dial.pipex.com>
To: "David Harrington" <ietfdbh@comcast.net>, "'Adrian Farrel'" <adrian@olddog.co.uk>, <opsawg@ietf.org>
References: <EDC652A26FB23C4EB6384A4584434A040132E373@307622ANEX5.global.avaya.com><5C8D68E9DDC2439B82F3CC0591A54F05@your029b8cecfe> <000801c98ba3$80df0780$0601a8c0@allison> <003601c98bbd$19086470$0600a8c0@china.huawei.com>
Date: Tue, 3 Mar 2009 17:41:11 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Cc: 'David B Harrington' <dbharrington@comcast.net>, tseely5@gmail.com
Subject: Re: [OPSAWG] (final) WGLCondraft-ietf-opsawg-operations-and-management
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: "tom.petch" <cfinss@dial.pipex.com>
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Mar 2009 18:30:42 -0000

----- Original Message -----
From: "David Harrington" <ietfdbh@comcast.net>
To: "'tom.petch'" <cfinss@dial.pipex.com>; "'Adrian Farrel'"
<adrian@olddog.co.uk>; <opsawg@ietf.org>
Cc: "'David B Harrington'" <dbharrington@comcast.net>; <tseely5@gmail.com>
Sent: Tuesday, February 10, 2009 9:21 PM
Subject: RE: [OPSAWG] (final) WGLCondraft-ietf-opsawg-operations-and-management


> Besides the comments form Juergen, Mike, and Adrian, what needs to be
> done to make this live up to its billing? Do you have explicit
> recommendations of text?
>

Not so much text as a different approach; I would be more radical than the
others.

It is billed as guidelines to protocol designers so should address what is OAM
and how it can benefit from being built into the protocol.

OAM has two radically different meanings within the IETF and so I think it
important to say what it is.  And this immediately becomes subjective.   For me,
it is delivering service and so the protocol needs to be clear what service it
offers; reliability, security, flow control,  ..... there are many aspects but
few protocol designers seem to document them except where they are forced to.
Happily, I see several ADs insisting on threats to security being defined before
the WG just says encrypt everything:-)  Defence against a threat is part of the
service just as regarding some threats as out of scope is saying they are not
part of the service.  So the starting point for me can only be a definition of
service, in regard to OAM, and that I do not often see in I-Ds.

Then it is a question of what a protocol can do.  Simple things protocols, an
exchange of messages, the need to cater for messages being lost, corrupted and
duplicated, some defined fields and their semantics.  If your concern is eg lost
messages, then you include sequencing in some shape or form; if your concern is
availability, then you may consider heartbeats but be careful, some networks
echo back your data so if there is nothing to distinguish a heartbeat from a
heartbeat response, then you may get fooled by a totally dead network.

Or again, is migration needed?  Yes, always.  If this is the first, then it will
not be perfect and will need migrating to something better.  If this is not the
first, then you need to migrate to it.  Ergo, migration will always happen.
Therefore you need a 100% reliable way of differentiating old from new, and of
ensuring that old boxes behave predictably when confronted with new (if version
NE 1, then send Notification) and this needs building in when you design the old
protocol; by the time you are designing the new, it is too late.  There are
plenty of examples of how not to do it.

Will the protocol need expanding?  Yes, beyond your wildest dreams.  OSI had the
right idea when it allowed BER.1 a length of 2**127-1; I think that that should
satisfy anyone's dreams:-)  But look at tcpm and their agonies with TCP option
space.  If only the original designers had had more foresight.

The structure of fields and encoding in some protocols is just designed to
induce faults, mostly from inconsistency; some fields count from zero, others
don't, some are fixed length, others are TLV, mix it all up for reasons that
seem good at the time and you have a fault-prone system.

Binary encoding, text, structured text (XML) lots of ways of doing it;
consistency, familiarity and lack of surpises for the user make for a good
protocol for OAM, less likely to go wrong, easier to troubleshoot.

That should give you some flavour of what I would like to see, not in the
specific examples but in the general approach; what is OAM to you, what can be
done in the structure, in the semantics, in the concepts usually represented by
a state diagram (not sure what the right term for that is) to achieve the goal.

Tom Petch

> dbh
>
> > -----Original Message-----
> > From: opsawg-bounces@ietf.org
> > [mailto:opsawg-bounces@ietf.org] On Behalf Of tom.petch
> > Sent: Tuesday, February 10, 2009 12:05 PM
> > To: Adrian Farrel; opsawg@ietf.org
> > Cc: David B Harrington; tseely5@gmail.com
> > Subject: Re: [OPSAWG] (final)
> > WGLCondraft-ietf-opsawg-operations-and-management
> >
> > I was going to say +1 to Juergen's comments and then I was
> > going to say +1 to
> > Mike's comments and then I was going to say +1 to Adrian's
> > comments and while I
> > was pondering, ... I left it too late:-(
> >
> > But I do echo much of what has been said.  I cannot see that
> > this I-D lives up
> > to its billing.  It is a good idea, and it is good stuff
> > (give or take some
> > infelicities of wording, most of which have been pointed out
> > already) but I do
> > not see it as good stuff for a working group coming up with a
> > new protocol, say
> > an MPLS-TP or sieve or sidr. And that is what I think is
> > needed.  If something
> > is not designed to be managed ab initio, then it may be
> > costly, impossible even,
> > to manage it in the wild.
> >
> > Tom Petch
> >
> >
> > ----- Original Message -----
> > From: "Adrian Farrel" <adrian@olddog.co.uk>
> > To: <opsawg@ietf.org>
> > Cc: "David B Harrington" <dbharrington@comcast.net>;
> > <tseely5@gmail.com>
> > Sent: Wednesday, February 04, 2009 8:54 PM
> > Subject: Re: [OPSAWG] (final) WGLC
> > ondraft-ietf-opsawg-operations-and-management
> >
> >
> > > Hi,
> > >
> > > Dan asked me to have a look at this which I do primarily
> > with a routing area
> > > view on the world.
> > >
> > > I'm sorry that I haven't been following this I-D very
> > closely and apologise
> > > if you have already discussed and reached conclusion on
> > some of the points I
> > > make.
> > >
> > > I am largely supportive of this work (see
> > > draft-ietf-pce-manageability-requirements-06.txt), but I do
> > have some
> > > issues. I would be comforted to know that the I-D had had
> > extensive review
> > > from within the Ops Area without relying just on my comments!
> > >
> > > I would also like to understand how the recommendations
> > parts of the draft
> > > will be interpreted by the Ops ADs as they perform IESG
> > review of I-Ds from
> > > other areas. Depending on the answer (which I would like to
> > see encapsulated
> > > in the document!) I might have other harsher comments about
> > the content.
> > >
> > > More details below.
> > >
> > > Cheers,
> > > Adrian
> > >
> > > ===
> > > Title is...
> > >  Guidelines for Considering Operations and Management of
> > New Protocols
> > > ...but the Abstract immediately includes...
> > >    New protocols or protocol extensions
> > > ===
> > > Obviously needs the new IPR boilerplate.
> > > ===
> > > Abstract line 3
> > > s/protocol/protocols/
> > > ===
> > > I am somewhat worried by "recommend appropriate standard
> management
> > > protocols ... to address the relevant operations and management
> > > needs."
> > >
> > > I understand the theory behind this guidance in terms of making
> > > equipment that will interwork with management systems, but I
> > > question its practicality given the vast array of management
> > > protocols available. And actually, I am not sure that this has a
> > > direct impact on the success of or development of a protocol.
> > >
> > > The introduction says that this "is similar to a WG considering
> > > which security threats are relevant to their protocol, and then
> > > recommending appropriate standard security protocols to mitigate
> > > the relevant threats." I dispute this. The security considerations
> > > normally make modifications to the protocol under development to
> > > make it secure, or mandate security features in other protocols
> > > that the protocol under development uses. But where there is a
> > > need for an external protocol, this is not usually mandated. For
> > > example, where key exchange is needed the text will usually say
> > > something like "may use some form of secure key exchange protocol
> > > (such as the Internet Key Exchange protocol v2 (IKE) [RFC4306]."
> > > This is far looser than a recommendation of a specific protocol.
> > >
> > > I believe that in practice operators want to go on using the
> > > management protocols that they already have deployed. If, for
> > > example, I have deployed routers that I manage using SNMP, I will
> > > not want to deploy a new routing protocol on those routers if that
> > > protocol is strongly recommended to be managed using TL1.
> > >
> > > Since data modeling is usually tied closely to the protocol used
> > > for management, it follows from this that developing specific
> > > data formats (SNMP MIB modules, XML schema, etc.) might also not
> > > be so very practical. (Arguably we have found this out with MIB
> > > modules over the last 10 years, but still churn them out.)
> > >
> > > What *would* be beneficial, however, is an abstract data model
> > > for management of the protocol. There are many ways of
> > > representing the data (XML, BNF, ASN.1, graphical representation,
> > > etc.) and the Ops Area could usefully pick one and standardise
> > > it. From there we would have a solid data set that all
> > > implementations could make available and which separate documents
> > > could easily map to suitable formats for use by specific
> > > management protocols. Smart implementers would be able to support
> > > multiple management protocols with ease.
> > >
> > > You do come to this to some extent in section 4.1, and the text
> > > there seems to be at odds with what you have said in the
> > > Introduction.
> > >
> > > ===
> > > Section 1
> > >
> > > Can you expand "WG" on first usage?
> > >
> > > ===
> > > Section 1
> > >
> > >    We want to avoid seeming to impose a solution by putting
> > in place a
> > >    strict terminology - for example implying that a formal
> > data model,
> > >    or even using a management protocol is mandatory.
> > >
> > > <grin mode=wry>
> > >
> > > You want to avoid seeming to impose it?
> > > So, you want to impose it, but you don't want anyone to notice?
> > >
> > > </grin>
> > >
> > > ===
> > > Section 1
> > >
> > >    Making a Management Considerations section a mandatory
> > publication
> > >    requirement for IETF documents is the responsibility of
> > the IESG, or
> > >    specific area directors, or working groups, and this
> > document avoids
> > >    recommending any mandatory publication requirements.
> > >
> > > I think you may need to go a step further to get this through the
> > > IESG. It would not be funny to see this paragraph as written, but
> > > to get a DISCUSS on an I-D from an Ops AD because the I-D did not
> > > contain a Management Considerations section.
> > >
> > > ===
> > > Introduction
> > >
> > >    We provide some objective criteria to promote interoperability
> > >
> > > <grin mode=laconic>
> > >
> > > There seems to be only one author. Are you royalty?
> > > Perhaps... "This document provides..."
> > >
> > > </grin>
> > >
> > > ===
> > > Section 1 final line
> > >
> > > s/??/?"/
> > >
> > > ===
> > >
> > > 2.1.  IETF Management Framework
> > >
> > >    For years the IETF has stressed the use of the IETF Standard
> > >    Management Framework and MIB modules [RFC2578] for managing new
> > >    protocols.  The IETF designed these to permit multiple
> > protocols to
> > >    utilize the MIB data [RFC1052], but it became a common
> > >
> > > s/became/is/
> > >
> > > ===
> > >
> > > 3.1.  Operations Model
> > >
> > >    o  what are the typical user interfaces - Command line (CLI) or
> > >       graphical user interface (GUI)?
> > >
> > > I am not sure that this last item is particularly relevant for a
> > > large number of the protocols designed in the IETF. We might say
> > > that the question is valid for a protocol such as FTP, but is it
> > > relevant for OSPF? Yes, there is a configuration interface to a
> > > device that runs OSPF, but it is surely nothing to do with the
> > > protocol design how that interface works. Indeed, you might
> > > reduce the question to: are the configuration interfaces local or
> > > remote? But I think you will find that the answer to the question
> > > is "both" as in the subsequent paragraph.
> > >
> > > ===
> > >
> > > 3.1.  Operations Model
> > >
> > >    Auto-configuration and default parameters might be
> > >    possible for some new protocols.
> > >
> > > I would make a much bigger noise about default parameters. There
> is
> > > a key question about how the protocol can operate "out of the
> box".
> > > If implementers are free to select their own defaults, the
> protocol
> > > needs to operate well with any choice of values. If there are
> > > sensible defaults, these need to be stated.
> > >
> > > Indeed, section 3.2 seems to say this. Perhaps a forward
> reference?
> > >
> > > ===
> > >
> > > 3.1.  Operations Model
> > >
> > >    There may be a need to support a human interface, e.g., for
> > >    troubleshooting, and a programmatic interface, e.g., for
> > automated
> > >    monitoring and root cause analysis.  It might be
> > important that the
> > >    internal method routines used by the application programming
> > >    interfaces and the human interfaces should be the same
> > to ensure that
> > >    data exchanged between these two interfaces is always
> consistent.
> > >    Mixing methods leads to inconsistency, so identifying
> consistent
> > >    methods of retrieving information is relevant.
> > >
> > > This is really sailing too close to the implementation. People
> > > must be free to construct sub-standard and unmarketable
> > > implementations. The IETF is not responsible for making all
> > > implementations successful. The job is to make it possible for
> > > all implementations to be successful given core competences in the
> > > developers.
> > >
> > > I think the furthest a protocol spec RFC could go would be to say
> > > what information must be available to an operator at a human
> > > interface for troubleshooting
> > >
> > > ===
> > >
> > > 3.2.  Installation and Initial Setup
> > >
> > > In view of the reasons you give why defaults might become out-
> > > dated, you might point out that sometimes it is not advisable to
> > > have defaults. In these cases explicit configuration is required.
> > >
> > > ===
> > >
> > > 3.2.  Installation and Initial Setup
> > >
> > > Is the text at the top of page 8 supposed to be a bullet list?
> > >
> > > ===
> > >
> > > 3.4.  Requirements on Other Protocols and Functional Components
> > >
> > >    These considerations should generally remain
> > illustrative to avoid
> > >    creating restrictions or dependencies, or potentially
> > impacting the
> > >    behavior of existing protocols, or restricting the
> > extensibility of
> > >    other protocols, or assuming other protocols will not be
> > extended in
> > >    certain ways.
> > >
> > > Well, this is quite interesting.
> > >
> > > Suppose you decide to utilise a particular feature of a transport
> > > protocol. You are creating a hard requirement that that feature is
> > > implemented in all implementations of the set {your new protocol,
> > > the transport protocol}. But more importantly, perhaps, you are
> > > requiring that new versions of the transport protocol do not
> > > deprecate the feature you require.
> > >
> > > In short, I don't think you should be too nervous about creating
> > > restrictions or dependencies. If they exist, they must be stated.
> > >
> > > ===
> > >
> > > 3.2.  Installation and Initial Setup
> > >
> > >    For example, the design of Resource ReSerVation Protocol (RSVP)
> > >
> > > I think this example is not well expressed.
> > >
> > > The problem in RSVP was that the IP packet was addressed to the
> > > ultimate RSVP-capable destination, but the RSVP-capable routers
> > > along the path needed to intercept and process the Path message.
> > > This they could only do by "deep packet inspection" or by the
> > > router alert option.
> > >
> > > I wonder whether this example adds significantly to the I-D.
> > >
> > > ===
> > >
> > > 4.  Management Considerations
> > >
> > >    NETCONF addresses this in a generic manner by
> > >
> > > Add citation.
> > >
> > > ===
> > >
> > > 4.  Management Considerations
> > >
> > >    However, debugging on-the-wire interactions is a protocol
> > >    issue: it is enormously helpful if a protocol has hooks to make
> > >    debugging of network interactions easy, and/or is
> > designed in such a
> > >    way that debugging protocol behaviors is easy.
> > Hand-waving this away
> > >    is not something that operators like ...
> > >
> > > I think you are including this by hand-waving!
> > > What do you mean by "hooks"?
> > > Surely any protocol can be debugged simply by sniffing it.
> > > If you have specific hooks in mind you must set them out and not
> > > leave the reader guessing.
> > > But if you force the implementation I shall be peeved!
> > > You might, for example, say that there should be alerts issued
> when
> > > messages are received, or when there are state transitions in the
> > > protocol state machine, but you must recall that:
> > > - the messages can be seen by sniffing
> > > - the state machine is not part of the protocol specification.
> > > This latter point is key. The state machine explains how the
> > > protocol works in order that an implementer can decide how to
> > > react to a received event, but it does not require that the
> > > machine is implemented.
> > >
> > > ===
> > >
> > > 4.1.  Interoperability
> > >
> > >    Interoperability needs to be considered on the syntactic
> > level and
> > >    the semantic level.  While it can be irritating and
> > time-consuming,
> > >    application designers including operators who write
> > their own scripts
> > >    can make their processing conditional to accommodate
> differences
> > >
> > > s/differences/syntactic differences/ ?
> > >
> > >    Then, whether the counter is gathered via SNMP or a CLI
> > >    command or a SYSLOG message, the counter will have
> > similar meaning.
> > >
> > > "similar"? I think that might not be good enough. Don't you need
> > > "the same"?
> > >
> > >    o  [RFC3805] - Printer MIB v2 (contains both an IM and a DM
> > >
> > > Missing ")"
> > >
> > > ===
> > >
> > > 4.2.  Management Information
> > >
> > > I would find it really helpful if you were able to recommend a
> > > language in which to write the information model. Ideally, all
> > > IETF IMs would be in the same language.
> > >
> > >    It is important to be able to separately fetch
> > configuration data,
> > >    operational state data, and statistics from devices, and
> > to be able
> > >    to compare current state to initial state, and to compare data
> > >    between devices.
> > >
> > > You seem to have drifted into DMs here. You cannot fetch data from
> > > an IM. It simply explains what data elements exist. In fact, an IM
> > > states all of the data that exists and so there is no confusion.
> > > Confusion can only arise as the DM is constructed and multiple IM
> > > data elements are conflated into single DM objects.
> > >
> > > ===
> > >
> > > 4.3.  Fault Management
> > >
> > >    The protocol designer should document the basic faults and
> health
> > >    indicators that need to be instrumented for the new
> > protocol, and the
> > >    alarms and events that must be propagated to management
> > applications
> > >    or exposed through a data model.
> > >
> > > Isn't "propagated to management applications" a subset of "exposed
> > > through a data model"?
> > >
> > >    The protocol designer should consider how faults
> > information will be
> > >
> > > s/faults/fault/
> > >
> > >    Should the event reporting provide gyaranteed accurate
> > delivery of
> > > s/gyaranteed/guaranteed/
> > >
> > > ===
> > >
> > > 4.3.3.  Fault Isolation
> > >
> > >    It might be useful to isolate faults, such as a system that
> emits
> > >    malformed messages necessary to coordinate connections
> properly.
> > >    Spanning tree comes to mind.  This might be able to be done by
> > >    configuring next-hop devices to drop the faulty messages
> > to prevent
> > >    them from entering the rest of the network.
> > >
> > > This is not what *I* mean by fault isolation!
> > > Fault isolation is about working out where in the network the
> fault
> > > is. For example, if end-to-end data delivery is failing (reported
> by
> > > a notification), fault isolation will find the failed link or node
> > > in the end-to-end path.
> > >
> > > You seem to be describing the process of quarantining faulty
> > > devices. This may also be valuable.
> > >
> > > "Spanning tree comes to mind" is a rather strange sentence without
> > > much context.
> > >
> > > ===
> > >
> > > 4.4.  Configuration Management
> > >
> > >    A protocol desoigners should document what the basic
> > configuration
> > >
> > > s/desoigners/designers/
> > >
> > >    "Requirements for Configuration Management of IP-based
> Networks"
> > >    [RFC3139] discusses requirements for configuration management.
> > > More precisely,
> > >    "Requirements for Configuration Management of IP-based
> Networks"
> > >    [RFC3139] discusses requirements for configuration management
> of
> > >    IP-based networks.
> > > Which makes me wonder about the purpose of the sentence :-)
> > >
> > >    This document includes...
> > > This document or that document?
> > >
> > >    A number of efforts have existed in the IETF to develop
> > policy-based
> > >    management.  "Terminology for Policy-Based Management"
> > [RFC3198] was
> > >    written to standardize the terminology across these
> > efforts.  Some of
> > >    the efforts resulted in proposals that are NOT RECOMMENDED, so
> a
> > >    protocol designer should check the current recommendation
> status
> > >    before depending on a specific protocol suggestion.
> > >
> > > You have used RFC2119 language, but in section 1.1 you said
> > >    This document deliberately does not use the
> > (capitalized) keywords
> > >    described in RFC 2119 [RFC2119].
> > > Furthermore, it is not clear to me whether this I-D is doing the
> > > NOT RECOMMENDing or whether some other RFC has done it. If it is
> > > this I-D, you will need to give reasons. If is some other RFC, you
> > > will need to give references.
> > >
> > >    It is highly desirable that text processing tools such
> > as diff, and
> > >    version management tools such as RCS or CVS or SVN, can
> > be used to
> > >    process configurations.  This approach simplifies comparing the
> > >    current operational state to the initial configuration.  It is
> > >    commonplace to compare configuration changes to e.g.,
> > last day, last
> > >    week, last month, etc. -- having configuration in a
> > text, and human-
> > >    understandable format is very valuable for various
> > reasons such as
> > >    change control (or verification), configuration
> > consistency checks,
> > >    etc.
> > >
> > > Yes, but what has this to do with the protocol design? It might be
> > > related to device implementation. Or it might be relevant to
> > > EMS/NMS implementation.
> > >
> > > As you note in the subsequent paragraph, this may be impossible
> > > even in some text-based DMs. It would certainly be impossible in
> > > an SNMP MIB module.
> > >
> > >    To simplify such configuration comparisons, devices should not
> > >    arbitrarily reorder data such as access control lists.
> > If a protocol
> > >    designer defines mechanisms for configuration, it would
> > be desirable
> > >    to standardize the order of elements for consistency of
> > configuration
> > >    and of reporting across vendors, and across releases
> > from vendors.
> > >
> > > This example seems a bit specific. And in any case, it is
> perfectly
> > > possible to sort a list before comparing.
> > >
> > >    There are two parts to this: 1.  An NMS system could
> > optimize ACLs
> > >    for performance reasons 2.  Unless the device/NMS
> > systems has correct
> > >    rules/a lot of experience, reordering ACLs can lead to a huge
> > >    security issue.
> > >
> > > Maybe what you are saying is:
> > >    Implementations should not arbitrarily modify configuration
> data.
> > >    In some cases (such as Access Control Lists) the order of data
> > >    items is significant and comprises part of the configured data.
> > >
> > >    Network wide configurations are ideally stored in central
> master
> > >    databases
> > >
> > > This looks like an unsubstantiated assertion. You might get away
> > > with "Many operators prefer that..."
> > >
> > >    It is important to distinguish between the distribution of
> > >    configurations and the activation of a certain configuration.
> > >    Devices should be able to hold multiple configurations.
> > >
> > > This is really an implementation issue and nothing to do with the
> > > protocol under design.
> > >
> > >    Consensus of the 2002 IAB Workshop was that textual
> configuration
> > >    files should be able to contain international characters.
> > >
> > > Do you have a citation?
> > >
> > >    These timers may need default values
> > >    suggested in the protocol specification and do not need to be
> > >    otherwise configurable.
> > >
> > > I had formed the opinion that timers must be given default values
> > > in IETF protocol specifications, but I can't lay my hands on a
> > > reference.
> > >
> > > ===
> > >
> > > 4.5.  Accounting Management
> > >
> > >    A protocol designer should consider whether it would be
> > appropriate
> > >    to collect usage information related to this protocol, and if
> so,
> > >    what usage information would be appropriate to collect?
> > >
> > > s/collect?/collect./
> > >
> > >    "Introduction to Accounting Management" [RFC2975]
> > discusses a number
> > >    of factors relevant to monitoring usage of protocols for
> > purposes of
> > >    capacity and trend analysis, cost allocation, auditing,
> > and billing.
> > >    This document also discusses how Remote Authentication
> > Dial In User
> > > This or that?
> > >
> > >    Service (RADIUS) [RFC2865], Terminal Access Controller
> > Access Control
> > >    System (TACACS) [RFC1492], SNMP, IPFIX, and Packet
> > Sampling (PSAMP)
> > >    Protocol [I-D.ietf-psamp-protocol] protocols can be used
> > for these
> > >    purposes.
> > >
> > > Surely RFC 2975 does not mention PSAMP? Which makes me wonder what
> > > you are trying to achieve with a list of example protocols. Are
> > > they intended as recommendations (in which case say so and why),
> > > or as a non-exclusive list (in which case a "such as" would be
> > > useful). At the moment it reads like these are your favorites and
> > > you would be upset if someone used a different protocol!
> > >
> > > ===
> > >
> > > 4.6.  Performance Management
> > >
> > >    There are several parts to performance management to be
> > considered:
> > >    protocol monitoring, services monitoring, and device
> > monitoring (the
> > >    impact of the new protocol/service activation on the device).
> > >
> > > s/services/service/
> > >
> > >    Consider scalability, such as whether performance will
> > be affected by
> > >    the number of protocol connections.
> > >
> > > Maybe say "protocol entities" rather than connections?
> > >
> > >
> > > This section seems to flit between the performance of the protocol
> > > under design and the network running the protocol under design,
> and
> > > the performance of the management of the protocol. Each is
> > > important, but it may be constructive to split them out into
> > > separate sections. The latter will also include a consideration of
> > > how the act of monitoring impacts on network performance.
> > >
> > >
> > >    The Benchmarking Methodology WG (bmwg) has defined
> > recommendations
> > > Later you have BMWG.
> > >
> > > ===
> > >
> > > 4.7.  Security Management
> > >
> > >    It must be possible to do consistency checks of access
> > control lists
> > >    across devices.  Protocol designers should consider information
> > >    models to promote comparisons across devices and across
> > vendors to
> > >    permit checking the consistency of security configurations.
> > >
> > > I think this "must" is massively excessive!
> > > I would expect each router to have a different access list in the
> > > control plane (a list of its neighbors). Such a mechanism would
> > > actually open up a security vulnerability that has to be
> protected.
> > > Perhaps you are talking about management plane access lists. This
> > > takes us into the area of securing management activity - see my
> > > comments on Section 7.
> > >
> > >    RADIUS and DIAMETER can provide authentication and
> > authorization.  A
> > >    protocol designer should consider which attributes would be
> > >    appropriate for their protocol.
> > >
> > > This paragraph is apropos of what? What are you trying to tell me?
> > > Should I run my management using Radius? Should I try to build
> > > Diameter into my new protocol?
> > >
> > >    Different protocols use different assumptions about
> > message security
> > > s/protocols/management protocols/
> > >
> > >    and data access controls.  A protocol designer that
> > recommends using
> > >    different protocols should consider how security will be
> > applied in a
> > > s/protocols/management protocols/
> > >
> > >
> > > Although you talk about (presumably management) access
> > lists, I think
> > > I would have expected a discussion of authority levels and policy
> > > with regard to management tasks.
> > >
> > > ===
> > >
> > > 7.  Security Considerations
> > >
> > >    This document is informational and provides guidelines for
> > >    considering manageability and operations.  It introduces no new
> > >    security concerns.
> > >
> > > I think that, although you introduce no new security concerns
> > > directly, you have some things to talk about.
> > >
> > > Firstly, the provision of a management portal to a network device
> > > provides a doorway through which an attack on the device may be
> > > launched. Since you are recommending that the protocol under
> > > development be manageable through the management protocol, you are
> > > requiring that the protocol be vulnerable to a new source of
> > > attacks. Therefore, you must talk about securing the protocol
> > > against these attacks. This might be as simple as saying that only
> > > management protocols with adequate (for some definition of
> > > adequate) security apparatus be used.
> > >
> > > I think it is also of note that a standard description of the
> > > manageable knobs and whistles on a protocol makes it easier for an
> > > attacker to understand what they may try to control and how to
> > > tweak it.
> > >
> > > On the other hand, it would be well worth pointing out that a
> > > well-designed protocol is usually more stable and secure. And that
> > > a protocol that can be managed and inspected offers the operator
> > > a better chance of spotting and quarantining any attacks.
> > > Conversely making a protocol inspectable, is a risk if the wrong
> > > person inspects it!
> > >
> > > If security events cause logs and or notifications/alerts, can
> > > a concerted attack be mounted by causing an excess of these
> > > events? In other words, to the security management mechanisms
> > > constitute the security vulnerability?
> > >
> > > Lastly, the management of security aspects is important, and you
> > > can just reference back to section 4.7.
> > >
> > > ===
> > >
> > > 9.  Informative References
> > >
> > > I (of course) would favor an informational reference to
> > draft-ietf-pce-
> > > manageability-requirements-06.txt
> > >
> > > ===
> > >
> > >    [RFC2821]                       Klensin, J., "Simple
> > Mail Transfer
> > >                                    Protocol", RFC 2821, April
> 2001.
> > >
> > > I think this has been obsoleted.
> > >
> > > ===
> > >
> > > Appendix A.  Operations and Management Review Checklist
> > >
> > > Maybe a forward reference to this appendix from sections 1 and 5?
> > >
> > > ===
> > >
> > > A.3.  Documentation
> > >
> > >    Does the proposed protocol have a significant
> > operational impact on
> > >    the Internet.  If it does, and the document under review
> targets
> > >    standards track, is their enough proof of implementation and/or
> > >    operational experience to grant Proposed Standard status?
> > >
> > > Whoah!
> > >
> > > You are going to use this I-D to try to block standards track I-Ds
> > > from becoming RFCs? You are going to get into such a fight!!!
> > >
> > > IMHO this sentence is a complete show-stopper in your I-D.
> > >
> > > (Oh, and s/their/there/)
> > >
> > > ===
> > >
> > > Appendix B.  Change Log
> > >
> > > Suggest you flag this for removal upon publication as an RFC.
> > >
> > > ===
> > >
> > > > Sent: Sunday, January 25, 2009 6:40 PM
> > > > To: opsawg@ietf.org
> > > > Subject: [OPSAWG] (final) WGLC on
> > > > draft-ietf-opsawg-operations-and-management
> > > >
> > > > This is a (hopefully final) WGLC for
> > > > draft-ietf-opsawg-operations-and-management
> > > > there was not enough respose to the last one back in October
> > > > please let the list know what you think of the draft
> > >
> > > _______________________________________________
> > > OPSAWG mailing list
> > > OPSAWG@ietf.org
> > > https://www.ietf.org/mailman/listinfo/opsawg
> >
> > _______________________________________________
> > OPSAWG mailing list
> > OPSAWG@ietf.org
> > https://www.ietf.org/mailman/listinfo/opsawg
> >
>


From dbharrington@comcast.net  Tue Mar  3 11:40:53 2009
Return-Path: <dbharrington@comcast.net>
X-Original-To: opsawg@core3.amsl.com
Delivered-To: opsawg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9DE233A6825 for <opsawg@core3.amsl.com>; Tue,  3 Mar 2009 11:40:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.187
X-Spam-Level: 
X-Spam-Status: No, score=-2.187 tagged_above=-999 required=5 tests=[AWL=-0.188, BAYES_00=-2.599, J_CHICKENPOX_35=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d30u-Nx-QQw4 for <opsawg@core3.amsl.com>; Tue,  3 Mar 2009 11:40:50 -0800 (PST)
Received: from QMTA08.westchester.pa.mail.comcast.net (qmta08.westchester.pa.mail.comcast.net [76.96.62.80]) by core3.amsl.com (Postfix) with ESMTP id 5187F3A67F9 for <opsawg@ietf.org>; Tue,  3 Mar 2009 11:40:50 -0800 (PST)
Received: from OMTA10.westchester.pa.mail.comcast.net ([76.96.62.28]) by QMTA08.westchester.pa.mail.comcast.net with comcast id Nisy1b0020cZkys58jhJ94; Tue, 03 Mar 2009 19:41:18 +0000
Received: from Harrington73653 ([24.147.240.21]) by OMTA10.westchester.pa.mail.comcast.net with comcast id NjhH1b00K0UQ6dC3WjhHrb; Tue, 03 Mar 2009 19:41:18 +0000
From: "David B Harrington" <dbharrington@comcast.net>
To: <opsawg@ietf.org>
References: <EDC652A26FB23C4EB6384A4584434A040132E373@307622ANEX5.global.avaya.com><5C8D68E9DDC2439B82F3CC0591A54F05@your029b8cecfe> <000801c98ba3$80df0780$0601a8c0@allison> <003601c98bbd$19086470$0600a8c0@china.huawei.com> <001f01c99c25$99418220$0601a8c0@allison>
Date: Tue, 3 Mar 2009 14:41:16 -0500
Message-ID: <141d01c99c38$04e26fa0$0600a8c0@china.huawei.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
In-reply-to: <001f01c99c25$99418220$0601a8c0@allison>
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
Thread-index: AcmcLjgTY17Gu9lFR0C7iiNgfDauaQACKp3Q
Subject: Re: [OPSAWG] (final) WGLCondraft-ietf-opsawg-operations-and-management
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Mar 2009 19:40:53 -0000

Hi Tom,

I believe another document is being written that discusses what OAM
means.
That is not the task we have undertaken here. What you are proposing
seems to be a different type of document. By all means, feel free to
write a draft along the idea of your suggestion.

I do not have a citation, but when this was raised early (possibly
before adopting the draft as a WG draft), the WG deicded we should
avoid trying to boil the ocean, avoid tryin to distinguish between
devices and services and network, and so on. The WG agreed to focus on
developing a list of items that should be considered by protocol
document authors. Our resulting document should be able to be used to
guide authors and reviewers what was expected, and should include a
checklist of things a reviewer should check for.

dbh

> -----Original Message-----
> From: tom.petch [mailto:cfinss@dial.pipex.com] 
> Sent: Tuesday, March 03, 2009 11:41 AM
> To: David Harrington; 'Adrian Farrel'; opsawg@ietf.org
> Cc: 'David B Harrington'; tseely5@gmail.com
> Subject: Re: [OPSAWG] (final) 
> WGLCondraft-ietf-opsawg-operations-and-management
> 
> ----- Original Message -----
> From: "David Harrington" <ietfdbh@comcast.net>
> To: "'tom.petch'" <cfinss@dial.pipex.com>; "'Adrian Farrel'"
> <adrian@olddog.co.uk>; <opsawg@ietf.org>
> Cc: "'David B Harrington'" <dbharrington@comcast.net>; 
> <tseely5@gmail.com>
> Sent: Tuesday, February 10, 2009 9:21 PM
> Subject: RE: [OPSAWG] (final) 
> WGLCondraft-ietf-opsawg-operations-and-management
> 
> 
> > Besides the comments form Juergen, Mike, and Adrian, what 
> needs to be
> > done to make this live up to its billing? Do you have explicit
> > recommendations of text?
> >
> 
> Not so much text as a different approach; I would be more 
> radical than the
> others.
> 
> It is billed as guidelines to protocol designers so should 
> address what is OAM
> and how it can benefit from being built into the protocol.
> 
> OAM has two radically different meanings within the IETF and 
> so I think it
> important to say what it is.  And this immediately becomes 
> subjective.   For me,
> it is delivering service and so the protocol needs to be 
> clear what service it
> offers; reliability, security, flow control,  ..... there are 
> many aspects but
> few protocol designers seem to document them except where 
> they are forced to.
> Happily, I see several ADs insisting on threats to security 
> being defined before
> the WG just says encrypt everything:-)  Defence against a 
> threat is part of the
> service just as regarding some threats as out of scope is 
> saying they are not
> part of the service.  So the starting point for me can only 
> be a definition of
> service, in regard to OAM, and that I do not often see in I-Ds.
> 
> Then it is a question of what a protocol can do.  Simple 
> things protocols, an
> exchange of messages, the need to cater for messages being 
> lost, corrupted and
> duplicated, some defined fields and their semantics.  If your 
> concern is eg lost
> messages, then you include sequencing in some shape or form; 
> if your concern is
> availability, then you may consider heartbeats but be 
> careful, some networks
> echo back your data so if there is nothing to distinguish a 
> heartbeat from a
> heartbeat response, then you may get fooled by a totally dead
network.
> 
> Or again, is migration needed?  Yes, always.  If this is the 
> first, then it will
> not be perfect and will need migrating to something better.  
> If this is not the
> first, then you need to migrate to it.  Ergo, migration will 
> always happen.
> Therefore you need a 100% reliable way of differentiating old 
> from new, and of
> ensuring that old boxes behave predictably when confronted 
> with new (if version
> NE 1, then send Notification) and this needs building in when 
> you design the old
> protocol; by the time you are designing the new, it is too 
> late.  There are
> plenty of examples of how not to do it.
> 
> Will the protocol need expanding?  Yes, beyond your wildest 
> dreams.  OSI had the
> right idea when it allowed BER.1 a length of 2**127-1; I 
> think that that should
> satisfy anyone's dreams:-)  But look at tcpm and their 
> agonies with TCP option
> space.  If only the original designers had had more foresight.
> 
> The structure of fields and encoding in some protocols is 
> just designed to
> induce faults, mostly from inconsistency; some fields count 
> from zero, others
> don't, some are fixed length, others are TLV, mix it all up 
> for reasons that
> seem good at the time and you have a fault-prone system.
> 
> Binary encoding, text, structured text (XML) lots of ways of doing
it;
> consistency, familiarity and lack of surpises for the user 
> make for a good
> protocol for OAM, less likely to go wrong, easier to troubleshoot.
> 
> That should give you some flavour of what I would like to 
> see, not in the
> specific examples but in the general approach; what is OAM to 
> you, what can be
> done in the structure, in the semantics, in the concepts 
> usually represented by
> a state diagram (not sure what the right term for that is) to 
> achieve the goal.
> 
> Tom Petch
> 
> > dbh
> >
> > > -----Original Message-----
> > > From: opsawg-bounces@ietf.org
> > > [mailto:opsawg-bounces@ietf.org] On Behalf Of tom.petch
> > > Sent: Tuesday, February 10, 2009 12:05 PM
> > > To: Adrian Farrel; opsawg@ietf.org
> > > Cc: David B Harrington; tseely5@gmail.com
> > > Subject: Re: [OPSAWG] (final)
> > > WGLCondraft-ietf-opsawg-operations-and-management
> > >
> > > I was going to say +1 to Juergen's comments and then I was
> > > going to say +1 to
> > > Mike's comments and then I was going to say +1 to Adrian's
> > > comments and while I
> > > was pondering, ... I left it too late:-(
> > >
> > > But I do echo much of what has been said.  I cannot see that
> > > this I-D lives up
> > > to its billing.  It is a good idea, and it is good stuff
> > > (give or take some
> > > infelicities of wording, most of which have been pointed out
> > > already) but I do
> > > not see it as good stuff for a working group coming up with a
> > > new protocol, say
> > > an MPLS-TP or sieve or sidr. And that is what I think is
> > > needed.  If something
> > > is not designed to be managed ab initio, then it may be
> > > costly, impossible even,
> > > to manage it in the wild.
> > >
> > > Tom Petch
> > >
> > >
> > > ----- Original Message -----
> > > From: "Adrian Farrel" <adrian@olddog.co.uk>
> > > To: <opsawg@ietf.org>
> > > Cc: "David B Harrington" <dbharrington@comcast.net>;
> > > <tseely5@gmail.com>
> > > Sent: Wednesday, February 04, 2009 8:54 PM
> > > Subject: Re: [OPSAWG] (final) WGLC
> > > ondraft-ietf-opsawg-operations-and-management
> > >
> > >
> > > > Hi,
> > > >
> > > > Dan asked me to have a look at this which I do primarily
> > > with a routing area
> > > > view on the world.
> > > >
> > > > I'm sorry that I haven't been following this I-D very
> > > closely and apologise
> > > > if you have already discussed and reached conclusion on
> > > some of the points I
> > > > make.
> > > >
> > > > I am largely supportive of this work (see
> > > > draft-ietf-pce-manageability-requirements-06.txt), but I do
> > > have some
> > > > issues. I would be comforted to know that the I-D had had
> > > extensive review
> > > > from within the Ops Area without relying just on my comments!
> > > >
> > > > I would also like to understand how the recommendations
> > > parts of the draft
> > > > will be interpreted by the Ops ADs as they perform IESG
> > > review of I-Ds from
> > > > other areas. Depending on the answer (which I would like to
> > > see encapsulated
> > > > in the document!) I might have other harsher comments about
> > > the content.
> > > >
> > > > More details below.
> > > >
> > > > Cheers,
> > > > Adrian
> > > >
> > > > ===
> > > > Title is...
> > > >  Guidelines for Considering Operations and Management of
> > > New Protocols
> > > > ...but the Abstract immediately includes...
> > > >    New protocols or protocol extensions
> > > > ===
> > > > Obviously needs the new IPR boilerplate.
> > > > ===
> > > > Abstract line 3
> > > > s/protocol/protocols/
> > > > ===
> > > > I am somewhat worried by "recommend appropriate standard
> > management
> > > > protocols ... to address the relevant operations and
management
> > > > needs."
> > > >
> > > > I understand the theory behind this guidance in terms of
making
> > > > equipment that will interwork with management systems, but I
> > > > question its practicality given the vast array of management
> > > > protocols available. And actually, I am not sure that this has
a
> > > > direct impact on the success of or development of a protocol.
> > > >
> > > > The introduction says that this "is similar to a WG
considering
> > > > which security threats are relevant to their protocol, and
then
> > > > recommending appropriate standard security protocols to
mitigate
> > > > the relevant threats." I dispute this. The security 
> considerations
> > > > normally make modifications to the protocol under development
to
> > > > make it secure, or mandate security features in other
protocols
> > > > that the protocol under development uses. But where there is a
> > > > need for an external protocol, this is not usually mandated.
For
> > > > example, where key exchange is needed the text will usually
say
> > > > something like "may use some form of secure key 
> exchange protocol
> > > > (such as the Internet Key Exchange protocol v2 (IKE)
[RFC4306]."
> > > > This is far looser than a recommendation of a specific
protocol.
> > > >
> > > > I believe that in practice operators want to go on using the
> > > > management protocols that they already have deployed. If, for
> > > > example, I have deployed routers that I manage using 
> SNMP, I will
> > > > not want to deploy a new routing protocol on those 
> routers if that
> > > > protocol is strongly recommended to be managed using TL1.
> > > >
> > > > Since data modeling is usually tied closely to the protocol
used
> > > > for management, it follows from this that developing specific
> > > > data formats (SNMP MIB modules, XML schema, etc.) might also
not
> > > > be so very practical. (Arguably we have found this out with
MIB
> > > > modules over the last 10 years, but still churn them out.)
> > > >
> > > > What *would* be beneficial, however, is an abstract data model
> > > > for management of the protocol. There are many ways of
> > > > representing the data (XML, BNF, ASN.1, graphical 
> representation,
> > > > etc.) and the Ops Area could usefully pick one and standardise
> > > > it. From there we would have a solid data set that all
> > > > implementations could make available and which separate 
> documents
> > > > could easily map to suitable formats for use by specific
> > > > management protocols. Smart implementers would be able 
> to support
> > > > multiple management protocols with ease.
> > > >
> > > > You do come to this to some extent in section 4.1, and the
text
> > > > there seems to be at odds with what you have said in the
> > > > Introduction.
> > > >
> > > > ===
> > > > Section 1
> > > >
> > > > Can you expand "WG" on first usage?
> > > >
> > > > ===
> > > > Section 1
> > > >
> > > >    We want to avoid seeming to impose a solution by putting
> > > in place a
> > > >    strict terminology - for example implying that a formal
> > > data model,
> > > >    or even using a management protocol is mandatory.
> > > >
> > > > <grin mode=wry>
> > > >
> > > > You want to avoid seeming to impose it?
> > > > So, you want to impose it, but you don't want anyone to
notice?
> > > >
> > > > </grin>
> > > >
> > > > ===
> > > > Section 1
> > > >
> > > >    Making a Management Considerations section a mandatory
> > > publication
> > > >    requirement for IETF documents is the responsibility of
> > > the IESG, or
> > > >    specific area directors, or working groups, and this
> > > document avoids
> > > >    recommending any mandatory publication requirements.
> > > >
> > > > I think you may need to go a step further to get this 
> through the
> > > > IESG. It would not be funny to see this paragraph as 
> written, but
> > > > to get a DISCUSS on an I-D from an Ops AD because the 
> I-D did not
> > > > contain a Management Considerations section.
> > > >
> > > > ===
> > > > Introduction
> > > >
> > > >    We provide some objective criteria to promote 
> interoperability
> > > >
> > > > <grin mode=laconic>
> > > >
> > > > There seems to be only one author. Are you royalty?
> > > > Perhaps... "This document provides..."
> > > >
> > > > </grin>
> > > >
> > > > ===
> > > > Section 1 final line
> > > >
> > > > s/??/?"/
> > > >
> > > > ===
> > > >
> > > > 2.1.  IETF Management Framework
> > > >
> > > >    For years the IETF has stressed the use of the IETF
Standard
> > > >    Management Framework and MIB modules [RFC2578] for 
> managing new
> > > >    protocols.  The IETF designed these to permit multiple
> > > protocols to
> > > >    utilize the MIB data [RFC1052], but it became a common
> > > >
> > > > s/became/is/
> > > >
> > > > ===
> > > >
> > > > 3.1.  Operations Model
> > > >
> > > >    o  what are the typical user interfaces - Command 
> line (CLI) or
> > > >       graphical user interface (GUI)?
> > > >
> > > > I am not sure that this last item is particularly relevant for
a
> > > > large number of the protocols designed in the IETF. We might
say
> > > > that the question is valid for a protocol such as FTP, but is
it
> > > > relevant for OSPF? Yes, there is a configuration interface to
a
> > > > device that runs OSPF, but it is surely nothing to do with the
> > > > protocol design how that interface works. Indeed, you might
> > > > reduce the question to: are the configuration 
> interfaces local or
> > > > remote? But I think you will find that the answer to 
> the question
> > > > is "both" as in the subsequent paragraph.
> > > >
> > > > ===
> > > >
> > > > 3.1.  Operations Model
> > > >
> > > >    Auto-configuration and default parameters might be
> > > >    possible for some new protocols.
> > > >
> > > > I would make a much bigger noise about default parameters.
There
> > is
> > > > a key question about how the protocol can operate "out of the
> > box".
> > > > If implementers are free to select their own defaults, the
> > protocol
> > > > needs to operate well with any choice of values. If there are
> > > > sensible defaults, these need to be stated.
> > > >
> > > > Indeed, section 3.2 seems to say this. Perhaps a forward
> > reference?
> > > >
> > > > ===
> > > >
> > > > 3.1.  Operations Model
> > > >
> > > >    There may be a need to support a human interface, e.g., for
> > > >    troubleshooting, and a programmatic interface, e.g., for
> > > automated
> > > >    monitoring and root cause analysis.  It might be
> > > important that the
> > > >    internal method routines used by the application
programming
> > > >    interfaces and the human interfaces should be the same
> > > to ensure that
> > > >    data exchanged between these two interfaces is always
> > consistent.
> > > >    Mixing methods leads to inconsistency, so identifying
> > consistent
> > > >    methods of retrieving information is relevant.
> > > >
> > > > This is really sailing too close to the implementation. People
> > > > must be free to construct sub-standard and unmarketable
> > > > implementations. The IETF is not responsible for making all
> > > > implementations successful. The job is to make it possible for
> > > > all implementations to be successful given core 
> competences in the
> > > > developers.
> > > >
> > > > I think the furthest a protocol spec RFC could go would 
> be to say
> > > > what information must be available to an operator at a human
> > > > interface for troubleshooting
> > > >
> > > > ===
> > > >
> > > > 3.2.  Installation and Initial Setup
> > > >
> > > > In view of the reasons you give why defaults might become out-
> > > > dated, you might point out that sometimes it is not advisable
to
> > > > have defaults. In these cases explicit configuration is 
> required.
> > > >
> > > > ===
> > > >
> > > > 3.2.  Installation and Initial Setup
> > > >
> > > > Is the text at the top of page 8 supposed to be a bullet list?
> > > >
> > > > ===
> > > >
> > > > 3.4.  Requirements on Other Protocols and Functional
Components
> > > >
> > > >    These considerations should generally remain
> > > illustrative to avoid
> > > >    creating restrictions or dependencies, or potentially
> > > impacting the
> > > >    behavior of existing protocols, or restricting the
> > > extensibility of
> > > >    other protocols, or assuming other protocols will not be
> > > extended in
> > > >    certain ways.
> > > >
> > > > Well, this is quite interesting.
> > > >
> > > > Suppose you decide to utilise a particular feature of a 
> transport
> > > > protocol. You are creating a hard requirement that that 
> feature is
> > > > implemented in all implementations of the set {your new 
> protocol,
> > > > the transport protocol}. But more importantly, perhaps, you
are
> > > > requiring that new versions of the transport protocol do not
> > > > deprecate the feature you require.
> > > >
> > > > In short, I don't think you should be too nervous about
creating
> > > > restrictions or dependencies. If they exist, they must 
> be stated.
> > > >
> > > > ===
> > > >
> > > > 3.2.  Installation and Initial Setup
> > > >
> > > >    For example, the design of Resource ReSerVation 
> Protocol (RSVP)
> > > >
> > > > I think this example is not well expressed.
> > > >
> > > > The problem in RSVP was that the IP packet was addressed to
the
> > > > ultimate RSVP-capable destination, but the RSVP-capable
routers
> > > > along the path needed to intercept and process the Path
message.
> > > > This they could only do by "deep packet inspection" or by the
> > > > router alert option.
> > > >
> > > > I wonder whether this example adds significantly to the I-D.
> > > >
> > > > ===
> > > >
> > > > 4.  Management Considerations
> > > >
> > > >    NETCONF addresses this in a generic manner by
> > > >
> > > > Add citation.
> > > >
> > > > ===
> > > >
> > > > 4.  Management Considerations
> > > >
> > > >    However, debugging on-the-wire interactions is a protocol
> > > >    issue: it is enormously helpful if a protocol has 
> hooks to make
> > > >    debugging of network interactions easy, and/or is
> > > designed in such a
> > > >    way that debugging protocol behaviors is easy.
> > > Hand-waving this away
> > > >    is not something that operators like ...
> > > >
> > > > I think you are including this by hand-waving!
> > > > What do you mean by "hooks"?
> > > > Surely any protocol can be debugged simply by sniffing it.
> > > > If you have specific hooks in mind you must set them out and
not
> > > > leave the reader guessing.
> > > > But if you force the implementation I shall be peeved!
> > > > You might, for example, say that there should be alerts issued
> > when
> > > > messages are received, or when there are state 
> transitions in the
> > > > protocol state machine, but you must recall that:
> > > > - the messages can be seen by sniffing
> > > > - the state machine is not part of the protocol specification.
> > > > This latter point is key. The state machine explains how the
> > > > protocol works in order that an implementer can decide how to
> > > > react to a received event, but it does not require that the
> > > > machine is implemented.
> > > >
> > > > ===
> > > >
> > > > 4.1.  Interoperability
> > > >
> > > >    Interoperability needs to be considered on the syntactic
> > > level and
> > > >    the semantic level.  While it can be irritating and
> > > time-consuming,
> > > >    application designers including operators who write
> > > their own scripts
> > > >    can make their processing conditional to accommodate
> > differences
> > > >
> > > > s/differences/syntactic differences/ ?
> > > >
> > > >    Then, whether the counter is gathered via SNMP or a CLI
> > > >    command or a SYSLOG message, the counter will have
> > > similar meaning.
> > > >
> > > > "similar"? I think that might not be good enough. Don't you
need
> > > > "the same"?
> > > >
> > > >    o  [RFC3805] - Printer MIB v2 (contains both an IM and a DM
> > > >
> > > > Missing ")"
> > > >
> > > > ===
> > > >
> > > > 4.2.  Management Information
> > > >
> > > > I would find it really helpful if you were able to recommend a
> > > > language in which to write the information model. Ideally, all
> > > > IETF IMs would be in the same language.
> > > >
> > > >    It is important to be able to separately fetch
> > > configuration data,
> > > >    operational state data, and statistics from devices, and
> > > to be able
> > > >    to compare current state to initial state, and to 
> compare data
> > > >    between devices.
> > > >
> > > > You seem to have drifted into DMs here. You cannot 
> fetch data from
> > > > an IM. It simply explains what data elements exist. In 
> fact, an IM
> > > > states all of the data that exists and so there is no
confusion.
> > > > Confusion can only arise as the DM is constructed and 
> multiple IM
> > > > data elements are conflated into single DM objects.
> > > >
> > > > ===
> > > >
> > > > 4.3.  Fault Management
> > > >
> > > >    The protocol designer should document the basic faults and
> > health
> > > >    indicators that need to be instrumented for the new
> > > protocol, and the
> > > >    alarms and events that must be propagated to management
> > > applications
> > > >    or exposed through a data model.
> > > >
> > > > Isn't "propagated to management applications" a subset 
> of "exposed
> > > > through a data model"?
> > > >
> > > >    The protocol designer should consider how faults
> > > information will be
> > > >
> > > > s/faults/fault/
> > > >
> > > >    Should the event reporting provide gyaranteed accurate
> > > delivery of
> > > > s/gyaranteed/guaranteed/
> > > >
> > > > ===
> > > >
> > > > 4.3.3.  Fault Isolation
> > > >
> > > >    It might be useful to isolate faults, such as a system that
> > emits
> > > >    malformed messages necessary to coordinate connections
> > properly.
> > > >    Spanning tree comes to mind.  This might be able to 
> be done by
> > > >    configuring next-hop devices to drop the faulty messages
> > > to prevent
> > > >    them from entering the rest of the network.
> > > >
> > > > This is not what *I* mean by fault isolation!
> > > > Fault isolation is about working out where in the network the
> > fault
> > > > is. For example, if end-to-end data delivery is failing 
> (reported
> > by
> > > > a notification), fault isolation will find the failed 
> link or node
> > > > in the end-to-end path.
> > > >
> > > > You seem to be describing the process of quarantining faulty
> > > > devices. This may also be valuable.
> > > >
> > > > "Spanning tree comes to mind" is a rather strange 
> sentence without
> > > > much context.
> > > >
> > > > ===
> > > >
> > > > 4.4.  Configuration Management
> > > >
> > > >    A protocol desoigners should document what the basic
> > > configuration
> > > >
> > > > s/desoigners/designers/
> > > >
> > > >    "Requirements for Configuration Management of IP-based
> > Networks"
> > > >    [RFC3139] discusses requirements for configuration 
> management.
> > > > More precisely,
> > > >    "Requirements for Configuration Management of IP-based
> > Networks"
> > > >    [RFC3139] discusses requirements for configuration
management
> > of
> > > >    IP-based networks.
> > > > Which makes me wonder about the purpose of the sentence :-)
> > > >
> > > >    This document includes...
> > > > This document or that document?
> > > >
> > > >    A number of efforts have existed in the IETF to develop
> > > policy-based
> > > >    management.  "Terminology for Policy-Based Management"
> > > [RFC3198] was
> > > >    written to standardize the terminology across these
> > > efforts.  Some of
> > > >    the efforts resulted in proposals that are NOT 
> RECOMMENDED, so
> > a
> > > >    protocol designer should check the current recommendation
> > status
> > > >    before depending on a specific protocol suggestion.
> > > >
> > > > You have used RFC2119 language, but in section 1.1 you said
> > > >    This document deliberately does not use the
> > > (capitalized) keywords
> > > >    described in RFC 2119 [RFC2119].
> > > > Furthermore, it is not clear to me whether this I-D is doing
the
> > > > NOT RECOMMENDing or whether some other RFC has done it. If it
is
> > > > this I-D, you will need to give reasons. If is some 
> other RFC, you
> > > > will need to give references.
> > > >
> > > >    It is highly desirable that text processing tools such
> > > as diff, and
> > > >    version management tools such as RCS or CVS or SVN, can
> > > be used to
> > > >    process configurations.  This approach simplifies 
> comparing the
> > > >    current operational state to the initial 
> configuration.  It is
> > > >    commonplace to compare configuration changes to e.g.,
> > > last day, last
> > > >    week, last month, etc. -- having configuration in a
> > > text, and human-
> > > >    understandable format is very valuable for various
> > > reasons such as
> > > >    change control (or verification), configuration
> > > consistency checks,
> > > >    etc.
> > > >
> > > > Yes, but what has this to do with the protocol design? 
> It might be
> > > > related to device implementation. Or it might be relevant to
> > > > EMS/NMS implementation.
> > > >
> > > > As you note in the subsequent paragraph, this may be
impossible
> > > > even in some text-based DMs. It would certainly be impossible
in
> > > > an SNMP MIB module.
> > > >
> > > >    To simplify such configuration comparisons, devices 
> should not
> > > >    arbitrarily reorder data such as access control lists.
> > > If a protocol
> > > >    designer defines mechanisms for configuration, it would
> > > be desirable
> > > >    to standardize the order of elements for consistency of
> > > configuration
> > > >    and of reporting across vendors, and across releases
> > > from vendors.
> > > >
> > > > This example seems a bit specific. And in any case, it is
> > perfectly
> > > > possible to sort a list before comparing.
> > > >
> > > >    There are two parts to this: 1.  An NMS system could
> > > optimize ACLs
> > > >    for performance reasons 2.  Unless the device/NMS
> > > systems has correct
> > > >    rules/a lot of experience, reordering ACLs can lead to a
huge
> > > >    security issue.
> > > >
> > > > Maybe what you are saying is:
> > > >    Implementations should not arbitrarily modify configuration
> > data.
> > > >    In some cases (such as Access Control Lists) the 
> order of data
> > > >    items is significant and comprises part of the 
> configured data.
> > > >
> > > >    Network wide configurations are ideally stored in central
> > master
> > > >    databases
> > > >
> > > > This looks like an unsubstantiated assertion. You might get
away
> > > > with "Many operators prefer that..."
> > > >
> > > >    It is important to distinguish between the distribution of
> > > >    configurations and the activation of a certain
configuration.
> > > >    Devices should be able to hold multiple configurations.
> > > >
> > > > This is really an implementation issue and nothing to 
> do with the
> > > > protocol under design.
> > > >
> > > >    Consensus of the 2002 IAB Workshop was that textual
> > configuration
> > > >    files should be able to contain international characters.
> > > >
> > > > Do you have a citation?
> > > >
> > > >    These timers may need default values
> > > >    suggested in the protocol specification and do not need to
be
> > > >    otherwise configurable.
> > > >
> > > > I had formed the opinion that timers must be given 
> default values
> > > > in IETF protocol specifications, but I can't lay my hands on a
> > > > reference.
> > > >
> > > > ===
> > > >
> > > > 4.5.  Accounting Management
> > > >
> > > >    A protocol designer should consider whether it would be
> > > appropriate
> > > >    to collect usage information related to this protocol, and
if
> > so,
> > > >    what usage information would be appropriate to collect?
> > > >
> > > > s/collect?/collect./
> > > >
> > > >    "Introduction to Accounting Management" [RFC2975]
> > > discusses a number
> > > >    of factors relevant to monitoring usage of protocols for
> > > purposes of
> > > >    capacity and trend analysis, cost allocation, auditing,
> > > and billing.
> > > >    This document also discusses how Remote Authentication
> > > Dial In User
> > > > This or that?
> > > >
> > > >    Service (RADIUS) [RFC2865], Terminal Access Controller
> > > Access Control
> > > >    System (TACACS) [RFC1492], SNMP, IPFIX, and Packet
> > > Sampling (PSAMP)
> > > >    Protocol [I-D.ietf-psamp-protocol] protocols can be used
> > > for these
> > > >    purposes.
> > > >
> > > > Surely RFC 2975 does not mention PSAMP? Which makes me 
> wonder what
> > > > you are trying to achieve with a list of example protocols.
Are
> > > > they intended as recommendations (in which case say so and
why),
> > > > or as a non-exclusive list (in which case a "such as" would be
> > > > useful). At the moment it reads like these are your 
> favorites and
> > > > you would be upset if someone used a different protocol!
> > > >
> > > > ===
> > > >
> > > > 4.6.  Performance Management
> > > >
> > > >    There are several parts to performance management to be
> > > considered:
> > > >    protocol monitoring, services monitoring, and device
> > > monitoring (the
> > > >    impact of the new protocol/service activation on the
device).
> > > >
> > > > s/services/service/
> > > >
> > > >    Consider scalability, such as whether performance will
> > > be affected by
> > > >    the number of protocol connections.
> > > >
> > > > Maybe say "protocol entities" rather than connections?
> > > >
> > > >
> > > > This section seems to flit between the performance of 
> the protocol
> > > > under design and the network running the protocol under
design,
> > and
> > > > the performance of the management of the protocol. Each is
> > > > important, but it may be constructive to split them out into
> > > > separate sections. The latter will also include a 
> consideration of
> > > > how the act of monitoring impacts on network performance.
> > > >
> > > >
> > > >    The Benchmarking Methodology WG (bmwg) has defined
> > > recommendations
> > > > Later you have BMWG.
> > > >
> > > > ===
> > > >
> > > > 4.7.  Security Management
> > > >
> > > >    It must be possible to do consistency checks of access
> > > control lists
> > > >    across devices.  Protocol designers should consider 
> information
> > > >    models to promote comparisons across devices and across
> > > vendors to
> > > >    permit checking the consistency of security configurations.
> > > >
> > > > I think this "must" is massively excessive!
> > > > I would expect each router to have a different access 
> list in the
> > > > control plane (a list of its neighbors). Such a mechanism
would
> > > > actually open up a security vulnerability that has to be
> > protected.
> > > > Perhaps you are talking about management plane access 
> lists. This
> > > > takes us into the area of securing management activity - see
my
> > > > comments on Section 7.
> > > >
> > > >    RADIUS and DIAMETER can provide authentication and
> > > authorization.  A
> > > >    protocol designer should consider which attributes would be
> > > >    appropriate for their protocol.
> > > >
> > > > This paragraph is apropos of what? What are you trying 
> to tell me?
> > > > Should I run my management using Radius? Should I try to build
> > > > Diameter into my new protocol?
> > > >
> > > >    Different protocols use different assumptions about
> > > message security
> > > > s/protocols/management protocols/
> > > >
> > > >    and data access controls.  A protocol designer that
> > > recommends using
> > > >    different protocols should consider how security will be
> > > applied in a
> > > > s/protocols/management protocols/
> > > >
> > > >
> > > > Although you talk about (presumably management) access
> > > lists, I think
> > > > I would have expected a discussion of authority levels 
> and policy
> > > > with regard to management tasks.
> > > >
> > > > ===
> > > >
> > > > 7.  Security Considerations
> > > >
> > > >    This document is informational and provides guidelines for
> > > >    considering manageability and operations.  It 
> introduces no new
> > > >    security concerns.
> > > >
> > > > I think that, although you introduce no new security concerns
> > > > directly, you have some things to talk about.
> > > >
> > > > Firstly, the provision of a management portal to a 
> network device
> > > > provides a doorway through which an attack on the device may
be
> > > > launched. Since you are recommending that the protocol under
> > > > development be manageable through the management 
> protocol, you are
> > > > requiring that the protocol be vulnerable to a new source of
> > > > attacks. Therefore, you must talk about securing the protocol
> > > > against these attacks. This might be as simple as 
> saying that only
> > > > management protocols with adequate (for some definition of
> > > > adequate) security apparatus be used.
> > > >
> > > > I think it is also of note that a standard description of the
> > > > manageable knobs and whistles on a protocol makes it 
> easier for an
> > > > attacker to understand what they may try to control and how to
> > > > tweak it.
> > > >
> > > > On the other hand, it would be well worth pointing out that a
> > > > well-designed protocol is usually more stable and 
> secure. And that
> > > > a protocol that can be managed and inspected offers the
operator
> > > > a better chance of spotting and quarantining any attacks.
> > > > Conversely making a protocol inspectable, is a risk if the
wrong
> > > > person inspects it!
> > > >
> > > > If security events cause logs and or notifications/alerts, can
> > > > a concerted attack be mounted by causing an excess of these
> > > > events? In other words, to the security management mechanisms
> > > > constitute the security vulnerability?
> > > >
> > > > Lastly, the management of security aspects is important, and
you
> > > > can just reference back to section 4.7.
> > > >
> > > > ===
> > > >
> > > > 9.  Informative References
> > > >
> > > > I (of course) would favor an informational reference to
> > > draft-ietf-pce-
> > > > manageability-requirements-06.txt
> > > >
> > > > ===
> > > >
> > > >    [RFC2821]                       Klensin, J., "Simple
> > > Mail Transfer
> > > >                                    Protocol", RFC 2821, April
> > 2001.
> > > >
> > > > I think this has been obsoleted.
> > > >
> > > > ===
> > > >
> > > > Appendix A.  Operations and Management Review Checklist
> > > >
> > > > Maybe a forward reference to this appendix from 
> sections 1 and 5?
> > > >
> > > > ===
> > > >
> > > > A.3.  Documentation
> > > >
> > > >    Does the proposed protocol have a significant
> > > operational impact on
> > > >    the Internet.  If it does, and the document under review
> > targets
> > > >    standards track, is their enough proof of 
> implementation and/or
> > > >    operational experience to grant Proposed Standard status?
> > > >
> > > > Whoah!
> > > >
> > > > You are going to use this I-D to try to block standards 
> track I-Ds
> > > > from becoming RFCs? You are going to get into such a fight!!!
> > > >
> > > > IMHO this sentence is a complete show-stopper in your I-D.
> > > >
> > > > (Oh, and s/their/there/)
> > > >
> > > > ===
> > > >
> > > > Appendix B.  Change Log
> > > >
> > > > Suggest you flag this for removal upon publication as an RFC.
> > > >
> > > > ===
> > > >
> > > > > Sent: Sunday, January 25, 2009 6:40 PM
> > > > > To: opsawg@ietf.org
> > > > > Subject: [OPSAWG] (final) WGLC on
> > > > > draft-ietf-opsawg-operations-and-management
> > > > >
> > > > > This is a (hopefully final) WGLC for
> > > > > draft-ietf-opsawg-operations-and-management
> > > > > there was not enough respose to the last one back in October
> > > > > please let the list know what you think of the draft
> > > >
> > > > _______________________________________________
> > > > OPSAWG mailing list
> > > > OPSAWG@ietf.org
> > > > https://www.ietf.org/mailman/listinfo/opsawg
> > >
> > > _______________________________________________
> > > OPSAWG mailing list
> > > OPSAWG@ietf.org
> > > https://www.ietf.org/mailman/listinfo/opsawg
> > >
> >
> 
> 


From dromasca@avaya.com  Thu Mar  5 08:18:47 2009
Return-Path: <dromasca@avaya.com>
X-Original-To: opsawg@core3.amsl.com
Delivered-To: opsawg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 234B33A684B for <opsawg@core3.amsl.com>; Thu,  5 Mar 2009 08:18:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.226
X-Spam-Level: 
X-Spam-Status: No, score=-2.226 tagged_above=-999 required=5 tests=[AWL=-0.227, BAYES_00=-2.599, J_CHICKENPOX_35=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FxtwG-s4Ro83 for <opsawg@core3.amsl.com>; Thu,  5 Mar 2009 08:18:44 -0800 (PST)
Received: from nj300815-nj-outbound.net.avaya.com (nj300815-nj-outbound.net.avaya.com [198.152.12.100]) by core3.amsl.com (Postfix) with ESMTP id 96BE33A694A for <opsawg@ietf.org>; Thu,  5 Mar 2009 08:18:43 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.38,307,1233550800"; d="scan'208";a="154334215"
Received: from unknown (HELO nj300815-nj-erheast.avaya.com) ([198.152.6.5]) by nj300815-nj-outbound.net.avaya.com with ESMTP; 05 Mar 2009 11:19:12 -0500
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.15]) by nj300815-nj-erheast-out.avaya.com with ESMTP; 05 Mar 2009 11:19:12 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 5 Mar 2009 17:19:00 +0100
Message-ID: <EDC652A26FB23C4EB6384A4584434A040149435D@307622ANEX5.global.avaya.com>
In-Reply-To: <141d01c99c38$04e26fa0$0600a8c0@china.huawei.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [OPSAWG] (final)WGLCondraft-ietf-opsawg-operations-and-management
Thread-Index: AcmcLjgTY17Gu9lFR0C7iiNgfDauaQACKp3QAF28beA=
References: <EDC652A26FB23C4EB6384A4584434A040132E373@307622ANEX5.global.avaya.com><5C8D68E9DDC2439B82F3CC0591A54F05@your029b8cecfe><000801c98ba3$80df0780$0601a8c0@allison><003601c98bbd$19086470$0600a8c0@china.huawei.com><001f01c99c25$99418220$0601a8c0@allison> <141d01c99c38$04e26fa0$0600a8c0@china.huawei.com>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "David B Harrington" <dbharrington@comcast.net>, <opsawg@ietf.org>
Subject: Re: [OPSAWG] (final)WGLCondraft-ietf-opsawg-operations-and-management
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Mar 2009 16:18:47 -0000

The draft David refers to is
http://www.ietf.org/internet-drafts/draft-andersson-mpls-tp-oam-def-01.t
xt

Which reminds me that the authors of that draft would be glad to hear
some feedback, and especially whether there is interest in the OPSAWG to
proceed with that work.=20

Dan
=20

> -----Original Message-----
> From: opsawg-bounces@ietf.org=20
> [mailto:opsawg-bounces@ietf.org] On Behalf Of David B Harrington
> Sent: Tuesday, March 03, 2009 9:41 PM
> To: opsawg@ietf.org
> Subject: Re: [OPSAWG]=20
> (final)WGLCondraft-ietf-opsawg-operations-and-management
>=20
> Hi Tom,
>=20
> I believe another document is being written that discusses=20
> what OAM means.
> That is not the task we have undertaken here. What you are=20
> proposing seems to be a different type of document. By all=20
> means, feel free to write a draft along the idea of your suggestion.
>=20
> I do not have a citation, but when this was raised early=20
> (possibly before adopting the draft as a WG draft), the WG=20
> deicded we should avoid trying to boil the ocean, avoid tryin=20
> to distinguish between devices and services and network, and=20
> so on. The WG agreed to focus on developing a list of items=20
> that should be considered by protocol document authors. Our=20
> resulting document should be able to be used to guide authors=20
> and reviewers what was expected, and should include a=20
> checklist of things a reviewer should check for.
>=20
> dbh
>=20
> > -----Original Message-----
> > From: tom.petch [mailto:cfinss@dial.pipex.com]
> > Sent: Tuesday, March 03, 2009 11:41 AM
> > To: David Harrington; 'Adrian Farrel'; opsawg@ietf.org
> > Cc: 'David B Harrington'; tseely5@gmail.com
> > Subject: Re: [OPSAWG] (final)
> > WGLCondraft-ietf-opsawg-operations-and-management
> >=20
> > ----- Original Message -----
> > From: "David Harrington" <ietfdbh@comcast.net>
> > To: "'tom.petch'" <cfinss@dial.pipex.com>; "'Adrian Farrel'"
> > <adrian@olddog.co.uk>; <opsawg@ietf.org>
> > Cc: "'David B Harrington'" <dbharrington@comcast.net>;=20
> > <tseely5@gmail.com>
> > Sent: Tuesday, February 10, 2009 9:21 PM
> > Subject: RE: [OPSAWG] (final)
> > WGLCondraft-ietf-opsawg-operations-and-management
> >=20
> >=20
> > > Besides the comments form Juergen, Mike, and Adrian, what
> > needs to be
> > > done to make this live up to its billing? Do you have explicit=20
> > > recommendations of text?
> > >
> >=20
> > Not so much text as a different approach; I would be more=20
> radical than=20
> > the others.
> >=20
> > It is billed as guidelines to protocol designers so should address=20
> > what is OAM and how it can benefit from being built into=20
> the protocol.
> >=20
> > OAM has two radically different meanings within the IETF and so I=20
> > think it important to say what it is.  And this immediately becomes
> > subjective.   For me,
> > it is delivering service and so the protocol needs to be clear what=20
> > service it offers; reliability, security, flow control, =20
> ..... there=20
> > are many aspects but few protocol designers seem to document them=20
> > except where they are forced to.
> > Happily, I see several ADs insisting on threats to security being=20
> > defined before the WG just says encrypt everything:-) =20
> Defence against=20
> > a threat is part of the service just as regarding some=20
> threats as out=20
> > of scope is saying they are not part of the service.  So=20
> the starting=20
> > point for me can only be a definition of service, in regard to OAM,=20
> > and that I do not often see in I-Ds.
> >=20
> > Then it is a question of what a protocol can do.  Simple things=20
> > protocols, an exchange of messages, the need to cater for messages=20
> > being lost, corrupted and duplicated, some defined fields and their=20
> > semantics.  If your concern is eg lost messages, then you include=20
> > sequencing in some shape or form; if your concern is availability,=20
> > then you may consider heartbeats but be careful, some networks echo=20
> > back your data so if there is nothing to distinguish a=20
> heartbeat from=20
> > a heartbeat response, then you may get fooled by a totally dead
> network.
> >=20
> > Or again, is migration needed?  Yes, always.  If this is the first,=20
> > then it will not be perfect and will need migrating to something=20
> > better.
> > If this is not the
> > first, then you need to migrate to it.  Ergo, migration will always=20
> > happen.
> > Therefore you need a 100% reliable way of differentiating old from=20
> > new, and of ensuring that old boxes behave predictably when=20
> confronted=20
> > with new (if version NE 1, then send Notification) and this needs=20
> > building in when you design the old protocol; by the time you are=20
> > designing the new, it is too late.  There are plenty of examples of=20
> > how not to do it.
> >=20
> > Will the protocol need expanding?  Yes, beyond your wildest=20
> dreams. =20
> > OSI had the right idea when it allowed BER.1 a length of=20
> 2**127-1; I=20
> > think that that should satisfy anyone's dreams:-)  But look at tcpm=20
> > and their agonies with TCP option space.  If only the original=20
> > designers had had more foresight.
> >=20
> > The structure of fields and encoding in some protocols is just=20
> > designed to induce faults, mostly from inconsistency; some fields=20
> > count from zero, others don't, some are fixed length,=20
> others are TLV,=20
> > mix it all up for reasons that seem good at the time and you have a=20
> > fault-prone system.
> >=20
> > Binary encoding, text, structured text (XML) lots of ways of doing
> it;
> > consistency, familiarity and lack of surpises for the user=20
> make for a=20
> > good protocol for OAM, less likely to go wrong, easier to=20
> > troubleshoot.
> >=20
> > That should give you some flavour of what I would like to=20
> see, not in=20
> > the specific examples but in the general approach; what is=20
> OAM to you,=20
> > what can be done in the structure, in the semantics, in the=20
> concepts=20
> > usually represented by a state diagram (not sure what the=20
> right term=20
> > for that is) to achieve the goal.
> >=20
> > Tom Petch
> >=20
> > > dbh
> > >
> > > > -----Original Message-----
> > > > From: opsawg-bounces@ietf.org
> > > > [mailto:opsawg-bounces@ietf.org] On Behalf Of tom.petch
> > > > Sent: Tuesday, February 10, 2009 12:05 PM
> > > > To: Adrian Farrel; opsawg@ietf.org
> > > > Cc: David B Harrington; tseely5@gmail.com
> > > > Subject: Re: [OPSAWG] (final)
> > > > WGLCondraft-ietf-opsawg-operations-and-management
> > > >
> > > > I was going to say +1 to Juergen's comments and then I=20
> was going=20
> > > > to say +1 to Mike's comments and then I was going to say +1 to=20
> > > > Adrian's comments and while I was pondering, ... I left it too=20
> > > > late:-(
> > > >
> > > > But I do echo much of what has been said.  I cannot see=20
> that this=20
> > > > I-D lives up to its billing.  It is a good idea, and it is good=20
> > > > stuff (give or take some infelicities of wording, most of which=20
> > > > have been pointed out
> > > > already) but I do
> > > > not see it as good stuff for a working group coming up=20
> with a new=20
> > > > protocol, say an MPLS-TP or sieve or sidr. And that is what I=20
> > > > think is needed.  If something is not designed to be managed ab=20
> > > > initio, then it may be costly, impossible even, to manage it in=20
> > > > the wild.
> > > >
> > > > Tom Petch
> > > >
> > > >
> > > > ----- Original Message -----
> > > > From: "Adrian Farrel" <adrian@olddog.co.uk>
> > > > To: <opsawg@ietf.org>
> > > > Cc: "David B Harrington" <dbharrington@comcast.net>;=20
> > > > <tseely5@gmail.com>
> > > > Sent: Wednesday, February 04, 2009 8:54 PM
> > > > Subject: Re: [OPSAWG] (final) WGLC=20
> > > > ondraft-ietf-opsawg-operations-and-management
> > > >
> > > >
> > > > > Hi,
> > > > >
> > > > > Dan asked me to have a look at this which I do primarily
> > > > with a routing area
> > > > > view on the world.
> > > > >
> > > > > I'm sorry that I haven't been following this I-D very
> > > > closely and apologise
> > > > > if you have already discussed and reached conclusion on
> > > > some of the points I
> > > > > make.
> > > > >
> > > > > I am largely supportive of this work (see=20
> > > > > draft-ietf-pce-manageability-requirements-06.txt), but I do
> > > > have some
> > > > > issues. I would be comforted to know that the I-D had had
> > > > extensive review
> > > > > from within the Ops Area without relying just on my comments!
> > > > >
> > > > > I would also like to understand how the recommendations
> > > > parts of the draft
> > > > > will be interpreted by the Ops ADs as they perform IESG
> > > > review of I-Ds from
> > > > > other areas. Depending on the answer (which I would like to
> > > > see encapsulated
> > > > > in the document!) I might have other harsher comments about
> > > > the content.
> > > > >
> > > > > More details below.
> > > > >
> > > > > Cheers,
> > > > > Adrian
> > > > >
> > > > > =3D=3D=3D
> > > > > Title is...
> > > > >  Guidelines for Considering Operations and Management of
> > > > New Protocols
> > > > > ...but the Abstract immediately includes...
> > > > >    New protocols or protocol extensions =3D=3D=3D Obviously=20
> needs the=20
> > > > > new IPR boilerplate.
> > > > > =3D=3D=3D
> > > > > Abstract line 3
> > > > > s/protocol/protocols/
> > > > > =3D=3D=3D
> > > > > I am somewhat worried by "recommend appropriate standard
> > > management
> > > > > protocols ... to address the relevant operations and
> management
> > > > > needs."
> > > > >
> > > > > I understand the theory behind this guidance in terms of
> making
> > > > > equipment that will interwork with management systems, but I=20
> > > > > question its practicality given the vast array of management=20
> > > > > protocols available. And actually, I am not sure that this has
> a
> > > > > direct impact on the success of or development of a protocol.
> > > > >
> > > > > The introduction says that this "is similar to a WG
> considering
> > > > > which security threats are relevant to their protocol, and
> then
> > > > > recommending appropriate standard security protocols to
> mitigate
> > > > > the relevant threats." I dispute this. The security
> > considerations
> > > > > normally make modifications to the protocol under development
> to
> > > > > make it secure, or mandate security features in other
> protocols
> > > > > that the protocol under development uses. But where=20
> there is a=20
> > > > > need for an external protocol, this is not usually mandated.
> For
> > > > > example, where key exchange is needed the text will usually
> say
> > > > > something like "may use some form of secure key
> > exchange protocol
> > > > > (such as the Internet Key Exchange protocol v2 (IKE)
> [RFC4306]."
> > > > > This is far looser than a recommendation of a specific
> protocol.
> > > > >
> > > > > I believe that in practice operators want to go on using the=20
> > > > > management protocols that they already have deployed. If, for=20
> > > > > example, I have deployed routers that I manage using
> > SNMP, I will
> > > > > not want to deploy a new routing protocol on those
> > routers if that
> > > > > protocol is strongly recommended to be managed using TL1.
> > > > >
> > > > > Since data modeling is usually tied closely to the protocol
> used
> > > > > for management, it follows from this that developing specific=20
> > > > > data formats (SNMP MIB modules, XML schema, etc.) might also
> not
> > > > > be so very practical. (Arguably we have found this out with
> MIB
> > > > > modules over the last 10 years, but still churn them out.)
> > > > >
> > > > > What *would* be beneficial, however, is an abstract=20
> data model=20
> > > > > for management of the protocol. There are many ways of=20
> > > > > representing the data (XML, BNF, ASN.1, graphical
> > representation,
> > > > > etc.) and the Ops Area could usefully pick one and=20
> standardise=20
> > > > > it. From there we would have a solid data set that all=20
> > > > > implementations could make available and which separate
> > documents
> > > > > could easily map to suitable formats for use by specific=20
> > > > > management protocols. Smart implementers would be able
> > to support
> > > > > multiple management protocols with ease.
> > > > >
> > > > > You do come to this to some extent in section 4.1, and the
> text
> > > > > there seems to be at odds with what you have said in the=20
> > > > > Introduction.
> > > > >
> > > > > =3D=3D=3D
> > > > > Section 1
> > > > >
> > > > > Can you expand "WG" on first usage?
> > > > >
> > > > > =3D=3D=3D
> > > > > Section 1
> > > > >
> > > > >    We want to avoid seeming to impose a solution by putting
> > > > in place a
> > > > >    strict terminology - for example implying that a formal
> > > > data model,
> > > > >    or even using a management protocol is mandatory.
> > > > >
> > > > > <grin mode=3Dwry>
> > > > >
> > > > > You want to avoid seeming to impose it?
> > > > > So, you want to impose it, but you don't want anyone to
> notice?
> > > > >
> > > > > </grin>
> > > > >
> > > > > =3D=3D=3D
> > > > > Section 1
> > > > >
> > > > >    Making a Management Considerations section a mandatory
> > > > publication
> > > > >    requirement for IETF documents is the responsibility of
> > > > the IESG, or
> > > > >    specific area directors, or working groups, and this
> > > > document avoids
> > > > >    recommending any mandatory publication requirements.
> > > > >
> > > > > I think you may need to go a step further to get this
> > through the
> > > > > IESG. It would not be funny to see this paragraph as
> > written, but
> > > > > to get a DISCUSS on an I-D from an Ops AD because the
> > I-D did not
> > > > > contain a Management Considerations section.
> > > > >
> > > > > =3D=3D=3D
> > > > > Introduction
> > > > >
> > > > >    We provide some objective criteria to promote
> > interoperability
> > > > >
> > > > > <grin mode=3Dlaconic>
> > > > >
> > > > > There seems to be only one author. Are you royalty?
> > > > > Perhaps... "This document provides..."
> > > > >
> > > > > </grin>
> > > > >
> > > > > =3D=3D=3D
> > > > > Section 1 final line
> > > > >
> > > > > s/??/?"/
> > > > >
> > > > > =3D=3D=3D
> > > > >
> > > > > 2.1.  IETF Management Framework
> > > > >
> > > > >    For years the IETF has stressed the use of the IETF
> Standard
> > > > >    Management Framework and MIB modules [RFC2578] for
> > managing new
> > > > >    protocols.  The IETF designed these to permit multiple
> > > > protocols to
> > > > >    utilize the MIB data [RFC1052], but it became a common
> > > > >
> > > > > s/became/is/
> > > > >
> > > > > =3D=3D=3D
> > > > >
> > > > > 3.1.  Operations Model
> > > > >
> > > > >    o  what are the typical user interfaces - Command
> > line (CLI) or
> > > > >       graphical user interface (GUI)?
> > > > >
> > > > > I am not sure that this last item is particularly relevant for
> a
> > > > > large number of the protocols designed in the IETF. We might
> say
> > > > > that the question is valid for a protocol such as FTP, but is
> it
> > > > > relevant for OSPF? Yes, there is a configuration interface to
> a
> > > > > device that runs OSPF, but it is surely nothing to do=20
> with the=20
> > > > > protocol design how that interface works. Indeed, you might=20
> > > > > reduce the question to: are the configuration
> > interfaces local or
> > > > > remote? But I think you will find that the answer to
> > the question
> > > > > is "both" as in the subsequent paragraph.
> > > > >
> > > > > =3D=3D=3D
> > > > >
> > > > > 3.1.  Operations Model
> > > > >
> > > > >    Auto-configuration and default parameters might be
> > > > >    possible for some new protocols.
> > > > >
> > > > > I would make a much bigger noise about default parameters.
> There
> > > is
> > > > > a key question about how the protocol can operate "out of the
> > > box".
> > > > > If implementers are free to select their own defaults, the
> > > protocol
> > > > > needs to operate well with any choice of values. If there are=20
> > > > > sensible defaults, these need to be stated.
> > > > >
> > > > > Indeed, section 3.2 seems to say this. Perhaps a forward
> > > reference?
> > > > >
> > > > > =3D=3D=3D
> > > > >
> > > > > 3.1.  Operations Model
> > > > >
> > > > >    There may be a need to support a human interface, e.g., for
> > > > >    troubleshooting, and a programmatic interface, e.g., for
> > > > automated
> > > > >    monitoring and root cause analysis.  It might be
> > > > important that the
> > > > >    internal method routines used by the application
> programming
> > > > >    interfaces and the human interfaces should be the same
> > > > to ensure that
> > > > >    data exchanged between these two interfaces is always
> > > consistent.
> > > > >    Mixing methods leads to inconsistency, so identifying
> > > consistent
> > > > >    methods of retrieving information is relevant.
> > > > >
> > > > > This is really sailing too close to the=20
> implementation. People=20
> > > > > must be free to construct sub-standard and unmarketable=20
> > > > > implementations. The IETF is not responsible for making all=20
> > > > > implementations successful. The job is to make it=20
> possible for=20
> > > > > all implementations to be successful given core
> > competences in the
> > > > > developers.
> > > > >
> > > > > I think the furthest a protocol spec RFC could go would
> > be to say
> > > > > what information must be available to an operator at a human=20
> > > > > interface for troubleshooting
> > > > >
> > > > > =3D=3D=3D
> > > > >
> > > > > 3.2.  Installation and Initial Setup
> > > > >
> > > > > In view of the reasons you give why defaults might=20
> become out-=20
> > > > > dated, you might point out that sometimes it is not advisable
> to
> > > > > have defaults. In these cases explicit configuration is
> > required.
> > > > >
> > > > > =3D=3D=3D
> > > > >
> > > > > 3.2.  Installation and Initial Setup
> > > > >
> > > > > Is the text at the top of page 8 supposed to be a bullet list?
> > > > >
> > > > > =3D=3D=3D
> > > > >
> > > > > 3.4.  Requirements on Other Protocols and Functional
> Components
> > > > >
> > > > >    These considerations should generally remain
> > > > illustrative to avoid
> > > > >    creating restrictions or dependencies, or potentially
> > > > impacting the
> > > > >    behavior of existing protocols, or restricting the
> > > > extensibility of
> > > > >    other protocols, or assuming other protocols will not be
> > > > extended in
> > > > >    certain ways.
> > > > >
> > > > > Well, this is quite interesting.
> > > > >
> > > > > Suppose you decide to utilise a particular feature of a
> > transport
> > > > > protocol. You are creating a hard requirement that that
> > feature is
> > > > > implemented in all implementations of the set {your new
> > protocol,
> > > > > the transport protocol}. But more importantly, perhaps, you
> are
> > > > > requiring that new versions of the transport protocol do not=20
> > > > > deprecate the feature you require.
> > > > >
> > > > > In short, I don't think you should be too nervous about
> creating
> > > > > restrictions or dependencies. If they exist, they must
> > be stated.
> > > > >
> > > > > =3D=3D=3D
> > > > >
> > > > > 3.2.  Installation and Initial Setup
> > > > >
> > > > >    For example, the design of Resource ReSerVation
> > Protocol (RSVP)
> > > > >
> > > > > I think this example is not well expressed.
> > > > >
> > > > > The problem in RSVP was that the IP packet was addressed to
> the
> > > > > ultimate RSVP-capable destination, but the RSVP-capable
> routers
> > > > > along the path needed to intercept and process the Path
> message.
> > > > > This they could only do by "deep packet inspection" or by the=20
> > > > > router alert option.
> > > > >
> > > > > I wonder whether this example adds significantly to the I-D.
> > > > >
> > > > > =3D=3D=3D
> > > > >
> > > > > 4.  Management Considerations
> > > > >
> > > > >    NETCONF addresses this in a generic manner by
> > > > >
> > > > > Add citation.
> > > > >
> > > > > =3D=3D=3D
> > > > >
> > > > > 4.  Management Considerations
> > > > >
> > > > >    However, debugging on-the-wire interactions is a protocol
> > > > >    issue: it is enormously helpful if a protocol has
> > hooks to make
> > > > >    debugging of network interactions easy, and/or is
> > > > designed in such a
> > > > >    way that debugging protocol behaviors is easy.
> > > > Hand-waving this away
> > > > >    is not something that operators like ...
> > > > >
> > > > > I think you are including this by hand-waving!
> > > > > What do you mean by "hooks"?
> > > > > Surely any protocol can be debugged simply by sniffing it.
> > > > > If you have specific hooks in mind you must set them out and
> not
> > > > > leave the reader guessing.
> > > > > But if you force the implementation I shall be peeved!
> > > > > You might, for example, say that there should be alerts issued
> > > when
> > > > > messages are received, or when there are state
> > transitions in the
> > > > > protocol state machine, but you must recall that:
> > > > > - the messages can be seen by sniffing
> > > > > - the state machine is not part of the protocol specification.
> > > > > This latter point is key. The state machine explains how the=20
> > > > > protocol works in order that an implementer can decide how to=20
> > > > > react to a received event, but it does not require that the=20
> > > > > machine is implemented.
> > > > >
> > > > > =3D=3D=3D
> > > > >
> > > > > 4.1.  Interoperability
> > > > >
> > > > >    Interoperability needs to be considered on the syntactic
> > > > level and
> > > > >    the semantic level.  While it can be irritating and
> > > > time-consuming,
> > > > >    application designers including operators who write
> > > > their own scripts
> > > > >    can make their processing conditional to accommodate
> > > differences
> > > > >
> > > > > s/differences/syntactic differences/ ?
> > > > >
> > > > >    Then, whether the counter is gathered via SNMP or a CLI
> > > > >    command or a SYSLOG message, the counter will have
> > > > similar meaning.
> > > > >
> > > > > "similar"? I think that might not be good enough. Don't you
> need
> > > > > "the same"?
> > > > >
> > > > >    o  [RFC3805] - Printer MIB v2 (contains both an IM and a DM
> > > > >
> > > > > Missing ")"
> > > > >
> > > > > =3D=3D=3D
> > > > >
> > > > > 4.2.  Management Information
> > > > >
> > > > > I would find it really helpful if you were able to=20
> recommend a=20
> > > > > language in which to write the information model.=20
> Ideally, all=20
> > > > > IETF IMs would be in the same language.
> > > > >
> > > > >    It is important to be able to separately fetch
> > > > configuration data,
> > > > >    operational state data, and statistics from devices, and
> > > > to be able
> > > > >    to compare current state to initial state, and to
> > compare data
> > > > >    between devices.
> > > > >
> > > > > You seem to have drifted into DMs here. You cannot
> > fetch data from
> > > > > an IM. It simply explains what data elements exist. In
> > fact, an IM
> > > > > states all of the data that exists and so there is no
> confusion.
> > > > > Confusion can only arise as the DM is constructed and
> > multiple IM
> > > > > data elements are conflated into single DM objects.
> > > > >
> > > > > =3D=3D=3D
> > > > >
> > > > > 4.3.  Fault Management
> > > > >
> > > > >    The protocol designer should document the basic faults and
> > > health
> > > > >    indicators that need to be instrumented for the new
> > > > protocol, and the
> > > > >    alarms and events that must be propagated to management
> > > > applications
> > > > >    or exposed through a data model.
> > > > >
> > > > > Isn't "propagated to management applications" a subset
> > of "exposed
> > > > > through a data model"?
> > > > >
> > > > >    The protocol designer should consider how faults
> > > > information will be
> > > > >
> > > > > s/faults/fault/
> > > > >
> > > > >    Should the event reporting provide gyaranteed accurate
> > > > delivery of
> > > > > s/gyaranteed/guaranteed/
> > > > >
> > > > > =3D=3D=3D
> > > > >
> > > > > 4.3.3.  Fault Isolation
> > > > >
> > > > >    It might be useful to isolate faults, such as a system that
> > > emits
> > > > >    malformed messages necessary to coordinate connections
> > > properly.
> > > > >    Spanning tree comes to mind.  This might be able to
> > be done by
> > > > >    configuring next-hop devices to drop the faulty messages
> > > > to prevent
> > > > >    them from entering the rest of the network.
> > > > >
> > > > > This is not what *I* mean by fault isolation!
> > > > > Fault isolation is about working out where in the network the
> > > fault
> > > > > is. For example, if end-to-end data delivery is failing
> > (reported
> > > by
> > > > > a notification), fault isolation will find the failed
> > link or node
> > > > > in the end-to-end path.
> > > > >
> > > > > You seem to be describing the process of quarantining faulty=20
> > > > > devices. This may also be valuable.
> > > > >
> > > > > "Spanning tree comes to mind" is a rather strange
> > sentence without
> > > > > much context.
> > > > >
> > > > > =3D=3D=3D
> > > > >
> > > > > 4.4.  Configuration Management
> > > > >
> > > > >    A protocol desoigners should document what the basic
> > > > configuration
> > > > >
> > > > > s/desoigners/designers/
> > > > >
> > > > >    "Requirements for Configuration Management of IP-based
> > > Networks"
> > > > >    [RFC3139] discusses requirements for configuration
> > management.
> > > > > More precisely,
> > > > >    "Requirements for Configuration Management of IP-based
> > > Networks"
> > > > >    [RFC3139] discusses requirements for configuration
> management
> > > of
> > > > >    IP-based networks.
> > > > > Which makes me wonder about the purpose of the sentence :-)
> > > > >
> > > > >    This document includes...
> > > > > This document or that document?
> > > > >
> > > > >    A number of efforts have existed in the IETF to develop
> > > > policy-based
> > > > >    management.  "Terminology for Policy-Based Management"
> > > > [RFC3198] was
> > > > >    written to standardize the terminology across these
> > > > efforts.  Some of
> > > > >    the efforts resulted in proposals that are NOT
> > RECOMMENDED, so
> > > a
> > > > >    protocol designer should check the current recommendation
> > > status
> > > > >    before depending on a specific protocol suggestion.
> > > > >
> > > > > You have used RFC2119 language, but in section 1.1 you said
> > > > >    This document deliberately does not use the
> > > > (capitalized) keywords
> > > > >    described in RFC 2119 [RFC2119].
> > > > > Furthermore, it is not clear to me whether this I-D is doing
> the
> > > > > NOT RECOMMENDing or whether some other RFC has done it. If it
> is
> > > > > this I-D, you will need to give reasons. If is some
> > other RFC, you
> > > > > will need to give references.
> > > > >
> > > > >    It is highly desirable that text processing tools such
> > > > as diff, and
> > > > >    version management tools such as RCS or CVS or SVN, can
> > > > be used to
> > > > >    process configurations.  This approach simplifies
> > comparing the
> > > > >    current operational state to the initial
> > configuration.  It is
> > > > >    commonplace to compare configuration changes to e.g.,
> > > > last day, last
> > > > >    week, last month, etc. -- having configuration in a
> > > > text, and human-
> > > > >    understandable format is very valuable for various
> > > > reasons such as
> > > > >    change control (or verification), configuration
> > > > consistency checks,
> > > > >    etc.
> > > > >
> > > > > Yes, but what has this to do with the protocol design?=20
> > It might be
> > > > > related to device implementation. Or it might be relevant to=20
> > > > > EMS/NMS implementation.
> > > > >
> > > > > As you note in the subsequent paragraph, this may be
> impossible
> > > > > even in some text-based DMs. It would certainly be impossible
> in
> > > > > an SNMP MIB module.
> > > > >
> > > > >    To simplify such configuration comparisons, devices
> > should not
> > > > >    arbitrarily reorder data such as access control lists.
> > > > If a protocol
> > > > >    designer defines mechanisms for configuration, it would
> > > > be desirable
> > > > >    to standardize the order of elements for consistency of
> > > > configuration
> > > > >    and of reporting across vendors, and across releases
> > > > from vendors.
> > > > >
> > > > > This example seems a bit specific. And in any case, it is
> > > perfectly
> > > > > possible to sort a list before comparing.
> > > > >
> > > > >    There are two parts to this: 1.  An NMS system could
> > > > optimize ACLs
> > > > >    for performance reasons 2.  Unless the device/NMS
> > > > systems has correct
> > > > >    rules/a lot of experience, reordering ACLs can lead to a
> huge
> > > > >    security issue.
> > > > >
> > > > > Maybe what you are saying is:
> > > > >    Implementations should not arbitrarily modify configuration
> > > data.
> > > > >    In some cases (such as Access Control Lists) the
> > order of data
> > > > >    items is significant and comprises part of the
> > configured data.
> > > > >
> > > > >    Network wide configurations are ideally stored in central
> > > master
> > > > >    databases
> > > > >
> > > > > This looks like an unsubstantiated assertion. You might get
> away
> > > > > with "Many operators prefer that..."
> > > > >
> > > > >    It is important to distinguish between the distribution of
> > > > >    configurations and the activation of a certain
> configuration.
> > > > >    Devices should be able to hold multiple configurations.
> > > > >
> > > > > This is really an implementation issue and nothing to
> > do with the
> > > > > protocol under design.
> > > > >
> > > > >    Consensus of the 2002 IAB Workshop was that textual
> > > configuration
> > > > >    files should be able to contain international characters.
> > > > >
> > > > > Do you have a citation?
> > > > >
> > > > >    These timers may need default values
> > > > >    suggested in the protocol specification and do not need to
> be
> > > > >    otherwise configurable.
> > > > >
> > > > > I had formed the opinion that timers must be given
> > default values
> > > > > in IETF protocol specifications, but I can't lay my=20
> hands on a=20
> > > > > reference.
> > > > >
> > > > > =3D=3D=3D
> > > > >
> > > > > 4.5.  Accounting Management
> > > > >
> > > > >    A protocol designer should consider whether it would be
> > > > appropriate
> > > > >    to collect usage information related to this protocol, and
> if
> > > so,
> > > > >    what usage information would be appropriate to collect?
> > > > >
> > > > > s/collect?/collect./
> > > > >
> > > > >    "Introduction to Accounting Management" [RFC2975]
> > > > discusses a number
> > > > >    of factors relevant to monitoring usage of protocols for
> > > > purposes of
> > > > >    capacity and trend analysis, cost allocation, auditing,
> > > > and billing.
> > > > >    This document also discusses how Remote Authentication
> > > > Dial In User
> > > > > This or that?
> > > > >
> > > > >    Service (RADIUS) [RFC2865], Terminal Access Controller
> > > > Access Control
> > > > >    System (TACACS) [RFC1492], SNMP, IPFIX, and Packet
> > > > Sampling (PSAMP)
> > > > >    Protocol [I-D.ietf-psamp-protocol] protocols can be used
> > > > for these
> > > > >    purposes.
> > > > >
> > > > > Surely RFC 2975 does not mention PSAMP? Which makes me
> > wonder what
> > > > > you are trying to achieve with a list of example protocols.
> Are
> > > > > they intended as recommendations (in which case say so and
> why),
> > > > > or as a non-exclusive list (in which case a "such as"=20
> would be=20
> > > > > useful). At the moment it reads like these are your
> > favorites and
> > > > > you would be upset if someone used a different protocol!
> > > > >
> > > > > =3D=3D=3D
> > > > >
> > > > > 4.6.  Performance Management
> > > > >
> > > > >    There are several parts to performance management to be
> > > > considered:
> > > > >    protocol monitoring, services monitoring, and device
> > > > monitoring (the
> > > > >    impact of the new protocol/service activation on the
> device).
> > > > >
> > > > > s/services/service/
> > > > >
> > > > >    Consider scalability, such as whether performance will
> > > > be affected by
> > > > >    the number of protocol connections.
> > > > >
> > > > > Maybe say "protocol entities" rather than connections?
> > > > >
> > > > >
> > > > > This section seems to flit between the performance of
> > the protocol
> > > > > under design and the network running the protocol under
> design,
> > > and
> > > > > the performance of the management of the protocol. Each is=20
> > > > > important, but it may be constructive to split them out into=20
> > > > > separate sections. The latter will also include a
> > consideration of
> > > > > how the act of monitoring impacts on network performance.
> > > > >
> > > > >
> > > > >    The Benchmarking Methodology WG (bmwg) has defined
> > > > recommendations
> > > > > Later you have BMWG.
> > > > >
> > > > > =3D=3D=3D
> > > > >
> > > > > 4.7.  Security Management
> > > > >
> > > > >    It must be possible to do consistency checks of access
> > > > control lists
> > > > >    across devices.  Protocol designers should consider
> > information
> > > > >    models to promote comparisons across devices and across
> > > > vendors to
> > > > >    permit checking the consistency of security configurations.
> > > > >
> > > > > I think this "must" is massively excessive!
> > > > > I would expect each router to have a different access
> > list in the
> > > > > control plane (a list of its neighbors). Such a mechanism
> would
> > > > > actually open up a security vulnerability that has to be
> > > protected.
> > > > > Perhaps you are talking about management plane access
> > lists. This
> > > > > takes us into the area of securing management activity - see
> my
> > > > > comments on Section 7.
> > > > >
> > > > >    RADIUS and DIAMETER can provide authentication and
> > > > authorization.  A
> > > > >    protocol designer should consider which attributes would be
> > > > >    appropriate for their protocol.
> > > > >
> > > > > This paragraph is apropos of what? What are you trying
> > to tell me?
> > > > > Should I run my management using Radius? Should I try=20
> to build=20
> > > > > Diameter into my new protocol?
> > > > >
> > > > >    Different protocols use different assumptions about
> > > > message security
> > > > > s/protocols/management protocols/
> > > > >
> > > > >    and data access controls.  A protocol designer that
> > > > recommends using
> > > > >    different protocols should consider how security will be
> > > > applied in a
> > > > > s/protocols/management protocols/
> > > > >
> > > > >
> > > > > Although you talk about (presumably management) access
> > > > lists, I think
> > > > > I would have expected a discussion of authority levels
> > and policy
> > > > > with regard to management tasks.
> > > > >
> > > > > =3D=3D=3D
> > > > >
> > > > > 7.  Security Considerations
> > > > >
> > > > >    This document is informational and provides guidelines for
> > > > >    considering manageability and operations.  It
> > introduces no new
> > > > >    security concerns.
> > > > >
> > > > > I think that, although you introduce no new security concerns=20
> > > > > directly, you have some things to talk about.
> > > > >
> > > > > Firstly, the provision of a management portal to a
> > network device
> > > > > provides a doorway through which an attack on the device may
> be
> > > > > launched. Since you are recommending that the protocol under=20
> > > > > development be manageable through the management
> > protocol, you are
> > > > > requiring that the protocol be vulnerable to a new source of=20
> > > > > attacks. Therefore, you must talk about securing the protocol=20
> > > > > against these attacks. This might be as simple as
> > saying that only
> > > > > management protocols with adequate (for some definition of
> > > > > adequate) security apparatus be used.
> > > > >
> > > > > I think it is also of note that a standard description of the=20
> > > > > manageable knobs and whistles on a protocol makes it
> > easier for an
> > > > > attacker to understand what they may try to control=20
> and how to=20
> > > > > tweak it.
> > > > >
> > > > > On the other hand, it would be well worth pointing out that a=20
> > > > > well-designed protocol is usually more stable and
> > secure. And that
> > > > > a protocol that can be managed and inspected offers the
> operator
> > > > > a better chance of spotting and quarantining any attacks.
> > > > > Conversely making a protocol inspectable, is a risk if the
> wrong
> > > > > person inspects it!
> > > > >
> > > > > If security events cause logs and or=20
> notifications/alerts, can a=20
> > > > > concerted attack be mounted by causing an excess of these=20
> > > > > events? In other words, to the security management mechanisms=20
> > > > > constitute the security vulnerability?
> > > > >
> > > > > Lastly, the management of security aspects is important, and
> you
> > > > > can just reference back to section 4.7.
> > > > >
> > > > > =3D=3D=3D
> > > > >
> > > > > 9.  Informative References
> > > > >
> > > > > I (of course) would favor an informational reference to
> > > > draft-ietf-pce-
> > > > > manageability-requirements-06.txt
> > > > >
> > > > > =3D=3D=3D
> > > > >
> > > > >    [RFC2821]                       Klensin, J., "Simple
> > > > Mail Transfer
> > > > >                                    Protocol", RFC 2821, April
> > > 2001.
> > > > >
> > > > > I think this has been obsoleted.
> > > > >
> > > > > =3D=3D=3D
> > > > >
> > > > > Appendix A.  Operations and Management Review Checklist
> > > > >
> > > > > Maybe a forward reference to this appendix from
> > sections 1 and 5?
> > > > >
> > > > > =3D=3D=3D
> > > > >
> > > > > A.3.  Documentation
> > > > >
> > > > >    Does the proposed protocol have a significant
> > > > operational impact on
> > > > >    the Internet.  If it does, and the document under review
> > > targets
> > > > >    standards track, is their enough proof of
> > implementation and/or
> > > > >    operational experience to grant Proposed Standard status?
> > > > >
> > > > > Whoah!
> > > > >
> > > > > You are going to use this I-D to try to block standards
> > track I-Ds
> > > > > from becoming RFCs? You are going to get into such a fight!!!
> > > > >
> > > > > IMHO this sentence is a complete show-stopper in your I-D.
> > > > >
> > > > > (Oh, and s/their/there/)
> > > > >
> > > > > =3D=3D=3D
> > > > >
> > > > > Appendix B.  Change Log
> > > > >
> > > > > Suggest you flag this for removal upon publication as an RFC.
> > > > >
> > > > > =3D=3D=3D
> > > > >
> > > > > > Sent: Sunday, January 25, 2009 6:40 PM
> > > > > > To: opsawg@ietf.org
> > > > > > Subject: [OPSAWG] (final) WGLC on=20
> > > > > > draft-ietf-opsawg-operations-and-management
> > > > > >
> > > > > > This is a (hopefully final) WGLC for=20
> > > > > > draft-ietf-opsawg-operations-and-management
> > > > > > there was not enough respose to the last one back=20
> in October=20
> > > > > > please let the list know what you think of the draft
> > > > >
> > > > > _______________________________________________
> > > > > OPSAWG mailing list
> > > > > OPSAWG@ietf.org
> > > > > https://www.ietf.org/mailman/listinfo/opsawg
> > > >
> > > > _______________________________________________
> > > > OPSAWG mailing list
> > > > OPSAWG@ietf.org
> > > > https://www.ietf.org/mailman/listinfo/opsawg
> > > >
> > >
> >=20
> >=20
>=20
> _______________________________________________
> OPSAWG mailing list
> OPSAWG@ietf.org
> https://www.ietf.org/mailman/listinfo/opsawg
>=20

From ietfdbh@comcast.net  Fri Mar  6 13:33:46 2009
Return-Path: <ietfdbh@comcast.net>
X-Original-To: opsawg@core3.amsl.com
Delivered-To: opsawg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D13163A6907 for <opsawg@core3.amsl.com>; Fri,  6 Mar 2009 13:33:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.198
X-Spam-Level: 
X-Spam-Status: No, score=-2.198 tagged_above=-999 required=5 tests=[AWL=-0.199, BAYES_00=-2.599, J_CHICKENPOX_34=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ryzqK+6ZKKDm for <opsawg@core3.amsl.com>; Fri,  6 Mar 2009 13:33:45 -0800 (PST)
Received: from QMTA07.westchester.pa.mail.comcast.net (qmta07.westchester.pa.mail.comcast.net [76.96.62.64]) by core3.amsl.com (Postfix) with ESMTP id 81D053A6869 for <opsawg@ietf.org>; Fri,  6 Mar 2009 13:32:54 -0800 (PST)
Received: from OMTA02.westchester.pa.mail.comcast.net ([76.96.62.19]) by QMTA07.westchester.pa.mail.comcast.net with comcast id Ppzj1b0560QuhwU57xZSsj; Fri, 06 Mar 2009 21:33:26 +0000
Received: from Harrington73653 ([24.147.240.21]) by OMTA02.westchester.pa.mail.comcast.net with comcast id PxZR1b00W0UQ6dC3NxZRYF; Fri, 06 Mar 2009 21:33:26 +0000
From: "David Harrington" <ietfdbh@comcast.net>
To: <j.schoenwaelder@jacobs-university.de>, "'Scott O. Bradner'" <sob@harvard.edu>
References: <20090125164013.802B5129CDC6@newdev.eecs.harvard.edu> <20090127083743.GB12355@elstar.local>
Date: Fri, 6 Mar 2009 16:33:24 -0500
Message-ID: <1b2701c99ea3$2e4dd380$0600a8c0@china.huawei.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
In-reply-to: <20090127083743.GB12355@elstar.local>
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
Thread-index: AcmAWo+ESxmBZwnbQl6+/MpVvh9zNAeQlmBQ
Cc: opsawg@ietf.org
Subject: Re: [OPSAWG] (final) WGLCon	draft-ietf-opsawg-operations-and-management
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Mar 2009 21:33:46 -0000

Hi,

I have recieved quite a few responses to this round of the WGLC (thank
you to those who responded).

I think we need a consensus call on two main questions:
1) should we publish pre-re-organization and then do a bis, and
2) how should the document be (re-)organized?

The first question:
I was asked to author this document to provide guidelines as the IETF
moves away from the "write a MIB" approach to the "consider mgmt
needs, and then select or develop a new mgmt protocol and associated
data models." We are already long past the "write a MIB" stage, and we
have WGs in multiple IETF areas developing new mgmt protocols and new
non-MIB data models, and they are doing so with no guidance from the
OPS+MGMT area because this document is taking so long to get done.
Should we publish this with some of the updates and then immediately
start a bis that reorganizes the document?

The second question:

I have two MAJOR editorial changes requested.
1) "I can't tell the difference between operations and management
considerations; let's just combine them into one section", and
2) "the section on management is ambiguous. Sections like performance
management mix the management of the performance of the targeted
protocol with performance of the protocol doing the management. Can we
better separate these?"

The text in this document frequently mixes discussion of management
protocol issues with the management of protocol issues. 

Is "what should the data model contain?" really an operations
question, or is it a management question? 
Is section 3.3's bullet list of things to look for in a management
protocol really an operations considerastion, or is it a management
consideration?
Is "Interoperability needs to be considered on the syntactic level and
the semantic level." really an operational consideration? or is it a
management consdieration?
Is "The protocol designer should consider the impact on infrastructure
applications like DNS" really a management consideration? or is this
really an operational consideration?

I re-published the "survey" document. This was removed from the
ops+mgmt document because it made the document too large. I wanted to
remind the WG that we are planning to publish both documents, so we
should not need a survey (or even a mini-survey) of available
management protocols in the ops+mgmt doc. I have added a paragraph
saying "go look in the other document for available mgmt
technologies."

I would like some comsensus from the WG about which way forward is
preferred for these two questions.

dbh
 

> -----Original Message-----
> From: opsawg-bounces@ietf.org 
> [mailto:opsawg-bounces@ietf.org] On Behalf Of Juergen Schoenwaelder
> Sent: Tuesday, January 27, 2009 3:38 AM
> To: Scott O. Bradner
> Cc: opsawg@ietf.org
> Subject: Re: [OPSAWG] (final) WGLCon 
> draft-ietf-opsawg-operations-and-management
> 
> On Sun, Jan 25, 2009 at 11:40:13AM -0500, Scott O. Bradner wrote:
>  
> > This is a (hopefully final) WGLC for
> > draft-ietf-opsawg-operations-and-management there was not enough
> > respose to the last one back in October
> 
> My review of draft-ietf-opsawg-operations-and-management-05.txt:
> 
> I find this a difficult document to review and I like to state
clearly
> upfront that I very much appreciate the efforts spend on putting
this
> document together. The reason for starting with this diclaimer is
that
> I find it difficult to provide constructive comments in the form of
> concrete suggestions for changes. While reading, I observed the
> following:
> 
> - The document makes a distinction between "Operational
>   Considerations" (section 3) and "Management Considerations"
(section
>   4) and I am not sure where the difference really is. I appears
that
>   section 4 is much more management technology oriented and
organized
>   following the FCAPS model but in general, I do not really see why
>   some issues are operational considerations and others management
>   considerations. Perhaps the document can be streamlined by merging
>   these two sections together. (For example, 3.6 and 4.3.1 do in my
>   view pretty much belong together.)
> 
> - At times, the document reads like a collection of text fragments
>   taken from other documents without a very clear story line. I
>   sometimes had the feeling that things were not developing in a
>   "natural way" (but it is difficult for me to say what such a
>   "natural way" would look like without going through the whole
>   exercise to dissect the document into its fragments and
reassembling
>   the puzzle again).
> 
> - I am not sure the discussion what the "IETF Management Framework"
>   means (historically and today) is that useful for designers of new
>   protocols and it might raise controversial discussions. Why not
>   replace this material with a section that provide a high-level
>   summary of the management technologies that can be considered by
>   protocol designers? In terms of structure, this could mean that
the
>   document should have this structure (in terms of top-level
>   sections):
> 
>   1. Introduction
>   2. Available Management Technologies
>      (briefly mention SNMP, SYSLOG, RADIUS/DIAMETER, NETCONF, IPFIX,
>      CLIs, GUIs, ...  and outline where they are particularly strong
>      and where not; this should be short and not a long elaboration)
>   3. Operational and Management Considerations
>   4. Documentation Guidelines
>   .. ...
> 
>   This would lift some of the text currently in section 4 into
section
>   2. I also killed the current section 2 since the core of this is
>   already discussed in the introduction. As an alterntative, one
could
>   keep a section "Design for Operations and Management" but then
some
>   of the discussion currently in the introduction should be moved.
> 
> - The "Terminology" section explains why RFC 2119 language is not
used
>   and then defines the terms "new protocol" and "protocol
designers".
>   The document later has quite some text related to terminology
(e.g.
>   the discussion of information model vs. data model). One option to
>   consider is to move all text discussing or clarifying terminology
>   into this "Terminology" section (including the text fragments
>   pointing to RFC 3198 and RFC 3444).
> 
> Some editorial nits:
> 
> - Define the acronym CLI the first time it is used.
> 
> - Is "later/never phase" a typo or there by intention?
> 
> - I am not sure this sentence is correct:
> 
>     This document sets forth a list of subjective guidelines 
> and a list
>     of objective criteria by which a protocol designer can evaluate
>     whether the protocol that he/she has developed addresses common
>      operations and management needs. 
> 
>   I am actually not sure whether the distinction between "subjective
>   guidelines" and "objective criteria" is worth to have. What I
>   believe is valuable is the checklist phrased as a collection of
>   questions to consider.
>   
> - The first paragraph in 2.1 should in my opinion cite RFC 3410. But
>   as mentioned above, I am not a big fan of this discussion at all.
> 
> - s/algoithms/algorithms
> 
> - Some text on top of page 8 that looks scratch pad text.
> 
> - s/should there be/Should there be
> 
> - s/gyaranteed/guaranteed
> 
> - garbaled sentence
> 
>      or can the right
>      counters that can be polled as needed?
> 
> - s/desoigners/designer
> 
> - s/For example, Sometimes/For example, sometimes
> 
> - s/should they stop counting/Should they stop counting
> 
> - A.1: Make it clear that scalability in terms of operations and
>   management is meant, not in terms of the primary protocol
functions.
> 
>   OLD
> 
>   Does the solution scale well?
> 
>   NEW
> 
>   Does the solution scale well from the operational and management
>   perspective?
> 
> - A.1: Capitalize the sentences with the questions consistently.
> 
> - A.1: Add the following:
> 
>     Are there any coexistance issues?
> 
> - A.1: Add some more detailed questions for the items refering to
3.5,
>        3.6 and 4.1.
> 
> - Appendix A tries to make a distinction between Operational
>   Considerations and Management Considerations and I am not sure
this
>   is a clear cut line. Earlier, the document talks about a single
>   "Manageability Considerations" section. See also my more general
>   comments above.
> 
> /js
> 
> -- 
> Juergen Schoenwaelder           Jacobs University Bremen gGmbH
> Phone: +49 421 200 3587         Campus Ring 1, 28759 Bremen, Germany
> Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>
> _______________________________________________
> OPSAWG mailing list
> OPSAWG@ietf.org
> https://www.ietf.org/mailman/listinfo/opsawg
> 


From dromasca@avaya.com  Sun Mar  8 08:08:33 2009
Return-Path: <dromasca@avaya.com>
X-Original-To: opsawg@core3.amsl.com
Delivered-To: opsawg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 964EE3A67FB for <opsawg@core3.amsl.com>; Sun,  8 Mar 2009 08:08:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.225
X-Spam-Level: 
X-Spam-Status: No, score=-2.225 tagged_above=-999 required=5 tests=[AWL=-0.226, BAYES_00=-2.599, J_CHICKENPOX_34=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ib86fplbZH6Y for <opsawg@core3.amsl.com>; Sun,  8 Mar 2009 08:08:31 -0700 (PDT)
Received: from nj300815-nj-outbound.net.avaya.com (nj300815-nj-outbound.net.avaya.com [198.152.12.100]) by core3.amsl.com (Postfix) with ESMTP id 397EF3A68DD for <opsawg@ietf.org>; Sun,  8 Mar 2009 08:08:31 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.38,325,1233550800"; d="scan'208";a="154594731"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by nj300815-nj-outbound.net.avaya.com with ESMTP; 08 Mar 2009 11:09:03 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.13]) by co300216-co-erhwest-out.avaya.com with ESMTP; 08 Mar 2009 11:09:02 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Sun, 8 Mar 2009 16:08:56 +0100
Message-ID: <EDC652A26FB23C4EB6384A4584434A040149467C@307622ANEX5.global.avaya.com>
In-Reply-To: <1b2701c99ea3$2e4dd380$0600a8c0@china.huawei.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [OPSAWG] (final)WGLCon	draft-ietf-opsawg-operations-and-management
Thread-Index: AcmAWo+ESxmBZwnbQl6+/MpVvh9zNAeQlmBQAFha9fA=
References: <20090125164013.802B5129CDC6@newdev.eecs.harvard.edu><20090127083743.GB12355@elstar.local> <1b2701c99ea3$2e4dd380$0600a8c0@china.huawei.com>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "David Harrington" <ietfdbh@comcast.net>, <j.schoenwaelder@jacobs-university.de>, "Scott O. Bradner" <sob@harvard.edu>
Cc: opsawg@ietf.org
Subject: Re: [OPSAWG] (final)WGLCon	draft-ietf-opsawg-operations-and-management
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 08 Mar 2009 15:08:33 -0000

Speaking as a contributor:=20

1) Please ship ASAP for the reasons that you have described.=20

2.1) I believe that the difference between operational impact and
manageability considerations is clearly stated in the document and that
the level of superposition between the two does not justify a
reorganization of the document and the related delays at this point in
time.=20

2.2) I actually believe that section 4.6 makes quite clear that the
focus is on the management of the performance of the managed protocol.
The protocol that performs management is mentioned only in the context
of the data modeling limitations. If judged necessary one more phrase in
the first paragraph of 4.6 could clarify these.=20

The rest of the comments seem to me valuable, but detail level, and none
of them a show stopper.=20

See again 1).=20

Regards,

Dan


> -----Original Message-----
> From: opsawg-bounces@ietf.org=20
> [mailto:opsawg-bounces@ietf.org] On Behalf Of David Harrington
> Sent: Friday, March 06, 2009 11:33 PM
> To: j.schoenwaelder@jacobs-university.de; 'Scott O. Bradner'
> Cc: opsawg@ietf.org
> Subject: Re: [OPSAWG] (final)WGLCon=20
> draft-ietf-opsawg-operations-and-management
>=20
> Hi,
>=20
> I have recieved quite a few responses to this round of the=20
> WGLC (thank you to those who responded).
>=20
> I think we need a consensus call on two main questions:
> 1) should we publish pre-re-organization and then do a bis, and
> 2) how should the document be (re-)organized?
>=20
> The first question:
> I was asked to author this document to provide guidelines as=20
> the IETF moves away from the "write a MIB" approach to the=20
> "consider mgmt needs, and then select or develop a new mgmt=20
> protocol and associated data models." We are already long=20
> past the "write a MIB" stage, and we have WGs in multiple=20
> IETF areas developing new mgmt protocols and new non-MIB data=20
> models, and they are doing so with no guidance from the
> OPS+MGMT area because this document is taking so long to get done.
> Should we publish this with some of the updates and then=20
> immediately start a bis that reorganizes the document?
>=20
> The second question:
>=20
> I have two MAJOR editorial changes requested.
> 1) "I can't tell the difference between operations and=20
> management considerations; let's just combine them into one=20
> section", and
> 2) "the section on management is ambiguous. Sections like=20
> performance management mix the management of the performance=20
> of the targeted protocol with performance of the protocol=20
> doing the management. Can we better separate these?"
>=20
> The text in this document frequently mixes discussion of=20
> management protocol issues with the management of protocol issues.=20
>=20
> Is "what should the data model contain?" really an operations=20
> question, or is it a management question?=20
> Is section 3.3's bullet list of things to look for in a=20
> management protocol really an operations considerastion, or=20
> is it a management consideration?
> Is "Interoperability needs to be considered on the syntactic=20
> level and the semantic level." really an operational=20
> consideration? or is it a management consdieration?
> Is "The protocol designer should consider the impact on=20
> infrastructure applications like DNS" really a management=20
> consideration? or is this really an operational consideration?
>=20
> I re-published the "survey" document. This was removed from the
> ops+mgmt document because it made the document too large. I wanted to
> remind the WG that we are planning to publish both documents,=20
> so we should not need a survey (or even a mini-survey) of=20
> available management protocols in the ops+mgmt doc. I have=20
> added a paragraph saying "go look in the other document for=20
> available mgmt technologies."
>=20
> I would like some comsensus from the WG about which way=20
> forward is preferred for these two questions.
>=20
> dbh
> =20
>=20
> > -----Original Message-----
> > From: opsawg-bounces@ietf.org
> > [mailto:opsawg-bounces@ietf.org] On Behalf Of Juergen Schoenwaelder
> > Sent: Tuesday, January 27, 2009 3:38 AM
> > To: Scott O. Bradner
> > Cc: opsawg@ietf.org
> > Subject: Re: [OPSAWG] (final) WGLCon
> > draft-ietf-opsawg-operations-and-management
> >=20
> > On Sun, Jan 25, 2009 at 11:40:13AM -0500, Scott O. Bradner wrote:
> > =20
> > > This is a (hopefully final) WGLC for=20
> > > draft-ietf-opsawg-operations-and-management there was not enough=20
> > > respose to the last one back in October
> >=20
> > My review of draft-ietf-opsawg-operations-and-management-05.txt:
> >=20
> > I find this a difficult document to review and I like to state
> clearly
> > upfront that I very much appreciate the efforts spend on putting
> this
> > document together. The reason for starting with this diclaimer is
> that
> > I find it difficult to provide constructive comments in the form of=20
> > concrete suggestions for changes. While reading, I observed the
> > following:
> >=20
> > - The document makes a distinction between "Operational
> >   Considerations" (section 3) and "Management Considerations"
> (section
> >   4) and I am not sure where the difference really is. I appears
> that
> >   section 4 is much more management technology oriented and
> organized
> >   following the FCAPS model but in general, I do not really see why
> >   some issues are operational considerations and others management
> >   considerations. Perhaps the document can be streamlined by merging
> >   these two sections together. (For example, 3.6 and 4.3.1 do in my
> >   view pretty much belong together.)
> >=20
> > - At times, the document reads like a collection of text fragments
> >   taken from other documents without a very clear story line. I
> >   sometimes had the feeling that things were not developing in a
> >   "natural way" (but it is difficult for me to say what such a
> >   "natural way" would look like without going through the whole
> >   exercise to dissect the document into its fragments and
> reassembling
> >   the puzzle again).
> >=20
> > - I am not sure the discussion what the "IETF Management Framework"
> >   means (historically and today) is that useful for designers of new
> >   protocols and it might raise controversial discussions. Why not
> >   replace this material with a section that provide a high-level
> >   summary of the management technologies that can be considered by
> >   protocol designers? In terms of structure, this could mean that
> the
> >   document should have this structure (in terms of top-level
> >   sections):
> >=20
> >   1. Introduction
> >   2. Available Management Technologies
> >      (briefly mention SNMP, SYSLOG, RADIUS/DIAMETER, NETCONF, IPFIX,
> >      CLIs, GUIs, ...  and outline where they are particularly strong
> >      and where not; this should be short and not a long elaboration)
> >   3. Operational and Management Considerations
> >   4. Documentation Guidelines
> >   .. ...
> >=20
> >   This would lift some of the text currently in section 4 into
> section
> >   2. I also killed the current section 2 since the core of this is
> >   already discussed in the introduction. As an alterntative, one
> could
> >   keep a section "Design for Operations and Management" but then
> some
> >   of the discussion currently in the introduction should be moved.
> >=20
> > - The "Terminology" section explains why RFC 2119 language is not
> used
> >   and then defines the terms "new protocol" and "protocol
> designers".
> >   The document later has quite some text related to terminology
> (e.g.
> >   the discussion of information model vs. data model). One option to
> >   consider is to move all text discussing or clarifying terminology
> >   into this "Terminology" section (including the text fragments
> >   pointing to RFC 3198 and RFC 3444).
> >=20
> > Some editorial nits:
> >=20
> > - Define the acronym CLI the first time it is used.
> >=20
> > - Is "later/never phase" a typo or there by intention?
> >=20
> > - I am not sure this sentence is correct:
> >=20
> >     This document sets forth a list of subjective guidelines and a=20
> > list
> >     of objective criteria by which a protocol designer can evaluate
> >     whether the protocol that he/she has developed addresses common
> >      operations and management needs.=20
> >=20
> >   I am actually not sure whether the distinction between "subjective
> >   guidelines" and "objective criteria" is worth to have. What I
> >   believe is valuable is the checklist phrased as a collection of
> >   questions to consider.
> >  =20
> > - The first paragraph in 2.1 should in my opinion cite RFC 3410. But
> >   as mentioned above, I am not a big fan of this discussion at all.
> >=20
> > - s/algoithms/algorithms
> >=20
> > - Some text on top of page 8 that looks scratch pad text.
> >=20
> > - s/should there be/Should there be
> >=20
> > - s/gyaranteed/guaranteed
> >=20
> > - garbaled sentence
> >=20
> >      or can the right
> >      counters that can be polled as needed?
> >=20
> > - s/desoigners/designer
> >=20
> > - s/For example, Sometimes/For example, sometimes
> >=20
> > - s/should they stop counting/Should they stop counting
> >=20
> > - A.1: Make it clear that scalability in terms of operations and
> >   management is meant, not in terms of the primary protocol
> functions.
> >=20
> >   OLD
> >=20
> >   Does the solution scale well?
> >=20
> >   NEW
> >=20
> >   Does the solution scale well from the operational and management
> >   perspective?
> >=20
> > - A.1: Capitalize the sentences with the questions consistently.
> >=20
> > - A.1: Add the following:
> >=20
> >     Are there any coexistance issues?
> >=20
> > - A.1: Add some more detailed questions for the items refering to
> 3.5,
> >        3.6 and 4.1.
> >=20
> > - Appendix A tries to make a distinction between Operational
> >   Considerations and Management Considerations and I am not sure
> this
> >   is a clear cut line. Earlier, the document talks about a single
> >   "Manageability Considerations" section. See also my more general
> >   comments above.
> >=20
> > /js
> >=20
> > --=20
> > Juergen Schoenwaelder           Jacobs University Bremen gGmbH
> > Phone: +49 421 200 3587         Campus Ring 1, 28759 Bremen, Germany
> > Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>
> > _______________________________________________
> > OPSAWG mailing list
> > OPSAWG@ietf.org
> > https://www.ietf.org/mailman/listinfo/opsawg
> >=20
>=20
> _______________________________________________
> OPSAWG mailing list
> OPSAWG@ietf.org
> https://www.ietf.org/mailman/listinfo/opsawg
>=20

From j.schoenwaelder@jacobs-university.de  Mon Mar  9 01:27:02 2009
Return-Path: <j.schoenwaelder@jacobs-university.de>
X-Original-To: opsawg@core3.amsl.com
Delivered-To: opsawg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4A9613A69DD for <opsawg@core3.amsl.com>; Mon,  9 Mar 2009 01:27:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.9
X-Spam-Level: 
X-Spam-Status: No, score=-0.9 tagged_above=-999 required=5 tests=[AWL=-1.065,  BAYES_40=-0.185, HELO_EQ_DE=0.35]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6ZmYJGC-ytGq for <opsawg@core3.amsl.com>; Mon,  9 Mar 2009 01:27:01 -0700 (PDT)
Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) by core3.amsl.com (Postfix) with ESMTP id 735603A6A04 for <opsawg@ietf.org>; Mon,  9 Mar 2009 01:27:01 -0700 (PDT)
Received: from localhost (demetrius3.jacobs-university.de [212.201.44.48]) by hermes.jacobs-university.de (Postfix) with ESMTP id D8DC6C0008; Mon,  9 Mar 2009 09:27:34 +0100 (CET)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius3.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id CVpHL0-FdgO1; Mon,  9 Mar 2009 09:27:34 +0100 (CET)
Received: from elstar.local (elstar.iuhb02.iu-bremen.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id D9F54C0003; Mon,  9 Mar 2009 09:27:33 +0100 (CET)
Received: by elstar.local (Postfix, from userid 501) id 68C199F2511; Mon,  9 Mar 2009 09:27:31 +0100 (CET)
Date: Mon, 9 Mar 2009 09:27:31 +0100
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
Message-ID: <20090309082731.GB5676@elstar.local>
Mail-Followup-To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>, David Harrington <ietfdbh@comcast.net>, "Scott O. Bradner" <sob@harvard.edu>, "opsawg@ietf.org" <opsawg@ietf.org>
References: <20090125164013.802B5129CDC6@newdev.eecs.harvard.edu> <20090127083743.GB12355@elstar.local> <1b2701c99ea3$2e4dd380$0600a8c0@china.huawei.com> <EDC652A26FB23C4EB6384A4584434A040149467C@307622ANEX5.global.avaya.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <EDC652A26FB23C4EB6384A4584434A040149467C@307622ANEX5.global.avaya.com>
User-Agent: Mutt/1.5.19 (2009-01-05)
Cc: "opsawg@ietf.org" <opsawg@ietf.org>
Subject: Re: [OPSAWG] (final)WGLCon	draft-ietf-opsawg-operations-and-management
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: j.schoenwaelder@jacobs-university.de
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Mar 2009 08:27:02 -0000

On Sun, Mar 08, 2009 at 04:08:56PM +0100, Romascanu, Dan (Dan) wrote:
> Speaking as a contributor: 
> 
> 1) Please ship ASAP for the reasons that you have described. 

I like to understand (a) what really pressures us to push this out
quickly and (b) what it will take time wise to rework this document
into a better shape.

How is this document been used once it has been published as RFC? Why
can't this usage not be achieved now already with an ID in place?

/js

-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: +49 421 200 3587         Campus Ring 1, 28759 Bremen, Germany
Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>

From dromasca@avaya.com  Mon Mar  9 01:59:11 2009
Return-Path: <dromasca@avaya.com>
X-Original-To: opsawg@core3.amsl.com
Delivered-To: opsawg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1EE733A68F9 for <opsawg@core3.amsl.com>; Mon,  9 Mar 2009 01:59:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.522
X-Spam-Level: 
X-Spam-Status: No, score=-2.522 tagged_above=-999 required=5 tests=[AWL=0.077,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2lLgpOTqC1TX for <opsawg@core3.amsl.com>; Mon,  9 Mar 2009 01:59:10 -0700 (PDT)
Received: from nj300815-nj-outbound.net.avaya.com (nj300815-nj-outbound.net.avaya.com [198.152.12.100]) by core3.amsl.com (Postfix) with ESMTP id 0956C3A672F for <opsawg@ietf.org>; Mon,  9 Mar 2009 01:59:09 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.38,328,1233550800"; d="scan'208";a="154643811"
Received: from unknown (HELO nj300815-nj-erheast.avaya.com) ([198.152.6.5]) by nj300815-nj-outbound.net.avaya.com with ESMTP; 09 Mar 2009 04:59:42 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.13]) by nj300815-nj-erheast-out.avaya.com with ESMTP; 09 Mar 2009 04:59:42 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 9 Mar 2009 09:59:27 +0100
Message-ID: <EDC652A26FB23C4EB6384A4584434A0401494781@307622ANEX5.global.avaya.com>
In-Reply-To: <20090309082731.GB5676@elstar.local>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [OPSAWG] (final)WGLCondraft-ietf-opsawg-operations-and-management
Thread-Index: AcmgkOgnOzIexbtdRxqks5v/IgIeMgAA4ccg
References: <20090125164013.802B5129CDC6@newdev.eecs.harvard.edu> <20090127083743.GB12355@elstar.local> <1b2701c99ea3$2e4dd380$0600a8c0@china.huawei.com> <EDC652A26FB23C4EB6384A4584434A040149467C@307622ANEX5.global.avaya.com> <20090309082731.GB5676@elstar.local>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <j.schoenwaelder@jacobs-university.de>
Cc: opsawg@ietf.org
Subject: Re: [OPSAWG] (final)WGLCondraft-ietf-opsawg-operations-and-management
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Mar 2009 08:59:11 -0000

=20

> -----Original Message-----
> From: Juergen Schoenwaelder=20
> [mailto:j.schoenwaelder@jacobs-university.de]=20
> Sent: Monday, March 09, 2009 10:28 AM
> To: Romascanu, Dan (Dan)
> Cc: David Harrington; Scott O. Bradner; opsawg@ietf.org
> Subject: Re: [OPSAWG]=20
> (final)WGLCondraft-ietf-opsawg-operations-and-management
>=20
> On Sun, Mar 08, 2009 at 04:08:56PM +0100, Romascanu, Dan (Dan) wrote:
> > Speaking as a contributor:=20
> >=20
> > 1) Please ship ASAP for the reasons that you have described.=20
>=20
> I like to understand (a) what really pressures us to push=20
> this out quickly and (b) what it will take time wise to=20
> rework this document into a better shape.
>=20
> How is this document been used once it has been published as=20
> RFC? Why can't this usage not be achieved now already with an=20
> ID in place?
>=20
> /js
>=20
> --=20
> Juergen Schoenwaelder           Jacobs University Bremen gGmbH
> Phone: +49 421 200 3587         Campus Ring 1, 28759 Bremen, Germany
> Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>
>=20

Speaking as AD:=20

>From the Abstract:=20

>   The purpose of this document is to provide guidance to authors and
   reviewers of documents defining new protocols or protocol extensions,
   about covering aspects of operations and management that should be
   considered.

There is a difference between having a BCP as reference, and having an
I-D which is work-in-progress.=20

Sealing as a contributor:=20

I believe that that the document is in good enough shape to meet its
principal goals, and to be submitted by the WG to the IESG.=20

Speaking as both:=20

We already discussed this document in the WG for more than one year. I
hope that by sending it to the IESG and entering IETF Last Call we shall
generate a level of response from other areas in the IETF who are
'customers' and 'users' of this document.=20

Dan
=20

From Hannes.Tschofenig@gmx.net  Mon Mar  9 02:41:10 2009
Return-Path: <Hannes.Tschofenig@gmx.net>
X-Original-To: opsawg@core3.amsl.com
Delivered-To: opsawg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B61E73A6BC1 for <opsawg@core3.amsl.com>; Mon,  9 Mar 2009 02:41:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.478
X-Spam-Level: 
X-Spam-Status: No, score=-1.478 tagged_above=-999 required=5 tests=[AWL=-0.368, BAYES_05=-1.11]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kMMx2X+bo28G for <opsawg@core3.amsl.com>; Mon,  9 Mar 2009 02:41:09 -0700 (PDT)
Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by core3.amsl.com (Postfix) with SMTP id 58CBD3A69E5 for <opsawg@ietf.org>; Mon,  9 Mar 2009 02:41:08 -0700 (PDT)
Received: (qmail invoked by alias); 09 Mar 2009 09:35:01 -0000
Received: from unknown (EHLO 4FIL42860) [192.100.124.156] by mail.gmx.net (mp005) with SMTP; 09 Mar 2009 10:35:01 +0100
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX1+ihKgHKCmi1POk4SF2VU6Bh7faVRUZ1vHMpZeifm Fy/rYJ8LAKZJsk
From: "Hannes Tschofenig" <Hannes.Tschofenig@gmx.net>
To: <j.schoenwaelder@jacobs-university.de>, "'Romascanu, Dan \(Dan\)'" <dromasca@avaya.com>
References: <20090125164013.802B5129CDC6@newdev.eecs.harvard.edu><20090127083743.GB12355@elstar.local><1b2701c99ea3$2e4dd380$0600a8c0@china.huawei.com><EDC652A26FB23C4EB6384A4584434A040149467C@307622ANEX5.global.avaya.com> <20090309082731.GB5676@elstar.local>
Date: Mon, 9 Mar 2009 11:36:04 +0200
Message-ID: <058e01c9a09a$78b0cbf0$0201a8c0@nsnintra.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
Thread-Index: AcmgkOe2gvlWb+gBTO+RgpViexgM9QACM3wA
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
In-Reply-To: <20090309082731.GB5676@elstar.local>
X-Y-GMX-Trusted: 0
X-FuHaFi: 0.82
Cc: opsawg@ietf.org
Subject: Re: [OPSAWG] (final)WGLCon	draft-ietf-opsawg-operations-and-management
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Mar 2009 09:41:10 -0000

>How is this document been used once it has been published as 
>RFC?

That's a question I had as well.


From dromasca@avaya.com  Mon Mar  9 03:03:31 2009
Return-Path: <dromasca@avaya.com>
X-Original-To: opsawg@core3.amsl.com
Delivered-To: opsawg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1EE073A6B8F for <opsawg@core3.amsl.com>; Mon,  9 Mar 2009 03:03:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.523
X-Spam-Level: 
X-Spam-Status: No, score=-2.523 tagged_above=-999 required=5 tests=[AWL=0.076,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8d+Fmq-IGiRb for <opsawg@core3.amsl.com>; Mon,  9 Mar 2009 03:03:30 -0700 (PDT)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by core3.amsl.com (Postfix) with ESMTP id 01E2E3A6811 for <opsawg@ietf.org>; Mon,  9 Mar 2009 03:03:29 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.38,328,1233550800"; d="scan'208";a="139634001"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 09 Mar 2009 06:04:01 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.13]) by co300216-co-erhwest-out.avaya.com with ESMTP; 09 Mar 2009 06:04:00 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 9 Mar 2009 11:03:59 +0100
Message-ID: <EDC652A26FB23C4EB6384A4584434A04014947EA@307622ANEX5.global.avaya.com>
In-Reply-To: <058e01c9a09a$78b0cbf0$0201a8c0@nsnintra.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [OPSAWG](final)WGLCon	draft-ietf-opsawg-operations-and-management
Thread-Index: AcmgkOe2gvlWb+gBTO+RgpViexgM9QACM3wAAAERzrA=
References: <20090125164013.802B5129CDC6@newdev.eecs.harvard.edu><20090127083743.GB12355@elstar.local><1b2701c99ea3$2e4dd380$0600a8c0@china.huawei.com><EDC652A26FB23C4EB6384A4584434A040149467C@307622ANEX5.global.avaya.com> <20090309082731.GB5676@elstar.local> <058e01c9a09a$78b0cbf0$0201a8c0@nsnintra.net>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Hannes Tschofenig" <Hannes.Tschofenig@gmx.net>, <j.schoenwaelder@jacobs-university.de>
Cc: opsawg@ietf.org
Subject: Re: [OPSAWG] (final)WGLCon	draft-ietf-opsawg-operations-and-management
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Mar 2009 10:03:31 -0000

The answer is I believe in the document itself:=20

>   The purpose of this document is to provide guidance to authors and
   reviewers of documents defining new protocols or protocol extensions,
   about covering aspects of operations and management that should be
   considered.

Appendix A will be used in the future as a reference for the authors and
OPS-DIR reviewers.=20

As I mentioned OPS-DIR I am copying them, in case they are not all
subscribed to opsawg. I apologize for the double posting.=20

Dan
=20

> -----Original Message-----
> From: Hannes Tschofenig [mailto:Hannes.Tschofenig@gmx.net]=20
> Sent: Monday, March 09, 2009 11:36 AM
> To: j.schoenwaelder@jacobs-university.de; Romascanu, Dan (Dan)
> Cc: opsawg@ietf.org
> Subject: RE: [OPSAWG](final)WGLCon=20
> draft-ietf-opsawg-operations-and-management
>=20
> >How is this document been used once it has been published as RFC?
>=20
> That's a question I had as well.
>=20
>=20

From j.schoenwaelder@jacobs-university.de  Mon Mar  9 04:12:38 2009
Return-Path: <j.schoenwaelder@jacobs-university.de>
X-Original-To: opsawg@core3.amsl.com
Delivered-To: opsawg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 26A233A6C78 for <opsawg@core3.amsl.com>; Mon,  9 Mar 2009 04:12:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.087
X-Spam-Level: 
X-Spam-Status: No, score=-2.087 tagged_above=-999 required=5 tests=[AWL=0.162,  BAYES_00=-2.599, HELO_EQ_DE=0.35]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2An8aj8jmVmZ for <opsawg@core3.amsl.com>; Mon,  9 Mar 2009 04:12:37 -0700 (PDT)
Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) by core3.amsl.com (Postfix) with ESMTP id 370183A6BFC for <opsawg@ietf.org>; Mon,  9 Mar 2009 04:12:37 -0700 (PDT)
Received: from localhost (demetrius4.jacobs-university.de [212.201.44.49]) by hermes.jacobs-university.de (Postfix) with ESMTP id C058AC0010; Mon,  9 Mar 2009 12:13:10 +0100 (CET)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius4.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id rg4Hjg1FK1n6; Mon,  9 Mar 2009 12:13:09 +0100 (CET)
Received: from elstar.local (elstar.iuhb02.iu-bremen.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id 64639C000F; Mon,  9 Mar 2009 12:13:09 +0100 (CET)
Received: by elstar.local (Postfix, from userid 501) id F0E719F2999; Mon,  9 Mar 2009 12:13:07 +0100 (CET)
Date: Mon, 9 Mar 2009 12:13:07 +0100
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
Message-ID: <20090309111307.GD6444@elstar.local>
Mail-Followup-To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>, David Harrington <ietfdbh@comcast.net>, "Scott O. Bradner" <sob@harvard.edu>, "opsawg@ietf.org" <opsawg@ietf.org>
References: <20090125164013.802B5129CDC6@newdev.eecs.harvard.edu> <20090127083743.GB12355@elstar.local> <1b2701c99ea3$2e4dd380$0600a8c0@china.huawei.com> <EDC652A26FB23C4EB6384A4584434A040149467C@307622ANEX5.global.avaya.com> <20090309082731.GB5676@elstar.local> <EDC652A26FB23C4EB6384A4584434A0401494781@307622ANEX5.global.avaya.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <EDC652A26FB23C4EB6384A4584434A0401494781@307622ANEX5.global.avaya.com>
User-Agent: Mutt/1.5.19 (2009-01-05)
Cc: "opsawg@ietf.org" <opsawg@ietf.org>
Subject: Re: [OPSAWG] (final)WGLCondraft-ietf-opsawg-operations-and-management
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: j.schoenwaelder@jacobs-university.de
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Mar 2009 11:12:38 -0000

On Mon, Mar 09, 2009 at 09:59:27AM +0100, Romascanu, Dan (Dan) wrote:

> Speaking as both:
> 
> We already discussed this document in the WG for more than one year. I
> hope that by sending it to the IESG and entering IETF Last Call we shall
> generate a level of response from other areas in the IETF who are
> 'customers' and 'users' of this document.

Discussed for more than one year, but not intensively as far as I
recall from the mailing list and the WG meetings I have attended. And
discussed without reaching a clear consensus what the scope, target,
and organization of this document should be as I read the WG last
reviews.

/js

-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: +49 421 200 3587         Campus Ring 1, 28759 Bremen, Germany
Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>

From ietfdbh@comcast.net  Mon Mar  9 09:15:34 2009
Return-Path: <ietfdbh@comcast.net>
X-Original-To: opsawg@core3.amsl.com
Delivered-To: opsawg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EAB8628C1C5 for <opsawg@core3.amsl.com>; Mon,  9 Mar 2009 09:15:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.498
X-Spam-Level: 
X-Spam-Status: No, score=-2.498 tagged_above=-999 required=5 tests=[AWL=0.101,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id buNzcRONrtLV for <opsawg@core3.amsl.com>; Mon,  9 Mar 2009 09:15:33 -0700 (PDT)
Received: from QMTA10.westchester.pa.mail.comcast.net (qmta10.westchester.pa.mail.comcast.net [76.96.62.17]) by core3.amsl.com (Postfix) with ESMTP id 7821F3A69DE for <opsawg@ietf.org>; Mon,  9 Mar 2009 09:15:33 -0700 (PDT)
Received: from OMTA02.westchester.pa.mail.comcast.net ([76.96.62.19]) by QMTA10.westchester.pa.mail.comcast.net with comcast id R1AU1b00A0QuhwU5A4G8Uf; Mon, 09 Mar 2009 16:16:08 +0000
Received: from Harrington73653 ([24.147.240.21]) by OMTA02.westchester.pa.mail.comcast.net with comcast id R4G71b00m0UQ6dC3N4G7SV; Mon, 09 Mar 2009 16:16:08 +0000
From: "David Harrington" <ietfdbh@comcast.net>
To: <j.schoenwaelder@jacobs-university.de>, "'Romascanu, Dan \(Dan\)'" <dromasca@avaya.com>
References: <20090125164013.802B5129CDC6@newdev.eecs.harvard.edu> <20090127083743.GB12355@elstar.local> <1b2701c99ea3$2e4dd380$0600a8c0@china.huawei.com> <EDC652A26FB23C4EB6384A4584434A040149467C@307622ANEX5.global.avaya.com> <20090309082731.GB5676@elstar.local> <EDC652A26FB23C4EB6384A4584434A0401494781@307622ANEX5.global.avaya.com> <20090309111307.GD6444@elstar.local>
Date: Mon, 9 Mar 2009 12:16:06 -0400
Message-ID: <04c301c9a0d2$5a110150$0600a8c0@china.huawei.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <20090309111307.GD6444@elstar.local>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
Thread-Index: AcmgqAlvRjnOtnGxTNKwWLtW7AMU1AAHQlsA
Cc: opsawg@ietf.org
Subject: Re: [OPSAWG] (final)WGLCondraft-ietf-opsawg-operations-and-management
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Mar 2009 16:15:35 -0000

Hi,

Here is my take on the discussions of scope, target, and organization.
Juergen, you did not clearly identify what you meant by these terms,
so my answers are based on my interpretation of those terms.

***** Scope *****
The WG discussed not getting into the mire of trying to distinguish
services and networks and devices. Many SDOs have tried to do that,
with varying levels of success. We do not want to boil the ocean. A
later discussion in opsawg brought up the inconsistencies of what OAM
means; another work-in-progress addresses that discussion.

The IETF focuses on protocols, and the WG had the discussion that this
document should focus on protocols, not services. The charter also
defines the scope:
"(A) Development of a BCP document that will provide guidelines for
authors and a reference for reviewers of IETF documents that specify 
new protocols or protocol extensions about the information about 
operational and manageability requirements that needs to be covered in

these documents"

If the chairs would like to codify the scope with a consensus call or
a declaration of scope, we can solve that issue.

***** Target *****
The target is IETF protocol developers. I was initially asked to write
such a document because the IESG was relaxing the "write a MIB"
requirement, and the IESG wanted something that gave guidelines to
protocol developers and reviewers about things that should be
considered for operating and managing new protocols (and extensions). 
The charter text above seems pretty clear what the target is.

***** Document Organization *****
When I first published this document, I mixed operations and
management together. But immediate feedback from people with
operations experience was that the document as written really was a
managment guidelines document, and said little about operations.
Operators seem to consider the two things to be different, while NM
protocol developers seem to see them as one thing. 

So, on advice from the operator community, and I believe based on
consensus of this WG, I separated out the issues and sought
contributions for the operations portion to build separate chapters.
And people did contribute, mostly in little snippets of operational
considerations. 

Unfortunately, I could not get solid advice about any overall approach
that let us organize the snippets into a story-line or anything,
because, as far as I have been able to determine from talking with
operators, every organization has their own "story-line" - their own
way of doing things. I suspect all we can really do is present these
snippets of information, and hope that subsequent feedback will
identify commonalities so we can develop a better storyline.

About the best I could see us providing for a storyline was some
discussion of the motivation for writing the document, and providing
some history of efforts to identify "requirements" for operations and
management. That is why I have a whole section discussing previous
efforts, starting with the decision to try to keep a separation
between data models and protocols and modeling languages, and
differentiating data models and information models, and repeated
attempts to identify common requirements for configuration, and
information models for things like policy-based management.

***** Document Status *****
I think the current document is very rough. I agree it has no
storyline like most good internet-drafts. I tried to organize the
snippets to provide some conceptual absractions of the storyline of
operating a network - installation, config, performance monitoring,
notifications, usage accounting. I welcome new text. I welcome
suggestions to move text from section to section. I welcome
suggestions to rename sections. But it is hard for me as editor to
reorganize the whole document without clear consensus that
operations+mgmt should be separated/mixed-together or that the whole
history/motivation section should be thrown out.

Some consensus determination would help me edit this document.
Some active discussion might motivate me to spend more time editing
this document to represent WG consensus. My previosu attempts to
stimulate discussion have generally led to me being emailed another
snippet or so, and no serious discussion of guidelines for things to
be considered about operating and managing new protocols.

***** Non-document Issues *****
I think that one of the issues that really needs some resolution, that
is not related to the editing function, is how the ADs/IESG plan to
use such a document. If this is going to be used to require an
"Operations and Management Considerations" section in every document,
and to dictate what content must be in such a section, then the WG
probably wants to severely limit what goes into this document (if they
are willing to publish the document at all). If this document is
informational "guidelines", not requirements, then we can add more
(optional) guidelines for people to consider. 

dbh

> -----Original Message-----
> From: Juergen Schoenwaelder 
> [mailto:j.schoenwaelder@jacobs-university.de] 
> Sent: Monday, March 09, 2009 7:13 AM
> To: Romascanu, Dan (Dan)
> Cc: David Harrington; Scott O. Bradner; opsawg@ietf.org
> Subject: Re: 
> [OPSAWG](final)WGLCondraft-ietf-opsawg-operations-and-management
> 
> On Mon, Mar 09, 2009 at 09:59:27AM +0100, Romascanu, Dan (Dan)
wrote:
> 
> > Speaking as both:
> > 
> > We already discussed this document in the WG for more than 
> one year. I
> > hope that by sending it to the IESG and entering IETF Last 
> Call we shall
> > generate a level of response from other areas in the IETF who are
> > 'customers' and 'users' of this document.
> 
> Discussed for more than one year, but not intensively as far as I
> recall from the mailing list and the WG meetings I have attended.
And
> discussed without reaching a clear consensus what the scope, target,
> and organization of this document should be as I read the WG last
> reviews.
> 
> /js
> 
> -- 
> Juergen Schoenwaelder           Jacobs University Bremen gGmbH
> Phone: +49 421 200 3587         Campus Ring 1, 28759 Bremen, Germany
> Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>
> 


From ietfdbh@comcast.net  Mon Mar  9 12:02:47 2009
Return-Path: <ietfdbh@comcast.net>
X-Original-To: opsawg@core3.amsl.com
Delivered-To: opsawg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F2FE728C249 for <opsawg@core3.amsl.com>; Mon,  9 Mar 2009 12:02:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.196
X-Spam-Level: 
X-Spam-Status: No, score=-2.196 tagged_above=-999 required=5 tests=[AWL=-0.197, BAYES_00=-2.599, J_CHICKENPOX_34=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R4YlG+-nB+ba for <opsawg@core3.amsl.com>; Mon,  9 Mar 2009 12:02:45 -0700 (PDT)
Received: from QMTA02.westchester.pa.mail.comcast.net (qmta02.westchester.pa.mail.comcast.net [76.96.62.24]) by core3.amsl.com (Postfix) with ESMTP id D939A28C225 for <opsawg@ietf.org>; Mon,  9 Mar 2009 12:02:19 -0700 (PDT)
Received: from OMTA11.westchester.pa.mail.comcast.net ([76.96.62.36]) by QMTA02.westchester.pa.mail.comcast.net with comcast id R5Zt1b07y0mv7h05272uGn; Mon, 09 Mar 2009 19:02:54 +0000
Received: from Harrington73653 ([24.147.240.21]) by OMTA11.westchester.pa.mail.comcast.net with comcast id R72u1b0050UQ6dC3X72uMl; Mon, 09 Mar 2009 19:02:54 +0000
From: "David Harrington" <ietfdbh@comcast.net>
To: <j.schoenwaelder@jacobs-university.de>, "'Scott O. Bradner'" <sob@harvard.edu>
References: <20090125164013.802B5129CDC6@newdev.eecs.harvard.edu> <20090127083743.GB12355@elstar.local>
Date: Mon, 9 Mar 2009 15:02:53 -0400
Message-ID: <060601c9a0e9$a67995e0$0600a8c0@china.huawei.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <20090127083743.GB12355@elstar.local>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
Thread-Index: AcmAWo+ESxmBZwnbQl6+/MpVvh9zNAge2fmg
Cc: opsawg@ietf.org
Subject: Re: [OPSAWG] (final) WGLCon	draft-ietf-opsawg-operations-and-management
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Mar 2009 19:02:47 -0000

Hi,

inline. 
I am responding to input because I am not sure how to convert reviews
like this into editing instructions.

> -----Original Message-----
> From: opsawg-bounces@ietf.org 
> [mailto:opsawg-bounces@ietf.org] On Behalf Of Juergen Schoenwaelder
[...]
> - The document makes a distinction between "Operational
>   Considerations" (section 3) and "Management Considerations"
(section
>   4) and I am not sure where the difference really is. I appears
that
>   section 4 is much more management technology oriented and
organized
>   following the FCAPS model but in general, I do not really see why
>   some issues are operational considerations and others management
>   considerations. Perhaps the document can be streamlined by merging
>   these two sections together. (For example, 3.6 and 4.3.1 do in my
>   view pretty much belong together.)

They are obviously closely related. They are separated because
feedback from operators say there is a distinction. I notice that our
area is called the "operations and Management Area"; if they are the
same, why do we name the area this way?

Are specific snippets of text more one than the other, or equally so?
Yeah, possibly. If there is something under operations you think is
really only about management, please let me know and we will look at
moving it. But sometimes, how a protocol designer expects operators to
deploy management for their protocol is an operational consideration.
It cna be tough to separate the two related concepts.

> 
> - At times, the document reads like a collection of text fragments
>   taken from other documents without a very clear story line. I
>   sometimes had the feeling that things were not developing in a
>   "natural way" (but it is difficult for me to say what such a
>   "natural way" would look like without going through the whole
>   exercise to dissect the document into its fragments and
reassembling
>   the puzzle again).

That is exactly what it is. I have had difficulty finding a storyline
in the many snippets contributions I have received, without getting
into debates about which "management architecture" or "operational
architectures" are reflected. One of the reasons this document is so
hard to edit is because there are few standard "architectures" for
operations and for management. This document hopefully will begin to
guide people toward some similar "best current practices", but "best"
is surely debatable if you try to craft a full storyline. 

> 
> - I am not sure the discussion what the "IETF Management Framework"
>   means (historically and today) is that useful for designers of new
>   protocols and it might raise controversial discussions. Why not
>   replace this material with a section that provide a high-level
>   summary of the management technologies that can be considered by
>   protocol designers? In terms of structure, this could mean that
the
>   document should have this structure (in terms of top-level
>   sections):

I think the "IETF Management Framework" section provides some
background and motivation for the guidelines. I can rename the section
Motivation and background if you prefer. Ultimately, I think it comes
down to "the IETF had a framework, but operators are not happy eith
it, so the the IETF has been considering how to change that framework.
In the absence of any real framework, these guidelines might help
produce protocols that can be added to operational environment without
major accident, and then can be managed effectively using a variety of
manageent protocols that conform to contradictory management
requirements."

I have commented out the section in the current sources, and I can
post an update with this section removed, if that is WG consensus. But
I think that the motivation and background for the guidelines will be
sorely lacking if we remove this section. The community has done lots
of work trying to determine best current practice for ops+mgmt, and
this section points people to those previous discussiosn so they don't
have to repeat those discussions all over again. Have some things
changed since those discussions? Of course. But we will never finish
if we just keep discussing requirements for almost-the-same wheels
over and over and over. Let's point out what has already been
discussed, and try to keep things moving forward.

The WG consensus was to move the discussion of available management
technologies into a separate document from the guidelines.

> 
>   1. Introduction
>   2. Available Management Technologies
>      (briefly mention SNMP, SYSLOG, RADIUS/DIAMETER, NETCONF, IPFIX,
>      CLIs, GUIs, ...  and outline where they are particularly strong
>      and where not; this should be short and not a long elaboration)
>   3. Operational and Management Considerations
>   4. Documentation Guidelines
>   .. ...
> 
>   This would lift some of the text currently in section 4 into
section
>   2. I also killed the current section 2 since the core of this is
>   already discussed in the introduction. As an alterntative, one
could
>   keep a section "Design for Operations and Management" but then
some
>   of the discussion currently in the introduction should be moved.
> 
> - The "Terminology" section explains why RFC 2119 language is not
used
>   and then defines the terms "new protocol" and "protocol
designers".
>   The document later has quite some text related to terminology
(e.g.
>   the discussion of information model vs. data model). One option to
>   consider is to move all text discussing or clarifying terminology
>   into this "Terminology" section (including the text fragments
>   pointing to RFC 3198 and RFC 3444).

Information and Data models seem to be very management-oriented to me.
I do not view these typically as exercises undertaken by operators
operating networks, but by engineers providing support for management.
So, in my opinion, this discussion belongs under "management
considerations", not operational considerations.

> 
> Some editorial nits:
> 
> - Define the acronym CLI the first time it is used.

done.

> 
> - Is "later/never phase" a typo or there by intention?

fixed.

> 
> - I am not sure this sentence is correct:
> 
>     This document sets forth a list of subjective guidelines 
> and a list
>     of objective criteria by which a protocol designer can evaluate
>     whether the protocol that he/she has developed addresses common
>      operations and management needs. 
> 
>   I am actually not sure whether the distinction between "subjective
>   guidelines" and "objective criteria" is worth to have. What I
>   believe is valuable is the checklist phrased as a collection of
>   questions to consider.

Yes. I have had a particular problem with the checklist. Because the
main text is all snippets, and there is no storyline or prioritization
of snippets, the checklist could easily end up being a repeat of all
the snippets.

>   
> - The first paragraph in 2.1 should in my opinion cite RFC 3410. But
>   as mentioned above, I am not a big fan of this discussion at all.

In my copy of the -05- revision, the first paragraph of 2.1 already
cites RFC3410.

> 
> - s/algoithms/algorithms
fixed.

> 
> - Some text on top of page 8 that looks scratch pad text.
I capitalized the first word in each sentence. I can put bullet
symbols in fron of each of these snippets, which related to the last
paragraph on page 7. Would that be more acceptable? I would merge them
into a paragraph, but they are making different points.

> 
> - s/should there be/Should there be
fixed.
> 
> - s/gyaranteed/guaranteed
fixed
> 
> - garbaled sentence
> 
>      or can the right
>      counters that can be polled as needed?
fixed.
> 
> - s/desoigners/designer
fixed.
> 
> - s/For example, Sometimes/For example, sometimes
fixed.
> 
> - s/should they stop counting/Should they stop counting
fixed.
> 
> - A.1: Make it clear that scalability in terms of operations and
>   management is meant, not in terms of the primary protocol
functions.
> 
>   OLD
> 
>   Does the solution scale well?
> 
>   NEW
> 
>   Does the solution scale well from the operational and management
>   perspective?
done.
> 
> - A.1: Capitalize the sentences with the questions consistently.
I think I got them all.

> 
> - A.1: Add the following:
> 
>     Are there any coexistance issues?
done.
> 
> - A.1: Add some more detailed questions for the items refering to
3.5,
>        3.6 and 4.1.

I could use some specific suggestions about which detailed questions
should appear in the checklist.

dbh


From dromasca@avaya.com  Mon Mar  9 12:23:08 2009
Return-Path: <dromasca@avaya.com>
X-Original-To: opsawg@core3.amsl.com
Delivered-To: opsawg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2C75C3A68AA for <opsawg@core3.amsl.com>; Mon,  9 Mar 2009 12:23:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.524
X-Spam-Level: 
X-Spam-Status: No, score=-2.524 tagged_above=-999 required=5 tests=[AWL=0.075,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tpzGx5cQ9Uor for <opsawg@core3.amsl.com>; Mon,  9 Mar 2009 12:23:07 -0700 (PDT)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by core3.amsl.com (Postfix) with ESMTP id 96AA83A6C1D for <opsawg@ietf.org>; Mon,  9 Mar 2009 12:22:58 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.38,330,1233550800"; d="scan'208";a="164062110"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 09 Mar 2009 15:23:32 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14]) by co300216-co-erhwest-out.avaya.com with ESMTP; 09 Mar 2009 15:23:31 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 9 Mar 2009 20:23:26 +0100
Message-ID: <EDC652A26FB23C4EB6384A4584434A04014949FB@307622ANEX5.global.avaya.com>
In-Reply-To: <20090309111307.GD6444@elstar.local>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [OPSAWG](final)WGLCondraft-ietf-opsawg-operations-and-management
Thread-Index: AcmgqBvFDWURWCDMS8CMtttmMBbYNgAQy6XA
References: <20090125164013.802B5129CDC6@newdev.eecs.harvard.edu> <20090127083743.GB12355@elstar.local> <1b2701c99ea3$2e4dd380$0600a8c0@china.huawei.com> <EDC652A26FB23C4EB6384A4584434A040149467C@307622ANEX5.global.avaya.com> <20090309082731.GB5676@elstar.local> <EDC652A26FB23C4EB6384A4584434A0401494781@307622ANEX5.global.avaya.com> <20090309111307.GD6444@elstar.local>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <j.schoenwaelder@jacobs-university.de>
Cc: opsawg@ietf.org
Subject: Re: [OPSAWG] (final)WGLCondraft-ietf-opsawg-operations-and-management
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Mar 2009 19:23:08 -0000

=20

> -----Original Message-----
> From: Juergen Schoenwaelder=20
> [mailto:j.schoenwaelder@jacobs-university.de]=20
> Sent: Monday, March 09, 2009 1:13 PM
> To: Romascanu, Dan (Dan)
> Cc: David Harrington; Scott O. Bradner; opsawg@ietf.org
> Subject: Re:=20
> [OPSAWG](final)WGLCondraft-ietf-opsawg-operations-and-management
>=20
> On Mon, Mar 09, 2009 at 09:59:27AM +0100, Romascanu, Dan (Dan) wrote:
>=20
> > Speaking as both:
> >=20
> > We already discussed this document in the WG for more than=20
> one year. I=20
> > hope that by sending it to the IESG and entering IETF Last Call we=20
> > shall generate a level of response from other areas in the IETF who=20
> > are 'customers' and 'users' of this document.
>=20
> Discussed for more than one year, but not intensively as far=20
> as I recall from the mailing list and the WG meetings I have=20
> attended. And discussed without reaching a clear consensus=20
> what the scope, target, and organization of this document=20
> should be as I read the WG last reviews.
>=20
> /js
>=20

As a contributor my opinion is that the scope and the target is well
explained in the introductory section. The organization is certainly
debatable, but this is to a certain extent in the eye of the beholder,
and I do not have a clear feeling that further discussions in the WG
will help improve the document in a revolutionary manner.=20

As an A-D I believe that the IETF needs this document yesterday.
Actually it was needed already three years ago.=20

Dan

From j.schoenwaelder@jacobs-university.de  Mon Mar  9 13:22:00 2009
Return-Path: <j.schoenwaelder@jacobs-university.de>
X-Original-To: opsawg@core3.amsl.com
Delivered-To: opsawg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D46733A69CF for <opsawg@core3.amsl.com>; Mon,  9 Mar 2009 13:22:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.09
X-Spam-Level: 
X-Spam-Status: No, score=-2.09 tagged_above=-999 required=5 tests=[AWL=0.159,  BAYES_00=-2.599, HELO_EQ_DE=0.35]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fZYmA8vhsmsA for <opsawg@core3.amsl.com>; Mon,  9 Mar 2009 13:22:00 -0700 (PDT)
Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) by core3.amsl.com (Postfix) with ESMTP id F1A4B3A69A8 for <opsawg@ietf.org>; Mon,  9 Mar 2009 13:21:59 -0700 (PDT)
Received: from localhost (demetrius3.jacobs-university.de [212.201.44.48]) by hermes.jacobs-university.de (Postfix) with ESMTP id C84CFC0027; Mon,  9 Mar 2009 21:22:33 +0100 (CET)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius3.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id 6V+Kf34mAsC2; Mon,  9 Mar 2009 21:22:33 +0100 (CET)
Received: from elstar.local (elstar.iuhb02.iu-bremen.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id CF7FAC0008; Mon,  9 Mar 2009 21:22:32 +0100 (CET)
Received: by elstar.local (Postfix, from userid 501) id 5962D9F6C09; Mon,  9 Mar 2009 21:22:31 +0100 (CET)
Date: Mon, 9 Mar 2009 21:22:31 +0100
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
Message-ID: <20090309202231.GA9282@elstar.local>
Mail-Followup-To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>, David Harrington <ietfdbh@comcast.net>, "Scott O. Bradner" <sob@harvard.edu>, "opsawg@ietf.org" <opsawg@ietf.org>
References: <20090125164013.802B5129CDC6@newdev.eecs.harvard.edu> <20090127083743.GB12355@elstar.local> <1b2701c99ea3$2e4dd380$0600a8c0@china.huawei.com> <EDC652A26FB23C4EB6384A4584434A040149467C@307622ANEX5.global.avaya.com> <20090309082731.GB5676@elstar.local> <EDC652A26FB23C4EB6384A4584434A0401494781@307622ANEX5.global.avaya.com> <20090309111307.GD6444@elstar.local> <EDC652A26FB23C4EB6384A4584434A04014949FB@307622ANEX5.global.avaya.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <EDC652A26FB23C4EB6384A4584434A04014949FB@307622ANEX5.global.avaya.com>
User-Agent: Mutt/1.5.19 (2009-01-05)
Cc: "opsawg@ietf.org" <opsawg@ietf.org>
Subject: Re: [OPSAWG] (final)WGLCondraft-ietf-opsawg-operations-and-management
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Mar 2009 20:22:00 -0000

On Mon, Mar 09, 2009 at 08:23:26PM +0100, Romascanu, Dan (Dan) wrote:
 
> As an A-D I believe that the IETF needs this document yesterday.
> Actually it was needed already three years ago. 

To do what with it?

/js

-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: +49 421 200 3587         Campus Ring 1, 28759 Bremen, Germany
Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>

From root@core3.amsl.com  Mon Mar  9 14:15:06 2009
Return-Path: <root@core3.amsl.com>
X-Original-To: opsawg@ietf.org
Delivered-To: opsawg@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id BE3553A6C6B; Mon,  9 Mar 2009 14:15:05 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20090309211505.BE3553A6C6B@core3.amsl.com>
Date: Mon,  9 Mar 2009 14:15:05 -0700 (PDT)
Cc: opsawg@ietf.org
Subject: [OPSAWG] I-D Action:draft-ietf-opsawg-syslog-msg-mib-02.txt
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Mar 2009 21:15:06 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Operations and Management Area Working Group Working Group of the IETF.


	Title           : Definitions of Managed Objects for Mapping SYSLOG Messages to Simple Network Management Protocol (SNMP) Notifications
	Author(s)       : J. Schoenwaelder, et al.
	Filename        : draft-ietf-opsawg-syslog-msg-mib-02.txt
	Pages           : 22
	Date            : 2009-03-09

This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community.
In particular, it defines a mapping of SYSLOG messages to Simple
Network Management Protocol (SNMP) notifications.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-opsawg-syslog-msg-mib-02.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-opsawg-syslog-msg-mib-02.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2009-03-09141232.I-D@ietf.org>


--NextPart--

From root@core3.amsl.com  Mon Mar  9 14:30:02 2009
Return-Path: <root@core3.amsl.com>
X-Original-To: opsawg@ietf.org
Delivered-To: opsawg@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id 15AB73A6B3B; Mon,  9 Mar 2009 14:30:01 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20090309213002.15AB73A6B3B@core3.amsl.com>
Date: Mon,  9 Mar 2009 14:30:02 -0700 (PDT)
Cc: opsawg@ietf.org
Subject: [OPSAWG] I-D Action:draft-ietf-opsawg-operations-and-management-06.txt
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Mar 2009 21:30:02 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Operations and Management Area Working Group Working Group of the IETF.


	Title           : Guidelines for Considering Operations and Management of New Protocols and Protocol Extensions
	Author(s)       : D. Harrington
	Filename        : draft-ietf-opsawg-operations-and-management-06.txt
	Pages           : 37
	Date            : 2009-03-09

New protocols or protocol extensions are best designed with due
consideration of functionality needed to operate and manage the
protocols.  Retrofitting operations and management is sub-optimal.
The purpose of this document is to provide guidance to authors and
reviewers of documents defining new protocols or protocol extensions,
about covering aspects of operations and management that should be
considered.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-opsawg-operations-and-management-06.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-opsawg-operations-and-management-06.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2009-03-09141707.I-D@ietf.org>


--NextPart--

From j.schoenwaelder@jacobs-university.de  Mon Mar  9 15:25:29 2009
Return-Path: <j.schoenwaelder@jacobs-university.de>
X-Original-To: opsawg@core3.amsl.com
Delivered-To: opsawg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D13573A6CE0 for <opsawg@core3.amsl.com>; Mon,  9 Mar 2009 15:25:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.093
X-Spam-Level: 
X-Spam-Status: No, score=-2.093 tagged_above=-999 required=5 tests=[AWL=0.156,  BAYES_00=-2.599, HELO_EQ_DE=0.35]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BADa4600DWi0 for <opsawg@core3.amsl.com>; Mon,  9 Mar 2009 15:25:28 -0700 (PDT)
Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) by core3.amsl.com (Postfix) with ESMTP id 00E093A6CDF for <opsawg@ietf.org>; Mon,  9 Mar 2009 15:25:22 -0700 (PDT)
Received: from localhost (demetrius4.jacobs-university.de [212.201.44.49]) by hermes.jacobs-university.de (Postfix) with ESMTP id 689BFC0022; Mon,  9 Mar 2009 23:25:56 +0100 (CET)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius4.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id DoWF21Z6LMZV; Mon,  9 Mar 2009 23:25:55 +0100 (CET)
Received: from elstar.local (elstar.iuhb02.iu-bremen.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id 34FECC0008; Mon,  9 Mar 2009 23:25:55 +0100 (CET)
Received: by elstar.local (Postfix, from userid 501) id B07579F71A2; Mon,  9 Mar 2009 23:25:53 +0100 (CET)
Date: Mon, 9 Mar 2009 23:25:53 +0100
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: Martin Bjorklund <mbj@tail-f.com>
Message-ID: <20090309222553.GA9746@elstar.local>
Mail-Followup-To: Martin Bjorklund <mbj@tail-f.com>, "opsawg@ietf.org" <opsawg@ietf.org>
References: <20090224160512.GA26471@elstar.iuhb02.iu-bremen.de> <20090225.100537.248875324.mbj@tail-f.com> <20090225112552.GD27716@elstar.iuhb02.iu-bremen.de> <20090225.133724.11667207.mbj@tail-f.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20090225.133724.11667207.mbj@tail-f.com>
User-Agent: Mutt/1.5.19 (2009-01-05)
Cc: "opsawg@ietf.org" <opsawg@ietf.org>
Subject: Re: [OPSAWG] comments on draft-ietf-opsawg-syslog-snmp-00
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Mar 2009 22:25:29 -0000

On Wed, Feb 25, 2009 at 01:37:24PM +0100, Martin Bjorklund wrote:
> Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de> wrote:
> > 
> > I just typed "I will do this" when I figured out that there is still a
> > potential problem. A MIB aware translator able to apply DISPLAY-HINTs
> > will turn a MacAddress binary value '00E0812E961E'h into
> > "00:E0:81:2E:96:1E" and a MIB unaware receiver might turn this back
> > into '30303A45303A38313A32453A39363A3145'h. This would be bad. I see
> > two options:
> > 
> > a) We always ship the hex value in addition to the rendered value. We
> >    might consider using base64 instead of hex to save space.
> > 
> > b) We restrict the alternate textual representations to DISPLAY-HINTs
> >    of the form 'Na' or 'Nt' where N is some number. This implies that
> >    a MacAddress or a DateAndTime value will be carried in hex / base64
> >    representation.
> > 
> > Hm, not nice.
> 
> [...]
> 
> > Given this, the simplest solution for the string
> > mapping problem mentioned above would be to actually do the same.
> 
> Yes.  An alternative could be that for the DISPLAY-HINTs in case b)
> above, the hex string does not need to be sent.

Yes, this should works. I have written this down in the updated ID I
have just submitted.

/js

-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: +49 421 200 3587         Campus Ring 1, 28759 Bremen, Germany
Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>

From root@core3.amsl.com  Mon Mar  9 15:30:01 2009
Return-Path: <root@core3.amsl.com>
X-Original-To: opsawg@ietf.org
Delivered-To: opsawg@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id BFE583A676A; Mon,  9 Mar 2009 15:30:01 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20090309223001.BFE583A676A@core3.amsl.com>
Date: Mon,  9 Mar 2009 15:30:01 -0700 (PDT)
Cc: opsawg@ietf.org
Subject: [OPSAWG] I-D Action:draft-ietf-opsawg-syslog-snmp-01.txt
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Mar 2009 22:30:01 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Operations and Management Area Working Group Working Group of the IETF.


	Title           : Mapping Simple Network Management Protocol (SNMP) Notifications to SYSLOG Messages
	Author(s)       : V. Marinov, J. Schoenwaelder
	Filename        : draft-ietf-opsawg-syslog-snmp-01.txt
	Pages           : 15
	Date            : 2009-03-09

This memo defines a mapping from Simple Network Management Protocol
(SNMP) notifications to SYSLOG notifications.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-opsawg-syslog-snmp-01.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-opsawg-syslog-snmp-01.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2009-03-09152354.I-D@ietf.org>


--NextPart--

From dromasca@avaya.com  Tue Mar 10 01:55:47 2009
Return-Path: <dromasca@avaya.com>
X-Original-To: opsawg@core3.amsl.com
Delivered-To: opsawg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B87313A67B4 for <opsawg@core3.amsl.com>; Tue, 10 Mar 2009 01:55:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.518
X-Spam-Level: 
X-Spam-Status: No, score=-2.518 tagged_above=-999 required=5 tests=[AWL=0.081,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xs2yTa6Ww3jM for <opsawg@core3.amsl.com>; Tue, 10 Mar 2009 01:55:40 -0700 (PDT)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by core3.amsl.com (Postfix) with ESMTP id 860BE3A6A14 for <opsawg@ietf.org>; Tue, 10 Mar 2009 01:55:40 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.38,335,1233550800"; d="scan'208";a="164133455"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 10 Mar 2009 04:56:14 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14]) by co300216-co-erhwest-out.avaya.com with ESMTP; 10 Mar 2009 04:56:14 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 10 Mar 2009 09:55:51 +0100
Message-ID: <EDC652A26FB23C4EB6384A4584434A0401494A9E@307622ANEX5.global.avaya.com>
In-Reply-To: <20090309202231.GA9282@elstar.local>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [OPSAWG](final)WGLCondraft-ietf-opsawg-operations-and-management
Thread-Index: Acmg9MvpRC+RMQdeTnK0p+7qKnAK4QAaLExQ
References: <20090125164013.802B5129CDC6@newdev.eecs.harvard.edu> <20090127083743.GB12355@elstar.local> <1b2701c99ea3$2e4dd380$0600a8c0@china.huawei.com> <EDC652A26FB23C4EB6384A4584434A040149467C@307622ANEX5.global.avaya.com> <20090309082731.GB5676@elstar.local> <EDC652A26FB23C4EB6384A4584434A0401494781@307622ANEX5.global.avaya.com> <20090309111307.GD6444@elstar.local> <EDC652A26FB23C4EB6384A4584434A04014949FB@307622ANEX5.global.avaya.com> <20090309202231.GA9282@elstar.local>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Juergen Schoenwaelder" <j.schoenwaelder@jacobs-university.de>
Cc: opsawg@ietf.org
Subject: Re: [OPSAWG] (final)WGLCondraft-ietf-opsawg-operations-and-management
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Mar 2009 08:55:47 -0000

   ... to provide guidance to authors and
   reviewers of documents defining new protocols or protocol extensions,
   about covering aspects of operations and management that should be
   considered.

(as the document Abstract and the OPSAWG say)


Dan
=20

> -----Original Message-----
> From: Juergen Schoenwaelder=20
> [mailto:j.schoenwaelder@jacobs-university.de]=20
> Sent: Monday, March 09, 2009 10:23 PM
> To: Romascanu, Dan (Dan)
> Cc: David Harrington; Scott O. Bradner; opsawg@ietf.org
> Subject:=20
> Re:[OPSAWG](final)WGLCondraft-ietf-opsawg-operations-and-management
>=20
> On Mon, Mar 09, 2009 at 08:23:26PM +0100, Romascanu, Dan (Dan) wrote:
> =20
> > As an A-D I believe that the IETF needs this document yesterday.
> > Actually it was needed already three years ago.=20
>=20
> To do what with it?
>=20
> /js
>=20
> --=20
> Juergen Schoenwaelder           Jacobs University Bremen gGmbH
> Phone: +49 421 200 3587         Campus Ring 1, 28759 Bremen, Germany
> Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>
>=20

From j.schoenwaelder@jacobs-university.de  Tue Mar 10 02:17:14 2009
Return-Path: <j.schoenwaelder@jacobs-university.de>
X-Original-To: opsawg@core3.amsl.com
Delivered-To: opsawg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2948B3A69A8 for <opsawg@core3.amsl.com>; Tue, 10 Mar 2009 02:17:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level: 
X-Spam-Status: No, score=-2.096 tagged_above=-999 required=5 tests=[AWL=0.153,  BAYES_00=-2.599, HELO_EQ_DE=0.35]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cM772JGNv6h3 for <opsawg@core3.amsl.com>; Tue, 10 Mar 2009 02:17:13 -0700 (PDT)
Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) by core3.amsl.com (Postfix) with ESMTP id EEDCB3A67F5 for <opsawg@ietf.org>; Tue, 10 Mar 2009 02:17:12 -0700 (PDT)
Received: from localhost (demetrius4.jacobs-university.de [212.201.44.49]) by hermes.jacobs-university.de (Postfix) with ESMTP id 6934AC0044; Tue, 10 Mar 2009 10:17:47 +0100 (CET)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius4.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id JKnQJNf7GnEB; Tue, 10 Mar 2009 10:17:46 +0100 (CET)
Received: from elstar.local (elstar.iuhb02.iu-bremen.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id 4F8E2C0042; Tue, 10 Mar 2009 10:17:46 +0100 (CET)
Received: by elstar.local (Postfix, from userid 501) id CB8BDA016A0; Tue, 10 Mar 2009 10:17:44 +0100 (CET)
Date: Tue, 10 Mar 2009 10:17:44 +0100
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
Message-ID: <20090310091744.GA26800@elstar.local>
Mail-Followup-To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>, David Harrington <ietfdbh@comcast.net>, "Scott O. Bradner" <sob@harvard.edu>, "opsawg@ietf.org" <opsawg@ietf.org>
References: <20090125164013.802B5129CDC6@newdev.eecs.harvard.edu> <20090127083743.GB12355@elstar.local> <1b2701c99ea3$2e4dd380$0600a8c0@china.huawei.com> <EDC652A26FB23C4EB6384A4584434A040149467C@307622ANEX5.global.avaya.com> <20090309082731.GB5676@elstar.local> <EDC652A26FB23C4EB6384A4584434A0401494781@307622ANEX5.global.avaya.com> <20090309111307.GD6444@elstar.local> <EDC652A26FB23C4EB6384A4584434A04014949FB@307622ANEX5.global.avaya.com> <20090309202231.GA9282@elstar.local> <EDC652A26FB23C4EB6384A4584434A0401494A9E@307622ANEX5.global.avaya.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <EDC652A26FB23C4EB6384A4584434A0401494A9E@307622ANEX5.global.avaya.com>
User-Agent: Mutt/1.5.19 (2009-01-05)
Cc: "opsawg@ietf.org" <opsawg@ietf.org>
Subject: Re: [OPSAWG] (final)WGLCondraft-ietf-opsawg-operations-and-management
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Mar 2009 09:17:14 -0000

On Tue, Mar 10, 2009 at 09:55:51AM +0100, Romascanu, Dan (Dan) wrote:
>    ... to provide guidance to authors and
>    reviewers of documents defining new protocols or protocol extensions,
>    about covering aspects of operations and management that should be
>    considered.
> 
> (as the document Abstract and the OPSAWG say)

Probably the text in the abstract is a bit to abstract for me. I guess
I have to read the revised version David just posted as it might be
clearer than the version I reviewed in spelling out what the concrete
recommendations are for authors and reviewers.

/js

-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: +49 421 200 3587         Campus Ring 1, 28759 Bremen, Germany
Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>

From sob@harvard.edu  Wed Mar 11 11:06:05 2009
Return-Path: <sob@harvard.edu>
X-Original-To: opsawg@core3.amsl.com
Delivered-To: opsawg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C0E1B3A6B9E for <opsawg@core3.amsl.com>; Wed, 11 Mar 2009 11:06:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.301
X-Spam-Level: 
X-Spam-Status: No, score=-2.301 tagged_above=-999 required=5 tests=[AWL=0.298,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RtWOht1DfVFu for <opsawg@core3.amsl.com>; Wed, 11 Mar 2009 11:06:05 -0700 (PDT)
Received: from newdev.eecs.harvard.edu (newdev.eecs.harvard.edu [140.247.60.212]) by core3.amsl.com (Postfix) with ESMTP id 1EAD03A6810 for <opsawg@ietf.org>; Wed, 11 Mar 2009 11:06:05 -0700 (PDT)
Received: by newdev.eecs.harvard.edu (Postfix, from userid 501) id D74841483B97; Wed, 11 Mar 2009 14:06:40 -0400 (EDT)
To: opsawg@ietf.org
Message-Id: <20090311180640.D74841483B97@newdev.eecs.harvard.edu>
Date: Wed, 11 Mar 2009 14:06:40 -0400 (EDT)
From: sob@harvard.edu (Scott O. Bradner)
Subject: Re: [OPSAWG] I-D Action:draft-ietf-opsawg-syslog-snmp-01.txt - ready for WGLC?
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Mar 2009 18:06:05 -0000

is the updated version of I-D Action:draft-ietf-opsawg-syslog-snmp-01.tx
ready for WLC?


Scott 

From j.schoenwaelder@jacobs-university.de  Wed Mar 11 12:00:07 2009
Return-Path: <j.schoenwaelder@jacobs-university.de>
X-Original-To: opsawg@core3.amsl.com
Delivered-To: opsawg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 69D0E28C1E5 for <opsawg@core3.amsl.com>; Wed, 11 Mar 2009 12:00:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.103
X-Spam-Level: 
X-Spam-Status: No, score=-2.103 tagged_above=-999 required=5 tests=[AWL=0.146,  BAYES_00=-2.599, HELO_EQ_DE=0.35]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4QxxVwzurH-j for <opsawg@core3.amsl.com>; Wed, 11 Mar 2009 12:00:06 -0700 (PDT)
Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) by core3.amsl.com (Postfix) with ESMTP id 9660628C200 for <opsawg@ietf.org>; Wed, 11 Mar 2009 12:00:05 -0700 (PDT)
Received: from localhost (demetrius3.jacobs-university.de [212.201.44.48]) by hermes.jacobs-university.de (Postfix) with ESMTP id 6523EC0039; Wed, 11 Mar 2009 20:00:41 +0100 (CET)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius3.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id CSI3PcuLCFvs; Wed, 11 Mar 2009 20:00:40 +0100 (CET)
Received: from elstar.local (elstar.iuhb02.iu-bremen.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id 790BDC0037; Wed, 11 Mar 2009 20:00:40 +0100 (CET)
Received: by elstar.local (Postfix, from userid 501) id F3D85A034F0; Wed, 11 Mar 2009 20:00:38 +0100 (CET)
Date: Wed, 11 Mar 2009 20:00:38 +0100
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: "Scott O. Bradner" <sob@harvard.edu>
Message-ID: <20090311190038.GB29633@elstar.local>
Mail-Followup-To: "Scott O. Bradner" <sob@harvard.edu>, "opsawg@ietf.org" <opsawg@ietf.org>
References: <20090311180640.D74841483B97@newdev.eecs.harvard.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20090311180640.D74841483B97@newdev.eecs.harvard.edu>
User-Agent: Mutt/1.5.19 (2009-01-05)
Cc: "opsawg@ietf.org" <opsawg@ietf.org>
Subject: Re: [OPSAWG] I-D Action:draft-ietf-opsawg-syslog-snmp-01.txt -	ready for WGLC?
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Mar 2009 19:00:07 -0000

On Wed, Mar 11, 2009 at 07:06:40PM +0100, Scott O. Bradner wrote:
 
> is the updated version of I-D
> Action:draft-ietf-opsawg-syslog-snmp-01.tx ready for WLC?

The MIB module <draft-ietf-opsawg-syslog-msg-mib-02.txt> is ready for
WG last call.

The SYSLOG to SNMP mapping <draft-ietf-opsawg-syslog-snmp-01.txt> is
missing 2-3 paragraphs in section 4, which I did not manage to
finalize before the ID cutoff.

I suggest to do the following: I can post updated version on March
23rd when the ID repository opens up again (these versions will then
also have the appropriate references to the SYSLOG RFCs) and these can
then go to WG last call. In the meantime, people are welcome to review
the two documents so that I can incorporate any editorial changes
etc. people might identify.

/js

-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: +49 421 200 3587         Campus Ring 1, 28759 Bremen, Germany
Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>

From cfinss@dial.pipex.com  Thu Mar 12 11:56:19 2009
Return-Path: <cfinss@dial.pipex.com>
X-Original-To: opsawg@core3.amsl.com
Delivered-To: opsawg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C9C5D28C295 for <opsawg@core3.amsl.com>; Thu, 12 Mar 2009 11:56:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.279
X-Spam-Level: 
X-Spam-Status: No, score=-1.279 tagged_above=-999 required=5 tests=[AWL=-0.367, BAYES_00=-2.599, DATE_IN_PAST_03_06=0.044, RCVD_IN_NJABL_PROXY=1.643]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 73K+0VFCEF2F for <opsawg@core3.amsl.com>; Thu, 12 Mar 2009 11:56:14 -0700 (PDT)
Received: from mk-outboundfilter-5.mail.uk.tiscali.com (mk-outboundfilter-5.mail.uk.tiscali.com [212.74.114.1]) by core3.amsl.com (Postfix) with ESMTP id 532EF28C284 for <opsawg@ietf.org>; Thu, 12 Mar 2009 11:56:14 -0700 (PDT)
X-Trace: 139648786/mk-outboundfilter-5.mail.uk.tiscali.com/PIPEX/$PIPEX-ACCEPTED/pipex-customers/62.188.17.11/None/cfinss@dial.pipex.com
X-SBRS: None
X-RemoteIP: 62.188.17.11
X-IP-MAIL-FROM: cfinss@dial.pipex.com
X-MUA: Microsoft Outlook Express 6.00.2800.1106Produced By Microsoft MimeOLE V6.00.2800.1106
X-IP-BHB: Once
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ArcEAKr3uEk+vBEL/2dsb2JhbACDJEOKDMRwB4JEBoE8BocnAg
X-IronPort-AV: E=Sophos;i="4.38,351,1233532800"; d="scan'208";a="139648786"
X-IP-Direction: IN
Received: from 1cust11.tnt1.lnd3.gbr.da.uu.net (HELO allison) ([62.188.17.11]) by smtp.pipex.tiscali.co.uk with SMTP; 12 Mar 2009 18:56:46 +0000
Message-ID: <001c01c9a33b$ad042de0$0601a8c0@allison>
From: "tom.petch" <cfinss@dial.pipex.com>
To: "David Harrington" <ietfdbh@comcast.net>, "'Romascanu, Dan \(Dan\)'" <dromasca@avaya.com>
References: <20090125164013.802B5129CDC6@newdev.eecs.harvard.edu><20090127083743.GB12355@elstar.local><1b2701c99ea3$2e4dd380$0600a8c0@china.huawei.com><EDC652A26FB23C4EB6384A4584434A040149467C@307622ANEX5.global.avaya.com><20090309082731.GB5676@elstar.local><EDC652A26FB23C4EB6384A4584434A0401494781@307622ANEX5.global.avaya.com><20090309111307.GD6444@elstar.local> <04c301c9a0d2$5a110150$0600a8c0@china.huawei.com>
Date: Thu, 12 Mar 2009 16:49:47 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Cc: opsawg@ietf.org
Subject: Re: [OPSAWG] (final)WGLCondraft-ietf-opsawg-operations-and-management
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: "tom.petch" <cfinss@dial.pipex.com>
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Mar 2009 18:56:19 -0000

David

Picking up on the question of Operations and Management,  I see a distinction
between these two which comes across most clearly in the IETF work that used to
be known as Sub-IP, where there is a distinct ITU-T flavour, doubtless not a
coincidence.  It seems possible that the operators you allude to are making the
same distinction.

I see a three way split.  Management is something static, it makes a change
which stays changed until changed again, usually via SNMP and SMI, but could be
by an equivalent functionality.

Control may achieve the same result but is dynamic, by signalling, by routing,
by invoking protection and such like.

Operations, often referred to as OAM, which may stand for Operations,
Administration and Maintenance is functionality in the data plane to verify its
correct operation - ping, traceroute and such like (as in
draft-vigoureux-mpls-tp-oam-requirements ).  On this basis, you can and probably
should have some OAM built into your control protocols <and> your management
protocols (eg as OSPF has, but SNMP has not)

And this last is usually configurable by the first and must operate
independently of the first.

So for me, a good protocol will have this last built into its semantics and
state machine, so that when things go wrong, that shows.  And for me, this last
is more important than the first even though the first encompasses more; usually
full FCAPS, with a data model, a protocol to access the data model and with the
ability to make changes where this is not inherent in the data model (perhaps
the ability to fire off a traceroute and get back the results).  SNMP takes the
view that everything is part of the data model, but other management systems do
not, and have separate protocol elements to cause actions and if you are moving
on from SNMP, then you should allow for that.

Tom Petch

----- Original Message -----
From: "David Harrington" <ietfdbh@comcast.net>
To: <j.schoenwaelder@jacobs-university.de>; "'Romascanu, Dan (Dan)'"
<dromasca@avaya.com>
Cc: <opsawg@ietf.org>
Sent: Monday, March 09, 2009 5:16 PM
Subject: Re: [OPSAWG](final)WGLCondraft-ietf-opsawg-operations-and-management


> Hi,
>
> Here is my take on the discussions of scope, target, and organization.
> Juergen, you did not clearly identify what you meant by these terms,
> so my answers are based on my interpretation of those terms.
>
> ***** Scope *****
> The WG discussed not getting into the mire of trying to distinguish
> services and networks and devices. Many SDOs have tried to do that,
> with varying levels of success. We do not want to boil the ocean. A
> later discussion in opsawg brought up the inconsistencies of what OAM
> means; another work-in-progress addresses that discussion.
>
> The IETF focuses on protocols, and the WG had the discussion that this
> document should focus on protocols, not services. The charter also
> defines the scope:
> "(A) Development of a BCP document that will provide guidelines for
> authors and a reference for reviewers of IETF documents that specify
> new protocols or protocol extensions about the information about
> operational and manageability requirements that needs to be covered in
>
> these documents"
>
> If the chairs would like to codify the scope with a consensus call or
> a declaration of scope, we can solve that issue.
>
> ***** Target *****
> The target is IETF protocol developers. I was initially asked to write
> such a document because the IESG was relaxing the "write a MIB"
> requirement, and the IESG wanted something that gave guidelines to
> protocol developers and reviewers about things that should be
> considered for operating and managing new protocols (and extensions).
> The charter text above seems pretty clear what the target is.
>
> ***** Document Organization *****
> When I first published this document, I mixed operations and
> management together. But immediate feedback from people with
> operations experience was that the document as written really was a
> managment guidelines document, and said little about operations.
> Operators seem to consider the two things to be different, while NM
> protocol developers seem to see them as one thing.
>
> So, on advice from the operator community, and I believe based on
> consensus of this WG, I separated out the issues and sought
> contributions for the operations portion to build separate chapters.
> And people did contribute, mostly in little snippets of operational
> considerations.
>
> Unfortunately, I could not get solid advice about any overall approach
> that let us organize the snippets into a story-line or anything,
> because, as far as I have been able to determine from talking with
> operators, every organization has their own "story-line" - their own
> way of doing things. I suspect all we can really do is present these
> snippets of information, and hope that subsequent feedback will
> identify commonalities so we can develop a better storyline.
>
> About the best I could see us providing for a storyline was some
> discussion of the motivation for writing the document, and providing
> some history of efforts to identify "requirements" for operations and
> management. That is why I have a whole section discussing previous
> efforts, starting with the decision to try to keep a separation
> between data models and protocols and modeling languages, and
> differentiating data models and information models, and repeated
> attempts to identify common requirements for configuration, and
> information models for things like policy-based management.
>
> ***** Document Status *****
> I think the current document is very rough. I agree it has no
> storyline like most good internet-drafts. I tried to organize the
> snippets to provide some conceptual absractions of the storyline of
> operating a network - installation, config, performance monitoring,
> notifications, usage accounting. I welcome new text. I welcome
> suggestions to move text from section to section. I welcome
> suggestions to rename sections. But it is hard for me as editor to
> reorganize the whole document without clear consensus that
> operations+mgmt should be separated/mixed-together or that the whole
> history/motivation section should be thrown out.
>
> Some consensus determination would help me edit this document.
> Some active discussion might motivate me to spend more time editing
> this document to represent WG consensus. My previosu attempts to
> stimulate discussion have generally led to me being emailed another
> snippet or so, and no serious discussion of guidelines for things to
> be considered about operating and managing new protocols.
>
> ***** Non-document Issues *****
> I think that one of the issues that really needs some resolution, that
> is not related to the editing function, is how the ADs/IESG plan to
> use such a document. If this is going to be used to require an
> "Operations and Management Considerations" section in every document,
> and to dictate what content must be in such a section, then the WG
> probably wants to severely limit what goes into this document (if they
> are willing to publish the document at all). If this document is
> informational "guidelines", not requirements, then we can add more
> (optional) guidelines for people to consider.
>
> dbh
>
> > -----Original Message-----
> > From: Juergen Schoenwaelder
> > [mailto:j.schoenwaelder@jacobs-university.de]


From j.schoenwaelder@jacobs-university.de  Thu Mar 12 15:06:43 2009
Return-Path: <j.schoenwaelder@jacobs-university.de>
X-Original-To: opsawg@core3.amsl.com
Delivered-To: opsawg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E22163A6BE6 for <opsawg@core3.amsl.com>; Thu, 12 Mar 2009 15:06:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.791
X-Spam-Level: 
X-Spam-Status: No, score=-1.791 tagged_above=-999 required=5 tests=[AWL=-0.142, BAYES_00=-2.599, HELO_EQ_DE=0.35, J_CHICKENPOX_35=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id McIzkUA-FaeI for <opsawg@core3.amsl.com>; Thu, 12 Mar 2009 15:06:38 -0700 (PDT)
Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) by core3.amsl.com (Postfix) with ESMTP id AA99C28C110 for <opsawg@ietf.org>; Thu, 12 Mar 2009 15:06:33 -0700 (PDT)
Received: from localhost (demetrius2.jacobs-university.de [212.201.44.47]) by hermes.jacobs-university.de (Postfix) with ESMTP id 33B0BC0056; Thu, 12 Mar 2009 23:07:11 +0100 (CET)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius2.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id Wx8sa9eLEyyB; Thu, 12 Mar 2009 23:07:10 +0100 (CET)
Received: from elstar.local (elstar.iuhb02.iu-bremen.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id 19188C0055; Thu, 12 Mar 2009 23:07:10 +0100 (CET)
Received: by elstar.local (Postfix, from userid 501) id 4ED9AA04FED; Thu, 12 Mar 2009 23:06:58 +0100 (CET)
Date: Thu, 12 Mar 2009 23:06:58 +0100
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: "tom.petch" <cfinss@dial.pipex.com>
Message-ID: <20090312220658.GD4327@elstar.local>
Mail-Followup-To: "tom.petch" <cfinss@dial.pipex.com>, "opsawg@ietf.org" <opsawg@ietf.org>
References: <20090125164013.802B5129CDC6@newdev.eecs.harvard.edu> <20090127083743.GB12355@elstar.local> <1b2701c99ea3$2e4dd380$0600a8c0@china.huawei.com> <EDC652A26FB23C4EB6384A4584434A040149467C@307622ANEX5.global.avaya.com> <20090309082731.GB5676@elstar.local> <EDC652A26FB23C4EB6384A4584434A0401494781@307622ANEX5.global.avaya.com> <20090309111307.GD6444@elstar.local> <04c301c9a0d2$5a110150$0600a8c0@china.huawei.com> <001c01c9a33b$ad042de0$0601a8c0@allison>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <001c01c9a33b$ad042de0$0601a8c0@allison>
User-Agent: Mutt/1.5.19 (2009-01-05)
Cc: "opsawg@ietf.org" <opsawg@ietf.org>
Subject: Re: [OPSAWG] (final)WGLCondraft-ietf-opsawg-operations-and-management
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Mar 2009 22:06:44 -0000

On Thu, Mar 12, 2009 at 04:49:47PM +0100, tom.petch wrote:

> Operations, often referred to as OAM, which may stand for
> Operations, Administration and Maintenance is functionality in the
> data plane to verify its correct operation - ping, traceroute and
> such like (as in draft-vigoureux-mpls-tp-oam-requirements ).  On
> this basis, you can and probably should have some OAM built into
> your control protocols <and> your management protocols (eg as OSPF
> has, but SNMP has not)

I do not understand the last sentence or the whole paragraph. It is
not clear which OAM functions OSPF has and that are missing in SNMP,
given your definition of OAM as "functionality in a X plane protocol
to verify its correct operation".

/js

-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: +49 421 200 3587         Campus Ring 1, 28759 Bremen, Germany
Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>

From cfinss@dial.pipex.com  Fri Mar 13 07:37:25 2009
Return-Path: <cfinss@dial.pipex.com>
X-Original-To: opsawg@core3.amsl.com
Delivered-To: opsawg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8CD873A6AB3 for <opsawg@core3.amsl.com>; Fri, 13 Mar 2009 07:37:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.048
X-Spam-Level: 
X-Spam-Status: No, score=-1.048 tagged_above=-999 required=5 tests=[AWL=-0.582, BAYES_05=-1.11, DATE_IN_PAST_03_06=0.044, J_CHICKENPOX_35=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VAkjRliOb4kf for <opsawg@core3.amsl.com>; Fri, 13 Mar 2009 07:37:18 -0700 (PDT)
Received: from mk-outboundfilter-6.mail.uk.tiscali.com (mk-outboundfilter-6.mail.uk.tiscali.com [212.74.114.14]) by core3.amsl.com (Postfix) with ESMTP id 43CF73A680E for <opsawg@ietf.org>; Fri, 13 Mar 2009 07:37:18 -0700 (PDT)
X-Trace: 84087091/mk-outboundfilter-6.mail.uk.tiscali.com/PIPEX/$PIPEX-ACCEPTED/pipex-customers/62.188.19.208/None/cfinss@dial.pipex.com
X-SBRS: None
X-RemoteIP: 62.188.19.208
X-IP-MAIL-FROM: cfinss@dial.pipex.com
X-MUA: Microsoft Outlook Express 6.00.2800.1106Produced By Microsoft MimeOLE V6.00.2800.1106
X-IP-BHB: Once
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjYFAGsMukk+vBPQ/2dsb2JhbACDJEOKDbNsCY4/AQaCOwuBMQY
X-IronPort-AV: E=Sophos;i="4.38,357,1233532800"; d="scan'208";a="84087091"
X-IP-Direction: IN
Received: from 1cust208.tnt2.lnd3.gbr.da.uu.net (HELO allison) ([62.188.19.208]) by smtp.pipex.tiscali.co.uk with SMTP; 13 Mar 2009 14:37:54 +0000
Message-ID: <013401c9a3e0$ac3c3b00$0601a8c0@allison>
From: "tom.petch" <cfinss@dial.pipex.com>
To: "Juergen Schoenwaelder" <j.schoenwaelder@jacobs-university.de>
References: <20090125164013.802B5129CDC6@newdev.eecs.harvard.edu> <20090127083743.GB12355@elstar.local> <1b2701c99ea3$2e4dd380$0600a8c0@china.huawei.com> <EDC652A26FB23C4EB6384A4584434A040149467C@307622ANEX5.global.avaya.com> <20090309082731.GB5676@elstar.local> <EDC652A26FB23C4EB6384A4584434A0401494781@307622ANEX5.global.avaya.com> <20090309111307.GD6444@elstar.local> <04c301c9a0d2$5a110150$0600a8c0@china.huawei.com> <001c01c9a33b$ad042de0$0601a8c0@allison> <20090312220658.GD4327@elstar.local>
Date: Fri, 13 Mar 2009 11:19:52 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Cc: opsawg@ietf.org
Subject: Re: [OPSAWG] (final)WGLCondraft-ietf-opsawg-operations-and-management
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: "tom.petch" <cfinss@dial.pipex.com>
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Mar 2009 14:37:25 -0000

---- Original Message -----
From: "Juergen Schoenwaelder" <j.schoenwaelder@jacobs-university.de>
To: "tom.petch" <cfinss@dial.pipex.com>
Cc: <opsawg@ietf.org>
Sent: Thursday, March 12, 2009 11:06 PM
Subject: Re: [OPSAWG](final)WGLCondraft-ietf-opsawg-operations-and-management


> On Thu, Mar 12, 2009 at 04:49:47PM +0100, tom.petch wrote:
>
> > Operations, often referred to as OAM, which may stand for
> > Operations, Administration and Maintenance is functionality in the
> > data plane to verify its correct operation - ping, traceroute and
> > such like (as in draft-vigoureux-mpls-tp-oam-requirements ).  On
> > this basis, you can and probably should have some OAM built into
> > your control protocols <and> your management protocols (eg as OSPF
> > has, but SNMP has not)
>
> I do not understand the last sentence or the whole paragraph. It is
> not clear which OAM functions OSPF has and that are missing in SNMP,
> given your definition of OAM as "functionality in a X plane protocol
> to verify its correct operation".

OSPF, in the routing/signalling plane, has a keepalive mechanism built in, which
IMO is comparable to role of ping for IP.  And in its use of multicast for DR
and BDR and the acknowledgements from other routers thereto it cleverly ensures
that everyone knows what is still alive.

SNMP the protocol, in the management plane, has no such functionality.  When a
crisis blows up and a Notification must be sent, only then does the engine find
that the network went down some hours ago and nothing can get through.  The onus
is on the SNMP application, which I am not counting here as part of SNMP, to
ensure what it needs to ensure, eg by polling some harmless object in the system
group every so many seconds.

Different protocols, different approaches.

In-band OAM I see at its richest in the 'sub-IP' protocols, GMPLS for example.

Tom Petch

>
> /js
>
> --
> Juergen Schoenwaelder           Jacobs University Bremen gGmbH
> Phone: +49 421 200 3587         Campus Ring 1, 28759 Bremen, Germany
> Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>


From RNATALE@mitre.org  Fri Mar 13 08:38:48 2009
Return-Path: <RNATALE@mitre.org>
X-Original-To: opsawg@core3.amsl.com
Delivered-To: opsawg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 857C53A687E for <opsawg@core3.amsl.com>; Fri, 13 Mar 2009 08:38:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.999
X-Spam-Level: 
X-Spam-Status: No, score=-5.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_35=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JU9958kH4UR2 for <opsawg@core3.amsl.com>; Fri, 13 Mar 2009 08:38:41 -0700 (PDT)
Received: from smtp-bedford.mitre.org (smtp-bedford.mitre.org [129.83.20.191]) by core3.amsl.com (Postfix) with ESMTP id E94A53A6A22 for <opsawg@ietf.org>; Fri, 13 Mar 2009 08:38:39 -0700 (PDT)
Received: from smtp-bedford.mitre.org (localhost.localdomain [127.0.0.1]) by smtp-bedford.mitre.org (8.13.1/8.13.1) with ESMTP id n2DFdHhd025179 for <opsawg@ietf.org>; Fri, 13 Mar 2009 11:39:17 -0400
Received: from imchub2.MITRE.ORG (imchub2.mitre.org [129.83.29.74]) by smtp-bedford.mitre.org (8.13.1/8.13.1) with ESMTP id n2DFdGJu025152 for <opsawg@ietf.org>; Fri, 13 Mar 2009 11:39:16 -0400
Received: from IMCMBX2.MITRE.ORG ([129.83.29.205]) by imchub2.MITRE.ORG ([129.83.29.74]) with mapi; Fri, 13 Mar 2009 11:39:16 -0400
From: "Natale, Bob" <RNATALE@mitre.org>
To: "opsawg@ietf.org" <opsawg@ietf.org>
Date: Fri, 13 Mar 2009 11:39:15 -0400
Thread-Topic: In-band OAM
Thread-Index: Acmj6VMmCtxnpQGPR6eKa4/HUYvNTQAAb+Fw
Message-ID: <17969D855F28964C88D177D45B6CDF11020EB99819@IMCMBX2.MITRE.ORG>
References: <20090125164013.802B5129CDC6@newdev.eecs.harvard.edu> <20090127083743.GB12355@elstar.local> <1b2701c99ea3$2e4dd380$0600a8c0@china.huawei.com> <EDC652A26FB23C4EB6384A4584434A040149467C@307622ANEX5.global.avaya.com> <20090309082731.GB5676@elstar.local> <EDC652A26FB23C4EB6384A4584434A0401494781@307622ANEX5.global.avaya.com> <20090309111307.GD6444@elstar.local> <04c301c9a0d2$5a110150$0600a8c0@china.huawei.com> <001c01c9a33b$ad042de0$0601a8c0@allison> <20090312220658.GD4327@elstar.local> <013401c9a3e0$ac3c3b00$0601a8c0@allison>
In-Reply-To: <013401c9a3e0$ac3c3b00$0601a8c0@allison>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [OPSAWG] In-band OAM
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Mar 2009 15:38:48 -0000

Tom's note prompts me to ask whether the Ops Area might want to consider th=
e topic of OAM evolution and/or co-evolution with higher-order management p=
rotocols at some point in the future.  GMPLS and other CCAMP work would lik=
ely be central to such work.  At what point(s) and via what mechanisms do/s=
hould signaling/control plane protocols interact with management plane inte=
rfaces on the one hand and OAM in the data plane on the other?  How can the=
 benefits (e.g., timeliness) and costs (e.g., how much OAM do you want in d=
ata streams, what happens when the in-band path is not accessible, etc.) be=
 leveraged/offset by management plane protocols (and maybe we would need to=
 include management applications as well)...?

Or are these non-questions (already adequately addressed in industry (and I=
'm too out-of-touch to know it)) or nonsensical ones or just not in scope f=
or the Ops Area, etc.?

Cheers,
BobN

-----Original Message-----
From: opsawg-bounces@ietf.org [mailto:opsawg-bounces@ietf.org] On Behalf Of=
 tom.petch
Sent: Friday, March 13, 2009 6:20 AM
To: Juergen Schoenwaelder
Cc: opsawg@ietf.org
Subject: Re: [OPSAWG] (final)WGLCondraft-ietf-opsawg-operations-and-managem=
ent

---- Original Message -----
From: "Juergen Schoenwaelder" <j.schoenwaelder@jacobs-university.de>
To: "tom.petch" <cfinss@dial.pipex.com>
Cc: <opsawg@ietf.org>
Sent: Thursday, March 12, 2009 11:06 PM
Subject: Re: [OPSAWG](final)WGLCondraft-ietf-opsawg-operations-and-manageme=
nt


> On Thu, Mar 12, 2009 at 04:49:47PM +0100, tom.petch wrote:
>
> > Operations, often referred to as OAM, which may stand for
> > Operations, Administration and Maintenance is functionality in the
> > data plane to verify its correct operation - ping, traceroute and
> > such like (as in draft-vigoureux-mpls-tp-oam-requirements ).  On
> > this basis, you can and probably should have some OAM built into
> > your control protocols <and> your management protocols (eg as OSPF
> > has, but SNMP has not)
>
> I do not understand the last sentence or the whole paragraph. It is
> not clear which OAM functions OSPF has and that are missing in SNMP,
> given your definition of OAM as "functionality in a X plane protocol
> to verify its correct operation".

OSPF, in the routing/signalling plane, has a keepalive mechanism built in, =
which
IMO is comparable to role of ping for IP.  And in its use of multicast for =
DR
and BDR and the acknowledgements from other routers thereto it cleverly ens=
ures
that everyone knows what is still alive.

SNMP the protocol, in the management plane, has no such functionality.  Whe=
n a
crisis blows up and a Notification must be sent, only then does the engine =
find
that the network went down some hours ago and nothing can get through.  The=
 onus
is on the SNMP application, which I am not counting here as part of SNMP, t=
o
ensure what it needs to ensure, eg by polling some harmless object in the s=
ystem
group every so many seconds.

Different protocols, different approaches.

In-band OAM I see at its richest in the 'sub-IP' protocols, GMPLS for examp=
le.

Tom Petch

>
> /js
>
> --
> Juergen Schoenwaelder           Jacobs University Bremen gGmbH
> Phone: +49 421 200 3587         Campus Ring 1, 28759 Bremen, Germany
> Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>

_______________________________________________
OPSAWG mailing list
OPSAWG@ietf.org
https://www.ietf.org/mailman/listinfo/opsawg

From dromasca@avaya.com  Sun Mar 15 06:20:32 2009
Return-Path: <dromasca@avaya.com>
X-Original-To: opsawg@core3.amsl.com
Delivered-To: opsawg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C02913A6928 for <opsawg@core3.amsl.com>; Sun, 15 Mar 2009 06:20:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.232
X-Spam-Level: 
X-Spam-Status: No, score=-2.232 tagged_above=-999 required=5 tests=[AWL=-0.233, BAYES_00=-2.599, J_CHICKENPOX_35=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2qSj36Tvd7CJ for <opsawg@core3.amsl.com>; Sun, 15 Mar 2009 06:20:31 -0700 (PDT)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by core3.amsl.com (Postfix) with ESMTP id 04B423A6857 for <opsawg@ietf.org>; Sun, 15 Mar 2009 06:20:30 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.38,366,1233550800"; d="scan'208";a="140294122"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 15 Mar 2009 09:21:09 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.12]) by co300216-co-erhwest-out.avaya.com with ESMTP; 15 Mar 2009 09:21:08 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Sun, 15 Mar 2009 14:21:00 +0100
Message-ID: <EDC652A26FB23C4EB6384A4584434A04014D4C99@307622ANEX5.global.avaya.com>
In-Reply-To: <17969D855F28964C88D177D45B6CDF11020EB99819@IMCMBX2.MITRE.ORG>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [OPSAWG] In-band OAM
Thread-Index: Acmj6VMmCtxnpQGPR6eKa4/HUYvNTQAAb+FwAGFWyyA=
References: <20090125164013.802B5129CDC6@newdev.eecs.harvard.edu><20090127083743.GB12355@elstar.local><1b2701c99ea3$2e4dd380$0600a8c0@china.huawei.com><EDC652A26FB23C4EB6384A4584434A040149467C@307622ANEX5.global.avaya.com><20090309082731.GB5676@elstar.local><EDC652A26FB23C4EB6384A4584434A0401494781@307622ANEX5.global.avaya.com><20090309111307.GD6444@elstar.local><04c301c9a0d2$5a110150$0600a8c0@china.huawei.com><001c01c9a33b$ad042de0$0601a8c0@allison><20090312220658.GD4327@elstar.local><013401c9a3e0$ac3c3b00$0601a8c0@allison> <17969D855F28964C88D177D45B6CDF11020EB99819@IMCMBX2.MITRE.ORG>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Natale, Bob" <RNATALE@mitre.org>, <opsawg@ietf.org>
Subject: Re: [OPSAWG] In-band OAM
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 15 Mar 2009 13:20:32 -0000

Bob,

These are generic questions that can be debated extensively. Do you have
a concrete proposal for IETF work that is missing and that should /
could be done in the OPS Area? The OPS Area is us, so ....

Regards,

Dan
=20

> -----Original Message-----
> From: opsawg-bounces@ietf.org=20
> [mailto:opsawg-bounces@ietf.org] On Behalf Of Natale, Bob
> Sent: Friday, March 13, 2009 5:39 PM
> To: opsawg@ietf.org
> Subject: [OPSAWG] In-band OAM
>=20
> Tom's note prompts me to ask whether the Ops Area might want=20
> to consider the topic of OAM evolution and/or co-evolution=20
> with higher-order management protocols at some point in the=20
> future.  GMPLS and other CCAMP work would likely be central=20
> to such work.  At what point(s) and via what mechanisms=20
> do/should signaling/control plane protocols interact with=20
> management plane interfaces on the one hand and OAM in the=20
> data plane on the other?  How can the benefits (e.g.,=20
> timeliness) and costs (e.g., how much OAM do you want in data=20
> streams, what happens when the in-band path is not=20
> accessible, etc.) be leveraged/offset by management plane=20
> protocols (and maybe we would need to include management=20
> applications as well)...?
>=20
> Or are these non-questions (already adequately addressed in=20
> industry (and I'm too out-of-touch to know it)) or=20
> nonsensical ones or just not in scope for the Ops Area, etc.?
>=20
> Cheers,
> BobN
>=20
> -----Original Message-----
> From: opsawg-bounces@ietf.org=20
> [mailto:opsawg-bounces@ietf.org] On Behalf Of tom.petch
> Sent: Friday, March 13, 2009 6:20 AM
> To: Juergen Schoenwaelder
> Cc: opsawg@ietf.org
> Subject: Re: [OPSAWG]=20
> (final)WGLCondraft-ietf-opsawg-operations-and-management
>=20
> ---- Original Message -----
> From: "Juergen Schoenwaelder" <j.schoenwaelder@jacobs-university.de>
> To: "tom.petch" <cfinss@dial.pipex.com>
> Cc: <opsawg@ietf.org>
> Sent: Thursday, March 12, 2009 11:06 PM
> Subject: Re:=20
> [OPSAWG](final)WGLCondraft-ietf-opsawg-operations-and-management
>=20
>=20
> > On Thu, Mar 12, 2009 at 04:49:47PM +0100, tom.petch wrote:
> >
> > > Operations, often referred to as OAM, which may stand for=20
> > > Operations, Administration and Maintenance is=20
> functionality in the=20
> > > data plane to verify its correct operation - ping, traceroute and=20
> > > such like (as in draft-vigoureux-mpls-tp-oam-requirements ).  On=20
> > > this basis, you can and probably should have some OAM built into=20
> > > your control protocols <and> your management protocols=20
> (eg as OSPF=20
> > > has, but SNMP has not)
> >
> > I do not understand the last sentence or the whole paragraph. It is=20
> > not clear which OAM functions OSPF has and that are missing=20
> in SNMP,=20
> > given your definition of OAM as "functionality in a X plane=20
> protocol=20
> > to verify its correct operation".
>=20
> OSPF, in the routing/signalling plane, has a keepalive=20
> mechanism built in, which IMO is comparable to role of ping=20
> for IP.  And in its use of multicast for DR and BDR and the=20
> acknowledgements from other routers thereto it cleverly=20
> ensures that everyone knows what is still alive.
>=20
> SNMP the protocol, in the management plane, has no such=20
> functionality.  When a crisis blows up and a Notification=20
> must be sent, only then does the engine find that the network=20
> went down some hours ago and nothing can get through.  The=20
> onus is on the SNMP application, which I am not counting here=20
> as part of SNMP, to ensure what it needs to ensure, eg by=20
> polling some harmless object in the system group every so=20
> many seconds.
>=20
> Different protocols, different approaches.
>=20
> In-band OAM I see at its richest in the 'sub-IP' protocols,=20
> GMPLS for example.
>=20
> Tom Petch
>=20
> >
> > /js
> >
> > --
> > Juergen Schoenwaelder           Jacobs University Bremen gGmbH
> > Phone: +49 421 200 3587         Campus Ring 1, 28759 Bremen, Germany
> > Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>
>=20
> _______________________________________________
> OPSAWG mailing list
> OPSAWG@ietf.org
> https://www.ietf.org/mailman/listinfo/opsawg
> _______________________________________________
> OPSAWG mailing list
> OPSAWG@ietf.org
> https://www.ietf.org/mailman/listinfo/opsawg
>=20

From cfinss@dial.pipex.com  Tue Mar 17 03:36:03 2009
Return-Path: <cfinss@dial.pipex.com>
X-Original-To: opsawg@core3.amsl.com
Delivered-To: opsawg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 50B1C3A68C0 for <opsawg@core3.amsl.com>; Tue, 17 Mar 2009 03:36:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.813
X-Spam-Level: 
X-Spam-Status: No, score=-1.813 tagged_above=-999 required=5 tests=[AWL=0.186,  BAYES_00=-2.599, J_CHICKENPOX_35=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id B11R3nRER+eY for <opsawg@core3.amsl.com>; Tue, 17 Mar 2009 03:36:02 -0700 (PDT)
Received: from mk-outboundfilter-2.mail.uk.tiscali.com (mk-outboundfilter-2.mail.uk.tiscali.com [212.74.114.38]) by core3.amsl.com (Postfix) with ESMTP id E57CA3A684C for <opsawg@ietf.org>; Tue, 17 Mar 2009 03:36:01 -0700 (PDT)
X-Trace: 194966435/mk-outboundfilter-2.mail.uk.tiscali.com/PIPEX/$PIPEX-ACCEPTED/pipex-customers/62.188.17.184/None/cfinss@dial.pipex.com
X-SBRS: None
X-RemoteIP: 62.188.17.184
X-IP-MAIL-FROM: cfinss@dial.pipex.com
X-MUA: Microsoft Outlook Express 6.00.2800.1106Produced By Microsoft MimeOLE V6.00.2800.1106
X-IP-BHB: Once
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApwEAO8Zv0k+vBG4/2dsb2JhbACDJYpYuA8JjwYBBoI5C4EzBg
X-IronPort-AV: E=Sophos;i="4.38,377,1233532800"; d="scan'208";a="194966435"
X-IP-Direction: IN
Received: from 1cust184.tnt1.lnd3.gbr.da.uu.net (HELO allison) ([62.188.17.184]) by smtp.pipex.tiscali.co.uk with SMTP; 17 Mar 2009 10:36:40 +0000
Message-ID: <007201c9a6e3$9fc8e520$0601a8c0@allison>
From: "tom.petch" <cfinss@dial.pipex.com>
To: "Natale, Bob" <RNATALE@mitre.org>, <opsawg@ietf.org>
References: <20090125164013.802B5129CDC6@newdev.eecs.harvard.edu><20090127083743.GB12355@elstar.local><1b2701c99ea3$2e4dd380$0600a8c0@china.huawei.com><EDC652A26FB23C4EB6384A4584434A040149467C@307622ANEX5.global.avaya.com><20090309082731.GB5676@elstar.local><EDC652A26FB23C4EB6384A4584434A0401494781@307622ANEX5.global.avaya.com><20090309111307.GD6444@elstar.local><04c301c9a0d2$5a110150$0600a8c0@china.huawei.com><001c01c9a33b$ad042de0$0601a8c0@allison><20090312220658.GD4327@elstar.local><013401c9a3e0$ac3c3b00$0601a8c0@allison> <17969D855F28964C88D177D45B6CDF11020EB99819@IMCMBX2.MITRE.ORG>
Date: Tue, 17 Mar 2009 09:19:10 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Subject: Re: [OPSAWG] In-band OAM
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: "tom.petch" <cfinss@dial.pipex.com>
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Mar 2009 10:36:03 -0000

----- Original Message -----
From: "Natale, Bob" <RNATALE@mitre.org>
To: <opsawg@ietf.org>
Sent: Friday, March 13, 2009 4:39 PM
Subject: [OPSAWG] In-band OAM


> Tom's note prompts me to ask whether the Ops Area might want to consider the
topic of OAM evolution and/or co-evolution with higher-order management
protocols at some point in the future.  GMPLS and other CCAMP work would likely
be central to such work.  At what point(s) and via what mechanisms do/should
signaling/control plane protocols interact with management plane interfaces on
the one hand and OAM in the data plane on the other?  How can the benefits
(e.g., timeliness) and costs (e.g., how much OAM do you want in data streams,
what happens when the in-band path is not accessible, etc.) be leveraged/offset
by management plane protocols (and maybe we would need to include management
applications as well)...?
>

Currently this is a hot topic, taking up a lot of bandwidth, on the mpls-tp
list, which is at the stage of specifying - separately - the overall
requirements and those for management, OAM etc.

Tom Petch

> Or are these non-questions (already adequately addressed in industry (and I'm
too out-of-touch to know it)) or nonsensical ones or just not in scope for the
Ops Area, etc.?
>
> Cheers,
> BobN
>
> -----Original Message-----
> From: opsawg-bounces@ietf.org [mailto:opsawg-bounces@ietf.org] On Behalf Of
tom.petch
> Sent: Friday, March 13, 2009 6:20 AM
> To: Juergen Schoenwaelder
> Cc: opsawg@ietf.org
> Subject: Re: [OPSAWG] (final)WGLCondraft-ietf-opsawg-operations-and-management
>
> ---- Original Message -----
> From: "Juergen Schoenwaelder" <j.schoenwaelder@jacobs-university.de>
> To: "tom.petch" <cfinss@dial.pipex.com>
> Cc: <opsawg@ietf.org>
> Sent: Thursday, March 12, 2009 11:06 PM
> Subject: Re: [OPSAWG](final)WGLCondraft-ietf-opsawg-operations-and-management
>
>
> > On Thu, Mar 12, 2009 at 04:49:47PM +0100, tom.petch wrote:
> >
> > > Operations, often referred to as OAM, which may stand for
> > > Operations, Administration and Maintenance is functionality in the
> > > data plane to verify its correct operation - ping, traceroute and
> > > such like (as in draft-vigoureux-mpls-tp-oam-requirements ).  On
> > > this basis, you can and probably should have some OAM built into
> > > your control protocols <and> your management protocols (eg as OSPF
> > > has, but SNMP has not)
> >
> > I do not understand the last sentence or the whole paragraph. It is
> > not clear which OAM functions OSPF has and that are missing in SNMP,
> > given your definition of OAM as "functionality in a X plane protocol
> > to verify its correct operation".
>
> OSPF, in the routing/signalling plane, has a keepalive mechanism built in,
which
> IMO is comparable to role of ping for IP.  And in its use of multicast for DR
> and BDR and the acknowledgements from other routers thereto it cleverly
ensures
> that everyone knows what is still alive.
>
> SNMP the protocol, in the management plane, has no such functionality.  When a
> crisis blows up and a Notification must be sent, only then does the engine
find
> that the network went down some hours ago and nothing can get through.  The
onus
> is on the SNMP application, which I am not counting here as part of SNMP, to
> ensure what it needs to ensure, eg by polling some harmless object in the
system
> group every so many seconds.
>
> Different protocols, different approaches.
>
> In-band OAM I see at its richest in the 'sub-IP' protocols, GMPLS for example.
>
> Tom Petch
>
> >
> > /js
> >
> > --
> > Juergen Schoenwaelder           Jacobs University Bremen gGmbH
> > Phone: +49 421 200 3587         Campus Ring 1, 28759 Bremen, Germany
> > Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>
>
> _______________________________________________
> OPSAWG mailing list
> OPSAWG@ietf.org
> https://www.ietf.org/mailman/listinfo/opsawg
> _______________________________________________
> OPSAWG mailing list
> OPSAWG@ietf.org
> https://www.ietf.org/mailman/listinfo/opsawg


From phil@juniper.net  Tue Mar 17 07:55:50 2009
Return-Path: <phil@juniper.net>
X-Original-To: opsawg@core3.amsl.com
Delivered-To: opsawg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E206928C17E for <opsawg@core3.amsl.com>; Tue, 17 Mar 2009 07:55:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mw5uvbidIEU8 for <opsawg@core3.amsl.com>; Tue, 17 Mar 2009 07:55:50 -0700 (PDT)
Received: from exprod7og107.obsmtp.com (exprod7og107.obsmtp.com [64.18.2.167]) by core3.amsl.com (Postfix) with ESMTP id B983428C163 for <opsawg@ietf.org>; Tue, 17 Mar 2009 07:55:47 -0700 (PDT)
Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob107.postini.com ([64.18.6.12]) with SMTP ID DSNKSb+6HkOu9lOZK6DIlVi4m//y3SE+pTiC@postini.com; Tue, 17 Mar 2009 07:56:33 PDT
Received: from p-emfe01-sac.jnpr.net (66.129.254.72) by P-EMHUB01-HQ.jnpr.net (172.24.192.35) with Microsoft SMTP Server id 8.1.340.0; Tue, 17 Mar 2009 07:52:59 -0700
Received: from p-emlb01-sac.jnpr.net ([66.129.254.46]) by p-emfe01-sac.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Tue, 17 Mar 2009 07:52:59 -0700
Received: from emailsmtp56.jnpr.net ([172.24.60.77]) by p-emlb01-sac.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Tue, 17 Mar 2009 07:52:59 -0700
Received: from magenta.juniper.net ([172.17.27.123]) by emailsmtp56.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Tue, 17 Mar 2009 07:52:58 -0700
Received: from idle.juniper.net (idleski.juniper.net [172.25.4.26])	by magenta.juniper.net (8.11.3/8.11.3) with ESMTP id n2HEqvM60591; Tue, 17 Mar 2009 07:52:58 -0700 (PDT)	(envelope-from phil@juniper.net)
Received: from idle.juniper.net (localhost [127.0.0.1])	by idle.juniper.net (8.13.8/8.13.8) with ESMTP id n2HEk2bF077322; Tue, 17 Mar 2009 14:46:02 GMT (envelope-from phil@idle.juniper.net)
Message-ID: <200903171446.n2HEk2bF077322@idle.juniper.net>
To: "tom.petch" <cfinss@dial.pipex.com>
In-Reply-To: <007201c9a6e3$9fc8e520$0601a8c0@allison> 
Date: Tue, 17 Mar 2009 10:46:01 -0400
From: Phil Shafer <phil@juniper.net>
X-OriginalArrivalTime: 17 Mar 2009 14:52:58.0417 (UTC) FILETIME=[0FDC2210:01C9A710]
MIME-Version: 1.0
Content-Type: text/plain
Cc: "Natale, Bob" <RNATALE@mitre.org>, opsawg@ietf.org
Subject: Re: [OPSAWG] In-band OAM
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Mar 2009 14:55:51 -0000

"tom.petch" writes:
>Currently this is a hot topic, taking up a lot of bandwidth, on the mpls-tp
>list, which is at the stage of specifying - separately - the overall
>requirements and those for management, OAM etc.

Would it be good to have these folks read
draft-ietf-opsawg-operations-and-management and see if it helps
them see what needs addressed?  Seems like a great place to get
feedback.

Thanks,
 Phil

From RNATALE@mitre.org  Tue Mar 17 08:32:03 2009
Return-Path: <RNATALE@mitre.org>
X-Original-To: opsawg@core3.amsl.com
Delivered-To: opsawg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2147F3A68E5 for <opsawg@core3.amsl.com>; Tue, 17 Mar 2009 08:32:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.999
X-Spam-Level: 
X-Spam-Status: No, score=-5.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_35=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YXL3oJm34j4p for <opsawg@core3.amsl.com>; Tue, 17 Mar 2009 08:32:02 -0700 (PDT)
Received: from smtp-bedford.mitre.org (smtp-bedford.mitre.org [129.83.20.191]) by core3.amsl.com (Postfix) with ESMTP id 322463A67AF for <opsawg@ietf.org>; Tue, 17 Mar 2009 08:32:02 -0700 (PDT)
Received: from smtp-bedford.mitre.org (localhost.localdomain [127.0.0.1]) by smtp-bedford.mitre.org (8.13.1/8.13.1) with ESMTP id n2HFWh9P032428 for <opsawg@ietf.org>; Tue, 17 Mar 2009 11:32:44 -0400
Received: from imchub2.MITRE.ORG (imchub2.mitre.org [129.83.29.74]) by smtp-bedford.mitre.org (8.13.1/8.13.1) with ESMTP id n2HFWhZM032414;  Tue, 17 Mar 2009 11:32:43 -0400
Received: from IMCMBX2.MITRE.ORG ([129.83.29.205]) by imchub2.MITRE.ORG ([129.83.29.74]) with mapi; Tue, 17 Mar 2009 11:32:43 -0400
From: "Natale, Bob" <RNATALE@mitre.org>
To: Phil Shafer <phil@juniper.net>, "tom.petch" <cfinss@dial.pipex.com>, "Romascanu, Dan (Dan)" <dromasca@avaya.com>
Date: Tue, 17 Mar 2009 11:32:41 -0400
Thread-Topic: [OPSAWG] In-band OAM 
Thread-Index: AcmnEJDTDKzbZQZTTSysyGagKvkW4wAAMSoQ
Message-ID: <17969D855F28964C88D177D45B6CDF11020EB9A258@IMCMBX2.MITRE.ORG>
References: <007201c9a6e3$9fc8e520$0601a8c0@allison> <200903171446.n2HEk2bF077322@idle.juniper.net>
In-Reply-To: <200903171446.n2HEk2bF077322@idle.juniper.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "opsawg@ietf.org" <opsawg@ietf.org>
Subject: Re: [OPSAWG] In-band OAM
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Mar 2009 15:32:03 -0000

Yes, Phil's suggestion would be very helpful.

To answer Dan's response to my original posting: No, I don't have a formal =
proposal -- I asked some questions because I really don't know what course =
of action should be taken.

I am aware of long-term development projects that need to be able to manage=
 the emerging control plane behaviors via management plane applications (so=
metimes via or in coordination with signaling plane mechanisms).  I would l=
ike to be able to address those needs via IETF standard mechanisms, where p=
ossible, to the extent appropriate.

I personally would like to see the OpsArea play a more active/leading role =
-- it seems like the signaling/control plane work is out-pacing management =
plane developments -- but I am not up-to-date on or actively engaged in the=
 distribution of work across the IESG Areas (and probably unable to contrib=
ute anything helpful in that respect in any case).

Cheers,
BobN

-----Original Message-----
From: Phil Shafer [mailto:phil@juniper.net]=20
Sent: Tuesday, March 17, 2009 10:46 AM
To: tom.petch
Cc: Natale, Bob; opsawg@ietf.org
Subject: Re: [OPSAWG] In-band OAM=20

"tom.petch" writes:
>Currently this is a hot topic, taking up a lot of bandwidth, on the mpls-t=
p
>list, which is at the stage of specifying - separately - the overall
>requirements and those for management, OAM etc.

Would it be good to have these folks read
draft-ietf-opsawg-operations-and-management and see if it helps
them see what needs addressed?  Seems like a great place to get
feedback.

Thanks,
 Phil

From cfinss@dial.pipex.com  Wed Mar 18 03:12:28 2009
Return-Path: <cfinss@dial.pipex.com>
X-Original-To: opsawg@core3.amsl.com
Delivered-To: opsawg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 78CD53A6996 for <opsawg@core3.amsl.com>; Wed, 18 Mar 2009 03:12:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.918
X-Spam-Level: 
X-Spam-Status: No, score=-0.918 tagged_above=-999 required=5 tests=[AWL=-0.733, BAYES_40=-0.185]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tvkgd4Hqo911 for <opsawg@core3.amsl.com>; Wed, 18 Mar 2009 03:12:27 -0700 (PDT)
Received: from mk-outboundfilter-2.mail.uk.tiscali.com (mk-outboundfilter-2.mail.uk.tiscali.com [212.74.114.38]) by core3.amsl.com (Postfix) with ESMTP id 56EB53A684D for <opsawg@ietf.org>; Wed, 18 Mar 2009 03:12:27 -0700 (PDT)
X-Trace: 195299910/mk-outboundfilter-2.mail.uk.tiscali.com/PIPEX/$PIPEX-ACCEPTED/pipex-customers/62.188.19.238/None/cfinss@dial.pipex.com
X-SBRS: None
X-RemoteIP: 62.188.19.238
X-IP-MAIL-FROM: cfinss@dial.pipex.com
X-MUA: Microsoft Outlook Express 6.00.2800.1106Produced By Microsoft MimeOLE V6.00.2800.1106
X-IP-BHB: Once
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgoFAJJlwEk+vBPu/2dsb2JhbACDJTETihjFOQeDdQY
X-IronPort-AV: E=Sophos;i="4.38,383,1233532800"; d="scan'208";a="195299910"
X-IP-Direction: IN
Received: from 1cust238.tnt2.lnd3.gbr.da.uu.net (HELO allison) ([62.188.19.238]) by smtp.pipex.tiscali.co.uk with SMTP; 18 Mar 2009 10:13:08 +0000
Message-ID: <000d01c9a7a9$7f529540$0601a8c0@allison>
From: "tom.petch" <cfinss@dial.pipex.com>
To: "Phil Shafer" <phil@juniper.net>
References: <200903171446.n2HEk2bF077322@idle.juniper.net>
Date: Wed, 18 Mar 2009 10:09:25 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Cc: "Natale, Bob" <RNATALE@mitre.org>, opsawg@ietf.org
Subject: Re: [OPSAWG] In-band OAM
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: "tom.petch" <cfinss@dial.pipex.com>
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Mar 2009 10:12:28 -0000

----- Original Message -----
From: "Phil Shafer" <phil@juniper.net>
To: "tom.petch" <cfinss@dial.pipex.com> <opsawg@ietf.org>
Sent: Tuesday, March 17, 2009 3:46 PM

> "tom.petch" writes:
> >Currently this is a hot topic, taking up a lot of bandwidth, on the mpls-tp
> >list, which is at the stage of specifying - separately - the overall
> >requirements and those for management, OAM etc.
>
> Would it be good to have these folks read
> draft-ietf-opsawg-operations-and-management and see if it helps
> them see what needs addressed?  Seems like a great place to get
> feedback.

In a sense, we have already done this.  Adrian Farrel, who has been very active
in the nexus of WGs - mpls, gmpls, mpls-tp, pce, pwe3 - where OAM is prevalent,
and especially active w.r.t operations, security, management etc commented on
this I-D last month.

And my comments, which dbh thought appropriate to a different I-D, were driven
by what I see, in mpls-tp in particular.  I think it would have been helpful to
have had something earlier to point to as what the IETF thinks, as an
alternative to the ideas originating in ITU-T Recommendations.

Tom Petch

> Thanks,
>  Phil


From ietfdbh@comcast.net  Wed Mar 18 07:59:32 2009
Return-Path: <ietfdbh@comcast.net>
X-Original-To: opsawg@core3.amsl.com
Delivered-To: opsawg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C75983A692E for <opsawg@core3.amsl.com>; Wed, 18 Mar 2009 07:59:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.202
X-Spam-Level: 
X-Spam-Status: No, score=-2.202 tagged_above=-999 required=5 tests=[AWL=-0.203, BAYES_00=-2.599, J_CHICKENPOX_35=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XtO80EZDpxUS for <opsawg@core3.amsl.com>; Wed, 18 Mar 2009 07:59:31 -0700 (PDT)
Received: from QMTA06.westchester.pa.mail.comcast.net (qmta06.westchester.pa.mail.comcast.net [76.96.62.56]) by core3.amsl.com (Postfix) with ESMTP id 838D83A691B for <opsawg@ietf.org>; Wed, 18 Mar 2009 07:59:31 -0700 (PDT)
Received: from OMTA06.westchester.pa.mail.comcast.net ([76.96.62.51]) by QMTA06.westchester.pa.mail.comcast.net with comcast id UczN1b00716LCl056f0Dwl; Wed, 18 Mar 2009 15:00:13 +0000
Received: from Harrington73653 ([24.147.240.21]) by OMTA06.westchester.pa.mail.comcast.net with comcast id Uf0E1b00Z0UQ6dC3Sf0FA0; Wed, 18 Mar 2009 15:00:15 +0000
From: "David Harrington" <ietfdbh@comcast.net>
To: "'tom.petch'" <cfinss@dial.pipex.com>, "'Phil Shafer'" <phil@juniper.net>
References: <200903171446.n2HEk2bF077322@idle.juniper.net> <000d01c9a7a9$7f529540$0601a8c0@allison>
Date: Wed, 18 Mar 2009 11:00:13 -0400
Message-ID: <023601c9a7da$3e16a3b0$0600a8c0@china.huawei.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
In-reply-to: <000d01c9a7a9$7f529540$0601a8c0@allison>
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
Thread-index: AcmnsifE4rPjWhEVR52x1HWciF3i2QAIN8Wg
Cc: "'Natale, Bob'" <RNATALE@mitre.org>, opsawg@ietf.org
Subject: Re: [OPSAWG] In-band OAM
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Mar 2009 14:59:32 -0000

Hi,

I don't want to get into a debate about what OAM means. As Ron and Dan
pointed out in Dublin or Minneapolis, the meaning of OAM differs
across standards development organizations. This has become more
obvious as the IETF has dropped the "write a MIB" approach, MPLS and
related virtual wires WGs started defining requirements for "OAM", and
the IETF started working with ITU-T to reach consensus about MPLS-TP
OAM standards. The result is that people involved in that work,
including IAB members, are planning to author a document to discuss
what OAM means, to describe the different approaches, and I think to
identify which aspects were appropriate to IETF work. I think this is
the document Tom wants to see. I absolutely agree that would be a
useful document to help define what the new "IETF Management
Framework" or "IETF Operations and Management Framework" should be
going forward.

Most IETF network management protocols defined in the OPS area follow
the IETF Management Framework as originally defined in RFC1052, which
treated Internet management as a collection of standardized data
objects (THE MIB), accessed using protocols that were separate from
the protocols being managed (expected to be SNMP for the short-term,
migrating to CMIP for the long term). OAM in other SDOs often build
management into the protocols to be managed. That is a very different
approach than the IETF Standard Management Framework in use since
RFC1052.

The guidelines document is really a guide to writing an "Operations
and Management" section in IETF documents, as an alternative to
continuing the simplistic "write a MIB" approach. Part of the goal is
to "standardize" what should be considered, as other BCPs have
standardized the Security Considerations section and the IANA
Consideration section. Part of the goal is to "standardize" what
should be considered in an expert review to prevent surprises late in
the approval process, much as RFC4181 does. MIB Doctor reviews used to
vary a lot depending on which Doctor did the review; RFC4181 now tells
authors what to expect from reviews, to a degree constrains Doctors
from raising pet peeves, and makes it easier to gain agreement between
authors and reviewers so expert reviews go easier and faster. This
guidelines document should do the same, allowing for different
protocols and data models best suited to the needs of operations and
management of the targeted protocol.

My interpretation of the consensus of the WG is that we should NOT get
involved in the debate about different meanings of OAM; we should
focus on guidelines that follow the existing conceptual IETF
Management Framework, but expand the options to include different
protocols, such as Netconf and syslog and CLI, and different data
modeling languages, such as XML Schema and Netmod and English-language
information models. If the IETF reaches consensus on a new IETF
Management Framework, then this guidelines BCP can be updated.

If it would make people feel more comfortable, we can change the title
to "Guidelines to Authors and Reviewers for Considerations of
Management and Operations of New Protocols and Protocol Extensions" -
although I think there might be a limit to how long a title can be,
and this might exceed the limit. 

dbh

> -----Original Message-----
> From: opsawg-bounces@ietf.org 
> [mailto:opsawg-bounces@ietf.org] On Behalf Of tom.petch
> Sent: Wednesday, March 18, 2009 5:09 AM
> To: Phil Shafer
> Cc: Natale, Bob; opsawg@ietf.org
> Subject: Re: [OPSAWG] In-band OAM
> 
> ----- Original Message -----
> From: "Phil Shafer" <phil@juniper.net>
> To: "tom.petch" <cfinss@dial.pipex.com> <opsawg@ietf.org>
> Sent: Tuesday, March 17, 2009 3:46 PM
> 
> > "tom.petch" writes:
> > >Currently this is a hot topic, taking up a lot of 
> bandwidth, on the mpls-tp
> > >list, which is at the stage of specifying - separately - 
> the overall
> > >requirements and those for management, OAM etc.
> >
> > Would it be good to have these folks read
> > draft-ietf-opsawg-operations-and-management and see if it helps
> > them see what needs addressed?  Seems like a great place to get
> > feedback.
> 
> In a sense, we have already done this.  Adrian Farrel, who 
> has been very active
> in the nexus of WGs - mpls, gmpls, mpls-tp, pce, pwe3 - where 
> OAM is prevalent,
> and especially active w.r.t operations, security, management 
> etc commented on
> this I-D last month.
> 
> And my comments, which dbh thought appropriate to a different 
> I-D, were driven
> by what I see, in mpls-tp in particular.  I think it would 
> have been helpful to
> have had something earlier to point to as what the IETF thinks, as
an
> alternative to the ideas originating in ITU-T Recommendations.
> 
> Tom Petch
> 
> > Thanks,
> >  Phil
> 
> _______________________________________________
> OPSAWG mailing list
> OPSAWG@ietf.org
> https://www.ietf.org/mailman/listinfo/opsawg
> 


From RNATALE@mitre.org  Wed Mar 18 10:59:43 2009
Return-Path: <RNATALE@mitre.org>
X-Original-To: opsawg@core3.amsl.com
Delivered-To: opsawg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 405823A6B7D for <opsawg@core3.amsl.com>; Wed, 18 Mar 2009 10:59:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.299
X-Spam-Level: 
X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5 tests=[AWL=0.300,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id G6pAvDO4gExb for <opsawg@core3.amsl.com>; Wed, 18 Mar 2009 10:59:41 -0700 (PDT)
Received: from smtp-bedford.mitre.org (smtp-bedford.mitre.org [129.83.20.191]) by core3.amsl.com (Postfix) with ESMTP id 653613A6B48 for <opsawg@ietf.org>; Wed, 18 Mar 2009 10:59:40 -0700 (PDT)
Received: from smtp-bedford.mitre.org (localhost.localdomain [127.0.0.1]) by smtp-bedford.mitre.org (8.13.1/8.13.1) with ESMTP id n2II0NJn024653 for <opsawg@ietf.org>; Wed, 18 Mar 2009 14:00:23 -0400
Received: from imchub2.MITRE.ORG (imchub2.mitre.org [129.83.29.74]) by smtp-bedford.mitre.org (8.13.1/8.13.1) with ESMTP id n2II0NrL024628 for <opsawg@ietf.org>; Wed, 18 Mar 2009 14:00:23 -0400
Received: from IMCMBX2.MITRE.ORG ([129.83.29.205]) by imchub2.MITRE.ORG ([129.83.29.74]) with mapi; Wed, 18 Mar 2009 14:00:23 -0400
From: "Natale, Bob" <RNATALE@mitre.org>
To: "opsawg@ietf.org" <opsawg@ietf.org>
Date: Wed, 18 Mar 2009 14:00:22 -0400
Thread-Topic: Post-WGLC edits: draft-ietf-opsawg-smi-datatypes-in-xsd-05
Thread-Index: Acmibzob79xAbx2aQE6MsMh3qwNd4gAADy0gAWCgEEAAACxawA==
Message-ID: <17969D855F28964C88D177D45B6CDF110210414097@IMCMBX2.MITRE.ORG>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/mixed; boundary="_002_17969D855F28964C88D177D45B6CDF110210414097IMCMBX2MITREO_"
MIME-Version: 1.0
Subject: [OPSAWG] Post-WGLC edits: draft-ietf-opsawg-smi-datatypes-in-xsd-05
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Mar 2009 17:59:43 -0000

--_002_17969D855F28964C88D177D45B6CDF110210414097IMCMBX2MITREO_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi,

Attached revision (-05) is the result of applying all WGLC edits, minor add=
itional fix-ups, and new IPR boilerplate.

Unable to post via I-D submission tool until next week due to cut-off perio=
d.

(I actually had this ready prior to the cut-off date, but got blocked at th=
at point due to the new IPR requirements.  While in the end it now seems fa=
irly simple, getting it right for xml2rfc and IDnits took a big chunk of ti=
me.)

I'll post it via the I-D submission tool as soon as possible after it reope=
ns next week.

Cheers,
BobN


--_002_17969D855F28964C88D177D45B6CDF110210414097IMCMBX2MITREO_
Content-Type: text/plain;
	name="draft-ietf-opsawg-smi-datatypes-in-xsd-05.txt"
Content-Description: draft-ietf-opsawg-smi-datatypes-in-xsd-05.txt
Content-Disposition: attachment;
	filename="draft-ietf-opsawg-smi-datatypes-in-xsd-05.txt"; size=26425;
	creation-date="Wed, 18 Mar 2009 02:29:03 GMT";
	modification-date="Wed, 18 Mar 2009 13:43:03 GMT"
Content-Transfer-Encoding: base64

CgoKTmV0d29yayBXb3JraW5nIEdyb3VwICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgQi4gTmF0YWxlCkludGVybmV0LURyYWZ0ICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICBNSVRSRQpJbnRlbmRlZCBzdGF0dXM6IFN0YW5k
YXJkcyBUcmFjayAgICAgICAgICAgICAgICAgICAgICAgICAgTWFyY2ggMTgsIDIwMDkKRXhwaXJl
czogU2VwdGVtYmVyIDE5LCAyMDA5CgoKICAgIEV4cHJlc3NpbmcgU05NUCBTTUkgRGF0YXR5cGVz
IGluIFhNTCBTY2hlbWEgRGVmaW5pdGlvbiBMYW5ndWFnZQogICAgICAgICAgICAgZHJhZnQtaWV0
Zi1vcHNhd2ctc21pLWRhdGF0eXBlcy1pbi14c2QtMDUudHh0CgpTdGF0dXMgb2YgdGhpcyBNZW1v
CgogICBUaGlzIEludGVybmV0LURyYWZ0IGlzIHN1Ym1pdHRlZCB0byBJRVRGIGluIGZ1bGwgY29u
Zm9ybWFuY2Ugd2l0aCB0aGUKICAgcHJvdmlzaW9ucyBvZiBCQ1AgNzggYW5kIEJDUCA3OS4KCiAg
IEludGVybmV0LURyYWZ0cyBhcmUgd29ya2luZyBkb2N1bWVudHMgb2YgdGhlIEludGVybmV0IEVu
Z2luZWVyaW5nCiAgIFRhc2sgRm9yY2UgKElFVEYpLCBpdHMgYXJlYXMsIGFuZCBpdHMgd29ya2lu
ZyBncm91cHMuICBOb3RlIHRoYXQKICAgb3RoZXIgZ3JvdXBzIG1heSBhbHNvIGRpc3RyaWJ1dGUg
d29ya2luZyBkb2N1bWVudHMgYXMgSW50ZXJuZXQtCiAgIERyYWZ0cy4KCiAgIEludGVybmV0LURy
YWZ0cyBhcmUgZHJhZnQgZG9jdW1lbnRzIHZhbGlkIGZvciBhIG1heGltdW0gb2Ygc2l4IG1vbnRo
cwogICBhbmQgbWF5IGJlIHVwZGF0ZWQsIHJlcGxhY2VkLCBvciBvYnNvbGV0ZWQgYnkgb3RoZXIg
ZG9jdW1lbnRzIGF0IGFueQogICB0aW1lLiAgSXQgaXMgaW5hcHByb3ByaWF0ZSB0byB1c2UgSW50
ZXJuZXQtRHJhZnRzIGFzIHJlZmVyZW5jZQogICBtYXRlcmlhbCBvciB0byBjaXRlIHRoZW0gb3Ro
ZXIgdGhhbiBhcyAid29yayBpbiBwcm9ncmVzcy4iCgogICBUaGUgbGlzdCBvZiBjdXJyZW50IElu
dGVybmV0LURyYWZ0cyBjYW4gYmUgYWNjZXNzZWQgYXQKICAgaHR0cDovL3d3dy5pZXRmLm9yZy9p
ZXRmLzFpZC1hYnN0cmFjdHMudHh0LgoKICAgVGhlIGxpc3Qgb2YgSW50ZXJuZXQtRHJhZnQgU2hh
ZG93IERpcmVjdG9yaWVzIGNhbiBiZSBhY2Nlc3NlZCBhdAogICBodHRwOi8vd3d3LmlldGYub3Jn
L3NoYWRvdy5odG1sLgoKICAgVGhpcyBJbnRlcm5ldC1EcmFmdCB3aWxsIGV4cGlyZSBvbiBTZXB0
ZW1iZXIgMTksIDIwMDkuCgpDb3B5cmlnaHQgTm90aWNlCgogICBDb3B5cmlnaHQgKGMpIDIwMDkg
SUVURiBUcnVzdCBhbmQgdGhlIHBlcnNvbnMgaWRlbnRpZmllZCBhcyB0aGUKICAgZG9jdW1lbnQg
YXV0aG9ycy4gIEFsbCByaWdodHMgcmVzZXJ2ZWQuCgogICBUaGlzIGRvY3VtZW50IGlzIHN1Ympl
Y3QgdG8gQkNQIDc4IGFuZCB0aGUgSUVURiBUcnVzdCdzIExlZ2FsCiAgIFByb3Zpc2lvbnMgUmVs
YXRpbmcgdG8gSUVURiBEb2N1bWVudHMgaW4gZWZmZWN0IG9uIHRoZSBkYXRlIG9mCiAgIHB1Ymxp
Y2F0aW9uIG9mIHRoaXMgZG9jdW1lbnQgKGh0dHA6Ly90cnVzdGVlLmlldGYub3JnL2xpY2Vuc2Ut
aW5mbykuCiAgIFBsZWFzZSByZXZpZXcgdGhlc2UgZG9jdW1lbnRzIGNhcmVmdWxseSwgYXMgdGhl
eSBkZXNjcmliZSB5b3VyIHJpZ2h0cwogICBhbmQgcmVzdHJpY3Rpb25zIHdpdGggcmVzcGVjdCB0
byB0aGlzIGRvY3VtZW50LgoKCgoKCgoKCgpOYXRhbGUgICAgICAgICAgICAgICAgIEV4cGlyZXMg
U2VwdGVtYmVyIDE5LCAyMDA5ICAgICAgICAgICAgICAgW1BhZ2UgMV0KDApJbnRlcm5ldC1EcmFm
dCAgICBFeHByZXNzaW5nIFNOTVAgU01JIERhdGF0eXBlcyBpbiBYU0QgICAgICAgIE1hcmNoIDIw
MDkKCgpBYnN0cmFjdAoKICAgVGhpcyBtZW1vIGRlZmluZXMgdGhlIElFVEYgc3RhbmRhcmQgZXhw
cmVzc2lvbiBvZiBTdHJ1Y3R1cmUgb2YKICAgTWFuYWdlbWVudCBJbmZvcm1hdGlvbiAoU01JKSBi
YXNlIGRhdGF0eXBlcyBpbiBFeHRlbnNpYmxlIE1hcmt1cAogICBMYW5ndWFnZSAoWE1MKSBTY2hl
bWEgRGVmaW5pdGlvbiAoWFNEKSBsYW5ndWFnZS4gIFRoZSBwcmltYXJ5CiAgIG9iamVjdGl2ZSBv
ZiB0aGlzIG1lbW8gaXMgdG8gZW5hYmxlIHRoZSBwcm9kdWN0aW9uIG9mIFhNTCBkb2N1bWVudHMK
ICAgdGhhdCBhcmUgYXMgZmFpdGhmdWwgdG8gdGhlIFNNSSBhcyBwb3NzaWJsZSwgdXNpbmcgWFNE
IGFzIHRoZQogICB2YWxpZGF0aW9uIG1lY2hhbmlzbS4KCgpUYWJsZSBvZiBDb250ZW50cwoKICAg
MS4gIEludHJvZHVjdGlvbiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuICAzCiAgIDIuICBDb252ZW50aW9ucyAgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgNQogICAzLiAgUmVxdWlyZW1lbnRzIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDYKICAgNC4gIFhTRCBm
b3IgU01JIEJhc2UgRGF0YXR5cGVzIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
ICA3CiAgIDUuICBSYXRpb25hbGUgIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAxMAogICAgIDUuMS4gIE51bWVyaWMgRGF0YXR5cGVzICAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gMTAKICAgICA1LjIuICBPY3RldFN0cmlu
ZyAgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIDEwCiAgICAg
NS4zLiAgT3BhcXVlIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAxMQogICAgIDUuNC4gIElwQWRkcmVzcyAgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gMTIKICAgICA1LjUuICBPYmplY3RJZGVudGlmaWVyIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIDEyCiAgIDYuICBTZWN1cml0
eSBDb25zaWRlcmF0aW9ucyAgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAx
MwogICA3LiAgSUFOQSBDb25zaWRlcmF0aW9ucyAgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gMTQKICAgICA3LjEuICBTTUkgQmFzZSBEYXRhdHlwZXMgTmFtZXNwYWNl
IFJlZ2lzdHJhdGlvbiAgLiAuIC4gLiAuIC4gLiAuIDE0CiAgICAgNy4yLiAgU01JIEJhc2UgRGF0
YXR5cGVzIFNjaGVtYSBSZWdpc3RyYXRpb24gLiAuIC4gLiAuIC4gLiAuIC4gLiAxNAogICA4LiAg
QWNrbm93bGVkZ2VtZW50cyAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gMTUKICAgOS4gIFJlZmVyZW5jZXMgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIDE2CiAgICAgOS4xLiAgTm9ybWF0aXZlIFJlZmVyZW5jZXMg
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAxNgogICAgIDkuMi4gIEluZm9y
bWF0aW9uYWwgUmVmZXJlbmNlcyAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gMTYK
ICAgQXV0aG9yJ3MgQWRkcmVzcyAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIDE3CgoKCgoKCgoKCgoKCgoKCgoKCgoKTmF0YWxlICAgICAgICAgICAgICAg
ICBFeHBpcmVzIFNlcHRlbWJlciAxOSwgMjAwOSAgICAgICAgICAgICAgIFtQYWdlIDJdCgwKSW50
ZXJuZXQtRHJhZnQgICAgRXhwcmVzc2luZyBTTk1QIFNNSSBEYXRhdHlwZXMgaW4gWFNEICAgICAg
ICBNYXJjaCAyMDA5CgoKMS4gIEludHJvZHVjdGlvbgoKICAgTnVtZXJvdXMgdXNlcyBleGlzdCAt
LSBib3RoIHdpdGhpbiBhbmQgb3V0c2lkZSB0aGUgdHJhZGl0aW9uYWwgSUVURgogICBuZXR3b3Jr
IG1hbmFnZW1lbnQgY29tbXVuaXR5IC0tIGZvciB0aGUgZXhwcmVzc2lvbiBvZiBtYW5hZ2VtZW50
CiAgIGluZm9ybWF0aW9uIGRlc2NyaWJlZCBpbiBhbmQgYWNjZXNzaWJsZSB2aWEgU01JIE1hbmFn
ZW1lbnQKICAgSW5mb3JtYXRpb24gQmFzZSAoTUlCKSBtb2R1bGVzIGFzIFhNTCBkb2N1bWVudHMg
W1hNTF0uICBGb3IgZXhhbXBsZSwKICAgWE1MLWJhc2VkIG1hbmFnZW1lbnQgYXBwbGljYXRpb25z
IHdoaWNoIHdhbnQgdG8gaW5jb3Jwb3JhdGUgTUlCCiAgIG1vZHVsZXMgYXMgZGF0YSBtb2RlbHMg
YW5kL29yIHRvIGFjY2VzcyBNSUIgbW9kdWxlIGluc3RydW1lbnRhdGlvbgogICB2aWEgZ2F0ZXdh
eXMgdG8gU05NUCBhZ2VudHMgd2lsbCBiZW5lZml0IGZyb20gYW4gSUVURiBzdGFuZGFyZAogICBt
YXBwaW5nIG9mIFNNSSBkYXRhdHlwZXMgdG8gWE1MIGRvY3VtZW50cyB2aWEgWFNELgoKICAgTUlC
IGRhdGEgbW9kZWxzIGFyZSBkZXNjcmliZWQgdXNpbmcgU01JdjIgW1JGQzI1NzhdIGFuZCwgZm9y
IGxlZ2FjeQogICBNSUJzLCBTTUl2MSBbUkZDMTE1NV0uICBNSUIgZGF0YSBpcyBjb252ZXllZCBp
biB2YXJpYWJsZSBiaW5kaW5ncwogICAoInZhcmJpbmRzIikgd2l0aGluIHByb3RvY29sIGRhdGEg
dW5pdHMgKFBEVXMpIHdpdGhpbiBTTk1QIG1lc3NhZ2VzCiAgIHVzaW5nIHRoZSBiYXNlL3ByaW1p
dGl2ZSBkYXRhdHlwZXMgZGVmaW5lZCBpbiB0aGUgU01JLgoKICAgVGhlIFNNSSBhbGxvd3MgZm9y
IGNyZWF0aW9uIG9mIGRlcml2YXRpdmUgZGF0YXR5cGVzLCB0ZXJtZWQgInRleHR1YWwKICAgY29u
dmVudGlvbnMiICgiVENzIiksIGVhY2ggb2Ygd2hpY2ggaGFzIGEgdW5pcXVlIG5hbWUsIGEgc3lu
dGF4IHdoaWNoCiAgIGlzIG9yIHJlZmluZXMgYSBwcmltaXRpdmUgU01JIGRhdGF0eXBlLCBhbmQg
cmVsYXRpdmVseSBwcmVjaXNlCiAgIGFwcGxpY2F0aW9uLWxldmVsIHNlbWFudGljcy4gIFRDcyBh
cmUgdXNlZCBwcmluY2lwYWxseSB0byBmYWNpbGl0YXRlCiAgIGNvcnJlY3QgYXBwbGljYXRpb24t
bGV2ZWwgaGFuZGxpbmcgb2YgTUlCIGRhdGEgYW5kIGZvciB0aGUKICAgY29udmVuaWVuY2Ugb2Yg
aHVtYW5zIHJlYWRpbmcgTUlCIG1vZHVsZXMgYW5kIGFwcHJvcHJpYXRlbHkgcmVuZGVyZWQKICAg
TUlCIGRhdGEgb3V0cHV0LiAgVmFsdWVzIGluIHZhcmJpbmRzIGNvcnJlc3BvbmRpbmcgdG8gTUlC
IG9iamVjdHMKICAgd2l0aCBUQyBzeW50YXhlcyBhcmUgYWx3YXlzIGVuY29kZWQgYXMgdGhlIHBy
aW1pdGl2ZSBTTUkgZGF0YXR5cGUKICAgdW5kZXJseWluZyB0aGUgVEMgc3ludGF4LiAgVGh1cywg
dGhlIFhTRCBtYXBwaW5ncyBkZWZpbmVkIGluIHRoaXMKICAgbWVtbyB3aWxsIHN1cHBvcnQgTUlC
IG9iamVjdHMgd2l0aCBUQyBzeW50YXggYXMgd2VsbCBhcyB0aG9zZSB3aXRoCiAgIGJhc2UgU01J
IHN5bnRheC4KCiAgIFZhcmlvdXMgaW5kZXBlbmRlbnQgc2NoZW1lcyBoYXZlIGJlZW4gZGV2aXNl
ZCBmb3IgZXhwcmVzc2luZyB0aGUgU01JCiAgIGRhdGF0eXBlcyBpbiBYU0QgW1hNTFNjaGVtYV0u
ICBUaGVzZSBzY2hlbWVzIGhhdmUgZXhoaWJpdGVkIGEgZGVncmVlCiAgIG9mIGNvbW1vbmFsaXR5
IChlc3BlY2lhbGx5IGNvbmNlcm5pbmcgdGhlIG51bWVyaWMgU01JIGRhdGF0eXBlcyksIGJ1dAog
ICBhbHNvIHN1ZmZpY2llbnQgZGlmZmVyZW5jZXMgKGVzcGVjaWFsbHkgY29uY2VybmluZyB0aGUg
bm9uLW51bWVyaWMKICAgU01JIGRhdGF0eXBlcykgdG8gcHJlY2x1ZGUgdW5pZm9ybWl0eSBhbmQg
Z2VuZXJhbCBpbnRlcm9wZXJhYmlsaXR5LgoKICAgVGhlIHByaW1hcnkgcHVycG9zZSBvZiB0aGlz
IG1lbW8gaXMgdG8gZGVmaW5lIGEgc3RhbmRhcmQgZXhwcmVzc2lvbgogICBvZiBTTUkgYmFzZSBk
YXRhdHlwZXMgaW4gWFNEIHRvIGVuc3VyZSBmaWRlbGl0eSwgY29uc2lzdGVuY3ksIGFuZAogICBn
ZW5lcmFsIGludGVyb3BlcmFiaWxpdHkgaW4gdGhpcyByZXNwZWN0LiAgSW50ZXJuZXQgb3BlcmF0
b3JzLAogICBtYW5hZ2VtZW50IHRvb2wgZGV2ZWxvcGVycywgYW5kIHVzZXJzIHdpbGwgYmVuZWZp
dCBmcm9tIHRoZSB3aWRlcgogICBzZWxlY3Rpb24gb2YgbWFuYWdlbWVudCB0b29scyBhbmQgdGhl
IGdyZWF0ZXIgZGVncmVlIG9mIHVuaWZpZWQKICAgbWFuYWdlbWVudCAtLSB3aXRoIGF0dGVuZGFu
dCBpbXByb3ZlbWVudHMgaW4gdGltZWxpbmVzcyBhbmQgYWNjdXJhY3kKICAgb2YgbWFuYWdlbWVu
dCBpbmZvcm1hdGlvbiAtLSB3aGljaCBzdWNoIGEgc3RhbmRhcmQgZmFjaWxpdGF0ZXMuCgogICBP
biBpdHMgb3duLCB0aGlzIG1lbW8gc3BlY2lmaWVzIHRoZSBJRVRGIHN0YW5kYXJkIHdheSB0byBy
ZW5kZXIgU01JCiAgIGRhdGEgdmFsdWVzIGNhcnJpZWQgaW4gU05NUCBtZXNzYWdlcyBhcyBYTUwg
aW4gYSBmYWl0aGZ1bCwKICAgY29uc2lzdGVudCwgYW5kIGludGVyb3BlcmFibGUgd2F5LgoKICAg
Q2VydGFpbiBYTUwtYmFzZWQgYXBwbGljYXRpb25zIHdpbGwgZmluZCB0aGlzIHNwZWNpZmljYXRp
b24KICAgc3VmZmljaWVudCBmb3IgdGhlaXIgcHVycG9zZXMuICBPdGhlciBYTUwgYXBwbGljYXRp
b25zIG1heSBuZWVkIHRvCgoKCk5hdGFsZSAgICAgICAgICAgICAgICAgRXhwaXJlcyBTZXB0ZW1i
ZXIgMTksIDIwMDkgICAgICAgICAgICAgICBbUGFnZSAzXQoMCkludGVybmV0LURyYWZ0ICAgIEV4
cHJlc3NpbmcgU05NUCBTTUkgRGF0YXR5cGVzIGluIFhTRCAgICAgICAgTWFyY2ggMjAwOQoKCiAg
IG1ha2UgbW9yZSBjb21wbGV0ZSByZXVzZSBvZiBleGlzdGluZyBNSUIgbW9kdWxlcywgcmVxdWly
aW5nIHN0YW5kYXJkCiAgIFhTRHMgZm9yIFRDcyBbUkZDMjU3OV0gYW5kIE1JQiBzdHJ1Y3R1cmUg
W1JGQzI1NzhdLiAgRG9jdW1lbnRzCiAgIHN1cHBvcnRpbmcgdGhvc2UgcmVxdWlyZW1lbnRzIGFy
ZSBwbGFubmVkLCBidXQgaGF2ZSBub3QgYmVlbiBwcm9kdWNlZAogICBhdCB0aGUgdGltZSBvZiB0
aGlzIHdyaXRpbmcuCgogICBUaGUgb2JqZWN0aXZlIG9mIHRoaXMgbWVtbywgYW5kIG9mIGFueSBm
dXR1cmUgcmVsYXRlZCBzcGVjaWZpY2F0aW9ucwogICB0aGF0IG1pZ2h0IGJlIHByb2R1Y2VkLCBp
cyB0byBkZWZpbmUgdGhlIFhTRCBlcXVpdmFsZW50CiAgIFtYU0REYXRhdHlwZXNdIG9mIFNNSXYy
IChTVEQ1OCkgdG8gZW5jb3VyYWdlIFhNTC1iYXNlZCBwcm90b2NvbHMgdG8KICAgY2FycnksIGFu
ZCBYTUwtYmFzZWQgYXBwbGljYXRpb25zIHRvIHVzZSwgdGhlIGluZm9ybWF0aW9uIG1vZGVsZWQg
aW4KICAgU01JdjItY29tcGxpYW50IE1JQiBtb2R1bGVzLgoKICAgSGF2aW5nIHN1Y2ggYSBzdGFu
ZGFyZCBtYXBwaW5nIG9mIFNNSXYyIHRvIFhNTCB2aWEgWFNEIHZhbGlkYXRpb24KICAgd2lsbCBl
bmFibGUgYW5kIHByb21vdGUgZWZmaWNpZW50IHJldXNlIG9mIGV4aXN0aW5nIChpbmNsdWRpbmcK
ICAgZnV0dXJlKSBNSUIgbW9kdWxlcyBhbmQgaW5zdHJ1bWVudGF0aW9uIGJ5IFhNTC1iYXNlZCBt
YW5hZ2VtZW50CiAgIHByb3RvY29scyBhbmQgYXBwbGljYXRpb25zLgoKICAgVGhlIGdvYWwgb2Yg
ZmlkZWxpdHkgdG8gdGhlIFNNSXYyIHN0YW5kYXJkIChTVEQ1OCksIGFzIHNwZWNpZmllZCBpbgog
ICB0aGUgIlJlcXVpcmVtZW50cyIgc2VjdGlvbiBiZWxvdywgaXMgY3J1Y2lhbCB0byB0aGlzIGVm
Zm9ydCB0bwogICBsZXZlcmFnZSB0aGUgZXN0YWJsaXNoZWQgInJvdWdoIGNvbnNlbnN1cyIgZm9y
IHRoZSBwcmVjaXNlIGRhdGEKICAgbW9kZWxpbmcgdXNlZCBpbiBNSUIgbW9kdWxlcywgYW5kIHRv
IGxldmVyYWdlIGV4aXN0aW5nICJydW5uaW5nIGNvZGUiCiAgIGZvciBpbXBsZW1lbnRlZCBTTUl2
MiBkYXRhIG1vZGVscy4gIFRoaXMgZWZmb3J0IGRvZXMgbm90IGluY2x1ZGUKICAgcmVkZXNpZ24g
b2YgU01JdjIgZGF0YXR5cGVzIG9yIGRhdGEgc3RydWN0dXJlcyBvciB0ZXh0dWFsIGNvbnZlbnRp
b25zCiAgIHRvIG92ZXJjb21lIGtub3duIGxpbWl0YXRpb25zIC0tIHRoYXQgd29yayBjYW4gYmUg
cHVyc3VlZCBpbiBvdGhlcgogICBlZmZvcnRzLgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgpO
YXRhbGUgICAgICAgICAgICAgICAgIEV4cGlyZXMgU2VwdGVtYmVyIDE5LCAyMDA5ICAgICAgICAg
ICAgICAgW1BhZ2UgNF0KDApJbnRlcm5ldC1EcmFmdCAgICBFeHByZXNzaW5nIFNOTVAgU01JIERh
dGF0eXBlcyBpbiBYU0QgICAgICAgIE1hcmNoIDIwMDkKCgoyLiAgQ29udmVudGlvbnMKCiAgIFRo
ZSBrZXkgd29yZHMgIk1VU1QiLCAiTVVTVCBOT1QiLCAiUkVRVUlSRUQiLCAiU0hBTEwiLCAiU0hB
TEwgTk9UIiwKICAgIlNIT1VMRCIsICJTSE9VTEQgTk9UIiwgIlJFQ09NTUVOREVEIiwgIk1BWSIs
IGFuZCAiT1BUSU9OQUwiIGluIHRoaXMKICAgZG9jdW1lbnQgYXJlIHRvIGJlIGludGVycHJldGVk
IGFzIGRlc2NyaWJlZCBpbiBSRkMgMjExOSBbUkZDMjExOV0uCgoKCgoKCgoKCgoKCgoKCgoKCgoK
CgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgpOYXRhbGUgICAgICAgICAgICAgICAgIEV4cGlyZXMg
U2VwdGVtYmVyIDE5LCAyMDA5ICAgICAgICAgICAgICAgW1BhZ2UgNV0KDApJbnRlcm5ldC1EcmFm
dCAgICBFeHByZXNzaW5nIFNOTVAgU01JIERhdGF0eXBlcyBpbiBYU0QgICAgICAgIE1hcmNoIDIw
MDkKCgozLiAgUmVxdWlyZW1lbnRzCgogICBUaGUgZm9sbG93aW5nIHNldCBvZiByZXF1aXJlbWVu
dHMgaXMgaW50ZW5kZWQgdG8gcHJvZHVjZSBYTUwKICAgZG9jdW1lbnRzIHdoaWNoIGNhbiBiZSB2
YWxpZGF0ZWQgdmlhIHRoZSBYU0QgZGVmaW5lZCBpbiB0aGlzCiAgIHNwZWNpZmljYXRpb24gdG8g
ZmFpdGhmdWxseSByZXByZXNlbnQgdmFsdWVzIGNhcnJpZWQgIm9uLXRoZS13aXJlIiBpbgogICBT
Tk1QIFBEVXMgYXMgZGVmaW5lZCBieSB0aGUgU01JOgoKICAgUjEuICBBbGwgU01JIGJhc2UgZGF0
YXR5cGVzIE1VU1QgaGF2ZSBhIGNvcnJlc3BvbmRpbmcgWFNEIGRhdGF0eXBlLgoKICAgUjIuICBT
TUl2MiBpcyB0aGUgbm9ybWF0aXZlIFNNSSBmb3IgdGhpcyBkb2N1bWVudCAtLSBTTUl2MSBtb2R1
bGVzLAogICAgICAgIGlmIGVuY291bnRlcmVkLCBNVVNUIGJlIGNvbnZlcnRlZCAoYXQgbGVhc3Qg
bG9naWNhbGx5KSBpbgogICAgICAgIGFjY29yZGFuY2Ugd2l0aCBTZWN0aW9uIDIuMSwgaW5jbHVz
aXZlLCBvZiB0aGUgIkNvZXhpc3RlbmNlIiBSRkMKICAgICAgICBbUkZDMzU4NF0uCgogICBSMy4g
IFRoZSBYU0QgZGF0YXR5cGUgc3BlY2lmaWVkIGZvciBhIGdpdmVuIFNNSSBkYXRhdHlwZSBNVVNU
IGJlIGFibGUKICAgICAgICB0byByZXByZXNlbnQgYWxsIHZhbGlkIHZhbHVlcyBmb3IgdGhhdCBT
TUkgZGF0YXR5cGUuCgogICBSNC4gIFRoZSBYU0QgZGF0YXR5cGUgc3BlY2lmaWVkIGZvciBhIGdp
dmVuIFNNSSBkYXRhdHlwZSBNVVNUCiAgICAgICAgcmVwcmVzZW50IGFueSBzcGVjaWFsIGVuY29k
aW5nIHJ1bGVzIGFzc29jaWF0ZWQgd2l0aCB0aGF0IFNNSQogICAgICAgIGRhdGF0eXBlLgoKICAg
UjUuICBUaGUgWFNEIGRhdGF0eXBlIHNwZWNpZmllZCBmb3IgYSBnaXZlbiBTTUkgZGF0YXR5cGUg
TVVTVCBpbmNsdWRlCiAgICAgICAgYW55IHJlc3RyaWN0aW9ucyBvbiB2YWx1ZXMgYXNzb2NpYXRl
ZCB3aXRoIHRoZSBTTUkgZGF0YXR5cGUuCgogICBSNi4gIFRoZSBYU0QgZGF0YXR5cGUgc3BlY2lm
aWVkIGZvciBhIGdpdmVuIFNNSSBkYXRhdHlwZSBNVVNUIGJlIHRoZQogICAgICAgIG1vc3QgZGly
ZWN0IFhTRCBkYXRhdHlwZSwgd2l0aCB0aGUgbW9zdCBwYXJzaW1vbmlvdXMKICAgICAgICByZXN0
cmljdGlvbnMsIHdoaWNoIG1hdGNoZXMgdGhlIGZvcmVnb2luZyByZXF1aXJlbWVudHMuCgogICBS
Ny4gIFRoZSBYTUwgb3V0cHV0IHByb2R1Y2VkIGFzIGEgcmVzdWx0IG9mIG1lZXRpbmcgdGhlIGZv
cmVnb2luZwogICAgICAgIHJlcXVpcmVtZW50cyBTSE9VTEQgYmUgdGhlIG1vc3QgZGlyZWN0IChp
LmUuLCBhdm9pZGluZwogICAgICAgIHN1cGVyZmx1b3VzICJkZWNvcmF0aW9uIikgZnJvbSB0aGUg
cGVyc3BlY3RpdmUgb2YgcmVhZGFiaWxpdHkgYnkKICAgICAgICBodW1hbnMuCgoKCgoKCgoKCgoK
CgoKCgoKCgpOYXRhbGUgICAgICAgICAgICAgICAgIEV4cGlyZXMgU2VwdGVtYmVyIDE5LCAyMDA5
ICAgICAgICAgICAgICAgW1BhZ2UgNl0KDApJbnRlcm5ldC1EcmFmdCAgICBFeHByZXNzaW5nIFNO
TVAgU01JIERhdGF0eXBlcyBpbiBYU0QgICAgICAgIE1hcmNoIDIwMDkKCgo0LiAgWFNEIGZvciBT
TUkgQmFzZSBEYXRhdHlwZXMKCiAgIFRoaXMgZG9jdW1lbnQgcHJvdmlkZXMgWFNEIGRhdGF0eXBl
IG1hcHBpbmdzIGZvciB0aGUgU01JdjIgYmFzZQogICBkYXRhdHlwZXMgb25seSAtLSBpLmUuLCB0
aGUgZWxldmVuICJPYmplY3RTeW50YXgiIGRhdGF0eXBlcyBkZWZpbmVkCiAgIGluIFJGQyAyNTc4
LiAgVGhlc2UgZGF0YXR5cGVzIC0tIHZpYSB0YWcgdmFsdWVzIGRlZmluZWQgaW4gdGhlIFNNSXYy
CiAgIHRvIGlkZW50aWZ5IHRoZW0gaW4gdmFyYmluZHMgLS0gY29uc3RyYWluIHZhbHVlcyBjYXJy
aWVkICJvbi10aGUtCiAgIHdpcmUiIGluIFNOTVAgUERVcyBiZXR3ZWVuIFNOTVAgbWFuYWdlbWVu
dCBhcHBsaWNhdGlvbnMgYW5kIFNOTVAKICAgYWdlbnRzOgoKICAgbyAgSU5URUdFUiwgSW50ZWdl
cjMyCgogICBvICBVbnNpZ25lZDMyLCBHYXVnZTMyCgogICBvICBDb3VudGVyMzIKCiAgIG8gIFRp
bWVUaWNrcwoKICAgbyAgQ291bnRlcjY0CgogICBvICBPQ1RFVCBTVFJJTkcKCiAgIG8gIE9wYXF1
ZQoKICAgbyAgSXBBZGRyZXNzCgogICBvICBPQkpFQ1QgSURFTlRJRklFUgoKICAgVGhlICJCSVRT
IiBwc2V1ZG8tdHlwZSAoYWxzbyByZWZlcnJlZCB0byBhcyBhICJjb25zdHJ1Y3QiIGluIFJGQwog
ICAyNTc4KSBpcyB0cmVhdGVkIGFzIGEgVGV4dHVhbCBDb252ZW50aW9uLCBub3QgYSBiYXNlIGRh
dGF0eXBlLCBmb3IKICAgdGhlIHB1cnBvc2Ugb2YgdGhpcyBkb2N1bWVudC4KCgoKCgoKCgoKCgoK
CgoKCgoKCgoKTmF0YWxlICAgICAgICAgICAgICAgICBFeHBpcmVzIFNlcHRlbWJlciAxOSwgMjAw
OSAgICAgICAgICAgICAgIFtQYWdlIDddCgwKSW50ZXJuZXQtRHJhZnQgICAgRXhwcmVzc2luZyBT
Tk1QIFNNSSBEYXRhdHlwZXMgaW4gWFNEICAgICAgICBNYXJjaCAyMDA5CgoKICAgQkVHSU4KCiAg
IDw/eG1sIHZlcnNpb249IjEuMCIgZW5jb2Rpbmc9InV0Zi04Ij8+CiAgIDx4czpzY2hlbWEgeG1s
bnM6eHM9Imh0dHA6Ly93d3cudzMub3JnLzIwMDEvWE1MU2NoZW1hIgogICB4bWxucz0idXJuOmll
dGY6cGFyYW1zOnhtbDpuczpvcHNhd2c6c21pOmJhc2U6MS4wIgogICB0YXJnZXROYW1lc3BhY2U9
InVybjppZXRmOnBhcmFtczp4bWw6bnM6b3BzYXdnOnNtaTpiYXNlOjEuMCIKICAgZWxlbWVudEZv
cm1EZWZhdWx0PSJxdWFsaWZpZWQiCiAgIGF0dHJpYnV0ZUZvcm1EZWZhdWx0PSJ1bnF1YWxpZmll
ZCIKICAgeG1sOmxhbmc9ImVuIj4KCiAgICAgPHhzOmFubm90YXRpb24+CiAgICAgICA8eHM6ZG9j
dW1lbnRhdGlvbj4KICAgICAgICAgICBNYXBwaW5nIG9mIFNNSXYyIGJhc2UgZGF0YXR5cGVzIGZy
b20gUkZDIDI1NzgKCiAgICAgICAgICAgQ29udGFjdDogICAgICBCb2IgTmF0YWxlCiAgICAgICAg
ICAgT3JnYW5pemF0aW9uOiBNSVRSRQogICAgICAgICAgIEFkZHJlc3M6ICAgICAgNzUxNSBDb2xz
aGlyZSBEcml2ZQogICAgICAgICAgICAgICAgICAgICAgICAgTWNMZWFuIFZBIDIyMTAyCiAgICAg
ICAgICAgICAgICAgICAgICAgICBVU0EKICAgICAgICAgICBUZWxlcGhvbmU6ICAgICsxIDcwMy05
ODMtMjUwNQogICAgICAgICAgIEUtTWFpbDogICAgICAgcm5hdGFsZUBtaXRyZS5vcmcKICAgICAg
ICAgICBMYXN0IFVwZGF0ZWQ6IDIwMDkwMzA5MDAwMFoKICAgICAgIDwveHM6ZG9jdW1lbnRhdGlv
bj4KICAgICA8L3hzOmFubm90YXRpb24+CgogICAgIDx4czpzaW1wbGVUeXBlIG5hbWU9IklOVEVH
RVIiPgogICAgICAgPHhzOnJlc3RyaWN0aW9uIGJhc2U9InhzOmludCIvPgogICAgIDwveHM6c2lt
cGxlVHlwZT4KCiAgICAgPHhzOnNpbXBsZVR5cGUgbmFtZT0iSW50ZWdlcjMyIj4KICAgICAgIDx4
czpyZXN0cmljdGlvbiBiYXNlPSJ4czppbnQiLz4KICAgICA8L3hzOnNpbXBsZVR5cGU+CgogICAg
IDx4czpzaW1wbGVUeXBlIG5hbWU9IlVuc2lnbmVkMzIiPgogICAgICAgPHhzOnJlc3RyaWN0aW9u
IGJhc2U9InhzOnVuc2lnbmVkSW50Ii8+CiAgICAgPC94czpzaW1wbGVUeXBlPgoKICAgICA8eHM6
c2ltcGxlVHlwZSBuYW1lPSJHYXVnZTMyIj4KICAgICAgIDx4czpyZXN0cmljdGlvbiBiYXNlPSJ4
czp1bnNpZ25lZEludCIvPgogICAgIDwveHM6c2ltcGxlVHlwZT4KCiAgICAgPHhzOnNpbXBsZVR5
cGUgbmFtZT0iQ291bnRlcjMyIj4KICAgICAgIDx4czpyZXN0cmljdGlvbiBiYXNlPSJ4czp1bnNp
Z25lZEludCIvPgogICAgIDwveHM6c2ltcGxlVHlwZT4KCiAgICAgPHhzOnNpbXBsZVR5cGUgbmFt
ZT0iVGltZVRpY2tzIj4KICAgICAgIDx4czpyZXN0cmljdGlvbiBiYXNlPSJ4czp1bnNpZ25lZElu
dCIvPgogICAgIDwveHM6c2ltcGxlVHlwZT4KCgoKTmF0YWxlICAgICAgICAgICAgICAgICBFeHBp
cmVzIFNlcHRlbWJlciAxOSwgMjAwOSAgICAgICAgICAgICAgIFtQYWdlIDhdCgwKSW50ZXJuZXQt
RHJhZnQgICAgRXhwcmVzc2luZyBTTk1QIFNNSSBEYXRhdHlwZXMgaW4gWFNEICAgICAgICBNYXJj
aCAyMDA5CgoKICAgICA8eHM6c2ltcGxlVHlwZSBuYW1lPSJDb3VudGVyNjQiPgogICAgICAgPHhz
OnJlc3RyaWN0aW9uIGJhc2U9InhzOnVuc2lnbmVkTG9uZyIvPgogICAgIDwveHM6c2ltcGxlVHlw
ZT4KCiAgICAgPHhzOnNpbXBsZVR5cGUgbmFtZT0iT2N0ZXRTdHJpbmciPgogICAgICAgPHhzOnJl
c3RyaWN0aW9uIGJhc2U9InhzOmhleEJpbmFyeSI+CiAgICAgICAgIDx4czptYXhMZW5ndGggdmFs
dWU9IjY1NTM1Ii8+CiAgICAgICA8L3hzOnJlc3RyaWN0aW9uPgogICAgIDwveHM6c2ltcGxlVHlw
ZT4KCiAgICAgPHhzOnNpbXBsZVR5cGUgbmFtZT0iT3BhcXVlIj4KICAgICAgIDx4czpyZXN0cmlj
dGlvbiBiYXNlPSJ4czpoZXhCaW5hcnkiLz4KICAgICA8L3hzOnNpbXBsZVR5cGU+CgogICAgIDx4
czpzaW1wbGVUeXBlIG5hbWU9IklwQWRkcmVzcyI+CiAgICAgICA8eHM6cmVzdHJpY3Rpb24gYmFz
ZT0ieHM6c3RyaW5nIj4KICAgICAgICAgPHhzOnBhdHRlcm4gdmFsdWU9CiAgICAgICAgICIoKDB8
KDFbMC05XXswLDJ9KXwKICAgICAgICAgICAoMigoWzAtNF1bMC05XT8pfCg1WzAtNV0/KXwoWzYt
OV0/KSkpfAogICAgICAgICAgIChbMy05XVswLTldPykpXC4pezN9CiAgICAgICAgICAgKDB8KDFb
MC05XXswLDJ9KXwKICAgICAgICAgICAoMigoWzAtNF1bMC05XT8pfCg1WzAtNV0/KXwoWzYtOV0/
KSkpfAogICAgICAgICAgIChbMy05XVswLTldPykpIi8+CiAgICAgICA8L3hzOnJlc3RyaWN0aW9u
PgogICAgIDwveHM6c2ltcGxlVHlwZT4KCiAgICAgPHhzOnNpbXBsZVR5cGUgbmFtZT0iT2JqZWN0
SWRlbnRpZmllciI+CiAgICAgICA8eHM6cmVzdHJpY3Rpb24gYmFzZT0ieHM6c3RyaW5nIj4KICAg
ICAgICAgPHhzOnBhdHRlcm4gdmFsdWU9CiAgICAgICAgICIoKFswLTFdKFwuWzEtM10/WzAtOV0p
KXwKICAgICAgICAgICAoMlwuKDB8KFsxLTldXGQqKSkpKQogICAgICAgICAgIChcLigwfChbMS05
XVxkKikpKXswLDEyNn0iLz4KICAgICAgIDwveHM6cmVzdHJpY3Rpb24+CiAgICAgPC94czpzaW1w
bGVUeXBlPgoKICAgPC94czpzY2hlbWE+CiAgIEVORAoKCgoKCgoKCgoKCgoKCk5hdGFsZSAgICAg
ICAgICAgICAgICAgRXhwaXJlcyBTZXB0ZW1iZXIgMTksIDIwMDkgICAgICAgICAgICAgICBbUGFn
ZSA5XQoMCkludGVybmV0LURyYWZ0ICAgIEV4cHJlc3NpbmcgU05NUCBTTUkgRGF0YXR5cGVzIGlu
IFhTRCAgICAgICAgTWFyY2ggMjAwOQoKCjUuICBSYXRpb25hbGUKCiAgIFRoZSBYU0QgZGF0YXR5
cGVzLCBpbmNsdWRpbmcgYW55IHNwZWNpZmllZCByZXN0cmljdGlvbnMsIHdlcmUgY2hvc2VuCiAg
IGJhc2VkIG9uIGZpdCB3aXRoIHRoZSByZXF1aXJlbWVudHMgc3BlY2lmaWVkIGVhcmxpZXIgaW4g
dGhpcwogICBkb2N1bWVudCwgYW5kIHdpdGggYXR0ZW50aW9uIHRvIHNpbXBsaWNpdHkgd2hpbGUg
bWFpbnRhaW5pbmcgZmlkZWxpdHkKICAgdG8gdGhlIFNNSS4gIEFsc28sIHRoZSAiY2Fub25pY2Fs
IHJlcHJlc2VudGF0aW9ucyIgKGkuZS4sIHJlZmluZW1lbnRzCiAgIG9mIHRoZSAibGV4aWNhbCBy
ZXByZXNlbnRhdGlvbnMiKSBkb2N1bWVudGVkIGluIHRoZSBXM0MgWFNECiAgIHNwZWNpZmljYXRp
b25zIGFyZSBhc3N1bWVkLgoKNS4xLiAgTnVtZXJpYyBEYXRhdHlwZXMKCiAgIEFsbCBvZiB0aGUg
bnVtZXJpYyBYU0QgZGF0YXR5cGVzIHNwZWNpZmllZCBpbiB0aGUgcHJldmlvdXMgc2VjdGlvbiAt
LQogICBJTlRFR0VSLCBJbnRlZ2VyMzIsIFVuc2lnbmVkMzIsIEdhdWdlMzIsIENvdW50ZXIzMiwg
VGltZVRpY2tzLCBhbmQKICAgQ291bnRlcjY0IC0tIGNvbXBseSB3aXRoIHRoZSByZWxldmFudCBy
ZXF1aXJlbWVudHMKCiAgIG8gIFRoZXkgY292ZXIgYWxsIHZhbGlkIHZhbHVlcyBmb3IgdGhlIGNv
cnJlc3BvbmRpbmcgU01JIGRhdGF0eXBlcy4KCiAgIG8gIFRoZXkgY29tcGx5IHdpdGggdGhlIHN0
YW5kYXJkIGVuY29kaW5nIHJ1bGVzIGFzc29jaWF0ZWQgd2l0aCB0aGUKICAgICAgY29ycmVzcG9u
ZGluZyBTTUkgZGF0YXR5cGVzLgoKICAgbyAgVGhleSBpbmhlcmVudGx5IG1hdGNoIHRoZSByYW5n
ZSByZXN0cmljdGlvbnMgYXNzb2NpYXRlZCB3aXRoIHRoZQogICAgICBjb3JyZXNwb25kaW5nIFNN
SSBkYXRhdHlwZXMuCgogICBvICBUaGV5IGFyZSB0aGUgbW9zdCBkaXJlY3QgWFNEIGRhdGF0eXBl
cyB3aGljaCBleGhpYml0IHRoZSBmb3JlZ29pbmcKICAgICAgY2hhcmFjdGVyaXN0aWNzIHJlbGF0
aXZlIHRvIHRoZSBjb3JyZXNwb25kaW5nIFNNSSBkYXRhdHlwZXMgKHdoaWNoCiAgICAgIGlzIHdo
eSBubyAicmVzdHJpY3Rpb24iIHN0YXRlbWVudHMgLS0gb3RoZXIgdGhhbiB0aGUgImJhc2UiIFhT
RAogICAgICB0eXBlIC0tIGFyZSByZXF1aXJlZCBpbiB0aGUgWFNEKS4KCiAgIG8gIFRoZSBYTUwg
b3V0cHV0IHByb2R1Y2VkIGZyb20gdGhlIGNhbm9uaWNhbCByZXByZXNlbnRhdGlvbiBvZiB0aGVz
ZQogICAgICBYU0QgZGF0YXR5cGVzIGlzIGFsc28gdGhlIG1vc3QgZGlyZWN0IGZyb20gdGhlIHBl
cnNwZWN0aXZlIG9mCiAgICAgIHJlYWRhYmlsaXR5IGJ5IGh1bWFucyAoaS5lLiwgbm8gbGVhZGlu
ZyAiKyIgc2lnbiBhbmQgbm8gbGVhZGluZwogICAgICB6ZXJvcykuCgogICBTcGVjaWFsIG5vdGUg
dG8gYXBwbGljYXRpb24gZGV2ZWxvcGVyczogQ29tcGxpYW5jZSB3aXRoIHRoaXMgc2NoZW1hCiAg
IGluIGFuIG90aGVyd2lzZSBjb3JyZWN0IHRyYW5zbGF0aW9uIGZyb20gcmF3ICgib24tdGhlLXdp
cmUiCiAgIHJlcHJlc2VudGF0aW9uKSBTTk1QIE1JQiBkYXRhIHByb2R1Y2VzIHZhbHVlcyB0aGF0
IGFyZSBmYWl0aGZ1bCB0bwogICB0aGUgb3JpZ2luYWwuICBIb3dldmVyLCB0aGUgR2F1Z2UzMiwg
Q291bnRlcjMyLCBDb3VudGVyNjQsIGFuZAogICBUaW1lVGlja3MgZGF0YXR5cGVzIGhhdmUgc3Bl
Y2lhbCBhcHBsaWNhdGlvbiBzZW1hbnRpY3MgdGhhdCBtdXN0IGJlCiAgIGNvbnNpZGVyZWQgd2hl
biB1c2luZyB0aGVpciByYXcgdmFsdWVzIGZvciBhbnl0aGluZyBvdGhlciB0aGFuCiAgIGRpc3Bs
YXksIHByaW50aW5nLCBzdG9yYWdlLCBvciB0cmFuc21pc3Npb24gb2YgdGhlIGxpdGVyYWwgdmFs
dWUuCiAgIFJGQyAyNTc4IHByb3ZpZGVzIHRoZSBuZWNlc3NhcnkgZGV0YWlscy4KCjUuMi4gIE9j
dGV0U3RyaW5nCgogICBUaGlzIFhTRCBkYXRhdHlwZSBjb3JyZXNwb25kcyB0byB0aGUgU01JICJP
Q1RFVCBTVFJJTkciIGRhdGF0eXBlLgoKICAgU2V2ZXJhbCBpbmRlcGVuZGVudCBzY2hlbWVzIGZv
ciBtYXBwaW5nIFNNSSBkYXRhdHlwZXMgdG8gWFNEIGhhdmUKICAgdXNlZCB0aGUgWFNEICJzdHJp
bmciIHR5cGUgdG8gcmVwcmVzZW50ICJPQ1RFVCBTVFJJTkciLCBidXQgdGhpcwoKCgpOYXRhbGUg
ICAgICAgICAgICAgICAgIEV4cGlyZXMgU2VwdGVtYmVyIDE5LCAyMDA5ICAgICAgICAgICAgICBb
UGFnZSAxMF0KDApJbnRlcm5ldC1EcmFmdCAgICBFeHByZXNzaW5nIFNOTVAgU01JIERhdGF0eXBl
cyBpbiBYU0QgICAgICAgIE1hcmNoIDIwMDkKCgogICBtYXBwaW5nIGRvZXMgbm90IGNvbmZvcm0g
dG8gdGhlIHJlcXVpcmVtZW50cyBzcGVjaWZpZWQgaW4gdGhpcwogICBkb2N1bWVudC4gIE1vc3Qg
bm90YWJseSwgInN0cmluZyIgY2Fubm90IGZhaXRoZnVsbHkgcmVwcmVzZW50IGFsbAogICB2YWxp
ZCB2YWx1ZXMgKDAgdGhydSAyNTUpIHRoYXQgZWFjaCBvY3RldCBpbiBhbiAiT0NURVQgU1RSSU5H
IiBjYW4KICAgaGF2ZSAtLSBvciBhdCBsZWFzdCBjYW5ub3QgZG8gc28gaW4gYSB3YXkgdGhhdCBw
cm92aWRlcyBmb3IgZWFzeQogICBodW1hbiByZWFkYWJpbGl0eSBvZiB0aGUgcmVzdWx0aW5nIFhN
TCBvdXRwdXQuCgogICBDb25zZXF1ZW50bHksIHRoZSBYU0QgZGF0YXR5cGUgImhleEJpbmFyeSIg
aXMgc3BlY2lmaWVkIGFzIHRoZQogICBzdGFuZGFyZCBtYXBwaW5nIG9mIHRoZSBTTUkgIk9DVEVU
IFNUUklORyIgZGF0YXR5cGUuICBJbiBoZXhCaW5hcnksCiAgIGVhY2ggb2N0ZXQgaXMgZW5jb2Rl
ZCBhcyB0d28gaGV4YWRlY2ltYWwgZGlnaXRzOyB0aGUgY2Fub25pY2FsCiAgIHJlcHJlc2VudGF0
aW9uIGxpbWl0cyB0aGUgc2V0IG9mIGFsbG93ZWQgaGV4YWRlY2ltYWwgZGlnaXRzIHRvIDAtOQog
ICBhbmQgdXBwZXJjYXNlIEEtRi4KCiAgIFRoZSBoZXhCaW5hcnkgcmVwcmVzZW50YXRpb24gb2Yg
Ik9DVEVUIFNUUklORyIgY29tcGxpZXMgd2l0aCB0aGUKICAgcmVsZXZhbnQgcmVxdWlyZW1lbnRz
OgoKICAgbyAgSXQgY292ZXJzIGFsbCB2YWxpZCB2YWx1ZXMgZm9yIHRoZSBjb3JyZXNwb25kaW5n
IFNNSSBkYXRhdHlwZS4KCiAgIG8gIEl0IGNvbXBsaWVzIHdpdGggdGhlIHN0YW5kYXJkIGVuY29k
aW5nIHJ1bGVzIGFzc29jaWF0ZWQgd2l0aCB0aGUKICAgICAgY29ycmVzcG9uZGluZyBTTUkgZGF0
YXR5cGUuCgogICBvICBXaXRoIHRoZSAibWF4TGVuZ3RoIiByZXN0cmljdGlvbiB0byA2NTUzNSBv
Y3RldHMsIHRoZSBYU0QgZGF0YXR5cGUKICAgICAgc3BlY2lmaWNhdGlvbiBtYXRjaGVzIHRoZSBy
ZXN0cmljdGlvbnMgYXNzb2NpYXRlZCB3aXRoIHRoZQogICAgICBjb3JyZXNwb25kaW5nIFNNSSBk
YXRhdHlwZS4KCiAgIG8gIEl0IGlzIHRoZSBtb3N0IGRpcmVjdCBYU0QgZGF0YXR5cGUgd2hpY2gg
ZXhoaWJpdHMgdGhlIGZvcmVnb2luZwogICAgICBjaGFyYWN0ZXJpc3RpY3MgcmVsYXRpdmUgdG8g
dGhlIGNvcnJlc3BvbmRpbmcgU01JIGRhdGF0eXBlICh3aGljaAogICAgICBtdXN0IGFsbG93IGZv
ciBhbnkgdmFsaWQgYmluYXJ5IG9jdGV0IHZhbHVlKS4KCiAgIG8gIFRoZSBYTUwgb3V0cHV0IHBy
b2R1Y2VkIGZyb20gdGhlIGNhbm9uaWNhbCByZXByZXNlbnRhdGlvbiBvZiB0aGlzCiAgICAgIFhT
RCBkYXRhdHlwZSBpcyBub3Qgb3B0aW1hbCB3aXRoIHJlc3BlY3QgdG8gcmVhZGFiaWxpdHkgYnkg
aHVtYW5zOwogICAgICBob3dldmVyLCB0aGF0IGlzIGEgY29uc2VxdWVuY2Ugb2YgdGhlIFNNSSBk
YXRhdHlwZSBpdHNlbGYuICBXaGVyZQogICAgICBodW1hbiByZWFkYWJpbGl0eSBpcyBtb3JlIG9m
IGEgY29uY2VybiwgaXQgaXMgbGlrZWx5IHRoYXQgdGhlCiAgICAgIGFjdHVhbCBNSUIgb2JqZWN0
cyBpbiBxdWVzdGlvbiB3aWxsIGJlIHJlcHJlc2VudGVkIGJ5IHRleHR1YWwKICAgICAgY29udmVu
dGlvbnMgd2hpY2ggbGltaXQgdGhlIHNldCBvZiB2YWx1ZXMgdGhhdCB3aWxsIGJlIGluY2x1ZGVk
IGluCiAgICAgIHRoZSBPY3RldFN0cmluZ3MgYW5kIHdpbGwsIHRodXMsIGJ5cGFzcyB0aGUgaGV4
QmluYXJ5IHR5cGluZy4KCjUuMy4gIE9wYXF1ZQoKICAgVGhlICJoZXhCaW5hcnkiIFhTRCBkYXRh
dHlwZSBpcyBzcGVjaWZpZWQgYXMgdGhlIHJlcHJlc2VudGF0aW9uIG9mCiAgIHRoZSBTTUkgIk9w
YXF1ZSIgZGF0YXR5cGUgZ2VuZXJhbGx5IGZvciB0aGUgc2FtZSByZWFzb25zIGFzCiAgICJoZXhC
aW5hcnkiIGlzIHNwZWNpZmllZCBmb3IgdGhlICJPY3RldFN0cmluZyIgZGF0YXR5cGU6CgogICBv
ICBJdCBjb3ZlcnMgYWxsIHZhbGlkIHZhbHVlcyBmb3IgdGhlIGNvcnJlc3BvbmRpbmcgU01JIGRh
dGF0eXBlLgoKICAgbyAgSXQgY29tcGxpZXMgd2l0aCB0aGUgc3RhbmRhcmQgZW5jb2RpbmcgcnVs
ZXMgYXNzb2NpYXRlZCB3aXRoIHRoZQogICAgICBjb3JyZXNwb25kaW5nIFNNSSBkYXRhdHlwZS4K
CgoKCgpOYXRhbGUgICAgICAgICAgICAgICAgIEV4cGlyZXMgU2VwdGVtYmVyIDE5LCAyMDA5ICAg
ICAgICAgICAgICBbUGFnZSAxMV0KDApJbnRlcm5ldC1EcmFmdCAgICBFeHByZXNzaW5nIFNOTVAg
U01JIERhdGF0eXBlcyBpbiBYU0QgICAgICAgIE1hcmNoIDIwMDkKCgogICBvICBUaGVyZSBhcmUg
bm8gcmVzdHJpY3Rpb24gaXNzdWVzIGFzc29jaWF0ZWQgd2l0aCB1c2luZyAiaGV4QmluYXJ5Igog
ICAgICBmb3IgIk9wYXF1ZSIuCgogICBvICBJdCBpcyB0aGUgbW9zdCBkaXJlY3QgWFNEIGRhdGF0
eXBlIHdoaWNoIGV4aGliaXRzIHRoZSBmb3JlZ29pbmcKICAgICAgY2hhcmFjdGVyaXN0aWNzIHJl
bGF0aXZlIHRvIHRoZSBjb3JyZXNwb25kaW5nIFNNSSBkYXRhdHlwZSAod2hpY2gKICAgICAgbXVz
dCBhbGxvdyBmb3IgYW55IHZhbGlkIGJpbmFyeSBvY3RldCB2YWx1ZSkuCgogICBvICBUaGUgWE1M
IG91dHB1dCBwcm9kdWNlZCBmcm9tIHRoZSBjYW5vbmljYWwgcmVwcmVzZW50YXRpb24gb2YgdGhp
cwogICAgICBYU0QgZGF0YXR5cGUgaXMgbm90IG9wdGltYWwgd2l0aCByZXNwZWN0IHRvIHJlYWRh
YmlsaXR5IGJ5IGh1bWFuczsKICAgICAgaG93ZXZlciwgdGhhdCBpcyBhIGNvbnNlcXVlbmNlIG9m
IHRoZSBTTUkgZGF0YXR5cGUgaXRzZWxmLgogICAgICBVbm1lZGlhdGVkICJPcGFxdWUiIGRhdGEg
aXMgaW50ZW5kZWQgZm9yIGNvbnN1bXB0aW9uIGJ5CiAgICAgIGFwcGxpY2F0aW9ucywgbm90IGh1
bWFucy4KCjUuNC4gIElwQWRkcmVzcwoKICAgVGhlIFhTRCAic3RyaW5nIiBkYXRhdHlwZSBpcyB0
aGUgbmF0dXJhbCBjaG9pY2UgdG8gcmVwcmVzZW50IGFuCiAgIElwQWRkcmVzcyBhcyBYTUwgb3V0
cHV0LiAgVGhlICJwYXR0ZXJuIiByZXN0cmljdGlvbiBhcHBsaWVkIGluIHRoaXMKICAgY2FzZSBy
ZXN1bHRzIGluIGEgZG90dGVkLWRlY2ltYWwgc3RyaW5nIG9mIGZvdXIgdmFsdWVzIGJldHdlZW4g
IjAiCiAgIGFuZCAiMjU1IiBzZXBhcmF0ZWQgYnkgYSBwZXJpb2QgKCIuIikgY2hhcmFjdGVyLiAg
VGhpcyBwYXR0ZXJuIGFsc28KICAgcHJlY2x1ZGVzIGxlYWRpbmcgemVyb3MuCgo1LjUuICBPYmpl
Y3RJZGVudGlmaWVyCgogICBUaGlzIFhTRCBkYXRhdHlwZSBjb3JyZXNwb25kcyB0byB0aGUgU01J
ICJPQkpFQ1QgSURFTlRJRklFUiIKICAgZGF0YXR5cGUuCgogICBUaGUgWFNEICJzdHJpbmciIGRh
dGF0eXBlIGlzIGFsc28gdGhlIG5hdHVyYWwgY2hvaWNlIHRvIHJlcHJlc2VudCBhbgogICBPYmpl
Y3RJZGVudGlmaWVyIGFzIFhNTCBvdXRwdXQsIGZvciB0aGUgc2FtZSByZWFzb25zIGFzIGZvciB0
aGUKICAgSXBBZGRyZXNzIGNob2ljZS4gIFRoZSAicGF0dGVybiIgcmVzdHJpY3Rpb24gYXBwbGll
ZCBpbiB0aGlzIGNhc2UKICAgcmVzdWx0cyBpbiBhIGRvdHRlZC1kZWNpbWFsIHN0cmluZyBvZiB1
cCB0byAxMjggZWxlbWVudHMgKHJlZmVycmVkIHRvCiAgIGFzICJzdWItaWRzIiksIGVhY2ggaG9s
ZGluZyBhbiAiVW5zaWduZWQzMiIgaW50ZWdlciB2YWx1ZS4KCiAgIE5vdGUgdGhhdCwgd2hpbGUg
bm90IG1lbnRpb25lZCBpbiBTZWMuIDcuMS4zIG9mIFJGQyAyNTc4LCBkdWUgdG8gdGhlCiAgIHVz
ZSBvZiBBYnN0cmFjdCBTeW50YXggTm90YXRpb24gT25lIChBU04uMSkgQmFzaWMgRW5jb2Rpbmcg
UnVsZXMKICAgKEJFUikgdGhlIGZpcnN0IHR3byBjb21wb25lbnRzIG9mIGFuICJPQkpFQ1QgSURF
TlRJRklFUiIgaGF2ZSBsaW1pdGVkCiAgIHZhbHVlIHJhbmdlcyBhbmQgYXJlIGVuY29kZWQgaW50
byBhIHNpbmdsZSBzdWItaWQgdmFsdWUgW1N0ZWVkbWFuXS4KICAgVGhlIEFTTi4xL0JFUiBzdGFu
ZGFyZHMgc3BlY2lmeSB0aGF0IHRoZSBudW1lcmljYWwgdmFsdWUgb2YgdGhlIGZpcnN0CiAgIHN1
Yi1pZGVudGlmaWVyIGlzIGRlcml2ZWQgZnJvbSB0aGUgdmFsdWVzIG9mIHRoZSBmaXJzdCB0d28g
Ik9CSkVDVAogICBJREVOVElGSUVSIiBjb21wb25lbnRzIGluIHRoZSB2YWx1ZSBiZWluZyBlbmNv
ZGVkLCB1c2luZyB0aGUgZm9ybXVsYToKICAgKFgqNDApICsgWSwgd2hlcmUgWCBpcyB0aGUgdmFs
dWUgb2YgdGhlIGZpcnN0IGNvbXBvbmVudCBhbmQgWSBpcyB0aGUKICAgdmFsdWUgb2YgdGhlIHNl
Y29uZCBjb21wb25lbnQuICBUaGlzIHBhY2tpbmcgb2YgdGhlIGZpcnN0IHR3bwogICBjb21wb25l
bnRzIHJlY29nbml6ZXMgdGhhdCBvbmx5IHRocmVlIHZhbHVlcyBhcmUgYWxsb2NhdGVkIGZyb20g
dGhlCiAgIHJvb3Qgbm9kZSwgYW5kIGF0IG1vc3QgMzkgc3Vic2VxdWVudCB2YWx1ZXMgZnJvbSBu
b2RlcyByZWFjaGVkIGJ5IFggPQogICAwIGFuZCBYID0gMS4gIFRoZSBtaW5pbXVtIGxlbmd0aCBv
ZiBhbiAiT0JKRUNUIElERU5USUZJRVIiIGlzIHR3bwogICBzdWItaWRzICh3aXRoIGEgemVyby12
YWx1ZWQgIk9CSkVDVCBJREVOVElGSUVSIiByZXByZXNlbnRlZCBhcwogICAiMC4wIikuICBObyBl
eHBsaWNpdCAibWluTGVuZ3RoIiByZXN0cmljdGlvbiAod2hpY2ggd291bGQgYmUgIjMiIHRvCiAg
IGFsbG93IGZvciB0aGUgbWluaW11bSBvZiB0d28gc3ViLWlkcyBhbmQgYSBzaW5nbGUgc2VwYXJh
dGluZyBkb3QpIGlzCiAgIHJlcXVpcmVkLCBzaW5jZSB0aGUgcGF0dGVybiBpdHNlbGYgZW5mb3Jj
ZXMgdGhpcyByZXN0cmljdGlvbi4KCgoKTmF0YWxlICAgICAgICAgICAgICAgICBFeHBpcmVzIFNl
cHRlbWJlciAxOSwgMjAwOSAgICAgICAgICAgICAgW1BhZ2UgMTJdCgwKSW50ZXJuZXQtRHJhZnQg
ICAgRXhwcmVzc2luZyBTTk1QIFNNSSBEYXRhdHlwZXMgaW4gWFNEICAgICAgICBNYXJjaCAyMDA5
CgoKNi4gIFNlY3VyaXR5IENvbnNpZGVyYXRpb25zCgogICBTZWN1cml0eSBjb25zaWRlcmF0aW9u
cyBmb3IgYW55IGdpdmVuIFNNSSBNSUIgbW9kdWxlIGFyZSBsaWtlbHkgdG8gYmUKICAgcmVsZXZh
bnQgdG8gYW55IFhTRC9YTUwgbWFwcGluZyBvZiB0aGF0IE1JQiBtb2R1bGU7IGhvd2V2ZXIsIHRo
ZQogICBtYXBwaW5nIGRlZmluZWQgaW4gdGhpcyBkb2N1bWVudCBkb2VzIG5vdCBpdHNlbGYgaW50
cm9kdWNlIGFueSBuZXcKICAgc2VjdXJpdHkgY29uc2lkZXJhdGlvbnMuCgogICBJZiBhbmQgd2hl
biBwcm94aWVzIG9yIGdhdGV3YXlzIGFyZSBkZXZlbG9wZWQgdG8gY29udmV5IFNOTVAKICAgbWFu
YWdlbWVudCBpbmZvcm1hdGlvbiBmcm9tIFNOTVAgYWdlbnRzIHRvIFhNTC1iYXNlZCBtYW5hZ2Vt
ZW50CiAgIGFwcGxpY2F0aW9ucyB2aWEgWFNEL1hNTCBtYXBwaW5nIG9mIE1JQiBtb2R1bGVzIGJh
c2VkIG9uIHRoaXMKICAgc3BlY2lmaWNhdGlvbiBhbmQgaXRzIHBsYW5uZWQgc2libGluZ3MsIHNw
ZWNpYWwgY2FyZSB3aWxsIG5lZWQgdG8gYmUKICAgdGFrZW4gdG8gZW5zdXJlIHRoYXQgYWxsIGFw
cGxpY2FibGUgU05NUCBzZWN1cml0eSBtZWNoYW5pc21zIGFyZQogICBzdXBwb3J0ZWQgaW4gYW4g
YXBwcm9wcmlhdGUgbWFubmVyIHlldCB0byBiZSBkZXRlcm1pbmVkLgoKCgoKCgoKCgoKCgoKCgoK
CgoKCgoKCgoKCgoKCgoKCgoKCgoKCk5hdGFsZSAgICAgICAgICAgICAgICAgRXhwaXJlcyBTZXB0
ZW1iZXIgMTksIDIwMDkgICAgICAgICAgICAgIFtQYWdlIDEzXQoMCkludGVybmV0LURyYWZ0ICAg
IEV4cHJlc3NpbmcgU05NUCBTTUkgRGF0YXR5cGVzIGluIFhTRCAgICAgICAgTWFyY2ggMjAwOQoK
CjcuICBJQU5BIENvbnNpZGVyYXRpb25zCgogICBJbiBhY2NvcmRhbmNlIHdpdGggUkZDIDM2ODgg
W1JGQzM2ODhdLCB3ZSByZXF1ZXN0IHRoZSBmb2xsb3dpbmcKICAgbmFtZXNwYWNlIGFuZCBzY2hl
bWEgcmVnaXN0cmF0aW9ucyBhc3NvY2lhdGVkIHdpdGggdGhpcyBkb2N1bWVudCBpbgogICB0aGUg
SUFOQSBYTUwgUmVnaXN0cnk6CgogICBvICB1cm46aWV0ZjpwYXJhbXM6eG1sOm5zOm9wc2F3Zzpz
bWk6YmFzZTpbdmVyc2lvbl9pZF0KCiAgIG8gIHVybjppZXRmOnBhcmFtczp4bWw6c2NoZW1hOm9w
c2F3ZzpzbWk6YmFzZTpbdmVyc2lvbl9pZF0KCjcuMS4gIFNNSSBCYXNlIERhdGF0eXBlcyBOYW1l
c3BhY2UgUmVnaXN0cmF0aW9uCgogICBUaGlzIGRvY3VtZW50IHJlZ2lzdGVycyBhIFVSSSBmb3Ig
dGhlIFNNSSBCYXNlIERhdGF0eXBlcyBYTUwKICAgbmFtZXNwYWNlIGluIHRoZSBJRVRGIFhNTCBy
ZWdpc3RyeS4gIEZvbGxvd2luZyB0aGUgZm9ybWF0IGluIFJGQwogICAzNjg4LCBJQU5BIGhhcyBt
YWRlIHRoZSBmb2xsb3dpbmcgcmVnaXN0cmF0aW9uOgoKICAgVVJJOiB1cm46aWV0ZjpwYXJhbXM6
eG1sOm5zOm9wc2F3ZzpzbWk6YmFzZToxLjAKCiAgIFJlZ2lzdHJhdGlvbiBDb250YWN0OiBUaGUg
SUVTRy4KCiAgIFhNTDogTi9BLCB0aGUgcmVxdWVzdGVkIFVSSSBpcyBhbiBYTUwgbmFtZXNwYWNl
LgoKNy4yLiAgU01JIEJhc2UgRGF0YXR5cGVzIFNjaGVtYSBSZWdpc3RyYXRpb24KCiAgIFRoaXMg
ZG9jdW1lbnQgcmVnaXN0ZXJzIGEgVVJJIGZvciB0aGUgU01JIEJhc2UgRGF0YXR5cGVzIFhNTCBz
Y2hlbWEKICAgaW4gdGhlIElFVEYgWE1MIHJlZ2lzdHJ5LiAgRm9sbG93aW5nIHRoZSBmb3JtYXQg
aW4gUkZDIDM2ODgsIElBTkEgaGFzCiAgIG1hZGUgdGhlIGZvbGxvd2luZyByZWdpc3RyYXRpb246
CgogICBVUkk6IHVybjppZXRmOnBhcmFtczp4bWw6c2NoZW1hOm9wc2F3ZzpzbWk6YmFzZToxLjAK
CiAgIFJlZ2lzdHJhdGlvbiBDb250YWN0OiBUaGUgSUVTRy4KCiAgIFhNTDogU2VjdGlvbiA0IG9m
IHRoaXMgZG9jdW1lbnQuCgoKCgoKCgoKCgoKCgoKCgoKCk5hdGFsZSAgICAgICAgICAgICAgICAg
RXhwaXJlcyBTZXB0ZW1iZXIgMTksIDIwMDkgICAgICAgICAgICAgIFtQYWdlIDE0XQoMCkludGVy
bmV0LURyYWZ0ICAgIEV4cHJlc3NpbmcgU05NUCBTTUkgRGF0YXR5cGVzIGluIFhTRCAgICAgICAg
TWFyY2ggMjAwOQoKCjguICBBY2tub3dsZWRnZW1lbnRzCgogICBEYXZlIEhhcnJpbmd0b24gcHJv
dmlkZWQgc3RyYXRlZ2ljIGFuZCB0ZWNobmljYWwgbGVhZGVyc2hpcCB0byB0aGUKICAgdGVhbSB3
aGljaCBkZXZlbG9wZWQgdGhpcyBwYXJ0aWN1bGFyIHNwZWNpZmljYXRpb24uICBZYW4gTGkgZGlk
IG11Y2gKICAgb2YgdGhlIHJlc2VhcmNoIGludG8gZXhpc3RpbmcgYXBwcm9hY2hlcyB0aGF0IHdh
cyB1c2VkIGFzIGEgYmFzZWxpbmUKICAgZm9yIHRoZSByZWNvbW1lbmRhdGlvbnMgaW4gdGhpcyBw
YXJ0aWN1bGFyIHNwZWNpZmljYXRpb24uCgogICBUaGlzIGRvY3VtZW50IG93ZXMgbXVjaCB0byBk
cmFmdC1yb21hc2NhbnUtbmV0Y29uZi1kYXRhdHlwZXMteHggYW5kCiAgIHRvIG1hbnkgb3RoZXIg
c291cmNlcyAoaW5jbHVkaW5nIGxpYnNtaSBhbmQgZ3JvdXAgZGlzY3Vzc2lvbnMgb24gdGhlCiAg
IE5FVENPTkYgbWFpbGluZyBsaXN0cykgZGV2ZWxvcGVkIGJ5IHRob3NlIHdobyBoYXZlIHJlc2Vh
cmNoZWQgYW5kCiAgIHB1Ymxpc2hlZCBjYW5kaWRhdGUgbWFwcGluZ3Mgb2YgU01JIGRhdGF0eXBl
cyB0byBYU0QuCgogICBJbmRpdmlkdWFscyB3aG8gcGFydGljaXBhdGVkIGluIHZhcmlvdXMgZGlz
Y3Vzc2lvbnMgb2YgdGhpcyB0b3BpYyBhdAogICBJRVRGIG1lZXRpbmdzIGFuZCBvbiBJRVRGIG1h
aWxpbmcgbGlzdHMgaW5jbHVkZTogUmF5IEF0YXJhc2hpLAogICBZb3NoaWZ1bWkgQXRhcmFzaGks
IEFuZHkgQmllcm1hbiwgU2hhcm9uIENoaXNob2xtLCBBdnJpIERvcmlhLCBNYXJrCiAgIEVsbGlz
b24sIFJvYiBFbm5lcywgTWVobWV0IEVyc3VlLCBEYXZpZCBIYXJyaW5ndG9uLCBBbGZyZWQgSGlu
ZXMsCiAgIEVsaW90IExlYXIsIENocmlzIExvbnZpY2ssIEZheWUgTHksIFJhbmR5IFByZXN1aG4s
IEp1ZXJnZW4KICAgU2Nob2Vud2FlbGRlciwgQW5kcmUgV2VzdGVyaW5lbiwgYW5kIEJlcnQgV2lq
bmVuLgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgpOYXRhbGUgICAgICAgICAgICAg
ICAgIEV4cGlyZXMgU2VwdGVtYmVyIDE5LCAyMDA5ICAgICAgICAgICAgICBbUGFnZSAxNV0KDApJ
bnRlcm5ldC1EcmFmdCAgICBFeHByZXNzaW5nIFNOTVAgU01JIERhdGF0eXBlcyBpbiBYU0QgICAg
ICAgIE1hcmNoIDIwMDkKCgo5LiAgUmVmZXJlbmNlcwoKOS4xLiAgTm9ybWF0aXZlIFJlZmVyZW5j
ZXMKCiAgIFtSRkMxMTU1XSAgUm9zZSwgTS4gYW5kIEsuIE1jQ2xvZ2hyaWUsICJTdHJ1Y3R1cmUg
YW5kIGlkZW50aWZpY2F0aW9uCiAgICAgICAgICAgICAgb2YgbWFuYWdlbWVudCBpbmZvcm1hdGlv
biBmb3IgVENQL0lQLWJhc2VkIGludGVybmV0cyIsCiAgICAgICAgICAgICAgU1REIDE2LCBSRkMg
MTE1NSwgTWF5IDE5OTAuCgogICBbUkZDMjExOV0gIEJyYWRuZXIsIHMuLCAiS2V5IHdvcmRzIGZv
ciB1c2UgaW4gUkZDcyB0byBJbmRpY2F0ZQogICAgICAgICAgICAgIFJlcXVpcmVtZW50IExldmVs
cyIsIEJDUCAxNCwgUkZDIDIxMTksIE1hcmNoIDE5OTcuCgogICBbUkZDMjU3OF0gIE1jQ2xvZ2hy
aWUsIEsuLCBFZC4sIFBlcmtpbnMsIEQuLCBFZC4sIGFuZCBKLgogICAgICAgICAgICAgIFNjaG9l
bndhZWxkZXIsIEVkLiwgIlN0cnVjdHVyZSBvZiBNYW5hZ2VtZW50IEluZm9ybWF0aW9uCiAgICAg
ICAgICAgICAgVmVyc2lvbiAyIChTTUl2MikiLCBTVEQgNTgsIFJGQyAyNTc4LCBBcHJpbCAxOTk5
LgoKICAgW1JGQzM1ODRdICBGcnllLCBSLiwgTGV2aSwgRC4sIFJvdXRoaWVyLCBTLiwgYW5kIEIu
IFdpam5lbiwKICAgICAgICAgICAgICAiQ29leGlzdGVuY2UgYmV0d2VlbiBWZXJzaW9uIDEsIFZl
cnNpb24gMiwgYW5kIFZlcnNpb24gMwogICAgICAgICAgICAgIG9mIHRoZSBJbnRlcm5ldC1zdGFu
ZGFyZCBOZXR3b3JrIE1hbmFnZW1lbnQgRnJhbWV3b3JrIiwKICAgICAgICAgICAgICBCQ1AgNzQs
IFJGQyAzNTg0LCBBdWd1c3QgMjAwMy4KCjkuMi4gIEluZm9ybWF0aW9uYWwgUmVmZXJlbmNlcwoK
ICAgW1JGQzI1NzldICBNY0Nsb2docmllLCBLLiwgUGVya2lucywgRC4sIGFuZCBKLiBTY2hvZW53
YWVsZGVyLAogICAgICAgICAgICAgICJUZXh0dWFsIENvbnZlbnRpb25zIGZvciBTTUl2MiIsIFNU
RCA1OCwgUkZDIDI1NzksCiAgICAgICAgICAgICAgQXByaWwgMTk5OS4KCiAgIFtSRkMzNjg4XSAg
TWVhbGxpbmcsIE0uLCAiVGhlIElFVEYgWE1MIFJlZ2lzdHJ5IiwgQkNQIDgxLCBSRkMgMzY4OCwK
ICAgICAgICAgICAgICBKYW51YXJ5IDIwMDQuCgogICBbU3RlZWRtYW5dCiAgICAgICAgICAgICAg
U3RlZWRtYW4sIEQuLCAiQVNOLjE6IFRoZSBUdXRvcmlhbCBhbmQgUmVmZXJlbmNlIi4KCiAgIFtY
TUxdICAgICAgV29ybGQgV2lkZSBXZWIgQ29uc29ydGl1bSwgIkV4dGVuc2libGUgTWFya3VwIExh
bmd1YWdlCiAgICAgICAgICAgICAgKFhNTCkgMS4wIiwgVzNDIFhNTCwgRmVicnVhcnkgMTk5OCwK
ICAgICAgICAgICAgICA8aHR0cDovL3d3dy53My5vcmcvVFIvMTk5OC9SRUMteG1sLTE5OTgwMjEw
Pi4KCiAgIFtYTUxTY2hlbWFdCiAgICAgICAgICAgICAgV29ybGQgV2lkZSBXZWIgQ29uc29ydGl1
bSwgIlhNTCBTY2hlbWEgUGFydCAxOiBTdHJ1Y3R1cmVzCiAgICAgICAgICAgICAgU2Vjb25kIEVk
aXRpb24iLCBXM0MgWE1MIFNjaGVtYSwgT2N0b2JlciAyMDA0LAogICAgICAgICAgICAgIDxodHRw
Oi8vd3d3LnczLm9yZy9UUi94bWxzY2hlbWEtMS8+LgoKICAgW1hTRERhdGF0eXBlc10KICAgICAg
ICAgICAgICBXb3JsZCBXaWRlIFdlYiBDb25zb3J0aXVtLCAiWE1MIFNjaGVtYSBQYXJ0IDI6IERh
dGF0eXBlcwogICAgICAgICAgICAgIFNlY29uZCBFZGl0aW9uIiwgVzNDIFhNTCBTY2hlbWEsIE9j
dG9iZXIgMjAwNCwKICAgICAgICAgICAgICA8aHR0cDovL3d3dy53My5vcmcvVFIveG1sc2NoZW1h
LTIvPi4KCgoKCgoKTmF0YWxlICAgICAgICAgICAgICAgICBFeHBpcmVzIFNlcHRlbWJlciAxOSwg
MjAwOSAgICAgICAgICAgICAgW1BhZ2UgMTZdCgwKSW50ZXJuZXQtRHJhZnQgICAgRXhwcmVzc2lu
ZyBTTk1QIFNNSSBEYXRhdHlwZXMgaW4gWFNEICAgICAgICBNYXJjaCAyMDA5CgoKQXV0aG9yJ3Mg
QWRkcmVzcwoKICAgQm9iIE5hdGFsZQogICBNSVRSRQogICA3NTE1IENvbHNoaXJlIERyCiAgIE1T
IEg0MDUKICAgTWNMZWFuLCBWQSAgMjIxMDIKICAgVVNBCgogICBQaG9uZTogKzEgNzAzLTk4My0y
NTA1CiAgIEVtYWlsOiBybmF0YWxlQG1pdHJlLm9yZwoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoK
CgoKCgoKCgoKCgoKCgoKTmF0YWxlICAgICAgICAgICAgICAgICBFeHBpcmVzIFNlcHRlbWJlciAx
OSwgMjAwOSAgICAgICAgICAgICAgW1BhZ2UgMTddCgwKCg==

--_002_17969D855F28964C88D177D45B6CDF110210414097IMCMBX2MITREO_--

From SCHISHOL@nortel.com  Mon Mar 23 05:53:46 2009
Return-Path: <SCHISHOL@nortel.com>
X-Original-To: opsawg@core3.amsl.com
Delivered-To: opsawg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 206833A6A1D for <opsawg@core3.amsl.com>; Mon, 23 Mar 2009 05:53:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id A4ve6OOdnuWp for <opsawg@core3.amsl.com>; Mon, 23 Mar 2009 05:53:45 -0700 (PDT)
Received: from zcars04e.nortel.com (zcars04e.nortel.com [47.129.242.56]) by core3.amsl.com (Postfix) with ESMTP id 0AF3B3A69D7 for <opsawg@ietf.org>; Mon, 23 Mar 2009 05:53:44 -0700 (PDT)
Received: from zcarhxm2.corp.nortel.com (zcarhxm2.corp.nortel.com [47.129.230.99]) by zcars04e.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id n2NCs5I23954; Mon, 23 Mar 2009 12:54:05 GMT
x-mimeole: Produced By Microsoft Exchange V6.5
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 Mar 2009 08:54:23 -0400
Message-ID: <713043CE8B8E1348AF3C546DBE02C1B418C6CA06@zcarhxm2.corp.nortel.com>
In-Reply-To: <20090201133347.GA18098@elstar.local>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [OPSAWG] Proposed update to syslog Alarm
Thread-Index: AcmEcb7ZYjblRLSWR1uAQhSEqN4VPgnQD25Q
References: <713043CE8B8E1348AF3C546DBE02C1B41824B2E0@zcarhxm2.corp.nortel.com> <20090201133347.GA18098@elstar.local>
From: "Sharon Chisholm" <schishol@nortel.com>
To: <j.schoenwaelder@jacobs-university.de>
Cc: opsawg@ietf.org
Subject: Re: [OPSAWG] Proposed update to syslog Alarm
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Mar 2009 12:53:46 -0000

Hi

Comments inline. Again, thanks for the review. If we can resolve the
outstanding issues, I'll post the update when updates are permitted
again.=20

Sharon

-----Original Message-----
From: Juergen Schoenwaelder
[mailto:j.schoenwaelder@jacobs-university.de]=20
Sent: Sunday, February 01, 2009 8:34 AM
To: Chisholm, Sharon (CAR:ZZ00)
Cc: opsawg@ietf.org
Subject: Re: [OPSAWG] Proposed update to syslog Alarm

On Fri, Jan 30, 2009 at 11:18:04AM -0500, Sharon Chisholm wrote:
=20
> Attached is the propose update to the Syslog Alarm draft as a result=20
> of comments received during working group last call. I believe it=20
> addresses all known issues.
>=20
> Please let me know if you have any comments or corrections and I can=20
> make any necessary changes before posting this as version -02.

- Capitalize the section 1.1 heading or get rid of the heading
  and make the two sentences part of section 1.
<sharon>
I suspect that since this section is so short, the merge makes the most
sense
</sharon>

- You sometimes use "resource" and sometimes "alarmResource",
  please pick one an be consistent.
<sharon>
Oops. The latter is residue since we just changed it to resource. I have
found and replaced 4 instances.
</sharon>

- Section 3.6 is confusing - we now have three resource identifiers:

  (1) resource (or alarmResource)

      The specification leaves it open what it contains; so this value
      is really just for humans to read.

  (2) resourceOID

      This SD-ID contains an OID, namely the value of the
      alarmActiveResourceId MIB object. This SD-ID suffers from the
      problem that it does not carry SNMP context information and is
      thus ambiguous.

  (3) resourceURI

      This is defined to hold an SNMP URI. This solved the missing
      SNMP context problem of resourceOID but fires back in the sense
      that it can't carry other URIs.

  My proposal is to keep (1), delete (2), and to change (3) such that
  it can carry arbitrary URIs and can appear multiple times. If an
  alarmActiveResourceId MIB object exists, the value should be reported
  using the SNMP URI format in an resourceURI SD-ID.
<sharon>
I don't think people actually understand URI in SNMP, so this is why I
prefer the OID one, even with its limitations. My preference would be to
keep all three.
</sharon>

- In the example, I find it strange to consider "su root" a resource.
  For me, the resource raising the alarm is a subsystem of the OS
  dealing with authorization decisions. Also the message in the
  message part is not likely to be generated when you have an
  unauthorizedAccessAttempt. Please make the example more realistic.
<sharon>
You had mentioned this before, but I was not sure what else to put and I
could not find a reply to my request for more information so I left it
as is.  Your second sentence here is helpful. (Note that this is the
example from the base syslog protocol and we are only extending it, so
the argument of it not being realistic is a bit moot potentially). So, I
could say something like "aaa" or "security system" and that would work?
</sharon>

From j.schoenwaelder@jacobs-university.de  Mon Mar 23 06:51:49 2009
Return-Path: <j.schoenwaelder@jacobs-university.de>
X-Original-To: opsawg@core3.amsl.com
Delivered-To: opsawg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4A1F23A68AE for <opsawg@core3.amsl.com>; Mon, 23 Mar 2009 06:51:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Level: 
X-Spam-Status: No, score=-2.106 tagged_above=-999 required=5 tests=[AWL=0.143,  BAYES_00=-2.599, HELO_EQ_DE=0.35]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ebKP8zngCpdt for <opsawg@core3.amsl.com>; Mon, 23 Mar 2009 06:51:48 -0700 (PDT)
Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) by core3.amsl.com (Postfix) with ESMTP id 1782B3A685C for <opsawg@ietf.org>; Mon, 23 Mar 2009 06:51:48 -0700 (PDT)
Received: from localhost (demetrius3.jacobs-university.de [212.201.44.48]) by hermes.jacobs-university.de (Postfix) with ESMTP id C4B51C0018; Mon, 23 Mar 2009 14:52:37 +0100 (CET)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius3.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id S2EoOOaTgRGM; Mon, 23 Mar 2009 14:52:36 +0100 (CET)
Received: from elstar.local (elstar.iuhb02.iu-bremen.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id DE676C0017; Mon, 23 Mar 2009 14:52:36 +0100 (CET)
Received: by elstar.local (Postfix, from userid 501) id 58A07A30841; Mon, 23 Mar 2009 14:52:24 +0100 (CET)
Date: Mon, 23 Mar 2009 14:52:24 +0100
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: Sharon Chisholm <schishol@nortel.com>
Message-ID: <20090323135224.GA14442@elstar.local>
Mail-Followup-To: Sharon Chisholm <schishol@nortel.com>, "opsawg@ietf.org" <opsawg@ietf.org>
References: <713043CE8B8E1348AF3C546DBE02C1B41824B2E0@zcarhxm2.corp.nortel.com> <20090201133347.GA18098@elstar.local> <713043CE8B8E1348AF3C546DBE02C1B418C6CA06@zcarhxm2.corp.nortel.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <713043CE8B8E1348AF3C546DBE02C1B418C6CA06@zcarhxm2.corp.nortel.com>
User-Agent: Mutt/1.5.19 (2009-01-05)
Cc: "opsawg@ietf.org" <opsawg@ietf.org>
Subject: Re: [OPSAWG] Proposed update to syslog Alarm
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Mar 2009 13:51:49 -0000

On Mon, Mar 23, 2009 at 01:54:23PM +0100, Sharon Chisholm wrote:
 
> - Section 3.6 is confusing - we now have three resource identifiers:
> 
>   (1) resource (or alarmResource)
> 
>       The specification leaves it open what it contains; so this value
>       is really just for humans to read.
> 
>   (2) resourceOID
> 
>       This SD-ID contains an OID, namely the value of the
>       alarmActiveResourceId MIB object. This SD-ID suffers from the
>       problem that it does not carry SNMP context information and is
>       thus ambiguous.
> 
>   (3) resourceURI
> 
>       This is defined to hold an SNMP URI. This solved the missing
>       SNMP context problem of resourceOID but fires back in the sense
>       that it can't carry other URIs.
> 
>   My proposal is to keep (1), delete (2), and to change (3) such that
>   it can carry arbitrary URIs and can appear multiple times. If an
>   alarmActiveResourceId MIB object exists, the value should be reported
>   using the SNMP URI format in an resourceURI SD-ID.
> <sharon>
> I don't think people actually understand URI in SNMP, so this is why I
> prefer the OID one, even with its limitations. My preference would be to
> keep all three.
> </sharon>

Those who understand SNMP know that an OID without context is broken.
I will keep pointing out this defect until it is fixed or higher
powers declare that RFC 3411 section 3.3.1 is not relevant anymore.

I believe using SNMP URIs is the easiest solution but I am fine if
people want to engineer something different as long as the solution
does take care of RFC 3411 section 3.3.1.

/js

-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: +49 421 200 3587         Campus Ring 1, 28759 Bremen, Germany
Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>

From SCHISHOL@nortel.com  Mon Mar 23 09:03:58 2009
Return-Path: <SCHISHOL@nortel.com>
X-Original-To: opsawg@core3.amsl.com
Delivered-To: opsawg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C47D928C13D for <opsawg@core3.amsl.com>; Mon, 23 Mar 2009 09:03:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9RvYn2OMaJaS for <opsawg@core3.amsl.com>; Mon, 23 Mar 2009 09:03:57 -0700 (PDT)
Received: from zrtps0kp.nortel.com (zrtps0kp.nortel.com [47.140.192.56]) by core3.amsl.com (Postfix) with ESMTP id 7E3123A6AB0 for <opsawg@ietf.org>; Mon, 23 Mar 2009 09:03:57 -0700 (PDT)
Received: from zcarhxm2.corp.nortel.com (zcarhxm2.corp.nortel.com [47.129.230.99]) by zrtps0kp.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id n2NG4hl18044; Mon, 23 Mar 2009 16:04:44 GMT
x-mimeole: Produced By Microsoft Exchange V6.5
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 Mar 2009 12:04:41 -0400
Message-ID: <713043CE8B8E1348AF3C546DBE02C1B418C6CEAD@zcarhxm2.corp.nortel.com>
In-Reply-To: <20090323135224.GA14442@elstar.local>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [OPSAWG] Proposed update to syslog Alarm
Thread-Index: AcmrvqRI8fVQWI1aTYKeOwxZH3qdcwAElu5Q
References: <713043CE8B8E1348AF3C546DBE02C1B41824B2E0@zcarhxm2.corp.nortel.com> <20090201133347.GA18098@elstar.local> <713043CE8B8E1348AF3C546DBE02C1B418C6CA06@zcarhxm2.corp.nortel.com> <20090323135224.GA14442@elstar.local>
From: "Sharon Chisholm" <schishol@nortel.com>
To: "Juergen Schoenwaelder" <j.schoenwaelder@jacobs-university.de>
Cc: opsawg@ietf.org
Subject: Re: [OPSAWG] Proposed update to syslog Alarm
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Mar 2009 16:03:58 -0000

Hi

So, are you OK with leaving all three in the document?

Sharon=20

-----Original Message-----
From: Juergen Schoenwaelder
[mailto:j.schoenwaelder@jacobs-university.de]=20
Sent: Monday, March 23, 2009 9:52 AM
To: Chisholm, Sharon (CAR:ZZ00)
Cc: opsawg@ietf.org
Subject: Re: [OPSAWG] Proposed update to syslog Alarm

On Mon, Mar 23, 2009 at 01:54:23PM +0100, Sharon Chisholm wrote:
=20
> - Section 3.6 is confusing - we now have three resource identifiers:
>=20
>   (1) resource (or alarmResource)
>=20
>       The specification leaves it open what it contains; so this value
>       is really just for humans to read.
>=20
>   (2) resourceOID
>=20
>       This SD-ID contains an OID, namely the value of the
>       alarmActiveResourceId MIB object. This SD-ID suffers from the
>       problem that it does not carry SNMP context information and is
>       thus ambiguous.
>=20
>   (3) resourceURI
>=20
>       This is defined to hold an SNMP URI. This solved the missing
>       SNMP context problem of resourceOID but fires back in the sense
>       that it can't carry other URIs.
>=20
>   My proposal is to keep (1), delete (2), and to change (3) such that
>   it can carry arbitrary URIs and can appear multiple times. If an
>   alarmActiveResourceId MIB object exists, the value should be
reported
>   using the SNMP URI format in an resourceURI SD-ID.
> <sharon>
> I don't think people actually understand URI in SNMP, so this is why I

> prefer the OID one, even with its limitations. My preference would be=20
> to keep all three.
> </sharon>

Those who understand SNMP know that an OID without context is broken.
I will keep pointing out this defect until it is fixed or higher powers
declare that RFC 3411 section 3.3.1 is not relevant anymore.

I believe using SNMP URIs is the easiest solution but I am fine if
people want to engineer something different as long as the solution does
take care of RFC 3411 section 3.3.1.

/js

--=20
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: +49 421 200 3587         Campus Ring 1, 28759 Bremen, Germany
Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>

From j.schoenwaelder@jacobs-university.de  Mon Mar 23 09:53:02 2009
Return-Path: <j.schoenwaelder@jacobs-university.de>
X-Original-To: opsawg@core3.amsl.com
Delivered-To: opsawg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 189FA3A690D for <opsawg@core3.amsl.com>; Mon, 23 Mar 2009 09:53:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.108
X-Spam-Level: 
X-Spam-Status: No, score=-2.108 tagged_above=-999 required=5 tests=[AWL=0.141,  BAYES_00=-2.599, HELO_EQ_DE=0.35]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H9xFAOOnu1oO for <opsawg@core3.amsl.com>; Mon, 23 Mar 2009 09:53:01 -0700 (PDT)
Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) by core3.amsl.com (Postfix) with ESMTP id 40A0828C1D2 for <opsawg@ietf.org>; Mon, 23 Mar 2009 09:53:01 -0700 (PDT)
Received: from localhost (demetrius4.jacobs-university.de [212.201.44.49]) by hermes.jacobs-university.de (Postfix) with ESMTP id 1DB57C0020; Mon, 23 Mar 2009 17:53:51 +0100 (CET)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius4.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id XaT7jBmQjeAP; Mon, 23 Mar 2009 17:53:50 +0100 (CET)
Received: from elstar.local (elstar.iuhb02.iu-bremen.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id 16EEBC0007; Mon, 23 Mar 2009 17:53:50 +0100 (CET)
Received: by elstar.local (Postfix, from userid 501) id 8A801A33D0B; Mon, 23 Mar 2009 17:53:37 +0100 (CET)
Date: Mon, 23 Mar 2009 17:53:37 +0100
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: Sharon Chisholm <schishol@nortel.com>
Message-ID: <20090323165337.GA15855@elstar.local>
Mail-Followup-To: Sharon Chisholm <schishol@nortel.com>, "opsawg@ietf.org" <opsawg@ietf.org>
References: <713043CE8B8E1348AF3C546DBE02C1B41824B2E0@zcarhxm2.corp.nortel.com> <20090201133347.GA18098@elstar.local> <713043CE8B8E1348AF3C546DBE02C1B418C6CA06@zcarhxm2.corp.nortel.com> <20090323135224.GA14442@elstar.local> <713043CE8B8E1348AF3C546DBE02C1B418C6CEAD@zcarhxm2.corp.nortel.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <713043CE8B8E1348AF3C546DBE02C1B418C6CEAD@zcarhxm2.corp.nortel.com>
User-Agent: Mutt/1.5.19 (2009-01-05)
Cc: "opsawg@ietf.org" <opsawg@ietf.org>
Subject: Re: [OPSAWG] Proposed update to syslog Alarm
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Mar 2009 16:53:02 -0000

On Mon, Mar 23, 2009 at 05:04:41PM +0100, Sharon Chisholm wrote:
 
> So, are you OK with leaving all three in the document?

Once again, resourceOID is broken. If you leave it, you have to fix
it. My preference would be to either (a) use the SNMP URI scheme or
(b) use the the SNMP to SYSLOG mappings also defined as part of the
OPSAWG working group. If you plan to invent a third solution, make
sure you have strong arguments; I prefer to reuse existing solutions.

/js

-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: +49 421 200 3587         Campus Ring 1, 28759 Bremen, Germany
Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>

From ietfdbh@comcast.net  Mon Mar 23 12:01:14 2009
Return-Path: <ietfdbh@comcast.net>
X-Original-To: opsawg@core3.amsl.com
Delivered-To: opsawg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A0D8B3A6B32 for <opsawg@core3.amsl.com>; Mon, 23 Mar 2009 12:01:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BpE1A7y1-DQj for <opsawg@core3.amsl.com>; Mon, 23 Mar 2009 12:01:13 -0700 (PDT)
Received: from QMTA06.westchester.pa.mail.comcast.net (qmta06.westchester.pa.mail.comcast.net [76.96.62.56]) by core3.amsl.com (Postfix) with ESMTP id 64CB728C212 for <opsawg@ietf.org>; Mon, 23 Mar 2009 12:00:50 -0700 (PDT)
Received: from OMTA14.westchester.pa.mail.comcast.net ([76.96.62.60]) by QMTA06.westchester.pa.mail.comcast.net with comcast id WZwS1b0031HzFnQ56j1YXM; Mon, 23 Mar 2009 19:01:32 +0000
Received: from Harrington73653 ([130.129.67.244]) by OMTA14.westchester.pa.mail.comcast.net with comcast id Wj1T1b0055GCXKW3aj1Wti; Mon, 23 Mar 2009 19:01:39 +0000
From: "David Harrington" <ietfdbh@comcast.net>
To: "'Sharon Chisholm'" <schishol@nortel.com>, "'Juergen Schoenwaelder'" <j.schoenwaelder@jacobs-university.de>
References: <713043CE8B8E1348AF3C546DBE02C1B41824B2E0@zcarhxm2.corp.nortel.com><20090201133347.GA18098@elstar.local><713043CE8B8E1348AF3C546DBE02C1B418C6CA06@zcarhxm2.corp.nortel.com><20090323135224.GA14442@elstar.local> <713043CE8B8E1348AF3C546DBE02C1B418C6CEAD@zcarhxm2.corp.nortel.com>
Date: Mon, 23 Mar 2009 12:01:25 -0700
Message-ID: <01b601c9abe9$cb128cd0$f4438182@china.huawei.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <713043CE8B8E1348AF3C546DBE02C1B418C6CEAD@zcarhxm2.corp.nortel.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
Thread-Index: AcmrvqRI8fVQWI1aTYKeOwxZH3qdcwAElu5QAAYvtKA=
Cc: opsawg@ietf.org
Subject: Re: [OPSAWG] Proposed update to syslog Alarm
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Mar 2009 19:01:14 -0000

no.

dbh 

> -----Original Message-----
> From: opsawg-bounces@ietf.org 
> [mailto:opsawg-bounces@ietf.org] On Behalf Of Sharon Chisholm
> Sent: Monday, March 23, 2009 9:05 AM
> To: Juergen Schoenwaelder
> Cc: opsawg@ietf.org
> Subject: Re: [OPSAWG] Proposed update to syslog Alarm
> 
> Hi
> 
> So, are you OK with leaving all three in the document?
> 
> Sharon 
> 
> -----Original Message-----
> From: Juergen Schoenwaelder
> [mailto:j.schoenwaelder@jacobs-university.de] 
> Sent: Monday, March 23, 2009 9:52 AM
> To: Chisholm, Sharon (CAR:ZZ00)
> Cc: opsawg@ietf.org
> Subject: Re: [OPSAWG] Proposed update to syslog Alarm
> 
> On Mon, Mar 23, 2009 at 01:54:23PM +0100, Sharon Chisholm wrote:
>  
> > - Section 3.6 is confusing - we now have three resource
identifiers:
> > 
> >   (1) resource (or alarmResource)
> > 
> >       The specification leaves it open what it contains; so 
> this value
> >       is really just for humans to read.
> > 
> >   (2) resourceOID
> > 
> >       This SD-ID contains an OID, namely the value of the
> >       alarmActiveResourceId MIB object. This SD-ID suffers from
the
> >       problem that it does not carry SNMP context information and
is
> >       thus ambiguous.
> > 
> >   (3) resourceURI
> > 
> >       This is defined to hold an SNMP URI. This solved the missing
> >       SNMP context problem of resourceOID but fires back in 
> the sense
> >       that it can't carry other URIs.
> > 
> >   My proposal is to keep (1), delete (2), and to change (3) 
> such that
> >   it can carry arbitrary URIs and can appear multiple times. If an
> >   alarmActiveResourceId MIB object exists, the value should be
> reported
> >   using the SNMP URI format in an resourceURI SD-ID.
> > <sharon>
> > I don't think people actually understand URI in SNMP, so 
> this is why I
> 
> > prefer the OID one, even with its limitations. My 
> preference would be 
> > to keep all three.
> > </sharon>
> 
> Those who understand SNMP know that an OID without context is
broken.
> I will keep pointing out this defect until it is fixed or 
> higher powers
> declare that RFC 3411 section 3.3.1 is not relevant anymore.
> 
> I believe using SNMP URIs is the easiest solution but I am fine if
> people want to engineer something different as long as the 
> solution does
> take care of RFC 3411 section 3.3.1.
> 
> /js
> 
> -- 
> Juergen Schoenwaelder           Jacobs University Bremen gGmbH
> Phone: +49 421 200 3587         Campus Ring 1, 28759 Bremen, Germany
> Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>
> _______________________________________________
> OPSAWG mailing list
> OPSAWG@ietf.org
> https://www.ietf.org/mailman/listinfo/opsawg
> 


From ietfdbh@comcast.net  Mon Mar 23 12:01:26 2009
Return-Path: <ietfdbh@comcast.net>
X-Original-To: opsawg@core3.amsl.com
Delivered-To: opsawg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4E2F728C24D for <opsawg@core3.amsl.com>; Mon, 23 Mar 2009 12:01:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r8FMqsi3lJZh for <opsawg@core3.amsl.com>; Mon, 23 Mar 2009 12:01:25 -0700 (PDT)
Received: from QMTA09.westchester.pa.mail.comcast.net (qmta09.westchester.pa.mail.comcast.net [76.96.62.96]) by core3.amsl.com (Postfix) with ESMTP id E5EBE28C0E5 for <opsawg@ietf.org>; Mon, 23 Mar 2009 12:01:01 -0700 (PDT)
Received: from OMTA14.westchester.pa.mail.comcast.net ([76.96.62.60]) by QMTA09.westchester.pa.mail.comcast.net with comcast id Wa0e1b0031HzFnQ59j1tga; Mon, 23 Mar 2009 19:01:53 +0000
Received: from Harrington73653 ([130.129.67.244]) by OMTA14.westchester.pa.mail.comcast.net with comcast id Wj1T1b0055GCXKW3aj1izP; Mon, 23 Mar 2009 19:01:51 +0000
From: "David Harrington" <ietfdbh@comcast.net>
To: "'Juergen Schoenwaelder'" <j.schoenwaelder@jacobs-university.de>, "'Sharon Chisholm'" <schishol@nortel.com>
References: <713043CE8B8E1348AF3C546DBE02C1B41824B2E0@zcarhxm2.corp.nortel.com><20090201133347.GA18098@elstar.local><713043CE8B8E1348AF3C546DBE02C1B418C6CA06@zcarhxm2.corp.nortel.com> <20090323135224.GA14442@elstar.local>
Date: Mon, 23 Mar 2009 12:01:41 -0700
Message-ID: <01b701c9abe9$d2243e10$f4438182@china.huawei.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <20090323135224.GA14442@elstar.local>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
Thread-Index: AcmrvqNhbSnLhCN1R+6f39F5PVfSbQAKyKLA
Cc: opsawg@ietf.org
Subject: Re: [OPSAWG] Proposed update to syslog Alarm
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Mar 2009 19:01:26 -0000

+1

dbh 

> -----Original Message-----
> From: opsawg-bounces@ietf.org 
> [mailto:opsawg-bounces@ietf.org] On Behalf Of Juergen Schoenwaelder
> Sent: Monday, March 23, 2009 6:52 AM
> To: Sharon Chisholm
> Cc: opsawg@ietf.org
> Subject: Re: [OPSAWG] Proposed update to syslog Alarm
> 
> On Mon, Mar 23, 2009 at 01:54:23PM +0100, Sharon Chisholm wrote:
>  
> > - Section 3.6 is confusing - we now have three resource
identifiers:
> > 
> >   (1) resource (or alarmResource)
> > 
> >       The specification leaves it open what it contains; so 
> this value
> >       is really just for humans to read.
> > 
> >   (2) resourceOID
> > 
> >       This SD-ID contains an OID, namely the value of the
> >       alarmActiveResourceId MIB object. This SD-ID suffers from
the
> >       problem that it does not carry SNMP context information and
is
> >       thus ambiguous.
> > 
> >   (3) resourceURI
> > 
> >       This is defined to hold an SNMP URI. This solved the missing
> >       SNMP context problem of resourceOID but fires back in 
> the sense
> >       that it can't carry other URIs.
> > 
> >   My proposal is to keep (1), delete (2), and to change (3) 
> such that
> >   it can carry arbitrary URIs and can appear multiple times. If an
> >   alarmActiveResourceId MIB object exists, the value should 
> be reported
> >   using the SNMP URI format in an resourceURI SD-ID.
> > <sharon>
> > I don't think people actually understand URI in SNMP, so 
> this is why I
> > prefer the OID one, even with its limitations. My 
> preference would be to
> > keep all three.
> > </sharon>
> 
> Those who understand SNMP know that an OID without context is
broken.
> I will keep pointing out this defect until it is fixed or higher
> powers declare that RFC 3411 section 3.3.1 is not relevant anymore.
> 
> I believe using SNMP URIs is the easiest solution but I am fine if
> people want to engineer something different as long as the solution
> does take care of RFC 3411 section 3.3.1.
> 
> /js
> 
> -- 
> Juergen Schoenwaelder           Jacobs University Bremen gGmbH
> Phone: +49 421 200 3587         Campus Ring 1, 28759 Bremen, Germany
> Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>
> _______________________________________________
> OPSAWG mailing list
> OPSAWG@ietf.org
> https://www.ietf.org/mailman/listinfo/opsawg
> 


From j.schoenwaelder@jacobs-university.de  Thu Mar 26 09:56:39 2009
Return-Path: <j.schoenwaelder@jacobs-university.de>
X-Original-To: opsawg@core3.amsl.com
Delivered-To: opsawg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 61AD028C0ED for <opsawg@core3.amsl.com>; Thu, 26 Mar 2009 09:56:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.894
X-Spam-Level: 
X-Spam-Status: No, score=-0.894 tagged_above=-999 required=5 tests=[AWL=-1.059, BAYES_40=-0.185, HELO_EQ_DE=0.35]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id N9rFOgQQYROc for <opsawg@core3.amsl.com>; Thu, 26 Mar 2009 09:56:38 -0700 (PDT)
Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) by core3.amsl.com (Postfix) with ESMTP id 4AE5C28C154 for <opsawg@ietf.org>; Thu, 26 Mar 2009 09:56:38 -0700 (PDT)
Received: from localhost (demetrius2.jacobs-university.de [212.201.44.47]) by hermes.jacobs-university.de (Postfix) with ESMTP id 6A82CC0047; Thu, 26 Mar 2009 17:57:31 +0100 (CET)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius2.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id J8pzpBohLa6u; Thu, 26 Mar 2009 17:57:30 +0100 (CET)
Received: from elstar.local (elstar.iuhb02.iu-bremen.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id CE266C000A; Thu, 26 Mar 2009 17:57:30 +0100 (CET)
Received: by elstar.local (Postfix, from userid 501) id 4E751A40F8D; Thu, 26 Mar 2009 17:57:14 +0100 (CET)
Date: Thu, 26 Mar 2009 17:57:14 +0100
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: "Scott O. Bradner" <sob@harvard.edu>
Message-ID: <20090326165714.GA21511@elstar.local>
Mail-Followup-To: "Scott O. Bradner" <sob@harvard.edu>, opsawg@ietf.org
References: <20090311180640.D74841483B97@newdev.eecs.harvard.edu> <20090311190038.GB29633@elstar.local>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20090311190038.GB29633@elstar.local>
User-Agent: Mutt/1.5.19 (2009-01-05)
Cc: opsawg@ietf.org
Subject: [OPSAWG] snmp syslog mappings ready for wg last call
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Mar 2009 16:56:39 -0000

I just posted an update for the SYSLOG to SNMP mapping ID. I believe
the two documents

    draft-ietf-opsawg-syslog-snmp-02.txt
    draft-ietf-opsawg-syslog-msg-mib-02.txt

are technically complete and ready for WG last call.

/js

-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: +49 421 200 3587         Campus Ring 1, 28759 Bremen, Germany
Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>

From root@core3.amsl.com  Thu Mar 26 10:00:02 2009
Return-Path: <root@core3.amsl.com>
X-Original-To: opsawg@ietf.org
Delivered-To: opsawg@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id 0B5B13A6E02; Thu, 26 Mar 2009 10:00:01 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20090326170002.0B5B13A6E02@core3.amsl.com>
Date: Thu, 26 Mar 2009 10:00:02 -0700 (PDT)
Cc: opsawg@ietf.org
Subject: [OPSAWG] I-D Action:draft-ietf-opsawg-syslog-snmp-02.txt
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Mar 2009 17:00:02 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Operations and Management Area Working Group Working Group of the IETF.


	Title           : Mapping Simple Network Management Protocol (SNMP) Notifications to SYSLOG Messages
	Author(s)       : V. Marinov, J. Schoenwaelder
	Filename        : draft-ietf-opsawg-syslog-snmp-02.txt
	Pages           : 15
	Date            : 2009-03-26

This memo defines a mapping from Simple Network Management Protocol
(SNMP) notifications to SYSLOG notifications.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-opsawg-syslog-snmp-02.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-opsawg-syslog-snmp-02.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2009-03-26094939.I-D@ietf.org>


--NextPart--

From sob@harvard.edu  Thu Mar 26 10:33:14 2009
Return-Path: <sob@harvard.edu>
X-Original-To: opsawg@core3.amsl.com
Delivered-To: opsawg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4A31C3A6A99 for <opsawg@core3.amsl.com>; Thu, 26 Mar 2009 10:33:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.493
X-Spam-Level: 
X-Spam-Status: No, score=-2.493 tagged_above=-999 required=5 tests=[AWL=0.106,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uBAYg-7UAo5y for <opsawg@core3.amsl.com>; Thu, 26 Mar 2009 10:33:13 -0700 (PDT)
Received: from newdev.eecs.harvard.edu (newdev.eecs.harvard.edu [140.247.60.212]) by core3.amsl.com (Postfix) with ESMTP id C8DC428C106 for <opsawg@ietf.org>; Thu, 26 Mar 2009 10:33:11 -0700 (PDT)
Received: by newdev.eecs.harvard.edu (Postfix, from userid 501) id 4D209152478F; Thu, 26 Mar 2009 13:34:04 -0400 (EDT)
To: opsawg@ietf.org
Message-Id: <20090326173404.4D209152478F@newdev.eecs.harvard.edu>
Date: Thu, 26 Mar 2009 13:34:04 -0400 (EDT)
From: sob@harvard.edu (Scott O. Bradner)
Subject: [OPSAWG] WGLC on syslog/snmp IDs
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Mar 2009 17:33:14 -0000

this starts a WGLC on 
    draft-ietf-opsawg-syslog-snmp-02.txt
and
    draft-ietf-opsawg-syslog-msg-mib-02.txt

please send any comments to the list by April 13th

thanks

Scott

From root@core3.amsl.com  Fri Mar 27 09:30:02 2009
Return-Path: <root@core3.amsl.com>
X-Original-To: opsawg@ietf.org
Delivered-To: opsawg@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id 1FB693A6C9D; Fri, 27 Mar 2009 09:30:01 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20090327163002.1FB693A6C9D@core3.amsl.com>
Date: Fri, 27 Mar 2009 09:30:02 -0700 (PDT)
Cc: opsawg@ietf.org
Subject: [OPSAWG] I-D Action:draft-ietf-opsawg-smi-datatypes-in-xsd-05.txt
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Mar 2009 16:30:02 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Operations and Management Area Working Group Working Group of the IETF.


	Title           : Expressing SNMP SMI Datatypes in XML Schema Definition Language
	Author(s)       : B. Natale
	Filename        : draft-ietf-opsawg-smi-datatypes-in-xsd-05.txt
	Pages           : 17
	Date            : 2009-03-27

This memo defines the IETF standard expression of Structure of
Management Information (SMI) base datatypes in Extensible Markup
Language (XML) Schema Definition (XSD) language.  The primary
objective of this memo is to enable the production of XML documents
that are as faithful to the SMI as possible, using XSD as the
validation mechanism.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-opsawg-smi-datatypes-in-xsd-05.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-opsawg-smi-datatypes-in-xsd-05.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2009-03-27092528.I-D@ietf.org>


--NextPart--
