
From glenn@cysols.com  Wed Sep  1 08:15:07 2010
Return-Path: <glenn@cysols.com>
X-Original-To: isms@core3.amsl.com
Delivered-To: isms@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 716E63A68BD; Wed,  1 Sep 2010 08:15:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.196
X-Spam-Level: 
X-Spam-Status: No, score=0.196 tagged_above=-999 required=5 tests=[AWL=0.286,  BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zVFKfQiLaLDB; Wed,  1 Sep 2010 08:15:03 -0700 (PDT)
Received: from niseko.cysol.co.jp (niseko.cysol.co.jp [210.233.3.236]) by core3.amsl.com (Postfix) with ESMTP id 907023A6812; Wed,  1 Sep 2010 08:15:02 -0700 (PDT)
Received: from [127.0.0.1] (cysvpn03.priv.cysol.co.jp [192.168.0.90]) (authenticated bits=0) by aso.priv.cysol.co.jp (8.14.4/8.14.4) with ESMTP id o81FFGub052809 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Thu, 2 Sep 2010 00:15:25 +0900 (JST) (envelope-from glenn@cysols.com)
Message-ID: <4C7E6E01.9090107@cysols.com>
Date: Thu, 02 Sep 2010 00:15:13 +0900
From: "Glenn M. Keeni" <glenn@cysols.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2
MIME-Version: 1.0
To: mib-doctors@ietf.org, "isms@ietf.org" <isms@ietf.org>
References: <002b01cb4967$d099f180$6801a8c0@oemcomputer>
In-Reply-To: <002b01cb4967$d099f180$6801a8c0@oemcomputer>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
Subject: Re: [Isms] [MIB-DOCTORS] Updated version of draft-ietf-isms-radius-vacm
X-BeenThere: isms@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mailing list for the ISMS working group <isms.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isms>
List-Post: <mailto:isms@ietf.org>
List-Help: <mailto:isms-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Sep 2010 15:15:07 -0000

Hi,
  Thanks. At a quick glance this document is certainly looking much
better. I will going through this in detail and will try to get my
review there ASAP. But one issue that is certainly unresolved is
the following-

On 2010/08/23 22:28, Glenn M. Keeni wrote:
> 10.2.3 In the DESCRIPTION vacmAaaSecurityToGroupEntry row object.
> |     vacmAaaSecurityToGroupEntry OBJECT-TYPE
> |         SYNTAX       VacmAaaSecurityToGroupEntry
> |         MAX-ACCESS   not-accessible
> |         STATUS       current
> |         DESCRIPTION "An entry in this table maps the combination of a
> |                      SnmpSecurityModel and SecurityName into a
> GroupName for
> |                      a particular session.
> |
> |                      Each entry corresponds to a session.
> |
> |                      Entries do not persist across reboots.
> |
> |                      When a session is torn down, disconnected,
timed out
> |                      (e.g. following the RADIUS Session-Timeout
> Attribute),
> |                      or otherwise terminated for any reason, the
> |                      corresponding vacmAaaSecurityToGroupEntry is
> deleted."
>
>        There is a need to mention the conditions under which the row is
>        created.
>        According to RFC 4181
>         "If the agent itself may also create and/or delete rows, then the
>          conditions under which this can occur MUST be clearly documented
>          in the row object DESCRIPTION clause."
>
>        The details are present in Section 7.2.1. Please add the relevant
>        part to the DESCRIPTION clause of this object. (That includes the
>        row update protocol.)

This issue needs fixing.

Glenn




On 2010/09/01 8:54, Randy Presuhn wrote:
> Hi -
> 
> I've posted an update to the radius vacm draft.  Due to the large
> number of (conflicting) comments and responses, I think this version
> needs close inspection.  I've tried to balance the various
> comments, but in some cases I could not see a middle ground.
> In other cases, I've tried to balance conflicting comments, and
> made changes different from what were suggested by either side.
> In several cases, this text differs substantially from the
> "proposed resolution" sent a few days ago, due to the fervent
> responses triggered by that message.
> 
> Diffs are available at
> http://tools.ietf.org/rfcdiff?url2=draft-ietf-isms-radius-vacm-10
> 
> Please look to see whether your concerns have been addressed, and,
> more importantly, to verify that I haven't broken something in the
> course of attempting to address the comments.
> 
> In the interest of email sanity, please direct your comments and
> follow-up discussion to the isms@ietf.org mailing list.  A few minor
> issues with this revision have already been dealt with there:
>     - module name / descriptor (in)consistency - MIB review guidelines
>       vs. common sense
>     - removed REFERENCE to RFC 5592 (tmSessionID debate)
>     - a misplaced REFERENCE clause broke compilation
>     - a few non-catastrophic typos
> 
> The WG has until Friday, September 3rd, to finish this sanity check,
> so please email your comments before then.
> 
> Randy
> 
> _______________________________________________
> MIB-DOCTORS mailing list
> MIB-DOCTORS@ietf.org
> https://www.ietf.org/mailman/listinfo/mib-doctors


From glenn@cysols.com  Thu Sep  2 09:22:07 2010
Return-Path: <glenn@cysols.com>
X-Original-To: isms@core3.amsl.com
Delivered-To: isms@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3AE763A6926; Thu,  2 Sep 2010 09:22:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.182
X-Spam-Level: 
X-Spam-Status: No, score=0.182 tagged_above=-999 required=5 tests=[AWL=0.272,  BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q7VML7dPhIZ9; Thu,  2 Sep 2010 09:22:05 -0700 (PDT)
Received: from niseko.cysol.co.jp (niseko.cysol.co.jp [210.233.3.236]) by core3.amsl.com (Postfix) with ESMTP id 3C1E23A6816; Thu,  2 Sep 2010 09:22:04 -0700 (PDT)
Received: from [127.0.0.1] (cysvpn03.priv.cysol.co.jp [192.168.0.90]) (authenticated bits=0) by aso.priv.cysol.co.jp (8.14.4/8.14.4) with ESMTP id o82GME4c029344 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Fri, 3 Sep 2010 01:22:20 +0900 (JST) (envelope-from glenn@cysols.com)
Message-ID: <4C7FCF34.2000004@cysols.com>
Date: Fri, 03 Sep 2010 01:22:12 +0900
From: "Glenn M. Keeni" <glenn@cysols.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2
MIME-Version: 1.0
To: isms@ietf.org, Glenn Mansfield Keeni <glenn@cysol.co.jp>
References: <4C527775.3000007@ieca.com>	<EDC652A26FB23C4EB6384A4584434A04023D1D0D@307622ANEX5.global.avaya.com>	<4C65D27F.30006@ieca.com><20100816132904.GA75407@elstar.local>	<4C69411E.8050907@cysols.com>	<EDC652A26FB23C4EB6384A4584434A040246CA42@307622ANEX5.global.avaya.com>	<4C694E1C.5070804@cysols.com> <EDC652A26FB23C4EB6384A4584434A040246CA75@307622ANEX5.global.avaya.com> <4C727773.5060703@cysols.com>
In-Reply-To: <4C727773.5060703@cysols.com>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
Cc: ietfmibs@ietf.org
Subject: [Isms] MIB Doctor Review: draft-ietf-isms-radius-vacm-10..txt Part-I
X-BeenThere: isms@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mailing list for the ISMS working group <isms.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isms>
List-Post: <mailto:isms@ietf.org>
List-Help: <mailto:isms-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Sep 2010 16:22:07 -0000

Hi,
  The following is a review of the revised document
    draft-ietf-isms-radius-vacm-10.txt.
I am happy to note that the document is looking much better,
most of the concerns raised in the review of -09.txt
have been addressed. Thanks. I will summarize the status below.

Cheers, Glenn

+------------------------------------------------------------+

1. I-D Boilerplate -- OK.
2. Abstract        -- OK.
==> Fixed.
3. MIB Boilerplate -- OK.
4. Security Considerations Section -- OK.
==> The actual vulnerabilities are not spelled out.
5. IANA Considerations Section     -- OK.
6. References                      -- OK.
6.1 RFC 5590 added
==> Fixed.
6.2 A reference to AAA service architecture/Framework will be
    in order if this document does target generic AAA services
   (as the title suggests).
==> There does not seem to be a  definitive reference which can
    be cited. AAA-DOCTORS advised that this is not an
    "important enough issue that changes to the document are
     required".
7. Copyright notices -- OK.
8. IPR notices -- OK.
9. Other Issues:
  a. in Section 3, "Conventions", please add "NOT RECOMMENDED" to
==> Fixed.
10.Technical content -- review of actual technical content for
   compliance with rfc4181
10.1  MIB compilation using smilint -- NOK.
   The REFERENCE clause for vacmAaaSecurityToGroupEntry should precede
   the INDEX clause. A fix is required on Page 11
==> TBD
10.2  MIB issues
10.2.1 In the MODULE-IDENTITY
|         REVISION "201007150000Z"
|         DESCRIPTION "Initial version, published as RFC XXXX."
|          ::= { mib-2 XXX }
      the note to the RFC-Editor to handle the literal XXX is
      missing.
==> Fixed.

10.2.2 the naming of the objects:
       consider the usage of the naming convention recommended in
       RFC 4181.
==> Fixed.
10.2.3 In the DESCRIPTION vacmAaaSecurityToGroupEntry row object.
      There is a need to mention the conditions under which the row is
      created.
      According to RFC 4181
       "If the agent itself may also create and/or delete rows, then the
        conditions under which this can occur MUST be clearly documented
        in the row object DESCRIPTION clause."

      The details are present in Section 7. Relevant parts must appear
      in the DESCRIPTION clause of this object.
==> Unresolved.
10.2.4 The term "AAA binding" appears for the first time here.
==> Fixed
10.2.5 The term "Security Name" is used
==> Fixed (securityName is used and Reference is added)
10.2.6  the object tmSessionID appears in this DESCRIPTION clause for
     the first time in this memo.
     Please add a REFERENCE clause citing the appropriate section
     in RFC 5590. E.g.
==> Fixed.
10.3  Document issues
==> The concerns raised on consistent terminology have been addressed.










On 2010/08/23 22:28, Glenn M. Keeni wrote:
> Hi,
> I have volunteered to do a MIB Doctor review of
> <draft-ietf-isms-radius-vacm-09.txt>. I have completed Part-I
> the more-or-less mechanical checklist aspects. I will work on
> and send a Part-II of comments on the remaining aspects of the
> memo.
> 
> The document is well written and has gone through several
> revisions. I appreciate the compactness of the MIB.
> 
> The comments below follow the checklist from Appendix A of
> rfc4181.txt. Please send comments/responses to the isms
> mailing list with cc to me and ietfmibs@ietf.org.
> 
> Glenn
> 
> +--------------------------------------------------------------+
> 
> 1. I-D Boilerplate -- OK.
> 2. Abstract        -- OK.
>     Please move the "Comments are solicited ... org" part to
>     Status of this Memo section or any other more appropriate
>     place.
> 3. MIB Boilerplate -- OK.
>     Body of the boilerplate is verbatim.
>     References are not not exact copies.
>     For RFC2578, RFC2579, there is an additional "Ed.," for
>     each author which is not there in the boilerplate. But
>     this is not a problem. It accurately reflects the actual
>     RFCs.
> 4. Security Considerations Section -- OK.
>     The Sensitive objects are listed but the risk/vulnerability
>     is not mentioned.
>     I would recommend adding something like
>       These objects may reveal that User X has logged on with
>          Security privileges Y in session Z .
>          This raises atleast two issues.
>          o Revealing the information may amount to breaching the
>            privacy of the User.
>          o The information may be misused by an attacker. E.g.
>            he/she may focus/narrow down his/her attack by making
>            informed guesses about the target system.
> 5. IANA Considerations Section     -- OK.
> 6. References                      -- NOK.
> 6.1 RFC 5590 to be added
> |      vacmAaaSessionID OBJECT-TYPE
> |          SYNTAX       Unsigned32
> |          MAX-ACCESS   not-accessible
> |          STATUS       current
> |          DESCRIPTION "A specific identifier of the session.
> |
> |                       This value MUST be unique among all currently open
> |                       sessions of all of this SNMP engine's transport
> models.
> |                       The value has no particular significance other
> than to
> |                       distinguish sessions.  Implementations in which
> |                       tmSessionID is unique across all transport
> models MAY
> |                       use the tmSessionID value."
> |          ::= { vacmAaaSecurityToGroupEntry 3 }
> 
>     A reference to RFC 5590 where the object "tmSessionID" is
>     probably defined, is required.
>     [I note that the reference was there in the earlier versions
>      of this memo but then it got removed along with "tmStateReference"
>         http://www.ietf.org/mail-archive/web/isms/current/msg04177.html]
>     Please put it back. Also, please note that this will be a
>     normative reference.
> 
> 6.2 A reference to AAA service architecture/Framework will be
>      in order if this document does target generic AAA services
>     (as the title suggests).
> 
> 7. Copyright notices -- OK.
>     Not in accordance with rfc3978 as reqd by rfc4181 but follows
>     the latest requirements as in
>     http://www.ietf.org/ietf-ftp/1id-guidelines.txt.
> 8. IPR notices -- OK.
>     Not in accordance with rfc3978 as reqd by rfc4181 but follows
>     the latest requirements as in
>     http://www.ietf.org/ietf-ftp/1id-guidelines.txt.
> 9. Other Issues:
>    a. in Section 3, "Conventions", please add "NOT RECOMMENDED" to
>       the list of imperatives (although the standard boilerplate in
>       RFC 2119 does not include it, it is used in the Security
>       Considerations section and it is defined in RFC 2119).
> 
> 10.Technical content -- review of actual technical content for
>     compliance with rfc4181
> 10.1  MIB compilation using smilint -- OK.
> 
> 10.2  MIB issues
> 10.2.1 In the MODULE-IDENTITY
> |         REVISION "201007150000Z"
> |         DESCRIPTION "Initial version, published as RFC XXXX."
> |          ::= { mib-2 XXX }
>        the note to the RFC-Editor to handle the literal XXX is
>        missing. I suggest-
> OLD:
> |         REVISION "201007150000Z"
> |         DESCRIPTION "Initial version, published as RFC XXXX."
> |          ::= { mib-2 XXX }
> NEW:
> |         REVISION "201007150000Z"
> |         DESCRIPTION "Initial version, published as RFC XXXX."
> |          ::= { mib-2 XXX }
> |         -- RFC Ed.: replace XXX with IANA-assigned number&  remove
> this note
> 
> 10.2.2 the naming of the objects:
>         In the MIB module the naming hierarchy uses the following
>         prefixes
>         snmpVacmAaaMIB
>         |
>         +-- vacmAaaMIBObjects
>         |
>         +-- vacmAaaMIBCompliance
> 
>         This does not follow the recommended naming conventions
>         given in Appendix C of RFC 4181 which urges the pattern
> 
>         snmpVacmAaaMIB
>         |
>         +-- snmpVacmAaaMIBObjects
>         |
>         +-- snmpVacmAaaMIBCompliance
> 
>         Please note, I have not found any opinions strong or weak
>         about the naming in the ISMS-WG mailing list archives.
>         [I have not looked at the archives in detail]
>         If the naming in the document is the result of deliberations
>         in the WG, please ignore this comment. Otherwise, please
>         consider the usage of the naming convention recommended in
>         RFC 4181.
> 
> 10.2.3 In the DESCRIPTION vacmAaaSecurityToGroupEntry row object.
> |     vacmAaaSecurityToGroupEntry OBJECT-TYPE
> |         SYNTAX       VacmAaaSecurityToGroupEntry
> |         MAX-ACCESS   not-accessible
> |         STATUS       current
> |         DESCRIPTION "An entry in this table maps the combination of a
> |                      SnmpSecurityModel and SecurityName into a
> GroupName for
> |                      a particular session.
> |
> |                      Each entry corresponds to a session.
> |
> |                      Entries do not persist across reboots.
> |
> |                      When a session is torn down, disconnected, timed out
> |                      (e.g. following the RADIUS Session-Timeout
> Attribute),
> |                      or otherwise terminated for any reason, the
> |                      corresponding vacmAaaSecurityToGroupEntry is
> deleted."
> 
>        There is a need to mention the conditions under which the row is
>        created.
>        According to RFC 4181
>         "If the agent itself may also create and/or delete rows, then the
>          conditions under which this can occur MUST be clearly documented
>          in the row object DESCRIPTION clause."
> 
>        The details are present in Section 7.2.1. Please add the relevant
>        part to the DESCRIPTION clause of this object. (That includes the
>        row update protocol.)
> 
>        It will be useful to have the term "AAA binding" mentioned here
>        (see 10.2.4, 10.2.5 below).  E.g.
> OLD:
> |         DESCRIPTION "An entry in this table maps the combination of a
> NEW:
> |         DESCRIPTION "An entry in this table represents a AAA binding
> |                      which maps the combination of a
> 
>        The terms "SnmpSecurityModel" and "SecurityName" are confusing as
>        they represent TEXTUAL CONVENTIONS which in turn represent the
>        SYNTAX and to some extent the semantics of objects. These are not
>        objects.
>        I recommend using "Security Model" and "Security Name". These terms
>        are used (not defined) in subsequent object DESCRIPTIONS.
> 
> 10.2.4
> |     vacmAaaSecurityModel OBJECT-TYPE
> |         SYNTAX       SnmpSecurityModel(1..2147483647)
> |         MAX-ACCESS   not-accessible
> |         STATUS       current
> |         DESCRIPTION "The Security Model associated with the AAA binding
> |                      represented by this entry.
> |
> |                      This object cannot take the 'any' (0) value."
> |         ::= { vacmAaaSecurityToGroupEntry 1 }
> 
>       The term "AAA binding" appears for the first time here.
>       (And in subsequent Object DESCRIPTIONs.). This term needs
>       to be defined.
>       [This will be remedied if the recommendation in 10.2.3 is
>        implemented.]
> 
>       The term "Security Model" appears for the first time here.
>       Presumably it is the term defined in RFC3411.
>       A REFERENCE clause would be appropriate here. E.g.
> OLD:
> |     vacmAaaSecurityModel OBJECT-TYPE
> |         SYNTAX       SnmpSecurityModel(1..2147483647)
> |         MAX-ACCESS   not-accessible
> |         STATUS       current
> |         DESCRIPTION "The Security Model associated with the AAA binding
> |                      represented by this entry.
> |
> |                      This object cannot take the 'any' (0) value."
> |         ::= { vacmAaaSecurityToGroupEntry 1 }
> NEW:
> |     vacmAaaSecurityModel OBJECT-TYPE
> |         SYNTAX       SnmpSecurityModel(1..2147483647)
> |         MAX-ACCESS   not-accessible
> |         STATUS       current
> |         DESCRIPTION "The Security Model associated with the AAA binding
> |                      represented by this entry.
> |
> |                      This object cannot take the 'any' (0) value."
> |         REFERENCE   "RFC 3411; Section 3.1.1.4.1"
> |         ::= { vacmAaaSecurityToGroupEntry 1 }
> 
> 10.2.5
> |         vacmAaaSecurityName OBJECT-TYPE
> |         SYNTAX       SnmpAdminString (SIZE(1..32))
> |         MAX-ACCESS   not-accessible
> |         STATUS       current
> |         DESCRIPTION "The Security Name of the principal associated
> with the
> |                      AAA binding represented by this entry.  In RADIUS
> |                      environments, this corresponds to the User-Name
> |                      Attribute."
> |         ::= { vacmAaaSecurityToGroupEntry 2 }
> 
>       The term "AAA binding" appears for the first time here.
>       A clear description of this term should be given.
>       [This will be remedied if the recommendation in 10.2.3 is
>        implemented.]
> 
>       The term "Security Name" is used here. It is first used in
>       Section 7.1 in the context "SNMP Security Name [RFC3411]".
>       RFC 3411 does NOT have the term Security Name. It has a
>       "securityName" object, though. In this memo there is no
>       other reference to "Security Name".
> 
>       The DESCRIPTION says "In RADIUS environments, this corresponds
>       to the User-Name Attribute."
>       To me it appears that in the AAA/RADIUS context this is the
>       "User-Name" (RFC 2865 section 5.1) and in VACM context it is
>       "securityName" (RFC 3411 section 3.2.2).
> 
>       Please
>            o fix the DESCRIPTION;
>            o add a REFERENCE clause citing the appropriate
>              document(s).
> 
> 10.2.6
> |      vacmAaaSessionID OBJECT-TYPE
> |          SYNTAX       Unsigned32
> |          MAX-ACCESS   not-accessible
> |          STATUS       current
> |          DESCRIPTION "A specific identifier of the session.
> |
> |                       This value MUST be unique among all currently open
> |                       sessions of all of this SNMP engine's transport
> models.
> |                       The value has no particular significance other
> than to
> |                       distinguish sessions.  Implementations in which
> |                       tmSessionID is unique across all transport
> models MAY
> |                       use the tmSessionID value."
> |          ::= { vacmAaaSecurityToGroupEntry 3 }
>       the object tmSessionID appears in this DESCRIPTION clause for
>       the first time in this memo. Presumably this refers to the
>       tmSessionID object in RFC 5590.
>       Please add a REFERENCE clause citing the appropriate section
>       in RFC 5590. E.g.
> OLD:
> |     vacmAaaSessionID OBJECT-TYPE
> |         SYNTAX       Unsigned32
> |         MAX-ACCESS   not-accessible
> |         STATUS       current
> |         DESCRIPTION "A specific identifier of the session.
> |
> |                      This value MUST be unique among all currently open
> |                      sessions of all of this SNMP engine's transport
> models.
> |                      The value has no particular significance other
> than to
> |                      distinguish sessions.  Implementations in which
> |                      tmSessionID is unique across all transport models MAY
> |                      use the tmSessionID value."
> |         ::= { vacmAaaSecurityToGroupEntry 3 }
> NEW:
> |     vacmAaaSessionID OBJECT-TYPE
> |         SYNTAX       Unsigned32
> |         MAX-ACCESS   not-accessible
> |         STATUS       current
> |         DESCRIPTION "A specific identifier of the session.
> |
> |                      This value MUST be unique among all currently open
> |                      sessions of all of this SNMP engine's transport
> models.
> |                      The value has no particular significance other
> than to
> |                      distinguish sessions.  Implementations in which
> |                      tmSessionID is unique across all transport models MAY
> |                      use the tmSessionID value."
> |         REFERENCE   "RFC 5590: Section 4.1.2"
> |         ::= { vacmAaaSecurityToGroupEntry 3 }
> 
> 
> 
> 10.3  Document issues
>        TBD
> 
> 
> 


From randy_presuhn@mindspring.com  Fri Sep  3 17:11:16 2010
Return-Path: <randy_presuhn@mindspring.com>
X-Original-To: isms@core3.amsl.com
Delivered-To: isms@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B31D33A69B3; Fri,  3 Sep 2010 17:10:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.392
X-Spam-Level: 
X-Spam-Status: No, score=-101.392 tagged_above=-999 required=5 tests=[AWL=-1.207, BAYES_40=-0.185, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4RTh2Zhn+xBf; Fri,  3 Sep 2010 17:10:10 -0700 (PDT)
Received: from elasmtp-curtail.atl.sa.earthlink.net (elasmtp-curtail.atl.sa.earthlink.net [209.86.89.64]) by core3.amsl.com (Postfix) with ESMTP id DD3A53A672F; Fri,  3 Sep 2010 17:10:09 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=rFSIjaxidDIxVbk5pAnZ+ecGuFyR3v7QV7lpjrB3qdEcnzFs9RlGYXYb8FpJ92nu; h=Received:Message-ID:From:To:Cc:References:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:X-MimeOLE:X-ELNK-Trace:X-Originating-IP;
Received: from [99.23.160.14] (helo=oemcomputer) by elasmtp-curtail.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <randy_presuhn@mindspring.com>) id 1OrgL8-0002ea-DA; Fri, 03 Sep 2010 20:10:38 -0400
Message-ID: <000401cb4bc5$a65acc40$6801a8c0@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: "Glenn M. Keeni" <glenn@cysols.com>, <isms@ietf.org>, "Glenn Mansfield Keeni" <glenn@cysol.co.jp>
References: <4C527775.3000007@ieca.com>	<EDC652A26FB23C4EB6384A4584434A04023D1D0D@307622ANEX5.global.avaya.com>	<4C65D27F.30006@ieca.com><20100816132904.GA75407@elstar.local>	<4C69411E.8050907@cysols.com>	<EDC652A26FB23C4EB6384A4584434A040246CA42@307622ANEX5.global.avaya.com>	<4C694E1C.5070804@cysols.com><EDC652A26FB23C4EB6384A4584434A040246CA75@307622ANEX5.global.avaya.com><4C727773.5060703@cysols.com> <4C7FCF34.2000004@cysols.com>
Date: Fri, 3 Sep 2010 17:10:56 -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: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d88829a3b650ee59d5fe4697025d4ede825e6b3e8cb92839a93e350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 99.23.160.14
Cc: ietfmibs@ietf.org
Subject: Re: [Isms] [IETFMIBS] MIB Doctor Review: draft-ietf-isms-radius-vacm-10..txtPart-I
X-BeenThere: isms@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mailing list for the ISMS working group <isms.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isms>
List-Post: <mailto:isms@ietf.org>
List-Help: <mailto:isms-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 04 Sep 2010 00:11:17 -0000

Hi -

> From: "Glenn M. Keeni" <glenn@cysols.com>
> To: <isms@ietf.org>; "Glenn Mansfield Keeni" <glenn@cysol.co.jp>
> Cc: <ietfmibs@ietf.org>
> Sent: Thursday, September 02, 2010 9:22 AM
> Subject: [IETFMIBS] MIB Doctor Review: draft-ietf-isms-radius-vacm-10..txtPart-I
...
> 10.2.3 In the DESCRIPTION vacmAaaSecurityToGroupEntry row object.
>       There is a need to mention the conditions under which the row is
>       created.
>       According to RFC 4181
>        "If the agent itself may also create and/or delete rows, then the
>         conditions under which this can occur MUST be clearly documented
>         in the row object DESCRIPTION clause."
> 
>       The details are present in Section 7. Relevant parts must appear
>       in the DESCRIPTION clause of this object.
> ==> Unresolved.
...

The -10 draft added the following to the DESCRIPTION
of vacmAaaSecurityToGroupEntry:


                 An entry is created whenever an indication occurs
                 that a new session has been established that would
                 not have the same index values as an existing entry.

The -09 text already clearly (I thought) described conditions for deletion.
I think the current -10 text provides what is needed, so I'd like to know
precisely what additional text is needed here. 

Randy


From glenn@cysols.com  Fri Sep  3 23:57:51 2010
Return-Path: <glenn@cysols.com>
X-Original-To: isms@core3.amsl.com
Delivered-To: isms@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 231253A6808; Fri,  3 Sep 2010 23:57:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.169
X-Spam-Level: 
X-Spam-Status: No, score=0.169 tagged_above=-999 required=5 tests=[AWL=0.259,  BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0zXtSydnJxXH; Fri,  3 Sep 2010 23:57:50 -0700 (PDT)
Received: from niseko.cysol.co.jp (niseko.cysol.co.jp [210.233.3.236]) by core3.amsl.com (Postfix) with ESMTP id D8F903A63EC; Fri,  3 Sep 2010 23:57:49 -0700 (PDT)
Received: from [127.0.0.1] (Bert.win2004.cysol.co.jp [192.168.0.198]) (authenticated bits=0) by aso.priv.cysol.co.jp (8.14.4/8.14.4) with ESMTP id o846w7aw046838 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Sat, 4 Sep 2010 15:58:10 +0900 (JST) (envelope-from glenn@cysols.com)
Message-ID: <4C81EDFD.9040207@cysols.com>
Date: Sat, 04 Sep 2010 15:58:05 +0900
From: "Glenn M. Keeni" <glenn@cysols.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2
MIME-Version: 1.0
To: Randy Presuhn <randy_presuhn@mindspring.com>
References: <4C527775.3000007@ieca.com>	<EDC652A26FB23C4EB6384A4584434A04023D1D0D@307622ANEX5.global.avaya.com>	<4C65D27F.30006@ieca.com><20100816132904.GA75407@elstar.local>	<4C69411E.8050907@cysols.com>	<EDC652A26FB23C4EB6384A4584434A040246CA42@307622ANEX5.global.avaya.com>	<4C694E1C.5070804@cysols.com><EDC652A26FB23C4EB6384A4584434A040246CA75@307622ANEX5.global.avaya.com><4C727773.5060703@cysols.com> <4C7FCF34.2000004@cysols.com> <000401cb4bc5$a65acc40$6801a8c0@oemcomputer>
In-Reply-To: <000401cb4bc5$a65acc40$6801a8c0@oemcomputer>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
Cc: ietfmibs@ietf.org, isms@ietf.org
Subject: Re: [Isms] [IETFMIBS] MIB Doctor Review: draft-ietf-isms-radius-vacm-10..txtPart-I
X-BeenThere: isms@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mailing list for the ISMS working group <isms.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isms>
List-Post: <mailto:isms@ietf.org>
List-Help: <mailto:isms-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 04 Sep 2010 06:57:51 -0000

Hi,
  I have noted that conditions for creation have been added to the
DESCRIPTION clause in the -10.draft. But, the DESCRIPTION still does
not capture the semantics of the table and the entry as is given in
Sec 7. Particularly what may be called the side-effects. To be specific-
a. When an entry is created in vacmAaaSecurityToGroupTable there are
   side-effects on vacmSecurityToGroupTable. This is specified in
   Sec 7.2.3 but does not appear in the DESCRIPTION and may be lost
   to the MIB reader/user/implementer.
b. When an entry is deleted from vacmAaaSecurityToGroupTable there
   may be side-effects on vacmSecurityToGroupTable. This is specified
   in Sec. 7.3.2 but does not appear anywhere in the DESCRIPTION.

Please add corresponding text to the DESCRIPTION.

Glenn




 2010/09/04 9:10, Randy Presuhn wrote:
> Hi -
> 
>> From: "Glenn M. Keeni"<glenn@cysols.com>
>> To:<isms@ietf.org>; "Glenn Mansfield Keeni"<glenn@cysol.co.jp>
>> Cc:<ietfmibs@ietf.org>
>> Sent: Thursday, September 02, 2010 9:22 AM
>> Subject: [IETFMIBS] MIB Doctor Review: draft-ietf-isms-radius-vacm-10..txtPart-I
> ...
>> 10.2.3 In the DESCRIPTION vacmAaaSecurityToGroupEntry row object.
>>        There is a need to mention the conditions under which the row is
>>        created.
>>        According to RFC 4181
>>         "If the agent itself may also create and/or delete rows, then the
>>          conditions under which this can occur MUST be clearly documented
>>          in the row object DESCRIPTION clause."
>>
>>        The details are present in Section 7. Relevant parts must appear
>>        in the DESCRIPTION clause of this object.
>> ==>  Unresolved.
> ...
> 
> The -10 draft added the following to the DESCRIPTION
> of vacmAaaSecurityToGroupEntry:
> 
> 
>                   An entry is created whenever an indication occurs
>                   that a new session has been established that would
>                   not have the same index values as an existing entry.
> 
> The -09 text already clearly (I thought) described conditions for deletion.
> I think the current -10 text provides what is needed, so I'd like to know
> precisely what additional text is needed here.
> 
> Randy
> 


From glenn@cysols.com  Sat Sep  4 01:22:51 2010
Return-Path: <glenn@cysols.com>
X-Original-To: isms@core3.amsl.com
Delivered-To: isms@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EFA2D3A67F6; Sat,  4 Sep 2010 01:22:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.157
X-Spam-Level: 
X-Spam-Status: No, score=0.157 tagged_above=-999 required=5 tests=[AWL=0.247,  BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XgnsSfl4zX8n; Sat,  4 Sep 2010 01:22:50 -0700 (PDT)
Received: from niseko.cysol.co.jp (niseko.cysol.co.jp [210.233.3.236]) by core3.amsl.com (Postfix) with ESMTP id 6C0123A6403; Sat,  4 Sep 2010 01:22:49 -0700 (PDT)
Received: from [127.0.0.1] (Bert.win2004.cysol.co.jp [192.168.0.198]) (authenticated bits=0) by aso.priv.cysol.co.jp (8.14.4/8.14.4) with ESMTP id o848Mova054558 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Sat, 4 Sep 2010 17:22:52 +0900 (JST) (envelope-from glenn@cysols.com)
Message-ID: <4C8201D8.1040005@cysols.com>
Date: Sat, 04 Sep 2010 17:22:48 +0900
From: "Glenn M. Keeni" <glenn@cysols.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2
MIME-Version: 1.0
To: Randy Presuhn <randy_presuhn@mindspring.com>
References: <4C527775.3000007@ieca.com>	<EDC652A26FB23C4EB6384A4584434A04023D1D0D@307622ANEX5.global.avaya.com>	<4C65D27F.30006@ieca.com><20100816132904.GA75407@elstar.local>	<4C69411E.8050907@cysols.com>	<EDC652A26FB23C4EB6384A4584434A040246CA42@307622ANEX5.global.avaya.com>	<4C694E1C.5070804@cysols.com><EDC652A26FB23C4EB6384A4584434A040246CA75@307622ANEX5.global.avaya.com><4C727773.5060703@cysols.com> <4C7FCF34.2000004@cysols.com> <000401cb4bc5$a65acc40$6801a8c0@oemcomputer>
In-Reply-To: <000401cb4bc5$a65acc40$6801a8c0@oemcomputer>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
Cc: ietfmibs@ietf.org, isms@ietf.org
Subject: [Isms] MIB Doctor Review: draft-ietf-isms-radius-vacm-10..txtPart-II
X-BeenThere: isms@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mailing list for the ISMS working group <isms.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isms>
List-Post: <mailto:isms@ietf.org>
List-Help: <mailto:isms-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 04 Sep 2010 08:22:51 -0000

Hi,
  This is the part-II of the review. With the extensive edits done by
the editor in -10.txt most of the concerns raised in the review of
-09.txt have been fixed or become irrelevant.
  There is one comment. In section 7.2.4 second paragraph

|  If a corresponding entry already exists in the
|  vacmSecurityToGroupTable, and the row's StorageType is anything other
|  than "volatile", or the RowStatus is anything other than "active",
|  then a role (group) mapping for this user (principal) has already
|  been put in place on this system, and will not be overridden.

Is that what we want to say? E.g. are we saying
   "If a corresponding entry already exists in the
    vacmSecurityToGroupTable and the RowStatus is "notReady"
    [notInService|..], then a role (group) mapping for this user
    (principal) has already been put in place on this system..." ?

To me appears that RowStatus other than active is just plain
unknown territory.
I fail to see how RowStatus other than "active" will imply
that there is a group mapping for this principal on the system.
Have I missed something?

In the subsequent (third) paragraph we have only the rationale
behind StorageType based action. There is no explanation about
the RowStatus based action.

Glenn


From j.schoenwaelder@jacobs-university.de  Sat Sep  4 04:26:09 2010
Return-Path: <j.schoenwaelder@jacobs-university.de>
X-Original-To: isms@core3.amsl.com
Delivered-To: isms@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7F8F83A680E for <isms@core3.amsl.com>; Sat,  4 Sep 2010 04:26:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.936
X-Spam-Level: 
X-Spam-Status: No, score=-101.936 tagged_above=-999 required=5 tests=[AWL=0.313, BAYES_00=-2.599, HELO_EQ_DE=0.35, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1+QSjvIrMLaR for <isms@core3.amsl.com>; Sat,  4 Sep 2010 04:26:08 -0700 (PDT)
Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) by core3.amsl.com (Postfix) with ESMTP id 08E413A680A for <isms@ietf.org>; Sat,  4 Sep 2010 04:26:08 -0700 (PDT)
Received: from localhost (demetrius1.jacobs-university.de [212.201.44.46]) by hermes.jacobs-university.de (Postfix) with ESMTP id 1BF29C0016; Sat,  4 Sep 2010 13:26:37 +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 w8cZ37QM6RKF; Sat,  4 Sep 2010 13:26:36 +0200 (CEST)
Received: from elstar.local (elstar.iuhb02.iu-bremen.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id 5A642C0002; Sat,  4 Sep 2010 13:26:36 +0200 (CEST)
Received: by elstar.local (Postfix, from userid 501) id D6315149FD84; Sat,  4 Sep 2010 13:26:12 +0200 (CEST)
Date: Sat, 4 Sep 2010 13:26:12 +0200
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: "isms@ietf.org" <isms@ietf.org>, "Glenn M. Keeni" <glenn@cysols.com>
Message-ID: <20100904112612.GA6333@elstar.local>
Mail-Followup-To: "isms@ietf.org" <isms@ietf.org>, "Glenn M. Keeni" <glenn@cysols.com>
References: <000701cb48bc$9b53c100$6801a8c0@oemcomputer> <20100831074839.GA80776@elstar.local>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20100831074839.GA80776@elstar.local>
User-Agent: Mutt/1.5.20 (2009-06-14)
Subject: Re: [Isms] Updated version of draft-ietf-isms-radius-vacm
X-BeenThere: isms@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
List-Id: Mailing list for the ISMS working group <isms.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isms>
List-Post: <mailto:isms@ietf.org>
List-Help: <mailto:isms-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 04 Sep 2010 11:26:09 -0000

On Tue, Aug 31, 2010 at 09:48:39AM +0200, Juergen Schoenwaelder wrote:
 
> I like to ask people to review the changes and to send any concerns to
> this list by Friday September 3rd. In case you find any issues, please
> provide detailed editing instructions. Note that we are only closing
> the issues that were raised during the IESG process and silence will
> be read as agreement with the edits made by Randy.

Thanks for all the reviews. We will only look at the issues that have
been brought up and that meet the above mentioned conditions.

/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 randy_presuhn@mindspring.com  Sat Sep  4 10:31:14 2010
Return-Path: <randy_presuhn@mindspring.com>
X-Original-To: isms@core3.amsl.com
Delivered-To: isms@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 755473A6873; Sat,  4 Sep 2010 10:31:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.392
X-Spam-Level: 
X-Spam-Status: No, score=-101.392 tagged_above=-999 required=5 tests=[AWL=-1.207, BAYES_40=-0.185, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7kizN1OXPsoi; Sat,  4 Sep 2010 10:31:12 -0700 (PDT)
Received: from elasmtp-junco.atl.sa.earthlink.net (elasmtp-junco.atl.sa.earthlink.net [209.86.89.63]) by core3.amsl.com (Postfix) with ESMTP id 655A23A6825; Sat,  4 Sep 2010 10:31:12 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=MihgFIOh1umvflHwWYW09M9WvzPi8euU5+UIemAErecMp3DMemOCGb3bFd+LKZS1; h=Received:Message-ID:From:To:Cc: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.30.227.177] (helo=oemcomputer) by elasmtp-junco.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <randy_presuhn@mindspring.com>) id 1OrwaV-0005gh-M9; Sat, 04 Sep 2010 13:31:36 -0400
Message-ID: <001e01cb4c57$1203dd60$6801a8c0@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: "Glenn M. Keeni" <glenn@cysols.com>
References: <4C820A04.7080803@cysols.com> <20100904091026.GB6146@elstar.local><4C8224EE.1070904@cysols.com> <20100904112949.GA6397@elstar.local><4C825D15.9000908@cysols.com> <20100904154546.GC6889@elstar.local>
Date: Sat, 4 Sep 2010 10:31:53 -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: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d88829a3b650ee59d5fe54d8626599a772b8d92f25c02c84fecf350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 99.30.227.177
Cc: ietfmibs@ietf.org, isms@ietf.org
Subject: Re: [Isms] [IETFMIBS] Objects and side-effects
X-BeenThere: isms@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mailing list for the ISMS working group <isms.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isms>
List-Post: <mailto:isms@ietf.org>
List-Help: <mailto:isms-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 04 Sep 2010 17:31:14 -0000

Hi -

Glenn wrote
...
> > >> Now, if the table-1 update is happening automatically, (every time
> > >> a start/stop indication arrives e.g. from RADIUS) as opposed to
> > >> being carried out by an Operator/NMS, the Operator/NMS will have no
> > >> way to tell that something is not working.
> > >> This will mean that though the RADIUS system lowered the privileges
> > >> of the principal the corresponding vacmAaaSecurityToGroupEntry will
> > >> retain the old values and this error condition will not be detectable
> > >> by an NMS or by any means.
> > >> Will this be OK?
...

We worked through the possible cases at some length on the isms WG
mailing list.  Keep in mind that the aaa/vacm table reflects what's going
on in aaa-land, and the vacm tables reflect the state of the vacm configuration.
Here are the cases I think you're concerned about.

A) indication arrives, conditions are not satisfied for the creation of
     an entry in vacmAaaSecurityToGroupTable.  Nothing happens -
     whether the corresponding session gets access is not affected
     by this.  Existing VACM configuration (and the decision of other
     parts of the implementation whether to authorize the session)
     prevail.

B) indication arrives, conditions are satisfied for the creation of an
     entry in vacmAaaSecurityToGroupTable, but conditions are not
     satisfied for an update of the corresponding vacmGroupName.
     Nothing happens - existing VACM configuration prevails.

C) indication arrives, conditions are satisfied for the creation of an
     entry in vacmAaaSecurityToGroupTable, but there is no corresponding
     entry in the vacmSecurityToGroupTable, and for whatever reason the
     implementation fails to create an entry in the vacmSecurityToGroupTable.
     The only way I can see this pathological condition occuring is if an
      implementation encounters an internal logic error or runs out of memory.
      In either case, there's really not much one can reasonably expect in the
      way of recovery via a management interface.  In this case, the result
      would that an entry would exist in the vacmAaaSecurityToGroupTable,
      reflecting the state of AAA-land, and the vacmSecurityToGroupTable
      would be unmodified, reflecting the state of VACM.  The net result is
      no different from if creation of the vacmSecurityToGroupEntry had
      succeeded, and a security administrator had subsequently deleted that
      entry via SNMP.  In short, the existing VACM configuration prevails.
      We deliberately remained silent on whether the session would continue
      or be terminated - neither case would grant access where it would be
      denied by the existing specifications.

On the isms  mailing list, we discussed the possibility of defining notifications for
some of these error conditions, worked out in considerably greater detail.
We opted to *not* put these in the MIB, awaiting operational experience.
For me the most convincing arguments against the notifications are:

  (1) if creation of a vacmSecurityToGroupEntry is failing due to lack
        of memory, it's unlikely that an implementation will have the (much greater)
        memory resources needed to create, filter, and send a notification.

  (2) for some of the error conditions considered, the network-wide scaling
       properties are worrisome.  Consider the family of cases where the
       VACM policy and AAA policy are (temporarily) out-of-sync.   In a very
       actively managed/monitored network with lots of short-lived sessions
       initiated by management systems, the resulting torrent of notifications
       could have the effect of a DoS attack on the security administrator.

  (3) we don't have any operational experience suggesting that this is a problem.
        I would suggest that trouble-shooting would have to proceed exactly as
        it does now when a user does not get the access writes (s)he expects,
        since it's still the VACM tables, and only the VACM tables, that control
        MIB access rights.

Does this answer your question?

Randy


From randy_presuhn@mindspring.com  Sat Sep  4 11:23:37 2010
Return-Path: <randy_presuhn@mindspring.com>
X-Original-To: isms@core3.amsl.com
Delivered-To: isms@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BD86A3A6832; Sat,  4 Sep 2010 11:23:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.197
X-Spam-Level: 
X-Spam-Status: No, score=-102.197 tagged_above=-999 required=5 tests=[AWL=0.402, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QQ54DLD2VUD7; Sat,  4 Sep 2010 11:23:36 -0700 (PDT)
Received: from elasmtp-dupuy.atl.sa.earthlink.net (elasmtp-dupuy.atl.sa.earthlink.net [209.86.89.62]) by core3.amsl.com (Postfix) with ESMTP id 595C53A67AC; Sat,  4 Sep 2010 11:23:36 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=sMQJieoMamqJcpDIpOT4uBp3eACAmKF4Y8OUF5vqVw9L5zWYudRVPH69b1G9GT0f; h=Received:Message-ID:From:To:Cc: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.30.227.177] (helo=oemcomputer) by elasmtp-dupuy.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <randy_presuhn@mindspring.com>) id 1OrxPD-0000RQ-Tw; Sat, 04 Sep 2010 14:24:00 -0400
Message-ID: <004a01cb4c5e$64fe1100$6801a8c0@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: "Glenn M. Keeni" <glenn@cysols.com>
References: <4C527775.3000007@ieca.com>	<EDC652A26FB23C4EB6384A4584434A04023D1D0D@307622ANEX5.global.avaya.com>	<4C65D27F.30006@ieca.com><20100816132904.GA75407@elstar.local>	<4C69411E.8050907@cysols.com>	<EDC652A26FB23C4EB6384A4584434A040246CA42@307622ANEX5.global.avaya.com>	<4C694E1C.5070804@cysols.com><EDC652A26FB23C4EB6384A4584434A040246CA75@307622ANEX5.global.avaya.com><4C727773.5060703@cysols.com> <4C7FCF34.2000004@cysols.com> <000401cb4bc5$a65acc40$6801a8c0@oemcomputer> <4C8201D8.1040005@cysols.com>
Date: Sat, 4 Sep 2010 11:24:19 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1478
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1478
X-ELNK-Trace: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d88829a3b650ee59d5fe079140caa28378d5256fdf08c62ca5da350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 99.30.227.177
Cc: ietfmibs@ietf.org, isms@ietf.org
Subject: Re: [Isms] MIB Doctor Review: draft-ietf-isms-radius-vacm-10..txtPart-II
X-BeenThere: isms@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mailing list for the ISMS working group <isms.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isms>
List-Post: <mailto:isms@ietf.org>
List-Help: <mailto:isms-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 04 Sep 2010 18:23:37 -0000

Hi -

> From: "Glenn M. Keeni" <glenn@cysols.com>
> To: "Randy Presuhn" <randy_presuhn@mindspring.com>
> Cc: <isms@ietf.org>; <ietfmibs@ietf.org>
> Sent: Saturday, September 04, 2010 1:22 AM
> Subject: MIB Doctor Review: draft-ietf-isms-radius-vacm-10..txtPart-II
>
> Hi,
>   This is the part-II of the review. With the extensive edits done by
> the editor in -10.txt most of the concerns raised in the review of
> -09.txt have been fixed or become irrelevant.
>   There is one comment. In section 7.2.4 second paragraph
> 
> |  If a corresponding entry already exists in the
> |  vacmSecurityToGroupTable, and the row's StorageType is anything other
> |  than "volatile", or the RowStatus is anything other than "active",
> |  then a role (group) mapping for this user (principal) has already
> |  been put in place on this system, and will not be overridden.
> 
> Is that what we want to say? E.g. are we saying
>    "If a corresponding entry already exists in the
>     vacmSecurityToGroupTable and the RowStatus is "notReady"
>     [notInService|..], then a role (group) mapping for this user
>     (principal) has already been put in place on this system..." ?
> 
> To me appears that RowStatus other than active is just plain
> unknown territory.
> I fail to see how RowStatus other than "active" will imply
> that there is a group mapping for this principal on the system.
> Have I missed something?
> 
> In the subsequent (third) paragraph we have only the rationale
> behind StorageType based action. There is no explanation about
> the RowStatus based action.

The other possible values of the RowStatus (notInService and notReady)
suggest that the row in question is still being manipulated by
(presumably) the security administrator, and we shouldn't modify
it.  This seems obvious from the RowStatus TC, and not in need of
explanation.  If the security administrator has created, or is in the
process of creating, a group mapping, we shouldn't mess with it.

Randy


From randy_presuhn@mindspring.com  Sat Sep  4 19:02:08 2010
Return-Path: <randy_presuhn@mindspring.com>
X-Original-To: isms@core3.amsl.com
Delivered-To: isms@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0C5A33A635F; Sat,  4 Sep 2010 19:02:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.079
X-Spam-Level: 
X-Spam-Status: No, score=-102.079 tagged_above=-999 required=5 tests=[AWL=0.520, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e5Ee++Ec+389; Sat,  4 Sep 2010 19:02:07 -0700 (PDT)
Received: from elasmtp-kukur.atl.sa.earthlink.net (elasmtp-kukur.atl.sa.earthlink.net [209.86.89.65]) by core3.amsl.com (Postfix) with ESMTP id E14023A6359; Sat,  4 Sep 2010 19:02:06 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=WuM7nH4ADKhVtSPDAtOxbn+MX35jn60vteHkSbnfqm/KJvZ/I908BaF6uxjqHm8r; h=Received:Message-ID:From:To:Cc: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.55.173.81] (helo=oemcomputer) by elasmtp-kukur.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <randy_presuhn@mindspring.com>) id 1Os4Yv-0000hN-Sn; Sat, 04 Sep 2010 22:02:30 -0400
Message-ID: <001701cb4c9e$72410a80$6801a8c0@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: "Glenn M. Keeni" <glenn@cysols.com>, <ietfmibs@ietf.org>
References: <4C820A04.7080803@cysols.com>	<20100904091026.GB6146@elstar.local><4C8224EE.1070904@cysols.com>	<20100904112949.GA6397@elstar.local><4C825D15.9000908@cysols.com>	<20100904154546.GC6889@elstar.local><001e01cb4c57$1203dd60$6801a8c0@oemcomputer> <4C82F1BF.9040701@cysols.com>
Date: Sat, 4 Sep 2010 19:02: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: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d88829a3b650ee59d5fe0e6aa27507bf657d7d1d4df94fdaf3bb350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 99.55.173.81
Cc: isms@ietf.org
Subject: Re: [Isms] [IETFMIBS] Objects and side-effects
X-BeenThere: isms@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mailing list for the ISMS working group <isms.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isms>
List-Post: <mailto:isms@ietf.org>
List-Help: <mailto:isms-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 05 Sep 2010 02:02:08 -0000

Hi -

> From: "Glenn M. Keeni" <glenn@cysols.com>
> To: <ietfmibs@ietf.org>
> Sent: Saturday, September 04, 2010 6:26 PM
> Subject: Re: [IETFMIBS] Objects and side-effects
...
> The separation of the AAA-land and VACM-land in the semantics of
> vacmAaaSecurityToGroupTable is not very clear and that is where the
> problem lies. You will notice that your interpretation differs from
> Juergen's for condition C. Your interpretation is that an
> entry will exist in table-1 (vacmAaaSecurityToGroupTable) but according
> to another interpretation the entry will not be created in table-1.
> [On 2010/09/04 18:10, Juergen Schoenwaelder wrote:]
> "In general, if you create a table entry and the row
> becomes active, the whole action must have been carried out
> successfully. It does not matter whether another MIB table is involved
> or any other resource of the managed device."
> [I interpret "whole action" to denote
>    - creation of entry in table-1 vacmAaaSecurityToGroupTable and
>    - side-effects in table-2 vacmSecurityToGroupTable.]

>From the wording of Juegren's response, I believe he was talking about
general principles of row creation via SNMP (using, e.g., RowStatus),
rather than a case where we are modeling system elements, where
changes to one system element may have consequences for some other
system element, and both are visible to management.

> It gets even more tricky with updates and deletes. With the
> success/failure in carrying out the side-effects muddying the table,
> we cannot tell what an entry in vacmAaaSecurityToGroupTable and its
> columns are supposed to mean/convey. We do not know whether it
> reflects AAA-land situation or VACM-land problems.

No.  There is nothing that one can do to the VACM configuration that
can cause the information in vacmAaaSecurityToGroupTable to change.
What text in the document would lead someone to conclude otherwise?

> If we made it abundantly clear that vacmAaaSecurityToGroupTable
> reflects AAA-land, specifically, the values received from the
> "indications",

I think the current text is clear.  Where does it even suggest that
something might propagate backwards from VACM into the
vacmAaaSecurityToGroupTable?

> and clarified that side-effects in VACM-land may or
> may not have succeeded  (success in carrying out side-effects is NOT
> a MUST/REQUIRED item in the semantics of vacmAaaSecurityToGroupTable)
> then there will be less confusion/ambiguity.

If a specifications need to spell out all the things that are "NOT REQUIRED",
we will  never finish.

> I have browsed through the discussion on notifications on the mailing
> list archives. I agree with the conclusions - notifications are not a
> good engineering solution. I may have missed it, but I did not see any
> discussion on the effects potential errors in creation/update/deletion
> of vacmSecurityToGroupTable will have on the semantics/usability of the
> vacmAaaSecurityToGroupTable.
 
Because there are no such effects.  VACM says what its configuration is.
The aaaVacmSecurityToGroupTable says what's been received most recently
from AAA-land.  That's all there is to it.  To make it any more elaborate
will be counter-productive, in my opinion.

Randy


From randy_presuhn@mindspring.com  Sat Sep  4 19:13:56 2010
Return-Path: <randy_presuhn@mindspring.com>
X-Original-To: isms@core3.amsl.com
Delivered-To: isms@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A4A563A6782; Sat,  4 Sep 2010 19:13:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.166
X-Spam-Level: 
X-Spam-Status: No, score=-102.166 tagged_above=-999 required=5 tests=[AWL=0.433, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Zkpt+TEjt10Z; Sat,  4 Sep 2010 19:13:55 -0700 (PDT)
Received: from elasmtp-kukur.atl.sa.earthlink.net (elasmtp-kukur.atl.sa.earthlink.net [209.86.89.65]) by core3.amsl.com (Postfix) with ESMTP id 2B03A3A6774; Sat,  4 Sep 2010 19:13:55 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=jPfU9G8m+K9Pf7PLbOEzWcAYBMfpM14F78hi4SFk2+5rQwjCr2otieQqWiha8W/S; h=Received:Message-ID:From:To:Cc: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.55.173.81] (helo=oemcomputer) by elasmtp-kukur.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <randy_presuhn@mindspring.com>) id 1Os4kR-0006AX-W0; Sat, 04 Sep 2010 22:14:24 -0400
Message-ID: <001c01cb4ca0$1c0bba00$6801a8c0@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: "Glenn M. Keeni" <glenn@cysols.com>, <ietfmibs@ietf.org>
References: <4C527775.3000007@ieca.com>	<EDC652A26FB23C4EB6384A4584434A04023D1D0D@307622ANEX5.global.avaya.com>	<4C65D27F.30006@ieca.com><20100816132904.GA75407@elstar.local>	<4C69411E.8050907@cysols.com>	<EDC652A26FB23C4EB6384A4584434A040246CA42@307622ANEX5.global.avaya.com>	<4C694E1C.5070804@cysols.com><EDC652A26FB23C4EB6384A4584434A040246CA75@307622ANEX5.global.avaya.com><4C727773.5060703@cysols.com>	<4C7FCF34.2000004@cysols.com>	<000401cb4bc5$a65acc40$6801a8c0@oemcomputer>	<4C8201D8.1040005@cysols.com><004a01cb4c5e$64fe1100$6801a8c0@oemcomputer> <4C82F74B.20309@cysols.com>
Date: Sat, 4 Sep 2010 19:14:44 -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: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d88829a3b650ee59d5fe4d3926ada5e781c4dd57eae346a7c551350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 99.55.173.81
Cc: isms@ietf.org
Subject: Re: [Isms] [IETFMIBS] MIB DoctorReview:	draft-ietf-isms-radius-vacm-10..txtPart-II
X-BeenThere: isms@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mailing list for the ISMS working group <isms.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isms>
List-Post: <mailto:isms@ietf.org>
List-Help: <mailto:isms-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 05 Sep 2010 02:13:57 -0000

Hi -

> From: "Glenn M. Keeni" <glenn@cysols.com>
> To: <ietfmibs@ietf.org>
> Sent: Saturday, September 04, 2010 6:50 PM
> Subject: Re: [IETFMIBS] MIB DoctorReview: draft-ietf-isms-radius-vacm-10..txtPart-II
...
> But the question is
> >>     "If a corresponding entry already exists in the
> >>      vacmSecurityToGroupTable and the RowStatus is "notReady"
> >>      [notInService|..], then a role (group) mapping for this user
> >>      (principal) has already been put in place on this system..."
> is that an accurate statement?
> How/why does RowStatus other than "active" imply that there IS a group
> mapping for this principal on the system.'?

As I understand VACM, the existence of an entry in the
vacmSecurityToGroupTable is *by* *definition*
a group mapping for a principal on the system.
 
> I understand that
> a. the operator may change his/her mind and send a set RowStatus to
>    "destroy" command for the row that was in notInService and notReady.
>    So in effect the row never sees the light of the day:-)
> b. RowStatus notReady implies that the columns of the row may not
>    have sufficient information (e.g. vacmGroupName ).

Yes, but what difference does either of these points make?  VACM was very
carefully designed so that the semantics of the user/group mapping are still
well-defined even when the vacmGroupName has no referent.

Randy


From randy_presuhn@mindspring.com  Sat Sep  4 19:24:46 2010
Return-Path: <randy_presuhn@mindspring.com>
X-Original-To: isms@core3.amsl.com
Delivered-To: isms@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 191AA3A6767; Sat,  4 Sep 2010 19:24:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.228
X-Spam-Level: 
X-Spam-Status: No, score=-102.228 tagged_above=-999 required=5 tests=[AWL=0.371, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 77iQDr8TUGwt; Sat,  4 Sep 2010 19:24:45 -0700 (PDT)
Received: from elasmtp-mealy.atl.sa.earthlink.net (elasmtp-mealy.atl.sa.earthlink.net [209.86.89.69]) by core3.amsl.com (Postfix) with ESMTP id 44E763A635F; Sat,  4 Sep 2010 19:24:45 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=ZOXhABtx3SKsRKtbagObhaWxIdAjw8dtkBhKjIfqdA7QTtpVTsv8NZhGrsSX5Qdy; h=Received:Message-ID:From:To:Cc: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.55.173.81] (helo=oemcomputer) by elasmtp-mealy.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <randy_presuhn@mindspring.com>) id 1Os4uv-0003J3-82; Sat, 04 Sep 2010 22:25:13 -0400
Message-ID: <000801cb4ca1$9f0bfe00$6801a8c0@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: "Glenn M. Keeni" <glenn@cysols.com>, <ietfmibs@ietf.org>
References: <4C527775.3000007@ieca.com>	<EDC652A26FB23C4EB6384A4584434A04023D1D0D@307622ANEX5.global.avaya.com>	<4C65D27F.30006@ieca.com><20100816132904.GA75407@elstar.local>	<4C69411E.8050907@cysols.com>	<EDC652A26FB23C4EB6384A4584434A040246CA42@307622ANEX5.global.avaya.com>	<4C694E1C.5070804@cysols.com><EDC652A26FB23C4EB6384A4584434A040246CA75@307622ANEX5.global.avaya.com><4C727773.5060703@cysols.com>	<4C7FCF34.2000004@cysols.com>	<000401cb4bc5$a65acc40$6801a8c0@oemcomputer>	<4C8201D8.1040005@cysols.com><004a01cb4c5e$64fe1100$6801a8c0@oemcomputer> <4C82F74B.20309@cysols.com>
Date: Sat, 4 Sep 2010 19:25:33 -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: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d88829a3b650ee59d5feadb57b0d69904c1bd4897f9ef1f0f45e350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 99.55.173.81
Cc: isms@ietf.org
Subject: Re: [Isms] [IETFMIBS] MIB DoctorReview:	draft-ietf-isms-radius-vacm-10..txtPart-II
X-BeenThere: isms@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mailing list for the ISMS working group <isms.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isms>
List-Post: <mailto:isms@ietf.org>
List-Help: <mailto:isms-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 05 Sep 2010 02:24:46 -0000

Hi -

Perhaps it would be helpful to think through this from a different
perspective: that of avoiding surprises for the security administrator.

Consider a security administrator doing create-and-wait provisioning
of the vacmSecurityToGroupTable.  Rows will exist with various
values for RowStatus and StorageType, until things are finally as
the administrator wants them.  At that point, there will be the
StorageType -> nonVolatile and RowStatus -> active transition.  We
don't want the AAA-supplied group to override whatever the security
administrator is putting in place.

The constraints in the current draft minimize the possibility of surprises.

Randy


From randy_presuhn@mindspring.com  Sat Sep  4 22:07:29 2010
Return-Path: <randy_presuhn@mindspring.com>
X-Original-To: isms@core3.amsl.com
Delivered-To: isms@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 38B7C3A67B1; Sat,  4 Sep 2010 22:07:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.274
X-Spam-Level: 
X-Spam-Status: No, score=-102.274 tagged_above=-999 required=5 tests=[AWL=0.325, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eGlc9xZ0HTC6; Sat,  4 Sep 2010 22:07:26 -0700 (PDT)
Received: from elasmtp-junco.atl.sa.earthlink.net (elasmtp-junco.atl.sa.earthlink.net [209.86.89.63]) by core3.amsl.com (Postfix) with ESMTP id AE9DD3A677C; Sat,  4 Sep 2010 22:07:23 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=oXizgj/5RqQqzYIERMHfd/wFYs/O2ipqLJZZfQj4xD7RBEJ0U2FJ15l7B9Tiqru7; h=Received:Message-ID:From:To:Cc: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.55.173.81] (helo=oemcomputer) by elasmtp-junco.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <randy_presuhn@mindspring.com>) id 1Os7SK-0003po-Ms; Sun, 05 Sep 2010 01:07:53 -0400
Message-ID: <000401cb4cb8$560ee020$6801a8c0@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: <ietfmibs@ietf.org>
References: <4C527775.3000007@ieca.com>	<EDC652A26FB23C4EB6384A4584434A04023D1D0D@307622ANEX5.global.avaya.com>	<4C65D27F.30006@ieca.com><20100816132904.GA75407@elstar.local>	<4C69411E.8050907@cysols.com>	<EDC652A26FB23C4EB6384A4584434A040246CA42@307622ANEX5.global.avaya.com>	<4C694E1C.5070804@cysols.com><EDC652A26FB23C4EB6384A4584434A040246CA75@307622ANEX5.global.avaya.com><4C727773.5060703@cysols.com>	<4C7FCF34.2000004@cysols.com>	<000401cb4bc5$a65acc40$6801a8c0@oemcomputer>	<4C8201D8.1040005@cysols.com><004a01cb4c5e$64fe1100$6801a8c0@oemcomputer>	<4C82F74B.20309@cysols.com><000801cb4ca1$9f0bfe00$6801a8c0@oemcomputer> <4C83192E.1040201@cysols.com>
Date: Sat, 4 Sep 2010 22:08:08 -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: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d88829a3b650ee59d5fea1be13caec78c1cf8a740cfcba4beda3350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 99.55.173.81
Cc: isms@ietf.org
Subject: Re: [Isms] [IETFMIBS]MIB	DoctorReview:	draft-ietf-isms-radius-vacm-10..txtPart-II
X-BeenThere: isms@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mailing list for the ISMS working group <isms.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isms>
List-Post: <mailto:isms@ietf.org>
List-Help: <mailto:isms-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 05 Sep 2010 05:07:29 -0000

Hi -

> From: "Glenn M. Keeni" <glenn@cysols.com>
> To: <ietfmibs@ietf.org>
> Sent: Saturday, September 04, 2010 9:14 PM
> Subject: Re: [IETFMIBS]MIB DoctorReview: draft-ietf-isms-radius-vacm-10..txtPart-II
...
> The issue is the accuracy of the statement (St-1) that appears in the
> current draft in the above context.
> St-1:
>     'If a corresponding entry already exists in the
>      vacmSecurityToGroupTable and the RowStatus is anything other than
>      "active" [e.g. notReady|notInService|..], then a role (group)
>       mapping for this user (principal) has already been put in place
>       on this system...'
> 
> Q-1. Is this an accurate statement?

yes

> Q-2. Is it possible that there is an entry in vacmSecurityToGroupTable
>       with RowStatus notReady and with no value for the vacmGroupName.
>      If the answer is "no" - my understanding of the table is
>      incomplete.
>      If the answer is yes - then next question is-

yes, though the mapping is from that user to a non-existent group

> Q-3  How do we know, even in the absence of a vacmGroupName value for
>      the corresponding vacmSecurityToGroupEntry that a "role (group)
>      mapping for this user (principal) has already been put in place
>      on this system" ?
>      This is something that I am certainly missing.

RFC 3415's DESCRIPTION clause for vacmSecurityToGroupEntry says
"An entry in this table maps the combination of a securityModel and
securityName into a groupName"  If the entry exists, QED.

> Is there any pointer that will substantiate the statement (St-1)?

I don't know how to make it any clearer.

Randy


From randy_presuhn@mindspring.com  Sat Sep  4 22:18:34 2010
Return-Path: <randy_presuhn@mindspring.com>
X-Original-To: isms@core3.amsl.com
Delivered-To: isms@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1C5353A68BF; Sat,  4 Sep 2010 22:18:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.31
X-Spam-Level: 
X-Spam-Status: No, score=-102.31 tagged_above=-999 required=5 tests=[AWL=0.289, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jPqNVHpTQpF1; Sat,  4 Sep 2010 22:18:22 -0700 (PDT)
Received: from elasmtp-banded.atl.sa.earthlink.net (elasmtp-banded.atl.sa.earthlink.net [209.86.89.70]) by core3.amsl.com (Postfix) with ESMTP id C25603A68C3; Sat,  4 Sep 2010 22:18:21 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=YvVTOKKlM7mTcM1cQwDa5HtqO0j233h0BzizVL0Ho/IpaL80LLBJ7MQhQkPiiS53; h=Received:Message-ID:From:To:Cc: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.55.173.81] (helo=oemcomputer) by elasmtp-banded.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <randy_presuhn@mindspring.com>) id 1Os7cw-0003xS-DN; Sun, 05 Sep 2010 01:18:50 -0400
Message-ID: <001901cb4cb9$dfb47f00$6801a8c0@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: <ietfmibs@ietf.org>
References: <4C694E1C.5070804@cysols.com><EDC652A26FB23C4EB6384A4584434A040246CA75@307622ANEX5.global.avaya.com><4C727773.5060703@cysols.com> <4C7FCF34.2000004@cysols.com><000401cb4bc5$a65acc40$6801a8c0@oemcomputer><4C8201D8.1040005@cysols.com><004a01cb4c5e$64fe1100$6801a8c0@oemcomputer><4C82F74B.20309@cysols.com><000801cb4ca1$9f0bfe00$6801a8c0@oemcomputer><4C83192E.1040201@cysols.com> <20100905045213.GB7902@elstar.local>
Date: Sat, 4 Sep 2010 22:19:10 -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: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d88829a3b650ee59d5fe40904b33b6d1801cb022284108109ce0350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 99.55.173.81
Cc: isms@ietf.org
Subject: Re: [Isms] [IETFMIBS] MIB	DoctorReview: draft-ietf-isms-radius-vacm-10..txtPart-II
X-BeenThere: isms@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mailing list for the ISMS working group <isms.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isms>
List-Post: <mailto:isms@ietf.org>
List-Help: <mailto:isms-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 05 Sep 2010 05:18:34 -0000

Hi -

> From: "Juergen Schoenwaelder" <j.schoenwaelder@jacobs-university.de>
> To: "Glenn M. Keeni" <glenn@cysols.com>
> Cc: <ietfmibs@ietf.org>
> Sent: Saturday, September 04, 2010 9:52 PM
> Subject: Re: [IETFMIBS] MIB DoctorReview: draft-ietf-isms-radius-vacm-10..txtPart-II
...
> > St-1:
> >     'If a corresponding entry already exists in the
> >      vacmSecurityToGroupTable and the RowStatus is anything other than
> >      "active" [e.g. notReady|notInService|..], then a role (group)
> >       mapping for this user (principal) has already been put in place
> >       on this system...'
> > 
> > Q-1. Is this an accurate statement?
> > Q-2. Is it possible that there is an entry in vacmSecurityToGroupTable
> >       with RowStatus notReady and with no value for the vacmGroupName.
> 
> No.
...

I disagree.  Consider security model X, user Y:

  administrator sends a set request with a single varbind:
        vacmSecurityToGroupStatus.X.Y = createAndWait

if that requests succeeds, then
    vacmSecurityToGroupStatus will be notReady
    vacmGroupName will have no value assigned
    vacmSecurityToGroupStorageType's value is not defined

The DESCRIPTION of vacmSecurityToGroupStatus explicitly says:

                 Until instances of all corresponding columns are
                 appropriately configured, the value of the
                 corresponding instance of the vacmSecurityToGroupStatus
                 column is 'notReady'.

                 In particular, a newly created row cannot be made
                 active until a value has been set for vacmGroupName.

 Randy


From j.schoenwaelder@jacobs-university.de  Sat Sep  4 23:00:10 2010
Return-Path: <j.schoenwaelder@jacobs-university.de>
X-Original-To: isms@core3.amsl.com
Delivered-To: isms@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id ADE6F3A67DA; Sat,  4 Sep 2010 23:00:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.96
X-Spam-Level: 
X-Spam-Status: No, score=-101.96 tagged_above=-999 required=5 tests=[AWL=0.289, BAYES_00=-2.599, HELO_EQ_DE=0.35, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id t4q5SXhDfo6j; Sat,  4 Sep 2010 23:00:08 -0700 (PDT)
Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) by core3.amsl.com (Postfix) with ESMTP id 03C6C3A67EF; Sat,  4 Sep 2010 23:00:08 -0700 (PDT)
Received: from localhost (demetrius2.jacobs-university.de [212.201.44.47]) by hermes.jacobs-university.de (Postfix) with ESMTP id C81C0C000C; Sun,  5 Sep 2010 08:00:36 +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 ytyxmGnI3RQX; Sun,  5 Sep 2010 08:00:36 +0200 (CEST)
Received: from elstar.local (elstar.iuhb02.iu-bremen.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id 01418C0002; Sun,  5 Sep 2010 08:00:35 +0200 (CEST)
Received: by elstar.local (Postfix, from userid 501) id 0570014A0E65; Sun,  5 Sep 2010 08:00:11 +0200 (CEST)
Date: Sun, 5 Sep 2010 08:00:11 +0200
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: Randy Presuhn <randy_presuhn@mindspring.com>
Message-ID: <20100905060011.GA8127@elstar.local>
Mail-Followup-To: Randy Presuhn <randy_presuhn@mindspring.com>, "ietfmibs@ietf.org" <ietfmibs@ietf.org>, "isms@ietf.org" <isms@ietf.org>
References: <4C727773.5060703@cysols.com> <4C7FCF34.2000004@cysols.com> <000401cb4bc5$a65acc40$6801a8c0@oemcomputer> <4C8201D8.1040005@cysols.com> <004a01cb4c5e$64fe1100$6801a8c0@oemcomputer> <4C82F74B.20309@cysols.com> <000801cb4ca1$9f0bfe00$6801a8c0@oemcomputer> <4C83192E.1040201@cysols.com> <20100905045213.GB7902@elstar.local> <001901cb4cb9$dfb47f00$6801a8c0@oemcomputer>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <001901cb4cb9$dfb47f00$6801a8c0@oemcomputer>
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: "ietfmibs@ietf.org" <ietfmibs@ietf.org>, "isms@ietf.org" <isms@ietf.org>
Subject: Re: [Isms] [IETFMIBS] MIB	DoctorReview: draft-ietf-isms-radius-vacm-10..txtPart-II
X-BeenThere: isms@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
List-Id: Mailing list for the ISMS working group <isms.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isms>
List-Post: <mailto:isms@ietf.org>
List-Help: <mailto:isms-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 05 Sep 2010 06:00:11 -0000

On Sun, Sep 05, 2010 at 07:19:10AM +0200, Randy Presuhn wrote:
> Hi -
> 
> > From: "Juergen Schoenwaelder" <j.schoenwaelder@jacobs-university.de>
> > To: "Glenn M. Keeni" <glenn@cysols.com>
> > Cc: <ietfmibs@ietf.org>
> > Sent: Saturday, September 04, 2010 9:52 PM
> > Subject: Re: [IETFMIBS] MIB DoctorReview: draft-ietf-isms-radius-vacm-10..txtPart-II
> ...
> > > St-1:
> > >     'If a corresponding entry already exists in the
> > >      vacmSecurityToGroupTable and the RowStatus is anything other than
> > >      "active" [e.g. notReady|notInService|..], then a role (group)
> > >       mapping for this user (principal) has already been put in place
> > >       on this system...'
> > > 
> > > Q-1. Is this an accurate statement?
> > > Q-2. Is it possible that there is an entry in vacmSecurityToGroupTable
> > >       with RowStatus notReady and with no value for the vacmGroupName.
> > 
> > No.
> ...
> 
> I disagree.  Consider security model X, user Y:
> 
>   administrator sends a set request with a single varbind:
>         vacmSecurityToGroupStatus.X.Y = createAndWait
> 
> if that requests succeeds, then
>     vacmSecurityToGroupStatus will be notReady
>     vacmGroupName will have no value assigned
>     vacmSecurityToGroupStorageType's value is not defined
> 
> The DESCRIPTION of vacmSecurityToGroupStatus explicitly says:
> 
>                  Until instances of all corresponding columns are
>                  appropriately configured, the value of the
>                  corresponding instance of the vacmSecurityToGroupStatus
>                  column is 'notReady'.
> 
>                  In particular, a newly created row cannot be made
>                  active until a value has been set for vacmGroupName.

Sorry, I confused vacmGroupName with vacmSecurityName. You are
absolutely right.

/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 glenn@cysols.com  Sun Sep  5 00:58:32 2010
Return-Path: <glenn@cysols.com>
X-Original-To: isms@core3.amsl.com
Delivered-To: isms@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5FF7B3A67EF; Sun,  5 Sep 2010 00:58:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.08
X-Spam-Level: 
X-Spam-Status: No, score=0.08 tagged_above=-999 required=5 tests=[AWL=0.170, BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I4iJgNusKXJX; Sun,  5 Sep 2010 00:58:31 -0700 (PDT)
Received: from niseko.cysol.co.jp (niseko.cysol.co.jp [210.233.3.236]) by core3.amsl.com (Postfix) with ESMTP id 06F603A67D3; Sun,  5 Sep 2010 00:58:30 -0700 (PDT)
Received: from [127.0.0.1] (cysvpn03.priv.cysol.co.jp [192.168.0.90]) (authenticated bits=0) by aso.priv.cysol.co.jp (8.14.4/8.14.4) with ESMTP id o857wOe1083583 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Sun, 5 Sep 2010 16:58:30 +0900 (JST) (envelope-from glenn@cysols.com)
Message-ID: <4C834D9F.5040502@cysols.com>
Date: Sun, 05 Sep 2010 16:58:23 +0900
From: "Glenn M. Keeni" <glenn@cysols.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2
MIME-Version: 1.0
To: isms@ietf.org, "ietfmibs@ietf.org" <ietfmibs@ietf.org>
References: <4C527775.3000007@ieca.com>	<EDC652A26FB23C4EB6384A4584434A04023D1D0D@307622ANEX5.global.avaya.com>	<4C65D27F.30006@ieca.com><20100816132904.GA75407@elstar.local>	<4C69411E.8050907@cysols.com>	<EDC652A26FB23C4EB6384A4584434A040246CA42@307622ANEX5.global.avaya.com>	<4C694E1C.5070804@cysols.com><EDC652A26FB23C4EB6384A4584434A040246CA75@307622ANEX5.global.avaya.com><4C727773.5060703@cysols.com>	<4C7FCF34.2000004@cysols.com>	<000401cb4bc5$a65acc40$6801a8c0@oemcomputer>	<4C8201D8.1040005@cysols.com><004a01cb4c5e$64fe1100$6801a8c0@oemcomputer>	<4C82F74B.20309@cysols.com><000801cb4ca1$9f0bfe00$6801a8c0@oemcomputer>	<4C83192E.1040201@cysols.com> <000401cb4cb8$560ee020$6801a8c0@oemcomputer>
In-Reply-To: <000401cb4cb8$560ee020$6801a8c0@oemcomputer>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
Subject: Re: [Isms] [IETFMIBS]MIB	DoctorReview:	draft-ietf-isms-radius-vacm-10..txtPart-II
X-BeenThere: isms@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mailing list for the ISMS working group <isms.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isms>
List-Post: <mailto:isms@ietf.org>
List-Help: <mailto:isms-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 05 Sep 2010 07:58:32 -0000

On 2010/09/05 14:08, Randy Presuhn wrote:
> Hi -
> 
>> From: "Glenn M. Keeni"<glenn@cysols.com>
>> To:<ietfmibs@ietf.org>
>> Sent: Saturday, September 04, 2010 9:14 PM
>> Subject: Re: [IETFMIBS]MIB DoctorReview: draft-ietf-isms-radius-vacm-10..txtPart-II
> ...
>> The issue is the accuracy of the statement (St-1) that appears in the
>> current draft in the above context.
>> St-1:
>>      'If a corresponding entry already exists in the
>>       vacmSecurityToGroupTable and the RowStatus is anything other than
>>       "active" [e.g. notReady|notInService|..], then a role (group)
>>        mapping for this user (principal) has already been put in place
>>        on this system...'
>>
>> Q-1. Is this an accurate statement?
> 
> yes
> 
>> Q-2. Is it possible that there is an entry in vacmSecurityToGroupTable
>>        with RowStatus notReady and with no value for the vacmGroupName.
>>       If the answer is "no" - my understanding of the table is
>>       incomplete.
>>       If the answer is yes - then next question is-
> 
> yes, though the mapping is from that user to a non-existent group
> 
>> Q-3  How do we know, even in the absence of a vacmGroupName value for
>>       the corresponding vacmSecurityToGroupEntry that a "role (group)
>>       mapping for this user (principal) has already been put in place
>>       on this system" ?
>>       This is something that I am certainly missing.
> 
> RFC 3415's DESCRIPTION clause for vacmSecurityToGroupEntry says
> "An entry in this table maps the combination of a securityModel and
> securityName into a groupName"  If the entry exists, QED.
>
I see your point here. And I disagree.
You are not implying that even if there is no value assigned to
vacmGroupName there is a mapping to some groupName somewhere and
that is implied by the DESCRIPTION in RFC3415. Are you?

The DESCRIPTION in RFC3415 is clear. It maps a securityModel and
securityName into a groupName which will be carried out by the
     vacmGroupName.SecModel.SecName = GroupName
assignment for a securityModel = SecModel and securityName = SecName.
If there is no GroupName assigned then there is no mapping, not yet.
This can happen when the RowStatus is "notReady". So obviously,
the DESCRIPTION of RFC3415 does not apply to such rows. [I guess
the same will apply to all Tables.]

>> Is there any pointer that will substantiate the statement (St-1)?
> 
> I don't know how to make it any clearer.
Yes. You have made it clear - but you are stretching the DESCRIPTION
beyond the applicable scope.

Glenn

From adonati@motorola.com  Sun Sep  5 07:37:59 2010
Return-Path: <adonati@motorola.com>
X-Original-To: isms@core3.amsl.com
Delivered-To: isms@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F0FF43A6814; Sun,  5 Sep 2010 07:37:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nmH7JUtfvKII; Sun,  5 Sep 2010 07:37:57 -0700 (PDT)
Received: from mail55.messagelabs.com (mail55.messagelabs.com [216.82.241.163]) by core3.amsl.com (Postfix) with ESMTP id 780A43A680E; Sun,  5 Sep 2010 07:37:57 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: adonati@motorola.com
X-Msg-Ref: server-3.tower-55.messagelabs.com!1283697500!21887125!1
X-StarScan-Version: 6.2.4; banners=-,-,-
X-Originating-IP: [129.188.136.8]
Received: (qmail 13973 invoked from network); 5 Sep 2010 14:38:21 -0000
Received: from motgate8.mot.com (HELO motgate8.mot.com) (129.188.136.8) by server-3.tower-55.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 5 Sep 2010 14:38:21 -0000
Received: from il06exr03.mot.com (il06exr03.mot.com [129.188.137.133]) by motgate8.mot.com (8.14.3/8.14.3) with ESMTP id o85EcIYJ018469; Sun, 5 Sep 2010 07:38:20 -0700 (MST)
Received: from il06vts01.mot.com (il06vts01.mot.com [129.188.137.141]) by il06exr03.mot.com (8.13.1/Vontu) with SMTP id o85EcIQl008531; Sun, 5 Sep 2010 09:38:18 -0500 (CDT)
Received: from de01exm62.ds.mot.com (de01exm62.am.mot.com [10.176.8.107]) by il06exr03.mot.com (8.13.1/8.13.0) with ESMTP id o85EcHUa008528; Sun, 5 Sep 2010 09:38:18 -0500 (CDT)
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, 5 Sep 2010 10:37:52 -0400
Message-ID: <EC7BA21E901B1D4FADFE19D9FF8943B2056D78F7@de01exm62.ds.mot.com>
In-Reply-To: <4C834D9F.5040502@cysols.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Isms][IETFMIBS]MIB	DoctorReview:	draft-ietf-isms-radius-vacm-10..txtPart-II
Thread-Index: ActM0DmkqmPT0W/WRh67Wd+kLOJlBwANJJlw
References: <4C527775.3000007@ieca.com>	<EDC652A26FB23C4EB6384A4584434A04023D1D0D@307622ANEX5.global.avaya.com>	<4C65D27F.30006@ieca.com><20100816132904.GA75407@elstar.local>	<4C69411E.8050907@cysols.com>	<EDC652A26FB23C4EB6384A4584434A040246CA42@307622ANEX5.global.avaya.com>	<4C694E1C.5070804@cysols.com><EDC652A26FB23C4EB6384A4584434A040246CA75@307622ANEX5.global.avaya.com><4C727773.5060703@cysols.com>	<4C7FCF34.2000004@cysols.com>	<000401cb4bc5$a65acc40$6801a8c0@oemcomputer>	<4C8201D8.1040005@cysols.com><004a01cb4c5e$64fe1100$6801a8c0@oemcomputer>	<4C82F74B.20309@cysols.com><000801cb4ca1$9f0bfe00$6801a8c0@oemcomputer>	<4C83192E.1040201@cysols.com><000401cb4cb8$560ee020$6801a8c0@oemcomputer> <4C834D9F.5040502@cysols.com>
From: "Donati Andrew-MGIA0477" <adonati@motorola.com>
To: "Glenn M. Keeni" <glenn@cysols.com>, <isms@ietf.org>, <ietfmibs@ietf.org>
X-CFilter-Loop: Reflected
Subject: Re: [Isms] [IETFMIBS]MIB	DoctorReview:	draft-ietf-isms-radius-vacm-10..txtPart-II
X-BeenThere: isms@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mailing list for the ISMS working group <isms.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isms>
List-Post: <mailto:isms@ietf.org>
List-Help: <mailto:isms-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 05 Sep 2010 14:37:59 -0000

>> St-1:
>>      'If a corresponding entry already exists in the
>>       vacmSecurityToGroupTable and the RowStatus is anything other
than
>>       "active" [e.g. notReady|notInService|..], then a role (group)
>>        mapping for this user (principal) has already been put in
place
>>        on this system...'
>>
>> Q-1. Is this an accurate statement?
>=20
> yes

Will changing the wording slightly as suggested below be of any help ? =20

... then a role (group) mapping for this user (principal) is presumably
already in place
on this system...'

- Andy

-----Original Message-----
From: isms-bounces@ietf.org [mailto:isms-bounces@ietf.org] On Behalf Of
Glenn M. Keeni
Sent: Sunday, September 05, 2010 3:58 AM
To: isms@ietf.org; ietfmibs@ietf.org
Subject: Re: [Isms][IETFMIBS]MIB DoctorReview:
draft-ietf-isms-radius-vacm-10..txtPart-II

On 2010/09/05 14:08, Randy Presuhn wrote:
> Hi -
>=20
>> From: "Glenn M. Keeni"<glenn@cysols.com> To:<ietfmibs@ietf.org>
>> Sent: Saturday, September 04, 2010 9:14 PM
>> Subject: Re: [IETFMIBS]MIB DoctorReview:=20
>> draft-ietf-isms-radius-vacm-10..txtPart-II
> ...
>> The issue is the accuracy of the statement (St-1) that appears in the

>> current draft in the above context.
>> St-1:
>>      'If a corresponding entry already exists in the
>>       vacmSecurityToGroupTable and the RowStatus is anything other
than
>>       "active" [e.g. notReady|notInService|..], then a role (group)
>>        mapping for this user (principal) has already been put in
place
>>        on this system...'
>>
>> Q-1. Is this an accurate statement?
>=20
> yes
>=20
>> Q-2. Is it possible that there is an entry in
vacmSecurityToGroupTable
>>        with RowStatus notReady and with no value for the
vacmGroupName.
>>       If the answer is "no" - my understanding of the table is
>>       incomplete.
>>       If the answer is yes - then next question is-
>=20
> yes, though the mapping is from that user to a non-existent group
>=20
>> Q-3  How do we know, even in the absence of a vacmGroupName value for
>>       the corresponding vacmSecurityToGroupEntry that a "role (group)
>>       mapping for this user (principal) has already been put in place
>>       on this system" ?
>>       This is something that I am certainly missing.
>=20
> RFC 3415's DESCRIPTION clause for vacmSecurityToGroupEntry says "An=20
> entry in this table maps the combination of a securityModel and=20
> securityName into a groupName"  If the entry exists, QED.
>
I see your point here. And I disagree.
You are not implying that even if there is no value assigned to
vacmGroupName there is a mapping to some groupName somewhere and that is
implied by the DESCRIPTION in RFC3415. Are you?

The DESCRIPTION in RFC3415 is clear. It maps a securityModel and
securityName into a groupName which will be carried out by the
     vacmGroupName.SecModel.SecName =3D GroupName assignment for a
securityModel =3D SecModel and securityName =3D SecName.
If there is no GroupName assigned then there is no mapping, not yet.
This can happen when the RowStatus is "notReady". So obviously, the
DESCRIPTION of RFC3415 does not apply to such rows. [I guess the same
will apply to all Tables.]

>> Is there any pointer that will substantiate the statement (St-1)?
>=20
> I don't know how to make it any clearer.
Yes. You have made it clear - but you are stretching the DESCRIPTION
beyond the applicable scope.

Glenn
_______________________________________________
Isms mailing list
Isms@ietf.org
https://www.ietf.org/mailman/listinfo/isms

From glenn@cysols.com  Sun Sep  5 15:38:32 2010
Return-Path: <glenn@cysols.com>
X-Original-To: isms@core3.amsl.com
Delivered-To: isms@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 721B23A677E; Sun,  5 Sep 2010 15:38:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.075
X-Spam-Level: 
X-Spam-Status: No, score=0.075 tagged_above=-999 required=5 tests=[AWL=0.165,  BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yykfO3QtTdAB; Sun,  5 Sep 2010 15:38:31 -0700 (PDT)
Received: from niseko.cysol.co.jp (niseko.cysol.co.jp [210.233.3.236]) by core3.amsl.com (Postfix) with ESMTP id 61AD63A6890; Sun,  5 Sep 2010 15:38:11 -0700 (PDT)
Received: from [127.0.0.1] (cysvpn03.priv.cysol.co.jp [192.168.0.90]) (authenticated bits=0) by aso.priv.cysol.co.jp (8.14.4/8.14.4) with ESMTP id o85McLO9064555 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Mon, 6 Sep 2010 07:38:23 +0900 (JST) (envelope-from glenn@cysols.com)
Message-ID: <4C841BDB.20002@cysols.com>
Date: Mon, 06 Sep 2010 07:38:19 +0900
From: "Glenn M. Keeni" <glenn@cysols.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2
MIME-Version: 1.0
To: Donati Andrew-MGIA0477 <adonati@motorola.com>
References: <4C527775.3000007@ieca.com>	<EDC652A26FB23C4EB6384A4584434A04023D1D0D@307622ANEX5.global.avaya.com>	<4C65D27F.30006@ieca.com><20100816132904.GA75407@elstar.local>	<4C69411E.8050907@cysols.com>	<EDC652A26FB23C4EB6384A4584434A040246CA42@307622ANEX5.global.avaya.com>	<4C694E1C.5070804@cysols.com><EDC652A26FB23C4EB6384A4584434A040246CA75@307622ANEX5.global.avaya.com><4C727773.5060703@cysols.com>	<4C7FCF34.2000004@cysols.com>	<000401cb4bc5$a65acc40$6801a8c0@oemcomputer>	<4C8201D8.1040005@cysols.com><004a01cb4c5e$64fe1100$6801a8c0@oemcomputer>	<4C82F74B.20309@cysols.com><000801cb4ca1$9f0bfe00$6801a8c0@oemcomputer>	<4C83192E.1040201@cysols.com><000401cb4cb8$560ee020$6801a8c0@oemcomputer> <4C834D9F.5040502@cysols.com> <EC7BA21E901B1D4FADFE19D9FF8943B2056D78F7@de01exm62.ds.mot.com>
In-Reply-To: <EC7BA21E901B1D4FADFE19D9FF8943B2056D78F7@de01exm62.ds.mot.com>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
Cc: ietfmibs@ietf.org, isms@ietf.org
Subject: Re: [Isms] [IETFMIBS]MIB	DoctorReview:	draft-ietf-isms-radius-vacm-10..txtPart-II
X-BeenThere: isms@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mailing list for the ISMS working group <isms.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isms>
List-Post: <mailto:isms@ietf.org>
List-Help: <mailto:isms-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 05 Sep 2010 22:38:32 -0000

On 2010/09/05 23:37, Donati Andrew-MGIA0477 wrote:
>>> St-1:
>>>       'If a corresponding entry already exists in the
>>>        vacmSecurityToGroupTable and the RowStatus is anything other
> than
>>>        "active" [e.g. notReady|notInService|..], then a role (group)
>>>         mapping for this user (principal) has already been put in
> place
>>>         on this system...'
>>>
>>> Q-1. Is this an accurate statement?
>>
>> yes
> 
> Will changing the wording slightly as suggested below be of any help ?
> 
> ... then a role (group) mapping for this user (principal) is presumably
> already in place
> on this system...'
>
Yes. It does help. Thanks.

Glenn

> - Andy
> 
> -----Original Message-----
> From: isms-bounces@ietf.org [mailto:isms-bounces@ietf.org] On Behalf Of
> Glenn M. Keeni
> Sent: Sunday, September 05, 2010 3:58 AM
> To: isms@ietf.org; ietfmibs@ietf.org
> Subject: Re: [Isms][IETFMIBS]MIB DoctorReview:
> draft-ietf-isms-radius-vacm-10..txtPart-II
> 
> On 2010/09/05 14:08, Randy Presuhn wrote:
>> Hi -
>>
>>> From: "Glenn M. Keeni"<glenn@cysols.com>  To:<ietfmibs@ietf.org>
>>> Sent: Saturday, September 04, 2010 9:14 PM
>>> Subject: Re: [IETFMIBS]MIB DoctorReview:
>>> draft-ietf-isms-radius-vacm-10..txtPart-II
>> ...
>>> The issue is the accuracy of the statement (St-1) that appears in the
> 
>>> current draft in the above context.
>>> St-1:
>>>       'If a corresponding entry already exists in the
>>>        vacmSecurityToGroupTable and the RowStatus is anything other
> than
>>>        "active" [e.g. notReady|notInService|..], then a role (group)
>>>         mapping for this user (principal) has already been put in
> place
>>>         on this system...'
>>>
>>> Q-1. Is this an accurate statement?
>>
>> yes
>>
>>> Q-2. Is it possible that there is an entry in
> vacmSecurityToGroupTable
>>>         with RowStatus notReady and with no value for the
> vacmGroupName.
>>>        If the answer is "no" - my understanding of the table is
>>>        incomplete.
>>>        If the answer is yes - then next question is-
>>
>> yes, though the mapping is from that user to a non-existent group
>>
>>> Q-3  How do we know, even in the absence of a vacmGroupName value for
>>>        the corresponding vacmSecurityToGroupEntry that a "role (group)
>>>        mapping for this user (principal) has already been put in place
>>>        on this system" ?
>>>        This is something that I am certainly missing.
>>
>> RFC 3415's DESCRIPTION clause for vacmSecurityToGroupEntry says "An
>> entry in this table maps the combination of a securityModel and
>> securityName into a groupName"  If the entry exists, QED.
>>
> I see your point here. And I disagree.
> You are not implying that even if there is no value assigned to
> vacmGroupName there is a mapping to some groupName somewhere and that is
> implied by the DESCRIPTION in RFC3415. Are you?
> 
> The DESCRIPTION in RFC3415 is clear. It maps a securityModel and
> securityName into a groupName which will be carried out by the
>       vacmGroupName.SecModel.SecName = GroupName assignment for a
> securityModel = SecModel and securityName = SecName.
> If there is no GroupName assigned then there is no mapping, not yet.
> This can happen when the RowStatus is "notReady". So obviously, the
> DESCRIPTION of RFC3415 does not apply to such rows. [I guess the same
> will apply to all Tables.]
> 
>>> Is there any pointer that will substantiate the statement (St-1)?
>>
>> I don't know how to make it any clearer.
> Yes. You have made it clear - but you are stretching the DESCRIPTION
> beyond the applicable scope.
> 
> Glenn
> _______________________________________________
> Isms mailing list
> Isms@ietf.org
> https://www.ietf.org/mailman/listinfo/isms
> 


From randy_presuhn@mindspring.com  Sun Sep  5 16:24:16 2010
Return-Path: <randy_presuhn@mindspring.com>
X-Original-To: isms@core3.amsl.com
Delivered-To: isms@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0CA333A6884; Sun,  5 Sep 2010 16:24:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.949
X-Spam-Level: 
X-Spam-Status: No, score=-101.949 tagged_above=-999 required=5 tests=[AWL=0.650, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id javaPiLZ3OxY; Sun,  5 Sep 2010 16:24:15 -0700 (PDT)
Received: from elasmtp-junco.atl.sa.earthlink.net (elasmtp-junco.atl.sa.earthlink.net [209.86.89.63]) by core3.amsl.com (Postfix) with ESMTP id C51043A687C; Sun,  5 Sep 2010 16:24:14 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=cU7Bo/GxIE5VMwcJRgn3cYz2m4JDA1J2yUhx5XhJux6CEOHqFiTqFIn5TuItURAT; h=Received:Message-ID:From:To:References:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:X-MIMEOLE:X-ELNK-Trace:X-Originating-IP;
Received: from [99.23.161.110] (helo=oemcomputer) by elasmtp-junco.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <randy_presuhn@mindspring.com>) id 1OsOZm-0004gA-DW; Sun, 05 Sep 2010 19:24:43 -0400
Message-ID: <004b01cb4d51$9308ac60$6801a8c0@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: <isms@ietf.org>, <ietfmibs@ietf.org>
References: <4C527775.3000007@ieca.com>	<EDC652A26FB23C4EB6384A4584434A04023D1D0D@307622ANEX5.global.avaya.com>	<4C65D27F.30006@ieca.com><20100816132904.GA75407@elstar.local>	<4C69411E.8050907@cysols.com>	<EDC652A26FB23C4EB6384A4584434A040246CA42@307622ANEX5.global.avaya.com>	<4C694E1C.5070804@cysols.com><EDC652A26FB23C4EB6384A4584434A040246CA75@307622ANEX5.global.avaya.com><4C727773.5060703@cysols.com>	<4C7FCF34.2000004@cysols.com>	<000401cb4bc5$a65acc40$6801a8c0@oemcomputer>	<4C8201D8.1040005@cysols.com><004a01cb4c5e$64fe1100$6801a8c0@oemcomputer>	<4C82F74B.20309@cysols.com><000801cb4ca1$9f0bfe00$6801a8c0@oemcomputer>	<4C83192E.1040201@cysols.com><000401cb4cb8$560ee020$6801a8c0@oemcomputer> <4C834D9F.5040502@cysols.com>
Date: Sun, 5 Sep 2010 16:25:04 -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: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d88829a3b650ee59d5fe935df938a3db2bb39c79128de229553c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 99.23.161.110
Subject: Re: [Isms] [IETFMIBS]	MIB	DoctorReview:	draft-ietf-isms-radius-vacm-10..txtPart-II
X-BeenThere: isms@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mailing list for the ISMS working group <isms.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isms>
List-Post: <mailto:isms@ietf.org>
List-Help: <mailto:isms-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 05 Sep 2010 23:24:16 -0000

Hi -

> From: "Glenn M. Keeni" <glenn@cysols.com>
> To: <isms@ietf.org>; <ietfmibs@ietf.org>
> Sent: Sunday, September 05, 2010 12:58 AM
> Subject: Re: [IETFMIBS][Isms] MIB DoctorReview: draft-ietf-isms-radius-vacm-10..txtPart-II
...
> >> Q-3  How do we know, even in the absence of a vacmGroupName value for
> >>       the corresponding vacmSecurityToGroupEntry that a "role (group)
> >>       mapping for this user (principal) has already been put in place
> >>       on this system" ?
> >>       This is something that I am certainly missing.
> > 
> > RFC 3415's DESCRIPTION clause for vacmSecurityToGroupEntry says
> > "An entry in this table maps the combination of a securityModel and
> > securityName into a groupName"  If the entry exists, QED.
> >
> I see your point here. And I disagree.
> You are not implying that even if there is no value assigned to
> vacmGroupName there is a mapping to some groupName somewhere and
> that is implied by the DESCRIPTION in RFC3415. Are you?

Yes.  The mapping is to null (in the database sense).  That's the only way
I can make sense of the VACM elements of procedure.  The original
proposal for what became VACM was horrifically complicated by inter-table
fate sharing due to over-zealous referential integrity constraints.  We
simplified things considerably by nailing down what it meant to, for example,
reference to a non-existant group.

> The DESCRIPTION in RFC3415 is clear. It maps a securityModel and
> securityName into a groupName which will be carried out by the
>      vacmGroupName.SecModel.SecName = GroupName
> assignment for a securityModel = SecModel and securityName = SecName.
> If there is no GroupName assigned then there is no mapping, not yet.

No.  The entry represents the mapping.  If there is an entry, there is a mapping.
In this particular case, the value mapped to is (database) null, which is a guaranteed
"no match" in terms of access policy.

> This can happen when the RowStatus is "notReady". So obviously,
> the DESCRIPTION of RFC3415 does not apply to such rows. [I guess
> the same will apply to all Tables.]
> 
> >> Is there any pointer that will substantiate the statement (St-1)?
> > 
> > I don't know how to make it any clearer.
> Yes. You have made it clear - but you are stretching the DESCRIPTION
> beyond the applicable scope.

What can I say?   This conversation doesn't seem to be going anywhere,
so I think we'll need to leave it to the WG and document shepherd to resolve this.

Randy


From j.schoenwaelder@jacobs-university.de  Mon Sep  6 01:04:18 2010
Return-Path: <j.schoenwaelder@jacobs-university.de>
X-Original-To: isms@core3.amsl.com
Delivered-To: isms@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 750623A67FC; Mon,  6 Sep 2010 01:04:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.962
X-Spam-Level: 
X-Spam-Status: No, score=-101.962 tagged_above=-999 required=5 tests=[AWL=0.287, BAYES_00=-2.599, HELO_EQ_DE=0.35, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3dhZWzLZrxTF; Mon,  6 Sep 2010 01:04:17 -0700 (PDT)
Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) by core3.amsl.com (Postfix) with ESMTP id 182523A659C; Mon,  6 Sep 2010 01:04:16 -0700 (PDT)
Received: from localhost (demetrius2.jacobs-university.de [212.201.44.47]) by hermes.jacobs-university.de (Postfix) with ESMTP id 48C44C0007; Mon,  6 Sep 2010 10:04:44 +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 FSyM4baNqnwW; Mon,  6 Sep 2010 10:04:43 +0200 (CEST)
Received: from elstar.local (elstar.iuhb02.iu-bremen.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id 5D2B6C0002; Mon,  6 Sep 2010 10:04:43 +0200 (CEST)
Received: by elstar.local (Postfix, from userid 501) id 2977D14A1E51; Mon,  6 Sep 2010 10:04:20 +0200 (CEST)
Date: Mon, 6 Sep 2010 10:04:20 +0200
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: Randy Presuhn <randy_presuhn@mindspring.com>
Message-ID: <20100906080420.GB9953@elstar.local>
Mail-Followup-To: Randy Presuhn <randy_presuhn@mindspring.com>, "isms@ietf.org" <isms@ietf.org>, "ietfmibs@ietf.org" <ietfmibs@ietf.org>
References: <4C7FCF34.2000004@cysols.com> <000401cb4bc5$a65acc40$6801a8c0@oemcomputer> <4C8201D8.1040005@cysols.com> <004a01cb4c5e$64fe1100$6801a8c0@oemcomputer> <4C82F74B.20309@cysols.com> <000801cb4ca1$9f0bfe00$6801a8c0@oemcomputer> <4C83192E.1040201@cysols.com> <000401cb4cb8$560ee020$6801a8c0@oemcomputer> <4C834D9F.5040502@cysols.com> <004b01cb4d51$9308ac60$6801a8c0@oemcomputer>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <004b01cb4d51$9308ac60$6801a8c0@oemcomputer>
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: "ietfmibs@ietf.org" <ietfmibs@ietf.org>, "isms@ietf.org" <isms@ietf.org>
Subject: Re: [Isms] [IETFMIBS]		MIB	DoctorReview: draft-ietf-isms-radius-vacm-10..txtPart-II
X-BeenThere: isms@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
List-Id: Mailing list for the ISMS working group <isms.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isms>
List-Post: <mailto:isms@ietf.org>
List-Help: <mailto:isms-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Sep 2010 08:04:18 -0000

On Mon, Sep 06, 2010 at 01:25:04AM +0200, Randy Presuhn wrote:
> Hi -
> 
> > From: "Glenn M. Keeni" <glenn@cysols.com>
> > To: <isms@ietf.org>; <ietfmibs@ietf.org>
> > Sent: Sunday, September 05, 2010 12:58 AM
> > Subject: Re: [IETFMIBS][Isms] MIB DoctorReview: draft-ietf-isms-radius-vacm-10..txtPart-II
> ...
> > >> Q-3  How do we know, even in the absence of a vacmGroupName value for
> > >>       the corresponding vacmSecurityToGroupEntry that a "role (group)
> > >>       mapping for this user (principal) has already been put in place
> > >>       on this system" ?
> > >>       This is something that I am certainly missing.
> > > 
> > > RFC 3415's DESCRIPTION clause for vacmSecurityToGroupEntry says
> > > "An entry in this table maps the combination of a securityModel and
> > > securityName into a groupName"  If the entry exists, QED.
> > >
> > I see your point here. And I disagree.
> > You are not implying that even if there is no value assigned to
> > vacmGroupName there is a mapping to some groupName somewhere and
> > that is implied by the DESCRIPTION in RFC3415. Are you?
> 
> Yes.  The mapping is to null (in the database sense).  That's the only way
> I can make sense of the VACM elements of procedure.  The original
> proposal for what became VACM was horrifically complicated by inter-table
> fate sharing due to over-zealous referential integrity constraints.  We
> simplified things considerably by nailing down what it meant to, for example,
> reference to a non-existant group.

I think step 2) in section 3.2 of RFC 3415 applies in this case. The
procedure stops with a noGroupName errorIndication. My understanding
of RowStatus is that a notReady row is not yet available to be used by
the managed device. But even if an implementation looks at such rows,
as Randy pointed out, you end up with a null group name that won't
provide you meaningful access either. VACM has been designed to handle
this corner case well.

/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 randy_presuhn@mindspring.com  Tue Sep  7 11:48:13 2010
Return-Path: <randy_presuhn@mindspring.com>
X-Original-To: isms@core3.amsl.com
Delivered-To: isms@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 88E393A6A5F; Tue,  7 Sep 2010 11:48:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.855
X-Spam-Level: 
X-Spam-Status: No, score=-101.855 tagged_above=-999 required=5 tests=[AWL=0.745, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cCu6lOYMM-fN; Tue,  7 Sep 2010 11:48:05 -0700 (PDT)
Received: from elasmtp-curtail.atl.sa.earthlink.net (elasmtp-curtail.atl.sa.earthlink.net [209.86.89.64]) by core3.amsl.com (Postfix) with ESMTP id 415923A6956; Tue,  7 Sep 2010 11:48:05 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=Byspu0IXs5dQHeb3m292nbJ14O7v4bgtDgwqUMXfIFh37mxWLpbE84K8AspYztpx; 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.187.238.15] (helo=oemcomputer) by elasmtp-curtail.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <randy_presuhn@mindspring.com>) id 1Ot3Dc-000461-TZ; Tue, 07 Sep 2010 14:48:33 -0400
Message-ID: <008f01cb4ebd$56339e40$6801a8c0@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: <isms@ietf.org>, <ietfmibs@ietf.org>
References: <4C527775.3000007@ieca.com>	<EDC652A26FB23C4EB6384A4584434A04023D1D0D@307622ANEX5.global.avaya.com>	<4C65D27F.30006@ieca.com><20100816132904.GA75407@elstar.local>	<4C69411E.8050907@cysols.com>	<EDC652A26FB23C4EB6384A4584434A040246CA42@307622ANEX5.global.avaya.com>	<4C694E1C.5070804@cysols.com><EDC652A26FB23C4EB6384A4584434A040246CA75@307622ANEX5.global.avaya.com><4C727773.5060703@cysols.com>	<4C7FCF34.2000004@cysols.com>	<000401cb4bc5$a65acc40$6801a8c0@oemcomputer>	<4C8201D8.1040005@cysols.com><004a01cb4c5e$64fe1100$6801a8c0@oemcomputer>	<4C82F74B.20309@cysols.com><000801cb4ca1$9f0bfe00$6801a8c0@oemcomputer>	<4C83192E.1040201@cysols.com><000401cb4cb8$560ee020$6801a8c0@oemcomputer><4C834D9F.5040502@cysols.com> <EC7BA21E901B1D4FADFE19D9FF8943B2056D78F7@de01exm62.ds.mot.com>
Date: Tue, 7 Sep 2010 11:48:59 -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: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d88829a3b650ee59d5fe6008f0f23169c44e41799fe3ce0f0872350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 99.187.238.15
Subject: Re: [Isms] [IETFMIBS]MIB	DoctorReview:	draft-ietf-isms-radius-vacm-10..txtPart-II
X-BeenThere: isms@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mailing list for the ISMS working group <isms.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isms>
List-Post: <mailto:isms@ietf.org>
List-Help: <mailto:isms-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Sep 2010 18:48:14 -0000

Hi -

> From: "Donati Andrew-MGIA0477" <adonati@motorola.com>
> To: "Glenn M. Keeni" <glenn@cysols.com>; <isms@ietf.org>; <ietfmibs@ietf.org>
> Sent: Sunday, September 05, 2010 7:37 AM
> Subject: Re: [IETFMIBS][Isms]MIB DoctorReview: draft-ietf-isms-radius-vacm-10..txtPart-II
>
> >> St-1:
> >>      'If a corresponding entry already exists in the
> >>       vacmSecurityToGroupTable and the RowStatus is anything other
> than
> >>       "active" [e.g. notReady|notInService|..], then a role (group)
> >>        mapping for this user (principal) has already been put in
> place
> >>        on this system...'
> >>
> >> Q-1. Is this an accurate statement?
> > 
> > yes
> 
> Will changing the wording slightly as suggested below be of any help ?  
> 
> ... then a role (group) mapping for this user (principal) is presumably
> already in place
> on this system...'

Thanks for the suggestion.  Since the part of the sentence that seems to
be causing difficulty is merely explanation, rather than specification, perhaps
we should just eliminate the explanatory material.  Would this make
everyone happy?

OLD:
If a corresponding entry already exists in the
vacmSecurityToGroupTable,
and the row's StorageType is anything other than "volatile",
or the RowStatus is anything other than "active",
then a role (group) mapping for this user (principal)
has already been 
put in place on this system,
and will not be overridden.

NEW:
If a corresponding entry already exists in the
vacmSecurityToGroupTable,
and that row's StorageType is anything other than "volatile",
or its RowStatus is anything other than "active",
then that instance of vacmGroupName MUST NOT be modified.

Randy


From glenn@cysols.com  Wed Sep  8 04:00:11 2010
Return-Path: <glenn@cysols.com>
X-Original-To: isms@core3.amsl.com
Delivered-To: isms@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AF0933A6805; Wed,  8 Sep 2010 04:00:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.07
X-Spam-Level: 
X-Spam-Status: No, score=0.07 tagged_above=-999 required=5 tests=[AWL=0.160, BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Cmk8BFWwUtjK; Wed,  8 Sep 2010 04:00:10 -0700 (PDT)
Received: from niseko.cysol.co.jp (niseko.cysol.co.jp [210.233.3.236]) by core3.amsl.com (Postfix) with ESMTP id 9D6F93A6846; Wed,  8 Sep 2010 04:00:10 -0700 (PDT)
Received: from [192.168.0.218] (cookie.win2004.cysol.co.jp [192.168.0.218]) (authenticated bits=0) by aso.priv.cysol.co.jp (8.14.4/8.14.4) with ESMTP id o88AxOsi061125 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Wed, 8 Sep 2010 19:59:28 +0900 (JST) (envelope-from glenn@cysols.com)
Message-ID: <4C876C8C.7050202@cysols.com>
Date: Wed, 08 Sep 2010 19:59:24 +0900
From: "Glenn M. Keeni" <glenn@cysols.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; ja; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2
MIME-Version: 1.0
To: isms@ietf.org, ietfmibs@ietf.org
References: <4C527775.3000007@ieca.com>	<EDC652A26FB23C4EB6384A4584434A04023D1D0D@307622ANEX5.global.avaya.com>	<4C65D27F.30006@ieca.com><20100816132904.GA75407@elstar.local>	<4C69411E.8050907@cysols.com>	<EDC652A26FB23C4EB6384A4584434A040246CA42@307622ANEX5.global.avaya.com>	<4C694E1C.5070804@cysols.com><EDC652A26FB23C4EB6384A4584434A040246CA75@307622ANEX5.global.avaya.com><4C727773.5060703@cysols.com>	<4C7FCF34.2000004@cysols.com>	<000401cb4bc5$a65acc40$6801a8c0@oemcomputer>	<4C8201D8.1040005@cysols.com><004a01cb4c5e$64fe1100$6801a8c0@oemcomputer>	<4C82F74B.20309@cysols.com><000801cb4ca1$9f0bfe00$6801a8c0@oemcomputer>	<4C83192E.1040201@cysols.com><000401cb4cb8$560ee020$6801a8c0@oemcomputer><4C834D9F.5040502@cysols.com>	<EC7BA21E901B1D4FADFE19D9FF8943B2056D78F7@de01exm62.ds.mot.com> <008f01cb4ebd$56339e40$6801a8c0@oemcomputer>
In-Reply-To: <008f01cb4ebd$56339e40$6801a8c0@oemcomputer>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
Subject: Re: [Isms] [IETFMIBS]MIB	DoctorReview:	draft-ietf-isms-radius-vacm-10..txtPart-II
X-BeenThere: isms@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mailing list for the ISMS working group <isms.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isms>
List-Post: <mailto:isms@ietf.org>
List-Help: <mailto:isms-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Sep 2010 11:00:11 -0000

(2010/09/08 3:48), Randy Presuhn wrote:
> Hi -
> 
>> From: "Donati Andrew-MGIA0477"<adonati@motorola.com>
>> To: "Glenn M. Keeni"<glenn@cysols.com>;<isms@ietf.org>;<ietfmibs@ietf.org>
>> Sent: Sunday, September 05, 2010 7:37 AM
>> Subject: Re: [IETFMIBS][Isms]MIB DoctorReview: draft-ietf-isms-radius-vacm-10..txtPart-II
>>
>>>> St-1:
>>>>       'If a corresponding entry already exists in the
>>>>        vacmSecurityToGroupTable and the RowStatus is anything other
>> than
>>>>        "active" [e.g. notReady|notInService|..], then a role (group)
>>>>         mapping for this user (principal) has already been put in
>> place
>>>>         on this system...'
>>>>
>>>> Q-1. Is this an accurate statement?
>>>
>>> yes
>>
>> Will changing the wording slightly as suggested below be of any help ?
>>
>> ... then a role (group) mapping for this user (principal) is presumably
>> already in place
>> on this system...'
> 
> Thanks for the suggestion.  Since the part of the sentence that seems to
> be causing difficulty is merely explanation, rather than specification, perhaps
> we should just eliminate the explanatory material.  Would this make
> everyone happy?
> 
> OLD:
> If a corresponding entry already exists in the
> vacmSecurityToGroupTable,
> and the row's StorageType is anything other than "volatile",
> or the RowStatus is anything other than "active",
> then a role (group) mapping for this user (principal)
> has already been
> put in place on this system,
> and will not be overridden.
> 
> NEW:
> If a corresponding entry already exists in the
> vacmSecurityToGroupTable,
> and that row's StorageType is anything other than "volatile",
> or its RowStatus is anything other than "active",
> then that instance of vacmGroupName MUST NOT be modified.

Yes. This looks/sounds good. Thanks.

Glenn

From randy_presuhn@mindspring.com  Wed Sep  8 11:30:27 2010
Return-Path: <randy_presuhn@mindspring.com>
X-Original-To: isms@core3.amsl.com
Delivered-To: isms@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 44CB13A690C; Wed,  8 Sep 2010 11:30:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.09
X-Spam-Level: 
X-Spam-Status: No, score=-101.09 tagged_above=-999 required=5 tests=[AWL=-0.905, BAYES_40=-0.185, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Xu+4R03A0JCm; Wed,  8 Sep 2010 11:30:12 -0700 (PDT)
Received: from elasmtp-scoter.atl.sa.earthlink.net (elasmtp-scoter.atl.sa.earthlink.net [209.86.89.67]) by core3.amsl.com (Postfix) with ESMTP id 4D21A3A68F6; Wed,  8 Sep 2010 11:30:11 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=c44SeXclT6ig9O0DaY5NATHiv2CShKWCtR3XlWtSK3dSmjqZwpTLXV6Yb3wMSpsg; h=Received:Message-ID:From:To: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.30.226.81] (helo=oemcomputer) by elasmtp-scoter.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <randy_presuhn@mindspring.com>) id 1OtPPq-00071T-Ng; Wed, 08 Sep 2010 14:30:39 -0400
Message-ID: <00d801cb4f84$0072ec00$6801a8c0@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: <isms@ietf.org>, <mib-doctors@ietf.org>
Date: Wed, 8 Sep 2010 11:31:05 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1478
x-mimeole: Produced By Microsoft MimeOLE V6.00.2800.1478
X-ELNK-Trace: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d88829a3b650ee59d5fefdf7a983c25cd6b1d304380923d7bee2350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 99.30.226.81
Subject: [Isms] status of draft-ietf-radius-vacm-10.txt
X-BeenThere: isms@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mailing list for the ISMS working group <isms.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isms>
List-Post: <mailto:isms@ietf.org>
List-Help: <mailto:isms-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Sep 2010 18:30:27 -0000

Hi -

I think all the issues from the MIB doctor review have
been resolved except the request to add more text to
the DESCRIPTION of vacmAaaSecurityToGroupEntry.

As editor, I'm awaiting direction from the working
group on this item.  Below is my summary of where I think
the issue stands.
---------------------------------------

The current editor's copy says:

vacmAaaSecurityToGroupEntry OBJECT-TYPE
    SYNTAX       VacmAaaSecurityToGroupEntry
    MAX-ACCESS   not-accessible
    STATUS       current
    DESCRIPTION "An entry in this table maps the combination of a
                 SnmpSecurityModel and securityName into the name
                 of a VACM group defining the access control policy
                 which is to govern a particular session.

                 Each entry corresponds to a session.

                 Entries do not persist across reboots.

                 An entry is created whenever an indication occurs
                 that a new session has been established that would
                 not have the same index values as an existing entry.

                 When a session is torn down, disconnected, timed out
                 (e.g., following the RADIUS Session-Timeout Attribute),
                 or otherwise terminated for any reason, the
                 corresponding vacmAaaSecurityToGroupEntry is deleted."
    REFERENCE   "RFC 3411 section 3.2.2 defines securityName"
    INDEX       {
                  vacmAaaSecurityModel,
                  vacmAaaSecurityName,
                  vacmAaaSessionID
                }
    ::= { vacmAaaSecurityToGroupTable 1 }

The requirement from RFC 4181 cited by the reviewer is:

     - If the agent itself may also create and/or delete rows, then the
       conditions under which this can occur MUST be clearly documented
       in the row object DESCRIPTION clause.

If one were in hair-splitting mode, one might argue that the requirement
does not apply in this case for two reasons.  First, it is subordinate
to the condition "[i]f dynamic row creation and/or deletion by management
applications is supported", and this is clearly not the case here.  (I do
agree with the general notion that the DESCRIPTION of a row should
provide the conditions under which those entries come into and go out
of existence, and the current text does so.)  Secondly, the changes requested
by the reviewer are to supply information about *another* table in a
different MIB module.

The issue is that the operation of the specification which happens to
contain this MIB module also entails the creation, modification, and
deletion of entries in the vacmSecurityToGroupTable.  The mechanism
by which these changes happen is not specified, but the conditions
may be described in terms of when certain changes would happen to the
vacmAaaSecurityToGroupTable, and the changes themselves are described
in terms readily translated to a management interface.  The question, as
I see it, is whether the DESCRIPTION of vacmAaaSecurityToGroupTable
is the appropriate place to replicate the description of how the
normal operation of the AAA/VACM spec would update VACM's
vacmSecurityToGroupTable.  My own opinion is that this would be
confusing rather than enlightening, and is not required by the
guidelines.

Opinions, and more importantly, ACTUAL TEXT, would be welcome!
As far as I know, this is the only issue preventing us
from returning the document to the IESG for approval.

Randy


From glenn@cysols.com  Wed Sep  8 22:55:46 2010
Return-Path: <glenn@cysols.com>
X-Original-To: isms@core3.amsl.com
Delivered-To: isms@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 91C353A6A11; Wed,  8 Sep 2010 22:55:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.087
X-Spam-Level: 
X-Spam-Status: No, score=0.087 tagged_above=-999 required=5 tests=[AWL=0.177,  BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k8lxSlWihJlK; Wed,  8 Sep 2010 22:55:44 -0700 (PDT)
Received: from niseko.cysol.co.jp (niseko.cysol.co.jp [210.233.3.236]) by core3.amsl.com (Postfix) with ESMTP id 9E79E3A6A15; Wed,  8 Sep 2010 22:55:24 -0700 (PDT)
Received: from [192.168.0.218] (cookie.win2004.cysol.co.jp [192.168.0.218]) (authenticated bits=0) by aso.priv.cysol.co.jp (8.14.4/8.14.4) with ESMTP id o895skaC069087 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Thu, 9 Sep 2010 14:55:04 +0900 (JST) (envelope-from glenn@cysols.com)
Message-ID: <4C8876A1.7090303@cysols.com>
Date: Thu, 09 Sep 2010 14:54:41 +0900
From: "Glenn M. Keeni" <glenn@cysols.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; ja; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2
MIME-Version: 1.0
To: isms@ietf.org, ietfmibs@ietf.org
References: <00d801cb4f84$0072ec00$6801a8c0@oemcomputer>
In-Reply-To: <00d801cb4f84$0072ec00$6801a8c0@oemcomputer>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
Subject: Re: [Isms] status of draft-ietf-radius-vacm-10.txt
X-BeenThere: isms@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mailing list for the ISMS working group <isms.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isms>
List-Post: <mailto:isms@ietf.org>
List-Help: <mailto:isms-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Sep 2010 05:55:46 -0000
X-List-Received-Date: Thu, 09 Sep 2010 05:55:46 -0000

Hi,
  There are actually two issues that need to be addressed.

Issue-1:
(2010/09/04 15:58), Glenn M. Keeni wrote:
>    I have noted that conditions for creation have been added to the
> DESCRIPTION clause in the -10.draft. But, the DESCRIPTION still does
> not capture the semantics of the table and the entry as is given in
> Sec 7. Particularly what may be called the side-effects. To be
> specific-
> a. When an entry is created in vacmAaaSecurityToGroupTable there are
>     side-effects on vacmSecurityToGroupTable. This is specified in
>     Sec 7.2.3 but does not appear in the DESCRIPTION and may be lost
>     to the MIB reader/user/implementer.
> b. When an entry is deleted from vacmAaaSecurityToGroupTable there
>     may be side-effects on vacmSecurityToGroupTable. This is specified
>     in Sec. 7.3.2 but does not appear anywhere in the DESCRIPTION.
>
> Please add corresponding text to the DESCRIPTION.

I think that the general idea is that the MIB module should by itself
provide the reader with all the information about the creation/update
/deletion of objects and related side-effects, if any.

Issue-2:
In Section 7 the text says-
   On receipt of indication
      a. create/update/delete entry in vacmAaaSecurityToGroupTable
           7.2.2.  Creation of Entries in vacmAaaSecurityToGroupTable
             Whenever an indication arrives  determine whether a
             corresponding entry exists in the
             vacmAaaSecurityToGroupTable. If one does not, create a
             new row......
             Otherwise, if the row already exists, update the
             vacmAaaGroupName
      b. create/update/delete entry in vacmSecurityToGroupTable
          7.2.3.  Creation of Entries in vacmSecurityToGroupTable
            Whenever an entry is created in the
            vacmAaaSecurityToGroupTable, the vacmSecurityToGroupTable
            is examined to determine whether corresponding entry
            exists there.  If no corresponding entry
            exists, create one, using the vacmAaaGroupName of the newly
            created entry to fill in vacmGroupName......

It is clear that only if a vacmAaaSecurityToGroupEntry creation in (a)
succeeds (b) will attempted. [(b) will not be attempted if (a) fails.]
But it does not say what will be the effect if (b) fails. It appears
that there are 2 options for an implementer
      b-1. if (b) fails - rollback changes in (a)
      b-2. if (b) fails - do not rollback changes done in (a).
Is it clear from the text which option,  b-1 or b-2, should be taken
by an implementer? If it is not clear a fix is needed here.

Glenn

> Hi,
>    Please see inline.

(2010/09/09 3:31), Randy Presuhn wrote:
> Hi -
> 
> I think all the issues from the MIB doctor review have
> been resolved except the request to add more text to
> the DESCRIPTION of vacmAaaSecurityToGroupEntry.
> 
> As editor, I'm awaiting direction from the working
> group on this item.  Below is my summary of where I think
> the issue stands.
> ---------------------------------------
> 
> The current editor's copy says:
> 
> vacmAaaSecurityToGroupEntry OBJECT-TYPE
>      SYNTAX       VacmAaaSecurityToGroupEntry
>      MAX-ACCESS   not-accessible
>      STATUS       current
>      DESCRIPTION "An entry in this table maps the combination of a
>                   SnmpSecurityModel and securityName into the name
>                   of a VACM group defining the access control policy
>                   which is to govern a particular session.
> 
>                   Each entry corresponds to a session.
> 
>                   Entries do not persist across reboots.
> 
>                   An entry is created whenever an indication occurs
>                   that a new session has been established that would
>                   not have the same index values as an existing entry.
> 
>                   When a session is torn down, disconnected, timed out
>                   (e.g., following the RADIUS Session-Timeout Attribute),
>                   or otherwise terminated for any reason, the
>                   corresponding vacmAaaSecurityToGroupEntry is deleted."
>      REFERENCE   "RFC 3411 section 3.2.2 defines securityName"
>      INDEX       {
>                    vacmAaaSecurityModel,
>                    vacmAaaSecurityName,
>                    vacmAaaSessionID
>                  }
>      ::= { vacmAaaSecurityToGroupTable 1 }
> 
> The requirement from RFC 4181 cited by the reviewer is:
> 
>       - If the agent itself may also create and/or delete rows, then the
>         conditions under which this can occur MUST be clearly documented
>         in the row object DESCRIPTION clause.
> 
> If one were in hair-splitting mode, one might argue that the requirement
> does not apply in this case for two reasons.  First, it is subordinate
> to the condition "[i]f dynamic row creation and/or deletion by management
> applications is supported", and this is clearly not the case here.  (I do
> agree with the general notion that the DESCRIPTION of a row should
> provide the conditions under which those entries come into and go out
> of existence, and the current text does so.)  Secondly, the changes requested
> by the reviewer are to supply information about *another* table in a
> different MIB module.
> 
> The issue is that the operation of the specification which happens to
> contain this MIB module also entails the creation, modification, and
> deletion of entries in the vacmSecurityToGroupTable.  The mechanism
> by which these changes happen is not specified, but the conditions
> may be described in terms of when certain changes would happen to the
> vacmAaaSecurityToGroupTable, and the changes themselves are described
> in terms readily translated to a management interface.  The question, as
> I see it, is whether the DESCRIPTION of vacmAaaSecurityToGroupTable
> is the appropriate place to replicate the description of how the
> normal operation of the AAA/VACM spec would update VACM's
> vacmSecurityToGroupTable.  My own opinion is that this would be
> confusing rather than enlightening, and is not required by the
> guidelines.
> 
> Opinions, and more importantly, ACTUAL TEXT, would be welcome!
> As far as I know, this is the only issue preventing us
> from returning the document to the IESG for approval.
> 
> Randy
> 
> _______________________________________________
> Isms mailing list
> Isms@ietf.org
> https://www.ietf.org/mailman/listinfo/isms


From j.schoenwaelder@jacobs-university.de  Thu Sep  9 00:59:33 2010
Return-Path: <j.schoenwaelder@jacobs-university.de>
X-Original-To: isms@core3.amsl.com
Delivered-To: isms@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 510133A6778; Thu,  9 Sep 2010 00:59:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.973
X-Spam-Level: 
X-Spam-Status: No, score=-101.973 tagged_above=-999 required=5 tests=[AWL=0.276, BAYES_00=-2.599, HELO_EQ_DE=0.35, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pNnMzhS9jQJZ; Thu,  9 Sep 2010 00:59:31 -0700 (PDT)
Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) by core3.amsl.com (Postfix) with ESMTP id 924993A67CC; Thu,  9 Sep 2010 00:59:30 -0700 (PDT)
Received: from localhost (demetrius4.jacobs-university.de [212.201.44.49]) by hermes.jacobs-university.de (Postfix) with ESMTP id EE808C0018; Thu,  9 Sep 2010 09:59:57 +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 im2WvS9JX9Lq; Thu,  9 Sep 2010 09:59:57 +0200 (CEST)
Received: from elstar.local (elstar.iuhb02.iu-bremen.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id EC5C1C0011; Thu,  9 Sep 2010 09:59:56 +0200 (CEST)
Received: by elstar.local (Postfix, from userid 501) id 7D8E414B68AE; Thu,  9 Sep 2010 09:59:31 +0200 (CEST)
Date: Thu, 9 Sep 2010 09:59:31 +0200
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: "Glenn M. Keeni" <glenn@cysols.com>
Message-ID: <20100909075931.GA12224@elstar.local>
Mail-Followup-To: "Glenn M. Keeni" <glenn@cysols.com>, "isms@ietf.org" <isms@ietf.org>, "ietfmibs@ietf.org" <ietfmibs@ietf.org>
References: <00d801cb4f84$0072ec00$6801a8c0@oemcomputer> <4C8876A1.7090303@cysols.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4C8876A1.7090303@cysols.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: "ietfmibs@ietf.org" <ietfmibs@ietf.org>, "isms@ietf.org" <isms@ietf.org>
Subject: Re: [Isms] status of draft-ietf-radius-vacm-10.txt
X-BeenThere: isms@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
List-Id: Mailing list for the ISMS working group <isms.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isms>
List-Post: <mailto:isms@ietf.org>
List-Help: <mailto:isms-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Sep 2010 07:59:33 -0000

On Thu, Sep 09, 2010 at 07:54:41AM +0200, Glenn M. Keeni wrote:
> Hi,
>   There are actually two issues that need to be addressed.
> 
> Issue-1:
> (2010/09/04 15:58), Glenn M. Keeni wrote:
> >    I have noted that conditions for creation have been added to the
> > DESCRIPTION clause in the -10.draft. But, the DESCRIPTION still does
> > not capture the semantics of the table and the entry as is given in
> > Sec 7. Particularly what may be called the side-effects. To be
> > specific-
> > a. When an entry is created in vacmAaaSecurityToGroupTable there are
> >     side-effects on vacmSecurityToGroupTable. This is specified in
> >     Sec 7.2.3 but does not appear in the DESCRIPTION and may be lost
> >     to the MIB reader/user/implementer.
> > b. When an entry is deleted from vacmAaaSecurityToGroupTable there
> >     may be side-effects on vacmSecurityToGroupTable. This is specified
> >     in Sec. 7.3.2 but does not appear anywhere in the DESCRIPTION.
> >
> > Please add corresponding text to the DESCRIPTION.
> 
> I think that the general idea is that the MIB module should by itself
> provide the reader with all the information about the creation/update
> /deletion of objects and related side-effects, if any.

Is your proposal to cut'n'paste 7.2.3 and 7.3.2 into the DESCRIPTION
clause? Or is your proposal to add an explicit reference to the
DESCRIPTION clause to sections 7.2.3 and 7.3.2? Or is your proposal to
completely inline section 7 into the DESCRIPTION clauses of the MIB
module, causing a major rewrite?

Looking at the flow of the discussion, I believe the WG does not
really care about this change since the specification overall is
considered clear enough to implement it.

> Issue-2:
> In Section 7 the text says-
>    On receipt of indication
>       a. create/update/delete entry in vacmAaaSecurityToGroupTable
>            7.2.2.  Creation of Entries in vacmAaaSecurityToGroupTable
>              Whenever an indication arrives  determine whether a
>              corresponding entry exists in the
>              vacmAaaSecurityToGroupTable. If one does not, create a
>              new row......
>              Otherwise, if the row already exists, update the
>              vacmAaaGroupName
>       b. create/update/delete entry in vacmSecurityToGroupTable
>           7.2.3.  Creation of Entries in vacmSecurityToGroupTable
>             Whenever an entry is created in the
>             vacmAaaSecurityToGroupTable, the vacmSecurityToGroupTable
>             is examined to determine whether corresponding entry
>             exists there.  If no corresponding entry
>             exists, create one, using the vacmAaaGroupName of the newly
>             created entry to fill in vacmGroupName......
> 
> It is clear that only if a vacmAaaSecurityToGroupEntry creation in (a)
> succeeds (b) will attempted. [(b) will not be attempted if (a) fails.]
> But it does not say what will be the effect if (b) fails. It appears
> that there are 2 options for an implementer
>       b-1. if (b) fails - rollback changes in (a)
>       b-2. if (b) fails - do not rollback changes done in (a).
> Is it clear from the text which option,  b-1 or b-2, should be taken
> by an implementer? If it is not clear a fix is needed here.

Since there is no concrete text proposal and given the lack of WG
support for adding more text detailing the handling of error
situations, I believe we should close this issue with no change.  Note
that once you look at why (b) can fail in real implementations, you
likely can convince yourself that the actions to take might also be
implementation specific.

/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 dnelson@elbrys.com  Thu Sep  9 06:46:05 2010
Return-Path: <dnelson@elbrys.com>
X-Original-To: isms@core3.amsl.com
Delivered-To: isms@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 334B23A6841; Thu,  9 Sep 2010 06:46:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fI2jDUp2Ui79; Thu,  9 Sep 2010 06:46:01 -0700 (PDT)
Received: from na3sys009aog108.obsmtp.com (na3sys009aog108.obsmtp.com [74.125.149.199]) by core3.amsl.com (Postfix) with SMTP id B3DD63A686A; Thu,  9 Sep 2010 06:46:00 -0700 (PDT)
Received: from source ([209.85.210.41]) by na3sys009aob108.postini.com ([74.125.148.12]) with SMTP ID DSNKTIjlNB5acQ8osuDukupKbkMQ4W3S4Jh/@postini.com; Thu, 09 Sep 2010 06:46:28 PDT
Received: by mail-pz0-f41.google.com with SMTP id 33so579176pzk.28 for <multiple recipients>; Thu, 09 Sep 2010 06:46:28 -0700 (PDT)
Received: by 10.142.4.9 with SMTP id 9mr28026wfd.98.1284039988100; Thu, 09 Sep 2010 06:46:28 -0700 (PDT)
Received: from dbn-imac.elbrysnetworks.com (host171.elbrysnetworks.com [64.140.243.171]) by mx.google.com with ESMTPS id k6sm637264vcs.17.2010.09.09.06.46.26 (version=SSLv3 cipher=RC4-MD5); Thu, 09 Sep 2010 06:46:27 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=us-ascii
From: "David B. Nelson" <dnelson@elbrys.com>
In-Reply-To: <4C8876A1.7090303@cysols.com>
Date: Thu, 9 Sep 2010 09:46:19 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <4611B1FC-6613-4273-BABF-C7714FF17908@elbrys.com>
References: <00d801cb4f84$0072ec00$6801a8c0@oemcomputer> <4C8876A1.7090303@cysols.com>
To: "Glenn M. Keeni" <glenn@cysols.com>
X-Mailer: Apple Mail (2.1081)
Cc: ietfmibs@ietf.org, isms@ietf.org
Subject: Re: [Isms] status of draft-ietf-radius-vacm-10.txt
X-BeenThere: isms@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mailing list for the ISMS working group <isms.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isms>
List-Post: <mailto:isms@ietf.org>
List-Help: <mailto:isms-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Sep 2010 13:46:05 -0000

On Sep 9, 2010, at 1:54 AM, Glenn M. Keeni wrote:

> I think that the general idea is that the MIB module should by itself
> provide the reader with all the information about the creation/update
> /deletion of objects and related side-effects, if any.

With all due respect, this seems to relegate the normative text of the =
RFC that contains the MIB module to the status of little more than =
introductory fluff.  Sometimes there are important points that can only =
be found in the normative text, and in my opinion that's as it should =
be.  Implementers need to read all that text.  While the DESCRIPTION =
clauses should be as fully descriptive as practical, attempting to =
shoe-horn *all* the normative behavior into these clauses can in some =
cases be a mistake. I think this is one of them.

> It is clear that only if a vacmAaaSecurityToGroupEntry creation in (a)
> succeeds (b) will attempted. [(b) will not be attempted if (a) fails.]
> But it does not say what will be the effect if (b) fails. It appears
> that there are 2 options for an implementer
>      b-1. if (b) fails - rollback changes in (a)
>      b-2. if (b) fails - do not rollback changes done in (a).
> Is it clear from the text which option,  b-1 or b-2, should be taken
> by an implementer?

It doesn't matter.   Action (b) only "fails" if statically configured =
information in the local configuration data store over-rides =
AAA-provisioned information.  In that event, it matters not what happens =
to the AAA-provisioned information in (a).

> If it is not clear a fix is needed here.

With due respect, I don't think so.


From glenn@cysols.com  Thu Sep  9 22:17:37 2010
Return-Path: <glenn@cysols.com>
X-Original-To: isms@core3.amsl.com
Delivered-To: isms@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 289A43A6838; Thu,  9 Sep 2010 22:17:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.078
X-Spam-Level: 
X-Spam-Status: No, score=0.078 tagged_above=-999 required=5 tests=[AWL=0.168,  BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IutaxcHB6Ayj; Thu,  9 Sep 2010 22:17:35 -0700 (PDT)
Received: from niseko.cysol.co.jp (niseko.cysol.co.jp [210.233.3.236]) by core3.amsl.com (Postfix) with ESMTP id ED5833A6837; Thu,  9 Sep 2010 22:17:33 -0700 (PDT)
Received: from [192.168.0.218] (cookie.win2004.cysol.co.jp [192.168.0.218]) (authenticated bits=0) by aso.priv.cysol.co.jp (8.14.4/8.14.4) with ESMTP id o8A5HZAw003860 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Fri, 10 Sep 2010 14:17:38 +0900 (JST) (envelope-from glenn@cysols.com)
Message-ID: <4C89BF6A.4030706@cysols.com>
Date: Fri, 10 Sep 2010 14:17:30 +0900
From: "Glenn M. Keeni" <glenn@cysols.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; ja; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2
MIME-Version: 1.0
To: ietfmibs@ietf.org, isms@ietf.org
References: <00d801cb4f84$0072ec00$6801a8c0@oemcomputer>	<4C8876A1.7090303@cysols.com> <20100909075931.GA12224@elstar.local>
In-Reply-To: <20100909075931.GA12224@elstar.local>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
Subject: Re: [Isms] [IETFMIBS]  status of draft-ietf-radius-vacm-10.txt
X-BeenThere: isms@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mailing list for the ISMS working group <isms.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isms>
List-Post: <mailto:isms@ietf.org>
List-Help: <mailto:isms-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Sep 2010 05:17:37 -0000

(2010/09/09 16:59), Juergen Schoenwaelder wrote:
> On Thu, Sep 09, 2010 at 07:54:41AM +0200, Glenn M. Keeni wrote:
>> Hi,
>>    There are actually two issues that need to be addressed.
>>
>> Issue-1:
>> (2010/09/04 15:58), Glenn M. Keeni wrote:
>>>     I have noted that conditions for creation have been added to the
>>> DESCRIPTION clause in the -10.draft. But, the DESCRIPTION still does
>>> not capture the semantics of the table and the entry as is given in
>>> Sec 7. Particularly what may be called the side-effects. To be
>>> specific-
>>> a. When an entry is created in vacmAaaSecurityToGroupTable there are
>>>      side-effects on vacmSecurityToGroupTable. This is specified in
>>>      Sec 7.2.3 but does not appear in the DESCRIPTION and may be lost
>>>      to the MIB reader/user/implementer.
>>> b. When an entry is deleted from vacmAaaSecurityToGroupTable there
>>>      may be side-effects on vacmSecurityToGroupTable. This is specified
>>>      in Sec. 7.3.2 but does not appear anywhere in the DESCRIPTION.
>>>
>>> Please add corresponding text to the DESCRIPTION.
>>
>> I think that the general idea is that the MIB module should by itself
>> provide the reader with all the information about the creation/update
>> /deletion of objects and related side-effects, if any.
> 
> Is your proposal to cut'n'paste 7.2.3 and 7.3.2 into the DESCRIPTION
> clause? Or is your proposal to add an explicit reference to the
> DESCRIPTION clause to sections 7.2.3 and 7.3.2? Or is your proposal to
> completely inline section 7 into the DESCRIPTION clauses of the MIB
> module, causing a major rewrite?
A gist of section 7  should do. E.g.
OLD:
    DESCRIPTION "An entry in this table maps the combination of a
                 SnmpSecurityModel and securityName into a the name
                 of a VACM group defining the access control policy
                 which is to govern a particular session.

                 Each entry corresponds to a session.

                 Entries do not persist across reboots.

                 An entry is created whenever an indication occurs
                 that a new session has been established that would
                 not have the same index values as an existing entry.

                 When a session is torn down, disconnected, timed out
                 (e.g., following the RADIUS Session-Timeout Attribute),
                 or otherwise terminated for any reason, the
                 corresponding vacmAaaSecurityToGroupEntry is deleted."
NEW:
    DESCRIPTION "An entry in this table maps the combination of a
                 SnmpSecurityModel and securityName into the name
                 of a VACM group defining the access control policy
                 which is to govern a particular session.

                 Each entry corresponds to a session.

                 Entries do not persist across reboots.

                 An entry is created whenever an indication occurs
                 that a new session has been established that would
                 not have the same index values as an existing entry.

                 If an entry with the same index values exists then
                 the vacmAaaGroupName is updated.

                 Whenever an entry is created, if no corresponding entry
                 exists in the vacmSecurityToGroupTable, an entry
                 will be created in that table.

                 If a corresponding entry exists in the
                 vacmSecurityToGroupTable, and that entry's StorageType
                 is 'volatile' and its RowStatus is 'active', the value
                 of vacmGroupName in that entry will be updated with
                 the value from vacmAaaGroupName.

                 When a session is torn down, disconnected, timed out
                 (e.g., following the RADIUS Session-Timeout Attribute),
                 or otherwise terminated for any reason, the
                 corresponding vacmAaaSecurityToGroupEntry is deleted.

                 Whenever the last remaining row bearing a particular
                 (vacmAaaSecurityModel, vacmAaaSecurityName) pair is
                 deleted from the vacmAaaSecurityToGroupTable, the
                 vacmSecurityToGroupTable is examined for a
                 corresponding row. If one exists, and if its
                 StorageType is 'volatile' and its RowStatus is
                 'active', that row will be deleted as well."

> 
> Looking at the flow of the discussion, I believe the WG does not
> really care about this change since the specification overall is
> considered clear enough to implement it.
> 
>> Issue-2:
>> In Section 7 the text says-
>>     On receipt of indication
>>        a. create/update/delete entry in vacmAaaSecurityToGroupTable
>>             7.2.2.  Creation of Entries in vacmAaaSecurityToGroupTable
>>               Whenever an indication arrives  determine whether a
>>               corresponding entry exists in the
>>               vacmAaaSecurityToGroupTable. If one does not, create a
>>               new row......
>>               Otherwise, if the row already exists, update the
>>               vacmAaaGroupName
>>        b. create/update/delete entry in vacmSecurityToGroupTable
>>            7.2.3.  Creation of Entries in vacmSecurityToGroupTable
>>              Whenever an entry is created in the
>>              vacmAaaSecurityToGroupTable, the vacmSecurityToGroupTable
>>              is examined to determine whether corresponding entry
>>              exists there.  If no corresponding entry
>>              exists, create one, using the vacmAaaGroupName of the newly
>>              created entry to fill in vacmGroupName......
>>
>> It is clear that only if a vacmAaaSecurityToGroupEntry creation in (a)
>> succeeds (b) will attempted. [(b) will not be attempted if (a) fails.]
>> But it does not say what will be the effect if (b) fails. It appears
>> that there are 2 options for an implementer
>>        b-1. if (b) fails - rollback changes in (a)
>>        b-2. if (b) fails - do not rollback changes done in (a).
>> Is it clear from the text which option,  b-1 or b-2, should be taken
>> by an implementer? If it is not clear a fix is needed here.
> 
> Since there is no concrete text proposal and given the lack of WG
A sentence, at the end of section 7, should fix this problem. E.g.

     Failure to carry out the actions on vacmSecurityToGroupTable,
     specified in 7.2.3, 7.2.4 and 7.3.2, for whatever reason, will not
     impact the actions specified in 7.2.2 and 7.3.1, carried out on
     vacmAaaSecurityToGroupTable.

> support for adding more text detailing the handling of error
> situations, I believe we should close this issue with no change.  Note
> that once you look at why (b) can fail in real implementations, you
> likely can convince yourself that the actions to take might also be
> implementation specific.

Glenn

From randy_presuhn@mindspring.com  Fri Sep 10 10:36:52 2010
Return-Path: <randy_presuhn@mindspring.com>
X-Original-To: isms@core3.amsl.com
Delivered-To: isms@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 466163A6866; Fri, 10 Sep 2010 10:36:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.227
X-Spam-Level: 
X-Spam-Status: No, score=-102.227 tagged_above=-999 required=5 tests=[AWL=0.372, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ih0JA7-11vHb; Fri, 10 Sep 2010 10:36:49 -0700 (PDT)
Received: from elasmtp-galgo.atl.sa.earthlink.net (elasmtp-galgo.atl.sa.earthlink.net [209.86.89.61]) by core3.amsl.com (Postfix) with ESMTP id 3ECEA3A6A5B; Fri, 10 Sep 2010 10:36:08 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=G3EQa+QAGUHwdMaV92xvdpZz55bQhA4CdDc1BsouCjZ1IetoU+joN8alPCwwdH6p; 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.187.238.82] (helo=oemcomputer) by elasmtp-galgo.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <randy_presuhn@mindspring.com>) id 1Ou7WR-0007gX-3q; Fri, 10 Sep 2010 13:36:23 -0400
Message-ID: <002a01cb510e$bf2ed2e0$6801a8c0@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: <ietfmibs@ietf.org>, <isms@ietf.org>
References: <00d801cb4f84$0072ec00$6801a8c0@oemcomputer>	<4C8876A1.7090303@cysols.com><20100909075931.GA12224@elstar.local> <4C89BF6A.4030706@cysols.com>
Date: Fri, 10 Sep 2010 10:36:46 -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: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d88829a3b650ee59d5fe08a201a4c5affe85ec913ee79c97197f350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 99.187.238.82
Subject: Re: [Isms] [IETFMIBS]  status of draft-ietf-radius-vacm-10.txt
X-BeenThere: isms@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mailing list for the ISMS working group <isms.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isms>
List-Post: <mailto:isms@ietf.org>
List-Help: <mailto:isms-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Sep 2010 17:36:52 -0000

Hi -

As a technical contributor...

> From: "Glenn M. Keeni" <glenn@cysols.com>
> To: <ietfmibs@ietf.org>; <isms@ietf.org>
> Sent: Thursday, September 09, 2010 10:17 PM
> Subject: Re: [Isms] [IETFMIBS] status of draft-ietf-radius-vacm-10.txt
....
> NEW:
>     DESCRIPTION "An entry in this table maps the combination of a
>                  SnmpSecurityModel and securityName into the name
>                  of a VACM group defining the access control policy
>                  which is to govern a particular session.
> 
>                  Each entry corresponds to a session.
> 
>                  Entries do not persist across reboots.
> 
>                  An entry is created whenever an indication occurs
>                  that a new session has been established that would
>                  not have the same index values as an existing entry.
> 
>                  If an entry with the same index values exists then
>                  the vacmAaaGroupName is updated.

I think this does not belong here, and is only confusing in this context.
Saying "an entry [in this table] with the same index values exists" in an
entry's DESCRIPTION makes no sense from an SMI point of view, since
such a situation is impossible.

>                  Whenever an entry is created, if no corresponding entry
>                  exists in the vacmSecurityToGroupTable, an entry
>                  will be created in that table.
>
>                  If a corresponding entry exists in the
>                  vacmSecurityToGroupTable, and that entry's StorageType
>                  is 'volatile' and its RowStatus is 'active', the value
>                  of vacmGroupName in that entry will be updated with
>                  the value from vacmAaaGroupName.

If we mention this at all, it doesn't belong here, but rather would make more
sense as part of the DESCRIPTION of vacmAaaGroupName, since this
applies whenever vacmAaaGroupName is assigned a value; creation is just
a special case of that.

>                  When a session is torn down, disconnected, timed out
>                  (e.g., following the RADIUS Session-Timeout Attribute),
>                  or otherwise terminated for any reason, the
>                  corresponding vacmAaaSecurityToGroupEntry is deleted.
> 
>                  Whenever the last remaining row bearing a particular
>                  (vacmAaaSecurityModel, vacmAaaSecurityName) pair is
>                  deleted from the vacmAaaSecurityToGroupTable, the
>                  vacmSecurityToGroupTable is examined for a
>                  corresponding row. If one exists, and if its
>                  StorageType is 'volatile' and its RowStatus is
>                  'active', that row will be deleted as well."

I think this does not belong here.  If we mention it at all, it would belong in the
DESCRIPTION of the table, rather than the entry, since the conditions
described require knowledge of more than just the entry to evaluate.
 
...
> >> Issue-2:
...
> A sentence, at the end of section 7, should fix this problem. E.g.
> 
>      Failure to carry out the actions on vacmSecurityToGroupTable,
>      specified in 7.2.3, 7.2.4 and 7.3.2, for whatever reason, will not
>      impact the actions specified in 7.2.2 and 7.3.1, carried out on
>      vacmAaaSecurityToGroupTable.

If I encountered a sentence like this in a specification, and did not have
the benefit of all this discussion, I would be left totally baffled, wondering
"why on earth did they put this here?"  If there is a dependency between
elements of procedure, we say so.  It makes no sense to me to point out
imaginary dependencies only to say that they don't apply.

The *only* way I could support doing something like this was if
(1) implementation experience showed that implementors tended to
get it "wrong" and (2) this actually caused interoperability problems.

I very much doubt that either of these will prove true, and strongly oppose
adding this language.  I think it would set a terrible precedent.

Randy


From glenn@cysols.com  Fri Sep 10 23:58:53 2010
Return-Path: <glenn@cysols.com>
X-Original-To: isms@core3.amsl.com
Delivered-To: isms@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 645DD3A6856; Fri, 10 Sep 2010 23:58:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.073
X-Spam-Level: 
X-Spam-Status: No, score=0.073 tagged_above=-999 required=5 tests=[AWL=0.163,  BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IE5Q0FshmtEk; Fri, 10 Sep 2010 23:58:52 -0700 (PDT)
Received: from niseko.cysol.co.jp (niseko.cysol.co.jp [210.233.3.236]) by core3.amsl.com (Postfix) with ESMTP id 211663A6846; Fri, 10 Sep 2010 23:58:51 -0700 (PDT)
Received: from [192.168.0.218] (cookie.win2004.cysol.co.jp [192.168.0.218]) (authenticated bits=0) by aso.priv.cysol.co.jp (8.14.4/8.14.4) with ESMTP id o8B6wwAC047087 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Sat, 11 Sep 2010 15:59:03 +0900 (JST) (envelope-from glenn@cysols.com)
Message-ID: <4C8B28B2.70300@cysols.com>
Date: Sat, 11 Sep 2010 15:58:58 +0900
From: "Glenn M. Keeni" <glenn@cysols.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; ja; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2
MIME-Version: 1.0
To: isms@ietf.org, ietfmibs@ietf.org
References: <00d801cb4f84$0072ec00$6801a8c0@oemcomputer>	<4C8876A1.7090303@cysols.com><20100909075931.GA12224@elstar.local>	<4C89BF6A.4030706@cysols.com> <002a01cb510e$bf2ed2e0$6801a8c0@oemcomputer>
In-Reply-To: <002a01cb510e$bf2ed2e0$6801a8c0@oemcomputer>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
Subject: Re: [Isms] [IETFMIBS]  status of draft-ietf-radius-vacm-10.txt
X-BeenThere: isms@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mailing list for the ISMS working group <isms.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isms>
List-Post: <mailto:isms@ietf.org>
List-Help: <mailto:isms-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Sep 2010 06:58:53 -0000

Hi,
(2010/09/11 2:36), Randy Presuhn wrote:
> Hi -
> 
> As a technical contributor...
> 
>> From: "Glenn M. Keeni"<glenn@cysols.com>
>> To:<ietfmibs@ietf.org>;<isms@ietf.org>
>> Sent: Thursday, September 09, 2010 10:17 PM
>> Subject: Re: [Isms] [IETFMIBS] status of draft-ietf-radius-vacm-10.txt
> ....
>> NEW:
>>      DESCRIPTION "An entry in this table maps the combination of a
>>                   SnmpSecurityModel and securityName into the name
>>                   of a VACM group defining the access control policy
>>                   which is to govern a particular session.
>>
>>                   Each entry corresponds to a session.
>>
>>                   Entries do not persist across reboots.
>>
>>                   An entry is created whenever an indication occurs
>>                   that a new session has been established that would
>>                   not have the same index values as an existing entry.
>>
>>                   If an entry with the same index values exists then
>>                   the vacmAaaGroupName is updated.
> 
> I think this does not belong here, and is only confusing in this context.
> Saying "an entry [in this table] with the same index values exists" in an
> entry's DESCRIPTION makes no sense from an SMI point of view, since
> such a situation is impossible.
> 
>>                   Whenever an entry is created, if no corresponding entry
>>                   exists in the vacmSecurityToGroupTable, an entry
>>                   will be created in that table.
>>
>>                   If a corresponding entry exists in the
>>                   vacmSecurityToGroupTable, and that entry's StorageType
>>                   is 'volatile' and its RowStatus is 'active', the value
>>                   of vacmGroupName in that entry will be updated with
>>                   the value from vacmAaaGroupName.
> 
> If we mention this at all, it doesn't belong here, but rather would make more
> sense as part of the DESCRIPTION of vacmAaaGroupName, since this
> applies whenever vacmAaaGroupName is assigned a value; creation is just
> a special case of that.
> 
>>                   When a session is torn down, disconnected, timed out
>>                   (e.g., following the RADIUS Session-Timeout Attribute),
>>                   or otherwise terminated for any reason, the
>>                   corresponding vacmAaaSecurityToGroupEntry is deleted.
>>
>>                   Whenever the last remaining row bearing a particular
>>                   (vacmAaaSecurityModel, vacmAaaSecurityName) pair is
>>                   deleted from the vacmAaaSecurityToGroupTable, the
>>                   vacmSecurityToGroupTable is examined for a
>>                   corresponding row. If one exists, and if its
>>                   StorageType is 'volatile' and its RowStatus is
>>                   'active', that row will be deleted as well."
> 
> I think this does not belong here.  If we mention it at all, it would belong in the
> DESCRIPTION of the table, rather than the entry, since the conditions
> described require knowledge of more than just the entry to evaluate.
>
> ...
I agree that some portions of the proposed text will need to be moved
to more appropriate DESCRIPTIONs. We are making progress here.

>>>> Issue-2:
> ...
>> A sentence, at the end of section 7, should fix this problem. E.g.
>>
>>       Failure to carry out the actions on vacmSecurityToGroupTable,
>>       specified in 7.2.3, 7.2.4 and 7.3.2, for whatever reason, will not
>>       impact the actions specified in 7.2.2 and 7.3.1, carried out on
>>       vacmAaaSecurityToGroupTable.
> 
> If I encountered a sentence like this in a specification, and did not have
> the benefit of all this discussion, I would be left totally baffled, wondering
> "why on earth did they put this here?"  If there is a dependency between
> elements of procedure, we say so.  It makes no sense to me to point out
> imaginary dependencies only to say that they don't apply.
> 
> The *only* way I could support doing something like this was if
> (1) implementation experience showed that implementors tended to
> get it "wrong" and (2) this actually caused interoperability problems.
> 
> I very much doubt that either of these will prove true, and strongly oppose
> adding this language.  I think it would set a terrible precedent.
> 
Please reword/rephrase/relocate the text as is appropriate. But the
relationship (dependence or independence) between the elements of
procedure needs to be clear to the implementer. We have two elements:
element-a and element-b.  It is possible that element-a succeeds
and element-b fails. Without further clarity, the outcome will be
unpredictable.

Glenn



From j.schoenwaelder@jacobs-university.de  Sat Sep 11 02:46:33 2010
Return-Path: <j.schoenwaelder@jacobs-university.de>
X-Original-To: isms@core3.amsl.com
Delivered-To: isms@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 74AFF3A6881; Sat, 11 Sep 2010 02:46:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.98
X-Spam-Level: 
X-Spam-Status: No, score=-101.98 tagged_above=-999 required=5 tests=[AWL=0.269, BAYES_00=-2.599, HELO_EQ_DE=0.35, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id G5q0Ipp+BWQn; Sat, 11 Sep 2010 02:46:32 -0700 (PDT)
Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) by core3.amsl.com (Postfix) with ESMTP id E48F23A689C; Sat, 11 Sep 2010 02:46:31 -0700 (PDT)
Received: from localhost (demetrius3.jacobs-university.de [212.201.44.48]) by hermes.jacobs-university.de (Postfix) with ESMTP id 8F4DFC0018; Sat, 11 Sep 2010 11:46:58 +0200 (CEST)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius3.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id uV5SltAu9GvP; Sat, 11 Sep 2010 11:46:58 +0200 (CEST)
Received: from elstar.local (elstar.iuhb02.iu-bremen.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id ADF10C0008; Sat, 11 Sep 2010 11:46:57 +0200 (CEST)
Received: by elstar.local (Postfix, from userid 501) id 3A38914BA83E; Sat, 11 Sep 2010 11:46:32 +0200 (CEST)
Date: Sat, 11 Sep 2010 11:46:31 +0200
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: "Glenn M. Keeni" <glenn@cysols.com>
Message-ID: <20100911094630.GB29261@elstar.local>
Mail-Followup-To: "Glenn M. Keeni" <glenn@cysols.com>, "isms@ietf.org" <isms@ietf.org>, "ietfmibs@ietf.org" <ietfmibs@ietf.org>
References: <00d801cb4f84$0072ec00$6801a8c0@oemcomputer> <4C8876A1.7090303@cysols.com> <20100909075931.GA12224@elstar.local> <4C89BF6A.4030706@cysols.com> <002a01cb510e$bf2ed2e0$6801a8c0@oemcomputer> <4C8B28B2.70300@cysols.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4C8B28B2.70300@cysols.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: "ietfmibs@ietf.org" <ietfmibs@ietf.org>, "isms@ietf.org" <isms@ietf.org>
Subject: Re: [Isms] [IETFMIBS]    status of draft-ietf-radius-vacm-10.txt
X-BeenThere: isms@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
List-Id: Mailing list for the ISMS working group <isms.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isms>
List-Post: <mailto:isms@ietf.org>
List-Help: <mailto:isms-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Sep 2010 09:46:33 -0000

On Sat, Sep 11, 2010 at 08:58:58AM +0200, Glenn M. Keeni wrote:

> >>>> Issue-2:
> > ...
> >> A sentence, at the end of section 7, should fix this problem. E.g.
> >>
> >>       Failure to carry out the actions on vacmSecurityToGroupTable,
> >>       specified in 7.2.3, 7.2.4 and 7.3.2, for whatever reason, will not
> >>       impact the actions specified in 7.2.2 and 7.3.1, carried out on
> >>       vacmAaaSecurityToGroupTable.
> > 
> > If I encountered a sentence like this in a specification, and did not have
> > the benefit of all this discussion, I would be left totally baffled, wondering
> > "why on earth did they put this here?"  If there is a dependency between
> > elements of procedure, we say so.  It makes no sense to me to point out
> > imaginary dependencies only to say that they don't apply.
> > 
> > The *only* way I could support doing something like this was if
> > (1) implementation experience showed that implementors tended to
> > get it "wrong" and (2) this actually caused interoperability problems.
> > 
> > I very much doubt that either of these will prove true, and strongly oppose
> > adding this language.  I think it would set a terrible precedent.
> > 
> Please reword/rephrase/relocate the text as is appropriate. But the
> relationship (dependence or independence) between the elements of
> procedure needs to be clear to the implementer. We have two elements:
> element-a and element-b.  It is possible that element-a succeeds
> and element-b fails. Without further clarity, the outcome will be
> unpredictable.

Glenn, as far as I recall, nobody in the WG supported your position
that this is a problem. In other words, I do not see WG concensus to
make a change. I consider this issue closed with no change needed.

/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 glenn@cysols.com  Sat Sep 11 03:50:00 2010
Return-Path: <glenn@cysols.com>
X-Original-To: isms@core3.amsl.com
Delivered-To: isms@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 407603A6886; Sat, 11 Sep 2010 03:50:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.069
X-Spam-Level: 
X-Spam-Status: No, score=0.069 tagged_above=-999 required=5 tests=[AWL=0.159,  BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pF4KfeIC4hyk; Sat, 11 Sep 2010 03:49:59 -0700 (PDT)
Received: from niseko.cysol.co.jp (niseko.cysol.co.jp [210.233.3.236]) by core3.amsl.com (Postfix) with ESMTP id 164563A67CC; Sat, 11 Sep 2010 03:49:58 -0700 (PDT)
Received: from [192.168.0.218] (cookie.win2004.cysol.co.jp [192.168.0.218]) (authenticated bits=0) by aso.priv.cysol.co.jp (8.14.4/8.14.4) with ESMTP id o8BAo03t067914 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Sat, 11 Sep 2010 19:50:18 +0900 (JST) (envelope-from glenn@cysols.com)
Message-ID: <4C8B5ED8.5010708@cysols.com>
Date: Sat, 11 Sep 2010 19:50:00 +0900
From: "Glenn M. Keeni" <glenn@cysols.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; ja; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2
MIME-Version: 1.0
To: "isms@ietf.org" <isms@ietf.org>, "ietfmibs@ietf.org" <ietfmibs@ietf.org>
References: <00d801cb4f84$0072ec00$6801a8c0@oemcomputer> <4C8876A1.7090303@cysols.com> <20100909075931.GA12224@elstar.local> <4C89BF6A.4030706@cysols.com> <002a01cb510e$bf2ed2e0$6801a8c0@oemcomputer> <4C8B28B2.70300@cysols.com> <20100911094630.GB29261@elstar.local>
In-Reply-To: <20100911094630.GB29261@elstar.local>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
Subject: Re: [Isms] [IETFMIBS]    status of draft-ietf-radius-vacm-10.txt
X-BeenThere: isms@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mailing list for the ISMS working group <isms.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isms>
List-Post: <mailto:isms@ietf.org>
List-Help: <mailto:isms-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Sep 2010 10:50:00 -0000

(2010/09/11 18:46), Juergen Schoenwaelder wrote:
> On Sat, Sep 11, 2010 at 08:58:58AM +0200, Glenn M. Keeni wrote:
> 
>>>>>> Issue-2:
>>> ...
>>>> A sentence, at the end of section 7, should fix this problem. E.g.
>>>>
>>>>        Failure to carry out the actions on vacmSecurityToGroupTable,
>>>>        specified in 7.2.3, 7.2.4 and 7.3.2, for whatever reason, will not
>>>>        impact the actions specified in 7.2.2 and 7.3.1, carried out on
>>>>        vacmAaaSecurityToGroupTable.
>>>
>>> If I encountered a sentence like this in a specification, and did not have
>>> the benefit of all this discussion, I would be left totally baffled, wondering
>>> "why on earth did they put this here?"  If there is a dependency between
>>> elements of procedure, we say so.  It makes no sense to me to point out
>>> imaginary dependencies only to say that they don't apply.
>>>
>>> The *only* way I could support doing something like this was if
>>> (1) implementation experience showed that implementors tended to
>>> get it "wrong" and (2) this actually caused interoperability problems.
>>>
>>> I very much doubt that either of these will prove true, and strongly oppose
>>> adding this language.  I think it would set a terrible precedent.
>>>
>> Please reword/rephrase/relocate the text as is appropriate. But the
>> relationship (dependence or independence) between the elements of
>> procedure needs to be clear to theI have tried  implementer. We have two elements:
>> element-a and element-b.  It is possible that element-a succeeds
>> and element-b fails. Without further clarity, the outcome will be
>> unpredictable.
> 
> Glenn, as far as I recall, nobody in the WG supported your position
> that this is a problem. In other words, I do not see WG concensus to
> make a change. I consider this issue closed with no change needed.
OK. I understand your position. There is a disagreement. I guess that
it is the AD's call now :-)

Glenn

From d.b.nelson@comcast.net  Sat Sep 11 05:51:34 2010
Return-Path: <d.b.nelson@comcast.net>
X-Original-To: isms@core3.amsl.com
Delivered-To: isms@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B8A383A6825 for <isms@core3.amsl.com>; Sat, 11 Sep 2010 05:51:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.925
X-Spam-Level: 
X-Spam-Status: No, score=-100.925 tagged_above=-999 required=5 tests=[AWL=-0.740, BAYES_40=-0.185, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xbB2LRTXxac6 for <isms@core3.amsl.com>; Sat, 11 Sep 2010 05:51:33 -0700 (PDT)
Received: from qmta01.westchester.pa.mail.comcast.net (qmta01.westchester.pa.mail.comcast.net [76.96.62.16]) by core3.amsl.com (Postfix) with ESMTP id 9FE2E3A67FF for <isms@ietf.org>; Sat, 11 Sep 2010 05:51:33 -0700 (PDT)
Received: from omta10.westchester.pa.mail.comcast.net ([76.96.62.28]) by qmta01.westchester.pa.mail.comcast.net with comcast id 5QB51f0050cZkys51Qs10G; Sat, 11 Sep 2010 12:52:01 +0000
Received: from NEWTON603 ([24.218.90.45]) by omta10.westchester.pa.mail.comcast.net with comcast id 5Qs01f00B0yip6Y3WQs0Rl; Sat, 11 Sep 2010 12:52:01 +0000
From: "Dave Nelson" <d.b.nelson@comcast.net>
To: "'Glenn M. Keeni'" <glenn@cysols.com>
References: <00d801cb4f84$0072ec00$6801a8c0@oemcomputer><4C8876A1.7090303@cysols.com> <20100909075931.GA12224@elstar.local><4C89BF6A.4030706@cysols.com><002a01cb510e$bf2ed2e0$6801a8c0@oemcomputer><4C8B28B2.70300@cysols.com> <20100911094630.GB29261@elstar.local> <4C8B5ED8.5010708@cysols.com>
Date: Sat, 11 Sep 2010 08:51:59 -0400
Message-ID: <7C118E41497B45B59333D9A6C0B241EE@NEWTON603>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5931
In-Reply-To: <4C8B5ED8.5010708@cysols.com>
Thread-Index: ActRnyc640g4IXQyS3eTU3WCxCf4gwAD6/Ug
Cc: ietfmibs@ietf.org, isms@ietf.org
Subject: Re: [Isms] [IETFMIBS]    status of draft-ietf-radius-vacm-10.txt
X-BeenThere: isms@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mailing list for the ISMS working group <isms.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isms>
List-Post: <mailto:isms@ietf.org>
List-Help: <mailto:isms-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Sep 2010 12:51:35 -0000

> OK. I understand your position. There is a disagreement.
> I guess that it is the AD's call now :-)

Glenn, I think you understand that in the IETF tradition all Last Call
comments have equal weight.  Expert reviews are treated the same as WG
member commentary.  The only individuals who have extraordinary influence
are the IESG members.  A corollary of this is that not all comments require
changes to the draft document.

Too often these days I see what amounts to a negotiation between a single
reviewer requesting specific changes and the document sheppard representing
the consensus of the WG.  The review process is supposed to be about
highlighting possible errors, omission, points of confusion, and so forth,
and then letting IETF *consensus* dictate the changes to be made, if any.

Thanks for listening.

Regards,

Dave Nelson



From ietfdbh@comcast.net  Sat Sep 11 06:46:58 2010
Return-Path: <ietfdbh@comcast.net>
X-Original-To: isms@core3.amsl.com
Delivered-To: isms@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8351E3A67E6 for <isms@core3.amsl.com>; Sat, 11 Sep 2010 06:46:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.198
X-Spam-Level: 
X-Spam-Status: No, score=-102.198 tagged_above=-999 required=5 tests=[AWL=0.401, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dWrl0oMJPuqU for <isms@core3.amsl.com>; Sat, 11 Sep 2010 06:46:57 -0700 (PDT)
Received: from qmta14.westchester.pa.mail.comcast.net (qmta14.westchester.pa.mail.comcast.net [76.96.59.212]) by core3.amsl.com (Postfix) with ESMTP id 65E393A67FE for <isms@ietf.org>; Sat, 11 Sep 2010 06:46:57 -0700 (PDT)
Received: from omta15.westchester.pa.mail.comcast.net ([76.96.62.87]) by qmta14.westchester.pa.mail.comcast.net with comcast id 5QH61f0031swQuc5ERnRDb; Sat, 11 Sep 2010 13:47:25 +0000
Received: from 23FX1C1 ([67.189.235.106]) by omta15.westchester.pa.mail.comcast.net with comcast id 5RnQ1f0062JQnJT3bRnQBd; Sat, 11 Sep 2010 13:47:25 +0000
From: "David Harrington" <ietfdbh@comcast.net>
To: "'Dave Nelson'" <d.b.nelson@comcast.net>, "'Glenn M. Keeni'" <glenn@cysols.com>
References: <00d801cb4f84$0072ec00$6801a8c0@oemcomputer><4C8876A1.7090303@cysols.com><20100909075931.GA12224@elstar.local><4C89BF6A.4030706@cysols.com><002a01cb510e$bf2ed2e0$6801a8c0@oemcomputer><4C8B28B2.70300@cysols.com><20100911094630.GB29261@elstar.local> <4C8B5ED8.5010708@cysols.com> <7C118E41497B45B59333D9A6C0B241EE@NEWTON603>
Date: Sat, 11 Sep 2010 09:46:56 -0400
Message-ID: <2382AF8C7DD045978EFE18A19B5133AF@23FX1C1>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <7C118E41497B45B59333D9A6C0B241EE@NEWTON603>
Thread-Index: ActRnyc640g4IXQyS3eTU3WCxCf4gwAD6/UgAAH94cA=
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.5931
Cc: ietfmibs@ietf.org, isms@ietf.org
Subject: Re: [Isms] [IETFMIBS]    status of draft-ietf-radius-vacm-10.txt
X-BeenThere: isms@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mailing list for the ISMS working group <isms.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isms>
List-Post: <mailto:isms@ietf.org>
List-Help: <mailto:isms-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Sep 2010 13:46:58 -0000

Hi,

Even the IESG has limited influence. We are constrained in when we can
apply a DISCUSS.
See http://www.ietf.org/iesg/statement/discuss-criteria.html 

dbh 

> -----Original Message-----
> From: isms-bounces@ietf.org [mailto:isms-bounces@ietf.org] On 
> Behalf Of Dave Nelson
> Sent: Saturday, September 11, 2010 8:52 AM
> To: 'Glenn M. Keeni'
> Cc: ietfmibs@ietf.org; isms@ietf.org
> Subject: Re: [Isms] [IETFMIBS] status of
draft-ietf-radius-vacm-10.txt
> 
> > OK. I understand your position. There is a disagreement.
> > I guess that it is the AD's call now :-)
> 
> Glenn, I think you understand that in the IETF tradition all 
> Last Call comments have equal weight.  Expert reviews are 
> treated the same as WG member commentary.  The only 
> individuals who have extraordinary influence are the IESG 
> members.  A corollary of this is that not all comments 
> require changes to the draft document.
> 
> Too often these days I see what amounts to a negotiation 
> between a single reviewer requesting specific changes and the 
> document sheppard representing the consensus of the WG.  The 
> review process is supposed to be about highlighting possible 
> errors, omission, points of confusion, and so forth, and then 
> letting IETF *consensus* dictate the changes to be made, if any.
> 
> Thanks for listening.
> 
> Regards,
> 
> Dave Nelson
> 
> 
> _______________________________________________
> Isms mailing list
> Isms@ietf.org
> https://www.ietf.org/mailman/listinfo/isms


From glenn@cysols.com  Sat Sep 11 07:55:59 2010
Return-Path: <glenn@cysols.com>
X-Original-To: isms@core3.amsl.com
Delivered-To: isms@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 761573A685A; Sat, 11 Sep 2010 07:55:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.065
X-Spam-Level: 
X-Spam-Status: No, score=0.065 tagged_above=-999 required=5 tests=[AWL=0.155,  BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bz80P8NDtNUZ; Sat, 11 Sep 2010 07:55:58 -0700 (PDT)
Received: from niseko.cysol.co.jp (niseko.cysol.co.jp [210.233.3.236]) by core3.amsl.com (Postfix) with ESMTP id D5C793A6830; Sat, 11 Sep 2010 07:55:57 -0700 (PDT)
Received: from [192.168.0.90] (cysvpn03.priv.cysol.co.jp [192.168.0.90]) (authenticated bits=0) by aso.priv.cysol.co.jp (8.14.4/8.14.4) with ESMTP id o8BEtuG3090489 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Sat, 11 Sep 2010 23:55:58 +0900 (JST) (envelope-from glenn@cysols.com)
Message-ID: <4C8B987C.2050603@cysols.com>
Date: Sat, 11 Sep 2010 23:55:56 +0900
From: "Glenn M. Keeni" <glenn@cysols.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; ja; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2
MIME-Version: 1.0
To: Dave Nelson <d.b.nelson@comcast.net>, isms@ietf.org
References: <00d801cb4f84$0072ec00$6801a8c0@oemcomputer><4C8876A1.7090303@cysols.com> <20100909075931.GA12224@elstar.local><4C89BF6A.4030706@cysols.com><002a01cb510e$bf2ed2e0$6801a8c0@oemcomputer><4C8B28B2.70300@cysols.com> <20100911094630.GB29261@elstar.local> <4C8B5ED8.5010708@cysols.com> <7C118E41497B45B59333D9A6C0B241EE@NEWTON603>
In-Reply-To: <7C118E41497B45B59333D9A6C0B241EE@NEWTON603>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
Cc: ietfmibs@ietf.org
Subject: Re: [Isms] [IETFMIBS]    status of draft-ietf-radius-vacm-10.txt
X-BeenThere: isms@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mailing list for the ISMS working group <isms.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isms>
List-Post: <mailto:isms@ietf.org>
List-Help: <mailto:isms-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Sep 2010 14:55:59 -0000

Dave,
(2010/09/11 21:51), Dave Nelson wrote:
>> OK. I understand your position. There is a disagreement.
>> I guess that it is the AD's call now :-)
> 
> Glenn, I think you understand that in the IETF tradition all Last Call
> comments have equal weight.  Expert reviews are treated the same as WG
> member commentary.  The only individuals who have extraordinary influence
> are the IESG members.  A corollary of this is that not all comments require
> changes to the draft document.
No disagreement here.
> 
> Too often these days I see what amounts to a negotiation between a single
> reviewer requesting specific changes and the document sheppard representing
> the consensus of the WG.  

> The review process is supposed to be about
> highlighting possible errors, omission, points of confusion, and so forth,
> and then letting IETF *consensus* dictate the changes to be made, if any.
>
No disagreement here too. This is all part of the IETF process. And,
I think it is working well. I have no doubt that the results have been
good.

Cheers,

Glenn


From Robert.Story@cobham.com  Mon Sep 13 06:56:01 2010
Return-Path: <Robert.Story@cobham.com>
X-Original-To: isms@core3.amsl.com
Delivered-To: isms@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E7AB13A69ED for <isms@core3.amsl.com>; Mon, 13 Sep 2010 06:56:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.092
X-Spam-Level: 
X-Spam-Status: No, score=-0.092 tagged_above=-999 required=5 tests=[AWL=-0.093, BAYES_50=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fNy8FFs+WC52 for <isms@core3.amsl.com>; Mon, 13 Sep 2010 06:55:54 -0700 (PDT)
Received: from M4.sparta.com (M4.sparta.com [157.185.61.2]) by core3.amsl.com (Postfix) with ESMTP id B32CE3A69C3 for <isms@ietf.org>; Mon, 13 Sep 2010 06:55:53 -0700 (PDT)
Received: from Beta5.sparta.com (beta5.sparta.com [157.185.63.21]) by M4.sparta.com (8.13.5/8.13.5) with ESMTP id o8DDuJ4F003472 for <isms@ietf.org>; Mon, 13 Sep 2010 08:56:19 -0500
Received: from mailbin2.ads.sparta.com (mailbin.sparta.com [157.185.85.6]) by Beta5.sparta.com (8.13.8/8.13.8) with ESMTP id o8DDuKZ0002490 for <isms@ietf.org>; Mon, 13 Sep 2010 08:56:20 -0500
Received: from sparta.com ([216.27.162.138]) by mailbin2.ads.sparta.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 13 Sep 2010 09:56:18 -0400
Date: Mon, 13 Sep 2010 09:56:08 -0400
From: Robert Story <Robert.Story@cobham.com>
To: <isms@ietf.org>
Message-ID: <20100913095608.5e44d051@sparta.com>
Organization: SPARTA
X-Mailer: Claws Mail 3.7.6 (GTK+ 2.20.1; i386-redhat-linux-gnu)
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=PGP-SHA1; boundary="Sig_/1i/fdg4vOxZH0ZAHfJjq+vq"; protocol="application/pgp-signature"
X-OriginalArrivalTime: 13 Sep 2010 13:56:18.0691 (UTC) FILETIME=[7098DD30:01CB534B]
Subject: [Isms] RFC 5953 Implementation Report
X-BeenThere: isms@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mailing list for the ISMS working group <isms.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isms>
List-Post: <mailto:isms@ietf.org>
List-Help: <mailto:isms-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Sep 2010 13:56:01 -0000

--Sig_/1i/fdg4vOxZH0ZAHfJjq+vq
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

1 Introduction

  Sparta, Inc. has implemented RFC 5953 in the open source Simple
  Network Management package Net-SNMP. This report discusses the status
  of the implementation and some issues encountered during the
  implementation.


2 Code Availability

  A proof-of-concept implementation of (D)TLS support based on early
  versions of draft-ietf-isms-dtls-tm was an available configuration
  option in release 5.5 of Net-SNMP. A more complete implementation,
  including the MIB modules in RFC 5953 and RFC 5592 (Transport
  Security Model) is included in release 5.6 of Net-SNMP.

  The source for release 5.6 is available at:

    * http://www.net-snmp.org/download.html=20

  The TLS and DTLS cryptographic functionality is provided by OpenSSL
  libraries.


3 Interoperability Testing

3.1 SNMP Research

  Some limited initial interoperability testing has been done with SNMP
  Research's implementations. We are maintaining communication with
  SNMP Research, and plan on continuing interoperability testing as
  each of our implementations mature.

3.2 Public Interoperability Testing Available

  The publicly-available Net-SNMP test server is running release 5.6
  with (D)TLS support enabled. We have made it available both for
  end-users that wish to explore SNMP over (D)TLS technologies as well
  as implementers that are in the process of implementing SNMP over
  (D)TLS. We encourage others implementing RFC 5953 to test their
  implementations with the Net-SNMP test server. We welcome any
  questions about interoperability issues and will gladly provide
  assistance in debugging and resolve any such issues.

  The client and server certificates needed for testing with the
  Net-SNMP test server, along with a tutorial on configuring and using
  (D)TLS with Net-SNMP, can be found at:

    * http://www.net-snmp.org/wiki/index.php/TUT:Using_TLS=20

  Questions or comments about any interoperability experiences or
  issues with the Net-SNMP test server should be directed to the
  Net-SNMP coders mailing list,
  <net-snmp-coders@lists.sourceforge.net>.


4 Net-SNMP Background

  Net-SNMP implements the transports over which SNMP messages can be
  sent using a pluggable architecture. This architecture defines hooks
  that allow implemented transports to handle opening, sending and
  receiving packets through "something or other". The "something or
  other" can be almost anything and Net-SNMP has support for: IPv4/UDP,
  IPv6/TCP, UnixDomain Sockets, IPX, and internal pipe()s and even
  stdin/stdout, to name just a few of the diverse examples.

  To implement (D)TLS support within Net-SNMP, several new transports
  were written to provide dtlsudp and tlstcp support.


5 Challenges

5.1 DTLS: one socket, multiple sessions

  Since all DTLS traffic is sent to a single well-known port,
  implementations must be able to demultiplex data for multiple
  sessions arriving on the same port. Unfortunately, OpenSSL's internal
  processing algorithm appears to be greedy; this means that calling
  the OpenSSL API while processing a packet for a particular session
  can result in packets intended for other sessions being returned to
  the application.

  To handle this, the Net-SNMP does all UDP packet processing itself
  (as is described in RFC 5953, section 5.1.2), handing off individual
  packets to OpenSSL for processing. While this works, it is
  inefficient. Hopefully we will find a solution for this issue in a
  future release as support for DTLS in the OpenSSL code base continues
  to be refined.

5.2 Configuring transport security

5.2.1 Peering into the black box

  Prior to adding support for the Transport Security Model all security
  was in the SNMP protocol. The transport model in the Net-SNMP code
  base was essentially a black box with a slot to feed packets in and
  and a bin where packets arrived. The only real configuration needed
  for the transport was the address specifying where the packets were
  coming and going to and/or from. For example, with IP based protocols
  this was a simple address/port number pair.

  With transport security models, the secure transports required
  additional configuration besides just the end-point description. The
  Net-SNMP transport system was extended to accommodate a new
  configuration API that could be used in between transport object
  instantiation and the point where the actual transport connection
  (i.e. socket opening) was performed. This additional middle
  configuration step allows for SNMP applications to pass opaque
  configuration data to the transport.

  This new configuration was done in such a way that older transport's
  code and existing code that used the older transports did not need to
  be modified. However, applications that want to make use of the newer
  secure transports may need to understand the newer transport
  configuration API mechanisms.

5.2.2 Certificate complexity

  Certificates have long been used for securing communication and
  providing identities. Unfortunately, no "killer application" has been
  written yet that makes certificate management easy for the masses.

  OpenSSL is a popular choice for creating certificates since it is
  available for free. The web is full of examples for generating
  certificates for a wide range of services. A common complaint,
  however, is that the command line interface OpenSSL is complex and
  cryptic.

  Net-SNMP has tried to mitigate this by creating a wrapper script for
  managing certificates. This script ("net-snmp-certs") can create a
  Certificate Authority, sign new certificates with that Certificate
  Authority and create self signed certificates. Certificates and keys
  are automatically stored in the directory structure used by the
  Net-SNMP tools and applications.

  Applications and tools need to configure their own/local identity and
  the peer/remote identity. The certificates can be configured via the
  application configuration file or on the command line. A new feature
  was also added to allow the tools and applications to read a host
  specific configuration file.

  The Net-SNMP tools and applications handle referring to certificates
  by file name, fingerprint or a tag. Applications will search the
  certificate directory structure for a certificate/key based on the
  default tag for the application so that explicit configuration of the
  local identity is not required in some cases.


6 Conclusions

  Testing of the Net-SNMP (D)TLS implementation is ongoing. Our
  internal test suite exercises the code for various certificate
  configurations, including variations of the Subject Alt Names. Tests
  exist for the certificate to security name mapping MIB tables, and
  additional tests are planned for the target and parameter tables.
  While these tests are currently designed to run against Net-SNMP, it
  is a goal to have the ability to run the test suite against other
  vendor implementations as well, as an aid to interoperability testing.

  If there is an area of concern for interoperability, it would be with
  the vagueness in the specification with regards to mapping between
  (D)TLS authentication and encryption algorithms and tmSecurityLevel
  since there is no standardized mechanisms for configuring the
  mapping. If an implementation allows (D)TLS to negotiate weaker
  algorithms but maps them to lower security levels and a client
  considers those same algorithms to be sufficient for authPriv then
  authorization errors will result.

  In summary, we have implemented the (D)TLS transport and successfully
  conducted limited interoperability testing with SNMP Research.
  Interoperability testing will continue, but we believe that the
  (D)TLS specification is sufficient to allow for interoperability.=20

--=20
Robert Story
Senior Software Engineer
SPARTA (dba Cobham Analytic Soloutions)

--Sig_/1i/fdg4vOxZH0ZAHfJjq+vq
Content-Type: application/pgp-signature; name=signature.asc
Content-Disposition: attachment; filename=signature.asc

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (GNU/Linux)

iEYEARECAAYFAkyOLYEACgkQ7/fVLLY1mnhq8gCfUx22wxKFcXQmDusD7r6VE0h6
qOwAmwQjIaaZlpfdr16YqoP7lTcXv6Lx
=rE8A
-----END PGP SIGNATURE-----

--Sig_/1i/fdg4vOxZH0ZAHfJjq+vq--

From root@core3.amsl.com  Tue Sep 14 10:45:46 2010
Return-Path: <root@core3.amsl.com>
X-Original-To: isms@ietf.org
Delivered-To: isms@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id 88D383A69EB; Tue, 14 Sep 2010 10:45:23 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20100914174542.88D383A69EB@core3.amsl.com>
Date: Tue, 14 Sep 2010 10:45:23 -0700 (PDT)
Cc: isms@ietf.org
Subject: [Isms] I-D Action:draft-ietf-isms-radius-vacm-11.txt
X-BeenThere: isms@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mailing list for the ISMS working group <isms.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isms>
List-Post: <mailto:isms@ietf.org>
List-Help: <mailto:isms-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Sep 2010 17:45:47 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Integrated Security Model for SNMP Working Group of the IETF.


	Title           : Using Authentication, Authorization, and Accounting services to Dynamically Provision View-based Access Control Model User-to-Group Mappings
	Author(s)       : K. Narayan, et al.
	Filename        : draft-ietf-isms-radius-vacm-11.txt
	Pages           : 19
	Date            : 2010-09-14

This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols.  It describes the use of
information provided by Authentication, Authorization, and Accounting
(AAA) services, such as the Remote Authentication Dial-In User
Service (RADIUS), to dynamically update user-to-group mappings in the
View-Based Access Control Model (VACM).

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-isms-radius-vacm-11.txt

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

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

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-isms-radius-vacm-11.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2010-09-14103436.I-D@ietf.org>


--NextPart--

From randy_presuhn@mindspring.com  Tue Sep 14 11:10:19 2010
Return-Path: <randy_presuhn@mindspring.com>
X-Original-To: isms@core3.amsl.com
Delivered-To: isms@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1930B3A6ADA; Tue, 14 Sep 2010 11:10:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.594
X-Spam-Level: 
X-Spam-Status: No, score=-101.594 tagged_above=-999 required=5 tests=[AWL=-0.484, BAYES_05=-1.11, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AtrRWOsWQD7o; Tue, 14 Sep 2010 11:10:17 -0700 (PDT)
Received: from elasmtp-banded.atl.sa.earthlink.net (elasmtp-banded.atl.sa.earthlink.net [209.86.89.70]) by core3.amsl.com (Postfix) with ESMTP id A6C113A6ADD; Tue, 14 Sep 2010 11:10:16 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=VzdMsg4maBsXR9/+WLlStnzKnzd9HR71EaFPS00GqyEXlQfD5MD1+4xJUgBqhAR4; h=Received:Message-ID:From:To: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.55.173.69] (helo=oemcomputer) by elasmtp-banded.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <randy_presuhn@mindspring.com>) id 1OvZxp-0001BI-9s; Tue, 14 Sep 2010 14:10:42 -0400
Message-ID: <007601cb5438$3ab47d80$6801a8c0@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: <isms@ietf.org>, <mib-doctors@ietf.org>
Date: Tue, 14 Sep 2010 11:11:17 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1478
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1478
X-ELNK-Trace: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d88829a3b650ee59d5fe096414b095445c3dfdd9b83806df29e9350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 99.55.173.69
Subject: [Isms] Fw: New Version Notification - draft-ietf-isms-radius-vacm-11.txt
X-BeenThere: isms@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mailing list for the ISMS working group <isms.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isms>
List-Post: <mailto:isms@ietf.org>
List-Help: <mailto:isms-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Sep 2010 18:10:19 -0000

Hi -

> From: <Internet-Draft@ietf.org>
> To: <isms-chairs@tools.ietf.org>; <draft-ietf-isms-radius-vacm@tools.ietf.org>; <turners@ieca.com>; <dromasca@avaya.com>
> Sent: Tuesday, September 14, 2010 10:45 AM
> Subject: New Version Notification - draft-ietf-isms-radius-vacm-11.txt 
>
> New version (-11) has been submitted for draft-ietf-isms-radius-vacm-11.txt.
> http://www.ietf.org/internet-drafts/draft-ietf-isms-radius-vacm-11.txt
> 
> 
> Diff from previous version:
> http://tools.ietf.org/rfcdiff?url2=draft-ietf-isms-radius-vacm-11
> 
> IETF Secretariat.

I believe this version incorporates all the changes agreed to in
response to MIB doctor and other IESG review comments.

Note that two MIB doctor comments (adding additional commentary
regarding VACM tables to the new MIB module's DESCRIPTION clauses,
recapping elements of procedure from the body of the document; 
and adding text proscribing implementation strategies that would
not fulfill the requirements set forth elsewhere in the document)
did not gain rough consensus support in the isms working group, even
after lengthy discussion. Consequently, those two changes were *not*
adopted.

Randy


From j.schoenwaelder@jacobs-university.de  Tue Sep 14 23:17:47 2010
Return-Path: <j.schoenwaelder@jacobs-university.de>
X-Original-To: isms@core3.amsl.com
Delivered-To: isms@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6CCA63A68D8 for <isms@core3.amsl.com>; Tue, 14 Sep 2010 23:17:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.683
X-Spam-Level: 
X-Spam-Status: No, score=-100.683 tagged_above=-999 required=5 tests=[AWL=-1.034, BAYES_50=0.001, HELO_EQ_DE=0.35, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a7dCwhKttKys for <isms@core3.amsl.com>; Tue, 14 Sep 2010 23:17:18 -0700 (PDT)
Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) by core3.amsl.com (Postfix) with ESMTP id 2E1F73A68B3 for <isms@ietf.org>; Tue, 14 Sep 2010 23:17:00 -0700 (PDT)
Received: from localhost (demetrius4.jacobs-university.de [212.201.44.49]) by hermes.jacobs-university.de (Postfix) with ESMTP id 398A1C0029; Wed, 15 Sep 2010 08:17:11 +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 k1-Ygq502xyE; Wed, 15 Sep 2010 08:17:10 +0200 (CEST)
Received: from elstar.local (elstar.iuhb02.iu-bremen.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id 824E6C0024; Wed, 15 Sep 2010 08:17:07 +0200 (CEST)
Received: by elstar.local (Postfix, from userid 501) id DB38714D7AC2; Wed, 15 Sep 2010 08:16:43 +0200 (CEST)
Date: Wed, 15 Sep 2010 08:16:43 +0200
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: Robert Story <Robert.Story@cobham.com>
Message-ID: <20100915061643.GB30817@elstar.local>
Mail-Followup-To: Robert Story <Robert.Story@cobham.com>, "isms@ietf.org" <isms@ietf.org>
References: <20100913095608.5e44d051@sparta.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20100913095608.5e44d051@sparta.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: "isms@ietf.org" <isms@ietf.org>
Subject: Re: [Isms] RFC 5953 Implementation Report
X-BeenThere: isms@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
List-Id: Mailing list for the ISMS working group <isms.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isms>
List-Post: <mailto:isms@ietf.org>
List-Help: <mailto:isms-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Sep 2010 06:17:49 -0000

On Mon, Sep 13, 2010 at 03:56:08PM +0200, Robert Story wrote:
> 1 Introduction
> 
>   Sparta, Inc. has implemented RFC 5953 in the open source Simple
>   Network Management package Net-SNMP. This report discusses the status
>   of the implementation and some issues encountered during the
>   implementation.

Robert,

many thanks for the implementation report. It is very good to hear
that implementations are being worked on and that interoperability
testing takes place.

Your report covers RFC 5953 and RFC 5591 (and implicitely also RFC
5590 as it provides the framework for RFC 5590). One question: Do
these implementations make use of RFC 5343 for context engineid
discovery?

/js

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

From dromasca@avaya.com  Wed Sep 15 05:39:29 2010
Return-Path: <dromasca@avaya.com>
X-Original-To: isms@core3.amsl.com
Delivered-To: isms@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D51C03A6BF9; Wed, 15 Sep 2010 05:39:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.501
X-Spam-Level: 
X-Spam-Status: No, score=-102.501 tagged_above=-999 required=5 tests=[AWL=0.098, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Aac6WvIter4s; Wed, 15 Sep 2010 05:39:28 -0700 (PDT)
Received: from p-us1-iereast-outbound-tmp.us1.avaya.com (p-us1-iereast-outbound-tmp.us1.avaya.com [135.11.29.16]) by core3.amsl.com (Postfix) with ESMTP id 50DC63A6BE3; Wed, 15 Sep 2010 05:38:45 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.56,371,1280721600"; d="scan'208";a="34714427"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by p-us1-iereast-outbound-tmp.us1.avaya.com with ESMTP; 15 Sep 2010 08:38:49 -0400
X-IronPort-AV: E=Sophos;i="4.56,371,1280721600"; d="scan'208";a="511707698"
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.12]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 15 Sep 2010 08:38:13 -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, 15 Sep 2010 14:37:54 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A040251E762@307622ANEX5.global.avaya.com>
In-Reply-To: <007601cb5438$3ab47d80$6801a8c0@oemcomputer>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [MIB-DOCTORS] Fw: New Version Notification -draft-ietf-isms-radius-vacm-11.txt
Thread-Index: ActUOClpv+zHKdaCS3CbA11RlqAWFQAmjA8A
References: <007601cb5438$3ab47d80$6801a8c0@oemcomputer>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Randy Presuhn" <randy_presuhn@mindspring.com>, <isms@ietf.org>, <mib-doctors@ietf.org>
Subject: Re: [Isms] [MIB-DOCTORS] Fw: New Version Notification -draft-ietf-isms-radius-vacm-11.txt
X-BeenThere: isms@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mailing list for the ISMS working group <isms.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isms>
List-Post: <mailto:isms@ietf.org>
List-Help: <mailto:isms-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Sep 2010 12:39:30 -0000

=20

> -----Original Message-----
> From: mib-doctors-bounces@ietf.org=20
> [mailto:mib-doctors-bounces@ietf.org] On Behalf Of Randy Presuhn
> Sent: Tuesday, September 14, 2010 8:11 PM
> To: isms@ietf.org; mib-doctors@ietf.org
> Subject: [MIB-DOCTORS] Fw: New Version Notification=20
> -draft-ietf-isms-radius-vacm-11.txt
>=20
> Hi -
>=20
> > From: <Internet-Draft@ietf.org>
> > To: <isms-chairs@tools.ietf.org>;=20
> > <draft-ietf-isms-radius-vacm@tools.ietf.org>; <turners@ieca.com>;=20
> > <dromasca@avaya.com>
> > Sent: Tuesday, September 14, 2010 10:45 AM
> > Subject: New Version Notification -=20
> draft-ietf-isms-radius-vacm-11.txt
> >
> > New version (-11) has been submitted for=20
> draft-ietf-isms-radius-vacm-11.txt.
> >=20
> http://www.ietf.org/internet-drafts/draft-ietf-isms-radius-vacm-11.txt
> >=20
> >=20
> > Diff from previous version:
> > http://tools.ietf.org/rfcdiff?url2=3Ddraft-ietf-isms-radius-vacm-11
> >=20
> > IETF Secretariat.
>=20
> I believe this version incorporates all the changes agreed to=20
> in response to MIB doctor and other IESG review comments.
>=20
> Note that two MIB doctor comments (adding additional=20
> commentary regarding VACM tables to the new MIB module's=20
> DESCRIPTION clauses, recapping elements of procedure from the=20
> body of the document; and adding text proscribing=20
> implementation strategies that would not fulfill the=20
> requirements set forth elsewhere in the document) did not=20
> gain rough consensus support in the isms working group, even=20
> after lengthy discussion. Consequently, those two changes=20
> were *not* adopted.
>=20
> Randy
>=20


The two remaining comments represent in my opinion optimizations and
reafirmation of texts that already exist in the document.=20

I have cleared my DISCUSS and changed my vote to a 'Yes'.=20

Thanks to the authors for writing this document and for answering
carefully to the concerns of the reviewers, thanks to Glen for the
detailed and attentive review.=20

Dan

From wjhns1@hardakers.net  Wed Sep 15 06:38:02 2010
Return-Path: <wjhns1@hardakers.net>
X-Original-To: isms@core3.amsl.com
Delivered-To: isms@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 723D83A6848 for <isms@core3.amsl.com>; Wed, 15 Sep 2010 06:38:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ecyzUgflOI4c for <isms@core3.amsl.com>; Wed, 15 Sep 2010 06:36:52 -0700 (PDT)
Received: from mail.hardakers.net (hardaker-pt.tunnel.tserv1.fmt.ipv6.he.net [IPv6:2001:470:1f00:ffff::af]) by core3.amsl.com (Postfix) with ESMTP id C979B3A6C01 for <isms@ietf.org>; Wed, 15 Sep 2010 06:36:25 -0700 (PDT)
Received: from localhost (wjh.hardakers.net [10.0.0.2]) by mail.hardakers.net (Postfix) with ESMTPSA id B33F1980E2; Wed, 15 Sep 2010 06:36:50 -0700 (PDT)
From: Wes Hardaker <wjhns1@hardakers.net>
To: Robert Story <Robert.Story@cobham.com>
Organization: Sparta
References: <20100913095608.5e44d051@sparta.com> <20100915061643.GB30817@elstar.local>
Date: Wed, 15 Sep 2010 06:36:50 -0700
In-Reply-To: <20100915061643.GB30817@elstar.local> (Juergen Schoenwaelder's message of "Wed, 15 Sep 2010 08:16:43 +0200")
Message-ID: <sdy6b3t9fx.fsf@wjh.hardakers.net>
User-Agent: Gnus/5.110011 (No Gnus v0.11) Emacs/23.2 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
Cc: "isms@ietf.org" <isms@ietf.org>
Subject: Re: [Isms] RFC 5953 Implementation Report
X-BeenThere: isms@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mailing list for the ISMS working group <isms.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isms>
List-Post: <mailto:isms@ietf.org>
List-Help: <mailto:isms-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Sep 2010 13:38:03 -0000

>>>>> On Wed, 15 Sep 2010 08:16:43 +0200, Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de> said:

JS> Your report covers RFC 5953 and RFC 5591 (and implicitely also RFC
JS> 5590 as it provides the framework for RFC 5590). One question: Do
JS> these implementations make use of RFC 5343 for context engineid
JS> discovery?

Yes, they both at least some support for 5343 (good question!  We should
have mentioned that!)

I don't know SNMP Research's plans for their products with it, but
Net-SNMP has full support for both the client and server side.
-- 
Wes Hardaker
Cobham Analytic Solutions

From wjhns1@hardakers.net  Wed Sep 15 09:26:32 2010
Return-Path: <wjhns1@hardakers.net>
X-Original-To: isms@core3.amsl.com
Delivered-To: isms@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5FF0D3A6A0E for <isms@core3.amsl.com>; Wed, 15 Sep 2010 09:26:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gRyAxHJG8ccl for <isms@core3.amsl.com>; Wed, 15 Sep 2010 09:26:31 -0700 (PDT)
Received: from mail.hardakers.net (hardaker-pt.tunnel.tserv1.fmt.ipv6.he.net [IPv6:2001:470:1f00:ffff::af]) by core3.amsl.com (Postfix) with ESMTP id 5B3EB3A69F1 for <isms@ietf.org>; Wed, 15 Sep 2010 09:26:31 -0700 (PDT)
Received: from localhost (wjh.hardakers.net [10.0.0.2]) by mail.hardakers.net (Postfix) with ESMTPSA id DDF53980A3 for <isms@ietf.org>; Wed, 15 Sep 2010 09:26:55 -0700 (PDT)
From: Wes Hardaker <wjhns1@hardakers.net>
To: isms@ietf.org
Organization: Sparta
Date: Wed, 15 Sep 2010 09:26:55 -0700
Message-ID: <sdlj73rn00.fsf@wjh.hardakers.net>
User-Agent: Gnus/5.110011 (No Gnus v0.11) Emacs/23.2 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
Subject: [Isms] RFC5590, 5591 (TSM) and 5953 (TLSTM) interoperability testing
X-BeenThere: isms@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mailing list for the ISMS working group <isms.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isms>
List-Post: <mailto:isms@ietf.org>
List-Help: <mailto:isms-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Sep 2010 16:26:32 -0000

We are looking for people interested in doing interoperability testing
for the specifications that make up the set required to implement TLSTM.
Specifically, we're looking for people, companies or organizations that
have implemented:

  5590 Transport Subsystem for the Simple Network Management Protocol
       (SNMP). D. Harrington, J. Schoenwaelder. June 2009. (Format:
       TXT=84513 bytes) (Updates RFC3411, RFC3412, RFC3414, RFC3417)
       (Status: PROPOSED STANDARD)

  5591 Transport Security Model for the Simple Network Management
       Protocol (SNMP). D. Harrington, W. Hardaker. June 2009. (Format:
       TXT=61747 bytes) (Status: PROPOSED STANDARD)

  5953 Transport Layer Security (TLS) Transport Model for the Simple
       Network Management Protocol (SNMP). W. Hardaker. August 2010.
       (Format: TXT=147393 bytes) (Status: PROPOSED STANDARD)

And ideally this one as well:

  5343 Simple Network Management Protocol (SNMP) Context EngineID
       Discovery. J. Schoenwaelder. September 2008. (Format: TXT=19938
       bytes) (Updates RFC3411) (Status: PROPOSED STANDARD)

If you have implemented or are currently implementing any of these
specifications, please let me know so we can coordinate interoperability
testing with your software, our software (Net-SNMP) and software from
any other participants that respond to this request.

Thank you!

-- 
Wes Hardaker
Cobham Analytic Solutions

From iesg-secretary@ietf.org  Wed Sep 15 12:33:08 2010
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: isms@core3.amsl.com
Delivered-To: isms@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 669A33A6A89; Wed, 15 Sep 2010 12:33:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oEj75jOFUsO7; Wed, 15 Sep 2010 12:33:06 -0700 (PDT)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4AA133A6ABB; Wed, 15 Sep 2010 12:32:53 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
X-Test-IDTracker: no
Message-ID: <20100915193253.21205.86404.idtracker@localhost>
Date: Wed, 15 Sep 2010 12:32:53 -0700
Cc: Internet Architecture Board <iab@iab.org>, isms mailing list <isms@ietf.org>, isms chair <isms-chairs@tools.ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>
Subject: [Isms] Protocol Action: 'Using Authentication, Authorization, and Accounting services to Dynamically Provision View-based Access	Control Model User-to-Group Mappings' to Proposed Standard
X-BeenThere: isms@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mailing list for the ISMS working group <isms.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isms>
List-Post: <mailto:isms@ietf.org>
List-Help: <mailto:isms-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Sep 2010 19:33:08 -0000

The IESG has approved the following document:
- 'Using Authentication, Authorization, and Accounting services to
   Dynamically Provision View-based Access Control Model User-to-Group
   Mappings'
  <draft-ietf-isms-radius-vacm-11.txt> as a Proposed Standard

This document is the product of the Integrated Security Model for SNMP
Working Group.

The IESG contact persons are Sean Turner and Tim Polk.

A URL of this Internet Draft is:
https://datatracker.ietf.org/doc/draft-ietf-isms-radius-vacm/



Technical Summary

  The document describes how to use Authentication,
  Authorization, and Accounting (AAA) services, such as the
  Remote Authentication Dial-In User Service (RADIUS), for
  access control authorization within the Simple Network
  Management Protocol (SNMP) framework. A MIB module is
  provided to dynamically update user-to-group mappings in the
  View-Based Access Control Model (VACM).

Working Group Summary

  The working group went over several revisions of this document
  and the document and all WG last call comments have been
  resolved. There has been strong WG consensus to publish this
  document as Proposed Standard.

Document Quality

  The chair is not aware of any implementations at this point in
  time. Dave Harrington has provided significant reviews that
  helped with the clarity and modularity aspects of the SNMP
  specifications. 

Personnel

  Juergen Schoenwaelder is the document shepherd.
  Sean Turner is the Responsible Area Director.

From glenn@cysols.com  Thu Sep 16 04:21:50 2010
Return-Path: <glenn@cysols.com>
X-Original-To: isms@core3.amsl.com
Delivered-To: isms@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1DEB03A6B29; Thu, 16 Sep 2010 04:21:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.062
X-Spam-Level: 
X-Spam-Status: No, score=0.062 tagged_above=-999 required=5 tests=[AWL=0.152,  BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8+LGRLHT8wOL; Thu, 16 Sep 2010 04:21:46 -0700 (PDT)
Received: from niseko.cysol.co.jp (niseko.cysol.co.jp [210.233.3.236]) by core3.amsl.com (Postfix) with ESMTP id 864F93A6ADF; Thu, 16 Sep 2010 04:19:56 -0700 (PDT)
Received: from [192.168.0.218] (cookie.win2004.cysol.co.jp [192.168.0.218]) (authenticated bits=0) by aso.priv.cysol.co.jp (8.14.4/8.14.4) with ESMTP id o8GBJw1K053998 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Thu, 16 Sep 2010 20:20:05 +0900 (JST) (envelope-from glenn@cysols.com)
Message-ID: <4C91FD5D.1020009@cysols.com>
Date: Thu, 16 Sep 2010 20:19:57 +0900
From: "Glenn M. Keeni" <glenn@cysols.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; ja; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2
MIME-Version: 1.0
To: mib-doctors@ietf.org, "isms@ietf.org" <isms@ietf.org>
References: <007601cb5438$3ab47d80$6801a8c0@oemcomputer> <EDC652A26FB23C4EB6384A4584434A040251E762@307622ANEX5.global.avaya.com>
In-Reply-To: <EDC652A26FB23C4EB6384A4584434A040251E762@307622ANEX5.global.avaya.com>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
Subject: Re: [Isms] [MIB-DOCTORS] Fw: New Version Notification	-draft-ietf-isms-radius-vacm-11.txt
X-BeenThere: isms@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mailing list for the ISMS working group <isms.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isms>
List-Post: <mailto:isms@ietf.org>
List-Help: <mailto:isms-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Sep 2010 11:21:51 -0000

Hi,
  I am happy that the review has concluded.
Thanks Dan. Thanks to the WG too for the
patience and cooperation during the review
process.
  We will be looking forward to seeing the
RFC and implementations.

Cheers
Glenn

(2010/09/15 21:37), Romascanu, Dan (Dan) wrote:
> 
> 
>> -----Original Message-----
>> From: mib-doctors-bounces@ietf.org
>> [mailto:mib-doctors-bounces@ietf.org] On Behalf Of Randy Presuhn
>> Sent: Tuesday, September 14, 2010 8:11 PM
>> To: isms@ietf.org; mib-doctors@ietf.org
>> Subject: [MIB-DOCTORS] Fw: New Version Notification
>> -draft-ietf-isms-radius-vacm-11.txt
>>
>> Hi -
>>
>>> From:<Internet-Draft@ietf.org>
>>> To:<isms-chairs@tools.ietf.org>;
>>> <draft-ietf-isms-radius-vacm@tools.ietf.org>;<turners@ieca.com>;
>>> <dromasca@avaya.com>
>>> Sent: Tuesday, September 14, 2010 10:45 AM
>>> Subject: New Version Notification -
>> draft-ietf-isms-radius-vacm-11.txt
>>>
>>> New version (-11) has been submitted for
>> draft-ietf-isms-radius-vacm-11.txt.
>>>
>> http://www.ietf.org/internet-drafts/draft-ietf-isms-radius-vacm-11.txt
>>>
>>>
>>> Diff from previous version:
>>> http://tools.ietf.org/rfcdiff?url2=draft-ietf-isms-radius-vacm-11
>>>
>>> IETF Secretariat.
>>
>> I believe this version incorporates all the changes agreed to
>> in response to MIB doctor and other IESG review comments.
>>
>> Note that two MIB doctor comments (adding additional
>> commentary regarding VACM tables to the new MIB module's
>> DESCRIPTION clauses, recapping elements of procedure from the
>> body of the document; and adding text proscribing
>> implementation strategies that would not fulfill the
>> requirements set forth elsewhere in the document) did not
>> gain rough consensus support in the isms working group, even
>> after lengthy discussion. Consequently, those two changes
>> were *not* adopted.
>>
>> Randy
>>
> 
> 
> The two remaining comments represent in my opinion optimizations and
> reafirmation of texts that already exist in the document.
> 
> I have cleared my DISCUSS and changed my vote to a 'Yes'.
> 
> Thanks to the authors for writing this document and for answering
> carefully to the concerns of the reviewers, thanks to Glen for the
> detailed and attentive review.
> 
> Dan
> _______________________________________________
> MIB-DOCTORS mailing list
> MIB-DOCTORS@ietf.org
> https://www.ietf.org/mailman/listinfo/mib-doctors


From wjhns1@hardakers.net  Thu Sep 16 09:02:11 2010
Return-Path: <wjhns1@hardakers.net>
X-Original-To: isms@core3.amsl.com
Delivered-To: isms@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D326E3A68F2 for <isms@core3.amsl.com>; Thu, 16 Sep 2010 09:02:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MX3gbOizjAkB for <isms@core3.amsl.com>; Thu, 16 Sep 2010 09:02:11 -0700 (PDT)
Received: from mail.hardakers.net (hardaker-pt.tunnel.tserv1.fmt.ipv6.he.net [IPv6:2001:470:1f00:ffff::af]) by core3.amsl.com (Postfix) with ESMTP id BEE403A682F for <isms@ietf.org>; Thu, 16 Sep 2010 09:02:10 -0700 (PDT)
Received: from localhost (wjh.hardakers.net [10.0.0.2]) by mail.hardakers.net (Postfix) with ESMTPSA id 68CD39805C; Thu, 16 Sep 2010 09:02:35 -0700 (PDT)
From: Wes Hardaker <wjhns1@hardakers.net>
To: isms@ietf.org
Organization: Sparta
Date: Thu, 16 Sep 2010 09:02:35 -0700
Message-ID: <sd62y5ekx0.fsf@wjh.hardakers.net>
User-Agent: Gnus/5.110011 (No Gnus v0.11) Emacs/23.2 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
Subject: [Isms] SSHTM implementation reports?
X-BeenThere: isms@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mailing list for the ISMS working group <isms.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isms>
List-Post: <mailto:isms@ietf.org>
List-Help: <mailto:isms-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Sep 2010 16:02:11 -0000

David H. pointed out to me recently that there are no implementation
reports for RFC5592 (SSHTM) yet.  Net-SNMP has a partial implementation,
but is not complete enough for us to have written an implementation
report on it.  If there are any implementations of RFC5592, the working
group would of course love to hear about it.

-- 
Wes Hardaker
Cobham Analytic Solutions

From luchuk@snmp.com  Thu Sep 16 11:38:30 2010
Return-Path: <luchuk@snmp.com>
X-Original-To: isms@core3.amsl.com
Delivered-To: isms@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5AC093A6B88 for <isms@core3.amsl.com>; Thu, 16 Sep 2010 11:38:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.586
X-Spam-Level: 
X-Spam-Status: No, score=-0.586 tagged_above=-999 required=5 tests=[AWL=0.154,  BAYES_20=-0.74]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pFBh-h0KN74u for <isms@core3.amsl.com>; Thu, 16 Sep 2010 11:38:25 -0700 (PDT)
Received: from mailbox.snmp.com (mailbox.snmp.com [192.147.142.80]) by core3.amsl.com (Postfix) with ESMTP id D93983A6B42 for <isms@ietf.org>; Thu, 16 Sep 2010 11:38:23 -0700 (PDT)
Received: from sol8.snmp.com (sol8.snmp.com [192.147.142.173]) by mailbox.snmp.com (8.9.3p2-20030922/m.0080228) with ESMTP id OAA27988; Thu, 16 Sep 2010 14:38:30 -0400 (EDT)
Received: from sol8 (localhost [127.0.0.1]) by sol8.snmp.com (8.11.7p1+Sun/8.11.2/snmpclient.mc-011018) with ESMTP id o8GIcTu05922; Thu, 16 Sep 2010 14:38:29 -0400 (EDT)
Message-Id: <201009161838.o8GIcTu05922@sol8.snmp.com>
X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.0.4
To: isms@ietf.org
In-Reply-To: Message from Wes Hardaker <wjhns1@hardakers.net>  of "Wed, 15 Sep 2010 09:26:55 PDT." <sdlj73rn00.fsf@wjh.hardakers.net> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 16 Sep 2010 14:38:29 -0400
From: Alan Luchuk <luchuk@snmp.com>
Cc: reid@snmp.com
Subject: Re: [Isms] RFC5590, 5591 (TSM) and 5953 (TLSTM) interoperability  testing
X-BeenThere: isms@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mailing list for the ISMS working group <isms.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isms>
List-Post: <mailto:isms@ietf.org>
List-Help: <mailto:isms-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Sep 2010 18:38:31 -0000

Hello all,

On Wednesday, September 15 2010, Wes Hardaker <wjhns1@hardakers.net> wrote:

> 
> We are looking for people interested in doing interoperability testing
> for the specifications that make up the set required to implement TLSTM.
> Specifically, we're looking for people, companies or organizations that
> have implemented:
> 
>   5590 Transport Subsystem for the Simple Network Management Protocol
>        (SNMP). D. Harrington, J. Schoenwaelder. June 2009. (Format:
>        TXT=84513 bytes) (Updates RFC3411, RFC3412, RFC3414, RFC3417)
>        (Status: PROPOSED STANDARD)
> 
>   5591 Transport Security Model for the Simple Network Management
>        Protocol (SNMP). D. Harrington, W. Hardaker. June 2009. (Format:
>        TXT=61747 bytes) (Status: PROPOSED STANDARD)
> 
>   5953 Transport Layer Security (TLS) Transport Model for the Simple
>        Network Management Protocol (SNMP). W. Hardaker. August 2010.
>        (Format: TXT=147393 bytes) (Status: PROPOSED STANDARD)
> 
> And ideally this one as well:
> 
>   5343 Simple Network Management Protocol (SNMP) Context EngineID
>        Discovery. J. Schoenwaelder. September 2008. (Format: TXT=19938
>        bytes) (Updates RFC3411) (Status: PROPOSED STANDARD)
> 
> If you have implemented or are currently implementing any of these
> specifications, please let me know so we can coordinate interoperability
> testing with your software, our software (Net-SNMP) and software from
> any other participants that respond to this request.

I've already communicated directly with Wes about interoperability testing, 
but I'd like to let the ISMS WG know that SNMP Research, Incorporated, has
an implementation of these specifications (including RFC 5343).

Regards,
--Alan


---
Alan Luchuk               SNMP Research, Inc            voice: +1 865 573 1434
Senior Software Engineer  3001 Kimberlin Heights Rd.    fax: +1 865 573 9197
luchuk at snmp.com        Knoxville, TN 37920-9716 USA  http://www.snmp.com




From turners@ieca.com  Thu Sep 16 12:23:27 2010
Return-Path: <turners@ieca.com>
X-Original-To: isms@core3.amsl.com
Delivered-To: isms@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 51B4E3A69AB for <isms@core3.amsl.com>; Thu, 16 Sep 2010 12:23:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.291
X-Spam-Level: 
X-Spam-Status: No, score=-102.291 tagged_above=-999 required=5 tests=[AWL=0.307, BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id maDtlESxIdFg for <isms@core3.amsl.com>; Thu, 16 Sep 2010 12:23:26 -0700 (PDT)
Received: from smtp115.biz.mail.mud.yahoo.com (smtp115.biz.mail.mud.yahoo.com [209.191.68.75]) by core3.amsl.com (Postfix) with SMTP id 4A6D03A69A7 for <isms@ietf.org>; Thu, 16 Sep 2010 12:23:26 -0700 (PDT)
Received: (qmail 98815 invoked from network); 16 Sep 2010 19:23:48 -0000
Received: from thunderfish.local (turners@71.191.12.50 with plain) by smtp115.biz.mail.mud.yahoo.com with SMTP; 16 Sep 2010 12:23:48 -0700 PDT
X-Yahoo-SMTP: ZrP3VLSswBDL75pF8ymZHDSu9B.vcMfDPgLJ
X-YMail-OSG: K1kX5jIVM1mWwlwgTylQaDc4SFw7.5f3cwxnaPIq_BfkZTT 1YbGxLMkr8rGSkslHp9Zlp66q0DJueMteIDvSoM7RIXWJfRg86TQ9CyBKC_V XxnUz.OFYgZgnsCVW116BO2uzq6sVYc_oQZglm4ItdFOZoaK0tQzS_Kq0xp_ VRoJqdoVN5YwdW2IgRk8LvIf8YPeEtNV8DrtroGaYgTNDN2oS8O13MZRZHaC tnrGft1BAlS3VxC84pOhZvGaUNxc3mmw3LjEQkEgHgR6vxp7jahbTdrnL8Zl nudC36SaFNZx5xSPm8.xX55k4W2pXralJjLMoZzjCARRhIjW4q_NLuA--
X-Yahoo-Newman-Property: ymail-3
Message-ID: <4C926EC3.5010209@ieca.com>
Date: Thu, 16 Sep 2010 15:23:47 -0400
From: Sean Turner <turners@ieca.com>
User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228)
MIME-Version: 1.0
To: nea@ietf.org, opsawg@ietf.org, netconf@ietf.org, isms@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [Isms] [Fwd: New Non-WG Mailing List: scap_interest -- Discussion List for IETFers interested in the Security Content Automation Protocol (SCAP)]
X-BeenThere: isms@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mailing list for the ISMS working group <isms.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isms>
List-Post: <mailto:isms@ietf.org>
List-Help: <mailto:isms-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Sep 2010 19:23:27 -0000

In case you are not subscribed to the IETF Announce mailing list, I'm 
forwarding this to you (sorry if you get it multiple times).  This 
mailing list will be used to discuss issues related to the SCAP BOF 
(http://trac.tools.ietf.org/bof/trac/).

spt

-------- Original Message --------
Subject: New Non-WG Mailing List: scap_interest -- Discussion List 
for 	IETFers interested in the Security Content Automation Protocol 
(SCAP)
Date: Tue, 14 Sep 2010 13:28:21 -0700 (PDT)
From: IETF Secretariat <ietf-secretariat@ietf.org>
To: IETF Announcement list <ietf-announce@ietf.org>
CC: dave.waltermire@nist.gov, scap_interest@ietf.org

A new IETF non-working group email list has been created.

List address: scap_interest@ietf.org
Archive: http://www.ietf.org/mail-archive/web/scap_interest/
To subscribe: https://www.ietf.org/mailman/listinfo/scap_interest

Description: This list is for discussions relating to the applicability
of the SCAP content formats to current and emerging IETF protocols.
Current SCAP specifications and Internet use scenarios are in scope for
this discussion list. Current SCAP specifications include the Common
Configuration Enumeration (CCE), Common Vulnerability Evaluation (CVE),
Common Platform Enumeration (CPM), Open Vulnerability and Assessment
Language (OVAL), and Extensible Configuration Checklist Description Format
(XCCDF).

For additional information, please contact the list administrators.
_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce


From j.schoenwaelder@jacobs-university.de  Thu Sep 16 23:23:28 2010
Return-Path: <j.schoenwaelder@jacobs-university.de>
X-Original-To: isms@core3.amsl.com
Delivered-To: isms@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D0C943A688C for <isms@core3.amsl.com>; Thu, 16 Sep 2010 23:23:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.249
X-Spam-Level: 
X-Spam-Status: No, score=-102.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zrcvM9dHvcvx for <isms@core3.amsl.com>; Thu, 16 Sep 2010 23:23:27 -0700 (PDT)
Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) by core3.amsl.com (Postfix) with ESMTP id 705973A6879 for <isms@ietf.org>; Thu, 16 Sep 2010 23:23:27 -0700 (PDT)
Received: from localhost (demetrius4.jacobs-university.de [212.201.44.49]) by hermes.jacobs-university.de (Postfix) with ESMTP id 0BE85C00C7 for <isms@ietf.org>; Fri, 17 Sep 2010 08:23:52 +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 ke9CNwkFz6Bf for <isms@ietf.org>; Fri, 17 Sep 2010 08:23:51 +0200 (CEST)
Received: from elstar.local (elstar.iuhb02.iu-bremen.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id 1C7FEC006B for <isms@ietf.org>; Fri, 17 Sep 2010 08:23:51 +0200 (CEST)
Received: by elstar.local (Postfix, from userid 501) id 288AA14DC284; Fri, 17 Sep 2010 08:23:26 +0200 (CEST)
Resent-From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
Resent-Date: Fri, 17 Sep 2010 08:23:26 +0200
Resent-Message-ID: <20100917062326.GA46580@elstar.local>
Resent-To: isms@ietf.org
Received: from SHUBCAS03.jacobs.jacobs-university.de (10.70.0.128) by SHUBCAS01.jacobs.jacobs-university.de (10.70.0.122) with Microsoft SMTP Server (TLS) id 8.2.254.0; Fri, 17 Sep 2010 01:27:20 +0200
Received: from hermes.jacobs-university.de (212.201.44.23) by shubcas03.jacobs.jacobs-university.de (10.70.0.128) with Microsoft SMTP Server id 14.1.218.12; Fri, 17 Sep 2010 01:27:20 +0200
Received: from atlas1.jacobs-university.de (atlas1a.jacobs-university.de [212.201.44.13])	by hermes.jacobs-university.de (Postfix) with ESMTP id 1C9AFC0069	for <j.schoenwaelder@jacobs-university.de>; Fri, 17 Sep 2010 01:27:20 +0200 (CEST)
Received: from localhost (demetrius2.jacobs-university.de [212.201.44.47])	by atlas1.jacobs-university.de (Postfix) with ESMTP id 0DA39419	for <j.schoenwaelder@jacobs-university.de>; Fri, 17 Sep 2010 01:27:20 +0200 (CEST)
Received: from atlas1b.jacobs-university.de ([212.201.44.13])	by localhost (demetrius2.jacobs-university.de [212.201.44.47]) (amavisd-new, port 10030) with ESMTP id jSV6Jegs+w+G for <j.schoenwaelder@jacobs-university.de>; Fri, 17 Sep 2010 01:27:18 +0200 (CEST)
Received: from mail.ietf.org (mail.ietf.org [64.170.98.32])	by atlas1b.jacobs-university.de (Postfix) with ESMTP	for <j.schoenwaelder@jacobs-university.de>; Fri, 17 Sep 2010 01:27:18 +0200 (CEST)
Received: from [127.0.0.1] (localhost [127.0.0.1])	by core3.amsl.com (Postfix) with ESMTP id AE35D3A6ABB;	Thu, 16 Sep 2010 16:26:05 -0700 (PDT)
Received: by core3.amsl.com (Postfix, from userid 30)	id BE4603A69FC; Thu, 16 Sep 2010 16:26:02 -0700 (PDT)
From: NomCom Chair <nomcom-chair@ietf.org>
To: IETF Announcement list <ietf-announce@ietf.org>
Sender: "ietf-announce-bounces@ietf.org" <ietf-announce-bounces@ietf.org>
Date: Fri, 17 Sep 2010 01:26:02 +0200
Thread-Topic: NomCom 2010-2011: Call for More Nominations 
Thread-Index: ActV9rWQOKzmJTsZT9iBKlG7a0p9HA==
Message-ID: <20100916232602.BE4603A69FC@core3.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Exchange-Organization-AuthAs: Anonymous
X-MS-Exchange-Organization-AuthSource: SHUBCAS03.jacobs.jacobs-university.de
X-MS-Has-Attach: yes
X-Auto-Response-Suppress: All
X-MS-TNEF-Correlator: 
x-beenthere: ietf-announce@ietf.org
x-original-to: ietf-announce@ietf.org
x-mailman-version: 2.1.9
errors-to: ietf-announce-bounces@ietf.org
x-virus-scanned: amavisd-new at jacobs-university.de
delivered-to: ietf-announce@core3.amsl.com
x-jacobsispwhitelisted: med ietf.org DNSWLId 1703
Content-Type: multipart/mixed; boundary="_002_20100916232602BE4603A69FCcore3amslcom_"
MIME-Version: 1.0
Subject: [Isms] NomCom 2010-2011: Call for More Nominations
X-BeenThere: isms@ietf.org
Precedence: list
List-Id: Mailing list for the ISMS working group <isms.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isms>
List-Post: <mailto:isms@ietf.org>
List-Help: <mailto:isms-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Sep 2010 06:23:28 -0000

--_002_20100916232602BE4603A69FCcore3amslcom_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

DQoNCkhpIEZvbGtzLA0KDQpOb21pbmF0aW9ucyBoYXZlIHNsb3dlZCBkb3duIGRyYW1hdGljYWxs
eSwgc28gdGhpcyB1cGRhdGUgaXMgdG8gZW5saXN0IA0KdGhlIGNvbW11bml0eSBpbiBhbiBlZmZv
cnQgdG8gcGljayB1cCB0aGUgcGFjZS4gDQoNCldlIGFyZSB2ZXJ5IGZhciBiZWhpbmQgaW4gbm9t
aW5hdGlvbnMgZm9yIGFsbCB0aGUgb3BlbiBwb3NpdGlvbnMgYnV0IGluIA0KcGFydGljdWxhciB3
ZSBuZWVkIG5vbWluYXRpb25zIGZvciB0aGUgSUVTRyBhbmQgSUFPQyBvcGVuIHBvc2l0aW9ucy4g
DQpUaGVyZSBoYXZlIGJlZW4gbm8gbm9taW5hdGlvbnMgcmVjZWl2ZWQgKG90aGVyIHRoYW4gZm9y
IHRoZSBpbmN1bWJlbnRzKSANCmluIElOVCwgUkFJLCBhbmQgUlRHLCBhbmQgb25seSAxIGZvciBP
UFMuICBMaWtld2lzZSwgaW4gSUFPQyB0aGVyZSBoYXZlIA0KYmVlbiBubyBub21pbmF0aW9ucyBz
dWJtaXR0ZWQgb3RoZXIgdGhhbiB0aGUgaW5jdW1iZW50Lg0KDQpUaGUgYWNjZXB0YW5jZSByYXRl
cyBvZiB0aG9zZSBub21pbmF0ZWQgaGFzIGFsc28gYmVlbiB2ZXJ5IHNsb3cuIEluIA0Kb3JkZXIg
dG8gaW5pdGlhdGUgdGhlIG9wZW4gbGlzdCBvZiB3aWxsaW5nIG5vbWluZWVzIHdlIGFyZSBpbiBu
ZWVkIG9mIGEgDQpyZWFzb25hYmxlIG51bWJlciBvZiBhY2NlcHRhbmNlcywgYW5kIGR1ZSB0byB0
aGUgbG93IG51bWJlciBvZiBub21pbmVlcyANCmFuZCBhY2NlcHRhbmNlcyBoYXZlIGRlbGF5ZWQg
dGhlIHN0YXJ0IGRhdGUgZm9yIHB1Ymxpc2hpbmcgdGhlIGZpcnN0IA0Kb3BlbiBsaXN0IHRvIFNl
cHRlbWJlciAyMC4gIFNvIGlmIHlvdSBoYXZlIGJlZW4gbm9taW5hdGVkIGFuZCBhcmUgDQp3aWxs
aW5nIHRvIHNlcnZlLCBidXQgaGF2ZSBub3QgeWV0IGNvbmZpcm1lZCB0aGlzIGJ5IGVtYWlsIGJh
Y2sgdG8gdGhlIA0KTm9tQ29tLCBwbGVhc2UgZG8gc28gYXMgc29vbiBhcyBwb3NzaWJsZS4NCg0K
V2UgbmVlZCBDb21tdW5pdHkgaW5wdXQgYW5kIHBhcnRpY2lwYXRpb24hIFdlIGNhbm5vdCBwcm9w
ZXJseSBleGVjdXRlIA0KdGhlIHRhc2sgb2Ygc2VsZWN0aW5nIHRoZSBiZXN0IGNhbmRpZGF0ZXMg
Zm9yIHRoZXNlIHBvc2l0aW9ucyB3aXRoIHNvIA0KZmV3IG5vbWluYXRpb25zIGFuZCBhY2NlcHRh
bmNlcy4gU28sIHBsZWFzZSBjb25zaWRlciBtYWtpbmcgDQpub21pbmF0aW9ucyBmb3IgdGhlIG9w
ZW4gcG9zaXRpb25zLCBpbiBwYXJ0aWN1bGFyIHRob3NlIGZvciB3aGljaCB3ZSANCmhhdmUgc28g
ZmV3IG5vbWluYXRpb25zIO+/vSBpdCB0YWtlcyBqdXN0IGEgZmV3IG1pbnV0ZXMgb2YgeW91ciB0
aW1lLiANClJpZ2h0IG5vdywgd2UganVzdCBuZWVkIHRoZSBuYW1lcy9lbWFpbCBhZGRyZXNzZXMu
DQoNCldoeSBkbyB3ZSBuZWVkIG1vcmUgbm9taW5hdGlvbnM/ICBXZWxsLCBldmVuIGlmIHlvdSB0
aGluayBhIHdpbGxpbmcNCmluY3VtYmVudCBpcyBkb2luZyBhIHZlcnkgZ29vZCBqb2IgYW5kIHNo
b3VsZCBiZSByZXR1cm5lZCwgaGlzIG9yIGhlcg0KYWJpbGl0eSB0byBzZXJ2ZSBhZ2FpbiBtaWdo
dCBiZSBpbXBhY3RlZCBieSB1bmZvcmVzZWVuIGNpcmN1bXN0YW5jZXMNCmJldHdlZW4gbm93IGFu
ZCBNYXJjaC4gTm9tQ29tIG5lZWRzIHRvIGNvbnNpZGVyIG11bHRpcGxlIG5vbWluZWVzIHRvIGJl
DQpwcmVwYXJlZCBpbiB0aGUgZXZlbnQgb25lIG9yIG1vcmUgY2FuZGlkYXRlcyBpcyB1bmFibGUg
dG8gc2VydmUgY29tZSBuZXh0DQpNYXJjaCBhbmQgdG8gZW5zdXJlIHdlIGhhdmUgY2hvc2VuIHRo
ZSBiZXN0IGNhbmRpZGF0ZS4gDQoNClRoZXJlIGFyZSBzZXZlcmFsIHdheXMgeW91IGNhbiBoZWxw
IHRoZSBJRVRGIE5vbWluYXRpbmcgQ29tbWl0dGVlLg0KDQotIFlvdSBtYXkgbm9taW5hdGUgeW91
cnNlbGYuDQotIFlvdSBjYW4gbm9taW5hdGUgc29tZW9uZSB5b3Uga25vdyB3aG9tIHlvdSB0aGlu
ayB3b3VsZCBkbyBhIGdvb2Qgam9iLg0KDQpEbyBub3Qgd29ycnkgYWJvdXQgd2hldGhlciB0aGV5
IG1pZ2h0IGFscmVhZHkgYmUgbm9taW5hdGVkLiBXZSB3b3VsZCANCm11Y2ggcHJlZmVyIHRvIHJl
Y2VpdmUgdGhlIHNhbWUgbm9taW5hdGlvbiBzZXZlcmFsIHRpbWVzIHJhdGhlciB0aGFuIA0KbWlz
cyBhIGdvb2QgcGVyc29uIHdlIHNob3VsZCBjb25zaWRlci4NCg0KSG93IHRvIHN1Ym1pdCBOb21p
bmF0aW9uczoNCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQpUaGUgbGlzdCBvZiBwb3NpdGlv
bnMgd2UgbmVlZCB0byBmaWxsLCBhbmQgdGhlIHByb3ZpZGVkIEpvYiANCkRlc2NyaXB0aW9ucywg
YW5kIGZvcm1zIGZvciBub21pbmF0aW9ucywgY2FuIGJlIGZvdW5kIGluIHRoZSBjYWxsIGZvciAN
Cm5vbWluYXRpb25zIGF0OiBodHRwczovL2RhdGF0cmFja2VyLmlldGYub3JnL2Fubi9ub21jb20v
MjQ2OC8gDQoNCllvdSBtYXkgZW50ZXIgYSBub21pbmF0aW9uIGJ5IGdvaW5nIHRvIHRoZSBmb2xs
b3dpbmcgVVJMIA0KaHR0cHM6Ly93aWtpLnRvb2xzLmlldGYub3JnL2dyb3VwL25vbWNvbS8xMC9u
b21pbmF0ZQ0KDQpZb3UgbWF5IGFsc28gbm9taW5hdGUgc29tZW9uZSBieSBzZW5kaW5nIGFuIGVt
YWlsIHRvIG5vbWNvbTEwQGlldGYub3JnIA0KYW5kIGdpdmluZyB1cyB0aGVpciBuYW1lLCBlbWFp
bCBhZGRyZXNzIGFuZCB0aGUgb3BlbiBwb3NpdGlvbiB5b3UgYXJlIA0Kbm9taW5hdGluZyB0aGVt
IGZvci4gV2Ugd2lsbCB0YWtlIGNhcmUgb2YgdGhlIHJlc3QuIA0KDQpJZiB5b3UgYXJlIGFza2Vk
IGZvciBhIHVzZXIgbmFtZSBhbmQgcGFzc3dvcmQsIHVzZSBhbiBleGlzdGluZyBpZXRmIGxvZ2lu
DQphbmQgcGFzc3dvcmQuIElmIHlvdSBuZWVkIGEgbG9naW4gYW5kIHBhc3N3b3JkLCByZXF1ZXN0
IG9uZSBmcm9tIHRoZSB0b29scw0KcGFnZSBhdCB0aGUgZm9sbG93aW5nIFVSTCBodHRwOi8vdHJh
Yy50b29scy5pZXRmLm9yZy9uZXdsb2dpbg0KDQoNCk9wZW4gTGlzdDoNCi0tLS0tLS0tLS0NCkFz
IHlvdSBhbHJlYWR5IGtub3csIE5vbUNvbSAyMDEwLTIwMTEgd2lsbCBmb2xsb3cgdGhlIHBvbGlj
eSBmb3IgIk9wZW4gDQpEaXNjbG9zdXJlIG9mIFdpbGxpbmcgTm9taW5lZXMiIGRlc2NyaWJlZCBp
biBSRkMgNTY4MC4NCg0KRmVlZGJhY2sgQ29sbGVjdGlvbjoNCi0tLS0tLS0tLS0tLS0tLS0tLS0t
DQpPbmNlIHRoZSBvcGVuIGxpc3QgaXMgYXZhaWxhYmxlLCB0aGUgZW50aXJlIGNvbW11bml0eSB3
aWxsIGJlIGludml0ZWQgDQp0byBwcm92aWRlIGZlZWRiYWNrLiBJIHdpbGwgc2VuZCBhIGZ1cnRo
ZXIgYW5ub3VuY2VtZW50IHJlcXVlc3RpbmcgDQpmZWVkYmFjayBvbiB0aGUgbm9taW5lZXMsIGRl
c2NyaWJpbmcgaG93IHRvIHN1Ym1pdCBmZWVkYmFjaywgYW5kIGhvdyB0byANCnZpZXcgdGhlIG9w
ZW4gbGlzdCBvZiBub21pbmVlcy4gDQoNClRoYW5rIHlvdSwNCg0KVGhvbWFzIFdhbHNoDQpDaGFp
ciwgTm9tQ29tIDIwMTAtMjAxMQ0Kbm9tY29tLWNoYWlyQGlldGYub3JnDQp0d2Fsc2hAanVuaXBl
ci5uZXQNCg0KDQoNCg==

--_002_20100916232602BE4603A69FCcore3amslcom_
Content-Type: text/plain; name="ATT00001..txt"
Content-Description: ATT00001..txt
Content-Disposition: attachment; filename="ATT00001..txt"; size=218;
	creation-date="Fri, 17 Sep 2010 01:27:20 GMT";
	modification-date="Fri, 17 Sep 2010 01:27:20 GMT"
Content-Transfer-Encoding: base64

X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCklFVEYtQW5u
b3VuY2UgbWFpbGluZyBsaXN0DQpJRVRGLUFubm91bmNlQGlldGYub3JnDQpodHRwczovL3d3dy5p
ZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2lldGYtYW5ub3VuY2UNCg==

--_002_20100916232602BE4603A69FCcore3amslcom_--

From j.schoenwaelder@jacobs-university.de  Fri Sep 17 01:20:45 2010
Return-Path: <j.schoenwaelder@jacobs-university.de>
X-Original-To: isms@core3.amsl.com
Delivered-To: isms@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 365003A677E for <isms@core3.amsl.com>; Fri, 17 Sep 2010 01:20:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.231
X-Spam-Level: 
X-Spam-Status: No, score=-101.231 tagged_above=-999 required=5 tests=[AWL=-0.471, BAYES_05=-1.11, HELO_EQ_DE=0.35, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OR4jqZy68lXE for <isms@core3.amsl.com>; Fri, 17 Sep 2010 01:20:41 -0700 (PDT)
Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) by core3.amsl.com (Postfix) with ESMTP id D434B3A6BD8 for <isms@ietf.org>; Fri, 17 Sep 2010 01:20:40 -0700 (PDT)
Received: from localhost (demetrius3.jacobs-university.de [212.201.44.48]) by hermes.jacobs-university.de (Postfix) with ESMTP id 6CBE2C051E for <isms@ietf.org>; Fri, 17 Sep 2010 10:21:05 +0200 (CEST)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius3.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id t-zqC57H61ef; Fri, 17 Sep 2010 10:21:05 +0200 (CEST)
Received: from elstar.local (elstar.iuhb02.iu-bremen.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id C303EC0517; Fri, 17 Sep 2010 10:21:04 +0200 (CEST)
Received: by elstar.local (Postfix, from userid 501) id C72FD14DC635; Fri, 17 Sep 2010 10:20:39 +0200 (CEST)
Date: Fri, 17 Sep 2010 10:20:39 +0200
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: isms@ietf.org
Message-ID: <20100917082039.GA47046@elstar.local>
Mail-Followup-To: isms@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.20 (2009-06-14)
Subject: [Isms] status and future of the isms working group
X-BeenThere: isms@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
List-Id: Mailing list for the ISMS working group <isms.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isms>
List-Post: <mailto:isms@ietf.org>
List-Help: <mailto:isms-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Sep 2010 08:20:45 -0000

Hi,

as you might have noticed, the last chartered WG document has been
approved by the IESG yesterday. I like to thank our document editors
and everybody who contributed to the development of this document.

The ISMS working started in 2004 to address the concern raised by
operators that using USM with its own key management scheme is costly.
The WG produced 6 RFCs (one still in the RFC editor queue) detailing:

- a transport subsystem of the RFC 3411 SNMP architecture
- a new transport security model supporting multiple secure transports
- an SSH secure transport model
- a DTLS/TLS secure transprot model
- the usage of RADIUS for session authorization
- the usage of RADIUS to provision VACM user to group mappings

This pretty much completes the mission of this WG and the natural next
step would be to close down this working group once the RFCs all have
appeared.

However, there might also be well justified reasons to keep the WG
running. One of them could be the advancement of some RFCs to Draft
standard. See section 4.1.2 of RFC 2026 for the detailed requirements
of a Draft standard. Please let the chairs know if you think the WG
should untertake such an activity. Please also mention whether you can
contribute implementation reports, provide interoperability tests, can
help with any document editing that might be needed etc.

If you think some other work should be undertaken by this WG, people
start a thread on the mailing list where you propose the work to be
done and where we can get a discussion going to see how much support
there is in the WG and how many people are willing to commit to help
with document editing and document reviewing tasks. As we have learned
here several times, writing SNMP specifications is not an easy task
given the architectural and terminology framework we are working
with. It is thus crucial to have sufficient people involved in the
reviewing and wordsmithing as well as the work needed to originally
produce and edit the specifications.

/js

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

From ietfdbh@comcast.net  Fri Sep 17 02:58:36 2010
Return-Path: <ietfdbh@comcast.net>
X-Original-To: isms@core3.amsl.com
Delivered-To: isms@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D01CB3A6C0F for <isms@core3.amsl.com>; Fri, 17 Sep 2010 02:58:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.232
X-Spam-Level: 
X-Spam-Status: No, score=-102.232 tagged_above=-999 required=5 tests=[AWL=0.367, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DjPv-3YZgSiM for <isms@core3.amsl.com>; Fri, 17 Sep 2010 02:58:34 -0700 (PDT)
Received: from qmta03.westchester.pa.mail.comcast.net (qmta03.westchester.pa.mail.comcast.net [76.96.62.32]) by core3.amsl.com (Postfix) with ESMTP id 848233A6BCC for <isms@ietf.org>; Fri, 17 Sep 2010 02:58:34 -0700 (PDT)
Received: from omta19.westchester.pa.mail.comcast.net ([76.96.62.98]) by qmta03.westchester.pa.mail.comcast.net with comcast id 7ln01f00327AodY53lz0DR; Fri, 17 Sep 2010 09:59:00 +0000
Received: from 23FX1C1 ([67.189.235.106]) by omta19.westchester.pa.mail.comcast.net with comcast id 7lyy1f0052JQnJT3flyzDN; Fri, 17 Sep 2010 09:59:00 +0000
From: "David Harrington" <ietfdbh@comcast.net>
To: "'Juergen Schoenwaelder'" <j.schoenwaelder@jacobs-university.de>, <isms@ietf.org>
References: <20100917082039.GA47046@elstar.local>
Date: Fri, 17 Sep 2010 05:57:31 -0400
Message-ID: <CCBEBEBD3ED849FCA53890C5792FD42B@23FX1C1>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.5994
Thread-index: ActWQUrrlxPbOHJOTbaxB1GkR9MNggABogLw
In-Reply-To: <20100917082039.GA47046@elstar.local>
Cc: Ron Bonica <rbonica@juniper.net>
Subject: Re: [Isms] status and future of the isms working group
X-BeenThere: isms@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mailing list for the ISMS working group <isms.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isms>
List-Post: <mailto:isms@ietf.org>
List-Help: <mailto:isms-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Sep 2010 09:58:36 -0000

Hi,

I would like to take this opportunity to thank this working group.
I enjoyed working with all of you getting these specifications
produced. 
Juergen, thank you for providing a steady helm for a fairly turbulent
journey.

I have two suggestions for further ISMS work.

1) I think gathering implementation reports can be a good thing. I am
not sure how much having a document advance to Draft Standard is
important in the real world, but implementation reports could help
vendors decide which specfications to support in their products, and
possibly which toolkits might be useful in their product engineering.
So I do encourage this activity.

2) As you observe, and as I have experienced as an ISMS editor, it is
not easy writing SNMP specifications; the RFC 3411 architecture is
rather difficult to work with. Comparing the SNMP/TLS document with
the SYSLOG/TLS or Netconf/TLS documents readily shows that the SNMP
architecture adds tremedous complexity to IETF specifications for
SNMP. I believe this complexity makes maintaining and/or extending
SNMP far more difficult than is justified by the benefits of the RFC
3411 architecture in SNMP standards development.

RFC 3411 was very explicitly "AN" architecture for describing SNMP
frameworks. It was never meant to be "THE" mandatory architecture for
SNMP frameworks. It was written to be highly modular largely because
there were many demands for different designs by different segments of
the industry. During the "SNMP wars", there was tremendous acrimony,
and many people unwilling to compromise on their demands for various
design decisions, such as simplicity versus additional features. The
RFC3411 modular architecture allowed the SNMP community to develop
models following the 90/10 rule; we produced standard models that
addressed the most common demands, and allowed for subsequent
development of additional models to meet the demands of specific
industry segments. Additional models to meet the specific demands
identified at that time never materialized. But we have been burdened
with the RFC 3411 architecture, and its Abstract Service Interfaces,
ever since.

I would like to recommend a new work item for ISMS - design a new
architecture standard for SNMP development. 
I recommend developing "A Simple Architecture for Describing SNMP
Frameworks" that is more consistent with the simpler layered
architectural models used for Netconf [RFC 4741, section 1.1] and
Syslog [RFC 5424 section 3], to bring simplicity back into SNMP
standards development. 

This should be accompanied by an update to RFC 3410 that would include
discussion of the simpler architecture, secure transport, engineID
discovery, RADIUS support, syslog-snmp mappings, and the SMI-XML
datatypes. There has been lots of work in SNMP that is not reflected
in RFC 3410. Since RFC3410 is "Introduction and Applicability
Statements for Internet-Standard Management Framework", this update
might also discuss the comparative applicability of SNMP, Netconf,
Syslog, and Ipfix standards.

I do not have the time to edit such documents, but would be willing to
provide reviews for such an effort.

David Harrington
Director, IETF Transport Area
ietfdbh@comcast.net (preferred for ietf)
dbharrington@huaweisymantec.com
+1 603 828 1401 (cell)

> -----Original Message-----
> From: isms-bounces@ietf.org [mailto:isms-bounces@ietf.org] On 
> Behalf Of Juergen Schoenwaelder
> Sent: Friday, September 17, 2010 4:21 AM
> To: isms@ietf.org
> Subject: [Isms] status and future of the isms working group
> 
> Hi,
> 
> as you might have noticed, the last chartered WG document has 
> been approved by the IESG yesterday. I like to thank our 
> document editors and everybody who contributed to the 
> development of this document.
> 
> The ISMS working started in 2004 to address the concern 
> raised by operators that using USM with its own key 
> management scheme is costly.
> The WG produced 6 RFCs (one still in the RFC editor queue)
detailing:
> 
> - a transport subsystem of the RFC 3411 SNMP architecture
> - a new transport security model supporting multiple secure
transports
> - an SSH secure transport model
> - a DTLS/TLS secure transprot model
> - the usage of RADIUS for session authorization
> - the usage of RADIUS to provision VACM user to group mappings
> 
> This pretty much completes the mission of this WG and the 
> natural next step would be to close down this working group 
> once the RFCs all have appeared.
> 
> However, there might also be well justified reasons to keep 
> the WG running. One of them could be the advancement of some 
> RFCs to Draft standard. See section 4.1.2 of RFC 2026 for the 
> detailed requirements of a Draft standard. Please let the 
> chairs know if you think the WG should untertake such an 
> activity. Please also mention whether you can contribute 
> implementation reports, provide interoperability tests, can 
> help with any document editing that might be needed etc.
> 
> If you think some other work should be undertaken by this WG, 
> people start a thread on the mailing list where you propose 
> the work to be done and where we can get a discussion going 
> to see how much support there is in the WG and how many 
> people are willing to commit to help with document editing 
> and document reviewing tasks. As we have learned here several 
> times, writing SNMP specifications is not an easy task given 
> the architectural and terminology framework we are working 
> with. It is thus crucial to have sufficient people involved 
> in the reviewing and wordsmithing as well as the work needed 
> to originally produce and edit the specifications.
> 
> /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/>
> _______________________________________________
> Isms mailing list
> Isms@ietf.org
> https://www.ietf.org/mailman/listinfo/isms


From j.schoenwaelder@jacobs-university.de  Fri Sep 17 03:11:08 2010
Return-Path: <j.schoenwaelder@jacobs-university.de>
X-Original-To: isms@core3.amsl.com
Delivered-To: isms@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 682A03A68B8 for <isms@core3.amsl.com>; Fri, 17 Sep 2010 03:11:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.972
X-Spam-Level: 
X-Spam-Status: No, score=-101.972 tagged_above=-999 required=5 tests=[AWL=0.277, BAYES_00=-2.599, HELO_EQ_DE=0.35, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2Pf1XALsitAC for <isms@core3.amsl.com>; Fri, 17 Sep 2010 03:11:07 -0700 (PDT)
Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) by core3.amsl.com (Postfix) with ESMTP id EF12C3A688C for <isms@ietf.org>; Fri, 17 Sep 2010 03:11:06 -0700 (PDT)
Received: from localhost (demetrius3.jacobs-university.de [212.201.44.48]) by hermes.jacobs-university.de (Postfix) with ESMTP id 830CDC0092; Fri, 17 Sep 2010 12:11:31 +0200 (CEST)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius3.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id 89VFHOWBQjC9; Fri, 17 Sep 2010 12:11:31 +0200 (CEST)
Received: from elstar.local (elstar.iuhb02.iu-bremen.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id 6715AC0102; Fri, 17 Sep 2010 12:11:27 +0200 (CEST)
Received: by elstar.local (Postfix, from userid 501) id 5AA4A14DCAC5; Fri, 17 Sep 2010 12:11:03 +0200 (CEST)
Date: Fri, 17 Sep 2010 12:11:02 +0200
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: David Harrington <ietfdbh@comcast.net>
Message-ID: <20100917101102.GA47610@elstar.local>
Mail-Followup-To: David Harrington <ietfdbh@comcast.net>, "isms@ietf.org" <isms@ietf.org>, "'ext Romascanu, Dan (Dan)'" <dromasca@avaya.com>, Ron Bonica <rbonica@juniper.net>
References: <20100917082039.GA47046@elstar.local> <CCBEBEBD3ED849FCA53890C5792FD42B@23FX1C1>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CCBEBEBD3ED849FCA53890C5792FD42B@23FX1C1>
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: "isms@ietf.org" <isms@ietf.org>, Ron Bonica <rbonica@juniper.net>
Subject: Re: [Isms] status and future of the isms working group
X-BeenThere: isms@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
List-Id: Mailing list for the ISMS working group <isms.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isms>
List-Post: <mailto:isms@ietf.org>
List-Help: <mailto:isms-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Sep 2010 10:11:08 -0000

On Fri, Sep 17, 2010 at 11:57:31AM +0200, David Harrington wrote:
 
> I would like to recommend a new work item for ISMS - design a new
> architecture standard for SNMP development. 
> I recommend developing "A Simple Architecture for Describing SNMP
> Frameworks" that is more consistent with the simpler layered
> architectural models used for Netconf [RFC 4741, section 1.1] and
> Syslog [RFC 5424 section 3], to bring simplicity back into SNMP
> standards development. 

ISMS stands for "Integrated Security Model for SNMP" and it seems the
work you are proposing really calls for a different working group,
likely located in the OPS area not in the security area (as can be
seen by the ADs you have put on the CC).

/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 lear@cisco.com  Fri Sep 17 06:47:44 2010
Return-Path: <lear@cisco.com>
X-Original-To: isms@core3.amsl.com
Delivered-To: isms@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DDA713A694D for <isms@core3.amsl.com>; Fri, 17 Sep 2010 06:47:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -108.799
X-Spam-Level: 
X-Spam-Status: No, score=-108.799 tagged_above=-999 required=5 tests=[AWL=1.800, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q-ThqQJ07lNQ for <isms@core3.amsl.com>; Fri, 17 Sep 2010 06:47:43 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id 92E1D3A696D for <isms@ietf.org>; Fri, 17 Sep 2010 06:47:43 -0700 (PDT)
Authentication-Results: ams-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EADMOk0yQ/khM/2dsb2JhbACDG58HcaYpigaST4EigytzBIoz
X-IronPort-AV: E=Sophos;i="4.56,382,1280707200"; d="scan'208";a="64599780"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-1.cisco.com with ESMTP; 17 Sep 2010 13:48:07 +0000
Received: from ams3-vpn-dhcp4342.cisco.com (ams3-vpn-dhcp4342.cisco.com [10.61.80.245]) by ams-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id o8HDm7nb017826; Fri, 17 Sep 2010 13:48:07 GMT
Message-ID: <4C9371A6.6040106@cisco.com>
Date: Fri, 17 Sep 2010 15:48:22 +0200
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.9) Gecko/20100825 Lightning/1.0b2 Thunderbird/3.1.3
MIME-Version: 1.0
To: David Harrington <ietfdbh@comcast.net>, "isms@ietf.org" <isms@ietf.org>, "'ext Romascanu, Dan (Dan)'" <dromasca@avaya.com>, Ron Bonica <rbonica@juniper.net>
References: <20100917082039.GA47046@elstar.local>	<CCBEBEBD3ED849FCA53890C5792FD42B@23FX1C1> <20100917101102.GA47610@elstar.local>
In-Reply-To: <20100917101102.GA47610@elstar.local>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: Re: [Isms] status and future of the isms working group
X-BeenThere: isms@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mailing list for the ISMS working group <isms.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isms>
List-Post: <mailto:isms@ietf.org>
List-Help: <mailto:isms-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Sep 2010 13:47:45 -0000

 While I agree with Juergen on the logistics, I think Dave highlights
interesting work to consider undertaking.  My only concern is that it
seems like people have tried to do this before, in particular in the
NMRG.  What's the trigger for success?

Eliot

On 9/17/10 12:11 PM, Juergen Schoenwaelder wrote:
> On Fri, Sep 17, 2010 at 11:57:31AM +0200, David Harrington wrote:
>  
>> I would like to recommend a new work item for ISMS - design a new
>> architecture standard for SNMP development. 
>> I recommend developing "A Simple Architecture for Describing SNMP
>> Frameworks" that is more consistent with the simpler layered
>> architectural models used for Netconf [RFC 4741, section 1.1] and
>> Syslog [RFC 5424 section 3], to bring simplicity back into SNMP
>> standards development. 
> ISMS stands for "Integrated Security Model for SNMP" and it seems the
> work you are proposing really calls for a different working group,
> likely located in the OPS area not in the security area (as can be
> seen by the ADs you have put on the CC).
>
> /js
>

From ietfdbh@comcast.net  Fri Sep 17 07:25:26 2010
Return-Path: <ietfdbh@comcast.net>
X-Original-To: isms@core3.amsl.com
Delivered-To: isms@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6DBBC3A6407 for <isms@core3.amsl.com>; Fri, 17 Sep 2010 07:25:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.233
X-Spam-Level: 
X-Spam-Status: No, score=-102.233 tagged_above=-999 required=5 tests=[AWL=0.366, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2tLuiHBImiLM for <isms@core3.amsl.com>; Fri, 17 Sep 2010 07:25:25 -0700 (PDT)
Received: from QMTA11.westchester.pa.mail.comcast.net (qmta11.westchester.pa.mail.comcast.net [76.96.59.211]) by core3.amsl.com (Postfix) with ESMTP id 541BC3A659C for <isms@ietf.org>; Fri, 17 Sep 2010 07:25:25 -0700 (PDT)
Received: from omta22.westchester.pa.mail.comcast.net ([76.96.62.73]) by QMTA11.westchester.pa.mail.comcast.net with comcast id 7nbJ1f0041ap0As5BqRqtP; Fri, 17 Sep 2010 14:25:50 +0000
Received: from 23FX1C1 ([67.189.235.106]) by omta22.westchester.pa.mail.comcast.net with comcast id 7qRq1f00F2JQnJT3iqRq31; Fri, 17 Sep 2010 14:25:50 +0000
From: "David Harrington" <ietfdbh@comcast.net>
To: "'Eliot Lear'" <lear@cisco.com>, <isms@ietf.org>, "'ext Romascanu, Dan \(Dan\)'" <dromasca@avaya.com>, "'Ron Bonica'" <rbonica@juniper.net>
References: <20100917082039.GA47046@elstar.local>	<CCBEBEBD3ED849FCA53890C5792FD42B@23FX1C1> <20100917101102.GA47610@elstar.local> <4C9371A6.6040106@cisco.com>
Date: Fri, 17 Sep 2010 10:24:15 -0400
Message-ID: <DC81494673134E448B019A3F0A41166B@23FX1C1>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.5994
Thread-index: ActWbvZeAeOpshHYQ2+hxVH16c11fQAAjwQQ
In-Reply-To: <4C9371A6.6040106@cisco.com>
Subject: Re: [Isms] status and future of the isms working group
X-BeenThere: isms@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mailing list for the ISMS working group <isms.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isms>
List-Post: <mailto:isms@ietf.org>
List-Help: <mailto:isms-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Sep 2010 14:25:26 -0000

Hi,

NMRG worked on information/data models (RFC3444) and XML-based NM
(e.g., through proxies).

I don't believe NMRG ever tried to write a new SNMP architecture
document.
and in the IETF, WGs have been told that modifying the RFC 3411
architecture is definitely out of scope. 
The EOS and SMING and ISMS WGs were all told to "work within" the
RFC3411 architecture.
I think that restriction was part (but only part) of the reason for
the failures of EOS and SMING.
We only got to modify the architecture in ISMS when we needed to
define a transport subsystem in rfc5590.
So I don't agree this has been tried before.

I think SNMP could be brought out of the 1980's, but first we need to
make it easier to add new features, such as new operations, and new
data modeling approaches. I think the RFC3411 architecture makes it so
hard to write any extensions, even models that fit within the RFC3411
architecture, that it greatly increases the complexity. 
A simpler architecture would allow SNMP to be maintained and updated
more easily.

Netconf can certainly do some of the things that an extended SNMP
might, but netconf is designed for a different usage scenario. I
certainly would think twice about using Netconf to repeatedly poll
sysuptime from multiple devices across my network as a liveness and
reachability detector.

dbh
 

> -----Original Message-----
> From: Eliot Lear [mailto:lear@cisco.com] 
> Sent: Friday, September 17, 2010 9:48 AM
> To: David Harrington; isms@ietf.org; 'ext Romascanu, Dan 
> (Dan)'; Ron Bonica
> Subject: Re: [Isms] status and future of the isms working group
> 
>  While I agree with Juergen on the logistics, I think Dave 
> highlights interesting work to consider undertaking.  My only 
> concern is that it seems like people have tried to do this 
> before, in particular in the NMRG.  What's the trigger for success?
> 
> Eliot
> 
> On 9/17/10 12:11 PM, Juergen Schoenwaelder wrote:
> > On Fri, Sep 17, 2010 at 11:57:31AM +0200, David Harrington wrote:
> >  
> >> I would like to recommend a new work item for ISMS - design a new

> >> architecture standard for SNMP development.
> >> I recommend developing "A Simple Architecture for Describing SNMP

> >> Frameworks" that is more consistent with the simpler layered 
> >> architectural models used for Netconf [RFC 4741, section 1.1] and

> >> Syslog [RFC 5424 section 3], to bring simplicity back into SNMP 
> >> standards development.
> > ISMS stands for "Integrated Security Model for SNMP" and it 
> seems the 
> > work you are proposing really calls for a different working group,

> > likely located in the OPS area not in the security area (as can be

> > seen by the ADs you have put on the CC).
> >
> > /js
> >


From dromasca@avaya.com  Fri Sep 17 07:38:39 2010
Return-Path: <dromasca@avaya.com>
X-Original-To: isms@core3.amsl.com
Delivered-To: isms@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0D0433A67A1 for <isms@core3.amsl.com>; Fri, 17 Sep 2010 07:38:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.505
X-Spam-Level: 
X-Spam-Status: No, score=-102.505 tagged_above=-999 required=5 tests=[AWL=0.094, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1KypwuQ2WlRJ for <isms@core3.amsl.com>; Fri, 17 Sep 2010 07:38:37 -0700 (PDT)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by core3.amsl.com (Postfix) with ESMTP id 2C2B93A67A3 for <isms@ietf.org>; Fri, 17 Sep 2010 07:38:31 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.56,383,1280721600"; d="scan'208";a="207959594"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 17 Sep 2010 10:38:35 -0400
X-IronPort-AV: E=Sophos;i="4.56,383,1280721600"; d="scan'208";a="517436353"
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.12]) by co300216-co-erhwest-out.avaya.com with ESMTP; 17 Sep 2010 10:38:34 -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: Fri, 17 Sep 2010 16:37:57 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A040256FEC0@307622ANEX5.global.avaya.com>
In-Reply-To: <DC81494673134E448B019A3F0A41166B@23FX1C1>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Isms] status and future of the isms working group
Thread-Index: ActWbvZeAeOpshHYQ2+hxVH16c11fQAAjwQQAAD6K5A=
References: <20100917082039.GA47046@elstar.local>	<CCBEBEBD3ED849FCA53890C5792FD42B@23FX1C1> <20100917101102.GA47610@elstar.local> <4C9371A6.6040106@cisco.com> <DC81494673134E448B019A3F0A41166B@23FX1C1>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "David Harrington" <ietfdbh@comcast.net>, "Eliot Lear" <lear@cisco.com>, <isms@ietf.org>, "Ron Bonica" <rbonica@juniper.net>
Subject: Re: [Isms] status and future of the isms working group
X-BeenThere: isms@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mailing list for the ISMS working group <isms.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isms>
List-Post: <mailto:isms@ietf.org>
List-Help: <mailto:isms-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Sep 2010 14:38:39 -0000

1. I agree that it's time to think about a new architecture which is
multiprotocol and does not impose the restrictions that 3411 had put on
SNMP. This work should start from the usage scenarios for SNMP, NETCONF
and other protocols and how we see them used by operators in real life
deployments. The example given by David was maybe talked about many
times, but was not (to my knowledge) put in any document. =20

2. I think this discussion exceeds the scope of ISMS. I suggest to move
it on ops-area@ietf.org

Dan


> -----Original Message-----
> From: David Harrington [mailto:ietfdbh@comcast.net]=20
> Sent: Friday, September 17, 2010 4:24 PM
> To: 'Eliot Lear'; isms@ietf.org; Romascanu, Dan (Dan); 'Ron Bonica'
> Subject: RE: [Isms] status and future of the isms working group
>=20
> Hi,
>=20
> NMRG worked on information/data models (RFC3444) and=20
> XML-based NM (e.g., through proxies).
>=20
> I don't believe NMRG ever tried to write a new SNMP=20
> architecture document.
> and in the IETF, WGs have been told that modifying the RFC=20
> 3411 architecture is definitely out of scope.=20
> The EOS and SMING and ISMS WGs were all told to "work within" the
> RFC3411 architecture.
> I think that restriction was part (but only part) of the=20
> reason for the failures of EOS and SMING.
> We only got to modify the architecture in ISMS when we needed=20
> to define a transport subsystem in rfc5590.
> So I don't agree this has been tried before.
>=20
> I think SNMP could be brought out of the 1980's, but first we=20
> need to make it easier to add new features, such as new=20
> operations, and new data modeling approaches. I think the=20
> RFC3411 architecture makes it so hard to write any=20
> extensions, even models that fit within the RFC3411=20
> architecture, that it greatly increases the complexity.=20
> A simpler architecture would allow SNMP to be maintained and=20
> updated more easily.
>=20
> Netconf can certainly do some of the things that an extended=20
> SNMP might, but netconf is designed for a different usage=20
> scenario. I certainly would think twice about using Netconf=20
> to repeatedly poll sysuptime from multiple devices across my=20
> network as a liveness and reachability detector.
>=20
> dbh
> =20
>=20
> > -----Original Message-----
> > From: Eliot Lear [mailto:lear@cisco.com]
> > Sent: Friday, September 17, 2010 9:48 AM
> > To: David Harrington; isms@ietf.org; 'ext Romascanu, Dan=20
> (Dan)'; Ron=20
> > Bonica
> > Subject: Re: [Isms] status and future of the isms working group
> >=20
> >  While I agree with Juergen on the logistics, I think Dave=20
> highlights=20
> > interesting work to consider undertaking.  My only concern=20
> is that it=20
> > seems like people have tried to do this before, in=20
> particular in the=20
> > NMRG.  What's the trigger for success?
> >=20
> > Eliot
> >=20
> > On 9/17/10 12:11 PM, Juergen Schoenwaelder wrote:
> > > On Fri, Sep 17, 2010 at 11:57:31AM +0200, David Harrington wrote:
> > > =20
> > >> I would like to recommend a new work item for ISMS - design a new
>=20
> > >> architecture standard for SNMP development.
> > >> I recommend developing "A Simple Architecture for Describing SNMP
>=20
> > >> Frameworks" that is more consistent with the simpler layered=20
> > >> architectural models used for Netconf [RFC 4741, section 1.1] and
>=20
> > >> Syslog [RFC 5424 section 3], to bring simplicity back into SNMP=20
> > >> standards development.
> > > ISMS stands for "Integrated Security Model for SNMP" and it
> > seems the
> > > work you are proposing really calls for a different working group,
>=20
> > > likely located in the OPS area not in the security area (as can be
>=20
> > > seen by the ADs you have put on the CC).
> > >
> > > /js
> > >
>=20
>=20

From wjhns1@hardakers.net  Fri Sep 17 09:43:48 2010
Return-Path: <wjhns1@hardakers.net>
X-Original-To: isms@core3.amsl.com
Delivered-To: isms@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 893223A685C for <isms@core3.amsl.com>; Fri, 17 Sep 2010 09:43:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZeAbawltnVFv for <isms@core3.amsl.com>; Fri, 17 Sep 2010 09:43:47 -0700 (PDT)
Received: from mail.hardakers.net (hardaker-pt.tunnel.tserv1.fmt.ipv6.he.net [IPv6:2001:470:1f00:ffff::af]) by core3.amsl.com (Postfix) with ESMTP id 037E33A6864 for <isms@ietf.org>; Fri, 17 Sep 2010 09:43:46 -0700 (PDT)
Received: from localhost (wjh.hardakers.net [10.0.0.2]) by mail.hardakers.net (Postfix) with ESMTPSA id EA57A981B4 for <isms@ietf.org>; Fri, 17 Sep 2010 09:44:10 -0700 (PDT)
From: Wes Hardaker <wjhns1@hardakers.net>
To: isms@ietf.org
Organization: Sparta
References: <20100917082039.GA47046@elstar.local>
Date: Fri, 17 Sep 2010 09:44:10 -0700
In-Reply-To: <20100917082039.GA47046@elstar.local> (Juergen Schoenwaelder's message of "Fri, 17 Sep 2010 10:20:39 +0200")
Message-ID: <sdtylo1fs5.fsf@wjh.hardakers.net>
User-Agent: Gnus/5.110011 (No Gnus v0.11) Emacs/23.2 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
Subject: Re: [Isms] Ismsstatus and future of the isms working group
X-BeenThere: isms@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mailing list for the ISMS working group <isms.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isms>
List-Post: <mailto:isms@ietf.org>
List-Help: <mailto:isms-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Sep 2010 16:43:48 -0000

>>>>> On Fri, 17 Sep 2010 10:20:39 +0200, Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de> said:

JS> However, there might also be well justified reasons to keep the WG
JS> running. One of them could be the advancement of some RFCs to Draft
JS> standard.

As you know based on our discussions and the messages that you've seen
recently from us about interoperability testing, I'm very interested in
pushing the 5953 to the Draft level.  We have two implementations of
5953 that already interoperate and we're continuing to work further to
perform even more testing between the two implementations.

I do see the "Draft" level standard as being an important step.  I know
in the IETF we've frequently wondered "whether it's worth it or not",
but I think definitely is as it shows the user community that a protocol
is considered important by the vendors that are offering it.  Most
importantly, when the protocol is a mission critical protocol then
advancing it to Draft shows that the protocol has been tested and is
thus more likely to get deployment.  Operators that make use of
management protocols like SNMP have always been wary of using new
features because SNMP is such a mission-critical protocol.
Demonstrating and documenting interoperability shows that the technology
is ready for deployment.

I would like to request that the ISMS working group take on the work of
documenting the interoperability results and pushing the 5953 (and
the needed pre-requisites mentioned in my other message) forward to
Draft.  I and other members of my team at Cobham are very willing to
help write, edit and review documents that work toward this goal.

-- 
Wes Hardaker
Cobham Analytic Solutions

From ietfc@btconnect.com  Mon Sep 20 01:29:20 2010
Return-Path: <ietfc@btconnect.com>
X-Original-To: isms@core3.amsl.com
Delivered-To: isms@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C14BB3A6998; Mon, 20 Sep 2010 01:29:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.496
X-Spam-Level: 
X-Spam-Status: No, score=-0.496 tagged_above=-999 required=5 tests=[AWL=-0.497, BAYES_50=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XnNNXU-WGWwX; Mon, 20 Sep 2010 01:29:19 -0700 (PDT)
Received: from mail.btconnect.com (c2bthomr10.btconnect.com [213.123.20.128]) by core3.amsl.com (Postfix) with ESMTP id ED5233A6996; Mon, 20 Sep 2010 01:29:18 -0700 (PDT)
Received: from host217-44-4-171.range217-44.btcentralplus.com (HELO pc6) ([217.44.4.171]) by c2bthomr10.btconnect.com with SMTP id AAJ15615; Mon, 20 Sep 2010 09:29:33 +0100 (BST)
Message-ID: <000b01cb5895$868c3ca0$4001a8c0@gateway.2wire.net>
From: "t.petch" <ietfc@btconnect.com>
To: "Romascanu, Dan \(Dan\)" <dromasca@avaya.com>, "David Harrington" <ietfdbh@comcast.net>, <isms@ietf.org>, "Ron Bonica" <rbonica@juniper.net>
References: <20100917082039.GA47046@elstar.local>	<CCBEBEBD3ED849FCA53890C5792FD42B@23FX1C1><20100917101102.GA47610@elstar.local> <4C9371A6.6040106@cisco.com><DC81494673134E448B019A3F0A41166B@23FX1C1> <EDC652A26FB23C4EB6384A4584434A040256FEC0@307622ANEX5.global.avaya.com>
Date: Mon, 20 Sep 2010 09:28:49 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Mirapoint-IP-Reputation: reputation=Fair-1, source=Queried, refid=tid=0001.0A0B0301.4C971B61.0030, actions=tag
X-Junkmail-Status: score=10/50, host=c2bthomr10.btconnect.com
X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B020A.4C971B72.03BE,ss=1,fgs=0, ip=0.0.0.0, so=2010-07-22 22:03:31, dmn=2009-09-10 00:05:08, mode=single engine
X-Junkmail-IWF: false
Cc: ops-area@ietf.org
Subject: Re: [Isms] status and future of the isms working group
X-BeenThere: isms@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mailing list for the ISMS working group <isms.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isms>
List-Post: <mailto:isms@ietf.org>
List-Help: <mailto:isms-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Sep 2010 08:29:20 -0000

----- Original Message -----
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "David Harrington" <ietfdbh@comcast.net>; "Eliot Lear" <lear@cisco.com>;
<isms@ietf.org>; "Ron Bonica" <rbonica@juniper.net>
Sent: Friday, September 17, 2010 4:37 PM

> 1. I agree that it's time to think about a new architecture which is
> multiprotocol and does not impose the restrictions that 3411 had put on
> SNMP. This work should start from the usage scenarios for SNMP, NETCONF
> and other protocols and how we see them used by operators in real life
> deployments. The example given by David was maybe talked about many
> times, but was not (to my knowledge) put in any document.

RFC3411 was a great piece of work, but turned out to be fatally flawed.  The
first time it was put to the test, introducing a new security model, it proved
unusable.  At the same time, the IESG said it was immutable and the isms working
group wasted years squaring that circle, producing RC5590 which is, to any
independent observer, replacing parts of RFC3411.  So great piece of work,
causing much damage.  With the benefit of hindsight, the isms working group
should have said 'Mission Impossible' and refused to continue until it was
allowed to replace RFC3411 (but I did not see that until 2008:-(

I see no reason to suppose we would do any better now, be it a single or multi
protocol architecture.

At the same time, there is activity currently taking the Management out of OAM,
in the mpls-tp nexus but in other related activities as well and it is that that
I think needs tackling.  What is management?  Can we agree an IETF wide
definition any more? I see
draft-ietf-opsawg-mpls-tp-oam-def
as just the tip of this iceberg.

Tom Petch




>
> 2. I think this discussion exceeds the scope of ISMS. I suggest to move
> it on ops-area@ietf.org
>
> Dan
>
>
> > -----Original Message-----
> > From: David Harrington [mailto:ietfdbh@comcast.net]
> > Sent: Friday, September 17, 2010 4:24 PM
> > To: 'Eliot Lear'; isms@ietf.org; Romascanu, Dan (Dan); 'Ron Bonica'
> > Subject: RE: [Isms] status and future of the isms working group
> >
> > Hi,
> >
> > NMRG worked on information/data models (RFC3444) and
> > XML-based NM (e.g., through proxies).
> >
> > I don't believe NMRG ever tried to write a new SNMP
> > architecture document.
> > and in the IETF, WGs have been told that modifying the RFC
> > 3411 architecture is definitely out of scope.
> > The EOS and SMING and ISMS WGs were all told to "work within" the
> > RFC3411 architecture.
> > I think that restriction was part (but only part) of the
> > reason for the failures of EOS and SMING.
> > We only got to modify the architecture in ISMS when we needed
> > to define a transport subsystem in rfc5590.
> > So I don't agree this has been tried before.
> >
> > I think SNMP could be brought out of the 1980's, but first we
> > need to make it easier to add new features, such as new
> > operations, and new data modeling approaches. I think the
> > RFC3411 architecture makes it so hard to write any
> > extensions, even models that fit within the RFC3411
> > architecture, that it greatly increases the complexity.
> > A simpler architecture would allow SNMP to be maintained and
> > updated more easily.
> >
> > Netconf can certainly do some of the things that an extended
> > SNMP might, but netconf is designed for a different usage
> > scenario. I certainly would think twice about using Netconf
> > to repeatedly poll sysuptime from multiple devices across my
> > network as a liveness and reachability detector.
> >
> > dbh
> >
> >
> > > -----Original Message-----
> > > From: Eliot Lear [mailto:lear@cisco.com]
> > > Sent: Friday, September 17, 2010 9:48 AM
> > > To: David Harrington; isms@ietf.org; 'ext Romascanu, Dan
> > (Dan)'; Ron
> > > Bonica
> > > Subject: Re: [Isms] status and future of the isms working group
> > >
> > >  While I agree with Juergen on the logistics, I think Dave
> > highlights
> > > interesting work to consider undertaking.  My only concern
> > is that it
> > > seems like people have tried to do this before, in
> > particular in the
> > > NMRG.  What's the trigger for success?
> > >
> > > Eliot
> > >
> > > On 9/17/10 12:11 PM, Juergen Schoenwaelder wrote:
> > > > On Fri, Sep 17, 2010 at 11:57:31AM +0200, David Harrington wrote:
> > > >
> > > >> I would like to recommend a new work item for ISMS - design a new
> >
> > > >> architecture standard for SNMP development.
> > > >> I recommend developing "A Simple Architecture for Describing SNMP
> >
> > > >> Frameworks" that is more consistent with the simpler layered
> > > >> architectural models used for Netconf [RFC 4741, section 1.1] and
> >
> > > >> Syslog [RFC 5424 section 3], to bring simplicity back into SNMP
> > > >> standards development.
> > > > ISMS stands for "Integrated Security Model for SNMP" and it
> > > seems the
> > > > work you are proposing really calls for a different working group,
> >
> > > > likely located in the OPS area not in the security area (as can be
> >
> > > > seen by the ADs you have put on the CC).
> > > >
> > > > /js
> > > >
> >
> >
> _______________________________________________
> Isms mailing list
> Isms@ietf.org
> https://www.ietf.org/mailman/listinfo/isms


From dromasca@avaya.com  Mon Sep 20 03:28:06 2010
Return-Path: <dromasca@avaya.com>
X-Original-To: isms@core3.amsl.com
Delivered-To: isms@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 674903A68D6; Mon, 20 Sep 2010 03:28:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.207
X-Spam-Level: 
X-Spam-Status: No, score=-102.207 tagged_above=-999 required=5 tests=[AWL=-0.208, BAYES_00=-2.599, J_CHICKENPOX_15=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id atxILRjn53bC; Mon, 20 Sep 2010 03:28:05 -0700 (PDT)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by core3.amsl.com (Postfix) with ESMTP id 12ECA3A688A; Mon, 20 Sep 2010 03:28:04 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.56,392,1280721600"; d="scan'208";a="238782703"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 20 Sep 2010 06:28:28 -0400
X-IronPort-AV: E=Sophos;i="4.56,392,1280721600"; d="scan'208";a="517953598"
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.12]) by co300216-co-erhwest-out.avaya.com with ESMTP; 20 Sep 2010 06:28:27 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 20 Sep 2010 12:28:06 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A0402570133@307622ANEX5.global.avaya.com>
In-Reply-To: <000b01cb5895$868c3ca0$4001a8c0@gateway.2wire.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Isms] status and future of the isms working group
Thread-Index: ActYnfrNdQ+2VcYqRv+BNgBfxtZh7gAD/XmA
References: <20100917082039.GA47046@elstar.local>	<CCBEBEBD3ED849FCA53890C5792FD42B@23FX1C1><20100917101102.GA47610@elstar.local> <4C9371A6.6040106@cisco.com><DC81494673134E448B019A3F0A41166B@23FX1C1> <EDC652A26FB23C4EB6384A4584434A040256FEC0@307622ANEX5.global.avaya.com> <000b01cb5895$868c3ca0$4001a8c0@gateway.2wire.net>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "t.petch" <ietfc@btconnect.com>, "David Harrington" <ietfdbh@comcast.net>, <isms@ietf.org>, "Ron Bonica" <rbonica@juniper.net>
Cc: ops-area@ietf.org
Subject: Re: [Isms] status and future of the isms working group
X-BeenThere: isms@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mailing list for the ISMS working group <isms.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isms>
List-Post: <mailto:isms@ietf.org>
List-Help: <mailto:isms-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Sep 2010 10:28:06 -0000

Hi Tom,

See in text.=20

Regards,

Dan
=20

> -----Original Message-----
> From: t.petch [mailto:ietfc@btconnect.com]=20
> Sent: Monday, September 20, 2010 9:29 AM
> To: Romascanu, Dan (Dan); David Harrington; isms@ietf.org; Ron Bonica
> Cc: ops-area@ietf.org
> Subject: Re: [Isms] status and future of the isms working group
>=20
> ----- Original Message -----
> From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
> To: "David Harrington" <ietfdbh@comcast.net>; "Eliot Lear"=20
> <lear@cisco.com>; <isms@ietf.org>; "Ron Bonica" <rbonica@juniper.net>
> Sent: Friday, September 17, 2010 4:37 PM
>=20
> > 1. I agree that it's time to think about a new architecture=20
> which is=20
> > multiprotocol and does not impose the restrictions that=20
> 3411 had put=20
> > on SNMP. This work should start from the usage scenarios for SNMP,=20
> > NETCONF and other protocols and how we see them used by=20
> operators in=20
> > real life deployments. The example given by David was maybe talked=20
> > about many times, but was not (to my knowledge) put in any document.
>=20
> RFC3411 was a great piece of work, but turned out to be=20
> fatally flawed.  The first time it was put to the test,=20
> introducing a new security model, it proved unusable.  At the=20
> same time, the IESG said it was immutable and the isms=20
> working group wasted years squaring that circle, producing=20
> RC5590 which is, to any independent observer, replacing parts=20
> of RFC3411.  So great piece of work, causing much damage. =20
> With the benefit of hindsight, the isms working group should=20
> have said 'Mission Impossible' and refused to continue until=20
> it was allowed to replace RFC3411 (but I did not see that=20
> until 2008:-(
>=20
> I see no reason to suppose we would do any better now, be it=20
> a single or multi protocol architecture.

Does this mean that we should not / need not try?=20

>=20
> At the same time, there is activity currently taking the=20
> Management out of OAM, in the mpls-tp nexus but in other=20
> related activities as well and it is that that I think needs=20
> tackling.  What is management?  Can we agree an IETF wide=20
> definition any more? I see draft-ietf-opsawg-mpls-tp-oam-def=20
> as just the tip of this iceberg.
>=20

One of the points that draft-ietf-opsawg-mpls-tp-oam-def makes is that
management is not part of OAM, the M in the trinity standing for
Maintenance. Right now draft-ietf-opsawg-mpls-tp-oam-def is being
returned by the IESG to the OPSAWG with the recommendation to broaden
its scope beyond mpls-tp. I would agree that it's still the tip of the
iceberg. =20

> Tom Petch
>=20
>=20
>=20
>=20
> >
> > 2. I think this discussion exceeds the scope of ISMS. I suggest to=20
> > move it on ops-area@ietf.org
> >
> > Dan
> >
> >
> > > -----Original Message-----
> > > From: David Harrington [mailto:ietfdbh@comcast.net]
> > > Sent: Friday, September 17, 2010 4:24 PM
> > > To: 'Eliot Lear'; isms@ietf.org; Romascanu, Dan (Dan);=20
> 'Ron Bonica'
> > > Subject: RE: [Isms] status and future of the isms working group
> > >
> > > Hi,
> > >
> > > NMRG worked on information/data models (RFC3444) and XML-based NM=20
> > > (e.g., through proxies).
> > >
> > > I don't believe NMRG ever tried to write a new SNMP architecture=20
> > > document.
> > > and in the IETF, WGs have been told that modifying the RFC
> > > 3411 architecture is definitely out of scope.
> > > The EOS and SMING and ISMS WGs were all told to "work within" the
> > > RFC3411 architecture.
> > > I think that restriction was part (but only part) of the=20
> reason for=20
> > > the failures of EOS and SMING.
> > > We only got to modify the architecture in ISMS when we needed to=20
> > > define a transport subsystem in rfc5590.
> > > So I don't agree this has been tried before.
> > >
> > > I think SNMP could be brought out of the 1980's, but=20
> first we need=20
> > > to make it easier to add new features, such as new=20
> operations, and=20
> > > new data modeling approaches. I think the
> > > RFC3411 architecture makes it so hard to write any=20
> extensions, even=20
> > > models that fit within the RFC3411 architecture, that it greatly=20
> > > increases the complexity.
> > > A simpler architecture would allow SNMP to be maintained=20
> and updated=20
> > > more easily.
> > >
> > > Netconf can certainly do some of the things that an extended SNMP=20
> > > might, but netconf is designed for a different usage scenario. I=20
> > > certainly would think twice about using Netconf to=20
> repeatedly poll=20
> > > sysuptime from multiple devices across my network as a=20
> liveness and=20
> > > reachability detector.
> > >
> > > dbh
> > >
> > >
> > > > -----Original Message-----
> > > > From: Eliot Lear [mailto:lear@cisco.com]
> > > > Sent: Friday, September 17, 2010 9:48 AM
> > > > To: David Harrington; isms@ietf.org; 'ext Romascanu, Dan
> > > (Dan)'; Ron
> > > > Bonica
> > > > Subject: Re: [Isms] status and future of the isms working group
> > > >
> > > >  While I agree with Juergen on the logistics, I think Dave
> > > highlights
> > > > interesting work to consider undertaking.  My only concern
> > > is that it
> > > > seems like people have tried to do this before, in
> > > particular in the
> > > > NMRG.  What's the trigger for success?
> > > >
> > > > Eliot
> > > >
> > > > On 9/17/10 12:11 PM, Juergen Schoenwaelder wrote:
> > > > > On Fri, Sep 17, 2010 at 11:57:31AM +0200, David=20
> Harrington wrote:
> > > > >
> > > > >> I would like to recommend a new work item for ISMS -=20
> design a=20
> > > > >> new
> > >
> > > > >> architecture standard for SNMP development.
> > > > >> I recommend developing "A Simple Architecture for Describing=20
> > > > >> SNMP
> > >
> > > > >> Frameworks" that is more consistent with the simpler layered=20
> > > > >> architectural models used for Netconf [RFC 4741,=20
> section 1.1]=20
> > > > >> and
> > >
> > > > >> Syslog [RFC 5424 section 3], to bring simplicity=20
> back into SNMP=20
> > > > >> standards development.
> > > > > ISMS stands for "Integrated Security Model for SNMP" and it
> > > > seems the
> > > > > work you are proposing really calls for a different working=20
> > > > > group,
> > >
> > > > > likely located in the OPS area not in the security=20
> area (as can=20
> > > > > be
> > >
> > > > > seen by the ADs you have put on the CC).
> > > > >
> > > > > /js
> > > > >
> > >
> > >
> > _______________________________________________
> > Isms mailing list
> > Isms@ietf.org
> > https://www.ietf.org/mailman/listinfo/isms
>=20
>=20

From ietfc@btconnect.com  Mon Sep 20 03:58:03 2010
Return-Path: <ietfc@btconnect.com>
X-Original-To: isms@core3.amsl.com
Delivered-To: isms@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7D8EE3A68B5; Mon, 20 Sep 2010 03:58:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.33
X-Spam-Level: 
X-Spam-Status: No, score=-1.33 tagged_above=-999 required=5 tests=[AWL=0.669,  BAYES_00=-2.599, J_CHICKENPOX_15=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id N2FuFN5uWzjZ; Mon, 20 Sep 2010 03:58:02 -0700 (PDT)
Received: from c2beaomr02.btconnect.com (c2beaomr02.btconnect.com [213.123.26.180]) by core3.amsl.com (Postfix) with ESMTP id AC0253A6A40; Mon, 20 Sep 2010 03:58:01 -0700 (PDT)
Received: from pc6 (host217-44-4-171.range217-44.btcentralplus.com [217.44.4.171]) by c2beaomr02.btconnect.com with SMTP id EEG83820; Mon, 20 Sep 2010 11:58:14 +0100 (BST)
X-Mirapoint-IP-Reputation: reputation=Fair-1, source=Queried, refid=0001.0A0B0301.4C973E46.0123, actions=TAG
Message-ID: <0b4b01cb58aa$4cd4f320$4001a8c0@gateway.2wire.net>
From: "t.petch" <ietfc@btconnect.com>
To: "Romascanu, Dan \(Dan\)" <dromasca@avaya.com>, "David Harrington" <ietfdbh@comcast.net>, <isms@ietf.org>, "Ron Bonica" <rbonica@juniper.net>
References: <20100917082039.GA47046@elstar.local>	<CCBEBEBD3ED849FCA53890C5792FD42B@23FX1C1><20100917101102.GA47610@elstar.local> <4C9371A6.6040106@cisco.com><DC81494673134E448B019A3F0A41166B@23FX1C1> <EDC652A26FB23C4EB6384A4584434A040256FEC0@307622ANEX5.global.avaya.com> <000b01cb5895$868c3ca0$4001a8c0@gateway.2wire.net> <EDC652A26FB23C4EB6384A4584434A0402570133@307622ANEX5.global.avaya.com>
Date: Mon, 20 Sep 2010 11:57:49 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Junkmail-Status: score=10/50, host=c2beaomr02.btconnect.com
X-Junkmail-SD-Raw: score=unknown, refid=str=0001.0A0B0206.4C973E4C.0153,ss=1,fgs=0, ip=0.0.0.0, so=2009-07-20 21:54:04, dmn=5.7.1/2009-08-27, mode=single engine
X-Junkmail-IWF: false
Cc: ops-area@ietf.org
Subject: Re: [Isms] status and future of the isms working group
X-BeenThere: isms@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mailing list for the ISMS working group <isms.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isms>
List-Post: <mailto:isms@ietf.org>
List-Help: <mailto:isms-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Sep 2010 10:58:03 -0000

----- Original Message -----
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "t.petch" <ietfc@btconnect.com>; "David Harrington"
Cc: <ops-area@ietf.org>
Sent: Monday, September 20, 2010 12:28 PM
> -----Original Message-----
> From: t.petch [mailto:ietfc@btconnect.com]
> Sent: Monday, September 20, 2010 9:29 AM
> To: Romascanu, Dan (Dan); David Harrington; isms@ietf.org; Ron Bonica
> Cc: ops-area@ietf.org
> Subject: Re: [Isms] status and future of the isms working group
>
> ----- Original Message -----
> From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
> To: "David Harrington" <ietfdbh@comcast.net>; "Eliot Lear"
> <lear@cisco.com>; <isms@ietf.org>; "Ron Bonica" <rbonica@juniper.net>
> Sent: Friday, September 17, 2010 4:37 PM
>
> > 1. I agree that it's time to think about a new architecture
> which is
> > multiprotocol and does not impose the restrictions that
> 3411 had put
> > on SNMP. This work should start from the usage scenarios for SNMP,
> > NETCONF and other protocols and how we see them used by
> operators in
> > real life deployments. The example given by David was maybe talked
> > about many times, but was not (to my knowledge) put in any document.
>
> RFC3411 was a great piece of work, but turned out to be
> fatally flawed.  The first time it was put to the test,
> introducing a new security model, it proved unusable.  At the
> same time, the IESG said it was immutable and the isms
> working group wasted years squaring that circle, producing
> RC5590 which is, to any independent observer, replacing parts
> of RFC3411.  So great piece of work, causing much damage.
> With the benefit of hindsight, the isms working group should
> have said 'Mission Impossible' and refused to continue until
> it was allowed to replace RFC3411 (but I did not see that
> until 2008:-(
>
> I see no reason to suppose we would do any better now, be it
> a single or multi protocol architecture.

Does this mean that we should not / need not try?

<tp>
I think that our resources are limited, and tend to decay with the age of a
working group, so I would rather see them applied elsewhere.  I look back at the
effort that went into RFC3411, over many years, and yet it fell at the first
hurdle, not accommodating the move of security from deep inside the engine to
off the bottom of the radar; why should we do any better this time?

I see comparisons with the architecture of syslog and netconf, and yet ...
There is a structure of layers, hardly an architecture.  syslog was doing nicely
without it, and I am not sure that it is any better with it.  netconf has been
debating recently how and where the messages should be delineated within a
stream transport, with various views of what it means in architectural terms,
yet I see the architecture as no help in resolving the issue of delineation.

So, potentially much work, for little or no gain.

Tom Petch

>
> At the same time, there is activity currently taking the
> Management out of OAM, in the mpls-tp nexus but in other
> related activities as well and it is that that I think needs
> tackling.  What is management?  Can we agree an IETF wide
> definition any more? I see draft-ietf-opsawg-mpls-tp-oam-def
> as just the tip of this iceberg.
>

One of the points that draft-ietf-opsawg-mpls-tp-oam-def makes is that
management is not part of OAM, the M in the trinity standing for
Maintenance. Right now draft-ietf-opsawg-mpls-tp-oam-def is being
returned by the IESG to the OPSAWG with the recommendation to broaden
its scope beyond mpls-tp. I would agree that it's still the tip of the
iceberg.

> Tom Petch
>
>
>
>
> >
> > 2. I think this discussion exceeds the scope of ISMS. I suggest to
> > move it on ops-area@ietf.org
> >
> > Dan
> >
> >
> > > -----Original Message-----
> > > From: David Harrington [mailto:ietfdbh@comcast.net]
> > > Sent: Friday, September 17, 2010 4:24 PM
> > > To: 'Eliot Lear'; isms@ietf.org; Romascanu, Dan (Dan);
> 'Ron Bonica'
> > > Subject: RE: [Isms] status and future of the isms working group
> > >
> > > Hi,
> > >
> > > NMRG worked on information/data models (RFC3444) and XML-based NM
> > > (e.g., through proxies).
> > >
> > > I don't believe NMRG ever tried to write a new SNMP architecture
> > > document.
> > > and in the IETF, WGs have been told that modifying the RFC
> > > 3411 architecture is definitely out of scope.
> > > The EOS and SMING and ISMS WGs were all told to "work within" the
> > > RFC3411 architecture.
> > > I think that restriction was part (but only part) of the
> reason for
> > > the failures of EOS and SMING.
> > > We only got to modify the architecture in ISMS when we needed to
> > > define a transport subsystem in rfc5590.
> > > So I don't agree this has been tried before.
> > >
> > > I think SNMP could be brought out of the 1980's, but
> first we need
> > > to make it easier to add new features, such as new
> operations, and
> > > new data modeling approaches. I think the
> > > RFC3411 architecture makes it so hard to write any
> extensions, even
> > > models that fit within the RFC3411 architecture, that it greatly
> > > increases the complexity.
> > > A simpler architecture would allow SNMP to be maintained
> and updated
> > > more easily.
> > >
> > > Netconf can certainly do some of the things that an extended SNMP
> > > might, but netconf is designed for a different usage scenario. I
> > > certainly would think twice about using Netconf to
> repeatedly poll
> > > sysuptime from multiple devices across my network as a
> liveness and
> > > reachability detector.
> > >
> > > dbh
> > >
> > >
> > > > -----Original Message-----
> > > > From: Eliot Lear [mailto:lear@cisco.com]
> > > > Sent: Friday, September 17, 2010 9:48 AM
> > > > To: David Harrington; isms@ietf.org; 'ext Romascanu, Dan
> > > (Dan)'; Ron
> > > > Bonica
> > > > Subject: Re: [Isms] status and future of the isms working group
> > > >
> > > >  While I agree with Juergen on the logistics, I think Dave
> > > highlights
> > > > interesting work to consider undertaking.  My only concern
> > > is that it
> > > > seems like people have tried to do this before, in
> > > particular in the
> > > > NMRG.  What's the trigger for success?
> > > >
> > > > Eliot
> > > >
> > > > On 9/17/10 12:11 PM, Juergen Schoenwaelder wrote:
> > > > > On Fri, Sep 17, 2010 at 11:57:31AM +0200, David
> Harrington wrote:
> > > > >
> > > > >> I would like to recommend a new work item for ISMS -
> design a
> > > > >> new
> > >
> > > > >> architecture standard for SNMP development.
> > > > >> I recommend developing "A Simple Architecture for Describing
> > > > >> SNMP
> > >
> > > > >> Frameworks" that is more consistent with the simpler layered
> > > > >> architectural models used for Netconf [RFC 4741,
> section 1.1]
> > > > >> and
> > >
> > > > >> Syslog [RFC 5424 section 3], to bring simplicity
> back into SNMP
> > > > >> standards development.
> > > > > ISMS stands for "Integrated Security Model for SNMP" and it
> > > > seems the
> > > > > work you are proposing really calls for a different working
> > > > > group,
> > >
> > > > > likely located in the OPS area not in the security
> area (as can
> > > > > be
> > >
> > > > > seen by the ADs you have put on the CC).
> > > > >
> > > > > /js
> > > > >
> > >
> > >
> > _______________________________________________
> > Isms mailing list
> > Isms@ietf.org
> > https://www.ietf.org/mailman/listinfo/isms
>
>


From randy_presuhn@mindspring.com  Mon Sep 20 10:04:51 2010
Return-Path: <randy_presuhn@mindspring.com>
X-Original-To: isms@core3.amsl.com
Delivered-To: isms@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9F3003A6B18; Mon, 20 Sep 2010 10:04:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.154
X-Spam-Level: 
X-Spam-Status: No, score=-101.154 tagged_above=-999 required=5 tests=[AWL=-1.155, BAYES_50=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3txohCXJbflM; Mon, 20 Sep 2010 10:04:50 -0700 (PDT)
Received: from elasmtp-banded.atl.sa.earthlink.net (elasmtp-banded.atl.sa.earthlink.net [209.86.89.70]) by core3.amsl.com (Postfix) with ESMTP id AE6A03A6B26; Mon, 20 Sep 2010 10:03:27 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=Q/R2PfdN678daUxM+bWIOKj+gNptzuDYaP+NIAsacjTnn8dmTOuPFvcVYluhoZUL; h=Received:Message-ID:From:To:Cc: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.49.28] (helo=oemcomputer) by elasmtp-banded.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <randy_presuhn@mindspring.com>) id 1OxjmO-0002BI-Ty; Mon, 20 Sep 2010 13:03:49 -0400
Message-ID: <003c01cb58e5$e95359e0$6801a8c0@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: <isms@ietf.org>
References: <20100917082039.GA47046@elstar.local>	<CCBEBEBD3ED849FCA53890C5792FD42B@23FX1C1><20100917101102.GA47610@elstar.local><4C9371A6.6040106@cisco.com><DC81494673134E448B019A3F0A41166B@23FX1C1><EDC652A26FB23C4EB6384A4584434A040256FEC0@307622ANEX5.global.avaya.com><000b01cb5895$868c3ca0$4001a8c0@gateway.2wire.net><EDC652A26FB23C4EB6384A4584434A0402570133@307622ANEX5.global.avaya.com> <0b4b01cb58aa$4cd4f320$4001a8c0@gateway.2wire.net>
Date: Mon, 20 Sep 2010 10:04:37 -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: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d88829a3b650ee59d5fe0b0ea7e7055a81f6d9cc73bb16c2ebed350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 99.41.49.28
Cc: ops-area@ietf.org
Subject: Re: [Isms] status and future of the isms working group
X-BeenThere: isms@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mailing list for the ISMS working group <isms.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isms>
List-Post: <mailto:isms@ietf.org>
List-Help: <mailto:isms-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Sep 2010 17:04:51 -0000

Hi -

> From: "t.petch" <ietfc@btconnect.com>
...
> I think that our resources are limited, and tend to decay with the age of a
> working group, so I would rather see them applied elsewhere.  I look back at the
> effort that went into RFC3411, over many years, and yet it fell at the first
> hurdle, not accommodating the move of security from deep inside the engine to
> off the bottom of the radar; why should we do any better this time?
...

The problem as I see it was that RFC3411 was intended to be the glue
describing how a particular set of specifications fit together, *not* as
*the* architecture for all future SNMP work.  *Requiring* extensions,
additions, and embellishments to adhere to that architecture is in
my opinion a huge mistake.  From my perspective, the real problem
addressed by RFC 3411 was that some of the preceding proposals
for securing SNMP had so many convolutions and interactions that
a lot of folks had trouble wrapping their heads around them.  The
modularity brought by RFC 3411 was modularity of *specification*,
not necessarily implementation.  The ASIs were rather controversial
because folks were (rightly, in retrospect) concerned that they would
be understood in a prescriptive sense, rather than descriptive sense
in which they were intended.

More importantly, I think focusing energy on this "problem" (which is
tempting because it's something we think we understand) would be
a huge distraction from the *real* problem: the kinds of information models
this infrastructure should provide access to.  If the information models
can't support the high-value functions administrators / operators need,
then embellishing the protocol engine architecture is a waste of time.

Randy


From wjhns1@hardakers.net  Mon Sep 20 11:43:59 2010
Return-Path: <wjhns1@hardakers.net>
X-Original-To: isms@core3.amsl.com
Delivered-To: isms@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9D7463A67AC; Mon, 20 Sep 2010 11:43:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L-Pj-WLY-AtQ; Mon, 20 Sep 2010 11:43:12 -0700 (PDT)
Received: from mail.hardakers.net (hardaker-pt.tunnel.tserv1.fmt.ipv6.he.net [IPv6:2001:470:1f00:ffff::af]) by core3.amsl.com (Postfix) with ESMTP id 744663A63EC; Mon, 20 Sep 2010 11:43:10 -0700 (PDT)
Received: from localhost (wjh.hardakers.net [10.0.0.2]) by mail.hardakers.net (Postfix) with ESMTPSA id 09E8C9808C; Mon, 20 Sep 2010 11:43:30 -0700 (PDT)
From: Wes Hardaker <wjhns1@hardakers.net>
To: "t.petch" <ietfc@btconnect.com>
Organization: Sparta
References: <20100917082039.GA47046@elstar.local> <CCBEBEBD3ED849FCA53890C5792FD42B@23FX1C1> <20100917101102.GA47610@elstar.local> <4C9371A6.6040106@cisco.com> <DC81494673134E448B019A3F0A41166B@23FX1C1> <EDC652A26FB23C4EB6384A4584434A040256FEC0@307622ANEX5.global.avaya.com> <000b01cb5895$868c3ca0$4001a8c0@gateway.2wire.net>
Date: Mon, 20 Sep 2010 11:43:29 -0700
In-Reply-To: <000b01cb5895$868c3ca0$4001a8c0@gateway.2wire.net> (t. petch's message of "Mon, 20 Sep 2010 09:28:49 +0200")
Message-ID: <sdlj6w1cj2.fsf@wjh.hardakers.net>
User-Agent: Gnus/5.110011 (No Gnus v0.11) Emacs/23.2 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
Cc: ops-area@ietf.org, isms@ietf.org, Ron Bonica <rbonica@juniper.net>
Subject: Re: [Isms] status and future of the isms working group
X-BeenThere: isms@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mailing list for the ISMS working group <isms.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isms>
List-Post: <mailto:isms@ietf.org>
List-Help: <mailto:isms-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Sep 2010 18:44:02 -0000

>>>>> On Mon, 20 Sep 2010 09:28:49 +0200, "t.petch" <ietfc@btconnect.com> said:

tp> RFC3411 was a great piece of work, but turned out to be fatally
tp> flawed.  The first time it was put to the test, introducing a new
tp> security model, it proved unusable.

Well, I'm not sure that's an entirely fair characterization.  The
problem wasn't that the model was flawed, it was that it wrapped *only*
around its own notion of the SNMP protocol.

When ISMS came along and the decision was to outsource the security to
something in a lower layer, then yes the original model had issues with
that because it didn't take that possibility into account.  5590 simply
fixed that.  Interestingly enough by providing some extra transmission
lines to the model and extra information to the data passed via the
ASIs.

However, the ISMS solutions were the first "standardized" ones.  More
documents and code have been written to provide other security models
that were either implemented or partially implemented and worked just
fine without changing the underlying 3411 model: KSM (which is now being
brought forward again) and SBSM (which is how the ISMS working group got
started but went the SSH-underneath route instead of an
in-SNMPv3-protocol integrated model).
-- 
Wes Hardaker
Cobham Analytic Solutions

From ietfc@btconnect.com  Mon Sep 20 14:32:15 2010
Return-Path: <ietfc@btconnect.com>
X-Original-To: isms@core3.amsl.com
Delivered-To: isms@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5C9DE3A677E; Mon, 20 Sep 2010 14:32:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.798
X-Spam-Level: 
X-Spam-Status: No, score=-1.798 tagged_above=-999 required=5 tests=[AWL=0.802,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cm5A9qZ4vRPg; Mon, 20 Sep 2010 14:31:54 -0700 (PDT)
Received: from c2beaomr08.btconnect.com (c2beaomr08.btconnect.com [213.123.26.186]) by core3.amsl.com (Postfix) with ESMTP id 81A4A3A6822; Mon, 20 Sep 2010 14:31:53 -0700 (PDT)
Received: from pc6 (host217-44-4-171.range217-44.btcentralplus.com [217.44.4.171]) by c2beaomr08.btconnect.com with SMTP id FKO61586; Mon, 20 Sep 2010 22:31:58 +0100 (BST)
X-Mirapoint-IP-Reputation: reputation=Fair-1, source=Queried, refid=0001.0A0B0302.4C97D2CE.0089, actions=TAG
Message-ID: <003901cb5902$d5627fc0$4001a8c0@gateway.2wire.net>
From: "t.petch" <ietfc@btconnect.com>
To: "Wes Hardaker" <wjhns1@hardakers.net>
References: <20100917082039.GA47046@elstar.local><CCBEBEBD3ED849FCA53890C5792FD42B@23FX1C1><20100917101102.GA47610@elstar.local> <4C9371A6.6040106@cisco.com><DC81494673134E448B019A3F0A41166B@23FX1C1><EDC652A26FB23C4EB6384A4584434A040256FEC0@307622ANEX5.global.avaya.com><000b01cb5895$868c3ca0$4001a8c0@gateway.2wire.net> <sdlj6w1cj2.fsf@wjh.hardakers.net>
Date: Mon, 20 Sep 2010 22:31:33 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Junkmail-Status: score=10/50, host=c2beaomr08.btconnect.com
X-Junkmail-SD-Raw: score=unknown, refid=str=0001.0A0B0202.4C97D2D1.01FC,ss=1,fgs=0, ip=0.0.0.0, so=2009-07-20 21:54:04, dmn=5.7.1/2009-08-27, mode=single engine
X-Junkmail-IWF: false
Cc: ops-area@ietf.org, isms <isms@ietf.org>, Ron Bonica <rbonica@juniper.net>
Subject: Re: [Isms] status and future of the isms working group
X-BeenThere: isms@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mailing list for the ISMS working group <isms.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isms>
List-Post: <mailto:isms@ietf.org>
List-Help: <mailto:isms-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Sep 2010 21:32:15 -0000

----- Original Message -----
From: "Wes Hardaker" <wjhns1@hardakers.net>
To: "t.petch" <ietfc@btconnect.com>
Cc: "Romascanu, Dan (Dan)" <dromasca@avaya.com>; "David Harrington"
<ietfdbh@comcast.net>; <isms@ietf.org>; "Ron Bonica" <rbonica@juniper.net>;
<ops-area@ietf.org>
Sent: Monday, September 20, 2010 8:43 PM
> >>>>> On Mon, 20 Sep 2010 09:28:49 +0200, "t.petch" <ietfc@btconnect.com>
said:
>
> tp> RFC3411 was a great piece of work, but turned out to be fatally
> tp> flawed.  The first time it was put to the test, introducing a new
> tp> security model, it proved unusable.
>
> Well, I'm not sure that's an entirely fair characterization.  The
> problem wasn't that the model was flawed, it was that it wrapped *only*
> around its own notion of the SNMP protocol.
>
> When ISMS came along and the decision was to outsource the security to
> something in a lower layer, then yes the original model had issues with
> that because it didn't take that possibility into account.  5590 simply
> fixed that.  Interestingly enough by providing some extra transmission
> lines to the model and extra information to the data passed via the
> ASIs.

Well, yes and no.  In isms, we retained the idea of 'no sessions', and I was
interested to see in the most recent I-D ....  vacmAaaSessionID OBJECT-TYPE

I always thought that SNMP had sessions, just that some of them were rather
short, and I that that is another disconnect that took quite a lot of time to
sort out in the isms work; it would have been easier if RFC3411 or RFC5590 had
had sessions in the architecture.

And yes, I am making my point quite strongly, because I think that an 'RFC6411'
would be a poor use of IETF resources.

Tom Petch

> However, the ISMS solutions were the first "standardized" ones.  More
> documents and code have been written to provide other security models
> that were either implemented or partially implemented and worked just
> fine without changing the underlying 3411 model: KSM (which is now being
> brought forward again) and SBSM (which is how the ISMS working group got
> started but went the SSH-underneath route instead of an
> in-SNMPv3-protocol integrated model).
> --
> Wes Hardaker
> Cobham Analytic Solutions


From randy_presuhn@mindspring.com  Mon Sep 20 15:45:55 2010
Return-Path: <randy_presuhn@mindspring.com>
X-Original-To: isms@core3.amsl.com
Delivered-To: isms@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3C55B3A689C; Mon, 20 Sep 2010 15:45:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.092
X-Spam-Level: 
X-Spam-Status: No, score=-100.092 tagged_above=-999 required=5 tests=[AWL=0.093, BAYES_40=-0.185, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id P1e-z4Wmor26; Mon, 20 Sep 2010 15:45:53 -0700 (PDT)
Received: from elasmtp-scoter.atl.sa.earthlink.net (elasmtp-scoter.atl.sa.earthlink.net [209.86.89.67]) by core3.amsl.com (Postfix) with ESMTP id 1760C3A6843; Mon, 20 Sep 2010 15:45:53 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=KdIqiLAeSMntKyQesnTq0xlopdoZh8xikP8PABZR9/6iFy6sQcE4T0f/ehDuuqCF; h=Message-ID:Date:From:Reply-To:To:Subject:Mime-Version:Content-Type:Content-Transfer-Encoding:X-Mailer:X-ELNK-Trace:X-Originating-IP;
Received: from [209.86.224.30] (helo=mswamui-chipeau.atl.sa.earthlink.net) by elasmtp-scoter.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <randy_presuhn@mindspring.com>) id 1Oxp7o-00031D-Hk; Mon, 20 Sep 2010 18:46:16 -0400
Received: from 99.35.226.183 by webmail.earthlink.net with HTTP; Mon, 20 Sep 2010 18:46:16 -0400
Message-ID: <12104020.1285022776517.JavaMail.root@mswamui-chipeau.atl.sa.earthlink.net>
Date: Mon, 20 Sep 2010 15:46:16 -0700 (GMT-07:00)
From: Randy Presuhn <randy_presuhn@mindspring.com>
To: ops-area@ietf.org, isms@ietf.org
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-Mailer: EarthLink Zoo Mail 1.0
X-ELNK-Trace: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d88829a3b650ee59d5fe431f29806a810180001caca12c37ae72350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 209.86.224.30
Subject: Re: [Isms] status and future of the isms working group
X-BeenThere: isms@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Randy Presuhn <randy_presuhn@mindspring.com>
List-Id: Mailing list for the ISMS working group <isms.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isms>
List-Post: <mailto:isms@ietf.org>
List-Help: <mailto:isms-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Sep 2010 22:45:55 -0000

Hi -

>From: "t.petch" <ietfc@btconnect.com>
...
>Well, yes and no.  In isms, we retained the idea of 'no sessions', and I was
>interested to see in the most recent I-D ....  vacmAaaSessionID OBJECT-TYPE
>
>I always thought that SNMP had sessions, just that some of them were rather
>short, and I that that is another disconnect that took quite a lot of time to
>sort out in the isms work; it would have been easier if RFC3411 or RFC5590 had
>had sessions in the architecture.

The issue DID come up when the work that led to RFC 3411
was being hashed out.  "No sessions" was a much-trumpeted
bit of dogma left over from the OSI and CMIP wars.  No matter
how much having a concept of (even short-lived) sessions might
have made sense, it could not have survived the somewhat toxic
atmosphere that followed the SNMPv2* wars.

Randy

From wjhns1@hardakers.net  Mon Sep 20 17:30:32 2010
Return-Path: <wjhns1@hardakers.net>
X-Original-To: isms@core3.amsl.com
Delivered-To: isms@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 087733A682E; Mon, 20 Sep 2010 17:30:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.593
X-Spam-Level: 
X-Spam-Status: No, score=-2.593 tagged_above=-999 required=5 tests=[AWL=0.006,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LOtPxVpJJbKN; Mon, 20 Sep 2010 17:30:30 -0700 (PDT)
Received: from mail.hardakers.net (hardaker-pt.tunnel.tserv1.fmt.ipv6.he.net [IPv6:2001:470:1f00:ffff::af]) by core3.amsl.com (Postfix) with ESMTP id 12C253A67D1; Mon, 20 Sep 2010 17:30:30 -0700 (PDT)
Received: from localhost (wjh.hardakers.net [10.0.0.2]) by mail.hardakers.net (Postfix) with ESMTPSA id 9D74E980EB; Mon, 20 Sep 2010 17:30:52 -0700 (PDT)
From: Wes Hardaker <wjhns1@hardakers.net>
To: "t.petch" <ietfc@btconnect.com>
Organization: Sparta
References: <20100917082039.GA47046@elstar.local> <CCBEBEBD3ED849FCA53890C5792FD42B@23FX1C1> <20100917101102.GA47610@elstar.local> <4C9371A6.6040106@cisco.com> <DC81494673134E448B019A3F0A41166B@23FX1C1> <EDC652A26FB23C4EB6384A4584434A040256FEC0@307622ANEX5.global.avaya.com> <000b01cb5895$868c3ca0$4001a8c0@gateway.2wire.net> <sdlj6w1cj2.fsf@wjh.hardakers.net> <003901cb5902$d5627fc0$4001a8c0@gateway.2wire.net>
Date: Mon, 20 Sep 2010 17:30:52 -0700
In-Reply-To: <003901cb5902$d5627fc0$4001a8c0@gateway.2wire.net> (t. petch's message of "Mon, 20 Sep 2010 22:31:33 +0200")
Message-ID: <sdlj6wvsxv.fsf@wjh.hardakers.net>
User-Agent: Gnus/5.110011 (No Gnus v0.11) Emacs/23.2 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
Cc: isms <isms@ietf.org>, Ron Bonica <rbonica@juniper.net>, ops-area@ietf.org
Subject: Re: [Isms] status and future of the isms working group
X-BeenThere: isms@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mailing list for the ISMS working group <isms.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isms>
List-Post: <mailto:isms@ietf.org>
List-Help: <mailto:isms-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Sep 2010 00:30:32 -0000

>>>>> On Mon, 20 Sep 2010 22:31:33 +0200, "t.petch" <ietfc@btconnect.com> said:

tp> And yes, I am making my point quite strongly, because I think that
tp> an 'RFC6411' would be a poor use of IETF resources.

Well, I won't dive into "sessions" because it's way beyond a useful
argument at this point.

But, I will agree I don't think the WG should go down the path of
defining a new architecture.  It just won't help much.

As I've said before, I think it's more important that developers can or
can't make the changes need to create a feature.  The architecture was a
way to say "if you can make the architecture bend in this way, then all
the implementations should".  But because we can, in general, enumerate
the SNMPv3 stack implementations on one hand it's not hard to survey
them and say "could you implement this new feature of the protocol in
your implementation"?

Trying to define a model that will always account for every way you
might need to break the rules in the future is an impossible task.
-- 
Wes Hardaker
Cobham Analytic Solutions

From j.schoenwaelder@jacobs-university.de  Mon Sep 20 23:56:25 2010
Return-Path: <j.schoenwaelder@jacobs-university.de>
X-Original-To: isms@core3.amsl.com
Delivered-To: isms@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 56E6C3A6953 for <isms@core3.amsl.com>; Mon, 20 Sep 2010 23:56:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.937
X-Spam-Level: 
X-Spam-Status: No, score=-100.937 tagged_above=-999 required=5 tests=[AWL=-0.700, BAYES_00=-2.599, FAKE_REPLY_C=2.012, HELO_EQ_DE=0.35, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id euEkrcPK66F8 for <isms@core3.amsl.com>; Mon, 20 Sep 2010 23:56:24 -0700 (PDT)
Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) by core3.amsl.com (Postfix) with ESMTP id 3E7D63A67BD for <isms@ietf.org>; Mon, 20 Sep 2010 23:56:24 -0700 (PDT)
Received: from localhost (demetrius2.jacobs-university.de [212.201.44.47]) by hermes.jacobs-university.de (Postfix) with ESMTP id B0340C0004 for <isms@ietf.org>; Tue, 21 Sep 2010 08:56:47 +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 Mdt8NA+0sI6z for <isms@ietf.org>; Tue, 21 Sep 2010 08:56:46 +0200 (CEST)
Received: from elstar.local (elstar.iuhb02.iu-bremen.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id A3571C0002 for <isms@ietf.org>; Tue, 21 Sep 2010 08:56:46 +0200 (CEST)
Received: by elstar.local (Postfix, from userid 501) id E057014E2B54; Tue, 21 Sep 2010 08:56:23 +0200 (CEST)
Resent-From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
Resent-Date: Tue, 21 Sep 2010 08:56:23 +0200
Resent-Message-ID: <20100921065623.GC69973@elstar.local>
Resent-To: isms@ietf.org
Received: from SHUBCAS03.jacobs.jacobs-university.de (10.70.0.128) by SHUBCAS01.jacobs.jacobs-university.de (10.70.0.122) with Microsoft SMTP Server (TLS) id 8.2.254.0; Tue, 21 Sep 2010 08:36:51 +0200
Received: from hermes.jacobs-university.de (212.201.44.23) by shubcas03.jacobs.jacobs-university.de (10.70.0.128) with Microsoft SMTP Server id 14.1.218.12; Tue, 21 Sep 2010 08:36:47 +0200
Received: from localhost (demetrius4.jacobs-university.de [212.201.44.49])	by hermes.jacobs-university.de (Postfix) with ESMTP id A40BBC0015	for <j.schoenwaelder@jacobs-university.de>; Tue, 21 Sep 2010 08:36:46 +0200 (CEST)
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 xaoGDTKP0cgo; Tue, 21 Sep 2010 08:36:46 +0200 (CEST)
Received: from elstar.local (elstar.iuhb02.iu-bremen.de [10.50.231.133])	by hermes.jacobs-university.de (Postfix) with ESMTP id 019E4C000C; Tue, 21 Sep 2010 08:36:45 +0200 (CEST)
Received: by elstar.local (Postfix, from userid 501)	id 0B45A14E2A51; Tue, 21 Sep 2010 08:36:21 +0200 (CEST)
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: Wes Hardaker <wjhns1@hardakers.net>
Date: Tue, 21 Sep 2010 08:36:21 +0200
Thread-Topic: [OPS-AREA] status and future of the isms working group
Thread-Index: ActZV1/nnBM4mTnNQqClcR3CRlwoLw==
Message-ID: <20100921063621.GA69973@elstar.local>
In-Reply-To: <sdlj6wvsxv.fsf@wjh.hardakers.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Exchange-Organization-AuthAs: Anonymous
X-MS-Exchange-Organization-AuthSource: SHUBCAS03.jacobs.jacobs-university.de
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Mutt/1.5.21 (2010-09-15)
x-virus-scanned: amavisd-new at jacobs-university.de
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [Isms] [OPS-AREA] status and future of the isms working group
X-BeenThere: isms@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: =?iso-8859-1?Q?Sch=F6nw=E4lder=2C_J=FCrgen?= <j.schoenwaelder@jacobs-university.de>
List-Id: Mailing list for the ISMS working group <isms.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isms>
List-Post: <mailto:isms@ietf.org>
List-Help: <mailto:isms-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Sep 2010 06:56:25 -0000

On Tue, Sep 21, 2010 at 02:30:52AM +0200, Wes Hardaker wrote:
=20
> But, I will agree I don't think the WG should go down the path of
> defining a new architecture.  It just won't help much.

The ISMS working group is not going to do any architecture work. This
is way out of the scope of the ISMS charter. Hence, I would appreciate
if any followup discussion of the SNMP architecture or the lack of a
multiprotocol network management architecture moves to the
<ops-area@ietf.org> mailing list.

Summarizing the discussion so far, I have only seen a proposal to
extend the ISMS lifetime in order to move some of the WG RFCs to Draft
Standard. There are two independent implementations and
interoperability testing is ongoing. If others are implementing or
planning to do so very soon, this would be nice to know.

/js

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

From ietfc@btconnect.com  Tue Sep 21 08:22:59 2010
Return-Path: <ietfc@btconnect.com>
X-Original-To: isms@core3.amsl.com
Delivered-To: isms@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1D2573A696D; Tue, 21 Sep 2010 08:22:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.958
X-Spam-Level: 
X-Spam-Status: No, score=-1.958 tagged_above=-999 required=5 tests=[AWL=0.641,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KxNLHDKFjky7; Tue, 21 Sep 2010 08:22:57 -0700 (PDT)
Received: from c2beaomr02.btconnect.com (c2beaomr02.btconnect.com [213.123.26.180]) by core3.amsl.com (Postfix) with ESMTP id 2AD0F3A6964; Tue, 21 Sep 2010 08:22:56 -0700 (PDT)
Received: from pc6 (host217-44-4-171.range217-44.btcentralplus.com [217.44.4.171]) by c2beaomr02.btconnect.com with SMTP id EEL35888; Tue, 21 Sep 2010 16:23:08 +0100 (BST)
X-Mirapoint-IP-Reputation: reputation=Fair-1, source=Queried, refid=0001.0A0B0301.4C98CDDC.0295, actions=TAG
Message-ID: <012201cb5998$7a0d8ac0$4001a8c0@gateway.2wire.net>
From: "t.petch" <ietfc@btconnect.com>
To: "Jon Saperia" <saperia@jdscons.com>, "Randy Presuhn" <randy_presuhn@mindspring.com>
References: <20100917082039.GA47046@elstar.local>	<CCBEBEBD3ED849FCA53890C5792FD42B@23FX1C1><20100917101102.GA47610@elstar.local><4C9371A6.6040106@cisco.com><DC81494673134E448B019A3F0A41166B@23FX1C1><EDC652A26FB23C4EB6384A4584434A040256FEC0@307622ANEX5.global.avaya.com><000b01cb5895$868c3ca0$4001a8c0@gateway.2wire.net><EDC652A26FB23C4EB6384A4584434A0402570133@307622ANEX5.global.avaya.com><0b4b01cb58aa$4cd4f320$4001a8c0@gateway.2wire.net><003c01cb58e5$e95359e0$6801a8c0@oemcomputer> <4FB2A2E7-04E3-4604-B709-36A0E2F809B2@jdscons.com>
Date: Tue, 21 Sep 2010 16:22:42 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Junkmail-Status: score=10/50, host=c2beaomr02.btconnect.com
X-Junkmail-SD-Raw: score=unknown, refid=str=0001.0A0B0207.4C98CDE4.00C4,ss=1,fgs=0, ip=0.0.0.0, so=2009-07-20 21:54:04, dmn=5.7.1/2009-08-27, mode=single engine
X-Junkmail-IWF: false
Cc: isms <isms@ietf.org>, ops-area@ietf.org
Subject: Re: [Isms] [OPS-AREA]  status and future of the isms working group
X-BeenThere: isms@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mailing list for the ISMS working group <isms.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isms>
List-Post: <mailto:isms@ietf.org>
List-Help: <mailto:isms-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Sep 2010 15:22:59 -0000

----- Original Message -----
From: "Jon Saperia" <saperia@jdscons.com>
To: "Randy Presuhn" <randy_presuhn@mindspring.com>
Cc: <isms@ietf.org>; <ops-area@ietf.org>
Sent: Monday, September 20, 2010 7:43 PM

> I could not agree more.
>
> I would add  that additional protocol/architecture/framework on any of the
management infrastructures we have does not address the key point I took from
Randy's post.  What we need are widely implemented objects (however you want to
call the structures) that give real visibility into what is going on in the
devices and networks.  That has always been the problem and until we address
that who cares how we transport the data. I would settle for RFC2549, if it
contained the right information.
>
Jon

My current hot button is not data but protocols.  I am worried about the
explosion in 'OAM' (ie ping, traceroute etc) protocols to run in the MPLS
dataplane, that are being defined in the MPLS-TP nexus.  Before long, we might
have Y.1731 as a standards track RFC:-(

I was relieved to see the IESG sending back
draft-ietf-opsawg-mpls-tp-oam-def
but what happens next, metaphorically speaking? I would rather more people with
a background in the IETF were involved with this.

Tom Petch

> /jon
> On Sep 20, 2010, at 1:04 PM, Randy Presuhn wrote:
>
> > Hi -
> >
> >> From: "t.petch" <ietfc@btconnect.com>
> > ...
> >> I think that our resources are limited, and tend to decay with the age of a
> >> working group, so I would rather see them applied elsewhere.  I look back
at the
> >> effort that went into RFC3411, over many years, and yet it fell at the
first
> >> hurdle, not accommodating the move of security from deep inside the engine
to
> >> off the bottom of the radar; why should we do any better this time?
> > ...
> >
> > The problem as I see it was that RFC3411 was intended to be the glue
> > describing how a particular set of specifications fit together, *not* as
> > *the* architecture for all future SNMP work.  *Requiring* extensions,
> > additions, and embellishments to adhere to that architecture is in
> > my opinion a huge mistake.  From my perspective, the real problem
> > addressed by RFC 3411 was that some of the preceding proposals
> > for securing SNMP had so many convolutions and interactions that
> > a lot of folks had trouble wrapping their heads around them.  The
> > modularity brought by RFC 3411 was modularity of *specification*,
> > not necessarily implementation.  The ASIs were rather controversial
> > because folks were (rightly, in retrospect) concerned that they would
> > be understood in a prescriptive sense, rather than descriptive sense
> > in which they were intended.
> >
> > More importantly, I think focusing energy on this "problem" (which is
> > tempting because it's something we think we understand) would be
> > a huge distraction from the *real* problem: the kinds of information models
> > this infrastructure should provide access to.  If the information models
> > can't support the high-value functions administrators / operators need,
> > then embellishing the protocol engine architecture is a waste of time.
> >
> > Randy
> >
> > _______________________________________________
> > OPS-AREA mailing list
> > OPS-AREA@ietf.org
> > https://www.ietf.org/mailman/listinfo/ops-area
> >
>
> _______________________________________________
> OPS-AREA mailing list
> OPS-AREA@ietf.org
> https://www.ietf.org/mailman/listinfo/ops-area


From j.schoenwaelder@jacobs-university.de  Wed Sep 22 23:13:26 2010
Return-Path: <j.schoenwaelder@jacobs-university.de>
X-Original-To: isms@core3.amsl.com
Delivered-To: isms@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id ED4073A6ABF for <isms@core3.amsl.com>; Wed, 22 Sep 2010 23:13:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.937
X-Spam-Level: 
X-Spam-Status: No, score=-101.937 tagged_above=-999 required=5 tests=[AWL=0.312, BAYES_00=-2.599, HELO_EQ_DE=0.35, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id x5bJjaMgwfI0 for <isms@core3.amsl.com>; Wed, 22 Sep 2010 23:13:24 -0700 (PDT)
Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) by core3.amsl.com (Postfix) with ESMTP id 574FB3A6AC0 for <isms@ietf.org>; Wed, 22 Sep 2010 23:13:24 -0700 (PDT)
Received: from localhost (demetrius3.jacobs-university.de [212.201.44.48]) by hermes.jacobs-university.de (Postfix) with ESMTP id 6FF84C0015 for <isms@ietf.org>; Thu, 23 Sep 2010 08:13:52 +0200 (CEST)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius3.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id AiDVc16iPYPi; Thu, 23 Sep 2010 08:13:50 +0200 (CEST)
Received: from elstar.local (elstar.iuhb02.iu-bremen.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id 84413C000D; Thu, 23 Sep 2010 08:13:50 +0200 (CEST)
Received: by elstar.local (Postfix, from userid 501) id 0927D14E89E2; Thu, 23 Sep 2010 08:13:19 +0200 (CEST)
Date: Thu, 23 Sep 2010 08:13:19 +0200
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: isms@ietf.org
Message-ID: <20100923061319.GA25787@elstar.local>
Mail-Followup-To: isms@ietf.org
References: <20100917082039.GA47046@elstar.local>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20100917082039.GA47046@elstar.local>
User-Agent: Mutt/1.5.21 (2010-09-15)
Subject: Re: [Isms] status and future of the isms working group
X-BeenThere: isms@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
List-Id: Mailing list for the ISMS working group <isms.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isms>
List-Post: <mailto:isms@ietf.org>
List-Help: <mailto:isms-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Sep 2010 06:13:26 -0000

On Fri, Sep 17, 2010 at 10:20:39AM +0200, Juergen Schoenwaelder wrote:
 
> If you think some other work should be undertaken by this WG, people
> start a thread on the mailing list where you propose the work to be
> done and where we can get a discussion going to see how much support
> there is in the WG and how many people are willing to commit to help
> with document editing and document reviewing tasks. As we have learned
> here several times, writing SNMP specifications is not an easy task
> given the architectural and terminology framework we are working
> with. It is thus crucial to have sufficient people involved in the
> reviewing and wordsmithing as well as the work needed to originally
> produce and edit the specifications.

Summarizing the discussion so far, I have only seen a proposal to
extend the ISMS lifetime in order to move some of the WG RFCs to Draft
Standard. There are two independent implementations and
interoperability testing is ongoing. If others are implementing or
planning to do so very soon, this would be nice to know.

Since advancement of the SNMP over [D]TLS specification has to wait
until early next year, I do not plan to ask for a WG meeting slot at
the upcoming IETF in Beijing. If you believe a WG meeting is needed,
speak up as soon as possible but no later than Sunday September 26th.

/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 rajaram_pejaver@cable.comcast.com  Fri Sep 24 08:16:00 2010
Return-Path: <rajaram_pejaver@cable.comcast.com>
X-Original-To: isms@core3.amsl.com
Delivered-To: isms@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8AFBB3A6ADF for <isms@core3.amsl.com>; Fri, 24 Sep 2010 08:16:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.258
X-Spam-Level: 
X-Spam-Status: No, score=-107.258 tagged_above=-999 required=5 tests=[AWL=1.205, BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Bhf2pOo4pIFN for <isms@core3.amsl.com>; Fri, 24 Sep 2010 08:15:58 -0700 (PDT)
Received: from pacdcimo01.cable.comcast.com (PacdcIMO01.cable.comcast.com [24.40.8.145]) by core3.amsl.com (Postfix) with ESMTP id 8960C3A69EA for <isms@ietf.org>; Fri, 24 Sep 2010 08:15:58 -0700 (PDT)
Received: from ([24.40.55.41]) by pacdcimo01.cable.comcast.com with ESMTP with TLS id 5503620.94429886; Fri, 24 Sep 2010 11:16:29 -0400
Received: from pacdcexcmb05.cable.comcast.com (24.40.15.116) by PACDCEXHUB02.cable.comcast.com (24.40.55.41) with Microsoft SMTP Server id 14.1.218.12; Fri, 24 Sep 2010 11:16:29 -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: Fri, 24 Sep 2010 11:16:03 -0400
Message-ID: <029A504294520A4F84113D5C45B65A5202CCF061@pacdcexcmb05.cable.comcast.com>
In-Reply-To: <20100923061319.GA25787@elstar.local>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Isms] status and future of the isms working group
Thread-Index: Acta5oS8g8X3iXk0RdifxpfS3cOaigBE/Agw
References: <20100917082039.GA47046@elstar.local> <20100923061319.GA25787@elstar.local>
From: "Pejaver, Rajaram" <Rajaram_Pejaver@cable.comcast.com>
To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>, <isms@ietf.org>
Subject: Re: [Isms] status and future of the isms working group
X-BeenThere: isms@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mailing list for the ISMS working group <isms.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isms>
List-Post: <mailto:isms@ietf.org>
List-Help: <mailto:isms-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Sep 2010 15:16:00 -0000

Juergen,

At Comcast, we are interested in defining the KSM security model.
An initial draft proposal was submitted to this WG on July 7, 2010.
A copy is at
http://www.lee-networks.com/draft-pejaver-isms-kerberos-00.txt

We are implementing it and expect to test it soon.
If it is successful, we will require our vendors to support it.
We would like the ISMS WG to consider adopting this work.

Besides Comcast, we have a working group hosted by CableLabs addressing
this issue.
This WG consists of several Cable companies, including Cablevision, Cox,
& Time Warner.

Regards

Rajaram Pejaver & Yiu Lee
Comcast Cable



-----Original Message-----
From: isms-bounces@ietf.org [mailto:isms-bounces@ietf.org] On Behalf Of
Juergen Schoenwaelder
Sent: Thursday, September 23, 2010 2:13 AM
To: isms@ietf.org
Subject: Re: [Isms] status and future of the isms working group

On Fri, Sep 17, 2010 at 10:20:39AM +0200, Juergen Schoenwaelder wrote:
=20
> If you think some other work should be undertaken by this WG, people
> start a thread on the mailing list where you propose the work to be
> done and where we can get a discussion going to see how much support
> there is in the WG and how many people are willing to commit to help
> with document editing and document reviewing tasks. As we have learned
> here several times, writing SNMP specifications is not an easy task
> given the architectural and terminology framework we are working
> with. It is thus crucial to have sufficient people involved in the
> reviewing and wordsmithing as well as the work needed to originally
> produce and edit the specifications.

Summarizing the discussion so far, I have only seen a proposal to
extend the ISMS lifetime in order to move some of the WG RFCs to Draft
Standard. There are two independent implementations and
interoperability testing is ongoing. If others are implementing or
planning to do so very soon, this would be nice to know.

Since advancement of the SNMP over [D]TLS specification has to wait
until early next year, I do not plan to ask for a WG meeting slot at
the upcoming IETF in Beijing. If you believe a WG meeting is needed,
speak up as soon as possible but no later than Sunday September 26th.

/js

--=20
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: +49 421 200 3587         Campus Ring 1, 28759 Bremen, Germany
Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>
_______________________________________________
Isms mailing list
Isms@ietf.org
https://www.ietf.org/mailman/listinfo/isms

From dnelson@elbrys.com  Fri Sep 24 11:00:19 2010
Return-Path: <dnelson@elbrys.com>
X-Original-To: isms@core3.amsl.com
Delivered-To: isms@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 38D5B3A69EC for <isms@core3.amsl.com>; Fri, 24 Sep 2010 11:00:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BprO-Ehd4bpt for <isms@core3.amsl.com>; Fri, 24 Sep 2010 11:00:18 -0700 (PDT)
Received: from na3sys009aog101.obsmtp.com (na3sys009aog101.obsmtp.com [74.125.149.67]) by core3.amsl.com (Postfix) with SMTP id C46373A69C1 for <isms@ietf.org>; Fri, 24 Sep 2010 11:00:17 -0700 (PDT)
Received: from source ([209.85.216.170]) by na3sys009aob101.postini.com ([74.125.148.12]) with SMTP ID DSNKTJznUemZHGmpj7RDY1I8X+rYoRRN8zyU@postini.com; Fri, 24 Sep 2010 11:00:50 PDT
Received: by mail-qy0-f170.google.com with SMTP id 35so1699745qyk.8 for <isms@ietf.org>; Fri, 24 Sep 2010 11:00:49 -0700 (PDT)
Received: by 10.224.28.71 with SMTP id l7mr2688488qac.318.1285351248788; Fri, 24 Sep 2010 11:00:48 -0700 (PDT)
Received: from dbn-imac.elbrysnetworks.com (host171.elbrysnetworks.com [64.140.243.171]) by mx.google.com with ESMTPS id l13sm2610980qck.7.2010.09.24.11.00.47 (version=SSLv3 cipher=RC4-MD5); Fri, 24 Sep 2010 11:00:48 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=us-ascii
From: "David B. Nelson" <dnelson@elbrys.com>
In-Reply-To: <029A504294520A4F84113D5C45B65A5202CCF061@pacdcexcmb05.cable.comcast.com>
Date: Fri, 24 Sep 2010 14:00:42 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <4ADC042A-C5AC-4B15-99CC-7C0DE5BF3E7F@elbrys.com>
References: <20100917082039.GA47046@elstar.local> <20100923061319.GA25787@elstar.local> <029A504294520A4F84113D5C45B65A5202CCF061@pacdcexcmb05.cable.comcast.com>
To: "Pejaver, Rajaram" <Rajaram_Pejaver@cable.comcast.com>
X-Mailer: Apple Mail (2.1081)
Cc: isms@ietf.org
Subject: Re: [Isms] status and future of the isms working group
X-BeenThere: isms@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mailing list for the ISMS working group <isms.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isms>
List-Post: <mailto:isms@ietf.org>
List-Help: <mailto:isms-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Sep 2010 18:00:19 -0000

On Sep 24, 2010, at 11:16 AM, Pejaver, Rajaram wrote:

> At Comcast, we are interested in defining the KSM security model.
> An initial draft proposal was submitted to this WG on July 7, 2010.
> A copy is at
> http://www.lee-networks.com/draft-pejaver-isms-kerberos-00.txt

Comments the content of the draft:

   SNMPv3 allows the definition of new security models.  The first
   security models [I-D.ietf-isms-radius-vacm] defined, USM and VACM,
   did not support centralized security administration.

DBN:  [I-D.ietf-isms-radius-vacm] is not a reasonable reference for =
"first security models".

   Recent work based on session based approaches are not=20
   suitable for large networks containing untrusted managed devices.

DBN: Can your provide a technical justification for this assertion?

   Ideally, RADIUS and Two factor authentication should be invoked only
   once when the administrator is "logging in".  These services should
   not be invoked each time a different managed device is selected.  If
   RADIUS is the source of authorization information, then this
   information should be cached somewhere.  Alternatively, it can be
   inserted into the AuthorizationData field in the TGT.  Thereafter,
   this data can be copied from the TGT into each service ticket.

DBN:  This section seems a bit sketchy.  Does it intent to indicate any =
actual integration between RADIUS and Kerberos, e.g. a shard back-end =
user/principal and authorization database?



From j.schoenwaelder@jacobs-university.de  Fri Sep 24 12:23:12 2010
Return-Path: <j.schoenwaelder@jacobs-university.de>
X-Original-To: isms@core3.amsl.com
Delivered-To: isms@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D09EB3A6B29 for <isms@core3.amsl.com>; Fri, 24 Sep 2010 12:23:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.954
X-Spam-Level: 
X-Spam-Status: No, score=-101.954 tagged_above=-999 required=5 tests=[AWL=0.295, BAYES_00=-2.599, HELO_EQ_DE=0.35, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4J+67RUGq6Y2 for <isms@core3.amsl.com>; Fri, 24 Sep 2010 12:23:11 -0700 (PDT)
Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) by core3.amsl.com (Postfix) with ESMTP id AB4E73A6783 for <isms@ietf.org>; Fri, 24 Sep 2010 12:23:11 -0700 (PDT)
Received: from localhost (demetrius2.jacobs-university.de [212.201.44.47]) by hermes.jacobs-university.de (Postfix) with ESMTP id A6EDFC0016; Fri, 24 Sep 2010 21:23:43 +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 iq18zCxzl8f9; Fri, 24 Sep 2010 21:23:43 +0200 (CEST)
Received: from elstar.local (elstar.iuhb02.iu-bremen.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id D2EFEC0008; Fri, 24 Sep 2010 21:23:39 +0200 (CEST)
Received: by elstar.local (Postfix, from userid 501) id 426D614ECECF; Fri, 24 Sep 2010 21:23:09 +0200 (CEST)
Date: Fri, 24 Sep 2010 21:23:09 +0200
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: "Pejaver, Rajaram" <Rajaram_Pejaver@cable.comcast.com>
Message-ID: <20100924192309.GA39384@elstar.local>
Mail-Followup-To: "Pejaver, Rajaram" <Rajaram_Pejaver@cable.comcast.com>, "isms@ietf.org" <isms@ietf.org>
References: <20100917082039.GA47046@elstar.local> <20100923061319.GA25787@elstar.local> <029A504294520A4F84113D5C45B65A5202CCF061@pacdcexcmb05.cable.comcast.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <029A504294520A4F84113D5C45B65A5202CCF061@pacdcexcmb05.cable.comcast.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: "isms@ietf.org" <isms@ietf.org>
Subject: Re: [Isms] status and future of the isms working group
X-BeenThere: isms@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
List-Id: Mailing list for the ISMS working group <isms.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isms>
List-Post: <mailto:isms@ietf.org>
List-Help: <mailto:isms-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Sep 2010 19:23:12 -0000

On Fri, Sep 24, 2010 at 05:16:03PM +0200, Pejaver, Rajaram wrote:
> Juergen,
> 
> At Comcast, we are interested in defining the KSM security model.
> An initial draft proposal was submitted to this WG on July 7, 2010.
> A copy is at
> http://www.lee-networks.com/draft-pejaver-isms-kerberos-00.txt
> 
> We are implementing it and expect to test it soon.
> If it is successful, we will require our vendors to support it.
> We would like the ISMS WG to consider adopting this work.
> 
> Besides Comcast, we have a working group hosted by CableLabs addressing
> this issue.
> This WG consists of several Cable companies, including Cablevision, Cox,
> & Time Warner.

So will this group contribute actively to the work of ISMS or will it
remain a closed group at CableLabs? As said earlier, we need to make
sure we have sufficient human resources available for any new work.
It will also help if you can come up with a suggested timeline for
this work.

/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 yiu_lee@cable.comcast.com  Fri Sep 24 12:28:26 2010
Return-Path: <yiu_lee@cable.comcast.com>
X-Original-To: isms@core3.amsl.com
Delivered-To: isms@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 942203A6978 for <isms@core3.amsl.com>; Fri, 24 Sep 2010 12:28:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.529
X-Spam-Level: 
X-Spam-Status: No, score=-103.529 tagged_above=-999 required=5 tests=[AWL=2.867, BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, RCVD_IN_DNSWL_HI=-8, RCVD_NUMERIC_HELO=2.067, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kMvIAI0rBNth for <isms@core3.amsl.com>; Fri, 24 Sep 2010 12:28:25 -0700 (PDT)
Received: from pacdcimo01.cable.comcast.com (PacdcIMO01.cable.comcast.com [24.40.8.145]) by core3.amsl.com (Postfix) with ESMTP id 7FEF13A6783 for <isms@ietf.org>; Fri, 24 Sep 2010 12:28:25 -0700 (PDT)
Received: from ([24.40.55.41]) by pacdcimo01.cable.comcast.com with ESMTP with TLS id 5503620.94486690; Fri, 24 Sep 2010 15:28:54 -0400
Received: from PACDCEXCMB04.cable.comcast.com (24.40.15.86) by PACDCEXHUB02.cable.comcast.com (24.40.55.41) with Microsoft SMTP Server id 14.1.218.12; Fri, 24 Sep 2010 15:28:54 -0400
Received: from 68.81.91.8 ([68.81.91.8]) by PACDCEXCMB04.cable.comcast.com ([24.40.15.86]) via Exchange Front-End Server legacywebmail.comcast.com ([24.40.8.154]) with Microsoft Exchange Server HTTP-DAV ; Fri, 24 Sep 2010 19:28:48 +0000
User-Agent: Microsoft-Entourage/12.26.0.100708
Date: Fri, 24 Sep 2010 15:28:48 -0400
From: "Yiu L. Lee" <yiu_lee@cable.comcast.com>
To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>, "Pejaver, Rajaram" <Rajaram_Pejaver@cable.comcast.com>
Message-ID: <C8C27430.3E6DF%yiu_lee@cable.comcast.com>
Thread-Topic: [Isms] status and future of the isms working group
Thread-Index: ActcHrXbxoclQHOiRUCpzjracBcSlA==
In-Reply-To: <20100924192309.GA39384@elstar.local>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Cc: "isms@ietf.org" <isms@ietf.org>
Subject: Re: [Isms] status and future of the isms working group
X-BeenThere: isms@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mailing list for the ISMS working group <isms.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isms>
List-Post: <mailto:isms@ietf.org>
List-Help: <mailto:isms-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Sep 2010 19:28:26 -0000

Hi Juergen,

We would like to make it as openly as possible. This is why we submitted the
draft to IETF. We also like to see any other in the WG is also interested in
this work.

>From the timeline perspective, we would like the WG would adopt this a WG
item (if we get enough interested people) this year and WGLC Q1/Q2 next
year. Do you think this timeline reasonable?

Thanks,
Yiu


On 9/24/10 3:23 PM, "Juergen Schoenwaelder"
<j.schoenwaelder@jacobs-university.de> wrote:

> On Fri, Sep 24, 2010 at 05:16:03PM +0200, Pejaver, Rajaram wrote:
>
> So will this group contribute actively to the work of ISMS or will it
> remain a closed group at CableLabs? As said earlier, we need to make
> sure we have sufficient human resources available for any new work.
> It will also help if you can come up with a suggested timeline for
> this work.
> 
> /js


From wjhns1@hardakers.net  Fri Sep 24 13:07:15 2010
Return-Path: <wjhns1@hardakers.net>
X-Original-To: isms@core3.amsl.com
Delivered-To: isms@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 891473A6B54 for <isms@core3.amsl.com>; Fri, 24 Sep 2010 13:07:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.887
X-Spam-Level: 
X-Spam-Status: No, score=-1.887 tagged_above=-999 required=5 tests=[AWL=-0.702, BAYES_40=-0.185, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D5c2t0mGEZyk for <isms@core3.amsl.com>; Fri, 24 Sep 2010 13:04:58 -0700 (PDT)
Received: from mail.hardakers.net (mail.hardakers.net [168.150.236.43]) by core3.amsl.com (Postfix) with ESMTP id 4C8B53A69B5 for <isms@ietf.org>; Fri, 24 Sep 2010 13:04:58 -0700 (PDT)
Received: from localhost (wjh.hardakers.net [10.0.0.2]) by mail.hardakers.net (Postfix) with ESMTPSA id 4536C98067; Fri, 24 Sep 2010 13:05:08 -0700 (PDT)
From: Wes Hardaker <wjhns1@hardakers.net>
To: "Pejaver\, Rajaram" <Rajaram_Pejaver@cable.comcast.com>
Organization: Sparta
References: <20100917082039.GA47046@elstar.local> <20100923061319.GA25787@elstar.local> <029A504294520A4F84113D5C45B65A5202CCF061@pacdcexcmb05.cable.comcast.com> <20100924192309.GA39384@elstar.local>
Date: Fri, 24 Sep 2010 13:05:08 -0700
In-Reply-To: <20100924192309.GA39384@elstar.local> (Juergen Schoenwaelder's message of "Fri, 24 Sep 2010 21:23:09 +0200")
Message-ID: <sdsk0y52mj.fsf@wjh.hardakers.net>
User-Agent: Gnus/5.110011 (No Gnus v0.11) Emacs/23.2 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
Cc: "isms@ietf.org" <isms@ietf.org>
Subject: Re: [Isms] status and future of the isms working group
X-BeenThere: isms@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mailing list for the ISMS working group <isms.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isms>
List-Post: <mailto:isms@ietf.org>
List-Help: <mailto:isms-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Sep 2010 20:07:15 -0000

>>>>> On Fri, 24 Sep 2010 21:23:09 +0200, Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de> said:

JS> So will this group contribute actively to the work of ISMS or will it
JS> remain a closed group at CableLabs? As said earlier, we need to make
JS> sure we have sufficient human resources available for any new work.

I'd like to see the work continue through the WG and would be willing to
read/review the document.
-- 
Wes Hardaker
Cobham Analytic Solutions

From rajaram_pejaver@cable.comcast.com  Fri Sep 24 13:24:57 2010
Return-Path: <rajaram_pejaver@cable.comcast.com>
X-Original-To: isms@core3.amsl.com
Delivered-To: isms@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3FADD3A69CA for <isms@core3.amsl.com>; Fri, 24 Sep 2010 13:24:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.502
X-Spam-Level: 
X-Spam-Status: No, score=-107.502 tagged_above=-999 required=5 tests=[AWL=0.646, BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, RCVD_IN_DNSWL_HI=-8, SARE_MILLIONSOF=0.315, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Puq9V+u9baoW for <isms@core3.amsl.com>; Fri, 24 Sep 2010 13:24:56 -0700 (PDT)
Received: from pacdcimo01.cable.comcast.com (PacdcIMO01.cable.comcast.com [24.40.8.145]) by core3.amsl.com (Postfix) with ESMTP id 08E383A67D4 for <isms@ietf.org>; Fri, 24 Sep 2010 13:24:55 -0700 (PDT)
Received: from ([24.40.55.40]) by pacdcimo01.cable.comcast.com with ESMTP with TLS id 5503620.94498317; Fri, 24 Sep 2010 16:25:24 -0400
Received: from pacdcexcmb05.cable.comcast.com (24.40.15.116) by pacdcexhub03.cable.comcast.com (24.40.55.40) with Microsoft SMTP Server id 14.1.218.12; Fri, 24 Sep 2010 16:25:24 -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: Fri, 24 Sep 2010 16:24:29 -0400
Message-ID: <029A504294520A4F84113D5C45B65A5202D7EEB2@pacdcexcmb05.cable.comcast.com>
In-Reply-To: <4ADC042A-C5AC-4B15-99CC-7C0DE5BF3E7F@elbrys.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Isms] status and future of the isms working group
Thread-Index: ActcEnJHycGdADFLTF+vbuPhtg4a0wADeDTg
References: <20100917082039.GA47046@elstar.local> <20100923061319.GA25787@elstar.local> <029A504294520A4F84113D5C45B65A5202CCF061@pacdcexcmb05.cable.comcast.com> <4ADC042A-C5AC-4B15-99CC-7C0DE5BF3E7F@elbrys.com>
From: "Pejaver, Rajaram" <Rajaram_Pejaver@cable.comcast.com>
To: "David B. Nelson" <dnelson@elbrys.com>
Cc: isms@ietf.org
Subject: Re: [Isms] status and future of the isms working group
X-BeenThere: isms@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mailing list for the ISMS working group <isms.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isms>
List-Post: <mailto:isms@ietf.org>
List-Help: <mailto:isms-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Sep 2010 20:24:57 -0000

David,

>    SNMPv3 allows the definition of new security models.  The first
>    security models [I-D.ietf-isms-radius-vacm] defined, USM and VACM,
>    did not support centralized security administration.
>
> DBN:  [I-D.ietf-isms-radius-vacm] is not a reasonable reference for
"first security models".

Agreed.  It should have been RFC3414 USM.

>    Recent work based on session based approaches are not=20
>    suitable for large networks containing untrusted managed devices.
>
> DBN: Can you provide a technical justification for this assertion?

Our target devices include millions of Cable Modems and TV Set top
boxes.
An ssh session involves sending an administrator's ID & password to the
modem so that it can do RADIUS authentication.
These devices which reside in our customer's homes may have been
compromised and cannot be trusted with admin credentials.
GSSAPI helps, but may not work if authorization values are to be
retrieved from RADIUS as in draft-ietf-isms-radius-vacm.
Also, every managed device would need to be a RADIUS client.

An ssh session requires establishing a TCP connection and exchanging a
few packets to set up the ssh session.
When we want to periodically poll many devices for a SNMP status
snapshot, a simple UDP request & response is more preferable.

Lastly, for low end devices like CPE bridges, it would be nice if they
did not need to maintain state between SNMP requests.

>
>    Ideally, RADIUS and Two factor authentication should be invoked
only
>    once when the administrator is "logging in".  These services should
>    not be invoked each time a different managed device is selected.
If
>    RADIUS is the source of authorization information, then this
>    information should be cached somewhere.  Alternatively, it can be
>    inserted into the AuthorizationData field in the TGT.  Thereafter,
>    this data can be copied from the TGT into each service ticket.
>
> DBN:  This section seems a bit sketchy.  Does it intent to indicate
any actual integration between RADIUS and Kerberos, e.g. a shard
back-end user/principal and authorization database?

Agreed.  We suggest that the initial proposal not deal with RADIUS and
2factor authentication.  I was trying to describe the flow in an ideal
situation.
We have ideas for how to integrate Kerberos & RADIUS, and would be glad
to present them, but it is a whole different discussion.  (It would also
need to be prototyped)
It is much easier to integrate a stock Kerberos server with a vanilla
LDAP based authorization database.

Regards

Rajaram Pejaver
Comcast Cable, NETO

From j.schoenwaelder@jacobs-university.de  Fri Sep 24 13:27:26 2010
Return-Path: <j.schoenwaelder@jacobs-university.de>
X-Original-To: isms@core3.amsl.com
Delivered-To: isms@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7CD603A6A45 for <isms@core3.amsl.com>; Fri, 24 Sep 2010 13:27:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.956
X-Spam-Level: 
X-Spam-Status: No, score=-101.956 tagged_above=-999 required=5 tests=[AWL=0.293, BAYES_00=-2.599, HELO_EQ_DE=0.35, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vxEJozFvubez for <isms@core3.amsl.com>; Fri, 24 Sep 2010 13:27:24 -0700 (PDT)
Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) by core3.amsl.com (Postfix) with ESMTP id 9850E3A69EE for <isms@ietf.org>; Fri, 24 Sep 2010 13:27:24 -0700 (PDT)
Received: from localhost (demetrius3.jacobs-university.de [212.201.44.48]) by hermes.jacobs-university.de (Postfix) with ESMTP id 56B5BC0014; Fri, 24 Sep 2010 22:27:56 +0200 (CEST)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius3.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id C0K5QntU2jGm; Fri, 24 Sep 2010 22:27:56 +0200 (CEST)
Received: from elstar.local (elstar.iuhb02.iu-bremen.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id B72B3C000A; Fri, 24 Sep 2010 22:27:52 +0200 (CEST)
Received: by elstar.local (Postfix, from userid 501) id 48F5014ED005; Fri, 24 Sep 2010 22:27:22 +0200 (CEST)
Date: Fri, 24 Sep 2010 22:27:22 +0200
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: "Yiu L. Lee" <yiu_lee@cable.comcast.com>
Message-ID: <20100924202722.GA39472@elstar.local>
Mail-Followup-To: "Yiu L. Lee" <yiu_lee@cable.comcast.com>, "Pejaver, Rajaram" <Rajaram_Pejaver@cable.comcast.com>, "isms@ietf.org" <isms@ietf.org>
References: <20100924192309.GA39384@elstar.local> <C8C27430.3E6DF%yiu_lee@cable.comcast.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <C8C27430.3E6DF%yiu_lee@cable.comcast.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: "isms@ietf.org" <isms@ietf.org>
Subject: Re: [Isms] status and future of the isms working group
X-BeenThere: isms@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
List-Id: Mailing list for the ISMS working group <isms.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isms>
List-Post: <mailto:isms@ietf.org>
List-Help: <mailto:isms-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Sep 2010 20:27:26 -0000

On Fri, Sep 24, 2010 at 09:28:48PM +0200, Yiu L. Lee wrote:
> Hi Juergen,
> 
> We would like to make it as openly as possible. This is why we submitted the
> draft to IETF. We also like to see any other in the WG is also interested in
> this work.
> 
> From the timeline perspective, we would like the WG would adopt this a WG
> item (if we get enough interested people) this year and WGLC Q1/Q2 next
> year. Do you think this timeline reasonable?

It all boils down to the resources put into this. From a cursory read
of the I-D, I think some work needs to be done to get the document
into a shape that fits the RFC3411 architecture etc. I have not looked
at the details of the Kerberos interface itself and of course it would
help a lot if some Kerberos expert gets involved into this. So we are
again back at the resources. ;-)

/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 adonati@motorola.com  Sun Sep 26 16:33:53 2010
Return-Path: <adonati@motorola.com>
X-Original-To: isms@core3.amsl.com
Delivered-To: isms@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D98543A6BD4 for <isms@core3.amsl.com>; Sun, 26 Sep 2010 16:33:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.185
X-Spam-Level: 
X-Spam-Status: No, score=-4.185 tagged_above=-999 required=5 tests=[BAYES_40=-0.185, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0Kuz2i7XT1jJ for <isms@core3.amsl.com>; Sun, 26 Sep 2010 16:33:52 -0700 (PDT)
Received: from mail55.messagelabs.com (mail55.messagelabs.com [216.82.241.163]) by core3.amsl.com (Postfix) with ESMTP id 74C3D3A6BCB for <isms@ietf.org>; Sun, 26 Sep 2010 16:33:51 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: adonati@motorola.com
X-Msg-Ref: server-13.tower-55.messagelabs.com!1285544055!104785562!1
X-StarScan-Version: 6.2.4; banners=-,-,-
X-Originating-IP: [136.182.1.13]
Received: (qmail 6011 invoked from network); 26 Sep 2010 23:34:15 -0000
Received: from motgate3.mot.com (HELO motgate3.mot.com) (136.182.1.13) by server-13.tower-55.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 26 Sep 2010 23:34:15 -0000
Received: from il27exr04.cig.mot.com ([10.17.196.73]) by motgate3.mot.com (8.14.3/8.14.3) with ESMTP id o8QNYFMS016984 for <isms@ietf.org>; Sun, 26 Sep 2010 16:34:15 -0700 (MST)
Received: from il27vts02.mot.com (il27vts02.cig.mot.com [10.17.196.86]) by il27exr04.cig.mot.com (8.13.1/Vontu) with SMTP id o8QNYESn009601 for <isms@ietf.org>; Sun, 26 Sep 2010 18:34:14 -0500 (CDT)
Received: from de01exm62.ds.mot.com (de01exm62.am.mot.com [10.176.8.107]) by il27exr04.cig.mot.com (8.13.1/8.13.0) with ESMTP id o8QNYEMv009596 for <isms@ietf.org>; Sun, 26 Sep 2010 18:34:14 -0500 (CDT)
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, 26 Sep 2010 19:33:52 -0400
Message-ID: <EC7BA21E901B1D4FADFE19D9FF8943B2057E14A5@de01exm62.ds.mot.com>
In-Reply-To: <20100924202722.GA39472@elstar.local>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Isms] status and future of the isms working group
Thread-Index: ActcJwXG6RcVmKYoSDaEgV6d4MHLlQBq28lA
References: <20100924192309.GA39384@elstar.local><C8C27430.3E6DF%yiu_lee@cable.comcast.com> <20100924202722.GA39472@elstar.local>
From: "Donati Andrew-MGIA0477" <adonati@motorola.com>
To: "Juergen Schoenwaelder" <j.schoenwaelder@jacobs-university.de>, "Yiu L. Lee" <yiu_lee@cable.comcast.com>
X-CFilter-Loop: Reflected
Cc: isms@ietf.org
Subject: Re: [Isms] status and future of the isms working group
X-BeenThere: isms@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mailing list for the ISMS working group <isms.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isms>
List-Post: <mailto:isms@ietf.org>
List-Help: <mailto:isms-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 26 Sep 2010 23:33:54 -0000

I am in support of the WG adopting this item and am willing review the
draft documents.=20
-- Andy Donati

-----Original Message-----
From: isms-bounces@ietf.org [mailto:isms-bounces@ietf.org] On Behalf Of
Juergen Schoenwaelder
Sent: Friday, September 24, 2010 4:27 PM
To: Yiu L. Lee
Cc: isms@ietf.org
Subject: Re: [Isms] status and future of the isms working group

On Fri, Sep 24, 2010 at 09:28:48PM +0200, Yiu L. Lee wrote:
> Hi Juergen,
>=20
> We would like to make it as openly as possible. This is why we=20
> submitted the draft to IETF. We also like to see any other in the WG=20
> is also interested in this work.
>=20
> From the timeline perspective, we would like the WG would adopt this a

> WG item (if we get enough interested people) this year and WGLC Q1/Q2=20
> next year. Do you think this timeline reasonable?

It all boils down to the resources put into this. From a cursory read of
the I-D, I think some work needs to be done to get the document into a
shape that fits the RFC3411 architecture etc. I have not looked at the
details of the Kerberos interface itself and of course it would help a
lot if some Kerberos expert gets involved into this. So we are again
back at the resources. ;-)

/js

--=20
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: +49 421 200 3587         Campus Ring 1, 28759 Bremen, Germany
Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>
_______________________________________________
Isms mailing list
Isms@ietf.org
https://www.ietf.org/mailman/listinfo/isms

From ietfc@btconnect.com  Tue Sep 28 08:24:27 2010
Return-Path: <ietfc@btconnect.com>
X-Original-To: isms@core3.amsl.com
Delivered-To: isms@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D20B43A6D29 for <isms@core3.amsl.com>; Tue, 28 Sep 2010 08:24:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.823
X-Spam-Level: 
X-Spam-Status: No, score=-0.823 tagged_above=-999 required=5 tests=[AWL=-0.824, BAYES_50=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NVuDqLCpYbew for <isms@core3.amsl.com>; Tue, 28 Sep 2010 08:24:26 -0700 (PDT)
Received: from mail.btconnect.com (c2beaomr09.btconnect.com [213.123.26.187]) by core3.amsl.com (Postfix) with ESMTP id B9A6A3A6D4D for <isms@ietf.org>; Tue, 28 Sep 2010 08:24:25 -0700 (PDT)
Received: from host217-44-4-171.range217-44.btcentralplus.com (HELO pc6) ([217.44.4.171]) by c2beaomr09.btconnect.com with SMTP id ACT80289; Tue, 28 Sep 2010 16:25:02 +0100 (BST)
Message-ID: <006c01cb5f18$de6e1040$4001a8c0@gateway.2wire.net>
From: "t.petch" <ietfc@btconnect.com>
To: "Yiu L. Lee" <yiu_lee@cable.comcast.com>, "Juergen Schoenwaelder" <j.schoenwaelder@jacobs-university.de>, "Pejaver,Rajaram" <Rajaram_Pejaver@cable.comcast.com>
References: <C8C27430.3E6DF%yiu_lee@cable.comcast.com>
Date: Tue, 28 Sep 2010 16:24:28 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Mirapoint-IP-Reputation: reputation=Fair-1, source=Queried, refid=tid=0001.0A0B0301.4CA208CE.0086, actions=tag
X-Junkmail-Status: score=10/50, host=c2beaomr09.btconnect.com
X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B0204.4CA208CF.0082,ss=1,fgs=0, ip=0.0.0.0, so=2010-07-22 22:03:31, dmn=2009-09-10 00:05:08, mode=single engine
X-Junkmail-IWF: false
Cc: isms@ietf.org
Subject: Re: [Isms] status and future of the isms working group
X-BeenThere: isms@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mailing list for the ISMS working group <isms.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isms>
List-Post: <mailto:isms@ietf.org>
List-Help: <mailto:isms-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Sep 2010 15:24:27 -0000

----- Original Message -----
From: "Yiu L. Lee" <yiu_lee@cable.comcast.com>
To: "Juergen Schoenwaelder" <j.schoenwaelder@jacobs-university.de>;
"Pejaver,Rajaram" <Rajaram_Pejaver@cable.comcast.com>
Cc: <isms@ietf.org>
Sent: Friday, September 24, 2010 9:28 PM

> Hi Juergen,
>
> We would like to make it as openly as possible. This is why we submitted the
> draft to IETF. We also like to see any other in the WG is also interested in
> this work.
>
> From the timeline perspective, we would like the WG would adopt this a WG
> item (if we get enough interested people) this year and WGLC Q1/Q2 next
> year. Do you think this timeline reasonable?

Looking back at the progress of other I-Ds, this might be a mite optimistic.

Also, having it adopted as a WG item gives the WG change control over it, so
what emerges as an RFC is what the WG (and others) agrees on, which might not be
what you are currently proposing.  Nothing new there, but something to be aware
of.  I am thinking that the WG might want this I-D recast in the style of other
such models, with elements of procedure and such like, an exercise which
has proven time consuming.

And looking in the archives, I find
  draft-pejaver-ismi-kerberos-00
which has just a subtle difference.

Tom Petch





>
> Thanks,
> Yiu
>
>
> On 9/24/10 3:23 PM, "Juergen Schoenwaelder"
> <j.schoenwaelder@jacobs-university.de> wrote:
>
> > On Fri, Sep 24, 2010 at 05:16:03PM +0200, Pejaver, Rajaram wrote:
> >
> > So will this group contribute actively to the work of ISMS or will it
> > remain a closed group at CableLabs? As said earlier, we need to make
> > sure we have sufficient human resources available for any new work.
> > It will also help if you can come up with a suggested timeline for
> > this work.
> >
> > /js
>
> _______________________________________________
> Isms mailing list
> Isms@ietf.org
> https://www.ietf.org/mailman/listinfo/isms


From yiu_lee@cable.comcast.com  Tue Sep 28 08:31:17 2010
Return-Path: <yiu_lee@cable.comcast.com>
X-Original-To: isms@core3.amsl.com
Delivered-To: isms@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 33C4D3A6C34 for <isms@core3.amsl.com>; Tue, 28 Sep 2010 08:31:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.396
X-Spam-Level: 
X-Spam-Status: No, score=-106.396 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, RCVD_IN_DNSWL_HI=-8, RCVD_NUMERIC_HELO=2.067, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F-55PHvCi1ew for <isms@core3.amsl.com>; Tue, 28 Sep 2010 08:31:15 -0700 (PDT)
Received: from pacdcimo01.cable.comcast.com (PacdcIMO01.cable.comcast.com [24.40.8.145]) by core3.amsl.com (Postfix) with ESMTP id 48F913A6CF2 for <isms@ietf.org>; Tue, 28 Sep 2010 08:31:15 -0700 (PDT)
Received: from ([24.40.55.41]) by pacdcimo01.cable.comcast.com with ESMTP with TLS id 5503620.94850749; Tue, 28 Sep 2010 11:31:41 -0400
Received: from PACDCEXCMB04.cable.comcast.com (24.40.15.86) by PACDCEXHUB02.cable.comcast.com (24.40.55.41) with Microsoft SMTP Server id 14.1.218.12; Tue, 28 Sep 2010 11:31:40 -0400
Received: from 32.178.71.156 ([32.178.71.156]) by PACDCEXCMB04.cable.comcast.com ([24.40.15.86]) via Exchange Front-End Server legacywebmail.comcast.com ([24.40.8.154]) with Microsoft Exchange Server HTTP-DAV ; Tue, 28 Sep 2010 15:31:39 +0000
User-Agent: Microsoft-Entourage/12.26.0.100708
Date: Tue, 28 Sep 2010 11:31:23 -0400
From: "Yiu L. Lee" <yiu_lee@cable.comcast.com>
To: t.petch <ietfc@btconnect.com>, Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>, "Pejaver,Rajaram" <Rajaram_Pejaver@cable.comcast.com>
Message-ID: <C8C7828B.3E8AA%yiu_lee@cable.comcast.com>
Thread-Topic: [Isms] status and future of the isms working group
Thread-Index: ActfIjTTLrVWoVhRtkmmyC8yv3L0sA==
In-Reply-To: <006c01cb5f18$de6e1040$4001a8c0@gateway.2wire.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Cc: isms@ietf.org
Subject: Re: [Isms] status and future of the isms working group
X-BeenThere: isms@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mailing list for the ISMS working group <isms.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isms>
List-Post: <mailto:isms@ietf.org>
List-Help: <mailto:isms-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Sep 2010 15:31:17 -0000

Hi Tom,

I agree I may be a little optimistic to the dates. I think the first step is
to get enough interest to make it a WG item before end of 2010. Then, we can
work together to make progress to the WGLC. I am also interested to hear
from you about the general approach of using Kerberos.

Thanks,
Yiu


On 9/28/10 10:24 AM, "t.petch" <ietfc@btconnect.com> wrote:

> ----- Original Message -----
> From: "Yiu L. Lee" <yiu_lee@cable.comcast.com>
> To: "Juergen Schoenwaelder" <j.schoenwaelder@jacobs-university.de>;
> "Pejaver,Rajaram" <Rajaram_Pejaver@cable.comcast.com>
> Cc: <isms@ietf.org>
> Sent: Friday, September 24, 2010 9:28 PM
> 
>> Hi Juergen,
>> 
>> We would like to make it as openly as possible. This is why we submitted the
>> draft to IETF. We also like to see any other in the WG is also interested in
>> this work.
>> 
>> From the timeline perspective, we would like the WG would adopt this a WG
>> item (if we get enough interested people) this year and WGLC Q1/Q2 next
>> year. Do you think this timeline reasonable?
> 
> Looking back at the progress of other I-Ds, this might be a mite optimistic.
> 
> Also, having it adopted as a WG item gives the WG change control over it, so
> what emerges as an RFC is what the WG (and others) agrees on, which might not
> be
> what you are currently proposing.  Nothing new there, but something to be
> aware
> of.  I am thinking that the WG might want this I-D recast in the style of
> other
> such models, with elements of procedure and such like, an exercise which
> has proven time consuming.
> 
> And looking in the archives, I find
>   draft-pejaver-ismi-kerberos-00
> which has just a subtle difference.
> 
> Tom Petch
> 
> 
> 
> 
> 
>> 
>> Thanks,
>> Yiu
>> 
>> 
>> On 9/24/10 3:23 PM, "Juergen Schoenwaelder"
>> <j.schoenwaelder@jacobs-university.de> wrote:
>> 
>>> On Fri, Sep 24, 2010 at 05:16:03PM +0200, Pejaver, Rajaram wrote:
>>> 
>>> So will this group contribute actively to the work of ISMS or will it
>>> remain a closed group at CableLabs? As said earlier, we need to make
>>> sure we have sufficient human resources available for any new work.
>>> It will also help if you can come up with a suggested timeline for
>>> this work.
>>> 
>>> /js
>> 
>> _______________________________________________
>> Isms mailing list
>> Isms@ietf.org
>> https://www.ietf.org/mailman/listinfo/isms
> 


From jhutz@cmu.edu  Tue Sep 28 11:59:35 2010
Return-Path: <jhutz@cmu.edu>
X-Original-To: isms@core3.amsl.com
Delivered-To: isms@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CC5213A6D29 for <isms@core3.amsl.com>; Tue, 28 Sep 2010 11:59:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.544
X-Spam-Level: 
X-Spam-Status: No, score=-106.544 tagged_above=-999 required=5 tests=[AWL=0.055, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fp7anChE94F6 for <isms@core3.amsl.com>; Tue, 28 Sep 2010 11:59:34 -0700 (PDT)
Received: from smtp03.srv.cs.cmu.edu (SMTP03.SRV.CS.CMU.EDU [128.2.217.198]) by core3.amsl.com (Postfix) with ESMTP id A1AC63A6B4E for <isms@ietf.org>; Tue, 28 Sep 2010 11:59:34 -0700 (PDT)
Received: from MINBAR.FAC.CS.CMU.EDU (MINBAR.FAC.CS.CMU.EDU [128.2.216.42]) (authenticated bits=0) by smtp03.srv.cs.cmu.edu (8.13.6/8.13.6) with ESMTP id o8SJ0C1D021176 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 28 Sep 2010 15:00:12 -0400 (EDT)
Date: Tue, 28 Sep 2010 15:00:12 -0400
From: Jeffrey Hutzelman <jhutz@cmu.edu>
To: "Pejaver, Rajaram" <Rajaram_Pejaver@cable.comcast.com>, Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>, isms@ietf.org
Message-ID: <DAB66C50A5285BB34510FA9A@minbar.fac.cs.cmu.edu>
In-Reply-To: <26939_1285341395_o8OFGYVt002791_029A504294520A4F84113D5C45B65A5202CCF061@pacdcexcmb05.cable.comcast.com>
References: <20100917082039.GA47046@elstar.local> <20100923061319.GA25787@elstar.local> <26939_1285341395_o8OFGYVt002791_029A504294520A4F84113D5C45B65A5202CCF061@pacdcexcmb05.cable.comcast.com>
X-Mailer: Mulberry/4.0.8 (Linux/x86)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Scanned-By: mimedefang-cmuscs on 128.2.217.198
Cc: jhutz@cmu.edu
Subject: Re: [Isms] status and future of the isms working group
X-BeenThere: isms@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mailing list for the ISMS working group <isms.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isms>
List-Post: <mailto:isms@ietf.org>
List-Help: <mailto:isms-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Sep 2010 18:59:35 -0000

--On Friday, September 24, 2010 11:16:03 AM -0400 "Pejaver, Rajaram" 
<Rajaram_Pejaver@cable.comcast.com> wrote:

> Juergen,
>
> At Comcast, we are interested in defining the KSM security model.
> An initial draft proposal was submitted to this WG on July 7, 2010.
> A copy is at
> http://www.lee-networks.com/draft-pejaver-isms-kerberos-00.txt

So, why does TSM + SSHTM + RFC4462 + GSS-krb5 not meet your needs?



From j.schoenwaelder@jacobs-university.de  Tue Sep 28 13:37:11 2010
Return-Path: <j.schoenwaelder@jacobs-university.de>
X-Original-To: isms@core3.amsl.com
Delivered-To: isms@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B211C3A6E48 for <isms@core3.amsl.com>; Tue, 28 Sep 2010 13:37:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.961
X-Spam-Level: 
X-Spam-Status: No, score=-101.961 tagged_above=-999 required=5 tests=[AWL=0.288, BAYES_00=-2.599, HELO_EQ_DE=0.35, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UQgovhn7rnvw for <isms@core3.amsl.com>; Tue, 28 Sep 2010 13:37:09 -0700 (PDT)
Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) by core3.amsl.com (Postfix) with ESMTP id 59A7D3A6E4E for <isms@ietf.org>; Tue, 28 Sep 2010 13:35:08 -0700 (PDT)
Received: from localhost (demetrius2.jacobs-university.de [212.201.44.47]) by hermes.jacobs-university.de (Postfix) with ESMTP id 496B1C001A; Tue, 28 Sep 2010 22:35:41 +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 MtG8DLsgupSP; Tue, 28 Sep 2010 22:35:40 +0200 (CEST)
Received: from elstar.local (elstar.iuhb02.iu-bremen.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id 6D168C0015; Tue, 28 Sep 2010 22:35:37 +0200 (CEST)
Received: by elstar.local (Postfix, from userid 501) id 03B3314F7A65; Tue, 28 Sep 2010 22:35:06 +0200 (CEST)
Date: Tue, 28 Sep 2010 22:35:06 +0200
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: "Yiu L. Lee" <yiu_lee@cable.comcast.com>
Message-ID: <20100928203506.GC96620@elstar.local>
Mail-Followup-To: "Yiu L. Lee" <yiu_lee@cable.comcast.com>, "t.petch" <ietfc@btconnect.com>, "Pejaver,Rajaram" <Rajaram_Pejaver@cable.comcast.com>, "isms@ietf.org" <isms@ietf.org>
References: <006c01cb5f18$de6e1040$4001a8c0@gateway.2wire.net> <C8C7828B.3E8AA%yiu_lee@cable.comcast.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <C8C7828B.3E8AA%yiu_lee@cable.comcast.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: "isms@ietf.org" <isms@ietf.org>
Subject: Re: [Isms] status and future of the isms working group
X-BeenThere: isms@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
List-Id: Mailing list for the ISMS working group <isms.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isms>
List-Post: <mailto:isms@ietf.org>
List-Help: <mailto:isms-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Sep 2010 20:37:11 -0000

On Tue, Sep 28, 2010 at 05:31:23PM +0200, Yiu L. Lee wrote:
 
> I agree I may be a little optimistic to the dates. I think the first
> step is to get enough interest to make it a WG item before end of
> 2010. Then, we can work together to make progress to the WGLC.

There are two incredients here: WG interest and author activity, and
sometimes both depend on each other. While WG interest is difficult to
control, author activity is in your hands. So what is supposed to
happen until end of 2010? Will we see a revised version of the
individual I-D before the cutoff where the authors try to express the
new security model in RFC3411 style, similar to other security models
we have?

/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 yiu_lee@cable.comcast.com  Tue Sep 28 13:47:21 2010
Return-Path: <yiu_lee@cable.comcast.com>
X-Original-To: isms@core3.amsl.com
Delivered-To: isms@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 349FC3A6B85 for <isms@core3.amsl.com>; Tue, 28 Sep 2010 13:47:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.401
X-Spam-Level: 
X-Spam-Status: No, score=-102.401 tagged_above=-999 required=5 tests=[AWL=3.995, BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, RCVD_IN_DNSWL_HI=-8, RCVD_NUMERIC_HELO=2.067, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RPjE5Mwse1U8 for <isms@core3.amsl.com>; Tue, 28 Sep 2010 13:47:15 -0700 (PDT)
Received: from pacdcimo01.cable.comcast.com (PacdcIMO01.cable.comcast.com [24.40.8.145]) by core3.amsl.com (Postfix) with ESMTP id 6D0F43A6C5F for <isms@ietf.org>; Tue, 28 Sep 2010 13:47:13 -0700 (PDT)
Received: from ([24.40.55.41]) by pacdcimo01.cable.comcast.com with ESMTP with TLS id 5503620.94928260; Tue, 28 Sep 2010 16:47:37 -0400
Received: from PACDCEXCMB04.cable.comcast.com (24.40.15.86) by PACDCEXHUB02.cable.comcast.com (24.40.55.41) with Microsoft SMTP Server id 14.1.218.12; Tue, 28 Sep 2010 16:47:37 -0400
Received: from 24.40.15.86 ([24.40.15.86]) by PACDCEXCMB04.cable.comcast.com ([24.40.15.86]) with Microsoft Exchange Server HTTP-DAV ; Tue, 28 Sep 2010 20:47:35 +0000
References: <006c01cb5f18$de6e1040$4001a8c0@gateway.2wire.net> <C8C7828B.3E8AA%yiu_lee@cable.comcast.com> <20100928203506.GC96620@elstar.local>
Message-ID: <F362BA0B-ED6D-4150-BEA8-97EACB60D18A@cable.comcast.com>
From: "Lee, Yiu" <Yiu_Lee@Cable.Comcast.com>
To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
In-Reply-To: <20100928203506.GC96620@elstar.local>
Content-Type: text/plain; format=flowed; delsp=yes; charset="us-ascii"
Content-Transfer-Encoding: 7bit
thread-topic: [Isms] status and future of the isms working group
thread-index: ActfTmFXInY+2kWjR/igoMgkbwLbQw==
MIME-Version: 1.0 (iPhone Mail 7E18)
Date: Tue, 28 Sep 2010 16:47:30 -0400
Cc: isms@ietf.org
Subject: Re: [Isms] status and future of the isms working group
X-BeenThere: isms@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mailing list for the ISMS working group <isms.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isms>
List-Post: <mailto:isms@ietf.org>
List-Help: <mailto:isms-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Sep 2010 20:47:22 -0000

Hi Juergen,

Yes, we are working on the revision and try to release it next week.  
Meanwhile, we love to hear more comments so that we can address them  
in the next revision.

Thanks,
Yiu

On Sep 28, 2010, at 4:35 PM, "Juergen Schoenwaelder" <j.schoenwaelder@jacobs-university.de 
 > wrote:

> On Tue, Sep 28, 2010 at 05:31:23PM +0200, Yiu L. Lee wrote:
>
>> I agree I may be a little optimistic to the dates. I think the first
>> step is to get enough interest to make it a WG item before end of
>> 2010. Then, we can work together to make progress to the WGLC.
>
> There are two incredients here: WG interest and author activity, and
> sometimes both depend on each other. While WG interest is difficult to
> control, author activity is in your hands. So what is supposed to
> happen until end of 2010? Will we see a revised version of the
> individual I-D before the cutoff where the authors try to express the
> new security model in RFC3411 style, similar to other security models
> we have?
>
> /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 wjhns1@hardakers.net  Tue Sep 28 20:00:32 2010
Return-Path: <wjhns1@hardakers.net>
X-Original-To: isms@core3.amsl.com
Delivered-To: isms@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5BAB93A6C0D for <isms@core3.amsl.com>; Tue, 28 Sep 2010 20:00:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.069
X-Spam-Level: 
X-Spam-Status: No, score=-3.069 tagged_above=-999 required=5 tests=[AWL=0.530,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Jkqtf+3UweWC for <isms@core3.amsl.com>; Tue, 28 Sep 2010 20:00:31 -0700 (PDT)
Received: from mail.hardakers.net (mail.hardakers.net [168.150.236.43]) by core3.amsl.com (Postfix) with ESMTP id 3CD5D3A6AA7 for <isms@ietf.org>; Tue, 28 Sep 2010 20:00:29 -0700 (PDT)
Received: from localhost (wjh.hardakers.net [10.0.0.2]) by mail.hardakers.net (Postfix) with ESMTPSA id C8A339809E; Tue, 28 Sep 2010 20:00:50 -0700 (PDT)
From: Wes Hardaker <wjhns1@hardakers.net>
To: Jeffrey Hutzelman <jhutz@cmu.edu>
Organization: Sparta
References: <20100917082039.GA47046@elstar.local> <20100923061319.GA25787@elstar.local> <26939_1285341395_o8OFGYVt002791_029A504294520A4F84113D5C45B65A5202CCF061@pacdcexcmb05.cable.comcast.com> <DAB66C50A5285BB34510FA9A@minbar.fac.cs.cmu.edu>
Date: Tue, 28 Sep 2010 20:00:50 -0700
In-Reply-To: <DAB66C50A5285BB34510FA9A@minbar.fac.cs.cmu.edu> (Jeffrey Hutzelman's message of "Tue, 28 Sep 2010 15:00:12 -0400")
Message-ID: <sdpqvxxnh9.fsf@wjh.hardakers.net>
User-Agent: Gnus/5.110011 (No Gnus v0.11) Emacs/23.2 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
Cc: isms@ietf.org
Subject: Re: [Isms] status and future of the isms working group
X-BeenThere: isms@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mailing list for the ISMS working group <isms.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isms>
List-Post: <mailto:isms@ietf.org>
List-Help: <mailto:isms-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Sep 2010 03:00:32 -0000

>>>>> On Tue, 28 Sep 2010 15:00:12 -0400, Jeffrey Hutzelman <jhutz@cmu.edu> said:

JH> So, why does TSM + SSHTM + RFC4462 + GSS-krb5 not meet your needs?

He mentioned a single round trip stateless UDP message at one point....
SSHTM won't fit that model.
-- 
Wes Hardaker
Cobham Analytic Solutions

From ietfc@btconnect.com  Wed Sep 29 01:47:51 2010
Return-Path: <ietfc@btconnect.com>
X-Original-To: isms@core3.amsl.com
Delivered-To: isms@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9C67B3A6C7F for <isms@core3.amsl.com>; Wed, 29 Sep 2010 01:47:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.032
X-Spam-Level: 
X-Spam-Status: No, score=-2.032 tagged_above=-999 required=5 tests=[AWL=0.567,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6PxJ3yW1v2i5 for <isms@core3.amsl.com>; Wed, 29 Sep 2010 01:47:50 -0700 (PDT)
Received: from mail.btconnect.com (c2bthomr14.btconnect.com [213.123.20.132]) by core3.amsl.com (Postfix) with ESMTP id 0C87D3A6B23 for <isms@ietf.org>; Wed, 29 Sep 2010 01:47:49 -0700 (PDT)
Received: from host217-44-4-171.range217-44.btcentralplus.com (HELO pc6) ([217.44.4.171]) by c2bthomr14.btconnect.com with SMTP id ABI26543; Wed, 29 Sep 2010 09:48:28 +0100 (BST)
Message-ID: <015901cb5faa$a1f5a320$4001a8c0@gateway.2wire.net>
From: "t.petch" <ietfc@btconnect.com>
To: "Lee, Yiu" <Yiu_Lee@Cable.Comcast.com>, "Juergen Schoenwaelder" <j.schoenwaelder@jacobs-university.de>
References: <006c01cb5f18$de6e1040$4001a8c0@gateway.2wire.net> <C8C7828B.3E8AA%yiu_lee@cable.comcast.com> <20100928203506.GC96620@elstar.local> <F362BA0B-ED6D-4150-BEA8-97EACB60D18A@cable.comcast.com>
Date: Wed, 29 Sep 2010 09:44:51 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Mirapoint-IP-Reputation: reputation=Fair-1, source=Queried, refid=tid=0001.0A0B0302.4CA2FD5C.0027, actions=tag
X-Junkmail-Status: score=10/50, host=c2bthomr14.btconnect.com
X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B0209.4CA2FD5D.016F,ss=1,fgs=0, ip=0.0.0.0, so=2010-07-22 22:03:31, dmn=2009-09-10 00:05:08, mode=single engine
X-Junkmail-IWF: false
Cc: isms@ietf.org
Subject: Re: [Isms] status and future of the isms working group
X-BeenThere: isms@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mailing list for the ISMS working group <isms.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isms>
List-Post: <mailto:isms@ietf.org>
List-Help: <mailto:isms-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Sep 2010 08:47:51 -0000

Yiu

I think that
draft-hornstein-snmpv3-ksm
should disappear except in the Acknowledgements; an out-of-date, expired I-D is
not something I want to look at, so any reference to it must be a distraction.

Rather, your model should be RFC5591 which is the most recent Security Model and
yes, you must include processing of tmStateReference etc since that is now part
of 'An Architecture'.

Likewise, Transport is now part of 'An Architecture' and you are going back to
the UDP Transport Model, except we have never defined that beyond showing that
if you mix and match Models, it doesn't work, you can send a message from
Command Generator to Command Responder but will never get a response, a trap you
might also fall into:-( so perhaps you will need to define the UTM as well.

So, 1Q/2Q yes, but perhaps 2010.

Tom Petch

----- Original Message -----
From: "Lee, Yiu" <Yiu_Lee@Cable.Comcast.com>
To: "Juergen Schoenwaelder" <j.schoenwaelder@jacobs-university.de>
Cc: "t.petch" <ietfc@btconnect.com>; "Pejaver,Rajaram"
<Rajaram_Pejaver@cable.comcast.com>; <isms@ietf.org>
Sent: Tuesday, September 28, 2010 10:47 PM
Subject: Re: [Isms] status and future of the isms working group


> Hi Juergen,
>
> Yes, we are working on the revision and try to release it next week.
> Meanwhile, we love to hear more comments so that we can address them
> in the next revision.
>
> Thanks,
> Yiu
>
> On Sep 28, 2010, at 4:35 PM, "Juergen Schoenwaelder"
<j.schoenwaelder@jacobs-university.de
>  > wrote:
>
> > On Tue, Sep 28, 2010 at 05:31:23PM +0200, Yiu L. Lee wrote:
> >
> >> I agree I may be a little optimistic to the dates. I think the first
> >> step is to get enough interest to make it a WG item before end of
> >> 2010. Then, we can work together to make progress to the WGLC.
> >
> > There are two incredients here: WG interest and author activity, and
> > sometimes both depend on each other. While WG interest is difficult to
> > control, author activity is in your hands. So what is supposed to
> > happen until end of 2010? Will we see a revised version of the
> > individual I-D before the cutoff where the authors try to express the
> > new security model in RFC3411 style, similar to other security models
> > we have?
> >
> > /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 yiu_lee@cable.comcast.com  Wed Sep 29 06:29:24 2010
Return-Path: <yiu_lee@cable.comcast.com>
X-Original-To: isms@core3.amsl.com
Delivered-To: isms@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 869583A6C63 for <isms@core3.amsl.com>; Wed, 29 Sep 2010 06:29:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.412
X-Spam-Level: 
X-Spam-Status: No, score=-103.412 tagged_above=-999 required=5 tests=[AWL=2.984, BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, RCVD_IN_DNSWL_HI=-8, RCVD_NUMERIC_HELO=2.067, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id B6PK2gedinP2 for <isms@core3.amsl.com>; Wed, 29 Sep 2010 06:29:23 -0700 (PDT)
Received: from pacdcimo01.cable.comcast.com (PacdcIMO01.cable.comcast.com [24.40.8.145]) by core3.amsl.com (Postfix) with ESMTP id 4CACA3A6AED for <isms@ietf.org>; Wed, 29 Sep 2010 06:29:22 -0700 (PDT)
Received: from ([24.40.55.42]) by pacdcimo01.cable.comcast.com with ESMTP with TLS id 5503620.94992266; Wed, 29 Sep 2010 09:13:27 -0400
Received: from PACDCEXCMB04.cable.comcast.com (24.40.15.86) by PACDCEXHUB01.cable.comcast.com (24.40.55.42) with Microsoft SMTP Server id 14.1.218.12; Wed, 29 Sep 2010 09:13:27 -0400
Received: from 69.241.25.0 ([69.241.25.0]) by PACDCEXCMB04.cable.comcast.com ([24.40.15.86]) via Exchange Front-End Server legacywebmail.comcast.com ([24.40.8.152]) with Microsoft Exchange Server HTTP-DAV ; Wed, 29 Sep 2010 13:13:24 +0000
User-Agent: Microsoft-Entourage/12.26.0.100708
Date: Wed, 29 Sep 2010 09:13:17 -0400
From: "Yiu L. Lee" <yiu_lee@cable.comcast.com>
To: t.petch <ietfc@btconnect.com>, Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
Message-ID: <C8C8B3AD.3E92D%yiu_lee@cable.comcast.com>
Thread-Topic: [Isms] status and future of the isms working group
Thread-Index: Actf2BRmvCJeBrxgzkmqdOkCKyE+Jg==
In-Reply-To: <015901cb5faa$a1f5a320$4001a8c0@gateway.2wire.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Cc: isms@ietf.org
Subject: Re: [Isms] status and future of the isms working group
X-BeenThere: isms@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mailing list for the ISMS working group <isms.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isms>
List-Post: <mailto:isms@ietf.org>
List-Help: <mailto:isms-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Sep 2010 13:29:24 -0000

Hi Tom,

Good comments. We will consider them and capture the necessary changes in
the next revision.

My mind set is still stuck in 2010 and I am not ready to let it go! Thanks
for finding the year wrong. I mean 2011 Q1/Q2. But it may be overly
optimistic. Raj and I will continue to work hard to make sure to address all
the questions and issues in the mailing list. Please don't stop giving us
feedback!

Thanks,
Yiu


On 9/29/10 3:44 AM, "t.petch" <ietfc@btconnect.com> wrote:

> Yiu
> 
> I think that
> draft-hornstein-snmpv3-ksm
> should disappear except in the Acknowledgements; an out-of-date, expired I-D
> is
> not something I want to look at, so any reference to it must be a distraction.
> 
> Rather, your model should be RFC5591 which is the most recent Security Model
> and
> yes, you must include processing of tmStateReference etc since that is now
> part
> of 'An Architecture'.
> 
> Likewise, Transport is now part of 'An Architecture' and you are going back to
> the UDP Transport Model, except we have never defined that beyond showing that
> if you mix and match Models, it doesn't work, you can send a message from
> Command Generator to Command Responder but will never get a response, a trap
> you
> might also fall into:-( so perhaps you will need to define the UTM as well.
> 
> So, 1Q/2Q yes, but perhaps 2010.
> 
> Tom Petch
> 
> ----- Original Message -----
> From: "Lee, Yiu" <Yiu_Lee@Cable.Comcast.com>
> To: "Juergen Schoenwaelder" <j.schoenwaelder@jacobs-university.de>
> Cc: "t.petch" <ietfc@btconnect.com>; "Pejaver,Rajaram"
> <Rajaram_Pejaver@cable.comcast.com>; <isms@ietf.org>
> Sent: Tuesday, September 28, 2010 10:47 PM
> Subject: Re: [Isms] status and future of the isms working group
> 
> 
>> Hi Juergen,
>> 
>> Yes, we are working on the revision and try to release it next week.
>> Meanwhile, we love to hear more comments so that we can address them
>> in the next revision.
>> 
>> Thanks,
>> Yiu
>> 
>> On Sep 28, 2010, at 4:35 PM, "Juergen Schoenwaelder"
> <j.schoenwaelder@jacobs-university.de
>>> wrote:
>> 
>>> On Tue, Sep 28, 2010 at 05:31:23PM +0200, Yiu L. Lee wrote:
>>> 
>>>> I agree I may be a little optimistic to the dates. I think the first
>>>> step is to get enough interest to make it a WG item before end of
>>>> 2010. Then, we can work together to make progress to the WGLC.
>>> 
>>> There are two incredients here: WG interest and author activity, and
>>> sometimes both depend on each other. While WG interest is difficult to
>>> control, author activity is in your hands. So what is supposed to
>>> happen until end of 2010? Will we see a revised version of the
>>> individual I-D before the cutoff where the authors try to express the
>>> new security model in RFC3411 style, similar to other security models
>>> we have?
>>> 
>>> /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 wjhns1@hardakers.net  Wed Sep 29 07:20:50 2010
Return-Path: <wjhns1@hardakers.net>
X-Original-To: isms@core3.amsl.com
Delivered-To: isms@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1FD7A3A6E04 for <isms@core3.amsl.com>; Wed, 29 Sep 2010 07:20:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.087
X-Spam-Level: 
X-Spam-Status: No, score=-3.087 tagged_above=-999 required=5 tests=[AWL=0.512,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QD1sb2PCGCPy for <isms@core3.amsl.com>; Wed, 29 Sep 2010 07:20:49 -0700 (PDT)
Received: from mail.hardakers.net (mail.hardakers.net [168.150.236.43]) by core3.amsl.com (Postfix) with ESMTP id 2B5273A6B5E for <isms@ietf.org>; Wed, 29 Sep 2010 07:20:49 -0700 (PDT)
Received: from localhost (wjh.hardakers.net [10.0.0.2]) by mail.hardakers.net (Postfix) with ESMTPSA id F2C0498104; Wed, 29 Sep 2010 07:21:11 -0700 (PDT)
From: Wes Hardaker <wjhns1@hardakers.net>
To: "t.petch" <ietfc@btconnect.com>
Organization: Sparta
References: <006c01cb5f18$de6e1040$4001a8c0@gateway.2wire.net> <C8C7828B.3E8AA%yiu_lee@cable.comcast.com> <20100928203506.GC96620@elstar.local> <F362BA0B-ED6D-4150-BEA8-97EACB60D18A@cable.comcast.com> <015901cb5faa$a1f5a320$4001a8c0@gateway.2wire.net>
Date: Wed, 29 Sep 2010 07:21:11 -0700
In-Reply-To: <015901cb5faa$a1f5a320$4001a8c0@gateway.2wire.net> (t. petch's message of "Wed, 29 Sep 2010 09:44:51 +0200")
Message-ID: <sdmxr0aaw8.fsf@wjh.hardakers.net>
User-Agent: Gnus/5.110011 (No Gnus v0.11) Emacs/23.2 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
Cc: isms@ietf.org, "Lee, Yiu" <Yiu_Lee@Cable.Comcast.com>
Subject: Re: [Isms] status and future of the isms working group
X-BeenThere: isms@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mailing list for the ISMS working group <isms.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isms>
List-Post: <mailto:isms@ietf.org>
List-Help: <mailto:isms-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Sep 2010 14:20:50 -0000

>>>>> On Wed, 29 Sep 2010 09:44:51 +0200, "t.petch" <ietfc@btconnect.com> said:

tp> Rather, your model should be RFC5591 which is the most recent
tp> Security Model and yes, you must include processing of
tp> tmStateReference etc since that is now part of 'An Architecture'.

He's right you should mention it, but it could be as trivial as "we
don't care about it".  Though caring about it will let you properly send
KSM protected SNMPv3 over DTLS, for example, and if you don't at least
do minimal processing [see 5591] then KSM won't work over DTLS, TLS or SSH.

tp> Likewise, Transport is now part of 'An Architecture' and you are
tp> going back to the UDP Transport Model, except we have never defined
tp> that beyond showing that if you mix and match Models, it doesn't
tp> work, you can send a message from Command Generator to Command
tp> Responder but will never get a response, a trap you might also fall
tp> into:-( so perhaps you will need to define the UTM as well.

That's unfair.  The security architecture is modular and the original
intent of SNMP was to complete separate out the message format and
security from the transport over which it is sent.  Yes, the UDP
transport model isn't spelled out, but neither is SNMP over appletalk,
SNMP over unix domain socket, or any of the transports that SNMP
actually works over.  Note the "works over" part of that sentence.  They
are defined and work today, just not inline with 5590 wording.

Making a new security model which is transport agnostic, which is how
proper layering should work, should not require redefining all the
potential other layers over which the new SNMPv3 with the new security
model (KSM) "might" go over.

If there was a problem unless it was defined, sure.  But there isn't one.
-- 
Wes Hardaker
Cobham Analytic Solutions

From j.schoenwaelder@jacobs-university.de  Wed Sep 29 07:28:58 2010
Return-Path: <j.schoenwaelder@jacobs-university.de>
X-Original-To: isms@core3.amsl.com
Delivered-To: isms@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0E6AE3A6C36 for <isms@core3.amsl.com>; Wed, 29 Sep 2010 07:28:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.963
X-Spam-Level: 
X-Spam-Status: No, score=-101.963 tagged_above=-999 required=5 tests=[AWL=0.286, BAYES_00=-2.599, HELO_EQ_DE=0.35, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6K5Cayb1ttrn for <isms@core3.amsl.com>; Wed, 29 Sep 2010 07:28:56 -0700 (PDT)
Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) by core3.amsl.com (Postfix) with ESMTP id 925EC3A6B36 for <isms@ietf.org>; Wed, 29 Sep 2010 07:28:56 -0700 (PDT)
Received: from localhost (demetrius3.jacobs-university.de [212.201.44.48]) by hermes.jacobs-university.de (Postfix) with ESMTP id 0FE9CC0051; Wed, 29 Sep 2010 16:29:39 +0200 (CEST)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius3.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id Kdj3mKvMWnFu; Wed, 29 Sep 2010 16:29:38 +0200 (CEST)
Received: from elstar.local (elstar.iuhb02.iu-bremen.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id 0DF8CC0043; Wed, 29 Sep 2010 16:29:35 +0200 (CEST)
Received: by elstar.local (Postfix, from userid 501) id 5319D14FB0C7; Wed, 29 Sep 2010 16:29:05 +0200 (CEST)
Date: Wed, 29 Sep 2010 16:29:05 +0200
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: Wes Hardaker <wjhns1@hardakers.net>
Message-ID: <20100929142905.GC98982@elstar.local>
Mail-Followup-To: Wes Hardaker <wjhns1@hardakers.net>, "t.petch" <ietfc@btconnect.com>, "Lee, Yiu" <Yiu_Lee@Cable.Comcast.com>, "isms@ietf.org" <isms@ietf.org>
References: <006c01cb5f18$de6e1040$4001a8c0@gateway.2wire.net> <C8C7828B.3E8AA%yiu_lee@cable.comcast.com> <20100928203506.GC96620@elstar.local> <F362BA0B-ED6D-4150-BEA8-97EACB60D18A@cable.comcast.com> <015901cb5faa$a1f5a320$4001a8c0@gateway.2wire.net> <sdmxr0aaw8.fsf@wjh.hardakers.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <sdmxr0aaw8.fsf@wjh.hardakers.net>
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: "isms@ietf.org" <isms@ietf.org>, "Lee, Yiu" <Yiu_Lee@Cable.Comcast.com>
Subject: Re: [Isms] status and future of the isms working group
X-BeenThere: isms@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
List-Id: Mailing list for the ISMS working group <isms.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isms>
List-Post: <mailto:isms@ietf.org>
List-Help: <mailto:isms-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Sep 2010 14:28:58 -0000

On Wed, Sep 29, 2010 at 04:21:11PM +0200, Wes Hardaker wrote:
> >>>>> On Wed, 29 Sep 2010 09:44:51 +0200, "t.petch" <ietfc@btconnect.com> said:
> 
> tp> Rather, your model should be RFC5591 which is the most recent
> tp> Security Model and yes, you must include processing of
> tp> tmStateReference etc since that is now part of 'An Architecture'.
> 
> He's right you should mention it, but it could be as trivial as "we
> don't care about it".  Though caring about it will let you properly send
> KSM protected SNMPv3 over DTLS, for example, and if you don't at least
> do minimal processing [see 5591] then KSM won't work over DTLS, TLS or SSH.

As far as I understand, KSM would do security processing in the
traditional way and not outsource the security processing to the
transport model. As such, I do not see any benefit of having KSM over
DTLS, TLS, or SSH. As matter of fact, USM over DTLS, TLS, or SSH does
not work either - except in the sense that all the DTLS, TLS, or SSH
stuff is simply ignored by the security model. And this is frankly
what I would expect to happen. So I guess the answer is really "KSM
does not care about any tmStateReference", like USM does.

> Making a new security model which is transport agnostic, which is how
> proper layering should work, should not require redefining all the
> potential other layers over which the new SNMPv3 with the new security
> model (KSM) "might" go over.
> 
> If there was a problem unless it was defined, sure.  But there isn't one.

I agree.

/js (speaking as technical contributor)

-- 
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 rajaram_pejaver@cable.comcast.com  Wed Sep 29 07:41:10 2010
Return-Path: <rajaram_pejaver@cable.comcast.com>
X-Original-To: isms@core3.amsl.com
Delivered-To: isms@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 502DF3A6B5E for <isms@core3.amsl.com>; Wed, 29 Sep 2010 07:41:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.821
X-Spam-Level: 
X-Spam-Status: No, score=-107.821 tagged_above=-999 required=5 tests=[AWL=0.642, BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XG-6N+HRtzXn for <isms@core3.amsl.com>; Wed, 29 Sep 2010 07:41:09 -0700 (PDT)
Received: from pacdcimo01.cable.comcast.com (PacdcIMO01.cable.comcast.com [24.40.8.145]) by core3.amsl.com (Postfix) with ESMTP id 3EDE13A6CF1 for <isms@ietf.org>; Wed, 29 Sep 2010 07:41:08 -0700 (PDT)
Received: from ([24.40.55.41]) by pacdcimo01.cable.comcast.com with ESMTP with TLS id 5503620.95011471; Wed, 29 Sep 2010 10:40:44 -0400
Received: from pacdcexcmb05.cable.comcast.com (24.40.15.116) by PACDCEXHUB02.cable.comcast.com (24.40.55.41) with Microsoft SMTP Server id 14.1.218.12; Wed, 29 Sep 2010 10:40:45 -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, 29 Sep 2010 10:39:44 -0400
Message-ID: <029A504294520A4F84113D5C45B65A5202D7FB17@pacdcexcmb05.cable.comcast.com>
In-Reply-To: <DAB66C50A5285BB34510FA9A@minbar.fac.cs.cmu.edu>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Isms] status and future of the isms working group
Thread-Index: ActfP2NRpibUzXGKQv+d8THiZ7vawAApAyEA
References: <20100917082039.GA47046@elstar.local> <20100923061319.GA25787@elstar.local> <26939_1285341395_o8OFGYVt002791_029A504294520A4F84113D5C45B65A5202CCF061@pacdcexcmb05.cable.comcast.com> <DAB66C50A5285BB34510FA9A@minbar.fac.cs.cmu.edu>
From: "Pejaver, Rajaram" <Rajaram_Pejaver@cable.comcast.com>
To: Jeffrey Hutzelman <jhutz@cmu.edu>, Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>, <isms@ietf.org>
Subject: Re: [Isms] status and future of the isms working group
X-BeenThere: isms@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mailing list for the ISMS working group <isms.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isms>
List-Post: <mailto:isms@ietf.org>
List-Help: <mailto:isms-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Sep 2010 14:41:10 -0000

> > At Comcast, we are interested in defining the KSM security model.
> > An initial draft proposal was submitted to this WG on July 7, 2010.
> > A copy is at
> > http://www.lee-networks.com/draft-pejaver-isms-kerberos-00.txt
>=20
> So, why does TSM + SSHTM + RFC4462 + GSS-krb5 not meet your needs?

Jeff,  We seek a lightweight transaction. =20
TCP+TSM+... is a lot of overhead for a quick status check on a managed
device.

Regret the slow response; I'm in an Internetless, airless lab this week.

--raj

From ietfc@btconnect.com  Wed Sep 29 10:48:53 2010
Return-Path: <ietfc@btconnect.com>
X-Original-To: isms@core3.amsl.com
Delivered-To: isms@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4AC0C3A6D71 for <isms@core3.amsl.com>; Wed, 29 Sep 2010 10:48:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.489
X-Spam-Level: 
X-Spam-Status: No, score=-1.489 tagged_above=-999 required=5 tests=[AWL=-0.182, BAYES_00=-2.599, MISSING_HEADERS=1.292]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xrVUX-2X4iLD for <isms@core3.amsl.com>; Wed, 29 Sep 2010 10:48:52 -0700 (PDT)
Received: from mail.btconnect.com (c2bthomr13.btconnect.com [213.123.20.131]) by core3.amsl.com (Postfix) with ESMTP id D9B553A6F06 for <isms@ietf.org>; Wed, 29 Sep 2010 10:48:14 -0700 (PDT)
Received: from host217-44-4-171.range217-44.btcentralplus.com (HELO pc6) ([217.44.4.171]) by c2bthomr13.btconnect.com with SMTP id ABP91639; Wed, 29 Sep 2010 18:47:44 +0100 (BST)
Message-ID: <007d01cb5ff5$f70de3e0$4001a8c0@gateway.2wire.net>
From: "t.petch" <ietfc@btconnect.com>
References: <006c01cb5f18$de6e1040$4001a8c0@gateway.2wire.net><C8C7828B.3E8AA%yiu_lee@cable.comcast.com><20100928203506.GC96620@elstar.local><F362BA0B-ED6D-4150-BEA8-97EACB60D18A@cable.comcast.com><015901cb5faa$a1f5a320$4001a8c0@gateway.2wire.net> <sdmxr0aaw8.fsf@wjh.hardakers.net>
Date: Wed, 29 Sep 2010 18:47:07 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Mirapoint-IP-Reputation: reputation=Fair-1, source=Queried, refid=tid=0001.0A0B0301.4CA37BBF.0220, actions=tag
X-Junkmail-Status: score=10/50, host=c2bthomr13.btconnect.com
X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B0206.4CA37BC1.0111,ss=1,fgs=0, ip=0.0.0.0, so=2010-07-22 22:03:31, dmn=2009-09-10 00:05:08, mode=single engine
X-Junkmail-IWF: false
Cc: isms <isms@ietf.org>, "Lee, Yiu" <Yiu_Lee@Cable.Comcast.com>
Subject: Re: [Isms] status and future of the isms working group
X-BeenThere: isms@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mailing list for the ISMS working group <isms.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isms>
List-Post: <mailto:isms@ietf.org>
List-Help: <mailto:isms-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Sep 2010 17:48:53 -0000

Wes, I am getting bounces from your e-mail address, so we will have to use the
list:-) - see below
----- Original Message -----
From: "Wes Hardaker" <wjhns1@hardakers.net>
To: "t.petch" <ietfc@btconnect.com>
Cc: "Lee, Yiu" <Yiu_Lee@Cable.Comcast.com>; "Juergen Schoenwaelder"
<j.schoenwaelder@jacobs-university.de>; <isms@ietf.org>
Sent: Wednesday, September 29, 2010 4:21 PM

> >>>>> On Wed, 29 Sep 2010 09:44:51 +0200, "t.petch" <ietfc@btconnect.com>
said:
>
> tp> Rather, your model should be RFC5591 which is the most recent
> tp> Security Model and yes, you must include processing of
> tp> tmStateReference etc since that is now part of 'An Architecture'.
>
> He's right you should mention it, but it could be as trivial as "we
> don't care about it".  Though caring about it will let you properly send
> KSM protected SNMPv3 over DTLS, for example, and if you don't at least
> do minimal processing [see 5591] then KSM won't work over DTLS, TLS or SSH.
>
> tp> Likewise, Transport is now part of 'An Architecture' and you are
> tp> going back to the UDP Transport Model, except we have never defined
> tp> that beyond showing that if you mix and match Models, it doesn't
> tp> work, you can send a message from Command Generator to Command
> tp> Responder but will never get a response, a trap you might also fall
> tp> into:-( so perhaps you will need to define the UTM as well.
>
> That's unfair.  The security architecture is modular and the original
> intent of SNMP was to complete separate out the message format and
> security from the transport over which it is sent.  Yes, the UDP
> transport model isn't spelled out, but neither is SNMP over appletalk,
> SNMP over unix domain socket, or any of the transports that SNMP
> actually works over.  Note the "works over" part of that sentence.  They
> are defined and work today, just not inline with 5590 wording.
>
> Making a new security model which is transport agnostic, which is how
> proper layering should work, should not require redefining all the
> potential other layers over which the new SNMPv3 with the new security
> model (KSM) "might" go over.

Yeah, and you know well that we don't have proper layering - tmStateReference
being a good example - which is why we sometimes do have to specify the
interactions since, as you and I demonstrated, to the surprise of some, USM will
not work over the existing secure Transport Models.

I am saying that at the least, a KSM I-D has to parallel RFC5591 (not USM),
covering all the topics that that covers.  It will probably specify that all
the additional parameters introduced by RFC5590 are ignored, but if it says
anything else, then I think we will need a UDP Transport Model.

And then there are the interactions with Kerberos; shades of VACM and RADIUS
perhaps, in that the Command Responder is setting up a
connection(/session/transport) to a third party, which needs specifying?

It's quite a lot of work.

Tom Petch
>
> If there was a problem unless it was defined, sure.  But there isn't one.
> --
> Wes Hardaker
> Cobham Analytic Solutions


From randy_presuhn@mindspring.com  Wed Sep 29 11:43:28 2010
Return-Path: <randy_presuhn@mindspring.com>
X-Original-To: isms@core3.amsl.com
Delivered-To: isms@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 002583A6CFB for <isms@core3.amsl.com>; Wed, 29 Sep 2010 11:43:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.33
X-Spam-Level: 
X-Spam-Status: No, score=-101.33 tagged_above=-999 required=5 tests=[AWL=1.269, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R1qzjTU4D1rl for <isms@core3.amsl.com>; Wed, 29 Sep 2010 11:43:27 -0700 (PDT)
Received: from elasmtp-spurfowl.atl.sa.earthlink.net (elasmtp-spurfowl.atl.sa.earthlink.net [209.86.89.66]) by core3.amsl.com (Postfix) with ESMTP id CDD513A6D33 for <isms@ietf.org>; Wed, 29 Sep 2010 11:43:26 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=pPIYNQ3kx+mRCE14WO5fv2rYOI3d92D2+ek75Ejqy25W2n0dSeskkq85Qm3fjfSX; 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.35.225.245] (helo=oemcomputer) by elasmtp-spurfowl.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <randy_presuhn@mindspring.com>) id 1P11dS-0008Ci-Il for isms@ietf.org; Wed, 29 Sep 2010 14:44:10 -0400
Message-ID: <000e01cb6006$76e54bc0$6801a8c0@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: <isms@ietf.org>
References: <006c01cb5f18$de6e1040$4001a8c0@gateway.2wire.net><C8C7828B.3E8AA%yiu_lee@cable.comcast.com><20100928203506.GC96620@elstar.local><F362BA0B-ED6D-4150-BEA8-97EACB60D18A@cable.comcast.com><015901cb5faa$a1f5a320$4001a8c0@gateway.2wire.net><sdmxr0aaw8.fsf@wjh.hardakers.net> <007d01cb5ff5$f70de3e0$4001a8c0@gateway.2wire.net>
Date: Wed, 29 Sep 2010 11:45:17 -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: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d88829a3b650ee59d5fe850e470630d8eaf2cf8e564c9ee132ee350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 99.35.225.245
Subject: Re: [Isms] status and future of the isms working group
X-BeenThere: isms@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mailing list for the ISMS working group <isms.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isms>
List-Post: <mailto:isms@ietf.org>
List-Help: <mailto:isms-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Sep 2010 18:43:28 -0000

Hi -

> From: "t.petch" <ietfc@btconnect.com>
> Cc: "isms" <isms@ietf.org>; "Lee, Yiu" <Yiu_Lee@Cable.Comcast.com>
> Sent: Wednesday, September 29, 2010 9:47 AM
> Subject: Re: [Isms] status and future of the isms working group
...
> It's quite a lot of work.

Perhaps, but let's not make it more work than is really necessary.
Imposing constraints that don't actually affect the bits on the wire
or make the specification clearer is not helpful, in my opinion.
In particular, I think alignment with a particular architectural model
should *not* be an absolute requirement.   Elements of the architecture
should be mentioned IFF they make it easier to understand how
something is supposed to work.

In my opinion, the important thing is to nail down any bits on the
wire, along with the operational and management characteristics.
If the resulting spec has a gestalt that makes for a clear description
in the terms of an existing architecture, great.  If it doesn't, I see no
benefit to subjecting it to procrustean edits to align it.

The fact of life is that the modularity of the architecture does NOT
correspond to implementation modularity.  Perhaps a concrete
example would be helpful.  Consider what a master agent needs
to do to process a get-next or get-bulk request in the presence of
access control.  The architecture would suggest an iterative solution,
applying isAccesAllowed() to each potential intermediate result
returned from a subagent.  From the point of describing the externally-
observable SNMP behaviour, this is fine.  But from the subagent protocol
perspective, or from an implementation perspective, this is crazy.  With
fine-grained access control  and/or tables distributed across multiple
subagents, this can be spectacularly inefficient.  Subagent query optimization
is possible, but requires operating directly on both the VACM and subagent
registration tables.  This is clearly not supported by the ASIs. but also not
something the standard should even talk about, since it is highly vendor-specific.
We shouldn't try to use the 3411 architecture for anything more than what it
was designed to do: to modularize the description of how USM, VACM,
and a more-or-less generic SNMP protocol engine work together to support
SNMP applications.

Randy


From wjhns1@hardakers.net  Wed Sep 29 11:46:52 2010
Return-Path: <wjhns1@hardakers.net>
X-Original-To: isms@core3.amsl.com
Delivered-To: isms@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AC6863A6D1F for <isms@core3.amsl.com>; Wed, 29 Sep 2010 11:46:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.104
X-Spam-Level: 
X-Spam-Status: No, score=-3.104 tagged_above=-999 required=5 tests=[AWL=0.495,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4GLnas60O4Yi for <isms@core3.amsl.com>; Wed, 29 Sep 2010 11:46:51 -0700 (PDT)
Received: from mail.hardakers.net (mail.hardakers.net [168.150.236.43]) by core3.amsl.com (Postfix) with ESMTP id B6AA83A6901 for <isms@ietf.org>; Wed, 29 Sep 2010 11:46:51 -0700 (PDT)
Received: from localhost (wjh.hardakers.net [10.0.0.2]) by mail.hardakers.net (Postfix) with ESMTPSA id 13CEB980F5; Wed, 29 Sep 2010 11:47:14 -0700 (PDT)
From: Wes Hardaker <wjhns1@hardakers.net>
To: "t.petch" <ietfc@btconnect.com>
Organization: Sparta
References: <006c01cb5f18$de6e1040$4001a8c0@gateway.2wire.net> <C8C7828B.3E8AA%yiu_lee@cable.comcast.com> <20100928203506.GC96620@elstar.local> <F362BA0B-ED6D-4150-BEA8-97EACB60D18A@cable.comcast.com> <015901cb5faa$a1f5a320$4001a8c0@gateway.2wire.net> <sdmxr0aaw8.fsf@wjh.hardakers.net> <007d01cb5ff5$f70de3e0$4001a8c0@gateway.2wire.net>
Date: Wed, 29 Sep 2010 11:47:13 -0700
In-Reply-To: <007d01cb5ff5$f70de3e0$4001a8c0@gateway.2wire.net> (t. petch's message of "Wed, 29 Sep 2010 18:47:07 +0200")
Message-ID: <sdiq1o2xqm.fsf@wjh.hardakers.net>
User-Agent: Gnus/5.110011 (No Gnus v0.11) Emacs/23.2 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
Cc: isms <isms@ietf.org>, "Lee, Yiu" <Yiu_Lee@Cable.Comcast.com>
Subject: Re: [Isms] status and future of the isms working group
X-BeenThere: isms@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mailing list for the ISMS working group <isms.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isms>
List-Post: <mailto:isms@ietf.org>
List-Help: <mailto:isms-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Sep 2010 18:46:52 -0000

>>>>> On Wed, 29 Sep 2010 18:47:07 +0200, "t.petch" <ietfc@btconnect.com> said:

tp> I am saying that at the least, a KSM I-D has to parallel RFC5591
tp> (not USM), covering all the topics that that covers.  It will
tp> probably specify that all the additional parameters introduced by
tp> RFC5590 are ignored, but if it says anything else, then I think we
tp> will need a UDP Transport Model.

Sounds like a one bullet incoming request saying "ignore the
tmStateReference" solves all your problems then.  (and the outgoing
doesn't need anything since by not creating a tmStateReference on the
outgoing path, you're already ignoring it).

tp> And then there are the interactions with Kerberos; shades of VACM
tp> and RADIUS perhaps, in that the Command Responder is setting up a
tp> connection(/session/transport) to a third party, which needs
tp> specifying?

I think I'll stop suggesting solutions as we haven't agreed to do the
work.  That being said, all of the above have already been accomplished
by two independent sets of folks so I know they can be worked out.
-- 
Wes Hardaker
Cobham Analytic Solutions
