Re: [dhcwg] Reg RFC6704 (Forcerenew Nonce Authentication)
Ted Lemon <Ted.Lemon@nominum.com> Wed, 12 September 2012 12:34 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 0C2EE21F859B for <dhcwg@ietfa.amsl.com>; Wed, 12 Sep 2012 05:34:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.543
X-Spam-Level:
X-Spam-Status: No, score=-106.543 tagged_above=-999 required=5 tests=[AWL=0.056, 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 MtB-oqv1avCV for <dhcwg@ietfa.amsl.com>; Wed, 12 Sep 2012 05:34:08 -0700 (PDT)
Received: from exprod7og111.obsmtp.com (exprod7og111.obsmtp.com [64.18.2.175]) by ietfa.amsl.com (Postfix) with ESMTP id 5B09921F85A2 for <dhcwg@ietf.org>; Wed, 12 Sep 2012 05:34:08 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob111.postini.com ([64.18.6.12]) with SMTP ID DSNKUFCBPaLpQiZVpnCCkD0Yc2BnWpK0Dn0v@postini.com; Wed, 12 Sep 2012 05:34:08 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 11925F80A3 for <dhcwg@ietf.org>; Wed, 12 Sep 2012 05:33:56 -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 06DAC19005C; Wed, 12 Sep 2012 05:33:56 -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; Wed, 12 Sep 2012 05:33:50 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: "Gaurav Halwasia (ghalwasi)" <ghalwasi@cisco.com>
Thread-Topic: [dhcwg] Reg RFC6704 (Forcerenew Nonce Authentication)
Thread-Index: AQHNkE8cKpbVbNLxRMad4YyhUAitE5eGD8kAgABVhgCAABPzAIAAI2EAgAB9z4A=
Date: Wed, 12 Sep 2012 12:33:48 +0000
Message-ID: <5B2EA53A-C3C9-4B6B-BE17-1B51B8BD5E44@nominum.com>
References: <90903C21C73202418A48BFBE80AEE5EB19241E49@xmb-rcd-x06.cisco.com> <CC756F01.221C%volz@cisco.com> <90903C21C73202418A48BFBE80AEE5EB19242188@xmb-rcd-x06.cisco.com>
In-Reply-To: <90903C21C73202418A48BFBE80AEE5EB19242188@xmb-rcd-x06.cisco.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="iso-8859-2"
Content-ID: <F13ADE68819E774BBC1EAB6809D1EDDD@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, "Bernie Volz (volz)" <volz@cisco.com>, "<curtis@occnc.com>" <curtis@occnc.com>
Subject: Re: [dhcwg] Reg RFC6704 (Forcerenew Nonce Authentication)
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: Wed, 12 Sep 2012 12:34:09 -0000
On Sep 12, 2012, at 1:03 AM, "Gaurav Halwasia (ghalwasi)" <ghalwasi@cisco.com> wrote: > Are you sure you are referring to the correct spec. (3318.?) In case you meant RFC3203, I wanted to clarify that original Forcerenew spec indeed accommodates DHCP INFORM triggered by Forcerenew as RFC 3315 accommodates Information-Request. So i was surprised to find no reference of INFORM in 6704. This is want I wanted to clarify. I am not particularly stressing to take this work right now but still finding it little confusing to find that as per current standards we are saying that we can use Forcerenew Nonce Authentication for RENEW triggered by FORCERENEW but we still have to use original DHCP authentication for INFORM triggered by FORCERENEW. Okay, now I understand why you raised this now. I still think it's not work we ought to take on right now, but it makes more sense now. BTW, having given you a bit of a hard time about proposing new work for the working group, I would like to commend you for raising this on the mailing list between meetings. Now is a really good time to be proposing new work, so that we can discuss it and decide whether it needs a presentation at the next IETF. I hope others will follow your example, and that my reaction won't discourage this.
- [dhcwg] Reg RFC6704 (Forcerenew Nonce Authenticat… Gaurav Halwasia (ghalwasi)
- Re: [dhcwg] Reg RFC6704 (Forcerenew Nonce Authent… Ted Lemon
- Re: [dhcwg] Reg RFC6704 (Forcerenew Nonce Authent… Ted Lemon
- Re: [dhcwg] Reg RFC6704 (Forcerenew Nonce Authent… Curtis Villamizar
- Re: [dhcwg] Reg RFC6704 (Forcerenew Nonce Authent… Curtis Villamizar
- Re: [dhcwg] Reg RFC6704 (Forcerenew Nonce Authent… Gaurav Halwasia (ghalwasi)
- Re: [dhcwg] Reg RFC6704 (Forcerenew Nonce Authent… Gaurav Halwasia (ghalwasi)
- Re: [dhcwg] Reg RFC6704 (Forcerenew Nonce Authent… Ted Lemon
- Re: [dhcwg] Reg RFC6704 (Forcerenew Nonce Authent… Bernie Volz (volz)
- Re: [dhcwg] Reg RFC6704 (Forcerenew Nonce Authent… Bernie Volz (volz)
- Re: [dhcwg] Reg RFC6704 (Forcerenew Nonce Authent… Gaurav Halwasia (ghalwasi)
- Re: [dhcwg] Reg RFC6704 (Forcerenew Nonce Authent… Bernie Volz (volz)
- Re: [dhcwg] Reg RFC6704 (Forcerenew Nonce Authent… Ted Lemon
- Re: [dhcwg] Reg RFC6704 (Forcerenew Nonce Authent… Curtis Villamizar