Ralph Droms | 1 Dec 2003 14:46
Picon
Favicon

***DRAFT*** minutes from dhc WG meeting in Minneapolis

Included below are ***draft*** minutes from the WG meeting in 
Minneapolis.  Please review and respond with comments before 9AM EST, Fri 12/5.

- Ralph

=====

Administrivia                                      Ralph Droms
   Agenda bashing
   Current last calls: failover; DHCPv4 threat analysis; PXE options

New I-Ds to be considered by the dhc WG

   Droms reviewed 6 I-Ds that will be reviewed as WG work items; these
   I-Ds will be published after IETF 58 publication moratorium:

   DHCPv6 support for IPv6 Transition,
   <draft-ietf-dhc-dhcpv6-ipv6trans-00.txt>
   A.K. Vijayabhaskar, S. Daniel Park

   DHCP Discovery Extensions,
   <draft-rentschler-dhc-discovery-00.txt>
   Rentschler

   DHCP Interface Information Option,
   <draft-rentschler-dhc-interface-opt-00.txt>
   Markus Rentschler

   DHCP Option for Proxy Server Configuration,
   <draft-ietf-dhc-proxyserver-opt-00.txt>
(Continue reading)

The IESG | 1 Dec 2003 16:07
Picon
Favicon

Last Call: 'Authentication of DHCP Relay Agent Options Using IPsec' to Proposed Standard

The IESG has received a request from the Dynamic Host Configuration WG to 
consider the following document:

- 'Authentication of DHCP Relay Agent Options Using IPsec '
   <draft-ietf-dhc-relay-agent-ipsec-01.txt> as a Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send any comments to the
iesg <at> ietf.org or ietf <at> ietf.org mailing lists by 2003-12-15.

The file can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-dhc-relay-agent-ipsec-01.txt
Kim Kinnear | 1 Dec 2003 16:42
Picon
Favicon

Re: draft-ietf-dhc-leasequery-06 clarification

At 12:42 PM 11/27/2003, Kostur, Andre wrote:

>I think that the draft has a potential ambiguity in handling option 82 in the leasequery replies. 
>
>RFC 3046 mandates that option 82 SHOULD be the last option in the reply packet.  The leasequery draft only
says that it will be included in the packet if the relay requested option 82 (and assuming that the DHCP
server has information to put in option 82).
>
>So, from a leasequery perspective, if the server has data to put in option 82, where should the draft
specify that the option should be placed within the packet?  Should it also specify that option 82 SHOULD be
the last option within the packet, and may not be placed in the overloaded fields?  Or should the draft
specify that option 82 within the leasequery reply may be anywhere within the options field?
>
>My opinion on the matter: I think that the presence of option 82 within a leasequery reply serves a
different purpose that the presence of option 82 within a "normal" DHCP reply.  Within a normal reply,
option 82 needs to be able to be removed by the Relay without potentially disrupting any 3118
authentication that may be in use.  Also option 82 may be carrying some sort of "routing" information for
where this reply is really destined for (which circuit ID, which remote ID, etc).  However in a leasequery
reply the presence of option 82 is simply "dead data" that is being passed from the DHCP server to the relay. 
It has no more significance within the packet than the presence of, say, option 3.  Given these points, I
would suggest that the draft specify that the option 82 inserted in a leasequery reply does not have to
follow the rules of 3046, but is to be handled like any other option (order & positioning is irrelevant, it
may be placed in overloads, etc...).

        I agree with your analysis.  I would expect that we could
        add a sentence or two to clarify this situation as part
        of the IETF last call comment handling.

>And come to think of it, another wrinkle within this mechanism: what would be the correct behaviour for a
DHCP server which receives a leasequery that has an option 82?  According to 3046, the DHCP server would be
(Continue reading)

Internet-Drafts | 1 Dec 2003 21:27
Picon
Favicon

I-D ACTION:draft-ietf-dhc-dhcpv6-opt-nisconfig-04.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Dynamic Host Configuration Working Group of the IETF.

	Title		: NIS Configuration Options for DHCPv6
	Author(s)	: a. Vijayabhaskar
	Filename	: draft-ietf-dhc-dhcpv6-opt-nisconfig-04.txt
	Pages		: 6
	Date		: 2003-12-1
	
This document describes four options for NIS-related configuration
information in DHCPv6: NIS Servers [3], NIS+ Servers [3], NIS Client
Domain Name [3], NIS+ Client Domain name [3].

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-dhc-dhcpv6-opt-nisconfig-04.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-dhc-dhcpv6-opt-nisconfig-04.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

(Continue reading)

Internet-Drafts | 2 Dec 2003 21:33
Picon
Favicon

I-D ACTION:draft-ietf-dhc-rapid-commit-opt-00.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Dynamic Host Configuration Working Group of the IETF.

	Title		: Rapid Commit Option for DHCPv4
	Author(s)	: S. Park
	Filename	: draft-ietf-dhc-rapid-commit-opt-00.txt
	Pages		: 11
	Date		: 2003-12-2
	
This document defines a new DHCPv4 option, modeled on the DHCPv6      
Rapid Commit option, for obtaining IP address and configuration      
information using a 2-message exchange rather than the usual 4-
message exchange, expediting client configuration.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-dhc-rapid-commit-opt-00.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-dhc-rapid-commit-opt-00.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.
(Continue reading)

Internet-Drafts | 2 Dec 2003 21:33
Picon
Favicon

I-D ACTION:draft-ietf-dhc-server-mib-09.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Dynamic Host Configuration Working Group of the IETF.

	Title		: Dynamic Host Configuration Protocol for IPv4 (DHCPv4) Server MIB
	Author(s)	: R. Hibbs, G. Waters
	Filename	: draft-ietf-dhc-server-mib-09.txt
	Pages		: 47
	Date		: 2003-12-2
	
This memo defines an experimental portion of the Management 
Information Base (MIB) for use with network management protocols in 
the Internet Community.  In particular, it defines objects used for 
the management of Dynamic Host Configuration Protocol for IPv4 
(DHCPv4) and Bootstrap Protocol (BOOTP) servers.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-dhc-server-mib-09.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-dhc-server-mib-09.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

(Continue reading)

Rentschler, Markus | 3 Dec 2003 09:22
Picon

WG: I-D ACTION:draft-ietf-dhc-server-mib-09.txt


	dhcpv4ServerAddressTable OBJECT-TYPE 
		SYNTAX	 SEQUENCE OF  Dhcpv4ServerAddressEntry 
		MAX-ACCESS  not-accessible 
		STATUS  current 
		DESCRIPTION 
			"An optional list of addresses that are known by
this server. The list MUST contain addresses that have not
expired. The list MUST NOT contain addresses that have never been assigned
by the server UNLESS the 				lease is
pre-configured in the server (e.g., a static lease for a host). Expired
leases MAY appear during the 				time they are
'remembered' by the server for subsequent assignment to the same host." 
	::= { dhcpv4ServerConfiguration 4 } 
>  
> 	Dhcpv4ServerAddressEntry ::= SEQUENCE { 
> 		dhcpv4ServerAddress
> InetAddressIPv4, 
> 		dhcpv4ServerAddressSubnetMask
> InetAddressPrefixLength, 
> 		dhcpv4ServerAddressRange
> InetAddressIPv4, 
> 		dhcpv4ServerAddressLeaseType 			INTEGER, 
> 		dhcpv4ServerAddressTimeRemaining 		Unsigned32, 
> 		dhcpv4ServerAddressAllowedProtocol		 INTEGER, 
> 		dhcpv4ServerAddressServedProtocol 		INTEGER, 
> 		dhcpv4ServerAddressPhysicalAddress 	DhcpPhysicalAddress,
> 
> 		dhcpv4ServerAddressClientId
> OCTET STRING, 
(Continue reading)

Internet-Drafts | 3 Dec 2003 21:26
Picon
Favicon

I-D ACTION:draft-ietf-dhc-dhcpv6-stateless-02.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Dynamic Host Configuration Working Group of the IETF.

	Title		: A Guide to Implementing Stateless DHCPv6 Service
	Author(s)	: R. Droms
	Filename	: draft-ietf-dhc-dhcpv6-stateless-02.txt
	Pages		: 10
	Date		: 2003-12-3
	
Stateless DHCPv6 service is used by nodes to obtain configuration
information such as the addresses of DNS recursive name servers
that does not require the maintenance of any dynamic state for
individual clients.  A node that uses stateless DHCP must have
obtained its IPv6 addresses through some other mechanism,
typically stateless address autoconfiguration.  This document is a
guide to the protocol messages and options that must be
implemented to provide stateless DHCPv6 service.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-dhc-dhcpv6-stateless-02.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-dhc-dhcpv6-stateless-02.txt".

A list of Internet-Drafts directories can be found in
(Continue reading)

Internet-Drafts | 3 Dec 2003 21:27
Picon
Favicon

I-D ACTION:draft-ietf-dhc-dhcpv6-opt-nisconfig-05.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Dynamic Host Configuration Working Group of the IETF.

	Title		: NIS Configuration Options for DHCPv6
	Author(s)	: a. Vijayabhaskar
	Filename	: draft-ietf-dhc-dhcpv6-opt-nisconfig-05.txt
	Pages		: 6
	Date		: 2003-12-3
	
This document describes four options for NIS-related configuration
information in DHCPv6: NIS Servers [3], NIS+ Servers [3], NIS Client
Domain Name [3], NIS+ Client Domain name [3].

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-dhc-dhcpv6-opt-nisconfig-05.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-dhc-dhcpv6-opt-nisconfig-05.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

(Continue reading)

Barr Hibbs | 4 Dec 2003 00:00

RE: I-D ACTION:draft-ietf-dhc-server-mib-09.txt


The "dhcpv4ServerAddressTable" is NOT intended to be used for configuration
of a DHCPv4 server, nor are ANY other tables declared in the proposed MIB
extension.  If the text does not make this clear I will consider suggested
wording changes that will add the needed clarity.

--Barr

> -----Original Message-----
> From: dhcwg-admin <at> ietf.org [mailto:dhcwg-admin <at> ietf.org]On Behalf Of
> Rentschler, Markus
> Sent: Wednesday, December 03, 2003 00:22
>
> This is a table with entries that contains both trigger criteria and
> parameters that are assigned after the trigger criteria have matched.  Is
> this table intended to be used to configure static leases?  To
> me the text does not make this clear.
>

Gmane