On Thu, Jun 1, 2023 at 1:55 PM Kent Watsen wrote:
> Hi Quifang,
>
> The latest update looks very good to me - IMO, ready for adoption.
>
> Jan, Jurgen, Andy, Rob - can you confirm that your concerns have been
> addressed?
>
>
IMO the problem statement and solution are still rough and unclear.
Th
Hi,
No changes are needed.
The notification definition says each leaf will be set to a value that
matches an instance of the leafref path.
The 'current()' linkage in your example links the sibling 'ifname' leaf to
select a matching instance.
That is not relevant to this notification example.
And
Hi Quifang,
The latest update looks very good to me - IMO, ready for adoption.
Jan, Jurgen, Andy, Rob - can you confirm that your concerns have been addressed?
Thanks,
Kent
> On May 25, 2023, at 8:16 AM, maqiufang (A)
> wrote:
>
> Hi, all
> This version reflects the input we've received fr
Forwarding to the authors of the RFC.
K.
> On May 30, 2023, at 3:47 AM, Vanapatla Ramana (Nokia)
> wrote:
>
> Hello Team,
>
> Gentle remainder on the below query.
>
> Regards,
> Ramana
>
> From: Vanapatla Ramana (Nokia)
> Sent: Friday, May 5, 2023 8:05 PM
> To: draft-ietf-netmod-ent...
Forwarding to the authors of the RFC.
K.
> On May 30, 2023, at 3:47 AM, Vanapatla Ramana (Nokia)
> wrote:
>
> Hello Team,
>
> Gentle remainder on the below query.
>
> Regards,
> Ramana
>
> From: Vanapatla Ramana (Nokia)
> Sent: Friday, May 5, 2023 8:05 PM
> To: draft-ietf-netmod-ent...
