Re: registering tunnel types
Joel Jaeggli <joelja@bogus.com> Tue, 30 October 2018 20:24 UTC
Return-Path: <joelja@bogus.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 E9B791276D0 for <ipv6@ietfa.amsl.com>; Tue, 30 Oct 2018 13:24:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.899
X-Spam-Level:
X-Spam-Status: No, score=-6.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5] 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 aVOM_q_ZLz3Q for <ipv6@ietfa.amsl.com>; Tue, 30 Oct 2018 13:24:04 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) (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 B2439124408 for <ipv6@ietf.org>; Tue, 30 Oct 2018 13:24:03 -0700 (PDT)
Received: from [IPv6:2607:fb90:f35:bf71:5596:3038:5b78:7735] ([IPv6:2607:fb90:f35:bf71:5596:3038:5b78:7735]) (authenticated bits=0) by nagasaki.bogus.com (8.15.2/8.15.2) with ESMTPSA id w9UKNtkt010376; Tue, 30 Oct 2018 20:23:57 GMT (envelope-from joelja@bogus.com)
From: Joel Jaeggli <joelja@bogus.com>
Message-Id: <2A649FB9-0696-40BC-BE4E-2CB5E4AA4F05@bogus.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_1752841F-47DB-457B-9BA1-C34B3401BCC1"
Mime-Version: 1.0 (Mac OS X Mail 12.0 \(3445.100.39\))
Subject: Re: registering tunnel types
Date: Tue, 30 Oct 2018 13:23:55 -0700
In-Reply-To: <026701d47048$dfd7b900$4001a8c0@gateway.2wire.net>
Cc: "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>, "ipv6@ietf.org" <ipv6@ietf.org>, Alexandre Petrescu <alexandre.petrescu@gmail.com>
To: tom petch <ietfc@btconnect.com>
References: <01a901d46bb2$26c23700$4001a8c0@gateway.2wire.net> <e1ebf233-6e34-8d78-3ce3-293602462665@gmail.com> <787AE7BB302AE849A7480A190F8B93302E039F88@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <e71cbb98-a841-013c-1baa-300c45db20bd@gmail.com> <026701d47048$dfd7b900$4001a8c0@gateway.2wire.net>
X-Mailer: Apple Mail (2.3445.100.39)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/pPbJa1HA-jd6bYg2tK-eHMaZy94>
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: Tue, 30 Oct 2018 20:24:06 -0000
> On Oct 30, 2018, at 05:07, tom petch <ietfc@btconnect.com> wrote: >> > > Alex > > I agree, at least in part; tunnels and interfaces are different animals > and it is unfortunate that they were conflated in SMI. > > I was surprised that NETMOD had not produced a YANG module for tunnels > but it seems that there has been no need for the past decade. That > said, I think that it is a good idea to have one. Whether or not it > should mirror the Tunnel MIB I find more debatable. It’s not entirely obvious to me that netted / netconfig would be where the tunnel models were produced. They tend if fact to be produced by the tunnel protocol maintainers e.g. l3sm/l2sm/ccamp and so on. The management tools for a product tend to be developed itself in my experience. > My own homework came across other IP in IP varieties which do not > appear. > > Tom Petch > > >> >> Alex >> >>> >>> If you need a new value or if you have a question about a given > interface tunnel type, please follow the guidelines in the url cited > above. All this is out of the scope of draft-ietf-softwire-yang. >>> >>> Cheers, >>> Med >>> >>>> -----Message d'origine----- >>>> De : ipv6 [mailto:ipv6-bounces@ietf.org] De la part de Alexandre > Petrescu >>>> Envoyé : jeudi 25 octobre 2018 09:54 >>>> À : ipv6@ietf.org >>>> Objet : Re: registering tunnel types >>>> >>>> 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 >> -------------------------------------------------------------------- >> > > -------------------------------------------------------------------- > IETF IPv6 working group mailing list > ipv6@ietf.org <mailto:ipv6@ietf.org> > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 <https://www.ietf.org/mailman/listinfo/ipv6> > --------------------------------------------------------------------
- registering tunnel types tom petch
- Re: registering tunnel types Sander Steffann
- Re: registering tunnel types Alexandre Petrescu
- Re: registering tunnel types Alexandre Petrescu
- Re: registering tunnel types Michael Richardson
- Re: registering tunnel types tom petch
- RE: registering tunnel types mohamed.boucadair
- RE: registering tunnel types mohamed.boucadair
- RE: registering tunnel types mohamed.boucadair
- RE: registering tunnel types mohamed.boucadair
- RE: registering tunnel types mohamed.boucadair
- Re: registering tunnel types Alexandre Petrescu
- RE: registering tunnel types mohamed.boucadair
- Re: registering tunnel types Alexandre Petrescu
- Re: registering tunnel types tom petch
- Re: registering tunnel types tom petch
- RE: registering tunnel types mohamed.boucadair
- Re: registering tunnel types Joel Jaeggli
- Re: registering tunnel types tom petch
- Re: registering tunnel types - proprietary enc in… Alexandre Petrescu
- Re: registering tunnel types - proprietary enc in… Michael Richardson
- Re: registering tunnel types - proprietary enc in… Alexandre Petrescu