Paul Hoffman writes: > At 8:16 AM +0100 3/8/10, <Pasi.Eronen@xxxxxxxxx> wrote: > >Well, this depends on whether you think Section 1.7 should list > >textual changes in the document, or clarification/changes to the > >protocol. > > > >IMHO, it should be the latter, but I see that currently it's really > >listing the textual changes (even when they clearly don't have any > >impact on the protocol); so perhaps listing these separately is > >consistent with that... > > The problem with making this list more conceptual (as both you and > Tero have requested) is that doing so may help future implementers > but can miss context that is important to a current implementer who > needs to change their implementation. As an implementor I disagree with you on that. > In this particular example, we have one change that affects two very > different parts of the document, and someone who implemented by > reading RFC 4306 (instead of knowing it instinctively like you and > Tero) might really need to see exactly which bits *of the spec* are > changing to decide which bits of their code is changing. Yes that change changes two locations of the text, but only one location in the implementation. Thus for someone who is doing this change for their implementation it would be important to understand that this change is actually just one code change, not two. Also the change is most likely going to be in the policy enforing part than in the actual exchange handling code (1.3.2) or the SKEYSEED calculation part. The implementation simply needs to enforce the IKE SA rekey policy so that Diffie-Hellman is not optional and that is only change they need to do in the code. They already have to calculate the SKEYSEED (most likely with or without the g^ir (new)), and they already have the code to parse KEi and KEr (generic code). > I will try to come up with a way to cover the conceptual change as > well, but really am loath to remove the section references in the > change description. -- kivinen@xxxxxx _______________________________________________ Ietf mailing list Ietf@xxxxxxxx https://www.ietf.org/mailman/listinfo/ietf