Re: [I2nsf] Call for adoption of draft-abad-i2nsf-sdn-ipsec-flow-protection

Yoav Nir <ynir.ietf@gmail.com> Mon, 02 October 2017 21:58 UTC

Return-Path: <ynir.ietf@gmail.com>
X-Original-To: i2nsf@ietfa.amsl.com
Delivered-To: i2nsf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EAF891348F5; Mon, 2 Oct 2017 14:58:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level:
X-Spam-Status: No, score=-2.698 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_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=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 0zq2GK8eoGSw; Mon, 2 Oct 2017 14:58:44 -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 A77FE124B18; Mon, 2 Oct 2017 14:58:43 -0700 (PDT)
Received: by mail-wm0-x22c.google.com with SMTP id b189so9265921wmd.4; Mon, 02 Oct 2017 14:58:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=ZP5u2hVSkNGkg5GVHW5yX/8ZdVHNJctWBxiaV7nx7BM=; b=T8K15ovI+OTAjsii4v5bwH3F7/1LjZNiW3TTKsjO6J0GBoROuM+nVsfx1QbTHTv/4N GumHaYVDs8yH7JXptmznMU1muYfrzml5az8VFODRmozUr0PDvWeL1SSKo4/ITiwRMGRM rnLMQyhUxu/ACXLkiXDx2J2CiUWdcaux5lrbCtWDBeJBbhQX4Qcg58nk6Of/VH0DZmTN YavD/LTpVUT+lGWwm2GxftgsY3eBS8EPRwzAOtk6QTmETEkGEFxaFFejK2iUrv43SiPS Yi46JjmDNBhblvPSmpWNDLx/3LBDrhilVUNwREm8WKJTR25L7KRq35/+TFY2oEHwZtWj SlZQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=ZP5u2hVSkNGkg5GVHW5yX/8ZdVHNJctWBxiaV7nx7BM=; b=h4akVgUeh6e6ygOMO1vpdGyAu9Qo9WiUNX2s5VurDldLQXvPTDYdFDtZCV/bUT5UHm 1qDyPIbI30Q1eRwuSc35ZNMc7ZxupueBEQVp/9zKDhDtfUN+u1PcryZM2Gu8916WiBuG OVZyIEbzVW+uAoTGD8QRSmLZbHpqk8UNQ1wgY/PHjTQe8/zNz2bE4NxQR5kxSwIK6BKS Pts2egn4oosFOsmiEEuwvKztU7MTwr9NR16ZG5nVYgyUKWK4U5G+rXGP8E3n48Z/ogu7 K3S5kk8dNJMD1fP6gF797sw5BFNuiw4e5GPpkQd0eayuVJjbzzpGmagF8VaSX12Ssgqj Mi5g==
X-Gm-Message-State: AHPjjUjBHuPytYN+fFsZbP05nWjgVVez/bk9vhNomkas/fQAwZxl1RU5 rCR9dYKVA57UC2mt8+XpdUe5U/Ec
X-Google-Smtp-Source: AOwi7QD73P9bpwRs36VqKSHrKFhbcOWn5E9swtKNrk1xowBFfRRvXpMjyMmDayAPPkzlVpLzsYw2GA==
X-Received: by 10.80.179.247 with SMTP id t52mr21271335edd.237.1506981521976; Mon, 02 Oct 2017 14:58:41 -0700 (PDT)
Received: from [192.168.1.18] ([46.120.57.147]) by smtp.gmail.com with ESMTPSA id a10sm10767721eda.37.2017.10.02.14.58.40 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 02 Oct 2017 14:58:41 -0700 (PDT)
From: Yoav Nir <ynir.ietf@gmail.com>
Message-Id: <69785799-3C40-4D51-B468-12A9672ACBD4@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_AE333B15-A590-493B-8CB4-5466C4EF8DCE"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Date: Tue, 03 Oct 2017 00:58:38 +0300
In-Reply-To: <79CC25F6-4B4D-4171-9DB7-274C629D38FE@gmail.com>
Cc: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>, draft-abad-i2nsf-sdn-ipsec-flow-protection@ietf.org
To: i2nsf@ietf.org
References: <79CC25F6-4B4D-4171-9DB7-274C629D38FE@gmail.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/7ho623Gva4_472J6OTCTJwuA_Pg>
Subject: Re: [I2nsf] Call for adoption of draft-abad-i2nsf-sdn-ipsec-flow-protection
X-BeenThere: i2nsf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "*I2NSF: Interface to Network Security Functions mailing list*" <i2nsf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/i2nsf>, <mailto:i2nsf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/i2nsf/>
List-Post: <mailto:i2nsf@ietf.org>
List-Help: <mailto:i2nsf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i2nsf>, <mailto:i2nsf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Oct 2017 21:58:46 -0000

Hi all.

Thank you all for chiming in. The response was mostly positive, and we judge that there is consensus to adopt this draft.

Authors: please re-submit as draft-ietf-i2nsf-ipsec-flow-00  .

During the call for adoption there was a suggestion to split the draft in two.  Because “case 2” (where the controller installs SAs with traffic keys) is controversial whereas “case 1” (where the controller only installs credentials and PAD entries) is not, it was suggested to make case 2 a separate document.  This could well be a decision we will make in the future, but for now Linda and I believe that this is not a good idea.  If the document is split, it means we also have to split the YANG models, creating two separate languages to perform the same task. There would be little point in having an SAD model in the case 1 document, and each document would need different versions of the PAD model.

For the time being, let’s have a single document. If the security posture is different, this can be covered in the text itself. Note again that this decision is not final or binding and the group may decide to change it before we finish with this document.

Thanks again.

Yoav

> On 15 Sep 2017, at 11:09, Yoav Nir <ynir.ietf@gmail.com> wrote:
> 
> Hi all
> 
> This starts a two-week call for adoption of draft-abad-i2nsf-sdn-ipsec-flow-protection. Please send in your comments both for and against adopting this as a working group document by EOD Monday, October 2nd.  As always, adoption by the working group does not require consensus on the details, and the group will have plenty of time to discuss the contents and modify them as appropriate.
> 
> This draft was proposed a while ago, and the interim meeting earlier this month was dedicated to discussing its issues. For more information:
> The draft: https://datatracker.ietf.org/doc/draft-abad-i2nsf-sdn-ipsec-flow-protection/ <https://datatracker.ietf.org/doc/draft-abad-i2nsf-sdn-ipsec-flow-protection/>
> The minutes of the interim meeting: https://datatracker.ietf.org/meeting/interim-2017-i2nsf-01/materials/minutes-interim-2017-i2nsf-01-201709061600/ <https://datatracker.ietf.org/meeting/interim-2017-i2nsf-01/materials/minutes-interim-2017-i2nsf-01-201709061600/>
> 
> Thanks
> 
> Yoav