Re: [mif] #5: only one default route? (there should be multiple, as for MIF WG)
"mif issue tracker" <trac+mif@trac.tools.ietf.org> Thu, 02 August 2012 00:12 UTC
Return-Path: <trac+mif@trac.tools.ietf.org>
X-Original-To: mif@ietfa.amsl.com
Delivered-To: mif@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C1B4021F89AB for <mif@ietfa.amsl.com>; Wed, 1 Aug 2012 17:12:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zqLAJQTQAajT for <mif@ietfa.amsl.com>; Wed, 1 Aug 2012 17:12:28 -0700 (PDT)
Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [77.72.230.30]) by ietfa.amsl.com (Postfix) with ESMTP id 1895D21F8914 for <mif@ietf.org>; Wed, 1 Aug 2012 17:12:28 -0700 (PDT)
Received: from localhost ([127.0.0.1]:39039 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.77) (envelope-from <trac+mif@trac.tools.ietf.org>) id 1Swj1T-0006w8-Gq; Thu, 02 Aug 2012 02:12:15 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: mif issue tracker <trac+mif@trac.tools.ietf.org>
X-Trac-Version: 0.12.2
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.2, by Edgewall Software
To: alexandru.petrescu@gmail.com
X-Trac-Project: mif
Date: Thu, 02 Aug 2012 00:12:15 -0000
X-URL: http://tools.ietf.org/mif/
X-Trac-Ticket-URL: https://trac.tools.ietf.org/wg/mif/trac/ticket/5#comment:10
Message-ID: <081.069e92c6652bc0f78d485c6fff60e47b@trac.tools.ietf.org>
References: <066.e7ab587a28a110b750f149a32ad4c783@trac.tools.ietf.org>
X-Trac-Ticket-ID: 5
In-Reply-To: <066.e7ab587a28a110b750f149a32ad4c783@trac.tools.ietf.org>
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: alexandru.petrescu@gmail.com, mif@ietf.org
X-SA-Exim-Mail-From: trac+mif@trac.tools.ietf.org
X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false
Cc: mif@ietf.org
Subject: Re: [mif] #5: only one default route? (there should be multiple, as for MIF WG)
X-BeenThere: mif@ietf.org
X-Mailman-Version: 2.1.12
List-Id: Multiple Interface Discussion List <mif.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mif>, <mailto:mif-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mif>
List-Post: <mailto:mif@ietf.org>
List-Help: <mailto:mif-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mif>, <mailto:mif-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Aug 2012 00:12:28 -0000
#5: only one default route? (there should be multiple, as for MIF WG) Comment (by alexandru.petrescu@…): I will write this down here so I have a trace. I discussed 1aug2012 with a co-author and there seems to be strong opposition to multiple default routes for the following reasons. If a Host has several interfaces, then on each of these interfaces there would be different responding DHCP Server that would allocate data specific to that interface in particular. It would be not reasonable for a DHCP Server answering to one interface of a Host to offer it configuration information for the other interface. An operator of both WiFi and 3G would deploy a different DHCP Server on each of the access routers of 3G and of WiFi (and would not use same DHCP Server to configure the cellular interface and the WiFi interface of the same Host). If you have two default routes in the same host then how to decide which is _the_ default route? This is bad because it is difficult to decide so. Source-based routing is not good (I forgot why). Alex -- -------------------------------------+--------------------------------- Reporter: alexandru.petrescu@… | Owner: Alexandru Petrescu Type: enhancement | Status: new Priority: minor | Milestone: milestone1 Component: dhcpv6-route-option | Version: Severity: In WG Last Call | Resolution: Keywords: multiple default routes | -------------------------------------+--------------------------------- Ticket URL: <https://trac.tools.ietf.org/wg/mif/trac/ticket/5#comment:10> mif <http://tools.ietf.org/mif/>
- [mif] #5: only one default route? (there should b… mif issue tracker
- Re: [mif] #5: only one default route? (there shou… mif issue tracker
- Re: [mif] #5: only one default route? (there shou… mif issue tracker
- Re: [mif] #5: only one default route? (there shou… mif issue tracker
- Re: [mif] #5: only one default route? (there shou… mif issue tracker
- Re: [mif] #5: only one default route? (there shou… mif issue tracker
- Re: [mif] #5: only one default route? (there shou… mif issue tracker
- Re: [mif] #5: only one default route? (there shou… mif issue tracker
- Re: [mif] #5: only one default route? (there shou… mif issue tracker
- Re: [mif] #5: only one default route? (there shou… mif issue tracker
- Re: [mif] #5: only one default route? (there shou… mif issue tracker