[Nea] [Technical Errata Reported] RFC5792 (3935)

RFC Errata System <rfc-editor@rfc-editor.org> Thu, 27 March 2014 14:18 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: nea@ietfa.amsl.com
Delivered-To: nea@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4B2AD1A06F6 for <nea@ietfa.amsl.com>; Thu, 27 Mar 2014 07:18:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.912
X-Spam-Level:
X-Spam-Status: No, score=-1.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 GN_T6MbABtXH for <nea@ietfa.amsl.com>; Thu, 27 Mar 2014 07:18:50 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2607:f170:8000:1500::d3]) by ietfa.amsl.com (Postfix) with ESMTP id 82A911A027F for <nea@ietf.org>; Thu, 27 Mar 2014 07:18:50 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id E42C97FC396; Thu, 27 Mar 2014 07:18:47 -0700 (PDT)
To: Paul_Sangster@symantec.com, kaushik@cisco.com, stephen.farrell@cs.tcd.ie, Kathleen.Moriarty.ietf@gmail.com, shanna@juniper.net, sethomso@cisco.com
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20140327141847.E42C97FC396@rfc-editor.org>
Date: Thu, 27 Mar 2014 07:18:47 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/nea/eaP24EOZr9YXMT9ltFv8jo4WzNY
Cc: steve@hannas.com, nea@ietf.org, rfc-editor@rfc-editor.org
Subject: [Nea] [Technical Errata Reported] RFC5792 (3935)
X-BeenThere: nea@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Network Endpoint Assessment discussion list <nea.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/nea>, <mailto:nea-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/nea/>
List-Post: <mailto:nea@ietf.org>
List-Help: <mailto:nea-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/nea>, <mailto:nea-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Mar 2014 14:18:56 -0000

The following errata report has been submitted for RFC5792,
"PA-TNC: A Posture Attribute (PA) Protocol Compatible with Trusted Network Connect (TNC)".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=5792&eid=3935

--------------------------------------
Type: Technical
Reported by: Steve Hanna <steve@hannas.com>

Section: 3.1

Original Text
-------------
Each PA-TNC message may
contain one or more attributes associated with the functional
component identified in the component type (PA Subtype) of the
Posture Broker (PB) protocol.

Corrected Text
--------------
Each PA-TNC message may
contain zero or more attributes associated with the functional
component identified in the component type (PA Subtype) of the
Posture Broker (PB) protocol.

Notes
-----
Section 4 of RFC 5792 says “A PA-TNC message MUST contain a PA-TNC header (defined in section 3.6. followed by a sequence of zero or more PA-TNC attributes.” This contradicts the text in section 3.1, which says “one or more”. The correct text is “zero or more”. There’s no reason why a PA-TNC message containing zero attributes should be prohibited. For PA-TNC messages with some PA subtypes, an empty message containing no attributes may be enough.

Instructions:
-------------
This errata is currently posted as "Reported". If necessary, please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party (IESG)
can log in to change the status and edit the report, if necessary. 

--------------------------------------
RFC5792 (draft-ietf-nea-pa-tnc-06)
--------------------------------------
Title               : PA-TNC: A Posture Attribute (PA) Protocol Compatible with Trusted Network Connect (TNC)
Publication Date    : March 2010
Author(s)           : P. Sangster, K. Narayan
Category            : PROPOSED STANDARD
Source              : Network Endpoint Assessment
Area                : Security
Stream              : IETF
Verifying Party     : IESG