Re: [I2nsf] Well done: RFC 8192 on Interface to Network Security Functions (I2NSF): Problem Statement and Use Cases

"Susan Hares" <shares@ndzh.com> Wed, 26 July 2017 19:34 UTC

Return-Path: <shares@ndzh.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 D8EE3126CD6 for <i2nsf@ietfa.amsl.com>; Wed, 26 Jul 2017 12:34:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.945
X-Spam-Level:
X-Spam-Status: No, score=0.945 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845] autolearn=no autolearn_force=no
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 RysByTyJDnLb for <i2nsf@ietfa.amsl.com>; Wed, 26 Jul 2017 12:34:49 -0700 (PDT)
Received: from hickoryhill-consulting.com (50-245-122-97-static.hfc.comcastbusiness.net [50.245.122.97]) (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 9F6AF131473 for <i2nsf@ietf.org>; Wed, 26 Jul 2017 12:34:47 -0700 (PDT)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=70.194.20.65;
From: Susan Hares <shares@ndzh.com>
To: adrian@olddog.co.uk, i2nsf@ietf.org
References: <008701d30645$08285f50$18791df0$@olddog.co.uk>
In-Reply-To: <008701d30645$08285f50$18791df0$@olddog.co.uk>
Date: Wed, 26 Jul 2017 15:28:38 -0400
Message-ID: <005c01d30645$61ea9530$25bfbf90$@ndzh.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQD1tt1dAYhEyIk6GpxZdF+AApsyWaQhHM2w
Content-Language: en-us
X-Authenticated-User: skh@ndzh.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/mldRj88JC8PFMu-z1I3bjiOvgkg>
Subject: Re: [I2nsf] Well done: RFC 8192 on Interface to Network Security Functions (I2NSF): Problem Statement and Use Cases
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: Wed, 26 Jul 2017 19:34:52 -0000

+1 - 3 Cheers for the I2NSF WG. Adrian observed in our first meeting that
this WG is one of the best working groups for collaboration!  We have
reached success together. 

Sue 

-----Original Message-----
From: I2nsf [mailto:i2nsf-bounces@ietf.org] On Behalf Of Adrian Farrel
Sent: Wednesday, July 26, 2017 3:26 PM
To: i2nsf@ietf.org
Subject: [I2nsf] Well done: RFC 8192 on Interface to Network Security
Functions (I2NSF): Problem Statement and Use Cases

Was hoping this would be out while we were in Prague, so we could celebrate.

But well done anyway.

Adrian

> -----Original Message-----
> From: I2nsf [mailto:i2nsf-bounces@ietf.org] On Behalf Of 
> rfc-editor@rfc- editor.org
> Sent: 26 July 2017 03:20
> To: ietf-announce@ietf.org; rfc-dist@rfc-editor.org
> Cc: i2nsf@ietf.org; drafts-update-ref@iana.org; 
> rfc-editor@rfc-editor.org
> Subject: [I2nsf] RFC 8192 on Interface to Network Security Functions
(I2NSF):
> Problem Statement and Use Cases
> 
> A new Request for Comments is now available in online RFC libraries.
> 
> 
>         RFC 8192
> 
>         Title:      Interface to Network Security Functions
>                     (I2NSF): Problem Statement and Use Cases
>         Author:     S. Hares, D. Lopez,
>                     M. Zarny, C. Jacquenet,
>                     R. Kumar, J. Jeong
>         Status:     Informational
>         Stream:     IETF
>         Date:       July 2017
>         Mailbox:    shares@ndzh.com,
>                     diego.r.lopez@telefonica.com,
>                     myo@varmour.com,
>                     christian.jacquenet@orange.com,
>                     rakeshkumarcloud@gmail.com,
>                     pauljeong@skku.edu
>         Pages:      29
>         Characters: 66651
>         Updates/Obsoletes/SeeAlso:   None
> 
>         I-D Tag:    draft-ietf-i2nsf-problem-and-use-cases-16.txt
> 
>         URL:        https://www.rfc-editor.org/info/rfc8192
> 
>         DOI:        10.17487/RFC8192
> 
> This document sets out the problem statement for Interface to Network 
> Security Functions (I2NSF) and outlines some companion use cases.
> 
> This document is a product of the Interface to Network Security 
> Functions Working Group of the IETF.
> 
> 
> INFORMATIONAL: This memo provides information for the Internet community.
> It does not specify an Internet standard of any kind. Distribution of 
> this memo is unlimited.
> 
> This announcement is sent to the IETF-Announce and rfc-dist lists.
> To subscribe or unsubscribe, see
>   https://www.ietf.org/mailman/listinfo/ietf-announce
>   https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
> 
> For searching the RFC series, see https://www.rfc-editor.org/search 
> For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
> 
> Requests for special distribution should be addressed to either the 
> author of the RFC in question, or to rfc-editor@rfc-editor.org.  
> Unless specifically noted otherwise on the RFC itself, all RFCs are 
> for unlimited distribution.
> 
> 
> The RFC Editor Team
> Association Management Solutions, LLC
> 
> 
> _______________________________________________
> 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