IETF Logo Mail Archive

Re: DHCPv6 address used when M or O bit is set

Suresh Krishnan <suresh.krishnan@ericsson.com> Wed, 04 April 2012 15:51 UTC

Return-Path: <suresh.krishnan@ericsson.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A1E4B21F86B2 for <ipv6@ietfa.amsl.com>; Wed, 4 Apr 2012 08:51:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level:
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TSjjZwqB8Dkw for <ipv6@ietfa.amsl.com>; Wed, 4 Apr 2012 08:51:45 -0700 (PDT)
Received: from imr3.ericy.com (imr3.ericy.com [198.24.6.13]) by ietfa.amsl.com (Postfix) with ESMTP id BCA1121F86A7 for <ipv6@ietf.org>; Wed, 4 Apr 2012 08:51:45 -0700 (PDT)
Received: from eusaamw0706.eamcs.ericsson.se ([147.117.20.31]) by imr3.ericy.com (8.13.8/8.13.8) with ESMTP id q34FpK8R003591 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 4 Apr 2012 10:51:43 -0500
Received: from [142.133.112.66] (147.117.20.214) by smtps-am.internal.ericsson.com (147.117.20.31) with Microsoft SMTP Server (TLS) id 8.3.213.0; Wed, 4 Apr 2012 11:51:33 -0400
Message-ID: <4F7C6E05.9010603@ericsson.com>
Date: Wed, 04 Apr 2012 11:51:33 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:11.0) Gecko/20120310 Thunderbird/11.0
MIME-Version: 1.0
To: "Duncan, Jeremy" <jeremy.duncan@salientfed.com>
Subject: Re: DHCPv6 address used when M or O bit is set
References: <CAAVMDnVNUaXBwi5cU87+0PkB71kdT+e4BaLUW7Ai39hCWitUrw@mail.gmail.com> <4F7C56BE.6010507@si6networks.com>, <CAAVMDnW2ZvzOAqkCSvgSL3yRFYEW8TpGjcZ0NTct8zPH7WKkjg@mail.gmail.com> <236CD5C26786804285D413A8021D8A34043B22E7CF@VA3DIAXVS7F1.RED001.local>
In-Reply-To: <236CD5C26786804285D413A8021D8A34043B22E7CF@VA3DIAXVS7F1.RED001.local>
X-Enigmail-Version: 1.4
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: Fernando Gont <fgont@si6networks.com>, "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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>
X-List-Received-Date: Wed, 04 Apr 2012 15:51:46 -0000

Hi Jeremy,
  The DHCPv6 client on a host will use its link-local address as the
source address and ff02::1:2 as the destination address.

Cheers
Suresh

On 04/04/2012 10:50 AM, Duncan, Jeremy wrote:
> ---I am still very curious which address a client should use, if the O or
> M flag is set, to find a DHCPv6 server.
> 
> 
> The server listens on ff02::1:2 and/or ff02::1:3
> 
> 
> 
> 010100110110010101101101011100000110010101110010001000000100011001101001
> 
> Jeremy Duncan
> Senior Director, IPv6 Network Architect Salient Federal Solutions, Inc.
> (Now including SGIS & Command Information Inc.)
> 4000 Legato Road, Suite 600 Fairfax, VA 22033
> Google Voice:  540.440.1193
> jeremy.duncan@salientfed.com
> 
> ________________________________________
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------

v2.31.3 | Report a Bug | By Email | System Status