[Hipsec] RFC 8003 on Host Identity Protocol (HIP) Registration Extension

rfc-editor@rfc-editor.org Fri, 14 October 2016 23:36 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 D514512968C; Fri, 14 Oct 2016 16:36:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.598
X-Spam-Level:
X-Spam-Status: No, score=-105.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-2.996, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 6R4GfCU7RUHU; Fri, 14 Oct 2016 16:36:41 -0700 (PDT)
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 22A9B129683; Fri, 14 Oct 2016 16:36:40 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 162EFB809D9; Fri, 14 Oct 2016 16:36:40 -0700 (PDT)
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: <20161014233640.162EFB809D9@rfc-editor.org>
Date: Fri, 14 Oct 2016 16:36:40 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/hipsec/6qME56S7IewZu2oXTtgZeIfNslw>
Cc: drafts-update-ref@iana.org, hipsec@ietf.org, rfc-editor@rfc-editor.org
Subject: [Hipsec] RFC 8003 on Host Identity Protocol (HIP) Registration Extension
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: Fri, 14 Oct 2016 23:36:50 -0000

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

        
        RFC 8003

        Title:      Host Identity Protocol (HIP) Registration 
                    Extension 
        Author:     J. Laganier,
                    L. Eggert
        Status:     Standards Track
        Stream:     IETF
        Date:       October 2016
        Mailbox:    julien.ietf@gmail.com, 
                    lars@netapp.com
        Pages:      16
        Characters: 34717
        Obsoletes:  RFC 5203

        I-D Tag:    draft-ietf-hip-rfc5203-bis-11.txt

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

        DOI:        http://dx.doi.org/10.17487/RFC8003

This document specifies a registration mechanism for the Host
Identity Protocol (HIP) that allows hosts to register with services,
such as HIP rendezvous servers or middleboxes.  This document
obsoletes RFC 5203.

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