Hello,

A few questions:

1.)    Do you have your own Internet ingress/egress, or, do you utilize
your upstream agencies connection?
2.)    Will your site provide Internet transit services to the rest of the
organization?
3.)    Is this BGP requirement due to you migrating to MPLS and are in need
of route peering with the provider?
4.)    Do you own your own CIDR block(s), or, do you share IP space with
another agency?

There are quite a few unanswered questions and options to discuss. It
might be helpful to understand some more background. The routers you're
describing won't work in a "traditional" Internet BGP peering scenario
(full Internet route table). You could get away with taking a default
route or perhaps even partial/customer routes from the provider, but you
also need to consider the robustness of your solution since router
instability (resources, interface, whatever) could bite you in the form
of route dampening upstream. You also need to consider issues such as
route policy to the Internet and your internal sites (e.g. iBGP
peering). You may need to weave your IGP (OSPF, EIGRP, etc.) routing
architecture into your BGP policies. You may need to deal with BGP
communities so that certain routes/prefixes can have appropriate
policies applied upstream from your net. And on and on it goes...in
short, there's a lot of horsepower with BGP. :-)

Could you elaborate on your situation a bit more?