Hi I2NSF,

Our charter says...

> The I2NSF working group's deliverables include:
>
> o A single document covering use cases, problem statement, and gap
>    analysis document. This document will initially be produced for reference
>    as a living list to track and record discussions: the working group may 
>    decide to not publish this document as an RFC.

We split this work into draft-ietf-i2nsf-problem-and-use-cases  and
draft-ietf-i2nsf-gap-analysis.

It looks to me that the Problem Statement and Use Cases document is something
that the WG wants to push to RFC (please correct me if I'm wrong), but I am less
certain about the Gap Analysis.

While the Gap Analysis is good work and has definitely helped us understand our
direction, I don't see a lot of value in publishing it as an RFC. My proposal
is, therefore, to keep it alive as a WG draft while it is useful reference
material, and then to let it expire. Expired drafts still remain available in
the IETF Tools repository, so it would not be lost forever.

What do you all think?
Does someone have a strong reason to publish it as an RFC?

Thanks,
Adrian (per pro Linda)

_______________________________________________
I2nsf mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/i2nsf

Reply via email to