Re: [OPSAWG] WGLC draft-ietf-opsawg-management-stds
David Harrington <ietfdbh@comcast.net> Thu, 02 February 2012 14:12 UTC
Return-Path: <ietfdbh@comcast.net>
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 2940721F85AF for <opsawg@ietfa.amsl.com>; Thu, 2 Feb 2012 06:12:36 -0800 (PST)
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=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Rh7g3NVdFiAB for <opsawg@ietfa.amsl.com>; Thu, 2 Feb 2012 06:12:35 -0800 (PST)
Received: from qmta03.westchester.pa.mail.comcast.net (qmta03.westchester.pa.mail.comcast.net [76.96.62.32]) by ietfa.amsl.com (Postfix) with ESMTP id 2675521F858D for <opsawg@ietf.org>; Thu, 2 Feb 2012 06:12:35 -0800 (PST)
Received: from omta20.westchester.pa.mail.comcast.net ([76.96.62.71]) by qmta03.westchester.pa.mail.comcast.net with comcast id V25b1i0041YDfWL532Cbjs; Thu, 02 Feb 2012 14:12:35 +0000
Received: from [192.168.1.7] ([96.252.194.151]) by omta20.westchester.pa.mail.comcast.net with comcast id V2CP1i0263GTgco3g2CSUW; Thu, 02 Feb 2012 14:12:33 +0000
User-Agent: Microsoft-MacOutlook/14.14.0.111121
Date: Thu, 02 Feb 2012 09:12:27 -0500
From: David Harrington <ietfdbh@comcast.net>
To: "Ersue, Mehmet (NSN - DE/Munich)" <mehmet.ersue@nsn.com>
Message-ID: <CB5003E2.F9F8%ietfdbh@comcast.net>
Thread-Topic: [OPSAWG] WGLC draft-ietf-opsawg-management-stds
In-Reply-To: <80A0822C5E9A4440A5117C2F4CD36A6403563BB5@DEMUEXC006.nsn-intra.net>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
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: Thu, 02 Feb 2012 14:12:36 -0000
That's better. Thanks, -- David Harrington Director, Transport Area Internet Engineering Task Force (IETF) Ietfdbh@comcast.net +1-603-828-1401 On 1/30/12 2:30 PM, "Ersue, Mehmet (NSN - DE/Munich)" <mehmet.ersue@nsn.com> wrote: >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 >
- [OPSAWG] WGLC draft-ietf-opsawg-management-stds Christopher LILJENSTOLPE
- Re: [OPSAWG] WGLC draft-ietf-opsawg-management-st… Juergen Schoenwaelder
- Re: [OPSAWG] WGLC draft-ietf-opsawg-management-st… Benoit Claise
- Re: [OPSAWG] WGLC draft-ietf-opsawg-management-st… Juergen Schoenwaelder
- Re: [OPSAWG] WGLC draft-ietf-opsawg-management-st… Benoit Claise
- Re: [OPSAWG] WGLC draft-ietf-opsawg-management-st… Ersue, Mehmet (NSN - DE/Munich)
- Re: [OPSAWG] WGLC draft-ietf-opsawg-management-st… Juergen Schoenwaelder
- Re: [OPSAWG] WGLC draft-ietf-opsawg-management-st… David Harrington
- Re: [OPSAWG] WGLC draft-ietf-opsawg-management-st… Ersue, Mehmet (NSN - DE/Munich)
- Re: [OPSAWG] WGLC draft-ietf-opsawg-management-st… Romascanu, Dan (Dan)
- Re: [OPSAWG] WGLC draft-ietf-opsawg-management-st… Ersue, Mehmet (NSN - DE/Munich)
- Re: [OPSAWG] WGLC draft-ietf-opsawg-management-st… Romascanu, Dan (Dan)
- Re: [OPSAWG] WGLC draft-ietf-opsawg-management-st… Bert Wijnen (IETF)
- Re: [OPSAWG] WGLC draft-ietf-opsawg-management-st… David Harrington
- [OPSAWG] FW: WGLC draft-ietf-opsawg-management-st… Ersue, Mehmet (NSN - DE/Munich)
- [OPSAWG] IPv6 zoneid in SNMP t.petch
- Re: [OPSAWG] IPv6 zoneid in SNMP Juergen Schoenwaelder
- Re: [OPSAWG] IPv6 zoneid in SNMP Brian E Carpenter