IETF Logo Mail Archive

Re: [dhcwg] Updating RFC 3633 with draft-ietf-dhc-dhcpv6-prefix-length-hint-issue

Suresh Krishnan <suresh.krishnan@ericsson.com> Sat, 25 February 2017 04:28 UTC

Return-Path: <suresh.krishnan@ericsson.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 66C451299B9 for <dhcwg@ietfa.amsl.com>; Fri, 24 Feb 2017 20:28:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 aK4OsAuuxXvv for <dhcwg@ietfa.amsl.com>; Fri, 24 Feb 2017 20:28:35 -0800 (PST)
Received: from usplmg20.ericsson.net (usplmg20.ericsson.net [198.24.6.45]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D848B129460 for <dhcwg@ietf.org>; Fri, 24 Feb 2017 20:28:34 -0800 (PST)
X-AuditID: c618062d-d5fff700000009d8-fa-58b1184e27fe
Received: from EUSAAHC002.ericsson.se (Unknown_Domain [147.117.188.78]) by (Symantec Mail Security) with SMTP id E7.36.02520.E4811B85; Sat, 25 Feb 2017 06:38:25 +0100 (CET)
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC002.ericsson.se ([147.117.188.78]) with mapi id 14.03.0319.002; Fri, 24 Feb 2017 23:28:30 -0500
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
To: Tomek Mrugalski <tomasz.mrugalski@gmail.com>
Thread-Topic: [dhcwg] Updating RFC 3633 with draft-ietf-dhc-dhcpv6-prefix-length-hint-issue
Thread-Index: AQHSjTNw3QKW4kxv/0usH25z4fmyLKF5eKYA
Date: Sat, 25 Feb 2017 04:28:29 +0000
Message-ID: <19A0AE7B-FBBA-44D3-A219-D7F43908B972@ericsson.com>
References: <CAFx+hEMNhzShhDWxSX+JLq+KPk4HyMzdGMEWYWG6i1o+LFMb3w@mail.gmail.com> <DE41B94D-78C3-4BDE-8BA3-555D67A59E49@ericsson.com> <cf4e6973-15ec-dee5-1772-f757d2b954f0@gmail.com>
In-Reply-To: <cf4e6973-15ec-dee5-1772-f757d2b954f0@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [147.117.188.11]
Content-Type: multipart/signed; boundary="Apple-Mail=_D548DC9E-E5EE-46C0-9496-D1E626C11AA5"; protocol="application/pkcs7-signature"; micalg="sha1"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrIIsWRmVeSWpSXmKPExsUyuXSPn26gxMYIg8ufrCzudrQwWuy/toDJ gclj56y77B5LlvxkCmCK4rJJSc3JLEst0rdL4Mr4t3Qnc0G7TcXdZd2MDYxfzLsYOTkkBEwk WrvmsnQxcnEICaxnlPje18UM4SxnlGj6NI0NpIoNqGrDzs9MILaIgIHEuTvPwWxmAVWJpZc3 MILYwgIxElf/nGGHqImVaLmzBijOAWQbSRyfqg4SZgEq37X5OiuIzStgL3FrYTcjxK6djBJ3 J+8F28UpYCsxY8IWsCJGATGJ76fWQO0Sl7j1ZD4TxNUiEg8vnmaDsEUlXj7+xwphK0l8/D2f HWQos8AURoltJ5YyQmwTlDg58wnLBEaRWUhmzUJWNwtJHUSRtsSyha+ZZwE9wSygIzF5ISNE 2FTi9dGPULa1xIxfB9kgbEWJKd0P2Rcwcqxi5CgtLsjJTTcy2MQIjKxjEmy6OxjvT/c8xCjA wajEw7uhaUOEEGtiWXFl7iFGFaDWRxtWX2CUYsnLz0tVEuHtZNgYIcSbklhZlVqUH19UmpNa fIhRmoNFSZw3bvX9cCGB9MSS1OzU1ILUIpgsEwenVANjQlg2j3SzVoWbtd4ZjY76W1JL2v7U eEz9o/Tur+u5xBlistpl/oJmd14Xvfvo5nGC4fq3aQHiJvzHd278xHf+qcJJVmmV+/qrz7q0 bb+t+lvpd4rhNpk5ibc8GcwDRFvYz6ctmtVdYXd4elSv/fWv77Nm5Hg/t4iZpnt157LZ3zZe 5nHOf1msxFKckWioxVxUnAgAnllr+bQCAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/WPxzNMXgUQmgo0rHO5kZFoUJkD0>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Updating RFC 3633 with draft-ietf-dhc-dhcpv6-prefix-length-hint-issue
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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: Sat, 25 Feb 2017 04:28:36 -0000

Hi Tomek,

> On Feb 22, 2017, at 12:45 PM, Tomek Mrugalski <tomasz.mrugalski@gmail.com> wrote:
> 
> W dniu 21.02.2017 o 05:06, Suresh Krishnan pisze:
>>> On Feb 17, 2017, at 12:32 AM, tianxiang li <peter416733@gmail.com> wrote:
>>> 
>>> Hi all,
>>> 
>>> The IESG review of draft-ietf-dhc-dhcpv6-prefix-length-hint-issue has ended, several reviewers suggested this document should update RFC 3633, as someone reading RFC3633 would need a pointer to this document. Hope to receive the comments from the WG regarding this issue. 
>>> 
>>> I personally have no objections to adding the Updates: RFC3633 tag to the document. It would be great if other WG participants can chime in one way or another.
> With my co-chair hat off, I don't have any specific preference here. On
> one hand, if we update 3633, we will be enforcing everyone to follow the
> recommendation made in prefix-length-hint-issue. The obvious benefit is
> that prefix-length-hint-issue will get more exposure, which is a good
> thing. On the other hand, the 3315bis work hopefully will be published
> later this year and it will obsolete 3633. Assuming the bis work gets
> published relatively soon, the window of opportunity when the 3633
> update will be applicable is several months. As Bernie pointed out,
> 3315bis references prefix-length-hint-issue.
> 
> If it was completely up to me, I would go with update 3633, because that
> would give this draft immediate exposure to more readers. Also, if
> 3315bis publication is delayed for whatever reason, updating seems like
> a better choice. But I wouldn't complain if we decide to go the "don't
> update" route.

Yes. This was my position as well. I will let Bernie and you make the call as chairs and let me know.

Thanks
Suresh

v2.23.0 | Report a Bug | By Email