|author||Ulf Lamping <firstname.lastname@example.org>||2004-04-30 07:56:33 +0000|
|committer||Ulf Lamping <email@example.com>||2004-04-30 07:56:33 +0000|
updated to reflect the latest changes of exporting PDML in ethereal
svn path=/trunk/; revision=10741
Diffstat (limited to 'doc/README.xml-output')
1 files changed, 13 insertions, 14 deletions
diff --git a/doc/README.xml-output b/doc/README.xml-output
index 4d9f83d..bbf008c 100644
@@ -1,15 +1,14 @@
Protocol Dissection in XML Format
-$Id: README.xml-output,v 1.2 2003/12/09 05:56:30 gram Exp $
+$Id: README.xml-output,v 1.3 2004/04/30 07:56:33 ulfl Exp $
Copyright (c) 2003 by Gilbert Ramirez <firstname.lastname@example.org>
-Tethereal has the ability to print its protocol dissection in an
-XML format, by using the "-Tpdml" options. Similar functionality
-could be put into the "Print" dialog of Ethereal, but that work has
-not been done yet.
+Ethereal has the ability to export its protocol dissection in an
+XML format, tethereal has similar functionality by using the "-Tpdml"
-The XML that tethereal produces follows the Packet Details Markup
+The XML that ethereal produces follows the Packet Details Markup
Language (PDML) specified by the group at the Politecnico Di Torino
working on Analyzer. The specification can be found at:
@@ -18,8 +17,8 @@ http://analyzer.polito.it/30alpha/docs/dissectors/PDMLSpec.htm
A related XML format, the Packet Summary Markup Language (PSML), is
also defined by the Analyzer group to provide packet summary information.
The PSML format is not documented in a publicly-available HTML document,
-but its format is simple. Some day it may be added to tethereal so
-that "-Tpsml" would produce PSML.
+but its format is simple. Ethereal can export this format too. Some day it
+may be added to tethereal so that "-Tpsml" would produce PSML.
One wonders if the "-T" option should read "-Txml" instead of "-Tpdml"
(and in the future, "-Tpsml"), but if tethereal was required to produce
@@ -28,12 +27,12 @@ be ambiguous.
-The PDML that tethereal produces is known not to be loadable into Analyzer.
-It causes Analyzer to crash. As such, the PDML that tethereal produces
+The PDML that ethereal produces is known not to be loadable into Analyzer.
+It causes Analyzer to crash. As such, the PDML that ethereal produces
is be labled with a version number of "0", which means that the PDML does
not fully follow the PDML spec. Furthemore, a creator attribute in the
"<pdml>" tag gives the version number of [t]ethereal that produced the PDML.
-In that way, as the PDML produced by tethereal matures, but still does not
+In that way, as the PDML produced by ethereal matures, but still does not
meet the PDML spec, scripts can make intelligent decisions about how to
best parse the PDML, based on the "creator" attribute.
@@ -43,7 +42,7 @@ A packet will contain multiple protocols, denoted by the "<proto>" tag.
A protocol might contain one or more fields, denoted by the "<field>" tag.
A pseudo-protocol named "geninfo" is produced, as is required by the PDML
-spec, and printed as the first protocol after the opening "<packet>" tag.
+spec, and exported as the first protocol after the opening "<packet>" tag.
Its information comes from ethereal's "frame" protocol, which servers
the similar purpose of storing packet meta-data. Both "geninfo" and
"frame" protocols are provided in the PDML output.
@@ -94,8 +93,8 @@ a field with a field-name. Those appear in PDML as "<field>" tags with no
Many dissectors label the undissected payload of a protocol as belonging
to a "data" protocol, and the "data" protocol usually resided inside
that last protocol dissected. In the PDML, The "data" protocol becomes
-a "data" field, placed exactly where the "data" protocol is in tethereal's
-protocol tree. So, if tethereal would normally show:
+a "data" field, placed exactly where the "data" protocol is in ethereal's
+protocol tree. So, if ethereal would normally show: