Subject: RE: [SIP] discussion

From: Jonathan Rosenberg <[email-masked]>
Date: Tue, 31 Oct 2000 11:58:19 -0500

These are ignored. Thats what optional means, although this probably needs
to be clarified. The text in Section 6 currently reads:

The header fields required, optional and not applicable for each method are
listed in Table 4 and Table 5.
The table uses "o" to indicate optional, "m" mandatory and "-" for not
applicable. "m*" indicates a header
that SHOULD be sent, but servers need to be prepared to receive requests
without that header field. A "*"
indicates that the header fields are needed only if message body is not
empty. See sections 6.18, 6.19 and 8
for details.

I would suggest:

The header fields required, optional, and not applicable for each method are
listed in Table 4 and Table 5. The table uses "o" to indicate optional, "m"
mandatory and "-" for not applicable. Optional means that a UAC \MAY include
the header in a request, and a UAS \MAY ignore the header if present in the
request. Similarly, an optional response header implies that a UAS \MAY
place the header in a response, and the UAC \MAY ignore the header if
present in a response it receives. A mandatory request header means the
header \MUST be present in a request, and \MUST be understood by the UAS
receiving the request. A mandatory response header means the header \MUST be
present in the response, and the header \MUST be understood by the UAS
processing the response. "Not applicable" for request headers means the
header \SHOULDNOT be present in a request. If one is placed in a request, it
\SHOULD be ignored by the UAS receiving the request. Similarly, a header
"not applicable" for a response means the UAS \SHOULDNOT place the header in
the response, and the UAC \SHOULD ignore the header in the response. "m*"
indicates a header
that SHOULD be sent, but servers need to be prepared to receive requests
without that header field. A "*"
indicates that the header fields are needed only if message body is not
empty. See sections 6.18, 6.19 and 8
for details.

Sound OK?

---
Jonathan D. Rosenberg                       72 Eagle Rock Ave.
Chief Scientist                             First Floor
dynamicsoft                                 East Hanover, NJ 07936
[email-masked]                     FAX:   (973) 952-5050
http://www.cs.columbia.edu/~jdrosen         PHONE: (973) 952-5000
http://www.dynamicsoft.com

> -----Original Message-----
> From: james jack [mailto:[email-masked]]
> Sent: Tuesday, October 31, 2000 7:02 AM
> To: [email-masked]
> Subject: [SIP] discussion
> 
> 
> Dear All:
>       I have one question to ask, If an request
> contains 
> One header that is not applicable according to
> RFC2543bis
> 02, for example, in REGISTER request, there appear
> Alert-info, Priority,
> how to cope with this request, 400 response code or
> discard this header
> and continue to process? 
>       Could anyone give me some advice or suggestion
> for processing such stuation? 
>      Best regards!
>                                Yours:james
>   
> 
> 
> __________________________________________________
> Do You Yahoo!?
> Yahoo! Messenger - Talk while you surf!  It's FREE.
> http://im.yahoo.com/
> 
> _______________________________________________
> SIP mailing list
> [email-masked]
> http://lists.bell-labs.com/mailman/listinfo/sip
> 

_______________________________________________
SIP mailing list
[email-masked]
http://lists.bell-labs.com/mailman/listinfo/sip