Re: [dhcwg] Review of draft-ietf-dhc-topo-conf-01

Qi Sun <sunqi.csnet.thu@gmail.com> Wed, 26 March 2014 11:47 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 C09401A0270 for <dhcwg@ietfa.amsl.com>; Wed, 26 Mar 2014 04:47:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, HTML_MESSAGE=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 ecBCzE5XSSaF for <dhcwg@ietfa.amsl.com>; Wed, 26 Mar 2014 04:47:04 -0700 (PDT)
Received: from mail-pb0-x236.google.com (mail-pb0-x236.google.com [IPv6:2607:f8b0:400e:c01::236]) by ietfa.amsl.com (Postfix) with ESMTP id A21AD1A0039 for <dhcwg@ietf.org>; Wed, 26 Mar 2014 04:47:04 -0700 (PDT)
Received: by mail-pb0-f54.google.com with SMTP id ma3so1809447pbc.41 for <dhcwg@ietf.org>; Wed, 26 Mar 2014 04:47:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-type:message-id:mime-version:subject:date:references :to:in-reply-to; bh=/2tIH5U08sqXd50BcrinYVxdC/iXjeecAwJMRgKvBAk=; b=Bya74GfxHluWJ6nH/p0ATtzMmykheGvHd9wFzawp3lltAn1a9IxJGR3YURCo3MXvXF 7e/hpvRkxCSIirXCOyktqWOZaopzK84XVPZIf1t7sUrab6SDa0+BCfffoTTDTa7IRQWp QJwPSnIbFTxUylHDBfev6gDsqhX8JDXm2L5D1FefZKibZjADqAdUibIMTHjALehk1oN1 lvpyz7TeJgcT1bfOG1vjDDxJPgf1dv5hMBvByTlAmFUtT30PK8553vc+yYKxMSsEWT9b wxId3zadDLSJMDwinU0gauURRH9+cIaEgKrLRIAOm2opPpIvEJYNujr4UdyN0nsGyCsI Y6Bw==
X-Received: by 10.66.155.133 with SMTP id vw5mr4036812pab.124.1395834423315; Wed, 26 Mar 2014 04:47:03 -0700 (PDT)
Received: from sunqideair.lan ([166.111.68.231]) by mx.google.com with ESMTPSA id qw8sm57218198pbb.27.2014.03.26.04.47.01 for <dhcwg@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 26 Mar 2014 04:47:02 -0700 (PDT)
From: Qi Sun <sunqi.csnet.thu@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_3283B6F1-4A8F-41AD-BD54-6839A2219D5D"
Message-Id: <EAE87BF9-62F5-48C7-81A2-3AA68A42EFD8@gmail.com>
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Date: Wed, 26 Mar 2014 19:46:57 +0800
References: <53319F93.7010902@viagenie.ca> <5D36713D8A4E7348A7E10DF7437A4B923AE2DE1C@nkgeml512-mbx.china.huawei.com>
To: "<dhcwg@ietf.org>" <dhcwg@ietf.org>
In-Reply-To: <5D36713D8A4E7348A7E10DF7437A4B923AE2DE1C@nkgeml512-mbx.china.huawei.com>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/IxzjOTBkcSfRZ-TgX4s2oFU5OLc
Subject: Re: [dhcwg] Review of draft-ietf-dhc-topo-conf-01
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, 26 Mar 2014 11:47:07 -0000

Dear all,

I volunteered to review the document. The document is well written and easy to review. I have some comments in addition to Simon and Sheng’s.

1. Sec 2, Terminology:
   an IP address with a scope of use wider than the local link.

[Qi] Is this the definition for “Link-identifying IP address”?

  provider edge router.  The provider router closest to the customer.

[Qi] Suggest:
Provider Edge router (PE router): ...

  customer premise equipment device.  Typically a router belonging to
  the customer that connects directly to the provider link.

[Qi] Suggest:
Customer Premise Equipment device (CPE device): ...

2. Sec 3, on Page 6
   In either case, the DHCP server is able to obtain an IP address that
  it knows is on-link for the link to which the DHCP client is
  connected: either the DHCPv4 client's routable IPv4 address, or the
  relay agent's IP address on the link to which the client is
   connected.

[Qi] The word “obtain” here is confusing: it seems the DHCP server obtains an IP address for its own configuration. Obviously not.

3. The 1st paragraph on Page 7
   DHCPv6 also has support for more finely grained link identification,
  using Lightweight DHCPv6 Relay Agents [RFC6221] (LDRA).  In this
  case, in addition to receiving an IPv6 address that is on-link for
  the link to which the client is connected, the DHCPv6 server also
  receives an Interface Identifier option from the relay agent that can
  be used to more precisely identify the client's location on the
   network.

[Qi] IMHO, the word “receive” here is also confusing, as “obtain” in the previous note.

4. Section 5
   Relay agent is a DHCP software that may be run on any IP node.
  Although it is typically run on a a router, it doesn't have to be
  one.  Relay agent can be run on a host connected to two links.  That
  case is presented in Figure 2.  There is router B that is connected
  to links D and E. At the same time there is also a host that is
  connected to the same links.  The relay agent software is running on
   that host.  That is uncommon, but legal configuration.

s/on a a router/on a router/
BTW, where is the host that connects to the same links with the router B in Figure 2?

Thanks for writing this.

Best Regards,
Qi