A Framework for Defining Network Complexity
RFC 7980
Revision differences
Document history
Date | Rev. | By | Action |
---|---|---|---|
2018-12-20
|
02 | (System) | Received changes through RFC Editor sync (changed abstract to 'Complexity is a widely used parameter in network design, yet there is no generally accepted definition … Received changes through RFC Editor sync (changed abstract to '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.') |
2016-10-21
|
02 | (System) | Received changes through RFC Editor sync (created alias RFC 7980, changed abstract to 'Complexity is a widely used parameter in network design, yet there … Received changes through RFC Editor sync (created alias RFC 7980, changed abstract to '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.', changed pages to 24, changed standardization level to Informational, changed state to RFC, added RFC published event at 2016-10-21, changed ISE state to Published RFC) |
2016-10-21
|
02 | (System) | RFC published |
2016-10-20
|
02 | (System) | RFC Editor state changed to AUTH48-DONE from AUTH48 |
2016-10-17
|
02 | (System) | RFC Editor state changed to AUTH48 from RFC-EDITOR |
2016-09-22
|
02 | (System) | RFC Editor state changed to RFC-EDITOR from EDIT |
2016-09-07
|
02 | (System) | RFC Editor state changed to EDIT |
2016-09-06
|
02 | (System) | IANA Action state changed to No IC from In Progress |
2016-09-06
|
02 | (System) | IANA Action state changed to In Progress |
2016-09-06
|
02 | Nevil Brownlee | ISE state changed to Sent to the RFC Editor from In IESG Review |
2016-09-06
|
02 | Nevil Brownlee | Sent request for publication to the RFC Editor |
2016-07-18
|
02 | (System) | IANA Review state changed to IANA OK - No Actions Needed |
2016-07-18
|
02 | Amanda Baber | (Via drafts-eval@iana.org): IESG/Authors/WG Chairs: IANA has reviewed draft-behringer-ncrg-complexity-framework-02 and has the following comments: We understand that this document doesn't require any IANA actions. While … (Via drafts-eval@iana.org): IESG/Authors/WG Chairs: IANA has reviewed draft-behringer-ncrg-complexity-framework-02 and has the following comments: We understand that this document doesn't require any IANA actions. While it's often helpful for a document's IANA Considerations section to remain in place upon publication even if there are no actions, if the authors strongly prefer to continue without an IANA Considerations section, IANA does not object. If this assessment is not accurate, please respond as soon as possible. Thank you, Amanda Baber IANA Lead Specialist ICANN |
2016-07-18
|
02 | Nevil Brownlee | ISE state changed to In IESG Review from Finding Reviewers |
2016-07-18
|
02 | Nevil Brownlee | IETF conflict review initiated - see conflict-review-behringer-ncrg-complexity-framework |
2016-07-18
|
02 | Nevil Brownlee | Changed document writeup |
2016-07-18
|
02 | Nevil Brownlee | Notification list changed to "Nevil Brownlee" <rfc-ise@rfc-editor.org> |
2016-07-18
|
02 | Nevil Brownlee | Document shepherd changed to Nevil Brownlee |
2016-04-25
|
02 | Michael Behringer | New version available: draft-behringer-ncrg-complexity-framework-02.txt |
2015-10-18
|
01 | Nevil Brownlee | ISE state changed to Finding Reviewers |
2015-10-18
|
01 | Nevil Brownlee | Intended Status changed to Informational from None |
2015-10-18
|
01 | Nevil Brownlee | Stream changed to ISE from None |
2015-10-07
|
01 | Alvaro Retana | This document now replaces draft-irtf-ncrg-network-design-complexity, draft-retana-network-complexity-framework, draft-irtf-ncrg-complexity-framework instead of draft-irtf-ncrg-network-design-complexity, draft-irtf-ncrg-complexity-framework |
2015-10-06
|
01 | Michael Behringer | New version available: draft-behringer-ncrg-complexity-framework-01.txt |
2015-08-21
|
00 | Michael Behringer | New version available: draft-behringer-ncrg-complexity-framework-00.txt |