Chapter 10 of RFC 3261 describes the way to process REGISTER requests.

There's no description of any screening of the Contact header uri. 

It's now very common to compare it with an ACL to disallow URLs that is 
considered dangerous, like URLs pointing to internal servers in a service 
provider's network.

I also see a case where a proxy on an IPv4 only network might choose not to 
accept IPv6 contacts.

When reading chapter 10, I realize that there's no documented way of refusing a 
REGISTER because of an invalid Contact - syntax error, policy error or 
something else. The text seems to describe a process where we store any 
authenticated valid requests in the location database to perform selection, 
prioritization and validation when using the result of a lookup.

Have I missed something? Is this described somewhere else?

regards,
/Olle
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors

Reply via email to