Thomas Narten wrote:
> you can always send comments to the author(s)...
Yes, but my only "comment" is that I liked your draft,
and that adding a reference to it in one or both of
the two IETF "list of lists" (taobis + procdoc) might
be a good idea,
Thanks, Frank
From: "Thomas Narten" <[EMAIL PROTECTED]>
For any document, you can always send comments to the author(s)... and
so far, I believe I've been quite responsive to comments...
Yes, very responsive, and both revisions have been pretty helpful in
facilitating related discussions. Thanks!
Spence
For any document, you can always send comments to the author(s)... and
so far, I believe I've been quite responsive to comments...
But if you want to post publically, here (the ietf list) is as good a
place as any, since the document isn't associated with any WG.
i.e., for draft-narten-successful
Spencer Dawkins wrote:
> if you've seen 00,
Yes, it could be referenced in the next procdoc-roadmap and
the next taobis (-04 was published the day before yesterday).
> I'm not sure where comments on this draft are supposed to
> go
If you find it out please post it here (dito for taobis, for
pr
I am not sure Dave's list is a complete list of stuff to remember, but it's
definitely a list of stuff to remember.
I'm not quite sure where the discussion forum for
http://www.ietf.org/internet-drafts/draft-narten-successful-bof-01.txt is,
but I really like the collection of stuff to remember
Elwyn Davies wrote:
Finding out what BOFs are being plotted is not very easy AFAIK. In the
case below there doesn't appear to have been any widespread public
announcement of the start of the mailing list and I suspect that is the
case for many others.
Obviously an announcement of intent to t
Finding out what BOFs are being plotted is not very easy AFAIK. In the
case below there doesn't appear to have been any widespread public
announcement of the start of the mailing list and I suspect that is the
case for many others.
Obviously an announcement of intent to the IETF list or the A
