Wireshark-bugs: [Wireshark-bugs] [Bug 5466] Improve dissection of bit-oriented fields, text fiel
Date: Thu, 9 Dec 2010 11:51:18 -0800 (PST)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5466

--- Comment #19 from Chris Maynard <[email protected]> 2010-12-09 11:51:18 PST ---
(In reply to comment #17)
> So, it turns out that in SAM3 the Link bit in the Control field was still
> defines, but it is Obsolete in SAM4 (which is the current standard).
> 
> I wonder if there is a way of figuring out which standard the target conforms
> to?
> 
> I guess if you can see the appropriate VPD page you could determine if it
> conforms to SPC2, SPC3 or SPC4 ...

Can you provide links to the relevant specifications you're using?  I don't
know much about SCSI so I want to be sure I'm looking at the same documents as
you are.  BTW, to possibly complicate things even further, I see mention of
SAM5 here: http://www.t10.org/new.htm.

In case there isn't any way to tell, I think it would be better to have the bit
described as the link bit rather than as obsolete.  If it's obsolete in later
versions, it can always be ignored, but it won't help older versions to have
the field marked as obsolete.  To help clarify which version(s) the field
applies to, the field description and/or blurb could indicate this.  The only
time you run into trouble is if the bit is re-used for another purpose and
needs to be described one way for one version, but a different way for another
version.

-- 
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.