IETF Logo Mail Archive

Re: [Softwires] New Version Notification for draft-fsc-softwire-dhcp4o6-saddr-opt-00.txt

Ted Lemon <ted.lemon@nominum.com> Wed, 02 July 2014 13:31 UTC

Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C657E1A0102 for <softwires@ietfa.amsl.com>; Wed, 2 Jul 2014 06:31:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.551
X-Spam-Level:
X-Spam-Status: No, score=-2.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lG0ope1kgoAg for <softwires@ietfa.amsl.com>; Wed, 2 Jul 2014 06:31:05 -0700 (PDT)
Received: from shell-too.nominum.com (shell-too.nominum.com [64.89.228.229]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8EF1B1A00AD for <softwires@ietf.org>; Wed, 2 Jul 2014 06:31:05 -0700 (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 457141B82FB for <softwires@ietf.org>; Wed, 2 Jul 2014 06:31:05 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id E1671190071; Wed, 2 Jul 2014 06:31:04 -0700 (PDT)
Received: from vpna-196.vpn.nominum.com (64.89.227.196) by CAS-01.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 2 Jul 2014 06:31:04 -0700
Content-Type: text/plain; charset="windows-1252"
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\))
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <53B406F2.5080007@gmail.com>
Date: Wed, 02 Jul 2014 09:30:57 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <5A713E33-1105-4A1C-A44E-0945297796DB@nominum.com>
References: <20140701112428.5519.69335.idtracker@ietfa.amsl.com> <3FA94CC3-983B-4494-B27D-E1FD6EB7CE31@gmail.com> <53B37279.1080001@gmail.com> <5355D29E-2EE7-44BC-BE28-562C21E8E4EA@gmail.com> <53B406F2.5080007@gmail.com>
To: Tom Taylor <tom.taylor.stds@gmail.com>
X-Mailer: Apple Mail (2.1878.2)
X-Originating-IP: [64.89.227.196]
Archived-At: http://mailarchive.ietf.org/arch/msg/softwires/RcrVAEH3Q94CR6FwyK8fkwtq1js
Cc: Softwires WG <softwires@ietf.org>
Subject: Re: [Softwires] New Version Notification for draft-fsc-softwire-dhcp4o6-saddr-opt-00.txt
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires/>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Jul 2014 13:31:10 -0000

On Jul 2, 2014, at 9:19 AM, Tom Taylor <tom.taylor.stds@gmail.com> wrote:
> That doesn't really deal with a change of address at the client. As an example, I'm thinking of a CE that changes its address regularly for privacy reasons. Of course, one answer you may give me is that autonomous address changes by the CE are out of scope or not allowed.

A CE that changes its privacy address regularly can still have a stable address for connections where privacy isn't an issue.   That's the current architecture: that's why we have temporary addresses.   There's no use case for using a temporary address when tunneling IPv4 traffic through your ISP's gateway.

v2.23.0 | Report a Bug | By Email