[DMM] RFC 8371 on Mobile Node Identifier Types for MIPv6

rfc-editor@rfc-editor.org Tue, 24 July 2018 05:44 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: dmm@ietfa.amsl.com
Delivered-To: dmm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8992C13105D; Mon, 23 Jul 2018 22:44:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 0thuyU6WG3AO; Mon, 23 Jul 2018 22:44:04 -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 45545131053; Mon, 23 Jul 2018 22:44:04 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 357B9B80C2A; Mon, 23 Jul 2018 22:43:56 -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
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, dmm@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20180724054356.357B9B80C2A@rfc-editor.org>
Date: Mon, 23 Jul 2018 22:43:56 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmm/3P9TYxjXBqSPmOpU8CQOUDuIVgs>
Subject: [DMM] RFC 8371 on Mobile Node Identifier Types for MIPv6
X-BeenThere: dmm@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: Distributed Mobility Management Working Group <dmm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmm>, <mailto:dmm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmm/>
List-Post: <mailto:dmm@ietf.org>
List-Help: <mailto:dmm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dmm>, <mailto:dmm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Jul 2018 05:44:08 -0000

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

        
        RFC 8371

        Title:      Mobile Node Identifier Types for MIPv6 
        Author:     C. Perkins,
                    V. Devarapalli
        Status:     Standards Track
        Stream:     IETF
        Date:       July 2018
        Mailbox:    charliep@computer.org, 
                    dvijay@gmail.com
        Pages:      16
        Characters: 34580
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-dmm-4283mnids-08.txt

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

        DOI:        10.17487/RFC8371

This document defines additional identifier type numbers for use with
the mobile node identifier option for Mobile IPv6 (MIPv6) as defined
by RFC 4283.

This document is a product of the Distributed Mobility Management 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