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

"Eric Vyncke (evyncke)" <evyncke@cisco.com> Thu, 31 October 2013 12:29 UTC

Return-Path: <evyncke@cisco.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 3858921F9E54 for <v6ops@ietfa.amsl.com>; Thu, 31 Oct 2013 05:29:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.074
X-Spam-Level:
X-Spam-Status: No, score=-10.074 tagged_above=-999 required=5 tests=[AWL=-0.075, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_HI=-8]
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 mkTtKntXHI1o for <v6ops@ietfa.amsl.com>; Thu, 31 Oct 2013 05:29:10 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) by ietfa.amsl.com (Postfix) with ESMTP id D39DC21F9E91 for <v6ops@ietf.org>; Thu, 31 Oct 2013 05:29:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1477; q=dns/txt; s=iport; t=1383222550; x=1384432150; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=HtGtMusMTpzTboiyXU8HMkX0Ksuc3gtcxT7LrgQ7BMo=; b=O7NHeYebK31ne/gSNYb/j7Oyy2CSUzoT+KFw+BXHeaFW1pSKxHTTc8/l bT3ZrSuWvMJHpdrN8gZf62vV80Im8GMCcaBHHhIizXn1lITJnnDK7bw04 oQHOX26Yo7/CaDzG4FIUB+F5W646TL53F6P4EFdoXidraR5cxXDrK2Ghl M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AlQGALRMclKtJXHA/2dsb2JhbABZgwc4VL9qgSQWbQeCJQEBAQQBAQFrCwwEAgEIEQQBAQsdBycLFAkIAgQOBQiHfw28Fo8eMQcGgxqBDgOJCJAykFqDJoIq
X-IronPort-AV: E=Sophos;i="4.93,608,1378857600"; d="scan'208";a="278920534"
Received: from rcdn-core2-5.cisco.com ([173.37.113.192]) by rcdn-iport-2.cisco.com with ESMTP; 31 Oct 2013 12:29:09 +0000
Received: from xhc-aln-x09.cisco.com (xhc-aln-x09.cisco.com [173.36.12.83]) by rcdn-core2-5.cisco.com (8.14.5/8.14.5) with ESMTP id r9VCT9AR003431 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 31 Oct 2013 12:29:09 GMT
Received: from xmb-aln-x02.cisco.com ([169.254.5.143]) by xhc-aln-x09.cisco.com ([173.36.12.83]) with mapi id 14.02.0318.004; Thu, 31 Oct 2013 07:29:09 -0500
From: "Eric Vyncke (evyncke)" <evyncke@cisco.com>
To: "v6ops@ietf.org" <v6ops@ietf.org>
Thread-Topic: [v6ops] new draft: draft-byrne-v6ops-clatip
Thread-Index: AQHOxn/MbNcUnb4RF06iE7HhtcnLUZoO2R8Q
Date: Thu, 31 Oct 2013 12:29:08 +0000
Message-ID: <97EB7536A2B2C549846804BBF3FD47E1237A6BA2@xmb-aln-x02.cisco.com>
References: <201310111245.r9BCj0319881@ftpeng-update.cisco.com>
In-Reply-To: <201310111245.r9BCj0319881@ftpeng-update.cisco.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.82.237.195]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "draft-byrne-v6ops-clatip@tools.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 12:29:15 -0000

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

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.

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

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