[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Sip] Comments on draft-ietf-sip-body-handling-02
From: Eric Burger <eburger at standardstrack.com>
In the e-mail world, the ;handling property was created for gateways
(B2BUA's), so the gateway could know whether dropping a body part,
because the connected network/protocol could not handle that body
part, would render the message useless. For example, if I am using an
old version of Outlook, and I send you a Word file, the Word body part
is required for the relay, but the application/tnef (proprietary
Outlook stuff) is optional and the gateway can silently drop the part.
Ah! This is an interesting difference, as the concept is that the
handling property is "global", that is, if a part labeled "required"
is necessary for successful processing of the entire message. (As
opposed to the "local" concept, where it is only neccessary for the
successful processing of the containing multipart, whose processing
might not be necessary for processing the entire message.)
Of course, with one-level nesFrom sip-bounces at ietf.org Mon Oct 6 19:41:44 2008
Return-Path: <sip-bounces at ietf.org>
X-Original-To: sip-archive at optimus.ietf.org
Delivered-To: ietfarch-sip-archive at core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
by core3.amsl.com (Postfix) with ESMTP id 14B013A6B1B;
Mon, 6 Oct 2008 19:41:44 -0700 (PDT)
X-Original-To: sip at core3.amsl.com
Delivered-To: sip at core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
by core3.amsl.com (Postfix) with ESMTP id B66B63A6AD9
for <sip at core3.amsl.com>; Mon, 6 Oct 2008 19:41:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.564
X-Spam-Level:
X-Spam-Status: No, score=-3.564 tagged_above=-999 required=5 tests=[AWL=0.035,
BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 2yY0KzelMF7E for <sip at core3.amsl.com>;
Mon, 6 Oct 2008 19:41:42 -0700 (PDT)
Received: from TheWorld.com (pcls4.std.com [192.74.137.84])
by core3.amsl.com (Postfix) with ESMTP id D47CB3A699E
for <sip at ietf.org>; Mon, 6 Oct 2008 19:41:41 -0700 (PDT)
Received: from shell.TheWorld.com (IDENT:105 at shell01.TheWorld.com
[192.74.137.71])
by TheWorld.com (8.13.6/8.13.6) with ESMTP id m972gAvd018553
for <sip at ietf.org>; Mon, 6 Oct 2008 22:42:12 -0400
Received: from shell01.TheWorld.com (localhost.theworld.com [127.0.0.1])
by shell.TheWorld.com (8.13.6/8.12.8) with ESMTP id m972gAcI41636564
for <sip at ietf.org>; Mon, 6 Oct 2008 22:42:10 -0400 (EDT)
Received: (from worley at localhost)
by shell01.TheWorld.com (8.13.6/8.13.6/Submit) id m972g7vC41474703;
Mon, 6 Oct 2008 22:42:07 -0400 (EDT)
Date: Mon, 6 Oct 2008 22:42:07 -0400 (EDT)
Message-Id: <200810070242.m972g7vC41474703 at shell01.TheWorld.com>
To: sip at ietf.org
From: Dale.Worley at comcast.net
In-reply-to: <9FF7202C-55A0-4635-84AC-1D7A8154C541 at standardstrack.com>
(eburger at standardstrack.com)
References: <5D1A7985295922448D5550C94DE2918002196DCC at DEEXC1U01.de.lucent.com> <48898492.7010601 at ericsson.com> <5D1A7985295922448D5550C94DE2918002196FF7 at DEEXC1U01.de.lucent.com> <4889F09B.8050407 at cisco.com> <200809262108.m8QL8fpj34800452 at shell01.TheWorld.com> <48E0F79B.8090402 at cisco.com> <200809300309.m8U39jFX37113365 at shell01.TheWorld.com>
<9BCA68EB-2AF2-4F88-A595-B4CE1ED6475B at standardstrack.com>
<48E3AA84.6010808 at cisco.com>
<9FF7202C-55A0-4635-84AC-1D7A8154C541 at standardstrack.com>
Subject: Re: [Sip] Comments on draft-ietf-sip-body-handling-02
X-BeenThere: sip at 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 at ietf.org?subject=unsubscribe>
List-Post: <mailto:sip at ietf.org>
List-Help: <mailto:sip-request at ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
<mailto:sip-request at ietf.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces at ietf.org
Errors-To: sip-bounces at ietf.org
From: Eric Burger <eburger at standardstrack.com>
In the e-mail world, the ;handling property was created for gateways
(B2BUA's), so the gateway could know whether dropping a body part,
because the connected network/protocol could not handle that body
part, would render the message useless. For example, if I am using an
old version of Outlook, and I send you a Word file, the Word body part
is required for the relay, but the application/tnef (proprietary
Outlook stuff) is optional and the gateway can silently drop the part.
Ah! This is an interesting difference, as the concept is that the
handling property is "global", that is, if a part labeled "required"
is necessary for successful processing of the entire message. (As
opposed to the "local" concept, where it is only neccessary for the
successful processing of the containing multipart, whose processing
might not be necessary for processing the entire message.)
Of course, with one-level nesting, thting, the two are equivalent.
Dale
_______________________________________________
Sip mailing list https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors at cs.columbia.edu for questions on current sip
Use sipping at ietf.org for new developments on the application of sip
e two are equivalent.
Dale
_______________________________________________
Sip mailing list https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors at cs.columbia.edu for questions on current sip
Use sipping at ietf.org for new developments on the application of sip