Re: [dtn] [EXT] draft-blanchet-dtn-email-over-bp-00.txt

[Marc Blanchet <[e-mail]>]

> Le 29 janv. 2023 à 22:43, Marc Blanchet <[e-mail]> a écrit :
> 
> 
>> Le 29 janv. 2023 à 17:26, Birrane, Edward J. <[e-mail]> a écrit :
>> 
>> 
>> My replies (prepended with EJB:) below.
>> 
>> -Ed
>> 
>> ---
>>> Attachments, encryption and signature of emails are all handled within the
>>> body of the email, so this is all included and working by RFC5322. I’ll add a
>>> note in the next rev.
>> 
>> EJB: RFC5322 Section 1.1 states "This document specifies a syntax only for text messages.  In  particular, it makes no provision for the transmission of images,  audio, or other sorts of structured data in electronic mail messages.".  Further, it seems that RFC6854 updates RFC5322 to allow group syntax in the From: and Sender: fields. 
> 
> Will look into RFC6854, but RFC5322 is really the master piece here.

Ok. I just read RFC6854. Yes, it is an appropriate update to RFC5322, but frankly, it is a very small update to a tiny portion of email. Not saying it is not appropriate or relevant, but I’m still not sure that it is the right thing to quote RFC6854 instead of RFC5322, as the latter really defines “everything” about email, and is the successor of our beloved RFC822 that we have been depending on for decades! An email developer looking to implement RFC5322 would certainly look at any of its updates. Encapsulation of email into BP is not that dependent on RFC6854.

So would you mind telling me what you want me to do with a ref to RFC6854?  

Marc.