Re: [scap_interest] scap_interest Digest, Vol 5, Issue 19

Adam Montville <amontville@tripwire.com> Fri, 17 February 2012 16:00 UTC

Return-Path: <amontville@tripwire.com>
X-Original-To: scap_interest@ietfa.amsl.com
Delivered-To: scap_interest@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CE8CE21F885C for <scap_interest@ietfa.amsl.com>; Fri, 17 Feb 2012 08:00:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.212
X-Spam-Level:
X-Spam-Status: No, score=-4.212 tagged_above=-999 required=5 tests=[AWL=-0.613, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 J+12EvXF7qtM for <scap_interest@ietfa.amsl.com>; Fri, 17 Feb 2012 08:00:11 -0800 (PST)
Received: from VA3EHSOBE009.bigfish.com (va3ehsobe001.messaging.microsoft.com [216.32.180.11]) by ietfa.amsl.com (Postfix) with ESMTP id 42A7421F8860 for <scap_interest@ietf.org>; Fri, 17 Feb 2012 08:00:11 -0800 (PST)
Received: from mail89-va3-R.bigfish.com (10.7.14.244) by VA3EHSOBE009.bigfish.com (10.7.40.29) with Microsoft SMTP Server id 14.1.225.23; Fri, 17 Feb 2012 16:00:10 +0000
Received: from mail89-va3 (localhost [127.0.0.1]) by mail89-va3-R.bigfish.com (Postfix) with ESMTP id 4D0364C0442; Fri, 17 Feb 2012 16:00:10 +0000 (UTC)
X-SpamScore: -81
X-BigFish: VPS-81(z73eW41dR21cRzbb2dI9371I9d9R542M1432N98dKzz1202hzz1033IL8275bh8275dhz2dh2a8h668h839h944h)
X-Forefront-Antispam-Report: CIP:174.47.84.216; KIP:(null); UIP:(null); IPV:NLI; H:PDXHB01.tripwire.com; RD:174-47-84-216.static.twtelecom.net; EFVD:NLI
Received: from mail89-va3 (localhost.localdomain [127.0.0.1]) by mail89-va3 (MessageSwitch) id 1329494408413481_11869; Fri, 17 Feb 2012 16:00:08 +0000 (UTC)
Received: from VA3EHSMHS028.bigfish.com (unknown [10.7.14.238]) by mail89-va3.bigfish.com (Postfix) with ESMTP id 55022140047; Fri, 17 Feb 2012 16:00:08 +0000 (UTC)
Received: from PDXHB01.tripwire.com (174.47.84.216) by VA3EHSMHS028.bigfish.com (10.7.99.38) with Microsoft SMTP Server (TLS) id 14.1.225.23; Fri, 17 Feb 2012 16:00:04 +0000
Received: from PDXHB01.tripwire.com (172.30.0.53) by PDXED01.tripwire.com (192.168.192.5) with Microsoft SMTP Server (TLS) id 14.1.355.2; Fri, 17 Feb 2012 08:08:46 -0800
Received: from PDXMB02.tripwire.com ([fe80::f997:7b65:8e64:438e]) by PDXHB01.tripwire.com ([fe80::d495:98d2:7df4:2154%11]) with mapi id 14.01.0355.002; Fri, 17 Feb 2012 08:00:02 -0800
From: Adam Montville <amontville@tripwire.com>
To: "kathleen.moriarty@emc.com" <kathleen.moriarty@emc.com>, "Oliva_Ruben@bah.com" <Oliva_Ruben@bah.com>, "scap_interest@ietf.org" <scap_interest@ietf.org>
Thread-Topic: [scap_interest] scap_interest Digest, Vol 5, Issue 19
Thread-Index: AQHM7NTHhKFALzSMaEqu/OwLf8yIt5ZBJcRwgAAN3oCAAA0bAA==
Date: Fri, 17 Feb 2012 16:00:01 +0000
Message-ID: <CB63B973.9615%amontville@tripwire.com>
In-Reply-To: <AE31510960917D478171C79369B660FA0E308BD133@MX06A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.14.0.111121
x-originating-ip: [172.30.0.234]
x-exclaimer-md-config: 79afcaa7-fdf4-4fa6-abe0-afeaa4640a4f
Content-Type: text/plain; charset="us-ascii"
Content-ID: <6A061F536CEFC1418A815E0A9FA7006E@tripwire.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: tripwire.com
Subject: Re: [scap_interest] scap_interest Digest, Vol 5, Issue 19
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: Fri, 17 Feb 2012 16:00:13 -0000

+1

On 2/17/12 7:28 AM, "kathleen.moriarty@emc.com";
<kathleen.moriarty@emc.com>; wrote:

>Hello, Rubin, Kent, all,
>
>I think interoperability testing is an important aspect of the
>standardization process.  It helps us prove out the specifications are
>well written (or that they require changes) which enables new vendors or
>implementers to code against the same specification and expect an
>interoperable implementation.
>
>This is important at each stage, from supporting data formats to the
>ability to uniformly exchanging those formats with interpretable controls
>and expected messaging patterns/flows.  The specifications for the data
>formats should go beyond schemas to cover error handling and other
>requirements for developers to enable interoperable solution development.
> When you move to transport and APIs for exchanges, this becomes more
>critical if we want to evolve the ability to support the ecosystem of
>data format specifications.  Products and use of these specifications can
>diverge by adding value in areas like data analysis and how exchanged
>data sets may be leveraged.
>
>Thank you,
>Kathleen  
>
>-----Original Message-----
>From: scap_interest-bounces@ietf.org
>[mailto:scap_interest-bounces@ietf.org] On Behalf Of Oliva, Ruben [USA]
>Sent: Friday, February 17, 2012 9:26 AM
>To: scap_interest@ietf.org
>Subject: Re: [scap_interest] scap_interest Digest, Vol 5, Issue 19
>
>To all:
>
>Kent brings up a good point.
>
>Validation does not equate to interoperability.
>
>How does the community feel about an SCAP interoperability testing
>function?
>
>David Oliva
>
>-----Original Message-----
>From: scap_interest-bounces@ietf.org
>[mailto:scap_interest-bounces@ietf.org] On Behalf Of
>scap_interest-request@ietf.org
>Sent: Thursday, February 16, 2012 1:00 PM
>To: scap_interest@ietf.org
>Subject: scap_interest Digest, Vol 5, Issue 19
>
>If you have received this digest without all the individual message
>attachments you will need to update your digest options in your list
>subscription.  To do so, go to
>
>https://www.ietf.org/mailman/listinfo/scap_interest
>
>Click the 'Unsubscribe or edit options' button, log in, and set "Get MIME
>or Plain Text Digests?" to MIME.  You can set this option globally for
>all the list digests you receive at this point.
>
>
>
>Send scap_interest mailing list submissions to
>	scap_interest@ietf.org
>
>To subscribe or unsubscribe via the World Wide Web, visit
>	https://www.ietf.org/mailman/listinfo/scap_interest
>or, via email, send a message with subject or body 'help' to
>	scap_interest-request@ietf.org
>
>You can reach the person managing the list at
>	scap_interest-owner@ietf.org
>
>When replying, please edit your Subject line so it is more specific than
>"Re: Contents of scap_interest digest..."
>_______________________________________________
>scap_interest mailing list
>scap_interest@ietf.org
>https://www.ietf.org/mailman/listinfo/scap_interest
>
>_______________________________________________
>scap_interest mailing list
>scap_interest@ietf.org
>https://www.ietf.org/mailman/listinfo/scap_interest
>