|
|
::= | | <printablestring
'/' | ':' | '?' | ' '
<printablestring> ::=
2.1.
Values of type Undefined are encoded as if they were values of
Octet String, with the string value being the BER-encoded version
the value
2.2. Case Ignore
A string of type caseIgnoreStringSyntax is encoded as the
value itself
Howes, Kille, Yeong & Robbins [Page 2]
RFC 1778 Syntax Encoding March 1995
2.3. Case Exact
The encoding of a string of type caseExactStringSyntax is the
value itself
2.4. Printable
The encoding of a string of type printableStringSyntax is the
value itself
2.5. Numeric
The encoding of a string of type numericStringSyntax is the
value itself
2.6. Octet
The encoding of a string of type octetStringSyntax is the
value itself
2.7. Case Ignore IA5
The encoding of a string of type caseIgnoreIA5String is the
value itself
2.8. IA5
The encoding of a string of type iA5StringSyntax is the string
itself
2.9. T61
The encoding of a string of type t61StringSyntax is the string
itself
2.10. Case Ignore
Values of type caseIgnoreListSyntax are encoded according to
following BNF
<caseignorestring> '$'
<caseignorestring> ::= a string encoded according to the rules for
Ignore String as above
Howes, Kille, Yeong & Robbins [Page 3]
RFC 1778 Syntax Encoding March 1995
2.11. Case Exact
Values of type caseExactListSyntax are encoded according to
following BNF
Exact String as above
2.12. Distinguished
Values of type distinguishedNameSyntax are encoded to have
representation defined in [5].
2.13.
Values of type booleanSyntax are encoded according to the
BNF
Boolean values have an encoding of "TRUE" if they are logically true
and have an encoding of "FALSE" otherwise
2.14.
Values of type integerSyntax are encoded as the
representation of their values, with each decimal digit
by the its character equivalent. So the digit 1 is represented by
2.15. Object
Values of type objectIdentifierSyntax are encoded according to
following BNF
In the above BNF,
object descriptor. When encoding values of
objectIdentifierSyntax, the first encoding option should be used
preference to the second, which should be used in preference to
Howes, Kille, Yeong & Robbins [Page 4]
RFC 1778 Syntax Encoding March 1995
third wherever possible. That is, in encoding object identifiers
object descriptors (where assigned and known by the implementation
should be used in preference to numeric oids to the greatest
possible. For example, in encoding the object identifier
an organizationName, the descriptor "organizationName" is
to "ds.4.10", which is in turn preferable to the string "2.5.4.10".
2.16. Telephone
Values of type telephoneNumberSyntax are encoded as if they
Printable String types
2.17. Telex
Values of type telexNumberSyntax are encoded according to
following BNF
<answerback> ::= <printablestring
In the above,
number portion of the TELEX number being encoded,
TELEX country code, and <answerback> is the answerback code of
TELEX terminal
2.18. Teletex Terminal
Values of type teletexTerminalIdentifier are encoded according to
following BNF
In the above, the first <printablestring> is the encoding of
first portion of the teletex terminal identifier to be encoded,
the subsequent 0 or more
of the teletex terminal identifier
Howes, Kille, Yeong & Robbins [Page 5]
RFC 1778 Syntax Encoding March 1995
2.19. Facsimile Telephone
Values of type FacsimileTelephoneNumber are encoded according to
following BNF
'b4Length' | 'a3Width' | 'b4Width' | 'uncompressed
In the above, the first <printablestring> is the actual fax number
and the
2.20. Presentation
Values of type PresentationAddress are encoded to have
representation described in [6].
2.21. UTC
Values of type uTCTimeSyntax are encoded as if they were
Strings with the strings containing a UTCTime value
2.22. Guide (search guide
Values of type Guide, such as values of the searchGuide attribute
are encoded according to the following BNF
<criteria> ::= <criteria-item> | <criteria-set> | '!' <criteria
<criteria-set> ::= [ '(' ] <criteria> '&' <criteria-set> [ ')' ] |
[ '(' ] <criteria> '|' <criteria-set> [ ')' ]
<criteria-item> ::= [ '(' ]
Howes, Kille, Yeong & Robbins [Page 6]
RFC 1778 Syntax Encoding March 1995
2.23. Postal
Values of type PostalAddress are encoded according to the
BNF
In the above, each
encoded as a value of type t61StringSyntax
2.24. User
Values of type userPasswordSyntax are encoded as if they were of
octetStringSyntax
2.25. User
Values of type userCertificate are encoded according to the
BNF
<certificate> ::=
'#'
<signature-algorithm-id> ::= <algorithm-id
<validity> ::=
<algorithm-parameters> ::=
'{ASN}'
<encrypted-sign-value> ::=
<algorithm-id> ::=
Howes, Kille, Yeong & Robbins [Page 7]
RFC 1778 Syntax Encoding March 1995
2.26. CA
Values of type cACertificate are encoded as if the values were
type userCertificate
2.27. Authority Revocation
Values of type authorityRevocationList are encoded according to
following BNF
<certificate-list> ::= <signature-algorithm-id> '#'
'#' <signature-algorithm-id
'#' <encrypted-sign-value
<signature-algorithm-id> '#' <encrypted-sign-value
The syntactic components <signature-algorithm-id>,
<encrypted-sign-value>,
same definitions as in the BNF for the userCertificate
syntax
2.28. Certificate Revocation
Values of type certificateRevocationList are encoded as if the
were of type authorityRevocationList
2.29. Cross Certificate
Values of type crossCertificatePair are encoded according to
following BNF
<certificate-pair> ::=
Howes, Kille, Yeong & Robbins [Page 8]
RFC 1778 Syntax Encoding March 1995
The syntactic component <certificate> has the same definition as
the BNF for the userCertificate attribute syntax
2.30. Delivery
Values of type deliveryMethod are encoded according to the
BNF
<delivery-value> ::=
'g3fax' | 'g4fax' | 'ia5' | 'videotex' | 'telephone
2.31. Other
Values of the type otherMailboxSyntax are encoded according to
following BNF
In the above,
which the mailbox resides, for example "Internet" or "MCIMail";
2.32. Mail
Values of type mailPreferenceOption are encoded according to
following BNF
2.33. MHS OR
Values of type MHS OR Address are encoded as strings, according
the format defined in [10].
Howes, Kille, Yeong & Robbins [Page 9]
RFC 1778 Syntax Encoding March 1995
2.34. Distribution List Submit
Values of type DLSubmitPermission are encoded as strings,
to the following BNF
::=
where
2.35.
Values of type Photo are encoded as if they were octet
containing JPEG images in the JPEG File Interchange Format (JFIF),
described in [8].
2.36.
Values of type Fax are encoded as if they were octet
containing Group 3 Fax images as defined in [7].
Howes, Kille, Yeong & Robbins [Page 10]
RFC 1778 Syntax Encoding March 1995
3. Security
Security issues are not discussed in this memo
4.
Many of the attribute syntax encodings defined in this document
adapted from those used in the QUIPU X.500 implementation.
contributions of the authors of the QUIPU implementation in
specification of the QUIPU syntaxes [4] are gratefully acknowledged
5.
[1] The Directory: Selected Attribute Syntaxes. CCITT
Recommendation X.520.
[2] Information Processing Systems -- Open Systems Interconnection --
The Directory: Selected Attribute Syntaxes
[3] Barker, P., and S. Kille, "The COSINE and Internet X.500 Schema",
RFC 1274, University College London, November 1991.
[4] The ISO Development Environment: User's Manual -- Volume 5:
QUIPU. Colin Robbins, Stephen E. Kille
[5] Kille, S., "A String Representation of Distinguished Names",
1779, ISODE Consortium, March 1995.
[6] Kille, S., "A String Representation for Presentation Addresses",
RFC 1278, University College London, November 1991.
[7] Terminal Equipment and Protocols for Telematic Services -
Standardization of Group 3 facsimile apparatus for
transmission. CCITT, Recommendation T.4.
[8] JPEG File Interchange Format (Version 1.02). Eric Hamilton, C
Cube Microsystems, Milpitas, CA, September 1, 1992.
[9] Yeong, W., Howes, T., and S. Kille, "Lightweight Directory
Protocol", RFC 1777, Performance Systems International
University of Michigan, ISODE Consortium, March 1995.
[10] Alvestrand, H., Kille, S., Miles, R., Rose, M., and S. Thompson
"Mapping between X.400 and RFC-822 Message Bodies", RFC 1495,
SINTEF DELAB, ISODE Consortium, Soft*Switch, Inc., Dover
Consulting, Inc., Soft*Switch, Inc., August 1993.
Howes, Kille, Yeong & Robbins [Page 11]
RFC 1778 Syntax Encoding March 1995
6. Authors'
Tim
University of
ITD Research
535 W William St
Ann Arbor, MI 48103-4943
Phone: +1 313 747-4454
EMail: tim@umich.
Steve
ISODE
PO Box 505
SW11 1
Phone: +44-71-223-4062
EMail: S.Kille@isode.
Wengyik
PSI Inc
510 Huntmar Park
Herndon, VA 22070
Phone: +1 703-450-8001
EMail: yeongw@psilink.
Colin
NeXor
University
NG7 2
Howes, Kille, Yeong & Robbins [Page 12]
if you see any problems within the linking, don't worry be happy,
this is version 0.1 of the Relevance System and you gotta expect some crappy subroutines sometimes,
just be content we did not write this in Java, which would have made this "bigger and better" HAHAHHA.
RFC documents can be found at I.E.T.F.
Relevance System Copyright © 2002 Spectrum WorldResearch
other technical nosh by ServerMasters Corporation
collaboration of BobX
