RFC 5726 on Mobile IPv6 Location Privacy Solutions

rfc-editor@rfc-editor.org Thu, 18 February 2010 18:21 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9581228C31F for <ietf-announce@core3.amsl.com>; Thu, 18 Feb 2010 10:21:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.564
X-Spam-Level:
X-Spam-Status: No, score=-2.564 tagged_above=-999 required=5 tests=[AWL=0.036, BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tzCas0SynWpf for <ietf-announce@core3.amsl.com>; Thu, 18 Feb 2010 10:21:44 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id 89DE528C30C for <ietf-announce@ietf.org>; Thu, 18 Feb 2010 10:21:44 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 3AC92130014; Thu, 18 Feb 2010 10:23:28 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5726 on Mobile IPv6 Location Privacy Solutions
From: rfc-editor@rfc-editor.org
Message-Id: <20100218182328.3AC92130014@rfc-editor.org>
Date: Thu, 18 Feb 2010 10:23:28 -0800 (PST)
Cc: rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Feb 2010 18:21:45 -0000

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

        
        RFC 5726

        Title:      Mobile IPv6 Location Privacy Solutions 
        Author:     Y. Qiu, F. Zhao,
                    Ed., R. Koodli
        Status:     Experimental
        Date:       February 2010
        Mailbox:    qiuying@i2r.a-star.edu.sg, 
                    fanzhao@google.com, 
                    rkoodli@cisco.com
        Pages:      48
        Characters: 116016
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-irtf-mobopts-location-privacy-solutions-16.txt

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

Mobile IPv6 (RFC 3775) enables a mobile node to remain reachable
while it roams on the Internet.  However, the location and movement
of the mobile node can be revealed by the IP addresses used in
signaling or data packets.  In this document, we consider the Mobile
IPv6 location privacy problem described in RFC 4882, and propose
efficient and secure techniques to protect location privacy of the
mobile node.  This document is a product of the IP Mobility
Optimizations (MobOpts) Research Group.  This document defines 
an Experimental Protocol for the Internet community.

This document is a product of the IRTF.


EXPERIMENTAL: This memo defines an Experimental Protocol for the
Internet community.  It does not specify an Internet standard of any
kind. Discussion and suggestions for improvement are requested.
Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

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
Association Management Solutions, LLC