- From: Mark Nottingham <mnot@mnot.net>
- Date: Fri, 28 Mar 2008 14:47:35 +1100
- To: "Frank Ellermann" <hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com>
- Cc: ietf-http-wg@w3.org
On 28/03/2008, at 2:08 PM, Frank Ellermann wrote: >> >> """ >> field-content = <field content> >> ; the OCTETs making up the field-value, >> ; consisting of either *TEXT or combinations >> ; of token, separators, quoted-string and encoded-word, >> ; according to the syntax specified by the field. >> """ > > Maybe not good enough, for an unstructured *TEXT field > you need 2047 chapter 5 clause (1), no problem. > > For a structured field you cannot permit encoded-word > as folks see fit, the structure must not be hidden by > encoding (parts of) it. Maybe the safest thing to do would be: field-content = <field content> ; the OCTETs making up the field-value, ; according to the syntax specified by the field. >> """ >> filename-parm = "filename" "=" quoted-string | encoded-word >> """ > > No 2231 folding here, might work. Please note somewhere > that 2231 updated <encoded-word> adding optional language > tags. Trying to forbid that could be bad. My first thought is just to add a reference to RFC2231 section 5, allowing that extension. >> Also, I haven't addressed From (p2, 10.3). Anybody want >> to take a stab at that? > > No Latin-1 in From. For starters s/2822/2822upd/ minus > the obsolete syntax in chapter 4 of 2822upd (trust me, > you don't want anything obs-* ;-) > > If you intend to evolve 2822upd From into some shrink > to fit 2047 MIME modulo 2231 forget it, only one person > ever tried to combine 2882 + MIME, he is not here, and > he started with not less than four I-Ds full of hardcore > ABNF (nobody needs any prose or examples if the syntax > is "obvious") Sounds like this should be punted to a separate issue... -- Mark Nottingham http://www.mnot.net/
Received on Friday, 28 March 2008 03:48:12 UTC