IETF Logo Mail Archive

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

Ted Lemon <ted.lemon@nominum.com> Tue, 04 March 2014 09:21 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 46F3A1A0434 for <softwires@ietfa.amsl.com>; Tue, 4 Mar 2014 01:21:11 -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 UOcPNKThAwZ4 for <softwires@ietfa.amsl.com>; Tue, 4 Mar 2014 01:21:09 -0800 (PST)
Received: from shell-too.nominum.com (shell-too.nominum.com [64.89.228.229]) by ietfa.amsl.com (Postfix) with ESMTP id 347201A041C for <softwires@ietf.org>; Tue, 4 Mar 2014 01:21:09 -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 2A2EF1B826F for <softwires@ietf.org>; Tue, 4 Mar 2014 01:21:06 -0800 (PST)
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 09C86190043; Tue, 4 Mar 2014 01:21:06 -0800 (PST)
Received: from nat64.meeting.ietf.org (192.168.1.10) by CAS-01.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 4 Mar 2014 01:21:00 -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: <CAFFjW4jROzB_KEyoE7-8TXF2oqCZ+0f0n5zVzJrw+TOQg8Cxwg@mail.gmail.com>
Date: Tue, 04 Mar 2014 09:20:55 +0000
Content-Transfer-Encoding: quoted-printable
Message-ID: <04B66292-1A04-4DE9-BAE8-C3551FD518BD@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> <AD73A61E-1C8D-4C55-9E24-9CBFC3D44374@nominum.com> <CAFFjW4jCueZSV5PQ=EvgCLugsW15eu669ZHAvstYdX29u5DRJw@mail.gmail.com> <8F3E2C06-4FB4-488D-AC52-FF597060B63D@nominum.com> <CAFFjW4jROzB_KEyoE7-8TXF2oqCZ+0f0n5zVzJrw+TOQg8Cxwg@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/Qwauijnbm-BuD4Ia6hP4SdAVPDs
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: Tue, 04 Mar 2014 09:21:11 -0000

If, as you say, Ian is happy to make the change that you've proposed, then I have no problem with that.   However, let's not needlessly delay both of these drafts arguing about marketing boilerplate.   The text as written is not a sufficiently glowing recommendation of MAP, but it doesn't need to be, for two reasons.   First, this is not a draft about MAP.   Secondly, everybody already knows what they intend to implement anyway, so getting this text exactly perfect will make not one iota of difference in regards to who implements what.

v2.23.0 | Report a Bug | By Email