RFC 8425 on IANA Considerations for IPv6 Neighbor Discovery Prefix Information Option Flags
rfc-editor@rfc-editor.org Mon, 30 July 2018 23:23 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C5C3C130E10; Mon, 30 Jul 2018 16:23:25 -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 T4jyo3r1oxOU; Mon, 30 Jul 2018 16:23:24 -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 0F126130DD5; Mon, 30 Jul 2018 16:23:24 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 60FFBB810C8; Mon, 30 Jul 2018 16:23:12 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8425 on IANA Considerations for IPv6 Neighbor Discovery Prefix Information Option Flags
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, ipv6@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20180730232312.60FFBB810C8@rfc-editor.org>
Date: Mon, 30 Jul 2018 16:23:12 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/lOXxbcWxtJGiAVTRrR_8aj3E-mM>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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: Mon, 30 Jul 2018 23:23:26 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8425
Title: IANA Considerations for IPv6 Neighbor Discovery
Prefix Information Option Flags
Author: O. Troan
Status: Standards Track
Stream: IETF
Date: July 2018
Mailbox: ot@cisco.com
Pages: 4
Characters: 6692
Updates: RFC 4861
I-D Tag: draft-ietf-6man-ndpioiana-04.txt
URL: https://www.rfc-editor.org/info/rfc8425
DOI: 10.17487/RFC8425
The Prefix Information Option (PIO) in the IPv6 Neighbor Discovery
Router Advertisement message defines an 8-bit flag field; this field
has two flags defined, and the remaining 6 bits are reserved
(Reserved1). RFC 6275 defines a flag from this field without
creating an IANA registry or updating RFC 4861. The purpose of this
document is to create an IANA registry for the PIO flags. This
document updates RFC 4861.
This document is a product of the IPv6 Maintenance 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