IETF Logo Mail Archive

Re: [v6ops] draft-binet-v6ops-cellular-host-reqs-rfc3316update

Ted Lemon <Ted.Lemon@nominum.com> Thu, 20 September 2012 15:32 UTC

Return-Path: <Ted.Lemon@nominum.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 3CAFB21F849B for <v6ops@ietfa.amsl.com>; Thu, 20 Sep 2012 08:32:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.435
X-Spam-Level:
X-Spam-Status: No, score=-106.435 tagged_above=-999 required=5 tests=[AWL=-0.063, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_SUB_OBFU_Q1=0.227, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DNH0bDkB7F3j for <v6ops@ietfa.amsl.com>; Thu, 20 Sep 2012 08:32:46 -0700 (PDT)
Received: from exprod7og124.obsmtp.com (exprod7og124.obsmtp.com [64.18.2.26]) by ietfa.amsl.com (Postfix) with ESMTP id A31B121F84A7 for <v6ops@ietf.org>; Thu, 20 Sep 2012 08:32:46 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob124.postini.com ([64.18.6.12]) with SMTP ID DSNKUFs3HhcdTOp7yh4wLIN2iHo0RW2vVshK@postini.com; Thu, 20 Sep 2012 08:32:46 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id B5EC01B829F for <v6ops@ietf.org>; Thu, 20 Sep 2012 08:32:45 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id A5A9019005C; Thu, 20 Sep 2012 08:32:45 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0247.003; Thu, 20 Sep 2012 08:32:45 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: GangChen <phdgang@gmail.com>
Thread-Topic: [v6ops] draft-binet-v6ops-cellular-host-reqs-rfc3316update
Thread-Index: Ac2WZk6bkygjt2tHRWm0TALPSDGcNgAlw55wAB/smYD//5A9Vg==
Date: Thu, 20 Sep 2012 15:32:44 +0000
Message-ID: <91BE181A-163D-43CC-8BDD-49D6E10AE8FF@nominum.com>
References: <94C682931C08B048B7A8645303FDC9F36E5A40D46C@PUEXCB1B.nanterre.francetelecom.fr>, <CAM+vMET-T6Docv1En+GsLJp=t6Dwzu-FKnEdhcYWBVLBu0ue8w@mail.gmail.com>
In-Reply-To: <CAM+vMET-T6Docv1En+GsLJp=t6Dwzu-FKnEdhcYWBVLBu0ue8w@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: IPv6 Ops WG <v6ops@ietf.org>
Subject: Re: [v6ops] draft-binet-v6ops-cellular-host-reqs-rfc3316update
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, 20 Sep 2012 15:32:47 -0000

On Sep 20, 2012, at 11:13 AM, "GangChen" <phdgang@gmail.com> wrote:
> REQ#8: I don't understand the purpose of embed a DNS64 function.
> Especially, the sentence of "This allows to be compatible with DNSSEC"

Because a DNS64 translator has to spoof records in a zone, by definition it's impossible for these spoofed records to be validated. So in order for DNSSEC to function with NAT64, it is required that the resolver on the end device do the DNS64 translation. 

Of course, in order for it to do this, it needs to know the NAT64 prefix...

v2.23.0 | Report a Bug | By Email