Re: [Sip] Question on RFC3840/3841

Mahesh Anjanappa <mahesha@samsung.com> Thu, 10 January 2008 12:41 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 1JCwik-00077l-Uo; Thu, 10 Jan 2008 07:41:18 -0500
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1JCwij-00077g-Ip for sip-confirm+ok@megatron.ietf.org; Thu, 10 Jan 2008 07:41:17 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JCwij-00077Y-99 for sip@ietf.org; Thu, 10 Jan 2008 07:41:17 -0500
Received: from [203.254.224.24] (helo=mailout1.samsung.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JCwig-0005x9-Sj for sip@ietf.org; Thu, 10 Jan 2008 07:41:17 -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 <0JUF00A6KHVTBY@mailout1.samsung.com> for sip@ietf.org; Thu, 10 Jan 2008 21:40:41 +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 <0JUF00KYWHVSOV@mmp1.samsung.com> for sip@ietf.org; Thu, 10 Jan 2008 21:40:41 +0900 (KST)
Date: Thu, 10 Jan 2008 18:13:06 +0530
From: Mahesh Anjanappa <mahesha@samsung.com>
Subject: Re: [Sip] Question on RFC3840/3841
To: Christer Holmberg <christer.holmberg@ericsson.com>, Paul Kyzivat <pkyzivat@cisco.com>
Message-id: <006401c85386$59ec2370$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=original; 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> <040101c852e3$a627f730$bd4a6c6b@sisodomain.com> <004401c8533f$8d197500$bd4a6c6b@sisodomain.com> <CA9998CD4A020D418654FCDEF4E707DF03FA6BD8@esealmw113.eemea.ericsson.se>
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 093efd19b5f651b2707595638f6c4003
Cc: sip@ietf.org
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

Yes the ';' is a mistake. But i'm not sure if  each Contact should contain 
"alice@atlanta.com"
because the predicate that i'm trying to represent is as follows meanig to 
say
alice supports a communication which whose capability is Duplex Audio + One 
Way Video.
If each of the COntact contains alice@atlanta.com wouldnt it be interpreted 
as " alice
supports duplex audio and oneway video separatley and not both at the same 
time".
Actually i'm not quite sure how to represesnt the predicate in the Contact 
header correctly, hence
my Queries. It all stems from the statement which you too noted " There MUST 
only be one instance of any
feature tag in feature-param." in RFC 3840


Predicate:
------------
 & ( & (sip.audio) (sip.duplex=full) )
    (  & (sip.video) (sip.duplex=receive-only) )

regards
Mahesh
----- Original Message ----- 
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Mahesh Anjanappa" <mahesha@samsung.com>om>; "Paul Kyzivat" 
<pkyzivat@cisco.com>
Cc: <sip@ietf.org>
Sent: Thursday, January 10, 2008 11:30 AM
Subject: RE: [Sip] Question on RFC3840/3841



Shouldn't each Contact also contain "alice@atlanta.com"?

Also, why do you have ";" at the end of each Contact?

Regards,

Christer



> -----Original Message-----
> From: Mahesh Anjanappa [mailto:mahesha@samsung.com]
> Sent: 10. tammikuuta 2008 6:16
> To: Paul Kyzivat
> Cc: sip@ietf.org; Christer Holmberg
> Subject: Re: [Sip] Question on RFC3840/3841
>
> hi Paul,
> Sorry there is a mistake in Contact header i
> described.Following is what i wanted to:
> Contact:sip:alice@atlanta.com;
> Contact:audio;duplex=full;
> Contact:video;duplex=recieve-only;
>
> Thanks
> Mahesh
> ----- Original Message -----
> From: "Mahesh Anjanappa" <mahesha@samsung.com>
> To: "Paul Kyzivat" <pkyzivat@cisco.com>
> Cc: <sip@ietf.org>rg>; "Christer Holmberg"
> <christer.holmberg@ericsson.com>
> Sent: Wednesday, January 09, 2008 10:48 PM
> Subject: Re: [Sip] Question on RFC3840/3841
>
>
> > 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
>
> 



_______________________________________________
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