IETF Logo Mail Archive

Re: [sfc] SFC Security

christian.jacquenet@orange.com Tue, 02 June 2020 06:41 UTC

Return-Path: <christian.jacquenet@orange.com>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A59ED3A085C for <sfc@ietfa.amsl.com>; Mon, 1 Jun 2020 23:41:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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=orange.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 J_TGi20Sa0S8 for <sfc@ietfa.amsl.com>; Mon, 1 Jun 2020 23:41:17 -0700 (PDT)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.70.34]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 237F43A085B for <sfc@ietf.org>; Mon, 1 Jun 2020 23:41:17 -0700 (PDT)
Received: from opfednr04.francetelecom.fr (unknown [xx.xx.xx.68]) by opfednr20.francetelecom.fr (ESMTP service) with ESMTP id 49bj9l2Ml5z1ykw for <sfc@ietf.org>; Tue, 2 Jun 2020 08:41:15 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orange.com; s=ORANGE001; t=1591080075; bh=YrfWLv9QztUChz+GkWNXogn0Fr1AB7WNRuBCk9iuvfo=; h=From:To:Subject:Date:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=trwp+J5HSSwYIWAIm0wOS72MLBpTKQp7CM24VkfYYmdE8YrPPCyubOB8QqfmfN7MX z7UvPC7bNL13LyF0QPzqqhjwc4ix/djG6CbNb5R1oXz52PSNhEBlae+eGA5McleVEH ZBTpGKCCJwqhyv+N9wujMZCM+y2CHR2KSyY5XM+vvQTLvD2j1o4JAZDmAG2+guFwoM 4AwCpXWBvr4R7aX4JBeUqU58pxJnk99934MSR2WFHWD3OA3LbqOc3Zc8fv7oi3ZXQ0 tiDFXq1j/vK1I4jckBInJFulSC7FczsuMA6fJQPX8FAa1XrtdhuAk9maa+IIx07UnZ mOhzV7zgj5Igg==
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.95]) by opfednr04.francetelecom.fr (ESMTP service) with ESMTP id 49bj9l1nXgz1xp4 for <sfc@ietf.org>; Tue, 2 Jun 2020 08:41:15 +0200 (CEST)
From: christian.jacquenet@orange.com
To: "sfc@ietf.org" <sfc@ietf.org>
Thread-Topic: [sfc] SFC Security
Thread-Index: AQHWNDyhdYdIRXesZE2p3BoAuJreA6i9jGgAgAdcVfA=
Date: Tue, 02 Jun 2020 06:41:14 +0000
Message-ID: <11211_1591080075_5ED5F48B_11211_336_1_88132E969123D14D9BD844E1CD516EDE3B569120@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
References: <9c712682-75ee-f6ea-3355-af2271fc0d75@joelhalpern.com> <787AE7BB302AE849A7480A190F8B9330314C791A@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
In-Reply-To: <787AE7BB302AE849A7480A190F8B9330314C791A@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.114.13.245]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/sfc/eEoLtsuVEJjI4NPsN8b1F1rDF1Y>
Subject: Re: [sfc] SFC Security
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Network Service Chaining <sfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sfc>, <mailto:sfc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sfc/>
List-Post: <mailto:sfc@ietf.org>
List-Help: <mailto:sfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sfc>, <mailto:sfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Jun 2020 06:41:19 -0000

Hello WG,

I too believe draft-rebo-sfc-nsh-integrity is a good start to define security mechanisms for the NSH and therefore suggest this draft should be moved forward.

Cheers,

Christian.

-----Message d'origine-----
De : sfc [mailto:sfc-bounces@ietf.org] De la part de Joel M. Halpern
Envoyé : mercredi 27 mai 2020 17:36
À : sfc@ietf.org
Objet : [sfc] SFC Security

We as a working group hava milestone which the IESG felt was important, 
and which we agreed to work on, to provide security mechanisms for NSH.

We have one individual draft that suggests such mechansims:
https://datatracker.ietf.org/doc/draft-rebo-sfc-nsh-integrity/

Do folks think this is a good start?  A bad start?

For those folks who would like to be working on other things, the chairs 
note that we are very reluctant to engage in new work items until we can 
prove we can complete out commitments.

Yours,
Joel

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

_________________________________________________________________________________________________________________________

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.

v2.23.0 | Report a Bug | By Email