Re: [Autoconf] Using DHCPv6 without link-local? Support onlyEUI-64interfaces?

"Dearlove, Christopher (UK)" <Chris.Dearlove@baesystems.com> Mon, 02 August 2010 12:44 UTC

Return-Path: <Chris.Dearlove@baesystems.com>
X-Original-To: autoconf@core3.amsl.com
Delivered-To: autoconf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 801FF3A6898 for <autoconf@core3.amsl.com>; Mon, 2 Aug 2010 05:44:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.78
X-Spam-Level:
X-Spam-Status: No, score=-6.78 tagged_above=-999 required=5 tests=[AWL=-0.181, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 W3wGKolC+kV1 for <autoconf@core3.amsl.com>; Mon, 2 Aug 2010 05:44:51 -0700 (PDT)
Received: from ukmta3.baesystems.com (ukmta3.baesystems.com [20.133.40.55]) by core3.amsl.com (Postfix) with ESMTP id 24C993A6878 for <autoconf@ietf.org>; Mon, 2 Aug 2010 05:44:51 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.55,302,1278284400"; d="scan'208";a="79674019"
Received: from unknown (HELO baemasodc004.greenlnk.net) ([10.108.36.11]) by Baemasodc001ir.sharelnk.net with ESMTP; 02 Aug 2010 13:45:18 +0100
Received: from glkms1102.GREENLNK.NET (glkms1102.greenlnk.net [10.108.36.193]) by baemasodc004.greenlnk.net (Switch-3.4.3/Switch-3.4.3) with ESMTP id o72CjHMH015843; Mon, 2 Aug 2010 13:45:18 +0100
Received: from GLKMS2100.GREENLNK.NET ([10.15.184.93]) by glkms1102.GREENLNK.NET with Microsoft SMTPSVC(6.0.3790.3959); Mon, 2 Aug 2010 13:45:18 +0100
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Date: Mon, 2 Aug 2010 13:45:15 +0100
Message-ID: <ABE739C5ADAC9A41ACCC72DF366B719D034C607F@GLKMS2100.GREENLNK.NET>
In-Reply-To: <47C9A85F-0920-4EED-A605-3BEB99C4BA9B@inf-net.nl>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
thread-topic: [Autoconf] Using DHCPv6 without link-local? Support onlyEUI-64interfaces?
thread-index: AcsyOsWpL1wfPa0iRDGL8nPHeTvJcQABSBMw
References: <EBE1B970-DADA-4643-BB75-4EDEDE41F758@inf-net.nl><ABE739C5ADAC9A41ACCC72DF366B719D034C5D21@GLKMS2100.GREENLNK.NET><9ED0AF66-FB65-485C-B418-E25200A0DE88@inf-net.nl><ABE739C5ADAC9A41ACCC72DF366B719D034C5EA0@GLKMS2100.GREENLNK.NET> <47C9A85F-0920-4EED-A605-3BEB99C4BA9B@inf-net.nl>
From: "Dearlove, Christopher (UK)" <Chris.Dearlove@baesystems.com>
To: "Teco Boot" <teco@inf-net.nl>
X-OriginalArrivalTime: 02 Aug 2010 12:45:18.0019 (UTC) FILETIME=[8FB06930:01CB3240]
Cc: autoconf@ietf.org
Subject: Re: [Autoconf] Using DHCPv6 without link-local? Support onlyEUI-64interfaces?
X-BeenThere: autoconf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Ad-Hoc Network Autoconfiguration WG discussion list <autoconf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/autoconf>, <mailto:autoconf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/autoconf>
List-Post: <mailto:autoconf@ietf.org>
List-Help: <mailto:autoconf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/autoconf>, <mailto:autoconf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Aug 2010 12:44:52 -0000

Essentially RFC 3941 is generating random interface IDs. (There
are practical issues, but really they are about what should be
random working and not e.g. having two nodes use the same PRNG
and repeatedly clash.) It is a solution that is not using EUI-64
(except as a part of a seed for the random process) to ensure
uniqueness. And all I said was that the EUI-64 solution isn't
acceptable in some cases.

-- 
Christopher Dearlove
Technology Leader, Communications Group
Networks, Security and Information Systems Department
BAE Systems Advanced Technology Centre
West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK
Tel: +44 1245 242194  Fax: +44 1245 242124

BAE Systems (Operations) Limited
Registered Office: Warwick House, PO Box 87,
Farnborough Aerospace Centre, Farnborough, Hants, GU14 6YU, UK
Registered in England & Wales No: 1996687

-----Original Message-----
From: autoconf-bounces@ietf.org [mailto:autoconf-bounces@ietf.org] On
Behalf Of Teco Boot
Sent: 02 August 2010 13:04
To: Dearlove, Christopher (UK)
Cc: autoconf@ietf.org
Subject: Re: [Autoconf] Using DHCPv6 without link-local? Support
onlyEUI-64interfaces?


                    *** WARNING ***

  This message has originated outside your organisation,
  either from an external partner or the Global Internet. 
      Keep this in mind if you answer this message.
 

>> On RFC 3091 and dupont-ipv6-rfc3041harmful, the recommendations are
in
> RFC 4901.
> 
> Is that the number you meant? That's titled "Protocol Extensions for
> Header
> Compression over MPLS" Without reading it, that's not the title of an
> RFC
> that I'd read to discuss the issues of EUI-64 addresses and the issues
I
> referenced.

Sorry, typo. RFC 4941 obsoletes RFC 3041.
RFC 4941 adopted recommendations in dupont-ipv6-rfc3041harmful.

Teco.

_______________________________________________
Autoconf mailing list
Autoconf@ietf.org
https://www.ietf.org/mailman/listinfo/autoconf


********************************************************************
This email and any attachments are confidential to the intended
recipient and may also be privileged. If you are not the intended
recipient please delete it from your system and notify the sender.
You should not copy it or use it for any purpose nor disclose or
distribute its contents to any other person.
********************************************************************