On Wed, 30 May 2007, JINMEI Tatuya / ¿ÀÌÀãºÈ wrote:
- section 3.1
IPv6 implementations are no longer required to implement RH0 in any
way.
I don't understand why we bother to say this. Isn't it enough to
state "IPv6 nodes MUST NOT originate IPv6 packets containing RH0."?
Only commenting on this as I feel rather strongly on this..
I don't think the wording you propose is good. That begs the
question, is a compliant IPv6 node required to prevent origination of
RH0? I.e., if a user, through a raw socket for example, were to send
RH0, would the node be required to drop it? What about if the IPv6
API is used to try to originate such a RH0 packet?
I don't think this is what you're suggesting, and a "MUST NOT
originate" seems to be on the borderline of the past Robert Elz's
RFC3513 appeal of unclarity in the spec.
However, I agree that the current wording could probably be better.
--
Pekka Savola "You each name yourselves king, yet the
Netcore Oy kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings
--------------------------------------------------------------------
IETF IPv6 working group mailing list
[email protected]
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------
