[dhcwg] Fwd: I-D Action: draft-ietf-dhc-dhcpv6-unknown-msg-04.txt

Qi Sun <sunqi.csnet.thu@gmail.com> Mon, 16 December 2013 03:30 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 []) by ietfa.amsl.com (Postfix) with ESMTP id AB6B71AE247 for <dhcwg@ietfa.amsl.com>; Sun, 15 Dec 2013 19:30:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
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 ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id 1JgMOIv-mlt1 for <dhcwg@ietfa.amsl.com>; Sun, 15 Dec 2013 19:30:06 -0800 (PST)
Received: from mail-pb0-x233.google.com (mail-pb0-x233.google.com [IPv6:2607:f8b0:400e:c01::233]) by ietfa.amsl.com (Postfix) with ESMTP id 89CBF1AE23B for <dhcwg@ietf.org>; Sun, 15 Dec 2013 19:30:06 -0800 (PST)
Received: by mail-pb0-f51.google.com with SMTP id up15so4919161pbc.10 for <dhcwg@ietf.org>; Sun, 15 Dec 2013 19:30:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-type:subject:date:references:to:message-id :mime-version; bh=8pdO6/aBtxBaEMLN45gz7c44VIjf6CUSEhn8n3NJW/g=; b=xUbvVKNhVCdhn400hzGRVYvVaRm+S3q1ns0QhbaPZWAJaQ4G2MwIsWbudXh72eT2jR sB4YfY7hp90yGWM/Olxv/ak+fo+n7PpVqqhIzFfb8VWwdC45XFAp+0VZeHyGXJjdVflG pse8YC/zQk9v/zmjxuIBrk1lSahVhmyvQr/k1/4SL/VL5yn4xMXzi5VIz4ji5mEgvt+M hrzzziL68cYXS2BT7sl6HClm96uTFBfLmI7rTeQz4G6SrAA/5/q72V26Vr1y+E+3OA53 jcsTrjIEodUSPZLwsqvyWFoSBCR32PbfSlhTbBy3npz98cHvl6lun9gmrWQE1KXXPakP fVZg==
X-Received: by with SMTP id ap1mr17489556pbc.117.1387164606115; Sun, 15 Dec 2013 19:30:06 -0800 (PST)
Received: from [] ([]) by mx.google.com with ESMTPSA id at4sm22450302pbc.30.2013. for <dhcwg@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 15 Dec 2013 19:30:05 -0800 (PST)
From: Qi Sun <sunqi.csnet.thu@gmail.com>
Content-Type: multipart/alternative; boundary=Apple-Mail-18-835507709
Date: Mon, 16 Dec 2013 11:30:00 +0800
References: <20131216032537.25601.52596.idtracker@ietfa.amsl.com>
To: "dhcwg@ietf.org WG" <dhcwg@ietf.org>
Message-Id: <E60FC26B-8075-46AB-B61A-EBB37FE9A509@gmail.com>
Mime-Version: 1.0 (Apple Message framework v1085)
X-Mailer: Apple Mail (2.1085)
Subject: [dhcwg] Fwd: I-D Action: draft-ietf-dhc-dhcpv6-unknown-msg-04.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: Mon, 16 Dec 2013 03:30:10 -0000

Dear all,

We have updated the draft-ietf-dhc-dhcpv6-unknown-msg. Major changes are: 

1) Update the Sec 3 (Problem Statement)
2) Rename the Sec 4.1 to "A Valid Message for Constructing a New Relay-forward Message" to avoid the confusion about what 'valid' is for.
3) Reword the definition to the 'valid' message and the subsequent paragraph about unknown messages targeting at the relay agent.
4) Choose "toward" among "toward/towards/to" when describing the relaying direction.
5) Use the pre-RFC5378 boilerplate.
6) Correct some nits.

Thanks a lot for your inputs during the WGLC. 

Best Regards,

Begin forwarded message:

> From: internet-drafts@ietf.org
> Date: 2013年12月16日 上午11时25分37秒格林尼治标准时间+0800
> To: i-d-announce@ietf.org
> Cc: dhcwg@ietf.org
> Subject: [dhcwg] I-D Action: draft-ietf-dhc-dhcpv6-unknown-msg-04.txt
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Dynamic Host Configuration Working Group of the IETF.
> 	Title           : Handling Unknown DHCPv6 Messages
> 	Author(s)       : Yong Cui
>                          Qi Sun
>                          Ted Lemon
> 	Filename        : draft-ietf-dhc-dhcpv6-unknown-msg-04.txt
> 	Pages           : 6
> 	Date            : 2013-12-15
> Abstract:
>   DHCPv6 is not specific about handling messages with unknown types.
>   This memo describes the problems and defines how a DHCPv6 server,
>   client or relay agent should behave when receiving unknown DHCPv6
>   messages.  This document updates RFC3315.
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-dhc-dhcpv6-unknown-msg
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-ietf-dhc-dhcpv6-unknown-msg-04
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=draft-ietf-dhc-dhcpv6-unknown-msg-04
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg