tech-invite   World Map     

3GPP     Specs     Glossaries     Architecture     IMS     UICC       IETF     RFCs     Groups     SIP     ABNFs       Search

RFC 4276

 
 
 

BGP-4 Implementation Report

Part 2 of 4, p. 7 to 29
Prev RFC Part       Next RFC Part

 


prevText      Top      Up      ToC       Page 7 
3.  BGP-4 Implementation Report

   For every item listed, the respondents indicated whether their
   implementation supports the Functionality/Description or not (Y/N)
   according to the [RFC2119] language indicated.  Any respondent
   comments are included.  If appropriate, the respondents indicated
   with "O" the fact that the support is neither Y/N (an alternate
   behavior, for example).  Refer to the appropriate sections in
   [RFC4271] for additional details.  Note that the last digit of the
   subsection number is the number of the survey question.

3.0.  Summary of Operation / Section 3 [RFC4271]

   3.0.1.  Base Behavior

       Functionality/Description: Is your implementation compatible
       with the base behavior described in this section?

       RFC2119: N/A

       Alcatel Y/N/O/Comments: Y
       Cisco   Y/N/O/Comments: Y
       Laurel  Y/N/O/Comments: Y
       NextHop Y/N/O/Comments: Y

Top      Up      ToC       Page 8 
   3.0.2.  Local Policy Changes

       Functionality/Description: To allow local policy changes to have
       the correct effect without resetting any BGP connections, a BGP
       speaker SHOULD either (a) retain the current version of the
       routes advertised to it by all of its peers for the duration of
       the connection, or (b) make use of the Route Refresh extension
       [RFC2918]

       RFC2119: SHOULD

       Alcatel Y/N/O/Comments: Y
       Cisco   Y/N/O/Comments: Y
       Laurel  Y/N/O/Comments: Y
       NextHop Y/N/O/Comments: Y


3.1.  Routes: Advertisement and Storage / Section 3.1 [RFC4271]

   3.1.3.  Withdraw Routes from Service

       Functionality/Description: Does your implementation support the
       three methods described in this section?

       RFC2119: N/A

       Alcatel Y/N/O/Comments: Y
       Cisco   Y/N/O/Comments: Y
       Laurel  Y/N/O/Comments: Y
       NextHop Y/N/O/Comments: Y


   3.1.4.  Path Attributes

       Functionality/Description: Added to or modified before
       advertising the route

       RFC2119: MAY

       Alcatel Y/N/O/Comments: Y
       Cisco   Y/N/O/Comments: Y
       Laurel  Y/N/O/Comments: Y
       NextHop Y/N/O/Comments: Y

Top      Up      ToC       Page 9 
3.2.  Routing Information Bases / Section 3.2 [RFC4271]

   3.2.5.  Routing Information Bases

       Functionality/Description: Is your implementation compatible
       with the RIB structure described in this section?

       RFC2119: N/A

       Alcatel Y/N/O/Comments: Y
       Cisco   Y/N/O/Comments: Y
       Laurel  Y/N/O/Comments: Y
       NextHop Y/N/O/Comments: Y


   3.2.6.  Next Hop Resolution

       Functionality/Description: The next hop for each route in the
       Loc-RIB MUST be resolvable via the local BGP speaker's Routing
       Table

       RFC2119: MUST

       Alcatel Y/N/O/Comments: Y
       Cisco   Y/N/O/Comments: Y
       Laurel  Y/N/O/Comments: Y
       NextHop Y/N/O/Comments: Y


3.3.  Message Formats / Section 4 [RFC4271]

   3.3.7.  Message Size

       Functionality/Description: Does your implementation support the
       message sizes described in this section?

       RFC2119: N/A

       Alcatel Y/N/O/Comments: Y
       Cisco   Y/N/O/Comments: Y
       Laurel  Y/N/O/Comments: Y
       NextHop Y/N/O/Comments: Y

Top      Up      ToC       Page 10 
3.4.  Message Header Format / Section 4.1 [RFC4271]


   3.4.8.  Marker

       Functionality/Description: MUST be set to all ones

       RFC2119: MUST

       Alcatel Y/N/O/Comments: Y
       Cisco   Y/N/O/Comments: Y
       Laurel  Y/N/O/Comments: Y
       NextHop Y/N/O/Comments: Y


   3.4.9.  Length

       Functionality/Description: MUST always be at least 19 and no
       greater than 4096

       RFC2119: MUST

       Alcatel Y/N/O/Comments: Y
       Cisco   Y/N/O/Comments: Y
       Laurel  Y/N/O/Comments: Y
       NextHop Y/N/O/Comments: Y


   3.4.10.  Length

       Functionality/Description: MAY be further constrained, depending
       on the message type

       RFC2119: MAY

       Alcatel Y/N/O/Comments: Y
       Cisco   Y/N/O/Comments: Y
       Laurel  Y/N/O/Comments: Y
       NextHop Y/N/O/Comments: Y

Top      Up      ToC       Page 11 
   3.4.11.  Message "Padding"

       Functionality/Description: No "padding" of extra data after the
       message is allowed, so the Length field MUST have the smallest
       value required given the rest of the message

       RFC2119: MUST

       Alcatel Y/N/O/Comments: Y
       Cisco   Y/N/O/Comments: Y
       Laurel  Y/N/O/Comments: Y
       NextHop Y/N/O/Comments: Y


3.5.  OPEN Message / Section 4.2 [RFC4271]

   3.5.12.  Hold Timer Calculation

       Functionality/Description: Use the smaller of its configured
       Hold Time and the Hold Time received in the OPEN message

       RFC2119: MUST

       Alcatel Y/N/O/Comments: Y
       Cisco   Y/N/O/Comments: Y
       Laurel  Y/N/O/Comments: Y
       NextHop Y/N/O/Comments: Y


   3.5.13.  Minimum Hold Time

       Functionality/Description: MUST be either zero or at least three
       seconds

       RFC2119: MUST

       Alcatel Y/N/O/Comments: Y
       Cisco   Y/N/O/Comments: Y
       Laurel  Y/N/O/Comments: Y
       NextHop Y/N/O/Comments: Y

Top      Up      ToC       Page 12 
   3.5.14.  Connection Rejection

       Functionality/Description: Based on the Hold Time

       RFC2119: MAY

       Alcatel Y/N/O/Comments: Y
       Cisco   Y/N/O/Comments: Y    Sends notification.
       Laurel  Y/N/O/Comments: Y
       NextHop Y/N/O/Comments: Y


3.6.  UPDATE Message Format / Section 4.3 [RFC4271]

   3.6.15.  UPDATE

       Functionality/Description: Simultaneously advertise a feasible
       route and withdraw multiple unfeasible routes from service

       RFC2119: MAY

       Alcatel Y/N/O/Comments: Y
       Cisco   Y/N/O/Comments: O    We have capability to process this
                                    functionality on receiving end but
                                    we don't send feasible & unfeasible
                                    simultaneously.
       Laurel  Y/N/O/Comments: Y
       NextHop Y/N/O/Comments: Y


   3.6.16.  Transitive Bit Setting

       Functionality/Description: For well-known attributes, the
       Transitive bit MUST be set to 1

       RFC2119: MUST

       Alcatel Y/N/O/Comments: Y
       Cisco   Y/N/O/Comments: Y
       Laurel  Y/N/O/Comments: Y
       NextHop Y/N/O/Comments: Y

Top      Up      ToC       Page 13 
   3.6.17.  Partial Bit Setting

       Functionality/Description: For well-known attributes and for
       optional non-transitive attributes the Partial bit MUST be set
       to 0

       RFC2119: MUST

       Alcatel Y/N/O/Comments: Y
       Cisco   Y/N/O/Comments: Y
       Laurel  Y/N/O/Comments: Y
       NextHop Y/N/O/Comments: Y


   3.6.18.  Attribute Flags Octet Sending

       Functionality/Description: Lower-order four bits set to zero

       RFC2119: MUST

       Alcatel Y/N/O/Comments: Y
       Cisco   Y/N/O/Comments: Y
       Laurel  Y/N/O/Comments: Y
       NextHop Y/N/O/Comments: Y


   3.6.19.  Attribute Flags Octet Receiving

       Functionality/Description: Lower-order four bits ignored

       RFC2119: MUST

       Alcatel Y/N/O/Comments: Y
       Cisco   Y/N/O/Comments: Y
       Laurel  Y/N/O/Comments: Y
       NextHop Y/N/O/Comments: Y

Top      Up      ToC       Page 14 
   3.6.20.  NEXT_HOP

       Functionality/Description: Used as the next hop to the
       destinations listed in the NLRI field of the UPDATE message

       RFC2119: SHOULD

       Alcatel Y/N/O/Comments: Y
       Cisco   Y/N/O/Comments: Y
       Laurel  Y/N/O/Comments: Y
       NextHop Y/N/O/Comments: Y


   3.6.21.  MULTI_EXIT_DISC

       Functionality/Description: Used by a BGP speaker's decision
       process to discriminate among multiple entry points to a
       neighboring autonomous system

       RFC2119: MAY

       Alcatel Y/N/O/Comments: Y
       Cisco   Y/N/O/Comments: Y
       Laurel  Y/N/O/Comments: Y
       NextHop Y/N/O/Comments: Y


   3.6.22.  AGGREGATOR IP Address

       Functionality/Description: Same address as the one used for the
       BGP Identifier of the speaker

       RFC2119: SHOULD

       Alcatel Y/N/O/Comments: Y    Default behavior.  Can be configured
                                    different from BGP ID.
       Cisco   Y/N/O/Comments: Y
       Laurel  Y/N/O/Comments: Y
       NextHop Y/N/O/Comments: Y

Top      Up      ToC       Page 15 
   3.6.23.  UPDATE messages that include the same address prefix in the
            WITHDRAWN ROUTES and Network Layer Reachability Information
            fields

       Functionality/Description: UPDATE messages SHOULD NOT include
       that information

       RFC2119: SHOULD NOT

       Alcatel Y/N/O/Comments: Y
       Cisco   Y/N/O/Comments: Y
       Laurel  Y/N/O/Comments: Y
       NextHop Y/N/O/Comments: Y


   3.6.24.  UPDATE messages that include the same address prefix in the
            WITHDRAWN ROUTES and Network Layer Reachability Information
            fields

       Functionality/Description: The BGP speaker MUST be able to handle
       them

       RFC2119: MUST

       Alcatel Y/N/O/Comments: Y
       Cisco   Y/N/O/Comments: Y
       Laurel  Y/N/O/Comments: Y
       NextHop Y/N/O/Comments: Y


   3.6.25.  UPDATE messages that include the same address prefix in the
            WITHDRAWN ROUTES and Network Layer Reachability Information
            fields

       Functionality/Description: Treated as if the WITHDRAWN ROUTES
       doesn't contain the address prefix

       RFC2119: SHOULD

       Alcatel Y/N/O/Comments: Y    Withdrawn routes are processed
                                    before NLRI fields.  Hence we get
                                    the desired behavior.
       Cisco   Y/N/O/Comments: Y
       Laurel  Y/N/O/Comments: Y
       NextHop Y/N/O/Comments: Y

Top      Up      ToC       Page 16 
3.7.  KEEPALIVE Message Format / Section 4.4 [RFC4271]

   3.7.26.  Maximum KEEPALIVE Frequency

       Functionality/Description: Not greater than one second

       RFC2119: MUST NOT

       Alcatel Y/N/O/Comments: Y
       Cisco   Y/N/O/Comments: Y
       Laurel  Y/N/O/Comments: Y
       NextHop Y/N/O/Comments: Y


   3.7.27.  KEEPALIVE Messages Rate

       Functionality/Description: Adjusted as a function of the Hold
       Time interval

       RFC2119: MAY

       Alcatel Y/N/O/Comments: Y
       Cisco   Y/N/O/Comments: Y
       Laurel  Y/N/O/Comments: Y
       NextHop Y/N/O/Comments: Y


   3.7.28.  Negotiated Hold Time of 0

       Functionality/Description: No KEEPALIVEs sent

       RFC2119: MUST NOT

       Alcatel Y/N/O/Comments: Y
       Cisco   Y/N/O/Comments: Y
       Laurel  Y/N/O/Comments: Y
       NextHop Y/N/O/Comments: Y

Top      Up      ToC       Page 17 
3.8.  NOTIFICATION Message Format / Section 4.5 [RFC4271]

   3.8.29.  NOTIFICATION Message

       Functionality/Description: Does your implementation support the
       NOTIFICATION Message as described in this section?

       RFC2119: N/A

       Alcatel Y/N/O/Comments: Y
       Cisco   Y/N/O/Comments: Y
       Laurel  Y/N/O/Comments: Y
       NextHop Y/N/O/Comments: Y


3.9.  Path Attributes /Section 5 [RFC4271]

   3.9.30.  Path Attributes

       Functionality/Description: Does your implementation support the
       path attributes as described in this section?

       RFC2119: N/A

       Alcatel Y/N/O/Comments: Y
       Cisco   Y/N/O/Comments: Y
       Laurel  Y/N/O/Comments: Y
       NextHop Y/N/O/Comments: Y


   3.9.31.  Well-Known Attributes

       Functionality/Description: Recognized by all BGP implementations

       RFC2119: MUST

       Alcatel Y/N/O/Comments: Y
       Cisco   Y/N/O/Comments: Y
       Laurel  Y/N/O/Comments: Y
       NextHop Y/N/O/Comments: Y

Top      Up      ToC       Page 18 
   3.9.32.  Mandatory Attributes

       Functionality/Description: Included in every UPDATE message that
       contains NLRI

       RFC2119: MUST

       Alcatel Y/N/O/Comments: Y
       Cisco   Y/N/O/Comments: Y
       Laurel  Y/N/O/Comments: Y
       NextHop Y/N/O/Comments: Y


   3.9.33/34.  Discretionary Attributes

       Functionality/Description: Sent in a particular UPDATE message

       RFC2119: MAY or MAY NOT

       Alcatel Y/N/O/Comments: Y
       Cisco   Y/N/O/Comments: Y
       Laurel  Y/N/O/Comments: Y
       NextHop Y/N/O/Comments: Y


   3.9.35.  Well-Known Attributes

       Functionality/Description: Passed along (after proper updating,
       if necessary) to other BGP peers

       RFC2119: MUST

       Alcatel Y/N/O/Comments: Y
       Cisco   Y/N/O/Comments: Y
       Laurel  Y/N/O/Comments: Y
       NextHop Y/N/O/Comments: Y

Top      Up      ToC       Page 19 
   3.9.36.  Optional Attributes

       Functionality/Description: In addition to well-known attributes,
       each path MAY contain one or more optional attributes

       RFC2119: MAY

       Alcatel Y/N/O/Comments: Y
       Cisco   Y/N/O/Comments: Y
       Laurel  Y/N/O/Comments: Y
       NextHop Y/N/O/Comments: Y


   3.9.37.  Unrecognized Transitive Optional Attributes

       Functionality/Description: Accepted

       RFC2119: SHOULD

       Alcatel Y/N/O/Comments: Y
       Cisco   Y/N/O/Comments: Y
       Laurel  Y/N/O/Comments: Y
       NextHop Y/N/O/Comments: Y


   3.9.38.  Partial Bit for Unrecognized Transitive Optional Attributes

       Functionality/Description: Set to 1 if the attribute is accepted
       and passed to other BGP speakers

       RFC2119: MUST

       Alcatel Y/N/O/Comments: Y
       Cisco   Y/N/O/Comments: Y
       Laurel  Y/N/O/Comments: Y
       NextHop Y/N/O/Comments: Y

Top      Up      ToC       Page 20 
   3.9.39.  Unrecognized Non-Transitive Optional Attributes

       Functionality/Description: Quietly ignored and not passed along
       to other BGP peers

       RFC2119: MUST

       Alcatel Y/N/O/Comments: Y
       Cisco   Y/N/O/Comments: Y
       Laurel  Y/N/O/Comments: Y
       NextHop Y/N/O/Comments: Y


   3.9.40.  New Transitive Optional Attributes

       Functionality/Description: Attached to the path by the
       originator or by any other BGP speaker in the path

       RFC2119: MAY

       Alcatel Y/N/O/Comments: Y
       Cisco   Y/N/O/Comments: Y
       Laurel  Y/N/O/Comments: Y
       NextHop Y/N/O/Comments: Y


   3.9.41.  Optional Attributes

       Functionality/Description: Updated by BGP speakers in the path

       RFC2119: MAY

       Alcatel Y/N/O/Comments: Y
       Cisco   Y/N/O/Comments: Y
       Laurel  Y/N/O/Comments: Y
       NextHop Y/N/O/Comments: Y

Top      Up      ToC       Page 21 
   3.9.42.  Path Attributes

       Functionality/Description: Ordered in ascending order of
       attribute type

       RFC2119: SHOULD

       Alcatel Y/N/O/Comments: Y
       Cisco   Y/N/O/Comments: O    All attributes are ordered in
                                    ascending order except Extended
                                    Community, which is type 16 but we
                                    send it out after community
                                    attribute.
       Laurel  Y/N/O/Comments: Y    except for MBGP which is always last
       NextHop Y/N/O/Comments: Y


   3.9.43.  Out of Order Received Path Attributes

       Functionality/Description: Receiver MUST be able to handle

       RFC2119: MUST

       Alcatel Y/N/O/Comments: Y
       Cisco   Y/N/O/Comments: Y
       Laurel  Y/N/O/Comments: Y
       NextHop Y/N/O/Comments: Y


   3.9.44.  Mandatory Attributes

       Functionality/Description: Present in all exchanges if NLRI are
       contained in the UPDATE message

       RFC2119: MUST

       Alcatel Y/N/O/Comments: Y
       Cisco   Y/N/O/Comments: Y
       Laurel  Y/N/O/Comments: Y
       NextHop Y/N/O/Comments: Y

Top      Up      ToC       Page 22 
3.10.  ORIGIN / Section 5.1.1 [RFC4271]

   3.10.45.  ORIGIN

       Functionality/Description: Value SHOULD NOT be changed by any
       speaker, except the originator

       RFC2119: SHOULD NOT

       Alcatel Y/N/O/Comments: Y
       Cisco   Y/N/O/Comments: Y
       Laurel  Y/N/O/Comments: Y
       NextHop Y/N/O/Comments: Y


3.11.  AS_PATH / Section 5.1.2 [RFC4271]

   3.11.46.  AS_PATH

       Functionality/Description: Not modified when advertising a route
       to an internal peer

       RFC2119: SHALL NOT

       Alcatel Y/N/O/Comments: Y
       Cisco   Y/N/O/Comments: Y
       Laurel  Y/N/O/Comments: Y
       NextHop Y/N/O/Comments: Y


   3.11.47.  Segment Overflow

       Functionality/Description: If the act of prepending will cause
       an overflow in the AS_PATH segment, i.e., more than 255 ASs, it
       SHOULD prepend a new segment of type AS_SEQUENCE and prepend its
       own AS number to this new segment

       RFC2119: SHOULD

       Alcatel Y/N/O/Comments: Y
       Cisco   Y/N/O/Comments: Y
       Laurel  Y/N/O/Comments: Y
       NextHop Y/N/O/Comments: Y

Top      Up      ToC       Page 23 
   3.11.48.  Prepending

       Functionality/Description: The local system MAY include/prepend
       more than one instance of its own AS number in the AS_PATH
       attribute

       RFC2119: MAY

       Alcatel Y/N/O/Comments: Y
       Cisco   Y/N/O/Comments: Y
       Laurel  Y/N/O/Comments: Y
       NextHop Y/N/O/Comments: Y


3.12.  NEXT_HOP / Section 5.1.3 [RFC4271]

   3.12.49.  NEXT_HOP

       Functionality/Description: Used as the next hop to the
       destinations listed in the UPDATE message

       RFC2119: SHOULD

       Alcatel Y/N/O/Comments: Y
       Cisco   Y/N/O/Comments: Y
       Laurel  Y/N/O/Comments: Y
       NextHop Y/N/O/Comments: Y


   3.12.50.  NEXT_HOP

       Functionality/Description: When sending a message to an internal
       peer, if the route is not locally originated, the BGP speaker
       SHOULD NOT modify the NEXT_HOP attribute, unless it has been
       explicitly configured to announce its own IP address as the
       NEXT_HOP

       RFC2119: SHOULD NOT

       Alcatel Y/N/O/Comments: Y
       Cisco   Y/N/O/Comments: Y
       Laurel  Y/N/O/Comments: Y
       NextHop Y/N/O/Comments: Y

Top      Up      ToC       Page 24 
   3.12.51.  NEXT_HOP

       Functionality/Description: When announcing a locally originated
       route to an internal peer, the BGP speaker SHOULD use as the
       NEXT_HOP the interface address of the router through which the
       announced network is reachable for the speaker

       RFC2119: SHOULD

       Alcatel Y/N/O/Comments: Y
       Cisco   Y/N/O/Comments: Y
       Laurel  Y/N/O/Comments: Y
       NextHop Y/N/O/Comments: Y


   3.12.52.  NEXT_HOP

       Functionality/Description: If the route is directly connected to
       the speaker, or the interface address of the router through
       which the announced network is reachable for the speaker is the
       internal peer's address, then the BGP speaker SHOULD use for the
       NEXT_HOP attribute its own IP address (the address of the
       interface that is used to reach the peer)

       RFC2119: SHOULD

       Alcatel Y/N/O/Comments: Y
       Cisco   Y/N/O/Comments: Y
       Laurel  Y/N/O/Comments: Y
       NextHop Y/N/O/Comments: Y


   3.12.53.  "First Party" NEXT_HOP

       Functionality/Description: If the external peer to which the
       route is being advertised shares a common subnet with one of the
       interfaces of the announcing BGP speaker, the speaker MAY use
       the IP address associated with such an interface in the NEXT_HOP
       attribute

       RFC2119: MAY

       Alcatel Y/N/O/Comments: Y
       Cisco   Y/N/O/Comments: Y
       Laurel  Y/N/O/Comments: Y
       NextHop Y/N/O/Comments: Y

Top      Up      ToC       Page 25 
   3.12.54.  Default NEXT_HOP

       Functionality/Description: IP address of the interface that the
       speaker uses to establish the BGP connection to peer X

       RFC2119: SHOULD

       Alcatel Y/N/O/Comments: Y
       Cisco   Y/N/O/Comments: Y
       Laurel  Y/N/O/Comments: Y
       NextHop Y/N/O/Comments: Y


   3.12.55.  NEXT_HOP Propagation

       Functionality/Description: The speaker MAY be configured to
       propagate the NEXT_HOP attribute.  In this case when advertising
       a route that the speaker learned from one of its peers, the
       NEXT_HOP attribute of the advertised route is exactly the same
       as the NEXT_HOP attribute of the learned route (the speaker just
       doesn't modify the NEXT_HOP attribute)

       RFC2119: MAY

       Alcatel Y/N/O/Comments: O
       Cisco   Y/N/O/Comments: Y
       Laurel  Y/N/O/Comments: Y
       NextHop Y/N/O/Comments: Y


   3.12.56.  Third Party NEXT_HOP

       Functionality/Description: MUST be able to support disabling it

       RFC2119: MUST

       Alcatel Y/N/O/Comments: Y
       Cisco   Y/N/O/Comments: Y
       Laurel  Y/N/O/Comments: Y
       NextHop Y/N/O/Comments: Y

Top      Up      ToC       Page 26 
   3.12.57.  NEXT_HOP

       Functionality/Description: A route originated by a BGP speaker
       SHALL NOT be advertised to a peer using an address of that peer
       as NEXT_HOP

       RFC2119: SHALL NOT

       Alcatel Y/N/O/Comments: Y
       Cisco   Y/N/O/Comments: Y
       Laurel  Y/N/O/Comments: Y
       NextHop Y/N/O/Comments: Y


   3.12.58.  NEXT_HOP

       Functionality/Description: A BGP speaker SHALL NOT install a
       route with itself as the next hop

       RFC2119: SHALL NOT

       Alcatel Y/N/O/Comments: Y
       Cisco   Y/N/O/Comments: Y
       Laurel  Y/N/O/Comments: Y
       NextHop Y/N/O/Comments: Y


   3.12.59.  NEXT_HOP

       Functionality/Description: Used to determine the actual outbound
       interface and immediate next-hop address that SHOULD be used to
       forward transit packets to the associated destinations

       RFC2119: SHOULD

       Alcatel Y/N/O/Comments: Y
       Cisco   Y/N/O/Comments: Y
       Laurel  Y/N/O/Comments: Y
       NextHop Y/N/O/Comments: Y

Top      Up      ToC       Page 27 
   3.12.60.  Resolved NEXT_HOP IP Address

       Functionality/Description: If the entry specifies an attached
       subnet, but does not specify a next-hop address, then the
       address in the NEXT_HOP attribute SHOULD be used as the
       immediate next-hop address

       RFC2119: SHOULD

       Alcatel Y/N/O/Comments: Y
       Cisco   Y/N/O/Comments: Y
       Laurel  Y/N/O/Comments: Y
       NextHop Y/N/O/Comments: Y


   3.12.61.  Resolved NEXT_HOP IP Address

       Functionality/Description: If the entry also specifies the
       next-hop address, this address SHOULD be used as the immediate
       next-hop address for packet forwarding

       RFC2119: SHOULD

       Alcatel Y/N/O/Comments: Y
       Cisco   Y/N/O/Comments: Y
       Laurel  Y/N/O/Comments: Y
       NextHop Y/N/O/Comments: Y


3.13.  MULTI_EXIT_DISC / Section 5.1.4 [RFC4271]

   3.13.62.  Preferred Metric

       Functionality/Description: Lowest value

       RFC2119: SHOULD

       Alcatel Y/N/O/Comments: Y
       Cisco   Y/N/O/Comments: Y
       Laurel  Y/N/O/Comments: Y
       NextHop Y/N/O/Comments: Y

Top      Up      ToC       Page 28 
   3.13.63.  MULTI_EXIT_DISC

       Functionality/Description: If received over EBGP, the
       MULTI_EXIT_DISC attribute MAY be propagated over IBGP to other
       BGP speakers within the same AS

       RFC2119: MAY

       Alcatel Y/N/O/Comments: Y
       Cisco   Y/N/O/Comments: Y
       Laurel  Y/N/O/Comments: Y
       NextHop Y/N/O/Comments: Y


   3.13.64.  MULTI_EXIT_DISC

       Functionality/Description: If received from a neighboring AS, it
       MUST NOT be propagated to other neighboring ASes

       RFC2119: MUST NOT

       Alcatel Y/N/O/Comments: Y
       Cisco   Y/N/O/Comments: Y
       Laurel  Y/N/O/Comments: Y
       NextHop Y/N/O/Comments: Y


   3.13.65.  Remove MULTI_EXIT_DISC

       Functionality/Description: Local configuration mechanism to
       remove the attribute from a route

       RFC2119: MUST

       Alcatel Y/N/O/Comments: Y
       Cisco   Y/N/O/Comments: Y
       Laurel  Y/N/O/Comments: Y
       NextHop Y/N/O/Comments: Y

Top      Up      ToC       Page 29 
   3.13.66.  Remove MULTI_EXIT_DISC

       Functionality/Description: Done prior to determining the degree
       of preference of the route and performing route selection

       RFC2119: MAY

       Alcatel Y/N/O/Comments: Y
       Cisco   Y/N/O/Comments: Y
       Laurel  Y/N/O/Comments: Y
       NextHop Y/N/O/Comments: Y


   3.13.67.  MULTI_EXIT_DISC Alteration

       Functionality/Description: An implementation MAY also (based on
       local configuration) alter the value of the MULTI_EXIT_DISC
       attribute received over EBGP

       RFC2119: MAY

       Alcatel Y/N/O/Comments: O
       Cisco   Y/N/O/Comments: Y
       Laurel  Y/N/O/Comments: Y
       NextHop Y/N/O/Comments: Y


   3.13.68.  MULTI_EXIT_DISC Alteration

       Functionality/Description: Done prior to determining the degree
       of preference of the route and performing route selection

       RFC2119: MAY

       Alcatel Y/N/O/Comments: Y
       Cisco   Y/N/O/Comments: Y
       Laurel  Y/N/O/Comments: Y
       NextHop Y/N/O/Comments: Y


Next RFC Part