Re: [Dots] WGLC on draft-ietf-dots-server-discovery-05

<mohamed.boucadair@orange.com> Wed, 06 November 2019 15:51 UTC

Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: dots@ietfa.amsl.com
Delivered-To: dots@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D49D12008D; Wed, 6 Nov 2019 07:51:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nhToawVafObw; Wed, 6 Nov 2019 07:51:46 -0800 (PST)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.70.35]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 43812120072; Wed, 6 Nov 2019 07:51:46 -0800 (PST)
Received: from opfednr06.francetelecom.fr (unknown [xx.xx.xx.70]) by opfednr20.francetelecom.fr (ESMTP service) with ESMTP id 477WHN6K47z1xvP; Wed, 6 Nov 2019 16:51:44 +0100 (CET)
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.54]) by opfednr06.francetelecom.fr (ESMTP service) with ESMTP id 477WHN5SRjzDq75; Wed, 6 Nov 2019 16:51:44 +0100 (CET)
Received: from OPEXCAUBMA2.corporate.adroot.infra.ftgroup ([fe80::e878:bd0:c89e:5b42]) by OPEXCAUBM7D.corporate.adroot.infra.ftgroup ([fe80::bcfe:4850:e646:f223%21]) with mapi id 14.03.0468.000; Wed, 6 Nov 2019 16:51:44 +0100
From: <mohamed.boucadair@orange.com>
To: Jon Shallow <supjps-ietf@jpshallow.com>, 'Valery Smyslov' <valery@smyslov.net>, "dots@ietf.org" <dots@ietf.org>, "dots-chairs@ietf.org" <dots-chairs@ietf.org>
Thread-Topic: [Dots] WGLC on draft-ietf-dots-server-discovery-05
Thread-Index: AQG7u70viJ1zeDaA3CAo0XFND0KMCaex55BggAATZEA=
Date: Wed, 6 Nov 2019 15:51:44 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B933031350F27@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
References: <011d01d58974$b70298b0$2507ca10$@smyslov.net> <1bb901d594b2$b4502b20$1cf08160$@jpshallow.com>
In-Reply-To: <1bb901d594b2$b4502b20$1cf08160$@jpshallow.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.114.13.245]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/UfBCMjFcl11u8cFj4urj3-frD4Y>
Subject: Re: [Dots] WGLC on draft-ietf-dots-server-discovery-05
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "List for discussion of DDoS Open Threat Signaling \(DOTS\) technology and directions." <dots.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dots>, <mailto:dots-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dots/>
List-Post: <mailto:dots@ietf.org>
List-Help: <mailto:dots-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dots>, <mailto:dots-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Nov 2019 15:51:49 -0000

Hi Jon, 

Thank you for the comments. 

Please see inline. 

Cheers,
Med

> -----Message d'origine-----
> De : Dots [mailto:dots-bounces@ietf.org] De la part de Jon Shallow
> Envoyé : mercredi 6 novembre 2019 15:59
> À : 'Valery Smyslov'; dots@ietf.org; dots-chairs@ietf.org
> Objet : Re: [Dots] WGLC on draft-ietf-dots-server-discovery-05
> 
> Hi All,
> 
> I have read through draft-ietf-dots-server-discovery-05 and think that it
> is
> a good document.
> 
> However, in particular with DHCPv(4|6), it is only possible to use the
> first
> OPTION_Vx_DOTS_ADDRESS (5.1.3, 5.2.3).

[Med] Yes

  If the server at the first address
> is down / unavailable for whatever reason, it is not possible to define a
> backup IP address as a secondary entry.  Is it the intention to not allow
> backup IP addresses?

[Med] Hmm, that is possible given that an instance is designed to carry a list of IP addresses.

   If the DHCP client receives OPTION_V6_DOTS_ADDRESS only, the
   address(es) included in OPTION_V6_DOTS_ADDRESS are used to reach the
   ^^^^^^^^^^
   peer DOTS agent.  In addition, these addresses can be used as
   identifiers for authentication.

> 
> With DNS, I know that A/AAAA records can be presented round-robin which
> gives the possibility of backup IP addresses, but am not sure whether this
> holds true for implementations for other Resource Records.  If backup
> addresses are to be allowed, the draft is unclear whether only the first
> A/AAAA RR is allowed, or each can be tested until the first non-failure is
> found, or whether happy-eyeballs it to be invoked against all of the IP
> addresses and then the final IP preferentially chosen according to the RR
> returned order.

[Med] Considerations related to address selection (including HE) are not detailed here on purpose because this is not part of discovery. 

> 
> Regards
> 
> Jon
> 
> > -----Original Message-----
> > From: Dots [mailto:ietf-supjps-dots-bounces@ietf.org] On Behalf Of Valery
> > Smyslov
> > Sent: 23 October 2019 08:37
> > To: dots@ietf.org
> > Cc: dots-chairs@ietf.org
> > Subject: [Dots] WGLC on draft-ietf-dots-server-discovery-05
> >
> > Hi,
> >
> > this message starts a Work Group Last Call (WGLC) for
> draft-ietf-dots-server-
> > discovery-05.
> > The version to be reviewed is here:
> https://www.ietf.org/id/draft-ietf-dots-
> > server-discovery-05.txt
> >
> > The WGLC will last for two weeks and will end on November the 7th.
> > Please send your comments to the list before this date.
> >
> > Regards,
> > Frank & Valery.
> >
> >
> > _______________________________________________
> > Dots mailing list
> > Dots@ietf.org
> > https://www.ietf.org/mailman/listinfo/dots
> 
> _______________________________________________
> Dots mailing list
> Dots@ietf.org
> https://www.ietf.org/mailman/listinfo/dots