Subject: RE: [Sip] draft-sparks-sip-mimetypes-00

From: Robert Sparks <[email-masked]>
Date: Thu, 6 Sep 2001 14:06:25 -0400

Based on feedback from Dean, I'm going to change the
encoding considerations section in this draft to the following:

SIP specifies UTF-8 encoding. While most header names and data
elements will lie in the 7-bit ascii compatible range, data
elements and SIP bodies may contain 8-bit values. In order to
preserve the "readability" of SIP messages being carried as the
body of other messages, message/sip parts (including any body parts 
the message/sip message contains) SHOULD be UTF-8 encoded. If 
transcoding a contained body part is not feasible, the message/sip
part MAY be binary encoded. If the transport is not 8-bit clean,
encoding formats such as base-64 can be used.

Any other comments?

RjS
> -----Original Message-----
> From: Robert Sparks [mailto:[email-masked]]
> Sent: Friday, August 31, 2001 4:33 PM
> To: [email-masked]'
> Subject: [Sip] draft-sparks-sip-mimetypes-00
> 
> 
> I've submitted a stab at a registration document
> for message/sip and message/sipfrag to the repository.
> Until it shows up, it is available at
> http://www.nostrum.com/~rjsparks/draft-sparks-sip-mimetypes-00.txt
> 
> RjS 
> 
> _______________________________________________
> Sip mailing list  http://www1.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use [email-masked] for questions on current sip
> Use [email-masked] for new developments on the application of sip
> 

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