domain
Click on the red underlined text to get to the source
... Postel82a], and RFC 1034std13
which is a Specification for domains and a distributed name
service [Mockapetris87a ...
... 822std11(-> 2822prop),
particularly in the addressing. They use domains which conform
to RFC 1034std13, but not the corresponding domain ...
... domains which conform
to RFC 1034std13, but not the corresponding domain nameservers
[Horton86a ...
... dialup portion of Csnet uses the Phonenet protocols as a
replacement for RFC 821std10(-> 2821prop). This portion uses domains which
conform to RFC 1034std13, but not the corresponding domain ...
... Mail Protocol, also known as Greybook [Kille84a]. This is used
with domains and name service specified by the JNT NRS (Name
...
... - This document does not obsolete RFC 987(-> 2156prop | 1327(-> 2156prop)), as it has a
different domain of application.
- If a gatewayed message is being transferred to a 1984
...
... functionality provided by such a gateway for communication with users
in the opposite domain. This chapter considers service mappings in
the context ...
... printable strings may only be derived from ASCII (and will therefore
have a restricted domain). For example, in this specification, it is
only applied to a Domain ...
... domain). For example, in this specification, it is
only applied to a Domain defined attribute which will have been
generated by use of this specification and a value such as "(" would
not be possible.
...
... X.400 attribute is
mapped onto one or more attribute value pairs. For domain defined
attributes, each element of the sequence will be mapped onto a triple
...
... MTS.TeletexPersonalName derived accordingly.
If dd-key is the recognised Domain Defined string (DD), then the type
and value should be interpreted according to the syntax implied from
...
...
If value is "RFC-822std11(-> 2822prop)", then the (printable string) Domain Defined
Type of "RFC-822std11(-> 2822prop)" is assumed. This is an optimised encoding ...
... 822std11(-> 2822prop)" is assumed. This is an optimised encoding of the
domain defined type defined by this specification.
The matching of all keywords should be done in a case- independent
...
... 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
...
... Addresses. The only way to
encode the full PrintableString character set in a domain is by use
of the 822.domain-ref syntax (i.e., 822.atom). This is likely to
...
... character set in a domain is by use
of the 822.domain-ref syntax (i.e., 822.atom). This is likely to
cause problems on many systems. The effective character set of
...
... cause problems on many systems. The effective character set of
domains is in practice reduced from the RFC 822std11(-> 2822prop) set, by restrictions
imposed by domain ...
... domains is in practice reduced from the RFC 822std11(-> 2822prop) set, by restrictions
imposed by domain conventions and policy.
A generic 822.address ...
... 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
822.domain associated with the 822.local-part (domain3 in this case)
...
... 822.domains (e.g., <@domain1,@domain2:user@domain3>). All except the
822.domain associated with the 822.local-part (domain3 in this case)
should be considered to specify routing within the RFC 822std11(-> 2822prop) ...
... Braden89a]).
The 822.domain associated with the 822.local-part may also identify
the gateway from within the RFC 822std11(-> 2822prop) ...
... the gateway from within the RFC 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
may be specified by the domain. They are (in order of hierarchy):
Country, ADMD, PRMD, Organisation, Organisational Unit
...
... There may be multiple Organisational Units.
Associations may be defined between domain specifications, and
some set of attributes. This association ...
... set of attributes. This association proceeds hierarchically.
For example, if a domain implies ADMD, it also implies country.
Subdomains under this are associated according to the O/R Address
...
... AC", O="Salford", OU="R-D"
There are three basic reasons why a domain/attribute mapping might
be maintained, as opposed to using simply subdomains:
...
... 822std11(-> 2822prop) allows for a more general syntax, this
restricted syntax is chosen as it is the one chosen by the
various domain service administrations.
...
...
3. To deal with missing elements in the hierarchy. A domain
may be associated with an omitted attribute in conjunction
...
... MTS.PersonalName.generation-qualifier = "5"
The first three attributes are determined by the domain Widget.COM.
Then, the first element of OrganizationalUnitNames is determined
...
... systematically, and the remaining attributes are encoded on the LHS.
In an extreme case, all of the attributes will be on the LHS. As the
domain cannot be null, the RHS will simply be a domain indicating the
gateway ...
... In an extreme case, all of the attributes will be on the LHS. As the
domain cannot be null, the RHS will simply be a domain indicating the
gateway.
...
... From the standpoint of the RFC 822std11(-> 2822prop) Message Transfer System, the
domain specification is simply used to route the message in the
standard manner. The standard domain ...
... domain specification is simply used to route the message in the
standard manner. The standard domain mechanisms are are used to
select appropriate gateways for the corresponding O/R Address space ...
... addresses. This depends
largely on the allocation of appropriate management domains.
The general case is mapped by use of domain ...
... domains.
The general case is mapped by use of domain defined attributes. A
Domain defined type "RFC-822std11(-> 2822prop) ...
... The general case is mapped by use of domain defined attributes. A
Domain defined type "RFC-822std11(-> 2822prop)" is defined. The associated attribute
value is an ASCII string ...
... Address will be interpreted. This might be a
Management Domain, or some part of a Management Domain which
...
... encoding of "@" as "(a)". In
the second example, the "RFC-822std11(-> 2822prop)" domain defined attribute is
interpreted everywhere within the (Private) Management Domain ...
... domain defined attribute is
interpreted everywhere within the (Private) Management Domain. In
the first example, further attributes are needed within the
Management ...
... the first example, further attributes are needed within the
Management Domain to identify a gateway. Thus, this scheme can be
used with varying levels of Management ...
... gateway. Thus, this scheme can be
used with varying levels of Management Domain co-operation.
...
... Address components is not significant
for the mappings specified. However, Organisational Units (printable
string and teletex forms) and Domain Defined Attributes are specified
as SEQUENCE in MTS.ORAddress, and so their order may be significant.
...
... This specification needs to take account of this:
1. To allow consistent mapping into the domain hierarchy
2. To ensure preservation of order over multiple mappings.
...
... address. An order is needed
for those components which may have multiple values
(Organisational Unit, and Domain Defined Attributes). When
generating an 822.std-or-address, components of a given type
...
... source route address
to this form by removal of all bar the last domain. In
terms of the design intentions of RFC 822std11(-> 2822prop), this would
...
... RFC 822std11(-> 2822prop) based systems. Either approach, or the
intermediate approach of stripping only domain
references which reference the local gateway are
...
... domain
Where EBNF.known-domain is the longest possible match in a
list of supported mappings (see Appendix F). If this fails,
and the EBNF.domain ...
... domain is the longest possible match in a
list of supported mappings (see Appendix F). If this fails,
and the EBNF.domain does not explicitly identify the local
gateway, go to stage II. If it succeeds, allocate the
...
... gateway, go to stage II. If it succeeds, allocate the
attributes associated with EBNF.known-domain, and
systematically allocate the attributes implied by each
...
... systematically allocate the attributes implied by each
EBNF.domain-syntax component. If the domain explicitly
identifies the gateway ...
...
EBNF.domain-syntax component. If the domain explicitly
identifies the gateway, allocate no attributes.
...
... EBNF.encoded-pn. The result is a set of type/value pairs.
If the values generated conflict with those derived in step
2 (e.g., a duplicated country attribute), the domain should
be assumed to be an RFC 987(-> 2156prop | 1327(-> 2156prop)) gateway ...
...
2. The "RFC-822std11(-> 2822prop)" domain defined attribute should be generated
from this string.
...
... Address in the local Management
Domain agreed manner, so that the O/R Address will receive a
correct global interpretation.
...
... correct global interpretation.
Note that the domain defined attribute value has a maximum length
of MTS ...
...
of MTS.ub-domain-defined-attribute-value-length (128). If this
is exceeded by a mapping at the MTS level, then the gateway ...
... Address is interpreted, gatewaying will be
selected if there a single "RFC-822std11(-> 2822prop)" domain defined attribute
present. In this case, use mapping A. For other O/R Addresses
...
... A pragmatic approach would be to assume that any O/R
Address with the special domain defined attribute identifies
an RFC 822std11(-> 2822prop) address ...
... 2. Noting the hierarchy specified in 4.3.1, determine the
maximum set of attributes which have an associated domain
specification. If no match is found, allocate the domain as
the domain specification ...
... maximum set of attributes which have an associated domain
specification. If no match is found, allocate the domain as
the domain specification of the local gateway ...
... domain
specification. If no match is found, allocate the domain as
the domain specification of the local gateway, and go to
step 4.
...
... components implied by the mapping tables (see Appendix F),
if each successive component exists, and conforms to the
syntax EBNF.domain-syntax (as defined in 4.3.1), allocate
the next subdomain. At least one attribute of the X.400
...
... X.400. Then it will be sent by JNT Mail to another gateway
determined by the domain Inria.ATLAS.FR (FR.ATLAS.Inria). This will
...
... ADMD, and PRMD components of this should be used to generate
MTS.MTSIdentifier.global-domain-identifier.
MTS ...
... form, as many systems use these ids as uninterpreted keys. The use
of table driven mappings is not always symmetrical, particularly in
the light of alternative domain names, and alternative management
domains ...
... domain names, and alternative management
domains. For this reason, a purely algorithmic mapping is used. A
mapping which is simpler than that for addresses can be used for two
...
...
The 822.domain of 822.msg-id is set to the value "MHS". The
822.local-part of 822.msg-id is built as:
...
... identifier. Use 822.quoted-string if necessary. The 822.msg-id is
generated with this 822.local-part, and "MHS" as the 822.domain.
...
... IPMS.IPMIdentifier.user-relative-identifier does not parse as
822.msg-id, generate an 822.phrase rather than adding the domain MHS.
...
... MTS.ORAddress, and used to derive
MTA.TraceInformationElement.global-domain-identifier. The
optional components of
...
... optional components of
MTA.TraceInformationElement.domain-supplied-information are
omitted, and the mandatory components are set as follows:
...
... created. The
MTA.InternalTraceInformationElement.global-domain-identifier
should be set to the value derived. The
...
... Global Domain Identifier ...
... This is encoded using the std-or-address syntax, for the attributes
within the Global Domain Identifier.
...
... trace from other management
domains has not been stripped, this may require complex interleaving.
Use this to generate a sequence of "X400-Received:" fields. The only
difference between external trace ...
... These are each given a section of this appendix.
2. Domain Ordering
When interpreting and generating domains ...
...
This syntax defined is initially in table form, but the syntax is
defined in a manner which makes it suitable for use with domain
nameservices (such as the Internet Domain ...
... First, an address syntax is defined, which is compatible with the
syntax used for 822.domains. It is intended that this syntax may be
used in conjunction with systems which support this form of name.
...
... Mockapetris, P., "Domain Names - Concepts and Facilities", RFC 1034std13, USC/Information Sciences Institute, November 1987. ...