
|
Issues Update Issue 5. Need to signal discrete set of possible values for parameters (in connection with using Status: some support, approaches suggested by Ronald Bless & Dave Oran; some opposition, continuous (not discrete) values OK Changes TBD: if agreed, describe mechanism to signal multiple choices of parameter values Issue 6. Need for "service schedule" as an optional parameter? Status: No support, too complex, no requirement Issue 7. PHB parameters & encodings. Status: Discussion with David Black, resolved to use RFC 3140 encoding of PHB Issue 8. Need to differentiate generic & optional QSPEC parameters? Status: Dave Oran suggests breakdown by 'traffic-description' & 'constraints' parameters in lieu of generic/optional parameters this has generally been followed in the updated I-D: |