Re: [v6ops] Call For Adoption: draft-ietf-v6ops-ipv6-deployment

Hi Nick

If you have certain sections within the draft that need rearrangement or
restructuring so the draft flows better for readability, we can certainly
take your comments as well as any others and update the draft well before
the end of the adoption call as well so the draft is in a reasonable state
to be taken on by the WG once adopted.

Please let us know the details.

We really appreciate yours as well as others feedback to help improved and
advance the document.

Kind Regards

Gyan
On Tue, Jun 8, 2021 at 12:30 PM Nick Hilliard <nick@foobar.org> wrote:

> Giuseppe Fioccola wrote on 08/06/2021 16:41:
> > [GF]: I agree that the document needs to be improved but I disagree
> > that this is not in scope of V6OPS WG.
>
> The issue is not whether the content area is in scope for v6ops (clearly
> it is), just that there were enough fundamental problems with the
> structure and content of the document such that it isn't appropriate for
> adoption at the moment.  Specifically, 1. there seem to be three main
> strands in the document which don't fit together well, and 2. there's no
> beginning, middle and end to the document - after reading the document,
> I didn't have a clear picture of what it was trying to say.
>
> I can't see a way of fixing this without complete restructuring from the
> beginning.  Maybe the individual strands could be made to work as
> standalone documents?  Possibly if the document started out with a
> formal design and was rewritten from scratch to fit inside this design,
> it would become more cohesive?  Either way, these are issues that need
> to be sorted before the document is adopted rather than after.
>
> Nick
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>
-- 

<http://www.verizon.com/>

*Gyan Mishra*

*Network Solutions A**rchitect *

*Email gyan.s.mishra@verizon.com <gyan.s.mishra@verizon.com>*

*M 301 502-1347*