[Diffserv-interest] diffserv control plane

Kathleen Nichols <nichols@pollere.com> Thu, 29 September 2005 18:46 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EL3Qi-0006Zx-Cq; Thu, 29 Sep 2005 14:46:52 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EL3Qg-0006Zp-BW; Thu, 29 Sep 2005 14:46:50 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA27769; Thu, 29 Sep 2005 14:46:48 -0400 (EDT)
Received: from outbound.mailhop.org ([63.208.196.171] ident=mailnull) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EL3YO-0001kc-MW; Thu, 29 Sep 2005 14:54:48 -0400
Received: from c-24-6-155-12.hsd1.ca.comcast.net ([24.6.155.12] helo=[10.1.1.74]) by outbound.mailhop.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.51) id 1EL3Qf-000IoT-2z; Thu, 29 Sep 2005 14:46:49 -0400
X-Mail-Handler: MailHop Outbound by DynDNS
X-Originating-IP: 24.6.155.12
X-Report-Abuse-To: abuse@dyndns.com (see http://www.mailhop.org/outbound/abuse.html for abuse reporting information)
X-MHO-User: kmnichols
Message-ID: <433C368A.7010003@pollere.com>
Date: Thu, 29 Sep 2005 11:46:34 -0700
From: Kathleen Nichols <nichols@pollere.com>
User-Agent: Mozilla Thunderbird 1.0 (Macintosh/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: diffserv-interest@ietf.org, end2end-interest@postel.org, dcpel@ietf.org
X-Enigmail-Version: 0.90.1.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793
Content-Transfer-Encoding: 7bit
Cc: Scott Bradner <sob@harvard.edu>
Subject: [Diffserv-interest] diffserv control plane
X-BeenThere: diffserv-interest@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Differentiated services general discussion <diffserv-interest.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/diffserv-interest>, <mailto:diffserv-interest-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:diffserv-interest@ietf.org>
List-Help: <mailto:diffserv-interest-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/diffserv-interest>, <mailto:diffserv-interest-request@ietf.org?subject=subscribe>
Sender: diffserv-interest-bounces@ietf.org
Errors-To: diffserv-interest-bounces@ietf.org

We've been working toward a possible IETF BoF on diffserv control plane
elements to be under the Operations and Management Area. Our in-progress
Background and Goals for the BoF:

It's been some time since the Diffserv forwarding path elements were
standardized. At that time, the approach was to get the mechanisms
deployed in routers so that approaches to service creation and control
plane could be attempted. Before closing, the Diffserv WG defined the
concept of Per-Domain Behaviors (PDBs) in RFC 3086, but left the
approach to controling PDBs open.

Now Diffserv forwarding elements are available in most routers and are
in use to create services in some networks. A variety of approaches are
being used for control and management of Diffserv but there appears to
be some commonality. A possible path for IETF work is to enumerate and
classify the common elements and to work toward some best common
practices. Additionally, it may be useful to present specifications for
a range of diffserv control plane elements using common interfaces.

The major issues to deploying Diffserv-based services are primarily
operational. The deployment must be cost-effective, be secured against
vulnerabilities and not become a vehicle for denial of service attacks.
Standardization should result in existing toolsets being either expanded
to cover more needed functionality or to interact with other tools. A
standardization effort should cover how to secure the architecture to
mitigate vulnerabilities. Standards for a control plane QoS agent for
routers may be useful. A desired outcome of IETF efforts is to make
multiple products available to network operators, obviating the time and
personnel expense of individual solutions. The end goal is to enable
more services, both for network customers and for control of the
network, without taxing personnel.

The starting point for a BoF is to look at what's out there, determine
if there is indeed some uniformity of approach useful as a starting
point, and determine what's missing.

The intial focus would be the intradomain control plane moving to
interdomain or AS under same provider and finally to interprovider or
interoperator.

------------------------------------------------------------------

The entire in-progress proposal for the BoF can be viewed at
www.pollere.com under Resources, then Current Work.

If you are interested in helping to further shape the proposal, please
sign up for the email list dcpel@ietf.org through
www1.ietf.org/mailman/listinfo/dcpel and comment on the list.

	thanks,
		Kathie Nichols
		Scott Bradner

_______________________________________________
Diffserv-interest mailing list
Diffserv-interest@ietf.org
https://www1.ietf.org/mailman/listinfo/diffserv-interest