Re: [v6ops] draft-ietf-v6ops-64share

Alexandru Petrescu <alexandru.petrescu@gmail.com> Tue, 22 January 2013 08:34 UTC

Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 305B721F84E8 for <v6ops@ietfa.amsl.com>; Tue, 22 Jan 2013 00:34:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.649
X-Spam-Level:
X-Spam-Status: No, score=-9.649 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4eL2cf1XoBFz for <v6ops@ietfa.amsl.com>; Tue, 22 Jan 2013 00:34:45 -0800 (PST)
Received: from sainfoin-out.extra.cea.fr (sainfoin-out.extra.cea.fr [132.167.192.145]) by ietfa.amsl.com (Postfix) with ESMTP id 138D521F8586 for <v6ops@ietf.org>; Tue, 22 Jan 2013 00:34:44 -0800 (PST)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id r0M8Yhxk025087 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <v6ops@ietf.org>; Tue, 22 Jan 2013 09:34:43 +0100
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (8.14.4/8.14.4) with ESMTP id r0M8Yh6B023690 for <v6ops@ietf.org>; Tue, 22 Jan 2013 09:34:43 +0100 (envelope-from alexandru.petrescu@gmail.com)
Received: from [127.0.0.1] (is010446-4.intra.cea.fr [10.8.33.116]) by muguet1.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id r0M8YQfA023166 for <v6ops@ietf.org>; Tue, 22 Jan 2013 09:34:42 +0100
Message-ID: <50FE4F11.3050800@gmail.com>
Date: Tue, 22 Jan 2013 09:34:25 +0100
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: v6ops@ietf.org
References: <CAD6AjGSEOva1RzDXJqmstFk=13JnPUSWM9rQ3PmXCXPQQwcBDQ@mail.gmail.com> <1358681491.98785.YahooMailNeo@web142502.mail.bf1.yahoo.com> <CAD6AjGRFh1ZrnHpFqbaaOWVFQ-L7NHaW1H8PkV==uJVoBqLCZQ@mail.gmail.com>
In-Reply-To: <CAD6AjGRFh1ZrnHpFqbaaOWVFQ-L7NHaW1H8PkV==uJVoBqLCZQ@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 8bit
Subject: Re: [v6ops] draft-ietf-v6ops-64share
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Tue, 22 Jan 2013 08:34:46 -0000

Le 20/01/2013 18:07, Cameron Byrne a écrit :
> Mark,
>
> Just on the this one topic
>
> <Snip>
>
>> Actually, reviewing the IPv6 Addressing Model in RFC4291, it says,
>>
> "An IPv6 unicast address refers to a single interface."
>>
>
> Should we explicitly call it anycast then? Is that worth noting in
> the draft, citing tools.ietf.org/html/rfc4291#section-2.6
> <http://tools.ietf.org/html/rfc4291#section-2.6>

But that sense of anycast has a notion of 'neareast', whereas here
they'd be equally distant (on same computer) and hence the decision to
route it would be guided by an unknown rule.

Instead of calling it anycast, one alternative is to remove it from the
cellular interface (ifconfig del), and then assign it to the WLAN interface.

In this way there would be no worry about same address on two different
interfaces.

Alex

>
> CB
>
>
>
> _______________________________________________ v6ops mailing list
> v6ops@ietf.org https://www.ietf.org/mailman/listinfo/v6ops
>