Jabber: xmpp:email@example.com?join (this is part of the MeetEcho interface)
Etherpad: https://codimd.ietf.org/notes-ietf-108-ace (This is where you are)
FP: Small comments from the IETF last call. Need to deal with some IANA issues still.
Issues have been put into the tracker on GitHub.
JS: Same situtation with the DTLS profile. It needs a new draft and then the AD can move all four documents to the IESG.
GS: Have not looked at the issues. Will ping Olaf for updates.
Question - CBOR shortcut value.
CS: Ask for guidence on what needs to be done for the document.
JS: This is here for possible adoption, but the WG is not not expected to have expertise in the CMP protocol, but just looking at how the CoAP work is done.
DM: Objections to doing this work?
No objections registered.
DM: Need to re-charter and then adopt.
JS: Recharter does not stop us from doing reviews.
GS: Reading table of contents - multicast and proxy support
MS: Don't use multicast for this. Only used for service discovery.
Need to have proxy support to get additional security for servers.
GS: This is just a transport draft?
DM: Is there a registry for the methods of AIF-REST?
CB: Yes - variants need to specify the permissions. For this used the CoAP method numbers
CB: Has it been adopted?
JS: Chairs need to get together to make final decision. Should be today or tomorrow.
BK: Who tracks the resources for dynamic permissions?
CB: It is the resource server, this is not generally communicated off the RS.
BK: Just asking about what else is similar due to the broader scope that this might be.
CB: When started, looked for other ways and not really found. Static resources on a server and somebody else telling the RS who has access seems to be a fairly new concept.
JS: On the use of different names for management and joining nodes: Don't know if there is an advantage, but that is what the pub-sub document in CoRE was doing so they may have ideas.
MT: Adoption call result?
DM: We'll let you know.
Adjourned - 5:43