[Nea] [Errata Verified] RFC5792 (3936)
RFC Errata System <rfc-editor@rfc-editor.org> Thu, 08 May 2014 16:40 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 1D2351A0074; Thu, 8 May 2014 09:40:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.853
X-Spam-Level:
X-Spam-Status: No, score=-104.853 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 Ip9ngAVOnwfb; Thu, 8 May 2014 09:40:34 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id A20A81A0087; Thu, 8 May 2014 09:40:29 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 5E7711801A4; Thu, 8 May 2014 09:39:47 -0700 (PDT)
To: steve@hannas.com, Paul_Sangster@symantec.com, kaushik@cisco.com
X-PHP-Originating-Script: 1005:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20140508163947.5E7711801A4@rfc-editor.org>
Date: Thu, 08 May 2014 09:39:47 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/nea/mQZT6CwuM86EcLVjNwciD-EhTmo
Cc: rfc-editor@rfc-editor.org, nea@ietf.org, iesg@ietf.org
Subject: [Nea] [Errata Verified] RFC5792 (3936)
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, 08 May 2014 16:40:35 -0000
The following errata report has been verified 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=3936 -------------------------------------- Status: Verified Type: Technical Reported by: Steve Hanna <steve@hannas.com> Date Reported: 2014-03-27 Verified by: Stephen Farrell (IESG) Section: 3.4 Original Text ------------- As depicted in section 3.2, a PA-TNC message consists of a PA-TNC header followed by a sequence of one or more attributes. Corrected Text -------------- As depicted in section 3.2, a PA-TNC message consists of a PA-TNC header followed by a sequence of zero or more attributes. 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.4, 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. -------------------------------------- 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
- [Nea] [Technical Errata Reported] RFC5792 (3936) RFC Errata System
- [Nea] [Errata Verified] RFC5792 (3936) RFC Errata System