Dear Murray,
Got it - I realise I wasn't clear with SHOULD - indeed the implementer
has limited discretion on what can happen: send the DISCONNECT, close
connection or drop the connection. I will discuss this with Ben but am
happy to add the additional text about dropping the connection.
Kind
Hi Cigdem,
On Thu, Mar 10, 2022 at 12:54 AM Cigdem Sengul
wrote:
> Thank you for your review. Our thinking was as Ben explained.
> In the draft, we used MUST/MUST NOT for the behaviour that affected
> security, and SHOULD for desired behaviour.
>
This doesn't match my understanding of how BCP
Hi Cigdem!
Thanks for the quick response. The clarifications and proposed edits listed
below address my feedback.
Roman
From: Cigdem Sengul
Sent: Thursday, March 10, 2022 7:33 AM
To: Roman Danyliw
Cc: The IESG ; draft-ietf-ace-mqtt-tls-prof...@ietf.org;
ace-cha...@ietf.org; Ace Wg ; Daniel
Hello Francesca,
Thank you. I welcome these suggestions - I do not foresee other permission
keywords looking at the MQTT vocabulary (control packets); happy to
"hard-code" "pub" and "sub".
If there aren't any other opinions, I will implement them this way.
There are a few other minor
Hi Cigdem,
Thank you for the quick reply!
The two additional registrations for the parameters Toid and Tperm look good,
although I have a couple of suggestions:
1. For Toid I would add a reference to Section 1.3 (and maybe capitalize
Topic Filter, just to be nitpicking). I would also
Dear Roman,
Thank you for your comments. I tried to respond to them inline below.
(I have made fixes here: https://github.com/ace-wg/mqtt-tls-profile/pull/104
)
On Tue, 8 Mar 2022 at 23:02, Roman Danyliw via Datatracker
wrote:
> Roman Danyliw has entered the following ballot position for
>
Francesca Palombini has entered the following ballot position for
draft-ietf-ace-aif-06: No Objection
When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)
Please refer to
Hello Francesca,
Thank you for your feedback. My response is below.
On Thu, 10 Mar 2022 at 10:03, Francesca Palombini via Datatracker <
nore...@ietf.org> wrote:
> Francesca Palombini has entered the following ballot position for
> draft-ietf-ace-mqtt-tls-profile-15: Discuss
>
> When responding,
Hi Carsten,
Please see inline ...
> -Original Message-
> From: iesg On Behalf Of Carsten Bormann
> Sent: 08 March 2022 21:12
> To: Rob Wilton (rwilton)
> Cc: logana...@gmail.com; ace-cha...@ietf.org; The IESG ;
> draft-ietf-ace-...@ietf.org; ace@ietf.org
> Subject: Re: Robert Wilton's
Francesca Palombini has entered the following ballot position for
draft-ietf-ace-mqtt-tls-profile-15: Discuss
When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)
Please
Hi Murray,
thank you for this review.
I’m currently collecting updates into https://github.com/cabo/ace-aif until the
ID submission opens again.
> On 2022-03-10, at 05:14, Murray Kucherawy via Datatracker
> wrote:
>
> Murray Kucherawy has entered the following ballot position for
>
Francesca Palombini has entered the following ballot position for
draft-ietf-ace-mqtt-tls-profile-15: No Objection
When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)
Hello Murray,
Thank you for your review. Our thinking was as Ben explained.
In the draft, we used MUST/MUST NOT for the behaviour that affected
security, and SHOULD for desired behaviour.
Would the following revision make it more clear:
"The Broker MUST NOT forward messages to unauthorized
13 matches
Mail list logo
