question on draft-ietf-sipping-rtcp-summary-05

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Howdy,
draft-ietf-sipping-rtcp-summary-05 has a body field named "CallID", which it says "provides the call id from the SIP header".  Does this mean it's the Call-ID from the NOTIFY/PUBLISH request, or from the call it's reporting about?  The examples show it's from the NOT/PUB message, but I don't understand the value of putting that in the body, compared to the one from the call being reported about.

The draft also says "The REPORTER SHALL populate the Request-URI of the NOTIFY method with the address of the COLLECTOR."  AFAIK, the Notify should follow the Subscribe dialog, and thus the req-uri should follow the rules for any in-dialog requests per 3261.

-hadriel

_______________________________________________
Sipping mailing list  https://www.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@xxxxxxxxxxxxxxx for questions on current sip
Use sip@xxxxxxxx for new developments of core SIP

[Index of Archives]     [IETF Announce]     [IETF Discussion]     [Linux SCSI]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [XFree86]     [Big List of Linux Books]

  Powered by Linux