BEHAVE Working Group

1
BEHAVE Working Group
Chair Dan Wing, dwing_at_cisco.com

• IETF 67

2
BEHAVE Agenda

• 900 Agenda and Document Status
• 910 Multicast (Dan)
• 915 STUNbis (Jonathan)
• 935 TCP (Philip)
• 945 ICMP (Fernando)
• 1015 NAT Behavior Discovery (Derek)
• 1025 Application Keepalives (Xavier)
• 1035 NAT Control STUN Usage (Jonathan)

3
N O T E W E L L

• Any submission to the IETF intended by the
  Contributor for publication as all or part of an
  IETF Internet-Draft or RFC and any statement made
  within the context of an IETF activity is
  considered an "IETF Contribution". Such
  statements include oral statements in IETF
  sessions, as well as written and electronic
  communications made at any time or place, which
  are addressed to
• the IETF plenary session,
• any IETF working group or portion thereof,
• the IESG, or any member thereof on behalf of the
  IESG,
• the IAB or any member thereof on behalf of the
  IAB,
• any IETF mailing list, including the IETF list
  itself, any working group or design team list, or
  any other list functioning under IETF auspices,
• the RFC Editor or the Internet-Drafts function
• All IETF Contributions are subject to the rules
  of RFC 3978 and RFC 3979.Statements made outside
  of an IETF session, mailing list or other
  function, that are clearly not intended to be
  input to an IETF activity, group or function, are
  not IETF Contributions in the context of this
  notice.
• Please consult RFC 3978 for details.

4
Administrative Items

• Note taker Spencer Dawkins
• Jabber scribe volunteer?

5
Document Status

• RFC Editors Queue
• NAT-UDP
• New Working Group document
• draft-ietf-behave-p2p-state
• Existing WG documents without presentations
• Turn-02 removed doors
• Turn-ipv6-01 updated, waiting for TURN
• Existing WG documents with presentations
• Multicast
• STUNbis (RFC3489bis)
• TCP
• ICMP
• Adopt draft-ford-behave-app-04 as our Application
  Milestone?
• Little discussion on the mailing list

6
Multicast

• Very little interest from working group
• One identified requirement for ASM
• Keep NAT binding open if ASM receiver sent RTCP
  Receiver Report
• No identified requirement for SSM
• Scope for IGMPv1? SSM-only?? ASM?
• Proposed steps
• revise document based on Magnus and Pekkas
  comments
• Push milestone after TCP, ICMP, TURN?

draft-ietf-behave-multicast-04