www-infrastructure-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Craig Russell <craig.russ...@oracle.com>
Subject Re: Adding a mail header to emails from our automation
Date Thu, 06 Oct 2016 17:59:27 GMT

> On Oct 6, 2016, at 7:07 AM, Alan Cabrera <list@toolazydogs.com> wrote:
> 
> 
>> On Oct 6, 2016, at 12:41 AM, Bertrand Delacretaz <bdelacretaz@apache.org> wrote:
>> 
>> Hi,
>> 
>> On Wed, Oct 5, 2016 at 11:52 PM, Alan Cabrera <list@toolazydogs.com> wrote:
>>> I was thinking that it would be handy to add
>>> X-asf-automation
>>> to the headers of the emails’ from our automation....
>> 
>> +1 but note that https://tools.ietf.org/html/rfc6648 deprecates the X-
>> prefix and recommends "assuming that all parameters that we create
>> might become public" and "using meaningful parameter names that we
>> have reason to believe are currently unused".
>> 
>> So org.apache.automation might be safer, with values like whimsy/1.4.2
>> to identify the source.
> 
> I was just talking to Fredrik Jonson about this as well.  It makes sense to me.  I was
thinking of something like:
> 
> org.apache.automation.event: urn:org:apache:automation:event:icla:received

What is the intended format of this line? The RFC you mention seems to deprecate the X- prefix,
but is it now ok to simply put anything you want to? Do email handlers simply skip unknown
headers now, or are there issues by not using the X- prefix?

> org.apache.automation.source: origin=whimsy,version=1.4.2

Seems clear enough.

> org.apache.automation.claim: 

What is a “claim” in this context? (I’m not an email RFC competent individual)

> eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJldmVudCI6InVybjpvcmc6YXBhY2hlOmF1dG9tYXRpb246ZXZlbnQ6aWNsYTpyZWNpZXZlZCIsInNvdXJjZSI6eyJvcmlnaW4iOiJ3aGltc3kiLCJ2ZXJpc29uIjoiMS40LjIifSwidXJuOm9yZzphcGFjaGU6Y2xhaW1zIjpbeyJ1cm46b3JnOmFwYWNoZTpjbGFpbTplbmNvZGluZzpqd3QiOiJleUpoYkdjaU9pSklVekkxTmlJc0luUjVjQ0k2SWtwWFZDSjkuZXlKbGRtVnVkQ0k2SW5WeWJqcHZjbWM2WVhCaFkyaGxPbUYxZEc5dFlYUnBiMjQ2WlhabGJuUTZhV05zWVRweVpXTnBaWFpsWkNJc0luQmxjbk52YmlJNklsWnNZV1JwYldseUlGWnZjMnR5WlhObGJuTnJlU0lzSW05eVoyRnVhWHBoZEdsdmJpSTZJazl5WVdOc1pTd2dTVzVqTGlJc0luSmxZMlZwZG1Wa0lqb2lNakF4TmpFd01EWlVNRFU2TkRZNk1qTmFJbjAubXNZbmtjR1VmOWZIcDREa2U2clpBTklJY21nVU5vUkE1eHUyU2RyRHV2ekozNVNUdjd2Mlpfa29DRUhucE1oS3dpYnROaE01Q0tFanRkTDc2c3llMUlUSUFkYS01d2w3dFNGdXFpNEg5c0dHaGJlaWJrdTFZci01QzluNDYxSV8zX1VuT3RJbnZOLVFQUmxUZVdXZ3N4clJ5Wm5iZ0w0czVMN1VydTFqRWdMNFI5T3I3N2VfVmJCRTN2bklkWmVYWElWRGFibDk2bVEwNmViRTNYaEZLSmtydlNGS0pUeThMaGh6N1l0RnpEMjF2aUFSemJqU0trWmwtS251TU9zZkR5VWs0MTRUNE5mNGJ3UHN3ZUxZVDhXR3RiNWxueUx0VFRvYnY5NXNIQzdrTWdXMXY0OG5mNFl5Sm1kS2wyZHFiaXlKdTM3cmJDQTZXSWJvVkk3NGJBIn1dfQ.E_2FDcMm2TwQwuFhZwBWbv0n-lj1T6NcRbgO0jd5eDzuLeFDoD7AJ9faL6n0W_FY8rqAkVE9BM4CJEefdQhw_0IGZT1GLHsquOuGGePy8obEchVIhljglzzan6X3tYKgqkely_6ZvBpEcglXBH1vDWTL4bvWyHRMSZ1pVsDJwS5VFufuwx33fzZLs6HFKtr6YoVrz9NZxd7mERVHrApHRgyXaxK9gnJ2y1BgRsL3CwbdQ1RKaHy4Cd64XBhU-XY1I_BvWqr3g0UJ1P_HFOWrsY1Q-drTxofL-8w_NvcVn-_bUxIJgCclpX-iIG95BCCY-bWRd6jSt96b5_QEHCu18Q
> 
> Various events I can think of so far would be:
> 
> urn:org:apache:automation:event:icla:received

What is an “urn”?

> urn:org:apache:automation:event:account:requested
> urn:org:apache:automation:event:account:created
> 
> I envision that whimsy would be extended to send multi-mime automation messages that
would contain:
> 
> text/plain
> text/html
> application/vnd.apache.automation+xml
> 
> The last mime would allow automation to consume the emails without having to resort to
scraping text.
> 
> The header org.apache.automation.claim, a jwt claim, is used to verify the validity of
the message and the event it is delivering.

What process would consume these messages?

What is motivating this proposal?

Regards,

Craig

> Regards,
> Alan
> 
Craig L Russell
Secretary, Apache Software Foundation
clr@apache.org http://db.apache.org/jdo


Mime
View raw message