Hi, >> I have reviewed this document as part of the security directorate's ongoing effort to review all IETF documents being processed by the IESG. >> These comments were written primarily for the benefit of the security area directors. Document editors and WG chairs should treat these comments just like any other last call comments. >> >> The subject matter is outside my area of expertise and proper understanding of the document requires reading of several referenced documents. But I think I got the gist of what the document is trying to do. >> >> The Security Consideration talks about data channels providing confidentiality, integrity and source authentication for MSRP traffic, which is good. It also points out to discussion of MSRP message attribution in RFC 4975. >> >> However, session setup is done over SIP, which has different security considerations and nothing is mentioned about that. > The mechanism does not require SIP - it only requires use of offer/answer. > Ok. >> Granted, offer/answer is mostly used together with SIP, but there is no such requirement, and we normally reference the SIP Security Considerations in offer/answer specifications. > I think you need to point this out explicitly in the security consideration. I could say: "If the Session Initiation Protocol (SIP) [RFC3261] is used to implement the offer/answer transactions for establishing the MSRP data channel, the SIP Security Considerations in [RFC3261] apply." Regards, Christer -- last-call mailing list last-call@xxxxxxxx https://www.ietf.org/mailman/listinfo/last-call
