Thanks, Murray, for the clarification. Matthias, are we good to go ahead with 
the document?

Thomas, let me know when you have uploaded the -16 version of the document.

Cheers.

> On Jan 14, 2025, at 9:55 PM, Murray S. Kucherawy <superu...@gmail.com> wrote:
> 
> The description of the "Interoperability Considerations" field of the media 
> types registration template is defined in RFC 6838 thus:
> 
>       Any issues regarding the interoperable use of types employing this
>       structured syntax should be given here.  Examples would include
>       the existence of incompatible versions of the syntax, issues
>       combining certain charsets with the syntax, or incompatibilities
>       with other types or protocols.
> 
> In response to this, the draft simply says:
> 
>       The format is designed to be broadly interoperable.
> 
> To me, this looks like you're being asked "What interoperability problems 
> exist that you know of?" and the answer is "We designed this to work 
> everywhere."  It's not quite answering the question, and that's why I raised 
> a concern.  If you have thought through questions of protocol 
> incompatibilities, character sets, version incompatibilities, etc., as in the 
> definition and are reasonably sure there aren't any, you can simply say 
> "None" or "N/A", or if you come up with some possible issues, describe them 
> here.
> 
> Hope this helps,
> 
> -MSK
> 
> On Tue, Jan 14, 2025 at 7:51 AM Mahesh Jethanandani <mjethanand...@gmail.com 
> <mailto:mjethanand...@gmail.com>> wrote:
> Thanks Thomas for working on the comments.
> 
> There is one particular comment from Murray on “Interoperability 
> considerations” as part of the registration request. Has that been addressed? 
> I did not see a response to his review, and I have not seen a change in text. 
> Murray, do you think you could help guide authors on what you think the 
> template is looking for?
> 
> Cheers.
> 
>> On Jan 14, 2025, at 5:36 PM, Werner, Thomas <thomas-wer...@siemens.com 
>> <mailto:thomas-wer...@siemens.com>> wrote:
>> 
>> Just uploaded: draft-ietf-anima-jws-voucher-15
>> this addresses the remaining COMMENTs provided as part of the telechat and 
>> mailing list.
>>  
>> Thanks, and regards!
>> Thomas
>>  
>>  
>> Von: internet-dra...@ietf.org <mailto:internet-dra...@ietf.org> 
>> <internet-dra...@ietf.org <mailto:internet-dra...@ietf.org>>
>> Datum: Dienstag, 14. Januar 2025 um 12:49
>> An: i-d-annou...@ietf.org <mailto:i-d-annou...@ietf.org> 
>> <i-d-annou...@ietf.org <mailto:i-d-annou...@ietf.org>>
>> Cc: anima@ietf.org <mailto:anima@ietf.org> <anima@ietf.org 
>> <mailto:anima@ietf.org>>
>> Betreff: [Anima] I-D Action: draft-ietf-anima-jws-voucher-15.txt
>> 
>> Internet-Draft draft-ietf-anima-jws-voucher-15.txt is now available. It is a
>> work item of the Autonomic Networking Integrated Model and Approach (ANIMA) 
>> WG
>> of the IETF.
>> 
>>    Title:   JWS signed Voucher Artifacts for Bootstrapping Protocols
>>    Authors: Thomas Werner
>>             Michael Richardson
>>    Name:    draft-ietf-anima-jws-voucher-15.txt
>>    Pages:   17
>>    Dates:   2025-01-14
>> 
>> Abstract:
>> 
>>    This document introduces a variant of the RFC8366 voucher artifact in
>>    which CMS is replaced by the JSON Object Signing and Encryption
>>    (JOSE) mechanism described in RFC7515.  This supports deployments in
>>    which JOSE is preferred over CMS.  In addition to specifying the
>>    format, the "application/voucher-jws+json" media type is registered
>>    and examples are provided.
>> 
>> The IETF datatracker status page for this Internet-Draft is:
>> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-ietf-anima-jws-voucher%2F&data=05%7C02%7Cthomas-werner%40siemens.com%7C500b1ec792ad4200ff5108dd349173a7%7C38ae3bcd95794fd4addab42e1495d55a%7C1%7C0%7C638724521501880129%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=3rKRtMREFclnaRRT59eYURerQPLvxgnG%2FvUr9GUyOkU%3D&reserved=0
>>  <https://datatracker.ietf.org/doc/draft-ietf-anima-jws-voucher/>
>> 
>> There is also an HTML version available at:
>> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Farchive%2Fid%2Fdraft-ietf-anima-jws-voucher-15.html&data=05%7C02%7Cthomas-werner%40siemens.com%7C500b1ec792ad4200ff5108dd349173a7%7C38ae3bcd95794fd4addab42e1495d55a%7C1%7C0%7C638724521501899468%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=EHdRgfmMB7U1tG8QFI4zvK0YtvBYBr9CnggHgGt86xY%3D&reserved=0
>>  <https://www.ietf.org/archive/id/draft-ietf-anima-jws-voucher-15.html>
>> 
>> A diff from the previous version is available at:
>> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fauthor-tools.ietf.org%2Fiddiff%3Furl2%3Ddraft-ietf-anima-jws-voucher-15&data=05%7C02%7Cthomas-werner%40siemens.com%7C500b1ec792ad4200ff5108dd349173a7%7C38ae3bcd95794fd4addab42e1495d55a%7C1%7C0%7C638724521501911051%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=Fm3x%2BuAA9HSoTQm%2BLAym3DbnYdeH7F5UcIbaH73iC8I%3D&reserved=0
>>  <https://author-tools.ietf.org/iddiff?url2=draft-ietf-anima-jws-voucher-15>
>> 
>> Internet-Drafts are also available by rsync at:
>> rsync.ietf.org <http://rsync.ietf.org/>::internet-drafts
>> 
>> 
>> _______________________________________________
>> Anima mailing list -- anima@ietf.org <mailto:anima@ietf.org>
>> To unsubscribe send an email to anima-le...@ietf.org 
>> <mailto:anima-le...@ietf.org>
> 
> Mahesh Jethanandani
> mjethanand...@gmail.com <mailto:mjethanand...@gmail.com>
> 
> 
> 
> 
> 
> 


Mahesh Jethanandani
mjethanand...@gmail.com






_______________________________________________
Anima mailing list -- anima@ietf.org
To unsubscribe send an email to anima-le...@ietf.org

Reply via email to