[LAC-TF] Fwd: RFC 6434 on IPv6 Node Requirements (IPSec en IPv6)

Arturo Servin aservin at lacnic.net
Fri Dec 23 00:07:46 BRST 2011

	IPsec deja de ser mandatorio (sección 11, pag. 17):

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.


Begin forwarded message:

> From: rfc-editor at rfc-editor.org
> Subject: RFC 6434 on IPv6 Node Requirements
> Date: 21 December 2011 15:00:18 GMT-02:00
> To: ietf-announce at ietf.org, rfc-dist at rfc-editor.org
> Cc: ipv6 at ietf.org, rfc-editor at rfc-editor.org
> A new Request for Comments is now available in online RFC libraries.
>        RFC 6434
>        Title:      IPv6 Node Requirements 
>        Author:     E. Jankiewicz, J. Loughney,
>                    T. Narten
>        Status:     Informational
>        Stream:     IETF
>        Date:       December 2011
>        Mailbox:    edward.jankiewicz at sri.com, 
>                    john.loughney at nokia.com, 
>                    narten at us.ibm.com
>        Pages:      30
>        Characters: 64407
>        Obsoletes:  RFC4294
>        I-D Tag:    draft-ietf-6man-node-req-bis-11.txt
>        URL:        http://www.rfc-editor.org/rfc/rfc6434.txt
> This document defines requirements for IPv6 nodes.  It is expected
> that IPv6 will be deployed in a wide range of devices and situations.
> Specifying the requirements for IPv6 nodes allows IPv6 to function
> well and interoperate in a large number of situations and
> deployments.  This document is not an Internet Standards Track 
> specification; it is published for informational purposes.
> This document is a product of the IPv6 Maintenance Working Group of the IETF.
> INFORMATIONAL: This memo provides information for the Internet community.
> It does not specify an Internet standard of any kind. Distribution of
> this memo is unlimited.
> This announcement is sent to the IETF-Announce and rfc-dist lists.
> To subscribe or unsubscribe, see
>  http://www.ietf.org/mailman/listinfo/ietf-announce
>  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
> For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
> For downloading RFCs, see http://www.rfc-editor.org/rfc.html.
> Requests for special distribution should be addressed to either the
> author of the RFC in question, or to rfc-editor at rfc-editor.org.  Unless
> specifically noted otherwise on the RFC itself, all RFCs are for
> unlimited distribution.
> The RFC Editor Team
> Association Management Solutions, LLC
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6 at ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.lacnic.net/pipermail/lactf/attachments/20111223/54bbd0ae/attachment.html>

More information about the LACTF mailing list