Re: [I2nsf] Working Group document adoption

<christian.jacquenet@orange.com> Tue, 12 January 2016 15:13 UTC

Return-Path: <christian.jacquenet@orange.com>
X-Original-To: i2nsf@ietfa.amsl.com
Delivered-To: i2nsf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 030BE1A0127 for <i2nsf@ietfa.amsl.com>; Tue, 12 Jan 2016 07:13:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
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 eL-WjNSpQCeC for <i2nsf@ietfa.amsl.com>; Tue, 12 Jan 2016 07:13:25 -0800 (PST)
Received: from relais-inet.francetelecom.com (relais-ias92.francetelecom.com [193.251.215.92]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8EC091B2A9A for <i2nsf@ietf.org>; Tue, 12 Jan 2016 07:13:24 -0800 (PST)
Received: from omfedm05.si.francetelecom.fr (unknown [xx.xx.xx.1]) by omfedm14.si.francetelecom.fr (ESMTP service) with ESMTP id B78A222C6CA; Tue, 12 Jan 2016 16:13:22 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [10.114.31.31]) by omfedm05.si.francetelecom.fr (ESMTP service) with ESMTP id 9913335C060; Tue, 12 Jan 2016 16:13:22 +0100 (CET)
Received: from OPEXCLILMA3.corporate.adroot.infra.ftgroup ([fe80::60a9:abc3:86e6:2541]) by OPEXCLILM22.corporate.adroot.infra.ftgroup ([fe80::8c90:f4e9:be28:2a1%19]) with mapi id 14.03.0279.002; Tue, 12 Jan 2016 16:13:22 +0100
From: christian.jacquenet@orange.com
To: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "i2nsf@ietf.org" <i2nsf@ietf.org>
Thread-Topic: [I2nsf] Working Group document adoption
Thread-Index: AdFMfpIrlSnoJPdlT7SaF1vgplQ0mf//8i+A//5YKAA=
Date: Tue, 12 Jan 2016 15:13:21 +0000
Message-ID: <19094_1452611602_56951812_19094_2943_1_88132E969123D14D9BD844E1CD516EDE12FB5D72@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
References: <00bc01d14c7e$95eb9690$c1c2c3b0$@olddog.co.uk> <00c501d14c80$0d1ffca0$275ff5e0$@olddog.co.uk>
In-Reply-To: <00c501d14c80$0d1ffca0$275ff5e0$@olddog.co.uk>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.168.234.3]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 6.2.1.2478543, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2016.1.12.143316
Archived-At: <http://mailarchive.ietf.org/arch/msg/i2nsf/8guaJ1Ga3nIW8me8PS7R3slghv8>
Subject: Re: [I2nsf] Working Group document adoption
X-BeenThere: i2nsf@ietf.org
X-Mailman-Version: 2.1.15
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: Tue, 12 Jan 2016 15:13:27 -0000

Dear all,

I too support the adoption of both drafts as i2nsf WG documents. I also second the said compacting strategy as well as Dan's comments about the appropriate track for these documents.

Cheers,

Christian.
> -----Original Message-----
> From: I2nsf [mailto:i2nsf-bounces@ietf.org] On Behalf Of Adrian Farrel
> Sent: 11 January 2016 14:45
> To: i2nsf@ietf.org
> Subject: [I2nsf] Working Group document adoption
> 
> Hi Working group,
> 
> We had a working group milestone before Christmas to "Adopt use Cases, 
> problem statement, and gap analysis as WG document".
> 
> Per the discussions in Yokohama, we struggled to compact all of this
information
> into a single document and plan to move ahead with two documents. The 
> first is
a
> combined problem statement and use case document, the second is a gap 
> analysis of existing IETF technologies.
> 
> We checked with the AD and she is happy that we take this approach.
> 
> Sue has been working on this and has posted 
> https://datatracker.ietf.org/doc/draft-hares-i2nsf-merged-problem-use-
> cases/
> and
> https://datatracker.ietf.org/doc/draft-hares-i2nsf-gap-analysis/
> 
> These replace
> https://datatracker.ietf.org/doc/draft-hares-i2nsf-use-case-gap-analys
> is/
> 
> There was some small discussion on the list raising some points that 
> may be addressed, but I think we can carry on, so this email starts a 
> two week poll
for
> adoption of these documents as working group drafts. The poll will end 
> on January 25th.
> 
> Please read the documents and express an opinion one way or another, 
> preferably giving a reason for your thoughts.
> 
> Since Linda is a co-author of 
> draft-hares-i2nsf-merged-problem-use-cases, I
will
> call consensus on that document.
> 
> Thanks,
> Adrian
> 
> _______________________________________________
> I2nsf mailing list
> I2nsf@ietf.org
> https://www.ietf.org/mailman/listinfo/i2nsf

_______________________________________________
I2nsf mailing list
I2nsf@ietf.org
https://www.ietf.org/mailman/listinfo/i2nsf

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.