[L2tpext] Updated to draft-ietf-l2tpext-keyed-v6-tunnel-yang

Ian Farrer <ianfarrer@gmx.com> Mon, 30 October 2017 14:11 UTC

Return-Path: <ianfarrer@gmx.com>
X-Original-To: l2tpext@ietfa.amsl.com
Delivered-To: l2tpext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 11A3913FA06 for <l2tpext@ietfa.amsl.com>; Mon, 30 Oct 2017 07:11:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.9
X-Spam-Level:
X-Spam-Status: No, score=-4.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-2.8, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-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 CM8tzdUdAbl7 for <l2tpext@ietfa.amsl.com>; Mon, 30 Oct 2017 07:11:51 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 12F9B13F9F3 for <l2tpext@ietf.org>; Mon, 30 Oct 2017 07:11:48 -0700 (PDT)
Received: from hargashouseofribs.lan ([80.159.240.8]) by mail.gmx.com (mrgmx102 [212.227.17.174]) with ESMTPSA (Nemesis) id 0Lj4xG-1dafr30OLO-00dHZM for <l2tpext@ietf.org>; Mon, 30 Oct 2017 15:11:47 +0100
From: Ian Farrer <ianfarrer@gmx.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Message-Id: <8DC64879-399B-4DBD-BC69-82D4972B56E2@gmx.com>
Date: Mon, 30 Oct 2017 15:11:46 +0100
To: l2tpext@ietf.org
X-Mailer: Apple Mail (2.3273)
X-Provags-ID: V03:K0:krufIP6zpR2caKb5BQA0R+x8L7SaqgeqmHsTRttQi9JtFTszmoH nb7+X6osNpTMPszyuJihNtFJ9BK8V+0klhb6ZMIhUdndazYwLgHeAXFEoNby7+NYBGYNA04 Hzq5afGlmkX5X3fRto9itJlotLE2+MHpwYjXiTeIyvfcIMcoOnccEfglZrdaLhIJoIWYNft gbkwwBVI0W4R6T+/108/w==
X-UI-Out-Filterresults: notjunk:1;V01:K0:8iANKiA4R+g=:pHWJrauLm9Q1xy1hHiD0J+ CfsQb9j1k7hGlFhQ2oFScljA77MIiO46+Q6K24xK2DSS1eIDHhJm0N9Tw7ogqRN//KfC4/V/e e3yBZRQ58s1Czatj+HzzRuQkjvl2ugVk59335NhwzmEgsGgW8Gyhak8ZRbB339dYC7A1lcDru Bmsa1nmMu+ECVWNbtM5AfNcCC1Cj1HRurZ4qNnWSa3gXtRN2JilZ/cnmC4N6nNrhsURkD9wEg KgcBLg/ISPzG4jRQml51MBmoMNwhvY+V1HagJyx65s8mw2qL/BnjcdiuR68bFb3gGRgNZYmiq oH3zzzqGSWLXfkDxbOKvVuAKovJyXiU5W25ILnEtp10TSvIIsS03c6tVF5Sfl+dSwDvOe3ADU qUPziVbX1BU63V6R6FpMNIRwGAYGFkEe3LzWmWAp5eRDFyGh9qO+6bKa2wDT9007bUJro8tbJ xsEzyZHz+XhAJ8pSgB4nxdVEXVIeMU0e1zuf0066Zum98eAQg2ieV70jBRcqIj2znTHHqs0iK RoupyoJ5dcXz3m6+Y6GIA6q06Vhiir+VUnS0LKk2MgWW/bIrS55AN85yuIFpHqnFsWhvoQk4v XNKiIZldPVurehn0FcxbcpTmeavVidgkSJsnNPaNQJVKkJtz7MOf5YClWb1KCP8lFr/W+2VMw LxBKz1ueMAEhVAfqSSl5rwTRrKQABM5pwZwRpWvrFv9lqV8Ul9yB1b+b5kiy7cNB8GJYn6Asg jLBPEFZKB5ji1CU+WTqnIWxORD1zyk+qLJ/gQCI0dDHxuiQoxXW1uy4twxh00ITKZmxpDRt+b Ra7C5VI14WxUcojnthGbMjlMumlgypxT05PcWKVkbFOjCcnI/I=
Archived-At: <https://mailarchive.ietf.org/arch/msg/l2tpext/-_UThBhUYaLSl2AuE8MGw7bZ6gw>
Subject: [L2tpext] Updated to draft-ietf-l2tpext-keyed-v6-tunnel-yang
X-BeenThere: l2tpext@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Layer Two Tunneling Protocol Extensions <l2tpext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/l2tpext>, <mailto:l2tpext-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/l2tpext/>
List-Post: <mailto:l2tpext@ietf.org>
List-Help: <mailto:l2tpext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l2tpext>, <mailto:l2tpext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Oct 2017 14:11:58 -0000

Hi,

We’ve just posted an updated version of draft-ietf-l2tpext-keyed-v6-tunnel-yang. There are no major changes in this version (minor text cleanups, checked for YANG1.1 compliance). Whilst updating the draft, a few questions have come to light that I would appreciate feedback on the following points:

1, In the current model, we don’t create an entry in the if:interfaces list for the l2tpv3 tunnel which is being configured.

2, The feature that we have for bfd seem a little useless at the moment (you can turn it on, but no actual BFD configuration). draft-ietf-bfd-yang has the yang model for BFD, so it would be better to remove this from the keyed tunnel model and put a pointer to that draft in the description text.
However, if I am reading the BFD model correctly, it requires an entry in if:interfaces to attach the BFD configuration to, so this would point to restructuring the model to augment if:interfaces instead of the current structure

3, There is also a feature for vccv, which again just enables but provides no other config.  draft-chen-pals-pw-yang-02 models VCCV as part of a pseudowire, but looking at the structure of that, I don’t see any way that we could re-use only the VCCV part in our model. I’m not familiar with VCCV, so does anyone with more experience have a view on what the best way to tackle this is?

Any comments or suggestions appreciated.

Thanks,
Ian