[GSMP] capability sets
avri <avri@apocalypse.org> Mon, 23 June 2003 14:27 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 KAA22622 for <gsmp-archive@odin.ietf.org>; Mon, 23 Jun 2003 10:27:35 -0400 (EDT)
Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5NER8G12216 for gsmp-archive@odin.ietf.org; Mon, 23 Jun 2003 10:27:08 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19USHk-0003Ax-NV for gsmp-web-archive@optimus.ietf.org; Mon, 23 Jun 2003 10:27:08 -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 KAA22595 for <gsmp-web-archive@ietf.org>; Mon, 23 Jun 2003 10:27:04 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19USHi-0002X9-00 for gsmp-web-archive@ietf.org; Mon, 23 Jun 2003 10:27:06 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19USHc-0002X5-00 for gsmp-web-archive@ietf.org; Mon, 23 Jun 2003 10:27:00 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19USHd-00039V-Cw; Mon, 23 Jun 2003 10:27:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19USGn-00035v-Ez for gsmp@optimus.ietf.org; Mon, 23 Jun 2003 10:26:09 -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 KAA22565 for <gsmp@ietf.org>; Mon, 23 Jun 2003 10:26:05 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19USGl-0002Wl-00 for gsmp@ietf.org; Mon, 23 Jun 2003 10:26:07 -0400
Received: from relay2.kornet.net ([211.48.62.162]) by ietf-mx with esmtp (Exim 4.12) id 19USGa-0002Vz-00 for gsmp@ietf.org; Mon, 23 Jun 2003 10:25:56 -0400
Received: from [220.89.170.14] (avri@apocalypse.org) by relay2.kornet.net (Terrace Internet Messaging Server) with ESMTP id 2003062323:24:24:491978.11561.11 for <gsmp@ietf.org>; Mon, 23 Jun 2003 23:24:24 +0900 (KST)
Date: Mon, 23 Jun 2003 23:24:24 +0900
Mime-Version: 1.0 (Apple Message framework v552)
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
From: avri <avri@apocalypse.org>
To: gsmp@ietf.org
Content-Transfer-Encoding: 7bit
Message-Id: <63B4D448-A586-11D7-9101-000393CC2112@apocalypse.org>
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Subject: [GSMP] capability sets
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>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
the one in the base spec now, is technology specific, so it will need to be moved to the packet based spec. 2 questions: -should each technology have a specific capability set definition. i think so, but am interested in hearing other opinions. -can it remain the fixed size? [capset id, traffic flags] [tech specific] [tech specific] the capset id would be subdivided to allow each technology its own range. or should it be variable? i.e. [capset id, length] [flags, tech specific] . . [tech specific] opinions please? i tend toward the fixed option, but if there is a good reason for a variable length block, please let me know. i am especially interested in hearing from the tech specific design teams. thanks a. _______________________________________________ GSMP mailing list GSMP@ietf.org https://www1.ietf.org/mailman/listinfo/gsmp
- [GSMP] capability sets avri
- Re: [GSMP] capability sets Kenneth Sundell