IRS Architectural Framework
draft-dimitri-irs-arch-frame-00

Document Type Expired Internet-Draft (individual)
Last updated 2013-04-19 (latest revision 2012-10-16)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-dimitri-irs-arch-frame-00.txt

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 (dimitri.papadimitriou@alcatel-lucent.com)
Martin Vigoureux (martin.vigoureux@alcatel-lucent.com)
Wouter Tavernier (wouter.tavernier@intec.ugent.be)
Didier Colle (didier.colle@intec.ugent.be)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)