Re: [Idr] AD Review of draft-ietf-idr-rfc5575bis-17 -> Updated Version -18 and Flowspec v6

[Christoph Loibl <[e-mail]>]

Alvaro,

> On 18.12.2019, at 17:17, Alvaro Retana <[e-mail]> wrote:
> 
>>> In case of an unknown flowspec component the parser can run until decoding
>>> the component type (always the first byte of the component). When it reads
>>> a unknown type-value it can easily jump over the remaining bytes of the
>>> entire NLRI (the length of the the complete NLRI is encoded in the first
>>> bytes of the NLRI) without needing to understand what is in there, because
>>> it should treat it as withdraw. I do not see the problem. It is supposed to
>>> “ignore” the entire NLRI not only a single component of it.
> 
> Christoph: It seems to me that we're getting to the same behavior: I
> call it "discard", you call it "treat it as withdraw...“ignore”".
> While discarding, ignoring and treat-as-withdraw are different things,
> the effect seems to be the same: we won't use the NLRI.  We can find
> the right words...  Do you also think we're going in the same
> direction?

I agree. I will need to collect the comments and think that I can come up with something that is acceptable while still giving some certain degree of flexibility to protocol extensions. 

I already started working on all the the issues in the document you pointed out on github:

	https://github.com/stoffi92/rfc5575bis <https://github.com/stoffi92/rfc5575bis>

Expect a new -19 to be ready by the end of January, maybe a little earlier.

Cheers,
Christoph

-- 
Christoph Loibl
[e-mail] | CL8-RIPE | PGP-Key-ID: 0x4B2C0055 | http://www.nextlayer.at