Re: [Sip] New version of draft-ietf-sip-body-handling-01.txt

Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com> Tue, 20 May 2008 08:08 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 9CCC63A68C1; Tue, 20 May 2008 01:08:06 -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 5AEA43A6BC7 for <sip@core3.amsl.com>; Tue, 20 May 2008 01:07:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.505
X-Spam-Level:
X-Spam-Status: No, score=-5.505 tagged_above=-999 required=5 tests=[AWL=0.744, 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 SFepJZgwDFnC for <sip@core3.amsl.com>; Tue, 20 May 2008 01:06:55 -0700 (PDT)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60]) by core3.amsl.com (Postfix) with ESMTP id 1145128C1A9 for <sip@ietf.org>; Tue, 20 May 2008 01:06:47 -0700 (PDT)
Received: from mailgw3.ericsson.se (unknown [127.0.0.1]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id 48E6620F35; Tue, 20 May 2008 10:05:38 +0200 (CEST)
X-AuditID: c1b4fb3c-ae89cbb00000193b-1f-48328652a59b
Received: from esealmw129.eemea.ericsson.se (unknown [153.88.254.124]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id 2AE9720F31; Tue, 20 May 2008 10:05:38 +0200 (CEST)
Received: from esealmw129.eemea.ericsson.se ([153.88.254.177]) by esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Tue, 20 May 2008 10:05:37 +0200
Received: from [131.160.37.21] ([131.160.37.21]) by esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Tue, 20 May 2008 10:05:37 +0200
Message-ID: <48328651.3050409@ericsson.com>
Date: Tue, 20 May 2008 11:05:37 +0300
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Thunderbird 2.0.0.14 (Windows/20080421)
MIME-Version: 1.0
To: Paul Kyzivat <pkyzivat@cisco.com>
References: <47979565.2050700@ericsson.com> <47980C64.2070801@cisco.com>
In-Reply-To: <47980C64.2070801@cisco.com>
X-OriginalArrivalTime: 20 May 2008 08:05:37.0624 (UTC) FILETIME=[49AC5580:01C8BA50]
X-Brightmail-Tracker: AAAAAA==
Cc: sip <sip@ietf.org>
Subject: Re: [Sip] New version of draft-ietf-sip-body-handling-01.txt
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-Archive: <https://www.ietf.org/mailman/private/sip>
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-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Hi Paul,

with respect to sipfrag, it is true that somebody could generate a 
sipfrag with a body without including the header that referenced that 
body. However, I believe that should be clarified in a revision of the 
sipfrag spec, and not in this one. Therefore, I will consider it out of 
the scope of this document.

Thanks for the comments,

Cheers,

Gonzalo

Paul Kyzivat wrote:
> Gonzalo,
> 
> This is *much* improved! (Not that it was bad before.) It is very 
> straightforward and clear. I like it a lot.
> 
> I was only thinking about one use case that may, or may not, warrant 
> some special explanation - the use of sipfrag.
> 
> A sipfrag is allowed to contain any subset of initial lines, headers, 
> and body from a sip message. This could for instance lead to unsatisfied 
> references to body parts, or to body parts that were intended to be 
> referenced, but whose references have been elided. As a result it may 
> not be possible to properly process the body parts of a sipfrag.
> 
> I think this this is pretty much intended behavior and so it should be 
> ok to send such ill-constructed things. But it might be good, here or 
> somewhere else, to clarify the construction and usage of sipfrags - what 
> makes sense and what does not.
> 
>     Thanks,
>     Paul
> 
> Gonzalo Camarillo wrote:
>> Folks,
>>
>> I have put together a new version of the body handling draft:
>>
>> http://www.ietf.org/internet-drafts/draft-ietf-sip-body-handling-01.txt
>>
>> This version addresses all the comments we got in its APPS review, 
>> which included modifying the structure of the document. With respect 
>> to references to body parts, per the guidelines we got from the APPS 
>> people, the document now only allows forward references.
>>
>> Comments are welcome.
>>
>> Cheers,
>>
>> Gonzalo
>>
>>
>>
>> _______________________________________________
>> Sip mailing list  https://www1.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