Re: [v6ops] I-D Action: draft-mawatari-v6ops-464xlat-00.txt

"Rajiv Asati (rajiva)" <rajiva@cisco.com> Thu, 26 January 2012 15:50 UTC

Return-Path: <rajiva@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 72A4721F86C2 for <v6ops@ietfa.amsl.com>; Thu, 26 Jan 2012 07:50:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.239
X-Spam-Level:
X-Spam-Status: No, score=-6.239 tagged_above=-999 required=5 tests=[AWL=-0.240, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_MED=-4]
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 OjuN4K360Tsu for <v6ops@ietfa.amsl.com>; Thu, 26 Jan 2012 07:50:30 -0800 (PST)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) by ietfa.amsl.com (Postfix) with ESMTP id 51D6021F8682 for <v6ops@ietf.org>; Thu, 26 Jan 2012 07:50:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=rajiva@cisco.com; l=3244; q=dns/txt; s=iport; t=1327593030; x=1328802630; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=e3Tqe2bDWBABzOBN89OI/fjPuU/aoyz2XprhsFRz3Qw=; b=h6cG51rC34fuyGkqvk7UlYeC/xSanjZbBI4SMq+l/FBNDDCqjkKH389V gkGMkAe8oK4Km+B38jz6AMb1/f/hoTnGw7rlAQKpnNNUGA3lBy3fB//sC Y5eGEIWDd/LtmVOlaCuqfnbgBLL3H0xYspSM6/F8YhanXiP/PZ0H1B4Mt c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAFACl1IU+tJV2c/2dsb2JhbABCrkqBBYFyAQEBBAEBAQ8BFAkKNAsMBAIBCBEBAwEBCwYXAQYBJh8DBggBAQQBEggah2KZNgGeRIkYJjUehEuCWGMEiD+fUA
X-IronPort-AV: E=Sophos;i="4.71,574,1320624000"; d="scan'208";a="54082316"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-7.cisco.com with ESMTP; 26 Jan 2012 15:50:30 +0000
Received: from xbh-rcd-202.cisco.com (xbh-rcd-202.cisco.com [72.163.62.201]) by rcdn-core-5.cisco.com (8.14.3/8.14.3) with ESMTP id q0QFoTGp019992; Thu, 26 Jan 2012 15:50:29 GMT
Received: from xmb-rcd-111.cisco.com ([72.163.62.153]) by xbh-rcd-202.cisco.com with Microsoft SMTPSVC(6.0.3790.4675); Thu, 26 Jan 2012 09:50:29 -0600
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 26 Jan 2012 09:50:29 -0600
Message-ID: <067E6CE33034954AAC05C9EC85E2577C073C54B4@XMB-RCD-111.cisco.com>
In-Reply-To: <20120125022122kawashimam@mail.jp.nec.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [v6ops] I-D Action: draft-mawatari-v6ops-464xlat-00.txt
Thread-Index: AczavN48j/LZ+jCTRJ+mEVcyWd8wGgAxTI9g
References: <4F1E0CEB.2060007@gmail.com> <20120125022122kawashimam@mail.jp.nec.com>
From: "Rajiv Asati (rajiva)" <rajiva@cisco.com>
To: Masanobu Kawashima <kawashimam@vx.jp.nec.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>
X-OriginalArrivalTime: 26 Jan 2012 15:50:29.0741 (UTC) FILETIME=[3AAF21D0:01CCDC42]
Cc: IPv6 Operations <v6ops@ietf.org>
Subject: Re: [v6ops] I-D Action: draft-mawatari-v6ops-464xlat-00.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: Thu, 26 Jan 2012 15:50:31 -0000

Masanobu-san,

This is an interesting discussion and proposal. Few Q --

1. How is IPv4 address getting assigned to the host?
2. Could we not use an existing DHCP option to convey DNS server IPv4
address to the CLAT device, which can convey the DNSv4 address the same
way as IPv4 address is conveyed? If we could, then we would not need DNS
proxy function on CLAT. 
3. Section 7.4 requires CLAT device to have router function. What
happens if it is a typical host device (without any router function)?

~~~~~~~~~
7.4. DNS Proxy Implementation
   If a router implement CLAT function, it performs DNS Proxy for IPv4
   hosts and IPv6 hosts in end-user network.  It MUST provide name
   resolution with IPv6 transport.  It does not need DNS64 [RFC6147]
~~~~~~~~~~~~~~~

4.  In section 8, did you mean to say IPv4 -> IPv6 -> IPv4 translation
below? :-)
~~~~~~~~~~~~
...
   This 464XLAT architecture has two capabilities.  One is a IPv6 ->
   IPv4 -> IPv6 translation for sharing global IPv4 addresses, another
~~~~~~~~~
	
5. Section 7.7 (Auto IPv6 Prefix Assignment) could benefit from some
explicit recommendation (since the current text says source v6 prefix
assignment is done via DHCPv6-PD or another method, and destination IPv6
prefix assignment is via some method).
	
Cheers,
Rajiv


> -----Original Message-----
> From: v6ops-bounces@ietf.org [mailto:v6ops-bounces@ietf.org] On Behalf
Of
> Masanobu Kawashima
> Sent: Tuesday, January 24, 2012 12:21 PM
> To: Brian E Carpenter
> Cc: IPv6 Operations
> Subject: Re: [v6ops] I-D Action: draft-mawatari-v6ops-464xlat-00.txt
> 
> 
> Hi Brian,
> 
> Thank you for your comment.
> 
> I take your point. However, a CLAT can only learn the address of an
IPv6
> DNS recursive server through DHCPv6 (or other way). The CLAT can not
easily
> discover the address of an IPv4 DNS recursive server, and it has to
perform
> all DNS resolution over IPv6.
> 
> The CLAT can pass this IPv6 address to downstream IPv6 hosts, but not
to
> downstream IPv4 hosts. As such, the CLAT should implement a DNS proxy.
> 
> Regards,
> Masanobu
> 
> 
> >> 7.4.  DNS Proxy Implementation
> >>
> >>    If a router implement CLAT function, it performs DNS Proxy for
IPv4
> >>    hosts and IPv6 hosts in end-user network.
> >
> >Why is this necessary? As far as I can see, the client could use any
> >normal DNS server, because the A and AAAA records it needs are
completely
> >standard.
> >
> >Regards
> >   Brian Carpenter
> >
> >_______________________________________________
> >v6ops mailing list
> >v6ops@ietf.org
> >https://www.ietf.org/mailman/listinfo/v6ops
> 
> ========================================
>  NEC AccessTechnica, Ltd.
>  Product Development Department
>  Masanobu Kawashima
>  kawashimam@vx.jp.nec.com
>  http://www.necat.co.jp/
> ========================================
> 
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops