Re: [Softwires] Martin Vigoureux's No Objection on draft-ietf-softwire-iftunnel-06: (with COMMENT)

<> Wed, 12 June 2019 05:31 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 9376D12004C; Tue, 11 Jun 2019 22:31:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id XwALHXHbkIjx; Tue, 11 Jun 2019 22:31:34 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id A118312001A; Tue, 11 Jun 2019 22:31:30 -0700 (PDT)
Received: from (unknown [xx.xx.xx.69]) by (ESMTP service) with ESMTP id 45NwTX5zgqz2290; Wed, 12 Jun 2019 07:31:28 +0200 (CEST)
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.57]) by (ESMTP service) with ESMTP id 45NwTX52PGzyR4; Wed, 12 Jun 2019 07:31:28 +0200 (CEST)
Received: from OPEXCAUBMA2.corporate.adroot.infra.ftgroup ([fe80::e878:bd0:c89e:5b42]) by OPEXCAUBM6D.corporate.adroot.infra.ftgroup ([fe80::4c24:f1ba:2b1:e490%21]) with mapi id 14.03.0439.000; Wed, 12 Jun 2019 07:31:28 +0200
From: <>
To: Martin Vigoureux <>, The IESG <>
CC: "" <>, Yong Cui <>, "" <>, "" <>
Thread-Topic: Martin Vigoureux's No Objection on draft-ietf-softwire-iftunnel-06: (with COMMENT)
Thread-Index: AQHVIHbgGArmh+lgxEiFL8+gCyUVuKaXeXew
Date: Wed, 12 Jun 2019 05:31:27 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B93302EAA54A3@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
References: <>
In-Reply-To: <>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
x-originating-ip: []
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <>
Subject: Re: [Softwires] Martin Vigoureux's No Objection on draft-ietf-softwire-iftunnel-06: (with COMMENT)
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: Wed, 12 Jun 2019 05:31:36 -0000

Hi Martin,

Thank you for the comment. 

Please see inline. 


> -----Message d'origine-----
> De : Martin Vigoureux via Datatracker []
> Envoyé : mardi 11 juin 2019 18:58
> À : The IESG
> Cc :; Yong Cui; softwire-
> Objet : Martin Vigoureux's No Objection on draft-ietf-softwire-iftunnel-
> 06: (with COMMENT)
> Martin Vigoureux has entered the following ballot position for
> draft-ietf-softwire-iftunnel-06: No Objection
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut this
> introductory paragraph, however.)
> Please refer to
> for more information about IESG DISCUSS and COMMENT positions.
> The document, along with other ballot positions, can be found here:
> ----------------------------------------------------------------------
> ----------------------------------------------------------------------
> Hello,
> I am a bit puzzled because the Abstract recognizes that the document is
> built
> onto an incomplete data-set and that makes me wonder whether the model
> will be
> usable until the data-set is completed.

[Med] The registry does not need to be comprehensive to be useful/usable. For example, this module is already used by a document which is in the RFC Editor queue: draft-ietf-softwire-yang. 

> Also, I really do not understand the update you propose to the registry.
> It
> seems that you point to the technology spec rather than to the original
> mib
> module definition, but I quickly looked and none of the specs I parsed
> define
> the mib entry/value

[Med] This update was requested by the Designated Experts. They want the technology spec to be cited, not the RFC defining the MIB or YANG. Please note that registering a code does not require a MIB or a YANG. 

, so getting rid of the existing reference appears to
> me as
> a clear loss of information. I think you should keep the original
> reference and
> add a new one if needed, but not simply replace.
> And if you have undertaken this effort of tidying the registry, why not
> complete it with the missing values?

[Med] We used to have this discussion as part of the tsv directorate review. We don't think it is the job of this document to register new tunnel techniques to an existing registry. Nevertheless, we tried to get in touch with the authors of draft-ietf-lisp-rfc6830bis, draft-ietf-nvo3-vxlan-gpe, draft-ietf-nvo3-geneve, and draft-ietf-intarea-gue to invite them to register their tunnel technology. 

The I-D is mirroring the content of an * existing * registry. The corresponding YANG module will be updated by IANA upon assignment of a new code.