[prev in list] [next in list] [prev in thread] [next in thread]
List: klyx
Subject: Bug#5936: marked as done (KLyX: footnote appears on wrong page) by Dirk Mueller <mueller@kde.org>
From: owner () bugs ! kde ! org (Stephan Kulow)
Date: 2001-03-13 12:03:12
[Download RAW message or body]
Your message dated Tue, 13 Mar 2001 12:47:48 +0100
with message-id <20010313124748.E28205@rotes20.wohnheim.uni-kl.de>
and subject line duplicate
has caused the attached bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I'm
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Stephan Kulow
(administrator, KDE bugs database)
Received: (at submit) by bugs.kde.org; 4 Jul 2000 17:02:05 +0000
From n7dr@uswest.net Tue Jul 4 19:02:05 2000
Received: from dnvrpop5.dnvr.uswest.net ([206.196.128.7]:35090 "HELO
dnvrpop5.dnvr.uswest.net") by master.kde.org with SMTP
id <S742575AbQGDRAY>; Tue, 4 Jul 2000 19:00:24 +0200
Received: (qmail 67440 invoked by alias); 4 Jul 2000 17:00:20 -0000
Delivered-To: fixup-submit@bugs.kde.org@fixme
Received: (qmail 67274 invoked by uid 0); 4 Jul 2000 17:00:14 -0000
Received: from rrdialup140.dnvr.uswest.net (HELO tux) (63.225.127.140)
by dnvrpop5.dnvr.uswest.net with SMTP; 4 Jul 2000 17:00:14 -0000
From: "D. R. Evans" <N7DR@arrl.net>
To: submit@bugs.kde.org
Date: Tue, 4 Jul 2000 11:00:15 -0600
MIME-Version: 1.0
Content-type: Multipart/Mixed; boundary=Message-Boundary-7522
Subject: KLyX: footnote appears on wrong page
Reply-to: N7DR@arrl.net
Priority: normal
X-mailer: Pegasus Mail for Win32 (v3.11)
Message-Id: <20000704170029Z742575-8110+174@master.kde.org>
Return-Path: <n7dr@uswest.net>
X-Orcpt: rfc822;submit@bugs.kde.org
Package: KLyX
Version: 0.10.0
I am running KLyX 0.10.0 (as included in the Mandrake 7.0 distribution).
This appears, as far as I can tell, to be the most recent version.
I have a KLyX file that is placing a footnote on the wrong page (the actual
footnote appears two pages later than it should). An earlier footnote
appears on the correct page.
Since the web page suggests that it's OK to include fairly lengthy files
with bug reports, I am attaching the KLyX file in question. The problem is
with the second footnote, which should appear on page 6.
(Looking at the file, it looks, to my limited understanding, as if there
may be a problem with the \begin_deeper and \end_deeper nesting; however,
moving the \end_deeper around by hand didn't solve the problem so I could
easily be wrong.)
Doc Evans
----------------------------------------------------------
D.R. Evans N7DR / G4AMJ N7DR@arrl.net
"Shadow" has been published (but don't blame me for the cover):
http://www.sff.net/people/N7DR/drevans.htp
----------------------------------------------------------
#This file was created by <N7DR> Tue Jul 4 10:11:37 2000
#LyX 0.12 (C) 1995-1998 Matthias Ettrich and the LyX Team
\lyxformat 2.15
\textclass article
\language default
\inputencoding latin1
\fontscheme default
\graphics default
\paperfontsize default
\spacing single
\papersize Default
\paperpackage a4
\use_geometry 0
\use_amsmath 0
\paperorientation portrait
\secnumdepth 3
\tocdepth 3
\paragraph_separation indent
\defskip medskip
\quotes_language english
\quotes_times 2
\papercolumns 1
\papersides 1
\paperpagestyle default
\layout Title
A Proposed Format for Electronic QSLs
\layout Author
Dr.
D.
R.
Evans, N7DR
\newline
N7DR@arrl.net
\layout Date
Draft 000702
\layout Section
Scope and Introduction
\layout Subsection
Purpose and Scope
\layout Standard
A QSL is a document that either:
\layout Enumerate
confirms contact between two amateur radio stations; or
\layout Enumerate
confirms that a listening station correctly identified a communication tha=
t
emanated from an amateur radio station.
\layout Standard
Historically, QSLs have been printed on cards (or, occasionally, other mat=
erial)
and have been exchanged between parties interested in obtaining a confirm=
ation
that an amateur radio communication has taken place.
\layout Standard
Typically, a traditional QSL is certified as valid by the inclusion of the
signature either of the transmitting party or of a third party with acces=
s
to the logs of the station that is certifying the QSL.
Traditional QSLs are regarded as difficult (but not impossible) to falsif=
y.
Many QSLs for particular stations contain unique elements (such as photog=
raphs)
that, as well as the signature, make it non-trivial to forge a confirmati=
on
without considerable risk of discovery.
However, it is still possible to forge traditional QSLs in many circumsta=
nces.
Two simple examples of methods of obtaining QSLs that act to certify comm=
unicat
ion that did not in fact take place are:
\layout Itemize
Bribery: Someone with access to blank QSLs (the owner of the station, the
QSL manager, or even the printer) may be paid to supply blank QSLs, which
may then be filled-out by an unscrupulous party (this frequently requires
forging a signature);
\layout Itemize
Altering legitimate QSLs: The information on an otherwise legitimate QSL
(band, mode, etc.) may be changed.
\layout Standard
As well as the relative ease with which QSLs may be forged, the fact that
they are traditionally printed on card makes them bulky and expensive to
transport.
In particular, many amateur radio enthusiasts are interested in pursuing
awards, application for which requires submission of the physical QSLs,
which may be costly and may also carry a non-zero possibility of loss of
the valued QSLs.
\layout Standard
This document defines a format for QSLs that may be created, examined and
exchanged electronically.
\shape italic
All other issues are explicitly beyond the scope of this document
\emph on
(however, see
\begin_inset LatexCommand \cite{5}
\end_inset
)
\emph toggle
.
\shape default
The format defined herein is designed so that electronic QSLs may be easi=
ly
created and authenticated but not easily forged.
They may be transported electronically through 7-bit communication channe=
ls.
They may also be
\begin_inset Quotes eld
\end_inset
batched
\begin_inset Quotes erd
\end_inset
for convenient transmission to awards-granting bodies.
\layout Standard
Note that the intent of an electronic QSL is not to replace the traditiona=
l
QSL.
Many QSLs are works of art, and most amateur radio operators keep a sampl=
e
of rare and/or attractive QSLs on the walls of the their shack.
An electronic QSL is designed simply to provide a simple (but admittedly
unaesthetic) mechanism to allow an amateur radio operator to submit proof=
s
of communication to an award-granting body, and for that body to confirm
that the communication did in fact occur as stated on the QSL.
We stress again, however, that this document defines only the format of
the electronic QSL and that all other considerations are deemed out of
scope.
\layout Subsection
Specification Language
\layout Standard
Throughout this document, a specific typographic convention is used to def=
ine
the significance of particular requirements.
This convention is that specific words rendered in the body of the text
in italic characters have meanings as follows:
\layout List
\labelwidthstring MMMMMMM
\emph on
must
\emph toggle
This word, or the adjective
\emph on
required,
\emph toggle
means that the item is an absolute requirement of this specification.
\layout List
\labelwidthstring MMMMMMM
\emph on
must
\protected_separator
not
\emph toggle
This phrase means that the item is an absolute prohibition of this specif=
icatio
n.
\layout List
\labelwidthstring MMMMMMM
\emph on
should
\emph toggle
This word, or the adjective
\emph on
recommended
\emph toggle
, means that there may exist valid reasons in particular circumstances to
ignore this item, but the full implications should be understood and the
case carefully weighed before choosing a different course.
\layout List
\labelwidthstring MMMMMMM
\emph on
should
\protected_separator
not
\emph toggle
This phrase means that there may exist valid reasons in particular circum=
stance
s when the listed behaviour is acceptable or even useful, but the full imp=
licati
ons should be understood and the case carefully weighed before implementin=
g
any behaviour described with this phrase.
\layout List
\labelwidthstring MMMMMMM
\emph on
may
\emph toggle
This word, or the adjective
\emph on
optional
\emph toggle
, means that this item is truly optional.
One conformant implementation may include the item and another conformant
implementation may omit the same item.
\layout Section
Format
\layout Standard
An electronic QSL contains a header, followed by a series of records, each
of which may be divided into fields, and concluded with a footer.
An electronic QSL may contain only ASCII printable characters and the con=
trol
characters 0x10 (Line Feed) and 0x13 (Carriage Return).
\layout Standard
An electronic QSL is formatted as a series of lines, separated by the newl=
ine
indicator.
The newline indicator may be either the pair of contiguous characters 0x1=
3
0x10, or the single character 0x10.
The newline indicator
\emph on
must
\emph toggle
be the same for every line in the QSL.
\layout Standard
An electronic QSL should not contain any lines longer than 76
\protected_separator
characters (excluding the newline indicator).
\layout Subsection
Header Format
\layout Standard
The header
\emph on
must
\emph toggle
consist of a line containing the ASCII encoded sequence
\begin_inset Quotes eld
\end_inset
QSL START: <format name> <format version> <options>
\begin_inset Quotes erd
\end_inset
\begin_float footnote
\layout Standard
Throughout this document, quotation marks are used to indicate ASCII-encod=
ed
strings.
The quotation marks are not to be considered part of the string.
\end_float
, where:
\layout Standard
<format name> is the name of the format in which the QSL is encoded.
For QSLs compliant with this specification, the format name
\emph on
must
\emph toggle
be encoded as the ASCII sequence
\begin_inset Quotes eld
\end_inset
N7DR
\begin_inset Quotes erd
\end_inset
.
\layout Standard
<format version> is the version identifier of the format in which the QSL
is encoded.
For QSLs compliant with this specification, the format version
\emph on
must
\emph toggle
be encoded as the ASCII sequence
\begin_inset Quotes eld
\end_inset
1.0
\begin_inset Quotes erd
\end_inset
.
\layout Standard
<options> is an ASCII-encoded string of options pertaining to the format
identified by <format name> and <format version>.
For QSLs compliant with this specification, the options
\emph on
must
\emph toggle
consist of an ASCII-encoded integer representing the total number of line=
s
contained in the QSL (
\emph on
i.e.
\emph toggle
, the sum total of the header, footer and all record lines).
\layout Subsection
Footer Format
\layout Standard
The footer
\emph on
must
\emph toggle
consist of a single line containing only the ASCII encoded sequence
\begin_inset Quotes eld
\end_inset
QSL END
\begin_inset Quotes erd
\end_inset
.
\layout Subsection
Record Format
\layout Standard
Each record
\emph on
must
\emph toggle
contain the name of the record, and
\emph on
must
\emph toggle
contain any mandatory values (here called
\begin_inset Quotes eld
\end_inset
value parameters
\begin_inset Quotes erd
\end_inset
) associated with that name.
The list of currently defined record names and their associated value par=
ameter
s is given in section
\begin_inset LatexCommand \ref{sec: Defined Record Names}
\end_inset
.
\layout Subsubsection
Name Format
\begin_inset LatexCommand \label{sec: Encoding}
\end_inset
\layout Standard
A record name
\emph on
must
\emph toggle
contain only the ASCII characters in the ranges (0x2D), (0x30, 0x39) and
(0x41, 0x5A).
These correspond to the hyphen, the digits 0...9, and the letters A...Z.
\layout Standard
A record name
\emph on
must
\emph toggle
be encoded on a single line, in the format
\begin_inset Quotes eld
\end_inset
<name> <lines> <encoding>
\begin_inset Quotes erd
\end_inset
, where:
\layout Standard
<name> is the ASCII encoded name of the record, followed by a colon.
\layout Standard
<lines> is an ASCII encoded number representing the total number of lines
contained in this record (including the current line).
\layout Standard
<encoding> is an optional paramater with one of the values
\begin_inset Quotes eld
\end_inset
CLEAR
\begin_inset Quotes erd
\end_inset
,
\begin_inset Quotes eld
\end_inset
BASE64
\begin_inset Quotes erd
\end_inset
or
\begin_inset Quotes eld
\end_inset
QP
\begin_inset Quotes erd
\end_inset
.
If <encoding> is absent, the encoding
\emph on
must
\emph toggle
be understood to take the value
\begin_inset Quotes eld
\end_inset
CLEAR
\begin_inset Quotes erd
\end_inset
.
\layout Standard
The encoding describes the format used to encode the value parameter of
the record, which
\emph on
must
\emph toggle
follow in the next (<lines>
\protected_separator
-
\protected_separator
1) lines.
The meaning of the possible values is as follows:
\layout List
\labelwidthstring 00.00.0000
CLEAR indicates that the value parameter is simple printable ASCII text.
\layout List
\labelwidthstring 00.00.0000
BASE64 indicates that the value parameter is encoded according to BASE64
encoding as defined in
\begin_inset LatexCommand \cite{6}
\end_inset
.
\layout List
\labelwidthstring 00.00.0000
QP indicates that the value parameter is encoded as quoted-printable text
as defined in
\begin_inset LatexCommand \cite{6}
\end_inset
.
\layout Standard
Any permitted encoding may be used to encode the value parameter of a reco=
rd,
except that if value parameter contains non-printable ASCII characters
the encoding CLEAR
\emph on
must not
\emph toggle
be used.
\layout Standard
Note that the definition of a particular record type may require a particu=
lar
method of encoding the data associated with that record.
It is important to recognize that such a requirement is independent of
the encoding used when formatting the QSL.
For example, the STN1 record as defined in section
\begin_inset LatexCommand \ref{sec: Defined Record Names}
\end_inset
must contain an ASCII-encoded callsign.
However, when the sequence of octets corresponding to the ASCII character=
s
of the callsign is inserted into a QSL, the octets may be encoded by any
of the permissible encodings defined in this section.
\layout Subsubsection
Parameter types
\layout Standard
Parameters are untyped.
However, the definition of a record with a particular name
\emph on
may
\emph toggle
place constraints on the possible values that may be associated with that
name (see section
\begin_inset LatexCommand \ref{sec: Defined Record Names}
\end_inset
).
\layout Section
Defined Record Names
\begin_inset LatexCommand \label{sec: Defined Record Names}
\end_inset
\layout Standard
This section lists all the record names defined by this specification, alo=
ng
with an indication of the parameters of each record and whether the recor=
d
is mandatory or optional.
An electronic QSL
\emph on
may
\emph toggle
contain records with names other than those defined in this section; howe=
ver,
all such record names
\emph on
must
\emph toggle
begin with the two-character ASCII sequence
\family typewriter
X-
\family default
.
\layout List
\labelwidthstring MMMMMMMMM
COMMENT An electronic QSL
\emph on
must
\emph toggle
contain a single COMMENT record, which
\emph on
must
\emph toggle
be the first record in the QSL.
The value parameter associated with a COMMENT may be of any length and
may contain octets with any value.
The ordinary purpose of the COMMENT record is to summarize in human-reada=
ble
form the other fields in the QSL.
However, the COMMENT record may be used for any purpose that the issuer
of the QSL desires.
\layout List
\labelwidthstring MMMMMMMMM
VERSION An electronic QSL
\emph on
must
\emph toggle
contain a single VERSION record, which
\emph on
must
\emph toggle
be the second record in the QSL.
The parameter value associated with the VERSION
\emph on
must
\emph toggle
be the ASCII string
\begin_inset Quotes eld
\end_inset
1.0
\begin_inset Quotes erd
\end_inset
.
\layout List
\labelwidthstring MMMMMMMMM
QSL-ID An electronic QSL
\emph on
may
\emph toggle
contain a single QSL-ID record.
The value parameter associated with a QSL-ID may be of any length and may
contain octets with any value.
The ordinary purpose of the QSL-ID record is to identify the QSL in some
manner that is useful to the issuer of the QSL.
However, the QSL-ID record may be used for any purpose that the issuer
of the QSL desires.
\layout List
\labelwidthstring MMMMMMMMM
STN1 An electronic QSL
\emph on
must
\emph toggle
contain a single STN1 record.
The parameter value of the STN1 record
\emph on
must
\emph toggle
contain the callsign of the station on whose behalf the QSL is issued,
encoded as ASCII characters.
\layout List
\labelwidthstring MMMMMMMMM
TO An electronic QSL
\emph on
must
\emph toggle
contain a single TO record.
The value parameter of the TO record
\emph on
must
\emph toggle
contain an identifer that corresponds to the entity for which the QSL is
issued, encoded as ASCII characters.
Normally, this is the callsign of the intended recipient.
\layout List
\labelwidthstring MMMMMMMMM
WKD An electronic QSL
\emph on
may
\emph toggle
contain a single WKD record.
The parameter value of the WKD record, if present,
\emph on
must
\emph toggle
contain the ASCII-encoded callsign of a station with whom the issuer cert=
ifies
contact to have taken place in accordance with the other records in the
QSL.
\layout List
\labelwidthstring MMMMMMMMM
AWARD-INFO An electronic QSL
\emph on
may
\emph toggle
contain any number of AWARD-INFO records (including zero).
An AWARD-INFO record is used to carry information pertaining to a particu=
lar
award.
The format of the value parameter
\emph on
must
\emph toggle
contain contiguous octets as follows:
\begin_deeper
\layout Enumerate
The name of the award.
This
\emph on
should
\emph toggle
be encoded in ASCII.
Although it
\emph on
may
\emph toggle
be encoded in a non-ASCII encoding it
\emph on
must not
\emph toggle
include octets with the value 0x13 or 0x10.
\layout Enumerate
A new line
\layout Enumerate
The information needed by the award, encoded in whatever manner the awardi=
ng
body has specified.
\end_deeper
\layout List
\labelwidthstring MMMMMMMMM
DATETIME An electronic QSL
\emph on
must
\emph toggle
contain a single DATETIME record.
The value parameter of a DATETIME record
\emph on
must
\emph toggle
contain thirteen ASCII octets in the form YYYYMMDDhhmm
\begin_inset Formula \( \alpha , \)
\end_inset
where YYYY is the year, MM the month, DD the day, hh the hour and mm the
minute of the contact.
Following this
\emph on
must
\emph toggle
be a single upper-case ASCII letter representing the time zone to which
the date and time refer.
The letter Z refers to UTC.
Other letters are as listed at
\begin_inset LatexCommand \cite{7}
\end_inset
.
\layout List
\labelwidthstring MMMMMMMMM
FREQUENCY An electronic QSL
\emph on
may
\emph toggle
contain a maximum of one FREQUENCY record.
If the QSL does not contain a BAND record, it
\emph on
must
\emph toggle
contain a single FREQUENCY record.
The value parameter of a FREQUENCY record
\emph on
must
\emph toggle
be encoded as follows:
\begin_deeper
\layout Enumerate
The
\emph on
Syst=E8me International
\emph toggle
abbreviation for the unit of measurement, encoded as ASCII characters.
\begin_float footnote
\end_deeper
\layout Standard
Note that
\family typewriter
MHz
\family default
is the correct abbreviation for megahertz;
\family typewriter
mHz
\family default
is the abbreviation for millihertz.
\end_float
See
\begin_inset LatexCommand \cite{4}
\end_inset
for more details.
\begin_deeper
\layout Enumerate
A space.
\layout Enumerate
The actual value of the frequency, encoded as ASCII characters.
The frequency
\emph on
must
\emph toggle
contain only digits, except that a single non-digit character representin=
g
either a comma (0x2C) or a full stop (0x2E)
\emph on
may
\emph toggle
be present.
If a non-digit character is present, the character immediately preceding
the non-digit character must be taken to represent the
\begin_inset Quotes eld
\end_inset
units
\begin_inset Quotes erd
\end_inset
value of the frequency in the specified SI units.
\end_deeper
\layout List
\labelwidthstring MMMMMMMMM
BAND An electronic QSL
\emph on
may
\emph toggle
contain a maximum of one BAND records.
If the QSL does not contain a FREQUENCY record, it
\emph on
must
\emph toggle
contain a single BAND record.
The value parameter of a BAND record
\emph on
must
\emph toggle
be encoded as follows:
\begin_deeper
\layout Enumerate
The
\emph on
Syst=E8me International
\emph toggle
abbreviation for the unit of measurement, encoded as ASCII characters.
See
\begin_inset LatexCommand \cite{5}
\end_inset
for more details.
\layout Enumerate
A space.
\layout Enumerate
The actual value of the band, encoded as ASCII characters.
The band must contain only digits.
\end_deeper
\layout List
\labelwidthstring MMMMMMMMM
TREPORT An electronic QSL
\emph on
may
\emph toggle
contain a maximum of one TREPORT records, which
\emph on
should
\emph toggle
correspond to the signal report transmitted by the QSLing station.
In the case that the QSL confirms a report from a receiving station, the
TREPORT, if present,
\emph on
should
\emph toggle
contain the signal report provided by the receiving station to the QSLing
station.
\layout List
\labelwidthstring MMMMMMMMM
RREPORT An electronic QSL
\emph on
may
\emph toggle
contain a maximum of one RREPORT records, which
\emph on
should
\emph toggle
correspond to the signal report received by the QSLing station from the
station identified in the WKD field.
\layout List
\labelwidthstring MMMMMMMMM
IMAGE An electronic QSL may contain a maximum of one IMAGE records.
The format of an image record must be as follows:
\begin_deeper
\layout Enumerate
The number of images contained in the QSL.
\layout Enumerate
A new line.
\layout Standard
For each image in the QSL, the QSL
\emph on
must
\emph toggle
contain:
\layout Enumerate
The number of lined occupied by the encoded image, including this line.
\layout Enumerate
A new line.
\layout Enumerate
The format of the image, which
\emph on
must
\emph toggle
be one of the following: JPG, LINK.
\layout Enumerate
A new line.
\layout Enumerate
The image.
If the image format is JPG, then the image
\emph on
must
\emph toggle
be BASE64 encoded.
If the image format is LINK, then this line
\emph on
must
\emph toggle
contain the complete URL of the image.
\end_deeper
\layout List
\labelwidthstring MMMMMMMMM
ISSUER An electronic QSL
\emph on
must
\emph toggle
contain a single ISSUER record.
The ISSUER record
\emph on
must
\emph toggle
identify the party resonsible for issuing the QSL.
\layout List
\labelwidthstring MMMMMMMMM
KEY-ID An electronic QSL
\emph on
may
\emph toggle
contain a single KEY-ID record.
If the QSL contains no CERTIFICATE record, then the QSL
\emph on
must
\emph toggle
contain a KEY-ID record.
If present, the KEY-ID record
\emph on
must
\emph toggle
contain the value of the public PGP key identifier (the so-called
\begin_inset Quotes eld
\end_inset
keyID
\begin_inset Quotes erd
\end_inset
) corresponding to the private PGP key used to sign the QSL.
The value parameter
\emph on
must
\emph toggle
be ASCII encoded.
\layout List
\labelwidthstring MMMMMMMMM
CERTIFICATE An electronic QSL
\emph on
may
\emph toggle
contain a single CERTIFICATE record.
If the QSL contains no KEY-ID record, then the QSL
\emph on
must
\emph toggle
contain a CERTIFICATE record.
If present, the CERTIFICATE
\emph on
must
\emph toggle
contain a valid digital certificate in X.509 format.
The certificate
\emph on
must
\emph toggle
contain the public key corresponding to the private key used to sign the
QSL.
The value parameter
\emph on
must
\emph toggle
be a BASE64 encoding of the underlying ASN.1.
\layout List
\labelwidthstring MMMMMMMMM
SIGNATURE An electronic QSL
\emph on
must
\emph toggle
contain a single SIGNATURE record.
The SIGNATURE record
\emph on
must
\emph toggle
contain a digital signature as follows:
\begin_deeper
\layout Enumerate
The private key used to sign the QSL
\emph on
must
\emph toggle
correspond to the public key identified by the KEY-ID record.
\layout Enumerate
The signature
\emph on
must
\emph toggle
be represented as a sequence of BASE64-encoded octets.
In other words, the digital signature is calculated; it is then converted
to BASE64 and inserted into the value parameter of the SIGNATURE record
(which is then further encoded by one of the mechanisms defined in sectio=
n
\begin_inset LatexCommand \ref{sec: Encoding}
\end_inset
).
\end_deeper
\layout List
\labelwidthstring MMMMMMMMM
VERIFIED-BY An electronic QSL
\emph on
may
\emph toggle
include any number of VERIFIED-BY records.
The purpose of a VERIFIED-BY record is to identify a third party that has
confirmed that the SIGNATURE on the QSL is valid.
The value parameter of a VERIFIED-BY record must contain the following
contigous entries:
\begin_deeper
\layout Enumerate
The name of the party that has verified the SIGNATURE.
\layout Enumerate
The keyID of the public key corresponding to the private key used by the
verifiying party to sign the verification.
\layout Enumerate
A digital signature from the verifying party.
\layout Standard
The actual value of the parameter must be formatted as follows:
\layout Enumerate
The identity of the verifying party, ASCII encoded.
\layout Enumerate
A new line.
\layout Enumerate
The value of the keyID, ASCII encoded.
\layout Enumerate
A new line.
\layout Enumerate
The digital signature, BASE64 encoded.
\end_deeper
\layout Section
Keys and Algorithms
\layout Standard
The key pair used to sign and authenticate an electronic QSL
\emph on
must
\emph toggle
be an RSA pair with length 1024 bits.
The algorithm used to sign the electronic QSL
\emph on
must
\emph toggle
be as follows:
\layout Enumerate
Concatenate all the records in the electronic QSL, in order.
This
\emph on
must not
\emph toggle
include a SIGNATURE record or a VERIFIED-BY record.
\layout Enumerate
Take the result of step 1 and calculate the SHA-1 hash.
\layout Enumerate
Take the result of step 2 and encrypt it with the private RSA key of the
ISSUER.
\layout Enumerate
This result is then converted to BASE64 and inserted into the value parame=
ter
of the SIGNATURE record.
\layout Standard
In order that the signature may be checked, the public RSA key correspondi=
ng
to the private RSA key that was used to sign the QSL
\emph on
must
\emph toggle
either be deposited on a globally-accessible PGP key server or present
in the CERTIFICATE record of the QSL.
If the key has been deposited on a server, the corresponding keyID
\emph on
must
\emph toggle
be included in the KEY-ID record of any QSLs signed by the corresponding
private key.
\layout Standard
A key pair used to verify an electronic QSL
\emph on
must
\emph toggle
be an RSA pair with length 1024 bits.
The algorithm used to sign the electronic QSL
\emph on
must
\emph toggle
be as follows:
\layout Enumerate
Concatenate all the records in the electronic QSL, in order.
This
\emph on
must not
\emph toggle
include a SIGNATURE record or a VERIFIED-BY record.
\layout Enumerate
Remove all 0x10 and 0x13 characters.
\layout Enumerate
Take the result of step 2 and calculate the SHA-1 hash.
\layout Enumerate
Take the result of step 3 and encrypt it with the private RSA key of the
verifying party.
\layout Enumerate
This result is then converted to BASE64 and inserted into the appropriate
position in the value parameter of the VERIFIED-BY record.
\layout Standard
In order that the signature may be checked, the public RSA key correspondi=
ng
to the private RSA key that was used to verify the QSL
\emph on
must
\emph toggle
be deposited on a globally-accessible PGP key server.
\layout Standard
Before any party adds a VERIFIED-BY record to an electronic QSL, that part=
y
\emph on
must
\emph toggle
validate the SIGNATURE record.
\layout Standard
Note that a party adding a VERIFIED-BY record to a QSL is not confirming
that the contents of the electronic QSL are accurate; it is confirming
that the contents have not been tampered with.
\layout Section
Batches
\layout Standard
One or more electronic QSLs may be aggregated into a batch.
A batch is a collection of electronic QSLs, all of which have been verifi=
ed
by a single party.
The batch is then digitally signed by the verifying party.
A batch of QSLs may be verified by an award-granting entity extremely qui=
ckly.
Providing that the entity trusts the signer of the batch, it need only
check the digital signature of the batch to confirm the authenticity of
all the electronic QSLs in the batch.
(If the entity does not trust the signer, it is still free to verify each
QSL individually.)
\layout Standard
All the QSLs in a batch
\emph on
must
\emph toggle
contain a VERIFIED-BY record identifying the party that signs the batch.
\layout Subsection
Batch Format
\layout Standard
A batch contains a header, followed by a series of QSLs, and concluded wit=
h
a footer.
A batch is formatted as a series of lines, separated by the newline indic=
ator.
The newline indicator may be either a pair of contiguous characters 0x13
0x10, or the single character 0x10.
The newline indicator
\emph on
must
\emph toggle
be the same for every line in the batch.
\layout Subsubsection
Header Format
\layout Standard
The header
\emph on
must
\emph toggle
consist of a line containing the ASCII encoded sequence
\begin_inset Quotes eld
\end_inset
BATCH START: <format name> <format version> <options>
\begin_inset Quotes erd
\end_inset
, where
\layout Standard
<format name> is the name of the format in which the batch is encoded.
For batchess compliant with this specification, the format name
\emph on
must
\emph toggle
be encoded as the ASCII sequence
\begin_inset Quotes eld
\end_inset
N7DR
\begin_inset Quotes erd
\end_inset
.
\layout Standard
<format version> is the version identifier of the format in which the batc=
h
is encoded.
For batches compliant with this specification, the format version
\emph on
must
\emph toggle
be encoded as the ASCII sequence
\begin_inset Quotes eld
\end_inset
1.0
\begin_inset Quotes erd
\end_inset
.
\layout Standard
<options> is an ASCII-encoded string of options pertaining to the format
identified by <format name> and <format version>.
For batches compliant with this specification, the options
\emph on
must
\emph toggle
consist of an ASCII-encoded number representing the total number of QSLs
contained in the batch.
\layout Subsubsection
Footer Format
\layout Standard
The footer
\emph on
must
\emph toggle
consist of a the following series of lines:
\layout Enumerate
A line containing only the ASCII-encoded string
\begin_inset Quotes eld
\end_inset
END OF QSLS
\begin_inset Quotes erd
\end_inset
\layout Enumerate
A line containing an ASCII encoded string identifying the party that has
created the batch.
This string
\emph on
must
\emph toggle
be the same as the string used in the VERIFIED-BY records in the QSLs.
\layout Enumerate
One of the following:
\begin_deeper
\layout Enumerate
A line containing only the string ASCII-encoded string
\begin_inset Quotes eld
\end_inset
KEY-ID
\begin_inset Quotes erd
\end_inset
, followed by a line containing the value of the public PGP key identifier
(the so-called
\begin_inset Quotes eld
\end_inset
keyID
\begin_inset Quotes erd
\end_inset
) corresponding to the private PGP key used to sign the batch.
\layout Enumerate
A line containing only the ASCII-encoded string
\begin_inset Quotes eld
\end_inset
CERTIFICATE
\begin_inset Quotes erd
\end_inset
, followed by a space, followed by an ASCII-encoded integer giving the num=
ber
of lines occupied by the digital certificate.
This line
\emph on
must
\emph toggle
be followed by a digital certificate in X.509 format.
The certificate
\emph on
must
\emph toggle
contain the BASE64-encoded public key corresponding to the private key
used to sign the batch.
\end_deeper
\layout Enumerate
A line containing only the ASCII-encoded string
\begin_inset Quotes eld
\end_inset
SIGNATURE
\begin_inset Quotes erd
\end_inset
, followed by a space, followed by an ASCII-encoded integer giving the num=
ber
of lines occupied by the signature.
\layout Enumerate
The BASE64-encoded digital signature.
\layout Enumerate
A line containing only the ASCII-encoded string
\begin_inset Quotes eld
\end_inset
BATCH END
\begin_inset Quotes erd
\end_inset
.
\layout Subsection
Batch Keys and Algorithms
\layout Standard
The key pair used to sign and authenticate a batch
\emph on
must
\emph toggle
be an RSA pair with length 1024 bits.
The algorithm used to sign the batch
\emph on
must
\emph toggle
be as follows:
\layout Enumerate
Concatenate, in order, all the digital signatures (after BASE64 decoding)
from all the VERIFIED-BY records added by the party that is signing the
batch.
\layout Enumerate
Take the result of step 1 and calculate the SHA-1 hash.
\layout Enumerate
Take the result of step 2 and encrypt it with the private RSA key of the
party that is signing the batch.
\layout Bibliography
\bibitem [POLICY]{5}
\emph on
Policy for Electronic QSLs
\emph toggle
, to be published.
\layout Bibliography
\bibitem [RFC 2045]{6}
RFC 2045,
\emph on
Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet
Message Bodies
\emph toggle
, Freed and Borenstein, 1996.
\layout Bibliography
\bibitem [SI]{4}
NIST Special Publication 811,
\emph on
Guide for the Use of the International System of Units (SI)
\emph toggle
, B.
N.
Taylor.
\layout Bibliography
\bibitem [TIME]{7}
\emph on
http://www.timeanddate.com/time/abbreviations.html
\the_end
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic