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

"Romascanu, Dan (Dan)" <dromasca@avaya.com> Tue, 31 January 2012 11:11 UTC

Return-Path: <dromasca@avaya.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 A758A21F8599 for <opsawg@ietfa.amsl.com>; Tue, 31 Jan 2012 03:11:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.886
X-Spam-Level:
X-Spam-Status: No, score=-102.886 tagged_above=-999 required=5 tests=[AWL=-0.287, 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 A3XPL8bxfeHj for <opsawg@ietfa.amsl.com>; Tue, 31 Jan 2012 03:11:46 -0800 (PST)
Received: from p-us1-iereast-outbound.us1.avaya.com (p-us1-iereast-outbound.us1.avaya.com [135.11.29.13]) by ietfa.amsl.com (Postfix) with ESMTP id 0E83B21F8598 for <opsawg@ietf.org>; Tue, 31 Jan 2012 03:11:45 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAFAKDLJ0+HCzI1/2dsb2JhbABDrl+BBYFyAQEBAQMBAQEPHgo0CwwEAgEIDQQEAQELBgwLAQYBJh8JCAEBBAESCBqHY50Mm2gEixAsBgGDZgGBBoJ1YwSbGYxc
X-IronPort-AV: E=Sophos;i="4.71,595,1320642000"; d="scan'208";a="229373169"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by p-us1-iereast-outbound.us1.avaya.com with ESMTP; 31 Jan 2012 06:11:44 -0500
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.13]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 31 Jan 2012 05:57:50 -0500
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: Tue, 31 Jan 2012 12:11:41 +0100
Message-ID: <EDC652A26FB23C4EB6384A4584434A040710D906@307622ANEX5.global.avaya.com>
In-Reply-To: <80A0822C5E9A4440A5117C2F4CD36A6403563ECE@DEMUEXC006.nsn-intra.net>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [OPSAWG] WGLC draft-ietf-opsawg-management-stds
Thread-Index: Aczd4oryAq1gW2YHSY2z7rh/6y1TYgBorCxwACAK2PAAAJJCkAAAUw6g
References: <20120126144944.GA64823@elstar.local><CB499481.E8B7%ietfdbh@comcast.net> <80A0822C5E9A4440A5117C2F4CD36A6403563BB5@DEMUEXC006.nsn-intra.net> <EDC652A26FB23C4EB6384A4584434A040710D8F2@307622ANEX5.global.avaya.com> <80A0822C5E9A4440A5117C2F4CD36A6403563ECE@DEMUEXC006.nsn-intra.net>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Ersue, Mehmet (NSN - DE/Munich)" <mehmet.ersue@nsn.com>, ext David Harrington <ietfdbh@comcast.net>
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: Tue, 31 Jan 2012 11:11:46 -0000

Can you please explain this and provide the reference in the text? 

Thanks and Regards,

Dan




> -----Original Message-----
> From: Ersue, Mehmet (NSN - DE/Munich) [mailto:mehmet.ersue@nsn.com]
> Sent: Tuesday, January 31, 2012 1:10 PM
> To: Romascanu, Dan (Dan); ext David Harrington
> Cc: opsawg@ietf.org
> Subject: RE: [OPSAWG] WGLC draft-ietf-opsawg-management-stds
> 
> Hi Dan,
> 
> STD62 uses the term principal to describe:
> securityName  - the principal on whose behalf access is requested
> 
> Cheers,
> Mehmet
> 
> 
> > -----Original Message-----
> > From: ext Romascanu, Dan (Dan) [mailto:dromasca@avaya.com]
> > Sent: Tuesday, January 31, 2012 11:50 AM
> > To: Ersue, Mehmet (NSN - DE/Munich); ext David Harrington
> > Cc: opsawg@ietf.org
> > Subject: RE: [OPSAWG] WGLC draft-ietf-opsawg-management-stds
> >
> > Sorry to jump in with a detail terminology question, but what does
> > exactly 'manager principal' mean, where does this term come from? It
> is
> > not used in the current version of the document AFAICT, possibly I
> > missed something in the discussion.
> >
> > Thanks and Regards,
> >
> > Dan
> >
> >
> >
> >
> >
> > > -----Original Message-----
> > > From: opsawg-bounces@ietf.org [mailto:opsawg-bounces@ietf.org] On
> > > Behalf Of Ersue, Mehmet (NSN - DE/Munich)
> > > Sent: Monday, January 30, 2012 9:31 PM
> > > To: ext David Harrington
> > > Cc: opsawg@ietf.org
> > > Subject: Re: [OPSAWG] WGLC draft-ietf-opsawg-management-stds
> > >
> > > 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 mailing list
> > > OPSAWG@ietf.org
> > > https://www.ietf.org/mailman/listinfo/opsawg