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

Michael Richardson <> Wed, 05 August 2009 14:55 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 56F5628C599 for <>; Wed, 5 Aug 2009 07:55:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.208
X-Spam-Status: No, score=-1.208 tagged_above=-999 required=5 tests=[AWL=0.146, BAYES_00=-2.599, HOST_MISMATCH_NET=0.311, IP_NOT_FRIENDLY=0.334, J_CHICKENPOX_15=0.6]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id HPx163XhioVr for <>; Wed, 5 Aug 2009 07:55:15 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id EBF9A28C5AA for <>; Wed, 5 Aug 2009 07:54:57 -0700 (PDT)
Received: from (unknown []) by (Postfix) with ESMTPS id 7A253343F2 for <>; Wed, 5 Aug 2009 14:55:00 +0000 (UTC)
Received: from (localhost []) by (Postfix) with ESMTP id 362C93EC5 for <>; Wed, 5 Aug 2009 10:54:59 -0400 (EDT)
From: Michael Richardson <>
To: "" <>
In-Reply-To: <>
References: <> <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: Wed, 05 Aug 2009 10:54:59 -0400
Message-ID: <>
Subject: Re: [btns] Q: How to deal with connection latch breaks?
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Better-Than-Nothing-Security Working Group discussion list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 05 Aug 2009 14:55:16 -0000

>>>>> "Julien" == Julien Laganier <Laganier> writes:
    Julien> Sorry I messed up. It should read:

    Julien> ETIMEOUT be returned to the application that didn't used a
    Julien> BTNS API to request the connection be broken when the latch
    Julien> transition to BROKEN, and ELATCHBROKEN otherwise (i.e., the
    Julien> application did use the BTNS API and thus knows what a
    Julien> BROKEN latch and ELACTHBROKEN are, and what to do.)

I concur.
Let's write:
      ETIMEOUT SHOULD be returned to applications when a broken connection
      latch causes communications to fail.  This is consistent with what
      would happen if a cable was unplugged, etc.

      Applications which have used a BTNS API to request a latched
      connection MAY receive a more detailed error to indicate if 
      the communication failure is a result of a connection latch
      being broken.  The details of this process are defined in an API

(I am hoping that we can find a way to avoid a direct reference to the
API document, as that would hold things up further)

]     Y'avait une poule de jammé dans l'muffler!!!!!!!!!        |  firewalls  [
]   Michael Richardson, Sandelman Software Works, Ottawa, ON    |net architect[
] |device driver[
]    h("Just another Debian GNU/Linux using, kernel hacking,    ruby  guy");  [