Re: [btns] Q: How to deal with connection latch breaks?

Michael Richardson <mcr@sandelman.ottawa.on.ca> Mon, 27 July 2009 17:01 UTC

Return-Path: <mcr@marajade.sandelman.ca>
X-Original-To: btns@core3.amsl.com
Delivered-To: btns@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6983928C245 for <btns@core3.amsl.com>; Mon, 27 Jul 2009 10:01:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.354
X-Spam-Level:
X-Spam-Status: No, score=-1.354 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HOST_MISMATCH_NET=0.311, IP_NOT_FRIENDLY=0.334, J_CHICKENPOX_15=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 67Os2Ce6KH5L for <btns@core3.amsl.com>; Mon, 27 Jul 2009 10:01:23 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [67.23.6.41]) by core3.amsl.com (Postfix) with ESMTP id B0F2228C2F8 for <btns@ietf.org>; Mon, 27 Jul 2009 10:01:23 -0700 (PDT)
Received: from sandelman.ottawa.on.ca (unknown [209.87.252.247]) by relay.sandelman.ca (Postfix) with ESMTPS id 030B634263; Mon, 27 Jul 2009 17:01:24 +0000 (UTC)
Received: from marajade.sandelman.ca (localhost [127.0.0.1]) by sandelman.ottawa.on.ca (Postfix) with ESMTP id EFAC23EC5; Mon, 27 Jul 2009 13:01:23 -0400 (EDT)
From: Michael Richardson <mcr@sandelman.ottawa.on.ca>
To: Nicolas Williams <Nicolas.Williams@sun.com>
In-Reply-To: <20090726221331.GS1020@Sun.COM>
References: <e2cf27e98757db0c8561baadfb3ca335.squirrel@webmail.eisler.com> <20090726221331.GS1020@Sun.COM>
X-Mailer: MH-E 8.1; nmh 1.1; XEmacs 21.4 (patch 21)
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Date: Mon, 27 Jul 2009 13:01:23 -0400
Message-ID: <9481.1248714083@marajade.sandelman.ca>
Sender: mcr@marajade.sandelman.ca
Cc: btns@ietf.org, Mike Eisler <mre-ietf@eisler.com>, lars.eggert@nokia.com
Subject: Re: [btns] Q: How to deal with connection latch breaks?
X-BeenThere: btns@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Better-Than-Nothing-Security Working Group discussion list <btns.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/btns>, <mailto:btns-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/btns>
List-Post: <mailto:btns@ietf.org>
List-Help: <mailto:btns-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/btns>, <mailto:btns-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jul 2009 17:01:24 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


>>>>> "Nicolas" == Nicolas Williams <Nicolas.Williams@sun.com> writes:
    >> My conclusion is that the API ought to provide information for
    >> the application about the connection latching, and it just does
    >> not seem to be there.  If you can point me to a discussion of
    >> this topic on the WG mail list, then I'll clear.  I'm not trying
    >> to alter consensus, but I do want to make sure that this topic
    >> was considered.

    Nicolas> APIs are nice, but existing apps won't use them until
    Nicolas> updated, and anyways, connection latching adds value even
    Nicolas> without adding APIs, which means we need a default response
    Nicolas> to latch breaks in the absence of new APIs (either because
    Nicolas> not implemented or not used).

  So, errno value from write(2) is not a new API.
  A new errno value should provide enough information, I think.

  However, an application might know what to do with ETIMEOUT, while it
would not know what to do with EUNLATCHED or some such....

- -- 
]     Y'avait une poule de jammé dans l'muffler!!!!!!!!!        |  firewalls  [
]   Michael Richardson, Sandelman Software Works, Ottawa, ON    |net architect[
] mcr@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |device driver[
]    h("Just another Debian GNU/Linux using, kernel hacking,    ruby  guy");  [
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Finger me for keys

iQEVAwUBSm3dYoCLcPvd0N1lAQLnNQf8CNCa4TWJY5I/TvtAH4+eyLbHzyO+I/dp
/l5Zcs3Ld16qhYh9OeWogBT2wCeicdx3cL1PdoyibTOfMw/PPxUSY+HKWyR78Ky5
afHA8JxRypvpLqULU7i2jCfwNJZbQi4wojPYl9oeQGAKKmwX3hsBQxKtWY5OWLh+
ExHXfZpGfvauG+LVYHMSNATJEveESpgqRXQyxUqGEChblWVFANHjX/OLJTRCZ7vQ
xXhI2rGIlBOwl9ssAx4vejDR0js8vQ98RXy7XiVJhGZq6+hklOuZfmW44T4iHUNk
emB7EpEWwO7MshVPRCxARIXjICaG2xnQ0XR9ZwSvbtNMsS1vCGVeVg==
=5max
-----END PGP SIGNATURE-----