IETF Logo Mail Archive

Re: [Autoconf] Updated ad hoc addressing model document

"Charles E. Perkins" <charles.perkins@earthlink.net> Fri, 29 January 2010 21:02 UTC

Return-Path: <charles.perkins@earthlink.net>
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 F2B7B3A6889 for <autoconf@core3.amsl.com>; Fri, 29 Jan 2010 13:02:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.98
X-Spam-Level:
X-Spam-Status: No, score=-1.98 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, RCVD_IN_SORBS_WEB=0.619]
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 Gw7jXtp9pQj8 for <autoconf@core3.amsl.com>; Fri, 29 Jan 2010 13:02:45 -0800 (PST)
Received: from elasmtp-spurfowl.atl.sa.earthlink.net (elasmtp-spurfowl.atl.sa.earthlink.net [209.86.89.66]) by core3.amsl.com (Postfix) with ESMTP id 2149B3A659A for <autoconf@ietf.org>; Fri, 29 Jan 2010 13:02:45 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=kfZtpCOFjrX60n26fPWhEehB3RFZFq8/cjrEKcmlnltAkX/tHy5zZSG67uXWHQU2; h=Received:Message-ID:Date:From:Organization:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [12.204.153.98] (helo=[10.166.254.12]) by elasmtp-spurfowl.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from <charles.perkins@earthlink.net>) id 1Naxzf-0004mS-VO; Fri, 29 Jan 2010 16:03:08 -0500
Message-ID: <4B634D09.4090201@earthlink.net>
Date: Fri, 29 Jan 2010 13:03:05 -0800
From: "Charles E. Perkins" <charles.perkins@earthlink.net>
Organization: Wichorus Inc.
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.7) Gecko/20100111 Thunderbird/3.0.1
MIME-Version: 1.0
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
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>
In-Reply-To: <4B63493E.7050705@earthlink.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 137d7d78656ed6919973fd6a8f21c4f2d780f4a490ca6956abb457f1b4332f52d751f736a17f551853fcb8f82c3a39ae350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 12.204.153.98
Cc: "autoconf@ietf.org" <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: Fri, 29 Jan 2010 21:02:46 -0000

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
>

v2.8.7 | Report a Bug | By Email