I noticed that the annex to H.225.0v2 on gatekeeper discover using DNS refers several times to DNS "SVR" records. But when I look at RFC 2052 where these are defined (see http://ds.internic.net/rfc/rfc2052.txt), they are called "SRV" records. Am I looking at the right thing? If so, this is a typo that should be corrected before publication.

Should H.225.0v2 include RFC 2052 as a reference?

Has anyone yet applied to IANA to register "ras" as a service name?

Also, I read with interest ftp://ietf.org/internet-drafts/draft-ietf-svrloc-discovery-05.txt, which suggests using "Service URLs" in TXT records as a fallback when SRV lookup fails. This differs from (although it is very close to) the format of RAS information in TXT records currently contained in H.225.0v2. Of course, this is just a draft, and I have no idea how well it was received in IETF, but if it gets legs, we may want to also add support for RAS URLs in TXT records via the H.323v2 Implementor's Guide. Regardless, it would be helpful to include a pointer to this draft -- or even an H.323-specific modified version of it -- in the Implementor's Guide to help people get gatekeeper discovery via DNS correctly implemented.

-- Toby ___________________________________________________________ Toby Nixon, Program Manager - NetMeeting http://www.microsoft.com/netmeeting Microsoft Corporation, Applications and Internet Client Group, Redmond WA USA +1 (425) 936-2792 Fax: +1 (425) 936-7329 mailto:tnixon@microsoft.com