Re: [Isms] Moving into some design/architectureissuesofExtendedVACM

To: "'David Harrington'" <ietfdbh at comcast.net>, "'Juergen Schoenwaelder'" <j.schoenwaelder at jacobs-university.de>
Subject: Re: [Isms] Moving into some design/architectureissuesofExtendedVACM
From: "David B. Nelson" <dnelson at elbrysnetworks.com>
Date: Thu, 11 Jun 2009 13:39:23 -0400
Cc: isms at ietf.org
Delivered-to: isms at core3.amsl.com
In-reply-to: <008601c9eab9$b15ab150$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>
Organization: Elbrys Networks, Inc.
References: <01fe01c9e9b1$607f52d0$0600a8c0 at china.huawei.com><002201c9e9ea$488a1dc0$6801a8c0 at oemcomputer><7D5B6351B90B4B7FB309277995E141F9 at NEWTON603><00e901c9e9fa$f7642100$6801a8c0 at oemcomputer><000601c9ea00$00795120$0600a8c0 at china.huawei.com><EBD40065B07A416BB5D47DDD8FC267BD at NEWTON603><006e01c9ea38$30aeccc0$6801a8c0 at oemcomputer><657B1423308A4454B0CE8A9BC3B92D41 at NEWTON603><20090611140545.GA9442 at elstar.local><007601c9eab0$fb7da930$0600a8c0 at china.huawei.com><20090611171411.GA388 at elstar.local> <008601c9eab9$b15ab150$0600a8c0 at china.huawei.com>
Thread-index: AcnquA40mmiN69sfRgyXI5Tq2P4ZGAAAZ2KAAABoC9A=

I've sent other responses in this thread this morning, but the Elbrys
Networks DNS servers don't seem to like the ietf.org domain and my outgoing
mail often languishes.  Sigh.

References:
- [Isms] FW: [OPS-DIR] [MIB-DOCTORS] FW: Recharter: ISMS
  - From: David B Harrington
- Re: [Isms] FW: [OPS-DIR] [MIB-DOCTORS] FW: Recharter: ISMS
  - From: Randy Presuhn
- [Isms] Moving into some design / architecture issues of Extended VACM
  - From: Dave Nelson
- Re: [Isms] Moving into some design / architecture issues of ExtendedVACM
  - From: Randy Presuhn
- Re: [Isms] Moving into some design / architecture issues ofExtendedVACM
  - From: David Harrington
- Re: [Isms] Moving into some design / architecture issuesofExtendedVACM
  - From: Dave Nelson
- Re: [Isms] Moving into some design / architectureissuesofExtendedVACM
  - From: Randy Presuhn
- 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: David Harrington

Prev by Date: Re: [Isms] Moving into some design/architectureissuesofExtendedVACM
Next by Date: Re: [Isms] Moving into some design / architecture issues of Extended VACM
Previous by thread: Re: [Isms] Moving into some design/architectureissuesofExtendedVACM
Next by thread: Re: [Isms] Moving into some design /architectureissuesofExtendedVACM
Index(es):
- Date
- Thread

Re: [Isms] Moving into some design/architectureissuesofExtendedVACM

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