I support the work behind this document, but I do have a concern that gives me
pause regarding publishing it as an RFC in its current form.
I worry that it will serve as a disincentive for people to attempt IPv6-only
deployments. This is not because of the way that it's written, nor a commentary
on the quality of the document itself. I think that it does a good job of
noting that it is a snapshot and that things will continue to improve, etc. but
it runs afoul of the limitations of the IETF's document process- a static
document reporting "current" test findings is almost instantly obsolete. This
is a much larger problem than this draft, but it is something to consider when
thinking about the content of this draft and how it will be interpreted, the
audience, etc.
If the draft were to focus strictly on things which the *IETF* must fix in
order to resolve outstanding problems with IPv6-only operation, those would be
clearly actionable and new drafts written to resolve those issues could
"update" this one, so that it's clear to future readers when something
materially changes. In its current form, most of the noted "broken" things are
related to specific implementations and therefore largely beyond the IETF's
control (eg Skype, video game consoles, mobile phone stacks, etc). Unless it is
updated with bis versions periodically when those issues are found to be
resolved, it has the potential to mislead people as a source of information
that they might use to determine if they should even consider trying this. Some
of that information perhaps is better suited to a curated wiki, since it is
easier to update it as the situation improves. FWIW,
draft-donley-nat444-impacts has similar problems - very useful information, but
not well-suited to s
tatic documents.
I don't know if that's enough to block the document, and I'm not going to be
upset if it's published as-is, but I thought it was something that IESG should
consider in their evaluation of the document. Perhaps it's a matter of delaying
it for a bit and touching the document with updates to keep it active until we
feel like we've reached an equilibrium after a bit more IPv6 deployment over
the next 6-12 or even 18 months.
Thanks,
Wes George
-----Original Message-----
From: ietf-announce-bounces(_at_)ietf(_dot_)org [mailto:ietf-announce-
bounces(_at_)ietf(_dot_)org] On Behalf Of The IESG
Sent: Friday, December 09, 2011 5:34 PM
To: IETF-Announce
Subject: Last Call: <draft-arkko-ipv6-only-experience-04.txt>
(Experiences from an IPv6-Only Network) to Informational RFC
The IESG has received a request from an individual submitter to
consider
the following document:
- 'Experiences from an IPv6-Only Network'
<draft-arkko-ipv6-only-experience-04.txt> as an Informational RFC
The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf(_at_)ietf(_dot_)org mailing lists by 2012-01-06. Exceptionally, comments
may
be
sent to iesg(_at_)ietf(_dot_)org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.
Abstract
This document discusses our experiences from moving a small number
of
users to an IPv6-only network, with access to the IPv4-only parts of
the Internet via a NAT64 device. The document covers practical
experiences as well as road blocks and opportunities for this type
of
a network setup. The document also makes some recommendations about
where such networks are applicable and what should be taken into
account in the network design. The document also discusses further
work that is needed to make IPv6-only networking applicable in all
environments.
The file can be obtained via
http://datatracker.ietf.org/doc/draft-arkko-ipv6-only-experience/
IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-arkko-ipv6-only-experience/
No IPR declarations have been submitted directly on this I-D.
_______________________________________________
IETF-Announce mailing list
IETF-Announce(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf-announce
This E-mail and any of its attachments may contain Time Warner Cable
proprietary information, which is privileged, confidential, or subject to
copyright belonging to Time Warner Cable. This E-mail is intended solely for
the use of the individual or entity to which it is addressed. If you are not
the intended recipient of this E-mail, you are hereby notified that any
dissemination, distribution, copying, or action taken in relation to the
contents of and attachments to this E-mail is strictly prohibited and may be
unlawful. If you have received this E-mail in error, please notify the sender
immediately and permanently delete the original and any copy of this E-mail and
any printout.
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf