Re: Comments: draft-ietf-vpim-vpimdir-09.txt

Hi Greg,

Thanks for the fixes.
In regards to the others... suppose your comments are fair enough, I'm 
just a directory person, looking at it from a directory and schema 
completeness point of view.
If you don't think that the substring matching rules have a real purpose 
within the environment that this schema will be used in, thats okay. 
Just throwing the idea out there, because they're not hard to include 
and may make someones life easier down the track :)

Regards,
Andrew.

Vaudreuil, Greg M (Greg) wrote:
> Comments below.  I appologise for the delay responding.  
> 
> Greg V.
> 
> -----Original Message-----
> From: Andrew Sciberras [mailto:[email protected]]
> Sent: Wednesday, February 02, 2005 7:55 PM
> To: [email protected]
> Subject: [vpim] Comments: draft-ietf-vpim-vpimdir-09.txt
> 
> 
> Hi Greg,
> 
> I just have a few comments to make about this draft, which mainly relate 
> to the inclusion of additional matching rules into the Attribute 
> definitions. I've only recently joined this list, so please excuse me if 
> these topics have been discussed before.
> 
> 
>>3.1 vPIMTelephoneNumber 
>>...
>>(IANA-ASSIGNED-OID.2.1 NAME 'vPIMTelephoneNumber' 
>>                           EQUALITY caseIgnoreMatch 
>>                           SYNTAX 1.3.6.1.4.1.1466.115.121.1.44 ) 
> 
> 
> Based on the nature of this attribute, it probably wouldn't hurt to 
> include a substrings matching rule of caseIgnoreSubstringsMatch. This 
> would enable operatins such as: "Searching for all phone numbers with a 
> sub address of 12", to be possible.
> 
> GV: I don't see any value to matching on a subaddress.  Since this is a high transaction-rate query, I don't believe the added query complexity of the query is worth it.
> 
> 
> 
>>  3.5 vPIMSupportedAudioMediaTypes 
>>       ...
>>
>>       (IANA-ASSIGNED-OID.2.5 NAME 'vPIMSupportedAudioMediaTypes' 
>>                         EQUALITY caseIgnoreIA5Match 
>>                         SYNTAX 1.3.6.1.4.1.1466.115.121.1.26 ) 
>>
>>
>>       The allowable values of DirectoryString for this attribute are 
>>       the MIME audio subtypes registered with IANA. 
> 
> 
> Your comment suggests that the Syntax of this attribute is a 
> DirectoryString, however the OID and matching rule indicate an IA5String.
> 
> GV:  I will fix the text to affirm this is a IA5 string.  I also changed vPIMExtendedAbsenceStatus and vPIMSupportedUABehaviors to be IA5 String for consistency.
> 
> 
> 
> 
>>(From 3.5) Non-standard and
>>       private encoding types must be indicated by prepending the new 
>>       type name with either "X-" or "x-". 
> 
> 
> With the inclusion of non-standard information it may be worth adding a 
> substrings matching rule. This may come in handy for directory 
> administrators attempting to identify all entries that contains 
> non-standard information.
> Note: This could also apply to section 3.8 as well.
> 
> GV: I would like to hear others support before making this change.
> 
> Greg V.
> 
> _______________________________________________
> VPIM mailing list
> [email protected]
> https://www1.ietf.org/mailman/listinfo/vpim
> 


_______________________________________________
VPIM mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/vpim