Re: [Softwires] I-D Action: draft-ietf-softwire-map-08.txt

<mohamed.boucadair@orange.com> Tue, 13 August 2013 12:12 UTC

Return-Path: <mohamed.boucadair@orange.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 31A9421E80AE for <softwires@ietfa.amsl.com>; Tue, 13 Aug 2013 05:12:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.188
X-Spam-Level:
X-Spam-Status: No, score=-2.188 tagged_above=-999 required=5 tests=[AWL=0.060, BAYES_00=-2.599, HELO_EQ_FR=0.35, UNPARSEABLE_RELAY=0.001]
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 tUyEA2hOGlaG for <softwires@ietfa.amsl.com>; Tue, 13 Aug 2013 05:12:20 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias92.francetelecom.com [193.251.215.92]) by ietfa.amsl.com (Postfix) with ESMTP id 2259611E8179 for <softwires@ietf.org>; Tue, 13 Aug 2013 05:12:20 -0700 (PDT)
Received: from omfedm05.si.francetelecom.fr (unknown [xx.xx.xx.1]) by omfedm12.si.francetelecom.fr (ESMTP service) with ESMTP id 1D29118CC3C; Tue, 13 Aug 2013 14:12:19 +0200 (CEST)
Received: from PUEXCH21.nanterre.francetelecom.fr (unknown [10.101.44.28]) by omfedm05.si.francetelecom.fr (ESMTP service) with ESMTP id 03B4835C048; Tue, 13 Aug 2013 14:12:19 +0200 (CEST)
Received: from PUEXCB1B.nanterre.francetelecom.fr ([10.101.44.12]) by PUEXCH21.nanterre.francetelecom.fr ([10.101.44.28]) with mapi; Tue, 13 Aug 2013 14:12:18 +0200
From: mohamed.boucadair@orange.com
To: Ole Troan <otroan@employees.org>
Date: Tue, 13 Aug 2013 14:12:17 +0200
Thread-Topic: [Softwires] I-D Action: draft-ietf-softwire-map-08.txt
Thread-Index: Ac6YFnfT9C1wndvZR72FKgLkcDv8swABxy3A
Message-ID: <94C682931C08B048B7A8645303FDC9F36EEC7E9983@PUEXCB1B.nanterre.francetelecom.fr>
References: <20130812121654.30206.92319.idtracker@ietfa.amsl.com> <94C682931C08B048B7A8645303FDC9F36EEC7E980D@PUEXCB1B.nanterre.francetelecom.fr> <86841AD5-1864-4177-BEE1-4181DDE085EF@employees.org> <94C682931C08B048B7A8645303FDC9F36EEC7E9915@PUEXCB1B.nanterre.francetelecom.fr> <8FF0368A-D069-4BDA-9919-58FE22B81026@employees.org> <9B5FC5D7-45F6-4768-9B96-66114662FA09@gmail.com> <77DB9DB1-90D8-447F-A4D2-D130FB277115@employees.org>
In-Reply-To: <77DB9DB1-90D8-447F-A4D2-D130FB277115@employees.org>
Accept-Language: fr-FR
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: fr-FR
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2013.8.13.113330
Cc: "softwires@ietf.org" <softwires@ietf.org>
Subject: Re: [Softwires] I-D Action: draft-ietf-softwire-map-08.txt
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, 13 Aug 2013 12:12:39 -0000

Re-,

Yes, there is a WGLC but this does not mean that the document as it is solves all raised issues. Senthil did already raised this point to the authors of MAP and MAP-T drafts in June 19, but unless I'm mistaken I didn't saw a follow up to his request. 

I hope we can close this point ASAP so that the MAP document can move forward.

Thanks.
Cheers,
Med


>-----Message d'origine-----
>De : Ole Troan [mailto:otroan@employees.org]
>Envoyé : mardi 13 août 2013 13:16
>À : Qi Sun
>Cc : BOUCADAIR Mohamed OLNC/OLN; softwires@ietf.org
>Objet : Re: [Softwires] I-D Action: draft-ietf-softwire-map-08.txt
>
>Qi,
>
>> IMHO, the Unified CPE defines some functionalities and behaviors of CE
>side, e.g. tunnel endpoint, NAT44, how to use these functions on CPE etc.,
>which MAP depends on.
>>
>> As for the provisioning method, map-dhcp is one of the methods could be
>used in MAP. The discussion is taking place in the Unified CPE for
>provisioning. So I think it should be an informative reference in MAP base
>draft.
>
>so you are saying that draft-ietf-softwire-map cannot stand on its own, but
>depend on text in unified CPE?
>if so, what is missing? which parts of the unified CPE draft should be
>referenced? please propose text changes to the document.
>
>I am open to the possibility that I'm wrong of course, but I can't know
>that for sure, before I see what text changes you propose.
>I'm not trying to be difficult (at least not more than usual), but the
>document has passed WGLC, and we're restrictive about accepting changes.
>
>cheers,
>Ole