Re: Fw: [GSMP] more changes to the base draft

Avri Doria <avri@acm.org> Sat, 06 December 2003 01:51 UTC

Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA06609 for <gsmp-archive@odin.ietf.org>; Fri, 5 Dec 2003 20:51:20 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ASRb7-0006dk-0F for gsmp-archive@odin.ietf.org; Fri, 05 Dec 2003 20:51:05 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hB61p4Op025518 for gsmp-archive@odin.ietf.org; Fri, 5 Dec 2003 20:51:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ASRb6-0006dV-T6 for gsmp-web-archive@optimus.ietf.org; Fri, 05 Dec 2003 20:51: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 UAA06606 for <gsmp-web-archive@ietf.org>; Fri, 5 Dec 2003 20:50:49 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ASRb4-0005zl-00 for gsmp-web-archive@ietf.org; Fri, 05 Dec 2003 20:51:02 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1ASRb4-0005zi-00 for gsmp-web-archive@ietf.org; Fri, 05 Dec 2003 20:51:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ASRb4-0006c9-Cm; Fri, 05 Dec 2003 20:51:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ASRaw-0006bl-Bc for gsmp@optimus.ietf.org; Fri, 05 Dec 2003 20:50:54 -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 UAA06596 for <gsmp@ietf.org>; Fri, 5 Dec 2003 20:50:39 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ASRat-0005zT-00 for gsmp@ietf.org; Fri, 05 Dec 2003 20:50:51 -0500
Received: from psg.com ([147.28.0.62] ident=mailnull) by ietf-mx with esmtp (Exim 4.12) id 1ASRat-0005zQ-00 for gsmp@ietf.org; Fri, 05 Dec 2003 20:50:51 -0500
Received: from [147.28.0.62] (helo=acm.org) by psg.com with esmtp (Exim 4.24; FreeBSD 4.9) id 1ASRat-000Jhw-Go for gsmp@ietf.org; Sat, 06 Dec 2003 01:50:51 +0000
Date: Sat, 6 Dec 2003 10:50:14 +0900
Subject: Re: Fw: [GSMP] more changes to the base draft
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Mime-Version: 1.0 (Apple Message framework v553)
From: Avri Doria <avri@acm.org>
To: gsmp@ietf.org
Content-Transfer-Encoding: quoted-printable
In-Reply-To: <9CB758BBEE58754F8F33234D75B9F4B00119B2AA@orsmsx410.jf.intel.com>
Message-Id: <890D517F-278E-11D8-A44D-000393CC2112@acm.org>
X-Mailer: Apple Mail (2.553)
Content-Transfer-Encoding: quoted-printable
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: quoted-printable
Content-Transfer-Encoding: quoted-printable

On lördag, dec 6, 2003, at 10:03 Asia/Seoul, Khosravi, Hormuzd M wrote:

> Hi Avri
>
> I had one question on this..
> Technically speaking GRMP seems quite different from GSMP v3
> to me. How could you possibly merge these protocols ?
> I must be missing something here.
>
>
> Thanks
> Hormuzd
>
>


The structure of the two protocols is very similar in that GRMP uses 
similar protocol protocol mechanisms, in fact GRMP imports much of its 
protocol structure from GSMP almost completely.  What is different, 
primary, is the way the information is expressed.  So yes, it is true 
that the messages for setting state for GMPLS objects is different then 
the way GRMP sets state for the LFBs, but this can be accommodated by 
introducing a new message type, or two, for LFBs.  I am also assuming, 
though I have not worked it out yet, that much of the technology 
specific changes that have been made to support various optical 
technologies could also be used.

As I indicated in my first message to Weiming, we would need to do some 
work to see if the merge is really feasible, but on the basis of my 
initial review, I don't think it would be impossible.  My initial 
reasons when the ForCES group first started out for not really being 
interested in having GSMP adapted to support ForCES was that it could 
complicate the simple structure of GSMP.  Now that we are almost 
finished with the rework of GSMP, it would be V3.1, for GMPLS, the 
structure has gotten at once more flexible and more complex and I think 
the merge could be done with a minimum of pain.

The advantage I see in this is that a controller that could use GSMP 
for controlling GMPLS switches might, with the addition of some 
specific GRMP-like modules could also support IP forwarders.  This 
could be a very strong argument for the folks in Asia, and perhaps 
elsewhere, who are already developing and using GSMP for switch 
control.  I guess the point is that now that the GSMP base has been 
generalized to support any of the varieties of GMPLS switch, it is more 
like other general carrier protocols  (except that it is a vertical 
protocol) - mostly what you have to do is define a payload format for 
the content you wish to carry.

But, this is a very high level analysis, and if we were to do this, and 
that would involve ForCES and AD consultation and charter update etc, 
we would need to put together a design team to work out the details for 
real.

a.


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