Paul Wouters writes: > On Thu, 25 Feb 2016, Tero Kivinen wrote: > > > It is notify from the server to client. I.e. client sends empty > > TIMEOUT_PERIOD_FOR_LIVENESS_CHECK in the CFG_REQUEST and server will > > send value in seconds inside its TIMEOUT_PERIOD_FOR_LIVENESS_CHECK in > > CFG_REPLY. I.e. the server asks client to use following livenss > > timeout period. > > Ok, then it should use NOTIFY and not CP.
That is my understanding too, but I do not really think this issue is big enough to require them to change their document, i.e., not to approve their IANA allocation request. > > If we could even get few paragraph explanation that would be really > > good, thats why I said it would be nice if 3gpp people would run their > > additions through this list before writing it in their draft. > > > > Now I have to check that 116 page document and find out what it is > > supposed to do :-) > > So this is a real problem. If we (implementors) want to implement these > IKEv2 extensions, we need to have clear proper RFC's. I do not want to > find 116 pages on third party websites (that may or may not be behind > a registration or pay wall) Most of that 116 pages is not related to the IKEv2 extensions, there is perhaps few tens of pages of IKEv2 related things in there. The documents can be downloaded from their web page, and as they do cover the 3gpp Evolved Packet Core (EPC) issues, I do not think they need to be RFCs. This is the reason why the IANA registries for IKEv2 are not RFC required... Anyways making suggestions like in the beginning of this email (i.e. use notify instead of configuration payload) is something that would be good to do before people define extensions to the IKEv2, and thats why I do encourage people to at least tell what they are doing, and why and how in the ipsec list while making the protocol, so we can give them hints and feedback how to do it properly. -- [email protected] _______________________________________________ IPsec mailing list [email protected] https://www.ietf.org/mailman/listinfo/ipsec
