Download
1 / 10
100 likes | 205 Vues
This document proposes extending IntServ to convey multiple Traffic Spec or Flow Spec in a single RSVP message, enhancing network efficiency and resource allocation. It defines a method to prioritize preferred Traffic Specs or Flow Specs when multiple options exist. Backwards compatible and allows for optional MULTI_TSPEC Object.
E N D
draft-polk-tsvwg-intserv-multiple-tspec-02 IETF76 James Polk Subha Dhesikan
Scope of ID • This doc creates the optimization of conveying more than one Traffic Spec or Flow Spec the same RSVP signaling message (PATH and RESV) • IntServ, actually, defines the RSVP Objects containing Traffic Spec and Flow Spec (TSPEC and FLOWSPEC Objects), so this is proposing an extension to IntServ • This WG chose which of the multiple proposed approaches is to be retained to extend IntServ for this functionality – so this ID defines the one approach • Defines a means to indicate which Traffic Spec or Flow Spec is preferred when more than one exists draft-polk-tsvwg-intserv-multiple-tspec-02
Concept of IntServ Extension for Multiple Traffic Specs Sender Rtr-1 Rtr-2 Rtr-N Receiver | | | | | | PATH (with 3 Traffic Specs :12Mbps, 5Mbps, 1Mbps) | |------------->|--------->|--------->|-------------->| | | | | | | | | RESV (with 3 Flow Specs | | | | 12Mbps, 5Mbps & 1Mbps) | | | X <--------|<--------------| | Rtr-2 cannot grant 12Mbps | | | | | | | | RESV (with 2 Flow Specs| | | | 5Mbps & 1Mbps) | | | |<-------------|<---------| ResvErr BW reduc. to 5Mbps | | |--------->|-------------->| | | | | | draft-polk-tsvwg-intserv-multiple-tspec-02
Format of a RSVP PATH and sender descriptor <Path Message> ::= <Common Header> [ <INTEGRITY> ] <SESSION> <RSVP_HOP> <TIME_VALUES> [ <POLICY_DATA> ... ] [ <sender descriptor> ] <sender descriptor> ::= <SENDER_TEMPLATE> <SENDER_TSPEC> ^^^^^^^^^^^^ [ <ADSPEC> ] draft-polk-tsvwg-intserv-multiple-tspec-02
Extending sender descriptor with new optional MULTI_TSPEC Object Focusing on just the <sender descriptor> in the PATH: <sender descriptor> ::= <SENDER_TEMPLATE> <SENDER_TSPEC> ^^^^^^^^^^^^ [ <ADSPEC> ] • Need to keep SENDER_TSPEC as is, so add optional MULTI_TSPEC Object <sender descriptor> ::= <SENDER_TEMPLATE> <SENDER_TSPEC> [ <ADSPEC> ] [ <MULTI_TSPEC> ] • <MULTI_TSPEC> uses a new parameter ID (‘125’ proposed) • Fully backwards compatible • as optional ( “[ <> ]” ) Objects are ignored if not understood draft-polk-tsvwg-intserv-multiple-tspec-02
Repeated per Traffic Spec instance repeated per Traffic Spec instance MULTI_TSPEC Object 31 24 23 16 15 8 7 0 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1 | 0 (a) | reserved | 13 (b) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2 | X (c) |0| reserved | 12 (d) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3 | 125 (e) | 0 (f) | 5 (g) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 4 | Token Bucket Rate [r] (32-bit IEEE floating point number) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 5 | Token Bucket Size [b] (32-bit IEEE floating point number) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 6 | Peak Data Rate [p] (32-bit IEEE floating point number) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 7 | Minimum Policed Unit [m] (32-bit integer) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 8 | Maximum Packet Size [M] (32-bit integer) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 9 | 125 (e) | 0 (f) | 5 (g) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 10 | Token Bucket Rate [r] (32-bit IEEE floating point number) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 11 | Token Bucket Size [b] (32-bit IEEE floating point number) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 12 | Peak Data Rate [p] (32-bit IEEE floating point number) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 13 | Minimum Policed Unit [m] (32-bit integer) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 14 | Maximum Packet Size [M] (32-bit integer) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Figure 4. Multiple TSPECs for Controlled-Load service draft-polk-tsvwg-intserv-multiple-tspec-02
Merged What changed in -02 • Refined Merging rules to RECOMMEND: • For Controlled Load – the descending order of the Token Bucket Rate “r” parameter value • For Guaranteed Service – the descending order of the RSPEC Rate “R” parameter value • <MULTI-FLOWSPEC-1> = 5Mb/s, 2 Mb/s, 1 Mb/s • <MULTI-FLOWSPEC-2> = 10Mb/s, 5Mb/s, 1 Mb/s • <MULTI-FLOWSPEC> = 10Mb/s, 5Mb/s, 2Mb/s, 1 Mb/s draft-polk-tsvwg-intserv-multiple-tspec-02
What changed in -02 • Editorials: • Changed Calling Node and Called Node to Sender and Receiver, respectively • Made discussion about old Option’s #1 & 2 in appendix less detailed/complicated draft-polk-tsvwg-intserv-multiple-tspec-02
Open issues • Issue about just how many Traffic Specs/Flow Specs allowed in a single message? • Right now, text says 17 (1 + 16) • Probably should be lower • AD guidance on beefing up Security Considerations section • To be in next rev • What else should be added, modified, removed from doc? draft-polk-tsvwg-intserv-multiple-tspec-02
Next Steps • Sufficiently robust in direction to make WG item? draft-polk-tsvwg-intserv-multiple-tspec-02
