The working group is responsible for completing the standardization of the GSMP protocol by responding to protocol issues that arise during implementation of the current specifications.
Additionally, the working group is responsible for augmenting the protocol as follows:
- Support for Optical and Other Extensions and CCAMP Features
The architecture of some optical, TDM, spatial and other switch types makes the ability to remotely control the connection state of a switch important. GSMP has been designed especially for such remote control operations. GSMP is, however, currently lacking in the specific semantics necessary for switches with some new technologies, especially in the optical space. The WG will collect requirements and define solutions to support optical and other new switching technologies, compatibly with the common control and measurement protocols WG (CCAMP) work. This work will be done in cooperation with the other Sub IP Working groups involved in this area.
The extensions will include definition of new instances of "labels" (for instance lambda identifiers) as needed, to support the usage in the new technologies. They will also include definitions of port types, of service definitions and of traffic parameters.
- Switch Partitioning
The current version of GSMP is designed to work with a static switch partition. Recently, some regulatory environments (on multiple continents) have mandated multi-provider access to the same physical infrastructure. Therefore, this work should allow network operators to dynamically open their forwarders (optical, TDM, and other switch types) to multiple administrative domains of control. As a result, the WG will analyze requirements for dynamic switch partioning with GSMP and determine if GSMP should be extended to support them. This work would be to adapt GSMP to work with multiple partitions in which resource allocation is dynamic and variable between the switch partitions. This would be achieved by using available management tools, e.g. MIBs (possibly PIBs), as well as potential extensions to GSMP.
- Relationship to Forwarding and Control Element Separation
The WG will conduct a brief (one-meeting) analysis of the potential use of GSMP in mechanisms that allow third party network processors in switch architectures. The output will be an agreement of the likely scope for a distinct WG that might be using GSMP for this purpose.
| Done | Define an IP encapsulation for GSMP messages | |
| Done | Extend GSMP message types to allow support of non-ATM Label Switch devices | |
| Done | Refine the support for QoS models in GSMP | |
| Done | Define an approved GSMP MIB | |
| Done | Define approved mechanisms for security and authentication in GSMP | |
| Done | Produce a version of the GSMP which has the consensus required for entry onto the standards track. | |
| Done | Analyze role of GSMP for control element separation and make recommendation as to a separate WG for extending GSMP for this | |
| May 01 | Document requirements for control of switches supporting optical, TDM and other CCAMP features | |
| Aug 01 | Submit GSMPv3 extensions to include control of switches supporting optical, TDM and other CCAMP features and any updates of the base spec for Proposed Standard | |
| Sep 01 | Document requirements for switch partitioning and determine whetherto recharter to extend GSMP capabilities to meet these | |
| Dec 01 | If requirements process has convinced ADs/IESG, produce GSMP extensions and MIBs to support dynamic switch partitioning | |
| Jun 02 | Submit GSMPv3, its extensions and MIBs for Draft Standard | |
| Jun 02 | Conclude Working Group |
Current Meeting Report
Minutes GSMP WG 53rd IETF, Minneapolis March 2002
Chairs: Avri Doria <avri@sm.luth.se>
Kenneth Sundell <ksundell@nortelnetworks.com>
Note taker: John Sauer
1. Agenda review (Avri)
One change to the agenda. After the optical requirements there will be a talk on ITU requirements.
2. Document Status
draft-ietf-gsmp-11.txt
draft-ietf-gsmp-mib-07.txt
draft-ietf-gsmp-applicability-02.txt
draft-ietf-gsmp-encaps-05.txt
There is little to say. The first three have been approved by the IESG and are in the RFC editor queue. How long it will not take is not known.
A new abstract was needed for the draft-ietf-gsmp-11.txt.
3. Status of Design groups -
Optical Requirements
- GSMP V3 extensions - J. Sadler
Changes are motivated by implementation experience. Suggestions for impovements were put in the requirements draft; e.g. window size, retransmission, delete branch, clarification of adjacency text, event return receipt.
The main focus of the document was a set of requirements on changes necessary for optical support.
- ITU-T SG15 Official Representative to IETF GSMP - J. Sadler
The ITU is intersted in establishing a relationship. Why is this needed? Because G.ASTN needs same function as GSMP provides for its CCI. Two way reports will take place (IETF<->ITU-T). This will bridge the gap with the ITU. The GSMPv3 extensions document should be presented by the 4/29 SG15 plenary. This does not need to be the final document and can be a working document. Merging should be done in the next two weeks.
The Working group last call should be 1-2 months, after comments from ITU are be folded in
-Dynamic Partition Requirements draft-ietf-gsmp-dyn-part-reqs-01.txt
Two issues were brought up.
1. Terminology of NE. It is now called Switching Element
2. Cardinality between controllers and switch parts fixed.
As there were no other comments: Is this ready for last call?
(Sadler) Same comment from Forces. Partition stacking can have STS-1s allocated to different controllers. It must be logical.
(Avri) This is not mentioned nor precluded (recursive partitioning) in the document.
(Sadler) GSMPV3 drafts are showing a problem in the realization.
(Avri) Do we need new text?
(Sadler) I will add some text before last call.
(Chair) Please read the document because of the new concepts and let us know if it is clear. In terms of partitioning, the IESG has not approved this work, only the requirements. To do further work they must first approve and milestones need to be established.
4. Milestone discussion (Avri)
the WG is late meeting most of the milestones. Corrections we discussed at the last meeting, but the chair (Avri) forgot to submitt them. They needed to be reviewed again to make sure they are still correct.
The following updates were agreed to by the group.
May 02 Document requirements for control of switches supporting optical, TDM and other CCAMP features
Dec 02 Submit GSMPv3 extensions to include control of switches supporting optical, TDM and other CCAMP features and any updates of the base spec for Proposed Standard
May 02 Document requirements for switch partitioning and determine whetherto recharter to extend GSMP capabilities to meet these
Sep 02 If requirements process has convinced ADs/IESG, produce GSMP extensions and MIBs to support dynamic switch partitioning
Jun 03 Submit GSMPv3, its extensions and MIBs for Draft Standard
Jun 03 Conclude Working Group
No other issues.
There was anannouncement that Inter-op testing with the MSF was still possible, however, there hadn't been any implementations announced as avaialble for test.
Developers were encouraged to repsond either list or privatly.
The meeting was adjourned.
Slides
Agenda
GSMPv3 Extensions Update