On Tue, 13 Sep 2022, Randy Bush wrote:
We strongly encourage all legacy resource holders who have not yet
signed an LRSA to cover their legacy resources to
consult a competent lawyer before signing an LRSA
randy
I concur , And seconded .
Hth , JimL
--
+--
> We strongly encourage all legacy resource holders who have not yet
> signed an LRSA to cover their legacy resources to
consult a competent lawyer before signing an LRSA
randy
NANOGers -
At present ARIN continues to provide the favorable annual maintenance fee cap
for legacy resource holders who enter
into an LRSA with ARIN, but this cap on total maintenance fees not be offered
to those entering an LRSA after 31 Dec
2023 and they will instead paying the same registrat
Hi,
MANRS is looking for volunteers to join a new working group to explore the idea
of creating a second, elevated tier of MANRS participation for organizations
that comply with more stringent requirements and auditing. We’re calling this
MANRS+ at the moment, though that’s only a working title
Jeff Tantsura writes:
> Looking at the fix, Donald has only removed IPV4_CLASS_DE(a)
> uint32_t)(a)) & 0xe000) == 0xe000)
> validation but kept INADDR_ANY.
> I’ll bring up RFC6286 to him
I believe it is implementing the RFC6286 requirements. INADDR_ANY is
((in_addr_t) 0x),
Looking at the fix, Donald has only removed IPV4_CLASS_DE(a) uint32_t)(a))
& 0xe000) == 0xe000)
validation but kept INADDR_ANY.
I’ll bring up RFC6286 to him
Cheers,
Jeff
> On Sep 12, 2022, at 13:41, Bjørn Mork wrote:
> Jeff Tantsura writes:
>
>> Indeed, someone was recently comp
6 matches
Mail list logo
