RE: registering tunnel types

<mohamed.boucadair@orange.com> Mon, 29 October 2018 12:20 UTC

Return-Path: <mohamed.boucadair@orange.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 085B6130EDB for <ipv6@ietfa.amsl.com>; Mon, 29 Oct 2018 05:20:00 -0700 (PDT)
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 1FZdQGu-eTkn for <ipv6@ietfa.amsl.com>; Mon, 29 Oct 2018 05:19:58 -0700 (PDT)
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 37FA3130ED6 for <ipv6@ietf.org>; Mon, 29 Oct 2018 05:19:58 -0700 (PDT)
Received: from opfednr07.francetelecom.fr (unknown [xx.xx.xx.71]) by opfednr23.francetelecom.fr (ESMTP service) with ESMTP id 42kDF90HPzz5wbl; Mon, 29 Oct 2018 13:19:57 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.21]) by opfednr07.francetelecom.fr (ESMTP service) with ESMTP id 42kDF86Q93zFpX6; Mon, 29 Oct 2018 13:19:56 +0100 (CET)
Received: from OPEXCLILMA3.corporate.adroot.infra.ftgroup ([fe80::60a9:abc3:86e6:2541]) by OPEXCLILM6C.corporate.adroot.infra.ftgroup ([fe80::d9f5:9741:7525:a199%18]) with mapi id 14.03.0415.000; Mon, 29 Oct 2018 13:19:56 +0100
From: mohamed.boucadair@orange.com
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>, "ipv6@ietf.org" <ipv6@ietf.org>
Subject: RE: registering tunnel types
Thread-Topic: registering tunnel types
Thread-Index: AQHUbDfn+4muaMNWPkKHpPUxzhC6eKUvdtsAgAaz+XA=
Date: Mon, 29 Oct 2018 12:19:56 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B93302E039F9C@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
References: <01a901d46bb2$26c23700$4001a8c0@gateway.2wire.net> <e1ebf233-6e34-8d78-3ce3-293602462665@gmail.com> <94ec78a4-e02f-f4f9-d694-9c5b51552b1a@gmail.com>
In-Reply-To: <94ec78a4-e02f-f4f9-d694-9c5b51552b1a@gmail.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.168.234.4]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/JG5EKNXaTK3Ol-nL0GIPLvamvrQ>
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: Mon, 29 Oct 2018 12:20:00 -0000

Re-,

Please check https://www.iana.org/assignments/smi-numbers/smi-numbers.xhtml#smi-numbers-6 for your questions. 

Cheers,
Med

> -----Message d'origine-----
> De : ipv6 [mailto:ipv6-bounces@ietf.org] De la part de Alexandre Petrescu
> Envoyé : jeudi 25 octobre 2018 09:58
> À : ipv6@ietf.org
> Objet : Re: registering tunnel types
> 
> 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
> > --------------------------------------------------------------------
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------