Yes > On Jan 11, 2024, at 11:28 AM, Lokesh Chakka <[email protected]> wrote: > > So if forwarding address is 0.0.0.0, traffic will be directed towards the LSA > originator. > Otherwise it will be directed towards the LPM referred by forwarding address. > > Would like to understand if you agree or not. > > > <1677214703247000_1695686347.png> > > > > > ---- On Fri,12 Jan 2024 05:48:48 +0530 [email protected] wrote ---- > > > > > On Jan 11, 2024, at 11:15 AM, Lokesh Chakka <[email protected]> wrote: > > > > Can you please give me an example of routable Address > > > An address to which you can forward traffic based on the LPM in the IP route > table. A Router ID may be routable but it need not be. > > I think we’re done now. > > Acee > > > > > > > > > <1677214703247000_1695686347.png> > > > > > > > > > > ---- On Fri,12 Jan 2024 05:40:55 +0530 [email protected] wrote ---- > > > > > > > > > On Jan 11, 2024, at 11:03 AM, [email protected] > > > <[email protected]> wrote: > > > > > > This is a valid Errata. Routable Address is nothing but a Router ID. > > > > It's funny that you would debate me on this point. If you make this > > assumption, you should open an Errata on your implementation. > > > > Excerpted from RFC 2328: > > > > Router ID > > A 32-bit number assigned to each router running the OSPF > > protocol. This number uniquely identifies the router within > > an Autonomous System. > > > > OSPF Router IDs need NOT be routable. > > > > Acee > > > > > > > > > > > > Thanks. > > > Lokesh. > > > > > > > > > > > > > > > ---- On Fri,12 Jan 2024 05:30:08 +0530 [email protected] wrote ---- > > > > > > This Errata is invalid. The forwarding address contains a routable > > > address on the LSA originator or 0.0.0.0 - not a Router ID address. > > > > > > Thanks, > > > Acee > > > > > > > On Jan 11, 2024, at 01:42, RFC Errata System > > > > <[email protected]> wrote: > > > > > > > > The following errata report has been submitted for RFC2328, > > > > "OSPF Version 2". > > > > > > > > -------------------------------------- > > > > You may review the report below and at: > > > > https://www.rfc-editor.org/errata/eid7757 > > > > > > > > -------------------------------------- > > > > Type: Technical > > > > Reported by: Lokesh Venkata Kumar Chakka <[email protected]> > > > > > > > > Section: A.4.5 > > > > > > > > Original Text > > > > ------------- > > > > Forwarding address > > > > Data traffic for the advertised destination will be forwarded to this > > > > address. If the Forwarding address is set to 0.0.0.0, data traffic will > > > > be forwarded instead to the LSA's originator (i.e., the responsible AS > > > > boundary router). > > > > > > > > Corrected Text > > > > -------------- > > > > Forwarding address > > > > Data traffic for the advertised destination will be forwarded to this > > > > address. If the Forwarding address is set to a Router ID address value > > > > other than 0.0.0.0, data traffic will be forwarded to that Router > > > > instead to the LSA's originator (i.e., the responsible AS boundary > > > > router). > > > > > > > > Notes > > > > ----- > > > > Data traffic destined to the network indicated by Link State ID will be > > > > routed to that Router ID mentioned in forwarding address. If forwarding > > > > address is set to 0.0.0.0, it will be forwarded to LSA Originator > > > > itself. > > > > > > > > Instructions: > > > > ------------- > > > > This erratum is currently posted as "Reported". (If it is spam, it > > > > will be removed shortly by the RFC Production Center.) Please > > > > use "Reply All" to discuss whether it should be verified or > > > > rejected. When a decision is reached, the verifying party > > > > will log in to change the status and edit the report, if necessary. > > > > > > > > -------------------------------------- > > > > RFC2328 (no draft string recorded) > > > > -------------------------------------- > > > > Title : OSPF Version 2 > > > > Publication Date : April 1998 > > > > Author(s) : J. Moy > > > > Category : INTERNET STANDARD > > > > Source : Open Shortest Path First IGP > > > > Area : Routing > > > > Stream : IETF > > > > Verifying Party : IESG > > > > > > > > _______________________________________________ > > > > Lsr mailing list > > > > [email protected] > > > > https://www.ietf.org/mailman/listinfo/lsr > > > > > > > > > > > >
_______________________________________________ Lsr mailing list [email protected] https://www.ietf.org/mailman/listinfo/lsr
