Return-Path: 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 2E85321F8674 for ; Wed, 15 Feb 2012 06:53:12 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=-0.001, BAYES_00=-2.599, HTML_MESSAGE=0.001] 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 5pAVq7JDeUSW for ; Wed, 15 Feb 2012 06:53:11 -0800 (PST) Received: from sxinet05.dtcc.com (sxinet05.dtcc.com [207.45.45.43]) by ietfa.amsl.com (Postfix) with ESMTP id 362C421F8545 for ; Wed, 15 Feb 2012 06:53:11 -0800 (PST) From: "Chernin, Michael A." Thread-Topic: [scap_interest] Scope of standards potentially moving to IETF Thread-Index: AczrY9ZA/rI0ysEqR+uJzeU+eJNThgAM6xSAABYlfpA= Date: Wed, 15 Feb 2012 14:53:02 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [172.18.113.13] Content-Type: multipart/alternative; boundary="_000_E3EFB6C0D90F82478AF227AA85ECF38015ADCCE2SXEMBP01corpdtc_" MIME-Version: 1.0 To: "kent_landfield@mcafee.com" , "scap_interest@ietf.org" 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\)." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Feb 2012 14:53:12 -0000 --_000_E3EFB6C0D90F82478AF227AA85ECF38015ADCCE2SXEMBP01corpdtc_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable 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 stand= ards consumers (private sector customers) who will also be participating in= IETF voting. I am trying to balance rapid development of standards using t= he IETF and complete vendor control of all standards. Once I see more consu= mer 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 identifie= d 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 consensu= s 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: www.mcafee.com From: Michael Aharon Chernin > Date: Tue, 14 Feb 2012 16:04:43 -0600 To: "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
_____________________________________________________________
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. _______________________________________________ scap_interest mailing list scap_interest@ietf.org https://www.ietf.org/mailman/listinfo/scap_interest --_000_E3EFB6C0D90F82478AF227AA85ECF38015ADCCE2SXEMBP01corpdtc_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Kent, understood. Like th= e 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 b= e 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 b= e more supportive of a large number of standards moving IETF.

 <= /p>

I know I am early and jum= ping 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.

 <= /p>

Aharon<= /p>

 <= /p>

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

 <= /p>

From: Kent_Lan= dfield@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 t= o IETF

 

From my perspective TBD.=

 =

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

 =

The idea here from my pe= rspective is to figure that out.  

 =

Kent Landfield
Director Content Strategy, Architecture an= d Standards

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

Direct: +1.972.963.7096  Mobile: +1.817.637.8026
Web: www.mcafee.com

 =

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

 =

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

 =

Aharon=

 =

DTCC Non-Confidential (W= hite)

------------------------= ---------------------------

Michael "Aharon&quo= t; Chernin

Security Automation Prog= ram Manager

Corporate Information Se= curity -Depository Trust & Clearing Corporation

O: 813-470-2173

 =

<BR>______________= _______________________________________________

<FONT size=3D2><= ;BR>

DTCC DISCLAIMER: This em= ail and any files transmitted with it are

confidential and intende= d 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 sy= stem. 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&= gt;

________________________= _______________________

scap_interest mailing li= st

 =

--_000_E3EFB6C0D90F82478AF227AA85ECF38015ADCCE2SXEMBP01corpdtc_--