Need clarification: for 'change_sig' attribute in 0160-Connections Response message

[naman1303]

In the Response Processing section of Connection Response step, below is mentioned:

When the invitee receives the response message, they will verify the change_sig provided.

But the attribute 'change_sig' is not mentioned anywhere else.
Is it a typo (where it actually meant 'sig_data' or 'connection~sig')?
Please correct it or add some detail to it otherwise.

[swcurran]

The specific reference is to this section of the 0160-Connections RFC.

@andrewwhitehead @tmarkovski - can either one of you take a read of that section, and perhaps the full Connection Response section? Is it accurate with what has been implemented and is working?

Thanks

[swcurran]

Per the Aries WG call on 20200108, @tmarkovski volunteered to review the RFC and respond to this question. Tomislav - I'm happy to do the RFC update if you want to summarize any needed changes.

[tmarkovski]

It should be sig_data. Submitted PR

[swcurran]

Thanks. Is that the only change, or does the rest of that section align with what you have implemented?

…

On Thu, Jan 9, 2020 at 6:43 AM Tomislav Markovski ***@***.***> wrote: It should be sig_data. Submitted PR — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#362?email_source=notifications&email_token=AAHYRQWS2Z676RSYDCBGKLLQ44ZZHA5CNFSM4J7KVZKKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEIQQ5QQ#issuecomment-572591810>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAHYRQSL2DPVHTUILDDNMILQ44ZZHANCNFSM4J7KVZKA> .

[tmarkovski]

Rest of the section looks good.

[swcurran]

Thanks @tmarkovski - closing this issue as resolved. The associated PR has been merged.