Hi Monhamed,
On Tue 12 Jul 2016 15:07, <[email protected]> writes:
>> list binding-entry {
>> key "binding-ipv6info";
>> description "binding entry";
>> uses binding-entry;
>> }
>>
>> was that "binding-ipv6info" uniquely identifies the B4 (because it's a
>> key within the binding-entry list). Is that not the case?
>
> [Med] "binding-ipv6info" uniquely identifies an entry, ** not ** a
> B4. The B4 is identified by applying, for example, a subscriber-mask
> (https://tools.ietf.org/html/rfc7785#section-3). That is, a filter on
> all "binding-ipv6info" that belong, e.g., to the same /56.
I see, thank you. If I understand you correctly, you are saying that to
have multiple softwires that a B4 should terminate those softwires with
distinct IPv6 addresses. From the AFTR perspective this restriction is
not neccessary but if you find it useful, sure.
Andy
_______________________________________________
Softwires mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/softwires
