aboutsummaryrefslogtreecommitdiffstats
path: root/diameter/dictionary.dtd
AgeCommit message (Collapse)AuthorFilesLines
2016-06-16Finish getting making the Diameter XML valid XML.Jeff Morriss1-1/+1
... Except for the fact that many AVP names start with "3GPP". Make the AVP names XML IDs again. Fix all the grouped AVPs that reference AVPs (by name) or vice-versa. This includes: * Fixing a bunch of typos (including type mismatches). * Commenting out a number of references to vendor AVPs for which we don't have the specs. * Adding a few missing AVPs. Change-Id: Ic2ddb50cc947877de9086be51f7813e8f9be02b4 Reviewed-on: https://code.wireshark.org/review/15973 Reviewed-by: Anders Broman <a.broman58@gmail.com>
2016-06-14Adjust the Diameter DTD to accept applications and vendors in any order.Jeff Morriss1-1/+1
Change-Id: I301a138b7f6db2d1a9ce1a20ebecf94e100bf831 Reviewed-on: https://code.wireshark.org/review/15887 Reviewed-by: Jeff Morriss <jeff.morriss.ws@gmail.com>
2015-05-09Eliminate a couple of empty Diameter grouped AVP lists.Jeff Morriss1-1/+1
Use Session-ID as a place holder for grouped AVPs that can hold any AVP and look up the contents of a couple grouped AVPs whose contents wasn't specified. Also, update the DTD to allow vendors to not add any AVPs. Change-Id: Id2852e31cecbcfaf64efb46918101b3a81ed5bdb Reviewed-on: https://code.wireshark.org/review/8355 Reviewed-by: Anders Broman <a.broman58@gmail.com>
2015-05-08Update the Diameter DTD to reflect the fact that vendors are no longer definedJeff Morriss1-4/+4
in base or applications. (IOW update the DTD to reflect I5119f0dc7f8e3bbf59e2207046a8bb0f42ab0ca1.) Change-Id: I459b3aac50ce4dabb552e674145d9097920e0a5d Reviewed-on: https://code.wireshark.org/review/8338 Reviewed-by: Anders Broman <a.broman58@gmail.com>
2010-08-20From Kirill A. Korinskiy via ↵Jeff Morriss1-2/+2
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5122: I try use diameters XML files as sources for my XSL transform by xslt and found some typos. I attach patch for fixing it. svn path=/trunk/; revision=33862
2005-09-29Move the Diameter dictionary files to a "diameter" subdirectory, alongGuy Harris1-0/+74
the lines of what's done for RADIUS. That keeps them together (and separate from other files), and makes the layout of the top-level source directory closer to the layout of the installation directory, so that if you run Ethereal or Tethereal from the top-level directory on Windows it'll pick up the Diameter dictionary files (if it supports loading them), and can do so on UN*X if we support a mechanism to let it find its control files in the directory in which the binary resides. Use the diameter_DATA, dtds_DATA, and radius_DATA macros in the EXTRA_DIST macro, so you only have to change the lists of Diameter, DTD, and RADIUS files in one place if you add or remove a file. svn path=/trunk/; revision=16050