[Dime] Enumerated Type

Carlos Fangmeier <carlos.fangmeier@gmail.com> Fri, 15 January 2016 12:27 UTC

Return-Path: <carlos.fangmeier@gmail.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 49F0B1B2C16 for <dime@ietfa.amsl.com>; Fri, 15 Jan 2016 04:27:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.6
X-Spam-Level:
X-Spam-Status: No, score=-0.6 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, 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 ghMt1DWhF6Zi for <dime@ietfa.amsl.com>; Fri, 15 Jan 2016 04:27:41 -0800 (PST)
Received: from mail-qk0-x22e.google.com (mail-qk0-x22e.google.com [IPv6:2607:f8b0:400d:c09::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 185951B2C15 for <dime@ietf.org>; Fri, 15 Jan 2016 04:27:41 -0800 (PST)
Received: by mail-qk0-x22e.google.com with SMTP id q19so261766388qke.3 for <dime@ietf.org>; Fri, 15 Jan 2016 04:27:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=ulXNiCCzQDERmRdHWYt/8gdqeM3sJTRuakpCYc+dyMY=; b=QeIUEqde9aSDJii5oER/DzMxT+eAxia+erQH9avhEs4NdPFhv48vD1GPVCjTmo30xa dEc3BFcI6xtJLuedF4OCq+LQhn9KuxzJ5gpeHE2uGxI1sSLKpm1o6X4QfMV7POhxaeQo Q2c0fBarZ9K2Qf/yZwbBXJ6FQGrryBfSoKopFsKMXuXGOsUhJUxLQAVWOizFKqICiWzq 2i/5eVCCCnIrW6g1pTMEdtEoH85c3MkwyqQmV8mCILI5HDcQc9m5iaCPQyFvAKlJtCkq O1vEbh3qzt1xEvQD5kYCowW5WwY75NyQvBFXU207pbGxkUdgpmQOGbzWH5Y9Eq8b2Nfn K8wA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to :content-type; bh=ulXNiCCzQDERmRdHWYt/8gdqeM3sJTRuakpCYc+dyMY=; b=bsQpg/GhkmZ7OzKiKeOlZKQC7xDT8ovNE0Y5ZjKG3GhaMRUSkJgI40El5OUBJiCycQ YdWevKF9V3PNrGv4jYrhpxJNX5Qf++jVuqERb2yzAoQB0uNa409+zDMfGrBp2B23RgQi 3WbyhL65+b7K/gzTPEAOC5tPqCf0uOoAN/+oXY1XCPXhE+FkFDStSggLmHP9iU+HKW53 WSWqo1Vak51GgNS2clWxPLLD4AmgbLw8ZFj3AzZIDYWzwPz8WMKN69pHhBwtUD5+5HGs 8TZqzftqw5LAcC/pHdyXeJ9QGQLykGdIMJsVkv+fHrf/9WXReGb/ud+qCozDIweDKBtS WGpA==
X-Gm-Message-State: ALoCoQkq5LbljXdVI0R19/nKkgfQ8J5xOUg9GnS2Y8fnAsBsD4QmC1k5wFbasnaXCZB7a13OX8XPUnbC6aY1f5XReXQE3eULGg==
MIME-Version: 1.0
X-Received: by 10.55.71.135 with SMTP id u129mr13028773qka.26.1452860860273; Fri, 15 Jan 2016 04:27:40 -0800 (PST)
Received: by 10.55.53.14 with HTTP; Fri, 15 Jan 2016 04:27:40 -0800 (PST)
Date: Fri, 15 Jan 2016 09:27:40 -0300
Message-ID: <CAKs0y4JEj4BALE6Qpt+uW=m5dSX2Ky3+LL2iQESqKK5VM3G_CA@mail.gmail.com>
From: Carlos Fangmeier <carlos.fangmeier@gmail.com>
To: dime@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <http://mailarchive.ietf.org/arch/msg/dime/5n_8nNNHExTsk8XUK_JgxL7CO3w>
X-Mailman-Approved-At: Fri, 15 Jan 2016 06:17:54 -0800
Subject: [Dime] Enumerated Type
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: <https://mailarchive.ietf.org/arch/browse/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, 15 Jan 2016 12:29:04 -0000

Hi everyone

In my work I implemented a diameter serializer/des-serializer from/to
a human readable json-like data structure. It is based on a dynamic
engine, capable of reading the message structure direct from the ABNF
command code specifictaion.
During the coding I realized that the diameter abnf grammar do not
consider a way to define the associated tags (human readable) for each
posbile value of a enumerated type. With a light modification to the
grammar it is possible to achieve it, and it gave the capability to my
serializer to validate and translate the value from/to the human
readable form.

Is this functionality beyond the scope of the diameter specification,
or is there a reason for not including it?

Thanks for your comments.


Carlos Fangmeier