Huaimo –
I am still not convinced you have understood the problem. Let me make one more
attempt.
Node A is currently advertising 255 bytes of information about a link.
A configuration change is made on that node requiring it to also advertise
unidirectional link delay (sub-TLV 33). This link
Hi Les,
Thank you very much for your responses.
draft-chen-lsr-isis-big-tlv resolves the issue: unpredictable behavior with
partial deployment, which are stated in both IETF 117 and IETF 118 slides. I
explained this in detail in my previous email.
For the existing Sub-TLVs in a TLV > 255,
Huaimo -
Thanx for bringing this up. Resolving this before the meeting hopefully will
save us time during the meeting.
"Backwards compatibility" is possible in situations where new advertisements
are being introduced and the legacy nodes either:
* Don't need to process the new
Hi Les,
In last IETF, you presented/stated that Backwards compatibility is not
possible. This seems not true. The solution proposed in
draft-chen-lsr-isis-big-tlv is backwards compatible. Can you give your
definition of backwards compatibility?
In this IETF and last IETF, the slides states
On Sat, Nov 04, 2023 at 09:33:57PM -0400, Acee Lindem wrote:
> I thought that DHCPv6 Prefix Delegation (PD) could have multiple
> levels of delegation and that mechanism alone could be used for
> assignment within a domain? I must admit that it has been a very long
> time since the home net WG
