H.323 (8.1) Phase A - Call Setup

Peter Price PeterP at VEGASTREAM.COM
Fri Jul 20 06:54:21 EDT 2001


Experts,

  Could someone clarify following aspects of H.235 V2 Annex D (Baseline Security Profile).
1) Section D.2, last but second paragraph (This profile defines to....). According
to this paragraph, the generalId field shall be set to the "called endpoint ID" for
H225 signalling messages. Since the calls must be GK routed, shouldn't the generalId
refer to the gkId for 225 messages sent by endpoints? Even if it is the called epId,
how the peer endpoint can ever know the called epId, since it does not appear ARQ/ACF
messages? Section D.10 throws some insight into the usage of senderId and generalId, but
it does it so only for RAS messages.

2) Section D.9.1 of H.235 V2 states the 225 UUIEs which shall contain cryptoTokens
field. H.323 V4 has added new UUIEs (Status, Status Enquiry,...). Does that mean
that H.323 V4 can not possibly use H.235 V2?

best regards
Manoj Paul.


-----Original Message-----
From: ssilvy at hss.hns.com [mailto:ssilvy at hss.hns.com]
Sent: Thursday, May 31, 2001 9:26 PM
To: mpaul at TRILLIUM.COM; ITU-SG16 at mailbag.cps.INTEL.COM
Subject: Re:





Hi,

In case of initial RRQ when EPID is not available the table D.10 in H235v2
says that sendersID would be NULL.
So the hash would be calculated with sendersID as NULL when the
identification information i.e EPID is not available as in initial RRQ.

Silvy.




Nagesh Kumar B V
06/01/2001 10:40 AM

To:   Silvy Samuel/HSSBLR at HSSBLR, Ivan T Varghis/HSSBLR at HSSBLR
cc:

Subject:


---------------------- Forwarded by Nagesh Kumar B V/HSSBLR on 06/01/2001
09:46 AM ---------------------------


"Paul, Manoj" <mpaul at TRILLIUM.COM> on 05/31/2001 06:35:31 PM

Please respond to "Paul, Manoj" <mpaul at TRILLIUM.COM>

To:   ITU-SG16 at mailbag.cps.INTEL.COM
cc:    (bcc: Nagesh Kumar B V/HSSBLR)

Subject:




 Hi All,

   I have a question on the use of H.235 Annex D (Baseline Security
Profile). According
to this profile, except for GRQ/GCF messages, all other RAS messages shall
contain a hash
value computed using HMAC-SHA1-96 algorightm on the entire RAS message.
Consider an
endpoint sending RRQ to the Gk. In the clearToken field of RRQ message, the
endpoint shall
fill generalId as gkId (which it got in GCF) and senderId as it's own epId.
EpId is
generally returned to the endpoint by the gatekeeper in RCF. That means
that
an endpoint
may not have an epId while sending RRQ to Gk. In such a case, how it is
supposed to
fill the senderId and compute the hash value on complete RRQ message?
Any pointers are appreciated.




thanks
Manoj Paul.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
For help on this mail list, send "HELP ITU-SG16" in a message to
listserv at mailbag.intel.com

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
For help on this mail list, send "HELP ITU-SG16" in a message to
listserv at mailbag.intel.com



More information about the sg16-avd mailing list