IETF Logo Mail Archive

Re: [dispatch] Fwd: sip ue-addr contact hdr parameter

Paul Kyzivat <pkyzivat@alum.mit.edu> Wed, 02 October 2019 18:56 UTC

Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D6AE21200B7 for <dispatch@ietfa.amsl.com>; Wed, 2 Oct 2019 11:56:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2pFAAfz3Z__n for <dispatch@ietfa.amsl.com>; Wed, 2 Oct 2019 11:56:19 -0700 (PDT)
Received: from outgoing-alum.mit.edu (outgoing-alum.mit.edu [18.7.68.33]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D72A6120052 for <dispatch@ietf.org>; Wed, 2 Oct 2019 11:56:18 -0700 (PDT)
Received: from Kokiri.localdomain (c-24-62-227-142.hsd1.ma.comcast.net [24.62.227.142]) (authenticated bits=0) (User authenticated as pkyzivat@ALUM.MIT.EDU) by outgoing-alum.mit.edu (8.14.7/8.12.4) with ESMTP id x92IuFiE012994 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 2 Oct 2019 14:56:16 -0400
To: ranjitkav12@gmail.com
References: <CAFXT-puSggAmTDCoeK7=A2aJsdGZAp-NtztXk_hh==OnjpjEzQ@mail.gmail.com> <CAFXT-ptARjgFSFnKyqfaKUDX-=3+01sWm9uEyWcEL0xJP1Q+-Q@mail.gmail.com> <HE1PR07MB3161E516064384192072173E939C0@HE1PR07MB3161.eurprd07.prod.outlook.com>
Cc: dispatch@ietf.org
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <4a0c083e-b5c7-4a68-7675-4591b679d68c@alum.mit.edu>
Date: Wed, 02 Oct 2019 14:56:15 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:60.0) Gecko/20100101 Thunderbird/60.9.0
MIME-Version: 1.0
In-Reply-To: <HE1PR07MB3161E516064384192072173E939C0@HE1PR07MB3161.eurprd07.prod.outlook.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/JkflLLiFjeixRaRQiT6k9LSMW14>
Subject: Re: [dispatch] Fwd: sip ue-addr contact hdr parameter
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Oct 2019 18:56:22 -0000

On 10/2/19 2:37 PM, Christer Holmberg wrote:
> Hi,
> 
> This question probably belongs to SIPCORE.

A more appropriate place would be sip-implementors@lists.cs.columbia.edu.

> …and, what is ue-addr parameter?

AFAIK it isn't a term that appears in ietf sip documents.
Given the use of "ue" I guess perhaps this may be a question about 3gpp.

	Thanks,
	Paul

> Regards,
> 
> Christer
> 
> *Lähettäjä:*dispatch <dispatch-bounces@ietf.org> *Puolesta *Ranjit Avasarala
> *Lähetetty:* keskiviikko 2. lokakuuta 2019 20.48
> *Vastaanottaja:* dispatch@ietf.org
> *Aihe:* [dispatch] Fwd: sip ue-addr contact hdr parameter
> 
> Hello all
> 
> I am looking for an I-D or RFC that describes the syntax and behaviour 
> of proxies receiving ue-addr parameter in SIP INVITE and when they do 
> and do not forward it further
> 
> Thank you
> 
> Ranjit
> 
> 
> _______________________________________________
> dispatch mailing list
> dispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/dispatch
>

v2.23.0 | Report a Bug | By Email