Re: [Autoconf] Updated ad hoc addressing model document
"Teco Boot" <teco@inf-net.nl> Sat, 30 January 2010 11:26 UTC
Return-Path: <teco@inf-net.nl>
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 D8C6F3A67AB for <autoconf@core3.amsl.com>;
Sat, 30 Jan 2010 03:26:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,
BAYES_00=-2.599]
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 A9iuGCDz17ZP for
<autoconf@core3.amsl.com>; Sat, 30 Jan 2010 03:26:51 -0800 (PST)
Received: from CPSMTPM-EML104.kpnxchange.com (cpsmtpm-eml104.kpnxchange.com
[195.121.3.8]) by core3.amsl.com (Postfix) with ESMTP id 7F9F63A67F8 for
<autoconf@ietf.org>; Sat, 30 Jan 2010 03:26:50 -0800 (PST)
Received: from M90Teco ([86.83.9.22]) by CPSMTPM-EML104.kpnxchange.com with
Microsoft SMTPSVC(7.0.6001.18000); Sat, 30 Jan 2010 12:27:15 +0100
From: "Teco Boot" <teco@inf-net.nl>
To: "'Charles E. Perkins'" <charles.perkins@earthlink.net>
References: <be8c8d781001260409qd23d4era0eac47eaeb3dba2@mail.gmail.com> <8DC BF4A4-7879-4148-A8FE-9A73219536B9@gmail.com><008c01caa0fe$0eee3530$2cca9f90$@nl><4B631699.7040504@earthlink.net> <009001caa10d$8729a2a0$957ce7e0$@nl> <E1829B60731D1740BB7A0626B4FAF0A64950F33B0C@XCH-NW-01V.nw.nos.boeing.com> <4B63493E.7050705@earthlink.net>
<4B634D09.4090201@earthlink.net>
In-Reply-To: <4B634D09.4090201@earthlink.net>
Date: Sat, 30 Jan 2010 12:27:12 +0100
Message-ID: <00a701caa19f$2ae7b260$80b71720$@nl>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcqhJnu4yJUYdduiQRqgywM6+QwV7AAeCG6A
Content-Language: nl
X-OriginalArrivalTime: 30 Jan 2010 11:27:15.0245 (UTC)
FILETIME=[2C87CDD0:01CAA19F]
Cc: autoconf@ietf.org, 'Thomas Heide Clausen' <thomas@thomasclausen.org>
Subject: Re: [Autoconf] Updated ad hoc addressing model document
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: Sat, 30 Jan 2010 11:26:51 -0000
Hi Charlie, I think you overlook something. Getting unique addresses applies to any address that should be unique :-). Why could we assume that non-link-local addresses work great with almost no effort? Regards, Teco >-----Oorspronkelijk bericht----- >Van: autoconf-bounces@ietf.org [mailto:autoconf-bounces@ietf.org] Namens >Charles E. Perkins >Verzonden: vrijdag 29 januari 2010 22:03 >Aan: Templin, Fred L >CC: autoconf@ietf.org; 'Thomas Heide Clausen' >Onderwerp: Re: [Autoconf] Updated ad hoc addressing model document > > >Hello again folks, > >I should have mentioned that, of course, link-locals >work great with almost no effort, if one can assume >unique L2 addresses. Mea culpa! > >And, as I mentioned before, I think it would be a >really good idea for link-local proponents to write >up a document (perhaps only one paragraph) >saying pretty much exactly that. > >Regards, >Charlie P. > > >On 1/29/2010 12:46 PM, Charles E. Perkins wrote: >> >> Hello Fred, >> >> On 1/29/2010 10:10 AM, Templin, Fred L wrote: >>> >>> I believe OSPFv3 for one is going to need link-locals >>> when it is used as a MANET routing protocol. (That is >>> not to say that OSPFv3 can only carry IPv6 routes; it >>> can also use Address Family extensions to carry IPv4 >>> routes.) >> >> I'd like to see how they are going to do it. >> >> For all the discussion about how some people really >> really need link-locals, I somehow missed the part >> about how they were really going to be able to do >> it -- except under highly restrictive circumstances >> (e.g., single hop from backbone, ...). But, full disclosure >> here, I didn't follow the OSPF effort very well. At one >> point, when I was paying attention, it seemed to me that >> they were trying to do the right thing. >> >> Regards, >> Charlie P. >> >> _______________________________________________ >> Autoconf mailing list >> Autoconf@ietf.org >> https://www.ietf.org/mailman/listinfo/autoconf >> > >_______________________________________________ >Autoconf mailing list >Autoconf@ietf.org >https://www.ietf.org/mailman/listinfo/autoconf
- [Autoconf] Updated ad hoc addressing model docume… Emmanuel Baccelli
- Re: [Autoconf] Updated ad hoc addressing model do… Zach Shelby
- Re: [Autoconf] Updated ad hoc addressing model do… Thomas Heide Clausen
- Re: [Autoconf] Updated ad hoc addressing model do… Ryuji Wakikawa
- Re: [Autoconf] Updated ad hoc addressing model do… Ryuji Wakikawa
- Re: [Autoconf] Updated ad hoc addressing model do… Ulrich Herberg
- Re: [Autoconf] Updated ad hoc addressing model do… Teco Boot
- Re: [Autoconf] Updated ad hoc addressing model do… Charles E. Perkins
- Re: [Autoconf] Updated ad hoc addressing model do… Teco Boot
- Re: [Autoconf] Updated ad hoc addressing model do… Templin, Fred L
- Re: [Autoconf] Updated ad hoc addressing model do… Charles E. Perkins
- Re: [Autoconf] Updated ad hoc addressing model do… Charles E. Perkins
- Re: [Autoconf] Updated ad hoc addressing model do… Charles E. Perkins
- Re: [Autoconf] Updated ad hoc addressing model do… Teco Boot
- Re: [Autoconf] Updated ad hoc addressing model do… Teco Boot
- Re: [Autoconf] Updated ad hoc addressing model do… Thomas Heide Clausen
- Re: [Autoconf] Updated ad hoc addressing model do… Thomas Heide Clausen
- Re: [Autoconf] Updated ad hoc addressing model do… Thomas Heide Clausen
- Re: [Autoconf] Updated ad hoc addressing model do… Zach Shelby
- Re: [Autoconf] Updated ad hoc addressing model do… Alexandru Petrescu
- Re: [Autoconf] Updated ad hoc addressing model do… Teco Boot
- Re: [Autoconf] Updated ad hoc addressing model do… Thomas Heide Clausen
- Re: [Autoconf] Updated ad hoc addressing model do… Charles E. Perkins
- Re: [Autoconf] Updated ad hoc addressing model do… Teco Boot
- Re: [Autoconf] Updated ad hoc addressing model do… Teco Boot
- Re: [Autoconf] Updated ad hoc addressing model do… Teco Boot
- Re: [Autoconf] Updated ad hoc addressing model do… Teco Boot
- Re: [Autoconf] Updated ad hoc addressing model do… Thomas Heide Clausen
- Re: [Autoconf] Updated ad hoc addressing model do… Teco Boot
- Re: [Autoconf] Updated ad hoc addressing model do… Thomas Heide Clausen
- Re: [Autoconf] Updated ad hoc addressing model do… Charles E. Perkins
- Re: [Autoconf] Updated ad hoc addressing model do… Charles E. Perkins
- Re: [Autoconf] Updated ad hoc addressing model do… Teco Boot
- Re: [Autoconf] Updated ad hoc addressing model do… Charles E. Perkins
- Re: [Autoconf] Updated ad hoc addressing model do… Carlos Jesús Bernardos Cano
- Re: [Autoconf] Updated ad hoc addressing model do… Charles E. Perkins
- Re: [Autoconf] Updated ad hoc addressing model do… Carlos Jesús Bernardos Cano
- Re: [Autoconf] Updated ad hoc addressing model do… Teco Boot
- Re: [Autoconf] Updated ad hoc addressing model do… Teco Boot
- Re: [Autoconf] Updated ad hoc addressing model do… Charles E. Perkins
- Re: [Autoconf] Updated ad hoc addressing model do… Charles E. Perkins