Re: RFC5201-bis status

> -----Original Message-----
> From: hipsec-bounces@... [mailto:hipsec-bounces@...] On
> Behalf Of Henderson, Thomas R
> Sent: Monday, March 12, 2012 2:10 PM
> To: hipsec@...
> Subject: [Hipsec] RFC5201-bis status
>
> The new version of RFC5201-bis was just published at:
> http://www.ietf.org/internet-drafts/draft-ietf-hip-rfc5201-bis-08.txt
>
> This version had the following changes:
>
>    o  Removed lingering references to SHA-1 as the mandatory hash
>       algorithm (which was changed to SHA-256 in the -02 draft
> version).
>
>    o  For parameter type number changes, changed "IETF Review" to "IETF
>       Review or IESG Approval".
>
>    o  Updated Appendix C checksum examples to conform to HIPv2 packets.
>
> There remain nine open issues in the tracker for this draft:
> http://trac.tools.ietf.org/wg/hip/trac/query?component=rfc5201-bis
>
> I believe that three could be closed immediately as being already done,
> and I will plan to do so in a week if there are no comments:
>
> #18 Selection of 160-bit ECC curve
> #26 IESG: Randomize hashing in signatures
> #28 IESG: support combined encryption modes
>
> I believe that two can be closed with some brief list discussion (will
> open separate discussion threads):
>
> #30 Handle interactions with complex SPDs
> #32 normative text on when to have Domain Identifier