BGP OPS BOF laugh test

[Randy Bush <randy@psg.com>]

this bof proposal is really the start of replacing ptomaine with a new wg.

randy


From: David Meyer <dmm@sprint.net>
To: agenda@ietf.org
cc: randy@psg.com, bwijnen@lucent.com, fenner@research.att.com, zinin@psg.com,
   smd@ab.use.net, mknopper@cisco.com
Subject: BGP OPS BOF Request
Date: Fri, 10 Jan 2003 08:11:17 -0800

	Please consider this request to hold a BGP OPS BOF.

	Thanks,

	Dave

	[While none of the documents seem to state it, Randy
	mentioned that we need a document that has been discussed
	on a mailing list: draft-gill-btsh-01.txt -- Thanks, Dave]

2. BOFs will not be scheduled unless the Area Director(s) approved request 
is accompanied by a BOF FULL NAME AND ACRONYM, AREA, CHAIRS NAME(s) (given 
together with e-mail address(es)), AN AGENDA AND FULL DESCRIPTION. 
(Please read the BOF Procedure at ftp://ftp.ietf.org/ietf/1bof-procedures.txt 
before requesting a slot for a BOF.)

	BOF Full Name:	BGP OPS BOF (BOPS)

	Area:		Operations and Management

	Chair Name(s):	David Meyer <dmm@sprint.net>
			Possibly Vijay Gill <vijay@umbc.edu>

	Agenda:		Agenda Bashing			 5 minutes
			Review BOPS Mission Statement	 5 minutes
			PTOMAINE Update/Review		10 minutes
			BOPS Scope Discussion		15 minutes
			Candidate Charter		15 minutes 
			Next Steps			10 minutes
	
	Full Description: 

	The Border Gateway Protocol (BGP) is fundamental to the
	operation of the Internet. In recent years, the occurrence
	of BGP related operational issues has increased, and
	while overall understanding of the default-free routing
	system has improved, there is still a long and growing
	list of concerns. Among these are routing table growth rates,
	dynamic properties of the routing system, and the effects
	of routing policy on both the size and dynamic nature of
	the routing table. In addition, new and innovative uses of
	BGP, such as the use of BGP as a signaling protocol for
	applications such as VPN, have created new and unexpected
	operational issues. 

	The purpose of the BGP OPS WG is continue and expand on
	the original charter of the PTOMAINE WG. In particular,
	the purpose of the BOPS WG is to consider and measure the
	problem of routing table growth, and where appropriate,
	to document the operational aspects of measurement,
	policy, security, and VPN infrastructures.
	
4. You MUST provide the following information before the meeting will be scheduled:
  a. Working Group or BOF full name with acronym in brackets: BGP OPS (BOPS)
  b. AREA under which Working Group or BOF appears: O&M
  c. CONFLICTS you wish to avoid, please be as specific as
  possible: IDR, ISIS, MBONED, CCAMP, RPSEC PWE3, IEPREP,PTOMAINE
  (if it meets), MPLS, PPVPN, IPO, TEWG
  d. Expected Attendance (figures from the 55th IETF are at the
  end of this message): 200
  e. Special requests (i.e. multicast):
  f. Number of slots: 1
  g. Length of slot: 1 hour