[calsify] AD review of draft-ietf-calext-jscontact-vcard-06

[Francesca Palombini <[e-mail]>]

Thank you for this document.

No major comments from me, minor comments and readability suggestions which you can take or leave as you prefer. Please address them together with any other last call comments. Note that the Last call will be longer than 2 weeks because overlapping with IETF 116.

Francesca


1. -----

Section 2.

nit: s/Its follows/It follows

2. -----

> To preserve the verbatim value of the ALTID parameter, set the JSContact extension properties props or params defined in Section 2.16.

I guess I might find out later in 2.16, but how do implementers chose to use props or params?

3. -----

> To convert this parameter for other vCard properties, see Section 2.16.2.

There is a lot of repetition of the sentence above. For readability, it could be good to say it once generally in section 2.3 for example and not have it in each subsection.

4. -----

Section 2.6.5

Figure 11 is missing the vCards FN, N and NICKNAME properties.

5. -----

> ORG-DIRECTORY;PREF=1:ldap://ldap.tech.example/o=Example%20Tech,ou=Engineer

I expect this is only a formatting problem, but the end is cut (should be Engineering)
Same for the following:

> JSCONTACT-PROP;VALUE=TEXT;JSPTR="phones/phone1/example.com:foo~1bar":"tux

6. -----

Table 5: I would see this fitting an Appendix.

7. -----

I believe ietf-calext-vcard-jscontact-extensions and ietf-calext-jscontact should be normative references. Also 8174 needs to be normative.