
From nobody Wed Jul  2 21:21:44 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 D707D1A0370 for <mib-doctors@ietfa.amsl.com>; Wed,  2 Jul 2014 21:21:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.278
X-Spam-Level: 
X-Spam-Status: No, score=-1.278 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uwoPGbBp4-Wl for <mib-doctors@ietfa.amsl.com>; Wed,  2 Jul 2014 21:21:30 -0700 (PDT)
Received: from mail-qg0-f42.google.com (mail-qg0-f42.google.com [209.85.192.42]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E9C231A01DD for <mib-doctors@ietf.org>; Wed,  2 Jul 2014 21:21:29 -0700 (PDT)
Received: by mail-qg0-f42.google.com with SMTP id e89so5674044qgf.1 for <mib-doctors@ietf.org>; Wed, 02 Jul 2014 21:21:29 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to :content-type; bh=XTCnrEGkq//YvEzX7MnNzbcc79Oi7NUh7oxMJwqZYyY=; b=O8PaviU7lZDM77UH6HKhc1315RlUpYI9tbN2KREEua0f1hcZc5SSb3neKW6AbVdJ8r XXarUb5AOKJYRGN/6PJ1iv8HVahEbG9co/HUlBaamlKMxmTaUzNh4UT6+HK7DzCj/8nL u8jV1MA+IBz4kRn6G9dykuknw8/6aGdsVOkMMYS6yLXTKAu/Mp+rkLY2QKjRDo4TisNt YBiL6r8B/DXjb2kFDRYugXnaGq2gQ3Q68uWUzYgIOV5DFFdZ4BvkLGPn52ZDqiUzUdnj lAVFsbV7ce+2TUFrkdJrq0BG6OC0aaZyF2ELp4+36wqIfnlrBejMDZVj7j0NgAbcUBoT kGyg==
X-Gm-Message-State: ALoCoQlGRSiVSUXPpJz3CjbYiQ5BP+Nf+fkV05FQ0p122c2bGLEzty0ZouQ913gPEoqHSFtLeThu
MIME-Version: 1.0
X-Received: by 10.224.22.12 with SMTP id l12mr3502944qab.88.1404361289079; Wed, 02 Jul 2014 21:21:29 -0700 (PDT)
Received: by 10.140.104.48 with HTTP; Wed, 2 Jul 2014 21:21:29 -0700 (PDT)
Date: Wed, 2 Jul 2014 21:21:29 -0700
Message-ID: <CABCOCHRi51P_Q9N2_G19+=uZYTBQdNrJ-wSadrOVTxSxrk+Shg@mail.gmail.com>
From: Andy Bierman <andy@yumaworks.com>
To: YANG Doctors <yang-doctors@ietf.org>, "MIB Doctors (E-mail)" <mib-doctors@ietf.org>,  Benoit Claise <bclaise@cisco.com>
Content-Type: multipart/alternative; boundary=047d7bf0e59cc5b3cb04fd4257df
Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/f6nVNC7xmv9kdIyxMP0LFKCf9Y0
Subject: [MIB-DOCTORS] New NETCONF/YANG tutorial
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, 03 Jul 2014 04:21:40 -0000

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

Hi,

I wrote a free tutorial called "A Guide to NETCONF for SNMP Developers".
http://dld.netconfcentral.org/doc/ncorg_netconf_yang_tutorial.pdf

It is 122 slides and it isn't done ;-)
I hoping some YANG and MIB doctors will have some time
to review it.  I need to present the basic sections (1 - 3) at
an IEEE conference in less than 2 weeks, so any bugfixes,
comments, other insights, etc. before July 10 would be greatly appreciated.


thanks,
Andy

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

<div dir=3D"ltr">Hi,<div><br></div><div>I wrote a free tutorial called &quo=
t;A Guide to NETCONF for SNMP Developers&quot;.</div><div><a href=3D"http:/=
/dld.netconfcentral.org/doc/ncorg_netconf_yang_tutorial.pdf">http://dld.net=
confcentral.org/doc/ncorg_netconf_yang_tutorial.pdf</a><br>
</div><div><br></div><div>It is 122 slides and it isn&#39;t done ;-)</div><=
div>I hoping some YANG and MIB doctors will have some time</div><div>to rev=
iew it. =A0I need to present the basic sections (1 - 3) at</div><div>an IEE=
E conference in less than 2 weeks, so any bugfixes,</div>
<div>comments, other insights, etc. before July 10 would be greatly appreci=
ated.</div><div><br></div><div><br></div><div>thanks,</div><div>Andy</div><=
div><br></div></div>

--047d7bf0e59cc5b3cb04fd4257df--


From nobody Wed Jul  2 23:00:22 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 387681A0A8A; Wed,  2 Jul 2014 23:00:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.201
X-Spam-Level: 
X-Spam-Status: No, score=-2.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RP_MATCHES_RCVD=-0.651] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id erjg3c4tc5Zj; Wed,  2 Jul 2014 23:00:16 -0700 (PDT)
Received: from atlas3.jacobs-university.de (atlas3.jacobs-university.de [212.201.44.18]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A069B1A00F5; Wed,  2 Jul 2014 23:00:16 -0700 (PDT)
Received: from localhost (demetrius5.irc-it.jacobs-university.de [10.70.0.222]) by atlas3.jacobs-university.de (Postfix) with ESMTP id EA361734; Thu,  3 Jul 2014 08:00:13 +0200 (CEST)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from atlas3.jacobs-university.de ([10.70.0.220]) by localhost (demetrius5.jacobs-university.de [10.70.0.222]) (amavisd-new, port 10030) with ESMTP id wXkxiJqSfMnq; Thu,  3 Jul 2014 07:59:58 +0200 (CEST)
Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hermes.jacobs-university.de", Issuer "Jacobs University CA - G01" (verified OK)) by atlas3.jacobs-university.de (Postfix) with ESMTPS; Thu,  3 Jul 2014 08:00:13 +0200 (CEST)
Received: from localhost (demetrius3.jacobs-university.de [212.201.44.48]) by hermes.jacobs-university.de (Postfix) with ESMTP id E845620054; Thu,  3 Jul 2014 08:00:13 +0200 (CEST)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius3.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id M6uiufomhnQp; Thu,  3 Jul 2014 08:00:12 +0200 (CEST)
Received: from elstar.local (elstar.jacobs.jacobs-university.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id BBFF920057; Thu,  3 Jul 2014 08:00:10 +0200 (CEST)
Received: by elstar.local (Postfix, from userid 501) id 2580C2DA0833; Thu,  3 Jul 2014 08:00:08 +0200 (CEST)
Date: Thu, 3 Jul 2014 08:00:08 +0200
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: Andy Bierman <andy@yumaworks.com>
Message-ID: <20140703060008.GA40306@elstar.local>
Mail-Followup-To: Andy Bierman <andy@yumaworks.com>, YANG Doctors <yang-doctors@ietf.org>, "MIB Doctors (E-mail)" <mib-doctors@ietf.org>, Benoit Claise <bclaise@cisco.com>
References: <CABCOCHRi51P_Q9N2_G19+=uZYTBQdNrJ-wSadrOVTxSxrk+Shg@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CABCOCHRi51P_Q9N2_G19+=uZYTBQdNrJ-wSadrOVTxSxrk+Shg@mail.gmail.com>
User-Agent: Mutt/1.4.2.3i
Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/A58zf9bWptln6_nLuKeDwPofd9U
Cc: YANG Doctors <yang-doctors@ietf.org>, "MIB Doctors \(E-mail\)" <mib-doctors@ietf.org>
Subject: Re: [MIB-DOCTORS] [yang-doctors] New NETCONF/YANG tutorial
X-BeenThere: mib-doctors@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
List-Id: MIB Doctors list <mib-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mib-doctors/>
List-Post: <mailto:mib-doctors@ietf.org>
List-Help: <mailto:mib-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Jul 2014 06:00:19 -0000

On Wed, Jul 02, 2014 at 09:21:29PM -0700, Andy Bierman wrote:
> Hi,
> 
> I wrote a free tutorial called "A Guide to NETCONF for SNMP Developers".
> http://dld.netconfcentral.org/doc/ncorg_netconf_yang_tutorial.pdf
> 

This is good stuff. Something I spotted on slide 75: I think SNMPv3
has way more than 3 error codes (and even SNMPv1 had more than 3).

/js

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


From nobody Thu Jul  3 00:14:34 2014
Return-Path: <mbj@tail-f.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 292F01A007A; Thu,  3 Jul 2014 00:14:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.552
X-Spam-Level: 
X-Spam-Status: No, score=-2.552 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ImA3-eRBz3Nc; Thu,  3 Jul 2014 00:14:28 -0700 (PDT)
Received: from mail.tail-f.com (mail.tail-f.com [83.241.162.140]) by ietfa.amsl.com (Postfix) with ESMTP id 3D54E1A006F; Thu,  3 Jul 2014 00:14:28 -0700 (PDT)
Received: from localhost (x15.tail-f.com [192.168.1.60]) by mail.tail-f.com (Postfix) with ESMTPSA id B14B712806AF; Thu,  3 Jul 2014 09:11:19 +0200 (CEST)
Date: Thu, 03 Jul 2014 09:14:23 +0200 (CEST)
Message-Id: <20140703.091423.2283970538774793528.mbj@tail-f.com>
To: andy@yumaworks.com
From: Martin Bjorklund <mbj@tail-f.com>
In-Reply-To: <CABCOCHRi51P_Q9N2_G19+=uZYTBQdNrJ-wSadrOVTxSxrk+Shg@mail.gmail.com>
References: <CABCOCHRi51P_Q9N2_G19+=uZYTBQdNrJ-wSadrOVTxSxrk+Shg@mail.gmail.com>
X-Mailer: Mew version 6.5 on Emacs 23.4 / Mule 6.0 (HANACHIRUSATO)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/X-JDA01-6QW7e8A8xZOXTM3hXKE
Cc: yang-doctors@ietf.org, mib-doctors@ietf.org
Subject: Re: [MIB-DOCTORS] [yang-doctors] New NETCONF/YANG tutorial
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, 03 Jul 2014 07:14:30 -0000

Andy Bierman <andy@yumaworks.com> wrote:
> Hi,
> 
> I wrote a free tutorial called "A Guide to NETCONF for SNMP Developers".
> http://dld.netconfcentral.org/doc/ncorg_netconf_yang_tutorial.pdf
> 
> It is 122 slides and it isn't done ;-)

Let me know when its done and I'll update yang-central with a link to
this presentation.

> I hoping some YANG and MIB doctors will have some time
> to review it.  I need to present the basic sections (1 - 3) at
> an IEEE conference in less than 2 weeks, so any bugfixes,
> comments, other insights, etc. before July 10 would be greatly appreciated.

This looks very good!  I like the slides where you show SMIv2 vs YANG
and SNMP vs NETCONF on the same slide; it gives a good overview.

Some comments:

- slide 13/14: to be fair to snmp there are other transports
  *defined*.  but I guess it is correct to say udp here since it's
  certainly the most deployed transport.

- slide 24: could you write the link as http://www.yang-central.org?
  The twiki part might change...

- slide 32: you may want to expand the YANG example so people don't
  have to guess the blanks, something like:

     module radius-accounting-server {
       ...
       rpc config-reset {
         description "...";
       }
       leaf server-state {
         config false;
         type enumeration {
           enum other;
           enum initializing;
           enum running;
         }
       }

  (good point about the dual purpose!)

- slide 38: in order to avoid information overflow, consider removing
  bullets 4,5, and 7.

- slide 42: [side note: I think it is a bug that ok and rpc-error of
  type warning cannot be returned at the same time...]

- slide 53: "foo" + bar + 'baz' is not allowed:

     If a quoted string is followed by a plus character ("+"),
     followed by another quoted string, the two strings are
     concatenated into one string,
   
  (for some reason...)

- slide 65-67: remove XSD column?

- slide 75: s/error-app-info/error-app-tag/



General comment: risk of information overflow?  sometimes the slides
contains all details - which of course is correct but you may consider
removing less important details.




/martin


From nobody Thu Jul  3 02:08:07 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 C60CF1B27FA; Thu,  3 Jul 2014 02:08:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.3
X-Spam-Level: 
X-Spam-Status: No, score=-1.3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_12=0.6] 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 B_qd5WjuNtyd; Thu,  3 Jul 2014 02:08:04 -0700 (PDT)
Received: from koko.ripe.net (koko.ripe.net [IPv6:2001:67c:2e8:11::c100:1348]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 42F8A1B27EC; Thu,  3 Jul 2014 02:08:04 -0700 (PDT)
Received: from titi.ripe.net ([193.0.23.11]) by koko.ripe.net with esmtps (UNKNOWN:AES256-GCM-SHA384:256) (Exim 4.72) (envelope-from <bertietf@bwijnen.net>) id 1X2czn-00058q-R7; Thu, 03 Jul 2014 11:08:01 +0200
Received: from kitten.ripe.net ([2001:67c:2e8:1::c100:1f0] helo=macintosh-5.fritz.box) by titi.ripe.net with esmtp (Exim 4.72) (envelope-from <bertietf@bwijnen.net>) id 1X2czn-0003LH-NL; Thu, 03 Jul 2014 11:07:59 +0200
Message-ID: <53B51D6F.9020504@bwijnen.net>
Date: Thu, 03 Jul 2014 11:07:59 +0200
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.5.0
MIME-Version: 1.0
To: Andy Bierman <andy@yumaworks.com>, YANG Doctors <yang-doctors@ietf.org>, "MIB Doctors (E-mail)" <mib-doctors@ietf.org>,  Benoit Claise <bclaise@cisco.com>
References: <CABCOCHRi51P_Q9N2_G19+=uZYTBQdNrJ-wSadrOVTxSxrk+Shg@mail.gmail.com>
In-Reply-To: <CABCOCHRi51P_Q9N2_G19+=uZYTBQdNrJ-wSadrOVTxSxrk+Shg@mail.gmail.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
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: 86ab03e524994f79ca2c75a176445dd4d785f8f76bd90a2a15568ab36cab918b
Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/w0wnVc4Qz0hE-FzbLS0bdaGOz9E
Subject: Re: [MIB-DOCTORS] [yang-doctors] New NETCONF/YANG tutorial
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, 03 Jul 2014 09:08:06 -0000

I like it. Looks like there is lots for me to refresh my mind.

Are you also planning to give this tutorial at an IETF EDU session
or maybe WG chairs lunch?

120+ slides. I normally calculate an average of 2 minutes per slide.
So that would make for 240 minutes or 4 hours. Add a couple of breaks
and it gets to 5-6 hours. Or a day for normal training days.

It has copyright Yumaworks. I understand that... but
Can other yang doctors/yang proponents still use the slides?

most of this is probably nits. But here it goes anyways.

On slide 2 I see reference to an IESG statement. Do you mean
     http://www.ietf.org/iesg/statement/writable-mib-module.html
You might want to add the ptr

around slide 40 I see several times:

     module example-mod {
        namespace “http://example.com/ns/example-mod”;
        prefix “sys”;

Why prefix "sys" ?? Would it not be better to use something aka: prefix "xmpl"
so s to indicate that you would normally use a prefix that is easy to link
up with (or remember what is) the full namespace?
Specifically sys might also collide with prefixes we have used i(or may use) n IETF, no?

Not sure I understand 2nd bullet (and sub bullets) on slide 55.
Probably my lack of YANG knowledge. But the slide does not help either.
May also be clearer if you do slides about "must" and "when" earlier.
They now show up as slides 72/73.
Begs the question: is the target audience complete novices or do we expect
them to have read the RFCs? If so, you might want to add that as a slide
at the very beginning. However, I think we should make this digestable for
those who are novice to NetConf but do have some skill in SNMP and SMI.

slide 60
    mmm the term "body statements"... is that well defined?
    in rfc6020, section 4.2.1 I see:

    .... the definition statements are
    the body of the module where the data model is defined

Is that what you refer to? cause from the RFC6020 I would think they
are "definition statements" instead of "body statements".

This slideset plus the demo that Juergen once did in a OPSAREA session
makes a great introduction to NETCONF and YANG (I think).

Bert

On 03/07/14 06:21, Andy Bierman wrote:
> Hi,
>
> I wrote a free tutorial called "A Guide to NETCONF for SNMP Developers".
> http://dld.netconfcentral.org/doc/ncorg_netconf_yang_tutorial.pdf
>
> It is 122 slides and it isn't done ;-)
> I hoping some YANG and MIB doctors will have some time
> to review it.  I need to present the basic sections (1 - 3) at
> an IEEE conference in less than 2 weeks, so any bugfixes,
> comments, other insights, etc. before July 10 would be greatly appreciated.
>
>
> thanks,
> Andy
>
>
>
> _______________________________________________
> yang-doctors mailing list
> yang-doctors@ietf.org
> https://www.ietf.org/mailman/listinfo/yang-doctors
>


From nobody Thu Jul  3 03:47: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 BAE8B1B283B; Thu,  3 Jul 2014 03:47:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.551
X-Spam-Level: 
X-Spam-Status: No, score=-2.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mR32XEVLXs3d; Thu,  3 Jul 2014 03:47:10 -0700 (PDT)
Received: from p-us1-iereast-outbound.us1.avaya.com (p-us1-iereast-outbound.us1.avaya.com [135.11.29.13]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0811D1B2829; Thu,  3 Jul 2014 03:47:09 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhAMADU0tVPGmAcV/2dsb2JhbABagmkkUlqrPAECAQEBBpJ4HAiHOQGBCRZ1hAMBAQEBAQEBAQEBDyguBgsFBwQCAQgNAQMEAQEBChQJBycLFAkIAgQBDQUIGogYCAEMoW+mPheFcIkBMQcGgyeBFgWWVYtPjFODQ2yBRA
X-IronPort-AV: E=Sophos;i="5.01,594,1400040000"; d="scan'208";a="74602441"
Received: from unknown (HELO co300216-co-erhwest-exch.avaya.com) ([198.152.7.21]) by p-us1-iereast-outbound.us1.avaya.com with ESMTP; 03 Jul 2014 06:46:56 -0400
X-OutboundMail_SMTP: 1
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; 03 Jul 2014 06:27:12 -0400
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; Thu, 3 Jul 2014 12:46:55 +0200
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: Martin Bjorklund <mbj@tail-f.com>, "andy@yumaworks.com" <andy@yumaworks.com>
Thread-Topic: [yang-doctors] New NETCONF/YANG tutorial
Thread-Index: AQHPlnZI4F8kpKbEjkWD9wxYazB8pZuOMvaA///2mbA=
Date: Thu, 3 Jul 2014 10:46:54 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA5C825D00@AZ-FFEXMB04.global.avaya.com>
References: <CABCOCHRi51P_Q9N2_G19+=uZYTBQdNrJ-wSadrOVTxSxrk+Shg@mail.gmail.com> <20140703.091423.2283970538774793528.mbj@tail-f.com>
In-Reply-To: <20140703.091423.2283970538774793528.mbj@tail-f.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/--NbNCJIZx9fb4O27CsjLM33pRI
Cc: "yang-doctors@ietf.org" <yang-doctors@ietf.org>, "mib-doctors@ietf.org" <mib-doctors@ietf.org>
Subject: Re: [MIB-DOCTORS] [yang-doctors] New NETCONF/YANG tutorial
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, 03 Jul 2014 10:47:11 -0000

To the latest issue raised by Martin (risk of information overflow)

As Andy pointed, one of the motivations of this preso is a tutorial the IET=
F was invited to give at the IEEE 802 meeting the week of 7/14, that Andy g=
raciously took upon himself preparing.=20

At the IEEE meeting he's got 90 min to present, including Q&A. We expect pa=
rt of the audience to be composed of IEEE folks developing MIB modules , ma=
ny of them with r/w capabilities.=20

The plan is to focus on sections 1-3. Even so it may be too many slides, so=
 the tactics are to flip only the slides that contain details and examples,=
 focusing on the differences between SNMP and NETCONF, SMI and YANG, and th=
e reasons the IETF embarked on the path of NETCONF/YANG.=20

The morning after Andy will be available at the IEEE plenary for discussion=
s and answering more detailed questions.=20

Regards,

Dan

> -----Original Message-----
> From: yang-doctors [mailto:yang-doctors-bounces@ietf.org] On Behalf Of
> Martin Bjorklund
> Sent: Thursday, July 03, 2014 10:14 AM
> To: andy@yumaworks.com
> Cc: yang-doctors@ietf.org; mib-doctors@ietf.org
> Subject: Re: [yang-doctors] New NETCONF/YANG tutorial
>=20
> Andy Bierman <andy@yumaworks.com> wrote:
> > Hi,
> >
> > I wrote a free tutorial called "A Guide to NETCONF for SNMP Developers"=
.
> > http://dld.netconfcentral.org/doc/ncorg_netconf_yang_tutorial.pdf
> >
> > It is 122 slides and it isn't done ;-)
>=20
> Let me know when its done and I'll update yang-central with a link to thi=
s
> presentation.
>=20
> > I hoping some YANG and MIB doctors will have some time to review it.
> > I need to present the basic sections (1 - 3) at an IEEE conference in
> > less than 2 weeks, so any bugfixes, comments, other insights, etc.
> > before July 10 would be greatly appreciated.
>=20
> This looks very good!  I like the slides where you show SMIv2 vs YANG and
> SNMP vs NETCONF on the same slide; it gives a good overview.
>=20
> Some comments:
>=20
> - slide 13/14: to be fair to snmp there are other transports
>   *defined*.  but I guess it is correct to say udp here since it's
>   certainly the most deployed transport.
>=20
> - slide 24: could you write the link as http://www.yang-central.org?
>   The twiki part might change...
>=20
> - slide 32: you may want to expand the YANG example so people don't
>   have to guess the blanks, something like:
>=20
>      module radius-accounting-server {
>        ...
>        rpc config-reset {
>          description "...";
>        }
>        leaf server-state {
>          config false;
>          type enumeration {
>            enum other;
>            enum initializing;
>            enum running;
>          }
>        }
>=20
>   (good point about the dual purpose!)
>=20
> - slide 38: in order to avoid information overflow, consider removing
>   bullets 4,5, and 7.
>=20
> - slide 42: [side note: I think it is a bug that ok and rpc-error of
>   type warning cannot be returned at the same time...]
>=20
> - slide 53: "foo" + bar + 'baz' is not allowed:
>=20
>      If a quoted string is followed by a plus character ("+"),
>      followed by another quoted string, the two strings are
>      concatenated into one string,
>=20
>   (for some reason...)
>=20
> - slide 65-67: remove XSD column?
>=20
> - slide 75: s/error-app-info/error-app-tag/
>=20
>=20
>=20
> General comment: risk of information overflow?  sometimes the slides
> contains all details - which of course is correct but you may consider re=
moving
> less important details.
>=20
>=20
>=20
>=20
> /martin
>=20
> _______________________________________________
> yang-doctors mailing list
> yang-doctors@ietf.org
> https://www.ietf.org/mailman/listinfo/yang-doctors


From nobody Thu Jul  3 05:28:16 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 9EB501B294C for <mib-doctors@ietfa.amsl.com>; Thu,  3 Jul 2014 05:28:13 -0700 (PDT)
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 XpJHDOasuoyo for <mib-doctors@ietfa.amsl.com>; Thu,  3 Jul 2014 05:28:12 -0700 (PDT)
Received: from mail-qa0-f52.google.com (mail-qa0-f52.google.com [209.85.216.52]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ED8151B293D for <mib-doctors@ietf.org>; Thu,  3 Jul 2014 05:28:11 -0700 (PDT)
Received: by mail-qa0-f52.google.com with SMTP id w8so106310qac.11 for <mib-doctors@ietf.org>; Thu, 03 Jul 2014 05:28:11 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=YA0HDNsKaq7YNHx5BvjG77Mp4+Rpo2FIdBYovL4fvX4=; b=Vahv7OYFaVh0B55oMJWaw6xT6+il14647tZUhkOWQZENYqItc9QE9DfWGxOd0egi4q jHW4mzMFDbByCBh9pN/S5FwiUY+4UP9vfe9D3H4eEsxq0wTNZZxMK4ub6xLDaezTNu5O 20ML6SvKVNRKo1/5OKZGMSkB0DzJ7B8SsRA+HGoCbCOgmP3tKfazLByJevxwoHDk0V30 K5fHe9VzMZ1B7TGpmkpxwYNvvcFinDf/wsVawVzJR6mvncuIjHZasLuGpnvukPiITZeo sepxF6kxzmYOEZswqs7+Rxy2s7WdFv3SnMqgov2S36lPur25oS114U6bgmaxm8EdRajG wy/w==
X-Gm-Message-State: ALoCoQkZegZOF0A5vtjdV+Ze64MUKvsxClk0/BtwjOzMijYUrqJvl/KJmhZVFj/SJvNtnA6/NbKH
MIME-Version: 1.0
X-Received: by 10.140.27.229 with SMTP id 92mr6323373qgx.18.1404390491144; Thu, 03 Jul 2014 05:28:11 -0700 (PDT)
Received: by 10.140.104.48 with HTTP; Thu, 3 Jul 2014 05:28:11 -0700 (PDT)
In-Reply-To: <20140703060008.GA40306@elstar.local>
References: <CABCOCHRi51P_Q9N2_G19+=uZYTBQdNrJ-wSadrOVTxSxrk+Shg@mail.gmail.com> <20140703060008.GA40306@elstar.local>
Date: Thu, 3 Jul 2014 05:28:11 -0700
Message-ID: <CABCOCHTExFg6UviiDxnYR0t5XKwzi2E1zHMKofeNiw0ahw6paw@mail.gmail.com>
From: Andy Bierman <andy@yumaworks.com>
To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>, Andy Bierman <andy@yumaworks.com>, YANG Doctors <yang-doctors@ietf.org>, "MIB Doctors (E-mail)" <mib-doctors@ietf.org>,  Benoit Claise <bclaise@cisco.com>
Content-Type: multipart/alternative; boundary=001a11c1302e59dd6d04fd49247b
Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/W_euxOtALGHeGFJ619Ve4nQQg1s
Subject: Re: [MIB-DOCTORS] [yang-doctors] New NETCONF/YANG tutorial
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, 03 Jul 2014 12:28:13 -0000

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

On Wed, Jul 2, 2014 at 11:00 PM, Juergen Schoenwaelder <
j.schoenwaelder@jacobs-university.de> wrote:

> On Wed, Jul 02, 2014 at 09:21:29PM -0700, Andy Bierman wrote:
> > Hi,
> >
> > I wrote a free tutorial called "A Guide to NETCONF for SNMP Developers".
> > http://dld.netconfcentral.org/doc/ncorg_netconf_yang_tutorial.pdf
> >
>
> This is good stuff. Something I spotted on slide 75: I think SNMPv3
> has way more than 3 error codes (and even SNMPv1 had more than 3).
>
>

OK -- I removed that line since I cannot find the list of SNMPv3 error
codes right now.



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

--001a11c1302e59dd6d04fd49247b
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 Wed, Jul 2, 2014 at 11:00 PM, Juergen Schoenwaelder <span dir=3D=
"ltr">&lt;<a href=3D"mailto:j.schoenwaelder@jacobs-university.de" target=3D=
"_blank">j.schoenwaelder@jacobs-university.de</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">On Wed, Jul 02, 2014 at 09:21:29PM -0700, An=
dy Bierman wrote:<br>
&gt; Hi,<br>
&gt;<br>
&gt; I wrote a free tutorial called &quot;A Guide to NETCONF for SNMP Devel=
opers&quot;.<br>
&gt; <a href=3D"http://dld.netconfcentral.org/doc/ncorg_netconf_yang_tutori=
al.pdf" target=3D"_blank">http://dld.netconfcentral.org/doc/ncorg_netconf_y=
ang_tutorial.pdf</a><br>
&gt;<br>
<br>
This is good stuff. Something I spotted on slide 75: I think SNMPv3<br>
has way more than 3 error codes (and even SNMPv1 had more than 3).<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br></font></span></blockquo=
te><div><br></div><div><br></div><div>OK -- I removed that line since I can=
not find the list of SNMPv3 error codes right now.</div><div><br></div><div=
>
=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;borde=
r-left:1px #ccc solid;padding-left:1ex"><span class=3D"HOEnZb"><font color=
=3D"#888888">
/js<br>
<br>
--<br>
Juergen Schoenwaelder =A0 =A0 =A0 =A0 =A0 Jacobs University Bremen gGmbH<br=
>
Phone: +49 421 200 3587 =A0 =A0 =A0 =A0 Campus Ring 1, 28759 Bremen, German=
y<br>
Fax: =A0 +49 421 200 3103 =A0 =A0 =A0 =A0 &lt;<a href=3D"http://www.jacobs-=
university.de/" target=3D"_blank">http://www.jacobs-university.de/</a>&gt;<=
br>
</font></span></blockquote></div><br></div></div>

--001a11c1302e59dd6d04fd49247b--


From nobody Thu Jul  3 05:43:44 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 024B21A0A8F for <mib-doctors@ietfa.amsl.com>; Thu,  3 Jul 2014 05:43:42 -0700 (PDT)
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_12=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 lp4EREYMupYm for <mib-doctors@ietfa.amsl.com>; Thu,  3 Jul 2014 05:43:39 -0700 (PDT)
Received: from mail-qc0-f173.google.com (mail-qc0-f173.google.com [209.85.216.173]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 952721A0379 for <mib-doctors@ietf.org>; Thu,  3 Jul 2014 05:43:39 -0700 (PDT)
Received: by mail-qc0-f173.google.com with SMTP id l6so135456qcy.4 for <mib-doctors@ietf.org>; Thu, 03 Jul 2014 05:43:38 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=izV/bdfEkn20khGcEvxKLEyKIZbcJu9/4dcVw99sJpM=; b=arMu1r2I2N49HtxO1cswEuzBwxnAVnFQgU7x3d6pxcyRqWGHSK/LgtLMy7YVZe/Ezs hInFCilkJDBOD0PWgYqiqDk1DKOhCk0nUvOMLVe0wqS4bzP+x/AJ3nYUTjztomFPVIMU PwoJue0hoAgFUz79xqBbgkHqNb/Uy9cR1NOv7zll5+3xbGuCRSiAQ1Jiny40awMAp5t0 +J2DJJtFuHTr3hdR7RiG+udNfWQW2dtPaTaXNhQZXp8wq29X31laeL+RHcfIYI8MIauN E1/HPFFo3fkzQzygUt+6rAqNVUQXyXUaRkxiNCOvHlsF+KQJBc616tVFCRRwEmZNr6ux KPCw==
X-Gm-Message-State: ALoCoQluMQmu8VkcYG1rTsdX6kHLd7gZty0dkDYsx7SIS/6+Exae8PfGF+taqFufUNktvdLGE0Df
MIME-Version: 1.0
X-Received: by 10.224.124.74 with SMTP id t10mr6980524qar.78.1404391418808; Thu, 03 Jul 2014 05:43:38 -0700 (PDT)
Received: by 10.140.104.48 with HTTP; Thu, 3 Jul 2014 05:43:38 -0700 (PDT)
In-Reply-To: <53B51D6F.9020504@bwijnen.net>
References: <CABCOCHRi51P_Q9N2_G19+=uZYTBQdNrJ-wSadrOVTxSxrk+Shg@mail.gmail.com> <53B51D6F.9020504@bwijnen.net>
Date: Thu, 3 Jul 2014 05:43:38 -0700
Message-ID: <CABCOCHTbt_2JcWMJui+cXOmAkv1Of1F547LVODv8KDyez-PCjg@mail.gmail.com>
From: Andy Bierman <andy@yumaworks.com>
To: "Bert Wijnen (IETF)" <bertietf@bwijnen.net>
Content-Type: multipart/alternative; boundary=001a11c29512a4e43d04fd495b9d
Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/GNL533y9JlGTN2CWF_41fwdl6wI
Cc: YANG Doctors <yang-doctors@ietf.org>, "MIB Doctors \(E-mail\)" <mib-doctors@ietf.org>
Subject: Re: [MIB-DOCTORS] [yang-doctors] New NETCONF/YANG tutorial
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, 03 Jul 2014 12:43:42 -0000

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

On Thu, Jul 3, 2014 at 2:07 AM, Bert Wijnen (IETF) <bertietf@bwijnen.net>
wrote:

> I like it. Looks like there is lots for me to refresh my mind.
>
> Are you also planning to give this tutorial at an IETF EDU session
> or maybe WG chairs lunch?
>
>
No


> 120+ slides. I normally calculate an average of 2 minutes per slide.
> So that would make for 240 minutes or 4 hours. Add a couple of breaks
> and it gets to 5-6 hours. Or a day for normal training days.
>
>
It could be expanded into a whole day I guess.
Maybe 2 min. average is accurate -- I plan on several short slides.


> It has copyright Yumaworks. I understand that... but
> Can other yang doctors/yang proponents still use the slides?
>

yes -- they are going to be posted on netconfcentral.org.

(I was somewhat disturbed that 21 of about 27 links on the NETCONF Wiki page
led me to a WEB page asking for money in order to read the article,)


>
> most of this is probably nits. But here it goes anyways.
>
> On slide 2 I see reference to an IESG statement. Do you mean
>     http://www.ietf.org/iesg/statement/writable-mib-module.html
> You might want to add the ptr
>

added


>
> around slide 40 I see several times:
>
>     module example-mod {
>        namespace "http://example.com/ns/example-mod";
>        prefix "sys";
>
> Why prefix "sys" ?? Would it not be better to use something aka: prefix
> "xmpl"
> so s to indicate that you would normally use a prefix that is easy to link
> up with (or remember what is) the full namespace?
> Specifically sys might also collide with prefixes we have used i(or may
> use) n IETF, no?
>

changed to 'ex'


>
> Not sure I understand 2nd bullet (and sub bullets) on slide 55.
> Probably my lack of YANG knowledge. But the slide does not help either.
> May also be clearer if you do slides about "must" and "when" earlier.
> They now show up as slides 72/73.
>

You're right.  I am just going to delete this slide.
It's just that YANG XPath and NETCONF "select" (XML XPath) look
the same and customers have been confused (e.g. -- the YANG prefix MUST be
used as the XML prefix).

Begs the question: is the target audience complete novices or do we expect
> them to have read the RFCs? If so, you might want to add that as a slide
> at the very beginning. However, I think we should make this digestable for
> those who are novice to NetConf but do have some skill in SNMP and SMI.
>
>
No -- I am assuming some familiarity with SNMP/SMIv2 in these slides.



> slide 60
>    mmm the term "body statements"... is that well defined?
>    in rfc6020, section 4.2.1 I see:
>
>    .... the definition statements are
>    the body of the module where the data model is defined
>
> Is that what you refer to? cause from the RFC6020 I would think they
> are "definition statements" instead of "body statements".
>
>
They are called body-stmts in the ABNF


> This slideset plus the demo that Juergen once did in a OPSAREA session
> makes a great introduction to NETCONF and YANG (I think).
>
>
I tried not to cover the same details.
Links to both tutorials are on netconfcentral now.


> Bert
>

Andy


>
> On 03/07/14 06:21, Andy Bierman wrote:
>
>> Hi,
>>
>> I wrote a free tutorial called "A Guide to NETCONF for SNMP Developers".
>> http://dld.netconfcentral.org/doc/ncorg_netconf_yang_tutorial.pdf
>>
>> It is 122 slides and it isn't done ;-)
>> I hoping some YANG and MIB doctors will have some time
>> to review it.  I need to present the basic sections (1 - 3) at
>> an IEEE conference in less than 2 weeks, so any bugfixes,
>> comments, other insights, etc. before July 10 would be greatly
>> appreciated.
>>
>>
>> thanks,
>> Andy
>>
>>
>>
>> _______________________________________________
>> yang-doctors mailing list
>> yang-doctors@ietf.org
>> https://www.ietf.org/mailman/listinfo/yang-doctors
>>
>>

--001a11c29512a4e43d04fd495b9d
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, Jul 3, 2014 at 2:07 AM, Bert Wijnen (IETF) <span dir=3D"ltr=
">&lt;<a href=3D"mailto:bertietf@bwijnen.net" target=3D"_blank">bertietf@bw=
ijnen.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">I like it. Looks like there is lots for me t=
o refresh my mind.<br>
<br>
Are you also planning to give this tutorial at an IETF EDU session<br>
or maybe WG chairs lunch?<br>
<br></blockquote><div><br></div><div>No</div><div>&nbsp;</div><blockquote c=
lass=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;=
padding-left:1ex">
120+ slides. I normally calculate an average of 2 minutes per slide.<br>
So that would make for 240 minutes or 4 hours. Add a couple of breaks<br>
and it gets to 5-6 hours. Or a day for normal training days.<br>
<br></blockquote><div><br></div><div>It could be expanded into a whole day =
I guess.</div><div>Maybe 2 min. average is accurate -- I plan on several sh=
ort slides.</div><div>&nbsp;</div><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">

It has copyright Yumaworks. I understand that... but<br>
Can other yang doctors/yang proponents still use the slides?<br></blockquot=
e><div><br></div><div>yes -- they are going to be posted on <a href=3D"http=
://netconfcentral.org">netconfcentral.org</a>.</div><div><br></div><div>
(I was somewhat disturbed that 21 of about 27 links on the NETCONF Wiki pag=
e</div><div>led me to a WEB page asking for money in order to read the arti=
cle,)</div><div>&nbsp;</div><blockquote class=3D"gmail_quote" style=3D"marg=
in:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">

<br>
most of this is probably nits. But here it goes anyways.<br>
<br>
On slide 2 I see reference to an IESG statement. Do you mean<br>
&nbsp; &nbsp; <a href=3D"http://www.ietf.org/iesg/statement/writable-mib-mo=
dule.html" target=3D"_blank">http://www.ietf.org/iesg/<u></u>statement/writ=
able-mib-module.<u></u>html</a><br>
You might want to add the ptr<br></blockquote><div><br></div><div>added</di=
v><div>&nbsp;</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
around slide 40 I see several times:<br>
<br>
&nbsp; &nbsp; module example-mod {<br>
&nbsp; &nbsp; &nbsp; &nbsp;namespace &ldquo;<a href=3D"http://example.com/n=
s/example-mod" target=3D"_blank">http://example.com/ns/<u></u>example-mod</=
a>&rdquo;;<br>
&nbsp; &nbsp; &nbsp; &nbsp;prefix &ldquo;sys&rdquo;;<br>
<br>
Why prefix &quot;sys&quot; ?? Would it not be better to use something aka: =
prefix &quot;xmpl&quot;<br>
so s to indicate that you would normally use a prefix that is easy to link<=
br>
up with (or remember what is) the full namespace?<br>
Specifically sys might also collide with prefixes we have used i(or may use=
) n IETF, no?<br></blockquote><div><br></div><div>changed to &#39;ex&#39;</=
div><div>&nbsp;</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 =
0 .8ex;border-left:1px #ccc solid;padding-left:1ex">

<br>
Not sure I understand 2nd bullet (and sub bullets) on slide 55.<br>
Probably my lack of YANG knowledge. But the slide does not help either.<br>
May also be clearer if you do slides about &quot;must&quot; and &quot;when&=
quot; earlier.<br>
They now show up as slides 72/73.<br></blockquote><div><br></div><div>You&#=
39;re right. &nbsp;I am just going to delete this slide.</div><div>It&#39;s=
 just that YANG XPath and NETCONF &quot;select&quot; (XML XPath) look</div>
<div>the same and customers have been confused (e.g. -- the YANG prefix MUS=
T be</div><div>used as the XML prefix).</div><div><br></div><blockquote cla=
ss=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;pa=
dding-left:1ex">

Begs the question: is the target audience complete novices or do we expect<=
br>
them to have read the RFCs? If so, you might want to add that as a slide<br=
>
at the very beginning. However, I think we should make this digestable for<=
br>
those who are novice to NetConf but do have some skill in SNMP and SMI.<br>
<br></blockquote><div><br></div><div>No -- I am assuming some familiarity w=
ith SNMP/SMIv2 in these slides.</div><div><br></div><div>&nbsp;</div><block=
quote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc=
 solid;padding-left:1ex">

slide 60<br>
&nbsp; &nbsp;mmm the term &quot;body statements&quot;... is that well defin=
ed?<br>
&nbsp; &nbsp;in rfc6020, section 4.2.1 I see:<br>
<br>
&nbsp; &nbsp;.... the definition statements are<br>
&nbsp; &nbsp;the body of the module where the data model is defined<br>
<br>
Is that what you refer to? cause from the RFC6020 I would think they<br>
are &quot;definition statements&quot; instead of &quot;body statements&quot=
;.<br>
<br></blockquote><div><br></div><div>They are called body-stmts in the ABNF=
</div><div>&nbsp;</div><blockquote class=3D"gmail_quote" style=3D"margin:0 =
0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
This slideset plus the demo that Juergen once did in a OPSAREA session<br>
makes a great introduction to NETCONF and YANG (I think).<br>
<br></blockquote><div><br></div><div>I tried not to cover the same details.=
</div><div>Links to both tutorials are on netconfcentral now.</div><div>&nb=
sp;</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;borde=
r-left:1px #ccc solid;padding-left:1ex">

Bert<br></blockquote><div><br></div><div>Andy</div><div>&nbsp;</div><blockq=
uote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc =
solid;padding-left:1ex">
<br>
On 03/07/14 06:21, Andy Bierman 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>
I wrote a free tutorial called &quot;A Guide to NETCONF for SNMP Developers=
&quot;.<br>
<a href=3D"http://dld.netconfcentral.org/doc/ncorg_netconf_yang_tutorial.pd=
f" target=3D"_blank">http://dld.netconfcentral.org/<u></u>doc/ncorg_netconf=
_yang_<u></u>tutorial.pdf</a><br>
<br>
It is 122 slides and it isn&#39;t done ;-)<br>
I hoping some YANG and MIB doctors will have some time<br>
to review it. &nbsp;I need to present the basic sections (1 - 3) at<br>
an IEEE conference in less than 2 weeks, so any bugfixes,<br>
comments, other insights, etc. before July 10 would be greatly appreciated.=
<br>
<br>
<br>
thanks,<br>
Andy<br>
<br>
<br>
<br>
______________________________<u></u>_________________<br>
yang-doctors mailing list<br>
<a href=3D"mailto:yang-doctors@ietf.org" target=3D"_blank">yang-doctors@iet=
f.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/yang-doctors" target=3D"_b=
lank">https://www.ietf.org/mailman/<u></u>listinfo/yang-doctors</a><br>
<br>
</blockquote>
</blockquote></div><br></div></div>

--001a11c29512a4e43d04fd495b9d--


From nobody Thu Jul  3 06:25: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 3D12D1B29BB for <mib-doctors@ietfa.amsl.com>; Thu,  3 Jul 2014 06:25:46 -0700 (PDT)
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 k3Ovege3teiQ for <mib-doctors@ietfa.amsl.com>; Thu,  3 Jul 2014 06:25:44 -0700 (PDT)
Received: from mail-qc0-f177.google.com (mail-qc0-f177.google.com [209.85.216.177]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D42351B29B1 for <mib-doctors@ietf.org>; Thu,  3 Jul 2014 06:25:43 -0700 (PDT)
Received: by mail-qc0-f177.google.com with SMTP id r5so187302qcx.36 for <mib-doctors@ietf.org>; Thu, 03 Jul 2014 06:25:43 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=jxUdMTLZIyjPyr6Iynd3DOVV/ftEcRh9zXM2/hrJVdI=; b=aflG3krP/QzCSEqaJzaSShhXT8D8V8Az3irWGLXC9hG1fG30j/4uviDmSDQT7UbcfY xg8qvDZePKjD+LncbahTUt/085+kvLrjGxBwQZCYG1rnPDNO/2dKNjLAtbiDxvrrWgAw 2y5BN49/sbVtint+4RaGj0xq6Zjy9jhyZy6n64aZAGmwprOAk27NCHlAdowaveY1+VKq 7DsprZPYgdJe723i5Ir/CJQ/W9TJOFhX6zsO8uzIxspmdiQ9YBU5aBXa51WIFhxN6hPo nBpT8wswhPQEF2Wuh+W5TSfOFGecG0bi0lH0oMVwidAoI+sdLotKWih+T8IaZ/CwmI3Z AQcg==
X-Gm-Message-State: ALoCoQnZ4J1rXo5NdYmInwNrj+JMf19A4GAoWJjVLf54a+DTqjGGBnf7/buvGidF1gWsGQzyrhlG
MIME-Version: 1.0
X-Received: by 10.140.101.115 with SMTP id t106mr6662648qge.91.1404393942960;  Thu, 03 Jul 2014 06:25:42 -0700 (PDT)
Received: by 10.140.104.48 with HTTP; Thu, 3 Jul 2014 06:25:42 -0700 (PDT)
In-Reply-To: <20140703.091423.2283970538774793528.mbj@tail-f.com>
References: <CABCOCHRi51P_Q9N2_G19+=uZYTBQdNrJ-wSadrOVTxSxrk+Shg@mail.gmail.com> <20140703.091423.2283970538774793528.mbj@tail-f.com>
Date: Thu, 3 Jul 2014 06:25:42 -0700
Message-ID: <CABCOCHSaveqs63ML9sRPNKv9m_b3kB25Tkh+t88DrFxF0ayBhw@mail.gmail.com>
From: Andy Bierman <andy@yumaworks.com>
To: Martin Bjorklund <mbj@tail-f.com>
Content-Type: multipart/alternative; boundary=001a11c1721e18627004fd49f2d9
Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/6jleDgnjEmKqtHnf2_aF8WINby0
Cc: YANG Doctors <yang-doctors@ietf.org>, "MIB Doctors \(E-mail\)" <mib-doctors@ietf.org>
Subject: Re: [MIB-DOCTORS] [yang-doctors] New NETCONF/YANG tutorial
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, 03 Jul 2014 13:25:46 -0000

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

On Thu, Jul 3, 2014 at 12:14 AM, Martin Bjorklund <mbj@tail-f.com> wrote:

> Andy Bierman <andy@yumaworks.com> wrote:
> > Hi,
> >
> > I wrote a free tutorial called "A Guide to NETCONF for SNMP Developers".
> > http://dld.netconfcentral.org/doc/ncorg_netconf_yang_tutorial.pdf
> >
> > It is 122 slides and it isn't done ;-)
>
> Let me know when its done and I'll update yang-central with a link to
> this presentation.
>
> > I hoping some YANG and MIB doctors will have some time
> > to review it.  I need to present the basic sections (1 - 3) at
> > an IEEE conference in less than 2 weeks, so any bugfixes,
> > comments, other insights, etc. before July 10 would be greatly
> appreciated.
>
> This looks very good!  I like the slides where you show SMIv2 vs YANG
> and SNMP vs NETCONF on the same slide; it gives a good overview.
>
>
thanks -- I hope it will help the migration (that has officially started in
the IETF).



> Some comments:
>
> - slide 13/14: to be fair to snmp there are other transports
>   *defined*.  but I guess it is correct to say udp here since it's
>   certainly the most deployed transport.
>

what should I put?


>
> - slide 24: could you write the link as http://www.yang-central.org?
>   The twiki part might change...
>

OK


>
> - slide 32: you may want to expand the YANG example so people don't
>   have to guess the blanks, something like:
>
>      module radius-accounting-server {
>        ...
>        rpc config-reset {
>          description "...";
>        }
>        leaf server-state {
>          config false;
>          type enumeration {
>            enum other;
>            enum initializing;
>            enum running;
>          }
>        }
>
>
done


>   (good point about the dual purpose!)
>
> - slide 38: in order to avoid information overflow, consider removing
>   bullets 4,5, and 7.
>

removed 4 &  7 (bottom part looked too empty)

>
> - slide 42: [side note: I think it is a bug that ok and rpc-error of
>   type warning cannot be returned at the same time...]
>

base:1.2


>
> - slide 53: "foo" + bar + 'baz' is not allowed:
>
>      If a quoted string is followed by a plus character ("+"),
>      followed by another quoted string, the two strings are
>      concatenated into one string,
>
>   (for some reason...)
>

Hmmm... Our code allows an unquoted string to be mixed in.
fixed


>
> - slide 65-67: remove XSD column?
>

Agreed, but...
Those slides are pulled in from an old tutorial -- I can't figure out how to
change them (LibreOffice doesn't think they are tables).

I went through my computer (12 years of ODP files scattered all over!).
I tried to get rid of most style mismatches but a lot left to fix.


> - slide 75: s/error-app-info/error-app-tag/
>
>
fixed


>
>
> General comment: risk of information overflow?  sometimes the slides
> contains all details - which of course is correct but you may consider
> removing less important details.
>


good point.  I should have lots of WEB links to the details and try to
do more high-level explanation. (There are many details still left out.)




>
>
>
> /martin
>

thanks,
Andy

--001a11c1721e18627004fd49f2d9
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, Jul 3, 2014 at 12:14 AM, Martin Bjorklund <span dir=3D"ltr"=
>&lt;<a href=3D"mailto:mbj@tail-f.com" target=3D"_blank">mbj@tail-f.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">Andy Bierman &lt;<a href=3D"mailto:andy@yuma=
works.com">andy@yumaworks.com</a>&gt; wrote:<br>
&gt; Hi,<br>
&gt;<br>
&gt; I wrote a free tutorial called &quot;A Guide to NETCONF for SNMP Devel=
opers&quot;.<br>
&gt; <a href=3D"http://dld.netconfcentral.org/doc/ncorg_netconf_yang_tutori=
al.pdf" target=3D"_blank">http://dld.netconfcentral.org/doc/ncorg_netconf_y=
ang_tutorial.pdf</a><br>
&gt;<br>
&gt; It is 122 slides and it isn&#39;t done ;-)<br>
<br>
Let me know when its done and I&#39;ll update yang-central with a link to<b=
r>
this presentation.<br>
<br>
&gt; I hoping some YANG and MIB doctors will have some time<br>
&gt; to review it. =A0I need to present the basic sections (1 - 3) at<br>
&gt; an IEEE conference in less than 2 weeks, so any bugfixes,<br>
&gt; comments, other insights, etc. before July 10 would be greatly appreci=
ated.<br>
<br>
This looks very good! =A0I like the slides where you show SMIv2 vs YANG<br>
and SNMP vs NETCONF on the same slide; it gives a good overview.<br>
<br></blockquote><div><br></div><div>thanks -- I hope it will help the migr=
ation (that has officially started in the IETF).</div><div><br></div><div>=
=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;borde=
r-left:1px #ccc solid;padding-left:1ex">

Some comments:<br>
<br>
- slide 13/14: to be fair to snmp there are other transports<br>
=A0 *defined*. =A0but I guess it is correct to say udp here since it&#39;s<=
br>
=A0 certainly the most deployed transport.<br></blockquote><div><br></div><=
div>what should I put?</div><div>=A0</div><blockquote class=3D"gmail_quote"=
 style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
- slide 24: could you write the link as <a href=3D"http://www.yang-central.=
org" target=3D"_blank">http://www.yang-central.org</a>?<br>
=A0 The twiki part might change...<br></blockquote><div><br></div><div>OK</=
div><div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .=
8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
- slide 32: you may want to expand the YANG example so people don&#39;t<br>
=A0 have to guess the blanks, something like:<br>
<br>
=A0 =A0 =A0module radius-accounting-server {<br>
=A0 =A0 =A0 =A0...<br>
=A0 =A0 =A0 =A0rpc config-reset {<br>
=A0 =A0 =A0 =A0 =A0description &quot;...&quot;;<br>
=A0 =A0 =A0 =A0}<br>
=A0 =A0 =A0 =A0leaf server-state {<br>
=A0 =A0 =A0 =A0 =A0config false;<br>
=A0 =A0 =A0 =A0 =A0type enumeration {<br>
=A0 =A0 =A0 =A0 =A0 =A0enum other;<br>
=A0 =A0 =A0 =A0 =A0 =A0enum initializing;<br>
=A0 =A0 =A0 =A0 =A0 =A0enum running;<br>
=A0 =A0 =A0 =A0 =A0}<br>
=A0 =A0 =A0 =A0}<br>
<br></blockquote><div><br></div><div>done</div><div>=A0</div><blockquote cl=
ass=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;p=
adding-left:1ex">
=A0 (good point about the dual purpose!)<br>
<br>
- slide 38: in order to avoid information overflow, consider removing<br>
=A0 bullets 4,5, and 7.<br></blockquote><div><br></div><div>removed 4 &amp;=
 =A07 (bottom part looked too empty)</div><blockquote class=3D"gmail_quote"=
 style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
- slide 42: [side note: I think it is a bug that ok and rpc-error of<br>
=A0 type warning cannot be returned at the same time...]<br></blockquote><d=
iv><br></div><div>base:1.2</div><div>=A0</div><blockquote class=3D"gmail_qu=
ote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex=
">
<br>
- slide 53: &quot;foo&quot; + bar + &#39;baz&#39; is not allowed:<br>
<br>
=A0 =A0 =A0If a quoted string is followed by a plus character (&quot;+&quot=
;),<br>
=A0 =A0 =A0followed by another quoted string, the two strings are<br>
=A0 =A0 =A0concatenated into one string,<br>
<br>
=A0 (for some reason...)<br></blockquote><div><br></div><div>Hmmm... Our co=
de allows an unquoted string to be mixed in.</div><div>fixed</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">

<br>
- slide 65-67: remove XSD column?<br></blockquote><div><br></div><div>Agree=
d, but...</div><div>Those slides are pulled in from an old tutorial -- I ca=
n&#39;t figure out how to</div><div>change them (LibreOffice doesn&#39;t th=
ink they are tables).</div>
<div><br></div><div>I went through my computer (12 years of ODP files scatt=
ered all over!).</div><div>I tried to get rid of most style mismatches but =
a lot left to fix.</div><div><br></div><blockquote class=3D"gmail_quote" st=
yle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">

<br>
- slide 75: s/error-app-info/error-app-tag/<br>
<br></blockquote><div><br></div><div>fixed</div><div>=A0</div><blockquote c=
lass=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;=
padding-left:1ex">
<br>
<br>
General comment: risk of information overflow? =A0sometimes the slides<br>
contains all details - which of course is correct but you may consider<br>
removing less important details.<br></blockquote><div><br></div><div><br></=
div><div>good point. =A0I should have lots of WEB links to the details and =
try to</div><div>do more high-level explanation. (There are many details st=
ill left out.)</div>
<div><br></div><div><br></div><div><br></div><blockquote class=3D"gmail_quo=
te" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"=
>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
<br>
<br>
<br>
/martin<br>
</font></span></blockquote></div><br></div><div class=3D"gmail_extra">thank=
s,</div><div class=3D"gmail_extra">Andy</div><div class=3D"gmail_extra"><br=
></div></div>

--001a11c1721e18627004fd49f2d9--


From nobody Thu Jul  3 07:49:44 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 8BDFD1A015F; Thu,  3 Jul 2014 07:49:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.201
X-Spam-Level: 
X-Spam-Status: No, score=-2.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RP_MATCHES_RCVD=-0.651] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vy8whFB_RmDm; Thu,  3 Jul 2014 07:49:40 -0700 (PDT)
Received: from atlas3.jacobs-university.de (atlas3.jacobs-university.de [212.201.44.18]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 17F761B2AE2; Thu,  3 Jul 2014 07:48:45 -0700 (PDT)
Received: from localhost (demetrius5.irc-it.jacobs-university.de [10.70.0.222]) by atlas3.jacobs-university.de (Postfix) with ESMTP id 89AB9740; Thu,  3 Jul 2014 16:48:43 +0200 (CEST)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from atlas3.jacobs-university.de ([10.70.0.220]) by localhost (demetrius5.jacobs-university.de [10.70.0.222]) (amavisd-new, port 10030) with ESMTP id LAXQPZFMdyrf; Thu,  3 Jul 2014 16:48:25 +0200 (CEST)
Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hermes.jacobs-university.de", Issuer "Jacobs University CA - G01" (verified OK)) by atlas3.jacobs-university.de (Postfix) with ESMTPS; Thu,  3 Jul 2014 16:48:42 +0200 (CEST)
Received: from localhost (demetrius4.jacobs-university.de [212.201.44.49]) by hermes.jacobs-university.de (Postfix) with ESMTP id 96C662002C; Thu,  3 Jul 2014 16:48:42 +0200 (CEST)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius4.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id BtBRJNUlzfuL; Thu,  3 Jul 2014 16:48:42 +0200 (CEST)
Received: from elstar.local (elstar.jacobs.jacobs-university.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id 7540A20017; Thu,  3 Jul 2014 16:48:41 +0200 (CEST)
Received: by elstar.local (Postfix, from userid 501) id 69D2C2DA118C; Thu,  3 Jul 2014 16:48:41 +0200 (CEST)
Date: Thu, 3 Jul 2014 16:48:41 +0200
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: Andy Bierman <andy@yumaworks.com>
Message-ID: <20140703144841.GB41572@elstar.local>
Mail-Followup-To: Andy Bierman <andy@yumaworks.com>, YANG Doctors <yang-doctors@ietf.org>, "MIB Doctors (E-mail)" <mib-doctors@ietf.org>, Benoit Claise <bclaise@cisco.com>
References: <CABCOCHRi51P_Q9N2_G19+=uZYTBQdNrJ-wSadrOVTxSxrk+Shg@mail.gmail.com> <20140703060008.GA40306@elstar.local> <CABCOCHTExFg6UviiDxnYR0t5XKwzi2E1zHMKofeNiw0ahw6paw@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CABCOCHTExFg6UviiDxnYR0t5XKwzi2E1zHMKofeNiw0ahw6paw@mail.gmail.com>
User-Agent: Mutt/1.4.2.3i
Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/CtDt3LZodCSbPIaxAzznag3FFlc
Cc: YANG Doctors <yang-doctors@ietf.org>, "MIB Doctors \(E-mail\)" <mib-doctors@ietf.org>
Subject: Re: [MIB-DOCTORS] [yang-doctors] New NETCONF/YANG tutorial
X-BeenThere: mib-doctors@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
List-Id: MIB Doctors list <mib-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mib-doctors/>
List-Post: <mailto:mib-doctors@ietf.org>
List-Help: <mailto:mib-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Jul 2014 14:49:42 -0000

On Thu, Jul 03, 2014 at 05:28:11AM -0700, Andy Bierman wrote:
> On Wed, Jul 2, 2014 at 11:00 PM, Juergen Schoenwaelder <
> j.schoenwaelder@jacobs-university.de> wrote:
> 
> > On Wed, Jul 02, 2014 at 09:21:29PM -0700, Andy Bierman wrote:
> > > Hi,
> > >
> > > I wrote a free tutorial called "A Guide to NETCONF for SNMP Developers".
> > > http://dld.netconfcentral.org/doc/ncorg_netconf_yang_tutorial.pdf
> > >
> >
> > This is good stuff. Something I spotted on slide 75: I think SNMPv3
> > has way more than 3 error codes (and even SNMPv1 had more than 3).
> 
> OK -- I removed that line since I cannot find the list of SNMPv3 error
> codes right now.
> 

RFC 3416 search for error-status. But removing this is best since the
number of error codes is not important - what matters I think is that
NETCONF not only gives you an error code but additional information
describing the context (and this is already on the slides).

/js

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


From nobody Thu Jul  3 08:53:45 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 3EB3B1A02F7 for <mib-doctors@ietfa.amsl.com>; Thu,  3 Jul 2014 08:53:43 -0700 (PDT)
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 blu6HgN0TdPR for <mib-doctors@ietfa.amsl.com>; Thu,  3 Jul 2014 08:53:40 -0700 (PDT)
Received: from mail-qa0-f44.google.com (mail-qa0-f44.google.com [209.85.216.44]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 821301A01E6 for <mib-doctors@ietf.org>; Thu,  3 Jul 2014 08:53:40 -0700 (PDT)
Received: by mail-qa0-f44.google.com with SMTP id hw13so350043qab.17 for <mib-doctors@ietf.org>; Thu, 03 Jul 2014 08:53:39 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=YIEHdT1jc55QI7JlGNccDvcerjAqUjcPo0g06mcx2RA=; b=f9jyGGeMgLf4nRE7FVol3+1dEFB5DhDDKGjdO9iZ3zP931TwUDYTR9Sp5NwMorRMaq k8F8vw4EA2jMpRnnMWx39h66tvpVm8zfrbpqj1h30nRXMsikMmvfTVJIHfqdBxcReyV6 IshnvzLs3Sq+wp6XJDOLx4+ClQFoT757fnbzxNbYJ3nzpW2D8MPMdZJG+COqY5U+L7A+ rgJ9+1YcqofXGGRu85faXza24qPyJANk9O0iJMseeFG3M/nkA/w1G4csjwRY4vGQJVGj MfIXoYIcOi/eZGHot0MfaivioAlLxUr7lic0IzAAvn4qXuXu3xUShr9Q2XtcXg/Q44tj zPBw==
X-Gm-Message-State: ALoCoQmJRblHLttQj0938sYnSKDZNyLdtQzO6jUYFLjw6sZQ7+eT+RzpUPPQ7/yiHpsbN9EMjz5t
MIME-Version: 1.0
X-Received: by 10.140.102.12 with SMTP id v12mr8491287qge.94.1404402819264; Thu, 03 Jul 2014 08:53:39 -0700 (PDT)
Received: by 10.140.104.48 with HTTP; Thu, 3 Jul 2014 08:53:39 -0700 (PDT)
In-Reply-To: <20140703144841.GB41572@elstar.local>
References: <CABCOCHRi51P_Q9N2_G19+=uZYTBQdNrJ-wSadrOVTxSxrk+Shg@mail.gmail.com> <20140703060008.GA40306@elstar.local> <CABCOCHTExFg6UviiDxnYR0t5XKwzi2E1zHMKofeNiw0ahw6paw@mail.gmail.com> <20140703144841.GB41572@elstar.local>
Date: Thu, 3 Jul 2014 08:53:39 -0700
Message-ID: <CABCOCHRuxSJB5cLOCqoKohrinFPg1Znvg+6h4aWo16YM7mq5Mw@mail.gmail.com>
From: Andy Bierman <andy@yumaworks.com>
To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>, Andy Bierman <andy@yumaworks.com>, YANG Doctors <yang-doctors@ietf.org>, "MIB Doctors (E-mail)" <mib-doctors@ietf.org>,  Benoit Claise <bclaise@cisco.com>
Content-Type: multipart/alternative; boundary=001a1134f1522a8b5b04fd4c033e
Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/6X8ISVCUSdlnBwBd_pO70pZaYNE
Subject: Re: [MIB-DOCTORS] [yang-doctors] New NETCONF/YANG tutorial
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, 03 Jul 2014 15:53:43 -0000

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

On Thu, Jul 3, 2014 at 7:48 AM, Juergen Schoenwaelder <
j.schoenwaelder@jacobs-university.de> wrote:

> On Thu, Jul 03, 2014 at 05:28:11AM -0700, Andy Bierman wrote:
> > On Wed, Jul 2, 2014 at 11:00 PM, Juergen Schoenwaelder <
> > j.schoenwaelder@jacobs-university.de> wrote:
> >
> > > On Wed, Jul 02, 2014 at 09:21:29PM -0700, Andy Bierman wrote:
> > > > Hi,
> > > >
> > > > I wrote a free tutorial called "A Guide to NETCONF for SNMP
> Developers".
> > > > http://dld.netconfcentral.org/doc/ncorg_netconf_yang_tutorial.pdf
> > > >
> > >
> > > This is good stuff. Something I spotted on slide 75: I think SNMPv3
> > > has way more than 3 error codes (and even SNMPv1 had more than 3).
> >
> > OK -- I removed that line since I cannot find the list of SNMPv3 error
> > codes right now.
> >
>
> RFC 3416 search for error-status. But removing this is best since the
> number of error codes is not important - what matters I think is that
> NETCONF not only gives you an error code but additional information
> describing the context (and this is already on the slides).
>
>
thanks (I should know that).

I updated the slides online with v0.4.
I do not like the table on slide 14.
Any suggestions on fixing it?




> /js
>


Andy


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

--001a1134f1522a8b5b04fd4c033e
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, Jul 3, 2014 at 7:48 AM, Juergen Schoenwaelder <span dir=3D"=
ltr">&lt;<a href=3D"mailto:j.schoenwaelder@jacobs-university.de" target=3D"=
_blank">j.schoenwaelder@jacobs-university.de</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">On Thu, Jul 03, 2014 at 05:28:11AM -0700, An=
dy Bierman wrote:<br>
&gt; On Wed, Jul 2, 2014 at 11:00 PM, Juergen Schoenwaelder &lt;<br>
&gt; <a href=3D"mailto:j.schoenwaelder@jacobs-university.de">j.schoenwaelde=
r@jacobs-university.de</a>&gt; wrote:<br>
&gt;<br>
&gt; &gt; On Wed, Jul 02, 2014 at 09:21:29PM -0700, Andy Bierman wrote:<br>
&gt; &gt; &gt; Hi,<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; I wrote a free tutorial called &quot;A Guide to NETCONF for =
SNMP Developers&quot;.<br>
&gt; &gt; &gt; <a href=3D"http://dld.netconfcentral.org/doc/ncorg_netconf_y=
ang_tutorial.pdf" target=3D"_blank">http://dld.netconfcentral.org/doc/ncorg=
_netconf_yang_tutorial.pdf</a><br>
&gt; &gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; This is good stuff. Something I spotted on slide 75: I think SNMP=
v3<br>
&gt; &gt; has way more than 3 error codes (and even SNMPv1 had more than 3)=
.<br>
&gt;<br>
&gt; OK -- I removed that line since I cannot find the list of SNMPv3 error=
<br>
&gt; codes right now.<br>
&gt;<br>
<br>
RFC 3416 search for error-status. But removing this is best since the<br>
number of error codes is not important - what matters I think is that<br>
NETCONF not only gives you an error code but additional information<br>
describing the context (and this is already on the slides).<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br></font></span></blockquo=
te><div><br></div><div>thanks (I should know that).</div><div><br></div><di=
v>I updated the slides online with v0.4.</div><div>I do not like the table =
on slide 14.</div>
<div>Any suggestions on fixing it?</div><div><br></div><div><br></div><div>=
=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;borde=
r-left:1px #ccc solid;padding-left:1ex"><span class=3D"HOEnZb"><font color=
=3D"#888888">
/js<br></font></span></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"><span class=3D"HOEnZb"><fo=
nt color=3D"#888888">
<br>
--<br>
Juergen Schoenwaelder =A0 =A0 =A0 =A0 =A0 Jacobs University Bremen gGmbH<br=
>
Phone: +49 421 200 3587 =A0 =A0 =A0 =A0 Campus Ring 1, 28759 Bremen, German=
y<br>
Fax: =A0 +49 421 200 3103 =A0 =A0 =A0 =A0 &lt;<a href=3D"http://www.jacobs-=
university.de/" target=3D"_blank">http://www.jacobs-university.de/</a>&gt;<=
br>
</font></span></blockquote></div><br></div></div>

--001a1134f1522a8b5b04fd4c033e--


From nobody Thu Jul  3 09:36:18 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 C5C651A0356; Thu,  3 Jul 2014 09:36:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.201
X-Spam-Level: 
X-Spam-Status: No, score=-2.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RP_MATCHES_RCVD=-0.651] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H0dHE9hOtgkU; Thu,  3 Jul 2014 09:36:15 -0700 (PDT)
Received: from atlas3.jacobs-university.de (atlas3.jacobs-university.de [212.201.44.18]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 874E31B2800; Thu,  3 Jul 2014 09:36:15 -0700 (PDT)
Received: from localhost (demetrius5.irc-it.jacobs-university.de [10.70.0.222]) by atlas3.jacobs-university.de (Postfix) with ESMTP id 4D43A740; Thu,  3 Jul 2014 18:36:14 +0200 (CEST)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from atlas3.jacobs-university.de ([10.70.0.220]) by localhost (demetrius5.jacobs-university.de [10.70.0.222]) (amavisd-new, port 10030) with ESMTP id k6303VMH82_p; Thu,  3 Jul 2014 18:35:55 +0200 (CEST)
Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hermes.jacobs-university.de", Issuer "Jacobs University CA - G01" (verified OK)) by atlas3.jacobs-university.de (Postfix) with ESMTPS; Thu,  3 Jul 2014 18:36:12 +0200 (CEST)
Received: from localhost (demetrius2.jacobs-university.de [212.201.44.47]) by hermes.jacobs-university.de (Postfix) with ESMTP id A6D6C2002C; Thu,  3 Jul 2014 18:36:12 +0200 (CEST)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius2.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id lUALq90VMx_D; Thu,  3 Jul 2014 18:36:12 +0200 (CEST)
Received: from elstar.local (elstar.jacobs.jacobs-university.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id AB11220017; Thu,  3 Jul 2014 18:36:11 +0200 (CEST)
Received: by elstar.local (Postfix, from userid 501) id 087502DA14DB; Thu,  3 Jul 2014 18:36:07 +0200 (CEST)
Date: Thu, 3 Jul 2014 18:36:06 +0200
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: Andy Bierman <andy@yumaworks.com>
Message-ID: <20140703163604.GA42000@elstar.local>
Mail-Followup-To: Andy Bierman <andy@yumaworks.com>, YANG Doctors <yang-doctors@ietf.org>, "MIB Doctors (E-mail)" <mib-doctors@ietf.org>, Benoit Claise <bclaise@cisco.com>
References: <CABCOCHRi51P_Q9N2_G19+=uZYTBQdNrJ-wSadrOVTxSxrk+Shg@mail.gmail.com> <20140703060008.GA40306@elstar.local> <CABCOCHTExFg6UviiDxnYR0t5XKwzi2E1zHMKofeNiw0ahw6paw@mail.gmail.com> <20140703144841.GB41572@elstar.local> <CABCOCHRuxSJB5cLOCqoKohrinFPg1Znvg+6h4aWo16YM7mq5Mw@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CABCOCHRuxSJB5cLOCqoKohrinFPg1Znvg+6h4aWo16YM7mq5Mw@mail.gmail.com>
User-Agent: Mutt/1.4.2.3i
Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/4U-fI4gmg7AlrREXjBgrxjfZTjs
Cc: YANG Doctors <yang-doctors@ietf.org>, "MIB Doctors \(E-mail\)" <mib-doctors@ietf.org>
Subject: Re: [MIB-DOCTORS] [yang-doctors] New NETCONF/YANG tutorial
X-BeenThere: mib-doctors@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
List-Id: MIB Doctors list <mib-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mib-doctors/>
List-Post: <mailto:mib-doctors@ietf.org>
List-Help: <mailto:mib-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Jul 2014 16:36:16 -0000

On Thu, Jul 03, 2014 at 08:53:39AM -0700, Andy Bierman wrote:
> 
> I do not like the table on slide 14.
> Any suggestions on fixing it?

I guess the table is likely creating more confusion than it helps to
convey a clear message. If you want to have comparsion slides, create
one comparing SMIv2 to YANG and one comparing SNMP with NETCONF.

That is, change slide 14 to a protocol comparison slide (name the
different transports, the difference in fixed set of protocol
operations vs. data model driven set of protocol operations, mention
the concept of datastores and separation of config from operational
state and the availability of standard primitives for locking and
cross-device transactions). Later, add a slide after you have talked
high-level about data models and YANG to compare SMIv2 to YANG
(interrelated flat tables vs. a hierarchical data model, data
serialization to BER vs. XML, must and when constraints, ...).

/js

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


From nobody Thu Jul  3 10:29:58 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 A96251B2B32 for <mib-doctors@ietfa.amsl.com>; Thu,  3 Jul 2014 10:29:55 -0700 (PDT)
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=unavailable
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UaBTkU_CJSvF for <mib-doctors@ietfa.amsl.com>; Thu,  3 Jul 2014 10:29:54 -0700 (PDT)
Received: from mail-qc0-f173.google.com (mail-qc0-f173.google.com [209.85.216.173]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4AC271B2996 for <mib-doctors@ietf.org>; Thu,  3 Jul 2014 10:29:54 -0700 (PDT)
Received: by mail-qc0-f173.google.com with SMTP id l6so523433qcy.18 for <mib-doctors@ietf.org>; Thu, 03 Jul 2014 10:29:53 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=Hvx1qDa8/eHMqObZIVcXrJ1zLKty6qp5okbVyxkh81Q=; b=UhHZ+trAgzfS7/5FFaLT61Er4VXNhOyhbz7gsrsYvf+12e2kM80cLzOTXLFxp6oTep IQIWT/xTsXrJVGNeucDAjBi4KOhxuEIFPrPkVMY+vfpGbfg6lkTMz+pLULlU6YF5sGoc e3RSJu1FQ2msWLnppd9GgANQf7h03bW5WvaibNpURmhbl7X3VB2BIt+wsJv80zfYOrj/ vnLH7qSH/yhRaHw8NKsydRb1Crrxz2IKnpUYgLI9I3vIakKGCie+b21HinrTkMGbtbnw Qllh0K45D8tK7ItUENJ0XYYAIv7sy+zmWcQsUjBY2VN21y1PpZpzRS1mCiarI60wwoRw MdAw==
X-Gm-Message-State: ALoCoQmjRFMOmNXoTHMBKIEOdV1TUxaYq1PzD9iBokTDMpO4oMyJuFsbSB9WNHvByd2F7QKHhWoZ
MIME-Version: 1.0
X-Received: by 10.140.102.12 with SMTP id v12mr9439068qge.94.1404408593564; Thu, 03 Jul 2014 10:29:53 -0700 (PDT)
Received: by 10.140.104.48 with HTTP; Thu, 3 Jul 2014 10:29:53 -0700 (PDT)
In-Reply-To: <53B51D6F.9020504@bwijnen.net>
References: <CABCOCHRi51P_Q9N2_G19+=uZYTBQdNrJ-wSadrOVTxSxrk+Shg@mail.gmail.com> <53B51D6F.9020504@bwijnen.net>
Date: Thu, 3 Jul 2014 10:29:53 -0700
Message-ID: <CABCOCHS54nraWL5Oyda8bx-CRdZZAvaj2L7LAMBe3CheSvstEA@mail.gmail.com>
From: Andy Bierman <andy@yumaworks.com>
To: "Bert Wijnen (IETF)" <bertietf@bwijnen.net>
Content-Type: multipart/alternative; boundary=001a1134f15256dfeb04fd4d5bc6
Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/786G6CZZ0v5v4v7UmC15vseMHb4
Cc: YANG Doctors <yang-doctors@ietf.org>, "MIB Doctors \(E-mail\)" <mib-doctors@ietf.org>
Subject: Re: [MIB-DOCTORS] [yang-doctors] New NETCONF/YANG tutorial
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, 03 Jul 2014 17:29:55 -0000

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

Hi Bert,


On Thu, Jul 3, 2014 at 2:07 AM, Bert Wijnen (IETF) <bertietf@bwijnen.net>
wrote:

> I like it. Looks like there is lots for me to refresh my mind.
>
> Are you also planning to give this tutorial at an IETF EDU session
> or maybe WG chairs lunch?
>


Do you think another EDU session is needed?
Maybe IETF 91 - this 1 has a 4 hour 'YANG Advice and Editing Session'
(I am really curious what people expect out of this 4 hour meeting.
Can we order out for pizza and beer? ;-)

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

<div dir=3D"ltr">Hi Bert,<br><div class=3D"gmail_extra"><br><br><div class=
=3D"gmail_quote">On Thu, Jul 3, 2014 at 2:07 AM, Bert Wijnen (IETF) <span d=
ir=3D"ltr">&lt;<a href=3D"mailto:bertietf@bwijnen.net" target=3D"_blank">be=
rtietf@bwijnen.net</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">I like it. Looks like there is lots for me to refresh my m=
ind.<br>

<br>
Are you also planning to give this tutorial at an IETF EDU session<br>
or maybe WG chairs lunch?<br></blockquote><div><br></div><div><br></div>Do =
you think another EDU session is needed?<br>Maybe IETF 91 - this 1 has a 4 =
hour &#39;YANG Advice and Editing Session&#39;</div><div class=3D"gmail_quo=
te">
(I am really curious what people expect out of this 4 hour meeting.</div><d=
iv class=3D"gmail_quote">Can we order out for pizza and beer? ;-)<br><div><=
span style=3D"color:rgb(128,0,0);font-family:arial,helvetica,clean,sans-ser=
if;font-size:13px;font-weight:bold;line-height:16.00299835205078px"><br>
</span></div></div></div></div>

--001a1134f15256dfeb04fd4d5bc6--


From nobody Thu Jul  3 11:58:16 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 EF4AD1B29FE; Thu,  3 Jul 2014 11:58:13 -0700 (PDT)
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 gE-mYbnw-ne0; Thu,  3 Jul 2014 11:58:12 -0700 (PDT)
Received: from koko.ripe.net (koko.ripe.net [IPv6:2001:67c:2e8:11::c100:1348]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DB2CE1B29DD; Thu,  3 Jul 2014 11:58:11 -0700 (PDT)
Received: from nene.ripe.net ([193.0.23.10]) by koko.ripe.net with esmtps (UNKNOWN:AES256-GCM-SHA384:256) (Exim 4.72) (envelope-from <bertietf@bwijnen.net>) id 1X2mCt-0001ft-Dk; Thu, 03 Jul 2014 20:58:09 +0200
Received: from kitten.ripe.net ([2001:67c:2e8:1::c100:1f0] helo=macintosh-5.fritz.box) by nene.ripe.net with esmtp (Exim 4.72) (envelope-from <bertietf@bwijnen.net>) id 1X2mCt-0006i2-9p; Thu, 03 Jul 2014 20:58:07 +0200
Message-ID: <53B5A7BE.1030703@bwijnen.net>
Date: Thu, 03 Jul 2014 20:58:06 +0200
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.6.0
MIME-Version: 1.0
To: Andy Bierman <andy@yumaworks.com>
References: <CABCOCHRi51P_Q9N2_G19+=uZYTBQdNrJ-wSadrOVTxSxrk+Shg@mail.gmail.com>	<53B51D6F.9020504@bwijnen.net> <CABCOCHS54nraWL5Oyda8bx-CRdZZAvaj2L7LAMBe3CheSvstEA@mail.gmail.com>
In-Reply-To: <CABCOCHS54nraWL5Oyda8bx-CRdZZAvaj2L7LAMBe3CheSvstEA@mail.gmail.com>
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: 86ab03e524994f79ca2c75a176445dd4184386d4014627a249501eafaf1274b1
Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/klAKIpuOEC72ZHsYf7yQ4erdeRQ
Cc: YANG Doctors <yang-doctors@ietf.org>, "MIB Doctors \(E-mail\)" <mib-doctors@ietf.org>
Subject: Re: [MIB-DOCTORS] [yang-doctors] New NETCONF/YANG tutorial
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, 03 Jul 2014 18:58:14 -0000

inline

On 03/07/14 19:29, Andy Bierman wrote:
> Hi Bert,
>
>
> On Thu, Jul 3, 2014 at 2:07 AM, Bert Wijnen (IETF) <bertietf@bwijnen.net <mailto:bertietf@bwijnen.net>> wrote:
>
>     I like it. Looks like there is lots for me to refresh my mind.
>
>     Are you also planning to give this tutorial at an IETF EDU session
>     or maybe WG chairs lunch?
>
>
>
> Do you think another EDU session is needed?

Maybe I missed it, did we do one?
As I said either an EDU session or a WG chairs lunch session.
But then you get max 1 hour.

> Maybe IETF 91 - this 1 has a 4 hour 'YANG Advice and Editing Session'
> (I am really curious what people expect out of this 4 hour meeting.

yeah, I am not sure yet either. but it is worth a try.

> Can we order out for pizza and beer? ;-)
>
I guess we can, as long as we pay our own way. which is fine by me.
Or we could try to find a sponsor. but I am not sure who would do that.

Bert


From nobody Thu Jul  3 12:09: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 812C71B2B1E for <mib-doctors@ietfa.amsl.com>; Thu,  3 Jul 2014 12:09:22 -0700 (PDT)
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 hYg8o3xC3qx9 for <mib-doctors@ietfa.amsl.com>; Thu,  3 Jul 2014 12:09:20 -0700 (PDT)
Received: from mail-qa0-f54.google.com (mail-qa0-f54.google.com [209.85.216.54]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 307971B2983 for <mib-doctors@ietf.org>; Thu,  3 Jul 2014 12:09:20 -0700 (PDT)
Received: by mail-qa0-f54.google.com with SMTP id v10so554176qac.27 for <mib-doctors@ietf.org>; Thu, 03 Jul 2014 12:09:19 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=HkHy1R8VFxNKgSL7QQLRiDMt/q/OsZEK0wYpekqa3e8=; b=IelQgSkpO/KFWbxEFp8llE1N9+4bkaRqJeRKmlJnW3OdEjuFIH18bqCQ0IEGzVmdhX zrpuFdnzDrmWZ8gubtxjP/0cyULzlVJvbdtF3jXKzKhS5DMyJOT1K3XyFl/qdr4TiPiG AYe0MasAZf804b8aayabRpbPDjUtGfU37X/XKvF+O45ULxqFMXwIB7hU9j64j3fRO9Qg C/aIBKvG8o4TE9Oj2J7cZVm6yeOrvsgymyihYrOJiWfQBfqMBvvf4UEv6Ju4exIHvPv9 G/pRxvkjyHuB91JFflQZl8hcB294qP7+xBtT7jfRKpQ3nd4J8mOVhIMfcNb+hhecK/1k ITVQ==
X-Gm-Message-State: ALoCoQmgk9f+JBu9NcwyV8WzrOdh68gSEX5JO0tWHz1AsrYLRWkYkjA/RV1kuzZrceVLTbwTEnUY
MIME-Version: 1.0
X-Received: by 10.224.22.12 with SMTP id l12mr10976794qab.88.1404414559433; Thu, 03 Jul 2014 12:09:19 -0700 (PDT)
Received: by 10.140.104.48 with HTTP; Thu, 3 Jul 2014 12:09:19 -0700 (PDT)
In-Reply-To: <53B5A7BE.1030703@bwijnen.net>
References: <CABCOCHRi51P_Q9N2_G19+=uZYTBQdNrJ-wSadrOVTxSxrk+Shg@mail.gmail.com> <53B51D6F.9020504@bwijnen.net> <CABCOCHS54nraWL5Oyda8bx-CRdZZAvaj2L7LAMBe3CheSvstEA@mail.gmail.com> <53B5A7BE.1030703@bwijnen.net>
Date: Thu, 3 Jul 2014 12:09:19 -0700
Message-ID: <CABCOCHSq7x6=_HmqSwbLNidce2QfQw1c4t2=Q76dyze3n5=axQ@mail.gmail.com>
From: Andy Bierman <andy@yumaworks.com>
To: "Bert Wijnen (IETF)" <bertietf@bwijnen.net>
Content-Type: multipart/alternative; boundary=047d7bf0e59ceecd8104fd4ebe14
Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/iqSoYV2sOMDUiXwFtmLWaMwHqCE
Cc: YANG Doctors <yang-doctors@ietf.org>, "MIB Doctors \(E-mail\)" <mib-doctors@ietf.org>
Subject: Re: [MIB-DOCTORS] [yang-doctors] New NETCONF/YANG tutorial
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, 03 Jul 2014 19:09:22 -0000

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

On Thu, Jul 3, 2014 at 11:58 AM, Bert Wijnen (IETF) <bertietf@bwijnen.net>
wrote:

> inline
>
> On 03/07/14 19:29, Andy Bierman wrote:
>
>> Hi Bert,
>>
>>
>> On Thu, Jul 3, 2014 at 2:07 AM, Bert Wijnen (IETF) <bertietf@bwijnen.net
>> <mailto:bertietf@bwijnen.net>> wrote:
>>
>>     I like it. Looks like there is lots for me to refresh my mind.
>>
>>     Are you also planning to give this tutorial at an IETF EDU session
>>     or maybe WG chairs lunch?
>>
>>
>>
>> Do you think another EDU session is needed?
>>
>
> Maybe I missed it, did we do one?
>

IETF 84
http://www.ietf.org/edu/documents/2012-ietf-84-netconf-yang.pdf



> As I said either an EDU session or a WG chairs lunch session.
> But then you get max 1 hour.
>

Does not seem like a Blue Dot topic to me.


>
>  Maybe IETF 91 - this 1 has a 4 hour 'YANG Advice and Editing Session'
>> (I am really curious what people expect out of this 4 hour meeting.
>>
>
> yeah, I am not sure yet either. but it is worth a try.
>
>  Can we order out for pizza and beer? ;-)
>>
>>  I guess we can, as long as we pay our own way. which is fine by me.
> Or we could try to find a sponsor. but I am not sure who would do that.


Yeah, speaking of food and beer, I think the agenda has a typo.
It says 14:00 - 18:00, but the welcome reception is 17:00 to 19:00.
Are we really overlapping that?



>
>
> Bert
>

Andy

--047d7bf0e59ceecd8104fd4ebe14
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, Jul 3, 2014 at 11:58 AM, Bert Wijnen (IETF) <span dir=3D"lt=
r">&lt;<a href=3D"mailto:bertietf@bwijnen.net" target=3D"_blank">bertietf@b=
wijnen.net</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">inline<br>
<br>
On 03/07/14 19:29, Andy Bierman 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 Bert,<br>
<br>
<br>
On Thu, Jul 3, 2014 at 2:07 AM, Bert Wijnen (IETF) &lt;<a href=3D"mailto:be=
rtietf@bwijnen.net" target=3D"_blank">bertietf@bwijnen.net</a> &lt;mailto:<=
a href=3D"mailto:bertietf@bwijnen.net" target=3D"_blank">bertietf@bwijnen.n=
et</a>&gt;&gt; wrote:<br>

<br>
=A0 =A0 I like it. Looks like there is lots for me to refresh my mind.<br>
<br>
=A0 =A0 Are you also planning to give this tutorial at an IETF EDU session<=
br>
=A0 =A0 or maybe WG chairs lunch?<br>
<br>
<br>
<br>
Do you think another EDU session is needed?<br>
</blockquote>
<br>
Maybe I missed it, did we do one?<br></blockquote><div><br></div><div>IETF =
84<br></div><div><a href=3D"http://www.ietf.org/edu/documents/2012-ietf-84-=
netconf-yang.pdf">http://www.ietf.org/edu/documents/2012-ietf-84-netconf-ya=
ng.pdf</a></div>
<div><br></div><div>=A0</div><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,2=
04);border-left-style:solid;padding-left:1ex">
As I said either an EDU session or a WG chairs lunch session.<br>
But then you get max 1 hour.<br></blockquote><div><br></div><div>Does not s=
eem like a Blue Dot topic to me.</div><div>=A0</div><blockquote class=3D"gm=
ail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-l=
eft-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">

<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">
Maybe IETF 91 - this 1 has a 4 hour &#39;YANG Advice and Editing Session&#3=
9;<br>
(I am really curious what people expect out of this 4 hour meeting.<br>
</blockquote>
<br>
yeah, I am not sure yet either. but it is worth a try.<br>
<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">
Can we order out for pizza and beer? ;-)<br>
<br>
</blockquote>
I guess we can, as long as we pay our own way. which is fine by me.<br>
Or we could try to find a sponsor. but I am not sure who would do that.</bl=
ockquote><div><br></div><div>Yeah, speaking of food and beer, I think the a=
genda has a typo.</div><div>It says 14:00 - 18:00, but the welcome receptio=
n is 17:00 to 19:00.</div>
<div>Are we really overlapping that?</div><div><br></div><div>=A0</div><blo=
ckquote 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;paddi=
ng-left:1ex">
<span class=3D""><font color=3D"#888888"><br>
<br>
Bert<br>
</font></span></blockquote></div><br></div><div class=3D"gmail_extra">Andy<=
/div><div class=3D"gmail_extra"><br></div></div>

--047d7bf0e59ceecd8104fd4ebe14--


From nobody Fri Jul  4 00:44:50 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 36A511B2C2C; Fri,  4 Jul 2014 00:44:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.151
X-Spam-Level: 
X-Spam-Status: No, score=-15.151 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.651, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C4QIBvyZ9K0B; Fri,  4 Jul 2014 00:44:46 -0700 (PDT)
Received: from aer-iport-4.cisco.com (aer-iport-4.cisco.com [173.38.203.54]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0FC571A0154; Fri,  4 Jul 2014 00:44:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7873; q=dns/txt; s=iport; t=1404459886; x=1405669486; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to; bh=uoS2D7HXhrZm8mU2txRce8FWch+8PjnlYNPMN6JXZtw=; b=QQiLwv6LD3s8+WShu1OKz3dHks0OUGlOUyWE6wD6ZUlRL7KFtRGmSGds CJBDfU9qppTw4L48JxtZr78l3pZFJR8SPhsHk8rF9dRZJunLJ6g/lvgRD hN1JZjIQIRPt5fHmCCda6iMGjellEEN6ceWB4pZBezAIMHBwi1ezKBwAy I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Am0KAGpatlOtJssW/2dsb2JhbABag1+/SYc3AYEidYQDAQEBAgJ4ARALGAkWCAcJAwIBAgE0EQYBDAEFAgEBBYg5Dcl9F48iB4RDBZZchBqHD4x9g0U7Lw
X-IronPort-AV: E=Sophos; i="5.01,599,1400025600"; d="scan'208,217"; a="99556236"
Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP; 04 Jul 2014 07:44:44 +0000
Received: from [10.60.67.84] (ams-bclaise-8913.cisco.com [10.60.67.84]) by aer-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id s647ihEI004067; Fri, 4 Jul 2014 07:44:43 GMT
Message-ID: <53B65B6B.3080902@cisco.com>
Date: Fri, 04 Jul 2014 09:44:43 +0200
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Andy Bierman <andy@yumaworks.com>, "Bert Wijnen (IETF)" <bertietf@bwijnen.net>
References: <CABCOCHRi51P_Q9N2_G19+=uZYTBQdNrJ-wSadrOVTxSxrk+Shg@mail.gmail.com>	<53B51D6F.9020504@bwijnen.net>	<CABCOCHS54nraWL5Oyda8bx-CRdZZAvaj2L7LAMBe3CheSvstEA@mail.gmail.com>	<53B5A7BE.1030703@bwijnen.net> <CABCOCHSq7x6=_HmqSwbLNidce2QfQw1c4t2=Q76dyze3n5=axQ@mail.gmail.com>
In-Reply-To: <CABCOCHSq7x6=_HmqSwbLNidce2QfQw1c4t2=Q76dyze3n5=axQ@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------070205020600040706060106"
Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/8d_X0sHb7NJWWBFpeF83u_A-nbI
Cc: YANG Doctors <yang-doctors@ietf.org>, "MIB Doctors \(E-mail\)" <mib-doctors@ietf.org>
Subject: Re: [MIB-DOCTORS] [yang-doctors] New NETCONF/YANG tutorial
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, 04 Jul 2014 07:44:48 -0000

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

On 3/07/2014 21:09, Andy Bierman wrote:
>
>
>
> On Thu, Jul 3, 2014 at 11:58 AM, Bert Wijnen (IETF) 
> <bertietf@bwijnen.net <mailto:bertietf@bwijnen.net>> wrote:
>
>     inline
>
>     On 03/07/14 19:29, Andy Bierman wrote:
>
>         Hi Bert,
>
>
>         On Thu, Jul 3, 2014 at 2:07 AM, Bert Wijnen (IETF)
>         <bertietf@bwijnen.net <mailto:bertietf@bwijnen.net>
>         <mailto:bertietf@bwijnen.net <mailto:bertietf@bwijnen.net>>>
>         wrote:
>
>             I like it. Looks like there is lots for me to refresh my mind.
>
>             Are you also planning to give this tutorial at an IETF EDU
>         session
>             or maybe WG chairs lunch?
>
>
>
>         Do you think another EDU session is needed?
>
>
>     Maybe I missed it, did we do one?
>
>
> IETF 84
> http://www.ietf.org/edu/documents/2012-ietf-84-netconf-yang.pdf
>
>     As I said either an EDU session or a WG chairs lunch session.
>     But then you get max 1 hour.
>
>
> Does not seem like a Blue Dot topic to me.
>
>
>         Maybe IETF 91 - this 1 has a 4 hour 'YANG Advice and Editing
>         Session'
>         (I am really curious what people expect out of this 4 hour
>         meeting.
>
>
>     yeah, I am not sure yet either. but it is worth a try.
>
>         Can we order out for pizza and beer? ;-)
>
>     I guess we can, as long as we pay our own way. which is fine by me.
>     Or we could try to find a sponsor. but I am not sure who would do
>     that.
>
>
> Yeah, speaking of food and beer, I think the agenda has a typo.
> It says 14:00 - 18:00, but the welcome reception is 17:00 to 19:00.
> Are we really overlapping that?
Let's see how that goes.
This is an experiment.

Regards, Benoit
>
>
>
>     Bert
>
>
> Andy
>


--------------070205020600040706060106
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 3/07/2014 21:09, Andy Bierman wrote:<br>
    </div>
    <blockquote
cite="mid:CABCOCHSq7x6=_HmqSwbLNidce2QfQw1c4t2=Q76dyze3n5=axQ@mail.gmail.com"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=ISO-8859-1">
      <div dir="ltr"><br>
        <div class="gmail_extra"><br>
          <br>
          <div class="gmail_quote">On Thu, Jul 3, 2014 at 11:58 AM, Bert
            Wijnen (IETF) <span dir="ltr">&lt;<a moz-do-not-send="true"
                href="mailto:bertietf@bwijnen.net" target="_blank">bertietf@bwijnen.net</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">inline<br>
              <br>
              On 03/07/14 19:29, Andy Bierman 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 Bert,<br>
                <br>
                <br>
                On Thu, Jul 3, 2014 at 2:07 AM, Bert Wijnen (IETF) &lt;<a
                  moz-do-not-send="true"
                  href="mailto:bertietf@bwijnen.net" target="_blank">bertietf@bwijnen.net</a>
                &lt;mailto:<a moz-do-not-send="true"
                  href="mailto:bertietf@bwijnen.net" target="_blank">bertietf@bwijnen.net</a>&gt;&gt;
                wrote:<br>
                <br>
                &nbsp; &nbsp; I like it. Looks like there is lots for me to
                refresh my mind.<br>
                <br>
                &nbsp; &nbsp; Are you also planning to give this tutorial at an
                IETF EDU session<br>
                &nbsp; &nbsp; or maybe WG chairs lunch?<br>
                <br>
                <br>
                <br>
                Do you think another EDU session is needed?<br>
              </blockquote>
              <br>
              Maybe I missed it, did we do one?<br>
            </blockquote>
            <div><br>
            </div>
            <div>IETF 84<br>
            </div>
            <div><a moz-do-not-send="true"
                href="http://www.ietf.org/edu/documents/2012-ietf-84-netconf-yang.pdf">http://www.ietf.org/edu/documents/2012-ietf-84-netconf-yang.pdf</a></div>
            <div><br>
            </div>
            <div>&nbsp;</div>
            <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">As
              I said either an EDU session or a WG chairs lunch session.<br>
              But then you get max 1 hour.<br>
            </blockquote>
            <div><br>
            </div>
            <div>Does not seem like a Blue Dot topic to me.</div>
            <div>&nbsp;</div>
            <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"><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">
                Maybe IETF 91 - this 1 has a 4 hour 'YANG Advice and
                Editing Session'<br>
                (I am really curious what people expect out of this 4
                hour meeting.<br>
              </blockquote>
              <br>
              yeah, I am not sure yet either. but it is worth a try.<br>
              <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">
                Can we order out for pizza and beer? ;-)<br>
                <br>
              </blockquote>
              I guess we can, as long as we pay our own way. which is
              fine by me.<br>
              Or we could try to find a sponsor. but I am not sure who
              would do that.</blockquote>
            <div><br>
            </div>
            <div>Yeah, speaking of food and beer, I think the agenda has
              a typo.</div>
            <div>It says 14:00 - 18:00, but the welcome reception is
              17:00 to 19:00.</div>
            <div>Are we really overlapping that?</div>
          </div>
        </div>
      </div>
    </blockquote>
    Let's see how that goes.<br>
    This is an experiment. <br>
    <br>
    Regards, Benoit<br>
    <blockquote
cite="mid:CABCOCHSq7x6=_HmqSwbLNidce2QfQw1c4t2=Q76dyze3n5=axQ@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div class="gmail_extra">
          <div class="gmail_quote">
            <div><br>
            </div>
            <div>&nbsp;</div>
            <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"><span
                class=""><font color="#888888"><br>
                  <br>
                  Bert<br>
                </font></span></blockquote>
          </div>
          <br>
        </div>
        <div class="gmail_extra">Andy</div>
        <div class="gmail_extra"><br>
        </div>
      </div>
    </blockquote>
    <br>
  </body>
</html>

--------------070205020600040706060106--


From nobody Fri Jul  4 05:36:06 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 812D41B288E; Fri,  4 Jul 2014 05:35:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.152
X-Spam-Level: 
X-Spam-Status: No, score=-15.152 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] 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 596yh6AWSk0y; Fri,  4 Jul 2014 05:35:40 -0700 (PDT)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7F7201A0344; Fri,  4 Jul 2014 05:35:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4591; q=dns/txt; s=iport; t=1404477340; x=1405686940; h=message-id:date:from:mime-version:to:subject:references: in-reply-to:content-transfer-encoding; bh=y1ti2ymA6V5L6W/knO5olUE5oZ+H0tiVQXkJqrdKnAs=; b=Mf9BHN1V3rhR4paAPT8zm61ZIKmXgKNuhn4q5E1Ptb2snhTZ6CA2cg0x 4QPmFWUvKYJp1bgiHSkRNk2LE+Fdq/QipU12fDmIBduRHO1ERIOxeglxT njOJebW+s/XdCNzfWh2vkXLiQJjWHssvA4rmb9C92lhvK5wpZ0D6nedK5 I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqMEAE+ftlOtJssW/2dsb2JhbABRCYNgg0nDOgGBI3WEAwEBAQQjFUANBB0IAgUWCwICCQMCAQIBNw4GAQwGAgEBiD6vFZsmEwSBLIpRgj0NDVWCd4FMAQSWXQWEFIcPhDeIRoNFO4EzJA
X-IronPort-AV: E=Sophos;i="5.01,601,1400025600"; d="scan'208";a="103808836"
Received: from aer-iport-nat.cisco.com (HELO aer-core-4.cisco.com) ([173.38.203.22]) by aer-iport-2.cisco.com with ESMTP; 04 Jul 2014 12:35:37 +0000
Received: from [10.60.67.84] (ams-bclaise-8913.cisco.com [10.60.67.84]) by aer-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id s64CZbbY021679; Fri, 4 Jul 2014 12:35:37 GMT
Message-ID: <53B69F99.7040005@cisco.com>
Date: Fri, 04 Jul 2014 14:35:37 +0200
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: "aaa-doctors@ietf.org" <aaa-doctors@ietf.org>, "MIB Doctors (E-mail)" <mib-doctors@ietf.org>, YANG Doctors <yang-doctors@ietf.org>, "ops-dir@ietf.org" <ops-dir@ietf.org>, "pm-dir@ietf.org" <pm-dir@ietf.org>, IETF DNS Directorate <dns-dir@ietf.org>
References: <20140703233531.27827.1171.idtracker@ietfa.amsl.com>
In-Reply-To: <20140703233531.27827.1171.idtracker@ietfa.amsl.com>
X-Forwarded-Message-Id: <20140703233531.27827.1171.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/nz8PG9YYv-CPaA9xug-GOnZwXv4
Subject: [MIB-DOCTORS] PRELIMINARY Agenda and Package for the July 10, 2014 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, 04 Jul 2014 12:35:42 -0000

Dear all,

Please find below the agenda of the July 10th IESG telechat.
Please send your questions, comments and concerns before July 9th COB.

Thanks and Regards, Benoit.

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

INTERNET ENGINEERING STEERING GROUP (IESG)
Summarized Agenda for the 2014-07-10 IESG Teleconference

This agenda was generated at 2014-07-03 16:34:54 PDT
Up-to-date web version of this agenda can be found at:
https:///iesg/agenda/


2. Protocol Actions
2.1 WG Submissions
2.1.1 New Items
     
   o draft-ietf-ppsp-peer-protocol-10  - IETF stream
     Peer-to-Peer Streaming Peer Protocol (PPSPP) (Proposed Standard)
     Note: Rachel Huang <Rachel@huawei.com> is the document shepherd.
     Token: Martin Stiemerling
     IANA Review: IANA - Not OK
     Consensus: Unknown

   o draft-ietf-straw-sip-traceroute-02  - IETF stream
     A Media-based Traceroute Function for the Session Initiation
     Protocol (SIP) (Proposed Standard)
     Token: Richard Barnes
     IANA Review: IANA OK - No Actions Needed
     Consensus: Yes
     Last call expires: 2014-07-04

   o draft-ietf-mmusic-rtsp-nat-21  - IETF stream
     A Network Address Translator (NAT) Traversal Mechanism for Media
     Controlled by Real-Time Streaming Protocol (RTSP) (Proposed
     Standard)
     Token: Alissa Cooper
     IANA Review: IANA OK - Actions Needed
     Consensus: Yes

   o draft-ietf-eman-energy-monitoring-mib-10  - IETF stream
     Power and Energy Monitoring MIB (Proposed Standard)
     Token: Joel Jaeggli
     IANA Review: IANA OK - Actions Needed
     Consensus: Unknown

   o draft-ietf-eman-energy-aware-mib-15  - IETF stream
     Energy Object Context MIB (Proposed Standard)
     Token: Joel Jaeggli
     IANA Review: IANA OK - Actions Needed
     Consensus: Unknown

   o draft-ietf-eman-battery-mib-12  - IETF stream
     Definition of Managed Objects for Battery Monitoring (Proposed
     Standard)
     Token: Joel Jaeggli
     IANA Review: IANA - Not OK
     Consensus: Unknown

   o draft-ietf-sidr-cps-04  - IETF stream
     Template for a Certification Practice Statement (CPS) for the
     Resource PKI (RPKI) (Best Current Practice)
     Token: Alia Atlas
     IANA Review: IANA OK - No Actions Needed
     Consensus: Unknown

   o draft-ietf-xmpp-websocket-07  - IETF stream
     An XMPP Sub-protocol for WebSocket (Proposed Standard)
     Token: Richard Barnes
     IANA Review: IANA OK - Actions Needed
     Consensus: Unknown
     Last call expires: 2014-07-04

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

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-ipfix-text-adt-06  - IETF stream
     Textual Representation of IPFIX Abstract Data Types (Informational)
     Token: Benoit Claise
     IANA Review: IANA OK - No Actions Needed
     Consensus: Unknown

   o draft-ietf-pce-questions-06  - IETF stream
     Unanswered Questions in the Path Computation Element Architecture
     (Informational)
     Token: Alia Atlas
     IANA Review: IANA OK - No Actions Needed
     Consensus: Unknown

   o draft-ietf-sidr-bgpsec-reqs-11  - IETF stream
     Security Requirements for BGP Path Validation (Informational)
     Token: Alia Atlas
     IANA Review: IANA OK - No Actions Needed
     Consensus: Unknown

   o draft-ietf-stir-threats-03  - IETF stream
     Secure Telephone Identity Threat Model (Informational)
     Token: Richard Barnes
     IANA Review: IANA OK - No Actions Needed
     Consensus: Unknown
     Last call expires: 2014-07-04

3.1.2 Returning Items

   NONE

3.2 Individual Submissions Via AD
3.2.1 New Items

   NONE

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

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

   o Timezone Data Distribution Service (tzdist)

4.1.2 Proposed for Approval

   NONE

4.2 WG Rechartering
4.2.1 Under Evaluation for IETF Review

   NONE

4.2.2 Proposed for Approval

   NONE



From nobody Fri Jul  4 06:27: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 440881B2939; Fri,  4 Jul 2014 06:27:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.552
X-Spam-Level: 
X-Spam-Status: No, score=-2.552 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.651, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yOTG9vPvIVRb; Fri,  4 Jul 2014 06:27:12 -0700 (PDT)
Received: from lucidvision.com (lucidvision.com [72.71.250.34]) by ietfa.amsl.com (Postfix) with ESMTP id 4B5BD1B27F3; Fri,  4 Jul 2014 06:27:12 -0700 (PDT)
Received: from [192.168.1.118] (static-72-71-250-37.cncdnh.fast04.myfairpoint.net [72.71.250.37]) by lucidvision.com (Postfix) with ESMTP id 3FA4D280DBA9; Fri,  4 Jul 2014 09:27:11 -0400 (EDT)
Content-Type: multipart/signed; boundary="Apple-Mail=_25E5F46A-2258-40F3-93BA-0DFCBD758C47"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\))
From: "Thomas D. Nadeau" <tnadeau@lucidvision.com>
In-Reply-To: <53B65B6B.3080902@cisco.com>
Date: Fri, 4 Jul 2014 09:27:10 -0400
Message-Id: <01C0CCD3-8336-4542-9900-DBEE04B54565@lucidvision.com>
References: <CABCOCHRi51P_Q9N2_G19+=uZYTBQdNrJ-wSadrOVTxSxrk+Shg@mail.gmail.com>	<53B51D6F.9020504@bwijnen.net>	<CABCOCHS54nraWL5Oyda8bx-CRdZZAvaj2L7LAMBe3CheSvstEA@mail.gmail.com>	<53B5A7BE.1030703@bwijnen.net> <CABCOCHSq7x6=_HmqSwbLNidce2QfQw1c4t2=Q76dyze3n5=axQ@mail.gmail.com> <53B65B6B.3080902@cisco.com>
To: Benoit Claise <bclaise@cisco.com>
X-Mailer: Apple Mail (2.1878.2)
Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/RlfYGW9bAxCrjMN-C9K35Yx6V_8
Cc: YANG Doctors <yang-doctors@ietf.org>, "MIB Doctors \(E-mail\)" <mib-doctors@ietf.org>
Subject: Re: [MIB-DOCTORS] [yang-doctors] New NETCONF/YANG tutorial
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, 04 Jul 2014 13:27:14 -0000

--Apple-Mail=_25E5F46A-2258-40F3-93BA-0DFCBD758C47
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_28FA724A-A50D-4FCE-974B-E4A72E4BA165"


--Apple-Mail=_28FA724A-A50D-4FCE-974B-E4A72E4BA165
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1


	Right. This is the first in what I personally hope, is a =
regularly run meeting for promoting (accelerated) yang development at =
the IETF.=20

	--Tom


On Jul 4, 2014:3:44 AM, at 3:44 AM, Benoit Claise <bclaise@cisco.com> =
wrote:

> On 3/07/2014 21:09, Andy Bierman wrote:
>>=20
>>=20
>>=20
>> On Thu, Jul 3, 2014 at 11:58 AM, Bert Wijnen (IETF) =
<bertietf@bwijnen.net> wrote:
>> inline
>>=20
>> On 03/07/14 19:29, Andy Bierman wrote:
>> Hi Bert,
>>=20
>>=20
>> On Thu, Jul 3, 2014 at 2:07 AM, Bert Wijnen (IETF) =
<bertietf@bwijnen.net <mailto:bertietf@bwijnen.net>> wrote:
>>=20
>>     I like it. Looks like there is lots for me to refresh my mind.
>>=20
>>     Are you also planning to give this tutorial at an IETF EDU =
session
>>     or maybe WG chairs lunch?
>>=20
>>=20
>>=20
>> Do you think another EDU session is needed?
>>=20
>> Maybe I missed it, did we do one?
>>=20
>> IETF 84
>> http://www.ietf.org/edu/documents/2012-ietf-84-netconf-yang.pdf
>>=20
>> =20
>> As I said either an EDU session or a WG chairs lunch session.
>> But then you get max 1 hour.
>>=20
>> Does not seem like a Blue Dot topic to me.
>> =20
>>=20
>> Maybe IETF 91 - this 1 has a 4 hour 'YANG Advice and Editing Session'
>> (I am really curious what people expect out of this 4 hour meeting.
>>=20
>> yeah, I am not sure yet either. but it is worth a try.
>>=20
>> Can we order out for pizza and beer? ;-)
>>=20
>> I guess we can, as long as we pay our own way. which is fine by me.
>> Or we could try to find a sponsor. but I am not sure who would do =
that.
>>=20
>> Yeah, speaking of food and beer, I think the agenda has a typo.
>> It says 14:00 - 18:00, but the welcome reception is 17:00 to 19:00.
>> Are we really overlapping that?
> Let's see how that goes.
> This is an experiment.=20
>=20
> Regards, Benoit
>>=20
>> =20
>>=20
>>=20
>> Bert
>>=20
>> Andy
>>=20
>=20
> _______________________________________________
> yang-doctors mailing list
> yang-doctors@ietf.org
> https://www.ietf.org/mailman/listinfo/yang-doctors


--Apple-Mail=_28FA724A-A50D-4FCE-974B-E4A72E4BA165
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;"><div><br></div><span class="Apple-tab-span" style="white-space:pre">	</span>Right. This is the first in what I personally hope, is a regularly run meeting for promoting (accelerated) yang development at the IETF.&nbsp;<div><br></div><div><span class="Apple-tab-span" style="white-space:pre">	</span>--Tom</div><div><br></div><div><br><div><div>On Jul 4, 2014:3:44 AM, at 3:44 AM, Benoit Claise &lt;<a href="mailto:bclaise@cisco.com">bclaise@cisco.com</a>&gt; wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">
  
    <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type">
  
  <div bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">On 3/07/2014 21:09, Andy Bierman wrote:<br>
    </div>
    <blockquote cite="mid:CABCOCHSq7x6=_HmqSwbLNidce2QfQw1c4t2=Q76dyze3n5=axQ@mail.gmail.com" type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=ISO-8859-1">
      <div dir="ltr"><br>
        <div class="gmail_extra"><br>
          <br>
          <div class="gmail_quote">On Thu, Jul 3, 2014 at 11:58 AM, Bert
            Wijnen (IETF) <span dir="ltr">&lt;<a moz-do-not-send="true" href="mailto:bertietf@bwijnen.net" target="_blank">bertietf@bwijnen.net</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">inline<br>
              <br>
              On 03/07/14 19:29, Andy Bierman 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 Bert,<br>
                <br>
                <br>
                On Thu, Jul 3, 2014 at 2:07 AM, Bert Wijnen (IETF) &lt;<a moz-do-not-send="true" href="mailto:bertietf@bwijnen.net" target="_blank">bertietf@bwijnen.net</a>
                &lt;mailto:<a moz-do-not-send="true" href="mailto:bertietf@bwijnen.net" target="_blank">bertietf@bwijnen.net</a>&gt;&gt;
                wrote:<br>
                <br>
                &nbsp; &nbsp; I like it. Looks like there is lots for me to
                refresh my mind.<br>
                <br>
                &nbsp; &nbsp; Are you also planning to give this tutorial at an
                IETF EDU session<br>
                &nbsp; &nbsp; or maybe WG chairs lunch?<br>
                <br>
                <br>
                <br>
                Do you think another EDU session is needed?<br>
              </blockquote>
              <br>
              Maybe I missed it, did we do one?<br>
            </blockquote>
            <div><br>
            </div>
            <div>IETF 84<br>
            </div>
            <div><a moz-do-not-send="true" href="http://www.ietf.org/edu/documents/2012-ietf-84-netconf-yang.pdf">http://www.ietf.org/edu/documents/2012-ietf-84-netconf-yang.pdf</a></div>
            <div><br>
            </div>
            <div>&nbsp;</div>
            <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">As
              I said either an EDU session or a WG chairs lunch session.<br>
              But then you get max 1 hour.<br>
            </blockquote>
            <div><br>
            </div>
            <div>Does not seem like a Blue Dot topic to me.</div>
            <div>&nbsp;</div>
            <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"><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">
                Maybe IETF 91 - this 1 has a 4 hour 'YANG Advice and
                Editing Session'<br>
                (I am really curious what people expect out of this 4
                hour meeting.<br>
              </blockquote>
              <br>
              yeah, I am not sure yet either. but it is worth a try.<br>
              <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">
                Can we order out for pizza and beer? ;-)<br>
                <br>
              </blockquote>
              I guess we can, as long as we pay our own way. which is
              fine by me.<br>
              Or we could try to find a sponsor. but I am not sure who
              would do that.</blockquote>
            <div><br>
            </div>
            <div>Yeah, speaking of food and beer, I think the agenda has
              a typo.</div>
            <div>It says 14:00 - 18:00, but the welcome reception is
              17:00 to 19:00.</div>
            <div>Are we really overlapping that?</div>
          </div>
        </div>
      </div>
    </blockquote>
    Let's see how that goes.<br>
    This is an experiment. <br>
    <br>
    Regards, Benoit<br>
    <blockquote cite="mid:CABCOCHSq7x6=_HmqSwbLNidce2QfQw1c4t2=Q76dyze3n5=axQ@mail.gmail.com" type="cite">
      <div dir="ltr">
        <div class="gmail_extra">
          <div class="gmail_quote">
            <div><br>
            </div>
            <div>&nbsp;</div>
            <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"><span class=""><font color="#888888"><br>
                  <br>
                  Bert<br>
                </font></span></blockquote>
          </div>
          <br>
        </div>
        <div class="gmail_extra">Andy</div>
        <div class="gmail_extra"><br>
        </div>
      </div>
    </blockquote>
    <br>
  </div>

_______________________________________________<br>yang-doctors mailing list<br><a href="mailto:yang-doctors@ietf.org">yang-doctors@ietf.org</a><br>https://www.ietf.org/mailman/listinfo/yang-doctors<br></blockquote></div><br></div></body></html>
--Apple-Mail=_28FA724A-A50D-4FCE-974B-E4A72E4BA165--

--Apple-Mail=_25E5F46A-2258-40F3-93BA-0DFCBD758C47
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

iQIcBAEBCgAGBQJTtquuAAoJEPcO+I7eiUJZiBsP/2S1gA+fr8zMhuXQCFFHf/+c
2aIsnVwofBXFe+t902z9LIaBn+5+G+2DJOGdCxn5msGPGQH2b7yDkuNpEaZdhYE9
Lrzi1r7iOjN/OlnHmyZrqKe6fcuRVH9DihCVeY6NeD7VnjIVR2+72h1dx+9ULk8p
20srZL0WTrWuPUd0XL5A0oEyQJa9xaemWfjxcQKQW0DSalWxZ+crKrgmwAJI1keJ
ECIPy42r+xzUxoARbDDY5E7uC2q7O/IQsGCB8hEt1YbHJLfVuG/8Gq5Os09M8eCj
lfHyq+mq4WKmTSapQn7y5+wA7PY+epLrEgZ6qdKHG0WGYRJpm3b/P3DT53v2Y4pk
B1uT+uNX25D5fDhp5Z4xc+l/+/PTw/YIyBEi2HzY/wymEmPqJJTIpBoGlOECAgJy
Pno6pKTHzZW8p+nLikRp8wS5PLtkC54w97b4WPOGac6Z4rcJwEz8x2qKz4ku+qUk
K/W01mp5OhzFg/GZuDkv7wVCq4tFVccLZC1bvoJu2tuSg2FRrNtgjzg875kjCoXw
WISXugVsWnylL/hccDj4ur4pACQeclVjfc1X0fyMsEpZDStnQX0lYbtSja0wyjO4
jtxXTBgc/gLYlcY3sgNrAfzsPnv2TtyFu8U/lfR16U9OkgKV6JNpCJ8NnoziAeAE
cbH+Bn4Iio2BosEYymEh
=hoJd
-----END PGP SIGNATURE-----

--Apple-Mail=_25E5F46A-2258-40F3-93BA-0DFCBD758C47--


From nobody Tue Jul  8 13:11:52 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 62A041A002B for <mib-doctors@ietfa.amsl.com>; Tue,  8 Jul 2014 13:11:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.151
X-Spam-Level: 
X-Spam-Status: No, score=-15.151 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.651, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Nd5ru5-tqSog for <mib-doctors@ietfa.amsl.com>; Tue,  8 Jul 2014 13:11:48 -0700 (PDT)
Received: from aer-iport-4.cisco.com (aer-iport-4.cisco.com [173.38.203.54]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A5B011A000B for <mib-doctors@ietf.org>; Tue,  8 Jul 2014 13:11:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=15669; q=dns/txt; s=iport; t=1404850307; x=1406059907; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to; bh=I/IhnP8MDyomAG27dn56n0L0o4DDC8i7i9QpZt4kzrU=; b=ZWJjCLXUVx8RcDI5RU0elsJEIJSXpNPZU9p6Rui+F4DHlB3Z0NO7Rhlv NC9bW5o+PA3Y+/KbnUayRGO2aFc61XawXf6SYDjYZ85swit1N2sRHzmXG Hkwn9mX46ke/1yEsuNuBKEBoqDBviKH9jcmA2Nus2V8Rf0KTnYkZRP4BB M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqQEAOdPvFOtJssW/2dsb2JhbABZg2CDSbwdh0EBgTB1hAMBAQEEI1UBDAQcAwECChYEBAMCAgkDAgECATQHAggGDQEFAgEBBYg5Da49mRoXjmARAQI9EQcGgnGBTAWFapUMgUiFR4x9ggGBRDsvgQs
X-IronPort-AV: E=Sophos;i="5.01,626,1400025600";  d="scan'208,217";a="102675925"
Received: from aer-iport-nat.cisco.com (HELO aer-core-3.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP; 08 Jul 2014 20:11:45 +0000
Received: from [10.60.67.84] (ams-bclaise-8913.cisco.com [10.60.67.84]) by aer-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id s68KBjQX002651; Tue, 8 Jul 2014 20:11:45 GMT
Message-ID: <53BC5081.6090809@cisco.com>
Date: Tue, 08 Jul 2014 22:11:45 +0200
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: "MIB Doctors (E-mail)" <mib-doctors@ietf.org>
References: <CFE17DDA.458C3%alissa@cooperw.in>
In-Reply-To: <CFE17DDA.458C3%alissa@cooperw.in>
X-Forwarded-Message-Id: <CFE17DDA.458C3%alissa@cooperw.in>
Content-Type: multipart/alternative; boundary="------------090502050507060704010803"
Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/82MW9h3iRb73W0J8bcvwf9rTyns
Cc: Adrian Farrel <adrian@olddog.co.uk>, 'Alissa Cooper' <alissa@cooperw.in>
Subject: [MIB-DOCTORS] Fwd: Re: Alissa Cooper's Discuss on draft-ietf-eman-energy-monitoring-mib-12: (with DISCUSS and COMMENT)
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, 08 Jul 2014 20:11:50 -0000

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

MIB doctors,

It seems that the "Security Guidelines for IETF MIB modules" receives 
comment for each MIB module submitted to the IESG.
Is it time to modify it, or are we redoing the same discussions over and 
over?

Regards, Benoit


-------- Original Message --------
Subject: 	Re: Alissa Cooper's Discuss on 
draft-ietf-eman-energy-monitoring-mib-12: (with DISCUSS and COMMENT)
Date: 	Tue, 8 Jul 2014 13:02:50 -0700
From: 	Alissa Cooper <alissa@cooperw.in>
To: 	Benoit Claise <bclaise@cisco.com>, The IESG <iesg@ietf.org>
CC: 	<draft-ietf-eman-energy-monitoring-mib@tools.ietf.org>, 
<eman-chairs@tools.ietf.org>



Hi Benoit,

On 7/8/14, 1:44 AM, "Benoit Claise" <bclaise@cisco.com 
<mailto:bclaise@cisco.com>> wrote:

    Hi Alissa,

    Thanks for your review.
>     Alissa Cooper has entered the following ballot position for
>     draft-ietf-eman-energy-monitoring-mib-12: Discuss
>
>     When responding, please keep the subject line intact and reply to all
>     email addresses included in the To and CC lines. (Feel free to cut this
>     introductory paragraph, however.)
>
>
>     Please refer tohttp://www.ietf.org/iesg/statement/discuss-criteria.html
>     for more information about IESG DISCUSS and COMMENT positions.
>
>
>     The document, along with other ballot positions, can be found here:
>     http://datatracker.ietf.org/doc/draft-ietf-eman-energy-monitoring-mib/
>
>
>
>     ----------------------------------------------------------------------
>     DISCUSS:
>     ----------------------------------------------------------------------
>
>     Section 11 is missing a discussion of the privacy considerations of
>     energy and power monitoring. I would suggest something along the lines of
>     the following:
>
>     "In certain situations, energy and power monitoring can reveal sensitive
>     information about individuals' activities and habits. Implementors of
>     this specification should use appropriate privacy protections as
>     discussed in Section 9 of RFC 6988 and monitoring of individuals and
>     homes should only occur with proper authorization."

    Regarding your first sentence, I propose the following text, which
    would be in line with Security Guidelines for IETF MIB modules at
    http://trac.tools.ietf.org/area/ops/trac/wiki/mib-security

        Some of the readable objects in this MIB module (i.e., objects with a
        MAX-ACCESS other than not-accessible) may be considered sensitive or
        vulnerable in some network environments.  It is thus important to
        control even GET and/or NOTIFY access to these objects and possibly
        to even encrypt the values of these objects when sending them over
        the network via SNMP.  These are the tables and objects and their
        sensitivity/vulnerability:

        Access to the content of the eoPowerStateTable, eoEnergyTable, and
        eoACPwrAttributesTable MIB tables can reveal sensitive
        information about individuals' activities and habits

Sounds good to me.


    Since this document is essentially a MIB module, your last sentence
    is covered by

             implementations
             claiming compliance to the SNMPv3 standard MUST include full
             support for authentication and privacy via the User-based
             Security Model (USM) [RFC3414  <http://tools.ietf.org/html/rfc3414>] with the AES cipher algorithm
             [RFC3826  <http://tools.ietf.org/html/rfc3826>].

RFC 6988 notes the need for privacy protections for stored data, which 
the above text does not speak to, so I still think a reference to RFC 
6988 would add value here.

It is a little disconcerting that use of SNMPv3 is provided as a 
SHOULD-level requirement without discussion of deployment scenarios and 
regardless of the sensitivity of the data being made available by any 
new MIB. For example, the tradeoffs between security and utility might 
be reasonable if (1) Iâ€™m using an older SNMP version on my closed home 
network to monitor my own energy use, but not if (2) my ISP is using it 
to monitor the same thing. The text quoted above basically  endorses 
unauthorized energy monitoring if the provider does not support SNMPv3, 
whereas it seems like what we would want to be saying is that in cases 
like (2) SNMPv3 is required.

I understand that this is basically boilerplate language for MIB docs, 
so Iâ€™m not sure what can be done, but it seems unfortunate.

Alissa



>     ----------------------------------------------------------------------
>     COMMENT:
>     ----------------------------------------------------------------------
>
>     Section 12.1:
>     "New Assignments (and potential deprecation) to Power State Sets
>              shall be administered by IANA and the guidelines and procedures
>              are specified in [EMAN-FMWK], and will, as a consequence, the
>              IANAPowerStateSet Textual Convention should be updated."
>              
>     Not sure what this sentence means.
    Good catch.
    NEW:

             "New Assignments (and potential deprecation) to Power State Sets
             shall be administered by IANA and the guidelines and procedures
             are specified in [EMAN-FMWK], and will, as a consequence, update the
             IANAPowerStateSet Textual Convention."


    Regards, Benoit (as a document author)




--------------090502050507060704010803
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=UTF-8">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    MIB doctors, <br>
    <br>
    It seems that the "<span id="OLK_SRC_BODY_SECTION">Security
      Guidelines for IETF MIB modules" receives comment for each MIB
      module submitted to the IESG.<br>
      Is it time to modify it, or are we redoing the same discussions
      over and over? <br>
      <br>
      Regards, Benoit<br>
    </span>
    <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>Re: Alissa Cooper's Discuss on
              draft-ietf-eman-energy-monitoring-mib-12: (with DISCUSS
              and COMMENT)</td>
          </tr>
          <tr>
            <th align="RIGHT" nowrap="nowrap" valign="BASELINE">Date: </th>
            <td>Tue, 8 Jul 2014 13:02:50 -0700</td>
          </tr>
          <tr>
            <th align="RIGHT" nowrap="nowrap" valign="BASELINE">From: </th>
            <td>Alissa Cooper <a class="moz-txt-link-rfc2396E" href="mailto:alissa@cooperw.in">&lt;alissa@cooperw.in&gt;</a></td>
          </tr>
          <tr>
            <th align="RIGHT" nowrap="nowrap" valign="BASELINE">To: </th>
            <td>Benoit Claise <a class="moz-txt-link-rfc2396E" href="mailto:bclaise@cisco.com">&lt;bclaise@cisco.com&gt;</a>, The IESG
              <a class="moz-txt-link-rfc2396E" href="mailto:iesg@ietf.org">&lt;iesg@ietf.org&gt;</a></td>
          </tr>
          <tr>
            <th align="RIGHT" nowrap="nowrap" valign="BASELINE">CC: </th>
            <td><a class="moz-txt-link-rfc2396E" href="mailto:draft-ietf-eman-energy-monitoring-mib@tools.ietf.org">&lt;draft-ietf-eman-energy-monitoring-mib@tools.ietf.org&gt;</a>,
              <a class="moz-txt-link-rfc2396E" href="mailto:eman-chairs@tools.ietf.org">&lt;eman-chairs@tools.ietf.org&gt;</a></td>
          </tr>
        </tbody>
      </table>
      <br>
      <br>
      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
      <div>Hi Benoit,</div>
      <div><br>
      </div>
      <span id="OLK_SRC_BODY_SECTION">
        <div>
          <div>On 7/8/14, 1:44 AM, "Benoit Claise" &lt;<a
              moz-do-not-send="true" href="mailto:bclaise@cisco.com">bclaise@cisco.com</a>&gt;
            wrote:</div>
        </div>
        <div><br>
        </div>
        <blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE"
          style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0
          0 0 5;">
          <div>
            <div bgcolor="#FFFFFF" text="#000000">
              <div class="moz-cite-prefix">Hi Alissa,<br>
                <br>
                Thanks for your review.<br>
              </div>
              <blockquote
                cite="mid:20140708042418.2373.4207.idtracker@ietfa.amsl.com"
                type="cite">
                <pre wrap="">Alissa Cooper has entered the following ballot position for
draft-ietf-eman-energy-monitoring-mib-12: Discuss

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to <a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://www.ietf.org/iesg/statement/discuss-criteria.html">http://www.ietf.org/iesg/statement/discuss-criteria.html</a>
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://datatracker.ietf.org/doc/draft-ietf-eman-energy-monitoring-mib/">http://datatracker.ietf.org/doc/draft-ietf-eman-energy-monitoring-mib/</a>



----------------------------------------------------------------------
DISCUSS:
----------------------------------------------------------------------

Section 11 is missing a discussion of the privacy considerations of
energy and power monitoring. I would suggest something along the lines of
the following:

"In certain situations, energy and power monitoring can reveal sensitive
information about individuals' activities and habits. Implementors of
this specification should use appropriate privacy protections as
discussed in Section 9 of RFC 6988 and monitoring of individuals and
homes should only occur with proper authorization."</pre>
              </blockquote>
              <br>
              Regarding your first sentence, I propose the following
              text, which would be in line with Security Guidelines for
              IETF MIB modules at <a moz-do-not-send="true"
                class="moz-txt-link-freetext"
                href="http://trac.tools.ietf.org/area/ops/trac/wiki/mib-security">http://trac.tools.ietf.org/area/ops/trac/wiki/mib-security</a>
              <pre class="wiki">   Some of the readable objects in this MIB module (i.e., objects with a
   MAX-ACCESS other than not-accessible) may be considered sensitive or
   vulnerable in some network environments.  It is thus important to
   control even GET and/or NOTIFY access to these objects and possibly
   to even encrypt the values of these objects when sending them over
   the network via SNMP.  These are the tables and objects and their
   sensitivity/vulnerability:

   Access to the content of the eoPowerStateTable, eoEnergyTable, and 
   eoACPwrAttributesTable MIB tables can reveal sensitive
   information about individuals' activities and habits
</pre>
            </div>
          </div>
        </blockquote>
      </span>
      <div>Sounds good to me.</div>
      <div><br>
      </div>
      <span id="OLK_SRC_BODY_SECTION">
        <blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE"
          style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0
          0 0 5;">
          <div>
            <div bgcolor="#FFFFFF" text="#000000"><br>
              Since this document is essentially a MIB module, your last
              sentence is covered by <br>
              <pre class="newpage">        implementations
        claiming compliance to the SNMPv3 standard MUST include full
        support for authentication and privacy via the User-based
        Security Model (USM) [<a moz-do-not-send="true" href="http://tools.ietf.org/html/rfc3414" title="U. and B. Wijnen">RFC3414</a>] with the AES cipher algorithm
        [<a moz-do-not-send="true" href="http://tools.ietf.org/html/rfc3826" title="&quot;The Advanced Encryption Standard (AES) Cipher Algorithm in the SNMP User-based Security Model&quot;">RFC3826</a>].</pre>
            </div>
          </div>
        </blockquote>
      </span>
      <div>RFC 6988 notes the need for privacy protections for stored
        data, which the above text does not speak to, so I still think a
        reference to RFC 6988 would add value here.</div>
      <div><br>
      </div>
      <div>It is a little disconcerting that use of SNMPv3 is provided
        as a SHOULD-level requirement without discussion of deployment
        scenarios and regardless of the sensitivity of the data being
        made available by any new MIB. For example, the tradeoffs
        between security and utility might be reasonable if (1) Iâ€™m
        using an older SNMP version on my closed home network to monitor
        my own energy use, but not if (2) my ISP is using it to monitor
        the same thing. The text quoted above basically Â endorses
        unauthorized energy monitoring if the provider does not support
        SNMPv3, whereas it seems like what we would want to be saying is
        that in cases like (2) SNMPv3 is required.</div>
      <div><br>
      </div>
      <div>I understand that this is basically boilerplate language for
        MIB docs, so Iâ€™m not sure what can be done, but it seems
        unfortunate.</div>
      <div><br>
      </div>
      <div>Alissa</div>
      <div><br>
      </div>
      <span id="OLK_SRC_BODY_SECTION">
        <blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE"
          style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0
          0 0 5;">
          <div>
            <div bgcolor="#FFFFFF" text="#000000"><br>
              <br>
              <blockquote
                cite="mid:20140708042418.2373.4207.idtracker@ietfa.amsl.com"
                type="cite">
                <pre wrap="">----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Section 12.1:
"New Assignments (and potential deprecation) to Power State Sets 
        shall be administered by IANA and the guidelines and procedures 
        are specified in [EMAN-FMWK], and will, as a consequence, the 
        IANAPowerStateSet Textual Convention should be updated."
        
Not sure what this sentence means.</pre>
              </blockquote>
              Good catch.<br>
              NEW:<br>
              <pre wrap="">        "New Assignments (and potential deprecation) to Power State Sets 
        shall be administered by IANA and the guidelines and procedures 
        are specified in [EMAN-FMWK], and will, as a consequence, update the 
        IANAPowerStateSet Textual Convention."


Regards, Benoit (as a document author)
</pre>
            </div>
          </div>
        </blockquote>
      </span>
      <br>
    </div>
    <br>
  </body>
</html>

--------------090502050507060704010803--


From nobody Tue Jul  8 13:26: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 B70CC1A000F for <mib-doctors@ietfa.amsl.com>; Tue,  8 Jul 2014 13:26:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.552
X-Spam-Level: 
X-Spam-Status: No, score=-2.552 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.651, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y0taeFPPbzzx for <mib-doctors@ietfa.amsl.com>; Tue,  8 Jul 2014 13:26:18 -0700 (PDT)
Received: from lucidvision.com (lucidvision.com [72.71.250.34]) by ietfa.amsl.com (Postfix) with ESMTP id A87CE1A0002 for <mib-doctors@ietf.org>; Tue,  8 Jul 2014 13:26:17 -0700 (PDT)
Received: from [192.168.1.105] (static-72-71-250-37.cncdnh.fast04.myfairpoint.net [72.71.250.37]) by lucidvision.com (Postfix) with ESMTP id 224B028160A0; Tue,  8 Jul 2014 16:26:17 -0400 (EDT)
Content-Type: multipart/signed; boundary="Apple-Mail=_EE4449E1-636E-446C-B17A-1755219FE111"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\))
From: "Thomas D. Nadeau" <tnadeau@lucidvision.com>
In-Reply-To: <53BC5081.6090809@cisco.com>
Date: Tue, 8 Jul 2014 16:26:15 -0400
Message-Id: <D3086CBF-F612-4C59-961E-4B41B28014EF@lucidvision.com>
References: <CFE17DDA.458C3%alissa@cooperw.in> <53BC5081.6090809@cisco.com>
To: Benoit Claise <bclaise@cisco.com>
X-Mailer: Apple Mail (2.1878.2)
Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/XgaeB7Twv0pasmizqCpTuUlKUp0
Cc: "MIB Doctors \(E-mail\)" <mib-doctors@ietf.org>, Alissa Cooper <alissa@cooperw.in>, Farrel Adrian <adrian@olddog.co.uk>
Subject: Re: [MIB-DOCTORS] Fwd: Re: Alissa Cooper's Discuss on draft-ietf-eman-energy-monitoring-mib-12: (with DISCUSS and COMMENT)
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, 08 Jul 2014 20:26:20 -0000

--Apple-Mail=_EE4449E1-636E-446C-B17A-1755219FE111
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_89A949CC-27A2-4934-BBB2-34ACB6AFA00E"


--Apple-Mail=_89A949CC-27A2-4934-BBB2-34ACB6AFA00E
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

Good idea.


On Jul 8, 2014:4:11 PM, at 4:11 PM, Benoit Claise <bclaise@cisco.com> =
wrote:

> MIB doctors,=20
>=20
> It seems that the "Security Guidelines for IETF MIB modules" receives =
comment for each MIB module submitted to the IESG.
> Is it time to modify it, or are we redoing the same discussions over =
and over?=20
>=20
> Regards, Benoit
>=20
>=20
> -------- Original Message --------
> Subject:	Re: Alissa Cooper's Discuss on =
draft-ietf-eman-energy-monitoring-mib-12: (with DISCUSS and COMMENT)
> Date:	Tue, 8 Jul 2014 13:02:50 -0700
> From:	Alissa Cooper <alissa@cooperw.in>
> To:	Benoit Claise <bclaise@cisco.com>, The IESG <iesg@ietf.org>
> CC:	<draft-ietf-eman-energy-monitoring-mib@tools.ietf.org>, =
<eman-chairs@tools.ietf.org>
>=20
> Hi Benoit,
>=20
> On 7/8/14, 1:44 AM, "Benoit Claise" <bclaise@cisco.com> wrote:
>=20
> Hi Alissa,
>=20
> Thanks for your review.
>> Alissa Cooper has entered the following ballot position for
>> draft-ietf-eman-energy-monitoring-mib-12: Discuss
>>=20
>> When responding, please keep the subject line intact and reply to all
>> email addresses included in the To and CC lines. (Feel free to cut =
this
>> introductory paragraph, however.)
>>=20
>>=20
>> Please refer to =
http://www.ietf.org/iesg/statement/discuss-criteria.html
>> for more information about IESG DISCUSS and COMMENT positions.
>>=20
>>=20
>> The document, along with other ballot positions, can be found here:
>> =
http://datatracker.ietf.org/doc/draft-ietf-eman-energy-monitoring-mib/
>>=20
>>=20
>>=20
>> =
----------------------------------------------------------------------
>> DISCUSS:
>> =
----------------------------------------------------------------------
>>=20
>> Section 11 is missing a discussion of the privacy considerations of
>> energy and power monitoring. I would suggest something along the =
lines of
>> the following:
>>=20
>> "In certain situations, energy and power monitoring can reveal =
sensitive
>> information about individuals' activities and habits. Implementors of
>> this specification should use appropriate privacy protections as
>> discussed in Section 9 of RFC 6988 and monitoring of individuals and
>> homes should only occur with proper authorization."
>=20
> Regarding your first sentence, I propose the following text, which =
would be in line with Security Guidelines for IETF MIB modules at =
http://trac.tools.ietf.org/area/ops/trac/wiki/mib-security
>    Some of the readable objects in this MIB module (i.e., objects with =
a
>    MAX-ACCESS other than not-accessible) may be considered sensitive =
or
>    vulnerable in some network environments.  It is thus important to
>    control even GET and/or NOTIFY access to these objects and possibly
>    to even encrypt the values of these objects when sending them over
>    the network via SNMP.  These are the tables and objects and their
>    sensitivity/vulnerability:
>=20
>    Access to the content of the eoPowerStateTable, eoEnergyTable, and=20=

>    eoACPwrAttributesTable MIB tables can reveal sensitive
>    information about individuals' activities and habits
> Sounds good to me.
>=20
>=20
> Since this document is essentially a MIB module, your last sentence is =
covered by=20
>         implementations
>         claiming compliance to the SNMPv3 standard MUST include full
>         support for authentication and privacy via the User-based
>         Security Model (USM) [RFC3414] with the AES cipher algorithm
>         [RFC3826].
> RFC 6988 notes the need for privacy protections for stored data, which =
the above text does not speak to, so I still think a reference to RFC =
6988 would add value here.
>=20
> It is a little disconcerting that use of SNMPv3 is provided as a =
SHOULD-level requirement without discussion of deployment scenarios and =
regardless of the sensitivity of the data being made available by any =
new MIB. For example, the tradeoffs between security and utility might =
be reasonable if (1) I=92m using an older SNMP version on my closed home =
network to monitor my own energy use, but not if (2) my ISP is using it =
to monitor the same thing. The text quoted above basically  endorses =
unauthorized energy monitoring if the provider does not support SNMPv3, =
whereas it seems like what we would want to be saying is that in cases =
like (2) SNMPv3 is required.
>=20
> I understand that this is basically boilerplate language for MIB docs, =
so I=92m not sure what can be done, but it seems unfortunate.
>=20
> Alissa
>=20
>=20
>=20
>> =
----------------------------------------------------------------------
>> COMMENT:
>> =
----------------------------------------------------------------------
>>=20
>> Section 12.1:
>> "New Assignments (and potential deprecation) to Power State Sets=20
>>         shall be administered by IANA and the guidelines and =
procedures=20
>>         are specified in [EMAN-FMWK], and will, as a consequence, the=20=

>>         IANAPowerStateSet Textual Convention should be updated."
>>        =20
>> Not sure what this sentence means.
> Good catch.
> NEW:
>         "New Assignments (and potential deprecation) to Power State =
Sets=20
>         shall be administered by IANA and the guidelines and =
procedures=20
>         are specified in [EMAN-FMWK], and will, as a consequence, =
update the=20
>         IANAPowerStateSet Textual Convention."
>=20
>=20
> Regards, Benoit (as a document author)
>=20
>=20
> _______________________________________________
> MIB-DOCTORS mailing list
> MIB-DOCTORS@ietf.org
> https://www.ietf.org/mailman/listinfo/mib-doctors


--Apple-Mail=_89A949CC-27A2-4934-BBB2-34ACB6AFA00E
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;">Good =
idea.<div><br></div><div><br><div style=3D""><div>On Jul 8, 2014:4:11 =
PM, at 4:11 PM, Benoit Claise &lt;<a =
href=3D"mailto:bclaise@cisco.com">bclaise@cisco.com</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite">
 =20

    <meta http-equiv=3D"content-type" content=3D"text/html; =
charset=3DUTF-8">
 =20
  <div bgcolor=3D"#FFFFFF" text=3D"#000000">
    MIB doctors, <br>
    <br>
    It seems that the "<span id=3D"OLK_SRC_BODY_SECTION">Security
      Guidelines for IETF MIB modules" receives comment for each MIB
      module submitted to the IESG.<br>
      Is it time to modify it, or are we redoing the same discussions
      over and over? <br>
      <br>
      Regards, Benoit<br>
    </span>
    <div class=3D"moz-forward-container"><br>
      <br>
      -------- Original Message --------
      <table class=3D"moz-email-headers-table" cellpadding=3D"0" =
cellspacing=3D"0" border=3D"0">
        <tbody>
          <tr>
            <th align=3D"RIGHT" nowrap=3D"nowrap" =
valign=3D"BASELINE">Subject:
            </th>
            <td>Re: Alissa Cooper's Discuss on
              draft-ietf-eman-energy-monitoring-mib-12: (with DISCUSS
              and COMMENT)</td>
          </tr>
          <tr>
            <th align=3D"RIGHT" nowrap=3D"nowrap" =
valign=3D"BASELINE">Date: </th>
            <td>Tue, 8 Jul 2014 13:02:50 -0700</td>
          </tr>
          <tr>
            <th align=3D"RIGHT" nowrap=3D"nowrap" =
valign=3D"BASELINE">From: </th>
            <td>Alissa Cooper <a class=3D"moz-txt-link-rfc2396E" =
href=3D"mailto:alissa@cooperw.in">&lt;alissa@cooperw.in&gt;</a></td>
          </tr>
          <tr>
            <th align=3D"RIGHT" nowrap=3D"nowrap" valign=3D"BASELINE">To: =
</th>
            <td>Benoit Claise <a class=3D"moz-txt-link-rfc2396E" =
href=3D"mailto:bclaise@cisco.com">&lt;bclaise@cisco.com&gt;</a>, The =
IESG
              <a class=3D"moz-txt-link-rfc2396E" =
href=3D"mailto:iesg@ietf.org">&lt;iesg@ietf.org&gt;</a></td>
          </tr>
          <tr>
            <th align=3D"RIGHT" nowrap=3D"nowrap" valign=3D"BASELINE">CC: =
</th>
            <td><a class=3D"moz-txt-link-rfc2396E" =
href=3D"mailto:draft-ietf-eman-energy-monitoring-mib@tools.ietf.org">&lt;d=
raft-ietf-eman-energy-monitoring-mib@tools.ietf.org&gt;</a>,
              <a class=3D"moz-txt-link-rfc2396E" =
href=3D"mailto:eman-chairs@tools.ietf.org">&lt;eman-chairs@tools.ietf.org&=
gt;</a></td>
          </tr>
        </tbody>
      </table>
      <br>
      <br>
      <meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3DUTF-8">
      <div>Hi Benoit,</div>
      <div><br>
      </div>
      <span id=3D"OLK_SRC_BODY_SECTION">
        <div>
          <div>On 7/8/14, 1:44 AM, "Benoit Claise" &lt;<a =
moz-do-not-send=3D"true" =
href=3D"mailto:bclaise@cisco.com">bclaise@cisco.com</a>&gt;
            wrote:</div>
        </div>
        <div><br>
        </div>
        <blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" =
style=3D"BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0
          0 0 5;">
          <div>
            <div bgcolor=3D"#FFFFFF" text=3D"#000000">
              <div class=3D"moz-cite-prefix">Hi Alissa,<br>
                <br>
                Thanks for your review.<br>
              </div>
              <blockquote =
cite=3D"mid:20140708042418.2373.4207.idtracker@ietfa.amsl.com" =
type=3D"cite">
                <pre wrap=3D"">Alissa Cooper has entered the following =
ballot position for
draft-ietf-eman-energy-monitoring-mib-12: Discuss

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to <a moz-do-not-send=3D"true" =
class=3D"moz-txt-link-freetext" =
href=3D"http://www.ietf.org/iesg/statement/discuss-criteria.html">http://w=
ww.ietf.org/iesg/statement/discuss-criteria.html</a>
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
<a moz-do-not-send=3D"true" class=3D"moz-txt-link-freetext" =
href=3D"http://datatracker.ietf.org/doc/draft-ietf-eman-energy-monitoring-=
mib/">http://datatracker.ietf.org/doc/draft-ietf-eman-energy-monitoring-mi=
b/</a>



----------------------------------------------------------------------
DISCUSS:
----------------------------------------------------------------------

Section 11 is missing a discussion of the privacy considerations of
energy and power monitoring. I would suggest something along the lines =
of
the following:

"In certain situations, energy and power monitoring can reveal sensitive
information about individuals' activities and habits. Implementors of
this specification should use appropriate privacy protections as
discussed in Section 9 of RFC 6988 and monitoring of individuals and
homes should only occur with proper authorization."</pre>
              </blockquote>
              <br>
              Regarding your first sentence, I propose the following
              text, which would be in line with Security Guidelines for
              IETF MIB modules at <a moz-do-not-send=3D"true" =
class=3D"moz-txt-link-freetext" =
href=3D"http://trac.tools.ietf.org/area/ops/trac/wiki/mib-security">http:/=
/trac.tools.ietf.org/area/ops/trac/wiki/mib-security</a>
              <pre class=3D"wiki">   Some of the readable objects in =
this MIB module (i.e., objects with a
   MAX-ACCESS other than not-accessible) may be considered sensitive or
   vulnerable in some network environments.  It is thus important to
   control even GET and/or NOTIFY access to these objects and possibly
   to even encrypt the values of these objects when sending them over
   the network via SNMP.  These are the tables and objects and their
   sensitivity/vulnerability:

   Access to the content of the eoPowerStateTable, eoEnergyTable, and=20
   eoACPwrAttributesTable MIB tables can reveal sensitive
   information about individuals' activities and habits
</pre>
            </div>
          </div>
        </blockquote>
      </span>
      <div>Sounds good to me.</div>
      <div><br>
      </div>
      <span id=3D"OLK_SRC_BODY_SECTION">
        <blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" =
style=3D"BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0
          0 0 5;">
          <div>
            <div bgcolor=3D"#FFFFFF" text=3D"#000000"><br>
              Since this document is essentially a MIB module, your last
              sentence is covered by <br>
              <pre class=3D"newpage">        implementations
        claiming compliance to the SNMPv3 standard MUST include full
        support for authentication and privacy via the User-based
        Security Model (USM) [<a moz-do-not-send=3D"true" =
href=3D"http://tools.ietf.org/html/rfc3414" title=3D"U. and B. =
Wijnen">RFC3414</a>] with the AES cipher algorithm
        [<a moz-do-not-send=3D"true" =
href=3D"http://tools.ietf.org/html/rfc3826" title=3D"&quot;The Advanced =
Encryption Standard (AES) Cipher Algorithm in the SNMP User-based =
Security Model&quot;">RFC3826</a>].</pre>
            </div>
          </div>
        </blockquote>
      </span>
      <div>RFC 6988 notes the need for privacy protections for stored
        data, which the above text does not speak to, so I still think a
        reference to RFC 6988 would add value here.</div>
      <div><br>
      </div>
      <div>It is a little disconcerting that use of SNMPv3 is provided
        as a SHOULD-level requirement without discussion of deployment
        scenarios and regardless of the sensitivity of the data being
        made available by any new MIB. For example, the tradeoffs
        between security and utility might be reasonable if (1) I=92m
        using an older SNMP version on my closed home network to monitor
        my own energy use, but not if (2) my ISP is using it to monitor
        the same thing. The text quoted above basically &nbsp;endorses
        unauthorized energy monitoring if the provider does not support
        SNMPv3, whereas it seems like what we would want to be saying is
        that in cases like (2) SNMPv3 is required.</div>
      <div><br>
      </div>
      <div>I understand that this is basically boilerplate language for
        MIB docs, so I=92m not sure what can be done, but it seems
        unfortunate.</div>
      <div><br>
      </div>
      <div>Alissa</div>
      <div><br>
      </div>
      <span id=3D"OLK_SRC_BODY_SECTION">
        <blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" =
style=3D"BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0
          0 0 5;">
          <div>
            <div bgcolor=3D"#FFFFFF" text=3D"#000000"><br>
              <br>
              <blockquote =
cite=3D"mid:20140708042418.2373.4207.idtracker@ietfa.amsl.com" =
type=3D"cite">
                <pre =
wrap=3D"">----------------------------------------------------------------=
------
COMMENT:
----------------------------------------------------------------------

Section 12.1:
"New Assignments (and potential deprecation) to Power State Sets=20
        shall be administered by IANA and the guidelines and procedures=20=

        are specified in [EMAN-FMWK], and will, as a consequence, the=20
        IANAPowerStateSet Textual Convention should be updated."
       =20
Not sure what this sentence means.</pre>
              </blockquote>
              Good catch.<br>
              NEW:<br>
              <pre wrap=3D"">        "New Assignments (and potential =
deprecation) to Power State Sets=20
        shall be administered by IANA and the guidelines and procedures=20=

        are specified in [EMAN-FMWK], and will, as a consequence, update =
the=20
        IANAPowerStateSet Textual Convention."


Regards, Benoit (as a document author)
</pre>
            </div>
          </div>
        </blockquote>
      </span>
      <br>
    </div>
    <br>
  </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></div><=
/body></html>=

--Apple-Mail=_89A949CC-27A2-4934-BBB2-34ACB6AFA00E--

--Apple-Mail=_EE4449E1-636E-446C-B17A-1755219FE111
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

iQIcBAEBCgAGBQJTvFPoAAoJEPcO+I7eiUJZhmYP/087JADfiw71RBS0ktV28TA5
bjbCV1NfXt3IJdEPW6TuwQ95QDvDvfUIFjTHmnmat1V3pv4ckuxZsKmdZikCK8s0
Y+C7cJUgKXtI/YKMofGJ2imAjl7Tvo0fCSV026r1VyvbiuypvlrMeHmRCKSk+mlZ
y1evfjEb5JpleCF0oqhy/bCxr/xKp1nCGRrmPEqx3320La6Vp9BtmEF2GlsRWtMP
DHzSTmfO1IAwoXVid0O+3uND0FgF0EGund1pQN5UoskeVIdnUo7bUcgDzJz2a1P0
M3yh/9M0mcPjpd8pFEE5PFxteA6XpcF8DIXh9SyPzivtNQlpsEy2q1TW+hKiXQ9I
iWqBJbuhsid6mC+CoXWJYZiMDBnpeURVXZuj9vre726YzSVU8x5TT6I5Sc0dk4qp
r71or48KHKmJO9D/o+ZisLSALkt+LBJ+13Sx17w2dSQcMqsMBV985ejCXOr1eoZD
4Ycp3IGP9uV31XLFd+YV+T/KsGeyPuHIsLBj9oUkx8Gh0YdfF16RlvtnJRSXU6L+
7i2eTVMB7tlTYBah/yOE48iWYaNn5oVHHTCTXtins2oVxjQHQFu7gIOViPM7vrI7
0WsHDUTH2ecrMseEbZE6FkiggOLvRY0N16e1toZLsntA4yCqc8KABQE/eKgWeIF9
B+NXDRvZCofHmKDnBm6s
=jKdK
-----END PGP SIGNATURE-----

--Apple-Mail=_EE4449E1-636E-446C-B17A-1755219FE111--


From nobody Wed Jul  9 08:42:51 2014
Return-Path: <bclaise@cisco.com>
X-Original-To: mib-doctors@ietfa.amsl.com
Delivered-To: mib-doctors@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 52F6D1A0AFC for <mib-doctors@ietfa.amsl.com>; Wed,  9 Jul 2014 08:42:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.151
X-Spam-Level: 
X-Spam-Status: No, score=-15.151 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.651, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0prVRlITxq0L for <mib-doctors@ietfa.amsl.com>; Wed,  9 Jul 2014 08:42:44 -0700 (PDT)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EE3CD1A0AF4 for <mib-doctors@ietf.org>; Wed,  9 Jul 2014 08:42:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=11880; q=dns/txt; s=iport; t=1404920571; x=1406130171; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to; bh=XI9aS4fZqNRlISEd5L66CYKp6m7VICXCQRVpb2K28r8=; b=TiHL2jQbZoumonI/z7iyfh0JqtDxXiyQtGQUHh8KBRoKloenGFQHcpyi FAqQFY3XjFDvAEeaWhpZKan6Fyydbe+AXkXSC9vtz0QfsUuS9mmlg5th1 5RoHnTvfdlLDgtcdszaLMmwVWj83pu68zOMd2ZQo1hp/3poDgZNVT0yQI k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvkTAJdivVOtJssW/2dsb2JhbABWA4Ngv3kJhhWBIQGBJnWEAwEBAQR4AQwCAgsQAQQBAQEJFggHCQMCAQIBCSsJCAYBDAEFAgEBiD4NyQsXBI5cEQEkHBAHBgMIhDIFmnaHD4x9ggGBRDuBOg
X-IronPort-AV: E=Sophos;i="5.01,631,1400025600";  d="scan'208,217";a="107731938"
Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-1.cisco.com with ESMTP; 09 Jul 2014 15:42:48 +0000
Received: from [10.60.67.84] (ams-bclaise-8913.cisco.com [10.60.67.84]) by aer-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id s69FgesO007656; Wed, 9 Jul 2014 15:42:40 GMT
Message-ID: <53BD62F0.8060200@cisco.com>
Date: Wed, 09 Jul 2014 17:42:40 +0200
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: adrian@olddog.co.uk, "'Juergen Schoenwaelder'" <j.schoenwaelder@jacobs-university.de>
References: <001e01cf80e0$ba2b1910$2e814b30$@olddog.co.uk> <20140605184314.GA12812@elstar.local> <00a101cf80f7$1da42d90$58ec88b0$@olddog.co.uk>
In-Reply-To: <00a101cf80f7$1da42d90$58ec88b0$@olddog.co.uk>
Content-Type: multipart/alternative; boundary="------------070807070400010001000605"
Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/seRclxs3lNvPqFxckepY4T7fH08
Cc: "'MIB Doctors \(E-mail\)'" <mib-doctors@ietf.org>
Subject: Re: [MIB-DOCTORS] Fwd: Request to add to the MIB boilperplate for "writeable objects"
X-BeenThere: mib-doctors@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: MIB Doctors list <mib-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mib-doctors/>
List-Post: <mailto:mib-doctors@ietf.org>
List-Help: <mailto:mib-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Jul 2014 15:42:47 -0000

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

Adrian,

Coming back to this one now that the dust has settled (another way to 
express: sorry for delay)

I make three conclusions from this email thread
1.  There is consensus not to add this text

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

    - <list of reasons>

    - <list of objects>

2.  I was wrong in my AD review 
(https://datatracker.ietf.org/doc/draft-ietf-bfd-mib/ballot/#benoit-claise). 

That led to your proposal in point 3.  Apologies for this.

3.  There is consensus not to add this text

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


Thanks Adrian for trying to improve the boilerplate.

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


--------------070807070400010001000605
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>
      Coming back to this one now that the dust has settled (another way
      to express: sorry for delay)<br>
      <br>
      I make three conclusions from this email thread <br>
      1.&nbsp; There is consensus not to add this text<br>
      <blockquote>
        <pre><span style="mso-ansi-language:EN-US" lang="EN-US">The following objects in the MIB modules in this document have write access<o:p></o:p>
either through read-write or read-create MAX-ACCESS clauses. The level of access<o:p></o:p>
to these objects have been discussed by the &lt;xxxx&gt; working group and it was<o:p></o:p>
concluded that write access was beneficial for the following reasons:<o:p></o:p></span></pre>
        <pre><span style="mso-ansi-language:EN-US" lang="EN-US">- &lt;list of reasons&gt;<o:p></o:p></span></pre>
        <pre><span style="mso-ansi-language:EN-US" lang="EN-US">- &lt;list of objects&gt;</span></pre>
      </blockquote>
      2.&nbsp; I was wrong in my AD review
      (<a class="moz-txt-link-freetext" href="https://datatracker.ietf.org/doc/draft-ietf-bfd-mib/ballot/#benoit-claise">https://datatracker.ietf.org/doc/draft-ietf-bfd-mib/ballot/#benoit-claise</a>).
      <br>
      That led to your proposal in point 3.&nbsp; Apologies for this.<br>
      <br>
      3.&nbsp; There is consensus not to add this text<br>
      <blockquote>
        <pre><span style="mso-ansi-language:EN-US" lang="EN-US">As with all MIB modules, an attempt to SET or CREATE an object to a value that<o:p></o:p>
is not supported by the implementation will result in a failure using a return<o:p></o:p>
code that indicates that the value is not supported.</span></pre>
      </blockquote>
      <br>
      Thanks Adrian for trying to improve the boilerplate.<br>
      <br>
      Regards, Benoit<br>
    </div>
    <blockquote cite="mid:00a101cf80f7$1da42d90$58ec88b0$@olddog.co.uk"
      type="cite">
      <pre wrap="">Well Juergen, I'm not under-occupied that I spend time concocting text and
proposing it for boilerplate just to fill a few idle hours!

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

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

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

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

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

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

Thanks to all for your time.

Adrian


</pre>
      <blockquote type="cite">
        <pre wrap="">-----Original Message-----
From: Juergen Schoenwaelder [<a class="moz-txt-link-freetext" href="mailto:j.schoenwaelder@jacobs-university.de">mailto:j.schoenwaelder@jacobs-university.de</a>]
Sent: 05 June 2014 19:43
To: Adrian Farrel
Cc: 'Romascanu, Dan (Dan)'; 'Benoit Claise'; 'MIB Doctors (E-mail)'
Subject: Re: [MIB-DOCTORS] Fwd: Request to add to the MIB boilperplate for
"writeable objects"

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

</pre>
        </blockquote>
        <pre wrap="">
Has this ever been a real issue?

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

/js

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

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

--------------070807070400010001000605--


From nobody Wed Jul  9 08: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 2F8601A0B00 for <mib-doctors@ietfa.amsl.com>; Wed,  9 Jul 2014 08:58:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.151
X-Spam-Level: 
X-Spam-Status: No, score=-15.151 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.651, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R08P1NskSfYh for <mib-doctors@ietfa.amsl.com>; Wed,  9 Jul 2014 08:58:12 -0700 (PDT)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D8CBA1A0AFF for <mib-doctors@ietf.org>; Wed,  9 Jul 2014 08:58:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=21362; q=dns/txt; s=iport; t=1404921498; x=1406131098; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to; bh=IiGAmTcKRtg0lOd/H0HLLz6CjiUoyKwfiLdqwYRz6vE=; b=D0+0zSareHFUa+R8Rl46+49ovCPVml6BI0+hSu19805w36NlnmKOG8If rQ0DdVusy8Z6OvWx1giwVICZOm3E8VDABXjHIpq4m5Z8R7cXV0Ip/UF3s Urg/JiDO1bhrxDb8wIJJRwsL3K0HSG6tWRLozVSTjIid7wkLB4uv0igWe s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AusTABtmvVOtJssW/2dsb2JhbABZg2C/bwEHC4c2AYEmdYQDAQEBAwEBAQFrCgEFBwQcAwECAQkWBAQHCQMCAQIBFR8JCAYNAQUCAQEFiDEIDch5F45gEQECLBERBwaEPQWFapUMgUiFR4x9ggGBRDsvgQs
X-IronPort-AV: E=Sophos;i="5.01,632,1400025600";  d="scan'208,217";a="107732380"
Received: from aer-iport-nat.cisco.com (HELO aer-core-1.cisco.com) ([173.38.203.22]) by aer-iport-1.cisco.com with ESMTP; 09 Jul 2014 15:58:16 +0000
Received: from [10.60.67.84] (ams-bclaise-8913.cisco.com [10.60.67.84]) by aer-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id s69Fw8Go002232; Wed, 9 Jul 2014 15:58:08 GMT
Message-ID: <53BD6690.2040102@cisco.com>
Date: Wed, 09 Jul 2014 17:58:08 +0200
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: "MIB Doctors (E-mail)" <mib-doctors@ietf.org>
References: <CFE17DDA.458C3%alissa@cooperw.in> <53BC5081.6090809@cisco.com>
In-Reply-To: <53BC5081.6090809@cisco.com>
Content-Type: multipart/alternative; boundary="------------070206080601090700060500"
Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/S1kQ_YbZWl05U21aoeMgsNNXmQY
Cc: Adrian Farrel <adrian@olddog.co.uk>, 'Alissa Cooper' <alissa@cooperw.in>
Subject: [MIB-DOCTORS] Change the boilerplate (was: Fwd: Re: Alissa Cooper's Discuss on draft-ietf-eman-energy-monitoring-mib-12: (with DISCUSS and COMMENT))
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, 09 Jul 2014 15:58:18 -0000

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

MIB doctors,

Let me focus the discussion a little bit.
Alissa refers to this sentence in the boilerplate at 
http://trac.tools.ietf.org/area/ops/trac/wiki/mib-security

        Implementations SHOULD provide the security features described by the
        SNMPv3 framework (see [RFC3410]), and implementations claiming compliance
        to the SNMPv3 standard MUST include full support for authentication and
        privacy via the User-based Security Model (USM) [RFC3414] with the AES
        cipher algorithm [RFC3826].


Alissa's feedback is:

    It is a little disconcerting that use of SNMPv3 is provided as a
    SHOULD-level requirement without discussion of deployment scenarios
    and regardless of the sensitivity of the data being made available
    by any new MIB. For example, the tradeoffs between security and
    utility might be reasonable if (1) I'm using an older SNMP version
    on my closed home network to monitor my own energy use, but not if
    (2) my ISP is using it to monitor the same thing. The text quoted
    above basically  endorses unauthorized energy monitoring if the
    provider does not support SNMPv3, whereas it seems like what we
    would want to be saying is that in cases like (2) SNMPv3 is required.

Can one of the old timers (who was part of the discussion) explain the 
SHOULD rational? Personally, I can see two use cases in favor off the 
SHOULD: an older SNMP version in a closed network,  or a private data 
communication network dedicated to network management with special 
protection out of SNMP (like encrypted tunnel)

Should we now modify this sentence to say?

    MUST provide the security features described by the
    SNMPv3 framework (see [RFC3410])

Regards, Benoit

> MIB doctors,
>
> It seems that the "Security Guidelines for IETF MIB modules" receives 
> comment for each MIB module submitted to the IESG.
> Is it time to modify it, or are we redoing the same discussions over 
> and over?
>
> Regards, Benoit
>
>
> -------- Original Message --------
> Subject: 	Re: Alissa Cooper's Discuss on 
> draft-ietf-eman-energy-monitoring-mib-12: (with DISCUSS and COMMENT)
> Date: 	Tue, 8 Jul 2014 13:02:50 -0700
> From: 	Alissa Cooper <alissa@cooperw.in>
> To: 	Benoit Claise <bclaise@cisco.com>, The IESG <iesg@ietf.org>
> CC: 	<draft-ietf-eman-energy-monitoring-mib@tools.ietf.org>, 
> <eman-chairs@tools.ietf.org>
>
>
>
> Hi Benoit,
>
> On 7/8/14, 1:44 AM, "Benoit Claise" <bclaise@cisco.com 
> <mailto:bclaise@cisco.com>> wrote:
>
>     Hi Alissa,
>
>     Thanks for your review.
>>     Alissa Cooper has entered the following ballot position for
>>     draft-ietf-eman-energy-monitoring-mib-12: Discuss
>>
>>     When responding, please keep the subject line intact and reply to all
>>     email addresses included in the To and CC lines. (Feel free to cut this
>>     introductory paragraph, however.)
>>
>>
>>     Please refer tohttp://www.ietf.org/iesg/statement/discuss-criteria.html
>>     for more information about IESG DISCUSS and COMMENT positions.
>>
>>
>>     The document, along with other ballot positions, can be found here:
>>     http://datatracker.ietf.org/doc/draft-ietf-eman-energy-monitoring-mib/
>>
>>
>>
>>     ----------------------------------------------------------------------
>>     DISCUSS:
>>     ----------------------------------------------------------------------
>>
>>     Section 11 is missing a discussion of the privacy considerations of
>>     energy and power monitoring. I would suggest something along the lines of
>>     the following:
>>
>>     "In certain situations, energy and power monitoring can reveal sensitive
>>     information about individuals' activities and habits. Implementors of
>>     this specification should use appropriate privacy protections as
>>     discussed in Section 9 of RFC 6988 and monitoring of individuals and
>>     homes should only occur with proper authorization."
>
>     Regarding your first sentence, I propose the following text, which
>     would be in line with Security Guidelines for IETF MIB modules at
>     http://trac.tools.ietf.org/area/ops/trac/wiki/mib-security
>
>         Some of the readable objects in this MIB module (i.e., objects with a
>         MAX-ACCESS other than not-accessible) may be considered sensitive or
>         vulnerable in some network environments.  It is thus important to
>         control even GET and/or NOTIFY access to these objects and possibly
>         to even encrypt the values of these objects when sending them over
>         the network via SNMP.  These are the tables and objects and their
>         sensitivity/vulnerability:
>
>         Access to the content of the eoPowerStateTable, eoEnergyTable, and
>         eoACPwrAttributesTable MIB tables can reveal sensitive
>         information about individuals' activities and habits
>
> Sounds good to me.
>
>
>     Since this document is essentially a MIB module, your last
>     sentence is covered by
>
>              implementations
>              claiming compliance to the SNMPv3 standard MUST include full
>              support for authentication and privacy via the User-based
>              Security Model (USM) [RFC3414  <http://tools.ietf.org/html/rfc3414>] with the AES cipher algorithm
>              [RFC3826  <http://tools.ietf.org/html/rfc3826>].
>
> RFC 6988 notes the need for privacy protections for stored data, which 
> the above text does not speak to, so I still think a reference to RFC 
> 6988 would add value here.
>
> It is a little disconcerting that use of SNMPv3 is provided as a 
> SHOULD-level requirement without discussion of deployment scenarios 
> and regardless of the sensitivity of the data being made available by 
> any new MIB. For example, the tradeoffs between security and utility 
> might be reasonable if (1) I'm using an older SNMP version on my 
> closed home network to monitor my own energy use, but not if (2) my 
> ISP is using it to monitor the same thing. The text quoted above 
> basically  endorses unauthorized energy monitoring if the provider 
> does not support SNMPv3, whereas it seems like what we would want to 
> be saying is that in cases like (2) SNMPv3 is required.
>
> I understand that this is basically boilerplate language for MIB docs, 
> so I'm not sure what can be done, but it seems unfortunate.
>
> Alissa
>
>
>
>>     ----------------------------------------------------------------------
>>     COMMENT:
>>     ----------------------------------------------------------------------
>>
>>     Section 12.1:
>>     "New Assignments (and potential deprecation) to Power State Sets
>>              shall be administered by IANA and the guidelines and procedures
>>              are specified in [EMAN-FMWK], and will, as a consequence, the
>>              IANAPowerStateSet Textual Convention should be updated."
>>              
>>     Not sure what this sentence means.
>     Good catch.
>     NEW:
>
>              "New Assignments (and potential deprecation) to Power State Sets
>              shall be administered by IANA and the guidelines and procedures
>              are specified in [EMAN-FMWK], and will, as a consequence, update the
>              IANAPowerStateSet Textual Convention."
>
>
>     Regards, Benoit (as a document author)
>
>
>
>
>
> _______________________________________________
> MIB-DOCTORS mailing list
> MIB-DOCTORS@ietf.org
> https://www.ietf.org/mailman/listinfo/mib-doctors


--------------070206080601090700060500
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>
      Let me focus the discussion a little bit.<br>
      Alissa refers to this sentence in the boilerplate at <span
        id="OLK_SRC_BODY_SECTION"><a moz-do-not-send="true"
          class="moz-txt-link-freetext"
          href="http://trac.tools.ietf.org/area/ops/trac/wiki/mib-security">http://trac.tools.ietf.org/area/ops/trac/wiki/mib-security</a></span><br>
      <blockquote>
        <pre class="wiki">   Implementations SHOULD provide the security features described by the   
   SNMPv3 framework (see [RFC3410]), and implementations claiming compliance 
   to the SNMPv3 standard MUST include full support for authentication and 
   privacy via the User-based Security Model (USM) [RFC3414] with the AES 
   cipher algorithm [RFC3826]. </pre>
      </blockquote>
      <br>
      <div>Alissa's feedback is: <br>
        <blockquote>It is a little disconcerting that use of SNMPv3 is
          provided as a SHOULD-level requirement without discussion of
          deployment scenarios and regardless of the sensitivity of the
          data being made available by any new MIB. For example, the
          tradeoffs between security and utility might be reasonable if
          (1) I&#8217;m using an older SNMP version on my closed home network
          to monitor my own energy use, but not if (2) my ISP is using
          it to monitor the same thing. The text quoted above basically
          &nbsp;endorses unauthorized energy monitoring if the provider does
          not support SNMPv3, whereas it seems like what we would want
          to be saying is that in cases like (2) SNMPv3 is required.</blockquote>
      </div>
      <div>Can one of the old timers (who was part of the discussion)
        explain the SHOULD rational? Personally, I can see two use cases
        in favor off the SHOULD: an older SNMP version in a closed
        network,&nbsp; or a private data communication network dedicated to
        network management with special protection out of SNMP (like
        encrypted tunnel)<br>
        <br>
        Should we now modify this sentence to say?<br>
        <pre class="wiki">   MUST provide the security features described by the   
   SNMPv3 framework (see [RFC3410])</pre>
        Regards, Benoit<br>
      </div>
      <br>
    </div>
    <blockquote cite="mid:53BC5081.6090809@cisco.com" type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=ISO-8859-1">
      MIB doctors, <br>
      <br>
      It seems that the "<span id="OLK_SRC_BODY_SECTION">Security
        Guidelines for IETF MIB modules" receives comment for each MIB
        module submitted to the IESG.<br>
        Is it time to modify it, or are we redoing the same discussions
        over and over? <br>
        <br>
        Regards, Benoit<br>
      </span>
      <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>Re: Alissa Cooper's Discuss on
                draft-ietf-eman-energy-monitoring-mib-12: (with DISCUSS
                and COMMENT)</td>
            </tr>
            <tr>
              <th align="RIGHT" nowrap="nowrap" valign="BASELINE">Date:
              </th>
              <td>Tue, 8 Jul 2014 13:02:50 -0700</td>
            </tr>
            <tr>
              <th align="RIGHT" nowrap="nowrap" valign="BASELINE">From:
              </th>
              <td>Alissa Cooper <a moz-do-not-send="true"
                  class="moz-txt-link-rfc2396E"
                  href="mailto:alissa@cooperw.in">&lt;alissa@cooperw.in&gt;</a></td>
            </tr>
            <tr>
              <th align="RIGHT" nowrap="nowrap" valign="BASELINE">To: </th>
              <td>Benoit Claise <a moz-do-not-send="true"
                  class="moz-txt-link-rfc2396E"
                  href="mailto:bclaise@cisco.com">&lt;bclaise@cisco.com&gt;</a>,
                The IESG <a moz-do-not-send="true"
                  class="moz-txt-link-rfc2396E"
                  href="mailto:iesg@ietf.org">&lt;iesg@ietf.org&gt;</a></td>
            </tr>
            <tr>
              <th align="RIGHT" nowrap="nowrap" valign="BASELINE">CC: </th>
              <td><a moz-do-not-send="true"
                  class="moz-txt-link-rfc2396E"
                  href="mailto:draft-ietf-eman-energy-monitoring-mib@tools.ietf.org">&lt;draft-ietf-eman-energy-monitoring-mib@tools.ietf.org&gt;</a>,
                <a moz-do-not-send="true" class="moz-txt-link-rfc2396E"
                  href="mailto:eman-chairs@tools.ietf.org">&lt;eman-chairs@tools.ietf.org&gt;</a></td>
            </tr>
          </tbody>
        </table>
        <br>
        <br>
        <div>Hi Benoit,</div>
        <div><br>
        </div>
        <span id="OLK_SRC_BODY_SECTION">
          <div>
            <div>On 7/8/14, 1:44 AM, "Benoit Claise" &lt;<a
                moz-do-not-send="true" href="mailto:bclaise@cisco.com">bclaise@cisco.com</a>&gt;

              wrote:</div>
          </div>
          <div><br>
          </div>
          <blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE"
            style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5;
            MARGIN:0 0 0 5;">
            <div>
              <div bgcolor="#FFFFFF" text="#000000">
                <div class="moz-cite-prefix">Hi Alissa,<br>
                  <br>
                  Thanks for your review.<br>
                </div>
                <blockquote
                  cite="mid:20140708042418.2373.4207.idtracker@ietfa.amsl.com"
                  type="cite">
                  <pre wrap="">Alissa Cooper has entered the following ballot position for
draft-ietf-eman-energy-monitoring-mib-12: Discuss

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to <a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://www.ietf.org/iesg/statement/discuss-criteria.html">http://www.ietf.org/iesg/statement/discuss-criteria.html</a>
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://datatracker.ietf.org/doc/draft-ietf-eman-energy-monitoring-mib/">http://datatracker.ietf.org/doc/draft-ietf-eman-energy-monitoring-mib/</a>



----------------------------------------------------------------------
DISCUSS:
----------------------------------------------------------------------

Section 11 is missing a discussion of the privacy considerations of
energy and power monitoring. I would suggest something along the lines of
the following:

"In certain situations, energy and power monitoring can reveal sensitive
information about individuals' activities and habits. Implementors of
this specification should use appropriate privacy protections as
discussed in Section 9 of RFC 6988 and monitoring of individuals and
homes should only occur with proper authorization."</pre>
                </blockquote>
                <br>
                Regarding your first sentence, I propose the following
                text, which would be in line with Security Guidelines
                for IETF MIB modules at <a moz-do-not-send="true"
                  class="moz-txt-link-freetext"
                  href="http://trac.tools.ietf.org/area/ops/trac/wiki/mib-security">http://trac.tools.ietf.org/area/ops/trac/wiki/mib-security</a>
                <pre class="wiki">   Some of the readable objects in this MIB module (i.e., objects with a
   MAX-ACCESS other than not-accessible) may be considered sensitive or
   vulnerable in some network environments.  It is thus important to
   control even GET and/or NOTIFY access to these objects and possibly
   to even encrypt the values of these objects when sending them over
   the network via SNMP.  These are the tables and objects and their
   sensitivity/vulnerability:

   Access to the content of the eoPowerStateTable, eoEnergyTable, and 
   eoACPwrAttributesTable MIB tables can reveal sensitive
   information about individuals' activities and habits
</pre>
              </div>
            </div>
          </blockquote>
        </span>
        <div>Sounds good to me.</div>
        <div><br>
        </div>
        <span id="OLK_SRC_BODY_SECTION">
          <blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE"
            style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5;
            MARGIN:0 0 0 5;">
            <div>
              <div bgcolor="#FFFFFF" text="#000000"><br>
                Since this document is essentially a MIB module, your
                last sentence is covered by <br>
                <pre class="newpage">        implementations
        claiming compliance to the SNMPv3 standard MUST include full
        support for authentication and privacy via the User-based
        Security Model (USM) [<a moz-do-not-send="true" href="http://tools.ietf.org/html/rfc3414" title="U. and B. Wijnen">RFC3414</a>] with the AES cipher algorithm
        [<a moz-do-not-send="true" href="http://tools.ietf.org/html/rfc3826" title="&quot;The Advanced Encryption Standard (AES) Cipher Algorithm in the SNMP User-based Security Model&quot;">RFC3826</a>].</pre>
              </div>
            </div>
          </blockquote>
        </span>
        <div>RFC 6988 notes the need for privacy protections for stored
          data, which the above text does not speak to, so I still think
          a reference to RFC 6988 would add value here.</div>
        <div><br>
        </div>
        <div>It is a little disconcerting that use of SNMPv3 is provided
          as a SHOULD-level requirement without discussion of deployment
          scenarios and regardless of the sensitivity of the data being
          made available by any new MIB. For example, the tradeoffs
          between security and utility might be reasonable if (1) I&#8217;m
          using an older SNMP version on my closed home network to
          monitor my own energy use, but not if (2) my ISP is using it
          to monitor the same thing. The text quoted above basically
          &nbsp;endorses unauthorized energy monitoring if the provider does
          not support SNMPv3, whereas it seems like what we would want
          to be saying is that in cases like (2) SNMPv3 is required.</div>
        <div><br>
        </div>
        <div>I understand that this is basically boilerplate language
          for MIB docs, so I&#8217;m not sure what can be done, but it seems
          unfortunate.</div>
        <div><br>
        </div>
        <div>Alissa</div>
        <div><br>
        </div>
        <span id="OLK_SRC_BODY_SECTION">
          <blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE"
            style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5;
            MARGIN:0 0 0 5;">
            <div>
              <div bgcolor="#FFFFFF" text="#000000"><br>
                <br>
                <blockquote
                  cite="mid:20140708042418.2373.4207.idtracker@ietfa.amsl.com"
                  type="cite">
                  <pre wrap="">----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Section 12.1:
"New Assignments (and potential deprecation) to Power State Sets 
        shall be administered by IANA and the guidelines and procedures 
        are specified in [EMAN-FMWK], and will, as a consequence, the 
        IANAPowerStateSet Textual Convention should be updated."
        
Not sure what this sentence means.</pre>
                </blockquote>
                Good catch.<br>
                NEW:<br>
                <pre wrap="">        "New Assignments (and potential deprecation) to Power State Sets 
        shall be administered by IANA and the guidelines and procedures 
        are specified in [EMAN-FMWK], and will, as a consequence, update the 
        IANAPowerStateSet Textual Convention."


Regards, Benoit (as a document author)
</pre>
              </div>
            </div>
          </blockquote>
        </span> <br>
      </div>
      <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>

--------------070206080601090700060500--


From nobody Thu Jul 10 00:15:18 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 057611A0361 for <mib-doctors@ietfa.amsl.com>; Thu, 10 Jul 2014 00:15:17 -0700 (PDT)
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 wl5SQMKh4fT5 for <mib-doctors@ietfa.amsl.com>; Thu, 10 Jul 2014 00:15:14 -0700 (PDT)
Received: from koko.ripe.net (koko.ripe.net [IPv6:2001:67c:2e8:11::c100:1348]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B54521A035C for <mib-doctors@ietf.org>; Thu, 10 Jul 2014 00:15:14 -0700 (PDT)
Received: from titi.ripe.net ([193.0.23.11]) by koko.ripe.net with esmtps (UNKNOWN:AES256-GCM-SHA384:256) (Exim 4.72) (envelope-from <bertietf@bwijnen.net>) id 1X58ZR-0004Lz-NF; Thu, 10 Jul 2014 09:15:11 +0200
Received: from kitten.ripe.net ([2001:67c:2e8:1::c100:1f0] helo=guest9.guestnet.ripe.net) by titi.ripe.net with esmtp (Exim 4.72) (envelope-from <bertietf@bwijnen.net>) id 1X58ZR-0000E2-Jr; Thu, 10 Jul 2014 09:15:09 +0200
Message-ID: <53BE3D7E.2090302@bwijnen.net>
Date: Thu, 10 Jul 2014 09:15:10 +0200
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.6.0
MIME-Version: 1.0
To: Benoit Claise <bclaise@cisco.com>,  "MIB Doctors (E-mail)" <mib-doctors@ietf.org>
References: <CFE17DDA.458C3%alissa@cooperw.in> <53BC5081.6090809@cisco.com> <53BD6690.2040102@cisco.com>
In-Reply-To: <53BD6690.2040102@cisco.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
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: 86ab03e524994f79ca2c75a176445dd491822f6a10e92c9e019eb3e161d67587
Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/07e-rzh24lJtZoDtAEUDeKXgeLU
Cc: Adrian Farrel <adrian@olddog.co.uk>, 'Alissa Cooper' <alissa@cooperw.in>
Subject: Re: [MIB-DOCTORS] Change the boilerplate
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, 10 Jul 2014 07:15:17 -0000

it is always interesting to see that when we get new ADs that we must rediscuss this whole topic.

But yes, there are/were implementations/deployments where one uses dedicated (secure) networks
for the network management systems, and so that would work under a SHOULD.

I do not recall if that was/is the only reason why we agreed on a SHOULD instead of MUST.

Bert

On 09/07/14 17:58, Benoit Claise wrote:
> MIB doctors,
>
> Let me focus the discussion a little bit.
> Alissa refers to this sentence in the boilerplate at http://trac.tools.ietf.org/area/ops/trac/wiki/mib-security
>
>         Implementations SHOULD provide the security features described by the
>         SNMPv3 framework (see [RFC3410]), and implementations claiming compliance
>         to the SNMPv3 standard MUST include full support for authentication and
>         privacy via the User-based Security Model (USM) [RFC3414] with the AES
>         cipher algorithm [RFC3826].
>
>
> Alissa's feedback is:
>
>     It is a little disconcerting that use of SNMPv3 is provided as a SHOULD-level requirement without discussion of deployment
>     scenarios and regardless of the sensitivity of the data being made available by any new MIB. For example, the tradeoffs between
>     security and utility might be reasonable if (1) I’m using an older SNMP version on my closed home network to monitor my own
>     energy use, but not if (2) my ISP is using it to monitor the same thing. The text quoted above basically  endorses unauthorized
>     energy monitoring if the provider does not support SNMPv3, whereas it seems like what we would want to be saying is that in
>     cases like (2) SNMPv3 is required.
>
> Can one of the old timers (who was part of the discussion) explain the SHOULD rational? Personally, I can see two use cases in favor
> off the SHOULD: an older SNMP version in a closed network,  or a private data communication network dedicated to network management
> with special protection out of SNMP (like encrypted tunnel)
>
> Should we now modify this sentence to say?
>
>     MUST provide the security features described by the
>     SNMPv3 framework (see [RFC3410])
>
> Regards, Benoit
>
>> MIB doctors,
>>
>> It seems that the "Security Guidelines for IETF MIB modules" receives comment for each MIB module submitted to the IESG.
>> Is it time to modify it, or are we redoing the same discussions over and over?
>>
>> Regards, Benoit
>>
>>
>> -------- Original Message --------
>> Subject: 	Re: Alissa Cooper's Discuss on draft-ietf-eman-energy-monitoring-mib-12: (with DISCUSS and COMMENT)
>> Date: 	Tue, 8 Jul 2014 13:02:50 -0700
>> From: 	Alissa Cooper <alissa@cooperw.in>
>> To: 	Benoit Claise <bclaise@cisco.com>, The IESG <iesg@ietf.org>
>> CC: 	<draft-ietf-eman-energy-monitoring-mib@tools.ietf.org>, <eman-chairs@tools.ietf.org>
>>
>>
>>
>> Hi Benoit,
>>
>> On 7/8/14, 1:44 AM, "Benoit Claise" <bclaise@cisco.com <mailto:bclaise@cisco.com>> wrote:
>>
>>     Hi Alissa,
>>
>>     Thanks for your review.
>>>     Alissa Cooper has entered the following ballot position for
>>>     draft-ietf-eman-energy-monitoring-mib-12: Discuss
>>>
>>>     When responding, please keep the subject line intact and reply to all
>>>     email addresses included in the To and CC lines. (Feel free to cut this
>>>     introductory paragraph, however.)
>>>
>>>
>>>     Please refer tohttp://www.ietf.org/iesg/statement/discuss-criteria.html
>>>     for more information about IESG DISCUSS and COMMENT positions.
>>>
>>>
>>>     The document, along with other ballot positions, can be found here:
>>>     http://datatracker.ietf.org/doc/draft-ietf-eman-energy-monitoring-mib/
>>>
>>>
>>>
>>>     ----------------------------------------------------------------------
>>>     DISCUSS:
>>>     ----------------------------------------------------------------------
>>>
>>>     Section 11 is missing a discussion of the privacy considerations of
>>>     energy and power monitoring. I would suggest something along the lines of
>>>     the following:
>>>
>>>     "In certain situations, energy and power monitoring can reveal sensitive
>>>     information about individuals' activities and habits. Implementors of
>>>     this specification should use appropriate privacy protections as
>>>     discussed in Section 9 of RFC 6988 and monitoring of individuals and
>>>     homes should only occur with proper authorization."
>>
>>     Regarding your first sentence, I propose the following text, which would be in line with Security Guidelines for IETF MIB
>>     modules at http://trac.tools.ietf.org/area/ops/trac/wiki/mib-security
>>
>>         Some of the readable objects in this MIB module (i.e., objects with a
>>         MAX-ACCESS other than not-accessible) may be considered sensitive or
>>         vulnerable in some network environments.  It is thus important to
>>         control even GET and/or NOTIFY access to these objects and possibly
>>         to even encrypt the values of these objects when sending them over
>>         the network via SNMP.  These are the tables and objects and their
>>         sensitivity/vulnerability:
>>
>>         Access to the content of the eoPowerStateTable, eoEnergyTable, and
>>         eoACPwrAttributesTable MIB tables can reveal sensitive
>>         information about individuals' activities and habits
>>
>> Sounds good to me.
>>
>>
>>     Since this document is essentially a MIB module, your last sentence is covered by
>>
>>              implementations
>>              claiming compliance to the SNMPv3 standard MUST include full
>>              support for authentication and privacy via the User-based
>>              Security Model (USM) [RFC3414  <http://tools.ietf.org/html/rfc3414>] with the AES cipher algorithm
>>              [RFC3826  <http://tools.ietf.org/html/rfc3826>].
>>
>> RFC 6988 notes the need for privacy protections for stored data, which the above text does not speak to, so I still think a
>> reference to RFC 6988 would add value here.
>>
>> It is a little disconcerting that use of SNMPv3 is provided as a SHOULD-level requirement without discussion of deployment
>> scenarios and regardless of the sensitivity of the data being made available by any new MIB. For example, the tradeoffs between
>> security and utility might be reasonable if (1) I’m using an older SNMP version on my closed home network to monitor my own energy
>> use, but not if (2) my ISP is using it to monitor the same thing. The text quoted above basically  endorses unauthorized energy
>> monitoring if the provider does not support SNMPv3, whereas it seems like what we would want to be saying is that in cases like
>> (2) SNMPv3 is required.
>>
>> I understand that this is basically boilerplate language for MIB docs, so I’m not sure what can be done, but it seems unfortunate.
>>
>> Alissa
>>
>>
>>
>>>     ----------------------------------------------------------------------
>>>     COMMENT:
>>>     ----------------------------------------------------------------------
>>>
>>>     Section 12.1:
>>>     "New Assignments (and potential deprecation) to Power State Sets
>>>              shall be administered by IANA and the guidelines and procedures
>>>              are specified in [EMAN-FMWK], and will, as a consequence, the
>>>              IANAPowerStateSet Textual Convention should be updated."
>>>
>>>     Not sure what this sentence means.
>>     Good catch.
>>     NEW:
>>
>>              "New Assignments (and potential deprecation) to Power State Sets
>>              shall be administered by IANA and the guidelines and procedures
>>              are specified in [EMAN-FMWK], and will, as a consequence, update the
>>              IANAPowerStateSet Textual Convention."
>>
>>
>>     Regards, Benoit (as a document author)
>>
>>
>>
>>
>>
>> _______________________________________________
>> 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 Thu Jul 10 00:26:23 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 F268E1A02E7 for <mib-doctors@ietfa.amsl.com>; Thu, 10 Jul 2014 00:26:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.152
X-Spam-Level: 
X-Spam-Status: No, score=-15.152 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] 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 DH5xvXcE_w5N for <mib-doctors@ietfa.amsl.com>; Thu, 10 Jul 2014 00:26:20 -0700 (PDT)
Received: from aer-iport-3.cisco.com (aer-iport-3.cisco.com [173.38.203.53]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6AD9D1A0114 for <mib-doctors@ietf.org>; Thu, 10 Jul 2014 00:26:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=9160; q=dns/txt; s=iport; t=1404977187; x=1406186787; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=epW7l0vvv6rZas7MjzlNU7bXNT9pVavdo3JnLlHQbL4=; b=D65pRyf9PqPVLiD+iFrBCvKvy9Lh2APvTez3Zw0MnJWIPkMDQtfT0aPe YO7BOn8ocShX60t7AWgwt/5ZACiB9rVYdtTb7rVBLdAWD2rikyV0tGjiT K93mLJFE5d/HGcxRlFaPuyz9PbxwV88Cqy8ereMWYEGXpaB5Wq99XMk1B s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjkJAKU/vlOtJssW/2dsb2JhbABZg2C/dwoJhzYBgR11hAMBAQEDAQEBAS8BBTYKAQUHBAsRAwECAQkWCAcJAwIBAgEVHwkIBgEMAQUCAQEFiDEIDcdWF45aBhEBAiwiBwaEPQEEmniBSIVHjH+DRTsvgQs
X-IronPort-AV: E=Sophos;i="5.01,636,1400025600"; d="scan'208";a="103017424"
Received: from aer-iport-nat.cisco.com (HELO aer-core-4.cisco.com) ([173.38.203.22]) by aer-iport-3.cisco.com with ESMTP; 10 Jul 2014 07:26:24 +0000
Received: from [10.60.67.84] (ams-bclaise-8913.cisco.com [10.60.67.84]) by aer-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id s6A7QGsV007823; Thu, 10 Jul 2014 07:26:17 GMT
Message-ID: <53BE4018.8030402@cisco.com>
Date: Thu, 10 Jul 2014 09:26:16 +0200
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: "Bert Wijnen (IETF)" <bertietf@bwijnen.net>, "MIB Doctors (E-mail)" <mib-doctors@ietf.org>
References: <CFE17DDA.458C3%alissa@cooperw.in> <53BC5081.6090809@cisco.com> <53BD6690.2040102@cisco.com> <53BE3D7E.2090302@bwijnen.net>
In-Reply-To: <53BE3D7E.2090302@bwijnen.net>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/ivf3sSx9E2mL4xgy8omgX6sTtD4
Cc: Adrian Farrel <adrian@olddog.co.uk>, 'Alissa Cooper' <alissa@cooperw.in>, sec-ads@tools.ietf.org
Subject: Re: [MIB-DOCTORS] Change the boilerplate
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, 10 Jul 2014 07:26:22 -0000

> it is always interesting to see that when we get new ADs that we must 
> rediscuss this whole topic.
Wait, there is more, two DISCUSSes from Kathleen regarding the 
boilerplate (copied the Security ADs):
http://datatracker.ietf.org/doc/draft-ietf-eman-battery-mib/ballot/#kathleen-moriarty
http://datatracker.ietf.org/doc/draft-ietf-eman-energy-aware-mib/ballot/#kathleen-moriarty

I would like to hear first from you guys before providing my opinion.

Regards, Benoit
>
> But yes, there are/were implementations/deployments where one uses 
> dedicated (secure) networks
> for the network management systems, and so that would work under a 
> SHOULD.
>
> I do not recall if that was/is the only reason why we agreed on a 
> SHOULD instead of MUST.
>
> Bert
>
> On 09/07/14 17:58, Benoit Claise wrote:
>> MIB doctors,
>>
>> Let me focus the discussion a little bit.
>> Alissa refers to this sentence in the boilerplate at 
>> http://trac.tools.ietf.org/area/ops/trac/wiki/mib-security
>>
>>         Implementations SHOULD provide the security features 
>> described by the
>>         SNMPv3 framework (see [RFC3410]), and implementations 
>> claiming compliance
>>         to the SNMPv3 standard MUST include full support for 
>> authentication and
>>         privacy via the User-based Security Model (USM) [RFC3414] 
>> with the AES
>>         cipher algorithm [RFC3826].
>>
>>
>> Alissa's feedback is:
>>
>>     It is a little disconcerting that use of SNMPv3 is provided as a 
>> SHOULD-level requirement without discussion of deployment
>>     scenarios and regardless of the sensitivity of the data being 
>> made available by any new MIB. For example, the tradeoffs between
>>     security and utility might be reasonable if (1) I’m using an 
>> older SNMP version on my closed home network to monitor my own
>>     energy use, but not if (2) my ISP is using it to monitor the same 
>> thing. The text quoted above basically  endorses unauthorized
>>     energy monitoring if the provider does not support SNMPv3, 
>> whereas it seems like what we would want to be saying is that in
>>     cases like (2) SNMPv3 is required.
>>
>> Can one of the old timers (who was part of the discussion) explain 
>> the SHOULD rational? Personally, I can see two use cases in favor
>> off the SHOULD: an older SNMP version in a closed network,  or a 
>> private data communication network dedicated to network management
>> with special protection out of SNMP (like encrypted tunnel)
>>
>> Should we now modify this sentence to say?
>>
>>     MUST provide the security features described by the
>>     SNMPv3 framework (see [RFC3410])
>>
>> Regards, Benoit
>>
>>> MIB doctors,
>>>
>>> It seems that the "Security Guidelines for IETF MIB modules" 
>>> receives comment for each MIB module submitted to the IESG.
>>> Is it time to modify it, or are we redoing the same discussions over 
>>> and over?
>>>
>>> Regards, Benoit
>>>
>>>
>>> -------- Original Message --------
>>> Subject:     Re: Alissa Cooper's Discuss on 
>>> draft-ietf-eman-energy-monitoring-mib-12: (with DISCUSS and COMMENT)
>>> Date:     Tue, 8 Jul 2014 13:02:50 -0700
>>> From:     Alissa Cooper <alissa@cooperw.in>
>>> To:     Benoit Claise <bclaise@cisco.com>, The IESG <iesg@ietf.org>
>>> CC: <draft-ietf-eman-energy-monitoring-mib@tools.ietf.org>, 
>>> <eman-chairs@tools.ietf.org>
>>>
>>>
>>>
>>> Hi Benoit,
>>>
>>> On 7/8/14, 1:44 AM, "Benoit Claise" <bclaise@cisco.com 
>>> <mailto:bclaise@cisco.com>> wrote:
>>>
>>>     Hi Alissa,
>>>
>>>     Thanks for your review.
>>>>     Alissa Cooper has entered the following ballot position for
>>>>     draft-ietf-eman-energy-monitoring-mib-12: Discuss
>>>>
>>>>     When responding, please keep the subject line intact and reply 
>>>> to all
>>>>     email addresses included in the To and CC lines. (Feel free to 
>>>> cut this
>>>>     introductory paragraph, however.)
>>>>
>>>>
>>>>     Please refer 
>>>> tohttp://www.ietf.org/iesg/statement/discuss-criteria.html
>>>>     for more information about IESG DISCUSS and COMMENT positions.
>>>>
>>>>
>>>>     The document, along with other ballot positions, can be found 
>>>> here:
>>>> http://datatracker.ietf.org/doc/draft-ietf-eman-energy-monitoring-mib/
>>>>
>>>>
>>>>
>>>> ----------------------------------------------------------------------
>>>>     DISCUSS:
>>>> ----------------------------------------------------------------------
>>>>
>>>>     Section 11 is missing a discussion of the privacy 
>>>> considerations of
>>>>     energy and power monitoring. I would suggest something along 
>>>> the lines of
>>>>     the following:
>>>>
>>>>     "In certain situations, energy and power monitoring can reveal 
>>>> sensitive
>>>>     information about individuals' activities and habits. 
>>>> Implementors of
>>>>     this specification should use appropriate privacy protections as
>>>>     discussed in Section 9 of RFC 6988 and monitoring of 
>>>> individuals and
>>>>     homes should only occur with proper authorization."
>>>
>>>     Regarding your first sentence, I propose the following text, 
>>> which would be in line with Security Guidelines for IETF MIB
>>>     modules at 
>>> http://trac.tools.ietf.org/area/ops/trac/wiki/mib-security
>>>
>>>         Some of the readable objects in this MIB module (i.e., 
>>> objects with a
>>>         MAX-ACCESS other than not-accessible) may be considered 
>>> sensitive or
>>>         vulnerable in some network environments.  It is thus 
>>> important to
>>>         control even GET and/or NOTIFY access to these objects and 
>>> possibly
>>>         to even encrypt the values of these objects when sending 
>>> them over
>>>         the network via SNMP.  These are the tables and objects and 
>>> their
>>>         sensitivity/vulnerability:
>>>
>>>         Access to the content of the eoPowerStateTable, 
>>> eoEnergyTable, and
>>>         eoACPwrAttributesTable MIB tables can reveal sensitive
>>>         information about individuals' activities and habits
>>>
>>> Sounds good to me.
>>>
>>>
>>>     Since this document is essentially a MIB module, your last 
>>> sentence is covered by
>>>
>>>              implementations
>>>              claiming compliance to the SNMPv3 standard MUST include 
>>> full
>>>              support for authentication and privacy via the User-based
>>>              Security Model (USM) [RFC3414 
>>> <http://tools.ietf.org/html/rfc3414>] with the AES cipher algorithm
>>>              [RFC3826 <http://tools.ietf.org/html/rfc3826>].
>>>
>>> RFC 6988 notes the need for privacy protections for stored data, 
>>> which the above text does not speak to, so I still think a
>>> reference to RFC 6988 would add value here.
>>>
>>> It is a little disconcerting that use of SNMPv3 is provided as a 
>>> SHOULD-level requirement without discussion of deployment
>>> scenarios and regardless of the sensitivity of the data being made 
>>> available by any new MIB. For example, the tradeoffs between
>>> security and utility might be reasonable if (1) I’m using an older 
>>> SNMP version on my closed home network to monitor my own energy
>>> use, but not if (2) my ISP is using it to monitor the same thing. 
>>> The text quoted above basically  endorses unauthorized energy
>>> monitoring if the provider does not support SNMPv3, whereas it seems 
>>> like what we would want to be saying is that in cases like
>>> (2) SNMPv3 is required.
>>>
>>> I understand that this is basically boilerplate language for MIB 
>>> docs, so I’m not sure what can be done, but it seems unfortunate.
>>>
>>> Alissa
>>>
>>>
>>>
>>>> ----------------------------------------------------------------------
>>>>     COMMENT:
>>>> ----------------------------------------------------------------------
>>>>
>>>>     Section 12.1:
>>>>     "New Assignments (and potential deprecation) to Power State Sets
>>>>              shall be administered by IANA and the guidelines and 
>>>> procedures
>>>>              are specified in [EMAN-FMWK], and will, as a 
>>>> consequence, the
>>>>              IANAPowerStateSet Textual Convention should be updated."
>>>>
>>>>     Not sure what this sentence means.
>>>     Good catch.
>>>     NEW:
>>>
>>>              "New Assignments (and potential deprecation) to Power 
>>> State Sets
>>>              shall be administered by IANA and the guidelines and 
>>> procedures
>>>              are specified in [EMAN-FMWK], and will, as a 
>>> consequence, update the
>>>              IANAPowerStateSet Textual Convention."
>>>
>>>
>>>     Regards, Benoit (as a document author)
>>>
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> 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 Thu Jul 10 01:01:02 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 E7EB21A0397 for <mib-doctors@ietfa.amsl.com>; Thu, 10 Jul 2014 01:00:59 -0700 (PDT)
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 hNStQ3dGMwwG for <mib-doctors@ietfa.amsl.com>; Thu, 10 Jul 2014 01:00:57 -0700 (PDT)
Received: from koko.ripe.net (koko.ripe.net [IPv6:2001:67c:2e8:11::c100:1348]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 31F871A0371 for <mib-doctors@ietf.org>; Thu, 10 Jul 2014 01:00:57 -0700 (PDT)
Received: from titi.ripe.net ([193.0.23.11]) by koko.ripe.net with esmtps (UNKNOWN:AES256-GCM-SHA384:256) (Exim 4.72) (envelope-from <bertietf@bwijnen.net>) id 1X59He-00015D-VT; Thu, 10 Jul 2014 10:00:53 +0200
Received: from kitten.ripe.net ([2001:67c:2e8:1::c100:1f0] helo=guest9.guestnet.ripe.net) by titi.ripe.net with esmtp (Exim 4.72) (envelope-from <bertietf@bwijnen.net>) id 1X59He-0005QI-Rl; Thu, 10 Jul 2014 10:00:50 +0200
Message-ID: <53BE4833.3060506@bwijnen.net>
Date: Thu, 10 Jul 2014 10:00:51 +0200
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.6.0
MIME-Version: 1.0
To: Benoit Claise <bclaise@cisco.com>,  "MIB Doctors (E-mail)" <mib-doctors@ietf.org>
References: <CFE17DDA.458C3%alissa@cooperw.in> <53BC5081.6090809@cisco.com> <53BD6690.2040102@cisco.com> <53BE3D7E.2090302@bwijnen.net> <53BE4018.8030402@cisco.com>
In-Reply-To: <53BE4018.8030402@cisco.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
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: 86ab03e524994f79ca2c75a176445dd42e7306b09fc88f6d3c14c7cfa5d77177
Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/o87r4ejSAukrgB4ahzhUVeE-abg
Cc: Adrian Farrel <adrian@olddog.co.uk>, 'Alissa Cooper' <alissa@cooperw.in>, sec-ads@tools.ietf.org
Subject: Re: [MIB-DOCTORS] Change the boilerplate
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, 10 Jul 2014 08:01:00 -0000

I can see that for IoT related MIB modules there might be specific privacy concerns that
you might want to describe in a special section. Not sure this should become a standard
section in all MIB related documents though.

My 2 cents.

Bert

On 10/07/14 09:26, Benoit Claise wrote:
>
>> it is always interesting to see that when we get new ADs that we must rediscuss this whole topic.
> Wait, there is more, two DISCUSSes from Kathleen regarding the boilerplate (copied the Security ADs):
> http://datatracker.ietf.org/doc/draft-ietf-eman-battery-mib/ballot/#kathleen-moriarty
> http://datatracker.ietf.org/doc/draft-ietf-eman-energy-aware-mib/ballot/#kathleen-moriarty
>
> I would like to hear first from you guys before providing my opinion.
>
> Regards, Benoit
>>
>> But yes, there are/were implementations/deployments where one uses dedicated (secure) networks
>> for the network management systems, and so that would work under a SHOULD.
>>
>> I do not recall if that was/is the only reason why we agreed on a SHOULD instead of MUST.
>>
>> Bert
>>
>> On 09/07/14 17:58, Benoit Claise wrote:
>>> MIB doctors,
>>>
>>> Let me focus the discussion a little bit.
>>> Alissa refers to this sentence in the boilerplate at http://trac.tools.ietf.org/area/ops/trac/wiki/mib-security
>>>
>>>         Implementations SHOULD provide the security features described by the
>>>         SNMPv3 framework (see [RFC3410]), and implementations claiming compliance
>>>         to the SNMPv3 standard MUST include full support for authentication and
>>>         privacy via the User-based Security Model (USM) [RFC3414] with the AES
>>>         cipher algorithm [RFC3826].
>>>
>>>
>>> Alissa's feedback is:
>>>
>>>     It is a little disconcerting that use of SNMPv3 is provided as a SHOULD-level requirement without discussion of deployment
>>>     scenarios and regardless of the sensitivity of the data being made available by any new MIB. For example, the tradeoffs between
>>>     security and utility might be reasonable if (1) I’m using an older SNMP version on my closed home network to monitor my own
>>>     energy use, but not if (2) my ISP is using it to monitor the same thing. The text quoted above basically  endorses unauthorized
>>>     energy monitoring if the provider does not support SNMPv3, whereas it seems like what we would want to be saying is that in
>>>     cases like (2) SNMPv3 is required.
>>>
>>> Can one of the old timers (who was part of the discussion) explain the SHOULD rational? Personally, I can see two use cases in favor
>>> off the SHOULD: an older SNMP version in a closed network,  or a private data communication network dedicated to network management
>>> with special protection out of SNMP (like encrypted tunnel)
>>>
>>> Should we now modify this sentence to say?
>>>
>>>     MUST provide the security features described by the
>>>     SNMPv3 framework (see [RFC3410])
>>>
>>> Regards, Benoit
>>>
>>>> MIB doctors,
>>>>
>>>> It seems that the "Security Guidelines for IETF MIB modules" receives comment for each MIB module submitted to the IESG.
>>>> Is it time to modify it, or are we redoing the same discussions over and over?
>>>>
>>>> Regards, Benoit
>>>>
>>>>
>>>> -------- Original Message --------
>>>> Subject:     Re: Alissa Cooper's Discuss on draft-ietf-eman-energy-monitoring-mib-12: (with DISCUSS and COMMENT)
>>>> Date:     Tue, 8 Jul 2014 13:02:50 -0700
>>>> From:     Alissa Cooper <alissa@cooperw.in>
>>>> To:     Benoit Claise <bclaise@cisco.com>, The IESG <iesg@ietf.org>
>>>> CC: <draft-ietf-eman-energy-monitoring-mib@tools.ietf.org>, <eman-chairs@tools.ietf.org>
>>>>
>>>>
>>>>
>>>> Hi Benoit,
>>>>
>>>> On 7/8/14, 1:44 AM, "Benoit Claise" <bclaise@cisco.com <mailto:bclaise@cisco.com>> wrote:
>>>>
>>>>     Hi Alissa,
>>>>
>>>>     Thanks for your review.
>>>>>     Alissa Cooper has entered the following ballot position for
>>>>>     draft-ietf-eman-energy-monitoring-mib-12: Discuss
>>>>>
>>>>>     When responding, please keep the subject line intact and reply to all
>>>>>     email addresses included in the To and CC lines. (Feel free to cut this
>>>>>     introductory paragraph, however.)
>>>>>
>>>>>
>>>>>     Please refer tohttp://www.ietf.org/iesg/statement/discuss-criteria.html
>>>>>     for more information about IESG DISCUSS and COMMENT positions.
>>>>>
>>>>>
>>>>>     The document, along with other ballot positions, can be found here:
>>>>> http://datatracker.ietf.org/doc/draft-ietf-eman-energy-monitoring-mib/
>>>>>
>>>>>
>>>>>
>>>>> ----------------------------------------------------------------------
>>>>>     DISCUSS:
>>>>> ----------------------------------------------------------------------
>>>>>
>>>>>     Section 11 is missing a discussion of the privacy considerations of
>>>>>     energy and power monitoring. I would suggest something along the lines of
>>>>>     the following:
>>>>>
>>>>>     "In certain situations, energy and power monitoring can reveal sensitive
>>>>>     information about individuals' activities and habits. Implementors of
>>>>>     this specification should use appropriate privacy protections as
>>>>>     discussed in Section 9 of RFC 6988 and monitoring of individuals and
>>>>>     homes should only occur with proper authorization."
>>>>
>>>>     Regarding your first sentence, I propose the following text, which would be in line with Security Guidelines for IETF MIB
>>>>     modules at http://trac.tools.ietf.org/area/ops/trac/wiki/mib-security
>>>>
>>>>         Some of the readable objects in this MIB module (i.e., objects with a
>>>>         MAX-ACCESS other than not-accessible) may be considered sensitive or
>>>>         vulnerable in some network environments.  It is thus important to
>>>>         control even GET and/or NOTIFY access to these objects and possibly
>>>>         to even encrypt the values of these objects when sending them over
>>>>         the network via SNMP.  These are the tables and objects and their
>>>>         sensitivity/vulnerability:
>>>>
>>>>         Access to the content of the eoPowerStateTable, eoEnergyTable, and
>>>>         eoACPwrAttributesTable MIB tables can reveal sensitive
>>>>         information about individuals' activities and habits
>>>>
>>>> Sounds good to me.
>>>>
>>>>
>>>>     Since this document is essentially a MIB module, your last sentence is covered by
>>>>
>>>>              implementations
>>>>              claiming compliance to the SNMPv3 standard MUST include full
>>>>              support for authentication and privacy via the User-based
>>>>              Security Model (USM) [RFC3414 <http://tools.ietf.org/html/rfc3414>] with the AES cipher algorithm
>>>>              [RFC3826 <http://tools.ietf.org/html/rfc3826>].
>>>>
>>>> RFC 6988 notes the need for privacy protections for stored data, which the above text does not speak to, so I still think a
>>>> reference to RFC 6988 would add value here.
>>>>
>>>> It is a little disconcerting that use of SNMPv3 is provided as a SHOULD-level requirement without discussion of deployment
>>>> scenarios and regardless of the sensitivity of the data being made available by any new MIB. For example, the tradeoffs between
>>>> security and utility might be reasonable if (1) I’m using an older SNMP version on my closed home network to monitor my own energy
>>>> use, but not if (2) my ISP is using it to monitor the same thing. The text quoted above basically  endorses unauthorized energy
>>>> monitoring if the provider does not support SNMPv3, whereas it seems like what we would want to be saying is that in cases like
>>>> (2) SNMPv3 is required.
>>>>
>>>> I understand that this is basically boilerplate language for MIB docs, so I’m not sure what can be done, but it seems unfortunate.
>>>>
>>>> Alissa
>>>>
>>>>
>>>>
>>>>> ----------------------------------------------------------------------
>>>>>     COMMENT:
>>>>> ----------------------------------------------------------------------
>>>>>
>>>>>     Section 12.1:
>>>>>     "New Assignments (and potential deprecation) to Power State Sets
>>>>>              shall be administered by IANA and the guidelines and procedures
>>>>>              are specified in [EMAN-FMWK], and will, as a consequence, the
>>>>>              IANAPowerStateSet Textual Convention should be updated."
>>>>>
>>>>>     Not sure what this sentence means.
>>>>     Good catch.
>>>>     NEW:
>>>>
>>>>              "New Assignments (and potential deprecation) to Power State Sets
>>>>              shall be administered by IANA and the guidelines and procedures
>>>>              are specified in [EMAN-FMWK], and will, as a consequence, update the
>>>>              IANAPowerStateSet Textual Convention."
>>>>
>>>>
>>>>     Regards, Benoit (as a document author)
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> 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 Thu Jul 10 01:03:22 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 73B361A0371 for <mib-doctors@ietfa.amsl.com>; Thu, 10 Jul 2014 01:03:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.551
X-Spam-Level: 
X-Spam-Status: No, score=-7.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.651] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1YICgceSbBMT for <mib-doctors@ietfa.amsl.com>; Thu, 10 Jul 2014 01:03:15 -0700 (PDT)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 095301A0418 for <mib-doctors@ietf.org>; Thu, 10 Jul 2014 01:03:14 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AuUKAEpIvlPGmAcV/2dsb2JhbABZgmokUlqrdwEBAQEBAQaFR407GQgLhzYBgQgWdYQDAQEBAQMBAQEPKDQLDAQCAQgNBAMBAQEBChQJBycLFAkIAgQBDQUIARIHiCABDKNro3MXhXqHDoFYEQECHTEHBoMngRYFhWqQdIVihXCMVoNDbIELOQ
X-IronPort-AV: E=Sophos;i="5.01,636,1400040000"; d="scan'208";a="64265080"
Received: from unknown (HELO co300216-co-erhwest-exch.avaya.com) ([198.152.7.21]) by de307622-de-outbound.net.avaya.com with ESMTP; 10 Jul 2014 04:02:51 -0400
X-OutboundMail_SMTP: 1
Received: from unknown (HELO AZ-FFEXHC03.global.avaya.com) ([135.64.58.13]) by co300216-co-erhwest-out.avaya.com with ESMTP/TLS/AES128-SHA; 10 Jul 2014 04:02:50 -0400
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC03.global.avaya.com ([135.64.58.13]) with mapi id 14.03.0174.001; Thu, 10 Jul 2014 04:02:49 -0400
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Bert Wijnen (IETF)" <bertietf@bwijnen.net>, Benoit Claise <bclaise@cisco.com>, "MIB Doctors (E-mail)" <mib-doctors@ietf.org>
Thread-Topic: [MIB-DOCTORS] Change the boilerplate
Thread-Index: AQHPnA62YNrUuQufrECSM9be/+m6wZuY6Umg
Date: Thu, 10 Jul 2014 08:02:48 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA5C83CC03@AZ-FFEXMB04.global.avaya.com>
References: <CFE17DDA.458C3%alissa@cooperw.in> <53BC5081.6090809@cisco.com> <53BD6690.2040102@cisco.com> <53BE3D7E.2090302@bwijnen.net>
In-Reply-To: <53BE3D7E.2090302@bwijnen.net>
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/BTxL6eyv3jk3dTW2gT68ad6h0c0
Cc: Adrian Farrel <adrian@olddog.co.uk>, 'Alissa Cooper' <alissa@cooperw.in>
Subject: Re: [MIB-DOCTORS] Change the boilerplate
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, 10 Jul 2014 08:03:18 -0000

That is what I remember as well. I inherited the boilerplate text from Bert=
, and during my tenure as AD we had at least one round of text revision (ma=
ybe two?). AFAICT this part did not change for the reasons described by Ber=
t. Another reason may have been that 3410 describes a number of security fe=
atures, each of them may use different cryptographic algorithms, and not al=
l are mandatory to implement (and of course to deploy) in order to obtain a=
 secure solution.

Regards,

Dan


> -----Original Message-----
> From: MIB-DOCTORS [mailto:mib-doctors-bounces@ietf.org] On Behalf Of
> Bert Wijnen (IETF)
> Sent: Thursday, July 10, 2014 10:15 AM
> To: Benoit Claise; MIB Doctors (E-mail)
> Cc: Adrian Farrel; 'Alissa Cooper'
> Subject: Re: [MIB-DOCTORS] Change the boilerplate
>=20
> it is always interesting to see that when we get new ADs that we must
> rediscuss this whole topic.
>=20
> But yes, there are/were implementations/deployments where one uses
> dedicated (secure) networks for the network management systems, and so
> that would work under a SHOULD.
>=20
> I do not recall if that was/is the only reason why we agreed on a SHOULD
> instead of MUST.
>=20
> Bert
>=20
> On 09/07/14 17:58, Benoit Claise wrote:
> > MIB doctors,
> >
> > Let me focus the discussion a little bit.
> > Alissa refers to this sentence in the boilerplate at
> > http://trac.tools.ietf.org/area/ops/trac/wiki/mib-security
> >
> >         Implementations SHOULD provide the security features described =
by
> the
> >         SNMPv3 framework (see [RFC3410]), and implementations claiming
> compliance
> >         to the SNMPv3 standard MUST include full support for authentica=
tion
> and
> >         privacy via the User-based Security Model (USM) [RFC3414] with =
the
> AES
> >         cipher algorithm [RFC3826].
> >
> >
> > Alissa's feedback is:
> >
> >     It is a little disconcerting that use of SNMPv3 is provided as a SH=
OULD-
> level requirement without discussion of deployment
> >     scenarios and regardless of the sensitivity of the data being made
> available by any new MIB. For example, the tradeoffs between
> >     security and utility might be reasonable if (1) I'm using an older =
SNMP
> version on my closed home network to monitor my own
> >     energy use, but not if (2) my ISP is using it to monitor the same t=
hing. The
> text quoted above basically  endorses unauthorized
> >     energy monitoring if the provider does not support SNMPv3, whereas =
it
> seems like what we would want to be saying is that in
> >     cases like (2) SNMPv3 is required.
> >
> > Can one of the old timers (who was part of the discussion) explain the
> > SHOULD rational? Personally, I can see two use cases in favor off the
> > SHOULD: an older SNMP version in a closed network,  or a private data
> > communication network dedicated to network management with special
> > protection out of SNMP (like encrypted tunnel)
> >
> > Should we now modify this sentence to say?
> >
> >     MUST provide the security features described by the
> >     SNMPv3 framework (see [RFC3410])
> >
> > Regards, Benoit
> >
> >> MIB doctors,
> >>
> >> It seems that the "Security Guidelines for IETF MIB modules" receives
> comment for each MIB module submitted to the IESG.
> >> Is it time to modify it, or are we redoing the same discussions over a=
nd
> over?
> >>
> >> Regards, Benoit
> >>
> >>
> >> -------- Original Message --------
> >> Subject: 	Re: Alissa Cooper's Discuss on draft-ietf-eman-energy-
> monitoring-mib-12: (with DISCUSS and COMMENT)
> >> Date: 	Tue, 8 Jul 2014 13:02:50 -0700
> >> From: 	Alissa Cooper <alissa@cooperw.in>
> >> To: 	Benoit Claise <bclaise@cisco.com>, The IESG <iesg@ietf.org>
> >> CC: 	<draft-ietf-eman-energy-monitoring-mib@tools.ietf.org>, <eman-
> chairs@tools.ietf.org>
> >>
> >>
> >>
> >> Hi Benoit,
> >>
> >> On 7/8/14, 1:44 AM, "Benoit Claise" <bclaise@cisco.com
> <mailto:bclaise@cisco.com>> wrote:
> >>
> >>     Hi Alissa,
> >>
> >>     Thanks for your review.
> >>>     Alissa Cooper has entered the following ballot position for
> >>>     draft-ietf-eman-energy-monitoring-mib-12: Discuss
> >>>
> >>>     When responding, please keep the subject line intact and reply to=
 all
> >>>     email addresses included in the To and CC lines. (Feel free to cu=
t this
> >>>     introductory paragraph, however.)
> >>>
> >>>
> >>>     Please refer tohttp://www.ietf.org/iesg/statement/discuss-
> criteria.html
> >>>     for more information about IESG DISCUSS and COMMENT positions.
> >>>
> >>>
> >>>     The document, along with other ballot positions, can be found her=
e:
> >>>
> >>> http://datatracker.ietf.org/doc/draft-ietf-eman-energy-monitoring-mi
> >>> b/
> >>>
> >>>
> >>>
> >>>     -----------------------------------------------------------------=
-----
> >>>     DISCUSS:
> >>>
> >>> --------------------------------------------------------------------
> >>> --
> >>>
> >>>     Section 11 is missing a discussion of the privacy considerations =
of
> >>>     energy and power monitoring. I would suggest something along the
> lines of
> >>>     the following:
> >>>
> >>>     "In certain situations, energy and power monitoring can reveal
> sensitive
> >>>     information about individuals' activities and habits. Implementor=
s of
> >>>     this specification should use appropriate privacy protections as
> >>>     discussed in Section 9 of RFC 6988 and monitoring of individuals =
and
> >>>     homes should only occur with proper authorization."
> >>
> >>     Regarding your first sentence, I propose the following text, which=
 would
> be in line with Security Guidelines for IETF MIB
> >>     modules at
> >> http://trac.tools.ietf.org/area/ops/trac/wiki/mib-security
> >>
> >>         Some of the readable objects in this MIB module (i.e., objects=
 with a
> >>         MAX-ACCESS other than not-accessible) may be considered sensit=
ive
> or
> >>         vulnerable in some network environments.  It is thus important=
 to
> >>         control even GET and/or NOTIFY access to these objects and pos=
sibly
> >>         to even encrypt the values of these objects when sending them =
over
> >>         the network via SNMP.  These are the tables and objects and th=
eir
> >>         sensitivity/vulnerability:
> >>
> >>         Access to the content of the eoPowerStateTable, eoEnergyTable,=
 and
> >>         eoACPwrAttributesTable MIB tables can reveal sensitive
> >>         information about individuals' activities and habits
> >>
> >> Sounds good to me.
> >>
> >>
> >>     Since this document is essentially a MIB module, your last
> >> sentence is covered by
> >>
> >>              implementations
> >>              claiming compliance to the SNMPv3 standard MUST include f=
ull
> >>              support for authentication and privacy via the User-based
> >>              Security Model (USM) [RFC3414
> <http://tools.ietf.org/html/rfc3414>] with the AES cipher algorithm
> >>              [RFC3826  <http://tools.ietf.org/html/rfc3826>].
> >>
> >> RFC 6988 notes the need for privacy protections for stored data,
> >> which the above text does not speak to, so I still think a reference t=
o RFC
> 6988 would add value here.
> >>
> >> It is a little disconcerting that use of SNMPv3 is provided as a
> >> SHOULD-level requirement without discussion of deployment scenarios
> >> and regardless of the sensitivity of the data being made available by
> >> any new MIB. For example, the tradeoffs between security and utility
> >> might be reasonable if (1) I'm using an older SNMP version on my
> >> closed home network to monitor my own energy use, but not if (2) my
> >> ISP is using it to monitor the same thing. The text quoted above
> >> basically  endorses unauthorized energy monitoring if the provider
> >> does not support SNMPv3, whereas it seems like what we would want to
> >> be saying is that in cases like
> >> (2) SNMPv3 is required.
> >>
> >> I understand that this is basically boilerplate language for MIB docs,=
 so I'm
> not sure what can be done, but it seems unfortunate.
> >>
> >> Alissa
> >>
> >>
> >>
> >>>     -----------------------------------------------------------------=
-----
> >>>     COMMENT:
> >>>
> >>> --------------------------------------------------------------------
> >>> --
> >>>
> >>>     Section 12.1:
> >>>     "New Assignments (and potential deprecation) to Power State Sets
> >>>              shall be administered by IANA and the guidelines and pro=
cedures
> >>>              are specified in [EMAN-FMWK], and will, as a consequence=
, the
> >>>              IANAPowerStateSet Textual Convention should be updated."
> >>>
> >>>     Not sure what this sentence means.
> >>     Good catch.
> >>     NEW:
> >>
> >>              "New Assignments (and potential deprecation) to Power Sta=
te Sets
> >>              shall be administered by IANA and the guidelines and proc=
edures
> >>              are specified in [EMAN-FMWK], and will, as a consequence,=
 update
> the
> >>              IANAPowerStateSet Textual Convention."
> >>
> >>
> >>     Regards, Benoit (as a document author)
> >>
> >>
> >>
> >>
> >>
> >> _______________________________________________
> >> 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
> >
>=20
> _______________________________________________
> MIB-DOCTORS mailing list
> MIB-DOCTORS@ietf.org
> https://www.ietf.org/mailman/listinfo/mib-doctors


From nobody Thu Jul 10 01:35:23 2014
Return-Path: <stephen.farrell@cs.tcd.ie>
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 9FFAE1A0185 for <mib-doctors@ietfa.amsl.com>; Thu, 10 Jul 2014 01:35:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.551
X-Spam-Level: 
X-Spam-Status: No, score=-2.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id f02cR9OKQEAt for <mib-doctors@ietfa.amsl.com>; Thu, 10 Jul 2014 01:35:18 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 095611A0034 for <mib-doctors@ietf.org>; Thu, 10 Jul 2014 01:35:17 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 612ABBDDC; Thu, 10 Jul 2014 09:35:16 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FR6FBmM013_Q; Thu, 10 Jul 2014 09:35:13 +0100 (IST)
Received: from [10.87.48.9] (unknown [86.46.20.156]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 9E5B9BDCF; Thu, 10 Jul 2014 09:35:13 +0100 (IST)
Message-ID: <53BE5041.1040308@cs.tcd.ie>
Date: Thu, 10 Jul 2014 09:35:13 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: "Bert Wijnen (IETF)" <bertietf@bwijnen.net>,  Benoit Claise <bclaise@cisco.com>, "MIB Doctors (E-mail)" <mib-doctors@ietf.org>
References: <CFE17DDA.458C3%alissa@cooperw.in> <53BC5081.6090809@cisco.com> <53BD6690.2040102@cisco.com> <53BE3D7E.2090302@bwijnen.net> <53BE4018.8030402@cisco.com> <53BE4833.3060506@bwijnen.net>
In-Reply-To: <53BE4833.3060506@bwijnen.net>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/JWkyFsEtDVThdoSpZoFCFlcnzFs
Cc: Adrian Farrel <adrian@olddog.co.uk>, 'Alissa Cooper' <alissa@cooperw.in>, sec-ads@tools.ietf.org
Subject: Re: [MIB-DOCTORS] Change the boilerplate
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, 10 Jul 2014 08:35:21 -0000

On 10/07/14 09:00, Bert Wijnen (IETF) wrote:
> I can see that for IoT related MIB modules there might be specific
> privacy concerns that
> you might want to describe in a special section. Not sure this should
> become a standard
> section in all MIB related documents though.

Yep, that's what I thought too. OTOH, its not clear that
boilerplate is really the right thing here - one common
way to handle privacy concerns is data minimisation which
here could map to not exposing an element or to only
exposing aggregate information rather than fine grained
values. Those are things that have to be thought about
by the MIB developers and can't just be handled via
current SNMP security since once the data is out there
the privacy breach has happened.

Cheers,
S.

PS: I'll add the above as a comment to the ballot later.

> 
> My 2 cents.
> 
> Bert
> 
> On 10/07/14 09:26, Benoit Claise wrote:
>>
>>> it is always interesting to see that when we get new ADs that we must
>>> rediscuss this whole topic.
>> Wait, there is more, two DISCUSSes from Kathleen regarding the
>> boilerplate (copied the Security ADs):
>> http://datatracker.ietf.org/doc/draft-ietf-eman-battery-mib/ballot/#kathleen-moriarty
>>
>> http://datatracker.ietf.org/doc/draft-ietf-eman-energy-aware-mib/ballot/#kathleen-moriarty
>>
>>
>> I would like to hear first from you guys before providing my opinion.
>>
>> Regards, Benoit
>>>
>>> But yes, there are/were implementations/deployments where one uses
>>> dedicated (secure) networks
>>> for the network management systems, and so that would work under a
>>> SHOULD.
>>>
>>> I do not recall if that was/is the only reason why we agreed on a
>>> SHOULD instead of MUST.
>>>
>>> Bert
>>>
>>> On 09/07/14 17:58, Benoit Claise wrote:
>>>> MIB doctors,
>>>>
>>>> Let me focus the discussion a little bit.
>>>> Alissa refers to this sentence in the boilerplate at
>>>> http://trac.tools.ietf.org/area/ops/trac/wiki/mib-security
>>>>
>>>>         Implementations SHOULD provide the security features
>>>> described by the
>>>>         SNMPv3 framework (see [RFC3410]), and implementations
>>>> claiming compliance
>>>>         to the SNMPv3 standard MUST include full support for
>>>> authentication and
>>>>         privacy via the User-based Security Model (USM) [RFC3414]
>>>> with the AES
>>>>         cipher algorithm [RFC3826].
>>>>
>>>>
>>>> Alissa's feedback is:
>>>>
>>>>     It is a little disconcerting that use of SNMPv3 is provided as a
>>>> SHOULD-level requirement without discussion of deployment
>>>>     scenarios and regardless of the sensitivity of the data being
>>>> made available by any new MIB. For example, the tradeoffs between
>>>>     security and utility might be reasonable if (1) I’m using an
>>>> older SNMP version on my closed home network to monitor my own
>>>>     energy use, but not if (2) my ISP is using it to monitor the
>>>> same thing. The text quoted above basically  endorses unauthorized
>>>>     energy monitoring if the provider does not support SNMPv3,
>>>> whereas it seems like what we would want to be saying is that in
>>>>     cases like (2) SNMPv3 is required.
>>>>
>>>> Can one of the old timers (who was part of the discussion) explain
>>>> the SHOULD rational? Personally, I can see two use cases in favor
>>>> off the SHOULD: an older SNMP version in a closed network,  or a
>>>> private data communication network dedicated to network management
>>>> with special protection out of SNMP (like encrypted tunnel)
>>>>
>>>> Should we now modify this sentence to say?
>>>>
>>>>     MUST provide the security features described by the
>>>>     SNMPv3 framework (see [RFC3410])
>>>>
>>>> Regards, Benoit
>>>>
>>>>> MIB doctors,
>>>>>
>>>>> It seems that the "Security Guidelines for IETF MIB modules"
>>>>> receives comment for each MIB module submitted to the IESG.
>>>>> Is it time to modify it, or are we redoing the same discussions
>>>>> over and over?
>>>>>
>>>>> Regards, Benoit
>>>>>
>>>>>
>>>>> -------- Original Message --------
>>>>> Subject:     Re: Alissa Cooper's Discuss on
>>>>> draft-ietf-eman-energy-monitoring-mib-12: (with DISCUSS and COMMENT)
>>>>> Date:     Tue, 8 Jul 2014 13:02:50 -0700
>>>>> From:     Alissa Cooper <alissa@cooperw.in>
>>>>> To:     Benoit Claise <bclaise@cisco.com>, The IESG <iesg@ietf.org>
>>>>> CC: <draft-ietf-eman-energy-monitoring-mib@tools.ietf.org>,
>>>>> <eman-chairs@tools.ietf.org>
>>>>>
>>>>>
>>>>>
>>>>> Hi Benoit,
>>>>>
>>>>> On 7/8/14, 1:44 AM, "Benoit Claise" <bclaise@cisco.com
>>>>> <mailto:bclaise@cisco.com>> wrote:
>>>>>
>>>>>     Hi Alissa,
>>>>>
>>>>>     Thanks for your review.
>>>>>>     Alissa Cooper has entered the following ballot position for
>>>>>>     draft-ietf-eman-energy-monitoring-mib-12: Discuss
>>>>>>
>>>>>>     When responding, please keep the subject line intact and reply
>>>>>> to all
>>>>>>     email addresses included in the To and CC lines. (Feel free to
>>>>>> cut this
>>>>>>     introductory paragraph, however.)
>>>>>>
>>>>>>
>>>>>>     Please refer
>>>>>> tohttp://www.ietf.org/iesg/statement/discuss-criteria.html
>>>>>>     for more information about IESG DISCUSS and COMMENT positions.
>>>>>>
>>>>>>
>>>>>>     The document, along with other ballot positions, can be found
>>>>>> here:
>>>>>> http://datatracker.ietf.org/doc/draft-ietf-eman-energy-monitoring-mib/
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> ----------------------------------------------------------------------
>>>>>>
>>>>>>     DISCUSS:
>>>>>> ----------------------------------------------------------------------
>>>>>>
>>>>>>
>>>>>>     Section 11 is missing a discussion of the privacy
>>>>>> considerations of
>>>>>>     energy and power monitoring. I would suggest something along
>>>>>> the lines of
>>>>>>     the following:
>>>>>>
>>>>>>     "In certain situations, energy and power monitoring can reveal
>>>>>> sensitive
>>>>>>     information about individuals' activities and habits.
>>>>>> Implementors of
>>>>>>     this specification should use appropriate privacy protections as
>>>>>>     discussed in Section 9 of RFC 6988 and monitoring of
>>>>>> individuals and
>>>>>>     homes should only occur with proper authorization."
>>>>>
>>>>>     Regarding your first sentence, I propose the following text,
>>>>> which would be in line with Security Guidelines for IETF MIB
>>>>>     modules at
>>>>> http://trac.tools.ietf.org/area/ops/trac/wiki/mib-security
>>>>>
>>>>>         Some of the readable objects in this MIB module (i.e.,
>>>>> objects with a
>>>>>         MAX-ACCESS other than not-accessible) may be considered
>>>>> sensitive or
>>>>>         vulnerable in some network environments.  It is thus
>>>>> important to
>>>>>         control even GET and/or NOTIFY access to these objects and
>>>>> possibly
>>>>>         to even encrypt the values of these objects when sending
>>>>> them over
>>>>>         the network via SNMP.  These are the tables and objects and
>>>>> their
>>>>>         sensitivity/vulnerability:
>>>>>
>>>>>         Access to the content of the eoPowerStateTable,
>>>>> eoEnergyTable, and
>>>>>         eoACPwrAttributesTable MIB tables can reveal sensitive
>>>>>         information about individuals' activities and habits
>>>>>
>>>>> Sounds good to me.
>>>>>
>>>>>
>>>>>     Since this document is essentially a MIB module, your last
>>>>> sentence is covered by
>>>>>
>>>>>              implementations
>>>>>              claiming compliance to the SNMPv3 standard MUST
>>>>> include full
>>>>>              support for authentication and privacy via the User-based
>>>>>              Security Model (USM) [RFC3414
>>>>> <http://tools.ietf.org/html/rfc3414>] with the AES cipher algorithm
>>>>>              [RFC3826 <http://tools.ietf.org/html/rfc3826>].
>>>>>
>>>>> RFC 6988 notes the need for privacy protections for stored data,
>>>>> which the above text does not speak to, so I still think a
>>>>> reference to RFC 6988 would add value here.
>>>>>
>>>>> It is a little disconcerting that use of SNMPv3 is provided as a
>>>>> SHOULD-level requirement without discussion of deployment
>>>>> scenarios and regardless of the sensitivity of the data being made
>>>>> available by any new MIB. For example, the tradeoffs between
>>>>> security and utility might be reasonable if (1) I’m using an older
>>>>> SNMP version on my closed home network to monitor my own energy
>>>>> use, but not if (2) my ISP is using it to monitor the same thing.
>>>>> The text quoted above basically  endorses unauthorized energy
>>>>> monitoring if the provider does not support SNMPv3, whereas it
>>>>> seems like what we would want to be saying is that in cases like
>>>>> (2) SNMPv3 is required.
>>>>>
>>>>> I understand that this is basically boilerplate language for MIB
>>>>> docs, so I’m not sure what can be done, but it seems unfortunate.
>>>>>
>>>>> Alissa
>>>>>
>>>>>
>>>>>
>>>>>> ----------------------------------------------------------------------
>>>>>>
>>>>>>     COMMENT:
>>>>>> ----------------------------------------------------------------------
>>>>>>
>>>>>>
>>>>>>     Section 12.1:
>>>>>>     "New Assignments (and potential deprecation) to Power State Sets
>>>>>>              shall be administered by IANA and the guidelines and
>>>>>> procedures
>>>>>>              are specified in [EMAN-FMWK], and will, as a
>>>>>> consequence, the
>>>>>>              IANAPowerStateSet Textual Convention should be updated."
>>>>>>
>>>>>>     Not sure what this sentence means.
>>>>>     Good catch.
>>>>>     NEW:
>>>>>
>>>>>              "New Assignments (and potential deprecation) to Power
>>>>> State Sets
>>>>>              shall be administered by IANA and the guidelines and
>>>>> procedures
>>>>>              are specified in [EMAN-FMWK], and will, as a
>>>>> consequence, update the
>>>>>              IANAPowerStateSet Textual Convention."
>>>>>
>>>>>
>>>>>     Regards, Benoit (as a document author)
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> 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 Thu Jul 10 06:01: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 2AE081B28D2 for <mib-doctors@ietfa.amsl.com>; Thu, 10 Jul 2014 06:01:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.553
X-Spam-Level: 
X-Spam-Status: No, score=-2.553 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lDlr-OiS72Rz for <mib-doctors@ietfa.amsl.com>; Thu, 10 Jul 2014 06:01:47 -0700 (PDT)
Received: from lucidvision.com (lucidvision.com [72.71.250.34]) by ietfa.amsl.com (Postfix) with ESMTP id 9A2431A0444 for <mib-doctors@ietf.org>; Thu, 10 Jul 2014 06:01:46 -0700 (PDT)
Received: from [192.168.1.105] (static-72-71-250-37.cncdnh.fast04.myfairpoint.net [72.71.250.37]) by lucidvision.com (Postfix) with ESMTP id 82F9D281998F; Thu, 10 Jul 2014 09:01:45 -0400 (EDT)
Content-Type: multipart/signed; boundary="Apple-Mail=_058FBAF4-6F16-4470-A4B3-42655BFEC064"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\))
From: "Thomas D. Nadeau" <tnadeau@lucidvision.com>
In-Reply-To: <53BE3D7E.2090302@bwijnen.net>
Date: Thu, 10 Jul 2014 09:01:44 -0400
Message-Id: <35D0B6EE-BEC2-44EB-869B-CBE462FE3CAB@lucidvision.com>
References: <CFE17DDA.458C3%alissa@cooperw.in> <53BC5081.6090809@cisco.com> <53BD6690.2040102@cisco.com> <53BE3D7E.2090302@bwijnen.net>
To: "Bert Wijnen (IETF)" <bertietf@bwijnen.net>
X-Mailer: Apple Mail (2.1878.2)
Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/Wytbqv-xzo1FkRykr-b0mC5QKEU
Cc: "MIB Doctors \(E-mail\)" <mib-doctors@ietf.org>, Alissa Cooper <alissa@cooperw.in>, Farrel Adrian <adrian@olddog.co.uk>
Subject: Re: [MIB-DOCTORS] Change the boilerplate
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, 10 Jul 2014 13:01:50 -0000

--Apple-Mail=_058FBAF4-6F16-4470-A4B3-42655BFEC064
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252


On Jul 10, 2014:3:15 AM, at 3:15 AM, Bert Wijnen (IETF) =
<bertietf@bwijnen.net> wrote:

> it is always interesting to see that when we get new ADs that we must =
rediscuss this whole topic.

	This is precisely one of the things that is broken about the =
IETF these days, if you ask me: the re-re-re-discussion of topics at the =
11:59th hour of a document's progress through the gauntlet.

> But yes, there are/were implementations/deployments where one uses =
dedicated (secure) networks
> for the network management systems, and so that would work under a =
SHOULD.

	I agree. Not all network operators use a secure management =
network, but many do.

> I do not recall if that was/is the only reason why we agreed on a =
SHOULD instead of MUST.

	I don't think you can do a MUST here; not everyone uses v3 - in =
fact, I think if you poll implementations you'll find VERY FEW using v3.=20=


	--Tom



>=20
> Bert
>=20
> On 09/07/14 17:58, Benoit Claise wrote:
>> MIB doctors,
>>=20
>> Let me focus the discussion a little bit.
>> Alissa refers to this sentence in the boilerplate at =
http://trac.tools.ietf.org/area/ops/trac/wiki/mib-security
>>=20
>>        Implementations SHOULD provide the security features described =
by the
>>        SNMPv3 framework (see [RFC3410]), and implementations claiming =
compliance
>>        to the SNMPv3 standard MUST include full support for =
authentication and
>>        privacy via the User-based Security Model (USM) [RFC3414] with =
the AES
>>        cipher algorithm [RFC3826].
>>=20
>>=20
>> Alissa's feedback is:
>>=20
>>    It is a little disconcerting that use of SNMPv3 is provided as a =
SHOULD-level requirement without discussion of deployment
>>    scenarios and regardless of the sensitivity of the data being made =
available by any new MIB. For example, the tradeoffs between
>>    security and utility might be reasonable if (1) I=92m using an =
older SNMP version on my closed home network to monitor my own
>>    energy use, but not if (2) my ISP is using it to monitor the same =
thing. The text quoted above basically  endorses unauthorized
>>    energy monitoring if the provider does not support SNMPv3, whereas =
it seems like what we would want to be saying is that in
>>    cases like (2) SNMPv3 is required.
>>=20
>> Can one of the old timers (who was part of the discussion) explain =
the SHOULD rational? Personally, I can see two use cases in favor
>> off the SHOULD: an older SNMP version in a closed network,  or a =
private data communication network dedicated to network management
>> with special protection out of SNMP (like encrypted tunnel)
>>=20
>> Should we now modify this sentence to say?
>>=20
>>    MUST provide the security features described by the
>>    SNMPv3 framework (see [RFC3410])
>>=20
>> Regards, Benoit
>>=20
>>> MIB doctors,
>>>=20
>>> It seems that the "Security Guidelines for IETF MIB modules" =
receives comment for each MIB module submitted to the IESG.
>>> Is it time to modify it, or are we redoing the same discussions over =
and over?
>>>=20
>>> Regards, Benoit
>>>=20
>>>=20
>>> -------- Original Message --------
>>> Subject: 	Re: Alissa Cooper's Discuss on =
draft-ietf-eman-energy-monitoring-mib-12: (with DISCUSS and COMMENT)
>>> Date: 	Tue, 8 Jul 2014 13:02:50 -0700
>>> From: 	Alissa Cooper <alissa@cooperw.in>
>>> To: 	Benoit Claise <bclaise@cisco.com>, The IESG =
<iesg@ietf.org>
>>> CC: 	<draft-ietf-eman-energy-monitoring-mib@tools.ietf.org>, =
<eman-chairs@tools.ietf.org>
>>>=20
>>>=20
>>>=20
>>> Hi Benoit,
>>>=20
>>> On 7/8/14, 1:44 AM, "Benoit Claise" <bclaise@cisco.com =
<mailto:bclaise@cisco.com>> wrote:
>>>=20
>>>    Hi Alissa,
>>>=20
>>>    Thanks for your review.
>>>>    Alissa Cooper has entered the following ballot position for
>>>>    draft-ietf-eman-energy-monitoring-mib-12: Discuss
>>>>=20
>>>>    When responding, please keep the subject line intact and reply =
to all
>>>>    email addresses included in the To and CC lines. (Feel free to =
cut this
>>>>    introductory paragraph, however.)
>>>>=20
>>>>=20
>>>>    Please refer =
tohttp://www.ietf.org/iesg/statement/discuss-criteria.html
>>>>    for more information about IESG DISCUSS and COMMENT positions.
>>>>=20
>>>>=20
>>>>    The document, along with other ballot positions, can be found =
here:
>>>>    =
http://datatracker.ietf.org/doc/draft-ietf-eman-energy-monitoring-mib/
>>>>=20
>>>>=20
>>>>=20
>>>>    =
----------------------------------------------------------------------
>>>>    DISCUSS:
>>>>    =
----------------------------------------------------------------------
>>>>=20
>>>>    Section 11 is missing a discussion of the privacy considerations =
of
>>>>    energy and power monitoring. I would suggest something along the =
lines of
>>>>    the following:
>>>>=20
>>>>    "In certain situations, energy and power monitoring can reveal =
sensitive
>>>>    information about individuals' activities and habits. =
Implementors of
>>>>    this specification should use appropriate privacy protections as
>>>>    discussed in Section 9 of RFC 6988 and monitoring of individuals =
and
>>>>    homes should only occur with proper authorization."
>>>=20
>>>    Regarding your first sentence, I propose the following text, =
which would be in line with Security Guidelines for IETF MIB
>>>    modules at =
http://trac.tools.ietf.org/area/ops/trac/wiki/mib-security
>>>=20
>>>        Some of the readable objects in this MIB module (i.e., =
objects with a
>>>        MAX-ACCESS other than not-accessible) may be considered =
sensitive or
>>>        vulnerable in some network environments.  It is thus =
important to
>>>        control even GET and/or NOTIFY access to these objects and =
possibly
>>>        to even encrypt the values of these objects when sending them =
over
>>>        the network via SNMP.  These are the tables and objects and =
their
>>>        sensitivity/vulnerability:
>>>=20
>>>        Access to the content of the eoPowerStateTable, =
eoEnergyTable, and
>>>        eoACPwrAttributesTable MIB tables can reveal sensitive
>>>        information about individuals' activities and habits
>>>=20
>>> Sounds good to me.
>>>=20
>>>=20
>>>    Since this document is essentially a MIB module, your last =
sentence is covered by
>>>=20
>>>             implementations
>>>             claiming compliance to the SNMPv3 standard MUST include =
full
>>>             support for authentication and privacy via the =
User-based
>>>             Security Model (USM) [RFC3414  =
<http://tools.ietf.org/html/rfc3414>] with the AES cipher algorithm
>>>             [RFC3826  <http://tools.ietf.org/html/rfc3826>].
>>>=20
>>> RFC 6988 notes the need for privacy protections for stored data, =
which the above text does not speak to, so I still think a
>>> reference to RFC 6988 would add value here.
>>>=20
>>> It is a little disconcerting that use of SNMPv3 is provided as a =
SHOULD-level requirement without discussion of deployment
>>> scenarios and regardless of the sensitivity of the data being made =
available by any new MIB. For example, the tradeoffs between
>>> security and utility might be reasonable if (1) I=92m using an older =
SNMP version on my closed home network to monitor my own energy
>>> use, but not if (2) my ISP is using it to monitor the same thing. =
The text quoted above basically  endorses unauthorized energy
>>> monitoring if the provider does not support SNMPv3, whereas it seems =
like what we would want to be saying is that in cases like
>>> (2) SNMPv3 is required.
>>>=20
>>> I understand that this is basically boilerplate language for MIB =
docs, so I=92m not sure what can be done, but it seems unfortunate.
>>>=20
>>> Alissa
>>>=20
>>>=20
>>>=20
>>>>    =
----------------------------------------------------------------------
>>>>    COMMENT:
>>>>    =
----------------------------------------------------------------------
>>>>=20
>>>>    Section 12.1:
>>>>    "New Assignments (and potential deprecation) to Power State Sets
>>>>             shall be administered by IANA and the guidelines and =
procedures
>>>>             are specified in [EMAN-FMWK], and will, as a =
consequence, the
>>>>             IANAPowerStateSet Textual Convention should be =
updated."
>>>>=20
>>>>    Not sure what this sentence means.
>>>    Good catch.
>>>    NEW:
>>>=20
>>>             "New Assignments (and potential deprecation) to Power =
State Sets
>>>             shall be administered by IANA and the guidelines and =
procedures
>>>             are specified in [EMAN-FMWK], and will, as a =
consequence, update the
>>>             IANAPowerStateSet Textual Convention."
>>>=20
>>>=20
>>>    Regards, Benoit (as a document author)
>>>=20
>>>=20
>>>=20
>>>=20
>>>=20
>>> _______________________________________________
>>> MIB-DOCTORS mailing list
>>> MIB-DOCTORS@ietf.org
>>> https://www.ietf.org/mailman/listinfo/mib-doctors
>>=20
>>=20
>>=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


--Apple-Mail=_058FBAF4-6F16-4470-A4B3-42655BFEC064
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

iQIcBAEBCgAGBQJTvo64AAoJEPcO+I7eiUJZfT8P/ju6HCgKnYS7dNBr6Xy1u63v
M4QlE72iPSUpADvDjW1yBGKgocd/mMnNrfpTWJAMXuYr4IWEUvSmaGFEyTRRr+wo
d59e8CTTc5KneIo56lptOhGw/sJur2ya21Jcaf5K6vDitt/6j/exYcUTtw6/HC1c
LEQ4kdUSC3cMFqDSCTnXn1mZGMF3pbbpXYdiD9TRD2GnEMJ0EBGaJp+vGeyPuS/+
s1x9UU1TUxITdPnCPaoONoIJyjcPctKFBD13lYtxMhPhnHPHqzWRMsO+qAxTCYyJ
CDnGGr/jXrRsgNa8uU43lCvPdlyDGvR6S0F119kA35FrlYi9Hu5czYFucGXX1URZ
pSYIiDlH9ilLF40CZXPHVKjr+oOMi6WQyN3ZG2hY+HHiG13/ZDYgogqdOKq02KLr
Jg22Zqh6Q2CVl29G5Ek0vKOaL7nOKpi8/0E+j+QMvnPzd7q4qnYDtpq2r8ajzpmj
BDWGWZn0Zo7gdoQ1JAdc0paVSNQ9vnu4p1cQqYXEQyIYC8S+AQz4jtt6a5QpXbpP
wNUEDVvIA0R16QPaout8NSrXgA9G/9iDISGoKUN8LkL8w5/xHLxztciXcHQkTYfr
qZmKPbd7pKU4Xcova9iajHsEG8kkHbHizTVcZMaNL7pg7RZT5WF4pG7JgOq4stVX
eKLCwr82eRA9x5w3SYSe
=SocF
-----END PGP SIGNATURE-----

--Apple-Mail=_058FBAF4-6F16-4470-A4B3-42655BFEC064--


From nobody Thu Jul 10 06:52:36 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 400221B28F1 for <mib-doctors@ietfa.amsl.com>; Thu, 10 Jul 2014 06:52:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.152
X-Spam-Level: 
X-Spam-Status: No, score=-15.152 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] 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 NbqLz5diz63a for <mib-doctors@ietfa.amsl.com>; Thu, 10 Jul 2014 06:52:29 -0700 (PDT)
Received: from aer-iport-4.cisco.com (aer-iport-4.cisco.com [173.38.203.54]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6C7671A05CB for <mib-doctors@ietf.org>; Thu, 10 Jul 2014 06:52:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=10045; q=dns/txt; s=iport; t=1405000348; x=1406209948; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=bdl9hLZvztwpux8tjAGpVMmPYDpmKr2zObeVSgtBDOE=; b=A3sYoauJ4N+5TqvNK+7Z+gLT7J0l+zsuO/OobnzCoyD+oJNSxAJNF1HF KAFsPdmN0iIk5RW53pcsGBo2BkDLdA/mr3Lv4GralUopOLcv8iCHVrOnL Kqz8bgQJKs5ZWxPHL8f6kh5lc2kjZjm9c/HwF4Vo0d4IR8cKQb3901WZh k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AnYLAGGZvlOtJssW/2dsb2JhbABZg2C/fAwJhzcBgSF1hAMBAQEDAQEBAS8BBTYKAQUHBAsRAwECAQkWCAcJAwIBAgEVHwkIBgEMAQUCAQEFiDEIDcd0F45iEQECTgcGhD0BBJsAgUiFR40Gg0U7L4EL
X-IronPort-AV: E=Sophos;i="5.01,638,1400025600"; d="scan'208";a="103021439"
Received: from aer-iport-nat.cisco.com (HELO aer-core-3.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP; 10 Jul 2014 13:52:25 +0000
Received: from [10.60.67.84] (ams-bclaise-8913.cisco.com [10.60.67.84]) by aer-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id s6ADqOol019740; Thu, 10 Jul 2014 13:52:25 GMT
Message-ID: <53BE9A98.8020805@cisco.com>
Date: Thu, 10 Jul 2014 15:52:24 +0200
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: "Thomas D. Nadeau" <tnadeau@lucidvision.com>, "Bert Wijnen (IETF)" <bertietf@bwijnen.net>
References: <CFE17DDA.458C3%alissa@cooperw.in> <53BC5081.6090809@cisco.com> <53BD6690.2040102@cisco.com> <53BE3D7E.2090302@bwijnen.net> <35D0B6EE-BEC2-44EB-869B-CBE462FE3CAB@lucidvision.com>
In-Reply-To: <35D0B6EE-BEC2-44EB-869B-CBE462FE3CAB@lucidvision.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/HmMuoqcbciJFFi78OqYsZ59R9Y4
Cc: "MIB Doctors \(E-mail\)" <mib-doctors@ietf.org>, Alissa Cooper <alissa@cooperw.in>, sec-ads@tools.ietf.org, Farrel Adrian <adrian@olddog.co.uk>
Subject: Re: [MIB-DOCTORS] Change the boilerplate - Kathleen'DISCUSS point 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: Thu, 10 Jul 2014 13:52:32 -0000

Dear all,

Let's try to address one point at a time, and get closure one by one.
https://datatracker.ietf.org/doc/draft-ietf-eman-energy-aware-mib/ballot/#kathleen-moriarty

Kathleen proposes:
OLD:

    "The
    support for SET operations in a non-secure environment without proper
    protection can have a negative effect on network operations."

NEW:

    "The
    support for SET operations in a non-secure environment without proper
    protection can have a negative effect on network operations or leave
    cyber physical devices used by individuals, homes, and business
    vulnerable to attack."


I believe this new proposal makes sense. Does anybody object?

Regards, Benoit

> On Jul 10, 2014:3:15 AM, at 3:15 AM, Bert Wijnen (IETF) <bertietf@bwijnen.net> wrote:
>
>> it is always interesting to see that when we get new ADs that we must rediscuss this whole topic.
> 	This is precisely one of the things that is broken about the IETF these days, if you ask me: the re-re-re-discussion of topics at the 11:59th hour of a document's progress through the gauntlet.
>
>> But yes, there are/were implementations/deployments where one uses dedicated (secure) networks
>> for the network management systems, and so that would work under a SHOULD.
> 	I agree. Not all network operators use a secure management network, but many do.
>
>> I do not recall if that was/is the only reason why we agreed on a SHOULD instead of MUST.
> 	I don't think you can do a MUST here; not everyone uses v3 - in fact, I think if you poll implementations you'll find VERY FEW using v3.
>
> 	--Tom
>
>
>
>> Bert
>>
>> On 09/07/14 17:58, Benoit Claise wrote:
>>> MIB doctors,
>>>
>>> Let me focus the discussion a little bit.
>>> Alissa refers to this sentence in the boilerplate at http://trac.tools.ietf.org/area/ops/trac/wiki/mib-security
>>>
>>>         Implementations SHOULD provide the security features described by the
>>>         SNMPv3 framework (see [RFC3410]), and implementations claiming compliance
>>>         to the SNMPv3 standard MUST include full support for authentication and
>>>         privacy via the User-based Security Model (USM) [RFC3414] with the AES
>>>         cipher algorithm [RFC3826].
>>>
>>>
>>> Alissa's feedback is:
>>>
>>>     It is a little disconcerting that use of SNMPv3 is provided as a SHOULD-level requirement without discussion of deployment
>>>     scenarios and regardless of the sensitivity of the data being made available by any new MIB. For example, the tradeoffs between
>>>     security and utility might be reasonable if (1) I’m using an older SNMP version on my closed home network to monitor my own
>>>     energy use, but not if (2) my ISP is using it to monitor the same thing. The text quoted above basically  endorses unauthorized
>>>     energy monitoring if the provider does not support SNMPv3, whereas it seems like what we would want to be saying is that in
>>>     cases like (2) SNMPv3 is required.
>>>
>>> Can one of the old timers (who was part of the discussion) explain the SHOULD rational? Personally, I can see two use cases in favor
>>> off the SHOULD: an older SNMP version in a closed network,  or a private data communication network dedicated to network management
>>> with special protection out of SNMP (like encrypted tunnel)
>>>
>>> Should we now modify this sentence to say?
>>>
>>>     MUST provide the security features described by the
>>>     SNMPv3 framework (see [RFC3410])
>>>
>>> Regards, Benoit
>>>
>>>> MIB doctors,
>>>>
>>>> It seems that the "Security Guidelines for IETF MIB modules" receives comment for each MIB module submitted to the IESG.
>>>> Is it time to modify it, or are we redoing the same discussions over and over?
>>>>
>>>> Regards, Benoit
>>>>
>>>>
>>>> -------- Original Message --------
>>>> Subject: 	Re: Alissa Cooper's Discuss on draft-ietf-eman-energy-monitoring-mib-12: (with DISCUSS and COMMENT)
>>>> Date: 	Tue, 8 Jul 2014 13:02:50 -0700
>>>> From: 	Alissa Cooper <alissa@cooperw.in>
>>>> To: 	Benoit Claise <bclaise@cisco.com>, The IESG <iesg@ietf.org>
>>>> CC: 	<draft-ietf-eman-energy-monitoring-mib@tools.ietf.org>, <eman-chairs@tools.ietf.org>
>>>>
>>>>
>>>>
>>>> Hi Benoit,
>>>>
>>>> On 7/8/14, 1:44 AM, "Benoit Claise" <bclaise@cisco.com <mailto:bclaise@cisco.com>> wrote:
>>>>
>>>>     Hi Alissa,
>>>>
>>>>     Thanks for your review.
>>>>>     Alissa Cooper has entered the following ballot position for
>>>>>     draft-ietf-eman-energy-monitoring-mib-12: Discuss
>>>>>
>>>>>     When responding, please keep the subject line intact and reply to all
>>>>>     email addresses included in the To and CC lines. (Feel free to cut this
>>>>>     introductory paragraph, however.)
>>>>>
>>>>>
>>>>>     Please refer tohttp://www.ietf.org/iesg/statement/discuss-criteria.html
>>>>>     for more information about IESG DISCUSS and COMMENT positions.
>>>>>
>>>>>
>>>>>     The document, along with other ballot positions, can be found here:
>>>>>     http://datatracker.ietf.org/doc/draft-ietf-eman-energy-monitoring-mib/
>>>>>
>>>>>
>>>>>
>>>>>     ----------------------------------------------------------------------
>>>>>     DISCUSS:
>>>>>     ----------------------------------------------------------------------
>>>>>
>>>>>     Section 11 is missing a discussion of the privacy considerations of
>>>>>     energy and power monitoring. I would suggest something along the lines of
>>>>>     the following:
>>>>>
>>>>>     "In certain situations, energy and power monitoring can reveal sensitive
>>>>>     information about individuals' activities and habits. Implementors of
>>>>>     this specification should use appropriate privacy protections as
>>>>>     discussed in Section 9 of RFC 6988 and monitoring of individuals and
>>>>>     homes should only occur with proper authorization."
>>>>     Regarding your first sentence, I propose the following text, which would be in line with Security Guidelines for IETF MIB
>>>>     modules at http://trac.tools.ietf.org/area/ops/trac/wiki/mib-security
>>>>
>>>>         Some of the readable objects in this MIB module (i.e., objects with a
>>>>         MAX-ACCESS other than not-accessible) may be considered sensitive or
>>>>         vulnerable in some network environments.  It is thus important to
>>>>         control even GET and/or NOTIFY access to these objects and possibly
>>>>         to even encrypt the values of these objects when sending them over
>>>>         the network via SNMP.  These are the tables and objects and their
>>>>         sensitivity/vulnerability:
>>>>
>>>>         Access to the content of the eoPowerStateTable, eoEnergyTable, and
>>>>         eoACPwrAttributesTable MIB tables can reveal sensitive
>>>>         information about individuals' activities and habits
>>>>
>>>> Sounds good to me.
>>>>
>>>>
>>>>     Since this document is essentially a MIB module, your last sentence is covered by
>>>>
>>>>              implementations
>>>>              claiming compliance to the SNMPv3 standard MUST include full
>>>>              support for authentication and privacy via the User-based
>>>>              Security Model (USM) [RFC3414  <http://tools.ietf.org/html/rfc3414>] with the AES cipher algorithm
>>>>              [RFC3826  <http://tools.ietf.org/html/rfc3826>].
>>>>
>>>> RFC 6988 notes the need for privacy protections for stored data, which the above text does not speak to, so I still think a
>>>> reference to RFC 6988 would add value here.
>>>>
>>>> It is a little disconcerting that use of SNMPv3 is provided as a SHOULD-level requirement without discussion of deployment
>>>> scenarios and regardless of the sensitivity of the data being made available by any new MIB. For example, the tradeoffs between
>>>> security and utility might be reasonable if (1) I’m using an older SNMP version on my closed home network to monitor my own energy
>>>> use, but not if (2) my ISP is using it to monitor the same thing. The text quoted above basically  endorses unauthorized energy
>>>> monitoring if the provider does not support SNMPv3, whereas it seems like what we would want to be saying is that in cases like
>>>> (2) SNMPv3 is required.
>>>>
>>>> I understand that this is basically boilerplate language for MIB docs, so I’m not sure what can be done, but it seems unfortunate.
>>>>
>>>> Alissa
>>>>
>>>>
>>>>
>>>>>     ----------------------------------------------------------------------
>>>>>     COMMENT:
>>>>>     ----------------------------------------------------------------------
>>>>>
>>>>>     Section 12.1:
>>>>>     "New Assignments (and potential deprecation) to Power State Sets
>>>>>              shall be administered by IANA and the guidelines and procedures
>>>>>              are specified in [EMAN-FMWK], and will, as a consequence, the
>>>>>              IANAPowerStateSet Textual Convention should be updated."
>>>>>
>>>>>     Not sure what this sentence means.
>>>>     Good catch.
>>>>     NEW:
>>>>
>>>>              "New Assignments (and potential deprecation) to Power State Sets
>>>>              shall be administered by IANA and the guidelines and procedures
>>>>              are specified in [EMAN-FMWK], and will, as a consequence, update the
>>>>              IANAPowerStateSet Textual Convention."
>>>>
>>>>
>>>>     Regards, Benoit (as a document author)
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> 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
>>


From nobody Thu Jul 10 06:56:02 2014
Return-Path: <stephen.farrell@cs.tcd.ie>
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 269E41A03EF for <mib-doctors@ietfa.amsl.com>; Thu, 10 Jul 2014 06:56:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.551
X-Spam-Level: 
X-Spam-Status: No, score=-2.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DIh2G1uRDDAm for <mib-doctors@ietfa.amsl.com>; Thu, 10 Jul 2014 06:55:58 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 635811A03A4 for <mib-doctors@ietf.org>; Thu, 10 Jul 2014 06:55:56 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 481B2BDFE; Thu, 10 Jul 2014 14:55:56 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 032nGNV-KSDz; Thu, 10 Jul 2014 14:55:54 +0100 (IST)
Received: from [10.87.48.9] (unknown [86.46.20.156]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 1285FBE14; Thu, 10 Jul 2014 14:55:53 +0100 (IST)
Message-ID: <53BE9B68.1010509@cs.tcd.ie>
Date: Thu, 10 Jul 2014 14:55:52 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Benoit Claise <bclaise@cisco.com>,  "Thomas D. Nadeau" <tnadeau@lucidvision.com>, "Bert Wijnen (IETF)" <bertietf@bwijnen.net>
References: <CFE17DDA.458C3%alissa@cooperw.in> <53BC5081.6090809@cisco.com> <53BD6690.2040102@cisco.com> <53BE3D7E.2090302@bwijnen.net> <35D0B6EE-BEC2-44EB-869B-CBE462FE3CAB@lucidvision.com> <53BE9A98.8020805@cisco.com>
In-Reply-To: <53BE9A98.8020805@cisco.com>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/NvvLoAmPq-9p8r9__3Iy94-yqso
Cc: "MIB Doctors \(E-mail\)" <mib-doctors@ietf.org>, Alissa Cooper <alissa@cooperw.in>, sec-ads@tools.ietf.org, Farrel Adrian <adrian@olddog.co.uk>
Subject: Re: [MIB-DOCTORS] Change the boilerplate - Kathleen'DISCUSS point 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: Thu, 10 Jul 2014 13:56:01 -0000

On 10/07/14 14:52, Benoit Claise wrote:
> Dear all,
> 
> Let's try to address one point at a time, and get closure one by one.
> https://datatracker.ietf.org/doc/draft-ietf-eman-energy-aware-mib/ballot/#kathleen-moriarty
> 
> 
> Kathleen proposes:
> OLD:
> 
>    "The
>    support for SET operations in a non-secure environment without proper
>    protection can have a negative effect on network operations."
> 
> NEW:
> 
>    "The
>    support for SET operations in a non-secure environment without proper
>    protection can have a negative effect on network operations or leave
>    cyber physical devices used by individuals, homes, and business
>    vulnerable to attack."
> 
> 
> I believe this new proposal makes sense. Does anybody object?

s/cyber physical// or replace it with something that does not
use the word cyber which is utterly laden with marketing and
other BS IMO. (Apologies to those of you who partly make a
living from such, which I do understand, but don't have to
do:-) I think we should avoid including such non-technical
terms in things like this. (Think "cloud":-)

S.


> 
> Regards, Benoit
> 
>> On Jul 10, 2014:3:15 AM, at 3:15 AM, Bert Wijnen (IETF)
>> <bertietf@bwijnen.net> wrote:
>>
>>> it is always interesting to see that when we get new ADs that we must
>>> rediscuss this whole topic.
>>     This is precisely one of the things that is broken about the IETF
>> these days, if you ask me: the re-re-re-discussion of topics at the
>> 11:59th hour of a document's progress through the gauntlet.
>>
>>> But yes, there are/were implementations/deployments where one uses
>>> dedicated (secure) networks
>>> for the network management systems, and so that would work under a
>>> SHOULD.
>>     I agree. Not all network operators use a secure management
>> network, but many do.
>>
>>> I do not recall if that was/is the only reason why we agreed on a
>>> SHOULD instead of MUST.
>>     I don't think you can do a MUST here; not everyone uses v3 - in
>> fact, I think if you poll implementations you'll find VERY FEW using v3.
>>
>>     --Tom
>>
>>
>>
>>> Bert
>>>
>>> On 09/07/14 17:58, Benoit Claise wrote:
>>>> MIB doctors,
>>>>
>>>> Let me focus the discussion a little bit.
>>>> Alissa refers to this sentence in the boilerplate at
>>>> http://trac.tools.ietf.org/area/ops/trac/wiki/mib-security
>>>>
>>>>         Implementations SHOULD provide the security features
>>>> described by the
>>>>         SNMPv3 framework (see [RFC3410]), and implementations
>>>> claiming compliance
>>>>         to the SNMPv3 standard MUST include full support for
>>>> authentication and
>>>>         privacy via the User-based Security Model (USM) [RFC3414]
>>>> with the AES
>>>>         cipher algorithm [RFC3826].
>>>>
>>>>
>>>> Alissa's feedback is:
>>>>
>>>>     It is a little disconcerting that use of SNMPv3 is provided as a
>>>> SHOULD-level requirement without discussion of deployment
>>>>     scenarios and regardless of the sensitivity of the data being
>>>> made available by any new MIB. For example, the tradeoffs between
>>>>     security and utility might be reasonable if (1) I’m using an
>>>> older SNMP version on my closed home network to monitor my own
>>>>     energy use, but not if (2) my ISP is using it to monitor the
>>>> same thing. The text quoted above basically  endorses unauthorized
>>>>     energy monitoring if the provider does not support SNMPv3,
>>>> whereas it seems like what we would want to be saying is that in
>>>>     cases like (2) SNMPv3 is required.
>>>>
>>>> Can one of the old timers (who was part of the discussion) explain
>>>> the SHOULD rational? Personally, I can see two use cases in favor
>>>> off the SHOULD: an older SNMP version in a closed network,  or a
>>>> private data communication network dedicated to network management
>>>> with special protection out of SNMP (like encrypted tunnel)
>>>>
>>>> Should we now modify this sentence to say?
>>>>
>>>>     MUST provide the security features described by the
>>>>     SNMPv3 framework (see [RFC3410])
>>>>
>>>> Regards, Benoit
>>>>
>>>>> MIB doctors,
>>>>>
>>>>> It seems that the "Security Guidelines for IETF MIB modules"
>>>>> receives comment for each MIB module submitted to the IESG.
>>>>> Is it time to modify it, or are we redoing the same discussions
>>>>> over and over?
>>>>>
>>>>> Regards, Benoit
>>>>>
>>>>>
>>>>> -------- Original Message --------
>>>>> Subject:     Re: Alissa Cooper's Discuss on
>>>>> draft-ietf-eman-energy-monitoring-mib-12: (with DISCUSS and COMMENT)
>>>>> Date:     Tue, 8 Jul 2014 13:02:50 -0700
>>>>> From:     Alissa Cooper <alissa@cooperw.in>
>>>>> To:     Benoit Claise <bclaise@cisco.com>, The IESG <iesg@ietf.org>
>>>>> CC:     <draft-ietf-eman-energy-monitoring-mib@tools.ietf.org>,
>>>>> <eman-chairs@tools.ietf.org>
>>>>>
>>>>>
>>>>>
>>>>> Hi Benoit,
>>>>>
>>>>> On 7/8/14, 1:44 AM, "Benoit Claise" <bclaise@cisco.com
>>>>> <mailto:bclaise@cisco.com>> wrote:
>>>>>
>>>>>     Hi Alissa,
>>>>>
>>>>>     Thanks for your review.
>>>>>>     Alissa Cooper has entered the following ballot position for
>>>>>>     draft-ietf-eman-energy-monitoring-mib-12: Discuss
>>>>>>
>>>>>>     When responding, please keep the subject line intact and reply
>>>>>> to all
>>>>>>     email addresses included in the To and CC lines. (Feel free to
>>>>>> cut this
>>>>>>     introductory paragraph, however.)
>>>>>>
>>>>>>
>>>>>>     Please refer
>>>>>> tohttp://www.ietf.org/iesg/statement/discuss-criteria.html
>>>>>>     for more information about IESG DISCUSS and COMMENT positions.
>>>>>>
>>>>>>
>>>>>>     The document, along with other ballot positions, can be found
>>>>>> here:
>>>>>>    
>>>>>> http://datatracker.ietf.org/doc/draft-ietf-eman-energy-monitoring-mib/
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>    
>>>>>> ----------------------------------------------------------------------
>>>>>>
>>>>>>     DISCUSS:
>>>>>>    
>>>>>> ----------------------------------------------------------------------
>>>>>>
>>>>>>
>>>>>>     Section 11 is missing a discussion of the privacy
>>>>>> considerations of
>>>>>>     energy and power monitoring. I would suggest something along
>>>>>> the lines of
>>>>>>     the following:
>>>>>>
>>>>>>     "In certain situations, energy and power monitoring can reveal
>>>>>> sensitive
>>>>>>     information about individuals' activities and habits.
>>>>>> Implementors of
>>>>>>     this specification should use appropriate privacy protections as
>>>>>>     discussed in Section 9 of RFC 6988 and monitoring of
>>>>>> individuals and
>>>>>>     homes should only occur with proper authorization."
>>>>>     Regarding your first sentence, I propose the following text,
>>>>> which would be in line with Security Guidelines for IETF MIB
>>>>>     modules at
>>>>> http://trac.tools.ietf.org/area/ops/trac/wiki/mib-security
>>>>>
>>>>>         Some of the readable objects in this MIB module (i.e.,
>>>>> objects with a
>>>>>         MAX-ACCESS other than not-accessible) may be considered
>>>>> sensitive or
>>>>>         vulnerable in some network environments.  It is thus
>>>>> important to
>>>>>         control even GET and/or NOTIFY access to these objects and
>>>>> possibly
>>>>>         to even encrypt the values of these objects when sending
>>>>> them over
>>>>>         the network via SNMP.  These are the tables and objects and
>>>>> their
>>>>>         sensitivity/vulnerability:
>>>>>
>>>>>         Access to the content of the eoPowerStateTable,
>>>>> eoEnergyTable, and
>>>>>         eoACPwrAttributesTable MIB tables can reveal sensitive
>>>>>         information about individuals' activities and habits
>>>>>
>>>>> Sounds good to me.
>>>>>
>>>>>
>>>>>     Since this document is essentially a MIB module, your last
>>>>> sentence is covered by
>>>>>
>>>>>              implementations
>>>>>              claiming compliance to the SNMPv3 standard MUST
>>>>> include full
>>>>>              support for authentication and privacy via the User-based
>>>>>              Security Model (USM) [RFC3414 
>>>>> <http://tools.ietf.org/html/rfc3414>] with the AES cipher algorithm
>>>>>              [RFC3826  <http://tools.ietf.org/html/rfc3826>].
>>>>>
>>>>> RFC 6988 notes the need for privacy protections for stored data,
>>>>> which the above text does not speak to, so I still think a
>>>>> reference to RFC 6988 would add value here.
>>>>>
>>>>> It is a little disconcerting that use of SNMPv3 is provided as a
>>>>> SHOULD-level requirement without discussion of deployment
>>>>> scenarios and regardless of the sensitivity of the data being made
>>>>> available by any new MIB. For example, the tradeoffs between
>>>>> security and utility might be reasonable if (1) I’m using an older
>>>>> SNMP version on my closed home network to monitor my own energy
>>>>> use, but not if (2) my ISP is using it to monitor the same thing.
>>>>> The text quoted above basically  endorses unauthorized energy
>>>>> monitoring if the provider does not support SNMPv3, whereas it
>>>>> seems like what we would want to be saying is that in cases like
>>>>> (2) SNMPv3 is required.
>>>>>
>>>>> I understand that this is basically boilerplate language for MIB
>>>>> docs, so I’m not sure what can be done, but it seems unfortunate.
>>>>>
>>>>> Alissa
>>>>>
>>>>>
>>>>>
>>>>>>    
>>>>>> ----------------------------------------------------------------------
>>>>>>
>>>>>>     COMMENT:
>>>>>>    
>>>>>> ----------------------------------------------------------------------
>>>>>>
>>>>>>
>>>>>>     Section 12.1:
>>>>>>     "New Assignments (and potential deprecation) to Power State Sets
>>>>>>              shall be administered by IANA and the guidelines and
>>>>>> procedures
>>>>>>              are specified in [EMAN-FMWK], and will, as a
>>>>>> consequence, the
>>>>>>              IANAPowerStateSet Textual Convention should be updated."
>>>>>>
>>>>>>     Not sure what this sentence means.
>>>>>     Good catch.
>>>>>     NEW:
>>>>>
>>>>>              "New Assignments (and potential deprecation) to Power
>>>>> State Sets
>>>>>              shall be administered by IANA and the guidelines and
>>>>> procedures
>>>>>              are specified in [EMAN-FMWK], and will, as a
>>>>> consequence, update the
>>>>>              IANAPowerStateSet Textual Convention."
>>>>>
>>>>>
>>>>>     Regards, Benoit (as a document author)
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> 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
>>>
> 


From nobody Thu Jul 10 06:56:27 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 902D31A0527 for <mib-doctors@ietfa.amsl.com>; Thu, 10 Jul 2014 06:56:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.551
X-Spam-Level: 
X-Spam-Status: No, score=-7.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.651] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K9HRoUg-TcXZ for <mib-doctors@ietfa.amsl.com>; Thu, 10 Jul 2014 06:56:18 -0700 (PDT)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C1B411A03A4 for <mib-doctors@ietf.org>; Thu, 10 Jul 2014 06:56:18 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AtYNAJaavlOHCzIm/2dsb2JhbABZgmokUlqreAEBAQEBAQaTBRkKC4c3AYELFnWEAwEBAQEDAQEBDyg0CwwEAgEIDQEDAwEBAQEKFAkHJwsUCQgCBAENBQgBGYggAQykB6NkF4V6hw+BWREBAh0xBwaDJ4EWBZxIhXCMXYNDbIELOQ
X-IronPort-AV: E=Sophos;i="5.01,638,1400040000"; d="scan'208";a="73299007"
Received: from unknown (HELO p-us1-erheast-smtpauth.us1.avaya.com) ([135.11.50.38]) by co300216-co-outbound.net.avaya.com with ESMTP; 10 Jul 2014 09:56:16 -0400
X-OutboundMail_SMTP: 1
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; 10 Jul 2014 09:56:16 -0400
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, 10 Jul 2014 15:56:14 +0200
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: Benoit Claise <bclaise@cisco.com>, "Thomas D. Nadeau" <tnadeau@lucidvision.com>, "Bert Wijnen (IETF)" <bertietf@bwijnen.net>
Thread-Topic: [MIB-DOCTORS] Change the boilerplate - Kathleen'DISCUSS point 2
Thread-Index: AQHPnEY2CUXpPMBo3UOPqE1AN3ioiZuZVCkg
Date: Thu, 10 Jul 2014 13:56:14 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA5C83D043@AZ-FFEXMB04.global.avaya.com>
References: <CFE17DDA.458C3%alissa@cooperw.in> <53BC5081.6090809@cisco.com> <53BD6690.2040102@cisco.com> <53BE3D7E.2090302@bwijnen.net> <35D0B6EE-BEC2-44EB-869B-CBE462FE3CAB@lucidvision.com> <53BE9A98.8020805@cisco.com>
In-Reply-To: <53BE9A98.8020805@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: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/QmjdvOQ4aq1zhtoQw4rntRTIdj8
Cc: "MIB Doctors \(E-mail\)" <mib-doctors@ietf.org>, Alissa Cooper <alissa@cooperw.in>, "sec-ads@tools.ietf.org" <sec-ads@tools.ietf.org>, Farrel Adrian <adrian@olddog.co.uk>
Subject: Re: [MIB-DOCTORS] Change the boilerplate - Kathleen'DISCUSS point 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: Thu, 10 Jul 2014 13:56:25 -0000

I do not know exactly what 'cyber physical devices' means. I think that you=
 mean 'devices connected to the network'. Otherwise, looks fine to me.=20

Regards,

Dan


> -----Original Message-----
> From: MIB-DOCTORS [mailto:mib-doctors-bounces@ietf.org] On Behalf Of
> Benoit Claise
> Sent: Thursday, July 10, 2014 4:52 PM
> To: Thomas D. Nadeau; Bert Wijnen (IETF)
> Cc: MIB Doctors (E-mail); Alissa Cooper; sec-ads@tools.ietf.org; Farrel A=
drian
> Subject: Re: [MIB-DOCTORS] Change the boilerplate - Kathleen'DISCUSS
> point 2
>=20
> Dear all,
>=20
> Let's try to address one point at a time, and get closure one by one.
> https://datatracker.ietf.org/doc/draft-ietf-eman-energy-aware-
> mib/ballot/#kathleen-moriarty
>=20
> Kathleen proposes:
> OLD:
>=20
>     "The
>     support for SET operations in a non-secure environment without proper
>     protection can have a negative effect on network operations."
>=20
> NEW:
>=20
>     "The
>     support for SET operations in a non-secure environment without proper
>     protection can have a negative effect on network operations or leave
>     cyber physical devices used by individuals, homes, and business
>     vulnerable to attack."
>=20
>=20
> I believe this new proposal makes sense. Does anybody object?
>=20
> Regards, Benoit
>=20
> > On Jul 10, 2014:3:15 AM, at 3:15 AM, Bert Wijnen (IETF)
> <bertietf@bwijnen.net> wrote:
> >
> >> it is always interesting to see that when we get new ADs that we must
> rediscuss this whole topic.
> > 	This is precisely one of the things that is broken about the IETF thes=
e
> days, if you ask me: the re-re-re-discussion of topics at the 11:59th hou=
r of a
> document's progress through the gauntlet.
> >
> >> But yes, there are/were implementations/deployments where one uses
> >> dedicated (secure) networks for the network management systems, and
> so that would work under a SHOULD.
> > 	I agree. Not all network operators use a secure management
> network, but many do.
> >
> >> I do not recall if that was/is the only reason why we agreed on a SHOU=
LD
> instead of MUST.
> > 	I don't think you can do a MUST here; not everyone uses v3 - in fact, =
I
> think if you poll implementations you'll find VERY FEW using v3.
> >
> > 	--Tom
> >
> >
> >
> >> Bert
> >>
> >> On 09/07/14 17:58, Benoit Claise wrote:
> >>> MIB doctors,
> >>>
> >>> Let me focus the discussion a little bit.
> >>> Alissa refers to this sentence in the boilerplate at
> >>> http://trac.tools.ietf.org/area/ops/trac/wiki/mib-security
> >>>
> >>>         Implementations SHOULD provide the security features describe=
d
> by the
> >>>         SNMPv3 framework (see [RFC3410]), and implementations claimin=
g
> compliance
> >>>         to the SNMPv3 standard MUST include full support for
> authentication and
> >>>         privacy via the User-based Security Model (USM) [RFC3414] wit=
h the
> AES
> >>>         cipher algorithm [RFC3826].
> >>>
> >>>
> >>> Alissa's feedback is:
> >>>
> >>>     It is a little disconcerting that use of SNMPv3 is provided as a =
SHOULD-
> level requirement without discussion of deployment
> >>>     scenarios and regardless of the sensitivity of the data being mad=
e
> available by any new MIB. For example, the tradeoffs between
> >>>     security and utility might be reasonable if (1) I'm using an olde=
r SNMP
> version on my closed home network to monitor my own
> >>>     energy use, but not if (2) my ISP is using it to monitor the same=
 thing.
> The text quoted above basically  endorses unauthorized
> >>>     energy monitoring if the provider does not support SNMPv3, wherea=
s
> it seems like what we would want to be saying is that in
> >>>     cases like (2) SNMPv3 is required.
> >>>
> >>> Can one of the old timers (who was part of the discussion) explain
> >>> the SHOULD rational? Personally, I can see two use cases in favor
> >>> off the SHOULD: an older SNMP version in a closed network,  or a
> >>> private data communication network dedicated to network
> management
> >>> with special protection out of SNMP (like encrypted tunnel)
> >>>
> >>> Should we now modify this sentence to say?
> >>>
> >>>     MUST provide the security features described by the
> >>>     SNMPv3 framework (see [RFC3410])
> >>>
> >>> Regards, Benoit
> >>>
> >>>> MIB doctors,
> >>>>
> >>>> It seems that the "Security Guidelines for IETF MIB modules" receive=
s
> comment for each MIB module submitted to the IESG.
> >>>> Is it time to modify it, or are we redoing the same discussions over=
 and
> over?
> >>>>
> >>>> Regards, Benoit
> >>>>
> >>>>
> >>>> -------- Original Message --------
> >>>> Subject: 	Re: Alissa Cooper's Discuss on draft-ietf-eman-energy-
> monitoring-mib-12: (with DISCUSS and COMMENT)
> >>>> Date: 	Tue, 8 Jul 2014 13:02:50 -0700
> >>>> From: 	Alissa Cooper <alissa@cooperw.in>
> >>>> To: 	Benoit Claise <bclaise@cisco.com>, The IESG <iesg@ietf.org>
> >>>> CC: 	<draft-ietf-eman-energy-monitoring-mib@tools.ietf.org>,
> <eman-chairs@tools.ietf.org>
> >>>>
> >>>>
> >>>>
> >>>> Hi Benoit,
> >>>>
> >>>> On 7/8/14, 1:44 AM, "Benoit Claise" <bclaise@cisco.com
> <mailto:bclaise@cisco.com>> wrote:
> >>>>
> >>>>     Hi Alissa,
> >>>>
> >>>>     Thanks for your review.
> >>>>>     Alissa Cooper has entered the following ballot position for
> >>>>>     draft-ietf-eman-energy-monitoring-mib-12: Discuss
> >>>>>
> >>>>>     When responding, please keep the subject line intact and reply =
to
> all
> >>>>>     email addresses included in the To and CC lines. (Feel free to =
cut this
> >>>>>     introductory paragraph, however.)
> >>>>>
> >>>>>
> >>>>>     Please refer tohttp://www.ietf.org/iesg/statement/discuss-
> criteria.html
> >>>>>     for more information about IESG DISCUSS and COMMENT positions.
> >>>>>
> >>>>>
> >>>>>     The document, along with other ballot positions, can be found h=
ere:
> >>>>>
> >>>>> http://datatracker.ietf.org/doc/draft-ietf-eman-energy-monitoring-
> >>>>> mib/
> >>>>>
> >>>>>
> >>>>>
> >>>>>     ---------------------------------------------------------------=
-------
> >>>>>     DISCUSS:
> >>>>>
> >>>>> ------------------------------------------------------------------
> >>>>> ----
> >>>>>
> >>>>>     Section 11 is missing a discussion of the privacy consideration=
s of
> >>>>>     energy and power monitoring. I would suggest something along th=
e
> lines of
> >>>>>     the following:
> >>>>>
> >>>>>     "In certain situations, energy and power monitoring can reveal
> sensitive
> >>>>>     information about individuals' activities and habits. Implement=
ors of
> >>>>>     this specification should use appropriate privacy protections a=
s
> >>>>>     discussed in Section 9 of RFC 6988 and monitoring of individual=
s and
> >>>>>     homes should only occur with proper authorization."
> >>>>     Regarding your first sentence, I propose the following text, whi=
ch
> would be in line with Security Guidelines for IETF MIB
> >>>>     modules at
> >>>> http://trac.tools.ietf.org/area/ops/trac/wiki/mib-security
> >>>>
> >>>>         Some of the readable objects in this MIB module (i.e., objec=
ts with
> a
> >>>>         MAX-ACCESS other than not-accessible) may be considered
> sensitive or
> >>>>         vulnerable in some network environments.  It is thus importa=
nt to
> >>>>         control even GET and/or NOTIFY access to these objects and
> possibly
> >>>>         to even encrypt the values of these objects when sending the=
m
> over
> >>>>         the network via SNMP.  These are the tables and objects and =
their
> >>>>         sensitivity/vulnerability:
> >>>>
> >>>>         Access to the content of the eoPowerStateTable, eoEnergyTabl=
e,
> and
> >>>>         eoACPwrAttributesTable MIB tables can reveal sensitive
> >>>>         information about individuals' activities and habits
> >>>>
> >>>> Sounds good to me.
> >>>>
> >>>>
> >>>>     Since this document is essentially a MIB module, your last
> >>>> sentence is covered by
> >>>>
> >>>>              implementations
> >>>>              claiming compliance to the SNMPv3 standard MUST include=
 full
> >>>>              support for authentication and privacy via the User-bas=
ed
> >>>>              Security Model (USM) [RFC3414
> <http://tools.ietf.org/html/rfc3414>] with the AES cipher algorithm
> >>>>              [RFC3826  <http://tools.ietf.org/html/rfc3826>].
> >>>>
> >>>> RFC 6988 notes the need for privacy protections for stored data,
> >>>> which the above text does not speak to, so I still think a reference=
 to
> RFC 6988 would add value here.
> >>>>
> >>>> It is a little disconcerting that use of SNMPv3 is provided as a
> >>>> SHOULD-level requirement without discussion of deployment
> scenarios
> >>>> and regardless of the sensitivity of the data being made available
> >>>> by any new MIB. For example, the tradeoffs between security and
> >>>> utility might be reasonable if (1) I'm using an older SNMP version
> >>>> on my closed home network to monitor my own energy use, but not if
> >>>> (2) my ISP is using it to monitor the same thing. The text quoted
> >>>> above basically  endorses unauthorized energy monitoring if the
> >>>> provider does not support SNMPv3, whereas it seems like what we
> >>>> would want to be saying is that in cases like
> >>>> (2) SNMPv3 is required.
> >>>>
> >>>> I understand that this is basically boilerplate language for MIB doc=
s, so
> I'm not sure what can be done, but it seems unfortunate.
> >>>>
> >>>> Alissa
> >>>>
> >>>>
> >>>>
> >>>>>     ---------------------------------------------------------------=
-------
> >>>>>     COMMENT:
> >>>>>
> >>>>> ------------------------------------------------------------------
> >>>>> ----
> >>>>>
> >>>>>     Section 12.1:
> >>>>>     "New Assignments (and potential deprecation) to Power State Set=
s
> >>>>>              shall be administered by IANA and the guidelines and
> procedures
> >>>>>              are specified in [EMAN-FMWK], and will, as a consequen=
ce, the
> >>>>>              IANAPowerStateSet Textual Convention should be updated=
."
> >>>>>
> >>>>>     Not sure what this sentence means.
> >>>>     Good catch.
> >>>>     NEW:
> >>>>
> >>>>              "New Assignments (and potential deprecation) to Power S=
tate
> Sets
> >>>>              shall be administered by IANA and the guidelines and
> procedures
> >>>>              are specified in [EMAN-FMWK], and will, as a consequenc=
e,
> update the
> >>>>              IANAPowerStateSet Textual Convention."
> >>>>
> >>>>
> >>>>     Regards, Benoit (as a document author)
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> _______________________________________________
> >>>> 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
> >>
>=20
> _______________________________________________
> MIB-DOCTORS mailing list
> MIB-DOCTORS@ietf.org
> https://www.ietf.org/mailman/listinfo/mib-doctors


From nobody Thu Jul 10 07:13:17 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 5B2B01B291A for <mib-doctors@ietfa.amsl.com>; Thu, 10 Jul 2014 07:13:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.152
X-Spam-Level: 
X-Spam-Status: No, score=-15.152 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] 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 2JHuTzKurf5B for <mib-doctors@ietfa.amsl.com>; Thu, 10 Jul 2014 07:13:12 -0700 (PDT)
Received: from aer-iport-4.cisco.com (aer-iport-4.cisco.com [173.38.203.54]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5F92D1B2918 for <mib-doctors@ietf.org>; Thu, 10 Jul 2014 07:13:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=11419; q=dns/txt; s=iport; t=1405001591; x=1406211191; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=kpg9Vtqilyte3Beu8HYPRRfnN5QYuqadeTEl6dJJKNI=; b=iBUZKlN6Me/yUQEixcPXUyfDBnoYlCaErd77G2RRAqFh3m4X/7P0Vphj DnVEL43ztntgSu6Bu6Ooal/DoapVDXkZAbeZCSuUo1zqFlz5V2R6bETbx kLuksxglgs8yB/iA1MRu7SrrXJANVkIt6tfC7WfkqSOWiY5K4QvrT76UW k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AnYLABKevlOtJssW/2dsb2JhbABZg2C/fAwJhzcBgSF1hAMBAQEDAQEBATU2CgEFBwQLEQMBAQEBCRYIBwkDAgECARUfCQgGAQwBBQIBAQUSiB8IDcdvF40JgVkRAQIsIgcGhD0BBJZmhBqBSIVHjQaDRTsvgQs
X-IronPort-AV: E=Sophos;i="5.01,638,1400025600"; d="scan'208";a="103022704"
Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP; 10 Jul 2014 14:13:09 +0000
Received: from [10.60.67.84] (ams-bclaise-8913.cisco.com [10.60.67.84]) by aer-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id s6AED8VA015245; Thu, 10 Jul 2014 14:13:09 GMT
Message-ID: <53BE9F74.9080705@cisco.com>
Date: Thu, 10 Jul 2014 16:13:08 +0200
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>, "Bert Wijnen (IETF)" <bertietf@bwijnen.net>, "MIB Doctors (E-mail)" <mib-doctors@ietf.org>
References: <CFE17DDA.458C3%alissa@cooperw.in> <53BC5081.6090809@cisco.com> <53BD6690.2040102@cisco.com> <53BE3D7E.2090302@bwijnen.net> <9904FB1B0159DA42B0B887B7FA8119CA5C83CC03@AZ-FFEXMB04.global.avaya.com>
In-Reply-To: <9904FB1B0159DA42B0B887B7FA8119CA5C83CC03@AZ-FFEXMB04.global.avaya.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/j87PuJhTiLKyu1iZkZj8mrmj5kM
Cc: Adrian Farrel <adrian@olddog.co.uk>, 'Alissa Cooper' <alissa@cooperw.in>, sec-ads@tools.ietf.org
Subject: Re: [MIB-DOCTORS] Change the boilerplate - Alissa's DISCUSS
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, 10 Jul 2014 14:13:14 -0000

Dear all,

The email below refers to Alissa's DISCUSS
See 
http://datatracker.ietf.org/doc/draft-ietf-eman-energy-monitoring-mib/ballot/#alissa-cooper

Alissa refers to this sentence in the boilerplate at 
http://trac.tools.ietf.org/area/ops/trac/wiki/mib-security

         Implementations SHOULD provide the security features described 
by the
         SNMPv3 framework (see [RFC3410]), and implementations claiming 
compliance
         to the SNMPv3 standard MUST include full support for 
authentication and
         privacy via the User-based Security Model (USM) [RFC3414] with 
the AES
         cipher algorithm [RFC3826].

 From the discussion (Dan andBert's feedback, on top of mine) , it seems 
that there are valid reasons to keep a SHOULD here in the generic 
boilerplate.

So what next?
- Should we justify the reasons in the boiler plate
- Should we  give some freedom in the boilerplate?

         Implementations SHOULD provide the security features described 
by the
         SNMPv3 framework (see [RFC3410]), and implementations claiming 
compliance
         to the SNMPv3 standard MUST include full support for 
authentication and
         privacy via the User-based Security Model (USM) [RFC3414] with 
the AES
         cipher algorithm [RFC3826].

         <if there are use cases where a MUST is required, described 
them here>

   Now, I hope it will not be abused by Security ADs, requesting a MUST 
for every single MIB module.
- Something else?
- Stop writing MIB modules :-)

Regards, Benoit


> That is what I remember as well. I inherited the boilerplate text from Bert, and during my tenure as AD we had at least one round of text revision (maybe two?). AFAICT this part did not change for the reasons described by Bert. Another reason may have been that 3410 describes a number of security features, each of them may use different cryptographic algorithms, and not all are mandatory to implement (and of course to deploy) in order to obtain a secure solution.
>
> Regards,
>
> Dan
>
>
>> -----Original Message-----
>> From: MIB-DOCTORS [mailto:mib-doctors-bounces@ietf.org] On Behalf Of
>> Bert Wijnen (IETF)
>> Sent: Thursday, July 10, 2014 10:15 AM
>> To: Benoit Claise; MIB Doctors (E-mail)
>> Cc: Adrian Farrel; 'Alissa Cooper'
>> Subject: Re: [MIB-DOCTORS] Change the boilerplate
>>
>> it is always interesting to see that when we get new ADs that we must
>> rediscuss this whole topic.
>>
>> But yes, there are/were implementations/deployments where one uses
>> dedicated (secure) networks for the network management systems, and so
>> that would work under a SHOULD.
>>
>> I do not recall if that was/is the only reason why we agreed on a SHOULD
>> instead of MUST.
>>
>> Bert
>>
>> On 09/07/14 17:58, Benoit Claise wrote:
>>> MIB doctors,
>>>
>>> Let me focus the discussion a little bit.
>>> Alissa refers to this sentence in the boilerplate at
>>> http://trac.tools.ietf.org/area/ops/trac/wiki/mib-security
>>>
>>>          Implementations SHOULD provide the security features described by
>> the
>>>          SNMPv3 framework (see [RFC3410]), and implementations claiming
>> compliance
>>>          to the SNMPv3 standard MUST include full support for authentication
>> and
>>>          privacy via the User-based Security Model (USM) [RFC3414] with the
>> AES
>>>          cipher algorithm [RFC3826].
>>>
>>>
>>> Alissa's feedback is:
>>>
>>>      It is a little disconcerting that use of SNMPv3 is provided as a SHOULD-
>> level requirement without discussion of deployment
>>>      scenarios and regardless of the sensitivity of the data being made
>> available by any new MIB. For example, the tradeoffs between
>>>      security and utility might be reasonable if (1) I'm using an older SNMP
>> version on my closed home network to monitor my own
>>>      energy use, but not if (2) my ISP is using it to monitor the same thing. The
>> text quoted above basically  endorses unauthorized
>>>      energy monitoring if the provider does not support SNMPv3, whereas it
>> seems like what we would want to be saying is that in
>>>      cases like (2) SNMPv3 is required.
>>>
>>> Can one of the old timers (who was part of the discussion) explain the
>>> SHOULD rational? Personally, I can see two use cases in favor off the
>>> SHOULD: an older SNMP version in a closed network,  or a private data
>>> communication network dedicated to network management with special
>>> protection out of SNMP (like encrypted tunnel)
>>>
>>> Should we now modify this sentence to say?
>>>
>>>      MUST provide the security features described by the
>>>      SNMPv3 framework (see [RFC3410])
>>>
>>> Regards, Benoit
>>>
>>>> MIB doctors,
>>>>
>>>> It seems that the "Security Guidelines for IETF MIB modules" receives
>> comment for each MIB module submitted to the IESG.
>>>> Is it time to modify it, or are we redoing the same discussions over and
>> over?
>>>> Regards, Benoit
>>>>
>>>>
>>>> -------- Original Message --------
>>>> Subject: 	Re: Alissa Cooper's Discuss on draft-ietf-eman-energy-
>> monitoring-mib-12: (with DISCUSS and COMMENT)
>>>> Date: 	Tue, 8 Jul 2014 13:02:50 -0700
>>>> From: 	Alissa Cooper <alissa@cooperw.in>
>>>> To: 	Benoit Claise <bclaise@cisco.com>, The IESG <iesg@ietf.org>
>>>> CC: 	<draft-ietf-eman-energy-monitoring-mib@tools.ietf.org>, <eman-
>> chairs@tools.ietf.org>
>>>>
>>>>
>>>> Hi Benoit,
>>>>
>>>> On 7/8/14, 1:44 AM, "Benoit Claise" <bclaise@cisco.com
>> <mailto:bclaise@cisco.com>> wrote:
>>>>      Hi Alissa,
>>>>
>>>>      Thanks for your review.
>>>>>      Alissa Cooper has entered the following ballot position for
>>>>>      draft-ietf-eman-energy-monitoring-mib-12: Discuss
>>>>>
>>>>>      When responding, please keep the subject line intact and reply to all
>>>>>      email addresses included in the To and CC lines. (Feel free to cut this
>>>>>      introductory paragraph, however.)
>>>>>
>>>>>
>>>>>      Please refer tohttp://www.ietf.org/iesg/statement/discuss-
>> criteria.html
>>>>>      for more information about IESG DISCUSS and COMMENT positions.
>>>>>
>>>>>
>>>>>      The document, along with other ballot positions, can be found here:
>>>>>
>>>>> http://datatracker.ietf.org/doc/draft-ietf-eman-energy-monitoring-mi
>>>>> b/
>>>>>
>>>>>
>>>>>
>>>>>      ----------------------------------------------------------------------
>>>>>      DISCUSS:
>>>>>
>>>>> --------------------------------------------------------------------
>>>>> --
>>>>>
>>>>>      Section 11 is missing a discussion of the privacy considerations of
>>>>>      energy and power monitoring. I would suggest something along the
>> lines of
>>>>>      the following:
>>>>>
>>>>>      "In certain situations, energy and power monitoring can reveal
>> sensitive
>>>>>      information about individuals' activities and habits. Implementors of
>>>>>      this specification should use appropriate privacy protections as
>>>>>      discussed in Section 9 of RFC 6988 and monitoring of individuals and
>>>>>      homes should only occur with proper authorization."
>>>>      Regarding your first sentence, I propose the following text, which would
>> be in line with Security Guidelines for IETF MIB
>>>>      modules at
>>>> http://trac.tools.ietf.org/area/ops/trac/wiki/mib-security
>>>>
>>>>          Some of the readable objects in this MIB module (i.e., objects with a
>>>>          MAX-ACCESS other than not-accessible) may be considered sensitive
>> or
>>>>          vulnerable in some network environments.  It is thus important to
>>>>          control even GET and/or NOTIFY access to these objects and possibly
>>>>          to even encrypt the values of these objects when sending them over
>>>>          the network via SNMP.  These are the tables and objects and their
>>>>          sensitivity/vulnerability:
>>>>
>>>>          Access to the content of the eoPowerStateTable, eoEnergyTable, and
>>>>          eoACPwrAttributesTable MIB tables can reveal sensitive
>>>>          information about individuals' activities and habits
>>>>
>>>> Sounds good to me.
>>>>
>>>>
>>>>      Since this document is essentially a MIB module, your last
>>>> sentence is covered by
>>>>
>>>>               implementations
>>>>               claiming compliance to the SNMPv3 standard MUST include full
>>>>               support for authentication and privacy via the User-based
>>>>               Security Model (USM) [RFC3414
>> <http://tools.ietf.org/html/rfc3414>] with the AES cipher algorithm
>>>>               [RFC3826  <http://tools.ietf.org/html/rfc3826>].
>>>>
>>>> RFC 6988 notes the need for privacy protections for stored data,
>>>> which the above text does not speak to, so I still think a reference to RFC
>> 6988 would add value here.
>>>> It is a little disconcerting that use of SNMPv3 is provided as a
>>>> SHOULD-level requirement without discussion of deployment scenarios
>>>> and regardless of the sensitivity of the data being made available by
>>>> any new MIB. For example, the tradeoffs between security and utility
>>>> might be reasonable if (1) I'm using an older SNMP version on my
>>>> closed home network to monitor my own energy use, but not if (2) my
>>>> ISP is using it to monitor the same thing. The text quoted above
>>>> basically  endorses unauthorized energy monitoring if the provider
>>>> does not support SNMPv3, whereas it seems like what we would want to
>>>> be saying is that in cases like
>>>> (2) SNMPv3 is required.
>>>>
>>>> I understand that this is basically boilerplate language for MIB docs, so I'm
>> not sure what can be done, but it seems unfortunate.
>>>> Alissa
>>>>
>>>>
>>>>
>>>>>      ----------------------------------------------------------------------
>>>>>      COMMENT:
>>>>>
>>>>> --------------------------------------------------------------------
>>>>> --
>>>>>
>>>>>      Section 12.1:
>>>>>      "New Assignments (and potential deprecation) to Power State Sets
>>>>>               shall be administered by IANA and the guidelines and procedures
>>>>>               are specified in [EMAN-FMWK], and will, as a consequence, the
>>>>>               IANAPowerStateSet Textual Convention should be updated."
>>>>>
>>>>>      Not sure what this sentence means.
>>>>      Good catch.
>>>>      NEW:
>>>>
>>>>               "New Assignments (and potential deprecation) to Power State Sets
>>>>               shall be administered by IANA and the guidelines and procedures
>>>>               are specified in [EMAN-FMWK], and will, as a consequence, update
>> the
>>>>               IANAPowerStateSet Textual Convention."
>>>>
>>>>
>>>>      Regards, Benoit (as a document author)
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> 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
> .
>


From nobody Thu Jul 10 07:43:58 2014
Return-Path: <kathleen.moriarty.ietf@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 F30E61B2920 for <mib-doctors@ietfa.amsl.com>; Thu, 10 Jul 2014 07:22:23 -0700 (PDT)
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, FREEMAIL_FROM=0.001, HTML_MESSAGE=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 SV6E2HJcrxh4 for <mib-doctors@ietfa.amsl.com>; Thu, 10 Jul 2014 07:22:20 -0700 (PDT)
Received: from mail-la0-x22a.google.com (mail-la0-x22a.google.com [IPv6:2a00:1450:4010:c03::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E7FF91B2925 for <mib-doctors@ietf.org>; Thu, 10 Jul 2014 07:22:18 -0700 (PDT)
Received: by mail-la0-f42.google.com with SMTP id pn19so6278871lab.1 for <mib-doctors@ietf.org>; Thu, 10 Jul 2014 07:22:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=9cF2RuupmctsOi7KkzkAGQB6bU1WAiem0V1yHMGvWsA=; b=dyO/ly18Yc0DPzRsos+sLx6VosZycJ0vLwOXTGFRhZyPXmpqu8nWy0g2wLU/ReLNq5 vMtmPdOeoZus87HZux4pykNGK1nWDOqWe86ZbQscx9v9TLtkAQ+KoH+IfKNm06rMLmg5 8Cn78GFUIJ9kR4Ey2jQa0kizTO2glg3idjJ2NTd6TKGnmeUn94E9Kwki7beblIYu2BE+ /YXgqfb0d2fHZgD3eOYMaxvL3tsS2Mv+MM8kRK1/o+hA/O77dOCsEJ8XnXj227yHvYX0 62xtnL4212Uj5v9e0PADc+r21LYerkN1EVIeR3qLpkpiz1LpFqpWJorGNtLqtWSTt16V 48RQ==
MIME-Version: 1.0
X-Received: by 10.112.151.237 with SMTP id ut13mr144021lbb.104.1405002137213;  Thu, 10 Jul 2014 07:22:17 -0700 (PDT)
Received: by 10.112.253.198 with HTTP; Thu, 10 Jul 2014 07:22:17 -0700 (PDT)
In-Reply-To: <9904FB1B0159DA42B0B887B7FA8119CA5C83D043@AZ-FFEXMB04.global.avaya.com>
References: <CFE17DDA.458C3%alissa@cooperw.in> <53BC5081.6090809@cisco.com> <53BD6690.2040102@cisco.com> <53BE3D7E.2090302@bwijnen.net> <35D0B6EE-BEC2-44EB-869B-CBE462FE3CAB@lucidvision.com> <53BE9A98.8020805@cisco.com> <9904FB1B0159DA42B0B887B7FA8119CA5C83D043@AZ-FFEXMB04.global.avaya.com>
Date: Thu, 10 Jul 2014 10:22:17 -0400
Message-ID: <CAHbuEH5z_z5-mtW1J6hECduZ+9i6aemO_OBgsEsremdRttuGLQ@mail.gmail.com>
From: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
Content-Type: multipart/alternative; boundary=047d7b87461a4c1fc704fdd78d4d
Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/5zqrTEFTug9JySs_BRY84Cdoe8s
X-Mailman-Approved-At: Thu, 10 Jul 2014 07:43:57 -0700
Cc: "MIB Doctors \(E-mail\)" <mib-doctors@ietf.org>, Alissa Cooper <alissa@cooperw.in>, "sec-ads@tools.ietf.org" <sec-ads@tools.ietf.org>, Farrel Adrian <adrian@olddog.co.uk>
Subject: Re: [MIB-DOCTORS] Change the boilerplate - Kathleen'DISCUSS point 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: Thu, 10 Jul 2014 14:22:24 -0000

--047d7b87461a4c1fc704fdd78d4d
Content-Type: text/plain; charset=UTF-8

On Thu, Jul 10, 2014 at 9:56 AM, Romascanu, Dan (Dan) <dromasca@avaya.com>
wrote:

> I do not know exactly what 'cyber physical devices' means. I think that
> you mean 'devices connected to the network'. Otherwise, looks fine to me.
>

I think I'm okay with 'devices connected to the network'.  Normally I would
agree to nix the 'cyber' in cyber physical, but it is the term used for all
of the stuff related to industrial control systems that are moving into the
networking space.  It lumps in the IoT devices, includes energy and other
industrial control systems.  It's the term being used to cover that space,
industrial control system doesn't go far enough.  Correct me if I am wrong
here, but I believe that is the right term that the industry will
understand.  But I guess if you guys have trouble with it, others not in
that space will too.

Thanks,
Kathleen

>
> Regards,
>
> Dan
>
>
> > -----Original Message-----
> > From: MIB-DOCTORS [mailto:mib-doctors-bounces@ietf.org] On Behalf Of
> > Benoit Claise
> > Sent: Thursday, July 10, 2014 4:52 PM
> > To: Thomas D. Nadeau; Bert Wijnen (IETF)
> > Cc: MIB Doctors (E-mail); Alissa Cooper; sec-ads@tools.ietf.org; Farrel
> Adrian
> > Subject: Re: [MIB-DOCTORS] Change the boilerplate - Kathleen'DISCUSS
> > point 2
> >
> > Dear all,
> >
> > Let's try to address one point at a time, and get closure one by one.
> > https://datatracker.ietf.org/doc/draft-ietf-eman-energy-aware-
> > mib/ballot/#kathleen-moriarty
> >
> > Kathleen proposes:
> > OLD:
> >
> >     "The
> >     support for SET operations in a non-secure environment without proper
> >     protection can have a negative effect on network operations."
> >
> > NEW:
> >
> >     "The
> >     support for SET operations in a non-secure environment without proper
> >     protection can have a negative effect on network operations or leave
> >     cyber physical devices used by individuals, homes, and business
> >     vulnerable to attack."
> >
> >
> > I believe this new proposal makes sense. Does anybody object?
> >
> > Regards, Benoit
> >
> > > On Jul 10, 2014:3:15 AM, at 3:15 AM, Bert Wijnen (IETF)
> > <bertietf@bwijnen.net> wrote:
> > >
> > >> it is always interesting to see that when we get new ADs that we must
> > rediscuss this whole topic.
> > >     This is precisely one of the things that is broken about the IETF
> these
> > days, if you ask me: the re-re-re-discussion of topics at the 11:59th
> hour of a
> > document's progress through the gauntlet.
> > >
> > >> But yes, there are/were implementations/deployments where one uses
> > >> dedicated (secure) networks for the network management systems, and
> > so that would work under a SHOULD.
> > >     I agree. Not all network operators use a secure management
> > network, but many do.
> > >
> > >> I do not recall if that was/is the only reason why we agreed on a
> SHOULD
> > instead of MUST.
> > >     I don't think you can do a MUST here; not everyone uses v3 - in
> fact, I
> > think if you poll implementations you'll find VERY FEW using v3.
> > >
> > >     --Tom
> > >
> > >
> > >
> > >> Bert
> > >>
> > >> On 09/07/14 17:58, Benoit Claise wrote:
> > >>> MIB doctors,
> > >>>
> > >>> Let me focus the discussion a little bit.
> > >>> Alissa refers to this sentence in the boilerplate at
> > >>> http://trac.tools.ietf.org/area/ops/trac/wiki/mib-security
> > >>>
> > >>>         Implementations SHOULD provide the security features
> described
> > by the
> > >>>         SNMPv3 framework (see [RFC3410]), and implementations
> claiming
> > compliance
> > >>>         to the SNMPv3 standard MUST include full support for
> > authentication and
> > >>>         privacy via the User-based Security Model (USM) [RFC3414]
> with the
> > AES
> > >>>         cipher algorithm [RFC3826].
> > >>>
> > >>>
> > >>> Alissa's feedback is:
> > >>>
> > >>>     It is a little disconcerting that use of SNMPv3 is provided as a
> SHOULD-
> > level requirement without discussion of deployment
> > >>>     scenarios and regardless of the sensitivity of the data being
> made
> > available by any new MIB. For example, the tradeoffs between
> > >>>     security and utility might be reasonable if (1) I'm using an
> older SNMP
> > version on my closed home network to monitor my own
> > >>>     energy use, but not if (2) my ISP is using it to monitor the
> same thing.
> > The text quoted above basically  endorses unauthorized
> > >>>     energy monitoring if the provider does not support SNMPv3,
> whereas
> > it seems like what we would want to be saying is that in
> > >>>     cases like (2) SNMPv3 is required.
> > >>>
> > >>> Can one of the old timers (who was part of the discussion) explain
> > >>> the SHOULD rational? Personally, I can see two use cases in favor
> > >>> off the SHOULD: an older SNMP version in a closed network,  or a
> > >>> private data communication network dedicated to network
> > management
> > >>> with special protection out of SNMP (like encrypted tunnel)
> > >>>
> > >>> Should we now modify this sentence to say?
> > >>>
> > >>>     MUST provide the security features described by the
> > >>>     SNMPv3 framework (see [RFC3410])
> > >>>
> > >>> Regards, Benoit
> > >>>
> > >>>> MIB doctors,
> > >>>>
> > >>>> It seems that the "Security Guidelines for IETF MIB modules"
> receives
> > comment for each MIB module submitted to the IESG.
> > >>>> Is it time to modify it, or are we redoing the same discussions
> over and
> > over?
> > >>>>
> > >>>> Regards, Benoit
> > >>>>
> > >>>>
> > >>>> -------- Original Message --------
> > >>>> Subject:         Re: Alissa Cooper's Discuss on
> draft-ietf-eman-energy-
> > monitoring-mib-12: (with DISCUSS and COMMENT)
> > >>>> Date:    Tue, 8 Jul 2014 13:02:50 -0700
> > >>>> From:    Alissa Cooper <alissa@cooperw.in>
> > >>>> To:      Benoit Claise <bclaise@cisco.com>, The IESG <iesg@ietf.org
> >
> > >>>> CC:      <draft-ietf-eman-energy-monitoring-mib@tools.ietf.org>,
> > <eman-chairs@tools.ietf.org>
> > >>>>
> > >>>>
> > >>>>
> > >>>> Hi Benoit,
> > >>>>
> > >>>> On 7/8/14, 1:44 AM, "Benoit Claise" <bclaise@cisco.com
> > <mailto:bclaise@cisco.com>> wrote:
> > >>>>
> > >>>>     Hi Alissa,
> > >>>>
> > >>>>     Thanks for your review.
> > >>>>>     Alissa Cooper has entered the following ballot position for
> > >>>>>     draft-ietf-eman-energy-monitoring-mib-12: Discuss
> > >>>>>
> > >>>>>     When responding, please keep the subject line intact and reply
> to
> > all
> > >>>>>     email addresses included in the To and CC lines. (Feel free to
> cut this
> > >>>>>     introductory paragraph, however.)
> > >>>>>
> > >>>>>
> > >>>>>     Please refer tohttp://www.ietf.org/iesg/statement/discuss-
> > criteria.html
> > >>>>>     for more information about IESG DISCUSS and COMMENT positions.
> > >>>>>
> > >>>>>
> > >>>>>     The document, along with other ballot positions, can be found
> here:
> > >>>>>
> > >>>>> http://datatracker.ietf.org/doc/draft-ietf-eman-energy-monitoring-
> > >>>>> mib/
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>>
> ----------------------------------------------------------------------
> > >>>>>     DISCUSS:
> > >>>>>
> > >>>>> ------------------------------------------------------------------
> > >>>>> ----
> > >>>>>
> > >>>>>     Section 11 is missing a discussion of the privacy
> considerations of
> > >>>>>     energy and power monitoring. I would suggest something along
> the
> > lines of
> > >>>>>     the following:
> > >>>>>
> > >>>>>     "In certain situations, energy and power monitoring can reveal
> > sensitive
> > >>>>>     information about individuals' activities and habits.
> Implementors of
> > >>>>>     this specification should use appropriate privacy protections
> as
> > >>>>>     discussed in Section 9 of RFC 6988 and monitoring of
> individuals and
> > >>>>>     homes should only occur with proper authorization."
> > >>>>     Regarding your first sentence, I propose the following text,
> which
> > would be in line with Security Guidelines for IETF MIB
> > >>>>     modules at
> > >>>> http://trac.tools.ietf.org/area/ops/trac/wiki/mib-security
> > >>>>
> > >>>>         Some of the readable objects in this MIB module (i.e.,
> objects with
> > a
> > >>>>         MAX-ACCESS other than not-accessible) may be considered
> > sensitive or
> > >>>>         vulnerable in some network environments.  It is thus
> important to
> > >>>>         control even GET and/or NOTIFY access to these objects and
> > possibly
> > >>>>         to even encrypt the values of these objects when sending
> them
> > over
> > >>>>         the network via SNMP.  These are the tables and objects and
> their
> > >>>>         sensitivity/vulnerability:
> > >>>>
> > >>>>         Access to the content of the eoPowerStateTable,
> eoEnergyTable,
> > and
> > >>>>         eoACPwrAttributesTable MIB tables can reveal sensitive
> > >>>>         information about individuals' activities and habits
> > >>>>
> > >>>> Sounds good to me.
> > >>>>
> > >>>>
> > >>>>     Since this document is essentially a MIB module, your last
> > >>>> sentence is covered by
> > >>>>
> > >>>>              implementations
> > >>>>              claiming compliance to the SNMPv3 standard MUST
> include full
> > >>>>              support for authentication and privacy via the
> User-based
> > >>>>              Security Model (USM) [RFC3414
> > <http://tools.ietf.org/html/rfc3414>] with the AES cipher algorithm
> > >>>>              [RFC3826  <http://tools.ietf.org/html/rfc3826>].
> > >>>>
> > >>>> RFC 6988 notes the need for privacy protections for stored data,
> > >>>> which the above text does not speak to, so I still think a
> reference to
> > RFC 6988 would add value here.
> > >>>>
> > >>>> It is a little disconcerting that use of SNMPv3 is provided as a
> > >>>> SHOULD-level requirement without discussion of deployment
> > scenarios
> > >>>> and regardless of the sensitivity of the data being made available
> > >>>> by any new MIB. For example, the tradeoffs between security and
> > >>>> utility might be reasonable if (1) I'm using an older SNMP version
> > >>>> on my closed home network to monitor my own energy use, but not if
> > >>>> (2) my ISP is using it to monitor the same thing. The text quoted
> > >>>> above basically  endorses unauthorized energy monitoring if the
> > >>>> provider does not support SNMPv3, whereas it seems like what we
> > >>>> would want to be saying is that in cases like
> > >>>> (2) SNMPv3 is required.
> > >>>>
> > >>>> I understand that this is basically boilerplate language for MIB
> docs, so
> > I'm not sure what can be done, but it seems unfortunate.
> > >>>>
> > >>>> Alissa
> > >>>>
> > >>>>
> > >>>>
> > >>>>>
> ----------------------------------------------------------------------
> > >>>>>     COMMENT:
> > >>>>>
> > >>>>> ------------------------------------------------------------------
> > >>>>> ----
> > >>>>>
> > >>>>>     Section 12.1:
> > >>>>>     "New Assignments (and potential deprecation) to Power State
> Sets
> > >>>>>              shall be administered by IANA and the guidelines and
> > procedures
> > >>>>>              are specified in [EMAN-FMWK], and will, as a
> consequence, the
> > >>>>>              IANAPowerStateSet Textual Convention should be
> updated."
> > >>>>>
> > >>>>>     Not sure what this sentence means.
> > >>>>     Good catch.
> > >>>>     NEW:
> > >>>>
> > >>>>              "New Assignments (and potential deprecation) to Power
> State
> > Sets
> > >>>>              shall be administered by IANA and the guidelines and
> > procedures
> > >>>>              are specified in [EMAN-FMWK], and will, as a
> consequence,
> > update the
> > >>>>              IANAPowerStateSet Textual Convention."
> > >>>>
> > >>>>
> > >>>>     Regards, Benoit (as a document author)
> > >>>>
> > >>>>
> > >>>>
> > >>>>
> > >>>>
> > >>>> _______________________________________________
> > >>>> 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
>



-- 

Best regards,
Kathleen

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On Thu, Jul 10, 2014 at 9:56 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">I do not know exactly what &#39;cyber physic=
al devices&#39; means. I think that you mean &#39;devices connected to the =
network&#39;. Otherwise, looks fine to me.<br>
</blockquote><div><br></div><div>I think I&#39;m okay with &#39;devices con=
nected to the network&#39;. =C2=A0Normally I would agree to nix the &#39;cy=
ber&#39; in cyber physical, but it is the term used for all of the stuff re=
lated to industrial control systems that are moving into the networking spa=
ce. =C2=A0It lumps in the IoT devices, includes energy and other industrial=
 control systems. =C2=A0It&#39;s the term being used to cover that space, i=
ndustrial control system doesn&#39;t go far enough. =C2=A0Correct me if I a=
m wrong here, but I believe that is the right term that the industry will u=
nderstand. =C2=A0But I guess if you guys have trouble with it, others not i=
n that space will too.</div>
<div><br></div><div>Thanks,</div><div>Kathleen</div><blockquote class=3D"gm=
ail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-le=
ft:1ex">
<br>
Regards,<br>
<br>
Dan<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
<br>
&gt; -----Original Message-----<br>
&gt; From: MIB-DOCTORS [mailto:<a href=3D"mailto:mib-doctors-bounces@ietf.o=
rg">mib-doctors-bounces@ietf.org</a>] On Behalf Of<br>
&gt; Benoit Claise<br>
&gt; Sent: Thursday, July 10, 2014 4:52 PM<br>
&gt; To: Thomas D. Nadeau; Bert Wijnen (IETF)<br>
&gt; Cc: MIB Doctors (E-mail); Alissa Cooper; <a href=3D"mailto:sec-ads@too=
ls.ietf.org">sec-ads@tools.ietf.org</a>; Farrel Adrian<br>
&gt; Subject: Re: [MIB-DOCTORS] Change the boilerplate - Kathleen&#39;DISCU=
SS<br>
&gt; point 2<br>
&gt;<br>
&gt; Dear all,<br>
&gt;<br>
&gt; Let&#39;s try to address one point at a time, and get closure one by o=
ne.<br>
&gt; <a href=3D"https://datatracker.ietf.org/doc/draft-ietf-eman-energy-awa=
re-" target=3D"_blank">https://datatracker.ietf.org/doc/draft-ietf-eman-ene=
rgy-aware-</a><br>
&gt; mib/ballot/#kathleen-moriarty<br>
&gt;<br>
&gt; Kathleen proposes:<br>
&gt; OLD:<br>
&gt;<br>
&gt; =C2=A0 =C2=A0 &quot;The<br>
&gt; =C2=A0 =C2=A0 support for SET operations in a non-secure environment w=
ithout proper<br>
&gt; =C2=A0 =C2=A0 protection can have a negative effect on network operati=
ons.&quot;<br>
&gt;<br>
&gt; NEW:<br>
&gt;<br>
&gt; =C2=A0 =C2=A0 &quot;The<br>
&gt; =C2=A0 =C2=A0 support for SET operations in a non-secure environment w=
ithout proper<br>
&gt; =C2=A0 =C2=A0 protection can have a negative effect on network operati=
ons or leave<br>
&gt; =C2=A0 =C2=A0 cyber physical devices used by individuals, homes, and b=
usiness<br>
&gt; =C2=A0 =C2=A0 vulnerable to attack.&quot;<br>
&gt;<br>
&gt;<br>
&gt; I believe this new proposal makes sense. Does anybody object?<br>
&gt;<br>
&gt; Regards, Benoit<br>
&gt;<br>
&gt; &gt; On Jul 10, 2014:3:15 AM, at 3:15 AM, Bert Wijnen (IETF)<br>
&gt; &lt;<a href=3D"mailto:bertietf@bwijnen.net">bertietf@bwijnen.net</a>&g=
t; wrote:<br>
&gt; &gt;<br>
&gt; &gt;&gt; it is always interesting to see that when we get new ADs that=
 we must<br>
&gt; rediscuss this whole topic.<br>
&gt; &gt; =C2=A0 =C2=A0 This is precisely one of the things that is broken =
about the IETF these<br>
&gt; days, if you ask me: the re-re-re-discussion of topics at the 11:59th =
hour of a<br>
&gt; document&#39;s progress through the gauntlet.<br>
&gt; &gt;<br>
&gt; &gt;&gt; But yes, there are/were implementations/deployments where one=
 uses<br>
&gt; &gt;&gt; dedicated (secure) networks for the network management system=
s, and<br>
&gt; so that would work under a SHOULD.<br>
&gt; &gt; =C2=A0 =C2=A0 I agree. Not all network operators use a secure man=
agement<br>
&gt; network, but many do.<br>
&gt; &gt;<br>
&gt; &gt;&gt; I do not recall if that was/is the only reason why we agreed =
on a SHOULD<br>
&gt; instead of MUST.<br>
&gt; &gt; =C2=A0 =C2=A0 I don&#39;t think you can do a MUST here; not every=
one uses v3 - in fact, I<br>
&gt; think if you poll implementations you&#39;ll find VERY FEW using v3.<b=
r>
&gt; &gt;<br>
&gt; &gt; =C2=A0 =C2=A0 --Tom<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;&gt; Bert<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; On 09/07/14 17:58, Benoit Claise wrote:<br>
&gt; &gt;&gt;&gt; MIB doctors,<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt; Let me focus the discussion a little bit.<br>
&gt; &gt;&gt;&gt; Alissa refers to this sentence in the boilerplate at<br>
&gt; &gt;&gt;&gt; <a href=3D"http://trac.tools.ietf.org/area/ops/trac/wiki/=
mib-security" target=3D"_blank">http://trac.tools.ietf.org/area/ops/trac/wi=
ki/mib-security</a><br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 Implementations SHOULD provid=
e the security features described<br>
&gt; by the<br>
&gt; &gt;&gt;&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 SNMPv3 framework (see [RFC341=
0]), and implementations claiming<br>
&gt; compliance<br>
&gt; &gt;&gt;&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 to the SNMPv3 standard MUST i=
nclude full support for<br>
&gt; authentication and<br>
&gt; &gt;&gt;&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 privacy via the User-based Se=
curity Model (USM) [RFC3414] with the<br>
&gt; AES<br>
&gt; &gt;&gt;&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 cipher algorithm [RFC3826].<b=
r>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt; Alissa&#39;s feedback is:<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt; =C2=A0 =C2=A0 It is a little disconcerting that use of SN=
MPv3 is provided as a SHOULD-<br>
&gt; level requirement without discussion of deployment<br>
&gt; &gt;&gt;&gt; =C2=A0 =C2=A0 scenarios and regardless of the sensitivity=
 of the data being made<br>
&gt; available by any new MIB. For example, the tradeoffs between<br>
&gt; &gt;&gt;&gt; =C2=A0 =C2=A0 security and utility might be reasonable if=
 (1) I&#39;m using an older SNMP<br>
&gt; version on my closed home network to monitor my own<br>
&gt; &gt;&gt;&gt; =C2=A0 =C2=A0 energy use, but not if (2) my ISP is using =
it to monitor the same thing.<br>
&gt; The text quoted above basically =C2=A0endorses unauthorized<br>
&gt; &gt;&gt;&gt; =C2=A0 =C2=A0 energy monitoring if the provider does not =
support SNMPv3, whereas<br>
&gt; it seems like what we would want to be saying is that in<br>
&gt; &gt;&gt;&gt; =C2=A0 =C2=A0 cases like (2) SNMPv3 is required.<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt; Can one of the old timers (who was part of the discussion=
) explain<br>
&gt; &gt;&gt;&gt; the SHOULD rational? Personally, I can see two use cases =
in favor<br>
&gt; &gt;&gt;&gt; off the SHOULD: an older SNMP version in a closed network=
, =C2=A0or a<br>
&gt; &gt;&gt;&gt; private data communication network dedicated to network<b=
r>
&gt; management<br>
&gt; &gt;&gt;&gt; with special protection out of SNMP (like encrypted tunne=
l)<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt; Should we now modify this sentence to say?<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt; =C2=A0 =C2=A0 MUST provide the security features describe=
d by the<br>
&gt; &gt;&gt;&gt; =C2=A0 =C2=A0 SNMPv3 framework (see [RFC3410])<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt; Regards, Benoit<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; MIB doctors,<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; It seems that the &quot;Security Guidelines for IETF =
MIB modules&quot; receives<br>
&gt; comment for each MIB module submitted to the IESG.<br>
&gt; &gt;&gt;&gt;&gt; Is it time to modify it, or are we redoing the same d=
iscussions over and<br>
&gt; over?<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; Regards, Benoit<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; -------- Original Message --------<br>
&gt; &gt;&gt;&gt;&gt; Subject: =C2=A0 =C2=A0 =C2=A0 =C2=A0 Re: Alissa Coope=
r&#39;s Discuss on draft-ietf-eman-energy-<br>
&gt; monitoring-mib-12: (with DISCUSS and COMMENT)<br>
&gt; &gt;&gt;&gt;&gt; Date: =C2=A0 =C2=A0Tue, 8 Jul 2014 13:02:50 -0700<br>
&gt; &gt;&gt;&gt;&gt; From: =C2=A0 =C2=A0Alissa Cooper &lt;<a href=3D"mailt=
o:alissa@cooperw.in">alissa@cooperw.in</a>&gt;<br>
&gt; &gt;&gt;&gt;&gt; To: =C2=A0 =C2=A0 =C2=A0Benoit Claise &lt;<a href=3D"=
mailto:bclaise@cisco.com">bclaise@cisco.com</a>&gt;, The IESG &lt;<a href=
=3D"mailto:iesg@ietf.org">iesg@ietf.org</a>&gt;<br>
&gt; &gt;&gt;&gt;&gt; CC: =C2=A0 =C2=A0 =C2=A0&lt;<a href=3D"mailto:draft-i=
etf-eman-energy-monitoring-mib@tools.ietf.org">draft-ietf-eman-energy-monit=
oring-mib@tools.ietf.org</a>&gt;,<br>
&gt; &lt;<a href=3D"mailto:eman-chairs@tools.ietf.org">eman-chairs@tools.ie=
tf.org</a>&gt;<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; Hi Benoit,<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; On 7/8/14, 1:44 AM, &quot;Benoit Claise&quot; &lt;<a =
href=3D"mailto:bclaise@cisco.com">bclaise@cisco.com</a><br>
&gt; &lt;mailto:<a href=3D"mailto:bclaise@cisco.com">bclaise@cisco.com</a>&=
gt;&gt; wrote:<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; =C2=A0 =C2=A0 Hi Alissa,<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; =C2=A0 =C2=A0 Thanks for your review.<br>
&gt; &gt;&gt;&gt;&gt;&gt; =C2=A0 =C2=A0 Alissa Cooper has entered the follo=
wing ballot position for<br>
&gt; &gt;&gt;&gt;&gt;&gt; =C2=A0 =C2=A0 draft-ietf-eman-energy-monitoring-m=
ib-12: Discuss<br>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt; =C2=A0 =C2=A0 When responding, please keep the su=
bject line intact and reply to<br>
&gt; all<br>
&gt; &gt;&gt;&gt;&gt;&gt; =C2=A0 =C2=A0 email addresses included in the To =
and CC lines. (Feel free to cut this<br>
&gt; &gt;&gt;&gt;&gt;&gt; =C2=A0 =C2=A0 introductory paragraph, however.)<b=
r>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt; =C2=A0 =C2=A0 Please refer tohttp://<a href=3D"ht=
tp://www.ietf.org/iesg/statement/discuss-" target=3D"_blank">www.ietf.org/i=
esg/statement/discuss-</a><br>
&gt; criteria.html<br>
&gt; &gt;&gt;&gt;&gt;&gt; =C2=A0 =C2=A0 for more information about IESG DIS=
CUSS and COMMENT positions.<br>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt; =C2=A0 =C2=A0 The document, along with other ball=
ot positions, can be found here:<br>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt; <a href=3D"http://datatracker.ietf.org/doc/draft-=
ietf-eman-energy-monitoring-" target=3D"_blank">http://datatracker.ietf.org=
/doc/draft-ietf-eman-energy-monitoring-</a><br>
&gt; &gt;&gt;&gt;&gt;&gt; mib/<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; =C2=A0 =C2=A0 -----------------------------------=
-----------------------------------<br>
&gt; &gt;&gt;&gt;&gt;&gt; =C2=A0 =C2=A0 DISCUSS:<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;<br>
&gt; &gt;&gt;&gt;&gt;&gt; =C2=A0 =C2=A0 Section 11 is missing a discussion =
of the privacy considerations of<br>
&gt; &gt;&gt;&gt;&gt;&gt; =C2=A0 =C2=A0 energy and power monitoring. I woul=
d suggest something along the<br>
&gt; lines of<br>
&gt; &gt;&gt;&gt;&gt;&gt; =C2=A0 =C2=A0 the following:<br>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt; =C2=A0 =C2=A0 &quot;In certain situations, energy=
 and power monitoring can reveal<br>
&gt; sensitive<br>
&gt; &gt;&gt;&gt;&gt;&gt; =C2=A0 =C2=A0 information about individuals&#39; =
activities and habits. Implementors of<br>
&gt; &gt;&gt;&gt;&gt;&gt; =C2=A0 =C2=A0 this specification should use appro=
priate privacy protections as<br>
&gt; &gt;&gt;&gt;&gt;&gt; =C2=A0 =C2=A0 discussed in Section 9 of RFC 6988 =
and monitoring of individuals and<br>
&gt; &gt;&gt;&gt;&gt;&gt; =C2=A0 =C2=A0 homes should only occur with proper=
 authorization.&quot;<br>
&gt; &gt;&gt;&gt;&gt; =C2=A0 =C2=A0 Regarding your first sentence, I propos=
e the following text, which<br>
&gt; would be in line with Security Guidelines for IETF MIB<br>
&gt; &gt;&gt;&gt;&gt; =C2=A0 =C2=A0 modules at<br>
&gt; &gt;&gt;&gt;&gt; <a href=3D"http://trac.tools.ietf.org/area/ops/trac/w=
iki/mib-security" target=3D"_blank">http://trac.tools.ietf.org/area/ops/tra=
c/wiki/mib-security</a><br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 Some of the readable obje=
cts in this MIB module (i.e., objects with<br>
&gt; a<br>
&gt; &gt;&gt;&gt;&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 MAX-ACCESS other than not=
-accessible) may be considered<br>
&gt; sensitive or<br>
&gt; &gt;&gt;&gt;&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 vulnerable in some networ=
k environments. =C2=A0It is thus important to<br>
&gt; &gt;&gt;&gt;&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 control even GET and/or N=
OTIFY access to these objects and<br>
&gt; possibly<br>
&gt; &gt;&gt;&gt;&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 to even encrypt the value=
s of these objects when sending them<br>
&gt; over<br>
&gt; &gt;&gt;&gt;&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 the network via SNMP. =C2=
=A0These are the tables and objects and their<br>
&gt; &gt;&gt;&gt;&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 sensitivity/vulnerability=
:<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 Access to the content of =
the eoPowerStateTable, eoEnergyTable,<br>
&gt; and<br>
&gt; &gt;&gt;&gt;&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 eoACPwrAttributesTable MI=
B tables can reveal sensitive<br>
&gt; &gt;&gt;&gt;&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 information about individ=
uals&#39; activities and habits<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; Sounds good to me.<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; =C2=A0 =C2=A0 Since this document is essentially a MI=
B module, your last<br>
&gt; &gt;&gt;&gt;&gt; sentence is covered by<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0imple=
mentations<br>
&gt; &gt;&gt;&gt;&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0claim=
ing compliance to the SNMPv3 standard MUST include full<br>
&gt; &gt;&gt;&gt;&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0suppo=
rt for authentication and privacy via the User-based<br>
&gt; &gt;&gt;&gt;&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Secur=
ity Model (USM) [RFC3414<br>
&gt; &lt;<a href=3D"http://tools.ietf.org/html/rfc3414" target=3D"_blank">h=
ttp://tools.ietf.org/html/rfc3414</a>&gt;] with the AES cipher algorithm<br=
>
&gt; &gt;&gt;&gt;&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0[RFC3=
826 =C2=A0&lt;<a href=3D"http://tools.ietf.org/html/rfc3826" target=3D"_bla=
nk">http://tools.ietf.org/html/rfc3826</a>&gt;].<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; RFC 6988 notes the need for privacy protections for s=
tored data,<br>
&gt; &gt;&gt;&gt;&gt; which the above text does not speak to, so I still th=
ink a reference to<br>
&gt; RFC 6988 would add value here.<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; It is a little disconcerting that use of SNMPv3 is pr=
ovided as a<br>
&gt; &gt;&gt;&gt;&gt; SHOULD-level requirement without discussion of deploy=
ment<br>
&gt; scenarios<br>
&gt; &gt;&gt;&gt;&gt; and regardless of the sensitivity of the data being m=
ade available<br>
&gt; &gt;&gt;&gt;&gt; by any new MIB. For example, the tradeoffs between se=
curity and<br>
&gt; &gt;&gt;&gt;&gt; utility might be reasonable if (1) I&#39;m using an o=
lder SNMP version<br>
&gt; &gt;&gt;&gt;&gt; on my closed home network to monitor my own energy us=
e, but not if<br>
&gt; &gt;&gt;&gt;&gt; (2) my ISP is using it to monitor the same thing. The=
 text quoted<br>
&gt; &gt;&gt;&gt;&gt; above basically =C2=A0endorses unauthorized energy mo=
nitoring if the<br>
&gt; &gt;&gt;&gt;&gt; provider does not support SNMPv3, whereas it seems li=
ke what we<br>
&gt; &gt;&gt;&gt;&gt; would want to be saying is that in cases like<br>
&gt; &gt;&gt;&gt;&gt; (2) SNMPv3 is required.<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; I understand that this is basically boilerplate langu=
age for MIB docs, so<br>
&gt; I&#39;m not sure what can be done, but it seems unfortunate.<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; Alissa<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt; =C2=A0 =C2=A0 -----------------------------------=
-----------------------------------<br>
&gt; &gt;&gt;&gt;&gt;&gt; =C2=A0 =C2=A0 COMMENT:<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;<br>
&gt; &gt;&gt;&gt;&gt;&gt; =C2=A0 =C2=A0 Section 12.1:<br>
&gt; &gt;&gt;&gt;&gt;&gt; =C2=A0 =C2=A0 &quot;New Assignments (and potentia=
l deprecation) to Power State Sets<br>
&gt; &gt;&gt;&gt;&gt;&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0s=
hall be administered by IANA and the guidelines and<br>
&gt; procedures<br>
&gt; &gt;&gt;&gt;&gt;&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0a=
re specified in [EMAN-FMWK], and will, as a consequence, the<br>
&gt; &gt;&gt;&gt;&gt;&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0I=
ANAPowerStateSet Textual Convention should be updated.&quot;<br>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt; =C2=A0 =C2=A0 Not sure what this sentence means.<=
br>
&gt; &gt;&gt;&gt;&gt; =C2=A0 =C2=A0 Good catch.<br>
&gt; &gt;&gt;&gt;&gt; =C2=A0 =C2=A0 NEW:<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&quot=
;New Assignments (and potential deprecation) to Power State<br>
&gt; Sets<br>
&gt; &gt;&gt;&gt;&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0shall=
 be administered by IANA and the guidelines and<br>
&gt; procedures<br>
&gt; &gt;&gt;&gt;&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0are s=
pecified in [EMAN-FMWK], and will, as a consequence,<br>
&gt; update the<br>
&gt; &gt;&gt;&gt;&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0IANAP=
owerStateSet Textual Convention.&quot;<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; =C2=A0 =C2=A0 Regards, Benoit (as a document author)<=
br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;<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;&gt;&gt;<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt; _______________________________________________<br>
&gt; &gt;&gt;&gt; MIB-DOCTORS mailing list<br>
&gt; &gt;&gt;&gt; <a href=3D"mailto:MIB-DOCTORS@ietf.org">MIB-DOCTORS@ietf.=
org</a><br>
&gt; &gt;&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/mib-doct=
ors" target=3D"_blank">https://www.ietf.org/mailman/listinfo/mib-doctors</a=
><br>
&gt; &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;<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>
</div></div></blockquote></div><br><br clear=3D"all"><div><br></div>-- <br>=
<div dir=3D"ltr"><br><div>Best regards,</div><div>Kathleen</div></div>
</div></div>

--047d7b87461a4c1fc704fdd78d4d--


From nobody Thu Jul 10 08:09:58 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 850A81A0AB1 for <mib-doctors@ietfa.amsl.com>; Thu, 10 Jul 2014 08:09:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.201
X-Spam-Level: 
X-Spam-Status: No, score=-2.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RP_MATCHES_RCVD=-0.651] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ol5o3FhkmcE8 for <mib-doctors@ietfa.amsl.com>; Thu, 10 Jul 2014 08:09:39 -0700 (PDT)
Received: from atlas3.jacobs-university.de (atlas3.jacobs-university.de [212.201.44.18]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 05EB81A0AB5 for <mib-doctors@ietf.org>; Thu, 10 Jul 2014 08:09:18 -0700 (PDT)
Received: from localhost (demetrius5.irc-it.jacobs-university.de [10.70.0.222]) by atlas3.jacobs-university.de (Postfix) with ESMTP id BC5A8FEE; Thu, 10 Jul 2014 17:09:16 +0200 (CEST)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from atlas3.jacobs-university.de ([10.70.0.220]) by localhost (demetrius5.jacobs-university.de [10.70.0.222]) (amavisd-new, port 10030) with ESMTP id XCJUQMbfWkew; Thu, 10 Jul 2014 17:08:58 +0200 (CEST)
Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hermes.jacobs-university.de", Issuer "Jacobs University CA - G01" (verified OK)) by atlas3.jacobs-university.de (Postfix) with ESMTPS; Thu, 10 Jul 2014 17:09:16 +0200 (CEST)
Received: from localhost (demetrius1.jacobs-university.de [212.201.44.46]) by hermes.jacobs-university.de (Postfix) with ESMTP id 301322002F; Thu, 10 Jul 2014 17:09:16 +0200 (CEST)
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 vA2wSKUJx1pL; Thu, 10 Jul 2014 17:09:15 +0200 (CEST)
Received: from elstar.local (elstar.jacobs.jacobs-university.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id DCFDF20017; Thu, 10 Jul 2014 17:09:14 +0200 (CEST)
Received: by elstar.local (Postfix, from userid 501) id 02F272DD50BD; Thu, 10 Jul 2014 17:09:10 +0200 (CEST)
Date: Thu, 10 Jul 2014 17:09:10 +0200
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: Benoit Claise <bclaise@cisco.com>
Message-ID: <20140710150910.GA90581@elstar.local>
Mail-Followup-To: Benoit Claise <bclaise@cisco.com>, "Thomas D. Nadeau" <tnadeau@lucidvision.com>, "Bert Wijnen (IETF)" <bertietf@bwijnen.net>, "MIB Doctors (E-mail)" <mib-doctors@ietf.org>, Alissa Cooper <alissa@cooperw.in>, sec-ads@tools.ietf.org, Farrel Adrian <adrian@olddog.co.uk>
References: <CFE17DDA.458C3%alissa@cooperw.in> <53BC5081.6090809@cisco.com> <53BD6690.2040102@cisco.com> <53BE3D7E.2090302@bwijnen.net> <35D0B6EE-BEC2-44EB-869B-CBE462FE3CAB@lucidvision.com> <53BE9A98.8020805@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <53BE9A98.8020805@cisco.com>
User-Agent: Mutt/1.4.2.3i
Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/MAaP8bpNpKEuWNNk58v2PBFqRw8
Cc: "MIB Doctors \(E-mail\)" <mib-doctors@ietf.org>, Alissa Cooper <alissa@cooperw.in>, sec-ads@tools.ietf.org, Farrel Adrian <adrian@olddog.co.uk>
Subject: Re: [MIB-DOCTORS] Change the boilerplate - Kathleen'DISCUSS point 2
X-BeenThere: mib-doctors@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
List-Id: MIB Doctors list <mib-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mib-doctors/>
List-Post: <mailto:mib-doctors@ietf.org>
List-Help: <mailto:mib-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Jul 2014 15:09:47 -0000

On Thu, Jul 10, 2014 at 03:52:24PM +0200, Benoit Claise wrote:
> Dear all,
> 
> Let's try to address one point at a time, and get closure one by one.
> https://datatracker.ietf.org/doc/draft-ietf-eman-energy-aware-mib/ballot/#kathleen-moriarty
> 
> Kathleen proposes:
> OLD:
> 
>    "The
>    support for SET operations in a non-secure environment without proper
>    protection can have a negative effect on network operations."
> 
> NEW:
> 
>    "The
>    support for SET operations in a non-secure environment without proper
>    protection can have a negative effect on network operations or leave
>    cyber physical devices used by individuals, homes, and business
>    vulnerable to attack."
> 
> 
> I believe this new proposal makes sense. Does anybody object?

Change to "or leave devices vulnerable to attack". Since we talk about
boilerplate, the text needs to be generic.

/js

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


From nobody Thu Jul 10 08:13: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 DEC8A1A05D1 for <mib-doctors@ietfa.amsl.com>; Thu, 10 Jul 2014 08:13:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.201
X-Spam-Level: 
X-Spam-Status: No, score=-2.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RP_MATCHES_RCVD=-0.651] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JiGsc4kN4OOK for <mib-doctors@ietfa.amsl.com>; Thu, 10 Jul 2014 08:13:45 -0700 (PDT)
Received: from atlas3.jacobs-university.de (atlas3.jacobs-university.de [212.201.44.18]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 67AF01A0ADA for <mib-doctors@ietf.org>; Thu, 10 Jul 2014 08:11:44 -0700 (PDT)
Received: from localhost (demetrius5.irc-it.jacobs-university.de [10.70.0.222]) by atlas3.jacobs-university.de (Postfix) with ESMTP id 2F0EF119C; Thu, 10 Jul 2014 17:11:43 +0200 (CEST)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from atlas3.jacobs-university.de ([10.70.0.220]) by localhost (demetrius5.jacobs-university.de [10.70.0.222]) (amavisd-new, port 10030) with ESMTP id euO87Fel06j1; Thu, 10 Jul 2014 17:11:25 +0200 (CEST)
Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hermes.jacobs-university.de", Issuer "Jacobs University CA - G01" (verified OK)) by atlas3.jacobs-university.de (Postfix) with ESMTPS; Thu, 10 Jul 2014 17:11:42 +0200 (CEST)
Received: from localhost (demetrius2.jacobs-university.de [212.201.44.47]) by hermes.jacobs-university.de (Postfix) with ESMTP id 750B82002F; Thu, 10 Jul 2014 17:11:42 +0200 (CEST)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius2.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id XzLNoysL4We8; Thu, 10 Jul 2014 17:11:41 +0200 (CEST)
Received: from elstar.local (elstar.jacobs.jacobs-university.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id E74D320017; Thu, 10 Jul 2014 17:11:40 +0200 (CEST)
Received: by elstar.local (Postfix, from userid 501) id 997472DD50F0; Thu, 10 Jul 2014 17:11:38 +0200 (CEST)
Date: Thu, 10 Jul 2014 17:11:38 +0200
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: Benoit Claise <bclaise@cisco.com>
Message-ID: <20140710151138.GB90581@elstar.local>
Mail-Followup-To: Benoit Claise <bclaise@cisco.com>, "Romascanu, Dan (Dan)" <dromasca@avaya.com>, "Bert Wijnen (IETF)" <bertietf@bwijnen.net>, "MIB Doctors (E-mail)" <mib-doctors@ietf.org>, Adrian Farrel <adrian@olddog.co.uk>, 'Alissa Cooper' <alissa@cooperw.in>, sec-ads@tools.ietf.org
References: <CFE17DDA.458C3%alissa@cooperw.in> <53BC5081.6090809@cisco.com> <53BD6690.2040102@cisco.com> <53BE3D7E.2090302@bwijnen.net> <9904FB1B0159DA42B0B887B7FA8119CA5C83CC03@AZ-FFEXMB04.global.avaya.com> <53BE9F74.9080705@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <53BE9F74.9080705@cisco.com>
User-Agent: Mutt/1.4.2.3i
Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/LFvvC1gvXuAIhHvrqgU3-OzIMIE
Cc: "MIB Doctors \(E-mail\)" <mib-doctors@ietf.org>, 'Alissa Cooper' <alissa@cooperw.in>, sec-ads@tools.ietf.org, Adrian Farrel <adrian@olddog.co.uk>
Subject: Re: [MIB-DOCTORS] Change the boilerplate - Alissa's DISCUSS
X-BeenThere: mib-doctors@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
List-Id: MIB Doctors list <mib-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mib-doctors/>
List-Post: <mailto:mib-doctors@ietf.org>
List-Help: <mailto:mib-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Jul 2014 15:13:48 -0000

On Thu, Jul 10, 2014 at 04:13:08PM +0200, Benoit Claise wrote:
> Dear all,
> 
> The email below refers to Alissa's DISCUSS
> See 
> http://datatracker.ietf.org/doc/draft-ietf-eman-energy-monitoring-mib/ballot/#alissa-cooper
> 
> Alissa refers to this sentence in the boilerplate at 
> http://trac.tools.ietf.org/area/ops/trac/wiki/mib-security
> 
>         Implementations SHOULD provide the security features described 
> by the
>         SNMPv3 framework (see [RFC3410]), and implementations claiming 
> compliance
>         to the SNMPv3 standard MUST include full support for 
> authentication and
>         privacy via the User-based Security Model (USM) [RFC3414] with 
> the AES
>         cipher algorithm [RFC3826].
> 
> From the discussion (Dan andBert's feedback, on top of mine) , it seems 
> that there are valid reasons to keep a SHOULD here in the generic 
> boilerplate.
> 
> So what next?
> - Should we justify the reasons in the boiler plate
> - Should we  give some freedom in the boilerplate?
> 
>         Implementations SHOULD provide the security features described 
> by the
>         SNMPv3 framework (see [RFC3410]), and implementations claiming 
> compliance
>         to the SNMPv3 standard MUST include full support for 
> authentication and
>         privacy via the User-based Security Model (USM) [RFC3414] with 
> the AES
>         cipher algorithm [RFC3826].
> 
>         <if there are use cases where a MUST is required, described 
> them here>
> 
>   Now, I hope it will not be abused by Security ADs, requesting a MUST 
> for every single MIB module.
> - Something else?
> - Stop writing MIB modules :-)
> 

Do nothing, re-discuss this every other year. ;-)

/js

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


From nobody Thu Jul 10 08:33:11 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 9AAC21A03D7 for <mib-doctors@ietfa.amsl.com>; Thu, 10 Jul 2014 08:33:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.551
X-Spam-Level: 
X-Spam-Status: No, score=-7.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.651] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uZ2FDhsMla4g for <mib-doctors@ietfa.amsl.com>; Thu, 10 Jul 2014 08:33:05 -0700 (PDT)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DD42E1A0A74 for <mib-doctors@ietf.org>; Thu, 10 Jul 2014 08:32:55 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AtcNABCxvlPGmAcV/2dsb2JhbABWA4JqJFJagm+pCQEBAQEBAQaTKAuHNwEZdBZ1hAMBAQEBAxIREUUMAgICAQgNAwEEAQEBAgIGHQMCAgIZFxQBCAgCBAENBQgaiCABDKQWikeZFxcEgSiETohoEQECHRYLEAcGC4JmNoEWBZxIhXCMXYNDbIELOQ
X-IronPort-AV: E=Sophos;i="5.01,638,1400040000"; d="scan'208";a="73320239"
Received: from unknown (HELO co300216-co-erhwest-exch.avaya.com) ([198.152.7.21]) by co300216-co-outbound.net.avaya.com with ESMTP; 10 Jul 2014 11:32:54 -0400
X-OutboundMail_SMTP: 1
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; 10 Jul 2014 11:32:54 -0400
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, 10 Jul 2014 17:32:51 +0200
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: Alissa Cooper <alissa@cooperw.in>, Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>, Benoit Claise <bclaise@cisco.com>
Thread-Topic: [MIB-DOCTORS] Change the boilerplate - Alissa's DISCUSS
Thread-Index: AQHPnEkXEqdvDO0CUU2EqBsaZONmeZuZSGQAgAAEiQCAACISMA==
Date: Thu, 10 Jul 2014 15:32:51 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA5C83D3FD@AZ-FFEXMB04.global.avaya.com>
References: <CFE17DDA.458C3%alissa@cooperw.in> <53BC5081.6090809@cisco.com> <53BD6690.2040102@cisco.com> <53BE3D7E.2090302@bwijnen.net> <9904FB1B0159DA42B0B887B7FA8119CA5C83CC03@AZ-FFEXMB04.global.avaya.com> <53BE9F74.9080705@cisco.com> <20140710151138.GB90581@elstar.local> <CFE3FCE9.45FFF%alissa@cooperw.in>
In-Reply-To: <CFE3FCE9.45FFF%alissa@cooperw.in>
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="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/HgcplLjfpxNztD2QE-36OxZSXhk
Cc: "MIB Doctors \(E-mail\)" <mib-doctors@ietf.org>, "sec-ads@tools.ietf.org" <sec-ads@tools.ietf.org>, Adrian Farrel <adrian@olddog.co.uk>
Subject: Re: [MIB-DOCTORS] Change the boilerplate - Alissa's DISCUSS
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, 10 Jul 2014 15:33:09 -0000

VGhlIHdheSBJIGFsd2F5cyB1bmRlcnN0b29kIHRoZSBib2lsZXJwbGF0ZSBpcyB0aGF0IGl0IHBy
b3ZpZGVkIGEgbWluaW1hbCBtYW5kYXRvcnkgdGV4dCAoYW5kIHRodXMgYSBtaW5pbWFsIHNldCBv
ZiBhZHZpY2UpIGZvciB0aGUgU2VjdXJpdHkgQ29uc2lkZXJhdGlvbnMgc2VjdGlvbnMgb2YgdGhl
IE1JQiBkb2N1bWVudHMuIEF1dGhvcnMgY2FuIGFsd2F5cyBhZGQgc2VjdXJpdHkgcmVsYXRlZCBj
b250ZW50IGFjY29yZGluZyB0byB0aGUgc3BlY2lmaWMgb2YgdGhlIHdvcmssIGFuZCB0aGlzIGlz
IHdoYXQgYXV0aG9ycyBoYXZlIGRvbmUgbWFueSB0aW1lcy4gDQoNClJlZ2FyZHMsDQoNCkRhbg0K
DQoNCj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4gRnJvbTogQWxpc3NhIENvb3BlciBb
bWFpbHRvOmFsaXNzYUBjb29wZXJ3LmluXQ0KPiBTZW50OiBUaHVyc2RheSwgSnVseSAxMCwgMjAx
NCA2OjI4IFBNDQo+IFRvOiBKdWVyZ2VuIFNjaG9lbndhZWxkZXI7IEJlbm9pdCBDbGFpc2UNCj4g
Q2M6IFJvbWFzY2FudSwgRGFuIChEYW4pOyBCZXJ0IFdpam5lbiAoSUVURik7IE1JQiBEb2N0b3Jz
IChFLW1haWwpOyBBZHJpYW4NCj4gRmFycmVsOyBzZWMtYWRzQHRvb2xzLmlldGYub3JnDQo+IFN1
YmplY3Q6IFJlOiBbTUlCLURPQ1RPUlNdIENoYW5nZSB0aGUgYm9pbGVycGxhdGUgLSBBbGlzc2En
cyBESVNDVVNTDQo+IA0KPiBQZXJoYXBzIHJhdGhlciB0aGFuIHJlLWRpc2N1c3NpbmcgdGhlIGJv
aWxlcnBsYXRlLCB3ZSBjb3VsZCBkaXNjdXNzIHdoYXQgdGhlDQo+IHB1cnBvc2Ugb2YgdGhlIGJv
aWxlcnBsYXRlIGlzLg0KPiANCj4gSWYgdGhlIHB1cnBvc2Ugb2YgdGhlIGJvaWxlcnBsYXRlIGlz
IHRvIHByb3ZpZGUgdGV4dCB0aGF0IGF1dGhvcnMgY2FuIGxvb2sgYXQNCj4gYW5kIHNheSwg4oCc
eWVzLCBpbiB0aGUgY2FzZSBvZiB0aGlzIGRvY3VtZW50LCB0aGUgYm9pbGVycGxhdGUgZnVsbHkg
Y292ZXJzIHRoZQ0KPiBzZWN1cml0eSBjb25zaWRlcmF0aW9ucyBvZiB0aGUgTUlCIGJlaW5nIHNw
ZWNpZmllZCzigJ0gdGhlbiBJIHRoaW5rIGl04oCZcyBhIGdyZWF0DQo+IHRoaW5nIHRvIGhhdmUu
IElmIHRoZSBwdXJwb3NlIG9mIHRoZSBib2lsZXJwbGF0ZSBpcyB0byBrZWVwIGFueSBhZGRpdGlv
bmFsDQo+IHNlY3VyaXR5IGNvbnNpZGVyYXRpb24gbm90IGNvdmVyZWQgaW4gdGhlIGJvaWxlcnBs
YXRlIGZyb20gYmVpbmcgYWRkcmVzc2VkIGluDQo+IGEgTUlCIGRvY3VtZW50LCB0aGVuIGl0IHNl
ZW1zIG92ZXJseSBjb25zdHJpY3RpbmcuDQo+IA0KPiBTZWN1cml0eSBjb25zaWRlcmF0aW9ucyBj
aGFuZ2Ugb3ZlciB0aW1lLiBJ4oCZbSBhc3N1bWluZyB0aGF0IGhvbWUvZGV2aWNlDQo+IGVuZXJn
eSBtb25pdG9yaW5nIHdhc27igJl0IHJlYWxseSB0b3Agb2YgbWluZCB3aGVuIFNOTVAgd2FzIGRl
dmVsb3BlZCBvcg0KPiB3aGVuIHRoZSBib2lsZXJwbGF0ZSB3YXMgb3JpZ2luYWxseSB3cml0dGVu
LiBTbyBpdOKAmXMgbm90IHN1cnByaXNpbmcgdGhhdCBuZXcNCj4gc2VjdXJpdHkgaXNzdWVzIGFy
ZSBhcmlzaW5nIHRoYXQgYXJlbuKAmXQgYWRkcmVzc2VkIHdpdGhpbiB0aGUgYm9pbGVycGxhdGUu
IElmIHRoZQ0KPiBib2lsZXJwbGF0ZSB3ZXJlIGp1c3QgYSBzdWdnZXN0aW9uIG9mIHRleHQgYW5k
IG5vdCBhIGxpbWl0YXRpb24gb24gd2hhdCBjYW4gYmUNCj4gZG9jdW1lbnRlZCwgd2UgY291bGQg
YWNjb21tb2RhdGUgdGhlIGNoYW5naW5nIHRpbWVzIGZhaXJseSBlYXNpbHkuDQo+IA0KPiBJbiBt
eSBvcmlnaW5hbCBESVNDVVNTLCBhbGwgSSBzdWdnZXN0ZWQgd2FzIHRleHQgdGhhdCBjb3VsZCBi
ZSBwcm92aWRlZCBpbg0KPiBhZGRpdGlvbiB0byB0aGUgYm9pbGVycGxhdGU6DQo+IA0KPiAiSW4g
Y2VydGFpbiBzaXR1YXRpb25zLCBlbmVyZ3kgYW5kIHBvd2VyIG1vbml0b3JpbmcgY2FuIHJldmVh
bCBzZW5zaXRpdmUNCj4gaW5mb3JtYXRpb24gYWJvdXQgaW5kaXZpZHVhbHMnIGFjdGl2aXRpZXMg
YW5kIGhhYml0cy4gSW1wbGVtZW50b3JzIG9mIHRoaXMNCj4gc3BlY2lmaWNhdGlvbiBzaG91bGQg
dXNlIGFwcHJvcHJpYXRlIHByaXZhY3kgcHJvdGVjdGlvbnMgYXMgZGlzY3Vzc2VkIGluDQo+IFNl
Y3Rpb24gOSBvZiBSRkMgNjk4OCBhbmQgbW9uaXRvcmluZyBvZiBpbmRpdmlkdWFscyBhbmQgaG9t
ZXMgc2hvdWxkIG9ubHkNCj4gb2NjdXIgd2l0aCBwcm9wZXIgYXV0aG9yaXphdGlvbi7igJ0NCj4g
DQo+IEkgaGF2ZSBub3QgaGFkIHRpbWUgdG8gbG9vayBhdCBTdGVwaGVu4oCZcyBjb21tZW50cyBi
dXQgSSBhZ3JlZSB3aXRoIGhpbSBhbmQNCj4gQmVydCB0aGF0IGFkZGluZyBhIHNwZWNpYWwgc2Vj
dGlvbiBvciBleHRyYSB0ZXh0IHRvIGRpc2N1c3MgcHJpdmFjeSBjb25jZXJucyBpbg0KPiB0aGUg
SW9ULXJlbGF0ZWQgZG9jdW1lbnRzIGlzIHRoZSByaWdodCB3YXkgdG8gZ28uDQo+IA0KPiBBbGlz
c2ENCj4gDQo+IA0KPiBPbiA3LzEwLzE0LCA4OjExIEFNLCAiSnVlcmdlbiBTY2hvZW53YWVsZGVy
Ig0KPiA8ai5zY2hvZW53YWVsZGVyQGphY29icy11bml2ZXJzaXR5LmRlPiB3cm90ZToNCj4gDQo+
ID5PbiBUaHUsIEp1bCAxMCwgMjAxNCBhdCAwNDoxMzowOFBNICswMjAwLCBCZW5vaXQgQ2xhaXNl
IHdyb3RlOg0KPiA+PiBEZWFyIGFsbCwNCj4gPj4NCj4gPj4gVGhlIGVtYWlsIGJlbG93IHJlZmVy
cyB0byBBbGlzc2EncyBESVNDVVNTIFNlZQ0KPiA+Pg0KPiA+Pmh0dHA6Ly9kYXRhdHJhY2tlci5p
ZXRmLm9yZy9kb2MvZHJhZnQtaWV0Zi1lbWFuLWVuZXJneS1tb25pdG9yaW5nLW1pYi8NCj4gPj5i
YWwNCj4gPj5sb3QvI2FsaXNzYS1jb29wZXINCj4gPj4NCj4gPj4gQWxpc3NhIHJlZmVycyB0byB0
aGlzIHNlbnRlbmNlIGluIHRoZSBib2lsZXJwbGF0ZSBhdA0KPiA+PiBodHRwOi8vdHJhYy50b29s
cy5pZXRmLm9yZy9hcmVhL29wcy90cmFjL3dpa2kvbWliLXNlY3VyaXR5DQo+ID4+DQo+ID4+ICAg
ICAgICAgSW1wbGVtZW50YXRpb25zIFNIT1VMRCBwcm92aWRlIHRoZSBzZWN1cml0eSBmZWF0dXJl
cw0KPiA+PiBkZXNjcmliZWQgYnkgdGhlDQo+ID4+ICAgICAgICAgU05NUHYzIGZyYW1ld29yayAo
c2VlIFtSRkMzNDEwXSksIGFuZCBpbXBsZW1lbnRhdGlvbnMNCj4gPj4gY2xhaW1pbmcgY29tcGxp
YW5jZQ0KPiA+PiAgICAgICAgIHRvIHRoZSBTTk1QdjMgc3RhbmRhcmQgTVVTVCBpbmNsdWRlIGZ1
bGwgc3VwcG9ydCBmb3INCj4gPj4gYXV0aGVudGljYXRpb24gYW5kDQo+ID4+ICAgICAgICAgcHJp
dmFjeSB2aWEgdGhlIFVzZXItYmFzZWQgU2VjdXJpdHkgTW9kZWwgKFVTTSkgW1JGQzM0MTRdDQo+
ID4+IHdpdGggdGhlIEFFUw0KPiA+PiAgICAgICAgIGNpcGhlciBhbGdvcml0aG0gW1JGQzM4MjZd
Lg0KPiA+Pg0KPiA+PiBGcm9tIHRoZSBkaXNjdXNzaW9uIChEYW4gYW5kQmVydCdzIGZlZWRiYWNr
LCBvbiB0b3Agb2YgbWluZSkgLCBpdA0KPiA+PiBzZWVtcyB0aGF0IHRoZXJlIGFyZSB2YWxpZCBy
ZWFzb25zIHRvIGtlZXAgYSBTSE9VTEQgaGVyZSBpbiB0aGUNCj4gPj4gZ2VuZXJpYyBib2lsZXJw
bGF0ZS4NCj4gPj4NCj4gPj4gU28gd2hhdCBuZXh0Pw0KPiA+PiAtIFNob3VsZCB3ZSBqdXN0aWZ5
IHRoZSByZWFzb25zIGluIHRoZSBib2lsZXIgcGxhdGUNCj4gPj4gLSBTaG91bGQgd2UgIGdpdmUg
c29tZSBmcmVlZG9tIGluIHRoZSBib2lsZXJwbGF0ZT8NCj4gPj4NCj4gPj4gICAgICAgICBJbXBs
ZW1lbnRhdGlvbnMgU0hPVUxEIHByb3ZpZGUgdGhlIHNlY3VyaXR5IGZlYXR1cmVzDQo+ID4+IGRl
c2NyaWJlZCBieSB0aGUNCj4gPj4gICAgICAgICBTTk1QdjMgZnJhbWV3b3JrIChzZWUgW1JGQzM0
MTBdKSwgYW5kIGltcGxlbWVudGF0aW9ucw0KPiA+PiBjbGFpbWluZyBjb21wbGlhbmNlDQo+ID4+
ICAgICAgICAgdG8gdGhlIFNOTVB2MyBzdGFuZGFyZCBNVVNUIGluY2x1ZGUgZnVsbCBzdXBwb3J0
IGZvcg0KPiA+PiBhdXRoZW50aWNhdGlvbiBhbmQNCj4gPj4gICAgICAgICBwcml2YWN5IHZpYSB0
aGUgVXNlci1iYXNlZCBTZWN1cml0eSBNb2RlbCAoVVNNKSBbUkZDMzQxNF0NCj4gPj4gd2l0aCB0
aGUgQUVTDQo+ID4+ICAgICAgICAgY2lwaGVyIGFsZ29yaXRobSBbUkZDMzgyNl0uDQo+ID4+DQo+
ID4+ICAgICAgICAgPGlmIHRoZXJlIGFyZSB1c2UgY2FzZXMgd2hlcmUgYSBNVVNUIGlzIHJlcXVp
cmVkLCBkZXNjcmliZWQNCj4gPj4gdGhlbSBoZXJlPg0KPiA+Pg0KPiA+PiAgIE5vdywgSSBob3Bl
IGl0IHdpbGwgbm90IGJlIGFidXNlZCBieSBTZWN1cml0eSBBRHMsIHJlcXVlc3RpbmcgYQ0KPiA+
PiBNVVNUIGZvciBldmVyeSBzaW5nbGUgTUlCIG1vZHVsZS4NCj4gPj4gLSBTb21ldGhpbmcgZWxz
ZT8NCj4gPj4gLSBTdG9wIHdyaXRpbmcgTUlCIG1vZHVsZXMgOi0pDQo+ID4+DQo+ID4NCj4gPkRv
IG5vdGhpbmcsIHJlLWRpc2N1c3MgdGhpcyBldmVyeSBvdGhlciB5ZWFyLiA7LSkNCj4gPg0KPiA+
L2pzDQo+ID4NCj4gPi0tDQo+ID5KdWVyZ2VuIFNjaG9lbndhZWxkZXIgICAgICAgICAgIEphY29i
cyBVbml2ZXJzaXR5IEJyZW1lbiBnR21iSA0KPiA+UGhvbmU6ICs0OSA0MjEgMjAwIDM1ODcgICAg
ICAgICBDYW1wdXMgUmluZyAxLCAyODc1OSBCcmVtZW4sIEdlcm1hbnkNCj4gPkZheDogICArNDkg
NDIxIDIwMCAzMTAzICAgICAgICAgPGh0dHA6Ly93d3cuamFjb2JzLXVuaXZlcnNpdHkuZGUvPg0K
PiANCg0K


From nobody Thu Jul 10 08:44:15 2014
Return-Path: <kathleen.moriarty.ietf@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 008011A043D for <mib-doctors@ietfa.amsl.com>; Thu, 10 Jul 2014 08:44:14 -0700 (PDT)
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, FREEMAIL_FROM=0.001, HTML_MESSAGE=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 DUg6dWGNhiTf for <mib-doctors@ietfa.amsl.com>; Thu, 10 Jul 2014 08:44:11 -0700 (PDT)
Received: from mail-la0-x230.google.com (mail-la0-x230.google.com [IPv6:2a00:1450:4010:c03::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9FB241A0385 for <mib-doctors@ietf.org>; Thu, 10 Jul 2014 08:44:09 -0700 (PDT)
Received: by mail-la0-f48.google.com with SMTP id el20so6388312lab.35 for <mib-doctors@ietf.org>; Thu, 10 Jul 2014 08:44:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=of94juMZpznbVP38Sf6URhvaeS5no/3jUyaEsDzCVVU=; b=hiMt11Rc/mSu/w7xVx7RKebIa75nSLwPEOuGKI5YZ55ZMEJMXCLA9Z03mHsMIAS2FW zHthI+YdIDEbyRidXp6Mm23SAAgKHO640F1ANGFNeNPYp5nwNyhO0ImfkEVPg1iHfppj nQa3qaPRvZJZ6OuWRtfk+unrX2WY1b74qcWYSyeTkV1H4wjga2EZgZ2YRz/iS3D70Tb0 5AD0uPP7Lxf7goB2oe7+vjBj9mQ8AFOVy44CM8UCCrKo54hws97g8MTjewp/HIhRHY+e BjrFEWskmWp+ytI398B21A8i7MZVL2sz7m/fjuMu3xlp+ZCT7ESR++IOKXsb+oZJDp0/ OL7Q==
MIME-Version: 1.0
X-Received: by 10.112.149.200 with SMTP id uc8mr4496227lbb.70.1405007047941; Thu, 10 Jul 2014 08:44:07 -0700 (PDT)
Received: by 10.112.253.198 with HTTP; Thu, 10 Jul 2014 08:44:07 -0700 (PDT)
In-Reply-To: <9904FB1B0159DA42B0B887B7FA8119CA5C83D3FD@AZ-FFEXMB04.global.avaya.com>
References: <CFE17DDA.458C3%alissa@cooperw.in> <53BC5081.6090809@cisco.com> <53BD6690.2040102@cisco.com> <53BE3D7E.2090302@bwijnen.net> <9904FB1B0159DA42B0B887B7FA8119CA5C83CC03@AZ-FFEXMB04.global.avaya.com> <53BE9F74.9080705@cisco.com> <20140710151138.GB90581@elstar.local> <CFE3FCE9.45FFF%alissa@cooperw.in> <9904FB1B0159DA42B0B887B7FA8119CA5C83D3FD@AZ-FFEXMB04.global.avaya.com>
Date: Thu, 10 Jul 2014 11:44:07 -0400
Message-ID: <CAHbuEH541FreYCR-BY1r=bjB0OrOX1aAmDOi5N_ym=t8s45JKw@mail.gmail.com>
From: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
Content-Type: multipart/alternative; boundary=047d7b342d74ffe4a104fdd8b187
Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/mptfl94DDVZeAPD-lqquXBCZztY
Cc: Alissa Cooper <alissa@cooperw.in>, "sec-ads@tools.ietf.org" <sec-ads@tools.ietf.org>, "MIB Doctors \(E-mail\)" <mib-doctors@ietf.org>, Adrian Farrel <adrian@olddog.co.uk>
Subject: Re: [MIB-DOCTORS] Change the boilerplate - Alissa's DISCUSS
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, 10 Jul 2014 15:44:14 -0000

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

On Thu, Jul 10, 2014 at 11:32 AM, Romascanu, Dan (Dan) <dromasca@avaya.com>
wrote:

> The way I always understood the boilerplate is that it provided a minimal
> mandatory text (and thus a minimal set of advice) for the Security
> Considerations sections of the MIB documents. Authors can always add
> security related content according to the specific of the work, and this =
is
> what authors have done many times.
>
> OK, I think the problem we ran into this time is that three drafts have
additional considerations that are not covered in the template.  In my
discuss, I suggested an optional section to be included and was trying some
other security considerations to tie it into Alissa's text for IoT, for
both privacy and security.

I appreciate the addition of text in the template discussed in another
thread.

Thanks,
Kathleen



> Regards,
>
> Dan
>
>
> > -----Original Message-----
> > From: Alissa Cooper [mailto:alissa@cooperw.in]
> > Sent: Thursday, July 10, 2014 6:28 PM
> > To: Juergen Schoenwaelder; Benoit Claise
> > Cc: Romascanu, Dan (Dan); Bert Wijnen (IETF); MIB Doctors (E-mail);
> Adrian
> > Farrel; sec-ads@tools.ietf.org
> > Subject: Re: [MIB-DOCTORS] Change the boilerplate - Alissa's DISCUSS
> >
> > Perhaps rather than re-discussing the boilerplate, we could discuss wha=
t
> the
> > purpose of the boilerplate is.
> >
> > If the purpose of the boilerplate is to provide text that authors can
> look at
> > and say, =E2=80=9Cyes, in the case of this document, the boilerplate fu=
lly
> covers the
> > security considerations of the MIB being specified,=E2=80=9D then I thi=
nk it=E2=80=99s a
> great
> > thing to have. If the purpose of the boilerplate is to keep any
> additional
> > security consideration not covered in the boilerplate from being
> addressed in
> > a MIB document, then it seems overly constricting.
> >
> > Security considerations change over time. I=E2=80=99m assuming that hom=
e/device
> > energy monitoring wasn=E2=80=99t really top of mind when SNMP was devel=
oped or
> > when the boilerplate was originally written. So it=E2=80=99s not surpri=
sing that
> new
> > security issues are arising that aren=E2=80=99t addressed within the
> boilerplate. If the
> > boilerplate were just a suggestion of text and not a limitation on what
> can be
> > documented, we could accommodate the changing times fairly easily.
> >
> > In my original DISCUSS, all I suggested was text that could be provided
> in
> > addition to the boilerplate:
> >
> > "In certain situations, energy and power monitoring can reveal sensitiv=
e
> > information about individuals' activities and habits. Implementors of
> this
> > specification should use appropriate privacy protections as discussed i=
n
> > Section 9 of RFC 6988 and monitoring of individuals and homes should on=
ly
> > occur with proper authorization.=E2=80=9D
> >
> > I have not had time to look at Stephen=E2=80=99s comments but I agree w=
ith him
> and
> > Bert that adding a special section or extra text to discuss privacy
> concerns in
> > the IoT-related documents is the right way to go.
> >
> > Alissa
> >
> >
> > On 7/10/14, 8:11 AM, "Juergen Schoenwaelder"
> > <j.schoenwaelder@jacobs-university.de> wrote:
> >
> > >On Thu, Jul 10, 2014 at 04:13:08PM +0200, Benoit Claise wrote:
> > >> Dear all,
> > >>
> > >> The email below refers to Alissa's DISCUSS See
> > >>
> > >>http://datatracker.ietf.org/doc/draft-ietf-eman-energy-monitoring-mib=
/
> > >>bal
> > >>lot/#alissa-cooper
> > >>
> > >> Alissa refers to this sentence in the boilerplate at
> > >> http://trac.tools.ietf.org/area/ops/trac/wiki/mib-security
> > >>
> > >>         Implementations SHOULD provide the security features
> > >> described by the
> > >>         SNMPv3 framework (see [RFC3410]), and implementations
> > >> claiming compliance
> > >>         to the SNMPv3 standard MUST include full support for
> > >> authentication and
> > >>         privacy via the User-based Security Model (USM) [RFC3414]
> > >> with the AES
> > >>         cipher algorithm [RFC3826].
> > >>
> > >> From the discussion (Dan andBert's feedback, on top of mine) , it
> > >> seems that there are valid reasons to keep a SHOULD here in the
> > >> generic boilerplate.
> > >>
> > >> So what next?
> > >> - Should we justify the reasons in the boiler plate
> > >> - Should we  give some freedom in the boilerplate?
> > >>
> > >>         Implementations SHOULD provide the security features
> > >> described by the
> > >>         SNMPv3 framework (see [RFC3410]), and implementations
> > >> claiming compliance
> > >>         to the SNMPv3 standard MUST include full support for
> > >> authentication and
> > >>         privacy via the User-based Security Model (USM) [RFC3414]
> > >> with the AES
> > >>         cipher algorithm [RFC3826].
> > >>
> > >>         <if there are use cases where a MUST is required, described
> > >> them here>
> > >>
> > >>   Now, I hope it will not be abused by Security ADs, requesting a
> > >> MUST for every single MIB module.
> > >> - Something else?
> > >> - Stop writing MIB modules :-)
> > >>
> > >
> > >Do nothing, re-discuss this every other year. ;-)
> > >
> > >/js
> > >
> > >--
> > >Juergen Schoenwaelder           Jacobs University Bremen gGmbH
> > >Phone: +49 421 200 3587         Campus Ring 1, 28759 Bremen, Germany
> > >Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>
> >
>
>


--=20

Best regards,
Kathleen

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On Thu, Jul 10, 2014 at 11:32 AM, Romascanu, Dan (Dan) <span dir=3D=
"ltr">&lt;<a href=3D"mailto:dromasca@avaya.com" target=3D"_blank">dromasca@=
avaya.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">The way I always understood the boilerplate =
is that it provided a minimal mandatory text (and thus a minimal set of adv=
ice) for the Security Considerations sections of the MIB documents. Authors=
 can always add security related content according to the specific of the w=
ork, and this is what authors have done many times.<br>

<br></blockquote><div>OK, I think the problem we ran into this time is that=
 three drafts have additional considerations that are not covered in the te=
mplate. =C2=A0In my discuss, I suggested an optional section to be included=
 and was trying some other security considerations to tie it into Alissa&#3=
9;s text for IoT, for both privacy and security.</div>
<div><br></div><div>I appreciate the addition of text in the template discu=
ssed in another thread.</div><div><br></div><div>Thanks,</div><div>Kathleen=
</div><div><br></div><div>=C2=A0</div><blockquote class=3D"gmail_quote" sty=
le=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">

Regards,<br>
<br>
Dan<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
<br>
&gt; -----Original Message-----<br>
&gt; From: Alissa Cooper [mailto:<a href=3D"mailto:alissa@cooperw.in">aliss=
a@cooperw.in</a>]<br>
&gt; Sent: Thursday, July 10, 2014 6:28 PM<br>
&gt; To: Juergen Schoenwaelder; Benoit Claise<br>
&gt; Cc: Romascanu, Dan (Dan); Bert Wijnen (IETF); MIB Doctors (E-mail); Ad=
rian<br>
&gt; Farrel; <a href=3D"mailto:sec-ads@tools.ietf.org">sec-ads@tools.ietf.o=
rg</a><br>
&gt; Subject: Re: [MIB-DOCTORS] Change the boilerplate - Alissa&#39;s DISCU=
SS<br>
&gt;<br>
&gt; Perhaps rather than re-discussing the boilerplate, we could discuss wh=
at the<br>
&gt; purpose of the boilerplate is.<br>
&gt;<br>
&gt; If the purpose of the boilerplate is to provide text that authors can =
look at<br>
&gt; and say, =E2=80=9Cyes, in the case of this document, the boilerplate f=
ully covers the<br>
&gt; security considerations of the MIB being specified,=E2=80=9D then I th=
ink it=E2=80=99s a great<br>
&gt; thing to have. If the purpose of the boilerplate is to keep any additi=
onal<br>
&gt; security consideration not covered in the boilerplate from being addre=
ssed in<br>
&gt; a MIB document, then it seems overly constricting.<br>
&gt;<br>
&gt; Security considerations change over time. I=E2=80=99m assuming that ho=
me/device<br>
&gt; energy monitoring wasn=E2=80=99t really top of mind when SNMP was deve=
loped or<br>
&gt; when the boilerplate was originally written. So it=E2=80=99s not surpr=
ising that new<br>
&gt; security issues are arising that aren=E2=80=99t addressed within the b=
oilerplate. If the<br>
&gt; boilerplate were just a suggestion of text and not a limitation on wha=
t can be<br>
&gt; documented, we could accommodate the changing times fairly easily.<br>
&gt;<br>
&gt; In my original DISCUSS, all I suggested was text that could be provide=
d in<br>
&gt; addition to the boilerplate:<br>
&gt;<br>
&gt; &quot;In certain situations, energy and power monitoring can reveal se=
nsitive<br>
&gt; information about individuals&#39; activities and habits. Implementors=
 of this<br>
&gt; specification should use appropriate privacy protections as discussed =
in<br>
&gt; Section 9 of RFC 6988 and monitoring of individuals and homes should o=
nly<br>
&gt; occur with proper authorization.=E2=80=9D<br>
&gt;<br>
&gt; I have not had time to look at Stephen=E2=80=99s comments but I agree =
with him and<br>
&gt; Bert that adding a special section or extra text to discuss privacy co=
ncerns in<br>
&gt; the IoT-related documents is the right way to go.<br>
&gt;<br>
&gt; Alissa<br>
&gt;<br>
&gt;<br>
&gt; On 7/10/14, 8:11 AM, &quot;Juergen Schoenwaelder&quot;<br>
&gt; &lt;<a href=3D"mailto:j.schoenwaelder@jacobs-university.de">j.schoenwa=
elder@jacobs-university.de</a>&gt; wrote:<br>
&gt;<br>
&gt; &gt;On Thu, Jul 10, 2014 at 04:13:08PM +0200, Benoit Claise wrote:<br>
&gt; &gt;&gt; Dear all,<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; The email below refers to Alissa&#39;s DISCUSS See<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt;<a href=3D"http://datatracker.ietf.org/doc/draft-ietf-eman-ene=
rgy-monitoring-mib/" target=3D"_blank">http://datatracker.ietf.org/doc/draf=
t-ietf-eman-energy-monitoring-mib/</a><br>
&gt; &gt;&gt;bal<br>
&gt; &gt;&gt;lot/#alissa-cooper<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; Alissa refers to this sentence in the boilerplate at<br>
&gt; &gt;&gt; <a href=3D"http://trac.tools.ietf.org/area/ops/trac/wiki/mib-=
security" target=3D"_blank">http://trac.tools.ietf.org/area/ops/trac/wiki/m=
ib-security</a><br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 Implementations SHOULD provide th=
e security features<br>
&gt; &gt;&gt; described by the<br>
&gt; &gt;&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 SNMPv3 framework (see [RFC3410]),=
 and implementations<br>
&gt; &gt;&gt; claiming compliance<br>
&gt; &gt;&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 to the SNMPv3 standard MUST inclu=
de full support for<br>
&gt; &gt;&gt; authentication and<br>
&gt; &gt;&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 privacy via the User-based Securi=
ty Model (USM) [RFC3414]<br>
&gt; &gt;&gt; with the AES<br>
&gt; &gt;&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 cipher algorithm [RFC3826].<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; From the discussion (Dan andBert&#39;s feedback, on top of mi=
ne) , it<br>
&gt; &gt;&gt; seems that there are valid reasons to keep a SHOULD here in t=
he<br>
&gt; &gt;&gt; generic boilerplate.<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; So what next?<br>
&gt; &gt;&gt; - Should we justify the reasons in the boiler plate<br>
&gt; &gt;&gt; - Should we =C2=A0give some freedom in the boilerplate?<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 Implementations SHOULD provide th=
e security features<br>
&gt; &gt;&gt; described by the<br>
&gt; &gt;&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 SNMPv3 framework (see [RFC3410]),=
 and implementations<br>
&gt; &gt;&gt; claiming compliance<br>
&gt; &gt;&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 to the SNMPv3 standard MUST inclu=
de full support for<br>
&gt; &gt;&gt; authentication and<br>
&gt; &gt;&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 privacy via the User-based Securi=
ty Model (USM) [RFC3414]<br>
&gt; &gt;&gt; with the AES<br>
&gt; &gt;&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 cipher algorithm [RFC3826].<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 &lt;if there are use cases where =
a MUST is required, described<br>
&gt; &gt;&gt; them here&gt;<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; =C2=A0 Now, I hope it will not be abused by Security ADs, req=
uesting a<br>
&gt; &gt;&gt; MUST for every single MIB module.<br>
&gt; &gt;&gt; - Something else?<br>
&gt; &gt;&gt; - Stop writing MIB modules :-)<br>
&gt; &gt;&gt;<br>
&gt; &gt;<br>
&gt; &gt;Do nothing, re-discuss this every other year. ;-)<br>
&gt; &gt;<br>
&gt; &gt;/js<br>
&gt; &gt;<br>
&gt; &gt;--<br>
&gt; &gt;Juergen Schoenwaelder =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Jacobs Un=
iversity Bremen gGmbH<br>
&gt; &gt;Phone: +49 421 200 3587 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Campus Ring 1,=
 28759 Bremen, Germany<br>
&gt; &gt;Fax: =C2=A0 +49 421 200 3103 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &lt;<a hr=
ef=3D"http://www.jacobs-university.de/" target=3D"_blank">http://www.jacobs=
-university.de/</a>&gt;<br>
&gt;<br>
<br>
</div></div></blockquote></div><br><br clear=3D"all"><div><br></div>-- <br>=
<div dir=3D"ltr"><br><div>Best regards,</div><div>Kathleen</div></div>
</div></div>

--047d7b342d74ffe4a104fdd8b187--


From nobody Thu Jul 10 09:10:56 2014
Return-Path: <alissa@cooperw.in>
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 51DC51A043D for <mib-doctors@ietfa.amsl.com>; Thu, 10 Jul 2014 08:28:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_LOW=-0.7] 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 Lanjd1al5ul8 for <mib-doctors@ietfa.amsl.com>; Thu, 10 Jul 2014 08:28:02 -0700 (PDT)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3C6061A0233 for <mib-doctors@ietf.org>; Thu, 10 Jul 2014 08:28:02 -0700 (PDT)
Received: from compute2.internal (compute2.nyi.mail.srv.osa [10.202.2.42]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id F1FA021B5F for <mib-doctors@ietf.org>; Thu, 10 Jul 2014 11:27:59 -0400 (EDT)
Received: from frontend1 ([10.202.2.160]) by compute2.internal (MEProxy); Thu, 10 Jul 2014 11:27:59 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=cooperw.in; h=date :subject:from:to:cc:message-id:references:in-reply-to :mime-version:content-type:content-transfer-encoding; s=mesmtp; bh=CdYOHvx7IhX9RQua5TUpQbZdraE=; b=Rl2QU5q7ZJsiFfvr2fWsIBqfWzot tMfKcIM+/nWkUGJ0E4u3rF2fFeh/KnIYsdTIFOmiU5vQW1InQXvZi1D6UvmtXTYh /IIWZsuApgu+RgM8gfGyHvi32cgKqTIqZiYmSexFqoiDYiiuVZsi97Q+sV9omoNs ZQP8n6pfJVlVBw8=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=date:subject:from:to:cc:message-id :references:in-reply-to:mime-version:content-type :content-transfer-encoding; s=smtpout; bh=CdYOHvx7IhX9RQua5TUpQb ZdraE=; b=O6ej8BINoYPsExzN3miRZVjge4zWZCy0XfVhnqKPM243/u+ztBsYwu lt2+T/0QU6uc+d2dGL7debHRUbEP4qDYzD4TcjzqhSNo1Gal5Akg/MNEmceq29a2 BOUwpaxJpaLq0YMbp+tL/YjpH+VoHprx84GK4DvUveWUtZKVktSm4=
X-Sasl-enc: lh/+rwGUTqbmrc8vpoeFMsrkhHigLYvH195RRo0K6Zv8 1405006079
Received: from [171.68.18.44] (unknown [171.68.18.44]) by mail.messagingengine.com (Postfix) with ESMTPA id E22EEC007AE; Thu, 10 Jul 2014 11:27:56 -0400 (EDT)
User-Agent: Microsoft-MacOutlook/14.3.9.131030
Date: Thu, 10 Jul 2014 08:27:52 -0700
From: Alissa Cooper <alissa@cooperw.in>
To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>, Benoit Claise <bclaise@cisco.com>
Message-ID: <CFE3FCE9.45FFF%alissa@cooperw.in>
Thread-Topic: [MIB-DOCTORS] Change the boilerplate - Alissa's DISCUSS
References: <CFE17DDA.458C3%alissa@cooperw.in> <53BC5081.6090809@cisco.com> <53BD6690.2040102@cisco.com> <53BE3D7E.2090302@bwijnen.net> <9904FB1B0159DA42B0B887B7FA8119CA5C83CC03@AZ-FFEXMB04.global.avaya.com> <53BE9F74.9080705@cisco.com> <20140710151138.GB90581@elstar.local>
In-Reply-To: <20140710151138.GB90581@elstar.local>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/dBiuV7OhDN6GYJ2pCCetYNgirN0
X-Mailman-Approved-At: Thu, 10 Jul 2014 09:10:44 -0700
Cc: Adrian Farrel <adrian@olddog.co.uk>, sec-ads@tools.ietf.org, "MIB Doctors \(E-mail\)" <mib-doctors@ietf.org>
Subject: Re: [MIB-DOCTORS] Change the boilerplate - Alissa's DISCUSS
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, 10 Jul 2014 15:28:04 -0000

Perhaps rather than re-discussing the boilerplate, we could discuss what
the purpose of the boilerplate is.

If the purpose of the boilerplate is to provide text that authors can look
at and say, =E2=80=9Cyes, in the case of this document, the boilerplate fully
covers the security considerations of the MIB being specified,=E2=80=9D then I
think it=E2=80=99s a great thing to have. If the purpose of the boilerplate is to
keep any additional security consideration not covered in the boilerplate
from being addressed in a MIB document, then it seems overly constricting.

Security considerations change over time. I=E2=80=99m assuming that home/device
energy monitoring wasn=E2=80=99t really top of mind when SNMP was developed or
when the boilerplate was originally written. So it=E2=80=99s not surprising that
new security issues are arising that aren=E2=80=99t addressed within the
boilerplate. If the boilerplate were just a suggestion of text and not a
limitation on what can be documented, we could accommodate the changing
times fairly easily.

In my original DISCUSS, all I suggested was text that could be provided in
addition to the boilerplate:

"In certain situations, energy and power monitoring can reveal sensitive
information about individuals' activities and habits. Implementors of this
specification should use appropriate privacy protections as discussed in
Section 9 of RFC 6988 and monitoring of individuals and homes should only
occur
with proper authorization.=E2=80=9D

I have not had time to look at Stephen=E2=80=99s comments but I agree with him an=
d
Bert that adding a special section or extra text to discuss privacy
concerns in the IoT-related documents is the right way to go.

Alissa


On 7/10/14, 8:11 AM, "Juergen Schoenwaelder"
<j.schoenwaelder@jacobs-university.de> wrote:

>On Thu, Jul 10, 2014 at 04:13:08PM +0200, Benoit Claise wrote:
>> Dear all,
>>=20
>> The email below refers to Alissa's DISCUSS
>> See=20
>>=20
>>http://datatracker.ietf.org/doc/draft-ietf-eman-energy-monitoring-mib/bal
>>lot/#alissa-cooper
>>=20
>> Alissa refers to this sentence in the boilerplate at
>> http://trac.tools.ietf.org/area/ops/trac/wiki/mib-security
>>=20
>>         Implementations SHOULD provide the security features described
>> by the
>>         SNMPv3 framework (see [RFC3410]), and implementations claiming
>> compliance
>>         to the SNMPv3 standard MUST include full support for
>> authentication and
>>         privacy via the User-based Security Model (USM) [RFC3414] with
>> the AES
>>         cipher algorithm [RFC3826].
>>=20
>> From the discussion (Dan andBert's feedback, on top of mine) , it seems
>> that there are valid reasons to keep a SHOULD here in the generic
>> boilerplate.
>>=20
>> So what next?
>> - Should we justify the reasons in the boiler plate
>> - Should we  give some freedom in the boilerplate?
>>=20
>>         Implementations SHOULD provide the security features described
>> by the
>>         SNMPv3 framework (see [RFC3410]), and implementations claiming
>> compliance
>>         to the SNMPv3 standard MUST include full support for
>> authentication and
>>         privacy via the User-based Security Model (USM) [RFC3414] with
>> the AES
>>         cipher algorithm [RFC3826].
>>=20
>>         <if there are use cases where a MUST is required, described
>> them here>
>>=20
>>   Now, I hope it will not be abused by Security ADs, requesting a MUST
>> for every single MIB module.
>> - Something else?
>> - Stop writing MIB modules :-)
>>=20
>
>Do nothing, re-discuss this every other year. ;-)
>
>/js
>
>--=20
>Juergen Schoenwaelder           Jacobs University Bremen gGmbH
>Phone: +49 421 200 3587         Campus Ring 1, 28759 Bremen, Germany
>Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>



From nobody Thu Jul 10 20:25:11 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 237071A0370 for <mib-doctors@ietfa.amsl.com>; Thu, 10 Jul 2014 20:25:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.651
X-Spam-Level: 
X-Spam-Status: No, score=-2.651 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JkWyV1vHXdOE for <mib-doctors@ietfa.amsl.com>; Thu, 10 Jul 2014 20:25:07 -0700 (PDT)
Received: from qmta13.westchester.pa.mail.comcast.net (qmta13.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:44:76:96:59:243]) by ietfa.amsl.com (Postfix) with ESMTP id 1D4021A0240 for <mib-doctors@ietf.org>; Thu, 10 Jul 2014 20:25:06 -0700 (PDT)
Received: from omta20.westchester.pa.mail.comcast.net ([76.96.62.71]) by qmta13.westchester.pa.mail.comcast.net with comcast id QrMR1o0021YDfWL5DrR6Pc; Fri, 11 Jul 2014 03:25:06 +0000
Received: from JV6RVH1 ([67.189.237.137]) by omta20.westchester.pa.mail.comcast.net with comcast id QrR51o00W2yZEBF3grR55w; Fri, 11 Jul 2014 03:25:06 +0000
From: "David Harrington" <dbharrington@comcast.net>
To: "'Bert Wijnen \(IETF\)'" <bertietf@bwijnen.net>, "'Benoit Claise'" <bclaise@cisco.com>, "'MIB Doctors \(E-mail\)'" <mib-doctors@ietf.org>
References: <CFE17DDA.458C3%alissa@cooperw.in> <53BC5081.6090809@cisco.com> <53BD6690.2040102@cisco.com> <53BE3D7E.2090302@bwijnen.net>
In-Reply-To: <53BE3D7E.2090302@bwijnen.net>
Date: Thu, 10 Jul 2014 23:25:04 -0400
Message-ID: <03b401cf9cb7$b534ac30$1f9e0490$@comcast.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQFl8rZKGe1/GoUrOyAIbnSi/UNwbgJVJfCQAeLZGl0Bnx6yJJw+zwRg
Content-Language: en-us
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1405049106; bh=Vt39HRCA9s6pJrm6PWj1YRse4pk03APUx7XySG3rh+w=; h=Received:Received:From:To:Subject:Date:Message-ID:MIME-Version: Content-Type; b=UC0l1wSxo+lfVBVsxBpQtBLhwEz742IhnUK5xnRl+BR+KPxJ5V19BRYaZcR8uvlT2 eh53L+di2RgGU69QPB36CkXSSEHc5ynX53fas+sn7YMdBHVEyIuxlzIKpStOQpohP6 TMQTcSra5YKz2pLyJHrnWWacrhKOprDQ+KXcqzXDQGrKy06sauQm+Wjry7j8P5PaZM BHYDDfLo2LBoy+SCAy9Gaw34EDPzpw2junIM/Em+jcErF1nBwIXlj2iAmLUCEh7abu szLzPCyt09SQncLML0/T258gRv72o3HMWqZexRCdQetmU0YsM2vDPCjJajMIP2+sQf h70MWm37uR84w==
Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/bzsPF_Ri9XH2AbeuYWW1qUdsJ7o
Cc: 'Adrian Farrel' <adrian@olddog.co.uk>, 'Alissa Cooper' <alissa@cooperw.in>
Subject: Re: [MIB-DOCTORS] Change the boilerplate
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, 11 Jul 2014 03:25:10 -0000

The design of IETF management is that the data models are separate from the
protocols that carry the data.
This is based on the precedent set by RFC1052, where the IAB made the
deliberate decision to separate them so that the temporary simple protocol
SNMP could be replaced by the more full-featured CMIP when it was ready.

A MIB module might be used with SNMPv3 (the recommended approach), or
SNMPv1/v2 (for secure networks, or at the administrator's discretion for
other reasons).
A MIB module might be used with a newer version of SNMP, such as SNMPv4,
should we ever choose to develop a later version.
A MIB module might also be used with other protocols, such as IPFIX or
Netconf or protocols standardized by other SDOs, and so on, when
appropriate.
A MIB module might also be used with other protocols, such as a proprietary
protocol used within a closed network.
So SHOULD is appropriate. 

David Harrington
dbharrington@comcast.net
+1-603-828-1401
> -----Original Message-----
> From: MIB-DOCTORS [mailto:mib-doctors-bounces@ietf.org] On Behalf Of
> Bert Wijnen (IETF)
> Sent: Thursday, July 10, 2014 3:15 AM
> To: Benoit Claise; MIB Doctors (E-mail)
> Cc: Adrian Farrel; 'Alissa Cooper'
> Subject: Re: [MIB-DOCTORS] Change the boilerplate
> 
> it is always interesting to see that when we get new ADs that we must
> rediscuss this whole topic.
> 
> But yes, there are/were implementations/deployments where one uses
> dedicated (secure) networks
> for the network management systems, and so that would work under a
> SHOULD.
> 
> I do not recall if that was/is the only reason why we agreed on a SHOULD
> instead of MUST.
> 
> Bert
> 
> On 09/07/14 17:58, Benoit Claise wrote:
> > MIB doctors,
> >
> > Let me focus the discussion a little bit.
> > Alissa refers to this sentence in the boilerplate at
> http://trac.tools.ietf.org/area/ops/trac/wiki/mib-security
> >
> >         Implementations SHOULD provide the security features described
by
> the
> >         SNMPv3 framework (see [RFC3410]), and implementations claiming
> compliance
> >         to the SNMPv3 standard MUST include full support for
authentication
> and
> >         privacy via the User-based Security Model (USM) [RFC3414] with
the
> AES
> >         cipher algorithm [RFC3826].
> >
> >
> > Alissa's feedback is:
> >
> >     It is a little disconcerting that use of SNMPv3 is provided as a
SHOULD-
> level requirement without discussion of deployment
> >     scenarios and regardless of the sensitivity of the data being made
> available by any new MIB. For example, the tradeoffs between
> >     security and utility might be reasonable if (1) I'm using an older
SNMP
> version on my closed home network to monitor my own
> >     energy use, but not if (2) my ISP is using it to monitor the same
thing. The
> text quoted above basically  endorses unauthorized
> >     energy monitoring if the provider does not support SNMPv3, whereas
it
> seems like what we would want to be saying is that in
> >     cases like (2) SNMPv3 is required.
> >
> > Can one of the old timers (who was part of the discussion) explain the
> SHOULD rational? Personally, I can see two use cases in favor
> > off the SHOULD: an older SNMP version in a closed network,  or a private
> data communication network dedicated to network management
> > with special protection out of SNMP (like encrypted tunnel)
> >
> > Should we now modify this sentence to say?
> >
> >     MUST provide the security features described by the
> >     SNMPv3 framework (see [RFC3410])
> >
> > Regards, Benoit
> >
> >> MIB doctors,
> >>
> >> It seems that the "Security Guidelines for IETF MIB modules" receives
> comment for each MIB module submitted to the IESG.
> >> Is it time to modify it, or are we redoing the same discussions over
and
> over?
> >>
> >> Regards, Benoit
> >>
> >>
> >> -------- Original Message --------
> >> Subject: 	Re: Alissa Cooper's Discuss on draft-ietf-eman-energy-
> monitoring-mib-12: (with DISCUSS and COMMENT)
> >> Date: 	Tue, 8 Jul 2014 13:02:50 -0700
> >> From: 	Alissa Cooper <alissa@cooperw.in>
> >> To: 	Benoit Claise <bclaise@cisco.com>, The IESG <iesg@ietf.org>
> >> CC: 	<draft-ietf-eman-energy-monitoring-mib@tools.ietf.org>,
<eman-
> chairs@tools.ietf.org>
> >>
> >>
> >>
> >> Hi Benoit,
> >>
> >> On 7/8/14, 1:44 AM, "Benoit Claise" <bclaise@cisco.com
> <mailto:bclaise@cisco.com>> wrote:
> >>
> >>     Hi Alissa,
> >>
> >>     Thanks for your review.
> >>>     Alissa Cooper has entered the following ballot position for
> >>>     draft-ietf-eman-energy-monitoring-mib-12: Discuss
> >>>
> >>>     When responding, please keep the subject line intact and reply to
all
> >>>     email addresses included in the To and CC lines. (Feel free to cut
this
> >>>     introductory paragraph, however.)
> >>>
> >>>
> >>>     Please refer tohttp://www.ietf.org/iesg/statement/discuss-
> criteria.html
> >>>     for more information about IESG DISCUSS and COMMENT positions.
> >>>
> >>>
> >>>     The document, along with other ballot positions, can be found
here:
> >>>     http://datatracker.ietf.org/doc/draft-ietf-eman-energy-monitoring-
> mib/
> >>>
> >>>
> >>>
> >>>
----------------------------------------------------------------------
> >>>     DISCUSS:
> >>>
----------------------------------------------------------------------
> >>>
> >>>     Section 11 is missing a discussion of the privacy considerations
of
> >>>     energy and power monitoring. I would suggest something along the
> lines of
> >>>     the following:
> >>>
> >>>     "In certain situations, energy and power monitoring can reveal
> sensitive
> >>>     information about individuals' activities and habits. Implementors
of
> >>>     this specification should use appropriate privacy protections as
> >>>     discussed in Section 9 of RFC 6988 and monitoring of individuals
and
> >>>     homes should only occur with proper authorization."
> >>
> >>     Regarding your first sentence, I propose the following text, which
would
> be in line with Security Guidelines for IETF MIB
> >>     modules at
http://trac.tools.ietf.org/area/ops/trac/wiki/mib-security
> >>
> >>         Some of the readable objects in this MIB module (i.e., objects
with a
> >>         MAX-ACCESS other than not-accessible) may be considered
sensitive
> or
> >>         vulnerable in some network environments.  It is thus important
to
> >>         control even GET and/or NOTIFY access to these objects and
possibly
> >>         to even encrypt the values of these objects when sending them
over
> >>         the network via SNMP.  These are the tables and objects and
their
> >>         sensitivity/vulnerability:
> >>
> >>         Access to the content of the eoPowerStateTable, eoEnergyTable,
and
> >>         eoACPwrAttributesTable MIB tables can reveal sensitive
> >>         information about individuals' activities and habits
> >>
> >> Sounds good to me.
> >>
> >>
> >>     Since this document is essentially a MIB module, your last sentence
is
> covered by
> >>
> >>              implementations
> >>              claiming compliance to the SNMPv3 standard MUST include
full
> >>              support for authentication and privacy via the User-based
> >>              Security Model (USM) [RFC3414
> <http://tools.ietf.org/html/rfc3414>] with the AES cipher algorithm
> >>              [RFC3826  <http://tools.ietf.org/html/rfc3826>].
> >>
> >> RFC 6988 notes the need for privacy protections for stored data, which
> the above text does not speak to, so I still think a
> >> reference to RFC 6988 would add value here.
> >>
> >> It is a little disconcerting that use of SNMPv3 is provided as a
SHOULD-
> level requirement without discussion of deployment
> >> scenarios and regardless of the sensitivity of the data being made
> available by any new MIB. For example, the tradeoffs between
> >> security and utility might be reasonable if (1) I'm using an older SNMP
> version on my closed home network to monitor my own energy
> >> use, but not if (2) my ISP is using it to monitor the same thing. The
text
> quoted above basically  endorses unauthorized energy
> >> monitoring if the provider does not support SNMPv3, whereas it seems
> like what we would want to be saying is that in cases like
> >> (2) SNMPv3 is required.
> >>
> >> I understand that this is basically boilerplate language for MIB docs,
so I'm
> not sure what can be done, but it seems unfortunate.
> >>
> >> Alissa
> >>
> >>
> >>
> >>>
----------------------------------------------------------------------
> >>>     COMMENT:
> >>>
----------------------------------------------------------------------
> >>>
> >>>     Section 12.1:
> >>>     "New Assignments (and potential deprecation) to Power State Sets
> >>>              shall be administered by IANA and the guidelines and
procedures
> >>>              are specified in [EMAN-FMWK], and will, as a consequence,
the
> >>>              IANAPowerStateSet Textual Convention should be updated."
> >>>
> >>>     Not sure what this sentence means.
> >>     Good catch.
> >>     NEW:
> >>
> >>              "New Assignments (and potential deprecation) to Power
State Sets
> >>              shall be administered by IANA and the guidelines and
procedures
> >>              are specified in [EMAN-FMWK], and will, as a consequence,
update
> the
> >>              IANAPowerStateSet Textual Convention."
> >>
> >>
> >>     Regards, Benoit (as a document author)
> >>
> >>
> >>
> >>
> >>
> >> _______________________________________________
> >> 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


From nobody Thu Jul 10 20:29:56 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 A77431A028B for <mib-doctors@ietfa.amsl.com>; Thu, 10 Jul 2014 20:29:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.651
X-Spam-Level: 
X-Spam-Status: No, score=-2.651 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0aJCM8LL89Gf for <mib-doctors@ietfa.amsl.com>; Thu, 10 Jul 2014 20:29:52 -0700 (PDT)
Received: from qmta02.westchester.pa.mail.comcast.net (qmta02.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:24]) by ietfa.amsl.com (Postfix) with ESMTP id 3E7A61A020A for <mib-doctors@ietf.org>; Thu, 10 Jul 2014 20:29:52 -0700 (PDT)
Received: from omta13.westchester.pa.mail.comcast.net ([76.96.62.52]) by qmta02.westchester.pa.mail.comcast.net with comcast id QrV81o00317dt5G51rVrvA; Fri, 11 Jul 2014 03:29:51 +0000
Received: from JV6RVH1 ([67.189.237.137]) by omta13.westchester.pa.mail.comcast.net with comcast id QrVq1o00D2yZEBF3ZrVqnr; Fri, 11 Jul 2014 03:29:51 +0000
From: "ietfdbh" <ietfdbh@comcast.net>
To: "'Benoit Claise'" <bclaise@cisco.com>, "'Thomas D. Nadeau'" <tnadeau@lucidvision.com>, "'Bert Wijnen \(IETF\)'" <bertietf@bwijnen.net>
References: <CFE17DDA.458C3%alissa@cooperw.in> <53BC5081.6090809@cisco.com> <53BD6690.2040102@cisco.com> <53BE3D7E.2090302@bwijnen.net> <35D0B6EE-BEC2-44EB-869B-CBE462FE3CAB@lucidvision.com> <53BE9A98.8020805@cisco.com>
In-Reply-To: <53BE9A98.8020805@cisco.com>
Date: Thu, 10 Jul 2014 23:29:49 -0400
Message-ID: <03b501cf9cb8$5f3ef230$1dbcd690$@comcast.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQFl8rZKGe1/GoUrOyAIbnSi/UNwbgJVJfCQAeLZGl0Bnx6yJAGmNG1/Af5ibAacIa0TUA==
Content-Language: en-us
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1405049391; bh=yfBsT7pa4YMEWSDQR7cHoOcAIyYVsLV27lwy9ET/h8M=; h=Received:Received:From:To:Subject:Date:Message-ID:MIME-Version: Content-Type; b=RzIPolY/ezMSL7/hqqb4FAXwmn+YvhOEnXKzvgSZToMEQvH31/2wWrqyrujxJGAAy s+LLj999IHIAD+qCHWWTS8H+jt2QZYNZuahySkX7Mtnso+27ZFAIroaE3G+0FYEcLb /4058v9jwF0jkfIfcb6RhNxLpmGYPzTPG4BAzvTYa7A5L02BWNOAHyb3nWozfXXgf7 h+3t92R+1fMWzAP02pUyItPSBOSRMkLpsGueXo9HAQBuEcEtbyDoWNfENDANWteG+5 qCVTFS83wx+m0Atb5OwnE3woqWt+KYK/X0D4CknqdNdNMfL8R35SSCZdhSpVg2i8Rn +qtQh7lknn4SQ==
Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/X-dkCNY4kkRsjOdh5sbrJ-PMCmo
Cc: "'MIB Doctors \(E-mail\)'" <mib-doctors@ietf.org>, 'Alissa Cooper' <alissa@cooperw.in>, sec-ads@tools.ietf.org, 'Farrel Adrian' <adrian@olddog.co.uk>
Subject: Re: [MIB-DOCTORS] Change the boilerplate - Kathleen'DISCUSS point 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, 11 Jul 2014 03:29:54 -0000

I think the new text is wordier, but doesn't really say more than the
original.
The devices being vulnerable to attack can have a negative effect on network
behavior.
I feat that readers of the wordier text would "tune out".

Rather than putting more details into the boilerplate, concerns should be
detailed in the security considerations, including an explanation of which
objects are sensitive, and how they increase vulnerability or impact network
behavior.

David Harrington
ietfdbh@comcast.net
+1-603-828-1401
> -----Original Message-----
> From: MIB-DOCTORS [mailto:mib-doctors-bounces@ietf.org] On Behalf Of
> Benoit Claise
> Sent: Thursday, July 10, 2014 9:52 AM
> To: Thomas D. Nadeau; Bert Wijnen (IETF)
> Cc: MIB Doctors (E-mail); Alissa Cooper; sec-ads@tools.ietf.org; Farrel
Adrian
> Subject: Re: [MIB-DOCTORS] Change the boilerplate - Kathleen'DISCUSS
> point 2
> 
> Dear all,
> 
> Let's try to address one point at a time, and get closure one by one.
> https://datatracker.ietf.org/doc/draft-ietf-eman-energy-aware-
> mib/ballot/#kathleen-moriarty
> 
> Kathleen proposes:
> OLD:
> 
>     "The
>     support for SET operations in a non-secure environment without proper
>     protection can have a negative effect on network operations."
> 
> NEW:
> 
>     "The
>     support for SET operations in a non-secure environment without proper
>     protection can have a negative effect on network operations or leave
>     cyber physical devices used by individuals, homes, and business
>     vulnerable to attack."
> 
> 
> I believe this new proposal makes sense. Does anybody object?
> 
> Regards, Benoit
> 
> > On Jul 10, 2014:3:15 AM, at 3:15 AM, Bert Wijnen (IETF)
> <bertietf@bwijnen.net> wrote:
> >
> >> it is always interesting to see that when we get new ADs that we must
> rediscuss this whole topic.
> > 	This is precisely one of the things that is broken about the IETF
these
> days, if you ask me: the re-re-re-discussion of topics at the 11:59th hour
of a
> document's progress through the gauntlet.
> >
> >> But yes, there are/were implementations/deployments where one uses
> dedicated (secure) networks
> >> for the network management systems, and so that would work under a
> SHOULD.
> > 	I agree. Not all network operators use a secure management
> network, but many do.
> >
> >> I do not recall if that was/is the only reason why we agreed on a
SHOULD
> instead of MUST.
> > 	I don't think you can do a MUST here; not everyone uses v3 - in
fact, I
> think if you poll implementations you'll find VERY FEW using v3.
> >
> > 	--Tom
> >
> >
> >
> >> Bert
> >>
> >> On 09/07/14 17:58, Benoit Claise wrote:
> >>> MIB doctors,
> >>>
> >>> Let me focus the discussion a little bit.
> >>> Alissa refers to this sentence in the boilerplate at
> http://trac.tools.ietf.org/area/ops/trac/wiki/mib-security
> >>>
> >>>         Implementations SHOULD provide the security features described
> by the
> >>>         SNMPv3 framework (see [RFC3410]), and implementations claiming
> compliance
> >>>         to the SNMPv3 standard MUST include full support for
> authentication and
> >>>         privacy via the User-based Security Model (USM) [RFC3414] with
the
> AES
> >>>         cipher algorithm [RFC3826].
> >>>
> >>>
> >>> Alissa's feedback is:
> >>>
> >>>     It is a little disconcerting that use of SNMPv3 is provided as a
SHOULD-
> level requirement without discussion of deployment
> >>>     scenarios and regardless of the sensitivity of the data being made
> available by any new MIB. For example, the tradeoffs between
> >>>     security and utility might be reasonable if (1) I'm using an older
SNMP
> version on my closed home network to monitor my own
> >>>     energy use, but not if (2) my ISP is using it to monitor the same
thing.
> The text quoted above basically  endorses unauthorized
> >>>     energy monitoring if the provider does not support SNMPv3, whereas
> it seems like what we would want to be saying is that in
> >>>     cases like (2) SNMPv3 is required.
> >>>
> >>> Can one of the old timers (who was part of the discussion) explain the
> SHOULD rational? Personally, I can see two use cases in favor
> >>> off the SHOULD: an older SNMP version in a closed network,  or a
private
> data communication network dedicated to network management
> >>> with special protection out of SNMP (like encrypted tunnel)
> >>>
> >>> Should we now modify this sentence to say?
> >>>
> >>>     MUST provide the security features described by the
> >>>     SNMPv3 framework (see [RFC3410])
> >>>
> >>> Regards, Benoit
> >>>
> >>>> MIB doctors,
> >>>>
> >>>> It seems that the "Security Guidelines for IETF MIB modules" receives
> comment for each MIB module submitted to the IESG.
> >>>> Is it time to modify it, or are we redoing the same discussions over
and
> over?
> >>>>
> >>>> Regards, Benoit
> >>>>
> >>>>
> >>>> -------- Original Message --------
> >>>> Subject: 	Re: Alissa Cooper's Discuss on
draft-ietf-eman-energy-
> monitoring-mib-12: (with DISCUSS and COMMENT)
> >>>> Date: 	Tue, 8 Jul 2014 13:02:50 -0700
> >>>> From: 	Alissa Cooper <alissa@cooperw.in>
> >>>> To: 	Benoit Claise <bclaise@cisco.com>, The IESG <iesg@ietf.org>
> >>>> CC: 	<draft-ietf-eman-energy-monitoring-mib@tools.ietf.org>,
> <eman-chairs@tools.ietf.org>
> >>>>
> >>>>
> >>>>
> >>>> Hi Benoit,
> >>>>
> >>>> On 7/8/14, 1:44 AM, "Benoit Claise" <bclaise@cisco.com
> <mailto:bclaise@cisco.com>> wrote:
> >>>>
> >>>>     Hi Alissa,
> >>>>
> >>>>     Thanks for your review.
> >>>>>     Alissa Cooper has entered the following ballot position for
> >>>>>     draft-ietf-eman-energy-monitoring-mib-12: Discuss
> >>>>>
> >>>>>     When responding, please keep the subject line intact and reply
to
> all
> >>>>>     email addresses included in the To and CC lines. (Feel free to
cut this
> >>>>>     introductory paragraph, however.)
> >>>>>
> >>>>>
> >>>>>     Please refer tohttp://www.ietf.org/iesg/statement/discuss-
> criteria.html
> >>>>>     for more information about IESG DISCUSS and COMMENT positions.
> >>>>>
> >>>>>
> >>>>>     The document, along with other ballot positions, can be found
here:
> >>>>>     http://datatracker.ietf.org/doc/draft-ietf-eman-energy-
> monitoring-mib/
> >>>>>
> >>>>>
> >>>>>
> >>>>>
----------------------------------------------------------------------
> >>>>>     DISCUSS:
> >>>>>
----------------------------------------------------------------------
> >>>>>
> >>>>>     Section 11 is missing a discussion of the privacy considerations
of
> >>>>>     energy and power monitoring. I would suggest something along the
> lines of
> >>>>>     the following:
> >>>>>
> >>>>>     "In certain situations, energy and power monitoring can reveal
> sensitive
> >>>>>     information about individuals' activities and habits.
Implementors of
> >>>>>     this specification should use appropriate privacy protections as
> >>>>>     discussed in Section 9 of RFC 6988 and monitoring of individuals
and
> >>>>>     homes should only occur with proper authorization."
> >>>>     Regarding your first sentence, I propose the following text,
which
> would be in line with Security Guidelines for IETF MIB
> >>>>     modules at
http://trac.tools.ietf.org/area/ops/trac/wiki/mib-security
> >>>>
> >>>>         Some of the readable objects in this MIB module (i.e.,
objects with
> a
> >>>>         MAX-ACCESS other than not-accessible) may be considered
> sensitive or
> >>>>         vulnerable in some network environments.  It is thus
important to
> >>>>         control even GET and/or NOTIFY access to these objects and
> possibly
> >>>>         to even encrypt the values of these objects when sending them
> over
> >>>>         the network via SNMP.  These are the tables and objects and
their
> >>>>         sensitivity/vulnerability:
> >>>>
> >>>>         Access to the content of the eoPowerStateTable,
eoEnergyTable,
> and
> >>>>         eoACPwrAttributesTable MIB tables can reveal sensitive
> >>>>         information about individuals' activities and habits
> >>>>
> >>>> Sounds good to me.
> >>>>
> >>>>
> >>>>     Since this document is essentially a MIB module, your last
sentence is
> covered by
> >>>>
> >>>>              implementations
> >>>>              claiming compliance to the SNMPv3 standard MUST include
full
> >>>>              support for authentication and privacy via the
User-based
> >>>>              Security Model (USM) [RFC3414
> <http://tools.ietf.org/html/rfc3414>] with the AES cipher algorithm
> >>>>              [RFC3826  <http://tools.ietf.org/html/rfc3826>].
> >>>>
> >>>> RFC 6988 notes the need for privacy protections for stored data,
which
> the above text does not speak to, so I still think a
> >>>> reference to RFC 6988 would add value here.
> >>>>
> >>>> It is a little disconcerting that use of SNMPv3 is provided as a
SHOULD-
> level requirement without discussion of deployment
> >>>> scenarios and regardless of the sensitivity of the data being made
> available by any new MIB. For example, the tradeoffs between
> >>>> security and utility might be reasonable if (1) I'm using an older
SNMP
> version on my closed home network to monitor my own energy
> >>>> use, but not if (2) my ISP is using it to monitor the same thing. The
text
> quoted above basically  endorses unauthorized energy
> >>>> monitoring if the provider does not support SNMPv3, whereas it seems
> like what we would want to be saying is that in cases like
> >>>> (2) SNMPv3 is required.
> >>>>
> >>>> I understand that this is basically boilerplate language for MIB
docs, so
> I'm not sure what can be done, but it seems unfortunate.
> >>>>
> >>>> Alissa
> >>>>
> >>>>
> >>>>
> >>>>>
----------------------------------------------------------------------
> >>>>>     COMMENT:
> >>>>>
----------------------------------------------------------------------
> >>>>>
> >>>>>     Section 12.1:
> >>>>>     "New Assignments (and potential deprecation) to Power State Sets
> >>>>>              shall be administered by IANA and the guidelines and
> procedures
> >>>>>              are specified in [EMAN-FMWK], and will, as a
consequence, the
> >>>>>              IANAPowerStateSet Textual Convention should be
updated."
> >>>>>
> >>>>>     Not sure what this sentence means.
> >>>>     Good catch.
> >>>>     NEW:
> >>>>
> >>>>              "New Assignments (and potential deprecation) to Power
State
> Sets
> >>>>              shall be administered by IANA and the guidelines and
> procedures
> >>>>              are specified in [EMAN-FMWK], and will, as a
consequence,
> update the
> >>>>              IANAPowerStateSet Textual Convention."
> >>>>
> >>>>
> >>>>     Regards, Benoit (as a document author)
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> _______________________________________________
> >>>> 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


From nobody Thu Jul 10 20:31:53 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 20AF51A028B for <mib-doctors@ietfa.amsl.com>; Thu, 10 Jul 2014 20:31:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.651
X-Spam-Level: 
X-Spam-Status: No, score=-2.651 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5eejBOH5E6eE for <mib-doctors@ietfa.amsl.com>; Thu, 10 Jul 2014 20:31:50 -0700 (PDT)
Received: from qmta03.westchester.pa.mail.comcast.net (qmta03.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:32]) by ietfa.amsl.com (Postfix) with ESMTP id 79E161A020A for <mib-doctors@ietf.org>; Thu, 10 Jul 2014 20:31:50 -0700 (PDT)
Received: from omta11.westchester.pa.mail.comcast.net ([76.96.62.36]) by qmta03.westchester.pa.mail.comcast.net with comcast id QrTG1o0080mv7h053rXqAT; Fri, 11 Jul 2014 03:31:50 +0000
Received: from JV6RVH1 ([67.189.237.137]) by omta11.westchester.pa.mail.comcast.net with comcast id QrXp1o00A2yZEBF3XrXpvu; Fri, 11 Jul 2014 03:31:50 +0000
From: "ietfdbh" <ietfdbh@comcast.net>
To: "'Juergen Schoenwaelder'" <j.schoenwaelder@jacobs-university.de>, "'Benoit Claise'" <bclaise@cisco.com>
References: <CFE17DDA.458C3%alissa@cooperw.in> <53BC5081.6090809@cisco.com> <53BD6690.2040102@cisco.com> <53BE3D7E.2090302@bwijnen.net> <9904FB1B0159DA42B0B887B7FA8119CA5C83CC03@AZ-FFEXMB04.global.avaya.com> <53BE9F74.9080705@cisco.com> <20140710151138.GB90581@elstar.local>
In-Reply-To: <20140710151138.GB90581@elstar.local>
Date: Thu, 10 Jul 2014 23:31:47 -0400
Message-ID: <03b601cf9cb8$a5d1f670$f175e350$@comcast.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQFl8rZKGe1/GoUrOyAIbnSi/UNwbgJVJfCQAeLZGl0Bnx6yJAI0KPZzAi+DyFYBjLkK6pwPT7UQ
Content-Language: en-us
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1405049510; bh=1k0K79Df1q/EkEZQqZ8wXuJlbi/Jf0SYMARCq0Wg1E4=; h=Received:Received:From:To:Subject:Date:Message-ID:MIME-Version: Content-Type; b=PXWdWKC2LyZAQkK0WdYHLe9XSQpl/WOb+xqcXSFKHoNl5dfF10Q2LEOEIw/6IEvmC 12023d6MXnYk1PxIPRfqUIEjNTB//6XywOsqR/Mf06S6XWx87WjsuuWLRZk2+oV7hA ZIanfz1KPUGDuzWJzldJj9W3S7VVSymgTqIDwNBO2IG4PWF55R+dM4mkK/1qtKRkEz 4tSli6QEWzzzUk57Jrzb+lYgoM9tIlMbSjJczcifrHmHvAE0FxOiDVJMnoh8pDAgCy kfM35Yz1fJMWZiecruarn2aSHecPPghj/zc1tDosFF9K8NzqV0VPftKmy4o0dKDvLb vbo4qQAsBqeVg==
Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/Ug8_V5bNDCt8TlYYvfs2bzLXo80
Cc: "'MIB Doctors \(E-mail\)'" <mib-doctors@ietf.org>, 'Alissa Cooper' <alissa@cooperw.in>, sec-ads@tools.ietf.org, 'Adrian Farrel' <adrian@olddog.co.uk>
Subject: Re: [MIB-DOCTORS] Change the boilerplate - Alissa's DISCUSS
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, 11 Jul 2014 03:31:53 -0000

+1 
;-)

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

> -----Original Message-----
> From: MIB-DOCTORS [mailto:mib-doctors-bounces@ietf.org] On Behalf Of
> Juergen Schoenwaelder
> Sent: Thursday, July 10, 2014 11:12 AM
> To: Benoit Claise
> Cc: MIB Doctors (E-mail); 'Alissa Cooper'; sec-ads@tools.ietf.org; Adrian
> Farrel
> Subject: Re: [MIB-DOCTORS] Change the boilerplate - Alissa's DISCUSS
> 
> On Thu, Jul 10, 2014 at 04:13:08PM +0200, Benoit Claise wrote:
> > Dear all,
> >
> > The email below refers to Alissa's DISCUSS
> > See
> > http://datatracker.ietf.org/doc/draft-ietf-eman-energy-monitoring-
> mib/ballot/#alissa-cooper
> >
> > Alissa refers to this sentence in the boilerplate at
> > http://trac.tools.ietf.org/area/ops/trac/wiki/mib-security
> >
> >         Implementations SHOULD provide the security features described
> > by the
> >         SNMPv3 framework (see [RFC3410]), and implementations claiming
> > compliance
> >         to the SNMPv3 standard MUST include full support for
> > authentication and
> >         privacy via the User-based Security Model (USM) [RFC3414] with
> > the AES
> >         cipher algorithm [RFC3826].
> >
> > From the discussion (Dan andBert's feedback, on top of mine) , it seems
> > that there are valid reasons to keep a SHOULD here in the generic
> > boilerplate.
> >
> > So what next?
> > - Should we justify the reasons in the boiler plate
> > - Should we  give some freedom in the boilerplate?
> >
> >         Implementations SHOULD provide the security features described
> > by the
> >         SNMPv3 framework (see [RFC3410]), and implementations claiming
> > compliance
> >         to the SNMPv3 standard MUST include full support for
> > authentication and
> >         privacy via the User-based Security Model (USM) [RFC3414] with
> > the AES
> >         cipher algorithm [RFC3826].
> >
> >         <if there are use cases where a MUST is required, described
> > them here>
> >
> >   Now, I hope it will not be abused by Security ADs, requesting a MUST
> > for every single MIB module.
> > - Something else?
> > - Stop writing MIB modules :-)
> >
> 
> Do nothing, re-discuss this every other year. ;-)
> 
> /js
> 
> --
> Juergen Schoenwaelder           Jacobs University Bremen gGmbH
> Phone: +49 421 200 3587         Campus Ring 1, 28759 Bremen, Germany
> Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>
> 
> _______________________________________________
> MIB-DOCTORS mailing list
> MIB-DOCTORS@ietf.org
> https://www.ietf.org/mailman/listinfo/mib-doctors


From nobody Thu Jul 10 20:34:19 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 A40071A0417 for <mib-doctors@ietfa.amsl.com>; Thu, 10 Jul 2014 20:34:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.651
X-Spam-Level: 
X-Spam-Status: No, score=-2.651 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vyImQG5YV-Fb for <mib-doctors@ietfa.amsl.com>; Thu, 10 Jul 2014 20:34:16 -0700 (PDT)
Received: from qmta03.westchester.pa.mail.comcast.net (qmta03.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:32]) by ietfa.amsl.com (Postfix) with ESMTP id 8A7461A0403 for <mib-doctors@ietf.org>; Thu, 10 Jul 2014 20:34:16 -0700 (PDT)
Received: from omta15.westchester.pa.mail.comcast.net ([76.96.62.87]) by qmta03.westchester.pa.mail.comcast.net with comcast id QrNm1o0011swQuc53raGJx; Fri, 11 Jul 2014 03:34:16 +0000
Received: from JV6RVH1 ([67.189.237.137]) by omta15.westchester.pa.mail.comcast.net with comcast id QraF1o00Q2yZEBF3braFba; Fri, 11 Jul 2014 03:34:16 +0000
From: "ietfdbh" <ietfdbh@comcast.net>
To: "'Alissa Cooper'" <alissa@cooperw.in>, "'Juergen Schoenwaelder'" <j.schoenwaelder@jacobs-university.de>, "'Benoit Claise'" <bclaise@cisco.com>
References: <CFE17DDA.458C3%alissa@cooperw.in> <53BC5081.6090809@cisco.com> <53BD6690.2040102@cisco.com> <53BE3D7E.2090302@bwijnen.net> <9904FB1B0159DA42B0B887B7FA8119CA5C83CC03@AZ-FFEXMB04.global.avaya.com> <53BE9F74.9080705@cisco.com> <20140710151138.GB90581@elstar.local> <CFE3FCE9.45FFF%alissa@cooperw.in>
In-Reply-To: <CFE3FCE9.45FFF%alissa@cooperw.in>
Date: Thu, 10 Jul 2014 23:34:14 -0400
Message-ID: <03b701cf9cb8$fce056f0$f6a104d0$@comcast.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQFl8rZKGe1/GoUrOyAIbnSi/UNwbgJVJfCQAeLZGl0Bnx6yJAI0KPZzAi+DyFYBjLkK6gEvfGyqnAXUgAA=
Content-Language: en-us
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1405049656; bh=AOkqHWw98ByC1jqfaUYzn4rDR0bb/JMevalBKQv4VPE=; h=Received:Received:From:To:Subject:Date:Message-ID:MIME-Version: Content-Type; b=P/sUzbFZoAt3reTyq/w8OZi7AbtMNjeX5vC21xMrMyg9DUMKrMoo9OvEwhqy3+RWj 2kMN/mnSysElHbqMZJLkBeN+K+vbB/d/9E0JMVRdK3baHlN3aHXo1WmzlkSPbISwyp Hyj/wqHL91OORxVFNPzcGTgWaCWZ3f9H6TK72XeQWwUPvYMhbiwPtnorh34nuCVbHm ooZ/sR3qyZjlNH5iLP5kTLlPaXs3sWZYSs1dDYEH6gaZGsEyxTohUwAqZWtUU5uu3b 4I8Ik5wz++ea5wpQcog+/iLQAfM2Qw9/aHXLfmDXvZR8JJmH/4mZgQss05kpWcDsiH 3rzl5TF+K/1Og==
Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/2NQF_XPEr_3X67uTTZ4BzgvSD7o
Cc: 'Adrian Farrel' <adrian@olddog.co.uk>, sec-ads@tools.ietf.org, "'MIB Doctors \(E-mail\)'" <mib-doctors@ietf.org>
Subject: Re: [MIB-DOCTORS] Change the boilerplate - Alissa's DISCUSS
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, 11 Jul 2014 03:34:18 -0000

" adding a special section or extra text to discuss privacy
concerns in the IoT-related documents is the right way to go."

+1

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

> -----Original Message-----
> From: MIB-DOCTORS [mailto:mib-doctors-bounces@ietf.org] On Behalf Of
> Alissa Cooper
> Sent: Thursday, July 10, 2014 11:28 AM
> To: Juergen Schoenwaelder; Benoit Claise
> Cc: Adrian Farrel; sec-ads@tools.ietf.org; MIB Doctors (E-mail)
> Subject: Re: [MIB-DOCTORS] Change the boilerplate - Alissa's DISCUSS
>=20
> Perhaps rather than re-discussing the boilerplate, we could discuss =
what
> the purpose of the boilerplate is.
>=20
> If the purpose of the boilerplate is to provide text that authors can =
look
> at and say, =E2=80=9Cyes, in the case of this document, the =
boilerplate fully
> covers the security considerations of the MIB being =
specified,=E2=80=9D then I
> think it=E2=80=99s a great thing to have. If the purpose of the =
boilerplate is to
> keep any additional security consideration not covered in the =
boilerplate
> from being addressed in a MIB document, then it seems overly =
constricting.
>=20
> Security considerations change over time. I=E2=80=99m assuming that =
home/device
> energy monitoring wasn=E2=80=99t really top of mind when SNMP was =
developed or
> when the boilerplate was originally written. So it=E2=80=99s not =
surprising that
> new security issues are arising that aren=E2=80=99t addressed within =
the
> boilerplate. If the boilerplate were just a suggestion of text and not =
a
> limitation on what can be documented, we could accommodate the =
changing
> times fairly easily.
>=20
> In my original DISCUSS, all I suggested was text that could be =
provided in
> addition to the boilerplate:
>=20
> "In certain situations, energy and power monitoring can reveal =
sensitive
> information about individuals' activities and habits. Implementors of =
this
> specification should use appropriate privacy protections as discussed =
in
> Section 9 of RFC 6988 and monitoring of individuals and homes should =
only
> occur
> with proper authorization.=E2=80=9D
>=20
> I have not had time to look at Stephen=E2=80=99s comments but I agree =
with him and
> Bert that adding a special section or extra text to discuss privacy
> concerns in the IoT-related documents is the right way to go.
>=20
> Alissa
>=20
>=20
> On 7/10/14, 8:11 AM, "Juergen Schoenwaelder"
> <j.schoenwaelder@jacobs-university.de> wrote:
>=20
> >On Thu, Jul 10, 2014 at 04:13:08PM +0200, Benoit Claise wrote:
> >> Dear all,
> >>
> >> The email below refers to Alissa's DISCUSS
> >> See
> >>
> >>http://datatracker.ietf.org/doc/draft-ietf-eman-energy-monitoring-
> mib/bal
> >>lot/#alissa-cooper
> >>
> >> Alissa refers to this sentence in the boilerplate at
> >> http://trac.tools.ietf.org/area/ops/trac/wiki/mib-security
> >>
> >>         Implementations SHOULD provide the security features =
described
> >> by the
> >>         SNMPv3 framework (see [RFC3410]), and implementations =
claiming
> >> compliance
> >>         to the SNMPv3 standard MUST include full support for
> >> authentication and
> >>         privacy via the User-based Security Model (USM) [RFC3414] =
with
> >> the AES
> >>         cipher algorithm [RFC3826].
> >>
> >> From the discussion (Dan andBert's feedback, on top of mine) , it =
seems
> >> that there are valid reasons to keep a SHOULD here in the generic
> >> boilerplate.
> >>
> >> So what next?
> >> - Should we justify the reasons in the boiler plate
> >> - Should we  give some freedom in the boilerplate?
> >>
> >>         Implementations SHOULD provide the security features =
described
> >> by the
> >>         SNMPv3 framework (see [RFC3410]), and implementations =
claiming
> >> compliance
> >>         to the SNMPv3 standard MUST include full support for
> >> authentication and
> >>         privacy via the User-based Security Model (USM) [RFC3414] =
with
> >> the AES
> >>         cipher algorithm [RFC3826].
> >>
> >>         <if there are use cases where a MUST is required, described
> >> them here>
> >>
> >>   Now, I hope it will not be abused by Security ADs, requesting a =
MUST
> >> for every single MIB module.
> >> - Something else?
> >> - Stop writing MIB modules :-)
> >>
> >
> >Do nothing, re-discuss this every other year. ;-)
> >
> >/js
> >
> >--
> >Juergen Schoenwaelder           Jacobs University Bremen gGmbH
> >Phone: +49 421 200 3587         Campus Ring 1, 28759 Bremen, Germany
> >Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>
>=20
>=20
> _______________________________________________
> MIB-DOCTORS mailing list
> MIB-DOCTORS@ietf.org
> https://www.ietf.org/mailman/listinfo/mib-doctors


From nobody Fri Jul 11 07:33:34 2014
Return-Path: <kathleen.moriarty.ietf@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 F31491B2B62 for <mib-doctors@ietfa.amsl.com>; Fri, 11 Jul 2014 07:33:31 -0700 (PDT)
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, FREEMAIL_FROM=0.001, HTML_MESSAGE=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 O-6x2O_SprtV for <mib-doctors@ietfa.amsl.com>; Fri, 11 Jul 2014 07:33:24 -0700 (PDT)
Received: from mail-la0-x231.google.com (mail-la0-x231.google.com [IPv6:2a00:1450:4010:c03::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B0B081B2B5B for <mib-doctors@ietf.org>; Fri, 11 Jul 2014 07:33:23 -0700 (PDT)
Received: by mail-la0-f49.google.com with SMTP id gf5so926687lab.8 for <mib-doctors@ietf.org>; Fri, 11 Jul 2014 07:33:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=PVnWKOwTmSZqOaFJFXb8Sa1wHCDShIoU1KkpTheQypU=; b=vDZqlqklZ2atag/oTQE5s6V4tKen3FjKca1qVN0dp/baVMe39IoSoXoviUTWdH5OuW 55Yejuq+6EgX/0oqIuF6cNnftMO5mfCc0tzQ+J3iAaq+p8S8A7QcU2gRqXwhbSmdNuRT Bj3eRoeAi1jk1gCL2XBhiW5V5x7Pi7jHI02vtGeRmzOwvMVbbC0AH6V5JXITKye44aIp eSkcoUTUxVFy19rjWIgNonv+OUq98SiXft01uOeqCLoObjX7G9dBtO+n49g5bLsbAIpn kp8A0sKlFJGGkJcu9tUxAS0ZKQujsaevqjt5EDff8PecLA4PMfV+w9m6zgGWnpljtU3b TWvw==
MIME-Version: 1.0
X-Received: by 10.112.122.113 with SMTP id lr17mr1915334lbb.105.1405089201720;  Fri, 11 Jul 2014 07:33:21 -0700 (PDT)
Received: by 10.112.253.198 with HTTP; Fri, 11 Jul 2014 07:33:21 -0700 (PDT)
In-Reply-To: <03b501cf9cb8$5f3ef230$1dbcd690$@comcast.net>
References: <CFE17DDA.458C3%alissa@cooperw.in> <53BC5081.6090809@cisco.com> <53BD6690.2040102@cisco.com> <53BE3D7E.2090302@bwijnen.net> <35D0B6EE-BEC2-44EB-869B-CBE462FE3CAB@lucidvision.com> <53BE9A98.8020805@cisco.com> <03b501cf9cb8$5f3ef230$1dbcd690$@comcast.net>
Date: Fri, 11 Jul 2014 10:33:21 -0400
Message-ID: <CAHbuEH6+qapXzei9Rkf3-nMimKfQM6rPYK=z9G+Mps+mPbjcLg@mail.gmail.com>
From: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
To: ietfdbh <ietfdbh@comcast.net>
Content-Type: multipart/alternative; boundary=047d7bfcf74abf149804fdebd263
Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/M5qyXkzHvJcrK-tQzdfPcSyE2AI
Cc: "MIB Doctors \(E-mail\)" <mib-doctors@ietf.org>, Alissa Cooper <alissa@cooperw.in>, "<sec-ads@tools.ietf.org>" <sec-ads@tools.ietf.org>, Farrel Adrian <adrian@olddog.co.uk>
Subject: Re: [MIB-DOCTORS] Change the boilerplate - Kathleen'DISCUSS point 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, 11 Jul 2014 14:33:32 -0000

--047d7bfcf74abf149804fdebd263
Content-Type: text/plain; charset=UTF-8

David,

Do you have alternate text to suggest?  The point was to expand the
possibilities beyond just effecting the network.  Attacks exploiting
vulnerabilities, other than DoS or similar attacks, are not targeting
network disruption.  There is a lot of information that could be gathered
that privacy implications (individuals, homes, businesses), could effect
business (reconnaissance leading to simple attacks or even espionage, etc.
- this is very real), etc.

Thanks.


On Thu, Jul 10, 2014 at 11:29 PM, ietfdbh <ietfdbh@comcast.net> wrote:

> I think the new text is wordier, but doesn't really say more than the
> original.
> The devices being vulnerable to attack can have a negative effect on
> network
> behavior.
> I feat that readers of the wordier text would "tune out".
>
> Rather than putting more details into the boilerplate, concerns should be
> detailed in the security considerations, including an explanation of which
> objects are sensitive, and how they increase vulnerability or impact
> network
> behavior.
>
> David Harrington
> ietfdbh@comcast.net
> +1-603-828-1401
> > -----Original Message-----
> > From: MIB-DOCTORS [mailto:mib-doctors-bounces@ietf.org] On Behalf Of
> > Benoit Claise
> > Sent: Thursday, July 10, 2014 9:52 AM
> > To: Thomas D. Nadeau; Bert Wijnen (IETF)
> > Cc: MIB Doctors (E-mail); Alissa Cooper; sec-ads@tools.ietf.org; Farrel
> Adrian
> > Subject: Re: [MIB-DOCTORS] Change the boilerplate - Kathleen'DISCUSS
> > point 2
> >
> > Dear all,
> >
> > Let's try to address one point at a time, and get closure one by one.
> > https://datatracker.ietf.org/doc/draft-ietf-eman-energy-aware-
> > mib/ballot/#kathleen-moriarty
> >
> > Kathleen proposes:
> > OLD:
> >
> >     "The
> >     support for SET operations in a non-secure environment without proper
> >     protection can have a negative effect on network operations."
> >
> > NEW:
> >
> >     "The
> >     support for SET operations in a non-secure environment without proper
> >     protection can have a negative effect on network operations or leave
> >     cyber physical devices used by individuals, homes, and business
> >     vulnerable to attack."
> >
> >
> > I believe this new proposal makes sense. Does anybody object?
> >
> > Regards, Benoit
> >
> > > On Jul 10, 2014:3:15 AM, at 3:15 AM, Bert Wijnen (IETF)
> > <bertietf@bwijnen.net> wrote:
> > >
> > >> it is always interesting to see that when we get new ADs that we must
> > rediscuss this whole topic.
> > >     This is precisely one of the things that is broken about the IETF
> these
> > days, if you ask me: the re-re-re-discussion of topics at the 11:59th
> hour
> of a
> > document's progress through the gauntlet.
> > >
> > >> But yes, there are/were implementations/deployments where one uses
> > dedicated (secure) networks
> > >> for the network management systems, and so that would work under a
> > SHOULD.
> > >     I agree. Not all network operators use a secure management
> > network, but many do.
> > >
> > >> I do not recall if that was/is the only reason why we agreed on a
> SHOULD
> > instead of MUST.
> > >     I don't think you can do a MUST here; not everyone uses v3 - in
> fact, I
> > think if you poll implementations you'll find VERY FEW using v3.
> > >
> > >     --Tom
> > >
> > >
> > >
> > >> Bert
> > >>
> > >> On 09/07/14 17:58, Benoit Claise wrote:
> > >>> MIB doctors,
> > >>>
> > >>> Let me focus the discussion a little bit.
> > >>> Alissa refers to this sentence in the boilerplate at
> > http://trac.tools.ietf.org/area/ops/trac/wiki/mib-security
> > >>>
> > >>>         Implementations SHOULD provide the security features
> described
> > by the
> > >>>         SNMPv3 framework (see [RFC3410]), and implementations
> claiming
> > compliance
> > >>>         to the SNMPv3 standard MUST include full support for
> > authentication and
> > >>>         privacy via the User-based Security Model (USM) [RFC3414]
> with
> the
> > AES
> > >>>         cipher algorithm [RFC3826].
> > >>>
> > >>>
> > >>> Alissa's feedback is:
> > >>>
> > >>>     It is a little disconcerting that use of SNMPv3 is provided as a
> SHOULD-
> > level requirement without discussion of deployment
> > >>>     scenarios and regardless of the sensitivity of the data being
> made
> > available by any new MIB. For example, the tradeoffs between
> > >>>     security and utility might be reasonable if (1) I'm using an
> older
> SNMP
> > version on my closed home network to monitor my own
> > >>>     energy use, but not if (2) my ISP is using it to monitor the same
> thing.
> > The text quoted above basically  endorses unauthorized
> > >>>     energy monitoring if the provider does not support SNMPv3,
> whereas
> > it seems like what we would want to be saying is that in
> > >>>     cases like (2) SNMPv3 is required.
> > >>>
> > >>> Can one of the old timers (who was part of the discussion) explain
> the
> > SHOULD rational? Personally, I can see two use cases in favor
> > >>> off the SHOULD: an older SNMP version in a closed network,  or a
> private
> > data communication network dedicated to network management
> > >>> with special protection out of SNMP (like encrypted tunnel)
> > >>>
> > >>> Should we now modify this sentence to say?
> > >>>
> > >>>     MUST provide the security features described by the
> > >>>     SNMPv3 framework (see [RFC3410])
> > >>>
> > >>> Regards, Benoit
> > >>>
> > >>>> MIB doctors,
> > >>>>
> > >>>> It seems that the "Security Guidelines for IETF MIB modules"
> receives
> > comment for each MIB module submitted to the IESG.
> > >>>> Is it time to modify it, or are we redoing the same discussions over
> and
> > over?
> > >>>>
> > >>>> Regards, Benoit
> > >>>>
> > >>>>
> > >>>> -------- Original Message --------
> > >>>> Subject:         Re: Alissa Cooper's Discuss on
> draft-ietf-eman-energy-
> > monitoring-mib-12: (with DISCUSS and COMMENT)
> > >>>> Date:    Tue, 8 Jul 2014 13:02:50 -0700
> > >>>> From:    Alissa Cooper <alissa@cooperw.in>
> > >>>> To:      Benoit Claise <bclaise@cisco.com>, The IESG <iesg@ietf.org
> >
> > >>>> CC:      <draft-ietf-eman-energy-monitoring-mib@tools.ietf.org>,
> > <eman-chairs@tools.ietf.org>
> > >>>>
> > >>>>
> > >>>>
> > >>>> Hi Benoit,
> > >>>>
> > >>>> On 7/8/14, 1:44 AM, "Benoit Claise" <bclaise@cisco.com
> > <mailto:bclaise@cisco.com>> wrote:
> > >>>>
> > >>>>     Hi Alissa,
> > >>>>
> > >>>>     Thanks for your review.
> > >>>>>     Alissa Cooper has entered the following ballot position for
> > >>>>>     draft-ietf-eman-energy-monitoring-mib-12: Discuss
> > >>>>>
> > >>>>>     When responding, please keep the subject line intact and reply
> to
> > all
> > >>>>>     email addresses included in the To and CC lines. (Feel free to
> cut this
> > >>>>>     introductory paragraph, however.)
> > >>>>>
> > >>>>>
> > >>>>>     Please refer tohttp://www.ietf.org/iesg/statement/discuss-
> > criteria.html
> > >>>>>     for more information about IESG DISCUSS and COMMENT positions.
> > >>>>>
> > >>>>>
> > >>>>>     The document, along with other ballot positions, can be found
> here:
> > >>>>>     http://datatracker.ietf.org/doc/draft-ietf-eman-energy-
> > monitoring-mib/
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>>
> ----------------------------------------------------------------------
> > >>>>>     DISCUSS:
> > >>>>>
> ----------------------------------------------------------------------
> > >>>>>
> > >>>>>     Section 11 is missing a discussion of the privacy
> considerations
> of
> > >>>>>     energy and power monitoring. I would suggest something along
> the
> > lines of
> > >>>>>     the following:
> > >>>>>
> > >>>>>     "In certain situations, energy and power monitoring can reveal
> > sensitive
> > >>>>>     information about individuals' activities and habits.
> Implementors of
> > >>>>>     this specification should use appropriate privacy protections
> as
> > >>>>>     discussed in Section 9 of RFC 6988 and monitoring of
> individuals
> and
> > >>>>>     homes should only occur with proper authorization."
> > >>>>     Regarding your first sentence, I propose the following text,
> which
> > would be in line with Security Guidelines for IETF MIB
> > >>>>     modules at
> http://trac.tools.ietf.org/area/ops/trac/wiki/mib-security
> > >>>>
> > >>>>         Some of the readable objects in this MIB module (i.e.,
> objects with
> > a
> > >>>>         MAX-ACCESS other than not-accessible) may be considered
> > sensitive or
> > >>>>         vulnerable in some network environments.  It is thus
> important to
> > >>>>         control even GET and/or NOTIFY access to these objects and
> > possibly
> > >>>>         to even encrypt the values of these objects when sending
> them
> > over
> > >>>>         the network via SNMP.  These are the tables and objects and
> their
> > >>>>         sensitivity/vulnerability:
> > >>>>
> > >>>>         Access to the content of the eoPowerStateTable,
> eoEnergyTable,
> > and
> > >>>>         eoACPwrAttributesTable MIB tables can reveal sensitive
> > >>>>         information about individuals' activities and habits
> > >>>>
> > >>>> Sounds good to me.
> > >>>>
> > >>>>
> > >>>>     Since this document is essentially a MIB module, your last
> sentence is
> > covered by
> > >>>>
> > >>>>              implementations
> > >>>>              claiming compliance to the SNMPv3 standard MUST include
> full
> > >>>>              support for authentication and privacy via the
> User-based
> > >>>>              Security Model (USM) [RFC3414
> > <http://tools.ietf.org/html/rfc3414>] with the AES cipher algorithm
> > >>>>              [RFC3826  <http://tools.ietf.org/html/rfc3826>].
> > >>>>
> > >>>> RFC 6988 notes the need for privacy protections for stored data,
> which
> > the above text does not speak to, so I still think a
> > >>>> reference to RFC 6988 would add value here.
> > >>>>
> > >>>> It is a little disconcerting that use of SNMPv3 is provided as a
> SHOULD-
> > level requirement without discussion of deployment
> > >>>> scenarios and regardless of the sensitivity of the data being made
> > available by any new MIB. For example, the tradeoffs between
> > >>>> security and utility might be reasonable if (1) I'm using an older
> SNMP
> > version on my closed home network to monitor my own energy
> > >>>> use, but not if (2) my ISP is using it to monitor the same thing.
> The
> text
> > quoted above basically  endorses unauthorized energy
> > >>>> monitoring if the provider does not support SNMPv3, whereas it seems
> > like what we would want to be saying is that in cases like
> > >>>> (2) SNMPv3 is required.
> > >>>>
> > >>>> I understand that this is basically boilerplate language for MIB
> docs, so
> > I'm not sure what can be done, but it seems unfortunate.
> > >>>>
> > >>>> Alissa
> > >>>>
> > >>>>
> > >>>>
> > >>>>>
> ----------------------------------------------------------------------
> > >>>>>     COMMENT:
> > >>>>>
> ----------------------------------------------------------------------
> > >>>>>
> > >>>>>     Section 12.1:
> > >>>>>     "New Assignments (and potential deprecation) to Power State
> Sets
> > >>>>>              shall be administered by IANA and the guidelines and
> > procedures
> > >>>>>              are specified in [EMAN-FMWK], and will, as a
> consequence, the
> > >>>>>              IANAPowerStateSet Textual Convention should be
> updated."
> > >>>>>
> > >>>>>     Not sure what this sentence means.
> > >>>>     Good catch.
> > >>>>     NEW:
> > >>>>
> > >>>>              "New Assignments (and potential deprecation) to Power
> State
> > Sets
> > >>>>              shall be administered by IANA and the guidelines and
> > procedures
> > >>>>              are specified in [EMAN-FMWK], and will, as a
> consequence,
> > update the
> > >>>>              IANAPowerStateSet Textual Convention."
> > >>>>
> > >>>>
> > >>>>     Regards, Benoit (as a document author)
> > >>>>
> > >>>>
> > >>>>
> > >>>>
> > >>>>
> > >>>> _______________________________________________
> > >>>> 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
>
>


-- 

Best regards,
Kathleen

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

<div dir=3D"ltr">David,<div><br></div><div>Do you have alternate text to su=
ggest? =C2=A0The point was to expand the possibilities beyond just effectin=
g the network. =C2=A0Attacks exploiting vulnerabilities, other than DoS or =
similar attacks, are not targeting network disruption. =C2=A0There is a lot=
 of information that could be gathered that privacy implications (individua=
ls, homes, businesses), could effect business (reconnaissance leading to si=
mple attacks or even espionage, etc. - this is very real), etc.</div>
<div><br></div><div>Thanks.</div></div><div class=3D"gmail_extra"><br><br><=
div class=3D"gmail_quote">On Thu, Jul 10, 2014 at 11:29 PM, ietfdbh <span d=
ir=3D"ltr">&lt;<a href=3D"mailto:ietfdbh@comcast.net" target=3D"_blank">iet=
fdbh@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">I think the new text is wordier, but doesn&#=
39;t really say more than the<br>
original.<br>
The devices being vulnerable to attack can have a negative effect on networ=
k<br>
behavior.<br>
I feat that readers of the wordier text would &quot;tune out&quot;.<br>
<br>
Rather than putting more details into the boilerplate, concerns should be<b=
r>
detailed in the security considerations, including an explanation of which<=
br>
objects are sensitive, and how they increase vulnerability or impact networ=
k<br>
behavior.<br>
<br>
David Harrington<br>
<a href=3D"mailto:ietfdbh@comcast.net">ietfdbh@comcast.net</a><br>
<a href=3D"tel:%2B1-603-828-1401" value=3D"+16038281401">+1-603-828-1401</a=
><br>
<div class=3D"im HOEnZb">&gt; -----Original Message-----<br>
&gt; From: MIB-DOCTORS [mailto:<a href=3D"mailto:mib-doctors-bounces@ietf.o=
rg">mib-doctors-bounces@ietf.org</a>] On Behalf Of<br>
&gt; Benoit Claise<br>
&gt; Sent: Thursday, July 10, 2014 9:52 AM<br>
&gt; To: Thomas D. Nadeau; Bert Wijnen (IETF)<br>
&gt; Cc: MIB Doctors (E-mail); Alissa Cooper; <a href=3D"mailto:sec-ads@too=
ls.ietf.org">sec-ads@tools.ietf.org</a>; Farrel<br>
Adrian<br>
&gt; Subject: Re: [MIB-DOCTORS] Change the boilerplate - Kathleen&#39;DISCU=
SS<br>
&gt; point 2<br>
&gt;<br>
</div><div class=3D"HOEnZb"><div class=3D"h5">&gt; Dear all,<br>
&gt;<br>
&gt; Let&#39;s try to address one point at a time, and get closure one by o=
ne.<br>
&gt; <a href=3D"https://datatracker.ietf.org/doc/draft-ietf-eman-energy-awa=
re-" target=3D"_blank">https://datatracker.ietf.org/doc/draft-ietf-eman-ene=
rgy-aware-</a><br>
&gt; mib/ballot/#kathleen-moriarty<br>
&gt;<br>
&gt; Kathleen proposes:<br>
&gt; OLD:<br>
&gt;<br>
&gt; =C2=A0 =C2=A0 &quot;The<br>
&gt; =C2=A0 =C2=A0 support for SET operations in a non-secure environment w=
ithout proper<br>
&gt; =C2=A0 =C2=A0 protection can have a negative effect on network operati=
ons.&quot;<br>
&gt;<br>
&gt; NEW:<br>
&gt;<br>
&gt; =C2=A0 =C2=A0 &quot;The<br>
&gt; =C2=A0 =C2=A0 support for SET operations in a non-secure environment w=
ithout proper<br>
&gt; =C2=A0 =C2=A0 protection can have a negative effect on network operati=
ons or leave<br>
&gt; =C2=A0 =C2=A0 cyber physical devices used by individuals, homes, and b=
usiness<br>
&gt; =C2=A0 =C2=A0 vulnerable to attack.&quot;<br>
&gt;<br>
&gt;<br>
&gt; I believe this new proposal makes sense. Does anybody object?<br>
&gt;<br>
&gt; Regards, Benoit<br>
&gt;<br>
&gt; &gt; On Jul 10, 2014:3:15 AM, at 3:15 AM, Bert Wijnen (IETF)<br>
&gt; &lt;<a href=3D"mailto:bertietf@bwijnen.net">bertietf@bwijnen.net</a>&g=
t; wrote:<br>
&gt; &gt;<br>
&gt; &gt;&gt; it is always interesting to see that when we get new ADs that=
 we must<br>
&gt; rediscuss this whole topic.<br>
&gt; &gt; =C2=A0 =C2=A0 This is precisely one of the things that is broken =
about the IETF<br>
these<br>
&gt; days, if you ask me: the re-re-re-discussion of topics at the 11:59th =
hour<br>
of a<br>
&gt; document&#39;s progress through the gauntlet.<br>
&gt; &gt;<br>
&gt; &gt;&gt; But yes, there are/were implementations/deployments where one=
 uses<br>
&gt; dedicated (secure) networks<br>
&gt; &gt;&gt; for the network management systems, and so that would work un=
der a<br>
&gt; SHOULD.<br>
&gt; &gt; =C2=A0 =C2=A0 I agree. Not all network operators use a secure man=
agement<br>
&gt; network, but many do.<br>
&gt; &gt;<br>
&gt; &gt;&gt; I do not recall if that was/is the only reason why we agreed =
on a<br>
SHOULD<br>
&gt; instead of MUST.<br>
&gt; &gt; =C2=A0 =C2=A0 I don&#39;t think you can do a MUST here; not every=
one uses v3 - in<br>
fact, I<br>
&gt; think if you poll implementations you&#39;ll find VERY FEW using v3.<b=
r>
&gt; &gt;<br>
&gt; &gt; =C2=A0 =C2=A0 --Tom<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;&gt; Bert<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; On 09/07/14 17:58, Benoit Claise wrote:<br>
&gt; &gt;&gt;&gt; MIB doctors,<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt; Let me focus the discussion a little bit.<br>
&gt; &gt;&gt;&gt; Alissa refers to this sentence in the boilerplate at<br>
&gt; <a href=3D"http://trac.tools.ietf.org/area/ops/trac/wiki/mib-security"=
 target=3D"_blank">http://trac.tools.ietf.org/area/ops/trac/wiki/mib-securi=
ty</a><br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 Implementations SHOULD provid=
e the security features described<br>
&gt; by the<br>
&gt; &gt;&gt;&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 SNMPv3 framework (see [RFC341=
0]), and implementations claiming<br>
&gt; compliance<br>
&gt; &gt;&gt;&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 to the SNMPv3 standard MUST i=
nclude full support for<br>
&gt; authentication and<br>
&gt; &gt;&gt;&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 privacy via the User-based Se=
curity Model (USM) [RFC3414] with<br>
the<br>
&gt; AES<br>
&gt; &gt;&gt;&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 cipher algorithm [RFC3826].<b=
r>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt; Alissa&#39;s feedback is:<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt; =C2=A0 =C2=A0 It is a little disconcerting that use of SN=
MPv3 is provided as a<br>
SHOULD-<br>
&gt; level requirement without discussion of deployment<br>
&gt; &gt;&gt;&gt; =C2=A0 =C2=A0 scenarios and regardless of the sensitivity=
 of the data being made<br>
&gt; available by any new MIB. For example, the tradeoffs between<br>
&gt; &gt;&gt;&gt; =C2=A0 =C2=A0 security and utility might be reasonable if=
 (1) I&#39;m using an older<br>
SNMP<br>
&gt; version on my closed home network to monitor my own<br>
&gt; &gt;&gt;&gt; =C2=A0 =C2=A0 energy use, but not if (2) my ISP is using =
it to monitor the same<br>
thing.<br>
&gt; The text quoted above basically =C2=A0endorses unauthorized<br>
&gt; &gt;&gt;&gt; =C2=A0 =C2=A0 energy monitoring if the provider does not =
support SNMPv3, whereas<br>
&gt; it seems like what we would want to be saying is that in<br>
&gt; &gt;&gt;&gt; =C2=A0 =C2=A0 cases like (2) SNMPv3 is required.<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt; Can one of the old timers (who was part of the discussion=
) explain the<br>
&gt; SHOULD rational? Personally, I can see two use cases in favor<br>
&gt; &gt;&gt;&gt; off the SHOULD: an older SNMP version in a closed network=
, =C2=A0or a<br>
private<br>
&gt; data communication network dedicated to network management<br>
&gt; &gt;&gt;&gt; with special protection out of SNMP (like encrypted tunne=
l)<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt; Should we now modify this sentence to say?<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt; =C2=A0 =C2=A0 MUST provide the security features describe=
d by the<br>
&gt; &gt;&gt;&gt; =C2=A0 =C2=A0 SNMPv3 framework (see [RFC3410])<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt; Regards, Benoit<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; MIB doctors,<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; It seems that the &quot;Security Guidelines for IETF =
MIB modules&quot; receives<br>
&gt; comment for each MIB module submitted to the IESG.<br>
&gt; &gt;&gt;&gt;&gt; Is it time to modify it, or are we redoing the same d=
iscussions over<br>
and<br>
&gt; over?<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; Regards, Benoit<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; -------- Original Message --------<br>
&gt; &gt;&gt;&gt;&gt; Subject: =C2=A0 =C2=A0 =C2=A0 =C2=A0 Re: Alissa Coope=
r&#39;s Discuss on<br>
draft-ietf-eman-energy-<br>
&gt; monitoring-mib-12: (with DISCUSS and COMMENT)<br>
&gt; &gt;&gt;&gt;&gt; Date: =C2=A0 =C2=A0Tue, 8 Jul 2014 13:02:50 -0700<br>
&gt; &gt;&gt;&gt;&gt; From: =C2=A0 =C2=A0Alissa Cooper &lt;<a href=3D"mailt=
o:alissa@cooperw.in">alissa@cooperw.in</a>&gt;<br>
&gt; &gt;&gt;&gt;&gt; To: =C2=A0 =C2=A0 =C2=A0Benoit Claise &lt;<a href=3D"=
mailto:bclaise@cisco.com">bclaise@cisco.com</a>&gt;, The IESG &lt;<a href=
=3D"mailto:iesg@ietf.org">iesg@ietf.org</a>&gt;<br>
&gt; &gt;&gt;&gt;&gt; CC: =C2=A0 =C2=A0 =C2=A0&lt;<a href=3D"mailto:draft-i=
etf-eman-energy-monitoring-mib@tools.ietf.org">draft-ietf-eman-energy-monit=
oring-mib@tools.ietf.org</a>&gt;,<br>
&gt; &lt;<a href=3D"mailto:eman-chairs@tools.ietf.org">eman-chairs@tools.ie=
tf.org</a>&gt;<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; Hi Benoit,<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; On 7/8/14, 1:44 AM, &quot;Benoit Claise&quot; &lt;<a =
href=3D"mailto:bclaise@cisco.com">bclaise@cisco.com</a><br>
&gt; &lt;mailto:<a href=3D"mailto:bclaise@cisco.com">bclaise@cisco.com</a>&=
gt;&gt; wrote:<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; =C2=A0 =C2=A0 Hi Alissa,<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; =C2=A0 =C2=A0 Thanks for your review.<br>
&gt; &gt;&gt;&gt;&gt;&gt; =C2=A0 =C2=A0 Alissa Cooper has entered the follo=
wing ballot position for<br>
&gt; &gt;&gt;&gt;&gt;&gt; =C2=A0 =C2=A0 draft-ietf-eman-energy-monitoring-m=
ib-12: Discuss<br>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt; =C2=A0 =C2=A0 When responding, please keep the su=
bject line intact and reply<br>
to<br>
&gt; all<br>
&gt; &gt;&gt;&gt;&gt;&gt; =C2=A0 =C2=A0 email addresses included in the To =
and CC lines. (Feel free to<br>
cut this<br>
&gt; &gt;&gt;&gt;&gt;&gt; =C2=A0 =C2=A0 introductory paragraph, however.)<b=
r>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt; =C2=A0 =C2=A0 Please refer tohttp://<a href=3D"ht=
tp://www.ietf.org/iesg/statement/discuss-" target=3D"_blank">www.ietf.org/i=
esg/statement/discuss-</a><br>
&gt; criteria.html<br>
&gt; &gt;&gt;&gt;&gt;&gt; =C2=A0 =C2=A0 for more information about IESG DIS=
CUSS and COMMENT positions.<br>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt; =C2=A0 =C2=A0 The document, along with other ball=
ot positions, can be found<br>
here:<br>
&gt; &gt;&gt;&gt;&gt;&gt; =C2=A0 =C2=A0 <a href=3D"http://datatracker.ietf.=
org/doc/draft-ietf-eman-energy-" target=3D"_blank">http://datatracker.ietf.=
org/doc/draft-ietf-eman-energy-</a><br>
&gt; monitoring-mib/<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;<br>
----------------------------------------------------------------------<br>
&gt; &gt;&gt;&gt;&gt;&gt; =C2=A0 =C2=A0 DISCUSS:<br>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
----------------------------------------------------------------------<br>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt; =C2=A0 =C2=A0 Section 11 is missing a discussion =
of the privacy considerations<br>
of<br>
&gt; &gt;&gt;&gt;&gt;&gt; =C2=A0 =C2=A0 energy and power monitoring. I woul=
d suggest something along the<br>
&gt; lines of<br>
&gt; &gt;&gt;&gt;&gt;&gt; =C2=A0 =C2=A0 the following:<br>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt; =C2=A0 =C2=A0 &quot;In certain situations, energy=
 and power monitoring can reveal<br>
&gt; sensitive<br>
&gt; &gt;&gt;&gt;&gt;&gt; =C2=A0 =C2=A0 information about individuals&#39; =
activities and habits.<br>
Implementors of<br>
&gt; &gt;&gt;&gt;&gt;&gt; =C2=A0 =C2=A0 this specification should use appro=
priate privacy protections as<br>
&gt; &gt;&gt;&gt;&gt;&gt; =C2=A0 =C2=A0 discussed in Section 9 of RFC 6988 =
and monitoring of individuals<br>
and<br>
&gt; &gt;&gt;&gt;&gt;&gt; =C2=A0 =C2=A0 homes should only occur with proper=
 authorization.&quot;<br>
&gt; &gt;&gt;&gt;&gt; =C2=A0 =C2=A0 Regarding your first sentence, I propos=
e the following text,<br>
which<br>
&gt; would be in line with Security Guidelines for IETF MIB<br>
&gt; &gt;&gt;&gt;&gt; =C2=A0 =C2=A0 modules at<br>
<a href=3D"http://trac.tools.ietf.org/area/ops/trac/wiki/mib-security" targ=
et=3D"_blank">http://trac.tools.ietf.org/area/ops/trac/wiki/mib-security</a=
><br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 Some of the readable obje=
cts in this MIB module (i.e.,<br>
objects with<br>
&gt; a<br>
&gt; &gt;&gt;&gt;&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 MAX-ACCESS other than not=
-accessible) may be considered<br>
&gt; sensitive or<br>
&gt; &gt;&gt;&gt;&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 vulnerable in some networ=
k environments. =C2=A0It is thus<br>
important to<br>
&gt; &gt;&gt;&gt;&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 control even GET and/or N=
OTIFY access to these objects and<br>
&gt; possibly<br>
&gt; &gt;&gt;&gt;&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 to even encrypt the value=
s of these objects when sending them<br>
&gt; over<br>
&gt; &gt;&gt;&gt;&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 the network via SNMP. =C2=
=A0These are the tables and objects and<br>
their<br>
&gt; &gt;&gt;&gt;&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 sensitivity/vulnerability=
:<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 Access to the content of =
the eoPowerStateTable,<br>
eoEnergyTable,<br>
&gt; and<br>
&gt; &gt;&gt;&gt;&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 eoACPwrAttributesTable MI=
B tables can reveal sensitive<br>
&gt; &gt;&gt;&gt;&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 information about individ=
uals&#39; activities and habits<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; Sounds good to me.<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; =C2=A0 =C2=A0 Since this document is essentially a MI=
B module, your last<br>
sentence is<br>
&gt; covered by<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0imple=
mentations<br>
&gt; &gt;&gt;&gt;&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0claim=
ing compliance to the SNMPv3 standard MUST include<br>
full<br>
&gt; &gt;&gt;&gt;&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0suppo=
rt for authentication and privacy via the<br>
User-based<br>
&gt; &gt;&gt;&gt;&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Secur=
ity Model (USM) [RFC3414<br>
&gt; &lt;<a href=3D"http://tools.ietf.org/html/rfc3414" target=3D"_blank">h=
ttp://tools.ietf.org/html/rfc3414</a>&gt;] with the AES cipher algorithm<br=
>
&gt; &gt;&gt;&gt;&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0[RFC3=
826 =C2=A0&lt;<a href=3D"http://tools.ietf.org/html/rfc3826" target=3D"_bla=
nk">http://tools.ietf.org/html/rfc3826</a>&gt;].<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; RFC 6988 notes the need for privacy protections for s=
tored data,<br>
which<br>
&gt; the above text does not speak to, so I still think a<br>
&gt; &gt;&gt;&gt;&gt; reference to RFC 6988 would add value here.<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; It is a little disconcerting that use of SNMPv3 is pr=
ovided as a<br>
SHOULD-<br>
&gt; level requirement without discussion of deployment<br>
&gt; &gt;&gt;&gt;&gt; scenarios and regardless of the sensitivity of the da=
ta being made<br>
&gt; available by any new MIB. For example, the tradeoffs between<br>
&gt; &gt;&gt;&gt;&gt; security and utility might be reasonable if (1) I&#39=
;m using an older<br>
SNMP<br>
&gt; version on my closed home network to monitor my own energy<br>
&gt; &gt;&gt;&gt;&gt; use, but not if (2) my ISP is using it to monitor the=
 same thing. The<br>
text<br>
&gt; quoted above basically =C2=A0endorses unauthorized energy<br>
&gt; &gt;&gt;&gt;&gt; monitoring if the provider does not support SNMPv3, w=
hereas it seems<br>
&gt; like what we would want to be saying is that in cases like<br>
&gt; &gt;&gt;&gt;&gt; (2) SNMPv3 is required.<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; I understand that this is basically boilerplate langu=
age for MIB<br>
docs, so<br>
&gt; I&#39;m not sure what can be done, but it seems unfortunate.<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; Alissa<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
----------------------------------------------------------------------<br>
&gt; &gt;&gt;&gt;&gt;&gt; =C2=A0 =C2=A0 COMMENT:<br>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
----------------------------------------------------------------------<br>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt; =C2=A0 =C2=A0 Section 12.1:<br>
&gt; &gt;&gt;&gt;&gt;&gt; =C2=A0 =C2=A0 &quot;New Assignments (and potentia=
l deprecation) to Power State Sets<br>
&gt; &gt;&gt;&gt;&gt;&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0s=
hall be administered by IANA and the guidelines and<br>
&gt; procedures<br>
&gt; &gt;&gt;&gt;&gt;&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0a=
re specified in [EMAN-FMWK], and will, as a<br>
consequence, the<br>
&gt; &gt;&gt;&gt;&gt;&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0I=
ANAPowerStateSet Textual Convention should be<br>
updated.&quot;<br>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt; =C2=A0 =C2=A0 Not sure what this sentence means.<=
br>
&gt; &gt;&gt;&gt;&gt; =C2=A0 =C2=A0 Good catch.<br>
&gt; &gt;&gt;&gt;&gt; =C2=A0 =C2=A0 NEW:<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&quot=
;New Assignments (and potential deprecation) to Power<br>
State<br>
&gt; Sets<br>
&gt; &gt;&gt;&gt;&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0shall=
 be administered by IANA and the guidelines and<br>
&gt; procedures<br>
&gt; &gt;&gt;&gt;&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0are s=
pecified in [EMAN-FMWK], and will, as a<br>
consequence,<br>
&gt; update the<br>
&gt; &gt;&gt;&gt;&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0IANAP=
owerStateSet Textual Convention.&quot;<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; =C2=A0 =C2=A0 Regards, Benoit (as a document author)<=
br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;<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;&gt;&gt;<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt; _______________________________________________<br>
&gt; &gt;&gt;&gt; MIB-DOCTORS mailing list<br>
&gt; &gt;&gt;&gt; <a href=3D"mailto:MIB-DOCTORS@ietf.org">MIB-DOCTORS@ietf.=
org</a><br>
&gt; &gt;&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/mib-doct=
ors" target=3D"_blank">https://www.ietf.org/mailman/listinfo/mib-doctors</a=
><br>
&gt; &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;<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>
</div></div></blockquote></div><br><br clear=3D"all"><div><br></div>-- <br>=
<div dir=3D"ltr"><br><div>Best regards,</div><div>Kathleen</div></div>
</div>

--047d7bfcf74abf149804fdebd263--


From nobody Sat Jul 12 03:12: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 C6D201B2A60 for <mib-doctors@ietfa.amsl.com>; Sat, 12 Jul 2014 03:12:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.47
X-Spam-Level: *
X-Spam-Status: No, score=1.47 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, 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 hpgl1KwQ4__l for <mib-doctors@ietfa.amsl.com>; Sat, 12 Jul 2014 03:12:13 -0700 (PDT)
Received: from elasmtp-dupuy.atl.sa.earthlink.net (elasmtp-dupuy.atl.sa.earthlink.net [209.86.89.62]) by ietfa.amsl.com (Postfix) with ESMTP id D254F1B27B9 for <mib-doctors@ietf.org>; Sat, 12 Jul 2014 03:12:13 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=XtTHv9exXGVh5MuCsGYAB4DUflNNxMVpkbq+MjlXd9uQowgKIEjZtwsBJ7bn2KRR; h=Message-ID:Date:From:Reply-To:To:Subject:Cc:Mime-Version:Content-Type:Content-Transfer-Encoding:X-Mailer:X-ELNK-Trace:X-Originating-IP;
Received: from [209.86.224.26] (helo=mswamui-bichon.atl.sa.earthlink.net) by elasmtp-dupuy.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <randy_presuhn@mindspring.com>) id 1X5uHr-0002Fs-M0; Sat, 12 Jul 2014 06:12:11 -0400
Received: from 58.186.220.179 by webmail.earthlink.net with HTTP; Sat, 12 Jul 2014 06:12:11 -0400
Message-ID: <16925706.1405159931457.JavaMail.root@mswamui-bichon.atl.sa.earthlink.net>
Date: Sat, 12 Jul 2014 17:12:11 +0700 (GMT+07:00)
From: Randy Presuhn <randy_presuhn@mindspring.com>
To: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
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: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d88864c4c3a38ce6fd81717dfef827882d84febf27257f24923b350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 209.86.224.26
Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/0qw9t_yVlHXOLLF5AOPE2jnnzqM
Cc: "MIB Doctors \(E-mail\)" <mib-doctors@ietf.org>, Alissa Cooper <alissa@cooperw.in>, "<sec-ads@tools.ietf.org>" <sec-ads@tools.ietf.org>, Farrel Adrian <adrian@olddog.co.uk>
Subject: Re: [MIB-DOCTORS] Change the boilerplate - Kathleen'DISCUSS point 2
X-BeenThere: mib-doctors@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Randy Presuhn <randy_presuhn@mindspring.com>
List-Id: MIB Doctors list <mib-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mib-doctors/>
List-Post: <mailto:mib-doctors@ietf.org>
List-Help: <mailto:mib-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 12 Jul 2014 10:12:14 -0000

Hi -

>From: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
>Sent: Jul 11, 2014 9:33 PM
>To: ietfdbh <ietfdbh@comcast.net>
>Cc: "MIB Doctors (E-mail)" <mib-doctors@ietf.org>, Alissa Cooper <alissa@cooperw.in>, "<sec-ads@tools.ietf.org>" <sec-ads@tools.ietf.org>, Farrel Adrian <adrian@olddog.co.uk>
>Subject: Re: [MIB-DOCTORS] Change the boilerplate - Kathleen'DISCUSS point 2
>
>David,
>
>Do you have alternate text to suggest?  The point was to expand the
>possibilities beyond just effecting the network.  Attacks exploiting
>vulnerabilities, other than DoS or similar attacks, are not targeting
>network disruption.  There is a lot of information that could be gathered
>that privacy implications (individuals, homes, businesses), could effect
>business (reconnaissance leading to simple attacks or even espionage, etc.
>- this is very real), etc.

There are plenty of other juicy targets omitted by the proposed list,
such as military, governmental, and industrial control targets.
I'd suggest the following replacement text:


   "Support for SET operations in non-secured environments without proper
    protection opens devices to attack."

Randy


From nobody Sat Jul 12 06:49:08 2014
Return-Path: <kathleen.moriarty.ietf@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 A00CE1B2932 for <mib-doctors@ietfa.amsl.com>; Sat, 12 Jul 2014 06:49:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=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 jFvG8n3vudsZ for <mib-doctors@ietfa.amsl.com>; Sat, 12 Jul 2014 06:49:06 -0700 (PDT)
Received: from mail-qc0-x233.google.com (mail-qc0-x233.google.com [IPv6:2607:f8b0:400d:c01::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4DEFC1B2890 for <mib-doctors@ietf.org>; Sat, 12 Jul 2014 06:49:06 -0700 (PDT)
Received: by mail-qc0-f179.google.com with SMTP id r5so1203163qcx.38 for <mib-doctors@ietf.org>; Sat, 12 Jul 2014 06:49:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=from:content-type:mime-version:subject:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=/Li+1/g3X2qhgnq60PkxgmT1+BoMGnkcLmRDmdYCBg8=; b=Ff1e5TCJcIikutmREm/J42aDYyk46evbe2ZUPgSqACyol68nK8A3OXS1YehcdOVyq6 3Sy+BG9SIITsmLt573t2AcwXlJWfjj9OYhI5YrQ8BVoEukiCBtIeJ4f+HIQzi8nrUQiW DW/8NIJ/t2k9MZWeYarXymiJggA1REH0Qtln9lhDgpsAkNRWcV19YSQNN3XMWyEeXd/t 0G+RYpLRaACY70anWFp24GzyRsHO6hzCVb3w/ZSHJqegIOy1sPzBRVaAeNVM4AremN0r g5gcX4ryjKQKwYFmw05WaDxbK8IS4aInV3fOgNnc2Z22oeAu0edzCrKbxJCKH+DbIc5H 0BTg==
X-Received: by 10.229.44.65 with SMTP id z1mr8374676qce.7.1405172945590; Sat, 12 Jul 2014 06:49:05 -0700 (PDT)
Received: from [192.168.1.4] (209-6-114-252.c3-0.arl-ubr1.sbo-arl.ma.cable.rcn.com. [209.6.114.252]) by mx.google.com with ESMTPSA id 81sm5409804qgw.21.2014.07.12.06.49.03 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 12 Jul 2014 06:49:04 -0700 (PDT)
From: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
X-Google-Original-From: Kathleen Moriarty <Kathleen.Moriarty.ietf@gmail.com>
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (1.0)
X-Mailer: iPhone Mail (11D167)
In-Reply-To: <16925706.1405159931457.JavaMail.root@mswamui-bichon.atl.sa.earthlink.net>
Date: Sat, 12 Jul 2014 09:49:04 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <717B313A-C2B0-4A6C-8D8B-B7D2590D0687@gmail.com>
References: <16925706.1405159931457.JavaMail.root@mswamui-bichon.atl.sa.earthlink.net>
To: Randy Presuhn <randy_presuhn@mindspring.com>
Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/hI4I3hcl3-OPeTuthHqjDYe94fA
Cc: "MIB Doctors \(E-mail\)" <mib-doctors@ietf.org>, Alissa Cooper <alissa@cooperw.in>, "<sec-ads@tools.ietf.org>" <sec-ads@tools.ietf.org>, Farrel Adrian <adrian@olddog.co.uk>
Subject: Re: [MIB-DOCTORS] Change the boilerplate - Kathleen'DISCUSS point 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: Sat, 12 Jul 2014 13:49:07 -0000

Sent from my iPhone

> On Jul 12, 2014, at 6:12 AM, Randy Presuhn <randy_presuhn@mindspring.com> w=
rote:
>=20
> Hi -
>=20
>> From: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
>> Sent: Jul 11, 2014 9:33 PM
>> To: ietfdbh <ietfdbh@comcast.net>
>> Cc: "MIB Doctors (E-mail)" <mib-doctors@ietf.org>, Alissa Cooper <alissa@=
cooperw.in>, "<sec-ads@tools.ietf.org>" <sec-ads@tools.ietf.org>, Farrel Adr=
ian <adrian@olddog.co.uk>
>> Subject: Re: [MIB-DOCTORS] Change the boilerplate - Kathleen'DISCUSS poin=
t 2
>>=20
>> David,
>>=20
>> Do you have alternate text to suggest?  The point was to expand the
>> possibilities beyond just effecting the network.  Attacks exploiting
>> vulnerabilities, other than DoS or similar attacks, are not targeting
>> network disruption.  There is a lot of information that could be gathered=

>> that privacy implications (individuals, homes, businesses), could effect
>> business (reconnaissance leading to simple attacks or even espionage, etc=
.
>> - this is very real), etc.
>=20
> There are plenty of other juicy targets omitted by the proposed list,
> such as military, governmental, and industrial control targets.
> I'd suggest the following replacement text:
>=20
>=20
>   "Support for SET operations in non-secured environments without proper
>    protection opens devices to attack."
>=20
> Randy
That works for me, getting the same point point across.

Thank you,
Kathleen=20=


From nobody Wed Jul 30 06:23:30 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 6D2B21A0046 for <mib-doctors@ietfa.amsl.com>; Wed, 30 Jul 2014 06:23:27 -0700 (PDT)
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 FVbqgCaiy4_a for <mib-doctors@ietfa.amsl.com>; Wed, 30 Jul 2014 06:23:24 -0700 (PDT)
Received: from koko.ripe.net (koko.ripe.net [IPv6:2001:67c:2e8:11::c100:1348]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 884581A0027 for <mib-doctors@ietf.org>; Wed, 30 Jul 2014 06:23:24 -0700 (PDT)
Received: from titi.ripe.net ([193.0.23.11]) by koko.ripe.net with esmtps (UNKNOWN:AES256-GCM-SHA384:256) (Exim 4.72) (envelope-from <bertietf@bwijnen.net>) id 1XCTqh-0003wj-9r; Wed, 30 Jul 2014 15:23:20 +0200
Received: from kitten.ripe.net ([2001:67c:2e8:1::c100:1f0] helo=macintosh-6.fritz.box) by titi.ripe.net with esmtp (Exim 4.72) (envelope-from <bertietf@bwijnen.net>) id 1XCTqh-00017e-5b; Wed, 30 Jul 2014 15:23:19 +0200
Message-ID: <53D8F1C5.1090709@bwijnen.net>
Date: Wed, 30 Jul 2014 15:23:17 +0200
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.6.0
MIME-Version: 1.0
To: Andrei Robachevsky <robachevsky@isoc.org>,  MIB Doctors <mib-doctors@ietf.org>
References: <53D1215D.6060606@isoc.org>
In-Reply-To: <53D1215D.6060606@isoc.org>
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: 86ab03e524994f79ca2c75a176445dd4ae37ac1fff781e1246d40743d8ce4a38
Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/LSoQx-MmVFqSaq8PsNC5ezrDQ1o
Subject: Re: [MIB-DOCTORS] SNMP for the STD for IETF standards EU procurement platform
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, 30 Jul 2014 13:23:27 -0000

Andrei, not sure if I correctly formulated the $subject.
Pls correct if needed.

So you had a set of SNMP standards that you would want to include.

It is probably best to include MIB doctors in the discussion.
AS I said, a set of base/always-present MIB modules should probably
also be included. I remember that we did define such a set several years back
when we worked together with ITU SG4 and other organizations to try and
define a list of applicable standards work in the various bodies.
Unfortunately I cannot quickly fin that list. I am sure there are MIB
doctors on the list that have the ptrs handy.

Also, the IETF OPS ADs may want to be onvolved in this.

Comments on the list that you did send to me;

On 24/07/14 17:08, Andrei Robachevsky wrote:
> RFC	TITLE	
 >       Base Spec Boolean	Rationale
> 2578	Structure of Management Information Version 2 (SMIv2)
	0	STD58, Data definition language
> 2579	Textual Conventions for SMIv2
	0	STD58, Data definition language
> 2580	Conformance Statements for SMIv2
	0	STD58, Data definition language

About the above 3:
As I said verbally to you, I am not sure that the data modeling language
itself is something that governments would use themselves. So not sure if it
is useful to include them.

> 3412	Message Processing and Dispatching for the Simple Network Management Protocol (SNMP)
>	1	STD62
> 3413	Simple Network Management Protocol (SNMP) Applications
	1	STD62
> 3414	User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3)
>	1	STD62, v3 security features
> 3415	View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP)
>	1	STD62, v3 security features
> 3416	Version 2 of the Protocol Operations for the Simple Network Management Protocol (SNMP)
>	1	STD62, Describes SNMPv2 (this is also the protocol operations used in SNMPv3)
> 3417	Transport Mappings for the Simple Network Management Protocol (SNMP)
>	1	STD62
> 3418	Management Information Base (MIB) for the Simple Network Management Protocol (SNMP)
> 	1	STD62
>

I think (as I experssed verbally) that I would also include a base set of MIB modules,
after all, it makes no sense to have SNMP if you do not have MIB modules.
The list should probably include

- RFC2863, IF-MIB
- RFC6933, ENTITY-MIB

but probably many more. There is a list at
     http://www.simpleweb.org/ietf/rfcs/rfcbynumber.php
or maybe even better
     http://www.simpleweb.org/ietf/rfcs/rfcbystatus.php#Draft%20standard

that lists a lot of them. Not all are relevant or must-be-present MIB modules though.

MIB doctors, does anyone of you have a handy ptr to the list that we normally promote
as needed/useful? I thought we used to have that also at the ops.ietf.org page,
but I do not see it on the current page.

Andrei,
I think it is also important to say something about the fact tht these days we (IETF)
promote MIB modules and SNMP for monitoring or traps.
But for configuration, we now promote NETCONF. See IESG statement:
     http://www.ietf.org/iesg/statement/writable-mib-module.html

Bert


From nobody Wed Jul 30 06:49:44 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 95F8D1A0060 for <mib-doctors@ietfa.amsl.com>; Wed, 30 Jul 2014 06:49:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.551
X-Spam-Level: 
X-Spam-Status: No, score=-1.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RP_MATCHES_RCVD=-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 D6Y6wo0jXeKa for <mib-doctors@ietfa.amsl.com>; Wed, 30 Jul 2014 06:49:42 -0700 (PDT)
Received: from atlas3.jacobs-university.de (atlas3.jacobs-university.de [212.201.44.18]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 884C21A004E for <mib-doctors@ietf.org>; Wed, 30 Jul 2014 06:49:42 -0700 (PDT)
Received: from localhost (demetrius5.irc-it.jacobs-university.de [10.70.0.222]) by atlas3.jacobs-university.de (Postfix) with ESMTP id 2309CA39; Wed, 30 Jul 2014 15:49:41 +0200 (CEST)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from atlas3.jacobs-university.de ([10.70.0.220]) by localhost (demetrius5.jacobs-university.de [10.70.0.222]) (amavisd-new, port 10030) with ESMTP id iV-5ucdwzpwe; Wed, 30 Jul 2014 15:49:37 +0200 (CEST)
Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hermes.jacobs-university.de", Issuer "Jacobs University CA - G01" (verified OK)) by atlas3.jacobs-university.de (Postfix) with ESMTPS; Wed, 30 Jul 2014 15:49:39 +0200 (CEST)
Received: from localhost (demetrius2.jacobs-university.de [212.201.44.47]) by hermes.jacobs-university.de (Postfix) with ESMTP id 961682002C; Wed, 30 Jul 2014 15:49:39 +0200 (CEST)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius2.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id ZKrdvMvDdozR; Wed, 30 Jul 2014 15:49:38 +0200 (CEST)
Received: from elstar.local (elstar.jacobs.jacobs-university.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id 6BFF220017; Wed, 30 Jul 2014 15:49:37 +0200 (CEST)
Received: by elstar.local (Postfix, from userid 501) id 355A82DFF553; Wed, 30 Jul 2014 15:49:37 +0200 (CEST)
Date: Wed, 30 Jul 2014 15:49:37 +0200
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: "Bert Wijnen (IETF)" <bertietf@bwijnen.net>
Message-ID: <20140730134936.GD61698@elstar.local>
Mail-Followup-To: "Bert Wijnen (IETF)" <bertietf@bwijnen.net>, Andrei Robachevsky <robachevsky@isoc.org>, MIB Doctors <mib-doctors@ietf.org>
References: <53D1215D.6060606@isoc.org> <53D8F1C5.1090709@bwijnen.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <53D8F1C5.1090709@bwijnen.net>
User-Agent: Mutt/1.4.2.3i
Archived-At: http://mailarchive.ietf.org/arch/msg/mib-doctors/O77FDaYLjK4sPp_BCZaUeR_hUYA
Cc: MIB Doctors <mib-doctors@ietf.org>, Andrei Robachevsky <robachevsky@isoc.org>
Subject: Re: [MIB-DOCTORS] SNMP for the STD for IETF standards EU procurement platform
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, 30 Jul 2014 13:49:43 -0000

On Wed, Jul 30, 2014 at 03:23:17PM +0200, Bert Wijnen (IETF) wrote:
> The list should probably include
> 
> - RFC2863, IF-MIB
> - RFC6933, ENTITY-MIB
> 
> but probably many more. There is a list at
>     http://www.simpleweb.org/ietf/rfcs/rfcbynumber.php
> or maybe even better
>     http://www.simpleweb.org/ietf/rfcs/rfcbystatus.php#Draft%20standard
> 
> that lists a lot of them. Not all are relevant or must-be-present MIB 
> modules though.
> 
> MIB doctors, does anyone of you have a handy ptr to the list that we
> normally promote as needed/useful? I thought we used to have that
> also at the ops.ietf.org page, but I do not see it on the current
> page.

I think coverage of the IP stack is generally a good thing. This means
typically the IP-MIB [RFC 4293], the IP-FORWARD-MIB [RFC 4292], the
UDP-MIB [RFC 4113], and the TCP-MIB [RFC 4022].

The rest is I believe more or less is device class specific.

- Devices having Ethernet interfaces may want to support the relevant
  MIB modules (which are now under IEEE control, not sure it makes
  sense to list to the old IETF specifications).

- Devices that are managed hosts (desktop but more typically servers)
  may want to support that HOST-RESOURCES-MIB [RFC 2790].

- Ethernet switches should implement one of the bridge MIB modules,
  they are meanwhile under IEEE control.

- IP routers likely should support MIB modules corresponding to the
  routing protocol(s) supported and the interface types supported.

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

