[dhcwg] Some comments regarding draft-ietf-dhc-dhcpv6-unknown-msg-01
Marcin Siodelski <msiodelski@gmail.com> Sun, 28 July 2013 22:37 UTC
Return-Path: <msiodelski@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2CB8821F9E51 for <dhcwg@ietfa.amsl.com>; Sun, 28 Jul 2013 15:37:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VswGEjSwHm41 for <dhcwg@ietfa.amsl.com>; Sun, 28 Jul 2013 15:37:42 -0700 (PDT)
Received: from mail-la0-x232.google.com (mail-la0-x232.google.com [IPv6:2a00:1450:4010:c03::232]) by ietfa.amsl.com (Postfix) with ESMTP id CCFB821F9CFF for <dhcwg@ietf.org>; Sun, 28 Jul 2013 15:37:37 -0700 (PDT)
Received: by mail-la0-f50.google.com with SMTP id ep20so3549252lab.9 for <dhcwg@ietf.org>; Sun, 28 Jul 2013 15:37:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=C1fFiwzV5kcuEvVOuxl4e7/cBj1tMWcT3LIMmwtANSU=; b=zzw5ouXYwQsl12O5J7Sd6flIbGGIPauFZMApDg+2ZHtUfmia/xI6R/7+OQ00H9UkGP nn5WifmzXFARhf7tlDe+N1sBVlI2o8uAdksXiOsnTVD1nhsy2pVerrC2DkAi4I4GwqGx HzJ90Ow4rvD/a6fhCD2vau+o02NaSWdSqWZAYLERFZKsiXd2aIfg4oWr2Uvp9azyOW3N C4VvAeMfEineCmchSG+bNO//2eRZ1j47k/HnHa5LVxSUImz/ua/d8ixVK+2S8v0kMH88 4AcJNHfPt1YSG41deRBBmhRCFp5wa/gbGXnYT40yV/0vZFx04iScO48liuxD24g8s26f PipQ==
MIME-Version: 1.0
X-Received: by 10.152.115.146 with SMTP id jo18mr1644344lab.56.1375051056726; Sun, 28 Jul 2013 15:37:36 -0700 (PDT)
Received: by 10.112.202.170 with HTTP; Sun, 28 Jul 2013 15:37:36 -0700 (PDT)
Date: Mon, 29 Jul 2013 00:37:36 +0200
Message-ID: <CAFGoqUPOVNOknZFD7JkhOSDqu63VML6iH7yyuA-je-_8W=G2bQ@mail.gmail.com>
From: Marcin Siodelski <msiodelski@gmail.com>
To: "Qi Sun (sunqi.csnet.thu@gmail.com)" <sunqi.csnet.thu@gmail.com>, "<cuiyong@tsinghua.edu.cn>" <cuiyong@tsinghua.edu.cn>, Ted Lemon <ted.lemon@nominum.com>
Content-Type: multipart/alternative; boundary="001a11c3561ac8c7f904e29a05d4"
Cc: dhcwg@ietf.org
Subject: [dhcwg] Some comments regarding draft-ietf-dhc-dhcpv6-unknown-msg-01
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 28 Jul 2013 22:37:43 -0000
I have read the draft-ietf-dhc-dhcpv6-unknown-msg-01 and I support this work move forward. Short comment on this. It would be good to distinguish between the term "intended recipient" and "recipient". From the context I understand that the intended recipient is used with regards to the target for the message being passed through relays and the recipient is a term used to describe a host which is currently holding a message. Perhaps this clarification could be placed in the glossary or somewhere in the text? Consider this: "... the message is valid for constructing a new Relay-forward message if the recipient is a relay agent, the relay agent does not identify itself as the intended recipient, and the message is not a Relay-Reply message". There is a mix-up of these two terms which may suggest that the message is sent to a wrong relay which is not an "intended recipient", while the sentence is actually meant to tell that the relay is not a target for the message being encapsulated. There is also another sentence: "A standards-complient DHCP server will never send a message to the a relay other than in response to a message from a relay, so there should never be a case where a relay receives a message for which it is the intended receipient, but is not able to recognize that it is the intended recipient for the message". I have to admit that I had to read this sentence 5 times before I caught the idea what it is about. It should be simplified, perhaps split into multiple simple sentences. And the last part could be maybe written as: "...but is not able to recognize it." Also, the first part may be wrong in a light of rfc3315, section 19.1.1 which says that server may send Reconfigure in the Relay-Reply message and since it is server initiated message, it is not sent "in response to a message from relay" as stated in the bullet. Cheers, Marcin
- [dhcwg] Some comments regarding draft-ietf-dhc-dh… Marcin Siodelski
- Re: [dhcwg] Some comments regarding draft-ietf-dh… Ted Lemon
- Re: [dhcwg] Some comments regarding draft-ietf-dh… Marcin Siodelski
- Re: [dhcwg] Some comments regarding draft-ietf-dh… Ted Lemon
- Re: [dhcwg] Some comments regarding draft-ietf-dh… Cong Liu
- Re: [dhcwg] Some comments regarding draft-ietf-dh… Tomek Mrugalski
- Re: [dhcwg] Some comments regarding draft-ietf-dh… Ted Lemon
- Re: [dhcwg] Some comments regarding draft-ietf-dh… Qi Sun
- Re: [dhcwg] Some comments regarding draft-ietf-dh… Qi Sun
- Re: [dhcwg] Some comments regarding draft-ietf-dh… Bernie Volz (volz)
- Re: [dhcwg] Some comments regarding draft-ietf-dh… Qi Sun
- Re: [dhcwg] Some comments regarding draft-ietf-dh… Qi Sun
- Re: [dhcwg] Some comments regarding draft-ietf-dh… Bernie Volz (volz)
- Re: [dhcwg] Some comments regarding draft-ietf-dh… Bernie Volz (volz)
- Re: [dhcwg] Some comments regarding draft-ietf-dh… Marcin Siodelski
- Re: [dhcwg] Some comments regarding draft-ietf-dh… Marcin Siodelski