IETF Logo Mail Archive

Re: [dhcwg] Call for adoption: draft-boucadair-dhc-triggered-reconfigure

Ted Lemon <Ted.Lemon@nominum.com> Tue, 11 September 2012 14:03 UTC

Return-Path: <Ted.Lemon@nominum.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 A052621F87F3 for <dhcwg@ietfa.amsl.com>; Tue, 11 Sep 2012 07:03:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.56
X-Spam-Level:
X-Spam-Status: No, score=-106.56 tagged_above=-999 required=5 tests=[AWL=0.039, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id s6bF8K7TdmQf for <dhcwg@ietfa.amsl.com>; Tue, 11 Sep 2012 07:03:36 -0700 (PDT)
Received: from exprod7og108.obsmtp.com (exprod7og108.obsmtp.com [64.18.2.169]) by ietfa.amsl.com (Postfix) with ESMTP id B359921F8623 for <dhcwg@ietf.org>; Tue, 11 Sep 2012 07:03:30 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob108.postini.com ([64.18.6.12]) with SMTP ID DSNKUE9Eshk8mzDX9zeS+4kicqGsfFWDlsVS@postini.com; Tue, 11 Sep 2012 07:03:30 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 EFFDCF809B for <dhcwg@ietf.org>; Tue, 11 Sep 2012 07:03:29 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id E7CA619005C for <dhcwg@ietf.org>; Tue, 11 Sep 2012 07:03:29 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.02.0247.003; Tue, 11 Sep 2012 07:03:30 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: "dhcwg@ietf.org WG" <dhcwg@ietf.org>
Thread-Topic: [dhcwg] Call for adoption: draft-boucadair-dhc-triggered-reconfigure
Thread-Index: AQHNggw8RB5j9kIDsUGrLGIrni1hs5eFuqYAgAADCQA=
Date: Tue, 11 Sep 2012 14:03:28 +0000
Message-ID: <50ACBB72-EA39-4E31-963B-77406E0D1807@nominum.com>
References: <AE6C424A-7BA3-4239-817E-44BE0B71D3DD@nominum.com> <BA6CAF38-5AFD-4998-A268-25AE1142BFCB@nominum.com>
In-Reply-To: <BA6CAF38-5AFD-4998-A268-25AE1142BFCB@nominum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <D18404EEC8FB9141904423541D7FCABB@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [dhcwg] Call for adoption: draft-boucadair-dhc-triggered-reconfigure
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 11 Sep 2012 14:03:36 -0000

On Sep 11, 2012, at 9:52 AM, Ted Lemon <Ted.Lemon@nominum.com> wrote:
> If, reading this, you feel that it was a mistake for me to approve the draft, please say so

To be more clear, what I mean by "approve this draft" is "click on the control button that allows it to be published as a working group draft," not "give the draft my seal of approval."   I had done a consensus evaluation on a different draft, and mistakenly remembered it as having been this draft, so that's why I clicked the approve button.   But then I went back and checked, and the response wasn't as big as I remembered, so that's why I sent the clarifying message out.   I apologize for the verbose explanations, but I feel that it's better to be verbose just in case anybody felt that I didn't do the right thing, so that we can be clear about precisely what right thing I didn't do. :)

v2.23.0 | Report a Bug | By Email