Elwell, John wrote:
Vijay,
[...]
RFC 3261 section 8.1.1 states:
"A valid SIP request formulated by a UAC MUST, at a minimum, contain
   the following header fields: To, From, CSeq, Call-ID, Max-Forwards,
   and Via; all of these header fields are mandatory in all SIP
   requests.  [...]
Even if all these header fields are not strictly needed by entities that
support sipsec, I think we should continue to mandate them, even if they
contain dummy values. Otherwise it might have unnecessary impact on SIP
stacks or might lead to unexpected responses (e.g. 400).

John: You are absolutely right.  Miraculously, the authors of the
draft acquired selective amnesia with respect to S8.1.1 of rfc3261
when drafting the contents of the CONNECT request ;-)

This will be rectified in subsequent revisions with appropriate
view towards privacy.

Thanks,

- vijay
--
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
2701 Lucent Lane, Rm. 9F-546, Lisle, Illinois 60532 (USA)
Email: [EMAIL PROTECTED],bell-labs.com,acm.org}
WWW:   http://www.alcatel-lucent.com/bell-labs


_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use [EMAIL PROTECTED] for questions on current sip
Use [EMAIL PROTECTED] for new developments on the application of sip

Reply via email to