More TWAMP

1
More TWAMP Mixed Security Mode Extension and
Modes Field Registry

• draft-ietf-ippm-more-twamp-00
• Al Morton, Kaynam Hedayat
• November, 2008

2
Security Modes MUST Match

• RFC4656 OWAMP requires TEST to match the CONTROL
  protocol.
• All OWAMP-Test sessions that are spawned by an
  OWAMP-Control session inherit its mode.
• Maybe clarify with a MUST in Errata

3
Security Modes Mandatory to Implement

• Secure modes may see more widespread use on the
  Control Protocol IF
• Test protocol can run Unauthenticated
• ALL resources on accuracy and scale when
  limitations are reached

4
Mode Field Extension

• -----------------------------------------------
  -----
• Protocol Permissible Mode Combinations
• -----------------------------------------------
  -----
• Control Unauth. Auth. ltgt
  Encrypted
• -----------------------------------------------
  -----
• Unauth. Unauth.
• --------------------------------------
  -----
• Test Auth.
• --------------------------------------
  -----
• Encrypted
• -----------------------------------------------
  -----

5
Mixed-Mode Extension (new registry needed)

• Value Description Reference/Explanati
  on
• 0 Reserved
• 1 Unauthenticated RFC4656,
  Section 3.1
• 2 Authenticated RFC4656,
  Section 3.1
• 4 Encrypted RFC4656,
  Section 3.1
• 8 Unauth. TEST protocol, new bit
  position (3)
• Encrypted CONTROL
• NOTE only ONE new mode is needed!

6
Mode Field Extension Compatibility (easy!)

• C-C Server
• ----------gt TCP SYN
• lt---------- SYN-ACK
• ----------gt ACK
• lt---------- Server Greeting
• Current TWAMP sets bits 0-2
• Mixed-Mode Extension, bit 3
• ----------gt Set-Up-Response

7
Next Step for IPPM WG

• This is very simple extension
• Adds one new communication mode, using existing
  features
• Creates a Mode Registry needed for any future
  features
• PROPOSAL WGLC on this WG draft.