Re: [L2tpext] New Version Notification for draft-ietf-l2tpext-keyed-v6-tunnel-yang-02.txt

Giles Heron <giles.heron@gmail.com> Fri, 28 October 2016 16:10 UTC

Return-Path: <giles.heron@gmail.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 D472212954D for <l2tpext@ietfa.amsl.com>; Fri, 28 Oct 2016 09:10:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 5_vWsphMea3P for <l2tpext@ietfa.amsl.com>; Fri, 28 Oct 2016 09:10:27 -0700 (PDT)
Received: from mail-pf0-x231.google.com (mail-pf0-x231.google.com [IPv6:2607:f8b0:400e:c00::231]) (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 0C249129496 for <l2tpext@ietf.org>; Fri, 28 Oct 2016 09:10:27 -0700 (PDT)
Received: by mail-pf0-x231.google.com with SMTP id 197so39808827pfu.0 for <l2tpext@ietf.org>; Fri, 28 Oct 2016 09:10:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=UuT2zfZhBkAMVa+XHZNDJLT0YAbHcvYgkBX2NXtj6oM=; b=HDdJDjUl9e2isMmOmFh7tRPr0slqdHjS4AMdqkx/xKzftvDbNGIgm7j8xx5gVg4xj1 nFVJZxfpNOMxTvKKKWDmonXi3wJsfzo66CcBvjc+lkR04sWAFzK77aWmeXfudy7O7HQu o6I/KkIczkMeK1oas51dKXdbuW56vlr+M2TqTheiHGsld130iL9n4LE5dUYhXdBtd561 pkuA2VgxsQhlT/k1KGJleVQs+ChBGezxtBVEZ9B4adeIaa3emiItRILycnrew90cTEPd Qu+WpRPzaVX/FzXrS8yX5824M4DID1bflDgn52T6MGpxUGPZq0g8vUUSFd4toqSE16z2 KsKA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=UuT2zfZhBkAMVa+XHZNDJLT0YAbHcvYgkBX2NXtj6oM=; b=SwzOb3aWy6tn0ApO7foy0etO591pUE9PJ+9uS0X3RcDKvSf6brjZeMUpI3GLYn5BZ0 lFQvV0DPAPAY75x/hTXj5YPUCcnMJW/SSshVJ2TzQLthzjBQ0J4j6Z8MBH4Zv2O3kFj2 sqjTT6PT9SvrXPh/TdgF0+/QREY8FSlMDI8WfQ1zLojit3xjFYXO/vn0XvGD6jr6rOCK 5ytsyAGrIdNTL3QCKyLa6/dk32Md6KN/ABdmDpZcGxyJL3NF7s4acKb30pu42ma4suHC 8kr1CxytNapyPj3pA1h6dUrnZFbDb5TKlOlxPncsmgc9NkUlSY8XsrakbdMKkGDbLtnm eb2w==
X-Gm-Message-State: ABUngve8ym4DjATf4hxt1YQtgWb5xrfLG+7PaS2YI37xu/84QdYjuIQh6ne4qg6r5ZzL1A==
X-Received: by 10.99.96.136 with SMTP id u130mr21825119pgb.47.1477671026629; Fri, 28 Oct 2016 09:10:26 -0700 (PDT)
Received: from ?IPv6:2001:420:c0c0:1002::107? ([2001:420:c0c0:1002::107]) by smtp.gmail.com with ESMTPSA id bx5sm19998127pad.6.2016.10.28.09.10.23 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Fri, 28 Oct 2016 09:10:26 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Giles Heron <giles.heron@gmail.com>
In-Reply-To: <F7641219-3A48-4F35-B351-1BA91F833D38@cisco.com>
Date: Fri, 28 Oct 2016 17:10:26 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <F0420F1F-9B3C-470F-B504-924D79A5D8FF@gmail.com>
References: <147764356272.24948.16837477966660147078.idtracker@ietfa.amsl.com> <05FADFF5-5D7D-482A-856E-8E8C7AD1091D@telekom.de> <F7641219-3A48-4F35-B351-1BA91F833D38@cisco.com>
To: "Carlos Pignataro (cpignata)" <cpignata@cisco.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/l2tpext/hemJfNOzKBXxBEToEOxqE0_f0PQ>
Cc: "ian.farrer@telekom.de" <ian.farrer@telekom.de>, "l2tpext@ietf.org" <l2tpext@ietf.org>
Subject: Re: [L2tpext] New Version Notification for draft-ietf-l2tpext-keyed-v6-tunnel-yang-02.txt
X-BeenThere: l2tpext@ietf.org
X-Mailman-Version: 2.1.17
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: Fri, 28 Oct 2016 16:10:29 -0000

Hi Carlos,

not sure if we need a “generic” L2TP YANG model.   Existing L2TP deployments happened without YANG models - I’m not sure how much the MIBs were used?

For keyed IP tunnel the YANG model is critical (as there’s no L2TP signalling so both ends of each tunnel need to be configured with the same IPv6 addresses, session IDs and cookies), so I’m not sure I’d want to slow the YANG models down by seeking commonality with a generic L2TP model that might not get used.

Giles

> On 28 Oct 2016, at 14:36, Carlos Pignataro (cpignata) <cpignata@cisco.com>; wrote:
> 
> Thank you, Ian, for this update.
> 
> Looking at the L2tpext list, there has not been significant discussion of this document — before a last-call, it may seem we need a first-call :-)
> 
> WG,
> 
> I would encourage you to read this document and comment on the list.
> 
> Authors,
> 
> I was just wondering — wouldn’t we need an L2tp YANG model, before a Keyed-v6-tunnel one?
> 
> Thanks!
> 
> — Carlos.
> 
>> On Oct 28, 2016, at 4:40 AM, ian.farrer@telekom.de wrote:
>> 
>> Hi,
>> 
>> We’ve just submitted a new version of this draft. This is a small update which cleans up some outstanding items:
>> 
>> • Updated the YANG model to YANG 1.1 (the model content and structure was already compliant, so this only required addition of the ‘yang-version 1.1’ statement
>> • Small language cleanup
>> • Completion of the IANA Considerations section
>> 
>> The model has been checked against yangvalidator.com and reports ‘No warning or errors’.
>> 
>> The authors believe that this draft is now ready and would like to request WGLC.
>> 
>> Thanks,
>> Ian
>> 
>> 
>> On 28/10/16 10:32, "internet-drafts@ietf.org"; <internet-drafts@ietf.org>; wrote:
>> 
>> 
>>   A new version of I-D, draft-ietf-l2tpext-keyed-v6-tunnel-yang-02.txt
>>   has been successfully submitted by Ian Farrer and posted to the
>>   IETF repository.
>> 
>>   Name:		draft-ietf-l2tpext-keyed-v6-tunnel-yang
>>   Revision:	02
>>   Title:		A YANG Data Model for Keyed IPv6 Tunnels
>>   Document date:	2016-10-28
>>   Group:		l2tpext
>>   Pages:		14
>>   URL:            https://www.ietf.org/internet-drafts/draft-ietf-l2tpext-keyed-v6-tunnel-yang-02.txt
>>   Status:         https://datatracker.ietf.org/doc/draft-ietf-l2tpext-keyed-v6-tunnel-yang/
>>   Htmlized:       https://tools.ietf.org/html/draft-ietf-l2tpext-keyed-v6-tunnel-yang-02
>>   Diff:           https://www.ietf.org/rfcdiff?url2=draft-ietf-l2tpext-keyed-v6-tunnel-yang-02
>> 
>>   Abstract:
>>      This document defines a YANG data model for the configuration and
>>      management of Keyed IPv6 tunnels.  The data model includes both
>>      configuration and state data.  Due to the stateless nature of keyed
>>      IPv6 tunnels, a model for NETCONF notifications is not necessary.
>> 
>> 
>> 
>> 
>> 
>>   Please note that it may take a couple of minutes from the time of submission
>>   until the htmlized version and diff are available at tools.ietf.org.
>> 
>>   The IETF Secretariat
>> 
>> 
>> 
>> _______________________________________________
>> L2tpext mailing list
>> L2tpext@ietf.org
>> https://www.ietf.org/mailman/listinfo/l2tpext
> 
> _______________________________________________
> L2tpext mailing list
> L2tpext@ietf.org
> https://www.ietf.org/mailman/listinfo/l2tpext