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

[Adam Montville <[e-mail]>]

Hi David,

I think the answer to all three of your questions is really that it's all up to the working group.  The WG has an interest in ensuring interoperability, and standards are created based on running code.  USG may continue to require validation outside the context of the WG.  Finally, as the IETF is an open organization, participation from any organization, including USG, would be welcomed.

Adam

From: <[e-mail]<mailto:[e-mail]>>
Date: Wed, 15 Feb 2012 10:42:34 -0600
To: <[e-mail]<mailto:[e-mail]>>, kent_landfield <[e-mail]<mailto:[e-mail]>>, <[e-mail]<mailto:[e-mail]>>
Subject: Re: [scap_interest] Scope of standards potentially moving to IETF

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.<[e-mail]<mailto:[e-mail]>> 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: [e-mail]<mailto:[e-mail]> [mailto:[e-mail]]
Sent: Tuesday, February 14, 2012 6:09 PM
To: Chernin, Michael A.; [e-mail]<mailto:[e-mail]>
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: [phone]
Web: www.mcafee.com<http://www.mcafee.com/>

From: Michael Aharon Chernin <[e-mail]<mailto:[e-mail]>>
Date: Tue, 14 Feb 2012 16:04:43 -0600
To: "[e-mail]<mailto:[e-mail]>" <[e-mail]<mailto:[e-mail]>>
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
[e-mail]<mailto:[e-mail]>
https://www.ietf.org/mailman/listinfo/scap_interest


________________________________

_______________________________________________
scap_interest mailing list
[e-mail]<mailto:[e-mail]>
https://www.ietf.org/mailman/listinfo/scap_interest
_______________________________________________ scap_interest mailing list [e-mail]<mailto:[e-mail]> https://www.ietf.org/mailman/listinfo/scap_interest