1 / 15

Review of draft-ietf-gsmp-04

Review of draft-ietf-gsmp-04. Avri Doria, Nokia Fiffi Hellstrand, Nortel Networks Kenneth Sundell, Nortel Networks Tom Worster, Ennovate Networks Adelaide AU Thursday 30 March, 2000. Changes from -02. Added list of contributors to document Ch 1 _ Introduction Minor wording changes

florence-brady
Download Presentation

Review of draft-ietf-gsmp-04

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. Review of draft-ietf-gsmp-04 Avri Doria, NokiaFiffi Hellstrand, Nortel NetworksKenneth Sundell, Nortel Networks Tom Worster, Ennovate Networks Adelaide AU Thursday 30 March, 2000

  2. Changes from -02 • Added list of contributors to document • Ch 1 _ Introduction • Minor wording changes • Ch 2 - GSMP Encapsulations • Encapsulation Information moved to draft-ietf-gsmp-encaps-00.txt • Ch 3 - Common Defintions and Procedures • Restructured to remove redundancy from following chapters, especially Ch 4 • Added SubMessage Indicator, Count, and Message Length • Moved Failure Response Messages to Appendix A • Added description of label usage including description of TLV labels Note: Items in itallics are covered in more detail in later slides or presentations

  3. Changes from -02……….cont'd • Ch 4 - Connection • Added Reservation ID • Added Input Service Selector & Output Traffic Parameter Block • Added Encapsulation Method • Separated out ATM specific procedures • Delete Port Message replaced by Delete Output Port and Delete Input Port • Move Branch Message replaced byMove Output Branch Message and Move Input Branch Message • Ch 5 - Reservation Messages Chapter Added • Reservation Request Message • Delete Reservation Message • Delete All Reservation Message

  4. Changes from -02……….cont'd • Ch 6 - Management • Added Flow Control Flags to Port Management Message • Add Multipoint Query Label to Label Range message • Add Disjoint label support to Label Range Messagequery and response • Ch 7 - State and Statistics - no change • Ch 8 - Configuration • Added Max Reservation count to Switch Configuration Message • Addition of port types; FR, MPLS, CES (E1, D1, E3, D3) • Added Event Sequence Number and Event Flags to PortConfiguration Message response • Port Type specific Data Section expanded for additional port types

  5. Changes from -02……….cont'd • Ch 9 - Events • ReturnReceipt flag added to force controller to acknowledgereceipt of Alarm • Added Adjacency Update Message • Ch 10 - Service Model • Addition of Circuit Emulation Service information • Other traffics parameters added • Ch 11 - Adjacency Message moved here • Added Support for Multiple Controller Adjacency • Ch 12 - Failure Response codes description updated and moved here. • Appendix A - Summary of messages updated and moved from chapter 12 • Appendix B - Added Assigned numbers

  6. Labels • Type Bit indicates whether a Short Label of TLV label was being used • Short Labels - traditional GSMP 28 bit label field • Addition of label type FR, MPLS, • TLV Labels • Stacked Labels • Replaced E(xtended) designation for S bit to indicate Stacked LabelStacked Labels are treated as a single label • All Labels in spec designated as: +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |T|S|x|x| Label | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Removed all references to extended labels in the messages themselves. Any label can be a stacked label (indicated by S). T indicates whether label is short or TLV.

  7. TLV Labels +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |T|S|x|x| Label Type | Label Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | ~ Label Value ~ | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ • Label Type A 12-bit field indicating the type of label. • Label Length A 16-bit field indicating the length of label in octets

  8. TLV Label Types Defined • TLV Label Type ATM Label 0x100 FR Label 0x101 MPLS Gen Label 0x102 FEC Label 0x103 DS3-DS1 Label 0x200 E3-E1 Label 0x201 Structured -DS1 Label 0x202 Unstructured -DS1 Label 0x203 Structured -E1 Label 0x204 Unstructured -E1 Label 0x205

  9. Adaptation Method • Adaptation MethodThe adaptation method is used to define the adaptation framing that may be in use when moving traffic from one port type to another port type; e.g. from a frame relay port to an ATM port.The content of this field is defined by the Opaque flag. If the Opaque flag is set, then this field is defined by the switch manufacturer and is not defined in this protocol. If the opaque flag is not set, the field is divided into two 12-bit fields as follows: +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |IQS|OQS|P|x|N|O| Input Adaptation | Output Adaptation | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Adaptation Types: 0x100 PPP0x200 FRF.50x201 FRF.8

  10. Flow Control changes +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Event Flags | Flow Control Flags | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ • Event Flags Field in the request message is used to reset the Event Flags in the switch port indicated by the Port field. Each Event Flag in a switch port corresponds to a type of Event message. When a switch port sends an Event message it sets the corresponding Event Flag on that port. Depending on the setting in the Flow Control Flag, a port is either subject to flow control or not. If it is subject to flow control then it is not permitted to send another Event message of the same type before the Event Flag has been reset. To reset an event flag, the Function field in the request message is set to "Reset Flags." For each bit that is set in the Event Flags field, the corresponding Event Flag in the switch port is reset.

  11. Flow Control changes cont'd • Flow Control Flags FieldThis flags in this field are used to indicate whether the flow control mechanism described in the Events Flag field is turned on or not. If the Flow Control Flag is on, then the flow control mechanism for that event on that port is activated. To toggle flow control, the Function field in the request message is set to "Reset Flags." For each bit that is set in the Flow Control Flags field, the flow control corresponding Event in the switch port is toggled.

  12. Flow Control - example Trigger Event Flag Flow Control Flag Action t0 0 1 event 1 1 message sent event 1 1 no message sent Reset Event Flag 0 1 event 1 1 message sent event 1 1 no message sent Toggle Flow Control 1 0 event 1 0 message sent event 1 0 message sent Toggle Flow Control 1 1 event 1 1 no message sent

  13. Label Range Message +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Version | Message Type | Result | Code | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Partition ID | Transaction Identifier | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Port | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Port Session Number | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |Q|M|D|x| Range Count | Range Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | ~ Label Data Block ~ | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Q - Query flag M - Multicast D - Disjoint Range

  14. Label Range Message cont'd • Each element of the Label Data Block has the following format: +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |T|S|V|x| Min Label | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |T|S|x x| Max Label | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Remaining Labels | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ • V: VP LabelThe Label flag use is ATM port type specific.

  15. Reservation Messages • Reservations are hard state objects in the switch that can be created by the controller by sending a Reservation Request message. • Each Reservation is uniquely identified by an identifying number called a Reservation ID. • Reservation objects can be deleted with the Delete Reservation message or the Delete All Reservations message. • A reservation object is also deleted when the Reservation is Deployed by specifying a Reservation ID in an Add Branch message. • A Reservation object includes its Reservation ID plus all the switch state associated with a branch with the exception that the branch’s input label and/or output label may be unspecified. • The switch established the maximum number of reservations it can store by setting the value of Max Reservations in the Switch Configuration response message. • The switch indicates that it does not support reservations by setting Max Reservations to 0. • Reservation Request Message = 70 • Reservation Delete Message = 71 • Delete All Reservations = 72

More Related