IETF Logo Mail Archive

Re: [v6ops] Interest in DHCPv6 Route/DefRouter/Src-basedRoute configuration to Client?

Ted Lemon <Ted.Lemon@nominum.com> Sat, 30 March 2013 19:13 UTC

Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6BC0221F874E for <v6ops@ietfa.amsl.com>; Sat, 30 Mar 2013 12:13:55 -0700 (PDT)
X-Quarantine-ID: <LITR-oatrq3k>
X-Amavis-Modified: Mail body modified (defanged) by ietfa.amsl.com
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Improper use of control character (char 0D hex): References: ...wtou7x6.wl%randy@psg.com>\r <2013032716331[...]
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level:
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[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 LITR-oatrq3k for <v6ops@ietfa.amsl.com>; Sat, 30 Mar 2013 12:13:54 -0700 (PDT)
Content-Type: multipart/mixed; boundary="----------=_1364670835-18023-0"
Content-Transfer-Encoding: binary
MIME-Version: 1.0
Received: from exprod7og123.obsmtp.com (exprod7og123.obsmtp.com [64.18.2.24]) by ietfa.amsl.com (Postfix) with ESMTP id BFD5621F86BC for <v6ops@ietf.org>; Sat, 30 Mar 2013 12:13:54 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob123.postini.com ([64.18.6.12]) with SMTP ID DSNKUVc5cuGCfwCaLWBj6AvZp2rAjyCNx6UD@postini.com; Sat, 30 Mar 2013 12:13:54 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 44E5F108280 for <v6ops@ietf.org>; Sat, 30 Mar 2013 12:13:54 -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 34FB119005C; Sat, 30 Mar 2013 12:13:54 -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.0318.004; Sat, 30 Mar 2013 12:13:48 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Philipp Kern <pkern@debian.org>
Date: Sat, 30 Mar 2013 19:13:47 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B630775127F3E@mbx-01.win.nominum.com>
References: <5151C83B.1010203@gmail.com> <CAKD1Yr20TUEd_+49531nFrs+PWOYL7eeADWOFVZPbgLUgbj=-g@mail.gmail.com> <C2EAFA4F-AAF8-48AD-8725-425025F7B239@ecs.soton.ac.uk> <5152B0C9.8010906@gmail.com> <EMEW3|8ba58554c4ae6d62b78016e584ba633bp2QBJq03tjc|ecs.soton.ac.uk|C2EAFA4F-AAF8-48AD-8725-425025F7B239@ecs.soton.ac.uk> <CAKD1Yr3=eeO+7KZNKkZH3dQMmxBh5LF3M2XkF+YBHaXRRc71QA@mail.gmail.com> <m2mwtou7x6.wl%randy@psg.com>\015 <20130327163318.GA10704@spike.0x539.de> <CC3B0D6C-3F3D-4922-93A1-58CF0BE159CA@delong.com> <20130330110545.GA29987@spike.0x539.de>
In-Reply-To: <20130330110545.GA29987@spike.0x539.de>
Cc: "v6ops@ietf.org" <v6ops@ietf.org>
Subject: Re: [v6ops] Interest in DHCPv6 Route/DefRouter/Src-basedRoute configuration to Client?
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 30 Mar 2013 19:13:55 -0000

WARNING: bad headers - Improper use of control character (char 0D hex):
 References: ...wtou7x6.wl%randy@psg.com>\r <2013032716331[...]
--- Begin Message --- 
On Mar 30, 2013, at 7:05 AM, Philipp Kern <pkern@debian.org> wrote:
> True. But it so utterly fails in multiboot and initially installation /
> provisioning scenarios that it isn't funny. So what should an installer do?
> Ubuntu did DUID-LL, but that's not really allowed in terms of the RFC. Maybe
> one should pass a fixed DUID in using PXE.

We're hoping that this will finally put the problem to bed:

https://datatracker.ietf.org/doc/draft-ietf-dhc-dhcpv6-client-link-layer-addr-opt/

Should be an RFC soon.   Put it in your RFPs and RFQs as a requirement.
--- End Message ---

v2.23.0 | Report a Bug | By Email