Last Modified: 2003-06-13
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 | |
Done | Document requirements for control of switches supporting optical, TDM and other CCAMP features | |
Done | Document requirements for switch partitioning and determine whetherto recharter to extend GSMP capabilities to meet these | |
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 | |
Jun 03 | Submit GSMPv3, its extensions and MIBs for Draft Standard | |
Jun 03 | Conclude Working Group |
kireeti GSMP Working Group minutes IETF57 Notes taken by Jonathan Sadler. The meeting was chaired by Kenneth Sundell and was scheduled for an hour. Topics covered included: - changes to the Base GSMP document including o Triggered add o Block add o removal of technology specific content - changes to the Packet spec o Label Type ranges updated o Stacking Section removed o Capability sets added - changes to optical spec o reservation message for recovery o addition of technology specific block for recovery o add of new short message for data burst o discussion about terminology following what is being done in ccamp for GMPLS Comment: There are some difference developing between the docs. There was an open meeting schedule for later in the IETF week to discuss the docs. Editors requested to attends with other being welcome. Details of the discussions to be discussed on the mailing list. All provisional decisions to be discussed and confirmed on the WG mailing list. - Discussion on Capability sets o each technology to have it own section and range of values o discussion of keeping it a fixed size or making variable. - opinions in favor of variable size especially for multi-layer support. - issue to be resolved on mailing list. - Discussion of triggered add message o quiet room o WG list to be asked again if the message will do - Discussion of bulk add message o predominant question of whether this form of the message meets the requirements in the requirement document. List to be inquired. - Discussion of protection o 1+1 added as argument to Add Branch o other modes still need solution. o issue to be discussed on the |