The latest version of the draft defines a modified form of the sub-TLV:
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Group ID | AMP Protocol |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
| IPv4 or IPv6 Host Address (4 or 16 octets) |
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Several questions:
1)Given the Router Capability TLV carries V4 Router ID/V6 Router ID - why is an
application specific address necessary - and how would it be chosen?
(I have asked this before but did not receive a substantive answer)
2)You are now requiring an address per "group ID". Why? And how would a group
specific address be chosen?
3)Section 4 states:
"Given that an IP endpoint may be used for multiple measurement groups
and AMP protocols, a router should only establish a single session of
a given protocol type between the same two pairs of IP endpoints
(independent of how many groups the endpoint participates in). "
This would argue that the encoding of the sub-TLV should be a list of Group
ID/AMP Protocol pairs so that unnecessary duplication is avoided.
4)There is no discussion of what a group ID is nor how consistency in
configuration between nodes is achieved.
Thanx.
Les
_______________________________________________
Lsr mailing list -- [email protected]
To unsubscribe send an email to [email protected]
