RE: [OSPF] Revised OSPF HMAC SHA Authentication Draft

Yes,

If an authentication fails it could mean the algo's used are different.

And if one implementation supports MD5 alone( "which I believe is commonly
used !" ), the others

support otherwise, It could be a problem, there is no explicit way we are
converying which algo is being used.

The Au Type = 2 is overloaded.

Now a "MUST" clause is for the WG to decide.

Regds,
Sujay G
My Location;
http://maps.google.com/maps?ll=14.626109,76.959229
<http://maps.google.com/maps?ll=14.626109,76.959229&spn=4.724852,7.525085&t=
h&hl=en> &spn=4.724852,7.525085&t=h&hl=en

This e-mail and attachments contain confidential information from HUAWEI,
which is intended only for the person or entity whose address is listed
above. Any use of the information contained herein in any way (including,
but not limited to, total or partial disclosure, reproduction, or
dissemination) by persons other than the intended recipient's) is
prohibited. If you receive this e-mail in error, please notify the sender by
phone or email immediately and delete it! 

  _____  

From: Manav Bhatia [mailto:manav@riverstonenet.com] 
Sent: 2006年8月23日 13:04
To: 'sujay'
Cc: 'Mailing List'
Subject: RE: [OSPF] Revised OSPF HMAC SHA Authentication Draft

Sujay, 

> 
>Can we have a default algo. concept?? 
> 

What do you mean by the default algo? Is it one authentication algorithm
that all implementations MUST support? 

Manav 