Re: [mif] #5: only one default route? (there should be multiple, as for MIF WG)
"mif issue tracker" <trac+mif@trac.tools.ietf.org> Wed, 01 August 2012 21:21 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 7684B11E8339 for <mif@ietfa.amsl.com>; Wed, 1 Aug 2012 14:21:01 -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 amSxWuKvodoT for <mif@ietfa.amsl.com>; Wed, 1 Aug 2012 14:21:00 -0700 (PDT)
Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [77.72.230.30]) by ietfa.amsl.com (Postfix) with ESMTP id 9F29611E8322 for <mif@ietf.org>; Wed, 1 Aug 2012 14:21:00 -0700 (PDT)
Received: from localhost ([127.0.0.1]:55275 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 1SwgLj-0004aW-9p; Wed, 01 Aug 2012 23:20:59 +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: Wed, 01 Aug 2012 21:20:59 -0000
X-URL: http://tools.ietf.org/mif/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/mif/trac/ticket/5#comment:8
Message-ID: <081.3d9ddf1e98fa03a61d304b3c8c73f26a@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
X-Mailman-Approved-At: Wed, 01 Aug 2012 15:26:40 -0700
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: Wed, 01 Aug 2012 21:21:01 -0000
#5: only one default route? (there should be multiple, as for MIF WG) Comment (by alexandru.petrescu@…): On Wed, Mar 28, 2012 at 00:16, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote: The phrase "more than one default route" on its own makes my head hurt, given the normal meaning in computer science of the word "default". One default route per source prefix in use makes perfect sense, in view of the need for address pair selection and ingress-filtering avoidance. (When I think about it, a default route even makes sense for a ULA prefix.) No, multiple default routes make sense even when they're not source- specific. For example, they make sense when you have two routers and one of them can go down. Remember that a route includes a next-hop, and that RFC 4861 defines a default router list (which is a list of possible next- hops for the default route). _______________________________________________ mif mailing list mif@ietf.org https://www.ietf.org/mailman/listinfo/mif -- -------------------------------------+--------------------------------- 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: <http://trac.tools.ietf.org/wg/mif/trac/ticket/5#comment:8> 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