[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: Last Call: draft-ietf-opsec-filter-caps (Filtering and Rate Limiting Capabilities for IP Network Infrastructure) to BCP
-----BEGIN PGP SIGNED MESSAGE-----
Informational can always be moved to a different status later. Start
with informational, have it be used in RFPs, then we'll see how it
> -----Original Message-----
> From: Ron Bonica [mailto:firstname.lastname@example.org]
> Sent: Wednesday, June 27, 2007 8:56 AM
> To: Barry Greene (bgreene)
> Cc: email@example.com
> Subject: Re: Last Call: draft-ietf-opsec-filter-caps
> (Filtering and Rate Limiting Capabilities for IP Network
> Infrastructure) to BCP
> The last call has ended and AFAIKS, this was the only
> comment. Would the authors object to publishing this document
> as INFORMATIONAL? If not, we can proceed immediately. If so,
> we need to work through the issue.
> Barry Greene (bgreene) wrote:
> > I don't understand "BCP." Information RFC yes. Something
> that can be
> > use for requirements yes. But Best Common Practice? How is an
> > operator's "I wish my equipment can do this in my network"
> become a BCP?
> > IESG - I think we are abusing the BCP system. It states:
> > 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."
> > Which means we should be going through the same lifecycle
> of document
> > status as the standards track.
> > What we are getting now is the equivelent of a straight to
> > Internet Standard status.
> >>-----Original Message-----
> >>From: The IESG [mailto:firstname.lastname@example.org]
> >>Sent: Monday, June 11, 2007 1:34 PM
> >>To: IETF-Announce
> >>Cc: email@example.com
> >>Subject: Last Call: draft-ietf-opsec-filter-caps (Filtering
> and Rate
> >>Limiting Capabilities for IP Network Infrastructure) to BCP
> >>The IESG has received a request from the Operational Security
> >>Capabilities for IP Network Infrastructure WG (opsec) to
> consider the
> >>following document:
> >>- 'Filtering and Rate Limiting Capabilities for IP Network
> >> Infrastructure '
> >> <draft-ietf-opsec-filter-caps-08.txt> as a BCP
> >>The IESG plans to make a decision in the next few weeks,
> and solicits
> >>final comments on this action. Please send substantive comments
> >>to the firstname.lastname@example.org mailing lists by 2007-06-25.
> Exceptionally, comments
> >>may be sent to email@example.com instead. In either case, please
> >>retain the beginning of the Subject line to allow automated
> >>The file can be obtained via
> >>IESG discussion can be tracked via
> >>IETF-Announce mailing list
-----BEGIN PGP SIGNATURE-----
Version: PGP 8.1
-----END PGP SIGNATURE-----