IETF Logo Mail Archive

Re: [sfc] TR: New Version Notification for draft-rebo-sfc-nsh-integrity-01.txt

"Joel M. Halpern" <jmh@joelhalpern.com> Mon, 04 November 2019 16:04 UTC

Return-Path: <jmh@joelhalpern.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 6C9A1120AC1 for <sfc@ietfa.amsl.com>; Mon, 4 Nov 2019 08:04:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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 (1024-bit key) header.d=joelhalpern.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 OqQ1cMdMV51g for <sfc@ietfa.amsl.com>; Mon, 4 Nov 2019 08:03:59 -0800 (PST)
Received: from maila2.tigertech.net (maila2.tigertech.net [208.80.4.152]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 891DA120ADA for <sfc@ietf.org>; Mon, 4 Nov 2019 08:03:59 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 476HfR3PVmz1x0K3 for <sfc@ietf.org>; Mon, 4 Nov 2019 08:03:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1572883439; bh=JsfdFcR1xaNLsyY2yomS1W0EXhL6/r8wBchfGVgWgcM=; h=Subject:To:References:From:Date:In-Reply-To:From; b=UP4EaykIuPHJPHsUnXR6OFTevyqTyrPd/YItoNh9xByhFjs/IEq74ExpXv2mf02Ee mU+H8VOlC6u93HYmeWDkGQ1dAsOz+UxXzrDKgo7bmisaHD/24/dWvDA3rrme7FFUe1 pLsH6U7R/+sH6LB0YWwZ7Ta96Cvx67qPFAJ69TJM=
X-Virus-Scanned: Debian amavisd-new at maila2.tigertech.net
Received: from [192.168.128.43] (209-255-163-147.ip.mcleodusa.net [209.255.163.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by maila2.tigertech.net (Postfix) with ESMTPSA id 476HfQ6p13z1x0K1 for <sfc@ietf.org>; Mon, 4 Nov 2019 08:03:58 -0800 (PST)
To: "sfc@ietf.org" <sfc@ietf.org>
References: <157288238359.16503.4915397025250194299.idtracker@ietfa.amsl.com> <787AE7BB302AE849A7480A190F8B93303134D9F2@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <3b5bf706-2676-db09-02da-2d2c314c0448@joelhalpern.com>
Date: Mon, 04 Nov 2019 11:03:57 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0
MIME-Version: 1.0
In-Reply-To: <787AE7BB302AE849A7480A190F8B93303134D9F2@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/sfc/Pi_N9Jr9IhQPazEvxJcbOLzdnFU>
Subject: Re: [sfc] TR: New Version Notification for draft-rebo-sfc-nsh-integrity-01.txt
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: Mon, 04 Nov 2019 16:04:02 -0000

Thank you for your work on this Med and Tiru.
Working Group, this is a topic we have in the charter, and explicitly 
told the IESG we would work on.  Please review and comment on the 
approach described here.

Thank you,
Joel (as co-chair)

On 11/4/2019 10:56 AM, mohamed.boucadair@orange.com wrote:
> Hi all,
> 
> This new version integrates the comments we received offline. The main changes are:
> 
> * Clarify why we don't encrypt the base and service path headers
> * Clarify that all metadata is integrity protected
> * Clarify that the Base header may (or not) be covered by integrity protection. Both schemes are discussed with trade-offs called out.
> * Updated the solution overview to provide a big picture view.
> 
> A detailed diff can be found at: https://www.ietf.org/rfcdiff?url2=draft-rebo-sfc-nsh-integrity-01
> 
> Please review and share your comments.
> 
> Cheers,
> Tiru & Med
> 
>> -----Message d'origine-----
>> De : internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
>> Envoyé : lundi 4 novembre 2019 16:46
>> À : Reddy K; Tirumaleswar Reddy; BOUCADAIR Mohamed TGI/OLN
>> Objet : New Version Notification for draft-rebo-sfc-nsh-integrity-01.txt
>>
>>
>> A new version of I-D, draft-rebo-sfc-nsh-integrity-01.txt
>> has been successfully submitted by Mohamed Boucadair and posted to the
>> IETF repository.
>>
>> Name:		draft-rebo-sfc-nsh-integrity
>> Revision:	01
>> Title:		Integrity Protection for Network Service Header (NSH) and
>> Encryption of Sensitive Metadata
>> Document date:	2019-11-04
>> Group:		Individual Submission
>> Pages:		21
>> URL:            https://www.ietf.org/internet-drafts/draft-rebo-sfc-nsh-
>> integrity-01.txt
>> Status:         https://datatracker.ietf.org/doc/draft-rebo-sfc-nsh-
>> integrity/
>> Htmlized:       https://tools.ietf.org/html/draft-rebo-sfc-nsh-integrity-01
>> Htmlized:       https://datatracker.ietf.org/doc/html/draft-rebo-sfc-nsh-
>> integrity
>> Diff:           https://www.ietf.org/rfcdiff?url2=draft-rebo-sfc-nsh-
>> integrity-01
>>
>> Abstract:
>>     This specification adds integrity protection and optional encryption
>>     directly to Network Service Headers (NSH) used for Service Function
>>     Chaining (SFC).
>>
>>
>>
>>
>> Please note that it may take a couple of minutes from the time of
>> submission
>> until the htmlized version and diff are available at tools.ietf.org.
>>
>> The IETF Secretariat
> 
> _______________________________________________
> sfc mailing list
> sfc@ietf.org
> https://www.ietf.org/mailman/listinfo/sfc
>

v2.23.0 | Report a Bug | By Email