IETF Logo Mail Archive

RE: [Autoconf] comments on draft-ietf-autoconf-manetarch-07.txt

"Templin, Fred L" <Fred.L.Templin@boeing.com> Tue, 04 December 2007 22:09 UTC

Return-path: <autoconf-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Izfxj-0000Qa-Fn; Tue, 04 Dec 2007 17:09:55 -0500
Received: from autoconf by megatron.ietf.org with local (Exim 4.43) id 1Izfxi-0000Pk-44 for autoconf-confirm+ok@megatron.ietf.org; Tue, 04 Dec 2007 17:09:54 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Izfxh-0000Pb-Qc for autoconf@ietf.org; Tue, 04 Dec 2007 17:09:53 -0500
Received: from blv-smtpout-01.boeing.com ([130.76.32.69]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Izfxh-0008A2-CF for autoconf@ietf.org; Tue, 04 Dec 2007 17:09:53 -0500
Received: from stl-av-01.boeing.com (stl-av-01.boeing.com [192.76.190.6]) by blv-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with ESMTP id lB4M9eKn020216 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 4 Dec 2007 14:09:41 -0800 (PST)
Received: from stl-av-01.boeing.com (localhost [127.0.0.1]) by stl-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id lB4M9euH010455; Tue, 4 Dec 2007 16:09:40 -0600 (CST)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com [130.247.55.84]) by stl-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id lB4M9dlr010425; Tue, 4 Dec 2007 16:09:39 -0600 (CST)
Received: from XCH-NW-7V2.nw.nos.boeing.com ([130.247.54.35]) by XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 4 Dec 2007 14:09:39 -0800
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: quoted-printable
Subject: RE: [Autoconf] comments on draft-ietf-autoconf-manetarch-07.txt
Date: Tue, 04 Dec 2007 14:08:52 -0800
Message-ID: <39C363776A4E8C4A94691D2BD9D1C9A1029EDC83@XCH-NW-7V2.nw.nos.boeing.com>
In-Reply-To: <4755CC22.9060300@gmail.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Autoconf] comments on draft-ietf-autoconf-manetarch-07.txt
Thread-Index: Acg2wANPcoB7J7r0TqCzWIJCSVmG1AAAbQUg
References: <200712041343.lB4Dhwq5006349@cichlid.raleigh.ibm.com> <009501c83696$7e9753a0$7bc5fae0$@nl><200712041945.lB4JjN83009254@cichlid.raleigh.ibm.com> <4755CC22.9060300@gmail.com>
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>, Thomas Narten <narten@us.ibm.com>
X-OriginalArrivalTime: 04 Dec 2007 22:09:39.0176 (UTC) FILETIME=[5CFDEE80:01C836C2]
X-Spam-Score: -4.0 (----)
X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0
Cc: autoconf@ietf.org
X-BeenThere: autoconf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Ad-Hoc Network Autoconfiguration WG discussion list <autoconf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/autoconf>, <mailto:autoconf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/autoconf>
List-Post: <mailto:autoconf@ietf.org>
List-Help: <mailto:autoconf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/autoconf>, <mailto:autoconf-request@ietf.org?subject=subscribe>
Errors-To: autoconf-bounces@ietf.org

 

> -----Original Message-----
> From: Alexandru Petrescu [mailto:alexandru.petrescu@gmail.com] 
> Sent: Tuesday, December 04, 2007 1:53 PM
> To: Thomas Narten
> Cc: autoconf@ietf.org
> Subject: Re: [Autoconf] comments on 
> draft-ietf-autoconf-manetarch-07.txt
> 
> Thomas Narten wrote:
> [...]
> >>> You really (I think) need to define an abstraction that defines
> >>> an link type of "manet" that handles all the "interesting" 
> >>> characteristics of MANETs (like non-transitive connectivity) but
> >>> that also presents itself to IP as a single IP subnet that has
> >>> the normal properties.
> > 
> >> I think there are two MANET implementation models.
> > 
> >> One is hiding MANET form IP, e.g. a sub-IP MANET model. This is
> >> more or less out-of-scope for IETF.
> > 
> > This could be done in the IETF, and maybe this is  a direction the
WG
> >  may want to pursue. But is this even a model the WG is currently 
> > considering?
> 
> As a member of this WG I can say that I currently consider a model
where
> the MANET protocol is run at sub-IP and offers a IP-friendly MAC
> already.   I mean the sub-IP may run MANET, or may not.  I'm
interested
> in the interface that sub-IP provides to my stack, and needing that
> interface to be a Ethernet MAC.

We talk about sub-IP MANET model in 'draft-templin-autoconf-dhcp'
(which contrary to the name is not only about dhcp solutions).
It makes life nice for IP, but may not be sufficient for MANETs
made up of heterogeneous link types.

Fred
fred.l.templin@boeing.com

> I would also like to learn from other WG members.
> 
> Alex
> 
> 
> ______________________________________________________________________
> This email has been scanned by the MessageLabs Email Security System.
> For more information please visit http://www.messagelabs.com/email 
> ______________________________________________________________________
> 
> 
> _______________________________________________
> Autoconf mailing list
> Autoconf@ietf.org
> https://www1.ietf.org/mailman/listinfo/autoconf
> 


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

v2.23.0 | Report a Bug | By Email