[j-nsp] JUNOS not compliant with RFC 3392?

[Derick Winkworth]

I just re-read this and realized that it says the speaker "SHOULD" try again without the code.  It doesn't say "MUST."  So technically, its compliant.  If Juniper chooses not to follow the recommendation of trying again without the code, then why is the "disable-4byte-as" command hidden?




________________________________
From: Derick Winkworth <dwinkworth at att.net>
To: juniper-nsp at puck.nether.net
Sent: Monday, March 30, 2009 3:13:35 PM
Subject: JUNOS not compliant with RFC 3392?


All:

We are establishing a BGP session between an M120 and a Checkpoint firewall.  The Checkpoint does not support 4-byte ASs.  It is sending the Notification to the M120 indicating so, but the M120 keeps sending the capability code everytime it trys to reestablish.

Doesn't that make JUNOS non-compliant with RFC 3392?

############
A BGP speaker determines that its peer doesn't support capabilities
   advertisement, if in response to an OPEN message that carries the
   Capabilities Optional Parameter, the speaker receives a NOTIFICATION
   message with the Error Subcode set to Unsupported Optional Parameter.
   In this case the speaker SHOULD attempt to re-establish a BGP
   connection with the peer without sending to the peer the Capabilities
   Optional Parameter.
#############


In the meantime, we used the hidden command "disable-4byte-as." to establish connectivity.

Derick