IETF Logo Mail Archive

Re: [Dots] Alexey Melnikov's Discuss on draft-ietf-dots-signal-channel-31: (with DISCUSS and COMMENT)

<mohamed.boucadair@orange.com> Thu, 02 May 2019 08:25 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 244AB1200B8; Thu, 2 May 2019 01:25:07 -0700 (PDT)
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_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=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 QfYXG906WpND; Thu, 2 May 2019 01:25:04 -0700 (PDT)
Received: from orange.com (mta135.mail.business.static.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 56B8D120307; Thu, 2 May 2019 01:25:04 -0700 (PDT)
Received: from opfednr07.francetelecom.fr (unknown [xx.xx.xx.71]) by opfednr25.francetelecom.fr (ESMTP service) with ESMTP id 44vpGk55sXzCrLj; Thu, 2 May 2019 10:25:02 +0200 (CEST)
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.70]) by opfednr07.francetelecom.fr (ESMTP service) with ESMTP id 44vpGk4L7MzFpWb; Thu, 2 May 2019 10:25:02 +0200 (CEST)
Received: from OPEXCAUBMA2.corporate.adroot.infra.ftgroup ([fe80::e878:bd0:c89e:5b42]) by OPEXCAUBM33.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.03.0439.000; Thu, 2 May 2019 10:25:02 +0200
From: mohamed.boucadair@orange.com
To: Alexey Melnikov <aamelnikov@fastmail.fm>
CC: The IESG <iesg@ietf.org>, "draft-ietf-dots-signal-channel@ietf.org" <draft-ietf-dots-signal-channel@ietf.org>, Liang Xia <frank.xialiang@huawei.com>, "dots-chairs@ietf.org" <dots-chairs@ietf.org>, "dots@ietf.org" <dots@ietf.org>
Thread-Topic: Alexey Melnikov's Discuss on draft-ietf-dots-signal-channel-31: (with DISCUSS and COMMENT)
Thread-Index: AQHVAL7/BSfJAKbW6ky4M5p3lE8N+KZXf0rA
Date: Thu, 02 May 2019 08:25:01 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B93302EA68B20@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
References: <155672115649.991.301467308616633255.idtracker@ietfa.amsl.com> <787AE7BB302AE849A7480A190F8B93302EA68A2C@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> <47A2BACF-3706-4548-A408-9F64C3DF0B20@fastmail.fm>
In-Reply-To: <47A2BACF-3706-4548-A408-9F64C3DF0B20@fastmail.fm>
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/0EHVUi-mICas2szdLZvdH7nrF4o>
Subject: Re: [Dots] Alexey Melnikov's Discuss on draft-ietf-dots-signal-channel-31: (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: Thu, 02 May 2019 08:25:07 -0000

Re-,

Updated my local copy with a pointer to that text. Thanks.

Cheers,
Med

> -----Message d'origine-----
> De : Alexey Melnikov [mailto:aamelnikov@fastmail.fm]
> Envoyé : jeudi 2 mai 2019 10:14
> À : BOUCADAIR Mohamed TGI/OLN
> Cc : The IESG; draft-ietf-dots-signal-channel@ietf.org; Liang Xia; dots-
> chairs@ietf.org; dots@ietf.org
> Objet : Re: Alexey Melnikov's Discuss on draft-ietf-dots-signal-channel-31:
> (with DISCUSS and COMMENT)
> 
> Hi,
> Thank you for detailed replies. Quick answer to one of them:
> 
> On 2 May 2019, at 07:54, <mohamed.boucadair@orange.com>
> <mohamed.boucadair@orange.com> wrote:
> 
> >> 4) Later in the same section:
> >>
> >>   If the request is missing a mandatory attribute, does not include
> >>   'cuid' or 'mid' Uri-Path options, includes multiple 'scope'
> >>   parameters, or contains invalid or unknown parameters, the DOTS
> >>   server MUST reply with 4.00 (Bad Request).  DOTS agents can safely
> >>   ignore comprehension-optional parameters they don't understand.
> >>
> >> How can DOTS agents know which parameters are comprehension-optional?
> >
> > [Med] This is done by looking at the key value:
> >
> >      Key value for the parameter.  The key value MUST be an integer in
> >      the 1-65535 range.  The key values of the comprehension-required
> >      range (0x0001 - 0x3FFF) and of the comprehension-optional range
> >      (0x8000 - 0xBFFF) are assigned by IETF Review (Section 4.8 of
> >      [RFC8126]).  The key values of the comprehension-optional range
> >      (0x4000 - 0x7FFF) are assigned by Specification Required
> >      (Section 4.6 of [RFC8126]) and of the comprehension-optional range
> >      (0xC000 - 0xFFFF) are reserved for Private Use (Section 4.1 of
> >      [RFC8126]).
> 
> I suggest you either add the above text or a pointer to where this is
> discussed.
> 
> Best Regards,
> Alexey

v2.23.0 | Report a Bug | By Email