the rfc package control file
Hello,
I kind of repackaged the doc-rfc package under the name rfc in order to
solve the plenty of problems repported against this package. On of the bug
where a typo in the description, and another was that the descriptions are
useless because explaining what the package contains only to the ones
already knowing what a RFC is.
So, I rewrote the descriptions, stealing some material here and there. But
since I'm not native speaker, I would be more than pleased if you guys could
review this text and help me improving what should be.
Thanks a lot, Mt.
--
C'est plus facile de faire l'amour que de faire la guerre. C'est une
question d'essence. Si on fait l'amour, c'est pour satisfaire les sens, et
c'est pour l'essence qu'on fait la guerre.
-- Raymond DEVOS.
Source: rfc
Section: non-free/doc
Priority: optional
Maintainer: Martin Quinson <Martin.Quinson@tuxfamily.org>
Build-Depends-Indep: debhelper (>> 3.0.0)
Standards-Version: 3.5.2
Package: rfc-tools
Architecture: all
Conflicts: doc-rfc (<< 20020901), doc-rfc-0001-0999 (<< 20020901), doc-rfc-1000-1999 (<< 20020901), doc-rfc-2000-2999 (<< 20020901), doc-rfc-3000-3999 (<< 20020901), doc-rfc-experimental (<< 20020901), doc-rfc-fyi-bcp (<< 20020901), doc-rfc-misc (<< 20020901), doc-rfc-old-std (<< 20020901), doc-rfc-std (<< 20020901), doc-rfc-std-proposed (<< 20020901)
Description: Searching tools for RFCs
The Requests for Comments (RFCs) form a series of notes, started in 1969,
about the Internet (originally the ARPANET). The notes discuss many aspects
of computer communication, focusing on networking protocols, procedures,
programs, and concepts but also including meeting notes, opinion, and
sometimes humor. See RFC2026 (in package rfc-bcp) for more information.
.
This package contains some searching tools about the RFCs.
Package: rfc-experimental
Architecture: all
Conflicts: doc-rfc (<< 20020901), doc-rfc-0001-0999 (<< 20020901), doc-rfc-1000-1999 (<< 20020901), doc-rfc-2000-2999 (<< 20020901), doc-rfc-3000-3999 (<< 20020901), doc-rfc-experimental (<< 20020901), doc-rfc-fyi-bcp (<< 20020901), doc-rfc-misc (<< 20020901), doc-rfc-old-std (<< 20020901), doc-rfc-std (<< 20020901), doc-rfc-std-proposed (<< 20020901)
Description: Experimental RFCs
The Requests for Comments (RFCs) form a series of notes, started in 1969,
about the Internet (originally the ARPANET). The notes discuss many aspects
of computer communication, focusing on networking protocols, procedures,
programs, and concepts but also including meeting notes, opinion, and
sometimes humor. See RFC2026 (in package rfc-bcp) for more information.
.
This package contains the 'experimental' RFCs. From RFC2026:
.
This designation typically denotes a specification that is part of some
research or development effort. Such a specification is published for the
general information of the Internet technical community and as an archival
record of the work, subject only to editorial considerations and to
verification that there has been adequate coordination with the standards
process.
Package: rfc-unclassified
Architecture: all
Conflicts: doc-rfc (<< 20020901), doc-rfc-0001-0999 (<< 20020901), doc-rfc-1000-1999 (<< 20020901), doc-rfc-2000-2999 (<< 20020901), doc-rfc-3000-3999 (<< 20020901), doc-rfc-experimental (<< 20020901), doc-rfc-fyi-bcp (<< 20020901), doc-rfc-misc (<< 20020901), doc-rfc-old-std (<< 20020901), doc-rfc-std (<< 20020901), doc-rfc-std-proposed (<< 20020901)
Description: RFCs which don't fit in other packages
The Requests for Comments (RFCs) form a series of notes, started in 1969,
about the Internet (originally the ARPANET). The notes discuss many aspects
of computer communication, focusing on networking protocols, procedures,
programs, and concepts but also including meeting notes, opinion, and
sometimes humor. See RFC2026 (in package rfc-bcp) for more information.
.
This package contains various RFCs whose status is 'unknown'.
Package: rfc-bcp
Architecture: all
Conflicts: doc-rfc (<< 20020901), doc-rfc-0001-0999 (<< 20020901), doc-rfc-1000-1999 (<< 20020901), doc-rfc-2000-2999 (<< 20020901), doc-rfc-3000-3999 (<< 20020901), doc-rfc-experimental (<< 20020901), doc-rfc-fyi-bcp (<< 20020901), doc-rfc-misc (<< 20020901), doc-rfc-old-std (<< 20020901), doc-rfc-std (<< 20020901), doc-rfc-std-proposed (<< 20020901)
Description: RFCs describing best current practices
The Requests for Comments (RFCs) form a series of notes, started in 1969,
about the Internet (originally the ARPANET). The notes discuss many aspects
of computer communication, focusing on networking protocols, procedures,
programs, and concepts but also including meeting notes, opinion, and
sometimes humor. See RFC2026 (in package rfc-bcp) for more information.
.
This package contains the 'best current practice' RFCs (also denoted BCP).
From RFC2026:
.
The BCP subseries of the RFC series is designed to be a way to standardize
practices and the results of community deliberations. A BCP document is
subject to the same basic set of procedures as standards track documents
and thus is a vehicle by which the IETF community can define and ratify the
community's best current thinking on a statement of principle or on what is
believed to be the best way to perform some operations or IETF process
function.
Package: rfc-standard
Architecture: all
Conflicts: doc-rfc (<< 20020901), doc-rfc-0001-0999 (<< 20020901), doc-rfc-1000-1999 (<< 20020901), doc-rfc-2000-2999 (<< 20020901), doc-rfc-3000-3999 (<< 20020901), doc-rfc-experimental (<< 20020901), doc-rfc-fyi-bcp (<< 20020901), doc-rfc-misc (<< 20020901), doc-rfc-old-std (<< 20020901), doc-rfc-std (<< 20020901), doc-rfc-std-proposed (<< 20020901)
Description: Standard RFCs
The Requests for Comments (RFCs) form a series of notes, started in 1969,
about the Internet (originally the ARPANET). The notes discuss many aspects
of computer communication, focusing on networking protocols, procedures,
programs, and concepts but also including meeting notes, opinion, and
sometimes humor. See RFC2026 (in package rfc-bcp) for more information.
.
This package contains the 'standards' RFCs. This is the third and last
maturity level for standard tracks. Please note that FYI and BCP standards
are in their own package. From RFC2026:
.
A specification for which significant implementation and successful
operational experience has been obtained may be elevated to the Internet
Standard level. An Internet Standard (which may simply be referred to as a
Standard) is characterized by a high degree of technical maturity and by a
generally held belief that the specified protocol or service provides
significant benefit to the Internet community.
Package: rfc-standard-old
Architecture: all
Conflicts: doc-rfc (<< 20020901), doc-rfc-0001-0999 (<< 20020901), doc-rfc-1000-1999 (<< 20020901), doc-rfc-2000-2999 (<< 20020901), doc-rfc-3000-3999 (<< 20020901), doc-rfc-experimental (<< 20020901), doc-rfc-fyi-bcp (<< 20020901), doc-rfc-misc (<< 20020901), doc-rfc-old-std (<< 20020901), doc-rfc-std (<< 20020901), doc-rfc-std-proposed (<< 20020901)
Description: Obsoleted standards
RFC stands for Request For Comment. Those documents are meant to become
Internet Standards after a maturiting process described in RFC2026 (which
can be found in package rfc-bcp).
.
This package contains the OBSOLETED 'standard' RFCs. Each of them
is obsoleted by another RFC, which can be found in another rfc-* package
(depending on the status of this new RFC).
Package: rfc-proposed
Architecture: all
Conflicts: doc-rfc (<< 20020901), doc-rfc-0001-0999 (<< 20020901), doc-rfc-1000-1999 (<< 20020901), doc-rfc-2000-2999 (<< 20020901), doc-rfc-3000-3999 (<< 20020901), doc-rfc-experimental (<< 20020901), doc-rfc-fyi-bcp (<< 20020901), doc-rfc-misc (<< 20020901), doc-rfc-old-std (<< 20020901), doc-rfc-std (<< 20020901), doc-rfc-std-proposed (<< 20020901)
Description: Proposed standard
The Requests for Comments (RFCs) form a series of notes, started in 1969,
about the Internet (originally the ARPANET). The notes discuss many aspects
of computer communication, focusing on networking protocols, procedures,
programs, and concepts but also including meeting notes, opinion, and
sometimes humor. See RFC2026 (in package rfc-bcp) for more information.
.
This package contains the 'proposed standard' RFCs. This is the entry-level
maturity for the standards track. From RFC2026:
.
A Proposed Standard specification is generally stable, has resolved known
design choices, is believed to be well-understood, has received
significant community review, and appears to enjoy enough community
interest to be considered valuable. However, further experience might
result in a change or even retraction of the specification before it
advances.
Package: rfc-proposed-old
Architecture: all
Conflicts: doc-rfc (<< 20020901), doc-rfc-0001-0999 (<< 20020901), doc-rfc-1000-1999 (<< 20020901), doc-rfc-2000-2999 (<< 20020901), doc-rfc-3000-3999 (<< 20020901), doc-rfc-experimental (<< 20020901), doc-rfc-fyi-bcp (<< 20020901), doc-rfc-misc (<< 20020901), doc-rfc-old-std (<< 20020901), doc-rfc-std (<< 20020901), doc-rfc-std-proposed (<< 20020901)
Description: Obsoleted proposed standards
RFC stands for Request For Comment. Those documents are meant to become
Internet Standards after a maturiting process described in RFC2026 (which
can be found in package rfc-bcp).
.
This package contains the OBSOLETED 'proposed standard' RFCs. Each of them
is obsoleted by another RFC, which can be found in another rfc-* package
(depending on the status of this new RFC).
Package: rfc-historic
Architecture: all
Conflicts: doc-rfc (<< 20020901), doc-rfc-0001-0999 (<< 20020901), doc-rfc-1000-1999 (<< 20020901), doc-rfc-2000-2999 (<< 20020901), doc-rfc-3000-3999 (<< 20020901), doc-rfc-experimental (<< 20020901), doc-rfc-fyi-bcp (<< 20020901), doc-rfc-misc (<< 20020901), doc-rfc-old-std (<< 20020901), doc-rfc-std (<< 20020901), doc-rfc-std-proposed (<< 20020901)
Description: Historical RFCs
The Requests for Comments (RFCs) form a series of notes, started in 1969,
about the Internet (originally the ARPANET). The notes discuss many aspects
of computer communication, focusing on networking protocols, procedures,
programs, and concepts but also including meeting notes, opinion, and
sometimes humor. See RFC2026 (in package rfc-bcp) for more information.
.
This package contains the 'historic' RFCs. From RFC2026:
.
A specification that has been superseded by a more recent specification or
is for any other reason considered to be obsolete is assigned to the
"Historic" level. (Purists have suggested that the word should be
"Historical"; however, at this point the use of "Historic" is
historical.
Package: rfc-informational
Architecture: all
Conflicts: doc-rfc (<< 20020901), doc-rfc-0001-0999 (<< 20020901), doc-rfc-1000-1999 (<< 20020901), doc-rfc-2000-2999 (<< 20020901), doc-rfc-3000-3999 (<< 20020901), doc-rfc-experimental (<< 20020901), doc-rfc-fyi-bcp (<< 20020901), doc-rfc-misc (<< 20020901), doc-rfc-old-std (<< 20020901), doc-rfc-std (<< 20020901), doc-rfc-std-proposed (<< 20020901)
Depends: rfc-fyi
Description: Informational RFCs
The Requests for Comments (RFCs) form a series of notes, started in 1969,
about the Internet (originally the ARPANET). The notes discuss many aspects
of computer communication, focusing on networking protocols, procedures,
programs, and concepts but also including meeting notes, opinion, and
sometimes humor. See RFC2026 (in package rfc-bcp) for more information.
.
This package contains the 'informational' RFCs. From RFC2026:
.
An 'Informational' specification is published for the general information
of the Internet community, and does not represent an Internet community
consensus or recommendation. The Informational designation is intended to
provide for the timely publication of a very broad range of responsible
informational documents from many sources, subject only to editorial
considerations and to verification that there has been adequate
coordination with the standards process.
Package: rfc-fyi
Architecture: all
Conflicts: doc-rfc (<< 20020901), doc-rfc-0001-0999 (<< 20020901), doc-rfc-1000-1999 (<< 20020901), doc-rfc-2000-2999 (<< 20020901), doc-rfc-3000-3999 (<< 20020901), doc-rfc-experimental (<< 20020901), doc-rfc-fyi-bcp (<< 20020901), doc-rfc-misc (<< 20020901), doc-rfc-old-std (<< 20020901), doc-rfc-std (<< 20020901), doc-rfc-std-proposed (<< 20020901)
Description: For Your Information RFCs
The Requests for Comments (RFCs) form a series of notes, started in 1969,
about the Internet (originally the ARPANET). The notes discuss many aspects
of computer communication, focusing on networking protocols, procedures,
programs, and concepts but also including meeting notes, opinion, and
sometimes humor. See RFC2026 (in package rfc-bcp) for more information.
.
This package contains the FYI serie of RFCs (For Your Information).
From RFC1150 (also known as FYI0001):
.
The FYI series of notes is designed to provide Internet users with a
central repository of information about any topics which relate to the
Internet. FYIs topics may range from historical memos on "Why it was was
done this way" to answers to commonly asked operational questions.
Package: rfc-draft
Architecture: all
Conflicts: doc-rfc (<< 20020901), doc-rfc-0001-0999 (<< 20020901), doc-rfc-1000-1999 (<< 20020901), doc-rfc-2000-2999 (<< 20020901), doc-rfc-3000-3999 (<< 20020901), doc-rfc-experimental (<< 20020901), doc-rfc-fyi-bcp (<< 20020901), doc-rfc-misc (<< 20020901), doc-rfc-old-std (<< 20020901), doc-rfc-std (<< 20020901), doc-rfc-std-proposed (<< 20020901)
Description: Draft standards
The Requests for Comments (RFCs) form a series of notes, started in 1969,
about the Internet (originally the ARPANET). The notes discuss many aspects
of computer communication, focusing on networking protocols, procedures,
programs, and concepts but also including meeting notes, opinion, and
sometimes humor. See RFC2026 (in package rfc-bcp) for more information.
.
This package contains the 'draft standards'. This is the second maturity
level for standards track, after 'proposed standard' and before 'standard'.
From RFC2026:
.
During the development of a specification, draft versions of the
document are made available for informal review and comment by
placing them in the IETF's 'Internet-Drafts' directory, which is
replicated on a number of Internet hosts. This makes an evolving
working document readily available to a wide audience, facilitating
the process of review and revision.
Package: rfc-draft-old
Architecture: all
Conflicts: doc-rfc (<< 20020901), doc-rfc-0001-0999 (<< 20020901), doc-rfc-1000-1999 (<< 20020901), doc-rfc-2000-2999 (<< 20020901), doc-rfc-3000-3999 (<< 20020901), doc-rfc-experimental (<< 20020901), doc-rfc-fyi-bcp (<< 20020901), doc-rfc-misc (<< 20020901), doc-rfc-old-std (<< 20020901), doc-rfc-std (<< 20020901), doc-rfc-std-proposed (<< 20020901)
Description: Obsoleted draft standards
RFC stands for Request For Comment. Those documents are meant to become
Internet Standards after a maturiting process described in RFC2026 (which
can be found in package rfc-bcp).
.
This package contains the OBSOLETED 'draft standard' RFCs. Each of them
is obsoleted by another RFC, which can be found in another rfc-* package
(depending on the status of this new RFC).
Package: doc-rfc
Architecture: all
Depends: rfc-standard, rfc-draft, rfc-fyi, rfc-bcp, rfc-experimental, rfc-historic, rfc-proposed-old, rfc-draft-old, rfc-standard-old, rfc-unclassified
Description: Transitional pseudo-package
This package pulls in some ot the new rfc-xxx packages (those that most
correspond to the old package).
.
It is otherwise useless and can be removed.
Package: doc-rfc-0001-0999
Architecture: all
Depends: rfc-unclassified
Description: Transitional pseudo-package
This package pulls in some ot the new rfc-xxx packages (those that most
correspond to the old package).
.
It is otherwise useless and can be removed.
Package: doc-rfc-1000-1999
Architecture: all
Depends: rfc-unclassified
Description: Transitional pseudo-package
This package pulls in some ot the new rfc-xxx packages (those that most
correspond to the old package).
.
It is otherwise useless and can be removed.
Package: doc-rfc-2000-2999
Architecture: all
Depends: rfc-unclassified
Description: Transitional pseudo-package
This package pulls in some ot the new rfc-xxx packages (those that most
correspond to the old package).
.
It is otherwise useless and can be removed.
Package: doc-rfc-3000-3999
Architecture: all
Depends: rfc-unclassified
Description: Transitional pseudo-package
This package pulls in some ot the new rfc-xxx packages (those that most
correspond to the old package).
.
It is otherwise useless and can be removed.
Package: doc-rfc-experimental
Architecture: all
Depends: rfc-experimental
Description: Transitional pseudo-package
This package pulls in some ot the new rfc-xxx packages (those that most
correspond to the old package).
.
It is otherwise useless and can be removed.
Package: doc-rfc-fyi-bcp
Architecture: all
Depends: rfc-fyi, rfc-bcp
Description: Transitional pseudo-package
This package pulls in some ot the new rfc-xxx packages (those that most
correspond to the old package).
.
It is otherwise useless and can be removed.
Package: doc-rfc-misc
Architecture: all
Depends: rfc-historic
Description: Transitional pseudo-package
This package pulls in some ot the new rfc-xxx packages (those that most
correspond to the old package).
.
It is otherwise useless and can be removed.
Package: doc-rfc-old-std
Architecture: all
Depends: rfc-proposed-old, rfc-draft-old, rfc-standard-old
Description: Transitional pseudo-package
This package pulls in some ot the new rfc-xxx packages (those that most
correspond to the old package).
.
It is otherwise useless and can be removed.
Package: doc-rfc-std
Architecture: all
Depends: rfc-standard, rfc-draft
Description: Transitional pseudo-package
This package pulls in some ot the new rfc-xxx packages (those that most
correspond to the old package).
.
It is otherwise useless and can be removed.
Package: doc-rfc-std-proposed
Architecture: all
Depends: rfc-proposed
Description: Transitional pseudo-package
This package pulls in some ot the new rfc-xxx packages (those that most
correspond to the old package).
.
It is otherwise useless and can be removed.
Reply to: