Re: [Softwires] Unified Softwire CPE: draft-bfmk-softwire-unified-cpe

Maoke <fibrib@gmail.com> Fri, 30 November 2012 02:31 UTC

Return-Path: <fibrib@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 7ACA021F84C6 for <softwires@ietfa.amsl.com>; Thu, 29 Nov 2012 18:31:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level:
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Clzm+8uWTXlE for <softwires@ietfa.amsl.com>; Thu, 29 Nov 2012 18:31:28 -0800 (PST)
Received: from mail-ee0-f44.google.com (mail-ee0-f44.google.com [74.125.83.44]) by ietfa.amsl.com (Postfix) with ESMTP id 25DC821F8457 for <softwires@ietf.org>; Thu, 29 Nov 2012 18:31:27 -0800 (PST)
Received: by mail-ee0-f44.google.com with SMTP id b47so9606243eek.31 for <softwires@ietf.org>; Thu, 29 Nov 2012 18:31:27 -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=bm+LJhWxX/RYbH+99gEhlRPgH2gfwFN4mB/e/5amMvo=; b=a4A4dx1dzCmxOBoUlXqTKbXbH9ahyiGZFdXu2okLzLyqt6WuIWneOKZPrjtmCM7fBC mK3qqXaqJXFsUHsODGokHINTmITtR8Mco0r/DXQUsHE9QAGW56spdIuoXRIVUB5+YSRM eygKWwA+TP0r8+coopCRKjMYUsrckFyEucdte0i2gy1foL8KJCC/TGIw510TJTfNJ89N 6YNs9/AJqvgdLFBLcWg1rjuAP17AUKLNn13trIENeFscGGALEk7hAiQojCYmKaO+zjCn +CmNGw3V3cPDaMIzt1GjCYnMpANVcBLR3+MmCXdjOtlcb/5sK8mkTuacjEejRTbfd5xF x48w==
MIME-Version: 1.0
Received: by 10.14.0.71 with SMTP id 47mr34713530eea.19.1354242687256; Thu, 29 Nov 2012 18:31:27 -0800 (PST)
Received: by 10.223.6.90 with HTTP; Thu, 29 Nov 2012 18:31:27 -0800 (PST)
In-Reply-To: <0wqhvffps96ej8anr48sw25g.1354197525263@email.android.com>
References: <94C682931C08B048B7A8645303FDC9F36E98AB16AD@PUEXCB1B.nanterre.francetelecom.fr> <0wqhvffps96ej8anr48sw25g.1354197525263@email.android.com>
Date: Fri, 30 Nov 2012 11:31:27 +0900
Message-ID: <CAFUBMqUi-8pMvvXf-5-rmqyiQ-2LXcXFciyFUutomNx1fH6=ZQ@mail.gmail.com>
From: Maoke <fibrib@gmail.com>
To: Suresh Krishnan <suresh.krishnan@ericsson.com>
Content-Type: multipart/alternative; boundary="047d7b66f32950481404cfad32b3"
Cc: draft-cui-softwire-b4-translated-ds-lite <draft-cui-softwire-b4-translated-ds-lite@tools.ietf.org>, "draft-ietf-softwire-map@tools.ietf.org" <draft-ietf-softwire-map@tools.ietf.org>, "draft-ietf-softwire-public-4over6@tools.ietf.org" <draft-ietf-softwire-public-4over6@tools.ietf.org>, "softwires@ietf.org" <softwires@ietf.org>, "draft-ietf-softwire-map-dhcp@tools.ietf.org" <draft-ietf-softwire-map-dhcp@tools.ietf.org>
Subject: Re: [Softwires] Unified Softwire CPE: draft-bfmk-softwire-unified-cpe
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: Fri, 30 Nov 2012 02:31:29 -0000

thanks Med for the initialization of the work!

i noticed that:

1. MAP is working in the context of prefix delegation and therefore the LAN
side IPv6 addresses (prefix) is involved in the mapping between the IPv4
and IPv6, while lw4over6 applies the WAN IPv6 address directly. when a
unified CPE is made, the logic of the address assignment to interfaces
should also consider this difference in the behaviour.

2. is the deployment of difference modes able to be overlapped? current
section 4.4 implies the answer is "yes". i agree. but is it the best
behaviour to select one mode at the device-wise according to a certain
preferences? my question is: when the CPE receives multiple
rules/parameter-sets from different sources of provisioning, can it store
and use these pieces of information to adapt packets for corresponding mode
of service, i.e., applying a proper mode on demand and session-specific?

3. related to 2, how can we keep the CPE/BR CPE/AFTR consistency?

4. fragmentation issue is common to all modes and it is also needed to be
clarified/unified for the unified CPE.

only my 2 cents, identifying the problems that i expect this draft to
cover.

- maoke

2012/11/29 Suresh Krishnan <suresh.krishnan@ericsson.com>

> Thanks Med. This is a highly exploratory draft to be used as a strawman to
> determine if an unified CPE is even possible. Please comment on it so that
> we can determine if proceeding in this path is worthwhile. Also, if you are
> interested in being an editor of this draft and are not currently working
> on any of the current solution drafts please contact the chairs.
>
> Thanks
> Suresh
>
>
> ----- Original Message -----
> From: "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>
> To: "draft-ietf-softwire-map@tools.ietf.org" <
> draft-ietf-softwire-map@tools.ietf.org>, "
> draft-ietf-softwire-map-dhcp@tools.ietf.org" <
> draft-ietf-softwire-map-dhcp@tools.ietf.org>, "
> draft-ietf-softwire-public-4over6@tools.ietf.org" <
> draft-ietf-softwire-public-4over6@tools.ietf.org>,
> draft-cui-softwire-b4-translated-ds-lite <
> draft-cui-softwire-b4-translated-ds-lite@tools.ietf.org>, "Reinaldo Penno
>  (repenno)" <repenno@cisco.com>, "softwires@ietf.org" <softwires@ietf.org>
> Sent: 11/29/2012 5:16 AM
> Subject: [Softwires] Unified Softwire CPE: draft-bfmk-softwire-unified-cpe
>
>
>
> Dear all,
>
> As agreed in Atlanta, we prepared an I-D describing a proposed approach
> for the unified CPE.
>
> We hope this version is a good starting point to have fruitful discussion.
>
> Your comments, suggestions and contributions are more than welcome.
>
> Cheers,
> Med
>
>
> -----Message d'origine-----
> De : i-d-announce-bounces@ietf.org [mailto:i-d-announce-bounces@ietf.org]
> De la part de internet-drafts@ietf.org
> Envoyé : jeudi 29 novembre 2012 10:57
> À : i-d-announce@ietf.org
> Objet : I-D Action: draft-bfmk-softwire-unified-cpe-00.txt
>
>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
>
>
>         Title           : Unified Softwire CPE
>         Author(s)       : Mohamed Boucadair
>                           Ian Farrer
>                           Suresh Krishnan
>         Filename        : draft-bfmk-softwire-unified-cpe-00.txt
>         Pages           : 12
>         Date            : 2012-11-29
>
> Abstract:
>    Transporting IPv4 packets over IPv6 is a common solution to the
>    problem of IPv4 service continuity over IPv6-only provider networks.
>    A number of differing functional approaches have been developed for
>    this, each having their own specific characteristics.  As these
>    approaches share a similar functional architecture and use the same
>    data plane mechanisms, this memo describes a specification whereby a
>    single CPE can interwork with all of the standardized and proposed
>    approaches to providing encapsulated IPv4 in IPv6 services.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-bfmk-softwire-unified-cpe
>
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-bfmk-softwire-unified-cpe-00
>
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires
>