RE: [OSPF] IETF 67 OSPF WG Meeting minutes - Correct file appended

["Manav Bhatia" <[e-mail]>]

Acee,

The minutes missed out my replies.

> Presentation: Manav Bhatia - Crypto Requirements Document

> NULL, MS5, sha1, cryptographic - refs in this doc 
>    more algorithms keep coming eg des was once must, now is should ot 
>	
>    What doc must, should, - running doc as algorithms come and go 
>    uses 2119 terms should+ = should may become must 
>		
>    See slides and draft for specific requirements. 
>		
>    Acee: "should not" wording is problematic for NULL and other 
>    existing requirements.  

Manav: NULL authentication is a "should NOT" in case an admin requires OSPF
security.

> Russ white: shold may become a must vs. should+ (better to say
> what is meant)

Manav: We have used these additional RFC2119 terms since the earlier
cryptographic implementation requirement RFCs 4305, 4307 have used a similar
language.

Cheers,
Manav    

> -----Original Message-----
> From: Acee Lindem [mailto:[e-mail]] 
> Sent: Monday, November 13, 2006 7:30 PM
> To: OSPF List
> Subject: [OSPF] IETF 67 OSPF WG Meeting minutes - Correct 
> file appended 
> 
> Here are the minutes from the 67th IETF OSPF WG meeting. Thanks
> to Steve Nadas from Ericsson for taking them.
> 
> There was quite a bit of dialog at the mike with respect to the
> OSPF MANET direction. I've also appended Thomas Clausen's
> jabber log. Please unicast corrections to me. IETF 67
> 
> Please unicast any corrections to me.
> 
> Thanks,
> Acee
> 

Send instant messages to your online friends http://uk.messenger.yahoo.com 


_______________________________________________
OSPF mailing list
[e-mail]
https://www1.ietf.org/mailman/listinfo/ospf