search

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

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

Jeff Haas comment: need more clarification for the Site Physical Availability Index Sub-TLV #13

Open lindadunbar opened 8 months ago

lindadunbar commented 8 months ago

When the Capacity Availability Index Metadata is attached to client prefix BGP update, it is for associating the client prefix with the Site-Index. When the Capacity Availability Index Metadata is attached to loopback address BGP update, it is for informing the receiving routers that all the prefixes associated with the Site-Index have been impacted.

lindadunbar commented 8 months ago

Added a bit flag in the Sub-TLV (Section 4.3):

When the bit flag is set to 1, the Site Availability Index is for BGP speakers (receivers) to associate the routes with the Site-ID. The Site Availability Percentage value is ignored. When set to 0, the BGP speakers (receivers) should apply the Site Availability Index value to all the routes associated with the Site-ID

suehares commented 4 months ago

re-opening until we discuss version 23 with Jeff Haas

jhaas-pfrc commented 1 month ago

I still don't think the text covering this is very clear. I've updated my XXX comment in main 24.xml to reflect the section that remains unclear.

It'd be helpful to see in a presentation what the intended protocol behavior is for this field in something like an actor diagram.