- From: Koen Holtman <koen@win.tue.nl>
- Date: Thu, 24 Jul 1997 21:10:22 +0200 (MET DST)
- To: Henning Schulzrinne <hgs@cs.columbia.edu>
- Cc: http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com, confctrl@isi.edu
Henning Schulzrinne: > >I brought this up at the San Jose meeting, but there never was a >satisfactory (official) answer, as far as I remember. > >SIP and RTSP re-use a number of HTTP status codes, among other >properties. It is likely that they may need to or want to adopt other >HTTP status codes that emerge in the future. Thus, it is desirable that >the SIP and RTSP-specific status codes do not conflict with HTTP codes. > >One possible solution: Declare officially that HTTP will only use status >codes up to x49 (say) and leave others for private extensions, including >SIP and RTSP. I don't know if there are any deployed implementations of SIP and RTPS already. If there are not, I would suggest using 4 digits for all SIP and RTPS codes not inherited from HTTP, e.g. 1xxx for SIP and 2xxx for RTPS. HTTP-inherited codes could be 0xxx or simply xxx. >Henning Koen.
Received on Thursday, 24 July 1997 12:14:40 UTC