[rfc-dist] RFC 3717 on IP over Optical Networks: A Framework
Tue, 02 Mar 2004 15:32:15 -0800
A new Request for Comments is now available in online RFC libraries.
Title: IP over Optical Networks: A Framework
Author(s): B. Rajagopalan, J. Luciani, D. Awduche
Date: March 2004
Mailbox: firstname.lastname@example.org, email@example.com,
I-D Tag: draft-ietf-ipo-framework-05.txt
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 document is a product of the IP over Optical Working Group of the
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 list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG. Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body
help: ways_to_get_rfcs. For example:
Subject: getting rfcs
Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC
Authors, for further information.
Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute
Below is the data which will enable a MIME compliant Mail Reader
implementation to automatically retrieve the ASCII version
of the RFCs.
Content-Type: Multipart/Alternative; Boundary="OtherAccess"