Re: [CCAMP] G.698.2 MIB concerns addressed by ITU-T colleagues

[Fatai Zhang <[e-mail]>]

Hi John,

Thanks, I knew RFC4207 & RFC4209 and LMP is optional and more (~100%) used in I-NNI context.

My concern could be stated in another way more explicitly:

Usecases or scenarios are needed to describe where the black link lies, UNI, E-NNI or I-NNI, and then describe why LMP ext is needed, rather than bring out a lot of parameters to be carried in LMP protocol without justification.



Best Regards

Fatai

From: John E Drake [mailto:[e-mail]]
Sent: Friday, March 14, 2014 8:44 PM
To: Fatai Zhang; Gabriele Maria Galimberti (ggalimbe); Dieter Beller; [e-mail]; [e-mail]
Subject: RE: [CCAMP] G.698.2 MIB concerns addressed by ITU-T colleagues

Fatai,

LMP already has technology specific extensions for SDH and WDM.

Yours Irrespectively,

John

From: CCAMP [mailto:[e-mail]] On Behalf Of Fatai Zhang
Sent: Friday, March 14, 2014 12:57 AM
To: Gabriele Maria Galimberti (ggalimbe); Dieter Beller; [e-mail]<mailto:[e-mail]>; [e-mail]<mailto:[e-mail]>
Subject: Re: [CCAMP] G.698.2 MIB concerns addressed by ITU-T colleagues

Hi Gabriele,

I prefer the first option, because CCAMP always follow the *G*MPLS principle: generic/generalized->specific.

Note that you did not clarify how to justify which parameters can/(can not) be exchanged.


Best Regards

Fatai

From: Gabriele Maria Galimberti (ggalimbe) [mailto:[e-mail]]
Sent: Friday, March 14, 2014 3:42 PM
To: Fatai Zhang; Dieter Beller; [e-mail]<mailto:[e-mail]>; [e-mail]<mailto:[e-mail]>
Subject: Re: [CCAMP] G.698.2 MIB concerns addressed by ITU-T colleagues

Hi All,

Thanks for the comments and suggestion.
The first action I would take is update the draft with the explanations requested during the ccamp session and in mailing list.

I'm not aware of any LMP extensions to support other technologies as Fatai is asking (apart the recent draft on sson),  I think this can be a matter of collaboration
Discussing also whether to extend the existing draft or propose a new one.
I prefer the second option.

I'd also note that the LMP is not an extension of the UNI, LMP is a management protocol to help interface management:
Discovery, negotiation, alarm correlation, etc.
It can run on interfaces not "served" by UNI e.g. On spans between ROADMS.

Regards,

Gabriele
[http://www.cisco.com/swa/i/logo.gif]


Gabriele Galimberti
Technical Leader
Cisco Photonics Srl

Via Philips, 12
20900 - Monza (MI)
Italy
www.cisco.com/global/IT/<http://www.cisco.com/global/IT/>

[e-mail]<mailto:[e-mail]>
Phone :[phone]
Mobile :[phone]
Fax :[phone]












From: Fatai Zhang <[e-mail]<mailto:[e-mail]>>
Date: Friday, March 14, 2014 2:22 AM
To: Dieter Beller <[e-mail]<mailto:[e-mail]>>, "[e-mail]<mailto:[e-mail]>" <[e-mail]<mailto:[e-mail]>>, "[e-mail]<mailto:[e-mail]>" <[e-mail]<mailto:[e-mail]>>
Subject: Re: [CCAMP] G.698.2 MIB concerns addressed by ITU-T colleagues

Hi Ruediger and other authors,

I agree with Dieter's point.

Is it really known what information can/should be exchanged and what can/should not? How to justify?

In addition, do you see any draft about LMP ext over UNI for other technologies such as OTN, WSON, SDH, etc. defined in CCAMP?

If no, why not make this draft more generic?

I would also kindly suggest the authors have a look at the OIF UNI IAs (UNI 1.0 & UNI 2.0 and their difference) to see if it really makes sense to have LMP ext over UNI.


Best Regards

Fatai

From: CCAMP [mailto:[e-mail]] On Behalf Of Dieter Beller
Sent: Thursday, March 13, 2014 11:17 PM
To: [e-mail]<mailto:[e-mail]>; [e-mail]<mailto:[e-mail]>
Subject: Re: [CCAMP] G.698.2 MIB concerns addressed by ITU-T colleagues

Hi Ruediger,
On 13.03.2014 15:36, [e-mail]<mailto:[e-mail]> wrote:
Hi all,

Huub and Dieter mentioned during the CAMP session in London that ITU-T Q6 has some concerns about additional values in document.

Huub mentioned that - I asked a follow-up question regarding the exchange of power values (see below).


Gabriele mentioned the reason for adding these values and we will update the documents with explaining text. During our common meeting with ITU-T at IETF  86 Pete Anslow mentioned: Transmit power may be useful, beyond that I cannot think of anything else you may want to set.

If you guys have still concerns lets discuss these points on the list.
The question I have is the following:

The draft defines LMP protocol messages (sub-objects) to convey the (current?) Output Power at the Ss
reference point and the Current Input Power at the Rs reference point from OXC1 to OLS1 and OXC2 to OLS2,
respectively. This is my interpretation. Now, I would like to understand for what purposes these power values
are exchanged.

My suggestion at the meeting was to add some explanatory text to the draft describing the application that
makes use of these values, i.e., that motivates the definition of these LMP extensions.


Thanks,
Dieter


Best regards

Ruediger







_______________________________________________

CCAMP mailing list

[e-mail]<mailto:[e-mail]>