Re: [yang-doctors] Need YANG Doctor reviewing the YANG module of draft-ietf-i2nsf-sdn-ipsec-flow-protection which I2NSF is about to call WGLC

"Mehmet Ersue" <mersue@gmail.com> Sat, 06 April 2019 10:53 UTC

Return-Path: <mersue@gmail.com>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 401C21200DF; Sat, 6 Apr 2019 03:53:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 4gOI91F_lVUd; Sat, 6 Apr 2019 03:53:24 -0700 (PDT)
Received: from mail-wr1-x432.google.com (mail-wr1-x432.google.com [IPv6:2a00:1450:4864:20::432]) (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 B64DB120045; Sat, 6 Apr 2019 03:53:23 -0700 (PDT)
Received: by mail-wr1-x432.google.com with SMTP id w10so10788470wrm.4; Sat, 06 Apr 2019 03:53:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-language:thread-index; bh=nMO93lWFss2c2APVfyH4/cxAlSeh/9T+21SB4DIvTXw=; b=R2VMXZzse33tcEuvoVs7LX36SrKMLcnPUawl+ho0+YF8YNdFeJvAhIkPv3f1ZWoxr3 EnJ8ESYM3BoHbnsP9WWByFUl1bczwYDN9SP3tr3ONXOVZ0ibP03ip8XxWspii161t2zU 9eafHpFyESjs8OhFLWHAefG6htFeFAztBPcbu01uNdP/LUVkUtc7up/GdO5qu21c5z3j rco6M3vsTTvAroj/qxBRaKYGgmfNmuEFz7Ml0MnLbHuSam6MmfIYdVbv5DVI8fCTrVS2 R37a1mQgCGfMwYbfDHgI1F/EoBdXTAnlrOxJkqDoRCDUOzSMFmvzJnMJ5VSQym1K4K14 MFyg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:references:in-reply-to:subject:date :message-id:mime-version:content-language:thread-index; bh=nMO93lWFss2c2APVfyH4/cxAlSeh/9T+21SB4DIvTXw=; b=CPHQ6BFjwATnNgMs9/j9fw8719MqxXQKpzTDtt4EEnAz02QVtS1/RC7GIX9+7JPiI8 EvcT1dIlZE4+WPOfDqfBoAUUYSbDGw6o0huvSWCScYzIslA1C7Mm1HglUOeG8r2XgE33 wET5DOSF3bkr2j3uB65crXRUU/raVcTwxMF+atbKgiU4/hmMqqpuV8B8SeJBPIVp01GM GJwKrcMYKNtLZtscFh1Cq1fB15cucvwUnm1PrTNVuDd6iXMHVyhojaD0b/NATc9D5ydv eUlm065tvqH7xZAkYtNOtCIBD/bgDzJK37ylBJO9rPpkjTNiBIGzBU9FLOIMlDeB5I+J o7wQ==
X-Gm-Message-State: APjAAAWsE55wW/TZSD+UJ76q1UowxuEGhnyXB92mXjGwqTUjAvvlVA/8 o2/85qv9n4G7JCnq73PrePE=
X-Google-Smtp-Source: APXvYqyrPCGmSuA8ByLaVfzAk/71bJw+Ys32HlKCcicYxsv9Vpi2EeFyQmeuNnOzTbK1tU0KJC+fhQ==
X-Received: by 2002:adf:eb84:: with SMTP id t4mr5302131wrn.43.1554548002142; Sat, 06 Apr 2019 03:53:22 -0700 (PDT)
Received: from DESKTOPFLHJVQJ (200116b82b8a0c00204a0da0139e22fe.dip.versatel-1u1.de. [2001:16b8:2b8a:c00:204a:da0:139e:22fe]) by smtp.gmail.com with ESMTPSA id r30sm72944387wrr.46.2019.04.06.03.53.20 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 06 Apr 2019 03:53:21 -0700 (PDT)
From: "Mehmet Ersue" <mersue@gmail.com>
To: "'Linda Dunbar'" <linda.dunbar@huawei.com>, <yang-doctors@ietf.org>
Cc: "'Yoav Nir'" <ynir.ietf@gmail.com>, <wgchairs@ietf.org>
References: <4A95BA014132FF49AE685FAB4B9F17F66B363EB2@sjceml521-mbs.china.huawei.com>
In-Reply-To: <4A95BA014132FF49AE685FAB4B9F17F66B363EB2@sjceml521-mbs.china.huawei.com>
Date: Sat, 6 Apr 2019 12:53:19 +0200
Message-ID: <00ad01d4ec66$f3200bd0$d9602370$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_00AE_01D4EC77.B6AB4CD0"
X-Mailer: Microsoft Outlook 16.0
Content-Language: de
Thread-Index: AQFgD0gaKN2GyC6482NgWA4JOjrAOqcYqnxQ
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/ShWjLUbNC_GePHMzjcSAShtRs50>
Subject: Re: [yang-doctors] Need YANG Doctor reviewing the YANG module of draft-ietf-i2nsf-sdn-ipsec-flow-protection which I2NSF is about to call WGLC
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Email list of the yang-doctors directorate <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 06 Apr 2019 10:53:26 -0000

Dear Linda,

 

following our process I would like to ask you to request a YANG Doctors
review on the datatracker page of your draft at:

https://datatracker.ietf.org/doc/draft-ietf-i2nsf-sdn-ipsec-flow-protection/


This will trigger a regular review by the YANG Doctors.

 

Note: You will not see the "Request review" button if you are not logged in
into the datatracker.

 

To point the reviewer to important issues you can enter on this page also
the "Requester's comments and instructions".

 

Please see following pages for further information on YANG Doctors and its
process:

https://datatracker.ietf.org/group/yangdoctors/about/

https://trac.ietf.org/trac/ops/wiki/yang-doctors-review

 

Many Thanks,

Mehmet

YANG Doctors Secretary

 

From: yang-doctors <yang-doctors-bounces@ietf.org>; On Behalf Of Linda Dunbar
Sent: Friday, April 5, 2019 6:51 PM
To: yang-doctors@ietf.org
Cc: i2nsf@ietf.org
Subject: [yang-doctors] Need YANG Doctor reviewing the YANG module of
draft-ietf-i2nsf-sdn-ipsec-flow-protection which I2NSF is about to call WGLC

 

Dear YANG Doctor:

 

We need your help in reviewing the YANG model in
draft-ietf-i2nsf-sdn-ipsec-flow-protection which I2NSF WG is about to call
WGLC. 

 

In particular, we need your advice on the following issue:

 

draft-ietf-i2nsf-sdn-ipsec-flow-protection-04 imports from
draft-ietf-netconf-crypto-types, which appears to be a generic list of
algorithms. 

The problem is that the list in draft-ietf-netconf-crypto-types could
contain algorithms that are not suitable for IPsec (such as secp192r1 for
key agreement), and right now it seems to lack some older algorithms that
have fallen out of fashion (3DES) but is still needed in IPsec.  

 

 

Questions to the YANG Doctor:

1.	 Is it better to list the IPsec specific algorithms in
draft-ietf-i2nsf-sdn-ipsec-flow-protection (which is a subset of
draft-ietf-netconf-crypto-types? Or to import all crypto algorithms many of
which are not relevant to IPsec? What is the common practice? 
2.	If we do import from draft-ietf-netconf-crypto-types, does it mean
draft-ietf-i2nsf-sdn-ipsec-flow-protection cannot be published until
draft-ietf-netconf-crypto-types is published?

 

 

Thank you very much, 

 

Linda & Yoav