Re: [Softwires] [Tsv-art] Tsvart last call review of draft-ietf-softwire-iftunnel-04

Mirja Kuehlewind <> Wed, 29 May 2019 16:46 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 0EF34120183; Wed, 29 May 2019 09:46:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id am7ttRDvbPw5; Wed, 29 May 2019 09:46:21 -0700 (PDT)
Received: from ( [IPv6:2a01:488:42:1000:50ed:8223::]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id E75E612018D; Wed, 29 May 2019 09:46:12 -0700 (PDT)
Received: from [] (helo=[]); authenticated by running ExIM with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) id 1hW1iK-00067x-O3; Wed, 29 May 2019 18:46:08 +0200
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.8\))
From: Mirja Kuehlewind <>
In-Reply-To: <>
Date: Wed, 29 May 2019 18:46:07 +0200
Cc: David Black <>, "" <>, "" <>, "" <>, "" <>
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <> <>
To: "Eric Vyncke (evyncke)" <>
X-Mailer: Apple Mail (2.3445.104.8)
X-HE-SMSGID: 1hW1iK-00067x-O3
Archived-At: <>
Subject: Re: [Softwires] [Tsv-art] Tsvart last call review of draft-ietf-softwire-iftunnel-04
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, 29 May 2019 16:46:24 -0000

Hi Eric,

Just catching up on this thread now. And indeed, thanks for the review, David. Just to complete my understanding of the situation, can you briefly explain what the plan for updating the tunnel type registry is then?


> On 28. May 2019, at 09:07, Eric Vyncke (evyncke) <> wrote:
> Dear all,
> Thank you again for the review.
> After discussion with Dave Thaler (who maintains the tunnel type IANA registry), it appears that the draft can go forward without waiting for a complete IANA registry for tunnel types.
> Best regards
> -éric
> On 08/05/2019, 00:45, "David Black via Datatracker" <> wrote:
>    Reviewer: David Black
>    Review result: Not Ready
>    This document has been reviewed as part of the transport area review team's
>    ongoing effort to review key IETF documents. These comments were written
>    primarily for the transport area directors, but are copied to the document's
>    authors and WG to allow them to address any issues raised and also to the
>    IETF discussion list for information.
>    When done at the time of IETF Last Call, the authors should consider this
>    review as part of the last-call comments they receive. Please always CC
> if you reply to or forward this review.
>    This draft defines a YANG module for tunnel types based on the MIB-2
>    tunnel type registry maintained by IANA.
>    My fundamental concern with this draft is that the MIB-2 tunnel type
>    registry is seriously incomplete and out of date, as there are a large
>    number of tunnel types that aren't included in that registry, e.g., IPsec
>    tunnel-mode AMT tunneling.  In its current form, that registry does not
>    appear to be a good starting point for specifying YANG management of
>    tunnels.     
>    A limited justification that I could envision for defining this YANG module
>    would be to use it for mechanical translations to YANG of existing MIBs
>    that use MIB-2 tunnel types - if that's the justification, then it would need
>    to be clearly stated in an applicability statement within this draft, and the
>    discussion of extension of this YANG module would need to be aligned with
>    that limited applicability. 
>    The proverbial "right thing to do" would be to update both the MIB-2 tunnel
>    type registry and this draft with all of the currently known tunnel types.
>    The references section of draft-ietf-tsvwg-rfc6040update-shim
>    (
>    may help in identifying tunnel protocols that should be included.
>    A minor concern involves the use of RFC 8085 as the reference for UDP
>    tunnels; while that's certainly better than the existing use of RFC 4087, due
>    to the extensive design guidance in RFC 8085, designers of UDP-encapsulated
>    tunnel protocols ought to be encouraged to register their protocols as separate
>    tunnel types (e.g., so the network operator has some idea of what the UDP
>    tunnel is actually being used for).  This draft ought to encourage tunnel
>    protocol designers to register their own tunnel types in preference to reuse
>    of the UDP tunnel type, including placing text in the IANA tunnel type
>    registry and this YANG module to encourage that course of action.
> _______________________________________________
> Tsv-art mailing list