What should the behavior of a registrar be if it receives a REGISTER request w/ an Expires: header that has no expiration parameter? In other words, instead of getting
Expires: 3600 it gets Expires: I looked briefly through Section 7 of 3261 and didn't immediately see anything addressing this anomalous case. On the one hand I could see a case for just dropping the message (since it's malformed); on the other hand, a robust implementation might want to reply w/ 200 OK that has a default expiration value associated with it. Thanks, Jeffrey Wright System Test Engineering Manager Aztek Networks _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
