No subject

ssilvy at HSS.HNS.COM ssilvy at HSS.HNS.COM
Fri Jun 1 00:26:10 EDT 2001


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.


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

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


---------------------- 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)


 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
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.

Manoj Paul.

For help on this mail list, send "HELP ITU-SG16" in a message to
listserv at

For help on this mail list, send "HELP ITU-SG16" in a message to
listserv at

More information about the sg16-avd mailing list