[core] ETag vs. Block Identifier

mohamed.boucadair@orange.com Thu, 11 June 2020 06:53 UTC

Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8FCE73A0F30; Wed, 10 Jun 2020 23:53:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.095
X-Spam-Level:
X-Spam-Status: No, score=-2.095 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, HTML_MESSAGE=0.001, 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 3eKmCaVJ1MNx; Wed, 10 Jun 2020 23:53:46 -0700 (PDT)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.66.39]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F3C593A0ED2; Wed, 10 Jun 2020 23:53:42 -0700 (PDT)
Received: from opfedar07.francetelecom.fr (unknown [xx.xx.xx.9]) by opfedar26.francetelecom.fr (ESMTP service) with ESMTP id 49jF1x2dyTzFpvm; Thu, 11 Jun 2020 08:53:41 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orange.com; s=ORANGE001; t=1591858421; bh=a18u3MH7jRtAYIRmAKTC5taQfRyXFqIwdUfnland5kY=; h=From:To:Subject:Date:Message-ID:Content-Type:MIME-Version; b=ufmjlAoehwt54QIYurgsNx/QYtj1MUWsMoFBXAxgqQ+4QpdRyBXQe9HyaqiYxzHvU fgdwlCqqn3gXdNegiBBGQC/gNy+CN3y/Jaas7py44nO8XBKJgUyqcTncfcSXmmksnW XkB5wmDKJYsLaYdLtapitOp/PqIeq2LV+IbE6Lr8Y4l721X9KZ1xB1p7IRH4jnuKBr KU8M2YL/jh/VTd3qFhYfnH/KZZLV/xhpcPZgFEBNo3TXVrBO7k2eIR3QDTff8dE8JQ VfL9/N2pigM4z1PFGZrGVtpCnb2Yj9Iqk0mFvupGXQWS799tlOph20GiwRgBf+OSi5 FXLO4IBblQ5WA==
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.92]) by opfedar07.francetelecom.fr (ESMTP service) with ESMTP id 49jF1x1Qszz5vT5; Thu, 11 Jun 2020 08:53:41 +0200 (CEST)
From: mohamed.boucadair@orange.com
To: "Christian Amsüss (christian@amsuess.com)" <christian@amsuess.com>, "Carsten Bormann (cabo@tzi.org)" <cabo@tzi.org>, "core@ietf.org" <core@ietf.org>
CC: "draft-bosh-core-new-block@ietf.org" <draft-bosh-core-new-block@ietf.org>
Thread-Topic: ETag vs. Block Identifier
Thread-Index: AdY/vQi72Dgc4yCYSFaTRadsL6au8w==
Date: Thu, 11 Jun 2020 06:53:40 +0000
Message-ID: <29244_1591858421_5EE1D4F5_29244_364_1_787AE7BB302AE849A7480A190F8B9330314DC153@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
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: multipart/alternative; boundary="_000_787AE7BB302AE849A7480A190F8B9330314DC153OPEXCAUBMA2corp_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/0NgBpedt1vNoqfpgI8X80Ng47TQ>
Subject: [core] ETag vs. Block Identifier
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/core>, <mailto:core-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/core/>
List-Post: <mailto:core@ietf.org>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Jun 2020 06:53:48 -0000

Hi Christian/Carsten, all,

It was suggested during yesterday's meeting that ETag can be used to achieve what BID is intended for in draft-bosh-core-new-block (block4 case). We still don't see how that would work given that only a 2.03 will be sent as per Section 5.10.6.2 of RFC7252.

Can you please clarify how a missing block can be sent back as a response to a GET+ETag?

Thank you.

Cheers,
Med




_________________________________________________________________________________________________________________________

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.