IETF Logo Mail Archive

Re: [dhcwg] Fwd: I-D Action: draft-ietf-dhc-dhcpv4-over-dhcpv6-05.txt

Qi Sun <sunqi.csnet.thu@gmail.com> Sun, 16 February 2014 14:45 UTC

Return-Path: <sunqi.csnet.thu@gmail.com>
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 6DC0D1A0225 for <dhcwg@ietfa.amsl.com>; Sun, 16 Feb 2014 06:45:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=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 74UxjkKCHmcx for <dhcwg@ietfa.amsl.com>; Sun, 16 Feb 2014 06:45:02 -0800 (PST)
Received: from mail-pd0-x22b.google.com (mail-pd0-x22b.google.com [IPv6:2607:f8b0:400e:c02::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 63F8E1A01BB for <dhcwg@ietf.org>; Sun, 16 Feb 2014 06:45:02 -0800 (PST)
Received: by mail-pd0-f171.google.com with SMTP id g10so13825504pdj.30 for <dhcwg@ietf.org>; Sun, 16 Feb 2014 06:45:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=arEeIi9+8QLdSS8xsA9R0mIOjepoXH8p6t1uDvP612E=; b=HAd6iHcj67XmFR7qf6cm3Hg7C6THc3PO+ZLtXKcen3tN9WSAOfvuGtvBCyP51KJDmA I2j9D8p6Mwqqp1ka4Djwewo8KWUp3TgncFkraXgAiH1VxV3YOiEjOlELT2Iqorob6jPw uDTv2nuQmN13U7Xz5chJvqAo/cxv8dVzJJC+5EGbLYgzdWL3VBEjrt2pEn9MXPgM3LD4 sjH85kzvcWUWbRIcdtoH6CJTFsd08F5mEVn5Pvf+YMBjNOZ6JEOwx2fuW7S20b2MyJ0v 5yz7uJ+5NeFS+eUJjGd0d6+7VaSc4kE8ExY9e/4RGTpz7vdtdyfmu67BhmTM7tTCBoFK aJ0w==
X-Received: by 10.68.213.41 with SMTP id np9mr20906754pbc.90.1392561900302; Sun, 16 Feb 2014 06:45:00 -0800 (PST)
Received: from [192.168.0.104] ([60.215.217.244]) by mx.google.com with ESMTPSA id e6sm36571729pbg.4.2014.02.16.06.44.56 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 16 Feb 2014 06:44:59 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset="utf-8"
From: Qi Sun <sunqi.csnet.thu@gmail.com>
In-Reply-To: <CAL10_Brty3i8rTxhwfu2yZF_RtRCm=MGBmxwxn7WG5BCyMoWSQ@mail.gmail.com>
Date: Sun, 16 Feb 2014 22:44:48 +0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <004A4A72-F1A5-480D-9AF7-680C2CC3C14E@gmail.com>
References: <20140214211006.9831.91801.idtracker@ietfa.amsl.com> <CAFGoqUMGc0ojyGp3pMYGhuP+1K-uDJsX+=evXTz9AajcAT1Bhg@mail.gmail.com> <CAL10_Brty3i8rTxhwfu2yZF_RtRCm=MGBmxwxn7WG5BCyMoWSQ@mail.gmail.com>
To: Andre Kostur <akostur@incognito.com>
X-Mailer: Apple Mail (2.1085)
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/zkVODDGU9_kY9MkNUy9WFVgua4A
Cc: "<dhcwg@ietf.org>" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Fwd: I-D Action: draft-ietf-dhc-dhcpv4-over-dhcpv6-05.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: Sun, 16 Feb 2014 14:45:05 -0000

Hi Andre,

Thanks for review. Please see inline.

On 2014-2-15, at 上午11:08, Andre Kostur wrote:

> Perhaps a quick question on section 6.2.
> 
> I'm curious as to why there's a special case of "if there are no
> addresses, use All_DHCP_Relay_Agents_and_Servers"?  If an
> administrator wanted the client to send to that address, they could
> also just supply that one address in the option.  And then clients
> wouldn't have to have a special case handling of receiving an empty
> option.

[Qi] This is intended to be compatible with the DHCPv6 architecture, where the client sends packets to the multicast address by default. So if there is no address in the 4o6 Server Address option, the 4o6 DHCP client just works like a DHCPv6 client. 

> 
> Also the section says "This list may include either multicast or
> unicast addresses."  Is that intended to say that it cannot contain a
> mix of both?

[Qi] There should be no such limit. The client just sends packets to the address(es) listed int the 4o6 Server Address option. An administrator can configure this option according to his needs. 
Will improve the wording.

Thanks,
QI

> 
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg

v2.23.0 | Report a Bug | By Email