Re: Seeking opinions on draft-akiya-bfd-seamless-alert-discrim

[Sam Aldrin <[e-mail]>]

[resending as mailer complained, mail is too long; removed earlier content
as well)
Hi Nobo et al,

I have finally read the 'alert discriminator' document.

Keeping the solution aside, what makes it special that the use case cannot
be documented in 'use case' ID?
Irrespectively, while explaining the solution, the problem has to be
explained anyway.
But, when there is use case document, like other use cases, adding the use
case will be good, doesn't it?

I know it will only delay the use-case document, which I am an editor of
it.
Want to understand the rationale behind it. (Read emails, but don't think I
am convinced).

Secondly, the alert-discriminator ID specifies the 'trace' option (sec 2.2).
I am not sure if it is indeed needed as BFD was not used so far like this.
Just a simple extension or not is different matter. Whether we should be
doing it with BFD (not just S-BFD) is more important and needs to be
discussed.
And I do not think that it should be part of S-BFD use case at this point.

cheers
sam