Re: [dhcwg] Last Call: <draft-ietf-dhc-option-guidelines-14.txt> (Guidelines for Creating New DHCPv6 Options) to Best Current Practice

Kevin Darcy <kcd@chrysler.com> Thu, 19 September 2013 23:01 UTC

Return-Path: <kcd@chrysler.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7A81A21F8B4E for <ietf@ietfa.amsl.com>; Thu, 19 Sep 2013 16:01:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 ApgdBFb35tim for <ietf@ietfa.amsl.com>; Thu, 19 Sep 2013 16:01:45 -0700 (PDT)
Received: from shbmap02.extra.chrysler.com (shbmap02.out.extra.chrysler.com [129.9.168.37]) by ietfa.amsl.com (Postfix) with ESMTP id 333AD21F8B07 for <ietf@ietf.org>; Thu, 19 Sep 2013 16:01:44 -0700 (PDT)
Received: from odbmap04.oddc.chrysler.com (Unknown_Domain [53.28.32.58]) by shbmap02.extra.chrysler.com (Symantec Messaging Gateway) with SMTP id FA.DD.18160.6528B325; Thu, 19 Sep 2013 19:01:42 -0400 (EDT)
X-AuditID: 8109a824-b7f9c6d0000046f0-41-523b82564cd6
Received: from shh006smtp01.shdc.chrysler.com (shh006smtp01.shdc.chrysler.com [151.171.97.83]) by odbmap04.oddc.chrysler.com (Symantec Messaging Gateway) with SMTP id 79.F9.21843.6528B325; Thu, 19 Sep 2013 19:01:42 -0400 (EDT)
Received: from [10.143.0.242] (CITMNCNU1410TPT.cg.chrysler.com [10.143.0.242]) by shh006smtp01.shdc.chrysler.com (8.13.8/8.13.8/chrysler-relay-1.4-kcd) with ESMTP id r8JN1g0U018169 for <ietf@ietf.org>; Thu, 19 Sep 2013 19:01:42 -0400
Message-ID: <523B8255.7010902@chrysler.com>
Date: Thu, 19 Sep 2013 19:01:41 -0400
From: Kevin Darcy <kcd@chrysler.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: [dhcwg] Last Call: <draft-ietf-dhc-option-guidelines-14.txt> (Guidelines for Creating New DHCPv6 Options) to Best Current Practice
References: <20130919215457.30925.98345.idtracker@ietfa.amsl.com>
In-Reply-To: <20130919215457.30925.98345.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: H4sIAAAAAAAAA11Ta0hTYRjm29nmUffV6Sznt02tlkFkmZplapQKQhJBrbLLj+w4T9twc/Oc rfRHpVEUUqugQKddp3TFKLqYzSKDMP+ogUFBF9KMDIOoDO16vrOdeda/l+d53/d5n+fjIwm6 gzSQ9ioPy1UxDpM6Trk0aXbeotL9+eaMZ/e1y0dunFUWgNWtrROKdWBb3IoK1mHfxXKLV+6I swUeNyrcfdNqGieb1XXgeXwDiCURlY0eHu4BoVqH+l9fVzeAOJKm+gB6f6dJITX9/PFWrGlq GKCvg/ZQ0xhAwfYuAhOQSkOddz+ocK2k5qFPE1/UuFZTqajz5cUYXCdQ21BL+1t1qH8Geto0 rGwAJDlTqB8N5eKdWuoEQL7bQVVIrBD5hsbF/bFUEQpce6zC/QSVj8bvcxgmqFno7lgLgWcR dSYGBS81EMcB7ZdJ+KdG/LKRc4C4Aoy8rdzJuDOy0tkaD8ekW2xcLe9guXSLy3kTCPnWx15K 7QD+ZtgNKkmFKQES9flmelq5q6LWxvC2Ms7rYHnTTHihToBhBC73OipNBpiEm7URtIrdLSz3 CK9nSoG+yRwznRjheC/vtlvsLi9f5uUc3cBIKk2JcOO3kvU0ZWU8bCXLulkupNcNdpOkCcEX WHQGx1rZmp12h0eihbkcLEzJGfGiZLgsNc9M6+SE7Kg50Lo210wb5PT/dynI2G5gJTWC5z+i Z97NOHm7NSythZuwtEZCRVk97NsjgLQEyiSToQPnoJOoaLleUGtIhCmiGdxh81ZFXBp0UPFT GJ0uI7CaIQn+wSsTZPiUoGE2/ItZvYyN1pR+1SiwkEDwA0Q/wp+bMknD7RiMD4OiRwQXiq8R xmQWk+A+8Z4wE602KmSpELLsPZeHs/QwHnmWXRjVSGg4y04M0hIYlaXYr5OoaCVDHdh+7Hm1 arAuOafoUdY1p+X3Ghd5clWuU1+0pKv9SO6A0n0quCEQLFUVl3KJn6+fDsy9Wtx2yNej3fzg 6Jvssu+nH24pf0Upnu51+qqHD3T8Omgs0X/cPNj2zmidf77/aJf33ta0+JQB5ZO1JQUThZm3 NIX+5CH//hHkianfur79ssuk5G1M5gKC45l/UrbIM8sEAAA=
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrAIsWRmVeSWpSXmKPExsUyfXVisG5Yk3WQwd8H3BbPNs5ncWD0WLLk J1MAYxSXTUpqTmZZapG+XQJXxuLDM5gKzvNVzPg1m62B8Rp3FyMnh4SAicTv7w+YIGwxiQv3 1rOB2EICTxglPl/N7GLkArLfMkrsWbeXGSTBK6AtsWv7c1YQm0VAVeL1z49gDWwCKhK7bi1n B7FFBaIk5qx7wAZRLyhxcuYTli5GDg4RIPvgY0uQmcICExkl+rbuYYVY5ijR9/gb2HxOASeJ xWsOs4LUMwtYS3zbXQQSZhaQl9j+dg7zBEb+WUimzkKomoWkagEj8ypGqfyUpNzEAgMTvfyU lGS95IyiyuKc1CK95PzcTYzAgDOVUbDcwTj3hvwhRgEORiUeXu0C6yAh1sSy4srcQ4ySHExK orzMjUAhvqT8lMqMxOKM+KLSnNTiQ4wSHMxKIrw7/lkFCfGmJFZWpRblw6SkOViUxHkNwp4E CgmkJ5akZqemFqQWwWRlODiUJHhvNgANFSxKTU+tSMvMKUFIM3FwggznARr+D6SGt7ggMbc4 Mx0if4pRUUqc9ypIQgAkkVGaB9cLSgj1////f8UoDvSKMC8jyN08wGQC1/0KaDAT0OBTC0Cu Li5JREhJNTA27b+7vPn9pYS0ux8CtGXidc7+7938cGWgqfv/A25CYnEf9Wo4hUQnx9R6XDM+ wzg/rMNixb493tZtdjdqvqXd1uww//luq76A5Zy8BV0v/sVsviRos2aCgvTlE8fklkekMs4p VmS2OSNSdPlajPcP80vRGyb0nu5XX3n8dDrzLc3V5ztNdVmUWIozEg21mIuKEwGNCr8C4wIA AA==
X-Mailman-Approved-At: Fri, 20 Sep 2013 08:09:33 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 19 Sep 2013 23:01:50 -0000

What would be the preferred way to provide a mixed list of IPv4 and IPv6 
addresses, in a DHCPv6 option? IPv4-mapped addresses?

Or, is it assumed that any service which can be reached over IPv4 or 
IPv6 by any given (dual-stack) client would use DNS FQDNs exclusively, 
rather than addresses?

By the way, the list of RFCs enumerated in Section 5.1 includes both 
4075 and 5908, but since 5908 deprecates 4075, it seems like only 1 of 
them should be in any given (normative) list, not both.

                 - Kevin

On 9/19/2013 5:54 PM, The IESG wrote:
> The IESG has received a request from the Dynamic Host Configuration WG
> (dhc) to consider the following document:
> - 'Guidelines for Creating New DHCPv6 Options'
>    <draft-ietf-dhc-option-guidelines-14.txt> as Best Current Practice
>
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2013-10-03. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
>
> Abstract
>
>
>     This document provides guidance to prospective DHCPv6 Option
>     developers to help them creating option formats that are easily
>     adoptable by existing DHCPv6 software.  This document updates
>     RFC3315.
>
>
>
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-dhc-option-guidelines/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-dhc-option-guidelines/ballot/
>
>
> No IPR declarations have been submitted directly on this I-D.
>
>
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg
>
>
>