[Dots] WGLC signal draft: Conflict information conflicts

["Jon Shallow" <[e-mail]>]

Hi there,

 

Issue A.

 

It is undefined as to how to tell the DOTS client that 4.09 conflict for a
"cuid" has occurred as in

 

4.1.1 Request Mitigation

      DOTS servers MUST return 4.09 (Conflict) error code to a DOTS peer

      to notify that the 'cuid' is already in-use by another DOTS

      client.  Upon receipt of that error code, a new 'cuid' MUST be

      generated by the DOTS peer.

 

The DOTS client generates a new "cuid" for every 4.09 ???

 

I think we need a new conflict status

 

         4:  DOTS server has detected the presented 'cuid' is already in use
by another DOTS client.  A new 'cuid' needs to be generated.

 

And text updated

 

      DOTS servers MUST return 4.09 (Conflict) error code to a DOTS peer

      to notify that the 'cuid' is already in-use by another DOTS

      client, along with a conflict-status of 4.  Upon receipt of that error
code and conflict-status, a new 'cuid' MUST be

      generated by the DOTS peer.

 

 

 

Issue B.

 

We have confusion over the use of the word "different" for "different DOTS
client" - this was previously brought up but got lost on the way.  The
following is (correctly) for the same client

 

   For example, if the DOTS server receives a mitigation request which

   overlaps with an existing mitigation with a higher numeric 'mid', the

   DOTS server rejects the request by returning 4.09 (Conflict) to the

   DOTS client.  The response includes enough information for a DOTS

   client to recognize the source of the conflict as described below:

 

Yet we later have (which really should be corrected)

 

   If the request is conflicting with an existing mitigation request

   from a different DOTS client, the DOTS server may return 2.01

   (Created) or 4.09 (Conflict) to the requesting DOTS client.  If the

   DOTS server decides to maintain the new mitigation request, the DOTS

   server returns 2.01 (Created) to the requesting DOTS client.  If the

   DOTS server decides to reject the new mitigation request, the DOTS

   server returns 4.09 (Conflict) to the requesting DOTS client.  For

   both 2.01 (Created) and 4.09 (Conflict) responses, the response

   includes enough information for a DOTS client to recognize the source

   of the conflict as described below:

 

   conflict-information:  Indicates that a mitigation request is

      conflicting with another mitigation request(s) from other DOTS

      client(s).  This optional attribute has the following structure:

 

      conflict-status:  Indicates the status of a conflicting mitigation

         request.  The following values are defined:

 

         1:  DOTS server has detected conflicting mitigation requests

             from different DOTS clients.  This mitigation request is

             currently inactive until the conflicts are resolved.

             Another mitigation request is active.

 

         2:  DOTS server has detected conflicting mitigation requests

             from different DOTS clients.  This mitigation request is

             currently active.

 

         3:  DOTS server has detected conflicting mitigation requests

             from different DOTS clients.  All conflicting mitigation

             requests are inactive.

 

Issue C.

 

'mid' is missing from the second definition of conflict-scope as in

 

      conflict-scope:  Indicates the conflict scope.  It may include a

         list of IP addresses, a list of prefixes, a list of port

         numbers, a list of target protocols, a list of FQDNs, a list of

         URIs, a list of alias-names, or references to conflicting ACLs.

 

Regards

 

Jon