Tero Kivinen <kivi...@iki.fi> wrote:
> Michael Richardson writes:
>> I was going through documents, and I was supprised that when we made
>> RFC7296 into STD79, that we didn't include RFC4301 into STD79. (and
>> maybe 4302 and 4303)
> The reason STD79 only has IKEv2 is because that was only thing that was
> needed. The reason we moved IKEv2 to internet standard was because
> certain contries suddenly said that they can't use IKEv2 because it is
> only proposed standard, and they said they can only use full interent
> standards, and then they proposed their own key exchange mechanisms.
Fair enough.
> IPsec architeture RFC4301 could and perhaps should have been included,
> but finding enough energy to work on it did not see feasible at the
> time.
> I think we do need to make new version of IPsec architecture RFC4301 if
> we want to move it to standard track, and this will require energy that
> we might not have.
I agree that it might be difficult, and I agree that we don't have the energy
*right now*
Mostly, it ought to be about crossing out words that turn out not to apply.
The problem is the reviewers then don't like 20+ year old language and want
changes, not really getting that we really don't want to do that.
> Moving ESP RFC4303 to internet standard most likely also requires new
> version of the document, but that should be much easier, and I do not
> see that document needing that many changes.
I will ask Carsten to turn 4301 and 4303 into Markdown, put them into a
github, and leave them like that for now.
Since we've agree to copy and paste to make ESPv3 (or whatever it is called),
then that ought to help with that work as well.
Is advancing to IS considered maintenance, or do we need more charter text?
I suggest we come back to this discussion at IETF124.
> I do not see point of making AH RFC4302 an internet standard. It is not
I would not advance 4302.
--
Michael Richardson <mcr+i...@sandelman.ca> . o O ( IPv6 IøT consulting )
Sandelman Software Works Inc, Ottawa and Worldwide
signature.asc
Description: PGP signature
_______________________________________________ IPsec mailing list -- ipsec@ietf.org To unsubscribe send an email to ipsec-le...@ietf.org
