Harald.T.Alvestrand | 1 Apr 20:42 1995
Picon
Picon

Re: Update to draft-onions-822-mailproblems-01.txt

Julian,
I've been thinking about how to deal with the fact that we have the
822-AS document and your document running more or less in parallel.

What do you think of attempting to tune them so that your document
explains all the horrors that can occur on the Internet, and why
it is important to do things right, while the AS takes care of the
SHOULD NOT and MUST NOTs?

BTW, you don't seem to have mentioned one of my favourite bugs:
The illusion that all systems will handle comments of the form
(This is believed \(mistakenly\) to be a comment with a \) in it)

At least I've experienced bounce storms after some messages with
a weird number of parentheses, most quoted, within a message.

(According to RFC 822, the above should be legal, and so should
(((((Five))))) be - comments nest - but I certainly had a hard
time figuring out whether the example that hit me was unbalanced or not)

         Harald A

Ned Freed | 4 Apr 03:35 1995

Numbering error part five labelled as part three

Part five seems to have gone out with part three in the subject line.
My apologies.

				Ned

Ned Freed | 4 Apr 03:35 1995

New MIME draft -- part three

Here is an updated version of the MIME specification. This version reflects a
major technical change: In response to IESG concerns about document size and
flexibility, the MIME specification has been broken up into five documents:

(1) Internet message bodies.
(2) Media types.
(3) Conformance and examples.
(4) Character sets in headers.
(5) Registration procedures.

This message contains part five of the updated specification.

Note for Internet-Drafts: The file name used here reflects the working group
that developed this specification, ietf-822. This group is no longer active.
I don't know whether or not it is appropriate to change the group to mailext.
If so, please do so and let me know so I can update the documents accordingly.

                                Ned

Network Working Group                         John Postel, ISI
Internet Draft                             Ned Freed, Innosoft
                           <draft-ietf-822ext-mime-reg-00.txt>

            Multipurpose Internet Mail Extensions
                      (MIME) Part Five:

                   Registration Procedures

(Continue reading)

Ned Freed | 4 Apr 03:33 1995

New MIME draft -- part three

Here is an updated version of the MIME specification. This version reflects a
major technical change: In response to IESG concerns about document size and
flexibility, the MIME specification has been broken up into five documents:

(1) Internet message bodies.
(2) Media types.
(3) Conformance and examples.
(4) Character sets in headers.
(5) Registration procedures.

This message contains part three of the updated specification.

Note for Internet-Drafts: The file name used here reflects the working group
that developed this specification, ietf-822. This group is no longer active.
I don't know whether or not it is appropriate to change the group to mailext.
If so, please do so and let me know so I can update the documents accordingly.

                                Ned

Network Working Group                     Nathaniel Borenstein
Internet Draft                                       Ned Freed
                           <draft-ietf-822ext-mime-conf-00.txt>

            Multipurpose Internet Mail Extensions
                      (MIME) Part Three:

              Conformance Criteria and Examples

(Continue reading)

Ned Freed | 4 Apr 03:25 1995

New MIME draft -- part one

Here is an updated version of the MIME specification. This version reflects a
major technical change: In response to IESG concerns about document size and
flexibility, the MIME specification has been broken up into five documents:

(1) Internet message bodies.
(2) Media types.
(3) Conformance and examples.
(4) Character sets in headers.
(5) Registration procedures.

This message contains part one of the updated specification.

Note for Internet-Drafts: The file name used here reflects the working group
that developed this specification, ietf-822. This group is no longer active.
I don't know whether or not it is appropriate to change the group to mailext.
If so, please do so and let me know so I can update the documents accordingly.

				Ned


Network Working Group                     Nathaniel Borenstein
Internet Draft                                       Ned Freed
                           <draft-ietf-822ext-mime-imb-02.txt>

            Multipurpose Internet Mail Extensions
                       (MIME) Part One:

              Format of Internet Message Bodies
(Continue reading)

Ned Freed | 4 Apr 03:31 1995

New MIME draft -- part two

Here is an updated version of the MIME specification. This version reflects a
major technical change: In response to IESG concerns about document size and
flexibility, the MIME specification has been broken up into five documents:

(1) Internet message bodies.
(2) Media types.
(3) Conformance and examples.
(4) Character sets in headers.
(5) Registration procedures.

This message contains part two of the updated specification.

Note for Internet-Drafts: The file name used here reflects the working group
that developed this specification, ietf-822. This group is no longer active.
I don't know whether or not it is appropriate to change the group to mailext.
If so, please do so and let me know so I can update the documents accordingly.

                                Ned

Network Working Group                     Nathaniel Borenstein
Internet Draft                                       Ned Freed
                           <draft-ietf-822ext-mime-imt-00.txt>

            Multipurpose Internet Mail Extensions
                       (MIME) Part Two:

                         Media Types

(Continue reading)

MARKJOSEPH | 4 Apr 20:50 1995

MIME question


Can the following header:

Content-Type: multipart/mixed; boundary="abcedfghiu"

be folded in the following way:

content-type: multipart/mixed; bounary="abced
 fghiu"

That is to say can the value in parameter"="value be 
folded ?

Same question applies to a header like:

Content-Type: message/partial;
  id="abced
 fghiu"

Mark Joseph
The Wollongong Advanced Applications Center
Santa Cruz, CA.

Dave Crocker | 5 Apr 15:44 1995
Picon

Re: MIME question

At 6:50 PM 4/4/95, MARKJOSEPH <at> delphi.com wrote:
>be folded in the following way:
>
>content-type: multipart/mixed; bounary="abced
> fghiu"

        No.  You may only break at word-type boundaries.  (I don't remember
the specific BNF rule name.)

d/

--------------------
Dave Crocker
Brandenburg Consulting                                  +1 408 246 8253
675 Spruce Dr.                                    fax:  +1 408 249 6205
Sunnyvale, CA  94086                       dcrocker <at> mordor.stanford.edu

John Gardiner Myers | 5 Apr 15:23 1995
Picon

Content-MD5

It is long been time to move RFC 1544 to Draft Standard status.  I
would appreciate if implementors of the Content-MD5 header would
contact me.

Also, if anyone believes the text of 1544 needs to change before
advancing, please contact me.

--

-- 
_.John G. Myers		Internet: jgm+ <at> CMU.EDU
			LoseNet:  ...!seismo!ihnp4!wiscvm.wisc.edu!give!up

Ned Freed | 5 Apr 16:31 1995

Re: MIME question


> Can the following header:

> Content-Type: multipart/mixed; boundary="abcedfghiu"

> be folded in the following way:

> content-type: multipart/mixed; bounary="abced
>  fghiu"

> That is to say can the value in parameter"="value be
> folded ?

Technically the answer is no, it can't. RFC822 allows breaks only at LWSP,
and the syntax of the boundary parameter doesn't include any.

However, since there are cases of very broken header folding out there I
strongly recommend that you implement something sensible to accomodate this
case.

> Same question applies to a header like:

> Content-Type: message/partial;
>   id="abced
>  fghiu"

Same answer.

				Ned

(Continue reading)


Gmane