The MPLS WG Archive[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index][Thread Index][Author Index][Subject Index] LDP to Draft Standard - implementation survey
Bob, Attached is Data Connection's response to the LDP to Draft Standard - implementation survey. Regards John Salloway Network Protocols Group Data Connection Ltd Tel: +44 20 8366 1177 Fax: +44 20 8363 1468 EMail: mailto:js@dataconnection.com Web: http://www.dataconnection.com/ -----Original Message----- From: Loa Andersson [mailto:loa.andersson@utfors.se] Sent: 13 August 2002 16:18 To: MPLS wg Cc: George Swallow; Loa Andersson; Bob Thomas; Scott Bradner Subject: LDP to Draft Standard - implementation survey LDP to Draft Standard As protocols gets implemented and deployed, there is an IETF process to take them further on the standrads track. LDP is a protocol that has been both widely implemented and deployed, we will therefore start the process to progress LDP to Draft Standard. Included is an "LDP Implemenation Survey Form", it specifies in some detail the information needed to take this step. We ask companies and other organizations that have implemented LDP to take the time and answer the questions. The result of the survey will be made available as an Internet Draft, the time schedule depends very much on that we have the responses in a timely fashion. Send the response to the Bob Thomas, who will act as Internet Draft editor for the resulting summary document: rhthomas@cisco.com with a Cc to the wg chairs and the mpls list: loa.andersson@utfors.se swallow@cisco.com mpls@uu.net Earlier experiences with this kind of survey indicates that there are always a few that likes to respond anonymously, if you want to do that send the response to our AD, Scott Bradner: sob@harvard.edu We want to stress the importance of getting the highest possible number of responses, since it is important to create a protocol specification of highest possible quality. If there are further questions contact the wg chairs. Loa and George ===================================================================== LDP Implementation Survey Form [V 1.0] The purpose of this form is to gather information about implementations of LDP as defined by RFC3036. The information is being requested as part of the process of advancing LDP from Proposed to Draft Standard. The form is patterned after the implementation report form used for HTTP/1.1; see: http://www.ietf.org/IESG/Implementations/http1.1-implementations.txt ======================================================================= A. General information. Please provide the following information. ---------------------------------------------------------------- Organization: Data Connection Ltd Organization url(s): www.dataconnection.com ---------------------------------------------------------------- Product title(s): DC-MPLS Brief description(s): DC-MPLS is a full function MPLS software implementation which supports RSVP-TE, CR-LDP, and LDP. ---------------------------------------------------------------- Contact for LDP information Name: Ben Miller Title: VP sales and marketing E-mail: bmm@dataconnection.com Organization/department: Data Connection Ltd Postal address: 100 Church St, Enfield, Middlesex, EN2 6BQ, United Kingdom Phone: +44 20 8366 1177 Fax: +44 20 8363 1468 ======================================================================= B. LDP Implementation Status, Availability, Origin Please check [x] the boxes that apply. ---------------------------------------------------------------- Status: [ ] Development [ ] Alpha [ ] Beta [X] Product [ ] Other (describe): Availability [ ] Public and free [ ] Only to selected organizations/companies but free [X] On sale. [ ] For internal company use only [ ] Other: Implementation based on: (check all that apply) [ ] Purchased code (please list source if possible) [ ] Free code (please list source if possible) [X] Internal implementation (no outside code, just from specs) [ ] Internal implementation on top of purchased or free code List portions from external source: List portions developed internally: ======================================================================= C. LDP Feature Survey. For each features listed, please indicate the Status of the implementation using one of the following: 't' tested against another independent implementation 'y' implemented but not tested against independent implementation 'n' not implemented '-' not applicable to this type of implementation Optional: For 'n' status, indicate reason not implemented using one of the following: 's' RFC specification inadequate, unclear, or confusing 'u' utility of feature unclear 'r' feature not required for feature set implemented ------------------+-----------------------------+------------------------- | | Status (one of t, y, n - | | If n, optionally one of Feature | RFC3036 Section(s) | s, u, r) ==================+=============================+========================= Interface types | 2.2.1, 2.5.3, 2.8.2, 3,4,2 ----------------+-----------------------------+------------------------- Packet | | t ----------------+-----------------------------+------------------------- Frame Relay | | y ----------------+-----------------------------+------------------------- ATM | | t ==================+=============================+========================= Label Spaces | 2.2.1, 2.2.2 ----------------+-----------------------------+------------------------- Per platform | | t ----------------+-----------------------------+------------------------- Per interface | | t ==================+=============================+========================= LDP Discovery | 2.4 ----------------+-----------------------------+------------------------- Basic | 2.4.1 | t ----------------+-----------------------------+------------------------- Targeted | 2.4.2 | t ------------------+-----------------------------+------------------------- LDP Sessions | 2.2.3 ----------------+-----------------------------+------------------------- Directly | -- | t Connected | | ----------------+-----------------------------+------------------------- Targeted | 2.3 | t ==================+=============================+========================= LDP Modes | 2.6 ----------------+-----------------------------+------------------------- DU, Ind cntl, | 2.6 | Lib retention | | t ----------------+-----------------------------+------------------------- DU, Ord cntl, | 2.6 | Lib retention | | t ----------------+-----------------------------+------------------------- DU, Ind cntl, | 2.6 | Cons retention | | t ----------------+-----------------------------+------------------------- DU, Ord cntl, | 2.6 | Cons retention | | t ----------------+-----------------------------+------------------------- DoD, Ind cntl, | 2.6 | Lib retention | | y ----------------+-----------------------------+------------------------- DoD, Ord cntl, | 2.6 | Lib retention | | y ----------------+-----------------------------+------------------------- DoD, Ind cntl, | 2.6 | Cons retention | | t ----------------+-----------------------------+------------------------- DoD, Ord cntl, | 2.6 | Cons retention | | t ==================+=============================+========================= Loop Detection | 2.8 | t ==================+=============================+========================= TCP MD5 Option | 2.9 | n r ==================+=============================+========================= LDP TLVs | 3.3, 3.4, throughout ----------------+-----------------------------+------------------------- U-bit | 3.3 | t ----------------+-----------------------------+------------------------- F-bit | 3.3 | t ------------------+-----------------------------+------------------------- FEC | 1., 2.1, 3.4.1 | t ----------------+-----------------------------+------------------------- Wildcard | 3.4.1 | y ----------------+-----------------------------+------------------------- Prefix | 2.1, 3.4.1 | t ----------------+-----------------------------+------------------------- Host | 2.1, 3.4.1 | t ------------------+-----------------------------+------------------------- Address List | 3.4.3 | t ------------------+-----------------------------+------------------------- Hop Count | 3.4.4 | t ------------------+-----------------------------+------------------------- Path Vector | 3.4.5 | t ------------------+-----------------------------+------------------------- Generic Label | 3.4.2.1 | t ------------------+-----------------------------+------------------------- ATM Label | 3.4.2.2 | t ------------------+-----------------------------+------------------------- Frame Relay | 3.4.2.3 | y Label | | ------------------+-----------------------------+------------------------- Status | 3.4.6 | t ------------------+-----------------------------+------------------------- Extended Status | 3.5.1 | t ------------------+-----------------------------+------------------------- Returned PDU | 3.5.1 | t ------------------+-----------------------------+------------------------- Returned Message| 3.5.1 | t ------------------+-----------------------------+------------------------- Common Hello | 3.5.2 | t Parameters | | ----------------+-----------------------------+------------------------- T-bit | 3.5.2 | t ----------------+-----------------------------+------------------------- R-bit | 3.5.2 | t ----------------+-----------------------------+------------------------- Hold Time | 3.5.2 | t ------------------+-----------------------------+------------------------- IPv4 Transport | 3.5.2 | t Address | | ------------------+-----------------------------+------------------------- Configuration | 3.5.2 | t Sequence Number | | ------------------+-----------------------------+------------------------- IPv6 Transport | 3.5.2 | n r Address | | ------------------+-----------------------------+------------------------- Common Session | 3.5.3 | t Parameters | | ----------------+-----------------------------+------------------------- KeepAlive Time| 3.5.3 | t ----------------+-----------------------------+------------------------- PVLim | 3.5.3 | t ----------------+-----------------------------+------------------------- Max PDU Length| 3.5.3 | t ------------------+-----------------------------+------------------------- ATM Session | 3.5.3 | t Parameters | | ----------------+-----------------------------+------------------------- M values | | t 0 No Merge | 3.5.3 | ------------+-----------------------------+------------------------- 1 VP Merge | 3.5.3 | t ------------+-----------------------------+------------------------- 2 VC Merge | 3.5.3 | t ------------+-----------------------------+------------------------- 3 VP & | 3.5.3 | t VC Merge | | ----------------+-----------------------------+------------------------- D-bit | 3.5.3 | t ----------------+-----------------------------+------------------------- ATM Label | 3.5.3 | t Range | | Component | | ------------------+-----------------------------+------------------------- Frame Relay | 3.5.3 | y Session | | Parameters | | ------------------+-----------------------------+------------------------- M values | | y 0 No Merge | 3.5.3 | ------------+-----------------------------+------------------------- 1 Merge | 3.5.3 | y ----------------+-----------------------------+------------------------- D-bit | 3.5.3 | y ----------------+-----------------------------+------------------------- Frame Relay | 3.5.3 | y Label Range | | Component | | ----------------+-----------------------------+------------------------- Label Request | 3.5.7 | t Message ID | | ------------------+-----------------------------+------------------------- Vendor-Private | 3.6.1.1 | y ------------------+-----------------------------+------------------------- Experimental | 3.6.2 | y ==================+=============================+========================= LDP Messages | 3.5, throughout ------------------+-----------------------------+------------------------- Notification | 3.5.1 | t ------------------+-----------------------------+------------------------- Hello | 3.5.2 | t ------------------+-----------------------------+------------------------- Initialization | 3.5.3 | t ------------------+-----------------------------+------------------------- KeepAlive | 3.5.4 | t ------------------+-----------------------------+------------------------- Address | 3.5.5 | t ------------------+-----------------------------+------------------------- Address Withdraw| 3.5.6 | t ------------------+-----------------------------+------------------------- Label Mapping | 3.5.7 | t ----------------+-----------------------------+------------------------- Label Request | 3.5.7 | t Message ID TLV| | ----------------+-----------------------------+------------------------- Hop Count TLV | 3.5.7 | t ----------------+-----------------------------+------------------------- Path Vect TLV | 3.5.7 | t ------------------+-----------------------------+------------------------- Label Request | 3.5.8 | t ----------------+-----------------------------+------------------------- Hop Count TLV | 3.5.8 | t ----------------+-----------------------------+------------------------- Path Vect TLV | 3.5.8 | t ------------------+-----------------------------+------------------------- Label Withdraw | 3.5.10 | t ----------------+-----------------------------+------------------------- Label TLV | 3.5.10 | t ------------------+-----------------------------+------------------------- Label Release | 3.5.11 | t ----------------+-----------------------------+------------------------- Label TLV | 3.5.11 | t ------------------+-----------------------------+------------------------- Label Abort Req | 3.5.9 | y ------------------+-----------------------------+------------------------- Vendor-Private | 3.6.1.2 | y ------------------+-----------------------------+------------------------- Experimental | 3.6.2 | y ==================+=============================+========================= LDP Status Codes | 3.4.6 ------------------+-----------------------------+------------------------- Success | 3.4.6, 3.9 | y ------------------+-----------------------------+------------------------- Bad LDP Id | 3.5.1.2.1 | y ------------------+-----------------------------+------------------------- Bad Ptcl Version| 3.5.1.2.1 | y ------------------+-----------------------------+------------------------- Bad PDU Length | 3.5.1.2.1 | y ------------------+-----------------------------+------------------------- Unknown Message | 3.5.1.2.1 | y Type | | ------------------+-----------------------------+------------------------- Bad Message | 3.5.1.2.1 | y Length | | ------------------+-----------------------------+------------------------- Unknown TLV | 3.5.1.2.2 | y ------------------+-----------------------------+------------------------- Bad TLV length | 3.5.1.2.2 | y ------------------+-----------------------------+------------------------- Malformed TLV | 3.5.1.2.2 | y Value | | ------------------+-----------------------------+------------------------- Hold Timer | 3.5.1.2.3 | t Expired | | ------------------+-----------------------------+------------------------- Shutdown | 3.5.1.2.4 | t ------------------+-----------------------------+------------------------- Loop Detected | 3.4.5.1.2, 3.5.8.1 | t ------------------+-----------------------------+------------------------- Unknown FEC | 3.4.1.1 | y ------------------+-----------------------------+------------------------- No Route | 3.5.8.1 | t ------------------+-----------------------------+------------------------- No Label | 3.5.8.1 | y Resources | | ------------------+-----------------------------+------------------------- Label Resources | 3.5.8.1 | y Available | | ------------------+-----------------------------+------------------------- Session Rejected| 2.5.3, 3.5.3 | y No Hello | | ------------------+-----------------------------+------------------------- Session Rejected| 2.5.3, 3.5.3 | y Parameters | | Advert Mode | | ------------------+-----------------------------+------------------------- Session Rejected| 2.5.3, 3.5.3 | t Parameters | | Max PDU Length | | ------------------+-----------------------------+------------------------- Session Rejected| 2.5.3, 3.5.3 | t Parameters | | Label Range | | ------------------+-----------------------------+------------------------- KeepAlive Timer | 2.5.6, 3.5.1.2.3 | t Expired | | ------------------+-----------------------------+------------------------- Label Request | 3.5.9.1 | t Aborted | | ------------------+-----------------------------+------------------------- Missing Message | 3.5.1.2.1 | y Parameters | | ------------------+-----------------------------+------------------------- Unsupported | 3.4.1.1, 3.5.5.1 | y Address Family | | ------------------+-----------------------------+------------------------- Session Rejected| 3.5.1.2.5, 3.5.3 | y Bad KeepAlive | | Time | | ------------------+-----------------------------+------------------------- Internal Error | 3.5.1.2.7 | y ==================+=============================+========================= -- Loa Andersson Chief Architect, Utfors Research, Architecture and Future Lab (URAX) Utfors AB Råsundavägen 12 Box 525, 169 29 Solna Office +46 8 5270 2000 Office direct +46 8 5270 5038 Mobile +46 70 848 5038 Email loa.andersson@utfors.se WWW www.utfors.se |
|