[Mip6] RFC 5419 on Why the Authentication Data Suboption is Needed for Mobile IPv6 (MIPv6)

rfc-editor@rfc-editor.org Fri, 30 January 2009 00:21 UTC

Return-Path: <mip6-bounces@ietf.org>
X-Original-To: mip6-archive@megatron.ietf.org
Delivered-To: ietfarch-mip6-archive@core3.amsl.com
Received: from [] (localhost []) by core3.amsl.com (Postfix) with ESMTP id 412103A68DC; Thu, 29 Jan 2009 16:21:13 -0800 (PST)
X-Original-To: mip6@core3.amsl.com
Delivered-To: mip6@core3.amsl.com
Received: from localhost (localhost []) by core3.amsl.com (Postfix) with ESMTP id 28CC13A68DC; Thu, 29 Jan 2009 16:21:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.791
X-Spam-Status: No, score=-16.791 tagged_above=-999 required=5 tests=[AWL=0.808, BAYES_00=-2.599, USER_IN_DEF_WHITELIST=-15]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id h8ZNUnf8biRg; Thu, 29 Jan 2009 16:21:07 -0800 (PST)
Received: from bosco.isi.edu (bosco.isi.edu []) by core3.amsl.com (Postfix) with ESMTP id 6AFDF3A6819; Thu, 29 Jan 2009 16:21:07 -0800 (PST)
Received: by bosco.isi.edu (Postfix, from userid 70) id 6BE57200267; Thu, 29 Jan 2009 16:20:49 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20090130002049.6BE57200267@bosco.isi.edu>
Date: Thu, 29 Jan 2009 16:20:49 -0800 (PST)
Cc: mip6@ietf.org, rfc-editor@rfc-editor.org
Subject: [Mip6] RFC 5419 on Why the Authentication Data Suboption is Needed for Mobile IPv6 (MIPv6)
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <mip6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mip6>, <mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mip6>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip6>, <mailto:mip6-request@ietf.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

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

        RFC 5419

        Title:      Why the Authentication Data Suboption 
                    is Needed for Mobile IPv6 (MIPv6) 
        Author:     B. Patil, G. Dommety
        Status:     Informational
        Date:       January 2009
        Mailbox:    basavaraj.patil@nokia.com, 
        Pages:      19
        Characters: 45178
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-mip6-whyauthdataoption-07.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5419.txt

Mobile IPv6 defines a set of signaling messages that enable the
mobile node (MN) to authenticate and perform registration with its
home agent (HA).  These authentication signaling messages between the
mobile node and home agent are secured by an IPsec security
association (SA) that is established between the MN and HA.  The MIP6
working group has specified a mechanism to secure the Binding Update
(BU) and Binding Acknowledgement (BAck) messages using an
authentication option, similar to the authentication option in Mobile
IPv4, carried within the signaling messages that are exchanged
between the MN and HA to establish a binding.  This document provides
the justifications as to why the authentication option mechanism is
needed for Mobile IPv6 deployment in certain environments.  This memo 
provides information for the Internet community.

This document is a product of the Mobility for IPv6 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

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@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team
USC/Information Sciences Institute

Mip6 mailing list