Re: [apps-discuss] APPSDIR review of draft-ietf-nea-pt-tls-04

Alexey Melnikov <alexey.melnikov@isode.com> Wed, 13 June 2012 12:58 UTC

Return-Path: <alexey.melnikov@isode.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EA02721F857A; Wed, 13 Jun 2012 05:58:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level:
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[AWL=-1.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id s67ev3iRP2Xl; Wed, 13 Jun 2012 05:58:27 -0700 (PDT)
Received: from rufus.isode.com (cl-125.lon-03.gb.sixxs.net [IPv6:2a00:14f0:e000:7c::2]) by ietfa.amsl.com (Postfix) with ESMTP id 0658F21F8554; Wed, 13 Jun 2012 05:58:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1339584399; d=isode.com; s=selector; i=@isode.com; bh=uWLgdw/EuKzNiCteJBgvfOWbbfJipLb2UCZKGzAMfNs=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=UFBO2g2pqLIL5iazrGOrjJdjXpHb5xhcMdct3QpCE5xKGAnlNyXEInlyxj/RgyCiO6EVsc iDfTF+e5ItswSGBa0A2UI4ckx1NuC1IW5E6EXfRdwPc+u5MX7f7lLOhm/SykLnCpPEKxk6 so3+IyLDM7OVNwU6JTucrTupESOLA3c=;
Received: from [172.16.1.29] (shiny.isode.com [62.3.217.250]) by rufus.isode.com (submission channel) via TCP with ESMTPSA id <T9hvjgAE413e@rufus.isode.com>; Wed, 13 Jun 2012 11:46:38 +0100
X-SMTP-Protocol-Errors: PIPELINING
Message-ID: <4FD86FB2.2050002@isode.com>
Date: Wed, 13 Jun 2012 11:47:14 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
To: apps-discuss@ietf.org, draft-ietf-nea-pt-tls.all@tools.ietf.org
Subject: Re: [apps-discuss] APPSDIR review of draft-ietf-nea-pt-tls-04
References: <4FCD0614.5050902@isode.com>
In-Reply-To: <4FCD0614.5050902@isode.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jun 2012 12:58:28 -0000

On 04/06/2012 20:01, Alexey Melnikov wrote:
> I have been selected as the Applications Area Directorate reviewer for 
> this draft (for background on APPSDIR, please see 
> http://trac.tools.ietf.org/area/app/trac/wiki/ApplicationsAreaDirectorate 
> ).
>
> Please resolve these comments along with any other Last Call comments 
> you may receive. Please wait for direction from your document shepherd 
> or AD before posting a new version of the draft.  The review is not 
> copied to the IESG as the Last Call has not been announced yet.
>
> Document: draft-ietf-nea-pt-tls-04
> Title: PT-TLS: A TCP-based Posture Transport (PT) Protocol
> Reviewer: Alexey Melnikov
> Review Date: June 4, 2012
>
> Summary: This document is almost ready for publication as a Proposed 
> Standard, although some [mostly] SASL related issues remain.
>
> This document specifies PT-TLS, a TCP-based Posture Transport (PT)
> protocol.  The PT-TLS protocol carries the Network Endpoint
> Assessment (NEA) message exchange under the protection of a Transport
> Layer Security (TLS) secured tunnel.
>
> (Note, I've reviewed -04, but I think all of this still applies to -05.)
Additional issues in -05:

1) I didn't find the updated text prohibiting TLS renegotiation to be 
any clearer in -05? Can you maybe try to explain what is allowed and 
what is not?

2) In the IANA Considerations:

The PEN 0 (IETF) PT-TLS Message Type values between 9 and 2^32-2
inclusive are allocated for future assignment by the IANA.  The value
2^32-1 is permanently reserved and is not to be allocated.

Whom does the last sentence apply to? This registry? Or the IANA PEN 
registry being documented by draft-liang-iana-pen?