[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: I-D ACTION:draft-ietf-shim6-applicability-01.txt
A few personal comments:
2. Application scenarios
is intended to provide protection for the end-site in the event of a
failure in some subset of the available transit providers without
requiring the end-site to acquire provider-independent (PI) address
I suggest adding:
or requiring any particular cooperation between the transit providers.
since this seems to be a significant feature of shim6.
3.3. Address Generation
Stateful address auto-configuration using DHCP [RFC3315] is not
currently supported, because there is no defined mechanism to convey
the CGA Parameter Data Structure and other relevant information from
the DHCP server to the host. The definition of such mechanisms seems
to be quite straightforward in the case of the HBA, ...
Is there a plan to perform this work?
5.3. Shim6 and SCTP
recommended that Shim6 is not used for SCTP sessions, and that path
maintenance is provided solely by SCTP.
What is the mechanism, i.e. how does SCTP tell shim6 to do nothing?