Re: [sipcore] About RFC3911(Join header)'s potential error: //Join header in REFER?

Christer Holmberg <christer.holmberg@ericsson.com> Fri, 15 October 2010 12:52 UTC

Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: sipcore@core3.amsl.com
Delivered-To: sipcore@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0C2AE3A69A4 for <sipcore@core3.amsl.com>; Fri, 15 Oct 2010 05:52:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.029
X-Spam-Level:
X-Spam-Status: No, score=-6.029 tagged_above=-999 required=5 tests=[AWL=0.570, BAYES_00=-2.599, 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 BNxzXVP0zRj2 for <sipcore@core3.amsl.com>; Fri, 15 Oct 2010 05:52:07 -0700 (PDT)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by core3.amsl.com (Postfix) with ESMTP id 339C33A68F3 for <sipcore@ietf.org>; Fri, 15 Oct 2010 05:52:06 -0700 (PDT)
X-AuditID: c1b4fb3d-b7b26ae00000638e-c4-4cb84eb972f9
Received: from esessmw0184.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw10.se.ericsson.net (Symantec Mail Security) with SMTP id 9C.22.25486.9BE48BC4; Fri, 15 Oct 2010 14:53:13 +0200 (CEST)
Received: from esessmw0191.eemea.ericsson.se (153.88.115.84) by esessmw0184.eemea.ericsson.se (153.88.115.81) with Microsoft SMTP Server (TLS) id 8.2.234.1; Fri, 15 Oct 2010 14:53:09 +0200
Received: from ESESSCMS0356.eemea.ericsson.se ([169.254.1.175]) by esessmw0191.eemea.ericsson.se ([153.88.115.84]) with mapi; Fri, 15 Oct 2010 14:53:07 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Paul Kyzivat <pkyzivat@cisco.com>, "gao.yang2@zte.com.cn" <gao.yang2@zte.com.cn>
Date: Fri, 15 Oct 2010 14:53:06 +0200
Thread-Topic: [sipcore] About RFC3911(Join header)'s potential error: //Join header in REFER?
Thread-Index: ActsZ3OLMjOTL/vqQCSY2br7jVhCkwAAE7zw
Message-ID: <7F2072F1E0DE894DA4B517B93C6A058502E26192@ESESSCMS0356.eemea.ericsson.se>
References: <OF9F863F48.D4CFA448-ON482577BC.0054725C-482577BC.00561B29@zte.com.cn> <4CB84DE4.60707@cisco.com>
In-Reply-To: <4CB84DE4.60707@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAA==
Cc: "sipcore@ietf.org" <sipcore@ietf.org>
Subject: Re: [sipcore] About RFC3911(Join header)'s potential error: //Join header in REFER?
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sipcore>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Oct 2010 12:52:09 -0000

Hi,

I think such discussion would be good, and I would like to participate.

Regards,

Christer
 

> -----Original Message-----
> From: sipcore-bounces@ietf.org 
> [mailto:sipcore-bounces@ietf.org] On Behalf Of Paul Kyzivat
> Sent: 15. lokakuuta 2010 15:50
> To: gao.yang2@zte.com.cn
> Cc: sipcore@ietf.org
> Subject: Re: [sipcore] About RFC3911(Join header)'s potential 
> error: //Join header in REFER?
> 
> Gao,
> 
> I presume you will be attending the meeting in Beijing?
> 
> This might be a good topic for a hallway discussion.
> 
> 	Thanks,
> 	Paul
> 
> On 10/14/2010 11:38 AM, gao.yang2@zte.com.cn wrote:
> >
> > Paul,
> >
> >  > I don't have a good answer for that. Something that 
> comes to mind 
> > is for  > a copy of the resulting request to be sent to the 
> referring 
> > UA as part  > of the refer subscription. But it would be 
> difficult to 
> > make good use of  > that.
> >
> > I have the same feeling as you for it, though we have opposite 
> > understanding(I think the UAS should do *semantic* check and *may* 
> > have the right to choose the headers to be honored, while 
> you think it 
> > is just copy).
> >
> > But for the pure audio usage, the copy way is working. And 
> there's no 
> > explicit use case to sustain more detailed 
> discussion/analysis. So, I 
> > think that this issue can be closed, at least for now.
> >
> > While, there's another issue about indication for streams in the 
> > REFER_with_embedded_Join request. Dale and Christer 
> suggested on it. 
> > And I will think it for details, and choose a proper WG to continue.
> >
> > Thanks,
> >
> > Gao
> >
> > --------------------------------------------------------
> > ZTE  Information  Security  Notice:  The  information  
> contained  in  this  mail  is  solely  property  of  the  
> sender's  organization.  This  mail  communication  is  
> confidential.  Recipients  named  above  are  obligated  to  
> maintain  secrecy  and  are  not  permitted  to  disclose  
> the  contents  of  this  communication  to  others.
> > This  email  and  any  files  transmitted  with  it  are  
> confidential  and  intended  solely  for  the  use  of  the  
> individual  or  entity  to  whom  they  are  addressed.  If  
> you  have  received  this  email  in  error  please  notify  
> the  originator  of  the  message.  Any  views  expressed  in 
>  this  message  are  those  of  the  individual  sender.
> > This  message  has  been  scanned  for  viruses  and  Spam  
> by  ZTE  Anti-Spam  system.
> >
> _______________________________________________
> sipcore mailing list
> sipcore@ietf.org
> https://www.ietf.org/mailman/listinfo/sipcore
>