[dhcwg] Fwd: [DNSOP] [rfc-editor@rfc-editor.org: BCP 187, RFC 7227 on Guidelines for Creating New DHCPv6 Options]

Ted Lemon <ted.lemon@nominum.com> Sat, 10 May 2014 14:14 UTC

Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 306F61A0255 for <dhcwg@ietfa.amsl.com>; Sat, 10 May 2014 07:14:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.55
X-Spam-Level:
X-Spam-Status: No, score=-2.55 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.651] 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 3qxUNte-MRdP for <dhcwg@ietfa.amsl.com>; Sat, 10 May 2014 07:14:18 -0700 (PDT)
Received: from shell-too.nominum.com (shell-too.nominum.com [64.89.228.229]) by ietfa.amsl.com (Postfix) with ESMTP id EEE351A024A for <dhcwg@ietf.org>; Sat, 10 May 2014 07:14:17 -0700 (PDT)
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id C2D1A1B81C7 for <dhcwg@ietf.org>; Sat, 10 May 2014 07:14:12 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id A46D8190043 for <dhcwg@ietf.org>; Sat, 10 May 2014 07:14:12 -0700 (PDT)
Received: from [10.0.10.40] (192.168.1.10) by CAS-01.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.158.1; Sat, 10 May 2014 07:14:05 -0700
From: Ted Lemon <ted.lemon@nominum.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_CA7438CA-D64A-40CB-9B5B-A49E6E4C7202"
Date: Sat, 10 May 2014 10:14:03 -0400
References: <20140510061841.GA23600@laperouse.bortzmeyer.org>
To: dhcwg <dhcwg@ietf.org>
Message-ID: <76AD81FE-11BE-4583-BCE3-D439886AA729@nominum.com>
MIME-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
X-Mailer: Apple Mail (2.1874)
X-Originating-IP: [192.168.1.10]
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/m5D1YWDf0ENbNRgWnTENYJ3rTZg
Subject: [dhcwg] Fwd: [DNSOP] [rfc-editor@rfc-editor.org: BCP 187, RFC 7227 on Guidelines for Creating New DHCPv6 Options]
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: Sat, 10 May 2014 14:14:20 -0000

For those who don't read dnsop, here is a nice thumbs-up for the work on the DHCP Options draft!

Begin forwarded message:

> From: Stephane Bortzmeyer <bortzmeyer@nic.fr>;
> Subject: [DNSOP] [rfc-editor@rfc-editor.org: BCP 187, RFC 7227 on Guidelines for Creating New DHCPv6 Options]
> Date: May 10, 2014 at 2:18:41 AM EDT
> To: <dnsop@ietf.org>;
> 
> The issues described in this RFC seem very close from the issues of
> new DNS RR types (reusing elements of previous formats, to avoid
> creating a parser from scratch, thinking in advance of implementation
> considerations, to increase the chances of atcual deployment,
> considering the end systems - provisioning and consumption - not only
> what goes on the wire, etc).
> 
> A very good reading, IMHO.
> 
> 
> Resent-From: Stephane Bortzmeyer <bortzmeyer@nic.fr>;
> From: <rfc-editor@rfc-editor.org>;
> Subject: BCP 187, RFC 7227 on Guidelines for Creating New DHCPv6 Options
> Date: May 8, 2014 at 8:08:09 PM EDT
> Resent-To: <stephane@laperouse.bortzmeyer.org>;
> To: <ietf-announce@ietf.org>;, <rfc-dist@rfc-editor.org>;
> Cc: <drafts-update-ref@iana.org>;, <dhcwg@ietf.org>;, <rfc-editor@rfc-editor.org>;
> Reply-To: <ietf@ietf.org>;
> 
> 
> A new Request for Comments is now available in online RFC libraries.
> 
>        BCP 187        
>        RFC 7227
> 
>        Title:      Guidelines for Creating New DHCPv6 
>                    Options 
>        Author:     D. Hankins, T. Mrugalski,
>                    M. Siodelski, S. Jiang,
>                    S. Krishnan
>        Status:     Best Current Practice
>        Stream:     IETF
>        Date:       May 2014
>        Mailbox:    dhankins@google.com, 
>                    tomasz.mrugalski@gmail.com, 
>                    msiodelski@gmail.com,
>                    jiangsheng@huawei.com, 
>                    suresh.krishnan@ericsson.com
>        Pages:      35
>        Characters: 83694
>        Updates:    RFC 3315
>        See Also:   BCP 187
> 
>        I-D Tag:    draft-ietf-dhc-option-guidelines-17.txt
> 
>        URL:        http://www.rfc-editor.org/rfc/rfc7227.txt
> 
> This document provides guidance to prospective DHCPv6 option
> developers to help them create option formats that are easily
> adoptable by existing DHCPv6 software.  It also provides guidelines
> for expert reviewers to evaluate new registrations.  This document
> updates RFC 3315.
> 
> This document is a product of the Dynamic Host Configuration Working Group of the IETF.
> 
> 
> BCP: This document specifies an Internet Best Current Practices for the
> Internet Community, and requests discussion and suggestions for 
> improvements. Distribution of this memo is unlimited.
> 
> This announcement is sent to the IETF-Announce and rfc-dist lists.
> To subscribe or unsubscribe, see
>  http://www.ietf.org/mailman/listinfo/ietf-announce
>  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
> 
> For searching the RFC series, see http://www.rfc-editor.org/search
> For downloading RFCs, see http://www.rfc-editor.org/rfc.html
> 
> Requests for special distribution should be addressed to either the
> author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
> specifically noted otherwise on the RFC itself, all RFCs are for
> unlimited distribution.
> 
> 
> The RFC Editor Team
> Association Management Solutions, LLC
> 
> 
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop