Re: [Dime] draft-ietf-dime-ovli-01 questions #1

<lionel.morand@orange.com> Mon, 02 December 2013 16:31 UTC

Return-Path: <lionel.morand@orange.com>
X-Original-To: dime@ietfa.amsl.com
Delivered-To: dime@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 314A31AC863 for <dime@ietfa.amsl.com>; Mon, 2 Dec 2013 08:31:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 VNvXm2TLpeBP for <dime@ietfa.amsl.com>; Mon, 2 Dec 2013 08:31:53 -0800 (PST)
Received: from relais-inet.francetelecom.com (relais-ias244.francetelecom.com [80.12.204.244]) by ietfa.amsl.com (Postfix) with ESMTP id 115221AC862 for <dime@ietf.org>; Mon, 2 Dec 2013 08:31:53 -0800 (PST)
Received: from omfeda06.si.francetelecom.fr (unknown [xx.xx.xx.199]) by omfeda09.si.francetelecom.fr (ESMTP service) with ESMTP id 8DFD0C01C7; Mon, 2 Dec 2013 17:31:50 +0100 (CET)
Received: from Exchangemail-eme1.itn.ftgroup (unknown [10.114.1.186]) by omfeda06.si.francetelecom.fr (ESMTP service) with ESMTP id 6BB9AC8056; Mon, 2 Dec 2013 17:31:50 +0100 (CET)
Received: from PEXCVZYM13.corporate.adroot.infra.ftgroup ([fe80::cc7e:e40b:42ef:164e]) by PEXCVZYH01.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.03.0158.001; Mon, 2 Dec 2013 17:31:50 +0100
From: <lionel.morand@orange.com>
To: Jouni Korhonen <jouni.nospam@gmail.com>, Steve Donovan <srdonovan@usdonovans.com>
Thread-Topic: [Dime] draft-ietf-dime-ovli-01 questions #1
Thread-Index: AQHO73UdaJz9GfnFkkGuDkGoBEK6cJpA+28AgAAbGAA=
Date: Mon, 2 Dec 2013 16:31:50 +0000
Message-ID: <3558_1386001910_529CB5F6_3558_6116_1_6B7134B31289DC4FAF731D844122B36E3110E6@PEXCVZYM13.corporate.adroot.infra.ftgroup>
References: <16E13E52-0DB9-4E72-964A-FE658536155B@gmail.com> <10629_1385971488_529C3F20_10629_5138_1_emlwd34vyt318xrd8i01xiee.1385971482719@email.android.com> <529CAA39.6050809@usdonovans.com> <C976FFBA-9E2F-463F-A099-7D53E5CCF234@gmail.com>
In-Reply-To: <C976FFBA-9E2F-463F-A099-7D53E5CCF234@gmail.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.197.38.3]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 6.0.3.2322014, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2013.12.2.94815
Cc: "dime@ietf.org" <dime@ietf.org>
Subject: Re: [Dime] draft-ietf-dime-ovli-01 questions #1
X-BeenThere: dime@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Diameter Maintanence and Extentions Working Group <dime.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dime>, <mailto:dime-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dime/>
List-Post: <mailto:dime@ietf.org>
List-Help: <mailto:dime-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dime>, <mailto:dime-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Dec 2013 16:31:55 -0000

RFC5729 is another example. Maybe can we be more generic saying that enhanced routing decisions can be performed at the application level based on specific info e.g. NAI and add some examples.

Lionel

-----Message d'origine-----
De : DiME [mailto:dime-bounces@ietf.org] De la part de Jouni Korhonen
Envoyé : lundi 2 décembre 2013 16:46
À : Steve Donovan
Cc : dime@ietf.org
Objet : Re: [Dime] draft-ietf-dime-ovli-01 questions #1


Ok. I'll put references to PCC. Would NAI based "source routing"
qualify here as an example i.e. RFC5729?

- Jouni

On Dec 2, 2013, at 5:41 PM, Steve Donovan <srdonovan@usdonovans.com>; wrote:

> The PCC architecture, where agents route based on pre-existing bindings is another example.
> 
> Steve
> On 12/2/13 2:04 AM, lionel.morand@orange.com wrote:
>> It was my understanding.
>> 
>> Envoyé depuis mon Sony Xperia SP d'Orange
>> 
>> Jouni Korhonen 
>> <jounikor@gmail.com>;
>>  a écrit :
>> 
>> 
>> Hi,
>> 
>> In Section 2 on Diameter routing it says:
>> 
>>       defined in [RFC6733].  Application level routing specifications
>>       that expand on [RFC6733] also exist.
>> 
>> What does this "expand" actually refer to? RFC5729? RFC7075?
>> 
>> - Jouni
>> _______________________________________________
>> DiME mailing list
>> 
>> DiME@ietf.org
>> https://www.ietf.org/mailman/listinfo/dime
>> 
>> 
>> _________________________________________________________________________________________________________________________
>> 
>> Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
>> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
>> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
>> Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
>> 
>> This message and its attachments may contain confidential or privileged information that may be protected by law;
>> they should not be distributed, used or copied without authorisation.
>> If you have received this email in error, please notify the sender and delete this message and its attachments.
>> As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
>> Thank you.
>> 
>> _______________________________________________
>> DiME mailing list
>> 
>> DiME@ietf.org
>> https://www.ietf.org/mailman/listinfo/dime
>> 
>> 
>> 
> 
> _______________________________________________
> DiME mailing list
> DiME@ietf.org
> https://www.ietf.org/mailman/listinfo/dime

_______________________________________________
DiME mailing list
DiME@ietf.org
https://www.ietf.org/mailman/listinfo/dime

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.