6 Appendix A: Product Behavior
The information in this specification is applicable to the following Microsoft products or supplemental software. References to product versions include released service packs:
Windows 2000 operating system Service Pack 4 (SP4)
Windows XP operating system
Windows Server 2003 operating system
Exceptions, if any, are noted below. If a service pack or Quick Fix Engineering (QFE) number appears with the product version, behavior changed in that service pack or QFE. The new behavior also applies to subsequent service packs of the product unless otherwise specified. If a product edition appears with the product version, behavior is different in that product edition.
Unless otherwise specified, any statement of optional behavior in this specification that is prescribed using the terms SHOULD or SHOULD NOT implies product behavior in accordance with the SHOULD or SHOULD NOT prescription. Unless otherwise specified, the term MAY implies that the product does not follow the prescription.
<1> Section 1: Encryption is not supported in Windows 2000 and the associated protocol extensions are not used.
<2> Section 126.96.36.199: In Windows, the encryption key to use is actually generated by the underlying NetMeeting application and, as a result, does not need to be exchanged between the RTC clients through the SIP/SDP signaling. This is handled within the T.120 stream itself, so no k= (key) line for the T.120 media will be present.
<4> Section 188.8.131.52.1: When interoperating with a Windows XP client, the policy of the client can be considered as allowed. The Windows XP client does not send any encryption attribute in the SDP signaling of its INVITE or INVITEresponse, as described in [RFC3261].
<5> Section 184.108.40.206: If the encryption attribute is not present in SDP signaling, as is the case for older Windows XP clients, encryption is not supported. This is different from the DC case because audio/video encryption requires a key exchange through SDP signaling.