Re: [dhcwg] [v6ops] [EXTERNAL] Re: Question to DHCPv6 Relay Implementors regarding draft-ietf-dhc-dhcpv6-pd-relay-requirements

[[e-mail]]

Hi Michael,

Thanks for the suggestion. It reads better than my version. One question: "The policy SHOULD^WMAY?”  - I guess this was meant to be MAY?

Thanks,
Ian

> On 29. Oct 2020, at 23:17, Michael Richardson <[e-mail]> wrote:
> 
> 
> [e-mail] wrote:
>> Sorry for the delay in reply, I’ve been out of the office for the last few weeks for various reasons.
> 
>> Here’s a new wording proposal incorporating Jen & Bernie’s suggestions:
> 
>> R-4
>> To prevent routing loops, the relay SHOULD implement a configurable policy to drop packets
>> received on a DHCP-PD client facing interface with a destination address in a prefix delegated
>> to a client connected to that interface, as follows:  For point-to-point links, when the packet’s
>> ingress and egress interfaces match. For multi-access links, when the packet’s ingress and
>> egress interface match, and the source MAC and next-hop MAC addresses match. An
>> ICMPv6 Type 1, Code 6 (Destination Unreachable, reject route to destination) error message MAY
>> be sent as per [RFC4443], section 3.1.  The ICMP policy SHOULD be configurable.
> 
> I'm okay with the new concept.
> 
> I think that the sentence lengths and punctuation could use some work.
> I suggest:
> 
>    R-4
>    To prevent routing loops, the relay SHOULD implement a configurable
>    policy to drop potential looping packets received on any DHCP-PD client
>    facing interfaces.
>    The policy SHOULD^WMAY? be configurable on a per-client or per-destination basis.
> 
>    Looping packets are those with a destination address in a prefix
>    delegated to a client connected to that interface, as follows:
> 
>         1) For point-to-point links (e.g., PPPoE), when the packet’s ingress and egress
>            interfaces match.
> 
>         2) For multi-access links (e.g., ethernet), when the packet’s
>            ingress and egress interface match, and the source MAC and next-hop MAC
>            addresses match.
> 
>    An ICMPv6 Type 1, Code 6 (Destination Unreachable, reject route to destination) error message MAY
>    e sent as per [RFC4443], section 3.1.  The ICMP policy SHOULD be configurable.
> 
> --
> Michael Richardson <[e-mail]>   . o O ( IPv6 IøT consulting )
>           Sandelman Software Works Inc, Ottawa and Worldwide