IETF Logo Mail Archive

Re: [arch-d] I-D Action: draft-iab-protocol-maintenance-08.txt

"touch@strayalpha.com" <touch@strayalpha.com> Wed, 13 July 2022 05:08 UTC

Return-Path: <touch@strayalpha.com>
X-Original-To: architecture-discuss@ietfa.amsl.com
Delivered-To: architecture-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5F20CC14F732 for <architecture-discuss@ietfa.amsl.com>; Tue, 12 Jul 2022 22:08:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.325
X-Spam-Level:
X-Spam-Status: No, score=-6.325 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_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=strayalpha.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ApBEVimzfGQw for <architecture-discuss@ietfa.amsl.com>; Tue, 12 Jul 2022 22:08:38 -0700 (PDT)
Received: from server217-2.web-hosting.com (server217-2.web-hosting.com [198.54.115.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5EE94C157B3A for <architecture-discuss@ietf.org>; Tue, 12 Jul 2022 22:08:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=strayalpha.com; s=default; h=To:References:Message-Id:Cc:Date:In-Reply-To: From:Subject:Mime-Version:Content-Type:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=QilKlK24Zvxa/R/ZP8PzlSlh2Z63RIdvLniWQ3sdzGA=; b=sPOMmP0+RPYFZPJrKy/BTBBozJ oR5+tYkfo/y4W9RXet99f43+JWeTQ74rnagMejcH8haXtRZn5vAGuieZEo4M51VzHX+yUS27H19S3 LTdV21x+79cVR1CvP1aIYyznRRS6d1HJCW1o23EolYruv8ih6e1B28YvJODS6yDrJJwMAlgZHJLIF f7h2ovyvNQTp37uZXIcQoPJXc1aCAQ98dLvP2zQ7pM/+Hj04YJyRY7jTSpqXksH6/Tvmoaj12VSam RK3Q6fubDvjmkZwcKCRxrt5cTe+iZPznqvrQab4Ug0G8xTEOH4xvsJYd7ChiKALO4mV92pwHwVqOj /63l72yQ==;
Received: from cpe-172-114-237-88.socal.res.rr.com ([172.114.237.88]:60078 helo=smtpclient.apple) by server217.web-hosting.com with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.95) (envelope-from <touch@strayalpha.com>) id 1oBUbx-00DxxQ-JC; Wed, 13 Jul 2022 01:08:37 -0400
Content-Type: multipart/alternative; boundary="Apple-Mail=_4CE46E16-0F8A-4DCB-9D76-D72A5C7519B0"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.100.31\))
From: "touch@strayalpha.com" <touch@strayalpha.com>
In-Reply-To: <dbee51f0-1913-af6e-de00-c3a7f5b77f68@gmail.com>
Date: Tue, 12 Jul 2022 22:08:27 -0700
Cc: Bernard Aboba <bernard.aboba@gmail.com>, iab@iab.org, architecture-discuss@ietf.org
Message-Id: <1A59B4B5-FA24-4AFD-91D5-14E620DD5E6E@strayalpha.com>
References: <a06000c5-939a-a896-9c0f-576e9e2ff97f@gmail.com> <D20FCDD6-3756-40E7-AD6A-416A2C464DF1@gmail.com> <dbee51f0-1913-af6e-de00-c3a7f5b77f68@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.3696.100.31)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server217.web-hosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - strayalpha.com
X-Get-Message-Sender-Via: server217.web-hosting.com: authenticated_id: touch@strayalpha.com
X-Authenticated-Sender: server217.web-hosting.com: touch@strayalpha.com
X-Source:
X-Source-Args:
X-Source-Dir:
X-From-Rewrite: unmodified, already matched
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/rKCKqfhWsc2lJHhgALnc0uu4m6g>
Subject: Re: [arch-d] I-D Action: draft-iab-protocol-maintenance-08.txt
X-BeenThere: architecture-discuss@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: open discussion forum for long/wide-range architectural issues <architecture-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/architecture-discuss>, <mailto:architecture-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/architecture-discuss/>
List-Post: <mailto:architecture-discuss@ietf.org>
List-Help: <mailto:architecture-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/architecture-discuss>, <mailto:architecture-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jul 2022 05:08:42 -0000

On Jul 12, 2022, at 9:03 PM, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
> 
> Would a state machine analysis detect possible race conditions? These are not mentioned in the draft, and I think they're the sort of corner case that the robustness principle should help with.

Not necessarily; state machine analysis is known to be challenging, esp. for temporal properties (e.g., timed Petri nets, etc.).

Additionally, there’s the difference between the state machine and the implementation; the idea at one point was to generate both the state machine and the protocol implementation from the same description, but it never fully developed.

Joe

v2.23.0 | Report a Bug | By Email