Re: [I2nsf] Tsvart last call review of draft-ietf-i2nsf-applicability-13

Benjamin Kaduk <kaduk@mit.edu> Mon, 22 July 2019 04:05 UTC

Return-Path: <kaduk@mit.edu>
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 4B4651200B3; Sun, 21 Jul 2019 21:05:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 TELaGmQsjibT; Sun, 21 Jul 2019 21:05:11 -0700 (PDT)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (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 81A20120086; Sun, 21 Jul 2019 21:05:11 -0700 (PDT)
Received: from kduck.mit.edu ([24.16.140.251]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id x6M452rn023062 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 22 Jul 2019 00:05:05 -0400
Date: Sun, 21 Jul 2019 23:05:02 -0500
From: Benjamin Kaduk <kaduk@mit.edu>
To: "Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com>
Cc: Tommy Pauly <tpauly@apple.com>, skku_iotlab_seminar@googlegroups.com, IETF Discussion <ietf@ietf.org>, "i2nsf@ietf.org" <i2nsf@ietf.org>, skku_secu-brain_all@googlegroups.com, draft-ietf-i2nsf-applicability.all@ietf.org, tsv-art@ietf.org
Message-ID: <20190722040501.GQ99187@kduck.mit.edu>
References: <156218558317.14631.14734667974826685969@ietfa.amsl.com> <CAPK2DeyHVq5UbzcE0BMDC94TPOmgGERGWjy+8PdCman+XfRZKw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAPK2DeyHVq5UbzcE0BMDC94TPOmgGERGWjy+8PdCman+XfRZKw@mail.gmail.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/QTPvt42zExWVCoiBX-31MS0kYSY>
Subject: Re: [I2nsf] Tsvart last call review of draft-ietf-i2nsf-applicability-13
X-BeenThere: i2nsf@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 22 Jul 2019 04:05:13 -0000

On Sun, Jul 21, 2019 at 01:18:29AM -0400, Mr. Jaehoon Paul Jeong wrote:
> Hi Tommy,
> I have reflected all your comments on version -14:
> https://tools.ietf.org/html/draft-ietf-i2nsf-applicability-14
> 
> I answer your comments one by one with an attached revision letter.
> 
> If you have comments on this revision, please let me know.

I see that in several places the new text refers to "obtained from the
certificate in TLS versions prior to 1.3 [RFC8446] or the Server Name
Indication (SNI) in a TCP-session packet in TLS", but as Tommy attempted to
note, when draft-ietf-tls-esni becomes available, even the SNI value will
be encrypted and not visible to the network.

-Ben