Questions:
1. Why do we need to have two(max) key items if "key-chain" is not implemented? I presume, control node implemented only authentication-key but not authentication-key-chains. Can I always assume that there is only one key present in auth data when it comes to programming MX?
2. XML Schema construct <sequence> is useless in this case since there is only only type of element present under the sequence.
Hi Nischal,
Few comments on AuthData schema type, currently it is defined as as:
<xsd:complexType name='Authentic ationData' >
< xsd:element name="key-type" type="Authentic ationKeyType" /> xsd:sequence>
<xsd:element name='key-items' type='Authentic ationKeyItem' maxOccurs='2'/>
< /xsd:sequence>
<
</xsd:complexType>
this can be seen as:
BgpRouterParam eters {
key- items[0. .1] {
int( range 0..63) key_id;
string key;
auth_data {
enum key-type (md5)
}
}
}
Questions: key-chains. Can I always assume that there is only one key present in auth data when it comes to programming MX?
1. Why do we need to have two(max) key items if "key-chain" is not implemented? I presume, control node implemented only authentication-key but not authentication-
2. XML Schema construct <sequence> is useless in this case since there is only only type of element present under the sequence.