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

Thanks Michael!!

+1

As a solutions architect and protocol designer for Verizon, a Tier 1
Service Provider, fully IPv6 enabled, with one of the largest enterprise
networks in the world that is fully IPv6 deployed for over 10 years, as
co-author I support adoption and advancement of this draft.

This draft provides crucial industry feedback and deployment challenges
that are faced by operators for both enterprises & service providers, as
well as feedback on successful deployment strategies to aid in the further
proliferation of IPv6 worldwide.  I will be providing some additional
feedback on both service provider and enterprise side both lessons learned
and success stories to help improve the draft.

As Giuseppe has mentioned we are working on revising the draft, coalescing
all the feedback provided thus far during the adoption call.

Kind Regards

Gyan

On Mon, Jun 14, 2021 at 11:30 PM Ackermann, Michael <MAckermann@bcbsm.com>
wrote:

> Some brief comments insupport of this Draft.
>
> As an enterprise operator,  we need more information such as contained in
> this document.   As a whole, we are NOT moving in the IPv6 direction.
>  INMO this unfortunate.
>
> The primary reasons appear to be.
>
> * Lack of knowledge and information about IPv6.
> * Not being aware of technical or business reasons to deploy IPv6.
> * If/when we deploy, not knowing where the major challenges will be nor
> how to deal with them.
> * No experience with transition technologies
>
> This draft addresses all those areas and more.
>
> If we want enterprises to successfully move to IPv6, and I think/hope we
> all do, then documents such as this will help greatly.
> I hope the working group supports this draft and can collectively help
> make it even better than it already is, as we enterprises need all the
> assistance we can get in these areas.
>
> As a side benefit,  drafts such as this serve to help IETF better
> understand enterprise environments and perspectives in general, where major
> disconnects and misunderstandings exist today.
>
> Thanks
>
> Mike
>
>
> -----Original Message-----
> From: v6ops <v6ops-bounces@ietf.org> On Behalf Of Giuseppe Fioccola
> Sent: Monday, June 14, 2021 2:35 PM
> To: Dale W. Carder <dwcarder@es.net>; Nick Hilliard <nick@foobar.org>
> Cc: Ron Bonica <rbonica=40juniper.net@dmarc.ietf.org>; v6ops@ietf.org
> Subject: Re: [v6ops] Call For Adoption: draft-ietf-v6ops-ipv6-deployment
>
> [External email]
>
>
> Hi Dale,
> Thanks for your feedback.
> Please find my answers inline tagged as [GF].
> Regards,
>
> Giuseppe
>
> -----Original Message-----
> From: v6ops <v6ops-bounces@ietf.org> On Behalf Of Dale W. Carder
> Sent: Monday, June 14, 2021 5:57 PM
> To: Nick Hilliard <nick@foobar.org>
> Cc: Ron Bonica <rbonica=40juniper.net@dmarc.ietf.org>; v6ops@ietf.org
> Subject: Re: [v6ops] Call For Adoption: draft-ietf-v6ops-ipv6-deployment
>
> Thus spake Nick Hilliard (nick@foobar.org) on Tue, Jun 08, 2021 at
> 10:37:04AM +0100:
> > Ron Bonica wrote on 02/06/2021 19:11:
> > > This message initiates a call for adoption on
> > > draft-ietf-v6ops-ipv6-deployment. Please post messages expressing
> > > your position on adoption and rationale by 6/16/2021.
> >
> > I'm struggling with this document. It looks like an aggregation of
> > three separate things: a copy / rewording of chunks of ETSI White
> > Paper 35, an operator survey with some results and the "Call for
> > action" section, a set of suggestions on how to improve matters.
>
> That was my observation from last October as well, and I think it still
> applies for me as I take another read pass through it.
> https://mailarchive.ietf.org/arch/msg/v6ops/Wokx6bH3Xvf0sAwqV3Q7JhGRgME/
>
> [GF]: As co-author of ETSI WP 35, I disagree. To avoid repeating myself, I
> already highlighted in the two emails below the differences:
> https://mailarchive.ietf.org/arch/msg/v6ops/DTM96W0CyA6n-6NIIw5Iaiwh9Cg/
> https://mailarchive.ietf.org/arch/msg/v6ops/IxijU1psR6uqTDYJDcMfbValUg0/
>
>
> from Nick,
> > The "Call for action" section has potential promise and would benefit
> > from being moved to a separate document which discusses considerations
> > for / impediments to IPv6 adoption.
>
> I would agree, but to pull this off effectively, I would expect that there
> would be adequate citations and references to back up the claims.
>
> [GF]: As said when answering the previous email, we would thoroughly
> revise this section and, consequently, change the title into "common
> challenges of the IPv6 transition". Since this section was extended over
> time due to the comments from the IETF community, our idea is to make it
> more effective and highlight only the key message for each topic.
>
> In it's current form, I still don't see the purpose of the document as
> abundantly clear, and I don't see this draft progressing through the WG in
> any sort of timely manner.  Perhaps splitting it up could help but I am not
> sure.
>
> [GF]: Let me clarify the purpose of the document. The authors would like
> to describe the current status of the IPv6 deployment globally. The idea is
> to report both public data and statistically meaningful surveys among
> operators/enterprises. All this allows to identify the common challenges
> and therefore, make the community aware and stimulate more contribution.
> Considering the concerns, it seems not clear. We can surely restructure the
> draft (sometimes less is more) and improve its readability in the next
> versions. In the last version we made a lot of changes to address the
> number of inputs from the community and, this may also have affected the
> clarity.
>
>
> Dale
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>
>
> The information contained in this communication is highly confidential and
> is intended solely for the use of the individual(s) to whom this
> communication is directed. If you are not the intended recipient, you are
> hereby notified that any viewing, copying, disclosure or distribution of
> this information is prohibited. Please notify the sender, by electronic
> mail or telephone, of any unintended receipt and delete the original
> message without making any copies.
>
>  Blue Cross Blue Shield of Michigan and Blue Care Network of Michigan are
> nonprofit corporations and independent licensees of the Blue Cross and Blue
> Shield Association.
>
>
> This message was secured by Zix(R).
>
> _______________________________________________
> 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*