From: "DRAGE, Keith \(Keith\)" <[EMAIL PROTECTED]> Well, at the moment, what I am trying to do is get some understanding of what we should scope as valid SIP work.
I've been busy, so I may be behind in the discussion, but it's not clear to me that there is anything that needs to be done specifically for SIP. I may well be wrong, but my impression is that MIME already has the features and specifications neede so that a receiver can decide whether it has adequately "understood" the document when it only understands some components. These mechanisms are all inherited by SIP and I would expect be a sufficient set of rules. E.g., a UAC that sends a request with a multipart body must expect that some UASs will respond with 415, and have some strategy in place for dealing with that situation. Similarly, a UAC that sends a nested multipart body must expect that some UASs will be unable to process the nested multipart, and will either ignore it or reject the request (as specified), and the UAC must be prepared to deal with that situation. Is there a reason we need to define new, narrower subsets of allowed behaviors and define a SIP mechanism to negotiate these? Dale _______________________________________________ Sip mailing list https://www1.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use [EMAIL PROTECTED] for questions on current sip Use [EMAIL PROTECTED] for new developments on the application of sip
