IETF Logo Mail Archive

Re: [v6ops] Comments on 464xlat-00

Washam Fan <washam.fan@gmail.com> Fri, 10 February 2012 15:22 UTC

Return-Path: <washam.fan@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 29D6721F841D for <v6ops@ietfa.amsl.com>; Fri, 10 Feb 2012 07:22:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.299
X-Spam-Level:
X-Spam-Status: No, score=-3.299 tagged_above=-999 required=5 tests=[AWL=0.300, BAYES_00=-2.599, 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 MKB384CAdwG5 for <v6ops@ietfa.amsl.com>; Fri, 10 Feb 2012 07:22:43 -0800 (PST)
Received: from mail-wi0-f172.google.com (mail-wi0-f172.google.com [209.85.212.172]) by ietfa.amsl.com (Postfix) with ESMTP id EF10821F86C2 for <v6ops@ietf.org>; Fri, 10 Feb 2012 07:22:40 -0800 (PST)
Received: by wibhm9 with SMTP id hm9so2676512wib.31 for <v6ops@ietf.org>; Fri, 10 Feb 2012 07:22:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=r3zm2AxQ19gcCvYcb3UrjhivkNz2BE1T/yLMq4RbVWg=; b=dJ4jJSpBIQQwDR84VC8Xodydj+JRwiUGAf+Gs0RTFZsuJARrrxN0C+KupaOCZcxipC rEDcReQD1jFrFIEPDrA8uTPYr1iqCbiMFtyUi9p0AZ4Cbc8/TRBS8lg3IAFZuvek2Mlo UnPUSlwpk9fk5Ddmssg3vJa3xvxcWJv1PU010=
MIME-Version: 1.0
Received: by 10.180.82.227 with SMTP id l3mr9994388wiy.1.1328887347604; Fri, 10 Feb 2012 07:22:27 -0800 (PST)
Received: by 10.216.1.6 with HTTP; Fri, 10 Feb 2012 07:22:27 -0800 (PST)
In-Reply-To: <20120210190234kawashimam@mail.jp.nec.com>
References: <CAAuHL_Ct1dsKacABw2Ts8m8Zt8P0c-0SvtXL2TCC95rGLc=OJg@mail.gmail.com> <20120210190234kawashimam@mail.jp.nec.com>
Date: Fri, 10 Feb 2012 23:22:27 +0800
Message-ID: <CAAuHL_ABqoyHNuFKA3xMik7cvU+XiB50+W56+z_MG6RHHvLa-w@mail.gmail.com>
From: Washam Fan <washam.fan@gmail.com>
To: Masanobu Kawashima <kawashimam@vx.jp.nec.com>
Content-Type: text/plain; charset="ISO-8859-1"
Cc: v6ops@ietf.org
Subject: Re: [v6ops] Comments on 464xlat-00
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: Fri, 10 Feb 2012 15:22:44 -0000

Hi,

>>My point was ND can perform even the prefix != 64, cant it? And when
>>you say ND, are you referring to DAD or full functionality of ND?
>
> Would you mind clarifying what you meant by that?
> If CLAT gets a single /64 prefix from WAN interface, it has to perform
> full functionality of ND for 464XLAT IPv6 addresses.

Sorry haven't made clearer. If CLAT gets a prefix length longer or
shorter than /64, should it perform ND for the IPv6 addresses? And
another question, did you mean perform ND at the interface facing the
network under CLAT or at the WAN interface?

Thanks,
washam

v2.23.0 | Report a Bug | By Email