Cisco CRS-1 - Carrier Routing System Router Administration Manual page 212

Managing AAR Files
Name
headerchar:
otherchar:
Note
The main section, which is terminated by an empty line:
•
•
The individual sections define various attributes for directories or files contained
in this AAR file. Not all files in the AAR file need to be listed in the manifest as
entries. The manifest file itself must not be listed. Each section must start with an
attribute with the name as "Name", and the value must be a relative path to the file
or directory.
If there are multiple individual sections for the same file entry, the attributes in
these sections are merged. If a certain attribute have different values in different
sections, the last one is recognized.
Attributes which are not understood are ignored. Such attributes may include
implementation specific information used by applications.
The following table describes the specification for any file that can be archived in
the AAR.
Name
manifest-file
main-section
version-info
version-number
main-attribute
individual-section
perentry-attribute
Cisco Customer Response Solutions Administration Guide, Release 4.1(1)
7-24
Chapter 7
To prevent corruption of files sent through e-mail, do not use "From" to
start a header.
Contains security and configuration information about the AAR file itself, as
well as the applications or extensions that this AAR file is defining.
Defines main attributes that apply to every individual manifest entry. No
attribute in this section can have its name equal to "Name".
Managing Prompts, Grammars, Documents, and Custom Files
Value
alphanum | - | _
Any UTF-8 character except NUL, CR and LF
Value
main-section newline *individual-section
version-info newline *main-attribute
Manifest-Version: version-number
digit+{.digit+}*
(any legitimate main attribute) newline
Name: value newline *perentry-attribute
(any legitimate perentry attribute) newline