1998
DOI: 10.17487/rfc2156
|View full text |Cite
|
Sign up to set email alerts
|

MIXER (Mime Internet X.400 Enhanced Relay): Mapping between X.400 and RFC 822/MIME

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
5
0

Year Published

1998
1998
2008
2008

Publication Types

Select...
6

Relationship

1
5

Authors

Journals

citations
Cited by 12 publications
(5 citation statements)
references
References 14 publications
0
5
0
Order By: Relevance
“…Objects larger than these sizes SHOULD be avoided when possible. However, some Internet mail constructs such as encoded X.400 addresses (RFC 2156 [35]) will often require larger objects. Clients MAY attempt to transmit these, but MUST be prepared for a server to reject them if they cannot be handled by it.…”
Section: Size Limits and Minimumsmentioning
confidence: 99%
“…Objects larger than these sizes SHOULD be avoided when possible. However, some Internet mail constructs such as encoded X.400 addresses (RFC 2156 [35]) will often require larger objects. Clients MAY attempt to transmit these, but MUST be prepared for a server to reject them if they cannot be handled by it.…”
Section: Size Limits and Minimumsmentioning
confidence: 99%
“…A value of the ORAddress type is encoded according to the <ORAddressValue> rule as a quoted character string. The character string is first derived according to the textual representation of MTS.ORAddress from RFC 2156 [2], and then encoded as if it were an IA5String value. The IETF takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights.…”
Section: Relativedistinguishednamevalue = Stringvaluementioning
confidence: 99%
“…/ "/" / ":" / "=" / "?" ) ; this definition comes from ITU F.401 [9] ; and MIXER [3] Table 1 includes short definition of qual2-label fields: …”
Section: The Extensible Recipient-qualifiermentioning
confidence: 99%
“…For example, to the extent possible, compatibility has been maintained with the MIXER [3] gateways specifications.…”
Section: Introductionmentioning
confidence: 99%