[GSMP] RFC 3532 on Requirements for the Dynamic Partitioning of Switching Elements
rfc-editor@rfc-editor.org Tue, 06 May 2003 09:47 UTC
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA12921 for <gsmp-archive@odin.ietf.org>; Tue, 6 May 2003 05:47:14 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h469tdJ05717 for gsmp-archive@odin.ietf.org; Tue, 6 May 2003 05:55:39 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h469tc805714 for <gsmp-web-archive@optimus.ietf.org>; Tue, 6 May 2003 05:55:38 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA12902 for <gsmp-web-archive@ietf.org>; Tue, 6 May 2003 05:46:43 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Cz44-0004bq-00 for gsmp-web-archive@ietf.org; Tue, 06 May 2003 05:48:48 -0400
Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19Cz44-0004bm-00 for gsmp-web-archive@ietf.org; Tue, 06 May 2003 05:48:48 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h469tI805695; Tue, 6 May 2003 05:55:18 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h45Glw816233 for <gsmp@optimus.ietf.org>; Mon, 5 May 2003 12:47:58 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA07305; Mon, 5 May 2003 12:39:23 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Cj1u-0006wH-00; Mon, 05 May 2003 12:41:30 -0400
Received: from gamma.isi.edu ([128.9.144.145]) by ietf-mx with esmtp (Exim 4.12) id 19Cj1o-0006vx-00; Mon, 05 May 2003 12:41:24 -0400
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6p2/8.11.2) with ESMTP id h45GfR028120; Mon, 5 May 2003 09:41:27 -0700 (PDT)
Message-Id: <200305051641.h45GfR028120@gamma.isi.edu>
To: IETF-Announce:;
Cc: rfc-editor@rfc-editor.org, gsmp@ietf.org
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Mon, 05 May 2003 09:41:27 -0700
Subject: [GSMP] RFC 3532 on Requirements for the Dynamic Partitioning of Switching Elements
Sender: gsmp-admin@ietf.org
Errors-To: gsmp-admin@ietf.org
X-BeenThere: gsmp@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/gsmp>, <mailto:gsmp-request@ietf.org?subject=unsubscribe>
List-Id: General Switch Management Protocol <gsmp.ietf.org>
List-Post: <mailto:gsmp@ietf.org>
List-Help: <mailto:gsmp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/gsmp>, <mailto:gsmp-request@ietf.org?subject=subscribe>
A new Request for Comments is now available in online RFC libraries. RFC 3532 Title: Requirements for the Dynamic Partitioning of Switching Elements Author(s): T. Anderson, J. Buerkle Status: Informational Date: May 2003 Mailbox: todd.a.anderson@intel.com, joachim.buerkle@nortelnetworks.com Pages: 11 Characters: 25119 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-gsmp-dyn-part-reqs-03.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3532.txt This document identifies a set of requirements for the mechanisms used to dynamically reallocate the resources of a switching element (e.g., an ATM switch) to its partitions. These requirements are particularly critical in the case of an operator creating a switch partition and then leasing control of that partition to a third party. This document is a product of the General Switch Management Protocol Working Group of the IETF. 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: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_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 unlimited distribution.echo 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.