Browse Prior Art Database

Home Network Prefix Renumbering in Proxy Mobile IPv6 (PMIPv6) (RFC8191) Disclosure Number: IPCOM000250592D
Original Publication Date: 2017-Aug-01
Included in the Prior Art Database: 2017-Aug-05
Document File: 20 page(s) / 21K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

Z. Yan: AUTHOR [+2]


At the time of writing, network managers prefer Provider-Independent (PI) addressing for IPv6 to attempt to minimize the need for future possible renumbering. However, a widespread use of PI addresses will cause Border Gateway Protocol (BGP) scaling problems [RFC7010]. It is thus desirable to develop tools and practices that make IPv6 renumbering a simpler process to reduce demand for IPv6 PI space [RFC6879]. In this document, we aim to support HNP renumbering when the HNP in PMIPv6 [RFC5213] is not a PI prefix.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 12% of the total text.

Internet Engineering Task Force (IETF)                            Z. Yan Request for Comments: 8191                                         CNNIC Category: Standards Track                                         J. Lee ISSN: 2070-1721                                     Sangmyung University                                                                   X. Lee                                                                    CNNIC                                                              August 2017

      Home Network Prefix Renumbering in Proxy Mobile IPv6 (PMIPv6)


   In the basic Proxy Mobile IPv6 (PMIPv6) specification, a Mobile Node    (MN) is assigned with a Home Network Prefix (HNP) during its initial    attachment, and the MN configures its Home Address (HoA) with the    HNP.  During the movement of the MN, the HNP remains unchanged to    keep ongoing communications associated with the HoA.  However, the    current PMIPv6 specification does not specify related operations when    HNP renumbering has occurred (e.g., due to change of service provider    or site topology, etc.).  In this document, a solution to support HNP    renumbering is proposed, as an optional extension of the PMIPv6    specification.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force    (IETF).  It represents the consensus of the IETF community.  It has    received public review and has been approved for publication by the    Internet Engineering Steering Group (IESG).  Further information on    Internet Standards is available in Section 2 of RFC 7841.

   Information about the current status of this document, any errata,    and how to provide feedback on it may be obtained at

 Yan, et al.                  Standards Track                    [Page 1]
 RFC 8191                 PMIPv6 HNP Renumbering              August 2017

 Copyright Notice

   Copyright (c) 2017 IETF Trust and the persons identified as the    document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal    Provisions Relating to IETF Documents    ( in effect on the date of    publication of this document.  Please review these documents    carefully, as they describe your rights and restrictions with respect    to this document.  Code Components extracted from this document must    include Simpl...