XPost: news.software.readers   
   From: oneingray@gmail.com   
      
   >>>>> Shmuel (Seymour J ) Metz  writes:   
   >>>>> Ivan Shmakov  said:   
      
    >>> While RFC 3977 provides an 8 bit transport mechanism, RFC 5536 does   
    >>> not permit un-encoded non-ASCII data.   
      
    >> Somehow, I fail to find such a prohibition there.  Could you please   
    >> quote the relevant part thereof?   
      
    > RFC 5536:   
      
    > 2.1.  Base   
      
    > An article is said to be conformant to this specification if it   
    > conforms to the format specified in Section 3 of [RFC5322] and to the   
    > additional requirements of this specification.   
      
    > RFC 5322   
      
   [...]   
      
    > Note: This document specifies that messages are made up of characters   
    > in the US-ASCII range of 1 through 127.  There are other documents,   
    > specifically the MIME document series ([RFC2045], [RFC2046],   
    > [RFC2047], [RFC2049], [RFC4288], [RFC4289]), that extend this   
    > specification to allow for values outside of that range.  Discussion   
    > of those mechanisms is not within the scope of this specification.   
      
   	ACK, thanks!   
      
   	... Thus, the real question is if by referencing this section   
   	RFC 5536 also effectively "inherits" the note above.   
      
   	(The other option is, obviously, that RFC 5536 fails to document   
   	the existing practice.)   
      
   [...]   
      
   --   
   FSF associate member #7257	http://hfday.org/   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)