this is
now changed. The routers inside a realm can keep operating unmodified, and
there's no need to deploy new policies for ingress filtering.
Keep safe;
Pascal
-----Original Message-----
From: Abraham Y. Chen
Sent: vendredi 15 avril 2022 0:47
To: Pascal Thubert (pthubert)
Cc:nanog@n
t version of the draft impacted routers for BCP 38 procedures, this is
now changed. The routers inside a realm can keep operating unmodified, and
there's no need to deploy new policies for ingress filtering.
Keep safe;
Pascal
-----Original Message-----
From: Abraham Y. Chen
Sent: vendred
ed to deploy new policies for ingress filtering.
Keep safe;
Pascal
> -Original Message-
> From: Abraham Y. Chen
> Sent: vendredi 15 avril 2022 0:47
> To: Pascal Thubert (pthubert)
> Cc: nanog@nanog.org
> Subject: Re: Ready to compromise? was RE: V6 still not supported
&
Dear Pascal:
1) I had a quick look at the below updated draft. I presume Figure 2
is intended to address my request. Since each IPv4 address has 4 bytes,
what are the 12 bytes allocated for IPv4 header fields (outer) and
(inner), each? Aren't they the standard first 12 bytes of packet
iden
Dear all
Following advice from thus list, I updated the YADA I-Draft (latest is
https://www.ietf.org/archive/id/draft-thubert-v6ops-yada-yatt-03.html, more to
come soon if feedback is heard) and proposed it to the v6ops WG at the IETF.
For memory, the main goal here is to find a compromise as
5 matches
Mail list logo
