The Implications... This is fine; the spaces have different purposes However, movements between spaces are complicated: It may be hard to adopt a VSA as an IETF attribute, even if we wanted to, if there is a type difference Question: what types do VSAs use? A definition of an attribute in Diameter can not be used in RADIUS, two different attributes lead to translation difficulties Only designed movement is RADIUS attribute => Diameter VSA Some people argue that current type system is too limiting Attribute number availability may be a problem too |