[homenet] RFC 7695 on Distributed Prefix Assignment Algorithm

rfc-editor@rfc-editor.org Tue, 24 November 2015 16:19 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 15CFE1A88BA; Tue, 24 Nov 2015 08:19:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.487
X-Spam-Level:
X-Spam-Status: No, score=-107.487 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.585, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
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 qu4Gwbr-dHdT; Tue, 24 Nov 2015 08:19:42 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id 2A2901A8F3D; Tue, 24 Nov 2015 08:19:35 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 0F717180009; Tue, 24 Nov 2015 08:17:58 -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: <20151124161758.0F717180009@rfc-editor.org>
Date: Tue, 24 Nov 2015 08:17:58 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/dPgE-dTyhGFJrbHhRRUWLTv4eL0>
Cc: homenet@ietf.org, rfc-editor@rfc-editor.org
Subject: [homenet] RFC 7695 on Distributed Prefix Assignment Algorithm
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/homenet/>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Nov 2015 16:19:44 -0000

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

        
        RFC 7695

        Title:      Distributed Prefix Assignment Algorithm 
        Author:     P. Pfister, B. Paterson, J. Arkko
        Status:     Standards Track
        Stream:     IETF
        Date:       November 2015
        Mailbox:    pierre.pfister@darou.fr, 
                    paterson.b@gmail.com, 
                    jari.arkko@piuha.net
        Pages:      20
        Characters: 46244
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-homenet-prefix-assignment-08.txt

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

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

This document specifies a distributed algorithm for dividing a set of 
prefixes in a manner that allows for automatic assignment of sub-prefixes 
that are unique and non-overlapping.  Used in conjunction with a protocol 
that provides flooding of information among a set of participating nodes, 
prefix configuration within a network may be automated.

This document is a product of the Home Networking 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/rfc.html

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