Re: [dhcwg] I-D Action: draft-ietf-dhc-conn-status-00.txt

Simon Perreault <simon.perreault@viagenie.ca> Tue, 04 February 2014 16:37 UTC

Return-Path: <simon.perreault@viagenie.ca>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E0AFA1A01A7 for <dhcwg@ietfa.amsl.com>; Tue, 4 Feb 2014 08:37:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.436
X-Spam-Level:
X-Spam-Status: No, score=-2.436 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4f8H9ELNxHkq for <dhcwg@ietfa.amsl.com>; Tue, 4 Feb 2014 08:37:25 -0800 (PST)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id 2C6F21A0211 for <dhcwg@ietf.org>; Tue, 4 Feb 2014 08:37:15 -0800 (PST)
Received: from porto.nomis80.org (ringo.viagenie.ca [206.123.31.67]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 938124037A; Tue, 4 Feb 2014 11:37:14 -0500 (EST)
Message-ID: <52F1173A.8070903@viagenie.ca>
Date: Tue, 04 Feb 2014 11:37:14 -0500
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Ted Lemon <ted.lemon@nominum.com>
References: <20140204093611.4914.51694.idtracker@ietfa.amsl.com> <52F0F3C2.20807@viagenie.ca> <4B094E1A-431F-4F2B-9004-37D6D12BE8F8@nominum.com> <52F0F8F4.4060905@viagenie.ca> <EEEC392B-7B7B-4AAE-BE24-AEC944DFABFA@nominum.com> <52F0FFE6.3050802@viagenie.ca> <C16244FB-DC1A-4E2A-8E51-64DB20F5C341@nominum.com>
In-Reply-To: <C16244FB-DC1A-4E2A-8E51-64DB20F5C341@nominum.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
Cc: "dhcwg@ietf.org WG" <dhcwg@ietf.org>
Subject: Re: [dhcwg] I-D Action: draft-ietf-dhc-conn-status-00.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Feb 2014 16:37:28 -0000

Le 2014-02-04 11:04, Ted Lemon a écrit :
> How can it work with SLAAC?

I was thinking:
The relay snoops the addresses as described in section 7. Then it sends
a reconfigure request.

But then I wondered: where does the DHCPv6 server send its reconfigure
if the client is not already "known" by the server?

And then I further wondered: what use is this draft if a client is
IPv4-only? The DHCPv6 server would not be able to talk to the client.

Me confused.

(I really should let the authors speak for themselves.)

Simon
-- 
DTN made easy, lean, and smart --> http://postellation.viagenie.ca
NAT64/DNS64 open-source        --> http://ecdysis.viagenie.ca
STUN/TURN server               --> http://numb.viagenie.ca