Re: [dispatch] Reminder: IETF-104 deadlines

Anders Rundgren <> Wed, 13 February 2019 17:26 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 5A673130E69 for <>; Wed, 13 Feb 2019 09:26:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 3X-xDOH34Z42 for <>; Wed, 13 Feb 2019 09:26:42 -0800 (PST)
Received: from ( [IPv6:2a00:1450:4864:20::342]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 4F02712F295 for <>; Wed, 13 Feb 2019 09:26:42 -0800 (PST)
Received: by with SMTP id q21so3293054wmc.5 for <>; Wed, 13 Feb 2019 09:26:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=subject:to:references:from:cc:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=agD0Jc+jevvTFamE9fIQbNw9Az8GX9MS48R5uZ/Qt4E=; b=Whrfxd5L14liMb7Fu/j+mjml0QcghMhE+6gFwHe2LupT4zemnYFkAy5LBy2bkxpk6E +P0SeFgaw43ISqRwEb8KfAkjjQUKXVJSsFgc/m5pwMDBcQIc5ltU7mq/TTJEml8pXbAW Cj4pv7nuU+v6WPic3JQtZizZ9nWhHaQn6mGWeAFi96mafR43MbekkVeW6YJC4dMCGVYb 0opehXKAZWVurqqL/9AoUF66iOL3wr9S+0JxUnaJqSRUcN5PUIvDUOVPe/wcdGubjjUv D2ONOD3yu1DvftAuMRtkhG9WZ4cixh+UDJ7XWcbJWgBsl0/hF6MhBAI+BY0t1Z1O2oUL PSKA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:subject:to:references:from:cc:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=agD0Jc+jevvTFamE9fIQbNw9Az8GX9MS48R5uZ/Qt4E=; b=YQ+Im6pTParFfNnrRo1pkMhn1LrioQBDHMTOfFmcFmURcP4rQpjZH0KkauZcW+GGpQ Kyt1OioqYZlAZi6SdxROMPJWP5Bh/4QQYmzWSvCBawnOUE6cqSr4eQVruvTOAD5L/eqM Hr49k8h+cFFnbz2rCBIMBQ6OMAzNUjUg9q7+q+EUHqLvpKTRR2BX1JdEBvwQrJfy+qPx vO1nIMamos8ALmkKgodcrf4NaQ0M9d6uHwdwMnfIE2JPvOL37N8OmYg7Yiyb3cgG8+j5 s0D05hv5XcpsNRf0MYYJaXSaKzLl7LY+kAjl9bHn10NrYQf+GPGQWR5gF1q3y39HnEew zuag==
X-Gm-Message-State: AHQUAuaoktZeF5AzcIJYblUgzxXEuriEuRPB8EZ4XFRcd7LWd2hK5n4+ WzptcKdZRmMmS/19A99uLoY=
X-Google-Smtp-Source: AHgI3IaIMNy0am9cGMP0zU/eqaq3mdQU6cHzNGZgGqvlHGD9DqZQIyoBHlpZOPp9R4F5BRC6HtV8hg==
X-Received: by 2002:a1c:f207:: with SMTP id s7mr1125180wmc.87.1550078800614; Wed, 13 Feb 2019 09:26:40 -0800 (PST)
Received: from [] ( []) by with ESMTPSA id r12sm21524173wrt.76.2019. (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 13 Feb 2019 09:26:39 -0800 (PST)
To: Mary Barnes <>, DISPATCH <>
References: <>
From: Anders Rundgren <>
Cc: Samuel Erdtman <>, Bret Jordan <>
Message-ID: <>
Date: Wed, 13 Feb 2019 18:26:31 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.5.0
MIME-Version: 1.0
In-Reply-To: <>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <>
Subject: Re: [dispatch] Reminder: IETF-104 deadlines
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DISPATCH Working Group Mail List <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 13 Feb 2019 17:26:44 -0000

The authors of
have already applied for a BoF session but in case this doesn't go through we would be happy to work with DISPATCH as well.


    Cryptographic operations like hashing and signing requires that the
    original data does not change during serialization or parsing.  By
    applying the rules defined by the JSON Canonicalization Scheme (JCS),
    data provided in JSON [RFC8259] format can be exchanged "as is",
    while still being usable by secure cryptographic operations.  JCS
    achieves this by building on the serialization formats for JSON
    primitives as defined by ECMAScript [ES6], constraining JSON data to
    the I-JSON [RFC7493] subset, and through a platform independent
    property sorting scheme.

In an earlier attempt there was a discussion whether this work belonged to the Application or Security area.

With the recent revision this is clearer: "Hashable" JSON is a scheme for Security constructs.

This work *might* also eventually lead to the creation of a standard for signed REST requests.

Anders Rundgren for the JCS team