[IPsec] FW: New Version Notification for draft-tran-ipsecme-ikev2-yang-00.txt

Khanh Tran <khanh.x.tran@ericsson.com> Tue, 29 March 2016 20:54 UTC

Return-Path: <khanh.x.tran@ericsson.com>
X-Original-To: ipsec@ietfa.amsl.com
Delivered-To: ipsec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 46C7612D9C2 for <ipsec@ietfa.amsl.com>; Tue, 29 Mar 2016 13:54:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H2=-0.001, 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 Wd8cTvh762Ah for <ipsec@ietfa.amsl.com>; Tue, 29 Mar 2016 13:54:37 -0700 (PDT)
Received: from usplmg21.ericsson.net (usplmg21.ericsson.net [198.24.6.65]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5574112DB93 for <IPsec@ietf.org>; Tue, 29 Mar 2016 13:22:06 -0700 (PDT)
X-AuditID: c6180641-f79fa6d0000057a9-d1-56fae3c957b9
Received: from EUSAAHC001.ericsson.se (Unknown_Domain [147.117.188.75]) by usplmg21.ericsson.net (Symantec Mail Security) with SMTP id C4.17.22441.9C3EAF65; Tue, 29 Mar 2016 22:21:29 +0200 (CEST)
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC001.ericsson.se ([147.117.188.75]) with mapi id 14.03.0248.002; Tue, 29 Mar 2016 16:22:04 -0400
From: Khanh Tran <khanh.x.tran@ericsson.com>
To: "IPsec@ietf.org" <IPsec@ietf.org>
Thread-Topic: [IPsec] FW: New Version Notification for draft-tran-ipsecme-ikev2-yang-00.txt
Thread-Index: AdGJ91d9IonKpe9xR8Kp3mn7UJOXWg==
Date: Tue, 29 Mar 2016 20:22:04 +0000
Message-ID: <2D1BA3CFD799FD44A1F3650A84C4000F1233D4F0@eusaamb107.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [147.117.188.10]
Content-Type: multipart/alternative; boundary="_000_2D1BA3CFD799FD44A1F3650A84C4000F1233D4F0eusaamb107erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrCLMWRmVeSWpSXmKPExsUyuXSPt+7Jx7/CDD69trHYv+UFmwOjx5Il P5kCGKO4bFJSczLLUov07RK4Ms6d+MpWsDm84vpNowbGWz5djJwcEgImEvu2L2eFsMUkLtxb z9bFyMUhJHCUUWJTxyd2CGc5o8S2vevAqtgEdCTOT1/GCGKLCKhKzO54ztzFyMEhLBAhMas1 GCIcK9G5axkThK0ncWn+XRYQmwWo/MLv9+wgNq+Ar0Tb0XVgcUagxd9PrQGrZxYQl7j1ZD4T xEECEkv2nGeGsEUlXj7+B3WoksSkpedYIerzJR6ea2eEmCkocXLmE5YJjEKzkIyahaRsFpIy iLiOxILdn9ggbG2JZQtfM8PYZw48ZkIWX8DIvoqRo7S4ICc33chwEyMw7I9JsDnuYNzb63mI UYCDUYmHN2HlzzAh1sSy4srcQ4wSHMxKIrwFj36FCfGmJFZWpRblxxeV5qQWH2KU5mBREuf9 9vFymJBAemJJanZqakFqEUyWiYNTqoExMXT9zkuGt/UYqk4YhM69OuWYce7OVaJrNZXV1Dfc e+/xsciRQUrxS2xVyYuii3UPJ9r9Pmra9PK5y6bDXzQOumv37/kQnuu+pPv58sKUi7t3rfVS aYj+pTmpzt/O+3DFnwpGL1cvsxtbjXzEtvYIylgqnrocdvZxECN/iHjwrQPzdvI5HGlSYinO SDTUYi4qTgQAOcFDjHcCAAA=
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipsec/VJCL8F90bGdqcjfe-e-TC6E5BGQ>
Subject: [IPsec] FW: New Version Notification for draft-tran-ipsecme-ikev2-yang-00.txt
X-BeenThere: ipsec@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Discussion of IPsec protocols <ipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipsec>, <mailto:ipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipsec/>
List-Post: <mailto:ipsec@ietf.org>
List-Help: <mailto:ipsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipsec>, <mailto:ipsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Mar 2016 20:54:39 -0000

Hi Paul,

Below are my comments to your questions that are relating to draft-tran-ipsecme-ikev2-yang-00.txt.

Q1: What does all right reserved means? I think the question beyond that is how the YANG model can be used, and who owns it? Can you respond to this?
A1: Yes, we will remove the following description:
       " Copyright (c) 2016 Ericsson AB."+
       " All rights reserved.";


Q2:   leaf initial-retransmission-timeout I think that the question is how do we specify units in the YANG model. Is that something that is part of the YANG model? I think we should also ask if the WG would like us to add different ways to express there transmission time out? - I can respond to this question if you prefer.
A2: yes, we can specify the unit for this attribute (I assume the unit will be "miliseconds")
Ex:
         leaf initial-retransmission-timeout {
           type uint32;
           units "miliseconds";
           default 100;
           description
             "initial retransmission timeout value";
         }

         leaf nat-keepalive-interval {
             type uint16 {
               range "5..300";
             }
             units "Seconds";
             default 20;
             description "NAT detected and keepalive interval";
         }


Q3: How YANG can be updated when IANA registries are updated. I think also some text could be added into the draft for that. - Can you respond to this?
A3: yes, we can add the text in the draft for reference to IANA.  When IANA registries are updated, the YANG module should be notified for changes and update accordingly.


Best regards,
Khanh Tran