Re: [Dots] Éric Vyncke's Discuss on draft-ietf-dots-server-discovery-14: (with DISCUSS and COMMENT)

mohamed.boucadair@orange.com Wed, 04 November 2020 15:43 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 D126C3A12E7; Wed, 4 Nov 2020 07:43:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=orange.com
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 9BX6WG0lYehb; Wed, 4 Nov 2020 07:43:48 -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 0E7BD3A12EF; Wed, 4 Nov 2020 07:43:47 -0800 (PST)
Received: from opfednr07.francetelecom.fr (unknown [xx.xx.xx.71]) by opfednr24.francetelecom.fr (ESMTP service) with ESMTP id 4CR9t96D1pz1y2T; Wed, 4 Nov 2020 16:43:45 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orange.com; s=ORANGE001; t=1604504625; bh=biGJ5woOTaPfahXCModZFZj9MeTkkHnPHNPlIZcI/Z8=; h=From:To:Subject:Date:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=BURPv/9zaofL6TEg8euXCAT5cWSBeiMEs2y06Vgm1Crd0aCmNuadY/R9ol0AwWbk0 DQ9Hc8ee80XC/MVy2AW0X6ybzr6IzmFY+czHl09V2CSTjrQj3fnrZFDdHsunihjiI6 Q2I5l6kf9t6KiRNNghHbsF3ttLvu0FPR/sIlKY88OUKzq8kzq8zcOGRLDPaeNKQv1s PohV1OReSso8hOwcyamHyMoalhv9Q2FmGj/CFK5XA0t70Kpon8jxW2NsBxHQE1W1XD 9VE8NzeELATAUkJ+f09Oy9uZZyCYJnX6N182sugOyBrm33pAQh5alxxYdESTbFUYzA bQSFaSlSX36RQ==
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.60]) by opfednr07.francetelecom.fr (ESMTP service) with ESMTP id 4CR9t96p7lzFpXX; Wed, 4 Nov 2020 16:43:45 +0100 (CET)
From: mohamed.boucadair@orange.com
To: "Eric Vyncke (evyncke)" <evyncke@cisco.com>, The IESG <iesg@ietf.org>
CC: Valery Smyslov <valery@smyslov.net>, "Bernie Volz (volz)" <volz@cisco.com>, "zhencao.ietf@gmail.com" <zhencao.ietf@gmail.com>, "dots@ietf.org" <dots@ietf.org>, "tim@qacafe.com" <tim@qacafe.com>, "dots-chairs@ietf.org" <dots-chairs@ietf.org>, "draft-ietf-dots-server-discovery@ietf.org" <draft-ietf-dots-server-discovery@ietf.org>
Thread-Topic: Éric Vyncke's Discuss on draft-ietf-dots-server-discovery-14: (with DISCUSS and COMMENT)
Thread-Index: AQHWshMdIy60/aZzWU6NT11nUIRB7qm3erxAgABiKoD///TcgIAAVFEA///3rkA=
Date: Wed, 04 Nov 2020 15:43:44 +0000
Message-ID: <21177_1604504626_5FA2CC31_21177_370_1_787AE7BB302AE849A7480A190F8B93303156FE82@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
References: <160442981984.8698.100494815694851250@ietfa.amsl.com> <888_1604474112_5FA25500_888_442_1_787AE7BB302AE849A7480A190F8B93303156F7F0@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> <6C00489A-9A46-4A6F-8F8C-50C564B616CA@cisco.com> <2804_1604490483_5FA294F3_2804_108_15_787AE7BB302AE849A7480A190F8B93303156FB75@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> <D64A8C72-9321-46CB-829E-F4ACAF91E16A@cisco.com>
In-Reply-To: <D64A8C72-9321-46CB-829E-F4ACAF91E16A@cisco.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="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/z1uUotQYuaOUvt2KKWsq_pFdYQM>
Subject: Re: [Dots] Éric Vyncke's Discuss on draft-ietf-dots-server-discovery-14: (with DISCUSS and COMMENT)
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, 04 Nov 2020 15:43:51 -0000

Re-,

This helpful. Thanks. 

I went with the proposal but without the last sentence. The changes can be tracked at:
https://tinyurl.com/dots-discovery-iesg

Cheers,
Med

> -----Message d'origine-----
> De : Eric Vyncke (evyncke) [mailto:evyncke@cisco.com]
> Envoyé : mercredi 4 novembre 2020 16:11
> À : BOUCADAIR Mohamed TGI/OLN <mohamed.boucadair@orange.com>; The
> IESG <iesg@ietf.org>
> Cc : Valery Smyslov <valery@smyslov.net>; Bernie Volz (volz)
> <volz@cisco.com>; zhencao.ietf@gmail.com; dots@ietf.org;
> tim@qacafe.com; dots-chairs@ietf.org; draft-ietf-dots-server-
> discovery@ietf.org
> Objet : Re: Éric Vyncke's Discuss on draft-ietf-dots-server-
> discovery-14: (with DISCUSS and COMMENT)
> 
> Med,
> 
> I guess we are converging about the remaining point, look for EV2>
> 
> -----Original Message-----
> From: iesg <iesg-bounces@ietf.org> on behalf of
> "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>
> Date: Wednesday, 4 November 2020 at 12:48
> To: Eric Vyncke <evyncke@cisco.com>, The IESG <iesg@ietf.org>
>     >     > -- Section 5.1.2 --
>     >     > I fully second Zhen Cao's review: how will the IPv4-
> mapped
>     > IPv6
>     >     > address(es) be used? They MUST not appear on the wire
> and
>     > there is a
>     >     > DHCPv4 option to convey the DOTS information. Is it when
>     > DHCPv6 is
>     >     > available, no DHCPv4, and only IPv4 connectivity to the
> DOTS
>     > server
>     >     > ? If so, then please clarify the text.
>     >     >
>     >
>     >     [Med] You got it. Added: " This is particularly useful in
> IPv4
>     > service continuity deployments where only DHCPv6 is used."
>     >
>     > EV> I am afraid that more text and explanations are required
> to
>     > clear my remaining DISCUSS even if your suggested modification
> is a
>     > big step forward
>     >
> 
>     [Med] We can add some pointers rather than expanding the text.
> What about:
> 
>     "This is particularly useful in IPv4 service continuity
> deployments (e.g., [RFC6333]) where only DHCPv6 is used and DHCPv4-
> over-DHCPv6 [RFC7341] is not supported."
> 
> EV2> What about
> 
> OLD TEXT
>       Note, IPv4-mapped IPv6 addresses (Section 2.5.5.2 of
> [RFC4291])
>       are allowed to be included in this option.
> 
> NEW TEXT
>       Note, IPv4-mapped IPv6 addresses (Section 2.5.5.2 of
> [RFC4291])
>       MAY to be included in this option when there is no DHCPv4
> server able to advertise the DHCPv4 DOTS options and when only IPv4
> connectivity is possible to the DOTS server. IPv4-mapped IPv6
> addresses MUST NOT be used when there are DHCPv4 servers able to
> advertise the DHCPv4 DOTS options.
> 
> END OF NEW TEXT (the "MUST NOT" may be removed at your convenience)
> 
> 


_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.