Sureļ¼ a long length shall break a parser,this happed . Date: Sun, 19 Apr 2015 16:40:57 -0400 From: [email protected] To: [email protected] CC: [email protected] Subject: Re: [alto] Restrictions on cost-type names?
Wendy, I see the same. The formal definition is at the beginning of Sec. 9.2.2. It is JSONString. I assume that an arbitrary long string may break a parser. What other potential issues do you see? Thanks, Richard On Friday, April 17, 2015, Wendy Roome <[email protected]> wrote: Does RFC 7285 define any restrictions on cost-type names? Eg, length or character set? I am referring to the names in the IRD meta for a combination of cost-metric & cost-mode. Eg, "num-routing" in "meta" : { "cost-types": { "num-routing": { "cost-mode" : "numerical", "cost-metric": "routingcost", "description": "My default" }, As near as I can tell, while we rigorously defined cost metric names, resource ids, and everything else, we missed cost-type names. - Wendy Roome -- Richard _______________________________________________ alto mailing list [email protected] https://www.ietf.org/mailman/listinfo/alto
_______________________________________________ alto mailing list [email protected] https://www.ietf.org/mailman/listinfo/alto
