IETF Logo Mail Archive

[v6ops] Er, we had this converstaion before [draft-ietf-v6ops-multihoming-without-nat66 WGLC]

Brian E Carpenter <brian.e.carpenter@gmail.com> Mon, 28 February 2011 20:54 UTC

Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EFD0E3A6C7D for <v6ops@core3.amsl.com>; Mon, 28 Feb 2011 12:54:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.159
X-Spam-Level:
X-Spam-Status: No, score=-103.159 tagged_above=-999 required=5 tests=[AWL=-0.160, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kPlmccHMBVbz for <v6ops@core3.amsl.com>; Mon, 28 Feb 2011 12:54:16 -0800 (PST)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by core3.amsl.com (Postfix) with ESMTP id C406F3A6C58 for <v6ops@ietf.org>; Mon, 28 Feb 2011 12:54:15 -0800 (PST)
Received: by fxm15 with SMTP id 15so4227599fxm.31 for <v6ops@ietf.org>; Mon, 28 Feb 2011 12:55:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=LFmFoDXCo+pR9Q0x+mGddio8selY2/kMWcEhIgIQq/4=; b=R0d5jPWONj268bSzn6mACFIzyn2ZeqOKJ6feljb2zfQwTVUDU6A/jdu2cqhMOZz2QV wNEth1G0+Fy97HM4FP2qR3EN3ssNMvr8326vd94ZA9JWCDuGcq5uuzOE8TnZPa66A01z 3zjn5L8z/UUp55PwX/F8HHCJAQyfzL2QvVeYc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=ti4I+hevfarbGlB8+hlEpeMA1EsX1i6dne90VTuM5KdwjRn/fK+uNGRTXUBvxQH+rg ohOSOonmfQAlS/hW2w7m2ZLk070i8MeHfsZwUUWYOkkKBcCaoW9w1Pb0awyP/GDzRQzB u2xvBi7gad2cI86P6hbBWRDS8X4vyAKIk6rQQ=
Received: by 10.223.104.147 with SMTP id p19mr6832533fao.6.1298926515360; Mon, 28 Feb 2011 12:55:15 -0800 (PST)
Received: from [130.216.38.124] (stf-brian.sfac.auckland.ac.nz [130.216.38.124]) by mx.google.com with ESMTPS id b7sm1796768faa.42.2011.02.28.12.55.10 (version=SSLv3 cipher=OTHER); Mon, 28 Feb 2011 12:55:14 -0800 (PST)
Message-ID: <4D6C0BAC.1040505@gmail.com>
Date: Tue, 01 Mar 2011 09:55:08 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: teemu.savolainen@nokia.com
References: <0E87AEAD-8476-499E-8946-C8E31D2E21E9@cisco.com> <m262s4poz2.wl%randy@psg.com> <056B511A55F8AA42A3E492B7DD19A3193C14BB@008-AM1MPN1-015.mgdnok.nokia.com> <m262s4cp4n.wl%randy@psg.com> <4D6C000B.1090704@bogus.com> <056B511A55F8AA42A3E492B7DD19A3193C19A8@008-AM1MPN1-015.mgdnok.nokia.com>
In-Reply-To: <056B511A55F8AA42A3E492B7DD19A3193C19A8@008-AM1MPN1-015.mgdnok.nokia.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Cc: v6ops@ietf.org, v6ops-chairs@tools.ietf.org, ron@bonica.org
Subject: [v6ops] Er, we had this converstaion before [draft-ietf-v6ops-multihoming-without-nat66 WGLC]
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Feb 2011 20:54:18 -0000

I politely suggest that people re-read RFC 4116 and RFC 3582.

And if you really want to avoid repeating several years of
discussion, see the other RFCs listed at
http://www.ietf.org/wg/concluded/multi6.html
and the WG archive at https://ops.ietf.org/lists/multi6/

Multihoming is generic. BGP-4 based multihoming is one solution.
Multi-address based multihoming is a fundamental design property
of IPv6 (and it does not require multiple interfaces, so
MIF is a somewhat different problem).

Regards
   Brian

On 2011-03-01 09:19, teemu.savolainen@nokia.com wrote:
> I don't really agree. 
> 
> For what I know multihoming is very commonly used to describe a scenario where a host has simultaneously multiple uplink ISP connections active. 
> 
> MEXT uses that in this context in RFC6089.
> 
> HIP uses that in this context in RFC5021.
> 
> MOBIKE uses that in this context in RFC4555.
> 
> NETLMM uses that in this context in RFC5213.
> 
> And I bet there are quite many other RFCs as well. Hence the train to call it something else went already. 
> 
> I don't know BGP very well, but doesn't this "BGP routing with multiple peers" sound like being "multihomed" as well, but there just happens to be BGP being used?
> 
> 
> Best regards,
> 
> 	Teemu
> 
>> -----Original Message-----
>> From: ext Joel Jaeggli [mailto:joelja@bogus.com]
>> Sent: 28. helmikuuta 2011 22:06
>> To: Randy Bush
>> Cc: Savolainen Teemu (Nokia-MS/Tampere); v6ops@ietf.org; v6ops-
>> chairs@tools.ietf.org; ron@bonica.org
>> Subject: Re: [v6ops] draft-ietf-v6ops-multihoming-without-nat66 WGLC
>>
>> On 2/28/11 4:36 AM, Randy Bush wrote:
>>> uh oh!  i think i get it.  this is trying to give a new meaning to the
>>> word 'multi-homing' which has been in wide use for a few decades.  it
>>> means bgp routing with multiple peers (a punny word meaning both any
>>> arbitrary bgp neighbor and alternatively one where you only exchange
>>> your customers' routes).
>>>
>>> can we please use a new, or at least different, word here?
>> Theoretically the MIF working-group should be working on that definition
>> if I correctly understand their charter.
>>
>>> randy
>>> _______________________________________________
>>> v6ops mailing list
>>> v6ops@ietf.org
>>> https://www.ietf.org/mailman/listinfo/v6ops
>>>
> 
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>

v2.23.0 | Report a Bug | By Email