IETF Logo Mail Archive

Re: [Softwires] I-D Action: draft-ietf-softwire-lw4over6-06.txt

Ted Lemon <ted.lemon@nominum.com> Mon, 03 March 2014 13:54 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 DB5341A011B for <softwires@ietfa.amsl.com>; Mon, 3 Mar 2014 05:54:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.447
X-Spam-Level:
X-Spam-Status: No, score=-2.447 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.547] 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 KxZu1WzQQkKj for <softwires@ietfa.amsl.com>; Mon, 3 Mar 2014 05:54:52 -0800 (PST)
Received: from shell-too.nominum.com (shell-too.nominum.com [64.89.228.229]) by ietfa.amsl.com (Postfix) with ESMTP id 96A481A012A for <softwires@ietf.org>; Mon, 3 Mar 2014 05:54:52 -0800 (PST)
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 0E5581B82B9 for <softwires@ietf.org>; Mon, 3 Mar 2014 05:54:50 -0800 (PST)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (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 01195190043; Mon, 3 Mar 2014 05:54:50 -0800 (PST)
Received: from nat64.meeting.ietf.org (192.168.1.10) by CAS-02.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 3 Mar 2014 05:54:49 -0800
Content-Type: text/plain; charset="iso-8859-1"
MIME-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <CAFFjW4gyvcBTBDjE8nzGbPz8BcHUasHizzzry0cRF+J2T82uSQ@mail.gmail.com>
Date: Mon, 03 Mar 2014 13:54:45 +0000
Content-Transfer-Encoding: quoted-printable
Message-ID: <AD73A61E-1C8D-4C55-9E24-9CBFC3D44374@nominum.com>
References: <20140211075445.17615.61208.idtracker@ietfa.amsl.com> <FD878467-904B-4441-95B4-11D4461A612E@employees.org> <CF237FDE.AACEB%ian.farrer@telekom.de> <CAFFjW4jOBfvnqCV4UH8qt0HA5zZ-35f+q5ZepzjnwGX5_Oj9Gg@mail.gmail.com> <8A1B81989BCFAE44A22B2B86BF2B76318A2CDB8ED2@HE111643.EMEA1.CDS.T-INTERNAL.COM> <CAFFjW4iP2KqNJFtJPr5rp0tzRwM5TPjaqiSP5r13JqbX46ao7w@mail.gmail.com> <CD1D4FF6-9509-43B4-AFC4-4F1AF99D0C4D@gmx.com> <CAFFjW4ibkj_xpTuXrbYjxkdxD=+qNzapCGPHJwXsZ-k0ZvGg-g@mail.gmail.com> <CF335888.AE89D%ian.farrer@telekom.de> <CAFFjW4hv5WBiqyw9jM+ZoLMGR5k49pjKXG0epnhrsOGoBBKMYA@mail.gmail.com> <CAFFjW4gyvcBTBDjE8nzGbPz8BcHUasHizzzry0cRF+J2T82uSQ@mail.gmail.com>
To: Wojciech Dec <wdec.ietf@gmail.com>
X-Mailer: Apple Mail (2.1874)
X-Originating-IP: [192.168.1.10]
Archived-At: http://mailarchive.ietf.org/arch/msg/softwires/IeQib6OwBMNB2Fkww-siIjnp89s
Cc: Softwires-wg <softwires@ietf.org>
Subject: Re: [Softwires] I-D Action: draft-ietf-softwire-lw4over6-06.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: Mon, 03 Mar 2014 13:54:54 -0000

On Mar 3, 2014, at 1:47 PM, Wojciech Dec <wdec.ietf@gmail.com> wrote:
> Lightweight 4over6 provides a solution for a hub-and-spoke softwire architecture only, 
> where the AFTR maintains (softwire) state for each subscriber. A means for 
> optmizing the amount of such state, as well as the option of meshed IPv4 
> 
> connectivity between subscribers, are features of the [
> I-D.ietf-softwire-map] solution.

This sounds like a marketing change, not an ICMP change.   Can you explain what this has to do with ICMP?

v2.23.0 | Report a Bug | By Email