IETF Logo Mail Archive

Re: [v6ops] draft-ietf-v6ops-multihoming-without-nat66 WGLC

<teemu.savolainen@nokia.com> Mon, 28 February 2011 20:18 UTC

Return-Path: <teemu.savolainen@nokia.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 04CE13A6C76 for <v6ops@core3.amsl.com>; Mon, 28 Feb 2011 12:18:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.999
X-Spam-Level:
X-Spam-Status: No, score=-2.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_LOW=-1]
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 AzbECI8-mbM7 for <v6ops@core3.amsl.com>; Mon, 28 Feb 2011 12:18:47 -0800 (PST)
Received: from mgw-da01.nokia.com (smtp.nokia.com [147.243.128.24]) by core3.amsl.com (Postfix) with ESMTP id 261023A6C71 for <v6ops@ietf.org>; Mon, 28 Feb 2011 12:18:47 -0800 (PST)
Received: from vaebh102.NOE.Nokia.com (vaebh102.europe.nokia.com [10.160.244.23]) by mgw-da01.nokia.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id p1SKJd4I029480; Mon, 28 Feb 2011 22:19:40 +0200
Received: from smtp.mgd.nokia.com ([65.54.30.7]) by vaebh102.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Mon, 28 Feb 2011 22:19:09 +0200
Received: from 008-AM1MMR1-003.mgdnok.nokia.com (65.54.30.58) by NOK-AM1MHUB-03.mgdnok.nokia.com (65.54.30.7) with Microsoft SMTP Server (TLS) id 8.2.255.0; Mon, 28 Feb 2011 21:19:09 +0100
Received: from 008-AM1MPN1-015.mgdnok.nokia.com ([169.254.5.61]) by 008-AM1MMR1-003.mgdnok.nokia.com ([65.54.30.58]) with mapi id 14.01.0270.002; Mon, 28 Feb 2011 21:19:09 +0100
From: teemu.savolainen@nokia.com
To: joelja@bogus.com, randy@psg.com
Thread-Topic: [v6ops] draft-ietf-v6ops-multihoming-without-nat66 WGLC
Thread-Index: AQHL14LZtS6rDrKywUmdLQdNcrszg5QXWC4g
Date: Mon, 28 Feb 2011 20:19:08 +0000
Message-ID: <056B511A55F8AA42A3E492B7DD19A3193C19A8@008-AM1MPN1-015.mgdnok.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>
In-Reply-To: <4D6C000B.1090704@bogus.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.162.93.108]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 28 Feb 2011 20:19:09.0766 (UTC) FILETIME=[C1D2BE60:01CBD784]
X-Nokia-AV: Clean
Cc: v6ops@ietf.org, v6ops-chairs@tools.ietf.org, ron@bonica.org
Subject: Re: [v6ops] 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:18:48 -0000

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
> >

v2.23.0 | Report a Bug | By Email