>>> My question is... what about the other way around? What about >>> packets sent from the client to the server? >> See the SSH_MSG_CHANNEL_OPEN_CONFIRMATION packet [...] > Hmmm - the first time I looked at the structure of > SSH_MSG_CHANNEL_OPEN_CONFIRMATION, I thought those extra fields were > for confirmation purposes and didn't give it a second thought. Seems > like the RFC should maybe state their purpose in > SSH_MSG_CHANNEL_OPEN_CONFIRMATION a bit more explicitly - Agreed. When (if) 4254 is updated, that's a change I'd like to see; as it stands, it is entirely silent on the purpose of those fields, which strikes me as a bad idea for a formal spec. /~\ The ASCII Mouse \ / Ribbon Campaign X Against HTML mouse at rodents-montreal.org / \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.