IETF Logo Mail Archive

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

Simon Perreault <simon.perreault@viagenie.ca> Wed, 19 March 2014 15:19 UTC

Return-Path: <simon.perreault@viagenie.ca>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BCE8B1A077B for <dhcwg@ietfa.amsl.com>; Wed, 19 Mar 2014 08:19:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level:
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.547, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PjAhGsmFMJmm for <dhcwg@ietfa.amsl.com>; Wed, 19 Mar 2014 08:19:42 -0700 (PDT)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id D3B0F1A0773 for <dhcwg@ietf.org>; Wed, 19 Mar 2014 08:19:41 -0700 (PDT)
Received: from porto.nomis80.org (unknown [IPv6:2620:0:230:c000:f981:e226:281f:c92d]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 097FE4037C for <dhcwg@ietf.org>; Wed, 19 Mar 2014 11:19:33 -0400 (EDT)
Message-ID: <5329B584.1090404@viagenie.ca>
Date: Wed, 19 Mar 2014 11:19:32 -0400
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: dhcwg@ietf.org
References: <94C682931C08B048B7A8645303FDC9F36F51A2DB17@PUEXCB1B.nanterre.francetelecom.fr> <C7964664-C302-4ABE-9CAC-1AD5D9048699@cisco.com> <489D13FBFA9B3E41812EA89F188F018E1AF1C1CA@xmb-rcd-x04.cisco.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1AF1C1CA@xmb-rcd-x04.cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/3I707bF1Z2ez-dyKDr1enYQzjwE
Subject: Re: [dhcwg] Please review draft-ietf-pcp-dhcp, particularly section 5.
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Mar 2014 15:19:45 -0000

Le 2014-03-19 09:35, Bernie Volz (volz) a écrit :
> To support 3396, you will likely have to encode the DHCPv4 PCP option as:
> 
> 	Option Code
> 	Length of option
> 	Length of PCP server 1
> 	IPv4 address(es) based on length of PCP server 1
> 	<Repeat the following as often as needed>
> 	Optional length of PCP server n
> 	     IPv4 address(es) based on PCP server n

As far as I can tell, there's no way to define this as a custom option
on ISC DHCP, whether using lengths or address counts. Just a data point.

Basically we would want this:

option pcp-server code xxx = array of array of ip-address;

But arrays of arrays seem to not be supported. :(

Simon
-- 
DTN made easy, lean, and smart --> http://postellation.viagenie.ca
NAT64/DNS64 open-source        --> http://ecdysis.viagenie.ca
STUN/TURN server               --> http://numb.viagenie.ca

v2.23.0 | Report a Bug | By Email