Just the obvious comment that while consistency within PCE is good, yet YANG shows no signs of being able to model floating point values.
Tom Petch ----- Original Message ----- From: "Dhruv Dhody" <[email protected]> To: <[email protected]> Sent: Monday, September 28, 2015 1:21 PM Subject: [Pce] Encoding in draft-ietf-pce-pcep-service-aware Hi All, In the service-aware draft [1], the new metric type encoding were similar to the IGP ([2][3]) encoding with 24-bits integer format. In this we deviated from RFC5440 [4] and other metric types where the metric value is always encoded in 32-bits in IEEE floating point format [5]. The authors discussed and wanted to align it to the rest of PCEP and use 32-bits floating point instead. Please find the attached update and the diff file for your reference. WG, please let us know if you disagree with this change. [1] https://tools.ietf.org/html/draft-ietf-pce-pcep-service-aware-07#section -4.1.1.1 [2] https://tools.ietf.org/html/rfc7471 [3] http://www.ietf.org/internet-drafts/draft-ietf-isis-te-metric-extensions -07.txt [4] https://tools.ietf.org/html/rfc5440#section-7.8 [5] http://ieeexplore.ieee.org/servlet/opac?punumber=4610933 Regards, Dhruv (on behalf of co-authors) ------------------------------------------------------------------------ -------- > _______________________________________________ > Pce mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/pce > _______________________________________________ Pce mailing list [email protected] https://www.ietf.org/mailman/listinfo/pce
