draft-ietf-forces-interoperability-03.txt   draft-ietf-forces-interoperability-04.txt 
Internet Engineering Task Force E. Haleplidis Internet Engineering Task Force E. Haleplidis
Internet-Draft University of Patras Internet-Draft University of Patras
Intended status: Informational K. Ogawa Intended status: Informational K. Ogawa
Expires: February 8, 2010 NTT Corporation Expires: March 11, 2010 NTT Corporation
X. Wang X. Wang
Huawei Technologies Co., Ltd. Huawei Technologies Co., Ltd.
C. Li C. Li
Zhejiang Gongshang University Zhejiang Gongshang University
August 7, 2009 September 7, 2009
ForCES Interoperability Draft ForCES Interoperability Draft
draft-ietf-forces-interoperability-03 draft-ietf-forces-interoperability-04
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.
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.
skipping to change at page 1, line 37 skipping to change at page 1, line 37
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 8, 2010. This Internet-Draft will expire on March 11, 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 42 skipping to change at page 2, line 42
6.1. Scenario 1 - Pre-association Setup . . . . . . . . . . . . 12 6.1. Scenario 1 - Pre-association Setup . . . . . . . . . . . . 12
6.2. Scenario 2 - TML priority channels connection . . . . . . 13 6.2. Scenario 2 - TML priority channels connection . . . . . . 13
6.3. Scenario 3 - Association Setup - Association Complete . . 13 6.3. Scenario 3 - Association Setup - Association Complete . . 13
6.4. Scenario 4 - CE query . . . . . . . . . . . . . . . . . . 13 6.4. Scenario 4 - CE query . . . . . . . . . . . . . . . . . . 13
6.5. Scenario 5 - Heartbeat monitoring . . . . . . . . . . . . 14 6.5. Scenario 5 - Heartbeat monitoring . . . . . . . . . . . . 14
6.6. Scenario 6 - Simple Config Command . . . . . . . . . . . . 14 6.6. Scenario 6 - Simple Config Command . . . . . . . . . . . . 14
6.7. Scenario 7 - Association Teardown . . . . . . . . . . . . 14 6.7. Scenario 7 - Association Teardown . . . . . . . . . . . . 14
7. Tested Features . . . . . . . . . . . . . . . . . . . . . . . 16 7. Tested Features . . . . . . . . . . . . . . . . . . . . . . . 16
7.1. ForCES Protocol Features . . . . . . . . . . . . . . . . . 16 7.1. ForCES Protocol Features . . . . . . . . . . . . . . . . . 16
7.1.1. Protocol Messages . . . . . . . . . . . . . . . . . . 16 7.1.1. Protocol Messages . . . . . . . . . . . . . . . . . . 16
7.1.2. MainHeader Handling . . . . . . . . . . . . . . . . . 17 7.1.2. MainHeader Handling . . . . . . . . . . . . . . . . . 16
7.1.3. TLV Handling . . . . . . . . . . . . . . . . . . . . . 17 7.1.3. TLV Handling . . . . . . . . . . . . . . . . . . . . . 17
7.1.4. Operation Types Supported . . . . . . . . . . . . . . 18 7.1.4. Operation Types Supported . . . . . . . . . . . . . . 17
7.1.5. ForCES Protocol Advanced Features . . . . . . . . . . 18
7.2. ForCES Model Features . . . . . . . . . . . . . . . . . . 18 7.2. ForCES Model Features . . . . . . . . . . . . . . . . . . 18
7.2.1. Basic Atomic Types Supported . . . . . . . . . . . . . 18 7.2.1. Basic Atomic Types Supported . . . . . . . . . . . . . 18
7.2.2. Compound Types Supported . . . . . . . . . . . . . . . 18 7.2.2. Compound Types Supported . . . . . . . . . . . . . . . 18
7.2.3. LFBs Supported . . . . . . . . . . . . . . . . . . . . 19 7.2.3. LFBs Supported . . . . . . . . . . . . . . . . . . . . 18
7.2.3.1. FE Protocol LFB . . . . . . . . . . . . . . . . . 19 7.2.3.1. FE Protocol LFB . . . . . . . . . . . . . . . . . 19
7.2.3.2. FE Object LFB . . . . . . . . . . . . . . . . . . 19 7.2.3.2. FE Object LFB . . . . . . . . . . . . . . . . . . 19
7.3. ForCES SCTP-TML Features . . . . . . . . . . . . . . . . . 20 7.3. ForCES SCTP-TML Features . . . . . . . . . . . . . . . . . 20
7.3.1. TML Priority Ports . . . . . . . . . . . . . . . . . . 20 7.3.1. TML Priority Ports . . . . . . . . . . . . . . . . . . 20
7.3.2. Message Handling at specific priorities . . . . . . . 20 7.3.2. Message Handling at specific priorities . . . . . . . 20
8. Test details . . . . . . . . . . . . . . . . . . . . . . . . . 22 8. Test details . . . . . . . . . . . . . . . . . . . . . . . . . 22
9. Results . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 9. Results . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 29 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 29
11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 30 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 30
12. Security Considerations . . . . . . . . . . . . . . . . . . . 31 12. Security Considerations . . . . . . . . . . . . . . . . . . . 31
skipping to change at page 16, line 11 skipping to change at page 16, line 11
The following ForCES protocol messages will be exchanged: The following ForCES protocol messages will be exchanged:
o Association Teardown Message o Association Teardown Message
7. Tested Features 7. Tested Features
The features that were tested are: The features that were tested are:
7.1. ForCES Protocol Features 7.1. ForCES Protocol Features
+------------+
| Feature |
+------------+
| Batching |
| |
| HeartBeats |
+------------+
ForCES Protocol Features
Although Batching was not initially designed to be tested, it was
tested during the interoperability test.
7.1.1. Protocol Messages 7.1.1. Protocol Messages
+----------------------------+ +----------------------------+
| Protocol Message | | Protocol Message |
+----------------------------+ +----------------------------+
| Association Setup | | Association Setup |
| | | |
| Association Setup Response | | Association Setup Response |
| | | |
| Association TearDown | | Association TearDown |
skipping to change at page 18, line 23 skipping to change at page 18, line 5
| | | |
| Get | | Get |
| | | |
| Get Response | | Get Response |
| | | |
| Report | | Report |
+--------------+ +--------------+
Operation Type Supported Operation Type Supported
7.1.5. ForCES Protocol Advanced Features
+------------+
| Feature |
+------------+
| Batching |
| |
| HeartBeats |
+------------+
ForCES Protocol Advanced Features
Although Batching was not initially designed to be tested, it was
tested during the interoperability test.
7.2. ForCES Model Features 7.2. ForCES Model Features
7.2.1. Basic Atomic Types Supported 7.2.1. Basic Atomic Types Supported
+-------------+ +-------------+
| Atomic Type | | Atomic Type |
+-------------+ +-------------+
| uchar | | uchar |
| | | |
| uint32 | | uint32 |
 End of changes. 9 change blocks. 
20 lines changed or deleted 23 lines changed or added

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