Re: registering tunnel types

Alexandre Petrescu <alexandre.petrescu@gmail.com> Thu, 25 October 2018 07:57 UTC

Return-Path: <alexandre.petrescu@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E6A2F12D4F2 for <ipv6@ietfa.amsl.com>; Thu, 25 Oct 2018 00:57:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.632
X-Spam-Level:
X-Spam-Status: No, score=-2.632 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_MED=-2.3, SPF_SOFTFAIL=0.665, 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 V9_eli4ERRux for <ipv6@ietfa.amsl.com>; Thu, 25 Oct 2018 00:57:46 -0700 (PDT)
Received: from sainfoin-smtp-out.extra.cea.fr (sainfoin-smtp-out.extra.cea.fr [132.167.192.228]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3CF41128CF2 for <ipv6@ietf.org>; Thu, 25 Oct 2018 00:57:46 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id w9P7vifV044831 for <ipv6@ietf.org>; Thu, 25 Oct 2018 09:57:44 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 76AC6202A1D for <ipv6@ietf.org>; Thu, 25 Oct 2018 09:57:44 +0200 (CEST)
Received: from muguet2-smtp-out.intra.cea.fr (muguet2-smtp-out.intra.cea.fr [132.166.192.13]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 6D015202A13 for <ipv6@ietf.org>; Thu, 25 Oct 2018 09:57:44 +0200 (CEST)
Received: from [10.8.34.184] (is227335.intra.cea.fr [10.8.34.184]) by muguet2-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id w9P7vigN006802 for <ipv6@ietf.org>; Thu, 25 Oct 2018 09:57:44 +0200
Subject: Re: registering tunnel types
To: ipv6@ietf.org
References: <01a901d46bb2$26c23700$4001a8c0@gateway.2wire.net> <e1ebf233-6e34-8d78-3ce3-293602462665@gmail.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <94ec78a4-e02f-f4f9-d694-9c5b51552b1a@gmail.com>
Date: Thu, 25 Oct 2018 09:57:44 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <e1ebf233-6e34-8d78-3ce3-293602462665@gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: fr
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/4DkNv5agVdhcLH32j08VqBKCboQ>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Oct 2018 07:57:49 -0000

why do you say 'sixtofour' and not '6to4'?  If that is a YANG software 
problem then it should be fixed.  If it is just a nicer manner to write 
text then I think it is a little bit confusing to me.

(there are similar problems with xml2rfc which cant reference '3gpp' 
documents because starting with a number;  I guess fixing one would help 
fix the other).

Alex

Le 25/10/2018 à 09:53, Alexandre Petrescu a écrit :
> Are:
> -IPv6 in UDPv4 and
> -IPv6 in IPv6 as used by openvpn;
> 
> covered by the list below?
> 
> These are a few tunnelling mechanisms I use routinely.
> 
> Existing identity 6tofour should be deprecated, if that means 6to4, 
> which is deprecated.
> 
> Existing identity iphttps has a version number for IP?
> 
> Alex
> 
> Le 24/10/2018 à 17:57, tom petch a écrit :
>> draft-ietf-softwire-yang
>> completed IETF Last Call two weeks ago and, since then, has acquired a
>> YANG module that defines tunnel types, as listed below.  It is intended
>> to be a IANA-maintained module and so changes to the list of tunnels
>> will not require a reissue of the softwires RFC-to-be.  At the same
>> time, getting it right first time never did any harm so if anyone can
>> think of any missing, or can think of other places where there might be
>> other tunnels lurking, now would be a good time to mention it.
>>
>> It is based on RFC4087 Tunnel MIB (which created an SMI Textual
>> Convention that went up to Teredo) so tunnels from that vintage are
>> likely well catered for.  softwires is not where I would have first
>> looked for tunnel types, but it has a certain logic to it.
>>
>>       identity  other
>>
>>       identity direct
>>
>>       identity gre
>>
>>       identity minimal
>>
>>       identity l2tp
>>
>>       identity pptp
>>
>>       identity l2f
>>
>>       identity udp
>>
>>       identity atmp
>>
>>       identity msdp
>>
>>       identity sixtofour
>>
>>       identity sixoverfour
>>
>>       identity isatap
>>
>>       identity teredo
>>
>>       identity iphttps
>>
>>       identity softwiremesh
>>
>>       identity dslite
>>
>>       identity  aplusp
>>
>> Tom Petch
>>
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> ipv6@ietf.org
>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------
>>
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------