Verifying Software Compatibility; Supported Software Versions; Authenticating With The Junos Xml Protocol Server; Table 6: Junos Xml Protocol Version 1.0 Pi And Opening Tag - Juniper JUNOS OS 10.3 - XML MANAGEMENT PROTOCOL GUIDE 6-30-2010 Manual

Authenticating with the Junos XML Protocol Server

Copyright © 2010, Juniper Networks, Inc.

Verifying Software Compatibility

Exchanging <?xml?> and <junoscript>
Junos XML protocol server to determine if they are running different versions of the
software used during a Junos XML protocol session. Different versions are sometimes
incompatible, and by Junos XML protocol convention the party running the later version
of software determines how to handle any incompatibility. For fully automated
performance, include code in the client application that determines if its version of
software is later than that of the Junos XML protocol server. Decide which of the following
options is appropriate when the application's version is more recent, and implement the
corresponding response:
Ignore differences in Junos version, and do not alter the client application's behavior
to accommodate the Junos XML protocol server. A difference in Junos versions does
not necessarily make the server and client incompatible, so this is often a valid approach.
Alter standard behavior to be compatible with the Junos XML protocol server. If the
client application is running a later version of the Junos OS, for example, it can choose
to emit only tag elements that represent the software features available in the Junos
XML protocol server's version of the Junos OS.
End the Junos XML protocol session and terminate the connection. This is appropriate
if you decide that it is not practical to accommodate the Junos XML protocol server's
version of software. For instructions, see "Ending a Junos XML Protocol Session and
Closing the Connection" on page 55.

Supported Software Versions

Table 6 on page 43 specifies the PI or opening tag and attribute used to convey version
information during Junos XML protocol session initialization in version 1.0 of the Junos
XML management protocol.

Table 6: Junos XML Protocol version 1.0 PI and Opening Tag

Software and Versions
XML 1.0
ANSI-standardized 7-bit ASCII
character set
Junos XML protocol 1.0
Junos OS Release
A client application that uses the clear-text or SSL protocol must now authenticate with
the Junos XML protocol server. (Applications that use the SSH or Telnet protocol use
the protocol's built-in authentication mechanism before emitting initialization tag
elements, as described in "Connecting to the Junos XML Protocol Server" on page 37.)
Chapter 3: Controlling the Junos XML Management Protocol Session
tag elements enables a client application and the
PI or Tag Attribute
<?xml?> version="1.0"
<?xml?> encoding="us-ascii"
<junoscript> version="1.0"
<junoscript> release="m.nZb"
For example:
release="10.3R1"
43