RE: [Sip] Question on RFC3840/3841

"Christer Holmberg" <christer.holmberg@ericsson.com> Thu, 10 January 2008 06:00 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 1JCqT5-0008SQ-VZ; Thu, 10 Jan 2008 01:00:43 -0500
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1JCqT4-0008SJ-HV for sip-confirm+ok@megatron.ietf.org; Thu, 10 Jan 2008 01:00:42 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JCqT4-0008S9-6U for sip@ietf.org; Thu, 10 Jan 2008 01:00:42 -0500
Received: from mailgw4.ericsson.se ([193.180.251.62]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JCqT3-00025k-HT for sip@ietf.org; Thu, 10 Jan 2008 01:00:42 -0500
Received: from mailgw4.ericsson.se (unknown [127.0.0.1]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id C6CA6211BA; Thu, 10 Jan 2008 07:00:26 +0100 (CET)
X-AuditID: c1b4fb3e-b06a2bb00000459d-25-4785b47a3a19
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id 98E7D2169A; Thu, 10 Jan 2008 07:00:26 +0100 (CET)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Thu, 10 Jan 2008 07:00:26 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Sip] Question on RFC3840/3841
Date: Thu, 10 Jan 2008 07:00:25 +0100
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF03FA6BD8@esealmw113.eemea.ericsson.se>
In-Reply-To: <004401c8533f$8d197500$bd4a6c6b@sisodomain.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Sip] Question on RFC3840/3841
Thread-Index: AchTPzYXn2dd8gh6QQaIfqe7ot0ndgADooYw
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>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Mahesh Anjanappa" <mahesha@samsung.com>, "Paul Kyzivat" <pkyzivat@cisco.com>
X-OriginalArrivalTime: 10 Jan 2008 06:00:26.0251 (UTC) FILETIME=[186E85B0:01C8534E]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 32b73d73e8047ed17386f9799119ce43
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

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