Hi Greg,

H.225.0 Annex G provides more than just address resolution. A short list of the functionality Annex G supports includes:

- support for different interdomain architectures (e.g., hierarchical, peer-to-peer, clearing house) - service relationships between domain (the interdomain security mechanisms are negotiated at the level of service relationships) - static and dynamic provisioning of address information - address resolution - usage information exchange - authorization of calls

Regarding your question about usage information, see the descriptions of the UsageSpec (1.8.2.4.5) and Pricing Information (1.8.2.3.2) structures, and the UsageRequest (1.8.2.25) and UsageIndication (1.8.2.28) messages (and the related confirmation and rejection messages) for more information.

Michael Fortinsky ----------------------------------------------------------------- Senior Program Manager, IP Telephony Group, VocalTec Communications Ltd. Email: mike@vocaltec.com Tel: 972 9 9707768 Fax: 972 9 9561867

Greg Herlein gherlein@HERLEIN.COM on 03/03/2000 03:39:00 PM

Please respond to Mailing list for parties associated with ITU-T Study Group 16 ITU-SG16@mailbag.cps.intel.com

To: ITU-SG16@mailbag.cps.intel.com cc: (bcc: Michael Fortinsky) Subject: H.225 Annex G

H.225 Annex G does not seem to have any meat - is it *just* a border information exchange mechanism, or is it intended to provide EDI the way OSP does (ie, exchanging usage information)?

From my review, this annex looks like it does not provide any AAA

functionality between administrative domains... though it does discuss address resolution. I'm looking at:

http://standard.pictel.com/ftp/avc-site/9905_San/H.225.0_Annex_G_990528.zip

Am I missing something, or is that all Annex G is supposed to do?

Greg

/************************************************************** Greg Herlein gherlein@herlein.com ***************************************************************/