[GSMP] more changes to the base draft

Avri Doria <avri@acm.org> Mon, 24 November 2003 08:47 UTC

Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA00123 for <gsmp-archive@odin.ietf.org>; Mon, 24 Nov 2003 03:47:21 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AOCN7-0001sY-7n for gsmp-archive@odin.ietf.org; Mon, 24 Nov 2003 03:47:05 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hAO8l5GH007223 for gsmp-archive@odin.ietf.org; Mon, 24 Nov 2003 03:47:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AOCN6-0001sQ-Ia for gsmp-web-archive@optimus.ietf.org; Mon, 24 Nov 2003 03:47:04 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA00113 for <gsmp-web-archive@ietf.org>; Mon, 24 Nov 2003 03:46:50 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AOCN3-0000cj-00 for gsmp-web-archive@ietf.org; Mon, 24 Nov 2003 03:47:02 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AOCN3-0000cf-00 for gsmp-web-archive@ietf.org; Mon, 24 Nov 2003 03:47:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AOCN2-0001rw-7s; Mon, 24 Nov 2003 03:47:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AOCM4-0001r1-Sj for gsmp@optimus.ietf.org; Mon, 24 Nov 2003 03:46:00 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA00093 for <gsmp@ietf.org>; Mon, 24 Nov 2003 03:45:46 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AOCM1-0000aT-00 for gsmp@ietf.org; Mon, 24 Nov 2003 03:45:57 -0500
Received: from psg.com ([147.28.0.62] ident=mailnull) by ietf-mx with esmtp (Exim 4.12) id 1AOCM1-0000aN-00 for gsmp@ietf.org; Mon, 24 Nov 2003 03:45:57 -0500
Received: from [147.28.0.62] (helo=acm.org) by psg.com with esmtp (Exim 4.24; FreeBSD 4.9) id 1AOCM1-000Kx8-Gi for gsmp@ietf.org; Mon, 24 Nov 2003 08:45:57 +0000
Date: Mon, 24 Nov 2003 17:45:36 +0900
Mime-Version: 1.0 (Apple Message framework v553)
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
From: Avri Doria <avri@acm.org>
To: gsmp@ietf.org
Content-Transfer-Encoding: 7bit
Message-Id: <92A51682-1E5A-11D8-B49D-000393CC2112@acm.org>
X-Mailer: Apple Mail (2.553)
Content-Transfer-Encoding: 7bit
Subject: [GSMP] more changes to the base draft
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

Based on conversations i had in Minneapolis, I have submitted some 
changes intended to support
the adaptation types needed for TDM switches.

    1.  changed Label TLV

           - changed length of label type to 16 bits
          -  added 16 bit adaptation type to tlv header

            (Have not yet started creating a list of adaptation types.  
I am assuming
             this is a global list that would be IANNA supported.
             For the most part I think the adaptation definitions belong 
to the
             technology specific documents, so perhaps subdividing the 
name space
             as was done with labels types is sufficient.  Opinions?)

    2.  changed definition of general adaptation parameter to identify
        special handling to be given to label adaptations. Meaning of
        opaque bit remains the same.  All other behavior to be defined
        in technology specific documents.

              (I am not sure how this technology specific attribute can 
be used.  One
               option was to completely remove the previous adaptation 
field, but I
               thought for backward compatibility it probably should 
remain.  Opinions?)

    3.  added section to port configuration record message to display
        possible adapatation types.  Each record includes the adaptation 
type and the label
       type it can be used with



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

Still need to add more text to the document on how these are used, but 
wanted to make sure that the structural changes were submitted as soon 
as possible so folks could discuss them and so that the folks who need 
to them for the technology specific specs could use them.

I think I am close to having made all the required technical changes to 
the doc and plan to start cleaning up and augmenting the text.  The 
hope is to get this and the packet specific doc  into last call around 
the time of the next IETF meeting.  So, folks, now is a good time to 
start reading and commenting.

cheers
a.



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