Re: iSCSI Implementer's Guide - WG Last Call status
"Eddy Quicksall" <[email protected]>
| Newsgroups | gmane.ietf.ips |
|---|---|
| Message-ID | <[email protected]> |
I remember long ago talking about this when we were developing the RFC. I remember some people clearly saying that if the RFC said "must do X" then it meant that the peer "must check X". I didn't pursue the issue because it seemed to be of little importance. But as time went on and the draft got finalized, I ran into cases where that view was still taken to hart. Of course "the customer is always right" so I added checks. More recently I thought that since this guide was being written that maybe a simple statement could be made to clarify the issue. I'm not debating the issue of the importance of making a check or even the criteria for making the check. Eddy ----- Original Message ----- From: "Paul Koning" <[email protected]> To: <[email protected]> Cc: <[email protected]> Sent: Thursday, January 04, 2007 6:00 PM Subject: Re: [Ips] iSCSI Implementer's Guide - WG Last Call status >>>>>> "Mallikarjun" == Mallikarjun C <[email protected]> writes: > > Mallikarjun> Paul, Agree with everything you wrote. > > Mallikarjun> RFC 3720 does not require sane reactions to non-sane > Mallikarjun> inputs. This draft should not say anything that > Mallikarjun> suggests target/initiator may draw sane interpretations > Mallikarjun> to non-sane inputs either. > > Great summary. > > Mallikarjun> Sounds like an agreement to not add any new text to me. > > Well, Eddy raised the issue a while back that some people writing > conformance tests were interpreting "initiator must do X" as "target > must check that initiator does X". That's clearly an incorrect > conclusion. But given that people make this mistake, I wonder if a > note in the guide saying "unless RFC 3720 specifically requires it, an > implementation is not required to do protocol conformance checking on > incoming message", or something like that, would be helpful. > > paul > > > _______________________________________________ > Ips mailing list > [email protected] > https://www1.ietf.org/mailman/listinfo/ips > _______________________________________________ Ips mailing list [email protected] https://www1.ietf.org/mailman/listinfo/ips