Re: [Isms] Moving into some design/architecture issuesofExtendedVACM

To: <isms at ietf.org>
Subject: Re: [Isms] Moving into some design/architecture issuesofExtendedVACM
From: "Dave Nelson" <d.b.nelson at comcast.net>
Date: Tue, 16 Jun 2009 09:46:18 -0400
Delivered-to: isms at core3.amsl.com
In-reply-to: <013b01c9ee85$cd6fff60$0600a8c0 at china.huawei.com>
List-archive: <http://www.ietf.org/mail-archive/web/isms>
List-help: <mailto:isms-request@ietf.org?subject=help>
List-id: Mailing list for the ISMS working group <isms.ietf.org>
List-post: <mailto:isms@ietf.org>
List-subscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=subscribe>
List-unsubscribe: <https://www.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@ietf.org?subject=unsubscribe>
References: <657B1423308A4454B0CE8A9BC3B92D41 at NEWTON603><20090611140545.GA9442 at elstar.local><007601c9eab0$fb7da930$0600a8c0 at china.huawei.com><20090611171411.GA388 at elstar.local><003b01c9ead6$e8e08920$6801a8c0 at oemcomputer><20090611225732.GA840 at elstar.local><0801A762ABE34A88B3FAF6D09192F5BC at NEWTON603><002501c9ee1b$6f5f1600$6801a8c0 at oemcomputer><20090616050156.GA6629 at elstar.local><000401c9ee44$1f2d0240$6801a8c0 at oemcomputer><20090616072902.GB6719 at elstar.local> <8E09C8E7F7AC41298C1AAF0979A538C9 at NEWTON603> <013b01c9ee85$cd6fff60$0600a8c0 at china.huawei.com>
Thread-index: AcnuVc8Kl8jIjfqYTvK3HWeWZgSWPAAJ319QAAIHONAAAMr/sA==

David Harrington writes...

> I think we actually have consensus about persistence.
> 
> I think everybody expects that the user-to-group mapping should go
> away when the radius-authorized session ends; ...

Excellent!

> ... we just need to figure how to do that without redesigning
> snmpv3 and the rfc3411 architecture.

I eagerly await suggestions, as I have (temporarily) run out of ideas.

Follow-Ups:
- Re: [Isms] Moving into some design/architecture issuesofExtendedVACM
  - From: David Harrington

References:
- Re: [Isms] Moving into some design /architectureissuesofExtendedVACM
  - From: Dave Nelson
- Re: [Isms] Moving into some design /architectureissuesofExtendedVACM
  - From: Juergen Schoenwaelder
- Re: [Isms] Moving into some design /architectureissuesofExtendedVACM
  - From: David Harrington
- Re: [Isms] Moving into some design /architectureissuesofExtendedVACM
  - From: Juergen Schoenwaelder
- Re: [Isms] Moving into some design /architectureissuesofExtendedVACM
  - From: Randy Presuhn
- Re: [Isms] Moving into some design /architectureissuesofExtendedVACM
  - From: Juergen Schoenwaelder
- Re: [Isms] Moving into some design/architecture issues of ExtendedVACM
  - From: Dave Nelson
- Re: [Isms] Moving into some design/architecture issues ofExtendedVACM
  - From: Randy Presuhn
- Re: [Isms] Moving into some design/architecture issues ofExtendedVACM
  - From: Juergen Schoenwaelder
- Re: [Isms] Moving into some design/architecture issuesofExtendedVACM
  - From: Randy Presuhn
- Re: [Isms] Moving into some design/architecture issuesofExtendedVACM
  - From: Juergen Schoenwaelder
- Re: [Isms] Moving into some design/architecture issuesofExtendedVACM
  - From: Dave Nelson
- Re: [Isms] Moving into some design/architecture issuesofExtendedVACM
  - From: David Harrington

Prev by Date: Re: [Isms] Moving into some design / architectureissues ofExtendedVACM
Next by Date: Re: [Isms] Moving into some design / architecture issues ofExtendedVACM
Previous by thread: Re: [Isms] Moving into some design/architecture issuesofExtendedVACM
Next by thread: Re: [Isms] Moving into some design/architecture issuesofExtendedVACM
Index(es):
- Date
- Thread

Re: [Isms] Moving into some design/architecture issuesofExtendedVACM

Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.