IETF Logo Mail Archive

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

"Dawes, Peter, Vodafone Group" <Peter.Dawes@vodafone.com> Thu, 11 June 2015 12:50 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 1B9BA1ACEC1 for <dispatch@ietfa.amsl.com>; Thu, 11 Jun 2015 05:50:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 xPhkjKTiJqHT for <dispatch@ietfa.amsl.com>; Thu, 11 Jun 2015 05:50:34 -0700 (PDT)
Received: from mail1.bemta5.messagelabs.com (mail1.bemta5.messagelabs.com [195.245.231.153]) (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 E17311ACEBF for <dispatch@ietf.org>; Thu, 11 Jun 2015 05:50:33 -0700 (PDT)
Received: from [85.158.136.83] by server-17.bemta-5.messagelabs.com id 46/4F-01139-81489755; Thu, 11 Jun 2015 12:50:32 +0000
X-Env-Sender: Peter.Dawes@vodafone.com
X-Msg-Ref: server-16.tower-36.messagelabs.com!1434027027!9172601!1
X-Originating-IP: [195.232.244.133]
X-StarScan-Received:
X-StarScan-Version: 6.13.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 9422 invoked from network); 11 Jun 2015 12:50:27 -0000
Received: from mailout01.vodafone.com (HELO mailout01.vodafone.com) (195.232.244.133) by server-16.tower-36.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 11 Jun 2015 12:50:27 -0000
Received: from mailint04.vodafone.com (mailint04.vodafone.com [195.232.244.201]) by mailout01.vodafone.com (Postfix) with ESMTP id 3m6lQq29lqz1yJj; Thu, 11 Jun 2015 14:50:27 +0200 (CEST)
Received: from mailint04.vodafone.com (localhost [127.0.0.1]) by mailint04.vodafone.com (Postfix) with ESMTP id 3m6lQT5kqbzfZnN; Thu, 11 Jun 2015 14:50:09 +0200 (CEST)
Received: from VOEXC03W.internal.vodafone.com (voexc03w.dc-ratingen.de [145.230.101.23]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mailint04.vodafone.com (Postfix) with ESMTPS id 3m6lQT57jWzfZlK; Thu, 11 Jun 2015 14:50:09 +0200 (CEST)
Received: from VOEXM31W.internal.vodafone.com ([169.254.7.90]) by VOEXC03W.internal.vodafone.com ([145.230.101.23]) with mapi id 14.03.0224.002; Thu, 11 Jun 2015 14:50:08 +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: AdCiHwUUGsBUGXYYRyCmNYpBt1QlewBXgnVwAATWnjAALOoNAA==
Date: Thu, 11 Jun 2015 12:50:08 +0000
Message-ID: <4A4F136CBD0E0D44AE1EDE36C4CD9D99AEEE2BFF@VOEXM31W.internal.vodafone.com>
References: <7594FB04B1934943A5C02806D1A2204B1D8AA730@ESESSMB209.ericsson.se> <4A4F136CBD0E0D44AE1EDE36C4CD9D99AEEE2567@VOEXM31W.internal.vodafone.com> <7594FB04B1934943A5C02806D1A2204B1D8B72D9@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D8B72D9@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_4A4F136CBD0E0D44AE1EDE36C4CD9D99AEEE2BFFVOEXM31Winterna_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/dispatch/gcbi69v6eV9xq4sV-3onaZHkOe8>
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: Thu, 11 Jun 2015 12:50:39 -0000

Thanks Christer,
I would like to see this draft progress, I think it describes functionality that is needed. I have other comments and questions on the text but they can be raised later.

Regards,
Peter

From: Christer Holmberg [mailto:christer.holmberg@ericsson.com]
Sent: 10 June 2015 16:20
To: Dawes, Peter, Vodafone Group; dispatch@ietf.org
Subject: RE: New draft: draft-holmberg-dispatch-received-realm-00

Hi Peter,

Thanks for your comments! See inline.

> 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.

Via headers may contain IP addresses, and they cannot always be used to identify the network. Also, the consumer of the information would have to scan through the Via headers, and figure out which belongs to the consumer network and which belongs to the adjacent network.

The purpose of the identifier is to have an explicit indicator, which prevents such scanning etc.

I try to explain that in the draft, but maybe more text is needed :)

Regards,

Christer


From: dispatch [mailto:dispatch-bounces@ietf.org] On Behalf Of Christer Holmberg
Sent: 08 June 2015 20:15
To: dispatch@ietf.org<mailto: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