IETF Logo Mail Archive

Re: [dispatch] New draft: draft-holmberg-dispatch-received-realm-00

"Dawes, Peter, Vodafone Group" <Peter.Dawes@vodafone.com> Wed, 10 June 2015 13:06 UTC

Return-Path: <Peter.Dawes@vodafone.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0CCC61A1F73 for <dispatch@ietfa.amsl.com>; Wed, 10 Jun 2015 06:06:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.801
X-Spam-Level:
X-Spam-Status: No, score=0.801 tagged_above=-999 required=5 tests=[BAYES_50=0.8, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001] autolearn=ham
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 7VwsjTOGZAdI for <dispatch@ietfa.amsl.com>; Wed, 10 Jun 2015 06:06:32 -0700 (PDT)
Received: from mail1.bemta5.messagelabs.com (mail1.bemta5.messagelabs.com [195.245.231.141]) (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 BAD0A1A1C04 for <dispatch@ietf.org>; Wed, 10 Jun 2015 06:06:31 -0700 (PDT)
Received: from [85.158.139.163] by server-5.bemta-5.messagelabs.com id 15/95-19215-65638755; Wed, 10 Jun 2015 13:06:30 +0000
X-Env-Sender: Peter.Dawes@vodafone.com
X-Msg-Ref: server-4.tower-188.messagelabs.com!1433941589!9024730!1
X-Originating-IP: [195.232.244.136]
X-StarScan-Received:
X-StarScan-Version: 6.13.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 10002 invoked from network); 10 Jun 2015 13:06:29 -0000
Received: from mailout04.vodafone.com (HELO mailout04.vodafone.com) (195.232.244.136) by server-4.tower-188.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 10 Jun 2015 13:06:29 -0000
Received: from mailint04.vodafone.com (mailint04.vodafone.com [195.232.244.201]) by mailout04.vodafone.com (Postfix) with ESMTP id 3m67qn3J2WznTX0; Wed, 10 Jun 2015 15:06:29 +0200 (CEST)
Received: from mailint04.vodafone.com (localhost [127.0.0.1]) by mailint04.vodafone.com (Postfix) with ESMTP id 3m67qn2HkLzfZMq; Wed, 10 Jun 2015 15:06:29 +0200 (CEST)
Received: from VOEXC06W.internal.vodafone.com (voexc06w.dc-ratingen.de [145.230.101.26]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mailint04.vodafone.com (Postfix) with ESMTPS id 3m67qn1n6YzfZMR; Wed, 10 Jun 2015 15:06:29 +0200 (CEST)
Received: from VOEXC09W.internal.vodafone.com (145.230.101.29) by VOEXC06W.internal.vodafone.com (145.230.101.26) with Microsoft SMTP Server (TLS) id 14.3.224.2; Wed, 10 Jun 2015 15:06:28 +0200
Received: from VOEXM31W.internal.vodafone.com ([169.254.7.90]) by VOEXC09W.internal.vodafone.com ([145.230.101.29]) with mapi id 14.03.0224.002; Wed, 10 Jun 2015 15:06:27 +0200
From: "Dawes, Peter, Vodafone Group" <Peter.Dawes@vodafone.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>, "dispatch@ietf.org" <dispatch@ietf.org>
Thread-Topic: New draft: draft-holmberg-dispatch-received-realm-00
Thread-Index: AdCiHwUUGsBUGXYYRyCmNYpBt1QlewBXgnVw
Date: Wed, 10 Jun 2015 13:06:26 +0000
Message-ID: <4A4F136CBD0E0D44AE1EDE36C4CD9D99AEEE2567@VOEXM31W.internal.vodafone.com>
References: <7594FB04B1934943A5C02806D1A2204B1D8AA730@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D8AA730@ESESSMB209.ericsson.se>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: multipart/alternative; boundary="_000_4A4F136CBD0E0D44AE1EDE36C4CD9D99AEEE2567VOEXM31Winterna_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/dispatch/OdOf9UHo7E56kZAtjXctbHVpEOE>
Subject: Re: [dispatch] New draft: draft-holmberg-dispatch-received-realm-00
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 10 Jun 2015 13:06:36 -0000

Hi Christer,
I agree that it is useful for a (transit) network to know which network a request arrived from, as this draft argues. But isn't this information to be in the Via header field already in the entry before the transit network? The draft mentions that inter-operator identifier cannot be used but I think the draft should expand on why a new header field parameter is needed.

Regards,
Peter

From: dispatch [mailto:dispatch-bounces@ietf.org] On Behalf Of Christer Holmberg
Sent: 08 June 2015 20:15
To: dispatch@ietf.org
Subject: [dispatch] New draft: draft-holmberg-dispatch-received-realm-00

Hi,

I've submitted a new draft to dispatch: draft-holmberg-dispatch-received-realm-00. The draft defines a new Via header field parameter, "received-realm", which network entry entities can insert in order to inform other entities in the network from which network the request was received.

Previous versions of the draft have been submitted to SIPCORE, but I was advised by the SIPCORE chairs to submit it to DISPATCH.

Compared to previous versions, there is a technical change: the entity which inserts a parameter also calculates a HMAC value, which is inserted together with the network value.

Regards,

Christer

v2.23.0 | Report a Bug | By Email