LDDOWN_INTERVAL 1 ms
The OSPF YANG module, however, doesn't have those default values. Shouldn't
they be added?
10. RFC 7949 defines a mechanism to use IPv4 to transport OSPFv3 packets.
Shouldn't there be a configuration leaf to enable that mechanism?
Best Regards,
--
Rena
le:
https://pastebin.com/raw/zyDASfm2 (the connected routes are the ones
without nexthops).
In any case, section 16.1.1 of RFC 2328 says that nexthop addresses aren't
required for point-to-point interfaces. So I'm still wondering whether a
keyless list wouldn't be a better option.
Be
Hi Acee,
Em sex., 30 de set. de 2022 às 09:32, Acee Lindem (acee)
escreveu:
> Hi Renato,
>
>
>
> *From: *Renato Westphal
> *Date: *Thursday, September 29, 2022 at 7:56 PM
> *To: *Acee Lindem
> *Cc: *"draft-ietf-ospf-y...@ietf.org" , "
> lsr@ietf.o
Em sex., 30 de set. de 2022 às 11:21, Acee Lindem (acee)
escreveu:
> Hi Renato,
>
> Thanks - see inline.
>
> On 9/30/22, 10:14 AM, "Renato Westphal" wrote:
>
> Hi Acee,
>
> Em sex., 30 de set. de 2022 às 09:32, Acee Lindem (acee) <
> a...@cis
> > does not match the current year
>> >
>> > == Line 1266 has weird spacing: '... allows a rou...'
>> >
>> > -- The document date (October 17, 2019) is 1337 days in the past.
>> > Is this intentional?
>> >
>> > Checking references for intended status: Proposed Standard
>> > -
>> >
>> > (See RFCs 3967 and 4897 for information about using normative
>> > references to lower-maturity documents in RFCs)
>> >
>> > == Outdated reference: draft-ietf-bfd-yang has been published as RFC
>> > 9127
>> >
>> > ** Downref: Normative reference to an Experimental RFC: RFC 1765
>> >
>> > ** Downref: Normative reference to an Experimental RFC: RFC 4973
>> >
>> > ** Downref: Normative reference to an Informational RFC: RFC 5309
>> >
>> > ** Downref: Normative reference to an Informational RFC: RFC 5714
>> >
>> > ** Downref: Normative reference to an Informational RFC: RFC 6987
>>
>>
>> These idnits are fixed.
>>
>>
>> Thanks,
>> Acee
>>
>>
>> >
>> > Summary: 5 errors (**), 0 flaws (~~), 3 warnings (==), 1 comment
>> > (--).
>> >
>> >
>> >
>>
>>
>
> Mahesh Jethanandani
> mjethanand...@gmail.com
>
>
>
>
>
>
> ___
> Lsr mailing list
> Lsr@ietf.org
> https://www.ietf.org/mailman/listinfo/lsr
>
--
Renato Westphal
___
Lsr mailing list
Lsr@ietf.org
https://www.ietf.org/mailman/listinfo/lsr
-lsa-yang/
>
> There is also an HTML version available at:
> https://www.ietf.org/archive/id/draft-ietf-lsr-ospfv3-extended-lsa-yang-20.html
>
> A diff from the previous version is available at:
> https://author-tools.ietf.org/iddiff?url2=draft-ietf-lsr-ospfv3-extended-lsa-yang-20
tf-ospf-sr-yang/
>
> There is also an HTML version available at:
> https://www.ietf.org/archive/id/draft-ietf-ospf-sr-yang-21.html
>
> A diff from the previous version is available at:
> https://author-tools.ietf.org/iddiff?url2=draft-ietf-ospf-sr-yang-21
>
> Internet-Drafts a
re are you using?
It's a tool called netgen I wrote several years ago, mostly for
personal use. It uses Linux namespaces and veth interfaces to create a
virtual topology. Today there are similar tools that are better
documented and maintained, but I'm too lazy to migrate to those tools
so I keep using netgen :)
Best Regards,
--
Renato Westphal
___
Lsr mailing list
Lsr@ietf.org
https://www.ietf.org/mailman/listinfo/lsr
s are malformed i.e., where the `length` field in the [sub-]TLV
> disagrees with the actual length of the `yang:hex-string` value. In this case
> though we might want to call it out as `malformed-length` or something.
That's an interesting suggestion. In practice, however, I think most
Em dom., 13 de ago. de 2023 às 18:16, Acee Lindem
escreveu:
>
> Hi Renato,
>
>
>
> > On Aug 11, 2023, at 9:41 PM, Renato Westphal
> > wrote:
> >
> > Em dom., 16 de jul. de 2023 às 22:37, Christian Hopps
> > escreveu:
> >>> On Jul 13,
Em qui., 13 de jul. de 2023 às 11:42, Renato Westphal <
renatowestp...@gmail.com> escreveu:
> 2 - For OSPFv3, the "prefix-sid-sub-tlv" container should be within
> the "sub-tlvs" list of each extended LSA type instead of being
> alongside it. The same applies
ub-tlvs") should be removed in favor of the generic
> > "sub-tlvs" list.
>
> I moved these to the sub-tlvs list for the link-tlv but kept the
> containers consistent with the other sub-tlv groupings in the model.
> We can discuss.
>
P
the external original bit is set is missing.
8 - The "decoded-completed" leaf is described as: "The IS-IS LSP body
has been fully decoded". Does "fully decoded" mean that no unknown
TLVs or Sub-TLVs are present?
Thanks for your time, and I hope you find this feedback useful.
[1] https://github.com/holo-routing/holo
Best regards,
--
Renato Westphal
___
Lsr mailing list -- lsr@ietf.org
To unsubscribe send an email to lsr-le...@ietf.org
I personally found all RFCs and the ISO
standard to be very precise and well written.
Regards,
Renato.
--
Renato Westphal
___
Lsr mailing list -- lsr@ietf.org
To unsubscribe send an email to lsr-le...@ietf.org
s version is available at:
> https://author-tools.ietf.org/iddiff?url2=draft-ietf-isis-sr-yang-26
>
> Internet-Drafts are also available by rsync at:
> rsync.ietf.org::internet-drafts
>
>
> ___
> Lsr mailing list -- lsr@ietf.org
> T
Hi Acee,
Thank you for your quick response.
Em seg., 14 de abr. de 2025 às 12:06, Acee Lindem
escreveu:
>
> Hi Renato,
>
> > On Apr 13, 2025, at 11:50 AM, Renato Westphal
> > wrote:
> >
> > Hi all,
> >
> > I'm implementing this draft and wou
oolean
>
>
> This is an augmentation of operational state. You're right, we don't have
> this in OSPF. I looked at RFC9129, this can be added to
> ospf:interface/ospf:neighbors/ospf:neighbor. Unfortunately we have different
> names in RFC9129 and 9130, neighbors vs. adjacencies.
Yes, that's what I mean. I think adding Adj-SID information to
ospf:interface/ospf:neighbors/ospf:neighbor would be useful.
Best Regards,
--
Renato Westphal
___
Lsr mailing list -- lsr@ietf.org
To unsubscribe send an email to lsr-le...@ietf.org
sex., 18 de abr. de 2025 às 09:15, Acee Lindem
escreveu:
>
> Hi Renato,
>
> Thanks so much for your implementation. All the reviews are also useful but
> this is invaluable.
>
> Yingzhen has incorporated your comments in -28.
>
> > On Apr 16, 2025, at 8:17 PM, Renat
18 matches
Mail list logo
