List-Header Digest Archive: September 1997

http://www.nisto.com/list-spec/mail/

X-List-Help: <http://www.nisto.com/listspec/mail/>, <mailto:list-header-request@list.nisto.com?Subject=help>
X-List-Unsubscribe: <mailto:list-header-request@list.nisto.com?Subject=unsubscribe>
X-List-Subscribe: <mailto:list-header-request@list.nisto.com?Subject=subscribe>
X-List-Archive: <http://www.nisto.com/listspec/mail/#Digest>
X-List-Post: <mailto:list-header@list.nisto.com>
X-List-Owner: <mailto:listmom@list.nisto.com?Subject=List-Header%20List>

Contents:

-> required changes to the list-header internet draft
     by Grant Neufeld <(suppressed)@achilles.net>
-> Registering list header fields
     by James Berriman <(suppressed)@frutiger.staffs.ac.uk>
-> Re: Registering list header fields
     by Grant Neufeld <(suppressed)@achilles.net>
-> Re: required changes to the list-header internet draft 
     by Keith Moore <(suppressed)@cs.utk.edu>
-> Re: Registering list header fields 
     by Keith Moore <(suppressed)@cs.utk.edu>
-> Re: Registering list header fields
     by Grant Neufeld <(suppressed)@achilles.net>
-> Re: Registering list header fields
     by James Berriman <(suppressed)@frutiger.staffs.ac.uk>


----------------------------------------------------------------------

Date: 24 Sep 1997 17:53:19 -0400
From: Grant Neufeld <(suppressed)@achilles.net>
Subject: required changes to the list-header internet draft

[I'm back in (partial) action after another hiatus due to other obligations]

As part of the IETF review process, the following clarifications /
additions / changes are being required before we can progress to RFC:


RFC 822 Comments support.

Basically, this means that we must handle the presence of a semi-colon in a
List- header field and treat the semi-colon and all subsequent characters
in the field as a comment.


Clear definition as a "structured header field". "That permits free
insertion of linear-white-space between tokens."


"MIME encoded-words and 8-bit content is not permitted within the URLs."


The security issues in RFC 1738 (on URLs) are relevant to the List- header
fields.


Supporting the List- header fields "does not remove the requirement to
support the '-request' convention as described in RFC 2142."


Multiple occurrances of the individual List- header fields within a single
message header is not permitted.


I'm working on integrating these into a new (and hopefully final) draft.

- --
grant@achilles.net  grant@kagi.com  http://arpp.carleton.ca/  O-  <*>
PGP 5: 4077 8306 9115 94B0 CEA6  F4F4 3B9A 9482 D158 7B9A


----------------------------------------------------------------------

Date: 25 Sep 1997 11:53:19 -0400
From: James Berriman <(suppressed)@frutiger.staffs.ac.uk>
Subject: Registering list header fields

I had a look at this:

>Network Working Group                                 Jacob Palme
>Internet Draft                   Stockholm University/KTH, Sweden
>draft-ietf-drums-MHRegistry-00.txt                   January 1997
>Category: Informational                       Expires August 1997
>
>
>
>                  Mail Header Registration Procedure

Have any moves been made to register the List- headers under this
procedure, or does this happen automatically as part of the IETF process?

( :-])  James


----------------------------------------------------------------------

Date: 25 Sep 1997 14:21:22 -0400
From: Grant Neufeld <(suppressed)@achilles.net>
Subject: Re: Registering list header fields

At 11:39 AM -0400 9/25/97, James Berriman wrote:
>>Network Working Group                                 Jacob Palme
>>Internet Draft                   Stockholm University/KTH, Sweden
>>draft-ietf-drums-MHRegistry-00.txt                   January 1997
>>Category: Informational                       Expires August 1997

Current url for that draft (now revision 01) is:

  ftp://ftp.ietf.org//internet-drafts/draft-ietf-drums-MHRegistry-01.txt
  ftp://ftp.dsv.su.se/users/jpalme/draft-ietf-drums-MHRegistry-01.txt

>>                  Mail Header Registration Procedure
>
>Have any moves been made to register the List- headers under this
>procedure, or does this happen automatically as part of the IETF process?

I suspect that as an Internet-Draft (and hopefully soon an RFC) the List-
header fields would be registered. In any case, the registry isn't
finalized yet, so we'll have to wait until it is before we can do anything
about it.

Thanks for pointing this out (I wasn't aware of it).

- --
"Thanks for the nose-news, neighbor!" - Ned Flanders
grant@achilles.net  grant@kagi.com  http://arpp.carleton.ca/  O-  <*>


----------------------------------------------------------------------

Date: 25 Sep 1997 16:54:05 -0400
From: Keith Moore <(suppressed)@cs.utk.edu>
Subject: Re: required changes to the list-header internet draft 

> RFC 822 Comments support.
> 
> Basically, this means that we must handle the presence of a semi-colon in a
> List- header field and treat the semi-colon and all subsequent characters
> in the field as a comment.

Nope.  RFC 822 comments are indicated by parentheses, not by
semicolon.  Semicolon is used as a separator in several MIME header
fields.

example:

	To: moore (this is a comment) @cs.utk.edu

is a valid To header field

	To: moore@cs.utk.edu ; this is not a comment

is NOT a valid To header field.


> Clear definition as a "structured header field". "That permits free
> insertion of linear-white-space between tokens."

It also permits free insertion of comments between tokens.


Keith


----------------------------------------------------------------------

Date: 25 Sep 1997 16:54:20 -0400
From: Keith Moore <(suppressed)@cs.utk.edu>
Subject: Re: Registering list header fields 

> I suspect that as an Internet-Draft (and hopefully soon an RFC) the List-
> header fields would be registered. In any case, the registry isn't
> finalized yet, so we'll have to wait until it is before we can do anything
> about it.

Don't hold up the listspec draft for this. 

Once the registry draft is finalized (this could take awhile), any
headers that have already been defined in RFCs will be added to the
registry.

Keith


----------------------------------------------------------------------

Date: 25 Sep 1997 21:27:11 -0400
From: Grant Neufeld <(suppressed)@achilles.net>
Subject: Re: Registering list header fields

At 4:45 PM -0400 9/25/97, Keith Moore wrote:
>> I suspect that as an Internet-Draft (and hopefully soon an RFC) the List-
>> header fields would be registered. In any case, the registry isn't
>> finalized yet, so we'll have to wait until it is before we can do anything
>> about it.
>
>Don't hold up the listspec draft for this.

I guess I wasn't clear there. I meant that we shouldn't worry about the
header registry at this point because it doesn't exist yet. When it does,
the list- header fields will no doubt be added, regardless of our status as
draft or rfc at that time.

- --
grant@achilles.net  grant@kagi.com  http://arpp.carleton.ca/  O-  <*>
"If at first you don't succeed, kill all the evidence that you ever tried."


----------------------------------------------------------------------

Date: 26 Sep 1997 05:31:33 -0400
From: James Berriman <(suppressed)@frutiger.staffs.ac.uk>
Subject: Re: Registering list header fields

At 22:15 25/09/97, Grant Neufeld wrote:

>I guess I wasn't clear there. I meant that we shouldn't worry about the
>header registry at this point because it doesn't exist yet. When it does,
>the list- header fields will no doubt be added, regardless of our status as
>draft or rfc at that time.

Immediately after I posted my question, I noticed that Jakob Palme, author of

ftp://ftp.dsv.su.se/users/jpalme/draft-ietf-drums-MHRegistry-01.txt

is here on the list-header mailing list!

( :-])  James


----------------------------------------------------------------------

End of Digest