RFC 3427:Change Process for the Session Initiation...
RFC-Ref

security


Click on the red underlined text to get to the source

... meet to solve the particular problem. The Internet-Draft must also describe in detail any security issues that arise from meeting those requirements. After the Internet-Draft ...


... 5. The proposed header MUST NOT undermine SIP security in any sense. The Internet Draft proposing the new header ...
... Internet Draft proposing the new header MUST address security issues in detail as if it were a Standards Track document. Note that, if the intended application scenario makes certain ...
... that, if the intended application scenario makes certain assumptions regarding security, the security considerations only need to meet the intended application scenario ...
... application scenario makes certain assumptions regarding security, the security considerations only need to meet the intended application scenario rather than the ...
... application scenario rather than the general Internet case. In any case, security issues need to be discussed for arbitrary usage scenarios (including the general Internet ...
... syntax and semantics, event package considerations, security considerations, and examples of usage. The author should submit his or her proposal as an individual Internet- ...
... 5. The proposed package MUST NOT undermine SIP security in any sense. The Internet Draft proposing the new package MUST address ...
... Internet Draft proposing the new package MUST address security issues in detail as if it were a Standards Track document. Security issues need to be discussed for arbitrary ...
... security issues in detail as if it were a Standards Track document. Security issues need to be discussed for arbitrary usage scenarios (including the general Internet case). ...


... Security Considerations ...
... Complexity and indeterminate or hard to define protocol behavior, depending on which of many extensions operate, is a fine breeding ground for security flaws. All Internet-Drafts ...
... SIP must include a discussion of the security requirements and implications inherent in the proposal. All RFCs that modify or extend SIP must ...
... inherent in the proposal. All RFCs that modify or extend SIP must show that they have adequate security and do not worsen SIP's existing security considerations ...
... security and do not worsen SIP's existing security considerations. ...



Google
Web
RFC-Ref