Re: [Autoconf] call for presentation for IETF
"Charles E. Perkins" <charles.perkins@earthlink.net> Mon, 25 October 2010 21:43 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 15E413A680F for <autoconf@core3.amsl.com>; Mon, 25 Oct 2010 14:43:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.286
X-Spam-Level:
X-Spam-Status: No, score=-2.286 tagged_above=-999 required=5 tests=[AWL=0.313, 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 dtKwvdj-YjIL for <autoconf@core3.amsl.com>; Mon, 25 Oct 2010 14:43:48 -0700 (PDT)
Received: from elasmtp-scoter.atl.sa.earthlink.net (elasmtp-scoter.atl.sa.earthlink.net [209.86.89.67]) by core3.amsl.com (Postfix) with ESMTP id 22EBB3A6868 for <autoconf@ietf.org>; Mon, 25 Oct 2010 14:43:48 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=mn9/k4KHt6t/yoQCoycWU/B/EPIB4v25GN0cSVIf8n1K1nNOQ5QCAMmvDV8YK23i; 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.169]) by elasmtp-scoter.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from <charles.perkins@earthlink.net>) id 1PAUrE-0007Wu-Ov; Mon, 25 Oct 2010 17:45:33 -0400
Message-ID: <4CC5FA79.8080802@earthlink.net>
Date: Mon, 25 Oct 2010 14:45:29 -0700
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.2.11) Gecko/20101013 Lightning/1.0b2 Thunderbird/3.1.5
MIME-Version: 1.0
To: Teco Boot <teco@inf-net.nl>
References: <5EB91455-D51E-41BE-A077-8AFA5EDE4B15@gmail.com> <4CC53295.7010702@earthlink.net> <81BE4C83-80E5-409E-9337-6C0D76D87DBA@inf-net.nl>
In-Reply-To: <81BE4C83-80E5-409E-9337-6C0D76D87DBA@inf-net.nl>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 137d7d78656ed6919973fd6a8f21c4f2d780f4a490ca6956abb457f1b4332f522dda2f4f04d8576d649b76a3a08831a4350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 12.204.153.98
Cc: autoconf@ietf.org
Subject: Re: [Autoconf] call for presentation for IETF
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, 25 Oct 2010 21:43:49 -0000
Hello Teco, I'm really short on time, but... On 10/25/2010 2:21 PM, Teco Boot wrote: > Charlie, > Interesting. > Has the host a fixed relation to the router that provided the address? No. The router that provides the address, if it is running a MANET protocol on that interface, should provide an address unique for the network. > What is the L-bit in RA? I haven't thought about this, but presumably '1'. If that's the wrong answer, maybe we need more text, but I can't work on it today. > How can two hosts without nearby router communicate? This is a problem that can be considered separately, and the draft does not bear on this issue. > How can other nodes in the network know a path to the host? Do you mean, non-router nodes? Presumably they will use a router node as a default router and send packets to the default router. If the default router doesn't have a route (e.g., is not proactive), presumably the default router will issue a Route Request and get a route. This seems straightforward. Regards, Charlie P.
- Re: [Autoconf] call for presentation for IETF Teco Boot
- [Autoconf] call for presentation for IETF Ryuji Wakikawa
- Re: [Autoconf] call for presentation for IETF Charles E. Perkins
- Re: [Autoconf] call for presentation for IETF Ryuji Wakikawa
- Re: [Autoconf] call for presentation for IETF Teco Boot
- Re: [Autoconf] call for presentation for IETF Charles E. Perkins
- Re: [Autoconf] call for presentation for IETF Ryuji Wakikawa