RFC 7980 on A Framework for Defining Network Complexity
rfc-editor@rfc-editor.org Fri, 21 October 2016 19:09 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 9C4C11296AC for <ietf-announce@ietfa.amsl.com>; Fri, 21 Oct 2016 12:09:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.033
X-Spam-Level:
X-Spam-Status: No, score=-103.033 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.431, 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 m2JySJwjNyir for <ietf-announce@ietfa.amsl.com>; Fri, 21 Oct 2016 12:09:40 -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 574A31297D4 for <ietf-announce@ietf.org>; Fri, 21 Oct 2016 12:09:40 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 4FEB4B820EE; Fri, 21 Oct 2016 12:09:40 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7980 on A Framework for Defining Network Complexity
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20161021190940.4FEB4B820EE@rfc-editor.org>
Date: Fri, 21 Oct 2016 12:09:40 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/5w-NPnt38zfIvEEq9FH462GvRZo>
Cc: drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: ietf@ietf.org
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: Fri, 21 Oct 2016 19:09:41 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 7980
Title: A Framework for Defining Network
Complexity
Author: M. Behringer, A. Retana,
R. White, G. Huston
Status: Informational
Stream: Independent
Date: October 2016
Mailbox: mbehring@cisco.com,
aretana@cisco.com,
russw@riw.us,
gih@apnic.net
Pages: 24
Characters: 56510
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-behringer-ncrg-complexity-framework-02.txt
URL: https://www.rfc-editor.org/info/rfc7980
DOI: http://dx.doi.org/10.17487/RFC7980
Complexity is a widely used parameter in network design, yet there is
no generally accepted definition of the term. Complexity metrics
exist in a wide range of research papers, but most of these address
only a particular aspect of a network, for example, the complexity of
a graph or software. While it may be impossible to define a metric
for overall network complexity, there is a desire to better
understand the complexity of a network as a whole, as deployed today
to provide Internet services. This document provides a framework to
guide research on the topic of network complexity as well as some
practical examples for trade-offs in networking.
This document summarizes the work of the IRTF's Network Complexity
Research Group (NCRG) at the time of its closure. It does not
present final results, but a snapshot of an ongoing activity, as a
basis for future work.
INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. 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