The following are a few comments and questions concerning draft-ietf-bliss-shared-appearances-00.
Concerning appearance seize, how does the seized appearance (from PUBLISH) actually get associated with outgoing INVITE appearance? More specifically, is the outbound proxy/b2bua receiving the INVITE supposed to assume this INVITE corresponds to the PUBLISHed seized appearance? And if so, what is explicitly/implicitly tying the two together? If PUBLISH not used to seize the appearance (prior to sending INVITE), section 5.3 indicates that the caller PUBLISHes the appearance from NOTIFY. Since the Appearance Agent is already aware of the current appearance status, at what point in the flow is such a PUBLISH needed? Concerning incoming calls, why using Alert-Info to indicate the appearance instead of defining or using another header? I ask mainly because I'm not currently aware of a defined value for indicating that the Alert-Info's absoluteURI should be ignored. The following are a few nits: Section 1: "aappearance". Section 10.2: Paragraph starting "F1 to F4" is not correctly formatted within the txt version. Within the same paragraph, "sate" should be "state". Thanks, Brett _______________________________________________ BLISS mailing list [email protected] https://www.ietf.org/mailman/listinfo/bliss
