%% You should probably cite draft-bryant-mpls-sfl-framework instead of this I-D. @techreport{bryant-mpls-synonymous-flow-labels-01, number = {draft-bryant-mpls-synonymous-flow-labels-01}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-bryant-mpls-synonymous-flow-labels/01/}, author = {Stewart Bryant and George Swallow and Siva Sivabalan and Greg Mirsky and Mach Chen and Zhenbin Li}, title = {{RFC6374 Synonymous Flow Labels}}, pagetotal = 14, year = 2015, month = jul, day = 4, abstract = {{[}Editor's note - there was a comment that synonymous was not the right term because synonymous implied a greater degree of interchangeability than is actually the case (there is only one way interchangeability). I have looked for other terms, and so far I have only come up with enhanced and multi-purpose, but they are not quite right either. I plan to continue with the term unless anyone has a better idea.{]} This document describes a method of providing flow identification information when making RFC6374 performance measurements. This allows RFC6374 measurements to be made on multi-point to point LSPs and allows the measurement of flows within an MPLS construct using RFC6374.}, }