Hi Cullen,
I would still like to stress that, even if the payload is binary, you
still need to use the binary transfer encoding. What about the following
change:
OLD:
Consequently, UAs MUST use the binary transfer encoding for binary
payloads in SIP.
NEW:
Consequently, UAs MUST use the binary transfer encoding for all
payloads in SIP, including binary payloads.
Cheers,
Gonzalo
Cullen Jennings wrote:
This document is good and looks ready to go to IESG.
One thing I think should be changed - it says "Consequently, UAs MUST
use the binary transfer encoding for binary payloads in SIP."
I actually believe that the binary transfer encoding is the right choice
for all payloads regardless of if they are binary or not. (It's not like
you are going to base64 encode the some ascii body). All binary means is
the bits will get transfered without being molested - which is alway
true for SIP since all the body handling is 8 bit safe.
So the change I would suggest would be to simply change "for binary
payloads" to "for payloads". I think we had consensus on this in a HUM
in a WG meeting back in 2004. A more detailed explanation of why think
this is in
http://www.softarmor.com/wgdb/docs/draft-jennings-sip-mime-02.txt
Cullen <with my individual contributor hat on>
On Jun 25, 2008, at 9:06 AM, Dean Willis wrote:
I'm pleased to announce a working group last call for the "Body
Handling" draft:
http://www.ietf.org/internet-drafts/draft-ietf-sip-body-handling-02.txt
This draft is intended for the Standards Track.
The only minor issue I'm aware of is an outdated reference that should
have no impact on the review:
== Outdated reference: A later version (-08) exists of
draft-ietf-mmusic-file-transfer-mech-06
Please review the draft carefully and post your comments back to the
list and author.
I'd like to conclude this WGLC period by July 11, 2008.
Ok everybody, get busy reviewing!
--
Dean
_______________________________________________
Sip mailing list https://www.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
_______________________________________________
Sip mailing list https://www.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