Re: [apps-discuss] apps-team review of draft-ietf-sidr-ghostbusters-09

[Randy Bush <[e-mail]>]

>>> NEW
>>>   Per [RFC6350], the BEGIN, VERSION, FN, N, and END properties MUST be
>>>   included in a record.  To be useful, one or more of ADR, TEL, and
>>>   EMAIL MUST be included.  Other properties MUST NOT be included.
>>
>> Actually vcard does not require the N property to be present, only VERSION
>> and FN in addition to BEGIN/END (as per
>> <http://tools.ietf.org/html/rfc6350#section-3.3>).
>> Note: vcard v3 used to require that N was present, but that requirement was
>> dropped in vcard v4.

i will probably drop unless you can explain to me the value it adds.

>> The "Other types MUST NOT be included." is perhaps a little strong. I can
>> certainly see situations where it might be useful to have other properties
>> such as SOURCE, KIND or REV present. Perhaps that can be changed to a
>> "SHOULD NOT"?
> 
> It seems clear from the SIDR doc that they very much *want* a MUST
> NOT.  For their use case, it's not too strong; it's exactly what they
> want in order to keep this record simple.  They could certainly extend
> this later, allowing additional properties if such turn out to make
> sense for their use case.

'zactly

we want to be brutally minimalist.

randy