> On 25 Sep 2019, at 11:52 am, John Levine <[email protected]> wrote:
>
> In article <[email protected]> you write:
>> ISP SITE <-> CPE <-> CUSTOMER SITE
>>
>> The CPE is a SITE boundary. It is also a Link-Local Boundary. ULA source
>> packets DO NOT cross the CPE by default it the CPE is properly configured.
>
> Really? Are you sure you're not confusing LL and ULA addresses? Why
> would CPE filter ULA addresses? In the normal case where the ISP
> provides the customer with a default route, they're like global
> addresses.
Because the CPE is a site boundary.
RFC 7084. Basic Requirements for IPv6 Customer Edge Routers
3.2.1
The IPv6 CE router defaults to acting as the
demarcation point between two networks by providing a ULA boundary, a
multicast zone boundary, and ingress and egress traffic filters.
Which is referenced in the CableLabs documents.
> R's,
> John
> _______________________________________________
> dns-operations mailing list
> [email protected]
> https://lists.dns-oarc.net/mailman/listinfo/dns-operations
--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: [email protected]
_______________________________________________
dns-operations mailing list
[email protected]
https://lists.dns-oarc.net/mailman/listinfo/dns-operations
