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

<ian.farrer@telekom.de> Fri, 28 October 2016 08:41 UTC

Return-Path: <prvs=102ce4c70=ian.farrer@telekom.de>
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 C066B129586 for <l2tpext@ietfa.amsl.com>; Fri, 28 Oct 2016 01:41:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.151
X-Spam-Level:
X-Spam-Status: No, score=-3.151 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.431] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=telekom.de
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 a6HXEUUym1pg for <l2tpext@ietfa.amsl.com>; Fri, 28 Oct 2016 01:41:12 -0700 (PDT)
Received: from mailout24.telekom.de (MAILOUT24.telekom.de [80.149.113.254]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1B8261294A0 for <l2tpext@ietf.org>; Fri, 28 Oct 2016 01:41:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telekom.de; i=@telekom.de; q=dns/txt; s=dtag1; t=1477643752; x=1509179752; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=nPIBkVd6Qo46B7dAdYGdSBaSCptT2NsonEZPOxQEqyk=; b=eCqwiso0WhZnZ2YWhLhGOyGpsVxHd7uLSDW1k4Q+DSkn6sq9Ql4sFztY FetL58O/ZYcGQGRScovhoFWJO/i3KFeeDAgZ4dV3r74uddruBazGqtn9B zNNwYjWChnUMS4vCGyofYXCfJnBqYwzHPjDTm0YnQAPnSmCtVDF695DOD k4sAPQs7uAeBE8Ws2MXjqrGtX219fh9yGgOgLHqEJRJz0xcwc69SNuLsb O0QNvwfat7m0RH7c2e9RIVzYQJl9CjboA2M6x4deOtZ0w2P4EF2jm4opl 5dRvfhVEO5iIFiEL9pLsHnnuAEG0PaQWO6TD3eBVVuLJ6q6drKGHF7DjF A==;
Received: from s4de8nsazdfe010.bmbg.telekom.de ([10.175.246.202]) by MAILOUT21.telekom.de with ESMTP/TLS/DHE-RSA-AES128-SHA; 28 Oct 2016 10:35:48 +0200
X-IronPort-AV: E=Sophos;i="5.31,557,1473112800"; d="scan'208";a="995609103"
Received: from he104838.emea1.cds.t-internal.com ([10.134.226.69]) by q4de8nsa015.bmbg.telekom.de with ESMTP/TLS/AES256-SHA; 28 Oct 2016 10:40:22 +0200
Received: from HE104834.EMEA1.cds.t-internal.com (172.28.204.43) by HE104838.emea1.cds.t-internal.com (172.28.204.45) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Fri, 28 Oct 2016 10:40:22 +0200
Received: from HE104834.EMEA1.cds.t-internal.com ([fe80::dfd:953:f2fd:5b2d]) by HE104834.emea1.cds.t-internal.com ([fe80::dfd:953:f2fd:5b2d%25]) with mapi id 15.00.1210.000; Fri, 28 Oct 2016 10:40:22 +0200
From: <ian.farrer@telekom.de>
To: <l2tpext@ietf.org>
Thread-Topic: New Version Notification for draft-ietf-l2tpext-keyed-v6-tunnel-yang-02.txt
Thread-Index: AQHSMPbrbpM5QLlI606Jeyb5scpWrw==
Date: Fri, 28 Oct 2016 08:40:22 +0000
Message-ID: <05FADFF5-5D7D-482A-856E-8E8C7AD1091D@telekom.de>
References: <147764356272.24948.16837477966660147078.idtracker@ietfa.amsl.com>
In-Reply-To: <147764356272.24948.16837477966660147078.idtracker@ietfa.amsl.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/f.1b.0.161010
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.137.249.66]
Content-Type: text/plain; charset="utf-8"
Content-ID: <D8A04ED9993C9C4E891135E5B9CC19F9@cds.t-internal.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/l2tpext/vb421PEXZJwMuBstEDgUhWwDyWc>
Subject: [L2tpext] FW: 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 08:41:15 -0000

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