rfc1495
Justin Ziegler <Justin.Ziegler@inria.fr> Wed, 04 May 1994 16:00 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa06809; 4 May 94 12:00 EDT
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa06804; 4 May 94 12:00 EDT
Received: from survis.surfnet.nl by CNRI.Reston.VA.US id aa11109; 4 May 94 12:00 EDT
Received: from concorde.inria.fr by survis.surfnet.nl with SMTP (PP) id <01876-0@survis.surfnet.nl>; Wed, 4 May 1994 17:47:32 +0200
Received: from chandon.inria.fr (chandon.inria.fr [128.93.2.8]) by concorde.inria.fr (8.6.9/8.6.9) with SMTP id RAA10562 for <mime-mhs@surfnet.nl>; Wed, 4 May 1994 17:47:29 +0200
Received: by chandon.inria.fr; Wed, 4 May 1994 17:47:17 +0200
Message-Id: <199405041547.AA01784@chandon.inria.fr>
To: mime-mhs@surfnet.nl
Cc: ziegler@chandon.inria.fr
Subject: rfc1495
Date: Wed, 04 May 1994 17:47:17 +0200
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Justin Ziegler <Justin.Ziegler@inria.fr>
hello, I am still studying all the rfcs about gatewaying MIME and X400. In particular section 3.2.1.2 of rfc1495 has kept my attention. ------------ 3.2.1.2. Message/Partial This is mapped onto a *message*, and the following heading extension is used. The extension is derived from the message/partial parameters: partial-message HEADING-EXTENSION VALUE PartialMessage ::= id-hex-partial-message PartialMessage ::= SEQUENCE { number INTEGER, total INTEGER, id IA5String } If this heading is present when mapping from MHS to MIME, then a message/partial should be generated. ------------ I guess the word message between stars refers to an IPMS.messageBodyPart. But an IPMS.messageBodyPart has a structure, and is a sequence of IPMS.BodyParts. The message broken into message/partials may also have a structure. Thus the partial message must be broken into BodyParts if it contains a multipart body. The parsing can not be applied separatly to the parts of the broken message. The only possible solution is that the gateway receives all the parts and reassembles them. But a gateway can not be expected to receive all the parts, some of them may be sent to other gateways... I feel this creates a few problems, that need a bit more consideration. Has this already been solved and discussed ?? Justin
- Re: rfc1495 Harald T. Alvestrand
- rfc1495 Justin Ziegler
- Re: rfc1495 Ned Freed
- Re: rfc1495 Harald T. Alvestrand
- Re: rfc1495 John Haxby
- Re: rfc1495 Justin Ziegler
- Re: rfc1495 Carl S. Gutekunst
- Re: rfc1495 Ned Freed
- Re: rfc1495 Keith Moore