The MPLS WG Archive

[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index][Thread Index][Author Index][Subject Index]

Proposal for structuring control plane work in the Routing area: Take 2

From: "David R. Oran" <oran@cisco.com>
Date: Wed, 2 Aug 2000 14:54:03 -0400
Cc: <mpls@UU.NET>, <te-wg@UU.NET>, <ip-optical@lists.bell-labs.com>
Importance: Normal
X-MIME-Autoconverted: from 8bit to quoted-printable by wodc7mr2.ffx.ops.us.uu.net id QQjagi07159
X-SMAP-Received-From: outside
X-SMTP-HELO: wodc7-2.corprelay.mail.uu.net
X-SMTP-MAIL-FROM: owner-mpls@UU.NET
X-SMTP-PEER-INFO: wodc7-2.corprelay.mail.uu.net [192.48.96.69]

			This is a Proposal
		...it is only a proposal
			Do not pass GO
		Do not collect 200 lamdas
			(at least not yet...)

Control Plane work organizational Goals
• Goal: divide the work in a way that
– Clearly maintains independence among the control plane signaling protocols
(e.g. RSVP-TE, CR-LDP), the routing protocols (e.g. ISIS, OSPF, BGP), and
the encapsulation methods (e.g. MPLS, GRE, IPSEC)
– Expeditiously moves new work on restoration, link characterization,
disjoint path computation, forward in a way that is generic across layer 1/2
technologies.
• Goal: provide home for "Foo-over-MPLS" sorts of things
• Goal: ensure IPO is focused on optical-specific issues, such as
– encapsulation,
– MIBS,
– Optical-specific requirements on control plane
Proposal
• We initiate a group in the Routing Area to undertake the generalized parts
of the control plane, with specific milestones for
– restoration,
– link management,
– and diversity routing as a starting point.
• This could be either a Routing-Area WG or one or more new WGs
• Work effort will also consider "Foo-over-MPLS" items where consensus
exists to do so

• This obviously need lots of work and has many un-answered questions, but
that's our proposed starting point.
• Further discussion should occur on the routing-discussion@ietf.org mailing
list