IETF Logo Mail Archive

Re: [Dime] #51: OC-Supported-Features in requests - conclusions

"Askerup, Anders" <anders.askerup@hp.com> Fri, 21 February 2014 17:21 UTC

Return-Path: <anders.askerup@hp.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 E450C1A04C6 for <dime@ietfa.amsl.com>; Fri, 21 Feb 2014 09:21:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level:
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548] 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 o_FRkIjCBg27 for <dime@ietfa.amsl.com>; Fri, 21 Feb 2014 09:21:35 -0800 (PST)
Received: from g4t3427.houston.hp.com (g4t3427.houston.hp.com [15.201.208.55]) by ietfa.amsl.com (Postfix) with ESMTP id ECF0C1A047E for <dime@ietf.org>; Fri, 21 Feb 2014 09:21:34 -0800 (PST)
Received: from G9W0364.americas.hpqcorp.net (g9w0364.houston.hp.com [16.216.193.45]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by g4t3427.houston.hp.com (Postfix) with ESMTPS id F3AF33ED for <dime@ietf.org>; Fri, 21 Feb 2014 17:21:30 +0000 (UTC)
Received: from G9W3617.americas.hpqcorp.net (16.216.186.52) by G9W0364.americas.hpqcorp.net (16.216.193.45) with Microsoft SMTP Server (TLS) id 14.3.123.3; Fri, 21 Feb 2014 17:20:19 +0000
Received: from G9W0747.americas.hpqcorp.net ([169.254.4.56]) by G9W3617.americas.hpqcorp.net ([16.216.186.52]) with mapi id 14.03.0123.003; Fri, 21 Feb 2014 17:20:19 +0000
From: "Askerup, Anders" <anders.askerup@hp.com>
To: Maria Cruz Bartolome <maria.cruz.bartolome@ericsson.com>, "dime@ietf.org" <dime@ietf.org>
Thread-Topic: [Dime] #51: OC-Supported-Features in requests - conclusions
Thread-Index: AQHPLuX+sF59CaBstE+joJsbC6KYmZq/b1kAgACEbiA=
Date: Fri, 21 Feb 2014 17:20:19 +0000
Message-ID: <602542051F40544EB188D494F506C2494792FB28@G9W0747.americas.hpqcorp.net>
References: <087A34937E64E74E848732CFF8354B9209783FFD@ESESSMB101.ericsson.se> <5BCBA1FC2B7F0B4C9D935572D9000668151B4120@DEMUMBX014.nsn-intra.net> <087A34937E64E74E848732CFF8354B920978409B@ESESSMB101.ericsson.se>
In-Reply-To: <087A34937E64E74E848732CFF8354B920978409B@ESESSMB101.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [16.210.48.37]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/dime/ZKwjcElg-rSnVxJwGIFwHkxhLKU
Subject: Re: [Dime] #51: OC-Supported-Features in requests - conclusions
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: Fri, 21 Feb 2014 17:21:37 -0000

Is the intent that it covers both the reporting nodes and reacting nodes, i.e. both Client and Server supporting DOIC must include the OC-Supported-Features AVP if they support DOIC?

/Anders  

-----Original Message-----
From: DiME [mailto:dime-bounces@ietf.org] On Behalf Of Maria Cruz Bartolome
Sent: Friday, February 21, 2014 3:23 AM
To: dime@ietf.org
Subject: Re: [Dime] #51: OC-Supported-Features in requests - conclusions

Yes, sorry about this, this was my understanding as well but I provided a wrong rephrasing.
My understanding is the following conclusions is reached:

#51: OC-Supported-Features in requests

 Now:
 The OC-Supported-Features AVP SHOULD be included into every Diameter  message a DOIC  supporting node sends (and intends to use for DOIC purposes).
 
Proposal:
The OC-Supported-Features AVP MUST be included into every Diameter request message a DOIC supporting node sends.


-----Original Message-----
From: Wiehe, Ulrich (NSN - DE/Munich) [mailto:ulrich.wiehe@nsn.com] 
Sent: viernes, 21 de febrero de 2014 10:19
To: Maria Cruz Bartolome; dime@ietf.org
Subject: RE: [Dime] #51: OC-Supported-Features in requests - conclusions

I do not agree
I think the conclusion was to say:
The OC-Supported-Features AVP MUST be included into every Diameter request message a DOIC supporting node sends.

For OC-Supported-Features AVP in answer messages refer to issue #30.

Ulrich  

-----Original Message-----
From: DiME [mailto:dime-bounces@ietf.org] On Behalf Of ext Maria Cruz Bartolome
Sent: Friday, February 21, 2014 9:35 AM
To: dime@ietf.org
Subject: [Dime] #51: OC-Supported-Features in requests - conclusions

#51: OC-Supported-Features in requests
 
My understanding is the following conclusions is reached:

 Now:
 The OC-Supported-Features AVP SHOULD be included into every Diameter  message a DOIC  supporting node sends (and intends to use for DOIC purposes).
 
Proposal:
replace SHOULD by MUST

_______________________________________________
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

v2.23.0 | Report a Bug | By Email