Re: [Softwires] [Softwire] draft-ietf-softwire-map-00 does NOT reflect the consensus from the WG

Wojciech Dec <wdec.ietf@gmail.com> Tue, 26 June 2012 06:04 UTC

Return-Path: <wdec.ietf@gmail.com>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BC2D221F8550 for <softwires@ietfa.amsl.com>; Mon, 25 Jun 2012 23:04:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.381
X-Spam-Level:
X-Spam-Status: No, score=-3.381 tagged_above=-999 required=5 tests=[AWL=-0.083, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, 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 dfZsoUKRSGOo for <softwires@ietfa.amsl.com>; Mon, 25 Jun 2012 23:04:07 -0700 (PDT)
Received: from mail-qc0-f170.google.com (mail-qc0-f170.google.com [209.85.216.170]) by ietfa.amsl.com (Postfix) with ESMTP id DA2EB21F8549 for <softwires@ietf.org>; Mon, 25 Jun 2012 23:04:06 -0700 (PDT)
Received: by qcmt36 with SMTP id t36so2666334qcm.15 for <softwires@ietf.org>; Mon, 25 Jun 2012 23:04:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=sjs8oMuQRt+QWALkaJVuOnTOv9lBg3FWJFDvdIWFhpA=; b=nw2JeipQM8rO5Jhw1LyK+Oc55LAzjVX1cn7tQHNTI/uRFWbyozHI3UfytTz97wT2oL pttWmd/NFxHn8QMgTYpehu8jo+ZlA5CdgRe3kLDyzPGmCDJfRt4KZkeWgfLgOshdBKoe uClHR+XS2N9Jlp3f8Bvi2Iuxdb5wiap0OVEz35eaGF8N6M66tQghgUiTqF1PwPtP+y3Y RuEVhj2wWoenZ2OCYrnFQ9F3hrA3ebVcZbluaJ4UUvDMEWsLtba38e+xx64eZ6ZO+MzO FUN2DaBWrtyH5Sbp5xX2LfxJYFezDByeCMoJX58E/bMxJ8EH+ZOCa61OhmNIZGPYt8pE m08A==
MIME-Version: 1.0
Received: by 10.224.201.136 with SMTP id fa8mr23876872qab.20.1340690646100; Mon, 25 Jun 2012 23:04:06 -0700 (PDT)
Received: by 10.229.127.231 with HTTP; Mon, 25 Jun 2012 23:04:05 -0700 (PDT)
In-Reply-To: <D99284BB-5240-463F-B73F-2B5DA6AEA9A1@laposte.net>
References: <CC0CC5BF.226A9%yiu_lee@cable.comcast.com> <10CE32B3-7DFB-47F4-85F1-F591C613689A@gmail.com> <2012062514514640804415@gmail.com> <CAFFjW4iouz0HGgV8xqm58UYUYKErJkLvn=xK2VkLNuRpZtHH-A@mail.gmail.com> <D99284BB-5240-463F-B73F-2B5DA6AEA9A1@laposte.net>
Date: Tue, 26 Jun 2012 08:04:05 +0200
Message-ID: <CAFFjW4iM7SR8=L4jsWiqNnb54-cG-qwcdaJ7OVtNT4aK4vmLQw@mail.gmail.com>
From: Wojciech Dec <wdec.ietf@gmail.com>
To: Rémi Després <despres.remi@laposte.net>
Content-Type: multipart/alternative; boundary="20cf300fafe5b6ead804c359dd6b"
Cc: softwires WG <softwires@ietf.org>, Yong Cui <cuiyong@gmail.com>
Subject: Re: [Softwires] [Softwire] draft-ietf-softwire-map-00 does NOT reflect the consensus from the WG
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.12
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, 26 Jun 2012 06:04:07 -0000

On 25 June 2012 17:28, Rémi Després <despres.remi@laposte.net> wrote:

>
> 2012-06-25 à 16:24, Wojciech Dec:
> ...
> > The updated MAP draft does not change the MAP architecture nor its
> technical underpinnings. In fact there are no changes, bar editorial to the
> normative parts of MAP,
>
> Having asked several times for a list of substantial evolutions from
> previous MAP drafts, with their justifications, and having received no
> answer, I see this statement as an indirect but first answer.
>

Woj> You were provided with an answer (pls see Ole's mail).

>
> But it doesn't seem acceptable (*):
> - AFAIK, the added 5th parameter of basic mapping rules is more than
> editorial
>

Woj> Please indicate what the new parameter in your opinion is.

- I didn't find the equivalent of the following sentence in previous
> drafts: "A MAP-E CE provisioned with only a Default Mapping Rule, as in the
> 1:1 case, and with no IPv4 address and port range configured by other
>  means, MUST disable its NAT44 functionality."
>

Woj> Well, perhaps you would like to suggest what the CPE should do in the
case the CPE is issued with a default mapping rule, ie a default route in
map terms, and the absence of an assigned IPv4 address or other parameters
(BMR). The above appears to be reasonable behaviour.

>
> => A carefully studied list of substantial changes MAP supporters have
> found appropriate after the Paris meeting remains to be due.
>

Woj> Take it from the other people who have done implementations,
technically there are no changes.

-Woj.


>
> > something that is proven by existing implementations prior to this draft
> supporting the current draft.
>
> Please understand that your stating that some tests (for which we don't
> have detailed reports) should be considered a proof that what you say is
> true, is difficult to accept.
> Especially if what you say seems contradicted by a verifiable fact (see
> (*) above).
>
> RD
>
>