> Please consider the following examples. Are these examples legal?
And what do you propose against these examples?
The specification should not prohibit anything just because it is not
considered useful, IMO. An unspecified source address looks harmless
because we don't use it except DAD.
In RFC2119, Key words for use in RFCs to Indicate Requirement Levels:
| $(Dk(B6. Guidance in the use of these Imperatives
|
| Imperatives of the type defined in this memo must be used with care
| and sparingly. In particular, they MUST only be used where it is
| actually required for interoperation or to limit behavior which has
| potential for causing harm (e.g., limiting retransmisssions) For
| example, they must not be used to try to impose a particular method
| on implementors where the method is not required for
| interoperability.
Atsushi Onoe
--------------------------------------------------------------------
IETF IPng Working Group Mailing List
IPng Home Page: http://playground.sun.com/ipng
FTP archive: ftp://playground.sun.com/pub/ipng
Direct all administrative requests to [EMAIL PROTECTED]
--------------------------------------------------------------------
- IPv6 packets with unspecified source address Jun-ichiro itojun Hagino
- Re: IPv6 packets with unspecified source add... Atsushi Onoe
- Re: IPv6 packets with unspecified source... itojun
- Re: IPv6 packets with unspecified so... Atsushi Onoe
- Re: IPv6 packets with unspecified source add... Steve Deering
- RE: IPv6 packets with unspecified source add... Richard Draves
- RE: IPv6 packets with unspecified source... Steve Deering
