Re: [VCARDDAV] AD review of draft-ietf-vcarddav-carddav-07.txt

[Alexey Melnikov <[e-mail]>]

Cyrus Daboo wrote:

> Hi Alexey,

Hi Cyrus,
All your changes (but one, see below) look good to me.

> --On August 17, 2009 12:02:08 AM +0100 Alexey Melnikov 
> <[e-mail]> wrote:

 [...]

>> 3.  Requirements Overview
>>
>>    o  MUST support secure transport as defined in [RFC2818] using TLS
>>       [RFC5246];
>>
>> This recently came up in review of
>> draft-ietf-geopriv-http-location-delivery-15.txt:
>>
>> RFC 2818, Section 3.1 says:
>>
>>   Matching is performed using the matching rules specified by
>>   [RFC2459].  If more than one identity of a given type is present in
>>   the certificate (e.g., more than one dNSName name, a match in any one
>>   of the set is considered acceptable.) Names may contain the wildcard
>>   character * which is considered to match any single domain name
>>   component or component fragment. E.g., *.a.com matches foo.a.com but
>>   not bar.foo.a.com. f*.com matches foo.com but not bar.com.
>>
>> Based on the discussion during an IESG telechat several ADs agreed that
>> f* wildcards shouldn't be allowed anymore. So, the document should say
>> that it complies with RFC 2818, except for f* type wildcards are not
>> allowed. (wildcards in the leftmost label are still allowed). This is
>> consistent with the advice from RFC 5280.
>>
>>
>> I also think this document should reference RFC 5280.
>
> I have changed the text to:
>
>   o  MUST support secure transport as defined in [RFC2818] using TLS
>      [RFC5246] and using the certificate validation procedures
>      described in [RFC5280];
>
> Is that sufficient?

I will reply to this separately. The short answer is that it is better, 
but not sufficient. However I don't consider this issue to be blocking 
as far as IETF LC is concerned.
 [...]

> I have just posted draft -08 that contains all the changes listed 
> here. Hopefully this is now ready for IESG last call?

I didn't hear answer to my main question: why is this document requiring 
support for vCard 3.0 and not for vCard 4.0?