Re: [IPsec] Candidate charter text is now in wiki

Yoav Nir <ynir.ietf@gmail.com> Fri, 09 February 2018 17:53 UTC

Return-Path: <ynir.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 D0F95120454 for <ipsec@ietfa.amsl.com>; Fri, 9 Feb 2018 09:53:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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, 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 XmrJC-rsG-vL for <ipsec@ietfa.amsl.com>; Fri, 9 Feb 2018 09:53:43 -0800 (PST)
Received: from mail-wr0-x236.google.com (mail-wr0-x236.google.com [IPv6:2a00:1450:400c:c0c::236]) (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 32B051201F8 for <ipsec@ietf.org>; Fri, 9 Feb 2018 09:53:43 -0800 (PST)
Received: by mail-wr0-x236.google.com with SMTP id o76so5958526wrb.7 for <ipsec@ietf.org>; Fri, 09 Feb 2018 09:53:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=SVtU7nqN912+ZzMO2laKm3j7nYHN/9IsHCvhdYODP/w=; b=Hz564+bstIorxewZngoYTnPO1scXt4Qmnzxr1Hha6T5L5pATG9+L4rQb+0v8SVtoo5 mW+nq/JOZOoNHHEdK9AAIG6S95p7p5DVYCt2cI8Y+CC1hwGweesM7cw/A1QIez1pC36k dxJDl9cQ4LOmAdsYlE397LIjHIYazsDmwtGyNHUfimgDSY7XQ/PWIN/RXcQlpvSNmN1l Ez8hrCVyn5Lf1Krp/IHJjXY0zD8XJcAxheEeQXX39BOGNMR9IpyBX95heUkjqoVkaLHW NVo0M16VFEUVmMgTcBJbHf7hGluyOIiQXx/jRwIDpMGS2YsNzMQ28ytbhpLUQ6IeZQgv +l0w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=SVtU7nqN912+ZzMO2laKm3j7nYHN/9IsHCvhdYODP/w=; b=BZdgyty8TMVn+7wDTaBpChZn6rtIIXTqOKcTdL8K7NMbn20EWIdAP77wOIrMJ7Y9bL mYCB7YAs463xw6OxK58vlixN1UFFyA3WanCKEddZoTjYUk/0iSyd9yGG9z9sM5jABlIq fQwt7YuAIGIuRNTkTrqqm+gvUQ9T2r++Xfl8K6dnnyMTbz7LR7CW9j6P9YUBDeiGrzGG 92x7IdunvFs9xlhe6/q8nhdTTlZJhC6f7SAypZkwUoNpEOxZw8XixquLzmgwqehvlEoB oYcWtS1esHQr9q8WPDyf2fUPjBYmbPn+NdLwnQZgjR5cDCpbkyeQteSWl3yBESFwEfa3 Q5Bw==
X-Gm-Message-State: APf1xPDTTti8KAhBiXr0KGJvyAX+brzXLbm9vbaqbW9BZp/jkFnIsTy+ CBS9rAVM8uLBhCWqcnGzhgzrgbSS
X-Google-Smtp-Source: AH8x225w7hny8bIisWqrYYj84WDzytXJZj8TXihSFR6jVj+5ThdUZXpKjrRhU8bT+Fzgr+6gQw+3YQ==
X-Received: by 10.223.169.182 with SMTP id b51mr3022861wrd.244.1518198821743; Fri, 09 Feb 2018 09:53:41 -0800 (PST)
Received: from [192.168.1.18] ([46.120.57.147]) by smtp.gmail.com with ESMTPSA id 4sm2472386wmz.31.2018.02.09.09.53.40 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 09 Feb 2018 09:53:40 -0800 (PST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\))
From: Yoav Nir <ynir.ietf@gmail.com>
In-Reply-To: <alpine.LRH.2.21.1802091138320.14532@bofh.nohats.ca>
Date: Fri, 09 Feb 2018 19:53:38 +0200
Cc: "ipsec@ietf.org" <ipsec@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <D676AE5F-7C01-476B-AC52-CBC99B825C78@gmail.com>
References: <23054.29098.665202.402605@fireball.acr.fi> <787AE7BB302AE849A7480A190F8B93300A07C37A@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <23161.62855.158031.367282@fireball.acr.fi> <787AE7BB302AE849A7480A190F8B93300A0CC90D@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <23162.53065.405334.393026@fireball.acr.fi> <alpine.LRH.2.21.1802091138320.14532@bofh.nohats.ca>
To: Paul Wouters <paul@nohats.ca>
X-Mailer: Apple Mail (2.3445.5.20)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipsec/wJi8S3cikjNKIKHAZcWMVBhVR7g>
Subject: Re: [IPsec] Candidate charter text is now in wiki
X-BeenThere: ipsec@ietf.org
X-Mailman-Version: 2.1.22
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: Fri, 09 Feb 2018 17:53:45 -0000


> On 9 Feb 2018, at 18:40, Paul Wouters <paul@nohats.ca> wrote:
> 
> On Wed, 7 Feb 2018, Tero Kivinen wrote:
> 
>> It depends. If we do not take the item as official working group
>> chartered item, there are still few different options. You can either
>> get it processed as AD sponsored draft, or you can go individual
>> submission track.
> 
> It is a little strange we don't have an ops group for ipsec. The IPsecME
> group really functions as such.

Are there any work items to add to the charter of this group or a dedicated ops group?

I don’t remember any draft about how you’d go about deploying IPsec either in VPN or within a datacenter. Certainly not at scale. 

There is the work in I2NSF for the datacenter and there are some “software defined WAN” products that use IPsec for VPN, but the latter is not standardised.

Yoav