[6lo] RFC 8929 on IPv6 Backbone Router

rfc-editor@rfc-editor.org Mon, 23 November 2020 20:05 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: 6lo@ietfa.amsl.com
Delivered-To: 6lo@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 00EF53A0BF5; Mon, 23 Nov 2020 12:05:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0
X-Spam-Level:
X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[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 Abj1QS10Ys61; Mon, 23 Nov 2020 12:05:21 -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 7804F3A0BF4; Mon, 23 Nov 2020 12:05:13 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 054BAF40782; Mon, 23 Nov 2020 12:05:12 -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
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, 6lo@ietf.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20201123200512.054BAF40782@rfc-editor.org>
Date: Mon, 23 Nov 2020 12:05:12 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/6lo/ALXakv7jwfl37qbHbXfSRQVxV1I>
Subject: [6lo] =?utf-8?q?RFC_8929_on_IPv6_Backbone_Router?=
X-BeenThere: 6lo@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Mailing list for the 6lo WG for Internet Area issues in IPv6 over constrained node networks." <6lo.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/6lo>, <mailto:6lo-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/6lo/>
List-Post: <mailto:6lo@ietf.org>
List-Help: <mailto:6lo-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/6lo>, <mailto:6lo-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Nov 2020 20:05:27 -0000

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

        
        RFC 8929

        Title:      IPv6 Backbone Router 
        Author:     P. Thubert, Ed.,
                    C.E. Perkins, 
                    E. Levy-Abegnoli
        Status:     Standards Track
        Stream:     IETF
        Date:       November 2020
        Mailbox:    pthubert@cisco.com, 
                    charliep@computer.org, 
                    elevyabe@cisco.com
        Pages:      32
        Updates:    RFC 6775, RFC 8505

        I-D Tag:    draft-ietf-6lo-backbone-router-20.txt

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

        DOI:        10.17487/RFC8929

This document updates RFCs 6775 and 8505 in order to enable proxy
services for IPv6 Neighbor Discovery by Routing Registrars called
"Backbone Routers". Backbone Routers are placed along the wireless
edge of a backbone and federate multiple wireless links to form a
single Multi-Link Subnet (MLSN).

This document is a product of the IPv6 over Networks of Resource-constrained Nodes 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