Re: [v6ops] (re)numbering [ULA draft revision #2 Regarding isolated networks]

[Matthew Petach <[e-mail]>]

On Thu, May 29, 2014 at 5:45 PM, Mark Andrews <[e-mail]> wrote:

>
> In message <CAKr6gn1DTUnt=9UbQjmCSsk9ZHUpVJtwQM2u7xp0-J=
> [e-mail]>
> , George Michaelson writes:
> >
> > How long ago Mark. How old, What OS.
>
> A Brother HL-4040CN printer only supports a single IPv4 address and
> it has IPv6 support.  To be fair only supports configuring a single
> static IPv6 address but will autoconf multiple ones.  It currently
> 3 IPv6 addresses (PI + ULA + LL).
>

Hm.  OK.  In my setup, only the hosts
need to support multiple addresses;
the peripheral devices are only on
the internal network, so there's
never been a need for them to
support multiple addresses.

Thanks for pointing that out.

Matt


>
> This is the difference between what is required by a host/node for
> IPv4 and IPv6.  Support for multiple prefixes is required for IPv6.
> It isn't required for IPv4.
>
> > If this is a UNISYS mainframe which used , to separate the elements of
> the
> > dotted-quad for instance (yes, that really happened) we'd be entitled to
> > say "so what"
> >
> > if this is a Vista or newer OS, we need to know.
> >
> >
> > On Fri, May 30, 2014 at 1:32 AM, Mark Andrews <[e-mail]> wrote:
> >
> > >
> > > In message <CAEmG1=rz=
> > > [e-mail]>
> > > , Matthew Petach writes:
> > > >
> > > > On Wed, May 28, 2014 at 2:24 PM, Mark ZZZ Smith <
> > > [e-mail]>
> > > > wrote:
> > > > [...]
> > > >
> > > > > RFC1918s have provided that internal connectivity robustness to
> both
> > > home
> > > > > networks and enterprise networks. Of course the drawback is that in
> > > IPv4 it
> > > > > is binary - hosts either have RFC1918s or public addresses, so if
> you
> > > have
> > > > > RFC1918s you have to use NAT to access external destinations on the
> > > > > Internet.
> > > >
> > > > Wow...that's news to me.
> > > >
> > > > For a decade now, I've been using
> > > > RFC1918 addresses+global addresses
> > > > in IPv4 on my home network; each
> > > > host has an address from each subnet,
> > > > and uses the 1918 addresses to reach
> > > > internal-only devices (printers, terminal
> > > > servers, etc.) which only have RFC1918
> > > > addresses, and use the globally routed
> > > > IPs for reaching non-local destinations.
> > > >
> > > > I'm not sure I'd agree with your characterization
> > > > that IPv4 is different from IPv6 in that regards;
> > > > there's nothing in the IPv4 world that prevents
> > > > hosts from having multiple addresses, and
> > > > making use of them.
> > > >
> > > > It's definitely a plus to have internal connectivity
> > > > stay working regardless of external connectivity,
> > > > I completely agree with you on that.
> > > >
> > > > Matt
> > >
> > > It may work with some machine some of the time.  It is not guarenteed
> > > to work with all machines all of the time.  I've definitely used
> > > machines which didn't support multiple IPv4 addresses on the same
> > > interface.
> > >
> > >
> > > --
> > > Mark Andrews, ISC
> > > 1 Seymour St., Dundas Valley, NSW 2117, Australia
> > > PHONE: [phone]                 INTERNET: [e-mail]
> > >
> > > _______________________________________________
> > > v6ops mailing list
> > > [e-mail]
> > > https://www.ietf.org/mailman/listinfo/v6ops
> > >
> >
> > --047d7b15abb1c861ed04fa921bb7
> > Content-Type: text/html; charset=UTF-8
> > Content-Transfer-Encoding: quoted-printable
> >
> > <div dir=3D"ltr">How long ago Mark. How old, What
> OS.<div><br></div><div>If=
> >  this is a UNISYS mainframe which used , to separate the elements of the
> do=
> > tted-quad for instance (yes, that really happened) we&#39;d be entitled
> to =
> > say &quot;so what&quot;</div>
> > <div><br></div><div>if this is a Vista or newer OS, we need to
> know.</div><=
> > /div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On
> Fri, =
> > May 30, 2014 at 1:32 AM, Mark Andrews <span dir=3D"ltr">&lt;<a
> href=3D"mail=
> > to:[e-mail]" target=3D"_blank">[e-mail]</a>&gt;</span>
> wrote:<br>
> > <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0
> .8ex;border-left:1p=
> > x #ccc solid;padding-left:1ex"><br>
> > In message &lt;CAEmG1=3Drz=3D<a href=3D"mailto:
> o3adK5a7M5DOFGVa1GnjKxj3bNRq=
> > [e-mail]
> ">o3adK5a7M5DOFGVa1GnjKxj3bNRq6896nBQGLOTVQ@mai=
> > l.gmail.com</a>&gt;<br>
> > <div><div class=3D"h5">, Matthew Petach writes:<br>
> > &gt;<br>
> > &gt; On Wed, May 28, 2014 at 2:24 PM, Mark ZZZ Smith &lt;<a
> href=3D"mailto:=
> > [e-mail]">[e-mail]</a>&gt;<br>
> > &gt; wrote:<br>
> > &gt; [...]<br>
> > &gt;<br>
> > &gt; &gt; RFC1918s have provided that internal connectivity robustness
> to b=
> > oth home<br>
> > &gt; &gt; networks and enterprise networks. Of course the drawback is
> that =
> > in IPv4 it<br>
> > &gt; &gt; is binary - hosts either have RFC1918s or public addresses, so
> if=
> >  you have<br>
> > &gt; &gt; RFC1918s you have to use NAT to access external destinations
> on t=
> > he<br>
> > &gt; &gt; Internet.<br>
> > &gt;<br>
> > &gt; Wow...that&#39;s news to me.<br>
> > &gt;<br>
> > &gt; For a decade now, I&#39;ve been using<br>
> > &gt; RFC1918 addresses+global addresses<br>
> > &gt; in IPv4 on my home network; each<br>
> > &gt; host has an address from each subnet,<br>
> > &gt; and uses the 1918 addresses to reach<br>
> > &gt; internal-only devices (printers, terminal<br>
> > &gt; servers, etc.) which only have RFC1918<br>
> > &gt; addresses, and use the globally routed<br>
> > &gt; IPs for reaching non-local destinations.<br>
> > &gt;<br>
> > &gt; I&#39;m not sure I&#39;d agree with your characterization<br>
> > &gt; that IPv4 is different from IPv6 in that regards;<br>
> > &gt; there&#39;s nothing in the IPv4 world that prevents<br>
> > &gt; hosts from having multiple addresses, and<br>
> > &gt; making use of them.<br>
> > &gt;<br>
> > &gt; It&#39;s definitely a plus to have internal connectivity<br>
> > &gt; stay working regardless of external connectivity,<br>
> > &gt; I completely agree with you on that.<br>
> > &gt;<br>
> > &gt; Matt<br>
> > <br>
> > </div></div>It may work with some machine some of the time. =C2=A0It is
> not=
> >  guarenteed<br>
> > to work with all machines all of the time. =C2=A0I&#39;ve definitely
> used<b=
> > r>
> > machines which didn&#39;t support multiple IPv4 addresses on the same<br>
> > interface.<br>
> > <span class=3D"HOEnZb"><font color=3D"#888888"><br>
> > <br>
> > --<br>
> > Mark Andrews, ISC<br>
> > 1 Seymour St., Dundas Valley, NSW 2117, Australia<br>
> > PHONE: <a href=3D"tel:%2B61%202%209871%204742"
> value=3D"[phone]">+61 2=
> >  9871 4742</a> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0
> INTE=
> > RNET: <a href=3D"mailto:[e-mail]">[e-mail]</a><br>
> > </font></span><div class=3D"HOEnZb"><div class=3D"h5"><br>
> > _______________________________________________<br>
> > v6ops mailing list<br>
> > <a href=3D"mailto:[e-mail]">[e-mail]</a><br>
> > <a href=3D"https://www.ietf.org/mailman/listinfo/v6ops"
> target=3D"_blank">h=
> > ttps://www.ietf.org/mailman/listinfo/v6ops</a><br>
> > </div></div></blockquote></div><br></div>
> >
> > --047d7b15abb1c861ed04fa921bb7--
> --
> Mark Andrews, ISC
> 1 Seymour St., Dundas Valley, NSW 2117, Australia
> PHONE: [phone]                 INTERNET: [e-mail]
>
>