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

"cb.list6" <cb.list6@gmail.com> Thu, 31 October 2013 14:04 UTC

Return-Path: <cb.list6@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 75F4121F9D3E for <v6ops@ietfa.amsl.com>; Thu, 31 Oct 2013 07:04:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level:
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[AWL=-0.250, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_13=0.6, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X7EXaHEiEn1V for <v6ops@ietfa.amsl.com>; Thu, 31 Oct 2013 07:04:25 -0700 (PDT)
Received: from mail-we0-x231.google.com (mail-we0-x231.google.com [IPv6:2a00:1450:400c:c03::231]) by ietfa.amsl.com (Postfix) with ESMTP id A7B0511E8196 for <v6ops@ietf.org>; Thu, 31 Oct 2013 07:04:21 -0700 (PDT)
Received: by mail-we0-f177.google.com with SMTP id x55so2671494wes.8 for <v6ops@ietf.org>; Thu, 31 Oct 2013 07:04:20 -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; bh=dQX6hwiZRs+4+a12afcnUsVl0Rb0dBjYV/7eJNJj0vc=; b=lDyh1R3lID3L2rfpjMCf+tRiqparRH2OSQGwtlk89Vtq7Nj6sjOKJgD8+FfauTfWv8 1mwZqXoQL48GlLPmj9PbE2t13/eY6BgEVQVVl5lFsp6I3Jzk2BcYkbzitbtmNMRdFgTk +t1624fyrkkV2n0KhziXT/Hsl9DR8UYf/72LdQw2H3tUOeybxxvfOawYB9UtSvOlyqF9 k3QwQSTMwPbKePhgAaS9ZdTiHknu/C5MXlLJqldXheYs98i7iV+/Qh1wPHWTu2nqU6jk yC0/lBzt1te1cArf7YUuLddfr39rPo8aNkrkeULGPeiFUNadnfqZ68+gET2JPv0N/A9m CMig==
MIME-Version: 1.0
X-Received: by 10.180.182.193 with SMTP id eg1mr1648916wic.49.1383228260849; Thu, 31 Oct 2013 07:04:20 -0700 (PDT)
Received: by 10.216.99.68 with HTTP; Thu, 31 Oct 2013 07:04:20 -0700 (PDT)
Received: by 10.216.99.68 with HTTP; Thu, 31 Oct 2013 07:04:20 -0700 (PDT)
In-Reply-To: <97EB7536A2B2C549846804BBF3FD47E1237A6BA2@xmb-aln-x02.cisco.com>
References: <201310111245.r9BCj0319881@ftpeng-update.cisco.com> <97EB7536A2B2C549846804BBF3FD47E1237A6BA2@xmb-aln-x02.cisco.com>
Date: Thu, 31 Oct 2013 07:04:20 -0700
Message-ID: <CAD6AjGTw3+EjdiYYEuMRZEwBV7y8oE5DRDi9cJ41UVFmfbFN-A@mail.gmail.com>
From: "cb.list6" <cb.list6@gmail.com>
To: "Eric Vyncke (evyncke)" <evyncke@cisco.com>
Content-Type: multipart/alternative; boundary=089e016340ce219fa804ea09ed2e
Cc: v6ops@ietf.org, draft-byrne-v6ops-clatip@tools.ietf.org
Subject: Re: [v6ops] new draft: draft-byrne-v6ops-clatip
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: Thu, 31 Oct 2013 14:04:26 -0000

Thanks Eric

On Oct 31, 2013 5:29 AM, "Eric Vyncke (evyncke)" <evyncke@cisco.com> wrote:
>
> Cameron
>
> As you asked for a quick review, here we go :-)
>
> Getting a CLAT prefix from IANA sounds logical for me as we cannot
'steal' a prefix from someone else. This would also allow some IPv4-only
application to detect CLAT (and possibly force the use of IPv6 even if
happy eyeball is not happy).
>

In theory, yes, but 464xlat is only a band-aid for the most archaic apps,
so I find it frustrating if someone tried to modify their app to have logic
to use or not use CLAT instead of enabling ipv6 or generically using HE.
Your line of thinking is correct in practice, I just dont like this certain
reality :)

In any event, the path in the i-d is to generalize the ds-lite range,  such
that in one step an app could know they are not on true dual-stack, they
are on some overlay.

> My concern about re-using the DS-lite prefix is when (if ever) the CLAT
will then go over DS-lite in some weird (home?) network configurations...
This would confuse traceroute and possibly other ICMP mechanisms.
>

The address is never on the wire from CLAT, and that topology should never
occur since both 464xlat emit only ipv6, so there should be no case where
the transition happens twice AND that on-path address responds...

But you made me think about the case of  tracerouting from 464xlat node to
a ds-lite node across the ipv6 internet... And  that b4 does not use the
specific addresses reserved for b4s.  In this case, the b4 can send a icmp
ttl exceeded to the clat, where the clat will see the packet with a
possible same source and destination

> Sharing the DS-lite prefix also prevents a dual-stack measurement apps to
detect whether it uses DS-lite or CLAT for the IPv4 path. About
measurements, it is really easy to detect Teredo & 6to4 but much less 6RD
(if you do not have the IPv4 address). So, 'just for measurements' I would
love to have another prefix for CLAT
>

Another  prefix dedicated for CLAT is an option.  Thanks for the feedback.

> Hope this helps
>
> -éric
>
> > -----Original Message-----
> > From: v6ops-bounces@ietf.org [mailto:v6ops-bounces@ietf.org] On Behalf
Of
> > Fred Baker (fred)
> > Sent: vendredi 11 octobre 2013 14:45
> > To: v6ops@ietf.org
> > Cc: draft-byrne-v6ops-clatip@tools.ietf.org
> > Subject: [v6ops] new draft: draft-byrne-v6ops-clatip
> >
> >
> > A new draft has been posted, at http://tools.ietf.org/html/draft-byrne-
> > 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