TCP/IP%20based%20TML%20(Transport%20Mapping%20Layer)%20for%20ForCES%20Protocol

1
TCP/IP based TML (Transport Mapping Layer) for
ForCES Protocol

• Hormuzd Khosravi
• Shuchi Chawla
• Furquan Ansari
• Jon Maloy
• 65th IETF Meeting, Dallas

2
Topics

• Areas updated
• Details on the updates
• Opens
• Summary

3
Areas Updated

• Data Channel Protocol
• TML Service Interface
• Added IPSec Usage
• High Availability

4
Data Channel Protocol

• Protocol related changes
• TCP no longer specified as protocol for the data
  channel
• DCCP will be used as data channel (default CCID
  2, same as TCP CC)
• Rough consensus from last WG meeting and email
  exchanges
• Added IANA requirement for DCCP

5
TML Service Interface

• Provides a service interface to an upper layer
  protocol (PL)
• Moved this section to the Appendix
• Should we eliminate this given there is a
  separate draft on this?
• This will introduce a synchronization problem
  between the drafts
• TML Service Interface Usage Model maintained as
  draft section

6
IPSec Usage Model

• IPSec Usage for TML security
• Can be used to secure both control and data
  channel
• TLS Usage model only limited to control channel
  since based on TCP
• No Security Mode also added
• For Single box, secured environment

7
High Availability

• TBD - Liveliness of the Data channel
• Options-
• Carry PL heartbeat on both control and data
  channels
• Use TML generated heartbeat for data channel
• This will re-introduce TML messaging
• Do not support this for data channel
• Feedback?

8
Opens/Under investigation

• High Availability TBD (data channel liveliness)
• Removal of TML Service Interface
• Manageability sectionDo we need it for this
  draft?

9
Summary

• Addressed feedback from the last session on the
  following
• Data Channel
• TML Service Interface
• Any final comments on the draft?
• Authors would like to issue a WG last call

10
Backup