Standards Compliant Mail Client Re: V6 still not supported Re: 202203211201.AYC
Abraham Y. Chen
aychen at avinta.com
Mon Mar 21 16:21:01 UTC 2022
Hi, Blake:
1) " so it's not a chore to tell what thread you're even replying
to? ": I am lost by your statement. I start each of my reply by
quoting a phrase or sentence of the message that I am responding to. To
be sure the original message in included, I copy the last message
following what I am writing. I also prefix it with the forum message tag
such as in this case "NANOG Digest, Vol 170, Issue 20 Message: 33 ".
This should be enough for anyone to follow in the latest exchange, as
well as tracing it back in history from the NANOG Digest, if interested.
Anything more could I do to ease your efforts without beginning to
create a long tail to a thread?
2) " ... a standards compliant mail client ... ": Please name
the "standards" and list a couple software that comply with it. This is
a topic that I am actually very interested in studying because eMails
these days come in too many formats / styles. Please teach me.
Thanks,
Abe (2022-03-21 12:20)
On 2022-03-20 19:01, Blake Dunlap wrote:
> Can you get a standards compliant mail client so it's not a chore to
> tell what thread you're even replying to?
>
> On Fri, Mar 18, 2022, 11:44 Abraham Y. Chen <aychen at avinta.com> wrote:
>
> Dear Borg:
>
> 1) " ... I dont see a way of extending IPv4 without making it a
> new protocol. ... new IP protocol that is much more similar to
> IPv4, just extends address space. ... ": I believe that you
> will be pleasantly surprised at the proposal summarized by the the
> below whitepaper. It proposes an overlay architecture over the
> current Internet. As such, assignable IPv4 addresses are extended
> without the baggage of the current Internet and no new protocol.
> To begin the deployment, all need be done is "*/disabling/* the
> program code that has been */disabling/* the use of the 240/4
> netblock" in routers.
>
> https://www.avinta.com/phoenix-1/home/RevampTheInternet.pdf
>
> 2) The "transition" will be mostly transparent from ordinary
> users' point of view, because IoTs do not need be reprogrammed.
> Please feel free to ask me to describe specific issues that you
> may come across.
>
> Regards,
>
>
> Abe (2022-03-18 12:43)
>
>
>
> ------------------------------
> NANOG Digest, Vol 170, Issue 20
>
> Message: 33
> Date: Fri, 18 Mar 2022 09:36:40 +0100 (CET)
> From:borg at uu3.net
> To:nanog at nanog.org
> Subject: Re: V6 still not supported
> Message-ID: <Pine.LNX.4.64.2203180928500.16585 at cube>
> Content-Type: TEXT/PLAIN; charset=US-ASCII
>
> While Im dont like IPv6, I see it as a bad idea.
> >From my knowledge I dont see a way of extending IPv4 without making it
> a new protocol. It was not designed that way.
>
> What I would LOVE to see that someone will pop in with new IP protocol
> that is much more similar to IPv4, just extends address space and fixes
> some well know issues. (for example remove netmask and use prefixlen/CIDR).
>
> Other importand aspect is some kind of IPvX -> IPv4 interop, so you can
> quickly put clients into new protocol and they have access to entire IPv4
> internet out of the box.
>
> Also, we need to please enterprises so we need largish RFC1918 space too.
>
> Just my 2 cents again
>
>
> ---------- Original message ----------
>
> From: Matt Hoppes<mattlists at rivervalleyinternet.net> <mailto:mattlists at rivervalleyinternet.net>
> To: Joe Maimon<jmaimon at jmaimon.com> <mailto:jmaimon at jmaimon.com>,bzs at theworld.com,
> Tom Beecher<beecher at beecher.cc> <mailto:beecher at beecher.cc>
> Cc: NANOG<nanog at nanog.org> <mailto:nanog at nanog.org>
> Subject: Re: V6 still not supported
> Date: Thu, 17 Mar 2022 23:34:19 -0500
>
> At this point I would**love** to see IPv4 get extended, a software patch applied
> to devices, and IPv6 die a quick painless death.
>
>> Its not impossible to envision that IPv4 does not ever go away but actually
>> gets extended in such a way that it obsoletes IPv6. The longer this drags out
>> the less implausible it seems.
>>
>> Joe
>>
>>
>
> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient&utm_term=icon>
> Virus-free. www.avast.com
> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient&utm_term=link>
>
>
> <#m_-5998402233395781358_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>
--
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20220321/81387c64/attachment.html>
More information about the NANOG
mailing list