Re: [OPSAWG] WGLC draft-ietf-opsawg-management-stds

"Ersue, Mehmet (NSN - DE/Munich)" <mehmet.ersue@nsn.com> Mon, 30 January 2012 19:30 UTC

Return-Path: <mehmet.ersue@nsn.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D7B6D21F8631 for <opsawg@ietfa.amsl.com>; Mon, 30 Jan 2012 11:30:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.556
X-Spam-Level:
X-Spam-Status: No, score=-106.556 tagged_above=-999 required=5 tests=[AWL=0.043, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eEKPjn-vs9Jl for <opsawg@ietfa.amsl.com>; Mon, 30 Jan 2012 11:30:49 -0800 (PST)
Received: from demumfd001.nsn-inter.net (demumfd001.nsn-inter.net [93.183.12.32]) by ietfa.amsl.com (Postfix) with ESMTP id 24CEC21F858E for <opsawg@ietf.org>; Mon, 30 Jan 2012 11:30:48 -0800 (PST)
Received: from demuprx016.emea.nsn-intra.net ([10.150.129.55]) by demumfd001.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id q0UJUi0I027439 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 30 Jan 2012 20:30:46 +0100
Received: from demuexc022.nsn-intra.net (demuexc022.nsn-intra.net [10.150.128.35]) by demuprx016.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id q0UJUgNq015627; Mon, 30 Jan 2012 20:30:42 +0100
Received: from DEMUEXC006.nsn-intra.net ([10.150.128.18]) by demuexc022.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675); Mon, 30 Jan 2012 20:30:42 +0100
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, 30 Jan 2012 20:30:41 +0100
Message-ID: <80A0822C5E9A4440A5117C2F4CD36A6403563BB5@DEMUEXC006.nsn-intra.net>
In-Reply-To: <CB499481.E8B7%ietfdbh@comcast.net>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [OPSAWG] WGLC draft-ietf-opsawg-management-stds
Thread-Index: Aczd4oryAq1gW2YHSY2z7rh/6y1TYgBorCxw
References: <20120126144944.GA64823@elstar.local> <CB499481.E8B7%ietfdbh@comcast.net>
From: "Ersue, Mehmet (NSN - DE/Munich)" <mehmet.ersue@nsn.com>
To: ext David Harrington <ietfdbh@comcast.net>
X-OriginalArrivalTime: 30 Jan 2012 19:30:42.0175 (UTC) FILETIME=[A78F90F0:01CCDF85]
Cc: opsawg@ietf.org
Subject: Re: [OPSAWG] WGLC draft-ietf-opsawg-management-stds
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Jan 2012 19:30:49 -0000

Hi David,

> >> NEW:
> >> An agent entity can restrict access to a certain portion of its
MIB,
> >> e.g.
> >> restrict some manager principals to view performance-related
statistics,
> >>
> >> allow only a single designated manager principal to view or update
> >> configuration parameters or disallow other manager principals to
read
> >> the performance-related statistics.
> >
> >OK
> 
> I agree with making the text examples. I think one example should be
that
> some managers might only be allowed read-only access while others are
> allowed read-write access.
> The new text mixes operations and specific views (perf stats), so the
RO
> vs RW example is not very clearly shown.

Would this work for you? If not please provide some NEW text.

NEW: 
An agent entity can restrict access to a certain portion of its MIB,
e.g. restrict 
some manager principals to view only performance-related statistics, or
disallow 
other manager principals to read those performance-related statistics. 
An agent entity can also restrict to monitoring (read-only) as opposed
to monitoring 
and configuration (read-write) of a certain portion of its MIB, e.g.
allowing only a 
single designated manager principal to update configuration parameters.

Cheers,
Mehmet