draft-ietf-forces-sctptml-05.txt   draft-ietf-forces-sctptml-06.txt 
Network Working Group J. Hadi Salim Network Working Group J. Hadi Salim
Internet-Draft Mojatatu Networks Internet-Draft Mojatatu Networks
Expires: February 12, 2010 K. Ogawa Intended status: Standards Track K. Ogawa
NTT Corporation Expires: April 2, 2010 NTT Corporation
August 11, 2009 September 29, 2009
SCTP based TML (Transport Mapping Layer) for ForCES protocol SCTP based TML (Transport Mapping Layer) for ForCES protocol
draft-ietf-forces-sctptml-05 draft-ietf-forces-sctptml-06
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79. This document may contain material
from IETF Documents or IETF Contributions published or made publicly
available before November 10, 2008. The person(s) controlling the
copyright in some of this material may not have granted the IETF
Trust the right to allow modifications of such material outside the
IETF Standards Process. Without obtaining an adequate license from
the person(s) controlling the copyright in such materials, this
document may not be modified outside the IETF Standards Process, and
derivative works of it may not be created outside the IETF Standards
Process, except to format it for publication as an RFC or to
translate it into languages other than English.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on February 12, 2010. This Internet-Draft will expire on April 2, 2010.
Copyright Notice Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the Copyright (c) 2009 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents in effect on the date of Provisions Relating to IETF Documents in effect on the date of
publication of this document (http://trustee.ietf.org/license-info). publication of this document (http://trustee.ietf.org/license-info).
Please review these documents carefully, as they describe your rights Please review these documents carefully, as they describe your rights
skipping to change at page 2, line 10 skipping to change at page 3, line 7
Abstract Abstract
This document defines the SCTP based TML (Transport Mapping Layer) This document defines the SCTP based TML (Transport Mapping Layer)
for the ForCES protocol. It explains the rationale for choosing the for the ForCES protocol. It explains the rationale for choosing the
SCTP (Stream Control Transmission Protocol) [RFC4960] and also SCTP (Stream Control Transmission Protocol) [RFC4960] and also
describes how this TML addresses all the requirements described in describes how this TML addresses all the requirements described in
[RFC3654] and the ForCES protocol [FE-PROTO] draft. [RFC3654] and the ForCES protocol [FE-PROTO] draft.
Table of Contents Table of Contents
1. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Protocol Framework Overview . . . . . . . . . . . . . . . . . 3 3. Protocol Framework Overview . . . . . . . . . . . . . . . . . 4
3.1. The PL . . . . . . . . . . . . . . . . . . . . . . . . . . 4 3.1. The PL . . . . . . . . . . . . . . . . . . . . . . . . . . 5
3.2. The TML . . . . . . . . . . . . . . . . . . . . . . . . . 5 3.2. The TML . . . . . . . . . . . . . . . . . . . . . . . . . 6
3.2.1. TML and PL Interfaces . . . . . . . . . . . . . . . . 5 3.2.1. TML and PL Interfaces . . . . . . . . . . . . . . . . 6
3.2.2. TML Parameterization . . . . . . . . . . . . . . . . . 6 3.2.2. TML Parameterization . . . . . . . . . . . . . . . . . 7
4. SCTP TML overview . . . . . . . . . . . . . . . . . . . . . . 6 4. SCTP TML overview . . . . . . . . . . . . . . . . . . . . . . 7
4.1. Rationale for using SCTP for TML . . . . . . . . . . . . . 8 4.1. Rationale for using SCTP for TML . . . . . . . . . . . . . 9
4.2. Meeting TML requirements . . . . . . . . . . . . . . . . . 9 4.2. Meeting TML requirements . . . . . . . . . . . . . . . . . 10
4.2.1. SCTP TML Channels . . . . . . . . . . . . . . . . . . 10 4.2.1. SCTP TML Channels . . . . . . . . . . . . . . . . . . 11
4.2.2. Satisfying TML Requirements . . . . . . . . . . . . . 15 4.2.2. Satisfying TML Requirements . . . . . . . . . . . . . 16
5. SCTP TML Channel Work . . . . . . . . . . . . . . . . . . . . 17 5. SCTP TML Channel Work . . . . . . . . . . . . . . . . . . . . 18
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18
7. Security Considerations . . . . . . . . . . . . . . . . . . . 17 7. Security Considerations . . . . . . . . . . . . . . . . . . . 18
7.1. IPsec Usage . . . . . . . . . . . . . . . . . . . . . . . 18 7.1. IPsec Usage . . . . . . . . . . . . . . . . . . . . . . . 19
7.1.1. SAD and SPD setup . . . . . . . . . . . . . . . . . . 19 7.1.1. SAD and SPD setup . . . . . . . . . . . . . . . . . . 20
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 19 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 20
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 19 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 20
9.1. Normative References . . . . . . . . . . . . . . . . . . . 19 9.1. Normative References . . . . . . . . . . . . . . . . . . . 20
9.2. Informative References . . . . . . . . . . . . . . . . . . 20 9.2. Informative References . . . . . . . . . . . . . . . . . . 21
Appendix A. Suggested SCTP TML Channel Work Implementation . . . 20 Appendix A. Suggested SCTP TML Channel Work Implementation . . . 21
A.1. SCTP TML Channel Initialization . . . . . . . . . . . . . 21 A.1. SCTP TML Channel Initialization . . . . . . . . . . . . . 22
A.2. Channel work scheduling . . . . . . . . . . . . . . . . . 21 A.2. Channel work scheduling . . . . . . . . . . . . . . . . . 22
A.2.1. FE Channel work scheduling . . . . . . . . . . . . . . 21 A.2.1. FE Channel work scheduling . . . . . . . . . . . . . . 22
A.2.2. CE Channel work scheduling . . . . . . . . . . . . . . 22 A.2.2. CE Channel work scheduling . . . . . . . . . . . . . . 23
A.3. SCTP TML Channel Termination . . . . . . . . . . . . . . . 22 A.3. SCTP TML Channel Termination . . . . . . . . . . . . . . . 23
A.4. SCTP TML NE level channel scheduling . . . . . . . . . . . 23 A.4. SCTP TML NE level channel scheduling . . . . . . . . . . . 24
Appendix B. Suggested Service Interface . . . . . . . . . . . . . 23 Appendix B. Suggested Service Interface . . . . . . . . . . . . . 24
B.1. TML Boot-strapping . . . . . . . . . . . . . . . . . . . . 24 B.1. TML Boot-strapping . . . . . . . . . . . . . . . . . . . . 25
B.2. TML Shutdown . . . . . . . . . . . . . . . . . . . . . . . 25 B.2. TML Shutdown . . . . . . . . . . . . . . . . . . . . . . . 26
B.3. TML Sending and Receiving . . . . . . . . . . . . . . . . 26 B.3. TML Sending and Receiving . . . . . . . . . . . . . . . . 27
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 27 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 28
1. Definitions 1. Definitions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119. document are to be interpreted as described in RFC 2119.
The following definitions are taken from [RFC3654]and [RFC3746]: The following definitions are taken from [RFC3654]and [RFC3746]:
ForCES Protocol -- The protocol used at the Fp reference point in the ForCES Protocol -- The protocol used at the Fp reference point in the
 End of changes. 5 change blocks. 
39 lines changed or deleted 49 lines changed or added

This html diff was produced by rfcdiff 1.37a. The latest version is available from http://tools.ietf.org/tools/rfcdiff/