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

Michael Richardson <mcr@sandelman.ottawa.on.ca> Wed, 05 August 2009 14:55 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 56F5628C599 for <btns@core3.amsl.com>; Wed, 5 Aug 2009 07:55:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.208
X-Spam-Level:
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 mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HPx163XhioVr for <btns@core3.amsl.com>; Wed, 5 Aug 2009 07:55:15 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [67.23.6.41]) by core3.amsl.com (Postfix) with ESMTP id EBF9A28C5AA for <btns@ietf.org>; Wed, 5 Aug 2009 07:54:57 -0700 (PDT)
Received: from sandelman.ottawa.on.ca (unknown [209.87.252.247]) by relay.sandelman.ca (Postfix) with ESMTPS id 7A253343F2 for <btns@ietf.org>; Wed, 5 Aug 2009 14:55:00 +0000 (UTC)
Received: from marajade.sandelman.ca (localhost [127.0.0.1]) by sandelman.ottawa.on.ca (Postfix) with ESMTP id 362C93EC5 for <btns@ietf.org>; Wed, 5 Aug 2009 10:54:59 -0400 (EDT)
From: Michael Richardson <mcr@sandelman.ottawa.on.ca>
To: "btns@ietf.org" <btns@ietf.org>
In-Reply-To: <BF345F63074F8040B58C00A186FCA57F1C22ACD107@NALASEXMB04.na.qualcomm.com>
References: <e2cf27e98757db0c8561baadfb3ca335.squirrel@webmail.eisler.com> <20090726221331.GS1020@Sun.COM> <9481.1248714083@marajade.sandelman.ca> <a0459a6daa0f2f67ff64eb0b2e328a58.squirrel@webmail.eisler.com> <16755.1248953791@marajade.sandelman.ca> <BF345F63074F8040B58C00A186FCA57F1C22ACD07C@NALASEXMB04.na.qualcomm.com> <bce30b84d39f3c1868a8bc75a5458b3b.squirrel@webmail.eisler.com> <BF345F63074F8040B58C00A186FCA57F1C22ACD107@NALASEXMB04.na.qualcomm.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: <7131.1249484099@marajade.sandelman.ca>
Sender: mcr@marajade.sandelman.ca
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: 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
      document.

(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[
] mcr@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |device driver[
]    h("Just another Debian GNU/Linux using, kernel hacking,    ruby  guy");  [