Fwd: RFC 5095 on Deprecation of Type 0 Routing Headers in IPv6

[Joe Abley]

Begin forwarded message:

> From: rfc-editor at rfc-editor.org
> Date: 12 December 2007 18:06:01 GMT-05:00
> To: ietf-announce at ietf.org, rfc-dist at rfc-editor.org
> Cc: ipv6 at ietf.org, rfc-editor at rfc-editor.org
> Subject: RFC 5095 on Deprecation of Type 0 Routing Headers in IPv6
>
>
> A new Request for Comments is now available in online RFC libraries.
>
>
>        RFC 5095
>
>        Title:      Deprecation of Type 0 Routing
>                    Headers in IPv6
>        Author:     J. Abley, P. Savola,
>                    G. Neville-Neil
>        Status:     Standards Track
>        Date:       December 2007
>        Mailbox:    jabley at ca.afilias.info,
>                    psavola at funet.fi,
>                    gnn at neville-neil.com
>        Pages:      7
>        Characters: 13423
>        Updates:    RFC2460, RFC4294
>        See-Also:
>
>        I-D Tag:    draft-ietf-ipv6-deprecate-rh0-01.txt
>
>        URL:        http://www.rfc-editor.org/rfc/rfc5095.txt
>
> The functionality provided by IPv6's Type 0 Routing Header can be
> exploited in order to achieve traffic amplification over a remote
> path for the purposes of generating denial-of-service traffic.  This
> document updates the IPv6 specification to deprecate the use of IPv6
> Type 0 Routing Headers, in light of this security concern.
> [STANDARDS TRACK]
>
> This document is a product of the IP Version 6 Working Group
> Working Group of the IETF.
>
> This is now a Proposed Standard Protocol.
>
> STANDARDS TRACK: This document specifies an Internet standards track
> protocol for the Internet community,and requests discussion and  
> suggestions
> for improvements.Please refer to the current edition of the Internet
> Official Protocol Standards (STD 1) for the standardization state and
> status of this protocol.  Distribution of this memo is unlimited.
>
> This announcement is sent to the IETF list and the RFC-DIST list.
> Requests to be added to or deleted from the IETF distribution list
> should be sent to IETF-REQUEST at IETF.ORG.  Requests to be
> added to or deleted from the RFC-DIST distribution list should
> be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.
>
> Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
> an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body
>
> help: ways_to_get_rfcs. For example:
>
>        To: rfc-info at RFC-EDITOR.ORG
>        Subject: getting rfcs
>
>        help: ways_to_get_rfcs
>
> Requests for special distribution should be addressed to either the
> author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG.   
> Unless
> specifically noted otherwise on the RFC itself, all RFCs are for
> unlimited distribution.
>
> Submissions for Requests for Comments should be sent to
> RFC-EDITOR at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to  
> RFC
> Authors, for further information.
>
>
> The RFC Editor Team
> USC/Information Sciences Institute
>
> ...
>
>
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6 at ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>