IETF Logo Mail Archive

[dhcwg] Re: draft-bakke-dhc-snmp-trap-00.txt

Mark Bakke <mbakke@cisco.com> Mon, 23 September 2002 14:04 UTC

Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA09539 for <dhcwg-archive@odin.ietf.org>; Mon, 23 Sep 2002 10:04:56 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g8NE6IR12557 for dhcwg-archive@odin.ietf.org; Mon, 23 Sep 2002 10:06:18 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8NE6Iv12554 for <dhcwg-web-archive@optimus.ietf.org>; Mon, 23 Sep 2002 10:06:18 -0400
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA09529 for <dhcwg-web-archive@ietf.org>; Mon, 23 Sep 2002 10:04:26 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8NDxBv12246; Mon, 23 Sep 2002 09:59:11 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8NDu0v12127 for <dhcwg@optimus.ietf.org>; Mon, 23 Sep 2002 09:56:00 -0400
Received: from sj-msg-core-3.cisco.com (sj-msg-core-3.cisco.com [171.70.157.152]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA09093 for <dhcwg@ietf.org>; Mon, 23 Sep 2002 09:54:08 -0400 (EDT)
Received: from sj-msg-av-1.cisco.com (sj-msg-av-1.cisco.com [171.69.11.151]) by sj-msg-core-3.cisco.com (8.12.2/8.12.2) with ESMTP id g8NDtM3x029616; Mon, 23 Sep 2002 06:55:22 -0700 (PDT)
Received: from nisser.cisco.com (localhost [127.0.0.1]) by sj-msg-av-1.cisco.com (8.12.2/8.12.2) with ESMTP id g8NDtRlY021489; Mon, 23 Sep 2002 06:55:27 -0700 (PDT)
Received: from cisco.com (mbakke-lnx2.cisco.com [64.101.211.59]) by nisser.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id GAA15349; Mon, 23 Sep 2002 06:55:26 -0700 (PDT)
Message-ID: <3D8F1D4E.B670EAE@cisco.com>
Date: Mon, 23 Sep 2002 08:55:26 -0500
From: Mark Bakke <mbakke@cisco.com>
X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.9-34.cisco.2 i686)
X-Accept-Language: en, de
MIME-Version: 1.0
To: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
CC: "'dhcwg@ietf.org'" <dhcwg@ietf.org>, "snmpv3@lists. tislabs. com (E-mail)" <snmpv3@lists.tislabs.com>, mibs@ops.ietf.org
References: <A451D5E6F15FD211BABC0008C7FAD7BC0EF24DC4@nl0006exch003u.nl.lucent.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [dhcwg] Re: draft-bakke-dhc-snmp-trap-00.txt
Sender: dhcwg-admin@ietf.org
Errors-To: dhcwg-admin@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Id: <dhcwg.ietf.org>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

I assumed that, when we get to configuring SNMPv3 security,
that the names "joe" and "bob" would be separately associated
with their keys.  I wanted to keep this particular DHCP
option scope to include the notification list, and the names
would reference keys configured somewhere else (perhaps another
DHCP option, but since I haven't seen encrypted DHCP, this
might not work).  In other words, I don't know, but I think
that if it was DHCP, it would be better as a separate option.

Any ideas?

"Wijnen, Bert (Bert)" wrote:
> 
> So in your new proposal, how did/do users Joe and Bob get
> defined with their secret keys etc at the agent side?
> 
> Thanks,
> Bert

-- 
Mark A. Bakke
Cisco Systems
mbakke@cisco.com
763.398.1054
_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www1.ietf.org/mailman/listinfo/dhcwg

v2.23.0 | Report a Bug | By Email