RFC 3776 on Using IPsec to Protect Mobile IPv6 Signaling Between Mobile Nodes and Home Agents
rfc-editor@rfc-editor.org Thu, 10 June 2004 13:27 UTC
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA02992 for <ietf-announce-archive@ietf.org>; Thu, 10 Jun 2004 09:27:34 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BYPah-0003bh-0E for ietf-announce-archive@ietf.org; Thu, 10 Jun 2004 09:27:35 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BYPVN-0001vh-00 for ietf-announce-archive@ietf.org; Thu, 10 Jun 2004 09:22:05 -0400
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx with esmtp (Exim 4.12) id 1BYPQq-00009g-00; Thu, 10 Jun 2004 09:17:24 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BYOph-0003I7-65; Thu, 10 Jun 2004 08:39:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BYDNV-0007F1-0q for ietf-announce@megatron.ietf.org; Wed, 09 Jun 2004 20:25:09 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA05632 for <ietf-announce@ietf.org>; Wed, 9 Jun 2004 20:25:07 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BYDNT-0007WS-Ca for ietf-announce@ietf.org; Wed, 09 Jun 2004 20:25:07 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BYDMR-0006dC-00 for ietf-announce@ietf.org; Wed, 09 Jun 2004 20:24:04 -0400
Received: from boreas.isi.edu ([128.9.160.161]) by ietf-mx with esmtp (Exim 4.12) id 1BYDLk-0005WW-00 for ietf-announce@ietf.org; Wed, 09 Jun 2004 20:23:20 -0400
Received: from ISI.EDU (adma.isi.edu [128.9.160.239]) by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id i5A0LnJ13043; Wed, 9 Jun 2004 17:21:49 -0700 (PDT)
Message-Id: <200406100021.i5A0LnJ13043@boreas.isi.edu>
To: IETF-Announce:;
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Wed, 09 Jun 2004 17:21:49 -0700
X-ISI-4-30-3-MailScanner: Found to be clean
X-MailScanner-From: rfc-ed@isi.edu
X-Mailman-Approved-At: Thu, 10 Jun 2004 08:38:44 -0400
Cc: mobile-ip@sunroof.eng.sun.com, rfc-editor@rfc-editor.org
Subject: RFC 3776 on Using IPsec to Protect Mobile IPv6 Signaling Between Mobile Nodes and Home Agents
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ietf-announce.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
Sender: ietf-announce-bounces@ietf.org
Errors-To: ietf-announce-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=-1.5 required=5.0 tests=AWL,MIME_BOUND_NEXTPART, NO_REAL_NAME autolearn=no version=2.60
A new Request for Comments is now available in online RFC libraries.
RFC 3776
Title: Using IPsec to Protect Mobile IPv6 Signaling
Between Mobile Nodes and Home Agents
Author(s): J. Arkko, V. Devarapalli, F. Dupont
Status: Standards Track
Date: June 2004
Mailbox: jari.arkko@ericsson.com, vijayd@iprg.nokia.com,
Francis.Dupont@enst-bretagne.fr
Pages: 40
Characters: 87076
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-mobileip-mipv6-ha-ipsec-06.txt
URL: ftp://ftp.rfc-editor.org/in-notes/rfc3776.txt
Mobile IPv6 uses IPsec to protect signaling between the home agent
and the mobile node. Mobile IPv6 base document defines the main
requirements these nodes must follow. This document discusses these
requirements in more depth, illustrates the used packet formats,
describes suitable configuration procedures, and shows how
implementations can process the packets in the right order.
This document is a product of the IP Routing for Wireless/Mobile Hosts
Working Group of the IETF.
This is now a Proposed Standard Protocol.
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@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.echo
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.
_______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce