Re: [Softwires] WGLC for draft-ietf-softwire-iftunnel-01

<> Thu, 10 January 2019 10:17 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 0AB9F130DC8 for <>; Thu, 10 Jan 2019 02:17:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, 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 ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id W7AEVinHm1Ua for <>; Thu, 10 Jan 2019 02:17:22 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 04706128CF3 for <>; Thu, 10 Jan 2019 02:17:22 -0800 (PST)
Received: from (unknown [xx.xx.xx.4]) by (ESMTP service) with ESMTP id 43b23q5Dnlz8tCf; Thu, 10 Jan 2019 11:17:11 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.69]) by (ESMTP service) with ESMTP id 43b23q46GJzCqkr; Thu, 10 Jan 2019 11:17:11 +0100 (CET)
Received: from OPEXCLILMA3.corporate.adroot.infra.ftgroup ([fe80::60a9:abc3:86e6:2541]) by OPEXCLILMA2.corporate.adroot.infra.ftgroup ([fe80::bc1c:ad2f:eda3:8c3d%18]) with mapi id 14.03.0415.000; Thu, 10 Jan 2019 11:17:11 +0100
From: <>
To: "" <>, Yong Cui <>
CC: Softwires-wg <>
Thread-Topic: [Softwires] WGLC for draft-ietf-softwire-iftunnel-01
Thread-Index: AQHUqLyCGwiAk8pHZUiGCtRiq1DFdaWoSS+Q
Date: Thu, 10 Jan 2019 10:17:10 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B93302E063C25@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
References: <> <> <>
In-Reply-To: <>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_787AE7BB302AE849A7480A190F8B93302E063C25OPEXCLILMA3corp_"
MIME-Version: 1.0
Archived-At: <>
Subject: Re: [Softwires] WGLC for draft-ietf-softwire-iftunnel-01
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: softwires wg discussion list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 10 Jan 2019 10:17:24 -0000

Hi all,

-02 will also implement a change requested by the smi expert to cite the RFCs defining the tunneling techniques instead of pointing to 4087. An action will be requested to IANA to update the table available at


De : Softwires [] De la part de
Envoyé : jeudi 10 janvier 2019 09:14
À : Yong Cui
Cc : Softwires-wg
Objet : Re: [Softwires] WGLC for draft-ietf-softwire-iftunnel-01

Hi Yong,

Further to my previous email.

During the review of draft-ietf-softwire-yang, there is a comment about following the published format for the Security Considerations section of a document containing a YANG module. I wasn’t previously aware of this:

As this comment will also be applicable to draft-ietf-softwire-iftunnel, I think we need to rewrite the Security Considerations section accordingly.


On 8. Jan 2019, at 17:48,<> wrote:

HI Yong,

Sorry for the late response. I’m still catching up after the holidays…

As a co-author, I support this document progressing. As you mention below, separating out the iftunnels module from draft-ietf-softwire-yang into a new draft was requested during the IANA review.  meaning that draft-ietf-softwire-yang (currently with the IESG) now has a normative reference to this draft.

Regarding the draft itself, the iftunnel module itself has already been through the final WGLC for draft-ietf-softwire-yang. As it models the IANA tunnelType Definitions registry (, we’ve tried to keep the format in line with other, similar documents with YANG modules for other IANA registries (e.g. RFC7224).


On 19. Dec 2018, at 08:26, Yong Cui <<>> wrote:

Dear all,

There were the following progress on Softwire YANG and related work during the past couple of months:
          • draft-ietf-softwire-yang completed WGLC
          • During expert review, a YANG module for the iana-iftunnel registry was requested as the softwire module needs to reference it.
          • draft-ietf-softwire-yang was updated to include this module and Sheng ran a WGLC on the new content. This passed without comment.
          • During IANA review, it was requested that the iana-iftunnel YANG module was put into a separate document.
          • draft-ietf-softwire-yang was updated, removing the iana-iftunnel YANG module, and draft-ietf-softwire-iftunnel was published containing just the module (it was posted as a WG doc as the content etc. is already under the scope of draft-ietf-softwire-yang)

So now, we’d like to issue a WGLC for draft-ietf-softwire-iftunnel-01.

Considering the coming Christmas and New Year, I would extend the WGLC to 3 weeks, i.e. Dec. 19, 2018 - Jan. 9, 2019. Please send your comments to our softwire mailing list, including your support or concerns.

Merry Christmas and Happy New Year!

Yong & Ian

Softwires mailing list<>