> On Feb 27, 2018, at 11:53, Benjamin Kaduk wrote:
>
> On Tue, Feb 27, 2018 at 11:25:29AM -0500, Russ Housley wrote:
>>
>>
>> Wouldn't it be sufficient to add a note a the bottom of the registry that
>> says:
>>
>> If an item is marked as not recommended it does not necessarily mean
>>
On Tue, Feb 27, 2018 at 11:25:29AM -0500, Russ Housley wrote:
>
>
> Wouldn't it be sufficient to add a note a the bottom of the registry that
> says:
>
>If an item is marked as not recommended it does not necessarily mean
>that it is flawed, rather, it indicates that either the item has
> On Feb 20, 2018, at 05:44, Dan Romascanu wrote:
>
> Reviewer: Dan Romascanu
> Review result: Has Issues
>
> I am the assigned OPS-DIR reviewer for this draft. The OPS DIrectorate reviews
> a great part of the IETF documents being processed by the IESG for the OPS
> ADs.
> Please treat with t
Hi Sean,
Thanks for the answer and for addressing my comments.
Short observations are inserted.
Regards,
Dan
On Tue, Feb 27, 2018 at 4:11 PM, Sean Turner wrote:
>
>
> > On Feb 20, 2018, at 05:44, Dan Romascanu wrote:
> >
> > Reviewer: Dan Romascanu
> > Review result: Has Issues
> >
> > I a
> On Feb 20, 2018, at 05:44, Dan Romascanu wrote:
>
> Reviewer: Dan Romascanu
> Review result: Has Issues
>
> I am the assigned OPS-DIR reviewer for this draft. The OPS DIrectorate reviews
> a great part of the IETF documents being processed by the IESG for the OPS
> ADs.
> Please treat with
Reviewer: Dan Romascanu
Review result: Has Issues
I am the assigned OPS-DIR reviewer for this draft. The OPS DIrectorate reviews
a great part of the IETF documents being processed by the IESG for the OPS ADs.
Please treat with these comments as with all other IETF LC comments. Please
wait for dire
