IETF Logo Mail Archive

Re: [Autoconf] Using DHCPv6 without link-local? Support only EUI-64interfaces?

Teco Boot <teco@inf-net.nl> Wed, 04 August 2010 07:39 UTC

Return-Path: <teco@inf-net.nl>
X-Original-To: autoconf@core3.amsl.com
Delivered-To: autoconf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DBC8E3A67A1 for <autoconf@core3.amsl.com>; Wed, 4 Aug 2010 00:39:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.478
X-Spam-Level:
X-Spam-Status: No, score=-2.478 tagged_above=-999 required=5 tests=[AWL=0.121, BAYES_00=-2.599]
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 3HfaeYexlfdK for <autoconf@core3.amsl.com>; Wed, 4 Aug 2010 00:39:13 -0700 (PDT)
Received: from mail-ey0-f172.google.com (mail-ey0-f172.google.com [209.85.215.172]) by core3.amsl.com (Postfix) with ESMTP id 0E80C3A696F for <autoconf@ietf.org>; Wed, 4 Aug 2010 00:39:11 -0700 (PDT)
Received: by eyb7 with SMTP id 7so2116672eyb.31 for <autoconf@ietf.org>; Wed, 04 Aug 2010 00:39:40 -0700 (PDT)
Received: by 10.213.30.15 with SMTP id s15mr6417925ebc.48.1280907580587; Wed, 04 Aug 2010 00:39:40 -0700 (PDT)
Received: from [192.168.2.197] (ip56530916.direct-adsl.nl [86.83.9.22]) by mx.google.com with ESMTPS id v8sm12283327eeh.8.2010.08.04.00.39.39 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 04 Aug 2010 00:39:39 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=us-ascii
From: Teco Boot <teco@inf-net.nl>
In-Reply-To: <201008040829.45561.henning.rogge@fkie.fraunhofer.de>
Date: Wed, 4 Aug 2010 09:39:38 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <C95F3A0C-14F7-4E3D-BDE0-EDAE0F0DFF0D@inf-net.nl>
References: <EBE1B970-DADA-4643-BB75-4EDEDE41F758@inf-net.nl> <AANLkTi=ZbLtCZsJZoHjMHN7fO3DDc-PVP6NjddZhjB1Y@mail.gmail.com> <29650CDE-A6A8-40C9-B626-FA8E58CA0345@inf-net.nl> <201008040829.45561.henning.rogge@fkie.fraunhofer.de>
To: Henning Rogge <henning.rogge@fkie.fraunhofer.de>
X-Mailer: Apple Mail (2.1081)
Cc: autoconf@ietf.org
Subject: Re: [Autoconf] Using DHCPv6 without link-local? Support only EUI-64interfaces?
X-BeenThere: autoconf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Ad-Hoc Network Autoconfiguration WG discussion list <autoconf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/autoconf>, <mailto:autoconf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/autoconf>
List-Post: <mailto:autoconf@ietf.org>
List-Help: <mailto:autoconf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/autoconf>, <mailto:autoconf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Aug 2010 07:39:15 -0000

Op 4 aug 2010, om 08:29 heeft Henning Rogge het volgende geschreven:
> 
>> Another problem is the discovery of the DHCP server(s). Easy to solve,
>> solutions are around (BRDP is just one of them). But in many solutions,
>> the MANET protocol is adjusted for service discovery support. (BRDP is not
>> a MANET protocol, it is an RA extension).
> Does a DHCP-reply from a relay contain the address of the DHCP-server ?

We have RFCs that document our protocols.
Is RFC3315 unclear on this?

Relay simply relays the DHCP-reply from server to client (or to downstream relay),
after stripped the Relay Message option.
When no relay adds a Relay Agent Option, server may send Server Unicast Option.
Clients may ask for the Server Unicast Option.


Teco

v2.1.27 | Report a Bug | By Email