[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Fwd: RFC 4218 on Threats Relating to IPv6 Multihoming Solutions



Begin forwarded message:


From: rfc-editor@rfc-editor.org
Date: tisdag 1 nov 2005 01.50.28 GMT+01:00
To: ietf-announce@ietf.org
Cc: multi6@ops.ietf.org, rfc-editor@rfc-editor.org
Subject: RFC 4218 on Threats Relating to IPv6 Multihoming Solutions



A new Request for Comments is now available in online RFC libraries.


        RFC 4218

        Title:      Threats Relating to IPv6 Multihoming Solutions
        Author(s):  E. Nordmark, T. Li
        Status:     Informational
        Date:       October 2005
        Mailbox:    erik.nordmark@sun.com, Tony.Li@tony.li
        Pages:      31
        Characters: 75969
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-multi6-multihoming-threats-03.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc4218.txt


This document lists security threats related to IPv6 multihoming.
Multihoming can introduce new opportunities to redirect packets to
different, unintended IP addresses.

The intent is to look at how IPv6 multihoming solutions might make
the Internet less secure; we examine threats that are inherent to
all IPv6 multihoming solutions rather than study any specific
proposed solution.  The threats in this document build
upon the threats discovered and discussed as part of the Mobile IPv6
work.

This document is a product of the Site Multihoming in IPv6 Working
Group of the IETF.

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 list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body
help: ways_to_get_rfcs.  For example:

        To: rfc-info@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@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@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader
implementation to automatically retrieve the ASCII version
of the RFCs.
Content-Type: text/plain
Content-ID: <051031164920.RFC@RFC-EDITOR.ORG>

_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce