> Raj Singh writes: >> Section 5. IANA Considerations can be reworded in-line with >> ikev2bis. > > It would be better align it with ikev2-parameters iana registry. > >> 5. IANA Considerations >> >> IANA has already registered the type and value for AES-CTR. >> >> Name Number Defined In >> -------------------------------------------- >> >> ENCR_AES_CTR 13 (RFC3686 >> <http://tools.ietf.org/html/rfc3686>) > > I.e. correct line to be put to the IANA registry will be: > > > Number Name ESP Reference IKEv2 Reference > ------------ --------------------- ------------- --------------- > 13 ENCR_AES_CTR [RFC3686] [RFC<this rfc>] > > > I.e this document change sthe IKEv2 Reference column of the > Transform Type 1 - Encryption Algorithm Transform IDs iana table for > number 13 - ENCR_AES_CTR from "-" to refer this document instead.
If we need to give clear expression of what a IANA reference should be, I believe the iana registry is the proper format as showed above (also at http://www.iana.org/assignments/ikev2-parameters). Sean _______________________________________________ IPsec mailing list IPsec@ietf.org https://www.ietf.org/mailman/listinfo/ipsec
