support that configuration.
YMMV.
Thomas
Hans Kruse, Associate Professor
J. Warren McClure School of Communication Systems Management
Ohio University, Athens, OH, 45701
740-593-4891 voice, 740-593-4889 fax
autoconfig) behind it. you can then get to any of
those hosts from any another machine that speaks IPv6. if those
machines don't speak IPv6, they can often be upgraded to do so.
if they don't have IPv6 connectity, they can get it using 6to4.
Hans Kruse, Associate Professor
J. Warren McClure
with
storm doors nor effective insect inhibitions in the home...
Hans Kruse, Associate Professor
J. Warren McClure School of Communication Systems Management
Adjunct Associate Professor of Electrical Engineering and Computer
Science
292 Lindley Hall, Ohio University, Athens, OH, 45701
740-593-4891
/ietf
___
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf
Hans Kruse, Associate Professor
J. Warren McClure School of Communication Systems Management
Adjunct Associate Professor of Electrical Engineering and Computer
Science
292
-- is, in this world, just delusional. And, if
that delusion prevents the IETF community from explaining, carefully
and in public why the idea is a bad one, then it is we who are putting
the Internet at risk.
Hans Kruse, Associate Professor
J. Warren McClure School of Communication Systems Management
compared to the potential for poorly designed IP options to have an
adverse effect on Internet interoperation, at any layer from 3 up.
and one stops that by refusing a unique codepoint?
one stops it by any means that is effective and available.
Hans Kruse, Associate Professor
J. Warren McClure
without IETF consensus, then why are these two separate
choices in RFC 2434?
Hans Kruse, Associate Professor
J. Warren McClure School of Communication Systems Management
Adjunct Associate Professor of Electrical Engineering and Computer
Science
Ohio University, Athens, OH, 45701
740-593-4891 voice
is *not* enough to justify a registration;
we also need to agree as a community that the proposed usage will
not be a cause of collateral damage to the Internet. There's every
reason that the same standard should apply to specifications
developed outside the IETF exactly as to IETF documents.
Hans Kruse