Re: [Rats] Call for feedback and interest

Carl Wallace <> Thu, 04 August 2022 17:30 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 1341DC15C502 for <>; Thu, 4 Aug 2022 10:30:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.104
X-Spam-Status: No, score=-2.104 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, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 15NfrQbfFCp1 for <>; Thu, 4 Aug 2022 10:30:07 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:4864:20::f33]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by (Postfix) with ESMTPS id F08BAC15C501 for <>; Thu, 4 Aug 2022 10:30:07 -0700 (PDT)
Received: by with SMTP id d1so139589qvs.0 for <>; Thu, 04 Aug 2022 10:30:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=google; h=content-transfer-encoding:mime-version:in-reply-to:references :thread-topic:message-id:cc:to:from:subject:date:user-agent:from:to :cc; bh=Q3sgtROd3AtYQfNZsasjh3ieqbo1U3l/HH+hqeQ4i34=; b=aW/+cdXAiDm9hRZDeMqDX5vZNwq9NSKrRuZQIikAj+HgwCVN0kbhxTnfbl6DYtfANd cSyfSg8U4jTNnS+VjDInZ/3iDxQwiA6zQcNxepChLaDdjScfJ8kGVAFGeMyAvSJXh/U6 4geJd60CVFMyqE7R8dYO2N1ovBqkYygf9XD10=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20210112; h=content-transfer-encoding:mime-version:in-reply-to:references :thread-topic:message-id:cc:to:from:subject:date:user-agent :x-gm-message-state:from:to:cc; bh=Q3sgtROd3AtYQfNZsasjh3ieqbo1U3l/HH+hqeQ4i34=; b=IZqFhIcvghodgmR8Qt3e5cvFyfrLzYcdgUSjkyznCf78lesofqqZ9KhuxcRLxPed8j qWLknCAbL9u7lV40gAu3cYdrtFbjBvfHhHpg52+kUdjvcEmLBAwciEgb9IqJf01oxR2Z CyBU8MCtKosodF4CNNcPXJY3LlB0GODPYta0foxMNJXbJoPVwZFs+6QqFuzGVD4jN4Xg AZLCqAQ/PwQP/y0dfibDw0qqsGqyWYPowsv+y2uNn96bO4QgDyqLRWsHz/Ekhtha7OvP 8SPyFSbPTt6QiXzJdbZNc+N4rbOSJm2aBOpnt8tqfPHGotyhveZBgjN+BPRoJjxYThv8 50tQ==
X-Gm-Message-State: ACgBeo1uE6HemhQPkcR49yt2iqtTU0PjZd3swGnHdLH3GVJySQ63XIrk kJ9yJq056nmU/Hjf4q5yL5UZxodqkyI2Dg==
X-Google-Smtp-Source: AA6agR68SOgSZn2GcmoSAM4FxMurSzkfYuAzQgi42DLDV5nxrBgx6u0LopNHweTNonC6dnyHfecYRA==
X-Received: by 2002:ad4:594c:0:b0:477:1f90:1b4 with SMTP id eo12-20020ad4594c000000b004771f9001b4mr2534299qvb.45.1659634206702; Thu, 04 Aug 2022 10:30:06 -0700 (PDT)
Received: from [] ( []) by with ESMTPSA id f12-20020ac87f0c000000b0031ea864d3b2sm1030145qtk.30.2022. (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 04 Aug 2022 10:30:06 -0700 (PDT)
User-Agent: Microsoft-MacOutlook/16.63.22070801
Date: Thu, 04 Aug 2022 13:30:05 -0400
From: Carl Wallace <>
To: Michael Richardson <>, "Nancy Cam-Winget (ncamwing)" <>
CC: "" <>
Message-ID: <>
Thread-Topic: [Rats] Call for feedback and interest
References: <> <19156.1659543376@localhost>
In-Reply-To: <19156.1659543376@localhost>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Archived-At: <>
Subject: Re: [Rats] Call for feedback and interest
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Remote ATtestation procedureS <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 04 Aug 2022 17:30:12 -0000

I can move the hex dump to an appendix and base64 encode it instead in the next release. I tend to favor ASCII hex for things like this so CBOR or DER can be read without decoding but it's not a strong preference.

On 8/3/22, 12:16 PM, "RATS on behalf of Michael Richardson" < on behalf of> wrote:

    I believe that I have previously reviewed this document, and found it worth adopting.

    I think it is important.  I think that it may have much wider applicability
    than RATS, but _Perfect is the Enemy of Good Enough_, so I am happy to limit
    applicability for now.

    I like the examples, but I would prefer the hexdump was in an appendix,
    and maybe that it was base64 encoded, as I find that it is easier to deal

    Nancy Cam-Winget \(ncamwing\) <> wrote:
        > There was discussion at the IETF 114 RATs session on defining a CoRIM
        > Extension to facilitate the conveyance of constrained trust anchor (TA)
        > stores.  The details are in

        > There was both a question of interest and whether RATs would be the
        > appropriate place to work on this draft as it has wider applicability
        > beyond RATs.

        > This is to start a discussion thread to get feedback on:

        >   1.  Is this work that is of interest to the IETF? (and if Yes) * Is
        > RATs the appropriate working group to work on the draft * Is the draft
        > ready for adoption?

        > Other feedback on the draft is also requested.

        > Thanks, Nancy

        > ----------------------------------------------------
        > Alternatives:

        > ----------------------------------------------------
        > _______________________________________________ RATS mailing list

    Michael Richardson <>   . o O ( IPv6 IøT consulting )
               Sandelman Software Works Inc, Ottawa and Worldwide

    RATS mailing list