Re: [auth48] AUTH48: RFC-to-be 9555 <draft-ietf-calext-jscontact-vcard-13> for your review

[Robert Stepanek <[e-mail]>]

Hi Karen,

I'm not sure if you are waiting for our approval for RFC 9555? I am waiting for Editors to provide an updated document version for RFC 9555 with the changes I agreed to below, but maybe I have missed some email thread and you are waiting for some action on my behalf?

I can certainly apply the changes outlined below myself, should you prefer that.

Thanks,
Robert

On Fri, Apr 5, 2024, at 11:10 AM, Robert Stepanek wrote:
> Hi Karen, Orie,
> 
> On Thu, Apr 4, 2024, at 11:29 PM, Karen Moore wrote:
>> > [OS] Thanks for making this change, in case "text/vcard" is rejected (for some tooling reason) "text/plain" would also work... in fact it may be more appropriate if the source code is not a fully valid vcard in text serialization... Is it valid?
>> 
>> Additionally, we updated Section 2.3.17 with Orie’s suggested text; however, if further changes are desired by the authors, we are happy to make the update.
> 
> The examples contain only partial vCard text, so strictly speaking "text/vcard" is not appropriate. If that is an issue, "text/plain" is equally fine.
> 
>> 
>> > NEW:
>> >    The PREF parameter (Section 5.3 of [RFC6350]) converts to the pref
>> >    property of the derived JSContact object.
>> 
>> 
>> Please consider if any updates are needed to this similar sentence that follows in Section 2.3.18:
>> 
>>   The PROP-ID parameter (Section 4.7 of [RFC9554]) converts to the Id-
>>    typed key of the JSContact object, to which the vCard property having
>>    this parameter converts.
> 
> I think Orie's suggestion for the PREF parameter is great, and I kindly ask you to apply it also to the PROP-ID definition.
> 
> Thanks,
> Robert