Re: [homenet] Homenets and MPVD

Pierre Pfister <> Tue, 03 February 2015 07:46 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 2B0801A86EF for <>; Mon, 2 Feb 2015 23:46:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.357
X-Spam-Status: No, score=-1.357 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_COM=0.553, T_RP_MATCHES_RCVD=-0.01] autolearn=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id gQBbGwtARFLf for <>; Mon, 2 Feb 2015 23:46:54 -0800 (PST)
Received: from ( [IPv6:2001:41d0:8:408c::1111]) by (Postfix) with ESMTP id 4EB5C1A86E3 for <>; Mon, 2 Feb 2015 23:46:54 -0800 (PST)
Received: by (Postfix, from userid 112) id 697FE60900; Tue, 3 Feb 2015 08:46:53 +0100 (CET)
Received: from [IPv6:2001:470:c974:1:c186:5caf:7a1f:fc54] (unknown [IPv6:2001:470:c974:1:c186:5caf:7a1f:fc54]) (Authenticated sender: by (Postfix) with ESMTPSA id 9EBB260653; Tue, 3 Feb 2015 08:46:51 +0100 (CET)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Pierre Pfister <>
In-Reply-To: <>
Date: Tue, 3 Feb 2015 08:46:53 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <>
To: Brian E Carpenter <>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <>
Subject: Re: [homenet] Homenets and MPVD
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 03 Feb 2015 07:46:56 -0000

Hello Brian,

MIF targets host configuration with PVDs. For that purpose, they are likely to do it using DHCP and RA options.
Service providers will also use such options for CPE routers configuration, associated with the delegated prefixes during the DHCP exchange.

Current HNCP strategy is to abstract what can be conveyed inside DHCP options by sharing them directly with all other routers.
For every external connection, CPE routers will advertise an External Connection TLV (Section 6.1. in HNCP).
This TLV may contain one or multiple Delegated Prefix TLVs as well as raw DHCP options (in the DHCPv4 or DHCPv6 TLV) associated with the external connection (e.g. DNS delegated zone or search domains).
Each Delegated Prefix may as well be associated with different DHCP options (e.g. Prefix class options).

All routers gather this information through HNCP and use it to configure hosts. DHCP options that are associated with a given delegated prefix are given to hosts associated with the link prefix provided by the prefix assignment algorithm. DHCP options that are not associated with a delegated prefix are aggregated and given to the host (Excepted for the DNS server option, as the router is used as DNS relay).
For now, the aggregation of such information is not specified (although in practice it can be done quite easily for most DHCP options).
But I believe it will be much clearer once MIF provides PVD specifications.

I think this approach will be sufficient. If it happen to not be, External Connection TLVs and Delegated Prefixes TLVs could contain other types of TLVs.



Le 3 févr. 2015 à 00:56, Brian E Carpenter <>; a écrit :

> Hi,
> I find myself wondering how draft-ietf-homenet-prefix-assignment
> and draft-ietf-homenet-hncp will be reconciled with the MIF
> MPVD architecture
> (
> Has anybody thought about that yet?
> Regards
>   Brian
> _______________________________________________
> homenet mailing list