Re: 2842 to Draft Standard

[Yakov Rekhter <[e-mail]>]

Bill

> IDR WG,
> 
>   In order to progress to Draft Standard, an implementation report
> is required (see section 4.1.2 of RFC 2026).  In particular:
> 
>    The requirement for at least two independent and interoperable
>    implementations applies to all of the options and features of the
>    specification.
> 
> RFC 2842 has several optional portions (e.g. sending Notifications
> and whether to include the capability in question in the Notification),
> which the implementation report that you included in the original
> request did not mention.
>
>   I'd like to see a more complete implementation report.  For
> example, if vendors don't mind being named:
> http://www.ietf.org/IESG/Implementations/IPCOMP-Implementation.txt
> or if they don't want to be named:
> http://www.ietf.org/IESG/Implementations/AGENTX-IMPLEMENTATION

See below.
  
>   Also, the process would go much more smoothly if there was an
> Internet-Draft containing the revision, even though it's so small.
> The RFC-Editor can supply the nroff of RFC 2842 if the authors 
> don't still have their source.

Done (see draft-ietf-idr-rfc2842bis-00.txt)

Yakov.
----------------------------------------------------------------------
The following is the list of some of the implementations of rfc2842:

Ericsson:
Interoperates with: Cisco, Juniper

Juniper Networks
Interoperates with: Cisco

Laurel Networks:
Interoperates with: Cisco, Juniper

NetPlane Systems Inc.
Interoperates with: Cisco, Juniper

Redback
Interoperates with: Cisco, Juniper

Riverstone:
Interoperates with: Cisco, Juniper, Zebra, Foundry

Unisphere Networks:
Interoperates with: Cisco, Juniper 

If a BGP speaker that supports a certain capability determines that
its peer doesn't support this capability, 2 implementations never
send a NOTIFICATION message to the peer, and 4 implementations
sometimes send a NOTIFICATION message to the peer.

Out of the 4 implementations that send the NOTIFICATION message
(when the peer doesn't support a particular capability), 2
implementations never include the Capability in question in the
message, and 2 implementations always include the Capability in
question in the message.