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

Maria Cruz Bartolome <maria.cruz.bartolome@ericsson.com> Fri, 21 February 2014 09:23 UTC

Return-Path: <maria.cruz.bartolome@ericsson.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 349DD1A04F8 for <dime@ietfa.amsl.com>; Fri, 21 Feb 2014 01:23:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 b9w_Qxu-IdDo for <dime@ietfa.amsl.com>; Fri, 21 Feb 2014 01:23:33 -0800 (PST)
Received: from sesbmg20.ericsson.net (sesbmg20.ericsson.net [193.180.251.56]) by ietfa.amsl.com (Postfix) with ESMTP id AD68F1A01B0 for <dime@ietf.org>; Fri, 21 Feb 2014 01:23:32 -0800 (PST)
X-AuditID: c1b4fb38-b7f418e000001099-42-53071b1047ba
Received: from ESESSHC007.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg20.ericsson.net (Symantec Mail Security) with SMTP id F3.C0.04249.01B17035; Fri, 21 Feb 2014 10:23:28 +0100 (CET)
Received: from ESESSMB101.ericsson.se ([169.254.1.28]) by ESESSHC007.ericsson.se ([153.88.183.39]) with mapi id 14.02.0387.000; Fri, 21 Feb 2014 10:23:27 +0100
From: Maria Cruz Bartolome <maria.cruz.bartolome@ericsson.com>
To: "dime@ietf.org" <dime@ietf.org>
Thread-Topic: [Dime] #51: OC-Supported-Features in requests - conclusions
Thread-Index: AQHPLuX68aES9cpBlkeq6x7MGvA5R5q/boKg
Date: Fri, 21 Feb 2014 09:23:26 +0000
Message-ID: <087A34937E64E74E848732CFF8354B920978409B@ESESSMB101.ericsson.se>
References: <087A34937E64E74E848732CFF8354B9209783FFD@ESESSMB101.ericsson.se> <5BCBA1FC2B7F0B4C9D935572D9000668151B4120@DEMUMBX014.nsn-intra.net>
In-Reply-To: <5BCBA1FC2B7F0B4C9D935572D9000668151B4120@DEMUMBX014.nsn-intra.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [153.88.183.150]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrGLMWRmVeSWpSXmKPExsUyM+Jvja6ANHuwQds/UYu5vSvYHBg9liz5 yRTAGMVlk5Kak1mWWqRvl8CVsebMXcaCubwVdzsvMDcw/uDqYuTkkBAwkfh1op8dwhaTuHBv PVsXIxeHkMARRomexdcYIZzFjBJHdnxnBaliE7CTuHT6BVMXIweHiICyxOlfDiCmsICnxKs1 YHNEBLwkJi24yQxhG0lsOz0JzGYRUJXoWXKUBcTmFfCVePf4JtT4yYwSe3bcZAWZwykQIHFp JS9IDSPQPd9PrWECsZkFxCVuPZnPBHGngMSSPeeZIWxRiZeP/7FC2EoSK7ZfYoSo15FYsPsT G4StLbFs4WtmiL2CEidnPmGZwCg6C8nYWUhaZiFpmYWkZQEjyypGjuLU4qTcdCODTYzAsD+4 5bfFDsbLf20OMUpzsCiJ83586xwkJJCeWJKanZpakFoUX1Sak1p8iJGJg1OqgZHxw6U1W+vF 368/z31ca6paZMreM5MXvk38unnLof733sWiYfc6NE9eEV0r0ad7bLHQldyquncb3xnUTZpa 8tPG9+/cIt2NCr2ne66kCCkn3LF9eCm03+z/vA+Xr3MeZO4JmTPz25/4jxd+dJe80zD4oN5S wtzwlnXSj6ftM+4EC3iJzV95qDxfiaU4I9FQi7moOBEAcgRADkkCAAA=
Archived-At: http://mailarchive.ietf.org/arch/msg/dime/50gIqhs_aloOrB4_-ViCyVQ8ozc
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 09:23:35 -0000

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