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

Daniel Migault <daniel.migault@ericsson.com> Mon, 28 March 2016 20:43 UTC

Return-Path: <mglt.ietf@gmail.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 8A53312DB1C for <ipsec@ietfa.amsl.com>; Mon, 28 Mar 2016 13:43:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.399
X-Spam-Level:
X-Spam-Status: No, score=-2.399 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.199, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=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 qW_o62Nox3cC for <ipsec@ietfa.amsl.com>; Mon, 28 Mar 2016 13:43:55 -0700 (PDT)
Received: from mail-wm0-x22c.google.com (mail-wm0-x22c.google.com [IPv6:2a00:1450:400c:c09::22c]) (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 4F9EC12D179 for <ipsec@ietf.org>; Mon, 28 Mar 2016 13:43:55 -0700 (PDT)
Received: by mail-wm0-x22c.google.com with SMTP id p65so111756644wmp.0 for <ipsec@ietf.org>; Mon, 28 Mar 2016 13:43:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc; bh=o5c1IoJiRpDqirNIFJrSkdp4WozDozXQMHlv1t+ihsA=; b=J8QwwnPbp7v0gKUzr3Yyh0kmkSUTTAMUHoAFeIU0ByokP5ab/LWBh+T/y+JVeC30Bg hehffTD0tKTc6yXiHXyLm0LpRUaKGyGXEMrfz+QA0s3EEph4ITvquoseR5Mux27QhD0n XfF2iIjcVQYa/1OyOoX+ml8IG9jR0R4nMHA8xjZicXPYSZ/dxzP9nSJfsxaRfF3/ggI1 y+5D5ryEyW5auU6xvUAfSD5Lh9l+WLsA24NPTtgVoPxNcvALRwNHPwM1HXMJr6XPTcJ3 2QayEp3vn4Mmtrz4nYDPkEouRbzhHJAVPsMiYQyjvvLNXEVUcPe6xjEje/v+5FPct7lR j/MA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc; bh=o5c1IoJiRpDqirNIFJrSkdp4WozDozXQMHlv1t+ihsA=; b=MhaRfReR0Pxanrdg/MPK54Gfc3QW7j62iyfV/KWlMOrwUZ83+/9JSvgcVgRB3djhti LcP5xNmhWPSUfajpwF3UkbziM8MxtDHtIcnUTyKeZNL15QmCbizf2s8txcHNUGp+AkOJ IU4ejOLUs8qUDVHT1gHqXuu/sEGLeVGNc1gBIQyHuiIdvIwVfwKxRepvXr3mGj+gR2ib sOwzQwZ6DHbC1I5g3Spfe4rm7fGIqsuNgOowjqz4cGmJRkpP5sFS1iB0+PlT8y3V/YrO W+3Auaj9RErx4RZlbGr018vdtmT2dgN2UVCrjLIMkfug5Prna2GZaD+IuvGxsb/bQTNa lL8A==
X-Gm-Message-State: AD7BkJJXdMMpxbxaAz+aHLde7lfS5Sg/5gPBsd0y+rl0kODhfuIRT7gpuU7U8sbMJlwkdPNzsl6dfoUWZbK49A==
MIME-Version: 1.0
X-Received: by 10.194.3.110 with SMTP id b14mr30427869wjb.116.1459197833614; Mon, 28 Mar 2016 13:43:53 -0700 (PDT)
Sender: mglt.ietf@gmail.com
Received: by 10.194.78.171 with HTTP; Mon, 28 Mar 2016 13:43:53 -0700 (PDT)
In-Reply-To: <alpine.LFD.2.20.1603271819220.22991@bofh.nohats.ca>
References: <20160318180059.2743.10884.idtracker@ietfa.amsl.com> <2D1BA3CFD799FD44A1F3650A84C4000F1231AFBC@eusaamb107.ericsson.se> <2DD56D786E600F45AC6BDE7DA4E8A8C11222B1D5@eusaamb108.ericsson.se> <alpine.LFD.2.20.1603271819220.22991@bofh.nohats.ca>
Date: Mon, 28 Mar 2016 17:43:53 -0300
X-Google-Sender-Auth: 65qWWWP4wYP627lTxZNHBgEcR0Q
Message-ID: <CADZyTknEeWdwE17=PJXs4Z4ae29FQB74psKbxrX82rzNi4Ndpw@mail.gmail.com>
From: Daniel Migault <daniel.migault@ericsson.com>
To: Paul Wouters <paul@nohats.ca>
Content-Type: multipart/alternative; boundary="047d7b33dc50879e01052f21f8dd"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipsec/5cYA7oiWZ81W6qrA3V4M_PZsvq4>
Cc: "ipsec@ietf.org WG" <ipsec@ietf.org>
Subject: Re: [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: Mon, 28 Mar 2016 20:43:57 -0000

Hi Paul,

I leave my co-authors to respond on the YANG aspects.

Regarding the initial-retransmission-timeout I think we meant a time in
second. Do you think we need more options?

BR,
Daniel

On Mon, Mar 28, 2016 at 11:29 AM, Paul Wouters <paul@nohats.ca> wrote:

> On Sun, 27 Mar 2016, Daniel Migault wrote:
>
> Subject: [IPsec] FW: New Version Notification for
>>     draft-tran-ipsecme-ikev2-yang-00.txt
>>
>
> Please find our first version for the YANG model for IKEv2. Feel free
>> to post comments. I would be also happy to have face-to-face
>> discussions on the draft - especially from IKEv2 implementers.
>>
>
> Might be good for me to have a talk about it, especially because I'm
> not a yang person. . I'm still a bit confused about the syntax. There is
> code in the document that looks like "ready to use" but also looks like
> "example to use". like:
>
>   description
>        "This YANG module defines the configuration and operational
>         state data for Internet Key Exchange version 2 (IKEv2) on
>         IETF draft.
>         Copyright (c) 2016 Ericsson AB.
>         All rights reserved.";
>
> All rights reserved? huh? Is that an example? or is this an error?
>
> I'm confused about units too, like:
>
>   leaf initial-retransmission-timeout {
>            type uint32;
>            description
>              "initial retransmission timeout value";
>          }
>
> look weird to me. What's the unit here? uint32 is not a unit, it is
> a number Is this seconds? miliseconds? seconds since 1970? Since 1772?
>
> Some of it looks like just copying IANA registries? So that would be
> outdated quickly. How would that get updated? Should we really put
> chunks of code in RFCs like that?
>
> Paul
>
>
> _______________________________________________
> IPsec mailing list
> IPsec@ietf.org
> https://www.ietf.org/mailman/listinfo/ipsec
>