search

ietf-wg-idr / draft-ietf-idr-5g-edge-service-metadata

Editing for the 5G Service Metadata
0 stars 2 forks source link

Discussion of BFD use #36

Open jhaas-pfrc opened 1 month ago

jhaas-pfrc commented 1 month ago

The document mentions BFD but not really how it's used.

BFD is capable of using concatenated mode in some circumstances which might address some ingress/egress behaviors. However, I think at this point the use of BFD isn't fully thought through.

My recommendation is to consider just removing the section on BFD and await further clarity for the use of it.

Otherwise, update the document to describe BFD procedures for routes that have the metadata attribute present.

lindadunbar commented 1 month ago

How about the following paragraph?

If the access network attached to the egress router doesn't support BFD, it can be challenging for the egress router to directly notify ingress routers about failures within the access network. However, if BFD is implemented on the access network, concatenated path down mechanisms can be employed to propagate failure information more effectively.

jhaas-pfrc commented 1 month ago

You've added text. I suspect you'll find that the IDR WG doesn't find the procedures clear for how BFD is getting setup for each of the routes with the metadata attribute. However, you can have that discussion in the WG and it doesn't have to hold publication.