RE: draft-ietf-opsec-filter-caps-08.txt

["Barry Greene \(bgreene\)" <bgreene@cisco.com>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

My issue is not with the document. My issue is with the jump to BCP
status. My issue is with a BROKEN IETF process around "BCPs." When
you read the process in IETF, BCP is ....  


   The BCP subseries of the RFC series is designed to be a way to
   standardize practices and the results of community deliberations. 
A
   BCP document is subject to the same basic set of procedures as
   standards track documents and thus is a vehicle by which the IETF
   community can define and ratify the community's best current
thinking
   on a statement of principle or on what is believed to be the best
way
   to perform some operations or IETF process function.


Since this is in the working group, work the problem. 

Submit the document as a "Proposed BCP" status. That is equivalent to
"Proposed Standard."



-----BEGIN PGP SIGNATURE-----
Version: PGP 8.1

iQA/AwUBRoO6HL/UEA/xivvmEQJafQCgnsbsroXwlfzjhqq0Mcysqb2JAFYAn0tu
RwVN/9lEuxP+CfkIvUnxR/sx
=AxQD
-----END PGP SIGNATURE-----