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 07:37 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 E6D1721F857D for <softwires@ietfa.amsl.com>; Tue, 26 Jun 2012 00:37:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.38
X-Spam-Level:
X-Spam-Status: No, score=-3.38 tagged_above=-999 required=5 tests=[AWL=-0.082, 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 SoV5Xd98gEuK for <softwires@ietfa.amsl.com>; Tue, 26 Jun 2012 00:37:13 -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 B1A8621F8534 for <softwires@ietf.org>; Tue, 26 Jun 2012 00:37:13 -0700 (PDT)
Received: by qcmt36 with SMTP id t36so2694712qcm.15 for <softwires@ietf.org>; Tue, 26 Jun 2012 00:37:13 -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=5XN1aKn23RyGTmWktKFxrQm+/vwIhDeTE77rKl9yUQk=; b=GT5gpj1zXBfxMsyXyGeJvUbNksCEefdgbK1vXUiWjYO3lJJ8JC8vBVe9PMsf94wm41 q4JKrxKOQDb1dEJhMtXyMlyBAUOw0vlWBc2tKnprt02dwS0P2e51SwrHmLc95Xa5J3CO cY4nJPD/dD8Ne8zQyhl5UwYZcE88vdegaxX2wIYFXPq0X9aHP/yBl31EpSGF8yNXAqlX 6MGpggaZ7A5gVxJUNRucr+OPNT2qLDmyrxkJMiOeQw8a6FQNIBFRASh4xtRydcLKRPsN A2047uNKbTK4x0kHyycs6VF4EyAiH1d6sVJBclTTo+0Jg8JLQPDWMRha8GYGlUxEPthf 39cA==
MIME-Version: 1.0
Received: by 10.224.207.138 with SMTP id fy10mr24087907qab.85.1340696233099; Tue, 26 Jun 2012 00:37:13 -0700 (PDT)
Received: by 10.229.127.231 with HTTP; Tue, 26 Jun 2012 00:37:12 -0700 (PDT)
In-Reply-To: <E367C4D7-CB99-45C5-939D-584EB75DD0EB@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> <CAFFjW4iM7SR8=L4jsWiqNnb54-cG-qwcdaJ7OVtNT4aK4vmLQw@mail.gmail.com> <E367C4D7-CB99-45C5-939D-584EB75DD0EB@laposte.net>
Date: Tue, 26 Jun 2012 09:37:12 +0200
Message-ID: <CAFFjW4hz7fJtHM3kFcfwdi6LXkJ-v4iv1inOL6_RXTads6vC6w@mail.gmail.com>
From: Wojciech Dec <wdec.ietf@gmail.com>
To: Rémi Després <despres.remi@laposte.net>
Content-Type: multipart/alternative; boundary="20cf300facd7b9c04504c35b2a63"
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 07:37:18 -0000

On 26 June 2012 09:13, Rémi Després <despres.remi@laposte.net> wrote:

>
> Le 2012-06-26 à 08:04, Wojciech Dec a écrit :
>
>
>
> 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).
>
>
> Could you please indicate which one?
>
>
>
>> 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.
>
>
> In Section 5, "Forwarding mode" has become a BMR 5th parameter.
> In Section 5 of the mdt draft of january 30, there were only 4 BMR
> parameter.
>
> Anything missed?
>

Ok, so fair point. MAP-E and -T have been merged in the draft, based on
previous feedback from the WG incl discussions at the last meeting. We
thought having less drafts is more as was discussed at the last meeting.
The updated draft also highlights how much commonality there is.
We're welcome to suggestions on how to provide information on which
transport mode to use, or if the merger is no desired.


>
> - 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."
>>
>
> Is there such an equivalent?
> Please answer (not answering the question isn't a way to eliminate it).
>

Equivalent of what?
Note: I asked you how you would propose dealing with the DMR but no BMR
corner case, and await your proposal..

-Woj.

>
> 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.
>
>
> In their implementation, maybe, but we talk about the specification.
>
> RD
>
>
>
> -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
>>
>>
>
>