Re: BGP OPS BOF laugh test

[Randy Bush <randy@psg.com>]

notice
  o more definition of interaction with idr
  o some talk of addressing and igps too

randy

---


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:	Global Routing Operations Working Group (GROW)

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

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

	Description: 

	The Border Gateway Protocol (BGP) is fundamental to the
	operation of the Internet. In recent years, occurrences
	of BGP related operational issues have 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, interaction of interior and exterior routing
	protcols, 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 some types of Virtual Private
	Networks, 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 GROW is to consider and measure the
	problem of routing table growth, the effects of the
	interactions between interior and exterior routing
	protocols, and the effect of address allocation policies
	and practices on the global routing system. Finally,
	where appropriate, the GROW documents the operational
	aspects of measurement, policy, security, and VPN
	infrastructures.  

	GROW will also advise the IDR WG with respect whether it
	is addressing the relevant operational needs, and where
	appropriate, suggest course corrections. Finally,
	operational requirements developed in the GROW can 
	also be used by any new working group charged with
	standardizing a next generation inter-domain routing
	protocol. 


	
4. You MUST provide the following information before the meeting will be scheduled:
  a. Working Group or BOF full name with acronym in brackets: Global Routing Operations Working Group (GROW)
  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