RE: [Ipsec] Important changes in draft-hoffman-rfc3664bis; please review

Earlier today I wrote:

>   "The only algorithms defined in this document that accept
>   attributes are the AES based encryption, integrity, and
>   pseudo-random functions, which require a single attribute
>   specifying key width."
>
> Only ENCR_AES_CBC and ENCR_AES_CTR accept different key lengths; 
> and since there's no specified default key length, the key length
> attribute MUST be included.

...except that RFC3602 actually does include a sentence saying 
"The default key size is 128 bits". However, it later talks about
negotiating this in IKEv1:

   Since the AES allows variable key lengths, the Key Length attribute
   MUST be specified in both a Phase 1 exchange [IKE] and a Phase 2
   exchange [DOI].

And since the IKEv2 draft also uses the word "require", I think the 
default value mentioned in RFC3602 was intended as a configuration
hint, and does not imply that sending the Key Length attribute
would be optional. 

(More stuff for the IKEv2 clarifications draft, it seems :-)

Best regards,
Pasi

_______________________________________________
Ipsec mailing list
Ipsec@ietf.org
https://www1.ietf.org/mailman/listinfo/ipsec