Re: DHCPv6 - does it have gateway option

Ralph Droms <rdroms@cisco.com> Tue, 18 September 2007 14:36 UTC

Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IXeBi-0006R4-ML; Tue, 18 Sep 2007 10:36:30 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IXeBh-0006PU-Be for ipv6@ietf.org; Tue, 18 Sep 2007 10:36:29 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IXeBg-0004Vm-VW for ipv6@ietf.org; Tue, 18 Sep 2007 10:36:29 -0400
Received: from rtp-dkim-2.cisco.com ([64.102.121.159]) by rtp-iport-2.cisco.com with ESMTP; 18 Sep 2007 10:36:28 -0400
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12]) by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l8IEaSGc023329; Tue, 18 Sep 2007 10:36:28 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l8IEaNci023366; Tue, 18 Sep 2007 14:36:23 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 18 Sep 2007 10:36:10 -0400
Received: from [192.168.21.12] ([10.86.240.114]) by xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 18 Sep 2007 10:36:09 -0400
In-Reply-To: <7ECEF9368E169544B43882BC98EB5D92032DA9FD@SVR-ALH-EXC-02.mgc.mentorg.com>
References: <7ECEF9368E169544B43882BC98EB5D92032DA9FD@SVR-ALH-EXC-02.mgc.mentorg.com>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Message-Id: <A66D1C83-9A46-4DF9-9FC9-24B69824C078@cisco.com>
Content-Transfer-Encoding: 7bit
From: Ralph Droms <rdroms@cisco.com>
Date: Tue, 18 Sep 2007 10:35:59 -0400
To: "Leino, Tammy" <tammy_leino@mentor.com>
X-Mailer: Apple Mail (2.752.2)
X-OriginalArrivalTime: 18 Sep 2007 14:36:09.0913 (UTC) FILETIME=[41332290:01C7FA01]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1965; t=1190126188; x=1190990188; c=relaxed/simple; s=rtpdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=rdroms@cisco.com; z=From:=20Ralph=20Droms=20<rdroms@cisco.com> |Subject:=20Re=3A=20DHCPv6=20-=20does=20it=20have=20gateway=20option |Sender:=20 |To:=20=22Leino,=20Tammy=22=20<tammy_leino@mentor.com>; bh=/JmMqFI2M3c1UO99nYdFSMiNwd6nPRjPgZBJx277FAU=; b=O0AqpkakXEVcI9WHgfkQjtWVSW5z0INklkGxlSpFr7jQG2bz6EocD30aBLYl+YG97W0Mbk1e fElujZIOQpJ3m+tEKCCr6/uX074ZKWnGc5aLVGObZSX5oLkSv8EMndpf;
Authentication-Results: rtp-dkim-2; header.From=rdroms@cisco.com; dkim=pass ( sig from cisco.com/rtpdkim2001 verified; );
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
Cc: Iljitsch van Beijnum <iljitsch@muada.com>, ipv6@ietf.org, Bill Manning <bmanning@ISI.EDU>
Subject: Re: DHCPv6 - does it have gateway option
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Well...I have to respectfully disagree about the reasoning behind the  
decision.  There is no IPv6 default router option in DHCPv6 because  
that information is given to hosts in RAs.  The assumption is that,  
if there is a router willing to act as a default router on a link,  
it's presence will be announced through RAs.  A host that receives no  
RAs can infer that there is no default router (which is a deployment  
scenario the dhc WG certainly understands and can imagine  
encountering in practice); if the host receives configuration from  
DHCPv6 in this scenario, there is no need for a default router option.

- Ralph

On Sep 18, 2007, at Sep 18, 2007,9:18 AM, Leino, Tammy wrote:

> I had this same discussion with the DHCP working group a few weeks  
> back.
> The end result was that there should always be an IPv6 router on-link
> configured to transmit RAs.  They could not fathom why an IPv6 network
> would not have an IPv6 router on-link.  That is why there is
> intentionally no DHCPv6 option for distributing the gateway.
>
> Best Regards,
> Tammy
>
>
>
>
> -----Original Message-----
> From: Iljitsch van Beijnum [mailto:iljitsch@muada.com]
> Sent: Tuesday, September 18, 2007 9:11 AM
> To: Bill Manning
> Cc: ipv6@ietf.org
> Subject: Re: DHCPv6 - does it have gateway option
>
>
> On 18-sep-2007, at 8:02, Bill Manning wrote:
>
>> 	presume the absense of a router.
>
> It almost seems like the DHCPv6 designers did...
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------

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