Re: Security Architecture for DHCP
bound@zk3.dec.com Mon, 21 April 1997 17:02 UTC
Received: from cnri by ietf.org id aa17608; 21 Apr 97 13:02 EDT
Received: from marge.bucknell.edu by CNRI.Reston.VA.US id aa29084; 21 Apr 97 13:02 EDT
Received: from reef.bucknell.edu by mail.bucknell.edu; (5.65v3.2/1.1.8.2/17Jul96-0109PM) id AA22554; Mon, 21 Apr 1997 12:57:23 -0400
Date: Mon, 21 Apr 1997 12:57:23 -0400
Message-Id: <9704211613.AA25931@wasted.zk3.dec.com>
Errors-To: droms@bucknell.edu
Reply-To: dhcp-v4@bucknell.edu
Originator: dhcp-v4@bucknell.edu
Sender: dhcp-v4@bucknell.edu
Precedence: bulk
From: bound@zk3.dec.com
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: Re: Security Architecture for DHCP
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: Discussion of DHCP for IPv4
Olafur, >I have an idea maybe for DHCPv6 that will "eliminate" relay agents for >DHCPv6 and reviewing it with Charlie now. It that works then that >special case for DHCPv6 will be gone. Forget this. The idea won't work and we need the relay as in DHCPv4 and it has served that protocol well. Just was checking before we go to IETF last call. So relays exist for DHCPv6 too. thx /jim
- Security Architecture for DHCP bound
- Re: Security Architecture for DHCP Ted Lemon
- Re: Security Architecture for DHCP bound
- Re: Security Architecture for DHCP bound
- Re: Security Architecture for DHCP Ted Lemon
- Re: Security Architecture for DHCP Olafur Gudmundsson
- Re: Security Architecture for DHCP bound