Gen-ART LC review of draft-ietf-dhc-dhcpv6-stateful-issues-11

"Roni Even" <ron.even.tlv@gmail.com> Sat, 28 February 2015 11:53 UTC

Return-Path: <ron.even.tlv@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7419E1A0406; Sat, 28 Feb 2015 03:53:42 -0800 (PST)
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 HXkJG1H1Q8sf; Sat, 28 Feb 2015 03:53:40 -0800 (PST)
Received: from mail-wi0-x22a.google.com (mail-wi0-x22a.google.com [IPv6:2a00:1450:400c:c05::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3B3611A00F5; Sat, 28 Feb 2015 03:53:40 -0800 (PST)
Received: by widex7 with SMTP id ex7so5472865wid.4; Sat, 28 Feb 2015 03:53:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:subject:date:message-id:mime-version:content-type :thread-index:content-language; bh=bSsohceNyNh6mkWN15leZRGa1QLelHhQBDKFuG0kzh8=; b=PhZ4cEPmxOr6YJlJbdwAson+G4pB4JmEbG1yijbTc1nGVfhE7O0J059QDMkFmtkLvd V1QSU22WN6n/9YOkpmA3Uk+rAnh027yf8pgT1zzv/I3tYTt0HfFK0AsexJ2FfMCNw/JQ teoVSr15Xq5zui3NI0OMZxAg3wa6eo1s96DfRhnyaVYezbpC0as9Peo09uwo67eHLfU1 LzcDofPBsJ6qCkSRvgkUpMI5O9EouOYhJ3O7LXsVBoBQiDFaCeRrb/upwmTgHLW7AWSw NodjX0j0j07oLj0PZE471qsMjZYxsdPu8IEKKEOVWUn1Fnq3rX1tzlf4Wc2FgQa5umKz CbDw==
X-Received: by 10.180.108.177 with SMTP id hl17mr15747802wib.35.1425124418961; Sat, 28 Feb 2015 03:53:38 -0800 (PST)
Received: from RoniE (bzq-79-177-192-183.red.bezeqint.net. [79.177.192.183]) by mx.google.com with ESMTPSA id hi6sm9891020wjc.34.2015.02.28.03.53.36 (version=TLSv1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Sat, 28 Feb 2015 03:53:37 -0800 (PST)
From: Roni Even <ron.even.tlv@gmail.com>
To: draft-ietf-dhc-dhcpv6-stateful-issues.all@tools.ietf.org
Subject: Gen-ART LC review of draft-ietf-dhc-dhcpv6-stateful-issues-11
Date: Sat, 28 Feb 2015 13:53:29 +0200
Message-ID: <01ba01d0534d$2eeb3ca0$8cc1b5e0$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_01BB_01D0535D.F274CFF0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AdBTTSsKDoBUtzL4TvC595jYUNTaKQ==
Content-Language: en-us
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/Ds-V9_PV9dab0-g_Abt2ZwAHYCA>
Cc: gen-art@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 28 Feb 2015 11:53:42 -0000

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments you
may receive.

Document:  draft-ietf-dhc-dhcpv6-stateful-issues-11

Reviewer: Roni Even

Review Date:2015-2-28

IETF LC End Date: 2015-3-4

IESG Telechat date: 

 

Summary: This draft is ready for publication as an Standard Track  RFC.

 

 

Major issues:

 

Minor issues:

 

 

Nits/editorial comments:

1.	The document defines the terms "Identity association (IA)" and "IA
option types" different from RFC3315 yet in the document sometimes this
terms are as specified in RFC3315 including the IA_TA option. An example is
for section with text changes.
2.	For clarification: Is this document going to be obsolete by
draft-dhcwg-dhc-rfc3315bis, there are some sections that include changes to
RFC3315 and RFC3633 and my reading is that this changes will be incorporated
un the rfc3315bis draft. I am not sure about sections that provides
clarifications and do not propose text changes.