As per Relevance of the word copyright, we have this rfc below:
Network Working Group H.
Request for Comments: 2158
Category: Standards Track January 1998
X.400 Image Body
Status of this
This document specifies an Internet standards track protocol for
Internet community, and requests discussion and suggestions
improvements. Please refer to the current edition of the "
Official Protocol Standards" (STD 1) for the standardization
and status of this protocol. Distribution of this memo is unlimited
Copyright
Copyright (C) The Internet Society (1998). All Rights Reserved
1.
This document contains the body parts defined in RFC 1495
carrying image formats that were originally defined in MIME
an X.400 system
It also documents the OIDs assigned to these data formats as
body parts, which allow the MIME types to be converted to FTAM
parts; this will probably be more useful than the new body
defined here
2. Newly defined X.400 body
2.1. The JPEG body
The following Extended Body Part is defined for JPEG data streams
It has no parameters
jpeg-body-part EXTENDED-BODY-PART-
DATA OCTET
::= mime-jpeg-
mime-jpeg-body OBJECT IDENTIFIER ::=
{ mixer-bp-data 3 }
The content is as defined in [MIME].
Alvestrand Standards Track [Page 1]
RFC 2158 X.400 Image Body Parts January 1998
2.2. The GIF body
The following Extended Body Part is defined for GIF data streams.
has no parameters
gif-body-part EXTENDED-BODY-PART-
DATA OCTET
::= mime-gif-
mime-gif-body OBJECT IDENTIFIER ::=
{ mixer-bp-data 4 }
The content is as defined in [MIME].
3. Defined equivalences with MIME
3.1. image/jpeg - jpeg-body-
X.400 Body Part: Extended Body Part, OID jpeg-body-
MIME Content-Type: image/
Conversion:
3.2. image/jpeg - FTAM EMA
X.400 Body Part: FTAM EMA
MIME Content-Type: image/
Conversion:
The OID assigned to JPEG by EMA in [MAWG]
{ ema objects(2) messaging (2) attachments(1) jpeg-image(6) }
while EMA's OID
{ joint-iso-ccitt(2) country(16) us(840) organization(1)
ema(113694) }
making the total OID, numeric
{ 2 16 840 1 113694 2 2 1 6 }
3.3. image/gif - gif-body-
X.400 Body Part: Extended Body Part, OID gif-body-
MIME Content-Type: image/
Conversion:
Alvestrand Standards Track [Page 2]
RFC 2158 X.400 Image Body Parts January 1998
3.4. image/gif - FTAM EMA
X.400 Body Part: FTAM EMA
MIME Content-Type: image/
Conversion:
The OID assigned to JPEG by EMA in [MAWG]
{ ema objects(2) messaging (2) attachments(1) gif-image(4) }
4. Security
Security issues are not considered in this memo
5.
[MIME
Freed, N., and N. Borenstein, "Multipurpose Internet
Extensions (MIME) Part One: Format of Internet Message Bodies",
RFC 2045, November 1996.
[MAWG
Electronic Messaging Association Message Attachment Working
(MAWG): File Transfer Body Part Feasibility Project Guide -
version 1.5.1 - March 1996.
6. Author's
Harald Tveit
Postboks 6883
N-7002
Phone: +47 73 59 70 94
EMail: Harald.T.Alvestrand@uninett.
Alvestrand Standards Track [Page 3]
RFC 2158 X.400 Image Body Parts January 1998
7. Full Copyright
Copyright (C) The Internet Society (1998). All Rights Reserved
This document and translations of it may be copied and furnished
others, and derivative works that comment on or otherwise explain
or assist in its implementation may be prepared, copied,
and distributed, in whole or in part, without restriction of
kind, provided that the above copyright notice and this paragraph
included on all such copies and derivative works. However,
document itself may not be modified in any way, such as by
the copyright notice or references to the Internet Society or
Internet organizations, except as needed for the purpose
developing Internet standards in which case the procedures
copyrights defined in the Internet Standards process must
followed, or as required to translate it into languages other
English
The limited permissions granted above are perpetual and will not
revoked by the Internet Society or its successors or assigns
This document and the information contained herein is provided on
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED,
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE
Alvestrand Standards Track [Page 4]
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
