To: dime@ietf.org
References: <154810458138.8188.8411786024206076306@ietfa.amsl.com>
From: Steve Donovan <srdonovan@usdonovans.com>
Message-ID: <71b3d38a-ac90-8ac7-0aa3-8a6c83d37534@usdonovans.com>
Date: Thu, 24 Jan 2019 17:42:03 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:45.0)
 Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <154810458138.8188.8411786024206076306@ietfa.amsl.com>
Content-Type: multipart/alternative;
 boundary="------------0EB645FECEC4AC41C06D9EEC"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dime/I2_hQndIqd2K7fzgXATxBAoi-RQ>
Subject: Re: [Dime] Opsdir last call review of
 draft-ietf-dime-doic-rate-control-10
Precedence: list

This is a multi-part message in MIME format.
--------------0EB645FECEC4AC41C06D9EEC
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit

Susan,

Thank you for your review and comments.

Please see my responses inline.

Regards,

Steve

On 1/21/19 3:03 PM, Susan Hares wrote:
> Reviewer: Susan Hares
> Review result: Ready
>
> Steve and Eric:
>
> I have reveiwed this document as part of the  operational directorate (ops-dir)
> ongoing effort to review all IETF documents being process by the IESG for
> operational aspects.  These comments are to aid the authors and the NM/OPS Area
> Directors.  The document editors and the WG chairs hsould treat these comments
> as any other last call comments.
>
> Status: ready,  with  2 operator questions and 1 yang question.  The question
> are just things to think about for the authors and ADS.
>
> Questions:
>
> The documentis readable and aligns with RFC7683 and
> draft-ietf-dime-agent-overload.     The language in this document also aligns
> with language in the SIP Overload Control (SOC) document [RFC7415].
>
> As I am not familar with current DIAMETER deployments, i've got a few
> operational questions for the authors to consider:
>
> 1)  If a operator where deploying this new algorithm,
>    what type of deployment considerations would
>     be necessary?   Should certain topologies
>     of Diameter deployments utilize certain
>    overload algorithms?
>
>  2) What failure modes will the operator see
>    in the current overload abatement that
>    would encourage the operator to
>    spend the effort to go to this new DOIC
>    rate limit?
>
> As a researcher and implementer, sections 1 and  7 were sufficient
> to answer these questions.   However,  I would ask the authors,
> WG chairs, and OPS/NM ADs to determine if these are sufficient
> for the normal operators.
SRD> We had multiple operators involved in the development of this
draft, in fact, one of the authors works for an operator.  As such, I'm
confident that their concerns have been addressed.
>
> Question 3:  Just for my own understanding,
> is there a plan to control DIAMETER protocols with YANG
> modules?
SRD> Not to my knowledge.
>
>
> _______________________________________________
> DiME mailing list
> DiME@ietf.org
> https://www.ietf.org/mailman/listinfo/dime


--------------0EB645FECEC4AC41C06D9EEC
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <font face="Times New Roman, Times, serif">Susan,<br>
      <br>
      Thank you for your review and comments.<br>
      <br>
      Please see my responses inline.<br>
      <br>
      Regards,<br>
      <br>
      Steve<br>
    </font><br>
    <div class="moz-cite-prefix">On 1/21/19 3:03 PM, Susan Hares wrote:<br>
    </div>
    <blockquote
      cite="mid:154810458138.8188.8411786024206076306@ietfa.amsl.com"
      type="cite">
      <pre wrap="">Reviewer: Susan Hares
Review result: Ready

Steve and Eric:

I have reveiwed this document as part of the  operational directorate (ops-dir)
ongoing effort to review all IETF documents being process by the IESG for
operational aspects.  These comments are to aid the authors and the NM/OPS Area
Directors.  The document editors and the WG chairs hsould treat these comments
as any other last call comments.

Status: ready,  with  2 operator questions and 1 yang question.  The question
are just things to think about for the authors and ADS.

Questions:

The documentis readable and aligns with RFC7683 and
draft-ietf-dime-agent-overload.     The language in this document also aligns
with language in the SIP Overload Control (SOC) document [RFC7415].

As I am not familar with current DIAMETER deployments, i've got a few
operational questions for the authors to consider:

1)  If a operator where deploying this new algorithm,
   what type of deployment considerations would
    be necessary?   Should certain topologies
    of Diameter deployments utilize certain
   overload algorithms?

 2) What failure modes will the operator see
   in the current overload abatement that
   would encourage the operator to
   spend the effort to go to this new DOIC
   rate limit?

As a researcher and implementer, sections 1 and  7 were sufficient
to answer these questions.   However,  I would ask the authors,
WG chairs, and OPS/NM ADs to determine if these are sufficient
for the normal operators.</pre>
    </blockquote>
    SRD&gt; We had multiple operators involved in the development of
    this draft, in fact, one of the authors works for an operator.  As
    such, I'm confident that their concerns have been addressed.<br>
    <blockquote
      cite="mid:154810458138.8188.8411786024206076306@ietfa.amsl.com"
      type="cite">
      <pre wrap="">

Question 3:  Just for my own understanding,
is there a plan to control DIAMETER protocols with YANG
modules?</pre>
    </blockquote>
    SRD&gt; Not to my knowledge.<br>
    <blockquote
      cite="mid:154810458138.8188.8411786024206076306@ietfa.amsl.com"
      type="cite">
      <pre wrap="">


_______________________________________________
DiME mailing list
<a class="moz-txt-link-abbreviated" href="mailto:DiME@ietf.org">DiME@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/dime">https://www.ietf.org/mailman/listinfo/dime</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------0EB645FECEC4AC41C06D9EEC--