LMP transport [Was: Re: Soliciting comments on moving drafts to WG status]

"Adrian Farrel" <adrian@olddog.co.uk> Tue, 10 August 2004 17:46 UTC

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA16787 for <ccamp-archive@ietf.org>; Tue, 10 Aug 2004 13:46:21 -0400 (EDT)
Received: from psg.com ([147.28.0.62] ident=mailnull) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BuamA-0001Tg-56 for ccamp-archive@ietf.org; Tue, 10 Aug 2004 13:51:07 -0400
Received: from majordom by psg.com with local (Exim 4.41 (FreeBSD)) id 1BuaQv-0008yj-Ds for ccamp-data@psg.com; Tue, 10 Aug 2004 17:29:09 +0000
Received: from [80.168.70.141] (helo=relay1.mail.uk.clara.net) by psg.com with esmtp (Exim 4.41 (FreeBSD)) id 1BuaQE-0008sO-KZ for ccamp@ops.ietf.org; Tue, 10 Aug 2004 17:28:26 +0000
Received: from du-069-0680.access.clara.net ([217.158.156.171] helo=Puppy) by relay1.mail.uk.clara.net with smtp (Exim 4.34) id 1BuaQD-0009V6-3w; Tue, 10 Aug 2004 18:28:26 +0100
Message-ID: <020601c47eff$73f78ca0$2e849ed9@Puppy>
Reply-To: Adrian Farrel <adrian@olddog.co.uk>
From: Adrian Farrel <adrian@olddog.co.uk>
To: zafar ali <zali@cisco.com>, ccamp@ops.ietf.org
References: <000601c47ef0$e478f680$0200a8c0@amer.cisco.com>
Subject: LMP transport [Was: Re: Soliciting comments on moving drafts to WG status]
Date: Tue, 10 Aug 2004 18:13:24 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on psg.com
X-Spam-Status: No, hits=-3.7 required=5.0 tests=AWL,BAYES_00, NEW_DOMAIN_EXTENSIONS autolearn=no version=2.64
Sender: owner-ccamp@ops.ietf.org
Precedence: bulk
X-Spam-Score: 2.1 (++)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Content-Transfer-Encoding: 7bit

> Conditional "yes" to draft-aboulmagd-ccamp-transport-lmp-02.txt, depending
> on the answer to the following:
>
> Does Author plan to address link management solution space between ASON and
> GMPLS in the same document? I would prefer that and in which case I think
> adaptation of this document as a WG document to be deferred to a later
> point.

Hi Zafar,

I'm not quite clear what you mean by "address link management solution space". Do you mean
a comparison of the ways that LMP is used and any extensions that may have been made to
the protocol? Or do you mean an analysis of what needs to be "fixed" and the appropriate
new extensions to the protocol?

If the latter, I think a question that led in this direction was asked in SD.

Kireeti's response was to the effect that we have to do the analysis first, identifying
the "secret decoder ring", and showing the differences between the ITU and IETF views.
Then we would start a series of liaisons to SG15 to figure out what needs to be fixed and
by whom. Finally, work could begin on protocol modifications.

This document is targeted at the first step only.

OTOH, if you meant the first option (i.e. a comparison of how the protocol is used and
what extensions have already been made), that seems to me to be valuable in this document.

What do the authors say?

Cheers,
Adrian