
From dromasca@avaya.com  Wed Oct  5 10:19:13 2011
Return-Path: <dromasca@avaya.com>
X-Original-To: mib-doctors@ietfa.amsl.com
Delivered-To: mib-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A0A441F0C51 for <mib-doctors@ietfa.amsl.com>; Wed,  5 Oct 2011 10:19:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.387
X-Spam-Level: 
X-Spam-Status: No, score=-103.387 tagged_above=-999 required=5 tests=[AWL=0.212, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AYUf5yJABWse for <mib-doctors@ietfa.amsl.com>; Wed,  5 Oct 2011 10:19:13 -0700 (PDT)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by ietfa.amsl.com (Postfix) with ESMTP id E1ED91F0C48 for <mib-doctors@ietf.org>; Wed,  5 Oct 2011 10:19:12 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0WADWRjE7GmAcF/2dsb2JhbABCmUOJGIU5gQWBVQEBAxIeClEBFRUGDAwHVwEEGxqgL4QPmyuGSGEEmTOMAA
X-IronPort-AV: E=Sophos;i="4.68,492,1312171200"; d="scan'208";a="271335322"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 05 Oct 2011 13:22:18 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14]) by co300216-co-erhwest-out.avaya.com with ESMTP; 05 Oct 2011 13:21:22 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 5 Oct 2011 19:22:16 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A0403BE8F90@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Sean Turner joining temporarily the MIB Doctors mail list
Thread-Index: AcyDg1RuJGiigr3KQJuuwR7p8KmM+A==
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <mib-doctors@ietf.org>
Subject: [MIB-DOCTORS] Sean Turner joining temporarily the MIB Doctors mail list
X-BeenThere: mib-doctors@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: MIB Doctors list <mib-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mib-doctors>
List-Post: <mailto:mib-doctors@ietf.org>
List-Help: <mailto:mib-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Oct 2011 17:19:13 -0000

Hi MIB Doctors,

I have added Sean Turner to the MIB Doctors mail list. Sean is as you
all know one of the security ADs and he is forwarding a proposal for
updating the guidelines for the Security Considerations section. I added
him to the mail list for the time period we debate his proposal.=20

Regards,=20

Dan





From turners@ieca.com  Wed Oct  5 11:27:06 2011
Return-Path: <turners@ieca.com>
X-Original-To: mib-doctors@ietfa.amsl.com
Delivered-To: mib-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 54CF921F8C93 for <mib-doctors@ietfa.amsl.com>; Wed,  5 Oct 2011 11:27:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.6
X-Spam-Level: 
X-Spam-Status: No, score=-100.6 tagged_above=-999 required=5 tests=[AWL=-1.202, BAYES_50=0.001, J_CHICKENPOX_43=0.6, UNPARSEABLE_RELAY=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F5hKpNFR51IA for <mib-doctors@ietfa.amsl.com>; Wed,  5 Oct 2011 11:27:05 -0700 (PDT)
Received: from nm8.bullet.mail.sp2.yahoo.com (nm8.bullet.mail.sp2.yahoo.com [98.139.91.78]) by ietfa.amsl.com (Postfix) with SMTP id E91F521F8C4E for <mib-doctors@ietf.org>; Wed,  5 Oct 2011 11:27:04 -0700 (PDT)
Received: from [98.139.91.67] by nm8.bullet.mail.sp2.yahoo.com with NNFMP; 05 Oct 2011 18:30:13 -0000
Received: from [98.139.91.35] by tm7.bullet.mail.sp2.yahoo.com with NNFMP; 05 Oct 2011 18:29:13 -0000
Received: from [127.0.0.1] by omp1035.mail.sp2.yahoo.com with NNFMP; 05 Oct 2011 18:29:13 -0000
X-Yahoo-Newman-Id: 629886.42909.bm@omp1035.mail.sp2.yahoo.com
Received: (qmail 5504 invoked from network); 5 Oct 2011 18:29:13 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1317839353; bh=ukrsksCcQb4bNpkExn1n6ZQTo0O3LZyKhCiqmAjpg8Y=; h=X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:Content-Type:Content-Transfer-Encoding; b=azqAB/0IudTqa5eHfski1XHwNfd5oavAiUcrAMbQHKJSZxRXzqJBBUp3WfF+xMxqEMc+1r45tieak1fbHUvA6gmPhndbOQSSojKYW6NgEX7LXasoiGp7obZR/D5O7O977kU61Cy027Rf/fgAxQb79w7blQCKZG80iUEY8Wgekog=
X-Yahoo-Newman-Property: ymail-3
X-YMail-OSG: h.Wlh.4VM1mkPTl5lMmneZ4brT_VRjMp0B_iRS7SqGOIOIc SBgpUjeqE5W0EUPpEYajjgwa8oXihxWFbnjOiva9.llEsW6NBhAFrGx3DtAH Aua7ta8Eary.cMqkolNcjlM1ukO8XPyytQoUK4J0ibWRb1bEtIvHQEsh1day xi8bzU3hNAEPnQuTAwvYdnpIDPgM7029Swfn4ffDW3xCyGRdmta4T6nrwn2V RtNyDLO53m3f0KMf4jsC1BbYKtVuVeuo6ejFygyBoN3pnK66ZFuzXlNTe98y LJkizhIzHc5AmnMunrI2YLewR.rwEmf0YWBC2lxcjI3Kb6jH5X9AKNi.AYYt rLy32kcC_75eGSDtxriGIeDviy6SlKyChwmUsAPSdEC189Y.4cSOy68fZGzJ hWLV.aMMBAHi2wf8tX_37l_PC5CiutNAy4g7UnA--
X-Yahoo-SMTP: ZrP3VLSswBDL75pF8ymZHDSu9B.vcMfDPgLJ
Received: from thunderfish.local (turners@71.191.1.163 with plain) by smtp114.biz.mail.mud.yahoo.com with SMTP; 05 Oct 2011 11:29:13 -0700 PDT
Message-ID: <4E8CA1F8.5040807@ieca.com>
Date: Wed, 05 Oct 2011 14:29:12 -0400
From: Sean Turner <turners@ieca.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: mib-doctors@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [MIB-DOCTORS] Updates to the Guidelines of the Security Considerations section of the MIB documents
X-BeenThere: mib-doctors@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: MIB Doctors list <mib-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mib-doctors>
List-Post: <mailto:mib-doctors@ietf.org>
List-Help: <mailto:mib-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Oct 2011 18:27:07 -0000

Hi,

After the publication of RFC 5591 and the fact that SNMP+DES really 
ought to be replaced with SNMP+AES, I'd like to propose the following 
change to the MIB security considerations:

OLD:

    It is RECOMMENDED that implementers consider the security features
    as provided by the SNMPv3 framework (see [RFC3410], section 8),
    including full support for the SNMPv3 cryptographic mechanisms (for
    authentication and privacy).

NEW:

    It is RECOMMENDED that implementers consider the security features
    as provided by the SNMPv3 framework (see [RFC3410], section 8),
    including full support for the USM [RFC3414][RFC3826] and Transport
    Security Model [RFC5591] cryptographic mechanisms (for authentication
    and privacy).

What I'm proposing is just being specific by listing the two mechanisms. 
  But, we can't just point to 3414 becaue it requires DES, hence the 
3826 reference.  And, the reference to 5591 expands the options to allow 
RFC 6353.

Thoughts?

spt

From randy_presuhn@mindspring.com  Wed Oct  5 12:15:19 2011
Return-Path: <randy_presuhn@mindspring.com>
X-Original-To: mib-doctors@ietfa.amsl.com
Delivered-To: mib-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1259D1F0C41 for <mib-doctors@ietfa.amsl.com>; Wed,  5 Oct 2011 12:15:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.021
X-Spam-Level: 
X-Spam-Status: No, score=-101.021 tagged_above=-999 required=5 tests=[AWL=-0.836, BAYES_40=-0.185, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O4di0RKns2Lg for <mib-doctors@ietfa.amsl.com>; Wed,  5 Oct 2011 12:15:18 -0700 (PDT)
Received: from elasmtp-kukur.atl.sa.earthlink.net (elasmtp-kukur.atl.sa.earthlink.net [209.86.89.65]) by ietfa.amsl.com (Postfix) with ESMTP id 654531F0C36 for <mib-doctors@ietf.org>; Wed,  5 Oct 2011 12:15:18 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=bewttmMEBerDdYHRJc+ryNMnS1vTWjtQKHZzryLBADs6XEcknaasM6lGV2wBwi6M; h=Received:Message-ID:From:To:References:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:X-MimeOLE:X-ELNK-Trace:X-Originating-IP;
Received: from [99.41.50.214] (helo=oemcomputer) by elasmtp-kukur.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <randy_presuhn@mindspring.com>) id 1RBWz2-0007zC-HK for mib-doctors@ietf.org; Wed, 05 Oct 2011 15:18:24 -0400
Message-ID: <003901cc8393$c09abfa0$6b01a8c0@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: <mib-doctors@ietf.org>
References: <4E8CA1F8.5040807@ieca.com>
Date: Wed, 5 Oct 2011 12:19:49 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1478
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478
X-ELNK-Trace: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d8887f779e183b2ee288b31b536d807ea6f47e412d773a9acdf8350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 99.41.50.214
Subject: Re: [MIB-DOCTORS] Updates to the Guidelines of the Security Considerations section of the MIB documents
X-BeenThere: mib-doctors@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: MIB Doctors list <mib-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mib-doctors>
List-Post: <mailto:mib-doctors@ietf.org>
List-Help: <mailto:mib-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Oct 2011 19:15:19 -0000

Hi -

> From: "Sean Turner" <turners@ieca.com>
> To: <mib-doctors@ietf.org>
> Sent: Wednesday, October 05, 2011 11:29 AM
> Subject: [MIB-DOCTORS] Updates to the Guidelines of the Security Considerations section of the MIB documents
...
> NEW:
> 
>     It is RECOMMENDED that implementers consider the security features
>     as provided by the SNMPv3 framework (see [RFC3410], section 8),
>     including full support for the USM [RFC3414][RFC3826] and Transport
>     Security Model [RFC5591] cryptographic mechanisms (for authentication
>     and privacy).
> 
> What I'm proposing is just being specific by listing the two mechanisms. 
>   But, we can't just point to 3414 becaue it requires DES, hence the 
> 3826 reference.  And, the reference to 5591 expands the options to allow 
> RFC 6353.
> 
> Thoughts?

Since RFC 3826 incorporates RFC 3414 as a normative reference, I don't
see why RFC 3414 needs to be cited.  Since there is no point in implementing
RFC 5591 *unless* one actually needs something like 6353 (which in turn
incorporates RFC 5591 as a normative reference) I also don't see any
point in mentioning RFC 5591 here, unless you intend to actuall recommend/
require 6353.  So here's a counter-proposal:

NEW':
    It is RECOMMENDED that implementers consider the security features
    as provided by the SNMPv3 framework (see [RFC3410], section 8),
    as well as full support for the Advanced Encryption Standard (AES)
    Cipher Algorithm in the SNMP User-based Security Model [RFC3826].

Randy


From j.schoenwaelder@jacobs-university.de  Wed Oct  5 13:10:44 2011
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 (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B312E21F8CB8 for <mib-doctors@ietfa.amsl.com>; Wed,  5 Oct 2011 13:10:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.818
X-Spam-Level: 
X-Spam-Status: No, score=-102.818 tagged_above=-999 required=5 tests=[AWL=-0.169, BAYES_00=-2.599, HELO_EQ_DE=0.35, J_CHICKENPOX_43=0.6, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id A-S2yYTMod61 for <mib-doctors@ietfa.amsl.com>; Wed,  5 Oct 2011 13:10:44 -0700 (PDT)
Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) by ietfa.amsl.com (Postfix) with ESMTP id A01EC21F8CB4 for <mib-doctors@ietf.org>; Wed,  5 Oct 2011 13:10:43 -0700 (PDT)
Received: from localhost (demetrius2.jacobs-university.de [212.201.44.47]) by hermes.jacobs-university.de (Postfix) with ESMTP id 8DE8620D12; Wed,  5 Oct 2011 22:13:51 +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 zx1fYh9IZYot; Wed,  5 Oct 2011 22:13:50 +0200 (CEST)
Received: from elstar.local (elstar.jacobs.jacobs-university.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id CCC0420CE3; Wed,  5 Oct 2011 22:13:49 +0200 (CEST)
Received: by elstar.local (Postfix, from userid 501) id 265B51B057C0; Wed,  5 Oct 2011 22:13:36 +0200 (CEST)
Date: Wed, 5 Oct 2011 22:13:35 +0200
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: Sean Turner <turners@ieca.com>
Message-ID: <20111005201335.GA48603@elstar.local>
Mail-Followup-To: Sean Turner <turners@ieca.com>, mib-doctors@ietf.org
References: <4E8CA1F8.5040807@ieca.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4E8CA1F8.5040807@ieca.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: mib-doctors@ietf.org
Subject: Re: [MIB-DOCTORS] Updates to the Guidelines of the Security Considerations section of the MIB documents
X-BeenThere: mib-doctors@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
List-Id: MIB Doctors list <mib-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mib-doctors>
List-Post: <mailto:mib-doctors@ietf.org>
List-Help: <mailto:mib-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Oct 2011 20:10:44 -0000

On Wed, Oct 05, 2011 at 02:29:12PM -0400, Sean Turner wrote:
> Hi,
> 
> After the publication of RFC 5591 and the fact that SNMP+DES really
> ought to be replaced with SNMP+AES, I'd like to propose the
> following change to the MIB security considerations:
> 
> OLD:
> 
>    It is RECOMMENDED that implementers consider the security features
>    as provided by the SNMPv3 framework (see [RFC3410], section 8),
>    including full support for the SNMPv3 cryptographic mechanisms (for
>    authentication and privacy).
> 
> NEW:
> 
>    It is RECOMMENDED that implementers consider the security features
>    as provided by the SNMPv3 framework (see [RFC3410], section 8),
>    including full support for the USM [RFC3414][RFC3826] and Transport
>    Security Model [RFC5591] cryptographic mechanisms (for authentication
>    and privacy).
> 
> What I'm proposing is just being specific by listing the two
> mechanisms.  But, we can't just point to 3414 becaue it requires
> DES, hence the 3826 reference.  And, the reference to 5591 expands
> the options to allow RFC 6353.

RFC 5591 does not have any "cryptographic mechanisms", so this is even
worse that RFC 3414 alone (which at least has DES). What about this:

   It is RECOMMENDED that implementers consider the security features
   as provided by the SNMPv3 framework (see [RFC3410], section 8),
   including full support for authentication and privacy via the
   User-based Security Model (USM) [RFC3414] with the AES cipher
   algorithm [RFC3826] and the Transport Security Model (TSM)
   [RFC5591] in combination with a secure transport such as SSH
   [RFC5592] or TLS/DTLS [RFC6353].

Probably a bit long. Here is a less verbose version:

   It is RECOMMENDED that implementers consider the security features
   provided by the SNMPv3 framework (see [RFC3410], section 8),
   including full support for authentication and privacy via the
   User-based Security Model (USM) [RFC3414] [RFC3826] and the
   Transport Security Model (TSM) [RFC5591] [RFC5592] [RFC6353].

Anyway, if we open up the security considerations template, we may
want to look at other wordings that often caused people to make
changed, e.g. the "even then" in the IPsec phrase (which IMHO should
simply be taken out).

OLD:

   SNMP versions prior to SNMPv3 did not include adequate security.
   Even if the network itself is secure (for example by using IPsec),
   even then, there is no control as to who on the secure network is
   allowed to access and GET/SET (read/change/create/delete) the objects
   in this MIB module.

NEW

   SNMP versions prior to SNMPv3 did not include adequate security.
   Even if the network itself is secure (for example by using IPsec),
   there is no control as to who on the secure network is
   allowed to access and GET/SET (read/change/create/delete) the objects
   in this MIB module.

/js

PS: Another good action would be to advance RFC3826 on the standards
    track - this is still a proposed standard...

-- 
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 turners@ieca.com  Wed Oct  5 14:28:37 2011
Return-Path: <turners@ieca.com>
X-Original-To: mib-doctors@ietfa.amsl.com
Delivered-To: mib-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2348F21F8D0C for <mib-doctors@ietfa.amsl.com>; Wed,  5 Oct 2011 14:28:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.596
X-Spam-Level: 
X-Spam-Status: No, score=-101.596 tagged_above=-999 required=5 tests=[AWL=-0.198, BAYES_00=-2.599, J_CHICKENPOX_31=0.6, J_CHICKENPOX_43=0.6, UNPARSEABLE_RELAY=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ocf+lEhj+353 for <mib-doctors@ietfa.amsl.com>; Wed,  5 Oct 2011 14:28:36 -0700 (PDT)
Received: from nm20-vm0.bullet.mail.sp2.yahoo.com (nm20-vm0.bullet.mail.sp2.yahoo.com [98.139.91.218]) by ietfa.amsl.com (Postfix) with SMTP id 57FA321F8D0A for <mib-doctors@ietf.org>; Wed,  5 Oct 2011 14:28:36 -0700 (PDT)
Received: from [98.139.91.68] by nm20.bullet.mail.sp2.yahoo.com with NNFMP; 05 Oct 2011 21:31:35 -0000
Received: from [98.139.91.30] by tm8.bullet.mail.sp2.yahoo.com with NNFMP; 05 Oct 2011 21:31:35 -0000
Received: from [127.0.0.1] by omp1030.mail.sp2.yahoo.com with NNFMP; 05 Oct 2011 21:31:35 -0000
X-Yahoo-Newman-Id: 871228.62467.bm@omp1030.mail.sp2.yahoo.com
Received: (qmail 51279 invoked from network); 5 Oct 2011 21:31:35 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1317850295; bh=OeitfBd4fGZmgtwEJBAD1zgQndhnbLy20IG7uqa/U3c=; h=X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=E3f6rLaefc8QPAS5y1PWVE8DW7E/+XXKA2pK8YJOEUF3dPbBcxmzMZykyPcSxHgetsLvpOrkvRwQ4EqSvc+xIJ93mchmXEiICH8brW6S7Qu3RWBJd+reeDS4Ia0mh0hZpisioewSaOnVuturtNV19sIjapT20wT6J5liGxLOKXM=
X-Yahoo-Newman-Property: ymail-3
X-YMail-OSG: WevWz2AVM1lXaZxeTdFKEhMtXlzwqE.8yDt79jxVGTKu1Le qvVJPKcu0KuKfSX3PyELY8TRgJ73_Yfalo28DG9XelpzX4SGwvr5r0z3NKks t1NG3Xt3ylnbI3wn4toRRf9SYVySrtGizr8QcKdugMii7770WF.NWR8BZNMJ TPC.sXxvxd2Sx2Gm.52jlbBFfeDqsDXhZHi2p.30Bo.O4O0idzDDqdlu54Ec 0PzaYloDf6Vsp0Sczp61neawzRhk3EM0A2.V3qay6oOZuvnxfoiivq_PcjuF XBW_k2PnrtYIyVW3vOdXbUnS.wpc.XL8wmLq_6YuI6pymxVht1ozgliz.WvP 14L4Yl4faYZ2PUIOAPmVB_XdDxjRS4tD_xQbbltRbJ_CtOgp6qQppuTZI0Z3 9sHD4QcFqW2Jxghgm9mVGWy1Z3h8FE4xYx.eZ1Q--
X-Yahoo-SMTP: ZrP3VLSswBDL75pF8ymZHDSu9B.vcMfDPgLJ
Received: from thunderfish.local (turners@71.191.1.163 with plain) by smtp112.biz.mail.sp1.yahoo.com with SMTP; 05 Oct 2011 14:31:34 -0700 PDT
Message-ID: <4E8CCCB5.9090501@ieca.com>
Date: Wed, 05 Oct 2011 17:31:33 -0400
From: Sean Turner <turners@ieca.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: mib-doctors@ietf.org
References: <4E8CA1F8.5040807@ieca.com> <20111005201335.GA48603@elstar.local>
In-Reply-To: <20111005201335.GA48603@elstar.local>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [MIB-DOCTORS] Updates to the Guidelines of the Security Considerations section of the MIB documents
X-BeenThere: mib-doctors@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: MIB Doctors list <mib-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mib-doctors>
List-Post: <mailto:mib-doctors@ietf.org>
List-Help: <mailto:mib-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Oct 2011 21:28:37 -0000

On 10/5/11 4:13 PM, Juergen Schoenwaelder wrote:
> On Wed, Oct 05, 2011 at 02:29:12PM -0400, Sean Turner wrote:
>> Hi,
>>
>> After the publication of RFC 5591 and the fact that SNMP+DES really
>> ought to be replaced with SNMP+AES, I'd like to propose the
>> following change to the MIB security considerations:
>>
>> OLD:
>>
>>     It is RECOMMENDED that implementers consider the security features
>>     as provided by the SNMPv3 framework (see [RFC3410], section 8),
>>     including full support for the SNMPv3 cryptographic mechanisms (for
>>     authentication and privacy).
>>
>> NEW:
>>
>>     It is RECOMMENDED that implementers consider the security features
>>     as provided by the SNMPv3 framework (see [RFC3410], section 8),
>>     including full support for the USM [RFC3414][RFC3826] and Transport
>>     Security Model [RFC5591] cryptographic mechanisms (for authentication
>>     and privacy).
>>
>> What I'm proposing is just being specific by listing the two
>> mechanisms.  But, we can't just point to 3414 becaue it requires
>> DES, hence the 3826 reference.  And, the reference to 5591 expands
>> the options to allow RFC 6353.
>
> RFC 5591 does not have any "cryptographic mechanisms", so this is even
> worse that RFC 3414 alone (which at least has DES). What about this:
>
>     It is RECOMMENDED that implementers consider the security features
>     as provided by the SNMPv3 framework (see [RFC3410], section 8),
>     including full support for authentication and privacy via the
>     User-based Security Model (USM) [RFC3414] with the AES cipher
>     algorithm [RFC3826] and the Transport Security Model (TSM)
>     [RFC5591] in combination with a secure transport such as SSH
>     [RFC5592] or TLS/DTLS [RFC6353].
>
> Probably a bit long. Here is a less verbose version:
>
>     It is RECOMMENDED that implementers consider the security features
>     provided by the SNMPv3 framework (see [RFC3410], section 8),
>     including full support for authentication and privacy via the
>     User-based Security Model (USM) [RFC3414] [RFC3826] and the
>     Transport Security Model (TSM) [RFC5591] [RFC5592] [RFC6353].

I'd take either of these actually.  But, I like the former slightly more 
because it explains why 3826 is included and the includes the 
SSH/TLS/DTLS mechanisms.

> Anyway, if we open up the security considerations template, we may
> want to look at other wordings that often caused people to make
> changed, e.g. the "even then" in the IPsec phrase (which IMHO should
> simply be taken out).

I'm okay with this too.

> OLD:
>
>     SNMP versions prior to SNMPv3 did not include adequate security.
>     Even if the network itself is secure (for example by using IPsec),
>     even then, there is no control as to who on the secure network is
>     allowed to access and GET/SET (read/change/create/delete) the objects
>     in this MIB module.
>
> NEW
>
>     SNMP versions prior to SNMPv3 did not include adequate security.
>     Even if the network itself is secure (for example by using IPsec),
>     there is no control as to who on the secure network is
>     allowed to access and GET/SET (read/change/create/delete) the objects
>     in this MIB module.

I'm fine with this.

> /js
>
> PS: Another good action would be to advance RFC3826 on the standards
>      track - this is still a proposed standard...

I'm willing to help out.  If we've got two interoperable implementations 
let's get'r done.

spt

From dromasca@avaya.com  Thu Oct  6 01:55:00 2011
Return-Path: <dromasca@avaya.com>
X-Original-To: mib-doctors@ietfa.amsl.com
Delivered-To: mib-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 378FA21F8CD2 for <mib-doctors@ietfa.amsl.com>; Thu,  6 Oct 2011 01:55:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.288
X-Spam-Level: 
X-Spam-Status: No, score=-102.288 tagged_above=-999 required=5 tests=[AWL=-0.889, BAYES_00=-2.599, J_CHICKENPOX_31=0.6, J_CHICKENPOX_43=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wRucMbUhoAVK for <mib-doctors@ietfa.amsl.com>; Thu,  6 Oct 2011 01:54:59 -0700 (PDT)
Received: from p-us1-iereast-outbound.us1.avaya.com (p-us1-iereast-outbound.us1.avaya.com [135.11.29.13]) by ietfa.amsl.com (Postfix) with ESMTP id 6FCE021F8CC5 for <mib-doctors@ietf.org>; Thu,  6 Oct 2011 01:54:59 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AiYCAEttjU6HCzI1/2dsb2JhbABEmRSJXIU7gQWBUwEBAQECAQEBAQ8eCjQQBwQCAQgNBAQBAQEKBgwHBAEGASYfCQgBAQQBEggah1wHmzWbGwOGS2EEmTWMAQ
X-IronPort-AV: E=Sophos;i="4.68,495,1312171200"; d="scan'208";a="211569885"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by p-us1-iereast-outbound.us1.avaya.com with ESMTP; 06 Oct 2011 04:58:07 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 06 Oct 2011 04:48:10 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 6 Oct 2011 10:58:05 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A0403BE90B0@307622ANEX5.global.avaya.com>
In-Reply-To: <4E8CCCB5.9090501@ieca.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [MIB-DOCTORS] Updates to the Guidelines of the Security Considerations section of the MIB documents
Thread-Index: AcyDpjG6582ogLJfRl6ky5/q3ZLmegAXuKOw
References: <4E8CA1F8.5040807@ieca.com> <20111005201335.GA48603@elstar.local> <4E8CCCB5.9090501@ieca.com>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Sean Turner" <turners@ieca.com>, <mib-doctors@ietf.org>
Subject: Re: [MIB-DOCTORS] Updates to the Guidelines of the Security Considerations section of the MIB documents
X-BeenThere: mib-doctors@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: MIB Doctors list <mib-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mib-doctors>
List-Post: <mailto:mib-doctors@ietf.org>
List-Help: <mailto:mib-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Oct 2011 08:55:00 -0000

See in-line.=20

Regards,

Dan

> -----Original Message-----
> From: mib-doctors-bounces@ietf.org [mailto:mib-doctors-
> bounces@ietf.org] On Behalf Of Sean Turner
> Sent: Wednesday, October 05, 2011 11:32 PM
> To: mib-doctors@ietf.org
> Subject: Re: [MIB-DOCTORS] Updates to the Guidelines of the Security
> Considerations section of the MIB documents
>=20
> On 10/5/11 4:13 PM, Juergen Schoenwaelder wrote:
> > On Wed, Oct 05, 2011 at 02:29:12PM -0400, Sean Turner wrote:
> >> Hi,
> >>
> >> After the publication of RFC 5591 and the fact that SNMP+DES really
> >> ought to be replaced with SNMP+AES, I'd like to propose the
> >> following change to the MIB security considerations:
> >>
> >> OLD:
> >>
> >>     It is RECOMMENDED that implementers consider the security
> features
> >>     as provided by the SNMPv3 framework (see [RFC3410], section 8),
> >>     including full support for the SNMPv3 cryptographic mechanisms
> (for
> >>     authentication and privacy).
> >>
> >> NEW:
> >>
> >>     It is RECOMMENDED that implementers consider the security
> features
> >>     as provided by the SNMPv3 framework (see [RFC3410], section 8),
> >>     including full support for the USM [RFC3414][RFC3826] and
> Transport
> >>     Security Model [RFC5591] cryptographic mechanisms (for
> authentication
> >>     and privacy).
> >>
> >> What I'm proposing is just being specific by listing the two
> >> mechanisms.  But, we can't just point to 3414 becaue it requires
> >> DES, hence the 3826 reference.  And, the reference to 5591 expands
> >> the options to allow RFC 6353.
> >
> > RFC 5591 does not have any "cryptographic mechanisms", so this is
> even
> > worse that RFC 3414 alone (which at least has DES). What about this:
> >
> >     It is RECOMMENDED that implementers consider the security
> features
> >     as provided by the SNMPv3 framework (see [RFC3410], section 8),
> >     including full support for authentication and privacy via the
> >     User-based Security Model (USM) [RFC3414] with the AES cipher
> >     algorithm [RFC3826] and the Transport Security Model (TSM)
> >     [RFC5591] in combination with a secure transport such as SSH
> >     [RFC5592] or TLS/DTLS [RFC6353].
> >
> > Probably a bit long. Here is a less verbose version:
> >
> >     It is RECOMMENDED that implementers consider the security
> features
> >     provided by the SNMPv3 framework (see [RFC3410], section 8),
> >     including full support for authentication and privacy via the
> >     User-based Security Model (USM) [RFC3414] [RFC3826] and the
> >     Transport Security Model (TSM) [RFC5591] [RFC5592] [RFC6353].
>=20
> I'd take either of these actually.  But, I like the former slightly
> more
> because it explains why 3826 is included and the includes the
> SSH/TLS/DTLS mechanisms.
>=20
[[DR]] I also prefer the first of the two versions as it makes clear the
models and the associated secure transports with the options.=20


> > Anyway, if we open up the security considerations template, we may
> > want to look at other wordings that often caused people to make
> > changed, e.g. the "even then" in the IPsec phrase (which IMHO should
> > simply be taken out).
>=20
> I'm okay with this too.
>=20
> > OLD:
> >
> >     SNMP versions prior to SNMPv3 did not include adequate security.
> >     Even if the network itself is secure (for example by using
> IPsec),
> >     even then, there is no control as to who on the secure network
is
> >     allowed to access and GET/SET (read/change/create/delete) the
> objects
> >     in this MIB module.
> >
> > NEW
> >
> >     SNMP versions prior to SNMPv3 did not include adequate security.
> >     Even if the network itself is secure (for example by using
> IPsec),
> >     there is no control as to who on the secure network is
> >     allowed to access and GET/SET (read/change/create/delete) the
> objects
> >     in this MIB module.
>=20
> I'm fine with this.
>=20
> > /js
> >
> > PS: Another good action would be to advance RFC3826 on the standards
> >      track - this is still a proposed standard...
>=20
> I'm willing to help out.  If we've got two interoperable
> implementations
> let's get'r done.
>=20
[[DR]] This could be done in OPSAWG. I do not remember if 3826 was done
in OPS or in SEC.=20

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

From turners@ieca.com  Thu Oct  6 03:11:26 2011
Return-Path: <turners@ieca.com>
X-Original-To: mib-doctors@ietfa.amsl.com
Delivered-To: mib-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E7A121F8CB1 for <mib-doctors@ietfa.amsl.com>; Thu,  6 Oct 2011 03:11:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.597
X-Spam-Level: 
X-Spam-Status: No, score=-101.597 tagged_above=-999 required=5 tests=[AWL=-0.199, BAYES_00=-2.599, J_CHICKENPOX_31=0.6, J_CHICKENPOX_43=0.6, UNPARSEABLE_RELAY=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9lHbX2jzaQu3 for <mib-doctors@ietfa.amsl.com>; Thu,  6 Oct 2011 03:11:25 -0700 (PDT)
Received: from nm18.bullet.mail.ac4.yahoo.com (nm18.bullet.mail.ac4.yahoo.com [98.139.52.215]) by ietfa.amsl.com (Postfix) with SMTP id A113421F8C32 for <mib-doctors@ietf.org>; Thu,  6 Oct 2011 03:11:25 -0700 (PDT)
Received: from [98.139.52.192] by nm18.bullet.mail.ac4.yahoo.com with NNFMP; 06 Oct 2011 10:14:31 -0000
Received: from [98.139.52.177] by tm5.bullet.mail.ac4.yahoo.com with NNFMP; 06 Oct 2011 10:14:31 -0000
Received: from [127.0.0.1] by omp1060.mail.ac4.yahoo.com with NNFMP; 06 Oct 2011 10:14:31 -0000
X-Yahoo-Newman-Id: 558664.12153.bm@omp1060.mail.ac4.yahoo.com
Received: (qmail 41076 invoked from network); 6 Oct 2011 10:14:30 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1317896070; bh=IhCJtsH4NIs+KnQTyoPJkpmx6sLVhDuL4LPrLPJLtkQ=; h=X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=JIjc2ZA4MTw3yoMLtT4kVLZtNZkYTO/mj9I8LqUhvEcTPcWj7d75F9xD+2PHfOQmxV6IGbznFfIq33JG27IAh+06Tz0x881c7kj4Rxi7w3TuIKLkNm4Zvmrv4UiA7Uo2Rz7DcEzSyeqOpoFmMGq0dn871qJwrLZRRRGgOrYvdLk=
X-Yahoo-Newman-Property: ymail-3
X-YMail-OSG: EYFzOBYVM1nYQGyepQqKwwjB6w9gTPGCoaBhtjIWVqVrOEQ E5vAzEKjuldDu_doSikejQbiTFEJ3wdWE3AzVGRMpvtCwCEKal7Fecj_jcWn DDIS4l7CyIJIcej7HB7kPwZeTm98jY.d5aKJDuGYCERZcs_e6qNoWT00tP2c ssaIiIJMOfWziMdLerOqeBc6cf9vQKkEuHJVCqd41BFYqPuT4yy0MmfmqXfU 9rm.RneqhNU8JHIN4y3ICJKdo1WCjzJ.xxPUBBXi.1deDZ6JOH9KAxg78ize DxAA5xvsUVspMwoOHBictusNHOPmXfgPSc1M66YE3dpAkdz9LpcYCzYPHu2a JO.RXFKFOjWSr5SkCjS_FPxQmEhVN3DOM9dTdak6Ee1vF9wANkDUqym2ztNn AZ6XCh_qxyTa3xBgoYkVlWFHte3CDMbga1Q3B
X-Yahoo-SMTP: ZrP3VLSswBDL75pF8ymZHDSu9B.vcMfDPgLJ
Received: from thunderfish.local (turners@71.191.1.163 with plain) by smtp113.biz.mail.mud.yahoo.com with SMTP; 06 Oct 2011 03:14:30 -0700 PDT
Message-ID: <4E8D7F85.6070106@ieca.com>
Date: Thu, 06 Oct 2011 06:14:29 -0400
From: Sean Turner <turners@ieca.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: "Romascanu, Dan \(Dan\)" <dromasca@avaya.com>
References: <4E8CA1F8.5040807@ieca.com> <20111005201335.GA48603@elstar.local> <4E8CCCB5.9090501@ieca.com> <EDC652A26FB23C4EB6384A4584434A0403BE90B0@307622ANEX5.global.avaya.com>
In-Reply-To: <EDC652A26FB23C4EB6384A4584434A0403BE90B0@307622ANEX5.global.avaya.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: mib-doctors@ietf.org
Subject: Re: [MIB-DOCTORS] Updates to the Guidelines of the Security Considerations section of the MIB documents
X-BeenThere: mib-doctors@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: MIB Doctors list <mib-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mib-doctors>
List-Post: <mailto:mib-doctors@ietf.org>
List-Help: <mailto:mib-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Oct 2011 10:11:26 -0000

On 10/6/11 4:58 AM, Romascanu, Dan (Dan) wrote:
> See in-line.
>
> Regards,
>
> Dan
>
>> -----Original Message-----
>> From: mib-doctors-bounces@ietf.org [mailto:mib-doctors-
>> bounces@ietf.org] On Behalf Of Sean Turner
>> Sent: Wednesday, October 05, 2011 11:32 PM
>> To: mib-doctors@ietf.org
>> Subject: Re: [MIB-DOCTORS] Updates to the Guidelines of the Security
>> Considerations section of the MIB documents
>>
>> On 10/5/11 4:13 PM, Juergen Schoenwaelder wrote:
>>> On Wed, Oct 05, 2011 at 02:29:12PM -0400, Sean Turner wrote:
>>>> Hi,
>>>>
>>>> After the publication of RFC 5591 and the fact that SNMP+DES really
>>>> ought to be replaced with SNMP+AES, I'd like to propose the
>>>> following change to the MIB security considerations:
>>>>
>>>> OLD:
>>>>
>>>>      It is RECOMMENDED that implementers consider the security
>> features
>>>>      as provided by the SNMPv3 framework (see [RFC3410], section 8),
>>>>      including full support for the SNMPv3 cryptographic mechanisms
>> (for
>>>>      authentication and privacy).
>>>>
>>>> NEW:
>>>>
>>>>      It is RECOMMENDED that implementers consider the security
>> features
>>>>      as provided by the SNMPv3 framework (see [RFC3410], section 8),
>>>>      including full support for the USM [RFC3414][RFC3826] and
>> Transport
>>>>      Security Model [RFC5591] cryptographic mechanisms (for
>> authentication
>>>>      and privacy).
>>>>
>>>> What I'm proposing is just being specific by listing the two
>>>> mechanisms.  But, we can't just point to 3414 becaue it requires
>>>> DES, hence the 3826 reference.  And, the reference to 5591 expands
>>>> the options to allow RFC 6353.
>>>
>>> RFC 5591 does not have any "cryptographic mechanisms", so this is
>> even
>>> worse that RFC 3414 alone (which at least has DES). What about this:
>>>
>>>      It is RECOMMENDED that implementers consider the security
>> features
>>>      as provided by the SNMPv3 framework (see [RFC3410], section 8),
>>>      including full support for authentication and privacy via the
>>>      User-based Security Model (USM) [RFC3414] with the AES cipher
>>>      algorithm [RFC3826] and the Transport Security Model (TSM)
>>>      [RFC5591] in combination with a secure transport such as SSH
>>>      [RFC5592] or TLS/DTLS [RFC6353].
>>>
>>> Probably a bit long. Here is a less verbose version:
>>>
>>>      It is RECOMMENDED that implementers consider the security
>> features
>>>      provided by the SNMPv3 framework (see [RFC3410], section 8),
>>>      including full support for authentication and privacy via the
>>>      User-based Security Model (USM) [RFC3414] [RFC3826] and the
>>>      Transport Security Model (TSM) [RFC5591] [RFC5592] [RFC6353].
>>
>> I'd take either of these actually.  But, I like the former slightly
>> more
>> because it explains why 3826 is included and the includes the
>> SSH/TLS/DTLS mechanisms.
>>
> [[DR]] I also prefer the first of the two versions as it makes clear the
> models and the associated secure transports with the options.
>
>
>>> Anyway, if we open up the security considerations template, we may
>>> want to look at other wordings that often caused people to make
>>> changed, e.g. the "even then" in the IPsec phrase (which IMHO should
>>> simply be taken out).
>>
>> I'm okay with this too.
>>
>>> OLD:
>>>
>>>      SNMP versions prior to SNMPv3 did not include adequate security.
>>>      Even if the network itself is secure (for example by using
>> IPsec),
>>>      even then, there is no control as to who on the secure network
> is
>>>      allowed to access and GET/SET (read/change/create/delete) the
>> objects
>>>      in this MIB module.
>>>
>>> NEW
>>>
>>>      SNMP versions prior to SNMPv3 did not include adequate security.
>>>      Even if the network itself is secure (for example by using
>> IPsec),
>>>      there is no control as to who on the secure network is
>>>      allowed to access and GET/SET (read/change/create/delete) the
>> objects
>>>      in this MIB module.
>>
>> I'm fine with this.
>>
>>> /js
>>>
>>> PS: Another good action would be to advance RFC3826 on the standards
>>>       track - this is still a proposed standard...
>>
>> I'm willing to help out.  If we've got two interoperable
>> implementations
>> let's get'r done.
>>
> [[DR]] This could be done in OPSAWG. I do not remember if 3826 was done
> in OPS or in SEC.

[spt] I think it was done in SEC because Steve Bellovin was the 
sponsoring AD.  However, I'm definitely not hard over having to sponsor 
it.  ISMS is closed now so maybe it's better to do this via OPSAWG.

spt

From bertietf@bwijnen.net  Thu Oct 13 03:24:04 2011
Return-Path: <bertietf@bwijnen.net>
X-Original-To: mib-doctors@ietfa.amsl.com
Delivered-To: mib-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B4EB21F8BAA for <mib-doctors@ietfa.amsl.com>; Thu, 13 Oct 2011 03:24:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.299
X-Spam-Level: 
X-Spam-Status: No, score=-102.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_31=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bk7+PnhVR3zH for <mib-doctors@ietfa.amsl.com>; Thu, 13 Oct 2011 03:24:04 -0700 (PDT)
Received: from postgirl.ripe.net (postgirl.ipv6.ripe.net [IPv6:2001:67c:2e8:11::c100:1342]) by ietfa.amsl.com (Postfix) with ESMTP id 2094121F8B95 for <mib-doctors@ietf.org>; Thu, 13 Oct 2011 03:24:02 -0700 (PDT)
Received: from ayeaye.ripe.net ([193.0.23.5]) by postgirl.ripe.net with esmtps (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from <bertietf@bwijnen.net>) id 1REISC-0007fH-Fw for mib-doctors@ietf.org; Thu, 13 Oct 2011 12:23:57 +0200
Received: from dog.ripe.net ([193.0.1.217] helo=guest187.guestnet.ripe.net) by ayeaye.ripe.net with esmtp (Exim 4.72) (envelope-from <bertietf@bwijnen.net>) id 1REISC-00051Z-6Y for mib-doctors@ietf.org; Thu, 13 Oct 2011 12:23:56 +0200
Message-ID: <4E96BC3B.2060004@bwijnen.net>
Date: Thu, 13 Oct 2011 12:23:55 +0200
From: "Bert Wijnen (IETF)" <bertietf@bwijnen.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: mib-doctors@ietf.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: 86ab03e524994f79ca2c75a176445dd497a0f53d2dc43db21062491c143f0aaf
Subject: [MIB-DOCTORS] help please - InetAddressType/InetAddress
X-BeenThere: mib-doctors@ietf.org
X-Mailman-Version: 2.1.12
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, 13 Oct 2011 10:24:04 -0000

I am working in the SIDR WG to create a rpkiRouterMib module.

They have large (can go up to 500K entries) tables that are
to be indexed by InetAddressType, InetAddress, InetPortNumber.

In principle, they only need ipv4 and ipv6 (current discussion
seems to not even want to allow for ipv4z or ipv6z). Not clear
yet if dns is wanted. I personally would be against allowing dns
in these huge tables because of indexing limitations and overhead
if we use dns names.

So my advise I think is that even in the OBJECT-TYPE definition
we will be explicit in stating that only ipv4 and ipv6 are valid
(allowed) values, and so for InetAddress we can limit the size to
(4|16).

Any objections against such advise?
Or any other comments/suggestions?

Thanks,
Bert

From j.schoenwaelder@jacobs-university.de  Thu Oct 13 03:42:51 2011
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 (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 16CDC21F87FA for <mib-doctors@ietfa.amsl.com>; Thu, 13 Oct 2011 03:42:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.717
X-Spam-Level: 
X-Spam-Status: No, score=-102.717 tagged_above=-999 required=5 tests=[AWL=-0.068, BAYES_00=-2.599, HELO_EQ_DE=0.35, J_CHICKENPOX_31=0.6, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 45utaDrBolJt for <mib-doctors@ietfa.amsl.com>; Thu, 13 Oct 2011 03:42:50 -0700 (PDT)
Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) by ietfa.amsl.com (Postfix) with ESMTP id 4FA9021F8BB7 for <mib-doctors@ietf.org>; Thu, 13 Oct 2011 03:42:50 -0700 (PDT)
Received: from localhost (demetrius4.jacobs-university.de [212.201.44.49]) by hermes.jacobs-university.de (Postfix) with ESMTP id 80C9320DA1; Thu, 13 Oct 2011 12:42:49 +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 Uxfcr8YHluRX; Thu, 13 Oct 2011 12:42:48 +0200 (CEST)
Received: from elstar.local (elstar.jacobs.jacobs-university.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id 343BE20D03; Thu, 13 Oct 2011 12:42:48 +0200 (CEST)
Received: by elstar.local (Postfix, from userid 501) id DC0CA1B21B08; Thu, 13 Oct 2011 12:42:34 +0200 (CEST)
Date: Thu, 13 Oct 2011 12:42:34 +0200
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: "Bert Wijnen (IETF)" <bertietf@bwijnen.net>
Message-ID: <20111013104234.GA23623@elstar.local>
Mail-Followup-To: "Bert Wijnen (IETF)" <bertietf@bwijnen.net>, mib-doctors@ietf.org
References: <4E96BC3B.2060004@bwijnen.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4E96BC3B.2060004@bwijnen.net>
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: mib-doctors@ietf.org
Subject: Re: [MIB-DOCTORS] help please - InetAddressType/InetAddress
X-BeenThere: mib-doctors@ietf.org
X-Mailman-Version: 2.1.12
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, 13 Oct 2011 10:42:51 -0000

On Thu, Oct 13, 2011 at 12:23:55PM +0200, Bert Wijnen (IETF) wrote:
> I am working in the SIDR WG to create a rpkiRouterMib module.
> 
> They have large (can go up to 500K entries) tables that are
> to be indexed by InetAddressType, InetAddress, InetPortNumber.
> 
> In principle, they only need ipv4 and ipv6 (current discussion
> seems to not even want to allow for ipv4z or ipv6z). Not clear
> yet if dns is wanted. I personally would be against allowing dns
> in these huge tables because of indexing limitations and overhead
> if we use dns names.
> 
> So my advise I think is that even in the OBJECT-TYPE definition
> we will be explicit in stating that only ipv4 and ipv6 are valid
> (allowed) values, and so for InetAddress we can limit the size to
> (4|16).
> 
> Any objections against such advise?
> Or any other comments/suggestions?

In some MIB modules, we have expressed address type constraints in
compliance statements rather than constraining the object definition:

        OBJECT      fooType
        SYNTAX      InetAddressType { ipv4(1), ipv6(2) }
        DESCRIPTION
            "An implementation is only required to support global IPv4
             and/or IPv6 address types."

This way, the object definition itself is not constrained but a
compliant implementation can be created by just supporting global IPv4
and/or IPv6 addresses (and the object definition would happily support
IPv8 if that were ever to happen ;-).

/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 bertietf@bwijnen.net  Thu Oct 13 04:16:06 2011
Return-Path: <bertietf@bwijnen.net>
X-Original-To: mib-doctors@ietfa.amsl.com
Delivered-To: mib-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 216CA21F85FF for <mib-doctors@ietfa.amsl.com>; Thu, 13 Oct 2011 04:16:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.149
X-Spam-Level: 
X-Spam-Status: No, score=-102.149 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, J_CHICKENPOX_31=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FwOIB8LVFuPk for <mib-doctors@ietfa.amsl.com>; Thu, 13 Oct 2011 04:16:05 -0700 (PDT)
Received: from postgirl.ripe.net (postgirl.ipv6.ripe.net [IPv6:2001:67c:2e8:11::c100:1342]) by ietfa.amsl.com (Postfix) with ESMTP id 7C58A21F85A8 for <mib-doctors@ietf.org>; Thu, 13 Oct 2011 04:16:04 -0700 (PDT)
Received: from ayeaye.ripe.net ([193.0.23.5]) by postgirl.ripe.net with esmtps (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from <bertietf@bwijnen.net>) id 1REJGa-0003Mr-4w for mib-doctors@ietf.org; Thu, 13 Oct 2011 13:16:02 +0200
Received: from dog.ripe.net ([193.0.1.217] helo=guest187.guestnet.ripe.net) by ayeaye.ripe.net with esmtp (Exim 4.72) (envelope-from <bertietf@bwijnen.net>) id 1REJGZ-0001zq-TD for mib-doctors@ietf.org; Thu, 13 Oct 2011 13:16:00 +0200
Message-ID: <4E96C86F.2040300@bwijnen.net>
Date: Thu, 13 Oct 2011 13:15:59 +0200
From: "Bert Wijnen (IETF)" <bertietf@bwijnen.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: mib-doctors@ietf.org
References: <4E96BC3B.2060004@bwijnen.net> <20111013104234.GA23623@elstar.local>
In-Reply-To: <20111013104234.GA23623@elstar.local>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-RIPE-Spam-Level: --
X-RIPE-Spam-Report: Spam Total Points:   -2.9 points pts rule name              description ---- ---------------------- ------------------------------------ -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP -1.9 BAYES_00               BODY: Bayes spam probability is 0 to 1% [score: 0.0000]
X-RIPE-Signature: 86ab03e524994f79ca2c75a176445dd4646bd496dfbd20e8b0275fc0437cb77f
Subject: Re: [MIB-DOCTORS] help please - InetAddressType/InetAddress
X-BeenThere: mib-doctors@ietf.org
X-Mailman-Version: 2.1.12
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, 13 Oct 2011 11:16:06 -0000

Inline

On 10/13/11 12:42 PM, Juergen Schoenwaelder wrote:
> On Thu, Oct 13, 2011 at 12:23:55PM +0200, Bert Wijnen (IETF) wrote:
>> I am working in the SIDR WG to create a rpkiRouterMib module.
>>
>> They have large (can go up to 500K entries) tables that are
>> to be indexed by InetAddressType, InetAddress, InetPortNumber.
>>
>> In principle, they only need ipv4 and ipv6 (current discussion
>> seems to not even want to allow for ipv4z or ipv6z). Not clear
>> yet if dns is wanted. I personally would be against allowing dns
>> in these huge tables because of indexing limitations and overhead
>> if we use dns names.
>>
>> So my advise I think is that even in the OBJECT-TYPE definition
>> we will be explicit in stating that only ipv4 and ipv6 are valid
>> (allowed) values, and so for InetAddress we can limit the size to
>> (4|16).
>>
>> Any objections against such advise?
>> Or any other comments/suggestions?
>
> In some MIB modules, we have expressed address type constraints in
> compliance statements rather than constraining the object definition:
>
>          OBJECT      fooType
>          SYNTAX      InetAddressType { ipv4(1), ipv6(2) }
>          DESCRIPTION
>              "An implementation is only required to support global IPv4
>               and/or IPv6 address types."
>
> This way, the object definition itself is not constrained but a
> compliant implementation can be created by just supporting global IPv4
> and/or IPv6 addresses (and the object definition would happily support
> IPv8 if that were ever to happen ;-).
>

YES, I am aware of that.
But if I do it that way, then (since the objects are used as Indices) I
MUST explain things like:
- make sure to not create indices that are more than 128 subIDs
- when dns gets resolved if they use it
- etc
And none of that seems needed in the forseeable future if I just
be explicit in the OBJECT-TYPE as opposed to the module-compliance.
In the MODULE compliance I also have to put it in as comments,
since they are index objects and so I cannot list them as OBJECTs.

Oh well.

Bert

> /js
>

From hhazewinkel@gmail.com  Thu Oct 13 04:30:54 2011
Return-Path: <hhazewinkel@gmail.com>
X-Original-To: mib-doctors@ietfa.amsl.com
Delivered-To: mib-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 23E5C21F84D3 for <mib-doctors@ietfa.amsl.com>; Thu, 13 Oct 2011 04:30:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.999
X-Spam-Level: 
X-Spam-Status: No, score=-2.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_31=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p0m0YOUE9EfS for <mib-doctors@ietfa.amsl.com>; Thu, 13 Oct 2011 04:30:53 -0700 (PDT)
Received: from mail-ey0-f172.google.com (mail-ey0-f172.google.com [209.85.215.172]) by ietfa.amsl.com (Postfix) with ESMTP id 0E68821F84D4 for <mib-doctors@ietf.org>; Thu, 13 Oct 2011 04:30:52 -0700 (PDT)
Received: by eyg24 with SMTP id 24so1836546eyg.31 for <mib-doctors@ietf.org>; Thu, 13 Oct 2011 04:30:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=nbj6T5vlAVy++F4J0ris7/sY0ff2SowYz9MMHziDSbE=; b=vh0OGOXnbLTemlEETg63+wQN6krEYMUxs1KLxvdaqkOXfb4GhjG+8KVihTJXFDWwuX zQVXClIvRy4iTwAFqWthNCZlPyJOgZA/W1Z1qsEL2sPBoSgMHhBYHGXgq+nJCgKF9Uoi ZJfzPABi0VGdoZCzuAN3Cw98jBURG14Y6jenI=
Received: by 10.213.16.198 with SMTP id p6mr567255eba.74.1318505450286; Thu, 13 Oct 2011 04:30:50 -0700 (PDT)
Received: from [192.168.50.106] ([87.213.99.166]) by mx.google.com with ESMTPS id y11sm13533076eej.5.2011.10.13.04.30.49 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 13 Oct 2011 04:30:49 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Harrie Hazewinkel <hhazewinkel@gmail.com>
In-Reply-To: <4E96C86F.2040300@bwijnen.net>
Date: Thu, 13 Oct 2011 13:30:48 +0200
Content-Transfer-Encoding: 7bit
Message-Id: <E30282E3-7C51-4FEF-9FBA-D239CCAE72B3@gmail.com>
References: <4E96BC3B.2060004@bwijnen.net> <20111013104234.GA23623@elstar.local> <4E96C86F.2040300@bwijnen.net>
To: Bert Wijnen (IETF) <bertietf@bwijnen.net>
X-Mailer: Apple Mail (2.1084)
Cc: mib-doctors@ietf.org
Subject: Re: [MIB-DOCTORS] help please - InetAddressType/InetAddress
X-BeenThere: mib-doctors@ietf.org
X-Mailman-Version: 2.1.12
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, 13 Oct 2011 11:30:54 -0000

Hi,

Would it not make sense to have a specific object that just combines
the two kinds (ipv4 and ipv6) of the InetAddress and so the DNS part
just by type 'ignores'?

I somehow see the need to be flexible enough to have all future changes
possible and supported, but should we not look at today and not to
some potential ipv8 (or ipv10, ..)?

Just thinking of the concern of Bert regarding the indexes and what it
would bring that other InetAddressTypes are supported.


regards,
Harrie

On Oct 13, 2011, at 1:15 PM, Bert Wijnen (IETF) wrote:

> Inline
> 
> On 10/13/11 12:42 PM, Juergen Schoenwaelder wrote:
>> On Thu, Oct 13, 2011 at 12:23:55PM +0200, Bert Wijnen (IETF) wrote:
>>> I am working in the SIDR WG to create a rpkiRouterMib module.
>>> 
>>> They have large (can go up to 500K entries) tables that are
>>> to be indexed by InetAddressType, InetAddress, InetPortNumber.
>>> 
>>> In principle, they only need ipv4 and ipv6 (current discussion
>>> seems to not even want to allow for ipv4z or ipv6z). Not clear
>>> yet if dns is wanted. I personally would be against allowing dns
>>> in these huge tables because of indexing limitations and overhead
>>> if we use dns names.
>>> 
>>> So my advise I think is that even in the OBJECT-TYPE definition
>>> we will be explicit in stating that only ipv4 and ipv6 are valid
>>> (allowed) values, and so for InetAddress we can limit the size to
>>> (4|16).
>>> 
>>> Any objections against such advise?
>>> Or any other comments/suggestions?
>> 
>> In some MIB modules, we have expressed address type constraints in
>> compliance statements rather than constraining the object definition:
>> 
>>         OBJECT      fooType
>>         SYNTAX      InetAddressType { ipv4(1), ipv6(2) }
>>         DESCRIPTION
>>             "An implementation is only required to support global IPv4
>>              and/or IPv6 address types."
>> 
>> This way, the object definition itself is not constrained but a
>> compliant implementation can be created by just supporting global IPv4
>> and/or IPv6 addresses (and the object definition would happily support
>> IPv8 if that were ever to happen ;-).
>> 
> 
> YES, I am aware of that.
> But if I do it that way, then (since the objects are used as Indices) I
> MUST explain things like:
> - make sure to not create indices that are more than 128 subIDs
> - when dns gets resolved if they use it
> - etc
> And none of that seems needed in the forseeable future if I just
> be explicit in the OBJECT-TYPE as opposed to the module-compliance.
> In the MODULE compliance I also have to put it in as comments,
> since they are index objects and so I cannot list them as OBJECTs.
> 
> Oh well.
> 
> Bert
> 
>> /js
>> 
> _______________________________________________
> MIB-DOCTORS mailing list
> MIB-DOCTORS@ietf.org
> https://www.ietf.org/mailman/listinfo/mib-doctors

Harrie
hhazewinkel@gmail.com





From j.schoenwaelder@jacobs-university.de  Thu Oct 13 04:51:45 2011
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 (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8023621F8B80 for <mib-doctors@ietfa.amsl.com>; Thu, 13 Oct 2011 04:51:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.713
X-Spam-Level: 
X-Spam-Status: No, score=-102.713 tagged_above=-999 required=5 tests=[AWL=-0.064, BAYES_00=-2.599, HELO_EQ_DE=0.35, J_CHICKENPOX_31=0.6, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ym95GGiR3FyT for <mib-doctors@ietfa.amsl.com>; Thu, 13 Oct 2011 04:51:44 -0700 (PDT)
Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) by ietfa.amsl.com (Postfix) with ESMTP id AC9D921F87C9 for <mib-doctors@ietf.org>; Thu, 13 Oct 2011 04:51:38 -0700 (PDT)
Received: from localhost (demetrius1.jacobs-university.de [212.201.44.46]) by hermes.jacobs-university.de (Postfix) with ESMTP id 182D920E69; Thu, 13 Oct 2011 13:51:38 +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 vSu_z2tMkREQ; Thu, 13 Oct 2011 13:51:36 +0200 (CEST)
Received: from elstar.local (elstar.jacobs.jacobs-university.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id 882DE20E5B; Thu, 13 Oct 2011 13:51:36 +0200 (CEST)
Received: by elstar.local (Postfix, from userid 501) id 338B71B2222A; Thu, 13 Oct 2011 13:51:23 +0200 (CEST)
Date: Thu, 13 Oct 2011 13:51:23 +0200
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: "Bert Wijnen (IETF)" <bertietf@bwijnen.net>
Message-ID: <20111013115123.GC23623@elstar.local>
Mail-Followup-To: "Bert Wijnen (IETF)" <bertietf@bwijnen.net>, mib-doctors@ietf.org
References: <4E96BC3B.2060004@bwijnen.net> <20111013104234.GA23623@elstar.local> <4E96C86F.2040300@bwijnen.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4E96C86F.2040300@bwijnen.net>
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: mib-doctors@ietf.org
Subject: Re: [MIB-DOCTORS] help please - InetAddressType/InetAddress
X-BeenThere: mib-doctors@ietf.org
X-Mailman-Version: 2.1.12
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, 13 Oct 2011 11:51:45 -0000

On Thu, Oct 13, 2011 at 01:15:59PM +0200, Bert Wijnen (IETF) wrote:
> Inline
> 
> On 10/13/11 12:42 PM, Juergen Schoenwaelder wrote:
> >On Thu, Oct 13, 2011 at 12:23:55PM +0200, Bert Wijnen (IETF) wrote:
> >>I am working in the SIDR WG to create a rpkiRouterMib module.
> >>
> >>They have large (can go up to 500K entries) tables that are
> >>to be indexed by InetAddressType, InetAddress, InetPortNumber.
> >>
> >>In principle, they only need ipv4 and ipv6 (current discussion
> >>seems to not even want to allow for ipv4z or ipv6z). Not clear
> >>yet if dns is wanted. I personally would be against allowing dns
> >>in these huge tables because of indexing limitations and overhead
> >>if we use dns names.
> >>
> >>So my advise I think is that even in the OBJECT-TYPE definition
> >>we will be explicit in stating that only ipv4 and ipv6 are valid
> >>(allowed) values, and so for InetAddress we can limit the size to
> >>(4|16).
> >>
> >>Any objections against such advise?
> >>Or any other comments/suggestions?
> >
> >In some MIB modules, we have expressed address type constraints in
> >compliance statements rather than constraining the object definition:
> >
> >         OBJECT      fooType
> >         SYNTAX      InetAddressType { ipv4(1), ipv6(2) }
> >         DESCRIPTION
> >             "An implementation is only required to support global IPv4
> >              and/or IPv6 address types."
> >
> >This way, the object definition itself is not constrained but a
> >compliant implementation can be created by just supporting global IPv4
> >and/or IPv6 addresses (and the object definition would happily support
> >IPv8 if that were ever to happen ;-).
> >
> 
> YES, I am aware of that.
> But if I do it that way, then (since the objects are used as Indices) I
> MUST explain things like:
> - make sure to not create indices that are more than 128 subIDs
> - when dns gets resolved if they use it
> - etc
> And none of that seems needed in the forseeable future if I just
> be explicit in the OBJECT-TYPE as opposed to the module-compliance.
> In the MODULE compliance I also have to put it in as comments,
> since they are index objects and so I cannot list them as OBJECTs.

OK, I missed the INDEX part. Well, if the WG is sure nothing else than
global IPv4 and IPv6 addresses will ever be needed, just subtype the
object definitions. I am not familiar with the RPKI stuff so I simply
have no clue. ;-)

/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 macfaden@gmail.com  Sat Oct 15 21:59:48 2011
Return-Path: <macfaden@gmail.com>
X-Original-To: mib-doctors@ietfa.amsl.com
Delivered-To: mib-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3D65B21F85B1 for <mib-doctors@ietfa.amsl.com>; Sat, 15 Oct 2011 21:59:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.71
X-Spam-Level: 
X-Spam-Status: No, score=-0.71 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, J_CHICKENPOX_31=0.6, RCVD_IN_DNSWL_LOW=-1, SARE_HTML_USL_OBFU=1.666]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E6Z9-VDVbRt3 for <mib-doctors@ietfa.amsl.com>; Sat, 15 Oct 2011 21:59:47 -0700 (PDT)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id 80D9521F85AA for <mib-doctors@ietf.org>; Sat, 15 Oct 2011 21:59:47 -0700 (PDT)
Received: by wwe6 with SMTP id 6so445417wwe.13 for <mib-doctors@ietf.org>; Sat, 15 Oct 2011 21:59:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=ViGFsLu/DmtB/Z1zQDBX8eX+cvbXXWSueFOIZVzBrb4=; b=DKoMsYrDUWVHkKIJKlJnDjFFou+U9vDl55nAMj3XvD+nmVle2zjWy4Aoz35uMZqg/A rDoF8YYL5HXqBkSZ75L/5Wmr2PThxCDJTU0M/3rW+PaJsX2vcOXhq2ENohAV678yv85+ Oh68jBYeenK2WBmwLYxf0mwp9YITH6H6g8y78=
MIME-Version: 1.0
Received: by 10.216.133.12 with SMTP id p12mr1991461wei.99.1318741186486; Sat, 15 Oct 2011 21:59:46 -0700 (PDT)
Sender: macfaden@gmail.com
Received: by 10.180.8.67 with HTTP; Sat, 15 Oct 2011 21:59:46 -0700 (PDT)
Received: by 10.180.8.67 with HTTP; Sat, 15 Oct 2011 21:59:46 -0700 (PDT)
In-Reply-To: <4E96BC3B.2060004@bwijnen.net>
References: <4E96BC3B.2060004@bwijnen.net>
Date: Sat, 15 Oct 2011 21:59:46 -0700
X-Google-Sender-Auth: 0DUSr9-b7NOXBe565IZEkBP-6PM
Message-ID: <CAD3a8T=CPuOnb3+8tP9MH5d9OYUu+wg9faBudgB+22NJ5CSw7g@mail.gmail.com>
From: Michael MacFaden <mrm@macfaden.com>
To: "Bert Wijnen (IETF)" <bertietf@bwijnen.net>
Content-Type: multipart/alternative; boundary=0016e6dd893af8a2fa04af635b06
Cc: mib-doctors@ietf.org
Subject: Re: [MIB-DOCTORS] help please - InetAddressType/InetAddress
X-BeenThere: mib-doctors@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: MIB Doctors list <mib-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mib-doctors>
List-Post: <mailto:mib-doctors@ietf.org>
List-Help: <mailto:mib-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 16 Oct 2011 04:59:48 -0000

--0016e6dd893af8a2fa04af635b06
Content-Type: text/plain; charset=ISO-8859-1

Hi Bert

This restriction seems reasonable to me. The rationale added to the mib
module should be clear as to why the limitation exists.

Mike
On Oct 13, 2011 3:24 AM, "Bert Wijnen (IETF)" <bertietf@bwijnen.net> wrote:

> I am working in the SIDR WG to create a rpkiRouterMib module.
>
> They have large (can go up to 500K entries) tables that are
> to be indexed by InetAddressType, InetAddress, InetPortNumber.
>
> In principle, they only need ipv4 and ipv6 (current discussion
> seems to not even want to allow for ipv4z or ipv6z). Not clear
> yet if dns is wanted. I personally would be against allowing dns
> in these huge tables because of indexing limitations and overhead
> if we use dns names.
>
> So my advise I think is that even in the OBJECT-TYPE definition
> we will be explicit in stating that only ipv4 and ipv6 are valid
> (allowed) values, and so for InetAddress we can limit the size to
> (4|16).
>
> Any objections against such advise?
> Or any other comments/suggestions?
>
> Thanks,
> Bert
> ______________________________**_________________
> MIB-DOCTORS mailing list
> MIB-DOCTORS@ietf.org
> https://www.ietf.org/mailman/**listinfo/mib-doctors<https://www.ietf.org/mailman/listinfo/mib-doctors>
>

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

<p>Hi Bert</p>
<p>This restriction seems reasonable to me. The rationale added to the mib =
module should be clear as to why the limitation exists.</p>
<p>Mike</p>
<div class=3D"gmail_quote">On Oct 13, 2011 3:24 AM, &quot;Bert Wijnen (IETF=
)&quot; &lt;<a href=3D"mailto:bertietf@bwijnen.net">bertietf@bwijnen.net</a=
>&gt; wrote:<br type=3D"attribution"><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I am working in the SIDR WG to create a rpkiRouterMib module.<br>
<br>
They have large (can go up to 500K entries) tables that are<br>
to be indexed by InetAddressType, InetAddress, InetPortNumber.<br>
<br>
In principle, they only need ipv4 and ipv6 (current discussion<br>
seems to not even want to allow for ipv4z or ipv6z). Not clear<br>
yet if dns is wanted. I personally would be against allowing dns<br>
in these huge tables because of indexing limitations and overhead<br>
if we use dns names.<br>
<br>
So my advise I think is that even in the OBJECT-TYPE definition<br>
we will be explicit in stating that only ipv4 and ipv6 are valid<br>
(allowed) values, and so for InetAddress we can limit the size to<br>
(4|16).<br>
<br>
Any objections against such advise?<br>
Or any other comments/suggestions?<br>
<br>
Thanks,<br>
Bert<br>
______________________________<u></u>_________________<br>
MIB-DOCTORS mailing list<br>
<a href=3D"mailto:MIB-DOCTORS@ietf.org" target=3D"_blank">MIB-DOCTORS@ietf.=
org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/mib-doctors" target=3D"_bl=
ank">https://www.ietf.org/mailman/<u></u>listinfo/mib-doctors</a><br>
</blockquote></div>

--0016e6dd893af8a2fa04af635b06--

From dromasca@avaya.com  Fri Oct 28 09:15:44 2011
Return-Path: <dromasca@avaya.com>
X-Original-To: mib-doctors@ietfa.amsl.com
Delivered-To: mib-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 35B0621F8AFE; Fri, 28 Oct 2011 09:15:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.253
X-Spam-Level: 
X-Spam-Status: No, score=-103.253 tagged_above=-999 required=5 tests=[AWL=0.346, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dOzqvPxWnL0S; Fri, 28 Oct 2011 09:15:43 -0700 (PDT)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by ietfa.amsl.com (Postfix) with ESMTP id E8A6421F8AE1; Fri, 28 Oct 2011 09:15:41 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AicFAAbUqk6HCzI1/2dsb2JhbAA6CYR3mSaKQIEDgQWBcgEBAQEDEhENBFEGAQgNCAUCBgYMCwECAgMBHyUHAQYEAQQBEggTB6AoiV+RToEwhCWCGjNhBJlZhGqHKw
X-IronPort-AV: E=Sophos;i="4.69,419,1315195200"; d="scan'208";a="274931732"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by de307622-de-outbound.net.avaya.com with ESMTP; 28 Oct 2011 12:15:39 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 28 Oct 2011 12:04:55 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Date: Fri, 28 Oct 2011 18:15:35 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A04042DF197@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
thread-topic: PRELIMINARY Agenda and Package for the November 3, 2011 IESG Teleconference 
thread-index: AcyU+ET7yxvnWFf0RhqqDZ5x30WN1wAk9K1w
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <aaa-doctors@ietf.org>, <mib-doctors@ietf.org>, "YANG Doctors" <yang-doctors@ietf.org>, <ops-dir@ietf.org>, <dns-dir@ietf.org>
Subject: [MIB-DOCTORS] FW: PRELIMINARY Agenda and Package for the November 3, 2011 IESG Teleconference
X-BeenThere: mib-doctors@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: MIB Doctors list <mib-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mib-doctors>
List-Post: <mailto:mib-doctors@ietf.org>
List-Help: <mailto:mib-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Oct 2011 16:15:44 -0000

UGxlYXNlIGZpbmQgYmVsb3cgdGhlIHByZWxpbWluYXJ5IGFnZW5kYSBvZiB0aGUgSUVTRyB0ZWxl
Y2hhdCBzY2hlZHVsZWQgZm9yIDExLzMuIFBsZWFzZSBzZW5kIG1lIHlvdXIgY29tbWVudHMsIHF1
ZXN0aW9ucyBhbmQgY29uY2VybnMgYWJvdXQgdGhlIGRvY3VtZW50cyBicm91Z2h0LXVwIGZvciBh
cHByb3ZhbCBiZWZvcmUgMTEvMiBDT0IuIA0KDQpUaGFua3MgYW5kIFJlZ2FyZHMsDQoNCkRhbg0K
DQoNCg0KDQotLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KRnJvbTogaWVzZy1ib3VuY2VzQGll
dGYub3JnIFttYWlsdG86aWVzZy1ib3VuY2VzQGlldGYub3JnXSBPbiBCZWhhbGYgT2YgSUVTRyBT
ZWNyZXRhcnkNCg0KDQoyLiBQcm90b2NvbCBBY3Rpb25zDQoyLjEgV0cgU3VibWlzc2lvbnMNCjIu
MS4xIE5ldyBJdGVtcw0KDQogIG8gZHJhZnQtaWV0Zi1tbXVzaWMtaWNlLXRjcC0xNQ0KICAgIFRD
UCBDYW5kaWRhdGVzIHdpdGggSW50ZXJhY3RpdmUgQ29ubmVjdGl2aXR5IEVzdGFibGlzaG1lbnQg
KElDRSkNCiAgICAoUHJvcG9zZWQgU3RhbmRhcmQpDQogICAgTm90ZTogRmxlbW1pbmcgQW5kcmVh
c2VuIChmYW5kcmVhc0BjaXNjby5jb20pIGlzIHRoZSBkb2N1bWVudA0KICAgIHNoZXBoZXJkLg0K
ICAgIFRva2VuOiBHb256YWxvIENhbWFyaWxsbw0KDQogIG8gZHJhZnQtaWV0Zi1mZWNmcmFtZS1y
dHAtcmFwdG9yLTA1DQogICAgUlRQIFBheWxvYWQgRm9ybWF0IGZvciBSYXB0b3IgRkVDIChQcm9w
b3NlZCBTdGFuZGFyZCkNCiAgICBOb3RlOiBHcmVnIFNoZXBoZXJkIChnanNoZXBAZ21haWwuY29t
KSBpcyB0aGUgZG9jdW1lbnQgc2hlcGhlcmQuDQogICAgVG9rZW46IERhdmlkIEhhcnJpbmd0b24N
Cg0KICBvIGRyYWZ0LWlldGYtb3NwZi1hdXRoLXRyYWlsZXItb3NwZnYzLTA4DQogICAgU3VwcG9y
dGluZyBBdXRoZW50aWNhdGlvbiBUcmFpbGVyIGZvciBPU1BGdjMgKFByb3Bvc2VkIFN0YW5kYXJk
KQ0KICAgIE5vdGU6IEFiaGF5IFJveSAoYWtyQGNpc2NvLmNvbSkgaXMgdGhlIGRvY3VtZW50IHNo
ZXBoZXJkLg0KICAgIFRva2VuOiBTdGV3YXJ0IEJyeWFudA0KDQogIG8gZHJhZnQtaWV0Zi1taXA0
LW5lbW92NC1keW5hbWljLTA1DQogICAgRHluYW1pYyBQcmVmaXggQWxsb2NhdGlvbiBmb3IgTkVN
T3Y0IChQcm9wb3NlZCBTdGFuZGFyZCkNCiAgICBOb3RlOiBQZXRlIE1jQ2FubiAobWNjYXBAcGV0
b25pLm9yZykgaXMgdGhlIGRvY3VtZW50IHNoZXBoZXJkLg0KICAgIFRva2VuOiBKYXJpIEFya2tv
DQoNCiAgbyBkcmFmdC1pZXRmLXB3ZTMtc3RhdGljLXB3LXN0YXR1cy0wOQ0KICAgIFBzZXVkb3dp
cmUgU3RhdHVzIGZvciBTdGF0aWMgUHNldWRvd2lyZXMgKFByb3Bvc2VkIFN0YW5kYXJkKQ0KICAg
IE5vdGU6IEFuZHkgTWFsaXMgKGFtYWxpc0BnbWFpbC5jb20pIGlzIHRoZSBkb2N1bWVudCBzaGVw
aGVyZC4NCiAgICBUb2tlbjogU3Rld2FydCBCcnlhbnQNCg0KICBvIGRyYWZ0LWlldGYtcGF5bG9h
ZC1yZmMzMTg5YmlzLTAzDQogICAgUlRQIFBheWxvYWQgRm9ybWF0IGZvciBEViAoSUVDIDYxODM0
KSBWaWRlbyAoUHJvcG9zZWQgU3RhbmRhcmQpDQogICAgTm90ZTogVGhlIGRvY3VtZW50IHNoZXBo
ZXJkIGlzIFJvbmkgRXZlbiAoRXZlbi5yb25pQGh1YXdlaS5jb20pLg0KICAgIFRva2VuOiBSb2Jl
cnQgU3BhcmtzDQoNCiAgbyBkcmFmdC1pZXRmLWF2dGV4dC1jbGllbnQtdG8tbWl4ZXItYXVkaW8t
bGV2ZWwtMDUNCiAgICBBIFJlYWwtVGltZSBUcmFuc3BvcnQgUHJvdG9jb2wgKFJUUCkgSGVhZGVy
IEV4dGVuc2lvbiBmb3IgQ2xpZW50LXRvLQ0KICAgIE1peGVyIEF1ZGlvIExldmVsIEluZGljYXRp
b24gKFByb3Bvc2VkIFN0YW5kYXJkKQ0KICAgIE5vdGU6IEtlaXRoIERyYWdlIChrZWl0aC5kcmFn
ZUBhbGNhdGVsLWx1Y2VudC5jb20pIGlzIHRoZSBkb2N1bWVudA0KICAgIHNoZXBoZXJkLg0KICAg
IFRva2VuOiBHb256YWxvIENhbWFyaWxsbw0KDQogIG8gZHJhZnQtaWV0Zi1hdnRleHQtbWl4ZXIt
dG8tY2xpZW50LWF1ZGlvLWxldmVsLTA1DQogICAgQSBSZWFsLVRpbWUgVHJhbnNwb3J0IFByb3Rv
Y29sIChSVFApIEhlYWRlciBFeHRlbnNpb24gZm9yIE1peGVyLXRvLQ0KICAgIENsaWVudCBBdWRp
byBMZXZlbCBJbmRpY2F0aW9uIChQcm9wb3NlZCBTdGFuZGFyZCkNCiAgICBOb3RlOiBLZWl0aCBE
cmFnZSAoa2VpdGguZHJhZ2VAYWxjYXRlbC1sdWNlbnQuY29tKSBpcyB0aGUgZG9jdW1lbnQNCiAg
ICBzaGVwaGVyZC4NCiAgICBUb2tlbjogR29uemFsbyBDYW1hcmlsbG8NCg0KICBvIGRyYWZ0LWll
dGYtdmNhcmRkYXYta2luZC1hcHAtMDANCiAgICB2Q2FyZCBLSU5EOmFwcGxpY2F0aW9uIChQcm9w
b3NlZCBTdGFuZGFyZCkNCiAgICBOb3RlOiBTaW1vbiBQZXJyZWF1bHQgKHNpbW9uLnBlcnJlYXVs
dEB2aWFnZW5pZS5jYSkgaXMgdGhlIGRvY3VtZW50DQogICAgc2hlcGhlcmQuDQogICAgVG9rZW46
IFBldGUgUmVzbmljaw0KDQogIG8gZHJhZnQtaWV0Zi12Y2FyZGRhdi1iaXJ0aC1kZWF0aC1leHRl
bnNpb25zLTAxDQogICAgdkNhcmQgRm9ybWF0IEV4dGVuc2lvbnMgOiBwbGFjZSBvZiBiaXJ0aCwg
cGxhY2UgYW5kIGRhdGUgb2YgZGVhdGgNCiAgICAoUHJvcG9zZWQgU3RhbmRhcmQpDQogICAgVG9r
ZW46IFBldGVyIFNhaW50LUFuZHJlDQoNCiAgbyBkcmFmdC1pZXRmLWF2dGNvcmUtc3J0cC12YnIt
YXVkaW8tMDMNCiAgICBHdWlkZWxpbmVzIGZvciB0aGUgdXNlIG9mIFZhcmlhYmxlIEJpdCBSYXRl
IEF1ZGlvIHdpdGggU2VjdXJlIFJUUA0KICAgIChCQ1ApDQogICAgTm90ZTogTWFnbnVzIFdlc3Rl
cmx1bmQgKG1hZ251cy53ZXN0ZXJsdW5kQGVyaWNzc29uLmNvbSkgaXMgdGhlDQogICAgZG9jdW1l
bnQgc2hlcGhlcmQuDQogICAgVG9rZW46IFJvYmVydCBTcGFya3MNCg0KICBvIGRyYWZ0LWlldGYt
dGxzLWR0bHMtaGVhcnRiZWF0LTAzDQogICAgVHJhbnNwb3J0IExheWVyIFNlY3VyaXR5IChUTFMp
IGFuZCBEYXRhZ3JhbSBUcmFuc3BvcnQgTGF5ZXIgU2VjdXJpdHkNCiAgICAoRFRMUykgSGVhcnRi
ZWF0IEV4dGVuc2lvbiAoUHJvcG9zZWQgU3RhbmRhcmQpDQogICAgTm90ZTogSm9lIFNhbG93ZXkg
KGpzYWxvd2V5QGNpc2NvLmNvbSkgaXMgdGhlIGRvY3VtZW50IHNoZXBoZXJkLg0KICAgIFRva2Vu
OiBTZWFuIFR1cm5lcg0KDQogIG8gZHJhZnQtaWV0Zi1pcHBtLW1ldHJpY3Rlc3QtMDQNCiAgICBJ
UFBNIHN0YW5kYXJkIGFkdmFuY2VtZW50IHRlc3RpbmcgKFByb3Bvc2VkIFN0YW5kYXJkKQ0KICAg
IE5vdGU6IEhlbmsgVWlqdGVyd2FhbCAoaGVua0B1aWp0ZXJ3YWFsLm5sKSBpcyB0aGUgZG9jdW1l
bnQgc2hlcGhlcmQuDQogICAgVG9rZW46IFdlc2xleSBFZGR5DQoNCiAgbyBkcmFmdC1pZXRmLXRj
cG0tcmZjMTk0OGJpcy0wMQ0KICAgIERlZmVuZGluZyBBZ2FpbnN0IFNlcXVlbmNlIE51bWJlciBB
dHRhY2tzIChQcm9wb3NlZCBTdGFuZGFyZCkNCiAgICBOb3RlOiBEYXZpZCBCb3JtYW4gKGRhdmlk
LmJvcm1hbkB3aW5kcml2ZXIuY29tKSBpcyB0aGUgZG9jdW1lbnQNCiAgICBzaGVwaGVyZC4NCiAg
ICBUb2tlbjogV2VzbGV5IEVkZHkNCg0KMi4xLjIgUmV0dXJuaW5nIEl0ZW1zDQoNCiAgTk9ORQ0K
DQoyLjIgSW5kaXZpZHVhbCBTdWJtaXNzaW9ucw0KMi4yLjEgTmV3IEl0ZW1zDQoNCiAgTk9ORQ0K
DQoyLjIuMiBSZXR1cm5pbmcgSXRlbXMNCg0KICBOT05FDQoNCjMuIERvY3VtZW50IEFjdGlvbnMN
CjMuMSBXRyBTdWJtaXNzaW9ucw0KMy4xLjEgTmV3IEl0ZW1zDQoNCiAgbyBkcmFmdC1pZXRmLXJt
dC1zaW1wbGUtYXV0aC1mb3ItYWxjLW5vcm0tMDUNCiAgICBTaW1wbGUgQXV0aGVudGljYXRpb24g
U2NoZW1lcyBmb3IgdGhlIEFMQyBhbmQgTk9STSBQcm90b2NvbHMNCiAgICAoRXhwZXJpbWVudGFs
KQ0KICAgIE5vdGU6IEJyaWFuIEFkYW1zb24gKGFkYW1zb25AaXRkLm5ybC5uYXZ5Lm1pbCkgaXMg
dGhlIGRvY3VtZW50DQogICAgc2hlcGhlcmQuDQogICAgVG9rZW46IERhdmlkIEhhcnJpbmd0b24N
Cg0KICBvIGRyYWZ0LWlldGYtbWlwNC1uZW1vLWhhYXJvLTA2DQogICAgSG9tZSBBZ2VudCBhc3Np
c3RlZCBSb3V0ZSBPcHRpbWl6YXRpb24gYmV0d2VlbiBNb2JpbGUgSVB2NCBOZXR3b3Jrcw0KICAg
IChFeHBlcmltZW50YWwpDQogICAgTm90ZTogUGV0ZSBNY0Nhbm4gKG1jY2FwQHBldG9uaS5vcmcp
IGlzIHRoZSBkb2N1bWVudCBzaGVwaGVyZC4NCiAgICBUb2tlbjogSmFyaSBBcmtrbw0KDQogIG8g
ZHJhZnQtaWV0Zi1mZWNmcmFtZS1jb25maWctc2lnbmFsaW5nLTA2DQogICAgTWV0aG9kcyB0byBj
b252ZXkgRkVDIEZyYW1ld29yayBDb25maWd1cmF0aW9uIEluZm9ybWF0aW9uDQogICAgKEV4cGVy
aW1lbnRhbCkNCiAgICBOb3RlOiBHcmVnIFNoZXBoZXJkIChnanNoZXBAZ21haWwuY29tKSBpcyB0
aGUgZG9jdW1lbnQgc2hlcGhlcmQuDQogICAgVG9rZW46IERhdmlkIEhhcnJpbmd0b24NCg0KICBv
IGRyYWZ0LWlldGYtcGltLXBvcnQtMDkNCiAgICBBIFJlbGlhYmxlIFRyYW5zcG9ydCBNZWNoYW5p
c20gZm9yIFBJTSAoRXhwZXJpbWVudGFsKQ0KICAgIE5vdGU6IE1pa2UgTWNCcmlkZSAobW1jYnJp
ZGVAY2lzY28uY29tKSBpcyB0aGUgZG9jdW1lbnQgc2hlcGhlcmQuDQogICAgVG9rZW46IEFkcmlh
biBGYXJyZWwNCg0KICBvIGRyYWZ0LWlldGYtZHJpbmtzLXVzZWNhc2VzLXJlcXVpcmVtZW50cy0w
Ng0KICAgIERhdGEgZm9yIFJlYWNoYWJpbGl0eSBvZiBJbnRlci90cmEtTmV0d29ySyBTSVAgKERS
SU5LUykgVXNlIGNhc2VzDQogICAgYW5kIFByb3RvY29sIFJlcXVpcmVtZW50cyAoSW5mb3JtYXRp
b25hbCkNCiAgICBOb3RlOiBBbGV4YW5kZXIgTWF5cmhvZmVyIChhbGV4YW5kZXIubWF5cmhvZmVy
QG5pYy5hdCkgaXMgdGhlDQogICAgZG9jdW1lbnQgc2hlcGhlcmQuDQogICAgVG9rZW46IEdvbnph
bG8gQ2FtYXJpbGxvDQoNCiAgbyBkcmFmdC1pZXRmLWNjYW1wLXdzb24taW1wYWlybWVudHMtMDcN
CiAgICBBIEZyYW1ld29yayBmb3IgdGhlIENvbnRyb2wgb2YgV2F2ZWxlbmd0aCBTd2l0Y2hlZCBP
cHRpY2FsIE5ldHdvcmtzDQogICAgKFdTT04pIHdpdGggSW1wYWlybWVudHMgKEluZm9ybWF0aW9u
YWwpDQogICAgTm90ZTogRGVib3JhaCBCcnVuZ2FyZCAoZGJydW5nYXJkQGF0dC5jb20pIGlzIHRo
ZSBEb2N1bWVudCBTaGVwaGVyZC4NCiAgICBUb2tlbjogQWRyaWFuIEZhcnJlbA0KDQozLjEuMiBS
ZXR1cm5pbmcgSXRlbXMNCg0KICBvIGRyYWZ0LWlldGYtc2F2aS1mcmFtZXdvcmstMDUNCiAgICBT
b3VyY2UgQWRkcmVzcyBWYWxpZGF0aW9uIEltcHJvdmVtZW50IEZyYW1ld29yayAoSW5mb3JtYXRp
b25hbCkNCiAgICBOb3RlOiBKZWFuLU1pY2hlbCBDb21iZXMgKGplYW5taWNoZWwuY29tYmVzQGdt
YWlsLmNvbSkgaXMgdGhlDQogICAgZG9jdW1lbnQgc2hlcGhlcmQuDQogICAgVG9rZW46IEphcmkg
QXJra28NCg0KICBvIGRyYWZ0LWlldGYtY3Vzcy1zaXAtdXVpLXJlcXMtMDcNCiAgICBQcm9ibGVt
IFN0YXRlbWVudCBhbmQgUmVxdWlyZW1lbnRzIGZvciBUcmFuc3BvcnRpbmcgVXNlciB0byBVc2Vy
DQogICAgQ2FsbCBDb250cm9sIEluZm9ybWF0aW9uIGluIFNJUCAoSW5mb3JtYXRpb25hbCkNCiAg
ICBOb3RlOiBWaWpheSBLLiBHdXJiYW5pICh2a2dAYmVsbC1sYWJzLmNvbSkgaXMgdGhlIGRvY3Vt
ZW50IHNoZXBoZXJkLg0KICAgIFRva2VuOiBHb256YWxvIENhbWFyaWxsbw0KDQozLjIgSW5kaXZp
ZHVhbCBTdWJtaXNzaW9ucyBWaWEgQUQNCjMuMi4xIE5ldyBJdGVtcw0KDQogIG8gZHJhZnQtc3By
ZWNoZXItbXBscy10cC1vYW0tY29uc2lkZXJhdGlvbnMtMDENCiAgICBUaGUgUmVhc29ucyBmb3Ig
U2VsZWN0aW5nIGEgU2luZ2xlIFNvbHV0aW9uIGZvciBNUExTLVRQIE9BTQ0KICAgIChJbmZvcm1h
dGlvbmFsKQ0KICAgIE5vdGU6IFJvc3MgQ2FsbG9uIChyY2FsbG9uQGp1bmlwZXIubmV0KSBpcyB0
aGUgZG9jdW1lbnQgc2hlcGhlcmQuDQogICAgVG9rZW46IEFkcmlhbiBGYXJyZWwNCg0KICBvIGRy
YWZ0LXNhbHRlci1yZmM1NDMwYmlzLTAxDQogICAgU3VpdGUgQiBQcm9maWxlIGZvciBUcmFuc3Bv
cnQgTGF5ZXIgU2VjdXJpdHkgKFRMUykgKEluZm9ybWF0aW9uYWwpDQogICAgTm90ZTogUnVzcyBI
b3VzbGV5IGlzIHRoZSBEb2N1bWVudCBTaGVwaGVyZC4NCiAgICBUb2tlbjogU2VhbiBUdXJuZXIN
Cg0KMy4yLjIgUmV0dXJuaW5nIEl0ZW1zDQoNCiAgTk9ORQ0KDQozLjMgSVJURiBhbmQgSW5kZXBl
bmRlbnQgU3VibWlzc2lvbiBTdHJlYW0gRG9jdW1lbnRzDQozLjMuMSBOZXcgSXRlbXMNCg0KICBv
IGRyYWZ0LWlydGYtaGlwLWV4cGVyaW1lbnQtMTMNCiAgICBISVAgRXhwZXJpbWVudCBSZXBvcnQg
KEluZm9ybWF0aW9uYWwpDQogICAgTm90ZTogVGhlIGRvY3VtZW50IHNoZXBoZXJkIGlzIFRvbSBI
ZW5kZXJzb24NCiAgICAodGhvbWFzLnIuaGVuZGVyc29uQGJvZWluZy5jb20pDQogICAgVG9rZW46
IFJhbHBoIERyb21zDQoNCiAgbyBkcmFmdC1pcnRmLWhpcHJnLWRodC0wNA0KICAgIEhvc3QgSWRl
bnRpdHkgUHJvdG9jb2wgRGlzdHJpYnV0ZWQgSGFzaCBUYWJsZSBJbnRlcmZhY2UNCiAgICAoRXhw
ZXJpbWVudGFsKQ0KICAgIE5vdGU6IFRoZSBkb2N1bWVudCBzaGVwaGVyZCBpcyBUb20gSGVuZGVy
c29uDQogICAgKHRob21hcy5yLmhlbmRlcnNvbkBib2VpbmcuY29tKS4NCiAgICBUb2tlbjogUmFs
cGggRHJvbXMNCg0KICBvIGRyYWZ0LWNha3VsZXYtaWJha2UtMDUNCiAgICBJQkFLRTogSWRlbnRp
dHktQmFzZWQgQXV0aGVudGljYXRlZCBLZXkgRXhjaGFuZ2UgKEluZm9ybWF0aW9uYWwpDQogICAg
VG9rZW46IFNlYW4gVHVybmVyDQoNCjMuMy4yIFJldHVybmluZyBJdGVtcw0KDQogIE5PTkUNCg0K
NC4gV29ya2luZyBHcm91cCBBY3Rpb25zDQo0LjEgV0cgQ3JlYXRpb24NCjQuMS4xIFByb3Bvc2Vk
IGZvciBJRVRGIFJldmlldw0KDQogIE5PTkUNCg0KNC4xLjIgUHJvcG9zZWQgZm9yIEFwcHJvdmFs
DQoNCiAgTk9ORQ0KDQo0LjIgV0cgUmVjaGFydGVyaW5nDQo0LjIuMSBVbmRlciBFdmFsdWF0aW9u
IGZvciBJRVRGIFJldmlldw0KDQogIG8gSVAgRmxvdyBJbmZvcm1hdGlvbiBFeHBvcnQgKGlwZml4
KQ0KICAgIFRva2VuOiBEYW4NCg0KDQo=

From dromasca@avaya.com  Sun Oct 30 04:18:28 2011
Return-Path: <dromasca@avaya.com>
X-Original-To: mib-doctors@ietfa.amsl.com
Delivered-To: mib-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C1F721F8AB9 for <mib-doctors@ietfa.amsl.com>; Sun, 30 Oct 2011 04:18:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.776
X-Spam-Level: 
X-Spam-Status: No, score=-102.776 tagged_above=-999 required=5 tests=[AWL=-0.177, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W3vLhjxl76hD for <mib-doctors@ietfa.amsl.com>; Sun, 30 Oct 2011 04:18:27 -0700 (PDT)
Received: from p-us1-iereast-outbound.us1.avaya.com (p-us1-iereast-outbound.us1.avaya.com [135.11.29.13]) by ietfa.amsl.com (Postfix) with ESMTP id B455621F8AB0 for <mib-doctors@ietf.org>; Sun, 30 Oct 2011 04:18:26 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjEDAIkxrU6HCzI1/2dsb2JhbAA6CZlriXaFXoEFgXIBAQEBAwEBAQ8eCjQEBwwEAgEIDQQEAQEBCgYMCwEGASYfCQgBAQQKCQgBGYdolzOaKIVUgk1hBJlajBQ
X-IronPort-AV: E=Sophos;i="4.69,426,1315195200"; d="scan'208";a="215394118"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by p-us1-iereast-outbound.us1.avaya.com with ESMTP; 30 Oct 2011 07:18:25 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 30 Oct 2011 07:07:37 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Sun, 30 Oct 2011 12:18:22 +0100
Message-ID: <EDC652A26FB23C4EB6384A4584434A04042DF300@307622ANEX5.global.avaya.com>
In-Reply-To: <98E5CB79-FA71-422C-AE57-89FE2FC041A0@charter.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
thread-topic: [rbridge] [MIB-DOCTORS] Volunteer needed to reviewdraft-ietf-trill-rbridge-mib-03
thread-index: AcyVI5skcMJ5eFU+TYy3N3pmjFvfpgB0cagw
References: <EDC652A26FB23C4EB6384A4584434A04037E1827@307622ANEX5.global.avaya.com> <EDC652A26FB23C4EB6384A4584434A040385FE8B@307622ANEX5.global.avaya.com> <8484B35D-1805-4ECC-8BF3-FDBB2FD7FE00@charter.net> <EDC652A26FB23C4EB6384A4584434A0403952B3A@307622ANEX5.global.avaya.com> <98E5CB79-FA71-422C-AE57-89FE2FC041A0@charter.net>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Anil Rijhsinghani" <anil@charter.net>
Cc: rbridge@postel.org, mib-doctors@ietf.org, Ralph Droms <rdroms.ietf@gmail.com>
Subject: Re: [MIB-DOCTORS] [rbridge] Volunteer needed to reviewdraft-ietf-trill-rbridge-mib-03
X-BeenThere: mib-doctors@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: MIB Doctors list <mib-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mib-doctors>
List-Post: <mailto:mib-doctors@ietf.org>
List-Help: <mailto:mib-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 30 Oct 2011 11:18:28 -0000

Hi Anil,

The changes look fine. Please go ahead to the next step as advised by
your AD.=20

The other MIB doctors are of course invited to jump in, possibly during
the IETF LC.=20

Dan




> -----Original Message-----
> From: Anil Rijhsinghani [mailto:anil@charter.net]
> Sent: Friday, October 28, 2011 5:42 AM
> To: Romascanu, Dan (Dan)
> Cc: rbridge@postel.org; mib-doctors@ietf.org; Ralph Droms
> Subject: Re: [rbridge] [MIB-DOCTORS] Volunteer needed to reviewdraft-
> ietf-trill-rbridge-mib-03
>=20
> Dan,
>=20
> Most of your feedback has been incorporated into the latest draft,
> draft-ietf-trill-rbridge-mib-04.txt. Please see comments below.
>=20
> >> Regarding your first comment, please note that references to IEEE
> > 802.1
> >> MIB modules have been added to the "Relationships" section,
> following
> >> your earlier round of comments. We cannot eliminate references to
> the
> >> IETF MIB modules, given that the vast majority of vendors have
> >> implemented those.
> >>
> > [[DR]] Understood. However, somebody who starts writing an
> > implementation today will probably look to the more recent MIB
> modules
> > and these are the one published by the IEEE 802.1 WG. I would at
> least
> > provide also the name of the MIB groups in the IEEE 802.1 MIB
> modules,
> > include references and even provide a paragraph that says that
Bridge
> > MIB work has been transferred to the IEEE 802.1 WG as per [RFC4663].
>=20
> A paragraph has been added to section 6 on relationship with IETF and
> IEEE Bridge MIBs as well as a reference to RFC 4663. In addition, MIB
> groups in IEEE 802.1 MIB modules have been added in the relationships
> section.
>=20
> >>> 2. There are several tables with read-create objects but no
> > rowStatus
> >>> object - rbridgeBaseNicknameTable, rbridgeBasePortTable,
> >>> rbridgeVlanPortTable, etc.
>=20
> rbridgeBasePortTable and rbridgeVlanPortTable should have been using
> read-write objects, and have been updated accordingly.
> rbridgeNicknameTable
> and rbridgeEsadiTable, which contain read-create objects, have status
> objects which, in addition to facilitating creation and deletion of
> rows, also
> serve additional purposes.
>=20
> >>>
> >>> 3. There are several writeable objects and tables with writeable
> >> objects
> >>> but no rowStorageType or any indication about persistency
>=20
> Information about persistency has been added to all read-write and
> read-create objects.
>=20
> >>>
> >>> 4. In several places SYNTAX of Integer32 is used for range
positive
> >>> integers. RFC 4181, section 4.6.1.1 says:
> >>>
> >>> - If the value range is between 0..4294967295 (inclusive), and
> > values
> >>>    greater than 2147483647 are possible, and the value of the
> >>>    information being modelled does not increase above the maximum
> >>>    value nor decrease below the minimum value, then:
> >>>
> >>>    - Unsigned32 is RECOMMENDED;
> >>>    - Gauge32 is acceptable;
> >>>    - INTEGER and Integer32 MUST NOT be used.
>=20
> All Integer32 objects have been changed to Unsigned32.
>=20
> >>>
> >>> 5. Use of Inter32 (0-65535) for port numbers instead of using
> >>> InetPortNumber from RFC4001
>=20
> Please note that these are Bridge port numbers, and not TCP/UDP
> port numbers, as defined by InetPortNumber. The syntax used for these
> objects is the same as that in the original Bridge MIBs.
>=20
> >>>
> >>> 6. SMICng strict checking gives:
> >>>
> >>> W: f(trill-rbridge.mi2), (46,17) The first revision should match
> the
> >>> last update for MODULE-IDENTITY rbridgeMIB
>=20
> Fixed.
>=20
> >>> W: f(trill-rbridge.mi2), (299,4) Sequence "RBridgeBasePortEntry"
> and
> >> Row
> >>> "rbridgeBasePortEntry" should have related names
>=20
> Fixed.
>=20
> >>> E: f(trill-rbridge.mi2), (299,4) Row "rbridgeBasePortEntry" may
not
> >> have
> >>> columns with MAX-ACCESS of read-write if any column is read-create
>=20
> Fixed.
>=20
> >>> E: f(trill-rbridge.mi2), (608,18) Index item "dot1qFdbId" must be
> >>> defined with syntax that includes a range
>=20
> Fixed. (rbridgeFdbId has been defined, with a range.)
>=20
> >>> W: f(trill-rbridge.mi2), (810,20) Item "rbridgeMultiFibPorts"
> should
> >>> have SIZE specified
>=20
> Cannot specify size as this is dependent on number of ports. See
> original Bridge MIBs.
>=20
> >>> E: f(trill-rbridge.mi2), (838,18) Index item "dot1qVlanIndex" must
> > be
> >>> defined with syntax that includes a range
>=20
> Fixed. (rbridgeVlanIndex has been defined, with a range.)
>=20
> >>> E: f(trill-rbridge.mi2), (912,18) Index item "dot1qVlanIndex" must
> > be
> >>> defined with syntax that includes a range
>=20
> Fixed.
>=20
> >>> E: f(trill-rbridge.mi2), (1113,18) Index item "dot1qVlanIndex"
must
> >> be
> >>> defined with syntax that includes a range
>=20
> Fixed.
>=20
> >>> E: f(trill-rbridge.mi2), (1272,17) Index item "dot1qVlanIndex"
must
> >> be
> >>> defined with syntax that includes a range
>=20
> Fixed.
>=20
> >>> W: f(trill-rbridge.mi2), (1265,4) Row "rbridgeSnoopingAddrEntry"
> has
> >>> indexing that may create variables with more than 128 sub-ids
>=20
> The index is (IP address, IP address type) which in the case of IPv6
> may
> cause sub-ids to be long. I don't see a way to get around this. Has
> this been
> an issue in other MIBs?
>=20
> >>> W: f(trill-rbridge.mi2), (1310,20) Item "rbridgeSnoopingAddrPorts"
> >>> should have SIZE specified
>=20
> Depends on number of ports.
>=20
> >>> W: f(trill-rbridge.mi2), (838,18) Row "rbridgeVlanEntry" does not
> >> have a
> >>> consistent indexing scheme - index items must be in same order as
> >> used
> >>> in INDEX cl ause for "base row" dot1qVlanCurrentEntry
>=20
> I believe this will be fixed with the use of rbridgeVlanIndex.
>=20
> >>> W: f(trill-rbridge.mi2), (912,18) Row "rbridgeVlanPortEntry" does
> > not
> >>> have a consistent indexing scheme - cannot specify an index item
> > from
> >>> additional "bas e row" dot1qVlanCurrentEntry, since can have only
> > one
> >>> "base row" which is rbridgeBasePortEntry
>=20
> I believe this will be fixed with the use of rbridgeVlanIndex.
>=20
> >>> W: f(trill-rbridge.mi2), (1113,18) Row "rbridgeEsadiEntry" does
not
> >> have
> >>> a consistent indexing scheme - index items must be in same order
as
> >> used
> >>> in INDEX clause for "base row" dot1qVlanCurrentEntry
>=20
> I believe this will be fixed with the use of rbridgeVlanIndex.
>=20
> >>> W: f(trill-rbridge.mi2), (1272,17) Row "rbridgeSnoopingAddrEntry"
> >> does
> >>> not have a consistent indexing scheme - index items must be in
same
> >>> order as used in  INDEX clause for "base row"
dot1qVlanCurrentEntry
>=20
> I believe this will be fixed with the use of rbridgeVlanIndex.
>=20
> >>>
> >>> 7. Objects like rbridgeBaseUniMultipathEnable or
> >>> rbridgeBaseMultiMultipathEnable could use the TruthValue TC as
> >> SYNTAX.
>=20
> OK, done.
>=20
> >>>
> >>> 8. UNITS clauses would be useful for counter objects.
>=20
> Done. In addition, large counters have been made Counter64, instead
> of using "overflow" Counter32.
>=20
> >>>
> >>> 9. There is no indication about the behavior of tables that
contain
> >>> counters wrt. counters discontinuity or any discontinuity
indicator
> >>> objects defined. (see section 4.6.1.2 in RFC 4181 for this)
>=20
> Added.
>=20
> Regards,
> Anil
>=20
>=20
> On Sep 5, 2011, at 11:47 AM, Romascanu, Dan (Dan) wrote:
>=20
> > Hi Anil,
> >
> > See in line.
> >
> > Thanks and Regards,
> >
> > Dan
> >
> >
> >
> >
> >> -----Original Message-----
> >> From: Anil Rijhsinghani [mailto:anil@charter.net]
> >> Sent: Friday, September 02, 2011 8:55 PM
> >> To: Romascanu, Dan (Dan)
> >> Cc: mib-doctors@ietf.org; rbridge@postel.org; Ralph Droms
> >> Subject: Re: [rbridge] [MIB-DOCTORS] Volunteer needed to
> reviewdraft-
> >> ietf-trill-rbridge-mib-03
> >>
> >> Hi Dan,
> >>
> >> I'm working through all your syntactical suggestions, and will wait
> to
> >> hear from you about any additional comments from MIB doctors.
> >>
> > [[DR]] I suggest that you do not wait for further comments and
> published
> > a revised version when you feel that you are ready, addressing the
> > comments received until now.
> >
> >
> >> Regarding your first comment, please note that references to IEEE
> > 802.1
> >> MIB modules have been added to the "Relationships" section,
> following
> >> your earlier round of comments. We cannot eliminate references to
> the
> >> IETF MIB modules, given that the vast majority of vendors have
> >> implemented those.
> >>
> > [[DR]] Understood. However, somebody who starts writing an
> > implementation today will probably look to the more recent MIB
> modules
> > and these are the one published by the IEEE 802.1 WG. I would at
> least
> > provide also the name of the MIB groups in the IEEE 802.1 MIB
> modules,
> > include references and even provide a paragraph that says that
Bridge
> > MIB work has been transferred to the IEEE 802.1 WG as per [RFC4663].
> >
> >> Regards,
> >> Anil
> >>
> >> On Aug 18, 2011, at 9:40 AM, Romascanu, Dan (Dan) wrote:
> >>
> >>> Hi,
> >>>
> >>> We did not receive any volunteering offers. The list is still open
> >> and
> >>> the MIB doctors are invited to step ahead.
> >>>
> >>> Bert and me did however a quick review of the I-D. Here are our
> >>> findings. Please treat them as review comments, but keep in mind
> > that
> >>> the list is not final and more things may accumulate.
> >>>
> >>> I would also note that I reviewed a previous version of the MIB
> >> module
> >>> and document and made a number of comments. Not all were taken
into
> >>> consideration.
> >>>
> >>> 1. The relationship with other MIB module sections refer to the
> IETF
> >>> RFCs. However, since 2006 the development of the Bridge MIB
modules
> >> and
> >>> their successors were transferred to IEEE 802.1. I suggest to
> define
> >> the
> >>> relationship sections in relation to the IEEE MIB modules
> >>>
> >>> 2. There are several tables with read-create objects but no
> > rowStatus
> >>> object - rbridgeBaseNicknameTable, rbridgeBasePortTable,
> >>> rbridgeVlanPortTable, etc.
> >>>
> >>> 3. There are several writeable objects and tables with writeable
> >> objects
> >>> but no rowStorageType or any indication about persistency
> >>>
> >>> 4. In several places SYNTAX of Integer32 is used for range
positive
> >>> integers. RFC 4181, section 4.6.1.1 says:
> >>>
> >>> - If the value range is between 0..4294967295 (inclusive), and
> > values
> >>>    greater than 2147483647 are possible, and the value of the
> >>>    information being modelled does not increase above the maximum
> >>>    value nor decrease below the minimum value, then:
> >>>
> >>>    - Unsigned32 is RECOMMENDED;
> >>>    - Gauge32 is acceptable;
> >>>    - INTEGER and Integer32 MUST NOT be used.
> >>>
> >>> 5. Use of Inter32 (0-65535) for port numbers instead of using
> >>> InetPortNumber from RFC4001
> >>>
> >>> 6. SMICng strict checking gives:
> >>>
> >>> W: f(trill-rbridge.mi2), (46,17) The first revision should match
> the
> >>> last update for MODULE-IDENTITY rbridgeMIB
> >>> W: f(trill-rbridge.mi2), (299,4) Sequence "RBridgeBasePortEntry"
> and
> >> Row
> >>> "rbridgeBasePortEntry" should have related names
> >>> E: f(trill-rbridge.mi2), (299,4) Row "rbridgeBasePortEntry" may
not
> >> have
> >>> columns with MAX-ACCESS of read-write if any column is read-create
> >>> E: f(trill-rbridge.mi2), (608,18) Index item "dot1qFdbId" must be
> >>> defined with syntax that includes a range
> >>> W: f(trill-rbridge.mi2), (810,20) Item "rbridgeMultiFibPorts"
> should
> >>> have SIZE specified
> >>> E: f(trill-rbridge.mi2), (838,18) Index item "dot1qVlanIndex" must
> > be
> >>> defined with syntax that includes a range
> >>> E: f(trill-rbridge.mi2), (912,18) Index item "dot1qVlanIndex" must
> > be
> >>> defined with syntax that includes a range
> >>> E: f(trill-rbridge.mi2), (1113,18) Index item "dot1qVlanIndex"
must
> >> be
> >>> defined with syntax that includes a range
> >>> E: f(trill-rbridge.mi2), (1272,17) Index item "dot1qVlanIndex"
must
> >> be
> >>> defined with syntax that includes a range
> >>> W: f(trill-rbridge.mi2), (1265,4) Row "rbridgeSnoopingAddrEntry"
> has
> >>> indexing that may create variables with more than 128 sub-ids
> >>> W: f(trill-rbridge.mi2), (1310,20) Item "rbridgeSnoopingAddrPorts"
> >>> should have SIZE specified
> >>> W: f(trill-rbridge.mi2), (838,18) Row "rbridgeVlanEntry" does not
> >> have a
> >>> consistent indexing scheme - index items must be in same order as
> >> used
> >>> in INDEX cl ause for "base row" dot1qVlanCurrentEntry
> >>> W: f(trill-rbridge.mi2), (912,18) Row "rbridgeVlanPortEntry" does
> > not
> >>> have a consistent indexing scheme - cannot specify an index item
> > from
> >>> additional "bas e row" dot1qVlanCurrentEntry, since can have only
> > one
> >>> "base row" which is rbridgeBasePortEntry
> >>> W: f(trill-rbridge.mi2), (1113,18) Row "rbridgeEsadiEntry" does
not
> >> have
> >>> a consistent indexing scheme - index items must be in same order
as
> >> used
> >>> in INDEX clause for "base row" dot1qVlanCurrentEntry
> >>> W: f(trill-rbridge.mi2), (1272,17) Row "rbridgeSnoopingAddrEntry"
> >> does
> >>> not have a consistent indexing scheme - index items must be in
same
> >>> order as used in  INDEX clause for "base row"
dot1qVlanCurrentEntry
> >>>
> >>> 7. Objects like rbridgeBaseUniMultipathEnable or
> >>> rbridgeBaseMultiMultipathEnable could use the TruthValue TC as
> >> SYNTAX.
> >>>
> >>> 8. UNITS clauses would be useful for counter objects.
> >>>
> >>> 9. There is no indication about the behavior of tables that
contain
> >>> counters wrt. counters discontinuity or any discontinuity
indicator
> >>> objects defined. (see section 4.6.1.2 in RFC 4181 for this)
> >>>
> >>>
> >>> Regards,
> >>>
> >>> Dan
> >>>
> >>>
> >>>
> >>>> -----Original Message-----
> >>>> From: mib-doctors-bounces@ietf.org [mailto:mib-doctors-
> >>>> bounces@ietf.org] On Behalf Of Romascanu, Dan (Dan)
> >>>> Sent: Thursday, August 11, 2011 3:27 PM
> >>>> To: mib-doctors@ietf.org
> >>>> Cc: Ralph Droms
> >>>> Subject: [MIB-DOCTORS] Volunteer needed to
reviewdraft-ietf-trill-
> >>>> rbridge-mib-03
> >>>>
> >>>> MIB-Doctors,
> >>>>
> >>>> We need a volunteer to review
> >>>> http://www.ietf.org/id/draft-ietf-trill-rbridge-mib-03.txt. The
> >>>> document
> >>>> is co-authored by Anil Rijhsinghani (author of the original
Bridge
> >>> MIB)
> >>>> and looks in pretty good shape.
> >>>>
> >>>> Thanks and Regards,
> >>>>
> >>>> Dan
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> _______________________________________________
> >>>> MIB-DOCTORS mailing list
> >>>> MIB-DOCTORS@ietf.org
> >>>> https://www.ietf.org/mailman/listinfo/mib-doctors
> >>>
> >>> _______________________________________________
> >>> rbridge mailing list
> >>> rbridge@postel.org
> >>> http://mailman.postel.org/mailman/listinfo/rbridge
> >
> >
> > _______________________________________________
> > rbridge mailing list
> > rbridge@postel.org
> > http://mailman.postel.org/mailman/listinfo/rbridge


From dromasca@avaya.com  Sun Oct 30 06:26:40 2011
Return-Path: <dromasca@avaya.com>
X-Original-To: mib-doctors@ietfa.amsl.com
Delivered-To: mib-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A8DA421F8B21; Sun, 30 Oct 2011 06:26:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.329
X-Spam-Level: 
X-Spam-Status: No, score=-103.329 tagged_above=-999 required=5 tests=[AWL=0.270, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iZQVWc8JnlS4; Sun, 30 Oct 2011 06:26:40 -0700 (PDT)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by ietfa.amsl.com (Postfix) with ESMTP id C843F21F8B1C; Sun, 30 Oct 2011 06:26:39 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Aj8SAFpQrU6HCzI1/2dsb2JhbABCo2KFXoEFgXQBAQMSHgpRARUVBgwMB1cBBAEaGp8dmiyIIWEEmVqMFA
X-IronPort-AV: E=Sophos;i="4.69,426,1315195200"; d="scan'208";a="275132013"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by de307622-de-outbound.net.avaya.com with ESMTP; 30 Oct 2011 09:26:15 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 30 Oct 2011 09:15:26 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Sun, 30 Oct 2011 14:26:11 +0100
Message-ID: <EDC652A26FB23C4EB6384A4584434A04042DF342@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
thread-topic: MIB and YANG Doctors Dinner at IETF-82
thread-index: AcyXB32sJFTXgdVUQS2cqxdWsEcSaw==
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <mib-doctors@ietf.org>, "YANG Doctors" <yang-doctors@ietf.org>
Subject: [MIB-DOCTORS] MIB and YANG Doctors Dinner at IETF-82
X-BeenThere: mib-doctors@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: MIB Doctors list <mib-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mib-doctors>
List-Post: <mailto:mib-doctors@ietf.org>
List-Help: <mailto:mib-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 30 Oct 2011 13:26:40 -0000

As usual the MIB and the YANG Doctors will meet for dinner at IETF-82 on
Sunday (11/13) at 19:00, after the IETF Welcome Reception. Location and
details TBD.=20

Thanks and Regards,

Dan



