[scap_interest] XCCDF going forward

"Schmidt, Charles M." <cmschmidt@mitre.org> Mon, 20 February 2012 16:05 UTC

Return-Path: <cmschmidt@mitre.org>
X-Original-To: scap_interest@ietfa.amsl.com
Delivered-To: scap_interest@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id EB48821F8716 for <scap_interest@ietfa.amsl.com>; Mon, 20 Feb 2012 08:05:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id HQckZPKU+kUG for <scap_interest@ietfa.amsl.com>; Mon, 20 Feb 2012 08:05:01 -0800 (PST)
Received: from smtpksrv1.mitre.org (smtpksrv1.mitre.org []) by ietfa.amsl.com (Postfix) with ESMTP id 4D67921F8522 for <scap_interest@ietf.org>; Mon, 20 Feb 2012 08:05:01 -0800 (PST)
Received: from smtpksrv1.mitre.org (localhost.localdomain []) by localhost (Postfix) with SMTP id A40E021B08ED for <scap_interest@ietf.org>; Mon, 20 Feb 2012 11:04:55 -0500 (EST)
Received: from IMCCAS04.MITRE.ORG (imccas04.mitre.org []) by smtpksrv1.mitre.org (Postfix) with ESMTP id 8C98E21B07EA for <scap_interest@ietf.org>; Mon, 20 Feb 2012 11:04:55 -0500 (EST)
Received: from IMCMBX04.MITRE.ORG ([]) by IMCCAS04.MITRE.ORG ([]) with mapi id 14.01.0339.001; Mon, 20 Feb 2012 11:04:55 -0500
From: "Schmidt, Charles M." <cmschmidt@mitre.org>
To: "scap_interest@ietf.org" <scap_interest@ietf.org>
Thread-Topic: XCCDF going forward
Thread-Index: Aczv5SDaxDnDzzmYQaGHYeSUB92ykg==
Date: Mon, 20 Feb 2012 16:04:54 +0000
Message-ID: <80B432C0A0D105468E74A98942733F77181DDA72@IMCMBX04.MITRE.ORG>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
x-originating-ip: []
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=SHA1; boundary="----=_NextPart_000_0068_01CCEFB7.11E7CF80"
MIME-Version: 1.0
Subject: [scap_interest] XCCDF going forward
X-BeenThere: scap_interest@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Discussion List for IETFers interested in the Security Content Automation Protocol \(SCAP\)." <scap_interest.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/scap_interest>, <mailto:scap_interest-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/scap_interest>
List-Post: <mailto:scap_interest@ietf.org>
List-Help: <mailto:scap_interest-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/scap_interest>, <mailto:scap_interest-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Feb 2012 16:05:06 -0000

Hello all,

Adam's original announcement specifically mentioned XCCDF 1.2.1 as something
to discuss at the upcoming side meeting. I wanted to add a few comments
along those lines.

First, NIST has a publicly accessible issue tracker where I have collected
the suggestions people have provided as to changes to the XCCDF language.
The list of open (and one re-opened) issues can be accessed here:
(Please note this is just a public repository of raised issues. The site
does not support public discussion - we have been using the XCCDF mailing
list for that.) The issues covered in this repository range from minor
tweaks and fixes (XCCDF-93 "Make the Benchmark status property optional" and
XCCDF-83 "Reconcile 'hidden' and 'selected' properties") to items that would
significantly change the structure of the language (XCCDF-62 "Merge Value
functionality into Rules", and XCCDF-76 "XCCDF as a high-level result
aggregator"). I imagine that most of these items would be too far in the
weeds for an initial side-meeting, but I thought it might be useful to note
what sort of things the XCCDF community has been considering.