Skip to main content

Using IPsec to Protect Mobile IPv6 Signaling Between Mobile Nodes and Home Agents
draft-ietf-mobileip-mipv6-ha-ipsec-06

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: Internet Architecture Board <iab@iab.org>,
    RFC Editor <rfc-editor@rfc-editor.org>, 
    mip6 mailing list <mip6@ietf.org>, 
    mip6 chair <mip6-chairs@tools.ietf.org>
Subject: Protocol Action: 'Using IPsec to Protect Mobile IPv6 
         Signaling between Mobile Nodes and Home Agents' to Proposed 
         Standard 

The IESG has approved the following document:

- 'Using IPsec to Protect Mobile IPv6 Signaling between Mobile Nodes and 
   Home Agents '
   <draft-ietf-mobileip-mipv6-ha-ipsec-07.txt> as a Proposed Standard

This document is the product of the Mobility for IPv6 Working Group. 

The IESG contact persons are Thomas Narten and Mark Townsley.

A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mobileip-mipv6-ha-ipsec-07.txt

Ballot Text

Technical Summary
 
Mobile IPv6 uses IPsec to protect signaling between the home agent and
the mobile node.  The 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.
 
Working Group Summary
 
There was support for this document in the WG.
 
Protocol Quality
 
This document has been reviewed for the IESG by Thomas Narten.

RFC Editor Note:

Delete the following sentence from the Introduction:

       Note that in addition to the use of ESP as specified here, it
       may also be possible to use Authentication Header (AH) [3], but
       for brevity this is not discussed in this specification.

Also, reference [3] should be moved from the "Normative References"
Section to the "Informative References" section.

RFC Editor Note