address
Click on the red underlined text to get to the source
... 1. Identification of a list of recipients.
2. Identification of an error return address.
3. Transfer of an RFC 822std11(-> 2822prop) ...
... X.400 O/R
names and RFC 822std11(-> 2822prop) addresses, which is a fundamental gateway
component.
...
... BNF Summary
F. Format of Address Tables
WARNING:
...
... Resent-*
Supported by use of a heading extension. Note that
addresses in these fields are mapped onto text, and so are
not accessible to the X.400 user as addresses ...
... addresses in these fields are mapped onto text, and so are
not accessible to the X.400 user as addresses. In
principle, fuller support would be possible by mapping onto
a forwarded IP Message ...
...
Originator Requested Alternate Recipient
Not supported, but is placed as comment next to address
(X400-Recipients:).
...
...
Reply Request Indication
Supported as comment next to address.
Replying IP Message ...
... N/A (reception).
Request for Forwarding Address
N/A (PDAU).
...
... There is also a need to represent Teletex Strings in ASCII, for some
aspects of O/R Address. For these, the following encoding is used:
...
... and right bracket ()). These characters, with the exception of round
brackets, are not included in PrintableString, but are common in RFC
822 addresses. The abbreviations will ease specification of RFC 822std11(-> 2822prop)
addresses ...
... addresses. The abbreviations will ease specification of RFC 822std11(-> 2822prop)
addresses from an X.400 system. These special encodings should be
...
... a side effect, also defines a textual representation of an X.400 O/R
Address.
Initially, we consider an address ...
... Address.
Initially, we consider an address in the (human) mail user sense of
"what is typed at the mailsystem to reference a mail user". A basic
RFC 822std11(-> 2822prop) ...
... "what is typed at the mailsystem to reference a mail user". A basic
RFC 822std11(-> 2822prop) address is defined by the EBNF EBNF.822-address:
...
... 822std11(-> 2822prop) header,
the EBNF.822-address is encapsulated in the 822.address syntax rule,
...
... the EBNF.822-address is encapsulated in the 822.address syntax rule,
and there may also be associated comments. None of this extra
information has any semantics ...
...
It can be seen that RFC 822std11(-> 2822prop) 822.address must be mapped with
IPMS.ORDescriptor, and that RFC 822std11(-> 2822prop) ...
... IPMS.ORDescriptor, and that RFC 822std11(-> 2822prop) EBNF.822-address must be mapped
with MTS.ORAddress.
...
...
An O/R Address has a number of structured and unstructured
attributes. For each unstructured attribute, a key and an encoding
...
... .ExtensionPhysicalDelivery
AddressComponents PD-EXT-LOC P/T 18.3.5 15
MTS.UnformattedPostalAddress PD-ADDRESS P/T 18.3.25 16
MTS.StreetAddress STREET P/T 18.3.22 17
MTS ...
... .LocalPostalAttributes PD-LOCAL P/T 18.3.6 21
MTS.ExtendedNetworkAddress
.e163-4-address.number NET-NUM N 18.3.7 22
MTS.ExtendedNetworkAddress
.e163-4- ...
... .number NET-NUM N 18.3.7 22
MTS.ExtendedNetworkAddress
.e163-4-address.sub-address NET-SUB N 18.3.7 22
MTS.ExtendedNetworkAddress
...
... MTS.ExtendedNetworkAddress
.e163-4-address.sub-address NET-SUB N 18.3.7 22
MTS.ExtendedNetworkAddress
.psap- ...
... NET-SUB N 18.3.7 22
MTS.ExtendedNetworkAddress
.psap-address NET-PSAP X 18.3.7 22
MTS.TerminalType NET-TTYPE I 18.3.24 23
...
...
The BNF for presentation-address is taken from the specification "A
String Encoding of Presentation Address ...
... address is taken from the specification "A
String Encoding of Presentation Address" [Kille89a].
...
... these components. A syntax is defined, which is designed to provide
a clean encoding for the common cases of O/R address specification
where:
...
...
This can be used to map from any string containing only printable
string characters to an O/R address personal name. Parse the string
according to the EBNF. The given name and surname are assigned
directly. All EBNF.initial tokens ...
... intervening full stops to generate the initials.
For an O/R address which follows the above restrictions, a string can
be derived in the natural manner. In this case, the mapping will be
reversible.
...
... Address.
std-or-address = 1*( "/" attribute "=" value ) "/"
attribute = standard-type
/ "RFC-822std11(-> 2822prop) ...
...
Ideally, the mapping specified would be entirely symmetrical and
global, to enable addresses to be referred to transparently in the
remote system, with the choice of gateway ...
...
The std-or-address syntax is used to encode O/R Address information
in the 822.local-part of EBNF.822-address ...
...
The std-or-address syntax is used to encode O/R Address information
in the 822.local-part of EBNF.822-address. Further O/R Address
information ...
... address syntax is used to encode O/R Address information
in the 822.local-part of EBNF.822-address. Further O/R Address
information may be associated with the 822.domain component. This
...
... Address information
in the 822.local-part of EBNF.822-address. Further O/R Address
information may be associated with the 822.domain component. This
cannot be used in the general case, basically due to character set ...
... character set
problems, and lack of order in X.400 O/R Addresses. The only way to
encode the full PrintableString character set in a domain ...
... domain conventions and policy.
A generic 822.address consists of a 822.local-part and a sequence of
822.domains (e.g., <@domain1,@domain2:user@domain3>). All except the
...
... 822std11(-> 2822prop) world. This final 822.domain may
be used to determine some number of O/R Address attributes. The
following O/R Address attributes are considered as a hierarchy, and
...
... be used to determine some number of O/R Address attributes. The
following O/R Address attributes are considered as a hierarchy, and
may be specified by the domain. They are (in order of hierarchy):
...
... For example, if a domain implies ADMD, it also implies country.
Subdomains under this are associated according to the O/R Address
hierarchy. For example:
...
... gateways relaying
between the RFC 822std11(-> 2822prop) world, and the O/R Address space associated with
the mapping in question. However, it is desirable (for the optimal
mapping of third party ...
... the mapping in question. However, it is desirable (for the optimal
mapping of third party addresses) for all gateways to know these
mappings. A format for the exchange of this information is defined
...
...
The remaining attributes are encoded on the LHS, using the EBNF.std-
or-address syntax. For example:
/I=J/S=Linnimouth/GQ=5/@Marketing.Widget.COM
...
... domain) encoding is designed to deal cleanly with common
addresses, and so the amount of information on the RHS should be
maximised. In particular, it covers the Mnemonic O/R Address ...
... addresses, and so the amount of information on the RHS should be
maximised. In particular, it covers the Mnemonic O/R Address using a
1984 compatible encoding. This is seen as the dominant form of O/R
...
... 1984 compatible encoding. This is seen as the dominant form of O/R
Address. Use of other forms of O/R Address, and teletex encoded
attributes will require an LHS encoding ...
... encoding. This is seen as the dominant form of O/R
Address. Use of other forms of O/R Address, and teletex encoded
attributes will require an LHS encoding.
...
... domain mechanisms are are used to
select appropriate gateways for the corresponding O/R Address space.
In most cases, this will be done by registering the higher levels,
and assuming that the gateway ...
... "natural" encoding of genuine RFC 822std11(-> 2822prop) addresses. This depends
largely on the allocation of appropriate management domains ...
... Horton86a].
Other O/R Address attributes will be used to identify a context in
which the O/R Address ...
... Address attributes will be used to identify a context in
which the O/R Address will be interpreted. This might be a
Management Domain ...
...
In most cases, ordering of O/R Address components is not significant
for the mappings specified. However, Organisational Units (printable
string and teletex forms) and Domain ...
...
1. The text encoding (std-or-address) of MTS.ORAddress as used
in the local-part of an RFC 822std11(-> 2822prop) ...
... MTS.ORAddress as used
in the local-part of an RFC 822std11(-> 2822prop) address. An order is needed
for those components which may have multiple values
(Organisational Unit, and Domain ...
... (Organisational Unit, and Domain Defined Attributes). When
generating an 822.std-or-address, components of a given type
shall be in hierarchical order with the most significant
component on the RHS. If there is an Organisation
...
...
- Alignment to the hierarchy of other components in RFC
822 addresses (thus, Organisational Units will appear
in the same order, whether encoded on the RHS or LHS).
Note the differences of JNT Mail as described in
...
...
- To ensure that gateways generate consistent addresses.
This is both to help end users, and to generate
identical message ids ...
...
There will be some cases where an X.400 O/R address of this
encoding will be generated by an end user from external
...
... - If an inversion of the Org Unit hierarchy generates a
valid address, when the preferred order does not,
assume that the hierarchy is inverted.
...
...
1. X.400 addresses encoded in RFC 822std11(-> 2822prop). This will also include
RFC 822std11(-> 2822prop) ...
... 822std11(-> 2822prop). This will also include
RFC 822std11(-> 2822prop) addresses which are given reversible encodings.
...
...
2. "Genuine" RFC 822std11(-> 2822prop) addresses.
The mapping should proceed as follows, by first assuming case 1).
...
...
NOTE:It may be appropriate to reduce a source route address
to this form by removal of all bar the last domain. In
...
... remove this quoting. Parse the (unquoted) 822.local-part
according to the EBNF EBNF.std-or-address. If this parse
fails, parse the local-part according to the EBNF
EBNF.encoded-pn. The result is a set of type/value pairs.
...
...
This will only be reached if the RFC 822std11(-> 2822prop) EBNF.822-address is not
a valid X.400 ...
... address is an 822-MTS recipient
address, it must be rejected, as there is a need to interpret
such an address in X.400 ...
... address, it must be rejected, as there is a need to interpret
such an address in X.400. For the 822-MTS return address ...
... address in X.400. For the 822-MTS return address, and
any addresses in the RFC 822std11(-> 2822prop) ...
... MTS return address, and
any addresses in the RFC 822std11(-> 2822prop) header, they should now be encoded
...
... header, they should now be encoded
as RFC 822std11(-> 2822prop) addresses in an X.400 O/R Name:
...
... X.400 O/R Name:
1. Convert the EBNF.822-address to PrintableString, as
specified in Chapter 3.
...
... Management
Domain agreed manner, so that the O/R Address will receive a
correct global interpretation.
...
...
2. "Genuine" X.400 addresses. This may include symmetrically
encoded RFC 822std11(-> 2822prop) addresses ...
... addresses. This may include symmetrically
encoded RFC 822std11(-> 2822prop) addresses.
When a MTS ...
...
When a MTS Recipient O/R Address is interpreted, gatewaying will be
selected if there a single "RFC-822std11(-> 2822prop)" domain ...
... 822std11(-> 2822prop)" domain defined attribute
present. In this case, use mapping A. For other O/R Addresses
which:
...
... NOTE:
A pragmatic approach would be to assume that any O/R
Address with the special domain defined attribute identifies
an RFC 822std11(-> 2822prop) ...
... domain defined attribute identifies
an RFC 822std11(-> 2822prop) address. This will usually work correctly, but is
in principle not correct.
...
...
This will be used for X.400 addresses which do not use the explicit
RFC 822std11(-> 2822prop) encoding ...
... the next subdomain. At least one attribute of the X.400
address should not be mapped onto subdomain, as
822.local-part cannot be null.
...
... pn should be derived to form 822.local-part. In other cases
the remaining components should simply be encoded as a
822.local-part using the EBNF.std-or-address syntax. If
necessary, the 822.quoted-string encoding should be used.
...
... received message will have the originator and any 3rd party X.400 O/R
Addresses in correct format (rather than doubly encoded). In cases
(X.400 or RFC 822std11(-> 2822prop) ...
...
Directory Names are an optional part of O/R Name, along with O/R
Address. The RFC 822std11(-> 2822prop) addresses are mapped onto the O/R Address ...
... Address. The RFC 822std11(-> 2822prop) addresses are mapped onto the O/R Address
component. As there is no functional mapping for the Directory Name
...
... Address. The RFC 822std11(-> 2822prop) addresses are mapped onto the O/R Address
component. As there is no functional mapping for the Directory Name
on the RFC 822std11(-> 2822prop) ...
... Use the basic ORAddress mapping, to generate the 822-MTS originator
(return address) from MTS.OtherMessageDeliveryFields.originator-name
(MTS ...
...
All RFC 822std11(-> 2822prop) addresses are assumed to use the 822.mailbox syntax.
This should include all 822.comments associated with the lexical
...
... address.
1. Take the address, and extract an EBNF.822-address. This can
be derived trivially from either the 822.addr-spec or
...
...
1. Take the address, and extract an EBNF.822-address. This can
be derived trivially from either the 822.addr-spec or
822.route ...
... 2. A string should be built consisting of (if present):
- The 822.phrase component if the 822.address is an
822.phrase 822.route-addr construct.
...
... Mapping from IPMS.ORDescriptor to RFC 822std11(-> 2822prop) address. In the basic
case, where IPMS.ORDescriptor.formal-name is present, proceed as
...
... 2b. If IPMS.ORDescriptor.free-form-name is absent. If
EBNF.822-address is parsed as 822.addr-spec use this as the
encoding of 822.mailbox ...
... encoding of 822.mailbox. If EBNF.822-address is parsed as
822.route 822.addr-spec, then a 822.phrase taken from
...
... Notification Requested)",
and/or "(IPM Return Requested)" should be appended to the
address. The effort of correlating P1 and P2 information is
too great to justify the gateway sending Receipt
...
... IPMS.RecipientSpecifier.reply-request is True, an
822.comment "(Reply requested)" should be appended to the
address.
If IPMS ...
... domains. For this reason, a purely algorithmic mapping is used. A
mapping which is simpler than that for addresses can be used for two
reasons:
...
... - There is no issue about being able to reply to message IDs.
(For addresses, creating a return path which works is more
important than being symmetrical).
...
... 822.local-part of 822.msg-id is built as:
[ printablestring ] "*" [ std-or-address ]
with EBNF.printablestring being the IPMS ...
... IPMS.IPMIdentifier.user-
relative-identifier, and std-or-address being an encoding of the
IPMS ...
... If the 822.local-part can be parsed as:
[ printablestring ] "*" [ std-or-address ]
and the 822.domain ...
... IPMS.IPMIdentifier.user-relative-identifier. If EBNF.std-or-address
is present, the O/R Address components derived from it are used to
...
... identifier. If EBNF.std-or-address
is present, the O/R Address components derived from it are used to
set IPMS.IPMIdentifier.user.
...
...
IPMS.IPMIdentifier.user to generate an EBNF.std-or-address form
string. Build the 822.local-part of the 822.msg-id with the syntax:
...
... string. Build the 822.local-part of the 822.msg-id with the syntax:
[ printablestring ] "*" [ std-or-address ]
The printablestring is taken from IPMS ...
... IPMS.Heading.originator. For this, and other components
containing addresses, the mappings of Chapter 4 are used
for each address.
...
... MTS.GlobalDomainIdentifier:
global-id = std-or-address
This is encoded using the std-or-address syntax ...
... address
This is encoded using the std-or-address syntax, for the attributes
within the Global Domain Identifier.
...
... IPMS.Heading is now specified for
each element. Addresses, and Message Identifiers are mapped
according to Chapter 4. Other mappings are explained, or are
...
... Priority" ":" priority
/ "Originator-Return-Address" ":" 1#mailbox
/ "DL-Expansion-History" ":" mailbox ...
... Mapped to the extended RFC 822std11(-> 2822prop) field
"Originator-Return-Address:".
physical ...
... [ "redirection history" 1#redirection ";"
[ "physical forwarding address"
printablestring ";" ]
...
... - Adopt an MTS Identifier syntax in line with the O/R Address
syntax.
- A new format for X400 Trace ...
... MTS.PerRecipientSubmissionFields.originator-request-
report.report shall be set for each recipient. If there is more that
one address in the Acknowledge-To: field, or if the one address is
not equivalent to the 822-MTS ...
... report.report shall be set for each recipient. If there is more that
one address in the Acknowledge-To: field, or if the one address is
not equivalent to the 822-MTS return address ...
... address is
not equivalent to the 822-MTS return address, then:
1. Acknowledgement(s) should be generated by the gateway ...
... Gatewaying of UUCP and X.400 is handled by first gatewaying the UUCP
address into RFC 822std11(-> 2822prop) syntax (using RFC 976) and then gatewaying the
...
... 976) and then gatewaying the
resulting RFC 822std11(-> 2822prop) address into X.400. For example, an X.400 address ...
... (assuming that Xerox.COM and /C=US/O=Xerox/ are equivalent.)
In the other direction, a UUCP address Smith@ATT.COM, integrated into
822, would be handled as any other 822 address. A non-integrated
...
... In the other direction, a UUCP address Smith@ATT.COM, integrated into
822, would be handled as any other 822 address. A non-integrated
address such as inthop!dest!user might be handled through a pair of
...
... 822, would be handled as any other 822 address. A non-integrated
address such as inthop!dest!user might be handled through a pair of
gateways:
...
... surname = printablestring
std-or-address = 1*( "/" attribute "=" value ) "/"
attribute = standard-type
/ "RFC-822std11(-> 2822prop) ...
... std-pair = "$" ps-char
dmn-or-address = dmn-part *( "." dmn-part )
dmn-part = attribute "$" value
attribute = standard-type
...
... [ "redirection history" 1#redirection ";"
[ "physical forwarding address"
printablestring ";" ]
...
... Priority" ":" priority
/ "Originator-Return-Address" ":" 1#mailbox
/ "DL-Expansion-History" ":" mailbox ...
... Appendix F - Format of address mapping tables ...
... possible match should be used.
First, an address syntax is defined, which is compatible with the
syntax used for 822.domains. It is intended that this syntax may be
...
... This syntax is not intended to be handled by users.
dmn-or-address = dmn-part *( "." dmn-part )
dmn-part = attribute "$" value
attribute = standard-type
...
...
Various further restrictions are placed on the usage of dmn-or-
address:
1. Only C, ADMD, PRMD, O, and OU may be used.
...
...
domain-syntax "#" dmn-or-address "#"
Note that the trailing "#" is used for clarity, as the dmn-or-
...
...
Note that the trailing "#" is used for clarity, as the dmn-or-
address syntax can lead to values with trailing blanks. Lines
staring with "#" are comments.
...
... Kille, S., "A String Encoding of Presentation Address", UCL Research Note 89/14, March 1989. ...
... Author's Address ...