IETF Logo Mail Archive

Re: [Dime] [dime] #65 (draft-ietf-dime-ovli): Definition of messages impacted by host overload report

"Wiehe, Ulrich (NSN - DE/Munich)" <ulrich.wiehe@nsn.com> Tue, 29 April 2014 07:24 UTC

Return-Path: <ulrich.wiehe@nsn.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 10D5C1A0746 for <dime@ietfa.amsl.com>; Tue, 29 Apr 2014 00:24:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level:
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_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 L7UYHSCbt5eI for <dime@ietfa.amsl.com>; Tue, 29 Apr 2014 00:24:56 -0700 (PDT)
Received: from demumfd002.nsn-inter.net (demumfd002.nsn-inter.net [93.183.12.31]) by ietfa.amsl.com (Postfix) with ESMTP id 762171A0317 for <dime@ietf.org>; Tue, 29 Apr 2014 00:24:56 -0700 (PDT)
Received: from demuprx017.emea.nsn-intra.net ([10.150.129.56]) by demumfd002.nsn-inter.net (8.14.3/8.14.3) with ESMTP id s3T7OsXE027288 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 29 Apr 2014 07:24:54 GMT
Received: from DEMUHTC002.nsn-intra.net ([10.159.42.33]) by demuprx017.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id s3T7Oq4J030252 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 29 Apr 2014 09:24:53 +0200
Received: from DEMUHTC014.nsn-intra.net (10.159.42.45) by DEMUHTC002.nsn-intra.net (10.159.42.33) with Microsoft SMTP Server (TLS) id 14.3.181.6; Tue, 29 Apr 2014 09:24:52 +0200
Received: from DEMUMBX014.nsn-intra.net ([169.254.14.33]) by DEMUHTC014.nsn-intra.net ([10.159.42.45]) with mapi id 14.03.0181.006; Tue, 29 Apr 2014 09:24:52 +0200
From: "Wiehe, Ulrich (NSN - DE/Munich)" <ulrich.wiehe@nsn.com>
To: ext Ben Campbell <ben@nostrum.com>, Steve Donovan <srdonovan@usdonovans.com>
Thread-Topic: [Dime] [dime] #65 (draft-ietf-dime-ovli): Definition of messages impacted by host overload report
Thread-Index: AQHPYxCUm+IwhSIzdUyOnK54gKkmWZsnXkwAgADO2lA=
Date: Tue, 29 Apr 2014 07:24:51 +0000
Message-ID: <5BCBA1FC2B7F0B4C9D935572D9000668151E3D6E@DEMUMBX014.nsn-intra.net>
References: <066.a99805710f0922547f49ff6eb5d6c0fa@trac.tools.ietf.org> <535E9F54.7010607@usdonovans.com> <DA0E4300-08EF-4DEB-BFC1-D2A3E40230EC@nostrum.com>
In-Reply-To: <DA0E4300-08EF-4DEB-BFC1-D2A3E40230EC@nostrum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.159.42.117]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-purgate-type: clean
X-purgate-Ad: Categorized by eleven eXpurgate (R) http://www.eleven.de
X-purgate: clean
X-purgate: This mail is considered clean (visit http://www.eleven.de for further information)
X-purgate-size: 1555
X-purgate-ID: 151667::1398756294-00001564-C0A80978/0/0
Archived-At: http://mailarchive.ietf.org/arch/msg/dime/hH3gu4P_mDbyGOugrH-jgQMmWg8
Cc: "dime@ietf.org" <dime@ietf.org>
Subject: Re: [Dime] [dime] #65 (draft-ietf-dime-ovli): Definition of messages impacted by host overload report
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: Tue, 29 Apr 2014 07:24:59 -0000

Steve,

I agree with the principle, however, with regard to e.g. issue #66, it may eventually not be the "value of the Origin-Host AVP of the received message that contained the OC-OLR AVP".

Ulrich

-----Original Message-----
From: DiME [mailto:dime-bounces@ietf.org] On Behalf Of ext Ben Campbell
Sent: Monday, April 28, 2014 10:47 PM
To: Steve Donovan
Cc: dime@ietf.org
Subject: Re: [Dime] [dime] #65 (draft-ietf-dime-ovli): Definition of messages impacted by host overload report


On Apr 28, 2014, at 1:35 PM, Steve Donovan <srdonovan@usdonovans.com> wrote:

> All,
> 
> I am planning to update the wording per the following minor adjustment to Lionel's suggested wording for second paragraph of the following.  
> 
> Let me know if there are any objections to closing this issue with the proposed wording.
> 
>       Either the Destination-Host AVP is present in the request and its value
>       matches the value of the Origin-Host AVP of the received message
>       that contained the OC-OLR AVP; or the Destination-Host is not present
>       in the request but the value of peer identity associated with the connection
>       used to send the request matches the value of the Origin-Host AVP of the
>       received message that contained the OC-OLR AVP. 
> Regards,
> 

s/"of peer identity"/"of the peer identity"

Otherwise WFM.

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

v2.23.0 | Report a Bug | By Email