Re: [Sip] Question on RFC3840/3841

Mahesh Anjanappa <mahesha@samsung.com> Wed, 09 January 2008 17:15 UTC

Return-path: <sip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1JCeWz-0001C0-2N; Wed, 09 Jan 2008 12:15:57 -0500
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1JCeWx-00018p-Rh for sip-confirm+ok@megatron.ietf.org; Wed, 09 Jan 2008 12:15:55 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JCeWx-00018S-Gk for sip@ietf.org; Wed, 09 Jan 2008 12:15:55 -0500
Received: from [203.254.224.24] (helo=mailout1.samsung.com) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JCeWw-0003B8-H8 for sip@ietf.org; Wed, 09 Jan 2008 12:15:55 -0500
Received: from epmmp1 (mailout1.samsung.com [203.254.224.24]) by mailout1.samsung.com (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004)) with ESMTP id <0JUD00977ZY856@mailout1.samsung.com> for sip@ietf.org; Thu, 10 Jan 2008 02:15:44 +0900 (KST)
Received: from mahesha ([107.108.74.189]) by mmp1.samsung.com (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004)) with ESMTPA id <0JUD00I06ZY7DP@mmp1.samsung.com> for sip@ietf.org; Thu, 10 Jan 2008 02:15:44 +0900 (KST)
Date: Wed, 09 Jan 2008 22:48:26 +0530
From: Mahesh Anjanappa <mahesha@samsung.com>
Subject: Re: [Sip] Question on RFC3840/3841
To: Paul Kyzivat <pkyzivat@cisco.com>
Message-id: <040101c852e3$a627f730$bd4a6c6b@sisodomain.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
X-Mailer: Microsoft Outlook Express 6.00.2900.3138
Content-type: text/plain; reply-type=response; charset=iso-8859-1; format=flowed
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
References: <CA9998CD4A020D418654FCDEF4E707DF03F7A681@esealmw113.eemea.ericsson.se> <038901c852c3$d222b750$bd4a6c6b@sisodomain.com> <4784D96A.5010104@cisco.com>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Cc: sip@ietf.org, Christer Holmberg <christer.holmberg@ericsson.com>
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www1.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://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
Errors-To: sip-bounces@ietf.org

Thanks Paul.
So would it be right if i have a Contact Headers describing Duplex Audio & 
one-way Video Capabilities as follows?

    Contact:sip:alice@atlanta.com;
    Contact:sip:audio;duplex=full;
    Contact:sip:video;duplex=recieve-only;

NOTE: The Predicate(for above) for which i'm attempting is
& ( & (sip.audio) (sip.duplex=full) )
    (  & (sip.video) (sip.duplex=receive-only) )

regards
Mahesh

----- Original Message ----- 
From: "Paul Kyzivat" <pkyzivat@cisco.com>
To: "Mahesh Anjanappa" <mahesha@samsung.com>
Cc: "Christer Holmberg" <christer.holmberg@ericsson.com>om>; <sip@ietf.org>
Sent: Wednesday, January 09, 2008 7:55 PM
Subject: Re: [Sip] Question on RFC3840/3841


>
>
> Mahesh Anjanappa wrote:
>> hi
>> That is my understanding as well. But if that is the case then it should 
>> apply to Contact header as well
>> when describing Capabilities using Feature parameters in Contact Header.
>> But i'm not sure if it applies the same way. I had posted this question 
>> long ago but didnt get any comments on it.
>
> The rule forbidding multiple instances of a parameter applies to all 
> headers, so it applies to Contact.  E.g. the following is illegal:
>
> Contact:sip:alice@atlanta.com;methods="INVITE";methods="CANCEL"
>
> Paul 



_______________________________________________
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