Subject: Re: [CCAMP] using RFC6205 encoding of wavelengths in draft-galikunze-ccamp-g-698-2-snmp-mib-01 and draft-dharinigert-ccamp-g-698-2-lmp-01

From: "Gabriele Maria Galimberti (ggalimbe)" <[email-masked]>
Date: Tue, 4 Dec 2012 09:04:54 +0000

Hi Chris,

Thanks for your comment and let us apologize for the late answer.

We agree to code the wavelengths as per RFC6205 definition.
We'll circulate the new draft version soon.

Best 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/>

[email-masked]<mailto:[email-masked]>
Phone :+39 039 2091462
Mobile :+39 335 7481947
Fax :+39 039 2092049

From: Chris Bowers <[email-masked]<mailto:[email-masked]>>
Date: Thursday, November 8, 2012 5:16 PM
To: "[email-masked]<mailto:[email-masked]>" <[email-masked]<mailto:[email-masked]>>
Subject: [CCAMP] using RFC6205 encoding of wavelengths in draft-galikunze-ccamp-g-698-2-snmp-mib-01 and draft-dharinigert-ccamp-g-698-2-lmp-01

Both draft-galikunze-ccamp-g-698-2-snmp-mib-0 and draft-dharinigert-ccamp-g-698-2-lmp-01 specify wavelengths in THz.   This would also require specifying the floating-point representation for proper encoding.

Instead, I would suggest that these drafts use the wavelength encoding defined in RFC6205.  This will allow the absolute wavelength values to be encoded as integer values for the encoded grid and channel spacing.  It also avoids creating multiple wavelength encodings in documents produced by CCAMP.

Chris