RFC 3717: IP over Optical Networks: A Framework
In plain English — editorial summary, not part of the RFC
The Internet transport infrastructure is moving towards a model of high-speed routers interconnected by optical core networks. The architectural choices for the interaction between IP and optical network layers, specifically, the routing and signaling aspects, are maturing. At the same time, a consensus has emerged in the industry on utilizing IP-based protocols for the optical control plane. This document defines a framework for IP over Optical networks, considering both the IP-based control plane for optical networks as well as IP-optical network interactions (together referred to as "IP over optical networks"). This memo provides information for the Internet community.
Document record
- Document ID
- RFC3717
- Published
- March 2004
- Authors
- B. Rajagopalan; J. Luciani; D. Awduche
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- sub
- Pages
- 48
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3604Requirements for Adding Optical Support to the General Switch Management Protocol version 3 (GSMPv3)Current
October 2003
- RFC 3917Requirements for IP Flow Information Export (IPFIX)Current
October 2004
- RFC 2966Domain-wide Prefix Distribution with Two-Level IS-ISObsoleted
October 2000
- RFC 2763Dynamic Hostname Exchange Mechanism for IS-ISObsoleted
February 2000
- RFC 2647Benchmarking Terminology for Firewall PerformanceCurrent
August 1999
- RFC 5301Dynamic Hostname Exchange Mechanism for IS-ISUpdated
October 2008
- RFC 5302Domain-Wide Prefix Distribution with Two-Level IS-ISCurrent
October 2008
- RFC 2072Router Renumbering GuideUpdated
January 1997
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?