Julien ÉLIE | 1 Mar 23:54 2009

Charset in newgroup sample


Hi,

In the sample of newgroup control message:

      Control: newgroup example.admin.info moderated
      MIME-Version: 1.0
      Content-Type: multipart/mixed; boundary="nxtprt"
      Content-Transfer-Encoding: 8bit

      This is a MIME control message.
      --nxtprt
      Content-Type: application/news-groupinfo

      For your newsgroups file:
      example.admin.info      About the example.* groups (Moderated)

      --nxtprt
      Content-Type: text/plain

      A moderated newsgroup for announcements about new newsgroups in
      the example.* hierarchy.

      --nxtprt--

wouldn't it be better to put the charsets in order to highlight the
fact they are useful (though it is said the default is US-ASCII)?
I fear people might still forget it...

      Content-Type: multipart/mixed; boundary="nxtprt"; charset=us-ascii
(Continue reading)

Russ Allbery | 2 Mar 03:27 2009
Picon

Re: Charset in newgroup sample


Julien ÉLIE <julien <at> trigofacile.com> writes:

> In the sample of newgroup control message:
>
>      Control: newgroup example.admin.info moderated
>      MIME-Version: 1.0
>      Content-Type: multipart/mixed; boundary="nxtprt"
>      Content-Transfer-Encoding: 8bit
>
>      This is a MIME control message.
>      --nxtprt
>      Content-Type: application/news-groupinfo
>
>      For your newsgroups file:
>      example.admin.info      About the example.* groups (Moderated)
>
>      --nxtprt
>      Content-Type: text/plain
>
>      A moderated newsgroup for announcements about new newsgroups in
>      the example.* hierarchy.
>
>      --nxtprt--
>
> wouldn't it be better to put the charsets in order to highlight the
> fact they are useful (though it is said the default is US-ASCII)?

Yeah, probably a good idea.  I'll make that change.

(Continue reading)

rra | 2 Mar 03:28 2009
Picon

Commit in docs/usefor (usepro.xml)


    Date: Sunday, March 1, 2009  <at>  18:28:39
  Author: eagle
Revision: 5766

Clarify handling of <chksernr> and change the example to use YYYYMMDDNN.
Suggest string comparisons for potentially long serial numbers.

Modified:
  docs/usefor/usepro.xml

Modified: docs/usefor/usepro.xml
===================================================================
--- docs/usefor/usepro.xml	2009-03-01 22:43:59 UTC (rev 5765)
+++ docs/usefor/usepro.xml	2009-03-02 02:28:39 UTC (rev 5766)
 <at>  <at>  -1962,19 +1962,28  <at>  <at> 
           or sub-hierarchy with a smaller &lt;chksernr> value or with no
           &lt;chksernr> value.</t>

+          <t>There is no upper limit on the length of &lt;chksernr>
+          other than the limitation on the length of header fields.
+          Implementations may therefore want to do comparisons by
+          zero-padding the shorter of two &lt;chksernr> values on the
+          left and then doing a string comparison rather than assuming
+          &lt;chksernr> can be manipulated as a number.</t>
+
           <figure>
             <preamble>For example, the following Control header
             field</preamble>

(Continue reading)

rra | 2 Mar 03:32 2009
Picon

Commit in docs/usefor (usepro.xml)


    Date: Sunday, March 1, 2009  <at>  18:32:11
  Author: eagle
Revision: 5767

Add explicit charset attributes to the newgroup example to remind
readers to think about them.

Modified:
  docs/usefor/usepro.xml

Modified: docs/usefor/usepro.xml
===================================================================
--- docs/usefor/usepro.xml	2009-03-02 02:28:39 UTC (rev 5766)
+++ docs/usefor/usepro.xml	2009-03-02 02:32:11 UTC (rev 5767)
 <at>  <at>  -1884,13 +1884,13  <at>  <at> 

       This is a MIME control message.
       --nxtprt
-      Content-Type: application/news-groupinfo
+      Content-Type: application/news-groupinfo; charset=us-ascii

       For your newsgroups file:
       example.admin.info      About the example.* groups (Moderated)

       --nxtprt
-      Content-Type: text/plain
+      Content-Type: text/plain; charset=us-ascii

       A moderated newsgroup for announcements about new newsgroups in
(Continue reading)

Julien ÉLIE | 2 Mar 08:19 2009

Re: Charset in newgroup sample


Hi Russ,

>> wouldn't it be better to put the charsets in order to highlight the
>> fact they are useful (though it is said the default is US-ASCII)?
>
> Yeah, probably a good idea.  I'll make that change.

Thanks for your commit.

>> Content-Type: multipart/mixed; boundary="nxtprt"; charset=us-ascii
>
> As near as I can tell from RFC 2046, charset is not a valid parameter for
> multipart/* content types.  It's only supposed to go on the final
> constituent parts.  Among other things, this avoids...
>
>> In our case, the most important is the second one.  Incidentally,
>> I wonder what happens when the first one is defined to utf-8 and
>> the second one is undefined.  Is it utf-8 (out of transitivity)
>> or us-ascii?
>
> ...that problem.  :)

All right!  Thanks!

--

-- 
Julien ÉLIE

« There's a way of transferring funds that is even faster
  than electronic banking.  It's called marriage. » (Sam Kinison)
(Continue reading)

Julien ÉLIE | 2 Mar 20:00 2009

Re: Charset in newgroup sample


Hi,

>>      Content-Type: multipart/mixed; boundary="nxtprt"; charset=us-ascii
>
> As near as I can tell from RFC 2046, charset is not a valid parameter for
> multipart/* content types.  It's only supposed to go on the final
> constituent parts.  Among other things, this avoids...

I also see that RFC 2046 only accepts US-ASCII for the preamble of
a MIME message (I thought a charset for multipart/mixed would be useful
for it, but it is in fact useless):

    preamble := discard-text
    discard-text := *(*text CRLF) *text
    text = <any CHAR, including bare CR & bare LF, but NOT including CRLF>
    CHAR = <any ASCII character> ; (  0-177,  0.-127.)

It is therefore impossible to write "This is a MIME control message."
in Chinese.

    Control: newgroup example.admin.info moderated
    MIME-Version: 1.0
    Content-Type: multipart/mixed; boundary="nxtprt"
    Content-Transfer-Encoding: 8bit

    This is a MIME control message.
    --nxtprt

The parts are defined as:
(Continue reading)

rra | 3 Mar 21:14 2009
Picon

Commit in docs/usefor (Makefile usepro.xml)


    Date: Tuesday, March 3, 2009  <at>  12:14:49
  Author: eagle
Revision: 5775

Make draft-ietf-usefor-usepro-14.

Modified:
  docs/usefor/Makefile
  docs/usefor/usepro.xml

Modified: docs/usefor/Makefile
===================================================================
--- docs/usefor/Makefile	2009-03-03 04:00:37 UTC (rev 5774)
+++ docs/usefor/Makefile	2009-03-03 20:14:49 UTC (rev 5775)
 <at>  <at>  -1,7 +1,7  <at>  <at> 
 # Generate new text and HTML versions of the USEPRO document and copy them
 # somewhere reasonable on my web site.

-DRAFT = draft-ietf-usefor-usepro-13
+DRAFT = draft-ietf-usefor-usepro-14
 WEB   = /home/eagle/web/eagle/usefor/drafts

 all: text html

Modified: docs/usefor/usepro.xml
===================================================================
--- docs/usefor/usepro.xml	2009-03-03 04:00:37 UTC (rev 5774)
+++ docs/usefor/usepro.xml	2009-03-03 20:14:49 UTC (rev 5775)
 <at>  <at>  -28,7 +28,7  <at>  <at> 
(Continue reading)

rra | 3 Mar 21:22 2009
Picon

Commit in docs/usefor (usepro.xml)


    Date: Tuesday, March 3, 2009  <at>  12:22:52
  Author: eagle
Revision: 5777

Update the legal boilerplate.

Modified:
  docs/usefor/usepro.xml

Modified: docs/usefor/usepro.xml
===================================================================
--- docs/usefor/usepro.xml	2009-03-03 20:15:39 UTC (rev 5776)
+++ docs/usefor/usepro.xml	2009-03-03 20:22:52 UTC (rev 5777)
 <at>  <at>  -28,7 +28,7  <at>  <at> 
     'http://xml.resource.org/public/rfc/bibxml/reference.RFC.5234.xml'>
 ]>

-<rfc ipr="full3978" docName="draft-ietf-usefor-usepro-14" obsoletes="1036"
+<rfc ipr="trust200902" docName="draft-ietf-usefor-usepro-14" obsoletes="1036"
      category="std">
   <front>
     <title>Netnews Architecture and Protocols</title>

Internet-Drafts | 3 Mar 21:30 2009
Picon

I-D Action:draft-ietf-usefor-usepro-14.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Usenet Article Standard Update Working Group of the IETF.

	Title           : Netnews Architecture and Protocols
	Author(s)       : R. Allbery, C. Lindsey
	Filename        : draft-ietf-usefor-usepro-14.txt
	Pages           : 54
	Date            : 2009-03-03

This document defines the architecture of Netnews systems and
specifies the correct manipulation and interpretation of Netnews
articles by software which originates, distributes, stores, and
displays them.  It also specifies the requirements that must be met
by any protocol used to transport and serve Netnews articles.Internet
Draft Comments

Comments are solicited and should be addressed to the Usenet Format
Working Group at ietf-usefor <at> imc.org.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-usefor-usepro-14.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.
Attachment (draft-ietf-usefor-usepro-14.txt): message/external-body, 70 bytes
(Continue reading)

Harald Alvestrand | 11 Mar 13:00 2009
Picon

USEPRO document on IESG processing queue


Lisa has scheduled the USEPRO document for IESG discussion on April 2.
Let's hope this is the end of this work.

             Harald Alvestrand


Gmane