Re: grow: Re: I-D ACTION:draft-ietf-grow-rfc1519bis-02.txt
Joe Abley <jabley@isc.org> Fri, 17 June 2005 02:05 UTC
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA05093 for <grow-archive@lists.ietf.org>; Thu, 16 Jun 2005 22:05:53 -0400 (EDT)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1]) by darkwing.uoregon.edu (8.13.4/8.13.4) with ESMTP id j5H22Fo0002409; Thu, 16 Jun 2005 19:02:15 -0700 (PDT)
Received: (from majordom@localhost) by darkwing.uoregon.edu (8.13.4/8.13.4/Submit) id j5H22Fgg002407; Thu, 16 Jun 2005 19:02:15 -0700 (PDT)
Received: from felix.automagic.org (felix.hopcount.ca [204.152.186.101]) by darkwing.uoregon.edu (8.13.4/8.13.4) with ESMTP id j5H22EBw002386 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT) for <grow@lists.uoregon.edu>; Thu, 16 Jun 2005 19:02:14 -0700 (PDT)
Received: from [199.212.90.21] (helo=[199.212.90.21]) by felix.automagic.org with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.42 (FreeBSD)) id 1Dj6BM-0005yU-P3; Fri, 17 Jun 2005 02:02:08 +0000
In-Reply-To: <Pine.LNX.4.61.0506161802440.2260@netcore.fi>
References: <200506131937.PAA14655@ietf.org> <Pine.LNX.4.61.0506150826460.18786@netcore.fi> <20050615181544.GA17285@vaf-lnx1.cisco.com> <Pine.LNX.4.61.0506161802440.2260@netcore.fi>
Mime-Version: 1.0 (Apple Message framework v622)
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Message-Id: <2ca393bdc7407f306b782b1d4e6833e8@isc.org>
Content-Transfer-Encoding: 7bit
Cc: Vince Fuller <vaf@cisco.com>, grow@lists.uoregon.edu
From: Joe Abley <jabley@isc.org>
Subject: Re: grow: Re: I-D ACTION:draft-ietf-grow-rfc1519bis-02.txt
Date: Thu, 16 Jun 2005 22:01:32 -0400
To: Pekka Savola <pekkas@netcore.fi>
X-Mailer: Apple Mail (2.622)
Sender: owner-grow@lists.uoregon.edu
Precedence: bulk
Content-Transfer-Encoding: 7bit
On 16 Jun 2005, at 11:31, Pekka Savola wrote: >>> It would be useful to consider to which degree the language of what >>> must be >>> done in multihoming scenarios is needed in this doc, but if it is >>> needed, >>> the tone should possibly be watered down a bit to also address the >>> cornercases like above. >> >> Again, this is current practice for routing-based multihoming in >> IPv4. It >> is also, IMHO, a core requirement of this document to describe how >> CIDR >> works in the presence of such multi-homing and the related issues of >> topological rehoming and renumbering. > > It is _a_ current practice; maybe the most dominant one, but others > provably exist as well. My maint point is to ensure that this > document does not attempt to specify which is the "right" multihoming > method. [...] >> Any modification would be to add a timeframe qualification. It might >> also be >> appropriate to add pointers to other documents that describe other >> multi- >> homing strategies. Can you offer appropriate references? It may be worth reviewing draft-multi6-v4-multihoming-03, which is has been approved for publication and is just waiting for the RFC editor. Joe _________________________________________________________________ web user interface: http://darkwing.uoregon.edu/~llynch/grow.html web archive: http://darkwing.uoregon.edu/~llynch/grow/
- grow: I-D ACTION:draft-ietf-grow-rfc1519bis-02.txt Internet-Drafts
- grow: Re: I-D ACTION:draft-ietf-grow-rfc1519bis-0… Pekka Savola
- Re: grow: Re: I-D ACTION:draft-ietf-grow-rfc1519b… Vince Fuller
- Re: grow: Re: I-D ACTION:draft-ietf-grow-rfc1519b… Pekka Savola
- Re: grow: Re: I-D ACTION:draft-ietf-grow-rfc1519b… Joe Abley