Re: [Softwires] advance draft-ietf-softwire-iftunnel

<mohamed.boucadair@orange.com> Mon, 28 January 2019 06:53 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 B7242130FA3; Sun, 27 Jan 2019 22:53:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 BFdw3nbyWl7T; Sun, 27 Jan 2019 22:53:43 -0800 (PST)
Received: from orange.com (mta135.mail.business.static.orange.com [80.12.70.35]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E90DA12896A; Sun, 27 Jan 2019 22:53:42 -0800 (PST)
Received: from opfednr04.francetelecom.fr (unknown [xx.xx.xx.68]) by opfednr26.francetelecom.fr (ESMTP service) with ESMTP id 43p0hh64X7z10bb; Mon, 28 Jan 2019 07:53:40 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.13]) by opfednr04.francetelecom.fr (ESMTP service) with ESMTP id 43p0hh58T9z1xnx; Mon, 28 Jan 2019 07:53:40 +0100 (CET)
Received: from OPEXCAUBM6E.corporate.adroot.infra.ftgroup (10.114.13.79) by OPEXCLILM6D.corporate.adroot.infra.ftgroup (10.114.31.13) with Microsoft SMTP Server (TLS) id 14.3.408.0; Mon, 28 Jan 2019 07:53:40 +0100
Received: from OPEXCAUBMA2.corporate.adroot.infra.ftgroup ([fe80::e878:bd0:c89e:5b42]) by OPEXCAUBM6E.corporate.adroot.infra.ftgroup ([fe80::d89a:9017:59c2:9724%21]) with mapi id 14.03.0415.000; Mon, 28 Jan 2019 07:53:40 +0100
From: <mohamed.boucadair@orange.com>
To: Yong Cui <cuiyong@tsinghua.edu.cn>, "draft-ietf-softwire-iftunnel@ietf.org" <draft-ietf-softwire-iftunnel@ietf.org>
CC: Softwires-wg <softwires@ietf.org>, "softwire-chairs@ietf.org" <softwire-chairs@ietf.org>
Thread-Topic: advance draft-ietf-softwire-iftunnel
Thread-Index: AQHUtW/eWxCHVgWDH0+hqo5UHgXU0KXEQJqA
Date: Mon, 28 Jan 2019 06:53:39 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B93302EA0E214@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
References: <0E6F8B92-1CA5-4AE9-8314-948DE9002642@tsinghua.edu.cn>
In-Reply-To: <0E6F8B92-1CA5-4AE9-8314-948DE9002642@tsinghua.edu.cn>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.114.13.245]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/softwires/23JvD_LNAjU6CfB-8HX0cRFysvM>
Subject: Re: [Softwires] advance draft-ietf-softwire-iftunnel
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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: Mon, 28 Jan 2019 06:53:45 -0000

Hi Chairs, all, 

Please see inline. 

Cheers, 
Med

> -----Message d'origine-----
> De : Yong Cui [mailto:cuiyong@tsinghua.edu.cn]
> Envoyé : samedi 26 janvier 2019 13:08
> À : draft-ietf-softwire-iftunnel@ietf.org
> Cc : Softwires-wg; softwire-chairs@ietf.org
> Objet : advance draft-ietf-softwire-iftunnel
> 
> Dear authors and all ,
> 
> During the WGLC, we have some clear support and reasons to advance this I-D.
> 
> Before that, I would like to know:
> 1) if you know any IPR issues on this draft, and

[Med] I don't have any IPR related to this I-D

> 2) if you know any implementations on this one?
> Additionally, would you please use the button of "check nits" to check this
> I-D and try to avoid any error, flaws and warnings?

[Med] Fixed. Here is the output of the idnits check for the draft (-03):

==
  Checking boilerplate required by RFC 5378 and the IETF Trust (see
  https://trustee.ietf.org/license-info):
  ----------------------------------------------------------------------------

     No issues found here.

  Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt:
  ----------------------------------------------------------------------------

     No issues found here.

  Checking nits according to https://www.ietf.org/id-info/checklist :
  ----------------------------------------------------------------------------

     No issues found here.

  Miscellaneous warnings:
  ----------------------------------------------------------------------------

     No issues found here.

  Checking references for intended status: Proposed Standard
  ----------------------------------------------------------------------------

     (See RFCs 3967 and 4897 for information about using normative references
     to lower-maturity documents in RFCs)

     No issues found here.
==

Thank you.

> 
> Thanks,
> 
> Yong & Ian