Re: [Dots] Data Channel - Deletion of Aliases when manually configured on DOTS Server

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

Hi Tiru,

 

I guess I missed / don’t currently recall that WG discussion (but can see the merit in having a standard set of aliases available to the DOTS clients which are just configured on the DOTS server).  I am trying to think of how the DOTS client configures directly without the data channel, but am failing to come up with how to do that without, say,  the operator doing it directly on the DOTS server.  “or other means” gets even more confusing.

 

I agree that directly/data channel methods are potentially mutually exclusive, but then the DOTS client/DOTS server need to negotiate which exclusive method to use…

 

It may just be simpler to drop a small amount of text.

 

Regards

 

Jon

 

From: Dots [mailto: [e-mail]] On Behalf Of Konda, Tirumaleswar Reddy
Sent: 05 September 2018 14:44
To: Jon Shallow; [e-mail]; Mortensen, Andrew
Subject: Re: [Dots] Data Channel - Deletion of Aliases when manually configured on DOTS Server

 

We meant DOTS client either uses data channel or direct configuration to create the aliases but not use both. It was discussed in the WG sometime back that DOTS client may or may not use DOTS data channel to create aliases and hence direct configuration got added but both modes are mutually exclusive. 

 

-Tiru

 

From: Jon Shallow <[e-mail]> 
Sent: Wednesday, September 5, 2018 6:49 PM
To: Konda, Tirumaleswar Reddy <[e-mail]>; [e-mail]; Mortensen, Andrew <[e-mail]>
Subject: RE: [Dots] Data Channel - Deletion of Aliases when manually configured on DOTS Server

 


CAUTION: External email. Do not click links or open attachments unless you recognize the sender and know the content is safe.

  _____  

Hi Tiru,

 

I meant the draft requirements document (and for some reason looking at an old draft (not the -15 version )) – I guess that this text needs to get updated then to remove the possibility of manual / direct configurations.

 

SIG-008

….

Old

      DOTS agents MUST support mitigation scope aliases, allowing DOTS

      client and server to refer to collections of protected resources

      by an opaque identifier created through the data channel, direct

      configuration, or other means.

 

SIG-008

….

New:

      DOTS agents MUST support mitigation scope aliases, allowing DOTS

      clients and servers to refer to collections of protected resources

      by an opaque identifier created through the data channel.

 

Regards

 

Jon

 

From: Dots [mailto: [e-mail]] On Behalf Of Konda, Tirumaleswar Reddy
Sent: 05 September 2018 14:01
To: Jon Shallow; [e-mail]
Subject: Re: [Dots] Data Channel - Deletion of Aliases when manually configured on DOTS Server

 

Hi Jon,

 

It looks like an oversight to me. If multiple modes of configuration is supported for aliases, it’s a troubleshooting nightmare, could lead to race condition and inconsistent configuration, and as you know one the goals of DOTS is to avoid manual configuration. 

 

-Tiru

 

From: Jon Shallow <[e-mail]> 
Sent: Wednesday, September 5, 2018 5:35 PM
To: Konda, Tirumaleswar Reddy <[e-mail]>; [e-mail]
Subject: RE: [Dots] Data Channel - Deletion of Aliases when manually configured on DOTS Server

 


CAUTION: External email. Do not click links or open attachments unless you recognize the sender and know the content is safe.

  _____  

Hi Tiru,

 

Unfortunately, manual / direct configuration is supported in the architecture draft, so cannot just be avoided.  

 

SIG-007

….

      DOTS agents MUST support mitigation scope aliases, allowing DOTS

      client and server to refer to collections of protected resources

      by an opaque identifier created through the data channel, direct

      configuration, or other means.

 

I agree with there being potential confusion when things are configured in multiple places, and troubleshooting  can get complicated.

 

I think we need a way of reflecting back to the DOTS client what is happening.

 

Regards

 

Jon

 

From: Dots [mailto: [e-mail]] On Behalf Of Konda, Tirumaleswar Reddy
Sent: 05 September 2018 11:38
To: Jon Shallow; [e-mail]
Subject: Re: [Dots] Data Channel - Deletion of Aliases when manually configured on DOTS Server

 

Manual configuration creates conflicts with the DOTS protocols (just like the conflicts network devices would face if configured using both SDN and manual configuration) and I guess should be avoided.

 

-Tiru

 

From: Dots <[e-mail]> On Behalf Of Jon Shallow
Sent: Wednesday, September 5, 2018 3:57 PM
To: [e-mail]
Subject: [Dots] Data Channel - Deletion of Aliases when manually configured on DOTS Server

 


CAUTION: External email. Do not click links or open attachments unless you recognize the sender and know the content is safe.

  _____  

Hi There,

 

When there is a manual configuration on the DOTS server of an alias by an operator, not created by the DOTS client, what should happen if the DOTS client tries to delete the alias?

 

The DOTS client will see the alias in a GET request for all aliases (as it is entitled to use it)

 

Returning a 404 (Not Found) could be confusing

 

Returning a 204 (No Content) is not right as it has not been deleted per se.

 

Should the alias in the GET response be marked as permanent (or some equivalent)?

 

The same is true for ACLs

 

Regards

 

Jon