RE: [Autoconf] Configuring 'default' in Multi-Subnet MANETs

"Dave Thaler" <dthaler@windows.microsoft.com> Sat, 01 April 2006 02:35 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FPVxc-00070w-76; Fri, 31 Mar 2006 21:35:32 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FPObW-0005su-E7 for autoconf@ietf.org; Fri, 31 Mar 2006 13:44:14 -0500
Received: from mail3.microsoft.com ([131.107.3.123]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FPObW-00083z-2k for autoconf@ietf.org; Fri, 31 Mar 2006 13:44:14 -0500
Received: from mailout6.microsoft.com ([157.54.69.150]) by mail3.microsoft.com with Microsoft SMTPSVC(6.0.3790.2499); Fri, 31 Mar 2006 10:44:13 -0800
Received: from tuk-hub-01.redmond.corp.microsoft.com ([157.54.70.27]) by mailout6.microsoft.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 31 Mar 2006 10:44:12 -0800
Received: from win-imc-01.wingroup.windeploy.ntdev.microsoft.com ([157.54.0.39]) by tuk-hub-01.redmond.corp.microsoft.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 31 Mar 2006 10:44:11 -0800
Received: from win-msg-01.wingroup.windeploy.ntdev.microsoft.com ([157.54.5.41]) by win-imc-01.wingroup.windeploy.ntdev.microsoft.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 31 Mar 2006 10:44:11 -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] Configuring 'default' in Multi-Subnet MANETs
Date: Fri, 31 Mar 2006 10:44:07 -0800
Message-ID: <2E33960095B58E40A4D3345AB9F65EC116742E9A@win-msg-01.wingroup.windeploy.ntdev.microsoft.com>
In-Reply-To: <013c01c654ef$c726e610$165cfa84@SEXTANT>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Autoconf] Configuring 'default' in Multi-Subnet MANETs
Thread-Index: AcZUXj109ThDOJ+TRcSPfZRMJStFbAAjjfGgAAGXACA=
From: Dave Thaler <dthaler@windows.microsoft.com>
To: Joe Macker <joseph.macker@nrl.navy.mil>, "Templin, Fred L" <Fred.L.Templin@boeing.com>, autoconf@ietf.org
X-OriginalArrivalTime: 31 Mar 2006 18:44:11.0630 (UTC) FILETIME=[19FAF0E0:01C654F3]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17
X-Mailman-Approved-At: Fri, 31 Mar 2006 21:35:31 -0500
Cc:
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

I agree with Joe.

Injecting a default route from the border router(s) into the routing
protocol in use is no different from injection of any other route from
any other router, and it's orthogonal to the issue of how to number
internal routers as discussed in the multisubnet-manets document.

-Dave

-----Original Message-----
From: Joe Macker [mailto:joseph.macker@nrl.navy.mil] 
Sent: Friday, March 31, 2006 10:20 AM
To: 'Templin, Fred L'; autoconf@ietf.org
Cc: Dave Thaler
Subject: RE: [Autoconf] Configuring 'default' in Multi-Subnet MANETs

Fred/All:
I know this question was addressed at Dave, but for at least proactive
routing issues should addressed with some relationship to architecture.
e.g., stub areas, totally stub areas, NSSA type, transit. So I think you
have to first say what is the deployment scenario. 

For stub or totally stub the border router(s) should proactively inject
a
default route.  This is normal operation for things like MANET-OSPF and
OLSR
types of deployments.  Other cases are more complex. Are there reasons
why
this should be different than normal intra-domain types of approaches?
I
see draft-thaler-autoconf-multisubnet-manets as a valid subcase of what
we
can do. Is there some motivation why there is a difference here in
default
route injection approach?  I guess I am thinking in terms of typical
OSPF
default route handling/deployment use cases.
  
Did you have something in mind or just curious? I think it's a good
question, but I would like to see this discussion be more generally
addressed and am presently hoping we could follow standard best
practices
where it makes sense.  I'd  also like to hear if someone has a reason
why we
should do something different.

-Joe

>-----Original Message-----
>From: Templin, Fred L [mailto:Fred.L.Templin@boeing.com] 
>Sent: Thursday, March 30, 2006 7:59 PM
>To: autoconf@ietf.org
>Cc: dthaler@microsoft.com
>Subject: [Autoconf] Configuring 'default' in Multi-Subnet MANETs
>
>Dave,
>
>I notice that 'draft-thaler-autoconf-multisubnet-manets'
>is silent on the subject of how MANET routers can configure 
>and use a default route. Do you have any thoughts on this?
>
>Fred
>fred.l.templin@boeing.com 
>
>_______________________________________________
>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