user61002: bitcoind v0.15.1 getrawmempool rpc in verbose mode returns size and vsize for a transaction:
vsize: size for fees post-segwit (ceil(weight/4))
size: disksize
But getrawmempool rcp also returns descendantsize and ancestorsize values.
Are these values segwit-aware? do they return the ancestor/descendant transaction disksize sum or ancestor/descendant vsize sum?

user61002: As easy as read an actual rpc call instead of bitcoin.org documentation:
"descendantsize" : n,   (numeric) virtual transaction size of in-mempool descendants (including this one)
"ancestorsize" : n,     (numeric) virtual transaction size of in-mempool ancestors (including this one)strong text

61002: <p>bitcoind v0.15.1 <code>getrawmempool</code> rpc in verbose mode returns <code>size</code> and <code>vsize</code> for a transaction:</p>

<p><code>vsize</code>: size for fees post-segwit (ceil(weight/4))</p>

<p><code>size</code>: disksize</p>

<p>But getrawmempool rcp also returns <code>descendantsize</code> and <code>ancestorsize</code> values.</p>

<p>Are these values segwit-aware? do they return the ancestor/descendant transaction disksize sum or ancestor/descendant vsize sum?</p>
 61002: <p>As easy as read an actual rpc call instead of bitcoin.org documentation:</p>

<p>"descendantsize" : n,   (numeric) <strong>virtual transaction size</strong> of in-mempool descendants (including this one)
"ancestorsize" : n,     (numeric) <strong>virtual transaction size</strong> of in-mempool ancestors (including this one)strong text</p>
