Return-Path: 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 BC61121F872A for ; Fri, 24 Aug 2012 08:24:02 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.9 X-Spam-Level: X-Spam-Status: No, score=-5.9 tagged_above=-999 required=5 tests=[AWL=0.077, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_MED=-4] 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 acX2rdhIhFkU for ; Fri, 24 Aug 2012 08:24:02 -0700 (PDT) Received: from na3sys010aog108.obsmtp.com (na3sys010aog108.obsmtp.com [74.125.245.84]) by ietfa.amsl.com (Postfix) with SMTP id 6F5B221F86C7 for ; Fri, 24 Aug 2012 08:23:58 -0700 (PDT) Received: from mail-qc0-f180.google.com ([209.85.216.180]) (using TLSv1) by na3sys010aob108.postini.com ([74.125.244.12]) with SMTP ID DSNKUDecjpwmw+k56n6f91f7L90FdSELveqq@postini.com; Fri, 24 Aug 2012 08:23:58 PDT Received: by qcmv28 with SMTP id v28so1244907qcm.25 for ; Fri, 24 Aug 2012 08:23:57 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding:x-gm-message-state; bh=5g3ayRmqAwcfAMTBSg82li2cJZrZJgYMgnsaXPe9U0U=; b=lhnG7o9q7CdSFHNVXLFJwLKOcweQoeWZaZ2LZblJjxppNBg0gu2V/FA01k8ve4uR4w OeP91Tk+0HZAsqZwxclUe6TtwjL91++9ntCxN+RZWCcJ1U+4JBkQaOlWPyt+2+ID6L8H zeAdYaw0VJ4fEpRGqQX6Cfxk4J8TjAQbF4lQ44rHzWsL3QDG2Od7JnKUsc2ORJTYmDJe Rb/f6VJHRi2gv4+VPF4ouFiT6kAL6vJqAjXbx21+eb2r78ZDCCXfo0foUnzUifzJVlC8 KI0IJDF4iT9ubiqcl0sgrGVjwROvPZyAqvcuvq++QDHQjbc+JHEjToYJ8x6F6YImeuer CxtQ== MIME-Version: 1.0 Received: by 10.224.185.198 with SMTP id cp6mr9204391qab.79.1345821837437; Fri, 24 Aug 2012 08:23:57 -0700 (PDT) Received: by 10.229.32.4 with HTTP; Fri, 24 Aug 2012 08:23:57 -0700 (PDT) In-Reply-To: References: Date: Fri, 24 Aug 2012 08:23:57 -0700 Message-ID: From: Andre Kostur To: Ted Lemon Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Gm-Message-State: ALoCoQkXXK88lw1aTs0UDzJ/1ZWBZ9oh2G6N8Rt2RTinUYfvTQVWoR0zbPYSRWUm888WYPrZkTOH Cc: "dhcwg@ietf.org WG" 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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Aug 2012 15:24:02 -0000 I can see this being useful in certain environments. Yes. On Fri, Aug 24, 2012 at 8:22 AM, Ted Lemon wrote: > The author of this draft has requested that the working group consider ad= opting it as a working group item. The document is in scope for the curre= nt DHC working group charter. The document proposes a mechanism whereby a= DHCP relay agent co-located with a RADIUS agent can trigger a DHCP Reconfi= gure when it receives a notification from the RADIUS server that informatio= n previously provided in the Relay-Supplied Options option has changed. > > If you think this is something the working group should work on, please r= eply to this message saying so. If you think the working group should not= do this work, please reply to this message saying so. We will evaluate c= onsensus to adopt on September 7. > > _______________________________________________ > dhcwg mailing list > dhcwg@ietf.org > https://www.ietf.org/mailman/listinfo/dhcwg --=20 Andre Kostur