Re: [dhcwg] WGLC for draft-ietf-dhc-dhcpv4-over-dhcpv6-03 - Respond by Dec 9, 2013

Simon Perreault <simon.perreault@viagenie.ca> Wed, 11 December 2013 16:03 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 1B1BC1AE017 for <dhcwg@ietfa.amsl.com>; Wed, 11 Dec 2013 08:03:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, 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 TAD1xq35Rvq1 for <dhcwg@ietfa.amsl.com>; Wed, 11 Dec 2013 08:03:11 -0800 (PST)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id C13E41AE013 for <dhcwg@ietf.org>; Wed, 11 Dec 2013 08:03:11 -0800 (PST)
Received: from porto.nomis80.org (unknown [IPv6:2620:0:230:c000:b146:2fa2:7507:a763]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 1433B403CA; Wed, 11 Dec 2013 11:03:06 -0500 (EST)
Message-ID: <52A88CB9.5010806@viagenie.ca>
Date: Wed, 11 Dec 2013 11:03:05 -0500
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0
MIME-Version: 1.0
To: Cong Liu <gnocuil@gmail.com>
References: <489D13FBFA9B3E41812EA89F188F018E1ADA99A8@xmb-rcd-x04.cisco.com> <52A1F8A8.3020200@viagenie.ca> <CAF+sHxH0c9miyc5piK8f9SCjd8rn34Y6p1-73Mrox5QKQDSW3Q@mail.gmail.com>
In-Reply-To: <CAF+sHxH0c9miyc5piK8f9SCjd8rn34Y6p1-73Mrox5QKQDSW3Q@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-dhcpv4-over-dhcpv6-03 - Respond by Dec 9, 2013
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: Wed, 11 Dec 2013 16:03:13 -0000

Le 2013-12-11 06:49, Cong Liu a écrit :
>     1. Section "4. Architecture Overview" ends before explaining a
>     crucial point: what does the client do with the IPv4 configuration
>     it has received? For example, when it receives an IPv4 address, does
>     it assign it to an interface? Which one? We need a general idea of
>     how this works before this section is over.
>
>     (Now that I have read the full draft, I realize that this is not
>     discussed at all. If this is out of scope, then that means this RFC
>     is not readily usable without another RFC describing how to use it
>     in one particular context. That could be fine if that's the intent,
>     but then that should be stated explicitly in this RFC.)
>
>
> When client receives an IPv4 address, it will assign it because it's
> DHCPv4. The difference is to which interface the IPv4 address is assigned.
> It's described in -00 version of this draft: "The IPv4 address allocated
> from the server MAY be assigned to a
> different interface from the IPv6 interface requesting the information."
> Maybe it should be added back to cover this issue.

I would expect much more substantial informative text to be added to the 
draft. Some things can be left out of scope for this draft, but at least 
enumerating and describing what those things are is necessary.

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