Re: [v6ops] I-D Action: draft-ietf-v6ops-nat64-experience-04.txt

Victor Kuarsingh <victor@jvknet.com> Tue, 05 November 2013 02:40 UTC

Return-Path: <victor@jvknet.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 20E1A21E833F for <v6ops@ietfa.amsl.com>; Mon, 4 Nov 2013 18:40:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[AWL=0.399, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_LOW=-1]
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 RbJ+6JR7yz4V for <v6ops@ietfa.amsl.com>; Mon, 4 Nov 2013 18:39:55 -0800 (PST)
Received: from mail-bk0-f50.google.com (mail-bk0-f50.google.com [209.85.214.50]) by ietfa.amsl.com (Postfix) with ESMTP id 9DEC321E80F1 for <v6ops@ietf.org>; Mon, 4 Nov 2013 18:39:53 -0800 (PST)
Received: by mail-bk0-f50.google.com with SMTP id v4so3346973bkz.9 for <v6ops@ietf.org>; Mon, 04 Nov 2013 18:39:52 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:user-agent:date:subject:from:to:message-id :thread-topic:in-reply-to:mime-version:content-type :content-transfer-encoding; bh=ELIyAq+CWJiTlnKswraxVEEUvnDHlbHa529mRtwcsyU=; b=O0y2M+z8aVo3MzwOlij0dq/NLefHApqXw1Sm8iNHUNsWnyQogpBv+tSP6f+4Pa8n70 SqAiNbC+FSkrwWqyPQqPIzyRWIEOqrQy20TcmPVA2AC/pY5iZI6W0ODHEJje5I1xY6wa NbDcs0uCMQ1+qFM3wt3IpqrY3x5MTWEI99BgSa5VkNEwXEI/cvB153GzRIwGdvqunhkk BJ8N8r+lQznyuZnUYNvrS9quizXG9fQXMuETvmvLFHeAmdJpH9pSfa9uTa7/4AQ/Jjoq FSm1AFgFC0q2vEQSctv9RVO51bariQYwvvk7/P3a6AGObHjSuWFsh5hKYr0kY+YxrZET UtrQ==
X-Gm-Message-State: ALoCoQnZNJF420a2+X7Gg2BqhuZVx2hAYa2GhJG1a/YKc2niaTPESft62lxWiiN89iqOsxXmVQXC
X-Received: by 10.204.226.135 with SMTP id iw7mr11861110bkb.4.1383619192760; Mon, 04 Nov 2013 18:39:52 -0800 (PST)
Received: from [31.133.162.206] (dhcp-a2ce.meeting.ietf.org. [31.133.162.206]) by mx.google.com with ESMTPSA id ny10sm17451130bkb.17.2013.11.04.18.39.51 for <multiple recipients> (version=TLSv1 cipher=RC4-SHA bits=128/128); Mon, 04 Nov 2013 18:39:52 -0800 (PST)
User-Agent: Microsoft-MacOutlook/14.10.0.110310
Date: Mon, 04 Nov 2013 18:39:47 -0800
From: Victor Kuarsingh <victor@jvknet.com>
To: "Eric Vyncke (evyncke)" <evyncke@cisco.com>, "v6ops@ietf.org" <v6ops@ietf.org>
Message-ID: <CE9D989C.5B9A8%victor@jvknet.com>
Thread-Topic: [v6ops] I-D Action: draft-ietf-v6ops-nat64-experience-04.txt
In-Reply-To: <97EB7536A2B2C549846804BBF3FD47E1237E18A6@xmb-aln-x02.cisco.com>
Mime-version: 1.0
Content-type: text/plain; charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable
Subject: Re: [v6ops] I-D Action: draft-ietf-v6ops-nat64-experience-04.txt
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, 05 Nov 2013 02:40:00 -0000

Eric,

On 2013-11-04 6:27 PM, "Eric Vyncke (evyncke)" <evyncke@cisco.com> wrote:

>I have hard time to understand the case described in section 3.1.4
>"co-existence of NAT44 and NAT64". Why would a provider use both at the
>same time? Using NAT44 + native IPv6 is sensible, using IPv6-only + NAT64
>is also valuable but I cannot imagine why NAT44 and NAT64 could be use
>together for the same subscribers.
>
>Thanks for shedding some light for me :-)


That's a good question. I cannot comment on the original intent of this
section, but one use case I can think of is a APN (with associated routing
contexts etc) which may land both IPv4-only, Dual Stack, or IPv6-only PDP
contexts (depending on what the device asks for and/or what is allowed by
network).


In such a case, if using private IPv6 addresses for the UE, it's possible
that you can have this happen.  Perhaps, as long as it does not break
anything, it's ok?

Regards,

Victor K


>
>-éric
>
>> -----Original Message-----
>> From: v6ops-bounces@ietf.org [mailto:v6ops-bounces@ietf.org] On Behalf
>>Of
>> internet-drafts@ietf.org
>> Sent: dimanche 13 octobre 2013 16:00
>> To: i-d-announce@ietf.org
>> Cc: v6ops@ietf.org
>> Subject: [v6ops] I-D Action: draft-ietf-v6ops-nat64-experience-04.txt
>> 
>> 
>> A New Internet-Draft is available from the on-line Internet-Drafts
>> directories.
>>  This draft is a work item of the IPv6 Operations Working Group of the
>> IETF.
>> 
>> 	Title           : NAT64 Operational Experiences
>> 	Author(s)       : Gang Chen
>>                           Zhen Cao
>>                           Chongfeng Xie
>>                           David Binet
>> 	Filename        : draft-ietf-v6ops-nat64-experience-04.txt
>> 	Pages           : 20
>> 	Date            : 2013-10-13
>> 
>> Abstract:
>>    This document summarizes NAT64 function deployment scenarios and
>>    operational experience.  Both NAT64 Carrier Grade NAT (NAT64-CGN) and
>>    NAT64 server Front End (NAT64-FE) are considered in this document.
>> 
>> 
>> The IETF datatracker status page for this draft is:
>> https://datatracker.ietf.org/doc/draft-ietf-v6ops-nat64-experience
>> 
>> There's also a htmlized version available at:
>> http://tools.ietf.org/html/draft-ietf-v6ops-nat64-experience-04
>> 
>> A diff from the previous version is available at:
>> http://www.ietf.org/rfcdiff?url2=draft-ietf-v6ops-nat64-experience-04
>> 
>> 
>> Please note that it may take a couple of minutes from the time of
>> submission until the htmlized version and diff are available at
>> tools.ietf.org.
>> 
>> Internet-Drafts are also available by anonymous FTP at:
>> ftp://ftp.ietf.org/internet-drafts/
>> 
>> _______________________________________________
>> 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