Re: [Fwd]: 2822 implementation report request

Hi, I think we could answer this reqest, suggestion:

| RFC 2822 / 2822upd Implementation Questionnaire
| ===============================================
|      0. Contact and Description
|         Organization Name:
+ IETF USEFOR WG

|         Implementation (Software or Service) Name:
+ draft-ietf-usefor-usefor-12 (approved standards track RFC)

|      1. Have you implemented RFC2822?
+ Yes, the RFC 1036 format used to build on RFC 822, the
+ revides NetNews formats builds on RFC 2822 (normative
+ reference importing major parts of the RFC 2822 syntax)
 
|      2. For how long it has been deployed?
+ January 2007 

|      3. What features have NOT been implemented from RFC2822?
+ Chapter 4 (obsolete syntax), NO-WS-CTL in <msg-id>, 
+ [CFWS] in traditional NetNews header fields, more than
+ one summary header field (see appendix C of the draft)

|      4. What features of RFC2822 are problematic for your implementation?
+ With two exceptions the obsolete syntax is not supported.
+ NetNews header fields require a space after the colon
+ between header field name and body, and don't allow any
+ folding before the first non-WSP character of the header
+ field body.

|      5. Please add any other comments you wish to share:
+ The USEFOR WG welcomes the simplified <msg-id> syntax as
+ proposed in 2822upd.

 Frank