Re: [Softwires] MAP compatibility with DS-Lite

Wojciech Dec <wdec.ietf@gmail.com> Wed, 27 November 2013 20:15 UTC

Return-Path: <wdec.ietf@gmail.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 E83981AE29C for <softwires@ietfa.amsl.com>; Wed, 27 Nov 2013 12:15:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.399
X-Spam-Level:
X-Spam-Status: No, score=-1.399 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, J_CHICKENPOX_18=0.6, SPF_PASS=-0.001] autolearn=no
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 OfAa8duF-hqW for <softwires@ietfa.amsl.com>; Wed, 27 Nov 2013 12:15:49 -0800 (PST)
Received: from mail-pb0-x230.google.com (mail-pb0-x230.google.com [IPv6:2607:f8b0:400e:c01::230]) by ietfa.amsl.com (Postfix) with ESMTP id BF9DD1AE172 for <softwires@ietf.org>; Wed, 27 Nov 2013 12:10:38 -0800 (PST)
Received: by mail-pb0-f48.google.com with SMTP id md12so11108665pbc.35 for <softwires@ietf.org>; Wed, 27 Nov 2013 12:10:38 -0800 (PST)
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=s7ch7wY0jt8q+0KlJzgTq5rf+2iUGKSEENr/Bxe9Z1U=; b=X9Qp7PwY1yvxN/pKB9RenVsgv2mugzPRtDW6g9UPQZaA3+na7A3LDsstUgi/yv49Hf PBK56F89Vpi7iQFtIwomXPA0O4iMWAYABKZKOueW65+mZVHPm2Fpd+A0z6Cbm7MEH75a mONT+ui/9ub9znx9CuUEkrECBiE3VmIdpcU3yMZ1eL9PMp45+EOBI/kEk31QPMzFxKLu shWrXrKSX6vLLxlOEAuKGqtqpe2BcaZv/X3/jixV6fNEQB0r+m61wEkAVDR6PlNUVoHK 24Fw842+DLfWevbuaqyd5yexGEGXIWi1dww1Q86ntVomHzLScSEnmQaoxgF/OOJieU8g 4qnQ==
MIME-Version: 1.0
X-Received: by 10.66.145.40 with SMTP id sr8mr43711453pab.60.1385583038265; Wed, 27 Nov 2013 12:10:38 -0800 (PST)
Received: by 10.70.57.163 with HTTP; Wed, 27 Nov 2013 12:10:38 -0800 (PST)
In-Reply-To: <6275CE5E-E0AD-4C0F-8661-443785C966DF@employees.org>
References: <528D136C.60803@viagenie.ca> <CAFFjW4i7u0UQ7=oSJovwFBZeNr_VdJtTzOnTwZtuKz=f0VnDGQ@mail.gmail.com> <528F6C88.1060508@viagenie.ca> <CAFFjW4jwf_t_8xOChYotyx+pxRAE-tZ5_=ASB772fPS44tO__A@mail.gmail.com> <CB352C8B-60E9-49BB-9DCE-62A4CDEAD7C3@employees.org> <CAFFjW4gjqh36nPZXNitMrJooOksdq99-c4NR-CZkipZ2Dcomzw@mail.gmail.com> <6275CE5E-E0AD-4C0F-8661-443785C966DF@employees.org>
Date: Wed, 27 Nov 2013 21:10:38 +0100
Message-ID: <CAFFjW4jn3gYO-NOwmGwL7FSg7A3SePVDccDYrnawouNi5sWtKw@mail.gmail.com>
From: Wojciech Dec <wdec.ietf@gmail.com>
To: Ole Troan <otroan@employees.org>
Content-Type: multipart/alternative; boundary="047d7b6da6f2cd7fc104ec2e3092"
Cc: "softwires@ietf.org" <softwires@ietf.org>
Subject: Re: [Softwires] MAP compatibility with DS-Lite
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, 27 Nov 2013 20:15:51 -0000

Now, how about this to move things forward: We replace the quoted
text/section with the following added into section 5.4

"A MAP-E CE provisioned with only the IPv6 address of the BR MUST
   disable its NAT44 functionality and treat the point-point tunnel
interface as active for IPv4 forwarding."

In case we want to proceed with the argument, it is continued inline...

On 25 November 2013 13:39, Ole Troan <otroan@employees.org> wrote:

> Wojciech,
>
> > You're apparently missing some key points:
>
> that's not uncommon. ;-)
>
> > 1.  It's a functional requirement of a CPE, specifying how the CPE
> behaves with a case of NOT having an IPv4 address. What is the to be the
> bahviour of a MAP CPE without one?
>
> just like if it didn't get an IPv4 address on native Ethernet.
>

Now, the way MAP's forwarding rules have been modelled, the IPv4 default
route follows the IPv6 BR address. Hence, the presence of the IPv6 address
equates to the presence of a v4 default route, accessible via the tunnel to
the BR. In none of the v4 auto tunneling technology in use here is it a
requirement for the tunneling router to have some operator assigned IPv4
address on an interface to be able to forward packets on it.



>
> > 2.  This is NOT about configuring a ds-lite CPE
>
> my understanding was that the CPE had to be provisioned for this mode,
> possibly as a separate MAP domain. and that the BR must also act as a CGN.
>

One doesn't need a DS-Lite CPE to be able to send IPv4inIPv6.

>
> > Throughout, its still not been answered what is the downside of having
> this functionality of a *MAP CPE*?
>
> it adds yet another variant.
> what's wrong with provisioning the DS-lite option when you want this
> behaviour?
>

Is DS-Lite required to configure a MAP CPE, or to enable IPv4inIPv6 on a
router?


> or if you want overflow from MAP to DS-lite?
>

I didn't bring up overflow - not sure why you added it.


>
> I don't get the benefit of what you are suggesting.
>

Clearly, but there are multiple as mentioned (not least, the ability for
the operator to actually turn off NAT44  on the user's CPE for t'shooting
purposes).

Cheers,
Wojciech.


> cheers,
> Ole
>