Re: [Isms] pre11 comments
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Isms] pre11 comments
Hi -
> From: "David B. Nelson" <dnelson at elbrysnetworks.com>
> To: <isms at ietf.org>
> Sent: Thursday, July 24, 2008 10:39 AM
> Subject: Re: [Isms] pre11 comments
...
> There is an "other side of the coin" type of added cost if there are
> multiple TMs in use, with a single namespace. In that case, each name would
> need to be entered twice in the VACM table(s), with differing "labels".
> Without labels, the names would only need to be entered once.
...
If this group had allowed itself to address the user/group VACM mapping
(which is really needed to solve the configuration problem the group
is trying to address) then this would be a non-issue. (ThiFrom isms-bounces at ietf.org Thu Jul 24 13:06:43 2008
Return-Path: <isms-bounces at ietf.org>
X-Original-To: isms-archive at megatron.ietf.org
Delivered-To: ietfarch-isms-archive at core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
by core3.amsl.com (Postfix) with ESMTP id 670CD3A68F4;
Thu, 24 Jul 2008 13:06:43 -0700 (PDT)
X-Original-To: isms at core3.amsl.com
Delivered-To: isms at core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
by core3.amsl.com (Postfix) with ESMTP id E17653A67F5
for <isms at core3.amsl.com>; Thu, 24 Jul 2008 13:06:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0
X-Spam-Level:
X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none]
Received: from mail.ietf.org ([64.170.98.32])
by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id PtPGETSe4Oui for <isms at core3.amsl.com>;
Thu, 24 Jul 2008 13:06:41 -0700 (PDT)
Received: from elasmtp-dupuy.atl.sa.earthlink.net
(elasmtp-dupuy.atl.sa.earthlink.net [209.86.89.62])
by core3.amsl.com (Postfix) with ESMTP id 2F9773A68F4
for <isms at ietf.org>; Thu, 24 Jul 2008 13:06:41 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
s=dk20050327; d=mindspring.com;
b=SMKENWUbzHu7pDRrgRkydn0A04Wa75c2waTWI/nclM80xqv1RmHqbo41h9XfgOVw;
h=Received:Message-ID:From:To:References:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:X-MimeOLE:X-ELNK-Trace:X-Originating-IP;
Received: from [66.167.206.160] (helo=oemcomputer)
by elasmtp-dupuy.atl.sa.earthlink.net with esmtpa (Exim 4.67)
(envelope-from <randy_presuhn at mindspring.com>) id 1KM75E-000589-JL
for isms at ietf.org; Thu, 24 Jul 2008 16:06:40 -0400
Message-ID: <002801c8edc8$d4a9d080$6801a8c0 at oemcomputer>
From: "Randy Presuhn" <randy_presuhn at mindspring.com>
To: <isms at ietf.org>
References: <006401c8dc30$bac0af30$51f780de at china.huawei.com><sd63rmy615.fsf at wes.hardakers.net><4F599A473EF04ECD99F4C358B291245E at xpsuperdvd2><sdskuqwoli.fsf at wes.hardakers.net><200807040057.m640v5DL015394 at grapenut.srv.cs.cmu.edu><ED7BF45E5D16B2A3ECD2E782 at atlantis.pc.cs.cmu.edu><20080724071719.GA5011 at elstar.local><153AB67386CBEFDB61867CE0 at atlantis.pc.cs.cmu.edu><200807241246.m6OCjgDE013865 at raisinbran.srv.cs.cmu.edu><BAD73561504C83A3F8959045 at atlantis.pc.cs.cmu.edu>
<E465D77D24FC49EF968184764165BCC5 at xpsuperdvd2>
Date: Thu, 24 Jul 2008 13:06:58 -0700
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1478
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478
X-ELNK-Trace: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d888a63b7957ab9b23b36a783482531b7b1b9ad15d4ce7f4380d350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 66.167.206.160
Subject: Re: [Isms] pre11 comments
X-BeenThere: isms at ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mailing list for the ISMS working group <isms.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/isms>,
<mailto:isms-request at ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/isms>
List-Post: <mailto:isms at ietf.org>
List-Help: <mailto:isms-request at ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isms>,
<mailto:isms-request at ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: isms-bounces at ietf.org
Errors-To: isms-bounces at ietf.org
Hi -
> From: "David B. Nelson" <dnelson at elbrysnetworks.com>
> To: <isms at ietf.org>
> Sent: Thursday, July 24, 2008 10:39 AM
> Subject: Re: [Isms] pre11 comments
...
> There is an "other side of the coin" type of added cost if there are
> multiple TMs in use, with a single namespace. In that case, each name would
> need to be entered twice in the VACM table(s), with differing "labels".
> Without labels, the names would only need to be entered once.
...
If this group had allowed itself to address the user/group VACM mapping
(which is really needed to solve the configuration problem the group
is trying to address) then this would be a non-issue. (This whole s whole process
started because the provisioning of USM and VACM was perceived to
be too much work. The TMs discussed here work around the provisioning
of USM, but don't address the user/group mapping in VACM needed
to make it actually work.
Look on the bright side - if/when the WG gets around to automating
the VACM user/group mapping, the problem of the differing labels
will go "poof".
Randy
_______________________________________________
Isms mailing list
Isms at ietf.org
https://www.ietf.org/mailman/listinfo/isms
process
started because the provisioning of USM and VACM was perceived to
be too much work. The TMs discussed here work around the provisioning
of USM, but don't address the user/group mapping in VACM needed
to make it actually work.
Look on the bright side - if/when the WG gets around to automating
the VACM user/group mapping, the problem of the differing labels
will go "poof".
Randy
_______________________________________________
Isms mailing list
Isms at ietf.org
https://www.ietf.org/mailman/listinfo/isms
Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.