RFC 3486:Compressing the Session Initiation Protoc...
RFC-Ref

DNS


Click on the red underlined text to get to the source

... client sending a request to a SIP server typically performs a DNS lookup for the domain name of the server. When NAPTR [4 ...
... SIP server that supports, for instance, three different transport protocols, will have three different DNS entries. Since it is foreseen that the number of transport protocols ...
... by a particular application layer protocol is not going to grow dramatically, having a DNS entry per transport seems like a scalable enough solution. ...
... these layers are transport layer security and compression. If DNS was used to discover the availability of these layers for a particular server, the number of DNS ...
... DNS was used to discover the availability of these layers for a particular server, the number of DNS entries needed for that server would grow dramatically. ...
... signaling compression, would need the 8 DNS entries listed below: 1. TCP ...
... SigComp It is clear that this way of using DNS is not scalable. Therefore, an application layer mechanism to express support of signalling ...


... Dynamic Delegation Discovery System (DDDS) Part Three: The Domain Name System (DNS) Database", RFC 3403prop, October 2002. ...
... Gulbrandsen, A., Vixie, P. and L. Esibov, "A DNS RR for specifying the location of services (DNS SRV ...
... DNS RR for specifying the location of services (DNS SRV)", RFC 2782prop, February 2000. ...



Google
Web
RFC-Ref