Re: [v6ops] new draft: draft-ietf-v6ops-clatip

Ca By <cb.list6@gmail.com> Wed, 14 May 2014 16:12 UTC

Return-Path: <cb.list6@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 501B01A0133 for <v6ops@ietfa.amsl.com>; Wed, 14 May 2014 09:12:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.75
X-Spam-Level:
X-Spam-Status: No, score=-1.75 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id v07XC3Sbf-_u for <v6ops@ietfa.amsl.com>; Wed, 14 May 2014 09:12:16 -0700 (PDT)
Received: from mail-wg0-x22b.google.com (mail-wg0-x22b.google.com [IPv6:2a00:1450:400c:c00::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 239CE1A029F for <v6ops@ietf.org>; Wed, 14 May 2014 09:12:15 -0700 (PDT)
Received: by mail-wg0-f43.google.com with SMTP id l18so2163807wgh.14 for <v6ops@ietf.org>; Wed, 14 May 2014 09:12:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=1hG1jrF72rfvNMXGKK4Wqb0DXPwlYO8qqP2lXwbH+SM=; b=GEogyz/W91cIVUlAvI3v0Ie9D5j+NYCromsZ19kzJVkjuwxHI5QITnca5q94qrgqrE K2yvc3otEc7thPBaxfBeJ4gOvbgkqEaThdEQUwq8b4EjE/XsdoHj+JdbxqT3vlV+cdHn 2LLnLIp1ZPuI13nPWoySVKv4RJ3uVecPhez8ocESMU2D+mIHlCpYpKdfJ6v6CAQCpUTF S7Y7ghVPMRIS3hl0SKWhhvqrlz/R+a8PGWFyhKXIeN5oKDx8HEZeewFuoN5GIEFnkNNa OFnTw2P5EYTDEkPpY9ptTcK13ShS+XzbpcMfv9gI3MBH0pvcuV8z0GSTl2LOa2Yk0R5x hagw==
MIME-Version: 1.0
X-Received: by 10.194.91.175 with SMTP id cf15mr3924028wjb.5.1400083928960; Wed, 14 May 2014 09:12:08 -0700 (PDT)
Received: by 10.217.61.198 with HTTP; Wed, 14 May 2014 09:12:08 -0700 (PDT)
In-Reply-To: <5373082E.5040007@gmail.com>
References: <201405061245.s46CjNEi013073@irp-view13.cisco.com> <5373082E.5040007@gmail.com>
Date: Wed, 14 May 2014 09:12:08 -0700
Message-ID: <CAD6AjGS=WtFA6yDG=2-c_-OCkwUK_X-K_LVOJB7vggnYDe_D7A@mail.gmail.com>
From: Ca By <cb.list6@gmail.com>
To: Alejandro Acosta <alejandroacostaalamo@gmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/_1_S87kVAHH8G1EsdPPw2NbuhVk
Cc: IPv6 Ops WG <v6ops@ietf.org>
Subject: Re: [v6ops] new draft: draft-ietf-v6ops-clatip
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.15
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: Wed, 14 May 2014 16:12:22 -0000

On Tue, May 13, 2014 at 11:07 PM, Alejandro Acosta
<alejandroacostaalamo@gmail.com> wrote:
> Hi,
>  Sorry if this question have been done before (and I guess it have been).
>  I'm know this kind of mechanism are oriented to simple devices such
> smartphones, but anyway I wonder how the prefix 192.0.0.0/29 is handle
> in a device with more than one interface.
>
>  I read in section three you mention:
>
> "   ..... It is important
>    that a host never be deployed with 2 active IPv4 continuity solutions
>    simultaneously in a way that would cause a node to have overlapping
>    address from 192.0.0.0/29."
>
>  Can I subnet this prefix in two /30 and then there won't be
> overlapping?, should I assign one /29 and then I can not used
> ds-lite/464xlat in the next interface (this is what I understand from
> the text above).
>
> Thanks,
>

Hi Alejandro,

Thanks for taking the time to read the I-D.  The goal of the I-D is
lift restrictions.  David Thaler suggested that since the 192.0.0.0/29
has fewer restriction on its use, it is possible for solutions to
overlap and cause problems on a host that has both solutions.  For
example, if a host has both a DS-lite and 464XLAT capability, and both
are active at the same time and both are assuming the full
192.0.0.0/29 can be used, this will cause a problem since the host
will have 2 connected routes to the same place.

To avoid this scenario of overlapping space (in the unlikely event a
host has 2 active IPv6 transition scenarios), the text you quoted was
added.  The text simply says "be smart" ... don't use overlapping
addresses on a host and cause yourself a problem.

That said, i find it perfectly reasonable, as you suggest, to take the
192.0.0.0/29 and create 2 /30s, 1 for DS-lite and the other for
464XLAT... if you must have this ability.  The common Android solution
for this is to just use 192.0.0.4/32, only 1 IPv4 address is needed
for 464XLAT to function on Android

https://android.googlesource.com/platform/external/android-clat/+/master/clatd.conf



>
> El 5/6/2014 8:15 AM, Fred Baker escribiรณ:
>>
>> A new draft has been posted, at http://tools.ietf.org/html/draft-ietf-v6ops-clatip. Please take a look at it and comment.
>>
>> _______________________________________________
>> 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