Re: [Dime] Issue #23 - Proposed resolution

<lionel.morand@orange.com> Wed, 30 July 2014 16:35 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 D05CE1A01D0 for <dime@ietfa.amsl.com>; Wed, 30 Jul 2014 09:35:23 -0700 (PDT)
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 ATWLIm9VuUbW for <dime@ietfa.amsl.com>; Wed, 30 Jul 2014 09:35:20 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias244.francetelecom.com [80.12.204.244]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 54E881A0084 for <dime@ietf.org>; Wed, 30 Jul 2014 09:35:20 -0700 (PDT)
Received: from omfeda08.si.francetelecom.fr (unknown [xx.xx.xx.201]) by omfeda12.si.francetelecom.fr (ESMTP service) with ESMTP id 881D23B4121; Wed, 30 Jul 2014 18:35:18 +0200 (CEST)
Received: from Exchangemail-eme1.itn.ftgroup (unknown [10.114.1.186]) by omfeda08.si.francetelecom.fr (ESMTP service) with ESMTP id 6E7EE384078; Wed, 30 Jul 2014 18:35:18 +0200 (CEST)
Received: from PEXCVZYM13.corporate.adroot.infra.ftgroup ([fe80::cc7e:e40b:42ef:164e]) by PEXCVZYH01.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.03.0181.006; Wed, 30 Jul 2014 18:35:18 +0200
From: lionel.morand@orange.com
To: Steve Donovan <srdonovan@usdonovans.com>, "dime@ietf.org" <dime@ietf.org>
Thread-Topic: [Dime] Issue #23 - Proposed resolution
Thread-Index: AQHPq2Jx3rQsneshpEqvUXHZZd+3bZu4vTxA///x+gCAACHCYA==
Date: Wed, 30 Jul 2014 16:35:17 +0000
Message-ID: <20099_1406738118_53D91EC6_20099_19198_1_6B7134B31289DC4FAF731D844122B36E682AFE@PEXCVZYM13.corporate.adroot.infra.ftgroup>
References: <53D7F470.3090500@usdonovans.com> <4485_1406733875_53D90E33_4485_11209_1_6B7134B31289DC4FAF731D844122B36E6827AB@PEXCVZYM13.corporate.adroot.infra.ftgroup> <53D91DF2.5070409@usdonovans.com>
In-Reply-To: <53D91DF2.5070409@usdonovans.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.6]
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: 2014.7.30.103920
Archived-At: http://mailarchive.ietf.org/arch/msg/dime/aouPMnzJ11j-Wr8supflzc_KEjo
Subject: Re: [Dime] Issue #23 - Proposed resolution
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: Wed, 30 Jul 2014 16:35:24 -0000

You are right. I was speaking about the discussion on the two possible interpretations of "realm" that it closed now.


-----Message d'origine-----
De : Steve Donovan [mailto:srdonovan@usdonovans.com] 
Envoyé : mercredi 30 juillet 2014 18:32
À : MORAND Lionel IMT/OLN; dime@ietf.org
Objet : Re: [Dime] Issue #23 - Proposed resolution

Lionel,

I believe it is closed from a conceptual basis but text changes are 
required before it can be truly considered closed.  At least that is the 
process we have been following to date.

I will propose those text changes for review prior to closing the issue.

Steve

On 7/30/14, 10:24 AM, lionel.morand@orange.com wrote:
> Hi Steve,
>
> As said during the meeting, you can consider this issue as closed.
> So please take it into account when reviewing the draft.
>
> Regards,
>
> Lionel
>
> -----Message d'origine-----
> De : DiME [mailto:dime-bounces@ietf.org] De la part de Steve Donovan
> Envoyé : mardi 29 juillet 2014 21:22
> À : dime@ietf.org
> Objet : [Dime] Issue #23 - Proposed resolution
>
> Issue @23 points out that there are two interpretations of the realm
> overload report in the current text.  One implies that a realm report
> applies to all requests sent to the realm, the other implies that it
> only applies to requests sent to the realm that does not contain a
> destination-host AVP.
>
> I believe we have consensus to use the second definition.
>
> There was also a proposal, made by me, to change the name of the report
> to something like "realm-routed-request" to be more accurate in defining
> what the scope of the overload report.  I no longer think this is
> necessary and am happy with the "realm" name for the report.
>
> If we have agreement on the direction then I will identify the text that
> needs to be changed to remove the conflicting definitions of the report
> type.  I will send it to the list for review before incorporating it
> into the -04 version of the draft and closing the issue.
>
> Please let me know if there are issues with this proposal.
>
> Regards,
>
> Steve
>
> _______________________________________________
> 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.
>
>


_________________________________________________________________________________________________________________________

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.