On 12/18/15, 4:30 AM, "Santosh P K" <[email protected]> wrote:
Santosh: Hi! >>There is another aspect: the protocols (OSPF, IS-IS, L2TP) plan to >>transport >>a list of discriminators. Okay ... but how is the receiver S-BFD module >>making sense out of this list? Would have expected something like (type, >>discriminator). The protocols don't need to understand the details, only >>that >>the API transports one or more of these tuples in/out of the protocol >>module. >>S-BFD would know/define what a particular type means. >>Just asking before we send OSPF, IS-IS, L2TP into the wrong direction :-) > >[SPK] This is implementation specific right? Do we need this to be >captured in document? What is implementation specific? Right now the IGPs (generalizing: ISIS, OSPF, L2TP, etc.) are developing drafts to only carry the discriminators. If, as Mark suggests, the IGPs also transport something like "type", then S-BFD would know what each discriminator is for. Several questions: Is this (transporting [type, discriminator]) what is expected from the IGPs? If so, I assume the S-BFD module on the nodes assigns those values for transportation, right? How does a receiver know what a particular type means? Maybe the expectation from S-BFD is different...?? That is something that needs to be clarified so the IGP work can proceed. Thanks! Alvaro.
