a BCP is a standard - to publish this ID as a BCP would violate 2804 but there would be no problem (RFC 2804-wise) publishing it as an informational RFC
Scott On Feb 19, 2013, at 4:06 PM, Owen DeLong <[email protected]> wrote: >>> >>> An example of the latter is RFC 3924. You can describe a solution, but >>> the IETF will not standardise it. >> >> >> Its probably time for IETF to re-visit that decision, I say this in all >> humbleness. But, my goal is not to battle that. We want solution documents >> that operators can use it as basis when deploying IETF protocols, in this >> case for SP WIFI. May be as you and Melinda pointed out, documentation in >> some form on the LI architecture identifying all considerations is some >> thing that operators can live with Š > > IMHO, the IETF should not standardize it, but the document may be worthy > of publication as a BCP. > > Owen > > _______________________________________________ > OPSAWG mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/opsawg _______________________________________________ OPSAWG mailing list [email protected] https://www.ietf.org/mailman/listinfo/opsawg
