Re: [scap_interest] Scope of standards potentially moving to IETF

david.oliva@verizon.net Wed, 15 February 2012 16:43 UTC

Return-Path: <david.oliva@verizon.net>
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 1DB1421E8019 for <scap_interest@ietfa.amsl.com>; Wed, 15 Feb 2012 08:43:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.044
X-Spam-Level:
X-Spam-Status: No, score=-1.044 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, HTML_MIME_NO_HTML_TAG=0.097, MIME_HTML_ONLY=1.457]
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 fD7oUbXwnhgo for <scap_interest@ietfa.amsl.com>; Wed, 15 Feb 2012 08:43:01 -0800 (PST)
Received: from vms173011pub.verizon.net (vms173011pub.verizon.net [206.46.173.11]) by ietfa.amsl.com (Postfix) with ESMTP id 89DE821F8557 for <scap_interest@ietf.org>; Wed, 15 Feb 2012 08:43:01 -0800 (PST)
Received: from vznit170060 ([unknown] [172.18.12.132]) by vms173011.mailsrvcs.net (Sun Java(tm) System Messaging Server 7u2-7.02 32bit (built Apr 16 2009)) with ESMTPA id <0LZG00KVZ12Y44B1@vms173011.mailsrvcs.net> for scap_interest@ietf.org; Wed, 15 Feb 2012 10:42:35 -0600 (CST)
Received: from 96.255.129.191 ([96.255.129.191]) by vznit170060 (Verizon Webmail) with HTTP; Wed, 15 Feb 2012 10:42:34 -0600 (CST)
Date: Wed, 15 Feb 2012 10:42:34 -0600 (CST)
From: david.oliva@verizon.net
To: mchernin@dtcc.com, kent_landfield@mcafee.com, scap_interest@ietf.org
Message-id: <764077.456681.1329324154353.JavaMail.root@vznit170060>
MIME-version: 1.0
Content-type: text/html; charset=UTF-8
Content-transfer-encoding: quoted-printable
X-Mailer: Verizon Webmail
X-Originating-IP: [96.255.129.191]
Subject: Re: [scap_interest] Scope of standards potentially moving to IETF
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: Wed, 15 Feb 2012 16:43:08 -0000

Hello all:
 
I also believe that SCAP can be used worlwide and should be marketted accordingly.
Maybe allowing IETF to endorse them is a good idea.
 
I just have a few questions.
 
1.  Would IETF also take a role in validating products?
2.  What mechanisms does IETF provide that encourage the cooperation needed for incorporation future specifications?
3.  How would IETF take into account the input of U.S. Federal agencies in future specifications?
 
David Oliva
 
On 02/15/12, Chernin, Michael A.<mchernin@dtcc.com> wrote:
 

Kent, understood. Like the vendors, I do agree that certain standards need to go to IETF. But, today the only people that would be voting during IETF calls would be the federal government and security tool vendors. I am going to be hesitant in supporting a move of all standards until there are standards consumers (private sector customers) who will also be participating in IETF voting. I am trying to balance rapid development of standards using the IETF and complete vendor control of all standards. Once I see more consumer activity during voting, I will be more supportive of a large number of standards moving IETF.

 

I know I am early and jumping the gun on this, but I just wanted to get my story out there. At this time no standards have been specifically identified and no specific action is required at this time.

 

Aharon

 

DTCC Non-Confidential (White)
---------------------------------------------------
Michael "Aharon" Chernin
Security Automation Program Manager
Corporate Information Security -Depository Trust & Clearing Corporation
O: 813-470-2173

 

From: Kent_Landfield@McAfee.com [mailto:Kent_Landfield@McAfee.com]
Sent: Tuesday, February 14, 2012 6:09 PM
To: Chernin, Michael A.; scap_interest@ietf.org
Subject: Re: [scap_interest] Scope of standards potentially moving to IETF

 

From my perspective TBD.

 

There are some that are unencumbered from and IPR perspective and those are potential candidates. Others will have to move as the appropriate consensus  is achieved and IPR issues are addressed.

 

The idea here from my perspective is to figure that out.  

 

Kent Landfield
Director Content Strategy, Architecture and Standards

McAfee | An Intel Company
5000 Headquarters Dr.
Plano, Texas 75024

Direct: +1.972.963.7096 
Mobile: +1.817.637.8026
Web: http://www.mcafee.com/" target="_blank" rel="nofollow">www.mcafee.com

 

From: Michael Aharon Chernin <mchernin@dtcc.com>
Date: Tue, 14 Feb 2012 16:04:43 -0600
To: "scap_interest@ietf.org" <scap_interest@ietf.org>
Subject: [scap_interest] Scope of standards potentially moving to IETF

 

I am just going to jump right on out there and ask. Which standards are we looking to go to IETF? Specific SCAP standards or the entire SCAP umbrella?

 

Aharon

 

DTCC Non-Confidential (White)

---------------------------------------------------

Michael "Aharon" Chernin

Security Automation Program Manager

Corporate Information Security -Depository Trust & Clearing Corporation

O: 813-470-2173

 

<BR>_____________________________________________________________

<FONT size=2><BR>

DTCC DISCLAIMER: This email and any files transmitted with it are

confidential and intended solely for the use of the individual or

entity to whom they are addressed. If you have received this email

in error, please notify us immediately and delete the email and any

attachments from your system. The recipient should check this email

and any attachments for the presence of viruses.  The company

accepts no liability for any damage caused by any virus transmitted

by this email.</FONT>

_______________________________________________

scap_interest mailing list

 




_______________________________________________
scap_interest mailing list
scap_interest@ietf.org
https://www.ietf.org/mailman/listinfo/scap_interest" target="_blank" rel="nofollow">https://www.ietf.org/mailman/listinfo/scap_interest