
From nobody Thu Jun  5 05:01:51 2014
Return-Path: <bclaise@cisco.com>
X-Original-To: mib-doctors@ietfa.amsl.com
Delivered-To: mib-doctors@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 98D1D1A0074 for <mib-doctors@ietfa.amsl.com>; Thu,  5 Jun 2014 05:01:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.15
X-Spam-Level: 
X-Spam-Status: No, score=-10.15 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.651, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ud7KfGiBUQA8 for <mib-doctors@ietfa.amsl.com>; Thu,  5 Jun 2014 05:01:43 -0700 (PDT)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 472461A0071 for <mib-doctors@ietf.org>; Thu,  5 Jun 2014 05:01:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4558; q=dns/txt; s=iport; t=1401969696; x=1403179296; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to; bh=aDwxO9xpZ5w9r15VqOOT2JdR8FREXf9pC8PB+F1rCvw=; b=OO5JFfVyZMxuJcjjoL2KbfeJgxxfiT1GgYt/l/HGCqOvXQxaZQULcESu 1aTmH3Y/CIo2OkyErzPxEpRG6RdtrUoyR1eXQ5z5yuGA4go0+CyVipSsU 1Cct5dYI8iHEYBvMGxYdqw8yXW6MC+iD2vEVMUDQcqhwdbcFkn6FAliK/ 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: At8EAMhbkFOtJssW/2dsb2JhbABZxhEBgR0BgSN0giUBAQEEeQwEDw0DAQIKJQ8CNQcCCAYNAQUCAQGIPtMoF45BEQcGhDoEmhOGcIxJgzo7
X-IronPort-AV: E=Sophos; i="4.98,980,1392163200"; d="scan'208,217"; a="75450214"
Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-1.cisco.com with ESMTP; 05 Jun 2014 12:01:34 +0000
Received: from [10.60.67.91] (ams-bclaise-89110.cisco.com [10.60.67.91]) by aer-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id s55C1YBf017943; Thu, 5 Jun 2014 12:01:34 GMT
Message-ID: <53905C1E.10808@cisco.com>
Date: Thu, 05 Jun 2014 14:01:34 +0200
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0
MIME-Version: 1.0
To: "MIB Doctors (E-mail)" <mib-doctors@ietf.org>
References: <07a601cf800e$ea9710e0$bfc532a0$@olddog.co.uk>
In-Reply-To: <07a601cf800e$ea9710e0$bfc532a0$@olddog.co.uk>
X-Forwarded-Message-Id: <07a601cf800e$ea9710e0$bfc532a0$@olddog.co.uk>
Content-Type: multipart/alternative; boundary="------------070508090901080505050001"
Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/rGfSqG1QPnxyaq9Lm3ZfczXyXUU
Cc: Adrian Farrel <adrian@olddog.co.uk>
Subject: [MIB-DOCTORS] Fwd: Request to add to the MIB boilperplate for "writeable objects"
X-BeenThere: mib-doctors@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: MIB Doctors list <mib-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mib-doctors/>
List-Post: <mailto:mib-doctors@ietf.org>
List-Help: <mailto:mib-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Jun 2014 12:01:49 -0000

This is a multi-part message in MIME format.
--------------070508090901080505050001
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Dear MIB-doctors,

Here is a proposal from Adrian on updating the MIB boilerplate.
This looks good to me. Any feedback?

Regards, Benoit


-------- Original Message --------
Subject: 	Request to add to the MIB boilperplate for "writeable objects"
Date: 	Wed, 4 Jun 2014 17:06:16 +0100
From: 	Adrian Farrel <adrian@olddog.co.uk>
Reply-To: 	<adrian@olddog.co.uk>
To: 	<bclaise@cisco.com>



Hi Benoit,

After the work on the BFD MIB modules and considering the IESG statement on
writeability, would you consider adding to the MIB boilerplate an optional piece
of text that says...

====
The following objects in the MIB modules in this document have write access
either through read-write or read-create MAX-ACCESS clauses. The level of access
to these objects have been discussed by the <xxxx> working group and it was
concluded that write access was beneficial for the following reasons:

- <list of reasons>

- <list of objects>

As with all MIB modules, an attempt to SET or CREATE an object to a value that
is not supported by the implementation will result in a failure using a return
code that indicates that the value is not supported.

====

I think this would help to contain and control work on MIB documents in the
future, and would give the Doctors something to review against.

Please wordsmith to your heart's content.

Ciao,
Adrian

.




--------------070508090901080505050001
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Dear MIB-doctors,<br>
    <br>
    Here is a proposal from Adrian on updating the MIB boilerplate.<br>
    This looks good to me. Any feedback?<br>
    <br>
    Regards, Benoit<br>
    <div class="moz-forward-container"><br>
      <br>
      -------- Original Message --------
      <table class="moz-email-headers-table" cellpadding="0"
        cellspacing="0" border="0">
        <tbody>
          <tr>
            <th align="RIGHT" nowrap="nowrap" valign="BASELINE">Subject:
            </th>
            <td>Request to add to the MIB boilperplate for "writeable
              objects"</td>
          </tr>
          <tr>
            <th align="RIGHT" nowrap="nowrap" valign="BASELINE">Date: </th>
            <td>Wed, 4 Jun 2014 17:06:16 +0100</td>
          </tr>
          <tr>
            <th align="RIGHT" nowrap="nowrap" valign="BASELINE">From: </th>
            <td>Adrian Farrel <a class="moz-txt-link-rfc2396E" href="mailto:adrian@olddog.co.uk">&lt;adrian@olddog.co.uk&gt;</a></td>
          </tr>
          <tr>
            <th align="RIGHT" nowrap="nowrap" valign="BASELINE">Reply-To:
            </th>
            <td><a class="moz-txt-link-rfc2396E" href="mailto:adrian@olddog.co.uk">&lt;adrian@olddog.co.uk&gt;</a></td>
          </tr>
          <tr>
            <th align="RIGHT" nowrap="nowrap" valign="BASELINE">To: </th>
            <td><a class="moz-txt-link-rfc2396E" href="mailto:bclaise@cisco.com">&lt;bclaise@cisco.com&gt;</a></td>
          </tr>
        </tbody>
      </table>
      <br>
      <br>
      <pre>Hi Benoit,

After the work on the BFD MIB modules and considering the IESG statement on
writeability, would you consider adding to the MIB boilerplate an optional piece
of text that says...

====
The following objects in the MIB modules in this document have write access
either through read-write or read-create MAX-ACCESS clauses. The level of access
to these objects have been discussed by the &lt;xxxx&gt; working group and it was
concluded that write access was beneficial for the following reasons:

- &lt;list of reasons&gt;

- &lt;list of objects&gt;

As with all MIB modules, an attempt to SET or CREATE an object to a value that
is not supported by the implementation will result in a failure using a return
code that indicates that the value is not supported.

====

I think this would help to contain and control work on MIB documents in the
future, and would give the Doctors something to review against.

Please wordsmith to your heart's content.

Ciao,
Adrian

.

</pre>
      <br>
    </div>
    <br>
  </body>
</html>

--------------070508090901080505050001--


From nobody Thu Jun  5 05:20:50 2014
Return-Path: <dromasca@avaya.com>
X-Original-To: mib-doctors@ietfa.amsl.com
Delivered-To: mib-doctors@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 500851A008C for <mib-doctors@ietfa.amsl.com>; Thu,  5 Jun 2014 05:20:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.55
X-Spam-Level: 
X-Spam-Status: No, score=-2.55 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.651] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dp3bFlHz01i2 for <mib-doctors@ietfa.amsl.com>; Thu,  5 Jun 2014 05:20:44 -0700 (PDT)
Received: from p-us1-iereast-outbound.us1.avaya.com (p-us1-iereast-outbound.us1.avaya.com [135.11.29.13]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9D9B21A008A for <mib-doctors@ietf.org>; Thu,  5 Jun 2014 05:20:44 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AlIOAIBfkFOHCzIm/2dsb2JhbABZgkIjIlJYqlEGkHaGEwGBHQGBDRZ0giUBAQEBAxIbTAwEAgEIDQEDAwEBAQsdBzIUCQgCBAENBQgaiCABoj2wWxeFVYhMIBEGAQaDJYEVBKEsjCCBeIFAgi8
X-IronPort-AV: E=Sophos; i="4.98,980,1392181200"; d="scan'208,217"; a="69160880"
Received: from unknown (HELO p-us1-erheast-smtpauth.us1.avaya.com) ([135.11.50.38]) by p-us1-iereast-outbound.us1.avaya.com with ESMTP; 05 Jun 2014 08:20:37 -0400
X-OutboundMail_SMTP: 1
Received: from unknown (HELO AZ-FFEXHC03.global.avaya.com) ([135.64.58.13]) by p-us1-erheast-out.us1.avaya.com with ESMTP/TLS/AES128-SHA; 05 Jun 2014 08:18:26 -0400
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC03.global.avaya.com ([135.64.58.13]) with mapi id 14.03.0174.001; Thu, 5 Jun 2014 08:20:35 -0400
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: Benoit Claise <bclaise@cisco.com>, "MIB Doctors (E-mail)" <mib-doctors@ietf.org>
Thread-Topic: [MIB-DOCTORS] Fwd: Request to add to the MIB boilperplate for "writeable objects"
Thread-Index: AQHPgLX2lV6O5tFwkk+8p3JYX2UEBZtibgRw
Date: Thu, 5 Jun 2014 12:20:34 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA5C7FE398@AZ-FFEXMB04.global.avaya.com>
References: <07a601cf800e$ea9710e0$bfc532a0$@olddog.co.uk> <53905C1E.10808@cisco.com>
In-Reply-To: <53905C1E.10808@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.64.58.45]
Content-Type: multipart/alternative; boundary="_000_9904FB1B0159DA42B0B887B7FA8119CA5C7FE398AZFFEXMB04globa_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/mHXm0QYKvexG0Y-hyj-o7N09pkI
Cc: Adrian Farrel <adrian@olddog.co.uk>
Subject: Re: [MIB-DOCTORS] Fwd: Request to add to the MIB boilperplate for "writeable objects"
X-BeenThere: mib-doctors@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: MIB Doctors list <mib-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mib-doctors/>
List-Post: <mailto:mib-doctors@ietf.org>
List-Help: <mailto:mib-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Jun 2014 12:20:47 -0000

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

See in-line.

Regards,

Dan


From: MIB-DOCTORS [mailto:mib-doctors-bounces@ietf.org] On Behalf Of Benoit=
 Claise
Sent: Thursday, June 05, 2014 3:02 PM
To: MIB Doctors (E-mail)
Cc: Adrian Farrel
Subject: [MIB-DOCTORS] Fwd: Request to add to the MIB boilperplate for "wri=
teable objects"

Dear MIB-doctors,

Here is a proposal from Adrian on updating the MIB boilerplate.
This looks good to me. Any feedback?

Regards, Benoit


-------- Original Message --------
Subject:

Request to add to the MIB boilperplate for "writeable objects"

Date:

Wed, 4 Jun 2014 17:06:16 +0100

From:

Adrian Farrel <adrian@olddog.co.uk><mailto:adrian@olddog.co.uk>

Reply-To:

<adrian@olddog.co.uk><mailto:adrian@olddog.co.uk>

To:

<bclaise@cisco.com><mailto:bclaise@cisco.com>



Hi Benoit,



After the work on the BFD MIB modules and considering the IESG statement on

writeability, would you consider adding to the MIB boilerplate an optional =
piece

of text that says...



n

n  Where is this text planned to be added? - Security considerations?



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

The following objects in the MIB modules in this document have write access

either through read-write or read-create MAX-ACCESS clauses. The level of a=
ccess

to these objects have been discussed by the <xxxx> working group and it was

concluded that write access was beneficial for the following reasons:



- <list of reasons>



- <list of objects>



As with all MIB modules, an attempt to SET or CREATE an object to a value t=
hat

is not supported by the implementation will result in a failure using a ret=
urn

code that indicates that the value is not supported.



n     I am not sure that we need this paragraph. A compliant implementation=
 will do what is supposed to do. Moreover, this is not about 'value not sup=
ported' but about trying to write objects that are not writeable - the erro=
r codes are different.



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



I think this would help to contain and control work on MIB documents in the

future, and would give the Doctors something to review against.



Please wordsmith to your heart's content.



Ciao,

Adrian



.





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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";
	color:black;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";
	color:black;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0cm;
	margin-right:0cm;
	margin-bottom:0cm;
	margin-left:36.0pt;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";
	color:black;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;
	color:black;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1271666698;
	mso-list-type:hybrid;
	mso-list-template-ids:892784830 -685880772 67698691 67698693 67698689 6769=
8691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-start-at:0;
	mso-level-number-format:bullet;
	mso-level-text:\F0D8;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:Arial;}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
@list l1
	{mso-list-id:1314027032;
	mso-list-type:hybrid;
	mso-list-template-ids:1632525898 1153189266 67698691 67698693 67698689 676=
98691 67698693 67698689 67698691 67698693;}
@list l1:level1
	{mso-level-start-at:0;
	mso-level-number-format:bullet;
	mso-level-text:\F06E;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:Arial;}
@list l1:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l1:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
@list l1:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Symbol;}
@list l1:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l1:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
@list l1:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Symbol;}
@list l1:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l1:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body bgcolor=3D"white" lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">See in-line.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Regards,<o:p></o:p></span=
></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Dan<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;;color:windowtext">From:</span></b><spa=
n style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif=
&quot;;color:windowtext"> MIB-DOCTORS [mailto:mib-doctors-bounces@ietf.org]
<b>On Behalf Of </b>Benoit Claise<br>
<b>Sent:</b> Thursday, June 05, 2014 3:02 PM<br>
<b>To:</b> MIB Doctors (E-mail)<br>
<b>Cc:</b> Adrian Farrel<br>
<b>Subject:</b> [MIB-DOCTORS] Fwd: Request to add to the MIB boilperplate f=
or &quot;writeable objects&quot;<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Dear MIB-doctors,<br>
<br>
Here is a proposal from Adrian on updating the MIB boilerplate.<br>
This looks good to me. Any feedback?<br>
<br>
Regards, Benoit<o:p></o:p></p>
<div>
<p class=3D"MsoNormal"><br>
<br>
-------- Original Message -------- <o:p></o:p></p>
<table class=3D"MsoNormalTable" border=3D"0" cellspacing=3D"0" cellpadding=
=3D"0">
<tbody>
<tr>
<td nowrap=3D"" valign=3D"top" style=3D"padding:0cm 0cm 0cm 0cm">
<p class=3D"MsoNormal" align=3D"right" style=3D"text-align:right"><b>Subjec=
t: <o:p></o:p></b></p>
</td>
<td style=3D"padding:0cm 0cm 0cm 0cm">
<p class=3D"MsoNormal">Request to add to the MIB boilperplate for &quot;wri=
teable objects&quot;<o:p></o:p></p>
</td>
</tr>
<tr>
<td nowrap=3D"" valign=3D"top" style=3D"padding:0cm 0cm 0cm 0cm">
<p class=3D"MsoNormal" align=3D"right" style=3D"text-align:right"><b>Date: =
<o:p></o:p></b></p>
</td>
<td style=3D"padding:0cm 0cm 0cm 0cm">
<p class=3D"MsoNormal">Wed, 4 Jun 2014 17:06:16 &#43;0100<o:p></o:p></p>
</td>
</tr>
<tr>
<td nowrap=3D"" valign=3D"top" style=3D"padding:0cm 0cm 0cm 0cm">
<p class=3D"MsoNormal" align=3D"right" style=3D"text-align:right"><b>From: =
<o:p></o:p></b></p>
</td>
<td style=3D"padding:0cm 0cm 0cm 0cm">
<p class=3D"MsoNormal">Adrian Farrel <a href=3D"mailto:adrian@olddog.co.uk"=
>&lt;adrian@olddog.co.uk&gt;</a><o:p></o:p></p>
</td>
</tr>
<tr>
<td nowrap=3D"" valign=3D"top" style=3D"padding:0cm 0cm 0cm 0cm">
<p class=3D"MsoNormal" align=3D"right" style=3D"text-align:right"><b>Reply-=
To: <o:p></o:p></b></p>
</td>
<td style=3D"padding:0cm 0cm 0cm 0cm">
<p class=3D"MsoNormal"><a href=3D"mailto:adrian@olddog.co.uk">&lt;adrian@ol=
ddog.co.uk&gt;</a><o:p></o:p></p>
</td>
</tr>
<tr>
<td nowrap=3D"" valign=3D"top" style=3D"padding:0cm 0cm 0cm 0cm">
<p class=3D"MsoNormal" align=3D"right" style=3D"text-align:right"><b>To: <o=
:p></o:p></b></p>
</td>
<td style=3D"padding:0cm 0cm 0cm 0cm">
<p class=3D"MsoNormal"><a href=3D"mailto:bclaise@cisco.com">&lt;bclaise@cis=
co.com&gt;</a><o:p></o:p></p>
</td>
</tr>
</tbody>
</table>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><o:p>&nbsp;</o:p></p>
<pre>Hi Benoit,<o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>After the work on the BFD MIB modules and considering the IESG stateme=
nt on<o:p></o:p></pre>
<pre>writeability, would you consider adding to the MIB boilerplate an opti=
onal piece<o:p></o:p></pre>
<pre>of text that says...<o:p></o:p></pre>
<pre><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></span></pre>
<p class=3D"MsoListParagraph" style=3D"margin-left:0cm;text-indent:0cm;mso-=
list:l1 level1 lfo2">
<![if !supportLists]><span style=3D"font-size:11.0pt;font-family:Wingdings;=
color:#1F497D"><span style=3D"mso-list:Ignore">n<span style=3D"font:7.0pt &=
quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span dir=3D"LTR"></span><span style=3D"font=
-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#=
1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-18.0pt;mso-list:l1 leve=
l1 lfo2"><![if !supportLists]><span style=3D"font-size:11.0pt;font-family:W=
ingdings;color:#1F497D"><span style=3D"mso-list:Ignore">n<span style=3D"fon=
t:7.0pt &quot;Times New Roman&quot;">&nbsp;
</span></span></span><![endif]><span dir=3D"LTR"></span><span style=3D"font=
-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#=
1F497D">Where is this text planned to be added? - Security considerations?
<o:p></o:p></span></p>
<pre><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;=
sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span></pre>
<pre>=3D=3D=3D=3D<o:p></o:p></pre>
<pre>The following objects in the MIB modules in this document have write a=
ccess<o:p></o:p></pre>
<pre>either through read-write or read-create MAX-ACCESS clauses. The level=
 of access<o:p></o:p></pre>
<pre>to these objects have been discussed by the &lt;xxxx&gt; working group=
 and it was<o:p></o:p></pre>
<pre>concluded that write access was beneficial for the following reasons:<=
o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>- &lt;list of reasons&gt;<o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>- &lt;list of objects&gt;<o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>As with all MIB modules, an attempt to SET or CREATE an object to a va=
lue that<o:p></o:p></pre>
<pre>is not supported by the implementation will result in a failure using =
a return<o:p></o:p></pre>
<pre>code that indicates that the value is not supported.<o:p></o:p></pre>
<pre><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;=
sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span></pre>
<pre style=3D"margin-left:0cm;text-indent:0cm;mso-list:l1 level1 lfo2"><![i=
f !supportLists]><span style=3D"font-size:11.0pt;font-family:Wingdings;colo=
r:#1F497D"><span style=3D"mso-list:Ignore">n<span style=3D"font:7.0pt &quot=
;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><![en=
dif]><span dir=3D"LTR"></span><span style=3D"font-size:11.0pt;font-family:&=
quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">I am not sure that=
 we need this paragraph. A compliant implementation will do what is suppose=
d to do. Moreover, this is not about &#8216;value not supported&#8217; but =
about trying to write objects that are not writeable &#8211; the error code=
s are different. <o:p></o:p></span></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>=3D=3D=3D=3D<o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>I think this would help to contain and control work on MIB documents i=
n the<o:p></o:p></pre>
<pre>future, and would give the Doctors something to review against.<o:p></=
o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>Please wordsmith to your heart's content.<o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>Ciao,<o:p></o:p></pre>
<pre>Adrian<o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>.<o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</body>
</html>

--_000_9904FB1B0159DA42B0B887B7FA8119CA5C7FE398AZFFEXMB04globa_--


From nobody Thu Jun  5 05:36:09 2014
Return-Path: <j.schoenwaelder@jacobs-university.de>
X-Original-To: mib-doctors@ietfa.amsl.com
Delivered-To: mib-doctors@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B45E71A00A2 for <mib-doctors@ietfa.amsl.com>; Thu,  5 Jun 2014 05:36:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.201
X-Spam-Level: 
X-Spam-Status: No, score=-2.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RP_MATCHES_RCVD=-0.651] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id P0mFKWxwZkfA for <mib-doctors@ietfa.amsl.com>; Thu,  5 Jun 2014 05:36:05 -0700 (PDT)
Received: from atlas3.jacobs-university.de (atlas3.jacobs-university.de [212.201.44.18]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6341F1A0097 for <mib-doctors@ietf.org>; Thu,  5 Jun 2014 05:36:05 -0700 (PDT)
Received: from localhost (demetrius5.irc-it.jacobs-university.de [10.70.0.222]) by atlas3.jacobs-university.de (Postfix) with ESMTP id 9F46F115F; Thu,  5 Jun 2014 14:35:57 +0200 (CEST)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from atlas3.jacobs-university.de ([10.70.0.220]) by localhost (demetrius5.jacobs-university.de [10.70.0.222]) (amavisd-new, port 10030) with ESMTP id kU3HH4z1GKKR; Thu,  5 Jun 2014 14:35:41 +0200 (CEST)
Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hermes.jacobs-university.de", Issuer "Jacobs University CA - G01" (verified OK)) by atlas3.jacobs-university.de (Postfix) with ESMTPS; Thu,  5 Jun 2014 14:35:57 +0200 (CEST)
Received: from localhost (demetrius2.jacobs-university.de [212.201.44.47]) by hermes.jacobs-university.de (Postfix) with ESMTP id 98ED420017; Thu,  5 Jun 2014 14:35:57 +0200 (CEST)
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 alb8hCPKqAaN; Thu,  5 Jun 2014 14:35:56 +0200 (CEST)
Received: from elstar.local (elstar.jacobs.jacobs-university.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id 20B6620013; Thu,  5 Jun 2014 14:35:56 +0200 (CEST)
Received: by elstar.local (Postfix, from userid 501) id 509BD2D523C1; Thu,  5 Jun 2014 14:35:55 +0200 (CEST)
Date: Thu, 5 Jun 2014 14:35:54 +0200
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: Benoit Claise <bclaise@cisco.com>
Message-ID: <20140605123554.GA11717@elstar.local>
Mail-Followup-To: Benoit Claise <bclaise@cisco.com>, "MIB Doctors (E-mail)" <mib-doctors@ietf.org>, Adrian Farrel <adrian@olddog.co.uk>
References: <07a601cf800e$ea9710e0$bfc532a0$@olddog.co.uk> <53905C1E.10808@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <53905C1E.10808@cisco.com>
User-Agent: Mutt/1.4.2.3i
Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/3vHSquRwkTJJCrMs41rX88I-EtU
Cc: "MIB Doctors \(E-mail\)" <mib-doctors@ietf.org>, Adrian Farrel <adrian@olddog.co.uk>
Subject: Re: [MIB-DOCTORS] Fwd: Request to add to the MIB boilperplate for "writeable objects"
X-BeenThere: mib-doctors@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
List-Id: MIB Doctors list <mib-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mib-doctors/>
List-Post: <mailto:mib-doctors@ietf.org>
List-Help: <mailto:mib-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Jun 2014 12:36:07 -0000

On Thu, Jun 05, 2014 at 02:01:34PM +0200, Benoit Claise wrote:

> The following objects in the MIB modules in this document have write access
> either through read-write or read-create MAX-ACCESS clauses. The level of 
> access
> to these objects have been discussed by the <xxxx> working group and it was
> concluded that write access was beneficial for the following reasons:
> 
> - <list of reasons>
> 
> - <list of objects>

I wonder why this belongs into the security considerations
section. This is a design decision, only marginally related to
security considerations.

> As with all MIB modules, an attempt to SET or CREATE an object to a
> value that is not supported by the implementation will result in a
> failure using a return code that indicates that the value is not
> supported.

This is all regulated in RFC 3416. I fail to see why this now have to
repeat this in security considerations (12 years after RFC 3416 got
published and lots of MIB modules got published).

> I think this would help to contain and control work on MIB documents in the
> future, and would give the Doctors something to review against.

Security considerations are IMHO the wrong place to document IETF
policies. I do not think the security properties of SNMP have changed
and I also believe the recent IESG statement was not motivated by
security concerns.

/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 nobody Thu Jun  5 08:31:17 2014
Return-Path: <tnadeau@lucidvision.com>
X-Original-To: mib-doctors@ietfa.amsl.com
Delivered-To: mib-doctors@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 979461A01E1 for <mib-doctors@ietfa.amsl.com>; Thu,  5 Jun 2014 08:31:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.552
X-Spam-Level: 
X-Spam-Status: No, score=-2.552 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.651, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JAw3DI8vflgb for <mib-doctors@ietfa.amsl.com>; Thu,  5 Jun 2014 08:31:11 -0700 (PDT)
Received: from lucidvision.com (lucidvision.com [72.71.250.34]) by ietfa.amsl.com (Postfix) with ESMTP id 1E0B51A025E for <mib-doctors@ietf.org>; Thu,  5 Jun 2014 08:30:41 -0700 (PDT)
Received: from [192.168.1.107] (static-72-71-250-38.cncdnh.fast04.myfairpoint.net [72.71.250.38]) by lucidvision.com (Postfix) with ESMTP id 04ECF27D1EF9; Thu,  5 Jun 2014 11:30:35 -0400 (EDT)
Content-Type: multipart/signed; boundary="Apple-Mail=_AECE5681-1E58-480C-A603-235589FEDC42"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\))
From: "Thomas D. Nadeau" <tnadeau@lucidvision.com>
In-Reply-To: <9904FB1B0159DA42B0B887B7FA8119CA5C7FE398@AZ-FFEXMB04.global.avaya.com>
Date: Thu, 5 Jun 2014 11:30:33 -0400
Message-Id: <4308CFC7-7341-4D66-A50C-5B808DB9FCEC@lucidvision.com>
References: <07a601cf800e$ea9710e0$bfc532a0$@olddog.co.uk> <53905C1E.10808@cisco.com> <9904FB1B0159DA42B0B887B7FA8119CA5C7FE398@AZ-FFEXMB04.global.avaya.com>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
X-Mailer: Apple Mail (2.1878.2)
Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/AdvnBW4dMh3Px381ZlbPyAnvaUc
Cc: "MIB Doctors \(E-mail\)" <mib-doctors@ietf.org>, Farrel Adrian <adrian@olddog.co.uk>
Subject: Re: [MIB-DOCTORS] Fwd: Request to add to the MIB boilperplate for "writeable objects"
X-BeenThere: mib-doctors@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: MIB Doctors list <mib-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mib-doctors/>
List-Post: <mailto:mib-doctors@ietf.org>
List-Help: <mailto:mib-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Jun 2014 15:31:15 -0000

--Apple-Mail=_AECE5681-1E58-480C-A603-235589FEDC42
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_7363CFAF-E141-434F-80B8-364D5F1B3EBD"


--Apple-Mail=_7363CFAF-E141-434F-80B8-364D5F1B3EBD
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252


	I agree. This is just swimming around the drain. We need to just =
emphatically stop r-w and be done with this issue.=20

	--Tom


> See in-line.
> =20
> Regards,
> =20
> Dan
> =20
> =20
> From: MIB-DOCTORS [mailto:mib-doctors-bounces@ietf.org] On Behalf Of =
Benoit Claise
> Sent: Thursday, June 05, 2014 3:02 PM
> To: MIB Doctors (E-mail)
> Cc: Adrian Farrel
> Subject: [MIB-DOCTORS] Fwd: Request to add to the MIB boilperplate for =
"writeable objects"
> =20
> Dear MIB-doctors,
>=20
> Here is a proposal from Adrian on updating the MIB boilerplate.
> This looks good to me. Any feedback?
>=20
> Regards, Benoit
>=20
>=20
> -------- Original Message --------
> Subject:
> Request to add to the MIB boilperplate for "writeable objects"
> Date:
> Wed, 4 Jun 2014 17:06:16 +0100
> From:
> Adrian Farrel <adrian@olddog.co.uk>
> Reply-To:
> <adrian@olddog.co.uk>
> To:
> <bclaise@cisco.com>
> =20
>=20
> Hi Benoit,
> =20
> After the work on the BFD MIB modules and considering the IESG =
statement on
> writeability, would you consider adding to the MIB boilerplate an =
optional piece
> of text that says...
> =20
> n    =20
> n  Where is this text planned to be added? - Security considerations?
> =20
> =3D=3D=3D=3D
> The following objects in the MIB modules in this document have write =
access
> either through read-write or read-create MAX-ACCESS clauses. The level =
of access
> to these objects have been discussed by the <xxxx> working group and =
it was
> concluded that write access was beneficial for the following reasons:
> =20
> - <list of reasons>
> =20
> - <list of objects>
> =20
> As with all MIB modules, an attempt to SET or CREATE an object to a =
value that
> is not supported by the implementation will result in a failure using =
a return
> code that indicates that the value is not supported.
> =20
> n     I am not sure that we need this paragraph. A compliant =
implementation will do what is supposed to do. Moreover, this is not =
about =91value not supported=92 but about trying to write objects that =
are not writeable =96 the error codes are different.=20
> =20
> =3D=3D=3D=3D
> =20
> I think this would help to contain and control work on MIB documents =
in the
> future, and would give the Doctors something to review against.
> =20
> Please wordsmith to your heart's content.
> =20
> Ciao,
> Adrian
> =20
> .
> =20
> =20
> =20
> _______________________________________________
> MIB-DOCTORS mailing list
> MIB-DOCTORS@ietf.org
> https://www.ietf.org/mailman/listinfo/mib-doctors


--Apple-Mail=_7363CFAF-E141-434F-80B8-364D5F1B3EBD
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=windows-1252

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dwindows-1252"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space;"><div><br></div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>I agree. This is just swimming =
around the drain. We need to just emphatically stop r-w and be done with =
this issue.&nbsp;<div><br></div><div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	=
</span>--Tom</div><div><br><div><div><br></div><blockquote =
type=3D"cite"><div bgcolor=3D"white" lang=3D"EN-US" link=3D"blue" =
vlink=3D"purple" style=3D"font-family: Helvetica; font-size: 16px; =
font-style: normal; font-variant: normal; font-weight: normal; =
letter-spacing: normal; line-height: normal; orphans: auto; text-align: =
start; text-indent: 0px; text-transform: none; white-space: normal; =
widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><div =
class=3D"WordSection1" style=3D"page: WordSection1;"><div style=3D"margin:=
 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', =
serif;"><span style=3D"font-size: 11pt; font-family: Calibri, =
sans-serif; color: rgb(31, 73, 125);">See =
in-line.<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif;"><span =
style=3D"font-size: 11pt; font-family: Calibri, sans-serif; color: =
rgb(31, 73, 125);">&nbsp;</span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><span =
style=3D"font-size: 11pt; font-family: Calibri, sans-serif; color: =
rgb(31, 73, 125);">Regards,<o:p></o:p></span></div><div style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', =
serif;"><span style=3D"font-size: 11pt; font-family: Calibri, =
sans-serif; color: rgb(31, 73, 125);">&nbsp;</span></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times =
New Roman', serif;"><span style=3D"font-size: 11pt; font-family: =
Calibri, sans-serif; color: rgb(31, 73, =
125);">Dan<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><span =
style=3D"font-size: 11pt; font-family: Calibri, sans-serif; color: =
rgb(31, 73, 125);">&nbsp;</span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><span =
style=3D"font-size: 11pt; font-family: Calibri, sans-serif; color: =
rgb(31, 73, 125);">&nbsp;</span></div><div style=3D"border-style: none =
none none solid; border-left-color: blue; border-left-width: 1.5pt; =
padding: 0cm 0cm 0cm 4pt;"><div><div style=3D"border-style: solid none =
none; border-top-color: rgb(181, 196, 223); border-top-width: 1pt; =
padding: 3pt 0cm 0cm;"><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif;"><b><span =
style=3D"font-size: 10pt; font-family: Tahoma, sans-serif; color: =
windowtext;">From:</span></b><span style=3D"font-size: 10pt; =
font-family: Tahoma, sans-serif; color: windowtext;"><span =
class=3D"Apple-converted-space">&nbsp;</span>MIB-DOCTORS [<a =
href=3D"mailto:mib-doctors-bounces@ietf.org" style=3D"color: purple; =
text-decoration: =
underline;">mailto:mib-doctors-bounces@ietf.org</a>]<span =
class=3D"Apple-converted-space">&nbsp;</span><b>On Behalf Of<span =
class=3D"Apple-converted-space">&nbsp;</span></b>Benoit =
Claise<br><b>Sent:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>Thursday, June 05, 2014 =
3:02 PM<br><b>To:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>MIB Doctors =
(E-mail)<br><b>Cc:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>Adrian =
Farrel<br><b>Subject:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>[MIB-DOCTORS] Fwd: Request =
to add to the MIB boilperplate for "writeable =
objects"<o:p></o:p></span></div></div></div><div style=3D"margin: 0cm =
0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', =
serif;"><o:p>&nbsp;</o:p></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif;">Dear =
MIB-doctors,<br><br>Here is a proposal from Adrian on updating the MIB =
boilerplate.<br>This looks good to me. Any feedback?<br><br>Regards, =
Benoit<o:p></o:p></div><div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', =
serif;"><br><br>-------- Original Message =
--------<o:p></o:p></div><table class=3D"MsoNormalTable" border=3D"0" =
cellspacing=3D"0" cellpadding=3D"0"><tbody><tr><td nowrap=3D"" =
valign=3D"top" style=3D"padding: 0cm;"><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; =
text-align: right;"><b>Subject:<o:p></o:p></b></div></td><td =
style=3D"padding: 0cm;"><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif;">Request to add =
to the MIB boilperplate for "writeable =
objects"<o:p></o:p></div></td></tr><tr><td nowrap=3D"" valign=3D"top" =
style=3D"padding: 0cm;"><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif; text-align: =
right;"><b>Date:<o:p></o:p></b></div></td><td style=3D"padding: =
0cm;"><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; =
font-family: 'Times New Roman', serif;">Wed, 4 Jun 2014 17:06:16 =
+0100<o:p></o:p></div></td></tr><tr><td nowrap=3D"" valign=3D"top" =
style=3D"padding: 0cm;"><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif; text-align: =
right;"><b>From:<o:p></o:p></b></div></td><td style=3D"padding: =
0cm;"><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; =
font-family: 'Times New Roman', serif;">Adrian Farrel<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:adrian@olddog.co.uk" style=3D"color: purple; =
text-decoration: =
underline;">&lt;adrian@olddog.co.uk&gt;</a><o:p></o:p></div></td></tr><tr>=
<td nowrap=3D"" valign=3D"top" style=3D"padding: 0cm;"><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times =
New Roman', serif; text-align: =
right;"><b>Reply-To:<o:p></o:p></b></div></td><td style=3D"padding: =
0cm;"><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; =
font-family: 'Times New Roman', serif;"><a =
href=3D"mailto:adrian@olddog.co.uk" style=3D"color: purple; =
text-decoration: =
underline;">&lt;adrian@olddog.co.uk&gt;</a><o:p></o:p></div></td></tr><tr>=
<td nowrap=3D"" valign=3D"top" style=3D"padding: 0cm;"><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times =
New Roman', serif; text-align: =
right;"><b>To:<o:p></o:p></b></div></td><td style=3D"padding: 0cm;"><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times =
New Roman', serif;"><a href=3D"mailto:bclaise@cisco.com" style=3D"color: =
purple; text-decoration: =
underline;">&lt;bclaise@cisco.com&gt;</a><o:p></o:p></div></td></tr></tbod=
y></table><p class=3D"MsoNormal" style=3D"margin: 0cm 0cm 12pt; =
font-size: 12pt; font-family: 'Times New Roman', =
serif;"><o:p>&nbsp;</o:p></p><pre style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';">Hi =
Benoit,<o:p></o:p></pre><pre style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 10pt; font-family: 'Courier =
New';"><o:p>&nbsp;</o:p></pre><pre style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';">After the work on the BFD =
MIB modules and considering the IESG statement on<o:p></o:p></pre><pre =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 10pt; font-family: =
'Courier New';">writeability, would you consider adding to the MIB =
boilerplate an optional piece<o:p></o:p></pre><pre style=3D"margin: 0cm =
0cm 0.0001pt; font-size: 10pt; font-family: 'Courier New';">of text that =
says...<o:p></o:p></pre><pre style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';"><span style=3D"color: =
rgb(31, 73, 125);">&nbsp;</span></pre><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; =
text-indent: 0cm;"><span style=3D"font-size: 11pt; font-family: =
Wingdings; color: rgb(31, 73, 125);"><span>n<span style=3D"font-style: =
normal; font-variant: normal; font-weight: normal; font-size: 7pt; =
line-height: normal; font-family: 'Times New =
Roman';">&nbsp;&nbsp;&nbsp;<span =
class=3D"Apple-converted-space">&nbsp;</span></span></span></span><span =
dir=3D"LTR"></span><span style=3D"font-size: 11pt; font-family: Calibri, =
sans-serif; color: rgb(31, 73, 125);">&nbsp;</span></div><div =
style=3D"margin: 0cm 0cm 0.0001pt 36pt; font-size: 12pt; font-family: =
'Times New Roman', serif; text-indent: -18pt;"><span style=3D"font-size: =
11pt; font-family: Wingdings; color: rgb(31, 73, 125);"><span>n<span =
style=3D"font-style: normal; font-variant: normal; font-weight: normal; =
font-size: 7pt; line-height: normal; font-family: 'Times New =
Roman';">&nbsp;<span =
class=3D"Apple-converted-space">&nbsp;</span></span></span></span><span =
dir=3D"LTR"></span><span style=3D"font-size: 11pt; font-family: Calibri, =
sans-serif; color: rgb(31, 73, 125);">Where is this text planned to be =
added? - Security considerations?<o:p></o:p></span></div><pre =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 10pt; font-family: =
'Courier New';"><span style=3D"font-size: 11pt; font-family: Calibri, =
sans-serif; color: rgb(31, 73, 125);">&nbsp;</span></pre><pre =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 10pt; font-family: =
'Courier New';">=3D=3D=3D=3D<o:p></o:p></pre><pre style=3D"margin: 0cm =
0cm 0.0001pt; font-size: 10pt; font-family: 'Courier New';">The =
following objects in the MIB modules in this document have write =
access<o:p></o:p></pre><pre style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';">either through read-write =
or read-create MAX-ACCESS clauses. The level of =
access<o:p></o:p></pre><pre style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';">to these objects have been =
discussed by the &lt;xxxx&gt; working group and it =
was<o:p></o:p></pre><pre style=3D"margin: 0cm 0cm 0.0001pt; font-size: =
10pt; font-family: 'Courier New';">concluded that write access was =
beneficial for the following reasons:<o:p></o:p></pre><pre =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 10pt; font-family: =
'Courier New';"><o:p>&nbsp;</o:p></pre><pre style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 10pt; font-family: 'Courier New';">- &lt;list of =
reasons&gt;<o:p></o:p></pre><pre style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 10pt; font-family: 'Courier =
New';"><o:p>&nbsp;</o:p></pre><pre style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';">- &lt;list of =
objects&gt;<o:p></o:p></pre><pre style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 10pt; font-family: 'Courier =
New';"><o:p>&nbsp;</o:p></pre><pre style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';">As with all MIB modules, =
an attempt to SET or CREATE an object to a value =
that<o:p></o:p></pre><pre style=3D"margin: 0cm 0cm 0.0001pt; font-size: =
10pt; font-family: 'Courier New';">is not supported by the =
implementation will result in a failure using a =
return<o:p></o:p></pre><pre style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';">code that indicates that =
the value is not supported.<o:p></o:p></pre><pre style=3D"margin: 0cm =
0cm 0.0001pt; font-size: 10pt; font-family: 'Courier New';"><span =
style=3D"font-size: 11pt; font-family: Calibri, sans-serif; color: =
rgb(31, 73, 125);">&nbsp;</span></pre><pre style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 10pt; font-family: 'Courier New'; text-indent: =
0cm;"><span style=3D"font-size: 11pt; font-family: Wingdings; color: =
rgb(31, 73, 125);"><span>n<span style=3D"font-style: normal; =
font-variant: normal; font-weight: normal; font-size: 7pt; line-height: =
normal; font-family: 'Times New Roman';">&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><span dir=3D"LTR"></span><span style=3D"font-size: =
11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">I am =
not sure that we need this paragraph. A compliant implementation will do =
what is supposed to do. Moreover, this is not about =91value not =
supported=92 but about trying to write objects that are not writeable =96 =
the error codes are different. <o:p></o:p></span></pre><pre =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 10pt; font-family: =
'Courier New';"><o:p>&nbsp;</o:p></pre><pre style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 10pt; font-family: 'Courier =
New';">=3D=3D=3D=3D<o:p></o:p></pre><pre style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 10pt; font-family: 'Courier =
New';"><o:p>&nbsp;</o:p></pre><pre style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';">I think this would help to =
contain and control work on MIB documents in the<o:p></o:p></pre><pre =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 10pt; font-family: =
'Courier New';">future, and would give the Doctors something to review =
against.<o:p></o:p></pre><pre style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 10pt; font-family: 'Courier =
New';"><o:p>&nbsp;</o:p></pre><pre style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';">Please wordsmith to your =
heart's content.<o:p></o:p></pre><pre style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 10pt; font-family: 'Courier =
New';"><o:p>&nbsp;</o:p></pre><pre style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';">Ciao,<o:p></o:p></pre><pre =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 10pt; font-family: =
'Courier New';">Adrian<o:p></o:p></pre><pre style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 10pt; font-family: 'Courier =
New';"><o:p>&nbsp;</o:p></pre><pre style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';">.<o:p></o:p></pre><pre =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 10pt; font-family: =
'Courier New';"><o:p>&nbsp;</o:p></pre><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 12pt; font-family: 'Times New Roman', =
serif;"><o:p>&nbsp;</o:p></div></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 12pt; font-family: 'Times New Roman', =
serif;"><o:p>&nbsp;</o:p></div></div></div>_______________________________=
________________<br>MIB-DOCTORS mailing list<br><a =
href=3D"mailto:MIB-DOCTORS@ietf.org" style=3D"color: purple; =
text-decoration: underline;">MIB-DOCTORS@ietf.org</a><br><a =
href=3D"https://www.ietf.org/mailman/listinfo/mib-doctors" style=3D"color:=
 purple; text-decoration: =
underline;">https://www.ietf.org/mailman/listinfo/mib-doctors</a><br></div=
></blockquote></div><br></div></body></html>=

--Apple-Mail=_7363CFAF-E141-434F-80B8-364D5F1B3EBD--

--Apple-Mail=_AECE5681-1E58-480C-A603-235589FEDC42
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJTkI0ZAAoJEPcO+I7eiUJZmIgQAJJdbwYzW3oOilu9FOnoM8Cx
yhV+qVkfOMwmiq32kRKEy5x2vnCKmDacqBrZ9VHmxqUGwxxK6jud6yLmEHZNuk6O
bOZuu7Z+X9W9FEDBBn8DXXeyQOzEwRDo69SnVbC/Xx3Hl/cS8vPo1uNnilDTbOuC
Odstl6ML/eGOX0AQAYYTSlJTbh171QhdpC87/A5KPe5B+20MGKPNvu2RPMG/x0Ra
oStLToBp+5WXy3Z7/YecN7AyojBaqaTIwjcknuOI3IQVo1wdpkl164siiccSIBqC
WMJEZTa98cimuBmAgvH//eBpZNdbwGC5Kjz0Ab7ReTbf7MFDztyPx1VwJMCyRAp8
p6idsUzMOaVAmREYzlpK+AfaE4jV++ZzsXq3caur7AvjMDnP7xJs18ugs02HRkwD
r77WhpKe0vQaDmfa+EBiBf+cSyDwzXEbAlKb9qVaitGKKPTi6d0x3T8FdaNIOGTA
0Gi8Vk2YvffaFNsxTQ6NxPe5Lo8CRV5sk9Y9ePqWoa6bPd7ZRp/w9zRTeub4/ZnW
eJDxx45o37x4aHx3obEE+Hjxx5eH9m5hbwXf3aOz4kiKhs7QjkNMLsYp/QTirBOK
1GJ5dp0PPuZtHHin/hkon2zPYf0uohfcWqWatS5C0DPamO4AzV96w07+DC8V8niV
QeoJBnX3qD6/s8FsX1/C
=9JCW
-----END PGP SIGNATURE-----

--Apple-Mail=_AECE5681-1E58-480C-A603-235589FEDC42--


From nobody Thu Jun  5 08:49:35 2014
Return-Path: <j.schoenwaelder@jacobs-university.de>
X-Original-To: mib-doctors@ietfa.amsl.com
Delivered-To: mib-doctors@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 245461A019C for <mib-doctors@ietfa.amsl.com>; Thu,  5 Jun 2014 08:49:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.201
X-Spam-Level: 
X-Spam-Status: No, score=-2.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RP_MATCHES_RCVD=-0.651] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i6wJUZcfvcnw for <mib-doctors@ietfa.amsl.com>; Thu,  5 Jun 2014 08:49:29 -0700 (PDT)
Received: from atlas3.jacobs-university.de (atlas3.jacobs-university.de [212.201.44.18]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AACA31A0143 for <mib-doctors@ietf.org>; Thu,  5 Jun 2014 08:49:29 -0700 (PDT)
Received: from localhost (demetrius5.irc-it.jacobs-university.de [10.70.0.222]) by atlas3.jacobs-university.de (Postfix) with ESMTP id 8AFED1121; Thu,  5 Jun 2014 17:49:21 +0200 (CEST)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from atlas3.jacobs-university.de ([10.70.0.220]) by localhost (demetrius5.jacobs-university.de [10.70.0.222]) (amavisd-new, port 10030) with ESMTP id FblGBxo4sdPU; Thu,  5 Jun 2014 17:49:04 +0200 (CEST)
Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hermes.jacobs-university.de", Issuer "Jacobs University CA - G01" (verified OK)) by atlas3.jacobs-university.de (Postfix) with ESMTPS; Thu,  5 Jun 2014 17:49:21 +0200 (CEST)
Received: from localhost (demetrius3.jacobs-university.de [212.201.44.48]) by hermes.jacobs-university.de (Postfix) with ESMTP id 99ED720034; Thu,  5 Jun 2014 17:49:21 +0200 (CEST)
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 OZaxIH12rBzZ; Thu,  5 Jun 2014 17:49:21 +0200 (CEST)
Received: from elstar.local (elstar.jacobs.jacobs-university.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id 6BE3D20017; Thu,  5 Jun 2014 17:49:20 +0200 (CEST)
Received: by elstar.local (Postfix, from userid 501) id 2A0D72D528F5; Thu,  5 Jun 2014 17:49:18 +0200 (CEST)
Date: Thu, 5 Jun 2014 17:49:18 +0200
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: "Thomas D. Nadeau" <tnadeau@lucidvision.com>
Message-ID: <20140605154918.GC12274@elstar.local>
Mail-Followup-To: "Thomas D. Nadeau" <tnadeau@lucidvision.com>, "Romascanu, Dan (Dan)" <dromasca@avaya.com>, "MIB Doctors (E-mail)" <mib-doctors@ietf.org>, Farrel Adrian <adrian@olddog.co.uk>
References: <07a601cf800e$ea9710e0$bfc532a0$@olddog.co.uk> <53905C1E.10808@cisco.com> <9904FB1B0159DA42B0B887B7FA8119CA5C7FE398@AZ-FFEXMB04.global.avaya.com> <4308CFC7-7341-4D66-A50C-5B808DB9FCEC@lucidvision.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4308CFC7-7341-4D66-A50C-5B808DB9FCEC@lucidvision.com>
User-Agent: Mutt/1.4.2.3i
Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/1C8uq5Uml7JVRWfnIuShOJEmFGQ
Cc: Farrel Adrian <adrian@olddog.co.uk>, "MIB Doctors \(E-mail\)" <mib-doctors@ietf.org>
Subject: Re: [MIB-DOCTORS] Fwd: Request to add to the MIB boilperplate for "writeable objects"
X-BeenThere: mib-doctors@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
List-Id: MIB Doctors list <mib-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mib-doctors/>
List-Post: <mailto:mib-doctors@ietf.org>
List-Help: <mailto:mib-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Jun 2014 15:49:34 -0000

On Thu, Jun 05, 2014 at 11:30:33AM -0400, Thomas D. Nadeau wrote:
> 
> 	I agree. This is just swimming around the drain. We need to just emphatically stop r-w and be done with this issue. 
> 

And I disagree with that. There are legitimate reasons for r-w and the
IESG statement is not generally banning r-w either.

/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 nobody Thu Jun  5 08:55:15 2014
Return-Path: <dromasca@avaya.com>
X-Original-To: mib-doctors@ietfa.amsl.com
Delivered-To: mib-doctors@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC3B41A0268 for <mib-doctors@ietfa.amsl.com>; Thu,  5 Jun 2014 08:55:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.551
X-Spam-Level: 
X-Spam-Status: No, score=-2.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hBpTAESTeen9 for <mib-doctors@ietfa.amsl.com>; Thu,  5 Jun 2014 08:55:11 -0700 (PDT)
Received: from p-us1-iereast-outbound.us1.avaya.com (p-us1-iereast-outbound.us1.avaya.com [135.11.29.13]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0E8AD1A028A for <mib-doctors@ietf.org>; Thu,  5 Jun 2014 08:55:10 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AiEOALWRkFOHCzIm/2dsb2JhbABWA4JlIlJYqloGkHaGEwGBHQGBDRZ0giUBAQEBAxIoPwwCAgIBCA0BAgEEAQEBChQJBxsXFAkIAgQBDQ0aiCABokWwUBcEhVGITCEQBwYLgxqBFQSbUoVajCCBeIFAgi8
X-IronPort-AV: E=Sophos;i="4.98,981,1392181200"; d="scan'208";a="69209779"
Received: from unknown (HELO p-us1-erheast-smtpauth.us1.avaya.com) ([135.11.50.38]) by p-us1-iereast-outbound.us1.avaya.com with ESMTP; 05 Jun 2014 11:55:03 -0400
X-OutboundMail_SMTP: 1
Received: from unknown (HELO AZ-FFEXHC03.global.avaya.com) ([135.64.58.13]) by p-us1-erheast-out.us1.avaya.com with ESMTP/TLS/AES128-SHA; 05 Jun 2014 11:52:53 -0400
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC03.global.avaya.com ([135.64.58.13]) with mapi id 14.03.0174.001; Thu, 5 Jun 2014 11:55:02 -0400
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>, "Thomas D. Nadeau" <tnadeau@lucidvision.com>
Thread-Topic: [MIB-DOCTORS] Fwd: Request to add to the MIB boilperplate for "writeable objects"
Thread-Index: AQHPgNMa9hspz4I5cUmg13WnE0nn1Jti7NMA//+9lzA=
Date: Thu, 5 Jun 2014 15:55:01 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA5C7FE794@AZ-FFEXMB04.global.avaya.com>
References: <07a601cf800e$ea9710e0$bfc532a0$@olddog.co.uk> <53905C1E.10808@cisco.com> <9904FB1B0159DA42B0B887B7FA8119CA5C7FE398@AZ-FFEXMB04.global.avaya.com> <4308CFC7-7341-4D66-A50C-5B808DB9FCEC@lucidvision.com> <20140605154918.GC12274@elstar.local>
In-Reply-To: <20140605154918.GC12274@elstar.local>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.64.58.45]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/d7p4ttObq6H-0Ob6mGE9iI2BRHc
Cc: "MIB Doctors \(E-mail\)" <mib-doctors@ietf.org>, Farrel Adrian <adrian@olddog.co.uk>
Subject: Re: [MIB-DOCTORS] Fwd: Request to add to the MIB boilperplate for "writeable objects"
X-BeenThere: mib-doctors@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: MIB Doctors list <mib-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mib-doctors/>
List-Post: <mailto:mib-doctors@ietf.org>
List-Help: <mailto:mib-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Jun 2014 15:55:13 -0000

+1 to what Juergen says. The boilerplate change should reflect what the IES=
G stated. It's just that the text has some words that are not necessary (la=
st paragraph) and it does not seem to belong to Security Considerations, so=
 we need to find it another place ('Read-Write Considerations' section?)

Dan

> -----Original Message-----
> From: Juergen Schoenwaelder [mailto:j.schoenwaelder@jacobs-
> university.de]
> Sent: Thursday, June 05, 2014 6:49 PM
> To: Thomas D. Nadeau
> Cc: Romascanu, Dan (Dan); MIB Doctors (E-mail); Farrel Adrian
> Subject: Re: [MIB-DOCTORS] Fwd: Request to add to the MIB boilperplate fo=
r
> "writeable objects"
>=20
> On Thu, Jun 05, 2014 at 11:30:33AM -0400, Thomas D. Nadeau wrote:
> >
> > 	I agree. This is just swimming around the drain. We need to just
> emphatically stop r-w and be done with this issue.
> >
>=20
> And I disagree with that. There are legitimate reasons for r-w and the IE=
SG
> statement is not generally banning r-w either.
>=20
> /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 nobody Thu Jun  5 08:55:24 2014
Return-Path: <macfaden@gmail.com>
X-Original-To: mib-doctors@ietfa.amsl.com
Delivered-To: mib-doctors@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C91031A029F for <mib-doctors@ietfa.amsl.com>; Thu,  5 Jun 2014 08:55:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.277
X-Spam-Level: 
X-Spam-Status: No, score=-1.277 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yZ7ftt6tNoYf for <mib-doctors@ietfa.amsl.com>; Thu,  5 Jun 2014 08:55:17 -0700 (PDT)
Received: from mail-qa0-x22a.google.com (mail-qa0-x22a.google.com [IPv6:2607:f8b0:400d:c00::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 52BFE1A02A5 for <mib-doctors@ietf.org>; Thu,  5 Jun 2014 08:55:17 -0700 (PDT)
Received: by mail-qa0-f42.google.com with SMTP id j5so1656144qaq.29 for <mib-doctors@ietf.org>; Thu, 05 Jun 2014 08:55:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:content-type; bh=86WH48lO4swk2GGoCwkasvdeKHqqRvPUPr8xp+5crs4=; b=JhOc+i+h0Xq1qQmNdjUvnaC2BJf+cWZrBd+YGw1UfWsNMF7drfQk4VDn5Zp8/+UDKq Z+FYk6lko9TY8vgwOKVjeB3sft/jWmXek79grOJ2ye5SWahlJFra5lY7HOYQaLqVjBS6 AvBOJzAHsmPSh3OgYIwQCOSSaPA67nq8ncdJt+8QoOTbJiNiy+x2Qv3+f6OWFUAF7tfx 90pbqdhwzR80cQonvzoY6mkZPqxJuSxOY9hH9eECTZL1HlhVuEl3o2oAGaBs0saopnB4 JPlBlr0wSCugLeLMgUZoVZUfX4zokvG+Ty5nHh/tyHMfchE/s+65KBRBk1X9AWw92jNl cAnQ==
MIME-Version: 1.0
X-Received: by 10.224.7.6 with SMTP id b6mr18903072qab.45.1401983709957; Thu, 05 Jun 2014 08:55:09 -0700 (PDT)
Sender: macfaden@gmail.com
Received: by 10.140.95.112 with HTTP; Thu, 5 Jun 2014 08:55:09 -0700 (PDT)
In-Reply-To: <20140605123554.GA11717@elstar.local>
References: <07a601cf800e$ea9710e0$bfc532a0$@olddog.co.uk> <53905C1E.10808@cisco.com> <20140605123554.GA11717@elstar.local>
Date: Thu, 5 Jun 2014 08:55:09 -0700
X-Google-Sender-Auth: ljocVX6978kneAyakGTEsB_Er58
Message-ID: <CAD3a8Tn4L8Fi4Y2rO9ohEhDW9UgW1iJVLzGjcVOA=i+ALaTraQ@mail.gmail.com>
From: Michael MacFaden <mrm@macfaden.com>
To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>, Benoit Claise <bclaise@cisco.com>,  "MIB Doctors (E-mail)" <mib-doctors@ietf.org>, Adrian Farrel <adrian@olddog.co.uk>
Content-Type: multipart/alternative; boundary=001a11c28ea00354dc04fb18c524
Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/idjM_-mlEGXrToiPzR0zFZUntn4
Subject: Re: [MIB-DOCTORS] Fwd: Request to add to the MIB boilperplate for "writeable objects"
X-BeenThere: mib-doctors@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: MIB Doctors list <mib-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mib-doctors/>
List-Post: <mailto:mib-doctors@ietf.org>
List-Help: <mailto:mib-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Jun 2014 15:55:19 -0000

--001a11c28ea00354dc04fb18c524
Content-Type: text/plain; charset=UTF-8

+1. What Juergen said.


> with all MIB modules, an attempt to SET or CREATE an object to a value that

>is not supported by the implementation will result in a failure using a return

>code that indicates that the value is not supported.


No kidding? Sometimes agent even crash. This is tutorial material.


Mike



On Thu, Jun 5, 2014 at 5:35 AM, Juergen Schoenwaelder <
j.schoenwaelder@jacobs-university.de> wrote:

> On Thu, Jun 05, 2014 at 02:01:34PM +0200, Benoit Claise wrote:
>
> > The following objects in the MIB modules in this document have write
> access
> > either through read-write or read-create MAX-ACCESS clauses. The level of
> > access
> > to these objects have been discussed by the <xxxx> working group and it
> was
> > concluded that write access was beneficial for the following reasons:
> >
> > - <list of reasons>
> >
> > - <list of objects>
>
> I wonder why this belongs into the security considerations
> section. This is a design decision, only marginally related to
> security considerations.
>
> > As with all MIB modules, an attempt to SET or CREATE an object to a
> > value that is not supported by the implementation will result in a
> > failure using a return code that indicates that the value is not
> > supported.
>
> This is all regulated in RFC 3416. I fail to see why this now have to
> repeat this in security considerations (12 years after RFC 3416 got
> published and lots of MIB modules got published).
>
> > I think this would help to contain and control work on MIB documents in
> the
> > future, and would give the Doctors something to review against.
>
> Security considerations are IMHO the wrong place to document IETF
> policies. I do not think the security properties of SNMP have changed
> and I also believe the recent IESG statement was not motivated by
> security concerns.
>
> /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/>
>
> _______________________________________________
> MIB-DOCTORS mailing list
> MIB-DOCTORS@ietf.org
> https://www.ietf.org/mailman/listinfo/mib-doctors
>

--001a11c28ea00354dc04fb18c524
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div style><br></div>+1. What Juergen said.<div><br><div><=
br></div><div><pre style=3D"white-space:pre-wrap;color:rgb(80,0,80);font-si=
ze:13.513513565063477px">&gt; with all MIB modules, an attempt to SET or CR=
EATE an object to a value that<u></u><u></u></pre>
<pre style=3D"white-space:pre-wrap;color:rgb(80,0,80);font-size:13.51351356=
5063477px">&gt;is not supported by the implementation will result in a fail=
ure using a return<u></u><u></u></pre><pre style=3D"white-space:pre-wrap;co=
lor:rgb(80,0,80);font-size:13.513513565063477px">
&gt;code that indicates that the value is not supported.<u></u><u></u></pre=
></div><div><br></div><div style>No kidding? Sometimes agent even crash. Th=
is is tutorial material.</div><div style><br></div><div><br></div><div styl=
e>
Mike</div><div style><br></div></div></div><div class=3D"gmail_extra"><br><=
br><div class=3D"gmail_quote">On Thu, Jun 5, 2014 at 5:35 AM, Juergen Schoe=
nwaelder <span dir=3D"ltr">&lt;<a href=3D"mailto:j.schoenwaelder@jacobs-uni=
versity.de" target=3D"_blank">j.schoenwaelder@jacobs-university.de</a>&gt;<=
/span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"">On Thu, Jun 05, 2014 at 02:0=
1:34PM +0200, Benoit Claise wrote:<br>
<br>
&gt; The following objects in the MIB modules in this document have write a=
ccess<br>
&gt; either through read-write or read-create MAX-ACCESS clauses. The level=
 of<br>
&gt; access<br>
&gt; to these objects have been discussed by the &lt;xxxx&gt; working group=
 and it was<br>
&gt; concluded that write access was beneficial for the following reasons:<=
br>
&gt;<br>
&gt; - &lt;list of reasons&gt;<br>
&gt;<br>
&gt; - &lt;list of objects&gt;<br>
<br>
</div>I wonder why this belongs into the security considerations<br>
section. This is a design decision, only marginally related to<br>
security considerations.<br>
<div class=3D""><br>
&gt; As with all MIB modules, an attempt to SET or CREATE an object to a<br=
>
&gt; value that is not supported by the implementation will result in a<br>
&gt; failure using a return code that indicates that the value is not<br>
&gt; supported.<br>
<br>
</div>This is all regulated in RFC 3416. I fail to see why this now have to=
<br>
repeat this in security considerations (12 years after RFC 3416 got<br>
published and lots of MIB modules got published).<br>
<div class=3D""><br>
&gt; I think this would help to contain and control work on MIB documents i=
n the<br>
&gt; future, and would give the Doctors something to review against.<br>
<br>
</div>Security considerations are IMHO the wrong place to document IETF<br>
policies. I do not think the security properties of SNMP have changed<br>
and I also believe the recent IESG statement was not motivated by<br>
security concerns.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
/js<br>
<br>
--<br>
Juergen Schoenwaelder =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Jacobs University =
Bremen gGmbH<br>
Phone: <a href=3D"tel:%2B49%20421%20200%203587" value=3D"+494212003587">+49=
 421 200 3587</a> =C2=A0 =C2=A0 =C2=A0 =C2=A0 Campus Ring 1, 28759 Bremen, =
Germany<br>
Fax: =C2=A0 <a href=3D"tel:%2B49%20421%20200%203103" value=3D"+494212003103=
">+49 421 200 3103</a> =C2=A0 =C2=A0 =C2=A0 =C2=A0 &lt;<a href=3D"http://ww=
w.jacobs-university.de/" target=3D"_blank">http://www.jacobs-university.de/=
</a>&gt;<br>
<br>
_______________________________________________<br>
MIB-DOCTORS mailing list<br>
<a href=3D"mailto:MIB-DOCTORS@ietf.org">MIB-DOCTORS@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/mib-doctors" target=3D"_bl=
ank">https://www.ietf.org/mailman/listinfo/mib-doctors</a><br>
</font></span></blockquote></div><br></div>

--001a11c28ea00354dc04fb18c524--


From nobody Thu Jun  5 09:22:04 2014
Return-Path: <andy@yumaworks.com>
X-Original-To: mib-doctors@ietfa.amsl.com
Delivered-To: mib-doctors@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 51FD81A02C4 for <mib-doctors@ietfa.amsl.com>; Thu,  5 Jun 2014 09:21:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.278
X-Spam-Level: 
X-Spam-Status: No, score=-1.278 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TZi8apHRmnB1 for <mib-doctors@ietfa.amsl.com>; Thu,  5 Jun 2014 09:21:56 -0700 (PDT)
Received: from mail-qg0-f54.google.com (mail-qg0-f54.google.com [209.85.192.54]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B9D4C1A033C for <mib-doctors@ietf.org>; Thu,  5 Jun 2014 09:21:55 -0700 (PDT)
Received: by mail-qg0-f54.google.com with SMTP id q108so1941117qgd.41 for <mib-doctors@ietf.org>; Thu, 05 Jun 2014 09:21:48 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=mgZzQDrYCrsuQd0Vbb9uNUXyss07q8mO9U1vKuUvxLM=; b=QT7OE8ueGeT5YvLHssmkD4zFXs6/7G/67baMtV6O8EDetyIRZD8w9LA7N0CGImV7KL 4wM0fNNM9EfSRjv5M1jyvnXterOJgVzrFGGWpOOoXfxhJewf8Tmw2vcbq0U2n5ljOxWo LH/rncvMGZTMD1kU0CM4Wrs/Y8/32JqzA3Wr1lYmDEbwBWah/88ISlIWRjelzJgsyLnp 1gYi6d3DNtMi9CegupGcddHO/VGl7FDVtgQgTHTgA2s2OoSyQ3+QQ9mzdf2xqATkkPyo GWycpUVOmAr1sRBAjfZY/ng29iACwcMfMyKzqrREwXa0bTDkK8ncWJB4m8K3eU8gE3o7 s5tQ==
X-Gm-Message-State: ALoCoQkhqE6jtfvJDfFndF/CV1H7apR4N+SBk86Aq78sADvEHAZDDLwYOps/tyB62ffYTvwZyyqc
MIME-Version: 1.0
X-Received: by 10.140.41.75 with SMTP id y69mr79438433qgy.34.1401985308772; Thu, 05 Jun 2014 09:21:48 -0700 (PDT)
Received: by 10.140.104.49 with HTTP; Thu, 5 Jun 2014 09:21:48 -0700 (PDT)
In-Reply-To: <CAD3a8Tn4L8Fi4Y2rO9ohEhDW9UgW1iJVLzGjcVOA=i+ALaTraQ@mail.gmail.com>
References: <07a601cf800e$ea9710e0$bfc532a0$@olddog.co.uk> <53905C1E.10808@cisco.com> <20140605123554.GA11717@elstar.local> <CAD3a8Tn4L8Fi4Y2rO9ohEhDW9UgW1iJVLzGjcVOA=i+ALaTraQ@mail.gmail.com>
Date: Thu, 5 Jun 2014 09:21:48 -0700
Message-ID: <CABCOCHRn80jmFbMO2jB9TVTDirZ2Xc0uxPxQzHtcWZmksQJ1bA@mail.gmail.com>
From: Andy Bierman <andy@yumaworks.com>
To: Michael MacFaden <mrm@macfaden.com>
Content-Type: multipart/alternative; boundary=001a11c126ba4f621804fb1924ba
Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/zH-5R8uDz-I44wv3Ur9HcnAendc
Cc: "MIB Doctors \(E-mail\)" <mib-doctors@ietf.org>, Adrian Farrel <adrian@olddog.co.uk>
Subject: Re: [MIB-DOCTORS] Fwd: Request to add to the MIB boilperplate for "writeable objects"
X-BeenThere: mib-doctors@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: MIB Doctors list <mib-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mib-doctors/>
List-Post: <mailto:mib-doctors@ietf.org>
List-Help: <mailto:mib-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Jun 2014 16:21:58 -0000

--001a11c126ba4f621804fb1924ba
Content-Type: text/plain; charset=ISO-8859-1

Hi,

Getting back to the original question:

  s/attempt to SET or CREATE/attempt to SET/

SNMP does not have a CREATE PDU AFAIK.

On your new thread: +1 for no statement on read-write use.

Somebody implementing the SMIv2 to YANG translation (RFC 6643)
asked me this week how to deal with read-write in YANG.
The mapping is read-only, so I told him out-of-scope ;-)
There is no mapping in YANG. IMO a bug, not a feature.
We have an extension statement to provide read-write semantics in YANG.
IMO SMIv2 read-write closely describes the semantics YANG needs
for 'system-owned' config data.


Andy


On Thu, Jun 5, 2014 at 8:55 AM, Michael MacFaden <mrm@macfaden.com> wrote:

>
> +1. What Juergen said.
>
>
> > with all MIB modules, an attempt to SET or CREATE an object to a value that
>
> >is not supported by the implementation will result in a failure using a return
>
> >code that indicates that the value is not supported.
>
>
> No kidding? Sometimes agent even crash. This is tutorial material.
>
>
> Mike
>
>
>
> On Thu, Jun 5, 2014 at 5:35 AM, Juergen Schoenwaelder <
> j.schoenwaelder@jacobs-university.de> wrote:
>
>> On Thu, Jun 05, 2014 at 02:01:34PM +0200, Benoit Claise wrote:
>>
>> > The following objects in the MIB modules in this document have write
>> access
>> > either through read-write or read-create MAX-ACCESS clauses. The level
>> of
>> > access
>> > to these objects have been discussed by the <xxxx> working group and it
>> was
>> > concluded that write access was beneficial for the following reasons:
>> >
>> > - <list of reasons>
>> >
>> > - <list of objects>
>>
>> I wonder why this belongs into the security considerations
>> section. This is a design decision, only marginally related to
>> security considerations.
>>
>> > As with all MIB modules, an attempt to SET or CREATE an object to a
>> > value that is not supported by the implementation will result in a
>> > failure using a return code that indicates that the value is not
>> > supported.
>>
>> This is all regulated in RFC 3416. I fail to see why this now have to
>> repeat this in security considerations (12 years after RFC 3416 got
>> published and lots of MIB modules got published).
>>
>> > I think this would help to contain and control work on MIB documents in
>> the
>> > future, and would give the Doctors something to review against.
>>
>> Security considerations are IMHO the wrong place to document IETF
>> policies. I do not think the security properties of SNMP have changed
>> and I also believe the recent IESG statement was not motivated by
>> security concerns.
>>
>> /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/>
>>
>> _______________________________________________
>> MIB-DOCTORS mailing list
>> MIB-DOCTORS@ietf.org
>> https://www.ietf.org/mailman/listinfo/mib-doctors
>>
>
>
> _______________________________________________
> MIB-DOCTORS mailing list
> MIB-DOCTORS@ietf.org
> https://www.ietf.org/mailman/listinfo/mib-doctors
>
>

--001a11c126ba4f621804fb1924ba
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi,<div><br></div><div>Getting back to the original questi=
on:</div><div><br></div><div>=A0 s/attempt to SET or CREATE/attempt to SET/=
</div><div><br></div><div>SNMP does not have a CREATE PDU AFAIK.</div><div>=
<br>
</div><div>On your new thread: +1 for no statement on read-write use.</div>=
<div><br></div><div>Somebody implementing the SMIv2 to YANG translation (RF=
C 6643)</div><div>asked me this week how to deal with read-write in YANG.</=
div>
<div>The mapping is read-only, so I told him out-of-scope ;-)</div><div>The=
re is no mapping in YANG. IMO a bug, not a feature.<br></div><div>We have a=
n extension statement to provide read-write semantics in YANG.</div><div>
<div class=3D"gmail_extra">IMO SMIv2 read-write closely describes the seman=
tics YANG needs</div><div class=3D"gmail_extra">for &#39;system-owned&#39; =
config data.<br><br><br>Andy</div><div class=3D"gmail_extra"><br></div><div=
 class=3D"gmail_extra">
<br><div class=3D"gmail_quote">On Thu, Jun 5, 2014 at 8:55 AM, Michael MacF=
aden <span dir=3D"ltr">&lt;<a href=3D"mailto:mrm@macfaden.com" target=3D"_b=
lank">mrm@macfaden.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_=
quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-=
color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div dir=3D"ltr"><div><br></div>+1. What Juergen said.<div><br><div><br></d=
iv><div><pre style=3D"white-space:pre-wrap;color:rgb(80,0,80);font-size:13.=
513513565063477px">&gt; with all MIB modules, an attempt to SET or CREATE a=
n object to a value that<u></u><u></u></pre>

<pre style=3D"white-space:pre-wrap;color:rgb(80,0,80);font-size:13.51351356=
5063477px">&gt;is not supported by the implementation will result in a fail=
ure using a return<u></u><u></u></pre><pre style=3D"white-space:pre-wrap;co=
lor:rgb(80,0,80);font-size:13.513513565063477px">
&gt;code that indicates that the value is not supported.<u></u><u></u></pre=
></div><div><br></div><div>No kidding? Sometimes agent even crash. This is =
tutorial material.</div><div><br></div><div><br></div><div>
Mike</div><div><br></div></div></div><div class=3D"gmail_extra"><br><br><di=
v class=3D"gmail_quote">On Thu, Jun 5, 2014 at 5:35 AM, Juergen Schoenwaeld=
er <span dir=3D"ltr">&lt;<a href=3D"mailto:j.schoenwaelder@jacobs-universit=
y.de" target=3D"_blank">j.schoenwaelder@jacobs-university.de</a>&gt;</span>=
 wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex"><div>On Thu, Jun 05, 2014 at 02:01:34PM +0200, Benoit Clai=
se wrote:<br>

<br>
&gt; The following objects in the MIB modules in this document have write a=
ccess<br>
&gt; either through read-write or read-create MAX-ACCESS clauses. The level=
 of<br>
&gt; access<br>
&gt; to these objects have been discussed by the &lt;xxxx&gt; working group=
 and it was<br>
&gt; concluded that write access was beneficial for the following reasons:<=
br>
&gt;<br>
&gt; - &lt;list of reasons&gt;<br>
&gt;<br>
&gt; - &lt;list of objects&gt;<br>
<br>
</div>I wonder why this belongs into the security considerations<br>
section. This is a design decision, only marginally related to<br>
security considerations.<br>
<div><br>
&gt; As with all MIB modules, an attempt to SET or CREATE an object to a<br=
>
&gt; value that is not supported by the implementation will result in a<br>
&gt; failure using a return code that indicates that the value is not<br>
&gt; supported.<br>
<br>
</div>This is all regulated in RFC 3416. I fail to see why this now have to=
<br>
repeat this in security considerations (12 years after RFC 3416 got<br>
published and lots of MIB modules got published).<br>
<div><br>
&gt; I think this would help to contain and control work on MIB documents i=
n the<br>
&gt; future, and would give the Doctors something to review against.<br>
<br>
</div>Security considerations are IMHO the wrong place to document IETF<br>
policies. I do not think the security properties of SNMP have changed<br>
and I also believe the recent IESG statement was not motivated by<br>
security concerns.<br>
<span><font color=3D"#888888"><br>
/js<span class=3D""><font color=3D"#888888"><br>
<br>
--<br>
Juergen Schoenwaelder =A0 =A0 =A0 =A0 =A0 Jacobs University Bremen gGmbH<br=
>
Phone: <a href=3D"tel:%2B49%20421%20200%203587" value=3D"+494212003587" tar=
get=3D"_blank">+49 421 200 3587</a> =A0 =A0 =A0 =A0 Campus Ring 1, 28759 Br=
emen, Germany<br>
Fax: =A0 <a href=3D"tel:%2B49%20421%20200%203103" value=3D"+494212003103" t=
arget=3D"_blank">+49 421 200 3103</a> =A0 =A0 =A0 =A0 &lt;<a href=3D"http:/=
/www.jacobs-university.de/" target=3D"_blank">http://www.jacobs-university.=
de/</a>&gt;<br>

<br>
_______________________________________________<br>
MIB-DOCTORS mailing list<br>
<a href=3D"mailto:MIB-DOCTORS@ietf.org" target=3D"_blank">MIB-DOCTORS@ietf.=
org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/mib-doctors" target=3D"_bl=
ank">https://www.ietf.org/mailman/listinfo/mib-doctors</a><br>
</font></span></font></span></blockquote></div><br></div>
<br>_______________________________________________<br>
MIB-DOCTORS mailing list<br>
<a href=3D"mailto:MIB-DOCTORS@ietf.org">MIB-DOCTORS@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/mib-doctors" target=3D"_bl=
ank">https://www.ietf.org/mailman/listinfo/mib-doctors</a><br>
<br></blockquote></div><br></div></div></div>

--001a11c126ba4f621804fb1924ba--


From nobody Thu Jun  5 09:34:45 2014
Return-Path: <j.schoenwaelder@jacobs-university.de>
X-Original-To: mib-doctors@ietfa.amsl.com
Delivered-To: mib-doctors@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 722A51A02EA for <mib-doctors@ietfa.amsl.com>; Thu,  5 Jun 2014 09:34:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.201
X-Spam-Level: 
X-Spam-Status: No, score=-2.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RP_MATCHES_RCVD=-0.651] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id G9qpVUQx1HEe for <mib-doctors@ietfa.amsl.com>; Thu,  5 Jun 2014 09:34:43 -0700 (PDT)
Received: from atlas3.jacobs-university.de (atlas3.jacobs-university.de [212.201.44.18]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 969011A021A for <mib-doctors@ietf.org>; Thu,  5 Jun 2014 09:34:42 -0700 (PDT)
Received: from localhost (demetrius5.irc-it.jacobs-university.de [10.70.0.222]) by atlas3.jacobs-university.de (Postfix) with ESMTP id C19F6AC9; Thu,  5 Jun 2014 18:34:34 +0200 (CEST)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from atlas3.jacobs-university.de ([10.70.0.220]) by localhost (demetrius5.jacobs-university.de [10.70.0.222]) (amavisd-new, port 10030) with ESMTP id ORkmV7NC3cgv; Thu,  5 Jun 2014 18:34:17 +0200 (CEST)
Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hermes.jacobs-university.de", Issuer "Jacobs University CA - G01" (verified OK)) by atlas3.jacobs-university.de (Postfix) with ESMTPS; Thu,  5 Jun 2014 18:34:34 +0200 (CEST)
Received: from localhost (demetrius4.jacobs-university.de [212.201.44.49]) by hermes.jacobs-university.de (Postfix) with ESMTP id CF2CC20017; Thu,  5 Jun 2014 18:34:34 +0200 (CEST)
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 HXyEjLXr2e53; Thu,  5 Jun 2014 18:34:34 +0200 (CEST)
Received: from elstar.local (elstar.jacobs.jacobs-university.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id 022F720013; Thu,  5 Jun 2014 18:34:34 +0200 (CEST)
Received: by elstar.local (Postfix, from userid 501) id 11BA72D5297C; Thu,  5 Jun 2014 18:34:32 +0200 (CEST)
Date: Thu, 5 Jun 2014 18:34:32 +0200
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: Andy Bierman <andy@yumaworks.com>
Message-ID: <20140605163432.GD12274@elstar.local>
Mail-Followup-To: Andy Bierman <andy@yumaworks.com>, Michael MacFaden <mrm@macfaden.com>, Benoit Claise <bclaise@cisco.com>, "MIB Doctors (E-mail)" <mib-doctors@ietf.org>, Adrian Farrel <adrian@olddog.co.uk>
References: <07a601cf800e$ea9710e0$bfc532a0$@olddog.co.uk> <53905C1E.10808@cisco.com> <20140605123554.GA11717@elstar.local> <CAD3a8Tn4L8Fi4Y2rO9ohEhDW9UgW1iJVLzGjcVOA=i+ALaTraQ@mail.gmail.com> <CABCOCHRn80jmFbMO2jB9TVTDirZ2Xc0uxPxQzHtcWZmksQJ1bA@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CABCOCHRn80jmFbMO2jB9TVTDirZ2Xc0uxPxQzHtcWZmksQJ1bA@mail.gmail.com>
User-Agent: Mutt/1.4.2.3i
Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/sSawxZoh25S0ZKklDRVeWpUxVr8
Cc: Michael MacFaden <mrm@macfaden.com>, Adrian Farrel <adrian@olddog.co.uk>, "MIB Doctors \(E-mail\)" <mib-doctors@ietf.org>
Subject: Re: [MIB-DOCTORS] Fwd: Request to add to the MIB boilperplate for "writeable objects"
X-BeenThere: mib-doctors@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
List-Id: MIB Doctors list <mib-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mib-doctors/>
List-Post: <mailto:mib-doctors@ietf.org>
List-Help: <mailto:mib-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Jun 2014 16:34:44 -0000

On Thu, Jun 05, 2014 at 09:21:48AM -0700, Andy Bierman wrote:
> 
> Somebody implementing the SMIv2 to YANG translation (RFC 6643)
> asked me this week how to deal with read-write in YANG.
> The mapping is read-only, so I told him out-of-scope ;-)
> There is no mapping in YANG. IMO a bug, not a feature.
> We have an extension statement to provide read-write semantics in YANG.
> IMO SMIv2 read-write closely describes the semantics YANG needs
> for 'system-owned' config data.
> 

This is getting off topic but the reasons why this is read-only are
explained in Section 11 of RFC 6643.

/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 nobody Thu Jun  5 09:44:34 2014
Return-Path: <andy@yumaworks.com>
X-Original-To: mib-doctors@ietfa.amsl.com
Delivered-To: mib-doctors@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 570111A017F for <mib-doctors@ietfa.amsl.com>; Thu,  5 Jun 2014 09:44:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.278
X-Spam-Level: 
X-Spam-Status: No, score=-1.278 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qmvVUnbZAhqJ for <mib-doctors@ietfa.amsl.com>; Thu,  5 Jun 2014 09:44:32 -0700 (PDT)
Received: from mail-qg0-f41.google.com (mail-qg0-f41.google.com [209.85.192.41]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2BB9F1A0075 for <mib-doctors@ietf.org>; Thu,  5 Jun 2014 09:44:32 -0700 (PDT)
Received: by mail-qg0-f41.google.com with SMTP id j5so2036949qga.14 for <mib-doctors@ietf.org>; Thu, 05 Jun 2014 09:44:25 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=V4hXcAAajdyfuKd95lbQXD+fOocrO8W3pgCD3weSkPE=; b=fZwgZqaawoIAbYvHhSN6p+TA7wWEPH+6jc7Dj+f+4nryhd+wNRumHL12L0kghPwwTl /2VibUUVn0KMUEBxxucEjbHgzo2a/300FGQSykDWzJX1bs6YtglyfJSyZ9ocYUGo/SMf YERgzICG/3k7zJEdmF8TcWali7dJ5BdLAyzhOwvnjPUCAsVKzF31NXUa9z6uwLgSquZd xj7aQGVMNa9KIoqKRXfKPGYBV5NvaBpPDk4LnL+egEZjAb6lLkH43VErjTqbUQ4JQpRQ EWUm9JByiSsxup0U3dj3IJTscUIrojVUWGOJkKfxJRQuO2j5O4pi67zVCaWmjVsTEHwA O2Bg==
X-Gm-Message-State: ALoCoQmFn66HJ2vAny/uWVEJnBR9/jvhbriBo1EEPc4jayuff55eIbKplF9wzugpZ/pRsAaPhXpc
MIME-Version: 1.0
X-Received: by 10.224.64.132 with SMTP id e4mr84426335qai.16.1401986665323; Thu, 05 Jun 2014 09:44:25 -0700 (PDT)
Received: by 10.140.104.49 with HTTP; Thu, 5 Jun 2014 09:44:25 -0700 (PDT)
In-Reply-To: <20140605163432.GD12274@elstar.local>
References: <07a601cf800e$ea9710e0$bfc532a0$@olddog.co.uk> <53905C1E.10808@cisco.com> <20140605123554.GA11717@elstar.local> <CAD3a8Tn4L8Fi4Y2rO9ohEhDW9UgW1iJVLzGjcVOA=i+ALaTraQ@mail.gmail.com> <CABCOCHRn80jmFbMO2jB9TVTDirZ2Xc0uxPxQzHtcWZmksQJ1bA@mail.gmail.com> <20140605163432.GD12274@elstar.local>
Date: Thu, 5 Jun 2014 09:44:25 -0700
Message-ID: <CABCOCHQc-tKzxrD0diukS-7uK3X3dh1yRVR0H9JB4EZeEgCoiQ@mail.gmail.com>
From: Andy Bierman <andy@yumaworks.com>
To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>, Andy Bierman <andy@yumaworks.com>,  Michael MacFaden <mrm@macfaden.com>, Benoit Claise <bclaise@cisco.com>,  "MIB Doctors (E-mail)" <mib-doctors@ietf.org>, Adrian Farrel <adrian@olddog.co.uk>
Content-Type: multipart/alternative; boundary=001a11c20e7a2ad04604fb197540
Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/QP7f0emft9yQWLzEM1xItO7L5JA
Subject: Re: [MIB-DOCTORS] Fwd: Request to add to the MIB boilperplate for "writeable objects"
X-BeenThere: mib-doctors@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: MIB Doctors list <mib-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mib-doctors/>
List-Post: <mailto:mib-doctors@ietf.org>
List-Help: <mailto:mib-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Jun 2014 16:44:33 -0000

--001a11c20e7a2ad04604fb197540
Content-Type: text/plain; charset=ISO-8859-1

On Thu, Jun 5, 2014 at 9:34 AM, Juergen Schoenwaelder <
j.schoenwaelder@jacobs-university.de> wrote:

> On Thu, Jun 05, 2014 at 09:21:48AM -0700, Andy Bierman wrote:
> >
> > Somebody implementing the SMIv2 to YANG translation (RFC 6643)
> > asked me this week how to deal with read-write in YANG.
> > The mapping is read-only, so I told him out-of-scope ;-)
> > There is no mapping in YANG. IMO a bug, not a feature.
> > We have an extension statement to provide read-write semantics in YANG.
> > IMO SMIv2 read-write closely describes the semantics YANG needs
> > for 'system-owned' config data.
> >
>
> This is getting off topic but the reasons why this is read-only are
> explained in Section 11 of RFC 6643.
>
>

fair enough, but...

The IESG is saying use NETCONF for new stuff and it's OK to
keep using SNMP read-create and read-only when there is good cause.
But there is no transition strategy to move from row-based SNMP to
datastore-based NETCONF, for writable objects.

The fact that a large vendor is attempting to implement the
translation for writable objects suggests a migration strategy is needed.



> /js
>
>
Andy


> --
> 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/>
>

--001a11c20e7a2ad04604fb197540
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On Thu, Jun 5, 2014 at 9:34 AM, Juergen Schoenwaelder <span dir=3D"=
ltr">&lt;<a href=3D"mailto:j.schoenwaelder@jacobs-university.de" target=3D"=
_blank">j.schoenwaelder@jacobs-university.de</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">On Thu, Jun 05, 2014 at 09:21:48AM -0700, An=
dy Bierman wrote:<br>
&gt;<br>
&gt; Somebody implementing the SMIv2 to YANG translation (RFC 6643)<br>
&gt; asked me this week how to deal with read-write in YANG.<br>
&gt; The mapping is read-only, so I told him out-of-scope ;-)<br>
&gt; There is no mapping in YANG. IMO a bug, not a feature.<br>
&gt; We have an extension statement to provide read-write semantics in YANG=
.<br>
&gt; IMO SMIv2 read-write closely describes the semantics YANG needs<br>
&gt; for &#39;system-owned&#39; config data.<br>
&gt;<br>
<br>
This is getting off topic but the reasons why this is read-only are<br>
explained in Section 11 of RFC 6643.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br></font></span></blockquo=
te><div><br></div><div><br></div><div>fair enough, but...</div><div><br></d=
iv><div>The IESG is saying use NETCONF for new stuff and it&#39;s OK to</di=
v>
<div>keep using SNMP read-create and read-only when there is good cause.</d=
iv><div>But there is no transition strategy to move from row-based SNMP to<=
/div><div>datastore-based NETCONF, for writable objects.</div><div><br>
</div><div>The fact that a large vendor is attempting to implement the</div=
><div>translation for writable objects suggests a migration strategy is nee=
ded.</div><div><br></div><div>=A0</div><blockquote class=3D"gmail_quote" st=
yle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<span class=3D"HOEnZb"><font color=3D"#888888">
/js<br>
<br></font></span></blockquote><div><br></div><div>Andy</div><div>=A0</div>=
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><span class=3D"HOEnZb"><font color=3D"#88888=
8">
--<br>
Juergen Schoenwaelder =A0 =A0 =A0 =A0 =A0 Jacobs University Bremen gGmbH<br=
>
Phone: +49 421 200 3587 =A0 =A0 =A0 =A0 Campus Ring 1, 28759 Bremen, German=
y<br>
Fax: =A0 +49 421 200 3103 =A0 =A0 =A0 =A0 &lt;<a href=3D"http://www.jacobs-=
university.de/" target=3D"_blank">http://www.jacobs-university.de/</a>&gt;<=
br>
</font></span></blockquote></div><br></div></div>

--001a11c20e7a2ad04604fb197540--


From nobody Thu Jun  5 09:45:18 2014
Return-Path: <tnadeau@lucidvision.com>
X-Original-To: mib-doctors@ietfa.amsl.com
Delivered-To: mib-doctors@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 47F171A0075 for <mib-doctors@ietfa.amsl.com>; Thu,  5 Jun 2014 09:45:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.553
X-Spam-Level: 
X-Spam-Status: No, score=-2.553 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h1sbQ4FgGmau for <mib-doctors@ietfa.amsl.com>; Thu,  5 Jun 2014 09:45:15 -0700 (PDT)
Received: from lucidvision.com (lucidvision.com [72.71.250.34]) by ietfa.amsl.com (Postfix) with ESMTP id E6EBA1A008C for <mib-doctors@ietf.org>; Thu,  5 Jun 2014 09:45:14 -0700 (PDT)
Received: from [192.168.1.107] (static-72-71-250-38.cncdnh.fast04.myfairpoint.net [72.71.250.38]) by lucidvision.com (Postfix) with ESMTP id 4861027D22BE; Thu,  5 Jun 2014 12:45:08 -0400 (EDT)
Content-Type: multipart/signed; boundary="Apple-Mail=_7889B422-DED8-4122-83D3-2FFBAA4CF960"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\))
From: "Thomas D. Nadeau" <tnadeau@lucidvision.com>
In-Reply-To: <20140605154918.GC12274@elstar.local>
Date: Thu, 5 Jun 2014 12:45:06 -0400
Message-Id: <FFBD2FEA-8431-41AF-B166-753D58933719@lucidvision.com>
References: <07a601cf800e$ea9710e0$bfc532a0$@olddog.co.uk> <53905C1E.10808@cisco.com> <9904FB1B0159DA42B0B887B7FA8119CA5C7FE398@AZ-FFEXMB04.global.avaya.com> <4308CFC7-7341-4D66-A50C-5B808DB9FCEC@lucidvision.com> <20140605154918.GC12274@elstar.local>
To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
X-Mailer: Apple Mail (2.1878.2)
Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/Ern9WaH85QPDaCAPgYnddPffFT8
Cc: Farrel Adrian <adrian@olddog.co.uk>, "MIB Doctors \(E-mail\)" <mib-doctors@ietf.org>
Subject: Re: [MIB-DOCTORS] Fwd: Request to add to the MIB boilperplate for "writeable objects"
X-BeenThere: mib-doctors@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: MIB Doctors list <mib-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mib-doctors/>
List-Post: <mailto:mib-doctors@ietf.org>
List-Help: <mailto:mib-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Jun 2014 16:45:16 -0000

--Apple-Mail=_7889B422-DED8-4122-83D3-2FFBAA4CF960
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


	Of course, which is why this statement is not very useful. *)

On Jun 5, 2014:11:49 AM, at 11:49 AM, Juergen Schoenwaelder =
<j.schoenwaelder@jacobs-university.de> wrote:

> On Thu, Jun 05, 2014 at 11:30:33AM -0400, Thomas D. Nadeau wrote:
>>=20
>> 	I agree. This is just swimming around the drain. We need to just =
emphatically stop r-w and be done with this issue.=20
>>=20
>=20
> And I disagree with that. There are legitimate reasons for r-w and the
> IESG statement is not generally banning r-w either.
>=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


--Apple-Mail=_7889B422-DED8-4122-83D3-2FFBAA4CF960
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJTkJ6TAAoJEPcO+I7eiUJZmGMQALrjJFus4jhlL+rjDXGNlc8k
LsDpQhG40MiZqx3I2rWff46jqwaHnba1BnnDFhqJE7GhOKTkcAeSu1qQiWRJ7sOL
pb3GMby0Kyd7j4wCWmI54btKPdPRNYWyj0cqIOeTak8kjx1e5309LE57FP9FHtdV
E+VBV3IweJ/J8JTCM9bAlcoiM1bLbdEYiDEj2qhpeCZgsy1Y3roDD3u2OMrPr1su
CDfMpnZzdnAop43LuyEl+odIFM4pxZ2yEn5VwlZPjdinuVdtCFGHGtb91l+V1wSl
0m0joZG2Ehki1+rDb0OcNi2vk6s3gf9O6mg3sXiqigoWPjfD9jX/ajPbc2BwKAaF
eHLGntSzKwWvn5xRD18EIW8tWiaxw4BCITxiIhnPOxK5lc8ex8rSEsetGAOOCaOi
9DEXRjirtLRn+GIiJRYrjBilF11eCs2HIPOe+Y0natJy++jDTb8Z0skWVMuFGJ5c
VjLlNpl4CGGsDPhuGTj+n7XWxdD2eb8fclxLe/9bFJo6ZWP8xodfQRPetsiD8djc
e5GO5vR3rWK9qpvkfI16Tbi+/5yHuhLXcvo6e8Uvq0UWyhWN6png0Z5RHRHbFzvh
yLP59Un28BzDQUS2XuiNJNmyHZIqWF+hTOjoEeSYlVknyV7+mRwNgJAOCFtfdK1Q
U97f4xJQp8rb6DB37zcp
=ZjQS
-----END PGP SIGNATURE-----

--Apple-Mail=_7889B422-DED8-4122-83D3-2FFBAA4CF960--


From nobody Thu Jun  5 09:55:40 2014
Return-Path: <j.schoenwaelder@jacobs-university.de>
X-Original-To: mib-doctors@ietfa.amsl.com
Delivered-To: mib-doctors@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 410E31A0221 for <mib-doctors@ietfa.amsl.com>; Thu,  5 Jun 2014 09:55:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.201
X-Spam-Level: 
X-Spam-Status: No, score=-2.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RP_MATCHES_RCVD=-0.651] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VtWYeWmd8NxK for <mib-doctors@ietfa.amsl.com>; Thu,  5 Jun 2014 09:55:37 -0700 (PDT)
Received: from atlas3.jacobs-university.de (atlas3.jacobs-university.de [212.201.44.18]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9567E1A017F for <mib-doctors@ietf.org>; Thu,  5 Jun 2014 09:55:36 -0700 (PDT)
Received: from localhost (demetrius5.irc-it.jacobs-university.de [10.70.0.222]) by atlas3.jacobs-university.de (Postfix) with ESMTP id BBDE9E77; Thu,  5 Jun 2014 18:55:28 +0200 (CEST)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from atlas3.jacobs-university.de ([10.70.0.220]) by localhost (demetrius5.jacobs-university.de [10.70.0.222]) (amavisd-new, port 10030) with ESMTP id GLGhhZDlW14N; Thu,  5 Jun 2014 18:55:11 +0200 (CEST)
Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hermes.jacobs-university.de", Issuer "Jacobs University CA - G01" (verified OK)) by atlas3.jacobs-university.de (Postfix) with ESMTPS; Thu,  5 Jun 2014 18:55:28 +0200 (CEST)
Received: from localhost (demetrius4.jacobs-university.de [212.201.44.49]) by hermes.jacobs-university.de (Postfix) with ESMTP id BA1692002F; Thu,  5 Jun 2014 18:55:28 +0200 (CEST)
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 7iPLXgz81Q-S; Thu,  5 Jun 2014 18:55:28 +0200 (CEST)
Received: from elstar.local (elstar.jacobs.jacobs-university.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id C389F2002C; Thu,  5 Jun 2014 18:55:27 +0200 (CEST)
Received: by elstar.local (Postfix, from userid 501) id B10D22D529CC; Thu,  5 Jun 2014 18:55:27 +0200 (CEST)
Date: Thu, 5 Jun 2014 18:55:27 +0200
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: Andy Bierman <andy@yumaworks.com>
Message-ID: <20140605165527.GE12274@elstar.local>
Mail-Followup-To: Andy Bierman <andy@yumaworks.com>, Michael MacFaden <mrm@macfaden.com>, Benoit Claise <bclaise@cisco.com>, "MIB Doctors (E-mail)" <mib-doctors@ietf.org>, Adrian Farrel <adrian@olddog.co.uk>
References: <07a601cf800e$ea9710e0$bfc532a0$@olddog.co.uk> <53905C1E.10808@cisco.com> <20140605123554.GA11717@elstar.local> <CAD3a8Tn4L8Fi4Y2rO9ohEhDW9UgW1iJVLzGjcVOA=i+ALaTraQ@mail.gmail.com> <CABCOCHRn80jmFbMO2jB9TVTDirZ2Xc0uxPxQzHtcWZmksQJ1bA@mail.gmail.com> <20140605163432.GD12274@elstar.local> <CABCOCHQc-tKzxrD0diukS-7uK3X3dh1yRVR0H9JB4EZeEgCoiQ@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CABCOCHQc-tKzxrD0diukS-7uK3X3dh1yRVR0H9JB4EZeEgCoiQ@mail.gmail.com>
User-Agent: Mutt/1.4.2.3i
Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/FHpmuH6nE4ILa-W3xSlPKRD82lw
Cc: Michael MacFaden <mrm@macfaden.com>, Adrian Farrel <adrian@olddog.co.uk>, "MIB Doctors \(E-mail\)" <mib-doctors@ietf.org>
Subject: Re: [MIB-DOCTORS] Fwd: Request to add to the MIB boilperplate for "writeable objects"
X-BeenThere: mib-doctors@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
List-Id: MIB Doctors list <mib-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mib-doctors/>
List-Post: <mailto:mib-doctors@ietf.org>
List-Help: <mailto:mib-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Jun 2014 16:55:39 -0000

On Thu, Jun 05, 2014 at 09:44:25AM -0700, Andy Bierman wrote:
> 
> The IESG is saying use NETCONF for new stuff and it's OK to
> keep using SNMP read-create and read-only when there is good cause.
> But there is no transition strategy to move from row-based SNMP to
> datastore-based NETCONF, for writable objects.
> 
> The fact that a large vendor is attempting to implement the
> translation for writable objects suggests a migration strategy is needed.
> 

For the configuration of an SNMP agent, the NETMOD WG has written a
data model.  Perhaps someone needs to sit down and look at how many
other IETF SNMP configuration MIB modules are widely implemented and
need a similar action. I assume this is a rather small set - but I may
be wrong. I assume the problem would be much harder for say the IEEE.

For vendors with vendor specific MIB modules, the situation is likely
a bit different (hopefully simpler) because a vendor presumable
understands how their writable SNMP agents deal with persistency. The
problem is harder for IETF MIB modules since implementations can use
very different persistency models (and this is what SNMP allows).

/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 nobody Thu Jun  5 10:08:32 2014
Return-Path: <adrian@olddog.co.uk>
X-Original-To: mib-doctors@ietfa.amsl.com
Delivered-To: mib-doctors@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8AEFD1A01A0 for <mib-doctors@ietfa.amsl.com>; Thu,  5 Jun 2014 10:08:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.899
X-Spam-Level: 
X-Spam-Status: No, score=-101.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id n4QLowhGnlyt for <mib-doctors@ietfa.amsl.com>; Thu,  5 Jun 2014 10:08:25 -0700 (PDT)
Received: from asmtp4.iomartmail.com (asmtp4.iomartmail.com [62.128.201.175]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6EDEE1A017F for <mib-doctors@ietf.org>; Thu,  5 Jun 2014 10:08:24 -0700 (PDT)
Received: from asmtp4.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id s55H8ABQ002875; Thu, 5 Jun 2014 18:08:10 +0100
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id s55H87wt002851 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 5 Jun 2014 18:08:08 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Romascanu, Dan \(Dan\)'" <dromasca@avaya.com>, "'Benoit Claise'" <bclaise@cisco.com>, "'MIB Doctors \(E-mail\)'" <mib-doctors@ietf.org>
Date: Thu, 5 Jun 2014 18:08:07 +0100
Message-ID: <001e01cf80e0$ba2b1910$2e814b30$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_001F_01CF80E9.1BF32A90"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac+A4LUBpwt79JWrRzOA7cYaPIjJag==
Content-Language: en-gb
X-TM-AS-MML: disable
X-TM-AS-Product-Ver: IMSS-7.1.0.1576-7.5.0.1017-20740.000
X-TM-AS-Result: No--14.896-10.0-31-10
X-imss-scan-details: No--14.896-10.0-31-10
X-TMASE-MatchedRID: yebcs53SkkBOfcbG5wTrAQRH1Nr7oERdQrO4XR6BRQOVz/nzey1gH49/ 6wlLhvp4hOgAHXcP0qhYycGSPNZu04ZwOxtSnuhYDYh1Uz6zv6PRahuPwaQ1WnhumUIYQCqw8IA TrQJNUc2z4hh/ctRdrnTHPtqsuxSw3ht8/bl7n7Jc/msUC5wFQUET2QkXV/XCARUbchnZQj19jN 6Yl/AtzoV+2JQwT1nucqNf0qe6F5V+HQEHIpIakwphJ/svEmvGZodCyXXZLextGYTovTq6ltIgY GWH7CoVb6t1z3KBxES8sJFj2wHh7N9mDBi6Lqhqj2FGM19l45chHWssEmb8zhAfwLHOKGmBfqaj p6GTnSocmZrqM5Ssk9oYR5Q1QShUKgsbwct+M1/5wpfrIJDXe4fGLZ++QpQz/69r3NqBht4j7h6 18kaIqG4Kqb0ahB2JB1IQ+wlP9+LXvsE3MPuDQrxygpRxo469gowzX/eKjhLagsZM0qVv1wnVBm 12Yily2jdg6l1FQRZJpV9rHFX3j+2u5u3xOQvhwbRQ2Bpmliq0X0Yw27VuouQ45nVtPqmxrsFU8 Uw5BC6ytmB2/5InT/zxIC9LasqudG57tpB6osSzLD5kmcW6ZCBW9lXcEHZA0ToSvkRVqOZbYToD RWMGWpDQiv0Qe0IxAkhxxowNxQIX8k3r0LX5EJHXKSSl+ScK/AZW18vjv1pyri/EgufZd2AqMCk r6SPvrZlfDIf02Jvz6c8TOd9Ak4RYbh/Eo+XF462sl6NKNzCH7D1bP/FcOhHyswgJ7SqQBpNqUz wLvvcpwCEGTgSxOxoVXDux0y5/NJyAyqAmcb+eAiCmPx4NwGmRqNBHmBvevqq8s2MNhPB9j2Gwz TE3vbyah9aCYUCHZlSP4uXXI7m/cZ9zjKjpi/U/CdNiAxg2MtcEccsntYxwgtnm/67jn8T7Rloj VUJS/SpAGqyOCYV5FUX6u9cLEcVosJO95GTb
Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/rZhQNiT9BEvSZl8mna-4_1pjdOA
Subject: Re: [MIB-DOCTORS] Fwd: Request to add to the MIB boilperplate for "writeable objects"
X-BeenThere: mib-doctors@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: MIB Doctors list <mib-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mib-doctors/>
List-Post: <mailto:mib-doctors@ietf.org>
List-Help: <mailto:mib-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Jun 2014 17:08:28 -0000

This is a multipart message in MIME format.

------=_NextPart_000_001F_01CF80E9.1BF32A90
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hi,
 
For some reason I'm only seeing half of these emails.
 
1. I was not proposing it for the Security Considerations section.
I think it is up to you to work out the right place in the documents to put the
text.
It does not follow that the two issues need to be in contiguous text in the same
section.
 
2. The second point (what happens with SET of an unsupported value) could be
argued to be entirely obvious and well-documented. If that is so, I am happy to
not include such text, but I would like to not see discussion of exactly this
point in MIB Doctor reviews and AD Comments in the future that cause the authors
to have to add exactly this text to their document!
 
A
 
 
From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com] 
Sent: 05 June 2014 13:21
To: Benoit Claise; MIB Doctors (E-mail)
Cc: Adrian Farrel
Subject: RE: [MIB-DOCTORS] Fwd: Request to add to the MIB boilperplate for
"writeable objects"
 
See in-line. 
 
Regards,
 
Dan
 
 
From: MIB-DOCTORS [mailto:mib-doctors-bounces@ietf.org] On Behalf Of Benoit
Claise
Sent: Thursday, June 05, 2014 3:02 PM
To: MIB Doctors (E-mail)
Cc: Adrian Farrel
Subject: [MIB-DOCTORS] Fwd: Request to add to the MIB boilperplate for
"writeable objects"
 
Dear MIB-doctors,

Here is a proposal from Adrian on updating the MIB boilerplate.
This looks good to me. Any feedback?

Regards, Benoit


-------- Original Message -------- 

Subject: 
Request to add to the MIB boilperplate for "writeable objects"

Date: 
Wed, 4 Jun 2014 17:06:16 +0100

From: 
Adrian Farrel  <mailto:adrian@olddog.co.uk> <adrian@olddog.co.uk>

Reply-To: 
 <mailto:adrian@olddog.co.uk> <adrian@olddog.co.uk>

To: 
 <mailto:bclaise@cisco.com> <bclaise@cisco.com>
 
Hi Benoit,
 
After the work on the BFD MIB modules and considering the IESG statement on
writeability, would you consider adding to the MIB boilerplate an optional piece
of text that says...
 
n    
n  Where is this text planned to be added? - Security considerations? 
 
====
The following objects in the MIB modules in this document have write access
either through read-write or read-create MAX-ACCESS clauses. The level of access
to these objects have been discussed by the <xxxx> working group and it was
concluded that write access was beneficial for the following reasons:
 
- <list of reasons>
 
- <list of objects>
 
As with all MIB modules, an attempt to SET or CREATE an object to a value that
is not supported by the implementation will result in a failure using a return
code that indicates that the value is not supported.
 
n    I am not sure that we need this paragraph. A compliant implementation will
do what is supposed to do. Moreover, this is not about 'value not supported' but
about trying to write objects that are not writeable - the error codes are
different. 
 
====
 
I think this would help to contain and control work on MIB documents in the
future, and would give the Doctors something to review against.
 
Please wordsmith to your heart's content.
 
Ciao,
Adrian
 
.
 
 
 

------=_NextPart_000_001F_01CF80E9.1BF32A90
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DProgId content=3DWord.Document><meta =
name=3DGenerator content=3D"Microsoft Word 14"><meta name=3DOriginator =
content=3D"Microsoft Word 14"><link rel=3DFile-List =
href=3D"cid:filelist.xml@01CF80E9.16C77760"><!--[if gte mso 9]><xml>
<o:OfficeDocumentSettings>
<o:AllowPNG/>
</o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:WordDocument>
<w:SpellingState>Clean</w:SpellingState>
<w:TrackMoves/>
<w:TrackFormatting/>
<w:EnvelopeVis/>
<w:ValidateAgainstSchemas/>
<w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>
<w:IgnoreMixedContent>false</w:IgnoreMixedContent>
<w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>
<w:DoNotPromoteQF/>
<w:LidThemeOther>EN-GB</w:LidThemeOther>
<w:LidThemeAsian>X-NONE</w:LidThemeAsian>
<w:LidThemeComplexScript>X-NONE</w:LidThemeComplexScript>
<w:Compatibility>
<w:DoNotExpandShiftReturn/>
<w:BreakWrappedTables/>
<w:SplitPgBreakAndParaMark/>
<w:EnableOpenTypeKerning/>
</w:Compatibility>
<w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel>
<m:mathPr>
<m:mathFont m:val=3D"Cambria Math"/>
<m:brkBin m:val=3D"before"/>
<m:brkBinSub m:val=3D"&#45;-"/>
<m:smallFrac m:val=3D"off"/>
<m:dispDef/>
<m:lMargin m:val=3D"0"/>
<m:rMargin m:val=3D"0"/>
<m:defJc m:val=3D"centerGroup"/>
<m:wrapIndent m:val=3D"1440"/>
<m:intLim m:val=3D"subSup"/>
<m:naryLim m:val=3D"undOvr"/>
</m:mathPr></w:WordDocument>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:LatentStyles DefLockedState=3D"false" DefUnhideWhenUsed=3D"true" =
DefSemiHidden=3D"true" DefQFormat=3D"false" DefPriority=3D"99" =
LatentStyleCount=3D"267">
<w:LsdException Locked=3D"false" Priority=3D"0" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Normal"/>
<w:LsdException Locked=3D"false" Priority=3D"9" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"heading 1"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 2"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 3"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 4"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 5"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 6"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 7"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 8"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 9"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 1"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 2"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 3"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 4"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 5"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 6"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 7"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 8"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 9"/>
<w:LsdException Locked=3D"false" Priority=3D"35" QFormat=3D"true" =
Name=3D"caption"/>
<w:LsdException Locked=3D"false" Priority=3D"10" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Title"/>
<w:LsdException Locked=3D"false" Priority=3D"1" Name=3D"Default =
Paragraph Font"/>
<w:LsdException Locked=3D"false" Priority=3D"11" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtitle"/>
<w:LsdException Locked=3D"false" Priority=3D"22" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Strong"/>
<w:LsdException Locked=3D"false" Priority=3D"20" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Emphasis"/>
<w:LsdException Locked=3D"false" Priority=3D"59" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Table Grid"/>
<w:LsdException Locked=3D"false" UnhideWhenUsed=3D"false" =
Name=3D"Placeholder Text"/>
<w:LsdException Locked=3D"false" Priority=3D"1" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"No Spacing"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 1"/>
<w:LsdException Locked=3D"false" UnhideWhenUsed=3D"false" =
Name=3D"Revision"/>
<w:LsdException Locked=3D"false" Priority=3D"34" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"List Paragraph"/>
<w:LsdException Locked=3D"false" Priority=3D"29" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Quote"/>
<w:LsdException Locked=3D"false" Priority=3D"30" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Quote"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"19" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtle Emphasis"/>
<w:LsdException Locked=3D"false" Priority=3D"21" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Emphasis"/>
<w:LsdException Locked=3D"false" Priority=3D"31" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtle Reference"/>
<w:LsdException Locked=3D"false" Priority=3D"32" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Reference"/>
<w:LsdException Locked=3D"false" Priority=3D"33" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Book Title"/>
<w:LsdException Locked=3D"false" Priority=3D"37" Name=3D"Bibliography"/>
<w:LsdException Locked=3D"false" Priority=3D"39" QFormat=3D"true" =
Name=3D"TOC Heading"/>
</w:LatentStyles>
</xml><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;
	mso-font-charset:2;
	mso-generic-font-family:auto;
	mso-font-pitch:variable;
	mso-font-signature:0 268435456 0 0 -2147483648 0;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;
	mso-font-charset:2;
	mso-generic-font-family:auto;
	mso-font-pitch:variable;
	mso-font-signature:0 268435456 0 0 -2147483648 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;
	mso-font-charset:0;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:-536870145 1073786111 1 0 415 0;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;
	mso-font-charset:0;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:-520081665 -1073717157 41 0 66047 0;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;
	mso-font-charset:0;
	mso-generic-font-family:modern;
	mso-font-pitch:fixed;
	mso-font-signature:-520092929 1073806591 9 0 415 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-unhide:no;
	mso-style-qformat:yes;
	mso-style-parent:"";
	margin:0cm;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";
	mso-fareast-font-family:Calibri;
	color:black;}
a:link, span.MsoHyperlink
	{mso-style-noshow:yes;
	mso-style-priority:99;
	color:blue;
	text-decoration:underline;
	text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-noshow:yes;
	mso-style-priority:99;
	color:purple;
	text-decoration:underline;
	text-underline:single;}
pre
	{mso-style-noshow:yes;
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0cm;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:10.0pt;
	font-family:"Courier New";
	mso-fareast-font-family:Calibri;
	color:black;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	mso-style-unhide:no;
	mso-style-qformat:yes;
	margin-top:0cm;
	margin-right:0cm;
	margin-bottom:0cm;
	margin-left:36.0pt;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";
	mso-fareast-font-family:Calibri;
	color:black;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-noshow:yes;
	mso-style-priority:99;
	mso-style-unhide:no;
	mso-style-locked:yes;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;
	mso-ascii-font-family:Consolas;
	mso-hansi-font-family:Consolas;
	mso-bidi-font-family:Consolas;
	color:black;}
span.EmailStyle20
	{mso-style-type:personal;
	mso-style-noshow:yes;
	mso-style-unhide:no;
	font-family:"Calibri","sans-serif";
	mso-ascii-font-family:Calibri;
	mso-hansi-font-family:Calibri;
	color:#1F497D;}
span.EmailStyle21
	{mso-style-type:personal-reply;
	mso-style-noshow:yes;
	mso-style-unhide:no;
	mso-ansi-font-size:11.0pt;
	mso-bidi-font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-ascii-font-family:Calibri;
	mso-fareast-font-family:Calibri;
	mso-hansi-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	mso-default-props:yes;
	font-size:10.0pt;
	mso-ansi-font-size:10.0pt;
	mso-bidi-font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;
	mso-header-margin:36.0pt;
	mso-footer-margin:36.0pt;
	mso-paper-source:0;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1314027032;
	mso-list-type:hybrid;
	mso-list-template-ids:1632525898 1153189266 67698691 67698693 67698689 =
67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-start-at:0;
	mso-level-number-format:bullet;
	mso-level-text:\F06E;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:Arial;}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
--></style><!--[if gte mso 10]><style>/* Style Definitions */
table.MsoNormalTable
	{mso-style-name:"Table Normal";
	mso-tstyle-rowband-size:0;
	mso-tstyle-colband-size:0;
	mso-style-noshow:yes;
	mso-style-priority:99;
	mso-style-parent:"";
	mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
	mso-para-margin:0cm;
	mso-para-margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:10.0pt;
	font-family:"Times New Roman","serif";}
</style><![endif]--><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body bgcolor=3Dwhite =
lang=3DEN-GB link=3Dblue vlink=3Dpurple =
style=3D'tab-interval:36.0pt'><div class=3DWordSection1><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'>Hi,<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'>For some reason I'm only =
seeing half of these emails.<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'>1. I was not proposing it for =
the Security Considerations section.<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'>I think it is up to you to =
work out the right place in the documents to put the =
text.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'>It does not follow that the =
two issues need to be in contiguous text in the same =
section.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'>2. The second point (what =
happens with SET of an unsupported value) could be argued to be entirely =
obvious and well-documented. If that is so, I am happy to not include =
such text, but I would like to not see discussion of exactly this point =
in MIB Doctor reviews and AD Comments in the future that cause the =
authors to have to add exactly this text to their =
document!<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'>A<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New =
Roman";color:#1F497D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=3DMsoNormal><b><span =
lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-f=
ont-family:"Times New =
Roman";color:windowtext;mso-ansi-language:EN-US'>From:</span></b><span =
lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-f=
ont-family:"Times New Roman";color:windowtext;mso-ansi-language:EN-US'> =
Romascanu, Dan (Dan) [mailto:dromasca@avaya.com] <br><b>Sent:</b> 05 =
June 2014 13:21<br><b>To:</b> Benoit Claise; MIB Doctors =
(E-mail)<br><b>Cc:</b> Adrian Farrel<br><b>Subject:</b> RE: =
[MIB-DOCTORS] Fwd: Request to add to the MIB boilperplate for =
&quot;writeable objects&quot;<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D;mso-ansi-language:EN-US'>See in-line. <o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D;mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D;mso-ansi-language:EN-US'>Regards,<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D;mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D;mso-ansi-language:EN-US'>Dan<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D;mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D;mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=3DMsoNormal><b><span =
lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowt=
ext;mso-ansi-language:EN-US'>From:</span></b><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowt=
ext;mso-ansi-language:EN-US'> MIB-DOCTORS =
[mailto:mib-doctors-bounces@ietf.org] <b>On Behalf Of </b>Benoit =
Claise<br><b>Sent:</b> Thursday, June 05, 2014 3:02 PM<br><b>To:</b> MIB =
Doctors (E-mail)<br><b>Cc:</b> Adrian Farrel<br><b>Subject:</b> =
[MIB-DOCTORS] Fwd: Request to add to the MIB boilperplate for =
&quot;writeable objects&quot;<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>Dear MIB-doctors,<br><br>Here is a =
proposal from Adrian on updating the MIB boilerplate.<br>This looks good =
to me. Any feedback?<br><br>Regards, Benoit<o:p></o:p></span></p><div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'><br><br>-------- Original Message =
-------- <o:p></o:p></span></p><table class=3DMsoNormalTable border=3D0 =
cellspacing=3D0 cellpadding=3D0 =
style=3D'mso-cellspacing:0cm;mso-yfti-tbllook:1184;mso-padding-alt:0cm =
0cm 0cm 0cm'><tr style=3D'mso-yfti-irow:0;mso-yfti-firstrow:yes'><td =
nowrap valign=3Dtop style=3D'padding:0cm 0cm 0cm 0cm'><p =
class=3DMsoNormal align=3Dright style=3D'text-align:right'><b>Subject: =
<o:p></o:p></b></p></td><td style=3D'padding:0cm 0cm 0cm 0cm'><p =
class=3DMsoNormal>Request to add to the MIB boilperplate for =
&quot;writeable objects&quot;<o:p></o:p></p></td></tr><tr =
style=3D'mso-yfti-irow:1'><td nowrap valign=3Dtop style=3D'padding:0cm =
0cm 0cm 0cm'><p class=3DMsoNormal align=3Dright =
style=3D'text-align:right'><b>Date: <o:p></o:p></b></p></td><td =
style=3D'padding:0cm 0cm 0cm 0cm'><p class=3DMsoNormal>Wed, 4 Jun 2014 =
17:06:16 +0100<o:p></o:p></p></td></tr><tr style=3D'mso-yfti-irow:2'><td =
nowrap valign=3Dtop style=3D'padding:0cm 0cm 0cm 0cm'><p =
class=3DMsoNormal align=3Dright style=3D'text-align:right'><b>From: =
<o:p></o:p></b></p></td><td style=3D'padding:0cm 0cm 0cm 0cm'><p =
class=3DMsoNormal>Adrian Farrel <a =
href=3D"mailto:adrian@olddog.co.uk">&lt;adrian@olddog.co.uk&gt;</a><o:p><=
/o:p></p></td></tr><tr style=3D'mso-yfti-irow:3'><td nowrap valign=3Dtop =
style=3D'padding:0cm 0cm 0cm 0cm'><p class=3DMsoNormal align=3Dright =
style=3D'text-align:right'><b>Reply-To: <o:p></o:p></b></p></td><td =
style=3D'padding:0cm 0cm 0cm 0cm'><p class=3DMsoNormal><a =
href=3D"mailto:adrian@olddog.co.uk">&lt;adrian@olddog.co.uk&gt;</a><o:p><=
/o:p></p></td></tr><tr =
style=3D'mso-yfti-irow:4;mso-yfti-lastrow:yes'><td nowrap valign=3Dtop =
style=3D'padding:0cm 0cm 0cm 0cm'><p class=3DMsoNormal align=3Dright =
style=3D'text-align:right'><b>To: <o:p></o:p></b></p></td><td =
style=3D'padding:0cm 0cm 0cm 0cm'><p class=3DMsoNormal><a =
href=3D"mailto:bclaise@cisco.com">&lt;bclaise@cisco.com&gt;</a><o:p></o:p=
></p></td></tr></table><p class=3DMsoNormal =
style=3D'margin-bottom:12.0pt'><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p><pre><span =
lang=3DEN-US style=3D'mso-ansi-language:EN-US'>Hi =
Benoit,<o:p></o:p></span></pre><pre><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></pre><pre><spa=
n lang=3DEN-US style=3D'mso-ansi-language:EN-US'>After the work on the =
BFD MIB modules and considering the IESG statement =
on<o:p></o:p></span></pre><pre><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>writeability, would you consider =
adding to the MIB boilerplate an optional =
piece<o:p></o:p></span></pre><pre><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>of text that =
says...<o:p></o:p></span></pre><pre><span lang=3DEN-US =
style=3D'color:#1F497D;mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span><=
/pre><p class=3DMsoListParagraph =
style=3D'margin-left:0cm;text-indent:0cm;mso-list:l0 level1 lfo2'><![if =
!supportLists]><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:Wingdings;mso-fareast-font-family:W=
ingdings;mso-bidi-font-family:Wingdings;color:#1F497D;mso-ansi-language:E=
N-US'><span style=3D'mso-list:Ignore'>n<span style=3D'font:7.0pt "Times =
New Roman"'>&nbsp;&nbsp; </span></span></span><![endif]><span =
lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D;mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoListParagraph style=3D'text-indent:-18.0pt;mso-list:l0 level1 =
lfo2'><![if !supportLists]><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:Wingdings;mso-fareast-font-family:W=
ingdings;mso-bidi-font-family:Wingdings;color:#1F497D;mso-ansi-language:E=
N-US'><span style=3D'mso-list:Ignore'>n<span style=3D'font:7.0pt "Times =
New Roman"'>&nbsp; </span></span></span><![endif]><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D;mso-ansi-language:EN-US'>Where is this text planned to be added? - =
Security considerations? <o:p></o:p></span></p><pre><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D;mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></pre><pre><span =
lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>=3D=3D=3D=3D<o:p></o:p></span></pre><pr=
e><span lang=3DEN-US style=3D'mso-ansi-language:EN-US'>The following =
objects in the MIB modules in this document have write =
access<o:p></o:p></span></pre><pre><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>either through read-write or =
read-create MAX-ACCESS clauses. The level of =
access<o:p></o:p></span></pre><pre><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>to these objects have been discussed =
by the &lt;xxxx&gt; working group and it =
was<o:p></o:p></span></pre><pre><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>concluded that write access was =
beneficial for the following reasons:<o:p></o:p></span></pre><pre><span =
lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></pre><pre><spa=
n lang=3DEN-US style=3D'mso-ansi-language:EN-US'>- &lt;list of =
reasons&gt;<o:p></o:p></span></pre><pre><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></pre><pre><spa=
n lang=3DEN-US style=3D'mso-ansi-language:EN-US'>- &lt;list of =
objects&gt;<o:p></o:p></span></pre><pre><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></pre><pre><spa=
n lang=3DEN-US style=3D'mso-ansi-language:EN-US'>As with all MIB =
modules, an attempt to SET or CREATE an object to a value =
that<o:p></o:p></span></pre><pre><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>is not supported by the implementation =
will result in a failure using a =
return<o:p></o:p></span></pre><pre><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>code that indicates that the value is =
not supported.<o:p></o:p></span></pre><pre><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D;mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></pre><pre =
style=3D'margin-left:0cm;text-indent:0cm;mso-list:l0 level1 lfo2'><![if =
!supportLists]><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:Wingdings;mso-fareast-font-family:W=
ingdings;mso-bidi-font-family:Wingdings;color:#1F497D;mso-ansi-language:E=
N-US'><span style=3D'mso-list:Ignore'>n<span style=3D'font:7.0pt "Times =
New Roman"'>&nbsp;&nbsp;&nbsp; </span></span></span><![endif]><span =
lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D;mso-ansi-language:EN-US'>I am not sure that we need this paragraph. A =
compliant implementation will do what is supposed to do. Moreover, this =
is not about &#8216;value not supported&#8217; but about trying to write =
objects that are not writeable &#8211; the error codes are different. =
<o:p></o:p></span></pre><pre><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></pre><pre><spa=
n lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>=3D=3D=3D=3D<o:p></o:p></span></pre><pr=
e><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></pre><pre><spa=
n lang=3DEN-US style=3D'mso-ansi-language:EN-US'>I think this would help =
to contain and control work on MIB documents in =
the<o:p></o:p></span></pre><pre><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>future, and would give the Doctors =
something to review against.<o:p></o:p></span></pre><pre><span =
lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></pre><pre><spa=
n lang=3DEN-US style=3D'mso-ansi-language:EN-US'>Please wordsmith to =
your heart's content.<o:p></o:p></span></pre><pre><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></pre><pre><spa=
n lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>Ciao,<o:p></o:p></span></pre><pre><span=
 lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>Adrian<o:p></o:p></span></pre><pre><spa=
n lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></pre><pre><spa=
n lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>.<o:p></o:p></span></pre><pre><span =
lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></pre><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p></div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p></div></div=
></div></body></html>
------=_NextPart_000_001F_01CF80E9.1BF32A90--



From nobody Thu Jun  5 11:43:32 2014
Return-Path: <j.schoenwaelder@jacobs-university.de>
X-Original-To: mib-doctors@ietfa.amsl.com
Delivered-To: mib-doctors@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C84921A024D for <mib-doctors@ietfa.amsl.com>; Thu,  5 Jun 2014 11:43:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.201
X-Spam-Level: 
X-Spam-Status: No, score=-2.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RP_MATCHES_RCVD=-0.651] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zq-CeYVfdzvg for <mib-doctors@ietfa.amsl.com>; Thu,  5 Jun 2014 11:43:25 -0700 (PDT)
Received: from atlas3.jacobs-university.de (atlas3.jacobs-university.de [212.201.44.18]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F171B1A0126 for <mib-doctors@ietf.org>; Thu,  5 Jun 2014 11:43:24 -0700 (PDT)
Received: from localhost (demetrius5.irc-it.jacobs-university.de [10.70.0.222]) by atlas3.jacobs-university.de (Postfix) with ESMTP id E3519113B; Thu,  5 Jun 2014 20:43:16 +0200 (CEST)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from atlas3.jacobs-university.de ([10.70.0.220]) by localhost (demetrius5.jacobs-university.de [10.70.0.222]) (amavisd-new, port 10030) with ESMTP id gv86DyLssV4L; Thu,  5 Jun 2014 20:42:59 +0200 (CEST)
Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hermes.jacobs-university.de", Issuer "Jacobs University CA - G01" (verified OK)) by atlas3.jacobs-university.de (Postfix) with ESMTPS; Thu,  5 Jun 2014 20:43:16 +0200 (CEST)
Received: from localhost (demetrius3.jacobs-university.de [212.201.44.48]) by hermes.jacobs-university.de (Postfix) with ESMTP id F26F720017; Thu,  5 Jun 2014 20:43:16 +0200 (CEST)
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 rcEeKAXWU_E5; Thu,  5 Jun 2014 20:43:16 +0200 (CEST)
Received: from elstar.local (elstar.jacobs.jacobs-university.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id 7B47E20013; Thu,  5 Jun 2014 20:43:15 +0200 (CEST)
Received: by elstar.local (Postfix, from userid 501) id 7064D2D52B22; Thu,  5 Jun 2014 20:43:14 +0200 (CEST)
Date: Thu, 5 Jun 2014 20:43:14 +0200
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: Adrian Farrel <adrian@olddog.co.uk>
Message-ID: <20140605184314.GA12812@elstar.local>
Mail-Followup-To: Adrian Farrel <adrian@olddog.co.uk>, "'Romascanu, Dan (Dan)'" <dromasca@avaya.com>, 'Benoit Claise' <bclaise@cisco.com>, "'MIB Doctors (E-mail)'" <mib-doctors@ietf.org>
References: <001e01cf80e0$ba2b1910$2e814b30$@olddog.co.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <001e01cf80e0$ba2b1910$2e814b30$@olddog.co.uk>
User-Agent: Mutt/1.4.2.3i
Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/siO8McLjKSpfNyOETEG6fJPggiA
Cc: "'MIB Doctors \(E-mail\)'" <mib-doctors@ietf.org>
Subject: Re: [MIB-DOCTORS] Fwd: Request to add to the MIB boilperplate for "writeable objects"
X-BeenThere: mib-doctors@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
List-Id: MIB Doctors list <mib-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mib-doctors/>
List-Post: <mailto:mib-doctors@ietf.org>
List-Help: <mailto:mib-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Jun 2014 18:43:29 -0000

On Thu, Jun 05, 2014 at 06:08:07PM +0100, Adrian Farrel wrote:
>  
> 2. The second point (what happens with SET of an unsupported value) could be
> argued to be entirely obvious and well-documented. If that is so, I am happy to
> not include such text, but I would like to not see discussion of exactly this
> point in MIB Doctor reviews and AD Comments in the future that cause the authors
> to have to add exactly this text to their document!
>  

Has this ever been a real issue?

We are adding more and more boilerplate over the years and I am not
sure anybody actually reads all this boilerplate. Repeating protocol
details in every data model just in case someone does not recall them
sounds like the wrong direction to me. I am not convinced that is a
general problem that justifies this to be in every MIB modules.

/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 nobody Thu Jun  5 12:48:43 2014
Return-Path: <adrian@olddog.co.uk>
X-Original-To: mib-doctors@ietfa.amsl.com
Delivered-To: mib-doctors@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 669771A036D for <mib-doctors@ietfa.amsl.com>; Thu,  5 Jun 2014 12:48:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level: 
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hFNcVEV3vBAJ for <mib-doctors@ietfa.amsl.com>; Thu,  5 Jun 2014 12:48:40 -0700 (PDT)
Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com [62.128.201.248]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 14FCD1A036B for <mib-doctors@ietf.org>; Thu,  5 Jun 2014 12:48:39 -0700 (PDT)
Received: from asmtp1.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id s55JmQGj025052; Thu, 5 Jun 2014 20:48:26 +0100
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id s55JmNoJ025030 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 5 Jun 2014 20:48:23 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Juergen Schoenwaelder'" <j.schoenwaelder@jacobs-university.de>
References: <001e01cf80e0$ba2b1910$2e814b30$@olddog.co.uk> <20140605184314.GA12812@elstar.local>
In-Reply-To: <20140605184314.GA12812@elstar.local>
Date: Thu, 5 Jun 2014 20:48:23 +0100
Message-ID: <00a101cf80f7$1da42d90$58ec88b0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQL68hD20UduFmH+/aeIbeJvWtMgvAFxnZCFmQB58FA=
Content-Language: en-gb
X-TM-AS-MML: disable
X-TM-AS-Product-Ver: IMSS-7.1.0.1576-7.0.0.1014-20740.002
X-TM-AS-Result: No--33.408-10.0-31-10
X-imss-scan-details: No--33.408-10.0-31-10
X-TMASE-MatchedRID: u6ojmU07PKxOfcbG5wTrAfs3IjAeeG13QrO4XR6BRQMeCS/fsNFROmlF 7OhYLlctTvjoJCGi2BJ/WNJFK0dQeaHNozT622Z4T7RVRbrn8wv0hIfAKsh1L0UNHQAoZf5cRm2 17yB1jE1aoQfx8WUX8vypMTQfBdGszfHBBlfWoAVo2fKvznNZwCXV4xeQKwhX47E6rstCUYtEYw GUoNeOTsTCH4UECy5BTa4Cf0D6Ap3eG3z9uXufsuw8wbnnSw8bKx5ICGp/WtEvfr1BJmC7hvh5g T8kXkoMU9Bu+efCJtAKaViiHGm/rJzYc9iV9HCmq0reih3E9rHj5lyuq8IOQRSX1u8BLtZAV96Q sW8/xRWm2lfQnDwzRBANmH21X4jRiNCj8jDazVJVnniKh7YTC7d2noO4P7rALraGNlLRahhHp3u RC0sBr6PicnTeH09Z4m/6in2CA/j51WNA1rE6t673FVUimLHPFJFr2qlKix81uYde5/QdVy9zyz JUEnZkBxuJ0GWNdVZeI3qPgsFyo4ToZqUCO9J5utvHF25zoU8hHWssEmb8zkI6wWqc4reWR+X4f j4ypMni+HZlNhr5qpwgqYHEEyVdGf0D7RCus+yjHlwF1TekB1b9NZ1QCRzCk85NxiPhRLjRMPpR 62Sh5ZZRpcrChfNhuHzCIjg1qyJYe6RsTDPSfTl/1fD/GopdyJ1gFgOMhOn6APa9i04WGCq2rl3 dzGQ1A/3R8k/14e0=
Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/gaZkkByrFy5c0UuA2zyXfdlP9wY
Cc: "'MIB Doctors \(E-mail\)'" <mib-doctors@ietf.org>
Subject: Re: [MIB-DOCTORS] Fwd: Request to add to the MIB boilperplate for "writeable objects"
X-BeenThere: mib-doctors@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: MIB Doctors list <mib-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mib-doctors/>
List-Post: <mailto:mib-doctors@ietf.org>
List-Help: <mailto:mib-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Jun 2014 19:48:42 -0000

Well Juergen, I'm not under-occupied that I spend time concocting text and
proposing it for boilerplate just to fill a few idle hours!

I quote from Benoit in the thread on draft-ietf-bfd-mib resulting from Bert's
MIB Doctor review and Benoit's IESG Comment...

  Discussing this matter with Bert Wijnen, a proposal would be to add to
  the description clause that only valid versions as supported by the
  implementation can be accepted. Others would return an error.

The discussion went on to ask why this would apply to only one object and not to
all read-write and read-create objects. My view was that it would be wrong to
add such a note to the Description clause of just one such object and would be
better to add a note to the preamble for the whole module. We used wording
similar to what I suggested for boilerplate.

Now, let me make several observations:
- MIB doctor reviews are immensely valuable. The work the MIB Doctors
  do is indispensable and this is not criticism of anyone.
- IESG Comments are just comments for the consideration of the
   responsible AD (me in this case) and are not demands for a change to
   the document.  Such Comments are a really valuable part of the 
   process.
- Most MIB document authors are not sophisticated MIB gurus. On the
   whole they are dabbling in majik that is way beyond their powers. Thus,
   when they receive review comments they will almost always "roll over"
   and seek to make the change.
- Most ADs have very little MIB experience and will not push back against
   suggested changes.

So we have a case here where the majority of voices on this list appear to be
saying "You don't need to add that sort of statement to the boilerplate because
it is obvious and already described in general MIB RFCs." Yet the authors and
responsible AD have been persuaded to add exactly such a statement to this
document.

FWIW I don't think this statement is in any way harmful, so I don't propose to
take it out. But, on the other hand, I wish we had a clearer view of what is
needed and what is not needed. Well, at least I have that view on this issue for
future documents :-)

Thanks to all for your time.

Adrian


> -----Original Message-----
> From: Juergen Schoenwaelder [mailto:j.schoenwaelder@jacobs-university.de]
> Sent: 05 June 2014 19:43
> To: Adrian Farrel
> Cc: 'Romascanu, Dan (Dan)'; 'Benoit Claise'; 'MIB Doctors (E-mail)'
> Subject: Re: [MIB-DOCTORS] Fwd: Request to add to the MIB boilperplate for
> "writeable objects"
> 
> On Thu, Jun 05, 2014 at 06:08:07PM +0100, Adrian Farrel wrote:
> >
> > 2. The second point (what happens with SET of an unsupported value) could be
> > argued to be entirely obvious and well-documented. If that is so, I am happy
to
> > not include such text, but I would like to not see discussion of exactly
this
> > point in MIB Doctor reviews and AD Comments in the future that cause the
> authors
> > to have to add exactly this text to their document!
> >
> 
> Has this ever been a real issue?
> 
> We are adding more and more boilerplate over the years and I am not
> sure anybody actually reads all this boilerplate. Repeating protocol
> details in every data model just in case someone does not recall them
> sounds like the wrong direction to me. I am not convinced that is a
> general problem that justifies this to be in every MIB modules.
> 
> /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 nobody Thu Jun  5 12:51:43 2014
Return-Path: <tnadeau@lucidvision.com>
X-Original-To: mib-doctors@ietfa.amsl.com
Delivered-To: mib-doctors@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E50E1A035B for <mib-doctors@ietfa.amsl.com>; Thu,  5 Jun 2014 12:51:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.553
X-Spam-Level: 
X-Spam-Status: No, score=-2.553 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3-CLgX1tGqWB for <mib-doctors@ietfa.amsl.com>; Thu,  5 Jun 2014 12:51:33 -0700 (PDT)
Received: from lucidvision.com (lucidvision.com [72.71.250.34]) by ietfa.amsl.com (Postfix) with ESMTP id 28C781A02F9 for <mib-doctors@ietf.org>; Thu,  5 Jun 2014 12:51:33 -0700 (PDT)
Received: from [192.168.1.107] (static-72-71-250-38.cncdnh.fast04.myfairpoint.net [72.71.250.38]) by lucidvision.com (Postfix) with ESMTP id 4B70C27D2A51; Thu,  5 Jun 2014 15:51:26 -0400 (EDT)
Content-Type: multipart/signed; boundary="Apple-Mail=_5DB1407A-02D6-4D88-A552-599AC79E25A9"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\))
From: "Thomas D. Nadeau" <tnadeau@lucidvision.com>
In-Reply-To: <00a101cf80f7$1da42d90$58ec88b0$@olddog.co.uk>
Date: Thu, 5 Jun 2014 15:51:25 -0400
Message-Id: <3C0CDAED-8399-4ACE-BAFA-5C24410010B5@lucidvision.com>
References: <001e01cf80e0$ba2b1910$2e814b30$@olddog.co.uk> <20140605184314.GA12812@elstar.local> <00a101cf80f7$1da42d90$58ec88b0$@olddog.co.uk>
To: Farrel Adrian <adrian@olddog.co.uk>
X-Mailer: Apple Mail (2.1878.2)
Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/djfEVe-ariiVxpUb27MaeWR0Jlg
Cc: "MIB Doctors \(E-mail\)" <mib-doctors@ietf.org>
Subject: Re: [MIB-DOCTORS] Fwd: Request to add to the MIB boilperplate for "writeable objects"
X-BeenThere: mib-doctors@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: MIB Doctors list <mib-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mib-doctors/>
List-Post: <mailto:mib-doctors@ietf.org>
List-Help: <mailto:mib-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Jun 2014 19:51:38 -0000

--Apple-Mail=_5DB1407A-02D6-4D88-A552-599AC79E25A9
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


On Jun 5, 2014:3:48 PM, at 3:48 PM, Adrian Farrel <adrian@olddog.co.uk> =
wrote:

> Well Juergen, I'm not under-occupied that I spend time concocting text =
and
> proposing it for boilerplate just to fill a few idle hours!
>=20
> I quote from Benoit in the thread on draft-ietf-bfd-mib resulting from =
Bert's
> MIB Doctor review and Benoit's IESG Comment...
>=20
>  Discussing this matter with Bert Wijnen, a proposal would be to add =
to
>  the description clause that only valid versions as supported by the
>  implementation can be accepted. Others would return an error.
>=20
> The discussion went on to ask why this would apply to only one object =
and not to
> all read-write and read-create objects. My view was that it would be =
wrong to
> add such a note to the Description clause of just one such object and =
would be
> better to add a note to the preamble for the whole module. We used =
wording
> similar to what I suggested for boilerplate.
>=20
> Now, let me make several observations:
> - MIB doctor reviews are immensely valuable. The work the MIB Doctors
>  do is indispensable and this is not criticism of anyone.
> - IESG Comments are just comments for the consideration of the
>   responsible AD (me in this case) and are not demands for a change to
>   the document.  Such Comments are a really valuable part of the=20
>   process.
> - Most MIB document authors are not sophisticated MIB gurus. On the
>   whole they are dabbling in majik that is way beyond their powers. =
Thus,
>   when they receive review comments they will almost always "roll =
over"
>   and seek to make the change.
> - Most ADs have very little MIB experience and will not push back =
against
>   suggested changes.
>=20
> So we have a case here where the majority of voices on this list =
appear to be
> saying "You don't need to add that sort of statement to the =
boilerplate because
> it is obvious and already described in general MIB RFCs." Yet the =
authors and
> responsible AD have been persuaded to add exactly such a statement to =
this
> document.
>=20
> FWIW I don't think this statement is in any way harmful, so I don't =
propose to
> take it out. But, on the other hand, I wish we had a clearer view of =
what is
> needed and what is not needed. Well, at least I have that view on this =
issue for
> future documents :-)

	The statement should be simple in the boiler plate and reflect =
the now official
position of the IESG that read-write objects in past modules are fine, =
but the
world HAS moved away from using SNMP for configuration and we strongly =
recommend that
you use NetConf, existing deployments notwithstanding.

	--Tom


> Thanks to all for your time.
>=20
> Adrian
>=20
>=20
>> -----Original Message-----
>> From: Juergen Schoenwaelder =
[mailto:j.schoenwaelder@jacobs-university.de]
>> Sent: 05 June 2014 19:43
>> To: Adrian Farrel
>> Cc: 'Romascanu, Dan (Dan)'; 'Benoit Claise'; 'MIB Doctors (E-mail)'
>> Subject: Re: [MIB-DOCTORS] Fwd: Request to add to the MIB =
boilperplate for
>> "writeable objects"
>>=20
>> On Thu, Jun 05, 2014 at 06:08:07PM +0100, Adrian Farrel wrote:
>>>=20
>>> 2. The second point (what happens with SET of an unsupported value) =
could be
>>> argued to be entirely obvious and well-documented. If that is so, I =
am happy
> to
>>> not include such text, but I would like to not see discussion of =
exactly
> this
>>> point in MIB Doctor reviews and AD Comments in the future that cause =
the
>> authors
>>> to have to add exactly this text to their document!
>>>=20
>>=20
>> Has this ever been a real issue?
>>=20
>> We are adding more and more boilerplate over the years and I am not
>> sure anybody actually reads all this boilerplate. Repeating protocol
>> details in every data model just in case someone does not recall them
>> sounds like the wrong direction to me. I am not convinced that is a
>> general problem that justifies this to be in every MIB modules.
>>=20
>> /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/>
>=20
> _______________________________________________
> MIB-DOCTORS mailing list
> MIB-DOCTORS@ietf.org
> https://www.ietf.org/mailman/listinfo/mib-doctors
>=20


--Apple-Mail=_5DB1407A-02D6-4D88-A552-599AC79E25A9
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJTkMo9AAoJEPcO+I7eiUJZ8WQP/3u0Vyq0CnyF3I7bIt2Qv8UU
ceIS2kWgob7rmt5ohT8X2BNTmhtTO+nYVtlYAPR9nMBCFg28xi+odNvtGh892XXX
Ke5nCLEVPK2GGTrVo9ZCW4x5RGICukSjsrr7IPQYU5gnjj0tEBOao/TwoHKX62aJ
Mr6oxHaL6FQL1drJnN8/B0uMY40sK32bkZLzrs5tHTkjyJXQe1RzDInVjyfx2zYr
VI1LX8Vb1cQkKfgXTqPpVNdW5pYn5GGKWyz6EE7bj1Da+natXW5uxpofC+tMLVFB
X7gGxQS295xpSbP/6e3TyiszEEElhV1BQc9RlzmvuSxIYkg7UXOhb8RyZfruWR63
3SXC39/FudO0vmkRnvvywwFq3RWnC9hMICK+p9LqTKcLs1tjmI18AuzgF515DakF
hoYYLITxrneUzADG5mtAQnjBNdTTm01PGlA3Gkfmsljf1znsNqZfiVRT+V4IU8JD
VIw8QrzhO4YVAUQZkwOAPCLmoeQEY89L+YilYgbMoKDxmp1ifZ1dIMerN7h78BQT
ghGCZntbKlm3z6LosMdWE1WmBhgI4cJEpxvWfrgVdZSfUbIIke2/bT3t1SraAAOJ
0fMUw28C7tx/sD/V5ZA6JgXDaMOQJTFJSXSs20QK9lK8EjV/FOJGe9auF9NIEkln
THouWVIk5sYT4i96819N
=grTs
-----END PGP SIGNATURE-----

--Apple-Mail=_5DB1407A-02D6-4D88-A552-599AC79E25A9--


From nobody Fri Jun  6 01:48:26 2014
Return-Path: <j.schoenwaelder@jacobs-university.de>
X-Original-To: mib-doctors@ietfa.amsl.com
Delivered-To: mib-doctors@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C47511A0409 for <mib-doctors@ietfa.amsl.com>; Fri,  6 Jun 2014 01:48:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.201
X-Spam-Level: 
X-Spam-Status: No, score=-2.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RP_MATCHES_RCVD=-0.651] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kA7arMesghW5 for <mib-doctors@ietfa.amsl.com>; Fri,  6 Jun 2014 01:48:23 -0700 (PDT)
Received: from atlas3.jacobs-university.de (atlas3.jacobs-university.de [212.201.44.18]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6CB231A00EF for <mib-doctors@ietf.org>; Fri,  6 Jun 2014 01:48:23 -0700 (PDT)
Received: from localhost (demetrius5.irc-it.jacobs-university.de [10.70.0.222]) by atlas3.jacobs-university.de (Postfix) with ESMTP id EF6AAAC2; Fri,  6 Jun 2014 10:48:14 +0200 (CEST)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from atlas3.jacobs-university.de ([10.70.0.220]) by localhost (demetrius5.jacobs-university.de [10.70.0.222]) (amavisd-new, port 10030) with ESMTP id 05fuf8l5_AJ6; Fri,  6 Jun 2014 10:47:54 +0200 (CEST)
Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hermes.jacobs-university.de", Issuer "Jacobs University CA - G01" (verified OK)) by atlas3.jacobs-university.de (Postfix) with ESMTPS; Fri,  6 Jun 2014 10:48:14 +0200 (CEST)
Received: from localhost (demetrius4.jacobs-university.de [212.201.44.49]) by hermes.jacobs-university.de (Postfix) with ESMTP id 9CDE520017; Fri,  6 Jun 2014 10:48:14 +0200 (CEST)
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 fkdRpI44o3_1; Fri,  6 Jun 2014 10:48:13 +0200 (CEST)
Received: from elstar.local (elstar.jacobs.jacobs-university.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id 4471420013; Fri,  6 Jun 2014 10:48:13 +0200 (CEST)
Received: by elstar.local (Postfix, from userid 501) id 0F0002D532AF; Fri,  6 Jun 2014 10:48:13 +0200 (CEST)
Date: Fri, 6 Jun 2014 10:48:12 +0200
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: Adrian Farrel <adrian@olddog.co.uk>
Message-ID: <20140606084812.GB14380@elstar.local>
Mail-Followup-To: Adrian Farrel <adrian@olddog.co.uk>, "'Romascanu, Dan (Dan)'" <dromasca@avaya.com>, 'Benoit Claise' <bclaise@cisco.com>, "'MIB Doctors (E-mail)'" <mib-doctors@ietf.org>
References: <001e01cf80e0$ba2b1910$2e814b30$@olddog.co.uk> <20140605184314.GA12812@elstar.local> <00a101cf80f7$1da42d90$58ec88b0$@olddog.co.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <00a101cf80f7$1da42d90$58ec88b0$@olddog.co.uk>
User-Agent: Mutt/1.4.2.3i
Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/z_4t-b4faozn0YexkYBfxr8OuDA
Cc: "'MIB Doctors \(E-mail\)'" <mib-doctors@ietf.org>
Subject: Re: [MIB-DOCTORS] Fwd: Request to add to the MIB boilperplate for "writeable objects"
X-BeenThere: mib-doctors@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
List-Id: MIB Doctors list <mib-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mib-doctors/>
List-Post: <mailto:mib-doctors@ietf.org>
List-Help: <mailto:mib-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Jun 2014 08:48:25 -0000

Adrian,

I am not convinced that (i) more boilerplate text improves things and
(ii) I am concerned that these boilerplate texts get soon out of
control once we start turning issues coming up during MIB doctor
reviews into more and more boilerplate texts and fill out templates.

If the issue is inconsistency of reviews provided by MIB doctors, then
we probably need to add more details that go beyond RFC 4181 on the
MIB doctors wiki, trying to make MIB doctor reviews more consistent
(but they will never really be since differnet people tend to look at
different things more carefully).

/js

On Thu, Jun 05, 2014 at 08:48:23PM +0100, Adrian Farrel wrote:
> Well Juergen, I'm not under-occupied that I spend time concocting text and
> proposing it for boilerplate just to fill a few idle hours!
> 
> I quote from Benoit in the thread on draft-ietf-bfd-mib resulting from Bert's
> MIB Doctor review and Benoit's IESG Comment...
> 
>   Discussing this matter with Bert Wijnen, a proposal would be to add to
>   the description clause that only valid versions as supported by the
>   implementation can be accepted. Others would return an error.
> 
> The discussion went on to ask why this would apply to only one object and not to
> all read-write and read-create objects. My view was that it would be wrong to
> add such a note to the Description clause of just one such object and would be
> better to add a note to the preamble for the whole module. We used wording
> similar to what I suggested for boilerplate.
> 
> Now, let me make several observations:
> - MIB doctor reviews are immensely valuable. The work the MIB Doctors
>   do is indispensable and this is not criticism of anyone.
> - IESG Comments are just comments for the consideration of the
>    responsible AD (me in this case) and are not demands for a change to
>    the document.  Such Comments are a really valuable part of the 
>    process.
> - Most MIB document authors are not sophisticated MIB gurus. On the
>    whole they are dabbling in majik that is way beyond their powers. Thus,
>    when they receive review comments they will almost always "roll over"
>    and seek to make the change.
> - Most ADs have very little MIB experience and will not push back against
>    suggested changes.
> 
> So we have a case here where the majority of voices on this list appear to be
> saying "You don't need to add that sort of statement to the boilerplate because
> it is obvious and already described in general MIB RFCs." Yet the authors and
> responsible AD have been persuaded to add exactly such a statement to this
> document.
> 
> FWIW I don't think this statement is in any way harmful, so I don't propose to
> take it out. But, on the other hand, I wish we had a clearer view of what is
> needed and what is not needed. Well, at least I have that view on this issue for
> future documents :-)
> 
> Thanks to all for your time.
> 
> Adrian
> 
> 
> > -----Original Message-----
> > From: Juergen Schoenwaelder [mailto:j.schoenwaelder@jacobs-university.de]
> > Sent: 05 June 2014 19:43
> > To: Adrian Farrel
> > Cc: 'Romascanu, Dan (Dan)'; 'Benoit Claise'; 'MIB Doctors (E-mail)'
> > Subject: Re: [MIB-DOCTORS] Fwd: Request to add to the MIB boilperplate for
> > "writeable objects"
> > 
> > On Thu, Jun 05, 2014 at 06:08:07PM +0100, Adrian Farrel wrote:
> > >
> > > 2. The second point (what happens with SET of an unsupported value) could be
> > > argued to be entirely obvious and well-documented. If that is so, I am happy
> to
> > > not include such text, but I would like to not see discussion of exactly
> this
> > > point in MIB Doctor reviews and AD Comments in the future that cause the
> > authors
> > > to have to add exactly this text to their document!
> > >
> > 
> > Has this ever been a real issue?
> > 
> > We are adding more and more boilerplate over the years and I am not
> > sure anybody actually reads all this boilerplate. Repeating protocol
> > details in every data model just in case someone does not recall them
> > sounds like the wrong direction to me. I am not convinced that is a
> > general problem that justifies this to be in every MIB modules.
> > 
> > /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/>
> 

-- 
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 nobody Fri Jun  6 06:01:49 2014
Return-Path: <nobo@cisco.com>
X-Original-To: mib-doctors@ietfa.amsl.com
Delivered-To: mib-doctors@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CD02B1A007F for <mib-doctors@ietfa.amsl.com>; Fri,  6 Jun 2014 06:01:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -115.152
X-Spam-Level: 
X-Spam-Status: No, score=-115.152 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1C9XuDAzzgkT for <mib-doctors@ietfa.amsl.com>; Fri,  6 Jun 2014 06:01:38 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C52871A0079 for <mib-doctors@ietf.org>; Fri,  6 Jun 2014 06:01:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4274; q=dns/txt; s=iport; t=1402059692; x=1403269292; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=yX8+IdaiosFssXwWZNuBhNnlD/LAgsSe/W7xNMN2BXU=; b=nLGkp7DXms+C06t8+Ycmk5nkpQcaBUvOHGEvZKCwzQ9VR0j1MWhTrblb zx1sfab1MUEBdcMszc/ogqJ/QwKdNESa8woZo/te7F6HQABsWYN6MhLA8 QmI5/2gvEei6OsmFyRbMM+H4Oq/RY8zTqehDS+zpX4OHoym4l7m5hWQDZ E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AlQGAK26kVOtJA2G/2dsb2JhbABZgmkkgSuIM7QYhCODEQGBBhZ1hAMBAQEDATo/EAIBCCIUEDIlAgQBDQ2IMggBzSEXjXw8MQeDK4EWAQOtVoM8gi8
X-IronPort-AV: E=Sophos;i="4.98,989,1392163200"; d="scan'208";a="330901273"
Received: from alln-core-12.cisco.com ([173.36.13.134]) by rcdn-iport-1.cisco.com with ESMTP; 06 Jun 2014 13:01:31 +0000
Received: from xhc-rcd-x02.cisco.com (xhc-rcd-x02.cisco.com [173.37.183.76]) by alln-core-12.cisco.com (8.14.5/8.14.5) with ESMTP id s56D1Vrw008348 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 6 Jun 2014 13:01:31 GMT
Received: from xmb-aln-x01.cisco.com ([fe80::747b:83e1:9755:d453]) by xhc-rcd-x02.cisco.com ([173.37.183.76]) with mapi id 14.03.0123.003; Fri, 6 Jun 2014 08:01:31 -0500
From: "Nobo Akiya (nobo)" <nobo@cisco.com>
To: "Benoit Claise (bclaise)" <bclaise@cisco.com>, Jeffrey Haas <jhaas@pfrc.org>, "Bert Wijnen (IETF)" <bertietf@bwijnen.net>
Thread-Topic: [MIB-DOCTORS] MIB doctor review for draft-ietf-bfd-tc-mib-07.txt
Thread-Index: AQHParjLwVtxC//AK0+ZwUj+MRVcEJs2+T+AgB9wUoCADcvqgA==
Date: Fri, 6 Jun 2014 13:01:30 +0000
Message-ID: <CECE764681BE964CBE1DFF78F3CDD3941E1D9683@xmb-aln-x01.cisco.com>
References: <536B77F8.8050407@bwijnen.net> <20140508130007.GP17758@pfrc> <5385DF43.1050408@cisco.com>
In-Reply-To: <5385DF43.1050408@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [161.44.212.71]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/i2HqNAFcpaVM5sjG8wW80w7BqE0
Cc: "mib-doctors >> MIB Doctors" <mib-doctors@ietf.org>, "draft-ietf-bfd-tc-mib.all@tools.ietf.org" <draft-ietf-bfd-tc-mib.all@tools.ietf.org>, "adrian@olddog.co.uk" <adrian@olddog.co.uk>
Subject: Re: [MIB-DOCTORS] MIB doctor review for draft-ietf-bfd-tc-mib-07.txt
X-BeenThere: mib-doctors@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: MIB Doctors list <mib-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mib-doctors/>
List-Post: <mailto:mib-doctors@ietf.org>
List-Help: <mailto:mib-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Jun 2014 13:01:45 -0000

Hi Benoit,

Please see in-line.

> >> 3.Same for:
> >>      BfdIntervalTC ::=3D TEXTUAL-CONVENTION
> >>      DISPLAY-HINT  "d"
> >>      STATUS        current
> >>      DESCRIPTION
> >>          "The BFD interval in microseconds."
> >>      SYNTAX Unsigned32 (0..4294967295)
> >>
> >>
> >>    If you see it used in, for example
> >>
> >>      bfdSessDesiredMinTxInterval OBJECT-TYPE
> >>          SYNTAX     BfdIntervalTC
> >>          MAX-ACCESS read-create
> >>          STATUS     current
> >>          DESCRIPTION
> >>              "This object specifies the minimum interval, in
> >>               microseconds, that the local system would like to use
> >>               when transmitting BFD Control packets. The value of
> >>               zero(0) is reserved in this case, and should not be
> >>               used."
> >>          REFERENCE
> >>              "Section 4.1 from Katz, D. and D. Ward, Bidirectional
> >>               Forwarding Detection (BFD), RFC 5880, June 2012."
> >>          ::=3D { bfdSessEntry 25 }
> >>
> >>     Then what value is added by using a TC. In fact you can even queti=
on if
> it
> >>     is not conflicting, because according to the TC description clause=
 I
> would
> >>     expect zero to be a valid interval value, where as here it describ=
es
> >>     that zero is a special value and should not be used. So it is only=
 special
> >>     Since it should NOT BE used, or does zero mean something special?
> >>     Assuming zero SHOULD NOT be used. I personally would just do:
> >>
> >>      bfdSessDesiredMinTxInterval OBJECT-TYPE
> >>          SYNTAX Unsigned32 (1..4294967295)
> >>          MAX-ACCESS read-create
> >>          STATUS     current
> >>          UNITS      microseconds
> >>          DESCRIPTION
> >>              "This object specifies the minimum interval that the loca=
l
> >>               system would like to use when transmitting BFD Control p=
ackets.
> >>          REFERENCE
> >>              "Section 4.1 from Katz, D. and D. Ward, Bidirectional
> >>               Forwarding Detection (BFD), RFC 5880, June 2012."
> >>          ::=3D { bfdSessEntry 25 }
> >>
> >>    In case zero has special meaning I would do:
> >>      bfdSessDesiredMinTxInterval OBJECT-TYPE
> >>          SYNTAX Unsigned32 (0 | 1..4294967295)
> >>          MAX-ACCESS read-create
> >>          STATUS     current
> >>          UNITS      microseconds
> >>          DESCRIPTION
> >>              "This object specifies the minimum interval that the loca=
l
> >>               system would like to use when transmitting BFD Control p=
ackets.
> >>               The value zero has been reserved for a special maning:
> >>               <describe what zero means>
> >>          REFERENCE
> >>              "Section 4.1 from Katz, D. and D. Ward, Bidirectional
> >>               Forwarding Detection (BFD), RFC 5880, June 2012."
> >>          ::=3D { bfdSessEntry 25 }
> > The primary benefit of having it in the object is that we get to
> > specify units.  (I never understood why that was missing from TC.)
> > Beyond that, it's just a refactoring of constraints in case they're fur=
ther
> refined.
> Fine with the units explanation. However, you don't answer the discrepanc=
y
> of the value 0.
> I'll file this in my AD review.
>=20
> Regards, Benoit

Regarding BfdIntervalTC, I'd like to make one additional response. This is =
a TC that is used by several objects in the base BFD MIB.

Zero(0) is valid in following objects:

        bfdSessReqMinRxInterval         BfdIntervalTC,
        bfdSessReqMinEchoRxInterval     BfdIntervalTC,
        bfdSessNegotiatedInterval       BfdIntervalTC,
        bfdSessNegotiatedEchoInterval   BfdIntervalTC,

Zero(0) is not valid in following object:

        bfdSessDesiredMinTxInterval     BfdIntervalTC,

All above objects describe "BFD interval". And rather than creating a separ=
ate TC or specifying different syntax just in bfdSessDesiredMinTxInterval, =
we decided to place more weight on the consistency/simplicity (and describe=
 the zero(0) in the description of bfdSessDesiredMinTxInterval). Thus the w=
ay it is, and I believe this is reasonable.

Thanks!

-Nobo


From nobody Fri Jun  6 19:12:39 2014
Return-Path: <randy_presuhn@mindspring.com>
X-Original-To: mib-doctors@ietfa.amsl.com
Delivered-To: mib-doctors@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 23CE91A02E8 for <mib-doctors@ietfa.amsl.com>; Fri,  6 Jun 2014 19:12:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GTTzgnCUcYBZ for <mib-doctors@ietfa.amsl.com>; Fri,  6 Jun 2014 19:12:35 -0700 (PDT)
Received: from elasmtp-banded.atl.sa.earthlink.net (elasmtp-banded.atl.sa.earthlink.net [209.86.89.70]) by ietfa.amsl.com (Postfix) with ESMTP id 772481A02E6 for <mib-doctors@ietf.org>; Fri,  6 Jun 2014 19:12:34 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=lmig0UNR7wRdfZQ5kIfzcOuKmgVytGzOwzKc8VOmFpsi+h4bpLqp93NELp9K4W/J; h=Message-ID:Date:From:Reply-To:To:Subject:Cc:Mime-Version:Content-Type:Content-Transfer-Encoding:X-Mailer:X-ELNK-Trace:X-Originating-IP;
Received: from [209.86.224.52] (helo=mswamui-valley.atl.sa.earthlink.net) by elasmtp-banded.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <randy_presuhn@mindspring.com>) id 1Wt67P-0001XW-4H; Fri, 06 Jun 2014 22:12:27 -0400
Received: from 76.254.50.81 by webmail.earthlink.net with HTTP; Fri, 6 Jun 2014 22:12:26 -0400
Message-ID: <22410435.1402107147107.JavaMail.root@mswamui-valley.atl.sa.earthlink.net>
Date: Fri, 6 Jun 2014 19:12:26 -0700 (GMT-07:00)
From: Randy Presuhn <randy_presuhn@mindspring.com>
To: Benoit Claise <bclaise@cisco.com>,  "MIB Doctors (E-mail)" <mib-doctors@ietf.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-Mailer: EarthLink Zoo Mail 1.0
X-ELNK-Trace: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d88864c4c3a38ce6fd810ce9eb2fdf25236d2c38bad8c9c6b633350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 209.86.224.52
Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/KRwbvIfP1aViacNJL6dqkScS3IM
Cc: Adrian Farrel <adrian@olddog.co.uk>
Subject: Re: [MIB-DOCTORS] Fwd: Request to add to the MIB boilperplate for "writeable objects"
X-BeenThere: mib-doctors@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Randy Presuhn <randy_presuhn@mindspring.com>
List-Id: MIB Doctors list <mib-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mib-doctors/>
List-Post: <mailto:mib-doctors@ietf.org>
List-Help: <mailto:mib-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 07 Jun 2014 02:12:37 -0000

Hi -

>From: Benoit Claise <bclaise@cisco.com>
>Sent: Jun 5, 2014 5:01 AM
>To: "MIB Doctors (E-mail)" <mib-doctors@ietf.org>
>Cc: Adrian Farrel <adrian@olddog.co.uk>
>Subject: [MIB-DOCTORS] Fwd: Request to add to the MIB boilperplate for	"writeable objects"
>
>Dear MIB-doctors,
>
>Here is a proposal from Adrian on updating the MIB boilerplate.
>This looks good to me. Any feedback?

The proposal contains two parts.  The first provides a historical
record of the working group's thinking, but is of no help in
implementation or deployment.  The second is purely tutorial.
>From my perspective, each would increase the length of a
specification without increasing its utility.  Consequently,
I believe this change would be counterproductive and should
*not* be adopted.

Randy

>Regards, Benoit
>
>
>-------- Original Message --------
>Subject: 	Request to add to the MIB boilperplate for "writeable objects"
>Date: 	Wed, 4 Jun 2014 17:06:16 +0100
>From: 	Adrian Farrel <adrian@olddog.co.uk>
>Reply-To: 	<adrian@olddog.co.uk>
>To: 	<bclaise@cisco.com>
>
>
>
>Hi Benoit,
>
>After the work on the BFD MIB modules and considering the IESG statement on
>writeability, would you consider adding to the MIB boilerplate an optional piece
>of text that says...
>
>====
>The following objects in the MIB modules in this document have write access
>either through read-write or read-create MAX-ACCESS clauses. The level of access
>to these objects have been discussed by the <xxxx> working group and it was
>concluded that write access was beneficial for the following reasons:
>
>- <list of reasons>
>
>- <list of objects>
>
>As with all MIB modules, an attempt to SET or CREATE an object to a value that
>is not supported by the implementation will result in a failure using a return
>code that indicates that the value is not supported.
>
>====
>
>I think this would help to contain and control work on MIB documents in the
>future, and would give the Doctors something to review against.
>
>Please wordsmith to your heart's content.
>
>Ciao,
>Adrian
>
>.
>
>
>


From nobody Mon Jun 16 13:01:25 2014
Return-Path: <ietfdbh@comcast.net>
X-Original-To: mib-doctors@ietfa.amsl.com
Delivered-To: mib-doctors@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1DD451A01C4 for <mib-doctors@ietfa.amsl.com>; Mon, 16 Jun 2014 13:01:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.651
X-Spam-Level: 
X-Spam-Status: No, score=-2.651 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=unavailable
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RZFGTKQTHLfn for <mib-doctors@ietfa.amsl.com>; Mon, 16 Jun 2014 13:01:13 -0700 (PDT)
Received: from qmta15.westchester.pa.mail.comcast.net (qmta15.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:44:76:96:59:228]) by ietfa.amsl.com (Postfix) with ESMTP id CCCC51A01B2 for <mib-doctors@ietf.org>; Mon, 16 Jun 2014 13:01:12 -0700 (PDT)
Received: from omta22.westchester.pa.mail.comcast.net ([76.96.62.73]) by qmta15.westchester.pa.mail.comcast.net with comcast id F2cZ1o0021ap0As5F81CnN; Mon, 16 Jun 2014 20:01:12 +0000
Received: from JV6RVH1 ([67.189.237.137]) by omta22.westchester.pa.mail.comcast.net with comcast id F81B1o00i2yZEBF3i81BMi; Mon, 16 Jun 2014 20:01:12 +0000
From: "ietfdbh" <ietfdbh@comcast.net>
To: "'Randy Presuhn'" <randy_presuhn@mindspring.com>, "'Benoit Claise'" <bclaise@cisco.com>, "'MIB Doctors \(E-mail\)'" <mib-doctors@ietf.org>
References: <22410435.1402107147107.JavaMail.root@mswamui-valley.atl.sa.earthlink.net>
In-Reply-To: <22410435.1402107147107.JavaMail.root@mswamui-valley.atl.sa.earthlink.net>
Date: Mon, 16 Jun 2014 15:59:49 -0400
Message-ID: <02e801cf899d$8802cf30$98086d90$@comcast.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQIXTaVxMfrVpujp4bWA44rOYgMSNZrkn5aw
Content-Language: en-us
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1402948872; bh=G29QdJOR08fvVf21dTSI/gN2KvnO8lgbVjkJEKqklVE=; h=Received:Received:From:To:Subject:Date:Message-ID:MIME-Version: Content-Type; b=iMzoqi8hFeGiWhwMvymrvG0utgOMJh1CoeyFRe/ibjCrJ0Z5IQg/74ZDU+GbWmDO9 YdmZOvYnGa7SDu6Z4e3DJpCMiQdMX3TUQaFVzbdhUr1NxQ+oQxVXfmNqWvTx3P1o4u 8/3OxvGAXBsNLCjPfDO0pAoCeAuYvk+LjErLkNXzkuk9ZT3pJlu6nRZXEsA8GiUalq u7YGEx8fBp2QC2XgWg8xRWED7knKlbIqw+VgPkJAhnejYbs8fKD5+YUcr3e6Z2d5JP 0aL4POXyVHZ3iYx3EXgQYIngTi3DgbjJ9+ooVCeQ7WkJvj6p++kwY7D1Ok0TFM1gwu F3lHd1UFXvrCg==
Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/uQEyErssVvz0s9B_q83qHtlM3kE
Cc: 'Adrian Farrel' <adrian@olddog.co.uk>
Subject: Re: [MIB-DOCTORS] Fwd: Request to add to the MIB boilperplate for "writeable objects"
X-BeenThere: mib-doctors@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: MIB Doctors list <mib-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mib-doctors/>
List-Post: <mailto:mib-doctors@ietf.org>
List-Help: <mailto:mib-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Jun 2014 20:01:24 -0000

+1

David Harrington
ietfdbh@comcast.net
+1-603-828-1401

> -----Original Message-----
> From: MIB-DOCTORS [mailto:mib-doctors-bounces@ietf.org] On Behalf Of
> Randy Presuhn
> Sent: Friday, June 06, 2014 10:12 PM
> To: Benoit Claise; MIB Doctors (E-mail)
> Cc: Adrian Farrel
> Subject: Re: [MIB-DOCTORS] Fwd: Request to add to the MIB boilperplate for
> "writeable objects"
> 
> Hi -
> 
> >From: Benoit Claise <bclaise@cisco.com>
> >Sent: Jun 5, 2014 5:01 AM
> >To: "MIB Doctors (E-mail)" <mib-doctors@ietf.org>
> >Cc: Adrian Farrel <adrian@olddog.co.uk>
> >Subject: [MIB-DOCTORS] Fwd: Request to add to the MIB boilperplate for
> 	"writeable objects"
> >
> >Dear MIB-doctors,
> >
> >Here is a proposal from Adrian on updating the MIB boilerplate.
> >This looks good to me. Any feedback?
> 
> The proposal contains two parts.  The first provides a historical
> record of the working group's thinking, but is of no help in
> implementation or deployment.  The second is purely tutorial.
> >From my perspective, each would increase the length of a
> specification without increasing its utility.  Consequently,
> I believe this change would be counterproductive and should
> *not* be adopted.
> 
> Randy
> 
> >Regards, Benoit
> >
> >
> >-------- Original Message --------
> >Subject: 	Request to add to the MIB boilperplate for "writeable
> objects"
> >Date: 	Wed, 4 Jun 2014 17:06:16 +0100
> >From: 	Adrian Farrel <adrian@olddog.co.uk>
> >Reply-To: 	<adrian@olddog.co.uk>
> >To: 	<bclaise@cisco.com>
> >
> >
> >
> >Hi Benoit,
> >
> >After the work on the BFD MIB modules and considering the IESG
> statement on
> >writeability, would you consider adding to the MIB boilerplate an
optional
> piece
> >of text that says...
> >
> >====
> >The following objects in the MIB modules in this document have write
> access
> >either through read-write or read-create MAX-ACCESS clauses. The level of
> access
> >to these objects have been discussed by the <xxxx> working group and it
> was
> >concluded that write access was beneficial for the following reasons:
> >
> >- <list of reasons>
> >
> >- <list of objects>
> >
> >As with all MIB modules, an attempt to SET or CREATE an object to a value
> that
> >is not supported by the implementation will result in a failure using a
return
> >code that indicates that the value is not supported.
> >
> >====
> >
> >I think this would help to contain and control work on MIB documents in
the
> >future, and would give the Doctors something to review against.
> >
> >Please wordsmith to your heart's content.
> >
> >Ciao,
> >Adrian
> >
> >.
> >
> >
> >
> 
> _______________________________________________
> MIB-DOCTORS mailing list
> MIB-DOCTORS@ietf.org
> https://www.ietf.org/mailman/listinfo/mib-doctors


From nobody Mon Jun 16 13:06:03 2014
Return-Path: <ietfdbh@comcast.net>
X-Original-To: mib-doctors@ietfa.amsl.com
Delivered-To: mib-doctors@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 106821A01CB for <mib-doctors@ietfa.amsl.com>; Mon, 16 Jun 2014 13:06:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.651
X-Spam-Level: 
X-Spam-Status: No, score=-2.651 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gy9riNzqMuZB for <mib-doctors@ietfa.amsl.com>; Mon, 16 Jun 2014 13:05:59 -0700 (PDT)
Received: from qmta01.westchester.pa.mail.comcast.net (qmta01.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:16]) by ietfa.amsl.com (Postfix) with ESMTP id A50081A01CA for <mib-doctors@ietf.org>; Mon, 16 Jun 2014 13:05:59 -0700 (PDT)
Received: from omta05.westchester.pa.mail.comcast.net ([76.96.62.43]) by qmta01.westchester.pa.mail.comcast.net with comcast id F63X1o0020vyq2s5185zGq; Mon, 16 Jun 2014 20:05:59 +0000
Received: from JV6RVH1 ([67.189.237.137]) by omta05.westchester.pa.mail.comcast.net with comcast id F85y1o0192yZEBF3R85ycu; Mon, 16 Jun 2014 20:05:59 +0000
From: "ietfdbh" <ietfdbh@comcast.net>
To: "'Juergen Schoenwaelder'" <j.schoenwaelder@jacobs-university.de>, "'Thomas D. Nadeau'" <tnadeau@lucidvision.com>
References: <07a601cf800e$ea9710e0$bfc532a0$@olddog.co.uk> <53905C1E.10808@cisco.com> <9904FB1B0159DA42B0B887B7FA8119CA5C7FE398@AZ-FFEXMB04.global.avaya.com> <4308CFC7-7341-4D66-A50C-5B808DB9FCEC@lucidvision.com> <20140605154918.GC12274@elstar.local>
In-Reply-To: <20140605154918.GC12274@elstar.local>
Date: Mon, 16 Jun 2014 16:04:36 -0400
Message-ID: <02ec01cf899e$3314e840$993eb8c0$@comcast.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQGAdguEPUXs4QCQJj1X46ZyvDpMqgKTe9G0AS4R5HgBy9ZnqAHjCwegm9bLk1A=
Content-Language: en-us
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1402949159; bh=n+lr4EYjW818NhGG8srkfKyqFMWCY9sjmlNobtCfrZM=; h=Received:Received:From:To:Subject:Date:Message-ID:MIME-Version: Content-Type; b=h8/Hx4Q606LxuU44c/JSKdeGeMB0CU/OilW6FZnpJduMT3YUyPm1K40JEMKThq7Ht QW6Qn6zMp1UOc6KEQN/ns7VN29cgIfdsVZycOC4JzGJ3D0Ki5zK0XQs2Dq5Xh2mt+8 O5U3ZwC0xJEQOTia9lg8TZioHxP0Dg8/OCIQjBqCQieBbGLu4qe1BCqUq2BnzQdX24 KmQpYygfD8xvTGK9Wq7ihoofaUAQGHcfUktDt0UUWCUL98lgiOqf4ZX3wOryjztJMX dFNDR2MsTP2N0/YH2SYDvVZDqKmBT9V34n5IwHH07nAlawKVRIvYcUvIxJC5MfYVFR CQm0dSrFJIwYg==
Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/P8JS_0wFDRK_yw-vUAXbkDB4rTY
Cc: 'Farrel Adrian' <adrian@olddog.co.uk>, "'MIB Doctors \(E-mail\)'" <mib-doctors@ietf.org>
Subject: Re: [MIB-DOCTORS] Fwd: Request to add to the MIB boilperplate for "writeable objects"
X-BeenThere: mib-doctors@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: MIB Doctors list <mib-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mib-doctors/>
List-Post: <mailto:mib-doctors@ietf.org>
List-Help: <mailto:mib-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Jun 2014 20:06:01 -0000

+1

David Harrington
ietfdbh@comcast.net
+1-603-828-1401

> -----Original Message-----
> From: MIB-DOCTORS [mailto:mib-doctors-bounces@ietf.org] On Behalf Of
> Juergen Schoenwaelder
> Sent: Thursday, June 05, 2014 11:49 AM
> To: Thomas D. Nadeau
> Cc: Farrel Adrian; MIB Doctors (E-mail)
> Subject: Re: [MIB-DOCTORS] Fwd: Request to add to the MIB boilperplate for
> "writeable objects"
> 
> On Thu, Jun 05, 2014 at 11:30:33AM -0400, Thomas D. Nadeau wrote:
> >
> > 	I agree. This is just swimming around the drain. We need to just
> emphatically stop r-w and be done with this issue.
> >
> 
> And I disagree with that. There are legitimate reasons for r-w and the
> IESG statement is not generally banning r-w either.
> 
> /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/>
> 
> _______________________________________________
> MIB-DOCTORS mailing list
> MIB-DOCTORS@ietf.org
> https://www.ietf.org/mailman/listinfo/mib-doctors


From nobody Tue Jun 17 06:40:55 2014
Return-Path: <ietfdbh@comcast.net>
X-Original-To: mib-doctors@ietfa.amsl.com
Delivered-To: mib-doctors@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D61BF1A004D for <mib-doctors@ietfa.amsl.com>; Tue, 17 Jun 2014 06:40:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.651
X-Spam-Level: 
X-Spam-Status: No, score=-4.651 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, GB_I_LETTER=-2, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O9x85L8xc6H4 for <mib-doctors@ietfa.amsl.com>; Tue, 17 Jun 2014 06:40:49 -0700 (PDT)
Received: from qmta08.westchester.pa.mail.comcast.net (qmta08.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:80]) by ietfa.amsl.com (Postfix) with ESMTP id EFDA81A0389 for <mib-doctors@ietf.org>; Tue, 17 Jun 2014 06:40:46 -0700 (PDT)
Received: from omta08.westchester.pa.mail.comcast.net ([76.96.62.12]) by qmta08.westchester.pa.mail.comcast.net with comcast id FRSm1o0020Fqzac58RgmCB; Tue, 17 Jun 2014 13:40:46 +0000
Received: from JV6RVH1 ([67.189.237.137]) by omta08.westchester.pa.mail.comcast.net with comcast id FRgl1o00X2yZEBF3URglSs; Tue, 17 Jun 2014 13:40:46 +0000
From: "ietfdbh" <ietfdbh@comcast.net>
To: "Benoit Claise" <bclaise@cisco.com>
References: <030201cf89f4$8547e260$8fd7a720$@comcast.net>
In-Reply-To: <030201cf89f4$8547e260$8fd7a720$@comcast.net>
Date: Tue, 17 Jun 2014 09:39:22 -0400
Message-ID: <033101cf8a31$8c206e80$a4614b80$@comcast.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQGvX9EMWvq5LmOaZ0DTXqp9cVV6b5u1oxUA
Content-Language: en-us
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1403012446; bh=N2ec7zulB6gMA/VRcBDQXsQmyjc4V3Hu9jwpj4l99H8=; h=Received:Received:From:To:Subject:Date:Message-ID:MIME-Version: Content-Type; b=wHU5GL97WPhZ43LdA+xkVVQwjG0knAP33KVRWgMWsyJyjM6t27xQcQvw8BuaLzyFs uLlwHSutcFGwrYzPVl0LTZHaY74kkIDefDkYQP8JzOdBwD/eQGA0BiTBsrFDgxq6nf tIamIn8hc4QJu7f3nxawQhOluQN11euLHJjJdDhSAbdJS5igYq75/zs+SJdQIX/CUh FxkrUo88jEuDYSIN6CvzoemxorzUasADjI/N3VkBzxmjftrj3M5afZ2k8xT9dmWdyB VFmrTR+N3rf6g0wB4BXCWgJ2NGNrWT/+vFNhMl7S38nIQsgEU13lFwZICx/xVIPO/3 BDD+qT+hCe6hw==
Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/EWQMogl-MEiiZSK9jFNeLKs4HbM
Cc: MIB Doctors <mib-doctors@ietf.org>
Subject: [MIB-DOCTORS] FW: MIB Doctor review of draft-ietf-behave-nat-mib-11
X-BeenThere: mib-doctors@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: MIB Doctors list <mib-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mib-doctors/>
List-Post: <mailto:mib-doctors@ietf.org>
List-Help: <mailto:mib-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Jun 2014 13:40:54 -0000

Hmmm; behave-ads doesn't work. So I'll send direct.
Forgot to include mib doctors list.

David Harrington
ietfdbh@comcast.net
+1-603-828-1401

> -----Original Message-----
> From: David Harrington [mailto:dbharrington@comcast.net]
> Sent: Tuesday, June 17, 2014 2:22 AM
> To: draft-ietf-behave-nat-mib@tools.ietf.org
> Cc: behave-chairs@ietf.org; behave-ads@ietf.org
> Subject: MIB Doctor review of draft-ietf-behave-nat-mib-11
> 
> Hi,
> 
> I have done a MIB Doctor review of draft-ietf-behave-nat-mib-11.
> I have reviewed this document as part of the MIB Doctor directorate's
> ongoing
> effort to review all IETF documents being processed by the IESG.  These
> comments
> were written primarily for the benefit of the operational area directors.
> Document editors and WG chairs should treat these comments just like any
> other
> last call comments.
> 
> My impression is that this document is not ready for publication.
> 
> Technical issues:
> The nature of the realm usage in NAT-MIB could have serious consequences
> to
> existing deployments of other MIB modules.
> The use of calculated thresholds, and calculated values to compare to
> thresholds, could be problematic, especially to resource-constrained agent
> implementations.
> 
> Editorial issues:
> A significant cause for concern is the naming, which doesn't follow RFC
4181
> guidelines. This will make the MIB harder for operators to use in the
field.
> Another significant concern is the lack of REFERENCE clauses. This will
make
> the MIB harder for operators to use in the field.
> The description clauses are sometimes rather sparse. This will make the
MIB
> harder for operators to use in the field.
> Some of the descriptions in the module are sparse, while the surrounding
> text contains a better description. But MIB modules are frequently
> distributed without the surrounding RFC text. This will make the MIB
harder
> for operators to use in the field.
> The IMPORTS clauses don't identify the RFC that contains the MIB module
> being imported from. This will make the MIB harder for operators to use in
> the field.
> The redefinition of realm in the middle of a bis could be a problem,
> especially for managers. This will make the MIB harder for operators to
use
> in the field.
> 
> 
> Detailed review:
> 
> 1) We have discussed whether the new objects really should be a new MIB
> module, published under a new MIB module name. Reading through this
> document, I feel that deprecating the whole previous NAT-MIB within the
> same
> document is a mistake. It makes the document harder to deal with. This
> really should be two separate documents and two separate MIBs - with
> different module names.
> 
> The current approach might be perfectly viable for an agent
implementation,
> where the NAT-MIB is likely to be an implementation of EITHER the first
half
> of this document, or the second half of this document.
> But it seems problematic for an NMS implementation that has to support
> BOTH
> implementations based on RFC4008, and implementations based on this
> document.
> I especially think about the fact that NMSs import MIB modules, including
> the Description clauses for the managed objects, and can display the
> description clauses so operators can see what the definition of the object
> is.
> With this document, NMS applications MUST parse all the deprecated
> objects,
> even if, at some future time, there are no devices that implement the
> RFC4008 NAT-MIB.
> If the deprecation was handled in a separate RFC from the new MIB module,
> and an NMS no longer had to support the "old" NAT-MIB, then NMSs in the
> future would only need to import the new document.
> 
> I found it especially irritating to review, because I am used to finding
> Textual Conventions at the beginning of the MIB module, which is usually
at
> the beginning of the document containing the MIB module, but here, I had
> to
> look for the T-Cs in the middle of a long MIB module, because I had to
work
> past the first 54 pages of deprecations to find the T-Cs of the new
module.
> Every user of this MIB document will be similarly inconvenienced, over and
> over.
> 
> 2) This new I-D is redefining a term "realm" that is defined in the
original
> NAT-MIB. (see section 3.3).
> RFC4008 defined realm objects to be of type INTEGER, but the new NAT-MIB
> defines realm objects as SnmpAdminStrings.
> An NMS (and operators) needs to be able to support devices that implement
> the "old" NAT-MIB and devices that implement the "new" NAT-MIB.
> With this new NAT-MIB, an NMS user must be aware when they look at the
> description of a realm-related object, whether that object was defined in
> the RFC4008 NAT-MIB or in the <new RFC> NAT-MIB, in order to understand
> which meaning and datatype of the term "realm" applies.
> But since RFC4008 is updated by being deprecated in the same document, in
> the same-named MIB module, the reader of the new NAT-MIB must
> determine
> whether the object was defined in the first half of this document, i.e.,
the
> first half of the NAT-MIB, i.e., the "old" deprecated NAT-MIB, or in the
> second half of this document,  to understand the meaning of the word
> realm.
> I think this is problematic.
> 
> 3) Section 3.3 explains that implementations of MIB modules that
implicitly
> support realms (e.g.,OSPFv2-MIB), and utilize SNMPv3 contexts (or
> presumably
> communities in community-based SNMP) in an SNMP-standard compliant
> manner,
> will no longer be able to do things in those standard-compliant manners,
> because the NAT-MIB design spans realms.
> 
> This I-D should list the names and references for the "many MIBs" that
> "implicitly support realms in one form or another" that may be broken by
> this NAT-MIB's usage of realm. I suggest an "Operational Considerations"
> section for this information. I think the IETF community needs to better
> understand this claim before approving this document.
> 
> 4) I will assume all the RFC4008 objects that are being deprecated have
been
> included here, and each has had its status changed to deprecated. I have
not
> gone through the document looking at each and every deprecation.
> 
> 5) ProtocolNumber is a rather generic name for this textual convention. It
> doesn't start with "nat". I fear there is a potential for conflict.
> This does not follow the conventions recommended in RFC4181 Appendix C:
>    - Names of TCs that are specific to the MIB module and names of
>      SEQUENCE types that are used in conceptual table definitions should
>      start with a prefix Xxx that is the same as xxx but with the
>      initial letter changed to uppercase.  OPT-IF-MIB uses the prefix
>      OptIf on the names of TCs and SEQUENCE types.
> 
> 6) ProtocolNumber is dependent on an IANA registry.
> There should be a REFERENCE clause with a link to the specific IANA
> registry, so implementers/users can see the list of valid values.
> 
> 7) This document does not provide REFERENCE clauses; it really should.
> 
> 8) natPoolID - the description does not describe what a pool is, or
provide
> a REFERENCE clause.
> 
> 9) natBehaviorType has only a reference in the description. In general it
is
> better to actually have a description in the description clause and
provide
> the reference in the REFERENCE clause. This is not merely an academic nit.
> Because GUI-based NMSs frequently display the Description clause in a
> window
> so the user can understand the meaning of the object, it is important that
> the description actually explain the meaning. Providing a reference in the
> description implies that the user would then need to go find the RFC and
> find the section of the RFC, and read the whole section to understand what
> this object means. Not very helpful.
> On top of that, an NMS might know how to track down an RFC and provide a
> link to the document in the REFERENCE clause, but it wouldn't necessarily
> know to parse the Description clause to find the reference.
> 
> 10) NatPoolingType is only used to define the type of one object.
> The description clause in the object is indirect - " "Type of address
> pooling behavior that was used to create this mapping."
> To understand this object, you need to look at the textual convention.
> But the textual convention is also indirect - "Pooling type as described
in
> [RFC4787] sections 4.1."
> Even looking at RFC4787 section 4.1 isn't immediately helpful, because the
> discussion of arbitrary versus paired is a subset of section 4.1 (that is
> not called out as a subsection); it is found in the one-paragraph
> explanatory text for REQ-2. A short description in the OBJECT description
> clause could be made from a couple sentences from section 4.1,
> supplemented
> with a REFRERENCE clause, which would be much easier for users than the
> current indirect-indirect-someplace-in-this-text  approach.
> 
> 11) SubscriberIdentifierType concerns me. We are supposed to be
> standardizing things here. But this appears to be a standardized "bucket"
> which implementers can stuff with their own proprietary identifiers,
> especially the "other" value. How is a vendor-neutral NMS supposed to know
> how to handle the "other" value?
> I feel uncomfortable with this whole identifierType, which implies that an
> implementation needs to go parse the packet to pull out additional
> information to identify the subscriber, without standardizing how this
> information should be extracted from the message in a standardized
> vendor-neutral manner.
> 
> I feel uncomfortable that for the "other" type, each implementation
defines
> the semantics of AND and OR combinations. How should a vendor-neutral
> NMS
> handle the implementation-specific variations; where is the AND/OR
> semantic
> decision documented by each implementer, to make this vendor-
> interoperable?
> 
> For the interfaces choice, how is the set of interface indexes
constructed?
> I'm confused by this. The classifying information is in the packet
(identify
> the subscriber from an incoming packet); so does the packet contain a set
of
> interface indexes that the receiving implementation is supposed to
extract?
> There is no reference to the type of packet involved, and I haven't had to
> unpack a set of interface indices from a packet before. What type of
packet
> contains a set of one or more ifIndexes? The RFC2863 textual convention
> doesn't seem to describe this.
> 
> 12) SubsInterfaceIdRowIndex - unique within what scope? Within the agent?
> 
> 13) I am concerned about abbreviations is naming. RFC4181 Appendix C
> suggests
>    - When abbreviations are used, then they should be used consistently.
>      Inconsistent usage such as
> 
>        xxxYyyDestAddr
>        xxxZzzDstAddr
> 
>      should be avoided.
> 
> But sometimes, object names in this module use Identifier and other times
> ID: natSubscriberVpnIdentifier vs. natSubscriberIPEncapsIdType
> Sometimes it's subscriber, other times it's "subs".
> natSubscriberVpnIdentifier vs. natSubsInterfaceIndex
> Sometimes it's threshold, sometimes it's "thresh":
> natMappingsNotifyThreshold  vs. natSubscriberMapNotifyThresh
> For an operator, especially one under stress, using a command-line SNMP
> tools to query a value, it is really irritating to have some objects
> abbreviated one way and other objects abbreviated other ways.
> 
> 14) This is made worse by inconsistent name construction, such as a set of
> nat limits being named nat + "Limit" + <specific>, as in natLimitMappings
> but the set of notify thresholds are constructed as nat + <specific> +
> "NotifyThreshold", as in natMappingsNotifyThreshold. So operators need to
> recall which way you chose to construct the names, on a case-by-case
basis,
> because you are not being consistent. Why not do nat + <specific> +
"Limit"
> to match the way you construct NotifyThreshold names, or use
> nat+"NotifyThreshold"+<specific> to match how you construct the Limit
> names?
> 
> 15) Once again, I will point out consistency in naming, following Appendix
C
> conventions:
> "   - The descriptor associated with a conceptual table should be of the
>      form xxxZzzTable; the descriptor associated with the corresponding
>      conceptual row should be of the form xxxZzzEntry; the name of the
>      associated SEQUENCE type should be of the form XxxZzzEntry; and the
>      descriptors associated with the subordinate columnar objects should
>      be of the form xxxZzzSomeotherName.  An example from the OPT-IF-MIB
>      is the OTMn table.  The descriptor of the table object is
>      optIfOTMnTable, the descriptor of the row object is optIfOTMnEntry,
>      the name of the associated SEQUENCE type is OptIfOTMnEntry, and the
>      descriptors of the columnar objects are optIfOTMnOrder,
>      optIfOTMnReduced, optIfOTMnBitRates, optIfOTMnInterfaceType,
>      optIfOTMnTcmMax, and optIfOTMnOpticalReach."
> 
> But we find in this NAT-MIB module inconsistency:
> natCountersTable OBJECT-TYPE
> ...
>  natCountersEntry OBJECT-TYPE
> ...
> NatCountersEntry ::=
>        SEQUENCE {
>            natTranslations             Counter64,
>            natOutOfPortErrors          Counter64,
>            natResourceErrors           Counter64,
>            natQuotaDrops               Counter64,
>            natMappingCreations         Counter64,
>            natMappingRemovals          Counter64,
>            natAddressMappingCreations  Counter64,
>            natAddressMappingRemovals   Counter64
>        }
> 
> And
> natLimitsTable OBJECT-TYPE
> ...
> natLimitsEntry OBJECT-TYPE
> ...
>    NatLimitsEntry ::=
>        SEQUENCE {
>            natLimitMappings            Unsigned32,
>            natMappingsNotifyThreshold  Unsigned32,
>            natLimitAddressMappings     Unsigned32,
>            natAddrMapNotifyThreshold   Unsigned32,
>            natLimitFragments           Unsigned32,
>            natLimitSubscribers         Unsigned32
>        }
> (notice Limits vs Limit, as well as objects with no natLimit prefix, as
well
> as "AddressMappings" vs "AddrMap".)
> 
> 16) If there is a concern that descriptor length can become problematic,
> "Threshold" is never used without the "Notify" prefix. You could probably
> shorten the NotifyThreshold names to just use Threshold.
> 
> 17) Consistency. Watermark vs Threshold.
> 
> 18) natLimitMappings - this is in a table of limits for a NAT instance.
> What does "Global" mean in this context? See others in this table as well.
> 
> 19) natMappingsNotifyThreshold - the description is "See
> natNotifMappings."
> Which says "This notification is generated when the number of active
>             mappings exceeds the value of natMappingsNotifyThreshold."
> Why not write the (modified) description into both places rather than
using
> indirection?
> 
> 20) natNotifMappings
> Typically we try to not derive values when defining objects. For example,
> RFC4188 states as a principle " Exclude objects that are simply derivable
> from others in this or
>       other MIB modules."
> But natNotifMappings is triggered when " the number of active mappings
> exceeds the value of natMappingsNotifyThreshold"
> But we don't actually track active mappings; we track creations and
> removals, and we calculate active by subtracting removals from creations
> (active=creations-removals).
> If you want to use active against the threshold, why not simply track
active
> and skip tracking creations and removals?
> 
> Is there a reason to track creations and removals?
> If the maximum number of creations performed  is important (maybe for
> memory
> management or something?), then why not track creations and active and let
> somebody else calculate the removals (removals=creations-active)
> If the number of removals is important (I have no idea why), then you can
> track active and removals, and let somebody else calculate
> (creations=active+removals)
> This way a notification doesn't have to wait to calculate active.
> 
> 21) natNotifMappings - the relationship between the notification and
> thresholds is clear.
> The relationship to "which mappings" is a bit less clear.
> I see a natMapIntAddrTable, and a natMappingTable; which one is related to
> natNotifMappings?
> (and is the savings from dropping the y from notify significant?)
> 
> I assume the fact we are sending a notification means it is important for
> the operator to know right away when "active exceeds threshold" happens.
> I have to guess that this might be related to memory/resource management.
> But I have to guess because nothing is said about why these particular
> values are tracked.
> Nothing is said about table row re-use when a mapping is removed.
> Is it really important to know the creation and removal counts, rather
than
> just the active count?
> Is it important to not reuse an index value to make sure that the NMS
> doesn't associate previously acquired data with a new mapping.
> (This is important, for example, if ifIndex changes during a reboot,
because
> an NMS could take data associated with an old ifIndex and confuse it as
> being associated with a new ifIndex, and totally misinterpret trends, and
so
> on. Other MIB modules need to protect against reuse of an index value, at
> least for some period of time, or until rollover.)
> 
> 22) It's a good thing the description of natPoolTable is "Table of pools"
> because I might have confused it as being something else. 8-ball anyone?
> Description please?
> 
> 23) natpoolRealm - "Realm to which this pool's addresses belong."
> MIB modules are often distributed without the surrounding text from the
> RFC.
> 
> So it is important to be sure the description is meaningful without the
> whole RFC being present.
> At a minimum, especially since you are defining realm in this document,
you
> should provide a REFERENCE to the text in this RFC that contains the
> definition for realm.
> 
> 24) natNotifPoolWatermarkLow and WatermarkHigh
> 
> we usually try to not use derived values in MIB modules. We try to keep
the
> agent simple, and push complexity toward the NMS, which normally has far
> more resources available.
> When you set a watermark/threshold as a percentage, then the system
> needs to
> use CPU cycles to calculate the percentage - CPU cycles that might be
better
> used forwarding packets.
> 
> The calculations you expect are rather complex - you require summing
> (allocations - deallocations) over all address ranges, then dividing by
the
> total number of ip addresses in the poll and by the size of the port range
> (calculated by portmax-portmin+1).
> 
> I'm not sure that that formula is unambiguous; is that
> (sum(allocations-deallocation)/ipaddresses)/portrange or am I calculating
> something with (ip addresses and size of portrange) before dividing? Can
you
> use parentheses or something?
> 
> How often should this complex calculation be done to monitor the
> percentage
> versus the threshold? Should this be re-calculated ***every time*** one of
> the following changes: allocation or deallocation across any address
range,
> total number of ip addresses, or size of the port range? (and of course,
the
> watermark setting).
> 
> Wow! That seems like a lot of CPU cycles.
> 
> 25) natpoolIndex - the description doesn't mention the scope of
uniqueness.
> Is this unique across all address pools in all instances? Unique within a
> nat instance, but not necessarily across other nat instances?
> 
> 26) natPool watermarks
> There is mention of low usage mode and high usage mode. Is there a
> REFERENCE
> you can make, maybe to NAT requirements or something, that explains this a
> bit more?
> Is there a reason why BEHAVE is not trying to standardize low/high usage
> behaviors? (isn't standardizing behaviors what behave is all about?)
> 
> Are the "may" terms here RFC2119-compliant? Usually RFC2119 "may" terms
> are
> capitalized.
> 
> 27) It is very helpful to add comments to your IMPORTS identifying the RFC
> that contains the MIB you are importing from.
> 
> 28) natPoolRangeType - can this support any of the address types allowed
by
> this textual convention? Or should the text constrain the acceptable
values?
> I'm not sure which ways to limit this are acceptable. Let me know if all
the
> address types cannot be supported, and I'll check with other mib doctors
to
> determine the best way to constrain it.
> 
> 29) natMappingTable - "Table of mappings indexed by external 3-tuple."
> I'm not sure this is accurate, given
>        INDEX { natInstanceIndex,
>                natMappingProto,
>                natMappingExtRealm,
>                natMappingExtAddressType,
>                natMappingExtAddress,
>                natMappingExtPort }
> 
> 30) natMappingExtAddress - can you point me to the REFERENCE for "the
> undefined address"? I didn't find it in RFC4001.
> Ditto for natMappingIntAddress
> 
> 31) natMappingMapBehavior and natMappingFilterBehavior - for reasons
> mentioned above, please include a description, not just a reference in the
> description text. Put the reference in a REFERENCE clause.
> 
> 32) natMappingSubsIndex - you don't really need the Index suffix. This
> would
> be more meaningful as natMappingSubscriber
> 
> 33) natSubscribersTable, natSubscribersEntry, and natSubscriberIndex (et
al)
> are not consistent. I recommend losing the plural.
> 
> 34) do the existence of fields natSubscriberVlanIdentifier,
> natSubscriberVpnIdentifier, natSubscriberIPEncapsIdType, and
> natSubscriberIPEncapsIdAddr depend on the value of
> natSubscriberIdentifierType? If so, then it might be better to define this
> as a sparse augments table. Let me know, and I'll check with the MIB
Doctors
> list about the best way to do this.
> 
> 35) natSubscriberIdentifierType - " Unused identifier values MUST be zero
or
> equivalent".
> I think this is under-specified.
> I think the zero-equivalents should be specified here for each type.
> When the type is none(0), and the identifier is "none", does this mean the
> identifier field is not implemented, or has a zero value or empty string
or
> what?
> Which of these is the zero equivalent?
> The TC SubscriberIdentifierType says the interfaces(1) type means the
> identifier is a set of **one or more** interface indexes. What is the
> zero-equivalent of a set of one or more interface indexes?
> VPNIdorZero says "           The semantics of the value zero-length OCTET
> STRING are
>             object-specific and must therefore be defined
>             as part of the description of any object that uses this
>             syntax."
> So presumably, the zero equivalent is a zero-length OCTET STRING. But the
> description here does not define the semantics of the zero-length string;
it
> only implies the semantics.
> And for other(5), we have no idea what a zero-equivalent is.
> 
> 36) natSubscriberIntPrefixType is a "Subscriber's internal prefix type."
> While the corresponding address is a "Prefix assigned to a subscriber's
> CPE."
> I tend to think of a CPE as being the border between a subscriber's
network
> and an ISP's network.
> If the subscriber entry represents a host served by a managed enterprise
> NAT, is this still the prefix type for the CPE?
> Please clarify if the type is the internal prefix type for the
subscriber's
> CPE, or simply the subscriber's internal prefix type.
> 
> 37) natSubscriberLimitMappings - again, we should avoid calculated
objects.
> This depends on "active" mappings, which is a calculated value.
> 
> 38) natSubscriberMapNotifyThresh - consistency in naming please; this
> seems
> to be a real problem throughout the subscriber table.
> (natSubscribers vs natSubscriber, thresh, mappngs vs Map)
> 
> 39) natSubscriberIPEncapsIdType -  I find the "when not unknown(0)" to be
> an
> odd description. The InetAddressType description is " A value that
> represents a type of Internet address." I think that should suffice here
as
> well, even though unknown(0) has special semantics described in the T-C.
> 
> 40) natSubsInterfaceIdentifierTable - the description contains a sentence
> fragment; I don't know what it means - " 'OR' semantics if multiple
> interface indexes
>             are present." I find the other sentences a bit short; I
> recommend rewriting the description to make it clearer.
> 
> 41) natSubsInterfaceIdSubsIndex - I have some concerns about the use of
> Index as parts of object descriptors and part of object descriptions, for
> objects that are not INDEXes, when INDEX is a SMI reserved word (RFC2578,
> section  3.7). I don't find the "Index" suffix necessary. I think
> SubscriberIndex would be fine as Subscriber, and SubsInterfaceIdRowIndex
> would be fine as SubsInterfaceIdRow, and natSubsInterfaceIdRowIndex
> would be
> fine as natSubsInterfaceIdRow, etc.
> 
> 42) natSubsInterfaceIdRowIndex - the description is "Row index."  There is
> no description of why this is being defined, or what it is expected to be
> used for.
> The T-C has a better explanation of its uniqueness and its assignment to
> rows, but no description of why it is needed.
> It might have been better explained in the natSubsInterfaceIdentifierEntry
> description, where it is used in the INDEX. But I don't understand the
> description there - "Each entry provides a single interface index."
> Can you provide an example of how this table works?
> 
> 43) I am a bit concerned about the compliance options. If we are
> standardizing behaviors, why do we have five compliance levels? Lots of
> compliance levels = lack of standardization.
> 
> --- Security considerations ---
> 44) What objects reveal host identities? Do  you mean host addresses? I
> think the community has made a statement about identity versus address in
> efforts like HIP and SNMPv3.
> 45) If a disgruntled former employee can break into private hosts, can
> attackers who never worked for the employer do so as well? I don't have
any
> employees, and no former employees; does that mean this is an attack
> vector
> I can totally ignore?
> 
> 
> Hope this helps,
> 
> David Harrington
> dbharrington@comcast.net
> +1-603-828-1401



From nobody Mon Jun 23 14:12:31 2014
Return-Path: <bclaise@cisco.com>
X-Original-To: mib-doctors@ietfa.amsl.com
Delivered-To: mib-doctors@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7346D1B2BFA; Mon, 23 Jun 2014 14:12:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.452
X-Spam-Level: 
X-Spam-Status: No, score=-7.452 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id udtvrcVQB3Kp; Mon, 23 Jun 2014 14:12:14 -0700 (PDT)
Received: from aer-iport-4.cisco.com (aer-iport-4.cisco.com [173.38.203.54]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5B0361B2C3E; Mon, 23 Jun 2014 14:12:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4834; q=dns/txt; s=iport; t=1403557934; x=1404767534; h=message-id:date:from:mime-version:to:subject:references: in-reply-to:content-transfer-encoding; bh=I0WqsR1AJrX71LeyFMdjfHvR7oBQgkERkvs6A7ClH44=; b=P+FsuK+0pAyJjpZMFlEn9CmD4oLak/+G49byilFLmZiwanYUiK6mKmnf u3qD8wPWE15S081J0vVOUpEWWnWHq+aLJWNhpj+0z/NEDa89OGwB2qUJM m8F3Zqefz1Khv1jLFfr4atSJwKV/jeEEv1zi81SCtauw5HH54gNnyCPtf E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AtIEAHOXqFOtJssW/2dsb2JhbABQCYNfqx0BAQEBAQeZNQGBJnWEAwEBAQQ4QA0ELBYPCQMCAQIBOwoGAQwGAgEBiD4Nw1MTBIVjhXeCQAcKAVeEQwEDmkyGfYxmggCBRDuBOg
X-IronPort-AV: E=Sophos;i="5.01,532,1400025600"; d="scan'208";a="92044573"
Received: from aer-iport-nat.cisco.com (HELO aer-core-4.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP; 23 Jun 2014 21:12:10 +0000
Received: from [10.60.67.84] (ams-bclaise-8913.cisco.com [10.60.67.84]) by aer-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id s5NLC9Hd013200; Mon, 23 Jun 2014 21:12:09 GMT
Message-ID: <53A89829.1010407@cisco.com>
Date: Mon, 23 Jun 2014 23:12:09 +0200
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: "aaa-doctors@ietf.org" <aaa-doctors@ietf.org>, "MIB Doctors (E-mail)" <mib-doctors@ietf.org>, YANG Doctors <yang-doctors@ietf.org>, "ops-dir@ietf.org" <ops-dir@ietf.org>, "pm-dir@ietf.org" <pm-dir@ietf.org>, IETF DNS Directorate <dns-dir@ietf.org>
References: <20140619223558.21435.31164.idtracker@ietfa.amsl.com>
In-Reply-To: <20140619223558.21435.31164.idtracker@ietfa.amsl.com>
X-Forwarded-Message-Id: <20140619223558.21435.31164.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/yEnltrl0ksxmyJ_IKlba5aB7I2Q
Subject: [MIB-DOCTORS] Fwd: [IESG-AGENDA-DIST] Summarized Agenda for the 2014-06-26 IESG Teleconference
X-BeenThere: mib-doctors@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: MIB Doctors list <mib-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mib-doctors/>
List-Post: <mailto:mib-doctors@ietf.org>
List-Help: <mailto:mib-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Jun 2014 21:12:18 -0000

Dear all,

Please find below the agenda of the June 26th IESG telechat.
Please send your questions, comments and concerns before June 25th COB.

Thanks and Regards, Benoit.

-------- Original Message --------

INTERNET ENGINEERING STEERING GROUP (IESG)
Summarized Agenda for the 2014-06-26 IESG Teleconference

This agenda was generated at 2014-06-19 15:34:10 PDT
Up-to-date web version of this agenda can be found at:
https://datatracker.ietf.org/iesg/agenda/



2. Protocol Actions
2.1 WG Submissions
2.1.1 New Items
     
   o draft-ietf-hip-rfc4843-bis-05  - IETF stream
     An IPv6 Prefix for Overlay Routable Cryptographic Hash Identifiers
     Version 2 (ORCHIDv2) (Proposed Standard)
     Token: Ted Lemon
     IANA Review: IANA - Not OK
     Consensus: Yes

   o draft-ietf-hip-rfc5201-bis-14  - IETF stream
     Host Identity Protocol Version 2 (HIPv2) (Proposed Standard)
     Token: Ted Lemon
     IANA Review: IANA - Not OK
     Consensus: Yes

   o draft-ietf-hip-rfc5202-bis-05  - IETF stream
     Using the Encapsulating Security Payload (ESP) Transport Format with
     the Host Identity Protocol (HIP) (Proposed Standard)
     Token: Ted Lemon
     IANA Review: IANA OK - Actions Needed
     Consensus: Yes

   o draft-ietf-p2psip-self-tuning-14  - IETF stream
     Self-tuning Distributed Hash Table (DHT) for REsource LOcation And
     Discovery (RELOAD) (Proposed Standard)
     Token: Alissa Cooper
     IANA Review: Version Changed - Review Needed
     Consensus: Yes

   o draft-ietf-v6ops-clatip-03  - IETF stream
     IPv4 Service Continuity Prefix (Proposed Standard)
     Token: Joel Jaeggli
     IANA Review: IANA - Not OK
     Consensus: Yes

   o draft-ietf-appsawg-sieve-duplicate-07  - IETF stream
     Sieve Email Filtering: Detecting Duplicate Deliveries (Proposed
     Standard)
     Token: Barry Leiba
     IANA Review: Version Changed - Review Needed
     Consensus: Yes

   o draft-ietf-tram-stun-dtls-03  - IETF stream
     Datagram Transport Layer Security (DTLS) as Transport for Session
     Traversal Utilities for NAT (STUN) (Proposed Standard)
     Token: Spencer Dawkins
     IANA Review: IANA - Review Needed
     Consensus: Unknown
     Last call expires: 2014-06-25

2.1.2 Returning Items
     
   o draft-ietf-mboned-auto-multicast-17  - IETF stream
     Automatic Multicast Tunneling (Proposed Standard)
     Note: Lenny Giuliano (lenny@juniper.net) is the Document Shepherd.
     Token: Joel Jaeggli
     IANA Review: IANA OK - Actions Needed
     Consensus: Yes

2.2 Individual Submissions
2.2.1 New Items
     
   o draft-salgueiro-dispatch-websocket-sipclf-01  - IETF stream
     Indicating WebSocket Protocol as a Transport in the Session
     Initiation Protocol (SIP) Common Log Format (CLF) (Proposed
     Standard)
     Token: Richard Barnes
     IANA Review: IANA OK - Actions Needed
     Consensus: Unknown

2.2.2 Returning Items
     
   o draft-kelsey-intarea-mesh-link-establishment-06  - IETF stream
     Mesh Link Establishment (Proposed Standard)
     Note: Robert Cragie (robert.cragie@gridmerge.com) is the document
     shepherd.
     Token: Ted Lemon
     IANA Review: IANA - Not OK
     Consensus: Yes

2.3 Status Changes
2.3.1 New Items

   NONE

2.3.2 Returning Items

   NONE

3. Document Actions
3.1 WG Submissions
3.1.1 New Items
     
   o draft-ietf-v6ops-enterprise-incremental-ipv6-05  - IETF stream
     Enterprise IPv6 Deployment Guidelines (Informational)
     Token: Joel Jaeggli
     IANA Review: IANA OK - No Actions Needed
     Consensus: Yes

3.1.2 Returning Items

   NONE

3.2 Individual Submissions Via AD
3.2.1 New Items
     
   o draft-adolf-dvb-urn-upd-00  - IETF stream
     Update to the Registrant Information for the Digital Video
     Broadcasting Project (DVB) Uniform Resource Name (URN) Namespace
     (Informational)
     Token: Barry Leiba
     IANA Review: IANA OK - Actions Needed
     Consensus: Unknown

3.2.2 Returning Items

   NONE

3.3 Status Changes
3.3.1 New Items

   NONE

3.3.2 Returning Items

   NONE

3.4 IRTF and Independent Submission Stream Documents
3.4.1 New Items

   o conflict-review-wilde-xml-patch-00
     IETF conflict review for draft-wilde-xml-patch
       draft-wilde-xml-patch-10
       A Media Type for XML Patch Operations (ISE: Informational)
     Token: Barry Leiba

3.4.2 Returning Items

   NONE

4. Working Group Actions
4.1 WG Creation
4.1.1 Proposed for IETF Review

   o Transport Services (taps)

4.1.2 Proposed for Approval

   o TCP Increased Security (tcpinc)

4.2 WG Rechartering
4.2.1 Under Evaluation for IETF Review

   NONE

4.2.2 Proposed for Approval

   o Domain Name System Operations (dnsop)




