Hi Randy, Thanks for this. > > > Since we include the 6.c.iii mumble, I have applied the > > noDerivatives200811 IPR directive. > > I do not think we want that, since that would hamstring attempts to > revised it in the future. I don't think that's entirely true. The IETF Standards Process is explicitly excluded from the derivative works text, at least in 6.c.iii. At the same time, 6.c.iii has an explicit no-derivatives section to it. IANAL, but since 6.c.iii prohibits derivatives, I don't see how I can check 'trust200811'?? Can I get guidance on this? In the meantime, I can remove the additional no-derivatives text and just use 6.c.iii. > ... > > I may need to move the 6.c.iii mumble into the copyright manually > before submission. > > I don't recall anyone saying exactly where the incantation needs > to go, but it would seem to make sense as the second paragraph > of the "Status of this Memo" section or as a third paragraph in > the copyright notice. Treating it as ordinary text before the > absract might cause XML2RFC to do the right thing. I'll try some permutations. My first attempt wasn't successful. > > Scanning the diffs, two potential problems jumped out at me: > - The text put in for issue #1 (which was cast as just > updating a reference) creates a technical change > - It looks issue #3's agreed text didn't get put in. > > PLEASE post followup on these two issues (or on any other issues) > in separate threads, including the issue number in the subject line. > Any response from me will be under separate cover... I have not looked at these issues as of yet. Addison Addison Phillips Globalization Architect -- Lab126 Internationalization is not a feature. It is an architecture.
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.