Hi,
I believe to have stumbled on two bugs in examples.
1) Quotation from draft-ietf-sipping-reg-event-00.txt, p. 18:
"Later on, the user registers (5):
REGISTER sip:[EMAIL PROTECTED] SIP/2.0
Via: SIP/2.0/UDP pc34.bar.com;branch=z9hG4bKnaaff
From: sip:[EMAIL PROTECTED];tag=99a8s
To: sip:[EMAIL PROTECTED]
Call-ID: [EMAIL PROTECTED]
CSeq: 9976 REGISTER
Contact: sip:[EMAIL PROTECTED]"
The Request-URI in this example violates RFC 3261, sec. 10.2:
"The userinfo and "@" components of the SIP URI MUST NOT be present."
2) The 200 OK in the REGISTER example of RFC 3261, sec. 24.1 contains
an Expires header, but no expires parameter in the Contact header.
This violates RFC 3261, sec. 10.3, bullet 8:
"Each Contact value MUST feature an "expires" parameter
indicating its expiration interval chosen by the registrar."
Regards,
Peter Paeppinghaus
--
Dr. Peter Päppinghaus
Siemens AG | Phone: +49 89 - 722 40065
ICM N PG U ID A1 | Fax: +49 89 - 722 58726
Hofmannstr. 51 | Visitors: Building 1713 / Room 714
D - 81359 München | Email: [EMAIL PROTECTED]
_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
