> If so that would seem to suggest that the apparent conflict with > draft-pmohapat-sidr-pfx-validate-03.txt is moot, since an Informative > document, strictly speaking, can't conflict with a Standards Track > document. > > Thanks, > > --John
If someone wanted to publish an informational document which gave a new version of BGP which is incompatible with existing deployed BGP, then I would expect that people would care a lot. If they argued "the new incompatible version of BGP is informational, so it is fine", I don't think that this would make most people happy (and as AD this argument by itself wouldn't make me happy). Thus I don't think that it is true that "an Informative document, strictly speaking, can't conflict with a Standards Track document". It is true that there have been cases of multiple incompatible experimental protocols published, but this is usually requires quite a bit of thought to make sure that there is a good reason to have multiple incompatible protocols. It is also true that there are cases where a protocol or an architecture that enjoys rough consensus of the WG will in some sense overtake a competitive document that did not enjoy rough consensus of the WG, but this of course requires judgment of the WG (which for example might be determined in WG discussions and a WG last call). Ross (speaking as AD) _______________________________________________ sidr mailing list [email protected] https://www.ietf.org/mailman/listinfo/sidr
