Re: [dhcwg] Some comments regarding draft-ietf-dhc-dhcpv6-unknown-msg-01
Qi Sun <sunqi.csnet.thu@gmail.com> Mon, 29 July 2013 09:06 UTC
Return-Path: <sunqi.csnet.thu@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 55FCA21F9D68 for <dhcwg@ietfa.amsl.com>; Mon, 29 Jul 2013 02:06:27 -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=[AWL=-0.000, 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 5LR0tduiJe0j for <dhcwg@ietfa.amsl.com>; Mon, 29 Jul 2013 02:06:24 -0700 (PDT)
Received: from mail-pd0-x236.google.com (mail-pd0-x236.google.com [IPv6:2607:f8b0:400e:c02::236]) by ietfa.amsl.com (Postfix) with ESMTP id F209021F9FEA for <dhcwg@ietf.org>; Mon, 29 Jul 2013 02:06:12 -0700 (PDT)
Received: by mail-pd0-f182.google.com with SMTP id r11so942552pdi.13 for <dhcwg@ietf.org>; Mon, 29 Jul 2013 02:06:12 -0700 (PDT)
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 :message-id:references:to:x-mailer; bh=WKRLyooiCK6wA7zK0Lz32QM0cRpnr2OvdEIY/+L0g7A=; b=HKoGr7q4rvaygFltrYl3kn+lVu5OzJf/UhEFJe/1thVMcT7wjrSCCbVa2FBSWYnLe+ oxb0K5O4NmyFfDziDrZxu7Z5XfvNcr5ZPz0t+oeb123CedvNCBD5MVXplOCoJpjMDrzs dX41vxzQ5s8dFMK316iM8o82wMmLVS7FeLIiYvIxeGj+Ll3t8Uz0cx6WSMvkMNEYBe/M LO9B2M6LYIGVQtdmztkFR7d9gyQfBbnOx3/VvL0hh2m8FewgcpizIQshe7Mqih2tT0DU L19h0UHUUD+pFaNjG4eSx6PrBLqvhNHjgBLLZAKR+CZJMnuUo2JG7ncLAHAvcscYKm7B o36w==
X-Received: by 10.66.136.237 with SMTP id qd13mr68553374pab.74.1375088772461; Mon, 29 Jul 2013 02:06:12 -0700 (PDT)
Received: from ?IPv6:2001:df8::16:9284:dff:fef3:d346? ([2001:df8:0:16:9284:dff:fef3:d346]) by mx.google.com with ESMTPSA id w8sm19652522paj.4.2013.07.29.02.06.09 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 29 Jul 2013 02:06:11 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary="Apple-Mail-111--502907211"
From: Qi Sun <sunqi.csnet.thu@gmail.com>
In-Reply-To: <51F61E9A.4040105@gmail.com>
Date: Mon, 29 Jul 2013 11:06:07 +0200
Message-Id: <83CD75ED-5232-418C-A5F6-0A3F62684839@gmail.com>
References: <CAFGoqUPOVNOknZFD7JkhOSDqu63VML6iH7yyuA-je-_8W=G2bQ@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307752334C7@mbx-01.win.nominum.com> <CAFGoqUMLgyVFnhbF7LYhaiFm8HZt3H4T=Oj_014g_U0LcZBD0A@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B63077523396E@mbx-01.win.nominum.com> <51F61E9A.4040105@gmail.com>
To: Tomek Mrugalski <tomasz.mrugalski@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: "<dhcwg@ietf.org>" <dhcwg@ietf.org>, "<cuiyong@tsinghua.edu.cn>" <cuiyong@tsinghua.edu.cn>, Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: [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: Mon, 29 Jul 2013 09:06:28 -0000
Tomek , > Note that the draft says nothing about message types. Here's part of the > text that needs to be updated in my opinion: "A standards-compliant DHCP > server will never send a message to the a relay other than in response > to a message from a relay,...". What do you think of the text: NEW: "A standards-complient DHCP server will never send a message to a relay for which the relay is the the intended recipient, but is not able to recognize it." Would it resolve the confusion? Thanks, Qi On 2013-7-29, at 上午9:49, Tomek Mrugalski wrote: > On 13-07-29 09:33, Ted Lemon wrote: >> On Jul 29, 2013, at 9:05 AM, Marcin Siodelski <msiodelski@gmail.com> wrote: >>> According to RFC3315, server may use Relay-Reply message if it can't send Reconfigure directly to the client: >> >> Right. That's a relay-reply message, not a reconfigure message. > Yes, but the message type is irrelevant. Marcin's point was that > the draft says that that server will never send a message that is not a > response to a message from a relay, which is not true. > > Note that the draft says nothing about message types. Here's part of the > text that needs to be updated in my opinion: "A standards-compliant DHCP > server will never send a message to the a relay other than in response > to a message from a relay,...". > > _______________________________________________ > dhcwg mailing list > dhcwg@ietf.org > https://www.ietf.org/mailman/listinfo/dhcwg
- [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