[dhcwg] To wait for RA or not to wait?
Ted Lemon <Ted.Lemon@nominum.com> Fri, 02 December 2011 17:41 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 6B2EF11E80C5 for <dhcwg@ietfa.amsl.com>; Fri, 2 Dec 2011 09:41:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.498
X-Spam-Level:
X-Spam-Status: No, score=-106.498 tagged_above=-999 required=5 tests=[AWL=0.101, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W3EqP0GAMh1s for <dhcwg@ietfa.amsl.com>; Fri, 2 Dec 2011 09:41:23 -0800 (PST)
Received: from exprod7og104.obsmtp.com (exprod7og104.obsmtp.com [64.18.2.161]) by ietfa.amsl.com (Postfix) with ESMTP id 6372F11E80B4 for <dhcwg@ietf.org>; Fri, 2 Dec 2011 09:41:23 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob104.postini.com ([64.18.6.12]) with SMTP ID DSNKTtkNwooww5ah3vG+4ygdckQx1VAphVsL@postini.com; Fri, 02 Dec 2011 09:41:23 PST
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 698721B8299 for <dhcwg@ietf.org>; Fri, 2 Dec 2011 09:41:22 -0800 (PST)
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 630CE190052; Fri, 2 Dec 2011 09:41:22 -0800 (PST) (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.01.0339.001; Fri, 2 Dec 2011 09:41:22 -0800
From: Ted Lemon <Ted.Lemon@nominum.com>
To: dhc WG <dhcwg@ietf.org>
Thread-Topic: To wait for RA or not to wait?
Thread-Index: AQHMsRmaAFDsJ61sskWNi8UGYH6hlQ==
Date: Fri, 02 Dec 2011 17:41:21 +0000
Message-ID: <A44BD847-A71B-49DB-80A2-B4B39F52ED58@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="Windows-1252"
Content-ID: <5D83731FD9B57C4482F7B0533100E4C5@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [dhcwg] To wait for RA or not to wait?
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: Fri, 02 Dec 2011 17:41:24 -0000
> Ted, I read “we are not qualified to make architectural decisions about IPv6 transition technologies that don't directly involve DHCP”. Good, however, the RFC6204 initially was putting a req in place to state that the CPE MUST wait for the RA prior of starting its DHCPv6 client. This is linked to DHCP I’d say, no ? I see too many times that links are being made between protocols or check for address or …. It is OK to say that one should wait for it, so to leave it open as implementation choice or configuration possibility for the vendor. If I had it to do over again, I'd do RA and DHCP a lot differently, but at this point I think in general we should assume that we will always have RAs, and DHCP clients should wait for them. DHCP doesn't really work without the RA—even if you get an address, you have no default route.
- Re: [dhcwg] To wait for RA or not to wait? Ted Lemon
- Re: [dhcwg] To wait for RA or not to wait? Ole Troan
- [dhcwg] To wait for RA or not to wait? Ted Lemon
- Re: [dhcwg] To wait for RA or not to wait? Wuyts Carl
- Re: [dhcwg] To wait for RA or not to wait? Ted Lemon
- Re: [dhcwg] To wait for RA or not to wait? Ole Troan
- Re: [dhcwg] To wait for RA or not to wait? Masataka Ohta
- Re: [dhcwg] To wait for RA or not to wait? Ted Lemon
- Re: [dhcwg] To wait for RA or not to wait? Ted Lemon
- Re: [dhcwg] To wait for RA or not to wait? Ole Troan
- Re: [dhcwg] To wait for RA or not to wait? Masataka Ohta
- Re: [dhcwg] To wait for RA or not to wait? Ted Lemon
- Re: [dhcwg] To wait for RA or not to wait? Masataka Ohta
- Re: [dhcwg] To wait for RA or not to wait? Hemant Singh (shemant)
- Re: [dhcwg] To wait for RA or not to wait? Hemant Singh (shemant)
- Re: [dhcwg] To wait for RA or not to wait? Masataka Ohta
- Re: [dhcwg] To wait for RA or not to wait? Masataka Ohta
- Re: [dhcwg] To wait for RA or not to wait? Hemant Singh (shemant)
- Re: [dhcwg] To wait for RA or not to wait? Hemant Singh (shemant)
- [dhcwg] No default routers (was Re: To wait for R… Masataka Ohta
- Re: [dhcwg] To wait for RA or not to wait? Wuyts Carl
- Re: [dhcwg] To wait for RA or not to wait? Masataka Ohta
- Re: [dhcwg] To wait for RA or not to wait? Hemant Singh (shemant)
- Re: [dhcwg] No default routers (was Re: To wait f… Ted Lemon
- Re: [dhcwg] No default routers (was Re: To wait f… Masataka Ohta
- Re: [dhcwg] To wait for RA or not to wait? Masataka Ohta
- Re: [dhcwg] To wait for RA or not to wait? Hemant Singh (shemant)
- Re: [dhcwg] To wait for RA or not to wait? Masataka Ohta
- Re: [dhcwg] To wait for RA or not to wait? Hemant Singh (shemant)
- Re: [dhcwg] To wait for RA or not to wait? Masataka Ohta
- Re: [dhcwg] To wait for RA or not to wait? Hemant Singh (shemant)
- Re: [dhcwg] To wait for RA or not to wait? Masataka Ohta