IRS Architectural Framework
draft-dimitri-irs-arch-frame-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Papadimitriou Dimitri , Martin Vigoureux , Wouter Tavernier , Didier Colle | ||
| Last updated | 2013-04-19 (Latest revision 2012-10-16) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document details the possible architectural and design choices in order to determine i) the spatial location of the so-called "IRS interface" and the functional entities it directly and/or indirectly involves, ii) the number of levels of redirection between routing modules and application (and associated identifier space), and iii) the various constraints that can be anticipated when dealing with the coupling of functional planes including the prevention of oscillations between two or more routing system states, coupling effects (leading to amplification chains) and, concurrency (leading to antagonistic action-reaction).
Authors
Papadimitriou Dimitri
Martin Vigoureux
Wouter Tavernier
Didier Colle
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)