IETF/BoF60 Report Whereabouts: IETF60, Behave (Behavior Engineering for Hindrance AVoidancE) BoF, Tuesday August 04th 2004 Chairs: Cullen Jennings , Jiri Kuthan Scribe: Alan Johnston Presentations: (attachments TO BE INCLUDED) - Cullen Jennings: WG Proposal - Francois Audet: draft-audet-nat-behave-00.txt The behave BOF discussed forming a WG to define the behavior of NATs. The draft charter that was discussed at the BOF is at: http://www.ietf.org/ietf/04aug/behave.txt At the end there was strong consensus of the 140 people in the room that a WG should be formed. There was discussion about some of the following key points: Should the output documents be BCP or informational? Conclusion was BCP after some discussion; people felt the output should be BCP, not informational. Concern over overlap with V6ops. Decided to remove mention of 6 to 4 in charter. Current schedule is wildly optimistic. People thought that Mar 05 might be achievable for UDP but Mar 06 was more likely for rest of protocols. Given they are BCPs, time will be needed to talk to a significant group of users. ALGs are out of scope. Discussed having each of the various protocol groups do its own document but decided it was better to do them all in one place. The analogy of sex education was brought up for this work. Everyone is using NATs: better to provide some behavioral guidance and reduce the harm they cause than to wish they did not exist. Plan Suggestions: ----------------- I think the following suggestions came from the BOF and are useful: - begin this effort - there was a very strong consensus hum - make the deliverables BCP - split the deliverables by protocol - make the first deliverable be UDP - host the protocol-specific work in behave as opposed to introducing inter-WG dependencies; let the parties interested in the specific protocols come with their expertise - charter suggestions: explicitly exclude application dependencies - clean up terminology - RFCs produced by NAT WG have become outdated; draft-audet-nat has some issues (mixing firewall behavior with NATs' packet matching techniques, NAT versus NAPT, etc.) An update to the proposed charter based on the comments from the BOF is at https://scm.sipfoundry.org/rep/ietf-drafts/behave/charter.txt Raw Minutes from multiple people are at http://scm.sipfoundry.org/rep/ietf-drafts/behave/ietf-60-raw-minutes.txt