From: Dave Taht <dave.taht@gmail.com>
To: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: [Cerowrt-devel] Fwd: [ipv6-wg] RIPE554-Bis consensus
Date: Fri, 3 Dec 2021 06:47:12 -0800 [thread overview]
Message-ID: <CAA93jw6Mz1+7+r=1qkORcz_wqa8mEw00Ecc+A1pavT9F7MUVfg@mail.gmail.com> (raw)
In-Reply-To: <HE1PR08MB2777C9EE9F8547DFE4DDDAE5E16A9@HE1PR08MB2777.eurprd08.prod.outlook.com>
rfc7567 is now here where it belongs, but optional. I can live with
that. Seeing the sea of standards for ipv6 is always intimidating, not
just for how enormous the list is,
but in knowing how much it leaves out for building a truly functional product.
---------- Forwarded message ---------
From: Jetten Raymond <raymond.jetten@elisa.fi>
Date: Fri, Dec 3, 2021 at 3:01 AM
Subject: [ipv6-wg] RIPE554-Bis consensus
To: ipv6-wg@ripe.net <ipv6-wg@ripe.net>
Cc: sander@steffann.nl <sander@steffann.nl>, jan@go6.si <jan@go6.si>,
merike@doubleshotsecurity.com <merike@doubleshotsecurity.com>
Dear List members,
The time has come, to declare consensus on RIPE554-Bis
https://docs.google.com/document/d/10HsfHDOIhUPIvGk9WP0azJiIsMVzQ49RsqWfnbNtceI/
Big thanks to all list discussion participants, participants at the
RIPE83 IPv6 Working Group session for their input, and most of all to
Merike Käo, Jan Žorž, Sander Steffann, Tim Chown, Tim Winters for
doing a lot of work.
I will contact the RIPE NCC shortly to get this new document published.
Raymond Jetten
Senior Technology Specialist
Production
Cloud Services, Networks and connectivity
Interconnectivity & Content
Elisa Oyj
Vuolteenkatu 2
33100 Tampere
+358 45 6700 139
raymond.jetten@elisa.fi
www.elisa.fi
Lisätietoa henkilötietojen käsittelystä ja tietosuojasta Elisalla
https://elisa.fi/tietosuoja
Mer information om Elisas hantering av personuppgifter och dataskydd
https://elisa.fi/tietosuoja
More information on personal data management and data protection at
Elisa https://elisa.com/dataprotection
*********************************************************************************************
For Internal Use Only
--
To unsubscribe from this mailing list, get a password reminder, or
change your subscription options, please visit:
https://lists.ripe.net/mailman/listinfo/ipv6-wg
--
I tried to build a better future, a few times:
https://wayforward.archive.org/?site=https%3A%2F%2Fwww.icei.org
Dave Täht CEO, TekLibre, LLC
parent reply other threads:[~2021-12-03 14:47 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <HE1PR08MB2777C9EE9F8547DFE4DDDAE5E16A9@HE1PR08MB2777.eurprd08.prod.outlook.com>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA93jw6Mz1+7+r=1qkORcz_wqa8mEw00Ecc+A1pavT9F7MUVfg@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox