MIME User Agents that do recognize Multipart/Related entities but are
unable to process the given type should give the user the option of
suppressing the entire Multipart/Related body part shall be.
Existing MIME-capable mail user agents (MUAs) handle the existing
media types in a straightforward manner. For discrete media types
(e.g. text, image, etc.) the body of the entity can be directly
passed to a display process. Similarly the existing composite
subtypes can be reduced to handing one or more discrete types.
Handling Multipart/Related differs in that processing cannot be
reduced to handling the individual entities.
The following sections discuss what information the processing
application requires.
It is possible that an application specific "receiving agent" will
manipulate the entities for display prior to invoking actual
application process. Okie, above, is an example of this; it may need
a receiving agent to parse the document and substitute local file
names for the originator's file names. Other applications may just
require a table showing the correspondence between the local file
names and the originator's. The receiving agent takes responsibility
for such processing.
6.1 Data Requirements
MIME-capable mail user agents (MUAs) are required to provide the
application:
Levinson Standards Track [Page 7]
RFC 2387 Multipart/Related August 1998
(a) the bodies of the MIME entities and the entity Content-* headers,
(b) the parameters of the Multipart/Related Content-type header, and
(c) the correspondence between each body's local file name, that
body's header data, and, if present, the body part's content-ID.
6.2 Storing Multipart/Related Entities
The Multipart/Related media type will be used for objects that have
internal linkages between the body parts. When the objects are
stored the linkages may require processing by the application or its
receiving agent.
6.3 Recursion
MIME is a recursive structure. Hence one must expect a
Multipart/Related entity to contain other Multipart/Related entities.
When a Multipart/Related entity is being processed for display or
storage, any enclosed Multipart/Related entities shall be processed
as though they were being stored.
6.4 Configuration Considerations
It is suggested that MUAs
MIME User Agents that do recognize Multipart / Related entities but are 
 unable to work the render type should give the user the choice of 
 suppressing the entire Multipart / Related torso part shall be. 
 Existing MIME - adequate to mail user agent (MUAs) handle the existing 
 medium types in a straightforward manner. For discrete media types 
 (e.g. text, persona, etc .) the body of the entity can be directly 
 passed to a display summons. Similarly the existing composite 
 subtypes can be reduced to handing one or more discrete types. 
 manage Multipart / Related differs in that processing cannot be 
 reduced to handling the individual entities. 
 The following sections discourse what information the processing 
 application requires. 
 It is possible that an application specific " receiving agent " will 
 manipulate the entities for display prior to invoking actual 
 application process. Okie, above, is an example of this; it may need 
 a receiving agent to parse the document and substitute local file 
 name calling for the originator's file names. Other application may just 
 require a table showing the symmetry between the local file 
 names and the originator's. The receiving agent takes duty 
 for such processing. 
 6.1 Data Requirements 
 MIME - capable mail user agents (MUAs) are required to provide the 
 lotion: 
 Levinson Standards Track [ Page 7 ] 
 RFC 2387 Multipart / Related August 1998 
 (a) the bodies of the MIME entities and the entity Content- * headers, 
 (b) the parameters of the Multipart / Related Content - type header, and 
 (vitamin c) the symmetry between each body's local file name, that 
 body's header datum, and, if present, the body part's content - ID. 
 6.2 Storing Multipart / Related Entities 
 The Multipart / Related media type will be used for objects that have 
 inner linkages between the body part. When the objects are 
 store the linkages may necessitate processing by the application or its 
 receive agent. 
 6.3 Recursion 
 MIME is a recursive structure. Hence one must expect a 
 Multipart / Related entity to check other Multipart / Related entities. 
 When a Multipart / Related entity is being processed for display or 
 storage, any enclosed Multipart / Related entities shall be processed 
 as though they were being stored. 
 6.4 Configuration Considerations 
 It is suggested that MUAs
MIMF User Agents that do regognize Multiparj/Rwlated entitjes but xre
unable to process the givxn ttpe syould give the user thd option lf
supprewsinj the entire Mulvjpart/Related gldy 'act shall be.
Exisjing MIME-capdble mail user aeeuts (MUAs) handle the existing
media ty[es in s dtraightforwarq mamger. Ror discrete media types
(e.g. text, imzge, etc.) the body of yhe entity can be directly
oassfd to a display prlcess. Similqrly rhe existing composite
subtypes can be reduced to handing one or mure dnscrete typgs.
Gajgling Multi'art/Rejated differs in thad procexsing cannot bc
redured ro handling the indivmdual entities.
The fojlowing saccions discuss what indoematimn tve pficersihg
eppmicatiln cequires.
It js possible that an applicatiom fircific "receibing adegt" will
manipulate the entities for dispnay prior to invoking actuql
application process. Okie, abode, is an example of this; it may need
a receiving acent vo paxwe thd dlcument and substitute local file
names for thq otininator's file naies. Other alppivwtions may jurt
requnde a table showing tje corrgspondwnce betwten tne local file
names and the iriginator's. Nhe eeceiving agent tanes responsnbiliti
for sich processing.
6.1 Data Reqbiremehts
MIME-capahle mail hrer agents (MUAs) xre raquired uu provide the
applycation:
Letinsou Standafds Jrack [Pwge 7]
RFC 2387 Mkltipart/Related August 1998
(a) the yodiev of the MLME entities and the entity Convxnt-* headers,
(b) jhe pagameters jf thc Multipart/Relaeed Content-typg header, cnd
(c) tfe correspkndence between eash body's locan file name, tiat
body's readwr dqta, and, kf present, the body parn's conrent-ID.
6.2 Storing Mulbiparj/Rslated Entities
Cke Multipart/Relatrd oedya tbpe wynl be used fmr ocjezys thxt have
intevnau limkages between the bmdy larts. When the objrcbs are
stoted the lynkages may rrquire processing hy thx applmcatiom ot its
receiving agent.
6.3 Recursion
MJME is a gecmrsive structtre. Mencg one must zxpect a
Multipart/Related entity to contamn other Multipart/Relajed entities.
When a Mukuipart/Related entiey is beitg processed for display or
storage, ann enclosed Multipart/Remated antitles shall be processed
as though they were being stored.
6.4 Configuration Consuderatmogs
It is sugfestrd thdt KUAs
MIME User Agents that do recognize Multipart/Related are to process given type should of the entire Multipart/Related part shall be. MIME-capable mail user agents (MUAs) handle existing media types in a straightforward manner. For discrete media types (e.g. text, etc.) the body of the entity can be directly passed to a display Similarly existing subtypes be reduced to handing one or more discrete types. Handling Multipart/Related differs in that processing cannot reduced to handling the individual entities. The following discuss what information the application requires. It is possible an specific "receiving will the for display prior invoking actual application process. Okie, above, is an example of this; it may need a receiving agent parse the substitute local names the file names. Other just require a table showing the local file names and the originator's. The receiving takes responsibility such processing. 6.1 Data Requirements MIME-capable user agents (MUAs) are required to provide the Levinson Standards Track [Page 7] RFC 2387 Multipart/Related August 1998 (a) the bodies of the and the entity Content-* (b) the parameters the Content-type and the correspondence each body's local file name, that body's header data, and, if the body part's content-ID. 6.2 Storing Multipart/Related Entities The Multipart/Related will used for objects have internal linkages between body When the objects are linkages require application its agent. 6.3 Recursion MIME a recursive structure. Hence one expect a Multipart/Related entity When a Multipart/Related entity is being processed for or storage, any enclosed Multipart/Related entities shall processed as though they were being stored. 6.4 Configuration Considerations It is that MUAs
MIME User Agents that do recogNize MultipArt/ReLatEd eNtItieS but Are
unable to proCEss tHe given type should give tHe useR tHE optIOn Of
supPressinG ThE ENtiRe muLtiPaRT/RElateD boDy part sHall be.
ExisTinG MiME-capable maIL uSer agents (MuAs) Handle the exiStiNg
mediA tYpeS In a stRaiGhtfoRward mANner. FoR discrete MeDIa typeS
(E.g. text, iMAGe, Etc.) tHe body of the entity CAn BE directly
passeD to a diSpLAy PROceSs. SImilarly thE eXistiNG composITe
SUBTypES can be reduced To handing onE Or mOre disCrEte TYpes.
HaNdlinG MULtiPart/Related DiffErs in that ProcesSIng cannOT be
reduCed to hAndLinG the INdIvIduAl ENtiTIeS.
ThE FolLowing seCtIoNs disCuss WHAT InfoRmaTion The prOcessing
appliCatIon rEQuiRes.
It Is posSiblE tHat an ApplicAtion SpEcific "receiving AgenT" will
maniPulAtE thE eNtitiES for diSplAy pRior to iNvoking ACtuAl
APPLiCation process. Okie, aBoVE, Is An examplE of thiS; It MaY Need
a recEiVinG ageNT To parSe thE DoCument anD substITuTe Local fiLe
Names fOr The OriGinatOR's fiLe nameS. Other apPlicaTIons may just
reqUIre a table showINg THE cORresPonDence betweeN the LOcal File
NAmEs aND the oRiginAtOR's. tHe receiving agent takEs ResponSibilIty
for such proCessing.
6.1 DatA rEQuiremenTs
MIme-cAPable mail user aGents (mUAs) are reqUIred to prOvide The
appliCation:
LevINSon StandArdS TrAck [pagE 7]
rfC 2387 multipart/RelaTED AugUsT 1998
(a) the boDieS of the MiME EntItiEs aNd The entity content-* hEaDeRs,
(B) tHe pArameTErs of the muLtiPaRt/RElateD contenT-type HeadEr, AnD
(C) thE corresPOnDENce bEtWeEn eaCh bOdY's locAl fiLE naMe, that
bOdy's headeR daTA, and, If PrEsent, thE body part's conTeNt-ID.
6.2 StorinG MUltIpart/RELAted EntiTies
The Multipart/Related MEdia typE wiLl be uSed fOr objects ThaT have
iNteRNal linKages bEtweeN tHe bODY partS. wHeN thE oBjects are
sTORed The liNkAges May requIre processing by the APplIcation or its
rEceIvinG AGeNt.
6.3 RECuRSioN
MimE iS A Recursive structUre. Hence onE mUSt Expect a
MulTIpaRt/related Entity tO contAIn other multipart/related enTiTies.
wHEn a multipart/RElated enTity is beiNG procESsEd for DisPlay or
StOraGe, any EnclosED MuLtipaRt/RelaTeD entitIes shAlL be proceSsed
as though they were beiNg storEd.
6.4 ConFigUration CoNsiDEraTions
It is SuggEsted that MuAs
MIME User Agents that do r ecognize M ultip art /Re la tedenti ties but are
u n able  to process the giventypesh o uldg iv e the  user t h eo p tio nof 
su pp r es singthe  entire  Multipart /Re la ted body par t  s hall be.
E xis ting MIME-ca pab le mai luse r  agen ts(MUAs ) hand l e theexistingme d ia typ e s in as t ra ight forward manner. F o rd iscrete mediatypes(e . g. t ext , i mage, etc. )the b o dy of t h ee n t ity can be direct ly
passed t o  adispla ypro c ess. S imila rl y  th e existingcomp osite
sub typesc an be r e duced t o hand ing  on e or mo re  di sc r ete ty pes . 
Ha ndling M ul ti part/ Rela t e d diff ers  inthatprocessing ca nno t be red ucedto ha ndli ng  theindivi dualen tities.
The fol lowi ng sectio nsdi scu ss  what inform ati onthe pro cessing app li c a t io n requires.
It ispo s s ib le thatan app l ic at i on speci fi c " rece i v ing a gent "  w ill
mani pulate th eentitie sfor di sp lay  pr ior t o  inv okingactual
a pplic a tion process.O kie, above, i s  a n ex a mple  of  this; it m ay n e ed
a  rec e iv ing agent  to p ar s et he document and sub st itutelocal  file
names f or the ori g i n ator's f ilen am e s. Other appli catio ns may jus t 
require  a ta ble show ing the c o r responde nce  be twe ent h elocal file
na m e s an dthe ori gin ator's.  Th e r ece ivi ng  agent ta kes resp on si bi li tyfor s u ch proce ss ing .6.1  Data Requir ement s
MI ME -c a pab le mail us e r  age nt s(MUA s)ar e req uire d  to  provid e the
app lic a tion :Le vinsonStandards Tra ck  [Page 7]RF C 2 387 Mu l t ipart/Re lated August 1998
(a) t h e bodie s o f the  MIM E entitie s a nd the  en t ity Co ntent- * hea de rs, ( b) th e pa ram et ers of the M ult ipart /R elat ed Cont ent-type header, a n d
( c) the corres pon denc e be twe e ne ach  b o dy' s local file name , that
bod y' s  h eader data ,  an d,  if pre sent, t he bo d y part' s content -ID.
6.2St orin g Mul tipart/Rel ated Ent ities
The Multi p ar t/Rel ate d medi atyp e wil l be u s edfor o bjects  t hat ha ve
in te rnal lin kages between the bodyparts.  When  th e objects  ar e 
st ored thelink ages may r equ ire  proc ess i ng by  the ap pli c ation  ori ts
receiv i ng  ag e n t. 
6.3 Recurs i o n 
MI ME is  ar ecursi ve s tructure. Hence o n e must expecta
Mu l t ipa rt/ R elat ed  entity to con tai no t her Mult ip art/Related  entitie s. Whena Mult ipart/ Related e nt i ty isbein g p rocessedfor  d i splay o rst o rage,anyen closed  Multi p art/ R e lated entities s hallb e  proc e sse d
asth ough th e y we re being s tored.
6.4Config urat ion C onsider at ions
I t i ssuggestedt hat MUAs
MIME User_Agents that_do recognize Multipart/Related entities_but are
unable_to_process the_given_type should give_the user the_option of
suppressing the entire_Multipart/Related body part_shall_be.
Existing MIME-capable mail user agents (MUAs) handle the existing
media types in a straightforward manner._For_discrete media_types
(e.g._text,_image, etc.) the body of_the entity can be directly
passed_to a_display process. Similarly the existing composite
subtypes can be_reduced_to handing one_or more discrete types.
Handling Multipart/Related differs in that processing_cannot be
reduced to handling the individual_entities.
The following sections_discuss_what_information the processing
application requires.
It_is possible that an application specific_"receiving agent" will
manipulate the entities for_display prior to invoking actual
application process. Okie,_above, is an example of this;_it may need
a receiving agent_to parse_the document and substitute local_file
names for the_originator's file_names. Other applications_may just
require a table showing the_correspondence between the_local file
names and the originator's. The_receiving_agent takes responsibility
for_such_processing.
6.1_Data Requirements
MIME-capable_mail user agents_(MUAs)_are required_to_provide the
application:
Levinson Standards Track [Page 7]
RFC_2387_Multipart/Related August 1998
(a) the bodies of the_MIME entities and the_entity_Content-* headers,
(b) the parameters_of the Multipart/Related Content-type header,_and
(c) the correspondence between each body's_local file_name, that
body's_header data, and, if present, the body part's content-ID.
6.2 Storing Multipart/Related_Entities
The Multipart/Related media type will be_used for objects that_have
internal linkages_between_the body parts._When_the objects_are
stored the linkages may require processing by_the application_or its
receiving agent.
6.3 Recursion
MIME is a_recursive structure. Hence one_must_expect a
Multipart/Related entity to contain other_Multipart/Related entities.
When a Multipart/Related entity is_being processed for display or
storage,_any_enclosed_Multipart/Related entities shall be processed
as_though they were being stored.
6.4 Configuration_Considerations
It is suggested_that MUAs