RE: Common feature sets: scenarios, term
[email protected] (Reynolds Franklin NRC/Boston)
| Newsgroups | gmane.ietf.medfree |
|---|---|
| Organization | Nokia Telecommunications |
| Message-ID | <[email protected]> |
>Candidate functional requirements: >---------------------------------- > >(R1) Extension of capability expressions to allow "indirect references" to >"common feature sets". > >(R2) Extension of capability expressions to allow "delegation" between >expressions. > >(R3) Procedure for registration of tags to describe common feature sets. > >(R4) Interpretation of URIs used to denote common feature sets. > >(R5) Guidelines for profiling the use of (R1), (R2) in specific >applications and/or protocols. > > >------------ >Graham Klyne >([email protected]) I don't think I understand (R2). I think someway to override a feature assertion within a common feature set (override a default) is valuable. I also think it is valuable to be able to dynamically change a single feature assertion without retransmitting the entire feature set. Franklin Reynolds