Re: [dhcwg] Please review draft-ietf-pcp-dhcp, particularly section 5.

"Bernie Volz (volz)" <> Thu, 20 March 2014 13:52 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 42D901A074E for <>; Thu, 20 Mar 2014 06:52:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -15.048
X-Spam-Status: No, score=-15.048 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.547, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id MhFUJBEiR1wZ for <>; Thu, 20 Mar 2014 06:52:39 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id E43C71A06D2 for <>; Thu, 20 Mar 2014 06:52:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;;; l=5705; q=dns/txt; s=iport; t=1395323550; x=1396533150; h=from:to:cc:subject:date:message-id:references: content-transfer-encoding:mime-version; bh=vC4f3JuMik/kmaJ7urJlPZLkYGa8JF/4ha61ZrhoLdU=; b=Pt9PexkFlAi+38pw/Ql0ZdN4YpOthfi7WshJ5W3OIKdJv8ptUA3VIKxq HpilFzbRzAVNOzYIBT7Lgcv185SVhuSx5CAf+H76u9lSWftM2NJSiErFt IM5GikPXQzcc9BbTaylCmhJ7kMUyPp0EmBN9NtSlvLCyffdyyNzC+cwKc g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="4.97,694,1389744000"; d="scan'208";a="308621655"
Received: from ([]) by with ESMTP; 20 Mar 2014 13:52:29 +0000
Received: from ( []) by (8.14.5/8.14.5) with ESMTP id s2KDqTGT018496 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 20 Mar 2014 13:52:29 GMT
Received: from ([]) by ([]) with mapi id 14.03.0123.003; Thu, 20 Mar 2014 08:52:29 -0500
From: "Bernie Volz (volz)" <>
To: Ted Lemon <>, "" <>
Thread-Topic: [dhcwg] Please review draft-ietf-pcp-dhcp, particularly section 5.
Thread-Index: AQHPQ3gRGS6zp6HuO0u6GVs38nhhAZrph5CAgABa8DGAAAkBsIAAW/QA//+tTdCAAApXgA==
Date: Thu, 20 Mar 2014 13:52:28 +0000
Message-ID: <>
References: <> <> <>, <> <> <> <>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "" <>
Subject: Re: [dhcwg] Please review draft-ietf-pcp-dhcp, particularly section 5.
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 20 Mar 2014 13:52:41 -0000

BTW: One nice thing to consider for the DHCPv6 multiple option instances design is that at least for the single PCP instance case, it would work immediately (on all DHCPv6 clients and servers).

I don't know how common it will be for there to be multiple PCP servers that clients need to contact.

(The downside with this is of course that few may implement the multiple PCP servers support unless it is widely required?)

- Bernie

-----Original Message-----
From: Bernie Volz (volz) 
Sent: Thursday, March 20, 2014 9:30 AM
To: 'Ted Lemon';
Subject: RE: [dhcwg] Please review draft-ietf-pcp-dhcp, particularly section 5.

FYI - Adding back dhcwg as I think this is important to keep there.

The only issue with DHCPv6 multiple options is the ordering - if ordering is important, you should not use them. In the PCP case, I don't see that ordering matters as the draft requires using each of them.

DHCPv6 clients and servers already have to deal with multiple instances of the same option so I don't think there are any significant issues here. (Whereas in DHCPv4, that has not been the case to date, so that's why there is more significant concern.)

The guidelines are:

   DHCPv6 does allow for multiple instances of a given option, and they
   are treated as distinct values following the defined format, however
   this feature is generally preferred to be restricted to protocol
   class features (such as the IA_* series of options).  In such cases,
   it is better to define an option as an array if it is possible.  It
   is recommended to clarify (with normative language) whether a given
   DHCPv6 option may appear once or multiple times.  The default
   assumption is only once.


16.  Singleton options

   Although [RFC3315] states that each option type MAY appear more than
   once, the original idea was that multiple instances are reserved for
   stateful options, like IA_NA or IA_PD.  For most other options it is
   usually expected that they will appear at most once.  Such options
   are called singleton options.  Sadly, RFCs have often failed to
   clearly specify whether a given option can appear more than once or

   Documents that define new options SHOULD state whether these options
   are singletons or not.  Unless otherwise specified, newly defined
   options are considered to be singletons.  If multiple instances are
   allowed, the document MUST explain how to use them.  Care should be
   taken to not assume the they will be processed in the order they
   appear in the message.  See Section 17 for more details.

(There's more in section 17.)

I don't really care that much which we go as I think either will require code changes in some (or most) clients and servers (servers may readily support configuring multiple instances of the options and probably don't support the <sub-length><address(es)> encoding either).

Personally, I don't see a problem with multiple instances of the options as that is the way DHCPv6 was designed. Again, the only issue is ordering (since this would require specialized handling on the server configuration to allow you to define the order). For clients, order might also be an issues in how they store the data (i.e., if lists are maintained, is a new instances inserted at start or end of list).

I WOULD like to see multiple instances of options used in the way PCP proposed - i.e., where there really are more than one thing a client needs to do RATHER than alternative values (i.e., list of addresses to contact for an instance). This is in keeping how we currently handle things like the DNS server address list and domain search list.

While we could encode this as proposed for DHCPv4, I also see no need to encode it that way for this particular usage.

I guess we need to get some rough consensus here as to what the DHC WG would prefer as this will set a precedence. So it would be great for others to chime in. (Note that my comments on this entire thread are to be taken as an individual with WG co-chair hat off.)

Again, my feeling is that when order is required or when there are a list of 'equal' values (i.e., try one or more of these addresses to reach a service), we should use a single option. When there are possibly multiple items that ALL must be used (simultaneously and there is no order importance), multiple options would be fine. This is exactly how IA_* and IAADDR/IAPREFIX and the multiple vendor options instances all work.

- Bernie

-----Original Message-----
From: Ted Lemon [] 
Sent: Thursday, March 20, 2014 9:07 AM
Cc: Bernie Volz (volz)
Subject: Re: [dhcwg] Please review draft-ietf-pcp-dhcp, particularly section 5.

On Mar 20, 2014, at 8:49 AM, <>; <>; wrote:
> Changing the format of the dhcpv4 option to be complaint with 3396 would lead to a dhcpv4 option and a dhcpv6 option that are not similar. Are you fine with that? Should we update only the dhcpv4 part of the document?

FWIW, I don't really see much value in the semantics of multiple options, and would rather see the DHCPv6 and DHCPv4 options done the same way.   It's not something that would stop me approving the document, but we did discuss this when the option guidelines draft was done, and it seemed that there was strong skepticism, which I _think_ was expressed in the draft, about giving semantic meaning to the presence of multiple options.