Re: [Sip] WGLC for draft-ietf-sip-body-handling

Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com> Fri, 04 July 2008 06:59 UTC

Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 43B253A681C; Thu, 3 Jul 2008 23:59:53 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 413FF3A6AC9 for <sip@core3.amsl.com>; Thu, 3 Jul 2008 23:59:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.249
X-Spam-Level:
X-Spam-Status: No, score=-6.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lMnQXwrQSorb for <sip@core3.amsl.com>; Thu, 3 Jul 2008 23:59:50 -0700 (PDT)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62]) by core3.amsl.com (Postfix) with ESMTP id D3EC93A6AB7 for <sip@ietf.org>; Thu, 3 Jul 2008 23:59:49 -0700 (PDT)
Received: from mailgw4.ericsson.se (unknown [127.0.0.1]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id 4ECB522E95; Fri, 4 Jul 2008 08:59:56 +0200 (CEST)
X-AuditID: c1b4fb3e-ac194bb000004ec0-a0-486dca6c91c7
Received: from esealmw129.eemea.ericsson.se (unknown [153.88.254.124]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id 3F1EE22E90; Fri, 4 Jul 2008 08:59:56 +0200 (CEST)
Received: from esealmw127.eemea.ericsson.se ([153.88.254.171]) by esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Fri, 4 Jul 2008 09:00:37 +0200
Received: from [131.160.37.21] ([131.160.37.21]) by esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Fri, 4 Jul 2008 09:00:37 +0200
Message-ID: <486DCA95.8010304@ericsson.com>
Date: Fri, 04 Jul 2008 10:00:37 +0300
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Thunderbird 2.0.0.14 (Windows/20080421)
MIME-Version: 1.0
To: Cullen Jennings <fluffy@cisco.com>
References: <D990FC93-11C1-409E-8CBE-CACE851A5138@softarmor.com> <4A607918-B8B3-4B31-A623-7230375C513A@cisco.com>
In-Reply-To: <4A607918-B8B3-4B31-A623-7230375C513A@cisco.com>
X-OriginalArrivalTime: 04 Jul 2008 07:00:37.0763 (UTC) FILETIME=[A9C38530:01C8DDA3]
X-Brightmail-Tracker: AAAAAA==
Cc: SIP List <sip@ietf.org>
Subject: Re: [Sip] WGLC for draft-ietf-sip-body-handling
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

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 sip-implementors@cs.columbia.edu for questions on current sip
>> Use sipping@ietf.org 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 sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip