forked from osmocom/wireshark
a275cd2495
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
23 lines
1.1 KiB
XML
23 lines
1.1 KiB
XML
<?xml version="1.0" encoding="UTF-8"?>
|
|
<application id="555" name="Sun Ping Application" uri="ftp://ftp.ietf.org/internet-drafts/draft-calhoun-diameter-sun-ping-02.txt">
|
|
<!-- *********************** Commands ***************************** -->
|
|
<!-- Sun Ping Extension -->
|
|
<command name="Ping" code="511" vendor-id="Sun"/>
|
|
<!-- ********************** End Commands ************************** -->
|
|
<!-- ************************ Sun Ping Extension AVPS ******************* -->
|
|
<avp name="Ping-Timestamp-Secs" code="1" vendor-id="Sun" mandatory="mustnot" vendor-bit="must">
|
|
<type type-name="Unsigned32"/>
|
|
</avp>
|
|
<avp name="Ping-Timestamp-Usecs" code="2" vendor-id="Sun" mandatory="mustnot" vendor-bit="must">
|
|
<type type-name="Unsigned32"/>
|
|
</avp>
|
|
<avp name="Ping-Timestamp" code="3" vendor-id="Sun" mandatory="mustnot" vendor-bit="must">
|
|
<grouped>
|
|
<gavp name="Ping-Timestamp-Secs"/>
|
|
<gavp name="Ping-Timestamp-Usecs"/>
|
|
</grouped>
|
|
</avp>
|
|
<!-- ********************** End Sun Ping Extension AVPS ***************** -->
|
|
<!-- ************************ Sun PING Extension AVPs ***************************-->
|
|
</application>
|