Subject: Binary Thoughts (was RE: [Sip] SIP Draft Minutes)

From: "Eric Burger" <[email-masked]>
Date: Fri, 5 Mar 2004 14:48:29 -0500

To be clear, binary ONLY.  The SHOULD strength below, as I recall, was rejected.  Of course, one may always be liberal in what you accept, but from a protocol point of view, binary is the only way to talk.

-----Original Message-----
From: Dean Willis [mailto:[email-masked]]
Sent: Monday, March 01, 2004 8:09 PM
To: [email-masked]
Cc: [email-masked]; [email-masked]
Subject: [Sip] SIP Draft Minutes

[snip]

Culleng Jennings: Binary Encoding
Bodies use content transfer encoding. 3261 gives no guidance on what sort of encoding. Proposal to change it so say you SHOULD use binary, but need to be able to receive any.

Question: What about indirect content?
Discussion indicates that indirect content woul be contyrolled by the rules of whatever protocol and data format is being indirected to.

Question: Do we have base64 in SIP specs we need to expunge? 
Robert volunteered to help editors change examples to show binary encoding, using scripts he used for the torture test draft.

Question: Why couldn't this be on the list.
No discussion, just muttering.

Conclusion: Only binary, no requirement to receive non-binary. Will go into errata in a prominent way.
[snip]

_______________________________________________
Sip mailing list  https://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