分享
 
 
 

RFC2161 - A MIME Body Part for ODA

王朝other·作者佚名  2008-05-31
窄屏简体版  字體: |||超大  

Network Working Group H. Alvestrand

Request for Comments: 2161 UNINETT

Category: EXPerimental January 1998

A MIME Body Part for ODA

Status of this Memo

This memo defines an Experimental Protocol for the Internet

community. It does not specify an Internet standard of any kind.

Discussion and suggestions for improvement are requested.

Distribution of this memo is unlimited.

Copyright Notice

Copyright (C) The Internet Society (1998). All Rights Reserved.

Table of Contents

Status of this Memo ........................................ 1

1 IntrodUCtion .............................................. 1

1.1 The Application/ODA MIME content-type ................... 1

1.2 ODA - application/oda ................................... 2

2 Security Considerations ................................... 3

3 References ................................................ 4

4 Author's Address .......................................... 4

5 Full Copyright Statement .................................. 5

1. Introduction

This document contains the definitions, originally contained in RFC

1495 and RFC1341, on how to carry ODA in MIME, and how to translate

it to its X.400 representation.

1.1. The Application/ODA MIME content-type

The "ODA" suBType of application is used to indicate that a body

contains information encoded according to the Office Document

Architecture [ODA] standards, using the ODIF representation

format. For application/oda, the Content-Type line should also

specify an attribute/value pair that indicates the document

application profile (DAP), using the key Word "profile", and the

document class, using the keyword "class".

For the keyword "class", the values "formatted", "processable" and

"formatted-processable" are legal values.

Thus an appropriate header field might look like this:

Content-Type: application/oda; profile=Q112; class=formatted

Consult the ODA standard [T.411] for further information.

The Base64 content-transfer-encoding is appropriate for carrying ODA.

1.2. ODA - application/oda

X.400 Body Part: ODA

MIME Content-Type: application/oda

Conversion: None

Comments:

The ODA body part is defined in the CCITT document T.411 [T.411],

appendix E, section E.2, "ODA identification in the P2 protocol of

MHS"

An abbreviated version of its ASN.1 definition is:

oda-body-part EXTENDED-BODY-PART-TYPE

PARAMETERS OdaBodyPartParameters

DATA OdaData

::= id-et-oda

OdaBodyPartParameters ::= SET {

document-application-profile [0] OBJECT IDENTIFIER

document-architecture-class [1] INTEGER {

formatted (0)

processable (1)

formatted-processable(2)}}

id-et-oda OBJECT IDENTIFIER ::= { 2 8 1 0 1 }

Mapping from X.400 to MIME, the following is done:

The Parameters.document-application-profile is mapped onto the MIME

parameter "profile" according to the table below.

Profile OBJECT IDENTIFIER

Q112 { iso (1) identified-organization (3) ewos (16)

eg (2) oda (6) profile (0) q112 (1) }

The Parameters.document-architecture-class is mapped onto the MIME

parameter "class" according to the table below.

String Integer

formatted formatted(0)

processable processable(1)

formatted-processable formatted-processable(2)

NOTE: This parameter is not defined in RFC1341.

The body of the MIME content-type is the Data part of the ODA body

part.

When mapping from MIME to X.400, the following steps are done:

The Parameters.document-application-profile and Parameters.document-

architecture-class are set from the tables above. If any of the

parameters are missing, the values for Q112 and formatted-processable

are used.

It is an option for the gateway implementor to try to Access them

from inside the document, where they are defined as

document-profile.document-characteristics.document-architecture-class

document-profile.document-characteristics.document-application-

profile

Gateways are NOT required to do this, since the document-

characteristics are optional parameters. If a gateway does not, it

simply uses the defaulting rules defined above.

The OBJECT IDENTIFIERs for the document application profile and for

ODA {2 8 0 0} must be added to the Encoded Information Types

parameter of the message envelope.

2. Security Considerations

ODA body parts have the natural propensity of complex structures that

it is hard to find out what the parts are capable of.

Moreover, ODA is an extensible architecture, where new content

portions may be added at any time, so that the threats posed by this

body part may change over time.

However, no security risks related to ODA are known at this time.

3. References

[MIME]

Freed, N., and N. Borenstein, "Multipurpose

Internet Mail Extensions (MIME) Part One: Format of Internet Message

Bodies", RFC2045, November 1996.

[T.411]

CCITT Recommendation T.411 (1988), Open Document Architecture

(ODA) and Interchange Format, Introduction and General

Principles.

4. Author's Address

Harald Tveit Alvestrand

UNINETT

Postboks 6883 Elgeseter

N-7002 TRONDHEIM

Phone: +47 73 59 70 94

EMail: Harald.T.Alvestrand@uninett.no

5. Full Copyright Statement

Copyright (C) The Internet Society (1998). All Rights Reserved.

This document and translations of it may be copied and furnished to

others, and derivative works that comment on or otherwise explain it

or assist in its implementation may be prepared, copied, published

and distributed, in whole or in part, without restriction of any

kind, provided that the above copyright notice and this paragraph are

included on all such copies and derivative works. However, this

document itself may not be modified in any way, such as by removing

the copyright notice or references to the Internet Society or other

Internet organizations, except as needed for the purpose of

developing Internet standards in which case the procedures for

copyrights defined in the Internet Standards process must be

followed, or as required to translate it into languages other than

English.

The limited permissions granted above are perpetual and will not be

revoked by the Internet Society or its successors or assigns.

This document and the information contained herein is provided on an

"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING

TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING

BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION

HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF

MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

 
 
 
免责声明:本文为网络用户发布,其观点仅代表作者个人观点,与本站无关,本站仅提供信息存储服务。文中陈述内容未经本站证实,其真实性、完整性、及时性本站不作任何保证或承诺,请读者仅作参考,并请自行核实相关内容。
2023年上半年GDP全球前十五强
 百态   2023-10-24
美众议院议长启动对拜登的弹劾调查
 百态   2023-09-13
上海、济南、武汉等多地出现不明坠落物
 探索   2023-09-06
印度或要将国名改为“巴拉特”
 百态   2023-09-06
男子为女友送行,买票不登机被捕
 百态   2023-08-20
手机地震预警功能怎么开?
 干货   2023-08-06
女子4年卖2套房花700多万做美容:不但没变美脸,面部还出现变形
 百态   2023-08-04
住户一楼被水淹 还冲来8头猪
 百态   2023-07-31
女子体内爬出大量瓜子状活虫
 百态   2023-07-25
地球连续35年收到神秘规律性信号,网友:不要回答!
 探索   2023-07-21
全球镓价格本周大涨27%
 探索   2023-07-09
钱都流向了那些不缺钱的人,苦都留给了能吃苦的人
 探索   2023-07-02
倩女手游刀客魅者强控制(强混乱强眩晕强睡眠)和对应控制抗性的关系
 百态   2020-08-20
美国5月9日最新疫情:美国确诊人数突破131万
 百态   2020-05-09
荷兰政府宣布将集体辞职
 干货   2020-04-30
倩女幽魂手游师徒任务情义春秋猜成语答案逍遥观:鹏程万里
 干货   2019-11-12
倩女幽魂手游师徒任务情义春秋猜成语答案神机营:射石饮羽
 干货   2019-11-12
倩女幽魂手游师徒任务情义春秋猜成语答案昆仑山:拔刀相助
 干货   2019-11-12
倩女幽魂手游师徒任务情义春秋猜成语答案天工阁:鬼斧神工
 干货   2019-11-12
倩女幽魂手游师徒任务情义春秋猜成语答案丝路古道:单枪匹马
 干货   2019-11-12
倩女幽魂手游师徒任务情义春秋猜成语答案镇郊荒野:与虎谋皮
 干货   2019-11-12
倩女幽魂手游师徒任务情义春秋猜成语答案镇郊荒野:李代桃僵
 干货   2019-11-12
倩女幽魂手游师徒任务情义春秋猜成语答案镇郊荒野:指鹿为马
 干货   2019-11-12
倩女幽魂手游师徒任务情义春秋猜成语答案金陵:小鸟依人
 干货   2019-11-12
倩女幽魂手游师徒任务情义春秋猜成语答案金陵:千金买邻
 干货   2019-11-12
 
推荐阅读
 
 
 
>>返回首頁<<
 
靜靜地坐在廢墟上,四周的荒凉一望無際,忽然覺得,淒涼也很美
© 2005- 王朝網路 版權所有