ust in time for fire season, along comes the draft Annual Funding Agreement for the National Bison Range.

It's the kind of issue that can inflame a community, much like a spark in August grass on a hot, dry hillside of the Range itself. And it certainly is shaping up to be a scorching topic for summer discussions.

The draft is a result of more than a year of negotiations between the Confederated Salish and Kootenai Tribes and the Department of Interior. As allowed under the Indian Self-Determination and Education Assistance Act passed by the U.S. Congress in 1994, the tribes asked to take over management functions at the National Bison Range Complex. The Complex includes the National Bison Range in Moiese, Swan Lake, Lost Trail, Pablo and Ninepipe National Wildlife Refuges, and the Northwest Montana Wetland Management District. However, the draft AFA only applies to facilities and property on the Flathead Indian Reservation.

According to the draft agreement, the tribes would perform some of the services currently being provide by the U.S. Fish and Wildlife Service, including biological programs, fire program, maintenance program and visitor services. The FWS would maintain ownership and management authority over all lands and buildings at the Bison Range.

The tribes have demonstrated to the Interior Department's satisfaction that the Bison Range holds a "special geographic, historical and cultural significance" to the CSKT. The draft AFA says so. But, the tribes haven't won over the hearts of a significant number of non-tribal members and wildlife management organizations who intensely oppose the transfer of any management function.

Public comment is currently being accepted and will continue with public meetings, though none have yet been formally scheduled. The comment period ends in early October, after which changes may or may not be made to the draft and it is submitted to Congress for a 90-day review period before implementation. Unless Congress takes separate action - and nobody yet knows how Montana's delegation will weigh in on the proposal - the tribes will begin taking over those functions under FWS supervision in 2005.

The draft agreement may be viewed on-line at http://mountain-prairie.fws.gov/cskt-fws-negotiation or by contacting the Bison Range, (406) 644-2211, or CSKT, (406) 675-2700. Comments may be submitted via email at: draftafapubliccomments@fws.gov, or in writing to the Bison Range.

Whenever they are scheduled, the public comment meetings will also provide the crucial opportunity for the public to voice their thoughts about the draft AFA. The problem with past public meetings has been the difficulty in maintaining comments within time limits, as well as dealing with the bubbling-over of emotions through contentious remarks.

It's not that contentious remarks shouldn't be aired, but the emotional nature of the matter drew out a few comments at last year's meetings that were not constructive. They also served to whip up even more emotional responses that may have stifled further intelligent debate.

For those who hesitate to stand up before a large crowd at a microphone, there is an alternative to provide comment. The opportunity to provide written comments shouldn't be passed up. Not only does it not restrict the length of comments, but it also allows for comments that are perhaps more focused and organized than when speaking before a large crowd.

Those comments are important to the development of this whole process, but equally important is the respect we afford each other. There's no room for disparaging comments about people's character, regardless of which side they come from. There doesn't have to be a hateful reason behind someone's differing viewpoint, either.

But this is a unique chance to exercise our right to speak up on the issue and let our government know what we think. Let's just make sure those comments are respectful.

This may be a prime time for neighbors to agree to disagree. Then let's move on.

With all of the problems in the valley that deserve our concerted effort, let's not let this volatile issue be a lightning bolt that splits this community any further apart.