Re: [GSMP] update of base draft

Avri Doria <avri@acm.org> Thu, 02 October 2003 07:41 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA06313 for <gsmp-archive@odin.ietf.org>; Thu, 2 Oct 2003 03:41:31 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A4y5F-0004nM-Mn for gsmp-archive@odin.ietf.org; Thu, 02 Oct 2003 03:41:09 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h927f9Mr018426 for gsmp-archive@odin.ietf.org; Thu, 2 Oct 2003 03:41:09 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A4y5E-0004n7-Rj for gsmp-web-archive@optimus.ietf.org; Thu, 02 Oct 2003 03:41: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 DAA06298 for <gsmp-web-archive@ietf.org>; Thu, 2 Oct 2003 03:41:00 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A4y5C-0004BY-00 for gsmp-web-archive@ietf.org; Thu, 02 Oct 2003 03:41:06 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1A4y5B-0004BV-00 for gsmp-web-archive@ietf.org; Thu, 02 Oct 2003 03:41:05 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A4y5A-0004lr-0t; Thu, 02 Oct 2003 03:41:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A4y52-0004lR-O3 for gsmp@optimus.ietf.org; Thu, 02 Oct 2003 03:40:56 -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 DAA06292 for <gsmp@ietf.org>; Thu, 2 Oct 2003 03:40:48 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A4y50-0004BL-00 for gsmp@ietf.org; Thu, 02 Oct 2003 03:40:54 -0400
Received: from psg.com ([147.28.0.62] ident=mailnull) by ietf-mx with esmtp (Exim 4.12) id 1A4y4z-0004BI-00 for gsmp@ietf.org; Thu, 02 Oct 2003 03:40:53 -0400
Received: from [147.28.0.62] (helo=acm.org) by psg.com with esmtp (Exim 4.22) id 1A4y4z-000FbI-ML for gsmp@ietf.org; Thu, 02 Oct 2003 07:40:53 +0000
Date: Thu, 2 Oct 2003 16:40:16 +0900
Subject: Re: [GSMP] update of base draft
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
From: Avri Doria <avri@acm.org>
To: gsmp@ietf.org
Content-Transfer-Encoding: 7bit
In-Reply-To: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAAlsvaVBJ1K0aAUMmT6B5cJcKAAAAQAAAAIY95FNeiGU6lCvA+DLogngEAAAAA@icu.ac.kr>
Message-Id: <AA24E496-F4AB-11D7-8F1A-000393CC2112@acm.org>
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
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 WG <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

Hi,

thanks for your comments.

On torsdag, okt 2, 2003, at 15:56 Asia/Seoul, passjay wrote:

> There are some typing errors in base draft(03).
>
> - page 23, line 1; 0x1 --> 0x2
> - page 83, line 24; &amp&amp --> &&

thanks

>
> AND more,
> In "draft-ietf-gsmp-reqs-06.txt" referred switch configuration in
> section 2.3. for layer switching identification. But the base spec(03)
> does not specify this function. In optical spec section 8.1 we proposed
> one way of identification of optical switch spec block. However, this
> block should be carefully taken into consideration in base spec to
> support general form of switch configuration. According to the
> requirements, base spec should provide a guideline to extend and modify
> switch configuration for general purpose.

Yes, I missed that.  I will look into adding either the technology 
specific block or a specific, but general purpose, layering field/block 
to the configuration message.  This will show up in the next draft 
though i will send the list a proposal next week.

Which reminds me that I am still waiting for a contribution (perhaps 
part of the TDM spec) that discusses layering in detail and proposes 
methods for handling it beyond this configuration message.

a.




_______________________________________________
GSMP mailing list
GSMP@ietf.org
https://www1.ietf.org/mailman/listinfo/gsmp