HTA> but if you add together:
HTA> I actually think we are reasonably close to a description.
That is quite a bit like saying that the presence of a requirements
document means that we are 'reasonably close' to a protocol
specification. If that were actually a valid assessment, we would
not have problems producing protocol specifications after having a
requirements document, and it would not take very long.
However, if you think we are "reasonably close", then it will not
be difficult for you to produce the document that contains the
necessary detail, so it can be inspected for concreteness, accuracy
HTA> I had one series of conversations where I tried to explain what the
HTA> secretariat does, and ended up with a puzzled "but where's the big
HTA> expensive problem?" - our activities may be far less extraordinary than we
HTA> may think.
First of all, for any interesting topic, there will always be some
people representing any given point of view. So it is not at all
significant that you found someone who thinks that none of this is
a big deal.
It would be more interesting to find someone who believes that and
who has real experience organizing and operating the relevant
activities (events and processes) that the IETF needs to get done.
You will not find such a person, because the actual details
required to conduct an operation like this are substantial, and the
constant attention to that detail required to keep things running
smoothly is daunting.
Dave Crocker <dcrocker-at-brandenburg-dot-com>
Brandenburg InternetWorking <www.brandenburg.com>
Sunnyvale, CA USA <tel:+1.408.246.8253>
Ietf mailing list