[j-nsp] RIP MD5 Key ID

[Paul Goyette]

> OK, I do see the problem now, and I was unable to get RIP working
> between a Cisco IOS 12.2(25)S1 and JunOS 6.4R2. RFC2082 clearly defines
> the key identifier, which IOS does implement with the "key <number>"
> statement in the key chain definition. Even using a key ID 0 on IOS
> side to trick around JunOS probably setting the key identifier field
> to zero doesn't help to get communication between IOS and JunOS going.

Try setting the other side's Key ID to 1 - a quick code examination 
indicates that we set the key_id to 1 in all cases, at least as of JUNOS 
release 6.3.

> Whatever JunOS implements there... it's not RFC2082 compliant as far
> as I can see.

Well, it is mostly compliant!  :)  I've filed a bug report to allow
the user to configure the key_id field.