Re: [dhcwg] RFC3633: REBIND/REPLY after the link has flapped
Ted Lemon <Ted.Lemon@nominum.com> Mon, 08 November 2010 08:39 UTC
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 31EF03A67D4 for <dhcwg@core3.amsl.com>; Mon, 8 Nov 2010 00:39:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.598
X-Spam-Level:
X-Spam-Status: No, score=-106.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vinlRZHXb+3g for <dhcwg@core3.amsl.com>; Mon, 8 Nov 2010 00:39:18 -0800 (PST)
Received: from exprod7og122.obsmtp.com (exprod7og122.obsmtp.com [64.18.2.22]) by core3.amsl.com (Postfix) with ESMTP id 5DF7B3A6452 for <dhcwg@ietf.org>; Mon, 8 Nov 2010 00:39:17 -0800 (PST)
Received: from source ([64.89.228.229]) (using TLSv1) by exprod7ob122.postini.com ([64.18.6.12]) with SMTP ID DSNKTNe3STs55MXxDw+Db9D8eM2TYMuB7tyg@postini.com; Mon, 08 Nov 2010 00:39:39 PST
Received: from webmail.nominum.com (exchange-10.nominum.com [64.89.228.57]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (Client CN "exchange-10.win.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id A387C1B882B; Mon, 8 Nov 2010 00:39:37 -0800 (PST)
Received: from exchange-10.WIN.NOMINUM.COM ([64.89.228.57]) by exchange-10.WIN.NOMINUM.COM ([64.89.228.57]) with mapi; Mon, 8 Nov 2010 00:39:37 -0800
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Dedecker Hans <Hans.Dedecker@technicolor.com>
Date: Mon, 08 Nov 2010 00:39:36 -0800
Thread-Topic: [dhcwg] RFC3633: REBIND/REPLY after the link has flapped
Thread-Index: Act/IHoCH9qONnPTQo2ZrpqGYzkb5Q==
Message-ID: <659006BE-6C35-458C-8F57-CCB339E5B658@nominum.com>
References: <3F4910A77924AF44876B1A096ECC92A7CC9F4A69B4@MOPESMBX01.eu.thmulti.com>
In-Reply-To: <3F4910A77924AF44876B1A096ECC92A7CC9F4A69B4@MOPESMBX01.eu.thmulti.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_659006BE6C35458C8F57CCB339E5B658nominumcom_"
MIME-Version: 1.0
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] RFC3633: REBIND/REPLY after the link has flapped
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 08 Nov 2010 08:39:20 -0000
On Oct 25, 2010, at 10:56 PM, Dedecker Hans wrote: As RFC3633 does not state explicitly that the DHCPv6 client can start immediately a REBIND/REPLY message exchange after the link has flapped it’s open for interpretation …. I didn't see an answer to this, so even though it's a month late I'll answer it now. The text you quote from RFC3633 section 12.1 doesn't make sense unless it specifies new behavior. DHCPv6 clients _always_ rebind when T2 expires. So the only reading that makes sense is that the text you've quoted from RFC3633 means that you are to *immediately* rebind.
- [dhcwg] RFC3633: REBIND/REPLY after the link has … Dedecker Hans
- Re: [dhcwg] RFC3633: REBIND/REPLY after the link … Bernie Volz (volz)
- Re: [dhcwg] RFC3633: REBIND/REPLY after the link … Ted Lemon