At Tue, 04 Mar 2008 22:44:01 +0200, Aki Niemi wrote: > > > On ti, 2008-03-04 at 12:20 -0800, ext Eric Rescorla wrote: > > > Then I'd appreciate any suggestion to make it clearer. > > > > Explicitly state that in the case I described that it's permissible > > to deliver the same Etag in the first and third versions. > > Something like in S 5.3: > > The subscriber MUST be > prepared to receive a NOTIFY with any entity-tag value, including a > value that matches any previous value that the subscriber might have > seen.
Yeah, I don't think that's at all clear. For all I know, that could mean the server is running in a VM and was rolled back. > > > > Given that when I asked this question I got two different answers from > > > > Dale and Dean, I submit that the draft might be improved by directly > > > > addressing this point. Note that I don't care about the resolution, > > > > but I do care that the draft be unambiguous. > > > > > > Can you point out the unambiguity? > > > > I think Dean did a good job with that, namely that one could > > view "versions" as instances, and that two versions with > > different content are different versions and so need > > different Etags. > > That's exactly what the model already says. Sorry, that should have said "the same content". > Your original question was whether "A" and "A" could have the same etag. > According to the draft, yes. But I don't think that's clear as you seem to think it is. > ALso according to the draft, if you decided > to give them a different etag, fine. Nothing would break. Everything > would work exactly the same way. > > I'm apparently missing what practical problem the draft is not > addressing. I'm not saying there's a practical problem the draft is not addressing. I'm saying the draft isn't unambiguous and it's simple to make it so. -Ekr _______________________________________________ Sip mailing list https://www.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use [EMAIL PROTECTED] for questions on current sip Use [EMAIL PROTECTED] for new developments on the application of sip
