Fw: [GSMP] more changes to the base draft

"Wang,Weiming" <wmwang@mail.hzic.edu.cn> Wed, 26 November 2003 08:52 UTC

Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA27862 for <gsmp-archive@odin.ietf.org>; Wed, 26 Nov 2003 03:52:57 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AOvPa-0004ip-Nw for gsmp-archive@odin.ietf.org; Wed, 26 Nov 2003 03:52:41 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hAQ8qc5R018144 for gsmp-archive@odin.ietf.org; Wed, 26 Nov 2003 03:52:38 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AOvPa-0004iO-BG for gsmp-web-archive@optimus.ietf.org; Wed, 26 Nov 2003 03:52:38 -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 DAA27814 for <gsmp-web-archive@ietf.org>; Wed, 26 Nov 2003 03:52:24 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AOvPX-0001fZ-00 for gsmp-web-archive@ietf.org; Wed, 26 Nov 2003 03:52:35 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AOvPX-0001fK-00 for gsmp-web-archive@ietf.org; Wed, 26 Nov 2003 03:52:35 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AOvP0-0004fh-Jg; Wed, 26 Nov 2003 03:52:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AOvOk-0004et-FV for gsmp@optimus.ietf.org; Wed, 26 Nov 2003 03:51:46 -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 DAA27783 for <gsmp@ietf.org>; Wed, 26 Nov 2003 03:51:32 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AOvOh-0001fC-00 for gsmp@ietf.org; Wed, 26 Nov 2003 03:51:43 -0500
Received: from [61.175.198.82] (helo=ns1.hzic.net) by ietf-mx with esmtp (Exim 4.12) id 1AOvOg-0001f9-00 for gsmp@ietf.org; Wed, 26 Nov 2003 03:51:43 -0500
Received: from WWM (unverified [61.175.198.84]) by ns1.hzic.net (Rockliffe SMTPRA 4.5.6) with SMTP id <B0000726302@ns1.hzic.net> for <gsmp@ietf.org>; Wed, 26 Nov 2003 17:00:38 +0800
Message-ID: <02e301c3b3fa$b0b2ce50$845c21d2@Necom.hzic.edu.cn>
From: "Wang,Weiming" <wmwang@mail.hzic.edu.cn>
To: <gsmp@ietf.org>
Subject: Fw: [GSMP] more changes to the base draft
Date: Wed, 26 Nov 2003 16:52:58 +0800
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: base64
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Content-Transfer-Encoding: base64
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: base64
Content-Transfer-Encoding: base64

 Hi Avri,
 
 I'm writing to seek the possiblity in GSMP base header to add following items:
 
 1. A proirity flag to indicate the processing priority for the message.
 2. An optional checksum part in GSMP for error control.
 
 If possible, I also ask to leave some space in the Version field for possible including of other 
 possible protocols like GRMP (http://www.ietf.org/internet-drafts/draft-wang-forces-grmp-01.txt). 
 
 Thank you. 
 
 Weiming
 
 ----- Original Message ----- 
> From: "Avri Doria" <avri@acm.org>
> To: <gsmp@ietf.org>
> Sent: Monday, November 24, 2003 4:45 PM
> Subject: [GSMP] more changes to the base draft
> 
> 
> > 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
>