>>>>> On Sat, 30 Jun 2001 23:18:34 +0700,
>>>>> Robert Elz <[EMAIL PROTECTED]> said:
> | Hmm, I see. So, "the API does not prohibit the bad behavior, but the
> | underlying kernel would (or might) prevent the bad packets from beiing
> | sent on the wire." Right? Then, I'm perhaps okay with it.
> It isn't so much that the API doesn't prohibit the bad behaviour, it
> can - but whether the API says something is legal or not, people are
> still going to do it.
> Sometimes it is important to specify exactly what does happen when the
> user does something stupid, other times it isn't.
> So, you could say "if the ancillary data contains multiple IPV6_HOPOPTS
> objects" (which was the particular case in question) "only the first is
> used", or "only the last is used", or "E2BIG is returned" or ...
> But there's no real need - allow any of those the implementation prefers
> and just say it is "implementation defined".
Okay, thanks for the explanation. Actually, I did not intend to
require the spec to clearly state that "the underlying kernel would
(or might) prevent the bad packets...", but just would like to make
the background intention clear. Thanks for the explanation.
JINMEI, Tatuya
Communication Platform Lab.
Corporate R&D Center, Toshiba Corp.
[EMAIL PROTECTED]
--------------------------------------------------------------------
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]
--------------------------------------------------------------------
