[Hipsec] RFC 8046 on Host Mobility with the Host Identity Protocol

rfc-editor@rfc-editor.org Wed, 15 February 2017 01:39 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: hipsec@ietfa.amsl.com
Delivered-To: hipsec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 100CB129493; Tue, 14 Feb 2017 17:39:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level:
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U7Zz6e64RMS5; Tue, 14 Feb 2017 17:39:32 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EC097129469; Tue, 14 Feb 2017 17:39:32 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 1BA63B81467; Tue, 14 Feb 2017 17:39:32 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20170215013932.1BA63B81467@rfc-editor.org>
Date: Tue, 14 Feb 2017 17:39:32 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/hipsec/MjMg7CF-YIfRpOLT0tnv3AyNqoY>
Cc: drafts-update-ref@iana.org, hipsec@ietf.org, rfc-editor@rfc-editor.org
Subject: [Hipsec] RFC 8046 on Host Mobility with the Host Identity Protocol
X-BeenThere: hipsec@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "This is the official IETF Mailing List for the HIP Working Group." <hipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/hipsec>, <mailto:hipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/hipsec/>
List-Post: <mailto:hipsec@ietf.org>
List-Help: <mailto:hipsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hipsec>, <mailto:hipsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Feb 2017 01:39:34 -0000

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

        
        RFC 8046

        Title:      Host Mobility with the Host 
                    Identity Protocol 
        Author:     T. Henderson, Ed.,
                    C. Vogt,
                    J. Arkko
        Status:     Standards Track
        Stream:     IETF
        Date:       February 2017
        Mailbox:    tomhend@u.washington.edu, 
                    mail@christianvogt.net, 
                    jari.arkko@piuha.net
        Pages:      37
        Characters: 86483
        Obsoletes:  RFC 5206

        I-D Tag:    draft-ietf-hip-rfc5206-bis-14.txt

        URL:        https://www.rfc-editor.org/info/rfc8046

        DOI:        10.17487/RFC8046

This document defines a mobility extension to the Host Identity
Protocol (HIP).  Specifically, this document defines a "LOCATOR_SET"
parameter for HIP messages that allows for a HIP host to notify peers
about alternate addresses at which it may be reached.  This document
also defines how the parameter can be used to preserve communications
across a change to the IP address used by one or both peer hosts.
The same LOCATOR_SET parameter can also be used to support end-host
multihoming (as specified in RFC 8047).  This document obsoletes RFC
5206.

This document is a product of the Host Identity Protocol Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: 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 Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

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

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

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