html5-img
1 / 18

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

TCP/IP based TML (Transport Mapping Layer) for ForCES Protocol. Hormuzd Khosravi Shuchi Chawla Furquan Ansari Jon Maloy 66 th IETF Meeting, Montreal. Topics. Areas updated Details on the updates Opens Summary. Areas Updated. High Availability – Data channel liveliness

tamyra
Télécharger la présentation

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

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. TCP/IP based TML (Transport Mapping Layer) for ForCES Protocol Hormuzd Khosravi Shuchi Chawla Furquan Ansari Jon Maloy 66th IETF Meeting, Montreal

  2. Topics • Areas updated • Details on the updates • Opens • Summary

  3. Areas Updated • High Availability – Data channel liveliness • TML Service Interface • Clarifications, Editorial changes

  4. High Availability Liveliness of the Data channel a) The TML will propagate any DCCP generated connectivity loss indications to the TML b) If the PL wishes more active monitoring, then the PL should arrange for a suitable redirect packet to be sent from the FE to the CE at regular intervals. (There is no need for a bidirectional check.)

  5. TML Service Interface • Moved this section to the Appendix • Added Note- Note that this is just an overview for understanding the protocol initialization/shutdown sequences. It is by no means complete; the complete service interface is being specified in a separate draft.

  6. Clarifications/Updates Thanks Joel for the feedback! • Correction to Protocol Initialization section • Clarification on security section • Clarification on Prioritization • Editorial updates

  7. Opens/Under investigation • Manageability section…Do we need it for this draft? • Given that Applicability draft section is going to address Manageability in general for ForCES

  8. Summary • Addressed feedback from the last WG session and mailing list • Any final comments on the draft? • Authors would like to issue a WG last call

  9. Backup

  10. Protocol for Data Channel • May need further investigation • Other options: • Datagram Congestion Control Protocol (DCCP) • Provides congestion control but not reliable (which satisfies requirements for data channel) • Experimented with this but no stable implementation available at this point • Generic Routing Encapsulation (GRE) Tunneling • Encapsulate data packets in a GRE header  data channel is a GRE tunnel • Rate limiting may be done by the FE to provide support for congestion control • Consider other tunneling protocols

  11. TML Service Interface (contd.) • tmlInit: Enable establishment of channels. [CE] • tmlOpen: Set up unicast channels for both control and data messaging. [FE] • tmlClose: Shut down channels for both control and data messaging. [CE or FE] • tmlWrite: Send a control or data message over a channel. [CE or FE] • tmlRead: Read a control or data message over a channel. [CE or FE] • tmlMulticastGroupJoin: Request an FE to join a multicast group. [CE] • tmlMulticastGroupLeave: Request an FE to leave a multicast group. [CE]

  12. TML Service Interface Usage: Channel Setup FE PL FE TML CE TML CE PL tmlInit () CE init/ boot up tmlOpen(Cc) Ctrl chan (Cc) setup Setup control channel FeId  [CcDes(ctrl)] Ctrl chan (Cc) rsp CeId  [CcDes(ctrl)] Data chan (Cd) setup Setup data channel FeId  [CcDes(ctrl), CdDes(data)] Data chan (Cd) rsp CeId  [CcDes(ctrl), CdDes(data)] status tmlEvent (chUp) tmlEvent (chUp) Association, capability, topology info STEADY STATE OPERATION tmlWrite (FeId, ctrl) tmlRead(CeId, ctrl)

  13. TML Service Interface Usage: Multicast Group Join FE1 PL FE1 TML CE TML CE PL STEADY STATE OPERATION PL level control message MC Grp Join Req (McId) FE TML maintains mapping b/w PL IDs and TML descriptors tmlJoin (McId) McId = {FE1_ChDes} status MC Grp Join Rsp (McId) FE TML maintains mapping b/w PL IDs and TML descriptors tmlJoin (McId) McId = {FE1_ChDes} status tmlWrite (McId) Similarly, FE2 join results in McId = {FE1_ChDes, FE2_ChDes}

  14. TML Service Interface Usage: Multicast Group Leave FE1 PL FE1 TML CE TML CE PL STEADY STATE OPERATION PL level control message MC Grp Leave Req (McId) FE TML maintains mapping b/w PL IDs and TML descriptors tmlLeave (McId) McId ={FE2_ChDes} status MC Grp Leave Rsp (McId) tmlLeave (McId) FE TML maintains mapping b/w PL IDs and TML descriptors McId = {FE2_ChDes} status

  15. TML Messaging Removal of TML Messaging • No TML Layer messaging for control messages • No encapsulation done at the TML layer for control messages • TML transports messages from the PL Layer encapsulated in a TCP/IP header

  16. CE-FE Communication Channels Modifications to channel setup • Single TML call by PL to set up channels for control and data messaging • PL unaware of number of channels setup • TML maintains mapping between PL layer addresses (CE/FE IDs) and the channel descriptors it allocates • No TML channel descriptors returned to PL • PL uses the FE/CE IDs for read/write calls and specifies message type (control/data); TML maps to appropriate channel to send the message

  17. Multicast Model Multicast configuration changes • CE initiated multicast group setup • TML maintains mapping between PL Layer Multicast IDs and TML assigned channel descriptors • No TML messaging involved in setup of multicast group

  18. Addressing Address mapping updates • TML allocates channel descriptors • PL is only aware of CE/FE IDs; unaware of TML channel descriptors • TML maintains mapping between PL layer CE/FE IDs/addresses and the channel descriptors

More Related