Nick, I am not going to argue with few of you here who want free form text and do not accept any suggestions.
But if you can not parse few defined keywords in any free form text to enable better automated interpretation of the message I think there is more problems here. TLV within current NOTIFICATION MSG is an overkill so do not count of new proposal from me on it. Operational message solved that already. Btw how are you going to handle it in IX ? I assume RS peers will not get any info if one of the parties they used to get routes from goes down and sends free form msg to RS ? Routes will be get withdrawn and that's it. Best, R. On Sat, Nov 19, 2016 at 3:48 PM, Nick Hilliard <[email protected]> wrote: > Robert Raszuk wrote: > > Just to be clear: I am also OK with free form text with the few well > > known and easy to machine parse keywords (in it). > > the field should either be fully structured or free-form, and the > explicit intent of this draft is free form, utf8. Having a half-way > house is in nobody's interest because the discussion will then rat-hole > on defining a new ad-hoc quasi-language, and the draft - if it ever gets > turned into running code - will end up being a protocol soup which > no-one will find satisying. > > If you feel it should be fully structured, then please feel free to > submit an alternative draft to that effect. > > Nick >
_______________________________________________ GROW mailing list [email protected] https://www.ietf.org/mailman/listinfo/grow
