<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><br></div><span class="Apple-tab-span" style="white-space:pre"> </span>IPsec deja de ser mandatorio (sección 11, pag. 17):<div><br></div><div>"</div><div><pre style="color: rgb(0, 0, 0); font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; word-wrap: break-word; white-space: pre-wrap; ">Previously, IPv6 mandated implementation of IPsec and recommended the
key management approach of IKE. This document updates that
recommendation by making support of the IPsec Architecture [RFC4301]
a SHOULD for all IPv6 nodes. Note that the IPsec Architecture
requires (e.g., Section 4.5 of RFC 4301) the implementation of both
manual and automatic key management. Currently, the default
automated key management protocol to implement is IKEv2 [RFC5996].
This document recognizes that there exists a range of device types
and environments where approaches to security other than IPsec can be
justified. For example, special-purpose devices may support only a
very limited number or type of applications, and an application-
specific security approach may be sufficient for limited management
or configuration capabilities. Alternatively, some devices may run
on extremely constrained hardware (e.g., sensors) where the full
IPsec Architecture is not justified.</pre><div>"</div></div><div><br></div><div>Saludos,</div><div>-as</div><div><div><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.0);"><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.0);"><b>Subject: </b></span><span style="font-family:'Helvetica'; font-size:medium;"><b>RFC 6434 on IPv6 Node Requirements</b><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.0);"><b>Date: </b></span><span style="font-family:'Helvetica'; font-size:medium;">21 December 2011 15:00:18 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.0);"><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.0);"><b>Cc: </b></span><span style="font-family:'Helvetica'; font-size:medium;"><a href="mailto:ipv6@ietf.org">ipv6@ietf.org</a>, <a href="mailto:rfc-editor@rfc-editor.org">rfc-editor@rfc-editor.org</a><br></span></div><br><div><br>A new Request for Comments is now available in online RFC libraries.<br><br><br> RFC 6434<br><br> Title: IPv6 Node Requirements <br> Author: E. Jankiewicz, J. Loughney,<br> T. Narten<br> Status: Informational<br> Stream: IETF<br> Date: December 2011<br> Mailbox: <a href="mailto:edward.jankiewicz@sri.com">edward.jankiewicz@sri.com</a>, <br> <a href="mailto:john.loughney@nokia.com">john.loughney@nokia.com</a>, <br> <a href="mailto:narten@us.ibm.com">narten@us.ibm.com</a><br> Pages: 30<br> Characters: 64407<br> Obsoletes: RFC4294<br><br> I-D Tag: draft-ietf-6man-node-req-bis-11.txt<br><br> URL: <a href="http://www.rfc-editor.org/rfc/rfc6434.txt">http://www.rfc-editor.org/rfc/rfc6434.txt</a><br><br>This document defines requirements for IPv6 nodes. It is expected<br>that IPv6 will be deployed in a wide range of devices and situations.<br>Specifying the requirements for IPv6 nodes allows IPv6 to function<br>well and interoperate in a large number of situations and<br>deployments. This document is not an Internet Standards Track <br>specification; it is published for informational purposes.<br><br>This document is a product of the IPv6 Maintenance Working Group of the IETF.<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 IPv6 working group mailing list<br><a href="mailto:ipv6@ietf.org">ipv6@ietf.org</a><br>Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6<br>--------------------------------------------------------------------<br></div></blockquote></div><br></div></div></body></html>