
From bclaise@cisco.com  Sat Feb  1 02:20:30 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 768F91ACCDE; Sat,  1 Feb 2014 02:20:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.036
X-Spam-Level: 
X-Spam-Status: No, score=-10.036 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.535, 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 hAoLsPNm8sK3; Sat,  1 Feb 2014 02:20:28 -0800 (PST)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) by ietfa.amsl.com (Postfix) with ESMTP id CA02E1A1F66; Sat,  1 Feb 2014 02:20:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5103; q=dns/txt; s=iport; t=1391250024; x=1392459624; h=message-id:date:from:mime-version:to:subject:references: in-reply-to:content-transfer-encoding; bh=73xsq5RhwJKTMfxYjHmvoT/L/vddripmNZiC2k2bqgA=; b=MG/eZp4tYO2MUvfgPdp/NL8aeClZrz9LjoDoLSb8WE+Wrzlboay0we3k FTnGbsl0r1r964paLO/67hCxtQ80ekofjsJTFBaLHpnFBOU5x0Ip720RT UrPYfY1gZpimn7W3Tt3DY5fRn/NA7A07RmSTOLn4LNJWTDBlrRHpe4M34 k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AiQFAFfJ7FKQ/khR/2dsb2JhbABYgwy7Z4MIgQYWdIIlAQEBBDhADQQdDxYPCQMCAQIBNw4GAQwIAQGIAc0qF48QhDgBA5gqhkiLWYMuOw
X-IronPort-AV: E=Sophos;i="4.95,760,1384300800";  d="scan'208";a="4512083"
Received: from ams-core-1.cisco.com ([144.254.72.81]) by aer-iport-1.cisco.com with ESMTP; 01 Feb 2014 10:20:22 +0000
Received: from [10.60.67.88] (ams-bclaise-8917.cisco.com [10.60.67.88]) by ams-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id s11AKL2K007264; Sat, 1 Feb 2014 10:20:21 GMT
Message-ID: <52ECCA65.4000105@cisco.com>
Date: Sat, 01 Feb 2014 11:20:21 +0100
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.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: <20140130234822.4124.16034.idtracker@ietfa.amsl.com>
In-Reply-To: <20140130234822.4124.16034.idtracker@ietfa.amsl.com>
X-Forwarded-Message-Id: <20140130234822.4124.16034.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [MIB-DOCTORS] IESG-AGENDA-DIST] Summarized Agenda for the 2014-02-06 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: Sat, 01 Feb 2014 10:20:30 -0000

Dear all,

Please find below the agenda of the Feb 6th IESG telechat.
Please send your questions, comments, and concerns before Feb 5th COB.

Thanks and Regards, Benoit.

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

  2. Protocol Actions
2.1 WG Submissions
2.1.1 New Items
     
   o draft-ietf-alto-protocol-25  - IETF stream
     ALTO Protocol (Proposed Standard)
     Token: Spencer Dawkins
     IANA Review: IANA - Review Needed
     Consensus: Unknown
     Last call expires: 2014-02-04

   o draft-ietf-p2psip-rpr-11  - IETF stream
     An Extension to REsource LOcation And Discovery (RELOAD) Protocol to
     Support Relay Peer Routing (Proposed Standard)
     Token: Gonzalo Camarillo
     IANA Review: IANA OK - Actions Needed
     Consensus: Yes

   o draft-ietf-p2psip-drr-11  - IETF stream
     An Extension to REsource LOcation And Discovery (RELOAD) Protocol to
     Support Direct Response Routing (Proposed Standard)
     Token: Gonzalo Camarillo
     IANA Review: IANA OK - Actions Needed
     Consensus: Yes

   o draft-ietf-xrblock-rtcp-xr-qoe-13  - IETF stream
     RTP Control Protocol (RTCP) Extended Report (XR) Blocks for MOS
     Metric Reporting (Proposed Standard)
     Token: Gonzalo Camarillo
     IANA Review: IANA OK - Actions Needed
     Consensus: Yes

   o draft-ietf-ancp-mc-extensions-14  - IETF stream
     Multicast Control Extensions for ANCP (Proposed Standard)
     Token: Ted Lemon
     IANA Review: IANA OK - Actions Needed
     Consensus: Unknown

   o draft-ietf-stox-core-09  - IETF stream
     Interworking between the Session Initiation Protocol (SIP) and the
     Extensible Messaging and Presence Protocol (XMPP): Architecture,
     Addresses, and Error Handling (Proposed Standard)
     Token: Gonzalo Camarillo
     IANA Review: IANA OK - No Actions Needed
     Consensus: Unknown

   o draft-ietf-stox-presence-07  - IETF stream
     Interworking between the Session Initiation Protocol (SIP) and the
     Extensible Messaging and Presence Protocol (XMPP): Presence
     (Proposed Standard)
     Token: Gonzalo Camarillo
     IANA Review: IANA OK - No Actions Needed
     Consensus: Unknown

2.1.2 Returning Items

   NONE

2.2 Individual Submissions
2.2.1 New Items

   NONE

2.2.2 Returning Items
     
   o draft-farrell-perpass-attack-05  - IETF stream
     Pervasive Monitoring is an Attack (Best Current Practice)
     Token: Jari Arkko
     IANA Review: IANA OK - No Actions Needed
     Consensus: Unknown
     Was deferred by Joel Jaeggli on 2014-01-23

2.3 Status Changes
2.3.1 New Items

   NONE

2.3.2 Returning Items

   NONE

2.3.3 For Action
     
   o status-change-5343-5590-5591-6353-to-internet-standard-01  - IETF stream
     Progressing RFCs 5343, 5590, 5591, and 6353 to Internet Standard
     (None)
     Token: Sean Turner

3. Document Actions
3.1 WG Submissions
3.1.1 New Items
     
   o draft-ietf-rtgwg-cl-requirement-15  - IETF stream
     Requirements for Advanced Multipath in MPLS Networks (Informational)
     Token: Stewart Bryant
     IANA Review: IANA OK - No Actions Needed
     Consensus: Yes

   o draft-ietf-insipid-session-id-reqts-09  - IETF stream
     Requirements for an End-to-End Session Identification in IP-Based
     Multimedia Communication Networks (Informational)
     Token: Gonzalo Camarillo
     IANA Review: IANA OK - No Actions Needed
     Consensus: Unknown

   o draft-ietf-clue-telepresence-requirements-07  - IETF stream
     Requirements for Telepresence Multi-Streams (Informational)
     Token: Gonzalo Camarillo
     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-crocker-id-adoption-05  - IETF stream
     Creating an IETF Working Group Draft (Informational)
     Token: Barry Leiba
     IANA Review: IANA OK - No Actions Needed
     Consensus: Unknown
     Last call expires: 2014-01-31

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

   NONE

3.4.2 Returning Items

   NONE

3.4.3 For Action

   o conflict-review-saintandre-jabberid-00
     IETF conflict review for draft-saintandre-jabberid
       draft-saintandre-jabberid-12
       The Jabber-ID Header Field (ISE: Informational)
     Token: Jari Arkko

   o conflict-review-irtf-dtnrg-tcp-clayer-00
     IETF conflict review for draft-irtf-dtnrg-tcp-clayer
       draft-irtf-dtnrg-tcp-clayer-08
       Delay Tolerant Networking TCP Convergence Layer Protocol (IRTF:
     Experimental)
     Token: Jari Arkko

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

   o TURN Revised and Modernized (tram)

4.1.2 Proposed for Approval

   o Public Notary Transparency  (trans)

4.2 WG Rechartering
4.2.1 Under Evaluation for IETF Review

   NONE

4.2.2 Proposed for Approval

   NONE





From bclaise@cisco.com  Sun Feb  2 05:58:19 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 9BE4B1A00D3 for <mib-doctors@ietfa.amsl.com>; Sun,  2 Feb 2014 05:58:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.035
X-Spam-Level: 
X-Spam-Status: No, score=-10.035 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.535, 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 lWgA-uNyO63j for <mib-doctors@ietfa.amsl.com>; Sun,  2 Feb 2014 05:58:16 -0800 (PST)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) by ietfa.amsl.com (Postfix) with ESMTP id CE6251A00D8 for <mib-doctors@ietf.org>; Sun,  2 Feb 2014 05:58:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=13671; q=dns/txt; s=iport; t=1391349492; x=1392559092; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to; bh=qoKsZ2re61KC9r8PmqjfMvVyA3yZU8i/vHLg1vZEn64=; b=j69Zdll6/QlQqcA7tGtdPWEUKpvkRZLTNALGIJlWAJuaOeh+I+2B+LBv RM2mtsliBIOX9OROOX06BQQLeSzD/QKzuCi3L5xn9oPwQWolT9lOyCiLk vMJWq7VUk/WAQiLGoiacoqtN6hY4/RwuBrzSn3LOPQGvmZhJHb3XNaCUs k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApEIAK9N7lKQ/khL/2dsb2JhbABYgww4iTWtYochgQEWdIIlAQEBBAEBAWsKAQwECxEEAQEBCRYIBwkDAgECARUfCQgGAQwBBQIBAQWHfA3MCBeOJxEBUAcGhDIEmCqGSItZgy47gTU
X-IronPort-AV: E=Sophos;i="4.95,766,1384300800"; d="scan'208,217";a="4545196"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by aer-iport-1.cisco.com with ESMTP; 02 Feb 2014 13:58:10 +0000
Received: from [10.60.67.88] (ams-bclaise-8917.cisco.com [10.60.67.88]) by ams-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id s12DwAx6003308; Sun, 2 Feb 2014 13:58:10 GMT
Message-ID: <52EE4EF1.3000102@cisco.com>
Date: Sun, 02 Feb 2014 14:58:09 +0100
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: adrian@olddog.co.uk, "'Bert Wijnen (IETF)'" <bertietf@bwijnen.net>, "'Thomas Nadeau'" <tnadeau@lucidvision.com>, "'Romascanu, Dan (Dan)'" <dromasca@avaya.com>
References: <52DD5FFC.8070103@cisco.com> <20140121094726.GB47210@elstar.local> <9904FB1B0159DA42B0B887B7FA8119CA243D33C0@AZ-FFEXMB04.global.avaya.com> <FE705A2D-F9F0-4A41-A992-36705527C24A@lucidvision.com> <9904FB1B0159DA42B0B887B7FA8119CA243D3C0F@AZ-FFEXMB04.global.avaya.com> <556BB556-669F-4EF5-B8B0-4F1CD7E45BD0@lucidvision.com> <52DE928D.1090909@bwijnen.net> <0b2301cf16ce$bad3a3e0$307aeba0$@olddog.co.uk> <52DF9D02.6070306@cisco.com>
In-Reply-To: <52DF9D02.6070306@cisco.com>
Content-Type: multipart/alternative; boundary="------------070006030707070404050403"
Cc: "'MIB Doctors \(E-mail\)'" <mib-doctors@ietf.org>
Subject: Re: [MIB-DOCTORS] Why is this MIB module read-write?
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: Sun, 02 Feb 2014 13:58:19 -0000

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

Mib doctors,

It's time to improve the following statement, to propose it to the OPS 
area, and if all goes well o make an IESG statement out of it.

    "The OPS Area henceforth strongly discourages the pursuit of
    writable SNMP MIBs for configuration purposes by working groups
    except in cases of clear utility and overwhelming consensus to do
    so. In all other cases, we recommend the use of NETCONF/YANG IETF
    standards for configuration, specifically in new charters."

I re-read the email thread, and want to make the following changes:
- Add IETF. It was mentioned that some other SDOs might still be using 
SNMP for configuration: IEEE, DOCSIS
- Add "for complete features or services" configuration. I want to 
address Chirs' point that SNMPSet for starting an action might be OK 
(router reload, start config download)

    "The OPS Area henceforth strongly discourages the pursuit of
    writable SNMP MIBs for complete features/services configuration
    purposes by IETF working groups, except in cases of clear utility
    and overwhelming consensus to do so. In all other cases, we
    recommend the use of NETCONF/YANG IETF standards for configuration,
    specifically in new charters."

Is this going in the right direction?
Is this good enough to discuss on the OPS area mailer?

Regards, Benoit
> Adrian, All,
>
> As expected and desired, this generated some good discussions (also in 
> a different email thread between the MIB doctors)
>
> So we went
> - from "SNMPSet is dead", as a comment to make people react
> - to "SNMPSet is dead?"
> - to "we do not require writable MIB modules"
> - A statement such as "The OPS Area henceforth strongly discourages 
> the pursuit of writable SNMP MIBs by working groups except in cases of 
> clear utility and overwhelming consensus to do so. In all other cases, 
> we recommend the use of tools such as Netconf/Netmod for configuration."
> - to "do not use writeable objects _for configuration_ in MIB modules"
>
> We could go with an IESG statement, but I propose to make it easy to 
> start with, with a statement on the MIB doctors page 
> (http://www.ietf.org/iesg/directorate/mib-doctors.html)
>
>     "The OPS Area henceforth strongly discourages the pursuit of
>     writable SNMP MIBs for configuration purposes by working groups
>     except in cases of clear utility and overwhelming consensus to do
>     so. In all other cases, we recommend the use of NETCONF/YANG IETF
>     standards for configuration, specifically in new charters."
>
> - I added "for configuration". SNMPSet could potentially be used for 
> action.
> - I removed "such as" in "tools such as Netconf/Netmod for 
> configuration." Not sure what you're referring to here Tom
> - I added "specifically in new charters." Right now, there are 
> read-write MIB modules in EMAN. It would not be a sound idea to say 
> now, specifically when documents went through LC: stop what you're 
> doing, recharter to do YANG modules. What's key in EMAN is that an 
> Information Model has been specified part of the framework.
>
> Feedback?
>
> Regards, Benoit
>
>> (speaking as not a MIB Doctor)
>>
>> I like that very much, thanks for the words Tom.
>>
>> Benoit, do you think this is a big enough issue that we should make it an IESG
>> statement?
>> Or do you just want to run it through the OPSAWG in some way?
>>
>> A
>>
>>> -----Original Message-----
>>> From: Bert Wijnen (IETF) [mailto:bertietf@bwijnen.net]
>>> Sent: 21 January 2014 15:30
>>> To: Thomas Nadeau; Romascanu, Dan (Dan)
>>> Cc: MIB Doctors (E-mail); Farrel Adrian
>>> Subject: Re: [MIB-DOCTORS] Why is this MIB module read-write?
>>>
>>> sounds good to me
>>>
>>> Bert
>>>
>>> On 21/01/14 16:14, Thomas Nadeau wrote:
>>>> 	Agreed. Something like, "The OPS Area henceforth strongly discourages
>>> the pursuit of writable SNMP MIBs by working groups except in cases of clear
>>> utility and overwhelming consensus to do so. In all other cases, we recommend
>>> the use of tools such as Netconf/Netmod for configuration."
>>>> 	--Tom
>>>>
>>>>
>>>>> Hi Tom,
>>>>>
>>>>> This is exactly my point. I think that we should not only say 'do not do
>> Sets
>>> using SNMP'. We should also say what to do instead.
>>>>> Regards,
>>>>>
>>>>> Dan
>>>>>
>>>>>
>>>>>> -----Original Message-----
>>>>>> From: Thomas Nadeau [mailto:tnadeau@lucidvision.com]
>>>>> ....
>>>>>
>>>>>> 	I do agree that guidance needs to be issues to developers and
>>>>>> especially IETF WGs on this matter.
>>>>>>
>>>>>> 	--Tom
>>>>>>
>>>>
>>>> _______________________________________________
>>>> 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
>> .
>>
>
>
>
> _______________________________________________
> MIB-DOCTORS mailing list
> MIB-DOCTORS@ietf.org
> https://www.ietf.org/mailman/listinfo/mib-doctors


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

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">Mib doctors,<br>
      <br>
      It's time to improve the following statement, to propose it to the
      OPS area, and if all goes well o make an IESG statement out of it.<br>
      <blockquote>"The OPS Area henceforth strongly discourages the
        pursuit of writable SNMP MIBs for configuration purposes by
        working groups except in cases of clear utility and overwhelming
        consensus to do so. In all other cases, we recommend the use of
        NETCONF/YANG IETF standards for configuration, specifically in
        new charters."<br>
      </blockquote>
      I re-read the email thread, and want to make the following
      changes:<br>
      - Add IETF. It was mentioned that some other SDOs might still be
      using SNMP for configuration: IEEE, DOCSIS<br>
      - Add "for complete features or services" configuration. I want to
      address Chirs' point that SNMPSet for starting an action might be
      OK (router reload, start config download)<br>
      <br>
      <blockquote>"The OPS Area henceforth strongly discourages the
        pursuit of writable SNMP MIBs for complete features/services
        configuration purposes by IETF working groups, except in cases
        of clear utility and overwhelming consensus to do so. In all
        other cases, we recommend the use of NETCONF/YANG IETF standards
        for configuration, specifically in new charters."<br>
      </blockquote>
      Is this going in the right direction?<br>
      Is this good enough to discuss on the OPS area mailer?<br>
      <br>
      Regards, Benoit<br>
    </div>
    <blockquote cite="mid:52DF9D02.6070306@cisco.com" type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=ISO-8859-1">
      <div class="moz-cite-prefix">Adrian, All,<br>
        <br>
        As expected and desired, this generated some good discussions
        (also in a different email thread between the MIB doctors)<br>
        <br>
        So we went <br>
        - from "SNMPSet is dead", as a comment to make people react<br>
        - to "SNMPSet is dead?" <br>
        - to "we do not require writable MIB modules"<br>
        - A statement such as "The OPS Area henceforth strongly
        discourages the pursuit of writable SNMP MIBs by working groups
        except in cases of clear utility and overwhelming consensus to
        do so. In all other cases, we recommend the use of tools such as
        Netconf/Netmod for configuration."<br>
        - to "do not use writeable objects <u>for configuration</u> in
        MIB modules"<br>
        <br>
        We could go with an IESG statement, but I propose to make it
        easy to start with, with a statement on the MIB doctors page (<a
          moz-do-not-send="true" class="moz-txt-link-freetext"
          href="http://www.ietf.org/iesg/directorate/mib-doctors.html">http://www.ietf.org/iesg/directorate/mib-doctors.html</a>)<br>
        <blockquote>"The OPS Area henceforth strongly discourages the
          pursuit of writable SNMP MIBs for configuration purposes by
          working groups except in cases of clear utility and
          overwhelming consensus to do so. In all other cases, we
          recommend the use of NETCONF/YANG IETF standards for
          configuration, specifically in new charters."<br>
        </blockquote>
        - I added "for configuration". SNMPSet could potentially be used
        for action.<br>
        - I removed "such as" in "tools such as Netconf/Netmod for
        configuration." Not sure what you're referring to here Tom<br>
        - I added "specifically in new charters." Right now, there are
        read-write MIB modules in EMAN. It would not be a sound idea to
        say now, specifically when documents went through LC: stop what
        you're doing, recharter to do YANG modules. What's key in EMAN
        is that an Information Model has been specified part of the
        framework.<br>
        <br>
        Feedback?<br>
        <br>
        Regards, Benoit<br>
        <br>
      </div>
      <blockquote
        cite="mid:0b2301cf16ce$bad3a3e0$307aeba0$@olddog.co.uk"
        type="cite">
        <pre wrap="">(speaking as not a MIB Doctor)

I like that very much, thanks for the words Tom.

Benoit, do you think this is a big enough issue that we should make it an IESG
statement?
Or do you just want to run it through the OPSAWG in some way?

A

</pre>
        <blockquote type="cite">
          <pre wrap="">-----Original Message-----
From: Bert Wijnen (IETF) [<a moz-do-not-send="true" class="moz-txt-link-freetext" href="mailto:bertietf@bwijnen.net">mailto:bertietf@bwijnen.net</a>]
Sent: 21 January 2014 15:30
To: Thomas Nadeau; Romascanu, Dan (Dan)
Cc: MIB Doctors (E-mail); Farrel Adrian
Subject: Re: [MIB-DOCTORS] Why is this MIB module read-write?

sounds good to me

Bert

On 21/01/14 16:14, Thomas Nadeau wrote:
</pre>
          <blockquote type="cite">
            <pre wrap="">	Agreed. Something like, "The OPS Area henceforth strongly discourages
</pre>
          </blockquote>
          <pre wrap="">the pursuit of writable SNMP MIBs by working groups except in cases of clear
utility and overwhelming consensus to do so. In all other cases, we recommend
the use of tools such as Netconf/Netmod for configuration."
</pre>
          <blockquote type="cite">
            <pre wrap="">	--Tom


</pre>
            <blockquote type="cite">
              <pre wrap="">Hi Tom,

This is exactly my point. I think that we should not only say 'do not do
</pre>
            </blockquote>
          </blockquote>
        </blockquote>
        <pre wrap="">Sets
</pre>
        <blockquote type="cite">
          <pre wrap="">using SNMP'. We should also say what to do instead.
</pre>
          <blockquote type="cite">
            <blockquote type="cite">
              <pre wrap="">Regards,

Dan


</pre>
              <blockquote type="cite">
                <pre wrap="">-----Original Message-----
From: Thomas Nadeau [<a moz-do-not-send="true" class="moz-txt-link-freetext" href="mailto:tnadeau@lucidvision.com">mailto:tnadeau@lucidvision.com</a>]
</pre>
              </blockquote>
              <pre wrap="">....

</pre>
              <blockquote type="cite">
                <pre wrap="">	I do agree that guidance needs to be issues to developers and
especially IETF WGs on this matter.

	--Tom

</pre>
              </blockquote>
              <pre wrap="">
</pre>
            </blockquote>
            <pre wrap="">

_______________________________________________
MIB-DOCTORS mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:MIB-DOCTORS@ietf.org">MIB-DOCTORS@ietf.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/mib-doctors">https://www.ietf.org/mailman/listinfo/mib-doctors</a>

</pre>
          </blockquote>
        </blockquote>
        <pre wrap="">_______________________________________________
MIB-DOCTORS mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:MIB-DOCTORS@ietf.org">MIB-DOCTORS@ietf.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/mib-doctors">https://www.ietf.org/mailman/listinfo/mib-doctors</a>
.

</pre>
      </blockquote>
      <br>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
MIB-DOCTORS mailing list
<a class="moz-txt-link-abbreviated" href="mailto:MIB-DOCTORS@ietf.org">MIB-DOCTORS@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/mib-doctors">https://www.ietf.org/mailman/listinfo/mib-doctors</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------070006030707070404050403--

From bclaise@cisco.com  Sun Feb  2 06:16:14 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 D984C1A00D9 for <mib-doctors@ietfa.amsl.com>; Sun,  2 Feb 2014 06:16:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.035
X-Spam-Level: 
X-Spam-Status: No, score=-10.035 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.535, 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 8iFJRBSi9cQW for <mib-doctors@ietfa.amsl.com>; Sun,  2 Feb 2014 06:16:11 -0800 (PST)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) by ietfa.amsl.com (Postfix) with ESMTP id D59F01A00D3 for <mib-doctors@ietf.org>; Sun,  2 Feb 2014 06:16:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=16556; q=dns/txt; s=iport; t=1391350567; x=1392560167; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to; bh=4vEKX95cRJ4EkIioxWczClH3LixQsaYJVGW8Wk7K2kE=; b=ApxxScIOuVduZYZoyhlaviu28lf/EpXWw1ytusVyrBPTkxrl/cAtdgoM jsFFSxxvIRMWtq8fluYXrdI+8iCJxThiQktitgoLd0Aoh92x9nbrGfeK4 aaUgXKkmLz/LvaGrbOQR4y8QWQhrf6xJjDIA53DjbTI4Irh0TbdDzZ0T1 o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ArcIAN1S7lKQ/khL/2dsb2JhbABYgkhEOIk1rWKHIYEBFnSCJQEBAQQBAQFrCgEMBAsRBAEBAQkWCAcJAwIBAgEVHwkIBgEMAQUCAQEFh3wNy3kXjicRAVAHBoQyBJgqhkiLWYMuO4E1
X-IronPort-AV: E=Sophos;i="4.95,766,1384300800"; d="scan'208,217";a="3878558"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by aer-iport-2.cisco.com with ESMTP; 02 Feb 2014 14:16:05 +0000
Received: from [10.60.67.88] (ams-bclaise-8917.cisco.com [10.60.67.88]) by ams-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id s12EG4wR007853; Sun, 2 Feb 2014 14:16:05 GMT
Message-ID: <52EE5324.8010602@cisco.com>
Date: Sun, 02 Feb 2014 15:16:04 +0100
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: adrian@olddog.co.uk, "'Bert Wijnen (IETF)'" <bertietf@bwijnen.net>, "'Thomas Nadeau'" <tnadeau@lucidvision.com>, "'Romascanu, Dan (Dan)'" <dromasca@avaya.com>
References: <52DD5FFC.8070103@cisco.com> <20140121094726.GB47210@elstar.local> <9904FB1B0159DA42B0B887B7FA8119CA243D33C0@AZ-FFEXMB04.global.avaya.com> <FE705A2D-F9F0-4A41-A992-36705527C24A@lucidvision.com> <9904FB1B0159DA42B0B887B7FA8119CA243D3C0F@AZ-FFEXMB04.global.avaya.com> <556BB556-669F-4EF5-B8B0-4F1CD7E45BD0@lucidvision.com> <52DE928D.1090909@bwijnen.net> <0b2301cf16ce$bad3a3e0$307aeba0$@olddog.co.uk> <52DF9D02.6070306@cisco.com> <52EE4EF1.3000102@cisco.com>
In-Reply-To: <52EE4EF1.3000102@cisco.com>
Content-Type: multipart/alternative; boundary="------------020802060006010105060100"
Cc: "'MIB Doctors \(E-mail\)'" <mib-doctors@ietf.org>
Subject: Re: [MIB-DOCTORS] Why is this MIB module read-write?
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: Sun, 02 Feb 2014 14:16:15 -0000

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

MIB doctors,

I forgot to include Dan's feedback.
See inline.
> Mib doctors,
>
> It's time to improve the following statement, to propose it to the OPS 
> area, and if all goes well o make an IESG statement out of it.
>
>     "The OPS Area henceforth strongly discourages the pursuit of
>     writable SNMP MIBs for configuration purposes by working groups
>     except in cases of clear utility and overwhelming consensus to do
>     so. In all other cases, we recommend the use of NETCONF/YANG IETF
>     standards for configuration, specifically in new charters."
>
> I re-read the email thread, and want to make the following changes:
> - Add IETF. It was mentioned that some other SDOs might still be using 
> SNMP for configuration: IEEE, DOCSIS
> - Add "for complete features or services" configuration. I want to 
> address Chirs' point that SNMPSet for starting an action might be OK 
> (router reload, start config download)
>
>     "The OPS Area henceforth strongly discourages the pursuit of
>     writable SNMP MIBs for complete features/services configuration
>     purposes by IETF working groups, except in cases of clear utility
>     and overwhelming consensus to do so. In all other cases, we
>     recommend the use of NETCONF/YANG IETF standards for
>     configuration, specifically in new charters."
>
    "The OPS Area henceforth strongly discourages the pursuit of
    writable SNMP MIB modules for complete features/services
    configuration purposes by IETF working groups, except in cases of
    clear utility and consensus to do so. Using SNMPSet to simple
    configuration, such as enable/disable notifications or initiating an
    action,  might be appropriate though.  In all other cases, we
    recommend the use of NETCONF/YANG IETF standards for configuration,
    specifically in new charters."

Regards, Benoit
>
> Is this going in the right direction?
> Is this good enough to discuss on the OPS area mailer?
>
> Regards, Benoit
>> Adrian, All,
>>
>> As expected and desired, this generated some good discussions (also 
>> in a different email thread between the MIB doctors)
>>
>> So we went
>> - from "SNMPSet is dead", as a comment to make people react
>> - to "SNMPSet is dead?"
>> - to "we do not require writable MIB modules"
>> - A statement such as "The OPS Area henceforth strongly discourages 
>> the pursuit of writable SNMP MIBs by working groups except in cases 
>> of clear utility and overwhelming consensus to do so. In all other 
>> cases, we recommend the use of tools such as Netconf/Netmod for 
>> configuration."
>> - to "do not use writeable objects _for configuration_ in MIB modules"
>>
>> We could go with an IESG statement, but I propose to make it easy to 
>> start with, with a statement on the MIB doctors page 
>> (http://www.ietf.org/iesg/directorate/mib-doctors.html)
>>
>>     "The OPS Area henceforth strongly discourages the pursuit of
>>     writable SNMP MIBs for configuration purposes by working groups
>>     except in cases of clear utility and overwhelming consensus to do
>>     so. In all other cases, we recommend the use of NETCONF/YANG IETF
>>     standards for configuration, specifically in new charters."
>>
>> - I added "for configuration". SNMPSet could potentially be used for 
>> action.
>> - I removed "such as" in "tools such as Netconf/Netmod for 
>> configuration." Not sure what you're referring to here Tom
>> - I added "specifically in new charters." Right now, there are 
>> read-write MIB modules in EMAN. It would not be a sound idea to say 
>> now, specifically when documents went through LC: stop what you're 
>> doing, recharter to do YANG modules. What's key in EMAN is that an 
>> Information Model has been specified part of the framework.
>>
>> Feedback?
>>
>> Regards, Benoit
>>
>>> (speaking as not a MIB Doctor)
>>>
>>> I like that very much, thanks for the words Tom.
>>>
>>> Benoit, do you think this is a big enough issue that we should make it an IESG
>>> statement?
>>> Or do you just want to run it through the OPSAWG in some way?
>>>
>>> A
>>>
>>>> -----Original Message-----
>>>> From: Bert Wijnen (IETF) [mailto:bertietf@bwijnen.net]
>>>> Sent: 21 January 2014 15:30
>>>> To: Thomas Nadeau; Romascanu, Dan (Dan)
>>>> Cc: MIB Doctors (E-mail); Farrel Adrian
>>>> Subject: Re: [MIB-DOCTORS] Why is this MIB module read-write?
>>>>
>>>> sounds good to me
>>>>
>>>> Bert
>>>>
>>>> On 21/01/14 16:14, Thomas Nadeau wrote:
>>>>> 	Agreed. Something like, "The OPS Area henceforth strongly discourages
>>>> the pursuit of writable SNMP MIBs by working groups except in cases of clear
>>>> utility and overwhelming consensus to do so. In all other cases, we recommend
>>>> the use of tools such as Netconf/Netmod for configuration."
>>>>> 	--Tom
>>>>>
>>>>>
>>>>>> Hi Tom,
>>>>>>
>>>>>> This is exactly my point. I think that we should not only say 'do not do
>>> Sets
>>>> using SNMP'. We should also say what to do instead.
>>>>>> Regards,
>>>>>>
>>>>>> Dan
>>>>>>
>>>>>>
>>>>>>> -----Original Message-----
>>>>>>> From: Thomas Nadeau [mailto:tnadeau@lucidvision.com]
>>>>>> ....
>>>>>>
>>>>>>> 	I do agree that guidance needs to be issues to developers and
>>>>>>> especially IETF WGs on this matter.
>>>>>>>
>>>>>>> 	--Tom
>>>>>>>
>>>>> _______________________________________________
>>>>> 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
>>> .
>>>
>>
>>
>>
>> _______________________________________________
>> 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


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

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">MIB doctors,<br>
      <br>
      I forgot to include Dan's feedback.<br>
      See inline.<br>
    </div>
    <blockquote cite="mid:52EE4EF1.3000102@cisco.com" type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=ISO-8859-1">
      <div class="moz-cite-prefix">Mib doctors,<br>
        <br>
        It's time to improve the following statement, to propose it to
        the OPS area, and if all goes well o make an IESG statement out
        of it.<br>
        <blockquote>"The OPS Area henceforth strongly discourages the
          pursuit of writable SNMP MIBs for configuration purposes by
          working groups except in cases of clear utility and
          overwhelming consensus to do so. In all other cases, we
          recommend the use of NETCONF/YANG IETF standards for
          configuration, specifically in new charters."<br>
        </blockquote>
        I re-read the email thread, and want to make the following
        changes:<br>
        - Add IETF. It was mentioned that some other SDOs might still be
        using SNMP for configuration: IEEE, DOCSIS<br>
        - Add "for complete features or services" configuration. I want
        to address Chirs' point that SNMPSet for starting an action
        might be OK (router reload, start config download)<br>
        <br>
        <blockquote>"The OPS Area henceforth strongly discourages the
          pursuit of writable SNMP MIBs for complete features/services
          configuration purposes by IETF working groups, except in cases
          of clear utility and overwhelming consensus to do so. In all
          other cases, we recommend the use of NETCONF/YANG IETF
          standards for configuration, specifically in new charters."<br>
        </blockquote>
      </div>
    </blockquote>
    <blockquote>"The OPS Area henceforth strongly discourages the
      pursuit of writable SNMP MIB modules for complete
      features/services configuration purposes by IETF working groups,
      except in cases of clear utility and consensus to do so. Using
      SNMPSet to simple configuration, such as enable/disable
      notifications or initiating an action,&nbsp; might be appropriate
      though.&nbsp; In all other cases, we recommend the use of NETCONF/YANG
      IETF standards for configuration, specifically in new charters."<br>
    </blockquote>
    Regards, Benoit<br>
    <span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><span
        style="mso-list:Ignore"><span style="font:7.0pt &quot;Times New
          Roman&quot;">
        </span></span></span><span dir="LTR"></span>
    <blockquote cite="mid:52EE4EF1.3000102@cisco.com" type="cite">
      <div class="moz-cite-prefix">
        <blockquote> </blockquote>
        Is this going in the right direction?<br>
        Is this good enough to discuss on the OPS area mailer?<br>
        <br>
        Regards, Benoit<br>
      </div>
      <blockquote cite="mid:52DF9D02.6070306@cisco.com" type="cite">
        <div class="moz-cite-prefix">Adrian, All,<br>
          <br>
          As expected and desired, this generated some good discussions
          (also in a different email thread between the MIB doctors)<br>
          <br>
          So we went <br>
          - from "SNMPSet is dead", as a comment to make people react<br>
          - to "SNMPSet is dead?" <br>
          - to "we do not require writable MIB modules"<br>
          - A statement such as "The OPS Area henceforth strongly
          discourages the pursuit of writable SNMP MIBs by working
          groups except in cases of clear utility and overwhelming
          consensus to do so. In all other cases, we recommend the use
          of tools such as Netconf/Netmod for configuration."<br>
          - to "do not use writeable objects <u>for configuration</u>
          in MIB modules"<br>
          <br>
          We could go with an IESG statement, but I propose to make it
          easy to start with, with a statement on the MIB doctors page (<a
            moz-do-not-send="true" class="moz-txt-link-freetext"
            href="http://www.ietf.org/iesg/directorate/mib-doctors.html">http://www.ietf.org/iesg/directorate/mib-doctors.html</a>)<br>
          <blockquote>"The OPS Area henceforth strongly discourages the
            pursuit of writable SNMP MIBs for configuration purposes by
            working groups except in cases of clear utility and
            overwhelming consensus to do so. In all other cases, we
            recommend the use of NETCONF/YANG IETF standards for
            configuration, specifically in new charters."<br>
          </blockquote>
          - I added "for configuration". SNMPSet could potentially be
          used for action.<br>
          - I removed "such as" in "tools such as Netconf/Netmod for
          configuration." Not sure what you're referring to here Tom<br>
          - I added "specifically in new charters." Right now, there are
          read-write MIB modules in EMAN. It would not be a sound idea
          to say now, specifically when documents went through LC: stop
          what you're doing, recharter to do YANG modules. What's key in
          EMAN is that an Information Model has been specified part of
          the framework.<br>
          <br>
          Feedback?<br>
          <br>
          Regards, Benoit<br>
          <br>
        </div>
        <blockquote
          cite="mid:0b2301cf16ce$bad3a3e0$307aeba0$@olddog.co.uk"
          type="cite">
          <pre wrap="">(speaking as not a MIB Doctor)

I like that very much, thanks for the words Tom.

Benoit, do you think this is a big enough issue that we should make it an IESG
statement?
Or do you just want to run it through the OPSAWG in some way?

A

</pre>
          <blockquote type="cite">
            <pre wrap="">-----Original Message-----
From: Bert Wijnen (IETF) [<a moz-do-not-send="true" class="moz-txt-link-freetext" href="mailto:bertietf@bwijnen.net">mailto:bertietf@bwijnen.net</a>]
Sent: 21 January 2014 15:30
To: Thomas Nadeau; Romascanu, Dan (Dan)
Cc: MIB Doctors (E-mail); Farrel Adrian
Subject: Re: [MIB-DOCTORS] Why is this MIB module read-write?

sounds good to me

Bert

On 21/01/14 16:14, Thomas Nadeau wrote:
</pre>
            <blockquote type="cite">
              <pre wrap="">	Agreed. Something like, "The OPS Area henceforth strongly discourages
</pre>
            </blockquote>
            <pre wrap="">the pursuit of writable SNMP MIBs by working groups except in cases of clear
utility and overwhelming consensus to do so. In all other cases, we recommend
the use of tools such as Netconf/Netmod for configuration."
</pre>
            <blockquote type="cite">
              <pre wrap="">	--Tom


</pre>
              <blockquote type="cite">
                <pre wrap="">Hi Tom,

This is exactly my point. I think that we should not only say 'do not do
</pre>
              </blockquote>
            </blockquote>
          </blockquote>
          <pre wrap="">Sets
</pre>
          <blockquote type="cite">
            <pre wrap="">using SNMP'. We should also say what to do instead.
</pre>
            <blockquote type="cite">
              <blockquote type="cite">
                <pre wrap="">Regards,

Dan


</pre>
                <blockquote type="cite">
                  <pre wrap="">-----Original Message-----
From: Thomas Nadeau [<a moz-do-not-send="true" class="moz-txt-link-freetext" href="mailto:tnadeau@lucidvision.com">mailto:tnadeau@lucidvision.com</a>]
</pre>
                </blockquote>
                <pre wrap="">....

</pre>
                <blockquote type="cite">
                  <pre wrap="">	I do agree that guidance needs to be issues to developers and
especially IETF WGs on this matter.

	--Tom

</pre>
                </blockquote>
              </blockquote>
              <pre wrap="">
_______________________________________________
MIB-DOCTORS mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:MIB-DOCTORS@ietf.org">MIB-DOCTORS@ietf.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/mib-doctors">https://www.ietf.org/mailman/listinfo/mib-doctors</a>

</pre>
            </blockquote>
          </blockquote>
          <pre wrap="">_______________________________________________
MIB-DOCTORS mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:MIB-DOCTORS@ietf.org">MIB-DOCTORS@ietf.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/mib-doctors">https://www.ietf.org/mailman/listinfo/mib-doctors</a>
.

</pre>
        </blockquote>
        <br>
        <br>
        <fieldset class="mimeAttachmentHeader"></fieldset>
        <br>
        <pre wrap="">_______________________________________________
MIB-DOCTORS mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:MIB-DOCTORS@ietf.org">MIB-DOCTORS@ietf.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/mib-doctors">https://www.ietf.org/mailman/listinfo/mib-doctors</a>
</pre>
      </blockquote>
      <br>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
MIB-DOCTORS mailing list
<a class="moz-txt-link-abbreviated" href="mailto:MIB-DOCTORS@ietf.org">MIB-DOCTORS@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/mib-doctors">https://www.ietf.org/mailman/listinfo/mib-doctors</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------020802060006010105060100--

From j.schoenwaelder@jacobs-university.de  Sun Feb  2 06:45:10 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 41D091A00E5 for <mib-doctors@ietfa.amsl.com>; Sun,  2 Feb 2014 06:45:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.785
X-Spam-Level: 
X-Spam-Status: No, score=-2.785 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.535] 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 r-4jvHqUYayH for <mib-doctors@ietfa.amsl.com>; Sun,  2 Feb 2014 06:45:08 -0800 (PST)
Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) by ietfa.amsl.com (Postfix) with ESMTP id 6ECB91A00E3 for <mib-doctors@ietf.org>; Sun,  2 Feb 2014 06:45:08 -0800 (PST)
Received: from localhost (demetrius1.jacobs-university.de [212.201.44.46]) by hermes.jacobs-university.de (Postfix) with ESMTP id D2CB120050; Sun,  2 Feb 2014 15:45:03 +0100 (CET)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius1.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id bjMykU0Q74jA; Sun,  2 Feb 2014 15:45:03 +0100 (CET)
Received: from elstar.local (elstar.jacobs.jacobs-university.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id A308F2004C; Sun,  2 Feb 2014 15:45:02 +0100 (CET)
Received: by elstar.local (Postfix, from userid 501) id EBD0B2B08B86; Sun,  2 Feb 2014 15:44:59 +0100 (CET)
Date: Sun, 2 Feb 2014 15:44:59 +0100
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: Benoit Claise <bclaise@cisco.com>
Message-ID: <20140202144457.GA35917@elstar.local>
Mail-Followup-To: Benoit Claise <bclaise@cisco.com>, adrian@olddog.co.uk, "'Bert Wijnen (IETF)'" <bertietf@bwijnen.net>, 'Thomas Nadeau' <tnadeau@lucidvision.com>, "'Romascanu, Dan (Dan)'" <dromasca@avaya.com>, "'MIB Doctors (E-mail)'" <mib-doctors@ietf.org>
References: <52DD5FFC.8070103@cisco.com> <20140121094726.GB47210@elstar.local> <9904FB1B0159DA42B0B887B7FA8119CA243D33C0@AZ-FFEXMB04.global.avaya.com> <FE705A2D-F9F0-4A41-A992-36705527C24A@lucidvision.com> <9904FB1B0159DA42B0B887B7FA8119CA243D3C0F@AZ-FFEXMB04.global.avaya.com> <556BB556-669F-4EF5-B8B0-4F1CD7E45BD0@lucidvision.com> <52DE928D.1090909@bwijnen.net> <0b2301cf16ce$bad3a3e0$307aeba0$@olddog.co.uk> <52DF9D02.6070306@cisco.com> <52EE4EF1.3000102@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <52EE4EF1.3000102@cisco.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: adrian@olddog.co.uk, "'MIB Doctors \(E-mail\)'" <mib-doctors@ietf.org>
Subject: Re: [MIB-DOCTORS] Why is this MIB module read-write?
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: Sun, 02 Feb 2014 14:45:10 -0000

On Sun, Feb 02, 2014 at 02:58:09PM +0100, Benoit Claise wrote:
> Mib doctors,
> 
> It's time to improve the following statement, to propose it to the
> OPS area, and if all goes well o make an IESG statement out of it.
> 
>    "The OPS Area henceforth strongly discourages the pursuit of
>    writable SNMP MIBs for configuration purposes by working groups
>    except in cases of clear utility and overwhelming consensus to do
>    so. In all other cases, we recommend the use of NETCONF/YANG IETF
>    standards for configuration, specifically in new charters."
> 
> I re-read the email thread, and want to make the following changes:
> - Add IETF. It was mentioned that some other SDOs might still be
> using SNMP for configuration: IEEE, DOCSIS
> - Add "for complete features or services" configuration. I want to
> address Chirs' point that SNMPSet for starting an action might be OK
> (router reload, start config download)

Since what Chirs is talking about s not configuration, I think the
original text was already OK. I am not sure people will easily
understand what 'complete features/services configuration' means.  I
also do not know what the difference between 'discourage' and
'strictly discourage' is.

/js

PS: Strictly speaking from an SMIv2 standpoint, I am not sure how to
    use the MAX-ACCESS clause anymore. ;-}

     The MAX-ACCESS clause, which must be present, defines whether it
     makes "protocol sense" to read, write and/or create an instance of
     the object, or to include its value in a notification.  This is the
     maximal level of access for the object.  (This maximal level of
     access is independent of any administrative authorization policy.)

-- 
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 tnadeau@lucidvision.com  Mon Feb  3 10:31:22 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 D0F541A0162 for <mib-doctors@ietfa.amsl.com>; Mon,  3 Feb 2014 10:31:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.035
X-Spam-Level: 
X-Spam-Status: No, score=-1.035 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, RP_MATCHES_RCVD=-0.535] 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 GdyN2lyezj5P for <mib-doctors@ietfa.amsl.com>; Mon,  3 Feb 2014 10:31:21 -0800 (PST)
Received: from lucidvision.com (lucidvision.com [72.71.250.34]) by ietfa.amsl.com (Postfix) with ESMTP id 0A3CC1A010F for <mib-doctors@ietf.org>; Mon,  3 Feb 2014 10:31:20 -0800 (PST)
Received: from eng-dhcp-170.vyatta.com (unknown [144.49.164.10]) by lucidvision.com (Postfix) with ESMTP id 21A4826D9FFF; Mon,  3 Feb 2014 13:31:18 -0500 (EST)
Content-Type: multipart/signed; boundary="Apple-Mail=_6F81221B-3868-4D8B-8A06-C11FBE0F70CC"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Thomas Nadeau <tnadeau@lucidvision.com>
In-Reply-To: <20140202144457.GA35917@elstar.local>
Date: Mon, 3 Feb 2014 10:31:14 -0800
Message-Id: <71294B36-30B9-4929-903D-C76936CE2B57@lucidvision.com>
References: <52DD5FFC.8070103@cisco.com> <20140121094726.GB47210@elstar.local> <9904FB1B0159DA42B0B887B7FA8119CA243D33C0@AZ-FFEXMB04.global.avaya.com> <FE705A2D-F9F0-4A41-A992-36705527C24A@lucidvision.com> <9904FB1B0159DA42B0B887B7FA8119CA243D3C0F@AZ-FFEXMB04.global.avaya.com> <556BB556-669F-4EF5-B8B0-4F1CD7E45BD0@lucidvision.com> <52DE928D.1090909@bwijnen.net> <0b2301cf16ce$bad3a3e0$307aeba0$@olddog.co.uk> <52DF9D02.6070306@cisco.com> <52EE4EF1.3000102@cisco.com> <20140202144457.GA35917@elstar.local>
To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
X-Mailer: Apple Mail (2.1827)
Cc: Farrel Adrian <adrian@olddog.co.uk>, "MIB Doctors \(E-mail\)" <mib-doctors@ietf.org>
Subject: Re: [MIB-DOCTORS] Why is this MIB module read-write?
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, 03 Feb 2014 18:31:22 -0000

--Apple-Mail=_6F81221B-3868-4D8B-8A06-C11FBE0F70CC
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


	Juergen,

	I like the use of the adverb; it shows we mean business. *)

	--Tom


On Feb 2, 2014:6:44 AM, at 6:44 AM, Juergen Schoenwaelder =
<j.schoenwaelder@jacobs-university.de> wrote:

> On Sun, Feb 02, 2014 at 02:58:09PM +0100, Benoit Claise wrote:
>> Mib doctors,
>>=20
>> It's time to improve the following statement, to propose it to the
>> OPS area, and if all goes well o make an IESG statement out of it.
>>=20
>>   "The OPS Area henceforth strongly discourages the pursuit of
>>   writable SNMP MIBs for configuration purposes by working groups
>>   except in cases of clear utility and overwhelming consensus to do
>>   so. In all other cases, we recommend the use of NETCONF/YANG IETF
>>   standards for configuration, specifically in new charters."
>>=20
>> I re-read the email thread, and want to make the following changes:
>> - Add IETF. It was mentioned that some other SDOs might still be
>> using SNMP for configuration: IEEE, DOCSIS
>> - Add "for complete features or services" configuration. I want to
>> address Chirs' point that SNMPSet for starting an action might be OK
>> (router reload, start config download)
>=20
> Since what Chirs is talking about s not configuration, I think the
> original text was already OK. I am not sure people will easily
> understand what 'complete features/services configuration' means.  I
> also do not know what the difference between 'discourage' and
> 'strictly discourage' is.
>=20
> /js
>=20
> PS: Strictly speaking from an SMIv2 standpoint, I am not sure how to
>    use the MAX-ACCESS clause anymore. ;-}
>=20
>     The MAX-ACCESS clause, which must be present, defines whether it
>     makes "protocol sense" to read, write and/or create an instance of
>     the object, or to include its value in a notification.  This is =
the
>     maximal level of access for the object.  (This maximal level of
>     access is independent of any administrative authorization policy.)
>=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=_6F81221B-3868-4D8B-8A06-C11FBE0F70CC
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

iQIcBAEBCgAGBQJS7+ByAAoJEPcO+I7eiUJZQKQP/32VRaX4IUHebfz1p21qXneV
hxpG8vsHazOxJOqFy2Bj2vEcAa74kqjslsQR2CXp7dUe+e2OY09Jd5DTJ4n9C6Td
5UYg5sfpcFXzkxNcgDnvExyBzJB6T63GpGRLjSkwfFujXn/sx1BJsCrSB5x2VDQ2
becQrPpVzO56Pqd92HpSzMzcTqPRdfwM/XhsFDmvKAv+9XUxA1LE++RUktH8VLms
Bl8FCMaPpBhcX/Qm8Qf0ytfykuYQLavCnvx7YpLFk+iHLkHUAX7nqg06/QaetOe8
vaLe6KjiDx/rrPAlcGqT1ay0XTMvrklMV1gqfAkUWoGzpR54KyXyz2cXBN6w48q+
uRgQic8BTlCMKr6Ph0hJVLxxbVG5KlHQsUWvEvmy8yoPbwa45uWiLu+YNpiWryaz
nvGU31CejmNO9CvDAXnihtUbfNEMIO/XliANcFw2pTP1tw4LNoLMouts19CZ1Uy9
yJiOFBK2PNA0cJ4AH+6aLKGQSIP6nUu58Tn5vreW0ct7tGJt1RyhCQYsGPw+0CIY
nv5cg3K6mfXe9TiYx5t8l3aUL3CkQE7zaentuzSBQjgX29O28EqxIOucs0X7rB/R
mbYMRYXV9qv+Ub7/SjLiWvFc2ZW342ertqPhf7R84GB+9gEKktD9r1NdztM8eJFp
GZXf2JLlrmkales+lJkb
=56/k
-----END PGP SIGNATURE-----

--Apple-Mail=_6F81221B-3868-4D8B-8A06-C11FBE0F70CC--

From randy_presuhn@mindspring.com  Mon Feb  3 13:01:38 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 B41001A022F for <mib-doctors@ietfa.amsl.com>; Mon,  3 Feb 2014 13:01:38 -0800 (PST)
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 PBFVyHeD5MPo for <mib-doctors@ietfa.amsl.com>; Mon,  3 Feb 2014 13:01:37 -0800 (PST)
Received: from elasmtp-spurfowl.atl.sa.earthlink.net (elasmtp-spurfowl.atl.sa.earthlink.net [209.86.89.66]) by ietfa.amsl.com (Postfix) with ESMTP id 3C1831A012E for <mib-doctors@ietf.org>; Mon,  3 Feb 2014 13:01:36 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=XMelGk6yDoxIXGw8OHeJIGEVG8QYNhS25C758ROjDje9usy0HmGNbmt7kCHrLrJu; h=Message-ID:Date:From:Reply-To:To:Subject:Mime-Version:Content-Type:Content-Transfer-Encoding:X-Mailer:X-ELNK-Trace:X-Originating-IP;
Received: from [209.86.224.39] (helo=elwamui-little.atl.sa.earthlink.net) by elasmtp-spurfowl.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <randy_presuhn@mindspring.com>) id 1WAQe8-0006ar-8X for mib-doctors@ietf.org; Mon, 03 Feb 2014 16:01:36 -0500
Received: from 99.23.161.180 by webmail.earthlink.net with HTTP; Mon, 3 Feb 2014 16:01:35 -0500
Message-ID: <26928351.1391461296232.JavaMail.root@elwamui-little.atl.sa.earthlink.net>
Date: Mon, 3 Feb 2014 13:01:35 -0800 (GMT-08:00)
From: Randy Presuhn <randy_presuhn@mindspring.com>
To: 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: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d88891b749bef7332bbc33a48aa92626cd766e72ec0ebe058768350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 209.86.224.39
Subject: Re: [MIB-DOCTORS] Why is this MIB module read-write?
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: Mon, 03 Feb 2014 21:01:38 -0000

Hi -

>From: Thomas Nadeau <tnadeau@lucidvision.com>
>Sent: Feb 3, 2014 10:31 AM
>To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
>Cc: Farrel Adrian <adrian@olddog.co.uk>, "MIB Doctors (E-mail)" <mib-doctors@ietf.org>
>Subject: Re: [MIB-DOCTORS] Why is this MIB module read-write?
>
>
>	Juergen,
>
>	I like the use of the adverb; it shows we mean business. *)
>
>	--Tom

To paraphrase another thread on another subject on the IETF list:
if someone puts any read-write or read-create objects in a MIB
module, such a statement gives the ADs another tool with which
to slap the WG down.

Randy

From adrian@olddog.co.uk  Tue Feb  4 05:32:16 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 BB03C1A0430 for <mib-doctors@ietfa.amsl.com>; Tue,  4 Feb 2014 05:32:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, 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 ZSIdszHavSsd for <mib-doctors@ietfa.amsl.com>; Tue,  4 Feb 2014 05:32:13 -0800 (PST)
Received: from asmtp5.iomartmail.com (asmtp5.iomartmail.com [62.128.201.176]) by ietfa.amsl.com (Postfix) with ESMTP id D87B11A041E for <mib-doctors@ietf.org>; Tue,  4 Feb 2014 05:32:12 -0800 (PST)
Received: from asmtp5.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id s14DWBug007304 for <mib-doctors@ietf.org>; Tue, 4 Feb 2014 13:32:11 GMT
Received: from 950129200 ([62.205.103.124]) (authenticated bits=0) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id s14DW8T6007258 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <mib-doctors@ietf.org>; Tue, 4 Feb 2014 13:32:09 GMT
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <mib-doctors@ietf.org>
Date: Tue, 4 Feb 2014 13:32:06 -0000
Message-ID: <05c501cf21ad$80d97ef0$828c7cd0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_05C6_01CF21AD.80DCDA50"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac8hrXgw6b2pv4v1Q1OdkmdclBj4bQ==
Content-Language: en-gb
X-TM-AS-MML: No
Subject: [MIB-DOCTORS] Read-only MIB modules
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: Tue, 04 Feb 2014 13:32:16 -0000

This is a multipart message in MIME format.

------=_NextPart_000_05C6_01CF21AD.80DCDA50
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hi,
 
The MPLS working group is testing the water to see whether one of its MIB
modules should be "reduced" to read-only. This is the document that triggered my
recent questions that led on to the draft advice you are working on. The WG took
the document back to make this decision.
 
You'll note below that we immediately have an implementation claim (not for this
doc, but for the modules it extends).
 
An interesting situation, I think.
 
A
 
From: mpls [mailto:mpls-bounces@ietf.org] On Behalf Of GyeRok Gwun (???)
Sent: 04 February 2014 09:57
To: 'mpls@ietf.org'
Cc: 'mpls-chairs@tools.ietf.org'; 'draft-ietf-mpls-tp-te-mib@tools.ietf.org'
Subject: Re: [mpls] seeking consensus on making draft-ietf-mpls-tp-te-mib read-
only
 
No/oppose to make as Read-only mib.
In our products we extensively use R/W object of TE mib. We also have NMS/EMS
that use TE read-write Objects
 
Best Regards
Gwun
 
-----Original Message-----
From: mpls [mailto:mpls-bounces@ietf.org] On Behalf Of Loa Andersson
Sent: Monday, February 03, 2014 10:55 PM
To: mpls@ietf.org
Cc: mpls-chairs@tools.ietf.org; draft-ietf-mpls-tp-te-mib@tools.ietf.org
Subject: [mpls] seeking consensus on making draft-ietf-mpls-tp-te-mib read- only
 
Working Group,
 
We have just recalled draft-ietf-mpls-tp-te-mib from the IESG to the working
group for more work. We have a series of comments that are mostly for
clarification. However the main reason for recalling the document is that there
is one point where we need to confirm working group consensus.
 
The IETF, the working group and the MIB Doctors are today very reluctant to
produce read-write MIB modules. The current draft is read-write for a few
objects, this is based on a consensus call for an earlier discussion, however
the consensus call was not clear. It can be taken to mean both that we want to
go with read-write objects and that we want to see read-only. Is it clear that
it has been interpreted differently by different individuals.
 
The authors and chairs have discussed the issue and we have a rough consensus
that we want the MIB module(s) to be read-only.
 
We therefore are asking the working group if this is OK for the MIB
module(s) in the current document. Please indicate Support or Oppose for this
MIB (draft-ietf-mpls-tp-te-mib) to be read-only.
 
Please send your comments to the working group mailing list before February 18,
2014.
 
Loa
for the MPLS wg chairs
-- 
 
 
Loa Andersson                        email: loa@mail01.huawei.com
Senior MPLS Expert                          loa@pi.nu
Huawei Technologies (consultant)     phone: +46 739 81 21 64
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls
 

------=_NextPart_000_05C6_01CF21AD.80DCDA50
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@01CF21AD.7DA72AC0"><!--[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:UseFELayout/>
</w:Compatibility>
<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:Gulim;
	panose-1:2 11 6 0 0 1 1 1 1 1;
	mso-font-alt:\AD74\B9BC;
	mso-font-charset:129;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:-1342176593 1775729915 48 0 524447 0;}
@font-face
	{font-family:Gulim;
	panose-1:2 11 6 0 0 1 1 1 1 1;
	mso-font-alt:\AD74\B9BC;
	mso-font-charset:129;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:-1342176593 1775729915 48 0 524447 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;}
@font-face
	{font-family:"Malgun Gothic";
	panose-1:2 11 5 3 2 0 0 2 0 4;
	mso-font-charset:129;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:-1879047505 165117179 18 0 524289 0;}
@font-face
	{font-family:"\@Malgun Gothic";
	panose-1:2 11 5 3 2 0 0 2 0 4;
	mso-font-charset:129;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:-1879047505 165117179 18 0 524289 0;}
@font-face
	{font-family:"\@Gulim";
	panose-1:2 11 6 0 0 1 1 1 1 1;
	mso-font-charset:129;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:-1342176593 1775729915 48 0 524447 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;
	text-align:justify;
	text-justify:inter-ideograph;
	mso-pagination:widow-orphan;
	text-autospace:none;
	word-break:break-all;
	font-size:10.0pt;
	font-family:"Malgun Gothic","sans-serif";
	mso-bidi-font-family:Gulim;
	mso-fareast-language:KO;}
a:link, span.MsoHyperlink
	{mso-style-noshow:yes;
	mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;
	text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-noshow:yes;
	mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;
	text-underline:single;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-noshow:yes;
	mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	text-autospace:none;
	word-break:break-all;
	font-size:10.0pt;
	font-family:"Courier New","serif";
	mso-fareast-font-family:Gulim;
	mso-fareast-language:KO;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-noshow:yes;
	mso-style-priority:99;
	mso-style-unhide:no;
	mso-style-locked:yes;
	mso-style-link:"Plain Text";
	mso-ansi-font-size:10.5pt;
	mso-bidi-font-size:10.5pt;
	font-family:Consolas;
	mso-ascii-font-family:Consolas;
	mso-fareast-font-family:"Malgun Gothic";
	mso-hansi-font-family:Consolas;
	mso-bidi-font-family:Consolas;
	mso-fareast-language:KO;}
span.EmailStyle19
	{mso-style-type:personal;
	mso-style-noshow:yes;
	mso-style-unhide:no;
	font-family:"Malgun Gothic","sans-serif";
	mso-ascii-font-family:"Malgun Gothic";
	mso-fareast-font-family:"Malgun Gothic";
	mso-hansi-font-family:"Malgun Gothic";
	color:windowtext;}
p.a, li.a, div.a
	{mso-style-name:\AE00\C790\B9CC;
	mso-style-unhide:no;
	mso-style-link:"\AE00\C790\B9CC Char";
	margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	mso-pagination:widow-orphan;
	text-autospace:none;
	word-break:break-all;
	font-size:10.0pt;
	font-family:"Malgun Gothic","sans-serif";
	mso-bidi-font-family:Gulim;
	mso-fareast-language:KO;}
span.Char
	{mso-style-name:"\AE00\C790\B9CC Char";
	mso-style-priority:99;
	mso-style-unhide:no;
	mso-style-locked:yes;
	mso-style-link:\AE00\C790\B9CC;
	font-family:"Courier New","serif";
	mso-ascii-font-family:"Courier New";
	mso-hansi-font-family:"Courier New";
	mso-bidi-font-family:"Courier New";}
span.EmailStyle22
	{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;}
span.SpellE
	{mso-style-name:"";
	mso-spl-e:yes;}
.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:3.0cm 72.0pt 72.0pt 72.0pt;
	mso-header-margin:36.0pt;
	mso-footer-margin:36.0pt;
	mso-paper-source:0;}
div.WordSection1
	{page:WordSection1;}
--></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 lang=3DEN-GB =
link=3D"#0563C1" vlink=3D"#954F72" style=3D'tab-interval:36.0pt'><div =
class=3DWordSection1><p class=3DMsoNormal =
style=3D'word-break:normal'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-fareast-=
font-family:Calibri;mso-bidi-font-family:"Times New =
Roman";color:#1F497D'>Hi,<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'word-break:normal'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-fareast-=
font-family:Calibri;mso-bidi-font-family:"Times New =
Roman";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal =
style=3D'word-break:normal'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-fareast-=
font-family:Calibri;mso-bidi-font-family:"Times New =
Roman";color:#1F497D'>The MPLS working group is testing the water to see =
whether one of its MIB modules should be &quot;reduced&quot; to =
read-only. This is the document that triggered my recent questions that =
led on to the draft advice you are working on. The WG took the document =
back to make this decision.<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'word-break:normal'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-fareast-=
font-family:Calibri;mso-bidi-font-family:"Times New =
Roman";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal =
style=3D'word-break:normal'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-fareast-=
font-family:Calibri;mso-bidi-font-family:"Times New =
Roman";color:#1F497D'>You'll note below that we immediately have an =
implementation claim (not for this doc, but for the modules it =
extends).<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'word-break:normal'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-fareast-=
font-family:Calibri;mso-bidi-font-family:"Times New =
Roman";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal =
style=3D'word-break:normal'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-fareast-=
font-family:Calibri;mso-bidi-font-family:"Times New =
Roman";color:#1F497D'>An interesting situation, I =
think.<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'word-break:normal'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-fareast-=
font-family:Calibri;mso-bidi-font-family:"Times New =
Roman";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal =
style=3D'word-break:normal'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-fareast-=
font-family:Calibri;mso-bidi-font-family:"Times New =
Roman";color:#1F497D'>A<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'word-break:normal'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-fareast-=
font-family:Calibri;mso-bidi-font-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 align=3Dleft =
style=3D'text-align:left;text-autospace:ideograph-numeric =
ideograph-other;word-break:normal'><b><span lang=3DEN-US =
style=3D'font-family:"Tahoma","sans-serif";mso-fareast-font-family:Gulim;=
mso-ansi-language:EN-US'>From:</span></b><span lang=3DEN-US =
style=3D'font-family:"Tahoma","sans-serif";mso-fareast-font-family:Gulim;=
mso-ansi-language:EN-US'> mpls [mailto:mpls-bounces@ietf.org] <b>On =
Behalf Of </b>GyeRok Gwun (???)<br><b>Sent:</b> 04 February 2014 =
09:57<br><b>To:</b> 'mpls@ietf.org'<br><b>Cc:</b> =
'mpls-chairs@tools.ietf.org'; =
'draft-ietf-mpls-tp-te-mib@tools.ietf.org'<br><b>Subject:</b> Re: [mpls] =
seeking consensus on making draft-ietf-mpls-tp-te-mib read- =
only<o:p></o:p></span></p></div></div><p class=3DMsoNormal align=3Dleft =
style=3D'text-align:left'><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>No/oppose to make as Read-only =
mib.<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>In our products we extensively use R/W =
object of TE mib. We also have NMS/EMS that use TE read-write =
Objects<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>Best Regards<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>Gwun<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>-----Original =
Message-----<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US style=3D'mso-ansi-language:EN-US'>From: mpls [<a =
href=3D"mailto:mpls-bounces@ietf.org">mailto:mpls-bounces@ietf.org</a>] =
On Behalf Of Loa Andersson<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>Sent: Monday, February 03, 2014 10:55 =
PM<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>To: <a =
href=3D"mailto:mpls@ietf.org">mpls@ietf.org</a><o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>Cc: <a =
href=3D"mailto:mpls-chairs@tools.ietf.org">mpls-chairs@tools.ietf.org</a>=
; <a =
href=3D"mailto:draft-ietf-mpls-tp-te-mib@tools.ietf.org">draft-ietf-mpls-=
tp-te-mib@tools.ietf.org</a><o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>Subject: [mpls] seeking consensus on =
making draft-ietf-mpls-tp-te-mib read- only<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>Working Group,<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>We have just recalled =
draft-ietf-mpls-tp-te-mib from the IESG to the working group for more =
work. We have a series of comments that are mostly for clarification. =
However the main reason for recalling the document is that there is one =
point where we need to confirm working group =
consensus.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>The IETF, the working group and the =
MIB Doctors are today very reluctant to produce read-write MIB modules. =
The current draft is read-write for a few objects, this is based on a =
consensus call for an earlier discussion, however the consensus call was =
not clear. It can be taken to mean both that we want to go with =
read-write objects and that we want to see read-only. Is it clear that =
it has been interpreted differently by different =
individuals.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>The authors and chairs have discussed =
the issue and we have a rough consensus that we want the MIB module(s) =
to be read-only.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>We therefore are asking the working =
group if this is OK for the MIB<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>module(s) in the current document. =
Please indicate Support or Oppose for this MIB =
(draft-ietf-mpls-tp-te-mib) to be read-only.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>Please send your comments to the =
working group mailing list before February 18, =
2014.<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>Loa<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>for the MPLS wg =
chairs<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>-- <o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>Loa =
Andersson&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
; email: <a =
href=3D"mailto:loa@mail01.huawei.com">loa@mail01.huawei.com</a><o:p></o:p=
></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>Senior MPLS =
Expert&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp; <a =
href=3D"mailto:loa@pi.nu">loa@pi.nu</a><o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>Huawei Technologies =
(consultant)&nbsp;&nbsp;&nbsp;&nbsp; phone: +46 739 81 21 =
64<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>_______________________________________=
________<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>mpls mailing =
list<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'><a =
href=3D"mailto:mpls@ietf.org">mpls@ietf.org</a><o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'><a =
href=3D"https://www.ietf.org/mailman/listinfo/mpls">https://www.ietf.org/=
mailman/listinfo/mpls</a><o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>_______________________________________=
________<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>mpls mailing =
list<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'><a =
href=3D"mailto:mpls@ietf.org">mpls@ietf.org</a><o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'><a =
href=3D"https://www.ietf.org/mailman/listinfo/mpls">https://www.ietf.org/=
mailman/listinfo/mpls</a><o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p></div></div=
></body></html>
------=_NextPart_000_05C6_01CF21AD.80DCDA50--



From tnadeau@lucidvision.com  Tue Feb  4 06:10:21 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 8E9F61A011A for <mib-doctors@ietfa.amsl.com>; Tue,  4 Feb 2014 06:10:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.433
X-Spam-Level: 
X-Spam-Status: No, score=-2.433 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RP_MATCHES_RCVD=-0.535] 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 DNdeJ6GsDImn for <mib-doctors@ietfa.amsl.com>; Tue,  4 Feb 2014 06:10:18 -0800 (PST)
Received: from lucidvision.com (lucidvision.com [72.71.250.34]) by ietfa.amsl.com (Postfix) with ESMTP id 1B68D1A00DB for <mib-doctors@ietf.org>; Tue,  4 Feb 2014 06:10:18 -0800 (PST)
Received: from [10.9.247.162] (mobile-166-137-187-011.mycingular.net [166.137.187.11]) by lucidvision.com (Postfix) with ESMTP id 1996726DBB07; Tue,  4 Feb 2014 09:10:17 -0500 (EST)
References: <05c501cf21ad$80d97ef0$828c7cd0$@olddog.co.uk>
Mime-Version: 1.0 (1.0)
In-Reply-To: <05c501cf21ad$80d97ef0$828c7cd0$@olddog.co.uk>
Content-Type: multipart/alternative; boundary=Apple-Mail-F0886F1A-E1B2-48A1-8186-78CEFEB577A8
Content-Transfer-Encoding: 7bit
Message-Id: <634D1E93-0ECE-477B-8778-D08814E85DB8@lucidvision.com>
X-Mailer: iPhone Mail (11B554a)
From: "Thomas D. Nadeau" <tnadeau@lucidvision.com>
Date: Tue, 4 Feb 2014 06:10:14 -0800
To: "adrian@olddog.co.uk" <adrian@olddog.co.uk>
Cc: "<mib-doctors@ietf.org>" <mib-doctors@ietf.org>
Subject: Re: [MIB-DOCTORS] Read-only MIB modules
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, 04 Feb 2014 14:10:21 -0000

--Apple-Mail-F0886F1A-E1B2-48A1-8186-78CEFEB577A8
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable

I will point out that there are and have been *many* implementations of r-w o=
bjects in the past; that is not at issue IMHO. What is at issue is to ask ou=
rselves whether or not anyone in practice actually uses them. The evidence i=
s pretty overwhelmingly in favor of netconf/json/or even the good old CLI.  =
For the IETF the question is then one of allocation of resources to work on s=
omething that is hardly if ever used in practice versus say pushing those fe=
w resources towards produce a yang mode that definitely is.

Tom=20
=20

> On Feb 4, 2014, at 5:32 AM, "Adrian Farrel" <adrian@olddog.co.uk> wrote:
>=20
> Hi,
> =20
> The MPLS working group is testing the water to see whether one of its MIB m=
odules should be "reduced" to read-only. This is the document that triggered=
 my recent questions that led on to the draft advice you are working on. The=
 WG took the document back to make this decision.
> =20
> You'll note below that we immediately have an implementation claim (not fo=
r this doc, but for the modules it extends).
> =20
> An interesting situation, I think.
> =20
> A
> =20
> From: mpls [mailto:mpls-bounces@ietf.org] On Behalf Of GyeRok Gwun (???)
> Sent: 04 February 2014 09:57
> To: 'mpls@ietf.org'
> Cc: 'mpls-chairs@tools.ietf.org'; 'draft-ietf-mpls-tp-te-mib@tools.ietf.or=
g'
> Subject: Re: [mpls] seeking consensus on making draft-ietf-mpls-tp-te-mib r=
ead- only
> =20
> No/oppose to make as Read-only mib.
> In our products we extensively use R/W object of TE mib. We also have NMS/=
EMS that use TE read-write Objects
> =20
> Best Regards
> Gwun
> =20
> -----Original Message-----
> From: mpls [mailto:mpls-bounces@ietf.org] On Behalf Of Loa Andersson
> Sent: Monday, February 03, 2014 10:55 PM
> To: mpls@ietf.org
> Cc: mpls-chairs@tools.ietf.org; draft-ietf-mpls-tp-te-mib@tools.ietf.org
> Subject: [mpls] seeking consensus on making draft-ietf-mpls-tp-te-mib read=
- only
> =20
> Working Group,
> =20
> We have just recalled draft-ietf-mpls-tp-te-mib from the IESG to the worki=
ng group for more work. We have a series of comments that are mostly for cla=
rification. However the main reason for recalling the document is that there=
 is one point where we need to confirm working group consensus.
> =20
> The IETF, the working group and the MIB Doctors are today very reluctant t=
o produce read-write MIB modules. The current draft is read-write for a few o=
bjects, this is based on a consensus call for an earlier discussion, however=
 the consensus call was not clear. It can be taken to mean both that we want=
 to go with read-write objects and that we want to see read-only. Is it clea=
r that it has been interpreted differently by different individuals.
> =20
> The authors and chairs have discussed the issue and we have a rough consen=
sus that we want the MIB module(s) to be read-only.
> =20
> We therefore are asking the working group if this is OK for the MIB
> module(s) in the current document. Please indicate Support or Oppose for t=
his MIB (draft-ietf-mpls-tp-te-mib) to be read-only.
> =20
> Please send your comments to the working group mailing list before Februar=
y 18, 2014.
> =20
> Loa
> for the MPLS wg chairs
> --
> =20
> =20
> Loa Andersson                      email: loa@mail01.huawei.com
> Senior MPLS Expert                 loa@pi.nu
> Huawei Technologies (consultant)   phone: +46 739 81 21 64
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
> =20
> _______________________________________________
> MIB-DOCTORS mailing list
> MIB-DOCTORS@ietf.org
> https://www.ietf.org/mailman/listinfo/mib-doctors

--Apple-Mail-F0886F1A-E1B2-48A1-8186-78CEFEB577A8
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=3D=
utf-8"></head><body dir=3D"auto"><div>I will point out that there are and ha=
ve been *many* implementations of r-w objects in the past; that is not at is=
sue IMHO. What is at issue is to ask ourselves whether or not anyone in prac=
tice actually uses them. The evidence is pretty overwhelmingly in favor of n=
etconf/json/or even the good old CLI. &nbsp;For the IETF the question is the=
n one of allocation of resources to work on something that is hardly if ever=
 used in practice versus say pushing those few resources towards produce a y=
ang mode that definitely is.</div><div><br></div><div>Tom&nbsp;</div><div>&n=
bsp;</div><div><br>On Feb 4, 2014, at 5:32 AM, "Adrian Farrel" &lt;<a href=3D=
"mailto:adrian@olddog.co.uk">adrian@olddog.co.uk</a>&gt; wrote:<br><br></div=
><blockquote type=3D"cite"><div><meta http-equiv=3D"Content-Type" content=3D=
"text/html; charset=3Dus-ascii"><meta name=3D"ProgId" content=3D"Word.Docume=
nt"><meta name=3D"Generator" content=3D"Microsoft Word 14"><meta name=3D"Ori=
ginator" content=3D"Microsoft Word 14"><link rel=3D"File-List" href=3D"cid:f=
ilelist.xml@01CF21AD.7DA72AC0"><!--[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:UseFELayout/>
</w:Compatibility>
<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" DefSemiH=
idden=3D"true" DefQFormat=3D"false" DefPriority=3D"99" LatentStyleCount=3D"2=
67">
<w:LsdException Locked=3D"false" Priority=3D"0" SemiHidden=3D"false" UnhideW=
henUsed=3D"false" QFormat=3D"true" Name=3D"Normal"/>
<w:LsdException Locked=3D"false" Priority=3D"9" SemiHidden=3D"false" UnhideW=
henUsed=3D"false" QFormat=3D"true" Name=3D"heading 1"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" Name=3D"hea=
ding 2"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" Name=3D"hea=
ding 3"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" Name=3D"hea=
ding 4"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" Name=3D"hea=
ding 5"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" Name=3D"hea=
ding 6"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" Name=3D"hea=
ding 7"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" Name=3D"hea=
ding 8"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" Name=3D"hea=
ding 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"ca=
ption"/>
<w:LsdException Locked=3D"false" Priority=3D"10" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" QFormat=3D"true" Name=3D"Title"/>
<w:LsdException Locked=3D"false" Priority=3D"1" Name=3D"Default Paragraph Fo=
nt"/>
<w:LsdException Locked=3D"false" Priority=3D"11" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtitle"/>
<w:LsdException Locked=3D"false" Priority=3D"22" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" QFormat=3D"true" Name=3D"Strong"/>
<w:LsdException Locked=3D"false" Priority=3D"20" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" QFormat=3D"true" Name=3D"Emphasis"/>
<w:LsdException Locked=3D"false" Priority=3D"59" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" Name=3D"Table Grid"/>
<w:LsdException Locked=3D"false" UnhideWhenUsed=3D"false" Name=3D"Placeholde=
r Text"/>
<w:LsdException Locked=3D"false" Priority=3D"1" SemiHidden=3D"false" UnhideW=
henUsed=3D"false" QFormat=3D"true" Name=3D"No Spacing"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" Name=3D"Light Shading"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" Name=3D"Light List"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" Name=3D"Light Grid"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" Name=3D"Medium Shading 1"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" Name=3D"Medium Shading 2"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" Name=3D"Medium List 1"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" Name=3D"Medium List 2"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" Name=3D"Medium Grid 1"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" Name=3D"Medium Grid 2"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" Name=3D"Medium Grid 3"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" Name=3D"Dark List"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" Name=3D"Colorful Shading"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" Name=3D"Colorful List"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" Name=3D"Colorful Grid"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" Name=3D"Light Shading Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" Name=3D"Light List Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" Name=3D"Light Grid Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" Unhide=
WhenUsed=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" Unhide=
WhenUsed=3D"false" QFormat=3D"true" Name=3D"List Paragraph"/>
<w:LsdException Locked=3D"false" Priority=3D"29" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" QFormat=3D"true" Name=3D"Quote"/>
<w:LsdException Locked=3D"false" Priority=3D"30" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Quote"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" Name=3D"Medium List 2 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" Name=3D"Dark List Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" Name=3D"Colorful Shading Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" Name=3D"Colorful List Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" Name=3D"Colorful Grid Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" Name=3D"Light Shading Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" Name=3D"Light List Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" Name=3D"Light Grid Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" Name=3D"Medium List 1 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" Name=3D"Medium List 2 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" Name=3D"Dark List Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" Name=3D"Colorful Shading Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" Name=3D"Colorful List Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" Name=3D"Colorful Grid Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" Name=3D"Light Shading Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" Name=3D"Light List Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" Name=3D"Light Grid Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" Name=3D"Medium List 1 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" Name=3D"Medium List 2 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" Name=3D"Dark List Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" Name=3D"Colorful Shading Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" Name=3D"Colorful List Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" Name=3D"Colorful Grid Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" Name=3D"Light Shading Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" Name=3D"Light List Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" Name=3D"Light Grid Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" Name=3D"Medium List 1 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" Name=3D"Medium List 2 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" Name=3D"Dark List Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" Name=3D"Colorful Shading Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" Name=3D"Colorful List Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" Name=3D"Colorful Grid Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" Name=3D"Light Shading Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" Name=3D"Light List Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" Name=3D"Light Grid Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" Name=3D"Medium List 1 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" Name=3D"Medium List 2 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" Name=3D"Dark List Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" Name=3D"Colorful Shading Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" Name=3D"Colorful List Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" Name=3D"Colorful Grid Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" Name=3D"Light Shading Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" Name=3D"Light List Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" Name=3D"Light Grid Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" Name=3D"Medium List 1 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" Name=3D"Medium List 2 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" Name=3D"Dark List Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" Name=3D"Colorful Shading Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" Name=3D"Colorful List Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" Name=3D"Colorful Grid Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"19" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtle Emphasis"/>
<w:LsdException Locked=3D"false" Priority=3D"21" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Emphasis"/>
<w:LsdException Locked=3D"false" Priority=3D"31" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtle Reference"/>
<w:LsdException Locked=3D"false" Priority=3D"32" SemiHidden=3D"false" Unhide=
WhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Reference"/>
<w:LsdException Locked=3D"false" Priority=3D"33" SemiHidden=3D"false" Unhide=
WhenUsed=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"TO=
C Heading"/>
</w:LatentStyles>
</xml><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:Gulim;
	panose-1:2 11 6 0 0 1 1 1 1 1;
	mso-font-alt:\AD74\B9BC;
	mso-font-charset:129;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:-1342176593 1775729915 48 0 524447 0;}
@font-face
	{font-family:Gulim;
	panose-1:2 11 6 0 0 1 1 1 1 1;
	mso-font-alt:\AD74\B9BC;
	mso-font-charset:129;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:-1342176593 1775729915 48 0 524447 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;}
@font-face
	{font-family:"Malgun Gothic";
	panose-1:2 11 5 3 2 0 0 2 0 4;
	mso-font-charset:129;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:-1879047505 165117179 18 0 524289 0;}
@font-face
	{font-family:"\@Malgun Gothic";
	panose-1:2 11 5 3 2 0 0 2 0 4;
	mso-font-charset:129;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:-1879047505 165117179 18 0 524289 0;}
@font-face
	{font-family:"\@Gulim";
	panose-1:2 11 6 0 0 1 1 1 1 1;
	mso-font-charset:129;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:-1342176593 1775729915 48 0 524447 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;
	text-align:justify;
	text-justify:inter-ideograph;
	mso-pagination:widow-orphan;
	text-autospace:none;
	word-break:break-all;
	font-size:10.0pt;
	font-family:"Malgun Gothic","sans-serif";
	mso-bidi-font-family:Gulim;
	mso-fareast-language:KO;}
a:link, span.MsoHyperlink
	{mso-style-noshow:yes;
	mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;
	text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-noshow:yes;
	mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;
	text-underline:single;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-noshow:yes;
	mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	text-autospace:none;
	word-break:break-all;
	font-size:10.0pt;
	font-family:"Courier New","serif";
	mso-fareast-font-family:Gulim;
	mso-fareast-language:KO;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-noshow:yes;
	mso-style-priority:99;
	mso-style-unhide:no;
	mso-style-locked:yes;
	mso-style-link:"Plain Text";
	mso-ansi-font-size:10.5pt;
	mso-bidi-font-size:10.5pt;
	font-family:Consolas;
	mso-ascii-font-family:Consolas;
	mso-fareast-font-family:"Malgun Gothic";
	mso-hansi-font-family:Consolas;
	mso-bidi-font-family:Consolas;
	mso-fareast-language:KO;}
span.EmailStyle19
	{mso-style-type:personal;
	mso-style-noshow:yes;
	mso-style-unhide:no;
	font-family:"Malgun Gothic","sans-serif";
	mso-ascii-font-family:"Malgun Gothic";
	mso-fareast-font-family:"Malgun Gothic";
	mso-hansi-font-family:"Malgun Gothic";
	color:windowtext;}
p.a, li.a, div.a
	{mso-style-name:\AE00\C790\B9CC;
	mso-style-unhide:no;
	mso-style-link:"\AE00\C790\B9CC Char";
	margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	mso-pagination:widow-orphan;
	text-autospace:none;
	word-break:break-all;
	font-size:10.0pt;
	font-family:"Malgun Gothic","sans-serif";
	mso-bidi-font-family:Gulim;
	mso-fareast-language:KO;}
span.Char
	{mso-style-name:"\AE00\C790\B9CC Char";
	mso-style-priority:99;
	mso-style-unhide:no;
	mso-style-locked:yes;
	mso-style-link:\AE00\C790\B9CC;
	font-family:"Courier New","serif";
	mso-ascii-font-family:"Courier New";
	mso-hansi-font-family:"Courier New";
	mso-bidi-font-family:"Courier New";}
span.EmailStyle22
	{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;}
span.SpellE
	{mso-style-name:"";
	mso-spl-e:yes;}
.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:3.0cm 72.0pt 72.0pt 72.0pt;
	mso-header-margin:36.0pt;
	mso-footer-margin:36.0pt;
	mso-paper-source:0;}
div.WordSection1
	{page:WordSection1;}
--></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]--><div class=3D"WordSection1"><p class=3D"Ms=
oNormal" style=3D"word-break:normal"><span style=3D"font-size:11.0pt;font-fa=
mily:&quot;Calibri&quot;,&quot;sans-serif&quot;;mso-fareast-font-family:Cali=
bri;mso-bidi-font-family:&quot;Times New Roman&quot;;color:#1F497D">Hi,<o:p>=
</o:p></span></p><p class=3D"MsoNormal" style=3D"word-break:normal"><span st=
yle=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quo=
t;;mso-fareast-font-family:Calibri;mso-bidi-font-family:&quot;Times New Roma=
n&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span></p><p class=3D"MsoNormal" st=
yle=3D"word-break:normal"><span style=3D"font-size:11.0pt;font-family:&quot;=
Calibri&quot;,&quot;sans-serif&quot;;mso-fareast-font-family:Calibri;mso-bid=
i-font-family:&quot;Times New Roman&quot;;color:#1F497D">The MPLS working gr=
oup is testing the water to see whether one of its MIB modules should be "re=
duced" to read-only. This is the document that triggered my recent questions=
 that led on to the draft advice you are working on. The WG took the documen=
t back to make this decision.<o:p></o:p></span></p><p class=3D"MsoNormal" st=
yle=3D"word-break:normal"><span style=3D"font-size:11.0pt;font-family:&quot;=
Calibri&quot;,&quot;sans-serif&quot;;mso-fareast-font-family:Calibri;mso-bid=
i-font-family:&quot;Times New Roman&quot;;color:#1F497D"><o:p>&nbsp;</o:p></=
span></p><p class=3D"MsoNormal" style=3D"word-break:normal"><span style=3D"f=
ont-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;mso-f=
areast-font-family:Calibri;mso-bidi-font-family:&quot;Times New Roman&quot;;=
color:#1F497D">You'll note below that we immediately have an implementation c=
laim (not for this doc, but for the modules it extends).<o:p></o:p></span></=
p><p class=3D"MsoNormal" style=3D"word-break:normal"><span style=3D"font-siz=
e:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;mso-fareast-=
font-family:Calibri;mso-bidi-font-family:&quot;Times New Roman&quot;;color:#=
1F497D"><o:p>&nbsp;</o:p></span></p><p class=3D"MsoNormal" style=3D"word-bre=
ak:normal"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&=
quot;sans-serif&quot;;mso-fareast-font-family:Calibri;mso-bidi-font-family:&=
quot;Times New Roman&quot;;color:#1F497D">An interesting situation, I think.=
<o:p></o:p></span></p><p class=3D"MsoNormal" style=3D"word-break:normal"><sp=
an style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-seri=
f&quot;;mso-fareast-font-family:Calibri;mso-bidi-font-family:&quot;Times New=
 Roman&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span></p><p class=3D"MsoNorma=
l" style=3D"word-break:normal"><span style=3D"font-size:11.0pt;font-family:&=
quot;Calibri&quot;,&quot;sans-serif&quot;;mso-fareast-font-family:Calibri;ms=
o-bidi-font-family:&quot;Times New Roman&quot;;color:#1F497D">A<o:p></o:p></=
span></p><p class=3D"MsoNormal" style=3D"word-break:normal"><span style=3D"f=
ont-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;mso-f=
areast-font-family:Calibri;mso-bidi-font-family:&quot;Times New Roman&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:n=
one;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm"><p class=3D"Ms=
oNormal" align=3D"left" style=3D"text-align:left;text-autospace:ideograph-nu=
meric ideograph-other;word-break:normal"><b><span lang=3D"EN-US" style=3D"fo=
nt-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;mso-fareast-font-family:=
Gulim;mso-ansi-language:EN-US">From:</span></b><span lang=3D"EN-US" style=3D=
"font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;mso-fareast-font-fami=
ly:Gulim;mso-ansi-language:EN-US"> mpls [<a href=3D"mailto:mpls-bounces@ietf=
.org">mailto:mpls-bounces@ietf.org</a>] <b>On Behalf Of </b>GyeRok Gwun (???=
)<br><b>Sent:</b> 04 February 2014 09:57<br><b>To:</b> '<a href=3D"mailto:mp=
ls@ietf.org">mpls@ietf.org</a>'<br><b>Cc:</b> '<a href=3D"mailto:mpls-chairs=
@tools.ietf.org">mpls-chairs@tools.ietf.org</a>'; '<a href=3D"mailto:draft-i=
etf-mpls-tp-te-mib@tools.ietf.org">draft-ietf-mpls-tp-te-mib@tools.ietf.org<=
/a>'<br><b>Subject:</b> Re: [mpls] seeking consensus on making draft-ietf-mp=
ls-tp-te-mib read- only<o:p></o:p></span></p></div></div><p class=3D"MsoNorm=
al" align=3D"left" style=3D"text-align:left"><o:p>&nbsp;</o:p></p><p class=3D=
"MsoPlainText"><span lang=3D"EN-US" style=3D"mso-ansi-language:EN-US">No/opp=
ose to make as Read-only mib.<o:p></o:p></span></p><p class=3D"MsoPlainText"=
><span lang=3D"EN-US" style=3D"mso-ansi-language:EN-US">In our products we e=
xtensively use R/W object of TE mib. We also have NMS/EMS that use TE read-w=
rite Objects<o:p></o:p></span></p><p class=3D"MsoPlainText"><span lang=3D"EN=
-US" style=3D"mso-ansi-language:EN-US"><o:p>&nbsp;</o:p></span></p><p class=3D=
"MsoPlainText"><span lang=3D"EN-US" style=3D"mso-ansi-language:EN-US">Best R=
egards<o:p></o:p></span></p><p class=3D"MsoPlainText"><span lang=3D"EN-US" s=
tyle=3D"mso-ansi-language:EN-US">Gwun<o:p></o:p></span></p><p class=3D"MsoPl=
ainText"><span lang=3D"EN-US" style=3D"mso-ansi-language:EN-US"><o:p>&nbsp;<=
/o:p></span></p><p class=3D"MsoPlainText"><span lang=3D"EN-US" style=3D"mso-=
ansi-language:EN-US">-----Original Message-----<o:p></o:p></span></p><p clas=
s=3D"MsoPlainText"><span lang=3D"EN-US" style=3D"mso-ansi-language:EN-US">From:=
 mpls [<a href=3D"mailto:mpls-bounces@ietf.org">mailto:mpls-bounces@ietf.org=
</a>] On Behalf Of Loa Andersson<o:p></o:p></span></p><p class=3D"MsoPlainTe=
xt"><span lang=3D"EN-US" style=3D"mso-ansi-language:EN-US">Sent: Monday, Feb=
ruary 03, 2014 10:55 PM<o:p></o:p></span></p><p class=3D"MsoPlainText"><span=
 lang=3D"EN-US" style=3D"mso-ansi-language:EN-US">To: <a href=3D"mailto:mpls=
@ietf.org">mpls@ietf.org</a><o:p></o:p></span></p><p class=3D"MsoPlainText">=
<span lang=3D"EN-US" style=3D"mso-ansi-language:EN-US">Cc: <a href=3D"mailto=
:mpls-chairs@tools.ietf.org">mpls-chairs@tools.ietf.org</a>; <a href=3D"mail=
to:draft-ietf-mpls-tp-te-mib@tools.ietf.org">draft-ietf-mpls-tp-te-mib@tools=
.ietf.org</a><o:p></o:p></span></p><p class=3D"MsoPlainText"><span lang=3D"E=
N-US" style=3D"mso-ansi-language:EN-US">Subject: [mpls] seeking consensus on=
 making draft-ietf-mpls-tp-te-mib read- only<o:p></o:p></span></p><p class=3D=
"MsoPlainText"><span lang=3D"EN-US" style=3D"mso-ansi-language:EN-US"><o:p>&=
nbsp;</o:p></span></p><p class=3D"MsoPlainText"><span lang=3D"EN-US" style=3D=
"mso-ansi-language:EN-US">Working Group,<o:p></o:p></span></p><p class=3D"Ms=
oPlainText"><span lang=3D"EN-US" style=3D"mso-ansi-language:EN-US"><o:p>&nbs=
p;</o:p></span></p><p class=3D"MsoPlainText"><span lang=3D"EN-US" style=3D"m=
so-ansi-language:EN-US">We have just recalled draft-ietf-mpls-tp-te-mib from=
 the IESG to the working group for more work. We have a series of comments t=
hat are mostly for clarification. However the main reason for recalling the d=
ocument is that there is one point where we need to confirm working group co=
nsensus.<o:p></o:p></span></p><p class=3D"MsoPlainText"><span lang=3D"EN-US"=
 style=3D"mso-ansi-language:EN-US"><o:p>&nbsp;</o:p></span></p><p class=3D"M=
soPlainText"><span lang=3D"EN-US" style=3D"mso-ansi-language:EN-US">The IETF,=
 the working group and the MIB Doctors are today very reluctant to produce r=
ead-write MIB modules. The current draft is read-write for a few objects, th=
is is based on a consensus call for an earlier discussion, however the conse=
nsus call was not clear. It can be taken to mean both that we want to go wit=
h read-write objects and that we want to see read-only. Is it clear that it h=
as been interpreted differently by different individuals.<o:p></o:p></span><=
/p><p class=3D"MsoPlainText"><span lang=3D"EN-US" style=3D"mso-ansi-language=
:EN-US"><o:p>&nbsp;</o:p></span></p><p class=3D"MsoPlainText"><span lang=3D"=
EN-US" style=3D"mso-ansi-language:EN-US">The authors and chairs have discuss=
ed the issue and we have a rough consensus that we want the MIB module(s) to=
 be read-only.<o:p></o:p></span></p><p class=3D"MsoPlainText"><span lang=3D"=
EN-US" style=3D"mso-ansi-language:EN-US"><o:p>&nbsp;</o:p></span></p><p clas=
s=3D"MsoPlainText"><span lang=3D"EN-US" style=3D"mso-ansi-language:EN-US">We=
 therefore are asking the working group if this is OK for the MIB<o:p></o:p>=
</span></p><p class=3D"MsoPlainText"><span lang=3D"EN-US" style=3D"mso-ansi-=
language:EN-US">module(s) in the current document. Please indicate Support o=
r Oppose for this MIB (draft-ietf-mpls-tp-te-mib) to be read-only.<o:p></o:p=
></span></p><p class=3D"MsoPlainText"><span lang=3D"EN-US" style=3D"mso-ansi=
-language:EN-US"><o:p>&nbsp;</o:p></span></p><p class=3D"MsoPlainText"><span=
 lang=3D"EN-US" style=3D"mso-ansi-language:EN-US">Please send your comments t=
o the working group mailing list before February 18, 2014.<o:p></o:p></span>=
</p><p class=3D"MsoPlainText"><span lang=3D"EN-US" style=3D"mso-ansi-languag=
e:EN-US"><o:p>&nbsp;</o:p></span></p><p class=3D"MsoPlainText"><span lang=3D=
"EN-US" style=3D"mso-ansi-language:EN-US">Loa<o:p></o:p></span></p><p class=3D=
"MsoPlainText"><span lang=3D"EN-US" style=3D"mso-ansi-language:EN-US">for th=
e MPLS wg chairs<o:p></o:p></span></p><p class=3D"MsoPlainText"><span lang=3D=
"EN-US" style=3D"mso-ansi-language:EN-US">-- <o:p></o:p></span></p><p class=3D=
"MsoPlainText"><span lang=3D"EN-US" style=3D"mso-ansi-language:EN-US"><o:p>&=
nbsp;</o:p></span></p><p class=3D"MsoPlainText"><span lang=3D"EN-US" style=3D=
"mso-ansi-language:EN-US"><o:p>&nbsp;</o:p></span></p><p class=3D"MsoPlainTe=
xt"><span lang=3D"EN-US" style=3D"mso-ansi-language:EN-US">Loa Andersson&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; email: <a href=3D=
"mailto:loa@mail01.huawei.com">loa@mail01.huawei.com</a><o:p></o:p></span></=
p><p class=3D"MsoPlainText"><span lang=3D"EN-US" style=3D"mso-ansi-language:=
EN-US">Senior MPLS Expert&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp; <a href=3D"mailto:loa@pi.nu">loa@pi.nu</a><o:p></o:p=
></span></p><p class=3D"MsoPlainText"><span lang=3D"EN-US" style=3D"mso-ansi=
-language:EN-US">Huawei Technologies (consultant)&nbsp;&nbsp;&nbsp;&nbsp; ph=
one: +46 739 81 21 64<o:p></o:p></span></p><p class=3D"MsoPlainText"><span l=
ang=3D"EN-US" style=3D"mso-ansi-language:EN-US">____________________________=
___________________<o:p></o:p></span></p><p class=3D"MsoPlainText"><span lan=
g=3D"EN-US" style=3D"mso-ansi-language:EN-US">mpls mailing list<o:p></o:p></=
span></p><p class=3D"MsoPlainText"><span lang=3D"EN-US" style=3D"mso-ansi-la=
nguage:EN-US"><a href=3D"mailto:mpls@ietf.org">mpls@ietf.org</a><o:p></o:p><=
/span></p><p class=3D"MsoPlainText"><span lang=3D"EN-US" style=3D"mso-ansi-l=
anguage:EN-US"><a href=3D"https://www.ietf.org/mailman/listinfo/mpls">https:=
//www.ietf.org/mailman/listinfo/mpls</a><o:p></o:p></span></p><p class=3D"Ms=
oPlainText"><span lang=3D"EN-US" style=3D"mso-ansi-language:EN-US">_________=
______________________________________<o:p></o:p></span></p><p class=3D"MsoP=
lainText"><span lang=3D"EN-US" style=3D"mso-ansi-language:EN-US">mpls mailin=
g list<o:p></o:p></span></p><p class=3D"MsoPlainText"><span lang=3D"EN-US" s=
tyle=3D"mso-ansi-language:EN-US"><a href=3D"mailto:mpls@ietf.org">mpls@ietf.=
org</a><o:p></o:p></span></p><p class=3D"MsoPlainText"><span lang=3D"EN-US" s=
tyle=3D"mso-ansi-language:EN-US"><a href=3D"https://www.ietf.org/mailman/lis=
tinfo/mpls">https://www.ietf.org/mailman/listinfo/mpls</a><o:p></o:p></span>=
</p><p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"mso-ansi-language:E=
N-US"><o:p>&nbsp;</o:p></span></p></div></div></div></blockquote><blockquote=
 type=3D"cite"><div><span>_______________________________________________</s=
pan><br><span>MIB-DOCTORS mailing list</span><br><span><a href=3D"mailto:MIB=
-DOCTORS@ietf.org">MIB-DOCTORS@ietf.org</a></span><br><span><a href=3D"https=
://www.ietf.org/mailman/listinfo/mib-doctors">https://www.ietf.org/mailman/l=
istinfo/mib-doctors</a></span><br></div></blockquote></body></html>=

--Apple-Mail-F0886F1A-E1B2-48A1-8186-78CEFEB577A8--


From jcucchiara@mindspring.com  Tue Feb  4 07:39:28 2014
Return-Path: <jcucchiara@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 122261A0196 for <mib-doctors@ietfa.amsl.com>; Tue,  4 Feb 2014 07:39:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 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, 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 ri3MmpWBjGqV for <mib-doctors@ietfa.amsl.com>; Tue,  4 Feb 2014 07:39:23 -0800 (PST)
Received: from elasmtp-kukur.atl.sa.earthlink.net (elasmtp-kukur.atl.sa.earthlink.net [209.86.89.65]) by ietfa.amsl.com (Postfix) with ESMTP id C65F41A0132 for <mib-doctors@ietf.org>; Tue,  4 Feb 2014 07:39:22 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=NURDnSr/mE51MZlaHyKfp9xU9d1sXcV2qtCnjsyiTmXA1W/CkE7+NCkRb5ydu+3j; h=Received:From:To:References:In-Reply-To:Subject:Date:Message-ID:MIME-Version:Content-Type:X-Mailer:Thread-Index:Content-language:X-ELNK-Trace:X-Originating-IP;
Received: from [24.41.69.138] (helo=JoanTower) by elasmtp-kukur.atl.sa.earthlink.net with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.67) (envelope-from <jcucchiara@mindspring.com>) id 1WAi5o-0005YH-V9; Tue, 04 Feb 2014 10:39:21 -0500
From: "Joan Cucchiara" <jcucchiara@mindspring.com>
To: <adrian@olddog.co.uk>, <mib-doctors@ietf.org>
References: <05c501cf21ad$80d97ef0$828c7cd0$@olddog.co.uk>
In-Reply-To: <05c501cf21ad$80d97ef0$828c7cd0$@olddog.co.uk>
Date: Tue, 4 Feb 2014 10:39:19 -0500
Message-ID: <00dc01cf21bf$45acdae0$d10690a0$@mindspring.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_00DD_01CF2195.5CD88090"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQFJjvDrKd3WqTHnQB+4M0ubo7RGRJuwWPSA
Content-language: en-us
X-ELNK-Trace: 4d68bbe9cb71969ea344cf2d1a8e60840a9da525759e26546b2372923ef1561f031332abb473e36c133ed92d71017c35350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 24.41.69.138
Subject: Re: [MIB-DOCTORS] Read-only MIB modules
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, 04 Feb 2014 15:39:28 -0000

This is a multipart message in MIME format.

------=_NextPart_000_00DD_01CF2195.5CD88090
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Adrian,

 

My understanding of RowStatus is that rows created by TE MIB which have
tables extended in draft-ietf-mpls-tp-te-mib will still be "allowed" to be
created using the RowStatus of the TE MIB.   (In other words, the RowStatus
object controls the row and extensions to this row, even if those extensions
are in a different MIB Module.)  Consider ,for example, changing RowStatus
to delete a row.   That will impact the entire row, even if parts of the
row's objects are in various MIB Modules.

 

I don't understand how the draft could truly be made read-only, unless
RowStatus is going to be redefined.  

 

Please note also, that this draft extends rows  for tables in  LSR MIB as
well as the TE MIB.    

 

Thanks,

  -Joan

 

 

 

From: MIB-DOCTORS [mailto:mib-doctors-bounces@ietf.org] On Behalf Of Adrian
Farrel
Sent: Tuesday, February 04, 2014 8:32 AM
To: mib-doctors@ietf.org
Subject: [MIB-DOCTORS] Read-only MIB modules

 

Hi,

 

The MPLS working group is testing the water to see whether one of its MIB
modules should be "reduced" to read-only. This is the document that
triggered my recent questions that led on to the draft advice you are
working on. The WG took the document back to make this decision.

 

You'll note below that we immediately have an implementation claim (not for
this doc, but for the modules it extends).

 

An interesting situation, I think.

 

A

 

From: mpls [mailto:mpls-bounces@ietf.org] On Behalf Of GyeRok Gwun (???)
Sent: 04 February 2014 09:57
To: 'mpls@ietf.org'
Cc: 'mpls-chairs@tools.ietf.org'; 'draft-ietf-mpls-tp-te-mib@tools.ietf.org'
Subject: Re: [mpls] seeking consensus on making draft-ietf-mpls-tp-te-mib
read- only

 

No/oppose to make as Read-only mib.

In our products we extensively use R/W object of TE mib. We also have
NMS/EMS that use TE read-write Objects

 

Best Regards

Gwun

 

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

From: mpls [mailto:mpls-bounces@ietf.org] On Behalf Of Loa Andersson

Sent: Monday, February 03, 2014 10:55 PM

To: mpls@ietf.org

Cc: mpls-chairs@tools.ietf.org; draft-ietf-mpls-tp-te-mib@tools.ietf.org

Subject: [mpls] seeking consensus on making draft-ietf-mpls-tp-te-mib read-
only

 

Working Group,

 

We have just recalled draft-ietf-mpls-tp-te-mib from the IESG to the working
group for more work. We have a series of comments that are mostly for
clarification. However the main reason for recalling the document is that
there is one point where we need to confirm working group consensus.

 

The IETF, the working group and the MIB Doctors are today very reluctant to
produce read-write MIB modules. The current draft is read-write for a few
objects, this is based on a consensus call for an earlier discussion,
however the consensus call was not clear. It can be taken to mean both that
we want to go with read-write objects and that we want to see read-only. Is
it clear that it has been interpreted differently by different individuals.

 

The authors and chairs have discussed the issue and we have a rough
consensus that we want the MIB module(s) to be read-only.

 

We therefore are asking the working group if this is OK for the MIB

module(s) in the current document. Please indicate Support or Oppose for
this MIB (draft-ietf-mpls-tp-te-mib) to be read-only.

 

Please send your comments to the working group mailing list before February
18, 2014.

 

Loa

for the MPLS wg chairs

-- 

 

 

Loa Andersson                        email: loa@mail01.huawei.com

Senior MPLS Expert                          loa@pi.nu

Huawei Technologies (consultant)     phone: +46 739 81 21 64

_______________________________________________

mpls mailing list

mpls@ietf.org

https://www.ietf.org/mailman/listinfo/mpls

_______________________________________________

mpls mailing list

mpls@ietf.org

https://www.ietf.org/mailman/listinfo/mpls

 


------=_NextPart_000_00DD_01CF2195.5CD88090
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=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Gulim;
	panose-1:2 11 6 0 0 1 1 1 1 1;}
@font-face
	{font-family:Gulim;
	panose-1:2 11 6 0 0 1 1 1 1 1;}
@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;}
@font-face
	{font-family:"\@Gulim";
	panose-1:2 11 6 0 0 1 1 1 1 1;}
@font-face
	{font-family:"Malgun Gothic";
	panose-1:2 11 5 3 2 0 0 2 0 4;}
@font-face
	{font-family:"\@Malgun Gothic";
	panose-1:2 11 5 3 2 0 0 2 0 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	text-align:justify;
	text-autospace:none;
	word-break:break-all;
	font-size:10.0pt;
	font-family:"Malgun Gothic","sans-serif";
	mso-fareast-language:KO;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	text-autospace:none;
	word-break:break-all;
	font-size:10.0pt;
	font-family:"Courier New";
	mso-fareast-language:KO;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	text-align:justify;
	text-autospace:none;
	word-break:break-all;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";
	mso-fareast-language:KO;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;
	mso-fareast-language:KO;}
span.Char
	{mso-style-name:"\AE00\C790\B9CC Char";
	mso-style-priority:99;
	mso-style-link:\AE00\C790\B9CC;
	font-family:"Courier New";}
p.a, li.a, div.a
	{mso-style-name:\AE00\C790\B9CC;
	mso-style-link:"\AE00\C790\B9CC Char";
	margin:0in;
	margin-bottom:.0001pt;
	text-align:justify;
	text-autospace:none;
	word-break:break-all;
	font-size:10.0pt;
	font-family:"Malgun Gothic","sans-serif";
	mso-fareast-language:KO;}
span.EmailStyle21
	{mso-style-type:personal;
	font-family:"Malgun Gothic","sans-serif";
	color:windowtext;}
span.EmailStyle22
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";
	mso-fareast-language:KO;}
span.EmailStyle25
	{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:8.5in 11.0in;
	margin:85.05pt 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></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 lang=3DEN-US =
link=3D"#0563C1" vlink=3D"#954F72"><div class=3DWordSection1><p =
class=3DMsoNormal style=3D'word-break:normal'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Adrian,<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'word-break:normal'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal =
style=3D'word-break:normal'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>My understanding of RowStatus is that rows created by TE MIB which =
have tables extended in draft-ietf-mpls-tp-te-mib will still be =
&#8220;allowed&#8221; to be created using the RowStatus of the TE =
MIB.&nbsp;&nbsp; (In other words, the RowStatus object controls the row =
and extensions to this row, even if those extensions are in a different =
MIB Module.)&nbsp; Consider ,for example, changing RowStatus to delete a =
row.&nbsp;&nbsp; That will impact the entire row, even if parts of the =
row&#8217;s objects are in various MIB Modules.<o:p></o:p></span></p><p =
class=3DMsoNormal style=3D'word-break:normal'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal =
style=3D'word-break:normal'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>I don&#8217;t understand how the draft could truly be made read-only, =
unless RowStatus is going to be redefined.&nbsp; =
<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'word-break:normal'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal =
style=3D'word-break:normal'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Please note also, that this draft extends rows &nbsp;for tables in =
&nbsp;LSR MIB as well as the TE MIB.&nbsp;&nbsp; =
&nbsp;<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'word-break:normal'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal =
style=3D'word-break:normal'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Thanks,<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'word-break:normal'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp; -Joan<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'word-break:normal'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal =
style=3D'word-break:normal'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal =
style=3D'word-break:normal'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><div><div =
style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in'><p class=3DMsoNormal align=3Dleft =
style=3D'text-align:left;text-autospace:ideograph-numeric =
ideograph-other;word-break:normal'><b><span =
style=3D'font-family:"Tahoma","sans-serif";mso-fareast-language:EN-US'>Fr=
om:</span></b><span =
style=3D'font-family:"Tahoma","sans-serif";mso-fareast-language:EN-US'> =
MIB-DOCTORS [mailto:mib-doctors-bounces@ietf.org] <b>On Behalf Of =
</b>Adrian Farrel<br><b>Sent:</b> Tuesday, February 04, 2014 8:32 =
AM<br><b>To:</b> mib-doctors@ietf.org<br><b>Subject:</b> [MIB-DOCTORS] =
Read-only MIB modules<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal align=3Dleft =
style=3D'text-align:left'><o:p>&nbsp;</o:p></p><p class=3DMsoNormal =
style=3D'word-break:normal'><span lang=3DEN-GB =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Hi,<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'word-break:normal'><span lang=3DEN-GB =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal =
style=3D'word-break:normal'><span lang=3DEN-GB =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>The MPLS working group is testing the water to see whether one of its =
MIB modules should be &quot;reduced&quot; to read-only. This is the =
document that triggered my recent questions that led on to the draft =
advice you are working on. The WG took the document back to make this =
decision.<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'word-break:normal'><span lang=3DEN-GB =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal =
style=3D'word-break:normal'><span lang=3DEN-GB =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>You'll note below that we immediately have an implementation claim =
(not for this doc, but for the modules it =
extends).<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'word-break:normal'><span lang=3DEN-GB =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal =
style=3D'word-break:normal'><span lang=3DEN-GB =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>An interesting situation, I think.<o:p></o:p></span></p><p =
class=3DMsoNormal style=3D'word-break:normal'><span lang=3DEN-GB =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal =
style=3D'word-break:normal'><span lang=3DEN-GB =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>A<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'word-break:normal'><span lang=3DEN-GB =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal align=3Dleft =
style=3D'text-align:left;text-autospace:ideograph-other;word-break:normal=
'><b><span =
style=3D'font-family:"Tahoma","sans-serif"'>From:</span></b><span =
style=3D'font-family:"Tahoma","sans-serif"'> mpls =
[mailto:mpls-bounces@ietf.org] <b>On Behalf Of </b>GyeRok Gwun =
(???)<br><b>Sent:</b> 04 February 2014 09:57<br><b>To:</b> =
'mpls@ietf.org'<br><b>Cc:</b> 'mpls-chairs@tools.ietf.org'; =
'draft-ietf-mpls-tp-te-mib@tools.ietf.org'<br><b>Subject:</b> Re: [mpls] =
seeking consensus on making draft-ietf-mpls-tp-te-mib read- =
only<o:p></o:p></span></p></div></div><p class=3DMsoNormal align=3Dleft =
style=3D'text-align:left'><span =
lang=3DEN-GB><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText>No/oppose to make as Read-only =
mib.<o:p></o:p></p><p class=3DMsoPlainText>In our products we =
extensively use R/W object of TE mib. We also have NMS/EMS that use TE =
read-write Objects<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText>Best =
Regards<o:p></o:p></p><p class=3DMsoPlainText>Gwun<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>-----Original Message-----<o:p></o:p></p><p =
class=3DMsoPlainText>From: mpls [<a =
href=3D"mailto:mpls-bounces@ietf.org">mailto:mpls-bounces@ietf.org</a>] =
On Behalf Of Loa Andersson<o:p></o:p></p><p class=3DMsoPlainText>Sent: =
Monday, February 03, 2014 10:55 PM<o:p></o:p></p><p =
class=3DMsoPlainText>To: <a =
href=3D"mailto:mpls@ietf.org">mpls@ietf.org</a><o:p></o:p></p><p =
class=3DMsoPlainText>Cc: <a =
href=3D"mailto:mpls-chairs@tools.ietf.org">mpls-chairs@tools.ietf.org</a>=
; <a =
href=3D"mailto:draft-ietf-mpls-tp-te-mib@tools.ietf.org">draft-ietf-mpls-=
tp-te-mib@tools.ietf.org</a><o:p></o:p></p><p =
class=3DMsoPlainText>Subject: [mpls] seeking consensus on making =
draft-ietf-mpls-tp-te-mib read- only<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>Working Group,<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText>We =
have just recalled draft-ietf-mpls-tp-te-mib from the IESG to the =
working group for more work. We have a series of comments that are =
mostly for clarification. However the main reason for recalling the =
document is that there is one point where we need to confirm working =
group consensus.<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText>The =
IETF, the working group and the MIB Doctors are today very reluctant to =
produce read-write MIB modules. The current draft is read-write for a =
few objects, this is based on a consensus call for an earlier =
discussion, however the consensus call was not clear. It can be taken to =
mean both that we want to go with read-write objects and that we want to =
see read-only. Is it clear that it has been interpreted differently by =
different individuals.<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText>The =
authors and chairs have discussed the issue and we have a rough =
consensus that we want the MIB module(s) to be =
read-only.<o:p></o:p></p><p class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>We therefore are asking the working group if this =
is OK for the MIB<o:p></o:p></p><p class=3DMsoPlainText>module(s) in the =
current document. Please indicate Support or Oppose for this MIB =
(draft-ietf-mpls-tp-te-mib) to be read-only.<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText>Please =
send your comments to the working group mailing list before February 18, =
2014.<o:p></o:p></p><p class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>Loa<o:p></o:p></p><p class=3DMsoPlainText>for the =
MPLS wg chairs<o:p></o:p></p><p class=3DMsoPlainText>-- =
<o:p></o:p></p><p class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText>Loa =
Andersson&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
; email: <a =
href=3D"mailto:loa@mail01.huawei.com">loa@mail01.huawei.com</a><o:p></o:p=
></p><p class=3DMsoPlainText>Senior MPLS =
Expert&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp; <a href=3D"mailto:loa@pi.nu">loa@pi.nu</a><o:p></o:p></p><p =
class=3DMsoPlainText>Huawei Technologies =
(consultant)&nbsp;&nbsp;&nbsp;&nbsp; phone: +46 739 81 21 =
64<o:p></o:p></p><p =
class=3DMsoPlainText>_______________________________________________<o:p>=
</o:p></p><p class=3DMsoPlainText>mpls mailing list<o:p></o:p></p><p =
class=3DMsoPlainText><a =
href=3D"mailto:mpls@ietf.org">mpls@ietf.org</a><o:p></o:p></p><p =
class=3DMsoPlainText><a =
href=3D"https://www.ietf.org/mailman/listinfo/mpls">https://www.ietf.org/=
mailman/listinfo/mpls</a><o:p></o:p></p><p =
class=3DMsoPlainText>_______________________________________________<o:p>=
</o:p></p><p class=3DMsoPlainText>mpls mailing list<o:p></o:p></p><p =
class=3DMsoPlainText><a =
href=3D"mailto:mpls@ietf.org">mpls@ietf.org</a><o:p></o:p></p><p =
class=3DMsoPlainText><a =
href=3D"https://www.ietf.org/mailman/listinfo/mpls">https://www.ietf.org/=
mailman/listinfo/mpls</a><o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div></body></html>
------=_NextPart_000_00DD_01CF2195.5CD88090--


From adrian@olddog.co.uk  Tue Feb  4 13:07:31 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 E31D61A010F for <mib-doctors@ietfa.amsl.com>; Tue,  4 Feb 2014 13:07:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, 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 tmjgADZ9QbvM for <mib-doctors@ietfa.amsl.com>; Tue,  4 Feb 2014 13:07:26 -0800 (PST)
Received: from asmtp4.iomartmail.com (asmtp4.iomartmail.com [62.128.201.175]) by ietfa.amsl.com (Postfix) with ESMTP id 7ED361A00EC for <mib-doctors@ietf.org>; Tue,  4 Feb 2014 13:07:25 -0800 (PST)
Received: from asmtp4.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id s14L7NXt032633; Tue, 4 Feb 2014 21:07:23 GMT
Received: from 950129200 (p57B2DC5C.dip0.t-ipconnect.de [87.178.220.92]) (authenticated bits=0) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id s14L7Mie032620 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 4 Feb 2014 21:07:22 GMT
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Joan Cucchiara'" <jcucchiara@mindspring.com>, <mib-doctors@ietf.org>
References: <05c501cf21ad$80d97ef0$828c7cd0$@olddog.co.uk> <00dc01cf21bf$45acdae0$d10690a0$@mindspring.com>
In-Reply-To: <00dc01cf21bf$45acdae0$d10690a0$@mindspring.com>
Date: Tue, 4 Feb 2014 21:07:20 -0000
Message-ID: <06e001cf21ed$1813a4a0$483aede0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_06E1_01CF21ED.18170000"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQFJjvDrKd3WqTHnQB+4M0ubo7RGRAFy1q1Jm6UkTOA=
Content-Language: en-gb
X-TM-AS-MML: No
Subject: Re: [MIB-DOCTORS] Read-only MIB modules
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: Tue, 04 Feb 2014 21:07:31 -0000

This is a multipart message in MIME format.

------=_NextPart_000_06E1_01CF21ED.18170000
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hello,
 
I thought that a compliance statement for this MIB module would require only
read access for the extended tables, and that all objects in this module would
be read-only.
 
A
 
From: Joan Cucchiara [mailto:jcucchiara@mindspring.com] 
Sent: 04 February 2014 15:39
To: adrian@olddog.co.uk; mib-doctors@ietf.org
Subject: RE: [MIB-DOCTORS] Read-only MIB modules
 
Adrian,
 
My understanding of RowStatus is that rows created by TE MIB which have tables
extended in draft-ietf-mpls-tp-te-mib will still be "allowed" to be created
using the RowStatus of the TE MIB.   (In other words, the RowStatus object
controls the row and extensions to this row, even if those extensions are in a
different MIB Module.)  Consider ,for example, changing RowStatus to delete a
row.   That will impact the entire row, even if parts of the row's objects are
in various MIB Modules.
 
I don't understand how the draft could truly be made read-only, unless RowStatus
is going to be redefined.  
 
Please note also, that this draft extends rows  for tables in  LSR MIB as well
as the TE MIB.    
 
Thanks,
  -Joan
 
 
 
From: MIB-DOCTORS [mailto:mib-doctors-bounces@ietf.org] On Behalf Of Adrian
Farrel
Sent: Tuesday, February 04, 2014 8:32 AM
To: mib-doctors@ietf.org
Subject: [MIB-DOCTORS] Read-only MIB modules
 
Hi,
 
The MPLS working group is testing the water to see whether one of its MIB
modules should be "reduced" to read-only. This is the document that triggered my
recent questions that led on to the draft advice you are working on. The WG took
the document back to make this decision.
 
You'll note below that we immediately have an implementation claim (not for this
doc, but for the modules it extends).
 
An interesting situation, I think.
 
A
 
From: mpls [mailto:mpls-bounces@ietf.org] On Behalf Of GyeRok Gwun (???)
Sent: 04 February 2014 09:57
To: 'mpls@ietf.org'
Cc: 'mpls-chairs@tools.ietf.org'; 'draft-ietf-mpls-tp-te-mib@tools.ietf.org'
Subject: Re: [mpls] seeking consensus on making draft-ietf-mpls-tp-te-mib read-
only
 
No/oppose to make as Read-only mib.
In our products we extensively use R/W object of TE mib. We also have NMS/EMS
that use TE read-write Objects
 
Best Regards
Gwun
 
-----Original Message-----
From: mpls [mailto:mpls-bounces@ietf.org] On Behalf Of Loa Andersson
Sent: Monday, February 03, 2014 10:55 PM
To: mpls@ietf.org
Cc: mpls-chairs@tools.ietf.org; draft-ietf-mpls-tp-te-mib@tools.ietf.org
Subject: [mpls] seeking consensus on making draft-ietf-mpls-tp-te-mib read- only
 
Working Group,
 
We have just recalled draft-ietf-mpls-tp-te-mib from the IESG to the working
group for more work. We have a series of comments that are mostly for
clarification. However the main reason for recalling the document is that there
is one point where we need to confirm working group consensus.
 
The IETF, the working group and the MIB Doctors are today very reluctant to
produce read-write MIB modules. The current draft is read-write for a few
objects, this is based on a consensus call for an earlier discussion, however
the consensus call was not clear. It can be taken to mean both that we want to
go with read-write objects and that we want to see read-only. Is it clear that
it has been interpreted differently by different individuals.
 
The authors and chairs have discussed the issue and we have a rough consensus
that we want the MIB module(s) to be read-only.
 
We therefore are asking the working group if this is OK for the MIB
module(s) in the current document. Please indicate Support or Oppose for this
MIB (draft-ietf-mpls-tp-te-mib) to be read-only.
 
Please send your comments to the working group mailing list before February 18,
2014.
 
Loa
for the MPLS wg chairs
-- 
 
 
Loa Andersson                        email: loa@mail01.huawei.com
Senior MPLS Expert                          loa@pi.nu
Huawei Technologies (consultant)     phone: +46 739 81 21 64
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls
 

------=_NextPart_000_06E1_01CF21ED.18170000
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@01CF21EC.93AF2040"><!--[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: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;}
@font-face
	{font-family:"Malgun Gothic";
	panose-1:2 11 5 3 2 0 0 2 0 4;
	mso-font-charset:129;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:-1879047505 165117179 18 0 524289 0;}
@font-face
	{font-family:"\@Malgun Gothic";
	panose-1:2 11 5 3 2 0 0 2 0 4;
	mso-font-charset:129;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:-1879047505 165117179 18 0 524289 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;
	text-align:justify;
	mso-pagination:widow-orphan;
	text-autospace:none;
	word-break:break-all;
	font-size:10.0pt;
	font-family:"Malgun Gothic","sans-serif";
	mso-bidi-font-family:"Times New Roman";
	mso-fareast-language:KO;}
a:link, span.MsoHyperlink
	{mso-style-noshow:yes;
	mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;
	text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-noshow:yes;
	mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;
	text-underline:single;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-noshow:yes;
	mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	text-autospace:none;
	word-break:break-all;
	font-size:10.0pt;
	font-family:"Courier New","serif";
	mso-fareast-font-family:Calibri;
	mso-fareast-language:KO;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-noshow:yes;
	mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	mso-pagination:widow-orphan;
	text-autospace:none;
	word-break:break-all;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";
	mso-fareast-font-family:Calibri;
	mso-fareast-language:KO;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-noshow:yes;
	mso-style-priority:99;
	mso-style-unhide:no;
	mso-style-locked:yes;
	mso-style-link:"Plain Text";
	font-family:Consolas;
	mso-ascii-font-family:Consolas;
	mso-hansi-font-family:Consolas;
	mso-bidi-font-family:Consolas;
	mso-fareast-language:KO;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-noshow:yes;
	mso-style-priority:99;
	mso-style-unhide:no;
	mso-style-locked:yes;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";
	mso-ascii-font-family:Tahoma;
	mso-hansi-font-family:Tahoma;
	mso-bidi-font-family:Tahoma;
	mso-fareast-language:KO;}
span.Char
	{mso-style-name:"\AE00\C790\B9CC Char";
	mso-style-priority:99;
	mso-style-unhide:no;
	mso-style-locked:yes;
	mso-style-link:\AE00\C790\B9CC;
	font-family:"Courier New","serif";
	mso-ascii-font-family:"Courier New";
	mso-hansi-font-family:"Courier New";
	mso-bidi-font-family:"Courier New";}
p.a, li.a, div.a
	{mso-style-name:\AE00\C790\B9CC;
	mso-style-unhide:no;
	mso-style-link:"\AE00\C790\B9CC Char";
	margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	mso-pagination:widow-orphan;
	text-autospace:none;
	word-break:break-all;
	font-size:10.0pt;
	font-family:"Malgun Gothic","sans-serif";
	mso-bidi-font-family:"Times New Roman";
	mso-fareast-language:KO;}
span.EmailStyle23
	{mso-style-type:personal;
	mso-style-noshow:yes;
	mso-style-unhide:no;
	font-family:"Malgun Gothic","sans-serif";
	mso-ascii-font-family:"Malgun Gothic";
	mso-fareast-font-family:"Malgun Gothic";
	mso-hansi-font-family:"Malgun Gothic";
	color:windowtext;}
span.EmailStyle24
	{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.EmailStyle25
	{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.EmailStyle26
	{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:3.0cm 72.0pt 72.0pt 72.0pt;
	mso-header-margin:36.0pt;
	mso-footer-margin:36.0pt;
	mso-paper-source:0;}
div.WordSection1
	{page:WordSection1;}
--></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 lang=3DEN-GB =
link=3D"#0563C1" vlink=3D"#954F72" style=3D'tab-interval:36.0pt'><div =
class=3DWordSection1><p class=3DMsoNormal =
style=3D'word-break:normal'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-fareast-=
font-family:Calibri;mso-bidi-font-family:"Times New =
Roman";color:#1F497D'>Hello,<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'word-break:normal'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-fareast-=
font-family:Calibri;mso-bidi-font-family:"Times New =
Roman";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal =
style=3D'word-break:normal'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-fareast-=
font-family:Calibri;mso-bidi-font-family:"Times New =
Roman";color:#1F497D'>I thought that a compliance statement for this MIB =
module would require only read access for the extended tables, and that =
all objects in this module would be read-only.<o:p></o:p></span></p><p =
class=3DMsoNormal style=3D'word-break:normal'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-fareast-=
font-family:Calibri;mso-bidi-font-family:"Times New =
Roman";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal =
style=3D'word-break:normal'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-fareast-=
font-family:Calibri;mso-bidi-font-family:"Times New =
Roman";color:#1F497D'>A<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'word-break:normal'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-fareast-=
font-family:Calibri;mso-bidi-font-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 align=3Dleft =
style=3D'text-align:left;text-autospace:ideograph-numeric =
ideograph-other;word-break:normal'><b><span lang=3DEN-US =
style=3D'font-family:"Tahoma","sans-serif";mso-fareast-font-family:"Times=
 New =
Roman";mso-ansi-language:EN-US;mso-fareast-language:EN-GB'>From:</span></=
b><span lang=3DEN-US =
style=3D'font-family:"Tahoma","sans-serif";mso-fareast-font-family:"Times=
 New Roman";mso-ansi-language:EN-US;mso-fareast-language:EN-GB'> Joan =
Cucchiara [mailto:jcucchiara@mindspring.com] <br><b>Sent:</b> 04 =
February 2014 15:39<br><b>To:</b> adrian@olddog.co.uk; =
mib-doctors@ietf.org<br><b>Subject:</b> RE: [MIB-DOCTORS] Read-only MIB =
modules<o:p></o:p></span></p></div></div><p class=3DMsoNormal =
align=3Dleft style=3D'text-align:left'><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal style=3D'word-break:normal'><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D;mso-ansi-language:EN-US'>Adrian,<o:p></o:p></span></p><p =
class=3DMsoNormal style=3D'word-break:normal'><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 style=3D'word-break:normal'><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D;mso-ansi-language:EN-US'>My understanding of RowStatus is that rows =
created by TE MIB which have tables extended in =
draft-ietf-mpls-tp-te-mib will still be &#8220;allowed&#8221; to be =
created using the RowStatus of the TE MIB.&nbsp;&nbsp; (In other words, =
the RowStatus object controls the row and extensions to this row, even =
if those extensions are in a different MIB Module.)&nbsp; Consider ,for =
example, changing RowStatus to delete a row.&nbsp;&nbsp; That will =
impact the entire row, even if parts of the row&#8217;s objects are in =
various MIB Modules.<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'word-break:normal'><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 style=3D'word-break:normal'><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D;mso-ansi-language:EN-US'>I don&#8217;t understand how the draft could =
truly be made read-only, unless RowStatus is going to be =
redefined.&nbsp; <o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'word-break:normal'><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 style=3D'word-break:normal'><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D;mso-ansi-language:EN-US'>Please note also, that this draft extends =
rows &nbsp;for tables in &nbsp;LSR MIB as well as the TE =
MIB.&nbsp;&nbsp; &nbsp;<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'word-break:normal'><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 style=3D'word-break:normal'><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D;mso-ansi-language:EN-US'>Thanks,<o:p></o:p></span></p><p =
class=3DMsoNormal style=3D'word-break:normal'><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D;mso-ansi-language:EN-US'>&nbsp; -Joan<o:p></o:p></span></p><p =
class=3DMsoNormal style=3D'word-break:normal'><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 style=3D'word-break:normal'><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 style=3D'word-break:normal'><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><div =
style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm'><p class=3DMsoNormal align=3Dleft =
style=3D'text-align:left;text-autospace:ideograph-other;word-break:normal=
'><b><span lang=3DEN-US =
style=3D'font-family:"Tahoma","sans-serif";mso-ansi-language:EN-US;mso-fa=
reast-language:EN-US'>From:</span></b><span lang=3DEN-US =
style=3D'font-family:"Tahoma","sans-serif";mso-ansi-language:EN-US;mso-fa=
reast-language:EN-US'> MIB-DOCTORS [mailto:mib-doctors-bounces@ietf.org] =
<b>On Behalf Of </b>Adrian Farrel<br><b>Sent:</b> Tuesday, February 04, =
2014 8:32 AM<br><b>To:</b> mib-doctors@ietf.org<br><b>Subject:</b> =
[MIB-DOCTORS] Read-only MIB modules<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal align=3Dleft style=3D'text-align:left'><span =
lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal style=3D'word-break:normal'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Hi,<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'word-break:normal'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal =
style=3D'word-break:normal'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>The MPLS working group is testing the water to see whether one of its =
MIB modules should be &quot;reduced&quot; to read-only. This is the =
document that triggered my recent questions that led on to the draft =
advice you are working on. The WG took the document back to make this =
decision.<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'word-break:normal'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal =
style=3D'word-break:normal'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>You'll note below that we immediately have an implementation claim =
(not for this doc, but for the modules it =
extends).<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'word-break:normal'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal =
style=3D'word-break:normal'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>An interesting situation, I think.<o:p></o:p></span></p><p =
class=3DMsoNormal style=3D'word-break:normal'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal =
style=3D'word-break:normal'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>A<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'word-break:normal'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><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 align=3Dleft =
style=3D'text-align:left;text-autospace:ideograph-other;word-break:normal=
'><b><span lang=3DEN-US =
style=3D'font-family:"Tahoma","sans-serif";mso-ansi-language:EN-US'>From:=
</span></b><span lang=3DEN-US =
style=3D'font-family:"Tahoma","sans-serif";mso-ansi-language:EN-US'> =
mpls [mailto:mpls-bounces@ietf.org] <b>On Behalf Of </b>GyeRok Gwun =
(???)<br><b>Sent:</b> 04 February 2014 09:57<br><b>To:</b> =
'mpls@ietf.org'<br><b>Cc:</b> 'mpls-chairs@tools.ietf.org'; =
'draft-ietf-mpls-tp-te-mib@tools.ietf.org'<br><b>Subject:</b> Re: [mpls] =
seeking consensus on making draft-ietf-mpls-tp-te-mib read- =
only<o:p></o:p></span></p></div></div><p class=3DMsoNormal align=3Dleft =
style=3D'text-align:left'><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>No/oppose to make as Read-only =
mib.<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>In our products we extensively use R/W =
object of TE mib. We also have NMS/EMS that use TE read-write =
Objects<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>Best Regards<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>Gwun<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>-----Original =
Message-----<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US style=3D'mso-ansi-language:EN-US'>From: mpls [<a =
href=3D"mailto:mpls-bounces@ietf.org">mailto:mpls-bounces@ietf.org</a>] =
On Behalf Of Loa Andersson<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>Sent: Monday, February 03, 2014 10:55 =
PM<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>To: <a =
href=3D"mailto:mpls@ietf.org">mpls@ietf.org</a><o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>Cc: <a =
href=3D"mailto:mpls-chairs@tools.ietf.org">mpls-chairs@tools.ietf.org</a>=
; <a =
href=3D"mailto:draft-ietf-mpls-tp-te-mib@tools.ietf.org">draft-ietf-mpls-=
tp-te-mib@tools.ietf.org</a><o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>Subject: [mpls] seeking consensus on =
making draft-ietf-mpls-tp-te-mib read- only<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>Working Group,<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>We have just recalled =
draft-ietf-mpls-tp-te-mib from the IESG to the working group for more =
work. We have a series of comments that are mostly for clarification. =
However the main reason for recalling the document is that there is one =
point where we need to confirm working group =
consensus.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>The IETF, the working group and the =
MIB Doctors are today very reluctant to produce read-write MIB modules. =
The current draft is read-write for a few objects, this is based on a =
consensus call for an earlier discussion, however the consensus call was =
not clear. It can be taken to mean both that we want to go with =
read-write objects and that we want to see read-only. Is it clear that =
it has been interpreted differently by different =
individuals.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>The authors and chairs have discussed =
the issue and we have a rough consensus that we want the MIB module(s) =
to be read-only.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>We therefore are asking the working =
group if this is OK for the MIB<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>module(s) in the current document. =
Please indicate Support or Oppose for this MIB =
(draft-ietf-mpls-tp-te-mib) to be read-only.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>Please send your comments to the =
working group mailing list before February 18, =
2014.<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>Loa<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>for the MPLS wg =
chairs<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>-- <o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>Loa =
Andersson&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
; email: <a =
href=3D"mailto:loa@mail01.huawei.com">loa@mail01.huawei.com</a><o:p></o:p=
></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>Senior MPLS =
Expert&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp; <a =
href=3D"mailto:loa@pi.nu">loa@pi.nu</a><o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>Huawei Technologies =
(consultant)&nbsp;&nbsp;&nbsp;&nbsp; phone: +46 739 81 21 =
64<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>_______________________________________=
________<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>mpls mailing =
list<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'><a =
href=3D"mailto:mpls@ietf.org">mpls@ietf.org</a><o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'><a =
href=3D"https://www.ietf.org/mailman/listinfo/mpls">https://www.ietf.org/=
mailman/listinfo/mpls</a><o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>_______________________________________=
________<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>mpls mailing =
list<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'><a =
href=3D"mailto:mpls@ietf.org">mpls@ietf.org</a><o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'><a =
href=3D"https://www.ietf.org/mailman/listinfo/mpls">https://www.ietf.org/=
mailman/listinfo/mpls</a><o:p></o:p></span></p><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_06E1_01CF21ED.18170000--



From j.schoenwaelder@jacobs-university.de  Tue Feb  4 14:42:27 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 B83291A0126 for <mib-doctors@ietfa.amsl.com>; Tue,  4 Feb 2014 14:42:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.785
X-Spam-Level: 
X-Spam-Status: No, score=-2.785 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.535] 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 j1IyOzkflZqB for <mib-doctors@ietfa.amsl.com>; Tue,  4 Feb 2014 14:42:26 -0800 (PST)
Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) by ietfa.amsl.com (Postfix) with ESMTP id 12F4C1A0032 for <mib-doctors@ietf.org>; Tue,  4 Feb 2014 14:42:26 -0800 (PST)
Received: from localhost (demetrius1.jacobs-university.de [212.201.44.46]) by hermes.jacobs-university.de (Postfix) with ESMTP id 5C10620120; Tue,  4 Feb 2014 23:42:25 +0100 (CET)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius1.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id GwsCW7rXTau4; Tue,  4 Feb 2014 23:42:25 +0100 (CET)
Received: from elstar.local (elstar.jacobs.jacobs-university.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id B7F35200DF; Tue,  4 Feb 2014 23:42:24 +0100 (CET)
Received: by elstar.local (Postfix, from userid 501) id C45042B0E620; Tue,  4 Feb 2014 23:42:22 +0100 (CET)
Date: Tue, 4 Feb 2014 23:42:22 +0100
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: Adrian Farrel <adrian@olddog.co.uk>
Message-ID: <20140204224220.GA44274@elstar.local>
Mail-Followup-To: Adrian Farrel <adrian@olddog.co.uk>, 'Joan Cucchiara' <jcucchiara@mindspring.com>, mib-doctors@ietf.org
References: <05c501cf21ad$80d97ef0$828c7cd0$@olddog.co.uk> <00dc01cf21bf$45acdae0$d10690a0$@mindspring.com> <06e001cf21ed$1813a4a0$483aede0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <06e001cf21ed$1813a4a0$483aede0$@olddog.co.uk>
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: mib-doctors@ietf.org
Subject: Re: [MIB-DOCTORS] Read-only MIB modules
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: Tue, 04 Feb 2014 22:42:27 -0000

On Tue, Feb 04, 2014 at 09:07:20PM +0000, Adrian Farrel wrote:
> Hello,
>  
> I thought that a compliance statement for this MIB module would
> require only read access for the extended tables, and that all
> objects in this module would be read-only.

Sounds backwards from the SMIv2's notion of MAX-ACCESS. If you set
MAX-ACCESS to read-only, then this thing can never be implemented
read-write or read-create. This is why at some time in the past we
started modeling MAX-ACCESS read-write with read-only conformance
statements if a WG decides to do so and everyone could implement
read-only and still claim compliance.

We learned that it is a good thing to separate configuration from
operational state and it used to be a WG decision whether the WG wants
to tackle configuration via SNMP or not. I believe WGs need to take
informed decisions and we should help them with that but be careful
with 'strongly discouraging' writable SNMP MIB modules for
configuration purposes (unless there is some evidence that WGs are
unable to take informed decisions).

/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 bclaise@cisco.com  Wed Feb  5 06:13:20 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 2D48D1A0147 for <mib-doctors@ietfa.amsl.com>; Wed,  5 Feb 2014 06:13:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.035
X-Spam-Level: 
X-Spam-Status: No, score=-15.035 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, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.535, 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 eLJvN0_2_IkV for <mib-doctors@ietfa.amsl.com>; Wed,  5 Feb 2014 06:13:17 -0800 (PST)
Received: from mtv-iport-1.cisco.com (mtv-iport-1.cisco.com [173.36.130.12]) by ietfa.amsl.com (Postfix) with ESMTP id 0D6421A015D for <mib-doctors@ietf.org>; Wed,  5 Feb 2014 06:13:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5895; q=dns/txt; s=iport; t=1391609596; x=1392819196; h=message-id:date:from:mime-version:to:subject:references: in-reply-to; bh=ft3+5cPnE9nt0j92fkV4chuJwR8nX69afS4ltzfDIs8=; b=NBcFlJAw+gpK2FRVDBUTCBpbsjR1h5DZMhKo/tHdv35pxjOn5HUyvjcd 0Kskd5bucpwR1zZF07pCEWcexhwJiPnk9GHQ8DaxaUbk2ax8TrPwm+0Od zIod3soH/uQd79xdFN2QjfOlQ+mgT+Ll/ikXOyYTO5btDl/2/pBb8KG9s I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AksKAJNF8lKrRDoG/2dsb2JhbABZgwy4M4QZgwaBDhZ0giUBAQEEeBELBBQJFg8JAwIBAgFFBgEMCAEBiADPRheOExEBV4Q4BIlJjmKGSItZg04bgTU
X-IronPort-AV: E=Sophos;i="4.95,786,1384300800";  d="scan'208,217";a="101653603"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by mtv-iport-1.cisco.com with ESMTP; 05 Feb 2014 14:13:16 +0000
Received: from [10.21.70.50] ([10.21.70.50]) by mtv-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id s15EDFZX022205; Wed, 5 Feb 2014 14:13:15 GMT
Message-ID: <52F246FB.8010403@cisco.com>
Date: Wed, 05 Feb 2014 06:13:15 -0800
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: adrian@olddog.co.uk, "'Bert Wijnen (IETF)'" <bertietf@bwijnen.net>, "'Thomas Nadeau'" <tnadeau@lucidvision.com>, "'Romascanu, Dan (Dan)'" <dromasca@avaya.com>, "'MIB Doctors (E-mail)'" <mib-doctors@ietf.org>
References: <52DD5FFC.8070103@cisco.com> <20140121094726.GB47210@elstar.local> <9904FB1B0159DA42B0B887B7FA8119CA243D33C0@AZ-FFEXMB04.global.avaya.com> <FE705A2D-F9F0-4A41-A992-36705527C24A@lucidvision.com> <9904FB1B0159DA42B0B887B7FA8119CA243D3C0F@AZ-FFEXMB04.global.avaya.com> <556BB556-669F-4EF5-B8B0-4F1CD7E45BD0@lucidvision.com> <52DE928D.1090909@bwijnen.net> <0b2301cf16ce$bad3a3e0$307aeba0$@olddog.co.uk> <52DF9D02.6070306@cisco.com> <52EE4EF1.3000102@cisco.com> <20140202144457.GA35917@elstar.local>
In-Reply-To: <20140202144457.GA35917@elstar.local>
Content-Type: multipart/alternative; boundary="------------000909040409080101060508"
Subject: Re: [MIB-DOCTORS] Why is this MIB module read-write?
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: Wed, 05 Feb 2014 14:13:20 -0000

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

On 2/02/2014 06:44, Juergen Schoenwaelder wrote:
> On Sun, Feb 02, 2014 at 02:58:09PM +0100, Benoit Claise wrote:
>> Mib doctors,
>>
>> It's time to improve the following statement, to propose it to the
>> OPS area, and if all goes well o make an IESG statement out of it.
>>
>>     "The OPS Area henceforth strongly discourages the pursuit of
>>     writable SNMP MIBs for configuration purposes by working groups
>>     except in cases of clear utility and overwhelming consensus to do
>>     so. In all other cases, we recommend the use of NETCONF/YANG IETF
>>     standards for configuration, specifically in new charters."
>>
>> I re-read the email thread, and want to make the following changes:
>> - Add IETF. It was mentioned that some other SDOs might still be
>> using SNMP for configuration: IEEE, DOCSIS
>> - Add "for complete features or services" configuration. I want to
>> address Chirs' point that SNMPSet for starting an action might be OK
>> (router reload, start config download)
> Since what Chirs is talking about s not configuration, I think the
> original text was already OK. I am not sure people will easily
> understand what 'complete features/services configuration' means.  I
> also do not know what the difference between 'discourage' and
> 'strictly discourage' is.
Then how should be call "such as enable/disable notifications" if this 
is not configuration.

    "The OPS Area henceforth strongly discourages the pursuit of
    writable SNMP MIB modules for complete features/services
    configuration purposes by IETF working groups, except in cases of
    clear utility and consensus to do so. Using SNMPSet to simple
    configuration, such as enable/disable notifications or initiating an
    action,  might be appropriate though.  In all other cases, we
    recommend the use of NETCONF/YANG IETF standards for configuration,
    specifically in new charters."

Regards, Benoit
>
> /js
>
> PS: Strictly speaking from an SMIv2 standpoint, I am not sure how to
>      use the MAX-ACCESS clause anymore. ;-}
>
>       The MAX-ACCESS clause, which must be present, defines whether it
>       makes "protocol sense" to read, write and/or create an instance of
>       the object, or to include its value in a notification.  This is the
>       maximal level of access for the object.  (This maximal level of
>       access is independent of any administrative authorization policy.)
>


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

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">On 2/02/2014 06:44, Juergen
      Schoenwaelder wrote:<br>
    </div>
    <blockquote cite="mid:20140202144457.GA35917@elstar.local"
      type="cite">
      <pre wrap="">On Sun, Feb 02, 2014 at 02:58:09PM +0100, Benoit Claise wrote:
</pre>
      <blockquote type="cite">
        <pre wrap="">Mib doctors,

It's time to improve the following statement, to propose it to the
OPS area, and if all goes well o make an IESG statement out of it.

   "The OPS Area henceforth strongly discourages the pursuit of
   writable SNMP MIBs for configuration purposes by working groups
   except in cases of clear utility and overwhelming consensus to do
   so. In all other cases, we recommend the use of NETCONF/YANG IETF
   standards for configuration, specifically in new charters."

I re-read the email thread, and want to make the following changes:
- Add IETF. It was mentioned that some other SDOs might still be
using SNMP for configuration: IEEE, DOCSIS
- Add "for complete features or services" configuration. I want to
address Chirs' point that SNMPSet for starting an action might be OK
(router reload, start config download)
</pre>
      </blockquote>
      <pre wrap="">
Since what Chirs is talking about s not configuration, I think the
original text was already OK. I am not sure people will easily
understand what 'complete features/services configuration' means.  I
also do not know what the difference between 'discourage' and
'strictly discourage' is.</pre>
    </blockquote>
    Then how should be call "such as enable/disable notifications" if
    this is not configuration.<br>
    <blockquote>"The OPS Area henceforth strongly discourages the
      pursuit of writable SNMP MIB modules for complete
      features/services configuration purposes by IETF working groups,
      except in cases of clear utility and consensus to do so. Using
      SNMPSet to simple configuration, such as enable/disable
      notifications or initiating an action,&nbsp; might be appropriate
      though.&nbsp; In all other cases, we recommend the use of NETCONF/YANG
      IETF standards for configuration, specifically in new charters."<br>
      <br>
    </blockquote>
    Regards, Benoit<br>
    <blockquote cite="mid:20140202144457.GA35917@elstar.local"
      type="cite">
      <pre wrap="">

/js

PS: Strictly speaking from an SMIv2 standpoint, I am not sure how to
    use the MAX-ACCESS clause anymore. ;-}

     The MAX-ACCESS clause, which must be present, defines whether it
     makes "protocol sense" to read, write and/or create an instance of
     the object, or to include its value in a notification.  This is the
     maximal level of access for the object.  (This maximal level of
     access is independent of any administrative authorization policy.)

</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------000909040409080101060508--

From dromasca@avaya.com  Wed Feb  5 06:22:54 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 CC11F1A015D for <mib-doctors@ietfa.amsl.com>; Wed,  5 Feb 2014 06:22:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.134
X-Spam-Level: 
X-Spam-Status: No, score=-3.134 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.535] 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 ea67rO98qz_I for <mib-doctors@ietfa.amsl.com>; Wed,  5 Feb 2014 06:22:52 -0800 (PST)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by ietfa.amsl.com (Postfix) with ESMTP id 3A6C31A0177 for <mib-doctors@ietf.org>; Wed,  5 Feb 2014 06:22:52 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AmcKAMZI8lLGmAcV/2dsb2JhbABZgkgjIThXtySHH4EOFnSCJQEBAQEDEhtcAgEGAg0BAwQBAQsdBzIUCQgCBAESCBqHYwGSFJE6q3gXjhECEQEfNwGDJIEUBJ8bizGDLYFoCRci
X-IronPort-AV: E=Sophos;i="4.95,786,1384318800"; d="scan'208,217";a="48094305"
Received: from unknown (HELO co300216-co-erhwest-exch.avaya.com) ([198.152.7.21]) by co300216-co-outbound.net.avaya.com with ESMTP; 05 Feb 2014 09:22:51 -0500
Received: from unknown (HELO AZ-FFEXHC01.global.avaya.com) ([135.64.58.11]) by co300216-co-erhwest-out.avaya.com with ESMTP/TLS/AES128-SHA; 05 Feb 2014 09:11:54 -0500
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC01.global.avaya.com ([135.64.58.11]) with mapi id 14.03.0174.001; Wed, 5 Feb 2014 15:22:49 +0100
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: Benoit Claise <bclaise@cisco.com>, "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "'Bert Wijnen (IETF)'" <bertietf@bwijnen.net>, "'Thomas Nadeau'" <tnadeau@lucidvision.com>, "'MIB Doctors (E-mail)'" <mib-doctors@ietf.org>
Thread-Topic: [MIB-DOCTORS] Why is this MIB module read-write?
Thread-Index: AQHPInxseCo5UMVfdE6YL3camyx6tZqmtf+Q
Date: Wed, 5 Feb 2014 14:22:48 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA2E3ECF99@AZ-FFEXMB04.global.avaya.com>
References: <52DD5FFC.8070103@cisco.com> <20140121094726.GB47210@elstar.local> <9904FB1B0159DA42B0B887B7FA8119CA243D33C0@AZ-FFEXMB04.global.avaya.com> <FE705A2D-F9F0-4A41-A992-36705527C24A@lucidvision.com> <9904FB1B0159DA42B0B887B7FA8119CA243D3C0F@AZ-FFEXMB04.global.avaya.com> <556BB556-669F-4EF5-B8B0-4F1CD7E45BD0@lucidvision.com> <52DE928D.1090909@bwijnen.net> <0b2301cf16ce$bad3a3e0$307aeba0$@olddog.co.uk> <52DF9D02.6070306@cisco.com> <52EE4EF1.3000102@cisco.com> <20140202144457.GA35917@elstar.local> <52F246FB.8010403@cisco.com>
In-Reply-To: <52F246FB.8010403@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.64.58.46]
Content-Type: multipart/alternative; boundary="_000_9904FB1B0159DA42B0B887B7FA8119CA2E3ECF99AZFFEXMB04globa_"
MIME-Version: 1.0
Subject: Re: [MIB-DOCTORS] Why is this MIB module read-write?
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: Wed, 05 Feb 2014 14:22:55 -0000

--_000_9904FB1B0159DA42B0B887B7FA8119CA2E3ECF99AZFFEXMB04globa_
Content-Type: text/plain; charset="windows-1255"
Content-Transfer-Encoding: quoted-printable

Following the discussions we are having =96 we should probably add to enabl=
e/disable notifications also creation and deletion of dynamic rows using th=
e RowStatus TC.

Regards,

Dan


From: Benoit Claise [mailto:bclaise@cisco.com]
Sent: =E9=E5=ED =E3 05 =F4=E1=F8=E5=E0=F8 2014 16:13
To: adrian@olddog.co.uk; 'Bert Wijnen (IETF)'; 'Thomas Nadeau'; Romascanu, =
Dan (Dan); 'MIB Doctors (E-mail)'
Subject: Re: [MIB-DOCTORS] Why is this MIB module read-write?

On 2/02/2014 06:44, Juergen Schoenwaelder wrote:

On Sun, Feb 02, 2014 at 02:58:09PM +0100, Benoit Claise wrote:

Mib doctors,



It's time to improve the following statement, to propose it to the

OPS area, and if all goes well o make an IESG statement out of it.



   "The OPS Area henceforth strongly discourages the pursuit of

   writable SNMP MIBs for configuration purposes by working groups

   except in cases of clear utility and overwhelming consensus to do

   so. In all other cases, we recommend the use of NETCONF/YANG IETF

   standards for configuration, specifically in new charters."



I re-read the email thread, and want to make the following changes:

- Add IETF. It was mentioned that some other SDOs might still be

using SNMP for configuration: IEEE, DOCSIS

- Add "for complete features or services" configuration. I want to

address Chirs' point that SNMPSet for starting an action might be OK

(router reload, start config download)



Since what Chirs is talking about s not configuration, I think the

original text was already OK. I am not sure people will easily

understand what 'complete features/services configuration' means.  I

also do not know what the difference between 'discourage' and

'strictly discourage' is.
Then how should be call "such as enable/disable notifications" if this is n=
ot configuration.
"The OPS Area henceforth strongly discourages the pursuit of writable SNMP =
MIB modules for complete features/services configuration purposes by IETF w=
orking groups, except in cases of clear utility and consensus to do so. Usi=
ng SNMPSet to simple configuration, such as enable/disable notifications or=
 initiating an action,  might be appropriate though.  In all other cases, w=
e recommend the use of NETCONF/YANG IETF standards for configuration, speci=
fically in new charters."
Regards, Benoit






/js



PS: Strictly speaking from an SMIv2 standpoint, I am not sure how to

    use the MAX-ACCESS clause anymore. ;-}



     The MAX-ACCESS clause, which must be present, defines whether it

     makes "protocol sense" to read, write and/or create an instance of

     the object, or to include its value in a notification.  This is the

     maximal level of access for the object.  (This maximal level of

     access is independent of any administrative authorization policy.)




--_000_9904FB1B0159DA42B0B887B7FA8119CA2E3ECF99AZFFEXMB04globa_
Content-Type: text/html; charset="windows-1255"
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=3Dwindows-1=
255">
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@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;}
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 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></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">Following the discussions=
 we are having =96 we should probably add to enable/disable notifications a=
lso creation and deletion of dynamic rows using the RowStatus
 TC. <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"> Benoit Claise [mailto:bclaise@cisco.com]
<br>
<b>Sent:</b> <span lang=3D"HE" dir=3D"RTL">=E9=E5=ED</span><span dir=3D"LTR=
"></span><span dir=3D"LTR"></span><span dir=3D"LTR"></span><span dir=3D"LTR=
"></span>&nbsp;<span lang=3D"HE" dir=3D"RTL">=E3</span><span dir=3D"LTR"></=
span><span dir=3D"LTR"></span><span dir=3D"LTR"></span><span dir=3D"LTR"></=
span>
 05 <span lang=3D"HE" dir=3D"RTL">=F4=E1=F8=E5=E0=F8</span><span dir=3D"LTR=
"></span><span dir=3D"LTR"></span><span dir=3D"LTR"></span><span dir=3D"LTR=
"></span> 2014 16:13<br>
<b>To:</b> adrian@olddog.co.uk; 'Bert Wijnen (IETF)'; 'Thomas Nadeau'; Roma=
scanu, Dan (Dan); 'MIB Doctors (E-mail)'<br>
<b>Subject:</b> Re: [MIB-DOCTORS] Why is this MIB module read-write?<o:p></=
o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">On 2/02/2014 06:44, Juergen Schoenwaelder wrote:<o:p=
></o:p></p>
</div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<pre>On Sun, Feb 02, 2014 at 02:58:09PM &#43;0100, Benoit Claise wrote:<o:p=
></o:p></pre>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<pre>Mib doctors,<o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>It's time to improve the following statement, to propose it to the<o:p=
></o:p></pre>
<pre>OPS area, and if all goes well o make an IESG statement out of it.<o:p=
></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>&nbsp;&nbsp; &quot;The OPS Area henceforth strongly discourages the pu=
rsuit of<o:p></o:p></pre>
<pre>&nbsp;&nbsp; writable SNMP MIBs for configuration purposes by working =
groups<o:p></o:p></pre>
<pre>&nbsp;&nbsp; except in cases of clear utility and overwhelming consens=
us to do<o:p></o:p></pre>
<pre>&nbsp;&nbsp; so. In all other cases, we recommend the use of NETCONF/Y=
ANG IETF<o:p></o:p></pre>
<pre>&nbsp;&nbsp; standards for configuration, specifically in new charters=
.&quot;<o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>I re-read the email thread, and want to make the following changes:<o:=
p></o:p></pre>
<pre>- Add IETF. It was mentioned that some other SDOs might still be<o:p><=
/o:p></pre>
<pre>using SNMP for configuration: IEEE, DOCSIS<o:p></o:p></pre>
<pre>- Add &quot;for complete features or services&quot; configuration. I w=
ant to<o:p></o:p></pre>
<pre>address Chirs' point that SNMPSet for starting an action might be OK<o=
:p></o:p></pre>
<pre>(router reload, start config download)<o:p></o:p></pre>
</blockquote>
<pre><o:p>&nbsp;</o:p></pre>
<pre>Since what Chirs is talking about s not configuration, I think the<o:p=
></o:p></pre>
<pre>original text was already OK. I am not sure people will easily<o:p></o=
:p></pre>
<pre>understand what 'complete features/services configuration' means.&nbsp=
; I<o:p></o:p></pre>
<pre>also do not know what the difference between 'discourage' and<o:p></o:=
p></pre>
<pre>'strictly discourage' is.<o:p></o:p></pre>
</blockquote>
<p class=3D"MsoNormal">Then how should be call &quot;such as enable/disable=
 notifications&quot; if this is not configuration.<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">&quot;The OPS Area he=
nceforth strongly discourages the pursuit of writable SNMP MIB modules for =
complete features/services configuration purposes by IETF working groups, e=
xcept in cases of clear utility and consensus
 to do so. Using SNMPSet to simple configuration, such as enable/disable no=
tifications or initiating an action,&nbsp; might be appropriate though.&nbs=
p; In all other cases, we recommend the use of NETCONF/YANG IETF standards =
for configuration, specifically in new charters.&quot;<o:p></o:p></p>
<p class=3D"MsoNormal">Regards, Benoit<br>
<br>
<o:p></o:p></p>
<pre><o:p>&nbsp;</o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>/js<o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>PS: Strictly speaking from an SMIv2 standpoint, I am not sure how to<o=
:p></o:p></pre>
<pre>&nbsp;&nbsp;&nbsp; use the MAX-ACCESS clause anymore. ;-}<o:p></o:p></=
pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>&nbsp;&nbsp;&nbsp;&nbsp; The MAX-ACCESS clause, which must be present,=
 defines whether it<o:p></o:p></pre>
<pre>&nbsp;&nbsp;&nbsp;&nbsp; makes &quot;protocol sense&quot; to read, wri=
te and/or create an instance of<o:p></o:p></pre>
<pre>&nbsp;&nbsp;&nbsp;&nbsp; the object, or to include its value in a noti=
fication.&nbsp; This is the<o:p></o:p></pre>
<pre>&nbsp;&nbsp;&nbsp;&nbsp; maximal level of access for the object.&nbsp;=
 (This maximal level of<o:p></o:p></pre>
<pre>&nbsp;&nbsp;&nbsp;&nbsp; access is independent of any administrative a=
uthorization policy.)<o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</body>
</html>

--_000_9904FB1B0159DA42B0B887B7FA8119CA2E3ECF99AZFFEXMB04globa_--

From bclaise@cisco.com  Wed Feb  5 06:28:48 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 2F9781A017B for <mib-doctors@ietfa.amsl.com>; Wed,  5 Feb 2014 06:28:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.035
X-Spam-Level: 
X-Spam-Status: No, score=-15.035 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, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.535, 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 1cNGMehPwU5g for <mib-doctors@ietfa.amsl.com>; Wed,  5 Feb 2014 06:28:45 -0800 (PST)
Received: from mtv-iport-1.cisco.com (mtv-iport-1.cisco.com [173.36.130.12]) by ietfa.amsl.com (Postfix) with ESMTP id D1CD01A015B for <mib-doctors@ietf.org>; Wed,  5 Feb 2014 06:28:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=43296; q=dns/txt; s=iport; t=1391610525; x=1392820125; h=message-id:date:from:mime-version:to:subject:references: in-reply-to; bh=A8Eklioh9RRxUnuMypuKfjwQ4leH/RdB//6aZMeXSxU=; b=fcHWktB3PVlGdwJHy4z7rbMT+rMCh/1jyaQ9ZWOf0uF/BjzcfZPcNSOD 3/SgQkx+QUNJ/7x6X91SCxBT3MDVM6dJnJYeKEBFwBIVgQu49DpUsQ7n5 WN19ss5fVHhcLJmPRLoDKoSmfmJ9ypR4zBF6ML4kJ00+lwPu2r1Ww5tk8 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AmYKAEBK8lKrRDoH/2dsb2JhbABZgkhEOLd7hx+BDhZ0giUBAQEDAQEBARoQPgMKBgcCAgsRBAEBChYBAQYHCQMCAQIBCQsBHwkIBwwFAQIBAYd5Bw7PPBMEBI4PEQEkMgEGhDIEiUmOYoZIi1mDThuBNQ
X-IronPort-AV: E=Sophos;i="4.95,786,1384300800";  d="scan'208,217";a="101655100"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by mtv-iport-1.cisco.com with ESMTP; 05 Feb 2014 14:28:35 +0000
Received: from [10.21.70.50] ([10.21.70.50]) by mtv-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id s15ESYlH001752; Wed, 5 Feb 2014 14:28:34 GMT
Message-ID: <52F24A92.7060008@cisco.com>
Date: Wed, 05 Feb 2014 06:28:34 -0800
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: adrian@olddog.co.uk, mib-doctors@ietf.org
References: <05c501cf21ad$80d97ef0$828c7cd0$@olddog.co.uk>
In-Reply-To: <05c501cf21ad$80d97ef0$828c7cd0$@olddog.co.uk>
Content-Type: multipart/alternative; boundary="------------090806080004070802050504"
Subject: Re: [MIB-DOCTORS] Read-only MIB modules
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: Wed, 05 Feb 2014 14:28:48 -0000

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

Adrian,

The following text is basically a statement of direction for the IETF. 
Clearly, there will be a transition period.

    "The OPS Area henceforth strongly discourages the pursuit of
    writable SNMP MIB modules for complete features/services
    configuration purposes by IETF working groups, except in cases of
    clear utility and consensus to do so. Using SNMPSet to simple
    configuration, such as enable/disable notifications or initiating an
    action,  might be appropriate though.  In all other cases, we
    recommend the use of NETCONF/YANG IETF standards for configuration,
    specifically in new charters."

This is the reason why I stressed "specifically in new charters"
Note: we have a similar situation in an EMAN MIB module where some 
objects are read-write (RowStatus TC)

Regards, Benoit

> Hi,
>
> The MPLS working group is testing the water to see whether one of its 
> MIB modules should be "reduced" to read-only. This is the document 
> that triggered my recent questions that led on to the draft advice you 
> are working on. The WG took the document back to make this decision.
>
> You'll note below that we immediately have an implementation claim 
> (not for this doc, but for the modules it extends).
>
> An interesting situation, I think.
>
> A
>
> *From:*mpls [mailto:mpls-bounces@ietf.org] *On Behalf Of *GyeRok Gwun 
> (???)
> *Sent:* 04 February 2014 09:57
> *To:* 'mpls@ietf.org'
> *Cc:* 'mpls-chairs@tools.ietf.org'; 
> 'draft-ietf-mpls-tp-te-mib@tools.ietf.org'
> *Subject:* Re: [mpls] seeking consensus on making 
> draft-ietf-mpls-tp-te-mib read- only
>
> No/oppose to make as Read-only mib.
>
> In our products we extensively use R/W object of TE mib. We also have 
> NMS/EMS that use TE read-write Objects
>
> Best Regards
>
> Gwun
>
> -----Original Message-----
>
> From: mpls [mailto:mpls-bounces@ietf.org] On Behalf Of Loa Andersson
>
> Sent: Monday, February 03, 2014 10:55 PM
>
> To: mpls@ietf.org <mailto:mpls@ietf.org>
>
> Cc: mpls-chairs@tools.ietf.org <mailto:mpls-chairs@tools.ietf.org>; 
> draft-ietf-mpls-tp-te-mib@tools.ietf.org 
> <mailto:draft-ietf-mpls-tp-te-mib@tools.ietf.org>
>
> Subject: [mpls] seeking consensus on making draft-ietf-mpls-tp-te-mib 
> read- only
>
> Working Group,
>
> We have just recalled draft-ietf-mpls-tp-te-mib from the IESG to the 
> working group for more work. We have a series of comments that are 
> mostly for clarification. However the main reason for recalling the 
> document is that there is one point where we need to confirm working 
> group consensus.
>
> The IETF, the working group and the MIB Doctors are today very 
> reluctant to produce read-write MIB modules. The current draft is 
> read-write for a few objects, this is based on a consensus call for an 
> earlier discussion, however the consensus call was not clear. It can 
> be taken to mean both that we want to go with read-write objects and 
> that we want to see read-only. Is it clear that it has been 
> interpreted differently by different individuals.
>
> The authors and chairs have discussed the issue and we have a rough 
> consensus that we want the MIB module(s) to be read-only.
>
> We therefore are asking the working group if this is OK for the MIB
>
> module(s) in the current document. Please indicate Support or Oppose 
> for this MIB (draft-ietf-mpls-tp-te-mib) to be read-only.
>
> Please send your comments to the working group mailing list before 
> February 18, 2014.
>
> Loa
>
> for the MPLS wg chairs
>
> -- 
>
> Loa Andersson                        email: loa@mail01.huawei.com 
> <mailto:loa@mail01.huawei.com>
>
> Senior MPLS Expert loa@pi.nu <mailto:loa@pi.nu>
>
> Huawei Technologies (consultant)     phone: +46 739 81 21 64
>
> _______________________________________________
>
> mpls mailing list
>
> mpls@ietf.org <mailto:mpls@ietf.org>
>
> https://www.ietf.org/mailman/listinfo/mpls
>
> _______________________________________________
>
> mpls mailing list
>
> mpls@ietf.org <mailto:mpls@ietf.org>
>
> https://www.ietf.org/mailman/listinfo/mpls
>
>
>
> _______________________________________________
> MIB-DOCTORS mailing list
> MIB-DOCTORS@ietf.org
> https://www.ietf.org/mailman/listinfo/mib-doctors


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

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">Adrian,<br>
      <br>
      The following text is basically a statement of direction for the
      IETF. Clearly, there will be a transition period.<br>
      <blockquote>"The OPS Area henceforth strongly discourages the
        pursuit of writable SNMP MIB modules for complete
        features/services configuration purposes by IETF working groups,
        except in cases of clear utility and consensus to do so. Using
        SNMPSet to simple configuration, such as enable/disable
        notifications or initiating an action,&nbsp; might be appropriate
        though.&nbsp; In all other cases, we recommend the use of
        NETCONF/YANG IETF standards for configuration, specifically in
        new charters."</blockquote>
      This is the reason why I stressed "specifically in new charters"<br>
      Note: we have a similar situation in an EMAN MIB module where some
      objects are read-write (RowStatus TC)<br>
      <br>
      Regards, Benoit<br>
      <br>
    </div>
    <blockquote cite="mid:05c501cf21ad$80d97ef0$828c7cd0$@olddog.co.uk"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=ISO-8859-1">
      <meta name="ProgId" content="Word.Document">
      <meta name="Generator" content="Microsoft Word 14">
      <meta name="Originator" content="Microsoft Word 14">
      <link rel="File-List" href="cid:filelist.xml@01CF21AD.7DA72AC0">
      <!--[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:UseFELayout/>
</w:Compatibility>
<m:mathPr>
<m:mathFont m:val="Cambria Math"/>
<m:brkBin m:val="before"/>
<m:brkBinSub m:val="&#45;-"/>
<m:smallFrac m:val="off"/>
<m:dispDef/>
<m:lMargin m:val="0"/>
<m:rMargin m:val="0"/>
<m:defJc m:val="centerGroup"/>
<m:wrapIndent m:val="1440"/>
<m:intLim m:val="subSup"/>
<m:naryLim m:val="undOvr"/>
</m:mathPr></w:WordDocument>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:LatentStyles DefLockedState="false" DefUnhideWhenUsed="true" DefSemiHidden="true" DefQFormat="false" DefPriority="99" LatentStyleCount="267">
<w:LsdException Locked="false" Priority="0" SemiHidden="false" UnhideWhenUsed="false" QFormat="true" Name="Normal"/>
<w:LsdException Locked="false" Priority="9" SemiHidden="false" UnhideWhenUsed="false" QFormat="true" Name="heading 1"/>
<w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 2"/>
<w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 3"/>
<w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 4"/>
<w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 5"/>
<w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 6"/>
<w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 7"/>
<w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 8"/>
<w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 9"/>
<w:LsdException Locked="false" Priority="39" Name="toc 1"/>
<w:LsdException Locked="false" Priority="39" Name="toc 2"/>
<w:LsdException Locked="false" Priority="39" Name="toc 3"/>
<w:LsdException Locked="false" Priority="39" Name="toc 4"/>
<w:LsdException Locked="false" Priority="39" Name="toc 5"/>
<w:LsdException Locked="false" Priority="39" Name="toc 6"/>
<w:LsdException Locked="false" Priority="39" Name="toc 7"/>
<w:LsdException Locked="false" Priority="39" Name="toc 8"/>
<w:LsdException Locked="false" Priority="39" Name="toc 9"/>
<w:LsdException Locked="false" Priority="35" QFormat="true" Name="caption"/>
<w:LsdException Locked="false" Priority="10" SemiHidden="false" UnhideWhenUsed="false" QFormat="true" Name="Title"/>
<w:LsdException Locked="false" Priority="1" Name="Default Paragraph Font"/>
<w:LsdException Locked="false" Priority="11" SemiHidden="false" UnhideWhenUsed="false" QFormat="true" Name="Subtitle"/>
<w:LsdException Locked="false" Priority="22" SemiHidden="false" UnhideWhenUsed="false" QFormat="true" Name="Strong"/>
<w:LsdException Locked="false" Priority="20" SemiHidden="false" UnhideWhenUsed="false" QFormat="true" Name="Emphasis"/>
<w:LsdException Locked="false" Priority="59" SemiHidden="false" UnhideWhenUsed="false" Name="Table Grid"/>
<w:LsdException Locked="false" UnhideWhenUsed="false" Name="Placeholder Text"/>
<w:LsdException Locked="false" Priority="1" SemiHidden="false" UnhideWhenUsed="false" QFormat="true" Name="No Spacing"/>
<w:LsdException Locked="false" Priority="60" SemiHidden="false" UnhideWhenUsed="false" Name="Light Shading"/>
<w:LsdException Locked="false" Priority="61" SemiHidden="false" UnhideWhenUsed="false" Name="Light List"/>
<w:LsdException Locked="false" Priority="62" SemiHidden="false" UnhideWhenUsed="false" Name="Light Grid"/>
<w:LsdException Locked="false" Priority="63" SemiHidden="false" UnhideWhenUsed="false" Name="Medium Shading 1"/>
<w:LsdException Locked="false" Priority="64" SemiHidden="false" UnhideWhenUsed="false" Name="Medium Shading 2"/>
<w:LsdException Locked="false" Priority="65" SemiHidden="false" UnhideWhenUsed="false" Name="Medium List 1"/>
<w:LsdException Locked="false" Priority="66" SemiHidden="false" UnhideWhenUsed="false" Name="Medium List 2"/>
<w:LsdException Locked="false" Priority="67" SemiHidden="false" UnhideWhenUsed="false" Name="Medium Grid 1"/>
<w:LsdException Locked="false" Priority="68" SemiHidden="false" UnhideWhenUsed="false" Name="Medium Grid 2"/>
<w:LsdException Locked="false" Priority="69" SemiHidden="false" UnhideWhenUsed="false" Name="Medium Grid 3"/>
<w:LsdException Locked="false" Priority="70" SemiHidden="false" UnhideWhenUsed="false" Name="Dark List"/>
<w:LsdException Locked="false" Priority="71" SemiHidden="false" UnhideWhenUsed="false" Name="Colorful Shading"/>
<w:LsdException Locked="false" Priority="72" SemiHidden="false" UnhideWhenUsed="false" Name="Colorful List"/>
<w:LsdException Locked="false" Priority="73" SemiHidden="false" UnhideWhenUsed="false" Name="Colorful Grid"/>
<w:LsdException Locked="false" Priority="60" SemiHidden="false" UnhideWhenUsed="false" Name="Light Shading Accent 1"/>
<w:LsdException Locked="false" Priority="61" SemiHidden="false" UnhideWhenUsed="false" Name="Light List Accent 1"/>
<w:LsdException Locked="false" Priority="62" SemiHidden="false" UnhideWhenUsed="false" Name="Light Grid Accent 1"/>
<w:LsdException Locked="false" Priority="63" SemiHidden="false" UnhideWhenUsed="false" Name="Medium Shading 1 Accent 1"/>
<w:LsdException Locked="false" Priority="64" SemiHidden="false" UnhideWhenUsed="false" Name="Medium Shading 2 Accent 1"/>
<w:LsdException Locked="false" Priority="65" SemiHidden="false" UnhideWhenUsed="false" Name="Medium List 1 Accent 1"/>
<w:LsdException Locked="false" UnhideWhenUsed="false" Name="Revision"/>
<w:LsdException Locked="false" Priority="34" SemiHidden="false" UnhideWhenUsed="false" QFormat="true" Name="List Paragraph"/>
<w:LsdException Locked="false" Priority="29" SemiHidden="false" UnhideWhenUsed="false" QFormat="true" Name="Quote"/>
<w:LsdException Locked="false" Priority="30" SemiHidden="false" UnhideWhenUsed="false" QFormat="true" Name="Intense Quote"/>
<w:LsdException Locked="false" Priority="66" SemiHidden="false" UnhideWhenUsed="false" Name="Medium List 2 Accent 1"/>
<w:LsdException Locked="false" Priority="67" SemiHidden="false" UnhideWhenUsed="false" Name="Medium Grid 1 Accent 1"/>
<w:LsdException Locked="false" Priority="68" SemiHidden="false" UnhideWhenUsed="false" Name="Medium Grid 2 Accent 1"/>
<w:LsdException Locked="false" Priority="69" SemiHidden="false" UnhideWhenUsed="false" Name="Medium Grid 3 Accent 1"/>
<w:LsdException Locked="false" Priority="70" SemiHidden="false" UnhideWhenUsed="false" Name="Dark List Accent 1"/>
<w:LsdException Locked="false" Priority="71" SemiHidden="false" UnhideWhenUsed="false" Name="Colorful Shading Accent 1"/>
<w:LsdException Locked="false" Priority="72" SemiHidden="false" UnhideWhenUsed="false" Name="Colorful List Accent 1"/>
<w:LsdException Locked="false" Priority="73" SemiHidden="false" UnhideWhenUsed="false" Name="Colorful Grid Accent 1"/>
<w:LsdException Locked="false" Priority="60" SemiHidden="false" UnhideWhenUsed="false" Name="Light Shading Accent 2"/>
<w:LsdException Locked="false" Priority="61" SemiHidden="false" UnhideWhenUsed="false" Name="Light List Accent 2"/>
<w:LsdException Locked="false" Priority="62" SemiHidden="false" UnhideWhenUsed="false" Name="Light Grid Accent 2"/>
<w:LsdException Locked="false" Priority="63" SemiHidden="false" UnhideWhenUsed="false" Name="Medium Shading 1 Accent 2"/>
<w:LsdException Locked="false" Priority="64" SemiHidden="false" UnhideWhenUsed="false" Name="Medium Shading 2 Accent 2"/>
<w:LsdException Locked="false" Priority="65" SemiHidden="false" UnhideWhenUsed="false" Name="Medium List 1 Accent 2"/>
<w:LsdException Locked="false" Priority="66" SemiHidden="false" UnhideWhenUsed="false" Name="Medium List 2 Accent 2"/>
<w:LsdException Locked="false" Priority="67" SemiHidden="false" UnhideWhenUsed="false" Name="Medium Grid 1 Accent 2"/>
<w:LsdException Locked="false" Priority="68" SemiHidden="false" UnhideWhenUsed="false" Name="Medium Grid 2 Accent 2"/>
<w:LsdException Locked="false" Priority="69" SemiHidden="false" UnhideWhenUsed="false" Name="Medium Grid 3 Accent 2"/>
<w:LsdException Locked="false" Priority="70" SemiHidden="false" UnhideWhenUsed="false" Name="Dark List Accent 2"/>
<w:LsdException Locked="false" Priority="71" SemiHidden="false" UnhideWhenUsed="false" Name="Colorful Shading Accent 2"/>
<w:LsdException Locked="false" Priority="72" SemiHidden="false" UnhideWhenUsed="false" Name="Colorful List Accent 2"/>
<w:LsdException Locked="false" Priority="73" SemiHidden="false" UnhideWhenUsed="false" Name="Colorful Grid Accent 2"/>
<w:LsdException Locked="false" Priority="60" SemiHidden="false" UnhideWhenUsed="false" Name="Light Shading Accent 3"/>
<w:LsdException Locked="false" Priority="61" SemiHidden="false" UnhideWhenUsed="false" Name="Light List Accent 3"/>
<w:LsdException Locked="false" Priority="62" SemiHidden="false" UnhideWhenUsed="false" Name="Light Grid Accent 3"/>
<w:LsdException Locked="false" Priority="63" SemiHidden="false" UnhideWhenUsed="false" Name="Medium Shading 1 Accent 3"/>
<w:LsdException Locked="false" Priority="64" SemiHidden="false" UnhideWhenUsed="false" Name="Medium Shading 2 Accent 3"/>
<w:LsdException Locked="false" Priority="65" SemiHidden="false" UnhideWhenUsed="false" Name="Medium List 1 Accent 3"/>
<w:LsdException Locked="false" Priority="66" SemiHidden="false" UnhideWhenUsed="false" Name="Medium List 2 Accent 3"/>
<w:LsdException Locked="false" Priority="67" SemiHidden="false" UnhideWhenUsed="false" Name="Medium Grid 1 Accent 3"/>
<w:LsdException Locked="false" Priority="68" SemiHidden="false" UnhideWhenUsed="false" Name="Medium Grid 2 Accent 3"/>
<w:LsdException Locked="false" Priority="69" SemiHidden="false" UnhideWhenUsed="false" Name="Medium Grid 3 Accent 3"/>
<w:LsdException Locked="false" Priority="70" SemiHidden="false" UnhideWhenUsed="false" Name="Dark List Accent 3"/>
<w:LsdException Locked="false" Priority="71" SemiHidden="false" UnhideWhenUsed="false" Name="Colorful Shading Accent 3"/>
<w:LsdException Locked="false" Priority="72" SemiHidden="false" UnhideWhenUsed="false" Name="Colorful List Accent 3"/>
<w:LsdException Locked="false" Priority="73" SemiHidden="false" UnhideWhenUsed="false" Name="Colorful Grid Accent 3"/>
<w:LsdException Locked="false" Priority="60" SemiHidden="false" UnhideWhenUsed="false" Name="Light Shading Accent 4"/>
<w:LsdException Locked="false" Priority="61" SemiHidden="false" UnhideWhenUsed="false" Name="Light List Accent 4"/>
<w:LsdException Locked="false" Priority="62" SemiHidden="false" UnhideWhenUsed="false" Name="Light Grid Accent 4"/>
<w:LsdException Locked="false" Priority="63" SemiHidden="false" UnhideWhenUsed="false" Name="Medium Shading 1 Accent 4"/>
<w:LsdException Locked="false" Priority="64" SemiHidden="false" UnhideWhenUsed="false" Name="Medium Shading 2 Accent 4"/>
<w:LsdException Locked="false" Priority="65" SemiHidden="false" UnhideWhenUsed="false" Name="Medium List 1 Accent 4"/>
<w:LsdException Locked="false" Priority="66" SemiHidden="false" UnhideWhenUsed="false" Name="Medium List 2 Accent 4"/>
<w:LsdException Locked="false" Priority="67" SemiHidden="false" UnhideWhenUsed="false" Name="Medium Grid 1 Accent 4"/>
<w:LsdException Locked="false" Priority="68" SemiHidden="false" UnhideWhenUsed="false" Name="Medium Grid 2 Accent 4"/>
<w:LsdException Locked="false" Priority="69" SemiHidden="false" UnhideWhenUsed="false" Name="Medium Grid 3 Accent 4"/>
<w:LsdException Locked="false" Priority="70" SemiHidden="false" UnhideWhenUsed="false" Name="Dark List Accent 4"/>
<w:LsdException Locked="false" Priority="71" SemiHidden="false" UnhideWhenUsed="false" Name="Colorful Shading Accent 4"/>
<w:LsdException Locked="false" Priority="72" SemiHidden="false" UnhideWhenUsed="false" Name="Colorful List Accent 4"/>
<w:LsdException Locked="false" Priority="73" SemiHidden="false" UnhideWhenUsed="false" Name="Colorful Grid Accent 4"/>
<w:LsdException Locked="false" Priority="60" SemiHidden="false" UnhideWhenUsed="false" Name="Light Shading Accent 5"/>
<w:LsdException Locked="false" Priority="61" SemiHidden="false" UnhideWhenUsed="false" Name="Light List Accent 5"/>
<w:LsdException Locked="false" Priority="62" SemiHidden="false" UnhideWhenUsed="false" Name="Light Grid Accent 5"/>
<w:LsdException Locked="false" Priority="63" SemiHidden="false" UnhideWhenUsed="false" Name="Medium Shading 1 Accent 5"/>
<w:LsdException Locked="false" Priority="64" SemiHidden="false" UnhideWhenUsed="false" Name="Medium Shading 2 Accent 5"/>
<w:LsdException Locked="false" Priority="65" SemiHidden="false" UnhideWhenUsed="false" Name="Medium List 1 Accent 5"/>
<w:LsdException Locked="false" Priority="66" SemiHidden="false" UnhideWhenUsed="false" Name="Medium List 2 Accent 5"/>
<w:LsdException Locked="false" Priority="67" SemiHidden="false" UnhideWhenUsed="false" Name="Medium Grid 1 Accent 5"/>
<w:LsdException Locked="false" Priority="68" SemiHidden="false" UnhideWhenUsed="false" Name="Medium Grid 2 Accent 5"/>
<w:LsdException Locked="false" Priority="69" SemiHidden="false" UnhideWhenUsed="false" Name="Medium Grid 3 Accent 5"/>
<w:LsdException Locked="false" Priority="70" SemiHidden="false" UnhideWhenUsed="false" Name="Dark List Accent 5"/>
<w:LsdException Locked="false" Priority="71" SemiHidden="false" UnhideWhenUsed="false" Name="Colorful Shading Accent 5"/>
<w:LsdException Locked="false" Priority="72" SemiHidden="false" UnhideWhenUsed="false" Name="Colorful List Accent 5"/>
<w:LsdException Locked="false" Priority="73" SemiHidden="false" UnhideWhenUsed="false" Name="Colorful Grid Accent 5"/>
<w:LsdException Locked="false" Priority="60" SemiHidden="false" UnhideWhenUsed="false" Name="Light Shading Accent 6"/>
<w:LsdException Locked="false" Priority="61" SemiHidden="false" UnhideWhenUsed="false" Name="Light List Accent 6"/>
<w:LsdException Locked="false" Priority="62" SemiHidden="false" UnhideWhenUsed="false" Name="Light Grid Accent 6"/>
<w:LsdException Locked="false" Priority="63" SemiHidden="false" UnhideWhenUsed="false" Name="Medium Shading 1 Accent 6"/>
<w:LsdException Locked="false" Priority="64" SemiHidden="false" UnhideWhenUsed="false" Name="Medium Shading 2 Accent 6"/>
<w:LsdException Locked="false" Priority="65" SemiHidden="false" UnhideWhenUsed="false" Name="Medium List 1 Accent 6"/>
<w:LsdException Locked="false" Priority="66" SemiHidden="false" UnhideWhenUsed="false" Name="Medium List 2 Accent 6"/>
<w:LsdException Locked="false" Priority="67" SemiHidden="false" UnhideWhenUsed="false" Name="Medium Grid 1 Accent 6"/>
<w:LsdException Locked="false" Priority="68" SemiHidden="false" UnhideWhenUsed="false" Name="Medium Grid 2 Accent 6"/>
<w:LsdException Locked="false" Priority="69" SemiHidden="false" UnhideWhenUsed="false" Name="Medium Grid 3 Accent 6"/>
<w:LsdException Locked="false" Priority="70" SemiHidden="false" UnhideWhenUsed="false" Name="Dark List Accent 6"/>
<w:LsdException Locked="false" Priority="71" SemiHidden="false" UnhideWhenUsed="false" Name="Colorful Shading Accent 6"/>
<w:LsdException Locked="false" Priority="72" SemiHidden="false" UnhideWhenUsed="false" Name="Colorful List Accent 6"/>
<w:LsdException Locked="false" Priority="73" SemiHidden="false" UnhideWhenUsed="false" Name="Colorful Grid Accent 6"/>
<w:LsdException Locked="false" Priority="19" SemiHidden="false" UnhideWhenUsed="false" QFormat="true" Name="Subtle Emphasis"/>
<w:LsdException Locked="false" Priority="21" SemiHidden="false" UnhideWhenUsed="false" QFormat="true" Name="Intense Emphasis"/>
<w:LsdException Locked="false" Priority="31" SemiHidden="false" UnhideWhenUsed="false" QFormat="true" Name="Subtle Reference"/>
<w:LsdException Locked="false" Priority="32" SemiHidden="false" UnhideWhenUsed="false" QFormat="true" Name="Intense Reference"/>
<w:LsdException Locked="false" Priority="33" SemiHidden="false" UnhideWhenUsed="false" QFormat="true" Name="Book Title"/>
<w:LsdException Locked="false" Priority="37" Name="Bibliography"/>
<w:LsdException Locked="false" Priority="39" QFormat="true" Name="TOC Heading"/>
</w:LatentStyles>
</xml><![endif]-->
      <style><!--
/* Font Definitions */
@font-face
	{font-family:Gulim;
	panose-1:2 11 6 0 0 1 1 1 1 1;
	mso-font-alt:\AD74\B9BC;
	mso-font-charset:129;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:-1342176593 1775729915 48 0 524447 0;}
@font-face
	{font-family:Gulim;
	panose-1:2 11 6 0 0 1 1 1 1 1;
	mso-font-alt:\AD74\B9BC;
	mso-font-charset:129;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:-1342176593 1775729915 48 0 524447 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;}
@font-face
	{font-family:"Malgun Gothic";
	panose-1:2 11 5 3 2 0 0 2 0 4;
	mso-font-charset:129;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:-1879047505 165117179 18 0 524289 0;}
@font-face
	{font-family:"\@Malgun Gothic";
	panose-1:2 11 5 3 2 0 0 2 0 4;
	mso-font-charset:129;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:-1879047505 165117179 18 0 524289 0;}
@font-face
	{font-family:"\@Gulim";
	panose-1:2 11 6 0 0 1 1 1 1 1;
	mso-font-charset:129;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:-1342176593 1775729915 48 0 524447 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;
	text-align:justify;
	text-justify:inter-ideograph;
	mso-pagination:widow-orphan;
	text-autospace:none;
	word-break:break-all;
	font-size:10.0pt;
	font-family:"Malgun Gothic","sans-serif";
	mso-bidi-font-family:Gulim;
	mso-fareast-language:KO;}
a:link, span.MsoHyperlink
	{mso-style-noshow:yes;
	mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;
	text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-noshow:yes;
	mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;
	text-underline:single;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-noshow:yes;
	mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	text-autospace:none;
	word-break:break-all;
	font-size:10.0pt;
	font-family:"Courier New","serif";
	mso-fareast-font-family:Gulim;
	mso-fareast-language:KO;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-noshow:yes;
	mso-style-priority:99;
	mso-style-unhide:no;
	mso-style-locked:yes;
	mso-style-link:"Plain Text";
	mso-ansi-font-size:10.5pt;
	mso-bidi-font-size:10.5pt;
	font-family:Consolas;
	mso-ascii-font-family:Consolas;
	mso-fareast-font-family:"Malgun Gothic";
	mso-hansi-font-family:Consolas;
	mso-bidi-font-family:Consolas;
	mso-fareast-language:KO;}
span.EmailStyle19
	{mso-style-type:personal;
	mso-style-noshow:yes;
	mso-style-unhide:no;
	font-family:"Malgun Gothic","sans-serif";
	mso-ascii-font-family:"Malgun Gothic";
	mso-fareast-font-family:"Malgun Gothic";
	mso-hansi-font-family:"Malgun Gothic";
	color:windowtext;}
p.a, li.a, div.a
	{mso-style-name:\AE00\C790\B9CC;
	mso-style-unhide:no;
	mso-style-link:"\AE00\C790\B9CC Char";
	margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	mso-pagination:widow-orphan;
	text-autospace:none;
	word-break:break-all;
	font-size:10.0pt;
	font-family:"Malgun Gothic","sans-serif";
	mso-bidi-font-family:Gulim;
	mso-fareast-language:KO;}
span.Char
	{mso-style-name:"\AE00\C790\B9CC Char";
	mso-style-priority:99;
	mso-style-unhide:no;
	mso-style-locked:yes;
	mso-style-link:\AE00\C790\B9CC;
	font-family:"Courier New","serif";
	mso-ascii-font-family:"Courier New";
	mso-hansi-font-family:"Courier New";
	mso-bidi-font-family:"Courier New";}
span.EmailStyle22
	{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;}
span.SpellE
	{mso-style-name:"";
	mso-spl-e:yes;}
.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:3.0cm 72.0pt 72.0pt 72.0pt;
	mso-header-margin:36.0pt;
	mso-footer-margin:36.0pt;
	mso-paper-source:0;}
div.WordSection1
	{page:WordSection1;}
--></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="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
      <div class="WordSection1">
        <p class="MsoNormal" style="word-break:normal"><span
            style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;mso-fareast-font-family:Calibri;mso-bidi-font-family:&quot;Times
            New Roman&quot;;color:#1F497D">Hi,<o:p></o:p></span></p>
        <p class="MsoNormal" style="word-break:normal"><span
            style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;mso-fareast-font-family:Calibri;mso-bidi-font-family:&quot;Times
            New Roman&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoNormal" style="word-break:normal"><span
            style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;mso-fareast-font-family:Calibri;mso-bidi-font-family:&quot;Times
            New Roman&quot;;color:#1F497D">The MPLS working group is
            testing the water to see whether one of its MIB modules
            should be "reduced" to read-only. This is the document that
            triggered my recent questions that led on to the draft
            advice you are working on. The WG took the document back to
            make this decision.<o:p></o:p></span></p>
        <p class="MsoNormal" style="word-break:normal"><span
            style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;mso-fareast-font-family:Calibri;mso-bidi-font-family:&quot;Times
            New Roman&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoNormal" style="word-break:normal"><span
            style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;mso-fareast-font-family:Calibri;mso-bidi-font-family:&quot;Times
            New Roman&quot;;color:#1F497D">You'll note below that we
            immediately have an implementation claim (not for this doc,
            but for the modules it extends).<o:p></o:p></span></p>
        <p class="MsoNormal" style="word-break:normal"><span
            style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;mso-fareast-font-family:Calibri;mso-bidi-font-family:&quot;Times
            New Roman&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoNormal" style="word-break:normal"><span
            style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;mso-fareast-font-family:Calibri;mso-bidi-font-family:&quot;Times
            New Roman&quot;;color:#1F497D">An interesting situation, I
            think.<o:p></o:p></span></p>
        <p class="MsoNormal" style="word-break:normal"><span
            style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;mso-fareast-font-family:Calibri;mso-bidi-font-family:&quot;Times
            New Roman&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoNormal" style="word-break:normal"><span
            style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;mso-fareast-font-family:Calibri;mso-bidi-font-family:&quot;Times
            New Roman&quot;;color:#1F497D">A<o:p></o:p></span></p>
        <p class="MsoNormal" style="word-break:normal"><span
            style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;mso-fareast-font-family:Calibri;mso-bidi-font-family:&quot;Times
            New Roman&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
        <div style="border:none;border-left:solid blue 1.5pt;padding:0cm
          0cm 0cm 4.0pt">
          <div>
            <div style="border:none;border-top:solid #B5C4DF
              1.0pt;padding:3.0pt 0cm 0cm 0cm">
              <p class="MsoNormal"
                style="text-align:left;text-autospace:ideograph-numeric
                ideograph-other;word-break:normal" align="left"><b><span
style="font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;mso-fareast-font-family:Gulim;mso-ansi-language:EN-US"
                    lang="EN-US">From:</span></b><span
style="font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;mso-fareast-font-family:Gulim;mso-ansi-language:EN-US"
                  lang="EN-US"> mpls [<a class="moz-txt-link-freetext" href="mailto:mpls-bounces@ietf.org">mailto:mpls-bounces@ietf.org</a>] <b>On
                    Behalf Of </b>GyeRok Gwun (???)<br>
                  <b>Sent:</b> 04 February 2014 09:57<br>
                  <b>To:</b> '<a class="moz-txt-link-abbreviated" href="mailto:mpls@ietf.org">mpls@ietf.org</a>'<br>
                  <b>Cc:</b> '<a class="moz-txt-link-abbreviated" href="mailto:mpls-chairs@tools.ietf.org">mpls-chairs@tools.ietf.org</a>';
                  '<a class="moz-txt-link-abbreviated" href="mailto:draft-ietf-mpls-tp-te-mib@tools.ietf.org">draft-ietf-mpls-tp-te-mib@tools.ietf.org</a>'<br>
                  <b>Subject:</b> Re: [mpls] seeking consensus on making
                  draft-ietf-mpls-tp-te-mib read- only<o:p></o:p></span></p>
            </div>
          </div>
          <p class="MsoNormal" style="text-align:left" align="left"><o:p>&nbsp;</o:p></p>
          <p class="MsoPlainText"><span style="mso-ansi-language:EN-US"
              lang="EN-US">No/oppose to make as Read-only mib.<o:p></o:p></span></p>
          <p class="MsoPlainText"><span style="mso-ansi-language:EN-US"
              lang="EN-US">In our products we extensively use R/W object
              of TE mib. We also have NMS/EMS that use TE read-write
              Objects<o:p></o:p></span></p>
          <p class="MsoPlainText"><span style="mso-ansi-language:EN-US"
              lang="EN-US"><o:p>&nbsp;</o:p></span></p>
          <p class="MsoPlainText"><span style="mso-ansi-language:EN-US"
              lang="EN-US">Best Regards<o:p></o:p></span></p>
          <p class="MsoPlainText"><span style="mso-ansi-language:EN-US"
              lang="EN-US">Gwun<o:p></o:p></span></p>
          <p class="MsoPlainText"><span style="mso-ansi-language:EN-US"
              lang="EN-US"><o:p>&nbsp;</o:p></span></p>
          <p class="MsoPlainText"><span style="mso-ansi-language:EN-US"
              lang="EN-US">-----Original Message-----<o:p></o:p></span></p>
          <p class="MsoPlainText"><span style="mso-ansi-language:EN-US"
              lang="EN-US">From: mpls [<a moz-do-not-send="true"
                href="mailto:mpls-bounces@ietf.org">mailto:mpls-bounces@ietf.org</a>]
              On Behalf Of Loa Andersson<o:p></o:p></span></p>
          <p class="MsoPlainText"><span style="mso-ansi-language:EN-US"
              lang="EN-US">Sent: Monday, February 03, 2014 10:55 PM<o:p></o:p></span></p>
          <p class="MsoPlainText"><span style="mso-ansi-language:EN-US"
              lang="EN-US">To: <a moz-do-not-send="true"
                href="mailto:mpls@ietf.org">mpls@ietf.org</a><o:p></o:p></span></p>
          <p class="MsoPlainText"><span style="mso-ansi-language:EN-US"
              lang="EN-US">Cc: <a moz-do-not-send="true"
                href="mailto:mpls-chairs@tools.ietf.org">mpls-chairs@tools.ietf.org</a>;
              <a moz-do-not-send="true"
                href="mailto:draft-ietf-mpls-tp-te-mib@tools.ietf.org">draft-ietf-mpls-tp-te-mib@tools.ietf.org</a><o:p></o:p></span></p>
          <p class="MsoPlainText"><span style="mso-ansi-language:EN-US"
              lang="EN-US">Subject: [mpls] seeking consensus on making
              draft-ietf-mpls-tp-te-mib read- only<o:p></o:p></span></p>
          <p class="MsoPlainText"><span style="mso-ansi-language:EN-US"
              lang="EN-US"><o:p>&nbsp;</o:p></span></p>
          <p class="MsoPlainText"><span style="mso-ansi-language:EN-US"
              lang="EN-US">Working Group,<o:p></o:p></span></p>
          <p class="MsoPlainText"><span style="mso-ansi-language:EN-US"
              lang="EN-US"><o:p>&nbsp;</o:p></span></p>
          <p class="MsoPlainText"><span style="mso-ansi-language:EN-US"
              lang="EN-US">We have just recalled
              draft-ietf-mpls-tp-te-mib from the IESG to the working
              group for more work. We have a series of comments that are
              mostly for clarification. However the main reason for
              recalling the document is that there is one point where we
              need to confirm working group consensus.<o:p></o:p></span></p>
          <p class="MsoPlainText"><span style="mso-ansi-language:EN-US"
              lang="EN-US"><o:p>&nbsp;</o:p></span></p>
          <p class="MsoPlainText"><span style="mso-ansi-language:EN-US"
              lang="EN-US">The IETF, the working group and the MIB
              Doctors are today very reluctant to produce read-write MIB
              modules. The current draft is read-write for a few
              objects, this is based on a consensus call for an earlier
              discussion, however the consensus call was not clear. It
              can be taken to mean both that we want to go with
              read-write objects and that we want to see read-only. Is
              it clear that it has been interpreted differently by
              different individuals.<o:p></o:p></span></p>
          <p class="MsoPlainText"><span style="mso-ansi-language:EN-US"
              lang="EN-US"><o:p>&nbsp;</o:p></span></p>
          <p class="MsoPlainText"><span style="mso-ansi-language:EN-US"
              lang="EN-US">The authors and chairs have discussed the
              issue and we have a rough consensus that we want the MIB
              module(s) to be read-only.<o:p></o:p></span></p>
          <p class="MsoPlainText"><span style="mso-ansi-language:EN-US"
              lang="EN-US"><o:p>&nbsp;</o:p></span></p>
          <p class="MsoPlainText"><span style="mso-ansi-language:EN-US"
              lang="EN-US">We therefore are asking the working group if
              this is OK for the MIB<o:p></o:p></span></p>
          <p class="MsoPlainText"><span style="mso-ansi-language:EN-US"
              lang="EN-US">module(s) in the current document. Please
              indicate Support or Oppose for this MIB
              (draft-ietf-mpls-tp-te-mib) to be read-only.<o:p></o:p></span></p>
          <p class="MsoPlainText"><span style="mso-ansi-language:EN-US"
              lang="EN-US"><o:p>&nbsp;</o:p></span></p>
          <p class="MsoPlainText"><span style="mso-ansi-language:EN-US"
              lang="EN-US">Please send your comments to the working
              group mailing list before February 18, 2014.<o:p></o:p></span></p>
          <p class="MsoPlainText"><span style="mso-ansi-language:EN-US"
              lang="EN-US"><o:p>&nbsp;</o:p></span></p>
          <p class="MsoPlainText"><span style="mso-ansi-language:EN-US"
              lang="EN-US">Loa<o:p></o:p></span></p>
          <p class="MsoPlainText"><span style="mso-ansi-language:EN-US"
              lang="EN-US">for the MPLS wg chairs<o:p></o:p></span></p>
          <p class="MsoPlainText"><span style="mso-ansi-language:EN-US"
              lang="EN-US">-- <o:p></o:p></span></p>
          <p class="MsoPlainText"><span style="mso-ansi-language:EN-US"
              lang="EN-US"><o:p>&nbsp;</o:p></span></p>
          <p class="MsoPlainText"><span style="mso-ansi-language:EN-US"
              lang="EN-US"><o:p>&nbsp;</o:p></span></p>
          <p class="MsoPlainText"><span style="mso-ansi-language:EN-US"
              lang="EN-US">Loa Andersson&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; email: <a
                moz-do-not-send="true"
                href="mailto:loa@mail01.huawei.com">loa@mail01.huawei.com</a><o:p></o:p></span></p>
          <p class="MsoPlainText"><span style="mso-ansi-language:EN-US"
              lang="EN-US">Senior MPLS Expert&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <a
                moz-do-not-send="true" href="mailto:loa@pi.nu">loa@pi.nu</a><o:p></o:p></span></p>
          <p class="MsoPlainText"><span style="mso-ansi-language:EN-US"
              lang="EN-US">Huawei Technologies (consultant)&nbsp;&nbsp;&nbsp;&nbsp; phone:
              +46 739 81 21 64<o:p></o:p></span></p>
          <p class="MsoPlainText"><span style="mso-ansi-language:EN-US"
              lang="EN-US">_______________________________________________<o:p></o:p></span></p>
          <p class="MsoPlainText"><span style="mso-ansi-language:EN-US"
              lang="EN-US">mpls mailing list<o:p></o:p></span></p>
          <p class="MsoPlainText"><span style="mso-ansi-language:EN-US"
              lang="EN-US"><a moz-do-not-send="true"
                href="mailto:mpls@ietf.org">mpls@ietf.org</a><o:p></o:p></span></p>
          <p class="MsoPlainText"><span style="mso-ansi-language:EN-US"
              lang="EN-US"><a moz-do-not-send="true"
                href="https://www.ietf.org/mailman/listinfo/mpls">https://www.ietf.org/mailman/listinfo/mpls</a><o:p></o:p></span></p>
          <p class="MsoPlainText"><span style="mso-ansi-language:EN-US"
              lang="EN-US">_______________________________________________<o:p></o:p></span></p>
          <p class="MsoPlainText"><span style="mso-ansi-language:EN-US"
              lang="EN-US">mpls mailing list<o:p></o:p></span></p>
          <p class="MsoPlainText"><span style="mso-ansi-language:EN-US"
              lang="EN-US"><a moz-do-not-send="true"
                href="mailto:mpls@ietf.org">mpls@ietf.org</a><o:p></o:p></span></p>
          <p class="MsoPlainText"><span style="mso-ansi-language:EN-US"
              lang="EN-US"><a moz-do-not-send="true"
                href="https://www.ietf.org/mailman/listinfo/mpls">https://www.ietf.org/mailman/listinfo/mpls</a><o:p></o:p></span></p>
          <p class="MsoNormal"><span style="mso-ansi-language:EN-US"
              lang="EN-US"><o:p>&nbsp;</o:p></span></p>
        </div>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
MIB-DOCTORS mailing list
<a class="moz-txt-link-abbreviated" href="mailto:MIB-DOCTORS@ietf.org">MIB-DOCTORS@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/mib-doctors">https://www.ietf.org/mailman/listinfo/mib-doctors</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------090806080004070802050504--


From bclaise@cisco.com  Wed Feb  5 06:30:01 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 B801E1A0192 for <mib-doctors@ietfa.amsl.com>; Wed,  5 Feb 2014 06:30:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.036
X-Spam-Level: 
X-Spam-Status: No, score=-15.036 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.535, 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 4-1PfexU-MIV for <mib-doctors@ietfa.amsl.com>; Wed,  5 Feb 2014 06:29:58 -0800 (PST)
Received: from mtv-iport-4.cisco.com (mtv-iport-4.cisco.com [173.36.130.15]) by ietfa.amsl.com (Postfix) with ESMTP id E50FA1A0180 for <mib-doctors@ietf.org>; Wed,  5 Feb 2014 06:29:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1258; q=dns/txt; s=iport; t=1391610598; x=1392820198; h=message-id:date:from:mime-version:to:subject:references: in-reply-to:content-transfer-encoding; bh=r4p1sIaDr62hbjpE0BYSCW+gZAnxTl3dvBpYiAVTTUM=; b=M9RLLCEpV504Ih0CPuDJsUjCvEK/lcma+/GjgQ2RVMMK9wOQS8Po8O58 liJFmhVHdb0xxCDmwpMUBW+5tBjD+UVc9RHZN/8QdWYjS2mOedpsljeN0 3H2sfadhc/WGFIKfaw8mZZAATOWMFARIJnxrwNt+niqI3zW2/xVZbxwpI U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AksKAIFK8lKrRDoG/2dsb2JhbABZgwy4M4QZgwaBDhZ0giUBAQEEOEARCxgJFg8JAwIBAgFFBgEMCAEBiADPSheOfIQ4AQOJSY5ihkiLWYNOGw
X-IronPort-AV: E=Sophos;i="4.95,786,1384300800"; d="scan'208";a="104879814"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by mtv-iport-4.cisco.com with ESMTP; 05 Feb 2014 14:29:58 +0000
Received: from [10.21.70.50] ([10.21.70.50]) by mtv-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id s15ETvrl031336; Wed, 5 Feb 2014 14:29:57 GMT
Message-ID: <52F24AE5.2020708@cisco.com>
Date: Wed, 05 Feb 2014 06:29:57 -0800
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Adrian Farrel <adrian@olddog.co.uk>, "'Joan Cucchiara'" <jcucchiara@mindspring.com>, mib-doctors@ietf.org
References: <05c501cf21ad$80d97ef0$828c7cd0$@olddog.co.uk> <00dc01cf21bf$45acdae0$d10690a0$@mindspring.com> <06e001cf21ed$1813a4a0$483aede0$@olddog.co.uk> <20140204224220.GA44274@elstar.local>
In-Reply-To: <20140204224220.GA44274@elstar.local>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [MIB-DOCTORS] Read-only MIB modules
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: Wed, 05 Feb 2014 14:30:01 -0000

On 4/02/2014 14:42, Juergen Schoenwaelder wrote:
> On Tue, Feb 04, 2014 at 09:07:20PM +0000, Adrian Farrel wrote:
>> Hello,
>>   
>> I thought that a compliance statement for this MIB module would
>> require only read access for the extended tables, and that all
>> objects in this module would be read-only.
> Sounds backwards from the SMIv2's notion of MAX-ACCESS. If you set
> MAX-ACCESS to read-only, then this thing can never be implemented
> read-write or read-create. This is why at some time in the past we
> started modeling MAX-ACCESS read-write with read-only conformance
> statements if a WG decides to do so and everyone could implement
> read-only and still claim compliance.
>
> We learned that it is a good thing to separate configuration from
> operational state and it used to be a WG decision whether the WG wants
> to tackle configuration via SNMP or not. I believe WGs need to take
> informed decisions and we should help them with that but be careful
> with 'strongly discouraging' writable SNMP MIB modules for
> configuration purposes (unless there is some evidence that WGs are
> unable to take informed decisions).
I have no problem to drop "strongly" in "strongly discourages"

Regards, Benoit
>
> /js
>


From j.schoenwaelder@jacobs-university.de  Wed Feb  5 06:33:51 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 D98161A01B9 for <mib-doctors@ietfa.amsl.com>; Wed,  5 Feb 2014 06:33:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.785
X-Spam-Level: 
X-Spam-Status: No, score=-2.785 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.535] 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 zbwx0WN4ngsi for <mib-doctors@ietfa.amsl.com>; Wed,  5 Feb 2014 06:33:49 -0800 (PST)
Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) by ietfa.amsl.com (Postfix) with ESMTP id 7838A1A01B1 for <mib-doctors@ietf.org>; Wed,  5 Feb 2014 06:33:49 -0800 (PST)
Received: from localhost (demetrius2.jacobs-university.de [212.201.44.47]) by hermes.jacobs-university.de (Postfix) with ESMTP id 696342003F; Wed,  5 Feb 2014 15:33:23 +0100 (CET)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius2.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id yHBmjvWbHVme; Wed,  5 Feb 2014 15:33:23 +0100 (CET)
Received: from elstar.local (elstar.jacobs.jacobs-university.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id 8C0DC20032; Wed,  5 Feb 2014 15:33:21 +0100 (CET)
Received: by elstar.local (Postfix, from userid 501) id 52CA92B107B0; Wed,  5 Feb 2014 15:33:20 +0100 (CET)
Date: Wed, 5 Feb 2014 15:33:20 +0100
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: Benoit Claise <bclaise@cisco.com>
Message-ID: <20140205143320.GC46555@elstar.local>
Mail-Followup-To: Benoit Claise <bclaise@cisco.com>, adrian@olddog.co.uk, "'Bert Wijnen (IETF)'" <bertietf@bwijnen.net>, 'Thomas Nadeau' <tnadeau@lucidvision.com>, "'Romascanu, Dan (Dan)'" <dromasca@avaya.com>, "'MIB Doctors (E-mail)'" <mib-doctors@ietf.org>
References: <9904FB1B0159DA42B0B887B7FA8119CA243D33C0@AZ-FFEXMB04.global.avaya.com> <FE705A2D-F9F0-4A41-A992-36705527C24A@lucidvision.com> <9904FB1B0159DA42B0B887B7FA8119CA243D3C0F@AZ-FFEXMB04.global.avaya.com> <556BB556-669F-4EF5-B8B0-4F1CD7E45BD0@lucidvision.com> <52DE928D.1090909@bwijnen.net> <0b2301cf16ce$bad3a3e0$307aeba0$@olddog.co.uk> <52DF9D02.6070306@cisco.com> <52EE4EF1.3000102@cisco.com> <20140202144457.GA35917@elstar.local> <52F246FB.8010403@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <52F246FB.8010403@cisco.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: adrian@olddog.co.uk, "'MIB Doctors \(E-mail\)'" <mib-doctors@ietf.org>
Subject: Re: [MIB-DOCTORS] Why is this MIB module read-write?
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: Wed, 05 Feb 2014 14:33:52 -0000

On Wed, Feb 05, 2014 at 06:13:15AM -0800, Benoit Claise wrote:
> On 2/02/2014 06:44, Juergen Schoenwaelder wrote:
> >On Sun, Feb 02, 2014 at 02:58:09PM +0100, Benoit Claise wrote:
> >>Mib doctors,
> >>
> >>It's time to improve the following statement, to propose it to the
> >>OPS area, and if all goes well o make an IESG statement out of it.
> >>
> >>    "The OPS Area henceforth strongly discourages the pursuit of
> >>    writable SNMP MIBs for configuration purposes by working groups
> >>    except in cases of clear utility and overwhelming consensus to do
> >>    so. In all other cases, we recommend the use of NETCONF/YANG IETF
> >>    standards for configuration, specifically in new charters."
> >>
> >>I re-read the email thread, and want to make the following changes:
> >>- Add IETF. It was mentioned that some other SDOs might still be
> >>using SNMP for configuration: IEEE, DOCSIS
> >>- Add "for complete features or services" configuration. I want to
> >>address Chirs' point that SNMPSet for starting an action might be OK
> >>(router reload, start config download)
> >Since what Chirs is talking about s not configuration, I think the
> >original text was already OK. I am not sure people will easily
> >understand what 'complete features/services configuration' means.  I
> >also do not know what the difference between 'discourage' and
> >'strictly discourage' is.
> Then how should be call "such as enable/disable notifications" if
> this is not configuration.

OK, this can be configuration or not, depending on whether the change
is persistent and not.
 
>    "The OPS Area henceforth strongly discourages the pursuit of
>    writable SNMP MIB modules for complete features/services
>    configuration purposes by IETF working groups, except in cases of
>    clear utility and consensus to do so. Using SNMPSet to simple
>    configuration, such as enable/disable notifications or initiating an
>    action,  might be appropriate though.  In all other cases, we
>    recommend the use of NETCONF/YANG IETF standards for configuration,
>    specifically in new charters."

I would rather write a positive statement instead of a negative one.
Something like this:

  The OPS area recommends the use of NETCONF/YANG standards for
  configuration. IETF working groups are therefore encouraged to use
  the NETCONF/YANG standards for configuration, specifically in new
  charters. SNMP MIB modules modifying persistent configuration state
  should only be produced by working groups in cases of clear utility
  and overwhelming consensus to use SNMP write operations for
  configuration.

Note that this statement limits the discussion to configuration data.
Note also that there is no standard way to modify operational state
via NETCONF at this point in time (so it would be strange to discourage
SNMP if there is no standardized alternative).

/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 tnadeau@lucidvision.com  Wed Feb  5 06:38:24 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 8E4EA1A0186 for <mib-doctors@ietfa.amsl.com>; Wed,  5 Feb 2014 06:38:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.433
X-Spam-Level: 
X-Spam-Status: No, score=-2.433 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RP_MATCHES_RCVD=-0.535] 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 fYO-97y7OKS1 for <mib-doctors@ietfa.amsl.com>; Wed,  5 Feb 2014 06:38:23 -0800 (PST)
Received: from lucidvision.com (lucidvision.com [72.71.250.34]) by ietfa.amsl.com (Postfix) with ESMTP id 7F5471A015B for <mib-doctors@ietf.org>; Wed,  5 Feb 2014 06:38:22 -0800 (PST)
Received: from [10.9.247.162] (mobile-166-137-187-011.mycingular.net [166.137.187.11]) by lucidvision.com (Postfix) with ESMTP id 2C78A26DDAF8; Wed,  5 Feb 2014 09:38:21 -0500 (EST)
References: <52DD5FFC.8070103@cisco.com> <20140121094726.GB47210@elstar.local> <9904FB1B0159DA42B0B887B7FA8119CA243D33C0@AZ-FFEXMB04.global.avaya.com> <FE705A2D-F9F0-4A41-A992-36705527C24A@lucidvision.com> <9904FB1B0159DA42B0B887B7FA8119CA243D3C0F@AZ-FFEXMB04.global.avaya.com> <556BB556-669F-4EF5-B8B0-4F1CD7E45BD0@lucidvision.com> <52DE928D.1090909@bwijnen.net> <0b2301cf16ce$bad3a3e0$307aeba0$@olddog.co.uk> <52DF9D02.6070306@cisco.com> <52EE4EF1.3000102@cisco.com> <20140202144457.GA35917@elstar.local> <52F246FB.8010403@cisco.com> <9904FB1B0159DA42B0B887B7FA8119CA2E3ECF99@AZ-FFEXMB04.global.avaya.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: <9904FB1B0159DA42B0B887B7FA8119CA2E3ECF99@AZ-FFEXMB04.global.avaya.com>
Content-Type: multipart/alternative; boundary=Apple-Mail-162F32EE-4C1E-44AD-B455-F63D3AA687C7
Content-Transfer-Encoding: 7bit
Message-Id: <013CA85E-B97E-479D-A763-6186D99B6A14@lucidvision.com>
X-Mailer: iPhone Mail (11B554a)
From: "Thomas D. Nadeau" <tnadeau@lucidvision.com>
Date: Wed, 5 Feb 2014 06:38:19 -0800
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
Cc: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "MIB Doctors \(E-mail\)" <mib-doctors@ietf.org>
Subject: Re: [MIB-DOCTORS] Why is this MIB module read-write?
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: Wed, 05 Feb 2014 14:38:24 -0000

--Apple-Mail-162F32EE-4C1E-44AD-B455-F63D3AA687C7
Content-Type: text/plain;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

good point. the idea is to discourage any "configuration" operations.

Tom=20


> On Feb 5, 2014, at 6:22 AM, "Romascanu, Dan (Dan)" <dromasca@avaya.com> wr=
ote:
>=20
> Following the discussions we are having =E2=80=93 we should probably add t=
o enable/disable notifications also creation and deletion of dynamic rows us=
ing the RowStatus TC.
> =20
> Regards,
> =20
> Dan
> =20
> =20
> From: Benoit Claise [mailto:bclaise@cisco.com]=20
> Sent: =D7=99=D7=95=D7=9D =D7=93 05 =D7=A4=D7=91=D7=A8=D7=95=D7=90=D7=A8 20=
14 16:13
> To: adrian@olddog.co.uk; 'Bert Wijnen (IETF)'; 'Thomas Nadeau'; Romascanu,=
 Dan (Dan); 'MIB Doctors (E-mail)'
> Subject: Re: [MIB-DOCTORS] Why is this MIB module read-write?
> =20
> On 2/02/2014 06:44, Juergen Schoenwaelder wrote:
> On Sun, Feb 02, 2014 at 02:58:09PM +0100, Benoit Claise wrote:
> Mib doctors,
> =20
> It's time to improve the following statement, to propose it to the
> OPS area, and if all goes well o make an IESG statement out of it.
> =20
>    "The OPS Area henceforth strongly discourages the pursuit of
>    writable SNMP MIBs for configuration purposes by working groups
>    except in cases of clear utility and overwhelming consensus to do
>    so. In all other cases, we recommend the use of NETCONF/YANG IETF
>    standards for configuration, specifically in new charters."
> =20
> I re-read the email thread, and want to make the following changes:
> - Add IETF. It was mentioned that some other SDOs might still be
> using SNMP for configuration: IEEE, DOCSIS
> - Add "for complete features or services" configuration. I want to
> address Chirs' point that SNMPSet for starting an action might be OK
> (router reload, start config download)
> =20
> Since what Chirs is talking about s not configuration, I think the
> original text was already OK. I am not sure people will easily
> understand what 'complete features/services configuration' means.  I
> also do not know what the difference between 'discourage' and
> 'strictly discourage' is.
> Then how should be call "such as enable/disable notifications" if this is n=
ot configuration.
> "The OPS Area henceforth strongly discourages the pursuit of writable SNMP=
 MIB modules for complete features/services configuration purposes by IETF w=
orking groups, except in cases of clear utility and consensus to do so. Usin=
g SNMPSet to simple configuration, such as enable/disable notifications or i=
nitiating an action,  might be appropriate though.  In all other cases, we r=
ecommend the use of NETCONF/YANG IETF standards for configuration, specifica=
lly in new charters."
>=20
> Regards, Benoit
>=20
> =20
> =20
> /js
> =20
> PS: Strictly speaking from an SMIv2 standpoint, I am not sure how to
>     use the MAX-ACCESS clause anymore. ;-}
> =20
>      The MAX-ACCESS clause, which must be present, defines whether it
>      makes "protocol sense" to read, write and/or create an instance of
>      the object, or to include its value in a notification.  This is the
>      maximal level of access for the object.  (This maximal level of
>      access is independent of any administrative authorization policy.)
> =20
> =20

--Apple-Mail-162F32EE-4C1E-44AD-B455-F63D3AA687C7
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=3D=
utf-8"></head><body dir=3D"auto"><div>good point. the idea is to discourage a=
ny "configuration" operations.</div><div><br></div><div>Tom&nbsp;</div><div>=
<br></div><div><br>On Feb 5, 2014, at 6:22 AM, "Romascanu, Dan (Dan)" &lt;<a=
 href=3D"mailto:dromasca@avaya.com">dromasca@avaya.com</a>&gt; wrote:<br><br=
></div><blockquote type=3D"cite"><div>

<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dwindows-12=
55">
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@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;}
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 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></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]-->


<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Cal=
ibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Following the discussions w=
e are having =E2=80=93 we should probably add to enable/disable notification=
s also creation and deletion of dynamic rows using the RowStatus
 TC. <o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Cal=
ibri&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;Cal=
ibri&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;Cal=
ibri&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;Cal=
ibri&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;Cal=
ibri&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;Cal=
ibri&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 0=
cm 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><span s=
tyle=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quo=
t;;color:windowtext"> Benoit Claise [<a href=3D"mailto:bclaise@cisco.com">ma=
ilto:bclaise@cisco.com</a>]
<br>
<b>Sent:</b> <span lang=3D"HE" dir=3D"RTL">=D7=99=D7=95=D7=9D</span><span di=
r=3D"LTR"></span><span dir=3D"LTR"></span><span dir=3D"LTR"></span><span dir=
=3D"LTR"></span>&nbsp;<span lang=3D"HE" dir=3D"RTL">=D7=93</span><span dir=3D=
"LTR"></span><span dir=3D"LTR"></span><span dir=3D"LTR"></span><span dir=3D"=
LTR"></span>
 05 <span lang=3D"HE" dir=3D"RTL">=D7=A4=D7=91=D7=A8=D7=95=D7=90=D7=A8</span=
><span dir=3D"LTR"></span><span dir=3D"LTR"></span><span dir=3D"LTR"></span>=
<span dir=3D"LTR"></span> 2014 16:13<br>
<b>To:</b> <a href=3D"mailto:adrian@olddog.co.uk">adrian@olddog.co.uk</a>; '=
Bert Wijnen (IETF)'; 'Thomas Nadeau'; Romascanu, Dan (Dan); 'MIB Doctors (E-=
mail)'<br>
<b>Subject:</b> Re: [MIB-DOCTORS] Why is this MIB module read-write?<o:p></o=
:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">On 2/02/2014 06:44, Juergen Schoenwaelder wrote:<o:p>=
</o:p></p>
</div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<pre>On Sun, Feb 02, 2014 at 02:58:09PM +0100, Benoit Claise wrote:<o:p></o:=
p></pre>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<pre>Mib doctors,<o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>It's time to improve the following statement, to propose it to the<o:p>=
</o:p></pre>
<pre>OPS area, and if all goes well o make an IESG statement out of it.<o:p>=
</o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>&nbsp;&nbsp; "The OPS Area henceforth strongly discourages the pursuit o=
f<o:p></o:p></pre>
<pre>&nbsp;&nbsp; writable SNMP MIBs for configuration purposes by working g=
roups<o:p></o:p></pre>
<pre>&nbsp;&nbsp; except in cases of clear utility and overwhelming consensu=
s to do<o:p></o:p></pre>
<pre>&nbsp;&nbsp; so. In all other cases, we recommend the use of NETCONF/YA=
NG IETF<o:p></o:p></pre>
<pre>&nbsp;&nbsp; standards for configuration, specifically in new charters.=
"<o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>I re-read the email thread, and want to make the following changes:<o:p=
></o:p></pre>
<pre>- Add IETF. It was mentioned that some other SDOs might still be<o:p></=
o:p></pre>
<pre>using SNMP for configuration: IEEE, DOCSIS<o:p></o:p></pre>
<pre>- Add "for complete features or services" configuration. I want to<o:p>=
</o:p></pre>
<pre>address Chirs' point that SNMPSet for starting an action might be OK<o:=
p></o:p></pre>
<pre>(router reload, start config download)<o:p></o:p></pre>
</blockquote>
<pre><o:p>&nbsp;</o:p></pre>
<pre>Since what Chirs is talking about s not configuration, I think the<o:p>=
</o:p></pre>
<pre>original text was already OK. I am not sure people will easily<o:p></o:=
p></pre>
<pre>understand what 'complete features/services configuration' means.&nbsp;=
 I<o:p></o:p></pre>
<pre>also do not know what the difference between 'discourage' and<o:p></o:p=
></pre>
<pre>'strictly discourage' is.<o:p></o:p></pre>
</blockquote>
<p class=3D"MsoNormal">Then how should be call "such as enable/disable notif=
ications" if this is not configuration.<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">"The OPS Area hencefor=
th strongly discourages the pursuit of writable SNMP MIB modules for complet=
e features/services configuration purposes by IETF working groups, except in=
 cases of clear utility and consensus
 to do so. Using SNMPSet to simple configuration, such as enable/disable not=
ifications or initiating an action,&nbsp; might be appropriate though.&nbsp;=
 In all other cases, we recommend the use of NETCONF/YANG IETF standards for=
 configuration, specifically in new charters."<o:p></o:p></p>
<p class=3D"MsoNormal">Regards, Benoit<br>
<br>
<o:p></o:p></p>
<pre><o:p>&nbsp;</o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>/js<o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>PS: Strictly speaking from an SMIv2 standpoint, I am not sure how to<o:=
p></o:p></pre>
<pre>&nbsp;&nbsp;&nbsp; use the MAX-ACCESS clause anymore. ;-}<o:p></o:p></p=
re>
<pre><o:p>&nbsp;</o:p></pre>
<pre>&nbsp;&nbsp;&nbsp;&nbsp; The MAX-ACCESS clause, which must be present, d=
efines whether it<o:p></o:p></pre>
<pre>&nbsp;&nbsp;&nbsp;&nbsp; makes "protocol sense" to read, write and/or c=
reate an instance of<o:p></o:p></pre>
<pre>&nbsp;&nbsp;&nbsp;&nbsp; the object, or to include its value in a notif=
ication.&nbsp; This is the<o:p></o:p></pre>
<pre>&nbsp;&nbsp;&nbsp;&nbsp; maximal level of access for the object.&nbsp; (=
This maximal level of<o:p></o:p></pre>
<pre>&nbsp;&nbsp;&nbsp;&nbsp; access is independent of any administrative au=
thorization policy.)<o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>


</div></blockquote></body></html>=

--Apple-Mail-162F32EE-4C1E-44AD-B455-F63D3AA687C7--

From tnadeau@lucidvision.com  Wed Feb  5 06:48:45 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 523081A0193 for <mib-doctors@ietfa.amsl.com>; Wed,  5 Feb 2014 06:48:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.435
X-Spam-Level: 
X-Spam-Status: No, score=-2.435 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.535] 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 vqhgqlbuMeSk for <mib-doctors@ietfa.amsl.com>; Wed,  5 Feb 2014 06:48:43 -0800 (PST)
Received: from lucidvision.com (lucidvision.com [72.71.250.34]) by ietfa.amsl.com (Postfix) with ESMTP id 5959A1A0198 for <mib-doctors@ietf.org>; Wed,  5 Feb 2014 06:48:43 -0800 (PST)
Received: from [10.9.247.162] (mobile-166-137-187-011.mycingular.net [166.137.187.11]) by lucidvision.com (Postfix) with ESMTP id 3CC9526DDD3C; Wed,  5 Feb 2014 09:48:42 -0500 (EST)
References: <9904FB1B0159DA42B0B887B7FA8119CA243D33C0@AZ-FFEXMB04.global.avaya.com> <FE705A2D-F9F0-4A41-A992-36705527C24A@lucidvision.com> <9904FB1B0159DA42B0B887B7FA8119CA243D3C0F@AZ-FFEXMB04.global.avaya.com> <556BB556-669F-4EF5-B8B0-4F1CD7E45BD0@lucidvision.com> <52DE928D.1090909@bwijnen.net> <0b2301cf16ce$bad3a3e0$307aeba0$@olddog.co.uk> <52DF9D02.6070306@cisco.com> <52EE4EF1.3000102@cisco.com> <20140202144457.GA35917@elstar.local> <52F246FB.8010403@cisco.com> <20140205143320.GC46555@elstar.local>
Mime-Version: 1.0 (1.0)
In-Reply-To: <20140205143320.GC46555@elstar.local>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <539FBA03-155E-41B3-8618-C2B46887553E@lucidvision.com>
X-Mailer: iPhone Mail (11B554a)
From: "Thomas D. Nadeau" <tnadeau@lucidvision.com>
Date: Wed, 5 Feb 2014 06:48:40 -0800
To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
Cc: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "MIB Doctors \(E-mail\)" <mib-doctors@ietf.org>
Subject: Re: [MIB-DOCTORS] Why is this MIB module read-write?
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: Wed, 05 Feb 2014 14:48:45 -0000

we could be picky and discuss running versus persistent configuration but th=
at's missing the issue: most providers disable snmp write regardless of ulti=
mate configuration state.

Tom=20


> On Feb 5, 2014, at 6:33 AM, Juergen Schoenwaelder <j.schoenwaelder@jacobs-=
university.de> wrote:
>=20
>> On Wed, Feb 05, 2014 at 06:13:15AM -0800, Benoit Claise wrote:
>>> On 2/02/2014 06:44, Juergen Schoenwaelder wrote:
>>>> On Sun, Feb 02, 2014 at 02:58:09PM +0100, Benoit Claise wrote:
>>>> Mib doctors,
>>>>=20
>>>> It's time to improve the following statement, to propose it to the
>>>> OPS area, and if all goes well o make an IESG statement out of it.
>>>>=20
>>>>   "The OPS Area henceforth strongly discourages the pursuit of
>>>>   writable SNMP MIBs for configuration purposes by working groups
>>>>   except in cases of clear utility and overwhelming consensus to do
>>>>   so. In all other cases, we recommend the use of NETCONF/YANG IETF
>>>>   standards for configuration, specifically in new charters."
>>>>=20
>>>> I re-read the email thread, and want to make the following changes:
>>>> - Add IETF. It was mentioned that some other SDOs might still be
>>>> using SNMP for configuration: IEEE, DOCSIS
>>>> - Add "for complete features or services" configuration. I want to
>>>> address Chirs' point that SNMPSet for starting an action might be OK
>>>> (router reload, start config download)
>>> Since what Chirs is talking about s not configuration, I think the
>>> original text was already OK. I am not sure people will easily
>>> understand what 'complete features/services configuration' means.  I
>>> also do not know what the difference between 'discourage' and
>>> 'strictly discourage' is.
>> Then how should be call "such as enable/disable notifications" if
>> this is not configuration.
>=20
> OK, this can be configuration or not, depending on whether the change
> is persistent and not.
>=20
>>   "The OPS Area henceforth strongly discourages the pursuit of
>>   writable SNMP MIB modules for complete features/services
>>   configuration purposes by IETF working groups, except in cases of
>>   clear utility and consensus to do so. Using SNMPSet to simple
>>   configuration, such as enable/disable notifications or initiating an
>>   action,  might be appropriate though.  In all other cases, we
>>   recommend the use of NETCONF/YANG IETF standards for configuration,
>>   specifically in new charters."
>=20
> I would rather write a positive statement instead of a negative one.
> Something like this:
>=20
>  The OPS area recommends the use of NETCONF/YANG standards for
>  configuration. IETF working groups are therefore encouraged to use
>  the NETCONF/YANG standards for configuration, specifically in new
>  charters. SNMP MIB modules modifying persistent configuration state
>  should only be produced by working groups in cases of clear utility
>  and overwhelming consensus to use SNMP write operations for
>  configuration.
>=20
> Note that this statement limits the discussion to configuration data.
> Note also that there is no standard way to modify operational state
> via NETCONF at this point in time (so it would be strange to discourage
> SNMP if there is no standardized alternative).
>=20
> /js
>=20
> --=20
> Juergen Schoenwaelder           Jacobs University Bremen gGmbH
> Phone: +49 421 200 3587         Campus Ring 1, 28759 Bremen, Germany
> Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>
>=20

From j.schoenwaelder@jacobs-university.de  Wed Feb  5 07:05:51 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 C15951A016E for <mib-doctors@ietfa.amsl.com>; Wed,  5 Feb 2014 07:05:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.785
X-Spam-Level: 
X-Spam-Status: No, score=-2.785 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.535] 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 Jq4WPmaCGuCq for <mib-doctors@ietfa.amsl.com>; Wed,  5 Feb 2014 07:05:49 -0800 (PST)
Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) by ietfa.amsl.com (Postfix) with ESMTP id 3607B1A00FD for <mib-doctors@ietf.org>; Wed,  5 Feb 2014 07:05:49 -0800 (PST)
Received: from localhost (demetrius2.jacobs-university.de [212.201.44.47]) by hermes.jacobs-university.de (Postfix) with ESMTP id 43BFC2013D; Wed,  5 Feb 2014 16:05:48 +0100 (CET)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius2.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id xjXO8pWDkBeb; Wed,  5 Feb 2014 16:05:48 +0100 (CET)
Received: from elstar.local (elstar.jacobs.jacobs-university.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id 96A652013C; Wed,  5 Feb 2014 16:05:47 +0100 (CET)
Received: by elstar.local (Postfix, from userid 501) id 7D7172B10A41; Wed,  5 Feb 2014 16:05:46 +0100 (CET)
Date: Wed, 5 Feb 2014 16:05:46 +0100
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: "Thomas D. Nadeau" <tnadeau@lucidvision.com>
Message-ID: <20140205150546.GA46787@elstar.local>
Mail-Followup-To: "Thomas D. Nadeau" <tnadeau@lucidvision.com>, Benoit Claise <bclaise@cisco.com>, "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "Bert Wijnen (IETF)" <bertietf@bwijnen.net>, "Romascanu, Dan (Dan)" <dromasca@avaya.com>, "MIB Doctors (E-mail)" <mib-doctors@ietf.org>
References: <9904FB1B0159DA42B0B887B7FA8119CA243D3C0F@AZ-FFEXMB04.global.avaya.com> <556BB556-669F-4EF5-B8B0-4F1CD7E45BD0@lucidvision.com> <52DE928D.1090909@bwijnen.net> <0b2301cf16ce$bad3a3e0$307aeba0$@olddog.co.uk> <52DF9D02.6070306@cisco.com> <52EE4EF1.3000102@cisco.com> <20140202144457.GA35917@elstar.local> <52F246FB.8010403@cisco.com> <20140205143320.GC46555@elstar.local> <539FBA03-155E-41B3-8618-C2B46887553E@lucidvision.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <539FBA03-155E-41B3-8618-C2B46887553E@lucidvision.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "MIB Doctors \(E-mail\)" <mib-doctors@ietf.org>
Subject: Re: [MIB-DOCTORS] Why is this MIB module read-write?
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: Wed, 05 Feb 2014 15:05:51 -0000

On Wed, Feb 05, 2014 at 06:48:40AM -0800, Thomas D. Nadeau wrote:

> we could be picky and discuss running versus persistent
> configuration but that's missing the issue: most providers disable
> snmp write regardless of ultimate configuration state.

Having worked on replacement technology for SNMP for a couple of years
now, I think I do understand the issues and concerns. But then I also
know that there are networks that are not 'provider' networks. I still
believe in positive encouragement to use alternatives (where they
exist) and informed decisions by WGs.

/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 jcucchiara@mindspring.com  Wed Feb  5 07:08:42 2014
Return-Path: <jcucchiara@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 9D2BC1A019E for <mib-doctors@ietfa.amsl.com>; Wed,  5 Feb 2014 07:08:42 -0800 (PST)
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 PxomtAzkJuNV for <mib-doctors@ietfa.amsl.com>; Wed,  5 Feb 2014 07:08:40 -0800 (PST)
Received: from elasmtp-spurfowl.atl.sa.earthlink.net (elasmtp-spurfowl.atl.sa.earthlink.net [209.86.89.66]) by ietfa.amsl.com (Postfix) with ESMTP id CE7611A015B for <mib-doctors@ietf.org>; Wed,  5 Feb 2014 07:08:39 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=JWxeF1TLg11O1y8aqlN0efcFN0cstKP+M+HlvlFAIeEd3soVHEMA/hjf9rf+eeXe; h=Received:From:To:Cc:References:In-Reply-To:Subject:Date:Message-ID:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Mailer:Thread-Index:Content-language:X-ELNK-Trace:X-Originating-IP;
Received: from [24.41.69.138] (helo=JoanTower) by elasmtp-spurfowl.atl.sa.earthlink.net with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.67) (envelope-from <jcucchiara@mindspring.com>) id 1WB45X-0008Nu-Dg; Wed, 05 Feb 2014 10:08:31 -0500
From: "Joan Cucchiara" <jcucchiara@mindspring.com>
To: "'Juergen Schoenwaelder'" <j.schoenwaelder@jacobs-university.de>, "'Adrian Farrel'" <adrian@olddog.co.uk>
References: <05c501cf21ad$80d97ef0$828c7cd0$@olddog.co.uk> <00dc01cf21bf$45acdae0$d10690a0$@mindspring.com> <06e001cf21ed$1813a4a0$483aede0$@olddog.co.uk> <20140204224220.GA44274@elstar.local>
In-Reply-To: <20140204224220.GA44274@elstar.local>
Date: Wed, 5 Feb 2014 10:08:29 -0500
Message-ID: <016c01cf2284$21a25d30$64e71790$@mindspring.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQFJjvDrKd3WqTHnQB+4M0ubo7RGRAFy1q1JAuiFd/AA2LLH2ZuIPN8w
Content-language: en-us
X-ELNK-Trace: 4d68bbe9cb71969ea344cf2d1a8e60840a9da525759e2654adc1e8722bb42f900b696a9faf82d00fb5548f7b21afc86f350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 24.41.69.138
Cc: mib-doctors@ietf.org
Subject: Re: [MIB-DOCTORS] Read-only MIB modules
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: Wed, 05 Feb 2014 15:08:42 -0000

So, it's sounds like there are 2 different discussions going on here:
specifically making this draft read-only and WG migration to using NetConf
for configuration.  

Wrt the draft, this should remain read-write as it is tied to 2 legacy MIBs
(LSR and TE MIBs).   Technically, I don't see how a purely read-only for the
draft is viable (and yes, maybe there is a way, but I don't see it.) 

For the migration issue, I tend to agree with Juergen.    It is really up to
the WGs in my opinion.    Vendors don't tend to migrate to a new technology
unless their customers want it.   Perhaps, reaching out to
customers/operators should be a focus (and maybe this is already being
done?) .   Also, I think a continuation of providing support in the way of
educational tutorials, web pages, etc. and other assistance to WGs is
crucial.  

Maybe some of you are having a different experience, but in the last 6
months, I've consulted for a startup that started with YANG and NetConf and
also did a proposal for another company where I recommended NetConf and Yang
and that was proposed since they didn't want to use SNMP for configuration.
I don't see such a resistance to adoption of using NetConf for configuration
and yes, my experience is somewhat limited, but just wanted to say, I've
seen some positive attitudes towards adoption of YANG and NetConf already.

Thanks,
  -Joan


-----Original Message-----
From: Juergen Schoenwaelder [mailto:j.schoenwaelder@jacobs-university.de] 
Sent: Tuesday, February 04, 2014 5:42 PM
To: Adrian Farrel
Cc: 'Joan Cucchiara'; mib-doctors@ietf.org
Subject: Re: [MIB-DOCTORS] Read-only MIB modules

On Tue, Feb 04, 2014 at 09:07:20PM +0000, Adrian Farrel wrote:
> Hello,
>  
> I thought that a compliance statement for this MIB module would 
> require only read access for the extended tables, and that all objects 
> in this module would be read-only.

Sounds backwards from the SMIv2's notion of MAX-ACCESS. If you set
MAX-ACCESS to read-only, then this thing can never be implemented read-write
or read-create. This is why at some time in the past we started modeling
MAX-ACCESS read-write with read-only conformance statements if a WG decides
to do so and everyone could implement read-only and still claim compliance.

We learned that it is a good thing to separate configuration from
operational state and it used to be a WG decision whether the WG wants to
tackle configuration via SNMP or not. I believe WGs need to take informed
decisions and we should help them with that but be careful with 'strongly
discouraging' writable SNMP MIB modules for configuration purposes (unless
there is some evidence that WGs are unable to take informed decisions).

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


-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2014.0.4259 / Virus Database: 3684/7061 - Release Date: 02/04/14


From macfaden@gmail.com  Wed Feb  5 07:34:23 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 1DE561A0192 for <mib-doctors@ietfa.amsl.com>; Wed,  5 Feb 2014 07:34:23 -0800 (PST)
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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=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 Pfjub27FCguU for <mib-doctors@ietfa.amsl.com>; Wed,  5 Feb 2014 07:34:22 -0800 (PST)
Received: from mail-qc0-x22a.google.com (mail-qc0-x22a.google.com [IPv6:2607:f8b0:400d:c01::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 0B24C1A016F for <mib-doctors@ietf.org>; Wed,  5 Feb 2014 07:34:21 -0800 (PST)
Received: by mail-qc0-f170.google.com with SMTP id e9so865769qcy.29 for <mib-doctors@ietf.org>; Wed, 05 Feb 2014 07:34:21 -0800 (PST)
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=6ZEaQ7zMuT5AgIBJYWy03x5Rhaz2gqy2+Dz2jxI/DxQ=; b=sGHqavMtY7jR1n7U9y44nUkUgHdyE1DgjgC3K+20IJcI97r1XN9ull1mMPnIvl7Vvc WjidxhhhTNaOAj8NMfYHnntB76foX1ZtoTagywzphqwlvXj/BrrxxqHlYhr6GAPVRPH6 mpZwWw0CoM6okLn1i7UWLecctfLUMyG0arUm+H38Ga4PRQFCPoNbDZnzjmw/+X2uFhjc JJxITKmxV2pXU9lKeFtOfM/8wsFke6yftnlHXFWRv/ukC6G8KF1RgXcbOZYsdEnD5wB1 bagLqDMY5O2JcUnmRA3ZWmBbkTqREhpeC99ArADV7axsRALhA4u+XzahOFym9PuBkeiz B6zQ==
MIME-Version: 1.0
X-Received: by 10.140.38.11 with SMTP id s11mr3426019qgs.62.1391614461202; Wed, 05 Feb 2014 07:34:21 -0800 (PST)
Sender: macfaden@gmail.com
Received: by 10.140.80.46 with HTTP; Wed, 5 Feb 2014 07:34:21 -0800 (PST)
In-Reply-To: <20140205143320.GC46555@elstar.local>
References: <9904FB1B0159DA42B0B887B7FA8119CA243D33C0@AZ-FFEXMB04.global.avaya.com> <FE705A2D-F9F0-4A41-A992-36705527C24A@lucidvision.com> <9904FB1B0159DA42B0B887B7FA8119CA243D3C0F@AZ-FFEXMB04.global.avaya.com> <556BB556-669F-4EF5-B8B0-4F1CD7E45BD0@lucidvision.com> <52DE928D.1090909@bwijnen.net> <0b2301cf16ce$bad3a3e0$307aeba0$@olddog.co.uk> <52DF9D02.6070306@cisco.com> <52EE4EF1.3000102@cisco.com> <20140202144457.GA35917@elstar.local> <52F246FB.8010403@cisco.com> <20140205143320.GC46555@elstar.local>
Date: Wed, 5 Feb 2014 07:34:21 -0800
X-Google-Sender-Auth: u_20yf8fqdxlyjJCS0iz5T33jS8
Message-ID: <CAD3a8T=R5dDcFsQaOZzE5iiJMS0axjStXUhbS8DsuxBLy4Ax6g@mail.gmail.com>
From: Michael MacFaden <mrm@macfaden.com>
To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>, Benoit Claise <bclaise@cisco.com>,  adrian@olddog.co.uk, "Bert Wijnen (IETF)" <bertietf@bwijnen.net>,  Thomas Nadeau <tnadeau@lucidvision.com>, "Romascanu, Dan (Dan)" <dromasca@avaya.com>,  "MIB Doctors (E-mail)" <mib-doctors@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [MIB-DOCTORS] Why is this MIB module read-write?
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: Wed, 05 Feb 2014 15:34:23 -0000

> I would rather write a positive statement instead of a negative one.
...

I agree Juergen's comments.

Mike MacFaden

From bertietf@bwijnen.net  Wed Feb  5 07:40:15 2014
Return-Path: <bertietf@bwijnen.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 C861E1A01F6 for <mib-doctors@ietfa.amsl.com>; Wed,  5 Feb 2014 07:40:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 k0fMnWTJiWss for <mib-doctors@ietfa.amsl.com>; Wed,  5 Feb 2014 07:40:14 -0800 (PST)
Received: from koko.ripe.net (koko.ripe.net [193.0.19.72]) by ietfa.amsl.com (Postfix) with ESMTP id 2DDFC1A0192 for <mib-doctors@ietf.org>; Wed,  5 Feb 2014 07:40:14 -0800 (PST)
Received: from nene.ripe.net ([193.0.23.10]) by koko.ripe.net with esmtps (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from <bertietf@bwijnen.net>) id 1WB4a4-0000Rw-0U; Wed, 05 Feb 2014 16:40:10 +0100
Received: from kitten.ipv6.ripe.net ([2001:67c:2e8:1::c100:1f0] helo=Macintosh.local) by nene.ripe.net with esmtp (Exim 4.72) (envelope-from <bertietf@bwijnen.net>) id 1WB4a3-000832-Qj; Wed, 05 Feb 2014 16:40:03 +0100
Message-ID: <52F25B53.9090208@bwijnen.net>
Date: Wed, 05 Feb 2014 16:40:03 +0100
From: "Bert Wijnen (IETF)" <bertietf@bwijnen.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Benoit Claise <bclaise@cisco.com>, adrian@olddog.co.uk,  'Thomas Nadeau' <tnadeau@lucidvision.com>, "'Romascanu, Dan (Dan)'" <dromasca@avaya.com>,  "'MIB Doctors (E-mail)'" <mib-doctors@ietf.org>
References: <9904FB1B0159DA42B0B887B7FA8119CA243D33C0@AZ-FFEXMB04.global.avaya.com> <FE705A2D-F9F0-4A41-A992-36705527C24A@lucidvision.com> <9904FB1B0159DA42B0B887B7FA8119CA243D3C0F@AZ-FFEXMB04.global.avaya.com> <556BB556-669F-4EF5-B8B0-4F1CD7E45BD0@lucidvision.com> <52DE928D.1090909@bwijnen.net> <0b2301cf16ce$bad3a3e0$307aeba0$@olddog.co.uk> <52DF9D02.6070306@cisco.com> <52EE4EF1.3000102@cisco.com> <20140202144457.GA35917@elstar.local> <52F246FB.8010403@cisco.com> <20140205143320.GC46555@elstar.local>
In-Reply-To: <20140205143320.GC46555@elstar.local>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-RIPE-Spam-Level: --
X-RIPE-Spam-Report: Spam Total Points:   -2.9 points pts rule name              description ---- ---------------------- ------------------------------------ -1.0 ALL_TRUSTED            Passed through trusted hosts only via SMTP -1.9 BAYES_00               BODY: Bayes spam probability is 0 to 1% [score: 0.0000]
X-RIPE-Signature: 86ab03e524994f79ca2c75a176445dd42bc853f619f6ad95413a53b930a21f63
Subject: Re: [MIB-DOCTORS] Why is this MIB module read-write?
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: Wed, 05 Feb 2014 15:40:16 -0000

I fully agree with Juergen here:

Bert

On 05/02/14 15:33, Juergen Schoenwaelder wrote:
> I would rather write a positive statement instead of a negative one.
> Something like this:
>
>    The OPS area recommends the use of NETCONF/YANG standards for
>    configuration. IETF working groups are therefore encouraged to use
>    the NETCONF/YANG standards for configuration, specifically in new
>    charters. SNMP MIB modules modifying persistent configuration state
>    should only be produced by working groups in cases of clear utility
>    and overwhelming consensus to use SNMP write operations for
>    configuration.
>
> Note that this statement limits the discussion to configuration data.
> Note also that there is no standard way to modify operational state
> via NETCONF at this point in time (so it would be strange to discourage
> SNMP if there is no standardized alternative).
>
> /js

From tnadeau@lucidvision.com  Wed Feb  5 10:40:15 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 B7A4E1A0174 for <mib-doctors@ietfa.amsl.com>; Wed,  5 Feb 2014 10:40:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.435
X-Spam-Level: 
X-Spam-Status: No, score=-2.435 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.535] 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 cC_anerFTy9u for <mib-doctors@ietfa.amsl.com>; Wed,  5 Feb 2014 10:40:12 -0800 (PST)
Received: from lucidvision.com (lucidvision.com [72.71.250.34]) by ietfa.amsl.com (Postfix) with ESMTP id 21E7E1A0138 for <mib-doctors@ietf.org>; Wed,  5 Feb 2014 10:40:12 -0800 (PST)
Received: from [10.36.0.205] (sccc-66-78-236-243.smartcity.com [66.78.236.243]) by lucidvision.com (Postfix) with ESMTP id 0E77B26DE4A6; Wed,  5 Feb 2014 13:40:09 -0500 (EST)
Content-Type: multipart/signed; boundary="Apple-Mail=_6B5E54DC-030F-4A4E-9AFA-E421804B05F0"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Thomas Nadeau <tnadeau@lucidvision.com>
In-Reply-To: <20140205150546.GA46787@elstar.local>
Date: Wed, 5 Feb 2014 10:40:07 -0800
Message-Id: <9E272EB0-909B-4D82-8379-DBD3F8F40C5C@lucidvision.com>
References: <9904FB1B0159DA42B0B887B7FA8119CA243D3C0F@AZ-FFEXMB04.global.avaya.com> <556BB556-669F-4EF5-B8B0-4F1CD7E45BD0@lucidvision.com> <52DE928D.1090909@bwijnen.net> <0b2301cf16ce$bad3a3e0$307aeba0$@olddog.co.uk> <52DF9D02.6070306@cisco.com> <52EE4EF1.3000102@cisco.com> <20140202144457.GA35917@elstar.local> <52F246FB.8010403@cisco.com> <20140205143320.GC46555@elstar.local> <539FBA03-155E-41B3-8618-C2B46887553E@lucidvision.com> <20140205150546.GA46787@elstar.local>
To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
X-Mailer: Apple Mail (2.1827)
Cc: Farrel Adrian <adrian@olddog.co.uk>, "MIB Doctors \(E-mail\)" <mib-doctors@ietf.org>
Subject: Re: [MIB-DOCTORS] Why is this MIB module read-write?
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: Wed, 05 Feb 2014 18:40:15 -0000

--Apple-Mail=_6B5E54DC-030F-4A4E-9AFA-E421804B05F0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=us-ascii


	Yes, lets keep it positive for sure. 8)

	--Tom


> On Wed, Feb 05, 2014 at 06:48:40AM -0800, Thomas D. Nadeau wrote:
> 
>> we could be picky and discuss running versus persistent
>> configuration but that's missing the issue: most providers disable
>> snmp write regardless of ultimate configuration state.
> 
> Having worked on replacement technology for SNMP for a couple of years
> now, I think I do understand the issues and concerns. But then I also
> know that there are networks that are not 'provider' networks. I still
> believe in positive encouragement to use alternatives (where they
> exist) and informed decisions by WGs.
> 
> /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/>
> 


--Apple-Mail=_6B5E54DC-030F-4A4E-9AFA-E421804B05F0
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

iQIcBAEBCgAGBQJS8oWHAAoJEPcO+I7eiUJZahEQAKhxK/aqV7+ZGeIPzENnhMNJ
3irbfN0OfllidTyuWpSGi9xR84tmPNz/ppGcJzS8mKopzH2WxzqVYnAmVGwJ/9Hq
Dk+qu5XYJpmY9RF3j3vecn3+Q/DqdImqLgOsHg2EmRBMGApo3XbyohMuqUyvpzPv
1WVGa9eVTDse40SOOKIDfU0nFFS5atvhqmpclC52+AjoA900RJ+6+/rqVVIOMylz
u9cupf/hjbphmJzlksrVv9qGXK7u1A/8a5KTJ5d7pPSWWxIBDMb1wcvZhA9/jQkY
g/IxkiPWmPe/pSHNemhJwwnkcF0ThAVFh5HMiYOB2QMpdqw0Aii/hmxXzRuJ2Xis
3/J8VqXjDywo1FdfR3E+4Xfe8c/nOtq7j2RtR/lRzrKLzU2BMW+8i1r7S0sAvWXE
Lg8rKb5Z7jDXwd+daPBpNJw2CGM+2IP4sPLbm2EIh1mPX9ZvAiPJEBJeO9xyiVtd
bsexVVbXvyIS6zbdAoUVBL/pn5KLW/XH4uJWLgfbN7Zf0iAJ5DpNAD0bDQ8ROHf6
634VESkTPq9hLneJ0JbIYYynwZfUqrT9EJTnS8n1HZH0N5Ew1e/xYqVbUTCEGYN2
FAx0QBoih0iPPvlElxCi5pU7WEQAgC8eHKn6u4Sztb2paPoaV1fFHmZuaMwzjJtA
PtMnYwARMCg82XfP6xaD
=/Q8U
-----END PGP SIGNATURE-----

--Apple-Mail=_6B5E54DC-030F-4A4E-9AFA-E421804B05F0--

From dromasca@avaya.com  Thu Feb  6 02:17:18 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 731631A0393 for <mib-doctors@ietfa.amsl.com>; Thu,  6 Feb 2014 02:17:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.135
X-Spam-Level: 
X-Spam-Status: No, score=-3.135 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.535] 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-GiDsNpp4Es for <mib-doctors@ietfa.amsl.com>; Thu,  6 Feb 2014 02:17:15 -0800 (PST)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by ietfa.amsl.com (Postfix) with ESMTP id 75DF01A0385 for <mib-doctors@ietf.org>; Thu,  6 Feb 2014 02:17:15 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjsWAOtf81LGmAcV/2dsb2JhbABWA4JrIThXqF6OcIcfgQcWdIIlAQEBAQMSZwwCAgIBBgINAQIBBAEBAQodBxsXFAkIAgQBDQUIGodjAZEtkTqrZBcEjkUhEAcGC4MTgRQEnxuLMYMtgio
X-IronPort-AV: E=Sophos;i="4.95,793,1384318800"; d="scan'208";a="48248231"
Received: from unknown (HELO co300216-co-erhwest-exch.avaya.com) ([198.152.7.21]) by co300216-co-outbound.net.avaya.com with ESMTP; 06 Feb 2014 05:17:13 -0500
Received: from unknown (HELO AZ-FFEXHC01.global.avaya.com) ([135.64.58.11]) by co300216-co-erhwest-out.avaya.com with ESMTP/TLS/AES128-SHA; 06 Feb 2014 05:06:14 -0500
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC01.global.avaya.com ([135.64.58.11]) with mapi id 14.03.0174.001; Thu, 6 Feb 2014 11:17:11 +0100
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: Thomas Nadeau <tnadeau@lucidvision.com>, Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
Thread-Topic: [MIB-DOCTORS] Why is this MIB module read-write?
Thread-Index: AQHPInxseCo5UMVfdE6YL3camyx6tZqmqLIAgAAESACAAGldAIAAO+OAgACx6HA=
Date: Thu, 6 Feb 2014 10:17:10 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA2E3EF04F@AZ-FFEXMB04.global.avaya.com>
References: <9904FB1B0159DA42B0B887B7FA8119CA243D3C0F@AZ-FFEXMB04.global.avaya.com> <556BB556-669F-4EF5-B8B0-4F1CD7E45BD0@lucidvision.com> <52DE928D.1090909@bwijnen.net> <0b2301cf16ce$bad3a3e0$307aeba0$@olddog.co.uk> <52DF9D02.6070306@cisco.com> <52EE4EF1.3000102@cisco.com> <20140202144457.GA35917@elstar.local> <52F246FB.8010403@cisco.com> <20140205143320.GC46555@elstar.local> <539FBA03-155E-41B3-8618-C2B46887553E@lucidvision.com> <20140205150546.GA46787@elstar.local> <9E272EB0-909B-4D82-8379-DBD3F8F40C5C@lucidvision.com>
In-Reply-To: <9E272EB0-909B-4D82-8379-DBD3F8F40C5C@lucidvision.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.64.58.46]
Content-Type: text/plain; charset="windows-1255"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Farrel Adrian <adrian@olddog.co.uk>, "MIB Doctors \(E-mail\)" <mib-doctors@ietf.org>
Subject: Re: [MIB-DOCTORS] Why is this MIB module read-write?
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, 06 Feb 2014 10:17:18 -0000

Yes, positive is good!

Regards,

Dan


> -----Original Message-----
> From: Thomas Nadeau [mailto:tnadeau@lucidvision.com]
> Sent: =E9=E5=ED=A0=E3 05 =F4=E1=F8=E5=E0=F8 2014 20:40
> To: Juergen Schoenwaelder
> Cc: Benoit Claise; Farrel Adrian; Bert Wijnen (IETF); Romascanu, Dan (Dan=
);
> MIB Doctors (E-mail)
> Subject: Re: [MIB-DOCTORS] Why is this MIB module read-write?
>=20
>=20
> 	Yes, lets keep it positive for sure. 8)
>=20
> 	--Tom
>=20
>=20
> > On Wed, Feb 05, 2014 at 06:48:40AM -0800, Thomas D. Nadeau wrote:
> >
> >> we could be picky and discuss running versus persistent configuration
> >> but that's missing the issue: most providers disable snmp write
> >> regardless of ultimate configuration state.
> >
> > Having worked on replacement technology for SNMP for a couple of years
> > now, I think I do understand the issues and concerns. But then I also
> > know that there are networks that are not 'provider' networks. I still
> > believe in positive encouragement to use alternatives (where they
> > exist) and informed decisions by WGs.
> >
> > /js
> >
> > --
> > Juergen Schoenwaelder           Jacobs University Bremen gGmbH
> > Phone: +49 421 200 3587         Campus Ring 1, 28759 Bremen, Germany
> > Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>
> >


From ietfdbh@comcast.net  Sat Feb  8 20:28:17 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 E9F391A0015 for <mib-doctors@ietfa.amsl.com>; Sat,  8 Feb 2014 20:28:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.648
X-Spam-Level: 
X-Spam-Status: No, score=-0.648 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.548, 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 tYBuU5cIHMlY for <mib-doctors@ietfa.amsl.com>; Sat,  8 Feb 2014 20:28:14 -0800 (PST)
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 E7F471A0680 for <mib-doctors@ietf.org>; Sat,  8 Feb 2014 20:28:13 -0800 (PST)
Received: from omta01.westchester.pa.mail.comcast.net ([76.96.62.11]) by qmta15.westchester.pa.mail.comcast.net with comcast id Q4T21n0040EZKEL5F4UDRL; Sun, 09 Feb 2014 04:28:13 +0000
Received: from [192.168.1.75] ([162.228.1.76]) by omta01.westchester.pa.mail.comcast.net with comcast id Q4U21n00K1ePg823M4U4Kd; Sun, 09 Feb 2014 04:28:11 +0000
Content-Type: multipart/alternative; boundary="Apple-Mail=_FFB692C0-D2C1-4EC5-954E-9876961CA43F"
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: David Harrington <ietfdbh@comcast.net>
In-Reply-To: <05c501cf21ad$80d97ef0$828c7cd0$@olddog.co.uk>
Date: Sat, 8 Feb 2014 23:28:02 -0500
Message-Id: <7D263081-6D84-4AA2-B0CB-FA74793BD135@comcast.net>
References: <05c501cf21ad$80d97ef0$828c7cd0$@olddog.co.uk>
To: adrian@olddog.co.uk
X-Mailer: Apple Mail (2.1510)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1391920093; bh=LE1VSmpiCvAsIBN75rwbNtAmOI6LGrjncqGYvCnsAlI=; h=Received:Received:Content-Type:Mime-Version:Subject:From:Date: Message-Id:To; b=VjWP9LJGNezDgWt4dxUvqmV3AN8edvsL0ecQKyAPocDtrkuCCmKT7gg1w3IEVaTJO o27szXh2WhS3qfjRVwcYZ6C2S30ngwq5DnSLfj3ZrWAW7v9JbmS3MFPJQ6D4ejOiKa PwH7Ho8QjBKXf5vxEzkjRRjRoTWuPr8VaS3cI9xkEBywqw1Wi3KdUHklWnClnuYS6j uu2sVLLYacvUili7M1vAP3YSyJ5LWEC+qt4qSiJQ7ehjknhQGufkWj6KDFhcvY3otn ctdSTk1gl7KSAiMaDwRTx00MJ8HHybG40Oip3mIutBvsrvpWJ7+7FqR3kQkq+euCRC kwsw4w6NMKb5w==
Cc: mib-doctors@ietf.org
Subject: Re: [MIB-DOCTORS] Read-only MIB modules
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: Sun, 09 Feb 2014 04:28:18 -0000

--Apple-Mail=_FFB692C0-D2C1-4EC5-954E-9876961CA43F
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi,

I object to this statement. (Should I say "strongly" object, to show I =
mean business?

There are many RW objects that can "adjust" a network configuration =
assuming SET is supported by the agent involved.
The NMS I used to work on, which helped determine and correct root cause =
for fault and performance problems, adjusted networks using writable MIB =
modules often.
To tell WGs they should not develop RW MIB modules I think is wrong.

I also have a concern with recommending Netconf/YANG at this point in =
time.
If we looked up the top ten router vendors using something like Gartner =
reports, how many of them really support configuration using Netconf =
with YANG in shipping products?
Ditto, the top ten switch vendors?
How many of them can be fully configured using YANG modules (not =
homegrown alternatives, but modules - standard or proprietary - written =
using the standards-compliant YANG language)?
I don't know the answer to that question, but would like to see some =
proof that YANG is at least as widely supported in currently shipping =
products as RW MIB objects.
I think Netconf/YANG should compete in an open market with RW MIB =
modules, not try to stack the deck in their favor by "strongly =
discouraging" RW MIB standards.

I have had discussions with vendors who are leaders in their particular =
networking niche, and they have told me they would not consider =
Netconf/YANG, because it has not been around long enough and been =
widely-enough deployed to prove stable for their production networks =
(whereas SNMP has enough track record to be known to be stable).
So I'm a bit concerned about telling WGs they should develop YANG =
modules rather than MIB modules.
And the current discussions of whether YANG 1.1 or 2.0 is needed to fix =
some problems with YANG 1.0, and it may not be backwards compatible, =
make me question the stability of YANG.

Don't get me wrong. I support Netconf/YANG going forward, but I think it =
is important to provide advice that non-MIB-Doctors/non-YANG-experts can =
interpret reasonably.
Any such statement should make a clear distinction between =
"configuration" - the complete configuration of a device by Netconf - =
versus RW objects in a MIB - which can be used by SNMP to adjust network =
parameters/configuration.
Telling people not to develop RW MIBs is throwing the baby out with the =
bathwater.
We should NOT recommend against RW MIBs, because these can be used for =
more than (full device) configuration.
That point is far from clear in the currently proposed statement.
Maybe the statement should be that, if a vendor wants to replace their =
CLI, they should replace it with Netconf/YANG, and not with =
SNMP/RW-MIBs.=20
That's probably a closer approximation  of Netconf/YANG's applicability =
versus RW MIBs.=20

In the past we have allowed implementations to make the conformance =
choice between supporting a MIB as RW, or implementing read-only.
If we advise WGs to not develop module with RW objects, then we take the =
choice away from the vendors.
I thick that would be a mistake.

In  addition, it is pointed out later in this thread that other SDOs use =
RW MIBs.=20
Well, those MIBs produced by other SDOs (and for that matter, vendors) =
might require some support for specific RW objects in IETF MIB modules.
Therefore, I think it would be providing bad advice to say that IETF WGs =
should not produce MIB  modules with RW objects in them.

If Netconf/YANG becomes widely deployed, then NMS implementations and =
operators can choose whether to use YANG or SNMP (or their CLI) to =
adjust network configurations.
THat should not be a decision we make in the IETF, effectively forcing =
WGs to not develop MIBs with writable objects.

Providing RW objects in MIB modules lets implementers and operators make =
the appropriate choice for their environments. (See RFC 3365 for similar =
thinking vis-a-vis security.)

dbh

On Feb 4, 2014, at 8:32 AM, Adrian Farrel <adrian@olddog.co.uk> wrote:

> Hi,
> =20
> The MPLS working group is testing the water to see whether one of its =
MIB modules should be "reduced" to read-only. This is the document that =
triggered my recent questions that led on to the draft advice you are =
working on. The WG took the document back to make this decision.
> =20
> You'll note below that we immediately have an implementation claim =
(not for this doc, but for the modules it extends).
> =20
> An interesting situation, I think.
> =20
> A
> =20
> From: mpls [mailto:mpls-bounces@ietf.org] On Behalf Of GyeRok Gwun =
(???)
> Sent: 04 February 2014 09:57
> To: 'mpls@ietf.org'
> Cc: 'mpls-chairs@tools.ietf.org'; =
'draft-ietf-mpls-tp-te-mib@tools.ietf.org'
> Subject: Re: [mpls] seeking consensus on making =
draft-ietf-mpls-tp-te-mib read- only
> =20
> No/oppose to make as Read-only mib.
> In our products we extensively use R/W object of TE mib. We also have =
NMS/EMS that use TE read-write Objects
> =20
> Best Regards
> Gwun
> =20
> -----Original Message-----
> From: mpls [mailto:mpls-bounces@ietf.org] On Behalf Of Loa Andersson
> Sent: Monday, February 03, 2014 10:55 PM
> To: mpls@ietf.org
> Cc: mpls-chairs@tools.ietf.org; =
draft-ietf-mpls-tp-te-mib@tools.ietf.org
> Subject: [mpls] seeking consensus on making draft-ietf-mpls-tp-te-mib =
read- only
> =20
> Working Group,
> =20
> We have just recalled draft-ietf-mpls-tp-te-mib from the IESG to the =
working group for more work. We have a series of comments that are =
mostly for clarification. However the main reason for recalling the =
document is that there is one point where we need to confirm working =
group consensus.
> =20
> The IETF, the working group and the MIB Doctors are today very =
reluctant to produce read-write MIB modules. The current draft is =
read-write for a few objects, this is based on a consensus call for an =
earlier discussion, however the consensus call was not clear. It can be =
taken to mean both that we want to go with read-write objects and that =
we want to see read-only. Is it clear that it has been interpreted =
differently by different individuals.
> =20
> The authors and chairs have discussed the issue and we have a rough =
consensus that we want the MIB module(s) to be read-only.
> =20
> We therefore are asking the working group if this is OK for the MIB
> module(s) in the current document. Please indicate Support or Oppose =
for this MIB (draft-ietf-mpls-tp-te-mib) to be read-only.
> =20
> Please send your comments to the working group mailing list before =
February 18, 2014.
> =20
> Loa
> for the MPLS wg chairs
> --
> =20
> =20
> Loa Andersson                        email: loa@mail01.huawei.com
> Senior MPLS Expert                          loa@pi.nu
> Huawei Technologies (consultant)     phone: +46 739 81 21 64
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
> =20
> _______________________________________________
> MIB-DOCTORS mailing list
> MIB-DOCTORS@ietf.org
> https://www.ietf.org/mailman/listinfo/mib-doctors


--Apple-Mail=_FFB692C0-D2C1-4EC5-954E-9876961CA43F
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"><base href=3D"x-msg://3655/"></head><body =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; ">Hi,<div><br></div><div>I object =
to this statement. (Should I say "strongly" object, to show I mean =
business?</div><div><br></div><div>There are many RW objects that can =
"adjust" a network configuration assuming SET is supported by the agent =
involved.</div><div>The NMS I used to work on, which helped determine =
and correct root cause for fault and performance problems, adjusted =
networks using writable MIB modules often.</div><div>To tell WGs they =
should not develop RW MIB modules I think is =
wrong.</div><div><br></div><div>I also have a concern with recommending =
Netconf/YANG at this point in time.</div><div>If we looked up the top =
ten router vendors using something like Gartner reports, how many of =
them really support configuration using Netconf with YANG in shipping =
products?</div><div>Ditto, the top ten switch vendors?</div><div>How =
many of them can be fully configured using YANG modules (not homegrown =
alternatives, but modules - standard or proprietary - written using the =
standards-compliant YANG language)?</div><div>I don't know the answer to =
that question, but would like to see some proof that YANG is at least as =
widely supported in currently shipping products as RW MIB =
objects.</div><div>I think Netconf/YANG should compete in an open market =
with RW MIB modules, not try to stack the deck in their favor by =
"strongly discouraging" RW MIB standards.</div><div><br></div><div>I =
have had discussions with vendors who are leaders in their particular =
networking niche, and they have told me they would not consider =
Netconf/YANG, because it has not been around long enough and been =
widely-enough deployed to prove stable for their production networks =
(whereas SNMP has enough track record to be known to be =
stable).</div><div>So I'm a bit concerned about telling WGs they should =
develop YANG modules rather than MIB modules.</div><div>And the current =
discussions of whether YANG 1.1 or 2.0 is needed to fix some problems =
with YANG 1.0, and it may not be backwards compatible, make me question =
the stability of YANG.</div><div><br></div><div>Don't get me wrong. I =
support Netconf/YANG going forward, but I think it is important to =
provide advice that non-MIB-Doctors/non-YANG-experts can interpret =
reasonably.</div><div>Any such statement should make a clear distinction =
between "configuration" - the complete configuration of a device by =
Netconf - versus RW objects in a MIB - which can be used by SNMP to =
adjust network parameters/configuration.</div><div>Telling people not to =
develop RW MIBs is throwing the baby out with the =
bathwater.</div><div>We should NOT recommend against RW MIBs, because =
these can be used for more than (full device) =
configuration.</div><div>That point is far from clear in the currently =
proposed statement.</div><div>Maybe the statement should be that, if a =
vendor wants to replace their CLI, they should replace it with =
Netconf/YANG, and not with SNMP/RW-MIBs.&nbsp;</div><div>That's probably =
a closer approximation &nbsp;of Netconf/YANG's applicability versus RW =
MIBs.&nbsp;</div><div><br></div><div>In the past we have allowed =
implementations to make the conformance choice between supporting a MIB =
as RW, or implementing read-only.</div><div>If we advise WGs to not =
develop module with RW objects, then we take the choice away from the =
vendors.</div><div>I thick that would be a =
mistake.</div><div><br></div><div>In &nbsp;addition, it is pointed out =
later in this thread that other SDOs use RW MIBs.&nbsp;</div><div>Well, =
those MIBs produced by other SDOs (and for that matter, vendors) might =
require some support for specific RW objects in IETF MIB =
modules.</div><div>Therefore, I think it would be providing bad advice =
to say that IETF WGs should not produce MIB &nbsp;modules with RW =
objects in them.</div><div><br></div><div>If Netconf/YANG becomes widely =
deployed, then NMS implementations and operators can choose whether to =
use YANG or SNMP (or their CLI) to adjust network =
configurations.</div><div>THat should not be a decision we make in the =
IETF, effectively forcing WGs to not develop MIBs with writable =
objects.</div><div><br></div><div>Providing RW objects in MIB modules =
lets implementers and operators make the appropriate choice for their =
environments. (See RFC 3365 for similar thinking vis-a-vis =
security.)</div><div><br></div><div>dbh</div><div><br><div><div>On Feb =
4, 2014, at 8:32 AM, Adrian Farrel &lt;<a =
href=3D"mailto:adrian@olddog.co.uk">adrian@olddog.co.uk</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div lang=3D"EN-GB" link=3D"#0563C1" vlink=3D"#954F72" =
style=3D"font-family: Helvetica; font-size: medium; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: =
0px; text-transform: none; white-space: normal; widows: 2; word-spacing: =
0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; =
"><div class=3D"WordSection1" style=3D"page: WordSection1; "><div =
style=3D"margin: 0cm 0cm 0.0001pt; text-align: justify; word-break: =
normal; font-size: 10pt; font-family: 'Malgun Gothic', sans-serif; =
"><span style=3D"font-size: 11pt; font-family: Calibri, sans-serif; =
color: rgb(31, 73, 125); ">Hi,<o:p></o:p></span></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; text-align: justify; word-break: =
normal; font-size: 10pt; font-family: 'Malgun Gothic', sans-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; text-align: justify; word-break: normal; font-size: 10pt; =
font-family: 'Malgun Gothic', sans-serif; "><span style=3D"font-size: =
11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); ">The =
MPLS working group is testing the water to see whether one of its MIB =
modules should be "reduced" to read-only. This is the document that =
triggered my recent questions that led on to the draft advice you are =
working on. The WG took the document back to make this =
decision.<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
text-align: justify; word-break: normal; font-size: 10pt; font-family: =
'Malgun Gothic', sans-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; text-align: =
justify; word-break: normal; font-size: 10pt; font-family: 'Malgun =
Gothic', sans-serif; "><span style=3D"font-size: 11pt; font-family: =
Calibri, sans-serif; color: rgb(31, 73, 125); ">You'll note below that =
we immediately have an implementation claim (not for this doc, but for =
the modules it extends).<o:p></o:p></span></div><div style=3D"margin: =
0cm 0cm 0.0001pt; text-align: justify; word-break: normal; font-size: =
10pt; font-family: 'Malgun Gothic', sans-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; text-align: justify; word-break: normal; font-size: 10pt; =
font-family: 'Malgun Gothic', sans-serif; "><span style=3D"font-size: =
11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); ">An =
interesting situation, I think.<o:p></o:p></span></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; text-align: justify; word-break: =
normal; font-size: 10pt; font-family: 'Malgun Gothic', sans-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; text-align: justify; word-break: normal; font-size: 10pt; =
font-family: 'Malgun Gothic', sans-serif; "><span style=3D"font-size: =
11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); =
">A<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
text-align: justify; word-break: normal; font-size: 10pt; font-family: =
'Malgun Gothic', sans-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-width: 1.5pt; border-left-color: blue; padding: 0cm 0cm 0cm =
4pt; "><div><div style=3D"border-style: solid none none; =
border-top-width: 1pt; border-top-color: rgb(181, 196, 223); padding: =
3pt 0cm 0cm; "><div style=3D"margin: 0cm 0cm 0.0001pt; text-align: left; =
word-break: normal; font-size: 10pt; font-family: 'Malgun Gothic', =
sans-serif; "><b><span lang=3D"EN-US" style=3D"font-family: Tahoma, =
sans-serif; ">From:</span></b><span lang=3D"EN-US" style=3D"font-family: =
Tahoma, sans-serif; "><span =
class=3D"Apple-converted-space">&nbsp;</span>mpls [mailto:mpls-<a =
href=3D"mailto:bounces@ietf.org" style=3D"color: rgb(149, 79, 114); =
text-decoration: underline; ">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>GyeRok Gwun =
(???)<br><b>Sent:</b><span class=3D"Apple-converted-space">&nbsp;</span>04=
 February 2014 09:57<br><b>To:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>'<a =
href=3D"mailto:mpls@ietf.org" style=3D"color: rgb(149, 79, 114); =
text-decoration: underline; ">mpls@ietf.org</a>'<br><b>Cc:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>'<a =
href=3D"mailto:mpls-chairs@tools.ietf.org" style=3D"color: rgb(149, 79, =
114); text-decoration: underline; ">mpls-chairs@tools.ietf.org</a>'; '<a =
href=3D"mailto:draft-ietf-mpls-tp-te-mib@tools.ietf.org" style=3D"color: =
rgb(149, 79, 114); text-decoration: underline; =
">draft-ietf-mpls-tp-te-mib@tools.ietf.org</a>'<br><b>Subject:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>Re: [mpls] seeking =
consensus on making draft-ietf-mpls-tp-te-mib read- =
only<o:p></o:p></span></div></div></div><div style=3D"margin: 0cm 0cm =
0.0001pt; text-align: left; word-break: break-all; font-size: 10pt; =
font-family: 'Malgun Gothic', sans-serif; "><o:p>&nbsp;</o:p></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; word-break: break-all; font-size: =
10pt; font-family: 'Courier New', serif; "><span lang=3D"EN-US">No/oppose =
to make as Read-only mib.<o:p></o:p></span></div><div style=3D"margin: =
0cm 0cm 0.0001pt; word-break: break-all; font-size: 10pt; font-family: =
'Courier New', serif; "><span lang=3D"EN-US">In our products we =
extensively use R/W object of TE mib. We also have NMS/EMS that use TE =
read-write Objects<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; word-break: break-all; font-size: 10pt; font-family: 'Courier =
New', serif; "><span lang=3D"EN-US">&nbsp;</span></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; word-break: break-all; font-size: =
10pt; font-family: 'Courier New', serif; "><span lang=3D"EN-US">Best =
Regards<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
word-break: break-all; font-size: 10pt; font-family: 'Courier New', =
serif; "><span lang=3D"EN-US">Gwun<o:p></o:p></span></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; word-break: break-all; font-size: =
10pt; font-family: 'Courier New', serif; "><span =
lang=3D"EN-US">&nbsp;</span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; word-break: break-all; font-size: 10pt; font-family: 'Courier =
New', serif; "><span lang=3D"EN-US">-----Original =
Message-----<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; word-break: break-all; font-size: 10pt; font-family: 'Courier =
New', serif; "><span lang=3D"EN-US">From: mpls [<a =
href=3D"mailto:mpls-bounces@ietf.org" style=3D"color: rgb(149, 79, 114); =
text-decoration: underline; ">mailto:mpls-bounces@ietf.org</a>] On =
Behalf Of Loa Andersson<o:p></o:p></span></div><div style=3D"margin: 0cm =
0cm 0.0001pt; word-break: break-all; font-size: 10pt; font-family: =
'Courier New', serif; "><span lang=3D"EN-US">Sent: Monday, February 03, =
2014 10:55 PM<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; word-break: break-all; font-size: 10pt; font-family: 'Courier =
New', serif; "><span lang=3D"EN-US">To:<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:mpls@ietf.org" style=3D"color: rgb(149, 79, 114); =
text-decoration: underline; =
">mpls@ietf.org</a><o:p></o:p></span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; word-break: break-all; font-size: 10pt; font-family: 'Courier =
New', serif; "><span lang=3D"EN-US">Cc:<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:mpls-chairs@tools.ietf.org" style=3D"color: rgb(149, 79, =
114); text-decoration: underline; ">mpls-chairs@tools.ietf.org</a>;<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:draft-ietf-mpls-tp-te-mib@tools.ietf.org" style=3D"color: =
rgb(149, 79, 114); text-decoration: underline; =
">draft-ietf-mpls-tp-te-mib@tools.ietf.org</a><o:p></o:p></span></div><div=
 style=3D"margin: 0cm 0cm 0.0001pt; word-break: break-all; font-size: =
10pt; font-family: 'Courier New', serif; "><span lang=3D"EN-US">Subject: =
[mpls] seeking consensus on making draft-ietf-mpls-tp-te-mib read- =
only<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
word-break: break-all; font-size: 10pt; font-family: 'Courier New', =
serif; "><span lang=3D"EN-US">&nbsp;</span></div><div style=3D"margin: =
0cm 0cm 0.0001pt; word-break: break-all; font-size: 10pt; font-family: =
'Courier New', serif; "><span lang=3D"EN-US">Working =
Group,<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
word-break: break-all; font-size: 10pt; font-family: 'Courier New', =
serif; "><span lang=3D"EN-US">&nbsp;</span></div><div style=3D"margin: =
0cm 0cm 0.0001pt; word-break: break-all; font-size: 10pt; font-family: =
'Courier New', serif; "><span lang=3D"EN-US">We have just recalled =
draft-ietf-mpls-tp-te-mib from the IESG to the working group for more =
work. We have a series of comments that are mostly for clarification. =
However the main reason for recalling the document is that there is one =
point where we need to confirm working group =
consensus.<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; word-break: break-all; font-size: 10pt; font-family: 'Courier =
New', serif; "><span lang=3D"EN-US">&nbsp;</span></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; word-break: break-all; font-size: =
10pt; font-family: 'Courier New', serif; "><span lang=3D"EN-US">The =
IETF, the working group and the MIB Doctors are today very reluctant to =
produce read-write MIB modules. The current draft is read-write for a =
few objects, this is based on a consensus call for an earlier =
discussion, however the consensus call was not clear. It can be taken to =
mean both that we want to go with read-write objects and that we want to =
see read-only. Is it clear that it has been interpreted differently by =
different individuals.<o:p></o:p></span></div><div style=3D"margin: 0cm =
0cm 0.0001pt; word-break: break-all; font-size: 10pt; font-family: =
'Courier New', serif; "><span lang=3D"EN-US">&nbsp;</span></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; word-break: break-all; font-size: =
10pt; font-family: 'Courier New', serif; "><span lang=3D"EN-US">The =
authors and chairs have discussed the issue and we have a rough =
consensus that we want the MIB module(s) to be =
read-only.<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; word-break: break-all; font-size: 10pt; font-family: 'Courier =
New', serif; "><span lang=3D"EN-US">&nbsp;</span></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; word-break: break-all; font-size: =
10pt; font-family: 'Courier New', serif; "><span lang=3D"EN-US">We =
therefore are asking the working group if this is OK for the =
MIB<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
word-break: break-all; font-size: 10pt; font-family: 'Courier New', =
serif; "><span lang=3D"EN-US">module(s) in the current document. Please =
indicate Support or Oppose for this MIB (draft-ietf-mpls-tp-te-mib) to =
be read-only.<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; word-break: break-all; font-size: 10pt; font-family: 'Courier =
New', serif; "><span lang=3D"EN-US">&nbsp;</span></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; word-break: break-all; font-size: =
10pt; font-family: 'Courier New', serif; "><span lang=3D"EN-US">Please =
send your comments to the working group mailing list before February 18, =
2014.<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
word-break: break-all; font-size: 10pt; font-family: 'Courier New', =
serif; "><span lang=3D"EN-US">&nbsp;</span></div><div style=3D"margin: =
0cm 0cm 0.0001pt; word-break: break-all; font-size: 10pt; font-family: =
'Courier New', serif; "><span =
lang=3D"EN-US">Loa<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; word-break: break-all; font-size: 10pt; font-family: 'Courier =
New', serif; "><span lang=3D"EN-US">for the MPLS wg =
chairs<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
word-break: break-all; font-size: 10pt; font-family: 'Courier New', =
serif; "><span lang=3D"EN-US">--<o:p></o:p></span></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; word-break: break-all; font-size: =
10pt; font-family: 'Courier New', serif; "><span =
lang=3D"EN-US">&nbsp;</span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; word-break: break-all; font-size: 10pt; font-family: 'Courier =
New', serif; "><span lang=3D"EN-US">&nbsp;</span></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; word-break: break-all; font-size: =
10pt; font-family: 'Courier New', serif; "><span lang=3D"EN-US">Loa =
Andersson&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
email:<span class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:loa@mail01.huawei.com" style=3D"color: rgb(149, 79, 114); =
text-decoration: underline; =
">loa@mail01.huawei.com</a><o:p></o:p></span></div><div style=3D"margin: =
0cm 0cm 0.0001pt; word-break: break-all; font-size: 10pt; font-family: =
'Courier New', serif; "><span lang=3D"EN-US">Senior MPLS =
Expert&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;<span class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:loa@pi.nu" style=3D"color: rgb(149, 79, 114); =
text-decoration: underline; ">loa@pi.nu</a><o:p></o:p></span></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; word-break: break-all; font-size: =
10pt; font-family: 'Courier New', serif; "><span lang=3D"EN-US">Huawei =
Technologies (consultant)&nbsp;&nbsp;&nbsp;&nbsp; phone: +46 739 81 21 =
64<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
word-break: break-all; font-size: 10pt; font-family: 'Courier New', =
serif; "><span =
lang=3D"EN-US">_______________________________________________<o:p></o:p><=
/span></div><div style=3D"margin: 0cm 0cm 0.0001pt; word-break: =
break-all; font-size: 10pt; font-family: 'Courier New', serif; "><span =
lang=3D"EN-US">mpls mailing list<o:p></o:p></span></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; word-break: break-all; font-size: =
10pt; font-family: 'Courier New', serif; "><span lang=3D"EN-US"><a =
href=3D"mailto:mpls@ietf.org" style=3D"color: rgb(149, 79, 114); =
text-decoration: underline; =
">mpls@ietf.org</a><o:p></o:p></span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; word-break: break-all; font-size: 10pt; font-family: 'Courier =
New', serif; "><span lang=3D"EN-US"><a =
href=3D"https://www.ietf.org/mailman/listinfo/mpls" style=3D"color: =
rgb(149, 79, 114); text-decoration: underline; =
">https://www.ietf.org/mailman/listinfo/mpls</a><o:p></o:p></span></div><d=
iv style=3D"margin: 0cm 0cm 0.0001pt; word-break: break-all; font-size: =
10pt; font-family: 'Courier New', serif; "><span =
lang=3D"EN-US">_______________________________________________<o:p></o:p><=
/span></div><div style=3D"margin: 0cm 0cm 0.0001pt; word-break: =
break-all; font-size: 10pt; font-family: 'Courier New', serif; "><span =
lang=3D"EN-US">mpls mailing list<o:p></o:p></span></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; word-break: break-all; font-size: =
10pt; font-family: 'Courier New', serif; "><span lang=3D"EN-US"><a =
href=3D"mailto:mpls@ietf.org" style=3D"color: rgb(149, 79, 114); =
text-decoration: underline; =
">mpls@ietf.org</a><o:p></o:p></span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; word-break: break-all; font-size: 10pt; font-family: 'Courier =
New', serif; "><span lang=3D"EN-US"><a =
href=3D"https://www.ietf.org/mailman/listinfo/mpls" style=3D"color: =
rgb(149, 79, 114); text-decoration: underline; =
">https://www.ietf.org/mailman/listinfo/mpls</a><o:p></o:p></span></div><d=
iv style=3D"margin: 0cm 0cm 0.0001pt; text-align: justify; word-break: =
break-all; font-size: 10pt; font-family: 'Malgun Gothic', sans-serif; =
"><span =
lang=3D"EN-US">&nbsp;</span></div></div></div>____________________________=
___________________<br>MIB-DOCTORS mailing list<br><a =
href=3D"mailto:MIB-DOCTORS@ietf.org" style=3D"color: rgb(149, 79, 114); =
text-decoration: underline; ">MIB-DOCTORS@ietf.org</a><br><a =
href=3D"https://www.ietf.org/mailman/listinfo/mib-doctors" style=3D"color:=
 rgb(149, 79, 114); text-decoration: underline; =
">https://www.ietf.org/mailman/listinfo/mib-doctors</a><br></div></blockqu=
ote></div><br></div></body></html>=

--Apple-Mail=_FFB692C0-D2C1-4EC5-954E-9876961CA43F--

From andy@yumaworks.com  Sat Feb  8 22:25:14 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 A89821A05A9 for <mib-doctors@ietfa.amsl.com>; Sat,  8 Feb 2014 22:25:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Level: 
X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 F33qoBgY1Ohq for <mib-doctors@ietfa.amsl.com>; Sat,  8 Feb 2014 22:25:10 -0800 (PST)
Received: from mail-qc0-f169.google.com (mail-qc0-f169.google.com [209.85.216.169]) by ietfa.amsl.com (Postfix) with ESMTP id 50A7F1A0592 for <mib-doctors@ietf.org>; Sat,  8 Feb 2014 22:25:10 -0800 (PST)
Received: by mail-qc0-f169.google.com with SMTP id w7so8730464qcr.14 for <mib-doctors@ietf.org>; Sat, 08 Feb 2014 22:25:10 -0800 (PST)
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=ZxK1PF1n0TJldrWZI4ILK+pDfzVW4su9i+a2CZ8/zvs=; b=KPoTxBIk4Q3+8/69PFezZY8LVP4WytJduR7Bqkdse7svMozg1257m4R6jibS18+bTh t47Cb2TyFgFF/Bed2MZ6W3oPIHzGNo6UtyQhFP6Ul7yVHJX1ofXUf0RMY6sjz3NXIUve u0V2igxCr9wj0EBVSWJWTlmTD/OJWeiQ7/8gusCzMK3fiX45uAq5pyi+oNPMNqr++9A2 GIwMfM+SwW/BaXQLB3ub/p7vPhYSwd8aGuBtJBmGsZMyNg7y8MYsmCV+hQ75VmavQLwK YsiA+NIOpMjJxqGwQJ1hJGsJSNb6fYbRKd1ZRpat+vzLeO/8CgBt4IIisaa9jnOGgX9S zizA==
X-Gm-Message-State: ALoCoQmlwwHedf6VJeEWurKiW/53tsTIxJyzQZ9N7wJrijqTspypa36rDNSS11mWporezI/xYMWQ
MIME-Version: 1.0
X-Received: by 10.224.79.19 with SMTP id n19mr36412171qak.99.1391927110318; Sat, 08 Feb 2014 22:25:10 -0800 (PST)
Received: by 10.140.98.195 with HTTP; Sat, 8 Feb 2014 22:25:10 -0800 (PST)
In-Reply-To: <7D263081-6D84-4AA2-B0CB-FA74793BD135@comcast.net>
References: <05c501cf21ad$80d97ef0$828c7cd0$@olddog.co.uk> <7D263081-6D84-4AA2-B0CB-FA74793BD135@comcast.net>
Date: Sat, 8 Feb 2014 22:25:10 -0800
Message-ID: <CABCOCHT3UCVmpLcEAH2Q3mrfbWMxh=c7FZ4d61pAmpwb8t-sug@mail.gmail.com>
From: Andy Bierman <andy@yumaworks.com>
To: David Harrington <ietfdbh@comcast.net>
Content-Type: multipart/alternative; boundary=047d7bdc8040f6cffb04f1f34816
Cc: Adrian Farrel <adrian@olddog.co.uk>, "MIB Doctors \(E-mail\)" <mib-doctors@ietf.org>
Subject: Re: [MIB-DOCTORS] Read-only MIB modules
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: Sun, 09 Feb 2014 06:25:14 -0000

--047d7bdc8040f6cffb04f1f34816
Content-Type: text/plain; charset=ISO-8859-1

Hi,

I do not really know if an official statement to avoid SNMP Set is needed.
IMO the verdict is in wrt/ SNMP for configuration.

It has been a long-held tradition in the IETF to let people flail in their
own
sandbox if that's what they really wanted to do.  Maybe that has been a
mistake. Maybe WGs should be forced to prove that they have enough
real stakeholders willing to implement a spec, so that every part of
every proposed standard gets sponsored.

We often presume that "some vendors", who have had no interest in the
work all along, will eventually come around and decide to implement.
Therefore there is no need to have strong interest in deployment during
the WG process.

Commitment to implementation should apply to everything -- protocols,
MIB modules, YANG modules --- it doesn't matter. No stakeholders,
no sandbox.  That would be a radical change ;-)


Andy



On Sat, Feb 8, 2014 at 8:28 PM, David Harrington <ietfdbh@comcast.net>wrote:

> Hi,
>
> I object to this statement. (Should I say "strongly" object, to show I
> mean business?
>
> There are many RW objects that can "adjust" a network configuration
> assuming SET is supported by the agent involved.
> The NMS I used to work on, which helped determine and correct root cause
> for fault and performance problems, adjusted networks using writable MIB
> modules often.
> To tell WGs they should not develop RW MIB modules I think is wrong.
>
> I also have a concern with recommending Netconf/YANG at this point in time.
> If we looked up the top ten router vendors using something like Gartner
> reports, how many of them really support configuration using Netconf with
> YANG in shipping products?
> Ditto, the top ten switch vendors?
> How many of them can be fully configured using YANG modules (not homegrown
> alternatives, but modules - standard or proprietary - written using the
> standards-compliant YANG language)?
> I don't know the answer to that question, but would like to see some proof
> that YANG is at least as widely supported in currently shipping products as
> RW MIB objects.
> I think Netconf/YANG should compete in an open market with RW MIB modules,
> not try to stack the deck in their favor by "strongly discouraging" RW MIB
> standards.
>
> I have had discussions with vendors who are leaders in their particular
> networking niche, and they have told me they would not consider
> Netconf/YANG, because it has not been around long enough and been
> widely-enough deployed to prove stable for their production networks
> (whereas SNMP has enough track record to be known to be stable).
> So I'm a bit concerned about telling WGs they should develop YANG modules
> rather than MIB modules.
> And the current discussions of whether YANG 1.1 or 2.0 is needed to fix
> some problems with YANG 1.0, and it may not be backwards compatible, make
> me question the stability of YANG.
>
> Don't get me wrong. I support Netconf/YANG going forward, but I think it
> is important to provide advice that non-MIB-Doctors/non-YANG-experts can
> interpret reasonably.
> Any such statement should make a clear distinction between "configuration"
> - the complete configuration of a device by Netconf - versus RW objects in
> a MIB - which can be used by SNMP to adjust network
> parameters/configuration.
> Telling people not to develop RW MIBs is throwing the baby out with the
> bathwater.
> We should NOT recommend against RW MIBs, because these can be used for
> more than (full device) configuration.
> That point is far from clear in the currently proposed statement.
> Maybe the statement should be that, if a vendor wants to replace their
> CLI, they should replace it with Netconf/YANG, and not with SNMP/RW-MIBs.
> That's probably a closer approximation  of Netconf/YANG's applicability
> versus RW MIBs.
>
> In the past we have allowed implementations to make the conformance choice
> between supporting a MIB as RW, or implementing read-only.
> If we advise WGs to not develop module with RW objects, then we take the
> choice away from the vendors.
> I thick that would be a mistake.
>
> In  addition, it is pointed out later in this thread that other SDOs use
> RW MIBs.
> Well, those MIBs produced by other SDOs (and for that matter, vendors)
> might require some support for specific RW objects in IETF MIB modules.
> Therefore, I think it would be providing bad advice to say that IETF WGs
> should not produce MIB  modules with RW objects in them.
>
> If Netconf/YANG becomes widely deployed, then NMS implementations and
> operators can choose whether to use YANG or SNMP (or their CLI) to adjust
> network configurations.
> THat should not be a decision we make in the IETF, effectively forcing WGs
> to not develop MIBs with writable objects.
>
> Providing RW objects in MIB modules lets implementers and operators make
> the appropriate choice for their environments. (See RFC 3365 for similar
> thinking vis-a-vis security.)
>
> dbh
>
> On Feb 4, 2014, at 8:32 AM, Adrian Farrel <adrian@olddog.co.uk> wrote:
>
> Hi,
>
> The MPLS working group is testing the water to see whether one of its MIB
> modules should be "reduced" to read-only. This is the document that
> triggered my recent questions that led on to the draft advice you are
> working on. The WG took the document back to make this decision.
>
> You'll note below that we immediately have an implementation claim (not
> for this doc, but for the modules it extends).
>
> An interesting situation, I think.
>
> A
>
> *From:* mpls [mailto:mpls-bounces@ietf.org] *On Behalf Of *GyeRok Gwun
> (???)
> *Sent:* 04 February 2014 09:57
> *To:* 'mpls@ietf.org'
> *Cc:* 'mpls-chairs@tools.ietf.org'; '
> draft-ietf-mpls-tp-te-mib@tools.ietf.org'
> *Subject:* Re: [mpls] seeking consensus on making
> draft-ietf-mpls-tp-te-mib read- only
>
> No/oppose to make as Read-only mib.
> In our products we extensively use R/W object of TE mib. We also have
> NMS/EMS that use TE read-write Objects
>
> Best Regards
> Gwun
>
> -----Original Message-----
> From: mpls [mailto:mpls-bounces@ietf.org <mpls-bounces@ietf.org>] On
> Behalf Of Loa Andersson
> Sent: Monday, February 03, 2014 10:55 PM
> To: mpls@ietf.org
> Cc: mpls-chairs@tools.ietf.org; draft-ietf-mpls-tp-te-mib@tools.ietf.org
> Subject: [mpls] seeking consensus on making draft-ietf-mpls-tp-te-mib
> read- only
>
> Working Group,
>
> We have just recalled draft-ietf-mpls-tp-te-mib from the IESG to the
> working group for more work. We have a series of comments that are mostly
> for clarification. However the main reason for recalling the document is
> that there is one point where we need to confirm working group consensus.
>
> The IETF, the working group and the MIB Doctors are today very reluctant
> to produce read-write MIB modules. The current draft is read-write for a
> few objects, this is based on a consensus call for an earlier discussion,
> however the consensus call was not clear. It can be taken to mean both that
> we want to go with read-write objects and that we want to see read-only. Is
> it clear that it has been interpreted differently by different individuals.
>
> The authors and chairs have discussed the issue and we have a rough
> consensus that we want the MIB module(s) to be read-only.
>
> We therefore are asking the working group if this is OK for the MIB
> module(s) in the current document. Please indicate Support or Oppose for
> this MIB (draft-ietf-mpls-tp-te-mib) to be read-only.
>
> Please send your comments to the working group mailing list before
> February 18, 2014.
>
> Loa
> for the MPLS wg chairs
> --
>
>
> Loa Andersson                        email: loa@mail01.huawei.com
> Senior MPLS Expert                          loa@pi.nu
> Huawei Technologies (consultant)     phone: +46 739 81 21 64
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
>
> _______________________________________________
> 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
>
>

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

<div dir=3D"ltr">Hi,<div><br></div><div>I do not really know if an official=
 statement to avoid SNMP Set is needed.</div><div>IMO the verdict is in wrt=
/ SNMP for configuration.</div><div><br></div><div>It has been a long-held =
tradition in the IETF to let people flail in their own</div>
<div>sandbox if that&#39;s what they really wanted to do. =A0Maybe that has=
 been a</div><div>mistake. Maybe WGs should be forced to prove that they ha=
ve enough</div><div>real stakeholders willing to implement a spec, so that =
every part of</div>
<div>every proposed standard gets sponsored.</div><div><br></div><div>We of=
ten presume that &quot;some vendors&quot;, who have had no interest in the<=
/div><div>work all along, will eventually come around and decide to impleme=
nt.</div>
<div>Therefore there is no need to have strong interest in deployment durin=
g</div><div>the WG process.</div><div><br></div><div>Commitment to implemen=
tation should apply to everything -- protocols,</div><div>MIB modules, YANG=
 modules --- it doesn&#39;t matter. No stakeholders,</div>
<div>no sandbox. =A0That would be a radical change ;-)</div><div><br></div>=
<div><br></div><div>Andy</div><div><br></div></div><div class=3D"gmail_extr=
a"><br><br><div class=3D"gmail_quote">On Sat, Feb 8, 2014 at 8:28 PM, David=
 Harrington <span dir=3D"ltr">&lt;<a href=3D"mailto:ietfdbh@comcast.net" ta=
rget=3D"_blank">ietfdbh@comcast.net</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 style=3D"word-wrap:break-word">Hi,<div>=
<br></div><div>I object to this statement. (Should I say &quot;strongly&quo=
t; object, to show I mean business?</div>
<div><br></div><div>There are many RW objects that can &quot;adjust&quot; a=
 network configuration assuming SET is supported by the agent involved.</di=
v><div>The NMS I used to work on, which helped determine and correct root c=
ause for fault and performance problems, adjusted networks using writable M=
IB modules often.</div>
<div>To tell WGs they should not develop RW MIB modules I think is wrong.</=
div><div><br></div><div>I also have a concern with recommending Netconf/YAN=
G at this point in time.</div><div>If we looked up the top ten router vendo=
rs using something like Gartner reports, how many of them really support co=
nfiguration using Netconf with YANG in shipping products?</div>
<div>Ditto, the top ten switch vendors?</div><div>How many of them can be f=
ully configured using YANG modules (not homegrown alternatives, but modules=
 - standard or proprietary - written using the standards-compliant YANG lan=
guage)?</div>
<div>I don&#39;t know the answer to that question, but would like to see so=
me proof that YANG is at least as widely supported in currently shipping pr=
oducts as RW MIB objects.</div><div>I think Netconf/YANG should compete in =
an open market with RW MIB modules, not try to stack the deck in their favo=
r by &quot;strongly discouraging&quot; RW MIB standards.</div>
<div><br></div><div>I have had discussions with vendors who are leaders in =
their particular networking niche, and they have told me they would not con=
sider Netconf/YANG, because it has not been around long enough and been wid=
ely-enough deployed to prove stable for their production networks (whereas =
SNMP has enough track record to be known to be stable).</div>
<div>So I&#39;m a bit concerned about telling WGs they should develop YANG =
modules rather than MIB modules.</div><div>And the current discussions of w=
hether YANG 1.1 or 2.0 is needed to fix some problems with YANG 1.0, and it=
 may not be backwards compatible, make me question the stability of YANG.</=
div>
<div><br></div><div>Don&#39;t get me wrong. I support Netconf/YANG going fo=
rward, but I think it is important to provide advice that non-MIB-Doctors/n=
on-YANG-experts can interpret reasonably.</div><div>Any such statement shou=
ld make a clear distinction between &quot;configuration&quot; - the complet=
e configuration of a device by Netconf - versus RW objects in a MIB - which=
 can be used by SNMP to adjust network parameters/configuration.</div>
<div>Telling people not to develop RW MIBs is throwing the baby out with th=
e bathwater.</div><div>We should NOT recommend against RW MIBs, because the=
se can be used for more than (full device) configuration.</div><div>That po=
int is far from clear in the currently proposed statement.</div>
<div>Maybe the statement should be that, if a vendor wants to replace their=
 CLI, they should replace it with Netconf/YANG, and not with SNMP/RW-MIBs.=
=A0</div><div>That&#39;s probably a closer approximation =A0of Netconf/YANG=
&#39;s applicability versus RW MIBs.=A0</div>
<div><br></div><div>In the past we have allowed implementations to make the=
 conformance choice between supporting a MIB as RW, or implementing read-on=
ly.</div><div>If we advise WGs to not develop module with RW objects, then =
we take the choice away from the vendors.</div>
<div>I thick that would be a mistake.</div><div><br></div><div>In =A0additi=
on, it is pointed out later in this thread that other SDOs use RW MIBs.=A0<=
/div><div>Well, those MIBs produced by other SDOs (and for that matter, ven=
dors) might require some support for specific RW objects in IETF MIB module=
s.</div>
<div>Therefore, I think it would be providing bad advice to say that IETF W=
Gs should not produce MIB =A0modules with RW objects in them.</div><div><br=
></div><div>If Netconf/YANG becomes widely deployed, then NMS implementatio=
ns and operators can choose whether to use YANG or SNMP (or their CLI) to a=
djust network configurations.</div>
<div>THat should not be a decision we make in the IETF, effectively forcing=
 WGs to not develop MIBs with writable objects.</div><div><br></div><div>Pr=
oviding RW objects in MIB modules lets implementers and operators make the =
appropriate choice for their environments. (See RFC 3365 for similar thinki=
ng vis-a-vis security.)</div>
<div><br></div><div>dbh</div><div><br><div><div>On Feb 4, 2014, at 8:32 AM,=
 Adrian Farrel &lt;<a href=3D"mailto:adrian@olddog.co.uk" target=3D"_blank"=
>adrian@olddog.co.uk</a>&gt; wrote:</div><br><blockquote type=3D"cite"><div=
 lang=3D"EN-GB" link=3D"#0563C1" vlink=3D"#954F72" style=3D"font-family:Hel=
vetica;font-size:medium;font-style:normal;font-variant:normal;font-weight:n=
ormal;letter-spacing:normal;line-height:normal;text-align:-webkit-auto;text=
-indent:0px;text-transform:none;white-space:normal;word-spacing:0px">
<div><div style=3D"margin:0cm 0cm 0.0001pt;text-align:justify;word-break:no=
rmal;font-size:10pt;font-family:&#39;Malgun Gothic&#39;,sans-serif"><span s=
tyle=3D"font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"=
>Hi,<u></u><u></u></span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;text-align:justify;word-break:normal;=
font-size:10pt;font-family:&#39;Malgun Gothic&#39;,sans-serif"><span style=
=3D"font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">=A0=
</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;text-align:justify;word-break:normal;=
font-size:10pt;font-family:&#39;Malgun Gothic&#39;,sans-serif"><span style=
=3D"font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">The=
 MPLS working group is testing the water to see whether one of its MIB modu=
les should be &quot;reduced&quot; to read-only. This is the document that t=
riggered my recent questions that led on to the draft advice you are workin=
g on. The WG took the document back to make this decision.<u></u><u></u></s=
pan></div>
<div style=3D"margin:0cm 0cm 0.0001pt;text-align:justify;word-break:normal;=
font-size:10pt;font-family:&#39;Malgun Gothic&#39;,sans-serif"><span style=
=3D"font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">=A0=
</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;text-align:justify;word-break:normal;=
font-size:10pt;font-family:&#39;Malgun Gothic&#39;,sans-serif"><span style=
=3D"font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">You=
&#39;ll note below that we immediately have an implementation claim (not fo=
r this doc, but for the modules it extends).<u></u><u></u></span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;text-align:justify;word-break:normal;=
font-size:10pt;font-family:&#39;Malgun Gothic&#39;,sans-serif"><span style=
=3D"font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">=A0=
</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;text-align:justify;word-break:normal;=
font-size:10pt;font-family:&#39;Malgun Gothic&#39;,sans-serif"><span style=
=3D"font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">An =
interesting situation, I think.<u></u><u></u></span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;text-align:justify;word-break:normal;=
font-size:10pt;font-family:&#39;Malgun Gothic&#39;,sans-serif"><span style=
=3D"font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">=A0=
</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;text-align:justify;word-break:normal;=
font-size:10pt;font-family:&#39;Malgun Gothic&#39;,sans-serif"><span style=
=3D"font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">A<u=
></u><u></u></span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;text-align:justify;word-break:normal;=
font-size:10pt;font-family:&#39;Malgun Gothic&#39;,sans-serif"><span style=
=3D"font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">=A0=
</span></div>
<div style=3D"border-style:none none none solid;border-left-width:1.5pt;bor=
der-left-color:blue;padding:0cm 0cm 0cm 4pt"><div><div style=3D"border-styl=
e:solid none none;border-top-width:1pt;border-top-color:rgb(181,196,223);pa=
dding:3pt 0cm 0cm">
<div style=3D"margin:0cm 0cm 0.0001pt;text-align:left;word-break:normal;fon=
t-size:10pt;font-family:&#39;Malgun Gothic&#39;,sans-serif"><b><span lang=
=3D"EN-US" style=3D"font-family:Tahoma,sans-serif">From:</span></b><span la=
ng=3D"EN-US" style=3D"font-family:Tahoma,sans-serif"><span>=A0</span>mpls [=
mailto:<a href=3D"mailto:mpls-" target=3D"_blank">mpls-</a><a href=3D"mailt=
o:bounces@ietf.org" style=3D"color:rgb(149,79,114);text-decoration:underlin=
e" target=3D"_blank">bounces@ietf.org</a>]<span>=A0</span><b>On Behalf Of<s=
pan>=A0</span></b>GyeRok Gwun (???)<br>
<b>Sent:</b><span>=A0</span>04 February 2014 09:57<br><b>To:</b><span>=A0</=
span>&#39;<a href=3D"mailto:mpls@ietf.org" style=3D"color:rgb(149,79,114);t=
ext-decoration:underline" target=3D"_blank">mpls@ietf.org</a>&#39;<br><b>Cc=
:</b><span>=A0</span>&#39;<a href=3D"mailto:mpls-chairs@tools.ietf.org" sty=
le=3D"color:rgb(149,79,114);text-decoration:underline" target=3D"_blank">mp=
ls-chairs@tools.ietf.org</a>&#39;; &#39;<a href=3D"mailto:draft-ietf-mpls-t=
p-te-mib@tools.ietf.org" style=3D"color:rgb(149,79,114);text-decoration:und=
erline" target=3D"_blank">draft-ietf-mpls-tp-te-mib@tools.ietf.org</a>&#39;=
<br>
<b>Subject:</b><span>=A0</span>Re: [mpls] seeking consensus on making draft=
-ietf-mpls-tp-te-mib read- only<u></u><u></u></span></div></div></div><div =
style=3D"margin:0cm 0cm 0.0001pt;text-align:left;word-break:break-all;font-=
size:10pt;font-family:&#39;Malgun Gothic&#39;,sans-serif">
<u></u>=A0<u></u></div><div style=3D"margin:0cm 0cm 0.0001pt;word-break:bre=
ak-all;font-size:10pt;font-family:&#39;Courier New&#39;,serif"><span lang=
=3D"EN-US">No/oppose to make as Read-only mib.<u></u><u></u></span></div><d=
iv style=3D"margin:0cm 0cm 0.0001pt;word-break:break-all;font-size:10pt;fon=
t-family:&#39;Courier New&#39;,serif">
<span lang=3D"EN-US">In our products we extensively use R/W object of TE mi=
b. We also have NMS/EMS that use TE read-write Objects<u></u><u></u></span>=
</div><div style=3D"margin:0cm 0cm 0.0001pt;word-break:break-all;font-size:=
10pt;font-family:&#39;Courier New&#39;,serif">
<span lang=3D"EN-US">=A0</span></div><div style=3D"margin:0cm 0cm 0.0001pt;=
word-break:break-all;font-size:10pt;font-family:&#39;Courier New&#39;,serif=
"><span lang=3D"EN-US">Best Regards<u></u><u></u></span></div><div style=3D=
"margin:0cm 0cm 0.0001pt;word-break:break-all;font-size:10pt;font-family:&#=
39;Courier New&#39;,serif">
<span lang=3D"EN-US">Gwun<u></u><u></u></span></div><div style=3D"margin:0c=
m 0cm 0.0001pt;word-break:break-all;font-size:10pt;font-family:&#39;Courier=
 New&#39;,serif"><span lang=3D"EN-US">=A0</span></div><div style=3D"margin:=
0cm 0cm 0.0001pt;word-break:break-all;font-size:10pt;font-family:&#39;Couri=
er New&#39;,serif">
<span lang=3D"EN-US">-----Original Message-----<u></u><u></u></span></div><=
div style=3D"margin:0cm 0cm 0.0001pt;word-break:break-all;font-size:10pt;fo=
nt-family:&#39;Courier New&#39;,serif"><span lang=3D"EN-US">From: mpls [<a =
href=3D"mailto:mpls-bounces@ietf.org" style=3D"color:rgb(149,79,114);text-d=
ecoration:underline" target=3D"_blank">mailto:mpls-bounces@ietf.org</a>] On=
 Behalf Of Loa Andersson<u></u><u></u></span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;word-break:break-all;font-size:10pt;f=
ont-family:&#39;Courier New&#39;,serif"><span lang=3D"EN-US">Sent: Monday, =
February 03, 2014 10:55 PM<u></u><u></u></span></div><div style=3D"margin:0=
cm 0cm 0.0001pt;word-break:break-all;font-size:10pt;font-family:&#39;Courie=
r New&#39;,serif">
<span lang=3D"EN-US">To:<span>=A0</span><a href=3D"mailto:mpls@ietf.org" st=
yle=3D"color:rgb(149,79,114);text-decoration:underline" target=3D"_blank">m=
pls@ietf.org</a><u></u><u></u></span></div><div style=3D"margin:0cm 0cm 0.0=
001pt;word-break:break-all;font-size:10pt;font-family:&#39;Courier New&#39;=
,serif">
<span lang=3D"EN-US">Cc:<span>=A0</span><a href=3D"mailto:mpls-chairs@tools=
.ietf.org" style=3D"color:rgb(149,79,114);text-decoration:underline" target=
=3D"_blank">mpls-chairs@tools.ietf.org</a>;<span>=A0</span><a href=3D"mailt=
o:draft-ietf-mpls-tp-te-mib@tools.ietf.org" style=3D"color:rgb(149,79,114);=
text-decoration:underline" target=3D"_blank">draft-ietf-mpls-tp-te-mib@tool=
s.ietf.org</a><u></u><u></u></span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;word-break:break-all;font-size:10pt;f=
ont-family:&#39;Courier New&#39;,serif"><span lang=3D"EN-US">Subject: [mpls=
] seeking consensus on making draft-ietf-mpls-tp-te-mib read- only<u></u><u=
></u></span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;word-break:break-all;font-size:10pt;f=
ont-family:&#39;Courier New&#39;,serif"><span lang=3D"EN-US">=A0</span></di=
v><div style=3D"margin:0cm 0cm 0.0001pt;word-break:break-all;font-size:10pt=
;font-family:&#39;Courier New&#39;,serif">
<span lang=3D"EN-US">Working Group,<u></u><u></u></span></div><div style=3D=
"margin:0cm 0cm 0.0001pt;word-break:break-all;font-size:10pt;font-family:&#=
39;Courier New&#39;,serif"><span lang=3D"EN-US">=A0</span></div><div style=
=3D"margin:0cm 0cm 0.0001pt;word-break:break-all;font-size:10pt;font-family=
:&#39;Courier New&#39;,serif">
<span lang=3D"EN-US">We have just recalled draft-ietf-mpls-tp-te-mib from t=
he IESG to the working group for more work. We have a series of comments th=
at are mostly for clarification. However the main reason for recalling the =
document is that there is one point where we need to confirm working group =
consensus.<u></u><u></u></span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;word-break:break-all;font-size:10pt;f=
ont-family:&#39;Courier New&#39;,serif"><span lang=3D"EN-US">=A0</span></di=
v><div style=3D"margin:0cm 0cm 0.0001pt;word-break:break-all;font-size:10pt=
;font-family:&#39;Courier New&#39;,serif">
<span lang=3D"EN-US">The IETF, the working group and the MIB Doctors are to=
day very reluctant to produce read-write MIB modules. The current draft is =
read-write for a few objects, this is based on a consensus call for an earl=
ier discussion, however the consensus call was not clear. It can be taken t=
o mean both that we want to go with read-write objects and that we want to =
see read-only. Is it clear that it has been interpreted differently by diff=
erent individuals.<u></u><u></u></span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;word-break:break-all;font-size:10pt;f=
ont-family:&#39;Courier New&#39;,serif"><span lang=3D"EN-US">=A0</span></di=
v><div style=3D"margin:0cm 0cm 0.0001pt;word-break:break-all;font-size:10pt=
;font-family:&#39;Courier New&#39;,serif">
<span lang=3D"EN-US">The authors and chairs have discussed the issue and we=
 have a rough consensus that we want the MIB module(s) to be read-only.<u><=
/u><u></u></span></div><div style=3D"margin:0cm 0cm 0.0001pt;word-break:bre=
ak-all;font-size:10pt;font-family:&#39;Courier New&#39;,serif">
<span lang=3D"EN-US">=A0</span></div><div style=3D"margin:0cm 0cm 0.0001pt;=
word-break:break-all;font-size:10pt;font-family:&#39;Courier New&#39;,serif=
"><span lang=3D"EN-US">We therefore are asking the working group if this is=
 OK for the MIB<u></u><u></u></span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;word-break:break-all;font-size:10pt;f=
ont-family:&#39;Courier New&#39;,serif"><span lang=3D"EN-US">module(s) in t=
he current document. Please indicate Support or Oppose for this MIB (draft-=
ietf-mpls-tp-te-mib) to be read-only.<u></u><u></u></span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;word-break:break-all;font-size:10pt;f=
ont-family:&#39;Courier New&#39;,serif"><span lang=3D"EN-US">=A0</span></di=
v><div style=3D"margin:0cm 0cm 0.0001pt;word-break:break-all;font-size:10pt=
;font-family:&#39;Courier New&#39;,serif">
<span lang=3D"EN-US">Please send your comments to the working group mailing=
 list before February 18, 2014.<u></u><u></u></span></div><div style=3D"mar=
gin:0cm 0cm 0.0001pt;word-break:break-all;font-size:10pt;font-family:&#39;C=
ourier New&#39;,serif">
<span lang=3D"EN-US">=A0</span></div><div style=3D"margin:0cm 0cm 0.0001pt;=
word-break:break-all;font-size:10pt;font-family:&#39;Courier New&#39;,serif=
"><span lang=3D"EN-US">Loa<u></u><u></u></span></div><div style=3D"margin:0=
cm 0cm 0.0001pt;word-break:break-all;font-size:10pt;font-family:&#39;Courie=
r New&#39;,serif">
<span lang=3D"EN-US">for the MPLS wg chairs<u></u><u></u></span></div><div =
style=3D"margin:0cm 0cm 0.0001pt;word-break:break-all;font-size:10pt;font-f=
amily:&#39;Courier New&#39;,serif"><span lang=3D"EN-US">--<u></u><u></u></s=
pan></div>
<div style=3D"margin:0cm 0cm 0.0001pt;word-break:break-all;font-size:10pt;f=
ont-family:&#39;Courier New&#39;,serif"><span lang=3D"EN-US">=A0</span></di=
v><div style=3D"margin:0cm 0cm 0.0001pt;word-break:break-all;font-size:10pt=
;font-family:&#39;Courier New&#39;,serif">
<span lang=3D"EN-US">=A0</span></div><div style=3D"margin:0cm 0cm 0.0001pt;=
word-break:break-all;font-size:10pt;font-family:&#39;Courier New&#39;,serif=
"><span lang=3D"EN-US">Loa Andersson=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 email:<span>=A0</span><a href=3D"mailto:loa@=
mail01.huawei.com" style=3D"color:rgb(149,79,114);text-decoration:underline=
" target=3D"_blank">loa@mail01.huawei.com</a><u></u><u></u></span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;word-break:break-all;font-size:10pt;f=
ont-family:&#39;Courier New&#39;,serif"><span lang=3D"EN-US">Senior MPLS Ex=
pert=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0<span>=A0</span><a href=3D"mailto:loa@pi.nu" style=3D"color:rgb(149,7=
9,114);text-decoration:underline" target=3D"_blank">loa@pi.nu</a><u></u><u>=
</u></span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;word-break:break-all;font-size:10pt;f=
ont-family:&#39;Courier New&#39;,serif"><span lang=3D"EN-US">Huawei Technol=
ogies (consultant)=A0=A0=A0=A0 phone: +46 739 81 21 64<u></u><u></u></span>=
</div><div style=3D"margin:0cm 0cm 0.0001pt;word-break:break-all;font-size:=
10pt;font-family:&#39;Courier New&#39;,serif">
<span lang=3D"EN-US">_______________________________________________<u></u>=
<u></u></span></div><div style=3D"margin:0cm 0cm 0.0001pt;word-break:break-=
all;font-size:10pt;font-family:&#39;Courier New&#39;,serif"><span lang=3D"E=
N-US">mpls mailing list<u></u><u></u></span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;word-break:break-all;font-size:10pt;f=
ont-family:&#39;Courier New&#39;,serif"><span lang=3D"EN-US"><a href=3D"mai=
lto:mpls@ietf.org" style=3D"color:rgb(149,79,114);text-decoration:underline=
" target=3D"_blank">mpls@ietf.org</a><u></u><u></u></span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;word-break:break-all;font-size:10pt;f=
ont-family:&#39;Courier New&#39;,serif"><span lang=3D"EN-US"><a href=3D"htt=
ps://www.ietf.org/mailman/listinfo/mpls" style=3D"color:rgb(149,79,114);tex=
t-decoration:underline" target=3D"_blank">https://www.ietf.org/mailman/list=
info/mpls</a><u></u><u></u></span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;word-break:break-all;font-size:10pt;f=
ont-family:&#39;Courier New&#39;,serif"><span lang=3D"EN-US">______________=
_________________________________<u></u><u></u></span></div><div style=3D"m=
argin:0cm 0cm 0.0001pt;word-break:break-all;font-size:10pt;font-family:&#39=
;Courier New&#39;,serif">
<span lang=3D"EN-US">mpls mailing list<u></u><u></u></span></div><div style=
=3D"margin:0cm 0cm 0.0001pt;word-break:break-all;font-size:10pt;font-family=
:&#39;Courier New&#39;,serif"><span lang=3D"EN-US"><a href=3D"mailto:mpls@i=
etf.org" style=3D"color:rgb(149,79,114);text-decoration:underline" target=
=3D"_blank">mpls@ietf.org</a><u></u><u></u></span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;word-break:break-all;font-size:10pt;f=
ont-family:&#39;Courier New&#39;,serif"><span lang=3D"EN-US"><a href=3D"htt=
ps://www.ietf.org/mailman/listinfo/mpls" style=3D"color:rgb(149,79,114);tex=
t-decoration:underline" target=3D"_blank">https://www.ietf.org/mailman/list=
info/mpls</a><u></u><u></u></span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;text-align:justify;word-break:break-a=
ll;font-size:10pt;font-family:&#39;Malgun Gothic&#39;,sans-serif"><span lan=
g=3D"EN-US">=A0</span></div></div></div>___________________________________=
____________<br>
MIB-DOCTORS mailing list<br><a href=3D"mailto:MIB-DOCTORS@ietf.org" style=
=3D"color:rgb(149,79,114);text-decoration:underline" target=3D"_blank">MIB-=
DOCTORS@ietf.org</a><br><a href=3D"https://www.ietf.org/mailman/listinfo/mi=
b-doctors" style=3D"color:rgb(149,79,114);text-decoration:underline" target=
=3D"_blank">https://www.ietf.org/mailman/listinfo/mib-doctors</a><br>
</div></blockquote></div><br></div></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>

--047d7bdc8040f6cffb04f1f34816--

From adrian@olddog.co.uk  Sun Feb  9 08:23:14 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 6948F1A0405 for <mib-doctors@ietfa.amsl.com>; Sun,  9 Feb 2014 08:23:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.552
X-Spam-Level: 
X-Spam-Status: No, score=-0.552 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_BL_SPAMCOP_NET=1.347, RCVD_IN_DNSWL_NONE=-0.0001] 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 033_ya7NOXWC for <mib-doctors@ietfa.amsl.com>; Sun,  9 Feb 2014 08:23:10 -0800 (PST)
Received: from asmtp3.iomartmail.com (asmtp3.iomartmail.com [62.128.201.159]) by ietfa.amsl.com (Postfix) with ESMTP id 9D1A11A01E1 for <mib-doctors@ietf.org>; Sun,  9 Feb 2014 08:23:09 -0800 (PST)
Received: from asmtp3.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id s19GN8wX000909; Sun, 9 Feb 2014 16:23:08 GMT
Received: from 950129200 (14.21.90.92.rev.sfr.net [92.90.21.14]) (authenticated bits=0) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id s19GN4wZ000889 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sun, 9 Feb 2014 16:23:06 GMT
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Andy Bierman'" <andy@yumaworks.com>
References: <05c501cf21ad$80d97ef0$828c7cd0$@olddog.co.uk>	<7D263081-6D84-4AA2-B0CB-FA74793BD135@comcast.net> <CABCOCHT3UCVmpLcEAH2Q3mrfbWMxh=c7FZ4d61pAmpwb8t-sug@mail.gmail.com>
In-Reply-To: <CABCOCHT3UCVmpLcEAH2Q3mrfbWMxh=c7FZ4d61pAmpwb8t-sug@mail.gmail.com>
Date: Sun, 9 Feb 2014 16:23:04 -0000
Message-ID: <00d601cf25b3$371c77e0$a55567a0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_00D7_01CF25B3.3723A3D0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQFJjvDrKd3WqTHnQB+4M0ubo7RGRAHiKeZfAXsqdsKbnVvW8A==
Content-Language: en-gb
Cc: "'MIB Doctors \(E-mail\)'" <mib-doctors@ietf.org>
Subject: Re: [MIB-DOCTORS] Read-only MIB modules
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: Sun, 09 Feb 2014 16:23:14 -0000

This is a multipart message in MIME format.

------=_NextPart_000_00D7_01CF25B3.3723A3D0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Andy,
 
I am all in favour of flailing in sandboxes as a way to burn off that excess
energy caused by high-tartrazine diets.
 
However, I think SNMP Set is showing up because people are putting together MIB
modules sans clue. They genuinely want to be helpful in the construction of MIB
modules that might have value, but they don't know how to do it and no-one else
in their immediate circle does either.
 
The consequence, beyond a spec that might or might not get implemented in full,
is that the MIB doctors have to do reviews of function they don't believe has
value.
 
A
 
 
From: Andy Bierman [mailto:andy@yumaworks.com] 
Sent: 09 February 2014 06:25
To: David Harrington
Cc: Adrian Farrel; MIB Doctors (E-mail)
Subject: Re: [MIB-DOCTORS] Read-only MIB modules
 
Hi,
 
I do not really know if an official statement to avoid SNMP Set is needed.
IMO the verdict is in wrt/ SNMP for configuration.
 
It has been a long-held tradition in the IETF to let people flail in their own
sandbox if that's what they really wanted to do.  Maybe that has been a
mistake. Maybe WGs should be forced to prove that they have enough
real stakeholders willing to implement a spec, so that every part of
every proposed standard gets sponsored.
 
We often presume that "some vendors", who have had no interest in the
work all along, will eventually come around and decide to implement.
Therefore there is no need to have strong interest in deployment during
the WG process.
 
Commitment to implementation should apply to everything -- protocols,
MIB modules, YANG modules --- it doesn't matter. No stakeholders,
no sandbox.  That would be a radical change ;-)
 
 
Andy
 
 
On Sat, Feb 8, 2014 at 8:28 PM, David Harrington <ietfdbh@comcast.net> wrote:
Hi,
 
I object to this statement. (Should I say "strongly" object, to show I mean
business?
 
There are many RW objects that can "adjust" a network configuration assuming SET
is supported by the agent involved.
The NMS I used to work on, which helped determine and correct root cause for
fault and performance problems, adjusted networks using writable MIB modules
often.
To tell WGs they should not develop RW MIB modules I think is wrong.
 
I also have a concern with recommending Netconf/YANG at this point in time.
If we looked up the top ten router vendors using something like Gartner reports,
how many of them really support configuration using Netconf with YANG in
shipping products?
Ditto, the top ten switch vendors?
How many of them can be fully configured using YANG modules (not homegrown
alternatives, but modules - standard or proprietary - written using the
standards-compliant YANG language)?
I don't know the answer to that question, but would like to see some proof that
YANG is at least as widely supported in currently shipping products as RW MIB
objects.
I think Netconf/YANG should compete in an open market with RW MIB modules, not
try to stack the deck in their favor by "strongly discouraging" RW MIB
standards.
 
I have had discussions with vendors who are leaders in their particular
networking niche, and they have told me they would not consider Netconf/YANG,
because it has not been around long enough and been widely-enough deployed to
prove stable for their production networks (whereas SNMP has enough track record
to be known to be stable).
So I'm a bit concerned about telling WGs they should develop YANG modules rather
than MIB modules.
And the current discussions of whether YANG 1.1 or 2.0 is needed to fix some
problems with YANG 1.0, and it may not be backwards compatible, make me question
the stability of YANG.
 
Don't get me wrong. I support Netconf/YANG going forward, but I think it is
important to provide advice that non-MIB-Doctors/non-YANG-experts can interpret
reasonably.
Any such statement should make a clear distinction between "configuration" - the
complete configuration of a device by Netconf - versus RW objects in a MIB -
which can be used by SNMP to adjust network parameters/configuration.
Telling people not to develop RW MIBs is throwing the baby out with the
bathwater.
We should NOT recommend against RW MIBs, because these can be used for more than
(full device) configuration.
That point is far from clear in the currently proposed statement.
Maybe the statement should be that, if a vendor wants to replace their CLI, they
should replace it with Netconf/YANG, and not with SNMP/RW-MIBs. 
That's probably a closer approximation  of Netconf/YANG's applicability versus
RW MIBs. 
 
In the past we have allowed implementations to make the conformance choice
between supporting a MIB as RW, or implementing read-only.
If we advise WGs to not develop module with RW objects, then we take the choice
away from the vendors.
I thick that would be a mistake.
 
In  addition, it is pointed out later in this thread that other SDOs use RW
MIBs. 
Well, those MIBs produced by other SDOs (and for that matter, vendors) might
require some support for specific RW objects in IETF MIB modules.
Therefore, I think it would be providing bad advice to say that IETF WGs should
not produce MIB  modules with RW objects in them.
 
If Netconf/YANG becomes widely deployed, then NMS implementations and operators
can choose whether to use YANG or SNMP (or their CLI) to adjust network
configurations.
THat should not be a decision we make in the IETF, effectively forcing WGs to
not develop MIBs with writable objects.
 
Providing RW objects in MIB modules lets implementers and operators make the
appropriate choice for their environments. (See RFC 3365 for similar thinking
vis-a-vis security.)
 
dbh
 
On Feb 4, 2014, at 8:32 AM, Adrian Farrel <adrian@olddog.co.uk> wrote:



Hi,
 
The MPLS working group is testing the water to see whether one of its MIB
modules should be "reduced" to read-only. This is the document that triggered my
recent questions that led on to the draft advice you are working on. The WG took
the document back to make this decision.
 
You'll note below that we immediately have an implementation claim (not for this
doc, but for the modules it extends).
 
An interesting situation, I think.
 
A
 
From: mpls [mailto:mpls- <mailto:bounces@ietf.org> bounces@ietf.org] On Behalf
Of GyeRok Gwun (???)
Sent: 04 February 2014 09:57
To: ' <mailto:mpls@ietf.org> mpls@ietf.org'
Cc: ' <mailto:mpls-chairs@tools.ietf.org> mpls-chairs@tools.ietf.org'; '
<mailto:draft-ietf-mpls-tp-te-mib@tools.ietf.org>
draft-ietf-mpls-tp-te-mib@tools.ietf.org'
Subject: Re: [mpls] seeking consensus on making draft-ietf-mpls-tp-te-mib read-
only
 
No/oppose to make as Read-only mib.
In our products we extensively use R/W object of TE mib. We also have NMS/EMS
that use TE read-write Objects
 
Best Regards
Gwun
 
-----Original Message-----
From: mpls [ <mailto:mpls-bounces@ietf.org> mailto:mpls-bounces@ietf.org] On
Behalf Of Loa Andersson
Sent: Monday, February 03, 2014 10:55 PM
To:  <mailto:mpls@ietf.org> mpls@ietf.org
Cc:  <mailto:mpls-chairs@tools.ietf.org> mpls-chairs@tools.ietf.org;
<mailto:draft-ietf-mpls-tp-te-mib@tools.ietf.org>
draft-ietf-mpls-tp-te-mib@tools.ietf.org
Subject: [mpls] seeking consensus on making draft-ietf-mpls-tp-te-mib read- only
 
Working Group,
 
We have just recalled draft-ietf-mpls-tp-te-mib from the IESG to the working
group for more work. We have a series of comments that are mostly for
clarification. However the main reason for recalling the document is that there
is one point where we need to confirm working group consensus.
 
The IETF, the working group and the MIB Doctors are today very reluctant to
produce read-write MIB modules. The current draft is read-write for a few
objects, this is based on a consensus call for an earlier discussion, however
the consensus call was not clear. It can be taken to mean both that we want to
go with read-write objects and that we want to see read-only. Is it clear that
it has been interpreted differently by different individuals.
 
The authors and chairs have discussed the issue and we have a rough consensus
that we want the MIB module(s) to be read-only.
 
We therefore are asking the working group if this is OK for the MIB
module(s) in the current document. Please indicate Support or Oppose for this
MIB (draft-ietf-mpls-tp-te-mib) to be read-only.
 
Please send your comments to the working group mailing list before February 18,
2014.
 
Loa
for the MPLS wg chairs
--
 
 
Loa Andersson                        email:  <mailto:loa@mail01.huawei.com>
loa@mail01.huawei.com
Senior MPLS Expert                           <mailto:loa@pi.nu> loa@pi.nu
Huawei Technologies (consultant)     phone: +46 739 81 21 64
_______________________________________________
mpls mailing list
 <mailto:mpls@ietf.org> mpls@ietf.org
 <https://www.ietf.org/mailman/listinfo/mpls>
https://www.ietf.org/mailman/listinfo/mpls
_______________________________________________
mpls mailing list
 <mailto:mpls@ietf.org> mpls@ietf.org
 <https://www.ietf.org/mailman/listinfo/mpls>
https://www.ietf.org/mailman/listinfo/mpls
 
_______________________________________________
MIB-DOCTORS mailing list
 <mailto:MIB-DOCTORS@ietf.org> MIB-DOCTORS@ietf.org
 <https://www.ietf.org/mailman/listinfo/mib-doctors>
https://www.ietf.org/mailman/listinfo/mib-doctors
 

_______________________________________________
MIB-DOCTORS mailing list
MIB-DOCTORS@ietf.org
https://www.ietf.org/mailman/listinfo/mib-doctors
 

------=_NextPart_000_00D7_01CF25B3.3723A3D0
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@01CF25B2.AFBA1CD0"><!--[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>
<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:Helvetica;
	panose-1:2 11 6 4 2 2 2 2 2 4;
	mso-font-charset:0;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:-536859905 -1073711037 9 0 511 0;}
@font-face
	{font-family:Helvetica;
	panose-1:2 11 6 4 2 2 2 2 2 4;
	mso-font-charset:0;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:-536859905 -1073711037 9 0 511 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:"Malgun Gothic";
	panose-1:2 11 5 3 2 0 0 2 0 4;
	mso-font-charset:129;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:-1879047505 165117179 18 0 524289 0;}
@font-face
	{font-family:"\@Malgun Gothic";
	panose-1:2 11 5 3 2 0 0 2 0 4;
	mso-font-charset:129;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:-1879047505 165117179 18 0 524289 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;}
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;}
span.EmailStyle17
	{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-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";
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;
	mso-header-margin:36.0pt;
	mso-footer-margin:36.0pt;
	mso-paper-source:0;}
div.WordSection1
	{page:WordSection1;}
--></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:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-ascii-font-family:Calibri;
	mso-hansi-font-family:Calibri;
	mso-fareast-language:EN-US;}
</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 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'>Andy,<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'>I am all in favour of flailing =
in sandboxes as a way to burn off that excess energy caused by =
high-tartrazine diets.<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'>However, I think SNMP Set is =
showing up because people are putting together MIB modules sans clue. =
They genuinely want to be helpful in the construction of MIB modules =
that might have value, but they don't know how to do it and no-one else =
in their immediate circle does either.<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'>The consequence, beyond a spec =
that might or might not get implemented in full, is that the MIB doctors =
have to do reviews of function they don't believe has =
value.<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";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";mso-ansi-language:EN-US'> Andy Bierman =
[mailto:andy@yumaworks.com] <br><b>Sent:</b> 09 February 2014 =
06:25<br><b>To:</b> David Harrington<br><b>Cc:</b> Adrian Farrel; MIB =
Doctors (E-mail)<br><b>Subject:</b> Re: [MIB-DOCTORS] Read-only MIB =
modules<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><p =
class=3DMsoNormal>Hi,<o:p></o:p></p><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>I =
do not really know if an official statement to avoid SNMP Set is =
needed.<o:p></o:p></p></div><div><p class=3DMsoNormal>IMO the verdict is =
in wrt/ SNMP for configuration.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>It has been a long-held tradition in the IETF to let =
people flail in their own<o:p></o:p></p></div><div><p =
class=3DMsoNormal>sandbox if that's what they really wanted to do. =
&nbsp;Maybe that has been a<o:p></o:p></p></div><div><p =
class=3DMsoNormal>mistake. Maybe WGs should be forced to prove that they =
have enough<o:p></o:p></p></div><div><p class=3DMsoNormal>real =
stakeholders willing to implement a spec, so that every part =
of<o:p></o:p></p></div><div><p class=3DMsoNormal>every proposed standard =
gets sponsored.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>We often presume that &quot;some vendors&quot;, who =
have had no interest in the<o:p></o:p></p></div><div><p =
class=3DMsoNormal>work all along, will eventually come around and decide =
to implement.<o:p></o:p></p></div><div><p class=3DMsoNormal>Therefore =
there is no need to have strong interest in deployment =
during<o:p></o:p></p></div><div><p class=3DMsoNormal>the WG =
process.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>Commitment to implementation should apply to =
everything -- protocols,<o:p></o:p></p></div><div><p =
class=3DMsoNormal>MIB modules, YANG modules --- it doesn't matter. No =
stakeholders,<o:p></o:p></p></div><div><p class=3DMsoNormal>no sandbox. =
&nbsp;That would be a radical change ;-)<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>Andy<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div><div><p =
class=3DMsoNormal =
style=3D'margin-bottom:12.0pt'><o:p>&nbsp;</o:p></p><div><p =
class=3DMsoNormal>On Sat, Feb 8, 2014 at 8:28 PM, David Harrington =
&lt;<a href=3D"mailto:ietfdbh@comcast.net" =
target=3D"_blank">ietfdbh@comcast.net</a>&gt; =
wrote:<o:p></o:p></p><div><p class=3DMsoNormal>Hi,<o:p></o:p></p><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>I =
object to this statement. (Should I say &quot;strongly&quot; object, to =
show I mean business?<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>There are many RW objects that can &quot;adjust&quot; =
a network configuration assuming SET is supported by the agent =
involved.<o:p></o:p></p></div><div><p class=3DMsoNormal>The NMS I used =
to work on, which helped determine and correct root cause for fault and =
performance problems, adjusted networks using writable MIB modules =
often.<o:p></o:p></p></div><div><p class=3DMsoNormal>To tell WGs they =
should not develop RW MIB modules I think is =
wrong.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>I =
also have a concern with recommending Netconf/YANG at this point in =
time.<o:p></o:p></p></div><div><p class=3DMsoNormal>If we looked up the =
top ten router vendors using something like Gartner reports, how many of =
them really support configuration using Netconf with YANG in shipping =
products?<o:p></o:p></p></div><div><p class=3DMsoNormal>Ditto, the top =
ten switch vendors?<o:p></o:p></p></div><div><p class=3DMsoNormal>How =
many of them can be fully configured using YANG modules (not homegrown =
alternatives, but modules - standard or proprietary - written using the =
standards-compliant YANG language)?<o:p></o:p></p></div><div><p =
class=3DMsoNormal>I don't know the answer to that question, but would =
like to see some proof that YANG is at least as widely supported in =
currently shipping products as RW MIB =
objects.<o:p></o:p></p></div><div><p class=3DMsoNormal>I think =
Netconf/YANG should compete in an open market with RW MIB modules, not =
try to stack the deck in their favor by &quot;strongly =
discouraging&quot; RW MIB standards.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>I =
have had discussions with vendors who are leaders in their particular =
networking niche, and they have told me they would not consider =
Netconf/YANG, because it has not been around long enough and been =
widely-enough deployed to prove stable for their production networks =
(whereas SNMP has enough track record to be known to be =
stable).<o:p></o:p></p></div><div><p class=3DMsoNormal>So I'm a bit =
concerned about telling WGs they should develop YANG modules rather than =
MIB modules.<o:p></o:p></p></div><div><p class=3DMsoNormal>And the =
current discussions of whether YANG 1.1 or 2.0 is needed to fix some =
problems with YANG 1.0, and it may not be backwards compatible, make me =
question the stability of YANG.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>Don't get me wrong. I support Netconf/YANG going =
forward, but I think it is important to provide advice that =
non-MIB-Doctors/non-YANG-experts can interpret =
reasonably.<o:p></o:p></p></div><div><p class=3DMsoNormal>Any such =
statement should make a clear distinction between =
&quot;configuration&quot; - the complete configuration of a device by =
Netconf - versus RW objects in a MIB - which can be used by SNMP to =
adjust network parameters/configuration.<o:p></o:p></p></div><div><p =
class=3DMsoNormal>Telling people not to develop RW MIBs is throwing the =
baby out with the bathwater.<o:p></o:p></p></div><div><p =
class=3DMsoNormal>We should NOT recommend against RW MIBs, because these =
can be used for more than (full device) =
configuration.<o:p></o:p></p></div><div><p class=3DMsoNormal>That point =
is far from clear in the currently proposed =
statement.<o:p></o:p></p></div><div><p class=3DMsoNormal>Maybe the =
statement should be that, if a vendor wants to replace their CLI, they =
should replace it with Netconf/YANG, and not with =
SNMP/RW-MIBs.&nbsp;<o:p></o:p></p></div><div><p class=3DMsoNormal>That's =
probably a closer approximation &nbsp;of Netconf/YANG's applicability =
versus RW MIBs.&nbsp;<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>In the past we have allowed implementations to make =
the conformance choice between supporting a MIB as RW, or implementing =
read-only.<o:p></o:p></p></div><div><p class=3DMsoNormal>If we advise =
WGs to not develop module with RW objects, then we take the choice away =
from the vendors.<o:p></o:p></p></div><div><p class=3DMsoNormal>I thick =
that would be a mistake.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>In &nbsp;addition, it is pointed out later in this =
thread that other SDOs use RW MIBs.&nbsp;<o:p></o:p></p></div><div><p =
class=3DMsoNormal>Well, those MIBs produced by other SDOs (and for that =
matter, vendors) might require some support for specific RW objects in =
IETF MIB modules.<o:p></o:p></p></div><div><p =
class=3DMsoNormal>Therefore, I think it would be providing bad advice to =
say that IETF WGs should not produce MIB &nbsp;modules with RW objects =
in them.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>If Netconf/YANG becomes widely deployed, then NMS =
implementations and operators can choose whether to use YANG or SNMP (or =
their CLI) to adjust network configurations.<o:p></o:p></p></div><div><p =
class=3DMsoNormal>THat should not be a decision we make in the IETF, =
effectively forcing WGs to not develop MIBs with writable =
objects.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>Providing RW objects in MIB modules lets implementers =
and operators make the appropriate choice for their environments. (See =
RFC 3365 for similar thinking vis-a-vis =
security.)<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>dbh<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><div><p class=3DMsoNormal>On =
Feb 4, 2014, at 8:32 AM, Adrian Farrel &lt;<a =
href=3D"mailto:adrian@olddog.co.uk" =
target=3D"_blank">adrian@olddog.co.uk</a>&gt; =
wrote:<o:p></o:p></p></div><p class=3DMsoNormal><br =
style=3D'mso-special-character:line-break'><![if =
!supportLineBreakNewLine]><br =
style=3D'mso-special-character:line-break'><![endif]><o:p></o:p></p><div>=
<div><p class=3DMsoNormal style=3D'text-align:justify'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-fareast-=
font-family:"Malgun =
Gothic";mso-bidi-font-family:Helvetica;color:#1F497D'>Hi,</span><span =
style=3D'font-size:10.0pt;font-family:"Malgun =
Gothic","sans-serif";mso-bidi-font-family:Helvetica'><o:p></o:p></span></=
p><p class=3DMsoNormal style=3D'text-align:justify'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-fareast-=
font-family:"Malgun =
Gothic";mso-bidi-font-family:Helvetica;color:#1F497D'>&nbsp;</span><span =
style=3D'font-size:10.0pt;font-family:"Malgun =
Gothic","sans-serif";mso-bidi-font-family:Helvetica'><o:p></o:p></span></=
p><p class=3DMsoNormal style=3D'text-align:justify'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-fareast-=
font-family:"Malgun =
Gothic";mso-bidi-font-family:Helvetica;color:#1F497D'>The MPLS working =
group is testing the water to see whether one of its MIB modules should =
be &quot;reduced&quot; to read-only. This is the document that triggered =
my recent questions that led on to the draft advice you are working on. =
The WG took the document back to make this decision.</span><span =
style=3D'font-size:10.0pt;font-family:"Malgun =
Gothic","sans-serif";mso-bidi-font-family:Helvetica'><o:p></o:p></span></=
p><p class=3DMsoNormal style=3D'text-align:justify'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-fareast-=
font-family:"Malgun =
Gothic";mso-bidi-font-family:Helvetica;color:#1F497D'>&nbsp;</span><span =
style=3D'font-size:10.0pt;font-family:"Malgun =
Gothic","sans-serif";mso-bidi-font-family:Helvetica'><o:p></o:p></span></=
p><p class=3DMsoNormal style=3D'text-align:justify'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-fareast-=
font-family:"Malgun =
Gothic";mso-bidi-font-family:Helvetica;color:#1F497D'>You'll note below =
that we immediately have an implementation claim (not for this doc, but =
for the modules it extends).</span><span =
style=3D'font-size:10.0pt;font-family:"Malgun =
Gothic","sans-serif";mso-bidi-font-family:Helvetica'><o:p></o:p></span></=
p><p class=3DMsoNormal style=3D'text-align:justify'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-fareast-=
font-family:"Malgun =
Gothic";mso-bidi-font-family:Helvetica;color:#1F497D'>&nbsp;</span><span =
style=3D'font-size:10.0pt;font-family:"Malgun =
Gothic","sans-serif";mso-bidi-font-family:Helvetica'><o:p></o:p></span></=
p><p class=3DMsoNormal style=3D'text-align:justify'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-fareast-=
font-family:"Malgun =
Gothic";mso-bidi-font-family:Helvetica;color:#1F497D'>An interesting =
situation, I think.</span><span =
style=3D'font-size:10.0pt;font-family:"Malgun =
Gothic","sans-serif";mso-bidi-font-family:Helvetica'><o:p></o:p></span></=
p><p class=3DMsoNormal style=3D'text-align:justify'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-fareast-=
font-family:"Malgun =
Gothic";mso-bidi-font-family:Helvetica;color:#1F497D'>&nbsp;</span><span =
style=3D'font-size:10.0pt;font-family:"Malgun =
Gothic","sans-serif";mso-bidi-font-family:Helvetica'><o:p></o:p></span></=
p><p class=3DMsoNormal style=3D'text-align:justify'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-fareast-=
font-family:"Malgun =
Gothic";mso-bidi-font-family:Helvetica;color:#1F497D'>A</span><span =
style=3D'font-size:10.0pt;font-family:"Malgun =
Gothic","sans-serif";mso-bidi-font-family:Helvetica'><o:p></o:p></span></=
p><p class=3DMsoNormal style=3D'text-align:justify'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-fareast-=
font-family:"Malgun =
Gothic";mso-bidi-font-family:Helvetica;color:#1F497D'>&nbsp;</span><span =
style=3D'font-size:10.0pt;font-family:"Malgun =
Gothic","sans-serif";mso-bidi-font-family:Helvetica'><o:p></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:"Malgun =
Gothic";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:"Malgun Gothic";mso-ansi-language:EN-US'>&nbsp;mpls =
[mailto:<a href=3D"mailto:mpls-" target=3D"_blank">mpls-</a><a =
href=3D"mailto:bounces@ietf.org" target=3D"_blank"><span =
style=3D'color:#954F72'>bounces@ietf.org</span></a>]&nbsp;<b>On Behalf =
Of&nbsp;</b>GyeRok Gwun (???)<br><b>Sent:</b>&nbsp;04 February 2014 =
09:57<br><b>To:</b>&nbsp;'<a href=3D"mailto:mpls@ietf.org" =
target=3D"_blank"><span =
style=3D'color:#954F72'>mpls@ietf.org</span></a>'<br><b>Cc:</b>&nbsp;'<a =
href=3D"mailto:mpls-chairs@tools.ietf.org" target=3D"_blank"><span =
style=3D'color:#954F72'>mpls-chairs@tools.ietf.org</span></a>'; '<a =
href=3D"mailto:draft-ietf-mpls-tp-te-mib@tools.ietf.org" =
target=3D"_blank"><span =
style=3D'color:#954F72'>draft-ietf-mpls-tp-te-mib@tools.ietf.org</span></=
a>'<br><b>Subject:</b>&nbsp;Re: [mpls] seeking consensus on making =
draft-ietf-mpls-tp-te-mib read- only</span><span =
style=3D'font-size:10.0pt;font-family:"Malgun =
Gothic","sans-serif";mso-bidi-font-family:Helvetica'><o:p></o:p></span></=
p></div></div><p class=3DMsoNormal style=3D'word-break:break-all'><span =
style=3D'font-size:10.0pt;font-family:"Malgun =
Gothic","sans-serif";mso-bidi-font-family:Helvetica'>&nbsp;<o:p></o:p></s=
pan></p><div><p class=3DMsoNormal style=3D'word-break:break-all'><span =
lang=3DEN-US style=3D'font-size:10.0pt;font-family:"Courier =
New";mso-ansi-language:EN-US'>No/oppose to make as Read-only =
mib.</span><span style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'word-break:break-all'><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Courier =
New";mso-ansi-language:EN-US'>In our products we extensively use R/W =
object of TE mib. We also have NMS/EMS that use TE read-write =
Objects</span><span style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'word-break:break-all'><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Courier =
New";mso-ansi-language:EN-US'>&nbsp;</span><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'word-break:break-all'><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Courier =
New";mso-ansi-language:EN-US'>Best Regards</span><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'word-break:break-all'><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Courier =
New";mso-ansi-language:EN-US'>Gwun</span><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'word-break:break-all'><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Courier =
New";mso-ansi-language:EN-US'>&nbsp;</span><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'word-break:break-all'><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Courier =
New";mso-ansi-language:EN-US'>-----Original Message-----</span><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'word-break:break-all'><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Courier =
New";mso-ansi-language:EN-US'>From: mpls [<a =
href=3D"mailto:mpls-bounces@ietf.org" target=3D"_blank"><span =
style=3D'color:#954F72'>mailto:mpls-bounces@ietf.org</span></a>] On =
Behalf Of Loa Andersson</span><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'word-break:break-all'><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Courier =
New";mso-ansi-language:EN-US'>Sent: Monday, February 03, 2014 10:55 =
PM</span><span style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'word-break:break-all'><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Courier =
New";mso-ansi-language:EN-US'>To:&nbsp;<a href=3D"mailto:mpls@ietf.org" =
target=3D"_blank"><span =
style=3D'color:#954F72'>mpls@ietf.org</span></a></span><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'word-break:break-all'><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Courier =
New";mso-ansi-language:EN-US'>Cc:&nbsp;<a =
href=3D"mailto:mpls-chairs@tools.ietf.org" target=3D"_blank"><span =
style=3D'color:#954F72'>mpls-chairs@tools.ietf.org</span></a>;&nbsp;<a =
href=3D"mailto:draft-ietf-mpls-tp-te-mib@tools.ietf.org" =
target=3D"_blank"><span =
style=3D'color:#954F72'>draft-ietf-mpls-tp-te-mib@tools.ietf.org</span></=
a></span><span style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'word-break:break-all'><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Courier =
New";mso-ansi-language:EN-US'>Subject: [mpls] seeking consensus on =
making draft-ietf-mpls-tp-te-mib read- only</span><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'word-break:break-all'><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Courier =
New";mso-ansi-language:EN-US'>&nbsp;</span><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'word-break:break-all'><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Courier =
New";mso-ansi-language:EN-US'>Working Group,</span><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'word-break:break-all'><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Courier =
New";mso-ansi-language:EN-US'>&nbsp;</span><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'word-break:break-all'><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Courier =
New";mso-ansi-language:EN-US'>We have just recalled =
draft-ietf-mpls-tp-te-mib from the IESG to the working group for more =
work. We have a series of comments that are mostly for clarification. =
However the main reason for recalling the document is that there is one =
point where we need to confirm working group consensus.</span><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'word-break:break-all'><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Courier =
New";mso-ansi-language:EN-US'>&nbsp;</span><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'word-break:break-all'><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Courier =
New";mso-ansi-language:EN-US'>The IETF, the working group and the MIB =
Doctors are today very reluctant to produce read-write MIB modules. The =
current draft is read-write for a few objects, this is based on a =
consensus call for an earlier discussion, however the consensus call was =
not clear. It can be taken to mean both that we want to go with =
read-write objects and that we want to see read-only. Is it clear that =
it has been interpreted differently by different =
individuals.</span><span style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'word-break:break-all'><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Courier =
New";mso-ansi-language:EN-US'>&nbsp;</span><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'word-break:break-all'><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Courier =
New";mso-ansi-language:EN-US'>The authors and chairs have discussed the =
issue and we have a rough consensus that we want the MIB module(s) to be =
read-only.</span><span style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'word-break:break-all'><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Courier =
New";mso-ansi-language:EN-US'>&nbsp;</span><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'word-break:break-all'><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Courier =
New";mso-ansi-language:EN-US'>We therefore are asking the working group =
if this is OK for the MIB</span><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'word-break:break-all'><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Courier =
New";mso-ansi-language:EN-US'>module(s) in the current document. Please =
indicate Support or Oppose for this MIB (draft-ietf-mpls-tp-te-mib) to =
be read-only.</span><span style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'word-break:break-all'><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Courier =
New";mso-ansi-language:EN-US'>&nbsp;</span><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'word-break:break-all'><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Courier =
New";mso-ansi-language:EN-US'>Please send your comments to the working =
group mailing list before February 18, 2014.</span><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'word-break:break-all'><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Courier =
New";mso-ansi-language:EN-US'>&nbsp;</span><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'word-break:break-all'><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Courier =
New";mso-ansi-language:EN-US'>Loa</span><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'word-break:break-all'><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Courier =
New";mso-ansi-language:EN-US'>for the MPLS wg chairs</span><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'word-break:break-all'><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Courier =
New";mso-ansi-language:EN-US'>--</span><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'word-break:break-all'><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Courier =
New";mso-ansi-language:EN-US'>&nbsp;</span><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'word-break:break-all'><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Courier =
New";mso-ansi-language:EN-US'>&nbsp;</span><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'word-break:break-all'><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Courier =
New";mso-ansi-language:EN-US'>Loa =
Andersson&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
; email:&nbsp;<a href=3D"mailto:loa@mail01.huawei.com" =
target=3D"_blank"><span =
style=3D'color:#954F72'>loa@mail01.huawei.com</span></a></span><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'word-break:break-all'><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Courier =
New";mso-ansi-language:EN-US'>Senior MPLS =
Expert&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;<a href=3D"mailto:loa@pi.nu" target=3D"_blank"><span =
style=3D'color:#954F72'>loa@pi.nu</span></a></span><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'word-break:break-all'><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Courier =
New";mso-ansi-language:EN-US'>Huawei Technologies =
(consultant)&nbsp;&nbsp;&nbsp;&nbsp; phone: +46 739 81 21 64</span><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'word-break:break-all'><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Courier =
New";mso-ansi-language:EN-US'>___________________________________________=
____</span><span style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'word-break:break-all'><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Courier =
New";mso-ansi-language:EN-US'>mpls mailing list</span><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'word-break:break-all'><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Courier =
New";mso-ansi-language:EN-US'><a href=3D"mailto:mpls@ietf.org" =
target=3D"_blank"><span =
style=3D'color:#954F72'>mpls@ietf.org</span></a></span><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'word-break:break-all'><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Courier =
New";mso-ansi-language:EN-US'><a =
href=3D"https://www.ietf.org/mailman/listinfo/mpls" =
target=3D"_blank"><span =
style=3D'color:#954F72'>https://www.ietf.org/mailman/listinfo/mpls</span>=
</a></span><span style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'word-break:break-all'><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Courier =
New";mso-ansi-language:EN-US'>___________________________________________=
____</span><span style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'word-break:break-all'><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Courier =
New";mso-ansi-language:EN-US'>mpls mailing list</span><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'word-break:break-all'><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Courier =
New";mso-ansi-language:EN-US'><a href=3D"mailto:mpls@ietf.org" =
target=3D"_blank"><span =
style=3D'color:#954F72'>mpls@ietf.org</span></a></span><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'word-break:break-all'><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Courier =
New";mso-ansi-language:EN-US'><a =
href=3D"https://www.ietf.org/mailman/listinfo/mpls" =
target=3D"_blank"><span =
style=3D'color:#954F72'>https://www.ietf.org/mailman/listinfo/mpls</span>=
</a></span><span style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p></o:p></span></p></div><p class=3DMsoNormal =
style=3D'text-align:justify;word-break:break-all'><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Malgun =
Gothic","sans-serif";mso-bidi-font-family:Helvetica;mso-ansi-language:EN-=
US'>&nbsp;</span><span style=3D'font-size:10.0pt;font-family:"Malgun =
Gothic","sans-serif";mso-bidi-font-family:Helvetica'><o:p></o:p></span></=
p></div></div><p class=3DMsoNormal><span =
style=3D'font-size:13.5pt;font-family:"Helvetica","sans-serif"'>_________=
______________________________________<br>MIB-DOCTORS mailing list<br><a =
href=3D"mailto:MIB-DOCTORS@ietf.org" target=3D"_blank"><span =
style=3D'color:#954F72'>MIB-DOCTORS@ietf.org</span></a><br><a =
href=3D"https://www.ietf.org/mailman/listinfo/mib-doctors" =
target=3D"_blank"><span =
style=3D'color:#954F72'>https://www.ietf.org/mailman/listinfo/mib-doctors=
</span></a><o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div><p class=3DMsoNormal =
style=3D'margin-bottom:12.0pt'><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"_blank">https://www.ietf.org/mailman/listinfo/mib-doctors</a><o=
:p></o:p></p></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div></div></body></html>
------=_NextPart_000_00D7_01CF25B3.3723A3D0--


From andy@yumaworks.com  Sun Feb  9 09:23:12 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 263581A0398 for <mib-doctors@ietfa.amsl.com>; Sun,  9 Feb 2014 09:23:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Level: 
X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 2za0vMAgJiph for <mib-doctors@ietfa.amsl.com>; Sun,  9 Feb 2014 09:23:07 -0800 (PST)
Received: from mail-qc0-f170.google.com (mail-qc0-f170.google.com [209.85.216.170]) by ietfa.amsl.com (Postfix) with ESMTP id E9EEA1A02F8 for <mib-doctors@ietf.org>; Sun,  9 Feb 2014 09:23:06 -0800 (PST)
Received: by mail-qc0-f170.google.com with SMTP id e9so9187576qcy.15 for <mib-doctors@ietf.org>; Sun, 09 Feb 2014 09:23:06 -0800 (PST)
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=YyVcl1jcsG4sF5cmmGOPBSa7qLyHc3rbIJVtNWYpBII=; b=aseqD4JH3VeQb8vm5nM2GTaG7MJmDUAnGqe20P9xhxDd+mWGQFN0KIg5UEfAOOtELW ecnbY4x8tKfxsizMcSOMdnyADnRYKjVxB6tVfz5tWJJaJqXarhEygGXw/skwp95rZIKM 6nGaHZXWQsO6dzWUn8wCa9QzNQJPhxNRxSSsAhT22jCuu3bLyRU/E3M0fgynh00W1IAN /jV00KG3iV29ply91O+ThYDuLU3uEHnlI0dWmjSSM4okmyYT8dj4dJm6MOicHOsLOssM 8dgBvniAT1CTWMrApERTiKVweOOhwXSAIBhL8ky/SD9fubjKpYg6Ax0gmLS6bOA73zvu ShTw==
X-Gm-Message-State: ALoCoQn9p4NF3e/j7PlaQn5KbEFYdEJMsY84wgFfWEZR7X1oWxcBZW0pXwXeUjPxiwxA9bbX694k
MIME-Version: 1.0
X-Received: by 10.224.46.130 with SMTP id j2mr40476035qaf.7.1391966586623; Sun, 09 Feb 2014 09:23:06 -0800 (PST)
Received: by 10.140.98.130 with HTTP; Sun, 9 Feb 2014 09:23:06 -0800 (PST)
In-Reply-To: <00d601cf25b3$371c77e0$a55567a0$@olddog.co.uk>
References: <05c501cf21ad$80d97ef0$828c7cd0$@olddog.co.uk> <7D263081-6D84-4AA2-B0CB-FA74793BD135@comcast.net> <CABCOCHT3UCVmpLcEAH2Q3mrfbWMxh=c7FZ4d61pAmpwb8t-sug@mail.gmail.com> <00d601cf25b3$371c77e0$a55567a0$@olddog.co.uk>
Date: Sun, 9 Feb 2014 09:23:06 -0800
Message-ID: <CABCOCHQJsBy8DvPEOy-b1Xs-MWzfgZCwWtWjrpngHLeicMAefA@mail.gmail.com>
From: Andy Bierman <andy@yumaworks.com>
To: Adrian Farrel <adrian@olddog.co.uk>
Content-Type: multipart/alternative; boundary=001a11c2a9caef689d04f1fc79ec
Cc: "MIB Doctors \(E-mail\)" <mib-doctors@ietf.org>
Subject: Re: [MIB-DOCTORS] Read-only MIB modules
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: Sun, 09 Feb 2014 17:23:12 -0000

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

On Sun, Feb 9, 2014 at 8:23 AM, Adrian Farrel <adrian@olddog.co.uk> wrote:

> Andy,
>
>
>
> I am all in favour of flailing in sandboxes as a way to burn off that
> excess energy caused by high-tartrazine diets.
>
>
>
> However, I think SNMP Set is showing up because people are putting
> together MIB modules sans clue. They genuinely want to be helpful in the
> construction of MIB modules that might have value, but they don't know how
> to do it and no-one else in their immediate circle does either.
>
>
>
> The consequence, beyond a spec that might or might not get implemented in
> full, is that the MIB doctors have to do reviews of function they don't
> believe has value.
>
>
>

The IESG and IETF have to reviews these documents as well.
I think people writing MIB modules know how to do it, but they are
following a formula setup by the IESG and blessed by MIB Doctors.

MIB authors seem encouraged to use read-create objects, but then
add MIN-ACCESS read-only in the conformance statement,
just in case anybody ever wants to implement the MAX-ACCESS.

Time to face the fact that nobody is implementing the MAX-ACCESS.
In order to claim conformance to a MIB module, it should be
without this MIB-ACCESS loophole.  WG groups can then decide
if they have enough participants who plan on implementing read-create.
If not, then they can't have it.  The MIB gets rejected and sent back
to the WG if it contains any MIN-ACCESS clauses.


Andy




A
>
>
>
>
>
> *From:* Andy Bierman [mailto:andy@yumaworks.com]
> *Sent:* 09 February 2014 06:25
> *To:* David Harrington
> *Cc:* Adrian Farrel; MIB Doctors (E-mail)
> *Subject:* Re: [MIB-DOCTORS] Read-only MIB modules
>
>
>
> Hi,
>
>
>
> I do not really know if an official statement to avoid SNMP Set is needed.
>
> IMO the verdict is in wrt/ SNMP for configuration.
>
>
>
> It has been a long-held tradition in the IETF to let people flail in their
> own
>
> sandbox if that's what they really wanted to do.  Maybe that has been a
>
> mistake. Maybe WGs should be forced to prove that they have enough
>
> real stakeholders willing to implement a spec, so that every part of
>
> every proposed standard gets sponsored.
>
>
>
> We often presume that "some vendors", who have had no interest in the
>
> work all along, will eventually come around and decide to implement.
>
> Therefore there is no need to have strong interest in deployment during
>
> the WG process.
>
>
>
> Commitment to implementation should apply to everything -- protocols,
>
> MIB modules, YANG modules --- it doesn't matter. No stakeholders,
>
> no sandbox.  That would be a radical change ;-)
>
>
>
>
>
> Andy
>
>
>
>
>
> On Sat, Feb 8, 2014 at 8:28 PM, David Harrington <ietfdbh@comcast.net>
> wrote:
>
> Hi,
>
>
>
> I object to this statement. (Should I say "strongly" object, to show I
> mean business?
>
>
>
> There are many RW objects that can "adjust" a network configuration
> assuming SET is supported by the agent involved.
>
> The NMS I used to work on, which helped determine and correct root cause
> for fault and performance problems, adjusted networks using writable MIB
> modules often.
>
> To tell WGs they should not develop RW MIB modules I think is wrong.
>
>
>
> I also have a concern with recommending Netconf/YANG at this point in time.
>
> If we looked up the top ten router vendors using something like Gartner
> reports, how many of them really support configuration using Netconf with
> YANG in shipping products?
>
> Ditto, the top ten switch vendors?
>
> How many of them can be fully configured using YANG modules (not homegrown
> alternatives, but modules - standard or proprietary - written using the
> standards-compliant YANG language)?
>
> I don't know the answer to that question, but would like to see some proof
> that YANG is at least as widely supported in currently shipping products as
> RW MIB objects.
>
> I think Netconf/YANG should compete in an open market with RW MIB modules,
> not try to stack the deck in their favor by "strongly discouraging" RW MIB
> standards.
>
>
>
> I have had discussions with vendors who are leaders in their particular
> networking niche, and they have told me they would not consider
> Netconf/YANG, because it has not been around long enough and been
> widely-enough deployed to prove stable for their production networks
> (whereas SNMP has enough track record to be known to be stable).
>
> So I'm a bit concerned about telling WGs they should develop YANG modules
> rather than MIB modules.
>
> And the current discussions of whether YANG 1.1 or 2.0 is needed to fix
> some problems with YANG 1.0, and it may not be backwards compatible, make
> me question the stability of YANG.
>
>
>
> Don't get me wrong. I support Netconf/YANG going forward, but I think it
> is important to provide advice that non-MIB-Doctors/non-YANG-experts can
> interpret reasonably.
>
> Any such statement should make a clear distinction between "configuration"
> - the complete configuration of a device by Netconf - versus RW objects in
> a MIB - which can be used by SNMP to adjust network
> parameters/configuration.
>
> Telling people not to develop RW MIBs is throwing the baby out with the
> bathwater.
>
> We should NOT recommend against RW MIBs, because these can be used for
> more than (full device) configuration.
>
> That point is far from clear in the currently proposed statement.
>
> Maybe the statement should be that, if a vendor wants to replace their
> CLI, they should replace it with Netconf/YANG, and not with SNMP/RW-MIBs.
>
> That's probably a closer approximation  of Netconf/YANG's applicability
> versus RW MIBs.
>
>
>
> In the past we have allowed implementations to make the conformance choice
> between supporting a MIB as RW, or implementing read-only.
>
> If we advise WGs to not develop module with RW objects, then we take the
> choice away from the vendors.
>
> I thick that would be a mistake.
>
>
>
> In  addition, it is pointed out later in this thread that other SDOs use
> RW MIBs.
>
> Well, those MIBs produced by other SDOs (and for that matter, vendors)
> might require some support for specific RW objects in IETF MIB modules.
>
> Therefore, I think it would be providing bad advice to say that IETF WGs
> should not produce MIB  modules with RW objects in them.
>
>
>
> If Netconf/YANG becomes widely deployed, then NMS implementations and
> operators can choose whether to use YANG or SNMP (or their CLI) to adjust
> network configurations.
>
> THat should not be a decision we make in the IETF, effectively forcing WGs
> to not develop MIBs with writable objects.
>
>
>
> Providing RW objects in MIB modules lets implementers and operators make
> the appropriate choice for their environments. (See RFC 3365 for similar
> thinking vis-a-vis security.)
>
>
>
> dbh
>
>
>
> On Feb 4, 2014, at 8:32 AM, Adrian Farrel <adrian@olddog.co.uk> wrote:
>
>
>
> Hi,
>
>
>
> The MPLS working group is testing the water to see whether one of its MIB
> modules should be "reduced" to read-only. This is the document that
> triggered my recent questions that led on to the draft advice you are
> working on. The WG took the document back to make this decision.
>
>
>
> You'll note below that we immediately have an implementation claim (not
> for this doc, but for the modules it extends).
>
>
>
> An interesting situation, I think.
>
>
>
> A
>
>
>
> *From:* mpls [mailto:mpls-bounces@ietf.org] *On Behalf Of *GyeRok Gwun
> (???)
> *Sent:* 04 February 2014 09:57
> *To:* 'mpls@ietf.org'
> *Cc:* 'mpls-chairs@tools.ietf.org'; '
> draft-ietf-mpls-tp-te-mib@tools.ietf.org'
> *Subject:* Re: [mpls] seeking consensus on making
> draft-ietf-mpls-tp-te-mib read- only
>
>
>
> No/oppose to make as Read-only mib.
>
> In our products we extensively use R/W object of TE mib. We also have
> NMS/EMS that use TE read-write Objects
>
>
>
> Best Regards
>
> Gwun
>
>
>
> -----Original Message-----
>
> From: mpls [mailto:mpls-bounces@ietf.org <mpls-bounces@ietf.org>] On
> Behalf Of Loa Andersson
>
> Sent: Monday, February 03, 2014 10:55 PM
>
> To: mpls@ietf.org
>
> Cc: mpls-chairs@tools.ietf.org; draft-ietf-mpls-tp-te-mib@tools.ietf.org
>
> Subject: [mpls] seeking consensus on making draft-ietf-mpls-tp-te-mib
> read- only
>
>
>
> Working Group,
>
>
>
> We have just recalled draft-ietf-mpls-tp-te-mib from the IESG to the
> working group for more work. We have a series of comments that are mostly
> for clarification. However the main reason for recalling the document is
> that there is one point where we need to confirm working group consensus.
>
>
>
> The IETF, the working group and the MIB Doctors are today very reluctant
> to produce read-write MIB modules. The current draft is read-write for a
> few objects, this is based on a consensus call for an earlier discussion,
> however the consensus call was not clear. It can be taken to mean both that
> we want to go with read-write objects and that we want to see read-only. Is
> it clear that it has been interpreted differently by different individuals.
>
>
>
> The authors and chairs have discussed the issue and we have a rough
> consensus that we want the MIB module(s) to be read-only.
>
>
>
> We therefore are asking the working group if this is OK for the MIB
>
> module(s) in the current document. Please indicate Support or Oppose for
> this MIB (draft-ietf-mpls-tp-te-mib) to be read-only.
>
>
>
> Please send your comments to the working group mailing list before
> February 18, 2014.
>
>
>
> Loa
>
> for the MPLS wg chairs
>
> --
>
>
>
>
>
> Loa Andersson                        email: loa@mail01.huawei.com
>
> Senior MPLS Expert                          loa@pi.nu
>
> Huawei Technologies (consultant)     phone: +46 739 81 21 64
>
> _______________________________________________
>
> mpls mailing list
>
> mpls@ietf.org
>
> https://www.ietf.org/mailman/listinfo/mpls
>
> _______________________________________________
>
> mpls mailing list
>
> mpls@ietf.org
>
> https://www.ietf.org/mailman/listinfo/mpls
>
>
>
> _______________________________________________
> 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
>
>
>

--001a11c2a9caef689d04f1fc79ec
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 Sun, Feb 9, 2014 at 8:23 AM, Adrian Farrel <span dir=3D"ltr">&lt=
;<a href=3D"mailto:adrian@olddog.co.uk" target=3D"_blank">adrian@olddog.co.=
uk</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 lang=3D"EN-GB" link=3D"blue" vlink=3D"p=
urple"><p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&=
quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">Andy,<u></u><u></u=
></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"><u></u>=A0<u></u></span><=
/p><p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">I am all in favour of =
flailing in sandboxes as a way to burn off that excess energy caused by hig=
h-tartrazine diets.<u></u><u></u></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"><u></u>=A0<u></u></span><=
/p><p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">However, I think SNMP =
Set is showing up because people are putting together MIB modules sans clue=
. They genuinely want to be helpful in the construction of MIB modules that=
 might have value, but they don&#39;t know how to do it and no-one else in =
their immediate circle does either.<u></u><u></u></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"><u></u>=A0<u></u></span><=
/p><p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">The consequence, beyon=
d a spec that might or might not get implemented in full, is that the MIB d=
octors have to do reviews of function they don&#39;t believe has value.<u><=
/u><u></u></span></p>
<p class=3D"MsoNormal"><br></p></div></blockquote><div><br></div><div><br><=
/div><div>The IESG and IETF have to reviews these documents as well.</div><=
div>I think people writing MIB modules know how to do it, but they are</div=
>
<div>following a formula setup by the IESG and blessed by MIB Doctors.</div=
><div><br></div><div>MIB authors seem encouraged to use read-create objects=
, but then</div><div>add MIN-ACCESS read-only in the conformance statement,=
</div>
<div>just in case anybody ever wants to implement the MAX-ACCESS.</div><div=
><br></div><div>Time to face the fact that nobody is implementing the MAX-A=
CCESS.</div><div>In order to claim conformance to a MIB module, it should b=
e</div>
<div>without this MIB-ACCESS loophole. =A0WG groups can then decide</div><d=
iv>if they have enough participants who plan on implementing read-create.</=
div><div>If not, then they can&#39;t have it. =A0The MIB gets rejected and =
sent back</div>
<div>to the WG if it contains any MIN-ACCESS clauses.</div><div><br></div><=
div><br></div><div>Andy</div><div><br></div><div><br></div><div><br></div><=
div><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex">
<div lang=3D"EN-GB" link=3D"blue" vlink=3D"purple"><p class=3D"MsoNormal"><=
/p><p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">A<u></u><u></u></span>=
</p><p class=3D"MsoNormal">
<span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-=
serif&quot;;color:#1f497d"><u></u>=A0<u></u></span></p><p class=3D"MsoNorma=
l"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;;color:#1f497d"><u></u>=A0<u></u></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;paddin=
g:3.0pt 0cm 0cm 0cm"><p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=
=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"=
>From:</span></b><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family=
:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Andy Bierman [mailto:<a href=
=3D"mailto:andy@yumaworks.com" target=3D"_blank">andy@yumaworks.com</a>] <b=
r>
<b>Sent:</b> 09 February 2014 06:25<br><b>To:</b> David Harrington<br><b>Cc=
:</b> Adrian Farrel; MIB Doctors (E-mail)<br><b>Subject:</b> Re: [MIB-DOCTO=
RS] Read-only MIB modules<u></u><u></u></span></p></div></div><p class=3D"M=
soNormal">
<u></u>=A0<u></u></p><div><p class=3D"MsoNormal">Hi,<u></u><u></u></p><div>=
<p class=3D"MsoNormal"><u></u>=A0<u></u></p></div><div><p class=3D"MsoNorma=
l">I do not really know if an official statement to avoid SNMP Set is neede=
d.<u></u><u></u></p>
</div><div><p class=3D"MsoNormal">IMO the verdict is in wrt/ SNMP for confi=
guration.<u></u><u></u></p></div><div><p class=3D"MsoNormal"><u></u>=A0<u><=
/u></p></div><div><p class=3D"MsoNormal">It has been a long-held tradition =
in the IETF to let people flail in their own<u></u><u></u></p>
</div><div><p class=3D"MsoNormal">sandbox if that&#39;s what they really wa=
nted to do. =A0Maybe that has been a<u></u><u></u></p></div><div><p class=
=3D"MsoNormal">mistake. Maybe WGs should be forced to prove that they have =
enough<u></u><u></u></p>
</div><div><p class=3D"MsoNormal">real stakeholders willing to implement a =
spec, so that every part of<u></u><u></u></p></div><div><p class=3D"MsoNorm=
al">every proposed standard gets sponsored.<u></u><u></u></p></div><div><p =
class=3D"MsoNormal">
<u></u>=A0<u></u></p></div><div><p class=3D"MsoNormal">We often presume tha=
t &quot;some vendors&quot;, who have had no interest in the<u></u><u></u></=
p></div><div><p class=3D"MsoNormal">work all along, will eventually come ar=
ound and decide to implement.<u></u><u></u></p>
</div><div><p class=3D"MsoNormal">Therefore there is no need to have strong=
 interest in deployment during<u></u><u></u></p></div><div><p class=3D"MsoN=
ormal">the WG process.<u></u><u></u></p></div><div><p class=3D"MsoNormal"><=
u></u>=A0<u></u></p>
</div><div><p class=3D"MsoNormal">Commitment to implementation should apply=
 to everything -- protocols,<u></u><u></u></p></div><div><p class=3D"MsoNor=
mal">MIB modules, YANG modules --- it doesn&#39;t matter. No stakeholders,<=
u></u><u></u></p>
</div><div><p class=3D"MsoNormal">no sandbox. =A0That would be a radical ch=
ange ;-)<u></u><u></u></p></div><div><p class=3D"MsoNormal"><u></u>=A0<u></=
u></p></div><div><p class=3D"MsoNormal"><u></u>=A0<u></u></p></div><div><p =
class=3D"MsoNormal">
Andy<u></u><u></u></p></div><div><p class=3D"MsoNormal"><u></u>=A0<u></u></=
p></div></div><div><p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><u=
></u>=A0<u></u></p><div><p class=3D"MsoNormal">On Sat, Feb 8, 2014 at 8:28 =
PM, David Harrington &lt;<a href=3D"mailto:ietfdbh@comcast.net" target=3D"_=
blank">ietfdbh@comcast.net</a>&gt; wrote:<u></u><u></u></p>
<div><p class=3D"MsoNormal">Hi,<u></u><u></u></p><div><p class=3D"MsoNormal=
"><u></u>=A0<u></u></p></div><div><p class=3D"MsoNormal">I object to this s=
tatement. (Should I say &quot;strongly&quot; object, to show I mean busines=
s?<u></u><u></u></p>
</div><div><p class=3D"MsoNormal"><u></u>=A0<u></u></p></div><div><p class=
=3D"MsoNormal">There are many RW objects that can &quot;adjust&quot; a netw=
ork configuration assuming SET is supported by the agent involved.<u></u><u=
></u></p>
</div><div><p class=3D"MsoNormal">The NMS I used to work on, which helped d=
etermine and correct root cause for fault and performance problems, adjuste=
d networks using writable MIB modules often.<u></u><u></u></p></div><div>
<p class=3D"MsoNormal">To tell WGs they should not develop RW MIB modules I=
 think is wrong.<u></u><u></u></p></div><div><p class=3D"MsoNormal"><u></u>=
=A0<u></u></p></div><div><p class=3D"MsoNormal">I also have a concern with =
recommending Netconf/YANG at this point in time.<u></u><u></u></p>
</div><div><p class=3D"MsoNormal">If we looked up the top ten router vendor=
s using something like Gartner reports, how many of them really support con=
figuration using Netconf with YANG in shipping products?<u></u><u></u></p>
</div><div><p class=3D"MsoNormal">Ditto, the top ten switch vendors?<u></u>=
<u></u></p></div><div><p class=3D"MsoNormal">How many of them can be fully =
configured using YANG modules (not homegrown alternatives, but modules - st=
andard or proprietary - written using the standards-compliant YANG language=
)?<u></u><u></u></p>
</div><div><p class=3D"MsoNormal">I don&#39;t know the answer to that quest=
ion, but would like to see some proof that YANG is at least as widely suppo=
rted in currently shipping products as RW MIB objects.<u></u><u></u></p></d=
iv>
<div><p class=3D"MsoNormal">I think Netconf/YANG should compete in an open =
market with RW MIB modules, not try to stack the deck in their favor by &qu=
ot;strongly discouraging&quot; RW MIB standards.<u></u><u></u></p></div><di=
v>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p></div><div><p class=3D"MsoNorma=
l">I have had discussions with vendors who are leaders in their particular =
networking niche, and they have told me they would not consider Netconf/YAN=
G, because it has not been around long enough and been widely-enough deploy=
ed to prove stable for their production networks (whereas SNMP has enough t=
rack record to be known to be stable).<u></u><u></u></p>
</div><div><p class=3D"MsoNormal">So I&#39;m a bit concerned about telling =
WGs they should develop YANG modules rather than MIB modules.<u></u><u></u>=
</p></div><div><p class=3D"MsoNormal">And the current discussions of whethe=
r YANG 1.1 or 2.0 is needed to fix some problems with YANG 1.0, and it may =
not be backwards compatible, make me question the stability of YANG.<u></u>=
<u></u></p>
</div><div><p class=3D"MsoNormal"><u></u>=A0<u></u></p></div><div><p class=
=3D"MsoNormal">Don&#39;t get me wrong. I support Netconf/YANG going forward=
, but I think it is important to provide advice that non-MIB-Doctors/non-YA=
NG-experts can interpret reasonably.<u></u><u></u></p>
</div><div><p class=3D"MsoNormal">Any such statement should make a clear di=
stinction between &quot;configuration&quot; - the complete configuration of=
 a device by Netconf - versus RW objects in a MIB - which can be used by SN=
MP to adjust network parameters/configuration.<u></u><u></u></p>
</div><div><p class=3D"MsoNormal">Telling people not to develop RW MIBs is =
throwing the baby out with the bathwater.<u></u><u></u></p></div><div><p cl=
ass=3D"MsoNormal">We should NOT recommend against RW MIBs, because these ca=
n be used for more than (full device) configuration.<u></u><u></u></p>
</div><div><p class=3D"MsoNormal">That point is far from clear in the curre=
ntly proposed statement.<u></u><u></u></p></div><div><p class=3D"MsoNormal"=
>Maybe the statement should be that, if a vendor wants to replace their CLI=
, they should replace it with Netconf/YANG, and not with SNMP/RW-MIBs.=A0<u=
></u><u></u></p>
</div><div><p class=3D"MsoNormal">That&#39;s probably a closer approximatio=
n =A0of Netconf/YANG&#39;s applicability versus RW MIBs.=A0<u></u><u></u></=
p></div><div><p class=3D"MsoNormal"><u></u>=A0<u></u></p></div><div><p clas=
s=3D"MsoNormal">
In the past we have allowed implementations to make the conformance choice =
between supporting a MIB as RW, or implementing read-only.<u></u><u></u></p=
></div><div><p class=3D"MsoNormal">If we advise WGs to not develop module w=
ith RW objects, then we take the choice away from the vendors.<u></u><u></u=
></p>
</div><div><p class=3D"MsoNormal">I thick that would be a mistake.<u></u><u=
></u></p></div><div><p class=3D"MsoNormal"><u></u>=A0<u></u></p></div><div>=
<p class=3D"MsoNormal">In =A0addition, it is pointed out later in this thre=
ad that other SDOs use RW MIBs.=A0<u></u><u></u></p>
</div><div><p class=3D"MsoNormal">Well, those MIBs produced by other SDOs (=
and for that matter, vendors) might require some support for specific RW ob=
jects in IETF MIB modules.<u></u><u></u></p></div><div><p class=3D"MsoNorma=
l">
Therefore, I think it would be providing bad advice to say that IETF WGs sh=
ould not produce MIB =A0modules with RW objects in them.<u></u><u></u></p><=
/div><div><p class=3D"MsoNormal"><u></u>=A0<u></u></p></div><div><p class=
=3D"MsoNormal">
If Netconf/YANG becomes widely deployed, then NMS implementations and opera=
tors can choose whether to use YANG or SNMP (or their CLI) to adjust networ=
k configurations.<u></u><u></u></p></div><div><p class=3D"MsoNormal">THat s=
hould not be a decision we make in the IETF, effectively forcing WGs to not=
 develop MIBs with writable objects.<u></u><u></u></p>
</div><div><p class=3D"MsoNormal"><u></u>=A0<u></u></p></div><div><p class=
=3D"MsoNormal">Providing RW objects in MIB modules lets implementers and op=
erators make the appropriate choice for their environments. (See RFC 3365 f=
or similar thinking vis-a-vis security.)<u></u><u></u></p>
</div><div><p class=3D"MsoNormal"><u></u>=A0<u></u></p></div><div><p class=
=3D"MsoNormal">dbh<u></u><u></u></p></div><div><p class=3D"MsoNormal"><u></=
u>=A0<u></u></p><div><div><p class=3D"MsoNormal">On Feb 4, 2014, at 8:32 AM=
, Adrian Farrel &lt;<a href=3D"mailto:adrian@olddog.co.uk" target=3D"_blank=
">adrian@olddog.co.uk</a>&gt; wrote:<u></u><u></u></p>
</div><p class=3D"MsoNormal"><br><u></u><br><u></u><u></u><u></u></p><div><=
div><p class=3D"MsoNormal" style=3D"text-align:justify"><span style=3D"font=
-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#=
1f497d">Hi,</span><span style=3D"font-size:10.0pt;font-family:&quot;Malgun =
Gothic&quot;,&quot;sans-serif&quot;"><u></u><u></u></span></p>
<p class=3D"MsoNormal" style=3D"text-align:justify"><span style=3D"font-siz=
e:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f49=
7d">=A0</span><span style=3D"font-size:10.0pt;font-family:&quot;Malgun Goth=
ic&quot;,&quot;sans-serif&quot;"><u></u><u></u></span></p>
<p class=3D"MsoNormal" style=3D"text-align:justify"><span style=3D"font-siz=
e:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f49=
7d">The MPLS working group is testing the water to see whether one of its M=
IB modules should be &quot;reduced&quot; to read-only. This is the document=
 that triggered my recent questions that led on to the draft advice you are=
 working on. The WG took the document back to make this decision.</span><sp=
an style=3D"font-size:10.0pt;font-family:&quot;Malgun Gothic&quot;,&quot;sa=
ns-serif&quot;"><u></u><u></u></span></p>
<p class=3D"MsoNormal" style=3D"text-align:justify"><span style=3D"font-siz=
e:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f49=
7d">=A0</span><span style=3D"font-size:10.0pt;font-family:&quot;Malgun Goth=
ic&quot;,&quot;sans-serif&quot;"><u></u><u></u></span></p>
<p class=3D"MsoNormal" style=3D"text-align:justify"><span style=3D"font-siz=
e:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f49=
7d">You&#39;ll note below that we immediately have an implementation claim =
(not for this doc, but for the modules it extends).</span><span style=3D"fo=
nt-size:10.0pt;font-family:&quot;Malgun Gothic&quot;,&quot;sans-serif&quot;=
"><u></u><u></u></span></p>
<p class=3D"MsoNormal" style=3D"text-align:justify"><span style=3D"font-siz=
e:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f49=
7d">=A0</span><span style=3D"font-size:10.0pt;font-family:&quot;Malgun Goth=
ic&quot;,&quot;sans-serif&quot;"><u></u><u></u></span></p>
<p class=3D"MsoNormal" style=3D"text-align:justify"><span style=3D"font-siz=
e:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f49=
7d">An interesting situation, I think.</span><span style=3D"font-size:10.0p=
t;font-family:&quot;Malgun Gothic&quot;,&quot;sans-serif&quot;"><u></u><u><=
/u></span></p>
<p class=3D"MsoNormal" style=3D"text-align:justify"><span style=3D"font-siz=
e:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f49=
7d">=A0</span><span style=3D"font-size:10.0pt;font-family:&quot;Malgun Goth=
ic&quot;,&quot;sans-serif&quot;"><u></u><u></u></span></p>
<p class=3D"MsoNormal" style=3D"text-align:justify"><span style=3D"font-siz=
e:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f49=
7d">A</span><span style=3D"font-size:10.0pt;font-family:&quot;Malgun Gothic=
&quot;,&quot;sans-serif&quot;"><u></u><u></u></span></p>
<p class=3D"MsoNormal" style=3D"text-align:justify"><span style=3D"font-siz=
e:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f49=
7d">=A0</span><span style=3D"font-size:10.0pt;font-family:&quot;Malgun Goth=
ic&quot;,&quot;sans-serif&quot;"><u></u><u></u></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;paddin=
g:3.0pt 0cm 0cm 0cm"><p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=
=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"=
>From:</span></b><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family=
:&quot;Tahoma&quot;,&quot;sans-serif&quot;">=A0mpls [mailto:<a href=3D"mail=
to:mpls-" target=3D"_blank">mpls-</a><a href=3D"mailto:bounces@ietf.org" ta=
rget=3D"_blank"><span style=3D"color:#954f72">bounces@ietf.org</span></a>]=
=A0<b>On Behalf Of=A0</b>GyeRok Gwun (???)<br>
<b>Sent:</b>=A004 February 2014 09:57<br><b>To:</b>=A0&#39;<a href=3D"mailt=
o:mpls@ietf.org" target=3D"_blank"><span style=3D"color:#954f72">mpls@ietf.=
org</span></a>&#39;<br><b>Cc:</b>=A0&#39;<a href=3D"mailto:mpls-chairs@tool=
s.ietf.org" target=3D"_blank"><span style=3D"color:#954f72">mpls-chairs@too=
ls.ietf.org</span></a>&#39;; &#39;<a href=3D"mailto:draft-ietf-mpls-tp-te-m=
ib@tools.ietf.org" target=3D"_blank"><span style=3D"color:#954f72">draft-ie=
tf-mpls-tp-te-mib@tools.ietf.org</span></a>&#39;<br>
<b>Subject:</b>=A0Re: [mpls] seeking consensus on making draft-ietf-mpls-tp=
-te-mib read- only</span><span style=3D"font-size:10.0pt;font-family:&quot;=
Malgun Gothic&quot;,&quot;sans-serif&quot;"><u></u><u></u></span></p></div>
</div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span style=3D"=
font-size:10.0pt;font-family:&quot;Malgun Gothic&quot;,&quot;sans-serif&quo=
t;">=A0<u></u><u></u></span></p><div><p class=3D"MsoNormal" style=3D"word-b=
reak:break-all">
<span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Courier Ne=
w&quot;">No/oppose to make as Read-only mib.</span><span style=3D"font-size=
:10.0pt;font-family:&quot;Courier New&quot;"><u></u><u></u></span></p></div=
><div>
<p class=3D"MsoNormal" style=3D"word-break:break-all"><span lang=3D"EN-US" =
style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">In our produ=
cts we extensively use R/W object of TE mib. We also have NMS/EMS that use =
TE read-write Objects</span><span style=3D"font-size:10.0pt;font-family:&qu=
ot;Courier New&quot;"><u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span lang=
=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">=
=A0</span><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quo=
t;"><u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span lang=
=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">B=
est Regards</span><span style=3D"font-size:10.0pt;font-family:&quot;Courier=
 New&quot;"><u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span lang=
=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">G=
wun</span><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quo=
t;"><u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span lang=
=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">=
=A0</span><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quo=
t;"><u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span lang=
=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">-=
----Original Message-----</span><span style=3D"font-size:10.0pt;font-family=
:&quot;Courier New&quot;"><u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span lang=
=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">F=
rom: mpls [<a href=3D"mailto:mpls-bounces@ietf.org" target=3D"_blank"><span=
 style=3D"color:#954f72">mailto:mpls-bounces@ietf.org</span></a>] On Behalf=
 Of Loa Andersson</span><span style=3D"font-size:10.0pt;font-family:&quot;C=
ourier New&quot;"><u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span lang=
=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">S=
ent: Monday, February 03, 2014 10:55 PM</span><span style=3D"font-size:10.0=
pt;font-family:&quot;Courier New&quot;"><u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span lang=
=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">T=
o:=A0<a href=3D"mailto:mpls@ietf.org" target=3D"_blank"><span style=3D"colo=
r:#954f72">mpls@ietf.org</span></a></span><span style=3D"font-size:10.0pt;f=
ont-family:&quot;Courier New&quot;"><u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span lang=
=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">C=
c:=A0<a href=3D"mailto:mpls-chairs@tools.ietf.org" target=3D"_blank"><span =
style=3D"color:#954f72">mpls-chairs@tools.ietf.org</span></a>;=A0<a href=3D=
"mailto:draft-ietf-mpls-tp-te-mib@tools.ietf.org" target=3D"_blank"><span s=
tyle=3D"color:#954f72">draft-ietf-mpls-tp-te-mib@tools.ietf.org</span></a><=
/span><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">=
<u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span lang=
=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">S=
ubject: [mpls] seeking consensus on making draft-ietf-mpls-tp-te-mib read- =
only</span><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&qu=
ot;"><u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span lang=
=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">=
=A0</span><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quo=
t;"><u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span lang=
=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">W=
orking Group,</span><span style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;"><u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span lang=
=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">=
=A0</span><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quo=
t;"><u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span lang=
=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">W=
e have just recalled draft-ietf-mpls-tp-te-mib from the IESG to the working=
 group for more work. We have a series of comments that are mostly for clar=
ification. However the main reason for recalling the document is that there=
 is one point where we need to confirm working group consensus.</span><span=
 style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;"><u></u><u><=
/u></span></p>
</div><div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span lang=
=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">=
=A0</span><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quo=
t;"><u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span lang=
=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">T=
he IETF, the working group and the MIB Doctors are today very reluctant to =
produce read-write MIB modules. The current draft is read-write for a few o=
bjects, this is based on a consensus call for an earlier discussion, howeve=
r the consensus call was not clear. It can be taken to mean both that we wa=
nt to go with read-write objects and that we want to see read-only. Is it c=
lear that it has been interpreted differently by different individuals.</sp=
an><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;"><u>=
</u><u></u></span></p>
</div><div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span lang=
=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">=
=A0</span><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quo=
t;"><u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span lang=
=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">T=
he authors and chairs have discussed the issue and we have a rough consensu=
s that we want the MIB module(s) to be read-only.</span><span style=3D"font=
-size:10.0pt;font-family:&quot;Courier New&quot;"><u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span lang=
=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">=
=A0</span><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quo=
t;"><u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span lang=
=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">W=
e therefore are asking the working group if this is OK for the MIB</span><s=
pan style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;"><u></u><=
u></u></span></p>
</div><div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span lang=
=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">m=
odule(s) in the current document. Please indicate Support or Oppose for thi=
s MIB (draft-ietf-mpls-tp-te-mib) to be read-only.</span><span style=3D"fon=
t-size:10.0pt;font-family:&quot;Courier New&quot;"><u></u><u></u></span></p=
>
</div><div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span lang=
=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">=
=A0</span><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quo=
t;"><u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span lang=
=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">P=
lease send your comments to the working group mailing list before February =
18, 2014.</span><span style=3D"font-size:10.0pt;font-family:&quot;Courier N=
ew&quot;"><u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span lang=
=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">=
=A0</span><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quo=
t;"><u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span lang=
=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">L=
oa</span><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot=
;"><u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span lang=
=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">f=
or the MPLS wg chairs</span><span style=3D"font-size:10.0pt;font-family:&qu=
ot;Courier New&quot;"><u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span lang=
=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">-=
-</span><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;=
"><u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span lang=
=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">=
=A0</span><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quo=
t;"><u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span lang=
=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">=
=A0</span><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quo=
t;"><u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span lang=
=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">L=
oa Andersson=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0 email:=A0<a href=3D"mailto:loa@mail01.huawei.com" target=3D"_blank">=
<span style=3D"color:#954f72">loa@mail01.huawei.com</span></a></span><span =
style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;"><u></u><u></=
u></span></p>
</div><div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span lang=
=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">S=
enior MPLS Expert=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0<a href=3D"mailto:loa@pi.nu" target=3D"_blank"><span s=
tyle=3D"color:#954f72">loa@pi.nu</span></a></span><span style=3D"font-size:=
10.0pt;font-family:&quot;Courier New&quot;"><u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span lang=
=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">H=
uawei Technologies (consultant)=A0=A0=A0=A0 phone: +46 739 81 21 64</span><=
span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;"><u></u>=
<u></u></span></p>
</div><div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span lang=
=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">_=
______________________________________________</span><span style=3D"font-si=
ze:10.0pt;font-family:&quot;Courier New&quot;"><u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span lang=
=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">m=
pls mailing list</span><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;"><u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span lang=
=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;"><=
a href=3D"mailto:mpls@ietf.org" target=3D"_blank"><span style=3D"color:#954=
f72">mpls@ietf.org</span></a></span><span style=3D"font-size:10.0pt;font-fa=
mily:&quot;Courier New&quot;"><u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span lang=
=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;"><=
a href=3D"https://www.ietf.org/mailman/listinfo/mpls" target=3D"_blank"><sp=
an style=3D"color:#954f72">https://www.ietf.org/mailman/listinfo/mpls</span=
></a></span><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&q=
uot;"><u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span lang=
=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">_=
______________________________________________</span><span style=3D"font-si=
ze:10.0pt;font-family:&quot;Courier New&quot;"><u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span lang=
=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">m=
pls mailing list</span><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;"><u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span lang=
=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;"><=
a href=3D"mailto:mpls@ietf.org" target=3D"_blank"><span style=3D"color:#954=
f72">mpls@ietf.org</span></a></span><span style=3D"font-size:10.0pt;font-fa=
mily:&quot;Courier New&quot;"><u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span lang=
=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;"><=
a href=3D"https://www.ietf.org/mailman/listinfo/mpls" target=3D"_blank"><sp=
an style=3D"color:#954f72">https://www.ietf.org/mailman/listinfo/mpls</span=
></a></span><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&q=
uot;"><u></u><u></u></span></p>
</div><p class=3D"MsoNormal" style=3D"text-align:justify;word-break:break-a=
ll"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Malgun=
 Gothic&quot;,&quot;sans-serif&quot;">=A0</span><span style=3D"font-size:10=
.0pt;font-family:&quot;Malgun Gothic&quot;,&quot;sans-serif&quot;"><u></u><=
u></u></span></p>
</div></div><p class=3D"MsoNormal"><span style=3D"font-size:13.5pt;font-fam=
ily:&quot;Helvetica&quot;,&quot;sans-serif&quot;">_________________________=
______________________<br>MIB-DOCTORS mailing list<br><a href=3D"mailto:MIB=
-DOCTORS@ietf.org" target=3D"_blank"><span style=3D"color:#954f72">MIB-DOCT=
ORS@ietf.org</span></a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/mib-doctors" target=3D"_bl=
ank"><span style=3D"color:#954f72">https://www.ietf.org/mailman/listinfo/mi=
b-doctors</span></a><u></u><u></u></span></p></div></div><p class=3D"MsoNor=
mal">
<u></u>=A0<u></u></p></div></div><p class=3D"MsoNormal" style=3D"margin-bot=
tom:12.0pt"><br>_______________________________________________<br>MIB-DOCT=
ORS mailing list<br><a href=3D"mailto:MIB-DOCTORS@ietf.org" target=3D"_blan=
k">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><u></u><u></u></p=
></div><p class=3D"MsoNormal"><u></u>=A0<u></u></p></div></div></div></bloc=
kquote>
</div><br></div></div>

--001a11c2a9caef689d04f1fc79ec--


From bclaise@cisco.com  Mon Feb 10 18:27:14 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 79BC41A0746 for <mib-doctors@ietfa.amsl.com>; Mon, 10 Feb 2014 18:27:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.448
X-Spam-Level: 
X-Spam-Status: No, score=-14.448 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, J_CHICKENPOX_26=0.6, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.548, 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 9lPTyquJ8zG7 for <mib-doctors@ietfa.amsl.com>; Mon, 10 Feb 2014 18:27:06 -0800 (PST)
Received: from mtv-iport-4.cisco.com (mtv-iport-4.cisco.com [173.36.130.15]) by ietfa.amsl.com (Postfix) with ESMTP id 271101A073F for <mib-doctors@ietf.org>; Mon, 10 Feb 2014 18:27:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=39954; q=dns/txt; s=iport; t=1392085626; x=1393295226; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to; bh=XHTOEbSZuTbk5M07EcAJs9Ej1hP/Ft+aHTWhWkIVYWo=; b=B9iTBQy6OcyQ2X7b8mxgVDMKYHR5M2S3XiW+Zc0Xf04wlCA5Ivee6+nF OVYvnDN+KvobXLO4ad3aFg6ZQtZW3vDds8+8zI+kiKcYcNE6pjj/oZsdo I4RcPePn0Rwm1Y7VMDzhc/S4Us01cS3H8kGRqVD/PoPfbv/+K0dyVqyMR U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AkwJAA2K+VKrRDoH/2dsb2JhbABZgkhEOIk1rmOHHoEQFnSCJQEBAQMBAQEBGk4DCgEFBwICCw4DBAEBChYBAQYHCQMCAQIBCQwfCQgGAQwBBQIBAYd5Bw7JcxMEBI4KEQEkLAYBBoQyBIlIijeEK4ZHi1mDThuBNQ
X-IronPort-AV: E=Sophos;i="4.95,822,1384300800";  d="scan'208,217";a="105374165"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by mtv-iport-4.cisco.com with ESMTP; 11 Feb 2014 02:27:05 +0000
Received: from [10.154.208.79] ([10.154.208.79]) by mtv-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id s1B2R4uI012676; Tue, 11 Feb 2014 02:27:04 GMT
Message-ID: <52F98A78.8040503@cisco.com>
Date: Mon, 10 Feb 2014 18:27:04 -0800
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: David Harrington <ietfdbh@comcast.net>, adrian@olddog.co.uk
References: <05c501cf21ad$80d97ef0$828c7cd0$@olddog.co.uk> <7D263081-6D84-4AA2-B0CB-FA74793BD135@comcast.net>
In-Reply-To: <7D263081-6D84-4AA2-B0CB-FA74793BD135@comcast.net>
Content-Type: multipart/alternative; boundary="------------050102000705050508090103"
Cc: mib-doctors@ietf.org
Subject: Re: [MIB-DOCTORS] Read-only MIB modules
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, 11 Feb 2014 02:27:14 -0000

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

Hi,

What this statement tries to achieve is
1. Set the direction for new MIB modules development
2. Still leave the door open (SNMP MIB modules modifying persistent 
configuration state should only be produced by working groups in cases 
of clear utility and overwhelming consensus to use SNMP write operations 
for configuration.)

On a recent read-write example, I asked an author:
- can you tell which OS/platform are/will be implementing this 
read-write MIB module?
- can you tell which NMS will be using the read-write capabilities?
The answer were eloquent.

Regards, Benoit

> Hi,
>
> I object to this statement. (Should I say "strongly" object, to show I 
> mean business?
>
> There are many RW objects that can "adjust" a network configuration 
> assuming SET is supported by the agent involved.
> The NMS I used to work on, which helped determine and correct root 
> cause for fault and performance problems, adjusted networks using 
> writable MIB modules often.
> To tell WGs they should not develop RW MIB modules I think is wrong.
>
> I also have a concern with recommending Netconf/YANG at this point in 
> time.
> If we looked up the top ten router vendors using something like 
> Gartner reports, how many of them really support configuration using 
> Netconf with YANG in shipping products?
> Ditto, the top ten switch vendors?
> How many of them can be fully configured using YANG modules (not 
> homegrown alternatives, but modules - standard or proprietary - 
> written using the standards-compliant YANG language)?
> I don't know the answer to that question, but would like to see some 
> proof that YANG is at least as widely supported in currently shipping 
> products as RW MIB objects.
> I think Netconf/YANG should compete in an open market with RW MIB 
> modules, not try to stack the deck in their favor by "strongly 
> discouraging" RW MIB standards.
>
> I have had discussions with vendors who are leaders in their 
> particular networking niche, and they have told me they would not 
> consider Netconf/YANG, because it has not been around long enough and 
> been widely-enough deployed to prove stable for their production 
> networks (whereas SNMP has enough track record to be known to be stable).
> So I'm a bit concerned about telling WGs they should develop YANG 
> modules rather than MIB modules.
> And the current discussions of whether YANG 1.1 or 2.0 is needed to 
> fix some problems with YANG 1.0, and it may not be backwards 
> compatible, make me question the stability of YANG.
>
> Don't get me wrong. I support Netconf/YANG going forward, but I think 
> it is important to provide advice that 
> non-MIB-Doctors/non-YANG-experts can interpret reasonably.
> Any such statement should make a clear distinction between 
> "configuration" - the complete configuration of a device by Netconf - 
> versus RW objects in a MIB - which can be used by SNMP to adjust 
> network parameters/configuration.
> Telling people not to develop RW MIBs is throwing the baby out with 
> the bathwater.
> We should NOT recommend against RW MIBs, because these can be used for 
> more than (full device) configuration.
> That point is far from clear in the currently proposed statement.
> Maybe the statement should be that, if a vendor wants to replace their 
> CLI, they should replace it with Netconf/YANG, and not with SNMP/RW-MIBs.
> That's probably a closer approximation  of Netconf/YANG's 
> applicability versus RW MIBs.
>
> In the past we have allowed implementations to make the conformance 
> choice between supporting a MIB as RW, or implementing read-only.
> If we advise WGs to not develop module with RW objects, then we take 
> the choice away from the vendors.
> I thick that would be a mistake.
>
> In  addition, it is pointed out later in this thread that other SDOs 
> use RW MIBs.
> Well, those MIBs produced by other SDOs (and for that matter, vendors) 
> might require some support for specific RW objects in IETF MIB modules.
> Therefore, I think it would be providing bad advice to say that IETF 
> WGs should not produce MIB  modules with RW objects in them.
>
> If Netconf/YANG becomes widely deployed, then NMS implementations and 
> operators can choose whether to use YANG or SNMP (or their CLI) to 
> adjust network configurations.
> THat should not be a decision we make in the IETF, effectively forcing 
> WGs to not develop MIBs with writable objects.
>
> Providing RW objects in MIB modules lets implementers and operators 
> make the appropriate choice for their environments. (See RFC 3365 for 
> similar thinking vis-a-vis security.)
>
> dbh
>
> On Feb 4, 2014, at 8:32 AM, Adrian Farrel <adrian@olddog.co.uk 
> <mailto:adrian@olddog.co.uk>> wrote:
>
>> Hi,
>> The MPLS working group is testing the water to see whether one of its 
>> MIB modules should be "reduced" to read-only. This is the document 
>> that triggered my recent questions that led on to the draft advice 
>> you are working on. The WG took the document back to make this decision.
>> You'll note below that we immediately have an implementation claim 
>> (not for this doc, but for the modules it extends).
>> An interesting situation, I think.
>> A
>> *From:*mpls [mailto:mpls-bounces@ietf.org 
>> <mailto:bounces@ietf.org>]*On Behalf Of*GyeRok Gwun (???)
>> *Sent:*04 February 2014 09:57
>> *To:*'mpls@ietf.org <mailto:mpls@ietf.org>'
>> *Cc:*'mpls-chairs@tools.ietf.org 
>> <mailto:mpls-chairs@tools.ietf.org>'; 
>> 'draft-ietf-mpls-tp-te-mib@tools.ietf.org 
>> <mailto:draft-ietf-mpls-tp-te-mib@tools.ietf.org>'
>> *Subject:*Re: [mpls] seeking consensus on making 
>> draft-ietf-mpls-tp-te-mib read- only
>> No/oppose to make as Read-only mib.
>> In our products we extensively use R/W object of TE mib. We also have 
>> NMS/EMS that use TE read-write Objects
>> Best Regards
>> Gwun
>> -----Original Message-----
>> From: mpls [mailto:mpls-bounces@ietf.org] On Behalf Of Loa Andersson
>> Sent: Monday, February 03, 2014 10:55 PM
>> To:mpls@ietf.org <mailto:mpls@ietf.org>
>> Cc:mpls-chairs@tools.ietf.org 
>> <mailto:mpls-chairs@tools.ietf.org>;draft-ietf-mpls-tp-te-mib@tools.ietf.org 
>> <mailto:draft-ietf-mpls-tp-te-mib@tools.ietf.org>
>> Subject: [mpls] seeking consensus on making draft-ietf-mpls-tp-te-mib 
>> read- only
>> Working Group,
>> We have just recalled draft-ietf-mpls-tp-te-mib from the IESG to the 
>> working group for more work. We have a series of comments that are 
>> mostly for clarification. However the main reason for recalling the 
>> document is that there is one point where we need to confirm working 
>> group consensus.
>> The IETF, the working group and the MIB Doctors are today very 
>> reluctant to produce read-write MIB modules. The current draft is 
>> read-write for a few objects, this is based on a consensus call for 
>> an earlier discussion, however the consensus call was not clear. It 
>> can be taken to mean both that we want to go with read-write objects 
>> and that we want to see read-only. Is it clear that it has been 
>> interpreted differently by different individuals.
>> The authors and chairs have discussed the issue and we have a rough 
>> consensus that we want the MIB module(s) to be read-only.
>> We therefore are asking the working group if this is OK for the MIB
>> module(s) in the current document. Please indicate Support or Oppose 
>> for this MIB (draft-ietf-mpls-tp-te-mib) to be read-only.
>> Please send your comments to the working group mailing list before 
>> February 18, 2014.
>> Loa
>> for the MPLS wg chairs
>> --
>> Loa Andersson                        email:loa@mail01.huawei.com 
>> <mailto:loa@mail01.huawei.com>
>> Senior MPLS Expert loa@pi.nu <mailto:loa@pi.nu>
>> Huawei Technologies (consultant)     phone: +46 739 81 21 64
>> _______________________________________________
>> mpls mailing list
>> mpls@ietf.org <mailto:mpls@ietf.org>
>> https://www.ietf.org/mailman/listinfo/mpls
>> _______________________________________________
>> mpls mailing list
>> mpls@ietf.org <mailto:mpls@ietf.org>
>> https://www.ietf.org/mailman/listinfo/mpls
>> _______________________________________________
>> MIB-DOCTORS mailing list
>> MIB-DOCTORS@ietf.org <mailto: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


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

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">Hi,<br>
      <br>
      What this statement tries to achieve is<br>
      1. Set the direction for new MIB modules development<br>
      2. Still leave the door open (SNMP MIB modules modifying
      persistent configuration state should only be produced by working
      groups in cases of clear utility and overwhelming consensus to use
      SNMP write operations for configuration.)<br>
      <br>
      On a recent read-write example, I asked an author:<br>
      - can you tell which OS/platform are/will be implementing this
      read-write MIB module?
      <br>
      - can you tell which NMS will be using the read-write
      capabilities? <br>
      The answer were eloquent.<br>
      <br>
      Regards, Benoit<br>
      <br>
    </div>
    <blockquote
      cite="mid:7D263081-6D84-4AA2-B0CB-FA74793BD135@comcast.net"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=ISO-8859-1">
      <base href="x-msg://3655/">Hi,
      <div><br>
      </div>
      <div>I object to this statement. (Should I say "strongly" object,
        to show I mean business?</div>
      <div><br>
      </div>
      <div>There are many RW objects that can "adjust" a network
        configuration assuming SET is supported by the agent involved.</div>
      <div>The NMS I used to work on, which helped determine and correct
        root cause for fault and performance problems, adjusted networks
        using writable MIB modules often.</div>
      <div>To tell WGs they should not develop RW MIB modules I think is
        wrong.</div>
      <div><br>
      </div>
      <div>I also have a concern with recommending Netconf/YANG at this
        point in time.</div>
      <div>If we looked up the top ten router vendors using something
        like Gartner reports, how many of them really support
        configuration using Netconf with YANG in shipping products?</div>
      <div>Ditto, the top ten switch vendors?</div>
      <div>How many of them can be fully configured using YANG modules
        (not homegrown alternatives, but modules - standard or
        proprietary - written using the standards-compliant YANG
        language)?</div>
      <div>I don't know the answer to that question, but would like to
        see some proof that YANG is at least as widely supported in
        currently shipping products as RW MIB objects.</div>
      <div>I think Netconf/YANG should compete in an open market with RW
        MIB modules, not try to stack the deck in their favor by
        "strongly discouraging" RW MIB standards.</div>
      <div><br>
      </div>
      <div>I have had discussions with vendors who are leaders in their
        particular networking niche, and they have told me they would
        not consider Netconf/YANG, because it has not been around long
        enough and been widely-enough deployed to prove stable for their
        production networks (whereas SNMP has enough track record to be
        known to be stable).</div>
      <div>So I'm a bit concerned about telling WGs they should develop
        YANG modules rather than MIB modules.</div>
      <div>And the current discussions of whether YANG 1.1 or 2.0 is
        needed to fix some problems with YANG 1.0, and it may not be
        backwards compatible, make me question the stability of YANG.</div>
      <div><br>
      </div>
      <div>Don't get me wrong. I support Netconf/YANG going forward, but
        I think it is important to provide advice that
        non-MIB-Doctors/non-YANG-experts can interpret reasonably.</div>
      <div>Any such statement should make a clear distinction between
        "configuration" - the complete configuration of a device by
        Netconf - versus RW objects in a MIB - which can be used by SNMP
        to adjust network parameters/configuration.</div>
      <div>Telling people not to develop RW MIBs is throwing the baby
        out with the bathwater.</div>
      <div>We should NOT recommend against RW MIBs, because these can be
        used for more than (full device) configuration.</div>
      <div>That point is far from clear in the currently proposed
        statement.</div>
      <div>Maybe the statement should be that, if a vendor wants to
        replace their CLI, they should replace it with Netconf/YANG, and
        not with SNMP/RW-MIBs.&nbsp;</div>
      <div>That's probably a closer approximation &nbsp;of Netconf/YANG's
        applicability versus RW MIBs.&nbsp;</div>
      <div><br>
      </div>
      <div>In the past we have allowed implementations to make the
        conformance choice between supporting a MIB as RW, or
        implementing read-only.</div>
      <div>If we advise WGs to not develop module with RW objects, then
        we take the choice away from the vendors.</div>
      <div>I thick that would be a mistake.</div>
      <div><br>
      </div>
      <div>In &nbsp;addition, it is pointed out later in this thread that
        other SDOs use RW MIBs.&nbsp;</div>
      <div>Well, those MIBs produced by other SDOs (and for that matter,
        vendors) might require some support for specific RW objects in
        IETF MIB modules.</div>
      <div>Therefore, I think it would be providing bad advice to say
        that IETF WGs should not produce MIB &nbsp;modules with RW objects in
        them.</div>
      <div><br>
      </div>
      <div>If Netconf/YANG becomes widely deployed, then NMS
        implementations and operators can choose whether to use YANG or
        SNMP (or their CLI) to adjust network configurations.</div>
      <div>THat should not be a decision we make in the IETF,
        effectively forcing WGs to not develop MIBs with writable
        objects.</div>
      <div><br>
      </div>
      <div>Providing RW objects in MIB modules lets implementers and
        operators make the appropriate choice for their environments.
        (See RFC 3365 for similar thinking vis-a-vis security.)</div>
      <div><br>
      </div>
      <div>dbh</div>
      <div><br>
        <div>
          <div>On Feb 4, 2014, at 8:32 AM, Adrian Farrel &lt;<a
              moz-do-not-send="true" href="mailto:adrian@olddog.co.uk">adrian@olddog.co.uk</a>&gt;
            wrote:</div>
          <br class="Apple-interchange-newline">
          <blockquote type="cite">
            <div link="#0563C1" vlink="#954F72" style="font-family:
              Helvetica; font-size: medium; font-style: normal;
              font-variant: normal; font-weight: normal; letter-spacing:
              normal; line-height: normal; orphans: 2; text-align:
              -webkit-auto; text-indent: 0px; text-transform: none;
              white-space: normal; widows: 2; word-spacing: 0px;
              -webkit-text-size-adjust: auto; -webkit-text-stroke-width:
              0px; " lang="EN-GB">
              <div class="WordSection1" style="page: WordSection1; ">
                <div style="margin: 0cm 0cm 0.0001pt; text-align:
                  justify; word-break: normal; font-size: 10pt;
                  font-family: 'Malgun Gothic', sans-serif; "><span
                    style="font-size: 11pt; font-family: Calibri,
                    sans-serif; color: rgb(31, 73, 125); ">Hi,<o:p></o:p></span></div>
                <div style="margin: 0cm 0cm 0.0001pt; text-align:
                  justify; word-break: normal; font-size: 10pt;
                  font-family: 'Malgun Gothic', sans-serif; "><span
                    style="font-size: 11pt; font-family: Calibri,
                    sans-serif; color: rgb(31, 73, 125); ">&nbsp;</span></div>
                <div style="margin: 0cm 0cm 0.0001pt; text-align:
                  justify; word-break: normal; font-size: 10pt;
                  font-family: 'Malgun Gothic', sans-serif; "><span
                    style="font-size: 11pt; font-family: Calibri,
                    sans-serif; color: rgb(31, 73, 125); ">The MPLS
                    working group is testing the water to see whether
                    one of its MIB modules should be "reduced" to
                    read-only. This is the document that triggered my
                    recent questions that led on to the draft advice you
                    are working on. The WG took the document back to
                    make this decision.<o:p></o:p></span></div>
                <div style="margin: 0cm 0cm 0.0001pt; text-align:
                  justify; word-break: normal; font-size: 10pt;
                  font-family: 'Malgun Gothic', sans-serif; "><span
                    style="font-size: 11pt; font-family: Calibri,
                    sans-serif; color: rgb(31, 73, 125); ">&nbsp;</span></div>
                <div style="margin: 0cm 0cm 0.0001pt; text-align:
                  justify; word-break: normal; font-size: 10pt;
                  font-family: 'Malgun Gothic', sans-serif; "><span
                    style="font-size: 11pt; font-family: Calibri,
                    sans-serif; color: rgb(31, 73, 125); ">You'll note
                    below that we immediately have an implementation
                    claim (not for this doc, but for the modules it
                    extends).<o:p></o:p></span></div>
                <div style="margin: 0cm 0cm 0.0001pt; text-align:
                  justify; word-break: normal; font-size: 10pt;
                  font-family: 'Malgun Gothic', sans-serif; "><span
                    style="font-size: 11pt; font-family: Calibri,
                    sans-serif; color: rgb(31, 73, 125); ">&nbsp;</span></div>
                <div style="margin: 0cm 0cm 0.0001pt; text-align:
                  justify; word-break: normal; font-size: 10pt;
                  font-family: 'Malgun Gothic', sans-serif; "><span
                    style="font-size: 11pt; font-family: Calibri,
                    sans-serif; color: rgb(31, 73, 125); ">An
                    interesting situation, I think.<o:p></o:p></span></div>
                <div style="margin: 0cm 0cm 0.0001pt; text-align:
                  justify; word-break: normal; font-size: 10pt;
                  font-family: 'Malgun Gothic', sans-serif; "><span
                    style="font-size: 11pt; font-family: Calibri,
                    sans-serif; color: rgb(31, 73, 125); ">&nbsp;</span></div>
                <div style="margin: 0cm 0cm 0.0001pt; text-align:
                  justify; word-break: normal; font-size: 10pt;
                  font-family: 'Malgun Gothic', sans-serif; "><span
                    style="font-size: 11pt; font-family: Calibri,
                    sans-serif; color: rgb(31, 73, 125); ">A<o:p></o:p></span></div>
                <div style="margin: 0cm 0cm 0.0001pt; text-align:
                  justify; word-break: normal; font-size: 10pt;
                  font-family: 'Malgun Gothic', sans-serif; "><span
                    style="font-size: 11pt; font-family: Calibri,
                    sans-serif; color: rgb(31, 73, 125); ">&nbsp;</span></div>
                <div style="border-style: none none none solid;
                  border-left-width: 1.5pt; border-left-color: blue;
                  padding: 0cm 0cm 0cm 4pt; ">
                  <div>
                    <div style="border-style: solid none none;
                      border-top-width: 1pt; border-top-color: rgb(181,
                      196, 223); padding: 3pt 0cm 0cm; ">
                      <div style="margin: 0cm 0cm 0.0001pt; text-align:
                        left; word-break: normal; font-size: 10pt;
                        font-family: 'Malgun Gothic', sans-serif; "><b><span
                            style="font-family: Tahoma, sans-serif; "
                            lang="EN-US">From:</span></b><span
                          style="font-family: Tahoma, sans-serif; "
                          lang="EN-US"><span
                            class="Apple-converted-space">&nbsp;</span>mpls
                          [<a class="moz-txt-link-freetext" href="mailto:mpls">mailto:mpls</a>-<a moz-do-not-send="true"
                            href="mailto:bounces@ietf.org" style="color:
                            rgb(149, 79, 114); text-decoration:
                            underline; ">bounces@ietf.org</a>]<span
                            class="Apple-converted-space">&nbsp;</span><b>On
                            Behalf Of<span class="Apple-converted-space">&nbsp;</span></b>GyeRok
                          Gwun (???)<br>
                          <b>Sent:</b><span
                            class="Apple-converted-space">&nbsp;</span>04
                          February 2014 09:57<br>
                          <b>To:</b><span class="Apple-converted-space">&nbsp;</span>'<a
                            moz-do-not-send="true"
                            href="mailto:mpls@ietf.org" style="color:
                            rgb(149, 79, 114); text-decoration:
                            underline; ">mpls@ietf.org</a>'<br>
                          <b>Cc:</b><span class="Apple-converted-space">&nbsp;</span>'<a
                            moz-do-not-send="true"
                            href="mailto:mpls-chairs@tools.ietf.org"
                            style="color: rgb(149, 79, 114);
                            text-decoration: underline; ">mpls-chairs@tools.ietf.org</a>';
                          '<a moz-do-not-send="true"
                            href="mailto:draft-ietf-mpls-tp-te-mib@tools.ietf.org"
                            style="color: rgb(149, 79, 114);
                            text-decoration: underline; ">draft-ietf-mpls-tp-te-mib@tools.ietf.org</a>'<br>
                          <b>Subject:</b><span
                            class="Apple-converted-space">&nbsp;</span>Re:
                          [mpls] seeking consensus on making
                          draft-ietf-mpls-tp-te-mib read- only<o:p></o:p></span></div>
                    </div>
                  </div>
                  <div style="margin: 0cm 0cm 0.0001pt; text-align:
                    left; word-break: break-all; font-size: 10pt;
                    font-family: 'Malgun Gothic', sans-serif; "><o:p>&nbsp;</o:p></div>
                  <div style="margin: 0cm 0cm 0.0001pt; word-break:
                    break-all; font-size: 10pt; font-family: 'Courier
                    New', serif; "><span lang="EN-US">No/oppose to make
                      as Read-only mib.<o:p></o:p></span></div>
                  <div style="margin: 0cm 0cm 0.0001pt; word-break:
                    break-all; font-size: 10pt; font-family: 'Courier
                    New', serif; "><span lang="EN-US">In our products we
                      extensively use R/W object of TE mib. We also have
                      NMS/EMS that use TE read-write Objects<o:p></o:p></span></div>
                  <div style="margin: 0cm 0cm 0.0001pt; word-break:
                    break-all; font-size: 10pt; font-family: 'Courier
                    New', serif; "><span lang="EN-US">&nbsp;</span></div>
                  <div style="margin: 0cm 0cm 0.0001pt; word-break:
                    break-all; font-size: 10pt; font-family: 'Courier
                    New', serif; "><span lang="EN-US">Best Regards<o:p></o:p></span></div>
                  <div style="margin: 0cm 0cm 0.0001pt; word-break:
                    break-all; font-size: 10pt; font-family: 'Courier
                    New', serif; "><span lang="EN-US">Gwun<o:p></o:p></span></div>
                  <div style="margin: 0cm 0cm 0.0001pt; word-break:
                    break-all; font-size: 10pt; font-family: 'Courier
                    New', serif; "><span lang="EN-US">&nbsp;</span></div>
                  <div style="margin: 0cm 0cm 0.0001pt; word-break:
                    break-all; font-size: 10pt; font-family: 'Courier
                    New', serif; "><span lang="EN-US">-----Original
                      Message-----<o:p></o:p></span></div>
                  <div style="margin: 0cm 0cm 0.0001pt; word-break:
                    break-all; font-size: 10pt; font-family: 'Courier
                    New', serif; "><span lang="EN-US">From: mpls [<a
                        moz-do-not-send="true"
                        href="mailto:mpls-bounces@ietf.org"
                        style="color: rgb(149, 79, 114);
                        text-decoration: underline; ">mailto:mpls-bounces@ietf.org</a>]
                      On Behalf Of Loa Andersson<o:p></o:p></span></div>
                  <div style="margin: 0cm 0cm 0.0001pt; word-break:
                    break-all; font-size: 10pt; font-family: 'Courier
                    New', serif; "><span lang="EN-US">Sent: Monday,
                      February 03, 2014 10:55 PM<o:p></o:p></span></div>
                  <div style="margin: 0cm 0cm 0.0001pt; word-break:
                    break-all; font-size: 10pt; font-family: 'Courier
                    New', serif; "><span lang="EN-US">To:<span
                        class="Apple-converted-space">&nbsp;</span><a
                        moz-do-not-send="true"
                        href="mailto:mpls@ietf.org" style="color:
                        rgb(149, 79, 114); text-decoration: underline; ">mpls@ietf.org</a><o:p></o:p></span></div>
                  <div style="margin: 0cm 0cm 0.0001pt; word-break:
                    break-all; font-size: 10pt; font-family: 'Courier
                    New', serif; "><span lang="EN-US">Cc:<span
                        class="Apple-converted-space">&nbsp;</span><a
                        moz-do-not-send="true"
                        href="mailto:mpls-chairs@tools.ietf.org"
                        style="color: rgb(149, 79, 114);
                        text-decoration: underline; ">mpls-chairs@tools.ietf.org</a>;<span
                        class="Apple-converted-space">&nbsp;</span><a
                        moz-do-not-send="true"
                        href="mailto:draft-ietf-mpls-tp-te-mib@tools.ietf.org"
                        style="color: rgb(149, 79, 114);
                        text-decoration: underline; ">draft-ietf-mpls-tp-te-mib@tools.ietf.org</a><o:p></o:p></span></div>
                  <div style="margin: 0cm 0cm 0.0001pt; word-break:
                    break-all; font-size: 10pt; font-family: 'Courier
                    New', serif; "><span lang="EN-US">Subject: [mpls]
                      seeking consensus on making
                      draft-ietf-mpls-tp-te-mib read- only<o:p></o:p></span></div>
                  <div style="margin: 0cm 0cm 0.0001pt; word-break:
                    break-all; font-size: 10pt; font-family: 'Courier
                    New', serif; "><span lang="EN-US">&nbsp;</span></div>
                  <div style="margin: 0cm 0cm 0.0001pt; word-break:
                    break-all; font-size: 10pt; font-family: 'Courier
                    New', serif; "><span lang="EN-US">Working Group,<o:p></o:p></span></div>
                  <div style="margin: 0cm 0cm 0.0001pt; word-break:
                    break-all; font-size: 10pt; font-family: 'Courier
                    New', serif; "><span lang="EN-US">&nbsp;</span></div>
                  <div style="margin: 0cm 0cm 0.0001pt; word-break:
                    break-all; font-size: 10pt; font-family: 'Courier
                    New', serif; "><span lang="EN-US">We have just
                      recalled draft-ietf-mpls-tp-te-mib from the IESG
                      to the working group for more work. We have a
                      series of comments that are mostly for
                      clarification. However the main reason for
                      recalling the document is that there is one point
                      where we need to confirm working group consensus.<o:p></o:p></span></div>
                  <div style="margin: 0cm 0cm 0.0001pt; word-break:
                    break-all; font-size: 10pt; font-family: 'Courier
                    New', serif; "><span lang="EN-US">&nbsp;</span></div>
                  <div style="margin: 0cm 0cm 0.0001pt; word-break:
                    break-all; font-size: 10pt; font-family: 'Courier
                    New', serif; "><span lang="EN-US">The IETF, the
                      working group and the MIB Doctors are today very
                      reluctant to produce read-write MIB modules. The
                      current draft is read-write for a few objects,
                      this is based on a consensus call for an earlier
                      discussion, however the consensus call was not
                      clear. It can be taken to mean both that we want
                      to go with read-write objects and that we want to
                      see read-only. Is it clear that it has been
                      interpreted differently by different individuals.<o:p></o:p></span></div>
                  <div style="margin: 0cm 0cm 0.0001pt; word-break:
                    break-all; font-size: 10pt; font-family: 'Courier
                    New', serif; "><span lang="EN-US">&nbsp;</span></div>
                  <div style="margin: 0cm 0cm 0.0001pt; word-break:
                    break-all; font-size: 10pt; font-family: 'Courier
                    New', serif; "><span lang="EN-US">The authors and
                      chairs have discussed the issue and we have a
                      rough consensus that we want the MIB module(s) to
                      be read-only.<o:p></o:p></span></div>
                  <div style="margin: 0cm 0cm 0.0001pt; word-break:
                    break-all; font-size: 10pt; font-family: 'Courier
                    New', serif; "><span lang="EN-US">&nbsp;</span></div>
                  <div style="margin: 0cm 0cm 0.0001pt; word-break:
                    break-all; font-size: 10pt; font-family: 'Courier
                    New', serif; "><span lang="EN-US">We therefore are
                      asking the working group if this is OK for the MIB<o:p></o:p></span></div>
                  <div style="margin: 0cm 0cm 0.0001pt; word-break:
                    break-all; font-size: 10pt; font-family: 'Courier
                    New', serif; "><span lang="EN-US">module(s) in the
                      current document. Please indicate Support or
                      Oppose for this MIB (draft-ietf-mpls-tp-te-mib) to
                      be read-only.<o:p></o:p></span></div>
                  <div style="margin: 0cm 0cm 0.0001pt; word-break:
                    break-all; font-size: 10pt; font-family: 'Courier
                    New', serif; "><span lang="EN-US">&nbsp;</span></div>
                  <div style="margin: 0cm 0cm 0.0001pt; word-break:
                    break-all; font-size: 10pt; font-family: 'Courier
                    New', serif; "><span lang="EN-US">Please send your
                      comments to the working group mailing list before
                      February 18, 2014.<o:p></o:p></span></div>
                  <div style="margin: 0cm 0cm 0.0001pt; word-break:
                    break-all; font-size: 10pt; font-family: 'Courier
                    New', serif; "><span lang="EN-US">&nbsp;</span></div>
                  <div style="margin: 0cm 0cm 0.0001pt; word-break:
                    break-all; font-size: 10pt; font-family: 'Courier
                    New', serif; "><span lang="EN-US">Loa<o:p></o:p></span></div>
                  <div style="margin: 0cm 0cm 0.0001pt; word-break:
                    break-all; font-size: 10pt; font-family: 'Courier
                    New', serif; "><span lang="EN-US">for the MPLS wg
                      chairs<o:p></o:p></span></div>
                  <div style="margin: 0cm 0cm 0.0001pt; word-break:
                    break-all; font-size: 10pt; font-family: 'Courier
                    New', serif; "><span lang="EN-US">--<o:p></o:p></span></div>
                  <div style="margin: 0cm 0cm 0.0001pt; word-break:
                    break-all; font-size: 10pt; font-family: 'Courier
                    New', serif; "><span lang="EN-US">&nbsp;</span></div>
                  <div style="margin: 0cm 0cm 0.0001pt; word-break:
                    break-all; font-size: 10pt; font-family: 'Courier
                    New', serif; "><span lang="EN-US">&nbsp;</span></div>
                  <div style="margin: 0cm 0cm 0.0001pt; word-break:
                    break-all; font-size: 10pt; font-family: 'Courier
                    New', serif; "><span lang="EN-US">Loa
                      Andersson&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; email:<span
                        class="Apple-converted-space">&nbsp;</span><a
                        moz-do-not-send="true"
                        href="mailto:loa@mail01.huawei.com"
                        style="color: rgb(149, 79, 114);
                        text-decoration: underline; ">loa@mail01.huawei.com</a><o:p></o:p></span></div>
                  <div style="margin: 0cm 0cm 0.0001pt; word-break:
                    break-all; font-size: 10pt; font-family: 'Courier
                    New', serif; "><span lang="EN-US">Senior MPLS
                      Expert&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<span
                        class="Apple-converted-space">&nbsp;</span><a
                        moz-do-not-send="true" href="mailto:loa@pi.nu"
                        style="color: rgb(149, 79, 114);
                        text-decoration: underline; ">loa@pi.nu</a><o:p></o:p></span></div>
                  <div style="margin: 0cm 0cm 0.0001pt; word-break:
                    break-all; font-size: 10pt; font-family: 'Courier
                    New', serif; "><span lang="EN-US">Huawei
                      Technologies (consultant)&nbsp;&nbsp;&nbsp;&nbsp; phone: +46 739 81 21
                      64<o:p></o:p></span></div>
                  <div style="margin: 0cm 0cm 0.0001pt; word-break:
                    break-all; font-size: 10pt; font-family: 'Courier
                    New', serif; "><span lang="EN-US">_______________________________________________<o:p></o:p></span></div>
                  <div style="margin: 0cm 0cm 0.0001pt; word-break:
                    break-all; font-size: 10pt; font-family: 'Courier
                    New', serif; "><span lang="EN-US">mpls mailing list<o:p></o:p></span></div>
                  <div style="margin: 0cm 0cm 0.0001pt; word-break:
                    break-all; font-size: 10pt; font-family: 'Courier
                    New', serif; "><span lang="EN-US"><a
                        moz-do-not-send="true"
                        href="mailto:mpls@ietf.org" style="color:
                        rgb(149, 79, 114); text-decoration: underline; ">mpls@ietf.org</a><o:p></o:p></span></div>
                  <div style="margin: 0cm 0cm 0.0001pt; word-break:
                    break-all; font-size: 10pt; font-family: 'Courier
                    New', serif; "><span lang="EN-US"><a
                        moz-do-not-send="true"
                        href="https://www.ietf.org/mailman/listinfo/mpls"
                        style="color: rgb(149, 79, 114);
                        text-decoration: underline; ">https://www.ietf.org/mailman/listinfo/mpls</a><o:p></o:p></span></div>
                  <div style="margin: 0cm 0cm 0.0001pt; word-break:
                    break-all; font-size: 10pt; font-family: 'Courier
                    New', serif; "><span lang="EN-US">_______________________________________________<o:p></o:p></span></div>
                  <div style="margin: 0cm 0cm 0.0001pt; word-break:
                    break-all; font-size: 10pt; font-family: 'Courier
                    New', serif; "><span lang="EN-US">mpls mailing list<o:p></o:p></span></div>
                  <div style="margin: 0cm 0cm 0.0001pt; word-break:
                    break-all; font-size: 10pt; font-family: 'Courier
                    New', serif; "><span lang="EN-US"><a
                        moz-do-not-send="true"
                        href="mailto:mpls@ietf.org" style="color:
                        rgb(149, 79, 114); text-decoration: underline; ">mpls@ietf.org</a><o:p></o:p></span></div>
                  <div style="margin: 0cm 0cm 0.0001pt; word-break:
                    break-all; font-size: 10pt; font-family: 'Courier
                    New', serif; "><span lang="EN-US"><a
                        moz-do-not-send="true"
                        href="https://www.ietf.org/mailman/listinfo/mpls"
                        style="color: rgb(149, 79, 114);
                        text-decoration: underline; ">https://www.ietf.org/mailman/listinfo/mpls</a><o:p></o:p></span></div>
                  <div style="margin: 0cm 0cm 0.0001pt; text-align:
                    justify; word-break: break-all; font-size: 10pt;
                    font-family: 'Malgun Gothic', sans-serif; "><span
                      lang="EN-US">&nbsp;</span></div>
                </div>
              </div>
              _______________________________________________<br>
              MIB-DOCTORS mailing list<br>
              <a moz-do-not-send="true"
                href="mailto:MIB-DOCTORS@ietf.org" style="color:
                rgb(149, 79, 114); text-decoration: underline; ">MIB-DOCTORS@ietf.org</a><br>
              <a moz-do-not-send="true"
                href="https://www.ietf.org/mailman/listinfo/mib-doctors"
                style="color: rgb(149, 79, 114); text-decoration:
                underline; ">https://www.ietf.org/mailman/listinfo/mib-doctors</a><br>
            </div>
          </blockquote>
        </div>
        <br>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
MIB-DOCTORS mailing list
<a class="moz-txt-link-abbreviated" href="mailto:MIB-DOCTORS@ietf.org">MIB-DOCTORS@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/mib-doctors">https://www.ietf.org/mailman/listinfo/mib-doctors</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------050102000705050508090103--


From bclaise@cisco.com  Mon Feb 10 18:27:19 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 1CF621A073F for <mib-doctors@ietfa.amsl.com>; Mon, 10 Feb 2014 18:27:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.048
X-Spam-Level: 
X-Spam-Status: No, score=-15.048 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, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.548, 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 lsA57acWCKFM for <mib-doctors@ietfa.amsl.com>; Mon, 10 Feb 2014 18:27:16 -0800 (PST)
Received: from mtv-iport-1.cisco.com (mtv-iport-1.cisco.com [173.36.130.12]) by ietfa.amsl.com (Postfix) with ESMTP id B69CD1A074A for <mib-doctors@ietf.org>; Mon, 10 Feb 2014 18:27:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5098; q=dns/txt; s=iport; t=1392085632; x=1393295232; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to; bh=N/S6cRsoe8G6ftHwpvRt0X6AVZB4/7JbK53bw5NSZL4=; b=LIfrx7ww32/ekN5a07IxjS8bkna3y7ucYZpr5tgjYApHbGK9agleRFXl Rdv7avTQexHxKGRRkpG2Dg0/5aDbHRtjedwVnCT1YwBeEiScvbcAU0TPj 7ybWIPktilJryzRerz/jZGNxLZyXnVUHoCFoNXVgk4XgOdOdIwqE9E7HR g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AkUJAA2K+VKrRDoG/2dsb2JhbABWA4MMOIk1rmOHHoEQFnSCJQEBAQR4AQwCAgkCBAwBBAEBAQkWCAcJAwIBAgEJKwkIBgEMAQUCAQGIAI1mvBsXBI5cEAcGAwiEJwSJSI5ihkeLWYNOGw
X-IronPort-AV: E=Sophos;i="4.95,822,1384300800";  d="scan'208,217";a="102149980"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by mtv-iport-1.cisco.com with ESMTP; 11 Feb 2014 02:27:12 +0000
Received: from [10.154.208.79] ([10.154.208.79]) by mtv-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id s1B2RBUi025837; Tue, 11 Feb 2014 02:27:11 GMT
Message-ID: <52F98A7F.1050002@cisco.com>
Date: Mon, 10 Feb 2014 18:27:11 -0800
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>, Thomas Nadeau <tnadeau@lucidvision.com>, Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
References: <9904FB1B0159DA42B0B887B7FA8119CA243D3C0F@AZ-FFEXMB04.global.avaya.com> <556BB556-669F-4EF5-B8B0-4F1CD7E45BD0@lucidvision.com> <52DE928D.1090909@bwijnen.net> <0b2301cf16ce$bad3a3e0$307aeba0$@olddog.co.uk> <52DF9D02.6070306@cisco.com> <52EE4EF1.3000102@cisco.com> <20140202144457.GA35917@elstar.local> <52F246FB.8010403@cisco.com> <20140205143320.GC46555@elstar.local> <539FBA03-155E-41B3-8618-C2B46887553E@lucidvision.com> <20140205150546.GA46787@elstar.local> <9E272EB0-909B-4D82-8379-DBD3F8F40C5C@lucidvision.com> <9904FB1B0159DA42B0B887B7FA8119CA2E3EF04F@AZ-FFEXMB04.global.avaya.com>
In-Reply-To: <9904FB1B0159DA42B0B887B7FA8119CA2E3EF04F@AZ-FFEXMB04.global.avaya.com>
Content-Type: multipart/alternative; boundary="------------080000040107000108060901"
Cc: Farrel Adrian <adrian@olddog.co.uk>, "MIB Doctors \(E-mail\)" <mib-doctors@ietf.org>
Subject: Re: [MIB-DOCTORS] Why is this MIB module read-write?
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, 11 Feb 2014 02:27:19 -0000

This is a multi-part message in MIME format.
--------------080000040107000108060901
Content-Type: text/plain; charset=windows-1255; format=flowed
Content-Transfer-Encoding: 8bit

Juergen's proposal (copied here for completeness) works for me

    The OPS area recommends the use of NETCONF/YANG standards for
    configuration. IETF working groups are therefore encouraged to use
    the NETCONF/YANG standards for configuration, specifically in new
    charters. SNMP MIB modules modifying persistent configuration state should only be produced by working groups in cases of clear utility and overwhelming consensus to use SNMP write operations for configuration.

Next logical step is to post on the OPS area mailer (in a day or two, to 
wait for the last reactions)

Regards, Benoit
> Yes, positive is good!
>
> Regards,
>
> Dan
>
>
>> -----Original Message-----
>> From: Thomas Nadeau [mailto:tnadeau@lucidvision.com]
>> Sent: éåí ã 05 ôáøåàø 2014 20:40
>> To: Juergen Schoenwaelder
>> Cc: Benoit Claise; Farrel Adrian; Bert Wijnen (IETF); Romascanu, Dan (Dan);
>> MIB Doctors (E-mail)
>> Subject: Re: [MIB-DOCTORS] Why is this MIB module read-write?
>>
>>
>> 	Yes, lets keep it positive for sure. 8)
>>
>> 	--Tom
>>
>>
>>> On Wed, Feb 05, 2014 at 06:48:40AM -0800, Thomas D. Nadeau wrote:
>>>
>>>> we could be picky and discuss running versus persistent configuration
>>>> but that's missing the issue: most providers disable snmp write
>>>> regardless of ultimate configuration state.
>>> Having worked on replacement technology for SNMP for a couple of years
>>> now, I think I do understand the issues and concerns. But then I also
>>> know that there are networks that are not 'provider' networks. I still
>>> believe in positive encouragement to use alternatives (where they
>>> exist) and informed decisions by WGs.
>>>
>>> /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/>
>>>
> .
>


--------------080000040107000108060901
Content-Type: text/html; charset=windows-1255
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=windows-1255"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">Juergen's proposal (copied here for
      completeness) works for me<br>
      <blockquote>
        <pre wrap="">The OPS area recommends the use of NETCONF/YANG standards for
configuration. IETF working groups are therefore encouraged to use
the NETCONF/YANG standards for configuration, specifically in new
charters. SNMP MIB modules modifying persistent configuration state should only be produced by working groups in cases of clear utility and overwhelming consensus to use SNMP write operations for configuration.</pre>
      </blockquote>
      Next logical step is to post on the OPS area mailer (in a day or
      two, to wait for the last reactions)<br>
      <br>
      Regards, Benoit<br>
    </div>
    <blockquote
cite="mid:9904FB1B0159DA42B0B887B7FA8119CA2E3EF04F@AZ-FFEXMB04.global.avaya.com"
      type="cite">
      <pre wrap="">Yes, positive is good!

Regards,

Dan


</pre>
      <blockquote type="cite">
        <pre wrap="">-----Original Message-----
From: Thomas Nadeau [<a class="moz-txt-link-freetext" href="mailto:tnadeau@lucidvision.com">mailto:tnadeau@lucidvision.com</a>]
Sent: éåí ã 05 ôáøåàø 2014 20:40
To: Juergen Schoenwaelder
Cc: Benoit Claise; Farrel Adrian; Bert Wijnen (IETF); Romascanu, Dan (Dan);
MIB Doctors (E-mail)
Subject: Re: [MIB-DOCTORS] Why is this MIB module read-write?


	Yes, lets keep it positive for sure. 8)

	--Tom


</pre>
        <blockquote type="cite">
          <pre wrap="">On Wed, Feb 05, 2014 at 06:48:40AM -0800, Thomas D. Nadeau wrote:

</pre>
          <blockquote type="cite">
            <pre wrap="">we could be picky and discuss running versus persistent configuration
but that's missing the issue: most providers disable snmp write
regardless of ultimate configuration state.
</pre>
          </blockquote>
          <pre wrap="">
Having worked on replacement technology for SNMP for a couple of years
now, I think I do understand the issues and concerns. But then I also
know that there are networks that are not 'provider' networks. I still
believe in positive encouragement to use alternatives (where they
exist) and informed decisions by WGs.

/js

--
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: +49 421 200 3587         Campus Ring 1, 28759 Bremen, Germany
Fax:   +49 421 200 3103         <a class="moz-txt-link-rfc2396E" href="http://www.jacobs-university.de/">&lt;http://www.jacobs-university.de/&gt;</a>

</pre>
        </blockquote>
      </blockquote>
      <pre wrap="">
.

</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------080000040107000108060901--


From randy_presuhn@mindspring.com  Mon Feb 10 21:51:28 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 8F3D01A0340 for <mib-doctors@ietfa.amsl.com>; Mon, 10 Feb 2014 21:51:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.7
X-Spam-Level: 
X-Spam-Status: No, score=0.7 tagged_above=-999 required=5 tests=[BAYES_50=0.8,  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 bbxo5nlfQRFr for <mib-doctors@ietfa.amsl.com>; Mon, 10 Feb 2014 21:51:25 -0800 (PST)
Received: from elasmtp-mealy.atl.sa.earthlink.net (elasmtp-mealy.atl.sa.earthlink.net [209.86.89.69]) by ietfa.amsl.com (Postfix) with ESMTP id 454911A0008 for <mib-doctors@ietf.org>; Mon, 10 Feb 2014 21:51:20 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=qIrP2Utn89sq2ankVrfgpOX4TwOcBwy9z+6xQtFVOVoB4YLcOb7aaJlJCwOnmEQ5; h=Received:Message-ID:From:To:References:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:X-MimeOLE:X-ELNK-Trace:X-Originating-IP;
Received: from [99.23.160.51] (helo=oemcomputer) by elasmtp-mealy.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <randy_presuhn@mindspring.com>) id 1WD6FZ-0005TC-8y for mib-doctors@ietf.org; Tue, 11 Feb 2014 00:51:17 -0500
Message-ID: <005401cf26ed$e4d1e7e0$6b01a8c0@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: "MIB Doctors \(E-mail\)" <mib-doctors@ietf.org>
References: <9904FB1B0159DA42B0B887B7FA8119CA243D3C0F@AZ-FFEXMB04.global.avaya.com> <556BB556-669F-4EF5-B8B0-4F1CD7E45BD0@lucidvision.com> <52DE928D.1090909@bwijnen.net> <0b2301cf16ce$bad3a3e0$307aeba0$@olddog.co.uk> <52DF9D02.6070306@cisco.com> <52EE4EF1.3000102@cisco.com> <20140202144457.GA35917@elstar.local> <52F246FB.8010403@cisco.com> <20140205143320.GC46555@elstar.local> <539FBA03-155E-41B3-8618-C2B46887553E@lucidvision.com> <20140205150546.GA46787@elstar.local> <9E272EB0-909B-4D82-8379-DBD3F8F40C5C@lucidvision.com> <9904FB1B0159DA42B0B887B7FA8119CA2E3EF04F@AZ-FFEXMB04.global.avaya.com> <52F98A7F.1050002@cisco.com>
Date: Mon, 10 Feb 2014 21:55:39 -0800
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1478
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478
X-ELNK-Trace: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d88891b749bef7332bbcd92927ded2971b65e212d83b7f4dc607350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 99.23.160.51
Subject: Re: [MIB-DOCTORS] Why is this MIB module read-write?
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, 11 Feb 2014 05:51:28 -0000

Hi -

> From: "Benoit Claise" <bclaise@cisco.com>
...
> clear utility and overwhelming consensus
...

What is the difference between "rough consensus"
and "overwhelming consensus"?

Randy


From bclaise@cisco.com  Mon Feb 10 22:03:12 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 A443F1A0763 for <mib-doctors@ietfa.amsl.com>; Mon, 10 Feb 2014 22:03:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.049
X-Spam-Level: 
X-Spam-Status: No, score=-15.049 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.548, 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 Gl890YMuSXgI for <mib-doctors@ietfa.amsl.com>; Mon, 10 Feb 2014 22:03:11 -0800 (PST)
Received: from mtv-iport-3.cisco.com (mtv-iport-3.cisco.com [173.36.130.14]) by ietfa.amsl.com (Postfix) with ESMTP id EC2421A0686 for <mib-doctors@ietf.org>; Mon, 10 Feb 2014 22:03:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=619; q=dns/txt; s=iport; t=1392098591; x=1393308191; h=message-id:date:from:mime-version:to:subject:references: in-reply-to:content-transfer-encoding; bh=HUpFn9biP5u5FSYBDb/sFtipeyxi91lUhpuadm9LmRU=; b=FXNVHGnE8WE17GMEmc/9Rm5Rgs9MnN0Qt3PbK2DSYMb9lX4ul6mlNjsi rLgnZ9PTxkCqW+TP5rvx6ZshQBbyoVgrNSoBFK7eE9p7gyQznlZ7m7eZP zDdFuna2rzPJLed8FxUYmxHmjM1QhdD15zb27/BOzOVsNymWpoOC+g/Um g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvgIAJq8+VKrRDoH/2dsb2JhbABZgww4uB2HHoEMFnSCJQEBAQQBAQE1NgoRCxUDCRYPCQMCAQIBFTAGAQwGAgEBiAAOyV4TBI53hDgBA4lIgxmLSYZHfIpdg04b
X-IronPort-AV: E=Sophos;i="4.95,823,1384300800"; d="scan'208";a="102867465"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by mtv-iport-3.cisco.com with ESMTP; 11 Feb 2014 06:03:10 +0000
Received: from [10.21.124.198] (sjc-vpn6-1222.cisco.com [10.21.124.198]) by mtv-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id s1B63ARP018352; Tue, 11 Feb 2014 06:03:10 GMT
Message-ID: <52F9BD1E.2000409@cisco.com>
Date: Mon, 10 Feb 2014 22:03:10 -0800
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Randy Presuhn <randy_presuhn@mindspring.com>, "MIB Doctors (E-mail)" <mib-doctors@ietf.org>
References: <9904FB1B0159DA42B0B887B7FA8119CA243D3C0F@AZ-FFEXMB04.global.avaya.com> <556BB556-669F-4EF5-B8B0-4F1CD7E45BD0@lucidvision.com> <52DE928D.1090909@bwijnen.net> <0b2301cf16ce$bad3a3e0$307aeba0$@olddog.co.uk> <52DF9D02.6070306@cisco.com> <52EE4EF1.3000102@cisco.com> <20140202144457.GA35917@elstar.local> <52F246FB.8010403@cisco.com> <20140205143320.GC46555@elstar.local> <539FBA03-155E-41B3-8618-C2B46887553E@lucidvision.com> <20140205150546.GA46787@elstar.local> <9E272EB0-909B-4D82-8379-DBD3F8F40C5C@lucidvision.com> <9904FB1B0159DA42B0B887B7FA8119CA2E3EF04F@AZ-FFEXMB04.global.avaya.com> <52F98A7F.1050002@cisco.com> <005401cf26ed$e4d1e7e0$6b01a8c0@oemcomputer>
In-Reply-To: <005401cf26ed$e4d1e7e0$6b01a8c0@oemcomputer>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [MIB-DOCTORS] Why is this MIB module read-write?
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, 11 Feb 2014 06:03:12 -0000

On 10/02/2014 21:55, Randy Presuhn wrote:
> Hi -
>
>> From: "Benoit Claise" <bclaise@cisco.com>
> ...
>> clear utility and overwhelming consensus
> ...
>
> What is the difference between "rough consensus"
> and "overwhelming consensus"?
We discussed this point while working on the first proposal. The 
agreement was to remove "overwhelming"
"overwhelming" should also be removed from this proposal.
Good catch!

Regards, Benoit
>
> Randy
>
> _______________________________________________
> MIB-DOCTORS mailing list
> MIB-DOCTORS@ietf.org
> https://www.ietf.org/mailman/listinfo/mib-doctors
>


From dromasca@avaya.com  Tue Feb 11 03:18:14 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 D3B3A1A06CA for <mib-doctors@ietfa.amsl.com>; Tue, 11 Feb 2014 03:18:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548] 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 L_uy3bQ1bQCJ for <mib-doctors@ietfa.amsl.com>; Tue, 11 Feb 2014 03:18:12 -0800 (PST)
Received: from p-us1-iereast-outbound.us1.avaya.com (p-us1-iereast-outbound.us1.avaya.com [135.11.29.13]) by ietfa.amsl.com (Postfix) with ESMTP id C5C411A00AE for <mib-doctors@ietf.org>; Tue, 11 Feb 2014 03:18:12 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AikHAH4G+lKHCzI1/2dsb2JhbABZgmshOFe3R4cegQ8WdIIlAQEBAQMBAQEPXBcEAgEGAg0BAwQBAQEKHQcnCxQJCAIEARIIGodjAQyMWZE8qmYTBI5IOAaDHoEUBIxhkjhUil2DLYIq
X-IronPort-AV: E=Sophos;i="4.95,825,1384318800"; d="scan'208";a="49075636"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by p-us1-iereast-outbound.us1.avaya.com with ESMTP; 11 Feb 2014 06:18:11 -0500
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; 11 Feb 2014 06:05:21 -0500
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; Tue, 11 Feb 2014 06:18:10 -0500
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: Benoit Claise <bclaise@cisco.com>, Randy Presuhn <randy_presuhn@mindspring.com>, "MIB Doctors (E-mail)" <mib-doctors@ietf.org>
Thread-Topic: [MIB-DOCTORS] Why is this MIB module read-write?
Thread-Index: AQHPJtDHKQ1+3Ratf0K/ekWYkJBngZqvjQyg///ycACAAGeXYA==
Date: Tue, 11 Feb 2014 11:18:09 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA2E3FCEA0@AZ-FFEXMB04.global.avaya.com>
References: <9904FB1B0159DA42B0B887B7FA8119CA243D3C0F@AZ-FFEXMB04.global.avaya.com> <556BB556-669F-4EF5-B8B0-4F1CD7E45BD0@lucidvision.com> <52DE928D.1090909@bwijnen.net> <0b2301cf16ce$bad3a3e0$307aeba0$@olddog.co.uk> <52DF9D02.6070306@cisco.com> <52EE4EF1.3000102@cisco.com> <20140202144457.GA35917@elstar.local> <52F246FB.8010403@cisco.com> <20140205143320.GC46555@elstar.local> <539FBA03-155E-41B3-8618-C2B46887553E@lucidvision.com> <20140205150546.GA46787@elstar.local> <9E272EB0-909B-4D82-8379-DBD3F8F40C5C@lucidvision.com> <9904FB1B0159DA42B0B887B7FA8119CA2E3EF04F@AZ-FFEXMB04.global.avaya.com> <52F98A7F.1050002@cisco.com> <005401cf26ed$e4d1e7e0$6b01a8c0@oemcomputer> <52F9BD1E.2000409@cisco.com>
In-Reply-To: <52F9BD1E.2000409@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: text/plain; charset="windows-1255"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [MIB-DOCTORS] Why is this MIB module read-write?
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, 11 Feb 2014 11:18:15 -0000

Yes, please. Let us avoid defining a new class of consensus and let the cha=
irs and the AD decide from case to case. Otherwise I support this statement=
 and I hope that it will be followed by an IESG action in the same directio=
n.

Regards,

Dan




> -----Original Message-----
> From: MIB-DOCTORS [mailto:mib-doctors-bounces@ietf.org] On Behalf Of
> Benoit Claise
> Sent: =E9=E5=ED=A0=E2 11 =F4=E1=F8=E5=E0=F8 2014 08:03
> To: Randy Presuhn; MIB Doctors (E-mail)
> Subject: Re: [MIB-DOCTORS] Why is this MIB module read-write?
>=20
> On 10/02/2014 21:55, Randy Presuhn wrote:
> > Hi -
> >
> >> From: "Benoit Claise" <bclaise@cisco.com>
> > ...
> >> clear utility and overwhelming consensus
> > ...
> >
> > What is the difference between "rough consensus"
> > and "overwhelming consensus"?
> We discussed this point while working on the first proposal. The agreemen=
t
> was to remove "overwhelming"
> "overwhelming" should also be removed from this proposal.
> Good catch!
>=20
> Regards, Benoit
> >
> > Randy
> >
> > _______________________________________________
> > MIB-DOCTORS mailing list
> > MIB-DOCTORS@ietf.org
> > https://www.ietf.org/mailman/listinfo/mib-doctors
> >
>=20
> _______________________________________________
> MIB-DOCTORS mailing list
> MIB-DOCTORS@ietf.org
> https://www.ietf.org/mailman/listinfo/mib-doctors


From tnadeau@lucidvision.com  Tue Feb 11 06:40:24 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 261441A032D for <mib-doctors@ietfa.amsl.com>; Tue, 11 Feb 2014 06:40:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548] 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 WKugRUyAtIgZ for <mib-doctors@ietfa.amsl.com>; Tue, 11 Feb 2014 06:40:22 -0800 (PST)
Received: from lucidvision.com (lucidvision.com [72.71.250.34]) by ietfa.amsl.com (Postfix) with ESMTP id C2B131A0326 for <mib-doctors@ietf.org>; Tue, 11 Feb 2014 06:40:21 -0800 (PST)
Received: from [192.168.1.122] (static-72-71-250-38.cncdnh.fast04.myfairpoint.net [72.71.250.38]) by lucidvision.com (Postfix) with ESMTP id 2AA0A26E9A22; Tue, 11 Feb 2014 09:40:21 -0500 (EST)
Content-Type: multipart/signed; boundary="Apple-Mail=_99550E59-CEFA-4B84-9D89-55D8199964E7"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Thomas Nadeau <tnadeau@lucidvision.com>
In-Reply-To: <9904FB1B0159DA42B0B887B7FA8119CA2E3FCEA0@AZ-FFEXMB04.global.avaya.com>
Date: Tue, 11 Feb 2014 09:40:20 -0500
Message-Id: <B11A877B-FF39-41AD-BC12-648195057DBE@lucidvision.com>
References: <9904FB1B0159DA42B0B887B7FA8119CA243D3C0F@AZ-FFEXMB04.global.avaya.com> <556BB556-669F-4EF5-B8B0-4F1CD7E45BD0@lucidvision.com> <52DE928D.1090909@bwijnen.net> <0b2301cf16ce$bad3a3e0$307aeba0$@olddog.co.uk> <52DF9D02.6070306@cisco.com> <52EE4EF1.3000102@cisco.com> <20140202144457.GA35917@elstar.local> <52F246FB.8010403@cisco.com> <20140205143320.GC46555@elstar.local> <539FBA03-155E-41B3-8618-C2B46887553E@lucidvision.com> <20140205150546.GA46787@elstar.local> <9E272EB0-909B-4D82-8379-DBD3F8F40C5C@lucidvision.com> <9904FB1B0159DA42B0B887B7FA8119CA2E3EF04F@AZ-FFEXMB04.global.avaya.com> <52F98A7F.1050002@cisco.com> <005401cf26ed$e4d1e7e0$6b01a8c0@oemcomputer> <52F9BD1E.2000409@cisco.com> <9904FB1B0159DA42B0B887B7FA8119CA2E3FCEA0@AZ-FFEXMB04.global.avaya.com>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
X-Mailer: Apple Mail (2.1827)
Cc: Randy Presuhn <randy_presuhn@mindspring.com>, "MIB Doctors \(E-mail\)" <mib-doctors@ietf.org>
Subject: Re: [MIB-DOCTORS] Why is this MIB module read-write?
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, 11 Feb 2014 14:40:24 -0000

--Apple-Mail=_99550E59-CEFA-4B84-9D89-55D8199964E7
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1255


	The reason we originally had "overwhelming" in the statement was =
simple: consensus rules are a bit loose for this. For example, WGs =
typically have about %.05 of the people there that care about doing MIBs =
to begin with, so it is hard to determine consensus to even work on new =
MIBs to start with. Once adopted, decisions on HOW those MIBs are =
constructed then largely falls onto the shoulders of those same few =
people. When questions of "read vs write" come up, I've witnessed in =
numerous WGs that only those few MIB authors have any opinions and the =
remaining %99.05 of the WG doesn't raise their hands for either option =
(read or read-write), and will often raise for "I don't care".  Then the =
matter falls onto basically a vote between the 2 or 3 co-authors as to =
making it read-write or not. The point here is that here is where the =
WGs could really use the extra time/resources of both the WG, MIB DRs =
and the IESG reviews to produce many more read-only MIBs to target WG =
charter items instead of spending the exponentially greater amount of =
time making 1 or 2 people in the WG happy with writable MIBs.   That =
approach to me anyways, seems to address the larger WG's needs.

	--Tom


On Feb 11, 2014:6:18 AM, at 6:18 AM, Romascanu, Dan (Dan) =
<dromasca@avaya.com> wrote:

> Yes, please. Let us avoid defining a new class of consensus and let =
the chairs and the AD decide from case to case. Otherwise I support this =
statement and I hope that it will be followed by an IESG action in the =
same direction.
>=20
> Regards,
>=20
> Dan
>=20
>=20
>=20
>=20
>> -----Original Message-----
>> From: MIB-DOCTORS [mailto:mib-doctors-bounces@ietf.org] On Behalf Of
>> Benoit Claise
>> Sent: =E9=E5=ED =E2 11 =F4=E1=F8=E5=E0=F8 2014 08:03
>> To: Randy Presuhn; MIB Doctors (E-mail)
>> Subject: Re: [MIB-DOCTORS] Why is this MIB module read-write?
>>=20
>> On 10/02/2014 21:55, Randy Presuhn wrote:
>>> Hi -
>>>=20
>>>> From: "Benoit Claise" <bclaise@cisco.com>
>>> ...
>>>> clear utility and overwhelming consensus
>>> ...
>>>=20
>>> What is the difference between "rough consensus"
>>> and "overwhelming consensus"?
>> We discussed this point while working on the first proposal. The =
agreement
>> was to remove "overwhelming"
>> "overwhelming" should also be removed from this proposal.
>> Good catch!
>>=20
>> Regards, Benoit
>>>=20
>>> Randy
>>>=20
>>> _______________________________________________
>>> MIB-DOCTORS mailing list
>>> MIB-DOCTORS@ietf.org
>>> https://www.ietf.org/mailman/listinfo/mib-doctors
>>>=20
>>=20
>> _______________________________________________
>> MIB-DOCTORS mailing list
>> MIB-DOCTORS@ietf.org
>> https://www.ietf.org/mailman/listinfo/mib-doctors
>=20
> _______________________________________________
> MIB-DOCTORS mailing list
> MIB-DOCTORS@ietf.org
> https://www.ietf.org/mailman/listinfo/mib-doctors


--Apple-Mail=_99550E59-CEFA-4B84-9D89-55D8199964E7
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

iQIcBAEBCgAGBQJS+jZUAAoJEPcO+I7eiUJZsG8QAI/qhz703W/vQemGsOB87tcq
mv+X1DOrHTn2rM/buaeRXxHiQFxkAqrL9V7UhhrvO8gubErU+HXluQPURtwnSEUW
lj0Rzl/LzDeZFVQJaXRZ+gxpdmtgYHzupxnwfpaxASeeRNHRdlurNqx8s3Spa+sD
A9xF/68DkOdG0U3NqCWC+2kOPj7GsbG3PY9a3r1NaNWCzn1e2BdijXVrrbPQBmFu
lTXinYAWvflrk2BHPsEiAbZT3L71fTctfLVXUFAUPzOVIIVIXlmRCRa2afcRRXnW
BYumPzxsUJp3rOszr3439e80IxKNExEPPskr3MSah+nxgqIoMMU5M3gCKXOEbIwb
F+i4e6pTO7RXV64to3o/PFzNU1uYwjWrVS/yUx1kEE7ib1TH6xssbuY7lH7v2E4d
iF8+EUmxjAOQdyhZM+P1Nesn6GrO4QnCHiZrfcqBBh4YgsEV5wWMuQSy63Z/h5WM
SusvdXZ9a2vLiVYRkyk2q+bw/EOl8WNhO+JwYkdw5Sk2rSIEyUFDK6fcJrFUQRdI
amctDKf4v8PLjV8Ih28bsgiJs7w28ci+NxvsuJWERGGe3/FY9rUtROSaMwj9KbZK
cz3gmPjZtksIZUJneAYh1QmQuYSNsq4sWoL4oWs1dopRN7S9oJV1hNAJSRxN9eTH
cnU39ym7QGzz43W2mGbw
=6LM0
-----END PGP SIGNATURE-----

--Apple-Mail=_99550E59-CEFA-4B84-9D89-55D8199964E7--


From andy@yumaworks.com  Tue Feb 11 07:47:29 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 4DC001A03AD for <mib-doctors@ietfa.amsl.com>; Tue, 11 Feb 2014 07:47:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Level: 
X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 1oMzrUMWaGbN for <mib-doctors@ietfa.amsl.com>; Tue, 11 Feb 2014 07:47:26 -0800 (PST)
Received: from mail-qc0-f181.google.com (mail-qc0-f181.google.com [209.85.216.181]) by ietfa.amsl.com (Postfix) with ESMTP id E25291A0308 for <mib-doctors@ietf.org>; Tue, 11 Feb 2014 07:47:25 -0800 (PST)
Received: by mail-qc0-f181.google.com with SMTP id e9so13098009qcy.40 for <mib-doctors@ietf.org>; Tue, 11 Feb 2014 07:47:25 -0800 (PST)
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=EqiqMD4cIOmycEdJ8178K+rqwSGlimRMz5BVHGKo1MY=; b=AhAZu+8ce71L5QRyLZ+pzBV/9tKWAEi/ssTKPQesDQRuyldSEV5TFLv5uxA+mQaj8W TU1FeXwMkNg/ljLjfTXXKKh8FGqDCk7XJAEZN3xVFB1J6uPB+zkpisd0JpwRZV2Lisvv zop6OqszdmgbDG70/7QjiM/FlyBbJ+TnhzdknwOwnOe7x3fkyReQvAIIx8IF7RUIf1wW LDY0CWXxnk3dKeexREqsLTpLXwj2ZB+l8BqEkOMbYGM3p1kKDLvsGuUwZIdeWuknceG9 j7U0a9IZQ2BwC1oULEEgNmL4Zqrf9xyvPgOZ2qWWekogSGOuIwH/l/rUG4t5ZnSdG3YN /YEg==
X-Gm-Message-State: ALoCoQnKHalVpbvAtULSp63pKLYXGTBoHd61hqZZfSp2daXZTNuX4alyAM2GbIIndqC0eKecTrLF
MIME-Version: 1.0
X-Received: by 10.224.19.199 with SMTP id c7mr39298969qab.78.1392133645191; Tue, 11 Feb 2014 07:47:25 -0800 (PST)
Received: by 10.140.98.130 with HTTP; Tue, 11 Feb 2014 07:47:25 -0800 (PST)
In-Reply-To: <B11A877B-FF39-41AD-BC12-648195057DBE@lucidvision.com>
References: <9904FB1B0159DA42B0B887B7FA8119CA243D3C0F@AZ-FFEXMB04.global.avaya.com> <556BB556-669F-4EF5-B8B0-4F1CD7E45BD0@lucidvision.com> <52DE928D.1090909@bwijnen.net> <0b2301cf16ce$bad3a3e0$307aeba0$@olddog.co.uk> <52DF9D02.6070306@cisco.com> <52EE4EF1.3000102@cisco.com> <20140202144457.GA35917@elstar.local> <52F246FB.8010403@cisco.com> <20140205143320.GC46555@elstar.local> <539FBA03-155E-41B3-8618-C2B46887553E@lucidvision.com> <20140205150546.GA46787@elstar.local> <9E272EB0-909B-4D82-8379-DBD3F8F40C5C@lucidvision.com> <9904FB1B0159DA42B0B887B7FA8119CA2E3EF04F@AZ-FFEXMB04.global.avaya.com> <52F98A7F.1050002@cisco.com> <005401cf26ed$e4d1e7e0$6b01a8c0@oemcomputer> <52F9BD1E.2000409@cisco.com> <9904FB1B0159DA42B0B887B7FA8119CA2E3FCEA0@AZ-FFEXMB04.global.avaya.com> <B11A877B-FF39-41AD-BC12-648195057DBE@lucidvision.com>
Date: Tue, 11 Feb 2014 07:47:25 -0800
Message-ID: <CABCOCHTGJwq3k87Cnez_FPoO2n4eH60wezvZTOsX_3-=WOJ1Rg@mail.gmail.com>
From: Andy Bierman <andy@yumaworks.com>
To: Thomas Nadeau <tnadeau@lucidvision.com>
Content-Type: multipart/alternative; boundary=001a11c2b3ca66e70504f2235f54
Cc: Randy Presuhn <randy_presuhn@mindspring.com>, "MIB Doctors \(E-mail\)" <mib-doctors@ietf.org>
Subject: Re: [MIB-DOCTORS] Why is this MIB module read-write?
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, 11 Feb 2014 15:47:29 -0000

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

Hi,

Have to agree with you.
I've been that 1 "MIB guy" in the room working with
a domain-specific WG that developed a MIB module nobody
cared about.

Back then I thought it would get us closer to getting SNMP Set adopted.
I was wrong.  It had no positive impact on SNMP adoption at all.
It has been far too easy to get a MIB through a WG that has barely
been read, let alone has supporters and implementations planned.

It is up to the IESG approving charters whether or not the policy is fixed.
Adding the word "overwhelming" is not going to change that. If the WG
says "let's have a MIB" the AD should ask for a hum or a show of hands who
is planning to implement read-write MIB objects.


Andy


On Tue, Feb 11, 2014 at 6:40 AM, Thomas Nadeau <tnadeau@lucidvision.com>wro=
te:

>
>         The reason we originally had "overwhelming" in the statement was
> simple: consensus rules are a bit loose for this. For example, WGs
> typically have about %.05 of the people there that care about doing MIBs =
to
> begin with, so it is hard to determine consensus to even work on new MIBs
> to start with. Once adopted, decisions on HOW those MIBs are constructed
> then largely falls onto the shoulders of those same few people. When
> questions of "read vs write" come up, I've witnessed in numerous WGs that
> only those few MIB authors have any opinions and the remaining %99.05 of
> the WG doesn't raise their hands for either option (read or read-write),
> and will often raise for "I don't care".  Then the matter falls onto
> basically a vote between the 2 or 3 co-authors as to making it read-write
> or not. The point here is that here is where the WGs could really use the
> extra time/resources of both the WG, MIB DRs and the IESG reviews to
> produce many more read-only MIBs to target WG charter items instead of
> spending the exponentially greater amount of time making 1 or 2 people in
> the WG happy with writable MIBs.   That approach to me anyways, seems to
> address the larger WG's needs.
>
>         --Tom
>
>
> On Feb 11, 2014:6:18 AM, at 6:18 AM, Romascanu, Dan (Dan) <
> dromasca@avaya.com> wrote:
>
> > Yes, please. Let us avoid defining a new class of consensus and let the
> chairs and the AD decide from case to case. Otherwise I support this
> statement and I hope that it will be followed by an IESG action in the sa=
me
> direction.
> >
> > Regards,
> >
> > Dan
> >
> >
> >
> >
> >> -----Original Message-----
> >> From: MIB-DOCTORS [mailto:mib-doctors-bounces@ietf.org] On Behalf Of
> >> Benoit Claise
> >> Sent: =D7=99=D7=95=D7=9D =D7=92 11 =D7=A4=D7=91=D7=A8=D7=95=D7=90=D7=
=A8 2014 08:03
> >> To: Randy Presuhn; MIB Doctors (E-mail)
> >> Subject: Re: [MIB-DOCTORS] Why is this MIB module read-write?
> >>
> >> On 10/02/2014 21:55, Randy Presuhn wrote:
> >>> Hi -
> >>>
> >>>> From: "Benoit Claise" <bclaise@cisco.com>
> >>> ...
> >>>> clear utility and overwhelming consensus
> >>> ...
> >>>
> >>> What is the difference between "rough consensus"
> >>> and "overwhelming consensus"?
> >> We discussed this point while working on the first proposal. The
> agreement
> >> was to remove "overwhelming"
> >> "overwhelming" should also be removed from this proposal.
> >> Good catch!
> >>
> >> Regards, Benoit
> >>>
> >>> Randy
> >>>
> >>> _______________________________________________
> >>> 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
> >
> > _______________________________________________
> > 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
>
>

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

<div dir=3D"ltr">Hi,<div><br></div><div>Have to agree with you.</div><div>I=
&#39;ve been that 1 &quot;MIB guy&quot; in the room working with</div><div>=
a domain-specific WG that developed a MIB module nobody</div><div>cared abo=
ut.<br>
<div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">Back then I=
 thought it would get us closer to getting SNMP Set adopted.</div><div clas=
s=3D"gmail_extra">I was wrong. =C2=A0It had no positive impact on SNMP adop=
tion at all.</div>
<div class=3D"gmail_extra">It has been far too easy to get a MIB through a =
WG that has barely</div><div class=3D"gmail_extra">been read, let alone has=
 supporters and implementations planned.</div><div class=3D"gmail_extra"><b=
r>
</div><div class=3D"gmail_extra">It is up to the IESG approving charters wh=
ether or not the policy is fixed.</div><div class=3D"gmail_extra">Adding th=
e word &quot;overwhelming&quot; is not going to change that. If the WG</div=
>
<div class=3D"gmail_extra">says &quot;let&#39;s have a MIB&quot; the AD sho=
uld ask for a hum or a show of hands who</div><div class=3D"gmail_extra">is=
 planning to implement read-write MIB objects.</div><div class=3D"gmail_ext=
ra">
<br></div><div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">A=
ndy</div><div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra"><b=
r><div class=3D"gmail_quote">On Tue, Feb 11, 2014 at 6:40 AM, Thomas Nadeau=
 <span dir=3D"ltr">&lt;<a href=3D"mailto:tnadeau@lucidvision.com" target=3D=
"_blank">tnadeau@lucidvision.com</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"><br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 The reason we originally had &quot;overwhelming=
&quot; in the statement was simple: consensus rules are a bit loose for thi=
s. For example, WGs typically have about %.05 of the people there that care=
 about doing MIBs to begin with, so it is hard to determine consensus to ev=
en work on new MIBs to start with. Once adopted, decisions on HOW those MIB=
s are constructed then largely falls onto the shoulders of those same few p=
eople. When questions of &quot;read vs write&quot; come up, I&#39;ve witnes=
sed in numerous WGs that only those few MIB authors have any opinions and t=
he remaining %99.05 of the WG doesn&#39;t raise their hands for either opti=
on (read or read-write), and will often raise for &quot;I don&#39;t care&qu=
ot;. =C2=A0Then the matter falls onto basically a vote between the 2 or 3 c=
o-authors as to making it read-write or not. The point here is that here is=
 where the WGs could really use the extra time/resources of both the WG, MI=
B DRs and the IESG reviews to produce many more read-only MIBs to target WG=
 charter items instead of spending the exponentially greater amount of time=
 making 1 or 2 people in the WG happy with writable MIBs. =C2=A0 That appro=
ach to me anyways, seems to address the larger WG&#39;s needs.<br>

<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 --Tom<br>
<br>
<br>
On Feb 11, 2014:6:18 AM, at 6:18 AM, Romascanu, Dan (Dan) &lt;<a href=3D"ma=
ilto:dromasca@avaya.com">dromasca@avaya.com</a>&gt; wrote:<br>
<br>
&gt; Yes, please. Let us avoid defining a new class of consensus and let th=
e chairs and the AD decide from case to case. Otherwise I support this stat=
ement and I hope that it will be followed by an IESG action in the same dir=
ection.<br>

&gt;<br>
&gt; Regards,<br>
&gt;<br>
&gt; Dan<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;&gt; -----Original Message-----<br>
&gt;&gt; From: MIB-DOCTORS [mailto:<a href=3D"mailto:mib-doctors-bounces@ie=
tf.org">mib-doctors-bounces@ietf.org</a>] On Behalf Of<br>
&gt;&gt; Benoit Claise<br>
&gt;&gt; Sent: =D7=99=D7=95=D7=9D =D7=92 11 =D7=A4=D7=91=D7=A8=D7=95=D7=90=
=D7=A8 2014 08:03<br>
&gt;&gt; To: Randy Presuhn; MIB Doctors (E-mail)<br>
&gt;&gt; Subject: Re: [MIB-DOCTORS] Why is this MIB module read-write?<br>
&gt;&gt;<br>
&gt;&gt; On 10/02/2014 21:55, Randy Presuhn wrote:<br>
&gt;&gt;&gt; Hi -<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; From: &quot;Benoit Claise&quot; &lt;<a href=3D"mailto:bcla=
ise@cisco.com">bclaise@cisco.com</a>&gt;<br>
&gt;&gt;&gt; ...<br>
&gt;&gt;&gt;&gt; clear utility and overwhelming consensus<br>
&gt;&gt;&gt; ...<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; What is the difference between &quot;rough consensus&quot;<br>
&gt;&gt;&gt; and &quot;overwhelming consensus&quot;?<br>
&gt;&gt; We discussed this point while working on the first proposal. The a=
greement<br>
&gt;&gt; was to remove &quot;overwhelming&quot;<br>
&gt;&gt; &quot;overwhelming&quot; should also be removed from this proposal=
.<br>
&gt;&gt; Good catch!<br>
&gt;&gt;<br>
&gt;&gt; Regards, Benoit<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Randy<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; _______________________________________________<br>
&gt;&gt;&gt; MIB-DOCTORS mailing list<br>
&gt;&gt;&gt; <a href=3D"mailto:MIB-DOCTORS@ietf.org">MIB-DOCTORS@ietf.org</=
a><br>
&gt;&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/mib-doctors" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/mib-doctors</a><br>
&gt;&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; _______________________________________________<br>
&gt;&gt; MIB-DOCTORS mailing list<br>
&gt;&gt; <a href=3D"mailto:MIB-DOCTORS@ietf.org">MIB-DOCTORS@ietf.org</a><b=
r>
&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/mib-doctors" targ=
et=3D"_blank">https://www.ietf.org/mailman/listinfo/mib-doctors</a><br>
&gt;<br>
&gt; _______________________________________________<br>
&gt; MIB-DOCTORS mailing list<br>
&gt; <a href=3D"mailto:MIB-DOCTORS@ietf.org">MIB-DOCTORS@ietf.org</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/mib-doctors" target=
=3D"_blank">https://www.ietf.org/mailman/listinfo/mib-doctors</a><br>
<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>
<br></blockquote></div><br></div></div></div>

--001a11c2b3ca66e70504f2235f54--


From randy_presuhn@mindspring.com  Tue Feb 11 11:17:16 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 4D1991A070F for <mib-doctors@ietfa.amsl.com>; Tue, 11 Feb 2014 11:17:16 -0800 (PST)
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 QLRiGZdRD7tH for <mib-doctors@ietfa.amsl.com>; Tue, 11 Feb 2014 11:17:13 -0800 (PST)
Received: from elasmtp-masked.atl.sa.earthlink.net (elasmtp-masked.atl.sa.earthlink.net [209.86.89.68]) by ietfa.amsl.com (Postfix) with ESMTP id 661341A06FF for <mib-doctors@ietf.org>; Tue, 11 Feb 2014 11:17:12 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=l5BXQcQVAV8MVuKwIeyzHd/yVQDN5b1KurmQu7QTXS0iF+xzWhQt4z6qWnggIQq1; h=Message-ID:Date:From:Reply-To:To:Subject:Mime-Version:Content-Type:Content-Transfer-Encoding:X-Mailer:X-ELNK-Trace:X-Originating-IP;
Received: from [209.86.224.40] (helo=elwamui-milano.atl.sa.earthlink.net) by elasmtp-masked.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <randy_presuhn@mindspring.com>) id 1WDIpT-0005vV-PM for mib-doctors@ietf.org; Tue, 11 Feb 2014 14:17:11 -0500
Received: from 99.23.163.81 by webmail.earthlink.net with HTTP; Tue, 11 Feb 2014 14:17:11 -0500
Message-ID: <22620850.1392146231683.JavaMail.root@elwamui-milano.atl.sa.earthlink.net>
Date: Tue, 11 Feb 2014 11:17:11 -0800 (GMT-08:00)
From: Randy Presuhn <randy_presuhn@mindspring.com>
To: 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: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d88891b749bef7332bbcaf6e82f40657a5986e6db278222a318a350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 209.86.224.40
Subject: Re: [MIB-DOCTORS] Why is this MIB module read-write?
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: Tue, 11 Feb 2014 19:17:16 -0000

Hi -

>From: Thomas Nadeau <tnadeau@lucidvision.com>
>Sent: Feb 11, 2014 6:40 AM
>To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
>Cc: Benoit Claise <bclaise@cisco.com>, Randy Presuhn <randy_presuhn@mindspring.com>, "MIB Doctors (E-mail)" <mib-doctors@ietf.org>
>Subject: Re: [MIB-DOCTORS] Why is this MIB module read-write?
...
>When questions of "read vs write" come up, I've witnessed
>in numerous WGs that only those few MIB authors have any
>opinions and the remaining %99.05 of the WG doesn't
>raise their hands for either option (read or read-write),
>and will often raise for "I don't care".  Then the matter
>falls onto basically a vote between the 2 or 3 co-authors
>as to making it read-write or not.

Perhaps things have changed, but my experience is that
this situation applies to most aspects of MIB design,
not merely the decision to make something configurable,
and not only in non-O&M working groups.

>The point here is that here is where the WGs could really
>use the extra time/resources of both the WG, MIB DRs and
>the IESG reviews to produce many more read-only MIBs to
>target WG charter items

But by going the "don't care route", they're disagreeing
with your assessment of priority and opportunity cost.

>instead of spending the exponentially greater amount of
>time making 1 or 2 people in the WG happy with writable MIBs.

Exponentially???

If the decision is to recommend Yang/Netconf for the
configuration data, the modeling effort remains - it's
just a decision to use a different syntax and idioms
to represent the configuration model.  I'd be quite
astonished if the time savings are significant,
particularly if there are any interactions between the
MIB module's semantics and those of the Neconf-managed
configuration data.

It sounds as though what you're really asking for is
for working groups to avoid standardizing configuration
interfaces.

Randy


From andy@yumaworks.com  Tue Feb 11 11:44:29 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 298061A0718 for <mib-doctors@ietfa.amsl.com>; Tue, 11 Feb 2014 11:44:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Level: 
X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 C3TTol9bjDKj for <mib-doctors@ietfa.amsl.com>; Tue, 11 Feb 2014 11:44:26 -0800 (PST)
Received: from mail-qa0-f52.google.com (mail-qa0-f52.google.com [209.85.216.52]) by ietfa.amsl.com (Postfix) with ESMTP id 78A4B1A0713 for <mib-doctors@ietf.org>; Tue, 11 Feb 2014 11:44:26 -0800 (PST)
Received: by mail-qa0-f52.google.com with SMTP id j15so12267090qaq.25 for <mib-doctors@ietf.org>; Tue, 11 Feb 2014 11:44:25 -0800 (PST)
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=unXwIMpYM7pB2ewr8UBs+V8fLrBIvR2ihv5VyFl0vqM=; b=DCOYKhX/bp/gIHxwoeq8u6g6Vdak0OTOZqdXjv2KrH7Tw+3Wfdej8Xq1kqJ04yo0US 7ZsyyGAZJvOkhX5R6cKrQKsQeLyYMHk9elfmZBCkZHU4QDlpQ2wsBFIVgnghKWyEPjNn ytUcbV9hVdzhe3Pxs4tyAec7k4xItYaNCNlIBzhZGYrVysNFSEbOC6cyq9imvg/cm0ty XxwN+IrFJhfzVCPvj9pakPkMGBdxoLP4RzfT5X9ohlloXlxnkjGGr0Z7CtWi5kT7IZoa M9lHu9lKHlYUF8XCCQzeOFgwWIpVB4Ro7+T306SegKO1h1gCpwZMx+SrX6zUzJ7kPKYe j8/A==
X-Gm-Message-State: ALoCoQm0fAeJeEhQRyE0nwG6p1pcuYXVtcqvkHWy0o+cz29omNzrRElkgSIZJ1BxcxKvdwL8oDnu
MIME-Version: 1.0
X-Received: by 10.140.87.9 with SMTP id q9mr56314343qgd.94.1392147865792; Tue, 11 Feb 2014 11:44:25 -0800 (PST)
Received: by 10.140.98.130 with HTTP; Tue, 11 Feb 2014 11:44:25 -0800 (PST)
In-Reply-To: <22620850.1392146231683.JavaMail.root@elwamui-milano.atl.sa.earthlink.net>
References: <22620850.1392146231683.JavaMail.root@elwamui-milano.atl.sa.earthlink.net>
Date: Tue, 11 Feb 2014 11:44:25 -0800
Message-ID: <CABCOCHTq+Zj3pAyT9C=8Bmg_TKEEnP__OW-07MDK==iz63j9XA@mail.gmail.com>
From: Andy Bierman <andy@yumaworks.com>
To: Randy Presuhn <randy_presuhn@mindspring.com>
Content-Type: multipart/alternative; boundary=001a113a359c0420ad04f226af26
Cc: "MIB Doctors \(E-mail\)" <mib-doctors@ietf.org>
Subject: Re: [MIB-DOCTORS] Why is this MIB module read-write?
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, 11 Feb 2014 19:44:29 -0000

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

Hi,

The issue here is whether MIB Police is willing to accept that
SNMP Set SHOULD NOT be used for configuration management.
Even if not, the IESG should decide what is the best policy,
not MIB Police. No legacy protocol wants to be replaced ;-)

We don't need to replay the "What's wrong with SNMP Set?" debate
that we had over a decade ago.  NETCONF/YANG is not fully deployed,
but there are many vendors shipping it and working on it.
There is more evidence that vendors are willing to adopt NETCONF/YANG
than there is they will adopt SNMP Set.



Andy





On Tue, Feb 11, 2014 at 11:17 AM, Randy Presuhn <
randy_presuhn@mindspring.com> wrote:

> Hi -
>
> >From: Thomas Nadeau <tnadeau@lucidvision.com>
> >Sent: Feb 11, 2014 6:40 AM
> >To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
> >Cc: Benoit Claise <bclaise@cisco.com>, Randy Presuhn <
> randy_presuhn@mindspring.com>, "MIB Doctors (E-mail)" <
> mib-doctors@ietf.org>
> >Subject: Re: [MIB-DOCTORS] Why is this MIB module read-write?
> ...
> >When questions of "read vs write" come up, I've witnessed
> >in numerous WGs that only those few MIB authors have any
> >opinions and the remaining %99.05 of the WG doesn't
> >raise their hands for either option (read or read-write),
> >and will often raise for "I don't care".  Then the matter
> >falls onto basically a vote between the 2 or 3 co-authors
> >as to making it read-write or not.
>
> Perhaps things have changed, but my experience is that
> this situation applies to most aspects of MIB design,
> not merely the decision to make something configurable,
> and not only in non-O&M working groups.
>
> >The point here is that here is where the WGs could really
> >use the extra time/resources of both the WG, MIB DRs and
> >the IESG reviews to produce many more read-only MIBs to
> >target WG charter items
>
> But by going the "don't care route", they're disagreeing
> with your assessment of priority and opportunity cost.
>
> >instead of spending the exponentially greater amount of
> >time making 1 or 2 people in the WG happy with writable MIBs.
>
> Exponentially???
>
> If the decision is to recommend Yang/Netconf for the
> configuration data, the modeling effort remains - it's
> just a decision to use a different syntax and idioms
> to represent the configuration model.  I'd be quite
> astonished if the time savings are significant,
> particularly if there are any interactions between the
> MIB module's semantics and those of the Neconf-managed
> configuration data.
>
> It sounds as though what you're really asking for is
> for working groups to avoid standardizing configuration
> interfaces.
>
> Randy
>
> _______________________________________________
> MIB-DOCTORS mailing list
> MIB-DOCTORS@ietf.org
> https://www.ietf.org/mailman/listinfo/mib-doctors
>

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

<div dir=3D"ltr">Hi,<div><br></div><div>The issue here is whether MIB Polic=
e is willing to accept that</div><div>SNMP Set SHOULD NOT be used for confi=
guration management.</div><div>Even if not, the IESG should decide what is =
the best policy,</div>
<div>not MIB Police. No legacy protocol wants to be replaced ;-)</div><div>=
<br></div><div>We don&#39;t need to replay the &quot;What&#39;s wrong with =
SNMP Set?&quot; debate</div><div>that we had over a decade ago. =A0NETCONF/=
YANG is not fully deployed,</div>
<div>but there are many vendors shipping it and working on it.</div><div>Th=
ere is more evidence that vendors are willing to adopt NETCONF/YANG</div><d=
iv>than there is they will adopt SNMP Set.</div><div><br></div><div><br>
</div><div><br></div><div>Andy</div><div><br></div><div><br></div><div><br>=
</div></div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">O=
n Tue, Feb 11, 2014 at 11:17 AM, Randy Presuhn <span dir=3D"ltr">&lt;<a hre=
f=3D"mailto:randy_presuhn@mindspring.com" target=3D"_blank">randy_presuhn@m=
indspring.com</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">Hi -<br>
<br>
&gt;From: Thomas Nadeau &lt;<a href=3D"mailto:tnadeau@lucidvision.com">tnad=
eau@lucidvision.com</a>&gt;<br>
&gt;Sent: Feb 11, 2014 6:40 AM<br>
&gt;To: &quot;Romascanu, Dan (Dan)&quot; &lt;<a href=3D"mailto:dromasca@ava=
ya.com">dromasca@avaya.com</a>&gt;<br>
&gt;Cc: Benoit Claise &lt;<a href=3D"mailto:bclaise@cisco.com">bclaise@cisc=
o.com</a>&gt;, Randy Presuhn &lt;<a href=3D"mailto:randy_presuhn@mindspring=
.com">randy_presuhn@mindspring.com</a>&gt;, &quot;MIB Doctors (E-mail)&quot=
; &lt;<a href=3D"mailto:mib-doctors@ietf.org">mib-doctors@ietf.org</a>&gt;<=
br>

&gt;Subject: Re: [MIB-DOCTORS] Why is this MIB module read-write?<br>
...<br>
&gt;When questions of &quot;read vs write&quot; come up, I&#39;ve witnessed=
<br>
&gt;in numerous WGs that only those few MIB authors have any<br>
&gt;opinions and the remaining %99.05 of the WG doesn&#39;t<br>
&gt;raise their hands for either option (read or read-write),<br>
&gt;and will often raise for &quot;I don&#39;t care&quot;. =A0Then the matt=
er<br>
&gt;falls onto basically a vote between the 2 or 3 co-authors<br>
&gt;as to making it read-write or not.<br>
<br>
Perhaps things have changed, but my experience is that<br>
this situation applies to most aspects of MIB design,<br>
not merely the decision to make something configurable,<br>
and not only in non-O&amp;M working groups.<br>
<br>
&gt;The point here is that here is where the WGs could really<br>
&gt;use the extra time/resources of both the WG, MIB DRs and<br>
&gt;the IESG reviews to produce many more read-only MIBs to<br>
&gt;target WG charter items<br>
<br>
But by going the &quot;don&#39;t care route&quot;, they&#39;re disagreeing<=
br>
with your assessment of priority and opportunity cost.<br>
<br>
&gt;instead of spending the exponentially greater amount of<br>
&gt;time making 1 or 2 people in the WG happy with writable MIBs.<br>
<br>
Exponentially???<br>
<br>
If the decision is to recommend Yang/Netconf for the<br>
configuration data, the modeling effort remains - it&#39;s<br>
just a decision to use a different syntax and idioms<br>
to represent the configuration model. =A0I&#39;d be quite<br>
astonished if the time savings are significant,<br>
particularly if there are any interactions between the<br>
MIB module&#39;s semantics and those of the Neconf-managed<br>
configuration data.<br>
<br>
It sounds as though what you&#39;re really asking for is<br>
for working groups to avoid standardizing configuration<br>
interfaces.<br>
<br>
Randy<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>
</blockquote></div><br></div>

--001a113a359c0420ad04f226af26--


From tnadeau@lucidvision.com  Tue Feb 11 12:31:44 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 934A41A0721 for <mib-doctors@ietfa.amsl.com>; Tue, 11 Feb 2014 12:31:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548] 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 WiRyIBXylrMB for <mib-doctors@ietfa.amsl.com>; Tue, 11 Feb 2014 12:31:42 -0800 (PST)
Received: from lucidvision.com (lucidvision.com [72.71.250.34]) by ietfa.amsl.com (Postfix) with ESMTP id 3A7581A0709 for <mib-doctors@ietf.org>; Tue, 11 Feb 2014 12:31:42 -0800 (PST)
Received: from [192.168.1.122] (static-72-71-250-38.cncdnh.fast04.myfairpoint.net [72.71.250.38]) by lucidvision.com (Postfix) with ESMTP id 6289026EA7FD; Tue, 11 Feb 2014 15:31:41 -0500 (EST)
Content-Type: multipart/signed; boundary="Apple-Mail=_1D702FEC-B8A1-45CE-981A-D86479799681"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Thomas Nadeau <tnadeau@lucidvision.com>
In-Reply-To: <22620850.1392146231683.JavaMail.root@elwamui-milano.atl.sa.earthlink.net>
Date: Tue, 11 Feb 2014 15:31:39 -0500
Message-Id: <A901B12A-6A42-4782-B3B0-DB0F0FD41ED4@lucidvision.com>
References: <22620850.1392146231683.JavaMail.root@elwamui-milano.atl.sa.earthlink.net>
To: Randy Presuhn <randy_presuhn@mindspring.com>
X-Mailer: Apple Mail (2.1827)
Cc: "MIB Doctors \(E-mail\)" <mib-doctors@ietf.org>
Subject: Re: [MIB-DOCTORS] Why is this MIB module read-write?
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, 11 Feb 2014 20:31:44 -0000

--Apple-Mail=_1D702FEC-B8A1-45CE-981A-D86479799681
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


On Feb 11, 2014:2:17 PM, at 2:17 PM, Randy Presuhn =
<randy_presuhn@mindspring.com> wrote:

> Hi -
>=20
>> From: Thomas Nadeau <tnadeau@lucidvision.com>
>> Sent: Feb 11, 2014 6:40 AM
>> To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
>> Cc: Benoit Claise <bclaise@cisco.com>, Randy Presuhn =
<randy_presuhn@mindspring.com>, "MIB Doctors (E-mail)" =
<mib-doctors@ietf.org>
>> Subject: Re: [MIB-DOCTORS] Why is this MIB module read-write?
> ...
>> When questions of "read vs write" come up, I've witnessed
>> in numerous WGs that only those few MIB authors have any
>> opinions and the remaining %99.05 of the WG doesn't
>> raise their hands for either option (read or read-write),
>> and will often raise for "I don't care".  Then the matter
>> falls onto basically a vote between the 2 or 3 co-authors
>> as to making it read-write or not.
>=20
> Perhaps things have changed, but my experience is that
> this situation applies to most aspects of MIB design,
> not merely the decision to make something configurable,
> and not only in non-O&M working groups.
>=20
>> The point here is that here is where the WGs could really
>> use the extra time/resources of both the WG, MIB DRs and
>> the IESG reviews to produce many more read-only MIBs to
>> target WG charter items
>=20
> But by going the "don't care route", they're disagreeing
> with your assessment of priority and opportunity cost.
>=20
>> instead of spending the exponentially greater amount of
>> time making 1 or 2 people in the WG happy with writable MIBs.
>=20
> Exponentially???
>=20
> If the decision is to recommend Yang/Netconf for the
> configuration data, the modeling effort remains - it's
> just a decision to use a different syntax and idioms
> to represent the configuration model.  I'd be quite
> astonished if the time savings are significant,
> particularly if there are any interactions between the
> MIB module's semantics and those of the Neconf-managed
> configuration data.

	I am just speaking from my experience having worked
on a couple dozen MIB modules over the past 10 or so years
at the IETF, for various companies (and reviewed a pile of others).=20
The review process for just the initial 4 or 5 MPLS MIBs=20
we did took literally years - ask Bert. *)  And most of
the back-and-forth was related to configuration. This was
the case with *every* MIB I've worked on since. How many
deployments are out there of those MIBs that allow writes?
In my experience working at Cisco, CA and BT (a not so small
network operator), I can safely say that it is 0.

	The point is that making MIBs writable is very painful
and time consuming, and all of that time spent is largely=20
a waste of time because most people are not (or ever were)=20
using SNMP for configuration.  A WG could very well use the
same time/resources to build additional MIBs instead -=20
or even build Yang modules that can be used for=20
configuration! *)

> It sounds as though what you're really asking for is
> for working groups to avoid standardizing configuration
> interfaces.

	Most definitely not.  Nor is the goal of this to
deprecate write from max-access or otherwise remove SETs
from the protocol; the market has taken care of that already.

	--Tom



>=20
> Randy
>=20
> _______________________________________________
> MIB-DOCTORS mailing list
> MIB-DOCTORS@ietf.org
> https://www.ietf.org/mailman/listinfo/mib-doctors
>=20


--Apple-Mail=_1D702FEC-B8A1-45CE-981A-D86479799681
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

iQIcBAEBCgAGBQJS+oisAAoJEPcO+I7eiUJZtSoP/1moGyTd5Tira2leQJ1a7gAu
0b90fLxGZPmaDUymgaFwa9lA1b7hxg4WVL5i9GX+pXn8B3xOapA4ptDdXsTwG5Ff
aIUSyaZS3qlQHq6dV/6yjhkmq0nXQ1myeyCRVQHc2McvqsVMTCfzrCNPaNl2jzg1
h0u21tyFIJ7YJb8riQnyuo921utQ/CFXRHcGZGG5r9fhh7JwnAN+CYc6rVydolUG
i87jQUM4BFrKygoNfyiA4LRlv3ynJiRgT6Pqe9Zsca3h0UH8OfYgI0MMLUMH9NH4
aiWO0CASCl1MfCMqfsBeEEPBH/KDqWYUQOaMTz2UqS5oLrPULBJZE94wNNFV6xR6
q8IMSFcVAfIXfO/to8CflNAKD6sFfVDFNgTheUnAWvrISy6jthXYv3apOSCTsTiW
wHaemxnUL87qxHRdATo+4/yVdroNZ9RvRAu1Akbx9A63aKhNKgpDccvxqgi+ksx3
/13onHtgV2YGpTCiSSSPDWVimiB0eSyyZ5+W02TakRJZTgq9rjtIugXpEUNdyNRj
cvsL7lD4T07HNaEDh9/iJjYKZlViL6rAHjQIBlaMO9IM7bjojpO96VBmDquu9Y1c
oLBPN+UigdJNT5VCQ+HFcjvT7QTtz2GKyELmMrBMR5E9jTPOvR+yblaTnJSwYIhX
O/60NZWvsF03vzDNF6LY
=sYLX
-----END PGP SIGNATURE-----

--Apple-Mail=_1D702FEC-B8A1-45CE-981A-D86479799681--


From randy_presuhn@mindspring.com  Tue Feb 11 12:32:17 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 2EB241A072F for <mib-doctors@ietfa.amsl.com>; Tue, 11 Feb 2014 12:32:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.6
X-Spam-Level: 
X-Spam-Status: No, score=-0.6 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, 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 4ObmSmmdeB2X for <mib-doctors@ietfa.amsl.com>; Tue, 11 Feb 2014 12:32:15 -0800 (PST)
Received: from elasmtp-curtail.atl.sa.earthlink.net (elasmtp-curtail.atl.sa.earthlink.net [209.86.89.64]) by ietfa.amsl.com (Postfix) with ESMTP id 465441A0721 for <mib-doctors@ietf.org>; Tue, 11 Feb 2014 12:32:15 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=n79sdD6tGpWd0lXp9SjGCBXbHaMgC7Xve8fmwVjti//E5iRvWnUcLCvUjfVgZDKY; h=Received:Message-ID:From:To:References:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:X-MimeOLE:X-ELNK-Trace:X-Originating-IP;
Received: from [99.23.163.81] (helo=oemcomputer) by elasmtp-curtail.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <randy_presuhn@mindspring.com>) id 1WDK06-0007VI-5Y for mib-doctors@ietf.org; Tue, 11 Feb 2014 15:32:14 -0500
Message-ID: <000801cf2768$f4c580a0$6b01a8c0@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: "MIB Doctors \(E-mail\)" <mib-doctors@ietf.org>
References: <22620850.1392146231683.JavaMail.root@elwamui-milano.atl.sa.earthlink.net> <CABCOCHTq+Zj3pAyT9C=8Bmg_TKEEnP__OW-07MDK==iz63j9XA@mail.gmail.com>
Date: Tue, 11 Feb 2014 12:36:33 -0800
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1478
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478
X-ELNK-Trace: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d88891b749bef7332bbc5f35d4e310982db1d0109b661cff9daa350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 99.23.163.81
Subject: Re: [MIB-DOCTORS] Why is this MIB module read-write?
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, 11 Feb 2014 20:32:17 -0000

Hi -

> From: "Andy Bierman" <andy@yumaworks.com>
> To: "Randy Presuhn" <randy_presuhn@mindspring.com>
> Cc: "MIB Doctors (E-mail)" <mib-doctors@ietf.org>
> Sent: Tuesday, February 11, 2014 11:44 AM
> Subject: Re: [MIB-DOCTORS] Why is this MIB module read-write?
...
> We don't need to replay the "What's wrong with SNMP Set?" debate
> that we had over a decade ago.

Agreed.  That's not the point of my response to Thomas Nadeau's post.

>  NETCONF/YANG is not fully deployed,
> but there are many vendors shipping it and working on it.
> There is more evidence that vendors are willing to adopt NETCONF/YANG
> than there is they will adopt SNMP Set.

I don't think that point being contended in this discussion.
My concern is that Thomas Nadeau's rationale was framed
in terms of WG opportunity cost, and that the presumed dichotomy
of "expensive configuration MIB module" vs. "free time to do other
needed work" is a false one if one admits the third possibility of
using Yang to model the configuration data.  The realistic choices
are between
   - MIB module
   - Yang module
   - no standardized configuration support

I remain to be convinced that standardizing a configuration data
model expressed  in Yang is significantly less effort for a *working*
*group* than it would be to produce a comparable MIB module,
particularly when there are significant interactions or linkages between
the configuration data and information visible through the operational
MIB module.

As for "no standardized configuration support" - do we really want
to stay^H^H^H^H go there?

Randy


From andy@yumaworks.com  Tue Feb 11 13:05:25 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 759981A0740 for <mib-doctors@ietfa.amsl.com>; Tue, 11 Feb 2014 13:05:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Level: 
X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 j4GxaflXs7ay for <mib-doctors@ietfa.amsl.com>; Tue, 11 Feb 2014 13:05:22 -0800 (PST)
Received: from mail-qa0-f54.google.com (mail-qa0-f54.google.com [209.85.216.54]) by ietfa.amsl.com (Postfix) with ESMTP id 66C301A0732 for <mib-doctors@ietf.org>; Tue, 11 Feb 2014 13:05:22 -0800 (PST)
Received: by mail-qa0-f54.google.com with SMTP id i13so12438937qae.41 for <mib-doctors@ietf.org>; Tue, 11 Feb 2014 13:05:21 -0800 (PST)
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=lAnWTCRQaNV689lhJmul0CIVswMrdbYKUjG9BFJSpt8=; b=RtAuYblvz5vXnUeWD0w3md4Agqp2Ha1bwf5F/Aw/Ia4l3NyJiu6Oa6NoZfYDQiDTGn 2XTMP/SZ1zKa9wZStyOdjovqNHY9JxQNarWz0x4sHAbGa88nv1r4lewGslos3Na9tB2P u97FFngtRCuEi1sAzlv/OjZYNMbzVkYNEd+E6DQKBnmhPHTjjFS73tnMnfOgF1djU3Q4 meG6O+Ce+tEYrxsDXY45pZEp9A4zP6sEzLHm114JIbpIWjTPXxlfOgkalZcJOGSgYoWE CtNoMHBoszIyZML7ZFO0P2AVMLe3FxF3KvUq5usoClaG7tYuB/Qayz598SlbCIV5fCYK rWvQ==
X-Gm-Message-State: ALoCoQk6D6IBM5vw5Lqdpk+E/soLppDa8FQ+i1Fuy6Jiaf/iX2wnR0ccy2NHFTacJPpOHZu7E3ot
MIME-Version: 1.0
X-Received: by 10.140.36.107 with SMTP id o98mr57829506qgo.25.1392152721578; Tue, 11 Feb 2014 13:05:21 -0800 (PST)
Received: by 10.140.98.130 with HTTP; Tue, 11 Feb 2014 13:05:21 -0800 (PST)
In-Reply-To: <000801cf2768$f4c580a0$6b01a8c0@oemcomputer>
References: <22620850.1392146231683.JavaMail.root@elwamui-milano.atl.sa.earthlink.net> <CABCOCHTq+Zj3pAyT9C=8Bmg_TKEEnP__OW-07MDK==iz63j9XA@mail.gmail.com> <000801cf2768$f4c580a0$6b01a8c0@oemcomputer>
Date: Tue, 11 Feb 2014 13:05:21 -0800
Message-ID: <CABCOCHQH7bbBK=7LT7kbKt6ZD4K2TDxfY09n2zboOEv3YD45_w@mail.gmail.com>
From: Andy Bierman <andy@yumaworks.com>
To: Randy Presuhn <randy_presuhn@mindspring.com>
Content-Type: multipart/alternative; boundary=001a11c154b672bdd704f227d09a
Cc: "MIB Doctors \(E-mail\)" <mib-doctors@ietf.org>
Subject: Re: [MIB-DOCTORS] Why is this MIB module read-write?
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, 11 Feb 2014 21:05:25 -0000

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

On Tue, Feb 11, 2014 at 12:36 PM, Randy Presuhn <
randy_presuhn@mindspring.com> wrote:

> Hi -
>
> > From: "Andy Bierman" <andy@yumaworks.com>
> > To: "Randy Presuhn" <randy_presuhn@mindspring.com>
> > Cc: "MIB Doctors (E-mail)" <mib-doctors@ietf.org>
> > Sent: Tuesday, February 11, 2014 11:44 AM
> > Subject: Re: [MIB-DOCTORS] Why is this MIB module read-write?
> ...
> > We don't need to replay the "What's wrong with SNMP Set?" debate
> > that we had over a decade ago.
>
> Agreed.  That's not the point of my response to Thomas Nadeau's post.
>
> >  NETCONF/YANG is not fully deployed,
> > but there are many vendors shipping it and working on it.
> > There is more evidence that vendors are willing to adopt NETCONF/YANG
> > than there is they will adopt SNMP Set.
>
> I don't think that point being contended in this discussion.
> My concern is that Thomas Nadeau's rationale was framed
> in terms of WG opportunity cost, and that the presumed dichotomy
> of "expensive configuration MIB module" vs. "free time to do other
> needed work" is a false one if one admits the third possibility of
> using Yang to model the configuration data.  The realistic choices
> are between
>    - MIB module
>    - Yang module
>    - no standardized configuration support
>
> I remain to be convinced that standardizing a configuration data
> model expressed  in Yang is significantly less effort for a *working*
> *group* than it would be to produce a comparable MIB module,
> particularly when there are significant interactions or linkages between
> the configuration data and information visible through the operational
> MIB module.
>
>
The goal should be to get running code out there.
If vendors don't implement the RFC, then all the work
put into the RFC doesn't count for much.

Something is wrong with the process.
Either vendors are showing great support for read-write
MIB modules and lying about it, or the WGs are creating these
MIB modules without caring if they have any industry support.
I think it is the latter.




> As for "no standardized configuration support" - do we really want
> to stay^H^H^H^H go there?
>
> Randy
>


Andy


>
> _______________________________________________
> MIB-DOCTORS mailing list
> MIB-DOCTORS@ietf.org
> https://www.ietf.org/mailman/listinfo/mib-doctors
>

--001a11c154b672bdd704f227d09a
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 Tue, Feb 11, 2014 at 12:36 PM, Randy Presuhn <span dir=3D"ltr">&=
lt;<a href=3D"mailto:randy_presuhn@mindspring.com" target=3D"_blank">randy_=
presuhn@mindspring.com</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">Hi -<br>
<br>
&gt; From: &quot;Andy Bierman&quot; &lt;<a href=3D"mailto:andy@yumaworks.co=
m">andy@yumaworks.com</a>&gt;<br>
&gt; To: &quot;Randy Presuhn&quot; &lt;<a href=3D"mailto:randy_presuhn@mind=
spring.com">randy_presuhn@mindspring.com</a>&gt;<br>
&gt; Cc: &quot;MIB Doctors (E-mail)&quot; &lt;<a href=3D"mailto:mib-doctors=
@ietf.org">mib-doctors@ietf.org</a>&gt;<br>
&gt; Sent: Tuesday, February 11, 2014 11:44 AM<br>
&gt; Subject: Re: [MIB-DOCTORS] Why is this MIB module read-write?<br>
...<br>
&gt; We don&#39;t need to replay the &quot;What&#39;s wrong with SNMP Set?&=
quot; debate<br>
&gt; that we had over a decade ago.<br>
<br>
Agreed. =A0That&#39;s not the point of my response to Thomas Nadeau&#39;s p=
ost.<br>
<br>
&gt; =A0NETCONF/YANG is not fully deployed,<br>
&gt; but there are many vendors shipping it and working on it.<br>
&gt; There is more evidence that vendors are willing to adopt NETCONF/YANG<=
br>
&gt; than there is they will adopt SNMP Set.<br>
<br>
I don&#39;t think that point being contended in this discussion.<br>
My concern is that Thomas Nadeau&#39;s rationale was framed<br>
in terms of WG opportunity cost, and that the presumed dichotomy<br>
of &quot;expensive configuration MIB module&quot; vs. &quot;free time to do=
 other<br>
needed work&quot; is a false one if one admits the third possibility of<br>
using Yang to model the configuration data. =A0The realistic choices<br>
are between<br>
=A0 =A0- MIB module<br>
=A0 =A0- Yang module<br>
=A0 =A0- no standardized configuration support<br>
<br>
I remain to be convinced that standardizing a configuration data<br>
model expressed =A0in Yang is significantly less effort for a *working*<br>
*group* than it would be to produce a comparable MIB module,<br>
particularly when there are significant interactions or linkages between<br=
>
the configuration data and information visible through the operational<br>
MIB module.<br>
<br></blockquote><div><br></div><div>The goal should be to get running code=
 out there.</div><div>If vendors don&#39;t implement the RFC, then all the =
work</div><div>put into the RFC doesn&#39;t count for much.</div><div>
<br></div><div>Something is wrong with the process.</div><div>Either vendor=
s are showing great support for read-write</div><div>MIB modules and lying =
about it, or the WGs are creating these</div><div>MIB modules without carin=
g if they have any industry support.</div>
<div>I think it is the latter.</div><div><br></div><div><br></div><div>=A0<=
/div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-le=
ft:1px #ccc solid;padding-left:1ex">
As for &quot;no standardized configuration support&quot; - do we really wan=
t<br>
to stay^H^H^H^H go there?<br>
<br>
Randy<br></blockquote><div><br></div><div><br></div><div>Andy</div><div>=A0=
</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-l=
eft:1px #ccc solid;padding-left:1ex">
<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>
</blockquote></div><br></div></div>

--001a11c154b672bdd704f227d09a--


From tnadeau@lucidvision.com  Tue Feb 11 13:15: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 1334E1A0760 for <mib-doctors@ietfa.amsl.com>; Tue, 11 Feb 2014 13:15:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.447
X-Spam-Level: 
X-Spam-Status: No, score=-2.447 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.548] 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 zHNW-95j9TLC for <mib-doctors@ietfa.amsl.com>; Tue, 11 Feb 2014 13:15:14 -0800 (PST)
Received: from lucidvision.com (lucidvision.com [72.71.250.34]) by ietfa.amsl.com (Postfix) with ESMTP id D2BF21A0735 for <mib-doctors@ietf.org>; Tue, 11 Feb 2014 13:15:13 -0800 (PST)
Received: from [10.227.147.247] (mobile-198-228-196-006.mycingular.net [198.228.196.6]) by lucidvision.com (Postfix) with ESMTP id 86D7726EA991; Tue, 11 Feb 2014 16:15:12 -0500 (EST)
References: <22620850.1392146231683.JavaMail.root@elwamui-milano.atl.sa.earthlink.net> <CABCOCHTq+Zj3pAyT9C=8Bmg_TKEEnP__OW-07MDK==iz63j9XA@mail.gmail.com> <000801cf2768$f4c580a0$6b01a8c0@oemcomputer> <CABCOCHQH7bbBK=7LT7kbKt6ZD4K2TDxfY09n2zboOEv3YD45_w@mail.gmail.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: <CABCOCHQH7bbBK=7LT7kbKt6ZD4K2TDxfY09n2zboOEv3YD45_w@mail.gmail.com>
Content-Type: multipart/alternative; boundary=Apple-Mail-CD408397-0278-4558-AD3C-07C6979FB9D4
Content-Transfer-Encoding: 7bit
Message-Id: <771D1B04-2D90-4FD8-A8E8-88840183D020@lucidvision.com>
X-Mailer: iPhone Mail (11B554a)
From: "Thomas D. Nadeau" <tnadeau@lucidvision.com>
Date: Tue, 11 Feb 2014 16:15:12 -0500
To: Andy Bierman <andy@yumaworks.com>
Cc: Randy Presuhn <randy_presuhn@mindspring.com>, "MIB Doctors \(E-mail\)" <mib-doctors@ietf.org>
Subject: Re: [MIB-DOCTORS] Why is this MIB module read-write?
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, 11 Feb 2014 21:15:17 -0000

--Apple-Mail-CD408397-0278-4558-AD3C-07C6979FB9D4
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable



> On Feb 11, 2014, at 4:05 PM, Andy Bierman <andy@yumaworks.com> wrote:
>=20
>=20
>=20
>=20
>> On Tue, Feb 11, 2014 at 12:36 PM, Randy Presuhn <randy_presuhn@mindspring=
.com> wrote:
>> Hi -
>>=20
>> > From: "Andy Bierman" <andy@yumaworks.com>
>> > To: "Randy Presuhn" <randy_presuhn@mindspring.com>
>> > Cc: "MIB Doctors (E-mail)" <mib-doctors@ietf.org>
>> > Sent: Tuesday, February 11, 2014 11:44 AM
>> > Subject: Re: [MIB-DOCTORS] Why is this MIB module read-write?
>> ...
>> > We don't need to replay the "What's wrong with SNMP Set?" debate
>> > that we had over a decade ago.
>>=20
>> Agreed.  That's not the point of my response to Thomas Nadeau's post.
>>=20
>> >  NETCONF/YANG is not fully deployed,
>> > but there are many vendors shipping it and working on it.
>> > There is more evidence that vendors are willing to adopt NETCONF/YANG
>> > than there is they will adopt SNMP Set.
>>=20
>> I don't think that point being contended in this discussion.
>> My concern is that Thomas Nadeau's rationale was framed
>> in terms of WG opportunity cost, and that the presumed dichotomy
>> of "expensive configuration MIB module" vs. "free time to do other
>> needed work" is a false one if one admits the third possibility of
>> using Yang to model the configuration data.  The realistic choices
>> are between
>>    - MIB module
>>    - Yang module
>>    - no standardized configuration support
>>=20
>> I remain to be convinced that standardizing a configuration data
>> model expressed  in Yang is significantly less effort for a *working*
>> *group* than it would be to produce a comparable MIB module,
>> particularly when there are significant interactions or linkages between
>> the configuration data and information visible through the operational
>> MIB module.
>=20
> The goal should be to get running code out there.
> If vendors don't implement the RFC, then all the work
> put into the RFC doesn't count for much.
>=20
> Something is wrong with the process.
> Either vendors are showing great support for read-write
> MIB modules and lying about it, or the WGs are creating these
> MIB modules without caring if they have any industry support.
> I think it is the latter.

It's not just vendors to worry about; it's operators to choose to use their i=
mplementations. I think there is a big difference between running and operat=
ionally in place code.  There are plenty of read-write implementations out t=
here, but almost no one uses them.

Tom=20


>=20
>=20
> =20
>> As for "no standardized configuration support" - do we really want
>> to stay^H^H^H^H go there?
>>=20
>> Randy
>=20
>=20
> Andy
> =20
>>=20
>> _______________________________________________
>> MIB-DOCTORS mailing list
>> MIB-DOCTORS@ietf.org
>> https://www.ietf.org/mailman/listinfo/mib-doctors
>=20
> _______________________________________________
> MIB-DOCTORS mailing list
> MIB-DOCTORS@ietf.org
> https://www.ietf.org/mailman/listinfo/mib-doctors

--Apple-Mail-CD408397-0278-4558-AD3C-07C6979FB9D4
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: 7bit

<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div><br></div><div><br>On Feb 11, 2014, at 4:05 PM, Andy Bierman &lt;<a href="mailto:andy@yumaworks.com">andy@yumaworks.com</a>&gt; wrote:<br><br></div><blockquote type="cite"><div><div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Feb 11, 2014 at 12:36 PM, Randy Presuhn <span dir="ltr">&lt;<a href="mailto:randy_presuhn@mindspring.com" target="_blank">randy_presuhn@mindspring.com</a>&gt;</span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi -<br>
<br>
&gt; From: "Andy Bierman" &lt;<a href="mailto:andy@yumaworks.com">andy@yumaworks.com</a>&gt;<br>
&gt; To: "Randy Presuhn" &lt;<a href="mailto:randy_presuhn@mindspring.com">randy_presuhn@mindspring.com</a>&gt;<br>
&gt; Cc: "MIB Doctors (E-mail)" &lt;<a href="mailto:mib-doctors@ietf.org">mib-doctors@ietf.org</a>&gt;<br>
&gt; Sent: Tuesday, February 11, 2014 11:44 AM<br>
&gt; Subject: Re: [MIB-DOCTORS] Why is this MIB module read-write?<br>
...<br>
&gt; We don't need to replay the "What's wrong with SNMP Set?" debate<br>
&gt; that we had over a decade ago.<br>
<br>
Agreed. &nbsp;That's not the point of my response to Thomas Nadeau's post.<br>
<br>
&gt; &nbsp;NETCONF/YANG is not fully deployed,<br>
&gt; but there are many vendors shipping it and working on it.<br>
&gt; There is more evidence that vendors are willing to adopt NETCONF/YANG<br>
&gt; than there is they will adopt SNMP Set.<br>
<br>
I don't think that point being contended in this discussion.<br>
My concern is that Thomas Nadeau's rationale was framed<br>
in terms of WG opportunity cost, and that the presumed dichotomy<br>
of "expensive configuration MIB module" vs. "free time to do other<br>
needed work" is a false one if one admits the third possibility of<br>
using Yang to model the configuration data. &nbsp;The realistic choices<br>
are between<br>
&nbsp; &nbsp;- MIB module<br>
&nbsp; &nbsp;- Yang module<br>
&nbsp; &nbsp;- no standardized configuration support<br>
<br>
I remain to be convinced that standardizing a configuration data<br>
model expressed &nbsp;in Yang is significantly less effort for a *working*<br>
*group* than it would be to produce a comparable MIB module,<br>
particularly when there are significant interactions or linkages between<br>
the configuration data and information visible through the operational<br>
MIB module.<br>
<br></blockquote><div><br></div><div>The goal should be to get running code out there.</div><div>If vendors don't implement the RFC, then all the work</div><div>put into the RFC doesn't count for much.</div><div>
<br></div><div>Something is wrong with the process.</div><div>Either vendors are showing great support for read-write</div><div>MIB modules and lying about it, or the WGs are creating these</div><div>MIB modules without caring if they have any industry support.</div>
<div>I think it is the latter.</div></div></div></div></div></blockquote><div><br></div><div>It's not just vendors to worry about; it's operators to choose to use their implementations. I think there is a big difference between running and operationally in place code. &nbsp;There are plenty of read-write implementations out there, but almost no one uses them.</div><div><br></div><div>Tom&nbsp;</div><div><br></div><br><blockquote type="cite"><div><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div><br></div><div><br></div><div>&nbsp;</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
As for "no standardized configuration support" - do we really want<br>
to stay^H^H^H^H go there?<br>
<br>
Randy<br></blockquote><div><br></div><div><br></div><div>Andy</div><div>&nbsp;</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
_______________________________________________<br>
MIB-DOCTORS mailing list<br>
<a href="mailto:MIB-DOCTORS@ietf.org">MIB-DOCTORS@ietf.org</a><br>
<a href="https://www.ietf.org/mailman/listinfo/mib-doctors" target="_blank">https://www.ietf.org/mailman/listinfo/mib-doctors</a><br>
</blockquote></div><br></div></div>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>MIB-DOCTORS mailing list</span><br><span><a href="mailto:MIB-DOCTORS@ietf.org">MIB-DOCTORS@ietf.org</a></span><br><span><a href="https://www.ietf.org/mailman/listinfo/mib-doctors">https://www.ietf.org/mailman/listinfo/mib-doctors</a></span><br></div></blockquote></body></html>
--Apple-Mail-CD408397-0278-4558-AD3C-07C6979FB9D4--


From andy@yumaworks.com  Tue Feb 11 13:37:46 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 AAAB51A0775 for <mib-doctors@ietfa.amsl.com>; Tue, 11 Feb 2014 13:37:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Level: 
X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 3uQVciAsx7DO for <mib-doctors@ietfa.amsl.com>; Tue, 11 Feb 2014 13:37:43 -0800 (PST)
Received: from mail-qc0-f172.google.com (mail-qc0-f172.google.com [209.85.216.172]) by ietfa.amsl.com (Postfix) with ESMTP id D49FC1A0777 for <mib-doctors@ietf.org>; Tue, 11 Feb 2014 13:37:42 -0800 (PST)
Received: by mail-qc0-f172.google.com with SMTP id c9so13890107qcz.17 for <mib-doctors@ietf.org>; Tue, 11 Feb 2014 13:37:42 -0800 (PST)
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=rO4eUs2t0x/bu+CHGJG0tjBLgVQ9wg+m2eo+ba02jdA=; b=L+BTKvlUUUWMyrxXiqL9l8rU0LQ0Mr3PbvSH21g//59eulO8a2/QPi/PUTJmwtFiQP fhQq3lyAGuL8JBLfa7X0LgRmyC8Fd7VlnW8Z0dBGfFb6jIo6nfp2v347lKr6WJi5lS+E vjkpAtoYWRw7p/bQtJn9TvTL8YuHgpE13baNuPnZpLbTBiPJybHnE0fXFRkSY+cpbq1X IeD02MJbDUIaqQg+o7TZjKz5OTonbqkX8JnXbn3Ah8YmKrQ5blv850+ffwY693ZwHMFk ZuuHI1c3OvKVrXJEqFOMVof0jI9xqdHDswlKcU+02W4SK1UWN7tKg5tl/igDvqBYdubv 8I8w==
X-Gm-Message-State: ALoCoQnvwLYkWgbSN+Io0SbpDP27QZVS13+aIm6mKJxxML6PNoN25001wg5a1/y2P6BKvy0uLJuJ
MIME-Version: 1.0
X-Received: by 10.140.92.65 with SMTP id a59mr57311377qge.34.1392154662105; Tue, 11 Feb 2014 13:37:42 -0800 (PST)
Received: by 10.140.98.130 with HTTP; Tue, 11 Feb 2014 13:37:41 -0800 (PST)
In-Reply-To: <771D1B04-2D90-4FD8-A8E8-88840183D020@lucidvision.com>
References: <22620850.1392146231683.JavaMail.root@elwamui-milano.atl.sa.earthlink.net> <CABCOCHTq+Zj3pAyT9C=8Bmg_TKEEnP__OW-07MDK==iz63j9XA@mail.gmail.com> <000801cf2768$f4c580a0$6b01a8c0@oemcomputer> <CABCOCHQH7bbBK=7LT7kbKt6ZD4K2TDxfY09n2zboOEv3YD45_w@mail.gmail.com> <771D1B04-2D90-4FD8-A8E8-88840183D020@lucidvision.com>
Date: Tue, 11 Feb 2014 13:37:41 -0800
Message-ID: <CABCOCHQ1=WgiSYdYfqLF5iwbVO7xOF=W88CNd1SVUZ+qus=N6Q@mail.gmail.com>
From: Andy Bierman <andy@yumaworks.com>
To: "Thomas D. Nadeau" <tnadeau@lucidvision.com>
Content-Type: multipart/alternative; boundary=001a113ab29e1bad2a04f2284422
Cc: Randy Presuhn <randy_presuhn@mindspring.com>, "MIB Doctors \(E-mail\)" <mib-doctors@ietf.org>
Subject: Re: [MIB-DOCTORS] Why is this MIB module read-write?
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, 11 Feb 2014 21:37:46 -0000

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

On Tue, Feb 11, 2014 at 1:15 PM, Thomas D. Nadeau
<tnadeau@lucidvision.com>wrote:

>
>
> On Feb 11, 2014, at 4:05 PM, Andy Bierman <andy@yumaworks.com> wrote:
>
>
>
>
> On Tue, Feb 11, 2014 at 12:36 PM, Randy Presuhn <
> randy_presuhn@mindspring.com> wrote:
>
>> Hi -
>>
>> > From: "Andy Bierman" <andy@yumaworks.com>
>> > To: "Randy Presuhn" <randy_presuhn@mindspring.com>
>> > Cc: "MIB Doctors (E-mail)" <mib-doctors@ietf.org>
>> > Sent: Tuesday, February 11, 2014 11:44 AM
>> > Subject: Re: [MIB-DOCTORS] Why is this MIB module read-write?
>> ...
>> > We don't need to replay the "What's wrong with SNMP Set?" debate
>> > that we had over a decade ago.
>>
>> Agreed.  That's not the point of my response to Thomas Nadeau's post.
>>
>> >  NETCONF/YANG is not fully deployed,
>> > but there are many vendors shipping it and working on it.
>> > There is more evidence that vendors are willing to adopt NETCONF/YANG
>> > than there is they will adopt SNMP Set.
>>
>> I don't think that point being contended in this discussion.
>> My concern is that Thomas Nadeau's rationale was framed
>> in terms of WG opportunity cost, and that the presumed dichotomy
>> of "expensive configuration MIB module" vs. "free time to do other
>> needed work" is a false one if one admits the third possibility of
>> using Yang to model the configuration data.  The realistic choices
>> are between
>>    - MIB module
>>    - Yang module
>>    - no standardized configuration support
>>
>> I remain to be convinced that standardizing a configuration data
>> model expressed  in Yang is significantly less effort for a *working*
>> *group* than it would be to produce a comparable MIB module,
>> particularly when there are significant interactions or linkages between
>> the configuration data and information visible through the operational
>> MIB module.
>>
>>
> The goal should be to get running code out there.
> If vendors don't implement the RFC, then all the work
> put into the RFC doesn't count for much.
>
> Something is wrong with the process.
> Either vendors are showing great support for read-write
> MIB modules and lying about it, or the WGs are creating these
> MIB modules without caring if they have any industry support.
> I think it is the latter.
>
>
> It's not just vendors to worry about; it's operators to choose to use
> their implementations. I think there is a big difference between running
> and operationally in place code.  There are plenty of read-write
> implementations out there, but almost no one uses them.
>
>
Good point.  Just me being vendor and agent-centric.
It's really about the transaction model, not the MIBs.
Turns out that processing a random set of varbinds and extrapolating
some sort of easy-to-implement transaction model out of it
is not as Simple as the first name would suggest.

Tom
>


Andy


>
>
>
>
>
>
>> As for "no standardized configuration support" - do we really want
>> to stay^H^H^H^H go there?
>>
>> Randy
>>
>
>
> Andy
>
>
>>
>> _______________________________________________
>> 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
>
>

--001a113ab29e1bad2a04f2284422
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 Tue, Feb 11, 2014 at 1:15 PM, Thomas D. Nadeau <span dir=3D"ltr"=
>&lt;<a href=3D"mailto:tnadeau@lucidvision.com" target=3D"_blank">tnadeau@l=
ucidvision.com</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 dir=3D"auto"><div><br></div><div><br>On=
 Feb 11, 2014, at 4:05 PM, Andy Bierman &lt;<a href=3D"mailto:andy@yumawork=
s.com" target=3D"_blank">andy@yumaworks.com</a>&gt; wrote:<br>
<br></div><blockquote type=3D"cite"><div><div dir=3D"ltr"><br><div class=3D=
"gmail_extra"><br><br><div class=3D"gmail_quote">On Tue, Feb 11, 2014 at 12=
:36 PM, Randy Presuhn <span dir=3D"ltr">&lt;<a href=3D"mailto:randy_presuhn=
@mindspring.com" target=3D"_blank">randy_presuhn@mindspring.com</a>&gt;</sp=
an> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Hi -<br>
<br>
&gt; From: &quot;Andy Bierman&quot; &lt;<a href=3D"mailto:andy@yumaworks.co=
m" target=3D"_blank">andy@yumaworks.com</a>&gt;<br>
&gt; To: &quot;Randy Presuhn&quot; &lt;<a href=3D"mailto:randy_presuhn@mind=
spring.com" target=3D"_blank">randy_presuhn@mindspring.com</a>&gt;<br>
&gt; Cc: &quot;MIB Doctors (E-mail)&quot; &lt;<a href=3D"mailto:mib-doctors=
@ietf.org" target=3D"_blank">mib-doctors@ietf.org</a>&gt;<br>
&gt; Sent: Tuesday, February 11, 2014 11:44 AM<br>
&gt; Subject: Re: [MIB-DOCTORS] Why is this MIB module read-write?<br>
...<br>
&gt; We don&#39;t need to replay the &quot;What&#39;s wrong with SNMP Set?&=
quot; debate<br>
&gt; that we had over a decade ago.<br>
<br>
Agreed. =A0That&#39;s not the point of my response to Thomas Nadeau&#39;s p=
ost.<br>
<br>
&gt; =A0NETCONF/YANG is not fully deployed,<br>
&gt; but there are many vendors shipping it and working on it.<br>
&gt; There is more evidence that vendors are willing to adopt NETCONF/YANG<=
br>
&gt; than there is they will adopt SNMP Set.<br>
<br>
I don&#39;t think that point being contended in this discussion.<br>
My concern is that Thomas Nadeau&#39;s rationale was framed<br>
in terms of WG opportunity cost, and that the presumed dichotomy<br>
of &quot;expensive configuration MIB module&quot; vs. &quot;free time to do=
 other<br>
needed work&quot; is a false one if one admits the third possibility of<br>
using Yang to model the configuration data. =A0The realistic choices<br>
are between<br>
=A0 =A0- MIB module<br>
=A0 =A0- Yang module<br>
=A0 =A0- no standardized configuration support<br>
<br>
I remain to be convinced that standardizing a configuration data<br>
model expressed =A0in Yang is significantly less effort for a *working*<br>
*group* than it would be to produce a comparable MIB module,<br>
particularly when there are significant interactions or linkages between<br=
>
the configuration data and information visible through the operational<br>
MIB module.<br>
<br></blockquote><div><br></div><div>The goal should be to get running code=
 out there.</div><div>If vendors don&#39;t implement the RFC, then all the =
work</div><div>put into the RFC doesn&#39;t count for much.</div><div>

<br></div><div>Something is wrong with the process.</div><div>Either vendor=
s are showing great support for read-write</div><div>MIB modules and lying =
about it, or the WGs are creating these</div><div>MIB modules without carin=
g if they have any industry support.</div>

<div>I think it is the latter.</div></div></div></div></div></blockquote><d=
iv><br></div><div>It&#39;s not just vendors to worry about; it&#39;s operat=
ors to choose to use their implementations. I think there is a big differen=
ce between running and operationally in place code. =A0There are plenty of =
read-write implementations out there, but almost no one uses them.</div>
<div><br></div></div></blockquote><div><br></div><div>Good point. =A0Just m=
e being vendor and agent-centric.</div><div>It&#39;s really about the trans=
action model, not the MIBs.</div><div>Turns out that processing a random se=
t of varbinds and extrapolating</div>
<div>some sort of easy-to-implement transaction model out of it</div><div>i=
s not as Simple as the first name would suggest.</div><div><br></div><block=
quote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc=
 solid;padding-left:1ex">
<div dir=3D"auto"><div></div><div>Tom=A0</div></div></blockquote><div><br><=
/div><div><br></div><div>Andy</div><div>=A0</div><blockquote class=3D"gmail=
_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:=
1ex"><div dir=3D"auto">
<div><br></div><br><blockquote type=3D"cite"><div><div dir=3D"ltr"><div cla=
ss=3D"gmail_extra"><div class=3D"gmail_quote"><div><br></div><div><br></div=
><div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex=
;border-left:1px #ccc solid;padding-left:1ex">

As for &quot;no standardized configuration support&quot; - do we really wan=
t<br>
to stay^H^H^H^H go there?<br>
<br>
Randy<br></blockquote><div><br></div><div><br></div><div>Andy</div><div>=A0=
</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-l=
eft:1px #ccc solid;padding-left:1ex">
<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>
</blockquote></div><br></div></div>
</div></blockquote><blockquote type=3D"cite"><div><span>___________________=
____________________________</span><br><span>MIB-DOCTORS mailing list</span=
><br><span><a href=3D"mailto:MIB-DOCTORS@ietf.org" target=3D"_blank">MIB-DO=
CTORS@ietf.org</a></span><br>
<span><a href=3D"https://www.ietf.org/mailman/listinfo/mib-doctors" target=
=3D"_blank">https://www.ietf.org/mailman/listinfo/mib-doctors</a></span><br=
></div></blockquote></div></blockquote></div><br></div></div>

--001a113ab29e1bad2a04f2284422--


From randy_presuhn@mindspring.com  Tue Feb 11 14:20:14 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 4A7DE1A074D for <mib-doctors@ietfa.amsl.com>; Tue, 11 Feb 2014 14:20:14 -0800 (PST)
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 eABrrNNfLNSp for <mib-doctors@ietfa.amsl.com>; Tue, 11 Feb 2014 14:20:11 -0800 (PST)
Received: from elasmtp-junco.atl.sa.earthlink.net (elasmtp-junco.atl.sa.earthlink.net [209.86.89.63]) by ietfa.amsl.com (Postfix) with ESMTP id B67651A0738 for <mib-doctors@ietf.org>; Tue, 11 Feb 2014 14:20:10 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=FEU3l48AfUmqThz4nBwlW1aEDNkaRTRYNg03oztx2zEwTPQvY1l3Dve3HHL0R2vC; h=Received:Message-ID:From:To:References:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:X-MimeOLE:X-ELNK-Trace:X-Originating-IP;
Received: from [76.254.55.183] (helo=oemcomputer) by elasmtp-junco.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <randy_presuhn@mindspring.com>) id 1WDLgW-0005GR-TE for mib-doctors@ietf.org; Tue, 11 Feb 2014 17:20:09 -0500
Message-ID: <006401cf2778$092f7e60$6b01a8c0@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: "MIB Doctors \(E-mail\)" <mib-doctors@ietf.org>
References: <22620850.1392146231683.JavaMail.root@elwamui-milano.atl.sa.earthlink.net> <CABCOCHTq+Zj3pAyT9C=8Bmg_TKEEnP__OW-07MDK==iz63j9XA@mail.gmail.com> <000801cf2768$f4c580a0$6b01a8c0@oemcomputer> <CABCOCHQH7bbBK=7LT7kbKt6ZD4K2TDxfY09n2zboOEv3YD45_w@mail.gmail.com> <771D1B04-2D90-4FD8-A8E8-88840183D020@lucidvision.com> <CABCOCHQ1=WgiSYdYfqLF5iwbVO7xOF=W88CNd1SVUZ+qus=N6Q@mail.gmail.com>
Date: Tue, 11 Feb 2014 14:24:30 -0800
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1478
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478
X-ELNK-Trace: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d88891b749bef7332bbcafbbce5045dd106d7092072db33bcb64350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 76.254.55.183
Subject: Re: [MIB-DOCTORS] Why is this MIB module read-write?
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, 11 Feb 2014 22:20:14 -0000

Hi -

> From: "Andy Bierman" <andy@yumaworks.com>
> To: "Thomas D. Nadeau" <tnadeau@lucidvision.com>
> Cc: "Randy Presuhn" <randy_presuhn@mindspring.com>; "MIB Doctors (E-mail)" <mib-doctors@ietf.org>
> Sent: Tuesday, February 11, 2014 1:37 PM
> Subject: Re: [MIB-DOCTORS] Why is this MIB module read-write?
...
> > It's not just vendors to worry about; it's operators to choose to use
> > their implementations. I think there is a big difference between running
> > and operationally in place code.  There are plenty of read-write
> > implementations out there, but almost no one uses them.
> >
> >
> Good point.  Just me being vendor and agent-centric.
> It's really about the transaction model, not the MIBs.
> Turns out that processing a random set of varbinds and extrapolating
> some sort of easy-to-implement transaction model out of it
> is not as Simple as the first name would suggest.

This is introducing another contention while still
avoiding the core of his argument.  There are two
rather large assertions on which the two of you are
respectively basing your arguments:

  (1) Tom's argument rests on the assumption that a  yang
        module is substantially (I won't hold him to the hyperbole
        of "exponentially") less work for a working group to
        standardize than an operationally equivalent MIB
        module would be.  I find this conceivable but implausible
        in the absence of hard data.

  (2) Andy's argument assumes that the *usage* level of
        fielded Yang modules through Netmod protocol is
        substantially higher than that of comparable MIB
        modules, and that the deciding factor for such
        usage has been the "transaction" model.  Also
        conceivable, but I've seen no hard data to back it up.

Without numbers to back up these assertions underlying the
proposed policy change, it'll quickly start to smell like GOSIP
as an effort to establish momentum by fiat.

Randy


From andy@yumaworks.com  Tue Feb 11 15:17:03 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 A987D1A07C5 for <mib-doctors@ietfa.amsl.com>; Tue, 11 Feb 2014 15:17:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Level: 
X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 kwtGnEQvdB2z for <mib-doctors@ietfa.amsl.com>; Tue, 11 Feb 2014 15:16:58 -0800 (PST)
Received: from mail-qa0-f43.google.com (mail-qa0-f43.google.com [209.85.216.43]) by ietfa.amsl.com (Postfix) with ESMTP id ED29A1A07AC for <mib-doctors@ietf.org>; Tue, 11 Feb 2014 15:16:57 -0800 (PST)
Received: by mail-qa0-f43.google.com with SMTP id o15so12713868qap.16 for <mib-doctors@ietf.org>; Tue, 11 Feb 2014 15:16:57 -0800 (PST)
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=yV7ma7AZoYcVDG9k+b6ly1zqjmd2QMn7XlyZT+7Huv4=; b=iq5tRISzQBgqXd6zyDWVtfEI0JgSdnfIiAXmyfSR99dMm6YqNyHQXvBT6/fd9uUecp /sIqzomKd+UIzUWQFaIBBrGZcLDlz9ZrNzgwpWfv+nikpPUkJjkYYC86d871/Kdvc67m QAWLwNMScKaxhpIBhtu27tSsJXPasBdLvajL2eU8hm7HZlxZqdtlS/nXCp9ywSNbjCnF N7sLfY1bD9HmlsjDLpKlKJqt6EdpNG/ukLAOShgRg3JzMdZ4LgKtCKK4cZ8ie8ePBZYF oEO05iE1P13fZQWkTE/bl5HdPsSwl/9CLcCjOJT+S3QgcuTDz4Ql6B+dTfakrktAPpva yUMw==
X-Gm-Message-State: ALoCoQnl3Ei6/1pXKEeHvLQZ4ZXIXmrDaBj4WuBn5JIX7gfeVjeGv6k4dRJcUGmyj5ua3in6I7eU
MIME-Version: 1.0
X-Received: by 10.224.66.8 with SMTP id l8mr11859944qai.16.1392160615983; Tue, 11 Feb 2014 15:16:55 -0800 (PST)
Received: by 10.140.98.130 with HTTP; Tue, 11 Feb 2014 15:16:55 -0800 (PST)
In-Reply-To: <006401cf2778$092f7e60$6b01a8c0@oemcomputer>
References: <22620850.1392146231683.JavaMail.root@elwamui-milano.atl.sa.earthlink.net> <CABCOCHTq+Zj3pAyT9C=8Bmg_TKEEnP__OW-07MDK==iz63j9XA@mail.gmail.com> <000801cf2768$f4c580a0$6b01a8c0@oemcomputer> <CABCOCHQH7bbBK=7LT7kbKt6ZD4K2TDxfY09n2zboOEv3YD45_w@mail.gmail.com> <771D1B04-2D90-4FD8-A8E8-88840183D020@lucidvision.com> <CABCOCHQ1=WgiSYdYfqLF5iwbVO7xOF=W88CNd1SVUZ+qus=N6Q@mail.gmail.com> <006401cf2778$092f7e60$6b01a8c0@oemcomputer>
Date: Tue, 11 Feb 2014 15:16:55 -0800
Message-ID: <CABCOCHT=um4kPq8b4ksDUOnYjsi5S-2cTkAY7KQA3nFtisRDqw@mail.gmail.com>
From: Andy Bierman <andy@yumaworks.com>
To: Randy Presuhn <randy_presuhn@mindspring.com>
Content-Type: multipart/alternative; boundary=001a11c2c27aff615704f229a61d
Cc: "MIB Doctors \(E-mail\)" <mib-doctors@ietf.org>
Subject: Re: [MIB-DOCTORS] Why is this MIB module read-write?
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, 11 Feb 2014 23:17:03 -0000

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

On Tue, Feb 11, 2014 at 2:24 PM, Randy Presuhn <randy_presuhn@mindspring.com
> wrote:

> Hi -
>
> > From: "Andy Bierman" <andy@yumaworks.com>
> > To: "Thomas D. Nadeau" <tnadeau@lucidvision.com>
> > Cc: "Randy Presuhn" <randy_presuhn@mindspring.com>; "MIB Doctors
> (E-mail)" <mib-doctors@ietf.org>
> > Sent: Tuesday, February 11, 2014 1:37 PM
> > Subject: Re: [MIB-DOCTORS] Why is this MIB module read-write?
> ...
> > > It's not just vendors to worry about; it's operators to choose to use
> > > their implementations. I think there is a big difference between
> running
> > > and operationally in place code.  There are plenty of read-write
> > > implementations out there, but almost no one uses them.
> > >
> > >
> > Good point.  Just me being vendor and agent-centric.
> > It's really about the transaction model, not the MIBs.
> > Turns out that processing a random set of varbinds and extrapolating
> > some sort of easy-to-implement transaction model out of it
> > is not as Simple as the first name would suggest.
>
> This is introducing another contention while still
> avoiding the core of his argument.  There are two
> rather large assertions on which the two of you are
> respectively basing your arguments:
>
>   (1) Tom's argument rests on the assumption that a  yang
>         module is substantially (I won't hold him to the hyperbole
>         of "exponentially") less work for a working group to
>         standardize than an operationally equivalent MIB
>         module would be.  I find this conceivable but implausible
>         in the absence of hard data.
>
>   (2) Andy's argument assumes that the *usage* level of
>         fielded Yang modules through Netmod protocol is
>         substantially higher than that of comparable MIB
>         modules, and that the deciding factor for such
>         usage has been the "transaction" model.  Also
>         conceivable, but I've seen no hard data to back it up.
>
> Without numbers to back up these assertions underlying the
> proposed policy change, it'll quickly start to smell like GOSIP
> as an effort to establish momentum by fiat.
>
>

The jury is not still out on SNMP Set.  There is enough evidence
gathered to declare that SNMP Set is not significantly deployed
for configuration management.  NETCONF/YANG is the standards
track solution the IETF is developing for configuration management.

Time will tell if YANG modules will get significantly deployed with either
NETCONF or RESTCONF.  It is possible that open-source projects
such as OpenDaylight will have much more influence on industry
trends than the IETF MIB Police.


Randy
>

Andy

--001a11c2c27aff615704f229a61d
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 Tue, Feb 11, 2014 at 2:24 PM, Randy Presuhn <span dir=3D"ltr">&l=
t;<a href=3D"mailto:randy_presuhn@mindspring.com" target=3D"_blank">randy_p=
resuhn@mindspring.com</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">Hi -<br>
<br>
&gt; From: &quot;Andy Bierman&quot; &lt;<a href=3D"mailto:andy@yumaworks.co=
m">andy@yumaworks.com</a>&gt;<br>
&gt; To: &quot;Thomas D. Nadeau&quot; &lt;<a href=3D"mailto:tnadeau@lucidvi=
sion.com">tnadeau@lucidvision.com</a>&gt;<br>
&gt; Cc: &quot;Randy Presuhn&quot; &lt;<a href=3D"mailto:randy_presuhn@mind=
spring.com">randy_presuhn@mindspring.com</a>&gt;; &quot;MIB Doctors (E-mail=
)&quot; &lt;<a href=3D"mailto:mib-doctors@ietf.org">mib-doctors@ietf.org</a=
>&gt;<br>

&gt; Sent: Tuesday, February 11, 2014 1:37 PM<br>
&gt; Subject: Re: [MIB-DOCTORS] Why is this MIB module read-write?<br>
...<br>
&gt; &gt; It&#39;s not just vendors to worry about; it&#39;s operators to c=
hoose to use<br>
&gt; &gt; their implementations. I think there is a big difference between =
running<br>
&gt; &gt; and operationally in place code. =A0There are plenty of read-writ=
e<br>
&gt; &gt; implementations out there, but almost no one uses them.<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; Good point. =A0Just me being vendor and agent-centric.<br>
&gt; It&#39;s really about the transaction model, not the MIBs.<br>
&gt; Turns out that processing a random set of varbinds and extrapolating<b=
r>
&gt; some sort of easy-to-implement transaction model out of it<br>
&gt; is not as Simple as the first name would suggest.<br>
<br>
This is introducing another contention while still<br>
avoiding the core of his argument. =A0There are two<br>
rather large assertions on which the two of you are<br>
respectively basing your arguments:<br>
<br>
=A0 (1) Tom&#39;s argument rests on the assumption that a =A0yang<br>
=A0 =A0 =A0 =A0 module is substantially (I won&#39;t hold him to the hyperb=
ole<br>
=A0 =A0 =A0 =A0 of &quot;exponentially&quot;) less work for a working group=
 to<br>
=A0 =A0 =A0 =A0 standardize than an operationally equivalent MIB<br>
=A0 =A0 =A0 =A0 module would be. =A0I find this conceivable but implausible=
<br>
=A0 =A0 =A0 =A0 in the absence of hard data.<br>
<br>
=A0 (2) Andy&#39;s argument assumes that the *usage* level of<br>
=A0 =A0 =A0 =A0 fielded Yang modules through Netmod protocol is<br>
=A0 =A0 =A0 =A0 substantially higher than that of comparable MIB<br>
=A0 =A0 =A0 =A0 modules, and that the deciding factor for such<br>
=A0 =A0 =A0 =A0 usage has been the &quot;transaction&quot; model. =A0Also<b=
r>
=A0 =A0 =A0 =A0 conceivable, but I&#39;ve seen no hard data to back it up.<=
br>
<br>
Without numbers to back up these assertions underlying the<br>
proposed policy change, it&#39;ll quickly start to smell like GOSIP<br>
as an effort to establish momentum by fiat.<br>
<br></blockquote><div><br></div><div><br></div><div>The jury is not still o=
ut on SNMP Set. =A0There is enough evidence</div><div>gathered to declare t=
hat SNMP Set is not significantly deployed</div><div>for configuration mana=
gement. =A0NETCONF/YANG is the standards</div>
<div>track solution the IETF is developing for configuration management.</d=
iv><div><br></div><div>Time will tell if YANG modules will get significantl=
y deployed with either</div><div>NETCONF or RESTCONF. =A0It is possible tha=
t open-source projects</div>
<div>such as OpenDaylight will have much more influence on industry</div><d=
iv>trends than the IETF MIB Police.</div><div><br></div><div><br></div><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #c=
cc solid;padding-left:1ex">

Randy<br></blockquote><div><br></div><div>Andy</div><div>=A0</div></div></d=
iv></div>

--001a11c2c27aff615704f229a61d--


From nobody Thu Feb 13 16:29:12 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 5CA041A0006 for <mib-doctors@ietfa.amsl.com>; Thu, 13 Feb 2014 16:29:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.049
X-Spam-Level: 
X-Spam-Status: No, score=-10.049 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.548, 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 hXeWLFHuDKA4 for <mib-doctors@ietfa.amsl.com>; Thu, 13 Feb 2014 16:29:10 -0800 (PST)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) by ietfa.amsl.com (Postfix) with ESMTP id 04B531A0015 for <mib-doctors@ietf.org>; Thu, 13 Feb 2014 16:29:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=129; q=dns/txt; s=iport; t=1392337742; x=1393547342; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=pQY9/RqgcVcZOnh6Usgs1gdNfPWfh3sMabP+u43nTVo=; b=AEIDmDhRh5xwXjnHfps8OR8KH+j52NbvgOsZArVrMNGlBvwowZ4Gyv4K cqfh5iaQ5i7mnEEF+bi2jaWANcjCW1wH8JBl9Bkr1ou7NMili3UM5khtu 4PgKpiZxzFoBIDAciup18bDYJwmFIsSPASRl65lv6Kzv7n8b1NRGrBlkz I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Aj8HAAhj/VKQ/khR/2dsb2JhbABZgwaNZ6tZhx+BGRZ0giYBAQQ4QAEQCw4TFg8JAwIBAgFFBgEMAQcBAYgByGAXjnkHhDgBA4lIjmSGR4tcg04b
X-IronPort-AV: E=Sophos;i="4.95,841,1384300800";  d="scan'208";a="4378421"
Received: from ams-core-1.cisco.com ([144.254.72.81]) by aer-iport-2.cisco.com with ESMTP; 14 Feb 2014 00:28:45 +0000
Received: from [10.21.124.51] (sjc-vpn6-1075.cisco.com [10.21.124.51]) by ams-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id s1E0ShC4008952; Fri, 14 Feb 2014 00:28:43 GMT
Message-ID: <52FD633A.9070106@cisco.com>
Date: Thu, 13 Feb 2014 16:28:42 -0800
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Thomas Nadeau <tnadeau@lucidvision.com>, Randy Presuhn <randy_presuhn@mindspring.com>
References: <22620850.1392146231683.JavaMail.root@elwamui-milano.atl.sa.earthlink.net> <A901B12A-6A42-4782-B3B0-DB0F0FD41ED4@lucidvision.com>
In-Reply-To: <A901B12A-6A42-4782-B3B0-DB0F0FD41ED4@lucidvision.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/COOWxytPTDhHNU5rCj83xcLy4B4
Cc: "MIB Doctors \(E-mail\)" <mib-doctors@ietf.org>
Subject: Re: [MIB-DOCTORS] Why is this MIB module read-write?
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, 14 Feb 2014 00:29:11 -0000

Dear all,

At this point, I'll be sending our agreed statement to the opsarea.
Thanks for the discussion.

Regards, Benoit


From nobody Fri Feb 14 11:19:02 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 015591A034A for <mib-doctors@ietfa.amsl.com>; Fri, 14 Feb 2014 11:19:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.817
X-Spam-Level: 
X-Spam-Status: No, score=0.817 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_15=0.6, RCVD_IN_BL_SPAMCOP_NET=1.347, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_SORBS_WEB=0.77] 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 UJ-frALielrU for <mib-doctors@ietfa.amsl.com>; Fri, 14 Feb 2014 11:18:57 -0800 (PST)
Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com [62.128.201.248]) by ietfa.amsl.com (Postfix) with ESMTP id CCBA61A02D0 for <mib-doctors@ietf.org>; Fri, 14 Feb 2014 11:18:56 -0800 (PST)
Received: from asmtp1.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id s1EJInW8026960; Fri, 14 Feb 2014 19:18:49 GMT
Received: from 950129200 (108.26.90.92.rev.sfr.net [92.90.26.108]) (authenticated bits=0) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id s1EJIlxQ026954 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 14 Feb 2014 19:18:48 GMT
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Joan Cucchiara'" <jcucchiara@mindspring.com>, "'t.petch'" <ietfc@btconnect.com>, "'Benoit Claise'" <bclaise@cisco.com>, <mib-doctors@ietf.org>
Date: Fri, 14 Feb 2014 19:18:46 -0000
Message-ID: <00b101cf29b9$95d979e0$c18c6da0$@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: Ac8puWG6yYzbe4F1RqCJuUl6Nv5v7g==
Content-Language: en-gb
Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/1MJtK6yAuitjfiekZip_LmSYs_c
Subject: Re: [MIB-DOCTORS] configuration: writable MIB modules versus NETCONF/YANGmodules
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: Fri, 14 Feb 2014 19:19:01 -0000

Hi Joan, 

[Reverting to the MIB Doctor Thread]

I will bow to your far (far, far) superior understanding of MIB-speak.

But I don't understand :-(

A row in a table that has RowStatus can have read-only objects and writeable
objects with Defaults as well as read-create objects.
When you use, for example, CreateAndGo the whole row gets created with
read-create objects as they are Set, with unSet writeable objects defaulting,
and with read-only objects filled with values from the implementation.

When I extend a table, surely I can extend with objects that are all only
read-only?
Furthermore, the whole row in the extension table could be automatically created
when the row in the extended table is created.

What am I missing?
 
Thanks,
Adrian

> -----Original Message-----
> From: OPS-AREA [mailto:ops-area-bounces@ietf.org] On Behalf Of Joan
> Cucchiara
> Sent: 14 February 2014 18:28
> To: 't.petch'; 'Benoit Claise'; ops-area@ietf.org
> Subject: Re: [OPS-AREA] configuration: writable MIB modules versus
> NETCONF/YANGmodules
> 
> Hi Tom,
> 
> As the MIB Dr. on this draft,  I have responded on the MIB Dr. thread that I
> do NOT see a way to make this draft (draft-ietf-mpls-tp-te-mib) read-only.
> This draft contains extension tables for tables in LSR and TE MIBS which are
> created by RowStatus (which is read-create).   Like it or not, RowStatus of
> those MIBs (i.e. LSR and TE MIBs) effect the rows in the extension tables of
> this draft (think the case of row creation or row deletion).   That is an
> SNMP Set operation which effects the draft.
> 
> I believe the statement that Benoit puts forth would allow for such a
> situation as this draft, specifically:
> 
> "... SNMP MIB modules modifying persistent configuration state
>  should only be produced by working groups in cases of clear utility
> and consensus to use SNMP write operations for configuration."
> 
> Perhaps, additional wording, such as "For example, in the case of proposed
> SNMP MIB modules which extend or augment rows that are created by
> configuration in a SNMP MIB module which is already a RFC, the proposed SNNP
> MIB modules will be grandfathered, if the working group finds consensus to
> do so."
> 
> However, I am okay with the statement as written.
> 
> Thanks,
>   -Joan
> 
> 
> -----Original Message-----
> From: OPS-AREA [mailto:ops-area-bounces@ietf.org] On Behalf Of t.petch
> Sent: Friday, February 14, 2014 10:02 AM
> To: Benoit Claise; ops-area@ietf.org
> Subject: Re: [OPS-AREA] configuration: writable MIB modules versus
> NETCONF/YANGmodules
> 
> ----- Original Message -----
> From: "Benoit Claise" <bclaise@cisco.com>
> To: <ops-area@ietf.org>
> Sent: Friday, February 14, 2014 12:39 AM
> > Dear all,
> >
> > We occasionally see read-write MIB module proposals within the IETF.
> > However, the write capabilities of those MIB modules are rarely
> implemented.
> >
> > While discussing this issue with the MIB doctors, we arrive to the
> > conclusion that it's now time to set the direction for future MIB
> > developments within the IETF. Basically, let's not specify read-write
> > MIB modules unless we have a good reason. Read-only MIB modules are
> > still fine though, as SNMP is clearly used for monitoring purposes.
> >
> > Here is the statement we came up with:
> >
> >     The OPS area recommends the use of NETCONF/YANG standards for
> >     configuration. IETF working groups are therefore encouraged to use
> >     the NETCONF/YANG standards for configuration, specifically in new
> >     charters. SNMP MIB modules modifying persistent configuration
> state
> >     should only be produced by working groups in cases of clear
> utility
> >     and consensus to use SNMP write operations for configuration.
> >
> > Ideally, this should become an IESG statement.
> > Your feedback is most welcome.
> 
> You probably know that there is currently a consensus call in progress over
> 
> "Please indicate Support or Oppose for this MIB
> (draft-ietf-mpls-tp-te-mib) to be read-only."
> 
> and I was pleasantly surprised to see opposition, albeit with one opponent
> later changing their mind (perhaps they were sat on from a height:-).  I
> don't see much sign of Netxxxx in the mpls arena but there is a need there
> for configuration, since there need not be a control plane to set things up.
> Perhaps writable MIB modules will still be with us in the distant future in
> some corners of the Internet..
> 
> Ideally, this idea would be fleshed out in an I-D.
> 
> Tom Petch
> 
> > Regards, the MIB doctors & Benoit
> 
> _______________________________________________
> OPS-AREA mailing list
> OPS-AREA@ietf.org
> https://www.ietf.org/mailman/listinfo/ops-area
> 
> 
> -----
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 2014.0.4259 / Virus Database: 3705/7092 - Release Date: 02/14/14
> 
> _______________________________________________
> OPS-AREA mailing list
> OPS-AREA@ietf.org
> https://www.ietf.org/mailman/listinfo/ops-area


From nobody Fri Feb 14 13:48:19 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 574251A0411; Fri, 14 Feb 2014 13:48:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -13.457
X-Spam-Level: 
X-Spam-Status: No, score=-13.457 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DATE_IN_PAST_03_06=1.592, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.548, 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 uSeI0055fUdh; Fri, 14 Feb 2014 13:48:09 -0800 (PST)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) by ietfa.amsl.com (Postfix) with ESMTP id E16311A03A9; Fri, 14 Feb 2014 13:48:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6501; q=dns/txt; s=iport; t=1392414488; x=1393624088; h=message-id:date:from:mime-version:to:subject:references: in-reply-to:content-transfer-encoding; bh=8zY+SX/q93/aCVMGWJJVT46Yu2CLjISVPARZaJ4MlL4=; b=b2m+FoupWoFQ2OjrfKmwG8qh8UbZaknlhm9BZqiVCQdO7QtHL17vSvFu ZyovrKs6oYaliYMzAgGGQc0r0dArgRzMedz7DyspBwKEoBUNxb6AoceaA IvNDuR4WcpzbL1YFcvaZF2yMOJiPnFXXiUK6SF6FjQ8Z6HMHbac8kOnq1 U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AsULAHKO/lKtJV2b/2dsb2JhbABQCSeCX8A+gRgWdIIlAQEBBDg1Cw0ELBYPCQMCAQIBRQYBDAgBAYgByGIXjh4IWoQ4AQOYLIZHi1yDLjuBNQ
X-IronPort-AV: E=Sophos;i="4.95,847,1384300800"; d="scan'208";a="304233676"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by rcdn-iport-6.cisco.com with ESMTP; 14 Feb 2014 21:48:05 +0000
Received: from [10.82.245.17] (rtp-vpn2-1296.cisco.com [10.82.245.17]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id s1ELm1oF017597; Fri, 14 Feb 2014 21:48:02 GMT
Message-ID: <52FE529B.1000602@cisco.com>
Date: Fri, 14 Feb 2014 18:30:03 +0100
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.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: <20140213233357.15870.40506.idtracker@ietfa.amsl.com>
In-Reply-To: <20140213233357.15870.40506.idtracker@ietfa.amsl.com>
X-Forwarded-Message-Id: <20140213233357.15870.40506.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/TMIUlJJi2R_10kBA8Obh7sUXndE
Subject: [MIB-DOCTORS] [IESG-AGENDA-DIST] Summarized Agenda for the 2014-02-20 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: Fri, 14 Feb 2014 21:48:12 -0000

Dear all,

Please find below the agenda of the Feb 20th IESG telechat.
Please send your questions, comments, and concerns before Feb 19th COB.

Thanks and Regards, Benoit.

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

2. Protocol Actions
2.1 WG Submissions
2.1.1 New Items
     
   o draft-ietf-pcp-nat64-prefix64-05  - IETF stream
     Learning NAT64 PREFIX64s using Port Control Protocol (PCP) (Proposed
     Standard)
     Token: Ted Lemon
     IANA Review: IANA OK - Actions Needed
     Consensus: Yes

   o draft-ietf-mmusic-sdp-g723-g729-05  - IETF stream
     Offer/Answer Considerations for G723 Annex A and G729 Annex B
     (Proposed Standard)
     Token: Gonzalo Camarillo
     IANA Review: IANA OK - No Actions Needed
     Consensus: Yes

   o draft-ietf-pcp-description-option-04  - IETF stream
     PCP Description Option (Proposed Standard)
     Token: Ted Lemon
     IANA Review: IANA OK - Actions Needed
     Consensus: Yes

   o draft-ietf-avtext-rtp-duplication-05  - IETF stream
     Duplicating RTP Streams (Proposed Standard)
     Token: Gonzalo Camarillo
     IANA Review: Version Changed - Review Needed
     Consensus: Unknown

   o draft-ietf-pwe3-iccp-13  - IETF stream
     Inter-Chassis Communication Protocol for L2VPN PE Redundancy
     (Proposed Standard)
     Token: Stewart Bryant
     IANA Review: IANA OK - Actions Needed
     Consensus: Yes

   o draft-ietf-dane-registry-acronyms-03  - IETF stream
     Adding acronyms to simplify DANE conversations (Proposed Standard)
     Token: Stephen Farrell
     IANA Review: IANA OK - Actions Needed
     Consensus: Unknown

   o draft-ietf-qresync-rfc5162bis-10  - IETF stream
     IMAP Extensions for Conditional STORE Operation or Quick Flag
     Changes Resynchronization (CONDSTORE) and Quick Mailbox
     Resynchronization (QRESYNC) (Proposed Standard)
     Token: Barry Leiba
     IANA Review: IANA OK - Actions Needed
     Consensus: Yes

   o draft-ietf-manet-olsrv2-rmpr-optimization-00  - IETF stream
     Routing MPR Optimization for the Optimized Link State Routing
     Protocol version 2 (OLSRv2) (Proposed Standard)
     Token: Adrian Farrel
     IANA Review: IANA OK - No Actions Needed
     Consensus: Yes

   o draft-ietf-l2vpn-vpls-mib-14  - IETF stream
     Virtual Private Lan Services (VPLS) Management Information Base
     (Proposed Standard)
     Token: Stewart Bryant
     IANA Review: IANA - Not OK
     Consensus: Unknown
     Last call expires: 2014-02-14

   o draft-ietf-xrblock-rtcp-xr-bytes-discarded-metric-01  - IETF stream
     RTP Control Protocol (RTCP) Extended Report (XR) for Bytes Discarded
     Metric (Proposed Standard)
     Token: Gonzalo Camarillo
     IANA Review: IANA OK - Actions Needed
     Consensus: Unknown

   o draft-ietf-xrblock-rtcp-xr-synchronization-08  - IETF stream
     RTP Control Protocol (RTCP) Extended Report (XR) Blocks for
     Synchronization Delay and Offset Metrics Reporting (Proposed
     Standard)
     Token: Gonzalo Camarillo
     IANA Review: Version Changed - Review Needed
     Consensus: Unknown

2.1.2 Returning Items
     
   o draft-ietf-alto-protocol-25  - IETF stream
     ALTO Protocol (Proposed Standard)
     Token: Spencer Dawkins
     IANA Review: IANA - Not OK
     Consensus: Unknown

2.2 Individual Submissions
2.2.1 New Items

   NONE

2.2.2 Returning Items

   NONE

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-opsec-vpn-leakages-03  - IETF stream
     Virtual Private Network (VPN) traffic leakages in dual-stack hosts/
     networks (Informational)
     Token: Joel Jaeggli
     IANA Review: IANA OK - No Actions Needed
     Consensus: Yes

   o draft-ietf-v6ops-nat64-experience-09  - IETF stream
     NAT64 Operational Experience (Informational)
     Token: Joel Jaeggli
     IANA Review: IANA OK - No Actions Needed
     Consensus: Yes

   o draft-ietf-mpls-forwarding-08  - IETF stream
     MPLS Forwarding Compliance and Performance Requirements
     (Informational)
     Token: Adrian Farrel
     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-allen-dispatch-imei-urn-as-instanceid-12  - IETF stream
     Using the International Mobile station Equipment Identity (IMEI)
     Uniform Resource Name (URN) as an Instance ID (Informational)
     Token: Gonzalo Camarillo
     IANA Review: IANA OK - No Actions Needed
     Consensus: Yes

   o draft-housley-pkix-test-oids-00  - IETF stream
     Object Identifiers for Test Certificate Policies (Informational)
     Token: Sean Turner
     IANA Review: IANA OK - No Actions Needed
     Consensus: Unknown

3.2.2 Returning Items
     
   o draft-montemurro-gsma-imei-urn-19  - IETF stream
     A Uniform Resource Name Namespace for the Global System for Mobile
     communications Association (GSMA) and the International Mobile
     station Equipment Identity (IMEI) (Informational)
     Token: Gonzalo Camarillo
     IANA Review: IANA OK - Actions Needed
     Consensus: Yes

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-saintandre-jabberid-00
     IETF conflict review for draft-saintandre-jabberid
       draft-saintandre-jabberid-12
       The Jabber-ID Header Field (ISE: Informational)
     Token: Pete Resnick

   o conflict-review-irtf-cfrg-ocb-00
     IETF conflict review for draft-irtf-cfrg-ocb
       draft-irtf-cfrg-ocb-07
       The OCB Authenticated-Encryption Algorithm (IRTF: Informational)
     Token: Stephen Farrell

3.4.2 Returning Items

   o conflict-review-irtf-dtnrg-tcp-clayer-00
     IETF conflict review for draft-irtf-dtnrg-tcp-clayer
       draft-irtf-dtnrg-tcp-clayer-08
       Delay Tolerant Networking TCP Convergence Layer Protocol (IRTF:
     Experimental)
     Token: Martin Stiemerling

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

   NONE

4.1.2 Proposed for Approval

   o TURN Revised and Modernized (tram)

4.2 WG Rechartering
4.2.1 Under Evaluation for IETF Review

   NONE

4.2.2 Proposed for Approval

   o Network Configuration (netconf)



From nobody Sun Feb 16 03:55:41 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 158281A03DF for <mib-doctors@ietfa.amsl.com>; Sun, 16 Feb 2014 03:55:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.548
X-Spam-Level: 
X-Spam-Status: No, score=-2.548 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_15=0.6, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.548] 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 oturFZSXbnbA for <mib-doctors@ietfa.amsl.com>; Sun, 16 Feb 2014 03:55:36 -0800 (PST)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by ietfa.amsl.com (Postfix) with ESMTP id 444D61A01A8 for <mib-doctors@ietf.org>; Sun, 16 Feb 2014 03:55:35 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AroHAPmlAFPGmAcV/2dsb2JhbABZgmUhOFe4F4cfgQ8WdIIlAQEBAQMBAQEPKA8lFwQCAQgNBAMBAQELFAkHJwsUCQgBAQQBEggah2MBDJ4Kq2IXjh0zOAaDHoEUBJ8bizSBb4E+gWhC
X-IronPort-AV: E=Sophos;i="4.95,855,1384318800"; d="scan'208";a="43144246"
Received: from unknown (HELO co300216-co-erhwest-exch.avaya.com) ([198.152.7.21]) by de307622-de-outbound.net.avaya.com with ESMTP; 16 Feb 2014 06:55:32 -0500
Received: from unknown (HELO AZ-FFEXHC04.global.avaya.com) ([135.64.58.14]) by co300216-co-erhwest-out.avaya.com with ESMTP/TLS/AES128-SHA; 16 Feb 2014 06:43:41 -0500
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC04.global.avaya.com ([135.64.58.14]) with mapi id 14.03.0174.001; Sun, 16 Feb 2014 12:55:14 +0100
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, 'Joan Cucchiara' <jcucchiara@mindspring.com>, 't.petch' <ietfc@btconnect.com>, 'Benoit Claise' <bclaise@cisco.com>, "mib-doctors@ietf.org" <mib-doctors@ietf.org>
Thread-Topic: [MIB-DOCTORS] configuration: writable MIB modules versus NETCONF/YANGmodules
Thread-Index: Ac8puWG6yYzbe4F1RqCJuUl6Nv5v7gBU9WWQ
Date: Sun, 16 Feb 2014 11:55:14 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA2E4187BC@AZ-FFEXMB04.global.avaya.com>
References: <00b101cf29b9$95d979e0$c18c6da0$@olddog.co.uk>
In-Reply-To: <00b101cf29b9$95d979e0$c18c6da0$@olddog.co.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.64.58.46]
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/9bTQpPELmbOeG-PrtR-12VmBlVI
Subject: Re: [MIB-DOCTORS] configuration: writable MIB modules versus NETCONF/YANGmodules
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: Sun, 16 Feb 2014 11:55:39 -0000

Hi Adrian,

Even if the row you extend is composed only by objects with MAX-ACCESS read=
-only, creating a new row involves a write operation on the object with SYN=
TAX RowStatus.=20

This is (I guess) what Joan meant.=20

Creating a new row may mean a modification of configuration on the managed =
entity. You now have n+1 rows instead of n rows in the table.=20

Regards,

Dan


> -----Original Message-----
> From: MIB-DOCTORS [mailto:mib-doctors-bounces@ietf.org] On Behalf Of
> Adrian Farrel
> Sent: Friday, February 14, 2014 9:19 PM
> To: 'Joan Cucchiara'; 't.petch'; 'Benoit Claise'; mib-doctors@ietf.org
> Subject: Re: [MIB-DOCTORS] configuration: writable MIB modules versus
> NETCONF/YANGmodules
>=20
> Hi Joan,
>=20
> [Reverting to the MIB Doctor Thread]
>=20
> I will bow to your far (far, far) superior understanding of MIB-speak.
>=20
> But I don't understand :-(
>=20
> A row in a table that has RowStatus can have read-only objects and writea=
ble
> objects with Defaults as well as read-create objects.
> When you use, for example, CreateAndGo the whole row gets created with
> read-create objects as they are Set, with unSet writeable objects default=
ing,
> and with read-only objects filled with values from the implementation.
>=20
> When I extend a table, surely I can extend with objects that are all only=
 read-
> only?
> Furthermore, the whole row in the extension table could be automatically
> created when the row in the extended table is created.
>=20
> What am I missing?
>=20
> Thanks,
> Adrian
>=20
> > -----Original Message-----
> > From: OPS-AREA [mailto:ops-area-bounces@ietf.org] On Behalf Of Joan
> > Cucchiara
> > Sent: 14 February 2014 18:28
> > To: 't.petch'; 'Benoit Claise'; ops-area@ietf.org
> > Subject: Re: [OPS-AREA] configuration: writable MIB modules versus
> > NETCONF/YANGmodules
> >
> > Hi Tom,
> >
> > As the MIB Dr. on this draft,  I have responded on the MIB Dr. thread
> > that I do NOT see a way to make this draft (draft-ietf-mpls-tp-te-mib) =
read-
> only.
> > This draft contains extension tables for tables in LSR and TE MIBS whic=
h are
> > created by RowStatus (which is read-create).   Like it or not, RowStatu=
s of
> > those MIBs (i.e. LSR and TE MIBs) effect the rows in the extension tabl=
es of
> > this draft (think the case of row creation or row deletion).   That is =
an
> > SNMP Set operation which effects the draft.
> >
> > I believe the statement that Benoit puts forth would allow for such a
> > situation as this draft, specifically:
> >
> > "... SNMP MIB modules modifying persistent configuration state  should
> > only be produced by working groups in cases of clear utility and
> > consensus to use SNMP write operations for configuration."
> >
> > Perhaps, additional wording, such as "For example, in the case of
> > proposed SNMP MIB modules which extend or augment rows that are
> > created by configuration in a SNMP MIB module which is already a RFC,
> > the proposed SNNP MIB modules will be grandfathered, if the working
> > group finds consensus to do so."
> >
> > However, I am okay with the statement as written.
> >
> > Thanks,
> >   -Joan
> >
> >
> > -----Original Message-----
> > From: OPS-AREA [mailto:ops-area-bounces@ietf.org] On Behalf Of t.petch
> > Sent: Friday, February 14, 2014 10:02 AM
> > To: Benoit Claise; ops-area@ietf.org
> > Subject: Re: [OPS-AREA] configuration: writable MIB modules versus
> > NETCONF/YANGmodules
> >
> > ----- Original Message -----
> > From: "Benoit Claise" <bclaise@cisco.com>
> > To: <ops-area@ietf.org>
> > Sent: Friday, February 14, 2014 12:39 AM
> > > Dear all,
> > >
> > > We occasionally see read-write MIB module proposals within the IETF.
> > > However, the write capabilities of those MIB modules are rarely
> > implemented.
> > >
> > > While discussing this issue with the MIB doctors, we arrive to the
> > > conclusion that it's now time to set the direction for future MIB
> > > developments within the IETF. Basically, let's not specify
> > > read-write MIB modules unless we have a good reason. Read-only MIB
> > > modules are still fine though, as SNMP is clearly used for monitoring
> purposes.
> > >
> > > Here is the statement we came up with:
> > >
> > >     The OPS area recommends the use of NETCONF/YANG standards for
> > >     configuration. IETF working groups are therefore encouraged to us=
e
> > >     the NETCONF/YANG standards for configuration, specifically in new
> > >     charters. SNMP MIB modules modifying persistent configuration
> > state
> > >     should only be produced by working groups in cases of clear
> > utility
> > >     and consensus to use SNMP write operations for configuration.
> > >
> > > Ideally, this should become an IESG statement.
> > > Your feedback is most welcome.
> >
> > You probably know that there is currently a consensus call in progress
> > over
> >
> > "Please indicate Support or Oppose for this MIB
> > (draft-ietf-mpls-tp-te-mib) to be read-only."
> >
> > and I was pleasantly surprised to see opposition, albeit with one
> > opponent later changing their mind (perhaps they were sat on from a
> > height:-).  I don't see much sign of Netxxxx in the mpls arena but
> > there is a need there for configuration, since there need not be a cont=
rol
> plane to set things up.
> > Perhaps writable MIB modules will still be with us in the distant
> > future in some corners of the Internet..
> >
> > Ideally, this idea would be fleshed out in an I-D.
> >
> > Tom Petch
> >
> > > Regards, the MIB doctors & Benoit
> >
> > _______________________________________________
> > OPS-AREA mailing list
> > OPS-AREA@ietf.org
> > https://www.ietf.org/mailman/listinfo/ops-area
> >
> >
> > -----
> > No virus found in this message.
> > Checked by AVG - www.avg.com
> > Version: 2014.0.4259 / Virus Database: 3705/7092 - Release Date:
> > 02/14/14
> >
> > _______________________________________________
> > OPS-AREA mailing list
> > OPS-AREA@ietf.org
> > https://www.ietf.org/mailman/listinfo/ops-area
>=20
> _______________________________________________
> MIB-DOCTORS mailing list
> MIB-DOCTORS@ietf.org
> https://www.ietf.org/mailman/listinfo/mib-doctors


From nobody Sun Feb 16 04:55:25 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 EF3EB1A01C7 for <mib-doctors@ietfa.amsl.com>; Sun, 16 Feb 2014 04:55:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.848
X-Spam-Level: 
X-Spam-Status: No, score=-1.848 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_15=0.6, RP_MATCHES_RCVD=-0.548] 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 jtJlhH_of6_B for <mib-doctors@ietfa.amsl.com>; Sun, 16 Feb 2014 04:55:21 -0800 (PST)
Received: from lucidvision.com (lucidvision.com [72.71.250.34]) by ietfa.amsl.com (Postfix) with ESMTP id 89F641A002B for <mib-doctors@ietf.org>; Sun, 16 Feb 2014 04:55:21 -0800 (PST)
Received: from [192.168.1.110] (static-72-71-250-38.cncdnh.fast04.myfairpoint.net [72.71.250.38]) by lucidvision.com (Postfix) with ESMTP id A7F1726F3BDC; Sun, 16 Feb 2014 07:55:18 -0500 (EST)
References: <00b101cf29b9$95d979e0$c18c6da0$@olddog.co.uk> <9904FB1B0159DA42B0B887B7FA8119CA2E4187BC@AZ-FFEXMB04.global.avaya.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: <9904FB1B0159DA42B0B887B7FA8119CA2E4187BC@AZ-FFEXMB04.global.avaya.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <6D77AF09-01F0-4D8E-B205-87FE325D0AE6@lucidvision.com>
X-Mailer: iPad Mail (11B554a)
From: "Thomas D. Nadeau" <tnadeau@lucidvision.com>
Date: Sun, 16 Feb 2014 07:55:20 -0500
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/eW3w77QTJCRMKqwAqJiOy_kmb50
Cc: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "t.petch" <ietfc@btconnect.com>, "mib-doctors@ietf.org" <mib-doctors@ietf.org>
Subject: Re: [MIB-DOCTORS] configuration: writable MIB modules versus NETCONF/YANGmodules
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: Sun, 16 Feb 2014 12:55:24 -0000

	What you describe here is one of the reasons why it has been pointe=
d out repeatedly (Andy I think) why SNMP is not very good at configuration. =
=20

	--Tom


> On Feb 16, 2014, at 6:55 AM, "Romascanu, Dan (Dan)" <dromasca@avaya.com> w=
rote:
>=20
> Hi Adrian,
>=20
> Even if the row you extend is composed only by objects with MAX-ACCESS rea=
d-only, creating a new row involves a write operation on the object with SYN=
TAX RowStatus.=20
>=20
> This is (I guess) what Joan meant.=20
>=20
> Creating a new row may mean a modification of configuration on the managed=
 entity. You now have n+1 rows instead of n rows in the table.=20
>=20
> Regards,
>=20
> Dan
>=20
>=20
>> -----Original Message-----
>> From: MIB-DOCTORS [mailto:mib-doctors-bounces@ietf.org] On Behalf Of
>> Adrian Farrel
>> Sent: Friday, February 14, 2014 9:19 PM
>> To: 'Joan Cucchiara'; 't.petch'; 'Benoit Claise'; mib-doctors@ietf.org
>> Subject: Re: [MIB-DOCTORS] configuration: writable MIB modules versus
>> NETCONF/YANGmodules
>>=20
>> Hi Joan,
>>=20
>> [Reverting to the MIB Doctor Thread]
>>=20
>> I will bow to your far (far, far) superior understanding of MIB-speak.
>>=20
>> But I don't understand :-(
>>=20
>> A row in a table that has RowStatus can have read-only objects and writea=
ble
>> objects with Defaults as well as read-create objects.
>> When you use, for example, CreateAndGo the whole row gets created with
>> read-create objects as they are Set, with unSet writeable objects default=
ing,
>> and with read-only objects filled with values from the implementation.
>>=20
>> When I extend a table, surely I can extend with objects that are all only=
 read-
>> only?
>> Furthermore, the whole row in the extension table could be automatically
>> created when the row in the extended table is created.
>>=20
>> What am I missing?
>>=20
>> Thanks,
>> Adrian
>>=20
>>> -----Original Message-----
>>> From: OPS-AREA [mailto:ops-area-bounces@ietf.org] On Behalf Of Joan
>>> Cucchiara
>>> Sent: 14 February 2014 18:28
>>> To: 't.petch'; 'Benoit Claise'; ops-area@ietf.org
>>> Subject: Re: [OPS-AREA] configuration: writable MIB modules versus
>>> NETCONF/YANGmodules
>>>=20
>>> Hi Tom,
>>>=20
>>> As the MIB Dr. on this draft,  I have responded on the MIB Dr. thread
>>> that I do NOT see a way to make this draft (draft-ietf-mpls-tp-te-mib) r=
ead-
>> only.
>>> This draft contains extension tables for tables in LSR and TE MIBS which=
 are
>>> created by RowStatus (which is read-create).   Like it or not, RowStatus=
 of
>>> those MIBs (i.e. LSR and TE MIBs) effect the rows in the extension table=
s of
>>> this draft (think the case of row creation or row deletion).   That is a=
n
>>> SNMP Set operation which effects the draft.
>>>=20
>>> I believe the statement that Benoit puts forth would allow for such a
>>> situation as this draft, specifically:
>>>=20
>>> "... SNMP MIB modules modifying persistent configuration state  should
>>> only be produced by working groups in cases of clear utility and
>>> consensus to use SNMP write operations for configuration."
>>>=20
>>> Perhaps, additional wording, such as "For example, in the case of
>>> proposed SNMP MIB modules which extend or augment rows that are
>>> created by configuration in a SNMP MIB module which is already a RFC,
>>> the proposed SNNP MIB modules will be grandfathered, if the working
>>> group finds consensus to do so."
>>>=20
>>> However, I am okay with the statement as written.
>>>=20
>>> Thanks,
>>>  -Joan
>>>=20
>>>=20
>>> -----Original Message-----
>>> From: OPS-AREA [mailto:ops-area-bounces@ietf.org] On Behalf Of t.petch
>>> Sent: Friday, February 14, 2014 10:02 AM
>>> To: Benoit Claise; ops-area@ietf.org
>>> Subject: Re: [OPS-AREA] configuration: writable MIB modules versus
>>> NETCONF/YANGmodules
>>>=20
>>> ----- Original Message -----
>>> From: "Benoit Claise" <bclaise@cisco.com>
>>> To: <ops-area@ietf.org>
>>> Sent: Friday, February 14, 2014 12:39 AM
>>>> Dear all,
>>>>=20
>>>> We occasionally see read-write MIB module proposals within the IETF.
>>>> However, the write capabilities of those MIB modules are rarely
>>> implemented.
>>>>=20
>>>> While discussing this issue with the MIB doctors, we arrive to the
>>>> conclusion that it's now time to set the direction for future MIB
>>>> developments within the IETF. Basically, let's not specify
>>>> read-write MIB modules unless we have a good reason. Read-only MIB
>>>> modules are still fine though, as SNMP is clearly used for monitoring
>> purposes.
>>>>=20
>>>> Here is the statement we came up with:
>>>>=20
>>>>    The OPS area recommends the use of NETCONF/YANG standards for
>>>>    configuration. IETF working groups are therefore encouraged to use
>>>>    the NETCONF/YANG standards for configuration, specifically in new
>>>>    charters. SNMP MIB modules modifying persistent configuration
>>> state
>>>>    should only be produced by working groups in cases of clear
>>> utility
>>>>    and consensus to use SNMP write operations for configuration.
>>>>=20
>>>> Ideally, this should become an IESG statement.
>>>> Your feedback is most welcome.
>>>=20
>>> You probably know that there is currently a consensus call in progress
>>> over
>>>=20
>>> "Please indicate Support or Oppose for this MIB
>>> (draft-ietf-mpls-tp-te-mib) to be read-only."
>>>=20
>>> and I was pleasantly surprised to see opposition, albeit with one
>>> opponent later changing their mind (perhaps they were sat on from a
>>> height:-).  I don't see much sign of Netxxxx in the mpls arena but
>>> there is a need there for configuration, since there need not be a contr=
ol
>> plane to set things up.
>>> Perhaps writable MIB modules will still be with us in the distant
>>> future in some corners of the Internet..
>>>=20
>>> Ideally, this idea would be fleshed out in an I-D.
>>>=20
>>> Tom Petch
>>>=20
>>>> Regards, the MIB doctors & Benoit
>>>=20
>>> _______________________________________________
>>> OPS-AREA mailing list
>>> OPS-AREA@ietf.org
>>> https://www.ietf.org/mailman/listinfo/ops-area
>>>=20
>>>=20
>>> -----
>>> No virus found in this message.
>>> Checked by AVG - www.avg.com
>>> Version: 2014.0.4259 / Virus Database: 3705/7092 - Release Date:
>>> 02/14/14
>>>=20
>>> _______________________________________________
>>> OPS-AREA mailing list
>>> OPS-AREA@ietf.org
>>> https://www.ietf.org/mailman/listinfo/ops-area
>>=20
>> _______________________________________________
>> MIB-DOCTORS mailing list
>> MIB-DOCTORS@ietf.org
>> https://www.ietf.org/mailman/listinfo/mib-doctors
>=20
> _______________________________________________
> MIB-DOCTORS mailing list
> MIB-DOCTORS@ietf.org
> https://www.ietf.org/mailman/listinfo/mib-doctors
>=20


From nobody Sun Feb 16 10:03:04 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 0CDB21A0152 for <mib-doctors@ietfa.amsl.com>; Sun, 16 Feb 2014 10:03:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.817
X-Spam-Level: 
X-Spam-Status: No, score=0.817 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_15=0.6, RCVD_IN_BL_SPAMCOP_NET=1.347, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_SORBS_WEB=0.77] 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 48cHnQ91cTLp for <mib-doctors@ietfa.amsl.com>; Sun, 16 Feb 2014 10:03:00 -0800 (PST)
Received: from asmtp2.iomartmail.com (asmtp2.iomartmail.com [62.128.201.249]) by ietfa.amsl.com (Postfix) with ESMTP id 698C61A0150 for <mib-doctors@ietf.org>; Sun, 16 Feb 2014 10:03:00 -0800 (PST)
Received: from asmtp2.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id s1GI2n4T008639; Sun, 16 Feb 2014 18:02:49 GMT
Received: from 950129200 (108.26.90.92.rev.sfr.net [92.90.26.108]) (authenticated bits=0) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id s1GI2k1o008626 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sun, 16 Feb 2014 18:02:47 GMT
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Romascanu, Dan \(Dan\)'" <dromasca@avaya.com>, "'Joan Cucchiara'" <jcucchiara@mindspring.com>, "'t.petch'" <ietfc@btconnect.com>, "'Benoit Claise'" <bclaise@cisco.com>, <mib-doctors@ietf.org>
References: <00b101cf29b9$95d979e0$c18c6da0$@olddog.co.uk> <9904FB1B0159DA42B0B887B7FA8119CA2E4187BC@AZ-FFEXMB04.global.avaya.com>
In-Reply-To: <9904FB1B0159DA42B0B887B7FA8119CA2E4187BC@AZ-FFEXMB04.global.avaya.com>
Date: Sun, 16 Feb 2014 18:02:45 -0000
Message-ID: <013501cf2b41$4d26a2c0$e773e840$@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: AQHx1En8PKiAdP7k24gVTn+0j3wjJQJqFfaZml+H9iA=
Content-Language: en-gb
Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/xKaJCZeTDHPBbY6N_FrLCAyk6Kg
Subject: Re: [MIB-DOCTORS] configuration: writable MIB modules versus	NETCONF/YANGmodules
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: Sun, 16 Feb 2014 18:03:03 -0000

I'm sorry if I am being thick.

The row in the old table has a RowStatus object which is, of course,
read-create.
The extension table entry has no object with SYNTAX rowStatus, but is created
automatically when the entry in the old table is created.

A

> -----Original Message-----
> From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com]
> Sent: 16 February 2014 11:55
> To: adrian@olddog.co.uk; 'Joan Cucchiara'; 't.petch'; 'Benoit Claise'; mib-
> doctors@ietf.org
> Subject: RE: [MIB-DOCTORS] configuration: writable MIB modules versus
> NETCONF/YANGmodules
> 
> Hi Adrian,
> 
> Even if the row you extend is composed only by objects with MAX-ACCESS read-
> only, creating a new row involves a write operation on the object with SYNTAX
> RowStatus.
> 
> This is (I guess) what Joan meant.
> 
> Creating a new row may mean a modification of configuration on the managed
> entity. You now have n+1 rows instead of n rows in the table.
> 
> Regards,
> 
> Dan
> 
> 
> > -----Original Message-----
> > From: MIB-DOCTORS [mailto:mib-doctors-bounces@ietf.org] On Behalf Of
> > Adrian Farrel
> > Sent: Friday, February 14, 2014 9:19 PM
> > To: 'Joan Cucchiara'; 't.petch'; 'Benoit Claise'; mib-doctors@ietf.org
> > Subject: Re: [MIB-DOCTORS] configuration: writable MIB modules versus
> > NETCONF/YANGmodules
> >
> > Hi Joan,
> >
> > [Reverting to the MIB Doctor Thread]
> >
> > I will bow to your far (far, far) superior understanding of MIB-speak.
> >
> > But I don't understand :-(
> >
> > A row in a table that has RowStatus can have read-only objects and writeable
> > objects with Defaults as well as read-create objects.
> > When you use, for example, CreateAndGo the whole row gets created with
> > read-create objects as they are Set, with unSet writeable objects
defaulting,
> > and with read-only objects filled with values from the implementation.
> >
> > When I extend a table, surely I can extend with objects that are all only
read-
> > only?
> > Furthermore, the whole row in the extension table could be automatically
> > created when the row in the extended table is created.
> >
> > What am I missing?
> >
> > Thanks,
> > Adrian
> >
> > > -----Original Message-----
> > > From: OPS-AREA [mailto:ops-area-bounces@ietf.org] On Behalf Of Joan
> > > Cucchiara
> > > Sent: 14 February 2014 18:28
> > > To: 't.petch'; 'Benoit Claise'; ops-area@ietf.org
> > > Subject: Re: [OPS-AREA] configuration: writable MIB modules versus
> > > NETCONF/YANGmodules
> > >
> > > Hi Tom,
> > >
> > > As the MIB Dr. on this draft,  I have responded on the MIB Dr. thread
> > > that I do NOT see a way to make this draft (draft-ietf-mpls-tp-te-mib)
read-
> > only.
> > > This draft contains extension tables for tables in LSR and TE MIBS which
are
> > > created by RowStatus (which is read-create).   Like it or not, RowStatus
of
> > > those MIBs (i.e. LSR and TE MIBs) effect the rows in the extension tables
of
> > > this draft (think the case of row creation or row deletion).   That is an
> > > SNMP Set operation which effects the draft.
> > >
> > > I believe the statement that Benoit puts forth would allow for such a
> > > situation as this draft, specifically:
> > >
> > > "... SNMP MIB modules modifying persistent configuration state  should
> > > only be produced by working groups in cases of clear utility and
> > > consensus to use SNMP write operations for configuration."
> > >
> > > Perhaps, additional wording, such as "For example, in the case of
> > > proposed SNMP MIB modules which extend or augment rows that are
> > > created by configuration in a SNMP MIB module which is already a RFC,
> > > the proposed SNNP MIB modules will be grandfathered, if the working
> > > group finds consensus to do so."
> > >
> > > However, I am okay with the statement as written.
> > >
> > > Thanks,
> > >   -Joan
> > >
> > >
> > > -----Original Message-----
> > > From: OPS-AREA [mailto:ops-area-bounces@ietf.org] On Behalf Of t.petch
> > > Sent: Friday, February 14, 2014 10:02 AM
> > > To: Benoit Claise; ops-area@ietf.org
> > > Subject: Re: [OPS-AREA] configuration: writable MIB modules versus
> > > NETCONF/YANGmodules
> > >
> > > ----- Original Message -----
> > > From: "Benoit Claise" <bclaise@cisco.com>
> > > To: <ops-area@ietf.org>
> > > Sent: Friday, February 14, 2014 12:39 AM
> > > > Dear all,
> > > >
> > > > We occasionally see read-write MIB module proposals within the IETF.
> > > > However, the write capabilities of those MIB modules are rarely
> > > implemented.
> > > >
> > > > While discussing this issue with the MIB doctors, we arrive to the
> > > > conclusion that it's now time to set the direction for future MIB
> > > > developments within the IETF. Basically, let's not specify
> > > > read-write MIB modules unless we have a good reason. Read-only MIB
> > > > modules are still fine though, as SNMP is clearly used for monitoring
> > purposes.
> > > >
> > > > Here is the statement we came up with:
> > > >
> > > >     The OPS area recommends the use of NETCONF/YANG standards for
> > > >     configuration. IETF working groups are therefore encouraged to use
> > > >     the NETCONF/YANG standards for configuration, specifically in new
> > > >     charters. SNMP MIB modules modifying persistent configuration
> > > state
> > > >     should only be produced by working groups in cases of clear
> > > utility
> > > >     and consensus to use SNMP write operations for configuration.
> > > >
> > > > Ideally, this should become an IESG statement.
> > > > Your feedback is most welcome.
> > >
> > > You probably know that there is currently a consensus call in progress
> > > over
> > >
> > > "Please indicate Support or Oppose for this MIB
> > > (draft-ietf-mpls-tp-te-mib) to be read-only."
> > >
> > > and I was pleasantly surprised to see opposition, albeit with one
> > > opponent later changing their mind (perhaps they were sat on from a
> > > height:-).  I don't see much sign of Netxxxx in the mpls arena but
> > > there is a need there for configuration, since there need not be a control
> > plane to set things up.
> > > Perhaps writable MIB modules will still be with us in the distant
> > > future in some corners of the Internet..
> > >
> > > Ideally, this idea would be fleshed out in an I-D.
> > >
> > > Tom Petch
> > >
> > > > Regards, the MIB doctors & Benoit
> > >
> > > _______________________________________________
> > > OPS-AREA mailing list
> > > OPS-AREA@ietf.org
> > > https://www.ietf.org/mailman/listinfo/ops-area
> > >
> > >
> > > -----
> > > No virus found in this message.
> > > Checked by AVG - www.avg.com
> > > Version: 2014.0.4259 / Virus Database: 3705/7092 - Release Date:
> > > 02/14/14
> > >
> > > _______________________________________________
> > > OPS-AREA mailing list
> > > OPS-AREA@ietf.org
> > > https://www.ietf.org/mailman/listinfo/ops-area
> >
> > _______________________________________________
> > MIB-DOCTORS mailing list
> > MIB-DOCTORS@ietf.org
> > https://www.ietf.org/mailman/listinfo/mib-doctors


From nobody Sun Feb 16 11:45:52 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 651AB1A0282 for <mib-doctors@ietfa.amsl.com>; Sun, 16 Feb 2014 11:45:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.548
X-Spam-Level: 
X-Spam-Status: No, score=-2.548 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_15=0.6, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.548] 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 VHiRagAunMCZ for <mib-doctors@ietfa.amsl.com>; Sun, 16 Feb 2014 11:45:47 -0800 (PST)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by ietfa.amsl.com (Postfix) with ESMTP id 94D771A0276 for <mib-doctors@ietf.org>; Sun, 16 Feb 2014 11:45:46 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AmkHAJUUAVOHCzIm/2dsb2JhbABZgmUhOFe4F4cfgQ8WdIIlAQEBAQMBAQEPKA8lFwQCAQgNBAMBAQELFAkHJwsUCQgCBAESCBqHYwEMnjWraReOHTM4BoMegRQEnxuLNIFvgT6BaEI
X-IronPort-AV: E=Sophos;i="4.95,856,1384318800"; d="scan'208";a="43161019"
Received: from unknown (HELO p-us1-erheast-smtpauth.us1.avaya.com) ([135.11.50.38]) by de307622-de-outbound.net.avaya.com with ESMTP; 16 Feb 2014 14:45:42 -0500
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; 16 Feb 2014 14:32:31 -0500
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; Sun, 16 Feb 2014 14:45:21 -0500
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, 'Joan Cucchiara' <jcucchiara@mindspring.com>, 't.petch' <ietfc@btconnect.com>, 'Benoit Claise' <bclaise@cisco.com>, "mib-doctors@ietf.org" <mib-doctors@ietf.org>
Thread-Topic: [MIB-DOCTORS] configuration: writable MIB modules versus NETCONF/YANGmodules
Thread-Index: AQHx1En8PKiAdP7k24gVTn+0j3wjJQJqFfaZml+H9iCAABk/AA==
Date: Sun, 16 Feb 2014 19:45:20 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA2E41AF25@AZ-FFEXMB04.global.avaya.com>
References: <00b101cf29b9$95d979e0$c18c6da0$@olddog.co.uk> <9904FB1B0159DA42B0B887B7FA8119CA2E4187BC@AZ-FFEXMB04.global.avaya.com> <013501cf2b41$4d26a2c0$e773e840$@olddog.co.uk>
In-Reply-To: <013501cf2b41$4d26a2c0$e773e840$@olddog.co.uk>
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/_eerEr-KjL010SoHyh7vnxzw2pA
Subject: Re: [MIB-DOCTORS] configuration: writable MIB modules versus NETCONF/YANGmodules
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: Sun, 16 Feb 2014 19:45:50 -0000

By using the already existing RowStatus object in the base table the creati=
on of new rows in the base table leads to the creation of new rows in the e=
xtended table. Even if the objects that you defined are all read-only, the =
effect is the same as defining a new table with a RowStatus object.=20

Dan


> -----Original Message-----
> From: Adrian Farrel [mailto:adrian@olddog.co.uk]
> Sent: Sunday, February 16, 2014 8:03 PM
> To: Romascanu, Dan (Dan); 'Joan Cucchiara'; 't.petch'; 'Benoit Claise'; m=
ib-
> doctors@ietf.org
> Subject: RE: [MIB-DOCTORS] configuration: writable MIB modules versus
> NETCONF/YANGmodules
>=20
> I'm sorry if I am being thick.
>=20
> The row in the old table has a RowStatus object which is, of course, read=
-
> create.
> The extension table entry has no object with SYNTAX rowStatus, but is
> created automatically when the entry in the old table is created.
>=20
> A
>=20
> > -----Original Message-----
> > From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com]
> > Sent: 16 February 2014 11:55
> > To: adrian@olddog.co.uk; 'Joan Cucchiara'; 't.petch'; 'Benoit Claise';
> > mib- doctors@ietf.org
> > Subject: RE: [MIB-DOCTORS] configuration: writable MIB modules versus
> > NETCONF/YANGmodules
> >
> > Hi Adrian,
> >
> > Even if the row you extend is composed only by objects with MAX-ACCESS
> > read- only, creating a new row involves a write operation on the
> > object with SYNTAX RowStatus.
> >
> > This is (I guess) what Joan meant.
> >
> > Creating a new row may mean a modification of configuration on the
> > managed entity. You now have n+1 rows instead of n rows in the table.
> >
> > Regards,
> >
> > Dan
> >
> >
> > > -----Original Message-----
> > > From: MIB-DOCTORS [mailto:mib-doctors-bounces@ietf.org] On Behalf
> Of
> > > Adrian Farrel
> > > Sent: Friday, February 14, 2014 9:19 PM
> > > To: 'Joan Cucchiara'; 't.petch'; 'Benoit Claise';
> > > mib-doctors@ietf.org
> > > Subject: Re: [MIB-DOCTORS] configuration: writable MIB modules
> > > versus NETCONF/YANGmodules
> > >
> > > Hi Joan,
> > >
> > > [Reverting to the MIB Doctor Thread]
> > >
> > > I will bow to your far (far, far) superior understanding of MIB-speak=
.
> > >
> > > But I don't understand :-(
> > >
> > > A row in a table that has RowStatus can have read-only objects and
> > > writeable objects with Defaults as well as read-create objects.
> > > When you use, for example, CreateAndGo the whole row gets created
> > > with read-create objects as they are Set, with unSet writeable
> > > objects
> defaulting,
> > > and with read-only objects filled with values from the implementation=
.
> > >
> > > When I extend a table, surely I can extend with objects that are all
> > > only
> read-
> > > only?
> > > Furthermore, the whole row in the extension table could be
> > > automatically created when the row in the extended table is created.
> > >
> > > What am I missing?
> > >
> > > Thanks,
> > > Adrian
> > >
> > > > -----Original Message-----
> > > > From: OPS-AREA [mailto:ops-area-bounces@ietf.org] On Behalf Of
> > > > Joan Cucchiara
> > > > Sent: 14 February 2014 18:28
> > > > To: 't.petch'; 'Benoit Claise'; ops-area@ietf.org
> > > > Subject: Re: [OPS-AREA] configuration: writable MIB modules versus
> > > > NETCONF/YANGmodules
> > > >
> > > > Hi Tom,
> > > >
> > > > As the MIB Dr. on this draft,  I have responded on the MIB Dr.
> > > > thread that I do NOT see a way to make this draft
> > > > (draft-ietf-mpls-tp-te-mib)
> read-
> > > only.
> > > > This draft contains extension tables for tables in LSR and TE MIBS
> > > > which
> are
> > > > created by RowStatus (which is read-create).   Like it or not, RowS=
tatus
> of
> > > > those MIBs (i.e. LSR and TE MIBs) effect the rows in the extension
> > > > tables
> of
> > > > this draft (think the case of row creation or row deletion).   That=
 is an
> > > > SNMP Set operation which effects the draft.
> > > >
> > > > I believe the statement that Benoit puts forth would allow for
> > > > such a situation as this draft, specifically:
> > > >
> > > > "... SNMP MIB modules modifying persistent configuration state
> > > > should only be produced by working groups in cases of clear
> > > > utility and consensus to use SNMP write operations for configuratio=
n."
> > > >
> > > > Perhaps, additional wording, such as "For example, in the case of
> > > > proposed SNMP MIB modules which extend or augment rows that are
> > > > created by configuration in a SNMP MIB module which is already a
> > > > RFC, the proposed SNNP MIB modules will be grandfathered, if the
> > > > working group finds consensus to do so."
> > > >
> > > > However, I am okay with the statement as written.
> > > >
> > > > Thanks,
> > > >   -Joan
> > > >
> > > >
> > > > -----Original Message-----
> > > > From: OPS-AREA [mailto:ops-area-bounces@ietf.org] On Behalf Of
> > > > t.petch
> > > > Sent: Friday, February 14, 2014 10:02 AM
> > > > To: Benoit Claise; ops-area@ietf.org
> > > > Subject: Re: [OPS-AREA] configuration: writable MIB modules versus
> > > > NETCONF/YANGmodules
> > > >
> > > > ----- Original Message -----
> > > > From: "Benoit Claise" <bclaise@cisco.com>
> > > > To: <ops-area@ietf.org>
> > > > Sent: Friday, February 14, 2014 12:39 AM
> > > > > Dear all,
> > > > >
> > > > > We occasionally see read-write MIB module proposals within the IE=
TF.
> > > > > However, the write capabilities of those MIB modules are rarely
> > > > implemented.
> > > > >
> > > > > While discussing this issue with the MIB doctors, we arrive to
> > > > > the conclusion that it's now time to set the direction for
> > > > > future MIB developments within the IETF. Basically, let's not
> > > > > specify read-write MIB modules unless we have a good reason.
> > > > > Read-only MIB modules are still fine though, as SNMP is clearly
> > > > > used for monitoring
> > > purposes.
> > > > >
> > > > > Here is the statement we came up with:
> > > > >
> > > > >     The OPS area recommends the use of NETCONF/YANG standards
> for
> > > > >     configuration. IETF working groups are therefore encouraged t=
o use
> > > > >     the NETCONF/YANG standards for configuration, specifically in=
 new
> > > > >     charters. SNMP MIB modules modifying persistent
> > > > > configuration
> > > > state
> > > > >     should only be produced by working groups in cases of clear
> > > > utility
> > > > >     and consensus to use SNMP write operations for configuration.
> > > > >
> > > > > Ideally, this should become an IESG statement.
> > > > > Your feedback is most welcome.
> > > >
> > > > You probably know that there is currently a consensus call in
> > > > progress over
> > > >
> > > > "Please indicate Support or Oppose for this MIB
> > > > (draft-ietf-mpls-tp-te-mib) to be read-only."
> > > >
> > > > and I was pleasantly surprised to see opposition, albeit with one
> > > > opponent later changing their mind (perhaps they were sat on from
> > > > a height:-).  I don't see much sign of Netxxxx in the mpls arena
> > > > but there is a need there for configuration, since there need not
> > > > be a control
> > > plane to set things up.
> > > > Perhaps writable MIB modules will still be with us in the distant
> > > > future in some corners of the Internet..
> > > >
> > > > Ideally, this idea would be fleshed out in an I-D.
> > > >
> > > > Tom Petch
> > > >
> > > > > Regards, the MIB doctors & Benoit
> > > >
> > > > _______________________________________________
> > > > OPS-AREA mailing list
> > > > OPS-AREA@ietf.org
> > > > https://www.ietf.org/mailman/listinfo/ops-area
> > > >
> > > >
> > > > -----
> > > > No virus found in this message.
> > > > Checked by AVG - www.avg.com
> > > > Version: 2014.0.4259 / Virus Database: 3705/7092 - Release Date:
> > > > 02/14/14
> > > >
> > > > _______________________________________________
> > > > OPS-AREA mailing list
> > > > OPS-AREA@ietf.org
> > > > https://www.ietf.org/mailman/listinfo/ops-area
> > >
> > > _______________________________________________
> > > MIB-DOCTORS mailing list
> > > MIB-DOCTORS@ietf.org
> > > https://www.ietf.org/mailman/listinfo/mib-doctors


From nobody Sun Feb 16 16:11:59 2014
Return-Path: <jcucchiara@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 AE66C1A0168 for <mib-doctors@ietfa.amsl.com>; Sun, 16 Feb 2014 16:11:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.4
X-Spam-Level: 
X-Spam-Status: No, score=-1.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, J_CHICKENPOX_15=0.6, RCVD_IN_DNSWL_NONE=-0.0001] 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 Sh4PYY_1atZB for <mib-doctors@ietfa.amsl.com>; Sun, 16 Feb 2014 16:11:55 -0800 (PST)
Received: from elasmtp-curtail.atl.sa.earthlink.net (elasmtp-curtail.atl.sa.earthlink.net [209.86.89.64]) by ietfa.amsl.com (Postfix) with ESMTP id EF0A91A0024 for <mib-doctors@ietf.org>; Sun, 16 Feb 2014 16:11:54 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=JyL8gmxOTw7EW2Tr0IFMoJpunX49ZcprVsDHUKdQLB725N40nq5fRdOLoyRCGXd4; h=Received:From:To:References:In-Reply-To:Subject:Date:Message-ID:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Mailer:Thread-Index:Content-Language:X-ELNK-Trace:X-Originating-IP;
Received: from [24.41.69.138] (helo=JoanTower) by elasmtp-curtail.atl.sa.earthlink.net with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.67) (envelope-from <jcucchiara@mindspring.com>) id 1WFBoL-0005uO-MA; Sun, 16 Feb 2014 19:11:50 -0500
From: "Joan Cucchiara" <jcucchiara@mindspring.com>
To: <adrian@olddog.co.uk>, "'t.petch'" <ietfc@btconnect.com>, "'Benoit Claise'" <bclaise@cisco.com>, <mib-doctors@ietf.org>
References: <00b101cf29b9$95d979e0$c18c6da0$@olddog.co.uk>
In-Reply-To: <00b101cf29b9$95d979e0$c18c6da0$@olddog.co.uk>
Date: Sun, 16 Feb 2014 19:11:45 -0500
Message-ID: <029901cf2b74$d9d74c00$8d85e400$@mindspring.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQHx1En8PKiAdP7k24gVTn+0j3wjJZpxTEdg
Content-Language: en-us
X-ELNK-Trace: 4d68bbe9cb71969ea344cf2d1a8e60840a9da525759e26544ce1726e5baca336e44065048261df2f7510c956a98deb90350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 24.41.69.138
Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/8T9yKHUlCRn6Hy44HA9BWtIrcGU
Subject: Re: [MIB-DOCTORS] configuration: writable MIB modules versus NETCONF/YANGmodules
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, 17 Feb 2014 00:11:57 -0000

Hi Adrian,

Please see inline below prefaced with JEC >.

-----Original Message-----
From: Adrian Farrel [mailto:adrian@olddog.co.uk] 
Sent: Friday, February 14, 2014 2:19 PM
To: 'Joan Cucchiara'; 't.petch'; 'Benoit Claise'; mib-doctors@ietf.org
Subject: RE: configuration: writable MIB modules versus NETCONF/YANGmodules

Hi Joan, 

[Reverting to the MIB Doctor Thread]

I will bow to your far (far, far) superior understanding of MIB-speak.

But I don't understand :-(

A row in a table that has RowStatus can have read-only objects and writeable
objects with Defaults as well as read-create objects.
When you use, for example, CreateAndGo the whole row gets created with
read-create objects as they are Set, with unSet writeable objects
defaulting, and with read-only objects filled with values from the
implementation.

JEC > But that is kind of beside the point.   The LSR and TE MIBs (rfc3813
and rfc3812, c. 2004) have two conformance statements, Full and Read-only. 
JEC >  Full Conformance allows for configuring with SNMP sets.   So this
discussion is focusing on only the Full Conformance. 
JEC >  The RowStatus objects in the TE and LSR MIB Modules (rfc3813 and
rfc3812) MUST be implemented as having  a MAX-ACCESS of read-create.   In
other words,
JEC > a row can be created or deleted, etc. because the agent processes an
SNMP set request to configure the RowStatus object (i.e. a set is issued 
JEC > for create-and-go, destroy, etc).    

JEC > The point is that RowStatus  creates the row because of an SNMP set
request.  (Certainly rows can be created other ways too.)
JEC >  There is only ONE RowStatus for the entire row, and 
JEC > if that row is extended or AUGMENTed in additional MIB Modules, as in
the case draft-ietf-mpls-tp-te-mib which extends rows in rfc3813 and
rfc3812, 
JEC > then these extended rows are controlled ALSO by that same RowStatus
object which was defined in the TE/LSR MIB Modules.    
JEC > There is only one RowStatus object which controls the entire row, even
if parts
JEC> of the row are in different MIB Modules (as with
draft-ietf-mpls-tp-te-mib).    If you think about the case of deleting a
row, this makes sense.
JEC > If the RowStatus object in the TE MIB is set to "destroy", then the
deletion of the entire row must happen, even if the objects of that row are
in 
JEC > other MIB modules.    

When I extend a table, surely I can extend with objects that are all only
read-only?
Furthermore, the whole row in the extension table could be automatically
created when the row in the extended table is created.

What am I missing?

JEC >  The agent  MUST "configure" (e.g. create the objects,  delete the
objects) in  these extended rows  in this draft because of an SNMP set
request.    
JEC >   I don't see any way around this, without redefining the RowStatus
TC, or rewriting the TE or LSR MIBs or (probably the simplest solution) the 
JEC> co-authors write the draft in such a way as to not extend tables in the
TE and LSR MIBs.

JEC > So to summarize, an SNMP agent that supports this draft MUST support
the SNMP set request for RowStatus for the rows which extend rows in
JEC> the LSR and TE MIBs.   

JEC> Since that is the case, and since this draft is tied to these RFCs that
are 10 years old now,  I don't have an issue 
JEC> with them configuring via SNMP for other objects also (but that is just
my opinion).

Thanks,
  -Joan



Thanks,
Adrian

> -----Original Message-----
> From: OPS-AREA [mailto:ops-area-bounces@ietf.org] On Behalf Of Joan 
> Cucchiara
> Sent: 14 February 2014 18:28
> To: 't.petch'; 'Benoit Claise'; ops-area@ietf.org
> Subject: Re: [OPS-AREA] configuration: writable MIB modules versus 
> NETCONF/YANGmodules
> 
> Hi Tom,
> 
> As the MIB Dr. on this draft,  I have responded on the MIB Dr. thread 
> that I do NOT see a way to make this draft (draft-ietf-mpls-tp-te-mib)
read-only.
> This draft contains extension tables for tables in LSR and TE MIBS which
are
> created by RowStatus (which is read-create).   Like it or not, RowStatus
of
> those MIBs (i.e. LSR and TE MIBs) effect the rows in the extension tables
of
> this draft (think the case of row creation or row deletion).   That is an
> SNMP Set operation which effects the draft.
> 
> I believe the statement that Benoit puts forth would allow for such a 
> situation as this draft, specifically:
> 
> "... SNMP MIB modules modifying persistent configuration state  should 
> only be produced by working groups in cases of clear utility and 
> consensus to use SNMP write operations for configuration."
> 
> Perhaps, additional wording, such as "For example, in the case of 
> proposed SNMP MIB modules which extend or augment rows that are 
> created by configuration in a SNMP MIB module which is already a RFC, 
> the proposed SNNP MIB modules will be grandfathered, if the working 
> group finds consensus to do so."
> 
> However, I am okay with the statement as written.
> 
> Thanks,
>   -Joan
> 
> 
> -----Original Message-----
> From: OPS-AREA [mailto:ops-area-bounces@ietf.org] On Behalf Of t.petch
> Sent: Friday, February 14, 2014 10:02 AM
> To: Benoit Claise; ops-area@ietf.org
> Subject: Re: [OPS-AREA] configuration: writable MIB modules versus 
> NETCONF/YANGmodules
> 
> ----- Original Message -----
> From: "Benoit Claise" <bclaise@cisco.com>
> To: <ops-area@ietf.org>
> Sent: Friday, February 14, 2014 12:39 AM
> > Dear all,
> >
> > We occasionally see read-write MIB module proposals within the IETF.
> > However, the write capabilities of those MIB modules are rarely
> implemented.
> >
> > While discussing this issue with the MIB doctors, we arrive to the 
> > conclusion that it's now time to set the direction for future MIB 
> > developments within the IETF. Basically, let's not specify 
> > read-write MIB modules unless we have a good reason. Read-only MIB 
> > modules are still fine though, as SNMP is clearly used for monitoring
purposes.
> >
> > Here is the statement we came up with:
> >
> >     The OPS area recommends the use of NETCONF/YANG standards for
> >     configuration. IETF working groups are therefore encouraged to use
> >     the NETCONF/YANG standards for configuration, specifically in new
> >     charters. SNMP MIB modules modifying persistent configuration
> state
> >     should only be produced by working groups in cases of clear
> utility
> >     and consensus to use SNMP write operations for configuration.
> >
> > Ideally, this should become an IESG statement.
> > Your feedback is most welcome.
> 
> You probably know that there is currently a consensus call in progress 
> over
> 
> "Please indicate Support or Oppose for this MIB
> (draft-ietf-mpls-tp-te-mib) to be read-only."
> 
> and I was pleasantly surprised to see opposition, albeit with one 
> opponent later changing their mind (perhaps they were sat on from a 
> height:-).  I don't see much sign of Netxxxx in the mpls arena but 
> there is a need there for configuration, since there need not be a control
plane to set things up.
> Perhaps writable MIB modules will still be with us in the distant 
> future in some corners of the Internet..
> 
> Ideally, this idea would be fleshed out in an I-D.
> 
> Tom Petch
> 
> > Regards, the MIB doctors & Benoit
> 
> _______________________________________________
> OPS-AREA mailing list
> OPS-AREA@ietf.org
> https://www.ietf.org/mailman/listinfo/ops-area
> 
> 
> -----
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 2014.0.4259 / Virus Database: 3705/7092 - Release Date: 
> 02/14/14
> 
> _______________________________________________
> OPS-AREA mailing list
> OPS-AREA@ietf.org
> https://www.ietf.org/mailman/listinfo/ops-area



-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2014.0.4259 / Virus Database: 3705/7092 - Release Date: 02/14/14


From nobody Sun Feb 16 17:28:39 2014
Return-Path: <jcucchiara@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 0AF1D1A0424 for <mib-doctors@ietfa.amsl.com>; Sun, 16 Feb 2014 17:28:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.4
X-Spam-Level: 
X-Spam-Status: No, score=-1.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, J_CHICKENPOX_15=0.6, RCVD_IN_DNSWL_NONE=-0.0001] 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 JWxw061flvQP for <mib-doctors@ietfa.amsl.com>; Sun, 16 Feb 2014 17:28:36 -0800 (PST)
Received: from elasmtp-masked.atl.sa.earthlink.net (elasmtp-masked.atl.sa.earthlink.net [209.86.89.68]) by ietfa.amsl.com (Postfix) with ESMTP id 1EA6A1A0317 for <mib-doctors@ietf.org>; Sun, 16 Feb 2014 17:28:35 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=Q791iQHveQmaKYAbY6MPA8oZJSboBWxu8cHLNZDukRDj63sAwhzgk0SaLbbjKLR1; h=Received:From:To:References:In-Reply-To:Subject:Date:Message-ID:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Mailer:Thread-Index:Content-Language:X-ELNK-Trace:X-Originating-IP;
Received: from [24.41.69.138] (helo=JoanTower) by elasmtp-masked.atl.sa.earthlink.net with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.67) (envelope-from <jcucchiara@mindspring.com>) id 1WFD0W-0007a4-AZ; Sun, 16 Feb 2014 20:28:29 -0500
From: "Joan Cucchiara" <jcucchiara@mindspring.com>
To: <adrian@olddog.co.uk>, "'Romascanu, Dan \(Dan\)'" <dromasca@avaya.com>, "'t.petch'" <ietfc@btconnect.com>, "'Benoit Claise'" <bclaise@cisco.com>, <mib-doctors@ietf.org>
References: <00b101cf29b9$95d979e0$c18c6da0$@olddog.co.uk> <9904FB1B0159DA42B0B887B7FA8119CA2E4187BC@AZ-FFEXMB04.global.avaya.com> <013501cf2b41$4d26a2c0$e773e840$@olddog.co.uk>
In-Reply-To: <013501cf2b41$4d26a2c0$e773e840$@olddog.co.uk>
Date: Sun, 16 Feb 2014 20:28:24 -0500
Message-ID: <029a01cf2b7f$8ece00e0$ac6a02a0$@mindspring.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQHx1En8PKiAdP7k24gVTn+0j3wjJQJqFfaZAelUtmaaUKf1wA==
Content-Language: en-us
X-ELNK-Trace: 4d68bbe9cb71969ea344cf2d1a8e60840a9da525759e26544f62d1531aa9a502ba49ebd14cacd124379a5ba0fa6c7c04350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 24.41.69.138
Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/36V1kMMt3aqoIGQGePAdb6ip4oc
Subject: Re: [MIB-DOCTORS] configuration: writable MIB modules versus	NETCONF/YANGmodules
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, 17 Feb 2014 01:28:39 -0000

Hi Adrian,

Yes.  Dan has correctly stated what I was trying to say.

The concept of a row is such that objects of a single row can be defined in
one or more MIB Modules.   For example,  Row A has 10 objects (one of them
being RowStatus).   5 objects (including the RowStatus object) are defined
in MIB-A and the other 5 are defined in draft-ietf-mpls-te-tp-mib.     

The managed entity which supports the draft, MUST be able to
create/delete/etc.  ALL the objects in  a row due to an SNMP set request to
RowStatus. 
The Row is an concept unto itself, and this row is impacted by SNMP sets to
RowStatus.   

If the goal (as I understand it) is to make this  draft read-only to prevent
configuration via SNMP sets, then that won't be the case with this draft
even if all the objects are made read-only.    Just the nature of Row and
RowStatus and Full Conformance.   In other words, the managed entity still
needs to create/delete all the objects in the row. This will be the same
managed entity that MUST support SNMP set requests to RowStatus, so the goal
of eliminating the processing of SNMP sets is not possible because of
RowStatus (or so I think).

Again, if you think about the deletion of a row, this makes sense.   You
don't want to delete only parts of a row, otherwise, the MIB tables would
end up with a partial rows that were not very helpful.  The entire row is
deleted.  It doesn't matter that the some of the objects in the row are
defined in MIB-A and some 
of the objects are defined in Draft-ietf-mpls-te-tp-mib.   The entire row is
deleted and there is one managed entity responsible for that.   

Thanks,
  -Joan


-----Original Message-----
From: Adrian Farrel [mailto:adrian@olddog.co.uk] 
Sent: Sunday, February 16, 2014 1:03 PM
To: 'Romascanu, Dan (Dan)'; 'Joan Cucchiara'; 't.petch'; 'Benoit Claise';
mib-doctors@ietf.org
Subject: RE: [MIB-DOCTORS] configuration: writable MIB modules versus
NETCONF/YANGmodules

I'm sorry if I am being thick.

The row in the old table has a RowStatus object which is, of course,
read-create.
The extension table entry has no object with SYNTAX rowStatus, but is
created automatically when the entry in the old table is created.

A

> -----Original Message-----
> From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com]
> Sent: 16 February 2014 11:55
> To: adrian@olddog.co.uk; 'Joan Cucchiara'; 't.petch'; 'Benoit Claise'; 
> mib- doctors@ietf.org
> Subject: RE: [MIB-DOCTORS] configuration: writable MIB modules versus 
> NETCONF/YANGmodules
> 
> Hi Adrian,
> 
> Even if the row you extend is composed only by objects with MAX-ACCESS 
> read- only, creating a new row involves a write operation on the 
> object with SYNTAX RowStatus.
> 
> This is (I guess) what Joan meant.
> 
> Creating a new row may mean a modification of configuration on the 
> managed entity. You now have n+1 rows instead of n rows in the table.
> 
> Regards,
> 
> Dan
> 
> 
> > -----Original Message-----
> > From: MIB-DOCTORS [mailto:mib-doctors-bounces@ietf.org] On Behalf Of 
> > Adrian Farrel
> > Sent: Friday, February 14, 2014 9:19 PM
> > To: 'Joan Cucchiara'; 't.petch'; 'Benoit Claise'; 
> > mib-doctors@ietf.org
> > Subject: Re: [MIB-DOCTORS] configuration: writable MIB modules 
> > versus NETCONF/YANGmodules
> >
> > Hi Joan,
> >
> > [Reverting to the MIB Doctor Thread]
> >
> > I will bow to your far (far, far) superior understanding of MIB-speak.
> >
> > But I don't understand :-(
> >
> > A row in a table that has RowStatus can have read-only objects and 
> > writeable objects with Defaults as well as read-create objects.
> > When you use, for example, CreateAndGo the whole row gets created 
> > with read-create objects as they are Set, with unSet writeable 
> > objects
defaulting,
> > and with read-only objects filled with values from the implementation.
> >
> > When I extend a table, surely I can extend with objects that are all 
> > only
read-
> > only?
> > Furthermore, the whole row in the extension table could be 
> > automatically created when the row in the extended table is created.
> >
> > What am I missing?
> >
> > Thanks,
> > Adrian
> >
> > > -----Original Message-----
> > > From: OPS-AREA [mailto:ops-area-bounces@ietf.org] On Behalf Of 
> > > Joan Cucchiara
> > > Sent: 14 February 2014 18:28
> > > To: 't.petch'; 'Benoit Claise'; ops-area@ietf.org
> > > Subject: Re: [OPS-AREA] configuration: writable MIB modules versus 
> > > NETCONF/YANGmodules
> > >
> > > Hi Tom,
> > >
> > > As the MIB Dr. on this draft,  I have responded on the MIB Dr. 
> > > thread that I do NOT see a way to make this draft 
> > > (draft-ietf-mpls-tp-te-mib)
read-
> > only.
> > > This draft contains extension tables for tables in LSR and TE MIBS 
> > > which
are
> > > created by RowStatus (which is read-create).   Like it or not,
RowStatus
of
> > > those MIBs (i.e. LSR and TE MIBs) effect the rows in the extension 
> > > tables
of
> > > this draft (think the case of row creation or row deletion).   That is
an
> > > SNMP Set operation which effects the draft.
> > >
> > > I believe the statement that Benoit puts forth would allow for 
> > > such a situation as this draft, specifically:
> > >
> > > "... SNMP MIB modules modifying persistent configuration state  
> > > should only be produced by working groups in cases of clear 
> > > utility and consensus to use SNMP write operations for configuration."
> > >
> > > Perhaps, additional wording, such as "For example, in the case of 
> > > proposed SNMP MIB modules which extend or augment rows that are 
> > > created by configuration in a SNMP MIB module which is already a 
> > > RFC, the proposed SNNP MIB modules will be grandfathered, if the 
> > > working group finds consensus to do so."
> > >
> > > However, I am okay with the statement as written.
> > >
> > > Thanks,
> > >   -Joan
> > >
> > >
> > > -----Original Message-----
> > > From: OPS-AREA [mailto:ops-area-bounces@ietf.org] On Behalf Of 
> > > t.petch
> > > Sent: Friday, February 14, 2014 10:02 AM
> > > To: Benoit Claise; ops-area@ietf.org
> > > Subject: Re: [OPS-AREA] configuration: writable MIB modules versus 
> > > NETCONF/YANGmodules
> > >
> > > ----- Original Message -----
> > > From: "Benoit Claise" <bclaise@cisco.com>
> > > To: <ops-area@ietf.org>
> > > Sent: Friday, February 14, 2014 12:39 AM
> > > > Dear all,
> > > >
> > > > We occasionally see read-write MIB module proposals within the IETF.
> > > > However, the write capabilities of those MIB modules are rarely
> > > implemented.
> > > >
> > > > While discussing this issue with the MIB doctors, we arrive to 
> > > > the conclusion that it's now time to set the direction for 
> > > > future MIB developments within the IETF. Basically, let's not 
> > > > specify read-write MIB modules unless we have a good reason. 
> > > > Read-only MIB modules are still fine though, as SNMP is clearly 
> > > > used for monitoring
> > purposes.
> > > >
> > > > Here is the statement we came up with:
> > > >
> > > >     The OPS area recommends the use of NETCONF/YANG standards for
> > > >     configuration. IETF working groups are therefore encouraged to
use
> > > >     the NETCONF/YANG standards for configuration, specifically in
new
> > > >     charters. SNMP MIB modules modifying persistent 
> > > > configuration
> > > state
> > > >     should only be produced by working groups in cases of clear
> > > utility
> > > >     and consensus to use SNMP write operations for configuration.
> > > >
> > > > Ideally, this should become an IESG statement.
> > > > Your feedback is most welcome.
> > >
> > > You probably know that there is currently a consensus call in 
> > > progress over
> > >
> > > "Please indicate Support or Oppose for this MIB
> > > (draft-ietf-mpls-tp-te-mib) to be read-only."
> > >
> > > and I was pleasantly surprised to see opposition, albeit with one 
> > > opponent later changing their mind (perhaps they were sat on from 
> > > a height:-).  I don't see much sign of Netxxxx in the mpls arena 
> > > but there is a need there for configuration, since there need not 
> > > be a control
> > plane to set things up.
> > > Perhaps writable MIB modules will still be with us in the distant 
> > > future in some corners of the Internet..
> > >
> > > Ideally, this idea would be fleshed out in an I-D.
> > >
> > > Tom Petch
> > >
> > > > Regards, the MIB doctors & Benoit
> > >
> > > _______________________________________________
> > > OPS-AREA mailing list
> > > OPS-AREA@ietf.org
> > > https://www.ietf.org/mailman/listinfo/ops-area
> > >
> > >
> > > -----
> > > No virus found in this message.
> > > Checked by AVG - www.avg.com
> > > Version: 2014.0.4259 / Virus Database: 3705/7092 - Release Date:
> > > 02/14/14
> > >
> > > _______________________________________________
> > > OPS-AREA mailing list
> > > OPS-AREA@ietf.org
> > > https://www.ietf.org/mailman/listinfo/ops-area
> >
> > _______________________________________________
> > MIB-DOCTORS mailing list
> > MIB-DOCTORS@ietf.org
> > https://www.ietf.org/mailman/listinfo/mib-doctors



-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2014.0.4259 / Virus Database: 3705/7097 - Release Date: 02/16/14


From nobody Sun Feb 16 18:06:26 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 6B2971A02E3 for <mib-doctors@ietfa.amsl.com>; Sun, 16 Feb 2014 18:06:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.678
X-Spam-Level: 
X-Spam-Status: No, score=-0.678 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, J_CHICKENPOX_15=0.6, 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 T3A0ikyOPXqC for <mib-doctors@ietfa.amsl.com>; Sun, 16 Feb 2014 18:06:22 -0800 (PST)
Received: from mail-qg0-f51.google.com (mail-qg0-f51.google.com [209.85.192.51]) by ietfa.amsl.com (Postfix) with ESMTP id 809AF1A0304 for <mib-doctors@ietf.org>; Sun, 16 Feb 2014 18:06:21 -0800 (PST)
Received: by mail-qg0-f51.google.com with SMTP id q108so4165164qgd.10 for <mib-doctors@ietf.org>; Sun, 16 Feb 2014 18:06:19 -0800 (PST)
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=D5xbV5sK2MAFvI1ejVKyUfGXXmOgapenszcBfJzL2nQ=; b=N2/GjdKlSt56vWbATjJ5Yw+o/3A1UkfeiLkxClSHNQzHtY7e7EbpG5mTmiCim6jfNC wiPZaQSJ4lUabizlZeNTPYzCVaRy0QPsBa1JjfkcSFF0wIV9CaNRpg+lWXB7nWlus+Rn MWBoKU6BdAA88QHmJwKzStKzSJB38hPL+dIZv+3TmQml6egchXDOdaohjm5kYEtze5iL 6p/W0+ehaAMCa8WmmqxG4nao891AEmoOVL8sXe3OPUY4C9/6SRqvJpk4YKW/fHkKY5BT 2sZeemh56QFcTSQAOC0pDVQMGLiUljr/Mtv2mhYFGxAOrMZNQ4v7MfLb2wb1XdPEJ3KT AZSA==
X-Gm-Message-State: ALoCoQkpUr/n3WvcBTCxaZZI4MGj0QINikP/NViTf/td8FsDS7o5C2poiQTP+CY1E/4SREP0dmG1
MIME-Version: 1.0
X-Received: by 10.224.60.131 with SMTP id p3mr31453629qah.27.1392602778961; Sun, 16 Feb 2014 18:06:18 -0800 (PST)
Received: by 10.140.98.130 with HTTP; Sun, 16 Feb 2014 18:06:18 -0800 (PST)
In-Reply-To: <029901cf2b74$d9d74c00$8d85e400$@mindspring.com>
References: <00b101cf29b9$95d979e0$c18c6da0$@olddog.co.uk> <029901cf2b74$d9d74c00$8d85e400$@mindspring.com>
Date: Sun, 16 Feb 2014 18:06:18 -0800
Message-ID: <CABCOCHTScmkGNTtEUcnYWBMJ3Pp1CLwG+1QmBaFOmJYPX64UYQ@mail.gmail.com>
From: Andy Bierman <andy@yumaworks.com>
To: Joan Cucchiara <jcucchiara@mindspring.com>
Content-Type: multipart/alternative; boundary=001a1132e004f41a0804f2909965
Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/6rTInbASi6NxHXEs0s1X5QbliMU
Cc: Adrian Farrel <adrian@olddog.co.uk>, "t.petch" <ietfc@btconnect.com>, "MIB Doctors \(E-mail\)" <mib-doctors@ietf.org>
Subject: Re: [MIB-DOCTORS] configuration: writable MIB modules versus NETCONF/YANGmodules
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, 17 Feb 2014 02:06:25 -0000

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

Hi,

I guess I am confused as well, although I don't claim to know the details
;-)

Looking at RFC 3812, there are 2 conformance statements:

    mplsTeModuleFullCompliance
    mplsTeModuleReadOnlyCompliance

If an agent supports the "ReadOnly" MODULE-COMPLIANCE, then the RowStatus

object is implemented read-only, hard-wired to active (i.e., the agent
just populates

the read-only table with the entries via some external configuration).



         OBJECT      mplsTunnelRowStatus
         SYNTAX      RowStatus { active(1) }
         MIN-ACCESS  read-only
         DESCRIPTION "Write access is not required."

Why can't new objects added to the row also allow the server to only claim
conformance to the read-only MODULE-COMPLIANCE?  I don't see the
connection between RowStatus and a developer selecting which
compliance level it will support in an implementation.

It does not matter if the new objects are read-only or read-create.
A "read-only" agent will magically instantiate the new columns,
if it supports the extension. A "read-create" agent will allow
a manager to create new rows, and allow the new r/c columns if
it supports the extension.


Andy




On Sun, Feb 16, 2014 at 4:11 PM, Joan Cucchiara
<jcucchiara@mindspring.com>wrote:

> Hi Adrian,
>
> Please see inline below prefaced with JEC >.
>
> -----Original Message-----
> From: Adrian Farrel [mailto:adrian@olddog.co.uk]
> Sent: Friday, February 14, 2014 2:19 PM
> To: 'Joan Cucchiara'; 't.petch'; 'Benoit Claise'; mib-doctors@ietf.org
> Subject: RE: configuration: writable MIB modules versus NETCONF/YANGmodules
>
> Hi Joan,
>
> [Reverting to the MIB Doctor Thread]
>
> I will bow to your far (far, far) superior understanding of MIB-speak.
>
> But I don't understand :-(
>
> A row in a table that has RowStatus can have read-only objects and
> writeable
> objects with Defaults as well as read-create objects.
> When you use, for example, CreateAndGo the whole row gets created with
> read-create objects as they are Set, with unSet writeable objects
> defaulting, and with read-only objects filled with values from the
> implementation.
>
> JEC > But that is kind of beside the point.   The LSR and TE MIBs (rfc3813
> and rfc3812, c. 2004) have two conformance statements, Full and Read-only.
> JEC >  Full Conformance allows for configuring with SNMP sets.   So this
> discussion is focusing on only the Full Conformance.
> JEC >  The RowStatus objects in the TE and LSR MIB Modules (rfc3813 and
> rfc3812) MUST be implemented as having  a MAX-ACCESS of read-create.   In
> other words,
> JEC > a row can be created or deleted, etc. because the agent processes an
> SNMP set request to configure the RowStatus object (i.e. a set is issued
> JEC > for create-and-go, destroy, etc).
>
> JEC > The point is that RowStatus  creates the row because of an SNMP set
> request.  (Certainly rows can be created other ways too.)
> JEC >  There is only ONE RowStatus for the entire row, and
> JEC > if that row is extended or AUGMENTed in additional MIB Modules, as in
> the case draft-ietf-mpls-tp-te-mib which extends rows in rfc3813 and
> rfc3812,
> JEC > then these extended rows are controlled ALSO by that same RowStatus
> object which was defined in the TE/LSR MIB Modules.
> JEC > There is only one RowStatus object which controls the entire row,
> even
> if parts
> JEC> of the row are in different MIB Modules (as with
> draft-ietf-mpls-tp-te-mib).    If you think about the case of deleting a
> row, this makes sense.
> JEC > If the RowStatus object in the TE MIB is set to "destroy", then the
> deletion of the entire row must happen, even if the objects of that row are
> in
> JEC > other MIB modules.
>
> When I extend a table, surely I can extend with objects that are all only
> read-only?
> Furthermore, the whole row in the extension table could be automatically
> created when the row in the extended table is created.
>
> What am I missing?
>
> JEC >  The agent  MUST "configure" (e.g. create the objects,  delete the
> objects) in  these extended rows  in this draft because of an SNMP set
> request.
> JEC >   I don't see any way around this, without redefining the RowStatus
> TC, or rewriting the TE or LSR MIBs or (probably the simplest solution) the
> JEC> co-authors write the draft in such a way as to not extend tables in
> the
> TE and LSR MIBs.
>
> JEC > So to summarize, an SNMP agent that supports this draft MUST support
> the SNMP set request for RowStatus for the rows which extend rows in
> JEC> the LSR and TE MIBs.
>
> JEC> Since that is the case, and since this draft is tied to these RFCs
> that
> are 10 years old now,  I don't have an issue
> JEC> with them configuring via SNMP for other objects also (but that is
> just
> my opinion).
>
> Thanks,
>   -Joan
>
>
>
> Thanks,
> Adrian
>
> > -----Original Message-----
> > From: OPS-AREA [mailto:ops-area-bounces@ietf.org] On Behalf Of Joan
> > Cucchiara
> > Sent: 14 February 2014 18:28
> > To: 't.petch'; 'Benoit Claise'; ops-area@ietf.org
> > Subject: Re: [OPS-AREA] configuration: writable MIB modules versus
> > NETCONF/YANGmodules
> >
> > Hi Tom,
> >
> > As the MIB Dr. on this draft,  I have responded on the MIB Dr. thread
> > that I do NOT see a way to make this draft (draft-ietf-mpls-tp-te-mib)
> read-only.
> > This draft contains extension tables for tables in LSR and TE MIBS which
> are
> > created by RowStatus (which is read-create).   Like it or not, RowStatus
> of
> > those MIBs (i.e. LSR and TE MIBs) effect the rows in the extension tables
> of
> > this draft (think the case of row creation or row deletion).   That is an
> > SNMP Set operation which effects the draft.
> >
> > I believe the statement that Benoit puts forth would allow for such a
> > situation as this draft, specifically:
> >
> > "... SNMP MIB modules modifying persistent configuration state  should
> > only be produced by working groups in cases of clear utility and
> > consensus to use SNMP write operations for configuration."
> >
> > Perhaps, additional wording, such as "For example, in the case of
> > proposed SNMP MIB modules which extend or augment rows that are
> > created by configuration in a SNMP MIB module which is already a RFC,
> > the proposed SNNP MIB modules will be grandfathered, if the working
> > group finds consensus to do so."
> >
> > However, I am okay with the statement as written.
> >
> > Thanks,
> >   -Joan
> >
> >
> > -----Original Message-----
> > From: OPS-AREA [mailto:ops-area-bounces@ietf.org] On Behalf Of t.petch
> > Sent: Friday, February 14, 2014 10:02 AM
> > To: Benoit Claise; ops-area@ietf.org
> > Subject: Re: [OPS-AREA] configuration: writable MIB modules versus
> > NETCONF/YANGmodules
> >
> > ----- Original Message -----
> > From: "Benoit Claise" <bclaise@cisco.com>
> > To: <ops-area@ietf.org>
> > Sent: Friday, February 14, 2014 12:39 AM
> > > Dear all,
> > >
> > > We occasionally see read-write MIB module proposals within the IETF.
> > > However, the write capabilities of those MIB modules are rarely
> > implemented.
> > >
> > > While discussing this issue with the MIB doctors, we arrive to the
> > > conclusion that it's now time to set the direction for future MIB
> > > developments within the IETF. Basically, let's not specify
> > > read-write MIB modules unless we have a good reason. Read-only MIB
> > > modules are still fine though, as SNMP is clearly used for monitoring
> purposes.
> > >
> > > Here is the statement we came up with:
> > >
> > >     The OPS area recommends the use of NETCONF/YANG standards for
> > >     configuration. IETF working groups are therefore encouraged to use
> > >     the NETCONF/YANG standards for configuration, specifically in new
> > >     charters. SNMP MIB modules modifying persistent configuration
> > state
> > >     should only be produced by working groups in cases of clear
> > utility
> > >     and consensus to use SNMP write operations for configuration.
> > >
> > > Ideally, this should become an IESG statement.
> > > Your feedback is most welcome.
> >
> > You probably know that there is currently a consensus call in progress
> > over
> >
> > "Please indicate Support or Oppose for this MIB
> > (draft-ietf-mpls-tp-te-mib) to be read-only."
> >
> > and I was pleasantly surprised to see opposition, albeit with one
> > opponent later changing their mind (perhaps they were sat on from a
> > height:-).  I don't see much sign of Netxxxx in the mpls arena but
> > there is a need there for configuration, since there need not be a
> control
> plane to set things up.
> > Perhaps writable MIB modules will still be with us in the distant
> > future in some corners of the Internet..
> >
> > Ideally, this idea would be fleshed out in an I-D.
> >
> > Tom Petch
> >
> > > Regards, the MIB doctors & Benoit
> >
> > _______________________________________________
> > OPS-AREA mailing list
> > OPS-AREA@ietf.org
> > https://www.ietf.org/mailman/listinfo/ops-area
> >
> >
> > -----
> > No virus found in this message.
> > Checked by AVG - www.avg.com
> > Version: 2014.0.4259 / Virus Database: 3705/7092 - Release Date:
> > 02/14/14
> >
> > _______________________________________________
> > OPS-AREA mailing list
> > OPS-AREA@ietf.org
> > https://www.ietf.org/mailman/listinfo/ops-area
>
>
>
> -----
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 2014.0.4259 / Virus Database: 3705/7092 - Release Date: 02/14/14
>
> _______________________________________________
> MIB-DOCTORS mailing list
> MIB-DOCTORS@ietf.org
> https://www.ietf.org/mailman/listinfo/mib-doctors
>

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

<div dir=3D"ltr">Hi,<div><br></div><div>I guess I am confused as well, alth=
ough I don&#39;t claim to know the details ;-)</div><div><br></div><div>Loo=
king at RFC 3812, there are 2 conformance statements:</div><div><br></div>
=A0 =A0 mplsTeModuleFullCompliance<br>=A0=A0=A0 mplsTeModuleReadOnlyComplia=
nce<div><br><div><pre class=3D"" style=3D"font-size:1em;margin-top:0px;marg=
in-bottom:0px;color:rgb(0,0,0)"><span style=3D"color:rgb(34,34,34);font-fam=
ily:arial;font-size:small;white-space:normal">If an agent supports the &quo=
t;ReadOnly&quot; MODULE-COMPLIANCE, then the RowStatus</span><br>
</pre><pre class=3D"" style=3D"font-size:1em;margin-top:0px;margin-bottom:0=
px;color:rgb(0,0,0)"><span style=3D"color:rgb(34,34,34);font-family:arial;f=
ont-size:small;white-space:normal">object is implemented read-only, hard-wi=
red to active (i.e., the agent just populates</span></pre>
<pre class=3D"" style=3D"font-size:1em;margin-top:0px;margin-bottom:0px;col=
or:rgb(0,0,0)"><span style=3D"color:rgb(34,34,34);font-family:arial;font-si=
ze:small;white-space:normal">the read-only table with the entries via some =
external configuration).</span></pre>
<pre class=3D"" style=3D"font-size:1em;margin-top:0px;margin-bottom:0px;col=
or:rgb(0,0,0)"><br></pre><pre class=3D"" style=3D"font-size:1em;margin-top:=
0px;margin-bottom:0px;color:rgb(0,0,0)"><span style=3D"color:rgb(34,34,34);=
font-family:arial;font-size:small;white-space:normal"><br>
</span></pre>=A0 =A0 =A0 =A0 =A0OBJECT =A0 =A0 =A0mplsTunnelRowStatus<br>=
=A0 =A0 =A0 =A0 =A0SYNTAX =A0 =A0 =A0RowStatus { active(1) }<br>=A0 =A0 =A0=
 =A0 =A0MIN-ACCESS =A0read-only<br>=A0 =A0 =A0 =A0 =A0DESCRIPTION &quot;Wri=
te access is not required.&quot;</div></div><div class=3D"gmail_extra">
<br></div><div class=3D"gmail_extra">Why can&#39;t new objects added to the=
 row also allow the server to only claim</div><div class=3D"gmail_extra">co=
nformance to the read-only MODULE-COMPLIANCE? =A0I don&#39;t see the</div><=
div class=3D"gmail_extra">
connection between RowStatus and a developer selecting which</div><div clas=
s=3D"gmail_extra">compliance level it will support in an implementation.</d=
iv><div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">It does =
not matter if the new objects are read-only or read-create.</div>
<div class=3D"gmail_extra">A &quot;read-only&quot; agent will magically ins=
tantiate the new columns,</div><div class=3D"gmail_extra">if it supports th=
e extension. A &quot;read-create&quot; agent will allow</div><div class=3D"=
gmail_extra">
a manager to create new rows, and allow the new r/c columns if</div><div cl=
ass=3D"gmail_extra">it supports the extension.</div><div class=3D"gmail_ext=
ra"><br></div><div class=3D"gmail_extra"><br></div><div class=3D"gmail_extr=
a">Andy</div>
<div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra"><br></div><=
div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra"><br><div cla=
ss=3D"gmail_quote">On Sun, Feb 16, 2014 at 4:11 PM, Joan Cucchiara <span di=
r=3D"ltr">&lt;<a href=3D"mailto:jcucchiara@mindspring.com" target=3D"_blank=
">jcucchiara@mindspring.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;p=
adding-left:1ex">Hi Adrian,<br>
<br>
Please see inline below prefaced with JEC &gt;.<br>
<br>
-----Original Message-----<br>
From: Adrian Farrel [mailto:<a href=3D"mailto:adrian@olddog.co.uk">adrian@o=
lddog.co.uk</a>]<br>
Sent: Friday, February 14, 2014 2:19 PM<br>
To: &#39;Joan Cucchiara&#39;; &#39;t.petch&#39;; &#39;Benoit Claise&#39;; <=
a href=3D"mailto:mib-doctors@ietf.org">mib-doctors@ietf.org</a><br>
Subject: RE: configuration: writable MIB modules versus NETCONF/YANGmodules=
<br>
<br>
Hi Joan,<br>
<br>
[Reverting to the MIB Doctor Thread]<br>
<br>
I will bow to your far (far, far) superior understanding of MIB-speak.<br>
<br>
But I don&#39;t understand :-(<br>
<br>
A row in a table that has RowStatus can have read-only objects and writeabl=
e<br>
objects with Defaults as well as read-create objects.<br>
When you use, for example, CreateAndGo the whole row gets created with<br>
read-create objects as they are Set, with unSet writeable objects<br>
defaulting, and with read-only objects filled with values from the<br>
implementation.<br>
<br>
JEC &gt; But that is kind of beside the point. =A0 The LSR and TE MIBs (rfc=
3813<br>
and rfc3812, c. 2004) have two conformance statements, Full and Read-only.<=
br>
JEC &gt; =A0Full Conformance allows for configuring with SNMP sets. =A0 So =
this<br>
discussion is focusing on only the Full Conformance.<br>
JEC &gt; =A0The RowStatus objects in the TE and LSR MIB Modules (rfc3813 an=
d<br>
rfc3812) MUST be implemented as having =A0a MAX-ACCESS of read-create. =A0 =
In<br>
other words,<br>
JEC &gt; a row can be created or deleted, etc. because the agent processes =
an<br>
SNMP set request to configure the RowStatus object (i.e. a set is issued<br=
>
JEC &gt; for create-and-go, destroy, etc).<br>
<br>
JEC &gt; The point is that RowStatus =A0creates the row because of an SNMP =
set<br>
request. =A0(Certainly rows can be created other ways too.)<br>
JEC &gt; =A0There is only ONE RowStatus for the entire row, and<br>
JEC &gt; if that row is extended or AUGMENTed in additional MIB Modules, as=
 in<br>
the case draft-ietf-mpls-tp-te-mib which extends rows in rfc3813 and<br>
rfc3812,<br>
JEC &gt; then these extended rows are controlled ALSO by that same RowStatu=
s<br>
object which was defined in the TE/LSR MIB Modules.<br>
JEC &gt; There is only one RowStatus object which controls the entire row, =
even<br>
if parts<br>
JEC&gt; of the row are in different MIB Modules (as with<br>
draft-ietf-mpls-tp-te-mib). =A0 =A0If you think about the case of deleting =
a<br>
row, this makes sense.<br>
JEC &gt; If the RowStatus object in the TE MIB is set to &quot;destroy&quot=
;, then the<br>
deletion of the entire row must happen, even if the objects of that row are=
<br>
in<br>
JEC &gt; other MIB modules.<br>
<br>
When I extend a table, surely I can extend with objects that are all only<b=
r>
read-only?<br>
Furthermore, the whole row in the extension table could be automatically<br=
>
created when the row in the extended table is created.<br>
<br>
What am I missing?<br>
<br>
JEC &gt; =A0The agent =A0MUST &quot;configure&quot; (e.g. create the object=
s, =A0delete the<br>
objects) in =A0these extended rows =A0in this draft because of an SNMP set<=
br>
request.<br>
JEC &gt; =A0 I don&#39;t see any way around this, without redefining the Ro=
wStatus<br>
TC, or rewriting the TE or LSR MIBs or (probably the simplest solution) the=
<br>
JEC&gt; co-authors write the draft in such a way as to not extend tables in=
 the<br>
TE and LSR MIBs.<br>
<br>
JEC &gt; So to summarize, an SNMP agent that supports this draft MUST suppo=
rt<br>
the SNMP set request for RowStatus for the rows which extend rows in<br>
JEC&gt; the LSR and TE MIBs.<br>
<br>
JEC&gt; Since that is the case, and since this draft is tied to these RFCs =
that<br>
are 10 years old now, =A0I don&#39;t have an issue<br>
JEC&gt; with them configuring via SNMP for other objects also (but that is =
just<br>
my opinion).<br>
<br>
Thanks,<br>
=A0 -Joan<br>
<br>
<br>
<br>
Thanks,<br>
Adrian<br>
<br>
&gt; -----Original Message-----<br>
&gt; From: OPS-AREA [mailto:<a href=3D"mailto:ops-area-bounces@ietf.org">op=
s-area-bounces@ietf.org</a>] On Behalf Of Joan<br>
&gt; Cucchiara<br>
&gt; Sent: 14 February 2014 18:28<br>
&gt; To: &#39;t.petch&#39;; &#39;Benoit Claise&#39;; <a href=3D"mailto:ops-=
area@ietf.org">ops-area@ietf.org</a><br>
&gt; Subject: Re: [OPS-AREA] configuration: writable MIB modules versus<br>
&gt; NETCONF/YANGmodules<br>
&gt;<br>
&gt; Hi Tom,<br>
&gt;<br>
&gt; As the MIB Dr. on this draft, =A0I have responded on the MIB Dr. threa=
d<br>
&gt; that I do NOT see a way to make this draft (draft-ietf-mpls-tp-te-mib)=
<br>
read-only.<br>
&gt; This draft contains extension tables for tables in LSR and TE MIBS whi=
ch<br>
are<br>
&gt; created by RowStatus (which is read-create). =A0 Like it or not, RowSt=
atus<br>
of<br>
&gt; those MIBs (i.e. LSR and TE MIBs) effect the rows in the extension tab=
les<br>
of<br>
&gt; this draft (think the case of row creation or row deletion). =A0 That =
is an<br>
&gt; SNMP Set operation which effects the draft.<br>
&gt;<br>
&gt; I believe the statement that Benoit puts forth would allow for such a<=
br>
&gt; situation as this draft, specifically:<br>
&gt;<br>
&gt; &quot;... SNMP MIB modules modifying persistent configuration state =
=A0should<br>
&gt; only be produced by working groups in cases of clear utility and<br>
&gt; consensus to use SNMP write operations for configuration.&quot;<br>
&gt;<br>
&gt; Perhaps, additional wording, such as &quot;For example, in the case of=
<br>
&gt; proposed SNMP MIB modules which extend or augment rows that are<br>
&gt; created by configuration in a SNMP MIB module which is already a RFC,<=
br>
&gt; the proposed SNNP MIB modules will be grandfathered, if the working<br=
>
&gt; group finds consensus to do so.&quot;<br>
&gt;<br>
&gt; However, I am okay with the statement as written.<br>
&gt;<br>
&gt; Thanks,<br>
&gt; =A0 -Joan<br>
&gt;<br>
&gt;<br>
&gt; -----Original Message-----<br>
&gt; From: OPS-AREA [mailto:<a href=3D"mailto:ops-area-bounces@ietf.org">op=
s-area-bounces@ietf.org</a>] On Behalf Of t.petch<br>
&gt; Sent: Friday, February 14, 2014 10:02 AM<br>
&gt; To: Benoit Claise; <a href=3D"mailto:ops-area@ietf.org">ops-area@ietf.=
org</a><br>
&gt; Subject: Re: [OPS-AREA] configuration: writable MIB modules versus<br>
&gt; NETCONF/YANGmodules<br>
&gt;<br>
&gt; ----- Original Message -----<br>
&gt; From: &quot;Benoit Claise&quot; &lt;<a href=3D"mailto:bclaise@cisco.co=
m">bclaise@cisco.com</a>&gt;<br>
&gt; To: &lt;<a href=3D"mailto:ops-area@ietf.org">ops-area@ietf.org</a>&gt;=
<br>
&gt; Sent: Friday, February 14, 2014 12:39 AM<br>
&gt; &gt; Dear all,<br>
&gt; &gt;<br>
&gt; &gt; We occasionally see read-write MIB module proposals within the IE=
TF.<br>
&gt; &gt; However, the write capabilities of those MIB modules are rarely<b=
r>
&gt; implemented.<br>
&gt; &gt;<br>
&gt; &gt; While discussing this issue with the MIB doctors, we arrive to th=
e<br>
&gt; &gt; conclusion that it&#39;s now time to set the direction for future=
 MIB<br>
&gt; &gt; developments within the IETF. Basically, let&#39;s not specify<br=
>
&gt; &gt; read-write MIB modules unless we have a good reason. Read-only MI=
B<br>
&gt; &gt; modules are still fine though, as SNMP is clearly used for monito=
ring<br>
purposes.<br>
&gt; &gt;<br>
&gt; &gt; Here is the statement we came up with:<br>
&gt; &gt;<br>
&gt; &gt; =A0 =A0 The OPS area recommends the use of NETCONF/YANG standards=
 for<br>
&gt; &gt; =A0 =A0 configuration. IETF working groups are therefore encourag=
ed to use<br>
&gt; &gt; =A0 =A0 the NETCONF/YANG standards for configuration, specificall=
y in new<br>
&gt; &gt; =A0 =A0 charters. SNMP MIB modules modifying persistent configura=
tion<br>
&gt; state<br>
&gt; &gt; =A0 =A0 should only be produced by working groups in cases of cle=
ar<br>
&gt; utility<br>
&gt; &gt; =A0 =A0 and consensus to use SNMP write operations for configurat=
ion.<br>
&gt; &gt;<br>
&gt; &gt; Ideally, this should become an IESG statement.<br>
&gt; &gt; Your feedback is most welcome.<br>
&gt;<br>
&gt; You probably know that there is currently a consensus call in progress=
<br>
&gt; over<br>
&gt;<br>
&gt; &quot;Please indicate Support or Oppose for this MIB<br>
&gt; (draft-ietf-mpls-tp-te-mib) to be read-only.&quot;<br>
&gt;<br>
&gt; and I was pleasantly surprised to see opposition, albeit with one<br>
&gt; opponent later changing their mind (perhaps they were sat on from a<br=
>
&gt; height:-). =A0I don&#39;t see much sign of Netxxxx in the mpls arena b=
ut<br>
&gt; there is a need there for configuration, since there need not be a con=
trol<br>
plane to set things up.<br>
&gt; Perhaps writable MIB modules will still be with us in the distant<br>
&gt; future in some corners of the Internet..<br>
&gt;<br>
&gt; Ideally, this idea would be fleshed out in an I-D.<br>
&gt;<br>
&gt; Tom Petch<br>
&gt;<br>
&gt; &gt; Regards, the MIB doctors &amp; Benoit<br>
&gt;<br>
&gt; _______________________________________________<br>
&gt; OPS-AREA mailing list<br>
&gt; <a href=3D"mailto:OPS-AREA@ietf.org">OPS-AREA@ietf.org</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/ops-area" target=3D"_=
blank">https://www.ietf.org/mailman/listinfo/ops-area</a><br>
&gt;<br>
&gt;<br>
&gt; -----<br>
&gt; No virus found in this message.<br>
&gt; Checked by AVG - <a href=3D"http://www.avg.com" target=3D"_blank">www.=
avg.com</a><br>
&gt; Version: 2014.0.4259 / Virus Database: 3705/7092 - Release Date:<br>
&gt; 02/14/14<br>
&gt;<br>
&gt; _______________________________________________<br>
&gt; OPS-AREA mailing list<br>
&gt; <a href=3D"mailto:OPS-AREA@ietf.org">OPS-AREA@ietf.org</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/ops-area" target=3D"_=
blank">https://www.ietf.org/mailman/listinfo/ops-area</a><br>
<br>
<br>
<br>
-----<br>
No virus found in this message.<br>
Checked by AVG - <a href=3D"http://www.avg.com" target=3D"_blank">www.avg.c=
om</a><br>
Version: 2014.0.4259 / Virus Database: 3705/7092 - Release Date: 02/14/14<b=
r>
<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>
</blockquote></div><br></div></div>

--001a1132e004f41a0804f2909965--


From nobody Mon Feb 17 07:10:08 2014
Return-Path: <jcucchiara@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 37D011A01CE for <mib-doctors@ietfa.amsl.com>; Mon, 17 Feb 2014 07:09:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.399
X-Spam-Level: 
X-Spam-Status: No, score=-1.399 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, J_CHICKENPOX_15=0.6, RCVD_IN_DNSWL_NONE=-0.0001] 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 LkbfepwQKcO0 for <mib-doctors@ietfa.amsl.com>; Mon, 17 Feb 2014 07:09:49 -0800 (PST)
Received: from elasmtp-scoter.atl.sa.earthlink.net (elasmtp-scoter.atl.sa.earthlink.net [209.86.89.67]) by ietfa.amsl.com (Postfix) with ESMTP id A890D1A0203 for <mib-doctors@ietf.org>; Mon, 17 Feb 2014 07:09:49 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=X+cgVmNyw7ACX04gM+1amLFn/UK1qeQz+Usb81HBxy4/eyIVuDj6F6dsQruXpj3e; h=Received:From:To:Cc:References:In-Reply-To:Subject:Date:Message-ID:MIME-Version:Content-Type:X-Mailer:Thread-Index:Content-Language:X-ELNK-Trace:X-Originating-IP;
Received: from [24.41.69.138] (helo=JoanTower) by elasmtp-scoter.atl.sa.earthlink.net with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.67) (envelope-from <jcucchiara@mindspring.com>) id 1WFPpH-0005Fc-JJ; Mon, 17 Feb 2014 10:09:44 -0500
From: "Joan Cucchiara" <jcucchiara@mindspring.com>
To: "'Andy Bierman'" <andy@yumaworks.com>
References: <00b101cf29b9$95d979e0$c18c6da0$@olddog.co.uk>	<029901cf2b74$d9d74c00$8d85e400$@mindspring.com> <CABCOCHTScmkGNTtEUcnYWBMJ3Pp1CLwG+1QmBaFOmJYPX64UYQ@mail.gmail.com>
In-Reply-To: <CABCOCHTScmkGNTtEUcnYWBMJ3Pp1CLwG+1QmBaFOmJYPX64UYQ@mail.gmail.com>
Date: Mon, 17 Feb 2014 10:09:40 -0500
Message-ID: <02c001cf2bf2$49150cb0$db3f2610$@mindspring.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_02C1_01CF2BC8.6041EAE0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQHx1En8PKiAdP7k24gVTn+0j3wjJQFSZgvIAUrV1VuaX0aSEA==
Content-Language: en-us
X-ELNK-Trace: 4d68bbe9cb71969ea344cf2d1a8e60840a9da525759e265481755e0df9f0aa2cdf667ae7e3b0ab73a26b888b88ba812a350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 24.41.69.138
Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/-s_4OVAvN_gAsAQ7eE2gyAgH6J0
Cc: 'Adrian Farrel' <adrian@olddog.co.uk>, "'t.petch'" <ietfc@btconnect.com>, "'MIB Doctors \(E-mail\)'" <mib-doctors@ietf.org>
Subject: Re: [MIB-DOCTORS] configuration: writable MIB modules versus NETCONF/YANGmodules
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, 17 Feb 2014 15:09:56 -0000

This is a multipart message in MIME format.

------=_NextPart_000_02C1_01CF2BC8.6041EAE0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hi Andy,

 

The discussion is wrt FullCompliance only, sorry if that wasn't clear.    

 

Even so, if RowStatus is defined as FullCompliance, doesn't that hold for
new extended table objects which are under the control of RowStatus with
FullCompliance?

 

Managed entity still needs to support the RowStatus  as defined originally.
Plus, I would think the "correct" Compliance for the draft should include
the 

support of Full Compliance for RowStatus of the relevant tables from TE MIB
and LSR MIB (i.e. the relevant tables meaning those which are extended in
the draft).

 

(Probably more info that you want to know but.)

Additionally, the TE and LSR MIBs have other MIBs (rfcs) in GMPLS and PWE
which also extend tables from LSR MIB/TE MIB.   So, for 10  years these MIBs
have been

around, and there is a lot of legacy even in other WGs.    

 

I agree that there needs to be some discussion and thought around migration
of MPLS management to NetConf for configuration.   The issue (as I see it)
is that

the LSR MIB contains a LIB (LSR table) and the TE MIB contains a Tunnel
Table and these have been extended/Augmented in various MIBs and in various
WGs for 10 years.

 

Either the WGs can keep going with MIBs, or rewrite in NetConf.   To me,
seems like everyone is focused on this draft, but not really focused on how
best to help MPLS migrate.   (Not sure the WG even wants to migrate, so may
have misspoken..)   Anyway, no matter what the decision is on the draft,
that is still not going to help

MPLS when new features are defined and folks still want to use the LIB and
Tunnel Tables in rfc3813 and rfc3812.

 

Thanks,

  -Joan

 

From: Andy Bierman [mailto:andy@yumaworks.com] 
Sent: Sunday, February 16, 2014 9:06 PM
To: Joan Cucchiara
Cc: Adrian Farrel; t.petch; Benoit Claise; MIB Doctors (E-mail)
Subject: Re: [MIB-DOCTORS] configuration: writable MIB modules versus
NETCONF/YANGmodules

 

Hi,

 

I guess I am confused as well, although I don't claim to know the details
;-)

 

Looking at RFC 3812, there are 2 conformance statements:

 

    mplsTeModuleFullCompliance
    mplsTeModuleReadOnlyCompliance

 

If an agent supports the "ReadOnly" MODULE-COMPLIANCE, then the RowStatus


object is implemented read-only, hard-wired to active (i.e., the agent just
populates
the read-only table with the entries via some external configuration).
 
 

         OBJECT      mplsTunnelRowStatus
         SYNTAX      RowStatus { active(1) }
         MIN-ACCESS  read-only
         DESCRIPTION "Write access is not required."

 

Why can't new objects added to the row also allow the server to only claim

conformance to the read-only MODULE-COMPLIANCE?  I don't see the

connection between RowStatus and a developer selecting which

compliance level it will support in an implementation.

 

It does not matter if the new objects are read-only or read-create.

A "read-only" agent will magically instantiate the new columns,

if it supports the extension. A "read-create" agent will allow

a manager to create new rows, and allow the new r/c columns if

it supports the extension.

 

 

Andy

 

 

 

 

On Sun, Feb 16, 2014 at 4:11 PM, Joan Cucchiara <jcucchiara@mindspring.com>
wrote:

Hi Adrian,

Please see inline below prefaced with JEC >.

-----Original Message-----
From: Adrian Farrel [mailto:adrian@olddog.co.uk]
Sent: Friday, February 14, 2014 2:19 PM
To: 'Joan Cucchiara'; 't.petch'; 'Benoit Claise'; mib-doctors@ietf.org
Subject: RE: configuration: writable MIB modules versus NETCONF/YANGmodules

Hi Joan,

[Reverting to the MIB Doctor Thread]

I will bow to your far (far, far) superior understanding of MIB-speak.

But I don't understand :-(

A row in a table that has RowStatus can have read-only objects and writeable
objects with Defaults as well as read-create objects.
When you use, for example, CreateAndGo the whole row gets created with
read-create objects as they are Set, with unSet writeable objects
defaulting, and with read-only objects filled with values from the
implementation.

JEC > But that is kind of beside the point.   The LSR and TE MIBs (rfc3813
and rfc3812, c. 2004) have two conformance statements, Full and Read-only.
JEC >  Full Conformance allows for configuring with SNMP sets.   So this
discussion is focusing on only the Full Conformance.
JEC >  The RowStatus objects in the TE and LSR MIB Modules (rfc3813 and
rfc3812) MUST be implemented as having  a MAX-ACCESS of read-create.   In
other words,
JEC > a row can be created or deleted, etc. because the agent processes an
SNMP set request to configure the RowStatus object (i.e. a set is issued
JEC > for create-and-go, destroy, etc).

JEC > The point is that RowStatus  creates the row because of an SNMP set
request.  (Certainly rows can be created other ways too.)
JEC >  There is only ONE RowStatus for the entire row, and
JEC > if that row is extended or AUGMENTed in additional MIB Modules, as in
the case draft-ietf-mpls-tp-te-mib which extends rows in rfc3813 and
rfc3812,
JEC > then these extended rows are controlled ALSO by that same RowStatus
object which was defined in the TE/LSR MIB Modules.
JEC > There is only one RowStatus object which controls the entire row, even
if parts
JEC> of the row are in different MIB Modules (as with
draft-ietf-mpls-tp-te-mib).    If you think about the case of deleting a
row, this makes sense.
JEC > If the RowStatus object in the TE MIB is set to "destroy", then the
deletion of the entire row must happen, even if the objects of that row are
in
JEC > other MIB modules.

When I extend a table, surely I can extend with objects that are all only
read-only?
Furthermore, the whole row in the extension table could be automatically
created when the row in the extended table is created.

What am I missing?

JEC >  The agent  MUST "configure" (e.g. create the objects,  delete the
objects) in  these extended rows  in this draft because of an SNMP set
request.
JEC >   I don't see any way around this, without redefining the RowStatus
TC, or rewriting the TE or LSR MIBs or (probably the simplest solution) the
JEC> co-authors write the draft in such a way as to not extend tables in the
TE and LSR MIBs.

JEC > So to summarize, an SNMP agent that supports this draft MUST support
the SNMP set request for RowStatus for the rows which extend rows in
JEC> the LSR and TE MIBs.

JEC> Since that is the case, and since this draft is tied to these RFCs that
are 10 years old now,  I don't have an issue
JEC> with them configuring via SNMP for other objects also (but that is just
my opinion).

Thanks,
  -Joan



Thanks,
Adrian

> -----Original Message-----
> From: OPS-AREA [mailto:ops-area-bounces@ietf.org] On Behalf Of Joan
> Cucchiara
> Sent: 14 February 2014 18:28
> To: 't.petch'; 'Benoit Claise'; ops-area@ietf.org
> Subject: Re: [OPS-AREA] configuration: writable MIB modules versus
> NETCONF/YANGmodules
>
> Hi Tom,
>
> As the MIB Dr. on this draft,  I have responded on the MIB Dr. thread
> that I do NOT see a way to make this draft (draft-ietf-mpls-tp-te-mib)
read-only.
> This draft contains extension tables for tables in LSR and TE MIBS which
are
> created by RowStatus (which is read-create).   Like it or not, RowStatus
of
> those MIBs (i.e. LSR and TE MIBs) effect the rows in the extension tables
of
> this draft (think the case of row creation or row deletion).   That is an
> SNMP Set operation which effects the draft.
>
> I believe the statement that Benoit puts forth would allow for such a
> situation as this draft, specifically:
>
> "... SNMP MIB modules modifying persistent configuration state  should
> only be produced by working groups in cases of clear utility and
> consensus to use SNMP write operations for configuration."
>
> Perhaps, additional wording, such as "For example, in the case of
> proposed SNMP MIB modules which extend or augment rows that are
> created by configuration in a SNMP MIB module which is already a RFC,
> the proposed SNNP MIB modules will be grandfathered, if the working
> group finds consensus to do so."
>
> However, I am okay with the statement as written.
>
> Thanks,
>   -Joan
>
>
> -----Original Message-----
> From: OPS-AREA [mailto:ops-area-bounces@ietf.org] On Behalf Of t.petch
> Sent: Friday, February 14, 2014 10:02 AM
> To: Benoit Claise; ops-area@ietf.org
> Subject: Re: [OPS-AREA] configuration: writable MIB modules versus
> NETCONF/YANGmodules
>
> ----- Original Message -----
> From: "Benoit Claise" <bclaise@cisco.com>
> To: <ops-area@ietf.org>
> Sent: Friday, February 14, 2014 12:39 AM
> > Dear all,
> >
> > We occasionally see read-write MIB module proposals within the IETF.
> > However, the write capabilities of those MIB modules are rarely
> implemented.
> >
> > While discussing this issue with the MIB doctors, we arrive to the
> > conclusion that it's now time to set the direction for future MIB
> > developments within the IETF. Basically, let's not specify
> > read-write MIB modules unless we have a good reason. Read-only MIB
> > modules are still fine though, as SNMP is clearly used for monitoring
purposes.
> >
> > Here is the statement we came up with:
> >
> >     The OPS area recommends the use of NETCONF/YANG standards for
> >     configuration. IETF working groups are therefore encouraged to use
> >     the NETCONF/YANG standards for configuration, specifically in new
> >     charters. SNMP MIB modules modifying persistent configuration
> state
> >     should only be produced by working groups in cases of clear
> utility
> >     and consensus to use SNMP write operations for configuration.
> >
> > Ideally, this should become an IESG statement.
> > Your feedback is most welcome.
>
> You probably know that there is currently a consensus call in progress
> over
>
> "Please indicate Support or Oppose for this MIB
> (draft-ietf-mpls-tp-te-mib) to be read-only."
>
> and I was pleasantly surprised to see opposition, albeit with one
> opponent later changing their mind (perhaps they were sat on from a
> height:-).  I don't see much sign of Netxxxx in the mpls arena but
> there is a need there for configuration, since there need not be a control
plane to set things up.
> Perhaps writable MIB modules will still be with us in the distant
> future in some corners of the Internet..
>
> Ideally, this idea would be fleshed out in an I-D.
>
> Tom Petch
>
> > Regards, the MIB doctors & Benoit
>
> _______________________________________________
> OPS-AREA mailing list
> OPS-AREA@ietf.org
> https://www.ietf.org/mailman/listinfo/ops-area
>
>
> -----
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 2014.0.4259 / Virus Database: 3705/7092 - Release Date:
> 02/14/14
>
> _______________________________________________
> OPS-AREA mailing list
> OPS-AREA@ietf.org
> https://www.ietf.org/mailman/listinfo/ops-area



-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2014.0.4259 / Virus Database: 3705/7092 - Release Date: 02/14/14

_______________________________________________
MIB-DOCTORS mailing list
MIB-DOCTORS@ietf.org
https://www.ietf.org/mailman/listinfo/mib-doctors

 

No virus found in this message.
Checked by AVG - www.avg.com
Version: 2014.0.4259 / Virus Database: 3705/7098 - Release Date: 02/16/14

  _____  

No virus found in this message.
Checked by AVG - www.avg.com
Version: 2014.0.4259 / Virus Database: 3697/7083 - Release Date: 02/11/14


------=_NextPart_000_02C1_01CF2BC8.6041EAE0
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=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><!--[if !mso]><style>v\:* =
{behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@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:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
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:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle21
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></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 lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Hi Andy,<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>The discussion is wrt FullCompliance only, sorry if that wasn&#8217;t =
clear.&nbsp; &nbsp;&nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Even so, if RowStatus is defined as FullCompliance, doesn&#8217;t =
that hold for new extended table objects which are under the control of =
RowStatus with FullCompliance?<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Managed entity still needs to support the RowStatus &nbsp;as defined =
originally.&nbsp;&nbsp; Plus, I would think the &#8220;correct&#8221; =
Compliance for the draft should include the <o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>support of Full Compliance for RowStatus of the relevant tables from =
TE MIB and LSR MIB (i.e. the relevant tables meaning those which are =
extended in the draft).<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>(Probably more info that you want to know =
but&#8230;)<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Additionally, the TE and LSR MIBs have other MIBs (rfcs) in GMPLS and =
PWE which also extend tables from LSR MIB/TE MIB.&nbsp;&nbsp; So, for 10 =
&nbsp;years these MIBs have been<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>around, and there is a lot of legacy even in other =
WGs.&nbsp;&nbsp;&nbsp; <o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>I agree that there needs to be some discussion and thought around =
migration of MPLS management to NetConf for configuration.&nbsp;&nbsp; =
The issue (as I see it) is that<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>the LSR MIB contains a LIB (LSR table) and the TE MIB contains a =
Tunnel Table and these have been extended/Augmented in various MIBs and =
in various WGs for 10 years.<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Either the WGs can keep going with MIBs, or rewrite in =
NetConf.&nbsp;&nbsp; To me, seems like everyone is focused on this =
draft, but not really focused on how best to help MPLS =
migrate.&nbsp;&nbsp; (Not sure the WG even wants to migrate, so may have =
misspoken&#8230;.)&nbsp;&nbsp; Anyway, no matter what the decision is on =
the draft, that is still not going to help<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>MPLS when new features are defined and folks still want to use the =
LIB and Tunnel Tables in rfc3813 and rfc3812.<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Thanks,<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp; -Joan<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'> <o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
Andy Bierman [mailto:andy@yumaworks.com] <br><b>Sent:</b> Sunday, =
February 16, 2014 9:06 PM<br><b>To:</b> Joan Cucchiara<br><b>Cc:</b> =
Adrian Farrel; t.petch; Benoit Claise; MIB Doctors =
(E-mail)<br><b>Subject:</b> Re: [MIB-DOCTORS] configuration: writable =
MIB modules versus NETCONF/YANGmodules<o:p></o:p></span></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><p =
class=3DMsoNormal>Hi,<o:p></o:p></p><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>I =
guess I am confused as well, although I don't claim to know the details =
;-)<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>Looking at RFC 3812, there are 2 conformance =
statements:<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><p class=3DMsoNormal>&nbsp; =
&nbsp; mplsTeModuleFullCompliance<br>&nbsp;&nbsp;&nbsp; =
mplsTeModuleReadOnlyCompliance<o:p></o:p></p><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><pre><span =
style=3D'font-size:12.0pt;font-family:"Arial","sans-serif";color:#222222'=
>If an agent supports the &quot;ReadOnly&quot; MODULE-COMPLIANCE, then =
the RowStatus</span><span =
style=3D'font-size:12.0pt;color:black'><br><br><o:p></o:p></span></pre><p=
re><span =
style=3D'font-size:12.0pt;font-family:"Arial","sans-serif";color:#222222'=
>object is implemented read-only, hard-wired to active (i.e., the agent =
just populates</span><span =
style=3D'font-size:12.0pt;color:black'><o:p></o:p></span></pre><pre><span=
 =
style=3D'font-size:12.0pt;font-family:"Arial","sans-serif";color:#222222'=
>the read-only table with the entries via some external =
configuration).</span><span =
style=3D'font-size:12.0pt;color:black'><o:p></o:p></span></pre><pre><span=
 =
style=3D'font-size:12.0pt;color:black'><o:p>&nbsp;</o:p></span></pre><pre=
><span =
style=3D'font-size:12.0pt;color:black'><o:p>&nbsp;</o:p></span></pre><p =
class=3DMsoNormal>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;OBJECT &nbsp; &nbsp; =
&nbsp;mplsTunnelRowStatus<br>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;SYNTAX =
&nbsp; &nbsp; &nbsp;RowStatus { active(1) }<br>&nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp;MIN-ACCESS &nbsp;read-only<br>&nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;DESCRIPTION &quot;Write access is not =
required.&quot;<o:p></o:p></p></div></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>Why can't new objects added to the row also allow the =
server to only claim<o:p></o:p></p></div><div><p =
class=3DMsoNormal>conformance to the read-only MODULE-COMPLIANCE? =
&nbsp;I don't see the<o:p></o:p></p></div><div><p =
class=3DMsoNormal>connection between RowStatus and a developer selecting =
which<o:p></o:p></p></div><div><p class=3DMsoNormal>compliance level it =
will support in an implementation.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>It does not matter if the new objects are read-only or =
read-create.<o:p></o:p></p></div><div><p class=3DMsoNormal>A =
&quot;read-only&quot; agent will magically instantiate the new =
columns,<o:p></o:p></p></div><div><p class=3DMsoNormal>if it supports =
the extension. A &quot;read-create&quot; agent will =
allow<o:p></o:p></p></div><div><p class=3DMsoNormal>a manager to create =
new rows, and allow the new r/c columns if<o:p></o:p></p></div><div><p =
class=3DMsoNormal>it supports the extension.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>Andy<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><p class=3DMsoNormal>On Sun, =
Feb 16, 2014 at 4:11 PM, Joan Cucchiara &lt;<a =
href=3D"mailto:jcucchiara@mindspring.com" =
target=3D"_blank">jcucchiara@mindspring.com</a>&gt; =
wrote:<o:p></o:p></p><p class=3DMsoNormal>Hi Adrian,<br><br>Please see =
inline below prefaced with JEC &gt;.<br><br>-----Original =
Message-----<br>From: Adrian Farrel [mailto:<a =
href=3D"mailto:adrian@olddog.co.uk">adrian@olddog.co.uk</a>]<br>Sent: =
Friday, February 14, 2014 2:19 PM<br>To: 'Joan Cucchiara'; 't.petch'; =
'Benoit Claise'; <a =
href=3D"mailto:mib-doctors@ietf.org">mib-doctors@ietf.org</a><br>Subject:=
 RE: configuration: writable MIB modules versus =
NETCONF/YANGmodules<br><br>Hi Joan,<br><br>[Reverting to the MIB Doctor =
Thread]<br><br>I will bow to your far (far, far) superior understanding =
of MIB-speak.<br><br>But I don't understand :-(<br><br>A row in a table =
that has RowStatus can have read-only objects and writeable<br>objects =
with Defaults as well as read-create objects.<br>When you use, for =
example, CreateAndGo the whole row gets created with<br>read-create =
objects as they are Set, with unSet writeable objects<br>defaulting, and =
with read-only objects filled with values from =
the<br>implementation.<br><br>JEC &gt; But that is kind of beside the =
point. &nbsp; The LSR and TE MIBs (rfc3813<br>and rfc3812, c. 2004) have =
two conformance statements, Full and Read-only.<br>JEC &gt; &nbsp;Full =
Conformance allows for configuring with SNMP sets. &nbsp; So =
this<br>discussion is focusing on only the Full Conformance.<br>JEC &gt; =
&nbsp;The RowStatus objects in the TE and LSR MIB Modules (rfc3813 =
and<br>rfc3812) MUST be implemented as having &nbsp;a MAX-ACCESS of =
read-create. &nbsp; In<br>other words,<br>JEC &gt; a row can be created =
or deleted, etc. because the agent processes an<br>SNMP set request to =
configure the RowStatus object (i.e. a set is issued<br>JEC &gt; for =
create-and-go, destroy, etc).<br><br>JEC &gt; The point is that =
RowStatus &nbsp;creates the row because of an SNMP set<br>request. =
&nbsp;(Certainly rows can be created other ways too.)<br>JEC &gt; =
&nbsp;There is only ONE RowStatus for the entire row, and<br>JEC &gt; if =
that row is extended or AUGMENTed in additional MIB Modules, as =
in<br>the case draft-ietf-mpls-tp-te-mib which extends rows in rfc3813 =
and<br>rfc3812,<br>JEC &gt; then these extended rows are controlled ALSO =
by that same RowStatus<br>object which was defined in the TE/LSR MIB =
Modules.<br>JEC &gt; There is only one RowStatus object which controls =
the entire row, even<br>if parts<br>JEC&gt; of the row are in different =
MIB Modules (as with<br>draft-ietf-mpls-tp-te-mib). &nbsp; &nbsp;If you =
think about the case of deleting a<br>row, this makes sense.<br>JEC &gt; =
If the RowStatus object in the TE MIB is set to &quot;destroy&quot;, =
then the<br>deletion of the entire row must happen, even if the objects =
of that row are<br>in<br>JEC &gt; other MIB modules.<br><br>When I =
extend a table, surely I can extend with objects that are all =
only<br>read-only?<br>Furthermore, the whole row in the extension table =
could be automatically<br>created when the row in the extended table is =
created.<br><br>What am I missing?<br><br>JEC &gt; &nbsp;The agent =
&nbsp;MUST &quot;configure&quot; (e.g. create the objects, &nbsp;delete =
the<br>objects) in &nbsp;these extended rows &nbsp;in this draft because =
of an SNMP set<br>request.<br>JEC &gt; &nbsp; I don't see any way around =
this, without redefining the RowStatus<br>TC, or rewriting the TE or LSR =
MIBs or (probably the simplest solution) the<br>JEC&gt; co-authors write =
the draft in such a way as to not extend tables in the<br>TE and LSR =
MIBs.<br><br>JEC &gt; So to summarize, an SNMP agent that supports this =
draft MUST support<br>the SNMP set request for RowStatus for the rows =
which extend rows in<br>JEC&gt; the LSR and TE MIBs.<br><br>JEC&gt; =
Since that is the case, and since this draft is tied to these RFCs =
that<br>are 10 years old now, &nbsp;I don't have an issue<br>JEC&gt; =
with them configuring via SNMP for other objects also (but that is =
just<br>my opinion).<br><br>Thanks,<br>&nbsp; =
-Joan<br><br><br><br>Thanks,<br>Adrian<br><br>&gt; -----Original =
Message-----<br>&gt; From: OPS-AREA [mailto:<a =
href=3D"mailto:ops-area-bounces@ietf.org">ops-area-bounces@ietf.org</a>] =
On Behalf Of Joan<br>&gt; Cucchiara<br>&gt; Sent: 14 February 2014 =
18:28<br>&gt; To: 't.petch'; 'Benoit Claise'; <a =
href=3D"mailto:ops-area@ietf.org">ops-area@ietf.org</a><br>&gt; Subject: =
Re: [OPS-AREA] configuration: writable MIB modules versus<br>&gt; =
NETCONF/YANGmodules<br>&gt;<br>&gt; Hi Tom,<br>&gt;<br>&gt; As the MIB =
Dr. on this draft, &nbsp;I have responded on the MIB Dr. thread<br>&gt; =
that I do NOT see a way to make this draft =
(draft-ietf-mpls-tp-te-mib)<br>read-only.<br>&gt; This draft contains =
extension tables for tables in LSR and TE MIBS which<br>are<br>&gt; =
created by RowStatus (which is read-create). &nbsp; Like it or not, =
RowStatus<br>of<br>&gt; those MIBs (i.e. LSR and TE MIBs) effect the =
rows in the extension tables<br>of<br>&gt; this draft (think the case of =
row creation or row deletion). &nbsp; That is an<br>&gt; SNMP Set =
operation which effects the draft.<br>&gt;<br>&gt; I believe the =
statement that Benoit puts forth would allow for such a<br>&gt; =
situation as this draft, specifically:<br>&gt;<br>&gt; &quot;... SNMP =
MIB modules modifying persistent configuration state =
&nbsp;should<br>&gt; only be produced by working groups in cases of =
clear utility and<br>&gt; consensus to use SNMP write operations for =
configuration.&quot;<br>&gt;<br>&gt; Perhaps, additional wording, such =
as &quot;For example, in the case of<br>&gt; proposed SNMP MIB modules =
which extend or augment rows that are<br>&gt; created by configuration =
in a SNMP MIB module which is already a RFC,<br>&gt; the proposed SNNP =
MIB modules will be grandfathered, if the working<br>&gt; group finds =
consensus to do so.&quot;<br>&gt;<br>&gt; However, I am okay with the =
statement as written.<br>&gt;<br>&gt; Thanks,<br>&gt; &nbsp; =
-Joan<br>&gt;<br>&gt;<br>&gt; -----Original Message-----<br>&gt; From: =
OPS-AREA [mailto:<a =
href=3D"mailto:ops-area-bounces@ietf.org">ops-area-bounces@ietf.org</a>] =
On Behalf Of t.petch<br>&gt; Sent: Friday, February 14, 2014 10:02 =
AM<br>&gt; To: Benoit Claise; <a =
href=3D"mailto:ops-area@ietf.org">ops-area@ietf.org</a><br>&gt; Subject: =
Re: [OPS-AREA] configuration: writable MIB modules versus<br>&gt; =
NETCONF/YANGmodules<br>&gt;<br>&gt; ----- Original Message -----<br>&gt; =
From: &quot;Benoit Claise&quot; &lt;<a =
href=3D"mailto:bclaise@cisco.com">bclaise@cisco.com</a>&gt;<br>&gt; To: =
&lt;<a =
href=3D"mailto:ops-area@ietf.org">ops-area@ietf.org</a>&gt;<br>&gt; =
Sent: Friday, February 14, 2014 12:39 AM<br>&gt; &gt; Dear all,<br>&gt; =
&gt;<br>&gt; &gt; We occasionally see read-write MIB module proposals =
within the IETF.<br>&gt; &gt; However, the write capabilities of those =
MIB modules are rarely<br>&gt; implemented.<br>&gt; &gt;<br>&gt; &gt; =
While discussing this issue with the MIB doctors, we arrive to =
the<br>&gt; &gt; conclusion that it's now time to set the direction for =
future MIB<br>&gt; &gt; developments within the IETF. Basically, let's =
not specify<br>&gt; &gt; read-write MIB modules unless we have a good =
reason. Read-only MIB<br>&gt; &gt; modules are still fine though, as =
SNMP is clearly used for monitoring<br>purposes.<br>&gt; &gt;<br>&gt; =
&gt; Here is the statement we came up with:<br>&gt; &gt;<br>&gt; &gt; =
&nbsp; &nbsp; The OPS area recommends the use of NETCONF/YANG standards =
for<br>&gt; &gt; &nbsp; &nbsp; configuration. IETF working groups are =
therefore encouraged to use<br>&gt; &gt; &nbsp; &nbsp; the NETCONF/YANG =
standards for configuration, specifically in new<br>&gt; &gt; &nbsp; =
&nbsp; charters. SNMP MIB modules modifying persistent =
configuration<br>&gt; state<br>&gt; &gt; &nbsp; &nbsp; should only be =
produced by working groups in cases of clear<br>&gt; utility<br>&gt; =
&gt; &nbsp; &nbsp; and consensus to use SNMP write operations for =
configuration.<br>&gt; &gt;<br>&gt; &gt; Ideally, this should become an =
IESG statement.<br>&gt; &gt; Your feedback is most =
welcome.<br>&gt;<br>&gt; You probably know that there is currently a =
consensus call in progress<br>&gt; over<br>&gt;<br>&gt; &quot;Please =
indicate Support or Oppose for this MIB<br>&gt; =
(draft-ietf-mpls-tp-te-mib) to be read-only.&quot;<br>&gt;<br>&gt; and I =
was pleasantly surprised to see opposition, albeit with one<br>&gt; =
opponent later changing their mind (perhaps they were sat on from =
a<br>&gt; height:-). &nbsp;I don't see much sign of Netxxxx in the mpls =
arena but<br>&gt; there is a need there for configuration, since there =
need not be a control<br>plane to set things up.<br>&gt; Perhaps =
writable MIB modules will still be with us in the distant<br>&gt; future =
in some corners of the Internet..<br>&gt;<br>&gt; Ideally, this idea =
would be fleshed out in an I-D.<br>&gt;<br>&gt; Tom =
Petch<br>&gt;<br>&gt; &gt; Regards, the MIB doctors &amp; =
Benoit<br>&gt;<br>&gt; =
_______________________________________________<br>&gt; OPS-AREA mailing =
list<br>&gt; <a =
href=3D"mailto:OPS-AREA@ietf.org">OPS-AREA@ietf.org</a><br>&gt; <a =
href=3D"https://www.ietf.org/mailman/listinfo/ops-area" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/ops-area</a><br>&=
gt;<br>&gt;<br>&gt; -----<br>&gt; No virus found in this =
message.<br>&gt; Checked by AVG - <a href=3D"http://www.avg.com" =
target=3D"_blank">www.avg.com</a><br>&gt; Version: 2014.0.4259 / Virus =
Database: 3705/7092 - Release Date:<br>&gt; 02/14/14<br>&gt;<br>&gt; =
_______________________________________________<br>&gt; OPS-AREA mailing =
list<br>&gt; <a =
href=3D"mailto:OPS-AREA@ietf.org">OPS-AREA@ietf.org</a><br>&gt; <a =
href=3D"https://www.ietf.org/mailman/listinfo/ops-area" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/ops-area</a><br><=
br><br><br>-----<br>No virus found in this message.<br>Checked by AVG - =
<a href=3D"http://www.avg.com" =
target=3D"_blank">www.avg.com</a><br>Version: 2014.0.4259 / Virus =
Database: 3705/7092 - Release Date: =
02/14/14<br><br>_______________________________________________<br>MIB-DO=
CTORS 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"_blank">https://www.ietf.org/mailman/listinfo/mib-doctors</a><o=
:p></o:p></p></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>No virus =
found in this message.<br>Checked by AVG - <a =
href=3D"http://www.avg.com">www.avg.com</a><br>Version: 2014.0.4259 / =
Virus Database: 3705/7098 - Release Date: 02/16/14<o:p></o:p></p><div =
class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><hr =
size=3D1 width=3D"100%" noshade style=3D'color:#A0A0A0' =
align=3Dcenter></div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>No virus =
found in this message.<br>Checked by AVG - <a =
href=3D"http://www.avg.com">www.avg.com</a><br>Version: 2014.0.4259 / =
Virus Database: 3697/7083 - Release Date: =
02/11/14<o:p></o:p></p></div></body></html>
------=_NextPart_000_02C1_01CF2BC8.6041EAE0--


From nobody Mon Feb 17 08:04:53 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 43B681A0519 for <mib-doctors@ietfa.amsl.com>; Mon, 17 Feb 2014 08:04:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.378
X-Spam-Level: 
X-Spam-Status: No, score=-1.378 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, J_CHICKENPOX_15=0.6, RCVD_IN_DNSWL_LOW=-0.7, 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 DGQEcwlFLCoB for <mib-doctors@ietfa.amsl.com>; Mon, 17 Feb 2014 08:04:44 -0800 (PST)
Received: from mail-qc0-f174.google.com (mail-qc0-f174.google.com [209.85.216.174]) by ietfa.amsl.com (Postfix) with ESMTP id A64D21A03F7 for <mib-doctors@ietf.org>; Mon, 17 Feb 2014 08:04:44 -0800 (PST)
Received: by mail-qc0-f174.google.com with SMTP id x13so23602409qcv.19 for <mib-doctors@ietf.org>; Mon, 17 Feb 2014 08:04:42 -0800 (PST)
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=V0pZ5ky3QOSrpVJ1SpcwjAfwINofBpYsTMI6RbqV+0c=; b=I3INYC/oW6C9KtnYRwWnBklR4Oged35B0gNiLlpy0M4Jh+uf6GMXBNP+3DHCiNE6lL GWTeDrQJ9sLm1jIkpI4/KwSJsmHUiFDE3+m0977UeLiKTmJnwR8dE1CzH38bFqIXprIp kra7Etjji9waIf/4PsMphRoJpmVQLcwc7+1SQICKto2kzJHVsiJKrf7BDA1CO5pchLak D+aw8aDaGzIWHqsd67MbVl4wmIxu471gPxN+vt7V42/Q/J+XX84eGbonzBv+f+kBpL8k iRjAkHNeKuJkAyVJ7UBUX0wD6q22i5tvZfvWp0HC/t1W4sAp0KSSFly1+I7ccELNYy4w 1jww==
X-Gm-Message-State: ALoCoQkVsxgnB1wLLh3+FZNEb0m2APiH2aZxE6Ky/7+XiSPmSBd7CfjBEictyfbAyxTByQPmicMF
MIME-Version: 1.0
X-Received: by 10.229.84.198 with SMTP id k6mr3268970qcl.20.1392653081945; Mon, 17 Feb 2014 08:04:41 -0800 (PST)
Received: by 10.140.98.130 with HTTP; Mon, 17 Feb 2014 08:04:41 -0800 (PST)
In-Reply-To: <02c001cf2bf2$49150cb0$db3f2610$@mindspring.com>
References: <00b101cf29b9$95d979e0$c18c6da0$@olddog.co.uk> <029901cf2b74$d9d74c00$8d85e400$@mindspring.com> <CABCOCHTScmkGNTtEUcnYWBMJ3Pp1CLwG+1QmBaFOmJYPX64UYQ@mail.gmail.com> <02c001cf2bf2$49150cb0$db3f2610$@mindspring.com>
Date: Mon, 17 Feb 2014 08:04:41 -0800
Message-ID: <CABCOCHQdW2eGWZ_=YyKb9dDTk-xM2F8iUVB0xFOYRQ5_tK6XKA@mail.gmail.com>
From: Andy Bierman <andy@yumaworks.com>
To: Joan Cucchiara <jcucchiara@mindspring.com>
Content-Type: multipart/alternative; boundary=001a1134541a3ebc2604f29c5056
Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/0uk-_XCnLbm9SnLLy-E2Nq_qxCI
Cc: Adrian Farrel <adrian@olddog.co.uk>, "t.petch" <ietfc@btconnect.com>, "MIB Doctors \(E-mail\)" <mib-doctors@ietf.org>
Subject: Re: [MIB-DOCTORS] configuration: writable MIB modules versus NETCONF/YANGmodules
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, 17 Feb 2014 16:04:52 -0000

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

On Mon, Feb 17, 2014 at 7:09 AM, Joan Cucchiara
<jcucchiara@mindspring.com>wrote:

> Hi Andy,
>
>
>
> The discussion is wrt FullCompliance only, sorry if that wasn't clear.
>
>
>
> Even so, if RowStatus is defined as FullCompliance, doesn't that hold for
> new extended table objects which are under the control of RowStatus with
> FullCompliance?
>
>
>


I think the OBJECT-TYPE and MODULE-COMPLIANCE macros are somewhat
independent.
You write the OBJECT-TYPE macros for full conformance, and the "ReadOnly"
MODULE-COMPLAINCE
changes the requirement for RowStatus from read-create to read-only.

The full compliance compliance macro should not add MIN-ACCESS clauses.



> Managed entity still needs to support the RowStatus  as defined
> originally.   Plus, I would think the "correct" Compliance for the draft
> should include the
>
> support of Full Compliance for RowStatus of the relevant tables from TE
> MIB and LSR MIB (i.e. the relevant tables meaning those which are extended
> in the draft).
>
>
>
> (Probably more info that you want to know but...)
>
> Additionally, the TE and LSR MIBs have other MIBs (rfcs) in GMPLS and PWE
> which also extend tables from LSR MIB/TE MIB.   So, for 10  years these
> MIBs have been
>
> around, and there is a lot of legacy even in other WGs.
>
>
>
> I agree that there needs to be some discussion and thought around
> migration of MPLS management to NetConf for configuration.   The issue (as
> I see it) is that
>
> the LSR MIB contains a LIB (LSR table) and the TE MIB contains a Tunnel
> Table and these have been extended/Augmented in various MIBs and in various
> WGs for 10 years.
>
>
>
> Either the WGs can keep going with MIBs, or rewrite in NetConf.   To me,
> seems like everyone is focused on this draft, but not really focused on how
> best to help MPLS migrate.   (Not sure the WG even wants to migrate, so may
> have misspoken....)   Anyway, no matter what the decision is on the draft,
> that is still not going to help
>
> MPLS when new features are defined and folks still want to use the LIB and
> Tunnel Tables in rfc3813 and rfc3812.
>
>
>


After 10 years, any implementations of full read-create conformance?
If not, why bother publishing any new read-create objects at all?
Academic completeness?

I am not sure changing to NETCONF would help at this point.
CM is very intrusive to implement, unlike monitoring.  One can
add agent monitoring instrumentation on top of pre-existing instrumentation
anytime.  Adding new CM instrumentation on top of pre-existing CLI
can be complicated ( == expensive), especially if the data models are not
well aligned.


Thanks,
>
>   -Joan
>


Andy



>
>
> *From:* Andy Bierman [mailto:andy@yumaworks.com]
> *Sent:* Sunday, February 16, 2014 9:06 PM
> *To:* Joan Cucchiara
> *Cc:* Adrian Farrel; t.petch; Benoit Claise; MIB Doctors (E-mail)
> *Subject:* Re: [MIB-DOCTORS] configuration: writable MIB modules versus
> NETCONF/YANGmodules
>
>
>
> Hi,
>
>
>
> I guess I am confused as well, although I don't claim to know the details
> ;-)
>
>
>
> Looking at RFC 3812, there are 2 conformance statements:
>
>
>
>     mplsTeModuleFullCompliance
>     mplsTeModuleReadOnlyCompliance
>
>
>
> If an agent supports the "ReadOnly" MODULE-COMPLIANCE, then the RowStatus
>
> object is implemented read-only, hard-wired to active (i.e., the agent just populates
>
> the read-only table with the entries via some external configuration).
>
>
>
>
>
>          OBJECT      mplsTunnelRowStatus
>          SYNTAX      RowStatus { active(1) }
>          MIN-ACCESS  read-only
>          DESCRIPTION "Write access is not required."
>
>
>
> Why can't new objects added to the row also allow the server to only claim
>
> conformance to the read-only MODULE-COMPLIANCE?  I don't see the
>
> connection between RowStatus and a developer selecting which
>
> compliance level it will support in an implementation.
>
>
>
> It does not matter if the new objects are read-only or read-create.
>
> A "read-only" agent will magically instantiate the new columns,
>
> if it supports the extension. A "read-create" agent will allow
>
> a manager to create new rows, and allow the new r/c columns if
>
> it supports the extension.
>
>
>
>
>
> Andy
>
>
>
>
>
>
>
>
>
> On Sun, Feb 16, 2014 at 4:11 PM, Joan Cucchiara <jcucchiara@mindspring.com>
> wrote:
>
> Hi Adrian,
>
> Please see inline below prefaced with JEC >.
>
> -----Original Message-----
> From: Adrian Farrel [mailto:adrian@olddog.co.uk]
> Sent: Friday, February 14, 2014 2:19 PM
> To: 'Joan Cucchiara'; 't.petch'; 'Benoit Claise'; mib-doctors@ietf.org
> Subject: RE: configuration: writable MIB modules versus NETCONF/YANGmodules
>
> Hi Joan,
>
> [Reverting to the MIB Doctor Thread]
>
> I will bow to your far (far, far) superior understanding of MIB-speak.
>
> But I don't understand :-(
>
> A row in a table that has RowStatus can have read-only objects and
> writeable
> objects with Defaults as well as read-create objects.
> When you use, for example, CreateAndGo the whole row gets created with
> read-create objects as they are Set, with unSet writeable objects
> defaulting, and with read-only objects filled with values from the
> implementation.
>
> JEC > But that is kind of beside the point.   The LSR and TE MIBs (rfc3813
> and rfc3812, c. 2004) have two conformance statements, Full and Read-only.
> JEC >  Full Conformance allows for configuring with SNMP sets.   So this
> discussion is focusing on only the Full Conformance.
> JEC >  The RowStatus objects in the TE and LSR MIB Modules (rfc3813 and
> rfc3812) MUST be implemented as having  a MAX-ACCESS of read-create.   In
> other words,
> JEC > a row can be created or deleted, etc. because the agent processes an
> SNMP set request to configure the RowStatus object (i.e. a set is issued
> JEC > for create-and-go, destroy, etc).
>
> JEC > The point is that RowStatus  creates the row because of an SNMP set
> request.  (Certainly rows can be created other ways too.)
> JEC >  There is only ONE RowStatus for the entire row, and
> JEC > if that row is extended or AUGMENTed in additional MIB Modules, as in
> the case draft-ietf-mpls-tp-te-mib which extends rows in rfc3813 and
> rfc3812,
> JEC > then these extended rows are controlled ALSO by that same RowStatus
> object which was defined in the TE/LSR MIB Modules.
> JEC > There is only one RowStatus object which controls the entire row,
> even
> if parts
> JEC> of the row are in different MIB Modules (as with
> draft-ietf-mpls-tp-te-mib).    If you think about the case of deleting a
> row, this makes sense.
> JEC > If the RowStatus object in the TE MIB is set to "destroy", then the
> deletion of the entire row must happen, even if the objects of that row are
> in
> JEC > other MIB modules.
>
> When I extend a table, surely I can extend with objects that are all only
> read-only?
> Furthermore, the whole row in the extension table could be automatically
> created when the row in the extended table is created.
>
> What am I missing?
>
> JEC >  The agent  MUST "configure" (e.g. create the objects,  delete the
> objects) in  these extended rows  in this draft because of an SNMP set
> request.
> JEC >   I don't see any way around this, without redefining the RowStatus
> TC, or rewriting the TE or LSR MIBs or (probably the simplest solution) the
> JEC> co-authors write the draft in such a way as to not extend tables in
> the
> TE and LSR MIBs.
>
> JEC > So to summarize, an SNMP agent that supports this draft MUST support
> the SNMP set request for RowStatus for the rows which extend rows in
> JEC> the LSR and TE MIBs.
>
> JEC> Since that is the case, and since this draft is tied to these RFCs
> that
> are 10 years old now,  I don't have an issue
> JEC> with them configuring via SNMP for other objects also (but that is
> just
> my opinion).
>
> Thanks,
>   -Joan
>
>
>
> Thanks,
> Adrian
>
> > -----Original Message-----
> > From: OPS-AREA [mailto:ops-area-bounces@ietf.org] On Behalf Of Joan
> > Cucchiara
> > Sent: 14 February 2014 18:28
> > To: 't.petch'; 'Benoit Claise'; ops-area@ietf.org
> > Subject: Re: [OPS-AREA] configuration: writable MIB modules versus
> > NETCONF/YANGmodules
> >
> > Hi Tom,
> >
> > As the MIB Dr. on this draft,  I have responded on the MIB Dr. thread
> > that I do NOT see a way to make this draft (draft-ietf-mpls-tp-te-mib)
> read-only.
> > This draft contains extension tables for tables in LSR and TE MIBS which
> are
> > created by RowStatus (which is read-create).   Like it or not, RowStatus
> of
> > those MIBs (i.e. LSR and TE MIBs) effect the rows in the extension tables
> of
> > this draft (think the case of row creation or row deletion).   That is an
> > SNMP Set operation which effects the draft.
> >
> > I believe the statement that Benoit puts forth would allow for such a
> > situation as this draft, specifically:
> >
> > "... SNMP MIB modules modifying persistent configuration state  should
> > only be produced by working groups in cases of clear utility and
> > consensus to use SNMP write operations for configuration."
> >
> > Perhaps, additional wording, such as "For example, in the case of
> > proposed SNMP MIB modules which extend or augment rows that are
> > created by configuration in a SNMP MIB module which is already a RFC,
> > the proposed SNNP MIB modules will be grandfathered, if the working
> > group finds consensus to do so."
> >
> > However, I am okay with the statement as written.
> >
> > Thanks,
> >   -Joan
> >
> >
> > -----Original Message-----
> > From: OPS-AREA [mailto:ops-area-bounces@ietf.org] On Behalf Of t.petch
> > Sent: Friday, February 14, 2014 10:02 AM
> > To: Benoit Claise; ops-area@ietf.org
> > Subject: Re: [OPS-AREA] configuration: writable MIB modules versus
> > NETCONF/YANGmodules
> >
> > ----- Original Message -----
> > From: "Benoit Claise" <bclaise@cisco.com>
> > To: <ops-area@ietf.org>
> > Sent: Friday, February 14, 2014 12:39 AM
> > > Dear all,
> > >
> > > We occasionally see read-write MIB module proposals within the IETF.
> > > However, the write capabilities of those MIB modules are rarely
> > implemented.
> > >
> > > While discussing this issue with the MIB doctors, we arrive to the
> > > conclusion that it's now time to set the direction for future MIB
> > > developments within the IETF. Basically, let's not specify
> > > read-write MIB modules unless we have a good reason. Read-only MIB
> > > modules are still fine though, as SNMP is clearly used for monitoring
> purposes.
> > >
> > > Here is the statement we came up with:
> > >
> > >     The OPS area recommends the use of NETCONF/YANG standards for
> > >     configuration. IETF working groups are therefore encouraged to use
> > >     the NETCONF/YANG standards for configuration, specifically in new
> > >     charters. SNMP MIB modules modifying persistent configuration
> > state
> > >     should only be produced by working groups in cases of clear
> > utility
> > >     and consensus to use SNMP write operations for configuration.
> > >
> > > Ideally, this should become an IESG statement.
> > > Your feedback is most welcome.
> >
> > You probably know that there is currently a consensus call in progress
> > over
> >
> > "Please indicate Support or Oppose for this MIB
> > (draft-ietf-mpls-tp-te-mib) to be read-only."
> >
> > and I was pleasantly surprised to see opposition, albeit with one
> > opponent later changing their mind (perhaps they were sat on from a
> > height:-).  I don't see much sign of Netxxxx in the mpls arena but
> > there is a need there for configuration, since there need not be a
> control
> plane to set things up.
> > Perhaps writable MIB modules will still be with us in the distant
> > future in some corners of the Internet..
> >
> > Ideally, this idea would be fleshed out in an I-D.
> >
> > Tom Petch
> >
> > > Regards, the MIB doctors & Benoit
> >
> > _______________________________________________
> > OPS-AREA mailing list
> > OPS-AREA@ietf.org
> > https://www.ietf.org/mailman/listinfo/ops-area
> >
> >
> > -----
> > No virus found in this message.
> > Checked by AVG - www.avg.com
> > Version: 2014.0.4259 / Virus Database: 3705/7092 - Release Date:
> > 02/14/14
> >
> > _______________________________________________
> > OPS-AREA mailing list
> > OPS-AREA@ietf.org
> > https://www.ietf.org/mailman/listinfo/ops-area
>
>
>
> -----
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 2014.0.4259 / Virus Database: 3705/7092 - Release Date: 02/14/14
>
> _______________________________________________
> MIB-DOCTORS mailing list
> MIB-DOCTORS@ietf.org
> https://www.ietf.org/mailman/listinfo/mib-doctors
>
>
>
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 2014.0.4259 / Virus Database: 3705/7098 - Release Date: 02/16/14
> ------------------------------
>
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 2014.0.4259 / Virus Database: 3697/7083 - Release Date: 02/11/14
>

--001a1134541a3ebc2604f29c5056
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 Mon, Feb 17, 2014 at 7:09 AM, Joan Cucchiara <span dir=3D"ltr">&=
lt;<a href=3D"mailto:jcucchiara@mindspring.com" target=3D"_blank">jcucchiar=
a@mindspring.com</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 lang=3D"EN-US" link=3D"blue" vlink=3D"p=
urple"><div><p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-fam=
ily:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">Hi Andy,<u></=
u><u></u></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"><u></u>&nbsp;<u></u></spa=
n></p><p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&q=
uot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">The discussion is w=
rt FullCompliance only, sorry if that wasn&rsquo;t clear.&nbsp; &nbsp;&nbsp=
;<u></u><u></u></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"><u></u>&nbsp;<u></u></spa=
n></p><p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&q=
uot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">Even so, if RowStat=
us is defined as FullCompliance, doesn&rsquo;t that hold for new extended t=
able objects which are under the control of RowStatus with FullCompliance?<=
u></u><u></u></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"><u></u>&nbsp;</span></p><=
/div></div></blockquote><div><br></div><div><br></div><div>I think the OBJE=
CT-TYPE and MODULE-COMPLIANCE macros are somewhat independent.</div>
<div>You write the OBJECT-TYPE macros for full conformance, and the &quot;R=
eadOnly&quot; MODULE-COMPLAINCE</div><div>changes the requirement for RowSt=
atus from read-create to read-only.</div><div><br></div><div>The full compl=
iance compliance macro should not add MIN-ACCESS clauses.</div>
<div><br></div><div>&nbsp;<br></div><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div lan=
g=3D"EN-US" link=3D"blue" vlink=3D"purple"><div><p class=3D"MsoNormal"><spa=
n style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-seri=
f&quot;;color:#1f497d"><u></u></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">Managed entity still need=
s to support the RowStatus &nbsp;as defined originally.&nbsp;&nbsp; Plus, I=
 would think the &ldquo;correct&rdquo; Compliance for the draft should incl=
ude the <u></u><u></u></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">support of Full Complianc=
e for RowStatus of the relevant tables from TE MIB and LSR MIB (i.e. the re=
levant tables meaning those which are extended in the draft).<u></u><u></u>=
</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"><u></u>&nbsp;<u></u></spa=
n></p><p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&q=
uot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">(Probably more info=
 that you want to know but&hellip;)<u></u><u></u></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">Additionally, the TE and =
LSR MIBs have other MIBs (rfcs) in GMPLS and PWE which also extend tables f=
rom LSR MIB/TE MIB.&nbsp;&nbsp; So, for 10 &nbsp;years these MIBs have been=
<u></u><u></u></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">around, and there is a lo=
t of legacy even in other WGs.&nbsp;&nbsp;&nbsp; <u></u><u></u></span></p><=
p class=3D"MsoNormal">
<span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-=
serif&quot;;color:#1f497d"><u></u>&nbsp;<u></u></span></p><p class=3D"MsoNo=
rmal"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot=
;sans-serif&quot;;color:#1f497d">I agree that there needs to be some discus=
sion and thought around migration of MPLS management to NetConf for configu=
ration.&nbsp;&nbsp; The issue (as I see it) is that<u></u><u></u></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">the LSR MIB contains a LI=
B (LSR table) and the TE MIB contains a Tunnel Table and these have been ex=
tended/Augmented in various MIBs and in various WGs for 10 years.<u></u><u>=
</u></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"><u></u>&nbsp;<u></u></spa=
n></p><p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&q=
uot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">Either the WGs can =
keep going with MIBs, or rewrite in NetConf.&nbsp;&nbsp; To me, seems like =
everyone is focused on this draft, but not really focused on how best to he=
lp MPLS migrate.&nbsp;&nbsp; (Not sure the WG even wants to migrate, so may=
 have misspoken&hellip;.)&nbsp;&nbsp; Anyway, no matter what the decision i=
s on the draft, that is still not going to help<u></u><u></u></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">MPLS when new features ar=
e defined and folks still want to use the LIB and Tunnel Tables in rfc3813 =
and rfc3812.<u></u><u></u></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"><u></u>&nbsp;</span></p><=
/div></div></blockquote><div><br></div><div><br></div><div>After 10 years, =
any implementations of full read-create conformance?</div>
<div>If not, why bother publishing any new read-create objects at all?</div=
><div>Academic completeness?</div><div><br></div><div>I am not sure changin=
g to NETCONF would help at this point.</div><div>CM is very intrusive to im=
plement, unlike monitoring. &nbsp;One can</div>
<div>add agent monitoring instrumentation on top of pre-existing instrument=
ation</div><div>anytime. &nbsp;Adding new CM instrumentation on top of pre-=
existing CLI&nbsp;</div><div>can be complicated ( =3D=3D expensive), especi=
ally if the data models are not</div>
<div>well aligned.</div><div><br></div><div><br></div><blockquote class=3D"=
gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-=
left:1ex"><div lang=3D"EN-US" link=3D"blue" vlink=3D"purple"><div><p class=
=3D"MsoNormal">
<span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-=
serif&quot;;color:#1f497d"><u></u></span></p><p class=3D"MsoNormal"><span s=
tyle=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&q=
uot;;color:#1f497d">Thanks,<u></u><u></u></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">&nbsp; -Joan</span></p></=
div></div></blockquote><div><br></div><div><br></div><div>Andy</div><div><b=
r></div>
<div>&nbsp;</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8=
ex;border-left:1px #ccc solid;padding-left:1ex"><div lang=3D"EN-US" link=3D=
"blue" vlink=3D"purple"><div><p class=3D"MsoNormal"><span style=3D"font-siz=
e:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f49=
7d"><u></u><u></u></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"> <u></u><u></u></span></p=
><p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>&nbsp;<u></u></sp=
an></p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Andy Bie=
rman [mailto:<a href=3D"mailto:andy@yumaworks.com" target=3D"_blank">andy@y=
umaworks.com</a>] <br>
<b>Sent:</b> Sunday, February 16, 2014 9:06 PM<br><b>To:</b> Joan Cucchiara=
<br><b>Cc:</b> Adrian Farrel; t.petch; Benoit Claise; MIB Doctors (E-mail)<=
br><b>Subject:</b> Re: [MIB-DOCTORS] configuration: writable MIB modules ve=
rsus NETCONF/YANGmodules<u></u><u></u></span></p>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p><div><p class=3D"MsoNormal">=
Hi,<u></u><u></u></p><div><p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p></=
div><div><p class=3D"MsoNormal">I guess I am confused as well, although I d=
on&#39;t claim to know the details ;-)<u></u><u></u></p>
</div><div><p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p></div><div><p cla=
ss=3D"MsoNormal">Looking at RFC 3812, there are 2 conformance statements:<u=
></u><u></u></p></div><div><p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p><=
/div><p class=3D"MsoNormal">
&nbsp; &nbsp; mplsTeModuleFullCompliance<br>&nbsp;&nbsp;&nbsp; mplsTeModule=
ReadOnlyCompliance<u></u><u></u></p><div><p class=3D"MsoNormal"><u></u>&nbs=
p;<u></u></p><div><pre><span style=3D"font-size:12.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;;color:#222222">If an agent supports the &q=
uot;ReadOnly&quot; MODULE-COMPLIANCE, then the RowStatus</span><span style=
=3D"font-size:12.0pt"><br>
<br><u></u><u></u></span></pre><pre><span style=3D"font-size:12.0pt;font-fa=
mily:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#222222">object is impl=
emented read-only, hard-wired to active (i.e., the agent just populates</sp=
an><span style=3D"font-size:12.0pt"><u></u><u></u></span></pre>
<pre><span style=3D"font-size:12.0pt;font-family:&quot;Arial&quot;,&quot;sa=
ns-serif&quot;;color:#222222">the read-only table with the entries via some=
 external configuration).</span><span style=3D"font-size:12.0pt"><u></u><u>=
</u></span></pre>
<pre><span style=3D"font-size:12.0pt"><u></u>&nbsp;<u></u></span></pre><pre=
><span style=3D"font-size:12.0pt"><u></u>&nbsp;<u></u></span></pre><p class=
=3D"MsoNormal">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;OBJECT &nbsp; &nbsp; &nbsp=
;mplsTunnelRowStatus<br>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;SYNTAX &nbsp; &nb=
sp; &nbsp;RowStatus { active(1) }<br>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;MIN-ACCESS &nbsp;read-only<br>&nbsp; &nbs=
p; &nbsp; &nbsp; &nbsp;DESCRIPTION &quot;Write access is not required.&quot=
;<u></u><u></u></p></div></div><div><p class=3D"MsoNormal"><u></u>&nbsp;<u>=
</u></p></div><div><p class=3D"MsoNormal">Why can&#39;t new objects added t=
o the row also allow the server to only claim<u></u><u></u></p>
</div><div><p class=3D"MsoNormal">conformance to the read-only MODULE-COMPL=
IANCE? &nbsp;I don&#39;t see the<u></u><u></u></p></div><div><p class=3D"Ms=
oNormal">connection between RowStatus and a developer selecting which<u></u=
><u></u></p>
</div><div><p class=3D"MsoNormal">compliance level it will support in an im=
plementation.<u></u><u></u></p></div><div><p class=3D"MsoNormal"><u></u>&nb=
sp;<u></u></p></div><div><p class=3D"MsoNormal">It does not matter if the n=
ew objects are read-only or read-create.<u></u><u></u></p>
</div><div><p class=3D"MsoNormal">A &quot;read-only&quot; agent will magica=
lly instantiate the new columns,<u></u><u></u></p></div><div><p class=3D"Ms=
oNormal">if it supports the extension. A &quot;read-create&quot; agent will=
 allow<u></u><u></u></p>
</div><div><p class=3D"MsoNormal">a manager to create new rows, and allow t=
he new r/c columns if<u></u><u></u></p></div><div><p class=3D"MsoNormal">it=
 supports the extension.<u></u><u></u></p></div><div><p class=3D"MsoNormal"=
><u></u>&nbsp;<u></u></p>
</div><div><p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p></div><div><p cla=
ss=3D"MsoNormal">Andy<u></u><u></u></p></div><div><p class=3D"MsoNormal"><u=
></u>&nbsp;<u></u></p></div><div><p class=3D"MsoNormal"><u></u>&nbsp;<u></u=
></p></div><div><p class=3D"MsoNormal">
<u></u>&nbsp;<u></u></p></div><div><p class=3D"MsoNormal"><u></u>&nbsp;<u><=
/u></p><div><p class=3D"MsoNormal">On Sun, Feb 16, 2014 at 4:11 PM, Joan Cu=
cchiara &lt;<a href=3D"mailto:jcucchiara@mindspring.com" target=3D"_blank">=
jcucchiara@mindspring.com</a>&gt; wrote:<u></u><u></u></p>
<p class=3D"MsoNormal">Hi Adrian,<br><br>Please see inline below prefaced w=
ith JEC &gt;.<br><br>-----Original Message-----<br>From: Adrian Farrel [mai=
lto:<a href=3D"mailto:adrian@olddog.co.uk" target=3D"_blank">adrian@olddog.=
co.uk</a>]<br>
Sent: Friday, February 14, 2014 2:19 PM<br>To: &#39;Joan Cucchiara&#39;; &#=
39;t.petch&#39;; &#39;Benoit Claise&#39;; <a href=3D"mailto:mib-doctors@iet=
f.org" target=3D"_blank">mib-doctors@ietf.org</a><br>Subject: RE: configura=
tion: writable MIB modules versus NETCONF/YANGmodules<br>
<br>Hi Joan,<br><br>[Reverting to the MIB Doctor Thread]<br><br>I will bow =
to your far (far, far) superior understanding of MIB-speak.<br><br>But I do=
n&#39;t understand :-(<br><br>A row in a table that has RowStatus can have =
read-only objects and writeable<br>
objects with Defaults as well as read-create objects.<br>When you use, for =
example, CreateAndGo the whole row gets created with<br>read-create objects=
 as they are Set, with unSet writeable objects<br>defaulting, and with read=
-only objects filled with values from the<br>
implementation.<br><br>JEC &gt; But that is kind of beside the point. &nbsp=
; The LSR and TE MIBs (rfc3813<br>and rfc3812, c. 2004) have two conformanc=
e statements, Full and Read-only.<br>JEC &gt; &nbsp;Full Conformance allows=
 for configuring with SNMP sets. &nbsp; So this<br>
discussion is focusing on only the Full Conformance.<br>JEC &gt; &nbsp;The =
RowStatus objects in the TE and LSR MIB Modules (rfc3813 and<br>rfc3812) MU=
ST be implemented as having &nbsp;a MAX-ACCESS of read-create. &nbsp; In<br=
>other words,<br>
JEC &gt; a row can be created or deleted, etc. because the agent processes =
an<br>SNMP set request to configure the RowStatus object (i.e. a set is iss=
ued<br>JEC &gt; for create-and-go, destroy, etc).<br><br>JEC &gt; The point=
 is that RowStatus &nbsp;creates the row because of an SNMP set<br>
request. &nbsp;(Certainly rows can be created other ways too.)<br>JEC &gt; =
&nbsp;There is only ONE RowStatus for the entire row, and<br>JEC &gt; if th=
at row is extended or AUGMENTed in additional MIB Modules, as in<br>the cas=
e draft-ietf-mpls-tp-te-mib which extends rows in rfc3813 and<br>
rfc3812,<br>JEC &gt; then these extended rows are controlled ALSO by that s=
ame RowStatus<br>object which was defined in the TE/LSR MIB Modules.<br>JEC=
 &gt; There is only one RowStatus object which controls the entire row, eve=
n<br>
if parts<br>JEC&gt; of the row are in different MIB Modules (as with<br>dra=
ft-ietf-mpls-tp-te-mib). &nbsp; &nbsp;If you think about the case of deleti=
ng a<br>row, this makes sense.<br>JEC &gt; If the RowStatus object in the T=
E MIB is set to &quot;destroy&quot;, then the<br>
deletion of the entire row must happen, even if the objects of that row are=
<br>in<br>JEC &gt; other MIB modules.<br><br>When I extend a table, surely =
I can extend with objects that are all only<br>read-only?<br>Furthermore, t=
he whole row in the extension table could be automatically<br>
created when the row in the extended table is created.<br><br>What am I mis=
sing?<br><br>JEC &gt; &nbsp;The agent &nbsp;MUST &quot;configure&quot; (e.g=
. create the objects, &nbsp;delete the<br>objects) in &nbsp;these extended =
rows &nbsp;in this draft because of an SNMP set<br>
request.<br>JEC &gt; &nbsp; I don&#39;t see any way around this, without re=
defining the RowStatus<br>TC, or rewriting the TE or LSR MIBs or (probably =
the simplest solution) the<br>JEC&gt; co-authors write the draft in such a =
way as to not extend tables in the<br>
TE and LSR MIBs.<br><br>JEC &gt; So to summarize, an SNMP agent that suppor=
ts this draft MUST support<br>the SNMP set request for RowStatus for the ro=
ws which extend rows in<br>JEC&gt; the LSR and TE MIBs.<br><br>JEC&gt; Sinc=
e that is the case, and since this draft is tied to these RFCs that<br>
are 10 years old now, &nbsp;I don&#39;t have an issue<br>JEC&gt; with them =
configuring via SNMP for other objects also (but that is just<br>my opinion=
).<br><br>Thanks,<br>&nbsp; -Joan<br><br><br><br>Thanks,<br>Adrian<br><br>&=
gt; -----Original Message-----<br>
&gt; From: OPS-AREA [mailto:<a href=3D"mailto:ops-area-bounces@ietf.org" ta=
rget=3D"_blank">ops-area-bounces@ietf.org</a>] On Behalf Of Joan<br>&gt; Cu=
cchiara<br>&gt; Sent: 14 February 2014 18:28<br>&gt; To: &#39;t.petch&#39;;=
 &#39;Benoit Claise&#39;; <a href=3D"mailto:ops-area@ietf.org" target=3D"_b=
lank">ops-area@ietf.org</a><br>
&gt; Subject: Re: [OPS-AREA] configuration: writable MIB modules versus<br>=
&gt; NETCONF/YANGmodules<br>&gt;<br>&gt; Hi Tom,<br>&gt;<br>&gt; As the MIB=
 Dr. on this draft, &nbsp;I have responded on the MIB Dr. thread<br>&gt; th=
at I do NOT see a way to make this draft (draft-ietf-mpls-tp-te-mib)<br>
read-only.<br>&gt; This draft contains extension tables for tables in LSR a=
nd TE MIBS which<br>are<br>&gt; created by RowStatus (which is read-create)=
. &nbsp; Like it or not, RowStatus<br>of<br>&gt; those MIBs (i.e. LSR and T=
E MIBs) effect the rows in the extension tables<br>
of<br>&gt; this draft (think the case of row creation or row deletion). &nb=
sp; That is an<br>&gt; SNMP Set operation which effects the draft.<br>&gt;<=
br>&gt; I believe the statement that Benoit puts forth would allow for such=
 a<br>
&gt; situation as this draft, specifically:<br>&gt;<br>&gt; &quot;... SNMP =
MIB modules modifying persistent configuration state &nbsp;should<br>&gt; o=
nly be produced by working groups in cases of clear utility and<br>&gt; con=
sensus to use SNMP write operations for configuration.&quot;<br>
&gt;<br>&gt; Perhaps, additional wording, such as &quot;For example, in the=
 case of<br>&gt; proposed SNMP MIB modules which extend or augment rows tha=
t are<br>&gt; created by configuration in a SNMP MIB module which is alread=
y a RFC,<br>
&gt; the proposed SNNP MIB modules will be grandfathered, if the working<br=
>&gt; group finds consensus to do so.&quot;<br>&gt;<br>&gt; However, I am o=
kay with the statement as written.<br>&gt;<br>&gt; Thanks,<br>&gt; &nbsp; -=
Joan<br>
&gt;<br>&gt;<br>&gt; -----Original Message-----<br>&gt; From: OPS-AREA [mai=
lto:<a href=3D"mailto:ops-area-bounces@ietf.org" target=3D"_blank">ops-area=
-bounces@ietf.org</a>] On Behalf Of t.petch<br>&gt; Sent: Friday, February =
14, 2014 10:02 AM<br>
&gt; To: Benoit Claise; <a href=3D"mailto:ops-area@ietf.org" target=3D"_bla=
nk">ops-area@ietf.org</a><br>&gt; Subject: Re: [OPS-AREA] configuration: wr=
itable MIB modules versus<br>&gt; NETCONF/YANGmodules<br>&gt;<br>&gt; -----=
 Original Message -----<br>
&gt; From: &quot;Benoit Claise&quot; &lt;<a href=3D"mailto:bclaise@cisco.co=
m" target=3D"_blank">bclaise@cisco.com</a>&gt;<br>&gt; To: &lt;<a href=3D"m=
ailto:ops-area@ietf.org" target=3D"_blank">ops-area@ietf.org</a>&gt;<br>&gt=
; Sent: Friday, February 14, 2014 12:39 AM<br>
&gt; &gt; Dear all,<br>&gt; &gt;<br>&gt; &gt; We occasionally see read-writ=
e MIB module proposals within the IETF.<br>&gt; &gt; However, the write cap=
abilities of those MIB modules are rarely<br>&gt; implemented.<br>&gt; &gt;=
<br>
&gt; &gt; While discussing this issue with the MIB doctors, we arrive to th=
e<br>&gt; &gt; conclusion that it&#39;s now time to set the direction for f=
uture MIB<br>&gt; &gt; developments within the IETF. Basically, let&#39;s n=
ot specify<br>
&gt; &gt; read-write MIB modules unless we have a good reason. Read-only MI=
B<br>&gt; &gt; modules are still fine though, as SNMP is clearly used for m=
onitoring<br>purposes.<br>&gt; &gt;<br>&gt; &gt; Here is the statement we c=
ame up with:<br>
&gt; &gt;<br>&gt; &gt; &nbsp; &nbsp; The OPS area recommends the use of NET=
CONF/YANG standards for<br>&gt; &gt; &nbsp; &nbsp; configuration. IETF work=
ing groups are therefore encouraged to use<br>&gt; &gt; &nbsp; &nbsp; the N=
ETCONF/YANG standards for configuration, specifically in new<br>
&gt; &gt; &nbsp; &nbsp; charters. SNMP MIB modules modifying persistent con=
figuration<br>&gt; state<br>&gt; &gt; &nbsp; &nbsp; should only be produced=
 by working groups in cases of clear<br>&gt; utility<br>&gt; &gt; &nbsp; &n=
bsp; and consensus to use SNMP write operations for configuration.<br>
&gt; &gt;<br>&gt; &gt; Ideally, this should become an IESG statement.<br>&g=
t; &gt; Your feedback is most welcome.<br>&gt;<br>&gt; You probably know th=
at there is currently a consensus call in progress<br>&gt; over<br>&gt;<br>
&gt; &quot;Please indicate Support or Oppose for this MIB<br>&gt; (draft-ie=
tf-mpls-tp-te-mib) to be read-only.&quot;<br>&gt;<br>&gt; and I was pleasan=
tly surprised to see opposition, albeit with one<br>&gt; opponent later cha=
nging their mind (perhaps they were sat on from a<br>
&gt; height:-). &nbsp;I don&#39;t see much sign of Netxxxx in the mpls aren=
a but<br>&gt; there is a need there for configuration, since there need not=
 be a control<br>plane to set things up.<br>&gt; Perhaps writable MIB modul=
es will still be with us in the distant<br>
&gt; future in some corners of the Internet..<br>&gt;<br>&gt; Ideally, this=
 idea would be fleshed out in an I-D.<br>&gt;<br>&gt; Tom Petch<br>&gt;<br>=
&gt; &gt; Regards, the MIB doctors &amp; Benoit<br>&gt;<br>&gt; ___________=
____________________________________<br>
&gt; OPS-AREA mailing list<br>&gt; <a href=3D"mailto:OPS-AREA@ietf.org" tar=
get=3D"_blank">OPS-AREA@ietf.org</a><br>&gt; <a href=3D"https://www.ietf.or=
g/mailman/listinfo/ops-area" target=3D"_blank">https://www.ietf.org/mailman=
/listinfo/ops-area</a><br>
&gt;<br>&gt;<br>&gt; -----<br>&gt; No virus found in this message.<br>&gt; =
Checked by AVG - <a href=3D"http://www.avg.com" target=3D"_blank">www.avg.c=
om</a><br>&gt; Version: 2014.0.4259 / Virus Database: 3705/7092 - Release D=
ate:<br>
&gt; 02/14/14<br>&gt;<br>&gt; _____________________________________________=
__<br>&gt; OPS-AREA mailing list<br>&gt; <a href=3D"mailto:OPS-AREA@ietf.or=
g" target=3D"_blank">OPS-AREA@ietf.org</a><br>&gt; <a href=3D"https://www.i=
etf.org/mailman/listinfo/ops-area" target=3D"_blank">https://www.ietf.org/m=
ailman/listinfo/ops-area</a><br>
<br><br><br>-----<br>No virus found in this message.<br>Checked by AVG - <a=
 href=3D"http://www.avg.com" target=3D"_blank">www.avg.com</a><br>Version: =
2014.0.4259 / Virus Database: 3705/7092 - Release Date: 02/14/14<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/mai=
lman/listinfo/mib-doctors" target=3D"_blank">https://www.ietf.org/mailman/l=
istinfo/mib-doctors</a><u></u><u></u></p>
</div><p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p></div></div><p class=
=3D"MsoNormal">No virus found in this message.<br>Checked by AVG - <a href=
=3D"http://www.avg.com" target=3D"_blank">www.avg.com</a><br>Version: 2014.=
0.4259 / Virus Database: 3705/7098 - Release Date: 02/16/14<u></u><u></u></=
p>
<div class=3D"MsoNormal" align=3D"center" style=3D"text-align:center"><hr s=
ize=3D"1" width=3D"100%" noshade style=3D"color:#a0a0a0" align=3D"center"><=
/div><p class=3D"MsoNormal">No virus found in this message.<br>Checked by A=
VG - <a href=3D"http://www.avg.com" target=3D"_blank">www.avg.com</a><br>
Version: 2014.0.4259 / Virus Database: 3697/7083 - Release Date: 02/11/14<u=
></u><u></u></p></div></div></blockquote></div><br></div></div>

--001a1134541a3ebc2604f29c5056--


From nobody Tue Feb 18 06:12:07 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 D97C61A0679 for <mib-doctors@ietfa.amsl.com>; Tue, 18 Feb 2014 06:12:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.848
X-Spam-Level: 
X-Spam-Status: No, score=-1.848 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_15=0.6, RP_MATCHES_RCVD=-0.548] 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 1EAEALFGM8Lp for <mib-doctors@ietfa.amsl.com>; Tue, 18 Feb 2014 06:12:00 -0800 (PST)
Received: from lucidvision.com (lucidvision.com [72.71.250.34]) by ietfa.amsl.com (Postfix) with ESMTP id 706DA1A067B for <mib-doctors@ietf.org>; Tue, 18 Feb 2014 06:11:56 -0800 (PST)
Received: from [192.168.1.122] (static-72-71-250-38.cncdnh.fast04.myfairpoint.net [72.71.250.38]) by lucidvision.com (Postfix) with ESMTP id 63A8A26F7B0D; Tue, 18 Feb 2014 09:11:53 -0500 (EST)
Content-Type: multipart/signed; boundary="Apple-Mail=_2B76B5EE-FA7A-4503-837F-1DD1A6B1C083"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Thomas Nadeau <tnadeau@lucidvision.com>
In-Reply-To: <9904FB1B0159DA42B0B887B7FA8119CA2E41AF25@AZ-FFEXMB04.global.avaya.com>
Date: Tue, 18 Feb 2014 09:11:52 -0500
Message-Id: <E73A794D-26D6-47B4-89EC-2F49DBD51770@lucidvision.com>
References: <00b101cf29b9$95d979e0$c18c6da0$@olddog.co.uk> <9904FB1B0159DA42B0B887B7FA8119CA2E4187BC@AZ-FFEXMB04.global.avaya.com> <013501cf2b41$4d26a2c0$e773e840$@olddog.co.uk> <9904FB1B0159DA42B0B887B7FA8119CA2E41AF25@AZ-FFEXMB04.global.avaya.com>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
X-Mailer: Apple Mail (2.1827)
Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/ZufyocVowSpUo7M2F4kcSzjxZUc
Cc: Farrel Adrian <adrian@olddog.co.uk>, "t.petch" <ietfc@btconnect.com>, "mib-doctors@ietf.org" <mib-doctors@ietf.org>
Subject: Re: [MIB-DOCTORS] configuration: writable MIB modules versus NETCONF/YANGmodules
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, 18 Feb 2014 14:12:06 -0000

--Apple-Mail=_2B76B5EE-FA7A-4503-837F-1DD1A6B1C083
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


	I am not sure as you cannot create rows in the new MIB module =
(call it B); they're created in the existing one (call it A) and as a =
side-effect objects are created in B, which is normal agent behavior in =
an "all writable" situation today.  We should point out that this occurs =
in both cases of AUGMENTSs and "extends" rows.  I do not see any issue =
with this as the behavior is as expected:

	So if I "row create new row in A" -> the system creates an entry =
in A, and row is created in B that corresponds. When you query A or B, =
you get responses.  Row destruction happens consistently too since you =
cannot issue row destruction instructions to B, but only to A, and =
corresponding entries in B are removed.  Of course, if I try a row =
create on B it fails.=20

	The other way to look at this is that this is the same situation =
as if we had the ability to configure A as read-write/create and B as =
read-only (where B contained read-write/create entries).  The exact same =
behavior should result.

	--tom




On Feb 16, 2014:2:45 PM, at 2:45 PM, Romascanu, Dan (Dan) =
<dromasca@avaya.com> wrote:

> By using the already existing RowStatus object in the base table the =
creation of new rows in the base table leads to the creation of new rows =
in the extended table. Even if the objects that you defined are all =
read-only, the effect is the same as defining a new table with a =
RowStatus object.=20
>=20
> Dan
>=20
>=20
>> -----Original Message-----
>> From: Adrian Farrel [mailto:adrian@olddog.co.uk]
>> Sent: Sunday, February 16, 2014 8:03 PM
>> To: Romascanu, Dan (Dan); 'Joan Cucchiara'; 't.petch'; 'Benoit =
Claise'; mib-
>> doctors@ietf.org
>> Subject: RE: [MIB-DOCTORS] configuration: writable MIB modules versus
>> NETCONF/YANGmodules
>>=20
>> I'm sorry if I am being thick.
>>=20
>> The row in the old table has a RowStatus object which is, of course, =
read-
>> create.
>> The extension table entry has no object with SYNTAX rowStatus, but is
>> created automatically when the entry in the old table is created.
>>=20
>> A
>>=20
>>> -----Original Message-----
>>> From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com]
>>> Sent: 16 February 2014 11:55
>>> To: adrian@olddog.co.uk; 'Joan Cucchiara'; 't.petch'; 'Benoit =
Claise';
>>> mib- doctors@ietf.org
>>> Subject: RE: [MIB-DOCTORS] configuration: writable MIB modules =
versus
>>> NETCONF/YANGmodules
>>>=20
>>> Hi Adrian,
>>>=20
>>> Even if the row you extend is composed only by objects with =
MAX-ACCESS
>>> read- only, creating a new row involves a write operation on the
>>> object with SYNTAX RowStatus.
>>>=20
>>> This is (I guess) what Joan meant.
>>>=20
>>> Creating a new row may mean a modification of configuration on the
>>> managed entity. You now have n+1 rows instead of n rows in the =
table.
>>>=20
>>> Regards,
>>>=20
>>> Dan
>>>=20
>>>=20
>>>> -----Original Message-----
>>>> From: MIB-DOCTORS [mailto:mib-doctors-bounces@ietf.org] On Behalf
>> Of
>>>> Adrian Farrel
>>>> Sent: Friday, February 14, 2014 9:19 PM
>>>> To: 'Joan Cucchiara'; 't.petch'; 'Benoit Claise';
>>>> mib-doctors@ietf.org
>>>> Subject: Re: [MIB-DOCTORS] configuration: writable MIB modules
>>>> versus NETCONF/YANGmodules
>>>>=20
>>>> Hi Joan,
>>>>=20
>>>> [Reverting to the MIB Doctor Thread]
>>>>=20
>>>> I will bow to your far (far, far) superior understanding of =
MIB-speak.
>>>>=20
>>>> But I don't understand :-(
>>>>=20
>>>> A row in a table that has RowStatus can have read-only objects and
>>>> writeable objects with Defaults as well as read-create objects.
>>>> When you use, for example, CreateAndGo the whole row gets created
>>>> with read-create objects as they are Set, with unSet writeable
>>>> objects
>> defaulting,
>>>> and with read-only objects filled with values from the =
implementation.
>>>>=20
>>>> When I extend a table, surely I can extend with objects that are =
all
>>>> only
>> read-
>>>> only?
>>>> Furthermore, the whole row in the extension table could be
>>>> automatically created when the row in the extended table is =
created.
>>>>=20
>>>> What am I missing?
>>>>=20
>>>> Thanks,
>>>> Adrian
>>>>=20
>>>>> -----Original Message-----
>>>>> From: OPS-AREA [mailto:ops-area-bounces@ietf.org] On Behalf Of
>>>>> Joan Cucchiara
>>>>> Sent: 14 February 2014 18:28
>>>>> To: 't.petch'; 'Benoit Claise'; ops-area@ietf.org
>>>>> Subject: Re: [OPS-AREA] configuration: writable MIB modules versus
>>>>> NETCONF/YANGmodules
>>>>>=20
>>>>> Hi Tom,
>>>>>=20
>>>>> As the MIB Dr. on this draft,  I have responded on the MIB Dr.
>>>>> thread that I do NOT see a way to make this draft
>>>>> (draft-ietf-mpls-tp-te-mib)
>> read-
>>>> only.
>>>>> This draft contains extension tables for tables in LSR and TE MIBS
>>>>> which
>> are
>>>>> created by RowStatus (which is read-create).   Like it or not, =
RowStatus
>> of
>>>>> those MIBs (i.e. LSR and TE MIBs) effect the rows in the extension
>>>>> tables
>> of
>>>>> this draft (think the case of row creation or row deletion).   =
That is an
>>>>> SNMP Set operation which effects the draft.
>>>>>=20
>>>>> I believe the statement that Benoit puts forth would allow for
>>>>> such a situation as this draft, specifically:
>>>>>=20
>>>>> "... SNMP MIB modules modifying persistent configuration state
>>>>> should only be produced by working groups in cases of clear
>>>>> utility and consensus to use SNMP write operations for =
configuration."
>>>>>=20
>>>>> Perhaps, additional wording, such as "For example, in the case of
>>>>> proposed SNMP MIB modules which extend or augment rows that are
>>>>> created by configuration in a SNMP MIB module which is already a
>>>>> RFC, the proposed SNNP MIB modules will be grandfathered, if the
>>>>> working group finds consensus to do so."
>>>>>=20
>>>>> However, I am okay with the statement as written.
>>>>>=20
>>>>> Thanks,
>>>>>  -Joan
>>>>>=20
>>>>>=20
>>>>> -----Original Message-----
>>>>> From: OPS-AREA [mailto:ops-area-bounces@ietf.org] On Behalf Of
>>>>> t.petch
>>>>> Sent: Friday, February 14, 2014 10:02 AM
>>>>> To: Benoit Claise; ops-area@ietf.org
>>>>> Subject: Re: [OPS-AREA] configuration: writable MIB modules versus
>>>>> NETCONF/YANGmodules
>>>>>=20
>>>>> ----- Original Message -----
>>>>> From: "Benoit Claise" <bclaise@cisco.com>
>>>>> To: <ops-area@ietf.org>
>>>>> Sent: Friday, February 14, 2014 12:39 AM
>>>>>> Dear all,
>>>>>>=20
>>>>>> We occasionally see read-write MIB module proposals within the =
IETF.
>>>>>> However, the write capabilities of those MIB modules are rarely
>>>>> implemented.
>>>>>>=20
>>>>>> While discussing this issue with the MIB doctors, we arrive to
>>>>>> the conclusion that it's now time to set the direction for
>>>>>> future MIB developments within the IETF. Basically, let's not
>>>>>> specify read-write MIB modules unless we have a good reason.
>>>>>> Read-only MIB modules are still fine though, as SNMP is clearly
>>>>>> used for monitoring
>>>> purposes.
>>>>>>=20
>>>>>> Here is the statement we came up with:
>>>>>>=20
>>>>>>    The OPS area recommends the use of NETCONF/YANG standards
>> for
>>>>>>    configuration. IETF working groups are therefore encouraged to =
use
>>>>>>    the NETCONF/YANG standards for configuration, specifically in =
new
>>>>>>    charters. SNMP MIB modules modifying persistent
>>>>>> configuration
>>>>> state
>>>>>>    should only be produced by working groups in cases of clear
>>>>> utility
>>>>>>    and consensus to use SNMP write operations for configuration.
>>>>>>=20
>>>>>> Ideally, this should become an IESG statement.
>>>>>> Your feedback is most welcome.
>>>>>=20
>>>>> You probably know that there is currently a consensus call in
>>>>> progress over
>>>>>=20
>>>>> "Please indicate Support or Oppose for this MIB
>>>>> (draft-ietf-mpls-tp-te-mib) to be read-only."
>>>>>=20
>>>>> and I was pleasantly surprised to see opposition, albeit with one
>>>>> opponent later changing their mind (perhaps they were sat on from
>>>>> a height:-).  I don't see much sign of Netxxxx in the mpls arena
>>>>> but there is a need there for configuration, since there need not
>>>>> be a control
>>>> plane to set things up.
>>>>> Perhaps writable MIB modules will still be with us in the distant
>>>>> future in some corners of the Internet..
>>>>>=20
>>>>> Ideally, this idea would be fleshed out in an I-D.
>>>>>=20
>>>>> Tom Petch
>>>>>=20
>>>>>> Regards, the MIB doctors & Benoit
>>>>>=20
>>>>> _______________________________________________
>>>>> OPS-AREA mailing list
>>>>> OPS-AREA@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/ops-area
>>>>>=20
>>>>>=20
>>>>> -----
>>>>> No virus found in this message.
>>>>> Checked by AVG - www.avg.com
>>>>> Version: 2014.0.4259 / Virus Database: 3705/7092 - Release Date:
>>>>> 02/14/14
>>>>>=20
>>>>> _______________________________________________
>>>>> OPS-AREA mailing list
>>>>> OPS-AREA@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/ops-area
>>>>=20
>>>> _______________________________________________
>>>> MIB-DOCTORS mailing list
>>>> MIB-DOCTORS@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/mib-doctors
>=20
> _______________________________________________
> MIB-DOCTORS mailing list
> MIB-DOCTORS@ietf.org
> https://www.ietf.org/mailman/listinfo/mib-doctors
>=20


--Apple-Mail=_2B76B5EE-FA7A-4503-837F-1DD1A6B1C083
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

iQIcBAEBCgAGBQJTA2ooAAoJEPcO+I7eiUJZlt0QAIErQW3xTNz7S6CHbVOWOoHP
ER6qwR4ElXX2iMTeK6EqzjNeD3R89NlqpMvjD7EYTFdivCJKfqEzjjEV4ogpLyvc
Q78IhZzUdxopqNJLhVzFd32bu4xUoEkKCoz/lJtF1bPfjc/gfzXPGFVgK4nqGlAs
5bLfGDZv3sIVBp/9OXxstSXss27TINyzbBTwoDrTwHdS+3PqfeSd03Y4GSyGLD8I
UtJRzhw4H5BhIrhWDKzJRYU87qwF15MH2YY5XIhKTtCh/kZyjDgHSHGD7qEbj2l/
QndWbBQRTCEGHdsYrJ/XtnOaC/iQQxSx8eKmW3pozJ/eyV8h8zSVzHe9LILYKnvj
x3t59NGRZHBHRJcEe8ROZDpU1wef5Y9paUo8ujrh5ti52uFPoaPYoSCL3wytwN6W
kMAm6LfOWFSLK4skMlOlph9hpc7I+LVEt44dsKa/htEErqlwikpTFa9fBgp9jsl4
lSA1fxKybkPKrE6XxgjdWsn5+Hfb4FaTzg3biH2HNDeyPeIVy2rvWl01Haw3IVA8
RYkc7otKHdfRC5YVB1ujheGoYMik14zspUREbMqinCmbGFP4JyGsf6DypvRh3GqM
6abmrO4fh9xL+eqS9A8hVJfe7aQ+SmrBu2xdthwqWiPdMXPgqrP5TXLKAMMpmGls
O1qkqVWevJKVaB4IPl3Z
=MrM9
-----END PGP SIGNATURE-----

--Apple-Mail=_2B76B5EE-FA7A-4503-837F-1DD1A6B1C083--


From nobody Tue Feb 18 06:15:19 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 CAEC51A064A for <mib-doctors@ietfa.amsl.com>; Tue, 18 Feb 2014 06:15:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.848
X-Spam-Level: 
X-Spam-Status: No, score=-1.848 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_15=0.6, RP_MATCHES_RCVD=-0.548] 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 A8ZpMIAwscSn for <mib-doctors@ietfa.amsl.com>; Tue, 18 Feb 2014 06:15:13 -0800 (PST)
Received: from lucidvision.com (lucidvision.com [72.71.250.34]) by ietfa.amsl.com (Postfix) with ESMTP id B321A1A04D7 for <mib-doctors@ietf.org>; Tue, 18 Feb 2014 06:15:11 -0800 (PST)
Received: from [192.168.1.122] (static-72-71-250-38.cncdnh.fast04.myfairpoint.net [72.71.250.38]) by lucidvision.com (Postfix) with ESMTP id B62DA26F7B48; Tue, 18 Feb 2014 09:15:08 -0500 (EST)
Content-Type: multipart/signed; boundary="Apple-Mail=_E44F98CD-04D7-461A-91DA-8C9053E0AB02"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Thomas Nadeau <tnadeau@lucidvision.com>
In-Reply-To: <029901cf2b74$d9d74c00$8d85e400$@mindspring.com>
Date: Tue, 18 Feb 2014 09:15:08 -0500
Message-Id: <2244EB0E-11CF-4B10-9C33-434EAB7D576B@lucidvision.com>
References: <00b101cf29b9$95d979e0$c18c6da0$@olddog.co.uk> <029901cf2b74$d9d74c00$8d85e400$@mindspring.com>
To: Cucchiara Joan <jcucchiara@mindspring.com>
X-Mailer: Apple Mail (2.1827)
Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/K-dR_0oAyyuod53aS8anx9Rzhqk
Cc: Farrel Adrian <adrian@olddog.co.uk>, "t.petch" <ietfc@btconnect.com>, MIB Doctors <mib-doctors@ietf.org>
Subject: Re: [MIB-DOCTORS] configuration: writable MIB modules versus NETCONF/YANGmodules
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, 18 Feb 2014 14:15:18 -0000

--Apple-Mail=_E44F98CD-04D7-461A-91DA-8C9053E0AB02
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


On Feb 16, 2014:7:11 PM, at 7:11 PM, Joan Cucchiara =
<jcucchiara@mindspring.com> wrote:

> Hi Adrian,
>=20
> Please see inline below prefaced with JEC >.
>=20
> -----Original Message-----
> From: Adrian Farrel [mailto:adrian@olddog.co.uk]=20
> Sent: Friday, February 14, 2014 2:19 PM
> To: 'Joan Cucchiara'; 't.petch'; 'Benoit Claise'; mib-doctors@ietf.org
> Subject: RE: configuration: writable MIB modules versus =
NETCONF/YANGmodules
>=20
> Hi Joan,=20
>=20
> [Reverting to the MIB Doctor Thread]
>=20
> I will bow to your far (far, far) superior understanding of MIB-speak.
>=20
> But I don't understand :-(
>=20
> A row in a table that has RowStatus can have read-only objects and =
writeable
> objects with Defaults as well as read-create objects.
> When you use, for example, CreateAndGo the whole row gets created with
> read-create objects as they are Set, with unSet writeable objects
> defaulting, and with read-only objects filled with values from the
> implementation.
>=20
> JEC > But that is kind of beside the point.   The LSR and TE MIBs =
(rfc3813
> and rfc3812, c. 2004) have two conformance statements, Full and =
Read-only.=20
> JEC >  Full Conformance allows for configuring with SNMP sets.   So =
this
> discussion is focusing on only the Full Conformance.=20
> JEC >  The RowStatus objects in the TE and LSR MIB Modules (rfc3813 =
and
> rfc3812) MUST be implemented as having  a MAX-ACCESS of read-create.   =
In
> other words,
> JEC > a row can be created or deleted, etc. because the agent =
processes an
> SNMP set request to configure the RowStatus object (i.e. a set is =
issued=20
> JEC > for create-and-go, destroy, etc).   =20
>=20
> JEC > The point is that RowStatus  creates the row because of an SNMP =
set
> request.  (Certainly rows can be created other ways too.)
> JEC >  There is only ONE RowStatus for the entire row, and=20
> JEC > if that row is extended or AUGMENTed in additional MIB Modules, =
as in
> the case draft-ietf-mpls-tp-te-mib which extends rows in rfc3813 and
> rfc3812,=20
> JEC > then these extended rows are controlled ALSO by that same =
RowStatus
> object which was defined in the TE/LSR MIB Modules.   =20
> JEC > There is only one RowStatus object which controls the entire =
row, even
> if parts
> JEC> of the row are in different MIB Modules (as with
> draft-ietf-mpls-tp-te-mib).    If you think about the case of deleting =
a
> row, this makes sense.
> JEC > If the RowStatus object in the TE MIB is set to "destroy", then =
the
> deletion of the entire row must happen, even if the objects of that =
row are
> in=20
> JEC > other MIB modules.   =20
>=20
> When I extend a table, surely I can extend with objects that are all =
only
> read-only?
> Furthermore, the whole row in the extension table could be =
automatically
> created when the row in the extended table is created.
>=20
> What am I missing?
>=20
> JEC >  The agent  MUST "configure" (e.g. create the objects,  delete =
the
> objects) in  these extended rows  in this draft because of an SNMP set
> request.   =20
> JEC >   I don't see any way around this, without redefining the =
RowStatus
> TC, or rewriting the TE or LSR MIBs or (probably the simplest =
solution) the=20
> JEC> co-authors write the draft in such a way as to not extend tables =
in the
> TE and LSR MIBs.
>=20
> JEC > So to summarize, an SNMP agent that supports this draft MUST =
support
> the SNMP set request for RowStatus for the rows which extend rows in
> JEC> the LSR and TE MIBs.  =20
>=20
> JEC> Since that is the case, and since this draft is tied to these =
RFCs that
> are 10 years old now,  I don't have an issue=20
> JEC> with them configuring via SNMP for other objects also (but that =
is just
> my opinion).

	But why is that an issue?  This is how things work today.  If I =
create a row
in say the mplsTunnelTable, I get a tunnel. The agent internally signals =
the tunnel
and assigns an ingress FEC label mapping. I can then examine the LSR =
MIB's inSegmentTable
and find an entry there without having manually created one.  I can =
however, go and manually=20
create entries and wire them back to the tunnelEntry too.=20

	--Tom


>=20
> Thanks,
>  -Joan
>=20
>=20
>=20
> Thanks,
> Adrian
>=20
>> -----Original Message-----
>> From: OPS-AREA [mailto:ops-area-bounces@ietf.org] On Behalf Of Joan=20=

>> Cucchiara
>> Sent: 14 February 2014 18:28
>> To: 't.petch'; 'Benoit Claise'; ops-area@ietf.org
>> Subject: Re: [OPS-AREA] configuration: writable MIB modules versus=20
>> NETCONF/YANGmodules
>>=20
>> Hi Tom,
>>=20
>> As the MIB Dr. on this draft,  I have responded on the MIB Dr. thread=20=

>> that I do NOT see a way to make this draft =
(draft-ietf-mpls-tp-te-mib)
> read-only.
>> This draft contains extension tables for tables in LSR and TE MIBS =
which
> are
>> created by RowStatus (which is read-create).   Like it or not, =
RowStatus
> of
>> those MIBs (i.e. LSR and TE MIBs) effect the rows in the extension =
tables
> of
>> this draft (think the case of row creation or row deletion).   That =
is an
>> SNMP Set operation which effects the draft.
>>=20
>> I believe the statement that Benoit puts forth would allow for such a=20=

>> situation as this draft, specifically:
>>=20
>> "... SNMP MIB modules modifying persistent configuration state  =
should=20
>> only be produced by working groups in cases of clear utility and=20
>> consensus to use SNMP write operations for configuration."
>>=20
>> Perhaps, additional wording, such as "For example, in the case of=20
>> proposed SNMP MIB modules which extend or augment rows that are=20
>> created by configuration in a SNMP MIB module which is already a RFC,=20=

>> the proposed SNNP MIB modules will be grandfathered, if the working=20=

>> group finds consensus to do so."
>>=20
>> However, I am okay with the statement as written.
>>=20
>> Thanks,
>>  -Joan
>>=20
>>=20
>> -----Original Message-----
>> From: OPS-AREA [mailto:ops-area-bounces@ietf.org] On Behalf Of =
t.petch
>> Sent: Friday, February 14, 2014 10:02 AM
>> To: Benoit Claise; ops-area@ietf.org
>> Subject: Re: [OPS-AREA] configuration: writable MIB modules versus=20
>> NETCONF/YANGmodules
>>=20
>> ----- Original Message -----
>> From: "Benoit Claise" <bclaise@cisco.com>
>> To: <ops-area@ietf.org>
>> Sent: Friday, February 14, 2014 12:39 AM
>>> Dear all,
>>>=20
>>> We occasionally see read-write MIB module proposals within the IETF.
>>> However, the write capabilities of those MIB modules are rarely
>> implemented.
>>>=20
>>> While discussing this issue with the MIB doctors, we arrive to the=20=

>>> conclusion that it's now time to set the direction for future MIB=20
>>> developments within the IETF. Basically, let's not specify=20
>>> read-write MIB modules unless we have a good reason. Read-only MIB=20=

>>> modules are still fine though, as SNMP is clearly used for =
monitoring
> purposes.
>>>=20
>>> Here is the statement we came up with:
>>>=20
>>>    The OPS area recommends the use of NETCONF/YANG standards for
>>>    configuration. IETF working groups are therefore encouraged to =
use
>>>    the NETCONF/YANG standards for configuration, specifically in new
>>>    charters. SNMP MIB modules modifying persistent configuration
>> state
>>>    should only be produced by working groups in cases of clear
>> utility
>>>    and consensus to use SNMP write operations for configuration.
>>>=20
>>> Ideally, this should become an IESG statement.
>>> Your feedback is most welcome.
>>=20
>> You probably know that there is currently a consensus call in =
progress=20
>> over
>>=20
>> "Please indicate Support or Oppose for this MIB
>> (draft-ietf-mpls-tp-te-mib) to be read-only."
>>=20
>> and I was pleasantly surprised to see opposition, albeit with one=20
>> opponent later changing their mind (perhaps they were sat on from a=20=

>> height:-).  I don't see much sign of Netxxxx in the mpls arena but=20
>> there is a need there for configuration, since there need not be a =
control
> plane to set things up.
>> Perhaps writable MIB modules will still be with us in the distant=20
>> future in some corners of the Internet..
>>=20
>> Ideally, this idea would be fleshed out in an I-D.
>>=20
>> Tom Petch
>>=20
>>> Regards, the MIB doctors & Benoit
>>=20
>> _______________________________________________
>> OPS-AREA mailing list
>> OPS-AREA@ietf.org
>> https://www.ietf.org/mailman/listinfo/ops-area
>>=20
>>=20
>> -----
>> No virus found in this message.
>> Checked by AVG - www.avg.com
>> Version: 2014.0.4259 / Virus Database: 3705/7092 - Release Date:=20
>> 02/14/14
>>=20
>> _______________________________________________
>> OPS-AREA mailing list
>> OPS-AREA@ietf.org
>> https://www.ietf.org/mailman/listinfo/ops-area
>=20
>=20
>=20
> -----
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 2014.0.4259 / Virus Database: 3705/7092 - Release Date: =
02/14/14
>=20
> _______________________________________________
> MIB-DOCTORS mailing list
> MIB-DOCTORS@ietf.org
> https://www.ietf.org/mailman/listinfo/mib-doctors
>=20


--Apple-Mail=_E44F98CD-04D7-461A-91DA-8C9053E0AB02
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

iQIcBAEBCgAGBQJTA2rsAAoJEPcO+I7eiUJZl6oQAJ4KGu736EP22kcZyLVxtciR
Hfd1pPDC2e5lIrRxj+XRRnl7yDTcqgKM40+35GdezkZv2hDXyjE6/C6GD7EJ+7sm
EiWV1wvj+UWMO6TmCqY9kp4qjyEi+EJm0F7mh1//38uaqnsNlP3HP7t9i1gGe1Z4
nuwdEC84rbKYa/6YVdANsxreE1fleJwzEdTuzBJFeOQ23lNCKaSoa+TvyfdXDSCS
bc1xIVbCPwJ7MY/0DNwmzS8wHDISYMUNWRmlzHGrOMIjyNd3N7reZx4XQxcqjyNn
eIT92MiSzwaa4cKbn+cVTGYTq2jM17pmvxKKl86xN+wpW/2GLQSn3OA79/Mx/W3S
wg/tTHNAwUhexjYxfxJOjPo8fB2jQCTXutiztlJ4Zem/iCmcZqBpJN4KjZNMWlwU
8FFE/OZKycj7XzTyCkxSb9Nr5KryrmYQClvaDQLVRADfuBsq1RhObbb+lZhCw10l
qkqSqqIkces+4iCIVrRnGezRNGsZmQffrWC9Ibv+ZxwBicqB280Dsi+qNNGK1OX4
UF2ib6Am20vHeNpbFPtkV4TiVE8jT+S3GIyDqBqAlTolfNMDJFdRV8NXfUHZLjRu
1skW/7vHtga6WSi4QFFl7/jqEi2VP3F2GtZYHnNT54lQWIhbNFhMauxz+Tg+FwwF
G/aQlA2OJqU/gERDjfwX
=I+4N
-----END PGP SIGNATURE-----

--Apple-Mail=_E44F98CD-04D7-461A-91DA-8C9053E0AB02--


From nobody Tue Feb 18 06:18:39 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 8170C1A01DE for <mib-doctors@ietfa.amsl.com>; Tue, 18 Feb 2014 06:18:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.848
X-Spam-Level: 
X-Spam-Status: No, score=-1.848 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_15=0.6, RP_MATCHES_RCVD=-0.548] 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 KSh8EianVbra for <mib-doctors@ietfa.amsl.com>; Tue, 18 Feb 2014 06:18:34 -0800 (PST)
Received: from lucidvision.com (lucidvision.com [72.71.250.34]) by ietfa.amsl.com (Postfix) with ESMTP id 3D3071A04D5 for <mib-doctors@ietf.org>; Tue, 18 Feb 2014 06:18:34 -0800 (PST)
Received: from [192.168.1.122] (static-72-71-250-38.cncdnh.fast04.myfairpoint.net [72.71.250.38]) by lucidvision.com (Postfix) with ESMTP id 3C91C26F7B7E; Tue, 18 Feb 2014 09:18:31 -0500 (EST)
Content-Type: multipart/signed; boundary="Apple-Mail=_DE27DDC7-2035-4084-86EF-2371FC2C66F6"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Thomas Nadeau <tnadeau@lucidvision.com>
In-Reply-To: <029a01cf2b7f$8ece00e0$ac6a02a0$@mindspring.com>
Date: Tue, 18 Feb 2014 09:18:30 -0500
Message-Id: <D911400E-C026-44F1-BACA-62F1D9855719@lucidvision.com>
References: <00b101cf29b9$95d979e0$c18c6da0$@olddog.co.uk> <9904FB1B0159DA42B0B887B7FA8119CA2E4187BC@AZ-FFEXMB04.global.avaya.com> <013501cf2b41$4d26a2c0$e773e840$@olddog.co.uk> <029a01cf2b7f$8ece00e0$ac6a02a0$@mindspring.com>
To: Cucchiara Joan <jcucchiara@mindspring.com>
X-Mailer: Apple Mail (2.1827)
Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/zKCj_HiGOxKJZ3XXkN_Q1IrNaas
Cc: Farrel Adrian <adrian@olddog.co.uk>, "t.petch" <ietfc@btconnect.com>, MIB Doctors <mib-doctors@ietf.org>
Subject: Re: [MIB-DOCTORS] configuration: writable MIB modules versus	NETCONF/YANGmodules
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, 18 Feb 2014 14:18:38 -0000

--Apple-Mail=_DE27DDC7-2035-4084-86EF-2371FC2C66F6
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


On Feb 16, 2014:8:28 PM, at 8:28 PM, Joan Cucchiara =
<jcucchiara@mindspring.com> wrote:

> Hi Adrian,
>=20
> Yes.  Dan has correctly stated what I was trying to say.
>=20
> The concept of a row is such that objects of a single row can be =
defined in
> one or more MIB Modules.   For example,  Row A has 10 objects (one of =
them
> being RowStatus).   5 objects (including the RowStatus object) are =
defined
> in MIB-A and the other 5 are defined in draft-ietf-mpls-te-tp-mib.    =20=

>=20
> The managed entity which supports the draft, MUST be able to
> create/delete/etc.  ALL the objects in  a row due to an SNMP set =
request to
> RowStatus.=20
> The Row is an concept unto itself, and this row is impacted by SNMP =
sets to
> RowStatus.  =20

	Yes, conceptually that is how I view things too.  But the =
reality is that
when you create a row in a table (i.e.: CreateAndGo) the agent will =
"create"
entries in extended or AUGMENTS tables for you using default values if =
they are
not specified in the request. To me, this is the same situation except =
that the
extended/AUGMENTS-ed MIB has %100 defaults.=20

> If the goal (as I understand it) is to make this  draft read-only to =
prevent
> configuration via SNMP sets, then that won't be the case with this =
draft
> even if all the objects are made read-only.    Just the nature of Row =
and
> RowStatus and Full Conformance.   In other words, the managed entity =
still
> needs to create/delete all the objects in the row. This will be the =
same
> managed entity that MUST support SNMP set requests to RowStatus, so =
the goal
> of eliminating the processing of SNMP sets is not possible because of
> RowStatus (or so I think).
>=20
> Again, if you think about the deletion of a row, this makes sense.   =
You
> don't want to delete only parts of a row, otherwise, the MIB tables =
would
> end up with a partial rows that were not very helpful.  The entire row =
is
> deleted.  It doesn't matter that the some of the objects in the row =
are
> defined in MIB-A and some=20
> of the objects are defined in Draft-ietf-mpls-te-tp-mib.   The entire =
row is
> deleted and there is one managed entity responsible for that.  =20

	I agree; its the same as I said above except in reverse. You =
delete from the
main table and the others are deleted as part of the same operation.  In
the case of AUGMENTS that is explicit, and in the case of extends, you =
have no
referring root indexes, so look-ups in the second table should fail =
anyways.

	--Tom

>=20
> Thanks,
>  -Joan
>=20
>=20
> -----Original Message-----
> From: Adrian Farrel [mailto:adrian@olddog.co.uk]=20
> Sent: Sunday, February 16, 2014 1:03 PM
> To: 'Romascanu, Dan (Dan)'; 'Joan Cucchiara'; 't.petch'; 'Benoit =
Claise';
> mib-doctors@ietf.org
> Subject: RE: [MIB-DOCTORS] configuration: writable MIB modules versus
> NETCONF/YANGmodules
>=20
> I'm sorry if I am being thick.
>=20
> The row in the old table has a RowStatus object which is, of course,
> read-create.
> The extension table entry has no object with SYNTAX rowStatus, but is
> created automatically when the entry in the old table is created.
>=20
> A
>=20
>> -----Original Message-----
>> From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com]
>> Sent: 16 February 2014 11:55
>> To: adrian@olddog.co.uk; 'Joan Cucchiara'; 't.petch'; 'Benoit =
Claise';=20
>> mib- doctors@ietf.org
>> Subject: RE: [MIB-DOCTORS] configuration: writable MIB modules versus=20=

>> NETCONF/YANGmodules
>>=20
>> Hi Adrian,
>>=20
>> Even if the row you extend is composed only by objects with =
MAX-ACCESS=20
>> read- only, creating a new row involves a write operation on the=20
>> object with SYNTAX RowStatus.
>>=20
>> This is (I guess) what Joan meant.
>>=20
>> Creating a new row may mean a modification of configuration on the=20
>> managed entity. You now have n+1 rows instead of n rows in the table.
>>=20
>> Regards,
>>=20
>> Dan
>>=20
>>=20
>>> -----Original Message-----
>>> From: MIB-DOCTORS [mailto:mib-doctors-bounces@ietf.org] On Behalf Of=20=

>>> Adrian Farrel
>>> Sent: Friday, February 14, 2014 9:19 PM
>>> To: 'Joan Cucchiara'; 't.petch'; 'Benoit Claise';=20
>>> mib-doctors@ietf.org
>>> Subject: Re: [MIB-DOCTORS] configuration: writable MIB modules=20
>>> versus NETCONF/YANGmodules
>>>=20
>>> Hi Joan,
>>>=20
>>> [Reverting to the MIB Doctor Thread]
>>>=20
>>> I will bow to your far (far, far) superior understanding of =
MIB-speak.
>>>=20
>>> But I don't understand :-(
>>>=20
>>> A row in a table that has RowStatus can have read-only objects and=20=

>>> writeable objects with Defaults as well as read-create objects.
>>> When you use, for example, CreateAndGo the whole row gets created=20
>>> with read-create objects as they are Set, with unSet writeable=20
>>> objects
> defaulting,
>>> and with read-only objects filled with values from the =
implementation.
>>>=20
>>> When I extend a table, surely I can extend with objects that are all=20=

>>> only
> read-
>>> only?
>>> Furthermore, the whole row in the extension table could be=20
>>> automatically created when the row in the extended table is created.
>>>=20
>>> What am I missing?
>>>=20
>>> Thanks,
>>> Adrian
>>>=20
>>>> -----Original Message-----
>>>> From: OPS-AREA [mailto:ops-area-bounces@ietf.org] On Behalf Of=20
>>>> Joan Cucchiara
>>>> Sent: 14 February 2014 18:28
>>>> To: 't.petch'; 'Benoit Claise'; ops-area@ietf.org
>>>> Subject: Re: [OPS-AREA] configuration: writable MIB modules versus=20=

>>>> NETCONF/YANGmodules
>>>>=20
>>>> Hi Tom,
>>>>=20
>>>> As the MIB Dr. on this draft,  I have responded on the MIB Dr.=20
>>>> thread that I do NOT see a way to make this draft=20
>>>> (draft-ietf-mpls-tp-te-mib)
> read-
>>> only.
>>>> This draft contains extension tables for tables in LSR and TE MIBS=20=

>>>> which
> are
>>>> created by RowStatus (which is read-create).   Like it or not,
> RowStatus
> of
>>>> those MIBs (i.e. LSR and TE MIBs) effect the rows in the extension=20=

>>>> tables
> of
>>>> this draft (think the case of row creation or row deletion).   That =
is
> an
>>>> SNMP Set operation which effects the draft.
>>>>=20
>>>> I believe the statement that Benoit puts forth would allow for=20
>>>> such a situation as this draft, specifically:
>>>>=20
>>>> "... SNMP MIB modules modifying persistent configuration state =20
>>>> should only be produced by working groups in cases of clear=20
>>>> utility and consensus to use SNMP write operations for =
configuration."
>>>>=20
>>>> Perhaps, additional wording, such as "For example, in the case of=20=

>>>> proposed SNMP MIB modules which extend or augment rows that are=20
>>>> created by configuration in a SNMP MIB module which is already a=20
>>>> RFC, the proposed SNNP MIB modules will be grandfathered, if the=20
>>>> working group finds consensus to do so."
>>>>=20
>>>> However, I am okay with the statement as written.
>>>>=20
>>>> Thanks,
>>>>  -Joan
>>>>=20
>>>>=20
>>>> -----Original Message-----
>>>> From: OPS-AREA [mailto:ops-area-bounces@ietf.org] On Behalf Of=20
>>>> t.petch
>>>> Sent: Friday, February 14, 2014 10:02 AM
>>>> To: Benoit Claise; ops-area@ietf.org
>>>> Subject: Re: [OPS-AREA] configuration: writable MIB modules versus=20=

>>>> NETCONF/YANGmodules
>>>>=20
>>>> ----- Original Message -----
>>>> From: "Benoit Claise" <bclaise@cisco.com>
>>>> To: <ops-area@ietf.org>
>>>> Sent: Friday, February 14, 2014 12:39 AM
>>>>> Dear all,
>>>>>=20
>>>>> We occasionally see read-write MIB module proposals within the =
IETF.
>>>>> However, the write capabilities of those MIB modules are rarely
>>>> implemented.
>>>>>=20
>>>>> While discussing this issue with the MIB doctors, we arrive to=20
>>>>> the conclusion that it's now time to set the direction for=20
>>>>> future MIB developments within the IETF. Basically, let's not=20
>>>>> specify read-write MIB modules unless we have a good reason.=20
>>>>> Read-only MIB modules are still fine though, as SNMP is clearly=20
>>>>> used for monitoring
>>> purposes.
>>>>>=20
>>>>> Here is the statement we came up with:
>>>>>=20
>>>>>    The OPS area recommends the use of NETCONF/YANG standards for
>>>>>    configuration. IETF working groups are therefore encouraged to
> use
>>>>>    the NETCONF/YANG standards for configuration, specifically in
> new
>>>>>    charters. SNMP MIB modules modifying persistent=20
>>>>> configuration
>>>> state
>>>>>    should only be produced by working groups in cases of clear
>>>> utility
>>>>>    and consensus to use SNMP write operations for configuration.
>>>>>=20
>>>>> Ideally, this should become an IESG statement.
>>>>> Your feedback is most welcome.
>>>>=20
>>>> You probably know that there is currently a consensus call in=20
>>>> progress over
>>>>=20
>>>> "Please indicate Support or Oppose for this MIB
>>>> (draft-ietf-mpls-tp-te-mib) to be read-only."
>>>>=20
>>>> and I was pleasantly surprised to see opposition, albeit with one=20=

>>>> opponent later changing their mind (perhaps they were sat on from=20=

>>>> a height:-).  I don't see much sign of Netxxxx in the mpls arena=20
>>>> but there is a need there for configuration, since there need not=20=

>>>> be a control
>>> plane to set things up.
>>>> Perhaps writable MIB modules will still be with us in the distant=20=

>>>> future in some corners of the Internet..
>>>>=20
>>>> Ideally, this idea would be fleshed out in an I-D.
>>>>=20
>>>> Tom Petch
>>>>=20
>>>>> Regards, the MIB doctors & Benoit
>>>>=20
>>>> _______________________________________________
>>>> OPS-AREA mailing list
>>>> OPS-AREA@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/ops-area
>>>>=20
>>>>=20
>>>> -----
>>>> No virus found in this message.
>>>> Checked by AVG - www.avg.com
>>>> Version: 2014.0.4259 / Virus Database: 3705/7092 - Release Date:
>>>> 02/14/14
>>>>=20
>>>> _______________________________________________
>>>> OPS-AREA mailing list
>>>> OPS-AREA@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/ops-area
>>>=20
>>> _______________________________________________
>>> MIB-DOCTORS mailing list
>>> MIB-DOCTORS@ietf.org
>>> https://www.ietf.org/mailman/listinfo/mib-doctors
>=20
>=20
>=20
> -----
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 2014.0.4259 / Virus Database: 3705/7097 - Release Date: =
02/16/14
>=20
> _______________________________________________
> MIB-DOCTORS mailing list
> MIB-DOCTORS@ietf.org
> https://www.ietf.org/mailman/listinfo/mib-doctors
>=20


--Apple-Mail=_DE27DDC7-2035-4084-86EF-2371FC2C66F6
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

iQIcBAEBCgAGBQJTA2u2AAoJEPcO+I7eiUJZuiEP/igMhZsOE7kfuJAwdlP5GYv6
d5GVcCyJYJKEIfEOOAH4lLPsPK551+Zcyox5EQ+xo9sqKsZRKVS2+5xNYL4qimFt
pu07iCtJFwDX62Kwh+xf5XV6SWTUy7vMvWwWYt4mtQ0wuaeXlykBaAOFYwzGb04y
HGbAnFccHBHR2Ct9vlMpuUpHpb7xkaXk9R5Gmxcmnf6y7j0Z98mezZ2SlnO1VqrQ
02BzSG8+xerQvEsxBoHpUzSOLTEofXpBoZOFycOQdkmJMbB7MoGlCZmdPcQfbfw/
HJD4ensiNBL6vX417swAoJzxn+ILGtXVEcX3cMdzPDNEi9TZshEq5+lQF+7s7qqR
KOHFsjcvg5qk79ri4qi16HZcJTpSEOQYe7j6wY3qhLpY31e2+q3uOn/5EmPdubFl
W1RkZpohZl1DTc4ZX7ntis7w5viXK7JHIHuRSDaYLrRaE85Gzi+3E/ci110L/hxW
i9TiB7Fh2UHz6rEc0zmzQPROz9G3omimE17Fbp4PRwlVaUGVZvhkxn4SiakBtkp4
r7euss7NCj1D1SmTV2emcrOT8ma0r07dH46VsWPeOCr6FeAUYBjQDxpBfm2i4ljs
v9HhXr4DyMkZ4qAZ9sWqYqS42Tmv0zfz6RGaCEiRUVHirgHWdPrP/O6jQN0fqZNZ
Ch6uxol9NmUq0ph/DklR
=ryPT
-----END PGP SIGNATURE-----

--Apple-Mail=_DE27DDC7-2035-4084-86EF-2371FC2C66F6--


From nobody Tue Feb 18 06:21:34 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 DFD481A0675 for <mib-doctors@ietfa.amsl.com>; Tue, 18 Feb 2014 06:21:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.847
X-Spam-Level: 
X-Spam-Status: No, score=-1.847 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, J_CHICKENPOX_15=0.6, RP_MATCHES_RCVD=-0.548] 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 ff115M1_mpox for <mib-doctors@ietfa.amsl.com>; Tue, 18 Feb 2014 06:21:27 -0800 (PST)
Received: from lucidvision.com (lucidvision.com [72.71.250.34]) by ietfa.amsl.com (Postfix) with ESMTP id 152AD1A01CB for <mib-doctors@ietf.org>; Tue, 18 Feb 2014 06:21:27 -0800 (PST)
Received: from [192.168.1.122] (static-72-71-250-38.cncdnh.fast04.myfairpoint.net [72.71.250.38]) by lucidvision.com (Postfix) with ESMTP id 0E1CE26F7B9A; Tue, 18 Feb 2014 09:21:24 -0500 (EST)
Content-Type: multipart/signed; boundary="Apple-Mail=_9CB634F4-5646-4E4B-B467-791A0501C8F3"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Thomas Nadeau <tnadeau@lucidvision.com>
In-Reply-To: <CABCOCHTScmkGNTtEUcnYWBMJ3Pp1CLwG+1QmBaFOmJYPX64UYQ@mail.gmail.com>
Date: Tue, 18 Feb 2014 09:21:23 -0500
Message-Id: <EE33FC2C-03EE-426F-8838-F3B61AA2296E@lucidvision.com>
References: <00b101cf29b9$95d979e0$c18c6da0$@olddog.co.uk> <029901cf2b74$d9d74c00$8d85e400$@mindspring.com> <CABCOCHTScmkGNTtEUcnYWBMJ3Pp1CLwG+1QmBaFOmJYPX64UYQ@mail.gmail.com>
To: Andy Bierman <andy@yumaworks.com>
X-Mailer: Apple Mail (2.1827)
Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/sTfJbLOpriB4YK-U2GZmjgwxFag
Cc: Farrel Adrian <adrian@olddog.co.uk>, "t.petch" <ietfc@btconnect.com>, "MIB Doctors \(E-mail\)" <mib-doctors@ietf.org>
Subject: Re: [MIB-DOCTORS] configuration: writable MIB modules versus NETCONF/YANGmodules
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, 18 Feb 2014 14:21:32 -0000

--Apple-Mail=_9CB634F4-5646-4E4B-B467-791A0501C8F3
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_2658CF4B-087A-41CD-84C6-DD17CB2AB89C"


--Apple-Mail=_2658CF4B-087A-41CD-84C6-DD17CB2AB89C
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1


On Feb 16, 2014:9:06 PM, at 9:06 PM, Andy Bierman <andy@yumaworks.com> =
wrote:

> Hi,
>=20
> I guess I am confused as well, although I don't claim to know the =
details ;-)
>=20
> Looking at RFC 3812, there are 2 conformance statements:
>=20
>     mplsTeModuleFullCompliance
>     mplsTeModuleReadOnlyCompliance
>=20
> If an agent supports the "ReadOnly" MODULE-COMPLIANCE, then the =
RowStatus
>=20
> object is implemented read-only, hard-wired to active (i.e., the agent =
just populates
> the read-only table with the entries via some external configuration).
>=20
>=20
>          OBJECT      mplsTunnelRowStatus
>          SYNTAX      RowStatus { active(1) }
>          MIN-ACCESS  read-only
>          DESCRIPTION "Write access is not required."
>=20
> Why can't new objects added to the row also allow the server to only =
claim
> conformance to the read-only MODULE-COMPLIANCE?  I don't see the
> connection between RowStatus and a developer selecting which
> compliance level it will support in an implementation.
>=20
> It does not matter if the new objects are read-only or read-create.
> A "read-only" agent will magically instantiate the new columns,
> if it supports the extension. A "read-create" agent will allow
> a manager to create new rows, and allow the new r/c columns if
> it supports the extension.

	Precisely - this is what I said earlier in the thread.  Your =
last paragraph
hits the nail on the head.

	--Tom


>=20
>=20
> Andy
>=20
>=20
>=20
>=20
> On Sun, Feb 16, 2014 at 4:11 PM, Joan Cucchiara =
<jcucchiara@mindspring.com> wrote:
> Hi Adrian,
>=20
> Please see inline below prefaced with JEC >.
>=20
> -----Original Message-----
> From: Adrian Farrel [mailto:adrian@olddog.co.uk]
> Sent: Friday, February 14, 2014 2:19 PM
> To: 'Joan Cucchiara'; 't.petch'; 'Benoit Claise'; mib-doctors@ietf.org
> Subject: RE: configuration: writable MIB modules versus =
NETCONF/YANGmodules
>=20
> Hi Joan,
>=20
> [Reverting to the MIB Doctor Thread]
>=20
> I will bow to your far (far, far) superior understanding of MIB-speak.
>=20
> But I don't understand :-(
>=20
> A row in a table that has RowStatus can have read-only objects and =
writeable
> objects with Defaults as well as read-create objects.
> When you use, for example, CreateAndGo the whole row gets created with
> read-create objects as they are Set, with unSet writeable objects
> defaulting, and with read-only objects filled with values from the
> implementation.
>=20
> JEC > But that is kind of beside the point.   The LSR and TE MIBs =
(rfc3813
> and rfc3812, c. 2004) have two conformance statements, Full and =
Read-only.
> JEC >  Full Conformance allows for configuring with SNMP sets.   So =
this
> discussion is focusing on only the Full Conformance.
> JEC >  The RowStatus objects in the TE and LSR MIB Modules (rfc3813 =
and
> rfc3812) MUST be implemented as having  a MAX-ACCESS of read-create.   =
In
> other words,
> JEC > a row can be created or deleted, etc. because the agent =
processes an
> SNMP set request to configure the RowStatus object (i.e. a set is =
issued
> JEC > for create-and-go, destroy, etc).
>=20
> JEC > The point is that RowStatus  creates the row because of an SNMP =
set
> request.  (Certainly rows can be created other ways too.)
> JEC >  There is only ONE RowStatus for the entire row, and
> JEC > if that row is extended or AUGMENTed in additional MIB Modules, =
as in
> the case draft-ietf-mpls-tp-te-mib which extends rows in rfc3813 and
> rfc3812,
> JEC > then these extended rows are controlled ALSO by that same =
RowStatus
> object which was defined in the TE/LSR MIB Modules.
> JEC > There is only one RowStatus object which controls the entire =
row, even
> if parts
> JEC> of the row are in different MIB Modules (as with
> draft-ietf-mpls-tp-te-mib).    If you think about the case of deleting =
a
> row, this makes sense.
> JEC > If the RowStatus object in the TE MIB is set to "destroy", then =
the
> deletion of the entire row must happen, even if the objects of that =
row are
> in
> JEC > other MIB modules.
>=20
> When I extend a table, surely I can extend with objects that are all =
only
> read-only?
> Furthermore, the whole row in the extension table could be =
automatically
> created when the row in the extended table is created.
>=20
> What am I missing?
>=20
> JEC >  The agent  MUST "configure" (e.g. create the objects,  delete =
the
> objects) in  these extended rows  in this draft because of an SNMP set
> request.
> JEC >   I don't see any way around this, without redefining the =
RowStatus
> TC, or rewriting the TE or LSR MIBs or (probably the simplest =
solution) the
> JEC> co-authors write the draft in such a way as to not extend tables =
in the
> TE and LSR MIBs.
>=20
> JEC > So to summarize, an SNMP agent that supports this draft MUST =
support
> the SNMP set request for RowStatus for the rows which extend rows in
> JEC> the LSR and TE MIBs.
>=20
> JEC> Since that is the case, and since this draft is tied to these =
RFCs that
> are 10 years old now,  I don't have an issue
> JEC> with them configuring via SNMP for other objects also (but that =
is just
> my opinion).
>=20
> Thanks,
>   -Joan
>=20
>=20
>=20
> Thanks,
> Adrian
>=20
> > -----Original Message-----
> > From: OPS-AREA [mailto:ops-area-bounces@ietf.org] On Behalf Of Joan
> > Cucchiara
> > Sent: 14 February 2014 18:28
> > To: 't.petch'; 'Benoit Claise'; ops-area@ietf.org
> > Subject: Re: [OPS-AREA] configuration: writable MIB modules versus
> > NETCONF/YANGmodules
> >
> > Hi Tom,
> >
> > As the MIB Dr. on this draft,  I have responded on the MIB Dr. =
thread
> > that I do NOT see a way to make this draft =
(draft-ietf-mpls-tp-te-mib)
> read-only.
> > This draft contains extension tables for tables in LSR and TE MIBS =
which
> are
> > created by RowStatus (which is read-create).   Like it or not, =
RowStatus
> of
> > those MIBs (i.e. LSR and TE MIBs) effect the rows in the extension =
tables
> of
> > this draft (think the case of row creation or row deletion).   That =
is an
> > SNMP Set operation which effects the draft.
> >
> > I believe the statement that Benoit puts forth would allow for such =
a
> > situation as this draft, specifically:
> >
> > "... SNMP MIB modules modifying persistent configuration state  =
should
> > only be produced by working groups in cases of clear utility and
> > consensus to use SNMP write operations for configuration."
> >
> > Perhaps, additional wording, such as "For example, in the case of
> > proposed SNMP MIB modules which extend or augment rows that are
> > created by configuration in a SNMP MIB module which is already a =
RFC,
> > the proposed SNNP MIB modules will be grandfathered, if the working
> > group finds consensus to do so."
> >
> > However, I am okay with the statement as written.
> >
> > Thanks,
> >   -Joan
> >
> >
> > -----Original Message-----
> > From: OPS-AREA [mailto:ops-area-bounces@ietf.org] On Behalf Of =
t.petch
> > Sent: Friday, February 14, 2014 10:02 AM
> > To: Benoit Claise; ops-area@ietf.org
> > Subject: Re: [OPS-AREA] configuration: writable MIB modules versus
> > NETCONF/YANGmodules
> >
> > ----- Original Message -----
> > From: "Benoit Claise" <bclaise@cisco.com>
> > To: <ops-area@ietf.org>
> > Sent: Friday, February 14, 2014 12:39 AM
> > > Dear all,
> > >
> > > We occasionally see read-write MIB module proposals within the =
IETF.
> > > However, the write capabilities of those MIB modules are rarely
> > implemented.
> > >
> > > While discussing this issue with the MIB doctors, we arrive to the
> > > conclusion that it's now time to set the direction for future MIB
> > > developments within the IETF. Basically, let's not specify
> > > read-write MIB modules unless we have a good reason. Read-only MIB
> > > modules are still fine though, as SNMP is clearly used for =
monitoring
> purposes.
> > >
> > > Here is the statement we came up with:
> > >
> > >     The OPS area recommends the use of NETCONF/YANG standards for
> > >     configuration. IETF working groups are therefore encouraged to =
use
> > >     the NETCONF/YANG standards for configuration, specifically in =
new
> > >     charters. SNMP MIB modules modifying persistent configuration
> > state
> > >     should only be produced by working groups in cases of clear
> > utility
> > >     and consensus to use SNMP write operations for configuration.
> > >
> > > Ideally, this should become an IESG statement.
> > > Your feedback is most welcome.
> >
> > You probably know that there is currently a consensus call in =
progress
> > over
> >
> > "Please indicate Support or Oppose for this MIB
> > (draft-ietf-mpls-tp-te-mib) to be read-only."
> >
> > and I was pleasantly surprised to see opposition, albeit with one
> > opponent later changing their mind (perhaps they were sat on from a
> > height:-).  I don't see much sign of Netxxxx in the mpls arena but
> > there is a need there for configuration, since there need not be a =
control
> plane to set things up.
> > Perhaps writable MIB modules will still be with us in the distant
> > future in some corners of the Internet..
> >
> > Ideally, this idea would be fleshed out in an I-D.
> >
> > Tom Petch
> >
> > > Regards, the MIB doctors & Benoit
> >
> > _______________________________________________
> > OPS-AREA mailing list
> > OPS-AREA@ietf.org
> > https://www.ietf.org/mailman/listinfo/ops-area
> >
> >
> > -----
> > No virus found in this message.
> > Checked by AVG - www.avg.com
> > Version: 2014.0.4259 / Virus Database: 3705/7092 - Release Date:
> > 02/14/14
> >
> > _______________________________________________
> > OPS-AREA mailing list
> > OPS-AREA@ietf.org
> > https://www.ietf.org/mailman/listinfo/ops-area
>=20
>=20
>=20
> -----
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 2014.0.4259 / Virus Database: 3705/7092 - Release Date: =
02/14/14
>=20
> _______________________________________________
> MIB-DOCTORS mailing list
> MIB-DOCTORS@ietf.org
> https://www.ietf.org/mailman/listinfo/mib-doctors
>=20
> _______________________________________________
> MIB-DOCTORS mailing list
> MIB-DOCTORS@ietf.org
> https://www.ietf.org/mailman/listinfo/mib-doctors


--Apple-Mail=_2658CF4B-087A-41CD-84C6-DD17CB2AB89C
Content-Transfer-Encoding: 7bit
Content-Type: text/html;
	charset=iso-8859-1

<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><br><div><div>On Feb 16, 2014:9:06 PM, at 9:06 PM, Andy Bierman &lt;<a href="mailto:andy@yumaworks.com">andy@yumaworks.com</a>&gt; wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr">Hi,<div><br></div><div>I guess I am confused as well, although I don't claim to know the details ;-)</div><div><br></div><div>Looking at RFC 3812, there are 2 conformance statements:</div><div><br></div>
&nbsp; &nbsp; mplsTeModuleFullCompliance<br>&nbsp;&nbsp;&nbsp; mplsTeModuleReadOnlyCompliance<div><br><div><pre class="" style="font-size: 1em; margin-top: 0px; margin-bottom: 0px;"><span style="color:rgb(34,34,34);font-family:arial;font-size:small;white-space:normal">If an agent supports the "ReadOnly" MODULE-COMPLIANCE, then the RowStatus</span><br>
</pre><pre class="" style="font-size: 1em; margin-top: 0px; margin-bottom: 0px;"><span style="color:rgb(34,34,34);font-family:arial;font-size:small;white-space:normal">object is implemented read-only, hard-wired to active (i.e., the agent just populates</span></pre>
<pre class="" style="font-size: 1em; margin-top: 0px; margin-bottom: 0px;"><span style="color:rgb(34,34,34);font-family:arial;font-size:small;white-space:normal">the read-only table with the entries via some external configuration).</span></pre>
<pre class="" style="font-size: 1em; margin-top: 0px; margin-bottom: 0px;"><br></pre><pre class="" style="font-size: 1em; margin-top: 0px; margin-bottom: 0px;"><span style="color:rgb(34,34,34);font-family:arial;font-size:small;white-space:normal"><br>
</span></pre>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;OBJECT &nbsp; &nbsp; &nbsp;mplsTunnelRowStatus<br>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;SYNTAX &nbsp; &nbsp; &nbsp;RowStatus { active(1) }<br>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;MIN-ACCESS &nbsp;read-only<br>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;DESCRIPTION "Write access is not required."</div></div><div class="gmail_extra">
<br></div><div class="gmail_extra">Why can't new objects added to the row also allow the server to only claim</div><div class="gmail_extra">conformance to the read-only MODULE-COMPLIANCE? &nbsp;I don't see the</div><div class="gmail_extra">
connection between RowStatus and a developer selecting which</div><div class="gmail_extra">compliance level it will support in an implementation.</div><div class="gmail_extra"><br></div><div class="gmail_extra">It does not matter if the new objects are read-only or read-create.</div>
<div class="gmail_extra">A "read-only" agent will magically instantiate the new columns,</div><div class="gmail_extra">if it supports the extension. A "read-create" agent will allow</div><div class="gmail_extra">
a manager to create new rows, and allow the new r/c columns if</div><div class="gmail_extra">it supports the extension.</div></div></blockquote><div><br></div><span class="Apple-tab-span" style="white-space:pre">	</span>Precisely - this is what I said earlier in the thread. &nbsp;Your last paragraph</div><div>hits the nail on the head.</div><div><br></div><div><span class="Apple-tab-span" style="white-space:pre">	</span>--Tom</div><div><br></div><div><br><blockquote type="cite"><div dir="ltr"><div class="gmail_extra"><br></div><div class="gmail_extra"><br></div><div class="gmail_extra">Andy</div>
<div class="gmail_extra"><br></div><div class="gmail_extra"><br></div><div class="gmail_extra"><br></div><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Feb 16, 2014 at 4:11 PM, Joan Cucchiara <span dir="ltr">&lt;<a href="mailto:jcucchiara@mindspring.com" target="_blank">jcucchiara@mindspring.com</a>&gt;</span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">Hi Adrian,<br>
<br>
Please see inline below prefaced with JEC &gt;.<br>
<br>
-----Original Message-----<br>
From: Adrian Farrel [mailto:<a href="mailto:adrian@olddog.co.uk">adrian@olddog.co.uk</a>]<br>
Sent: Friday, February 14, 2014 2:19 PM<br>
To: 'Joan Cucchiara'; 't.petch'; 'Benoit Claise'; <a href="mailto:mib-doctors@ietf.org">mib-doctors@ietf.org</a><br>
Subject: RE: configuration: writable MIB modules versus NETCONF/YANGmodules<br>
<br>
Hi Joan,<br>
<br>
[Reverting to the MIB Doctor Thread]<br>
<br>
I will bow to your far (far, far) superior understanding of MIB-speak.<br>
<br>
But I don't understand :-(<br>
<br>
A row in a table that has RowStatus can have read-only objects and writeable<br>
objects with Defaults as well as read-create objects.<br>
When you use, for example, CreateAndGo the whole row gets created with<br>
read-create objects as they are Set, with unSet writeable objects<br>
defaulting, and with read-only objects filled with values from the<br>
implementation.<br>
<br>
JEC &gt; But that is kind of beside the point. &nbsp; The LSR and TE MIBs (rfc3813<br>
and rfc3812, c. 2004) have two conformance statements, Full and Read-only.<br>
JEC &gt; &nbsp;Full Conformance allows for configuring with SNMP sets. &nbsp; So this<br>
discussion is focusing on only the Full Conformance.<br>
JEC &gt; &nbsp;The RowStatus objects in the TE and LSR MIB Modules (rfc3813 and<br>
rfc3812) MUST be implemented as having &nbsp;a MAX-ACCESS of read-create. &nbsp; In<br>
other words,<br>
JEC &gt; a row can be created or deleted, etc. because the agent processes an<br>
SNMP set request to configure the RowStatus object (i.e. a set is issued<br>
JEC &gt; for create-and-go, destroy, etc).<br>
<br>
JEC &gt; The point is that RowStatus &nbsp;creates the row because of an SNMP set<br>
request. &nbsp;(Certainly rows can be created other ways too.)<br>
JEC &gt; &nbsp;There is only ONE RowStatus for the entire row, and<br>
JEC &gt; if that row is extended or AUGMENTed in additional MIB Modules, as in<br>
the case draft-ietf-mpls-tp-te-mib which extends rows in rfc3813 and<br>
rfc3812,<br>
JEC &gt; then these extended rows are controlled ALSO by that same RowStatus<br>
object which was defined in the TE/LSR MIB Modules.<br>
JEC &gt; There is only one RowStatus object which controls the entire row, even<br>
if parts<br>
JEC&gt; of the row are in different MIB Modules (as with<br>
draft-ietf-mpls-tp-te-mib). &nbsp; &nbsp;If you think about the case of deleting a<br>
row, this makes sense.<br>
JEC &gt; If the RowStatus object in the TE MIB is set to "destroy", then the<br>
deletion of the entire row must happen, even if the objects of that row are<br>
in<br>
JEC &gt; other MIB modules.<br>
<br>
When I extend a table, surely I can extend with objects that are all only<br>
read-only?<br>
Furthermore, the whole row in the extension table could be automatically<br>
created when the row in the extended table is created.<br>
<br>
What am I missing?<br>
<br>
JEC &gt; &nbsp;The agent &nbsp;MUST "configure" (e.g. create the objects, &nbsp;delete the<br>
objects) in &nbsp;these extended rows &nbsp;in this draft because of an SNMP set<br>
request.<br>
JEC &gt; &nbsp; I don't see any way around this, without redefining the RowStatus<br>
TC, or rewriting the TE or LSR MIBs or (probably the simplest solution) the<br>
JEC&gt; co-authors write the draft in such a way as to not extend tables in the<br>
TE and LSR MIBs.<br>
<br>
JEC &gt; So to summarize, an SNMP agent that supports this draft MUST support<br>
the SNMP set request for RowStatus for the rows which extend rows in<br>
JEC&gt; the LSR and TE MIBs.<br>
<br>
JEC&gt; Since that is the case, and since this draft is tied to these RFCs that<br>
are 10 years old now, &nbsp;I don't have an issue<br>
JEC&gt; with them configuring via SNMP for other objects also (but that is just<br>
my opinion).<br>
<br>
Thanks,<br>
&nbsp; -Joan<br>
<br>
<br>
<br>
Thanks,<br>
Adrian<br>
<br>
&gt; -----Original Message-----<br>
&gt; From: OPS-AREA [mailto:<a href="mailto:ops-area-bounces@ietf.org">ops-area-bounces@ietf.org</a>] On Behalf Of Joan<br>
&gt; Cucchiara<br>
&gt; Sent: 14 February 2014 18:28<br>
&gt; To: 't.petch'; 'Benoit Claise'; <a href="mailto:ops-area@ietf.org">ops-area@ietf.org</a><br>
&gt; Subject: Re: [OPS-AREA] configuration: writable MIB modules versus<br>
&gt; NETCONF/YANGmodules<br>
&gt;<br>
&gt; Hi Tom,<br>
&gt;<br>
&gt; As the MIB Dr. on this draft, &nbsp;I have responded on the MIB Dr. thread<br>
&gt; that I do NOT see a way to make this draft (draft-ietf-mpls-tp-te-mib)<br>
read-only.<br>
&gt; This draft contains extension tables for tables in LSR and TE MIBS which<br>
are<br>
&gt; created by RowStatus (which is read-create). &nbsp; Like it or not, RowStatus<br>
of<br>
&gt; those MIBs (i.e. LSR and TE MIBs) effect the rows in the extension tables<br>
of<br>
&gt; this draft (think the case of row creation or row deletion). &nbsp; That is an<br>
&gt; SNMP Set operation which effects the draft.<br>
&gt;<br>
&gt; I believe the statement that Benoit puts forth would allow for such a<br>
&gt; situation as this draft, specifically:<br>
&gt;<br>
&gt; "... SNMP MIB modules modifying persistent configuration state &nbsp;should<br>
&gt; only be produced by working groups in cases of clear utility and<br>
&gt; consensus to use SNMP write operations for configuration."<br>
&gt;<br>
&gt; Perhaps, additional wording, such as "For example, in the case of<br>
&gt; proposed SNMP MIB modules which extend or augment rows that are<br>
&gt; created by configuration in a SNMP MIB module which is already a RFC,<br>
&gt; the proposed SNNP MIB modules will be grandfathered, if the working<br>
&gt; group finds consensus to do so."<br>
&gt;<br>
&gt; However, I am okay with the statement as written.<br>
&gt;<br>
&gt; Thanks,<br>
&gt; &nbsp; -Joan<br>
&gt;<br>
&gt;<br>
&gt; -----Original Message-----<br>
&gt; From: OPS-AREA [mailto:<a href="mailto:ops-area-bounces@ietf.org">ops-area-bounces@ietf.org</a>] On Behalf Of t.petch<br>
&gt; Sent: Friday, February 14, 2014 10:02 AM<br>
&gt; To: Benoit Claise; <a href="mailto:ops-area@ietf.org">ops-area@ietf.org</a><br>
&gt; Subject: Re: [OPS-AREA] configuration: writable MIB modules versus<br>
&gt; NETCONF/YANGmodules<br>
&gt;<br>
&gt; ----- Original Message -----<br>
&gt; From: "Benoit Claise" &lt;<a href="mailto:bclaise@cisco.com">bclaise@cisco.com</a>&gt;<br>
&gt; To: &lt;<a href="mailto:ops-area@ietf.org">ops-area@ietf.org</a>&gt;<br>
&gt; Sent: Friday, February 14, 2014 12:39 AM<br>
&gt; &gt; Dear all,<br>
&gt; &gt;<br>
&gt; &gt; We occasionally see read-write MIB module proposals within the IETF.<br>
&gt; &gt; However, the write capabilities of those MIB modules are rarely<br>
&gt; implemented.<br>
&gt; &gt;<br>
&gt; &gt; While discussing this issue with the MIB doctors, we arrive to the<br>
&gt; &gt; conclusion that it's now time to set the direction for future MIB<br>
&gt; &gt; developments within the IETF. Basically, let's not specify<br>
&gt; &gt; read-write MIB modules unless we have a good reason. Read-only MIB<br>
&gt; &gt; modules are still fine though, as SNMP is clearly used for monitoring<br>
purposes.<br>
&gt; &gt;<br>
&gt; &gt; Here is the statement we came up with:<br>
&gt; &gt;<br>
&gt; &gt; &nbsp; &nbsp; The OPS area recommends the use of NETCONF/YANG standards for<br>
&gt; &gt; &nbsp; &nbsp; configuration. IETF working groups are therefore encouraged to use<br>
&gt; &gt; &nbsp; &nbsp; the NETCONF/YANG standards for configuration, specifically in new<br>
&gt; &gt; &nbsp; &nbsp; charters. SNMP MIB modules modifying persistent configuration<br>
&gt; state<br>
&gt; &gt; &nbsp; &nbsp; should only be produced by working groups in cases of clear<br>
&gt; utility<br>
&gt; &gt; &nbsp; &nbsp; and consensus to use SNMP write operations for configuration.<br>
&gt; &gt;<br>
&gt; &gt; Ideally, this should become an IESG statement.<br>
&gt; &gt; Your feedback is most welcome.<br>
&gt;<br>
&gt; You probably know that there is currently a consensus call in progress<br>
&gt; over<br>
&gt;<br>
&gt; "Please indicate Support or Oppose for this MIB<br>
&gt; (draft-ietf-mpls-tp-te-mib) to be read-only."<br>
&gt;<br>
&gt; and I was pleasantly surprised to see opposition, albeit with one<br>
&gt; opponent later changing their mind (perhaps they were sat on from a<br>
&gt; height:-). &nbsp;I don't see much sign of Netxxxx in the mpls arena but<br>
&gt; there is a need there for configuration, since there need not be a control<br>
plane to set things up.<br>
&gt; Perhaps writable MIB modules will still be with us in the distant<br>
&gt; future in some corners of the Internet..<br>
&gt;<br>
&gt; Ideally, this idea would be fleshed out in an I-D.<br>
&gt;<br>
&gt; Tom Petch<br>
&gt;<br>
&gt; &gt; Regards, the MIB doctors &amp; Benoit<br>
&gt;<br>
&gt; _______________________________________________<br>
&gt; OPS-AREA mailing list<br>
&gt; <a href="mailto:OPS-AREA@ietf.org">OPS-AREA@ietf.org</a><br>
&gt; <a href="https://www.ietf.org/mailman/listinfo/ops-area" target="_blank">https://www.ietf.org/mailman/listinfo/ops-area</a><br>
&gt;<br>
&gt;<br>
&gt; -----<br>
&gt; No virus found in this message.<br>
&gt; Checked by AVG - <a href="http://www.avg.com/" target="_blank">www.avg.com</a><br>
&gt; Version: 2014.0.4259 / Virus Database: 3705/7092 - Release Date:<br>
&gt; 02/14/14<br>
&gt;<br>
&gt; _______________________________________________<br>
&gt; OPS-AREA mailing list<br>
&gt; <a href="mailto:OPS-AREA@ietf.org">OPS-AREA@ietf.org</a><br>
&gt; <a href="https://www.ietf.org/mailman/listinfo/ops-area" target="_blank">https://www.ietf.org/mailman/listinfo/ops-area</a><br>
<br>
<br>
<br>
-----<br>
No virus found in this message.<br>
Checked by AVG - <a href="http://www.avg.com/" target="_blank">www.avg.com</a><br>
Version: 2014.0.4259 / Virus Database: 3705/7092 - Release Date: 02/14/14<br>
<br>
_______________________________________________<br>
MIB-DOCTORS mailing list<br>
<a href="mailto:MIB-DOCTORS@ietf.org">MIB-DOCTORS@ietf.org</a><br>
<a href="https://www.ietf.org/mailman/listinfo/mib-doctors" target="_blank">https://www.ietf.org/mailman/listinfo/mib-doctors</a><br>
</blockquote></div><br></div></div>
_______________________________________________<br>MIB-DOCTORS mailing list<br><a href="mailto:MIB-DOCTORS@ietf.org">MIB-DOCTORS@ietf.org</a><br>https://www.ietf.org/mailman/listinfo/mib-doctors<br></blockquote></div><br></body></html>
--Apple-Mail=_2658CF4B-087A-41CD-84C6-DD17CB2AB89C--

--Apple-Mail=_9CB634F4-5646-4E4B-B467-791A0501C8F3
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

iQIcBAEBCgAGBQJTA2xjAAoJEPcO+I7eiUJZuUMP/0Twht/kN57851pqGJ5CFAcB
ufIqEGrvXdwj5IIUX6KobTWSiJQAIcwI4Q++JYakaKqMS0ZeIs6gQwe3Ra0Sj1Mf
+jK3lcvkdU/yIZxh2/sWmqZQxV/yBPmPjojwSU7ZYApwR/4+XnD9kHtw6B5iTv0d
J5z7+otSHaFAtTc6rST6TxPtWP7eapdHbyES/dv2FG3bsH3kxr7BddYxmZCgOzT/
K8J2Fk6iH9UGhCL6xaqywEZwgWtmr8scN++7pBjrbdgWvZik8OobLwHc/cmnE81Z
xbEBHSOIwb6LCU6Y8yF0tLB8wI6GIk4rUw8x8YDZE6C5pyDC1ea5Pp1QAXILbg0B
nG4XFT52kt1LGgy38m6IbSTTucLS7jnFeP/Cgkk9AoWBHDe2jZN3xAR5a+tSxTK9
T79MEh9kmGw+r3rtosOIf6K8t4EBjyI0LsamD4/ezEwAJvHuIGegkABPKmtBjpM8
h+3zdFJQwh7NHB0KrZlGWt414TKvn3MTfHpfXqtDkcenf7sPwOYPcOFFKybcYNs4
lIrNxlLIqzgQyzKK2c2fuU+e08HZab4Tn0vr/B4I0QNAJHWJUxuv23Qtedeee4jA
5m01ADSrZRwdnhuUkOwk3nQqedrrxA/UrFPdor4A+oSVWAP/79NZ5Ou0X0bf09Tg
aJIh5S8ZDfDDhFUrgWZm
=+z1E
-----END PGP SIGNATURE-----

--Apple-Mail=_9CB634F4-5646-4E4B-B467-791A0501C8F3--


From nobody Tue Feb 18 06:28:29 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 968F11A060E for <mib-doctors@ietfa.amsl.com>; Tue, 18 Feb 2014 06:28:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.847
X-Spam-Level: 
X-Spam-Status: No, score=-1.847 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, J_CHICKENPOX_15=0.6, RP_MATCHES_RCVD=-0.548] 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 Q2DRKz7mCxjj for <mib-doctors@ietfa.amsl.com>; Tue, 18 Feb 2014 06:28:16 -0800 (PST)
Received: from lucidvision.com (lucidvision.com [72.71.250.34]) by ietfa.amsl.com (Postfix) with ESMTP id D56241A0675 for <mib-doctors@ietf.org>; Tue, 18 Feb 2014 06:28:12 -0800 (PST)
Received: from [192.168.1.122] (static-72-71-250-38.cncdnh.fast04.myfairpoint.net [72.71.250.38]) by lucidvision.com (Postfix) with ESMTP id CF68926F7C39; Tue, 18 Feb 2014 09:28:09 -0500 (EST)
Content-Type: multipart/signed; boundary="Apple-Mail=_9E1C9785-36DD-4961-A3AF-2FCABE1FD6E4"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Thomas Nadeau <tnadeau@lucidvision.com>
In-Reply-To: <02c001cf2bf2$49150cb0$db3f2610$@mindspring.com>
Date: Tue, 18 Feb 2014 09:28:09 -0500
Message-Id: <30293C96-AB8F-476D-BFBF-0DEA0790D9F4@lucidvision.com>
References: <00b101cf29b9$95d979e0$c18c6da0$@olddog.co.uk>	<029901cf2b74$d9d74c00$8d85e400$@mindspring.com> <CABCOCHTScmkGNTtEUcnYWBMJ3Pp1CLwG+1QmBaFOmJYPX64UYQ@mail.gmail.com> <02c001cf2bf2$49150cb0$db3f2610$@mindspring.com>
To: Cucchiara Joan <jcucchiara@mindspring.com>
X-Mailer: Apple Mail (2.1827)
Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/IOy-h43xtiKuihrFgYF82WtUdjo
Cc: Farrel Adrian <adrian@olddog.co.uk>, "MIB Doctors \(E-mail\)" <mib-doctors@ietf.org>, "t.petch" <ietfc@btconnect.com>
Subject: Re: [MIB-DOCTORS] configuration: writable MIB modules versus NETCONF/YANGmodules
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, 18 Feb 2014 14:28:26 -0000

--Apple-Mail=_9E1C9785-36DD-4961-A3AF-2FCABE1FD6E4
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_EC3C20E4-4DD4-4245-950C-76AB85A61E99"


--Apple-Mail=_EC3C20E4-4DD4-4245-950C-76AB85A61E99
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252


On Feb 17, 2014:10:09 AM, at 10:09 AM, Joan Cucchiara =
<jcucchiara@mindspring.com> wrote:

> Hi Andy,
> =20
> The discussion is wrt FullCompliance only, sorry if that wasn=92t =
clear.   =20
> =20
> Even so, if RowStatus is defined as FullCompliance, doesn=92t that =
hold for new extended table objects which are under the control of =
RowStatus with FullCompliance?
> =20
> Managed entity still needs to support the RowStatus  as defined =
originally.   Plus, I would think the =93correct=94 Compliance for the =
draft should include the
> support of Full Compliance for RowStatus of the relevant tables from =
TE MIB and LSR MIB (i.e. the relevant tables meaning those which are =
extended in the draft).
>=20

	I would think it would be ok to support any one of the =
compliance statements, whether full or one of the subsets.  I have never =
heard of any rules implicit or explicit, requiring conformance to the =
full compliance per se, but I might have missed something in the nuance =
of MIB creation. *)

> (Probably more info that you want to know but=85)
> Additionally, the TE and LSR MIBs have other MIBs (rfcs) in GMPLS and =
PWE which also extend tables from LSR MIB/TE MIB.   So, for 10  years =
these MIBs have been
> around, and there is a lot of legacy even in other WGs.  =20
> =20
> I agree that there needs to be some discussion and thought around =
migration of MPLS management to NetConf for configuration.   The issue =
(as I see it) is that
> the LSR MIB contains a LIB (LSR table) and the TE MIB contains a =
Tunnel Table and these have been extended/Augmented in various MIBs and =
in various WGs for 10 years.
> =20
> Either the WGs can keep going with MIBs, or rewrite in NetConf.   To =
me, seems like everyone is focused on this draft, but not really focused =
on how best to help MPLS migrate.   (Not sure the WG even wants to =
migrate, so may have misspoken=85.)   Anyway, no matter what the =
decision is on the draft, that is still not going to help
> MPLS when new features are defined and folks still want to use the LIB =
and Tunnel Tables in rfc3813 and rfc3812.

	It is worth discussing further, because as you say, there are a =
pile of MIBs for MPLS and derivative technologies.  However, I do not =
think configuration is really a big issue with those as there are =
scantly few read-write implementations that ever existed (and may not =
exist any further). Before we embark on any significant work here, we =
should poll the community to see if anyone cares (and if they do are =
will to help!). *)=20

	--Tom

> =20
> Thanks,
>   -Joan
> =20
> From: Andy Bierman [mailto:andy@yumaworks.com]=20
> Sent: Sunday, February 16, 2014 9:06 PM
> To: Joan Cucchiara
> Cc: Adrian Farrel; t.petch; Benoit Claise; MIB Doctors (E-mail)
> Subject: Re: [MIB-DOCTORS] configuration: writable MIB modules versus =
NETCONF/YANGmodules
> =20
> Hi,
> =20
> I guess I am confused as well, although I don't claim to know the =
details ;-)
> =20
> Looking at RFC 3812, there are 2 conformance statements:
> =20
>     mplsTeModuleFullCompliance
>     mplsTeModuleReadOnlyCompliance
> =20
> If an agent supports the "ReadOnly" MODULE-COMPLIANCE, then the =
RowStatus
>=20
> object is implemented read-only, hard-wired to active (i.e., the agent =
just populates
> the read-only table with the entries via some external configuration).
> =20
> =20
>          OBJECT      mplsTunnelRowStatus
>          SYNTAX      RowStatus { active(1) }
>          MIN-ACCESS  read-only
>          DESCRIPTION "Write access is not required."
> =20
> Why can't new objects added to the row also allow the server to only =
claim
> conformance to the read-only MODULE-COMPLIANCE?  I don't see the
> connection between RowStatus and a developer selecting which
> compliance level it will support in an implementation.
> =20
> It does not matter if the new objects are read-only or read-create.
> A "read-only" agent will magically instantiate the new columns,
> if it supports the extension. A "read-create" agent will allow
> a manager to create new rows, and allow the new r/c columns if
> it supports the extension.
> =20
> =20
> Andy
> =20
> =20
> =20
> =20
> On Sun, Feb 16, 2014 at 4:11 PM, Joan Cucchiara =
<jcucchiara@mindspring.com> wrote:
> Hi Adrian,
>=20
> Please see inline below prefaced with JEC >.
>=20
> -----Original Message-----
> From: Adrian Farrel [mailto:adrian@olddog.co.uk]
> Sent: Friday, February 14, 2014 2:19 PM
> To: 'Joan Cucchiara'; 't.petch'; 'Benoit Claise'; mib-doctors@ietf.org
> Subject: RE: configuration: writable MIB modules versus =
NETCONF/YANGmodules
>=20
> Hi Joan,
>=20
> [Reverting to the MIB Doctor Thread]
>=20
> I will bow to your far (far, far) superior understanding of MIB-speak.
>=20
> But I don't understand :-(
>=20
> A row in a table that has RowStatus can have read-only objects and =
writeable
> objects with Defaults as well as read-create objects.
> When you use, for example, CreateAndGo the whole row gets created with
> read-create objects as they are Set, with unSet writeable objects
> defaulting, and with read-only objects filled with values from the
> implementation.
>=20
> JEC > But that is kind of beside the point.   The LSR and TE MIBs =
(rfc3813
> and rfc3812, c. 2004) have two conformance statements, Full and =
Read-only.
> JEC >  Full Conformance allows for configuring with SNMP sets.   So =
this
> discussion is focusing on only the Full Conformance.
> JEC >  The RowStatus objects in the TE and LSR MIB Modules (rfc3813 =
and
> rfc3812) MUST be implemented as having  a MAX-ACCESS of read-create.   =
In
> other words,
> JEC > a row can be created or deleted, etc. because the agent =
processes an
> SNMP set request to configure the RowStatus object (i.e. a set is =
issued
> JEC > for create-and-go, destroy, etc).
>=20
> JEC > The point is that RowStatus  creates the row because of an SNMP =
set
> request.  (Certainly rows can be created other ways too.)
> JEC >  There is only ONE RowStatus for the entire row, and
> JEC > if that row is extended or AUGMENTed in additional MIB Modules, =
as in
> the case draft-ietf-mpls-tp-te-mib which extends rows in rfc3813 and
> rfc3812,
> JEC > then these extended rows are controlled ALSO by that same =
RowStatus
> object which was defined in the TE/LSR MIB Modules.
> JEC > There is only one RowStatus object which controls the entire =
row, even
> if parts
> JEC> of the row are in different MIB Modules (as with
> draft-ietf-mpls-tp-te-mib).    If you think about the case of deleting =
a
> row, this makes sense.
> JEC > If the RowStatus object in the TE MIB is set to "destroy", then =
the
> deletion of the entire row must happen, even if the objects of that =
row are
> in
> JEC > other MIB modules.
>=20
> When I extend a table, surely I can extend with objects that are all =
only
> read-only?
> Furthermore, the whole row in the extension table could be =
automatically
> created when the row in the extended table is created.
>=20
> What am I missing?
>=20
> JEC >  The agent  MUST "configure" (e.g. create the objects,  delete =
the
> objects) in  these extended rows  in this draft because of an SNMP set
> request.
> JEC >   I don't see any way around this, without redefining the =
RowStatus
> TC, or rewriting the TE or LSR MIBs or (probably the simplest =
solution) the
> JEC> co-authors write the draft in such a way as to not extend tables =
in the
> TE and LSR MIBs.
>=20
> JEC > So to summarize, an SNMP agent that supports this draft MUST =
support
> the SNMP set request for RowStatus for the rows which extend rows in
> JEC> the LSR and TE MIBs.
>=20
> JEC> Since that is the case, and since this draft is tied to these =
RFCs that
> are 10 years old now,  I don't have an issue
> JEC> with them configuring via SNMP for other objects also (but that =
is just
> my opinion).
>=20
> Thanks,
>   -Joan
>=20
>=20
>=20
> Thanks,
> Adrian
>=20
> > -----Original Message-----
> > From: OPS-AREA [mailto:ops-area-bounces@ietf.org] On Behalf Of Joan
> > Cucchiara
> > Sent: 14 February 2014 18:28
> > To: 't.petch'; 'Benoit Claise'; ops-area@ietf.org
> > Subject: Re: [OPS-AREA] configuration: writable MIB modules versus
> > NETCONF/YANGmodules
> >
> > Hi Tom,
> >
> > As the MIB Dr. on this draft,  I have responded on the MIB Dr. =
thread
> > that I do NOT see a way to make this draft =
(draft-ietf-mpls-tp-te-mib)
> read-only.
> > This draft contains extension tables for tables in LSR and TE MIBS =
which
> are
> > created by RowStatus (which is read-create).   Like it or not, =
RowStatus
> of
> > those MIBs (i.e. LSR and TE MIBs) effect the rows in the extension =
tables
> of
> > this draft (think the case of row creation or row deletion).   That =
is an
> > SNMP Set operation which effects the draft.
> >
> > I believe the statement that Benoit puts forth would allow for such =
a
> > situation as this draft, specifically:
> >
> > "... SNMP MIB modules modifying persistent configuration state  =
should
> > only be produced by working groups in cases of clear utility and
> > consensus to use SNMP write operations for configuration."
> >
> > Perhaps, additional wording, such as "For example, in the case of
> > proposed SNMP MIB modules which extend or augment rows that are
> > created by configuration in a SNMP MIB module which is already a =
RFC,
> > the proposed SNNP MIB modules will be grandfathered, if the working
> > group finds consensus to do so."
> >
> > However, I am okay with the statement as written.
> >
> > Thanks,
> >   -Joan
> >
> >
> > -----Original Message-----
> > From: OPS-AREA [mailto:ops-area-bounces@ietf.org] On Behalf Of =
t.petch
> > Sent: Friday, February 14, 2014 10:02 AM
> > To: Benoit Claise; ops-area@ietf.org
> > Subject: Re: [OPS-AREA] configuration: writable MIB modules versus
> > NETCONF/YANGmodules
> >
> > ----- Original Message -----
> > From: "Benoit Claise" <bclaise@cisco.com>
> > To: <ops-area@ietf.org>
> > Sent: Friday, February 14, 2014 12:39 AM
> > > Dear all,
> > >
> > > We occasionally see read-write MIB module proposals within the =
IETF.
> > > However, the write capabilities of those MIB modules are rarely
> > implemented.
> > >
> > > While discussing this issue with the MIB doctors, we arrive to the
> > > conclusion that it's now time to set the direction for future MIB
> > > developments within the IETF. Basically, let's not specify
> > > read-write MIB modules unless we have a good reason. Read-only MIB
> > > modules are still fine though, as SNMP is clearly used for =
monitoring
> purposes.
> > >
> > > Here is the statement we came up with:
> > >
> > >     The OPS area recommends the use of NETCONF/YANG standards for
> > >     configuration. IETF working groups are therefore encouraged to =
use
> > >     the NETCONF/YANG standards for configuration, specifically in =
new
> > >     charters. SNMP MIB modules modifying persistent configuration
> > state
> > >     should only be produced by working groups in cases of clear
> > utility
> > >     and consensus to use SNMP write operations for configuration.
> > >
> > > Ideally, this should become an IESG statement.
> > > Your feedback is most welcome.
> >
> > You probably know that there is currently a consensus call in =
progress
> > over
> >
> > "Please indicate Support or Oppose for this MIB
> > (draft-ietf-mpls-tp-te-mib) to be read-only."
> >
> > and I was pleasantly surprised to see opposition, albeit with one
> > opponent later changing their mind (perhaps they were sat on from a
> > height:-).  I don't see much sign of Netxxxx in the mpls arena but
> > there is a need there for configuration, since there need not be a =
control
> plane to set things up.
> > Perhaps writable MIB modules will still be with us in the distant
> > future in some corners of the Internet..
> >
> > Ideally, this idea would be fleshed out in an I-D.
> >
> > Tom Petch
> >
> > > Regards, the MIB doctors & Benoit
> >
> > _______________________________________________
> > OPS-AREA mailing list
> > OPS-AREA@ietf.org
> > https://www.ietf.org/mailman/listinfo/ops-area
> >
> >
> > -----
> > No virus found in this message.
> > Checked by AVG - www.avg.com
> > Version: 2014.0.4259 / Virus Database: 3705/7092 - Release Date:
> > 02/14/14
> >
> > _______________________________________________
> > OPS-AREA mailing list
> > OPS-AREA@ietf.org
> > https://www.ietf.org/mailman/listinfo/ops-area
>=20
>=20
>=20
> -----
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 2014.0.4259 / Virus Database: 3705/7092 - Release Date: =
02/14/14
>=20
> _______________________________________________
> MIB-DOCTORS mailing list
> MIB-DOCTORS@ietf.org
> https://www.ietf.org/mailman/listinfo/mib-doctors
> =20
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 2014.0.4259 / Virus Database: 3705/7098 - Release Date: =
02/16/14
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 2014.0.4259 / Virus Database: 3697/7083 - Release Date: =
02/11/14
> _______________________________________________
> MIB-DOCTORS mailing list
> MIB-DOCTORS@ietf.org
> https://www.ietf.org/mailman/listinfo/mib-doctors


--Apple-Mail=_EC3C20E4-4DD4-4245-950C-76AB85A61E99
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;"><br><div><div>On Feb 17, 2014:10:09 AM, at 10:09 AM, =
Joan Cucchiara &lt;<a =
href=3D"mailto:jcucchiara@mindspring.com">jcucchiara@mindspring.com</a>&gt=
; wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div 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: 0in 0in 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);">Hi Andy,<o:p></o:p></span></div><div style=3D"margin: =
0in 0in 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: 0in 0in 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);">The discussion is wrt =
FullCompliance only, sorry if that wasn=92t clear.&nbsp; =
&nbsp;&nbsp;<o:p></o:p></span></div><div style=3D"margin: 0in 0in =
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: 0in 0in =
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);">Even so, if RowStatus is defined as FullCompliance, =
doesn=92t that hold for new extended table objects which are under the =
control of RowStatus with FullCompliance?<o:p></o:p></span></div><div =
style=3D"margin: 0in 0in 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: 0in 0in 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);">Managed entity still =
needs to support the RowStatus &nbsp;as defined originally.&nbsp;&nbsp; =
Plus, I would think the =93correct=94 Compliance for the draft should =
include the<o:p></o:p></span></div><div style=3D"margin: 0in 0in =
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);">support of Full Compliance for RowStatus of the =
relevant tables from TE MIB and LSR MIB (i.e. the relevant tables =
meaning those which are extended in the =
draft).<o:p></o:p></span></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', =
serif;"><br></div></div></div></blockquote><div><br></div><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span>I would =
think it would be ok to support any one of the compliance statements, =
whether full or one of the subsets. &nbsp;I have never heard of any =
rules implicit or explicit, requiring conformance to the full compliance =
per se, but I might have missed something in the nuance of MIB creation. =
*)<br><div><br></div><blockquote type=3D"cite"><div 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: 0in 0in 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);">(Probably more info that =
you want to know but=85)<o:p></o:p></span></div><div style=3D"margin: =
0in 0in 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);">Additionally, the TE and LSR MIBs =
have other MIBs (rfcs) in GMPLS and PWE which also extend tables from =
LSR MIB/TE MIB.&nbsp;&nbsp; So, for 10 &nbsp;years these MIBs have =
been<o:p></o:p></span></div><div style=3D"margin: 0in 0in 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);">around, and there is a lot of legacy even in other =
WGs.&nbsp;&nbsp;&nbsp;<o:p></o:p></span></div><div style=3D"margin: 0in =
0in 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: 0in 0in 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);">I agree that there needs =
to be some discussion and thought around migration of MPLS management to =
NetConf for configuration.&nbsp;&nbsp; The issue (as I see it) is =
that<o:p></o:p></span></div><div style=3D"margin: 0in 0in 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);">the LSR MIB contains a LIB (LSR table) and the TE MIB =
contains a Tunnel Table and these have been extended/Augmented in =
various MIBs and in various WGs for 10 =
years.<o:p></o:p></span></div><div style=3D"margin: 0in 0in 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: 0in 0in =
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);">Either the WGs can keep going with MIBs, or rewrite =
in NetConf.&nbsp;&nbsp; To me, seems like everyone is focused on this =
draft, but not really focused on how best to help MPLS =
migrate.&nbsp;&nbsp; (Not sure the WG even wants to migrate, so may have =
misspoken=85.)&nbsp;&nbsp; Anyway, no matter what the decision is on the =
draft, that is still not going to help<o:p></o:p></span></div><div =
style=3D"margin: 0in 0in 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);">MPLS when new features =
are defined and folks still want to use the LIB and Tunnel Tables in =
rfc3813 and =
rfc3812.</span></div></div></div></blockquote><div><br></div><div><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span>It is =
worth discussing further, because as you say, there are a pile of MIBs =
for MPLS and derivative technologies. &nbsp;However, I do not think =
configuration is really a big issue with those as there are scantly few =
read-write implementations that ever existed (and may not exist any =
further). Before we embark on any significant work here, we should poll =
the community to see if anyone cares (and if they do are will to help!). =
*)&nbsp;</div><div><br></div><div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>--Tom</div><br><blockquote =
type=3D"cite"><div 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: 0in 0in 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);"><o:p></o:p></span></div><div style=3D"margin: 0in 0in =
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: 0in 0in =
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);">Thanks,<o:p></o:p></span></div><div style=3D"margin: =
0in 0in 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; =
-Joan<o:p></o:p></span></div><div style=3D"margin: 0in 0in 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);"><o:p></o:p></span></div><div style=3D"margin: 0in 0in =
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: 0in 0in =
0.0001pt; font-size: 12pt; font-family: 'Times New Roman', =
serif;"><b><span style=3D"font-size: 10pt; font-family: Tahoma, =
sans-serif;">From:</span></b><span style=3D"font-size: 10pt; =
font-family: Tahoma, sans-serif;"><span =
class=3D"Apple-converted-space">&nbsp;</span>Andy Bierman [<a =
href=3D"mailto:andy@yumaworks.com" style=3D"color: purple; =
text-decoration: underline;">mailto:andy@yumaworks.com</a>]<span =
class=3D"Apple-converted-space">&nbsp;</span><br><b>Sent:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>Sunday, February 16, 2014 =
9:06 PM<br><b>To:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>Joan =
Cucchiara<br><b>Cc:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>Adrian Farrel; t.petch; =
Benoit Claise; MIB Doctors (E-mail)<br><b>Subject:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>Re: [MIB-DOCTORS] =
configuration: writable MIB modules versus =
NETCONF/YANGmodules<o:p></o:p></span></div><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 12pt; font-family: 'Times New Roman', =
serif;"><o:p>&nbsp;</o:p></div><div><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 12pt; font-family: 'Times New Roman', =
serif;">Hi,<o:p></o:p></div><div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', =
serif;"><o:p>&nbsp;</o:p></div></div><div><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">I =
guess I am confused as well, although I don't claim to know the details =
;-)<o:p></o:p></div></div><div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', =
serif;"><o:p>&nbsp;</o:p></div></div><div><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 12pt; font-family: 'Times New Roman', =
serif;">Looking at RFC 3812, there are 2 conformance =
statements:<o:p></o:p></div></div><div><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 12pt; font-family: 'Times New Roman', =
serif;"><o:p>&nbsp;</o:p></div></div><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 12pt; font-family: 'Times New Roman', =
serif;">&nbsp; &nbsp; mplsTeModuleFullCompliance<br>&nbsp;&nbsp;&nbsp; =
mplsTeModuleReadOnlyCompliance<o:p></o:p></div><div><div style=3D"margin: =
0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', =
serif;"><o:p>&nbsp;</o:p></div><div><pre style=3D"margin: 0in 0in =
0.0001pt; font-size: 10pt; font-family: 'Courier New';"><span =
style=3D"font-size: 12pt; font-family: Arial, sans-serif; color: rgb(34, =
34, 34);">If an agent supports the "ReadOnly" MODULE-COMPLIANCE, then =
the RowStatus</span><span style=3D"font-size: =
12pt;"><br><br><o:p></o:p></span></pre><pre style=3D"margin: 0in 0in =
0.0001pt; font-size: 10pt; font-family: 'Courier New';"><span =
style=3D"font-size: 12pt; font-family: Arial, sans-serif; color: rgb(34, =
34, 34);">object is implemented read-only, hard-wired to active (i.e., =
the agent just populates</span><span style=3D"font-size: =
12pt;"><o:p></o:p></span></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';"><span style=3D"font-size: =
12pt; font-family: Arial, sans-serif; color: rgb(34, 34, 34);">the =
read-only table with the entries via some external =
configuration).</span><span style=3D"font-size: =
12pt;"><o:p></o:p></span></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';"><span style=3D"font-size: =
12pt;">&nbsp;</span></pre><pre style=3D"margin: 0in 0in 0.0001pt; =
font-size: 10pt; font-family: 'Courier New';"><span style=3D"font-size: =
12pt;">&nbsp;</span></pre><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif;">&nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp;OBJECT &nbsp; &nbsp; =
&nbsp;mplsTunnelRowStatus<br>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;SYNTAX =
&nbsp; &nbsp; &nbsp;RowStatus { active(1) }<br>&nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp;MIN-ACCESS &nbsp;read-only<br>&nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;DESCRIPTION "Write access is not =
required."<o:p></o:p></div></div></div><div><div style=3D"margin: 0in =
0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', =
serif;"><o:p>&nbsp;</o:p></div></div><div><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">Why =
can't new objects added to the row also allow the server to only =
claim<o:p></o:p></div></div><div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif;">conformance to =
the read-only MODULE-COMPLIANCE? &nbsp;I don't see =
the<o:p></o:p></div></div><div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif;">connection =
between RowStatus and a developer selecting =
which<o:p></o:p></div></div><div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif;">compliance =
level it will support in an =
implementation.<o:p></o:p></div></div><div><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 12pt; font-family: 'Times New Roman', =
serif;"><o:p>&nbsp;</o:p></div></div><div><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">It =
does not matter if the new objects are read-only or =
read-create.<o:p></o:p></div></div><div><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">A =
"read-only" agent will magically instantiate the new =
columns,<o:p></o:p></div></div><div><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">if it =
supports the extension. A "read-create" agent will =
allow<o:p></o:p></div></div><div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif;">a manager to =
create new rows, and allow the new r/c columns =
if<o:p></o:p></div></div><div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif;">it supports the =
extension.<o:p></o:p></div></div><div><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 12pt; font-family: 'Times New Roman', =
serif;"><o:p>&nbsp;</o:p></div></div><div><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 12pt; font-family: 'Times New Roman', =
serif;"><o:p>&nbsp;</o:p></div></div><div><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 12pt; font-family: 'Times New Roman', =
serif;">Andy<o:p></o:p></div></div><div><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 12pt; font-family: 'Times New Roman', =
serif;"><o:p>&nbsp;</o:p></div></div><div><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 12pt; font-family: 'Times New Roman', =
serif;"><o:p>&nbsp;</o:p></div></div><div><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 12pt; font-family: 'Times New Roman', =
serif;"><o:p>&nbsp;</o:p></div></div><div><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 12pt; font-family: 'Times New Roman', =
serif;"><o:p>&nbsp;</o:p></div><div><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">On =
Sun, Feb 16, 2014 at 4:11 PM, Joan Cucchiara &lt;<a =
href=3D"mailto:jcucchiara@mindspring.com" target=3D"_blank" =
style=3D"color: purple; text-decoration: =
underline;">jcucchiara@mindspring.com</a>&gt; =
wrote:<o:p></o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif;">Hi =
Adrian,<br><br>Please see inline below prefaced with JEC =
&gt;.<br><br>-----Original Message-----<br>From: Adrian Farrel =
[mailto:<a href=3D"mailto:adrian@olddog.co.uk" style=3D"color: purple; =
text-decoration: underline;">adrian@olddog.co.uk</a>]<br>Sent: Friday, =
February 14, 2014 2:19 PM<br>To: 'Joan Cucchiara'; 't.petch'; 'Benoit =
Claise';<span class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:mib-doctors@ietf.org" style=3D"color: purple; =
text-decoration: underline;">mib-doctors@ietf.org</a><br>Subject: RE: =
configuration: writable MIB modules versus NETCONF/YANGmodules<br><br>Hi =
Joan,<br><br>[Reverting to the MIB Doctor Thread]<br><br>I will bow to =
your far (far, far) superior understanding of MIB-speak.<br><br>But I =
don't understand :-(<br><br>A row in a table that has RowStatus can have =
read-only objects and writeable<br>objects with Defaults as well as =
read-create objects.<br>When you use, for example, CreateAndGo the whole =
row gets created with<br>read-create objects as they are Set, with unSet =
writeable objects<br>defaulting, and with read-only objects filled with =
values from the<br>implementation.<br><br>JEC &gt; But that is kind of =
beside the point. &nbsp; The LSR and TE MIBs (rfc3813<br>and rfc3812, c. =
2004) have two conformance statements, Full and Read-only.<br>JEC &gt; =
&nbsp;Full Conformance allows for configuring with SNMP sets. &nbsp; So =
this<br>discussion is focusing on only the Full Conformance.<br>JEC &gt; =
&nbsp;The RowStatus objects in the TE and LSR MIB Modules (rfc3813 =
and<br>rfc3812) MUST be implemented as having &nbsp;a MAX-ACCESS of =
read-create. &nbsp; In<br>other words,<br>JEC &gt; a row can be created =
or deleted, etc. because the agent processes an<br>SNMP set request to =
configure the RowStatus object (i.e. a set is issued<br>JEC &gt; for =
create-and-go, destroy, etc).<br><br>JEC &gt; The point is that =
RowStatus &nbsp;creates the row because of an SNMP set<br>request. =
&nbsp;(Certainly rows can be created other ways too.)<br>JEC &gt; =
&nbsp;There is only ONE RowStatus for the entire row, and<br>JEC &gt; if =
that row is extended or AUGMENTed in additional MIB Modules, as =
in<br>the case draft-ietf-mpls-tp-te-mib which extends rows in rfc3813 =
and<br>rfc3812,<br>JEC &gt; then these extended rows are controlled ALSO =
by that same RowStatus<br>object which was defined in the TE/LSR MIB =
Modules.<br>JEC &gt; There is only one RowStatus object which controls =
the entire row, even<br>if parts<br>JEC&gt; of the row are in different =
MIB Modules (as with<br>draft-ietf-mpls-tp-te-mib). &nbsp; &nbsp;If you =
think about the case of deleting a<br>row, this makes sense.<br>JEC &gt; =
If the RowStatus object in the TE MIB is set to "destroy", then =
the<br>deletion of the entire row must happen, even if the objects of =
that row are<br>in<br>JEC &gt; other MIB modules.<br><br>When I extend a =
table, surely I can extend with objects that are all =
only<br>read-only?<br>Furthermore, the whole row in the extension table =
could be automatically<br>created when the row in the extended table is =
created.<br><br>What am I missing?<br><br>JEC &gt; &nbsp;The agent =
&nbsp;MUST "configure" (e.g. create the objects, &nbsp;delete =
the<br>objects) in &nbsp;these extended rows &nbsp;in this draft because =
of an SNMP set<br>request.<br>JEC &gt; &nbsp; I don't see any way around =
this, without redefining the RowStatus<br>TC, or rewriting the TE or LSR =
MIBs or (probably the simplest solution) the<br>JEC&gt; co-authors write =
the draft in such a way as to not extend tables in the<br>TE and LSR =
MIBs.<br><br>JEC &gt; So to summarize, an SNMP agent that supports this =
draft MUST support<br>the SNMP set request for RowStatus for the rows =
which extend rows in<br>JEC&gt; the LSR and TE MIBs.<br><br>JEC&gt; =
Since that is the case, and since this draft is tied to these RFCs =
that<br>are 10 years old now, &nbsp;I don't have an issue<br>JEC&gt; =
with them configuring via SNMP for other objects also (but that is =
just<br>my opinion).<br><br>Thanks,<br>&nbsp; =
-Joan<br><br><br><br>Thanks,<br>Adrian<br><br>&gt; -----Original =
Message-----<br>&gt; From: OPS-AREA [mailto:<a =
href=3D"mailto:ops-area-bounces@ietf.org" style=3D"color: purple; =
text-decoration: underline;">ops-area-bounces@ietf.org</a>] On Behalf Of =
Joan<br>&gt; Cucchiara<br>&gt; Sent: 14 February 2014 18:28<br>&gt; To: =
't.petch'; 'Benoit Claise';<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:ops-area@ietf.org" style=3D"color: purple; =
text-decoration: underline;">ops-area@ietf.org</a><br>&gt; Subject: Re: =
[OPS-AREA] configuration: writable MIB modules versus<br>&gt; =
NETCONF/YANGmodules<br>&gt;<br>&gt; Hi Tom,<br>&gt;<br>&gt; As the MIB =
Dr. on this draft, &nbsp;I have responded on the MIB Dr. thread<br>&gt; =
that I do NOT see a way to make this draft =
(draft-ietf-mpls-tp-te-mib)<br>read-only.<br>&gt; This draft contains =
extension tables for tables in LSR and TE MIBS which<br>are<br>&gt; =
created by RowStatus (which is read-create). &nbsp; Like it or not, =
RowStatus<br>of<br>&gt; those MIBs (i.e. LSR and TE MIBs) effect the =
rows in the extension tables<br>of<br>&gt; this draft (think the case of =
row creation or row deletion). &nbsp; That is an<br>&gt; SNMP Set =
operation which effects the draft.<br>&gt;<br>&gt; I believe the =
statement that Benoit puts forth would allow for such a<br>&gt; =
situation as this draft, specifically:<br>&gt;<br>&gt; "... SNMP MIB =
modules modifying persistent configuration state &nbsp;should<br>&gt; =
only be produced by working groups in cases of clear utility and<br>&gt; =
consensus to use SNMP write operations for =
configuration."<br>&gt;<br>&gt; Perhaps, additional wording, such as =
"For example, in the case of<br>&gt; proposed SNMP MIB modules which =
extend or augment rows that are<br>&gt; created by configuration in a =
SNMP MIB module which is already a RFC,<br>&gt; the proposed SNNP MIB =
modules will be grandfathered, if the working<br>&gt; group finds =
consensus to do so."<br>&gt;<br>&gt; However, I am okay with the =
statement as written.<br>&gt;<br>&gt; Thanks,<br>&gt; &nbsp; =
-Joan<br>&gt;<br>&gt;<br>&gt; -----Original Message-----<br>&gt; From: =
OPS-AREA [mailto:<a href=3D"mailto:ops-area-bounces@ietf.org" =
style=3D"color: purple; text-decoration: =
underline;">ops-area-bounces@ietf.org</a>] On Behalf Of t.petch<br>&gt; =
Sent: Friday, February 14, 2014 10:02 AM<br>&gt; To: Benoit Claise;<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:ops-area@ietf.org" style=3D"color: purple; =
text-decoration: underline;">ops-area@ietf.org</a><br>&gt; Subject: Re: =
[OPS-AREA] configuration: writable MIB modules versus<br>&gt; =
NETCONF/YANGmodules<br>&gt;<br>&gt; ----- Original Message -----<br>&gt; =
From: "Benoit Claise" &lt;<a href=3D"mailto:bclaise@cisco.com" =
style=3D"color: purple; text-decoration: =
underline;">bclaise@cisco.com</a>&gt;<br>&gt; To: &lt;<a =
href=3D"mailto:ops-area@ietf.org" style=3D"color: purple; =
text-decoration: underline;">ops-area@ietf.org</a>&gt;<br>&gt; Sent: =
Friday, February 14, 2014 12:39 AM<br>&gt; &gt; Dear all,<br>&gt; =
&gt;<br>&gt; &gt; We occasionally see read-write MIB module proposals =
within the IETF.<br>&gt; &gt; However, the write capabilities of those =
MIB modules are rarely<br>&gt; implemented.<br>&gt; &gt;<br>&gt; &gt; =
While discussing this issue with the MIB doctors, we arrive to =
the<br>&gt; &gt; conclusion that it's now time to set the direction for =
future MIB<br>&gt; &gt; developments within the IETF. Basically, let's =
not specify<br>&gt; &gt; read-write MIB modules unless we have a good =
reason. Read-only MIB<br>&gt; &gt; modules are still fine though, as =
SNMP is clearly used for monitoring<br>purposes.<br>&gt; &gt;<br>&gt; =
&gt; Here is the statement we came up with:<br>&gt; &gt;<br>&gt; &gt; =
&nbsp; &nbsp; The OPS area recommends the use of NETCONF/YANG standards =
for<br>&gt; &gt; &nbsp; &nbsp; configuration. IETF working groups are =
therefore encouraged to use<br>&gt; &gt; &nbsp; &nbsp; the NETCONF/YANG =
standards for configuration, specifically in new<br>&gt; &gt; &nbsp; =
&nbsp; charters. SNMP MIB modules modifying persistent =
configuration<br>&gt; state<br>&gt; &gt; &nbsp; &nbsp; should only be =
produced by working groups in cases of clear<br>&gt; utility<br>&gt; =
&gt; &nbsp; &nbsp; and consensus to use SNMP write operations for =
configuration.<br>&gt; &gt;<br>&gt; &gt; Ideally, this should become an =
IESG statement.<br>&gt; &gt; Your feedback is most =
welcome.<br>&gt;<br>&gt; You probably know that there is currently a =
consensus call in progress<br>&gt; over<br>&gt;<br>&gt; "Please indicate =
Support or Oppose for this MIB<br>&gt; (draft-ietf-mpls-tp-te-mib) to be =
read-only."<br>&gt;<br>&gt; and I was pleasantly surprised to see =
opposition, albeit with one<br>&gt; opponent later changing their mind =
(perhaps they were sat on from a<br>&gt; height:-). &nbsp;I don't see =
much sign of Netxxxx in the mpls arena but<br>&gt; there is a need there =
for configuration, since there need not be a control<br>plane to set =
things up.<br>&gt; Perhaps writable MIB modules will still be with us in =
the distant<br>&gt; future in some corners of the =
Internet..<br>&gt;<br>&gt; Ideally, this idea would be fleshed out in an =
I-D.<br>&gt;<br>&gt; Tom Petch<br>&gt;<br>&gt; &gt; Regards, the MIB =
doctors &amp; Benoit<br>&gt;<br>&gt; =
_______________________________________________<br>&gt; OPS-AREA mailing =
list<br>&gt;<span class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:OPS-AREA@ietf.org" style=3D"color: purple; =
text-decoration: underline;">OPS-AREA@ietf.org</a><br>&gt;<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"https://www.ietf.org/mailman/listinfo/ops-area" target=3D"_blank" =
style=3D"color: purple; text-decoration: =
underline;">https://www.ietf.org/mailman/listinfo/ops-area</a><br>&gt;<br>=
&gt;<br>&gt; -----<br>&gt; No virus found in this message.<br>&gt; =
Checked by AVG -<span class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"http://www.avg.com/" target=3D"_blank" style=3D"color: purple; =
text-decoration: underline;">www.avg.com</a><br>&gt; Version: =
2014.0.4259 / Virus Database: 3705/7092 - Release Date:<br>&gt; =
02/14/14<br>&gt;<br>&gt; =
_______________________________________________<br>&gt; OPS-AREA mailing =
list<br>&gt;<span class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:OPS-AREA@ietf.org" style=3D"color: purple; =
text-decoration: underline;">OPS-AREA@ietf.org</a><br>&gt;<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"https://www.ietf.org/mailman/listinfo/ops-area" target=3D"_blank" =
style=3D"color: purple; text-decoration: =
underline;">https://www.ietf.org/mailman/listinfo/ops-area</a><br><br><br>=
<br>-----<br>No virus found in this message.<br>Checked by AVG -<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"http://www.avg.com/" target=3D"_blank" style=3D"color: purple; =
text-decoration: underline;">www.avg.com</a><br>Version: 2014.0.4259 / =
Virus Database: 3705/7092 - Release Date: =
02/14/14<br><br>_______________________________________________<br>MIB-DOC=
TORS 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" =
target=3D"_blank" style=3D"color: purple; text-decoration: =
underline;">https://www.ietf.org/mailman/listinfo/mib-doctors</a><o:p></o:=
p></div></div><div style=3D"margin: 0in 0in 0.0001pt; font-size: 12pt; =
font-family: 'Times New Roman', =
serif;"><o:p>&nbsp;</o:p></div></div></div><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">No =
virus found in this message.<br>Checked by AVG -<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"http://www.avg.com/" style=3D"color: purple; text-decoration: =
underline;">www.avg.com</a><br>Version: 2014.0.4259 / Virus Database: =
3705/7098 - Release Date: 02/16/14<o:p></o:p></div><div =
class=3D"MsoNormal" align=3D"center" style=3D"margin: 0in 0in 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif; text-align: =
center;"><hr size=3D"1" width=3D"100%" noshade=3D"" align=3D"center" =
style=3D"color: rgb(160, 160, 160);"></div><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">No =
virus found in this message.<br>Checked by AVG -<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"http://www.avg.com/" style=3D"color: purple; text-decoration: =
underline;">www.avg.com</a><br>Version: 2014.0.4259 / Virus Database: =
3697/7083 - Release Date: =
02/11/14<o:p></o:p></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></div></b=
lockquote></div><br></body></html>=

--Apple-Mail=_EC3C20E4-4DD4-4245-950C-76AB85A61E99--

--Apple-Mail=_9E1C9785-36DD-4961-A3AF-2FCABE1FD6E4
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

iQIcBAEBCgAGBQJTA235AAoJEPcO+I7eiUJZpacQALqFHc4OZU7HjQqFiwDotG8d
sUi7NQoRr+g+Au0AAIcg4NfHKpnFQ6rGm/CjPk3OnRbIaJFcLoJqLu84k/jITkmG
lpWvaIJsX981UsHA6wwDSRWZVI+/uZzlmntfc8qx/0lUR+yZ/NC20bWD4G11cpBE
/OczywkoHKEO+rml76s0lrKiF+qbDSV+0vRkwhGAy1X0wy5c3r5UT74TnyWUloiL
CywkeKcPFNEMe9TEAH4Z3+Ojl2+/AVsv2B4HX8yu2z3r8QBxRlY9yBXVYvxsWwBD
OKc6qbaqYKe3uT7bD6ttaXNMzPIv8CoL3g1oUZGF4bTuKt7ZLZB/bVk5ZRZF8yyY
eXCWUQAHxHRkaFUzxn9TjPNxy8a7QDUQE22wlMWNb4SNxzl5irZU7QwFA+hsdzp3
teyczmYpKvZke0Q62tefxoZu3rQzt2GkyMj6xILK3Nb81rST+sOMH3yafHth6VvP
/WjrUdgsoeupR5W/etuDXbdBsddNkiVzagBr6oCpghUddwb/fakV2WmDlfGkeDx9
cxLvh2Bn3j9BtNrO0MOuCvbBXJwJrr1cMP2IfoUbQibBFEkMxAEXUWjC0jly3cki
YXWye/hHdSUOaR7W3bJ1MCgP09du25YLcJwaaVCpPTtbtGHdw9KACgmAwEPJ+O4H
6f78At9uv2zoGwCUqDOL
=WSvi
-----END PGP SIGNATURE-----

--Apple-Mail=_9E1C9785-36DD-4961-A3AF-2FCABE1FD6E4--


From nobody Tue Feb 18 07:00:41 2014
Return-Path: <jcucchiara@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 50BD31A04FE for <mib-doctors@ietfa.amsl.com>; Tue, 18 Feb 2014 07:00:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.399
X-Spam-Level: 
X-Spam-Status: No, score=-1.399 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, J_CHICKENPOX_15=0.6, RCVD_IN_DNSWL_NONE=-0.0001] 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 GmWe8aIbRM19 for <mib-doctors@ietfa.amsl.com>; Tue, 18 Feb 2014 07:00:32 -0800 (PST)
Received: from elasmtp-spurfowl.atl.sa.earthlink.net (elasmtp-spurfowl.atl.sa.earthlink.net [209.86.89.66]) by ietfa.amsl.com (Postfix) with ESMTP id 1F75C1A04FD for <mib-doctors@ietf.org>; Tue, 18 Feb 2014 07:00:31 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=ZM7SQcZoa7PlXbWNdGgzMrj2tGC1Q7f1hFT9CnPj+eA1qDsLMd+2noY72ns5dz4Y; h=Received:From:To:Cc:References:In-Reply-To:Subject:Date:Message-ID:MIME-Version:Content-Type:X-Mailer:Thread-Index:Content-Language:X-ELNK-Trace:X-Originating-IP;
Received: from [24.41.69.138] (helo=JoanTower) by elasmtp-spurfowl.atl.sa.earthlink.net with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.67) (envelope-from <jcucchiara@mindspring.com>) id 1WFm9k-0005xC-09; Tue, 18 Feb 2014 10:00:20 -0500
From: "Joan Cucchiara" <jcucchiara@mindspring.com>
To: "'Thomas Nadeau'" <tnadeau@lucidvision.com>
References: <00b101cf29b9$95d979e0$c18c6da0$@olddog.co.uk>	<029901cf2b74$d9d74c00$8d85e400$@mindspring.com> <CABCOCHTScmkGNTtEUcnYWBMJ3Pp1CLwG+1QmBaFOmJYPX64UYQ@mail.gmail.com> <02c001cf2bf2$49150cb0$db3f2610$@mindspring.com> <30293C96-AB8F-476D-BFBF-0DEA0790D9F4@lucidvision.com>
In-Reply-To: <30293C96-AB8F-476D-BFBF-0DEA0790D9F4@lucidvision.com>
Date: Tue, 18 Feb 2014 09:59:57 -0500
Message-ID: <007901cf2cba$238d5d80$6aa81880$@mindspring.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_007A_01CF2C90.3ABB4D20"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQHx1En8PKiAdP7k24gVTn+0j3wjJQFSZgvIAUrV1VsA7A5IvAGWOWYMmkzLaoA=
Content-Language: en-us
X-ELNK-Trace: 4d68bbe9cb71969ea344cf2d1a8e60840a9da525759e265437c74d1162dbd02af9f867a6610423391ee4b264fab01f9d350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 24.41.69.138
Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/mU25ut_heQNW262JRczVscDbdgk
Cc: 'Farrel Adrian' <adrian@olddog.co.uk>, "'MIB Doctors \(E-mail\)'" <mib-doctors@ietf.org>, "'t.petch'" <ietfc@btconnect.com>
Subject: Re: [MIB-DOCTORS] configuration: writable MIB modules versus NETCONF/YANGmodules
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, 18 Feb 2014 15:00:39 -0000

This is a multipart message in MIME format.

------=_NextPart_000_007A_01CF2C90.3ABB4D20
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hi,

 

Inline below, prefaced with JEC.

 

From: Thomas Nadeau [mailto:tnadeau@lucidvision.com] 
Sent: Tuesday, February 18, 2014 9:28 AM
To: Cucchiara Joan
Cc: Andy Bierman; Farrel Adrian; t.petch; MIB Doctors (E-mail)
Subject: Re: [MIB-DOCTORS] configuration: writable MIB modules versus
NETCONF/YANGmodules

 

 

On Feb 17, 2014:10:09 AM, at 10:09 AM, Joan Cucchiara
<jcucchiara@mindspring.com> wrote:





Hi Andy,

 

The discussion is wrt FullCompliance only, sorry if that wasn't clear.    

 

Even so, if RowStatus is defined as FullCompliance, doesn't that hold for
new extended table objects which are under the control of RowStatus with
FullCompliance?

 

Managed entity still needs to support the RowStatus  as defined originally.
Plus, I would think the "correct" Compliance for the draft should include
the

support of Full Compliance for RowStatus of the relevant tables from TE MIB
and LSR MIB (i.e. the relevant tables meaning those which are extended in
the draft).

 

 

            I would think it would be ok to support any one of the
compliance statements, whether full or one of the subsets.  I have never
heard of any rules implicit or explicit, requiring conformance to the full
compliance per se, but I might have missed something in the nuance of MIB
creation. *)

 

JEC:  Tom, I agree.   The issue as Dan so eloquently stated is that the
managed entity is responsible for RowStatus and if that was implemented via
SNMP Set, that

Software still is supported on the managed entity.   (I was just trying to
put out, that getting rid of read-create/read-write is not necessarily
getting rid of SNMP sets on the managed entity for these sets of MPLS MIBs.


 

 

(Probably more info that you want to know but.)

Additionally, the TE and LSR MIBs have other MIBs (rfcs) in GMPLS and PWE
which also extend tables from LSR MIB/TE MIB.   So, for 10  years these MIBs
have been

around, and there is a lot of legacy even in other WGs.   

 

I agree that there needs to be some discussion and thought around migration
of MPLS management to NetConf for configuration.   The issue (as I see it)
is that

the LSR MIB contains a LIB (LSR table) and the TE MIB contains a Tunnel
Table and these have been extended/Augmented in various MIBs and in various
WGs for 10 years.

 

Either the WGs can keep going with MIBs, or rewrite in NetConf.   To me,
seems like everyone is focused on this draft, but not really focused on how
best to help MPLS migrate.   (Not sure the WG even wants to migrate, so may
have misspoken..)   Anyway, no matter what the decision is on the draft,
that is still not going to help

MPLS when new features are defined and folks still want to use the LIB and
Tunnel Tables in rfc3813 and rfc3812.

 

            It is worth discussing further, because as you say, there are a
pile of MIBs for MPLS and derivative technologies.  However, I do not think
configuration is really a big issue with those as there are scantly few
read-write implementations that ever existed (and may not exist any
further). Before we embark on any significant work here, we should poll the
community to see if anyone cares (and if they do are will to help!). *) 

 

JEC:   I think a decent analogy is to say, that the Label Switching Table
(LIB) in the LSR MIB is to MPLS as the IP Routing Table is to IP (certainly
NOT the same scale).    The Tunnel Table in the TE MIB is added to for most
new tunnel types/features.   After 10 years of tacking on to these tables in
3 different WGs, and learning quite a bit in the process, I do think at a
minimum defining these in NetConf (or even redo them in SNMP if
monitoring-only (?)) maybe something to consider, or at least, discuss a
timeframe for.    I suppose that adding on to the same tables can continue
too, but that is getting more and more cumbersome.

 

Thanks,

-Joan 

 

 

            --Tom





 

Thanks,

  -Joan

 

From: Andy Bierman [ <mailto:andy@yumaworks.com> mailto:andy@yumaworks.com] 
Sent: Sunday, February 16, 2014 9:06 PM
To: Joan Cucchiara
Cc: Adrian Farrel; t.petch; Benoit Claise; MIB Doctors (E-mail)
Subject: Re: [MIB-DOCTORS] configuration: writable MIB modules versus
NETCONF/YANGmodules

 

Hi,

 

I guess I am confused as well, although I don't claim to know the details
;-)

 

Looking at RFC 3812, there are 2 conformance statements:

 

    mplsTeModuleFullCompliance
    mplsTeModuleReadOnlyCompliance

 

If an agent supports the "ReadOnly" MODULE-COMPLIANCE, then the RowStatus



object is implemented read-only, hard-wired to active (i.e., the agent just
populates
the read-only table with the entries via some external configuration).
 
 

         OBJECT      mplsTunnelRowStatus
         SYNTAX      RowStatus { active(1) }
         MIN-ACCESS  read-only
         DESCRIPTION "Write access is not required."

 

Why can't new objects added to the row also allow the server to only claim

conformance to the read-only MODULE-COMPLIANCE?  I don't see the

connection between RowStatus and a developer selecting which

compliance level it will support in an implementation.

 

It does not matter if the new objects are read-only or read-create.

A "read-only" agent will magically instantiate the new columns,

if it supports the extension. A "read-create" agent will allow

a manager to create new rows, and allow the new r/c columns if

it supports the extension.

 

 

Andy

 

 

 

 

On Sun, Feb 16, 2014 at 4:11 PM, Joan Cucchiara <
<mailto:jcucchiara@mindspring.com> jcucchiara@mindspring.com> wrote:

Hi Adrian,

Please see inline below prefaced with JEC >.

-----Original Message-----
From: Adrian Farrel [mailto: <mailto:adrian@olddog.co.uk>
adrian@olddog.co.uk]
Sent: Friday, February 14, 2014 2:19 PM
To: 'Joan Cucchiara'; 't.petch'; 'Benoit Claise';
<mailto:mib-doctors@ietf.org> mib-doctors@ietf.org
Subject: RE: configuration: writable MIB modules versus NETCONF/YANGmodules

Hi Joan,

[Reverting to the MIB Doctor Thread]

I will bow to your far (far, far) superior understanding of MIB-speak.

But I don't understand :-(

A row in a table that has RowStatus can have read-only objects and writeable
objects with Defaults as well as read-create objects.
When you use, for example, CreateAndGo the whole row gets created with
read-create objects as they are Set, with unSet writeable objects
defaulting, and with read-only objects filled with values from the
implementation.

JEC > But that is kind of beside the point.   The LSR and TE MIBs (rfc3813
and rfc3812, c. 2004) have two conformance statements, Full and Read-only.
JEC >  Full Conformance allows for configuring with SNMP sets.   So this
discussion is focusing on only the Full Conformance.
JEC >  The RowStatus objects in the TE and LSR MIB Modules (rfc3813 and
rfc3812) MUST be implemented as having  a MAX-ACCESS of read-create.   In
other words,
JEC > a row can be created or deleted, etc. because the agent processes an
SNMP set request to configure the RowStatus object (i.e. a set is issued
JEC > for create-and-go, destroy, etc).

JEC > The point is that RowStatus  creates the row because of an SNMP set
request.  (Certainly rows can be created other ways too.)
JEC >  There is only ONE RowStatus for the entire row, and
JEC > if that row is extended or AUGMENTed in additional MIB Modules, as in
the case draft-ietf-mpls-tp-te-mib which extends rows in rfc3813 and
rfc3812,
JEC > then these extended rows are controlled ALSO by that same RowStatus
object which was defined in the TE/LSR MIB Modules.
JEC > There is only one RowStatus object which controls the entire row, even
if parts
JEC> of the row are in different MIB Modules (as with
draft-ietf-mpls-tp-te-mib).    If you think about the case of deleting a
row, this makes sense.
JEC > If the RowStatus object in the TE MIB is set to "destroy", then the
deletion of the entire row must happen, even if the objects of that row are
in
JEC > other MIB modules.

When I extend a table, surely I can extend with objects that are all only
read-only?
Furthermore, the whole row in the extension table could be automatically
created when the row in the extended table is created.

What am I missing?

JEC >  The agent  MUST "configure" (e.g. create the objects,  delete the
objects) in  these extended rows  in this draft because of an SNMP set
request.
JEC >   I don't see any way around this, without redefining the RowStatus
TC, or rewriting the TE or LSR MIBs or (probably the simplest solution) the
JEC> co-authors write the draft in such a way as to not extend tables in the
TE and LSR MIBs.

JEC > So to summarize, an SNMP agent that supports this draft MUST support
the SNMP set request for RowStatus for the rows which extend rows in
JEC> the LSR and TE MIBs.

JEC> Since that is the case, and since this draft is tied to these RFCs that
are 10 years old now,  I don't have an issue
JEC> with them configuring via SNMP for other objects also (but that is just
my opinion).

Thanks,
  -Joan



Thanks,
Adrian

> -----Original Message-----
> From: OPS-AREA [mailto: <mailto:ops-area-bounces@ietf.org>
ops-area-bounces@ietf.org] On Behalf Of Joan
> Cucchiara
> Sent: 14 February 2014 18:28
> To: 't.petch'; 'Benoit Claise';  <mailto:ops-area@ietf.org>
ops-area@ietf.org
> Subject: Re: [OPS-AREA] configuration: writable MIB modules versus
> NETCONF/YANGmodules
>
> Hi Tom,
>
> As the MIB Dr. on this draft,  I have responded on the MIB Dr. thread
> that I do NOT see a way to make this draft (draft-ietf-mpls-tp-te-mib)
read-only.
> This draft contains extension tables for tables in LSR and TE MIBS which
are
> created by RowStatus (which is read-create).   Like it or not, RowStatus
of
> those MIBs (i.e. LSR and TE MIBs) effect the rows in the extension tables
of
> this draft (think the case of row creation or row deletion).   That is an
> SNMP Set operation which effects the draft.
>
> I believe the statement that Benoit puts forth would allow for such a
> situation as this draft, specifically:
>
> "... SNMP MIB modules modifying persistent configuration state  should
> only be produced by working groups in cases of clear utility and
> consensus to use SNMP write operations for configuration."
>
> Perhaps, additional wording, such as "For example, in the case of
> proposed SNMP MIB modules which extend or augment rows that are
> created by configuration in a SNMP MIB module which is already a RFC,
> the proposed SNNP MIB modules will be grandfathered, if the working
> group finds consensus to do so."
>
> However, I am okay with the statement as written.
>
> Thanks,
>   -Joan
>
>
> -----Original Message-----
> From: OPS-AREA [mailto: <mailto:ops-area-bounces@ietf.org>
ops-area-bounces@ietf.org] On Behalf Of t.petch
> Sent: Friday, February 14, 2014 10:02 AM
> To: Benoit Claise;  <mailto:ops-area@ietf.org> ops-area@ietf.org
> Subject: Re: [OPS-AREA] configuration: writable MIB modules versus
> NETCONF/YANGmodules
>
> ----- Original Message -----
> From: "Benoit Claise" < <mailto:bclaise@cisco.com> bclaise@cisco.com>
> To: < <mailto:ops-area@ietf.org> ops-area@ietf.org>
> Sent: Friday, February 14, 2014 12:39 AM
> > Dear all,
> >
> > We occasionally see read-write MIB module proposals within the IETF.
> > However, the write capabilities of those MIB modules are rarely
> implemented.
> >
> > While discussing this issue with the MIB doctors, we arrive to the
> > conclusion that it's now time to set the direction for future MIB
> > developments within the IETF. Basically, let's not specify
> > read-write MIB modules unless we have a good reason. Read-only MIB
> > modules are still fine though, as SNMP is clearly used for monitoring
purposes.
> >
> > Here is the statement we came up with:
> >
> >     The OPS area recommends the use of NETCONF/YANG standards for
> >     configuration. IETF working groups are therefore encouraged to use
> >     the NETCONF/YANG standards for configuration, specifically in new
> >     charters. SNMP MIB modules modifying persistent configuration
> state
> >     should only be produced by working groups in cases of clear
> utility
> >     and consensus to use SNMP write operations for configuration.
> >
> > Ideally, this should become an IESG statement.
> > Your feedback is most welcome.
>
> You probably know that there is currently a consensus call in progress
> over
>
> "Please indicate Support or Oppose for this MIB
> (draft-ietf-mpls-tp-te-mib) to be read-only."
>
> and I was pleasantly surprised to see opposition, albeit with one
> opponent later changing their mind (perhaps they were sat on from a
> height:-).  I don't see much sign of Netxxxx in the mpls arena but
> there is a need there for configuration, since there need not be a control
plane to set things up.
> Perhaps writable MIB modules will still be with us in the distant
> future in some corners of the Internet..
>
> Ideally, this idea would be fleshed out in an I-D.
>
> Tom Petch
>
> > Regards, the MIB doctors & Benoit
>
> _______________________________________________
> OPS-AREA mailing list
>  <mailto:OPS-AREA@ietf.org> OPS-AREA@ietf.org
>  <https://www.ietf.org/mailman/listinfo/ops-area>
https://www.ietf.org/mailman/listinfo/ops-area
>
>
> -----
> No virus found in this message.
> Checked by AVG -  <http://www.avg.com/> www.avg.com
> Version: 2014.0.4259 / Virus Database: 3705/7092 - Release Date:
> 02/14/14
>
> _______________________________________________
> OPS-AREA mailing list
>  <mailto:OPS-AREA@ietf.org> OPS-AREA@ietf.org
>  <https://www.ietf.org/mailman/listinfo/ops-area>
https://www.ietf.org/mailman/listinfo/ops-area



-----
No virus found in this message.
Checked by AVG -  <http://www.avg.com/> www.avg.com
Version: 2014.0.4259 / Virus Database: 3705/7092 - Release Date: 02/14/14

_______________________________________________
MIB-DOCTORS mailing list
 <mailto:MIB-DOCTORS@ietf.org> MIB-DOCTORS@ietf.org
 <https://www.ietf.org/mailman/listinfo/mib-doctors>
https://www.ietf.org/mailman/listinfo/mib-doctors

 

No virus found in this message.
Checked by AVG -  <http://www.avg.com/> www.avg.com
Version: 2014.0.4259 / Virus Database: 3705/7098 - Release Date: 02/16/14

  _____  

No virus found in this message.
Checked by AVG -  <http://www.avg.com/> www.avg.com
Version: 2014.0.4259 / Virus Database: 3697/7083 - Release Date: 02/11/14

_______________________________________________
MIB-DOCTORS mailing list
 <mailto:MIB-DOCTORS@ietf.org> MIB-DOCTORS@ietf.org
 <https://www.ietf.org/mailman/listinfo/mib-doctors>
https://www.ietf.org/mailman/listinfo/mib-doctors

 


------=_NextPart_000_007A_01CF2C90.3ABB4D20
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=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><!--[if !mso]><style>v\:* =
{behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:Helvetica;
	panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
	{font-family:Helvetica;
	panose-1:2 11 6 4 2 2 2 2 2 4;}
@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:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
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:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.apple-tab-span
	{mso-style-name:apple-tab-span;}
span.apple-converted-space
	{mso-style-name:apple-converted-space;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Consolas","serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle23
	{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:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></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 lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Hi,<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Inline below, prefaced with JEC.<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><div><div =
style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
Thomas Nadeau [mailto:tnadeau@lucidvision.com] <br><b>Sent:</b> Tuesday, =
February 18, 2014 9:28 AM<br><b>To:</b> Cucchiara Joan<br><b>Cc:</b> =
Andy Bierman; Farrel Adrian; t.petch; MIB Doctors =
(E-mail)<br><b>Subject:</b> Re: [MIB-DOCTORS] configuration: writable =
MIB modules versus =
NETCONF/YANGmodules<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><div><p class=3DMsoNormal>On =
Feb 17, 2014:10:09 AM, at 10:09 AM, Joan Cucchiara &lt;<a =
href=3D"mailto:jcucchiara@mindspring.com">jcucchiara@mindspring.com</a>&g=
t; wrote:<o:p></o:p></p></div><p =
class=3DMsoNormal><br><br><o:p></o:p></p><div><div><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Hi Andy,</span><o:p></o:p></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;</span><o:p></o:p></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>The discussion is wrt FullCompliance only, sorry if that wasn&#8217;t =
clear.&nbsp; &nbsp;&nbsp;</span><o:p></o:p></p></div><div><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;</span><o:p></o:p></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Even so, if RowStatus is defined as FullCompliance, doesn&#8217;t =
that hold for new extended table objects which are under the control of =
RowStatus with FullCompliance?</span><o:p></o:p></p></div><div><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;</span><o:p></o:p></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Managed entity still needs to support the RowStatus &nbsp;as defined =
originally.&nbsp;&nbsp; Plus, I would think the &#8220;correct&#8221; =
Compliance for the draft should include =
the</span><o:p></o:p></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>support of Full Compliance for RowStatus of the relevant tables from =
TE MIB and LSR MIB (i.e. the relevant tables meaning those which are =
extended in the draft).</span><o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><p class=3DMsoNormal><span =
class=3Dapple-tab-span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp; </span>I would think it would be ok to support any one =
of the compliance statements, whether full or one of the subsets. =
&nbsp;I have never heard of any rules implicit or explicit, requiring =
conformance to the full compliance per se, but I might have missed =
something in the nuance of MIB creation. *)<o:p></o:p></p><div><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>JEC:&nbsp; Tom, I agree.&nbsp;&nbsp; The issue as Dan so eloquently =
stated is that the managed entity is responsible for RowStatus and if =
that was implemented via SNMP Set, that<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Software still is supported on the managed entity.&nbsp;&nbsp; (I was =
just trying to put out, that getting rid of read-create/read-write is =
not necessarily getting rid of SNMP sets on the managed entity for these =
sets of MPLS MIBs. &nbsp;&nbsp;&nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p></div><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><div><div><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>(Probably more info that you want to know =
but&#8230;)</span><o:p></o:p></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Additionally, the TE and LSR MIBs have other MIBs (rfcs) in GMPLS and =
PWE which also extend tables from LSR MIB/TE MIB.&nbsp;&nbsp; So, for 10 =
&nbsp;years these MIBs have been</span><o:p></o:p></p></div><div><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>around, and there is a lot of legacy even in other =
WGs.&nbsp;&nbsp;&nbsp;</span><o:p></o:p></p></div><div><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;</span><o:p></o:p></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>I agree that there needs to be some discussion and thought around =
migration of MPLS management to NetConf for configuration.&nbsp;&nbsp; =
The issue (as I see it) is that</span><o:p></o:p></p></div><div><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>the LSR MIB contains a LIB (LSR table) and the TE MIB contains a =
Tunnel Table and these have been extended/Augmented in various MIBs and =
in various WGs for 10 years.</span><o:p></o:p></p></div><div><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;</span><o:p></o:p></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Either the WGs can keep going with MIBs, or rewrite in =
NetConf.&nbsp;&nbsp; To me, seems like everyone is focused on this =
draft, but not really focused on how best to help MPLS =
migrate.&nbsp;&nbsp; (Not sure the WG even wants to migrate, so may have =
misspoken&#8230;.)&nbsp;&nbsp; Anyway, no matter what the decision is on =
the draft, that is still not going to =
help</span><o:p></o:p></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>MPLS when new features are defined and folks still want to use the =
LIB and Tunnel Tables in rfc3813 and =
rfc3812.</span><o:p></o:p></p></div></div></blockquote><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal><span =
class=3Dapple-tab-span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp; </span>It is worth discussing further, because as you =
say, there are a pile of MIBs for MPLS and derivative technologies. =
&nbsp;However, I do not think configuration is really a big issue with =
those as there are scantly few read-write implementations that ever =
existed (and may not exist any further). Before we embark on any =
significant work here, we should poll the community to see if anyone =
cares (and if they do are will to help!). =
*)&nbsp;<o:p></o:p></p></div><div><p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>JEC:&nbsp;&nbsp; I think a decent analogy is to say, that the Label =
Switching Table (LIB) in the LSR MIB is to MPLS as the IP Routing Table =
is to IP (certainly NOT the same scale).&nbsp;&nbsp;&nbsp; The Tunnel =
Table in the TE MIB is added to for most new tunnel =
types/features.&nbsp;&nbsp; After 10 years of tacking on to these tables =
in 3 different WGs, and learning quite a bit in the process, I do think =
at a minimum defining these in NetConf (or even redo them in SNMP if =
monitoring-only (?)) maybe something to consider, or at least, discuss a =
timeframe for.&nbsp;&nbsp;&nbsp; I suppose that adding on to the same =
tables can continue too, but that is getting more and more =
cumbersome.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Thanks,<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'> -Joan <o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p></div><div><p class=3DMsoNormal><span =
class=3Dapple-tab-span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp; </span>--Tom<o:p></o:p></p></div><p =
class=3DMsoNormal><br><br><o:p></o:p></p><div><div><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;</span><o:p></o:p></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Thanks,</span><o:p></o:p></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp; -Joan</span><o:p></o:p></p></div><div><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;</span><o:p></o:p></p></div><div><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span class=3Dapple-converted-space><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>&nbsp;</span=
></span><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>Andy =
Bierman [<a href=3D"mailto:andy@yumaworks.com"><span =
style=3D'color:purple'>mailto:andy@yumaworks.com</span></a>]<span =
class=3Dapple-converted-space>&nbsp;</span><br><b>Sent:</b><span =
class=3Dapple-converted-space>&nbsp;</span>Sunday, February 16, 2014 =
9:06 PM<br><b>To:</b><span =
class=3Dapple-converted-space>&nbsp;</span>Joan =
Cucchiara<br><b>Cc:</b><span =
class=3Dapple-converted-space>&nbsp;</span>Adrian Farrel; t.petch; =
Benoit Claise; MIB Doctors (E-mail)<br><b>Subject:</b><span =
class=3Dapple-converted-space>&nbsp;</span>Re: [MIB-DOCTORS] =
configuration: writable MIB modules versus =
NETCONF/YANGmodules</span><o:p></o:p></p></div><div><p =
class=3DMsoNormal>&nbsp;<o:p></o:p></p></div><div><div><p =
class=3DMsoNormal>Hi,<o:p></o:p></p></div><div><div><p =
class=3DMsoNormal>&nbsp;<o:p></o:p></p></div></div><div><div><p =
class=3DMsoNormal>I guess I am confused as well, although I don't claim =
to know the details ;-)<o:p></o:p></p></div></div><div><div><p =
class=3DMsoNormal>&nbsp;<o:p></o:p></p></div></div><div><div><p =
class=3DMsoNormal>Looking at RFC 3812, there are 2 conformance =
statements:<o:p></o:p></p></div></div><div><div><p =
class=3DMsoNormal>&nbsp;<o:p></o:p></p></div></div><div><p =
class=3DMsoNormal>&nbsp; &nbsp; =
mplsTeModuleFullCompliance<br>&nbsp;&nbsp;&nbsp; =
mplsTeModuleReadOnlyCompliance<o:p></o:p></p></div><div><div><p =
class=3DMsoNormal>&nbsp;<o:p></o:p></p></div><div><pre><span =
style=3D'font-size:12.0pt;font-family:"Arial","sans-serif";color:#222222'=
>If an agent supports the &quot;ReadOnly&quot; MODULE-COMPLIANCE, then =
the RowStatus</span><span =
style=3D'font-size:12.0pt'><br><br><br></span><o:p></o:p></pre><pre><span=
 =
style=3D'font-size:12.0pt;font-family:"Arial","sans-serif";color:#222222'=
>object is implemented read-only, hard-wired to active (i.e., the agent =
just populates</span><o:p></o:p></pre><pre><span =
style=3D'font-size:12.0pt;font-family:"Arial","sans-serif";color:#222222'=
>the read-only table with the entries via some external =
configuration).</span><o:p></o:p></pre><pre><span =
style=3D'font-size:12.0pt'>&nbsp;</span><o:p></o:p></pre><pre><span =
style=3D'font-size:12.0pt'>&nbsp;</span><o:p></o:p></pre><div><p =
class=3DMsoNormal>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;OBJECT &nbsp; &nbsp; =
&nbsp;mplsTunnelRowStatus<br>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;SYNTAX =
&nbsp; &nbsp; &nbsp;RowStatus { active(1) }<br>&nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp;MIN-ACCESS &nbsp;read-only<br>&nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;DESCRIPTION &quot;Write access is not =
required.&quot;<o:p></o:p></p></div></div></div><div><div><p =
class=3DMsoNormal>&nbsp;<o:p></o:p></p></div></div><div><div><p =
class=3DMsoNormal>Why can't new objects added to the row also allow the =
server to only claim<o:p></o:p></p></div></div><div><div><p =
class=3DMsoNormal>conformance to the read-only MODULE-COMPLIANCE? =
&nbsp;I don't see the<o:p></o:p></p></div></div><div><div><p =
class=3DMsoNormal>connection between RowStatus and a developer selecting =
which<o:p></o:p></p></div></div><div><div><p =
class=3DMsoNormal>compliance level it will support in an =
implementation.<o:p></o:p></p></div></div><div><div><p =
class=3DMsoNormal>&nbsp;<o:p></o:p></p></div></div><div><div><p =
class=3DMsoNormal>It does not matter if the new objects are read-only or =
read-create.<o:p></o:p></p></div></div><div><div><p class=3DMsoNormal>A =
&quot;read-only&quot; agent will magically instantiate the new =
columns,<o:p></o:p></p></div></div><div><div><p class=3DMsoNormal>if it =
supports the extension. A &quot;read-create&quot; agent will =
allow<o:p></o:p></p></div></div><div><div><p class=3DMsoNormal>a manager =
to create new rows, and allow the new r/c columns =
if<o:p></o:p></p></div></div><div><div><p class=3DMsoNormal>it supports =
the extension.<o:p></o:p></p></div></div><div><div><p =
class=3DMsoNormal>&nbsp;<o:p></o:p></p></div></div><div><div><p =
class=3DMsoNormal>&nbsp;<o:p></o:p></p></div></div><div><div><p =
class=3DMsoNormal>Andy<o:p></o:p></p></div></div><div><div><p =
class=3DMsoNormal>&nbsp;<o:p></o:p></p></div></div><div><div><p =
class=3DMsoNormal>&nbsp;<o:p></o:p></p></div></div><div><div><p =
class=3DMsoNormal>&nbsp;<o:p></o:p></p></div></div><div><div><p =
class=3DMsoNormal>&nbsp;<o:p></o:p></p></div><div><div><p =
class=3DMsoNormal>On Sun, Feb 16, 2014 at 4:11 PM, Joan Cucchiara &lt;<a =
href=3D"mailto:jcucchiara@mindspring.com" target=3D"_blank"><span =
style=3D'color:purple'>jcucchiara@mindspring.com</span></a>&gt; =
wrote:<o:p></o:p></p></div><div><p class=3DMsoNormal>Hi =
Adrian,<br><br>Please see inline below prefaced with JEC =
&gt;.<br><br>-----Original Message-----<br>From: Adrian Farrel =
[mailto:<a href=3D"mailto:adrian@olddog.co.uk"><span =
style=3D'color:purple'>adrian@olddog.co.uk</span></a>]<br>Sent: Friday, =
February 14, 2014 2:19 PM<br>To: 'Joan Cucchiara'; 't.petch'; 'Benoit =
Claise';<span class=3Dapple-converted-space>&nbsp;</span><a =
href=3D"mailto:mib-doctors@ietf.org"><span =
style=3D'color:purple'>mib-doctors@ietf.org</span></a><br>Subject: RE: =
configuration: writable MIB modules versus NETCONF/YANGmodules<br><br>Hi =
Joan,<br><br>[Reverting to the MIB Doctor Thread]<br><br>I will bow to =
your far (far, far) superior understanding of MIB-speak.<br><br>But I =
don't understand :-(<br><br>A row in a table that has RowStatus can have =
read-only objects and writeable<br>objects with Defaults as well as =
read-create objects.<br>When you use, for example, CreateAndGo the whole =
row gets created with<br>read-create objects as they are Set, with unSet =
writeable objects<br>defaulting, and with read-only objects filled with =
values from the<br>implementation.<br><br>JEC &gt; But that is kind of =
beside the point. &nbsp; The LSR and TE MIBs (rfc3813<br>and rfc3812, c. =
2004) have two conformance statements, Full and Read-only.<br>JEC &gt; =
&nbsp;Full Conformance allows for configuring with SNMP sets. &nbsp; So =
this<br>discussion is focusing on only the Full Conformance.<br>JEC &gt; =
&nbsp;The RowStatus objects in the TE and LSR MIB Modules (rfc3813 =
and<br>rfc3812) MUST be implemented as having &nbsp;a MAX-ACCESS of =
read-create. &nbsp; In<br>other words,<br>JEC &gt; a row can be created =
or deleted, etc. because the agent processes an<br>SNMP set request to =
configure the RowStatus object (i.e. a set is issued<br>JEC &gt; for =
create-and-go, destroy, etc).<br><br>JEC &gt; The point is that =
RowStatus &nbsp;creates the row because of an SNMP set<br>request. =
&nbsp;(Certainly rows can be created other ways too.)<br>JEC &gt; =
&nbsp;There is only ONE RowStatus for the entire row, and<br>JEC &gt; if =
that row is extended or AUGMENTed in additional MIB Modules, as =
in<br>the case draft-ietf-mpls-tp-te-mib which extends rows in rfc3813 =
and<br>rfc3812,<br>JEC &gt; then these extended rows are controlled ALSO =
by that same RowStatus<br>object which was defined in the TE/LSR MIB =
Modules.<br>JEC &gt; There is only one RowStatus object which controls =
the entire row, even<br>if parts<br>JEC&gt; of the row are in different =
MIB Modules (as with<br>draft-ietf-mpls-tp-te-mib). &nbsp; &nbsp;If you =
think about the case of deleting a<br>row, this makes sense.<br>JEC &gt; =
If the RowStatus object in the TE MIB is set to &quot;destroy&quot;, =
then the<br>deletion of the entire row must happen, even if the objects =
of that row are<br>in<br>JEC &gt; other MIB modules.<br><br>When I =
extend a table, surely I can extend with objects that are all =
only<br>read-only?<br>Furthermore, the whole row in the extension table =
could be automatically<br>created when the row in the extended table is =
created.<br><br>What am I missing?<br><br>JEC &gt; &nbsp;The agent =
&nbsp;MUST &quot;configure&quot; (e.g. create the objects, &nbsp;delete =
the<br>objects) in &nbsp;these extended rows &nbsp;in this draft because =
of an SNMP set<br>request.<br>JEC &gt; &nbsp; I don't see any way around =
this, without redefining the RowStatus<br>TC, or rewriting the TE or LSR =
MIBs or (probably the simplest solution) the<br>JEC&gt; co-authors write =
the draft in such a way as to not extend tables in the<br>TE and LSR =
MIBs.<br><br>JEC &gt; So to summarize, an SNMP agent that supports this =
draft MUST support<br>the SNMP set request for RowStatus for the rows =
which extend rows in<br>JEC&gt; the LSR and TE MIBs.<br><br>JEC&gt; =
Since that is the case, and since this draft is tied to these RFCs =
that<br>are 10 years old now, &nbsp;I don't have an issue<br>JEC&gt; =
with them configuring via SNMP for other objects also (but that is =
just<br>my opinion).<br><br>Thanks,<br>&nbsp; =
-Joan<br><br><br><br>Thanks,<br>Adrian<br><br>&gt; -----Original =
Message-----<br>&gt; From: OPS-AREA [mailto:<a =
href=3D"mailto:ops-area-bounces@ietf.org"><span =
style=3D'color:purple'>ops-area-bounces@ietf.org</span></a>] On Behalf =
Of Joan<br>&gt; Cucchiara<br>&gt; Sent: 14 February 2014 18:28<br>&gt; =
To: 't.petch'; 'Benoit Claise';<span =
class=3Dapple-converted-space>&nbsp;</span><a =
href=3D"mailto:ops-area@ietf.org"><span =
style=3D'color:purple'>ops-area@ietf.org</span></a><br>&gt; Subject: Re: =
[OPS-AREA] configuration: writable MIB modules versus<br>&gt; =
NETCONF/YANGmodules<br>&gt;<br>&gt; Hi Tom,<br>&gt;<br>&gt; As the MIB =
Dr. on this draft, &nbsp;I have responded on the MIB Dr. thread<br>&gt; =
that I do NOT see a way to make this draft =
(draft-ietf-mpls-tp-te-mib)<br>read-only.<br>&gt; This draft contains =
extension tables for tables in LSR and TE MIBS which<br>are<br>&gt; =
created by RowStatus (which is read-create). &nbsp; Like it or not, =
RowStatus<br>of<br>&gt; those MIBs (i.e. LSR and TE MIBs) effect the =
rows in the extension tables<br>of<br>&gt; this draft (think the case of =
row creation or row deletion). &nbsp; That is an<br>&gt; SNMP Set =
operation which effects the draft.<br>&gt;<br>&gt; I believe the =
statement that Benoit puts forth would allow for such a<br>&gt; =
situation as this draft, specifically:<br>&gt;<br>&gt; &quot;... SNMP =
MIB modules modifying persistent configuration state =
&nbsp;should<br>&gt; only be produced by working groups in cases of =
clear utility and<br>&gt; consensus to use SNMP write operations for =
configuration.&quot;<br>&gt;<br>&gt; Perhaps, additional wording, such =
as &quot;For example, in the case of<br>&gt; proposed SNMP MIB modules =
which extend or augment rows that are<br>&gt; created by configuration =
in a SNMP MIB module which is already a RFC,<br>&gt; the proposed SNNP =
MIB modules will be grandfathered, if the working<br>&gt; group finds =
consensus to do so.&quot;<br>&gt;<br>&gt; However, I am okay with the =
statement as written.<br>&gt;<br>&gt; Thanks,<br>&gt; &nbsp; =
-Joan<br>&gt;<br>&gt;<br>&gt; -----Original Message-----<br>&gt; From: =
OPS-AREA [mailto:<a href=3D"mailto:ops-area-bounces@ietf.org"><span =
style=3D'color:purple'>ops-area-bounces@ietf.org</span></a>] On Behalf =
Of t.petch<br>&gt; Sent: Friday, February 14, 2014 10:02 AM<br>&gt; To: =
Benoit Claise;<span class=3Dapple-converted-space>&nbsp;</span><a =
href=3D"mailto:ops-area@ietf.org"><span =
style=3D'color:purple'>ops-area@ietf.org</span></a><br>&gt; Subject: Re: =
[OPS-AREA] configuration: writable MIB modules versus<br>&gt; =
NETCONF/YANGmodules<br>&gt;<br>&gt; ----- Original Message -----<br>&gt; =
From: &quot;Benoit Claise&quot; &lt;<a =
href=3D"mailto:bclaise@cisco.com"><span =
style=3D'color:purple'>bclaise@cisco.com</span></a>&gt;<br>&gt; To: =
&lt;<a href=3D"mailto:ops-area@ietf.org"><span =
style=3D'color:purple'>ops-area@ietf.org</span></a>&gt;<br>&gt; Sent: =
Friday, February 14, 2014 12:39 AM<br>&gt; &gt; Dear all,<br>&gt; =
&gt;<br>&gt; &gt; We occasionally see read-write MIB module proposals =
within the IETF.<br>&gt; &gt; However, the write capabilities of those =
MIB modules are rarely<br>&gt; implemented.<br>&gt; &gt;<br>&gt; &gt; =
While discussing this issue with the MIB doctors, we arrive to =
the<br>&gt; &gt; conclusion that it's now time to set the direction for =
future MIB<br>&gt; &gt; developments within the IETF. Basically, let's =
not specify<br>&gt; &gt; read-write MIB modules unless we have a good =
reason. Read-only MIB<br>&gt; &gt; modules are still fine though, as =
SNMP is clearly used for monitoring<br>purposes.<br>&gt; &gt;<br>&gt; =
&gt; Here is the statement we came up with:<br>&gt; &gt;<br>&gt; &gt; =
&nbsp; &nbsp; The OPS area recommends the use of NETCONF/YANG standards =
for<br>&gt; &gt; &nbsp; &nbsp; configuration. IETF working groups are =
therefore encouraged to use<br>&gt; &gt; &nbsp; &nbsp; the NETCONF/YANG =
standards for configuration, specifically in new<br>&gt; &gt; &nbsp; =
&nbsp; charters. SNMP MIB modules modifying persistent =
configuration<br>&gt; state<br>&gt; &gt; &nbsp; &nbsp; should only be =
produced by working groups in cases of clear<br>&gt; utility<br>&gt; =
&gt; &nbsp; &nbsp; and consensus to use SNMP write operations for =
configuration.<br>&gt; &gt;<br>&gt; &gt; Ideally, this should become an =
IESG statement.<br>&gt; &gt; Your feedback is most =
welcome.<br>&gt;<br>&gt; You probably know that there is currently a =
consensus call in progress<br>&gt; over<br>&gt;<br>&gt; &quot;Please =
indicate Support or Oppose for this MIB<br>&gt; =
(draft-ietf-mpls-tp-te-mib) to be read-only.&quot;<br>&gt;<br>&gt; and I =
was pleasantly surprised to see opposition, albeit with one<br>&gt; =
opponent later changing their mind (perhaps they were sat on from =
a<br>&gt; height:-). &nbsp;I don't see much sign of Netxxxx in the mpls =
arena but<br>&gt; there is a need there for configuration, since there =
need not be a control<br>plane to set things up.<br>&gt; Perhaps =
writable MIB modules will still be with us in the distant<br>&gt; future =
in some corners of the Internet..<br>&gt;<br>&gt; Ideally, this idea =
would be fleshed out in an I-D.<br>&gt;<br>&gt; Tom =
Petch<br>&gt;<br>&gt; &gt; Regards, the MIB doctors &amp; =
Benoit<br>&gt;<br>&gt; =
_______________________________________________<br>&gt; OPS-AREA mailing =
list<br>&gt;<span class=3Dapple-converted-space>&nbsp;</span><a =
href=3D"mailto:OPS-AREA@ietf.org"><span =
style=3D'color:purple'>OPS-AREA@ietf.org</span></a><br>&gt;<span =
class=3Dapple-converted-space>&nbsp;</span><a =
href=3D"https://www.ietf.org/mailman/listinfo/ops-area" =
target=3D"_blank"><span =
style=3D'color:purple'>https://www.ietf.org/mailman/listinfo/ops-area</sp=
an></a><br>&gt;<br>&gt;<br>&gt; -----<br>&gt; No virus found in this =
message.<br>&gt; Checked by AVG -<span =
class=3Dapple-converted-space>&nbsp;</span><a =
href=3D"http://www.avg.com/" target=3D"_blank"><span =
style=3D'color:purple'>www.avg.com</span></a><br>&gt; Version: =
2014.0.4259 / Virus Database: 3705/7092 - Release Date:<br>&gt; =
02/14/14<br>&gt;<br>&gt; =
_______________________________________________<br>&gt; OPS-AREA mailing =
list<br>&gt;<span class=3Dapple-converted-space>&nbsp;</span><a =
href=3D"mailto:OPS-AREA@ietf.org"><span =
style=3D'color:purple'>OPS-AREA@ietf.org</span></a><br>&gt;<span =
class=3Dapple-converted-space>&nbsp;</span><a =
href=3D"https://www.ietf.org/mailman/listinfo/ops-area" =
target=3D"_blank"><span =
style=3D'color:purple'>https://www.ietf.org/mailman/listinfo/ops-area</sp=
an></a><br><br><br><br>-----<br>No virus found in this =
message.<br>Checked by AVG -<span =
class=3Dapple-converted-space>&nbsp;</span><a =
href=3D"http://www.avg.com/" target=3D"_blank"><span =
style=3D'color:purple'>www.avg.com</span></a><br>Version: 2014.0.4259 / =
Virus Database: 3705/7092 - Release Date: =
02/14/14<br><br>_______________________________________________<br>MIB-DO=
CTORS mailing list<br><a href=3D"mailto:MIB-DOCTORS@ietf.org"><span =
style=3D'color:purple'>MIB-DOCTORS@ietf.org</span></a><br><a =
href=3D"https://www.ietf.org/mailman/listinfo/mib-doctors" =
target=3D"_blank"><span =
style=3D'color:purple'>https://www.ietf.org/mailman/listinfo/mib-doctors<=
/span></a><o:p></o:p></p></div></div><div><p =
class=3DMsoNormal>&nbsp;<o:p></o:p></p></div></div></div><div><p =
class=3DMsoNormal>No virus found in this message.<br>Checked by AVG =
-<span class=3Dapple-converted-space>&nbsp;</span><a =
href=3D"http://www.avg.com/"><span =
style=3D'color:purple'>www.avg.com</span></a><br>Version: 2014.0.4259 / =
Virus Database: 3705/7098 - Release Date: =
02/16/14<o:p></o:p></p></div><div class=3DMsoNormal align=3Dcenter =
style=3D'text-align:center'><hr size=3D1 width=3D"100%" noshade =
style=3D'color:#A0A0A0' align=3Dcenter></div><div><p =
class=3DMsoNormal>No virus found in this message.<br>Checked by AVG =
-<span class=3Dapple-converted-space>&nbsp;</span><a =
href=3D"http://www.avg.com/"><span =
style=3D'color:purple'>www.avg.com</span></a><br>Version: 2014.0.4259 / =
Virus Database: 3697/7083 - Release Date: =
02/11/14<o:p></o:p></p></div><p class=3DMsoNormal><span =
style=3D'font-family:"Helvetica","sans-serif"'>__________________________=
_____________________<br>MIB-DOCTORS mailing list<br><a =
href=3D"mailto:MIB-DOCTORS@ietf.org"><span =
style=3D'color:purple'>MIB-DOCTORS@ietf.org</span></a><br><a =
href=3D"https://www.ietf.org/mailman/listinfo/mib-doctors"><span =
style=3D'color:purple'>https://www.ietf.org/mailman/listinfo/mib-doctors<=
/span></a><o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_007A_01CF2C90.3ABB4D20--



From nobody Tue Feb 18 07:02:56 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 A8AFB1A04FD for <mib-doctors@ietfa.amsl.com>; Tue, 18 Feb 2014 07:02:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.848
X-Spam-Level: 
X-Spam-Status: No, score=-1.848 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_15=0.6, RP_MATCHES_RCVD=-0.548] 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 Y8KS_HfBFPlf for <mib-doctors@ietfa.amsl.com>; Tue, 18 Feb 2014 07:02:50 -0800 (PST)
Received: from p-us1-iereast-outbound.us1.avaya.com (p-us1-iereast-outbound.us1.avaya.com [135.11.29.13]) by ietfa.amsl.com (Postfix) with ESMTP id 475701A04F6 for <mib-doctors@ietf.org>; Tue, 18 Feb 2014 07:02:50 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApQFAPN0A1OHCzIm/2dsb2JhbABZgmUhOFe4LYcjgRgWdIIlAQEBAQMBAQEPFRMPJQsMBAIBCA0BAwMBAQEBChQJBycLFAkIAgQOBQgah2MBDJ8drFUXjh0zMQcGgx6BFASfG4s0gW+BPoFoQg
X-IronPort-AV: E=Sophos;i="4.97,502,1389762000"; d="scan'208";a="49987772"
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; 18 Feb 2014 10:02:46 -0500
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; 18 Feb 2014 09:49:51 -0500
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; Tue, 18 Feb 2014 10:02:44 -0500
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: Thomas Nadeau <tnadeau@lucidvision.com>
Thread-Topic: [MIB-DOCTORS] configuration: writable MIB modules versus NETCONF/YANGmodules
Thread-Index: AQHPLLNe7mRsszR4rEC7y4sAuzOokJq7Goxw
Date: Tue, 18 Feb 2014 15:02:43 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA2E421F9E@AZ-FFEXMB04.global.avaya.com>
References: <00b101cf29b9$95d979e0$c18c6da0$@olddog.co.uk> <9904FB1B0159DA42B0B887B7FA8119CA2E4187BC@AZ-FFEXMB04.global.avaya.com> <013501cf2b41$4d26a2c0$e773e840$@olddog.co.uk> <9904FB1B0159DA42B0B887B7FA8119CA2E41AF25@AZ-FFEXMB04.global.avaya.com> <E73A794D-26D6-47B4-89EC-2F49DBD51770@lucidvision.com>
In-Reply-To: <E73A794D-26D6-47B4-89EC-2F49DBD51770@lucidvision.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: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/2tDhvmHZPRw8RNrnKKPz8QN-pSM
Cc: Farrel Adrian <adrian@olddog.co.uk>, "t.petch" <ietfc@btconnect.com>, "mib-doctors@ietf.org" <mib-doctors@ietf.org>
Subject: Re: [MIB-DOCTORS] configuration: writable MIB modules versus NETCONF/YANGmodules
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, 18 Feb 2014 15:02:54 -0000

Tom,

There is only one table. There is only one conceptual MIB. Objects in the t=
able happen to be defined in two MIB modules (you call them A and B) - but =
the operations with rows apply to all objects.

If you wanted to define two separate tables you would have defined them sep=
arately using the same indexation, not use the AUGMENT construct.=20

This is at least my understanding.=20

Regards,

Dan


> -----Original Message-----
> From: Thomas Nadeau [mailto:tnadeau@lucidvision.com]
> Sent: Tuesday, February 18, 2014 4:12 PM
> To: Romascanu, Dan (Dan)
> Cc: Farrel Adrian; Cucchiara Joan; t.petch; Benoit Claise; mib-doctors@ie=
tf.org
> Subject: Re: [MIB-DOCTORS] configuration: writable MIB modules versus
> NETCONF/YANGmodules
>=20
>=20
> 	I am not sure as you cannot create rows in the new MIB module (call
> it B); they're created in the existing one (call it A) and as a side-effe=
ct objects
> are created in B, which is normal agent behavior in an "all writable" sit=
uation
> today.  We should point out that this occurs in both cases of AUGMENTSs a=
nd
> "extends" rows.  I do not see any issue with this as the behavior is as
> expected:
>=20
> 	So if I "row create new row in A" -> the system creates an entry in A,
> and row is created in B that corresponds. When you query A or B, you get
> responses.  Row destruction happens consistently too since you cannot iss=
ue
> row destruction instructions to B, but only to A, and corresponding entri=
es in
> B are removed.  Of course, if I try a row create on B it fails.
>=20
> 	The other way to look at this is that this is the same situation as if w=
e
> had the ability to configure A as read-write/create and B as read-only (w=
here
> B contained read-write/create entries).  The exact same behavior should
> result.
>=20
> 	--tom
>=20
>=20
>=20
>=20
> On Feb 16, 2014:2:45 PM, at 2:45 PM, Romascanu, Dan (Dan)
> <dromasca@avaya.com> wrote:
>=20
> > By using the already existing RowStatus object in the base table the
> creation of new rows in the base table leads to the creation of new rows =
in
> the extended table. Even if the objects that you defined are all read-onl=
y,
> the effect is the same as defining a new table with a RowStatus object.
> >
> > Dan
> >
> >
> >> -----Original Message-----
> >> From: Adrian Farrel [mailto:adrian@olddog.co.uk]
> >> Sent: Sunday, February 16, 2014 8:03 PM
> >> To: Romascanu, Dan (Dan); 'Joan Cucchiara'; 't.petch'; 'Benoit
> >> Claise'; mib- doctors@ietf.org
> >> Subject: RE: [MIB-DOCTORS] configuration: writable MIB modules versus
> >> NETCONF/YANGmodules
> >>
> >> I'm sorry if I am being thick.
> >>
> >> The row in the old table has a RowStatus object which is, of course,
> >> read- create.
> >> The extension table entry has no object with SYNTAX rowStatus, but is
> >> created automatically when the entry in the old table is created.
> >>
> >> A
> >>
> >>> -----Original Message-----
> >>> From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com]
> >>> Sent: 16 February 2014 11:55
> >>> To: adrian@olddog.co.uk; 'Joan Cucchiara'; 't.petch'; 'Benoit
> >>> Claise';
> >>> mib- doctors@ietf.org
> >>> Subject: RE: [MIB-DOCTORS] configuration: writable MIB modules
> >>> versus NETCONF/YANGmodules
> >>>
> >>> Hi Adrian,
> >>>
> >>> Even if the row you extend is composed only by objects with
> >>> MAX-ACCESS
> >>> read- only, creating a new row involves a write operation on the
> >>> object with SYNTAX RowStatus.
> >>>
> >>> This is (I guess) what Joan meant.
> >>>
> >>> Creating a new row may mean a modification of configuration on the
> >>> managed entity. You now have n+1 rows instead of n rows in the table.
> >>>
> >>> Regards,
> >>>
> >>> Dan
> >>>
> >>>
> >>>> -----Original Message-----
> >>>> From: MIB-DOCTORS [mailto:mib-doctors-bounces@ietf.org] On Behalf
> >> Of
> >>>> Adrian Farrel
> >>>> Sent: Friday, February 14, 2014 9:19 PM
> >>>> To: 'Joan Cucchiara'; 't.petch'; 'Benoit Claise';
> >>>> mib-doctors@ietf.org
> >>>> Subject: Re: [MIB-DOCTORS] configuration: writable MIB modules
> >>>> versus NETCONF/YANGmodules
> >>>>
> >>>> Hi Joan,
> >>>>
> >>>> [Reverting to the MIB Doctor Thread]
> >>>>
> >>>> I will bow to your far (far, far) superior understanding of MIB-spea=
k.
> >>>>
> >>>> But I don't understand :-(
> >>>>
> >>>> A row in a table that has RowStatus can have read-only objects and
> >>>> writeable objects with Defaults as well as read-create objects.
> >>>> When you use, for example, CreateAndGo the whole row gets created
> >>>> with read-create objects as they are Set, with unSet writeable
> >>>> objects
> >> defaulting,
> >>>> and with read-only objects filled with values from the implementatio=
n.
> >>>>
> >>>> When I extend a table, surely I can extend with objects that are
> >>>> all only
> >> read-
> >>>> only?
> >>>> Furthermore, the whole row in the extension table could be
> >>>> automatically created when the row in the extended table is created.
> >>>>
> >>>> What am I missing?
> >>>>
> >>>> Thanks,
> >>>> Adrian
> >>>>
> >>>>> -----Original Message-----
> >>>>> From: OPS-AREA [mailto:ops-area-bounces@ietf.org] On Behalf Of
> >>>>> Joan Cucchiara
> >>>>> Sent: 14 February 2014 18:28
> >>>>> To: 't.petch'; 'Benoit Claise'; ops-area@ietf.org
> >>>>> Subject: Re: [OPS-AREA] configuration: writable MIB modules versus
> >>>>> NETCONF/YANGmodules
> >>>>>
> >>>>> Hi Tom,
> >>>>>
> >>>>> As the MIB Dr. on this draft,  I have responded on the MIB Dr.
> >>>>> thread that I do NOT see a way to make this draft
> >>>>> (draft-ietf-mpls-tp-te-mib)
> >> read-
> >>>> only.
> >>>>> This draft contains extension tables for tables in LSR and TE MIBS
> >>>>> which
> >> are
> >>>>> created by RowStatus (which is read-create).   Like it or not,
> RowStatus
> >> of
> >>>>> those MIBs (i.e. LSR and TE MIBs) effect the rows in the extension
> >>>>> tables
> >> of
> >>>>> this draft (think the case of row creation or row deletion).   That=
 is an
> >>>>> SNMP Set operation which effects the draft.
> >>>>>
> >>>>> I believe the statement that Benoit puts forth would allow for
> >>>>> such a situation as this draft, specifically:
> >>>>>
> >>>>> "... SNMP MIB modules modifying persistent configuration state
> >>>>> should only be produced by working groups in cases of clear
> >>>>> utility and consensus to use SNMP write operations for
> configuration."
> >>>>>
> >>>>> Perhaps, additional wording, such as "For example, in the case of
> >>>>> proposed SNMP MIB modules which extend or augment rows that
> are
> >>>>> created by configuration in a SNMP MIB module which is already a
> >>>>> RFC, the proposed SNNP MIB modules will be grandfathered, if the
> >>>>> working group finds consensus to do so."
> >>>>>
> >>>>> However, I am okay with the statement as written.
> >>>>>
> >>>>> Thanks,
> >>>>>  -Joan
> >>>>>
> >>>>>
> >>>>> -----Original Message-----
> >>>>> From: OPS-AREA [mailto:ops-area-bounces@ietf.org] On Behalf Of
> >>>>> t.petch
> >>>>> Sent: Friday, February 14, 2014 10:02 AM
> >>>>> To: Benoit Claise; ops-area@ietf.org
> >>>>> Subject: Re: [OPS-AREA] configuration: writable MIB modules versus
> >>>>> NETCONF/YANGmodules
> >>>>>
> >>>>> ----- Original Message -----
> >>>>> From: "Benoit Claise" <bclaise@cisco.com>
> >>>>> To: <ops-area@ietf.org>
> >>>>> Sent: Friday, February 14, 2014 12:39 AM
> >>>>>> Dear all,
> >>>>>>
> >>>>>> We occasionally see read-write MIB module proposals within the
> IETF.
> >>>>>> However, the write capabilities of those MIB modules are rarely
> >>>>> implemented.
> >>>>>>
> >>>>>> While discussing this issue with the MIB doctors, we arrive to
> >>>>>> the conclusion that it's now time to set the direction for future
> >>>>>> MIB developments within the IETF. Basically, let's not specify
> >>>>>> read-write MIB modules unless we have a good reason.
> >>>>>> Read-only MIB modules are still fine though, as SNMP is clearly
> >>>>>> used for monitoring
> >>>> purposes.
> >>>>>>
> >>>>>> Here is the statement we came up with:
> >>>>>>
> >>>>>>    The OPS area recommends the use of NETCONF/YANG standards
> >> for
> >>>>>>    configuration. IETF working groups are therefore encouraged to
> use
> >>>>>>    the NETCONF/YANG standards for configuration, specifically in n=
ew
> >>>>>>    charters. SNMP MIB modules modifying persistent configuration
> >>>>> state
> >>>>>>    should only be produced by working groups in cases of clear
> >>>>> utility
> >>>>>>    and consensus to use SNMP write operations for configuration.
> >>>>>>
> >>>>>> Ideally, this should become an IESG statement.
> >>>>>> Your feedback is most welcome.
> >>>>>
> >>>>> You probably know that there is currently a consensus call in
> >>>>> progress over
> >>>>>
> >>>>> "Please indicate Support or Oppose for this MIB
> >>>>> (draft-ietf-mpls-tp-te-mib) to be read-only."
> >>>>>
> >>>>> and I was pleasantly surprised to see opposition, albeit with one
> >>>>> opponent later changing their mind (perhaps they were sat on from
> >>>>> a height:-).  I don't see much sign of Netxxxx in the mpls arena
> >>>>> but there is a need there for configuration, since there need not
> >>>>> be a control
> >>>> plane to set things up.
> >>>>> Perhaps writable MIB modules will still be with us in the distant
> >>>>> future in some corners of the Internet..
> >>>>>
> >>>>> Ideally, this idea would be fleshed out in an I-D.
> >>>>>
> >>>>> Tom Petch
> >>>>>
> >>>>>> Regards, the MIB doctors & Benoit
> >>>>>
> >>>>> _______________________________________________
> >>>>> OPS-AREA mailing list
> >>>>> OPS-AREA@ietf.org
> >>>>> https://www.ietf.org/mailman/listinfo/ops-area
> >>>>>
> >>>>>
> >>>>> -----
> >>>>> No virus found in this message.
> >>>>> Checked by AVG - www.avg.com
> >>>>> Version: 2014.0.4259 / Virus Database: 3705/7092 - Release Date:
> >>>>> 02/14/14
> >>>>>
> >>>>> _______________________________________________
> >>>>> OPS-AREA mailing list
> >>>>> OPS-AREA@ietf.org
> >>>>> https://www.ietf.org/mailman/listinfo/ops-area
> >>>>
> >>>> _______________________________________________
> >>>> 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
> >


From nobody Tue Feb 18 07:16:03 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 09DC81A01F0 for <mib-doctors@ietfa.amsl.com>; Tue, 18 Feb 2014 07:16:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.678
X-Spam-Level: 
X-Spam-Status: No, score=-0.678 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, J_CHICKENPOX_15=0.6, 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 THqEsDhgtwWN for <mib-doctors@ietfa.amsl.com>; Tue, 18 Feb 2014 07:15:58 -0800 (PST)
Received: from mail-qg0-f49.google.com (mail-qg0-f49.google.com [209.85.192.49]) by ietfa.amsl.com (Postfix) with ESMTP id 39B411A01D5 for <mib-doctors@ietf.org>; Tue, 18 Feb 2014 07:15:58 -0800 (PST)
Received: by mail-qg0-f49.google.com with SMTP id j107so7120606qga.8 for <mib-doctors@ietf.org>; Tue, 18 Feb 2014 07:15:55 -0800 (PST)
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=ph0Dc05mgR5Llj9dWRJsIcWkAiktDdgof8bVBjzIc9g=; b=BKu+lh+8TP8Vy7zGoO+wxtfiIPDzXKWkBtXS9yMIP/lLs9cx5FhDAr2hiQt+GewMQO M7906RdG+HnzpYvYdldiIK14ew7dCO/jCnA3NIP0cuiOL414PpsOhW6CFkj57kBwUhaN PEA9LsWodtSdsxHYWWWG0lhvmG2cw21nNeLEna/MMpjqNAzrpJ7dSuGUMFFUWkVPDmtu q/blS46PAhbr7CDCaFNMw5K6rk5bB1Qp1O8yXICLK0DFlMt0EpgwR3k6GwA/pLroCcEK XYjW5kBOobj1BJsbQAI6sZBWTrUZs8tq1eq5Kx5v1Z7SD43UgKTvqOPXS8Pvc9f1BozY HSig==
X-Gm-Message-State: ALoCoQmwdYGAb03DxV4lSf7jS+RbccQ3dYwqO5D+dbrICe7A348ZxEH9ruGdQQHq8YizggpgYxGw
MIME-Version: 1.0
X-Received: by 10.224.46.130 with SMTP id j2mr43181701qaf.7.1392736554852; Tue, 18 Feb 2014 07:15:54 -0800 (PST)
Received: by 10.140.98.130 with HTTP; Tue, 18 Feb 2014 07:15:54 -0800 (PST)
In-Reply-To: <9904FB1B0159DA42B0B887B7FA8119CA2E421F9E@AZ-FFEXMB04.global.avaya.com>
References: <00b101cf29b9$95d979e0$c18c6da0$@olddog.co.uk> <9904FB1B0159DA42B0B887B7FA8119CA2E4187BC@AZ-FFEXMB04.global.avaya.com> <013501cf2b41$4d26a2c0$e773e840$@olddog.co.uk> <9904FB1B0159DA42B0B887B7FA8119CA2E41AF25@AZ-FFEXMB04.global.avaya.com> <E73A794D-26D6-47B4-89EC-2F49DBD51770@lucidvision.com> <9904FB1B0159DA42B0B887B7FA8119CA2E421F9E@AZ-FFEXMB04.global.avaya.com>
Date: Tue, 18 Feb 2014 07:15:54 -0800
Message-ID: <CABCOCHROPyAaRF6f5j3NjtduuBw7y_xmG0nBcy-nVVap9EgXww@mail.gmail.com>
From: Andy Bierman <andy@yumaworks.com>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
Content-Type: multipart/alternative; boundary=001a11c2a9ca9e343104f2afbf8f
Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/Ppt13aEQVbvdU_hUEnHBUT1Hcmo
Cc: "t.petch" <ietfc@btconnect.com>, "mib-doctors@ietf.org" <mib-doctors@ietf.org>, Farrel Adrian <adrian@olddog.co.uk>
Subject: Re: [MIB-DOCTORS] configuration: writable MIB modules versus NETCONF/YANGmodules
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, 18 Feb 2014 15:16:02 -0000

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

On Tue, Feb 18, 2014 at 7:02 AM, Romascanu, Dan (Dan) <dromasca@avaya.com>wrote:

> Tom,
>
> There is only one table. There is only one conceptual MIB. Objects in the
> table happen to be defined in two MIB modules (you call them A and B) - but
> the operations with rows apply to all objects.
>
> If you wanted to define two separate tables you would have defined them
> separately using the same indexation, not use the AUGMENT construct.
>
> This is at least my understanding.
>
>

OK -- you seem to be saying "If the agent supports read-create compliance
for the A columns, then it must support read-create for the new B columns".
Yes -- there is only 1 conceptual row and 1 RowStatus.  But an agent can
choose to implement the read-only compliance, so there is no real
requirement to support read-create for the B columns.  Making them read-only
instead of read-create is not necessary.


Regards,
>
> Dan
>

Andy


>
>
> > -----Original Message-----
> > From: Thomas Nadeau [mailto:tnadeau@lucidvision.com]
> > Sent: Tuesday, February 18, 2014 4:12 PM
> > To: Romascanu, Dan (Dan)
> > Cc: Farrel Adrian; Cucchiara Joan; t.petch; Benoit Claise;
> mib-doctors@ietf.org
> > Subject: Re: [MIB-DOCTORS] configuration: writable MIB modules versus
> > NETCONF/YANGmodules
> >
> >
> >       I am not sure as you cannot create rows in the new MIB module (call
> > it B); they're created in the existing one (call it A) and as a
> side-effect objects
> > are created in B, which is normal agent behavior in an "all writable"
> situation
> > today.  We should point out that this occurs in both cases of AUGMENTSs
> and
> > "extends" rows.  I do not see any issue with this as the behavior is as
> > expected:
> >
> >       So if I "row create new row in A" -> the system creates an entry
> in A,
> > and row is created in B that corresponds. When you query A or B, you get
> > responses.  Row destruction happens consistently too since you cannot
> issue
> > row destruction instructions to B, but only to A, and corresponding
> entries in
> > B are removed.  Of course, if I try a row create on B it fails.
> >
> >       The other way to look at this is that this is the same situation
> as if we
> > had the ability to configure A as read-write/create and B as read-only
> (where
> > B contained read-write/create entries).  The exact same behavior should
> > result.
> >
> >       --tom
> >
> >
> >
> >
> > On Feb 16, 2014:2:45 PM, at 2:45 PM, Romascanu, Dan (Dan)
> > <dromasca@avaya.com> wrote:
> >
> > > By using the already existing RowStatus object in the base table the
> > creation of new rows in the base table leads to the creation of new rows
> in
> > the extended table. Even if the objects that you defined are all
> read-only,
> > the effect is the same as defining a new table with a RowStatus object.
> > >
> > > Dan
> > >
> > >
> > >> -----Original Message-----
> > >> From: Adrian Farrel [mailto:adrian@olddog.co.uk]
> > >> Sent: Sunday, February 16, 2014 8:03 PM
> > >> To: Romascanu, Dan (Dan); 'Joan Cucchiara'; 't.petch'; 'Benoit
> > >> Claise'; mib- doctors@ietf.org
> > >> Subject: RE: [MIB-DOCTORS] configuration: writable MIB modules versus
> > >> NETCONF/YANGmodules
> > >>
> > >> I'm sorry if I am being thick.
> > >>
> > >> The row in the old table has a RowStatus object which is, of course,
> > >> read- create.
> > >> The extension table entry has no object with SYNTAX rowStatus, but is
> > >> created automatically when the entry in the old table is created.
> > >>
> > >> A
> > >>
> > >>> -----Original Message-----
> > >>> From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com]
> > >>> Sent: 16 February 2014 11:55
> > >>> To: adrian@olddog.co.uk; 'Joan Cucchiara'; 't.petch'; 'Benoit
> > >>> Claise';
> > >>> mib- doctors@ietf.org
> > >>> Subject: RE: [MIB-DOCTORS] configuration: writable MIB modules
> > >>> versus NETCONF/YANGmodules
> > >>>
> > >>> Hi Adrian,
> > >>>
> > >>> Even if the row you extend is composed only by objects with
> > >>> MAX-ACCESS
> > >>> read- only, creating a new row involves a write operation on the
> > >>> object with SYNTAX RowStatus.
> > >>>
> > >>> This is (I guess) what Joan meant.
> > >>>
> > >>> Creating a new row may mean a modification of configuration on the
> > >>> managed entity. You now have n+1 rows instead of n rows in the table.
> > >>>
> > >>> Regards,
> > >>>
> > >>> Dan
> > >>>
> > >>>
> > >>>> -----Original Message-----
> > >>>> From: MIB-DOCTORS [mailto:mib-doctors-bounces@ietf.org] On Behalf
> > >> Of
> > >>>> Adrian Farrel
> > >>>> Sent: Friday, February 14, 2014 9:19 PM
> > >>>> To: 'Joan Cucchiara'; 't.petch'; 'Benoit Claise';
> > >>>> mib-doctors@ietf.org
> > >>>> Subject: Re: [MIB-DOCTORS] configuration: writable MIB modules
> > >>>> versus NETCONF/YANGmodules
> > >>>>
> > >>>> Hi Joan,
> > >>>>
> > >>>> [Reverting to the MIB Doctor Thread]
> > >>>>
> > >>>> I will bow to your far (far, far) superior understanding of
> MIB-speak.
> > >>>>
> > >>>> But I don't understand :-(
> > >>>>
> > >>>> A row in a table that has RowStatus can have read-only objects and
> > >>>> writeable objects with Defaults as well as read-create objects.
> > >>>> When you use, for example, CreateAndGo the whole row gets created
> > >>>> with read-create objects as they are Set, with unSet writeable
> > >>>> objects
> > >> defaulting,
> > >>>> and with read-only objects filled with values from the
> implementation.
> > >>>>
> > >>>> When I extend a table, surely I can extend with objects that are
> > >>>> all only
> > >> read-
> > >>>> only?
> > >>>> Furthermore, the whole row in the extension table could be
> > >>>> automatically created when the row in the extended table is created.
> > >>>>
> > >>>> What am I missing?
> > >>>>
> > >>>> Thanks,
> > >>>> Adrian
> > >>>>
> > >>>>> -----Original Message-----
> > >>>>> From: OPS-AREA [mailto:ops-area-bounces@ietf.org] On Behalf Of
> > >>>>> Joan Cucchiara
> > >>>>> Sent: 14 February 2014 18:28
> > >>>>> To: 't.petch'; 'Benoit Claise'; ops-area@ietf.org
> > >>>>> Subject: Re: [OPS-AREA] configuration: writable MIB modules versus
> > >>>>> NETCONF/YANGmodules
> > >>>>>
> > >>>>> Hi Tom,
> > >>>>>
> > >>>>> As the MIB Dr. on this draft,  I have responded on the MIB Dr.
> > >>>>> thread that I do NOT see a way to make this draft
> > >>>>> (draft-ietf-mpls-tp-te-mib)
> > >> read-
> > >>>> only.
> > >>>>> This draft contains extension tables for tables in LSR and TE MIBS
> > >>>>> which
> > >> are
> > >>>>> created by RowStatus (which is read-create).   Like it or not,
> > RowStatus
> > >> of
> > >>>>> those MIBs (i.e. LSR and TE MIBs) effect the rows in the extension
> > >>>>> tables
> > >> of
> > >>>>> this draft (think the case of row creation or row deletion).
> That is an
> > >>>>> SNMP Set operation which effects the draft.
> > >>>>>
> > >>>>> I believe the statement that Benoit puts forth would allow for
> > >>>>> such a situation as this draft, specifically:
> > >>>>>
> > >>>>> "... SNMP MIB modules modifying persistent configuration state
> > >>>>> should only be produced by working groups in cases of clear
> > >>>>> utility and consensus to use SNMP write operations for
> > configuration."
> > >>>>>
> > >>>>> Perhaps, additional wording, such as "For example, in the case of
> > >>>>> proposed SNMP MIB modules which extend or augment rows that
> > are
> > >>>>> created by configuration in a SNMP MIB module which is already a
> > >>>>> RFC, the proposed SNNP MIB modules will be grandfathered, if the
> > >>>>> working group finds consensus to do so."
> > >>>>>
> > >>>>> However, I am okay with the statement as written.
> > >>>>>
> > >>>>> Thanks,
> > >>>>>  -Joan
> > >>>>>
> > >>>>>
> > >>>>> -----Original Message-----
> > >>>>> From: OPS-AREA [mailto:ops-area-bounces@ietf.org] On Behalf Of
> > >>>>> t.petch
> > >>>>> Sent: Friday, February 14, 2014 10:02 AM
> > >>>>> To: Benoit Claise; ops-area@ietf.org
> > >>>>> Subject: Re: [OPS-AREA] configuration: writable MIB modules versus
> > >>>>> NETCONF/YANGmodules
> > >>>>>
> > >>>>> ----- Original Message -----
> > >>>>> From: "Benoit Claise" <bclaise@cisco.com>
> > >>>>> To: <ops-area@ietf.org>
> > >>>>> Sent: Friday, February 14, 2014 12:39 AM
> > >>>>>> Dear all,
> > >>>>>>
> > >>>>>> We occasionally see read-write MIB module proposals within the
> > IETF.
> > >>>>>> However, the write capabilities of those MIB modules are rarely
> > >>>>> implemented.
> > >>>>>>
> > >>>>>> While discussing this issue with the MIB doctors, we arrive to
> > >>>>>> the conclusion that it's now time to set the direction for future
> > >>>>>> MIB developments within the IETF. Basically, let's not specify
> > >>>>>> read-write MIB modules unless we have a good reason.
> > >>>>>> Read-only MIB modules are still fine though, as SNMP is clearly
> > >>>>>> used for monitoring
> > >>>> purposes.
> > >>>>>>
> > >>>>>> Here is the statement we came up with:
> > >>>>>>
> > >>>>>>    The OPS area recommends the use of NETCONF/YANG standards
> > >> for
> > >>>>>>    configuration. IETF working groups are therefore encouraged to
> > use
> > >>>>>>    the NETCONF/YANG standards for configuration, specifically in
> new
> > >>>>>>    charters. SNMP MIB modules modifying persistent configuration
> > >>>>> state
> > >>>>>>    should only be produced by working groups in cases of clear
> > >>>>> utility
> > >>>>>>    and consensus to use SNMP write operations for configuration.
> > >>>>>>
> > >>>>>> Ideally, this should become an IESG statement.
> > >>>>>> Your feedback is most welcome.
> > >>>>>
> > >>>>> You probably know that there is currently a consensus call in
> > >>>>> progress over
> > >>>>>
> > >>>>> "Please indicate Support or Oppose for this MIB
> > >>>>> (draft-ietf-mpls-tp-te-mib) to be read-only."
> > >>>>>
> > >>>>> and I was pleasantly surprised to see opposition, albeit with one
> > >>>>> opponent later changing their mind (perhaps they were sat on from
> > >>>>> a height:-).  I don't see much sign of Netxxxx in the mpls arena
> > >>>>> but there is a need there for configuration, since there need not
> > >>>>> be a control
> > >>>> plane to set things up.
> > >>>>> Perhaps writable MIB modules will still be with us in the distant
> > >>>>> future in some corners of the Internet..
> > >>>>>
> > >>>>> Ideally, this idea would be fleshed out in an I-D.
> > >>>>>
> > >>>>> Tom Petch
> > >>>>>
> > >>>>>> Regards, the MIB doctors & Benoit
> > >>>>>
> > >>>>> _______________________________________________
> > >>>>> OPS-AREA mailing list
> > >>>>> OPS-AREA@ietf.org
> > >>>>> https://www.ietf.org/mailman/listinfo/ops-area
> > >>>>>
> > >>>>>
> > >>>>> -----
> > >>>>> No virus found in this message.
> > >>>>> Checked by AVG - www.avg.com
> > >>>>> Version: 2014.0.4259 / Virus Database: 3705/7092 - Release Date:
> > >>>>> 02/14/14
> > >>>>>
> > >>>>> _______________________________________________
> > >>>>> OPS-AREA mailing list
> > >>>>> OPS-AREA@ietf.org
> > >>>>> https://www.ietf.org/mailman/listinfo/ops-area
> > >>>>
> > >>>> _______________________________________________
> > >>>> 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
> > >
>
> _______________________________________________
> MIB-DOCTORS mailing list
> MIB-DOCTORS@ietf.org
> https://www.ietf.org/mailman/listinfo/mib-doctors
>

--001a11c2a9ca9e343104f2afbf8f
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 Tue, Feb 18, 2014 at 7:02 AM, Romascanu, Dan (Dan) <span dir=3D"=
ltr">&lt;<a href=3D"mailto:dromasca@avaya.com" target=3D"_blank">dromasca@a=
vaya.com</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">Tom,<br>
<br>
There is only one table. There is only one conceptual MIB. Objects in the t=
able happen to be defined in two MIB modules (you call them A and B) - but =
the operations with rows apply to all objects.<br>
<br>
If you wanted to define two separate tables you would have defined them sep=
arately using the same indexation, not use the AUGMENT construct.<br>
<br>
This is at least my understanding.<br>
<br></blockquote><div><br></div><div><br></div><div>OK -- you seem to be sa=
ying &quot;If the agent supports read-create compliance</div><div>for the A=
 columns, then it must support read-create for the new B columns&quot;.</di=
v>
<div>Yes -- there is only 1 conceptual row and 1 RowStatus. =A0But an agent=
 can</div><div>choose to implement the read-only compliance, so there is no=
 real</div><div>requirement to support read-create for the B columns. =A0Ma=
king them read-only</div>
<div>instead of read-create is not necessary.</div><div><br></div><div><br>=
</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-l=
eft:1px #ccc solid;padding-left:1ex">
Regards,<br>
<br>
Dan<br></blockquote><div><br></div><div>Andy</div><div>=A0</div><blockquote=
 class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc soli=
d;padding-left:1ex">
<br>
<br>
&gt; -----Original Message-----<br>
&gt; From: Thomas Nadeau [mailto:<a href=3D"mailto:tnadeau@lucidvision.com"=
>tnadeau@lucidvision.com</a>]<br>
&gt; Sent: Tuesday, February 18, 2014 4:12 PM<br>
&gt; To: Romascanu, Dan (Dan)<br>
&gt; Cc: Farrel Adrian; Cucchiara Joan; t.petch; Benoit Claise; <a href=3D"=
mailto:mib-doctors@ietf.org">mib-doctors@ietf.org</a><br>
&gt; Subject: Re: [MIB-DOCTORS] configuration: writable MIB modules versus<=
br>
&gt; NETCONF/YANGmodules<br>
&gt;<br>
&gt;<br>
&gt; =A0 =A0 =A0 I am not sure as you cannot create rows in the new MIB mod=
ule (call<br>
&gt; it B); they&#39;re created in the existing one (call it A) and as a si=
de-effect objects<br>
&gt; are created in B, which is normal agent behavior in an &quot;all writa=
ble&quot; situation<br>
&gt; today. =A0We should point out that this occurs in both cases of AUGMEN=
TSs and<br>
&gt; &quot;extends&quot; rows. =A0I do not see any issue with this as the b=
ehavior is as<br>
&gt; expected:<br>
&gt;<br>
&gt; =A0 =A0 =A0 So if I &quot;row create new row in A&quot; -&gt; the syst=
em creates an entry in A,<br>
&gt; and row is created in B that corresponds. When you query A or B, you g=
et<br>
&gt; responses. =A0Row destruction happens consistently too since you canno=
t issue<br>
&gt; row destruction instructions to B, but only to A, and corresponding en=
tries in<br>
&gt; B are removed. =A0Of course, if I try a row create on B it fails.<br>
&gt;<br>
&gt; =A0 =A0 =A0 The other way to look at this is that this is the same sit=
uation as if we<br>
&gt; had the ability to configure A as read-write/create and B as read-only=
 (where<br>
&gt; B contained read-write/create entries). =A0The exact same behavior sho=
uld<br>
&gt; result.<br>
&gt;<br>
&gt; =A0 =A0 =A0 --tom<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; On Feb 16, 2014:2:45 PM, at 2:45 PM, Romascanu, Dan (Dan)<br>
&gt; &lt;<a href=3D"mailto:dromasca@avaya.com">dromasca@avaya.com</a>&gt; w=
rote:<br>
&gt;<br>
&gt; &gt; By using the already existing RowStatus object in the base table =
the<br>
&gt; creation of new rows in the base table leads to the creation of new ro=
ws in<br>
&gt; the extended table. Even if the objects that you defined are all read-=
only,<br>
&gt; the effect is the same as defining a new table with a RowStatus object=
.<br>
&gt; &gt;<br>
&gt; &gt; Dan<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;&gt; -----Original Message-----<br>
&gt; &gt;&gt; From: Adrian Farrel [mailto:<a href=3D"mailto:adrian@olddog.c=
o.uk">adrian@olddog.co.uk</a>]<br>
&gt; &gt;&gt; Sent: Sunday, February 16, 2014 8:03 PM<br>
&gt; &gt;&gt; To: Romascanu, Dan (Dan); &#39;Joan Cucchiara&#39;; &#39;t.pe=
tch&#39;; &#39;Benoit<br>
&gt; &gt;&gt; Claise&#39;; mib- <a href=3D"mailto:doctors@ietf.org">doctors=
@ietf.org</a><br>
&gt; &gt;&gt; Subject: RE: [MIB-DOCTORS] configuration: writable MIB module=
s versus<br>
&gt; &gt;&gt; NETCONF/YANGmodules<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; I&#39;m sorry if I am being thick.<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; The row in the old table has a RowStatus object which is, of =
course,<br>
&gt; &gt;&gt; read- create.<br>
&gt; &gt;&gt; The extension table entry has no object with SYNTAX rowStatus=
, but is<br>
&gt; &gt;&gt; created automatically when the entry in the old table is crea=
ted.<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; A<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt;&gt; -----Original Message-----<br>
&gt; &gt;&gt;&gt; From: Romascanu, Dan (Dan) [mailto:<a href=3D"mailto:drom=
asca@avaya.com">dromasca@avaya.com</a>]<br>
&gt; &gt;&gt;&gt; Sent: 16 February 2014 11:55<br>
&gt; &gt;&gt;&gt; To: <a href=3D"mailto:adrian@olddog.co.uk">adrian@olddog.=
co.uk</a>; &#39;Joan Cucchiara&#39;; &#39;t.petch&#39;; &#39;Benoit<br>
&gt; &gt;&gt;&gt; Claise&#39;;<br>
&gt; &gt;&gt;&gt; mib- <a href=3D"mailto:doctors@ietf.org">doctors@ietf.org=
</a><br>
&gt; &gt;&gt;&gt; Subject: RE: [MIB-DOCTORS] configuration: writable MIB mo=
dules<br>
&gt; &gt;&gt;&gt; versus NETCONF/YANGmodules<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt; Hi Adrian,<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt; Even if the row you extend is composed only by objects wi=
th<br>
&gt; &gt;&gt;&gt; MAX-ACCESS<br>
&gt; &gt;&gt;&gt; read- only, creating a new row involves a write operation=
 on the<br>
&gt; &gt;&gt;&gt; object with SYNTAX RowStatus.<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt; This is (I guess) what Joan meant.<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt; Creating a new row may mean a modification of configurati=
on on the<br>
&gt; &gt;&gt;&gt; managed entity. You now have n+1 rows instead of n rows i=
n the table.<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt; Regards,<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt; Dan<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; -----Original Message-----<br>
&gt; &gt;&gt;&gt;&gt; From: MIB-DOCTORS [mailto:<a href=3D"mailto:mib-docto=
rs-bounces@ietf.org">mib-doctors-bounces@ietf.org</a>] On Behalf<br>
&gt; &gt;&gt; Of<br>
&gt; &gt;&gt;&gt;&gt; Adrian Farrel<br>
&gt; &gt;&gt;&gt;&gt; Sent: Friday, February 14, 2014 9:19 PM<br>
&gt; &gt;&gt;&gt;&gt; To: &#39;Joan Cucchiara&#39;; &#39;t.petch&#39;; &#39=
;Benoit Claise&#39;;<br>
&gt; &gt;&gt;&gt;&gt; <a href=3D"mailto:mib-doctors@ietf.org">mib-doctors@i=
etf.org</a><br>
&gt; &gt;&gt;&gt;&gt; Subject: Re: [MIB-DOCTORS] configuration: writable MI=
B modules<br>
&gt; &gt;&gt;&gt;&gt; versus NETCONF/YANGmodules<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; Hi Joan,<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; [Reverting to the MIB Doctor Thread]<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; I will bow to your far (far, far) superior understand=
ing of MIB-speak.<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; But I don&#39;t understand :-(<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; A row in a table that has RowStatus can have read-onl=
y objects and<br>
&gt; &gt;&gt;&gt;&gt; writeable objects with Defaults as well as read-creat=
e objects.<br>
&gt; &gt;&gt;&gt;&gt; When you use, for example, CreateAndGo the whole row =
gets created<br>
&gt; &gt;&gt;&gt;&gt; with read-create objects as they are Set, with unSet =
writeable<br>
&gt; &gt;&gt;&gt;&gt; objects<br>
&gt; &gt;&gt; defaulting,<br>
&gt; &gt;&gt;&gt;&gt; and with read-only objects filled with values from th=
e implementation.<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; When I extend a table, surely I can extend with objec=
ts that are<br>
&gt; &gt;&gt;&gt;&gt; all only<br>
&gt; &gt;&gt; read-<br>
&gt; &gt;&gt;&gt;&gt; only?<br>
&gt; &gt;&gt;&gt;&gt; Furthermore, the whole row in the extension table cou=
ld be<br>
&gt; &gt;&gt;&gt;&gt; automatically created when the row in the extended ta=
ble is created.<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; What am I missing?<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; Thanks,<br>
&gt; &gt;&gt;&gt;&gt; Adrian<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt; -----Original Message-----<br>
&gt; &gt;&gt;&gt;&gt;&gt; From: OPS-AREA [mailto:<a href=3D"mailto:ops-area=
-bounces@ietf.org">ops-area-bounces@ietf.org</a>] On Behalf Of<br>
&gt; &gt;&gt;&gt;&gt;&gt; Joan Cucchiara<br>
&gt; &gt;&gt;&gt;&gt;&gt; Sent: 14 February 2014 18:28<br>
&gt; &gt;&gt;&gt;&gt;&gt; To: &#39;t.petch&#39;; &#39;Benoit Claise&#39;; <=
a href=3D"mailto:ops-area@ietf.org">ops-area@ietf.org</a><br>
&gt; &gt;&gt;&gt;&gt;&gt; Subject: Re: [OPS-AREA] configuration: writable M=
IB modules versus<br>
&gt; &gt;&gt;&gt;&gt;&gt; NETCONF/YANGmodules<br>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt; Hi Tom,<br>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt; As the MIB Dr. on this draft, =A0I have responded=
 on the MIB Dr.<br>
&gt; &gt;&gt;&gt;&gt;&gt; thread that I do NOT see a way to make this draft=
<br>
&gt; &gt;&gt;&gt;&gt;&gt; (draft-ietf-mpls-tp-te-mib)<br>
&gt; &gt;&gt; read-<br>
&gt; &gt;&gt;&gt;&gt; only.<br>
&gt; &gt;&gt;&gt;&gt;&gt; This draft contains extension tables for tables i=
n LSR and TE MIBS<br>
&gt; &gt;&gt;&gt;&gt;&gt; which<br>
&gt; &gt;&gt; are<br>
&gt; &gt;&gt;&gt;&gt;&gt; created by RowStatus (which is read-create). =A0 =
Like it or not,<br>
&gt; RowStatus<br>
&gt; &gt;&gt; of<br>
&gt; &gt;&gt;&gt;&gt;&gt; those MIBs (i.e. LSR and TE MIBs) effect the rows=
 in the extension<br>
&gt; &gt;&gt;&gt;&gt;&gt; tables<br>
&gt; &gt;&gt; of<br>
&gt; &gt;&gt;&gt;&gt;&gt; this draft (think the case of row creation or row=
 deletion). =A0 That is an<br>
&gt; &gt;&gt;&gt;&gt;&gt; SNMP Set operation which effects the draft.<br>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt; I believe the statement that Benoit puts forth wo=
uld allow for<br>
&gt; &gt;&gt;&gt;&gt;&gt; such a situation as this draft, specifically:<br>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt; &quot;... SNMP MIB modules modifying persistent c=
onfiguration state<br>
&gt; &gt;&gt;&gt;&gt;&gt; should only be produced by working groups in case=
s of clear<br>
&gt; &gt;&gt;&gt;&gt;&gt; utility and consensus to use SNMP write operation=
s for<br>
&gt; configuration.&quot;<br>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt; Perhaps, additional wording, such as &quot;For ex=
ample, in the case of<br>
&gt; &gt;&gt;&gt;&gt;&gt; proposed SNMP MIB modules which extend or augment=
 rows that<br>
&gt; are<br>
&gt; &gt;&gt;&gt;&gt;&gt; created by configuration in a SNMP MIB module whi=
ch is already a<br>
&gt; &gt;&gt;&gt;&gt;&gt; RFC, the proposed SNNP MIB modules will be grandf=
athered, if the<br>
&gt; &gt;&gt;&gt;&gt;&gt; working group finds consensus to do so.&quot;<br>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt; However, I am okay with the statement as written.=
<br>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt; Thanks,<br>
&gt; &gt;&gt;&gt;&gt;&gt; =A0-Joan<br>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt; -----Original Message-----<br>
&gt; &gt;&gt;&gt;&gt;&gt; From: OPS-AREA [mailto:<a href=3D"mailto:ops-area=
-bounces@ietf.org">ops-area-bounces@ietf.org</a>] On Behalf Of<br>
&gt; &gt;&gt;&gt;&gt;&gt; t.petch<br>
&gt; &gt;&gt;&gt;&gt;&gt; Sent: Friday, February 14, 2014 10:02 AM<br>
&gt; &gt;&gt;&gt;&gt;&gt; To: Benoit Claise; <a href=3D"mailto:ops-area@iet=
f.org">ops-area@ietf.org</a><br>
&gt; &gt;&gt;&gt;&gt;&gt; Subject: Re: [OPS-AREA] configuration: writable M=
IB modules versus<br>
&gt; &gt;&gt;&gt;&gt;&gt; NETCONF/YANGmodules<br>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt; ----- Original Message -----<br>
&gt; &gt;&gt;&gt;&gt;&gt; From: &quot;Benoit Claise&quot; &lt;<a href=3D"ma=
ilto:bclaise@cisco.com">bclaise@cisco.com</a>&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt; To: &lt;<a href=3D"mailto:ops-area@ietf.org">ops-=
area@ietf.org</a>&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt; Sent: Friday, February 14, 2014 12:39 AM<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; Dear all,<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; We occasionally see read-write MIB module pro=
posals within the<br>
&gt; IETF.<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; However, the write capabilities of those MIB =
modules are rarely<br>
&gt; &gt;&gt;&gt;&gt;&gt; implemented.<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; While discussing this issue with the MIB doct=
ors, we arrive to<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; the conclusion that it&#39;s now time to set =
the direction for future<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; MIB developments within the IETF. Basically, =
let&#39;s not specify<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; read-write MIB modules unless we have a good =
reason.<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; Read-only MIB modules are still fine though, =
as SNMP is clearly<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; used for monitoring<br>
&gt; &gt;&gt;&gt;&gt; purposes.<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; Here is the statement we came up with:<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; =A0 =A0The OPS area recommends the use of NET=
CONF/YANG standards<br>
&gt; &gt;&gt; for<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; =A0 =A0configuration. IETF working groups are=
 therefore encouraged to<br>
&gt; use<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; =A0 =A0the NETCONF/YANG standards for configu=
ration, specifically in new<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; =A0 =A0charters. SNMP MIB modules modifying p=
ersistent configuration<br>
&gt; &gt;&gt;&gt;&gt;&gt; state<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; =A0 =A0should only be produced by working gro=
ups in cases of clear<br>
&gt; &gt;&gt;&gt;&gt;&gt; utility<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; =A0 =A0and consensus to use SNMP write operat=
ions for configuration.<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; Ideally, this should become an IESG statement=
.<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; Your feedback is most welcome.<br>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt; You probably know that there is currently a conse=
nsus call in<br>
&gt; &gt;&gt;&gt;&gt;&gt; progress over<br>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt; &quot;Please indicate Support or Oppose for this =
MIB<br>
&gt; &gt;&gt;&gt;&gt;&gt; (draft-ietf-mpls-tp-te-mib) to be read-only.&quot=
;<br>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt; and I was pleasantly surprised to see opposition,=
 albeit with one<br>
&gt; &gt;&gt;&gt;&gt;&gt; opponent later changing their mind (perhaps they =
were sat on from<br>
&gt; &gt;&gt;&gt;&gt;&gt; a height:-). =A0I don&#39;t see much sign of Netx=
xxx in the mpls arena<br>
&gt; &gt;&gt;&gt;&gt;&gt; but there is a need there for configuration, sinc=
e there need not<br>
&gt; &gt;&gt;&gt;&gt;&gt; be a control<br>
&gt; &gt;&gt;&gt;&gt; plane to set things up.<br>
&gt; &gt;&gt;&gt;&gt;&gt; Perhaps writable MIB modules will still be with u=
s in the distant<br>
&gt; &gt;&gt;&gt;&gt;&gt; future in some corners of the Internet..<br>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt; Ideally, this idea would be fleshed out in an I-D=
.<br>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt; Tom Petch<br>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; Regards, the MIB doctors &amp; Benoit<br>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt; _______________________________________________<b=
r>
&gt; &gt;&gt;&gt;&gt;&gt; OPS-AREA mailing list<br>
&gt; &gt;&gt;&gt;&gt;&gt; <a href=3D"mailto:OPS-AREA@ietf.org">OPS-AREA@iet=
f.org</a><br>
&gt; &gt;&gt;&gt;&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/=
ops-area" target=3D"_blank">https://www.ietf.org/mailman/listinfo/ops-area<=
/a><br>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt; -----<br>
&gt; &gt;&gt;&gt;&gt;&gt; No virus found in this message.<br>
&gt; &gt;&gt;&gt;&gt;&gt; Checked by AVG - <a href=3D"http://www.avg.com" t=
arget=3D"_blank">www.avg.com</a><br>
&gt; &gt;&gt;&gt;&gt;&gt; Version: 2014.0.4259 / Virus Database: 3705/7092 =
- Release Date:<br>
&gt; &gt;&gt;&gt;&gt;&gt; 02/14/14<br>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt; _______________________________________________<b=
r>
&gt; &gt;&gt;&gt;&gt;&gt; OPS-AREA mailing list<br>
&gt; &gt;&gt;&gt;&gt;&gt; <a href=3D"mailto:OPS-AREA@ietf.org">OPS-AREA@iet=
f.org</a><br>
&gt; &gt;&gt;&gt;&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/=
ops-area" target=3D"_blank">https://www.ietf.org/mailman/listinfo/ops-area<=
/a><br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; _______________________________________________<br>
&gt; &gt;&gt;&gt;&gt; MIB-DOCTORS mailing list<br>
&gt; &gt;&gt;&gt;&gt; <a href=3D"mailto:MIB-DOCTORS@ietf.org">MIB-DOCTORS@i=
etf.org</a><br>
&gt; &gt;&gt;&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/mib-=
doctors" target=3D"_blank">https://www.ietf.org/mailman/listinfo/mib-doctor=
s</a><br>
&gt; &gt;<br>
&gt; &gt; _______________________________________________<br>
&gt; &gt; MIB-DOCTORS mailing list<br>
&gt; &gt; <a href=3D"mailto:MIB-DOCTORS@ietf.org">MIB-DOCTORS@ietf.org</a><=
br>
&gt; &gt; <a href=3D"https://www.ietf.org/mailman/listinfo/mib-doctors" tar=
get=3D"_blank">https://www.ietf.org/mailman/listinfo/mib-doctors</a><br>
&gt; &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>
</blockquote></div><br></div></div>

--001a11c2a9ca9e343104f2afbf8f--


From nobody Tue Feb 18 07:31:59 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 66FB01A01E2 for <mib-doctors@ietfa.amsl.com>; Tue, 18 Feb 2014 07:31:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.547
X-Spam-Level: 
X-Spam-Status: No, score=-2.547 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, J_CHICKENPOX_15=0.6, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.548] 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 NgxWRV4Mzg6h for <mib-doctors@ietfa.amsl.com>; Tue, 18 Feb 2014 07:31:53 -0800 (PST)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by ietfa.amsl.com (Postfix) with ESMTP id D5D941A06C0 for <mib-doctors@ietf.org>; Tue, 18 Feb 2014 07:31:18 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ArUFAJp7A1OHCzIm/2dsb2JhbABZgkIjIThXuC2HI4EYFnSCJQEBAQEDAQEBDwgNBhwlCwwEAgEIDQQDAQEBAQoWAQYHJwsUCQgCBA4FCBqHYwEMnyWsUReOHTMgDQEDBgEGA4MbgRQEnxuLNIFvgT6BaEI
X-IronPort-AV: E=Sophos; i="4.97,502,1389762000"; d="scan'208,217"; a="49890655"
Received: from unknown (HELO p-us1-erheast-smtpauth.us1.avaya.com) ([135.11.50.38]) by co300216-co-outbound.net.avaya.com with ESMTP; 18 Feb 2014 10:31:13 -0500
Received: from unknown (HELO AZ-FFEXHC01.global.avaya.com) ([135.64.58.11]) by p-us1-erheast-out.us1.avaya.com with ESMTP/TLS/AES128-SHA; 18 Feb 2014 10:18:18 -0500
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC01.global.avaya.com ([135.64.58.11]) with mapi id 14.03.0174.001; Tue, 18 Feb 2014 16:31:12 +0100
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: Andy Bierman <andy@yumaworks.com>
Thread-Topic: [MIB-DOCTORS] configuration: writable MIB modules versus NETCONF/YANGmodules
Thread-Index: AQHPLLNe7mRsszR4rEC7y4sAuzOokJq7Goxw///z6wCAABSL0A==
Date: Tue, 18 Feb 2014 15:31:11 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA2E42201E@AZ-FFEXMB04.global.avaya.com>
References: <00b101cf29b9$95d979e0$c18c6da0$@olddog.co.uk> <9904FB1B0159DA42B0B887B7FA8119CA2E4187BC@AZ-FFEXMB04.global.avaya.com> <013501cf2b41$4d26a2c0$e773e840$@olddog.co.uk> <9904FB1B0159DA42B0B887B7FA8119CA2E41AF25@AZ-FFEXMB04.global.avaya.com> <E73A794D-26D6-47B4-89EC-2F49DBD51770@lucidvision.com> <9904FB1B0159DA42B0B887B7FA8119CA2E421F9E@AZ-FFEXMB04.global.avaya.com> <CABCOCHROPyAaRF6f5j3NjtduuBw7y_xmG0nBcy-nVVap9EgXww@mail.gmail.com>
In-Reply-To: <CABCOCHROPyAaRF6f5j3NjtduuBw7y_xmG0nBcy-nVVap9EgXww@mail.gmail.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_9904FB1B0159DA42B0B887B7FA8119CA2E42201EAZFFEXMB04globa_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/DyOcxei4Xn3MjMQSQNRdk3ZIERU
Cc: "t.petch" <ietfc@btconnect.com>, "mib-doctors@ietf.org" <mib-doctors@ietf.org>, Farrel Adrian <adrian@olddog.co.uk>
Subject: Re: [MIB-DOCTORS] configuration: writable MIB modules versus NETCONF/YANGmodules
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, 18 Feb 2014 15:31:58 -0000

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

Sure - the agent can chose to implement the read-only compliance. But this =
is different from full compliance.

Regards,

Dan


From: Andy Bierman [mailto:andy@yumaworks.com]
Sent: Tuesday, February 18, 2014 5:16 PM
To: Romascanu, Dan (Dan)
Cc: Thomas Nadeau; Farrel Adrian; t.petch; mib-doctors@ietf.org
Subject: Re: [MIB-DOCTORS] configuration: writable MIB modules versus NETCO=
NF/YANGmodules



On Tue, Feb 18, 2014 at 7:02 AM, Romascanu, Dan (Dan) <dromasca@avaya.com<m=
ailto:dromasca@avaya.com>> wrote:
Tom,

There is only one table. There is only one conceptual MIB. Objects in the t=
able happen to be defined in two MIB modules (you call them A and B) - but =
the operations with rows apply to all objects.

If you wanted to define two separate tables you would have defined them sep=
arately using the same indexation, not use the AUGMENT construct.

This is at least my understanding.


OK -- you seem to be saying "If the agent supports read-create compliance
for the A columns, then it must support read-create for the new B columns".
Yes -- there is only 1 conceptual row and 1 RowStatus.  But an agent can
choose to implement the read-only compliance, so there is no real
requirement to support read-create for the B columns.  Making them read-onl=
y
instead of read-create is not necessary.


Regards,

Dan

Andy



> -----Original Message-----
> From: Thomas Nadeau [mailto:tnadeau@lucidvision.com<mailto:tnadeau@lucidv=
ision.com>]
> Sent: Tuesday, February 18, 2014 4:12 PM
> To: Romascanu, Dan (Dan)
> Cc: Farrel Adrian; Cucchiara Joan; t.petch; Benoit Claise; mib-doctors@ie=
tf.org<mailto:mib-doctors@ietf.org>
> Subject: Re: [MIB-DOCTORS] configuration: writable MIB modules versus
> NETCONF/YANGmodules
>
>
>       I am not sure as you cannot create rows in the new MIB module (call
> it B); they're created in the existing one (call it A) and as a side-effe=
ct objects
> are created in B, which is normal agent behavior in an "all writable" sit=
uation
> today.  We should point out that this occurs in both cases of AUGMENTSs a=
nd
> "extends" rows.  I do not see any issue with this as the behavior is as
> expected:
>
>       So if I "row create new row in A" -> the system creates an entry in=
 A,
> and row is created in B that corresponds. When you query A or B, you get
> responses.  Row destruction happens consistently too since you cannot iss=
ue
> row destruction instructions to B, but only to A, and corresponding entri=
es in
> B are removed.  Of course, if I try a row create on B it fails.
>
>       The other way to look at this is that this is the same situation as=
 if we
> had the ability to configure A as read-write/create and B as read-only (w=
here
> B contained read-write/create entries).  The exact same behavior should
> result.
>
>       --tom
>
>
>
>
> On Feb 16, 2014:2:45 PM, at 2:45 PM, Romascanu, Dan (Dan)
> <dromasca@avaya.com<mailto:dromasca@avaya.com>> wrote:
>
> > By using the already existing RowStatus object in the base table the
> creation of new rows in the base table leads to the creation of new rows =
in
> the extended table. Even if the objects that you defined are all read-onl=
y,
> the effect is the same as defining a new table with a RowStatus object.
> >
> > Dan
> >
> >
> >> -----Original Message-----
> >> From: Adrian Farrel [mailto:adrian@olddog.co.uk<mailto:adrian@olddog.c=
o.uk>]
> >> Sent: Sunday, February 16, 2014 8:03 PM
> >> To: Romascanu, Dan (Dan); 'Joan Cucchiara'; 't.petch'; 'Benoit
> >> Claise'; mib- doctors@ietf.org<mailto:doctors@ietf.org>
> >> Subject: RE: [MIB-DOCTORS] configuration: writable MIB modules versus
> >> NETCONF/YANGmodules
> >>
> >> I'm sorry if I am being thick.
> >>
> >> The row in the old table has a RowStatus object which is, of course,
> >> read- create.
> >> The extension table entry has no object with SYNTAX rowStatus, but is
> >> created automatically when the entry in the old table is created.
> >>
> >> A
> >>
> >>> -----Original Message-----
> >>> From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com<mailto:dromasca=
@avaya.com>]
> >>> Sent: 16 February 2014 11:55
> >>> To: adrian@olddog.co.uk<mailto:adrian@olddog.co.uk>; 'Joan Cucchiara'=
; 't.petch'; 'Benoit
> >>> Claise';
> >>> mib- doctors@ietf.org<mailto:doctors@ietf.org>
> >>> Subject: RE: [MIB-DOCTORS] configuration: writable MIB modules
> >>> versus NETCONF/YANGmodules
> >>>
> >>> Hi Adrian,
> >>>
> >>> Even if the row you extend is composed only by objects with
> >>> MAX-ACCESS
> >>> read- only, creating a new row involves a write operation on the
> >>> object with SYNTAX RowStatus.
> >>>
> >>> This is (I guess) what Joan meant.
> >>>
> >>> Creating a new row may mean a modification of configuration on the
> >>> managed entity. You now have n+1 rows instead of n rows in the table.
> >>>
> >>> Regards,
> >>>
> >>> Dan
> >>>
> >>>
> >>>> -----Original Message-----
> >>>> From: MIB-DOCTORS [mailto:mib-doctors-bounces@ietf.org<mailto:mib-do=
ctors-bounces@ietf.org>] On Behalf
> >> Of
> >>>> Adrian Farrel
> >>>> Sent: Friday, February 14, 2014 9:19 PM
> >>>> To: 'Joan Cucchiara'; 't.petch'; 'Benoit Claise';
> >>>> mib-doctors@ietf.org<mailto:mib-doctors@ietf.org>
> >>>> Subject: Re: [MIB-DOCTORS] configuration: writable MIB modules
> >>>> versus NETCONF/YANGmodules
> >>>>
> >>>> Hi Joan,
> >>>>
> >>>> [Reverting to the MIB Doctor Thread]
> >>>>
> >>>> I will bow to your far (far, far) superior understanding of MIB-spea=
k.
> >>>>
> >>>> But I don't understand :-(
> >>>>
> >>>> A row in a table that has RowStatus can have read-only objects and
> >>>> writeable objects with Defaults as well as read-create objects.
> >>>> When you use, for example, CreateAndGo the whole row gets created
> >>>> with read-create objects as they are Set, with unSet writeable
> >>>> objects
> >> defaulting,
> >>>> and with read-only objects filled with values from the implementatio=
n.
> >>>>
> >>>> When I extend a table, surely I can extend with objects that are
> >>>> all only
> >> read-
> >>>> only?
> >>>> Furthermore, the whole row in the extension table could be
> >>>> automatically created when the row in the extended table is created.
> >>>>
> >>>> What am I missing?
> >>>>
> >>>> Thanks,
> >>>> Adrian
> >>>>
> >>>>> -----Original Message-----
> >>>>> From: OPS-AREA [mailto:ops-area-bounces@ietf.org<mailto:ops-area-bo=
unces@ietf.org>] On Behalf Of
> >>>>> Joan Cucchiara
> >>>>> Sent: 14 February 2014 18:28
> >>>>> To: 't.petch'; 'Benoit Claise'; ops-area@ietf.org<mailto:ops-area@i=
etf.org>
> >>>>> Subject: Re: [OPS-AREA] configuration: writable MIB modules versus
> >>>>> NETCONF/YANGmodules
> >>>>>
> >>>>> Hi Tom,
> >>>>>
> >>>>> As the MIB Dr. on this draft,  I have responded on the MIB Dr.
> >>>>> thread that I do NOT see a way to make this draft
> >>>>> (draft-ietf-mpls-tp-te-mib)
> >> read-
> >>>> only.
> >>>>> This draft contains extension tables for tables in LSR and TE MIBS
> >>>>> which
> >> are
> >>>>> created by RowStatus (which is read-create).   Like it or not,
> RowStatus
> >> of
> >>>>> those MIBs (i.e. LSR and TE MIBs) effect the rows in the extension
> >>>>> tables
> >> of
> >>>>> this draft (think the case of row creation or row deletion).   That=
 is an
> >>>>> SNMP Set operation which effects the draft.
> >>>>>
> >>>>> I believe the statement that Benoit puts forth would allow for
> >>>>> such a situation as this draft, specifically:
> >>>>>
> >>>>> "... SNMP MIB modules modifying persistent configuration state
> >>>>> should only be produced by working groups in cases of clear
> >>>>> utility and consensus to use SNMP write operations for
> configuration."
> >>>>>
> >>>>> Perhaps, additional wording, such as "For example, in the case of
> >>>>> proposed SNMP MIB modules which extend or augment rows that
> are
> >>>>> created by configuration in a SNMP MIB module which is already a
> >>>>> RFC, the proposed SNNP MIB modules will be grandfathered, if the
> >>>>> working group finds consensus to do so."
> >>>>>
> >>>>> However, I am okay with the statement as written.
> >>>>>
> >>>>> Thanks,
> >>>>>  -Joan
> >>>>>
> >>>>>
> >>>>> -----Original Message-----
> >>>>> From: OPS-AREA [mailto:ops-area-bounces@ietf.org<mailto:ops-area-bo=
unces@ietf.org>] On Behalf Of
> >>>>> t.petch
> >>>>> Sent: Friday, February 14, 2014 10:02 AM
> >>>>> To: Benoit Claise; ops-area@ietf.org<mailto:ops-area@ietf.org>
> >>>>> Subject: Re: [OPS-AREA] configuration: writable MIB modules versus
> >>>>> NETCONF/YANGmodules
> >>>>>
> >>>>> ----- Original Message -----
> >>>>> From: "Benoit Claise" <bclaise@cisco.com<mailto:bclaise@cisco.com>>
> >>>>> To: <ops-area@ietf.org<mailto:ops-area@ietf.org>>
> >>>>> Sent: Friday, February 14, 2014 12:39 AM
> >>>>>> Dear all,
> >>>>>>
> >>>>>> We occasionally see read-write MIB module proposals within the
> IETF.
> >>>>>> However, the write capabilities of those MIB modules are rarely
> >>>>> implemented.
> >>>>>>
> >>>>>> While discussing this issue with the MIB doctors, we arrive to
> >>>>>> the conclusion that it's now time to set the direction for future
> >>>>>> MIB developments within the IETF. Basically, let's not specify
> >>>>>> read-write MIB modules unless we have a good reason.
> >>>>>> Read-only MIB modules are still fine though, as SNMP is clearly
> >>>>>> used for monitoring
> >>>> purposes.
> >>>>>>
> >>>>>> Here is the statement we came up with:
> >>>>>>
> >>>>>>    The OPS area recommends the use of NETCONF/YANG standards
> >> for
> >>>>>>    configuration. IETF working groups are therefore encouraged to
> use
> >>>>>>    the NETCONF/YANG standards for configuration, specifically in n=
ew
> >>>>>>    charters. SNMP MIB modules modifying persistent configuration
> >>>>> state
> >>>>>>    should only be produced by working groups in cases of clear
> >>>>> utility
> >>>>>>    and consensus to use SNMP write operations for configuration.
> >>>>>>
> >>>>>> Ideally, this should become an IESG statement.
> >>>>>> Your feedback is most welcome.
> >>>>>
> >>>>> You probably know that there is currently a consensus call in
> >>>>> progress over
> >>>>>
> >>>>> "Please indicate Support or Oppose for this MIB
> >>>>> (draft-ietf-mpls-tp-te-mib) to be read-only."
> >>>>>
> >>>>> and I was pleasantly surprised to see opposition, albeit with one
> >>>>> opponent later changing their mind (perhaps they were sat on from
> >>>>> a height:-).  I don't see much sign of Netxxxx in the mpls arena
> >>>>> but there is a need there for configuration, since there need not
> >>>>> be a control
> >>>> plane to set things up.
> >>>>> Perhaps writable MIB modules will still be with us in the distant
> >>>>> future in some corners of the Internet..
> >>>>>
> >>>>> Ideally, this idea would be fleshed out in an I-D.
> >>>>>
> >>>>> Tom Petch
> >>>>>
> >>>>>> Regards, the MIB doctors & Benoit
> >>>>>
> >>>>> _______________________________________________
> >>>>> OPS-AREA mailing list
> >>>>> OPS-AREA@ietf.org<mailto:OPS-AREA@ietf.org>
> >>>>> https://www.ietf.org/mailman/listinfo/ops-area
> >>>>>
> >>>>>
> >>>>> -----
> >>>>> No virus found in this message.
> >>>>> Checked by AVG - www.avg.com<http://www.avg.com>
> >>>>> Version: 2014.0.4259 / Virus Database: 3705/7092 - Release Date:
> >>>>> 02/14/14
> >>>>>
> >>>>> _______________________________________________
> >>>>> OPS-AREA mailing list
> >>>>> OPS-AREA@ietf.org<mailto:OPS-AREA@ietf.org>
> >>>>> https://www.ietf.org/mailman/listinfo/ops-area
> >>>>
> >>>> _______________________________________________
> >>>> MIB-DOCTORS mailing list
> >>>> MIB-DOCTORS@ietf.org<mailto:MIB-DOCTORS@ietf.org>
> >>>> https://www.ietf.org/mailman/listinfo/mib-doctors
> >
> > _______________________________________________
> > MIB-DOCTORS mailing list
> > MIB-DOCTORS@ietf.org<mailto:MIB-DOCTORS@ietf.org>
> > https://www.ietf.org/mailman/listinfo/mib-doctors
> >

_______________________________________________
MIB-DOCTORS mailing list
MIB-DOCTORS@ietf.org<mailto:MIB-DOCTORS@ietf.org>
https://www.ietf.org/mailman/listinfo/mib-doctors


--_000_9904FB1B0159DA42B0B887B7FA8119CA2E42201EAZFFEXMB04globa_
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: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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
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;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.WordSection1
	{page:WordSection1;}
--></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 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">Sure &#8211; the agent ca=
n chose to implement the read-only compliance. But this is different from f=
ull compliance.
<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;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Andy Bie=
rman [mailto:andy@yumaworks.com]
<br>
<b>Sent:</b> Tuesday, February 18, 2014 5:16 PM<br>
<b>To:</b> Romascanu, Dan (Dan)<br>
<b>Cc:</b> Thomas Nadeau; Farrel Adrian; t.petch; mib-doctors@ietf.org<br>
<b>Subject:</b> Re: [MIB-DOCTORS] configuration: writable MIB modules versu=
s NETCONF/YANGmodules<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">On Tue, Feb 18, 2014 at 7:02 AM, Romascanu, Dan (Dan=
) &lt;<a href=3D"mailto:dromasca@avaya.com" target=3D"_blank">dromasca@avay=
a.com</a>&gt; wrote:<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">Tom,<br>
<br>
There is only one table. There is only one conceptual MIB. Objects in the t=
able happen to be defined in two MIB modules (you call them A and B) - but =
the operations with rows apply to all objects.<br>
<br>
If you wanted to define two separate tables you would have defined them sep=
arately using the same indexation, not use the AUGMENT construct.<br>
<br>
This is at least my understanding.<o:p></o:p></p>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">OK -- you seem to be saying &quot;If the agent suppo=
rts read-create compliance<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">for the A columns, then it must support read-create =
for the new B columns&quot;.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Yes -- there is only 1 conceptual row and 1 RowStatu=
s. &nbsp;But an agent can<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">choose to implement the read-only compliance, so the=
re is no real<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">requirement to support read-create for the B columns=
. &nbsp;Making them read-only<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">instead of read-create is not necessary.<o:p></o:p><=
/p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<blockquote style=3D"border:none;border-left:solid #CCCCCC 1.0pt;padding:0c=
m 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<p class=3D"MsoNormal">Regards,<br>
<br>
Dan<o:p></o:p></p>
</blockquote>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Andy<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
<blockquote style=3D"border:none;border-left:solid #CCCCCC 1.0pt;padding:0c=
m 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<p class=3D"MsoNormal"><br>
<br>
&gt; -----Original Message-----<br>
&gt; From: Thomas Nadeau [mailto:<a href=3D"mailto:tnadeau@lucidvision.com"=
>tnadeau@lucidvision.com</a>]<br>
&gt; Sent: Tuesday, February 18, 2014 4:12 PM<br>
&gt; To: Romascanu, Dan (Dan)<br>
&gt; Cc: Farrel Adrian; Cucchiara Joan; t.petch; Benoit Claise; <a href=3D"=
mailto:mib-doctors@ietf.org">
mib-doctors@ietf.org</a><br>
&gt; Subject: Re: [MIB-DOCTORS] configuration: writable MIB modules versus<=
br>
&gt; NETCONF/YANGmodules<br>
&gt;<br>
&gt;<br>
&gt; &nbsp; &nbsp; &nbsp; I am not sure as you cannot create rows in the ne=
w MIB module (call<br>
&gt; it B); they're created in the existing one (call it A) and as a side-e=
ffect objects<br>
&gt; are created in B, which is normal agent behavior in an &quot;all writa=
ble&quot; situation<br>
&gt; today. &nbsp;We should point out that this occurs in both cases of AUG=
MENTSs and<br>
&gt; &quot;extends&quot; rows. &nbsp;I do not see any issue with this as th=
e behavior is as<br>
&gt; expected:<br>
&gt;<br>
&gt; &nbsp; &nbsp; &nbsp; So if I &quot;row create new row in A&quot; -&gt;=
 the system creates an entry in A,<br>
&gt; and row is created in B that corresponds. When you query A or B, you g=
et<br>
&gt; responses. &nbsp;Row destruction happens consistently too since you ca=
nnot issue<br>
&gt; row destruction instructions to B, but only to A, and corresponding en=
tries in<br>
&gt; B are removed. &nbsp;Of course, if I try a row create on B it fails.<b=
r>
&gt;<br>
&gt; &nbsp; &nbsp; &nbsp; The other way to look at this is that this is the=
 same situation as if we<br>
&gt; had the ability to configure A as read-write/create and B as read-only=
 (where<br>
&gt; B contained read-write/create entries). &nbsp;The exact same behavior =
should<br>
&gt; result.<br>
&gt;<br>
&gt; &nbsp; &nbsp; &nbsp; --tom<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; On Feb 16, 2014:2:45 PM, at 2:45 PM, Romascanu, Dan (Dan)<br>
&gt; &lt;<a href=3D"mailto:dromasca@avaya.com">dromasca@avaya.com</a>&gt; w=
rote:<br>
&gt;<br>
&gt; &gt; By using the already existing RowStatus object in the base table =
the<br>
&gt; creation of new rows in the base table leads to the creation of new ro=
ws in<br>
&gt; the extended table. Even if the objects that you defined are all read-=
only,<br>
&gt; the effect is the same as defining a new table with a RowStatus object=
.<br>
&gt; &gt;<br>
&gt; &gt; Dan<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;&gt; -----Original Message-----<br>
&gt; &gt;&gt; From: Adrian Farrel [mailto:<a href=3D"mailto:adrian@olddog.c=
o.uk">adrian@olddog.co.uk</a>]<br>
&gt; &gt;&gt; Sent: Sunday, February 16, 2014 8:03 PM<br>
&gt; &gt;&gt; To: Romascanu, Dan (Dan); 'Joan Cucchiara'; 't.petch'; 'Benoi=
t<br>
&gt; &gt;&gt; Claise'; mib- <a href=3D"mailto:doctors@ietf.org">doctors@iet=
f.org</a><br>
&gt; &gt;&gt; Subject: RE: [MIB-DOCTORS] configuration: writable MIB module=
s versus<br>
&gt; &gt;&gt; NETCONF/YANGmodules<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; I'm sorry if I am being thick.<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; The row in the old table has a RowStatus object which is, of =
course,<br>
&gt; &gt;&gt; read- create.<br>
&gt; &gt;&gt; The extension table entry has no object with SYNTAX rowStatus=
, but is<br>
&gt; &gt;&gt; created automatically when the entry in the old table is crea=
ted.<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; A<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt;&gt; -----Original Message-----<br>
&gt; &gt;&gt;&gt; From: Romascanu, Dan (Dan) [mailto:<a href=3D"mailto:drom=
asca@avaya.com">dromasca@avaya.com</a>]<br>
&gt; &gt;&gt;&gt; Sent: 16 February 2014 11:55<br>
&gt; &gt;&gt;&gt; To: <a href=3D"mailto:adrian@olddog.co.uk">adrian@olddog.=
co.uk</a>; 'Joan Cucchiara'; 't.petch'; 'Benoit<br>
&gt; &gt;&gt;&gt; Claise';<br>
&gt; &gt;&gt;&gt; mib- <a href=3D"mailto:doctors@ietf.org">doctors@ietf.org=
</a><br>
&gt; &gt;&gt;&gt; Subject: RE: [MIB-DOCTORS] configuration: writable MIB mo=
dules<br>
&gt; &gt;&gt;&gt; versus NETCONF/YANGmodules<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt; Hi Adrian,<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt; Even if the row you extend is composed only by objects wi=
th<br>
&gt; &gt;&gt;&gt; MAX-ACCESS<br>
&gt; &gt;&gt;&gt; read- only, creating a new row involves a write operation=
 on the<br>
&gt; &gt;&gt;&gt; object with SYNTAX RowStatus.<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt; This is (I guess) what Joan meant.<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt; Creating a new row may mean a modification of configurati=
on on the<br>
&gt; &gt;&gt;&gt; managed entity. You now have n&#43;1 rows instead of n ro=
ws in the table.<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt; Regards,<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt; Dan<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; -----Original Message-----<br>
&gt; &gt;&gt;&gt;&gt; From: MIB-DOCTORS [mailto:<a href=3D"mailto:mib-docto=
rs-bounces@ietf.org">mib-doctors-bounces@ietf.org</a>] On Behalf<br>
&gt; &gt;&gt; Of<br>
&gt; &gt;&gt;&gt;&gt; Adrian Farrel<br>
&gt; &gt;&gt;&gt;&gt; Sent: Friday, February 14, 2014 9:19 PM<br>
&gt; &gt;&gt;&gt;&gt; To: 'Joan Cucchiara'; 't.petch'; 'Benoit Claise';<br>
&gt; &gt;&gt;&gt;&gt; <a href=3D"mailto:mib-doctors@ietf.org">mib-doctors@i=
etf.org</a><br>
&gt; &gt;&gt;&gt;&gt; Subject: Re: [MIB-DOCTORS] configuration: writable MI=
B modules<br>
&gt; &gt;&gt;&gt;&gt; versus NETCONF/YANGmodules<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; Hi Joan,<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; [Reverting to the MIB Doctor Thread]<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; I will bow to your far (far, far) superior understand=
ing of MIB-speak.<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; But I don't understand :-(<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; A row in a table that has RowStatus can have read-onl=
y objects and<br>
&gt; &gt;&gt;&gt;&gt; writeable objects with Defaults as well as read-creat=
e objects.<br>
&gt; &gt;&gt;&gt;&gt; When you use, for example, CreateAndGo the whole row =
gets created<br>
&gt; &gt;&gt;&gt;&gt; with read-create objects as they are Set, with unSet =
writeable<br>
&gt; &gt;&gt;&gt;&gt; objects<br>
&gt; &gt;&gt; defaulting,<br>
&gt; &gt;&gt;&gt;&gt; and with read-only objects filled with values from th=
e implementation.<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; When I extend a table, surely I can extend with objec=
ts that are<br>
&gt; &gt;&gt;&gt;&gt; all only<br>
&gt; &gt;&gt; read-<br>
&gt; &gt;&gt;&gt;&gt; only?<br>
&gt; &gt;&gt;&gt;&gt; Furthermore, the whole row in the extension table cou=
ld be<br>
&gt; &gt;&gt;&gt;&gt; automatically created when the row in the extended ta=
ble is created.<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; What am I missing?<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; Thanks,<br>
&gt; &gt;&gt;&gt;&gt; Adrian<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt; -----Original Message-----<br>
&gt; &gt;&gt;&gt;&gt;&gt; From: OPS-AREA [mailto:<a href=3D"mailto:ops-area=
-bounces@ietf.org">ops-area-bounces@ietf.org</a>] On Behalf Of<br>
&gt; &gt;&gt;&gt;&gt;&gt; Joan Cucchiara<br>
&gt; &gt;&gt;&gt;&gt;&gt; Sent: 14 February 2014 18:28<br>
&gt; &gt;&gt;&gt;&gt;&gt; To: 't.petch'; 'Benoit Claise'; <a href=3D"mailto=
:ops-area@ietf.org">ops-area@ietf.org</a><br>
&gt; &gt;&gt;&gt;&gt;&gt; Subject: Re: [OPS-AREA] configuration: writable M=
IB modules versus<br>
&gt; &gt;&gt;&gt;&gt;&gt; NETCONF/YANGmodules<br>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt; Hi Tom,<br>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt; As the MIB Dr. on this draft, &nbsp;I have respon=
ded on the MIB Dr.<br>
&gt; &gt;&gt;&gt;&gt;&gt; thread that I do NOT see a way to make this draft=
<br>
&gt; &gt;&gt;&gt;&gt;&gt; (draft-ietf-mpls-tp-te-mib)<br>
&gt; &gt;&gt; read-<br>
&gt; &gt;&gt;&gt;&gt; only.<br>
&gt; &gt;&gt;&gt;&gt;&gt; This draft contains extension tables for tables i=
n LSR and TE MIBS<br>
&gt; &gt;&gt;&gt;&gt;&gt; which<br>
&gt; &gt;&gt; are<br>
&gt; &gt;&gt;&gt;&gt;&gt; created by RowStatus (which is read-create). &nbs=
p; Like it or not,<br>
&gt; RowStatus<br>
&gt; &gt;&gt; of<br>
&gt; &gt;&gt;&gt;&gt;&gt; those MIBs (i.e. LSR and TE MIBs) effect the rows=
 in the extension<br>
&gt; &gt;&gt;&gt;&gt;&gt; tables<br>
&gt; &gt;&gt; of<br>
&gt; &gt;&gt;&gt;&gt;&gt; this draft (think the case of row creation or row=
 deletion). &nbsp; That is an<br>
&gt; &gt;&gt;&gt;&gt;&gt; SNMP Set operation which effects the draft.<br>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt; I believe the statement that Benoit puts forth wo=
uld allow for<br>
&gt; &gt;&gt;&gt;&gt;&gt; such a situation as this draft, specifically:<br>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt; &quot;... SNMP MIB modules modifying persistent c=
onfiguration state<br>
&gt; &gt;&gt;&gt;&gt;&gt; should only be produced by working groups in case=
s of clear<br>
&gt; &gt;&gt;&gt;&gt;&gt; utility and consensus to use SNMP write operation=
s for<br>
&gt; configuration.&quot;<br>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt; Perhaps, additional wording, such as &quot;For ex=
ample, in the case of<br>
&gt; &gt;&gt;&gt;&gt;&gt; proposed SNMP MIB modules which extend or augment=
 rows that<br>
&gt; are<br>
&gt; &gt;&gt;&gt;&gt;&gt; created by configuration in a SNMP MIB module whi=
ch is already a<br>
&gt; &gt;&gt;&gt;&gt;&gt; RFC, the proposed SNNP MIB modules will be grandf=
athered, if the<br>
&gt; &gt;&gt;&gt;&gt;&gt; working group finds consensus to do so.&quot;<br>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt; However, I am okay with the statement as written.=
<br>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt; Thanks,<br>
&gt; &gt;&gt;&gt;&gt;&gt; &nbsp;-Joan<br>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt; -----Original Message-----<br>
&gt; &gt;&gt;&gt;&gt;&gt; From: OPS-AREA [mailto:<a href=3D"mailto:ops-area=
-bounces@ietf.org">ops-area-bounces@ietf.org</a>] On Behalf Of<br>
&gt; &gt;&gt;&gt;&gt;&gt; t.petch<br>
&gt; &gt;&gt;&gt;&gt;&gt; Sent: Friday, February 14, 2014 10:02 AM<br>
&gt; &gt;&gt;&gt;&gt;&gt; To: Benoit Claise; <a href=3D"mailto:ops-area@iet=
f.org">ops-area@ietf.org</a><br>
&gt; &gt;&gt;&gt;&gt;&gt; Subject: Re: [OPS-AREA] configuration: writable M=
IB modules versus<br>
&gt; &gt;&gt;&gt;&gt;&gt; NETCONF/YANGmodules<br>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt; ----- Original Message -----<br>
&gt; &gt;&gt;&gt;&gt;&gt; From: &quot;Benoit Claise&quot; &lt;<a href=3D"ma=
ilto:bclaise@cisco.com">bclaise@cisco.com</a>&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt; To: &lt;<a href=3D"mailto:ops-area@ietf.org">ops-=
area@ietf.org</a>&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt; Sent: Friday, February 14, 2014 12:39 AM<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; Dear all,<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; We occasionally see read-write MIB module pro=
posals within the<br>
&gt; IETF.<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; However, the write capabilities of those MIB =
modules are rarely<br>
&gt; &gt;&gt;&gt;&gt;&gt; implemented.<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; While discussing this issue with the MIB doct=
ors, we arrive to<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; the conclusion that it's now time to set the =
direction for future<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; MIB developments within the IETF. Basically, =
let's not specify<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; read-write MIB modules unless we have a good =
reason.<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; Read-only MIB modules are still fine though, =
as SNMP is clearly<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; used for monitoring<br>
&gt; &gt;&gt;&gt;&gt; purposes.<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; Here is the statement we came up with:<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; &nbsp; &nbsp;The OPS area recommends the use =
of NETCONF/YANG standards<br>
&gt; &gt;&gt; for<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; &nbsp; &nbsp;configuration. IETF working grou=
ps are therefore encouraged to<br>
&gt; use<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; &nbsp; &nbsp;the NETCONF/YANG standards for c=
onfiguration, specifically in new<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; &nbsp; &nbsp;charters. SNMP MIB modules modif=
ying persistent configuration<br>
&gt; &gt;&gt;&gt;&gt;&gt; state<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; &nbsp; &nbsp;should only be produced by worki=
ng groups in cases of clear<br>
&gt; &gt;&gt;&gt;&gt;&gt; utility<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; &nbsp; &nbsp;and consensus to use SNMP write =
operations for configuration.<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; Ideally, this should become an IESG statement=
.<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; Your feedback is most welcome.<br>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt; You probably know that there is currently a conse=
nsus call in<br>
&gt; &gt;&gt;&gt;&gt;&gt; progress over<br>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt; &quot;Please indicate Support or Oppose for this =
MIB<br>
&gt; &gt;&gt;&gt;&gt;&gt; (draft-ietf-mpls-tp-te-mib) to be read-only.&quot=
;<br>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt; and I was pleasantly surprised to see opposition,=
 albeit with one<br>
&gt; &gt;&gt;&gt;&gt;&gt; opponent later changing their mind (perhaps they =
were sat on from<br>
&gt; &gt;&gt;&gt;&gt;&gt; a height:-). &nbsp;I don't see much sign of Netxx=
xx in the mpls arena<br>
&gt; &gt;&gt;&gt;&gt;&gt; but there is a need there for configuration, sinc=
e there need not<br>
&gt; &gt;&gt;&gt;&gt;&gt; be a control<br>
&gt; &gt;&gt;&gt;&gt; plane to set things up.<br>
&gt; &gt;&gt;&gt;&gt;&gt; Perhaps writable MIB modules will still be with u=
s in the distant<br>
&gt; &gt;&gt;&gt;&gt;&gt; future in some corners of the Internet..<br>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt; Ideally, this idea would be fleshed out in an I-D=
.<br>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt; Tom Petch<br>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; Regards, the MIB doctors &amp; Benoit<br>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt; _______________________________________________<b=
r>
&gt; &gt;&gt;&gt;&gt;&gt; OPS-AREA mailing list<br>
&gt; &gt;&gt;&gt;&gt;&gt; <a href=3D"mailto:OPS-AREA@ietf.org">OPS-AREA@iet=
f.org</a><br>
&gt; &gt;&gt;&gt;&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/=
ops-area" target=3D"_blank">
https://www.ietf.org/mailman/listinfo/ops-area</a><br>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt; -----<br>
&gt; &gt;&gt;&gt;&gt;&gt; No virus found in this message.<br>
&gt; &gt;&gt;&gt;&gt;&gt; Checked by AVG - <a href=3D"http://www.avg.com" t=
arget=3D"_blank">www.avg.com</a><br>
&gt; &gt;&gt;&gt;&gt;&gt; Version: 2014.0.4259 / Virus Database: 3705/7092 =
- Release Date:<br>
&gt; &gt;&gt;&gt;&gt;&gt; 02/14/14<br>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt; _______________________________________________<b=
r>
&gt; &gt;&gt;&gt;&gt;&gt; OPS-AREA mailing list<br>
&gt; &gt;&gt;&gt;&gt;&gt; <a href=3D"mailto:OPS-AREA@ietf.org">OPS-AREA@iet=
f.org</a><br>
&gt; &gt;&gt;&gt;&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/=
ops-area" target=3D"_blank">
https://www.ietf.org/mailman/listinfo/ops-area</a><br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; _______________________________________________<br>
&gt; &gt;&gt;&gt;&gt; MIB-DOCTORS mailing list<br>
&gt; &gt;&gt;&gt;&gt; <a href=3D"mailto:MIB-DOCTORS@ietf.org">MIB-DOCTORS@i=
etf.org</a><br>
&gt; &gt;&gt;&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/mib-=
doctors" target=3D"_blank">
https://www.ietf.org/mailman/listinfo/mib-doctors</a><br>
&gt; &gt;<br>
&gt; &gt; _______________________________________________<br>
&gt; &gt; MIB-DOCTORS mailing list<br>
&gt; &gt; <a href=3D"mailto:MIB-DOCTORS@ietf.org">MIB-DOCTORS@ietf.org</a><=
br>
&gt; &gt; <a href=3D"https://www.ietf.org/mailman/listinfo/mib-doctors" tar=
get=3D"_blank">https://www.ietf.org/mailman/listinfo/mib-doctors</a><br>
&gt; &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><o:p></o:p></p>
</blockquote>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</div>
</div>
</body>
</html>

--_000_9904FB1B0159DA42B0B887B7FA8119CA2E42201EAZFFEXMB04globa_--


From nobody Mon Feb 24 08:54:12 2014
Return-Path: <lsmt@ietf.org>
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 4483B1A01BA; Mon, 24 Feb 2014 08:48:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 5eDdTlVK0wQr; Mon, 24 Feb 2014 08:48:21 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id C42511A01A7; Mon, 24 Feb 2014 08:48:21 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Liaison Statement Management Tool <lsmt@ietf.org>
To: The IETF Chair <chair@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 5.0.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140224164821.30151.64061.idtracker@ietfa.amsl.com>
Date: Mon, 24 Feb 2014 08:48:21 -0800
Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/JE6b8C8HN_htytJ5ChIvrA7H6U4
X-Mailman-Approved-At: Mon, 24 Feb 2014 08:54:10 -0800
Cc: Bill Bjorkman <bill@metroethernetforum.net>, mib-doctors@ietf.org, nan@metroethernetforum.org, joelja@bogus.com, The IESG <iesg@ietf.org>, Raghu Ranganathan <rraghu@ciena.com>
Subject: [MIB-DOCTORS] New Liaison Statement, "Virtual NID (vNID) Functionality for E-Access Services MIB"
X-BeenThere: mib-doctors@ietf.org
X-Mailman-Version: 2.1.15
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, 24 Feb 2014 16:48:23 -0000

Title: Virtual NID (vNID) Functionality for E-Access Services MIB
Submission Date: 2014-02-24
URL of the IETF Web page: http://datatracker.ietf.org/liaison/1307/

From: MEF (Mike Bencheck <mike.bencheck@verizon.com>)
To: The IETF (The IETF Chair <chair@ietf.org>)
Cc: The IESG <iesg@ietf.org>,Nan Chen <nan@metroethernetforum.org>,Bill Bjorkman <bill@metroethernetforum.net>,Raghu Ranganathan <rraghu@ciena.com>,joelja@bogus.com,bclaise@cisco.com,mib-doctors@ietf.org
Response Contact: nan@metroethernetforum.org
Technical Contact: 
Purpose: For information

Body: 
Attachments:

    Virtual NID (vNID) Functionality for E-Access Services MIB
    https://datatracker.ietf.org/documents/LIAISON/liaison-2014-02-24-mef-the-ietf-virtual-nid-vnid-functionality-for-e-access-services-mib-attachment-1.pdf


From nobody Mon Feb 24 13:35:03 2014
Return-Path: <jhaas@slice.pfrc.org>
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 E924F1A01E5 for <mib-doctors@ietfa.amsl.com>; Mon, 24 Feb 2014 13:35:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.216
X-Spam-Level: 
X-Spam-Status: No, score=-0.216 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, IP_NOT_FRIENDLY=0.334, RP_MATCHES_RCVD=-0.547, 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 ei4LNOf7Cy4f for <mib-doctors@ietfa.amsl.com>; Mon, 24 Feb 2014 13:35:00 -0800 (PST)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id 1A7151A0165 for <mib-doctors@ietf.org>; Mon, 24 Feb 2014 13:35:00 -0800 (PST)
Received: by slice.pfrc.org (Postfix, from userid 1001) id 633B9C391; Mon, 24 Feb 2014 16:34:59 -0500 (EST)
Date: Mon, 24 Feb 2014 16:34:59 -0500
From: Jeffrey Haas <jhaas@pfrc.org>
To: "Bert Wijnen (IETF)" <bertietf@bwijnen.net>
Message-ID: <20140224213459.GB24908@pfrc>
References: <066d01cf0416$bccb85c0$36629140$@olddog.co.uk> <52D57335.40205@cisco.com> <52D576E1.9060600@bwijnen.net> <CECE764681BE964CBE1DFF78F3CDD3941DF24367@xmb-aln-x01.cisco.com> <52E754A4.3080702@bwijnen.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <52E754A4.3080702@bwijnen.net>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/bBZxBdlXoc8LTELal0u2X4sKdRE
Cc: "mib-doctors@ietf.org" <mib-doctors@ietf.org>, "ops-ads@tools.ietf.org" <ops-ads@tools.ietf.org>, "Nobo Akiya \(nobo\)" <nobo@cisco.com>, "bfd-chairs@tools.ietf.org" <bfd-chairs@tools.ietf.org>, "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "Zafar Ali \(zali\)" <zali@cisco.com>
Subject: Re: [MIB-DOCTORS] Heads up MIB documents in the pipe
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, 24 Feb 2014 21:35:02 -0000

[continuing the top-post]
Bert,

I spoke to Tom who is the current token holder to get in the necessary IANA
MIB split in the TC document.  Tom is currently having issues finding the
time to do the edits as a result of his recent change of employment.  He
will attempt to get it done soon, but it's possible that Nobo will need to
pick this up after he returns from his travels.

Since I am the document shepherd, it's probably inappropriate for me to make
the required changes.

-- Jeff

On Tue, Jan 28, 2014 at 07:56:36AM +0100, Bert Wijnen (IETF) wrote:
> my appologies,
> 
> I did not get to it last week, and this week I am in an all week
> ISOC Board meeting. Will try to work on it next week.
> 
> Bert
> 
> On 14/01/14 19:42, Nobo Akiya (nobo) wrote:
> >Hi,
> >
> >Thank you Bert. There were number of comments provided from Adrian. It'll be beneficial to address those before MIB doctor pass through. Tom/Zafar, can you notify Bert when pending comments have been addressed?
> >
> >Thanks,
> >Nobo
> >
> >>-----Original Message-----
> >>From: Bert Wijnen (IETF) [mailto:bertietf@bwijnen.net]
> >>Sent: Tuesday, January 14, 2014 12:42 PM
> >>To: Benoit Claise (bclaise); adrian@olddog.co.uk; ops-ads@tools.ietf.org;
> >>mib-doctors@ietf.org
> >>Cc: bfd-chairs@tools.ietf.org
> >>Subject: Re: [MIB-DOCTORS] Heads up MIB documents in the pipe
> >>
> >>I can do these in the next week or so.
> >>
> >>Bert
> >>
> >>On 14/01/14 18:26, Benoit Claise wrote:
> >>>Dear MIB doctors,
> >>>
> >>>Who would like to volunteer?
> >>>A simple comparison between the MIB doctors list
> >>>(http://www.ietf.org/iesg/directorate/mib-doctors.html) and the latest
> >>>assignments
> >>>(http://trac.tools.ietf.org/area/ops/trac/wiki/mib-doctors-review-history)
> >>would guide me in kindly requesting the next volunteers.
> >>>However, it's always better if you volunteer yourself :-)
> >>>
> >>>Regards, Benoit
> >>>
> >>>>Hi,
> >>>>
> >>>>Heads up that two documents are in the pipe.
> >>>>
> >>>>https://datatracker.ietf.org/doc/draft-ietf-bfd-tc-mib/
> >>>>https://datatracker.ietf.org/doc/draft-ietf-bfd-mib/
> >>>>
> >>>>I shall be reviewing them as AD in the next couple of days and then
> >>>>expect to issue IETF last call.
> >>>>
> >>>>Thanks for the work.
> >>>>
> >>>>Adrian
> >>>>
> >>>>_______________________________________________
> >>>>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
> >>>
> >


From nobody Mon Feb 24 13:38:54 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 80E821A025F for <mib-doctors@ietfa.amsl.com>; Mon, 24 Feb 2014 13:38:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.447
X-Spam-Level: 
X-Spam-Status: No, score=-2.447 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.547] 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 CTSEcqWMryL4 for <mib-doctors@ietfa.amsl.com>; Mon, 24 Feb 2014 13:38:51 -0800 (PST)
Received: from lucidvision.com (lucidvision.com [72.71.250.34]) by ietfa.amsl.com (Postfix) with ESMTP id 633581A0193 for <mib-doctors@ietf.org>; Mon, 24 Feb 2014 13:38:51 -0800 (PST)
Received: from [192.168.1.122] (static-72-71-250-38.cncdnh.fast04.myfairpoint.net [72.71.250.38]) by lucidvision.com (Postfix) with ESMTP id 9FA342704A68; Mon, 24 Feb 2014 16:38:50 -0500 (EST)
Content-Type: multipart/signed; boundary="Apple-Mail=_9BC2268C-2515-4A00-841D-46D6EB0C721D"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Thomas Nadeau <tnadeau@lucidvision.com>
In-Reply-To: <20140224213459.GB24908@pfrc>
Date: Mon, 24 Feb 2014 16:38:47 -0500
Message-Id: <81885B13-B643-40D4-B9A8-FF2169230610@lucidvision.com>
References: <066d01cf0416$bccb85c0$36629140$@olddog.co.uk> <52D57335.40205@cisco.com> <52D576E1.9060600@bwijnen.net> <CECE764681BE964CBE1DFF78F3CDD3941DF24367@xmb-aln-x01.cisco.com> <52E754A4.3080702@bwijnen.net> <20140224213459.GB24908@pfrc>
To: Jeffrey Haas <jhaas@pfrc.org>
X-Mailer: Apple Mail (2.1827)
Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/oAWfJXtSyWqLj6-MCCnNBsCDvX8
Cc: "mib-doctors@ietf.org" <mib-doctors@ietf.org>, "ops-ads@tools.ietf.org" <ops-ads@tools.ietf.org>, "Nobo Akiya \(nobo\)" <nobo@cisco.com>, "bfd-chairs@tools.ietf.org" <bfd-chairs@tools.ietf.org>, Farrel Adrian <adrian@olddog.co.uk>, "Zafar Ali \(zali\)" <zali@cisco.com>
Subject: Re: [MIB-DOCTORS] Heads up MIB documents in the pipe
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, 24 Feb 2014 21:38:53 -0000

--Apple-Mail=_9BC2268C-2515-4A00-841D-46D6EB0C721D
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


	For the record, I am about %50 through Adrian's edits. Some of =
them require changes needed for configuration to work correctly and are =
taking some time, but I will withhold a rant against doing configurable =
MIBs for now. *)

	--Tom

On Feb 24, 2014:4:34 PM, at 4:34 PM, Jeffrey Haas <jhaas@pfrc.org> =
wrote:

> [continuing the top-post]
> Bert,
>=20
> I spoke to Tom who is the current token holder to get in the necessary =
IANA
> MIB split in the TC document.  Tom is currently having issues finding =
the
> time to do the edits as a result of his recent change of employment.  =
He
> will attempt to get it done soon, but it's possible that Nobo will =
need to
> pick this up after he returns from his travels.
>=20
> Since I am the document shepherd, it's probably inappropriate for me =
to make
> the required changes.
>=20
> -- Jeff
>=20
> On Tue, Jan 28, 2014 at 07:56:36AM +0100, Bert Wijnen (IETF) wrote:
>> my appologies,
>>=20
>> I did not get to it last week, and this week I am in an all week
>> ISOC Board meeting. Will try to work on it next week.
>>=20
>> Bert
>>=20
>> On 14/01/14 19:42, Nobo Akiya (nobo) wrote:
>>> Hi,
>>>=20
>>> Thank you Bert. There were number of comments provided from Adrian. =
It'll be beneficial to address those before MIB doctor pass through. =
Tom/Zafar, can you notify Bert when pending comments have been =
addressed?
>>>=20
>>> Thanks,
>>> Nobo
>>>=20
>>>> -----Original Message-----
>>>> From: Bert Wijnen (IETF) [mailto:bertietf@bwijnen.net]
>>>> Sent: Tuesday, January 14, 2014 12:42 PM
>>>> To: Benoit Claise (bclaise); adrian@olddog.co.uk; =
ops-ads@tools.ietf.org;
>>>> mib-doctors@ietf.org
>>>> Cc: bfd-chairs@tools.ietf.org
>>>> Subject: Re: [MIB-DOCTORS] Heads up MIB documents in the pipe
>>>>=20
>>>> I can do these in the next week or so.
>>>>=20
>>>> Bert
>>>>=20
>>>> On 14/01/14 18:26, Benoit Claise wrote:
>>>>> Dear MIB doctors,
>>>>>=20
>>>>> Who would like to volunteer?
>>>>> A simple comparison between the MIB doctors list
>>>>> (http://www.ietf.org/iesg/directorate/mib-doctors.html) and the =
latest
>>>>> assignments
>>>>> =
(http://trac.tools.ietf.org/area/ops/trac/wiki/mib-doctors-review-history)=

>>>> would guide me in kindly requesting the next volunteers.
>>>>> However, it's always better if you volunteer yourself :-)
>>>>>=20
>>>>> Regards, Benoit
>>>>>=20
>>>>>> Hi,
>>>>>>=20
>>>>>> Heads up that two documents are in the pipe.
>>>>>>=20
>>>>>> https://datatracker.ietf.org/doc/draft-ietf-bfd-tc-mib/
>>>>>> https://datatracker.ietf.org/doc/draft-ietf-bfd-mib/
>>>>>>=20
>>>>>> I shall be reviewing them as AD in the next couple of days and =
then
>>>>>> expect to issue IETF last call.
>>>>>>=20
>>>>>> Thanks for the work.
>>>>>>=20
>>>>>> Adrian
>>>>>>=20
>>>>>> _______________________________________________
>>>>>> MIB-DOCTORS mailing list
>>>>>> MIB-DOCTORS@ietf.org
>>>>>> https://www.ietf.org/mailman/listinfo/mib-doctors
>>>>>>=20
>>>>>=20
>>>>> _______________________________________________
>>>>> MIB-DOCTORS mailing list
>>>>> MIB-DOCTORS@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/mib-doctors
>>>>>=20
>>>=20
>=20


--Apple-Mail=_9BC2268C-2515-4A00-841D-46D6EB0C721D
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

iQIcBAEBCgAGBQJTC7vnAAoJEPcO+I7eiUJZpv4P/3ECoW49BCSTPFrsj84wEZIJ
h2fDYA4gO0xDBiIvlmgqSG/6TgPQGNpKCzuW9OuSAXkDHooXl2BVSUDkWufeMWIh
qBP0hvmN7EWql/zdW5rdFleD7ciGICPcxPxRltX+TIkRXvZc2gm0F80P9qAk6uzI
0K3o3H7F11FSnP6Kmweh9vUNnNaGQeYrpfK3wfKru8Y1oiCZ9Zua/uCj7h0znxL6
uD8WpE5KEZZ70oq5nucTZQK2CBOx55qyyODvMoTxk9gZjzS6e7Q7TpSXiRDWCLWV
lISxgicFv0ot8B8LgvlZod3LtKfyHtaW7BKtMSBesCvj9pDwljMW/WhdugngYsFy
zvp24ru8ER/56AU6knCLzma9+GVKw4AfvJYn/0rNzuLrctZ/x8Le6DxD+g+so65/
TxvJmm//F/bc3vR2VXRN8tyv5IrfNbgAnDZsRD3jISsRNuC6y7ay5C3qmXMr9RoN
QPXkOT1Eyxm5zUcuEhjTZG7oJdfFPqWpDXkHbBaAZaUxMozFJ8QTrJQ/rTk+kxRR
wCt7bmISmQyi4rBcUcaFBxOwmk43RJ6j/t8I4QgwCtkfQGfiO2Aozhj/wV5ij66c
CWlHv2p0n7AjwGG35bvqiPVnC1x9xwdpQ4OFTyHfm37ScgtVZCzhkGFT4hP0Ctym
OKjh3nbt6Fjx2GPzerCC
=MDSd
-----END PGP SIGNATURE-----

--Apple-Mail=_9BC2268C-2515-4A00-841D-46D6EB0C721D--


From nobody Wed Feb 26 14:41:02 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 05B0A1A00BA for <mib-doctors@ietfa.amsl.com>; Wed, 26 Feb 2014 14:40:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.254
X-Spam-Level: 
X-Spam-Status: No, score=0.254 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.547] 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 58X4jlO5_R6g for <mib-doctors@ietfa.amsl.com>; Wed, 26 Feb 2014 14:40:44 -0800 (PST)
Received: from lucidvision.com (lucidvision.com [72.71.250.34]) by ietfa.amsl.com (Postfix) with ESMTP id 39AF01A014C for <mib-doctors@ietf.org>; Wed, 26 Feb 2014 14:40:44 -0800 (PST)
Received: from [192.168.1.122] (static-72-71-250-38.cncdnh.fast04.myfairpoint.net [72.71.250.38]) by lucidvision.com (Postfix) with ESMTP id 03EEC270950B; Wed, 26 Feb 2014 17:40:41 -0500 (EST)
Content-Type: multipart/signed; boundary="Apple-Mail=_18DB3BD0-2DF3-4807-BC14-8A1073DEAEE6"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Thomas Nadeau <tnadeau@lucidvision.com>
In-Reply-To: <CABCOCHQJsBy8DvPEOy-b1Xs-MWzfgZCwWtWjrpngHLeicMAefA@mail.gmail.com>
Date: Wed, 26 Feb 2014 17:40:38 -0500
Message-Id: <A41519E1-DE8A-4B0C-B421-45B5D42BA2C7@lucidvision.com>
References: <05c501cf21ad$80d97ef0$828c7cd0$@olddog.co.uk> <7D263081-6D84-4AA2-B0CB-FA74793BD135@comcast.net> <CABCOCHT3UCVmpLcEAH2Q3mrfbWMxh=c7FZ4d61pAmpwb8t-sug@mail.gmail.com> <00d601cf25b3$371c77e0$a55567a0$@olddog.co.uk> <CABCOCHQJsBy8DvPEOy-b1Xs-MWzfgZCwWtWjrpngHLeicMAefA@mail.gmail.com>
To: Andy Bierman <andy@yumaworks.com>
X-Mailer: Apple Mail (2.1827)
Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/7ODwp9Zg1NrXYd8dk0T4BCgR-AI
Cc: Farrel Adrian <adrian@olddog.co.uk>, "MIB Doctors \(E-mail\)" <mib-doctors@ietf.org>
Subject: Re: [MIB-DOCTORS] Read-only MIB modules
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: Wed, 26 Feb 2014 22:40:52 -0000

--Apple-Mail=_18DB3BD0-2DF3-4807-BC14-8A1073DEAEE6
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_51DC14BE-6015-44C5-B50A-8BA947A38148"


--Apple-Mail=_51DC14BE-6015-44C5-B50A-8BA947A38148
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1


On Feb 9, 2014:12:23 PM, at 12:23 PM, Andy Bierman <andy@yumaworks.com> =
wrote:

>=20
>=20
>=20
> On Sun, Feb 9, 2014 at 8:23 AM, Adrian Farrel <adrian@olddog.co.uk> =
wrote:
> Andy,
>=20
> =20
>=20
> I am all in favour of flailing in sandboxes as a way to burn off that =
excess energy caused by high-tartrazine diets.
>=20
> =20
>=20
> However, I think SNMP Set is showing up because people are putting =
together MIB modules sans clue. They genuinely want to be helpful in the =
construction of MIB modules that might have value, but they don't know =
how to do it and no-one else in their immediate circle does either.
>=20
> =20
>=20
> The consequence, beyond a spec that might or might not get implemented =
in full, is that the MIB doctors have to do reviews of function they =
don't believe has value.
>=20
>=20
>=20
>=20
>=20
> The IESG and IETF have to reviews these documents as well.
> I think people writing MIB modules know how to do it, but they are
> following a formula setup by the IESG and blessed by MIB Doctors.
>=20
> MIB authors seem encouraged to use read-create objects, but then
> add MIN-ACCESS read-only in the conformance statement,
> just in case anybody ever wants to implement the MAX-ACCESS.
>=20
> Time to face the fact that nobody is implementing the MAX-ACCESS.
> In order to claim conformance to a MIB module, it should be
> without this MIB-ACCESS loophole.  WG groups can then decide
> if they have enough participants who plan on implementing read-create.
> If not, then they can't have it.  The MIB gets rejected and sent back
> to the WG if it contains any MIN-ACCESS clauses.

	And hence my point about wasting time of those resources writing =
those min-access statements (and conformance clauses). That stuff is =
non-trivial, nor is getting row construction ordering/etc... details =
right.  And then its all for nothing because as you rightly said, nearly =
no one is using it.=20

	--Tom


>=20
>=20
> Andy
>=20
>=20
>=20
>=20
>=20
> A
>=20
> =20
>=20
> =20
>=20
> From: Andy Bierman [mailto:andy@yumaworks.com]=20
> Sent: 09 February 2014 06:25
> To: David Harrington
> Cc: Adrian Farrel; MIB Doctors (E-mail)
> Subject: Re: [MIB-DOCTORS] Read-only MIB modules
>=20
> =20
>=20
> Hi,
>=20
> =20
>=20
> I do not really know if an official statement to avoid SNMP Set is =
needed.
>=20
> IMO the verdict is in wrt/ SNMP for configuration.
>=20
> =20
>=20
> It has been a long-held tradition in the IETF to let people flail in =
their own
>=20
> sandbox if that's what they really wanted to do.  Maybe that has been =
a
>=20
> mistake. Maybe WGs should be forced to prove that they have enough
>=20
> real stakeholders willing to implement a spec, so that every part of
>=20
> every proposed standard gets sponsored.
>=20
> =20
>=20
> We often presume that "some vendors", who have had no interest in the
>=20
> work all along, will eventually come around and decide to implement.
>=20
> Therefore there is no need to have strong interest in deployment =
during
>=20
> the WG process.
>=20
> =20
>=20
> Commitment to implementation should apply to everything -- protocols,
>=20
> MIB modules, YANG modules --- it doesn't matter. No stakeholders,
>=20
> no sandbox.  That would be a radical change ;-)
>=20
> =20
>=20
> =20
>=20
> Andy
>=20
> =20
>=20
> =20
>=20
> On Sat, Feb 8, 2014 at 8:28 PM, David Harrington <ietfdbh@comcast.net> =
wrote:
>=20
> Hi,
>=20
> =20
>=20
> I object to this statement. (Should I say "strongly" object, to show I =
mean business?
>=20
> =20
>=20
> There are many RW objects that can "adjust" a network configuration =
assuming SET is supported by the agent involved.
>=20
> The NMS I used to work on, which helped determine and correct root =
cause for fault and performance problems, adjusted networks using =
writable MIB modules often.
>=20
> To tell WGs they should not develop RW MIB modules I think is wrong.
>=20
> =20
>=20
> I also have a concern with recommending Netconf/YANG at this point in =
time.
>=20
> If we looked up the top ten router vendors using something like =
Gartner reports, how many of them really support configuration using =
Netconf with YANG in shipping products?
>=20
> Ditto, the top ten switch vendors?
>=20
> How many of them can be fully configured using YANG modules (not =
homegrown alternatives, but modules - standard or proprietary - written =
using the standards-compliant YANG language)?
>=20
> I don't know the answer to that question, but would like to see some =
proof that YANG is at least as widely supported in currently shipping =
products as RW MIB objects.
>=20
> I think Netconf/YANG should compete in an open market with RW MIB =
modules, not try to stack the deck in their favor by "strongly =
discouraging" RW MIB standards.
>=20
> =20
>=20
> I have had discussions with vendors who are leaders in their =
particular networking niche, and they have told me they would not =
consider Netconf/YANG, because it has not been around long enough and =
been widely-enough deployed to prove stable for their production =
networks (whereas SNMP has enough track record to be known to be =
stable).
>=20
> So I'm a bit concerned about telling WGs they should develop YANG =
modules rather than MIB modules.
>=20
> And the current discussions of whether YANG 1.1 or 2.0 is needed to =
fix some problems with YANG 1.0, and it may not be backwards compatible, =
make me question the stability of YANG.
>=20
> =20
>=20
> Don't get me wrong. I support Netconf/YANG going forward, but I think =
it is important to provide advice that non-MIB-Doctors/non-YANG-experts =
can interpret reasonably.
>=20
> Any such statement should make a clear distinction between =
"configuration" - the complete configuration of a device by Netconf - =
versus RW objects in a MIB - which can be used by SNMP to adjust network =
parameters/configuration.
>=20
> Telling people not to develop RW MIBs is throwing the baby out with =
the bathwater.
>=20
> We should NOT recommend against RW MIBs, because these can be used for =
more than (full device) configuration.
>=20
> That point is far from clear in the currently proposed statement.
>=20
> Maybe the statement should be that, if a vendor wants to replace their =
CLI, they should replace it with Netconf/YANG, and not with =
SNMP/RW-MIBs.=20
>=20
> That's probably a closer approximation  of Netconf/YANG's =
applicability versus RW MIBs.=20
>=20
> =20
>=20
> In the past we have allowed implementations to make the conformance =
choice between supporting a MIB as RW, or implementing read-only.
>=20
> If we advise WGs to not develop module with RW objects, then we take =
the choice away from the vendors.
>=20
> I thick that would be a mistake.
>=20
> =20
>=20
> In  addition, it is pointed out later in this thread that other SDOs =
use RW MIBs.=20
>=20
> Well, those MIBs produced by other SDOs (and for that matter, vendors) =
might require some support for specific RW objects in IETF MIB modules.
>=20
> Therefore, I think it would be providing bad advice to say that IETF =
WGs should not produce MIB  modules with RW objects in them.
>=20
> =20
>=20
> If Netconf/YANG becomes widely deployed, then NMS implementations and =
operators can choose whether to use YANG or SNMP (or their CLI) to =
adjust network configurations.
>=20
> THat should not be a decision we make in the IETF, effectively forcing =
WGs to not develop MIBs with writable objects.
>=20
> =20
>=20
> Providing RW objects in MIB modules lets implementers and operators =
make the appropriate choice for their environments. (See RFC 3365 for =
similar thinking vis-a-vis security.)
>=20
> =20
>=20
> dbh
>=20
> =20
>=20
> On Feb 4, 2014, at 8:32 AM, Adrian Farrel <adrian@olddog.co.uk> wrote:
>=20
>=20
>=20
>=20
> Hi,
>=20
> =20
>=20
> The MPLS working group is testing the water to see whether one of its =
MIB modules should be "reduced" to read-only. This is the document that =
triggered my recent questions that led on to the draft advice you are =
working on. The WG took the document back to make this decision.
>=20
> =20
>=20
> You'll note below that we immediately have an implementation claim =
(not for this doc, but for the modules it extends).
>=20
> =20
>=20
> An interesting situation, I think.
>=20
> =20
>=20
> A
>=20
> =20
>=20
> From: mpls [mailto:mpls-bounces@ietf.org] On Behalf Of GyeRok Gwun =
(???)
> Sent: 04 February 2014 09:57
> To: 'mpls@ietf.org'
> Cc: 'mpls-chairs@tools.ietf.org'; =
'draft-ietf-mpls-tp-te-mib@tools.ietf.org'
> Subject: Re: [mpls] seeking consensus on making =
draft-ietf-mpls-tp-te-mib read- only
>=20
> =20
>=20
> No/oppose to make as Read-only mib.
>=20
> In our products we extensively use R/W object of TE mib. We also have =
NMS/EMS that use TE read-write Objects
>=20
> =20
>=20
> Best Regards
>=20
> Gwun
>=20
> =20
>=20
> -----Original Message-----
>=20
> From: mpls [mailto:mpls-bounces@ietf.org] On Behalf Of Loa Andersson
>=20
> Sent: Monday, February 03, 2014 10:55 PM
>=20
> To: mpls@ietf.org
>=20
> Cc: mpls-chairs@tools.ietf.org; =
draft-ietf-mpls-tp-te-mib@tools.ietf.org
>=20
> Subject: [mpls] seeking consensus on making draft-ietf-mpls-tp-te-mib =
read- only
>=20
> =20
>=20
> Working Group,
>=20
> =20
>=20
> We have just recalled draft-ietf-mpls-tp-te-mib from the IESG to the =
working group for more work. We have a series of comments that are =
mostly for clarification. However the main reason for recalling the =
document is that there is one point where we need to confirm working =
group consensus.
>=20
> =20
>=20
> The IETF, the working group and the MIB Doctors are today very =
reluctant to produce read-write MIB modules. The current draft is =
read-write for a few objects, this is based on a consensus call for an =
earlier discussion, however the consensus call was not clear. It can be =
taken to mean both that we want to go with read-write objects and that =
we want to see read-only. Is it clear that it has been interpreted =
differently by different individuals.
>=20
> =20
>=20
> The authors and chairs have discussed the issue and we have a rough =
consensus that we want the MIB module(s) to be read-only.
>=20
> =20
>=20
> We therefore are asking the working group if this is OK for the MIB
>=20
> module(s) in the current document. Please indicate Support or Oppose =
for this MIB (draft-ietf-mpls-tp-te-mib) to be read-only.
>=20
> =20
>=20
> Please send your comments to the working group mailing list before =
February 18, 2014.
>=20
> =20
>=20
> Loa
>=20
> for the MPLS wg chairs
>=20
> --
>=20
> =20
>=20
> =20
>=20
> Loa Andersson                        email: loa@mail01.huawei.com
>=20
> Senior MPLS Expert                          loa@pi.nu
>=20
> Huawei Technologies (consultant)     phone: +46 739 81 21 64
>=20
> _______________________________________________
>=20
> mpls mailing list
>=20
> mpls@ietf.org
>=20
> https://www.ietf.org/mailman/listinfo/mpls
>=20
> _______________________________________________
>=20
> mpls mailing list
>=20
> mpls@ietf.org
>=20
> https://www.ietf.org/mailman/listinfo/mpls
>=20
> =20
>=20
> _______________________________________________
> MIB-DOCTORS mailing list
> MIB-DOCTORS@ietf.org
> https://www.ietf.org/mailman/listinfo/mib-doctors
>=20
> =20
>=20
>=20
> _______________________________________________
> MIB-DOCTORS mailing list
> MIB-DOCTORS@ietf.org
> https://www.ietf.org/mailman/listinfo/mib-doctors
>=20
> =20
>=20
>=20
> _______________________________________________
> MIB-DOCTORS mailing list
> MIB-DOCTORS@ietf.org
> https://www.ietf.org/mailman/listinfo/mib-doctors


--Apple-Mail=_51DC14BE-6015-44C5-B50A-8BA947A38148
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=iso-8859-1

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Diso-8859-1"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space;"><br><div><div>On Feb 9, 2014:12:23 PM, at 12:23 PM, =
Andy Bierman &lt;<a =
href=3D"mailto:andy@yumaworks.com">andy@yumaworks.com</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div=
 class=3D"gmail_quote">On Sun, Feb 9, 2014 at 8:23 AM, Adrian Farrel =
<span dir=3D"ltr">&lt;<a href=3D"mailto:adrian@olddog.co.uk" =
target=3D"_blank">adrian@olddog.co.uk</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex"><div lang=3D"EN-GB" =
link=3D"blue" vlink=3D"purple"><p class=3D"MsoNormal"><span =
style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif=
&quot;;color:#1f497d">Andy,<u></u><u></u></span></p><p =
class=3D"MsoNormal"><span =
style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif=
&quot;;color:#1f497d"><u></u>&nbsp;<u></u></span></p><p =
class=3D"MsoNormal"><span =
style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif=
&quot;;color:#1f497d">I am all in favour of flailing in sandboxes as a =
way to burn off that excess energy caused by high-tartrazine =
diets.<u></u><u></u></span></p><p class=3D"MsoNormal"><span =
style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif=
&quot;;color:#1f497d"><u></u>&nbsp;<u></u></span></p><p =
class=3D"MsoNormal"><span =
style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif=
&quot;;color:#1f497d">However, I think SNMP Set is showing up because =
people are putting together MIB modules sans clue. They genuinely want =
to be helpful in the construction of MIB modules that might have value, =
but they don't know how to do it and no-one else in their immediate =
circle does either.<u></u><u></u></span></p><p class=3D"MsoNormal"><span =
style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif=
&quot;;color:#1f497d"><u></u>&nbsp;<u></u></span></p><p =
class=3D"MsoNormal"><span =
style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif=
&quot;;color:#1f497d">The consequence, beyond a spec that might or might =
not get implemented in full, is that the MIB doctors have to do reviews =
of function they don't believe has value.<u></u><u></u></span></p><p =
class=3D"MsoNormal"><br></p></div></blockquote><div><br></div><div><br></d=
iv><div>The IESG and IETF have to reviews these documents as =
well.</div><div>I think people writing MIB modules know how to do it, =
but they are</div>
<div>following a formula setup by the IESG and blessed by MIB =
Doctors.</div><div><br></div><div>MIB authors seem encouraged to use =
read-create objects, but then</div><div>add MIN-ACCESS read-only in the =
conformance statement,</div>
<div>just in case anybody ever wants to implement the =
MAX-ACCESS.</div><div><br></div><div>Time to face the fact that nobody =
is implementing the MAX-ACCESS.</div><div>In order to claim conformance =
to a MIB module, it should be</div>
<div>without this MIB-ACCESS loophole. &nbsp;WG groups can then =
decide</div><div>if they have enough participants who plan on =
implementing read-create.</div><div>If not, then they can't have it. =
&nbsp;The MIB gets rejected and sent back</div>
<div>to the WG if it contains any MIN-ACCESS =
clauses.</div></div></div></div></blockquote><div><br></div><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span>And hence =
my point about wasting time of those resources writing those min-access =
statements (and conformance clauses). That stuff is non-trivial, nor is =
getting row construction ordering/etc... details right. &nbsp;And then =
its all for nothing because as you rightly said, nearly no one is using =
it.&nbsp;</div><div><br></div><div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	=
</span>--Tom</div><div><br></div><div><br><blockquote type=3D"cite"><div =
dir=3D"ltr"><div class=3D"gmail_extra"><div =
class=3D"gmail_quote"><div><br></div><div><br></div><div>Andy</div><div><b=
r></div><div><br></div><div><br></div><div><br></div><blockquote =
class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc =
solid;padding-left:1ex">
<div lang=3D"EN-GB" link=3D"blue" vlink=3D"purple"><div><br =
class=3D"webkit-block-placeholder"></div><p class=3D"MsoNormal"><span =
style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif=
&quot;;color:#1f497d">A<u></u><u></u></span></p><p class=3D"MsoNormal">
<span =
style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif=
&quot;;color:#1f497d"><u></u>&nbsp;<u></u></span></p><p =
class=3D"MsoNormal"><span =
style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif=
&quot;;color:#1f497d"><u></u>&nbsp;<u></u></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 =
lang=3D"EN-US" =
style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&=
quot;">From:</span></b><span lang=3D"EN-US" =
style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&=
quot;"> Andy Bierman [mailto:<a href=3D"mailto:andy@yumaworks.com" =
target=3D"_blank">andy@yumaworks.com</a>] <br>
<b>Sent:</b> 09 February 2014 06:25<br><b>To:</b> David =
Harrington<br><b>Cc:</b> Adrian Farrel; MIB Doctors =
(E-mail)<br><b>Subject:</b> Re: [MIB-DOCTORS] Read-only MIB =
modules<u></u><u></u></span></p></div></div><p class=3D"MsoNormal">
<u></u>&nbsp;<u></u></p><div><p =
class=3D"MsoNormal">Hi,<u></u><u></u></p><div><p =
class=3D"MsoNormal"><u></u>&nbsp;<u></u></p></div><div><p =
class=3D"MsoNormal">I do not really know if an official statement to =
avoid SNMP Set is needed.<u></u><u></u></p>
</div><div><p class=3D"MsoNormal">IMO the verdict is in wrt/ SNMP for =
configuration.<u></u><u></u></p></div><div><p =
class=3D"MsoNormal"><u></u>&nbsp;<u></u></p></div><div><p =
class=3D"MsoNormal">It has been a long-held tradition in the IETF to let =
people flail in their own<u></u><u></u></p>
</div><div><p class=3D"MsoNormal">sandbox if that's what they really =
wanted to do. &nbsp;Maybe that has been a<u></u><u></u></p></div><div><p =
class=3D"MsoNormal">mistake. Maybe WGs should be forced to prove that =
they have enough<u></u><u></u></p>
</div><div><p class=3D"MsoNormal">real stakeholders willing to implement =
a spec, so that every part of<u></u><u></u></p></div><div><p =
class=3D"MsoNormal">every proposed standard gets =
sponsored.<u></u><u></u></p></div><div><p class=3D"MsoNormal">
<u></u>&nbsp;<u></u></p></div><div><p class=3D"MsoNormal">We often =
presume that "some vendors", who have had no interest in =
the<u></u><u></u></p></div><div><p class=3D"MsoNormal">work all along, =
will eventually come around and decide to implement.<u></u><u></u></p>
</div><div><p class=3D"MsoNormal">Therefore there is no need to have =
strong interest in deployment during<u></u><u></u></p></div><div><p =
class=3D"MsoNormal">the WG process.<u></u><u></u></p></div><div><p =
class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
</div><div><p class=3D"MsoNormal">Commitment to implementation should =
apply to everything -- protocols,<u></u><u></u></p></div><div><p =
class=3D"MsoNormal">MIB modules, YANG modules --- it doesn't matter. No =
stakeholders,<u></u><u></u></p>
</div><div><p class=3D"MsoNormal">no sandbox. &nbsp;That would be a =
radical change ;-)<u></u><u></u></p></div><div><p =
class=3D"MsoNormal"><u></u>&nbsp;<u></u></p></div><div><p =
class=3D"MsoNormal"><u></u>&nbsp;<u></u></p></div><div><p =
class=3D"MsoNormal">
Andy<u></u><u></u></p></div><div><p =
class=3D"MsoNormal"><u></u>&nbsp;<u></u></p></div></div><div><p =
class=3D"MsoNormal" =
style=3D"margin-bottom:12.0pt"><u></u>&nbsp;<u></u></p><div><p =
class=3D"MsoNormal">On Sat, Feb 8, 2014 at 8:28 PM, David Harrington =
&lt;<a href=3D"mailto:ietfdbh@comcast.net" =
target=3D"_blank">ietfdbh@comcast.net</a>&gt; wrote:<u></u><u></u></p>
<div><p class=3D"MsoNormal">Hi,<u></u><u></u></p><div><p =
class=3D"MsoNormal"><u></u>&nbsp;<u></u></p></div><div><p =
class=3D"MsoNormal">I object to this statement. (Should I say "strongly" =
object, to show I mean business?<u></u><u></u></p>
</div><div><p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p></div><div><p =
class=3D"MsoNormal">There are many RW objects that can "adjust" a =
network configuration assuming SET is supported by the agent =
involved.<u></u><u></u></p>
</div><div><p class=3D"MsoNormal">The NMS I used to work on, which =
helped determine and correct root cause for fault and performance =
problems, adjusted networks using writable MIB modules =
often.<u></u><u></u></p></div><div><p class=3D"MsoNormal">To tell WGs =
they should not develop RW MIB modules I think is =
wrong.<u></u><u></u></p></div><div><p =
class=3D"MsoNormal"><u></u>&nbsp;<u></u></p></div><div><p =
class=3D"MsoNormal">I also have a concern with recommending Netconf/YANG =
at this point in time.<u></u><u></u></p>
</div><div><p class=3D"MsoNormal">If we looked up the top ten router =
vendors using something like Gartner reports, how many of them really =
support configuration using Netconf with YANG in shipping =
products?<u></u><u></u></p>
</div><div><p class=3D"MsoNormal">Ditto, the top ten switch =
vendors?<u></u><u></u></p></div><div><p class=3D"MsoNormal">How many of =
them can be fully configured using YANG modules (not homegrown =
alternatives, but modules - standard or proprietary - written using the =
standards-compliant YANG language)?<u></u><u></u></p>
</div><div><p class=3D"MsoNormal">I don't know the answer to that =
question, but would like to see some proof that YANG is at least as =
widely supported in currently shipping products as RW MIB =
objects.<u></u><u></u></p></div>
<div><p class=3D"MsoNormal">I think Netconf/YANG should compete in an =
open market with RW MIB modules, not try to stack the deck in their =
favor by "strongly discouraging" RW MIB =
standards.<u></u><u></u></p></div><div><p =
class=3D"MsoNormal"><u></u>&nbsp;<u></u></p></div><div><p =
class=3D"MsoNormal">I have had discussions with vendors who are leaders =
in their particular networking niche, and they have told me they would =
not consider Netconf/YANG, because it has not been around long enough =
and been widely-enough deployed to prove stable for their production =
networks (whereas SNMP has enough track record to be known to be =
stable).<u></u><u></u></p>
</div><div><p class=3D"MsoNormal">So I'm a bit concerned about telling =
WGs they should develop YANG modules rather than MIB =
modules.<u></u><u></u></p></div><div><p class=3D"MsoNormal">And the =
current discussions of whether YANG 1.1 or 2.0 is needed to fix some =
problems with YANG 1.0, and it may not be backwards compatible, make me =
question the stability of YANG.<u></u><u></u></p>
</div><div><p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p></div><div><p =
class=3D"MsoNormal">Don't get me wrong. I support Netconf/YANG going =
forward, but I think it is important to provide advice that =
non-MIB-Doctors/non-YANG-experts can interpret =
reasonably.<u></u><u></u></p>
</div><div><p class=3D"MsoNormal">Any such statement should make a clear =
distinction between "configuration" - the complete configuration of a =
device by Netconf - versus RW objects in a MIB - which can be used by =
SNMP to adjust network parameters/configuration.<u></u><u></u></p>
</div><div><p class=3D"MsoNormal">Telling people not to develop RW MIBs =
is throwing the baby out with the =
bathwater.<u></u><u></u></p></div><div><p class=3D"MsoNormal">We should =
NOT recommend against RW MIBs, because these can be used for more than =
(full device) configuration.<u></u><u></u></p>
</div><div><p class=3D"MsoNormal">That point is far from clear in the =
currently proposed statement.<u></u><u></u></p></div><div><p =
class=3D"MsoNormal">Maybe the statement should be that, if a vendor =
wants to replace their CLI, they should replace it with Netconf/YANG, =
and not with SNMP/RW-MIBs.&nbsp;<u></u><u></u></p>
</div><div><p class=3D"MsoNormal">That's probably a closer approximation =
&nbsp;of Netconf/YANG's applicability versus RW =
MIBs.&nbsp;<u></u><u></u></p></div><div><p =
class=3D"MsoNormal"><u></u>&nbsp;<u></u></p></div><div><p =
class=3D"MsoNormal">
In the past we have allowed implementations to make the conformance =
choice between supporting a MIB as RW, or implementing =
read-only.<u></u><u></u></p></div><div><p class=3D"MsoNormal">If we =
advise WGs to not develop module with RW objects, then we take the =
choice away from the vendors.<u></u><u></u></p>
</div><div><p class=3D"MsoNormal">I thick that would be a =
mistake.<u></u><u></u></p></div><div><p =
class=3D"MsoNormal"><u></u>&nbsp;<u></u></p></div><div><p =
class=3D"MsoNormal">In &nbsp;addition, it is pointed out later in this =
thread that other SDOs use RW MIBs.&nbsp;<u></u><u></u></p>
</div><div><p class=3D"MsoNormal">Well, those MIBs produced by other =
SDOs (and for that matter, vendors) might require some support for =
specific RW objects in IETF MIB modules.<u></u><u></u></p></div><div><p =
class=3D"MsoNormal">
Therefore, I think it would be providing bad advice to say that IETF WGs =
should not produce MIB &nbsp;modules with RW objects in =
them.<u></u><u></u></p></div><div><p =
class=3D"MsoNormal"><u></u>&nbsp;<u></u></p></div><div><p =
class=3D"MsoNormal">
If Netconf/YANG becomes widely deployed, then NMS implementations and =
operators can choose whether to use YANG or SNMP (or their CLI) to =
adjust network configurations.<u></u><u></u></p></div><div><p =
class=3D"MsoNormal">THat should not be a decision we make in the IETF, =
effectively forcing WGs to not develop MIBs with writable =
objects.<u></u><u></u></p>
</div><div><p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p></div><div><p =
class=3D"MsoNormal">Providing RW objects in MIB modules lets =
implementers and operators make the appropriate choice for their =
environments. (See RFC 3365 for similar thinking vis-a-vis =
security.)<u></u><u></u></p>
</div><div><p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p></div><div><p =
class=3D"MsoNormal">dbh<u></u><u></u></p></div><div><p =
class=3D"MsoNormal"><u></u>&nbsp;<u></u></p><div><div><p =
class=3D"MsoNormal">On Feb 4, 2014, at 8:32 AM, Adrian Farrel &lt;<a =
href=3D"mailto:adrian@olddog.co.uk" =
target=3D"_blank">adrian@olddog.co.uk</a>&gt; wrote:<u></u><u></u></p>
</div><p =
class=3D"MsoNormal"><br><u></u><br><u></u><u></u><u></u></p><div><div><p =
class=3D"MsoNormal" style=3D"text-align:justify"><span =
style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif=
&quot;;color:#1f497d">Hi,</span><span =
style=3D"font-size:10.0pt;font-family:&quot;Malgun =
Gothic&quot;,&quot;sans-serif&quot;"><u></u><u></u></span></p><p =
class=3D"MsoNormal" style=3D"text-align:justify"><span =
style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif=
&quot;;color:#1f497d">&nbsp;</span><span =
style=3D"font-size:10.0pt;font-family:&quot;Malgun =
Gothic&quot;,&quot;sans-serif&quot;"><u></u><u></u></span></p><p =
class=3D"MsoNormal" style=3D"text-align:justify"><span =
style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif=
&quot;;color:#1f497d">The MPLS working group is testing the water to see =
whether one of its MIB modules should be "reduced" to read-only. This is =
the document that triggered my recent questions that led on to the draft =
advice you are working on. The WG took the document back to make this =
decision.</span><span style=3D"font-size:10.0pt;font-family:&quot;Malgun =
Gothic&quot;,&quot;sans-serif&quot;"><u></u><u></u></span></p><p =
class=3D"MsoNormal" style=3D"text-align:justify"><span =
style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif=
&quot;;color:#1f497d">&nbsp;</span><span =
style=3D"font-size:10.0pt;font-family:&quot;Malgun =
Gothic&quot;,&quot;sans-serif&quot;"><u></u><u></u></span></p><p =
class=3D"MsoNormal" style=3D"text-align:justify"><span =
style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif=
&quot;;color:#1f497d">You'll note below that we immediately have an =
implementation claim (not for this doc, but for the modules it =
extends).</span><span style=3D"font-size:10.0pt;font-family:&quot;Malgun =
Gothic&quot;,&quot;sans-serif&quot;"><u></u><u></u></span></p><p =
class=3D"MsoNormal" style=3D"text-align:justify"><span =
style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif=
&quot;;color:#1f497d">&nbsp;</span><span =
style=3D"font-size:10.0pt;font-family:&quot;Malgun =
Gothic&quot;,&quot;sans-serif&quot;"><u></u><u></u></span></p><p =
class=3D"MsoNormal" style=3D"text-align:justify"><span =
style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif=
&quot;;color:#1f497d">An interesting situation, I think.</span><span =
style=3D"font-size:10.0pt;font-family:&quot;Malgun =
Gothic&quot;,&quot;sans-serif&quot;"><u></u><u></u></span></p><p =
class=3D"MsoNormal" style=3D"text-align:justify"><span =
style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif=
&quot;;color:#1f497d">&nbsp;</span><span =
style=3D"font-size:10.0pt;font-family:&quot;Malgun =
Gothic&quot;,&quot;sans-serif&quot;"><u></u><u></u></span></p><p =
class=3D"MsoNormal" style=3D"text-align:justify"><span =
style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif=
&quot;;color:#1f497d">A</span><span =
style=3D"font-size:10.0pt;font-family:&quot;Malgun =
Gothic&quot;,&quot;sans-serif&quot;"><u></u><u></u></span></p><p =
class=3D"MsoNormal" style=3D"text-align:justify"><span =
style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif=
&quot;;color:#1f497d">&nbsp;</span><span =
style=3D"font-size:10.0pt;font-family:&quot;Malgun =
Gothic&quot;,&quot;sans-serif&quot;"><u></u><u></u></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 =
lang=3D"EN-US" =
style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&=
quot;">From:</span></b><span lang=3D"EN-US" =
style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&=
quot;">&nbsp;mpls [mailto:<a href=3D"mailto:mpls-" =
target=3D"_blank">mpls-</a><a href=3D"mailto:bounces@ietf.org" =
target=3D"_blank"><span =
style=3D"color:#954f72">bounces@ietf.org</span></a>]&nbsp;<b>On Behalf =
Of&nbsp;</b>GyeRok Gwun (???)<br>
<b>Sent:</b>&nbsp;04 February 2014 09:57<br><b>To:</b>&nbsp;'<a =
href=3D"mailto:mpls@ietf.org" target=3D"_blank"><span =
style=3D"color:#954f72">mpls@ietf.org</span></a>'<br><b>Cc:</b>&nbsp;'<a =
href=3D"mailto:mpls-chairs@tools.ietf.org" target=3D"_blank"><span =
style=3D"color:#954f72">mpls-chairs@tools.ietf.org</span></a>'; '<a =
href=3D"mailto:draft-ietf-mpls-tp-te-mib@tools.ietf.org" =
target=3D"_blank"><span =
style=3D"color:#954f72">draft-ietf-mpls-tp-te-mib@tools.ietf.org</span></a=
>'<br>
<b>Subject:</b>&nbsp;Re: [mpls] seeking consensus on making =
draft-ietf-mpls-tp-te-mib read- only</span><span =
style=3D"font-size:10.0pt;font-family:&quot;Malgun =
Gothic&quot;,&quot;sans-serif&quot;"><u></u><u></u></span></p></div>
</div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span =
style=3D"font-size:10.0pt;font-family:&quot;Malgun =
Gothic&quot;,&quot;sans-serif&quot;">&nbsp;<u></u><u></u></span></p><div><=
p class=3D"MsoNormal" style=3D"word-break:break-all">
<span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;">No/oppose to make as Read-only mib.</span><span =
style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;"><u></u><u></u></span></p></div><div><p class=3D"MsoNormal" =
style=3D"word-break:break-all"><span lang=3D"EN-US" =
style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">In our =
products we extensively use R/W object of TE mib. We also have NMS/EMS =
that use TE read-write Objects</span><span =
style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;"><u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span =
lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;">&nbsp;</span><span =
style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;"><u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span =
lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;">Best Regards</span><span =
style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;"><u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span =
lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;">Gwun</span><span =
style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;"><u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span =
lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;">&nbsp;</span><span =
style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;"><u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span =
lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;">-----Original Message-----</span><span =
style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;"><u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span =
lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;">From: mpls [<a href=3D"mailto:mpls-bounces@ietf.org" =
target=3D"_blank"><span =
style=3D"color:#954f72">mailto:mpls-bounces@ietf.org</span></a>] On =
Behalf Of Loa Andersson</span><span =
style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;"><u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span =
lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;">Sent: Monday, February 03, 2014 10:55 PM</span><span =
style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;"><u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span =
lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;">To:&nbsp;<a href=3D"mailto:mpls@ietf.org" =
target=3D"_blank"><span =
style=3D"color:#954f72">mpls@ietf.org</span></a></span><span =
style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;"><u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span =
lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;">Cc:&nbsp;<a href=3D"mailto:mpls-chairs@tools.ietf.org" =
target=3D"_blank"><span =
style=3D"color:#954f72">mpls-chairs@tools.ietf.org</span></a>;&nbsp;<a =
href=3D"mailto:draft-ietf-mpls-tp-te-mib@tools.ietf.org" =
target=3D"_blank"><span =
style=3D"color:#954f72">draft-ietf-mpls-tp-te-mib@tools.ietf.org</span></a=
></span><span style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;"><u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span =
lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;">Subject: [mpls] seeking consensus on making =
draft-ietf-mpls-tp-te-mib read- only</span><span =
style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;"><u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span =
lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;">&nbsp;</span><span =
style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;"><u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span =
lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;">Working Group,</span><span =
style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;"><u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span =
lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;">&nbsp;</span><span =
style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;"><u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span =
lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;">We have just recalled draft-ietf-mpls-tp-te-mib from the IESG =
to the working group for more work. We have a series of comments that =
are mostly for clarification. However the main reason for recalling the =
document is that there is one point where we need to confirm working =
group consensus.</span><span =
style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;"><u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span =
lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;">&nbsp;</span><span =
style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;"><u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span =
lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;">The IETF, the working group and the MIB Doctors are today =
very reluctant to produce read-write MIB modules. The current draft is =
read-write for a few objects, this is based on a consensus call for an =
earlier discussion, however the consensus call was not clear. It can be =
taken to mean both that we want to go with read-write objects and that =
we want to see read-only. Is it clear that it has been interpreted =
differently by different individuals.</span><span =
style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;"><u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span =
lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;">&nbsp;</span><span =
style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;"><u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span =
lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;">The authors and chairs have discussed the issue and we have a =
rough consensus that we want the MIB module(s) to be =
read-only.</span><span style=3D"font-size:10.0pt;font-family:&quot;Courier=
 New&quot;"><u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span =
lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;">&nbsp;</span><span =
style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;"><u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span =
lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;">We therefore are asking the working group if this is OK for =
the MIB</span><span style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;"><u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span =
lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;">module(s) in the current document. Please indicate Support or =
Oppose for this MIB (draft-ietf-mpls-tp-te-mib) to be =
read-only.</span><span style=3D"font-size:10.0pt;font-family:&quot;Courier=
 New&quot;"><u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span =
lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;">&nbsp;</span><span =
style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;"><u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span =
lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;">Please send your comments to the working group mailing list =
before February 18, 2014.</span><span =
style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;"><u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span =
lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;">&nbsp;</span><span =
style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;"><u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span =
lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;">Loa</span><span =
style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;"><u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span =
lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;">for the MPLS wg chairs</span><span =
style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;"><u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span =
lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;">--</span><span =
style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;"><u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span =
lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;">&nbsp;</span><span =
style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;"><u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span =
lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;">&nbsp;</span><span =
style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;"><u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span =
lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;">Loa =
Andersson&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
email:&nbsp;<a href=3D"mailto:loa@mail01.huawei.com" =
target=3D"_blank"><span =
style=3D"color:#954f72">loa@mail01.huawei.com</span></a></span><span =
style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;"><u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span =
lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;">Senior MPLS =
Expert&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;<a href=3D"mailto:loa@pi.nu" target=3D"_blank"><span =
style=3D"color:#954f72">loa@pi.nu</span></a></span><span =
style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;"><u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span =
lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;">Huawei Technologies (consultant)&nbsp;&nbsp;&nbsp;&nbsp; =
phone: +46 739 81 21 64</span><span =
style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;"><u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span =
lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;">_______________________________________________</span><span =
style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;"><u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span =
lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;">mpls mailing list</span><span =
style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;"><u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span =
lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;"><a href=3D"mailto:mpls@ietf.org" target=3D"_blank"><span =
style=3D"color:#954f72">mpls@ietf.org</span></a></span><span =
style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;"><u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span =
lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;"><a href=3D"https://www.ietf.org/mailman/listinfo/mpls" =
target=3D"_blank"><span =
style=3D"color:#954f72">https://www.ietf.org/mailman/listinfo/mpls</span><=
/a></span><span style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;"><u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span =
lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;">_______________________________________________</span><span =
style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;"><u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span =
lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;">mpls mailing list</span><span =
style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;"><u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span =
lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;"><a href=3D"mailto:mpls@ietf.org" target=3D"_blank"><span =
style=3D"color:#954f72">mpls@ietf.org</span></a></span><span =
style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;"><u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span =
lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;"><a href=3D"https://www.ietf.org/mailman/listinfo/mpls" =
target=3D"_blank"><span =
style=3D"color:#954f72">https://www.ietf.org/mailman/listinfo/mpls</span><=
/a></span><span style=3D"font-size:10.0pt;font-family:&quot;Courier =
New&quot;"><u></u><u></u></span></p>
</div><p class=3D"MsoNormal" =
style=3D"text-align:justify;word-break:break-all"><span lang=3D"EN-US" =
style=3D"font-size:10.0pt;font-family:&quot;Malgun =
Gothic&quot;,&quot;sans-serif&quot;">&nbsp;</span><span =
style=3D"font-size:10.0pt;font-family:&quot;Malgun =
Gothic&quot;,&quot;sans-serif&quot;"><u></u><u></u></span></p>
</div></div><p class=3D"MsoNormal"><span =
style=3D"font-size:13.5pt;font-family:&quot;Helvetica&quot;,&quot;sans-ser=
if&quot;">_______________________________________________<br>MIB-DOCTORS =
mailing list<br><a href=3D"mailto:MIB-DOCTORS@ietf.org" =
target=3D"_blank"><span =
style=3D"color:#954f72">MIB-DOCTORS@ietf.org</span></a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/mib-doctors" =
target=3D"_blank"><span =
style=3D"color:#954f72">https://www.ietf.org/mailman/listinfo/mib-doctors<=
/span></a><u></u><u></u></span></p></div></div><p class=3D"MsoNormal">
<u></u>&nbsp;<u></u></p></div></div><p class=3D"MsoNormal" =
style=3D"margin-bottom:12.0pt"><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"_blank">https://www.ietf.org/mailman/listinfo/mib-doctors</a><u>=
</u><u></u></p></div><p =
class=3D"MsoNormal"><u></u>&nbsp;<u></u></p></div></div></div></blockquote=
>
</div><br></div></div>
_______________________________________________<br>MIB-DOCTORS mailing =
list<br><a =
href=3D"mailto:MIB-DOCTORS@ietf.org">MIB-DOCTORS@ietf.org</a><br>https://w=
ww.ietf.org/mailman/listinfo/mib-doctors<br></blockquote></div><br></body>=
</html>=

--Apple-Mail=_51DC14BE-6015-44C5-B50A-8BA947A38148--

--Apple-Mail=_18DB3BD0-2DF3-4807-BC14-8A1073DEAEE6
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

iQIcBAEBCgAGBQJTDm1mAAoJEPcO+I7eiUJZOggP/jhBHKFuIqaMVp66TMuJoC0m
hMttgvwnMXciiMPqlFqOFKFqetDWjqQ5FqOMUn3mNsM+qIUEqKZGnSxoCFRdhcyR
Hw6/HrBpqMFsXwBn+EXkuI6D48GihFefJ65KKxXdFIrx3oee1GM88WaXoh+Iqjzg
Q6zBNa+0HQ7wQ7s4yp7q3+xOVpDZ/8iLscTQodK3BmxP5pO+2qzxcEq04Ty4hn83
zOYj1bfzVEZ0YhTcCAElOLYpO25E1TvEHorAxrRO1o8Ei4ID8bahFvs1hDI8rakD
cCAaohmYHE9hz+bRWsfRdWfwFIsqtQEC6eqE7eyt8da20Eqhv1Er1K1TAGge7KPh
HnLL59pO9dsM/0y4ZOKBXwAkunBTXuuRZR8yQYv8gLq4vHzG4dwxX+6WGJMn5VSs
jN5S8NNRN64MAYW0wgJmNelCdOc4A2G1IUuK70LPbPja3oDj2QeIpVXzeyY5Y4fE
Jsk8sts7Gw+MhmgwObScAgmUvSXIjcQXJxNlQB3CwBWsoMKfKO3dWmgOXaSdwEcd
8ogSyFnzwdE4S2yq5KVfOiyzB2lIZxeePfcuYxvNzODxpZO9ksCUed/fcIduFO/b
KJEy6LNCjJ/OV9KmM6gmq0PG01Ir98/F5nQL2x97NqWNipdAKzrIDIIm3GqwXonQ
oicu0jqMUeMnIBvC2GR4
=JDPx
-----END PGP SIGNATURE-----

--Apple-Mail=_18DB3BD0-2DF3-4807-BC14-8A1073DEAEE6--


From nobody Thu Feb 27 02:06:29 2014
Return-Path: <Quittek@neclab.eu>
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 623CC1A0806; Thu, 27 Feb 2014 02:06:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.449
X-Spam-Level: 
X-Spam-Status: No, score=-0.449 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.547, 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 dk2oNI3xcIGz; Thu, 27 Feb 2014 02:06:26 -0800 (PST)
Received: from mailer1.neclab.eu (mailer1.neclab.eu [195.37.70.40]) by ietfa.amsl.com (Postfix) with ESMTP id 693341A07EF; Thu, 27 Feb 2014 02:06:26 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailer1.neclab.eu (Postfix) with ESMTP id B9B88106E5C; Thu, 27 Feb 2014 11:06:24 +0100 (CET)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (netlab.nec.de)
Received: from mailer1.neclab.eu ([127.0.0.1]) by localhost (atlas-a.office.hd [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vjNbFzu6LezB; Thu, 27 Feb 2014 11:06:24 +0100 (CET)
X-ENC: Last-Hop-TLS-encrypted
X-ENC: Last-Hop-TLS-encrypted
Received: from ENCELADUS.office.hd (enceladus.office.hd [192.168.24.52]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mailer1.neclab.eu (Postfix) with ESMTPS id 99F3F106E84; Thu, 27 Feb 2014 11:06:04 +0100 (CET)
Received: from PALLENE.office.hd ([169.254.1.233]) by ENCELADUS.office.hd ([192.168.24.52]) with mapi id 14.01.0323.003; Thu, 27 Feb 2014 11:06:04 +0100
From: Juergen Quittek <Quittek@neclab.eu>
To: Thomas Nadeau <tnadeau@lucidvision.com>, "draft-ietf-eman-battery-mib@tools.ietf.org" <draft-ietf-eman-battery-mib@tools.ietf.org>
Thread-Topic: [eman] MIB-Doctor Review of draft-ietf-eman-battery-mib-11
Thread-Index: AQHPGUrAPWHfU4CFBUe1IOKiozRfY5rHwzYA
Date: Thu, 27 Feb 2014 10:06:04 +0000
Message-ID: <9AB93E4127C26F4BA7829DEFDCE5A6E877A6D34F@PALLENE.office.hd>
References: <BE98C880-7F58-41E4-BA0D-D1E233D79ACA@lucidvision.com>
In-Reply-To: <BE98C880-7F58-41E4-BA0D-D1E233D79ACA@lucidvision.com>
Accept-Language: de-DE, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.1.99.69]
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/yq-oy64RlK9bkD1lfoQublS3iXA
Cc: "MIB Doctors \(E-mail\)" <mib-doctors@ietf.org>, eman mailing list <eman@ietf.org>
Subject: Re: [MIB-DOCTORS] [eman] MIB-Doctor Review of draft-ietf-eman-battery-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: Thu, 27 Feb 2014 10:06:28 -0000

Dear Tom,

Thank you very much for your review.=20
Please see replies in line. This email addresses all of your issues
 except for the last one which I will reply to in a separate message.
Cheers,
    Juergen

> -----Original Message-----
> From: eman [mailto:eman-bounces@ietf.org] On Behalf Of Thomas Nadeau
> Sent: Freitag, 24. Januar 2014 22:24
> To: draft-ietf-eman-battery-mib@tools.ietf.org
> Cc: MIB Doctors (E-mail); eman mailing list
> Subject: [eman] MIB-Doctor Review of draft-ietf-eman-battery-mib-11
>=20
>=20
>=20
> 	I reviewed this draft as part of the MIB Doctor review on Friday,
> January 24, 2014.
> In general the MIB is in good shape. I have some questions/comments inlin=
e
> begin with TOM:
>=20
>    General Comments on the draft:
>=20
>    1) My run of id-nits produced no errors and a few warnings that can be
> ignored.
>=20
>    2) In general, please go through the MIB modules and verify that the
> Integer32 values are indeed ok to be negative values or change them to
> Unsigned. For example, there are many instances where you used Integer32
> for things like watts or amps where negative values do not make sense, to
> me at least.

We use Integer32 for Current and temperatures. For temperature we do not
use Kelvin, but degree Celsius as units which may have negative values. For
current the DESCRIPTION clause explains that positive values are for chargi=
ng
current and negative values are for discharging current.

>
     [snip]
>    --------------------------------------------------------------------
>    -- 1.1. Battery Table
>    --------------------------------------------------------------------
>    batteryTable  OBJECT-TYPE
>        SYNTAX      SEQUENCE OF BatteryEntry
>        MAX-ACCESS  not-accessible
>        STATUS      current
>        DESCRIPTION
>            "This table provides information on batteries.  It contains
>            one conceptual row per battery.
>=20
> TOM: Is this a set of batteries per managed device?

Yes. For example, the notebook I am writing this email on has two batteries=
.

Proposal:
OLD
        "This table provides information on batteries.  It contains=20
        one conceptual row per battery. =20
NEW
        "This table provides information on batteries.  It contains=20
        one conceptual row per battery in a managed entity
=20
> =20
     [snip]
>=20
>    batteryTemperature OBJECT-TYPE
>        SYNTAX      Integer32
>        UNITS       "deci-degrees Celsius"
>        MAX-ACCESS  read-only
>        STATUS      current
>        DESCRIPTION
>            "The ambient temperature at or near the battery.
>=20
> TOM: Is there some spec that defines what "near" means?

No, there is not. Actual implementations vary significantly. Some sensors a=
re directly attached to or even inside the battery, some are a few centimet=
ers away from the battery, but (hopefully) in the flow of heated air that p=
assed the battery for cooling. Even for sensors inside the battery, there a=
re problems. Sometimes single cells in a multi-cell battery become very hot=
. Then it depends on the location of the sensor (close to the particular ce=
ll or rather far away) if this is observable from outside.

>=20
     [snip]
>=20
>    batteryAlarmHighCycleCount OBJECT-TYPE
>        SYNTAX      Unsigned32
>        MAX-ACCESS  read-write
>        STATUS      current
>        DESCRIPTION
>            "This object provides the upper threshold value for object
>            batteryChargingCycleCount.  If the value of object
>            batteryChargingCycleCount rises above this threshold,
>            a battery aging alarm will be raised.  The alarm procedure
>            may include generating a batteryAgingNotification.
>=20
>            A value of 0 indicates that no alarm will be raised for any
>            value of object batteryChargingCycleCount."
>=20
> TOM: Is there  any sort of holding time period over which an alarm should=
 be
> not emitted? I can imagine a case where a battery is charged, discharged,
> etc... and just goes above and below this threshold causing a lot of
> notifications to be emitted. Another option would be to add variable that
> defines X numebr of notifications per time period.

Yes, there is. We have specified this in the DESCRIPTION clauses of=20
Some NOTIFICATION-TYPEs but apparently not for all where this would
Be desirable. Please see a separate email on this issue.

For the cycle count alarm above we do not see a need for this, because=20
The cycle count is monotonically increasing.
=20
>=20
     [snip]
>=20
>    batteryTemperatureNotification NOTIFICATION-TYPE
>        OBJECTS     {
>            batteryTemperature,
>            batteryCellIdentifier
>        }
>        STATUS      current
>        DESCRIPTION
>            "This notification can be generated when the measured
>            temperature (batteryTemperature) rises above the threshold
>            defined by object batteryAlarmHighTemperature or falls
>            below the threshold defined by object
>            batteryAlarmLowTemperature.
>=20
>            If the low or high temperature has been detected for a
>            single cell or a set of cells of the battery and not for the
>            entire battery, then object batteryCellIdentifier should be
>            set to a value that identifies the cell or set of cells.
>            Otherwise, the value of object batteryCellIdentifier should
>            be set to the empty string when this notification is
>            generated."
>        ::=3D { batteryNotifications 4 }
>=20
> TOM: The same comment about rate limiting as above. I can see when a
> battery is failing this value could float just about and below this value=
 causing
> numerious notifications to be issued. Have you considered such cases?

Please see separate email.

Thanks,
    Juergen


From nobody Thu Feb 27 03:44:25 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 6A6CF1A012B; Thu, 27 Feb 2014 03:44:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.447
X-Spam-Level: 
X-Spam-Status: No, score=-2.447 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.547] 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 ax4kBlLpJbl5; Thu, 27 Feb 2014 03:44:23 -0800 (PST)
Received: from lucidvision.com (lucidvision.com [72.71.250.34]) by ietfa.amsl.com (Postfix) with ESMTP id 7A7FF1A018F; Thu, 27 Feb 2014 03:44:23 -0800 (PST)
Received: from [192.168.1.122] (static-72-71-250-38.cncdnh.fast04.myfairpoint.net [72.71.250.38]) by lucidvision.com (Postfix) with ESMTP id 5402F270A13F; Thu, 27 Feb 2014 06:44:21 -0500 (EST)
Content-Type: multipart/signed; boundary="Apple-Mail=_976B61A0-E6C8-4995-A714-6B99675923F3"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Thomas Nadeau <tnadeau@lucidvision.com>
In-Reply-To: <9AB93E4127C26F4BA7829DEFDCE5A6E877A6D34F@PALLENE.office.hd>
Date: Thu, 27 Feb 2014 06:44:19 -0500
Message-Id: <5FB8FBDF-C7AD-42F9-9E7C-60813DDC5149@lucidvision.com>
References: <BE98C880-7F58-41E4-BA0D-D1E233D79ACA@lucidvision.com> <9AB93E4127C26F4BA7829DEFDCE5A6E877A6D34F@PALLENE.office.hd>
To: Juergen Quittek <Quittek@neclab.eu>
X-Mailer: Apple Mail (2.1827)
Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/K27-_xkynyBzDeNH6a0RzirVE_A
Cc: "MIB Doctors \(E-mail\)" <mib-doctors@ietf.org>, eman mailing list <eman@ietf.org>, "draft-ietf-eman-battery-mib@tools.ietf.org" <draft-ietf-eman-battery-mib@tools.ietf.org>
Subject: Re: [MIB-DOCTORS] [eman] MIB-Doctor Review of draft-ietf-eman-battery-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: Thu, 27 Feb 2014 11:44:25 -0000

--Apple-Mail=_976B61A0-E6C8-4995-A714-6B99675923F3
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


On Feb 27, 2014:5:06 AM, at 5:06 AM, Juergen Quittek <Quittek@neclab.eu> =
wrote:

> Dear Tom,
>=20
> Thank you very much for your review.=20
> Please see replies in line. This email addresses all of your issues
> except for the last one which I will reply to in a separate message.
> Cheers,
>    Juergen
>=20
>> -----Original Message-----
>> From: eman [mailto:eman-bounces@ietf.org] On Behalf Of Thomas Nadeau
>> Sent: Freitag, 24. Januar 2014 22:24
>> To: draft-ietf-eman-battery-mib@tools.ietf.org
>> Cc: MIB Doctors (E-mail); eman mailing list
>> Subject: [eman] MIB-Doctor Review of draft-ietf-eman-battery-mib-11
>>=20
>>=20
>>=20
>> 	I reviewed this draft as part of the MIB Doctor review on =
Friday,
>> January 24, 2014.
>> In general the MIB is in good shape. I have some questions/comments =
inline
>> begin with TOM:
>>=20
>>   General Comments on the draft:
>>=20
>>   1) My run of id-nits produced no errors and a few warnings that can =
be
>> ignored.
>>=20
>>   2) In general, please go through the MIB modules and verify that =
the
>> Integer32 values are indeed ok to be negative values or change them =
to
>> Unsigned. For example, there are many instances where you used =
Integer32
>> for things like watts or amps where negative values do not make =
sense, to
>> me at least.
>=20
> We use Integer32 for Current and temperatures. For temperature we do =
not
> use Kelvin, but degree Celsius as units which may have negative =
values. For
> current the DESCRIPTION clause explains that positive values are for =
charging
> current and negative values are for discharging current.

TOM: OK.  Just ensure that the descriptions are clear of these boundary =
conditions.

>=20
>>=20
>     [snip]
>>   =
--------------------------------------------------------------------
>>   -- 1.1. Battery Table
>>   =
--------------------------------------------------------------------
>>   batteryTable  OBJECT-TYPE
>>       SYNTAX      SEQUENCE OF BatteryEntry
>>       MAX-ACCESS  not-accessible
>>       STATUS      current
>>       DESCRIPTION
>>           "This table provides information on batteries.  It contains
>>           one conceptual row per battery.
>>=20
>> TOM: Is this a set of batteries per managed device?
>=20
> Yes. For example, the notebook I am writing this email on has two =
batteries.
>=20
> Proposal:
> OLD
>        "This table provides information on batteries.  It contains=20
>        one conceptual row per battery. =20
> NEW
>        "This table provides information on batteries.  It contains=20
>        one conceptual row per battery in a managed entity

TOM: Cool.

>=20
>>=20
>     [snip]
>>=20
>>   batteryTemperature OBJECT-TYPE
>>       SYNTAX      Integer32
>>       UNITS       "deci-degrees Celsius"
>>       MAX-ACCESS  read-only
>>       STATUS      current
>>       DESCRIPTION
>>           "The ambient temperature at or near the battery.
>>=20
>> TOM: Is there some spec that defines what "near" means?
>=20
> No, there is not. Actual implementations vary significantly. Some =
sensors are directly attached to or even inside the battery, some are a =
few centimeters away from the battery, but (hopefully) in the flow of =
heated air that passed the battery for cooling. Even for sensors inside =
the battery, there are problems. Sometimes single cells in a multi-cell =
battery become very hot. Then it depends on the location of the sensor =
(close to the particular cell or rather far away) if this is observable =
from outside.

TOM: Maybe change "near" to "within close proximity" ?

>>=20
>     [snip]
>>=20
>>   batteryAlarmHighCycleCount OBJECT-TYPE
>>       SYNTAX      Unsigned32
>>       MAX-ACCESS  read-write
>>       STATUS      current
>>       DESCRIPTION
>>           "This object provides the upper threshold value for object
>>           batteryChargingCycleCount.  If the value of object
>>           batteryChargingCycleCount rises above this threshold,
>>           a battery aging alarm will be raised.  The alarm procedure
>>           may include generating a batteryAgingNotification.
>>=20
>>           A value of 0 indicates that no alarm will be raised for any
>>           value of object batteryChargingCycleCount."
>>=20
>> TOM: Is there  any sort of holding time period over which an alarm =
should be
>> not emitted? I can imagine a case where a battery is charged, =
discharged,
>> etc... and just goes above and below this threshold causing a lot of
>> notifications to be emitted. Another option would be to add variable =
that
>> defines X numebr of notifications per time period.
>=20
> Yes, there is. We have specified this in the DESCRIPTION clauses of=20
> Some NOTIFICATION-TYPEs but apparently not for all where this would
> Be desirable. Please see a separate email on this issue.

TOM: Indeed. Can you please ensure that each one has this?  Otherwise we =
could have interop issues.=20

> For the cycle count alarm above we do not see a need for this, because=20=

> The cycle count is monotonically increasing.

TOM: Again, its good to explicitly put that into the description so that =
interop of implementations can be made easier.

>=20
>>=20
>     [snip]
>>=20
>>   batteryTemperatureNotification NOTIFICATION-TYPE
>>       OBJECTS     {
>>           batteryTemperature,
>>           batteryCellIdentifier
>>       }
>>       STATUS      current
>>       DESCRIPTION
>>           "This notification can be generated when the measured
>>           temperature (batteryTemperature) rises above the threshold
>>           defined by object batteryAlarmHighTemperature or falls
>>           below the threshold defined by object
>>           batteryAlarmLowTemperature.
>>=20
>>           If the low or high temperature has been detected for a
>>           single cell or a set of cells of the battery and not for =
the
>>           entire battery, then object batteryCellIdentifier should be
>>           set to a value that identifies the cell or set of cells.
>>           Otherwise, the value of object batteryCellIdentifier should
>>           be set to the empty string when this notification is
>>           generated."
>>       ::=3D { batteryNotifications 4 }
>>=20
>> TOM: The same comment about rate limiting as above. I can see when a
>> battery is failing this value could float just about and below this =
value causing
>> numerious notifications to be issued. Have you considered such cases?
>=20
> Please see separate email.
>=20
> Thanks,
>    Juergen
>=20


--Apple-Mail=_976B61A0-E6C8-4995-A714-6B99675923F3
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

iQIcBAEBCgAGBQJTDyUUAAoJEPcO+I7eiUJZETUP/3x2csoe9HEieGh86sB1q3ry
ROPtNrLLzHzzOudV5sZl2BW8bCA0iGKQnzOqC7MgPKqXSQaOMIIMYPPvXpnEPbJD
qgdXjHjvkop8/uOvvBIdEm+g0XNQSPC4I85YS/i35N/Jflvn/pSxt7ElEcQei3Sp
qcQm10SOo00/bk2npY6OSzBNHDoArmr5cZiY+/nyAG4rgW3MnmWhXXtouILERSTz
PkYkbpsBoeX/GCf7dAagUGs/f0wTRQx01dbWlQaIgEMbwIifwGK8KJMuKkPiVUqK
Q6Y11lB+CkGGZrjbPBnzxy/A+8snjfIWUfcjD21986vUU8PKAVa29/ApT/fbZbCu
gfcjYUe55VxUr37OxS+sWwaTeXpNQJgcWRmr9wr8FtYqguTB8fi5HzLmi6nde1/5
hldwfnElOOy1CuVfQJL1RCf6k5SKQCX5x//9V+ZGvD80bDPQummi2eXcWCANgh6K
ZK2m2OY48uMO+T7l9MDHN3pDTiMdyGcP/A5cuHJAJr3w+nvvrvsyMvlnp9xZbH65
m8ASxXVfnaTDvSW+SOp26jNLHT6VwGQVSvyZqjciQBhoc213hLjBLpSqzztuKsC3
NC2n4KV6Od8gqHo+Lcfcm8+hN4C20Zf/58za1sw1Kz64wI62x2BEiM2BDCYgFL48
zan1zc4aYYU1xuv6tJUB
=waIq
-----END PGP SIGNATURE-----

--Apple-Mail=_976B61A0-E6C8-4995-A714-6B99675923F3--


From nobody Thu Feb 27 14:14:56 2014
Return-Path: <dbharrington@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 70E8A1A01F3 for <mib-doctors@ietfa.amsl.com>; Thu, 27 Feb 2014 14:14:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.546
X-Spam-Level: 
X-Spam-Status: No, score=-2.546 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, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.547, 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 8Jby6uoUbbb7 for <mib-doctors@ietfa.amsl.com>; Thu, 27 Feb 2014 14:14:47 -0800 (PST)
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 0CD661A0198 for <mib-doctors@ietf.org>; Thu, 27 Feb 2014 14:14:46 -0800 (PST)
Received: from omta12.westchester.pa.mail.comcast.net ([76.96.62.44]) by qmta01.westchester.pa.mail.comcast.net with comcast id XQFL1n0080xGWP851aElVY; Thu, 27 Feb 2014 22:14:45 +0000
Received: from JV6RVH1 ([67.189.237.137]) by omta12.westchester.pa.mail.comcast.net with comcast id XaEk1n00Z2yZEBF3YaEkl8; Thu, 27 Feb 2014 22:14:45 +0000
From: "David Harrington" <dbharrington@comcast.net>
To: "'Thomas Nadeau'" <tnadeau@lucidvision.com>, "'Andy Bierman'" <andy@yumaworks.com>
References: <05c501cf21ad$80d97ef0$828c7cd0$@olddog.co.uk> <7D263081-6D84-4AA2-B0CB-FA74793BD135@comcast.net> <CABCOCHT3UCVmpLcEAH2Q3mrfbWMxh=c7FZ4d61pAmpwb8t-sug@mail.gmail.com> <00d601cf25b3$371c77e0$a55567a0$@olddog.co.uk> <CABCOCHQJsBy8DvPEOy-b1Xs-MWzfgZCwWtWjrpngHLeicMAefA@mail.gmail.com> <A41519E1-DE8A-4B0C-B421-45B5D42BA2C7@lucidvision.com>
In-Reply-To: <A41519E1-DE8A-4B0C-B421-45B5D42BA2C7@lucidvision.com>
Date: Thu, 27 Feb 2014 17:14:41 -0500
Message-ID: <00d301cf3409$504f7b90$f0ee72b0$@comcast.net>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_00D4_01CF33DF.67805160"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQFJjvDrKd3WqTHnQB+4M0ubo7RGRAHiKeZfAXsqdsICn1z5DgG0QTzRAZ5TE8KbineDEA==
Content-Language: en-us
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1393539285; bh=Z5C8V9HmtwqdWNmB0zi/CsDriyrQCwS315dt/xwMzk0=; h=Received:Received:From:To:Subject:Date:Message-ID:MIME-Version: Content-Type; b=ifoJrBjbqh4/2HQs9wDULTJ2AJOpmU+6Y3DoUa5XomXjWMeH1ClrQtoJpUNI0bh9F r1ttTyZHfraIhT3F2lY1UUooO+l3YuYwUn24ELtZFKSy1pdREI/XJGA4fNXCngSb/a odOvAdSdVID+liLDNMz5QYU1boBy05Qj/PjAEJchVCnfiSsYkt0XtHnRN5dPzeJPOY hScbOHU/9vHDF3U+6HDripHu3+RBrYMNGrDfNJST0BR8uhnoPZKpLs0XSRmkMLwAaJ RewvMm/cWEfrk9F+jkjBAQDU58ORPs8OPapE5vcLsQGUuoiDJQu9R5SGQbSNXHCck3 RhHwQPghL62SA==
Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/AwioZ0ryJlke_VEWmaPhOLeMnMc
Cc: 'Farrel Adrian' <adrian@olddog.co.uk>, "'MIB Doctors \(E-mail\)'" <mib-doctors@ietf.org>
Subject: Re: [MIB-DOCTORS] Read-only MIB modules
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, 27 Feb 2014 22:14:54 -0000

This is a multipart message in MIME format.

------=_NextPart_000_00D4_01CF33DF.67805160
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

"WG groups can then decide

if they have enough participants who plan on implementing read-create.

If not, then they can't have it.  The MIB gets rejected and sent back

to the WG if it contains any MIN-ACCESS clauses.

"

So why should rw mibs be held to a higher standard than other IETF proposed
standards?

 

David Harrington

 <mailto:dbharrington@comcast.net> dbharrington@comcast.net

+1-603-828-1401

From: MIB-DOCTORS [mailto:mib-doctors-bounces@ietf.org] On Behalf Of Thomas
Nadeau
Sent: Wednesday, February 26, 2014 5:41 PM
To: Andy Bierman
Cc: Farrel Adrian; MIB Doctors (E-mail)
Subject: Re: [MIB-DOCTORS] Read-only MIB modules

 

 

On Feb 9, 2014:12:23 PM, at 12:23 PM, Andy Bierman <andy@yumaworks.com>
wrote:





 

 

On Sun, Feb 9, 2014 at 8:23 AM, Adrian Farrel <adrian@olddog.co.uk> wrote:

Andy,

 

I am all in favour of flailing in sandboxes as a way to burn off that excess
energy caused by high-tartrazine diets.

 

However, I think SNMP Set is showing up because people are putting together
MIB modules sans clue. They genuinely want to be helpful in the construction
of MIB modules that might have value, but they don't know how to do it and
no-one else in their immediate circle does either.

 

The consequence, beyond a spec that might or might not get implemented in
full, is that the MIB doctors have to do reviews of function they don't
believe has value.

 

 

 

The IESG and IETF have to reviews these documents as well.

I think people writing MIB modules know how to do it, but they are

following a formula setup by the IESG and blessed by MIB Doctors.

 

MIB authors seem encouraged to use read-create objects, but then

add MIN-ACCESS read-only in the conformance statement,

just in case anybody ever wants to implement the MAX-ACCESS.

 

Time to face the fact that nobody is implementing the MAX-ACCESS.

In order to claim conformance to a MIB module, it should be

without this MIB-ACCESS loophole.  WG groups can then decide

if they have enough participants who plan on implementing read-create.

If not, then they can't have it.  The MIB gets rejected and sent back

to the WG if it contains any MIN-ACCESS clauses.

 

          And hence my point about wasting time of those resources writing
those min-access statements (and conformance clauses). That stuff is
non-trivial, nor is getting row construction ordering/etc... details right.
And then its all for nothing because as you rightly said, nearly no one is
using it. 

 

          --Tom

 





 

 

Andy

 

 

 

 

 

A

 

 

From: Andy Bierman [mailto:andy@yumaworks.com] 
Sent: 09 February 2014 06:25
To: David Harrington
Cc: Adrian Farrel; MIB Doctors (E-mail)
Subject: Re: [MIB-DOCTORS] Read-only MIB modules

 

Hi,

 

I do not really know if an official statement to avoid SNMP Set is needed.

IMO the verdict is in wrt/ SNMP for configuration.

 

It has been a long-held tradition in the IETF to let people flail in their
own

sandbox if that's what they really wanted to do.  Maybe that has been a

mistake. Maybe WGs should be forced to prove that they have enough

real stakeholders willing to implement a spec, so that every part of

every proposed standard gets sponsored.

 

We often presume that "some vendors", who have had no interest in the

work all along, will eventually come around and decide to implement.

Therefore there is no need to have strong interest in deployment during

the WG process.

 

Commitment to implementation should apply to everything -- protocols,

MIB modules, YANG modules --- it doesn't matter. No stakeholders,

no sandbox.  That would be a radical change ;-)

 

 

Andy

 

 

On Sat, Feb 8, 2014 at 8:28 PM, David Harrington <ietfdbh@comcast.net>
wrote:

Hi,

 

I object to this statement. (Should I say "strongly" object, to show I mean
business?

 

There are many RW objects that can "adjust" a network configuration assuming
SET is supported by the agent involved.

The NMS I used to work on, which helped determine and correct root cause for
fault and performance problems, adjusted networks using writable MIB modules
often.

To tell WGs they should not develop RW MIB modules I think is wrong.

 

I also have a concern with recommending Netconf/YANG at this point in time.

If we looked up the top ten router vendors using something like Gartner
reports, how many of them really support configuration using Netconf with
YANG in shipping products?

Ditto, the top ten switch vendors?

How many of them can be fully configured using YANG modules (not homegrown
alternatives, but modules - standard or proprietary - written using the
standards-compliant YANG language)?

I don't know the answer to that question, but would like to see some proof
that YANG is at least as widely supported in currently shipping products as
RW MIB objects.

I think Netconf/YANG should compete in an open market with RW MIB modules,
not try to stack the deck in their favor by "strongly discouraging" RW MIB
standards.

 

I have had discussions with vendors who are leaders in their particular
networking niche, and they have told me they would not consider
Netconf/YANG, because it has not been around long enough and been
widely-enough deployed to prove stable for their production networks
(whereas SNMP has enough track record to be known to be stable).

So I'm a bit concerned about telling WGs they should develop YANG modules
rather than MIB modules.

And the current discussions of whether YANG 1.1 or 2.0 is needed to fix some
problems with YANG 1.0, and it may not be backwards compatible, make me
question the stability of YANG.

 

Don't get me wrong. I support Netconf/YANG going forward, but I think it is
important to provide advice that non-MIB-Doctors/non-YANG-experts can
interpret reasonably.

Any such statement should make a clear distinction between "configuration" -
the complete configuration of a device by Netconf - versus RW objects in a
MIB - which can be used by SNMP to adjust network parameters/configuration.

Telling people not to develop RW MIBs is throwing the baby out with the
bathwater.

We should NOT recommend against RW MIBs, because these can be used for more
than (full device) configuration.

That point is far from clear in the currently proposed statement.

Maybe the statement should be that, if a vendor wants to replace their CLI,
they should replace it with Netconf/YANG, and not with SNMP/RW-MIBs. 

That's probably a closer approximation  of Netconf/YANG's applicability
versus RW MIBs. 

 

In the past we have allowed implementations to make the conformance choice
between supporting a MIB as RW, or implementing read-only.

If we advise WGs to not develop module with RW objects, then we take the
choice away from the vendors.

I thick that would be a mistake.

 

In  addition, it is pointed out later in this thread that other SDOs use RW
MIBs. 

Well, those MIBs produced by other SDOs (and for that matter, vendors) might
require some support for specific RW objects in IETF MIB modules.

Therefore, I think it would be providing bad advice to say that IETF WGs
should not produce MIB  modules with RW objects in them.

 

If Netconf/YANG becomes widely deployed, then NMS implementations and
operators can choose whether to use YANG or SNMP (or their CLI) to adjust
network configurations.

THat should not be a decision we make in the IETF, effectively forcing WGs
to not develop MIBs with writable objects.

 

Providing RW objects in MIB modules lets implementers and operators make the
appropriate choice for their environments. (See RFC 3365 for similar
thinking vis-a-vis security.)

 

dbh

 

On Feb 4, 2014, at 8:32 AM, Adrian Farrel <adrian@olddog.co.uk> wrote:

 

Hi,

 

The MPLS working group is testing the water to see whether one of its MIB
modules should be "reduced" to read-only. This is the document that
triggered my recent questions that led on to the draft advice you are
working on. The WG took the document back to make this decision.

 

You'll note below that we immediately have an implementation claim (not for
this doc, but for the modules it extends).

 

An interesting situation, I think.

 

A

 

From: mpls [mailto:mpls- <mailto:bounces@ietf.org> bounces@ietf.org] On
Behalf Of GyeRok Gwun (???)
Sent: 04 February 2014 09:57
To: ' <mailto:mpls@ietf.org> mpls@ietf.org'
Cc: ' <mailto:mpls-chairs@tools.ietf.org> mpls-chairs@tools.ietf.org'; '
<mailto:draft-ietf-mpls-tp-te-mib@tools.ietf.org>
draft-ietf-mpls-tp-te-mib@tools.ietf.org'
Subject: Re: [mpls] seeking consensus on making draft-ietf-mpls-tp-te-mib
read- only

 

No/oppose to make as Read-only mib.

In our products we extensively use R/W object of TE mib. We also have
NMS/EMS that use TE read-write Objects

 

Best Regards

Gwun

 

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

From: mpls [ <mailto:mpls-bounces@ietf.org> mailto:mpls-bounces@ietf.org] On
Behalf Of Loa Andersson

Sent: Monday, February 03, 2014 10:55 PM

To:  <mailto:mpls@ietf.org> mpls@ietf.org

Cc:  <mailto:mpls-chairs@tools.ietf.org> mpls-chairs@tools.ietf.org;
<mailto:draft-ietf-mpls-tp-te-mib@tools.ietf.org>
draft-ietf-mpls-tp-te-mib@tools.ietf.org

Subject: [mpls] seeking consensus on making draft-ietf-mpls-tp-te-mib read-
only

 

Working Group,

 

We have just recalled draft-ietf-mpls-tp-te-mib from the IESG to the working
group for more work. We have a series of comments that are mostly for
clarification. However the main reason for recalling the document is that
there is one point where we need to confirm working group consensus.

 

The IETF, the working group and the MIB Doctors are today very reluctant to
produce read-write MIB modules. The current draft is read-write for a few
objects, this is based on a consensus call for an earlier discussion,
however the consensus call was not clear. It can be taken to mean both that
we want to go with read-write objects and that we want to see read-only. Is
it clear that it has been interpreted differently by different individuals.

 

The authors and chairs have discussed the issue and we have a rough
consensus that we want the MIB module(s) to be read-only.

 

We therefore are asking the working group if this is OK for the MIB

module(s) in the current document. Please indicate Support or Oppose for
this MIB (draft-ietf-mpls-tp-te-mib) to be read-only.

 

Please send your comments to the working group mailing list before February
18, 2014.

 

Loa

for the MPLS wg chairs

--

 

 

Loa Andersson                        email:  <mailto:loa@mail01.huawei.com>
loa@mail01.huawei.com

Senior MPLS Expert                           <mailto:loa@pi.nu> loa@pi.nu

Huawei Technologies (consultant)     phone: +46 739 81 21 64

_______________________________________________

mpls mailing list

 <mailto:mpls@ietf.org> mpls@ietf.org

 <https://www.ietf.org/mailman/listinfo/mpls>
https://www.ietf.org/mailman/listinfo/mpls

_______________________________________________

mpls mailing list

 <mailto:mpls@ietf.org> mpls@ietf.org

 <https://www.ietf.org/mailman/listinfo/mpls>
https://www.ietf.org/mailman/listinfo/mpls

 

_______________________________________________
MIB-DOCTORS mailing list
 <mailto:MIB-DOCTORS@ietf.org> MIB-DOCTORS@ietf.org
 <https://www.ietf.org/mailman/listinfo/mib-doctors>
https://www.ietf.org/mailman/listinfo/mib-doctors

 


_______________________________________________
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

 


------=_NextPart_000_00D4_01CF33DF.67805160
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=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Helvetica;
	panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
	{font-family:Helvetica;
	panose-1:2 11 6 4 2 2 2 2 2 4;}
@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:"Malgun Gothic";
	panose-1:2 11 5 3 2 0 0 2 0 4;}
@font-face
	{font-family:"\@Malgun Gothic";
	panose-1:2 11 5 3 2 0 0 2 0 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
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;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.apple-tab-span
	{mso-style-name:apple-tab-span;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></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 lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><a =
name=3D"_MailEndCompose"><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&#8220;</span></a>WG groups can then decide<o:p></o:p></p><p =
class=3DMsoNormal>if they have enough participants who plan on =
implementing read-create.<o:p></o:p></p><p class=3DMsoNormal>If not, =
then they can't have it. &nbsp;The MIB gets rejected and sent =
back<o:p></o:p></p><p class=3DMsoNormal>to the WG if it contains any =
MIN-ACCESS clauses.<o:p></o:p></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&#8220;<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>So why should rw mibs be held to a higher standard than other IETF =
proposed standards?<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><div><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'=
>David Harrington</span><span =
style=3D'color:#1F497D'><o:p></o:p></span></p><p class=3DMsoNormal><a =
href=3D"mailto:dbharrington@comcast.net"><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'>dbharrington@=
comcast.net</span></a><span =
style=3D'color:#1F497D'><o:p></o:p></span></p></div><p =
class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'=
>+1-603-828-1401</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p></o:p></span></p><div style=3D'border:none;border-left:solid =
blue 1.5pt;padding:0in 0in 0in 4.0pt'><div><div =
style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
MIB-DOCTORS [mailto:mib-doctors-bounces@ietf.org] <b>On Behalf Of =
</b>Thomas Nadeau<br><b>Sent:</b> Wednesday, February 26, 2014 5:41 =
PM<br><b>To:</b> Andy Bierman<br><b>Cc:</b> Farrel Adrian; MIB Doctors =
(E-mail)<br><b>Subject:</b> Re: [MIB-DOCTORS] Read-only MIB =
modules<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><div><p class=3DMsoNormal>On =
Feb 9, 2014:12:23 PM, at 12:23 PM, Andy Bierman &lt;<a =
href=3D"mailto:andy@yumaworks.com">andy@yumaworks.com</a>&gt; =
wrote:<o:p></o:p></p></div><p =
class=3DMsoNormal><br><br><o:p></o:p></p><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><p class=3DMsoNormal =
style=3D'margin-bottom:12.0pt'><o:p>&nbsp;</o:p></p><div><p =
class=3DMsoNormal>On Sun, Feb 9, 2014 at 8:23 AM, Adrian Farrel &lt;<a =
href=3D"mailto:adrian@olddog.co.uk" =
target=3D"_blank">adrian@olddog.co.uk</a>&gt; =
wrote:<o:p></o:p></p><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Andy,</span><span lang=3DEN-GB><o:p></o:p></span></p><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;</span><span lang=3DEN-GB><o:p></o:p></span></p><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>I am all in favour of flailing in sandboxes as a way to burn off that =
excess energy caused by high-tartrazine diets.</span><span =
lang=3DEN-GB><o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;</span><span lang=3DEN-GB><o:p></o:p></span></p><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>However, I think SNMP Set is showing up because people are putting =
together MIB modules sans clue. They genuinely want to be helpful in the =
construction of MIB modules that might have value, but they don't know =
how to do it and no-one else in their immediate circle does =
either.</span><span lang=3DEN-GB><o:p></o:p></span></p><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;</span><span lang=3DEN-GB><o:p></o:p></span></p><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>The consequence, beyond a spec that might or might not get =
implemented in full, is that the MIB doctors have to do reviews of =
function they don't believe has value.</span><span =
lang=3DEN-GB><o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB><o:p>&nbsp;</o:p></span></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>The IESG and IETF have to reviews these documents as =
well.<o:p></o:p></p></div><div><p class=3DMsoNormal>I think people =
writing MIB modules know how to do it, but they =
are<o:p></o:p></p></div><div><p class=3DMsoNormal>following a formula =
setup by the IESG and blessed by MIB =
Doctors.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>MIB authors seem encouraged to use read-create =
objects, but then<o:p></o:p></p></div><div><p class=3DMsoNormal>add =
MIN-ACCESS read-only in the conformance =
statement,<o:p></o:p></p></div><div><p class=3DMsoNormal>just in case =
anybody ever wants to implement the =
MAX-ACCESS.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>Time to face the fact that nobody is implementing the =
MAX-ACCESS.<o:p></o:p></p></div><div><p class=3DMsoNormal>In order to =
claim conformance to a MIB module, it should =
be<o:p></o:p></p></div><div><p class=3DMsoNormal>without this MIB-ACCESS =
loophole. &nbsp;WG groups can then decide<o:p></o:p></p></div><div><p =
class=3DMsoNormal>if they have enough participants who plan on =
implementing read-create.<o:p></o:p></p></div><div><p =
class=3DMsoNormal>If not, then they can't have it. &nbsp;The MIB gets =
rejected and sent back<o:p></o:p></p></div><div><p class=3DMsoNormal>to =
the WG if it contains any MIN-ACCESS =
clauses.<o:p></o:p></p></div></div></div></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><p class=3DMsoNormal><span =
class=3Dapple-tab-span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp; </span>And hence my point about wasting time of those resources =
writing those min-access statements (and conformance clauses). That =
stuff is non-trivial, nor is getting row construction ordering/etc... =
details right. &nbsp;And then its all for nothing because as you rightly =
said, nearly no one is using it.&nbsp;<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal><span =
class=3Dapple-tab-span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp; </span>--Tom<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal><br><br><o:p></o:p></p><div><div><div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>Andy<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><blockquote =
style=3D'border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in =
6.0pt;margin-left:4.8pt;margin-right:0in'><div><div><p =
class=3DMsoNormal><span =
lang=3DEN-GB><o:p>&nbsp;</o:p></span></p></div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>A</span><span lang=3DEN-GB><o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;</span><span lang=3DEN-GB><o:p></o:p></span></p><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;</span><span lang=3DEN-GB><o:p></o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
Andy Bierman [mailto:<a href=3D"mailto:andy@yumaworks.com" =
target=3D"_blank">andy@yumaworks.com</a>] <br><b>Sent:</b> 09 February =
2014 06:25<br><b>To:</b> David Harrington<br><b>Cc:</b> Adrian Farrel; =
MIB Doctors (E-mail)<br><b>Subject:</b> Re: [MIB-DOCTORS] Read-only MIB =
modules</span><span lang=3DEN-GB><o:p></o:p></span></p></div></div><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB>&nbsp;<o:p></o:p></span></p><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB>Hi,<o:p></o:p></span></p><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB>&nbsp;<o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB>I do not really know if an official statement to avoid SNMP =
Set is needed.<o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB>IMO the verdict is in wrt/ SNMP for =
configuration.<o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB>&nbsp;<o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB>It has been a long-held tradition in the IETF to let people =
flail in their own<o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB>sandbox if that's what they really wanted to do. =
&nbsp;Maybe that has been a<o:p></o:p></span></p></div><div><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB>mistake. Maybe WGs should be forced to prove that they have =
enough<o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB>real stakeholders willing to implement a spec, so that =
every part of<o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB>every proposed standard gets =
sponsored.<o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB>&nbsp;<o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB>We often presume that &quot;some vendors&quot;, who have =
had no interest in the<o:p></o:p></span></p></div><div><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB>work all along, will eventually come around and decide to =
implement.<o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB>Therefore there is no need to have strong interest in =
deployment during<o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB>the WG process.<o:p></o:p></span></p></div><div><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB>&nbsp;<o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB>Commitment to implementation should apply to everything -- =
protocols,<o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB>MIB modules, YANG modules --- it doesn't matter. No =
stakeholders,<o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB>no sandbox. &nbsp;That would be a radical change =
;-)<o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB>&nbsp;<o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB>&nbsp;<o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB>Andy<o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB>&nbsp;<o:p></o:p></span></p></div></div><div><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;margin-bottom:12.0pt'><span =
lang=3DEN-GB>&nbsp;<o:p></o:p></span></p><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB>On Sat, Feb 8, 2014 at 8:28 PM, David Harrington &lt;<a =
href=3D"mailto:ietfdbh@comcast.net" =
target=3D"_blank">ietfdbh@comcast.net</a>&gt; =
wrote:<o:p></o:p></span></p><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB>Hi,<o:p></o:p></span></p><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB>&nbsp;<o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB>I object to this statement. (Should I say =
&quot;strongly&quot; object, to show I mean =
business?<o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB>&nbsp;<o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB>There are many RW objects that can &quot;adjust&quot; a =
network configuration assuming SET is supported by the agent =
involved.<o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB>The NMS I used to work on, which helped determine and =
correct root cause for fault and performance problems, adjusted networks =
using writable MIB modules often.<o:p></o:p></span></p></div><div><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB>To tell WGs they should not develop RW MIB modules I think =
is wrong.<o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB>&nbsp;<o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB>I also have a concern with recommending Netconf/YANG at =
this point in time.<o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB>If we looked up the top ten router vendors using something =
like Gartner reports, how many of them really support configuration =
using Netconf with YANG in shipping =
products?<o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB>Ditto, the top ten switch =
vendors?<o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB>How many of them can be fully configured using YANG modules =
(not homegrown alternatives, but modules - standard or proprietary - =
written using the standards-compliant YANG =
language)?<o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB>I don't know the answer to that question, but would like to =
see some proof that YANG is at least as widely supported in currently =
shipping products as RW MIB objects.<o:p></o:p></span></p></div><div><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB>I think Netconf/YANG should compete in an open market with =
RW MIB modules, not try to stack the deck in their favor by =
&quot;strongly discouraging&quot; RW MIB =
standards.<o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB>&nbsp;<o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB>I have had discussions with vendors who are leaders in =
their particular networking niche, and they have told me they would not =
consider Netconf/YANG, because it has not been around long enough and =
been widely-enough deployed to prove stable for their production =
networks (whereas SNMP has enough track record to be known to be =
stable).<o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB>So I'm a bit concerned about telling WGs they should =
develop YANG modules rather than MIB =
modules.<o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB>And the current discussions of whether YANG 1.1 or 2.0 is =
needed to fix some problems with YANG 1.0, and it may not be backwards =
compatible, make me question the stability of =
YANG.<o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB>&nbsp;<o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB>Don't get me wrong. I support Netconf/YANG going forward, =
but I think it is important to provide advice that =
non-MIB-Doctors/non-YANG-experts can interpret =
reasonably.<o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB>Any such statement should make a clear distinction between =
&quot;configuration&quot; - the complete configuration of a device by =
Netconf - versus RW objects in a MIB - which can be used by SNMP to =
adjust network =
parameters/configuration.<o:p></o:p></span></p></div><div><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB>Telling people not to develop RW MIBs is throwing the baby =
out with the bathwater.<o:p></o:p></span></p></div><div><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB>We should NOT recommend against RW MIBs, because these can =
be used for more than (full device) =
configuration.<o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB>That point is far from clear in the currently proposed =
statement.<o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB>Maybe the statement should be that, if a vendor wants to =
replace their CLI, they should replace it with Netconf/YANG, and not =
with SNMP/RW-MIBs.&nbsp;<o:p></o:p></span></p></div><div><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB>That's probably a closer approximation &nbsp;of =
Netconf/YANG's applicability versus RW =
MIBs.&nbsp;<o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB>&nbsp;<o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB>In the past we have allowed implementations to make the =
conformance choice between supporting a MIB as RW, or implementing =
read-only.<o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB>If we advise WGs to not develop module with RW objects, =
then we take the choice away from the =
vendors.<o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB>I thick that would be a =
mistake.<o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB>&nbsp;<o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB>In &nbsp;addition, it is pointed out later in this thread =
that other SDOs use RW MIBs.&nbsp;<o:p></o:p></span></p></div><div><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB>Well, those MIBs produced by other SDOs (and for that =
matter, vendors) might require some support for specific RW objects in =
IETF MIB modules.<o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB>Therefore, I think it would be providing bad advice to say =
that IETF WGs should not produce MIB &nbsp;modules with RW objects in =
them.<o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB>&nbsp;<o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB>If Netconf/YANG becomes widely deployed, then NMS =
implementations and operators can choose whether to use YANG or SNMP (or =
their CLI) to adjust network =
configurations.<o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB>THat should not be a decision we make in the IETF, =
effectively forcing WGs to not develop MIBs with writable =
objects.<o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB>&nbsp;<o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB>Providing RW objects in MIB modules lets implementers and =
operators make the appropriate choice for their environments. (See RFC =
3365 for similar thinking vis-a-vis =
security.)<o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB>&nbsp;<o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB>dbh<o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB>&nbsp;<o:p></o:p></span></p><div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB>On Feb 4, 2014, at 8:32 AM, Adrian Farrel &lt;<a =
href=3D"mailto:adrian@olddog.co.uk" =
target=3D"_blank">adrian@olddog.co.uk</a>&gt; =
wrote:<o:p></o:p></span></p></div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;margin-bottom:12.0pt'><span =
lang=3DEN-GB><o:p>&nbsp;</o:p></span></p><div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;text-align:ju=
stify'><span lang=3DEN-GB =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Hi,</span><span lang=3DEN-GB><o:p></o:p></span></p><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;text-align:ju=
stify'><span lang=3DEN-GB =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;</span><span lang=3DEN-GB><o:p></o:p></span></p><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;text-align:ju=
stify'><span lang=3DEN-GB =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>The MPLS working group is testing the water to see whether one of its =
MIB modules should be &quot;reduced&quot; to read-only. This is the =
document that triggered my recent questions that led on to the draft =
advice you are working on. The WG took the document back to make this =
decision.</span><span lang=3DEN-GB><o:p></o:p></span></p><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;text-align:ju=
stify'><span lang=3DEN-GB =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;</span><span lang=3DEN-GB><o:p></o:p></span></p><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;text-align:ju=
stify'><span lang=3DEN-GB =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>You'll note below that we immediately have an implementation claim =
(not for this doc, but for the modules it extends).</span><span =
lang=3DEN-GB><o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;text-align:ju=
stify'><span lang=3DEN-GB =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;</span><span lang=3DEN-GB><o:p></o:p></span></p><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;text-align:ju=
stify'><span lang=3DEN-GB =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>An interesting situation, I think.</span><span =
lang=3DEN-GB><o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;text-align:ju=
stify'><span lang=3DEN-GB =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;</span><span lang=3DEN-GB><o:p></o:p></span></p><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;text-align:ju=
stify'><span lang=3DEN-GB =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>A</span><span lang=3DEN-GB><o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;text-align:ju=
stify'><span lang=3DEN-GB =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;</span><span lang=3DEN-GB><o:p></o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>&nbsp;mpls =
[mailto:<a href=3D"mailto:mpls-" target=3D"_blank">mpls-</a><a =
href=3D"mailto:bounces@ietf.org" target=3D"_blank"><span =
style=3D'color:#954F72'>bounces@ietf.org</span></a>]&nbsp;<b>On Behalf =
Of&nbsp;</b>GyeRok Gwun (???)<br><b>Sent:</b>&nbsp;04 February 2014 =
09:57<br><b>To:</b>&nbsp;'<a href=3D"mailto:mpls@ietf.org" =
target=3D"_blank"><span =
style=3D'color:#954F72'>mpls@ietf.org</span></a>'<br><b>Cc:</b>&nbsp;'<a =
href=3D"mailto:mpls-chairs@tools.ietf.org" target=3D"_blank"><span =
style=3D'color:#954F72'>mpls-chairs@tools.ietf.org</span></a>'; '<a =
href=3D"mailto:draft-ietf-mpls-tp-te-mib@tools.ietf.org" =
target=3D"_blank"><span =
style=3D'color:#954F72'>draft-ietf-mpls-tp-te-mib@tools.ietf.org</span></=
a>'<br><b>Subject:</b>&nbsp;Re: [mpls] seeking consensus on making =
draft-ietf-mpls-tp-te-mib read- only</span><span =
lang=3DEN-GB><o:p></o:p></span></p></div></div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;word-break:br=
eak-all'><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:"Malgun =
Gothic","sans-serif"'>&nbsp;</span><span =
lang=3DEN-GB><o:p></o:p></span></p><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;word-break:br=
eak-all'><span style=3D'font-size:10.0pt;font-family:"Courier =
New"'>No/oppose to make as Read-only mib.</span><span =
lang=3DEN-GB><o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;word-break:br=
eak-all'><span style=3D'font-size:10.0pt;font-family:"Courier New"'>In =
our products we extensively use R/W object of TE mib. We also have =
NMS/EMS that use TE read-write Objects</span><span =
lang=3DEN-GB><o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;word-break:br=
eak-all'><span style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;</span><span =
lang=3DEN-GB><o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;word-break:br=
eak-all'><span style=3D'font-size:10.0pt;font-family:"Courier New"'>Best =
Regards</span><span lang=3DEN-GB><o:p></o:p></span></p></div><div><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;word-break:br=
eak-all'><span style=3D'font-size:10.0pt;font-family:"Courier =
New"'>Gwun</span><span lang=3DEN-GB><o:p></o:p></span></p></div><div><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;word-break:br=
eak-all'><span style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;</span><span =
lang=3DEN-GB><o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;word-break:br=
eak-all'><span style=3D'font-size:10.0pt;font-family:"Courier =
New"'>-----Original Message-----</span><span =
lang=3DEN-GB><o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;word-break:br=
eak-all'><span style=3D'font-size:10.0pt;font-family:"Courier =
New"'>From: mpls [<a href=3D"mailto:mpls-bounces@ietf.org" =
target=3D"_blank"><span =
style=3D'color:#954F72'>mailto:mpls-bounces@ietf.org</span></a>] On =
Behalf Of Loa Andersson</span><span =
lang=3DEN-GB><o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;word-break:br=
eak-all'><span style=3D'font-size:10.0pt;font-family:"Courier =
New"'>Sent: Monday, February 03, 2014 10:55 PM</span><span =
lang=3DEN-GB><o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;word-break:br=
eak-all'><span style=3D'font-size:10.0pt;font-family:"Courier =
New"'>To:&nbsp;<a href=3D"mailto:mpls@ietf.org" target=3D"_blank"><span =
style=3D'color:#954F72'>mpls@ietf.org</span></a></span><span =
lang=3DEN-GB><o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;word-break:br=
eak-all'><span style=3D'font-size:10.0pt;font-family:"Courier =
New"'>Cc:&nbsp;<a href=3D"mailto:mpls-chairs@tools.ietf.org" =
target=3D"_blank"><span =
style=3D'color:#954F72'>mpls-chairs@tools.ietf.org</span></a>;&nbsp;<a =
href=3D"mailto:draft-ietf-mpls-tp-te-mib@tools.ietf.org" =
target=3D"_blank"><span =
style=3D'color:#954F72'>draft-ietf-mpls-tp-te-mib@tools.ietf.org</span></=
a></span><span lang=3DEN-GB><o:p></o:p></span></p></div><div><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;word-break:br=
eak-all'><span style=3D'font-size:10.0pt;font-family:"Courier =
New"'>Subject: [mpls] seeking consensus on making =
draft-ietf-mpls-tp-te-mib read- only</span><span =
lang=3DEN-GB><o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;word-break:br=
eak-all'><span style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;</span><span =
lang=3DEN-GB><o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;word-break:br=
eak-all'><span style=3D'font-size:10.0pt;font-family:"Courier =
New"'>Working Group,</span><span =
lang=3DEN-GB><o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;word-break:br=
eak-all'><span style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;</span><span =
lang=3DEN-GB><o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;word-break:br=
eak-all'><span style=3D'font-size:10.0pt;font-family:"Courier New"'>We =
have just recalled draft-ietf-mpls-tp-te-mib from the IESG to the =
working group for more work. We have a series of comments that are =
mostly for clarification. However the main reason for recalling the =
document is that there is one point where we need to confirm working =
group consensus.</span><span =
lang=3DEN-GB><o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;word-break:br=
eak-all'><span style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;</span><span =
lang=3DEN-GB><o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;word-break:br=
eak-all'><span style=3D'font-size:10.0pt;font-family:"Courier New"'>The =
IETF, the working group and the MIB Doctors are today very reluctant to =
produce read-write MIB modules. The current draft is read-write for a =
few objects, this is based on a consensus call for an earlier =
discussion, however the consensus call was not clear. It can be taken to =
mean both that we want to go with read-write objects and that we want to =
see read-only. Is it clear that it has been interpreted differently by =
different individuals.</span><span =
lang=3DEN-GB><o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;word-break:br=
eak-all'><span style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;</span><span =
lang=3DEN-GB><o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;word-break:br=
eak-all'><span style=3D'font-size:10.0pt;font-family:"Courier New"'>The =
authors and chairs have discussed the issue and we have a rough =
consensus that we want the MIB module(s) to be read-only.</span><span =
lang=3DEN-GB><o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;word-break:br=
eak-all'><span style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;</span><span =
lang=3DEN-GB><o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;word-break:br=
eak-all'><span style=3D'font-size:10.0pt;font-family:"Courier New"'>We =
therefore are asking the working group if this is OK for the =
MIB</span><span lang=3DEN-GB><o:p></o:p></span></p></div><div><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;word-break:br=
eak-all'><span style=3D'font-size:10.0pt;font-family:"Courier =
New"'>module(s) in the current document. Please indicate Support or =
Oppose for this MIB (draft-ietf-mpls-tp-te-mib) to be =
read-only.</span><span lang=3DEN-GB><o:p></o:p></span></p></div><div><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;word-break:br=
eak-all'><span style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;</span><span =
lang=3DEN-GB><o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;word-break:br=
eak-all'><span style=3D'font-size:10.0pt;font-family:"Courier =
New"'>Please send your comments to the working group mailing list before =
February 18, 2014.</span><span =
lang=3DEN-GB><o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;word-break:br=
eak-all'><span style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;</span><span =
lang=3DEN-GB><o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;word-break:br=
eak-all'><span style=3D'font-size:10.0pt;font-family:"Courier =
New"'>Loa</span><span lang=3DEN-GB><o:p></o:p></span></p></div><div><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;word-break:br=
eak-all'><span style=3D'font-size:10.0pt;font-family:"Courier New"'>for =
the MPLS wg chairs</span><span =
lang=3DEN-GB><o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;word-break:br=
eak-all'><span style=3D'font-size:10.0pt;font-family:"Courier =
New"'>--</span><span lang=3DEN-GB><o:p></o:p></span></p></div><div><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;word-break:br=
eak-all'><span style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;</span><span =
lang=3DEN-GB><o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;word-break:br=
eak-all'><span style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;</span><span =
lang=3DEN-GB><o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;word-break:br=
eak-all'><span style=3D'font-size:10.0pt;font-family:"Courier New"'>Loa =
Andersson&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
; email:&nbsp;<a href=3D"mailto:loa@mail01.huawei.com" =
target=3D"_blank"><span =
style=3D'color:#954F72'>loa@mail01.huawei.com</span></a></span><span =
lang=3DEN-GB><o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;word-break:br=
eak-all'><span style=3D'font-size:10.0pt;font-family:"Courier =
New"'>Senior MPLS =
Expert&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;<a href=3D"mailto:loa@pi.nu" target=3D"_blank"><span =
style=3D'color:#954F72'>loa@pi.nu</span></a></span><span =
lang=3DEN-GB><o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;word-break:br=
eak-all'><span style=3D'font-size:10.0pt;font-family:"Courier =
New"'>Huawei Technologies (consultant)&nbsp;&nbsp;&nbsp;&nbsp; phone: =
+46 739 81 21 64</span><span =
lang=3DEN-GB><o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;word-break:br=
eak-all'><span style=3D'font-size:10.0pt;font-family:"Courier =
New"'>_______________________________________________</span><span =
lang=3DEN-GB><o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;word-break:br=
eak-all'><span style=3D'font-size:10.0pt;font-family:"Courier New"'>mpls =
mailing list</span><span =
lang=3DEN-GB><o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;word-break:br=
eak-all'><span style=3D'font-size:10.0pt;font-family:"Courier New"'><a =
href=3D"mailto:mpls@ietf.org" target=3D"_blank"><span =
style=3D'color:#954F72'>mpls@ietf.org</span></a></span><span =
lang=3DEN-GB><o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;word-break:br=
eak-all'><span style=3D'font-size:10.0pt;font-family:"Courier New"'><a =
href=3D"https://www.ietf.org/mailman/listinfo/mpls" =
target=3D"_blank"><span =
style=3D'color:#954F72'>https://www.ietf.org/mailman/listinfo/mpls</span>=
</a></span><span lang=3DEN-GB><o:p></o:p></span></p></div><div><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;word-break:br=
eak-all'><span style=3D'font-size:10.0pt;font-family:"Courier =
New"'>_______________________________________________</span><span =
lang=3DEN-GB><o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;word-break:br=
eak-all'><span style=3D'font-size:10.0pt;font-family:"Courier New"'>mpls =
mailing list</span><span =
lang=3DEN-GB><o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;word-break:br=
eak-all'><span style=3D'font-size:10.0pt;font-family:"Courier New"'><a =
href=3D"mailto:mpls@ietf.org" target=3D"_blank"><span =
style=3D'color:#954F72'>mpls@ietf.org</span></a></span><span =
lang=3DEN-GB><o:p></o:p></span></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;word-break:br=
eak-all'><span style=3D'font-size:10.0pt;font-family:"Courier New"'><a =
href=3D"https://www.ietf.org/mailman/listinfo/mpls" =
target=3D"_blank"><span =
style=3D'color:#954F72'>https://www.ietf.org/mailman/listinfo/mpls</span>=
</a></span><span lang=3DEN-GB><o:p></o:p></span></p></div><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;text-align:ju=
stify;word-break:break-all'><span =
style=3D'font-size:10.0pt;font-family:"Malgun =
Gothic","sans-serif"'>&nbsp;</span><span =
lang=3DEN-GB><o:p></o:p></span></p></div></div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB =
style=3D'font-size:13.5pt;font-family:"Helvetica","sans-serif"'>_________=
______________________________________<br>MIB-DOCTORS mailing list<br><a =
href=3D"mailto:MIB-DOCTORS@ietf.org" target=3D"_blank"><span =
style=3D'color:#954F72'>MIB-DOCTORS@ietf.org</span></a><br><a =
href=3D"https://www.ietf.org/mailman/listinfo/mib-doctors" =
target=3D"_blank"><span =
style=3D'color:#954F72'>https://www.ietf.org/mailman/listinfo/mib-doctors=
</span></a></span><span =
lang=3DEN-GB><o:p></o:p></span></p></div></div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB>&nbsp;<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;margin-bottom:12.0pt'><span =
lang=3DEN-GB><br>_______________________________________________<br>MIB-D=
OCTORS 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"_blank">https://www.ietf.org/mailman/listinfo/mib-doctors</a><o=
:p></o:p></span></p></div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB>&nbsp;<o:p></o:p></span></p></div></div></div></blockquote><=
/div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div><p =
class=3DMsoNormal>_______________________________________________<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">https://www.ie=
tf.org/mailman/listinfo/mib-doctors</a><o:p></o:p></p></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div></body></html>
------=_NextPart_000_00D4_01CF33DF.67805160--


From nobody Thu Feb 27 15:52:39 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 8D56E1A068D for <mib-doctors@ietfa.amsl.com>; Thu, 27 Feb 2014 15:52:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Level: 
X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 SMDAFsteAMQU for <mib-doctors@ietfa.amsl.com>; Thu, 27 Feb 2014 15:52:26 -0800 (PST)
Received: from mail-qa0-f53.google.com (mail-qa0-f53.google.com [209.85.216.53]) by ietfa.amsl.com (Postfix) with ESMTP id 6F8E41A02B3 for <mib-doctors@ietf.org>; Thu, 27 Feb 2014 15:52:26 -0800 (PST)
Received: by mail-qa0-f53.google.com with SMTP id cm18so4736651qab.26 for <mib-doctors@ietf.org>; Thu, 27 Feb 2014 15:52:24 -0800 (PST)
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=SFNC7B/H2FGJGsxq+W88jQKfxxs4H0RuS05U7WoV1Cc=; b=NmJ4Vnoydq6kmIVCepNh5wVnZ2TmK36TkS+9f8DYV9ToJGU6It/ERq4nCNNCjdImg4 egad+eFpIX14zQndxTXshvW9xgMnyqqrP6K7EVdtyo5hnjAkJL0u7Fm2ReDcyg8k4ZBB bxnuMXh/qtEpLe61ZL/zsoiHuyr57Vy/O6ORLQV5mkWAKipGsD9C/DDYVIl0L+N4h8mH vCPFcN7k6M3YcGHLhmQtsY3hBo+oS25dIeNCtFXyIQCwz63TrAY95oohwarjJj2hj/oJ w4Ztknnlo473/XE9n730VpYSaijvNHV7/aHRVLmehJzSHmnNEFZh35D9DHr/+6lsmPo2 71Aw==
X-Gm-Message-State: ALoCoQkUyOVunVecz1I8HL/7zxXmIQfxiNWsuBVVzA0art5wprpj1S2NsuzB0/nhPQQHumK7kWR9
MIME-Version: 1.0
X-Received: by 10.224.79.19 with SMTP id n19mr20619398qak.99.1393545144549; Thu, 27 Feb 2014 15:52:24 -0800 (PST)
Received: by 10.140.104.194 with HTTP; Thu, 27 Feb 2014 15:52:24 -0800 (PST)
In-Reply-To: <00d301cf3409$504f7b90$f0ee72b0$@comcast.net>
References: <05c501cf21ad$80d97ef0$828c7cd0$@olddog.co.uk> <7D263081-6D84-4AA2-B0CB-FA74793BD135@comcast.net> <CABCOCHT3UCVmpLcEAH2Q3mrfbWMxh=c7FZ4d61pAmpwb8t-sug@mail.gmail.com> <00d601cf25b3$371c77e0$a55567a0$@olddog.co.uk> <CABCOCHQJsBy8DvPEOy-b1Xs-MWzfgZCwWtWjrpngHLeicMAefA@mail.gmail.com> <A41519E1-DE8A-4B0C-B421-45B5D42BA2C7@lucidvision.com> <00d301cf3409$504f7b90$f0ee72b0$@comcast.net>
Date: Thu, 27 Feb 2014 15:52:24 -0800
Message-ID: <CABCOCHTKkKXbLVdd9jAnbaf6W3u3657ShmVNxCVu7CP9V+mepA@mail.gmail.com>
From: Andy Bierman <andy@yumaworks.com>
To: David Harrington <dbharrington@comcast.net>
Content-Type: multipart/alternative; boundary=047d7bdc804051d18f04f36c03dc
Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/tiHcP0slwNJRk9rRy1LbYD7548k
Cc: "MIB Doctors \(E-mail\)" <mib-doctors@ietf.org>, Farrel Adrian <adrian@olddog.co.uk>
Subject: Re: [MIB-DOCTORS] Read-only MIB modules
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, 27 Feb 2014 23:52:37 -0000

--047d7bdc804051d18f04f36c03dc
Content-Type: text/plain; charset=ISO-8859-1

On Thu, Feb 27, 2014 at 2:14 PM, David Harrington
<dbharrington@comcast.net>wrote:

> "WG groups can then decide
>
> if they have enough participants who plan on implementing read-create.
>
> If not, then they can't have it.  The MIB gets rejected and sent back
>
> to the WG if it contains any MIN-ACCESS clauses.
>
> "
>
> So why should rw mibs be held to a higher standard than other IETF
> proposed standards?
>
>
>


They should not, but if industry does not implement read-write MIB modules,
then the IETF should really ask itself why it is wasting so many volunteer
resources to produce these RFCs.

If the answer is "volunteers are free" so who cares if they do work
that nobody uses, then that is a valid answer I suppose, but not
one that will inspire more people to volunteer.


Andy

David Harrington
>
> dbharrington@comcast.net
>
> +1-603-828-1401
>
> *From:* MIB-DOCTORS [mailto:mib-doctors-bounces@ietf.org] *On Behalf Of *Thomas
> Nadeau
> *Sent:* Wednesday, February 26, 2014 5:41 PM
> *To:* Andy Bierman
> *Cc:* Farrel Adrian; MIB Doctors (E-mail)
> *Subject:* Re: [MIB-DOCTORS] Read-only MIB modules
>
>
>
>
>
> On Feb 9, 2014:12:23 PM, at 12:23 PM, Andy Bierman <andy@yumaworks.com>
> wrote:
>
>
>
>
>
>
>
> On Sun, Feb 9, 2014 at 8:23 AM, Adrian Farrel <adrian@olddog.co.uk> wrote:
>
> Andy,
>
>
>
> I am all in favour of flailing in sandboxes as a way to burn off that
> excess energy caused by high-tartrazine diets.
>
>
>
> However, I think SNMP Set is showing up because people are putting
> together MIB modules sans clue. They genuinely want to be helpful in the
> construction of MIB modules that might have value, but they don't know how
> to do it and no-one else in their immediate circle does either.
>
>
>
> The consequence, beyond a spec that might or might not get implemented in
> full, is that the MIB doctors have to do reviews of function they don't
> believe has value.
>
>
>
>
>
>
>
> The IESG and IETF have to reviews these documents as well.
>
> I think people writing MIB modules know how to do it, but they are
>
> following a formula setup by the IESG and blessed by MIB Doctors.
>
>
>
> MIB authors seem encouraged to use read-create objects, but then
>
> add MIN-ACCESS read-only in the conformance statement,
>
> just in case anybody ever wants to implement the MAX-ACCESS.
>
>
>
> Time to face the fact that nobody is implementing the MAX-ACCESS.
>
> In order to claim conformance to a MIB module, it should be
>
> without this MIB-ACCESS loophole.  WG groups can then decide
>
> if they have enough participants who plan on implementing read-create.
>
> If not, then they can't have it.  The MIB gets rejected and sent back
>
> to the WG if it contains any MIN-ACCESS clauses.
>
>
>
>           And hence my point about wasting time of those resources
> writing those min-access statements (and conformance clauses). That stuff
> is non-trivial, nor is getting row construction ordering/etc... details
> right.  And then its all for nothing because as you rightly said, nearly no
> one is using it.
>
>
>
>           --Tom
>
>
>
>
>
>
>
>
>
> Andy
>
>
>
>
>
>
>
>
>
>
>
> A
>
>
>
>
>
> *From:* Andy Bierman [mailto:andy@yumaworks.com]
> *Sent:* 09 February 2014 06:25
> *To:* David Harrington
> *Cc:* Adrian Farrel; MIB Doctors (E-mail)
> *Subject:* Re: [MIB-DOCTORS] Read-only MIB modules
>
>
>
> Hi,
>
>
>
> I do not really know if an official statement to avoid SNMP Set is needed.
>
> IMO the verdict is in wrt/ SNMP for configuration.
>
>
>
> It has been a long-held tradition in the IETF to let people flail in their
> own
>
> sandbox if that's what they really wanted to do.  Maybe that has been a
>
> mistake. Maybe WGs should be forced to prove that they have enough
>
> real stakeholders willing to implement a spec, so that every part of
>
> every proposed standard gets sponsored.
>
>
>
> We often presume that "some vendors", who have had no interest in the
>
> work all along, will eventually come around and decide to implement.
>
> Therefore there is no need to have strong interest in deployment during
>
> the WG process.
>
>
>
> Commitment to implementation should apply to everything -- protocols,
>
> MIB modules, YANG modules --- it doesn't matter. No stakeholders,
>
> no sandbox.  That would be a radical change ;-)
>
>
>
>
>
> Andy
>
>
>
>
>
> On Sat, Feb 8, 2014 at 8:28 PM, David Harrington <ietfdbh@comcast.net>
> wrote:
>
> Hi,
>
>
>
> I object to this statement. (Should I say "strongly" object, to show I
> mean business?
>
>
>
> There are many RW objects that can "adjust" a network configuration
> assuming SET is supported by the agent involved.
>
> The NMS I used to work on, which helped determine and correct root cause
> for fault and performance problems, adjusted networks using writable MIB
> modules often.
>
> To tell WGs they should not develop RW MIB modules I think is wrong.
>
>
>
> I also have a concern with recommending Netconf/YANG at this point in time.
>
> If we looked up the top ten router vendors using something like Gartner
> reports, how many of them really support configuration using Netconf with
> YANG in shipping products?
>
> Ditto, the top ten switch vendors?
>
> How many of them can be fully configured using YANG modules (not homegrown
> alternatives, but modules - standard or proprietary - written using the
> standards-compliant YANG language)?
>
> I don't know the answer to that question, but would like to see some proof
> that YANG is at least as widely supported in currently shipping products as
> RW MIB objects.
>
> I think Netconf/YANG should compete in an open market with RW MIB modules,
> not try to stack the deck in their favor by "strongly discouraging" RW MIB
> standards.
>
>
>
> I have had discussions with vendors who are leaders in their particular
> networking niche, and they have told me they would not consider
> Netconf/YANG, because it has not been around long enough and been
> widely-enough deployed to prove stable for their production networks
> (whereas SNMP has enough track record to be known to be stable).
>
> So I'm a bit concerned about telling WGs they should develop YANG modules
> rather than MIB modules.
>
> And the current discussions of whether YANG 1.1 or 2.0 is needed to fix
> some problems with YANG 1.0, and it may not be backwards compatible, make
> me question the stability of YANG.
>
>
>
> Don't get me wrong. I support Netconf/YANG going forward, but I think it
> is important to provide advice that non-MIB-Doctors/non-YANG-experts can
> interpret reasonably.
>
> Any such statement should make a clear distinction between "configuration"
> - the complete configuration of a device by Netconf - versus RW objects in
> a MIB - which can be used by SNMP to adjust network
> parameters/configuration.
>
> Telling people not to develop RW MIBs is throwing the baby out with the
> bathwater.
>
> We should NOT recommend against RW MIBs, because these can be used for
> more than (full device) configuration.
>
> That point is far from clear in the currently proposed statement.
>
> Maybe the statement should be that, if a vendor wants to replace their
> CLI, they should replace it with Netconf/YANG, and not with SNMP/RW-MIBs.
>
> That's probably a closer approximation  of Netconf/YANG's applicability
> versus RW MIBs.
>
>
>
> In the past we have allowed implementations to make the conformance choice
> between supporting a MIB as RW, or implementing read-only.
>
> If we advise WGs to not develop module with RW objects, then we take the
> choice away from the vendors.
>
> I thick that would be a mistake.
>
>
>
> In  addition, it is pointed out later in this thread that other SDOs use
> RW MIBs.
>
> Well, those MIBs produced by other SDOs (and for that matter, vendors)
> might require some support for specific RW objects in IETF MIB modules.
>
> Therefore, I think it would be providing bad advice to say that IETF WGs
> should not produce MIB  modules with RW objects in them.
>
>
>
> If Netconf/YANG becomes widely deployed, then NMS implementations and
> operators can choose whether to use YANG or SNMP (or their CLI) to adjust
> network configurations.
>
> THat should not be a decision we make in the IETF, effectively forcing WGs
> to not develop MIBs with writable objects.
>
>
>
> Providing RW objects in MIB modules lets implementers and operators make
> the appropriate choice for their environments. (See RFC 3365 for similar
> thinking vis-a-vis security.)
>
>
>
> dbh
>
>
>
> On Feb 4, 2014, at 8:32 AM, Adrian Farrel <adrian@olddog.co.uk> wrote:
>
>
>
> Hi,
>
>
>
> The MPLS working group is testing the water to see whether one of its MIB
> modules should be "reduced" to read-only. This is the document that
> triggered my recent questions that led on to the draft advice you are
> working on. The WG took the document back to make this decision.
>
>
>
> You'll note below that we immediately have an implementation claim (not
> for this doc, but for the modules it extends).
>
>
>
> An interesting situation, I think.
>
>
>
> A
>
>
>
> *From:* mpls [mailto:mpls-bounces@ietf.org] *On Behalf Of *GyeRok Gwun
> (???)
> *Sent:* 04 February 2014 09:57
> *To:* 'mpls@ietf.org'
> *Cc:* 'mpls-chairs@tools.ietf.org'; '
> draft-ietf-mpls-tp-te-mib@tools.ietf.org'
> *Subject:* Re: [mpls] seeking consensus on making
> draft-ietf-mpls-tp-te-mib read- only
>
>
>
> No/oppose to make as Read-only mib.
>
> In our products we extensively use R/W object of TE mib. We also have
> NMS/EMS that use TE read-write Objects
>
>
>
> Best Regards
>
> Gwun
>
>
>
> -----Original Message-----
>
> From: mpls [mailto:mpls-bounces@ietf.org <mpls-bounces@ietf.org>] On
> Behalf Of Loa Andersson
>
> Sent: Monday, February 03, 2014 10:55 PM
>
> To: mpls@ietf.org
>
> Cc: mpls-chairs@tools.ietf.org; draft-ietf-mpls-tp-te-mib@tools.ietf.org
>
> Subject: [mpls] seeking consensus on making draft-ietf-mpls-tp-te-mib
> read- only
>
>
>
> Working Group,
>
>
>
> We have just recalled draft-ietf-mpls-tp-te-mib from the IESG to the
> working group for more work. We have a series of comments that are mostly
> for clarification. However the main reason for recalling the document is
> that there is one point where we need to confirm working group consensus.
>
>
>
> The IETF, the working group and the MIB Doctors are today very reluctant
> to produce read-write MIB modules. The current draft is read-write for a
> few objects, this is based on a consensus call for an earlier discussion,
> however the consensus call was not clear. It can be taken to mean both that
> we want to go with read-write objects and that we want to see read-only. Is
> it clear that it has been interpreted differently by different individuals.
>
>
>
> The authors and chairs have discussed the issue and we have a rough
> consensus that we want the MIB module(s) to be read-only.
>
>
>
> We therefore are asking the working group if this is OK for the MIB
>
> module(s) in the current document. Please indicate Support or Oppose for
> this MIB (draft-ietf-mpls-tp-te-mib) to be read-only.
>
>
>
> Please send your comments to the working group mailing list before
> February 18, 2014.
>
>
>
> Loa
>
> for the MPLS wg chairs
>
> --
>
>
>
>
>
> Loa Andersson                        email: loa@mail01.huawei.com
>
> Senior MPLS Expert                          loa@pi.nu
>
> Huawei Technologies (consultant)     phone: +46 739 81 21 64
>
> _______________________________________________
>
> mpls mailing list
>
> mpls@ietf.org
>
> https://www.ietf.org/mailman/listinfo/mpls
>
> _______________________________________________
>
> mpls mailing list
>
> mpls@ietf.org
>
> https://www.ietf.org/mailman/listinfo/mpls
>
>
>
> _______________________________________________
> 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
>
>
>
>
>
> _______________________________________________
> MIB-DOCTORS mailing list
> MIB-DOCTORS@ietf.org
> https://www.ietf.org/mailman/listinfo/mib-doctors
>
>
>

--047d7bdc804051d18f04f36c03dc
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, Feb 27, 2014 at 2:14 PM, David Harrington <span dir=3D"ltr"=
>&lt;<a href=3D"mailto:dbharrington@comcast.net" target=3D"_blank">dbharrin=
gton@comcast.net</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 lang=3D"EN-US" link=3D"blue" vlink=3D"p=
urple"><div><p class=3D"MsoNormal"><a name=3D"144756a04ee3eb19__MailEndComp=
ose"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;=
sans-serif&quot;;color:#1f497d">&ldquo;</span></a>WG groups can then decide=
<u></u><u></u></p>
<p class=3D"MsoNormal">if they have enough participants who plan on impleme=
nting read-create.<u></u><u></u></p><p class=3D"MsoNormal">If not, then the=
y can&#39;t have it. &nbsp;The MIB gets rejected and sent back<u></u><u></u=
></p>
<p class=3D"MsoNormal">to the WG if it contains any MIN-ACCESS clauses.<u><=
/u><u></u></p><p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-f=
amily:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">&ldquo;<u><=
/u><u></u></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">So why should rw mibs be =
held to a higher standard than other IETF proposed standards?<u></u><u></u>=
</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"><u></u>&nbsp;</span></p><=
/div></div></blockquote><div><br></div><div><br></div><div>They should not,=
 but if industry does not implement read-write MIB modules,</div>
<div>then the IETF should really ask itself why it is wasting so many volun=
teer</div><div>resources to produce these RFCs.</div><div><br></div><div>If=
 the answer is &quot;volunteers are free&quot; so who cares if they do work=
</div>
<div>that nobody uses, then that is a valid answer I suppose, but not</div>=
<div>one that will inspire more people to volunteer.</div><div><br></div><d=
iv><br></div><div>Andy</div><div><br></div><blockquote class=3D"gmail_quote=
" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple"><div><p class=3D"MsoNorm=
al"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;s=
ans-serif&quot;;color:#1f497d"><u></u></span></p><div><p class=3D"MsoNormal=
"><span style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-=
serif&quot;;color:#1f497d">David Harrington</span><span style=3D"color:#1f4=
97d"><u></u><u></u></span></p>
<p class=3D"MsoNormal"><a href=3D"mailto:dbharrington@comcast.net" target=
=3D"_blank"><span style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&=
quot;sans-serif&quot;">dbharrington@comcast.net</span></a><span style=3D"co=
lor:#1f497d"><u></u><u></u></span></p>
</div><p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&q=
uot;Arial&quot;,&quot;sans-serif&quot;;color:#1f497d">+1-603-828-1401</span=
><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans=
-serif&quot;;color:#1f497d"><u></u><u></u></span></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt"><div><div style=3D"border:none;border-top:solid #b5c4df 1.0pt;paddin=
g:3.0pt 0in 0in 0in"><p class=3D"MsoNormal"><b><span style=3D"font-size:10.=
0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b>=
<span style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-s=
erif&quot;"> MIB-DOCTORS [mailto:<a href=3D"mailto:mib-doctors-bounces@ietf=
.org" target=3D"_blank">mib-doctors-bounces@ietf.org</a>] <b>On Behalf Of <=
/b>Thomas Nadeau<br>
<b>Sent:</b> Wednesday, February 26, 2014 5:41 PM<br><b>To:</b> Andy Bierma=
n<br><b>Cc:</b> Farrel Adrian; MIB Doctors (E-mail)<br><b>Subject:</b> Re: =
[MIB-DOCTORS] Read-only MIB modules<u></u><u></u></span></p></div></div>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p><p class=3D"MsoNormal"><u></=
u>&nbsp;<u></u></p><div><div><p class=3D"MsoNormal">On Feb 9, 2014:12:23 PM=
, at 12:23 PM, Andy Bierman &lt;<a href=3D"mailto:andy@yumaworks.com" targe=
t=3D"_blank">andy@yumaworks.com</a>&gt; wrote:<u></u><u></u></p>
</div><p class=3D"MsoNormal"><br><br><u></u><u></u></p><div><p class=3D"Mso=
Normal"><u></u>&nbsp;<u></u></p><div><p class=3D"MsoNormal" style=3D"margin=
-bottom:12.0pt"><u></u>&nbsp;<u></u></p><div><p class=3D"MsoNormal">On Sun,=
 Feb 9, 2014 at 8:23 AM, Adrian Farrel &lt;<a href=3D"mailto:adrian@olddog.=
co.uk" target=3D"_blank">adrian@olddog.co.uk</a>&gt; wrote:<u></u><u></u></=
p>
<div><p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"font-size:11.0pt;=
font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">Andy,=
</span><span lang=3D"EN-GB"><u></u><u></u></span></p><p class=3D"MsoNormal"=
><span lang=3D"EN-GB" style=3D"font-size:11.0pt;font-family:&quot;Calibri&q=
uot;,&quot;sans-serif&quot;;color:#1f497d">&nbsp;</span><span lang=3D"EN-GB=
"><u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">I am all i=
n favour of flailing in sandboxes as a way to burn off that excess energy c=
aused by high-tartrazine diets.</span><span lang=3D"EN-GB"><u></u><u></u></=
span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">&nbsp;</sp=
an><span lang=3D"EN-GB"><u></u><u></u></span></p><p class=3D"MsoNormal"><sp=
an lang=3D"EN-GB" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;=
,&quot;sans-serif&quot;;color:#1f497d">However, I think SNMP Set is showing=
 up because people are putting together MIB modules sans clue. They genuine=
ly want to be helpful in the construction of MIB modules that might have va=
lue, but they don&#39;t know how to do it and no-one else in their immediat=
e circle does either.</span><span lang=3D"EN-GB"><u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">&nbsp;</sp=
an><span lang=3D"EN-GB"><u></u><u></u></span></p><p class=3D"MsoNormal"><sp=
an lang=3D"EN-GB" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;=
,&quot;sans-serif&quot;;color:#1f497d">The consequence, beyond a spec that =
might or might not get implemented in full, is that the MIB doctors have to=
 do reviews of function they don&#39;t believe has value.</span><span lang=
=3D"EN-GB"><u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><u></u>&nbsp;<u></u></span></p>=
</div><div><p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p></div><div><p cla=
ss=3D"MsoNormal"><u></u>&nbsp;<u></u></p></div><div><p class=3D"MsoNormal">=
The IESG and IETF have to reviews these documents as well.<u></u><u></u></p=
>
</div><div><p class=3D"MsoNormal">I think people writing MIB modules know h=
ow to do it, but they are<u></u><u></u></p></div><div><p class=3D"MsoNormal=
">following a formula setup by the IESG and blessed by MIB Doctors.<u></u><=
u></u></p>
</div><div><p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p></div><div><p cla=
ss=3D"MsoNormal">MIB authors seem encouraged to use read-create objects, bu=
t then<u></u><u></u></p></div><div><p class=3D"MsoNormal">add MIN-ACCESS re=
ad-only in the conformance statement,<u></u><u></u></p>
</div><div><p class=3D"MsoNormal">just in case anybody ever wants to implem=
ent the MAX-ACCESS.<u></u><u></u></p></div><div><p class=3D"MsoNormal"><u><=
/u>&nbsp;<u></u></p></div><div><p class=3D"MsoNormal">Time to face the fact=
 that nobody is implementing the MAX-ACCESS.<u></u><u></u></p>
</div><div><p class=3D"MsoNormal">In order to claim conformance to a MIB mo=
dule, it should be<u></u><u></u></p></div><div><p class=3D"MsoNormal">witho=
ut this MIB-ACCESS loophole. &nbsp;WG groups can then decide<u></u><u></u><=
/p></div>
<div><p class=3D"MsoNormal">if they have enough participants who plan on im=
plementing read-create.<u></u><u></u></p></div><div><p class=3D"MsoNormal">=
If not, then they can&#39;t have it. &nbsp;The MIB gets rejected and sent b=
ack<u></u><u></u></p>
</div><div><p class=3D"MsoNormal">to the WG if it contains any MIN-ACCESS c=
lauses.<u></u><u></u></p></div></div></div></div><div><p class=3D"MsoNormal=
"><u></u>&nbsp;<u></u></p></div><p class=3D"MsoNormal"><span>&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span>And hence my point about wa=
sting time of those resources writing those min-access statements (and conf=
ormance clauses). That stuff is non-trivial, nor is getting row constructio=
n ordering/etc... details right. &nbsp;And then its all for nothing because=
 as you rightly said, nearly no one is using it.&nbsp;<u></u><u></u></p>
</div><div><p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p></div><div><p cla=
ss=3D"MsoNormal"><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p; </span>--Tom<u></u><u></u></p></div><div><p class=3D"MsoNormal"><u></u>&=
nbsp;<u></u></p></div><div><p class=3D"MsoNormal"><br><br><u></u><u></u></p=
>
<div><div><div><div><p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p></div><d=
iv><p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p></div><div><p class=3D"Ms=
oNormal">Andy<u></u><u></u></p></div><div><p class=3D"MsoNormal"><u></u>&nb=
sp;<u></u></p></div>
<div><p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p></div><div><p class=3D"=
MsoNormal"><u></u>&nbsp;<u></u></p></div><div><p class=3D"MsoNormal"><u></u=
>&nbsp;<u></u></p></div><blockquote style=3D"border:none;border-left:solid =
#cccccc 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in"=
>
<div><div><p class=3D"MsoNormal"><span lang=3D"EN-GB"><u></u>&nbsp;<u></u><=
/span></p></div><p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"font-s=
ize:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f=
497d">A</span><span lang=3D"EN-GB"><u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">&nbsp;</sp=
an><span lang=3D"EN-GB"><u></u><u></u></span></p><p class=3D"MsoNormal"><sp=
an lang=3D"EN-GB" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;=
,&quot;sans-serif&quot;;color:#1f497d">&nbsp;</span><span lang=3D"EN-GB"><u=
></u><u></u></span></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt"><div><div style=3D"border:none;border-top:solid #b5c4df 1.0pt;paddin=
g:3.0pt 0in 0in 0in"><p class=3D"MsoNormal"><b><span style=3D"font-size:10.=
0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b>=
<span style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-s=
erif&quot;"> Andy Bierman [mailto:<a href=3D"mailto:andy@yumaworks.com" tar=
get=3D"_blank">andy@yumaworks.com</a>] <br>
<b>Sent:</b> 09 February 2014 06:25<br><b>To:</b> David Harrington<br><b>Cc=
:</b> Adrian Farrel; MIB Doctors (E-mail)<br><b>Subject:</b> Re: [MIB-DOCTO=
RS] Read-only MIB modules</span><span lang=3D"EN-GB"><u></u><u></u></span><=
/p>
</div></div><p class=3D"MsoNormal"><span lang=3D"EN-GB">&nbsp;<u></u><u></u=
></span></p><div><p class=3D"MsoNormal"><span lang=3D"EN-GB">Hi,<u></u><u><=
/u></span></p><div><p class=3D"MsoNormal"><span lang=3D"EN-GB">&nbsp;<u></u=
><u></u></span></p>
</div><div><p class=3D"MsoNormal"><span lang=3D"EN-GB">I do not really know=
 if an official statement to avoid SNMP Set is needed.<u></u><u></u></span>=
</p></div><div><p class=3D"MsoNormal"><span lang=3D"EN-GB">IMO the verdict =
is in wrt/ SNMP for configuration.<u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal"><span lang=3D"EN-GB">&nbsp;<u></u><u></u>=
</span></p></div><div><p class=3D"MsoNormal"><span lang=3D"EN-GB">It has be=
en a long-held tradition in the IETF to let people flail in their own<u></u=
><u></u></span></p>
</div><div><p class=3D"MsoNormal"><span lang=3D"EN-GB">sandbox if that&#39;=
s what they really wanted to do. &nbsp;Maybe that has been a<u></u><u></u><=
/span></p></div><div><p class=3D"MsoNormal"><span lang=3D"EN-GB">mistake. M=
aybe WGs should be forced to prove that they have enough<u></u><u></u></spa=
n></p>
</div><div><p class=3D"MsoNormal"><span lang=3D"EN-GB">real stakeholders wi=
lling to implement a spec, so that every part of<u></u><u></u></span></p></=
div><div><p class=3D"MsoNormal"><span lang=3D"EN-GB">every proposed standar=
d gets sponsored.<u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal"><span lang=3D"EN-GB">&nbsp;<u></u><u></u>=
</span></p></div><div><p class=3D"MsoNormal"><span lang=3D"EN-GB">We often =
presume that &quot;some vendors&quot;, who have had no interest in the<u></=
u><u></u></span></p>
</div><div><p class=3D"MsoNormal"><span lang=3D"EN-GB">work all along, will=
 eventually come around and decide to implement.<u></u><u></u></span></p></=
div><div><p class=3D"MsoNormal"><span lang=3D"EN-GB">Therefore there is no =
need to have strong interest in deployment during<u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal"><span lang=3D"EN-GB">the WG process.<u></=
u><u></u></span></p></div><div><p class=3D"MsoNormal"><span lang=3D"EN-GB">=
&nbsp;<u></u><u></u></span></p></div><div><p class=3D"MsoNormal"><span lang=
=3D"EN-GB">Commitment to implementation should apply to everything -- proto=
cols,<u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal"><span lang=3D"EN-GB">MIB modules, YANG mo=
dules --- it doesn&#39;t matter. No stakeholders,<u></u><u></u></span></p><=
/div><div><p class=3D"MsoNormal"><span lang=3D"EN-GB">no sandbox. &nbsp;Tha=
t would be a radical change ;-)<u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal"><span lang=3D"EN-GB">&nbsp;<u></u><u></u>=
</span></p></div><div><p class=3D"MsoNormal"><span lang=3D"EN-GB">&nbsp;<u>=
</u><u></u></span></p></div><div><p class=3D"MsoNormal"><span lang=3D"EN-GB=
">Andy<u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal"><span lang=3D"EN-GB">&nbsp;<u></u><u></u>=
</span></p></div></div><div><p class=3D"MsoNormal" style=3D"margin-bottom:1=
2.0pt"><span lang=3D"EN-GB">&nbsp;<u></u><u></u></span></p><div><p class=3D=
"MsoNormal"><span lang=3D"EN-GB">On Sat, Feb 8, 2014 at 8:28 PM, David Harr=
ington &lt;<a href=3D"mailto:ietfdbh@comcast.net" target=3D"_blank">ietfdbh=
@comcast.net</a>&gt; wrote:<u></u><u></u></span></p>
<div><p class=3D"MsoNormal"><span lang=3D"EN-GB">Hi,<u></u><u></u></span></=
p><div><p class=3D"MsoNormal"><span lang=3D"EN-GB">&nbsp;<u></u><u></u></sp=
an></p></div><div><p class=3D"MsoNormal"><span lang=3D"EN-GB">I object to t=
his statement. (Should I say &quot;strongly&quot; object, to show I mean bu=
siness?<u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal"><span lang=3D"EN-GB">&nbsp;<u></u><u></u>=
</span></p></div><div><p class=3D"MsoNormal"><span lang=3D"EN-GB">There are=
 many RW objects that can &quot;adjust&quot; a network configuration assumi=
ng SET is supported by the agent involved.<u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal"><span lang=3D"EN-GB">The NMS I used to wo=
rk on, which helped determine and correct root cause for fault and performa=
nce problems, adjusted networks using writable MIB modules often.<u></u><u>=
</u></span></p>
</div><div><p class=3D"MsoNormal"><span lang=3D"EN-GB">To tell WGs they sho=
uld not develop RW MIB modules I think is wrong.<u></u><u></u></span></p></=
div><div><p class=3D"MsoNormal"><span lang=3D"EN-GB">&nbsp;<u></u><u></u></=
span></p>
</div><div><p class=3D"MsoNormal"><span lang=3D"EN-GB">I also have a concer=
n with recommending Netconf/YANG at this point in time.<u></u><u></u></span=
></p></div><div><p class=3D"MsoNormal"><span lang=3D"EN-GB">If we looked up=
 the top ten router vendors using something like Gartner reports, how many =
of them really support configuration using Netconf with YANG in shipping pr=
oducts?<u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal"><span lang=3D"EN-GB">Ditto, the top ten s=
witch vendors?<u></u><u></u></span></p></div><div><p class=3D"MsoNormal"><s=
pan lang=3D"EN-GB">How many of them can be fully configured using YANG modu=
les (not homegrown alternatives, but modules - standard or proprietary - wr=
itten using the standards-compliant YANG language)?<u></u><u></u></span></p=
>
</div><div><p class=3D"MsoNormal"><span lang=3D"EN-GB">I don&#39;t know the=
 answer to that question, but would like to see some proof that YANG is at =
least as widely supported in currently shipping products as RW MIB objects.=
<u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal"><span lang=3D"EN-GB">I think Netconf/YANG=
 should compete in an open market with RW MIB modules, not try to stack the=
 deck in their favor by &quot;strongly discouraging&quot; RW MIB standards.=
<u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal"><span lang=3D"EN-GB">&nbsp;<u></u><u></u>=
</span></p></div><div><p class=3D"MsoNormal"><span lang=3D"EN-GB">I have ha=
d discussions with vendors who are leaders in their particular networking n=
iche, and they have told me they would not consider Netconf/YANG, because i=
t has not been around long enough and been widely-enough deployed to prove =
stable for their production networks (whereas SNMP has enough track record =
to be known to be stable).<u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal"><span lang=3D"EN-GB">So I&#39;m a bit con=
cerned about telling WGs they should develop YANG modules rather than MIB m=
odules.<u></u><u></u></span></p></div><div><p class=3D"MsoNormal"><span lan=
g=3D"EN-GB">And the current discussions of whether YANG 1.1 or 2.0 is neede=
d to fix some problems with YANG 1.0, and it may not be backwards compatibl=
e, make me question the stability of YANG.<u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal"><span lang=3D"EN-GB">&nbsp;<u></u><u></u>=
</span></p></div><div><p class=3D"MsoNormal"><span lang=3D"EN-GB">Don&#39;t=
 get me wrong. I support Netconf/YANG going forward, but I think it is impo=
rtant to provide advice that non-MIB-Doctors/non-YANG-experts can interpret=
 reasonably.<u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal"><span lang=3D"EN-GB">Any such statement s=
hould make a clear distinction between &quot;configuration&quot; - the comp=
lete configuration of a device by Netconf - versus RW objects in a MIB - wh=
ich can be used by SNMP to adjust network parameters/configuration.<u></u><=
u></u></span></p>
</div><div><p class=3D"MsoNormal"><span lang=3D"EN-GB">Telling people not t=
o develop RW MIBs is throwing the baby out with the bathwater.<u></u><u></u=
></span></p></div><div><p class=3D"MsoNormal"><span lang=3D"EN-GB">We shoul=
d NOT recommend against RW MIBs, because these can be used for more than (f=
ull device) configuration.<u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal"><span lang=3D"EN-GB">That point is far fr=
om clear in the currently proposed statement.<u></u><u></u></span></p></div=
><div><p class=3D"MsoNormal"><span lang=3D"EN-GB">Maybe the statement shoul=
d be that, if a vendor wants to replace their CLI, they should replace it w=
ith Netconf/YANG, and not with SNMP/RW-MIBs.&nbsp;<u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal"><span lang=3D"EN-GB">That&#39;s probably =
a closer approximation &nbsp;of Netconf/YANG&#39;s applicability versus RW =
MIBs.&nbsp;<u></u><u></u></span></p></div><div><p class=3D"MsoNormal"><span=
 lang=3D"EN-GB">&nbsp;<u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal"><span lang=3D"EN-GB">In the past we have =
allowed implementations to make the conformance choice between supporting a=
 MIB as RW, or implementing read-only.<u></u><u></u></span></p></div><div><=
p class=3D"MsoNormal">
<span lang=3D"EN-GB">If we advise WGs to not develop module with RW objects=
, then we take the choice away from the vendors.<u></u><u></u></span></p></=
div><div><p class=3D"MsoNormal"><span lang=3D"EN-GB">I thick that would be =
a mistake.<u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal"><span lang=3D"EN-GB">&nbsp;<u></u><u></u>=
</span></p></div><div><p class=3D"MsoNormal"><span lang=3D"EN-GB">In &nbsp;=
addition, it is pointed out later in this thread that other SDOs use RW MIB=
s.&nbsp;<u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal"><span lang=3D"EN-GB">Well, those MIBs pro=
duced by other SDOs (and for that matter, vendors) might require some suppo=
rt for specific RW objects in IETF MIB modules.<u></u><u></u></span></p></d=
iv>
<div><p class=3D"MsoNormal"><span lang=3D"EN-GB">Therefore, I think it woul=
d be providing bad advice to say that IETF WGs should not produce MIB &nbsp=
;modules with RW objects in them.<u></u><u></u></span></p></div><div><p cla=
ss=3D"MsoNormal">
<span lang=3D"EN-GB">&nbsp;<u></u><u></u></span></p></div><div><p class=3D"=
MsoNormal"><span lang=3D"EN-GB">If Netconf/YANG becomes widely deployed, th=
en NMS implementations and operators can choose whether to use YANG or SNMP=
 (or their CLI) to adjust network configurations.<u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal"><span lang=3D"EN-GB">THat should not be a=
 decision we make in the IETF, effectively forcing WGs to not develop MIBs =
with writable objects.<u></u><u></u></span></p></div><div><p class=3D"MsoNo=
rmal">
<span lang=3D"EN-GB">&nbsp;<u></u><u></u></span></p></div><div><p class=3D"=
MsoNormal"><span lang=3D"EN-GB">Providing RW objects in MIB modules lets im=
plementers and operators make the appropriate choice for their environments=
. (See RFC 3365 for similar thinking vis-a-vis security.)<u></u><u></u></sp=
an></p>
</div><div><p class=3D"MsoNormal"><span lang=3D"EN-GB">&nbsp;<u></u><u></u>=
</span></p></div><div><p class=3D"MsoNormal"><span lang=3D"EN-GB">dbh<u></u=
><u></u></span></p></div><div><p class=3D"MsoNormal"><span lang=3D"EN-GB">&=
nbsp;<u></u><u></u></span></p>
<div><div><p class=3D"MsoNormal"><span lang=3D"EN-GB">On Feb 4, 2014, at 8:=
32 AM, Adrian Farrel &lt;<a href=3D"mailto:adrian@olddog.co.uk" target=3D"_=
blank">adrian@olddog.co.uk</a>&gt; wrote:<u></u><u></u></span></p></div><p =
class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">
<span lang=3D"EN-GB"><u></u>&nbsp;<u></u></span></p><div><div><p class=3D"M=
soNormal" style=3D"text-align:justify"><span lang=3D"EN-GB" style=3D"font-s=
ize:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f=
497d">Hi,</span><span lang=3D"EN-GB"><u></u><u></u></span></p>
<p class=3D"MsoNormal" style=3D"text-align:justify"><span lang=3D"EN-GB" st=
yle=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&qu=
ot;;color:#1f497d">&nbsp;</span><span lang=3D"EN-GB"><u></u><u></u></span><=
/p><p class=3D"MsoNormal" style=3D"text-align:justify">
<span lang=3D"EN-GB" style=3D"font-size:11.0pt;font-family:&quot;Calibri&qu=
ot;,&quot;sans-serif&quot;;color:#1f497d">The MPLS working group is testing=
 the water to see whether one of its MIB modules should be &quot;reduced&qu=
ot; to read-only. This is the document that triggered my recent questions t=
hat led on to the draft advice you are working on. The WG took the document=
 back to make this decision.</span><span lang=3D"EN-GB"><u></u><u></u></spa=
n></p>
<p class=3D"MsoNormal" style=3D"text-align:justify"><span lang=3D"EN-GB" st=
yle=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&qu=
ot;;color:#1f497d">&nbsp;</span><span lang=3D"EN-GB"><u></u><u></u></span><=
/p><p class=3D"MsoNormal" style=3D"text-align:justify">
<span lang=3D"EN-GB" style=3D"font-size:11.0pt;font-family:&quot;Calibri&qu=
ot;,&quot;sans-serif&quot;;color:#1f497d">You&#39;ll note below that we imm=
ediately have an implementation claim (not for this doc, but for the module=
s it extends).</span><span lang=3D"EN-GB"><u></u><u></u></span></p>
<p class=3D"MsoNormal" style=3D"text-align:justify"><span lang=3D"EN-GB" st=
yle=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&qu=
ot;;color:#1f497d">&nbsp;</span><span lang=3D"EN-GB"><u></u><u></u></span><=
/p><p class=3D"MsoNormal" style=3D"text-align:justify">
<span lang=3D"EN-GB" style=3D"font-size:11.0pt;font-family:&quot;Calibri&qu=
ot;,&quot;sans-serif&quot;;color:#1f497d">An interesting situation, I think=
.</span><span lang=3D"EN-GB"><u></u><u></u></span></p><p class=3D"MsoNormal=
" style=3D"text-align:justify">
<span lang=3D"EN-GB" style=3D"font-size:11.0pt;font-family:&quot;Calibri&qu=
ot;,&quot;sans-serif&quot;;color:#1f497d">&nbsp;</span><span lang=3D"EN-GB"=
><u></u><u></u></span></p><p class=3D"MsoNormal" style=3D"text-align:justif=
y"><span lang=3D"EN-GB" style=3D"font-size:11.0pt;font-family:&quot;Calibri=
&quot;,&quot;sans-serif&quot;;color:#1f497d">A</span><span lang=3D"EN-GB"><=
u></u><u></u></span></p>
<p class=3D"MsoNormal" style=3D"text-align:justify"><span lang=3D"EN-GB" st=
yle=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&qu=
ot;;color:#1f497d">&nbsp;</span><span lang=3D"EN-GB"><u></u><u></u></span><=
/p><div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0=
in 4.0pt">
<div><div style=3D"border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt=
 0in 0in 0in"><p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;fon=
t-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span s=
tyle=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&qu=
ot;">&nbsp;mpls [mailto:<a href=3D"mailto:mpls-" target=3D"_blank">mpls-</a=
><a href=3D"mailto:bounces@ietf.org" target=3D"_blank"><span style=3D"color=
:#954f72">bounces@ietf.org</span></a>]&nbsp;<b>On Behalf Of&nbsp;</b>GyeRok=
 Gwun (???)<br>
<b>Sent:</b>&nbsp;04 February 2014 09:57<br><b>To:</b>&nbsp;&#39;<a href=3D=
"mailto:mpls@ietf.org" target=3D"_blank"><span style=3D"color:#954f72">mpls=
@ietf.org</span></a>&#39;<br><b>Cc:</b>&nbsp;&#39;<a href=3D"mailto:mpls-ch=
airs@tools.ietf.org" target=3D"_blank"><span style=3D"color:#954f72">mpls-c=
hairs@tools.ietf.org</span></a>&#39;; &#39;<a href=3D"mailto:draft-ietf-mpl=
s-tp-te-mib@tools.ietf.org" target=3D"_blank"><span style=3D"color:#954f72"=
>draft-ietf-mpls-tp-te-mib@tools.ietf.org</span></a>&#39;<br>
<b>Subject:</b>&nbsp;Re: [mpls] seeking consensus on making draft-ietf-mpls=
-tp-te-mib read- only</span><span lang=3D"EN-GB"><u></u><u></u></span></p><=
/div></div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span lang=
=3D"EN-GB" style=3D"font-size:10.0pt;font-family:&quot;Malgun Gothic&quot;,=
&quot;sans-serif&quot;">&nbsp;</span><span lang=3D"EN-GB"><u></u><u></u></s=
pan></p>
<div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span style=3D"f=
ont-size:10.0pt;font-family:&quot;Courier New&quot;">No/oppose to make as R=
ead-only mib.</span><span lang=3D"EN-GB"><u></u><u></u></span></p></div><di=
v><p class=3D"MsoNormal" style=3D"word-break:break-all">
<span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">In our=
 products we extensively use R/W object of TE mib. We also have NMS/EMS tha=
t use TE read-write Objects</span><span lang=3D"EN-GB"><u></u><u></u></span=
></p>
</div><div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span styl=
e=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;</span><sp=
an lang=3D"EN-GB"><u></u><u></u></span></p></div><div><p class=3D"MsoNormal=
" style=3D"word-break:break-all">
<span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">Best R=
egards</span><span lang=3D"EN-GB"><u></u><u></u></span></p></div><div><p cl=
ass=3D"MsoNormal" style=3D"word-break:break-all"><span style=3D"font-size:1=
0.0pt;font-family:&quot;Courier New&quot;">Gwun</span><span lang=3D"EN-GB">=
<u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span styl=
e=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;</span><sp=
an lang=3D"EN-GB"><u></u><u></u></span></p></div><div><p class=3D"MsoNormal=
" style=3D"word-break:break-all">
<span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">-----O=
riginal Message-----</span><span lang=3D"EN-GB"><u></u><u></u></span></p></=
div><div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span style=
=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">From: mpls [<a hr=
ef=3D"mailto:mpls-bounces@ietf.org" target=3D"_blank"><span style=3D"color:=
#954f72">mailto:mpls-bounces@ietf.org</span></a>] On Behalf Of Loa Andersso=
n</span><span lang=3D"EN-GB"><u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span styl=
e=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">Sent: Monday, Fe=
bruary 03, 2014 10:55 PM</span><span lang=3D"EN-GB"><u></u><u></u></span></=
p></div>
<div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span style=3D"f=
ont-size:10.0pt;font-family:&quot;Courier New&quot;">To:&nbsp;<a href=3D"ma=
ilto:mpls@ietf.org" target=3D"_blank"><span style=3D"color:#954f72">mpls@ie=
tf.org</span></a></span><span lang=3D"EN-GB"><u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span styl=
e=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">Cc:&nbsp;<a href=
=3D"mailto:mpls-chairs@tools.ietf.org" target=3D"_blank"><span style=3D"col=
or:#954f72">mpls-chairs@tools.ietf.org</span></a>;&nbsp;<a href=3D"mailto:d=
raft-ietf-mpls-tp-te-mib@tools.ietf.org" target=3D"_blank"><span style=3D"c=
olor:#954f72">draft-ietf-mpls-tp-te-mib@tools.ietf.org</span></a></span><sp=
an lang=3D"EN-GB"><u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span styl=
e=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">Subject: [mpls] =
seeking consensus on making draft-ietf-mpls-tp-te-mib read- only</span><spa=
n lang=3D"EN-GB"><u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span styl=
e=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;</span><sp=
an lang=3D"EN-GB"><u></u><u></u></span></p></div><div><p class=3D"MsoNormal=
" style=3D"word-break:break-all">
<span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">Workin=
g Group,</span><span lang=3D"EN-GB"><u></u><u></u></span></p></div><div><p =
class=3D"MsoNormal" style=3D"word-break:break-all"><span style=3D"font-size=
:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;</span><span lang=3D"EN-=
GB"><u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span styl=
e=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">We have just rec=
alled draft-ietf-mpls-tp-te-mib from the IESG to the working group for more=
 work. We have a series of comments that are mostly for clarification. Howe=
ver the main reason for recalling the document is that there is one point w=
here we need to confirm working group consensus.</span><span lang=3D"EN-GB"=
><u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span styl=
e=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;</span><sp=
an lang=3D"EN-GB"><u></u><u></u></span></p></div><div><p class=3D"MsoNormal=
" style=3D"word-break:break-all">
<span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">The IE=
TF, the working group and the MIB Doctors are today very reluctant to produ=
ce read-write MIB modules. The current draft is read-write for a few object=
s, this is based on a consensus call for an earlier discussion, however the=
 consensus call was not clear. It can be taken to mean both that we want to=
 go with read-write objects and that we want to see read-only. Is it clear =
that it has been interpreted differently by different individuals.</span><s=
pan lang=3D"EN-GB"><u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span styl=
e=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;</span><sp=
an lang=3D"EN-GB"><u></u><u></u></span></p></div><div><p class=3D"MsoNormal=
" style=3D"word-break:break-all">
<span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">The au=
thors and chairs have discussed the issue and we have a rough consensus tha=
t we want the MIB module(s) to be read-only.</span><span lang=3D"EN-GB"><u>=
</u><u></u></span></p>
</div><div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span styl=
e=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;</span><sp=
an lang=3D"EN-GB"><u></u><u></u></span></p></div><div><p class=3D"MsoNormal=
" style=3D"word-break:break-all">
<span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">We the=
refore are asking the working group if this is OK for the MIB</span><span l=
ang=3D"EN-GB"><u></u><u></u></span></p></div><div><p class=3D"MsoNormal" st=
yle=3D"word-break:break-all">
<span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">module=
(s) in the current document. Please indicate Support or Oppose for this MIB=
 (draft-ietf-mpls-tp-te-mib) to be read-only.</span><span lang=3D"EN-GB"><u=
></u><u></u></span></p>
</div><div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span styl=
e=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;</span><sp=
an lang=3D"EN-GB"><u></u><u></u></span></p></div><div><p class=3D"MsoNormal=
" style=3D"word-break:break-all">
<span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">Please=
 send your comments to the working group mailing list before February 18, 2=
014.</span><span lang=3D"EN-GB"><u></u><u></u></span></p></div><div><p clas=
s=3D"MsoNormal" style=3D"word-break:break-all">
<span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;=
</span><span lang=3D"EN-GB"><u></u><u></u></span></p></div><div><p class=3D=
"MsoNormal" style=3D"word-break:break-all"><span style=3D"font-size:10.0pt;=
font-family:&quot;Courier New&quot;">Loa</span><span lang=3D"EN-GB"><u></u>=
<u></u></span></p>
</div><div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span styl=
e=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">for the MPLS wg =
chairs</span><span lang=3D"EN-GB"><u></u><u></u></span></p></div><div><p cl=
ass=3D"MsoNormal" style=3D"word-break:break-all">
<span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">--</sp=
an><span lang=3D"EN-GB"><u></u><u></u></span></p></div><div><p class=3D"Mso=
Normal" style=3D"word-break:break-all"><span style=3D"font-size:10.0pt;font=
-family:&quot;Courier New&quot;">&nbsp;</span><span lang=3D"EN-GB"><u></u><=
u></u></span></p>
</div><div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span styl=
e=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;</span><sp=
an lang=3D"EN-GB"><u></u><u></u></span></p></div><div><p class=3D"MsoNormal=
" style=3D"word-break:break-all">
<span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">Loa An=
dersson&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; emai=
l:&nbsp;<a href=3D"mailto:loa@mail01.huawei.com" target=3D"_blank"><span st=
yle=3D"color:#954f72">loa@mail01.huawei.com</span></a></span><span lang=3D"=
EN-GB"><u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span styl=
e=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">Senior MPLS Expe=
rt&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;<a href=3D"mailto:loa@pi.nu" target=3D"_blank"><span style=3D"color=
:#954f72">loa@pi.nu</span></a></span><span lang=3D"EN-GB"><u></u><u></u></s=
pan></p>
</div><div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span styl=
e=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">Huawei Technolog=
ies (consultant)&nbsp;&nbsp;&nbsp;&nbsp; phone: +46 739 81 21 64</span><spa=
n lang=3D"EN-GB"><u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span styl=
e=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">________________=
_______________________________</span><span lang=3D"EN-GB"><u></u><u></u></=
span></p>
</div><div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span styl=
e=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">mpls mailing lis=
t</span><span lang=3D"EN-GB"><u></u><u></u></span></p></div><div><p class=
=3D"MsoNormal" style=3D"word-break:break-all">
<span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;"><a hre=
f=3D"mailto:mpls@ietf.org" target=3D"_blank"><span style=3D"color:#954f72">=
mpls@ietf.org</span></a></span><span lang=3D"EN-GB"><u></u><u></u></span></=
p></div>
<div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span style=3D"f=
ont-size:10.0pt;font-family:&quot;Courier New&quot;"><a href=3D"https://www=
.ietf.org/mailman/listinfo/mpls" target=3D"_blank"><span style=3D"color:#95=
4f72">https://www.ietf.org/mailman/listinfo/mpls</span></a></span><span lan=
g=3D"EN-GB"><u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span styl=
e=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">________________=
_______________________________</span><span lang=3D"EN-GB"><u></u><u></u></=
span></p>
</div><div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span styl=
e=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">mpls mailing lis=
t</span><span lang=3D"EN-GB"><u></u><u></u></span></p></div><div><p class=
=3D"MsoNormal" style=3D"word-break:break-all">
<span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;"><a hre=
f=3D"mailto:mpls@ietf.org" target=3D"_blank"><span style=3D"color:#954f72">=
mpls@ietf.org</span></a></span><span lang=3D"EN-GB"><u></u><u></u></span></=
p></div>
<div><p class=3D"MsoNormal" style=3D"word-break:break-all"><span style=3D"f=
ont-size:10.0pt;font-family:&quot;Courier New&quot;"><a href=3D"https://www=
.ietf.org/mailman/listinfo/mpls" target=3D"_blank"><span style=3D"color:#95=
4f72">https://www.ietf.org/mailman/listinfo/mpls</span></a></span><span lan=
g=3D"EN-GB"><u></u><u></u></span></p>
</div><p class=3D"MsoNormal" style=3D"text-align:justify;word-break:break-a=
ll"><span style=3D"font-size:10.0pt;font-family:&quot;Malgun Gothic&quot;,&=
quot;sans-serif&quot;">&nbsp;</span><span lang=3D"EN-GB"><u></u><u></u></sp=
an></p></div>
</div><p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"font-size:13.5pt=
;font-family:&quot;Helvetica&quot;,&quot;sans-serif&quot;">________________=
_______________________________<br>MIB-DOCTORS mailing list<br><a href=3D"m=
ailto:MIB-DOCTORS@ietf.org" target=3D"_blank"><span style=3D"color:#954f72"=
>MIB-DOCTORS@ietf.org</span></a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/mib-doctors" target=3D"_bl=
ank"><span style=3D"color:#954f72">https://www.ietf.org/mailman/listinfo/mi=
b-doctors</span></a></span><span lang=3D"EN-GB"><u></u><u></u></span></p></=
div>
</div><p class=3D"MsoNormal"><span lang=3D"EN-GB">&nbsp;<u></u><u></u></spa=
n></p></div></div><p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><sp=
an lang=3D"EN-GB"><br>_______________________________________________<br>MI=
B-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" ta=
rget=3D"_blank">https://www.ietf.org/mailman/listinfo/mib-doctors</a><u></u=
><u></u></span></p>
</div><p class=3D"MsoNormal"><span lang=3D"EN-GB">&nbsp;<u></u><u></u></spa=
n></p></div></div></div></blockquote></div><p class=3D"MsoNormal"><u></u>&n=
bsp;<u></u></p></div></div><p class=3D"MsoNormal">_________________________=
______________________<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/mai=
lman/listinfo/mib-doctors" target=3D"_blank">https://www.ietf.org/mailman/l=
istinfo/mib-doctors</a><u></u><u></u></p>
</div><p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p></div></div></div></bl=
ockquote></div><br></div></div>

--047d7bdc804051d18f04f36c03dc--


From nobody Thu Feb 27 17:26:16 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 F02661A02C6 for <mib-doctors@ietfa.amsl.com>; Thu, 27 Feb 2014 17:26:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.7
X-Spam-Level: 
X-Spam-Status: No, score=0.7 tagged_above=-999 required=5 tests=[BAYES_50=0.8,  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 3Hbnf4qULIbA for <mib-doctors@ietfa.amsl.com>; Thu, 27 Feb 2014 17:26:12 -0800 (PST)
Received: from elasmtp-masked.atl.sa.earthlink.net (elasmtp-masked.atl.sa.earthlink.net [209.86.89.68]) by ietfa.amsl.com (Postfix) with ESMTP id DFBB01A01E0 for <mib-doctors@ietf.org>; Thu, 27 Feb 2014 17:26:11 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=twJHS9RhNYQ5hoxpeo6FvJZ4ljCrA3vaHLaBGtAHzwhEUAhRxoQxrk9mT8BKnxiK; h=Message-ID:Date:From:Reply-To:To:Subject:Mime-Version:Content-Type:Content-Transfer-Encoding:X-Mailer:X-ELNK-Trace:X-Originating-IP;
Received: from [209.86.224.30] (helo=mswamui-chipeau.atl.sa.earthlink.net) by elasmtp-masked.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <randy_presuhn@mindspring.com>) id 1WJCDJ-0005jQ-IU for mib-doctors@ietf.org; Thu, 27 Feb 2014 20:26:09 -0500
Received: from 99.101.142.158 by webmail.earthlink.net with HTTP; Thu, 27 Feb 2014 20:26:09 -0500
Message-ID: <23691644.1393550769462.JavaMail.root@mswamui-chipeau.atl.sa.earthlink.net>
Date: Thu, 27 Feb 2014 20:26:09 -0500 (EST)
From: Randy Presuhn <randy_presuhn@mindspring.com>
To: 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: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d88891b749bef7332bbcb805349b9f4dc7867943edf66c483704350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 209.86.224.30
Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/syuEWcJkcjN8m4AmkV2OnhWxaA4
Subject: Re: [MIB-DOCTORS] Read-only MIB modules
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: Fri, 28 Feb 2014 01:26:14 -0000

Hi -

>From: David Harrington <dbharrington@comcast.net>
>Sent: Feb 27, 2014 2:14 PM
...
>"WG groups can then decide
>if they have enough participants who plan on implementing read-create.
>If not, then they can't have it.  The MIB gets rejected and sent back
>to the WG if it contains any MIN-ACCESS clauses.
>"
>
>So why should rw mibs be held to a higher standard than other IETF proposed
>standards?

I can think of three barely plausible policy motivations:

   - WGs are stupid and don't know what they're getting
     into when they decide to standardize configuration,
     so they should be discouraged in every way possible

   - by making rw mibs more difficult to standardize WGs
     will be encouraged to use Yang / Netconf instead,
     presumably because Yang modules are cheaper to develop
     or because there has been a policy decision to favor
     that technology.

   - standardized configuration of any kind is expensive
     (in terms of WG resources) to develop and consequently
     should be discouraged in favor of whatever vendor-
     specific solutions might arise.

I think all of these are lousy rationales, so I
would welcome a more plausible explanation.

Randy


From nobody Thu Feb 27 18:12:33 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 EEBCE1A02C6 for <mib-doctors@ietfa.amsl.com>; Thu, 27 Feb 2014 18:12:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Level: 
X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 csTWXnZ29UN8 for <mib-doctors@ietfa.amsl.com>; Thu, 27 Feb 2014 18:12:29 -0800 (PST)
Received: from mail-qa0-f50.google.com (mail-qa0-f50.google.com [209.85.216.50]) by ietfa.amsl.com (Postfix) with ESMTP id 531EF1A0334 for <mib-doctors@ietf.org>; Thu, 27 Feb 2014 18:12:29 -0800 (PST)
Received: by mail-qa0-f50.google.com with SMTP id cm18so87459qab.9 for <mib-doctors@ietf.org>; Thu, 27 Feb 2014 18:12:27 -0800 (PST)
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=jWSDsAN64li8QMt6Xq1W5f1ENEvhLaNf5/EpxNQ6pwc=; b=BbsY2eucdIW9cnSZI86ZhHSClrFqa2R7YD4fNyPsEJ9zRSXprmW4VN4FHfV4YyRGmB rpE9oAU9+k/RCQC7fJjDYcpn/rDJVBkIzUdwS7KBZHZoXMIKeVhZGSiUY8NpWmwxK1io EOkG+7Dg8C1AWIGLbC13cO0NfgudsSUcQFvvk1b3WvMlA9jQLzKs22oXKY39NpasJ/my 6zoypVWytQTbFRlpRPcD4Eb1x8nMPukBj6MBA2Kg+DGxFNtyUbGKFZXiq1MunHESIOMj KtcVn/FsKZO0ZupFBtv3mRbci2j5AXsO24r6VDmCLrYSyfevpIKhYMXW6tfYL9tN0Bxn V0oQ==
X-Gm-Message-State: ALoCoQnAURdcArtjvv0W+CyUfmIWp6wfGIUtsFQ/r+KrQqpFmT9nTyHOh2rasGVPYAUSBvIu0rtw
MIME-Version: 1.0
X-Received: by 10.140.92.65 with SMTP id a59mr369309qge.34.1393553547426; Thu, 27 Feb 2014 18:12:27 -0800 (PST)
Received: by 10.140.104.194 with HTTP; Thu, 27 Feb 2014 18:12:27 -0800 (PST)
In-Reply-To: <23691644.1393550769462.JavaMail.root@mswamui-chipeau.atl.sa.earthlink.net>
References: <23691644.1393550769462.JavaMail.root@mswamui-chipeau.atl.sa.earthlink.net>
Date: Thu, 27 Feb 2014 18:12:27 -0800
Message-ID: <CABCOCHRXxqDuU7mQLzstAvtZtueV8AnQysPkOAC3+009rB=CtQ@mail.gmail.com>
From: Andy Bierman <andy@yumaworks.com>
To: Randy Presuhn <randy_presuhn@mindspring.com>
Content-Type: multipart/alternative; boundary=001a113ab29e2b8c3304f36df895
Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/jPkA01jUzY7ULuDcko_JeGP9VH4
Cc: "MIB Doctors \(E-mail\)" <mib-doctors@ietf.org>
Subject: Re: [MIB-DOCTORS] Read-only MIB modules
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, 28 Feb 2014 02:12:32 -0000

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

Hi,

If 20+ years of publishing RFCs for ANY technology has not produced
industry adoption, then it might just be time to reevaluate the practice
of publishing these RFCs.

It is not surprising that MIB Police would remain in denial that
the jury is still out on SNMP Set.

We have understood for at least 15 years now that adding standard config
on top of proprietary config is complicated.  NETCONF/YANG has its
best chance with new products that do not have lots of legacy code
to work around.

Given the new marketing push for programmatic interfaces, companies
are forced to address this problem, more than ever before.

I am usually in favor of letting others flail in their own sandbox, as
long as I don't have to waste my time on it.  So if the MPLS world
feels better producing r/w MIBs that nobody implements, then
let them keep flailing.

The NETMOD WG has a backlog of configuration models that
have come from vendors.  There is some evidence that vendors
are willing to implement data models for configuration, using YANG.
IMO, nothing in the "SNMP world" is remotely relevant to this trend.
The industry has already decided SNMP is for monitoring.  That memo
apparently never got delivered to MIB police.


Andy




On Thu, Feb 27, 2014 at 5:26 PM, Randy Presuhn <randy_presuhn@mindspring.com
> wrote:

> Hi -
>
> >From: David Harrington <dbharrington@comcast.net>
> >Sent: Feb 27, 2014 2:14 PM
> ...
> >"WG groups can then decide
> >if they have enough participants who plan on implementing read-create.
> >If not, then they can't have it.  The MIB gets rejected and sent back
> >to the WG if it contains any MIN-ACCESS clauses.
> >"
> >
> >So why should rw mibs be held to a higher standard than other IETF
> proposed
> >standards?
>
> I can think of three barely plausible policy motivations:
>
>    - WGs are stupid and don't know what they're getting
>      into when they decide to standardize configuration,
>      so they should be discouraged in every way possible
>
>    - by making rw mibs more difficult to standardize WGs
>      will be encouraged to use Yang / Netconf instead,
>      presumably because Yang modules are cheaper to develop
>      or because there has been a policy decision to favor
>      that technology.
>
>    - standardized configuration of any kind is expensive
>      (in terms of WG resources) to develop and consequently
>      should be discouraged in favor of whatever vendor-
>      specific solutions might arise.
>
> I think all of these are lousy rationales, so I
> would welcome a more plausible explanation.
>
> Randy
>
> _______________________________________________
> MIB-DOCTORS mailing list
> MIB-DOCTORS@ietf.org
> https://www.ietf.org/mailman/listinfo/mib-doctors
>

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

<div dir=3D"ltr">Hi,<div><br></div><div>If 20+ years of publishing RFCs for=
 ANY technology has not produced</div><div>industry adoption, then it might=
 just be time to reevaluate the practice</div><div>of publishing these RFCs=
.</div>
<div><br></div><div>It is not surprising that MIB Police would remain in de=
nial that</div><div>the jury is still out on SNMP Set.</div><div><br></div>=
<div>We have understood for at least 15 years now that adding standard conf=
ig</div>
<div>on top of proprietary config is complicated. =A0NETCONF/YANG has its</=
div><div>best chance with new products that do not have lots of legacy code=
</div><div>to work around.</div><div><br></div><div>Given the new marketing=
 push for programmatic interfaces, companies</div>
<div>are forced to address this problem, more than ever before.</div><div><=
br></div><div>I am usually in favor of letting others flail in their own sa=
ndbox, as</div><div>long as I don&#39;t have to waste my time on it. =A0So =
if the MPLS world</div>
<div>feels better producing r/w MIBs that nobody implements, then</div><div=
>let them keep flailing.</div><div><br></div><div>The NETMOD WG has a backl=
og of configuration models that</div><div>have come from vendors. =A0There =
is some evidence that vendors</div>
<div>are willing to implement data models for configuration, using YANG.</d=
iv><div>IMO, nothing in the &quot;SNMP world&quot; is remotely relevant to =
this trend.</div><div>The industry has already decided SNMP is for monitori=
ng. =A0That memo</div>
<div>apparently never got delivered to MIB police.</div><div><br></div><div=
><br></div><div>Andy</div><div><br></div><div><br></div><div><br></div><div=
><br></div><div><div><div class=3D"gmail_extra"><div class=3D"gmail_quote">
On Thu, Feb 27, 2014 at 5:26 PM, Randy Presuhn <span dir=3D"ltr">&lt;<a hre=
f=3D"mailto:randy_presuhn@mindspring.com" target=3D"_blank">randy_presuhn@m=
indspring.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" st=
yle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi -<br><br>
&gt;From: David Harrington &lt;<a href=3D"mailto:dbharrington@comcast.net">=
dbharrington@comcast.net</a>&gt;<br>
&gt;Sent: Feb 27, 2014 2:14 PM<br>
...<br>
&gt;&quot;WG groups can then decide<br>
&gt;if they have enough participants who plan on implementing read-create.<=
br>
&gt;If not, then they can&#39;t have it. =A0The MIB gets rejected and sent =
back<br>
&gt;to the WG if it contains any MIN-ACCESS clauses.<br>
&gt;&quot;<br>
&gt;<br>
&gt;So why should rw mibs be held to a higher standard than other IETF prop=
osed<br>
&gt;standards?<br>
<br>
I can think of three barely plausible policy motivations:<br>
<br>
=A0 =A0- WGs are stupid and don&#39;t know what they&#39;re getting<br>
=A0 =A0 =A0into when they decide to standardize configuration,<br>
=A0 =A0 =A0so they should be discouraged in every way possible<br>
<br>
=A0 =A0- by making rw mibs more difficult to standardize WGs<br>
=A0 =A0 =A0will be encouraged to use Yang / Netconf instead,<br>
=A0 =A0 =A0presumably because Yang modules are cheaper to develop<br>
=A0 =A0 =A0or because there has been a policy decision to favor<br>
=A0 =A0 =A0that technology.<br>
<br>
=A0 =A0- standardized configuration of any kind is expensive<br>
=A0 =A0 =A0(in terms of WG resources) to develop and consequently<br>
=A0 =A0 =A0should be discouraged in favor of whatever vendor-<br>
=A0 =A0 =A0specific solutions might arise.<br>
<br>
I think all of these are lousy rationales, so I<br>
would welcome a more plausible explanation.<br>
<br>
Randy<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>
</blockquote></div><br></div></div></div></div>

--001a113ab29e2b8c3304f36df895--


From nobody Fri Feb 28 00:21:37 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 9F9AA1A00CB for <mib-doctors@ietfa.amsl.com>; Fri, 28 Feb 2014 00:21:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.446
X-Spam-Level: 
X-Spam-Status: No, score=-2.446 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.547] 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 LWxlm2LSlbTN for <mib-doctors@ietfa.amsl.com>; Fri, 28 Feb 2014 00:21:32 -0800 (PST)
Received: from lucidvision.com (lucidvision.com [72.71.250.34]) by ietfa.amsl.com (Postfix) with ESMTP id 4647A1A0011 for <mib-doctors@ietf.org>; Fri, 28 Feb 2014 00:21:32 -0800 (PST)
Received: from [10.21.248.168] (unknown [166.170.57.106]) by lucidvision.com (Postfix) with ESMTP id 7DBAE270C4C9; Fri, 28 Feb 2014 03:21:13 -0500 (EST)
References: <23691644.1393550769462.JavaMail.root@mswamui-chipeau.atl.sa.earthlink.net> <CABCOCHRXxqDuU7mQLzstAvtZtueV8AnQysPkOAC3+009rB=CtQ@mail.gmail.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: <CABCOCHRXxqDuU7mQLzstAvtZtueV8AnQysPkOAC3+009rB=CtQ@mail.gmail.com>
Content-Type: multipart/alternative; boundary=Apple-Mail-454E47C9-A148-4AF8-802E-DA20AF66E14D
Content-Transfer-Encoding: 7bit
Message-Id: <AF01DF83-D5C1-4A3D-95E8-6B4E0907F6D7@lucidvision.com>
X-Mailer: iPhone Mail (11B651)
From: Thomas D Nadeau <tnadeau@lucidvision.com>
Date: Fri, 28 Feb 2014 08:20:49 +0000
To: Andy Bierman <andy@yumaworks.com>
Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/yYoIQb65DRoiq7EGMI-iDzSY_Ec
Cc: Randy Presuhn <randy_presuhn@mindspring.com>, "MIB Doctors \(E-mail\)" <mib-doctors@ietf.org>
Subject: Re: [MIB-DOCTORS] Read-only MIB modules
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, 28 Feb 2014 08:21:34 -0000

--Apple-Mail-454E47C9-A148-4AF8-802E-DA20AF66E14D
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable

well said; totally agree.

Tom=20


> On Feb 28, 2014, at 2:12, Andy Bierman <andy@yumaworks.com> wrote:
>=20
> Hi,
>=20
> If 20+ years of publishing RFCs for ANY technology has not produced
> industry adoption, then it might just be time to reevaluate the practice
> of publishing these RFCs.
>=20
> It is not surprising that MIB Police would remain in denial that
> the jury is still out on SNMP Set.
>=20
> We have understood for at least 15 years now that adding standard config
> on top of proprietary config is complicated.  NETCONF/YANG has its
> best chance with new products that do not have lots of legacy code
> to work around.
>=20
> Given the new marketing push for programmatic interfaces, companies
> are forced to address this problem, more than ever before.
>=20
> I am usually in favor of letting others flail in their own sandbox, as
> long as I don't have to waste my time on it.  So if the MPLS world
> feels better producing r/w MIBs that nobody implements, then
> let them keep flailing.
>=20
> The NETMOD WG has a backlog of configuration models that
> have come from vendors.  There is some evidence that vendors
> are willing to implement data models for configuration, using YANG.
> IMO, nothing in the "SNMP world" is remotely relevant to this trend.
> The industry has already decided SNMP is for monitoring.  That memo
> apparently never got delivered to MIB police.
>=20
>=20
> Andy
>=20
>=20
>=20
>=20
>> On Thu, Feb 27, 2014 at 5:26 PM, Randy Presuhn <randy_presuhn@mindspring.=
com> wrote:
>> Hi -
>>=20
>> >From: David Harrington <dbharrington@comcast.net>
>> >Sent: Feb 27, 2014 2:14 PM
>> ...
>> >"WG groups can then decide
>> >if they have enough participants who plan on implementing read-create.
>> >If not, then they can't have it.  The MIB gets rejected and sent back
>> >to the WG if it contains any MIN-ACCESS clauses.
>> >"
>> >
>> >So why should rw mibs be held to a higher standard than other IETF propo=
sed
>> >standards?
>>=20
>> I can think of three barely plausible policy motivations:
>>=20
>>    - WGs are stupid and don't know what they're getting
>>      into when they decide to standardize configuration,
>>      so they should be discouraged in every way possible
>>=20
>>    - by making rw mibs more difficult to standardize WGs
>>      will be encouraged to use Yang / Netconf instead,
>>      presumably because Yang modules are cheaper to develop
>>      or because there has been a policy decision to favor
>>      that technology.
>>=20
>>    - standardized configuration of any kind is expensive
>>      (in terms of WG resources) to develop and consequently
>>      should be discouraged in favor of whatever vendor-
>>      specific solutions might arise.
>>=20
>> I think all of these are lousy rationales, so I
>> would welcome a more plausible explanation.
>>=20
>> Randy
>>=20
>> _______________________________________________
>> MIB-DOCTORS mailing list
>> MIB-DOCTORS@ietf.org
>> https://www.ietf.org/mailman/listinfo/mib-doctors
>=20
> _______________________________________________
> MIB-DOCTORS mailing list
> MIB-DOCTORS@ietf.org
> https://www.ietf.org/mailman/listinfo/mib-doctors

--Apple-Mail-454E47C9-A148-4AF8-802E-DA20AF66E14D
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: 7bit

<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>well said; totally agree.</div><div><br></div><div>Tom&nbsp;</div><div><br></div><div><br>On Feb 28, 2014, at 2:12, Andy Bierman &lt;<a href="mailto:andy@yumaworks.com">andy@yumaworks.com</a>&gt; wrote:<br><br></div><blockquote type="cite"><div><div dir="ltr">Hi,<div><br></div><div>If 20+ years of publishing RFCs for ANY technology has not produced</div><div>industry adoption, then it might just be time to reevaluate the practice</div><div>of publishing these RFCs.</div>
<div><br></div><div>It is not surprising that MIB Police would remain in denial that</div><div>the jury is still out on SNMP Set.</div><div><br></div><div>We have understood for at least 15 years now that adding standard config</div>
<div>on top of proprietary config is complicated. &nbsp;NETCONF/YANG has its</div><div>best chance with new products that do not have lots of legacy code</div><div>to work around.</div><div><br></div><div>Given the new marketing push for programmatic interfaces, companies</div>
<div>are forced to address this problem, more than ever before.</div><div><br></div><div>I am usually in favor of letting others flail in their own sandbox, as</div><div>long as I don't have to waste my time on it. &nbsp;So if the MPLS world</div>
<div>feels better producing r/w MIBs that nobody implements, then</div><div>let them keep flailing.</div><div><br></div><div>The NETMOD WG has a backlog of configuration models that</div><div>have come from vendors. &nbsp;There is some evidence that vendors</div>
<div>are willing to implement data models for configuration, using YANG.</div><div>IMO, nothing in the "SNMP world" is remotely relevant to this trend.</div><div>The industry has already decided SNMP is for monitoring. &nbsp;That memo</div>
<div>apparently never got delivered to MIB police.</div><div><br></div><div><br></div><div>Andy</div><div><br></div><div><br></div><div><br></div><div><br></div><div><div><div class="gmail_extra"><div class="gmail_quote">
On Thu, Feb 27, 2014 at 5:26 PM, Randy Presuhn <span dir="ltr">&lt;<a href="mailto:randy_presuhn@mindspring.com" target="_blank">randy_presuhn@mindspring.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi -<br><br>
&gt;From: David Harrington &lt;<a href="mailto:dbharrington@comcast.net">dbharrington@comcast.net</a>&gt;<br>
&gt;Sent: Feb 27, 2014 2:14 PM<br>
...<br>
&gt;"WG groups can then decide<br>
&gt;if they have enough participants who plan on implementing read-create.<br>
&gt;If not, then they can't have it. &nbsp;The MIB gets rejected and sent back<br>
&gt;to the WG if it contains any MIN-ACCESS clauses.<br>
&gt;"<br>
&gt;<br>
&gt;So why should rw mibs be held to a higher standard than other IETF proposed<br>
&gt;standards?<br>
<br>
I can think of three barely plausible policy motivations:<br>
<br>
&nbsp; &nbsp;- WGs are stupid and don't know what they're getting<br>
&nbsp; &nbsp; &nbsp;into when they decide to standardize configuration,<br>
&nbsp; &nbsp; &nbsp;so they should be discouraged in every way possible<br>
<br>
&nbsp; &nbsp;- by making rw mibs more difficult to standardize WGs<br>
&nbsp; &nbsp; &nbsp;will be encouraged to use Yang / Netconf instead,<br>
&nbsp; &nbsp; &nbsp;presumably because Yang modules are cheaper to develop<br>
&nbsp; &nbsp; &nbsp;or because there has been a policy decision to favor<br>
&nbsp; &nbsp; &nbsp;that technology.<br>
<br>
&nbsp; &nbsp;- standardized configuration of any kind is expensive<br>
&nbsp; &nbsp; &nbsp;(in terms of WG resources) to develop and consequently<br>
&nbsp; &nbsp; &nbsp;should be discouraged in favor of whatever vendor-<br>
&nbsp; &nbsp; &nbsp;specific solutions might arise.<br>
<br>
I think all of these are lousy rationales, so I<br>
would welcome a more plausible explanation.<br>
<br>
Randy<br>
<br>
_______________________________________________<br>
MIB-DOCTORS mailing list<br>
<a href="mailto:MIB-DOCTORS@ietf.org">MIB-DOCTORS@ietf.org</a><br>
<a href="https://www.ietf.org/mailman/listinfo/mib-doctors" target="_blank">https://www.ietf.org/mailman/listinfo/mib-doctors</a><br>
</blockquote></div><br></div></div></div></div>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>MIB-DOCTORS mailing list</span><br><span><a href="mailto:MIB-DOCTORS@ietf.org">MIB-DOCTORS@ietf.org</a></span><br><span><a href="https://www.ietf.org/mailman/listinfo/mib-doctors">https://www.ietf.org/mailman/listinfo/mib-doctors</a></span><br></div></blockquote></body></html>
--Apple-Mail-454E47C9-A148-4AF8-802E-DA20AF66E14D--


From nobody Fri Feb 28 04:22:13 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 E82731A07C7; Fri, 28 Feb 2014 04:22:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.047
X-Spam-Level: 
X-Spam-Status: No, score=-10.047 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.547, 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 v-iNb2mirLdK; Fri, 28 Feb 2014 04:22:08 -0800 (PST)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) by ietfa.amsl.com (Postfix) with ESMTP id EFF051A07CB; Fri, 28 Feb 2014 04:20:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=12733; q=dns/txt; s=iport; t=1393590005; x=1394799605; h=message-id:date:from:mime-version:to:subject:references: in-reply-to; bh=NmNOZm1bj+W2XeVyrmoBJucdikFZJOXXMFtQt8LR2mE=; b=NZKFoKGynta+brKjmKnwqh86wk7xKdKcEO6nAsMWyGzYfNChXeh0J8vn bwwp2PZ3+B6SnJo1dz2XwDqRTEeE80epRElcRXKrdUPykk1i4Zj2706UG aOeXhkH2JUN7HzGnVo2QYEqi/5jonQqL2ciKvOK379vor++4ScZe21XLj I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AlAIAMN+EFOQ/khM/2dsb2JhbABagwY7iTe4PIETFnSCJQEBAQR4DQQcAwECChYPCQMCAQIBOwIIBgEMBgIBARCHZQ3LMBeNcxEBPxgGhDEEmDmBMoUYi2GDLTyBNQ
X-IronPort-AV: E=Sophos;i="4.97,561,1389744000"; d="scan'208,217";a="5791132"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by aer-iport-2.cisco.com with ESMTP; 28 Feb 2014 12:19:46 +0000
Received: from [10.61.206.166] ([10.61.206.166]) by ams-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id s1SCJk2O022190; Fri, 28 Feb 2014 12:19:46 GMT
Message-ID: <53107EE2.4080703@cisco.com>
Date: Fri, 28 Feb 2014 12:19:46 +0000
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: "MIB Doctors (E-mail)" <mib-doctors@ietf.org>, YANG Doctors <yang-doctors@ietf.org>
References: <53107BAF.2050808@cisco.com>
In-Reply-To: <53107BAF.2050808@cisco.com>
X-Forwarded-Message-Id: <53107BAF.2050808@cisco.com>
Content-Type: multipart/alternative; boundary="------------060207070602020707090705"
Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/rYbJT2Tdy0XlEupud5FYqXA-vhI
Subject: [MIB-DOCTORS] Fwd: configuration: writable MIB modules versus NETCONF/YANG modules - part 2
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, 28 Feb 2014 12:22:11 -0000

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

Dear all,

Hopefully, you are all part of the ops-area mailer, where the discussion 
should continue.

Regards, Benoit


-------- Original Message --------
Subject: 	configuration: writable MIB modules versus NETCONF/YANG 
modules - part 2
Date: 	Fri, 28 Feb 2014 12:06:07 +0000
From: 	Benoit Claise <bclaise@cisco.com>
To: 	ops-area@ietf.org <ops-area@ietf.org>



Dear all,

[I bcc'ed some people, with whom I discussed this issue privately. I 
want to make sure they're in the opsarea loop. Sorry, if you receive 
this email twice]

I discussed the following statement with the IESG. I ideally wanted to 
have this statement approved as an IESG statement before the beginning 
of the week, but I realize that it might need some more discussion among 
the OPS community...

    The OPS area recommends the use of NETCONF/YANG standards for
    configuration. IETF working groups are therefore encouraged to use
    the NETCONF/YANG standards for configuration, especially in new
    charters. SNMP MIB modules _creating and_ modifying persistent
    configuration state should only be produced by working groups in
    cases of clear utility and consensus to use SNMP write operations
    for configuration.

Btw, one IESG member insisted on having "_creating and_ modifying" 
instead of "modifying".

Let me focus on a more important issue.
First let me make sure that we agree on one terminology. The 
NETCONF/YANG terminology is in RFC 6244:

   o  Configuration data is the set of writable data that is required to
       transform a system from its initial default state into its current
       state [RFC4741  <http://tools.ietf.org/html/rfc4741>].

    o  Operational state data is a set of data that has been obtained by
       the system at runtime and influences the system's behavior similar
       to configuration data.  In contrast to configuration data,
       operational state is transient and modified by interactions with
       internal components or other systems via specialized protocols.

    o  Statistical data is the set of read-only data created by a system
       itself.  It describes the performance of the system and its
       components.

Operational state data is sometimes called ephemeral (or non-persistent 
configuration data), as opposed to the "configuration data" that is 
persistent.
See RFC 6244 section 4.3.2.x for some useful examples.

The statement has been carefully crafted to cover the 4 different cases:

           SNMP      NETCONF/YANG
+-----------------------------------------------------------------+--------------------------------------------------+
             Configuration data  | SHOULD NOT specify writable MIB 
modules    |  SHOULD use NETCONF/YANG          |
|-----------------------------------------------------------------+--------------------------------------------------|
      Operational State data  | Not clear guidelines at time point in 
time  (*)   |   SHOULD use NETCONF/YANG         |
+---------------------------------------------------------------------------------------------------------------------+ 


Let me focus on (*).
Some of you are telling: SNMPset is not enabled in networks, period. 
Don't specify new writable MIB modules, even for operational state data, 
it doesn't make sense.
Some others are telling: Note that this statement limits the discussion 
to configuration data. Note also that there is no standard way to modify 
operational state via NETCONF at this point in time (so it would be 
strange to discourage SNMP if there is no standardized alternative).

I believe we need some more discussion on this specific point. Please 
share your point of view:
- Should we keep the statement as it is, but better explain it? (which 
might require more background, so maybe a draft instead of a brief 
statement)
- Should we extend the statement and remove "persistent" from this 
sentence: SNMP MIB modules creating and modifying persistent 
configuration state should only be produced by working groups in cases 
of clear utility and consensus to use SNMP write operations for 
configuration?
- Something else?

Regards, Benoit







--------------060207070602020707090705
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 all,<br>
    <br>
    Hopefully, you are all part of the ops-area mailer, where the
    discussion should continue.<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>configuration: writable MIB modules versus NETCONF/YANG
              modules - part 2</td>
          </tr>
          <tr>
            <th align="RIGHT" nowrap="nowrap" valign="BASELINE">Date: </th>
            <td>Fri, 28 Feb 2014 12:06:07 +0000</td>
          </tr>
          <tr>
            <th align="RIGHT" nowrap="nowrap" valign="BASELINE">From: </th>
            <td>Benoit Claise <a class="moz-txt-link-rfc2396E" href="mailto:bclaise@cisco.com">&lt;bclaise@cisco.com&gt;</a></td>
          </tr>
          <tr>
            <th align="RIGHT" nowrap="nowrap" valign="BASELINE">To: </th>
            <td><a class="moz-txt-link-abbreviated" href="mailto:ops-area@ietf.org">ops-area@ietf.org</a> <a class="moz-txt-link-rfc2396E" href="mailto:ops-area@ietf.org">&lt;ops-area@ietf.org&gt;</a></td>
          </tr>
        </tbody>
      </table>
      <br>
      <br>
      <meta http-equiv="content-type" content="text/html;
        charset=ISO-8859-1">
      Dear all,<br>
      <br>
      [I bcc'ed some people, with whom I discussed this issue privately.
      I want to make sure they're in the opsarea loop. Sorry, if you
      receive this email twice]<br>
      <br>
      I discussed the following statement with the IESG. I ideally
      wanted to have this statement approved as an IESG statement before
      the beginning of the week, but I realize that it might need some
      more discussion among the OPS community...
      <blockquote>The OPS area recommends the use of NETCONF/YANG
        standards for configuration. IETF working groups are therefore
        encouraged to use the NETCONF/YANG standards for configuration,
        especially in new charters. SNMP MIB modules <u>creating and</u>
        modifying persistent configuration state should only be produced
        by working groups in cases of clear utility and consensus to use
        SNMP write operations for configuration.<br>
      </blockquote>
      Btw, one IESG member insisted on having "<u>creating and</u>
      modifying" instead of "modifying". <br>
      <br>
      Let me focus on a more important issue.<br>
      First let me make sure that we agree on one terminology. The
      NETCONF/YANG terminology is in RFC 6244:<br>
      <pre wrap="">  o  Configuration data is the set of writable data that is required to
      transform a system from its initial default state into its current
      state [<a moz-do-not-send="true" href="http://tools.ietf.org/html/rfc4741" title="&quot;NETCONF Configuration Protocol&quot;">RFC4741</a>].

   o  Operational state data is a set of data that has been obtained by
      the system at runtime and influences the system's behavior similar
      to configuration data.  In contrast to configuration data,
      operational state is transient and modified by interactions with
      internal components or other systems via specialized protocols.

   o  Statistical data is the set of read-only data created by a system
      itself.  It describes the performance of the system and its
      components. </pre>
      Operational state data is sometimes called ephemeral (or
      non-persistent configuration data), as opposed to the
      "configuration data" that is persistent.<br>
      See RFC 6244 section 4.3.2.x for some useful examples.<br>
      <br>
      The statement has been carefully crafted to cover the 4 different
      cases:<br>
      <br>
      &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
      &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; SNMP &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
      &nbsp; &nbsp;&nbsp; NETCONF/YANG <br>
      &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
+-----------------------------------------------------------------+--------------------------------------------------+<br>
      &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; Configuration data&nbsp; | SHOULD NOT specify writable MIB
      modules&nbsp; &nbsp; |&nbsp; SHOULD use NETCONF/YANG &nbsp; &nbsp;&nbsp; &nbsp; &nbsp; |<br>
      &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
|-----------------------------------------------------------------+--------------------------------------------------|<br>
      &nbsp;&nbsp;&nbsp;&nbsp; Operational State data&nbsp; | Not clear guidelines at time point
      in time&nbsp; (*) &nbsp; |&nbsp;&nbsp; SHOULD use NETCONF/YANG&nbsp; &nbsp; &nbsp; &nbsp;&nbsp; |<br>
      &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
      +---------------------------------------------------------------------------------------------------------------------+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;

      <br>
      <br>
      Let me focus on (*).<br>
      Some of you are telling: SNMPset is not enabled in networks,
      period. Don't specify new writable MIB modules, even for
      operational state data, it doesn't make sense.<br>
      Some others are telling: Note that this statement limits the
      discussion to configuration data. Note also that there is no
      standard way to modify operational state via NETCONF at this point
      in time (so it would be strange to discourage SNMP if there is no
      standardized alternative). <br>
      <br>
      I believe we need some more discussion on this specific point.&nbsp;
      Please share your point of view:<br>
      - Should we keep the statement as it is, but better explain it?
      (which might require more background, so maybe a draft instead of
      a brief statement)<br>
      - Should we extend the statement and remove "persistent" from this
      sentence: SNMP MIB modules creating and modifying persistent
      configuration state should only be produced by working groups in
      cases of clear utility and consensus to use SNMP write operations
      for configuration?<br>
      - Something else?<br>
      <br>
      Regards, Benoit<br>
      <br>
      <br>
      <br>
      <br>
      <br>
    </div>
    <br>
  </body>
</html>

--------------060207070602020707090705--


From nobody Fri Feb 28 05:52:07 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 0CAD31A049E for <mib-doctors@ietfa.amsl.com>; Fri, 28 Feb 2014 05:52:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Level: 
X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 7WBFd3EhsWi2 for <mib-doctors@ietfa.amsl.com>; Fri, 28 Feb 2014 05:52:02 -0800 (PST)
Received: from mail-qa0-f42.google.com (mail-qa0-f42.google.com [209.85.216.42]) by ietfa.amsl.com (Postfix) with ESMTP id BA7911A04A4 for <mib-doctors@ietf.org>; Fri, 28 Feb 2014 05:52:01 -0800 (PST)
Received: by mail-qa0-f42.google.com with SMTP id k15so660832qaq.1 for <mib-doctors@ietf.org>; Fri, 28 Feb 2014 05:51:59 -0800 (PST)
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=KnzDveEaAD8ECMSA+Ttitw40F1ZkOIUOgCYqng7uKZU=; b=N+6R27v3pnn6EGo4HXcd/vyZE8mWobei+BLbpWF4xbNWnY3sIveaZZJtzW0dwsRVJo Yts1xTzkUng/Qh6JjflNQ2Za54JHqDHLaaYfiN7YuQ0QkEIwvZQP1E7gicENKW3GZrtP Fo6HWe8a5ADUmpE2WwFTa1LxGOgaDfQAZybg9p3nPvC/uJ7GrkHxc55/6B8OPpvz/z36 qwQj5YVyfe9a2WSrdD2/10ylOG1fRlTebF02I78lqvHyoCCxpodhDxDUUc6QEDJ1hMPP kZBPxh/ymoazcsOKM5cp7whAk7DQcKFGiMw+zSn3SV1wPo4RCflDMRbHvZKYEjAQdkkD RlOQ==
X-Gm-Message-State: ALoCoQn56n7KmV3sVDF9VgpccklwnXI4xIhHSl8kPh520SD7pivGW2HqZ9cZp1OL1sUABWSVrKQX
MIME-Version: 1.0
X-Received: by 10.140.87.9 with SMTP id q9mr3470850qgd.94.1393595519719; Fri, 28 Feb 2014 05:51:59 -0800 (PST)
Received: by 10.140.104.194 with HTTP; Fri, 28 Feb 2014 05:51:59 -0800 (PST)
In-Reply-To: <53107EE2.4080703@cisco.com>
References: <53107BAF.2050808@cisco.com> <53107EE2.4080703@cisco.com>
Date: Fri, 28 Feb 2014 05:51:59 -0800
Message-ID: <CABCOCHSGtdQNWEvZwr6S1rDcN=8CNkxcqBbmhu4abBuY34mf-Q@mail.gmail.com>
From: Andy Bierman <andy@yumaworks.com>
To: Benoit Claise <bclaise@cisco.com>
Content-Type: multipart/alternative; boundary=001a113a359cea257804f377bdca
Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/54kIwZUJVTKqrYp-X_nE2dwuF2Y
Cc: "MIB Doctors \(E-mail\)" <mib-doctors@ietf.org>, YANG Doctors <yang-doctors@ietf.org>
Subject: Re: [MIB-DOCTORS] Fwd: configuration: writable MIB modules versus NETCONF/YANG modules - part 2
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, 28 Feb 2014 13:52:05 -0000

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

Hi,

I think we are entering new territory wrt/ editing what has traditionally
been read-only data.
There have always been "actions with side effects", e.g. a "clear-counters"
operation.
People seem to want a more direct management model, but down in the code it
is basically the same.

The definition of "config data" has a very real impact on YANG XPath.
We explicitly forbid must/when conditionals for config data to reference
non-config data. This is (IMO) due to the perception that config is stable
and operational state is not, and implementing must/when is intractable
if it includes operational state.

>From a security POV, editing operational state seems scary hard.
The opportunities to mess with a system and stay under the radar
are almost unbounded.

So far, the NETCONF community has not even figured out how to
audit all these changes.  How do I know if a hacker set those RIB
entries with I2RS or if a routing protocol did it?  Maybe the I2RS
folks will make better progress on these issues.

I don't think SNMP actually meets many of the requirements
posed by I2RS-ARCH. NETCONF is currently much closer.
Nobody has actually proposed that I2RS use SNMP, so it
is odd that this topic even came up.


Andy


On Fri, Feb 28, 2014 at 4:19 AM, Benoit Claise <bclaise@cisco.com> wrote:

>  Dear all,
>
> Hopefully, you are all part of the ops-area mailer, where the discussion
> should continue.
>
> Regards, Benoit
>
>
> -------- Original Message --------  Subject: configuration: writable MIB
> modules versus NETCONF/YANG modules - part 2  Date: Fri, 28 Feb 2014
> 12:06:07 +0000  From: Benoit Claise <bclaise@cisco.com><bclaise@cisco.com>  To:
> ops-area@ietf.org <ops-area@ietf.org> <ops-area@ietf.org>
>
> Dear all,
>
> [I bcc'ed some people, with whom I discussed this issue privately. I want
> to make sure they're in the opsarea loop. Sorry, if you receive this email
> twice]
>
> I discussed the following statement with the IESG. I ideally wanted to
> have this statement approved as an IESG statement before the beginning of
> the week, but I realize that it might need some more discussion among the
> OPS community...
>
> The OPS area recommends the use of NETCONF/YANG standards for
> configuration. IETF working groups are therefore encouraged to use the
> NETCONF/YANG standards for configuration, especially in new charters. SNMP
> MIB modules *creating and* modifying persistent configuration state
> should only be produced by working groups in cases of clear utility and
> consensus to use SNMP write operations for configuration.
>
> Btw, one IESG member insisted on having "*creating and* modifying"
> instead of "modifying".
>
> Let me focus on a more important issue.
> First let me make sure that we agree on one terminology. The NETCONF/YANG
> terminology is in RFC 6244:
>
>   o  Configuration data is the set of writable data that is required to
>       transform a system from its initial default state into its current
>       state [RFC4741 <http://tools.ietf.org/html/rfc4741>].
>
>    o  Operational state data is a set of data that has been obtained by
>       the system at runtime and influences the system's behavior similar
>       to configuration data.  In contrast to configuration data,
>       operational state is transient and modified by interactions with
>       internal components or other systems via specialized protocols.
>
>    o  Statistical data is the set of read-only data created by a system
>       itself.  It describes the performance of the system and its
>       components.
>
> Operational state data is sometimes called ephemeral (or non-persistent
> configuration data), as opposed to the "configuration data" that is
> persistent.
> See RFC 6244 section 4.3.2.x for some useful examples.
>
> The statement has been carefully crafted to cover the 4 different cases:
>
>
>   SNMP                                                         NETCONF/YANG
>
> +-----------------------------------------------------------------+--------------------------------------------------+
>             Configuration data  | SHOULD NOT specify writable MIB modules
>   |  SHOULD use NETCONF/YANG          |
>
> |-----------------------------------------------------------------+--------------------------------------------------|
>      Operational State data  | Not clear guidelines at time point in time
> (*)   |   SHOULD use NETCONF/YANG         |
>
> +---------------------------------------------------------------------------------------------------------------------+
>
>
> Let me focus on (*).
> Some of you are telling: SNMPset is not enabled in networks, period. Don't
> specify new writable MIB modules, even for operational state data, it
> doesn't make sense.
> Some others are telling: Note that this statement limits the discussion to
> configuration data. Note also that there is no standard way to modify
> operational state via NETCONF at this point in time (so it would be strange
> to discourage SNMP if there is no standardized alternative).
>
> I believe we need some more discussion on this specific point.  Please
> share your point of view:
> - Should we keep the statement as it is, but better explain it? (which
> might require more background, so maybe a draft instead of a brief
> statement)
> - Should we extend the statement and remove "persistent" from this
> sentence: SNMP MIB modules creating and modifying persistent configuration
> state should only be produced by working groups in cases of clear utility
> and consensus to use SNMP write operations for configuration?
> - Something else?
>
> Regards, Benoit
>
>
>
>
>
>
>
> _______________________________________________
> MIB-DOCTORS mailing list
> MIB-DOCTORS@ietf.org
> https://www.ietf.org/mailman/listinfo/mib-doctors
>
>

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

<div dir=3D"ltr">Hi,<div><br><div>I think we are entering new territory wrt=
/ editing what has traditionally been read-only data.</div><div>There have =
always been &quot;actions with side effects&quot;, e.g. a &quot;clear-count=
ers&quot; operation.</div>
<div>People seem to want a more direct management model, but down in the co=
de it</div><div>is basically the same.=A0</div><div><br></div><div>The defi=
nition of &quot;config data&quot; has a very real impact on YANG XPath.</di=
v>
<div>We explicitly forbid must/when conditionals for config data to referen=
ce</div><div>non-config data. This is (IMO) due to the perception that conf=
ig is stable</div><div>and operational state is not, and implementing must/=
when is intractable</div>
<div>if it includes operational state.</div><div><br></div><div><div class=
=3D"gmail_extra">From a security POV, editing operational state seems scary=
 hard.</div><div class=3D"gmail_extra">The opportunities to mess with a sys=
tem and stay under the radar</div>
<div class=3D"gmail_extra">are almost unbounded.</div><div class=3D"gmail_e=
xtra"><br></div><div class=3D"gmail_extra">So far, the NETCONF community ha=
s not even figured out how to</div><div class=3D"gmail_extra">audit all the=
se changes. =A0How do I know if a hacker set those RIB</div>
<div class=3D"gmail_extra">entries with I2RS or if a routing protocol did i=
t? =A0Maybe the I2RS</div><div class=3D"gmail_extra">folks will make better=
 progress on these issues.</div><div class=3D"gmail_extra"><br></div><div c=
lass=3D"gmail_extra">
I don&#39;t think SNMP actually meets many of the requirements</div><div cl=
ass=3D"gmail_extra">posed by I2RS-ARCH. NETCONF is currently much closer.</=
div><div class=3D"gmail_extra">Nobody has actually proposed that I2RS use S=
NMP, so it</div>
<div class=3D"gmail_extra">is odd that this topic even came up.</div><div c=
lass=3D"gmail_extra"><br></div><div class=3D"gmail_extra"><br></div><div cl=
ass=3D"gmail_extra">Andy</div><div class=3D"gmail_extra"><br><br><div class=
=3D"gmail_quote">
On Fri, Feb 28, 2014 at 4:19 AM, Benoit Claise <span dir=3D"ltr">&lt;<a hre=
f=3D"mailto:bclaise@cisco.com" target=3D"_blank">bclaise@cisco.com</a>&gt;<=
/span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8=
ex;border-left:1px #ccc solid;padding-left:1ex">

 =20

   =20
 =20
  <div bgcolor=3D"#FFFFFF" text=3D"#000000">
    Dear all,<br>
    <br>
    Hopefully, you are all part of the ops-area mailer, where the
    discussion should continue.<br>
    <br>
    Regards, Benoit<br>
    <div><br>
      <br>
      -------- Original Message --------
      <table cellpadding=3D"0" cellspacing=3D"0" border=3D"0">
        <tbody>
          <tr>
            <th align=3D"RIGHT" nowrap valign=3D"BASELINE">Subject:
            </th>
            <td>configuration: writable MIB modules versus NETCONF/YANG
              modules - part 2</td>
          </tr>
          <tr>
            <th align=3D"RIGHT" nowrap valign=3D"BASELINE">Date: </th>
            <td>Fri, 28 Feb 2014 12:06:07 +0000</td>
          </tr>
          <tr>
            <th align=3D"RIGHT" nowrap valign=3D"BASELINE">From: </th>
            <td>Benoit Claise <a href=3D"mailto:bclaise@cisco.com" target=
=3D"_blank">&lt;bclaise@cisco.com&gt;</a></td>
          </tr>
          <tr>
            <th align=3D"RIGHT" nowrap valign=3D"BASELINE">To: </th>
            <td><a href=3D"mailto:ops-area@ietf.org" target=3D"_blank">ops-=
area@ietf.org</a> <a href=3D"mailto:ops-area@ietf.org" target=3D"_blank">&l=
t;ops-area@ietf.org&gt;</a></td>
          </tr>
        </tbody>
      </table>
      <br>
      <br>
     =20
      Dear all,<br>
      <br>
      [I bcc&#39;ed some people, with whom I discussed this issue privately=
.
      I want to make sure they&#39;re in the opsarea loop. Sorry, if you
      receive this email twice]<br>
      <br>
      I discussed the following statement with the IESG. I ideally
      wanted to have this statement approved as an IESG statement before
      the beginning of the week, but I realize that it might need some
      more discussion among the OPS community...
      <blockquote>The OPS area recommends the use of NETCONF/YANG
        standards for configuration. IETF working groups are therefore
        encouraged to use the NETCONF/YANG standards for configuration,
        especially in new charters. SNMP MIB modules <u>creating and</u>
        modifying persistent configuration state should only be produced
        by working groups in cases of clear utility and consensus to use
        SNMP write operations for configuration.<br>
      </blockquote>
      Btw, one IESG member insisted on having &quot;<u>creating and</u>
      modifying&quot; instead of &quot;modifying&quot;. <br>
      <br>
      Let me focus on a more important issue.<br>
      First let me make sure that we agree on one terminology. The
      NETCONF/YANG terminology is in RFC 6244:<br>
      <pre>  o  Configuration data is the set of writable data that is requ=
ired to
      transform a system from its initial default state into its current
      state [<a href=3D"http://tools.ietf.org/html/rfc4741" title=3D"&quot;=
NETCONF Configuration Protocol&quot;" target=3D"_blank">RFC4741</a>].

   o  Operational state data is a set of data that has been obtained by
      the system at runtime and influences the system&#39;s behavior simila=
r
      to configuration data.  In contrast to configuration data,
      operational state is transient and modified by interactions with
      internal components or other systems via specialized protocols.

   o  Statistical data is the set of read-only data created by a system
      itself.  It describes the performance of the system and its
      components. </pre>
      Operational state data is sometimes called ephemeral (or
      non-persistent configuration data), as opposed to the
      &quot;configuration data&quot; that is persistent.<br>
      See RFC 6244 section 4.3.2.x for some useful examples.<br>
      <br>
      The statement has been carefully crafted to cover the 4 different
      cases:<br>
      <br>
      =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0 =A0 =A0 =A0 =A0 =A0
      =A0 =A0 =A0 =A0 =A0 SNMP =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 =
=A0 =A0 =A0 =A0 =A0 =A0
      =A0 =A0=A0 NETCONF/YANG <br>
      =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0
+-----------------------------------------------------------------+--------=
------------------------------------------+<br>
      =A0=A0=A0 =A0=A0=A0 =A0=A0=A0 Configuration data=A0 | SHOULD NOT spec=
ify writable MIB
      modules=A0 =A0 |=A0 SHOULD use NETCONF/YANG =A0 =A0=A0 =A0 =A0 |<br>
      =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0
|-----------------------------------------------------------------+--------=
------------------------------------------|<br>
      =A0=A0=A0=A0 Operational State data=A0 | Not clear guidelines at time=
 point
      in time=A0 (*) =A0 |=A0=A0 SHOULD use NETCONF/YANG=A0 =A0 =A0 =A0=A0 =
|<br>
      =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0
      +--------------------------------------------------------------------=
-------------------------------------------------+=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0

      <br>
      <br>
      Let me focus on (*).<br>
      Some of you are telling: SNMPset is not enabled in networks,
      period. Don&#39;t specify new writable MIB modules, even for
      operational state data, it doesn&#39;t make sense.<br>
      Some others are telling: Note that this statement limits the
      discussion to configuration data. Note also that there is no
      standard way to modify operational state via NETCONF at this point
      in time (so it would be strange to discourage SNMP if there is no
      standardized alternative). <br>
      <br>
      I believe we need some more discussion on this specific point.=A0
      Please share your point of view:<br>
      - Should we keep the statement as it is, but better explain it?
      (which might require more background, so maybe a draft instead of
      a brief statement)<br>
      - Should we extend the statement and remove &quot;persistent&quot; fr=
om this
      sentence: SNMP MIB modules creating and modifying persistent
      configuration state should only be produced by working groups in
      cases of clear utility and consensus to use SNMP write operations
      for configuration?<br>
      - Something else?<br>
      <br>
      Regards, Benoit<br>
      <br>
      <br>
      <br>
      <br>
      <br>
    </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></div>

--001a113a359cea257804f377bdca--

