<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>El RFC puede ser de interés para esta lista.</div><div><br></div><div>Saludos,</div><div>-as</div><br><div><br><div>Begin forwarded message:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;"><span style="font-family:'Helvetica'; font-size:medium; color:rgba(0, 0, 0, 1);"><b>From: </b></span><span style="font-family:'Helvetica'; font-size:medium;"><a href="mailto:rfc-editor@rfc-editor.org">rfc-editor@rfc-editor.org</a><br></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;"><span style="font-family:'Helvetica'; font-size:medium; color:rgba(0, 0, 0, 1);"><b>Date: </b></span><span style="font-family:'Helvetica'; font-size:medium;">8 November 2010 03:49:20 GMT-02:00<br></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;"><span style="font-family:'Helvetica'; font-size:medium; color:rgba(0, 0, 0, 1);"><b>To: </b></span><span style="font-family:'Helvetica'; font-size:medium;"><a href="mailto:ietf-announce@ietf.org">ietf-announce@ietf.org</a>, <a href="mailto:rfc-dist@rfc-editor.org">rfc-dist@rfc-editor.org</a><br></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;"><span style="font-family:'Helvetica'; font-size:medium; color:rgba(0, 0, 0, 1);"><b>Cc: </b></span><span style="font-family:'Helvetica'; font-size:medium;"><a href="mailto:rfc-editor@rfc-editor.org">rfc-editor@rfc-editor.org</a><br></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;"><span style="font-family:'Helvetica'; font-size:medium; color:rgba(0, 0, 0, 1);"><b>Subject: </b></span><span style="font-family:'Helvetica'; font-size:medium;"><b>RFC 6045 on Real-time Inter-network Defense (RID)</b><br></span></div><br><div><br>A new Request for Comments is now available in online RFC libraries.<br><br><br> RFC 6045<br><br> Title: Real-time Inter-network Defense (RID) <br> Author: K. Moriarty<br> Status: Informational<br> Stream: IETF<br> Date: November 2010<br> Mailbox: <a href="mailto:Moriarty_Kathleen@EMC.com">Moriarty_Kathleen@EMC.com</a><br> Pages: 75<br> Characters: 172817<br> Updates/Obsoletes/SeeAlso: None<br><br> I-D Tag: draft-moriarty-post-inch-rid-12.txt<br><br> URL: <a href="http://www.rfc-editor.org/rfc/rfc6045.txt">http://www.rfc-editor.org/rfc/rfc6045.txt</a><br><br>Network security incidents, such as system compromises, worms,<br>viruses, phishing incidents, and denial of service, typically<br>result in the loss of service, data, and resources both human and<br>system. Network providers and Computer Security Incident Response<br>Teams need to be equipped and ready to assist in communicating and<br>tracing security incidents with tools and procedures in place<br>before the occurrence of an attack. Real-time Inter-network<br>Defense (RID) outlines a proactive inter-network communication method to<br>facilitate sharing incident handling data while integrating<br>existing detection, tracing, source identification, and mitigation<br>mechanisms for a complete incident handling solution. Combining<br>these capabilities in a communication system provides a way to<br>achieve higher security levels on networks. Policy guidelines for<br>handling incidents are recommended and can be agreed upon by a<br>consortium using the security recommendations and considerations.<br><br>RID has found use within the international research communities,<br>but has not been widely adopted in other sectors. This publication<br>provides the specification to those communities that have adopted<br>it, and communities currently considering solutions for real-time<br>inter-network defense. The specification may also accelerate<br>development of solutions where different transports or message<br>formats are required by leveraging the data elements and structures<br>specified here. This document is not an Internet Standards Track <br>specification; it is published for informational purposes.<br><br><br>INFORMATIONAL: This memo provides information for the Internet community.<br>It does not specify an Internet standard of any kind. Distribution of<br>this memo is unlimited.<br><br>This announcement is sent to the IETF-Announce and rfc-dist lists.<br>To subscribe or unsubscribe, see<br> <a href="http://www.ietf.org/mailman/listinfo/ietf-announce">http://www.ietf.org/mailman/listinfo/ietf-announce</a><br> <a href="http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist">http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist</a><br><br>For searching the RFC series, see <a href="http://www.rfc-editor.org/rfcsearch.html">http://www.rfc-editor.org/rfcsearch.html</a>.<br>For downloading RFCs, see <a href="http://www.rfc-editor.org/rfc.html">http://www.rfc-editor.org/rfc.html</a>.<br><br>Requests for special distribution should be addressed to either the<br>author of the RFC in question, or to <a href="mailto:rfc-editor@rfc-editor.org">rfc-editor@rfc-editor.org</a>. Unless<br>specifically noted otherwise on the RFC itself, all RFCs are for<br>unlimited distribution.<br><br><br>The RFC Editor Team<br>Association Management Solutions, LLC<br><br><br>_______________________________________________<br>IETF-Announce mailing list<br><a href="mailto:IETF-Announce@ietf.org">IETF-Announce@ietf.org</a><br><a href="https://www.ietf.org/mailman/listinfo/ietf-announce">https://www.ietf.org/mailman/listinfo/ietf-announce</a><br></div></blockquote></div><br></body></html>