RE: [dhcwg] Brokenness of specs w.r.t. client behavior with M&O bits

<teemu.savolainen@nokia.com> Mon, 27 October 2008 06:50 UTC

Return-Path: <ipv6-bounces@ietf.org>
X-Original-To: ipngwg-archive@lists.ietf.org
Delivered-To: ietfarch-ipngwg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A8AF73A6922; Sun, 26 Oct 2008 23:50:35 -0700 (PDT)
X-Original-To: IPV6@core3.amsl.com
Delivered-To: IPV6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6C75A3A6922 for <IPV6@core3.amsl.com>; Sun, 26 Oct 2008 23:50:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.299
X-Spam-Level:
X-Spam-Status: No, score=-5.299 tagged_above=-999 required=5 tests=[AWL=1.300, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id roYsKuR-ni-J for <IPV6@core3.amsl.com>; Sun, 26 Oct 2008 23:50:33 -0700 (PDT)
Received: from mgw-mx03.nokia.com (smtp.nokia.com [192.100.122.230]) by core3.amsl.com (Postfix) with ESMTP id 595D33A6800 for <IPV6@core3.amsl.com>; Sun, 26 Oct 2008 23:50:30 -0700 (PDT)
Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213]) by mgw-mx03.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id m9R6oNx2030741; Mon, 27 Oct 2008 08:50:26 +0200
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 27 Oct 2008 08:50:21 +0200
Received: from vaebe102.NOE.Nokia.com ([10.160.244.12]) by esebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 27 Oct 2008 08:50:20 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [dhcwg] Brokenness of specs w.r.t. client behavior with M&O bits
Date: Mon, 27 Oct 2008 08:50:20 +0200
Message-ID: <DC237AE116C10E4C9AD162D6C2EE62FE01383D2B@vaebe102.NOE.Nokia.com>
In-Reply-To: <a3c826bd0810232004v50879492j97d4be8132e0cd97@mail.gmail.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [dhcwg] Brokenness of specs w.r.t. client behavior with M&O bits
Thread-Index: Ack1hUZMNBZPCIPZQn+ZMp/EmBqN5wCeeg3A
References: <7182010.12431219366974773.JavaMail.weblogic@epml09> <9A613C72-E818-410B-9769-8C34E8A78AE1@cisco.com> <200810131540.m9DFeRGR009155@rotala.raleigh.ibm.com> <BA6C47AC-1668-47CE-94D0-49C4F7A6775E@muada.com> <20081013163846.GA5577@isc.org> <FA7A47C2-0935-4BA3-A0EF-EC1773B181A0@muada.com> <20081014163236.GD5364@isc.org> <F3BF1907-5B33-4B6E-9ED8-B5AF275134BE@muada.com> <7465F7E3-931F-4924-AC84-2993AF447E68@nominum.com> <DC237AE116C10E4C9AD162D6C2EE62FE0134D3BC@vaebe102.NOE.Nokia.com> <a3c826bd0810232004v50879492j97d4be8132e0cd97@mail.gmail.com>
From: teemu.savolainen@nokia.com
To: hyunwook.cha@gmail.com
X-OriginalArrivalTime: 27 Oct 2008 06:50:20.0875 (UTC) FILETIME=[479321B0:01C93800]
X-Nokia-AV: Clean
Cc: ipv6@ietf.org, IPV6@core3.amsl.com, David_Hankins@isc.org, iljitsch@muada.com, Ted.Lemon@nominum.com, dhcwg@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ipv6-bounces@ietf.org
Errors-To: ipv6-bounces@ietf.org

Hi Joseph,

Thank you for your responses, comment inline 

>As for your question, I would say that it depends on implementations.
>AFAIK, there are already several opensources like ISC DHCP 
>which supports IA_NA(maybe IA_TA) as well as IA_PD. And 
>Windows 2008 server also does. Even though details of 
>implementations may be different, site prefixes are derived 
>from delegated prefixes and the LAN interface is configured 
>with addresses from the site prefixes as pre-configured 
>policy. Then, site prefixes are advertised through following 
>RA messages from the LAN interface and hosts have addresses 
>configured via SLAAC. However, I am not sure that ND proxy has 
>been deployed well.

Actually I was more concerned on operator policies: if operator is
running DHCPv6, will it be their policy decision whether or not to allow
hosts to request for prefixes as well? 

Consider cellular host case:
- host implements e.g. ND proxy and DHCPv6 PD for WAN connection sharing
- host attaches to a network where only DHCPv6 happens to be used
- host gets single /128 IPv6 address from DHCPv6
- host tries to get some prefixes for its LAN interface with DHCPv6 PD,
but network's policy rejects the prefix request

Now what can host do? Tell user that the currently attached network does
not allow network connection sharing feature?

In IPv4 it is possible to do NAT to avoid this problem..

Best regards,

	Teemu
--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------